Michał Dzienisiewicz
Michał Dzienisiewicz
I can confirm that upgrading Chrome from v104 to v105 has exposed the same behavior.
Any update on this?
@bnoordhuis ```javascript // since it's ESM, save it as .mjs import fs from 'node:fs' import process from 'node:process' import {Readable} from 'node:stream' // we initialize a stream, but not start...
@debadree25 Sounds like a workaround that is good enough for me, thanks!
In meanwhile I found another workaround - `ReadableStream.from(randomNodeStream)` seems to do the job just right, without having to set the queueing strategy explicitly.
We have tested 10.3.0 and 10.5.0 on Node 21.7.3 & MacOS Sonoma and unfortunately the problem is still there.
OK, I've tested my hypothesis by adding extra checks for emptiness and unfortunately that's not it. The fixed code immediately tries to log in using username & password, but it...
I've contacted Proton using URL received in the error and that's their response: > Hello, > > Thank you for your message. > > Please note that this error message...
@EnneGiKVis96 yes, I confirm. ``` michal@dzieni rclone % rclone copy README.md proton:/ --protondrive-app-version "[email protected]" 2024/05/29 10:36:31.621072 WARN RESTY 400 POST https://mail.proton.me/api/drive/blocks: You are using an outdated version of the app....
My real-life use case is a series of integration tests that cover a broad range of API requests (a few dozen). I don't want to think which requests will exactly...