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 newly implemented V2 API endpoint (/api/v2/issues) is currently returning a 500 Internal Server Error, preventing the successful migration from the legacy endpoint. This issue was discovered during the implementation of updated Hugo shortcodes for the contributor grid system.
🐛 Current Behavior
When accessing the V2 API endpoint, the server responds with a 500 Internal Server Error:
Whitelabel Error Page
This application has no explicit mapping for /error, so you are seeing this as a fallback.
Sat Oct 19 22:25:41 UTC 2024
There was an unexpected error (type=Internal Server Error, status=500).
✅ Expected Behavior
The endpoint should return a JSON response containing the issues data, similar to the current working endpoint (/api/hacktoberfest-issues).
🔍 Issue Summary
The newly implemented V2 API endpoint (
/api/v2/issues
) is currently returning a 500 Internal Server Error, preventing the successful migration from the legacy endpoint. This issue was discovered during the implementation of updated Hugo shortcodes for the contributor grid system.🐛 Current Behavior
When accessing the V2 API endpoint, the server responds with a 500 Internal Server Error:
✅ Expected Behavior
The endpoint should return a JSON response containing the issues data, similar to the current working endpoint (
/api/hacktoberfest-issues
).🔄 Steps to Reproduce
🔍 Technical Details
Endpoint Information
Code vs. Production Mismatch
ApiEndpoint.java
but appears to have deployment or configuration issues📝 Additional Context
/api/hacktoberfest-issues
) continues to function correctly🔧 Possible Investigation Points
ApiEndpoint.java
📎 Related Links
Environment
The text was updated successfully, but these errors were encountered: