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.

Sign up for GitHub

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

Jump to bottom

Fix for OUJS collaboration failure #404

Merged
merged 1 commit into from
Nov 4, 2014
Merged

Fix for OUJS collaboration failure #404

merged 1 commit into from
Nov 4, 2014

Conversation

Martii
Copy link
Member

@Martii Martii commented Nov 4, 2014

  • Currently pro returns a 502 and dev returns the error when trying to submit a change to an OUJS collaboration... this should fix that... works on dev.

Refs:

Fix for OUJS collaboration failure
bd0139a 
* Currently pro returns a 502 and dev returns the error when trying to submit a change to an OUJS collaboration... this *should* fix that... works on dev.

Refs:
* OpenUserJS#273
* OpenUserJS#264
Martii added a commit that referenced this pull request Nov 4, 2014
@Martii
Merge pull request #404 from Martii/fixCollaboration
e4ea956 
Fix for OUJS collaboration failure

Auto-merge
@Martii Martii merged commit e4ea956 into OpenUserJS:master Nov 4, 2014
@Martii Martii deleted the fixCollaboration branch November 4, 2014 01:32
@Martii Martii added this to the #262 milestone Nov 4, 2014
@Martii Martii added bug You've guessed it... this means a bug is reported. migration Use this to indicate that it may apply to an existing or announced migration. CODE Some other Code related issue and it should clearly describe what it is affecting in a comment. labels Nov 4, 2014
@Martii
Copy link
Member Author

Martii commented Nov 4, 2014

Confirmed working with collaborative edited script here. Really unusual that a identifier not defined on dev would generate a 502 on pro.

@snyk-bot snyk-bot mentioned this pull request Sep 23, 2020
Open
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
bug You've guessed it... this means a bug is reported. CODE Some other Code related issue and it should clearly describe what it is affecting in a comment. migration Use this to indicate that it may apply to an existing or announced migration.
Milestone
#262
Development

Successfully merging this pull request may close these issues.
1 participant
@Martii