-
Notifications
You must be signed in to change notification settings - Fork 42
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
EDU:1615 Error handling #2382
base: main
Are you sure you want to change the base?
EDU:1615 Error handling #2382
Conversation
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
9d80a82
to
c042913
Compare
c042913
to
65cc759
Compare
a892b4f
to
5f8fe53
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to be missing a significant number of errors in addition to the notes on the error codes page.
content/push/index.textile
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we drop this out of the PR please? 🙂
@@ -0,0 +1,301 @@ | |||
--- | |||
title: Error handling |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be 'Error codes'.
What are your thoughts about the folder being errors
and this file being codes
. We can still label this differently in the nav, but it keeps the URL concise.
@@ -0,0 +1,301 @@ | |||
--- | |||
title: Error handling | |||
meta_description: " " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need a description here.
|
||
h2(#errors). Invalid input/request errors | ||
|
||
h3(40000). 40000 - Bad request |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing your #
If the provided information does not resolve your issue, contact Ably "support":https://ably.com/support. When contacting, include details such as your app ID, the error code, and any relevant logs to help troubleshoot. Include as much of the following information as possible: | ||
* Provide timestamps in UTC format. | ||
* Include complete SDK logs from the time of the failure. Ensure these logs show activity before and after the timeout, as SDKs retry failed requests by default. | ||
* Specify which endpoints were accessed. Mention if you use custom client options, the environment setting, and the failing SDK operation. | ||
* State the SDK/s you use, including the platform and versions. | ||
* Include any stack traces related to the error. | ||
* Indicate whether the issue occurs consistently or was a one-time event. | ||
* Provide details to confirm whether the issue was related to your network or Ably's availability. For example, note whether other internet operations were succeeding simultaneously. | ||
* Include the app ID associated with the request. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this would be better off on the main errors page, rather than here. WDYT?
|
||
*Resolution:* If you need to change your client's @clientId@, deactivate and reactivate the device. This process triggers an internal @device.reset()@ call, which clears and resets the old device details. | ||
|
||
h2(#spaces). Spaces and locking errors |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
h2(#spaces). Spaces and locking errors | |
h2(#spaces). Spaces errors |
|
||
*Resolution:* Specify the name parameter when calling the @spaces.get()@ method: | ||
|
||
```[realtime_javascript] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The above is only js, this is realtime_js
|
||
*Resolution:* Call the @space.enter()@ method before using any features. For example: | ||
|
||
```[realtime_javascript] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As above - these should be consistent throughout
|
||
h3(#40022). 40022 - Invalid resource | ||
|
||
The requested resource is invalid or already exists. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should mention that it's returned by the Control API
|
||
An example of this error is attempting to create an app named "MyApp" when an app with that name already exists or attempting to create a user account with an email address that is already registered. | ||
|
||
*Resolution:* Ensure unique app's name has valid capabilities in requests. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This only covers 1 instance of the error occurring.
4f03213
to
8abdcf8
Compare
This PR:
Question
Question
The padding below the bullet points throws the general look of the document off IMO.