You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The challenge lies in the limited information provided by this error message. The code snippet here reveals that only an error message is logged, without details such as the actual URL or specific error messages. This lack of detailed logging makes it challenging to diagnose and resolve the issue effectively.
Notably, reverting to Node.js version 18.18.2 circumvents this error, indicating a potential compatibility issue with Node.js version 20.
I tried with different logging settings and even tried with github debug logging. I see WIRE it environment variables are set properly.
Your support in resolving this matter is greatly appreciated. Thank you.
The text was updated successfully, but these errors were encountered:
koolshams
changed the title
wireit github actions cache throw error on github enterprise server on nodejs version 20
Error Thrown by Wireit GitHub Actions Cache on Node.js Version 20 running on GitHub Enterprise Server
Nov 28, 2023
Environment
Node: v18.18.2 => v20.9.0
GitHub Enterprise Server 3.8.11
Wireit: 0.14.1
we use github action cache
Upon running tests, we encounter the following error:
The challenge lies in the limited information provided by this error message. The code snippet here reveals that only an error message is logged, without details such as the actual URL or specific error messages. This lack of detailed logging makes it challenging to diagnose and resolve the issue effectively.
Notably, reverting to Node.js version 18.18.2 circumvents this error, indicating a potential compatibility issue with Node.js version 20.
I tried with different logging settings and even tried with github debug logging. I see WIRE it environment variables are set properly.
Your support in resolving this matter is greatly appreciated. Thank you.
The text was updated successfully, but these errors were encountered: