You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like zef has a bad failure mode if the file obtained from the ecosystem is being blocked / redirected / replaced by garbage that is not the right JSON: like the ecosystem is empty.
Spotted at the GPW of which the WiFi apparently had some parental controls enabled on one of the outer routers.
The text was updated successfully, but these errors were encountered:
lizmat
changed the title
zef not copying with parental controls / filters / proxies doing wrong things
zef not coping with parental controls / filters / proxies doing wrong things
Mar 7, 2019
The above should probably fail if it gets invalid json. So this should probably throw, and be caught inside Zef::Repository (where it gets called) to deliver the exception message via $logger.emit(...).
If the content of the package list is not valid json then report
this to the user and don't overwrite any (possibly) existing
valid json package list.
Resolves#292
It looks like
zef
has a bad failure mode if the file obtained from the ecosystem is being blocked / redirected / replaced by garbage that is not the right JSON: like the ecosystem is empty.Spotted at the GPW of which the WiFi apparently had some parental controls enabled on one of the outer routers.
The text was updated successfully, but these errors were encountered: