Expiration time idea

I think it may be more convenient and type-safe to provide expiration time as time.Duration (for EX/PX) or time.Time (for EXAT/PXAT). Just convert to milliseconds and use the value.

Hi @ash2k,
Thank you for your suggestions. I would much prefer doing that with helpers, for example:
c.B().Set().Key("k").Value("v").ExSeconds(rueidis.Sec(time.Now()))

I believe this way will make the API very clear and be no room for wondering whether it converts to other precision like microseconds.
We have actually done a similar thing here: https://github.com/redis/rueidis/blob/45b2008fb313b16110d304b50c8af11b04238083/rueidiscompat/adapter.go#L819-L823
Maybe we can just expose those helpers from rueidis.

I don't think there is much value in helpers as the same can be done with just methods on Duration and Time. The whole point (type safety and ease of use) is lost when in the end user still needs to provide an int64. People who care how exactly the method works can read it's docs (it can explain that what resolution it uses) or code.
Type safety is important as some methods/commands accept seconds and some milliseconds and it's easy to use a wrong helper for a wrong resolution (but the same type) and not notice.

I can take this migration up if required ^_^

I can take this migration up if required ^_^

Hi @SoulPancake, this should be done by adding new functions instead of a migration.

Hi @ash2k,
Thanks to @HoganEdwardChu (https://github.com/redis/rueidis/pull/267), we will be able to do this in the next version:
client.B().Set().Key("k").Value("v").Ex(time.Second).Build()
client.B().Set().Key("k").Value("v").Exat(time.Now()).Build()
client.B().Set().Key("k").Value("v").Px(time.Second).Build()
client.B().Set().Key("k").Value("v").Pxat(time.Now()).Build()

Does it make sense to you?

Hi @rueian! Yes, this is perfect, thank you!


ModuleNotFoundError : from tensorflow.compat.v1 import *

ModuleNotFoundError: No module named tensorflow.compat.v1 in tensorflow==2.2.0-rc3
python == 3.6.8 in MacBook Pro

Can you please share more details. I am able to run this

Hi Aditya,
Thanks for the response, yes I am also able to run it in colab but not in mac book.
In colab it is using python 3.6.9.
but in python website, python 3.6.9 build is not there for mac so i am using python 3.6.8 and tensorflow==2.2.0-rc3 as it is the same tensorflow version in colab.
Now I am facing ModuleNotFoundError in macbook but not in colab.

@ajay-sreeram are other functionalities of TensorFlow working fine? like are you able to
import tensorflow as tf
print(tf.__version__)

Is the issue only with tensorflow.compat.v1 import * or with other stuff in the package as well?

Yes I am able to import tensorflow and all the other functionalities are working fine and I see only .compat.v1 issue for now.

If the issue is Mac specific. I am unsure of Mac Platform as I haven't used it. Hope someone helps here @ravikyram

I am seeing no issues with linux platform and colab.
@ymodak can you please look into this issue.Thanks!

I am seeing no issues with Windows 7 as well.

I could successfully import the compat.v1 module in macOS with Python 3.7 and TF 2.2.0-rc3.
Also I found the python 3.6.9 version you were looking for.
However  I doubt that is a reason for failure. May be you can try setting virtual env before importing the modules or use an IDE.
Thanks!

I could successfully import the compat.v1 module in macOS with Python 3.7 and TF 2.2.0-rc3.
Also I found the python 3.6.9 version you were looking for.
However  I doubt that is a reason for failure. May be you can try setting virtual env before importing the modules or use an IDE.
Thanks!

Thankyou Yasir, I will try with python 3.7 then.

closing the issue as it worked with python 3.6.9 version

Hi
I am using python 3.6
cuda : 10.1
tensorflow-gpu==2.2.0
i am getting this error :

import tensorflow.compat.v1 as tf
Traceback (most recent call last):
File "", line 1, in
ModuleNotFoundError: No module named 'tensorflow.compat.v1'

Can anyone please suggest some work around or solution?

Hi
I am using python 3.6
cuda : 10.1
tensorflow-gpu==2.2.0
Ubuntu = 18.04
i am getting this error :

import tensorflow.compat.v1 as tf
Traceback (most recent call last):
File "", line 1, in
ModuleNotFoundError: No module named 'tensorflow.compat.v1'

Can anyone please suggest some work around or solution?

Try with python 3.7 Satish, it might work.

Hi
I am using python 3.6
cuda : 10.1
tensorflow-gpu==2.2.0
Ubuntu = 18.04
i am getting this error :

import tensorflow.compat.v1 as tf
Traceback (most recent call last):
File "", line 1, in
ModuleNotFoundError: No module named 'tensorflow.compat.v1'

Can anyone please suggest some work around or solution?

If you are running Tensorflow v2.2 and Python 3.6, you can try this workaround:
import tensorflow._api.v2.compat.v1 as tf

I think problem is the version specific.

Hi
I am using:
python 3.6
tensorflow==1.5
i am getting this error :
File "C:\Users\User\miniconda3\envs\bot\lib\site-packages\tflearn_init_.py", line 4, in
import tensorflow.compat.v1 as tf
ModuleNotFoundError: No module named 'tensorflow.compat

Hi
same issue
python 3.10.7
tensorflow 2.9.2
Mac pro 11.6
error:
Traceback (most recent call last):   File "/Users/xuyao/Workspaces/ai/tensorflow/models/research/object_detection/builders/model_builder_tf2_test.py", line 21, in <module>     import tensorflow.compat.v1 as tf ModuleNotFoundError: No module named 'tensorflow.compat'

Hi same issue,
OS: Ubuntu 22.04
Python version: 3.10.6
Tensorflow version: 2.11
lTraceback (most recent call last):
  File "[/pythonAI/Tensorflow/models/research/object_detection/builders/model_builder_tf2_test.py](https://file+.vscode-resource.vscode-cdn.net/Storage/pythonAI/Tensorflow/models/research/object_detection/builders/model_builder_tf2_test.py)", line 21, in <module>
    import tensorflow._api.v2.compat.v1 as tf
  File "[/anprsys/lib/python3.10/site-packages/tensorflow/__init__.py](https://file+.vscode-resource.vscode-cdn.net/anprsys/lib/python3.10/site-packages/tensorflow/__init__.py)", line 37, in <module>
    from tensorflow.python.tools import module_util as _module_util
  File "[/anprsys/lib/python3.10/site-packages/tensorflow/python/__init__.py](https://file+.vscode-resource.vscode-cdn.net/media/soumalya/Storage/pythonAI/anprsys/lib/python3.10/site-packages/tensorflow/python/__init__.py)", line 36, in <module>
    from tensorflow.python import pywrap_tensorflow as _pywrap_tensorflow
  File "[/anprsys/lib/python3.10/site-packages/tensorflow/python/pywrap_tensorflow.py](https://file+.vscode-resource.vscode-cdn.net/media/soumalya/Storage/pythonAI/anprsys/lib/python3.10/site-packages/tensorflow/python/pywrap_tensorflow.py)", line 26, in <module>
    self_check.preload_check()
  File "[/anprsys/lib/python3.10/site-packages/tensorflow/python/platform/self_check.py](https://file+.vscode-resource.vscode-cdn.net/anprsys/lib/python3.10/site-packages/tensorflow/python/platform/self_check.py)", line 63, in preload_check
    from tensorflow.python.platform import _pywrap_cpu_feature_guard
ImportError: libhsa-runtime64.so.1: cannot open shared object file: No such file or directory

Please reopen this issue

Hi Same Isse
"    import tensorflow.compat.v1 as tf
ModuleNotFoundError: No module named 'tensorflow.compat'"
Python 3.7.16
Tensorflow 2.2.0


Wednesday evening: OccupyGitHub

We have a tentative offer from GitHub to host an evening reception at GitHub HQ. We've discussed having this on Wednesday, August 31. This issue is to firm up plans for the time, date and content. It can be closed when we post those details to the website.
We had one idea for the content (other than a drinks and snacks reception): Good software development practices, such as licensing or Python packaging or (of course) using git. GitHub seems the appropriate place to discuss such things. Hopefully we can also get a tour.

opening a related issue...

Alright! I just met up with Patrick McKenna @patrickmckenna Arfon Smith @arfon from GitHub, and we talked about what would work best for our two communities when we mix them together on Wednesday Aug 31. Below is the rough plan we cooked up, for comment!

We head over to GitHub HQ after lunch, aiming to arrive at 3pm
We get settled in the main hall and restart hacking
At 4pm one of us from AHW gives a short talk on GitHub is used (and best used?) in astronomy - the GitHub staff are likely to be very interested in this.
At that talk we encourage any GitHub people to join us in the hacking, either taking part in the ongoing or emergent astro projects, or starting something new related to GitHub useage in astronomy (including astro hack week)
At some point we have dinner, and the bar will open. We'll need to let them know our dietary preferences, and then they'll get a contractor in.
We continue hacking into the evening, leaving by 10pm.
At some point in the evening we do a breakout, as usual: ideas for this include:

Using Jupyter Notebooks - best practices / tips for researchers, examples of what to use them for (and what not to). One of us would lead this, but the GitHub staff would be very interested, to help them think about how to support notebook use.
Data Engineering - how to think about scaling up data analysis to industrial levels. Ben Eddy or Rohini from GitHub could lead this, maybe with one of us in tandem?

Comment: That sounds like an awesome plan!
It's also very convenient that we'll be out of the BIDS space for one afternoon that week (there's a one-afternoon event that our director would like to hold in the space).

I think we should get @dfm to give the talk on how to use github, because that puts him perfectly on the spot!

We could also do a small panel to get some different perspectives, such as how github is used in big collaborations like LSST (from @drphilmarshall).

As far as I can tell this issue is done.


Fix: Select of "Popular search terms" work only on the first page.

This PR fixes the issue belonging to #3384. For some reason it had an Ajax callback when clicking on query terms in the modal listing. But the response was not adding any additional functionality, it was only throwing an eval error since the it isn't the correct response the ModalWorkflow was expecting.
I removed the listening for modal.loadUrl and bound it to the method to select the query and close the modal.

@gasman I'm requesting you for a review instead of Thibaud, since I saw you originally implemented this section.

Thanks @jjanssen! Merged in 23649990c269285570fb0be16329de10a8f8ab8b.
Not sure what was going on in the old code there :-)


Update tax-service-set-up-environment-master-data-lookup.md

Update Security role name
Update the order to enable Dataverse feature

:x: Organization membership check failed
Members of the MicrosoftDocs organization should use the private repo. Please move your changes to https://github.com/MicrosoftDocs/Dynamics-365-Operations, and close this pull request.


Item was disposed or moved to another subscription

Describe the bug
We have a OPC Publisher with about 24 Endpoints with around 2000-3000 Nodes each. We just updates to version 3.9.10 and facing the issue that after a couple of hours the OPC Publisher removed almost all nodes of the endpoints with the logs stating:
24-08-07 15:35:27.9796] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=...' with server id 1 (created): Item was disposed or moved to another subscription
We can see this error message a lot in the logs, since the issue occurred it was written for the same nodes every hour.
This affected 22 of the endpoints where for most of them, all nodes where disposed and for some only about 60% were disposed.
We athough noticed this happend in two waves. Yesterday at 17:30 6 Endpoints went down and after about 2 hours the other 16 were affected.
After restarting the publisher, all connections were established again and working fine for now. It seems that this is not an issue with the OPC Servers or Nodes because with a restart everything works fine again
To Reproduce
Publisher Config:
{     "Hostname": "publisher_axh_active",     "Cmd": [         "--cl=5",         "--cf",         "--aa",         "--pf=/mount/publishednodes.json",         "--PkiRootPath=/mount/pki",         "--bs=100",         "--di=3600"     ],     "HostConfig": {         "Binds": [             "/home/edge/OPCPublisherMount_Active:/mount"         ]     } }
Version used: 3.9.10
Expected behavior
The nodes are not disposed.
Additional context
Part of the logs:
em.DataChange[0]       Data Item 'ns=2;s=RO_KW_AGGREGAT_NL.1_3MFB40_EA700.in.betriebsart.value' with server id 205 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_MELDEKONTAKT.1_3MFB40_EA801_YA03.in.kontakt.value' with server id 206 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_ALARMKONTAKT.1_3MFB40_EA801_XM54.in.kontakt.value' with server id 207 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_MELDEKONTAKT.1_3MFB40_EA802_YA03.in.kontakt.value' with server id 208 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_ALARMKONTAKT.1_3MFB40_EA802_XM54.in.kontakt.value' with server id 209 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_MELDEKONTAKT.1_3MFB40_EA811_YA03.in.kontakt.value' with server id 210 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_ALARMKONTAKT.1_3MFB40_EA811_XM54.in.kontakt.value' with server id 211 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_MELDEKONTAKT.1_3MFB40_EA812_YA03.in.kontakt.value' with server id 212 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_ALARMKONTAKT.1_3MFB40_EA812_XM54.in.kontakt.value' with server id 213 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_ALARMKONTAKT.1_3MFB40_EA851_XM54.in.kontakt.value' with server id 214 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_ALARMKONTAKT.1_3MFB40_EA852_XM54.in.kontakt.value' with server id 215 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_ALARMKONTAKT.1_3MFB40_EA862_XM54.in.kontakt.value' with server id 216 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_ALARMKONTAKT.1_3MFB40_EA861_XM54.in.kontakt.value' with server id 217 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_ALARMKONTAKT.1_3MFB40_EA871_XM54.in.kontakt.value' with server id 218 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_ALARMKONTAKT.1_3MFB40_EA872_XM54.in.kontakt.value' with server id 219 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_KW_AGGREGAT_NL.1_3MFB40_EA710.in.zustand0.value' with server id 220 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_KW_AGGREGAT_NL.1_3MFB40_EA710.in.zustand1.value' with server id 221 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_KW_AGGREGAT_NL.1_3MFB40_EA710.in.aktive_bedienebene.value' with server id 222 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_KW_AGGREGAT_NL.1_3MFB40_EA710.in.modus.value' with server id 223 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_SOLLWERT.1_3MFB41_AP100_ZE11.out.sollwert.value' with server id 224 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_SOLLWERT.1_3MFB41_AP200_ZE11.out.sollwert.value' with server id 225 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_KW_AGGREGAT_NL.1_3MFB40_EA711.in.zustand0.value' with server id 226 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_KW_AGGREGAT_NL.1_3MFB40_EA711.in.zustand1.value' with server id 227 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_KW_MESSWERT.1_3MFB41_CL001_XQ01.in.ausfall.value' with server id 228 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_KW_MESSWERT.1_3MFB41_CL001_XQ01.in.minalarm.value' with server id 229 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_KW_MESSWERT.1_3MFB41_CL001_XQ01.out.gw_minalarm.value' with server id 230 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_KW_MESSWERT.1_3MFB41_CL001_XQ01.in.tief.value' with server id 231 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_KW_MESSWERT.1_3MFB41_CL001_XQ01.out.gw_tief.value' with server id 232 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_KW_MESSWERT.1_3MFB41_CL001_XQ01.in.wert.value' with server id 233 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s={827D3700-C4FF-41A9-884F-B49DA06097ED}' with server id 1 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_KW_MESSWERT.1_3MFB41_CT001_XQ01.in.ausfall.value' with server id 234 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_KW_MESSWERT.1_3MFB41_CT001_XQ01.in.meldung1.value' with server id 235 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s={82218900-CF04-457D-89AA-4658952B6D64}' with server id 2 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s={101CE900-4D46-4D4B-A828-84D575C85DEF}' with server id 3 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s={D3E10101-CD29-445D-89EB-3D5089A7F197}' with server id 4 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9835] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaMonitoredItem.DataChange[0]       Data Item 'ns=2;s=RO_KW_MESSWERT.1_3MFB41_CT001_XQ01.in.meldung2.value' with server id 236 (created): Item was disposed or moved to another subscription [24-08-07 15:35:27.9847] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaSubscription[0]       1fdf3dbee7ab3b7700eb7c690aab5a41af407714_0:3762709867 - Now monitoring 155 nodes:       # Good/Bad:     155/0       # Reporting:    155       # Sampling:     0       # Disabled:     0       # Not applied:  0       # Removed:      0 [24-08-07 15:35:27.9849] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaSubscription[0]       989ca92c8a770ee4b215750a5e242542683c1ca9_0:3762709869 - Now monitoring 52 nodes:       # Good/Bad:     52/0       # Reporting:    52       # Sampling:     0       # Disabled:     0       # Not applied:  0       # Removed:      0

Please try mcr.microsoft.com/iotedge/opc-publisher:2.9.11-preview1, which should address this issue.

Background - this happens during subscription reset where the old monitored items are not properly removed from the subscription and then remain in a disposed state.  Data should flow, but heartbeats and other timers are off and not firing anymore.

Thank you for the quick response! To understand the issue: Why are the subscriptions reset in the first place? I noticed that every hour the subscriptions were recreated, eg:
[24-08-07 15:05:45.2384] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaSubscription[0]       4e7e56282acc83bbaae502cca831be66e4365a23_3:2124724734 - Now monitoring 1000 nodes:       # Good/Bad:     969/31       # Reporting:    1000       # Sampling:     0       # Disabled:     0       # Not applied:  0       # Removed:      0
In our case, we sadly hadn't any dataflow anymore for the affected subscriptions?

The message you are seeing there happens as a result of a) when a session recovery/reconnect sequence was run and produced either a new session or the old one.  Then the subscription state in the session is synchronized which if it is new creates the monitored items - or - b) the subscription itself ran into an issue e.g. the subscription lifetime expired on the server and status change notification returned, or keep alives were missing on our side - then the subscription in a running session is reset (closed and recreated). Then the items should have been recreated, but the bug we had was that the existing (now disposed items) are not even touched anymore.  But they are reported now as "bad".  We fixed this in 2.9.11.
This should all be prominent in the log.  If you can try 2.9.11-preview1 that would help me a lot.
You also see this message you pasted if applying one or more monitored items failed before or on the general management timer.  Typically nothing is done to the subscription or items at this point though if all is working fine.

Thanks for the clarification!
I upgraded to 2.9.11-preview1 and so far everything looks good. I will monitor the logs and will give an update tomorrow!

It seems like 3.9.11-preview11 helped with the issue of Item was disposed or moved to another subscription. But we had one endpoint with issues where I am not to sure what happend and if it is related to the new publisher version. Here are the findings:

yesterday at around 17:36 we did not receive any new data for the endpoint.
The Publisher metric iiot_edge_publisher_is_connection_ok for the endpoint was still sending 1 (so connection is ok)
The Publisher metric iiot_edge_publisher_data_changes_per_second went down to zero
After restarting the publisher, the endpoint worked again.
We have two separate publisher modules listening on the endpoint (both Version 3.9.11-preview1) and it failed for both at around the same time.
It seems like we had a network issue from the edge device to the opc ua servers because we can see that for a lot of the connections the error:
[24-08-08 17:36:59.8927] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaClient[0]     opc.tcp://***4980_6A0BCD90 [state:Connecting|refs:5]: Publish error: BadSecureChannelClosed 'BadSecureChannelClosed' (Actively handled: False)...
-- it seems that the connections could recover them self after a one minute (we are checking with our network team, if there was an issue on their side)
But the logs does not mention the failed endpoint, but I found these logs after the network issue, where subscription id matches with the one of the endpoint reported by the metric iiot_edge_publisher_monitored_items:
[24-08-08 17:36:49.9598] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaSubscription[0]     #2/30: Subscription e8586836593ba92624a1f0b6516d1bcf11d4b67c_2:15 is missing keep alive. [24-08-08 17:36:49.9598] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaSubscription[0]     #2/30: Subscription e8586836593ba92624a1f0b6516d1bcf11d4b67c_1:14 is missing keep alive. [24-08-08 17:36:49.9598] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaSubscription[0]     #2/30: Subscription e8586836593ba92624a1f0b6516d1bcf11d4b67c_0:13 is missing keep alive.
and bit after that:
[24-08-08 17:36:59.9693] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaSubscription[0]     Subscription e8586836593ba92624a1f0b6516d1bcf11d4b67c_1:14 STOPPED! [24-08-08 17:36:59.9694] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaSubscription[0]     Subscription e8586836593ba92624a1f0b6516d1bcf11d4b67c_2:15 STOPPED! [24-08-08 17:36:59.9694] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaSubscription[0]     Subscription e8586836593ba92624a1f0b6516d1bcf11d4b67c_0:13 STOPPED!
after this logs, I could not find any mentions of the subscriptions anymore.

Thank you for the details @steffenbeermann, when the subscription is STOPPED, do you see keep alive timeout logs as well (this is the way in OPC UA connection drops are discovered).  If the channel is closed, the keep alive check should fail and trigger a reconnect.  The reconnect should be visible in the logs, if not it would be great if you could share (e.g., via github gist or support team the full logs).
Another important diagnostics info is the number of publish requests in progress, it is one of the metrics at the top of the diagnostic output to console (if --di is not disabled) like this:
 # Queued/Minimum request count       :              4 | 2
 # Good/Bad Publish request count     :              2 | 2

What server is this connected to?
You can also try to re-enable "active" publish error management (--peh).  This used to be the default to quirk around the OPC UA stack not discovering BadChannelClosed or BadSessionIdInvalid on its publish path, and maybe that would help here, but comes with downsides (as both stack and publisher will try to do the same, therefore we turned this off in 2.9.11).

We have two Publisher Modules that connect to the same endpoints. In one of them I could not find the  Got Keep Alive error, but this could happen because the save the logs with an custom module and with this there is a chance that when a lot of logs are written some logs get lost....
In the second module log I found some, here are the logs related to the failed endpoint and I maybe found some usefull logs:
[24-08-08 17:36:58.3624] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaClient[0]       opc.tcp://<IP_ADDRESS>:4840_116A0CAD_KWT [state:Ready|refs:3]: Got Keep Alive error: BadNoCommunication 'Server not responding to keep alive requests.' (08/08/2024 17:36:58:BadNoCommunication 'Server not responding to keep alive requests.' [24-08-08 17:36:58.3645] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaClient[0]       opc.tcp://<IP_ADDRESS>:4840_116A0CAD_KWT [state:Ready|refs:3]: Got Keep Alive error: BadNoCommunication 'Server not responding to keep alive requests.' (08/08/2024 17:36:58:BadNoCommunication 'Server not responding to keep alive requests.' ... 24-08-08 17:36:58.3651] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaClient[0]       opc.tcp://<IP_ADDRESS>:4840_116A0CAD_KWT [state:Ready|refs:3]: Reconnecting session opc.tcp://<IP_ADDRESS>:4840_116A0CAD_KWT due to error BadNoCommunication 'Server not responding to keep alive requests.'... [24-08-08 17:36:58.3651] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaClient[0]       opc.tcp://<IP_ADDRESS>:4840_116A0CAD_KWT [state:Connecting|refs:3]: Session opc.tcp://<IP_ADDRESS>:4840_116A0CAD_KWT with opc.tcp://<IP_ADDRESS>:4840 changed from Ready to Connecting ... [24-08-08 17:36:59.2681] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaClient[0]       opc.tcp://<IP_ADDRESS>:4840_116A0CAD_KWT [state:Ready|refs:3]: Session opc.tcp://<IP_ADDRESS>:4840_116A0CAD_KWT with opc.tcp://<IP_ADDRESS>:4840 changed from Connecting to Ready [24-08-08 17:36:59.2682] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaClient[0]       opc.tcp://<IP_ADDRESS>:4840_116A0CAD_KWT [state:Ready|refs:3]: Client RECOVERED! [24-08-08 17:36:59.2769] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaStack[0]       Publish #93680, Reconnecting=False, Error: BadNoSubscription [24-08-08 17:36:59.2857] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaStack[0]       Publish #93681, Reconnecting=False, Error: BadNoSubscription [24-08-08 17:36:59.2915] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaSubscription[0]       e8586836593ba92624a1f0b6516d1bcf11d4b67c_0:16 - Now monitoring 1000 nodes:       # Good/Bad:      1000/0       # Reporting:     1000       # Sampling:      0       # Heartbeat/ing: 0/0       # Condition/ing: 0/0       # Disabled:      0       # Not applied:   0       # Removed:       0 [24-08-08 17:36:59.2952] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaSubscription[0]       e8586836593ba92624a1f0b6516d1bcf11d4b67c_1:17 - Now monitoring 1000 nodes:       # Good/Bad:      1000/0       # Reporting:     1000       # Sampling:      0       # Heartbeat/ing: 0/0       # Condition/ing: 0/0       # Disabled:      0       # Not applied:   0       # Removed:       0 [24-08-08 17:36:59.2982] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaSubscription[0]       e8586836593ba92624a1f0b6516d1bcf11d4b67c_2:18 - Now monitoring 757 nodes:       # Good/Bad:      757/0       # Reporting:     757       # Sampling:      0       # Heartbeat/ing: 0/0       # Condition/ing: 0/0       # Disabled:      0       # Not applied:   0       # Removed:       0 [24-08-08 17:36:59.2984] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaClient[0]       opc.tcp://<IP_ADDRESS>:4840_116A0CAD_KWT [state:Ready|refs:3]: Applying changes to 3 subscription(s) took 00:00:00.0301485. [24-08-08 17:36:59.3074] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaStack[0]       Publish #93682, Reconnecting=False, Error: BadNoSubscription [24-08-08 17:36:59.3157] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaStack[0]       Publish #93683, Reconnecting=False, Error: BadNoSubscription [24-08-08 17:36:59.3630] fail: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaStack[0]       Publish #27560, Reconnecting=True, Error: BadSecureChannelClosed ... [24-08-08 17:37:59.2879] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaSubscription[0]       #5/30: Subscription e8586836593ba92624a1f0b6516d1bcf11d4b67c_0:16 is missing keep alive. [24-08-08 17:37:59.2920] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaSubscription[0]       #5/30: Subscription e8586836593ba92624a1f0b6516d1bcf11d4b67c_1:17 is missing keep alive. [24-08-08 17:37:59.2961] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaSubscription[0]       #5/30: Subscription e8586836593ba92624a1f0b6516d1bcf11d4b67c_2:18 is missing keep alive. ... [24-08-08 17:43:11.2889] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaSubscription[0]       Trigger management of subscription e8586836593ba92624a1f0b6516d1bcf11d4b67c_0:16... [24-08-08 17:43:11.2923] crit: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaSubscription[0]       #31/30: Keep alive count exceeded. Perform Reset for e8586836593ba92624a1f0b6516d1bcf11d4b67c_1:17... [24-08-08 17:43:11.2923] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaSubscription[0]       Trigger management of subscription e8586836593ba92624a1f0b6516d1bcf11d4b67c_1:17... [24-08-08 17:43:11.2964] crit: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaSubscription[0]       #31/30: Keep alive count exceeded. Perform Reset for e8586836593ba92624a1f0b6516d1bcf11d4b67c_2:18... [24-08-08 17:43:11.2964] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaSubscription[0]       Trigger management of subscription e8586836593ba92624a1f0b6516d1bcf11d4b67c_2:18... ... 24-08-08 17:43:12.7730] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaSubscription[0]       Enabled Subscription e8586836593ba92624a1f0b6516d1bcf11d4b67c_1:20 in session opc.tcp://<IP_ADDRESS>:4840_116A0CAD_KWT. [24-08-08 17:43:12.7828] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaSubscription[0]       ========  Closing subscription e8586836593ba92624a1f0b6516d1bcf11d4b67c_2:18 and re-creating ========= [24-08-08 17:43:12.8242] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaSubscription[0]       Subscription 'e8586836593ba92624a1f0b6516d1bcf11d4b67c_2:0' closed. [24-08-08 17:43:12.8242] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaSubscription[0]       Creating new disabled subscription e8586836593ba92624a1f0b6516d1bcf11d4b67c_2:0 in session opc.tcp://<IP_ADDRESS>:4840_116A0CAD_KWT. [24-08-08 17:43:12.8329] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaSubscription[0]       Successfully created subscription e8586836593ba92624a1f0b6516d1bcf11d4b67c_2:21'.       Actual (revised) state/desired state:       # PublishingEnabled False/False       # PublishingInterval 1000/1000       # KeepAliveCount 10/0       # LifetimeCount 30/0 [24-08-08 17:43:13.3566] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaSubscription[0]       e8586836593ba92624a1f0b6516d1bcf11d4b67c_2:21 - Now monitoring 757 nodes:       # Good/Bad:      757/0       # Reporting:     757       # Sampling:      0       # Heartbeat/ing: 0/0       # Condition/ing: 0/0       # Disabled:      0       # Not applied:   0       # Removed:       0 [24-08-08 17:43:13.3651] info: Azure.IIoT.OpcUa.Publisher.Stack.Services.OpcUaSubscription[0]       Enabled Subscription e8586836593ba92624a1f0b6516d1bcf11d4b67c_2:21 in session opc.tcp://<IP_ADDRESS>:4840_116A0CAD_KWT.
Because there are some additional informations like node names and so on, I need to check if I can upload the full logs. I will give an update on monday.
I could not find the diagnostic info, even the start up is with '--dii==3600'? But we collect all metrics via the metric collector. For iiot_edge_publisher_good_nodes / iiot_edge_publisher_bad_nodes there were no changes in the timespan of the issue. But I am not sure if this is the same? I could not find the corresponding metrics to  Queued/Minimum request count?
It connects to an OPC UA Server that is provided by a power plant provider. Sadly I don't know which kind of software they are using to provide the OPC UA Server.

You can set --di=60 and there will be metrics printed to the console every minute.  But it is ok what you are doing.  I could not see anything concerning above.  Don't share - it is ok.
But you could test 2.9.11-preview2 which I just released which will re-enable the quirk that resets the session when the publish requests return BadNoSession or BadInvalidSessionId.  Because of a reported interop issue, I went through a lot of reconnect testing using a network shaper yesterday and today and validated that with TCP RST or tampered packets the publisher always recovered, so it is possibly a server vendor issue, too, just like in the reported case.

okay, I will test 2.9.11-preview2. But over the weekend it ran without problems with 2.9.11-preview1 as well.

Thanks for testing and confirming, I will close, please let me know if you encounter issues by either commenting here or open a new issue.


Enable EaaS in public production

@dperaza4dustbit please review the SpaceProvisionerConfig. Have you verified the behavior in staging as we discussed on #4251?
@manish-jangra @hugares @hmariset please review the other parts.


import moment for es locale

Details
fix crash on date picker page
Fixed Issues
$ https://github.com/Expensify/App/issues/26719
$ https://github.com/Expensify/App/issues/28315
PROPOSAL: https://github.com/Expensify/App/issues/26719#issuecomment-1708873889
Tests
Same as QA step

[x] Verify that no errors appear in the JS console

Offline tests
Same as QA step
QA Steps

Go to Settings > Preferences > Language > choose Spanish
Go to FAB > Request money > select Distance tab
Enter start and finish addresses and click Next
Select any participant
On confirmation page, click Date field
Verify that Date picker page shows without crash

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
https://github.com/Expensify/App/assets/97676131/b33037eb-c9b1-4a26-8b24-1df6b89627f5

Mobile Web - Chrome
https://github.com/Expensify/App/assets/97676131/0d860ea2-49eb-4429-99d3-22c31de86546

Mobile Web - Safari
https://github.com/Expensify/App/assets/97676131/9af861bf-7447-4248-a4ff-34f64e560e3a

Desktop
https://github.com/Expensify/App/assets/97676131/33152e46-5c9d-4e9a-ae18-01d8713b4d05

iOS
https://github.com/Expensify/App/assets/97676131/21d82a75-47a2-46a5-a602-22505fad54ba

Android
https://github.com/Expensify/App/assets/97676131/c2831aed-f5db-4fe7-8839-93c97e50f15d

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
https://github.com/Expensify/App/assets/108292595/95db6c8a-2d1d-45fe-b955-fb407f8a4232

Mobile Web - Chrome
https://github.com/Expensify/App/assets/108292595/585e3af0-cc89-4986-b650-a4f08962aca6

Mobile Web - Safari
https://github.com/Expensify/App/assets/108292595/0a2d7834-a6f0-4fa6-bf33-21ffce8baabc

Desktop
https://github.com/Expensify/App/assets/108292595/d47263ae-96c6-4d8e-815e-97760f3b053b

iOS
https://github.com/Expensify/App/assets/108292595/7d75be6a-719d-46f1-98ef-258ff44e3a8c

Android
https://github.com/Expensify/App/assets/108292595/ae92d8b1-74ad-4d51-8ae1-9dcb06266646

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/neil-marcellini in version: 1.3.80-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/jasperhuangg in version: 1.3.80-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/neil-marcellini in version: 1.3.81-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/jasperhuangg in version: 1.3.83-11 🚀

platform
result

🤖 android 🤖
skipped 🚫

🖥 desktop 🖥
skipped 🚫

🍎 iOS 🍎
skipped 🚫

🕸 web 🕸
skipped 🚫

🚀 Deployed to production by https://github.com/jasperhuangg in version: 1.3.83-11 🚀

platform
result

🤖 android 🤖
skipped 🚫

🖥 desktop 🖥
skipped 🚫

🍎 iOS 🍎
skipped 🚫

🕸 web 🕸
skipped 🚫

🚀 Deployed to production by https://github.com/jasperhuangg in version: 1.3.83-11 🚀

platform
result

🤖 android 🤖
skipped 🚫

🖥 desktop 🖥
skipped 🚫

🍎 iOS 🍎
skipped 🚫

🕸 web 🕸
skipped 🚫

🚀 Deployed to production by https://github.com/jasperhuangg in version: 1.3.83-11 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/francoisl in version: 1.3.84-10 🚀

platform
result

🤖 android 🤖
skipped 🚫

🖥 desktop 🖥
skipped 🚫

🍎 iOS 🍎
skipped 🚫

🕸 web 🕸
skipped 🚫


Add fil pilote

Add ApplianceType mixin for legrand modules supporting it
Make rooms with NLC radiator supporting climate
Change async_therm_set to add fil pilote value

Any news on this request?

Let me know if I can help you.

This PR is still in draft state. Please set it as "ready for review" if you're happy your changes

Thanks but currently I can't test more as the current weather is quite hot and I can't turn on radiator 😉

@NatMarchand any progress ? It's starting to be cold again :)
I just recently switched from Zigbee2MQTT to Home+Control gateway for my radiators and was disapointed to see the HA Netatmo integration didn't allow to control them correctly.
I'd be happy to help if you can tell more about what's still preventing the PR to be ready, and how you test the changes in HA


hot reload

After reference to import xx form 'react-slick'. After modifying the code，webpack Automatic compilation have a problem. Cannot read property 'apply' of undefined, why?????

Could you please provide the whole snippet or link to the snippet that you're using?

