You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/development/sidekiq/compatibility_across_updates.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -226,7 +226,7 @@ We should treat this similar to adding a new worker. That means we only start sc
226
226
To ensure backward and forward compatibility between consecutive versions
227
227
of the application, follow these steps over three minor releases:
228
228
229
-
1. Create the newly named worker, and have the old worker call the new worker's `#perform` method. Inroduce a feature flag to control when we start scheduling the new worker. (Release M)
229
+
1. Create the newly named worker, and have the old worker call the new worker's `#perform` method. Introduce a feature flag to control when we start scheduling the new worker. (Release M)
230
230
231
231
Any old worker jobs that are still in the queue will delegate to the new worker. When this version is deployed, it is no longer relevant which version of the job is scheduled or which Sidekiq handles it, an old-Sidekiq will use the old worker's full implementation, a new-Sidekiq will delegate to the new worker.
Copy file name to clipboardExpand all lines: doc/user/workspace/configuration.md
+1
Original file line number
Diff line number
Diff line change
@@ -173,6 +173,7 @@ When creating a workspace in a project, one of the following errors might occur:
173
173
-`You can't create a workspace for this project` when you attempt to create the workspace from **Workspaces** on the left sidebar.
174
174
-`To set up this feature, contact your administrator.` when you attempt to create the workspace in a specific project using the `Edit` function.
175
175
- An expected agent is not be present in the list of available agents.
176
+
176
177
Possible reasons for this error are:
177
178
178
179
- The user does not have at least Developer role for the workspace project and/or the agent project. To resolve this issue, ask the respective group or project owner to grant you access.
0 commit comments