search

msupply-foundation / open-msupply

Open mSupply represents our most recent advancement in the Logistics Management Information System (LMIS), expanding on more than two decades of development inherited from the well-established legacy of the original mSupply.
https://msupply.foundation/open-msupply/
Other
23 stars 15 forks source link

Problem in label printer connection testing #3849

Open AnushaUp opened 6 months ago

AnushaUp commented 6 months ago

What went wrong? 😲

Evan though the connection is OK. There's showing problem in testing connection ![Screenshot 2024-05-09 at 10 17 38 am](https://github.com/msupply-foundation/open-msupply/assets/115983430/0564f5e6-fc99-432e-9f5e-c04be2467b67) ## Expected behaviour 🤔 Should give a proper alert ## How to Reproduce 🔨 Steps to reproduce the behaviour: 1. Open oms site 2. Go to Admin -> Devices 3. Connect label printer 4. Click on Test button 5. See error ## Your environment 🌱
nishaDangol-Sussol commented 6 months ago

Checked in v2.0.0-rc5 standalone exe; still doesn't work

mark-prins commented 6 months ago

when did v2.0.00-rc5 get built? I cannot see it in the releases, and there's no tag in the repo. I cannot check that this fix is in the build you are using 😢

nishaDangol-Sussol commented 6 months ago

when did v2.0.00-rc5 get built? I cannot see it in the releases, and there's no tag in the repo. I cannot check that this fix is in the build you are using 😢

@raviSussol built the installers on Jenkins from V2.0.0-RC branch yesterday.

mark-prins commented 6 months ago

ok, thanks. this fix is in that build - it's working for me here using our zebra printer. difficult to diagnose the problem from here, possibly will have to make a test utility which tries various timeout values

marthakeezy commented 6 months ago

Can confirm worked for me in V2.0.0-rc5 ✅

roxy-dao commented 6 months ago

Can I close this as complete? @mark-prins

mark-prins commented 6 months ago

No - Nisha still had an issue; we need to implement some sort of tester for the Nepal team to check so that we can refine the settings. hopefully it is a timeout issue with the network and we just have to adjust, but I would have thought a 1s connection timeout is enough 🤷