react-router config + webpack :
export const routes = {   path: '/',   getComponent(nextState,cb){     require.ensure([],require=>{       cb(null,require('../views/home/App'));     },'app')   },   indexRoute: {   getComponent(nextState,cb){     require.ensure([],require=>{       cb(null,require('../views/home/Home'));     },'home')   } },
reference  react-slick
import Slider from 'react-slick'
If you don't introduce react-slick, compilation will not make a mistake，The component that the error directly causes the routing match is null

We can't invest time in reproducing this issue at the moment
Can you provide a repo replicating this issue and re-open it


Great app

Hi great app!
Can you please share the public apis you are using for the data, and if you know of other useful apis too?
Thanks

@shubhnik I created my own api - the relevant endpoints are:
https://vast-beach-43552.herokuapp.com/table
https://vast-beach-43552.herokuapp.com/topscorers
https://vast-beach-43552.herokuapp.com/topassists
https://vast-beach-43552.herokuapp.com/headlines
https://vast-beach-43552.herokuapp.com/teams
https://vast-beach-43552.herokuapp.com/prevGames/${team}
https://vast-beach-43552.herokuapp.com/nextGames/${team}

thanks for sharing the api realted info it will be helpful a lot


Remove irritating name

The name structure1 is always used, which can be very irritating.

Codecov Report

Merging #101 (f7edb4b) into master (bb7e404) will increase coverage by 0.02%.
The diff coverage is n/a.

:exclamation: Current head f7edb4b differs from pull request most recent head 24cceed. Consider uploading reports for the commit 24cceed to get more accurate results

Additional details and impacted files


feat(swagger-ts): support nullable types

Hi, this PR adds support for nullable: true annotations for types in swagger-ts plugin. The annotation seems to be supported but there's a bug that skips creation of union type.

@all-contributors please add @raveclassic for code

@stijnvanhulle I fixed the test but it seems there's a type issue somewhere in the internals, as TypeBuilder#getTypeFromSchema received undefined instead of object, I couldn't find the reason.

Hi @stijnvanhulle, it seems something is off with E2E tests. typecheck shows an error which I can't reproduce locally. The issue is on the line e2e/src/gen/mocks/databasesController/createDatabasesUpdateMaintenanceWindow.ts:56, and TS in the current E2E CI snapshot is unable to assign return type of createDatabaseMaintenanceWindow, which is DatabaseMaintenanceWindow (or {...} | null) to DatabasesUpdateMaintenanceWindowMutationRequest which is DatabaseMaintenanceWindow | null (or {...} | null | null). Essentially, there should be no error.

Hi, can you pull in the main in to your branch? There was an issue on a previous PR but it should be fixed now.


Use consistent names for issuing flags

Preview is available here:http://developers-pr76.previews.kube001.services.stellar-ops.com


Add keepalive config in bootstrap.yaml

As per title, this patch adds the keepalive configuration recommended by
https://www.envoyproxy.io/docs/envoy/latest/api-docs/xds_protocol.
Release Note
keepalive config for xDS is added in `kourier-bootstrap` by default.

For the context, downstream is seeing sporadic test failures (various tests, but similar symptoms), with ksvcs not becoming Ready due to Reason:Uninitialized Message:Waiting for load balancer to be ready. And config dumps showed that only one of the gateway pod had the updated config.

/cc @skonto @maschmid

@skonto @maschmid Is it not OK to merge this?

Hi, I want to test it with this exact bits first, I didn't get to it last week.

/lgtm


iOS Simulator Crashes on Launch with Storage Exception

After pulling from master, I could no longer build the osu!framework test suite in the iOS simulator due to the following exception.

After consulting with @smoogipoo, it appears this is a regression due to #3522. Reverting to a commit before that PR being merged fixes the issue.

@TimOliver are you going to look at a fix for this? is it just tests? does running on a device still work?

Just tested on my iPhone 11 Pro and can confirm the same crash happens.
Sure! I'll see if I can make a fix for this. :)

Only in tests, right?

Uh, as opposed to what else exactly? osu! itself?

The information you've given so far is ambiguous as to where this is occurring. The changes in the PR you point at basically should have no effect outside of the newly added tests (which understandably will fail on iOS).
I'm trying to attain whether this is an issue with standard runtime. My hypothesis is that it should not even affect framework visual tests, nor samplegame.


[nit][eytzinger] Fix example of eytzinger layout.

Looks like a typo because 18 is missing from the Eytzinger layout.

Thanks @ttsugriy — well spotted.

Thanks @ttsugriy — well spotted.

Thank you, @jorangreef! It's a pleasure to read your code - it's one of the cleanest examples of mechanical sympathy in action.


feat: added half second transition to ProgressBar

Added half second transition to ProgressBar
The old one had it and the new one doesn't. For shame...

📬Published Alpha Packages:@codecademy/brand-components@0.8.9-alpha.71747b.0@codecademy/gamut-templates@2.5.8-alpha.71747b.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://5e87ea40b02005f4c7db8c34--codecademy-styleguide.netlify.comDeploy Logs


[Feature request] ZeroWidth combined with Mangled

ZeroWidth is really interesting feature, the first time i see it, a lot of editor doesn't even show these characters.
But currently it using all default JS protected var (like if, for, of...) which look too suspicious because it should be syntax error.
I suggest if we combine it with something like mangled, the code looks more naturally, just like a normally minifed code, when looking through the codebase, it gonna be much less suspicious.
(I don't want it looks suspicious partly because I don't obfuscate whole codebase to avoid perf problem, i just obfuscate some important part, so I prefer to blend it in with other minified code)
Also, ZeroWidthMangled mode should also reduce file size compared to pure ZeroWidth I think.

#150
Same issue. I'm open to add a ZeroWidthMangled mode if you have an implementation. Just send it as a reply or create PR.


Stop using URI.encode since it is deprecated

It's deprecated since Ruby 1.9, and since 2.7 it will always print a warning regardless of the verbosity level.
It's a bit tricky to replace, as it's never clear what it's supposed to escape or not. There are several alternatives in the stdlib, but none does escape exactly what we want here, namely the PATH component of the URI.
So I added addressable as a dependency, it's a very popular gem, so most likely not really an extra dependency.

This is causing issues on storefronts, where strings that weren't previously escaped are now escaped but shouldn't be. The following snippet is pulled from mackweldon.com—notice how before this PR, the key wouldn't be escaped, and now it is, which breaks the client-side .replace JavaScript call a few lines below:
<script>
- var fileTemplate =  "//cdn.shopify.com/s/files/1/0078/6825/2273/files/%5BFILE_NAME%5D?v=0"
+ var fileTemplate =  "//cdn.shopify.com/s/files/1/0078/6825/2273/files/%5BFILE_NAME%5D?v=0"
  function fileUrlFor(assetName, assetExtension) {
    return fileTemplate.replace(
      "[FILE_NAME]",
      assetName + "." + assetExtension
    )
  }
</script>


training datasets

Hi, I met a problem when I run  python3 train.py --load /path/to/COCO-R101FPN-MaskRCNN-ScratchGN.npz. I use the datasets downloaded from the official website, the information shows that  training_set.txt  is missed , but I do not see anything  about training_set.txt from readme.md.Could you kindly tell me how to create training_set.txt?

Hi,
I think training_set.txt should have been part of the LaSOT download. I will attach it here as well.
training_set.txt

你好
我认为training_set.txt应该是LaSOT下载的一部分。我也会把它附在这里。
training_set.txt

I run python3 train.py --load /path/to/COCO-R101FPN-MaskRCNN-ScratchGN.npz.

Hi,
I think training_set.txt should have been part of the LaSOT download. I will attach it here as well.
training_set.txt

Hi,
I think training_set.txt should have been part of the LaSOT download. I will attach it here as well.
training_set.txt

I run python3 train.py --load /path/to/COCO-R101FPN-MaskRCNN-ScratchGN.npz. so train_txt should have been part of the imagenet vid download.I download ILSVRC2015 from the official website,could I use  train_*  in ImageSets that downloaded from  the official website ?eg .train_1.txt or train_10.txt

Thanks for your help ,but I met another problem.
I run python3 train.py --load /path/to/COCO-R101FPN-MaskRCNN-ScratchGN.npz.
Could you kindly provide the train.txt?

Hello, can you tell me where all the data sets can be downloaded? Is there Baidu Cloud or Google Cloud?

We don't provide the datasets ourselves, unfortunately you'll have to check the webpage of each dataset individually


Model can inject arbitrary HTML into my results page

The results table seems to deliberately inject text as HTML ...?
The model's output is arbitrary. I don't want the model to be able to inject random scripts into my results table. At best, this is annoying, and at worst, it's a security vuln.
IMO, input/output in the results page should be shown as plaintext.

Introduced in https://github.com/promptfoo/promptfoo/pull/55 - but not sure why

Thanks for pointing this out.  #309 should fix

Amazingly fast response! Thanks! ❤

No problem!  This fix was included in 0.30.0


[backport] Change 0 to 0.0 for python2

Backport of #7373

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit 7a10666a20b261a5aa5a6483dc9e0dcc8df66163, target branch v6) failed with status FAILURE.


Add a more informational README

Includes more information about where workflows live (specs/ directory)
Includes a workflow example directly within the README
Lists information about what makes a workflow

PTAL


Cache crashes under load (200+ rps)

Hello team!
My team has been using your caching solution and noticed that it tends to crash at around 200 requests per second. Do you have any suggestions for how we manage this or surpass this threshold?
For context, we used a locally running hardhat network for our RPC endpoint and a mix of rpc method calls to simulate typical load we expect for our service.
Reproduction steps
We have been using the following erpc.yaml and reproduction script
erpc.yaml
logLevel: debug
database:
  evmJsonRpcCache:
    driver: memory
    #driver: redis
    #redis:
    #  addr: 'http://<IP_ADDRESS>'
    #  port: 6379
server:
  httpHostV4: <IP_ADDRESS>
  httpPort: 4000
metrics:
  enabled: true
  hostV4: <IP_ADDRESS>
  port: 4001
projects:
  - id: main
    networks:
      - architecture: evm
        evm:
          chainId: 31337
        failsafe:
          timeout:
            duration: 30s
          retry:
            maxCount: 3
            delay: 500ms
            backoffMaxDelay: 10s
            backoffFactor: 0.3
            jitter: 500ms
          hedge:
            delay: 3000ms
            maxCount: 2
    upstreams:
      - id: optimism-sepolia-1
        endpoint: 'http://<IP_ADDRESS>:8545/'
        rateLimitBudget: default-budget
        failsafe:
          timeout:
            duration: 15s
          retry:
            maxCount: 2
            delay: 1000ms
            backoffMaxDelay: 10s
            backoffFactor: 0.3
            jitter: 500ms
rateLimiters:
  budgets:
    - id: default-budget
      rules:
        - method: '*'
          maxCount: 10000
          period: 1s
    - id: global-blast
      rules:
        - method: '*'
          maxCount: 1000
          period: 1s
    - id: global-quicknode
      rules:
        - method: '*'
          maxCount: 300
          period: 1s

reproduction script
#!/bin/bash

function queryBlock() {
    local i=$1
    printf "[{ \"id\": %s, \"jsonrpc\": \"2.0\", \"method\": \"eth_getBlockByNumber\", \"params\": [\"latest\", false]}]" $i
}

function queryBlockNumber() {
    local i=$1
    printf "[{ \"id\": %s, \"jsonrpc\": \"2.0\", \"method\": \"eth_blockNumber\", \"params\": []}]" $i
}

function queryChainId() {
    local i=$1
    printf "[{ \"id\": %s, \"jsonrpc\": \"2.0\", \"method\": \"eth_chainId\", \"params\": []}]" $i
}

function query() {
    local i=$RANDOM
    local random_query=$(($i%3))
    local method="foo"
    case $random_query in
    0)
        method="eth_getBlockByNumber"
        query=$(queryBlock $i);;
    1)
        method="eth_chainId"
        query=$(queryChainId $i);;
    2)
        method="eth_blockNumber"
        query=$(queryBlockNumber $i);;
    *)
        echo "Invalid selection";;
    esac

    #echo $query
    echo "$method: $i"
    local j=$(curl -so - --request POST  http://localhost:4000/main/evm/31337 --header 'accept: application/json' --header 'content-type: application/json' --data "$query" | jq .[].id)
    echo "expected $i, got $j for $method"

}

for i in $(seq 1 200); do
    query &
done

wait

Thanks for sharing the reproduction code.
There are few memory improvements that we're working on which is the reason of these crashes (looks like it originates from one of libraries, or how we use it). Will ping you here when I pushed the changes.
In your logs, do you see the reason of those crashes? It would be helpful to have the stack traces.
When this memory regressions are solved you should be able to get 15k rps with 8 cpu and 8 gb ram

I have attached my most recent run of the reproduction script which includes the stack trace. The fatal error is as follows:
fatal error: concurrent map read and map write{"level":"info","project":"main","method":"eth_getBlockByNumber","id":"20346.000000","ptr":"0xc000ba0510","time":"2024-09-10T10:17:25-04:00","message":"successfully forwarded request for network"}
This occurs on line 623 of the attached file.
erpc-output.txt

Thanks @OBlackmon3 for sharing this output, looking at this specific error looks like this is what I already tried to solve in 0.0.22
Can you try with the latest (0.0.23) and see if you still face this one? The high memory usage might still be there, but the concurrent map race condition must be solved already 👌

I have tried this out locally and there is a very significant improvement in throughput and no crashes. I am going to try this in our development environment and report back. Thank you


chore(main): release 0.1.10

:robot: I have created a release beep boop
0.1.10 (2024-09-04)
Other

bump oci and network plugin versions (#411) (8fc8616)

Dependency Updates

deps: update module github.com/onsi/ginkgo/v2 to v2.20.2 (#407) (a9f8f6b)
deps: update module github.com/onsi/gomega to v1.34.2 (#408) (3043175)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.1.10
:sunflower:


Lazier cmake exclusion handling

With fixed auto-test.

Pull Request Test Coverage Report for Build 301

0 of 25 (0.0%)  changed or added relevant lines in 1 file are covered.
62 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-12.3%) to 56.239%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

cmake-ide.el
0
25
0.0%

Files with Coverage Reduction
New Missed Lines
%

cmake-ide.el
62
56.78%

Totals

Change from base Build 299:
-12.3%

Covered Lines:
311

Relevant Lines:
553

💛  - Coveralls


add missing inject

amazing, thanks for sending this PR, @felipeweb!
Could you just fix the indentation to use tabs instead of spaces?

done!! sorry about my indent.

great! thank you again, Felipe!


Add a fallback implementation of getrandom for unsupported targets

I'm trying to compile all the programs using cargo-build-bpf.
I think it won't compile because this repo depends on solana modules, which in turn, don't support getrandom.
This is discussed in the docs here: https://docs.solana.com/developing/on-chain-programs/developing-rust#depending-on-rand
The solution is usually to add to the Cargo.toml
getrandom = { version = "0.1.14", features = ["dummy"] } or getrandom = { version = "0.2.2", features = ["custom"] }
However no package in this module depends directly on getrandom so it's unclear at a glance which Cargo.toml need to have the workaround added, and which version of getrandom to use.
More investigation needed.

In your project, after the initial build, there should be a Cargo.lock file which defines all of the crates included in your build.  From there, you can see which version of getrandom is being used, along with the chain of dependencies, so you can either remove dependencies that transitively depend on getrandom or add either version as needed.
Adding a fallback implementation of getrandom on the BPF side could be dangerous, since it could lead people to wrongly assume that they have randomness. By specifying the dependency in your program explicitly, it's totally clear.
Either way, if you have more questions about this, it's best to ask in the Solana Stack Exchange https://solana.stackexchange.com/


Add API docs for commands API

Forgot to add this when I added the functionality a few months ago.

Ah no, there's a mistake in this.

Ok, I have removed the info about the runAsUser command on the Commands API because I realised it doesn't even work right now, and even if it did, it's kinda pointless because you need to pass through the client, which if you had you could just call runAsUser on the client itself.
So I'm going to fix that in another thing and then put the docs up for it.

Can you add explanation for what the callback arguments are? function(client, target, command, args)

Done. I also added docs for the client object as a separate page, because:

It'll get too messy if that's in the same page
I'm sure we'll use client elsewhere as well

I merged #220, can you review this PR please.


Linking errors and warnings lead to failure in generating shared library

I followed the timeloop tutorial to install it, and then followed the timeloop-python Installing, but pip3 install -e. The following error message is returned.
(base) root@2b5da774569c:/home/workspace/gamma/accelergy-timeloop-infrastructure/src/timeloop-python# pip3 install .
Processing /home/workspace/gamma/accelergy-timeloop-infrastructure/src/timeloop-python
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Requirement already satisfied: pyyaml in /root/miniforge-pypy3/lib/python3.9/site-packages (from pytimeloop==0.0.1) (6.0.1)
Building wheels for collected packages: pytimeloop
  Building wheel for pytimeloop (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Building wheel for pytimeloop (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [150 lines of output]
      running bdist_wheel
      running build
      running build_py
      creating build
      creating build/lib.linux-x86_64-pypy39
      creating build/lib.linux-x86_64-pypy39/pytimeloop
      copying pytimeloop/__init__.py -> build/lib.linux-x86_64-pypy39/pytimeloop
      copying pytimeloop/accelergy_interface.py -> build/lib.linux-x86_64-pypy39/pytimeloop
      copying pytimeloop/config.py -> build/lib.linux-x86_64-pypy39/pytimeloop
      copying pytimeloop/engine.py -> build/lib.linux-x86_64-pypy39/pytimeloop
      copying pytimeloop/mapper.py -> build/lib.linux-x86_64-pypy39/pytimeloop
      copying pytimeloop/mapping.py -> build/lib.linux-x86_64-pypy39/pytimeloop
      copying pytimeloop/mapspace.py -> build/lib.linux-x86_64-pypy39/pytimeloop
      copying pytimeloop/model.py -> build/lib.linux-x86_64-pypy39/pytimeloop
      copying pytimeloop/problem.py -> build/lib.linux-x86_64-pypy39/pytimeloop
      copying pytimeloop/search.py -> build/lib.linux-x86_64-pypy39/pytimeloop
      creating build/lib.linux-x86_64-pypy39/tests
      copying tests/__init__.py -> build/lib.linux-x86_64-pypy39/tests
      copying tests/test_accelerator.py -> build/lib.linux-x86_64-pypy39/tests
      copying tests/test_buffer.py -> build/lib.linux-x86_64-pypy39/tests
      copying tests/test_config.py -> build/lib.linux-x86_64-pypy39/tests
      copying tests/test_mapper.py -> build/lib.linux-x86_64-pypy39/tests
      copying tests/test_model.py -> build/lib.linux-x86_64-pypy39/tests
      copying tests/test_topology.py -> build/lib.linux-x86_64-pypy39/tests
      copying tests/util.py -> build/lib.linux-x86_64-pypy39/tests
      creating build/lib.linux-x86_64-pypy39/pytimeloop/app
      copying pytimeloop/app/__init__.py -> build/lib.linux-x86_64-pypy39/pytimeloop/app
      copying pytimeloop/app/call_utils.py -> build/lib.linux-x86_64-pypy39/pytimeloop/app
      copying pytimeloop/app/mapper.py -> build/lib.linux-x86_64-pypy39/pytimeloop/app
      copying pytimeloop/app/model.py -> build/lib.linux-x86_64-pypy39/pytimeloop/app
      creating build/lib.linux-x86_64-pypy39/tests/demo
      copying tests/demo/__init__.py -> build/lib.linux-x86_64-pypy39/tests/demo
      copying tests/demo/demo.py -> build/lib.linux-x86_64-pypy39/tests/demo
      running build_ext
      CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required):
        Compatibility with CMake < 3.5 will be removed from a future version of
        CMake.

        Update the VERSION argument <min> value or use a ...<max> suffix to tell
        CMake that the project does not need compatibility with older versions.

      -- The C compiler identification is GNU 11.4.0
      -- The CXX compiler identification is GNU 11.4.0
      -- Detecting C compiler ABI info
      -- Detecting C compiler ABI info - done
      -- Check for working C compiler: /usr/bin/cc - skipped
      -- Detecting C compile features
      -- Detecting C compile features - done
      -- Detecting CXX compiler ABI info
      -- Detecting CXX compiler ABI info - done
      -- Check for working CXX compiler: /usr/bin/c++ - skipped
      -- Detecting CXX compile features
      -- Detecting CXX compile features - done
      -- Using timeloop includes from: /home/workspace/gamma/accelergy-timeloop-infrastructure/src/timeloop/include
      -- Performing Test CMAKE_HAVE_LIBC_PTHREAD
      -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
      -- Found Threads: TRUE
      -- pybind11 v2.13.0 dev1
      -- Found PythonInterp: /root/miniforge-pypy3/bin/python3.9 (found suitable version "3.9.18", minimum required is "3.6")
      -- Found PythonLibs: python3.9
      -- Performing Test HAS_FLTO
      -- Performing Test HAS_FLTO - Success
      -- Configuring done (0.9s)
      -- Generating done (0.0s)
      -- Build files have been written to: /home/workspace/gamma/accelergy-timeloop-infrastructure/src/timeloop-python/build/temp.linux-x86_64-pypy39
      [  3%] Building CXX object CMakeFiles/define_gterminate.dir/bindings/gterminate.cpp.o
      [  7%] Linking CXX static library libdefine_gterminate.a
      [  7%] Built target define_gterminate
      [ 10%] Building CXX object CMakeFiles/pytimeloop.dir/src/mapper/coupled-mapper.cpp.o
      [ 14%] Building CXX object CMakeFiles/pytimeloop.dir/src/mapspace/status.cpp.o
      [ 17%] Building CXX object CMakeFiles/pytimeloop.dir/src/model/accelerator.cpp.o
      [ 21%] Building CXX object CMakeFiles/pytimeloop.dir/src/model/bounded-queue-accelerator-pool.cpp.o
      [ 25%] Building CXX object CMakeFiles/pytimeloop.dir/src/model/unbounded-queue-accelerator-pool.cpp.o
      [ 28%] Building CXX object CMakeFiles/pytimeloop.dir/src/model/util.cpp.o
      [ 32%] Linking CXX shared library /home/workspace/gamma/accelergy-timeloop-infrastructure/src/timeloop-python/build/lib.linux-x86_64-pypy39/libpytimeloop.so
      lto-wrapper: warning: using serial compilation of 39 LTRANS jobs
      ../../../timeloop/src/loop-analysis/mapping-to-isl/mapping-to-isl.cpp: In function 'LogicalBufSkewsFromMapping':
      ../../../timeloop/src/loop-analysis/mapping-to-isl/mapping-to-isl.cpp:284:34: warning: 'MEM[(const int &)&last_y_idx_opt]' may be used uninitialized in this function [-Wmaybe-uninitialized]
        284 |       for (int i = last_y_idx; i < loop_idx; ++i)
            |                                  ^
      ../../../timeloop/src/loop-analysis/mapping-to-isl/mapping-to-isl.cpp:174:22: note: 'MEM[(const int &)&last_y_idx_opt]' was declared here
        174 |   std::optional<int> last_y_idx_opt = std::nullopt;
            |                      ^
      ../../../timeloop/src/loop-analysis/mapping-to-isl/mapping-to-isl.cpp:246:7: warning: 'MEM[(const int &)&last_x_idx_opt]' may be used uninitialized in this function [-Wmaybe-uninitialized]
        246 |       for (auto i = last_x_idx; i < loop_idx; ++i)
            |       ^
      ../../../timeloop/src/loop-analysis/mapping-to-isl/mapping-to-isl.cpp:173:22: note: 'MEM[(const int &)&last_x_idx_opt]' was declared here
        173 |   std::optional<int> last_x_idx_opt = std::nullopt;
            |                      ^
      /usr/bin/ld: /tmp/cchzahKo.ltrans30.ltrans.o: relocation R_X86_64_TPOFF32 against symbol `gCtx' can not be used when making a shared object; recompile with -fPIC
      /usr/bin/ld: failed to set dynamic section sizes: bad value
      collect2: error: ld returned 1 exit status
      gmake[2]: *** [CMakeFiles/pytimeloop.dir/build.make:179: /home/workspace/gamma/accelergy-timeloop-infrastructure/src/timeloop-python/build/lib.linux-x86_64-pypy39/libpytimeloop.so] Error 1
      gmake[1]: *** [CMakeFiles/Makefile2:130: CMakeFiles/pytimeloop.dir/all] Error 2
      gmake: *** [Makefile:91: all] Error 2
      Traceback (most recent call last):
        File "/root/miniforge-pypy3/lib/pypy3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
          main()
        File "/root/miniforge-pypy3/lib/pypy3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
        File "/root/miniforge-pypy3/lib/pypy3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 251, in build_wheel
          return _build_backend().build_wheel(wheel_directory, config_settings,
        File "/tmp/pip-build-env-8c1iw72k/overlay/lib/pypy3.9/site-packages/setuptools/build_meta.py", line 410, in build_wheel
          return self._build_with_temp_dir(
        File "/tmp/pip-build-env-8c1iw72k/overlay/lib/pypy3.9/site-packages/setuptools/build_meta.py", line 395, in _build_with_temp_dir
          self.run_setup()
        File "/tmp/pip-build-env-8c1iw72k/overlay/lib/pypy3.9/site-packages/setuptools/build_meta.py", line 311, in run_setup
          exec(code, locals())
        File "<string>", line 97, in <module>
        File "/tmp/pip-build-env-8c1iw72k/overlay/lib/pypy3.9/site-packages/setuptools/__init__.py", line 104, in setup
          return distutils.core.setup(**attrs)
        File "/tmp/pip-build-env-8c1iw72k/overlay/lib/pypy3.9/site-packages/setuptools/_distutils/core.py", line 184, in setup
          return run_commands(dist)
        File "/tmp/pip-build-env-8c1iw72k/overlay/lib/pypy3.9/site-packages/setuptools/_distutils/core.py", line 200, in run_commands
          dist.run_commands()
        File "/tmp/pip-build-env-8c1iw72k/overlay/lib/pypy3.9/site-packages/setuptools/_distutils/dist.py", line 969, in run_commands
          self.run_command(cmd)
        File "/tmp/pip-build-env-8c1iw72k/overlay/lib/pypy3.9/site-packages/setuptools/dist.py", line 967, in run_command
          super().run_command(command)
        File "/tmp/pip-build-env-8c1iw72k/overlay/lib/pypy3.9/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/tmp/pip-build-env-8c1iw72k/overlay/lib/pypy3.9/site-packages/wheel/bdist_wheel.py", line 368, in run
          self.run_command("build")
        File "/tmp/pip-build-env-8c1iw72k/overlay/lib/pypy3.9/site-packages/setuptools/_distutils/cmd.py", line 316, in run_command
          self.distribution.run_command(command)
        File "/tmp/pip-build-env-8c1iw72k/overlay/lib/pypy3.9/site-packages/setuptools/dist.py", line 967, in run_command
          super().run_command(command)
        File "/tmp/pip-build-env-8c1iw72k/overlay/lib/pypy3.9/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/tmp/pip-build-env-8c1iw72k/overlay/lib/pypy3.9/site-packages/setuptools/_distutils/command/build.py", line 132, in run
          self.run_command(cmd_name)
        File "/tmp/pip-build-env-8c1iw72k/overlay/lib/pypy3.9/site-packages/setuptools/_distutils/cmd.py", line 316, in run_command
          self.distribution.run_command(command)
        File "/tmp/pip-build-env-8c1iw72k/overlay/lib/pypy3.9/site-packages/setuptools/dist.py", line 967, in run_command
          super().run_command(command)
        File "/tmp/pip-build-env-8c1iw72k/overlay/lib/pypy3.9/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/tmp/pip-build-env-8c1iw72k/overlay/lib/pypy3.9/site-packages/setuptools/command/build_ext.py", line 91, in run
          _build_ext.run(self)
        File "/tmp/pip-build-env-8c1iw72k/overlay/lib/pypy3.9/site-packages/setuptools/_distutils/command/build_ext.py", line 359, in run
          self.build_extensions()
        File "/tmp/pip-build-env-8c1iw72k/overlay/lib/pypy3.9/site-packages/setuptools/_distutils/command/build_ext.py", line 479, in build_extensions
          self._build_extensions_serial()
        File "/tmp/pip-build-env-8c1iw72k/overlay/lib/pypy3.9/site-packages/setuptools/_distutils/command/build_ext.py", line 505, in _build_extensions_serial
          self.build_extension(ext)
        File "<string>", line 91, in build_extension
        File "/root/miniforge-pypy3/lib/pypy3.9/subprocess.py", line 373, in check_call
          raise CalledProcessError(retcode, cmd)
      subprocess.CalledProcessError: Command '['cmake', '--build', '.']' returned non-zero exit status 2.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for pytimeloop
Failed to build pytimeloop
ERROR: Could not build wheels for pytimeloop, which is required to install pyproject.toml-based projects

Thank you for your assistance!

I haven't seen this error before, but it seems like the timeloop libraries are built without PIC and that is causing the issue. Would you mind providing some information about how you built timeloop? E.g., what commands did you call to build timeloop.

Hi,
I apologize for the disturbance, but I am also encountering the same issue after pulling the most recent version of the Accelergy-Timeloop Infrastructure.
I built the infrastructure as explained in: https://timeloop.csail.mit.edu/v4/installation
Subsequently I proceeded to install pytimeloop as per its README: https://github.com/Accelergy-Project/timeloop-python/blob/main/README.md
As a result, the same error as above occurs.
I managed to work around the issue somewhat by modifying Timeloop's SConstruct as follows:
# ...
env = Environment(ENV = os.environ)

if not GetOption('clang'):
    env.Append(CCFLAGS=['-fPIC'])
#...

And after re-building Timeloop, I got a different error while running pip3 install -e . for pytimeloop:
# ...
    [ 46%] Building CXX object CMakeFiles/bindings.dir/src/model/bounded-queue-accelerator-pool.cpp.o
    [ 50%] Building CXX object CMakeFiles/bindings.dir/src/model/unbounded-queue-accelerator-pool.cpp.o
    [ 53%] Building CXX object CMakeFiles/bindings.dir/src/model/util.cpp.o
    [ 56%] Building CXX object CMakeFiles/bindings.dir/bindings/accelergy_interface.cpp.o
    [ 60%] Building CXX object CMakeFiles/bindings.dir/bindings/applications.cpp.o
    [ 63%] Building CXX object CMakeFiles/bindings.dir/bindings/bindings.cpp.o
    [ 66%] Building CXX object CMakeFiles/bindings.dir/bindings/buffer.cpp.o
    [ 70%] Building CXX object CMakeFiles/bindings.dir/bindings/config.cpp.o
    [ 73%] Building CXX object CMakeFiles/bindings.dir/bindings/looptree.cpp.o
    /home/zero/Desktop/Timeloop/accelergy-timeloop-infrastructure/src/timeloop-python/bindings/looptree.cpp: In function ‘void pytimeloop::looptree_bindings::BindLooptree(pybind11::module&)’:
    /home/zero/Desktop/Timeloop/accelergy-timeloop-infrastructure/src/timeloop-python/bindings/looptree.cpp:14:16: error: ‘application’ was not declared in this scope; did you mean ‘Application’?
       14 |     py::class_<application::LooptreeModel>(m, "LooptreeModelApp")
          |                ^~~~~~~~~~~
          |                Application
    /home/zero/Desktop/Timeloop/accelergy-timeloop-infrastructure/src/timeloop-python/bindings/looptree.cpp:14:42: error: template argument 1 is invalid
       14 |     py::class_<application::LooptreeModel>(m, "LooptreeModelApp")
          |                                          ^
    /home/zero/Desktop/Timeloop/accelergy-timeloop-infrastructure/src/timeloop-python/bindings/looptree.cpp:18:32: error: ‘application’ is not a class, namespace, or enumeration
       18 |         .def_readwrite("ops", &application::LooptreeModel::Result::ops)
          |                                ^~~~~~~~~~~
    /home/zero/Desktop/Timeloop/accelergy-timeloop-infrastructure/src/timeloop-python/bindings/looptree.cpp:19:33: error: ‘application’ is not a class, namespace, or enumeration
       19 |         .def_readwrite("fill", &application::LooptreeModel::Result::fill)
          |                                 ^~~~~~~~~~~
    /home/zero/Desktop/Timeloop/accelergy-timeloop-infrastructure/src/timeloop-python/bindings/looptree.cpp:20:38: error: ‘application’ is not a class, namespace, or enumeration
       20 |         .def_readwrite("occupancy", &application::LooptreeModel::Result::occupancy);
          |                                      ^~~~~~~~~~~
    gmake[2]: *** [CMakeFiles/bindings.dir/build.make:244: CMakeFiles/bindings.dir/bindings/looptree.cpp.o] Error 1
    gmake[1]: *** [CMakeFiles/Makefile2:156: CMakeFiles/bindings.dir/all] Error 2
    gmake: *** [Makefile:91: all] Error 2
    Traceback (most recent call last):
      File "<string>", line 2, in <module>
      File "<pip-setuptools-caller>", line 34, in <module>
      File "/home/zero/Desktop/Timeloop/accelergy-timeloop-infrastructure/src/timeloop-python/setup.py", line 97, in <module>
        setup(
      File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 153, in setup
        return distutils.core.setup(**attrs)
      File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 148, in setup
        return run_commands(dist)
      File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 163, in run_commands
        dist.run_commands()
      File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 967, in run_commands
        self.run_command(cmd)
      File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 986, in run_command
        cmd_obj.run()
      File "/usr/lib/python3/dist-packages/setuptools/command/develop.py", line 34, in run
        self.install_for_development()
      File "/usr/lib/python3/dist-packages/setuptools/command/develop.py", line 114, in install_for_development
        self.run_command('build_ext')
      File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 313, in run_command
        self.distribution.run_command(command)
      File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 986, in run_command
        cmd_obj.run()
      File "/usr/lib/python3/dist-packages/setuptools/command/build_ext.py", line 79, in run
        _build_ext.run(self)
      File "/usr/lib/python3/dist-packages/setuptools/_distutils/command/build_ext.py", line 339, in run
        self.build_extensions()
      File "/usr/lib/python3/dist-packages/setuptools/_distutils/command/build_ext.py", line 448, in build_extensions
        self._build_extensions_serial()
      File "/usr/lib/python3/dist-packages/setuptools/_distutils/command/build_ext.py", line 473, in _build_extensions_serial
        self.build_extension(ext)
      File "/home/zero/Desktop/Timeloop/accelergy-timeloop-infrastructure/src/timeloop-python/setup.py", line 91, in build_extension
        subprocess.check_call(
      File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
        raise CalledProcessError(retcode, cmd)
    subprocess.CalledProcessError: Command '['cmake', '--build', '.']' returned non-zero exit status 2.
    [end of output]

To solve this error, I temporarily rolled back the last commit of pytimeloop, going from 54cdc1e50a1d0b34dedd3c39f1c649e14f983253 to 95e4a731d7e518ea16a59ed217fbac5330a6b777.
After this, I have been able to successfully run pip3 install -e . for pytimeloop.
However, once I try to import it, I get the following error:
Python 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import pytimeloop
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/zero/Desktop/Timeloop/accelergy-timeloop-infrastructure/src/timeloop-python/pytimeloop/init.py", line 1, in <module>
    from bindings import *
ImportError: /home/zero/Desktop/Timeloop/accelergy-timeloop-infrastructure/src/timeloop-python/bindings.cpython-310-x86_64-linux-gnu.so: undefined symbol: _ZTIN5boost13serialization13typeid_system27extended_type_info_typeid_0E

I don't know if the steps I took were meaningful in fixing the problem.
If there is any further information that you think could be of help, I will promptly to provide it.
Thank you in advance.

On a side note, I also tried to use pytimeloop within the Docker container mentioned in the documentation, however I cannot successfully pytimeloop there too, with the following error (on a freshly created container):
workspace@accelergy-timeloop:~$ python3
Python 3.8.10 (default, Nov 22 2023, 10:22:35)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import pytimeloop
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python3.8/dist-packages/pytimeloop/init.py", line 1, in <module>
    from bindings import *
ImportError: libbarvinok.so.23: cannot open shared object file: No such file or directory


How does the method "placemarkFromCoordinates" & "placemarkFromAddress" internally works?

As per my understanding, usually we have Google APIs to get the location information based on coordinates or address. So, how does this library gets the information without API? Or, it internally uses any API?
This is just a question which might have a very simple answer and I am just looking for that :)
Thanks in advance,

Hi @bajajsahil,
That is here not any different. The geocoding features use the default APIs on the device to handle the translation.
This mean on iOS the plugin uses the CLGeocoder SDK, which internally makes a call to the Apple Maps API. On Android the plugin uses the Android Geocoder class (part of the Google Play Services), which internally makes use of the Google Maps API.
These APIs are free to use but have limitations to there use. Both are rate limited which means you can only do a x amount of request in a certain time period, when you do more you will receive an error. I don’t know the exact values since Apple and Google are not very clear about them in their documentation.
Hope this answers helps. More information can be found when searching the Net for those SDKs I mentioned.

Hi @mvanbeusekom,
Thanks for the answer. Appreciate it.
One suggestion though, it would be really helpful if you put this information in plugin readme so that people can handle the error gracefully if the quota exceeds. I think many of us aren't aware of this.
Also, if I or someone found the exact quota limit then it will be good to share with everyone.
Thanks.


Folder is displayed as empty when clicked from search results

Describe the bug
Folder is displayed as empty when clicked from search results.
Expected behavior
The folder should display the three files shown in the video below.
To Reproduce
I used the JupyterLab GitHub repository and searched path:packages/console/style.
Screenshots or output
https://github.com/BloopAI/bloop/assets/36907905/91e3ac65-3636-4f3c-8e02-ab8310571fe7

Can you link the GitHub repository that you have indexed?

Can you please confirm if your host platform is Windows? I notice the \ at the end of your prompt in the video. If that's the case, this is probably a Windows-specific thing.

Yes I am on Windows. Here is the repository https://github.com/jupyterlab/jupyterlab.


tag v0.12.5

Purpose
Update release to v0.12.5

Is there a way to restart buildkite manually? (without pushing a commit)