Skip to content
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

Error: /api/sync returned disallowed changes -- declining an invitation #4743

Closed
sentry-io bot opened this issue Sep 19, 2024 · 0 comments · Fixed by #4750
Closed

Error: /api/sync returned disallowed changes -- declining an invitation #4743

sentry-io bot opened this issue Sep 19, 2024 · 0 comments · Fixed by #4750
Assignees
Labels
bug DEV: frontend P0 - critical Priority: Release blocker or regression

Comments

@sentry-io
Copy link

sentry-io bot commented Sep 19, 2024

Observed behavior

Seems declining a channel invitation results in the change being disallowed. I do not believe this is a regression. See the attachment in the Sentry issue for the change objects. Here's a preview:

[

{
"channel_id": "a28114cfd97a4def9b0910334ec3fcff",
"key": "4d6f8f3aeef045408e19a1a4114dbfa9",

"mods": {
"declined": true
},
"rev": 199,
"table": "invitation",
"type": 2,
"user_id": 29689
}
]

Sentry Issue: STUDIO-HC3

Error: /api/sync returned disallowed changes
  at handleDisallowed (./shared/data/serverSync.js:66:19)
  at <anonymous> (./shared/data/serverSync.js:291:9)

Expected behavior

Declining an invitation does not result in a 'disallowed change'

@akolson akolson added this to the Studio: Bulk Editing Release milestone Sep 23, 2024
@akolson akolson self-assigned this Sep 23, 2024
@akolson akolson added bug P0 - critical Priority: Release blocker or regression DEV: frontend labels Sep 23, 2024
@akolson akolson mentioned this issue Sep 23, 2024
24 tasks
This was referenced Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug DEV: frontend P0 - critical Priority: Release blocker or regression
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant