------------------------------------------------------------------------------
To reply, visit https://hellosplat.com/s/beanbag/tickets/4705/
------------------------------------------------------------------------------

New ticket #4705 by hr3pswtk
For Beanbag, Inc. > Review Board

Status: New
Tags: Priority:Medium, Type:Defect

File attachments:

 * reviewboard-http410-gitlab.txt
   <https://hellosplat.com/s/beanbag/attachments/1310/>



------------------------------------------------------------------------------
"HTTP Error 410: Gone" for Gitlab projects
==============================================================================

# What version are you running?

2.5.17

# What's the URL of the page containing the problem?

https://projects/admin/db/scmtools/repository/add/   (new Gitlab project)

https://projects.dx-erkrath.de:8081/r/new/   (existing Gitlab project)

# What steps will reproduce the problem?
1. create repository with Gitlab private-token
2. OR add a new review request on existing repository with same Gitlab 
private-token
3. 


# What is the expected output? What do you see instead?

1. sucessfully add a new repository
2. successfully add a new review reqest to existing repository

both not possible right now

# What operating system are you using? What browser?

Chromium

# Please provide any additional information below.

The existing repository (#2) was working weeks ago with the very same 
private-token. It has no expire date set.

I have tried with a newly created private-token, which gives another error: 
unable to decode base64. Are the hashes produced by Gitlab different now?

When using the existing repository (#1) a trace is written to reviewboard.log, 
see attachment. Also a decoding problem, I dont see if its the private-token or 
something else.

------------------------------------------------------------------------------

-- 
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.

Reply via email to