Integration tests fail with 303 #74

Open
opened 2023-01-09 18:06:12 +00:00 by dachary · 1 comment

https://woodpecker.gna.org/Hostea/dashboard/pipeline/236/6

It is likely because the Forgejo 1.18 API changed a little when it comes to bootstraping an instance. IIRC there is some webscrapping involved to get the JWT token from woodpecker and the structure changed. A wild guess though.

https://woodpecker.gna.org/Hostea/dashboard/pipeline/236/6 It is likely because the Forgejo 1.18 API changed a little when it comes to bootstraping an instance. IIRC there is some webscrapping involved to get the JWT token from woodpecker and the structure changed. A wild guess though.

Create repository form responds with HTTP 303, probably part of the update from upstream. We are checking for HTTP 302 only, updating to require HTTP 303 will fix this issue.

image

Create repository form responds with HTTP 303, probably part of the update from upstream. We are checking for [HTTP 302 only](https://forgejo.gna.org/Hostea/dashboard/src/commit/eaff09efd42bfb70794e8457588e621a00a20df2/integration/forgejo.py#L199), updating to require HTTP 303 will fix this issue. ![image](/attachments/f3ea8926-c969-4f33-9437-b5be8bd0d389)
realaravinth self-assigned this 2023-01-14 06:40:06 +00:00
realaravinth started working 2023-01-14 06:40:06 +00:00
realaravinth cancelled time tracking 2023-01-14 07:33:29 +00:00
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Hostea/dashboard#74
There is no content yet.