Mathieu Agopian

Hi, I'm not maintaining this repository anymore. If it's useful to you, please let me know and we can discuss adding you as a maintainer. Regarding the travis failure, it...

Thanks @nnako for your work! However, I don't think the key itself should be bytes, should it? According to the py33 test in travis, the key doesn't exist. The py27...

Thanks for the feedback, I've updated the `keymap.md` file accordingly 👍

J'ai pu tester hier, et il me semble bien que ça retiens les infos. Le 4 avril 2020 02:35:21 GMT+02:00, Joachim Jablon a écrit : >J’ouvre une issue pour discuter...

Je pense oui, mais ils ont retiré le site (jusqu'à lundi ? ah ces effets d'annonce ...)

The interpreter version that's displayed in travis is the one used by the travis.yml file. But this file is only used to "proxy" to tox: https://github.com/clouserw/tower/pull/32/files#diff-354f30a63fb0907d4ad57269548329e3L13 What you want, though,...

Ah, that's a hard problem to solve then, chicken and egg of some sorts. How did you make sure the code was compatible (and ran correctly) under py3 if the...

A few questions: - does it make sense to duplicate the data if it's already displayed (very nicely!) in mission control? - which data point would we be interested in?...

I could be totally wrong, but I thought that the current code would result in an error (`response.json()` would throw), and thus be caught by the caller: https://github.com/mozilla/delivery-dashboard/blob/master/src/sagas.js#L158-L163

Yeah the `console.error` was meant to be temporary and an added information when debugging (like it's done some other sagas where you would also display a nice error to the...