GitLab backend doesn't support long issue descriptions #41
Comments
plajjan
added
bug
This was referenced Apr 3, 2018
plajjan
added a commit
to plajjan/org-sync
that referenced
this issue
Dec 4, 2018
We used to send the issue data like title and description in the URI but there's a limit to the length of data we can send. By instead sending the data JSON encoded in the body we get around this! I introduced a second function for POST/PUTing JSON data that sets the correct Content-Type. This can probably be written in a more elegant manner but this works for now :) Fixes arbox#41.
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This isn't really about org-sync's gitlab backend but rather about GitLab itself, however, I'm opening an issue here since it's nice to track it in case someone else runs into it and I just need externalize things from my memory.
I have an issue with a pretty long description and it fails when trying to sync. Just manually trying to PUT the issue using curl fails and I get back
414 Request-URI Too Largefrom the gitlab server.The problem is that the GitLab issue API accepts the title and description encoded in the URL and if it gets to big it just doesn't work. GitLab's own web UI uses a different URL to PUT updates to the backend. It doesn't appear to be immediately usable though, I suspect we can't use token authentication. I have quite a distaste for projects that offer different interfaces to different clients - like here the native web UI gets one path whereas other external integrations are supposed to use a separate API. Quite poor form.
The solution is quite clear, just allow description in the body instead. There's a issue for GitLab here: https://gitlab.com/gitlab-org/gitlab-ce/issues/43490
When that happens we have to update our gitlab backend.
The text was updated successfully, but these errors were encountered: