duplicated tab names and missing arrows

I see the "buffers" flag at the top right when I have only one tab opened, when I open another one it shows the tab names both at the top right and left, with the left one missing the arrows. Spent two hours last night fighting with it.  Also I am wondering, why you wouln't see the correct separators. Can you show the output of airline#extensions#tabline#get()?

It doesn't matter if I use gnome-terminal or LXTerminal (Lubuntu's native). Also, when you say "correct separators", you're talking about the first image, right? The second one I just googled... all the other separators work just fine, just the tabones don't show up.
But maybe we're on the right track, airline#extensions#tabline#get() yields: E492: Not an editor command: airline#extensions#tabline#get().

Well, thanks to your suggestion I did the obvious and read again the README.md and noticed I could change the tabs separators, they're now OK, with my so desired arrows.... but that duplicate thing still happens... probably because of that E492... but I do have let g:airline#extensions#tabline#enabled = 1 in my .vimrc (actually vim.init since I'm in nvim, but the same happens in VI as I pointed). So I'm clueless again...

you should use :echo airline#extensions#tabline#get()? You need an actual command before the function name, that's why you see the error E492.  BTW: What exactly is the problem now?

I face same issue
My os: Archlinux
My term: Termite
Output of echo airline#extensions#tabline#get()
%1@airline#extensions#tabline#buffers#clickbuf@%#airline_tabhid# %(%{airline#extensions#tabline#get_buffer_name(1)}%) %X%2@airline#extensions#tabline#buffers#clickbuf@  %(%{airline#extensions#tabline#get_buffer_name(2)}%) %X%3@airline#extensions#tabline#buffers#clickbuf@  %(%{airline#extensions#tabline#get_buffer_name(3)}%) %X%4@airline#extensions#tabline#buffers#clickbuf@  %(%{airline#extensions#tabline#get_buffer_name(4)}%) %X%5@airline#extensions#tabline#buffers#clickbuf@  %(%{airline#extensions#tabline#get_buffer_name(5)}%) %X%6@airline#extensions#tabline#buffers#clickbuf@%#airline_tabhid_to_airline_tabsel# %#airline_tabsel# %(%{airline#extensions#tabline#get_buffer_name(6)}%) %X%#airline_tabsel_to_airline_tabfill# %#airline_tabfill#%=%#airline_tabfill_to_airline_tabfill# %#airline_tabfill#%#airline_tabfill_to_airline_tabtype# %#airline_tabtype# buffers

may be the issue caused by tmux, I start vim without tmux and no face this issue

I solved my issue, downgrade tmux to 2.3.1

@chrisba sorry for such late delay, couldn't look at it ealier, thanks for reaching out.
So, the output now is (copy/paste):
%1@airline#extensions#tabline#buffers#clickbuf@%#airline_tabsel# %(%{airline#extensions#tabline#get_buffer_name(1)}%) %X%#airline_tabsel_to_airline_tabfill#%#airline_tab
fill#%=%#airline_tabfill_to_airline_tabfill#%#airline_tabfill#%#airline_tabfill_to_airline_tabtype#%#airline_tabtype# buffers

tried using it outside tmux and it still happens...

Is the character shown in echo airline#extensions#tabline#get()the expected one?

that the left and the right side contain the same name is expected. The left side show the actual buffers open, the right side show the buffer in the current tabpage.

@chrisbra totally missed that detail. So, in the end, the people who see "buffers" written in the top right are the ones experiencing a problem.


Add support for customizing axis label as well as title of the plots

Currently, the user cannot customize the axis label and the title of a plot. It's good if we could provide a built-in support for this.

Thanks for the issue, @JustinaPetr will get back to you about it soon!
You may find help in the docs and the forum, too 🤗

With the advent of features like https://github.com/RasaHQ/whatlies/issues/129 I wonder what the best approach is here. One concern I have is that the plot method might get "super full of variables". Especially if we're also considering another backend like Bokeh.
Might it be enough to document how to work with Altair? Something like;
(lang[text]
  .transform(Umap(2))
  .plot_interactive("umap_0", "umap_1", annot=False)
  .properties(title="spaCy", height=200, width=200))

If possible, I'd prefer to relay customisation of the plots to the user. The feature list of customisation options can get really big.

If possible, I'd prefer to relay customisation of the plots to the user. The feature list of customisation options can get really big.

All right, agreed If you think that's a lot to offer and might not noticeably make the user life easier; although, personally, when I see a method with lots of arguments I cheer up because it gives more freedom to do various things in a builtin-way and without me to take care of it implementation. On the other hand, that's also a fair point to consider the current stage and scope of the library.

For this issue then we'd consider an addition to the documentation to also be a valid solution?

For this issue then we'd consider an addition to the documentation to also be a valid solution?

Yeah, if the plan is to not support these. We can add a note or an example to the documentation or FAQ section for further configuring the plots.

I'll make a PR that adds this to the FAQ. That should help.

I've made a PR here https://github.com/RasaHQ/whatlies/pull/136 but it seems like renaming the axes is not supported via .properties. This is making me wonder if we do need to add it as a feature. I can certainly see people wanting to customise the axes.

I've stumbled across a related issue.

If we apply operations on embeddings then the name updates. Unfortunately this makes certain interactive charts verbose. It'd be nice if there was an easier way to deal with this. We could change the standard that we won't take the name of an Embedding but rather the orig property. But maybe there's something more elegant that we can do with plot settings.

This is making me wonder if we do need to add it as a feature. I can certainly see people wanting to customise the axes.

I also have the same thought. For example, in for EmebeddingSet.plot when x_axis and y_axis are string values, they are used to fetch projection embedding (for 3D+ embedding case). But there is a conflict for 2D case: should they be used for label of axis or fetching embedding? That's one more reason that we should also provide x_label and y_label argument for plot methods and completely separate them from x_axis and y_axis arguments (of course, if x_axis is an Embedding and x_label is not provided we use the name of embedding; though, the preference is always given to x_label if set).

@koaning This was implemented for matlplotlib plots, i.e. plot method. After all the discussion here, is the final decision to implement it for Altair plots as well, or should this issue be closed?

I saw you've already made the PR but I'd say this is indeed also valid for Altair.

@mkaze I think this issue can be closed. Just to check, agree?

@mkaze I think this issue can be closed. Just to check, agree?

Actually, a few days ago, I was thinking whether other plot methods like plot_interactive_matrix should support these or not. So, I am not sure.

I'm closing issues because ever since the project moved to my personal account it's been more into maintenance mode than a "active work" mode.


Change paths for js

Updating codeql.yml following refactor which is now creating js files instead of mjs.

@stoe, just noticed that utils\ActionPolicy.mjs is still using the mjs extension, do you anticipate to change this:

To js also
Or should the codeql.yml file include both mjs and js?


Integrating Pre- commit hook

Feature Request 🛍

Pre-commit hooks should be integrated into the project to prevent the push of bad code( not linted properly and others).
Context

Currently, if someone pushes the code into the repo which is not properly linted there is no check on it. This can cause inconsistencies in code. This feature would prevent this from happening.
Detailed Description

Some info regarding the pre-commit hooks

Can I take it up?

@Aniruddha-Shriwant
Actually I am gonna work upon this. I think i forgot to write would you like to work on this😅

I think i forgot to write would you like to work on this😅

Yeah that's why I asked if I can take this up 😅

@algomaster99
I have made a PR for the issue. Let me know if there are any changes required.


Error when running DeepSpeed integration test with Rocm 62

I was trying to build ACPT ROCm 62 image but encountered below error while running deepspeed integration test and failed withWorker 0 killed by signal 6

:0:rocdevice.cpp            :2984:<PHONE_NUMBER>7254 us: [pid:213   tid:0x7f59bcd69700] Callback: Queue 0x7f59d8000000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016

OS_TYPE=ubuntu2004
GPU_TYPE=rocm62
DESIRED_PYTHON=39
PYTORCH_TYPE=stable
PYTORCH_VERSION=221

deepspeed=0.15.1
horovod=0.24.2
torch_nebula=0.16.13
nebulaml=0.16.13
onnxruntime_training=1.18.0
torch_ort=1.18.0

The below is part of the error logs
2024-10-16T19:14:55.7825728Z =================================== FAILURES ===================================
2024-10-16T19:14:55.7826479Z ________________________________ TestInit.test _________________________________
2024-10-16T19:14:55.7828304Z Worker 0 killed by signal 6
2024-10-16T19:14:55.7830382Z ----------------------------- Captured stdout call -----------------------------
2024-10-16T19:14:55.7831792Z [2024-10-16 19:13:18,383] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.7833100Z [2024-10-16 19:13:18,388] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.7833950Z [2024-10-16 19:13:20,019] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.7834714Z [2024-10-16 19:13:20,048] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.7835574Z [2024-10-16 19:13:20,048] [INFO] [comm.py:683:init_distributed] Initializing TorchBackend in DeepSpeed with backend nccl
2024-10-16T19:14:55.7836438Z ----------------------------- Captured stderr call -----------------------------
2024-10-16T19:14:55.7837421Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.7838218Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.7839213Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.7840042Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.7840923Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>7254 us: [pid:213   tid:0x7f59bcd69700] Callback: Queue 0x7f59d8000000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.7842092Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>7424 us: [pid:212   tid:0x7f59bed69700] Callback: Queue 0x7f59d8400000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.7843173Z _______________ TestDistArgs.test[hello-icosahedron-1138-purple] _______________
2024-10-16T19:14:55.7843670Z Worker 0 killed by signal 6
2024-10-16T19:14:55.7844300Z ---------------------------- Captured stderr setup -----------------------------
2024-10-16T19:14:55.7845070Z /opt/conda/envs/ptca/lib/python3.9/multiprocessing/resource_tracker.py:216: UserWarning: resource_tracker: There appear to be 3 leaked semaphore objects to clean up at shutdown
2024-10-16T19:14:55.7845925Z   warnings.warn('resource_tracker: There appear to be %d '
2024-10-16T19:14:55.7846625Z ----------------------------- Captured stdout call -----------------------------
2024-10-16T19:14:55.7847477Z [2024-10-16 19:13:24,186] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.7848443Z [2024-10-16 19:13:24,187] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.7849314Z [2024-10-16 19:13:25,848] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.7850186Z [2024-10-16 19:13:25,848] [INFO] [comm.py:683:init_distributed] Initializing TorchBackend in DeepSpeed with backend nccl
2024-10-16T19:14:55.7851016Z [2024-10-16 19:13:25,850] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.7851761Z ----------------------------- Captured stderr call -----------------------------
2024-10-16T19:14:55.7852772Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.7853562Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.7854814Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.7855608Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.7856464Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>3558 us: [pid:394   tid:0x7fa6840bd700] Callback: Queue 0x7fa697200000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.7857605Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>4337 us: [pid:393   tid:0x7fa6820bd700] Callback: Queue 0x7fa69d300000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.7858469Z ______________________ TestGroupedDistTest.test_one[1138] ______________________
2024-10-16T19:14:55.7858965Z Worker 0 killed by signal 6
2024-10-16T19:14:55.7859607Z ---------------------------- Captured stderr setup -----------------------------
2024-10-16T19:14:55.7860378Z /opt/conda/envs/ptca/lib/python3.9/multiprocessing/resource_tracker.py:216: UserWarning: resource_tracker: There appear to be 3 leaked semaphore objects to clean up at shutdown
2024-10-16T19:14:55.7861405Z   warnings.warn('resource_tracker: There appear to be %d '
2024-10-16T19:14:55.7862090Z ----------------------------- Captured stdout call -----------------------------
2024-10-16T19:14:55.7862953Z [2024-10-16 19:13:29,047] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.7863888Z [2024-10-16 19:13:29,051] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.7864725Z [2024-10-16 19:13:30,661] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.7865578Z [2024-10-16 19:13:30,661] [INFO] [comm.py:683:init_distributed] Initializing TorchBackend in DeepSpeed with backend nccl
2024-10-16T19:14:55.7866416Z [2024-10-16 19:13:30,683] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.7867142Z ----------------------------- Captured stderr call -----------------------------
2024-10-16T19:14:55.7868121Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.7868887Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.7869864Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.7870633Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.7871501Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>9082 us: [pid:575   tid:0x7f2bd7506700] Callback: Queue 0x7f2bea800000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.7872647Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>9094 us: [pid:574   tid:0x7f2bd7506700] Callback: Queue 0x7f2bea400000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.7873582Z ______________________ TestGroupedDistTest.test_two[1138] ______________________
2024-10-16T19:14:55.7874077Z Worker 0 killed by signal 6
2024-10-16T19:14:55.7874718Z ---------------------------- Captured stderr setup -----------------------------
2024-10-16T19:14:55.7875478Z /opt/conda/envs/ptca/lib/python3.9/multiprocessing/resource_tracker.py:216: UserWarning: resource_tracker: There appear to be 3 leaked semaphore objects to clean up at shutdown
2024-10-16T19:14:55.7876330Z   warnings.warn('resource_tracker: There appear to be %d '
2024-10-16T19:14:55.7877132Z ----------------------------- Captured stdout call -----------------------------
2024-10-16T19:14:55.7878053Z [2024-10-16 19:13:33,899] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.7879009Z [2024-10-16 19:13:33,931] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.7879833Z [2024-10-16 19:13:35,510] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.7880703Z [2024-10-16 19:13:35,511] [INFO] [comm.py:683:init_distributed] Initializing TorchBackend in DeepSpeed with backend nccl
2024-10-16T19:14:55.7881530Z [2024-10-16 19:13:35,706] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.7882270Z ----------------------------- Captured stderr call -----------------------------
2024-10-16T19:14:55.7883287Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.7884235Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.7885221Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.7886005Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.7886889Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>6307 us: [pid:756   tid:0x7f6084ccb700] Callback: Queue 0x7f60a2700000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.7888023Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>6349 us: [pid:755   tid:0x7f608cccb700] Callback: Queue 0x7f60a0400000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.7888907Z _______________ TestWorldSizeOverrideDistTest.test_world_size_2 ________________
2024-10-16T19:14:55.7889406Z Worker 0 killed by signal 6
2024-10-16T19:14:55.7890054Z ---------------------------- Captured stderr setup -----------------------------
2024-10-16T19:14:55.7890827Z /opt/conda/envs/ptca/lib/python3.9/multiprocessing/resource_tracker.py:216: UserWarning: resource_tracker: There appear to be 3 leaked semaphore objects to clean up at shutdown
2024-10-16T19:14:55.7891683Z   warnings.warn('resource_tracker: There appear to be %d '
2024-10-16T19:14:55.7892369Z ----------------------------- Captured stdout call -----------------------------
2024-10-16T19:14:55.7893218Z [2024-10-16 19:13:38,887] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.7894173Z [2024-10-16 19:13:38,892] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.7894995Z [2024-10-16 19:13:40,552] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.7895869Z [2024-10-16 19:13:40,552] [INFO] [comm.py:683:init_distributed] Initializing TorchBackend in DeepSpeed with backend nccl
2024-10-16T19:14:55.7896695Z [2024-10-16 19:13:40,658] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.7897483Z ----------------------------- Captured stderr call -----------------------------
2024-10-16T19:14:55.7898464Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.7899251Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.7900227Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.7901128Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.7902153Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>6048 us: [pid:937   tid:0x7f4ab8921700] Callback: Queue 0x7f4acba00000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.7903349Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>6290 us: [pid:936   tid:0x7f4ab6921700] Callback: Queue 0x7f4ac9800000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.7904230Z ____________________________ TestDistAllReduce.test ____________________________
2024-10-16T19:14:55.7904735Z Worker 0 killed by signal 6
2024-10-16T19:14:55.7905392Z ----------------------------- Captured stdout call -----------------------------
2024-10-16T19:14:55.7906251Z [2024-10-16 19:13:49,398] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.7907095Z [2024-10-16 19:13:51,203] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.7907962Z [2024-10-16 19:13:51,203] [INFO] [comm.py:683:init_distributed] Initializing TorchBackend in DeepSpeed with backend nccl
2024-10-16T19:14:55.7908915Z [2024-10-16 19:13:55,102] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.7909856Z [2024-10-16 19:13:55,149] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.7910695Z [2024-10-16 19:13:56,721] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.7911436Z [2024-10-16 19:13:56,757] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.7912301Z [2024-10-16 19:13:56,757] [INFO] [comm.py:683:init_distributed] Initializing TorchBackend in DeepSpeed with backend nccl
2024-10-16T19:14:55.7913125Z ----------------------------- Captured stderr call -----------------------------
2024-10-16T19:14:55.7914161Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.7914958Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.7915947Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.7916723Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.7917705Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.7918480Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.7919352Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>5016 us: [pid:1301  tid:0x7f17869d0700] Callback: Queue 0x7f1799c00000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.7920502Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>5018 us: [pid:1300  tid:0x7f17869d0700] Callback: Queue 0x7f1799800000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.7921386Z _____________________ TestDistInit.test_already_init[True] _____________________
2024-10-16T19:14:55.7921880Z Worker 0 killed by signal 6
2024-10-16T19:14:55.7922516Z ---------------------------- Captured stderr setup -----------------------------
2024-10-16T19:14:55.7923293Z /opt/conda/envs/ptca/lib/python3.9/multiprocessing/resource_tracker.py:216: UserWarning: resource_tracker: There appear to be 3 leaked semaphore objects to clean up at shutdown
2024-10-16T19:14:55.7924147Z   warnings.warn('resource_tracker: There appear to be %d '
2024-10-16T19:14:55.7924848Z ----------------------------- Captured stdout call -----------------------------
2024-10-16T19:14:55.7925839Z [2024-10-16 19:14:00,866] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.7926795Z [2024-10-16 19:14:00,934] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.7927624Z [2024-10-16 19:14:02,553] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.7928367Z [2024-10-16 19:14:02,556] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.7929095Z ----------------------------- Captured stderr call -----------------------------
2024-10-16T19:14:55.7930076Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.7930857Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.7931833Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.7932636Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.7933505Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>7589 us: [pid:1481  tid:0x7f2f401df700] Callback: Queue 0x7f2f53000000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.7934663Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>7827 us: [pid:1482  tid:0x7f2f3a1df700] Callback: Queue 0x7f2f53800000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.7935541Z ____________________ TestDistInit.test_already_init[False] _____________________
2024-10-16T19:14:55.7936032Z Worker 0 killed by signal 6
2024-10-16T19:14:55.7936664Z ---------------------------- Captured stderr setup -----------------------------
2024-10-16T19:14:55.7937449Z /opt/conda/envs/ptca/lib/python3.9/multiprocessing/resource_tracker.py:216: UserWarning: resource_tracker: There appear to be 3 leaked semaphore objects to clean up at shutdown
2024-10-16T19:14:55.7938296Z   warnings.warn('resource_tracker: There appear to be %d '
2024-10-16T19:14:55.7938991Z ----------------------------- Captured stdout call -----------------------------
2024-10-16T19:14:55.7939857Z [2024-10-16 19:14:05,725] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.7941010Z [2024-10-16 19:14:05,730] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.7941844Z [2024-10-16 19:14:07,371] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.7942593Z [2024-10-16 19:14:07,378] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.7943327Z ----------------------------- Captured stderr call -----------------------------
2024-10-16T19:14:55.7944325Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.7945108Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.7946082Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.7946920Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.7947784Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>9132 us: [pid:1662  tid:0x7fdae0b7a700] Callback: Queue 0x7fdaf9900000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.7948934Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>9277 us: [pid:1663  tid:0x7fdae6b7a700] Callback: Queue 0x7fdafe200000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.7950004Z _____________________ TestDistInit.test_already_init[None] _____________________
2024-10-16T19:14:55.7950497Z Worker 0 killed by signal 6
2024-10-16T19:14:55.7951145Z ---------------------------- Captured stderr setup -----------------------------
2024-10-16T19:14:55.7951910Z /opt/conda/envs/ptca/lib/python3.9/multiprocessing/resource_tracker.py:216: UserWarning: resource_tracker: There appear to be 3 leaked semaphore objects to clean up at shutdown
2024-10-16T19:14:55.7952753Z   warnings.warn('resource_tracker: There appear to be %d '
2024-10-16T19:14:55.7953445Z ----------------------------- Captured stdout call -----------------------------
2024-10-16T19:14:55.7954299Z [2024-10-16 19:14:10,534] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.7955255Z [2024-10-16 19:14:10,544] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.7956086Z [2024-10-16 19:14:13,163] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.7956835Z [2024-10-16 19:14:13,168] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.7957566Z ----------------------------- Captured stderr call -----------------------------
2024-10-16T19:14:55.7958538Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.7959325Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.7960302Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.7961083Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.7961958Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>6077 us: [pid:1843  tid:0x7fb7da5c8700] Callback: Queue 0x7fb7f5800000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.7963114Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>6079 us: [pid:1844  tid:0x7fb7da5c8700] Callback: Queue 0x7fb7f1c00000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.7964047Z _______________________ TestDistInit.test_no_init[True] ________________________
2024-10-16T19:14:55.7964546Z Worker 0 killed by signal 6
2024-10-16T19:14:55.7965182Z ---------------------------- Captured stderr setup -----------------------------
2024-10-16T19:14:55.7965950Z /opt/conda/envs/ptca/lib/python3.9/multiprocessing/resource_tracker.py:216: UserWarning: resource_tracker: There appear to be 3 leaked semaphore objects to clean up at shutdown
2024-10-16T19:14:55.7966809Z   warnings.warn('resource_tracker: There appear to be %d '
2024-10-16T19:14:55.7967500Z ----------------------------- Captured stdout call -----------------------------
2024-10-16T19:14:55.7968353Z [2024-10-16 19:14:16,285] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.7969310Z [2024-10-16 19:14:16,351] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.7970138Z [2024-10-16 19:14:17,893] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.7971001Z [2024-10-16 19:14:17,893] [INFO] [comm.py:683:init_distributed] Initializing TorchBackend in DeepSpeed with backend nccl
2024-10-16T19:14:55.7971826Z [2024-10-16 19:14:18,060] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.7972556Z ----------------------------- Captured stderr call -----------------------------
2024-10-16T19:14:55.7973690Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.7974526Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.7975528Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.7976304Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.7977180Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>9282 us: [pid:2025  tid:0x7faf78da7700] Callback: Queue 0x7faf90400000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.7978317Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>9281 us: [pid:2024  tid:0x7faf76da7700] Callback: Queue 0x7faf8dc00000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.7979210Z _______________________ TestDistInit.test_no_init[None] ________________________
2024-10-16T19:14:55.7979706Z Worker 0 killed by signal 6
2024-10-16T19:14:55.7980347Z ----------------------------- Captured stdout call -----------------------------
2024-10-16T19:14:55.7981315Z [2024-10-16 19:14:25,565] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.7982269Z [2024-10-16 19:14:25,650] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.7983092Z [2024-10-16 19:14:27,159] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.7983841Z [2024-10-16 19:14:27,241] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.7984698Z [2024-10-16 19:14:27,242] [INFO] [comm.py:683:init_distributed] Initializing TorchBackend in DeepSpeed with backend nccl
2024-10-16T19:14:55.7985539Z ----------------------------- Captured stderr call -----------------------------
2024-10-16T19:14:55.7986514Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.7987304Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.7988281Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.7989055Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.7989937Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>7244 us: [pid:2375  tid:0x7f12c7e30700] Callback: Queue 0x7f12e1400000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.7991093Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>7241 us: [pid:2374  tid:0x7f12b1e30700] Callback: Queue 0x7f12e4c00000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.7991986Z ________________ TestDistInitWithModel.test_already_init[True] _________________
2024-10-16T19:14:55.7992481Z Worker 0 killed by signal 6
2024-10-16T19:14:55.7993129Z ----------------------------- Captured stdout call -----------------------------
2024-10-16T19:14:55.7993978Z [2024-10-16 19:14:36,912] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.7994931Z [2024-10-16 19:14:36,962] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.7995915Z [2024-10-16 19:14:38,716] [INFO] [logging.py:96:log_dist] [Rank -1] DeepSpeed info: version=0.15.1, git-hash=unknown, git-branch=unknown
2024-10-16T19:14:55.7996890Z [2024-10-16 19:14:38,716] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.7997794Z [2024-10-16 19:14:38,716] [INFO] [config.py:733:__init__] Config mesh_device None world_size = 2
2024-10-16T19:14:55.7998740Z [2024-10-16 19:14:38,736] [INFO] [logging.py:96:log_dist] [Rank -1] DeepSpeed info: version=0.15.1, git-hash=unknown, git-branch=unknown
2024-10-16T19:14:55.7999589Z [2024-10-16 19:14:38,736] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.8000392Z [2024-10-16 19:14:38,737] [INFO] [config.py:733:__init__] Config mesh_device None world_size = 2
2024-10-16T19:14:55.8001168Z ----------------------------- Captured stderr call -----------------------------
2024-10-16T19:14:55.8002133Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.8002926Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.8003913Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.8004701Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.8005575Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>2385 us: [pid:2648  tid:0x7f5e62452700] Callback: Queue 0x7f5e86600000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.8006727Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>2940 us: [pid:2649  tid:0x7f5e5c452700] Callback: Queue 0x7f5e87600000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.8007610Z ________________ TestDistInitWithModel.test_already_init[False] ________________
2024-10-16T19:14:55.8008110Z Worker 0 killed by signal 6
2024-10-16T19:14:55.8008754Z ---------------------------- Captured stderr setup -----------------------------
2024-10-16T19:14:55.8009527Z /opt/conda/envs/ptca/lib/python3.9/multiprocessing/resource_tracker.py:216: UserWarning: resource_tracker: There appear to be 3 leaked semaphore objects to clean up at shutdown
2024-10-16T19:14:55.8010374Z   warnings.warn('resource_tracker: There appear to be %d '
2024-10-16T19:14:55.8011063Z ----------------------------- Captured stdout call -----------------------------
2024-10-16T19:14:55.8011914Z [2024-10-16 19:14:41,875] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.8012870Z [2024-10-16 19:14:41,890] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.8013906Z [2024-10-16 19:14:44,501] [INFO] [logging.py:96:log_dist] [Rank -1] DeepSpeed info: version=0.15.1, git-hash=unknown, git-branch=unknown
2024-10-16T19:14:55.8014776Z [2024-10-16 19:14:44,502] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.8015580Z [2024-10-16 19:14:44,502] [INFO] [config.py:733:__init__] Config mesh_device None world_size = 2
2024-10-16T19:14:55.8016523Z [2024-10-16 19:14:44,516] [INFO] [logging.py:96:log_dist] [Rank -1] DeepSpeed info: version=0.15.1, git-hash=unknown, git-branch=unknown
2024-10-16T19:14:55.8017376Z [2024-10-16 19:14:44,516] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.8018171Z [2024-10-16 19:14:44,516] [INFO] [config.py:733:__init__] Config mesh_device None world_size = 2
2024-10-16T19:14:55.8018957Z ----------------------------- Captured stderr call -----------------------------
2024-10-16T19:14:55.8019927Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.8020821Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.8021916Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.8022761Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.8023688Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>5673 us: [pid:2832  tid:0x7f925f6c8700] Callback: Queue 0x7f9278a00000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.8024841Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>6647 us: [pid:2831  tid:0x7f92636c8700] Callback: Queue 0x7f9278200000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.8025714Z ___________________ TestDistInitWithModel.test_no_init[True] ___________________
2024-10-16T19:14:55.8026221Z Worker 0 killed by signal 6
2024-10-16T19:14:55.8026872Z ----------------------------- Captured stdout call -----------------------------
2024-10-16T19:14:55.8027744Z [2024-10-16 19:14:47,656] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.8028686Z [2024-10-16 19:14:47,730] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
2024-10-16T19:14:55.8029681Z [2024-10-16 19:14:49,320] [INFO] [logging.py:96:log_dist] [Rank -1] DeepSpeed info: version=0.15.1, git-hash=unknown, git-branch=unknown
2024-10-16T19:14:55.8030541Z [2024-10-16 19:14:49,320] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.8031443Z [2024-10-16 19:14:49,433] [INFO] [logging.py:96:log_dist] [Rank -1] DeepSpeed info: version=0.15.1, git-hash=unknown, git-branch=unknown
2024-10-16T19:14:55.8032301Z [2024-10-16 19:14:49,433] [INFO] [comm.py:652:init_distributed] cdb=None
2024-10-16T19:14:55.8033182Z [2024-10-16 19:14:49,433] [INFO] [comm.py:683:init_distributed] Initializing TorchBackend in DeepSpeed with backend nccl
2024-10-16T19:14:55.8034111Z [2024-10-16 19:14:50,324] [INFO] [config.py:733:__init__] Config mesh_device None world_size = 2
2024-10-16T19:14:55.8034947Z [2024-10-16 19:14:50,327] [INFO] [config.py:733:__init__] Config mesh_device None world_size = 2
2024-10-16T19:14:55.8035728Z ----------------------------- Captured stderr call -----------------------------
2024-10-16T19:14:55.8036705Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.8037494Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.8038472Z /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.8039263Z   warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.8040141Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>1920 us: [pid:3014  tid:0x7f3046649700] Callback: Queue 0x7f307d200000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.8041292Z :0:rocdevice.cpp            :2984:<PHONE_NUMBER>3048 us: [pid:3015  tid:0x7f3050649700] Callback: Queue 0x7f3081800000 aborting with error : HSA_STATUS_ERROR_EXCEPTION: An HSAIL operation resulted in a hardware exception. code: 0x1016
2024-10-16T19:14:55.8042163Z =============================== warnings summary ===============================
2024-10-16T19:14:55.8043025Z ../../../opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113
2024-10-16T19:14:55.8044050Z   /opt/conda/envs/ptca/lib/python3.9/site-packages/onnxruntime/capi/onnxruntime_validation.py:113: UserWarning: WARNING: failed to get cudart_version from onnxruntime build info.
2024-10-16T19:14:55.8044959Z     warnings.warn("WARNING: failed to get cudart_version from onnxruntime build info.")
2024-10-16T19:14:55.8045276Z
2024-10-16T19:14:55.8045886Z ../../../opt/conda/envs/ptca/lib/python3.9/site-packages/pydantic/fields.py:826
2024-10-16T19:14:55.8047304Z   /opt/conda/envs/ptca/lib/python3.9/site-packages/pydantic/fields.py:826: PydanticDeprecatedSince20: Using extra keyword arguments on `Field` is deprecated and will be removed. Use `json_schema_extra` instead. (Extra keys: 'new_param'). Deprecated in Pydantic V2.0 to be removed in V3.0. See Pydantic V2 Migration Guide at https://errors.pydantic.dev/2.9/migration/
2024-10-16T19:14:55.8048270Z     warn(
2024-10-16T19:14:55.8048405Z
2024-10-16T19:14:55.8048823Z ../../integration_test/test_deepspeed/unit/test_dist.py:62
2024-10-16T19:14:55.8049952Z   /test/integration_test/test_deepspeed/unit/test_dist.py:62: PytestUnknownMarkWarning: Unknown pytest.mark.world_size - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/stable/how-to/mark.html
2024-10-16T19:14:55.8050795Z     @pytest.mark.world_size(1)
2024-10-16T19:14:55.8050969Z
2024-10-16T19:14:55.8051535Z -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
2024-10-16T19:14:55.8052105Z =========================== short test summary info ============================
2024-10-16T19:14:55.8052708Z FAILED ../../integration_test/test_deepspeed/unit/test_dist.py::TestInit::test
2024-10-16T19:14:55.8053599Z FAILED ../../integration_test/test_deepspeed/unit/test_dist.py::TestDistArgs::test[hello-icosahedron-1138-purple]
2024-10-16T19:14:55.8054331Z FAILED ../../integration_test/test_deepspeed/unit/test_dist.py::TestGroupedDistTest::test_one[1138]
2024-10-16T19:14:55.8055027Z FAILED ../../integration_test/test_deepspeed/unit/test_dist.py::TestGroupedDistTest::test_two[1138]
2024-10-16T19:14:55.8055758Z FAILED ../../integration_test/test_deepspeed/unit/test_dist.py::TestWorldSizeOverrideDistTest::test_world_size_2
2024-10-16T19:14:55.8056465Z FAILED ../../integration_test/test_deepspeed/unit/test_dist.py::TestDistAllReduce::test
2024-10-16T19:14:55.8057138Z FAILED ../../integration_test/test_deepspeed/unit/test_dist.py::TestDistInit::test_already_init[True]
2024-10-16T19:14:55.8057841Z FAILED ../../integration_test/test_deepspeed/unit/test_dist.py::TestDistInit::test_already_init[False]
2024-10-16T19:14:55.8058540Z FAILED ../../integration_test/test_deepspeed/unit/test_dist.py::TestDistInit::test_already_init[None]
2024-10-16T19:14:55.8059232Z FAILED ../../integration_test/test_deepspeed/unit/test_dist.py::TestDistInit::test_no_init[True]
2024-10-16T19:14:55.8059903Z FAILED ../../integration_test/test_deepspeed/unit/test_dist.py::TestDistInit::test_no_init[None]
2024-10-16T19:14:55.8060875Z FAILED ../../integration_test/test_deepspeed/unit/test_dist.py::TestDistInitWithModel::test_already_init[True]
2024-10-16T19:14:55.8061613Z FAILED ../../integration_test/test_deepspeed/unit/test_dist.py::TestDistInitWithModel::test_already_init[False]
2024-10-16T19:14:55.8062350Z FAILED ../../integration_test/test_deepspeed/unit/test_dist.py::TestDistInitWithModel::test_no_init[True]
2024-10-16T19:14:55.8063026Z ============= 14 failed, 4 passed, 3 warnings in 102.03s (0:01:42) =============
2024-10-16T19:14:56.7134939Z ERROR (104.341s)
2024-10-16T19:14:56.7135124Z
2024-10-16T19:14:56.7135560Z ======================================================================
2024-10-16T19:14:56.7136135Z ERROR [104.341s]: test_deepspeed_integration (__main__.TestPTCA)
2024-10-16T19:14:56.7136627Z Check DeepSpeed integration with PTCA.
2024-10-16T19:14:56.7137460Z ----------------------------------------------------------------------
2024-10-16T19:14:56.7137953Z Traceback (most recent call last):
2024-10-16T19:14:56.7138451Z   File "/test/test_PTCA.py", line 368, in test_deepspeed_integration
2024-10-16T19:14:56.7139367Z     subprocess.check_call("pytest -v --forked {0}/integration_test/test_deepspeed/unit".format(ROOT_PATH).split(), cwd=downloads_test_folder)
2024-10-16T19:14:56.7140386Z   File "/opt/conda/envs/ptca/lib/python3.9/subprocess.py", line 373, in check_call
2024-10-16T19:14:56.7141098Z     raise CalledProcessError(retcode, cmd)
2024-10-16T19:14:56.7141944Z subprocess.CalledProcessError: Command '['pytest', '-v', '--forked', '/test/integration_test/test_deepspeed/unit']' returned non-zero exit status 1.
2024-10-16T19:14:56.7142335Z
2024-10-16T19:14:56.7142884Z ----------------------------------------------------------------------

Also saw the below error, not sure if it's relevant
2024-10-16T19:15:05.5948970Z Traceback (most recent call last):
2024-10-16T19:15:05.5949652Z   File "/opt/conda/envs/ptca/lib/python3.9/runpy.py", line 197, in _run_module_as_main
2024-10-16T19:15:05.5950190Z     return _run_code(code, main_globals, None,
2024-10-16T19:15:05.5950688Z   File "/opt/conda/envs/ptca/lib/python3.9/runpy.py", line 87, in _run_code
2024-10-16T19:15:05.5951158Z     exec(code, run_globals)
2024-10-16T19:15:05.5951902Z   File "/opt/conda/envs/ptca/lib/python3.9/site-packages/torch/distributed/launch.py", line 198, in <module>
2024-10-16T19:15:05.5952410Z     main()
2024-10-16T19:15:05.5953056Z   File "/opt/conda/envs/ptca/lib/python3.9/site-packages/torch/distributed/launch.py", line 194, in main
2024-10-16T19:15:05.5953565Z     launch(args)
2024-10-16T19:15:05.5954219Z   File "/opt/conda/envs/ptca/lib/python3.9/site-packages/torch/distributed/launch.py", line 179, in launch
2024-10-16T19:15:05.5954718Z     run(args)
2024-10-16T19:15:05.5955369Z   File "/opt/conda/envs/ptca/lib/python3.9/site-packages/torch/distributed/run.py", line 803, in run
2024-10-16T19:15:05.5955886Z     elastic_launch(
2024-10-16T19:15:05.5956582Z   File "/opt/conda/envs/ptca/lib/python3.9/site-packages/torch/distributed/launcher/api.py", line 135, in __call__
2024-10-16T19:15:05.5957229Z     return launch_agent(self._config, self._entrypoint, list(args))
2024-10-16T19:15:05.5958025Z   File "/opt/conda/envs/ptca/lib/python3.9/site-packages/torch/distributed/launcher/api.py", line 268, in launch_agent
2024-10-16T19:15:05.5958597Z     raise ChildFailedError(
2024-10-16T19:15:05.5959075Z torch.distributed.elastic.multiprocessing.errors.ChildFailedError:
2024-10-16T19:15:05.5959615Z ============================================================
2024-10-16T19:15:05.5960171Z /test/integration_test/test_nvidia_apex/distributed_data_parallel.py FAILED
2024-10-16T19:15:05.5960852Z ------------------------------------------------------------
2024-10-16T19:15:05.5961272Z Failures:
2024-10-16T19:15:05.5961601Z [1]:
2024-10-16T19:15:05.5962070Z   time      : 2024-10-16_19:15:05
2024-10-16T19:15:05.5962477Z   host      : a184145b9c07
2024-10-16T19:15:05.5962845Z   rank      : 1 (local_rank: 1)
2024-10-16T19:15:05.5963334Z   exitcode  : -6 (pid: 3495)
2024-10-16T19:15:05.5963706Z   error_file: <N/A>
2024-10-16T19:15:05.5964115Z   traceback : Signal 6 (SIGABRT) received by PID 3495
2024-10-16T19:15:05.5964734Z ------------------------------------------------------------
2024-10-16T19:15:05.5965198Z Root Cause (first observed failure):
2024-10-16T19:15:05.5965553Z [0]:
2024-10-16T19:15:05.5966024Z   time      : 2024-10-16_19:15:05
2024-10-16T19:15:05.5966411Z   host      : a184145b9c07
2024-10-16T19:15:05.5966791Z   rank      : 0 (local_rank: 0)
2024-10-16T19:15:05.5967281Z   exitcode  : -6 (pid: 3494)
2024-10-16T19:15:05.5967652Z   error_file: <N/A>
2024-10-16T19:15:05.5968078Z   traceback : Signal 6 (SIGABRT) received by PID 3494
2024-10-16T19:15:05.5968577Z ============================================================

Where is the DeepSpeed error? I only see onnx and torch in the stack traces.

For ROCm issues, FYI @rraminen and @jithunnair-amd


Webtorrent without tracker.

Hi Feross.
I'm using webtorrent, but I don't use bitorrent-tracker, to add a peer to download I use torrent.addPeer(addr). But, I really run on LAN network with "addr" is IP and port of computers.
When two computers in the different LAN network, I don't know what is "addr".
Because a computer has public IP address and private IP address.
Please help me.
Thanks!

You can usually just use the built-in list of torrents in a .torrent file or magnet link. If your use case is your own private torrents, then you should consider running your own bitorrent-tracker instance to make peer discovery automatic and easy.
That said, if you want to use torrent.addPeer(addr), you need to know an IP address that will let you reach another peer. Usually it's safest to just use the public IP address. But you can try passing in the private IP address as well, especially if you know the peers are on the same network.
Don't worry if the host at the IP address might not be reachable – the torrent client is smart enough to try and give up after a number of consecutive connect failures. Just add both the public and private IPs.
You can get the port that the torrent client is listening on by calling client.address().port.

Thanks, I will try.

Great - feel free to ask additional questions if you run into trouble.


Blocking of Facebook and Threads.net?

I use weserv for serving my OpenGraph images.  When I try to share pages on Facebook and Threads.net, the images aren't displayed.  They are displayed on other services.
Using the Facebook OGP debugger I receive an error that the image is corrupted.

could not be processed as an image. It may be corrupted or may have an invalid format.

I've tried both JPG and WebP formats - the error remains.
Is weserv blocking Meta from retrieving the images?
FB report https://developers.facebook.com/community/threads/564775512695053/
Possibly related to #310

Looks like you're returning HTTP 403 https://developers.facebook.com/tools/debug/?q=https%3A%2F%2Fimages.weserv.nl%2F%3Furl%3Dopenbenches.org%2Fimage%2Fe2725d861dc6902da7069f9e8e1f02ab13994fa6%2F%26w%3D600%26q%3D60%26output%3Dwebp%26il
I assume that's intentional?


Change forEach to for...of

This is a WIP, because it breaks a lot of things (specifically the forEach's with multiple params), so I will need to test each one of them and fix accordingly.

This pull request introduces 1 alert when merging c766ce0e5a203bc45a5b23b8068dc09116779d02 into 295f7c6c9f3620829801813daae401a97a48e1f3 - view on LGTM.com
new alerts:

1 for Syntax error

Comment posted by LGTM.com

Okay, at this point, I feel like I shouldn't keep doing this review.
The important thing you need to understand here is the difference between a Map and an Array, and how to iterate them.
Arrays and Sets work like this:
array.forEach(value => {...});
=> for (const value of array) {...}
Maps work like this:
map.forEach(value => {...});
=> for (const value of map.values()) {...}
map.forEach((value, key) => {...});
=> for (const [key, value] of map) {...}

Thanks!


[Storage] Fix #16489: Upgrade azcopy to 10.8.0

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Storage

Storage


Mocking input event for controlled inputs in react

This extension works in a way that leads to unexpected behaviour when used in a react controlled input. Currently this extension assigns the value to the dom element without dispatching/triggering an event:
app/scripts/ate.js(ln.343)
textInput.value = replaceText(
  textInput.value,
  shortcut,
  autotext,
  cursorPosition
);

Here's a fiddle illustrating the problem: JS Fiddle example
and a rudimentary fix I made to get this working:
https://github.com/briantingtc/ChromeAutoTextExpander/commit/76d8ad5b8b0bc17f4f195ead5bd2f42a5b15f1a4
Let me know if we could get something like the above commit merged in or whether or if adding custom behaviour for a specific domain would be possible.

Hey Brian! Wow thanks, I've been meaning to get to this but since getting
married haven't had a chance to at all. I'll try to take a look tomorrow
and would love to merge it in if we can.
On Fri, May 3, 2019 at 4:29 PM Brian Ting<EMAIL_ADDRESS>wrote:

This extension works in a way that leads to unexpected behaviour when used
in a react controlled input. Currently this extension assigns the value to
the dom element without dispatching/triggering an event:
app/scripts/ate.js(ln.343)
textInput.value = replaceText(
textInput.value,
shortcut,
autotext,
cursorPosition
);
Here's a fiddle illustrating the problem: JS Fiddle example
https://jsfiddle.net/r3b7tq6g/4/
and a rudimentary fix I made to get this working:
briantingtc@76d8ad5
https://github.com/briantingtc/ChromeAutoTextExpander/commit/76d8ad5b8b0bc17f4f195ead5bd2f42a5b15f1a4
Let me know if we could get something like the above commit merged in or
whether or if adding custom behaviour for a specific domain would be
possible.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/carlinyuen/ChromeAutoTextExpander/issues/51, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AADHHXKTG2OPSOF3JJHZNITPTSOB3ANCNFSM4HKWYYMQ
.

Thanks Carlin, let me know if there's anything I can do to help -- and congrats on getting hitched!

Hey @carlinyuen we are running into this same issue with some of our users. Is there any way that we could help getting a fix merged?

Hey Will, thanks for the poke. Yeah absolutely, I'm going to commit time to
looking at it this week, hopefully have the fix in by EOW at the latest.
Sorry for the wait!
.C
On Thu, Jun 20, 2019, 13:54 Will Douglas<EMAIL_ADDRESS>wrote:

Hey @carlinyuen https://github.com/carlinyuen we are running into this
same issue with some of our users. Is there any way that we could help
getting a fix merged?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/carlinyuen/ChromeAutoTextExpander/issues/51?email_source=notifications&email_token=AADHHXKFMBV5NPE44HNLLVTP3PVAVA5CNFSM4HKWYYM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYGST6A#issuecomment-504179192,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADHHXK2SEUIQMJU56DRJ63P3PVAVANCNFSM4HKWYYMQ
.

Hey folks, confirming that I'm looking into this now. Thanks for being patient! Life got busy, not a great excuse. :P

Hey @carlinyuen, wondering if you guys can push the most recent (2.0) version to the chrome web store.. I kinda rely on that tool for my daily activities and now with improvements in iframe support it would really help me out. thanks!

Hey @ghbeckman workin' on it. :)
With the iframe change, I have to retest some of the code to make sure the extension still works in the same input fields. Hopefully can have this out for some of you folks by July 4th.
Actually, it'd really help to have a bunch of you test the changes for me on some of the sites you use. Please let me know if any of you would be interested in joining some sort of "dogfood" group. I'd create a Google group and basically send an early version of the extension to you, would just need you to test it on whatever product you already use it on, to make sure it's not busted.

I'd be down, lmk how I can help

@carlinyuen Absolutely! Glad to help in anyway possible. Thanks for your effort. Appreciate it

Hey folks, thanks for being great sports. Sincere apologies, life got in the way again. :( I'm going to try and get back into this this weekend.

Sorry to poke you again @carlinyuen as I know you're super busy but we'll be needing this plugin to work with one of our features. If I create a pr with specific behavior for our domain would you consider merging that in? Otherwise would it be okay if we re hosted the plugin with that specific change?

Any update on this? it's important for me thais fix as well

There is any plan to update to Manifest 3.0 ? This extension is great but now google says it may soon no longer be supported :(


support for useContext

I really appreciate this utility. It would be great if it could support all hooks

I am very grateful for your use of the library and for the suggested improvement.
But unfortunately, I admit the implementation of the useContext hook is impossible within the useBetween section.
useBetween shared state with logic initializes its state and exists outside the React component tree. React components can use any such state that exists as long as it is used. But this state cannot refer to the useContext hook, since it is executed outside the React component tree.
In the case of useBetween, it is better to use it in conjunction with useContext, but not one inside the other.
You can store some data in the React context and transfer it deep into the React component trees, and some can be shared for the entire application, and then it is convenient to place them in the useBetween.
You can synchronize data from context to a shared state using the useEffect (if strictly necessary).
const value = useContext(MyContext);
const { setValue } = useMySharedState();

useEffect(() => {
  setValue(value);
}, [value]);


Adding Ezhil-Lang README

Please reference the Issue in the pr description so that I can merge.

@kishansundar Is this PR still active?

Any updates here?


Removed empty nested template "pid-5990..." and default value for "certifcatePassword" param from mainTemplate.json

Please continue with release to marketplace. I'll then submit the templates

Please continue with release to marketplace. I'll then submit the templates


TLS failed to start the connection process.

Hi all, I am new to this and are haveing som issues sending my sensor data to the IoT Azure Hub. I have cheked my setup several times, this is last resort.
In the serial logger I get this statuses:

Attempting
to connect to SSID: Utsikten 17
Connected to wifi
Fetched NTP epoch time is:<PHONE_NUMBER>
Checking for the presence of the BME280 temp/humid/press module.
Found and initialized BME280 module.
Info: IoT Hub SDK for C, version 1.0.17
Info: deviceId=FeatherWifi
Info: IoTHubClient accepted the message for delivery
Error: Time:Wed Dec  7 22:59:27 2016 File:C:\Users\Trond Erik Mometo\Documents\Arduino\libraries\AzureIoTUtility\src\adapters\tlsio_arduino.c Func:tlsio_arduino_open Line:264 TLS failed to start the connection process.
Error: Time:Wed Dec  7 22:59:27 2016 File:C:\Users\Trond Erik Mometo\Documents\Arduino\libraries\AzureIoTProtocol_MQTT\src\azure_umqtt_c\mqtt_client.c Func:mqtt_client_connect Line:884 Error: io_open failed
Error: Time:Wed Dec  7 22:59:27 2016 File:C:\Users\Trond Erik Mometo\Documents\Arduino\libraries\AzureIoTHub\src\sdk\iothubtransport_mqtt_common.c Func:SendMqttConnectMsg Line:1554 failure connecting to address MometoIoTv3.azure-devices.net:0.
Info: Evaluated delay 0 at 1 attempt to retry

Any help leading me in the right direction would be appreciated :)
Looking at the address the port definition ":0" looks somewhat strange to a newbee like me?
Best regards
Trond Erik

I don't believe MQTT is a supported option for the Arduino and FeatherM0.  Http only, there is commitment to MQTT going forward based on an issue posted in the azure-iot-arduino repo (see link below).
https://github.com/Azure/azure-iot-arduino/issues/26

Thanks for reply :)
Then I guess this should be updated in the code or the guide for this starter-pack. Because I followed the guide several times and ended up with the error above.

Hi tebones,
Microsoft has just added MQTT for Arduino. You are probably running in a issue with your Connection Key. Please double check if all configurations there are correct, mainly if you are not providing the MometoloTv3 twice.

Hi mamokarz, changed my code to use http and it worked, but stops again after about 3 hours.
Motivated with my luck I went ahead with your second example making really sure all my keys are ok. Node is up, all azure devices is up, even my feather is online but I end up with the same error as the previous example: "TLS failed to start the connection process". There must be something woring somewhere :)
Pls advice :) I need to get this working for a showcase on IoT for my co-workers ;)

I too was unable to get things working with MQTT due to this connection error.  Gave the HTTP example a try, and it worked.
I can't seem to get Wireshark to read my traffic today so I can't be sure, but any chance that this device doesn't support TLS 1.2 and the Azure IoT HTTP endpoint is allowing an older TLS version, but the MQTT endpoint isn't?  MQTT works fine from C#, just not from this Arduino Feather M0.

Can you please activate the MQTT logs, localize IoTHubClient_LL_CreateFromConnectionString on remote_monitoring.c, and add the traceOn option after that, as follow.
#if defined(IOT_CONFIG_MQTT)
iotHubClientHandle = IoTHubClient_LL_CreateFromConnectionString(IOT_CONFIG_CONNECTION_STRING, MQTT_Protocol);
#elif defined(IOT_CONFIG_HTTP)
iotHubClientHandle = IoTHubClient_LL_CreateFromConnectionString(IOT_CONFIG_CONNECTION_STRING, HTTP_Protocol);
#else
iotHubClientHandle = NULL;
#endif

bool traceOn = true;
IoTHubClient_LL_SetOption(iotHubClientHandle, "logtrace", &traceOn);

Added that, but didn't result in any more logging.  I'm guessing that's because the connection is what's failing - it's not a MQTT protocol error - it's the raw TLS connection setup that's failing.  Ie. where adapters/sslClient_arduino.c calls the underlying sslClient.connect, it's getting back a 'false' (0), leading to the failure.
To help debug, I've tried using the WiFiSSLClient example to connect to my *.azure-devices.net hostname.  When I connect on 443, I get a successful connection.  When I connect to 8883 (the port my C# MQTT example connects to), I don't get a successful connection (Adafruit_WINC1500SSLClient.connect returns false).

Routing my traffic through my desktop so I can sniff it in Wireshark, I see a difference in how the connection setup process goes on 443 vs. 8883.
Here's what the port 443 connection looks like:
C->S: Client Hello
S->C: Server Hello, Certificate, Certificate Request, Server Hello Done
C->S: Client Key Exchange, Change Cipher Spec, Hello Request, Hello Request
S->C: Change Cipher Spec, Hello Request, Hello Request

(ie. successful connection - data flows)
And here's the port 8883 connection (same for first 3 parts):
C->S: Client Hello
S->C: Server Hello, Certificate, Certificate Request, Server Hello Done
C->S: Client Key Exchange, Change Cipher Spec, Hello Request, Hello Request
S->C: [TCP ACK]
<no data for 15 seconds>
C->S: [TCP FIN, ACK]
(ie. connect timeout, client disconnects)
Shouldn't the TLS handshake process work the same on both ports?
And to add more fun, here's what the port 8883 conversation looks like from my .Net test app:
C->S: Client Hello
S->C: Server Hello, Certificate, Certificate Request, Server Hello Done
C->S: Client Key Exchange, Change Cipher Spec, Encrypted Handshake Message
S->C: Change Cipher Spec, Encrypted Handshake Message

(ie. successful connection - data flows)

I’m wondering if we are running in some contamination problem. Sometimes, the Arduino IDE do not recognize changes in the library and just reuse parts of the previous compilation. To avoid it, can you please totally delete the previous result? It is located in a temporary directory with the name arduino_build_#####
C:\Users\ <<userName>> \AppData\Local\Temp\arduino_build_####

You will find simplesample_mqtt.ino.bin inside of it. Delete all files and directories inside of this arduino_build_#### directory. Recompile the code and check if this directory was populated again.

Still not getting any debug output :(  Doesn't really surprise me though, as all that output comes after the connection happens.  The underlying SSL/TLS connection isn't getting established - that's the issue.

And @mamokarz - re: the address you suggested on the other thread - I can't get a TLS connection to MokaFeatherM0Suite.azure-devices.net:8883 either, but :443 works just fine (same thing I'm experiencing on the IoT hub I'm testing with).  It's got to be something with the details of how the TLS security handshake is working between the Feather M0 w/ WINC1500 and the MQTT-SSL endpoint of the IoT Hub.

I'm investigating.

Hi, at my first glance I know I have exactly the same problem with @jorupp , and it's definitely a problem of the TLS connection establishment.
For M0 trying to establish TLS connection via port 8883, it's all the way good UNTIL here:
// File: Adafruit_WINC1500Client.cpp
int Adafruit_WINC1500Client::connect(IPAddress ip, uint16_t port, uint8_t opt, const uint8_t *hostname)
{
        .....
	// Connect to remote host:
	if (connectSocket(_socket, (struct sockaddr *)&addr, sizeof(struct sockaddr_in)) < 0) {
		close(_socket);
		_socket = -1;
		return 0;
	}
----->// Wait for connection or timeout:
	unsigned long start = millis();
	while (!IS_CONNECTED && millis() - start < 20000) {
		m2m_wifi_handle_events(NULL);
	}
	if (!IS_CONNECTED) {
		close(_socket);
		_socket = -1;
		return 0;
	}

	return 1;
}

And it finally leads to a SOCK_ERR_CONN_ABORTED.
And following is part of tcpdump log for M0 to connect 8883:
......
C->S: TLSv1.2	Client Key Exchange, Change Cipher Spec, Hello Request, Hello Request
S->C: TCP 8883→52174 [ACK] Seq=3185 Ack=393 Win=64752 Len=0
C->S: TCP 52174→8883 [FIN, ACK] Seq=393 Ack=3185 Win=4338 Len=0
......

My tests

[FAIL] M0 using MQTT_Protocol with port 8883
[ok] M0 using HTTP_Protocol with port 443
[ok] Mock Device (azure-iot-sdk-c in Visual Studio) using MQTT_Protocol with port 8883
[ok] Mock Device (azure-iot-sdk-node) using MQTT_Protocol with port 8883

Following are my Arduino related specs, FYI.
Board

Adafruit feather M0

AzureIoT Libraries

AzureIoTHub v1.0.21
AzureIoTProtocol_HTTP v1.0.21
AzureIoTProtocol_MQTT v1.0.21
AzureIoTUtility v1.0.21

WiFi Library
Either Adafruit_WINC1500 or WiFi101 works well.
@mamokarz So is there any positive news? If needed I can provide my source code and connection string.
Thanks.

I also have the same problem: HTTP is working, but MQTT isn't.
Same errors messages as posted above.
Library versions:

AzureIoTHub v1.0.21
AzureIoTProtocol_HTTP v1.0.21
AzureIoTProtocol_MQTT v1.0.21
AzureIoTUtility v1.0.21
Adafruit_WINC1500 v0.8.1
WiFi101 v0.12.1

@mamokarz Just wanted to check in on this issue. I am also experiencing the same problems with the same libraries as others in this thread. Any outlook on a possible solution? Thanks

Same here. And now with the Direct Methods feature only working over MQTT, protocol isn't much of a choice anymore.
I've always used Adafruit_WINC1500SSLClient sslClient in ATWINC1500 projects to connect to various endpoints over TLS 1.2, 443/TCP or arbitrary ports, this always seems to work. I'm assuming there's a bit more complexity involved in this case. If we can help here with testing stuff out, i'd be glad to do it.
IoT Hub product group, is this MQTT sample working for you on ATWINC1500?

@snobu It seems to be firmware issue, look at the related issue here

Solved by this new firmware

I've also verified this.  I couldn't use MQTT with the  19.4.4 firmware and it worked with the 19.5.2 firmware.

After one year I faced the same problem; Firmware update and uploading personal Azure IoT hub address' certificate (.azure-devices.net) into the WiFi module exactly solved it. Thank you very much.

Hi @berkaysit could you elaborate a bit more and provide all the library versions and the chip used by you,
I have access to The NodeMCU and Adafruit Feather HUZZAH chipset both based on the esp8266.
The error I am receiving is

connected with Moriarty, channel 11
dhcp client start...
ip:<IP_ADDRESS>,mask:<IP_ADDRESS>,gw:<IP_ADDRESS>
Connected to wifi Moriarty.
Fetched NTP epoch time is: 28812.
result = IOTHUB_CLIENT_OK
Sending message: {"deviceId":"Feather HUZZAH ESP8266 WiFi","messageId":1,"temperature":28,"humidity":36}.
IoTHubClient accepted the message for delivery.
TLS failed to start the connection process.
Error: io_open failed
failure connecting to address iotpra2.azure-devices.net.
TLS failed to start the connection process.
Error: io_open failed
failure connecting to address iotpra2.azure-devices.net.
TLS failed to start the connection process.
Error: io_open failed
failure connecting to address iotpra2.azure-devices.net.
TLS failed to start the connection process.
Error: io_open failed
failure connecting to address iotpra2.azure-devices.net.

Hi @mysaggar I was using Arduino MKR1000. I have made the firmware update by original Arduino IDE desktop software. Since over a year has passed, I can't check the library versions. Maybe you should use https or http prefix at your adress.

Is There any workaround for Adafruit Feather HUZZAH ESP8266 board? Or you received this error right?, so what firmware update did you install ?
Also I didn't get the last part of using the https/http prefice at my address.


search and replace with positive lookahead won't replace

I am having trouble getting the replace functionality to work when using positive lookaheads (I have not tried the same problem with negative lookaheads). An example:
some text to test11293898
Using regex, case insensitive find: (some text)([^0-9]+)(?=[0-9]+)
This will properly match "some text to test" but no matter what is placed in the replace bar even "asdfasdfasdf" hitting replace will not actually replace text.

Same issue as in atom/find-and-replace#299 .


Fix Socket dataintake in new GatewayService

There were couple of issues at WensnPiVS01.py. Also I've updated Socket adapter to make it retry connection when already used socket dies.

We need to make the pythin socket script a client and the gateway DataIntake a server

Splitting into two issues, closing first, opening second


Double the timeout

Purpose

No ticket is linked to this PR.

Changes

Doubles the timeout in the e2e test.

Review Instructions

No instructions.

Also something we might want to look into https://clojureverse.org/t/how-to-make-clojure-tests-stop-tests-running-in-case-one-of-them-failed/4635


generating a query example

this is more a feature request
After a users has standardised all of the terms and submitted it. Would it be possible to provide the user an example query containing the standardizations he/she just applied plus the location of the endpoint.

@AshkanA  you can actually label the issue as a feature request by using the 'enhancement' label.

@RinkeHoekstra thanks dat zocht ik


Report validation on submit: verification statement presence only in certain cases

Description:
After #405 is completed, we can amend the verification statement validation to include the following rules:

Verification Page Requirement

Registration Purpose: Users must complete the verification page if the registration purpose is any of the following:

OBPS Regulated Operation
Opt-in
New Entrants

Emissions Threshold: Users must complete the verification page if:

The registration purpose is Reporting Operation, and
Total attributable emissions (as shown on the Emissions Summary page) are greater than or equal to 25,000 TCo₂e.

Blocked: #405
Acceptance Criteria:
Given
When
Then
Development Checklist:

[ ] Refactor the logic from #405 into a backend service of some sort
[ ] Checklist item
[ ] Checklist item
[ ] Meets the DOD

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

[ ] User story is included
[ ] User role and type are identified
[ ] Acceptance criteria are included
[ ] Wireframes are included (if required)
[ ] Design / Solution is accepted by Product Owner
[ ] Dependencies are identified (technical, business, regulatory/policy)
[ ] Story has been estimated (under 13 pts)

Definition of Done (Note: If any of these points are not applicable, mark N/A)

[ ] Acceptance criteria are tested by the CI pipeline
[ ] UI meets accessibility requirements
[ ] Configuration changes are documented, documentation and designs are updated
[ ] Passes code peer-review
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Ticket is ready to be merged to main branch
[ ] Can be demoed in Sprint Review
[ ] Bugs or future work cards are identified and created
[ ] Reviewed and approved by Product Owner

Blocked By/Blocking
Notes:

@shon to write AC+Dev Checklist


[THREESCALE-1289] Fix error when loading a config with only some services using OIDC

This PR fixes properly the bug that we tried to fix in https://github.com/3scale/apicast/pull/893
The bug was still there because the integration tests that load the configuration on boot mock the loader v2 module. In the previous PR, we fixed the bug in the remote loader v2. Unfortunately, the same bug was present also in the OIDC loader module and we didn't have tests for that.
In this PR, I've added integration tests that properly test the whole loading flow including the OIDC loader module.
Ref: https://issues.jboss.org/browse/THREESCALE-1289

I fixed the codeclimate checks and also adapted a couple of tests of the management endpoint (https://github.com/3scale/apicast/pull/940/commits/bd60b9c1335023216775896395ba153c1d4274dd)


fix bug in is_scanned, wierd explode

There was strange use of explode, fix and test added.

All good! Thanks for the tests too!


SNAP Builds are using the wrong name for Binary

ive set build->productName and build->appID to the name i wanted and my OSX as also Win Portable builds are using the right binary names.
Snaps are not using the names of this properties but the package->name property
https://github.com/FreaKzero/ssgl-doom-launcher/releases/tag/v2.0.0-devpreview.13
referencing: https://github.com/FreaKzero/ssgl-doom-launcher/issues/73

Closing Issue here since i realized that this isnt a Problem of the Action but most likely the builder
Sorry for bothering.