profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/johnhany97/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
John H. Ayad johnhany97 Palantir Technologies London, UK http://JohnAyad.com Software Engineer @palantir

johnhany97/dental-clinic-system 1

Dental Clinic Appointments and Patients management System in Java

johnhany97/Android-Push-Notify 0

Push notification to mutiple Android devices from local server using Google Cloud Messaging(GCM)

johnhany97/angular-project 0

Recipes and Shopping list app

johnhany97/angular-tour-of-heroes 0

Angular application to cover basics of Angular Framework

johnhany97/appengine-apns-gcm 0

A unified push service for iPhone and Android push notifications that runs on Google App Engine (GAE).

johnhany97/banko 0

Personal banking web-app to montiro financial transactions across your various banks using Plaid

johnhany97/CCI-solutions 0

Cracking the Coding Interview - 6th edition solutions in Python

push eventconda-forge/iso3166-feedstock

regro-cf-autotick-bot

commit sha 830f6425d86e7a7c90409c74d2d239b891aabceb

updated v2.0.2

view details

John H. Ayad

commit sha ef2868fa47a2909ef154e6c0444b4c12a8aff7d9

Merge pull request #4 from regro-cf-autotick-bot/2.0.2_h827c04

view details

push time in 2 days

PR merged conda-forge/iso3166-feedstock

Reviewers
iso3166 v2.0.2

It is very likely that the current package version for this feedstock is out of date. Notes for merging this PR:

  1. Feel free to push to the bot's branch to update this PR if needed.
  2. The bot will almost always only open one PR per version. Checklist before merging this PR:
  • [ ] Dependencies have been updated if changed: see upstream
  • [ ] Tests have passed
  • [ ] Updated license if changed and license_file is packaged

Note that the bot will stop issuing PRs if more than 3 Version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.

NEW: If you want these PRs to be merged automatically, make an issue with <code>@conda-forge-admin,</code>please add bot automerge in the title and merge the resulting PR. This command will add our new bot automerge feature to your feedstock!

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase <code>@<space/>conda-forge-admin, please rerun bot</code> in a PR comment to have the conda-forge-admin add it for you.

<sub>This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. If you would like a local version of this bot, you might consider using rever. Rever is a tool for automating software releases and forms the backbone of the bot's conda-forge PRing capability. Rever is both conda (conda install -c conda-forge rever) and pip (pip install re-ver) installable. Finally, feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/autotick-bot/actions/runs/1255779739, please use this URL for debugging</sub>

Dependency Analysis

Please note that this analysis is highly experimental. The aim here is to make maintenance easier by inspecting the package's dependencies. Importantly this analysis does not support optional dependencies, please double check those before making changes. If you do not want hinting of this kind ever please add bot: inspection: false to your conda-forge.yml. If you encounter issues with this feature please ping the bot team conda-forge/bot.

Analysis of the source code shows no discrepancy between the library's imports and the package's stated requirements in the meta.yaml.

+2 -2

1 comment

1 changed file

regro-cf-autotick-bot

pr closed time in 2 days

push eventconda-forge/iso3166-feedstock

regro-cf-autotick-bot

commit sha 1b26f96ed48018bb862125e4f1f7c811ec595dce

updated v2.0.1

view details

regro-cf-autotick-bot

commit sha 629970a2d0cce0e99d5e0fd22caf7a52294f45bf

MNT: Re-rendered with conda-build 3.21.4, conda-smithy 3.12, and conda-forge-pinning 2021.09.15.18.54.07

view details

John H. Ayad

commit sha 800794a874d782fc24c4205b24a5141ebf80d2ec

Merge pull request #3 from regro-cf-autotick-bot/2.0.1_h1c84ab iso3166 v2.0.1

view details

push time in 7 days

PR merged conda-forge/iso3166-feedstock

Reviewers
iso3166 v2.0.1

It is very likely that the current package version for this feedstock is out of date. Notes for merging this PR:

  1. Feel free to push to the bot's branch to update this PR if needed.
  2. The bot will almost always only open one PR per version. Checklist before merging this PR:
  • [x] Dependencies have been updated if changed: see upstream
  • [x] Tests have passed
  • [x] Updated license if changed and license_file is packaged

Note that the bot will stop issuing PRs if more than 3 Version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.

NEW: If you want these PRs to be merged automatically, make an issue with <code>@conda-forge-admin,</code>please add bot automerge in the title and merge the resulting PR. This command will add our new bot automerge feature to your feedstock!

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase <code>@<space/>conda-forge-admin, please rerun bot</code> in a PR comment to have the conda-forge-admin add it for you.

<sub>This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. If you would like a local version of this bot, you might consider using rever. Rever is a tool for automating software releases and forms the backbone of the bot's conda-forge PRing capability. Rever is both conda (conda install -c conda-forge rever) and pip (pip install re-ver) installable. Finally, feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/autotick-bot/actions/runs/1241605526, please use this URL for debugging</sub>

Dependency Analysis

Please note that this analysis is highly experimental. The aim here is to make maintenance easier by inspecting the package's dependencies. Importantly this analysis does not support optional dependencies, please double check those before making changes. If you do not want hinting of this kind ever please add bot: inspection: false to your conda-forge.yml. If you encounter issues with this feature please ping the bot team conda-forge/bot.

Analysis of the source code shows no discrepancy between the library's imports and the package's stated requirements in the meta.yaml.

+2 -8

1 comment

2 changed files

regro-cf-autotick-bot

pr closed time in 7 days

push eventconda-forge/iso3166-feedstock

regro-cf-autotick-bot

commit sha 3decdcc962ee30c354f53f139792db7f91a575fb

updated v2.0.0

view details

regro-cf-autotick-bot

commit sha 1ea9c4d029eee4f1ca8864513e55352b0efd21cb

MNT: Re-rendered with conda-build 3.21.4, conda-smithy 3.12, and conda-forge-pinning 2021.09.15.06.06.59

view details

John H. Ayad

commit sha ce2ae7133b83eca6db6d705fa51114df71afe1a0

Update meta.yaml

view details

John H. Ayad

commit sha d332441195acb5705bf0040904f5ff077007e15e

Merge pull request #1 from regro-cf-autotick-bot/2.0.0_he39f7c

view details

push time in 7 days

PR merged conda-forge/iso3166-feedstock

Reviewers
iso3166 v2.0.0

It is very likely that the current package version for this feedstock is out of date. Notes for merging this PR:

  1. Feel free to push to the bot's branch to update this PR if needed.
  2. The bot will almost always only open one PR per version. Checklist before merging this PR:
  • [x] Dependencies have been updated if changed: see upstream
  • [x] Tests have passed
  • [x] Updated license if changed and license_file is packaged

Note that the bot will stop issuing PRs if more than 3 Version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.

NEW: If you want these PRs to be merged automatically, make an issue with <code>@conda-forge-admin,</code>please add bot automerge in the title and merge the resulting PR. This command will add our new bot automerge feature to your feedstock!

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase <code>@<space/>conda-forge-admin, please rerun bot</code> in a PR comment to have the conda-forge-admin add it for you.

<sub>This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. If you would like a local version of this bot, you might consider using rever. Rever is a tool for automating software releases and forms the backbone of the bot's conda-forge PRing capability. Rever is both conda (conda install -c conda-forge rever) and pip (pip install re-ver) installable. Finally, feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/autotick-bot/actions/runs/1236689650, please use this URL for debugging</sub>

Dependency Analysis

Please note that this analysis is highly experimental. The aim here is to make maintenance easier by inspecting the package's dependencies. Importantly this analysis does not support optional dependencies, please double check those before making changes. If you do not want hinting of this kind ever please add bot: inspection: false to your conda-forge.yml. If you encounter issues with this feature please ping the bot team conda-forge/bot.

Analysis of the source code shows no discrepancy between the library's imports and the package's stated requirements in the meta.yaml.

+184 -38

2 comments

10 changed files

regro-cf-autotick-bot

pr closed time in 7 days

push eventregro-cf-autotick-bot/iso3166-feedstock

John H. Ayad

commit sha ce2ae7133b83eca6db6d705fa51114df71afe1a0

Update meta.yaml

view details

push time in 7 days

issue commentmamba-org/mamba

Basic auth gets dropped from some network requests, leading to failures

Hey @wolfv - sorry for taking a while to come back on this one. I've stripped down our server to the most core version of it and still got the issues described above with the upgraded curl. So from there, I've gone ahead and put up https://github.com/mamba-org/mamba/pull/1141 which has a repro of the same bug we're seeing, using the examples provided from this repo.

We were also able to find that this issue only comes up when the connection is being re-used. This is not to say that if the connection was reused, the auth header is dropped, but more like -> we never saw this issue come up unless the connection was reused.

Notably, we saw that:

* Connection #4 to host localhost left intact
* Couldn't find host localhost in the (nil) file; using defaults
* Found bundle for host localhost: 0x7fbd8fd4a640 [serially]
* Re-using existing connection! (#0) with host localhost
* Connected to localhost (127.0.0.1) port 8080 (#0)
* Transfer was pending, now try another
> GET /service/noarch/repodata.json HTTP/1.1
Host: localhost:8080
Accept: */*
Accept-Encoding: gzip, deflate, compress, identity
Content-Type: application/json

for a request that got a 401, but then saw

* Couldn't find host localhost in the (nil) file; using defaults
* Found bundle for host localhost: 0x7f8fe0e08f30 [serially]
* Re-using existing connection! (#0) with host localhost
* Connected to localhost (127.0.0.1) port 8080 (#0)
* Server auth using Basic with user ''
> GET /service/noarch/test-package-0.1-0.tar.bz2 HTTP/1.1
Host: localhost:8080
Authorization: Basic KG5pbCk6dGVzdA==
Accept: */*

for a successful, non 401, request.

It's interesting to see * Server auth using Basic with user '' show up in the successful one, but not in the failing one. And that seems to be the case for all the logs I have.

johnhany97

comment created time in a month

PR opened mamba-org/mamba

Repro libcurl 401s

Reproing https://github.com/mamba-org/mamba/issues/1132

Running this locally after setting up the dev environment will lead to this snippet:

127.0.0.1 - - [24/Aug/2021 15:01:29] "GET /noarch/repodata.json HTTP/1.1" 401 -
Got Basic KG5pbCk6dGVzdA==
Got Basic KG5pbCk6dGVzdA==
127.0.0.1 - - [24/Aug/2021 15:01:31] "GET /osx-64/repodata.json HTTP/1.1" 401 -
127.0.0.1 - - [24/Aug/2021 15:01:31] "GET /osx-64/repodata.json HTTP/1.1" 401 -
Got Basic KG5pbCk6dGVzdA==
127.0.0.1 - - [24/Aug/2021 15:01:31] "GET /osx-64/repodata.json HTTP/1.1" 401 -
Got Basic KG5pbCk6dGVzdA==
127.0.0.1 - - [24/Aug/2021 15:01:31] "GET /noarch/repodata.json HTTP/1.1" 401 -
Got Basic KG5pbCk6dGVzdA==
127.0.0.1 - - [24/Aug/2021 15:01:31] "GET /noarch/repodata.json HTTP/1.1" 401 -
Got
127.0.0.1 - - [24/Aug/2021 15:01:31] "GET /noarch/repodata.json HTTP/1.1" 401 -
Got Basic KG5pbCk6dGVzdA==
127.0.0.1 - - [24/Aug/2021 15:01:33] "GET /osx-64/repodata.json HTTP/1.1" 401 -
Got Basic KG5pbCk6dGVzdA==
127.0.0.1 - - [24/Aug/2021 15:01:33] "GET /osx-64/repodata.json HTTP/1.1" 401 -
Got Basic KG5pbCk6dGVzdA==
127.0.0.1 - - [24/Aug/2021 15:01:33] "GET /osx-64/repodata.json HTTP/1.1" 401 -
Got Basic KG5pbCk6dGVzdA==
127.0.0.1 - - [24/Aug/2021 15:01:33] "GET /noarch/repodata.json HTTP/1.1" 401 -
Got Basic KG5pbCk6dGVzdA==
127.0.0.1 - - [24/Aug/2021 15:01:33] "GET /noarch/repodata.json HTTP/1.1" 401 -
Got
127.0.0.1 - - [24/Aug/2021 15:01:33] "GET /noarch/repodata.json HTTP/1.1" 401 -

Noting how some of the requests have nothing logged for the auth header, while the others do.

+16 -29

0 comment

2 changed files

pr created time in a month

create barnchjohnhany97/mamba

branch : jayad/repro

created branch time in a month

issue commentmamba-org/mamba

Basic auth gets dropped from some network requests, leading to failures

Link to the PR with the workaround in the meantime so that mamba isn't blocked on investigating the libcurl issue https://github.com/mamba-org/mamba/pull/1131

johnhany97

comment created time in a month

issue openedmamba-org/mamba

Basic auth gets dropped from some network requests, leading to failures

In an internal setup, we have conda channels that require basic auth for access purposes. An example call to a repodata.json file would require us to hit:

https://:$TOKEN@host/channel/repodata.json

We therefore pass to mamba the following 2 args

mamba ... --override-channels -c https://:$TOKEN@host/channel1/repodata.json -c https://:$TOKEN@host/channel2/repodata.json

Initially, we were using mamba 0.9.0, but we wanted to bump to a later mamba to benefit from the improvements recently made to the solve mechanism. However, on bumping to the latest release, 0.15.2, we noticed that we started seeing errors manifesting as:

ERROR File not valid: file size doesn't match expectation "/tmp/caches/CONDA_PKGS_DIRS/future-0.18.2-py36h5fab9bb_3.tar.bz2"

Expected: 733415

That was the time we opened https://github.com/mamba-org/mamba/pull/1095 to get more logs. In the meantime, upon upping the verbosity, I noticed we always got a result of size 71 bytes, and a HTTP status code 401 for all these random packages.

At the same time, we had a MambaSolver implemented that uses the Python APIs and we noticed that one also started exhibiting 401s, though on downloading the repodata.json files.

These errors manifest from https://github.com/mamba-org/mamba/blob/0.15.2/mamba/utils.py#L100 with the exception:

Runtime Error: Multi-download failed.

From what we can tell, those 401s thrown from our server-side mean that the authorization header never got to the service.

We binary searched our way through mamba releases to find this broke between 0.9.0 and 0.9.2. We noticed that mamba 0.9.0 had the following spec for libcurl:

libcurl >=7.75.0,<8.0a0

while 0.9.2 had:

libcurl >=7.76.0,<8.0a0

So on attempting to install mamba 0.9.0, which we know doesn't exhibit this bug, in our environment, we required libcurl to be >=7.76.0 and we saw the bug come back again.

Given the above investigation, we believe the bug is in libcurl, though a little bit hard to pinpoint given the amount of changes made between 7.75.0 and 7.76.0.

We propose as a workaround that we downgrade libcurl in mamba, as we don't particularly leverage any newer feature from libcurl AFAICT until this is followed up on with curl.

N.B. I do suspect https://github.com/curl/curl/commit/27fb920abe23468b503f178bc62fdec3f29d3cf6 might be a relevant change, but I am not certain enough.

created time in a month

push eventjohnhany97/stmarkos-scouts

John Ayad

commit sha fd969a24a1650f32b6b86f202aee28fa442ac68e

announcement

view details

push time in a month

PR opened gradlets/gradle-typescript

Fix: Stop using deprecated property

Before this PR

Applying the webpack plugin leads to errors like:

The SourceDirectorySet.outputDir property has been deprecated. This is scheduled to be removed in Gradle 8.0. Please use the classesDirectory property instead. See https://docs.gradle.org/7.1.1/dsl/org.gradle.api.file.SourceDirectorySet.html#org.gradle.api.file.SourceDirectorySet:outputDir for more details.
        at org.gradle.api.internal.file.DefaultSourceDirectorySet.getOutputDir(DefaultSourceDirectorySet.java:202)
        at com.gradlets.baseline.typescript.BaselineWebpack.lambda$applyInternal$2(BaselineWebpack.java:56)
        at org.gradle.api.internal.DefaultMutationGuard$2.execute(DefaultMutationGuard.java:44)
        at org.gradle.api.internal.DefaultMutationGuard$2.execute(DefaultMutationGuard.java:44)

After this PR

Stop using outputDir

+1 -1

0 comment

1 changed file

pr created time in a month

create barnchjohnhany97/gradle-typescript

branch : jayad/gradle7

created branch time in a month

pull request commentmamba-org/mamba

Improvement: Log actual MD5/Size/SHA256 when we fail to validate

Unsure why umamba_tests are failing checks. The error seems to be a 443: Connection refused which makes me suspect this is not relevant to the changes introduced in the PR.

johnhany97

comment created time in 2 months

push eventjohnhany97/mamba

John H. Ayad

commit sha e90a615cedf7a2dcec36a13e4520f3d1a87da79a

Update transaction.cpp

view details

push time in 2 months

PR opened mamba-org/mamba

Improvement: Log actual MD5/Size/SHA256 when we fail to validate

Before this PR

Currently when mamba logs the validation error, we only see information about what we expect, with no info on what was expected. Example:

ERROR File not valid: file size doesn't match expectation "/tmp/caches/CONDA_PKGS_DIRS/future-0.18.2-py36h5fab9bb_3.tar.bz2"

Expected: 733415

or

ERROR File not valid: MD5 sum doesn't match expectation "/tmp/caches/CONDA_PKGS_DIRS/pip-21.1.3-py36h06a4308_0.tar.bz2"

Expected: 5ffa50ebfad2aab590348cff27322d32

After this PR

I propose we additionally log the actual value we got, not just the expected value. This should help facilitate debugging issues and help understand what was going on.

+6 -3

0 comment

1 changed file

pr created time in 2 months

create barnchjohnhany97/mamba

branch : jayad/more-info

created branch time in 2 months

fork johnhany97/mamba

The Fast Cross-Platform Package Manager

fork in 2 months

push eventjohnhany97/stmarkos-scouts

John Ayad

commit sha 2793689f923e1676232c9ab1d04b900d8d5d04ef

Announcement

view details

push time in 2 months

push eventjohnhany97/stmarkos-scouts

John H. Ayad

commit sha f3c0015bfd12ef512506f525ade1a828757512f7

Create index.md

view details

push time in 3 months