Bastien Gandouet

A different use case than what was described here before: we need (and forked to get) a second entrypoint for our service worker. The current SW approaches (with workbox and...

Our fork is pretty much "make it work" for our use case, definitely not "make it right". There would be multiple other concerns for inclusion in a project like CRA...

Hey, sorry I didn't anwser, I haven't got any notification... I'm not confortable uploading a "real" module doing what is showcased here to npm, basically we are monkey-patching `text-encoding` (this...

From the signature there for instance : https://github.com/agronholm/apscheduler/blob/18b50d9ee9ff14e816b557e34d7d3abc861d57e5/apscheduler/triggers/interval.py#L22. Also there : https://github.com/agronholm/apscheduler/blob/7e78cad90ce080825c46de8967d9573e9fc86353/apscheduler/job.py#L32 "It works with datetime, but if you specify a `tzinfo` it must comes from `pytz`" is not very...

To precise my comment (and issue) the fact that when giving explicit timezone to apscheduler you have to use `pytz` stuff is not a problem (and I apologize for not...

There are two closely related but different subjects : the timezones we give directly to apscheduler and the timezones attached to datetimes we give to apscheduler. ### Timezone gave to...

Cool, feel free to ping me if/when you want help on this matter 👍

> Hey, did you implement the distributed scheduler architecture you mentioned above? Were there any pitfalls or unexpected bugs you encountered if you did? We did, no particular roadblock to...

> Great! Thank you very much for the information You're welcome, apscheduler is a great-rock-solid project, we're happy if we can somewhat contribute back to the community. I needed, this...

Locally at least (through `chalice local`) this issue is not resolved. With @cmann50 example (that I reproduce below), if you're not authorized to access the endpoint the OPTIONS request will...