-
Notifications
You must be signed in to change notification settings - Fork 35
Incompatible Sock.js versions #913
Comments
I was tested this on chrome, firefox, opera. I can't reproduce this bug. If I notice this behavior, I will check the conditions in which it happened. |
@tomaszfryc Yes, me also. Cannot reproduce - but i believe it is not influencing any behavior of application. Additionally it looks like version mismatch on api server and frontend app so i've downgraded version to match your API. Maybe it will stop occuring. |
@damianprzygodzki |
I don't know your dependencies on that 1.0.0 version so to make less risky change i've downgraded on frontend. If you want to update that on your side - just let me know. |
cannot be tested. moving it to done. |
[#474](metasfresh/metasfresh-webui-api-legacy#474) Dashboard API: specify position when adding a new KPI/target indicator [metasfresh/metasfresh/issues#1814](#1814) Hide Processed flag from all M_InOut/Returns windows (webui) [#926](metasfresh/metasfresh-webui-frontend-legacy#926) Board window does not open via Sitemap menu [#470](metasfresh/metasfresh-webui-api-legacy#470) Cache image endpoint [#464](metasfresh/metasfresh-webui-api-legacy#464) Dashboard API: unify get available kpis/targetIndicators endpoints [#465](metasfresh/metasfresh-webui-api-legacy#465) Provide Endpoint w/ entry selections for given Breadcrumb [#864](metasfresh/metasfresh-webui-frontend-legacy#864) Show view sticky/readonly filters [#833](metasfresh/metasfresh-webui-frontend-legacy#833) Dashboard Window w/ Swimlane type functionalities [#1861](#1861) Performance degradation in HUKey.isReadonly() [#1873](#1873) Fix control amount and qty in payment data imported from camt.54 [#467](metasfresh/metasfresh-webui-api-legacy#467) board API: GET board/{boardId}/card?cardIds [#913](metasfresh/metasfresh-webui-frontend-legacy#913) Incompatible Sock.js versions me-45
Type of issue
Bug
Current behavior
Occurring Incompatibility error w/ Sock.js
Expected behavior
No errors.
Steps to reproduce
This happens occasionally. Here in Login.
The text was updated successfully, but these errors were encountered: