on 02-14-2024 5:41 PM
We have a fairly large application - approx 340 files total (including folders/files). Wehn trying to deploy from VSCode to our Fiori gateway, npm run deploy starts correctly (cleans/builds the /dist folder, creates the archive.zip file, etc.) and starts the upload.
After approximately 60 seconds we get a HTTP 502 Proxy error - I'm assuming because of the timeout and loss of connection between the http host and the fiori backend (we are in a distributed environment i.e. Fiori on separate system and oData services on another system). I can also set a breakpoint in /UI5/ABAP_REPOSITORY_SRV and step through the whole upload - it will process all the files in the project - but I can see where about 60 seconds in VSCode gets the 502 error even though I'm still processing the deployment through debug.
I have no issues deploying any smaller applications (most are under 60 files). I also am able to successfully deploy the large application from WebIDE - just not from VSCode.
Any ideas on handling the timeout issue? I have included my ui5.deploy.yaml file (also note the timeout: value seems to have no impact on anything)
Hi pbstl1,
not sure if this could help: Are you behind a corporate proxy? In my case there was some proxy configuration for npm in the .npmrc file to use avoid npm certificate issues. As far I know VS-Code uses this npm config too.
After delete the config I could deploy my application on system.
I know you have timeout issues but maybe this could help?
Best regards Timo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
6 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.