-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Failed to send thanks" notification, but thank actually sent successfully #3559
Comments
I've seen this too. |
Can I try to work on this? I was able to reproduce this issue for betaDebug. I observed that we get the same failure notification when the thanks is recorded and when it actually fails (I did this by turning off the WiFi just before sending thanks). |
@6point022 Yes it's yours! Please use "prodDebug" instead. Thanks :-) |
I'll really appreciate some help with this. This is from the
I tried to see what
I could be way off here (I am just learning!!), but I think the reason for failure could be that it is actually returning 0, since the default value of |
@6point022 It's a good thing you shared your doubts here :) I'm not so familiar with the code base but I'll share my views here assuming others will correct me if I'm wrong.
You won't find the code that initializes the value of I think you're in the right track, though. If I were to just go by the example pointed to by the API page, the value of Hope this helps. |
@sivaraam Thanks a lot for the response. ^_^
So, I checked for two cases.
Can you help me understand in what case |
How do you know that the thank succeeded? Did you check the thank log (Special:Log?type=thanks) of the corresponding wiki? I just tried using the API sandbox and could see that the value of
Well, that's what would happen when the app could not connect to the network. But we're actually interested in a different kind of failure here. We have to send a request that reaches the server and the server would respond to us indicating that for some reason the server could not complete the request. It's easier to check that via the API:Sandbox. You can try a thank API request using the following link. Make sure you're logged in before you visit the link. https://commons.wikimedia.org/wiki/Special:ApiSandbox#action=thank&format=json I'm not sure for what cases we would be able to see a different value for
Ideally it should be present in the API documentation. Unfortunately, the API page doesn't help us here as it doesn't have an exhaustive list of values that
It doesn't seem to be returning 0 on success as you could see from the API response above. But if we do get 0 for I'll just note one thing I observed when checking for this. I was checking if the Wikipedia app (which also uses the data client library albeit a different version, I suppose) was correctly receiving the |
Thanks a lot for taking out the time to explain, it's really helpful. 😄
Yes, I checked the thank log and if the thank appeared in it, I considered it a success. If the thank is successful, the value of
Even I am not sure how to proceed from here. Let's see if someone else can help us. :) |
I'd like to try my hand at figuring out what's going on. Edit: Actually, there seem to be a lot of bugs involving the JSON being sent to the API. I just noticed that there are other tickets reporting that number of Thanks is also returning 0. I suspect these are related issues. |
Please feel free, @Daykeras ! |
can i work on this issue |
Yes
…On Thu, Jan 21, 2021, 10:54 AM Prince kushwaha ***@***.***> wrote:
can i work on this issue
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3559 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD6MJD6SUFOLZT5DSGRTB33S3BE3XANCNFSM4LQ2MSEA>
.
|
ok |
…ly sent successfully I create another Model Class->"MwThankPostResponse.java" to store the Result of Post Request POST(MW_API_PREFIX+"action=thank")
Steps to reproduce:
Example:
Even though the thank has actually been sent successfully:
The text was updated successfully, but these errors were encountered: