I don't want this to happen, and nowhere I can find in the documentation says that this should happen. Any ideas on how to prevent this?
(This is the v6 REST API)
Related
at my company we want to make use of the relatively new API feature "Automerge" (not through a UI but through an API call),
However we can't seem to find any documentation of a webhook (or other asyc way) of finding out if a merge request failed and why,
anyone know a way to receive such a notification?
Thanks! :)
Hope this saves some work for someone out there,
we asked Github.com support directly and they said there was no async / webhooky way of doing this (as of Nov 2021).
Here's a quote from the support person when asked if there were a way to find out, here's what they wrote:
There wouldn't be a great way to discern that (reason for failure) and
it may be better when you see that, to use the REST API to Get the
Pull Request to get some additional information.
looking at the documentation as suggested in the quote above it seems that through the "closed" action and "merged" key one could discern whether a merge was successful or not, but without any further information about the failure.
After some time working out why our gscript plugin didn't work with error "We're sorry, a server error occurred while reading from storage. Error code PERMISSION_DENIED" we discovered that "../auth/script.storage" was listed in our consent screen.
We assume here that this scope is perhaps a new scope that didn't previously exist that are app now requires. We discount the possibility that we accidentally added the scope ourselves, forcing the app to fail when in fact it does not require this scope.
https://i.stack.imgur.com/DUjY1.png
The attached image is a screenshot of our listed authentication scopes. The green tick, when hovered over says "This API scope is approved and no longer restricted for use."
As you can see, the scope we want does not have the desired green tick.
We then asked for verification, on the assumption that the scopes in the list would be scopes that could be verified on submission.
It is difficult to speculate what other purpose having scopes in the list would serve.
However, our submission came back successful and our green tick for the desired scope was not granted. Our plugin still fails with the same error.
How might we proceed with the submission request and have the auth scope we need be granted to us?
Some more stuff we don't know:
We don't know why email, profile and openid are in the list, why they appear twice and why the 2nd set are removalable and the first set aren't.
After reading some documentation, I figured out that the re-captcha risk-analysis of invisible re-captcha V2 and V3 is triggered just after that the user clicks on submit buttons. Then, according to the output of the risk-analysis system, is asked a challenge (or not) to be solved by the user. Once that the challenge has been solved, the re-captcha token populates the innerHTML of "g.recaptcha.response".
Does it work in this way right? Is it not possible knowing if the captcha-challenge is going to be triggered (or not) before of the event that activates the risk-analysis system of captcha?
I mean, are there parameters of the DOM that tell you if the captcha-challenge is going to be asked?
I'm trying to use webhooks to get notifications for changes in a user's Box account. One thing I don't see is an option to get a webhook notification when an item is renamed. Is it possible to get a notification for rename? I see that RENAME is available via the event API, is it preferable to use the event API? I saw another stackoverflow question asking about webhook vs event (Box webhooks deprecated in favor of long polling?) and the answer said webhooks are still valid, but didn't really comment on webhook vs event.
I'd prefer webhooks since they are a close fit to how I get changes for Dropbox accounts but it appears from the docs that event has more information/options. Also, it seems it's possible to miss a Box webhook notification which could create an inconsistent state between Box the model in my application.
Which to choose?
Many thanks!
I don't believe it's possible to get a WebHook notification when an item is renamed.
The choice between WebHooks and events really depends on what you're building. WebHooks are generally easier to use, but the events stream can give you more power. In your case, you'll probably need to use events so you can be notified of a renames.
It's also worth noting that if your application really depends on staying in sync with the state of Box, you're better off using the events stream. It lets you specify a last known position in the stream so that you can catch up on any missed events if your application goes offline.
We are interested in getting the enterprise events from Box API which are documented here. I see that there are enterprise events for items being shared and unshared. These are SHARE and UNSHARE. However there are no events when permission(access level) are changed for shared links. So e.g if someone changes the access level from OPEN to YOUR_COMPANY or vice-versa, the Box API does not send any event..Our use-case is such that we would like to known when the access level changed. How can this be achieved?
Do we need to submit a feature request to Box? If so, what is the process? Also, what can be the timelines for any new revisions in which this feature can be added?
Good catch. Consider you feature request submitted.