One-line summary
POST /v1/datapackets for MSFT timed out on three attempts using two API keys; no HTTP status or response body was received.
Steps to reproduce
- Use thesis-cli at commit b815ff6 with Node v24.15.0 on macOS (Apple Silicon).
- Configure an API key generated at thesis-investing.com.
- Call the existing fetchDataPacket("MSFT", config) function through a standalone test script, sending POST https://api.thesis-investing.com/v1/datapackets with JSON body {"ticker":"MSFT"}.
- Use a fetch wrapper with redirects blocked, no retries, and a 30-second timeout.
- Observe a timeout without an HTTP status or response body.
Three attempts were made: one with a 20-second timeout and two with 30-second timeouts. The final attempt used a newly generated key. The last two attempts had the execution tool’s network restriction lifted for that command only.
The full /analyze workflow was not invoked. This checkout has local storage-path changes and report uploads disabled, but src/api/thesisDataApi.js was unchanged.
Authentication remains indeterminate. Is this endpoint operational, and does DataPacket access require billing activation or a different API address?
Expected behavior
Receive an HTTP response containing either a valid MSFT DataPacket or a clear error explaining any authentication, billing, rate-limit, or service-availability requirement.
Actual behavior
All three requests timed out without an HTTP status or response body: the first after 20 seconds, the next two after 30 seconds. Two different API keys were used. No retries or redirects were followed.
Authentication and DataPacket validation remain unverified. The cause is unknown; no server error or stack trace was received.
Thesis commit SHA
b815ff6
Operating system
macOS
Node.js version
v24.15.0
One-line summary
POST /v1/datapackets for MSFT timed out on three attempts using two API keys; no HTTP status or response body was received.
Steps to reproduce
Three attempts were made: one with a 20-second timeout and two with 30-second timeouts. The final attempt used a newly generated key. The last two attempts had the execution tool’s network restriction lifted for that command only.
The full /analyze workflow was not invoked. This checkout has local storage-path changes and report uploads disabled, but src/api/thesisDataApi.js was unchanged.
Authentication remains indeterminate. Is this endpoint operational, and does DataPacket access require billing activation or a different API address?
Expected behavior
Receive an HTTP response containing either a valid MSFT DataPacket or a clear error explaining any authentication, billing, rate-limit, or service-availability requirement.
Actual behavior
All three requests timed out without an HTTP status or response body: the first after 20 seconds, the next two after 30 seconds. Two different API keys were used. No retries or redirects were followed.
Authentication and DataPacket validation remain unverified. The cause is unknown; no server error or stack trace was received.
Thesis commit SHA
b815ff6
Operating system
macOS
Node.js version
v24.15.0