Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CMD-N & menu New crash app #275

Closed
InvisibleOrdinary opened this issue Oct 24, 2018 · 7 comments
Closed

CMD-N & menu New crash app #275

InvisibleOrdinary opened this issue Oct 24, 2018 · 7 comments
Labels
Milestone

Comments

@InvisibleOrdinary
Copy link

Expected Behavior

either selecting from the menu or CMD-N would save current roast and begin new roast

Actual Behavior

it just hangs up, requiring a force-quit, and restart for both avenues to a new roast

Steps to Reproduce the Problem

Specifications

  • Artisan Version: 1.5
  • Artisan Build (number in brackets shown in the about box): fc6ebda
  • Platform (Mac/Windows/Linux + OS version): Mac OS 10.14
  • Connected devices or roasting machine: Phidgets 1048, 2 probes, Proaster 10K

Please attach your current Artisan settings file (as exported via menu Help >> Save Setings as *.aset) file.

181023_artisan-settings.aset.zip

Please attach any relevant Artisan *.alog profiles.

Note that you need either add a .txt extension or zip the files before uploading. Otherwise you will receive a "Not a supported file type" error on uploading.

@MAKOMO
Copy link
Member

MAKOMO commented Oct 24, 2018

I cannot reproduce this one. What are the exact steps to reproduce this crash? I loaded your settings in Artisan v1.5 on my Mac and pressed CMD-N and it works as expected. Please give a bit more information. Thanks!

@MAKOMO
Copy link
Member

MAKOMO commented Oct 24, 2018

Now I can reproduce. I am looking into this...

@MAKOMO
Copy link
Member

MAKOMO commented Oct 24, 2018

Found the cause of this hang. This is a feature interaction with the "Always ON" flag (Config >> Sampling Interval). For now you can just turn that one off. I will fix this for the next version. Thanks for reporting. Good catch!

@MAKOMO MAKOMO added the bug label Oct 24, 2018
@MAKOMO MAKOMO added this to the v1.6 milestone Oct 24, 2018
@MAKOMO
Copy link
Member

MAKOMO commented Oct 24, 2018

Fixed by Commit 2308085

@MAKOMO MAKOMO closed this as completed Oct 24, 2018
@MAKOMO
Copy link
Member

MAKOMO commented Oct 24, 2018

You can test this using the current builds on BinTray https://bintray.com/artisan/artisan-artifacts/artisan/master#files

@MAKOMO
Copy link
Member

MAKOMO commented Oct 24, 2018

Totally unrelated to this issue. You document here that you have a "Proaster 10K", but I see from your settings that you use Phidgets to read the data from the machine. I was under the impression that this machine features a USB connector delivering data via MODBUS RTU. Did the "Proaster" machine setup provided by Artisan not work for your machine? If not, I just got a slightly modified settings that seems to work for another Artisan user with such a machine.

@InvisibleOrdinary
Copy link
Author

Thanks - I will test this build next week… 

On the Proaster question… I did open that once, but it didn't immediately seem to work… though that might have been my hurry… I do know that the phidgets was installed aftermarket.

But also, I am leasing time on this machine, and so don't own it and there are others who also lease time but don't use software (hence the multiple lines out form phidgets)… 

however, I will look to see if there is a different connection next week… and if you'd send me that setting file, I will try that too.

Cheers

Dave

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants