VisiCut
VisiCut copied to clipboard
Getting previous versions.
An user of ours needs to download the .deb for a specific 1.8 version of Visicut ( 1.8-62 , older ones won't import the settings, more recent ones have all sorts of bugs ). However I can't find those anywhere, only builds for the latest ones. Where can the .deb be found for all versions ?
Thanks.
If you have docker you can use https://github.com/t-oster/VisicutBuilder to build whatever version you need. I can send you the deb tomorrow
Hey.
I'm on the run, I'd love it if you could do the .deb for me, it'd really get me out of a pinch. Thanks for answering so fast too btw.
Cheers.
On Wed, Oct 9, 2019 at 5:16 PM Thomas Oster [email protected] wrote:
If you have docker you can use https://github.com/t-oster/VisicutBuilder to build whatever version you need. I can send you the deb tomorrow
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/t-oster/VisiCut/issues/529?email_source=notifications&email_token=AAA2SFMAERFZG6ZMXAQ4XITQNXYS7A5CNFSM4I67ITH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAYHWPI#issuecomment-540048189, or mute the thread https://github.com/notifications/unsubscribe-auth/AAA2SFNE4WCUAB7JLIFRUSLQNXYS7ANCNFSM4I67ITHQ .
--
勇気と気分
By the way, it would be helpful if your user would report the bug you are talking about. I don't know of any significant bugs on Linux.
Yes, there's several of them, I'm supposed to make tickets about them but never find the time. I'll work harder on getting there.
On Thu, Oct 10, 2019 at 9:03 PM Max Gaukler [email protected] wrote:
By the way, it would be helpful if your user would report the bug you are talking about. I don't know of any significant bugs on Linux.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/t-oster/VisiCut/issues/529?email_source=notifications&email_token=AAA2SFNBJJVYRZ7RBFOVFPLQN54ABA5CNFSM4I67ITH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEA5OLZY#issuecomment-540730855, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAA2SFKQIX2PHD5ZE4IANUDQN54ABANCNFSM4I67ITHQ .
--
勇気と気分
I think @arthurwolf might be right about the bugs.
Trying to download recommended settings (for any lab) on the latest build crashes on my PC. I ran into this while trying to download settings that were added by me in a recent pull request (by the name of Makerspace BLR). Interestingly, on my laptop, downloading settings works just fine. I'm running version 1.8.94-... on my laptop. But I tried that same version on my PC, which too crashed.
Let me know if there's a way I can help debug this (since it seems tricky to reproduce).
The error dump on terminal is not much helpful:
Oct 14, 2019 3:06:01 PM com.t_oster.visicut.managers.FilebasedManager readObjectFromXmlFile
WARNING: Could not load object in current XML format, retrying with old format from 2012:
Can't load settings.
'/usr/local/home/pallavag/.visicut' doesn't exist. We create it.
Copying default settings...
done.
Copying default settings...
done.
cannot find default settings folder for mappings
Copying default settings...
done.
Copying default settings...
done.
Generating some defaults if no examples exist...
Security framework of XStream not initialized, XStream is probably vulnerable.
Security framework of XStream not initialized, XStream is probably vulnerable.
Security framework of XStream not initialized, XStream is probably vulnerable.
Saving generated settings...
/usr/bin/visicut: line 10: 46852 Segmentation fault java -Xms256m -Xmx2048m -jar "$DIR/Visicut.jar" --singleinstanceport $port "$@"
Running Debian based, same OS on both PC and Laptop.
Hi @arthurwolf here is the 1.8-62 deb.Sorry it took so long, but I am quite busy as always... https://cloud.thomas-oster.de/s/Bq90Mi1FPasuDfb
@pallavagarwal07 please create a new issue for your problem, including the Java version and exact name and version of your operating system.
@mgmax your ask "including the java version" tipped me to the workaround, as both laptop and PC were running different Java versions. I've created the modified bug report as a new issue.
Thanks :)
@arthurwolf which settings do not work anymore? Please provide a reproducible example, because we can now add automatic migrations to fix old settings
@t-oster would it be possible to keep more than the last 5 versions on the download page, for example the last 50 ones? If space is a problem, we could also use GitHub releases and automatically build and upload them via GH actions (like GitLab's CI/CD): https://github.com/actions/upload-release-asset
Thank you very much for the .deb I'm going to be opening tickets for small issues and feature requests based on the reports/requests from the Fablabs using our lasers. Sorry I haven't been able to earlier, was very busy with Smoothieboard v2. Thanks again !
On Sun, Dec 8, 2019 at 4:20 PM Max Gaukler [email protected] wrote:
@t-oster https://github.com/t-oster would it be possible to keep more than the last 5 versions on the download page, for example the last 50 ones? If space is a problem, we could also use GitHub releases and automatically build and upload them via GH actions (like GitLab's CI/CD): https://github.com/actions/upload-release-asset
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/t-oster/VisiCut/issues/529?email_source=notifications&email_token=AAA2SFKOWRKXXIR35EJVVE3QXUGFLA5CNFSM4I67ITH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGHBHAA#issuecomment-562959232, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAA2SFN46VRREYE5J5VGFE3QXUGFLANCNFSM4I67ITHQ .
--
勇気と気分
@mgmax looks interesting. If you have time, you can create a github workflow for automatic releases from master branch. Maybe this workflow can use the docker image of visicutbuildservice.