UserWarning on acquisition notification handler.

[carlkesselman]

Bug report

Bug summary

I am getting the following warning message. Pip install of latest versions of pycromanager. Have latest nightly build of micromanager installed. It tells me not to worry, but I'm worried....

C:\ProgramData\Anaconda3\envs\spim-data\Lib\site-packages\pycromanager\acquisitions.py:366: UserWarning: Could not create acquisition notification handler. This should not affect performance, but indicates that Micro-Manager is out of date
  warnings.warn('Could not create acquisition notification handler. This should not affect performance,'

Expected outcome

Actual outcome

Version Info

• Operating system: Windows 10
• pycromanager version: 28.2
• MicroManager version: 2.03 20230827
• Python version: 3.11.5
• Python environment (command line, IDE, Jupyter notebook, etc)

[henrypinkard]

Hahahah. I'm working on a branch that should enable a very useful new API and some cool functionality, which hopefully will be PRed soon and should fix this. Perhaps a more reassuring error message in the mean time? :)

[carlkesselman]

Take a look at my recently posted bug report: #682 I’m wondering if I was right to be worried after all…… Carl On Sep 5, 2023, at 9:40 AM, Carl Kesselman ***@***.***> wrote: Actually, I’m ok… so this is expected behavior. I’m fighting another issue and I didn’t want to waste time chasing it down if it was a different problem. I have been tracking the new API…. I think I could use it. Carl On Sep 5, 2023, at 9:03 AM, Henry Pinkard ***@***.***> wrote: Hahahah. I'm working on a branch that should enable a very useful new API and some cool functionality, which hopefully will be PRed soon and should fix this. Perhaps a more reassuring error message in the mean time? :) — Reply to this email directly, view it on GitHub<https://urldefense.us/v2/url?u=https-3A__github.com_micro-2Dmanager_pycro-2Dmanager_issues_678-23issuecomment-2D1706905503&d=DwMCaQ&c=qzHnJIRvjI6L-clJH8JwLQvf_Iq43fzikf6aoxZgMb8&r=sGCma2ufaUVT-N141kRIZQ&m=u6JRjrVBK6cPykm0AMvfMOEjSv1KZO4J9srnV7Tl3QDiNU_3noGQB_8nNtNqSJsm&s=XB60AD7K_hu5YMt7gaXEeXsXqpU5BomhhRT1Cm-MaCE&e=>, or unsubscribe<https://urldefense.us/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AA3OGXTBYH7XDQXXJSEAUODXY5ENFANCNFSM6AAAAAA4IDEK6Y&d=DwMCaQ&c=qzHnJIRvjI6L-clJH8JwLQvf_Iq43fzikf6aoxZgMb8&r=sGCma2ufaUVT-N141kRIZQ&m=u6JRjrVBK6cPykm0AMvfMOEjSv1KZO4J9srnV7Tl3QDiNU_3noGQB_8nNtNqSJsm&s=S0qCVBpvvTpin6XKDIbEbNDNqHUWaT6PsOHUCRcr9pg&e=>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[henrypinkard]

Ack! Your intuition was right yet again! I will look into a fix ASAP

[henrypinkard]

I think #685 should fix this