I was trying to change the state of the driver to accept a ride and it keeps on giving me a 500 internal server error saying that it was a ride dispatch timeout.
I did change the state from offline - online and it's working fine.
Any work arounds on this one ?
This is on sandbox mode.
It's just me, I chose the wrong ID that produces this error. It's all working now.
Related
I had made a whole chat application using signalr as a socket with the online and offline facility. I am facing a few problems,
Signalr connection is always time out after some time, to overcome that I had condition if hubconnection is not connected then create new hubconnection (onResume app), but still it get hubconnection._callback got increased when sending message and not moving to server side socket. Again need to refresh whole app.
Can someone tell me whether this is problem because there are lot of operations going on and so signalr loses its connection as flutter is single thread and it cannot handle much? or should I use Isolate or inherit widget.
Summary problem:
I cannot send message in chat after sometime. It stores all message in hubconnection._callback and not going for server.
Is anything better solution to keep alive in both Android+iOS.
I had used https://pub.dev/packages/signalr_netcore package.
Please do not mention about firebase.
Any other logic suggestion is appreciable.
Thank you.
I've been using a different package, https://pub.dev/packages/signalr_core, which works fine without any particular issues what I have observed at the moment.
I'm only running about 10 listeners simultaneously, not sure if that is more or less than you. In the package I'm running you can establish connection with automatic reconnect. It looks like this:
HubConnectionBuilder().withAutomaticReconnect().withUrl(....)
It seems like your package have the same functionality... Have you tried that?
I had previously been using the SendAsync method to call my SignalR Core hub with no problems. I realized that if there is an error on the server that I will never know about it from the client with SendAsync, so I decided to use InvokeAsync with the exact same arguments. When InvokeAsync is called, I can tell that my hub is called and it processes correctly, but the call on the client side ("await InvokeAsync") freezes. It just locks up and never makes it to the next line of code. This is a WPF application. What could be going on? await SendAsync returns immediately and has never locked up in this way.
I found the issue. It turned out it was because the message being sent from the WPF app was also being received by the WPF app, which caused a blocking issue when I tried to update the UI upon receiving a message. I updated my receive code to use Dispatcher.BeginInvoke, instead of Dispatcher.Invoke, and now it works. This was not an issue when I was calling SendAsync from the SignalR client.
Im trying to do my first xmpp client with webrtc videochat using strophe with. strophe.jingle
There is very little documentation for it, so ive ended up pillaging example code to try and get it working.
I am successfully sending the videochat invite over to the other user via XMPP and the app is trying to setup the chat.
However its giving me errors about ICE Candidates like this (it throws 6-8):
addIceCandidate failed SyntaxError: Failed to execute 'addIceCandidate'
on 'RTCPeerConnection': The ICE candidate could not be added.
a=candidate 2565634929 1 udp 41819903 66.228.45.110 64264 typ relay
raddr 79.260.27.217 rport 58182 generation 0
Ive done enough searching to realize that i need to set ice server urls or something.
But i am at a loss as to how.
Ive tried:
var ice_config = {iceServers: [{url: 'stun:stun.l.google.com:19302'}]};
connection.jingle.ice_config = ice_config;
I am sending the invite like this
connection.send($pres({to:peer}));
connection.jingle.initiate(peer, connection.jid);
At this point i feel like its all over my head and its really hard to read up on it without any real documentation.
If anyone can throw me a bone, id be really really happy.
try removing the 'a=' from the line returned by
https://github.com/ESTOS/strophe.jingle/blob/master/strophe.jingle.session.js#L542
chrome changed the syntax of this at some point and seems to no longer accept the old syntax.
Update: turned out to be a bug. Check the updated version on github and file an issue there if it is still not working.
I'm not really sure what's going on, but today I've noticed that the facebook api is working extremely slow for me.
At first I though it was a bug in my code, but I tried the Graph API Explorer, and even that's causing timeout errors half the time (just using /me):
Failed to load resource: the server responded with a status of 504 (Server timeout)
I don't think its my internet connection, since everything else seems to be working quickly, and http://speedtest.net is giving me good results.
Is my problem somehow fixable or is this just some sort of freak occurance?
Has this happened for anyone else?
Do I need to consider the case that it will take exceedingly long in my application to recieve a response?
I currently have a registration page that waits for a FB.api response (with a spinner gif) before displaying the form. I could use a timeout to wait a few seconds and show it if the api doesn't respond, but I'd really rather not have to use this same sort of logic in every api call that my application depends on...
EDIT: its spontaneously fixed itself now. still no clue what happened.
You can check facebook api live status with this URL
https://developers.facebook.com/live_status
today at 11:13pm: API issues We're currently experiencing a problem
that may result in high API latency and timeouts. We are working on a
fix now.
I have a small GWT application that gets the contents for a FlexTable from a database based on some string parameters. It is triggered by the click of a button on the GUI.
Everything works as expected when the app is initially started. But, upon multiple clicks (requests), the app stops working and my requests from the client no longer reaches the sever code. I am running on hosted mode and have breakpoints in my code. I can trace the code on client side; but after it submits the request to server using my service instance, it never reaches the server; nor the onSuccess() gets called.
Can someone please help me debug this? Where should i start to see traces of what is happening?
Turns out that it wasnt anything about GWT RPC. The request was indeed getting submitted to server but because of a db resource contention, Eclipse wasn't showing me any trace of the code on server side. I switched on debug loggings in the code and everything because real clear.
Thanks!
pjames