Failure to connect to kernal

Description
What steps will reproduce the problem?

Edited $PATH using
export PATH=$PATH:/home/browlins/.local/bin
Traceback
Uncaught exception in ZMQStream callback
Traceback (most recent call last):
  File "/home/browlins/.local/lib/python3.9/site-packages/zmq/eventloop/zmqstream.py", line 560, in _run_callback
    f = callback(*args, **kwargs)
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/site-packages/jupyter_client/threaded.py", line 123, in _handle_recv
    msg_list = self.ioloop._asyncio_event_loop.run_until_complete(get_msg(future_msg))
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/site-packages/nest_asyncio.py", line 90, in run_until_complete
    return f.result()
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/asyncio/futures.py", line 201, in result
    raise self._exception
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/asyncio/tasks.py", line 256, in __step
    result = coro.send(None)
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/site-packages/jupyter_client/threaded.py", line 34, in get_msg
    return await msg
TypeError: object list can't be used in 'await' expression
Uncaught exception in zmqstream callback
Traceback (most recent call last):
  File "/home/browlins/.local/lib/python3.9/site-packages/zmq/eventloop/zmqstream.py", line 610, in _handle_events
    self._handle_recv()
  File "/home/browlins/.local/lib/python3.9/site-packages/zmq/eventloop/zmqstream.py", line 639, in _handle_recv
    self._run_callback(callback, msg)
  File "/home/browlins/.local/lib/python3.9/site-packages/zmq/eventloop/zmqstream.py", line 560, in _run_callback
    f = callback(*args, **kwargs)
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/site-packages/jupyter_client/threaded.py", line 123, in _handle_recv
    msg_list = self.ioloop._asyncio_event_loop.run_until_complete(get_msg(future_msg))
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/site-packages/nest_asyncio.py", line 90, in run_until_complete
    return f.result()
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/asyncio/futures.py", line 201, in result
    raise self._exception
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/asyncio/tasks.py", line 256, in __step
    result = coro.send(None)
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/site-packages/jupyter_client/threaded.py", line 34, in get_msg
    return await msg
TypeError: object list can't be used in 'await' expression
Exception in callback BaseAsyncIOLoop._handle_events(107, 1)
handle: <Handle BaseAsyncIOLoop._handle_events(107, 1)>
Traceback (most recent call last):
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/asyncio/events.py", line 80, in _run
    self._context.run(self._callback, *self._args)
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/site-packages/tornado/platform/asyncio.py", line 206, in _handle_events
    handler_func(fileobj, events)
  File "/home/browlins/.local/lib/python3.9/site-packages/zmq/eventloop/zmqstream.py", line 610, in _handle_events
    self._handle_recv()
  File "/home/browlins/.local/lib/python3.9/site-packages/zmq/eventloop/zmqstream.py", line 639, in _handle_recv
    self._run_callback(callback, msg)
  File "/home/browlins/.local/lib/python3.9/site-packages/zmq/eventloop/zmqstream.py", line 560, in _run_callback
    f = callback(*args, **kwargs)
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/site-packages/jupyter_client/threaded.py", line 123, in _handle_recv
    msg_list = self.ioloop._asyncio_event_loop.run_until_complete(get_msg(future_msg))
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/site-packages/nest_asyncio.py", line 90, in run_until_complete
    return f.result()
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/asyncio/futures.py", line 201, in result
    raise self._exception
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/asyncio/tasks.py", line 256, in __step
    result = coro.send(None)
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/site-packages/jupyter_client/threaded.py", line 34, in get_msg
    return await msg
TypeError: object list can't be used in 'await' expression
Uncaught exception in ZMQStream callback
Traceback (most recent call last):
  File "/home/browlins/.local/lib/python3.9/site-packages/zmq/eventloop/zmqstream.py", line 560, in _run_callback
    f = callback(*args, **kwargs)
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/site-packages/jupyter_client/threaded.py", line 123, in _handle_recv
    msg_list = self.ioloop._asyncio_event_loop.run_until_complete(get_msg(future_msg))
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/site-packages/nest_asyncio.py", line 90, in run_until_complete
    return f.result()
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/asyncio/futures.py", line 201, in result
    raise self._exception
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/asyncio/tasks.py", line 256, in __step
    result = coro.send(None)
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/site-packages/jupyter_client/threaded.py", line 34, in get_msg
    return await msg
TypeError: object list can't be used in 'await' expression
Uncaught exception in zmqstream callback
Traceback (most recent call last):
  File "/home/browlins/.local/lib/python3.9/site-packages/zmq/eventloop/zmqstream.py", line 610, in _handle_events
    self._handle_recv()
  File "/home/browlins/.local/lib/python3.9/site-packages/zmq/eventloop/zmqstream.py", line 639, in _handle_recv
    self._run_callback(callback, msg)
  File "/home/browlins/.local/lib/python3.9/site-packages/zmq/eventloop/zmqstream.py", line 560, in _run_callback
    f = callback(*args, **kwargs)
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/site-packages/jupyter_client/threaded.py", line 123, in _handle_recv
    msg_list = self.ioloop._asyncio_event_loop.run_until_complete(get_msg(future_msg))
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/site-packages/nest_asyncio.py", line 90, in run_until_complete
    return f.result()
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/asyncio/futures.py", line 201, in result
    raise self._exception
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/asyncio/tasks.py", line 256, in __step
    result = coro.send(None)
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/site-packages/jupyter_client/threaded.py", line 34, in get_msg
    return await msg
TypeError: object list can't be used in 'await' expression
Exception in callback BaseAsyncIOLoop._handle_events(106, 1)
handle: <Handle BaseAsyncIOLoop._handle_events(106, 1)>
Traceback (most recent call last):
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/asyncio/events.py", line 80, in _run
    self._context.run(self._callback, *self._args)
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/site-packages/tornado/platform/asyncio.py", line 206, in _handle_events
    handler_func(fileobj, events)
  File "/home/browlins/.local/lib/python3.9/site-packages/zmq/eventloop/zmqstream.py", line 610, in _handle_events
    self._handle_recv()
  File "/home/browlins/.local/lib/python3.9/site-packages/zmq/eventloop/zmqstream.py", line 639, in _handle_recv
    self._run_callback(callback, msg)
  File "/home/browlins/.local/lib/python3.9/site-packages/zmq/eventloop/zmqstream.py", line 560, in _run_callback
    f = callback(*args, **kwargs)
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/site-packages/jupyter_client/threaded.py", line 123, in _handle_recv
    msg_list = self.ioloop._asyncio_event_loop.run_until_complete(get_msg(future_msg))
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/site-packages/nest_asyncio.py", line 90, in run_until_complete
    return f.result()
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/asyncio/futures.py", line 201, in result
    raise self._exception
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/asyncio/tasks.py", line 256, in __step
    result = coro.send(None)
  File "/opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9/site-packages/jupyter_client/threaded.py", line 34, in get_msg
    return await msg
TypeError: object list can't be used in 'await' expression

Versions

Spyder version: 5.4.0  (conda)
Python version: 3.9.13 64-bit
Qt version: 5.15.6
PyQt5 version: 5.15.7
Operating System: Linux 3.10.0-1160.118.1.el7.x86_64

Dependencies
# Mandatory:
atomicwrites >=1.2.0          :  1.4.1 (OK)
chardet >=2.0.0               :  5.0.0 (OK)
cloudpickle >=0.5.0           :  2.2.0 (OK)
cookiecutter >=1.6.0          :  2.1.1 (OK)
diff_match_patch >=20181111   :  20200713 (OK)
intervaltree >=3.0.2          :  3.0.2 (OK)
IPython >=7.31.1;<8.0.0       :  7.33.0 (OK)
jedi >=0.17.2;<0.19.0         :  0.18.1 (OK)
jellyfish >=0.7               :  0.9.0 (OK)
jsonschema >=3.2.0            :  4.17.0 (OK)
keyring >=17.0.0              :  23.9.3 (OK)
nbconvert >=4.0               :  7.2.3 (OK)
numpydoc >=0.6.0              :  1.5.0 (OK)
parso >=0.7.0;<0.9.0          :  0.8.3 (OK)
pexpect >=4.4.0               :  4.8.0 (OK)
pickleshare >=0.4             :  0.7.5 (OK)
psutil >=5.3                  :  5.9.3 (OK)
pygments >=2.0                :  2.13.0 (OK)
pylint >=2.5.0;<3.0           :  2.15.5 (OK)
pylint_venv >=2.1.1           :  2.3.0 (OK)
pyls_spyder >=0.4.0           :  0.4.0 (OK)
pylsp >=1.6.0;<1.7.0          :  1.6.0 (OK)
pylsp_black >=1.2.0           :  1.2.1 (OK)
qdarkstyle >=3.0.2;<3.1.0     :  3.0.3 (OK)
qstylizer >=0.2.2             :  0.2.2 (OK)
qtawesome >=1.2.1             :  1.2.1 (OK)
qtconsole >=5.4.0;<5.5.0      :  5.4.0 (OK)
qtpy >=2.1.0                  :  2.2.1 (OK)
rtree >=0.9.7                 :  1.0.1 (OK)
setuptools >=49.6.0           :  65.5.1 (OK)
sphinx >=0.6.6                :  5.3.0 (OK)
spyder_kernels >=2.4.0;<2.5.0 :  2.4.0 (OK)
textdistance >=4.2.0          :  4.5.0 (OK)
three_merge >=0.1.1           :  0.1.1 (OK)
watchdog >=0.10.3             :  2.1.9 (OK)
xdg >=0.26                    :  0.28 (OK)
zmq >=22.1.0                  :  26.2.0 (OK)

# Optional:
cython >=0.21                 :  0.29.32 (OK)
matplotlib >=3.0.0            :  3.9.2 (OK)
numpy >=1.7                   :  1.26.4 (OK)
pandas >=1.1.1                :  2.2.3 (OK)
scipy >=0.17.0                :  1.13.1 (OK)
sympy >=0.7.3                 :  1.11.1 (OK)

Hey @ben-rowlinson, thanks for reporting. You said:

Edited $PATH using
export PATH=$PATH:/home/browlins/.local/bin

What happens if you remove that extra path from PATH? Do things work as expected in that case?

Hi,
What's the best way to remove the additional path part from the PATH? Is this different from PYTHONPATH - I've been reading that this might come into it too.
Based on the readback it seems to be more of an issue with installing an upgraded matplotlib package that causes an uncaught exception in ZMQStream library.
Kind regards,
Ben

From: Carlos Cordoba @.>
Sent: 04 October 2024 18:09
To: spyder-ide/spyder @.>
Cc: Ben Rowlinson @.>; Mention @.>
Subject: Re: [spyder-ide/spyder] Failure to connect to kernal (Issue #22634)
This email was sent to you by someone outside the University.
You should only click on links or attachments if you are certain that the email is genuine and the content is safe.
Hey @ben-rowlinsonhttps://github.com/ben-rowlinson, thanks for reporting. You said:
Edited $PATH using
export PATH=$PATH:/home/browlins/.local/bin
What happens if you remove that extra path from PATH? Do things work as expected in that case?
—
Reply to this email directly, view it on GitHubhttps://github.com/spyder-ide/spyder/issues/22634#issuecomment-2394171765, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BLGPU6FSWVBCO36YT4HO5NTZZ3DTBAVCNFSM6AAAAABPLSUFD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJUGE3TCNZWGU.
You are receiving this because you were mentioned.Message ID: @.***>
The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. Is e buidheann carthannais a th’ ann an Oilthigh Dhùn Èideann, clàraichte an Alba, àireamh clàraidh SC005336.

What's the best way to remove the additional path part from the PATH?

You said you did
export PATH=$PATH:/home/browlins/.local/bin

So, where did you do that? In the console? Or did you add that line to your .bashrc?

Is this different from PYTHONPATH - I've been reading that this might come into it too.

Yes, PATH is the set of directories used by the system to find executables.

Based on the readback it seems to be more of an issue with installing an upgraded matplotlib package that causes an uncaught exception in ZMQStream library.

It could be. Did you use pip to do do that?
If so, then that would explain why you ended up mixing Python packages from two different environments: /opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9 and /home/browlins/.local/lib/python3.9/ (which is shown in your error report above).

Hi Carlos,
Yep, it was in the terminal that I changed the PATH. The console in Spyder wouldn't start at all.
I have reset the PATH variable to remove the added parts and deleted the zmq folder from my local site-packages folder.
The kernel is running as expected when using the command:
LIBGL_ALWAYS_SOFTWARE=1 spyder5
Thanks for your help with this!
Kind regards,
Ben

From: Carlos Cordoba @.>
Sent: 07 October 2024 18:19
To: spyder-ide/spyder @.>
Cc: Ben Rowlinson @.>; Mention @.>
Subject: Re: [spyder-ide/spyder] Failure to connect to kernal (Issue #22634)
This email was sent to you by someone outside the University.
You should only click on links or attachments if you are certain that the email is genuine and the content is safe.
What's the best way to remove the additional path part from the PATH?
You said you did
export PATH=$PATH:/home/browlins/.local/bin
So, where did you do that? In the console? Or did you add that line to your .bashrc?
Is this different from PYTHONPATH - I've been reading that this might come into it too.
Yes, PATH is the set of directories used by the system to find executables.
Based on the readback it seems to be more of an issue with installing an upgraded matplotlib package that causes an uncaught exception in ZMQStream library.
It could be. Did you use pip to do do that?
If so, then that would explain why you ended up mixing Python packages from two different environments: /opt/spyder-5.4.1/envs/spyder-5.4.1.dev0/lib/python3.9 and /home/browlins/.local/lib/python3.9/ (which is shown in your error report above).
—
Reply to this email directly, view it on GitHubhttps://github.com/spyder-ide/spyder/issues/22634#issuecomment-2397481918, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BLGPU6GIJGUH25HYJHVHALLZ2K7BHAVCNFSM6AAAAABPLSUFD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJXGQ4DCOJRHA.
You are receiving this because you were mentioned.Message ID: @.***>
The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. Is e buidheann carthannais a th’ ann an Oilthigh Dhùn Èideann, clàraichte an Alba, àireamh clàraidh SC005336.

Great! Thanks for letting us know about it.


doc: Update WindowsBuild.md

This pull request contains some cosmetic changes (typo + breaking down of the cmake command) to the WindowsBuild.md documentation file and a change to the cmake options listed in that same documentation (LLVM_ENABLE_LIBEDIT=NO)  which is necessary to compile correctly on Windows. I checked in the azure pipeline configuration of compnerd to make sure he was using that option too.
This should make the life a little easier for those trying to replicate the build process on Windows.
NOTE: I was not sure if it was better to split the commits or to make a single one.

@swift-ci please smoke test

@patrickdes - wrt your note - the split commits that you did are definitely much nicer because they make it easier to review.

Windows test failure is waiting the automerger, its not related to this change.


[tests-only] Consistent interaction names

This PR makes pact interaction names more consistent
All interaction names follow the same pattern i.e. .uponReceiving(a <METHOD> request ...)
closes https://github.com/owncloud/owncloud-sdk/issues/723

LGTM


hyperband and rl search strategies are nut running for Tabular prediction.

import autogluon as ag
from autogluon.task import TabularPrediction as task

import sklearn.datasets
import pandas as pd

cancer_data = sklearn.datasets.load_breast_cancer(return_X_y=False)
data = pd.DataFrame(cancer_data['data'], columns=cancer_data['feature_names'])
data['target'] = cancer_data['target']

gbm_options = {
    'num_boost_round': 100,
    'num_leaves': ag.space.Int(lower=26, upper=66, default=36),
}

hyperparameters = {
    'GBM': gbm_options,
}

hp_tune = True
time_limits = 2 * 60
num_trials = 3
output_directory = './agModels--tuningCancerDataset'
data = task.Dataset(data)
label_column = 'target'
search_strategy = 'hyperband'
predictor = task.fit(
    train_data=data,
    holdout_frac=0.3,
    label=label_column,
    output_directory=output_directory,
    time_limits=time_limits,
    num_trials=num_trials,
    hyperparameter_tune=hp_tune,
    hyperparameters=hyperparameters,
    search_strategy=search_strategy,
    auto_stack=False,
    stack_ensemble_levels=0
)

The error:
File "/Users/rmelikbe/Desktop/repos/autogluon/autogluon/utils/tabular/ml/trainer/abstract_trainer.py", line 354, in train_single_full
    Y_train=y_train, Y_test=y_test, scheduler_options=(self.scheduler_func, self.scheduler_options), verbosity=self.verbosity)
  File "/Users/rmelikbe/Desktop/repos/autogluon/autogluon/utils/tabular/ml/models/lgb/lgb_model.py", line 285, in hyperparameter_tune
    scheduler = scheduler_func(lgb_trial, **scheduler_options)
  File "/Users/rmelikbe/Desktop/repos/autogluon/autogluon/scheduler/hyperband.py", line 136, in __init__
    reward_attr=reward_attr, visualizer=visualizer, dist_ip_addrs=dist_ip_addrs)
  File "/Users/rmelikbe/Desktop/repos/autogluon/autogluon/scheduler/fifo.py", line 91, in __init__
    self.searcher = searcher_factory(searcher, **kwargs)
  File "/Users/rmelikbe/Desktop/repos/autogluon/autogluon/searcher/searcher_factory.py", line 14, in searcher_factory
    raise AssertionError("name = '{}' not supported".format(name))

What is the output of the assertion message?
hyperband is not a search strategy, but a scheduling strategy which can be run with different underlying searchers. Currently supported are 'random' (default), 'skopt', 'grid'. You probably want to keep it at 'random' (as this is what gives you the Hyperband method as published).
In the near future, there will be more searchers being supported here, but it may take a few months still.

I am personally not much familiar how a call to task.fit maps to the creation of a scheduler. When you create a scheduler (FIFOScheduler, HyperbandScheduler), you can pass searcher and search_options, and searcher -> name in searcher_factory. You seem to be using search_strategy above ...

Hi @mseeger yep, I was using hyperband as a search_strategy. I wanted to use HyperbandScheduler behind the scenes. If it is not supported at this moment, it would be correct to remove it from docstring: https://github.com/awslabs/autogluon/blob/a1347ea81ff678a6047cc1723c32fcf0dc81bbf2/autogluon/task/tabular_prediction/tabular_prediction.py#L179

Hello,
this is not the problem here.
If you look into tabular_predicition.py you see that towards the end, when scheduler_options are set, you have
searcher = search_strategy
This is wrong for Hyperband. HB is not a searcher, but a scheduler, and you want searcher = 'random' if search_strategy is 'hyperband'. This would fix your issue.
I still think that code should be refactored, because it mixes searcher and scheduler, something we need to keep apart for future use cases. @Innixma ?
One complexity here is that now every searcher can be used with the two different schedulers we have, namely FIFO and Hyperband. Currently, all searchers can be used with FIFO, but only 'random' can be used with Hyperband. But this will change at some point ...

In fact, let me try and fix this for now. I'll do a pull request and notify you.

Have a look at #316

In fact, let me try and fix this for now. I'll do a pull request and notify you.

Thanks for reply. Yep it is a a confusing that in search_strategy you put hyperband.
What about rl scheduler ? This also works only with random.

Hello, rl is a searcher, it works with FIFO scheduler. There are currently only two schedulers, FIFO and Hyperband. And making Hyperband work with searcher != random is not trivial, we work on this.
But maybe we should not bother the user with the distinction between scheduler and searcher. Let us see what others say.

If 'rl' does not work for you, this has a different reason, check what you pass for search_options.
I have no idea what the RL searcher is doing,

There is another bug that affects why 'rl' does not work. It has to be rewritten (but not by me).

Hyperband should now work with TabularPrediction thanks to:  https://github.com/awslabs/autogluon/pull/316
We will look into why 'rl' does not work.


train_flux_lora_deepspeed.py Error : The size of tensor a (2) must match the size of tensor b (64)

Well, this is new for me.
08/23/2024 10:47:34 - INFO - __main__ - ***** Running training *****
08/23/2024 10:47:34 - INFO - __main__ -   Num Epochs = 500
08/23/2024 10:47:34 - INFO - __main__ -   Instantaneous batch size per device = 2
08/23/2024 10:47:34 - INFO - __main__ -   Total train batch size (w. parallel, distributed & accumulation) = 8
08/23/2024 10:47:34 - INFO - __main__ -   Gradient Accumulation steps = 2
08/23/2024 10:47:34 - INFO - __main__ -   Total optimization steps = 2000
Checkpoint 'latest' does not exist. Starting a new training run.
Steps:   0%|                                                                                | 0/2000 [00:00<?, ?it/s][rank1]: Traceback (most recent call last):
[rank1]:   File "/workspace/x-flux/train_flux_lora_deepspeed.py", line 301, in <module>
[rank1]:     main()
[rank1]:   File "/workspace/x-flux/train_flux_lora_deepspeed.py", line 226, in main
[rank1]:     x_t = (1 - t) * x_1 + t * x_0
[rank1]: RuntimeError: The size of tensor a (2) must match the size of tensor b (64) at non-singleton dimension 2
[rank0]: Traceback (most recent call last):
[rank0]:   File "/workspace/x-flux/train_flux_lora_deepspeed.py", line 301, in <module>
[rank0]:     main()
[rank0]:   File "/workspace/x-flux/train_flux_lora_deepspeed.py", line 226, in main
[rank0]:     x_t = (1 - t) * x_1 + t * x_0
[rank0]: RuntimeError: The size of tensor a (2) must match the size of tensor b (64) at non-singleton dimension 2
Steps:   0%|                                                                                | 0/2000 [00:01<?, ?it/s]
[rank0]:[W823 10:47:36.712866358 ProcessGroupNCCL.cpp:1168] Warning: WARNING: process group has NOT been destroyed before we destruct ProcessGroupNCCL. On normal program exit, the application should call destroy_process_group to ensure that any pending NCCL operations have finished in this process. In rare cases this process can exit before this point and block the progress of another member of the process group. This constraint has always been present,  but this warning has only been added since PyTorch 2.4 (function operator())
E0823 10:47:40.287000<PHONE_NUMBER>99072 torch/distributed/elastic/multiprocessing/api.py:833] failed (exitcode: 1) local_rank: 0 (pid: 3328) of binary: /workspace/x-flux/xflux_env/bin/python3
Traceback (most recent call last):
  File "/workspace/x-flux/xflux_env/bin/accelerate", line 8, in <module>
    sys.exit(main())
  File "/workspace/x-flux/xflux_env/lib/python3.10/site-packages/accelerate/commands/accelerate_cli.py", line 46, in main
    args.func(args)
  File "/workspace/x-flux/xflux_env/lib/python3.10/site-packages/accelerate/commands/launch.py", line 1067, in launch_command
    deepspeed_launcher(args)
  File "/workspace/x-flux/xflux_env/lib/python3.10/site-packages/accelerate/commands/launch.py", line 771, in deepspeed_launcher
    distrib_run.run(args)
  File "/workspace/x-flux/xflux_env/lib/python3.10/site-packages/torch/distributed/run.py", line 892, in run
    elastic_launch(
  File "/workspace/x-flux/xflux_env/lib/python3.10/site-packages/torch/distributed/launcher/api.py", line 133, in __call__
    return launch_agent(self._config, self._entrypoint, list(args))
  File "/workspace/x-flux/xflux_env/lib/python3.10/site-packages/torch/distributed/launcher/api.py", line 264, in launch_agent
    raise ChildFailedError(
torch.distributed.elastic.multiprocessing.errors.ChildFailedError:
============================================================
train_flux_lora_deepspeed.py FAILED

seems like the bug with reshaping when batch size > 1

Hi, I already encountered this issue. Have you found the solution?


Fix: #306: send_signal_to_dart() function in rust code isn't generated when message contains enum and oneof fields in .protofile

Changes
I've found if enum and oneof are used in the message definition, then statement can be like }\n\n// [RINF:RUST-SIGNAL] in parsing proto file. That causes not generating send_signal_to_dart() function.
So, my fix is simply string compare logic using contains() instead of startsWith().
I think in most cases it works. But I would suggest using a grammar parser in the future.
Also added a unit test to verify the fix.
To run it flutter test on flutter_ffi_plugin folder.
Hope this helps.

Hello @yeoupooh, Indeed, it would be nice to implement a grammar parser someday. For now, I will publish a new version as soon as the tests pass. Thanks for your contribution :)

Currently, the CI system as well as Python scripts utilizes the example app directory for tests, so I moved some Protobuf definitions into that folder. Will merge it soon!


Use StructuredScript

rust bitcoin script has an update on the chunker branch and these changes make it compatible again

@stillsaiko can you make the change to bitvm branch?


InstallUpstreamKernel.py: getting console was unsuccessful some times when sending credentials to prompt

[   32.081422] IPv6: ADDRCONF(NETDEV_CHANGE): vnic1: link becomes ready^M
[   34.755227] IPv6: ADDRCONF(NETDEV_CHANGE): vnic2: link becomes ready^M
^M^M
Red Hat Enterprise Linux 8.1 (Ootpa)^M
Kernel 5.7.0-rc4+ on an ppc64le^M
^M
Activate the web console with: systemctl enable --now cockpit.socket^M
^M
ltc-zz1b login: [console-expect]#command-line line 0: Unsupported option "afstokenpassing"^M

ERROR

======================================================================
ERROR: runTest (testcases.InstallUpstreamKernel.InstallUpstreamKernel)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/jenkins/jenkins_home/workspace/ioci/testcases/InstallUpstreamKernel.py", line 150, in runTest
    res = con.run_command("uname -r")
  File "/home/jenkins/jenkins_home/workspace/ioci/common/OpTestSSH.py", line 225, in run_command
    return self.util.run_command(self, command, timeout, retry)
  File "/home/jenkins/jenkins_home/workspace/ioci/common/OpTestUtil.py", line 1611, in run_command
    output = self.try_command(term_obj, command, timeout)
  File "/home/jenkins/jenkins_home/workspace/ioci/common/OpTestUtil.py", line 1631, in try_command
    pty = term_obj.get_console()
  File "/home/jenkins/jenkins_home/workspace/ioci/common/OpTestSSH.py", line 205, in get_console
    self.connect(logger)
  File "/home/jenkins/jenkins_home/workspace/ioci/common/OpTestSSH.py", line 185, in connect
    self.check_set_term()
  File "/home/jenkins/jenkins_home/workspace/ioci/common/OpTestSSH.py", line 201, in check_set_term
    self, setup_term_flag)
  File "/home/jenkins/jenkins_home/workspace/ioci/common/OpTestUtil.py", line 1506, in setup_term
    msg="Getting login and sudo not successful, probably connection issue, retry")
common.Exceptions.ConsoleSettings: Setting the prompt or logging in for the console was not successful, check credentials and review the following for more details
Expect Before Buffer="command-line line 0: Unsupported option "afstokenpassing"^M^M
"
Expect After Buffer="<class 'pexpect.exceptions.EOF'>"
Message="Getting login and sudo not successful, probably connection issue, retry"

----------------------------------------------------------------------
Ran 1 test in 1584.104s

