Form Submit functionality issue. Should be a simple fix.  : )

Hello and thank you for the wonderful application!
I've set this up with formspree.io to receive automatic emails with the form data. However, I'm only able to submit the form correctly when typing and sending an additional message after all the fieldsets are completed. I basically just need to understand how to correctly submit the form, and then afterward give some conclusion text to the user. I tried to replicate the example in the appearance section, but no luck.
Everything else is working great!
Here's the Wordpress page with the code.
v 0.9.71
Chrome 64
Please forgive me if this is in the documentation--I couldn't find it.
Thank you very much!

Anyone able to help? Thanks much. : )

Hi @dolanb12. Great that you are using Conversational Form. A few ideas to can improve your implementation.

Using an AJAX request to submit data to formspring so the user is not redirected. This requires that you use a custom submit callback and here is someones method for posting to formspring
The last 3 messages can be implemented using cf-robot-message-tag. This is new in 0.9.80 and heres a link to the documentation.

Saw the close, but wanted to give a late thank you for the help!
Formspree decided to block AJAX callbacks last month, but I can still redirect users to a confirmation page.
=)

@dolanb12 you are welcome. Yeah, I think you have to be a premium subscriber of Formspree now to take advantage of AJAX requests. Glad it worked out though.


Questions Regarding Baidu Embeddings

Hi Silvio, I have some questions about the baidu emdeddings, I wonder if you have any information about them. I couldn't find any information regarding these questions from either of their github repo or the published paper:

Is the baidu embeddings already gone through PCA, or was it still a "raw" features? I noticed it's in Tx8576 dimension, which could probably mean they are still "raw", am I right about this?
In your opinion, if I were to reduce the dimension, would it be better to have PCA reduce them, or have them go through a FCL like in the implementation of TemporallyAwarePooling? https://github.com/SilvioGiancola/SoccerNetv2-DevKit/blob/20f2f74007c82b68a73c519dff852188df4a8b5a/Task1-ActionSpotting/TemporallyAwarePooling/src/model.py#L32
If they are still raw, do you have any idea what was the initial dimension before they are flatten to 8576? They used 398x224 video as mentioned in the paper, but it's not possible to reshape them to it. I was thinking maybe I could used them in video transformer based architecture (MViT etc) if I'm able to reshape them to the original dimension.
Do we have any of their fine-tuned feature extraction code publicly available? I think not, but I'm just going to ask anyway in case you know any since their embeddings have very few public information available.

Thanks!

I found a closed issue on their repo, it might have answered some of the questions, but looks like they're not planning on releasing the code publicly (at least from a comment dated a year ago), unfortunately.
https://github.com/baidu-research/vidpress-sports/issues/4#issuecomment-941297411

That's a pity, but I am sure fine-tuning even simple encoders like ResNET or an MViT using a similar trick would lead to very similar boost in performances. If you have reproducible code that train a better encoder, I would be happy to advertise it on our soccer-net github repos and websites, as it could very useful for future development.


callback_duration.ipynb works but lifecycle_states.ipynb and memory_usage.ipynb fails

With the following setting, callback_duration.ipynb works but lifecycle_states.ipynb and memory_usage.ipynb
    # Set up the Trace action with a session name that uniquely includes a timestamp
    ros2_tracing = Trace(
        condition=IfCondition(enable_tracing),
        session_name=f'ros_tracing_navigation_session_{timestamp}',
        events_kernel=[],
        events_ust=['ros2:*'],  # Tracks all user-space ROS 2 events
    )

The errors of lifecycle_states.ipynb are as below:
data_util = Ros2DataModelUtil(handler.data)

state_intervals = data_util.get_lifecycle_node_state_intervals()
for handle, states in state_intervals.items():
    print(handle)
    print(states.to_string())

output_notebook()
psize = 450

---------------------------------------------------------------------------
KeyError                                  Traceback (most recent call last)
File /usr/local/lib/python3.10/dist-packages/pandas/core/indexes/base.py:3805, in Index.get_loc(self, key)
   3804 try:
-> 3805     return self._engine.get_loc(casted_key)
   3806 except KeyError as err:

File index.pyx:167, in pandas._libs.index.IndexEngine.get_loc()

File index.pyx:196, in pandas._libs.index.IndexEngine.get_loc()

File pandas/_libs/hashtable_class_helper.pxi:2606, in pandas._libs.hashtable.Int64HashTable.get_item()

File pandas/_libs/hashtable_class_helper.pxi:2630, in pandas._libs.hashtable.Int64HashTable.get_item()

KeyError: 0

The above exception was the direct cause of the following exception:

KeyError                                  Traceback (most recent call last)
Cell In[5], line 3
      1 data_util = Ros2DataModelUtil(handler.data)
----> 3 state_intervals = data_util.get_lifecycle_node_state_intervals()
      4 for handle, states in state_intervals.items():
      5     print(handle)

File ~/src/ag_navigation/amr_navigation/external/tracetools_analysis/tracetools_analysis/analysis/../tracetools_analysis/utils/ros2.py:540, in Ros2DataModelUtil.get_lifecycle_node_state_intervals(self)
    536 node_creation_timestamp = self.data.nodes.loc[lifecycle_node_handle, 'timestamp']
    538 # Add initial and final timestamps
    539 # Last states has an unknown end timestamp
--> 540 first_state_label = transitions.loc[0, 'start_label']
    541 last_state_label = transitions.loc[transitions.index[-1], 'goal_label']
    542 transitions.loc[-1] = ['', first_state_label, node_creation_timestamp]

File /usr/local/lib/python3.10/dist-packages/pandas/core/indexing.py:1183, in _LocationIndexer.__getitem__(self, key)
   1181     key = tuple(com.apply_if_callable(x, self.obj) for x in key)
   1182     if self._is_scalar_access(key):
-> 1183         return self.obj._get_value(*key, takeable=self._takeable)
   1184     return self._getitem_tuple(key)
   1185 else:
   1186     # we by definition only have the 0th axis

File /usr/local/lib/python3.10/dist-packages/pandas/core/frame.py:4221, in DataFrame._get_value(self, index, col, takeable)
   4215 engine = self.index._engine
   4217 if not isinstance(self.index, MultiIndex):
   4218     # CategoricalIndex: Trying to use the engine fastpath may give incorrect
   4219     #  results if our categories are integers that dont match our codes
   4220     # IntervalIndex: IntervalTree has no get_loc
-> 4221     row = self.index.get_loc(index)
   4222     return series._values[row]
   4224 # For MultiIndex going through engine effectively restricts us to
   4225 #  same-length tuples; see test_get_set_value_no_partial_indexing

File /usr/local/lib/python3.10/dist-packages/pandas/core/indexes/base.py:3812, in Index.get_loc(self, key)
   3807     if isinstance(casted_key, slice) or (
   3808         isinstance(casted_key, abc.Iterable)
   3809         and any(isinstance(x, slice) for x in casted_key)
   3810     ):
   3811         raise InvalidIndexError(key)
-> 3812     raise KeyError(key) from err
   3813 except TypeError:
   3814     # If we have a listlike key, _check_indexing_error will raise
   3815     #  InvalidIndexError. Otherwise we fall through and re-raise
   3816     #  the TypeError.
   3817     self._check_indexing_error(key)

KeyError: 0

Can you share the trace that results in this error? I can try reproducing this when I get some time, but having the trace would be ideal.

I think your trace might just not contain any lifecycle transitions. In that case, get_lifecycle_node_state_intervals() should just return an empty dict instead of raising an error. I've fixed this in #28.
I'll close this, but feel free to open it if it still doesn't work.


SPIR-V module segfaults spirv-opt -O

segfault.asm.txt
Commit: Current master as of this time.

I believe I have fixed this with #1406.

Confirmed fixed.


Embedding 157 only has 989 elements in it.

All embeddings_x.json files should have 1000 elements in them except for the last one. embeddings_157.json only has 989.

Further work needs to be done to identify whether there is missing data and if so - which elements.


⚠ Bofrost.lu has degraded performance

In 4433628, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1755 ms

Resolved: Bofrost.lu performance has improved in 8de440a after 23 minutes.


Camera keeps crashing after recording is finished with image_picker

As the title says, image_picker crashes after recording a video. The issue is very similar to #84540. The error is reproduced with the example app as well. Picking images work, and picking videos from the gallery works as well. There is no debug output, the camera app just crashes and returns me to the app. After the second try Android will give me an error message saying "Camera keeps stopping."
flutter doctor -v
[✓] Flutter (Channel stable, 3.7.1, on Microsoft Windows [Version 10.0.22621.1265], locale en-US)
    • Flutter version 3.7.1 on channel stable at <path>\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 7048ed95a5 (4 weeks ago), 2023-02-01 09:07:31 -0800
    • Engine revision 800594f1f4
    • Dart version 2.19.1
    • DevTools version 2.20.1

[✓] Windows Version (Installed version of Windows is version 10 or higher)

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    • Android SDK at <path>\Local\Android\sdk
    • Platform android-33, build-tools 33.0.1
    • Java binary at: <path>\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-9505619)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[✓] Visual Studio - develop for Windows (Visual Studio Build Tools 2019 16.11.8)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools
    • Visual Studio Build Tools 2019 version 16.11.32002.261
    • Windows 10 SDK version 10.0.19041.0

[✓] Android Studio (version 2022.1)
    • Android Studio at <path>\andoid-studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-9505619)

[✓] VS Code (version 1.76.0)
    • VS Code at <path>\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.60.0

[✓] Connected device (4 available)
    • sdk gphone64 x86 64 (mobile) • emulator-5554 • android-x64    • Android 13 (API 33) (emulator)
    • Windows (desktop)            • windows       • windows-x64    • Microsoft Windows [Version 10.0.22621.1265]
    • Chrome (web)                 • chrome        • web-javascript • Google Chrome 110.0.5481.178
    • Edge (web)                   • edge          • web-javascript • Microsoft Edge 110.0.1587.63

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Creating a brand new application and running flutter pub get video_player and flutter pub get image_picker won't help either.

The plugin has no control over the camera, it's just requesting that the system launch it via an intent. A crash in the camera is something you would need to report to the developer of the camera application.

Camera application works in itself, I can capture videos and save them natively in the android emulator. Third-party packages such as camera awesome also work. The crash happens in a fresh example app and a fresh android emulator as well.

I've just found #118443, my issue is identical to this.

Camera application works in itself, I can capture videos and save them natively in the android emulator.

Those aren't the same code paths. The fact that one code path works in an application doesn't mean all of them do.

Third-party packages such as camera awesome also work.

That is entirely different from an intent to the camera activity.

The crash happens in a fresh example app and a fresh android emulator as well.

This would be good information to provide in a report to the developer of the crashing code.


Log Z term in loss

I think it is intended for numerical stability, but I don't know how it works.
Could you explain it or provide a reference for that code?
https://github.com/salesforce/jaxformer/blob/9c41fd44a1b052301ad216e2c8fe20677c77adf7/jaxformer/models/decoder/inter/model.py#L71

In the mentioned paper (https://arxiv.org/abs/2206.13517), regularization term is added to prevent the divergence.
Is it right? @enijkamp Can I get further details about the loss term?


[Figma] Callout with media

Add the Callout with media component to Figma kit. Remember we are only building variants for xlg, md, and sm.
Design specs
Website
Must haves:

[ ] Content should be flexible - the designer should be able to condense or stretch the component and the content should respond. Removing text for example should maintain the right padding automatically through auto layout.
[ ] This component uses a fluid type token for the heading. If this is not created already, create a base to help swap the header type based on breakpoint size. See Content group in the library. This should be tested with for Cards.
[ ] Bring in any Image or Video components directly into the _Base component.
[ ] Designers should be able to toggle Copy on or off.
[ ] Designer should be able to include Image, Video, or no media as a variant.
[ ] The header is a fluid typeface, consider creating a separate base to handle the responsive type.

Resources

C4IBM.com Component checklist is available in the Read Me 👀 page of the Figma library
Bases demo from the Figma Fridays (Episode 23)
Reference the best practices from Figma guild
Info on auto layout

Moved off to fix sizing issue with Image with caption


⚠ Cioos National CKAN has degraded performance

In 22c5f88, Cioos National CKAN (https://catalogue.cioos.ca/) experienced degraded performance:

HTTP code: 200
Response time: 9544 ms

Resolved: Cioos National CKAN performance has improved in 43092a6 after 5 minutes.


Specifying _x86_64-microarch-level=something doesn't solve properly.

Solution to issue cannot be found in the documentation.

[x] I checked the documentation.

Issue
Example: conda create -n bug awkward=2.7.2 python=3.11 _x86_64-microarch-level=1 is giving
Channels:
 - conda-forge
Platform: linux-64
Collecting package metadata (repodata.json): done
Solving environment: failed

LibMambaUnsatisfiableError: Encountered problems while solving:
  - nothing provides __archspec 1 core2 needed by _x86_64-microarch-level-1-0_core2

Could not solve for environment specs
The following packages are incompatible
└─ _x86_64-microarch-level =1 * is not installable because there are no viable options
   ├─ _x86_64-microarch-level 1 would require
   │  └─ __archspec ==1 core2, which is missing on the system;
   ├─ _x86_64-microarch-level 1 would require
   │  └─ __archspec ==1 k10, which is missing on the system;
   ├─ _x86_64-microarch-level 1 would require
   │  └─ __archspec ==1 nocona, which is missing on the system;
   └─ _x86_64-microarch-level 1 would require
      └─ __archspec ==1 x86_64, which is missing on the system.

The way I read it, this is a problem with __archspec=1=broadwell which you can see in the conda info because broadwell is not a viable microarch 1/2 version. However the newer ones are extensions, so older instructions are supported by newer cpus so it shouldn't care right?
On the other hand, pixi is able to do this fine
$ pixi add 'awkward 2.7.2' 'python 3.11' '_x86_64-microarch-level 1'
✔ Added awkward 2.7.2
✔ Added python 3.11
✔ Added _x86_64-microarch-level 1

cc @matthewfeickert
Installed packages
Well this is creating a new environment but the `conda list` of `base` is

iason@lima-x86-ubuntu:/Users/iason$ conda list
# packages in environment at /home/iason.linux/miniforge3:
#
# Name                    Version                   Build  Channel
_libgcc_mutex             0.1                 conda_forge    conda-forge
_openmp_mutex             4.5                       2_gnu    conda-forge
archspec                  0.2.3              pyhd8ed1ab_0    conda-forge
boltons                   24.0.0             pyhd8ed1ab_1    conda-forge
brotli-python             1.1.0           py312h2ec8cdc_2    conda-forge
bzip2                     1.0.8                h4bc722e_7    conda-forge
c-ares                    1.34.3               hb9d3cd8_1    conda-forge
ca-certificates           2024.8.30            hbcca054_0    conda-forge
certifi                   2024.8.30          pyhd8ed1ab_0    conda-forge
cffi                      1.17.1          py312h06ac9bb_0    conda-forge
charset-normalizer        3.4.0              pyhd8ed1ab_1    conda-forge
colorama                  0.4.6              pyhd8ed1ab_1    conda-forge
conda                     24.11.0         py312h7900ff3_0    conda-forge
conda-libmamba-solver     24.11.1            pyhd8ed1ab_0    conda-forge
conda-package-handling    2.4.0              pyha770c72_1    conda-forge
conda-package-streaming   0.11.0             pyhd8ed1ab_0    conda-forge
cpp-expected              1.1.0                hf52228f_0    conda-forge
distro                    1.9.0              pyhd8ed1ab_0    conda-forge
fmt                       11.0.2               h434a139_0    conda-forge
frozendict                2.4.6           py312h66e93f0_0    conda-forge
h2                        4.1.0              pyhd8ed1ab_1    conda-forge
hpack                     4.0.0              pyhd8ed1ab_1    conda-forge
hyperframe                6.0.1              pyhd8ed1ab_1    conda-forge
idna                      3.10               pyhd8ed1ab_1    conda-forge
jsonpatch                 1.33               pyhd8ed1ab_1    conda-forge
jsonpointer               3.0.0           py312h7900ff3_1    conda-forge
keyutils                  1.6.1                h166bdaf_0    conda-forge
krb5                      1.21.3               h659f571_0    conda-forge
ld_impl_linux-64          2.43                 h712a8e2_2    conda-forge
libarchive                3.7.7                h4585015_3    conda-forge
libcurl                   8.11.1               h332b0f4_0    conda-forge
libedit                   3.1.20191231         he28a2e2_2    conda-forge
libev                     4.33                 hd590300_2    conda-forge
libexpat                  2.6.4                h5888daf_0    conda-forge
libffi                    3.4.2                h7f98852_5    conda-forge
libgcc                    14.2.0               h77fa898_1    conda-forge
libgcc-ng                 14.2.0               h69a702a_1    conda-forge
libgomp                   14.2.0               h77fa898_1    conda-forge
libiconv                  1.17                 hd590300_2    conda-forge
liblzma                   5.6.3                hb9d3cd8_1    conda-forge
libmamba                  2.0.5                hf72d635_0    conda-forge
libmambapy                2.0.5           py312hf3f0a4e_0    conda-forge
libnghttp2                1.64.0               h161d5f1_0    conda-forge
libnsl                    2.0.1                hd590300_0    conda-forge
libsolv                   0.7.30               h3509ff9_0    conda-forge
libsqlite                 3.47.2               hee588c1_0    conda-forge
libssh2                   1.11.1               hf672d98_0    conda-forge
libstdcxx                 14.2.0               hc0a3c3a_1    conda-forge
libstdcxx-ng              14.2.0               h4852527_1    conda-forge
libuuid                   2.38.1               h0b41bf4_0    conda-forge
libxcrypt                 4.4.36               hd590300_1    conda-forge
libxml2                   2.13.5               h0d44e9d_1    conda-forge
libzlib                   1.3.1                hb9d3cd8_2    conda-forge
lz4-c                     1.10.0               h5888daf_1    conda-forge
lzo                       2.10              hd590300_1001    conda-forge
mamba                     2.0.5                hfdd0a45_0    conda-forge
menuinst                  2.2.0           py312h7900ff3_0    conda-forge
ncurses                   6.5                  he02047a_1    conda-forge
nlohmann_json             3.11.3               he02047a_1    conda-forge
openssl                   3.4.0                hb9d3cd8_0    conda-forge
packaging                 24.2               pyhd8ed1ab_2    conda-forge
pip                       24.3.1             pyh8b19718_0    conda-forge
platformdirs              4.3.6              pyhd8ed1ab_1    conda-forge
pluggy                    1.5.0              pyhd8ed1ab_1    conda-forge
pybind11-abi              4                    hd8ed1ab_3    conda-forge
pycosat                   0.6.6           py312h66e93f0_2    conda-forge
pycparser                 2.22               pyh29332c3_1    conda-forge
pysocks                   1.7.1              pyha55dd90_7    conda-forge
python                    3.12.8          h9e4cc4f_1_cpython    conda-forge
python_abi                3.12                    5_cp312    conda-forge
readline                  8.2                  h8228510_1    conda-forge
reproc                    14.2.5.post0         hb9d3cd8_0    conda-forge
reproc-cpp                14.2.5.post0         h5888daf_0    conda-forge
requests                  2.32.3             pyhd8ed1ab_1    conda-forge
ruamel.yaml               0.18.6          py312h66e93f0_1    conda-forge
ruamel.yaml.clib          0.2.8           py312h66e93f0_1    conda-forge
setuptools                75.6.0             pyhff2d567_1    conda-forge
simdjson                  3.11.3               h84d6215_0    conda-forge
spdlog                    1.14.1               hed91bc2_1    conda-forge
tk                        8.6.13          noxft_h4845f30_101    conda-forge
tqdm                      4.67.1             pyhd8ed1ab_0    conda-forge
truststore                0.10.0             pyhd8ed1ab_0    conda-forge
tzdata                    2024b                hc8b5060_0    conda-forge
urllib3                   2.2.3              pyhd8ed1ab_1    conda-forge
wheel                     0.45.1             pyhd8ed1ab_1    conda-forge
yaml-cpp                  0.8.0                h59595ed_0    conda-forge
zstandard                 0.23.0          py312hef9b889_1    conda-forge
zstd                      1.5.6                ha6fb4c9_0    conda-forge

Environment info
iason@lima-x86-ubuntu:/Users/iason/work/coffea_dev$ conda info

     active environment : None
            shell level : 0
       user config file : /home/iason.linux/.condarc
 populated config files : /home/iason.linux/miniforge3/.condarc
                          /home/iason.linux/.condarc
          conda version : 24.11.0
    conda-build version : not installed
         python version : 3.12.8.final.0
                 solver : libmamba (default)
       virtual packages : __archspec=1=broadwell
                          __conda=24.11.0=0
                          __glibc=2.35=0
                          __linux=5.15.0=0
                          __unix=0=0
       base environment : /home/iason.linux/miniforge3  (writable)
      conda av data dir : /home/iason.linux/miniforge3/etc/conda
  conda av metadata url : None
           channel URLs : https://conda.anaconda.org/conda-forge/linux-64
                          https://conda.anaconda.org/conda-forge/noarch
          package cache : /home/iason.linux/miniforge3/pkgs
                          /home/iason.linux/.conda/pkgs
       envs directories : /home/iason.linux/miniforge3/envs
                          /home/iason.linux/.conda/envs
               platform : linux-64
             user-agent : conda/24.11.0 requests/2.32.3 CPython/3.12.8 Linux/5.15.0-100-generic ubuntu/22.04.4 glibc/2.35 solver/libmamba conda-libmamba-solver/24.11.1 libmambapy/2.0.5
                UID:GID : 501:1000
             netrc file : None
           offline mode : False

Also reported on mamba: https://github.com/mamba-org/mamba/issues/3698 as there is a somewhat similar issue but not exactly the same https://github.com/mamba-org/mamba/issues/3222

What's your use-case for doing such a convoluted solve?

What's your use-case for doing such a convoluted solve?

We make docker containers that are unpacked into apptainers and are then used by workers of a condor clusters. Sometimes those workers may have old CPUs that don't support newer instructions. Therefore, if libraries provide packages with different microarch builds (like awkward does), we would like to install the microarch=1 build.

In that case, the correct invocation is
CONDA_OVERRIDE_ARCHSPEC=x86_64 conda create -n bug awkward=2.7.2 python=3.11
or
CONDA_OVERRIDE_ARCHSPEC=x86_64_v2 conda create -n bug awkward=2.7.2 python=3.11
or similar

In that case, the correct invocation is
CONDA_OVERRIDE_ARCHSPEC=x86_64 conda create -n bug awkward=2.7.2 python=3.11

or
CONDA_OVERRIDE_ARCHSPEC=x86_64_v2 conda create -n bug awkward=2.7.2 python=3.11

or similar

Ah yes, I also read about this CONDA_OVERRIDE_ARCHSPEC in the docs. Thanks for this!
One question though, is this safe? In the sense If I do, CONDA_OVERRIDE_ARCHSPEC=x86_64_v2, will it check that my system actually supports x86_64_v2 or will it just install things anyways?

@jjerphan, ccing from the other issue on mamba. The suggested solution from @isuruf is good. Intuitively, I would expect _x86_64-microarch-level=1 to work as well. Just seeing in case you wanna leave it as is and only allow CONDA_OVERRIDE_ARCHSPEC as the solution. If yes, it should be a little more clear in the docs how to pick your microarch.

Intuitively, I would expect _x86_64-microarch-level=1 to work as well though.

It starts with a underscore, so it's not a public thing that a user should be dealing with.

will it check that my system actually supports x86_64_v2 or will it just install things anyways?

No checks

will it check that my system actually supports x86_64_v2 or will it just install things anyways?

No checks

Isn't that a little dangerous?

Isn't that a little dangerous?

It is, but it also allows an upgrade too. i.e. install a better optimized package to be run in a compute node (eg: level=4) than what is there in a login node (eg: level = 2)

Alrighty, if that is the only recommended solution and you don't wanna make any changes to _x86_64-microarch-level, I'm happy and you can close this. Already used in https://github.com/CoffeaTeam/af-images/pull/60.
I'd like to request some documentation of this though as I couldn't find it anywhere. Related issue already exists: https://github.com/conda-forge/conda-forge.github.io/issues/2105


could not find load file EosioWasmToolchain

I build and install the project ,but cmake command reports error:
CMake Error at CMakeLists.txt:13 (include):
include could not find load file:
EosioWasmToolchain

Did you run install.sh?

Yeah,I have ran install.sh .

What OS are you using? And what version?  Can you post your CMakeLists.txt for your project and the cmake commands you are using?

Same issue. I'm able to build eosio.contracts, but I'm not able to run the examples included in this repo.

cmake_minimum_required(VERSION 3.5)
project(hello_example VERSION 1.0.0)
if(EOSIO_ROOT STREQUAL "" OR NOT EOSIO_ROOT)
set(EOSIO_ROOT "/usr/local/eosio")
endif()
if(EOSIO_WASMSDK_ROOT STREQUAL "" OR NOT EOSIO_WASMSDK_ROOT)
set(EOSIO_WASMSDK_ROOT "/usr/local/eosio.wasmsdk")
endif()
append the path to the module to include
list(APPEND CMAKE_MODULE_PATH ${EOSIO_WASMSDK_ROOT}/lib/cmake)
#include the toolchain cmake
include(EosioWasmToolchain)
add_executable( hello hello.cpp )

set path as pasted.

then
    cmake ../

Thank you @dabdevelop , this compiles now, however i just get 1 hello binary, there are no .wast and no .abi files.
how do i deploy this contract?


R2.7 rocm enhanced revert

revert since these updates break the build for 5.1.
Will rework so it works on both.

replaced with https://github.com/ROCmSoftwarePlatform/tensorflow-upstream/pull/1655


make fetches to fspackages not fail on unknown types

while using this to mount nfs, ran across this issue. Instead
of fixing for the particular case I think it's prudent to let the user
install any fs tools they may need in the case the attributes don't
supply them. also in my case with nfs, no tools are needed.
This will make it safe for a user to nil out the fs tools attribs.

Looks good.

I'll merge for now and test / cut a new release later.


Update _config.yml

Broken link for Patreon gold sponsor due to malformed URL.

Oops, thanks for the fix!


better performance

I find that there are for loop, and in some situations, we can add break to make better performance. at least for your situation, add break does not affect the result

I think only in few situations this will cause influence

You're right, good spot!


fix(sdk): Fix several BatchSpanProcessor errors related to fork safety

This fixes several issues that I noticed when running Ruby 3.0 tests.
Removed the call to reset_on_fork from the thread worker code.
This call is redundant because worker threads go away in a forked child process. In fact, the presence of the call is causing the fork safety test to flake (https://github.com/open-telemetry/opentelemetry-ruby/runs/1642237548). AFAICT the sequence of events is this:

BatchSpanProcessor initializes, and the worker thread starts up.
The test stubs Process.pid (simulating a fork)
If we're unlucky in the timing, the worker thread runs reset_on_fork(restart_thread: false) at this point. This causes @pid to update, but not @thread. (Note that this would never happen in a real system because the forked child process would not run the worker thread, but it can happen in the test simulation.)
Now, back in the main test thread, on_finish is called, which calls reset_on_fork. This is supposed to update @pid and restart the @thread. But since the worker thread has already updated @pid, this call to reset_on_fork returns early, and the @thread never gets restarted. Hence, we fail the expectation that the thread ID has changed.

Removed restart_thread: false in the reset_on_fork call in force_flush
I believe this setting is incorrect. Any time we detect that we've moved into a child process (i.e. any time reset_on_fork determines that @pid has changed, except for the special case of start_thread_on_boot == false), we must restart the worker thread. This is regardless of whether the detection happens in on_finish or force_flush.
The failure mode is the following:

We start up on a FaaS system.
BatchSpanProcessor initializes. (Doesn't matter whether we start a worker thread at this point.)
We fork the process (e.g. Unicorn prefork). Now, @pid is wrong, and the child process has no worker thread.
The first request happens, and it so happens that no spans are generated. That is, on_finish is not called, and neither is reset_on_fork.
The FaaS system calls force_flush in preparation to dial CPU allocation back to zero. This calls reset_on_fork(restart_thread: false) which updates @pid but does not start a worker thread.
Now, for the rest of the life of this child process, it is impossible for a worker thread to start, because @pid now matches, and the only way to get a thread is for @pid to be wrong. Hence, this process never exports its spans.

Put a guard around the thread join in shutdown
Modified shutdown to call @thread.join only if @thread is non-nil and we are not in a child process where the thread has not yet been restarted.
This fixes two failure modes:

Any call to shutdown on a BatchSpanProcessor that was started with start_thread_on_boot: false In this case, the initial call to reset_on_fork intentionally does not create a thread, but then this process never creates a thread. Hence @thread is still nil when shutdown is called.
shutdown is the first method called in a forked child process. The call to @thread.join is invalid because the @thread refers to a worker thread in the parent process that does not exist in the child process.

👍 great PR, thank you!

👍 great PR, thank you!

ref: #363
/cc @sribalakumar in case I'm missing something

ref: #363
/cc @sribalakumar in case I'm missing something


Support type-checking

Mypy complains that this package has neither library stubs or a py.typed marker. Assuming this isn't deliberate, can we add a empty py.typed file to each top-level package so that my code can be type-checked?

Mypy complains that this package has neither library stubs or a py.typed marker. Assuming this isn't deliberate, can we add a empty py.typed file to each top-level package so that my code can be type-checked?

I don't have experience using mypy. Would you like to provide a PR to add that py.typed marker?

Sure! WIP: #168


Capture job links

The CLI captures job links from CI providers in the test sessions command to show the links on the web app. It supports the following providers:

Jenkins
Github Action
CircleCI

It doesn't exist in the original plan, but I added it because it's easy to add.

@Konboi I modified the code based on suggestions. Please review it again.


Update resource-metrics-pipeline.md

Found a invalid link to kubelet section in https://kubernetes.io/docs/tasks/debug/debug-cluster/resource-metrics-pipeline/. This PR fixes the link to point to correct location.
Preview page link-  https://deploy-preview-47744--kubernetes-io-main-staging.netlify.app/docs/tasks/debug/debug-cluster/resource-metrics-pipeline/
(Checkout the "kubelet" link in second bullet point)

/lgtm
/approve


Whether to support the collection of trace data through Kafka like zipkin

Whether to support the collection of trace data through Kafka like zipkin, if it is supported, whether there are related documents, if not, what are the main considerations based on

Read FAQ https://github.com/apache/skywalking/blob/master/docs/en/FAQ/README.md#design


LEGO: Pull request from lego/hb_04604851-bac4-4681-9f74-73de611d6e48_20210720153451953 to main

LEGO: Pull request from lego/hb_04604851-bac4-4681-9f74-73de611d6e48_20210720153451953 to main with localized lcls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.002%) to 42.555%

Totals

Change from base Build<PHONE_NUMBER>:
0.002%

Covered Lines:
26727

Relevant Lines:
56924

💛  - Coveralls


Update build-messaging-for-cyberconnect-profiles.md

added additional links / formatting numbered list

Thank you for taking the time to provide feedback and these links, @nazihkalo!


Fixed issue:Typescript easy

Added the necessary return statement to the greet function so that it returns a greeting message. The function returns a string in the format Hello, [name]! where [name] is the value of the input argument.

Have you tried using node_modules/ in your .gitignore?
Seems to be the fix according to https://stackoverflow.com/a/51991384

Have you tried using node_modules/ in your .gitignore? Seems to be the fix according to https://stackoverflow.com/a/51991384

Thanks for the tip! I think the issue is that since i am using Linux, and in Linux it can be just node_modules or /node_modules but maybe for Windows or Mac users it needs to be node_modules/ then. I'll try it out.

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out my other projects. Just click here to find more. These projects contain real issues that you can help resolve.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!

okay @nikohoffren, done that


python3Packages.yamlfix: init at 0.7.2

Motivation for this change
The yamlfix Python package let's you quickly fix yaml files.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Are there more options that need to be set as pytestFlagsArray?

  postPatch = ''
    substituteInPlace pyproject.toml \
      --replace 'python_paths = "."' ""
  '';

Thanks a lot @fabaff, it correctly installs now on my NixOS when I use:
nix-env -f $(git rev-parse --show-toplevel) -iA yamlfix -vvv


Fix opening leak canary instead of app launcher

Proposed Changes
There was an issue when I used maestro for an Android app with LeakCanary. I fixed the issue in this PR.
Issues Fixed

I was unable to find a solution to it. Maybe we should raise the issue on LeakCanary repo and try to figure it out there.


Autocomplete snippets seem to be displayed in arbitrary order

In language-javascript/snippets, there's an "f" snippet for an anonymous function, and language-todo/snippets has "fix" for a "fix me" comment. To see this:

Open a javascript file
Type "f"

The former should be offered as the first suggestion, as it's the best match, but instead it appears 6th on the list, behind fix, for, forin, forof and fun.

Are you using autocomplete or autocomplete-plus?

autocomplete-plus and autocomplete-snippets

Duplicate of atom-community/autocomplete-snippets#43 - please subscribe there for updates.


Video Labelling

Hello how can i labbelling to video .İ wanna use to yolov5 .But i need to labbeling  video .Do you know  video Labbelling Tools
-OS: Windows 10

Hello @ozicmoi, you have to use ffmpeg or any other app to transform your video into sets of images, then you will able to label each image individuali


Prototype - add electrification profiles to change table

Purpose
Get feedback on the new schema for electrification profiles and scaling by grid/zone.
What the code is doing
Define one new function add_electrification (not attached to the change table yet), which can specify profiles and scaling for supported types: currently these are building and transportation. If specifying scaling factors by zone, the zone name is checked against the current grid object. There isn't yet validation for the profile name/version, but I'll add that if the general approach looks good.
Depending on expected usage patterns, the schema could also be "inverted" by mapping profiles to zones and scaling factors, but I think either way has trade offs in how easy it is to specify the change table and how much code is required to aggregate the profiles during the preparation phase.
Testing
New unit tests.
Usage Example/Visuals
The tests are the best usage example. The full schema will look like:
{
    "building": {
        "grid": [scale_factors],
        "zone": { zone_name: [scale_factors], ... }
    },
    "transportation": {...}
}

Where the scale_factors dict has the structure:
{profile_name_and_version_1: s_1, profile_name_and_version_2: s_2, ...}

And 0 <= s_i <= 1
Time estimate
20 min

Not sure I understand why you constrain the scaling factors to be less than 1

Not sure I understand why you constrain the scaling factors to be less than 1

We can't change more than 100% of e.g. fossil fuel heating to electrified heating, and the profiles that we're getting from the collaborators represent 100% conversion of fossil end uses to 100% of one particular technology.

Not sure I understand why you constrain the scaling factors to be less than 1

The scaling factor here is essentially adoption rate.

I like the examples shown in the tests. Being able to scale across the whole grid is a nice addition!

I like the examples shown in the tests. Being able to scale across the whole grid is a nice addition!

Should we implement it for other methods?

Looking at this, I realize that I specified this feature incompletely. I think we need one more layer of nesting in the change table schema, because we have multiple end uses within each of buildings and transportation. So we would go from [buildings/transportation][zone/grid][technology] = adoption to [buildings/transportation][zone/grid][end_use][technology] = adoption. Currently we have:
info = {
    "New York City": {"advanced_heat_pump_v2": 0.7},
    "Western North Carolina": {
        "standard_heat_pump_v1": 0.5,
        "advanced_heat_pump_v2": 0.5,
    },
}

But I think we need something more like:
info = {
    "New York City": {
        "res_heating": {"advanced_heat_pump_v2": 0.7},
        "com_hot_water": {"advanced_heat_pump_v2": 0.7},
        "res_cooking": {"mid_efficiency": 0.5, "high_efficiency": 0.3},
    },
    "Western North Carolina": {
        "res_heating": {
            "standard_heat_pump_v1": 0.5,
            "advanced_heat_pump_v2": 0.5,
        },
    },
}

Adoption rates for various technologies still need to sum to less than one for a given (class, zone, end use). Sorry for the bad spec.


fix: 调整 popconfirm 组件导出命名

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@c48c298). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop     #585   +/-   ##
==========================================
  Coverage           ?   64.84%
==========================================
  Files              ?      723
  Lines              ?    12466
  Branches           ?     2991
==========================================
  Hits               ?     8083
  Misses             ?     4383
  Partials           ?        0

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c48c298...292a38b. Read the comment docs.


Python: Update non-aiohttp samples

Since some code is now in botbuilder-integration-aiohttp, will this effect the non-aiohttp framework samples.

Deferring until R9


⚠ Bofrost.de has degraded performance

In bd2af23, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1541 ms

Resolved: Bofrost.de performance has improved in e388e04.


How to save a screenshot together with iv and xml files

Hi! I've managed to run
roslaunch grasp_planning_graspit_ros graspit_planner_jaco_example.launch
results_output_directory:=
and save the inventor and world files. However, I would also like to also save a "screenshot" of the scene - similar to Save Image when running  graspit_interface. I've tried adding a function to GraspitSceneManager that does something like:
core->getIVmgr()->saveImage(filename.c_str());
The code can compile but it breaks when I try to execute it. Do you have any idea how to do this? Thanks a lot!

Hi, this should be possible, can you be more specific about how it "breaks", is it a segmentation fault at the call of saveImage?

Since I haven't heard back, I presume you have fixed this and will close the issue. Please re-open if you keep having problems.


Cannot upload app to app store on iOS

Environment

Dev OS: Mac OS 13.5.2
@rnmapbox/maps version: 10.1.16
React Native version: 0.71.2

Steps to reproduce
Upload app to App Store Connect from Xcode (Product > Archive)
Description
Hello, I installed RN Mapbox without any issue and am able to use it in my app when running on the simulator. The build phase does not throw any error.
But when I try to archive the app to upload it to App Store Connect, I get the following error :

Do you have any idea ? Thank you for your help

@nathanael-anstett is this a new project? Can you try with a  new once created with npx react-native init?

Hello @mfazekas , it also happens with a blank project freshly created with npx react-native init


Update docs regarding zstd:chunked

What is the problem you're trying to solve
https://github.com/containerd/nerdctl/blob/f21bca52d09cccf5c16f9a881049a3f44e3165c9/docs/stargz.md#tips-2-using-zstd-instead-of-gzip-aka-zstdchunked talks about versions that are long released.
Describe the solution you'd like
Please update the docs.
Additional context
No response

/close


v1.2.2 does not work on Mac

When v1.2.2 is installed, simply get blank Tabli window.  Re-installing v1.1.0 works just fine. Please fix.
Problem is that Chrome keeps updating to v1.2.2 automatically, so have to repeatedly reinstall v1.1.0.
Other problem is that I used to have keyboard shortcut set as Opt-T to open the pop-out window. I do not recall how I set this but I no longer see this anywhere. The only shortcut I see is Ctrl-, but again , I am on a Mac. Can you please advise?
Currently using Chrome v49.x (cannot upgrade because of my macOS version).
If v1.2.2. is not compatible with Chrome 49.x and this cannot be fixed, then please prevent autoupdate of the extension for users like me.

(Worked offline with user on a bespoke solution to provide an older version of Tabli for use with this older version of Chrome.)

As for the keyboard shortcut, this was set using Chrome's built-in keyboard shortcut list via link at the bottom of the Extensions list.


Menu stuck in compact mode

Issue Type: Bug
I don't know how it happened, but I was reading the June 2022 (version 1.69) Release Notes, and had just set the following in user Settings UI:
workbench.preferredDarkColorTheme
workbench.preferredLightColorTheme
workbench.preferredHighContrastColorTheme
workbench.preferredHighContrastLightColorTheme

...when I looked up and saw the MenuBar had changed to a 'hamberger menu'!

I restored the defaults for those settings
I closed Settings UI
I restarted vscode
I opened Settings UI
I found the  window.menuBarVisibility was set to classic

I set window.menuBarVisibility to toggle

after doing this, hitting alt key toggled the visibility of the hamburger menu from visible to invisible...but this did NOT restore the full menubar (classic menu)

I restarted vscode
I tried every option for window.menuBarVisibility (hidden, toggle, etc)

with vscode restarts between each change

I opened user settings.json

I confirmed that  "window.menuBarVisibility" was NOT present
I added item:

"window.menuBarVisibility": "classic"

restarted vscode

I tried 15 different google searches, rewording the search text each time:
vscode menu bar compact
vscode menu bar stuck in compact
vscode menu bar hamburger menu broken
vscode menu bar settings broken
etc

...but 45 min of reading similar issues and testing recommended fixes...produced no change.
I really don't like the compact menu, I hope you can help!
 Please paste.

Have you enabled Command Center using "window.commandCenter": true?
Yes I have!

Then please see #152906
/duplicate

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Various documentation amendments and added common-mapping-transform.

Various documentation amendments and added common-mapping-transform.

Thanks for the file Kelvin. We will update the same in the upcoming commit.


Bug: Asteroid duplication, asteroid can collide with multiple bullets/mines/ships and spawn multiple sets of children

In the update() loop when checking asteroid-bullet collisions, after an asteroid collides with a bullet, the asteroid can go on to collide with more bullets in subsequent loop iterations, and each time it collides, it spawns off 3 new children.

To fix this, we can add the following check, so that asteroids marked for removal cannot go on to collide with more bullets:

And as a possible optimization, we can actually just cull the asteroids once at the end of update(), and along the way just skip over indices that are marked for removal. That's what I'm doing in my controller to reduce the amount of list comprehensions.
Super sneaky bug that I only found with randomized testing, where my controller using different collision code desynced with the game for seemingly no reason.

Oops, missed that this same bug happens in the other loops for mine-asteroid and ship-asteroid collisions too. As a fix, I'll just change over the entire asteroid culling to do one list comprehension at the end, and collect and check deleted asteroid indices along the way. This will fix the bug, along with speeding up asteroid culling.


testMatch on Windows

🐛 Bug Report
The following testMatch works on unix systems while does not on Windows machines. It is required to narrow the folders where to look for tests.
  testMatch: [
    '<rootDir>/src/**/?(*.)+(spec|test).(ts|tsx|mjs|js|jsx)',
  ],

Error on Windows:
  636 files checked.
  testMatch: C:/Users/IEUser/Fusion-UI/packages/infodesk/src/**\?(*.)+(spec|test).(ts|tsx|mjs|js|jsx) - 0 matches
  testPathIgnorePatterns: \\node_modules\\ - 636 matches
  testRegex:  - 636 matches
Pattern:  - 0 matches
error Command failed with exit code 1.

To Reproduce
Set a testMatch that starts with <rootDir>/src/... in place of the default **/*/....
See in the error message src/**\?(*.) here the / was replaced by \ and it is a lonely case.
Expected behavior
testMatch should work cross OS as in v23.
Link to repl or repo (highly encouraged)
this repro work in v22 while fails in v24 with Windows: https://repl.it/@artola/jest-bug
Run npx envinfo --preset jest
Paste the results here:
  System:
    OS: macOS 10.14.3
    CPU: (4) x64 Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz
  Binaries:
    Node: 11.9.0 - /usr/local/bin/node
    Yarn: 1.13.0 - /usr/local/bin/yarn
    npm: 6.5.0 - /usr/local/bin/npm
  npmPackages:
    jest: ^24.1.0 => 24.1.0

We moved to micromatch@3 and it seems like your glib is not valid anymore. You'll need to adjust it to be compliant. We're sorry this happens but it was announced as a breaking change

I wonder if this is #7814?

@thymikee I know about the breaking change and we changed the glob, mainly I just use the default one shown in jest --init with the prefix <rootDir>/src/. While this works on Mac/Unix, does not on Windows.

Oh, that may be the case. Reopening then

I wonder if this is #7814? Seeing as OP says it works on unix

@SimenB I am using v24.1 but if I add the slash wrapper as shown here (https://github.com/facebook/jest/blob/d81c4cb5443e529a5c0572e5b9e4f231249c3609/packages/jest-config/src/utils.js#L70) the testMatch works on unix and also on Windows.

@SimenB @thymikee When I create a config using jest --init shows this block:
  // The glob patterns Jest uses to detect test files
  // testMatch: [
  //   "**/__tests__/**/*.[jt]s?(x)",
  //   "**/?(*.)+(spec|test).[tj]s?(x)"
  // ],

Then I just uncommented this block and tweaked a bit to support <rootDir>/src/.
This change does not play well in Windows while in Unix is ok as reported above.
Now what I did is slightly change the glob and works in both OS, following the doc in micromatch.
  // The glob patterns Jest uses to detect test files
  testMatch: [
     "<rootDir>/src/**/__tests__/**/*.[jt]s?(x)",
     "<rootDir>/src/**/*(*.)@(spec|test).[tj]s?(x)"
  ],

Here the more important changes:

?(*.) => *(*.) ... from 0 or 1 occurrence to 0 or more occurrences
+(spec|test) => @(spec|test) ... from 1 or more occurrences to matches 1

Could be that "just" the default for testMatch shown in the documentation need some update?

@artola That solves my issues after upgrading multiple of my projects to latest Jest. Befeorehand I had to add a bunch of ignore entries to stop it from picking up files that Jest thought had tests but didn't actually, resulting in fake fails. One such example is the Create React App's test.js script which actually executes Jest.

Can we count on fix?

Not sure what a fix would be? Is it a documentation or implementation issue? A PR for either is very much welcome as none on the core team uses windows. We do test windows on CI though, so if it's a code issue we can add a test as well

@SimenB It is a code issue, see my comment above, a solution is wrap this return with slash.
https://github.com/facebook/jest/blob/16930281c466ef3ac7a07d9777d47b2d208ce16e/packages/jest-config/src/utils.ts#L66
It will be great if some Windows expert verifies and creates the PR.
In the meantime the solution was change the micromatch as explained.

Aight, fair enough! Looking forward to that PR 😊

yup, the focus is the path slash
In windows default slash like tests\rules\indent\indent.test.ts, but jest does not match this, must change like tests/rules/indent/indent.test.ts

Hello!
I'm not sure if it's the same bug,
I've found the testMatch glob like ...__tests__/+(unit|integration)... is internally converted to ...__tests__\+(unit|integration)... on Windows so it does not match. Other slashes in my pattern are not converted. It works on linux.
Workaround for me was ...__tests__+(/unit|/integration)....

Hello!
I encountered a similar issue. The following wildcard works on Unix machines but does not work on Windows machines:
'<rootDir>/packages/**/(src|test)/**/*.(test|spec|e2e-spec).*'

@SimenB, after some debugging I found that there is replacePathSepForGlob function in jest-utils which is used in parsing of config files.
Here is this function:
// node_modules/jest-util/build/replacePathSepForGlob.js

function replacePathSepForGlob(path) {
  return path.replace(/\\(?![{}()+?.^$])/g, '/');
}

I changed it to log the result and path:
function replacePathSepForGlob(path) {
  const result =  path.replace(/\\(?![{}()+?.^$])/g, '/');
  console.log('Replace sep for glob', {path, result})
  return result
}

So, the issue happens because this function converts glob patents on Windows machines in the following way:
Original: '<rootDir>/packages/**/(tests|src)/**/*.(test|spec|e2e-spec).*'
Path: 'C:\\Users\\user\\Documents\\project\\packages\\**\\(src|test)\\**\\*.(test|spec|e2e-spec).*',
Replaced path: 'C:/Users/user/Documents/project/packages/**\\(src|test)/**/*.(test|spec|e2e-spec).*'

The issue is in this place (in replaced part) .../packages/**\\(src|test)/**/... - double slash is not replaced with a singular slash to be .../packages/**/(src|test)/**/....
It looks like ecranisation logic conflicts with double backslashes. So, if / is followed by (a|b) wildcard on Windows then the replaced path is incorrect.
Additional notes:

/+(a|b) wildcard (with modificator prefix) does not work
/(a|b) wildcard (without modificator prefix) works well if you try it e.g. here: https://globster.xyz/
/(a|b) wildcard (without modificator prefix) works on Unix machines
/{a..b} (braces) does not work, e.g.:

Original: '<rootDir>/packages/**/{1..3}/**/*.(test|spec|e2e-spec).*'
Path: 'C:\\Users\\user\\Documents\\project\\packages\\**\\{1..3}\\**\\*.(test|spec|e2e-spec).*',
Replaced path: 'C:/Users/user/Documents/project/packages/**\\{1..3}/**/*.(test|spec|e2e-spec).*'

Am I missing something? Or there is an issue?

In my case, I found only one workaround for /(a|b) wildcard. Such wildcard can be split into multiple wildcards:
testMatch: [
   '<rootDir>/packages/**/(tests|src)/**/*.(test|spec|e2e-spec).*'
  ],

change to
testMatch: [
    '<rootDir>/packages/**/tests/**/*.(test|spec|e2e-spec).*',
    '<rootDir>/packages/**/src/**/*.(test|spec|e2e-spec).*',
  ],

We do test windows on CI though

@SimenB correct me if I'm wrong, the test uses path.posix on Windows, so it doesn't behave the same as require('path') on Windows (should be path.win32 on Windows by default).
https://github.com/facebook/jest/blob/abca0fe6c1d9fed884e4dc8bb911b3497db506ee/packages/jest-config/src/__tests__/normalize.test.ts#L21
I want to take a stab at fixing this, but writing a separate test suite for Windows seems like a lot of work to me.

Forgive my ignorance, but does this mean that testMatch doesn't work at all under windows? I've attempted to run jest on a new project with every possible permutations of patterns I can think of - including hard coding to the exact file location - and I can't get jest to see my test file to attempt to run it.
Based on my understanding of this report, the issue is limited to failing on forward-slash paths, i.e. the default patterns: **/__tests__/**/*.[jt]s?(x), **/?(*.)+(spec|test).[tj]s?(x)
What I'm experiencing, however, is an out-right refusal to work no matter the pattern. For example, \jest --testMatch "\\node_modules\\" produces the following output:
o tests found, exiting with code 1
Run with `--passWithNoTests` to exit with code 0
In C:\Users\chadb\OneDrive\Documents\Code\chads_superawesome_angular_workspace
  252 files checked.
  testMatch: //node_modules/ - 0 matches
  testPathIgnorePatterns: \\node_modules\\ - 252 matches
  testRegex:  - 0 matches
Pattern:  - 0 matches

For good measure, here is the default pattern (which should match successfully):
C:\Users\chadb\OneDrive\Documents\Code\chads_superawesome_angular_workspace>jest
No tests found, exiting with code 1
Run with `--passWithNoTests` to exit with code 0
In C:\Users\chadb\OneDrive\Documents\Code\chads_superawesome_angular_workspace
  252 files checked.
  testMatch: **/__tests__/**/*.[jt]s?(x), **/?(*.)+(spec|test).[tj]s?(x) - 0 matches
  testPathIgnorePatterns: \\node_modules\\ - 252 matches
  testRegex:  - 0 matches
Pattern:  - 0 matches

I am, however, able to explicitly set a file via --runTestsByPath and it discovers the file just fine (though my test is failing for a presumably unrelated reason)
C:\Users\chadb\OneDrive\Documents\Code\chads_superawesome_angular_workspace>jest --runTestsByPath "src/app/__tests__/jestSmoke.ts"
 FAIL  src/app/__tests__/jestSmoke.ts
  ● Test suite failed to run

    TypeError: Cannot read properties of undefined (reading 'html')

      at new JSDOMEnvironment (node_modules/jest-environment-jsdom/build/index.js:72:44)
      at async TestScheduler.scheduleTests (node_modules/@jest/core/build/TestScheduler.js:317:13)
      at async runJest (node_modules/@jest/core/build/runJest.js:407:19)
      at async _run10000 (node_modules/@jest/core/build/cli/index.js:338:7)
      at async runCLI (node_modules/@jest/core/build/cli/index.js:190:3)

Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        0.711 s
Ran all test suites within paths "src/app/__tests__/jestSmoke.ts".

C:\Users\chadb\OneDrive\Documents\Code\chads_superawesome_angular_workspace>

The reason I am being so specific with the behavior here is I have a non-standard setup that may be further compounding the issue - and I suspect there are probably others like me. I have (by choice) installed the linux command line utilities within my typical windows cmd shell. This means commands like this work just fine (notice the intentional use of / for file directories)
C:\Users\chadb\OneDrive\Documents\Code\chads_superawesome_angular_workspace>cat ./src/app/__tests__/jestSmoke.ts
/**
 * @jest-environment jsdom
 */

test('use jsdom in this test file', () => {
  const element = document.createElement('div');
  expect(element).not.toBeNull();
});

C:\Users\chadb\OneDrive\Documents\Code\chads_superawesome_angular_workspace>

The topic, workarounds given, and age of this bug seem to indicate it's very low priority and that makes sense. For me though, this bug is a hard blocker. I am unable to find any satisfactory config which allows jest, npm test, or ng test to run my unit tests. Surely I've overlooked a possible workaround or I'm experiencing an unrelated bug?
Output of npx envinfo --preset jest:
  System:
    OS: Windows 10 10.0.22000
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1195G7 @ 2.90GHz
  Binaries:
    Node: 17.2.0 - C:\Program Files\nodejs\node.EXE
    npm: 8.1.4 - C:\Program Files\nodejs\npm.CMD
  npmPackages:
    jest: ^28.1.0 => 28.1.0

This issue persists. I have Jest version 28.1.3 installed on Windows Version 10.0.22621. My testMatch option is defined as, testMatch: ['/**/*.test.*(/ts|/tsx)'] within jest.config.js.
The message I get when I run Jest is,
No tests found, exiting with code 1
Run with `--passWithNoTests` to exit with code 0
In C:\Users\jaitj\Documents\osc\chapter
  432 files checked.
  testMatch: /**/*.test.(ts|tsx) - 0 matches
  testPathIgnorePatterns: \\node_modules\\ - 432 matches
  testRegex:  - 0 matches
Pattern:  - 0 matches

The path separators for testMatch & testPathIgnorePatterns in the message above stand out to me. I wonder what makes Jest internally translate the path separator correctly for testPathIgnorePatterns but NOT for testMatch. The former option is defined as watchPathIgnorePatterns: ['/node_modules'] in jest.config.js.

+1 still experiencing issue in feb, 2023 ☹

One possible workaround when trying to get a launch.json file to work on Windows is to use this VSCode extension:
https://marketplace.visualstudio.com/items?itemName=rioj7.command-variable
I installed this, and then used the following launch.json configuration:
        {
            "name": "Debug One Test File",
            "type": "node",
            "request": "launch",
            "runtimeArgs": [
                "--inspect-brk",
                "${workspaceRoot}/node_modules/jest/bin/jest.js",
                "--runInBand",
                "${command:extension.commandvariable.file.relativeFilePosix}"
            ],
            "console": "integratedTerminal",
            "internalConsoleOptions": "neverOpen",
            "env": {
                "JEST_TEST_TIMEOUT": "2147483647",
            }
        }


after deleting ingress, ingress service re-appears in rancher ui

Rancher versions:
rancher/server or rancher/rancher: 1.6.18
Infrastructure Stack versions:
healthcheck:
ipsec:
network-services:
scheduler:
kubernetes (if applicable):
Docker version: (docker version,docker info preferred)
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
HA
Steps to Reproduce:
Here is Ingress control log which is showing ingress is deleted and also showing lb created within minutes. Rancher is creating Ingress after deleted via kubectl cli
8/28/2018 2:21:42 PMtime="2018-08-28T18:21:42Z" level=info msg="Event(api.ObjectReference{Kind:\"Ingress\", Namespace:\"my-ns\", Name:\"my-ingress\", UID:\"fdf59274-a7de-11e8-9229-020a529960bb\", APIVersion:\"extensions\", ResourceVersion:\"69027707\", FieldPath:\"\"}): type: 'Normal' reason: 'DELETE' my-ns/my-ingress"
8/28/2018 2:21:42 PMtime="2018-08-28T18:21:42Z" level=info msg="Deleting lb service [my-ns-lb-my-ingress]"

8/28/2018 2:22:59 PMtime="2018-08-28T18:22:59Z" level=info msg="Creating lb service [%!s(*client.LoadBalancerService=<nil>)]"
8/28/2018 2:23:06 PMtime="2018-08-28T18:23:06Z" level=info msg="Updating Rancher LB with the new lbConfig [&{{ map[] map[]} [] defaults\nlog <IP_ADDRESS>:8514 local0 info\noption httplog\ntimeout client 50000\ntimeout connect 5000\ntimeout server 50000 1c33 [{{ map[] map[]} %!s(int64=0) https 1s8167 %!s(int64=10081) %!s(int64=8443)}] %!s(*client.LoadBalancerCookieStickinessPolicy=<nil>)}] "```

Tested with v1.6.22-rc3 on a HA setup. Created K8s environment on the HA setup.
Created pods and ingress . Deleted the ingress. Ingress was not re-created . The steps were repeated several times and the issue did not reproduce.
Ingress controller logs:
9/5/2018 4:52:48 PMtime="2018-09-05T23:52:48Z" level=info msg="Updating ingress default/ingress3 with IP <IP_ADDRESS>"
9/5/2018 4:52:48 PMtime="2018-09-05T23:52:48Z" level=info msg="Event(api.ObjectReference{Kind:\"Ingress\", Namespace:\"default\", Name:\"ingress3\", UID:\"c81dee96-b166-11e8-b1f1-02ae1e206d60\", APIVersion:\"extensions\", ResourceVersion:\"8004\", FieldPath:\"\"}): type: 'Normal' reason: 'UPDATE' default/ingress3"
9/5/2018 4:52:48 PMtime="2018-09-05T23:52:48Z" level=info msg="Event(api.ObjectReference{Kind:\"Ingress\", Namespace:\"default\", Name:\"ingress3\", UID:\"c81dee96-b166-11e8-b1f1-02ae1e206d60\", APIVersion:\"extensions\", ResourceVersion:\"7997\", FieldPath:\"\"}): type: 'Normal' reason: 'CREATE' ip: <IP_ADDRESS>"
9/5/2018 4:52:48 PMtime="2018-09-05T23:52:48Z" level=info msg="Updating Rancher LB with the new lbConfig [&{{  map[] map[]} []   [{{  map[] map[]}    %!s(int64=0) http  1s31 %!s(int64=85) %!s(int64=80)}] %!s(*client.LoadBalancerCookieStickinessPolicy=<nil>)}] "
9/5/2018 4:53:31 PMtime="2018-09-05T23:53:31Z" level=info msg="Event(api.ObjectReference{Kind:\"Ingress\", Namespace:\"default\", Name:\"ingress3\", UID:\"c81dee96-b166-11e8-b1f1-02ae1e206d60\", APIVersion:\"extensions\", ResourceVersion:\"8068\", FieldPath:\"\"}): type: 'Normal' reason: 'UPDATE' default/ingress3"
9/5/2018 4:53:31 PMtime="2018-09-05T23:53:31Z" level=info msg="Event(api.ObjectReference{Kind:\"Ingress\", Namespace:\"default\", Name:\"ingress3\", UID:\"c81dee96-b166-11e8-b1f1-02ae1e206d60\", APIVersion:\"extensions\", ResourceVersion:\"8070\", FieldPath:\"\"}): type: 'Normal' reason: 'DELETE' default/ingress3"
9/5/2018 4:53:31 PMtime="2018-09-05T23:53:31Z" level=info msg="Deleting lb service [default-rancherlb-ingress3]"

Fixed in rancher/lb-service-rancher:v0.9.7

Setup:
Fresh install of v1.6.18-patch1-rc2 .
Created K8s env . k8s version - k8s 1.10.11-rancher1-2.
Manually updated ingress controller in Kunbernetes service to rancher/lb-service-rancher:v0.9.8-rc2
Delete 10 existing ingress
Create 10 ingress.
Repeated the above 2 steps multiple times in parallel.
rancherlb services relating to the ingresses get removed for all the deleted ingresses.


Feature request: pre-commit hook

It'd be nice if this was provided as a pre-commit hook so that people can easily integrate it into their local and CI runs.
https://pre-commit.com/#new-hooks

Have you tried husky or lint-staged?


Display held items of remote players in multiplayer sessions.

Clients' local system for displaying held items of all remote players in multiplayer sessions.
Tackled issues: #3280
Based on @Josharias 's firstPersonClientSystem introduced mid 2016, practically clones his changes.
image summary
Added java classes:
ThirdPersonRemoteClientSystem.java - Essential class which glues all together. Handles displaying held items for all remote players in multiplayer session. Locally, registered for clients.
RemotePersonHeldItemTransformComponent.java - Component represents transformations of various held item types (used in hand,itemBase and blockItemBase prefabs)
RemotePersonHeldItemMountPointComponent.java - Component represents mounting point of characters for held items to attach to.
ItemIsRemotelyHeldComponent.java - This is used on the client side to track and clean up items that are no longer held by remote players, but are still location linked
Added prefabs:
remotePersonHeldItemMountPoint.prefab - represents RemotePersonHeldItemMountPointComponent.java
Modified prefabs:
blockItemBase.prefab,itemBase.prefab,hand.prefab - added remotePersonHeldItemTransform components to handle transformations of these items in game
player.prefab - added remotePersonHeldItemMountPoint component to attach all the held items to. Corresponds to same named .java
How to test and try out
Host a server, run another instance, join the server, run around, change held items, pickup blocks, observe one another holding different types of held items (empty hand, blocks, weapons, torches)...
Run multiple instances of the game, host a multiplayer session, connect and disconnect players and watch their items. - ❗  More than two players tends to crash often.
Client sometimes logs in with a detached camera spawned at 0 0 0.
ToDo:

[ ] UnitTests

Outstanding before merging ❗

[ ] Occassional nullpointer crashes while: - simultaneously joining server, - on disconnecting of crashed player. Needs more testing and more eyes :) I've changed these mechanics so many times I can't see clearly.

Can one of the admins please verify this patch?

@GooeyHub: add to whitelist
@dave2s: thanks again for this! :-)

Hooray Jenkins reported success with all tests good!


A user with the following RBAC (Storage Blob Data Contributor) should perform a copy/rename

Preflight Checklist

[X] I have installed the latest version of Storage Explorer.
[X] I have checked existing resources, including the troubleshooting guide and the release notes.
[X] I have searched for similar issues.

Problem
A user with IAM READER level on storage account and full rights on the content of a container (Read, write, exec) can't copy/paste  folder and files
Desired Solution
Allow copy/paste on folder and files
Alternatives and Workarounds
No response
Additional Context
No response

I assume you are seeing the Copy button disabled when you are using Azure AD credential to access your ADLS Gen2 data. The reason of disabling the button is explained in https://github.com/Azure/azure-storage-azcopy/issues/1304 and https://github.com/microsoft/AzureStorageExplorer/issues/3992.
If that's the case, we will be tracking this feature request in #3992. If not, please reopen the issue and elaborate on your case.


Develop doesn't build

We merged a few branches that all were green, yet develop is red.
See https://semaphoreci.com/torxakis-admin/torxakis/branches/develop/builds/82 which error seems to be related to the new procid.
While Issue746/proc #774 built fine.

Is the dependency management of txs-compiler faulty? Why first everything fine and finally not?


Error: Peer-to-peer access is unsupported on this platform

Hi, the problem is:
(ParaWorker pid=1955026) Error: Peer-to-peer access is unsupported on this platform.
(ParaWorker pid=1955026) In the current version of distserve, it is necessary to use a platform that supports GPU P2P access.
(ParaWorker pid=1955026) Exiting...
I face a problem like this, but I actually checked the P2P connection between the two GPUs, and I tried the following codes for testing the P2P connection between GPUs:
tensor_a = torch.randn(10, device="cuda:0")
try:
    # Attempt to directly copy tensor_a from GPU 0 to GPU 1
    tensor_b = tensor_a.to("cuda:1")
    print("Successfully copied tensor from GPU 0 to GPU 1 using P2P.")
except RuntimeError as e:
    print("Failed to copy tensor from GPU 0 to GPU 1 using P2P. Error:", e)

and the output is:
Successfully copied tensor from GPU 0 to GPU 1 using P2P.
and the GPU topo is:

can you provide any suggestions?
thank you!

The GPUs I use are RTX 4090s

Yeah I solved the problem, seems that RTX 4090/PCIe connections cannot support DistServe, we run DistServe successfully on A100 machines with NVLINKs.


[BUG] - Navbar ShowIn & HideIn Props Swapped

Describe the bug
Currently, the props for the Navbar.Toggle at the least are switched. The hideIn acts as the showIn prop should and viceversa.
The current work around I have is using the showIn prop where I need the Navbar to Hide at, which works great, however this is not what is documented per the documentation.
I could be plainly misunderstanding the logic of the documentation, but if so, I would recommend that it be amended for clearer documentation.
Your Example Website or App
https://github.com/kentond18/nextui-bug
Steps to Reproduce the Bug or Issue

Run npm run dev
Open in browser
Resize the browser
View MainNav.tsx and navigate to <Navbar.Toggle> component
See how showIn prop is set to sm and upon resizing the toggle is missing from md and up

Expected behavior
As a user, I am expecting the toggle to be visible from the defined breakpoint and up within the showIn prop rather than hidden from 0 to defined breakpoint. Same happens if I alter this and use hideIn="md", it hides it from xs and sm and displays from md and up, rather than the opposite.
Screenshots or Videos
No response
Operating System Version
macOS 12.5.1
Browser
Chrome

Hey please upgrade to V2 since V1 will no receive more updates.


Bring the checker back!

It could have saved me a few hours of debugging recently, so I suggest we bring it back.
Ok, I agree that it is on the verbose side, but I actually like that - and it seems to be the trend with most IDEs I am using at the moment, to give me a lot of notices and warnings. If they are too annoying, we could have annotations to just disable all warnings.

It should now be mostly back.


.Should().Equal(...) enumerates the collection multiple times

Similar to #124
I tried to upgrade the tests of my Linq.Extras library to the latest version of FluentAssertions, and suddenly many tests started breaking. Apparently a change introduced in 4.3.0 caused FA to enumerate the collection multiple times. Since I wrap my collections specifically to ensure that they're enumerated only once (see #124 for details), the tests break...

Aich. Do you know which extension method is the cause of this?

@dennisdoomen I'm not sure what you mean...
It happens for instance in this test:
    [Test]
    public void CommonPrefix_Returns_Common_Prefix_Of_Two_Sequences()
    {
        var source = new[] { 4, 8, 15, 16, 23, 42 }.ForbidMultipleEnumeration();
        var other = new[] { 4, 8, 15, 99, 123, 999 }.ForbidMultipleEnumeration();
        var result = source.CommonPrefix(other);
        result.Should().Equal(4, 8, 15);
    }

Ah, Should().Equal(). That was my question ;-)

The workaround is easy, I just need to call ToList() on the result to materialize it. But I think it would be better for FA to enumerate only once, if it's possible.

Agreed


WIP: Add GA to event log

We planned to convert everything to ES6 or TS eventually.
These modules are trivial and plain JS should be enough.
It makes the repo simpler and doesn't require the build step.
On Thu, Jan 12, 2017 at 2:31 AM, Page-<EMAIL_ADDRESS>wrote:

@Page- commented on this pull request.
In packages/resin-event-log/CHANGELOG.md
https://github.com/resin-io-modules/resin-analytics/pull/1#pullrequestreview-16261356
:

@@ -1,3 +1,5 @@
+* Convert to JS

Why?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/resin-io-modules/resin-analytics/pull/1#pullrequestreview-16261356,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAgGCKsJkT-LnhD57VbSANgjJH13jBA5ks5rRWZJgaJpZM4LfPlY
.

--
Eugene Mirotin
Senior Frontend Engineer
site: Resin.io https://resin.io/, twitter: @resin_io
https://twitter.com/resin_io

Yeah, but it was just easier to take the CS-built files and clean up a bit.
I can later convert to TS from this rather than directly from CS.
On Thu, Jan 19, 2017 at 1:38 AM, Page-<EMAIL_ADDRESS>wrote:

@Page- commented on this pull request.
In packages/resin-event-log/CHANGELOG.md
https://github.com/resin-io-modules/resin-analytics/pull/1:

@@ -1,3 +1,5 @@
+* Convert to JS

Right, ES6 or TS, with compilation to ES5 for the time being but this
isn't either of those
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/resin-io-modules/resin-analytics/pull/1, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAgGCK5evN2o0ERsKx0g6h0JIRFKZzWgks5rTpRTgaJpZM4LfPlY
.

--
Eugene Mirotin
Senior Frontend Engineer
site: Resin.io https://resin.io/, twitter: @resin_io
https://twitter.com/resin_io

Thanks, missed that when converting.
On Thu, Jan 19, 2017 at 1:39 AM, Page-<EMAIL_ADDRESS>wrote:

@Page- commented on this pull request.
In packages/resin-mixpanel-client/README.md
https://github.com/resin-io-modules/resin-analytics/pull/1#pullrequestreview-17344034
:

-...
-if eventType is 'signup'

MixpanelClient.signup userId, -> # optional callback
+if (eventType is 'signup') {

These examples use is which is coffee-script only
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/resin-io-modules/resin-analytics/pull/1#pullrequestreview-17344034,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAgGCDpY8qiX3XzIKXpPYeX9x3ovOS9Oks5rTpSRgaJpZM4LfPlY
.

--
Eugene Mirotin
Senior Frontend Engineer
site: Resin.io https://resin.io/, twitter: @resin_io
https://twitter.com/resin_io

@pimterry if you have some time could you have another look please?
I've managed to make the XHR mocking work (I had to fork and improve a bit an xhr-mock lib) which actually helped me identify some issues in my code (mixpanel library is replacing the global object instead of patching it, and my code was plucking it from window).
But I still can't make the GA tests pass in the browser — it doesn't seem to do the XHR requests, but I have no idea why.
With mixpanel it was simpler to debug as they provide the unminified version of their code which I've configured for the tests.
But I didn't find the same for GA.
So now Mixpanel tests pass everywhere (but are skipped atm), and GA passes in Node but not in the browser.

@emirotin Ok, got it: you haven't configured GA a tracking config for the command you're trying to run (resinAnalytics.send). You need to call ga('create', 'UA-XXXXX-1', 'auto', 'resinAnalytics') before that command, or the ga code doesn't know where to send the event. From your code, it looks like you're expecting something to do that by calling login, but there's nothing in the tests that does that. If you do, it should work I think. I've manually run the create command before the tests, and that does fix it.
If you do that, it does then successfully make requests, which is the first step. They don't get mocked though, because GA doesn't actually use XHR by default - it loads a tracking pixel. You can configure this by setting the transport explicitly though, and they do have an XHR option: https://developers.google.com/analytics/devguides/collection/analyticsjs/field-reference#transport. I haven't played with that further, but there should be a route through there I think. Let me know if you want me to dig in more there though.
Btw, for debugging this generally, if you swap out https://www.google-analytics.com/analytics.js for https://www.google-analytics.com/analytics_debug.js (see the GA debugging guide) it'll give you errors, and you can chase things down from there. That doesn't give you unminified code, but it's just about enough enough anyway.

Woah man great investigation, thanks.
I supposed the login method is called but apparently not — will fix.
I tried to find the GA debugging tips but failed. Will use, thanks!
On Fri, Feb 3, 2017 at 4:26 PM, Tim Perry<EMAIL_ADDRESS>wrote:

@emirotin https://github.com/emirotin Ok, got it: you haven't
configured GA a tracking config for the command you're trying to run (
resinAnalytics.send). You need to call ga('create', 'UA-XXXXX-1', 'auto',
'resinAnalytics') before that command, or the ga code doesn't know where
to send the event. From your code, it looks like you're expecting something
to do that by calling login, but there's nothing in the tests that does
that. If you do, it should work I think. I've manually run the create
command before the tests, and that does fix it.
If you do that, it does then successfully make requests, which is the
first step. They don't get mocked though, because GA doesn't actually use
XHR by default - it loads a tracking pixel. You can configure this by
setting the transport explicitly though, and they do have an XHR option:
https://developers.google.com/analytics/devguides/
collection/analyticsjs/field-reference#transport. I haven't played with
that further, but there should be a route through there I think. Let me
know if you want me to dig in more there though.
Btw, for debugging this generally, if you swap out
https://www.google-analytics.com/analytics.js for
https://www.google-analytics.com/analytics_debug.js (see the GA debugging
guide
https://developers.google.com/analytics/devguides/collection/analyticsjs/debugging)
it'll give you errors, and you can chase things down from there. That
doesn't give you unminified code, but it's just about enough enough anyway.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/resin-io-modules/resin-analytics/pull/1#issuecomment-277246067,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAgGCGd71sgi4WOPAZdVkRKhImfbQsqtks5rYyr0gaJpZM4LfPlY
.

--
Eugene Mirotin
Senior Frontend Engineer
site: Resin.io https://resin.io/, twitter: @resin_io
https://twitter.com/resin_io

Meh... I did all the fixes mentioned above (and some extra) and I see the requests being mocked etc. I've also added some timeout because I supposed GA may have some kind of buffering or just to make the check in a separate task.
And now I see something really weird.
When running manually in the browser I can now see both GA tests passing.
But when running from the CLI (npm run test-browser in the packages/resin-event-log folder) the first test always fails and the 2nd usually passes.

When running manually in the browser I can now see both GA tests passing.
But when running from the CLI (npm run test-browser in the packages/resin-event-log folder) the first test always fails and the 2nd usually passes.

@emirotin That's very strange, and I can reproduce it locally too. Sounds like a race somewhere from unusual behaviour in Phantom. You can debug phantom in Chrome (http://phantomjs.org/troubleshooting.html#remote-debugging) if you set debug: true in the phantom launcher for karma, which might come up with some clues. I'd guess that it's some kind of race condition between either GA and our test code loading, or between the GA requests and our assertions, but it's very hard to know much more without looking deeper. Happy to dig in more and help out if you'd like, let me know if you need a hand.

So by adding some logging I can tell that the first request does not reach the XHR mocking code.
If I repeat the test case or just double the call in one test case the first call never hits the XHR mocking code. Interesting, continue observation.

I don't think it's a race condition as I've added logging and I see that the XHR mocking code is not hit for the first request at all

Pushed my code with logging.

Interesting. It's something with mocking, the request reaches the mocked XHR but is not handled.
At least it's not something with GA and looks like race condition indeed

Argh, the first request goes to https://www.google-analytics.com/r/collect, notice the /r/

Great, now some mocking doesn't work for mixpanel, lol (as I've added the call to login I now have to mock the /engage endpoint, but nock doesn't receive this mock for some reason)

Now I'm left with this single problem.
Let's look at this code:
return Promise.fromCallback(function (callback) {
				var login = function() {
					mixpanel.login(user.username, function() {
						mixpanel.setUserOnce(mixpanelUser, callback)
					})
				}

				if (mixpanelUser.$created) {
					mixpanel.signup(user.username, function() {
						login()
					})
				} else {
					login()
				}

			})

Behind the scenes mixpanel.login does identify (actual mixpanel lib's method), and mixpanel.setUserOnce does people.set_once
In the browser both first hit the dumb queue created by the mixpanel-loader script.
Then the actual library loads and picks up the queue.
For some reason it first runs the set_once method and then the identify.
Unfortunately, the former checks if identify was called before it and returns an error otherwise.
There's also no callback from the mixpanel side to ensure identify was actually performed.
@pimterry if you have any good ideas that would be helpful.
I've already spent couple of hours fixing other bugs so right now just hate this piece of code :)

Ok, I've done some digging. Conclusion:

These two functions are indeed queued while the library loads, but they are actually retrieved from the queue correctly.
What's happening is that Mixpanel is calling people.set_once before identify on purpose, because a later identify will automatically flush people.X requests anyway.
When set_once is called before identify though (which is pretty much guaranteed if you call them both on first load, because of this behaviour), then it does indeed enqueue itself to wait for identify, but it doesn't enqueue the callback: for some crazy reason it calls it immediately with -1.
Later, the request does look like it gets sent, once the identify actually flushes, so that's good. The behaviour isn't actually broken, just how it calls the callback. I've filed a bug.

I think you said these tests were passing before? I haven't chased down exactly how that changed, but I think it's related to some bugs in our own mixpanel code that I found along the way:

We wrap the mixpanel callbacks, to fix their poor callback behaviour, but we only check for 0 as a result to consider as an error, and in this case -1 is an error too. Currently, we consider -1 as a successful result and we'd happily resolve the promise with that value, which makes this look successful, even though the request hasn't even been attempted yet.
That issue was hidden by a different bug: in resin-mixpanel-client, in both setUser and setUserOnce, we wrap the third callback argument, to fix this callback behaviour. The 2nd argument is optional though, so often the callback appears in the 2nd position instead (e.g. mixpanel.setUserOnce(mixpanelUser, callback)), and in that case we don't wrap it, and you get different behaviour.
If previously we were supplying all three arguments, then this test would pass, because of how these two bugs interact.

Phew. Anyway, given all this, I think they're assuming that either nobody depends on the callbacks with set_once, or at least that nobody uses callbacks while also calling set_once immediately on page load.
I do have a solution though: mixpanel.init() takes an options object we're not using at the moment, and if you provide a loaded() callback it seems to wait until after the library is loaded. If you call identify only after that happens, then everything will happen in the right order. You'll need some refactoring to make that work nicely (since library setup is now async), and you'll also need to fix those couple of bugs above too.

Great investigation, as usual.
The tests didn't call .start() before, that's why they were passing.
Will look into the bugs (I'm not sure about the one with treating -1 as success, it definitely leads to rejection with -1 at some point, but I'll see).
In the worst case we can have the special handling for -1 in set_once and discard it.
Thanks a lot!

Hm, I think the _set_once_callback:function is a better way to go here [https://github.com/mixpanel/mixpanel-js/blob/b4cf2c5cb900fbb102370c01553e9a70f4c6e2d0/src/mixpanel-core.js#L1336], will try it.

Good find! Yes, that'll work even better.
And yes, it does reject with -1 right now, but that's because of how the two bugs combine. The first bug means we only consider 0 as an error case when we wrap the callbacks (so it looked successful before), but the 2nd bug means currently we don't wrap this callback at all, and we'll actually consider any of mixpanel's callback responses to be a error.
In the successful case, I think the only good response is 1 - we should probably just check for that. That's because the callback eventually (in non-verbose mode) is called with the response body, as a number and the body of the HTTP response for all tracking methods is 1 (...because there is no other numerical way to signal success in HTTP responses...).

So just sorting out the callbacks wrapping fixed it. Great catch, I was blind having looked at this code for too many times :)
An yes, as you've described it's because -1 is now treated as success. Will try using this (undocumented, sigh) callback now.

Now another issue.
We do first call mixpanel.alias if it's signup, and then mixpanel.identify (unconditionally)
The thing is alias does call identify behind the scenes which causes the queues flushing which calls set_once first, then identify (which I've now made accepting the _set_once_callback is called and the callback is not because the queue is already flushed.
Have refactored and testing it currently.

Argh! It doesn't work because alias doesn't accept the same callback params 🙄
https://github.com/mixpanel/mixpanel-js/blob/b4cf2c5cb900fbb102370c01553e9a70f4c6e2d0/src/mixpanel-core.js#L1402

Generally seems like this mixpanel library is not great tbh.
Can we not use the init callback? It makes the initial library setup asynchronous, which is annoying, but it should mean we can guarantee that we'll be past all the queues and flushing before we start doing any of the interesting work.

Yeah not great at all. Will check what it takes to use it.

I will squash many commits now to simplify the review

Ready for the review now. Better to do commit-by-commit. Some of them are big but only represent the changes like replacing CS with the compiled JS. The last but one is the one that actually adds GA and refactors lots of stuff.


Following quickstart and SPA sends an opaque token to backend

I've asked the initial question here: https://github.com/auth0/angular-jwt/issues/157
I have 2 clients set up, one for the Angular 1 SPA, and one for the Python/Flask API. Both set to HS256.
When logging in via the hosted page, the callback to my SPA is in seemingly in the correct format:
https://myapp.com/callback#access_token=NLcH4l337-d-8D7x&expires_in=7200&token_type=Bearer&state=g02VgjgHLGU.ZDFBEEF1S5Fj5El8ZI8X&id_token=abc.xyz.def

However, the SPA sends (what I'm told) an opaque token to my API:
Authorization: Bearer NzmWR9AfD40PEYfC

Please let me know where in my travels I might have made the wrong turn. Thanks!

I simply have to change this line to get id_token from localStorage instead of the opaque access_token:
https://github.com/auth0-samples/auth0-angularjs-samples/blob/a28650bd2b6ce227f2ef73c5f9679c8bab1b4bb7/03-Calling-an-API/app/app.js#L65

Reopening as switching to the ID token isn't the solution. You need to send the access token to your API and not the ID token.
There's likely a problem with how you have your API authorization configured. You need to get a JWT for your access token and not an opaque access token like you're getting now. Can you paste your auth0.WebAuth config here?

Hi Ryan, thanks for the reply. Here you go:
angularAuth0Provider.init({
      clientID: '6FYq0WqAS3ZHS5Zv9A8OSKD1eyWZDFTi',
      domain: 'mydomain.eu.auth0.com',
      responseType: 'token id_token',
      audience: 'https://api.mydomain.com',
      redirectUri: 'https://www.mydomain.com/callback',
      scope: 'openid profile email'
    });

(using a fake clientID for this issue)

Thanks
Can you confirm that you've created your API in the APIs section of the dashboard and that its identifier is the URL you've got as your audience there?

The audience is the API's ID. But...
It works now - perhaps it's support who made a change to my account or my random settings fiddling earlier propagated finally.
Thanks for looking into this.


Fix incorrect subscription on demo

🦟 Bug fix
Summary
This PR fixes an incorrect subscription on one of the demos. Running
ros2 launch ros_gz_sim_demos gpu_lidar_bridge.launch.py

causes rviz2 to crash and exit with the error:
rviz2-3]
[rviz2-3] >>> [rcutils|error_handling.c:108] rcutils_set_error_state()
[rviz2-3] This error state is being overwritten:
[rviz2-3]
[rviz2-3]   'create_subscription() called for existing topic name rt/lidar with incompatible type sensor_msgs::msg::dds_::PointCloud2_, at ./src/subscription.cpp:146, at ./src/rcl/subscription.c:108'
[rviz2-3]
[rviz2-3] with this new error message:
[rviz2-3]
[rviz2-3]   'invalid allocator, at ./src/rcl/subscription.c:218'
[rviz2-3]
[rviz2-3] rcutils_reset_error() should be called after error handling to avoid this.

This is due to an incorrect subscription on the part of the demo. This PR fixes it by getting a subscription to the right topic for the pointcloud display. (lidar/points instead of lidar). Was tested on garden + humble.
Checklist

[x] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.
🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸

I'm not sure how forward porting works. This fix needs to also be applied to rolling and other branches.

If you have time to cherry-pick this change let me know, Otherwise I will create the PRs


BAD BUG REMAINED OPEN!

Issue Type: Bug
THIS ISSUE WAS BAD INTERPRETED BY EVERYONE:
https://github.com/Microsoft/vscode/issues/39988
connected with this
https://github.com/Microsoft/vscode/issues/15949
what i want to say is that isn´t that when opening a xml file for example via explorer, its wrong that an empty workspace is opened... BUT, the question is that EVEN if u close it, and reopen via ICON, ppl want that the workspace that it always used to be get back including open windows tabs preferrably.
in the first topic that settings is related with multiple IDE WINDOWS, not document tabs
and the second tab hotfix setting seems nothing to do with this for me too...
i think that one possible mid term solution (that dont breaks anything) could it be... when opening a single file in explorer... uses a NEW window, with empty workspace...
plz fix that! :D
Thanks.
VS Code version: Code 1.27.0 (7b9afc4196bda60b0facdf62cfc02815509b23d6, 2018-09-05T05:29:44.670Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz (8 x 2295)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
7.88GB (2.72GB free)

Process Argv
C:\Users\Xtronoid\AppData\Local\Programs\Microsoft VS Code\Code.exe

Screen Reader
no

VM
0%

Extensions (9)

Extension
Author (truncated)
Version

overtype
ada
0.2.0

npm-intellisense
chr
1.3.0

xml
Dot
2.3.2

beautify
Hoo
1.4.2

Angular2
joh
6.1.5

team
ms-
1.136.0

debugger-for-chrome
msj
4.9.1

nativescript
Tel
0.8.0

nativescript-ng2-snippets
www
2.0.1

Sorry but this is not readable. Please follow this guide to file a proper issue report. Start with:

Steps to reproduce the proble,
What you expected to happen.
What actually happened.

-> open vs code via associated file in explorer
-> i want new window with empty workspace (for not breaking some compatibilites as mentioned in that posts, dont need to be the same one)
-> watch it:
a) replace your workspace with an empty one
b) or - if not already open a window with your workspace, it will open a window with empty workspace and even after you close that, and reopen via icon u are not in your workspace anymore

Pretty Anyonning,
Thanks.

Sorry I do not understand. You can configure window.openFilesInNewWindow: on to force open files in separate windows. Does that help?

Hi there!
Well, this helps surely! thanks! But... if you dont already have an open window, it will change it to the empty workspace, even opening by icon later...

@xtronoid so you want to restore the last opened workspace when opening a single file via doubleclick and add it there?

no...
i meant that if there´s no one open window before... it makes the empty the default one forever... got it?

@xtronoid what do you mean by "default"? You mean it restores itself next time you just start VSCode?

let me help u solve it:

An empty (new) workspace (that was created and switched to via click on file) dont have to got precedence over your saved and nice workspace! simple 💯

about your question... yes it restores the new empty each time you open via icon after, one time opened by file

@xtronoid so to recap, you suggest to:

if no window is open and you open a file, open it within the last workspace that was opened
if a window is open and you open a file, open it in a new empty window

the second item u said now, was fixed creating in another one empty (the settings you helped me)
but the first item.... no... the first item... is a suggestion that someone said that can broken somethings like git or i dunno what...
so i suggested a fix to the first item that´s less intrusive... that´s as i said:
im saying about not what i want. but what´s happening:
if you got no one window open with your workspace,
then click on file,
it opens in a new empty workspace OK <- would be cooler yet if it mantains your actual workspace, BUT if it brokens something, it will be a bad choice.
so again... i suggest that AT LEAST:
afterrrrr you opent the file, after closssssed, then when you open it again via icon... it dont goes to the empty as a default forever! (but back to YOUR WORKSPACE! and not the new not saved one) got it?? lol

@xtronoid how does that make any sense though, it seems to me that introduces very unpredictable behaviour for the user.

None taken.

u can close it, but i just sayin that the empty one when u click via file, must not turn to be the default one! so u can click on the icon shortcut and starts normally back in your workspace...
or if isn´t really a problem, open in the same workspace and not in the new....
so simple

If it helps, what I think he means is this.
1: You close a workspace. Normally when you re-open Code it opens the last used workspace.
2: You then open a single file Code by using the file explorer context menu, but this should open in an empty workspace.
3: When you close the 2nd workspace above and open VS Code normally through the start menu / icon, it should open the 1st workspace again.
Basically opening a file via context menu should not override the "last opened workspace".


Improper handling of ISO 8601 time zone designator

The DateConverter class ignores the time zone designator in ISO 8601. For example, 2019-03-15T14:04:59-05:00 becomes local date time of 2019-03-15 14:04:59, completely ignoring the local time zone.  When translated to UTC it should be 2019-03-15T19:04:59+00:00.

Replacing all LocalDateTime references with ZonedDateTime so that the time zone designator will no longer be ignored.