I'm using GitHub API v3 to connect to a repository and get the list of issues that were update/created since a specific date. I use these parameters to get a filtered result:
filter: all
labels: bug
state: all
sort: updated
direction: ascendent
since: date
If i find any result, for each issue I get the issue events that triggered a change (filtering for the ones that happened since date).
Everything works fine for every issue event except for locked and unlocked
events that, for some reason, don't update the issue updated field.
This leads to the inability to get then the list of issues that were updated since that specific date and therefore I don't check for the issue events.
Questions:
Is there a reason why these two events don't update the issue?
Is there an acceptable solution, except for the one where I should get all the issues and query them manually?
As of today (4th of October, 2015), I cannot reproduce this issue. If it was reproducible when the question was posted, probably it was a bug, not a feature.
Is there a reason why these two events don't update the issue?
They do update the issue (see the updated_at field) and the since parameter works fine.
Is there an acceptable solution, except for the one where I should get all the issues and query them manually?
Just use the since parameter, the way how it is supposed to work, but keep in mind the timezone could be different. Since you're in Romania (like me! :-)) and your server could be into another timezone, you may want to modify the date to match the Romanian time. That's most probably your issue. Just add/substract few hours and see if that helps.
curling the issues, I cannot reproduce the behavior you have.
On the other side, you may want to use the locked parameter which is anyway updated.
Related
I have added a 'number_of_members' value to the Customer DocType via customization.
In my application I have tried several ways to update the value. However the value never updates in the webpage. I feel like I'm missing some sort of save or update or commit step.
For example I have tried:
frappe.client.set_value('Customer', '00042', 'number_of_members', 8887)
frappe.set_value('Customer', '00042', 'number_of_members', 8887)
frappe.db.set_value('Customer', '00042', 'number_of_members', 8887)
and also
customer = frappe.get_doc('Customer', '00042')
customer.number_of_members = 8887
customer.save()
In each case I can do something like frappe.get_value, or frappe.get_doc and it shows the value is set to 8887. However it never updates in the web side. This is what makes me think I'm updating some sort of cache or database transaction and I need some way to save it, but have not had any luck.
I am mostly testing this via bench console if that has any bearing on it, but I've tried a couple of the methods in my application code as well.
Relevant documentation:
Frappe Developer API - Document
Frappe Developer API - Database
Turns out the answer is to call frappe.db.commit() after making changes. If someone can point this out in the documentation so I can better understand how I'm missing stuff, I would appreciate it.
I also noticed if you try to Save something in the UI before you send frappe.db.commit() the UI will hang.
Struggling to find some forum to get help on this.
We've started using chatbase and are struggling to see our data in the dashboard. The API returns 200's with message_ids. Anyone able to point me in the right direction in terms of how to debug this further?
Have followed the docs here: https://chatbase.com/documentation/generic and their 'codelab'. Issues logged on github and tweeted.
Some of our data does show up - specifically the Intents and some of the 'Session flows', but the rest is blank. No messages, no 'active users' ever.
So this was resolved by Chatbase updating their code and by us updating the timestamp to match their docs, i.e.:
"time_stamp: int, milliseconds since the UNIX epoch, used to sequence messages"
The full issue was discussed over on Github: https://github.com/google/chatbase-dotnet/issues/1
We have been using the following library for months:
https://unpkg.com/react#15.3.0/dist/react.min.js
Yes - I know we can just reference 15.3 and get the URL rewrite to the latest, but they released a breaking change. That's another issue for another day. Don't get distracted.
Yesterday this simply stopped working. You'll notice that if you load the URL mentioned, that the file is TRUNCATED. Simply cuts off. This made everything we use react with break. Interestingly, if you go to the following URL (without the .js extension) - things work.
https://unpkg.com/react#15.3.0/dist/react.min
My question is - what the heck happened? Why did the URL we've been using for 8 months suddenly stop working, and who can we get to fix it. In the interim, we had a copy locally that we've started referencing (which we probably should have been doing to begin with, since we don't want the automatic upgrade). When things like this happen, who do you inform?
I'm not sure you'll find the answer as to why this file is no longer working here but based off of the website you could reached out to the creator on twitter: https://twitter.com/mjackson
On the website it says:
SUPPORT
unpkg is a free, best-effort service and cannot provide any uptime or
support guarantees.
i.e. you should probably only use this link if you are messing around with a small project and shouldn't be used for any website where you actually care about the uptime of the site.
I read from the threedubmedia site "The previous version of this plugin allowed this method to be overloaded with arguments to additionally bind handlers for "dragstart" and "dragend" in a single call, but this is no longer supported." but since I haven't actually read every line of the code I was wondering if this has already been accounted for?
Yes I upgraded to v2.2 (Updated: 2012-05-21) and it works fine for me.
I actually had an issue with 'dragend' event getting missed sometimes with v2.0.
I was doing some operations at the end of 'dragend' event (like when user stops resizing column width), but sometimes the operation won't trigger because this event was missed. Actually one had to resize rather quickly and release mouse soon to get the problem in v2.0.
After upgrading to v2.2 those issues are gone.
I am making a simple time sheet for which people can register times
worked on a bug real quickly.
But the hours added to the bugs_activity table are not noticed
anywhere.
here is a simple made up line
Bugzilla::Bug::LogActivityEntry(1, 'work_time', 0, 66, 1, '2010-01-12 14:44:44');
Pretty much, add 66 hours to bug 1, work time. This executes like I would expect but does nothing else. I also need to send e-mails and add comments. I can't find anything on using Bug.pm or LogActivityEntry API.
Is this a huge undertaking or what ?
What I would need is what else is required of me, this is just a batch job that runs when the user presses submit and this info can be on many bugs. I know how to get the bugs, user and such, just not registering the hours, I need the final item. This can be almost as rough as the example above.
I am using Bugzilla 3.4.4
Time worked is kept in longdescs table - the table with comments. Hours worked in fact is a property of a comment. (I also think it's weird.)
bugs_activity table that you're modifying is the table for the history of changes, I bet you can see the result of your call on the "bug activity" page. But it does not change the state of the bug.
Hope this helps.
Igor