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
What is the bug?
When using the HTTP hubble API to submit a message via the /v1/submitMessage endpoint the request never responds / times out. The message itself is accepted and shows up when requesting the user's casts via the /v1/castsByFid endpoint.
Maybe some relevant context?
My app is getting permission to post on the user's behalf by creating a signature and adding it to the KeyRegistry by interacting directly with the contracts (not going through warpcast api).
I've reproduced this against my own hub (v1.14.2) as well as nemes.farcaster.xyz both inside my app and outside it by constructing the request in Postman.
Example code
exportconstsendCast=async(options: {text: stringsigner: NobleEd25519Signerfid: numberparentUrl?: stringreplyToHash?: string})=>{const{ text, replyToHash, parentUrl, signer, fid }=optionsconstmsg=awaitmakeCastAdd({
parentUrl,parentCastId: replyToHash
? CastId.create({hash: replyToHash})
: undefined,
text,embeds: [],embedsDeprecated: [],mentions: [],mentionsPositions: []},{
fid,network: FarcasterNetwork.MAINNET},signer)constmessageBytes=Buffer.from(Message.encode(msg._unsafeUnwrap()).finish())// This times out but the message is addedawaitaxios.post(`${Config.HUB_URL}/v1/submitMessage`,messageBytes,{headers: {'Content-Type': 'application/octet-stream'},timeout: 10000})}
The text was updated successfully, but these errors were encountered:
Observed the same with my own hub. Could be a coincidence but I noticed that it generally occurs when Merkle Trie Queue Size shows higher values in the grafana dashboard.
It sounds like you're encountering a timeout issue when submitting a message through the Hubble API, even though the message is successfully created and retrievable. You can try out this few steps to troubleshoot and potentially resolve the issue:
Check API Documentation: Ensure that you are adhering to the expected request format and parameters for the /v1/submitMessage endpoint. Look for any specific requirements that might cause the request to hang.
Inspect Network Traffic: Use a tool like Postman or browser dev tools to inspect the network traffic. Check for:
Request headers and body to ensure they're formatted correctly.
Any error responses or logs from the server.
What is the bug?
When using the HTTP hubble API to submit a message via the
/v1/submitMessage
endpoint the request never responds / times out. The message itself is accepted and shows up when requesting the user's casts via the/v1/castsByFid
endpoint.Maybe some relevant context?
My app is getting permission to post on the user's behalf by creating a signature and adding it to the KeyRegistry by interacting directly with the contracts (not going through warpcast api).
I've reproduced this against my own hub (v1.14.2) as well as
nemes.farcaster.xyz
both inside my app and outside it by constructing the request in Postman.Example code
The text was updated successfully, but these errors were encountered: