Andrew K comments

Results 77 comments of


                                            Andrew K

pytest-flake8 is very slow and uses lots of RAM with -vv

Have the same problem, no .tox in the project

Using fireEvent.change() on a select element fires the event handler, but doesn't update state.

Same error, happened after upgrade from react 17 to react 18. adding `{delay: 0}` fixed the problem and I have no idea, why

Using fireEvent.change() on a select element fires the event handler, but doesn't update state.

Oh, I found, why. Both of us are missing await after userEvent.type

Using fireEvent.change() on a select element fires the event handler, but doesn't update state.

This issue is because issue author forgot to add await in their code (me as well) On Mon, Jun 6, 2022, at 00:01, Sebastian Silbermann wrote: > > > For...

Using fireEvent.change() on a select element fires the event handler, but doesn't update state.

Cannot access [Model] before initialization

I'm trying to remove emitDecoratorMetadata option. If you set types/table names manually it can be a solution as well

Rewrite local git detection using git command

@nickmerwin after `git gc` it puts that file to `.git/packed-refs` So I vote for this pull request

Protocol error in kinesis putRecords in aws sdk > 3.81.0

I confirm that it is not fixed in 3.128.0 Here is what I have in Sentry (not much) It can be kinesis problem and not SDK, related: https://github.com/awslabs/amazon-kinesis-client/issues/711

Protocol error in kinesis putRecords in aws sdk > 3.81.0

@cesarfd let's try to debug. Do you use some other other AWS service, which does not support http2, for example DynamoDB? This error happens if someone uses http2 protocol for...

Protocol error in kinesis putRecords in aws sdk > 3.81.0

Here is my workaround: ``` const usKinesis = new KinesisClient({ region: "us-east-1", requestHandler: new NodeHttpHandler() }); ```