Bernhard Frauendienst

I can confirm that this leads to the session being loaded from redis multiple times per request, which really should be avoided.

I don't think the secrets are evaluated by the `eval` call. They are already evaluated as part of the `overwrite` value by GitHub Actions. You need to escape the `${{...}}}`...

I believe you have to add the device using AddDevice with BackgroundScan action. Then you'll get a passive scan with multiple events. Afaict, the kernel mgmt interface does not allow...

I don't even have PowerToys installed, but still experiencing the same issue. It gets massively worse if there is more than one WSLg window open, at that point I can...

> I guess, some features require the future parser or Puppet 4. That would be foremost the iterations. The checks on newer puppet versions seem to fail only on the...

We're facing the same issue in `@aws-amplify/auth`. The token is still valid when it's validated on the client, but 0.3 seconds later, when the server checks, it's expired.

The relevant code for @aws-amplify/auth is probably here https://github.com/aws-amplify/amplify-js/blob/72c43643065da09908f83968996cea4243fdadda/packages/auth/src/providers/cognito/tokenProvider/TokenOrchestrator.ts#L118-L138 and here https://github.com/aws-amplify/amplify-js/blob/72c43643065da09908f83968996cea4243fdadda/packages/core/src/singleton/Auth/index.ts#L12-L22

Just for the record, please note that we are not using a custom expiration time, but the standard time of 60 minutes. However, we have a polling task that runs...

Not currently, no, because it loads @remix-run packages which will no longer be part of your node_modules after migration to react router 7.

I've forked this as https://github.com/oxc/react-router-aws and published as https://www.npmjs.com/package/react-router-aws, because I needed it urgently for a project. I'm more than happy to hand over both projects back to @wingleung !!...