Joel Willi

Thank you @matus-tomlein - I will be able to look into it on Monday.

This solution should solve our current problem, and I also appreciate the options provided to further specify an appropriate strategy such as `pathname`. Thank you! However, we are currently aiming...

As an addition to my previous comment: If there is some sort of override available in combination with a global context getter, this could work with a deferred approach. But...

Sure thing, good questions. 1. We don't see this bahaviour with the `keepalive` setting turned off with `false` (same Chrome incognito) 2. We are not sending snowplow tracking events through...

Beside changing our host setting I will also play around with the `bufferSize` setting to check if this will have any impact by reducing the amount of concurrent keepalive requests....

Ah, then I misunderstood the bufferSize setting. I thought that requests would hold the amount of events represented by this number; e.g., a `bufferSize: 16` would collect 16 events in...

Alright - I'll come back to this in a later point of time, as we would like to experiment with increasing the bufferSize and e.g. flush on demand on tab...

Thanks for the update @matus-tomlein, the issue is still occurring with the new changes in place. I see a higher chance of success with a buffer size of 1 compared...

The issue might be that we currently don't match hexadecimal digits (which include the characters 0-9 and A-F/a-f). [pgloader/src/parsers/parse-pgpass.lisp](https://github.com/dimitri/pgloader/blob/70f355767018cc1d2770948563100b328fcc3f26/src/parsers/parse-pgpass.lisp#L18C44-L18C66) I think we should use: ```lisp (digit-char-p character 16) ``` This...

I'm not sure how to contribute a pull request or how the workflow regarding permissions should be. But it would be awesome if you could confirm my assumption, @dimitri, and...