Repository navigation
Beet hackathon demo - Beet if reopened creates new process ids and the old process ids stay the same (Observed on Linux may be windows users wont face this issue) I needed to manually kill them for the app to work. #124
Description
Please assign to me @sschiessl-bcp
Activity
sschiessl-bcp commentedon May 14, 2019
Can you describe the steps to reproduce?
manikey123 commentedon May 29, 2019
Below lines are spawning redundant threads. Resulting in stale UI. That needs to be manually killed.
Do suggest recommendation for the below lines. Should they be removed. Then the connection icon wont come. Plz suggest any ideas
@sschiessl-bcp
sschiessl-bcp commentedon Jun 1, 2019
How to reproduce?
manikey123 commentedon Jun 8, 2019
Use Linux OS and then start the beet app.
Observed that the line keeps frequently repeating.
manikey123 commentedon Jun 8, 2019
In order to fix above issue I researched AppImg
https://appimage.org/
AppImg is open source. Set ups are handled in the AppImg itself and it would be seamless for Linux users
AppImg is also implemented by Scatter
https://get-scatter.com/download
This also helps solve below setups which the user needs to do manually
#123 (comment)
Let me know if I can fix using this approach or do suggest any other resolution.
sschiessl-bcp commentedon Jun 26, 2019
Yes, ideally we would be building AppImage through travis. Please continue