FAILED (errors=1)
2020-05-05 18:22:30,565:op-test:<module>:INFO:Exit with Result errors="1" and failures="0"
2020-05-05 18:22:30,566:op-test.common.OpTestUtil:cleanup:INFO:OpTestSystem Starting to Gather ESEL's
2020-05-05 18:22:30,566:op-test.common.OpTestUtil:dump_versions:INFO:Log Location: /home/jenkins/jenkins_home/workspace/ioci/test-reports/test-run-20200505175528/*debug*
2020-05-05 18:22:30,567:op-test.common.OpTestUtil:dump_versions:INFO:

Looking into the issue.

Tried Installation  on OpenBMC box, it ran successfully.
./op-test -c ./../config/wspoon2.cnf --run testcases.InstallUpstreamKernel.InstallUpstreamKernel
System was installed with the upstream kernel.
Discussed with @abdhaleegit he mentioned it happens every 10 tries on PowerVM. Will check on VM too.

Was able to recreate the issue on PowerVM, looking into the issue.

@harihare I am seeing this issue at different stages of the test here is the new trace
[console-expect]#echo $?
echo $?
0
[console-expect]#^M~.

Red Hat Enterprise Linux 8.1 (Ootpa)
Kernel 4.18.0-147.el8.ppc64le on an ppc64le

Activate the web console with: systemctl enable --now cockpit.socket

ltc-zz1b-lp7 login: ERROR

======================================================================
ERROR: runTest (testcases.InstallUpstreamKernel.InstallUpstreamKernel)
----------------------------------------------------------------------
Traceback (most recent call last):
  File<EMAIL_ADDRESS>line 147, in runTest
    raw_pty = self.cv_SYSTEM.console.get_console()
  File<EMAIL_ADDRESS>line 487, in get_console
    None, self.system.block_setup_term)
  File<EMAIL_ADDRESS>line 1506, in setup_term
    msg="Getting login and sudo not successful, probably connection issue, retry")
common.Exceptions.ConsoleSettings: Setting the prompt or logging in for the console was not successful, check credentials and review the following for more details
Expect Before Buffer="Red Hat Enterprise Linux 8.1 (Ootpa)
Kernel 4.18.0-147.el8.ppc64le on an ppc64le

Activate the web console with: systemctl enable --now cockpit.socket

ltc-zz1b-lp7 login: "
Expect After Buffer="<class 'pexpect.exceptions.TIMEOUT'>"
Message="Getting login and sudo not successful, probably connection issue, retry"

in another system i see this
console-expect]#echo $?
echo $?
0
[console-expect]#^M~.

Red Hat Enterprise Linux 8.1 (Ootpa)
Kernel 4.18.0-147.el8.ppc64le on an ppc64le

Activate the web console with: systemctl enable --now cockpit.socket

ltc-zz1b-lp2 login:

Red Hat Enterprise Linux 8.1 (Ootpa)
Kernel 4.18.0-147.el8.ppc64le on an ppc64le

Activate the web console with: systemctl enable --now cockpit.socket

ltc-zz1b-lp2 login: root

root

2020-06-29 18:11:58,707:op-test.common.OpTestUtil:get_login:WARNING:OpTestSystem Problem with the login and/or password prompt, raised Exception ConsoleSettings but continuing
ERROR

======================================================================
ERROR: runTest (testcases.InstallUpstreamKernel.InstallUpstreamKernel)
----------------------------------------------------------------------
Traceback (most recent call last):
  File<EMAIL_ADDRESS>line 147, in runTest
    raw_pty = self.cv_SYSTEM.console.get_console()
  File<EMAIL_ADDRESS>line 487, in get_console
    None, self.system.block_setup_term)
  File<EMAIL_ADDRESS>line 1490, in setup_term
    system_obj.cv_HOST, term_obj, pty, self.build_prompt(system_obj.prompt))
  File<EMAIL_ADDRESS>line 1299, in get_login
    msg="Problem with the login and/or password prompt, probably a connection or credential issue, retry")
common.Exceptions.ConsoleSettings: Setting the prompt or logging in for the console was not successful, check credentials and review the following for more details
Expect Before Buffer="root

"
Expect After Buffer="<class 'pexpect.exceptions.TIMEOUT'>"
Message="Problem with the login and/or password prompt, probably a connection or credential issue, retry"

----------------------------------------------------------------------
Ran 1 test in 1342.156s

FAILED (errors=1)
2020-06-29 18:12:00,712:op-test:<module>:INFO:Exit with Result errors="1" and failures="0"
2020-06-29 18:12:00,712:op-test.common.OpTestUtil:cleanup:INFO:OpTestSystem Starting to Gather ESEL's
2020-06-29 18:12:00,713:op-test.common.OpTestUtil:dump_versions:INFO:Log Location: /home/jenkins/jenkins_home/workspace/ioci@2/test-reports/test-run-20200629174900/*debug*
2020-06-29 18:12:00,713:op-test.common.OpTestUtil:dump_versions:INFO:

@harihare We are seeing this more often, can you please provide some comments if any thing from your debugging ?

The below patch fixes the issue, will be sending out the same
diff --git a/common/OpTestUtil.py b/common/OpTestUtil.py
index 162b8ce..34e6ce0 100644
--- a/common/OpTestUtil.py
+++ b/common/OpTestUtil.py
@@ -1454,7 +1454,7 @@ class OpTestUtil():
             return
         rc = pty.expect(['login: $', ".*#$", ".*# $", ".*\$", "~>", "~ #",
-                         'Petitboot', pexpect.TIMEOUT, pexpect.EOF], timeout=10)
+                         'Petitboot', pexpect.TIMEOUT, pexpect.EOF], timeout=100)
         if rc == 0:
             track_obj.PS1_set, track_obj.LOGIN_set = self.get_login(
                 system_obj.cv_HOST, term_obj, pty, self.build_prompt(system_obj.prompt))

looks like we hit it again with different code path
[  OK  ] Started LSB: Starts and stops the InfiniBand SRP client service.

Red Hat Enterprise Linux 8.1 Beta (Ootpa)
Kernel 4.18.0-144.el8.ppc64le on an ppc64le

Activate the web console with: systemctl enable --now cockpit.socket

ltc-zz3-lp1 login: 5

5
Password: [console-expect]#command-line line 0: Unsupported option "afstokenpassing"^M
login: timed out after 60 seconds

Red Hat Enterprise Linux 8.1 Beta (Ootpa)
Kernel 4.18.0-144.el8.ppc64le on an ppc64le

Activate the web console with: systemctl enable --now cockpit.socket

ltc-zz3-lp1 login:

^M~.
~.command-line line 0: Unsupported option "afstokenpassing"^M

^M~.
ERROR

======================================================================
ERROR: runTest (testcases.InstallUpstreamKernel.InstallUpstreamKernel)
----------------------------------------------------------------------
Traceback (most recent call last):
  File<EMAIL_ADDRESS>line 92, in runTest
    (self.home, self.home))
  File<EMAIL_ADDRESS>line 225, in run_command
    return self.util.run_command(self, command, timeout, retry)
  File<EMAIL_ADDRESS>line 1611, in run_command
    output = self.try_command(term_obj, command, timeout)
  File<EMAIL_ADDRESS>line 1631, in try_command
    pty = term_obj.get_console()
  File<EMAIL_ADDRESS>line 205, in get_console
    self.connect(logger)
  File<EMAIL_ADDRESS>line 185, in connect
    self.check_set_term()
  File<EMAIL_ADDRESS>line 201, in check_set_term
    self, setup_term_flag)
  File<EMAIL_ADDRESS>line 1506, in setup_term
    msg="Getting login and sudo not successful, probably connection issue, retry")
common.Exceptions.ConsoleSettings: Setting the prompt or logging in for the console was not successful, check credentials and review the following for more details
Expect Before Buffer="command-line line 0: Unsupported option "afstokenpassing"

~."
Expect After Buffer="<class 'pexpect.exceptions.TIMEOUT'>"
Message="Getting login and sudo not successful, probably connection issue, retry"

@harihare can you have a look at it ?

@abdhaleegit so just increasing the timeout solves the issue? I think increasing it 10-fold might be excessive, but in your testing, can you tell how many seconds would be acceptable? Can you send a PR? Thanks

@klauskiwi just increasing the timeout did not solve the problem.. looks like there is more to it. I able to see the problem even with increase timeout. @harihare I am seeing consistently on  p10 lpars
2021-01-13 07:57:14,270:op-test.common.OpTestHMC:write:DEBUG:Red Hat Enterprise Linux 8.3 (Ootpa)
2021-01-13 07:57:14,270:op-test.common.OpTestHMC:write:DEBUG:Kernel 5.11.0-rc2+ on an ppc64le
2021-01-13 07:57:14,270:op-test.common.OpTestHMC:write:DEBUG:
2021-01-13 07:57:14,271:op-test.common.OpTestHMC:write:DEBUG:Activate the web console with:
2021-01-13 07:57:14,273:op-test.common.OpTestHMC:write:DEBUG:systemctl enable --now cockpit.socket
2021-01-13 07:57:14,273:op-test.common.OpTestHMC:write:DEBUG:
2021-01-13 07:57:14,273:op-test.common.OpTestHMC:write:DEBUG:ltcden11-lp1 login: 5
2021-01-13 07:57:14,273:op-test.common.OpTestHMC:write:DEBUG:
2021-01-13 07:57:14,273:op-test.common.OpTestHMC:write:DEBUG:5
2021-01-13 07:57:14,273:op-test.common.OpTestHMC:write:DEBUG:Password:
2021-01-13 07:57:14,275:op-test.common.OpTestSystem:goto_state:DEBUG:OpTestSystem TRANSITIONED TO: 6
2021-01-13 07:57:14,276:op-test.common.OpTestSOL:run:DEBUG:Starting console
2021-01-13 07:57:14,276:op-test.common.OpTestSSH:connect:DEBUG:sshpass -p passw0rd  ssh -p 22 -l root 9.ab.cd.efg -o PubkeyAuthentication=no -o afstokenpassing=no -q -o 'UserKnownHostsFile=/dev/null'  -o 'StrictHostKeyChecking=no'
2021-01-13 07:57:14,276:op-test.common.OpTestSOL:nontimeout_run:DEBUG:Starting console for new SOL thread
2021-01-13 07:57:16,284:op-test.common.OpTestSSH:write:DEBUG:command-line line 0: Unsupported option "afstokenpassing"
2021-01-13 07:57:16,285:op-test.common.OpTestSSH:write:DEBUG:
2021-01-13 07:57:16,386:op-test.common.OpTestSSH:write:DEBUG:
2021-01-13 07:57:16,386:op-test.common.OpTestSSH:write:DEBUG:~.
2021-01-13 07:57:16,386:op-test.common.OpTestSSH:close:DEBUG:CLOSE Expect Buffer ID=0x7fffa535cf28
2021-01-13 07:57:16,487:op-test.testcases.InstallUpstreamKernel:runTest:DEBUG:Downloading linux kernel
2021-01-13 07:57:16,487:op-test.common.OpTestSSH:connect:DEBUG:sshpass -p passw0rd  ssh -p 22 -l root 9.ab.cd.efg -o PubkeyAuthentication=no -o afstokenpassing=no -q -o 'UserKnownHostsFile=/dev/null'  -o 'StrictHostKeyChecking=no'
2021-01-13 07:57:18,495:op-test.common.OpTestSSH:write:DEBUG:command-line line 0: Unsupported option "afstokenpassing"
2021-01-13 07:57:18,495:op-test.common.OpTestSSH:write:DEBUG:
2021-01-13 07:57:18,596:op-test.common.OpTestSSH:write:DEBUG:
2021-01-13 07:57:18,597:op-test.common.OpTestSSH:write:DEBUG:~.
2021-01-13 07:57:18,597:op-test.common.OpTestSSH:close:DEBUG:CLOSE Expect Buffer ID=0x7fffa48c0f28
2021-01-13 07:57:20,703:op-test:<module>:INFO:Exit with Result errors="1" and failures="0"
2021-01-13 07:57:20,703:op-test.common.OpTestUtil:cleanup:INFO:OpTestSystem Starting to Gather ESEL's
2021-01-13 07:57:20,703:op-test.common.OpTestUtil:cleanup:DEBUG:OpTestSystem encountered a problem trying to gather ESEL's, Exception='NoneType' object has no attribute 'ipmi_sel_elist'
2021-01-13 07:57:20,704:op-test.common.OpTestUtil:dump_versions:INFO:Log Location: /home/jenkins/jenkins_home/workspace/ioci@p10/test-reports/test-run-20210113072941/*debug*
2021-01-13 07:57:20,704:op-test.common.OpTestUtil:dump_versions:INFO:

2021-01-13 07:57:20,705:op-test.common.OpTestUtil:cleanup:DEBUG:self.conf.args.qemu_scratch_disk=None
2021-01-13 07:57:20,705:op-test:<module>:DEBUG:Exit Results with No Failures
2021-01-13 07:57:20,705:op-test:<module>:DEBUG:Exit Results Error #1=
(<testcases.InstallUpstreamKernel.InstallUpstreamKernel testMethod=runTest>, 'Traceback (most recent call last):\n
 File<EMAIL_ADDRESS>line 92, in runTest\n    (self.home, self.home))\n
 File<EMAIL_ADDRESS>line 225, in run_command\n    return self.util.run_command(self, command, timeout, retry)\n
 File<EMAIL_ADDRESS>line 1611, in run_command\n    output = self.try_command(term_obj, command, timeout)\n
 File<EMAIL_ADDRESS>line 1631, in try_command\n    pty = term_obj.get_console()\n
 File<EMAIL_ADDRESS>line 205, in get_console\n    self.connect(logger)\n
 File<EMAIL_ADDRESS>line 185, in connect\n    self.check_set_term()\n
 File<EMAIL_ADDRESS>line 201, in check_set_term\n    self, setup_term_flag)\n
 File<EMAIL_ADDRESS>line 1477, in setup_term\n    msg="Getting login and sudo not successful, probably connection or credential issue, retry")\ncommon.Exceptions.ConsoleSettings: Setting the prompt or logging in for the console was not successful, check credentials and review the following for more details\nExpect Before Buffer="\r\n~."\nExpect After Buffer="<class \'pexpect.exceptions.EOF\'>" \nMessage="Getting login and sudo not successful, probably connection or credential issue, retry"\n')
2021-01-13 07:58:14,028:op-test.common.OpTestHMC:write:DEBUG:login: timed out after 60 seconds
2021-01-13 07:58:14,279:op-test.common.OpTestSOL:nontimeout_run:DEBUG:Terminating SOL monitoring thread
2021-01-13 07:58:14,279:op-test.common.OpTestSOL:run:DEBUG:Exiting console
2021-01-13 07:58:14,279:op-test.common.OpTestUtil:cleanup:DEBUG:self.conf.args.qemu_scratch_disk=None

@klauskiwi just increasing the timeout did not solve the problem.. looks like there is more to it. I able to see the problem even with increase timeout. @harihare I am seeing consistently on  p10 lpars
2021-01-13 07:57:14,270:op-test.common.OpTestHMC:write:DEBUG:Red Hat Enterprise Linux 8.3 (Ootpa)
2021-01-13 07:57:14,270:op-test.common.OpTestHMC:write:DEBUG:Kernel 5.11.0-rc2+ on an ppc64le
2021-01-13 07:57:14,270:op-test.common.OpTestHMC:write:DEBUG:
2021-01-13 07:57:14,271:op-test.common.OpTestHMC:write:DEBUG:Activate the web console with:
2021-01-13 07:57:14,273:op-test.common.OpTestHMC:write:DEBUG:systemctl enable --now cockpit.socket
2021-01-13 07:57:14,273:op-test.common.OpTestHMC:write:DEBUG:
2021-01-13 07:57:14,273:op-test.common.OpTestHMC:write:DEBUG:ltcden11-lp1 login: 5
2021-01-13 07:57:14,273:op-test.common.OpTestHMC:write:DEBUG:
2021-01-13 07:57:14,273:op-test.common.OpTestHMC:write:DEBUG:5
2021-01-13 07:57:14,273:op-test.common.OpTestHMC:write:DEBUG:Password:
2021-01-13 07:57:14,275:op-test.common.OpTestSystem:goto_state:DEBUG:OpTestSystem TRANSITIONED TO: 6
2021-01-13 07:57:14,276:op-test.common.OpTestSOL:run:DEBUG:Starting console
2021-01-13 07:57:14,276:op-test.common.OpTestSSH:connect:DEBUG:sshpass -p passw0rd  ssh -p 22 -l root 9.ab.cd.efg -o PubkeyAuthentication=no -o afstokenpassing=no -q -o 'UserKnownHostsFile=/dev/null'  -o 'StrictHostKeyChecking=no'
2021-01-13 07:57:14,276:op-test.common.OpTestSOL:nontimeout_run:DEBUG:Starting console for new SOL thread
2021-01-13 07:57:16,284:op-test.common.OpTestSSH:write:DEBUG:command-line line 0: Unsupported option "afstokenpassing"
2021-01-13 07:57:16,285:op-test.common.OpTestSSH:write:DEBUG:
2021-01-13 07:57:16,386:op-test.common.OpTestSSH:write:DEBUG:
2021-01-13 07:57:16,386:op-test.common.OpTestSSH:write:DEBUG:~.
2021-01-13 07:57:16,386:op-test.common.OpTestSSH:close:DEBUG:CLOSE Expect Buffer ID=0x7fffa535cf28
2021-01-13 07:57:16,487:op-test.testcases.InstallUpstreamKernel:runTest:DEBUG:Downloading linux kernel
2021-01-13 07:57:16,487:op-test.common.OpTestSSH:connect:DEBUG:sshpass -p passw0rd  ssh -p 22 -l root 9.ab.cd.efg -o PubkeyAuthentication=no -o afstokenpassing=no -q -o 'UserKnownHostsFile=/dev/null'  -o 'StrictHostKeyChecking=no'
2021-01-13 07:57:18,495:op-test.common.OpTestSSH:write:DEBUG:command-line line 0: Unsupported option "afstokenpassing"
2021-01-13 07:57:18,495:op-test.common.OpTestSSH:write:DEBUG:
2021-01-13 07:57:18,596:op-test.common.OpTestSSH:write:DEBUG:
2021-01-13 07:57:18,597:op-test.common.OpTestSSH:write:DEBUG:~.
2021-01-13 07:57:18,597:op-test.common.OpTestSSH:close:DEBUG:CLOSE Expect Buffer ID=0x7fffa48c0f28
2021-01-13 07:57:20,703:op-test:<module>:INFO:Exit with Result errors="1" and failures="0"
2021-01-13 07:57:20,703:op-test.common.OpTestUtil:cleanup:INFO:OpTestSystem Starting to Gather ESEL's
2021-01-13 07:57:20,703:op-test.common.OpTestUtil:cleanup:DEBUG:OpTestSystem encountered a problem trying to gather ESEL's, Exception='NoneType' object has no attribute 'ipmi_sel_elist'
2021-01-13 07:57:20,704:op-test.common.OpTestUtil:dump_versions:INFO:Log Location: /home/jenkins/jenkins_home/workspace/ioci@p10/test-reports/test-run-20210113072941/*debug*
2021-01-13 07:57:20,704:op-test.common.OpTestUtil:dump_versions:INFO:

2021-01-13 07:57:20,705:op-test.common.OpTestUtil:cleanup:DEBUG:self.conf.args.qemu_scratch_disk=None
2021-01-13 07:57:20,705:op-test:<module>:DEBUG:Exit Results with No Failures
2021-01-13 07:57:20,705:op-test:<module>:DEBUG:Exit Results Error #1=
(<testcases.InstallUpstreamKernel.InstallUpstreamKernel testMethod=runTest>, 'Traceback (most recent call last):\n
 File<EMAIL_ADDRESS>line 92, in runTest\n    (self.home, self.home))\n
 File<EMAIL_ADDRESS>line 225, in run_command\n    return self.util.run_command(self, command, timeout, retry)\n
 File<EMAIL_ADDRESS>line 1611, in run_command\n    output = self.try_command(term_obj, command, timeout)\n
 File<EMAIL_ADDRESS>line 1631, in try_command\n    pty = term_obj.get_console()\n
 File<EMAIL_ADDRESS>line 205, in get_console\n    self.connect(logger)\n
 File<EMAIL_ADDRESS>line 185, in connect\n    self.check_set_term()\n
 File<EMAIL_ADDRESS>line 201, in check_set_term\n    self, setup_term_flag)\n
 File<EMAIL_ADDRESS>line 1477, in setup_term\n    msg="Getting login and sudo not successful, probably connection or credential issue, retry")\ncommon.Exceptions.ConsoleSettings: Setting the prompt or logging in for the console was not successful, check credentials and review the following for more details\nExpect Before Buffer="\r\n~."\nExpect After Buffer="<class \'pexpect.exceptions.EOF\'>" \nMessage="Getting login and sudo not successful, probably connection or credential issue, retry"\n')
2021-01-13 07:58:14,028:op-test.common.OpTestHMC:write:DEBUG:login: timed out after 60 seconds
2021-01-13 07:58:14,279:op-test.common.OpTestSOL:nontimeout_run:DEBUG:Terminating SOL monitoring thread
2021-01-13 07:58:14,279:op-test.common.OpTestSOL:run:DEBUG:Exiting console
2021-01-13 07:58:14,279:op-test.common.OpTestUtil:cleanup:DEBUG:self.conf.args.qemu_scratch_disk=None

@harihare I'm seeing same issue on my lpar also .
Running tests...

E749: empty buffer
:  runTest (testcases.InstallUpstreamKernel.InstallUpstreamKernel) ... ERROR (20.245s)
======================================================================
ERROR [20.245s]: runTest (testcases.InstallUpstreamKernel.InstallUpstreamKernel)
Traceback (most recent call last):
File<EMAIL_ADDRESS>line 65, in setUp
self.console_thread = OpSOLMonitorThread(1, "console")
File<EMAIL_ADDRESS>line 63, in init
self.c = self.system.console.get_console(logger=self.logger)
File<EMAIL_ADDRESS>line 487, in get_console
None, self.system.block_setup_term)
File<EMAIL_ADDRESS>line 1506, in setup_term
msg="Getting login and sudo not successful, probably connection issue, retry")
common.Exceptions.ConsoleSettings: Setting the prompt or logging in for the console was not successful, check credentials and review the following for more details
Expect Before Buffer="
^H
^[[7mE749: empty buffer^[[27m^M
:^H
^[[7mE749: empty buffer^[[27m^M
:^H
^[[7mE749: empty buffer^[[27m^M
:PS1=[console-expect]#^M
^[[7mE492: Not an editor command: PS1=[console-expect]#^[[27m^M
:^H
^[[7mE749: empty buffer^[[27m^M
:^H
^[[7mE749: empty buffer^[[27m^M
:^H
^[[7mE749: empty buffer^[[27m^M
:^H
^[[7mE749: empty buffer^[[27m^M
:"
Expect After Buffer="<class 'pexpect.exceptions.TIMEOUT'>"
Message="Getting login and sudo not successful, probably connection issue, retry"
2021-02-03 00:43:02,380:op-test::INFO:Exit with Result errors="1" and failures="0"
2021-02-03 00:43:02,380:op-test.common.OpTestUtil:cleanup:INFO:OpTestSystem Starting to Gather ESEL's
2021-02-03 00:43:02,381:op-test.common.OpTestUtil:dump_versions:INFO:Log Location: /var/lib/jenkins/workspace/op-test@2/test-reports/test-run-20210203004101/debug
2021-02-03 00:43:02,381:op-test.common.OpTestUtil:dump_versions:INFO:

I tried on two lpars, on the both the lpars I was able to install upstream kernel and boot, on one lp kernel panic occured due to which test failed. However it was a bug. From framework point of view it was handled appropriately.
@abdhaleegit request to give a try on lp1 or lp2 via jenkins. (make sure ip is changed in the config file)
@vijaykumarpuliyala : may I know the system details where it is failing so that, I can try it out on your system it self.

@harihare I shared machine  details on your slack. Please let me know if you need any other information.

As per discussion with Abdul and Vijay. The issue is not reproducible. Even for me it work fine on Power 8 Box.

Make sure the system is not in panic state before starting the test

Closing the issue. if you have any concerns or issues. Please feel free to reopen the issue with system details for debugging.


Feature: Add Leetcode Number Of islands Solution

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

Describe alternatives you've considered

Additional context

Hey!
I would like to implement my solution for this problem.
I will solve this using bfs and recursion.
This question can also be solved using dfs but the bfs solution of the same is easy to understand and implement.

@lakshita15  This issue is still open . Should I also try a pr of my solution to this problem ?


add verilator vcd command line option

I have created a pull-request for rocket that support passing VCD filename from command line

Also, I'm pretty sure rocket-chip doesn't use this file so the reference to Makefrag-verilator doesn't really make sense in this repo

Hi Jack,
Fair enough

Thanks for this suggestion though! When I finally move this out of Firrtl I'll be sure to include it!


Host messages should let you discover what is registered

We should add a message that dumps the list of registered callbacks.

@collinjackson Is this still worth doing?

If I remember correctly, we wanted this to allow wrappers around native host messages to detect when the native side hadn't been set up correctly and log an error. If a handler isn't registered, sendJSON will complete with null, and that can be distinguished from an empty JSON object, so it is possible to accomplish this goal with the current setup.
Is there a reason not to throw an error instead of completing with null? That would make for an informative log message if the error isn't caught, but maybe there are some use cases for sending messages to nonexistent handlers that I haven't thought of.

Sounds like fixing #5962 would be sufficient if we make non-existent handlers return errors.

Agree, I think we can close this one.


compare performance of source terms in 3D

I used the following code to set up benchmarks (adapted to the examples).
julia --threads=1 --check-bounds=no

Taam
julia> using BenchmarkTools, Revise, Cthulhu, Test; using Trixi

julia> Trixi.init_parameters("examples/3d/parameters_euler_mortar.toml")

julia> mesh, solver, time_parameters, time_integration_function = Trixi.init_simulation();

julia> Trixi.run_simulation(mesh, solver, time_parameters, time_integration_function)

julia> @benchmark Trixi.calc_sources!(
           $(solver),
           $(solver.source_terms),
           $(Trixi.parameter("t_end")))

Taal
julia> using BenchmarkTools, Revise, Cthulhu, Test; using Trixi

julia> trixi_include("examples/3d/elixir_euler_mortar.jl")

julia> @benchmark Trixi.calc_sources!(
           $(Trixi.wrap_array(copy(sol.u[end]), semi)),
           $(Trixi.wrap_array(copy(sol.u[end]), semi)),
           $(sol.t[end]),
           $(semi.source_terms),
           $(equations),
           $(solver),
           $(semi.cache))

examples/3d/elixir_euler_source_terms.jl
Taam
Section                             ncalls     time   %tot     avg     alloc   %tot      avg
--------------------------------------------------------------------------------------------
     source terms                     1.54k    116ms  18.3%  74.9μs   1.25MiB  4.55%     848B

BenchmarkTools.Trial:
  memory estimate:  848 bytes
  allocs estimate:  6
  --------------
  minimum time:     75.516 μs (0.00% GC)
  median time:      76.715 μs (0.00% GC)
  mean time:        80.521 μs (0.00% GC)
  maximum time:     280.836 μs (0.00% GC)
  --------------
  samples:          10000
  evals/sample:     1

Taal
Section                ncalls     time   %tot     avg     alloc   %tot      avg
-------------------------------------------------------------------------------
  source terms            951   79.6ms  21.9%  83.7μs    966KiB  7.91%  1.02KiB

BenchmarkTools.Trial:
  memory estimate:  928 bytes
  allocs estimate:  6
  --------------
  minimum time:     85.270 μs (0.00% GC)
  median time:      87.191 μs (0.00% GC)
  mean time:        89.418 μs (0.00% GC)
  maximum time:     202.735 μs (0.00% GC)
  --------------
  samples:          10000
  evals/sample:     1

examples/3d/elixir_euler_mortar.jl
Taam
Section                             ncalls     time   %tot     avg     alloc   %tot      avg
--------------------------------------------------------------------------------------------
    source terms                       620   89.7ms  16.9%   145μs    513KiB  3.42%     848B

BenchmarkTools.Trial:
  memory estimate:  848 bytes
  allocs estimate:  6
  --------------
  minimum time:     136.219 μs (0.00% GC)
  median time:      138.133 μs (0.00% GC)
  mean time:        144.758 μs (0.00% GC)
  maximum time:     370.309 μs (0.00% GC)
  --------------
  samples:          10000
  evals/sample:     1

Taal
Section                ncalls     time   %tot     avg     alloc   %tot      avg
-------------------------------------------------------------------------------
  source terms            636    105ms  20.2%   165μs    646KiB  5.40%  1.02KiB

BenchmarkTools.Trial:
  memory estimate:  928 bytes
  allocs estimate:  6
  --------------
  minimum time:     154.726 μs (0.00% GC)
  median time:      157.977 μs (0.00% GC)
  mean time:        161.632 μs (0.00% GC)
  maximum time:     318.420 μs (0.00% GC)
  --------------
  samples:          10000
  evals/sample:     1

examples/3d/elixir_hyp_diff_llf.jl
Taam
I used time_integration_scheme = timestep_carpenter_kennedy_erk54_2N!
with cfl = 0.4 since the optimized 3S* method isn't ported yet.
Section                             ncalls     time   %tot     avg     alloc   %tot      avg
--------------------------------------------------------------------------------------------
    source terms                     7.14k    7.37s  47.8%  1.03ms   5.77MiB  2.55%     848B

BenchmarkTools.Trial:
  memory estimate:  848 bytes
  allocs estimate:  6
  --------------
  minimum time:     983.161 μs (0.00% GC)
  median time:      993.635 μs (0.00% GC)
  mean time:        1.017 ms (0.00% GC)
  maximum time:     1.517 ms (0.00% GC)
  --------------
  samples:          4916
  evals/sample:     1

Taal
Section                ncalls     time   %tot     avg     alloc   %tot      avg
-------------------------------------------------------------------------------
  source terms          3.57k    3.72s  49.7%  1.04ms   3.76MiB  3.08%  1.08KiB

BenchmarkTools.Trial:
  memory estimate:  960 bytes
  allocs estimate:  6
  --------------
  minimum time:     968.202 μs (0.00% GC)
  median time:      981.306 μs (0.00% GC)
  mean time:        1.004 ms (0.00% GC)
  maximum time:     1.873 ms (0.00% GC)
  --------------
  samples:          4981
  evals/sample:     1

examples/3d/elixir_hyp_diff_nonperiodic.jl
Taam
I used time_integration_scheme = timestep_carpenter_kennedy_erk54_2N!
with cfl = 0.4 since the optimized 3S* method isn't ported yet.
Section                             ncalls     time   %tot     avg     alloc   %tot      avg
--------------------------------------------------------------------------------------------
    source terms                     4.48k    1.23s  41.8%   275μs   3.62MiB  4.28%     848B

BenchmarkTools.Trial:
  memory estimate:  848 bytes
  allocs estimate:  6
  --------------
  minimum time:     262.515 μs (0.00% GC)
  median time:      266.568 μs (0.00% GC)
  mean time:        273.177 μs (0.00% GC)
  maximum time:     498.764 μs (0.00% GC)
  --------------
  samples:          10000
  evals/sample:     1

Taal
Section                ncalls     time   %tot     avg     alloc   %tot      avg
-------------------------------------------------------------------------------
  source terms          4.48k    1.05s  39.0%   234μs   4.72MiB  4.97%  1.08KiB

BenchmarkTools.Trial:
  memory estimate:  960 bytes
  allocs estimate:  6
  --------------
  minimum time:     197.238 μs (0.00% GC)
  median time:      200.645 μs (0.00% GC)
  mean time:        208.289 μs (0.00% GC)
  maximum time:     442.517 μs (0.00% GC)
  --------------
  samples:          10000
  evals/sample:     1

examples/3d/elixir_eulergravity_eoc_test.jl
Here, I benchmarked the source term calculation of the Euler solver in more detail.
Taam
Section                                 ncalls     time   %tot     avg     alloc   %tot      avg
------------------------------------------------------------------------------------------------
    gravity solver                         110    8.99s  98.5%  81.8ms    670MiB  98.3%  6.09MiB
        source terms                     49.8k    547ms  5.99%  11.0μs   40.2MiB  5.91%     848B
    Euler solver                           110   39.8ms  0.44%   362μs   1.40MiB  0.21%  13.0KiB
      source terms                         110   9.13ms  0.10%  83.0μs   91.1KiB  0.01%     848B

julia> @benchmark Trixi.calc_sources!(
           $(solver[1]),
           $(solver[1].source_terms),
           $(Trixi.parameter("t_end")))
BenchmarkTools.Trial:
  memory estimate:  848 bytes
  allocs estimate:  6
  --------------
  minimum time:     80.742 μs (0.00% GC)
  median time:      82.682 μs (0.00% GC)
  mean time:        84.673 μs (0.00% GC)
  maximum time:     200.525 μs (0.00% GC)
  --------------
  samples:          10000
  evals/sample:     1

Taal
Section                  ncalls     time   %tot     avg     alloc   %tot      avg
---------------------------------------------------------------------------------
gravity solver              121    8.96s  97.9%  74.1ms    548MiB  97.5%  4.52MiB
    source terms          52.9k    511ms  5.59%  9.67μs   55.7MiB  9.92%  1.08KiB
Euler solver                121   43.6ms  0.48%   360μs   1.14MiB  0.20%  9.67KiB
    source terms            121   11.8ms  0.13%  97.5μs    123KiB  0.02%  1.02KiB

julia> @benchmark Trixi.calc_sources!(
           $(Trixi.wrap_array(copy(sol.u[end]), semi)),
           $(Trixi.wrap_array(copy(sol.u[end]), semi)),
           $(sol.t[end]),
           $(semi.semi_euler.source_terms),
           $(equations_euler),
           $(solver_euler),
           $(semi_euler.cache))
BenchmarkTools.Trial:
  memory estimate:  928 bytes
  allocs estimate:  6
  --------------
  minimum time:     84.501 μs (0.00% GC)
  median time:      86.401 μs (0.00% GC)
  mean time:        88.911 μs (0.00% GC)
  maximum time:     244.091 μs (0.00% GC)
  --------------
  samples:          10000
  evals/sample:     1

Conclusions
There can be a slight performance impact of using point-wise source terms in Taal vs. element-wise source terms in Taam.
However, this performance impact is often smaller than the impact of optimizing the code itself, e.g. by using
sinpi(...) instead of sin(pi * ...) or sincos(...) instead of sin(...), cos(...). Moreover, a performance
impact occurs mostly for the Euler equations, where it is not really important. In contrast, there is no negative
performance impact on the hyperbolic diffusion system, where the source terms are more important. Hence, I think it's
fine to keep point-wise source terms in Taal to get a clear separation of the solver and the equations.
Closes #208

Hence, I think it's fine to keep point-wise source terms in Taal to get a clear separation of the solver and the equations.

I agree (will do a review shortly). However, can you explain the increased memory footprint? By my account, most source terms should be completely allocation-free, unless there's type instability from the equations etc. Any ideas?

However, can you explain the increased memory footprint? By my account, most source terms should be completely allocation-free, unless there's type instability from the equations etc. Any ideas?

We're using threads in the for loops, which create closures. Their size depends on the arguments being used - that explains this difference. There are no allocations if I remove Threads.@threads in calc_sources!.

However, can you explain the increased memory footprint? By my account, most source terms should be completely allocation-free, unless there's type instability from the equations etc. Any ideas?

We're using threads in the for loops, which create closures. Their size depends on the arguments being used - that explains this difference. There are no allocations if I remove Threads.@threads in calc_sources!.

Ah, yes, we had this before. Say, is this something we should file an issue for with julialang? I guess they are probably aware of this, but it might help to show that there are real-world codes out there who suffer from it.

Say, is this something we should file an issue for with julialang? I guess they are probably aware of this, but it might help to show that there are real-world codes out there who suffer from it.

You could do that, but I'm not sure whether you will get positive reactions.

The failing test for examples/2d/elixir_mhd_rotor_shockcapturing_amr.jl seems to be the same kind of problem as in https://github.com/trixi-framework/Trixi.jl/pull/275#issuecomment-720352787.


Address Failing test-proxy-local-tool install

I went on vacation last wednesday, which is when the failure began.
This should address the failing build / livetest pipeline.
Next update of eng/common/testproxy/target_version.txt will also need to change how the package is installed under eng/common/testproxy/test-proxy-tool.yml. I will do that in the update that actually changes the target_version, this will keep everything in alignment and making sense.

/check-enforcer override


Implement changes from @mfiano

https://gist.github.com/mfiano/3ddf2810cf8101f66009c3fdde8b020b

The local swap functions are closing over state. Make them take the parent and left/right indices. To do this just return the left/right indices and wrap the callers in (setf parent-index ...).
You can lexibind some aref lookups that are called multiple times, particular the parent, left, and right priority.
In some various other places in the codebase, you can also lexibind the aref calls that are called more than once. I forget where though.

Also read-eval (ash 1 64) just to be sure it's a constant for implementations that don't do constant folding for whatever reason.

Also see the benchmark at https://github.com/jdz/simple-pairing-heap/blob/master/bench.org


Warnings from ruby 2.7

.../necromancer-0.5.0/lib/necromancer/conversion_target.rb:61: warning: The last argument is used as the keyword parameter
.../necromancer-0.5.0/lib/necromancer/null_converter.rb:8: warning: for `call' defined here

Released v0.5.1 with your patch.


Wires up cassandra test rule

@michaelsembwever the last commit is the important one. Too tired to figure out which tests are validly failing or not. you can always override the failing ones with @Ignore.
Feel free to use as little or as much of this code as you like.. you can copy/paste it in or whatever.
catch you tomorrow

thanks @adriancole
i'll merge this in, then delete the commits that already exist in upstream master, and then rebase the replace-cassie-with-datastax-cql-driver branch against upstream master.


Please check script ID and read permissions settings.

I have "You do not have access to library Cheerio, used by your script, or it has been deleted.", Please check script ID and read permissions settings.

Thank you for your report. Now I make it public at the following place. Please check it.
https://script.google.com/d/1ReeQ6WO8kKNxoaA_O0XEQ589cIrRvEBA9qcWpNqdOP17i47u6N9M5Xh0/edit?usp=sharing


Fix broken unit tests

For some reason, the UTs are broken in development. This PR fixes them in order to make the build run again.
I didn't focus on types. We can do it later.
Note: Please, remember that when you are importing types from a definition file, it should be included using .d

This PR fixes them in order to make the build run again.

The build runs just fine

The build runs just fine

CI does not pass.
https://travis-ci.org/github/gnosis/safe-react/builds/715476677?utm_source=github_status&utm_medium=notification

Travis automatic deployment:
https://pr1216--safereact.review.gnosisdev.com/app

Travis automatic deployment:
https://pr1216--safereact.review.gnosisdev.com/app

Travis automatic deployment:
https://pr1216--safereact.review.gnosisdev.com/app

@nicosampler it has nothing to do with tests

No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received

Travis automatic deployment:
https://pr1216--safereact.review.gnosisdev.com/app

Travis automatic deployment:
https://pr1216--safereact.review.gnosisdev.com/app

Travis automatic deployment:
https://pr1216--safereact.review.gnosisdev.com/app


App flashes when moving app window from external monitor to internal monitor

Steps to reproduce
I use an external monitor connected to my laptop.
When I move the window of the apps from the internal to external monitor and vice versa,
There is some sort of flashing/ flickering that occurs.
And in some situations, because of this, some things get reset and start from the beginning.
i.e. it loses its progress and starts from the beginning.
one example I can give is that the youtube shorts in the youtube app start playing from the beginning  when I move the window from one screen to another.
I don't know if this is due to nvidia optimus on laptops but thought I'd mention it just in case.
✔ Expected Behavior
The app should not flash/flicker when moving the  window from one monitor to another
❌ Actual Behavior
The app flashes/flickers when moving the window from one monitor to another.
Other Software
No response
Please specify the version of Windows Subsystem for Android
2208.40000.5.0

This is generally expected behavior. See https://developer.android.com/guide/topics/resources/runtime-changes for how to handle configuration changes such as DPI, screen size, etc. that may be associated with moving an app from one display to another.
The experience should be similar to an Android device connected to external monitor in freeform windowing mode. Let us know if that's not the case with some additional specifics on how to reproduce the problem.

@nieubank It's not just flashing that occurs, If you're playing a video for example, the video will start from the beginning if moved to the external screen and vice versa.
To reproduce, you can attach an external monitor to a laptop and play an mp4 video from the files app in wsa. While the video is playing, if you move the window to another screen, the video starts from the beginning all over again.
I'm not able to reopen this issue for some reason.

Unfortunately this is still expected behavior on apps that are not designed to handle configuration changes. To ensure resources are populated correctly and updated, Android will just restart the activity and this is entirely up to the app as to how they handle it. Older apps that aren't updated since Android 6 or so typically are the ones that have these problems. If you're the developer reference this documentation. Otherwise, you'll need to reach out to the developer.
https://developer.android.com/guide/topics/resources/runtime-changes


CRC/MD5/SHA1 incorrect when creating dats of .zip file contents 1.1.0-test_642

When running 1.1.0-test_642 from Appveyor, I found that creating an xml dat for the contents of a zipped (.zip) file produces bad CRC's/md5/sha1 unless the -CRC switch is used on its own (which then produces accurate CRC's).
Example:
Bad CRC's/md5/sha1 come out of this command when run against a folder with one zip file (two files in the zip):
sabretools --dfd "[path]\Visual Pinball [DX9] PinMame Tables [MODs, HACKs]" --output-type=xml
Good CRC's come out with the -CRC switch added
sabretools --dfd "[path]Visual Pinball [DX9] PinMame Tables [MODs, HACKs]" -crc --output-type=xml
The same bad CRC's/md5/sha1 come out if I manually add -md5 and/or -sha1 switches:
sabretools --dfd "[path]Visual Pinball [DX9] PinMame Tables [MODs, HACKs]" -crc -sha1 -md5 --output-type=xml
sabretools --dfd "[path]Visual Pinball [DX9] PinMame Tables [MODs, HACKs]" -crc -md5 --output-type=xml
sabretools --dfd "[path]Visual Pinball [DX9] PinMame Tables [MODs, HACKs]" -crc -sha1 --output-type=xml

If I unzip the target files OR convert the zip to 7zip and run
sabretools --dfd "[path]\Visual Pinball [DX9] PinMame Tables [MODs, HACKs]" --output-type=xml
it produces the correct CRC's/md5/sha1.
So the problem appears to ONLY be with running the md5/sha1 options on the contents of zipped (.zip) files.  Unzipped or 7-zipped files produce the correct CRC's/md5/sha1
Good CRC's/md5/sha1 from unzipped or 7-zipped files:
		<rom name="Junk Yard_VP9_2_2_DX9.vpt" size="22917120" crc="2d0871f9" md5="75387cae56f636f7c4c6e00cccbe6a2f" sha1="dc9e20db5b6e497169f9d0b2f0e459ae65feb998" />
		<rom name="screen_43.jpg" size="571725" crc="328047e5" md5="e11c1a6db3c8d7f938adaa5dacbe2dbd" sha1="63fa2c96cfd0e10e078e8c3b6492b4dad92b2a14" />

Bad CRC's/md5/sha1 from zipped file:
		<rom name="Junk Yard_VP9_2_2_DX9.vpt" size="22917120" crc="d8eec684" md5="8194432f49fd238723171380a46e3e1a" sha1="75c182859f23aec83d1f24bd581a4aa3a40eea7e" />
		<rom name="screen_43.jpg" size="571725" crc="1094a4e1" md5="5d9b4feef429382fc9ba653dca332279" sha1="9a0932c030f0a792a2320aaa506403c9ba011f55" />

I am getting the exact same problem.. I'm glad I'm not alone on this!
I'm using a build cloned from the sabretools github and built in a fresh install of VS2022.  I'm using the following commands to scan a root folder that contains a single-level folder structure  with zips inside each folder.  some of the zips do contain files and also a single nested folder with uncompressed content inside (no zips in zips, anything in the zips is uncompressed).
sabretools.exe --d2d --superdat --output-type=xml --threads=8 --no-automatic-date --name=PC98test PC98_TEST_DAT.dat D:\Downloads_NeoKobe_test
sabretools.exe dfd --output-type=xml --threads=8 --include-crc --include-md5 --include-sha1 --include-sha256 --name=PC98test --filename=PC98_TEST_DAT.dat "D:\Downloads\NeoKobe_test"
All contents get scanned and dat builds fine, loads into RomVault and displays content fine.  The scanned content is added as a tosort to rebuild from, and 99.95% of the hashes are incorrect.
I haven't gone as far as bstaghare's troubleshooting but I'd likely see the same results at this point.

This has been determined to be related directly to .NET 6 and how it handles reads. Please try the build for https://github.com/SabreTools/SabreTools/commit/48d15ff09ca5767179f8219f1f081fdd4594b6f0 and see if that works

Compiled SabreTools with build [48d15ff] with VS2022.
Scanned a multi-level nested folder structure which included zips that contained a single subfolder alongside files in the zip root. 22,751 files total, 7,980 zips and 385 folders.  CRC, MD5, SHA1, SHA256 included in scan.
Zero errors encountered during scan and dat build phase.  Loaded new dat into RomVault and rebuilt the entire structure to a new folder using the scanned folder as a source.  No errors encountered, all files accounted for.
I would say with confidence the fix worked!  Thank you.

Awesome, thanks for reporting and testing.


mysql errors are missing properties

Currently the errors within the mysql package are merely typed as the default Error (it does extend these so it's not inherently wrong); here.
However the mysql package adds a couple of properties for debugging/logging purposes. As of<EMAIL_ADDRESS>this probably became a bit bigger of a problem as they no longer allow unknown property checks.
Am willing to open a PR however I'm not completely certain how to go about adding this, was thinking of something along the lines of adding a custom error type:
declare type MySQLError = Error & {
    code: string,
    fatal: boolean,
    sql?: string,
    sqlMessage?: string,
}

Or since it's probably a class that extends it:
declare class MySQLError extends Error{
    code: string,
    fatal: boolean,
    sql?: string,
    sqlMessage?: string,
}

Extending the class is most likely the way to go.

Yeah, I think the Foo & Bar approach would work better if Error were a type, not a class itself.


Disable/Hide all icons

I realised now that the icons take up too much space. Is there some way to disable/hide all icons?

Nope.

So, hiding it individually it is.
POWERLEVEL9K_ANACONDA_LEFT_DELIMITER=""
POWERLEVEL9K_ANACONDA_RIGHT_DELIMITER=""
POWERLEVEL9K_TIME_ICON=""
POWERLEVEL9K_LOAD_ICON=""
POWERLEVEL9K_RAM_ICON=""
POWERLEVEL9K_HOME_ICON=""
POWERLEVEL9K_HOME_SUB_ICON=""
POWERLEVEL9K_FOLDER_ICON=""
POWERLEVEL9K_PYTHON_ICON=""

Yes, that's the only way.
There are also brutal approaches such as icons=() but it'll kill too much. All separators and even the trailing whitespace before cursor will be gone.
You also probably don't want to disable icons from segments that have no other content. For example, status and background_jobs can sometimes display nothing but an icon. If you disable the icon, it'll look very odd indeed.
tl;dr: What you do is the best you can do.


[Bug] Override name and value of series.map.data

Version
5.3.0
Link to Minimal Reproduction
No response
Steps to Reproduce
Example from USA Population Estimation
https://echarts.apache.org/examples/en/editor.html?c=map-usa
Current Behavior
I want to give my own values to the name and value property like shown below
const obj = {
name: feature.properties.STATE_NAME,
value: feature.properties.PERSONS
};
When i prepare an object like that i'm not able to see labels on the map
Expected Behavior
We would like to map name and value with any other attribute and value from the response. For ex, Labels like state name and value is visible on the map.
Environment
- OS:
- Browser:
- Framework:

Any additional comments?
I'm trying to fetch my response from the geoserver and passing its response to the series.map.data array like an object with name and value properties. Even though I'm sending the data correctly, my map is failing to display labels on the map and there's no error in the console as well.

If you are using extractly the same way as the demo, it should work the same as the demo. Otherwise, please provide a working demo.


add a reminder for ics files

Pull Request Test Coverage Report for Build 72

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.4%) to 81.429%

Totals

Change from base Build 71:
-0.4%

Covered Lines:
25

Relevant Lines:
25

💛  - Coveralls

Codecov Report

Merging #44 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #44   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines           25        25
=========================================
  Hits            25        25

Impacted Files
Coverage Δ

src/lib/utils.js
100.00% <ø> (ø)

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 c230e75...5c4afa6. Read the comment docs.


Projects page

Reference

[ ] Should house the Project Component
[ ] Should use #7

@diterra-code any way we could get a design for this before the hackathon?


Runtime APIs: MessageChannel

The MessageChannel API is available on node but not CF Workers. This is causing an issue during the deployment of sites using React 19 + Astro + Workers, see https://github.com/facebook/react/issues/31827 and https://github.com/withastro/astro/issues/12824. The usage of this API may be a bug for this use case (meaning the solution there may be to stop using MessageChannel), but workerd may want to support it anyway.
I made a repository with steps to reproduce the crash mentioned in those issues here: https://github.com/phase/test-astro-react19-cf-workers

Relabeling this as a feature request. The fact that we currently do not support MessageChannel is currently intentional as there aren't really any usable use cases for it in the runtime currently. It is something we can revisit but it likely won't be soon. To help with that, it would be helpful to have a better idea of how MessageChannel is being used in this particular case.


[question]How To Run BriteCharts Demo

Hi, I want to run the demo by using command:
"npm run demos:serve"
then browser has open a website <IP_ADDRESS>:8001 automatically (ERR_ADDRESS_INVALID ofcourse..
then I input localhost:8001, It shows Can not get /
so how to run this demo based on your source code (src) locally?
Thanks for you guys helping 🍡
enviroment:
Hardware: Surface Pro 4
System: Win10 16299
NodeJS version: 8.9.2
npm version: 5.5.1

Hi @Dieber, thanks for the question.
I understand you are following the Contributing guide, right? I guess you need to run yarn run docs before in order to see something there.
Let me know if that helped, it is really important to us that contributing becomes easier.

@Golodhros
Thanks for your help.
It's my fault, I didn't see the Contributing guide link before.


[UI]Horizontal Scrollbar Bug: Components Break and Display White Line When Scrolled Right

Current Behavior
When sliding the horizontal scrollbar to the right, certain components (e.g., labels inside pods/namespace) break and display a white vertical line across the page. This issue disrupts the visual integrity and functionality of the affected components.
Desired Behavior
Components should maintain their structure and functionality when the horizontal scrollbar is used. There should be no white vertical line or visual disturbances, ensuring a seamless user experience.
Screenshots/Logs

Environment

Browser: Chrome
Host OS:Linux Windows
Meshery Server Version: stable-v
Platform: Docker  @Kubernetes
@Ashparshp @leecalcote

I'd like to work on this if the issue is found valid.
Contributor Guides and Handbook

🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🖥 Contributing to Meshery UI
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

@subho30666 Hey, I want to work on this issue. Can you assign me this?

@subho30666 Hey, I want to work on this issue. Can you assign me this?

Hey, I can't assign the project to you as I'm not a maintainer. But if I get assigned, I'll request to include you as an assignee too. This way, we can complete it faster together.
@Ashparshp  @leecalcote @Jougan-0

@subho30666 Okay, thanks 👍

Hey @leecalcote @SAHU-01 @sudhanshutech , I have setup meshery locally,  have understood this issue and want to work in it. Can this issue be assigned to me?

Hey @leecalcote @SAHU-01 @sudhanshutech ,I have setup meshery locally,can you assign this issue to me

@sudhidutta7694, are you all good here / making progress?

Yes, @leecalcote I have started working on the issue.

@subho30666 🙌


Audio stops after 4 minutes and 30 seconds

Good evening,
I have recently switched to Scream from ich9 QEMU audio as it let's me have 5.1 audio. The problem I seem to be having is after 4 minutes and 30 seconds it stops and I have to restart the reciever. Scream doesn't report any errors in verbose mode, and it just stops. If I enable IGMP snooping I see that it drops the "<IP_ADDRESS> " after that time. Even when I set the IGMP timeout to be much longer on the switch(Zyxel GS1920-24) on the IGMP Snooping Status screen it still shows it but the audio still stops. I have also tried as recommended in another post to disable IGMP Snooping but this doesn't fix it.
I have tried using unicast by adding the registry keys as recommended but it seems that I am not smart enough to understand how to use it as I add the registery keys, add -u to the scream command and it doesn't work(Just doesn't detect the stream). Hope you boys have some advice.

Just wanted to say right now I have it working by having a systemd user service restart after 180 seconds but this is obviosly not ideal.

Update, didn't get multicast working.. but I did find out why unicast didn't work... port 4011 wasn't allowed through the firewall.


fix garbled output on node v6

Fixes: https://github.com/nodesecurity/nsp/issues/100

Thanks for the quick find! Doing some quick testing with the various versions.

Tested fix in the latest in 6, 5, 0.12, 0.10 versions. LGTM,


Getting import error

Getting import error ImportError: No module named queue while running using venv.

Try to run with docker help.

@elukey You can resolve this as this problem was related to python version..my python version was 2.7, I have upgraded it to 3.6.


Action stopped working

Currently it throws HTTPError: Response code 422 (Unprocessable Entity)

Thanks for reporting the issue @vcoolish !
I haven't used Shortcut for a while and don't have an account any more, do you have a test repo where we can reproduce this?

There's no information in the API docs on that error :/

@vcoolish do you have any further information / a reproduction on this?