softworkz
softworkz
Hi, what you are encountering here is in fact a tiny ugliness, essentially the price that had to be paid for some of the major benefits over earlier Electron.NET. Here's...
> ; I had to explicitly specify the target framework in the publish command for it to build properly: `dotnet publish -p:PublishProfile=osx-arm64 -r osx-arm64` That's a bit unfortunate, yea. I'm...
> For me this is fine - I'd like to have @softworkz opinion especially regarding potential cleanups / memory leaks on this one. Please give me a little bit more...
> > Looks like the tests are flaky 😕 > > Some of the npm downloads did not go well (npm responded with a 503). This can (and realistically, unfortunately,...
> If it would be rate limiting then 503 is the wrong status code. Holding the connection and timing out after some time is a well-known technique for defeating attacks...
But of course I'm not sure either wether the delay will be of any help...
I have read somewhere that they have proxies for the DevOps runners to avoid downloading the same things a thousand times, and "gateway timeout" is a typical proxy error -...
Well - just one bullet is closed :-)
Good idea - added to the OP
#### Note Thinking about it: using npm for web/client related packages must still be possible, so that part needs consideration.