Maybe we can still work async as we did last weekend when you asked me to test v.0.0. However you have my GitHub handler and I’m actively following this space, so feel free to DM me here or in GitHub. I noticed your message was 4h ago, so I guess we’re not in the same timezone (here in Chicago is almost 8AM). I hope others in this thread would be also able to contribute, so we could divide and conquer a solution that otherwise may take a huge effort for you alone. I’m not much familiar with TypeScript, so trying to help with my coding may not be the most efficient contribution, but I could certainly help you to debug and test the code if you need a hand and a second pair of eyes! Wow, very much appreciated I was thinking that this workaround would need to stay until the library you were using before gets updated to fix the problems with v.1.82.2, but I really appreciate you spend your personal time to re-write the class to use the TypeScript SDK. GitHub Isuue on Visual Studio Code editor. GitLab and Visual Studio Code integration. Set github personal access token in visual studio code. VSCode prompts for username and password. Thanks in advance for your work fixing this. Unfortunately, now we cant commit our work in visual studio code. Let me know if you need a guinea pig for testing, I’ll be more than happy to help. VSCode & IDN extension installed versions: Version: 1.82.2 (system setup)Ĭommit: abd2f3db4bdb28f9e95536dfa84d8479f1eb312d I confirmed my tokens are still working via Postman, so I’ll switch to the old way of doing things hoping that your plugin gets a patch to resolve this, as it has been VERY useful to manage our environment. I removed my tenant and tried to add it back, but it keeps failing. This is preventing both PAT and Access Token authentications. haven’t yet experienced problems with their environment. This started happening right after I updated my VSCode version (the extension was working fine to me until then), so maybe that explains why some users (e.g. I checked in the DevTools and the error I found is: notificationsAlerts.ts:40 TypeError: fetch failedĪt Object.fetch (node:internal/deps/undici/undici:11413:11)Īt async q.getResource (\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:107:12650) Hi I’m having the same “fetch failed” error that reported 2 days ago. I’m getting a gateway timeout when trying to import a config object, I’m unable to do any source aggregations or identity profile refreshes, and I also have a client that is getting “fetch failed” errors when trying to use the extension when things were working fine last week with no changes on our end. Adam are there issues going on with the extension?
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |