atlassian / atlassian/nucleus

downloading released package gives 102 error

Open
#111 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
420
Forks
100
PR merge metrics
No merged PRs in 30d

Description

Im running nucleus server through docker on a Linux Debian.

I created a 'Stable' channel:
![image](https://user-images.githubusercontent.com/74248109/98681545-2423ea00-2363-11eb-8f4f-18fb6dde2676.png)

When I click on the released package (5.0.0) I receive a 102 error in the browser: ERR_CONNECTION_REFUSED.
URL of the released package:
`http://localhost:9999/Pencil/123403167abc0aeb56a4cc1a1e17e222/_index/5.0.0/win32/x64/5.0.0.exe`
I run the nucleus with `DEBUG=nucleus*`. The logs in docker doesnt show any error message.

I receive no error when I download the draft package (1.0.0.exe).

tree .files:
```
.files
|-- Pencil
| |-- 123403167abc0aeb56a4cc1a1e17e222
| | |-- _index
| | | |-- 0.0.4
| | | | -- win32
| | | | -- x64
| | | | -- 0.0.4.exe
| | | |-- 4.0.0
| | | | -- win32
| | | | -- x64
| | | | -- pencil\ Setup\ 4.0.0.exe
| | | -- 5.0.0
| | | -- win32
| | | -- x64
| | | -- 5.0.0.exe
| | |-- darwin
| | | -- x64
| | | |-- 0
| | | | -- RELEASES.json
| | | |-- 1
| | | | -- RELEASES.json
...
| | | |-- 98
| | | | -- RELEASES.json
| | | |-- 99
| | | | -- RELEASES.json
| | | -- RELEASES.json
| | |-- latest
| | | -- win32
| | | -- x64
| | | |-- Pencil.exe
| | | -- Pencil.exe.ref
| | |-- linux
| | | |-- Pencil.repo
| | | |-- debian
| | | | -- binary
| | | | |-- Packages
| | | | |-- Packages.gz
| | | | |-- Release
| | | | |-- Release.gpg
| | | | |-- Sources
| | | | -- Sources.gz
| | | -- redhat
| | | -- repodata
| | | |-- 401dc19bda88c82c403423fb835844d64345f7e95f5b9835888189c03834cc93-filelists.xml.gz
| | | |-- 6bf9672d0862e8ef8b8ff05a2fd0208a922b1f5978e6589d87944c88259cb670-other.xml.gz
| | | |-- dabe2ce5481d23de1f4f52bdcfee0f9af98316c9e0de2ce8123adeefa0dd08b9-primary.xml.gz
| | | -- repomd.xml
| | |-- versions.json
| | -- win32
| | |-- ia32
| | | |-- 0
...
| | | |-- 99
| | | | -- RELEASES
| | | -- RELEASES
| | -- x64
| | |-- 0
| | | -- RELEASES
| | |-- 0.0.4.exe
| | |-- 1
| | | -- RELEASES
| | |-- 10
| | | -- RELEASES
...
| | |-- 49
| | | -- RELEASES
| | |-- 5
| | | -- RELEASES
| | |-- 5.0.0.exe
| | |-- 50
| | | -- RELEASES
...
| | |-- 99
| | | -- RELEASES
| | |-- RELEASES
| | -- pencil\ Setup\ 4.0.0.exe
| |-- icon.ico
| |-- icon.png
| -- temp
| -- e9378c9e5b5af6d30634a7bb476a2357
| -- 1.0.0.exe
-- public.key
```

Contributor guide

No contributing guide indexed for this repository

Research direction

No source file, test, or entry point is named. Start by reproducing the released-package URL in the Docker/Linux Debian setup and compare it with the working draft-package download, checking the listed .files path and DEBUG=nucleus* logs. Done means the 5.0.0 package downloads successfully and the cause of ERR_CONNECTION_REFUSED is covered by a verified fix or clear diagnosis.

Written by the indexing model from the issue text.

Assessment

Tech stack
debian, docker, electron, typescript
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.