#nukesforbreakfast_docs
tender adderBOT
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- rc_account-country, 1 day ago, 8 messages
- nukesforbreakfast_docs, 5 days ago, 51 messages
thorny capeBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1237477271997120542
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
opal remnant
Here's a screenshot:
there's weird spacing and black bars that weren't there yesterday.
analog sun
hmm works fine for me. Can you try using a different browser?
opal remnant
yeah, it works in Chrome. But it fails in Firefox 125.0.3 (64-bit)
analog sun
Odd. Are you seeing any network errors in the console?
opal remnant
let me check
I restarted it with all add ons disabled and the same thing happens
I see some errors in the console:
Uncaught (in promise) TypeError: NetworkError when attempting to fetch resource.
Uncaught (in promise) DOMException: IDBDatabase.transaction: 'docs-keyval-store' is not a known object store name
_withIDBStore idb-keyval.mjs:16
_withIDBStore idb-keyval.mjs:15
promise callback*_withIDBStore idb-keyval.mjs:15
a idb-keyval.mjs:31
l loadItem.ts:20
o usePersistentState.ts:42
kc React
unstable_runWithPriority scheduler.production.min.js:18
React 4
unstable_runWithPriority scheduler.production.min.js:18
React 6
2080 client.tsx:57
2080 client.tsx:65
Webpack 4
common.adc7003a0997cf166793.js:75
Content-Security-Policy: The page’s settings blocked a JavaScript eval (script-src) from being executed because it violates the following directive: “script-src 'self' https://.demandbase.com https://.google.com https://.marketo.com https://.zoominfo.com https://connect.facebook.net https://js.zi-scripts.com https://munchkin.marketo.net https://ssl.google-analytics.com https://static.ads-twitter.com https://tags.clickagy.com https://www.google-analytics.com https://www.googleadservices.com https://www.googletagmanager.com https://www.redditstatic.com/ads/pixel.js 'sha256-xkhGWyWav2HccuE2V7MFZhTc/aonl5j0Vw/z6wM1YB4=' 'sha256-7wNSE3PP9mVwS3YyLuJfRgYWV7z2BOlrVwLqZ5xmClo='” (Missing 'unsafe-eval') 4 gtm.js:5:28
analog sun
Ah I can reproduce this on my laptop with firefox. Let me flag this internally
analog sun
that's okay. We've flagged our docs team about this.
opal remnant
ok great, thanks!
analog sun
They're taking a look
opal remnant
@analog sun can I ask a different question?
I'm seeing unexpected behavior with the https://docs.stripe.com/api/accounts/delete endpoint in a test env. It is giving me a 403 forbidden instead of a 404 when I attempt to delete a stripe account that doesn't exist/has already been deleted.
analog sun
Can you share the request ID?
https://support.stripe.com/questions/finding-the-id-for-an-api-request
opal remnant
hmm, it's not appearing in the logs. Probably rejected before being tried. Let me see if there's a response header that contains one.
nevermind I wasn't in the sandbox
req_EEawQ4VDDxf5lp
no, that's the wrong request, one second
hmm, it's not showing up in the dashboard logs, and the response headers don't contain the request ID
so I can't give you one
analog sun
Hmm I haven't been able to reproduce this unfortunately.
opal remnant
if you create a connected account, then delete it, and then try to delete it again, it gives you a 404 instead of a 403?
-> raise err
(Pdb) err
PermissionError(message="The provided key 'sk_test_*********************************************************************************************1Iz7qc' does not have access to account 'acct_1PDtj5PbWiDig0fg' (or that account does not exist). Application access may have been revoked.", http_status=403, request_id=None)
*** AttributeError: 'PermissionError' object has no attribute 'reqiest'
(Pdb) err.request_id
(Pdb) err.json_body
OrderedDict([('error', OrderedDict([('code', 'account_invalid'), ('doc_url', 'https://stripe.com/docs/error-codes/account-invalid'), ('message', "The provided key 'sk_test_*********************************************************************************************1Iz7qc' does not have access to account 'acct_1PDtj5PbWiDig0fg' (or that account does not exist). Application access may have been revoked."), ('type', 'invalid_request_error')]))])
(Pdb) err.http_status
403
Ah I think that's expected here. I think I was testing it differently.
opal remnant
oh, so a 403 is expected?
analog sun
Yeah for this specific request type, the account ID is valid (even though deleted).
opal remnant
alright, that makes it a bit harder to distinguish between unrecoverable errors (like our API key got borked somehow) versus recoverable ones like "this account is already deleted, so we can continue."
analog sun
You could use the error code to distinguish no?