smop command not found even after installation

Hi victorlei,
I successfully downloaded and installed (or so I thought) smop, but I am encountering the following issues whenever I try to use it:
Any smop etc. command yields
-bash: smop: command not found
while attempting
python main.py file.m
from within smop/smop/ yields
Traceback (most recent call last):   File "main.py", line 15, in <module>     from . import options ValueError: Attempted relative import in non-package
Trying
python3 main.py file.m
gives
Traceback (most recent call last):   File "main.py", line 15, in <module>     from . import options ImportError: cannot import name 'options' from '__main__' (main.py)
Any ideas?
Thanks in advance!

SAME Q


Unable to claim direct debit #3035

https://github.com/bitshares/bitshares-ui/issues/3035
Please investigate and confirm this problem, and if reproducable, fix it :)

@sschiessl-bcp

1.there is some warning says "Limit > payer balance!" when Payer balance is okay

This issue is not reproducible for me

2.trying to type anything in memo closes the modal.

FeeAssetSelector implementation merging  should fix this problem


App crashing after ota by amplitude library

App Crashing while reloading after an OTA update and throws this error - NativeArgumentsParseException
AmplitudeReactNative.getApplicationContext got 3 arguments, expected 2

Hi @Harsh-Pratap-Singh1 thanks for using Amplitude.
We will look into the issue. Can you please provide the version of the SDK giving you the error? Thanks

@justin-fiedler I'm seeing this on version 1.3.0
"<EMAIL_ADDRESS>  version "1.3.0"
  resolved<EMAIL_ADDRESS>  integrity sha512-48qaiihLpvoo06bAOHyCLyXBk/mMlTonzZEyAO9EEFCXxI6q7jpjL6+wavlwCrVhjrt07W55kqgWoUn8MxXxpw==
  dependencies:
    "@amplitude/analytics-client-common" "^1.1.0"
    "@amplitude/analytics-core" "^1.2.0"
    "@amplitude/analytics-types" "^1.3.0"
    "@amplitude/ua-parser-js" "^0.7.31"
    "@react-native-async-storage/async-storage" "^1.17.11"
    tslib "^2.4.1"

Thanks @natphysnahagey. A couple more questions for you.

What OS is this happening on (Android, iOS, both?)
Can you provide some details on how the OTA update process works in your application.

If this error is only happening in iOS, could you please make sure the latest native code is installed.
cd ios
pod install

Hi @natphysnahagey based on the Expo documentation OTA updates do not support native code changes. We changed both JS and native code in<EMAIL_ADDRESS>Setting "runtimeVersion" should help - Avoiding crashes with incompatible updates


Xiomi Ble thermo and humidity meter doesn't work in HA

Hi!
Sorry for interrupting and bad english.
A few weeks ago my mentioned thermometers suddenly stop working in HA (not because an update), but stil working in Xiaomi home.
All of zigbee devices still working, only Ble devices gone.
The exact type on picture:

Do you use supported gateway firmware?

I think yes, because it worked for months.

Sorry, my fault.
There was an automatic update for 1.5.4_0090......
(But it happened months after the faults.)

Well. 1.5.4 doesn't supported yet


Can't install with setuptools >= 52

ImportError: cannot import name 'main' from 'setuptools.command.easy_install'

This seems like a bug elsewhere in your system. We never mention easy_install at all. Or setuptools for that matter.

I hit another problem and through that found out that it is caused by using zc.buildout together with the changes in recent setuptools releases. Sorry for the false alarm.


Fixes a couple of meme-based compliments

Changes Power level 9000! to Power level? It's over 9000! as suggested by @raisedadead.
Changes Head to the chopper! to Get to the choppa!. Reference

closes #6155

:100:


python311Packages.publicsuffixlist: <IP_ADDRESS>30429 -> <IP_ADDRESS>30506

Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 230332 run on x86_64-linux 1

3 packages built:

python310Packages.publicsuffixlist
python311Packages.publicsuffixlist
trustymail


Guide on how to post news item for training stakeholders

As discussed, draft guide of steps and screenshots of how to post news items on Drought site. Outcome will be to use in training stakeholders and as future reference for them.

[ ] Draft steps with screenshots in Google Docs
[ ] Have @chachasikes check for accuracy
[ ] Get approval/edits from @jaredwyee
[ ] Share with stakeholders when training

Draft: https://docs.google.com/document/d/1SXHOx0npr6FwUXG12ubmLff04kVmTPp7WckT8V_wOw8/edit#

Thanks @thepegisin Looks great. Just going to hold for a bit on scheduling the initial training session to make sure we don't throw too much at stakeholders at once.

Guide is done. Doing initial training session today.

While we have some rockiness with receiving emails for invites and OTP, stakeholder was able to setup 2fa via authenticator app and has first new posted up successfully.

Made into slides and shared with trainees. https://docs.google.com/presentation/d/1_v2Yi2O07bu2ay_8tzaL1TS1R0VDR6fW8lIQ-DWTd1Y/edit#slide=id.gd01156d741_1_3


Release 0.37.1

Update version 0.37.1
For contributor use:

[x] Targeted PR against master branch
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work
[x] Code follows the standards mentioned here
[x] Updated relevant documentation
[x] Re-reviewed Files changed in the Github PR explorer
[x] Added appropriate labels

Codecov Report

Merging #548 (ada8ac6) into master (4fbbc12) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #548   +/-   ##
=======================================
  Coverage   54.87%   54.87%
=======================================
  Files          37       37
  Lines        2030     2030
=======================================
  Hits         1114     1114
  Misses        771      771
  Partials      145      145

Flag
Coverage Δ

unittests
54.87% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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 4fbbc12...ada8ac6. Read the comment docs.


Performance

Work in improving performance 'under the hood'

Codecov Report

Merging #60 (e2d36a5) into master (3180c0e) will decrease coverage by 0.07%.
The diff coverage is 94.53%.

@@            Coverage Diff             @@
##           master      #60      +/-   ##
==========================================
- Coverage   81.67%   81.59%   -0.08%
==========================================
  Files          25       24       -1
  Lines        1413     1326      -87
==========================================
- Hits         1154     1082      -72
+ Misses        259      244      -15

Impacted Files
Coverage Δ

src/Term.jl
66.66% <ø> (ø)

src/_errors.jl
0.00% <0.00%> (ø)

src/errors.jl
2.53% <0.00%> (ø)

src/logo.jl
100.00% <ø> (ø)

src/progress.jl
92.50% <66.66%> (ø)

src/renderables.jl
87.50% <78.94%> (-1.79%)
:arrow_down:

src/segment.jl
75.00% <85.71%> (-6.49%)
:arrow_down:

src/__text_utils.jl
92.30% <92.19%> (+2.45%)
:arrow_up:

src/color.jl
97.91% <96.42%> (+1.14%)
:arrow_up:

src/panel.jl
96.15% <98.41%> (-1.35%)
:arrow_down:

... and 20 more

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 3180c0e...e2d36a5. Read the comment docs.


Support LSP encoding negotiation

In version 3.17, LSP introduced the ability for clients and servers to negotiate which encoding they'd like to use for source positions. In previous versions of LSP, source positions were always expressed in terms of variable-width 16-bit Unicode, which many clients have not properly implemented.
These changes allow Lean to negotiate which position style should be used. In the short term, this is a workaround for a long-standing lsp-mode issue that has bitten a number of Lean Emacs users - given the repeated offers of support in that issue's thread that were ignored by the maintainer, I figured it'd be faster to just fix it here. In the long term, this will also make it easier for others to build innovative tools on top of Lean, as it removes one of the trickiest parts of LSP to get right. Lean code is more likely to be affected by 16-bit Unicode problems than other languages, due to the heavy idiomatic use of high-range Unicode for mathematics.
This is the first time I've had to work around bootstrapping issues, so this includes an updated stage0. In case I did something silly with it, I haven't squashed any of my "wip" commits - that should definitely be done prior to merging! You'll also notice lots of bogus little commits, so please ignore the commit history's structure. I'll squash once I get the go-ahead.
I also updated the LSP tests to take Unicode into account, and added the ability to run them with a variety of position encodings using a configuration line at the top.
Summary of changes:

Added module Lean.Data.Lsp.PositionEncodingKind - it's its own module because it ends up being used in a few places, and this avoids tricky import cycles.
Renamed module Lean.Data.Lsp.Utf16 to Lean.Data.Lsp.PositionEncoding and added functions that work with 8- and 32-bit Unicode.
Added versions of Lean.Data.Lsp.Position and Lean.Data.Lsp.Range that contain all three supported encodings of column positions, allowing them to be generated when the text is present and avoiding a tricky global invariant (the code already did LSP UTF-16 conversions for the same reason).
Added Unicode support to the LSP testing infrastructure, including the ability to select an encoding (see tests/lean/interactive/run.lean and tests/lean/interactive/fancyUnicode.lean).

Everything seems to work well in Emacs now, which it didn't before, and in VS Code.

It looks like I'll have to update Std to keep compatibility here. What's the way to prepare a PR to it that the Mathlib compatibility check will take into account?

!bench

It looks like I'll have to update Std to keep compatibility here. What's the way to prepare a PR to it that the Mathlib compatibility check will take into account?

Apologies, @david-christiansen, that I never answered this. I'm finally getting to the end of the backlog of breaks-mathlib labels. :-)
Things you need to know to defeat the dreaded breaks-mathlib label:

You need to rebase your PR onto origin-nightly. (Just once, it doesn't matter that nightly will move on, although you can keep rebasing if otherwise needed.)
This will automatically create a lean-pr-testing-NNNN branch at Mathlib, on which adaptations can be made (or, realistically, you can ask me to make adaptations on!)
If it also causes breakages in Std, we need to manually create a lean-pr-testing-NNNN branch at Std, based off the nightly-testing-YYYY-MM-DD branch of Std for whichever date script/most-recent-nightly-tag.sh reports in your Lean PR. (This step is rarer, so not as automated yet.) You then need to change the lakefile.lean in the Mathlib lean-pr-testing-NNNN branch to point to the lean-pr-testing-NNNN branch of Std, and run lake update std.

There is further documentation at https://leanprover-community.github.io/contribute/tags_and_branches.html, although it is more descriptive of the setup rather than instructional.
As this PR is currently broken in Lean CI, I'm just going to remove the breaks-mathlib label. Please feel free to ping me if/when you want Mathlib CI to resume, of the instructions above are insufficient.


Enable LoRA support for HPU

This PR enables LoRA support in HPU.

Implemented custom BGMV for LoRA modules using index-select operator.
Support for both single and multi card scenarios has been tested

I ran some multi-LoRA tests on this branch and wanted to share a few additional issues that I encountered, hoping it might help.
[1] In tests/lora/test_llama_hpu.py, setting VLLM_SKIP_WARMUP=false seems to cause an error when running on multi-card setups. It would be appreciated if you could verify this. My SynapseAI SDK version is 1.16, so the issue might be related to running with multiple cards.

Error message w/ 'VLLM_SKIP_WARMUP=false pytest tests/lora/test_llama_hpu.py'

============================= HABANA PT BRIDGE CONFIGURATION ===========================
PT_HPU_LAZY_MODE = 1
PT_RECIPE_CACHE_PATH =
PT_CACHE_FOLDER_DELETE = 0
PT_HPU_RECIPE_CACHE_CONFIG =
PT_HPU_MAX_COMPOUND_OP_SIZE =<PHONE_NUMBER>854775807
PT_HPU_LAZY_ACC_PAR_MODE = 1
PT_HPU_ENABLE_REFINE_DYNAMIC_SHAPES = 0
---------------------------: System Configuration :---------------------------
Num CPU Cores : 160
CPU RAM       :<PHONE_NUMBER> KB
(RayWorkerWrapper pid=1491762) ============================= HABANA PT BRIDGE CONFIGURATION ===========================
(RayWorkerWrapper pid=1491762)  PT_HPU_LAZY_MODE = 1
(RayWorkerWrapper pid=1491762)  PT_RECIPE_CACHE_PATH =
(RayWorkerWrapper pid=1491762)  PT_CACHE_FOLDER_DELETE = 0
(RayWorkerWrapper pid=1491762)  PT_HPU_RECIPE_CACHE_CONFIG =
(RayWorkerWrapper pid=1491762)  PT_HPU_MAX_COMPOUND_OP_SIZE =<PHONE_NUMBER>854775807
(RayWorkerWrapper pid=1491762)  PT_HPU_LAZY_ACC_PAR_MODE = 1
(RayWorkerWrapper pid=1491762)  PT_HPU_ENABLE_REFINE_DYNAMIC_SHAPES = 0
(RayWorkerWrapper pid=1491762) ---------------------------: System Configuration :---------------------------
(RayWorkerWrapper pid=1491762) Num CPU Cores : 160
(RayWorkerWrapper pid=1491762) CPU RAM       :<PHONE_NUMBER> KB
(RayWorkerWrapper pid=1491762) ------------------------------------------------------------------------------
Loading safetensors checkpoint shards:   0% Completed | 0/2 [00:00<?, ?it/s]
Loading safetensors checkpoint shards:  50% Completed | 1/2 [00:00<00:00,  2.73it/s]
Loading safetensors checkpoint shards: 100% Completed | 2/2 [00:00<00:00,  2.12it/s]
Loading safetensors checkpoint shards: 100% Completed | 2/2 [00:00<00:00,  2.20it/s]
Process Process-3:
Traceback (most recent call last):
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/multiprocessing/process.py", line 314, in _bootstrap
self.run()
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/multiprocessing/process.py", line 108, in run
self._target(*self._args, **self._kwargs)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/tests/lora/test_llama_hpu.py", line 40, in _test_llama_lora
llm = vllm.LLM(MODEL_PATH,
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/entrypoints/llm.py", line 155, in init
self.llm_engine = LLMEngine.from_engine_args(
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/engine/llm_engine.py", line 455, in from_engine_args
engine = cls(
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/engine/llm_engine.py", line 265, in init
self._initialize_kv_caches()
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/engine/llm_engine.py", line 377, in _initialize_kv_caches
self.model_executor.initialize_cache(num_gpu_blocks, num_cpu_blocks)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/executor/distributed_gpu_executor.py", line 62, in initialize_cache
self._run_workers("initialize_cache",
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/executor/ray_habana_executor.py", line 321, in _run_workers
self.driver_worker.execute_method(method, *driver_args,
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/worker/worker_base.py", line 383, in execute_method
raise e
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/worker/worker_base.py", line 374, in execute_method
return executor(*args, **kwargs)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/worker/habana_worker.py", line 190, in initialize_cache
self._warm_up_model()
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/worker/habana_worker.py", line 208, in _warm_up_model
self.model_runner.warmup_model(self.hpu_cache[0])
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
return func(*args, **kwargs)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/worker/habana_model_runner.py", line 1268, in warmup_model
self.warmup_graphs(
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/worker/habana_model_runner.py", line 1213, in warmup_graphs
self.warmup_scenario(batch_size, seq_len, is_prompt, kv_caches)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/worker/habana_model_runner.py", line 1126, in warmup_scenario
self.execute_model(inputs, kv_caches)
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
return func(*args, **kwargs)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/worker/habana_model_runner.py", line 1521, in execute_model
hidden_states = self.model.forward(
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/site-packages/habana_frameworks/torch/hpu/graphs.py", line 716, in forward
return wrapped_hpugraph_forward(
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/site-packages/habana_frameworks/torch/hpu/graphs.py", line 594, in wrapped_hpugraph_forward
outputs = orig_fwd(*args, **kwargs)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/worker/habana_model_runner.py", line 193, in forward
hidden_states = self.model(*args, **kwargs)
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1514, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1523, in _call_impl
return forward_call(*args, **kwargs)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/model_executor/models/llama.py", line 423, in forward
model_output = self.model(input_ids, positions, kv_caches,
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1514, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1564, in _call_impl
result = forward_call(*args, **kwargs)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/model_executor/models/llama.py", line 313, in forward
hidden_states = self.get_input_embeddings(input_ids)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/model_executor/models/llama.py", line 298, in get_input_embeddings
return self.embed_tokens(input_ids)
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1514, in _wrapped_call_impl
return self.call_impl(*args, **kwargs)
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1564, in call_impl
result = forward_call(*args, **kwargs)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/lora/layers.py", line 387, in forward
full_output = self.base_layer.forward(
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/model_executor/layers/vocab_parallel_embedding.py", line 365, in forward
output = tensor_model_parallel_all_reduce(output_parallel)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/distributed/communication_op.py", line 11, in tensor_model_parallel_all_reduce
return get_tp_group().all_reduce(input)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/distributed/parallel_state.py", line 317, in all_reduce
return hpu_comm.all_reduce(input)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/distributed/device_communicators/hpu_communicator.py", line 26, in all_reduce
dist.all_reduce(x, group=self.group)
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/site-packages/torch/distributed/c10d_logger.py", line 72, in wrapper
return func(*args, **kwargs)
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/site-packages/torch/distributed/distributed_c10d.py", line 1993, in all_reduce
work = group.allreduce([tensor], opts)
RuntimeError: collective nonSFG is not supported during hpu graph capturing
2024-08-12 07:56:46,050 ERROR worker.py:409 -- Unhandled error (suppress with 'RAY_IGNORE_UNHANDLED_ERRORS=1'): ray::RayWorkerWrapper.execute_method() (pid=1491762, ip=<IP_ADDRESS>, actor_id=71fbdd983c7fa33407b5196001000000, repr=<vllm.executor.ray_utils.RayWorkerWrapper object at 0x7f8bb5d21810>)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/worker/worker_base.py", line 383, in execute_method
raise e
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/worker/worker_base.py", line 374, in execute_method
return executor(*args, **kwargs)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/worker/habana_worker.py", line 190, in initialize_cache
self._warm_up_model()
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/worker/habana_worker.py", line 208, in _warm_up_model
self.model_runner.warmup_model(self.hpu_cache[0])
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
return func(*args, **kwargs)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/worker/habana_model_runner.py", line 1268, in warmup_model
self.warmup_graphs(
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/worker/habana_model_runner.py", line 1213, in warmup_graphs
self.warmup_scenario(batch_size, seq_len, is_prompt, kv_caches)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/worker/habana_model_runner.py", line 1126, in warmup_scenario
self.execute_model(inputs, kv_caches)
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
return func(*args, **kwargs)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/worker/habana_model_runner.py", line 1521, in execute_model
hidden_states = self.model.forward(
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/site-packages/habana_frameworks/torch/hpu/graphs.py", line 716, in forward
return wrapped_hpugraph_forward(
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/site-packages/habana_frameworks/torch/hpu/graphs.py", line 594, in wrapped_hpugraph_forward
outputs = orig_fwd(*args, **kwargs)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/worker/habana_model_runner.py", line 193, in forward
hidden_states = self.model(*args, **kwargs)
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1514, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1523, in _call_impl
return forward_call(*args, **kwargs)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/model_executor/models/llama.py", line 423, in forward
model_output = self.model(input_ids, positions, kv_caches,
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1514, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1564, in _call_impl
result = forward_call(*args, **kwargs)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/model_executor/models/llama.py", line 313, in forward
hidden_states = self.get_input_embeddings(input_ids)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/model_executor/models/llama.py", line 298, in get_input_embeddings
return self.embed_tokens(input_ids)
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1514, in _wrapped_call_impl
return self.call_impl(*args, **kwargs)
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1564, in call_impl
result = forward_call(*args, **kwargs)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/lora/layers.py", line 387, in forward
full_output = self.base_layer.forward(
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/model_executor/layers/vocab_parallel_embedding.py", line 365, in forward
output = tensor_model_parallel_all_reduce(output_parallel)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/distributed/communication_op.py", line 11, in tensor_model_parallel_all_reduce
return get_tp_group().all_reduce(input)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/distributed/parallel_state.py", line 317, in all_reduce
return hpu_comm.all_reduce(input)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/distributed/device_communicators/hpu_communicator.py", line 26, in all_reduce
dist.all_reduce(x, group=self.group)
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/site-packages/torch/distributed/c10d_logger.py", line 72, in wrapper
return func(*args, **kwargs)
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/site-packages/torch/distributed/distributed_c10d.py", line 1993, in all_reduce
work = group.allreduce([tensor], opts)
RuntimeError: collective nonSFG is not supported during hpu graph capturing
/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/multiprocessing/resource_tracker.py:224: UserWarning: resource_tracker: There appear to be 1 leaked shared_memory objects to clean up at shutdown
warnings.warn('resource_tracker: There appear to be %d '

[2] In tests/lora/test_multilora_hpu.py, it seems that not setting the prompt_logprobs=1 option in the sampling params avoids a dimension error. However, even with this workaround, I still encounter the same error as in [1] when using 2x or 4x multi-card setups. Additionally, in the 1x setup, 1 out of 6 prompts does not match between generated_texts and expected_output.

Error message w/ 'VLLM_SKIP_WARMUP=false pytest tests/lora/test_multilora_hpu.py'

-------------------------------------------------------- Captured stderr call --------------------------------------------------------
============================= HABANA PT BRIDGE CONFIGURATION ===========================
PT_HPU_LAZY_MODE = 1
PT_RECIPE_CACHE_PATH =
PT_CACHE_FOLDER_DELETE = 0
PT_HPU_RECIPE_CACHE_CONFIG =
PT_HPU_MAX_COMPOUND_OP_SIZE =<PHONE_NUMBER>854775807
PT_HPU_LAZY_ACC_PAR_MODE = 1
PT_HPU_ENABLE_REFINE_DYNAMIC_SHAPES = 0
---------------------------: System Configuration :---------------------------
Num CPU Cores : 160
CPU RAM       :<PHONE_NUMBER> KB
Loading safetensors checkpoint shards:   0% Completed | 0/2 [00:00<?, ?it/s]
Loading safetensors checkpoint shards:  50% Completed | 1/2 [00:00<00:00,  1.34it/s]
Loading safetensors checkpoint shards: 100% Completed | 2/2 [00:02<00:00,  1.28s/it]
Loading safetensors checkpoint shards: 100% Completed | 2/2 [00:02<00:00,  1.20s/it]
Process Process-1:
Traceback (most recent call last):
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/multiprocessing/process.py", line 314, in _bootstrap
self.run()
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/multiprocessing/process.py", line 108, in run
self._target(*self._args, **self._kwargs)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/tests/lora/test_multilora_hpu.py", line 111, in _test_llama_multilora
results = process_requests(engine, test_prompts)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/tests/lora/test_multilora_hpu.py", line 79, in process_requests
request_outputs: List[RequestOutput] = engine.step()
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/engine/llm_engine.py", line 925, in step
output = self.model_executor.execute_model(
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/executor/habana_executor.py", line 150, in execute_model
output = self.driver_worker.execute_model(execute_model_req)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/worker/worker_base.py", line 272, in execute_model
output = self.model_runner.execute_model(
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
return func(*args, **kwargs)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/worker/habana_model_runner.py", line 1534, in execute_model
logits = self.model.compute_logits(hidden_states,
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/worker/habana_model_runner.py", line 205, in compute_logits
return self.model.compute_logits(*args, **kwargs)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/model_executor/models/llama.py", line 430, in compute_logits
logits = self.logits_processor(self.lm_head, hidden_states,
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1514, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/home/sdp/miniconda3/envs/vllm-fork/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1564, in _call_impl
result = forward_call(*args, **kwargs)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/lora/layers.py", line 1311, in forward
return type(self.base_layer).forward(self, *args, **kwargs)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/model_executor/layers/logits_processor.py", line 61, in forward
logits = self._get_logits(hidden_states, lm_head, embedding_bias)
File "/home/sdp/works/jongho/HabanaAI/vllm-fork/vllm/lora/layers.py", line 1293, in _get_logits
logits[:,
RuntimeError: The expanded size of the tensor (59) must match the existing size (128) at non-singleton dimension 0.  Target sizes: [59, 256].  Tensor sizes: [128, 256]

I ran some multi-LoRA tests on this branch and wanted to share a few additional issues that I encountered, hoping it might help.
[1] In tests/lora/test_llama_hpu.py, setting VLLM_SKIP_WARMUP=false seems to cause an error when running on multi-card setups. It would be appreciated if you could verify this. My SynapseAI SDK version is 1.16, so the issue might be related to running with multiple cards.
Error message w/ 'VLLM_SKIP_WARMUP=false pytest tests/lora/test_llama_hpu.py'
[2] In tests/lora/test_multilora_hpu.py, it seems that not setting the prompt_logprobs=1 option in the sampling params avoids a dimension error. However, even with this workaround, I still encounter the same error as in [1] when using 2x or 4x multi-card setups. Additionally, in the 1x setup, 1 out of 6 prompts does not match between generated_texts and expected_output.
Error message w/ 'VLLM_SKIP_WARMUP=false pytest tests/lora/test_multilora_hpu.py'

Thank you @JHLEE17 for identifying the issues. We had also identified the same issues internally, and are currently working on a fix.

@afierka-intel @madamczykhabana please help review this PR.

@JHLEE17 PR is merged to habana_main. 1x, 2x, 4x tests in tests/lora/test_llama_hpu.py and tests/lora/test_multilora_hpu.py are all passing with following caveats,

PT_HPU_ENABLE_LAZY_COLLECTIVES: required to be true for tensor parallel inference with HPU Graphs (as described in vllm-fork/README_GAUDI.md)
Tests are running with float32 precision where outputs from 1x, 2x, 4x can all use same reference output. For bfloat16 precision there are small differences between 1x and (2x, 4x) outputs, this happens without LoRA also, we are checking if this is something which can be fixed.
Current implementation of BGMV operator is not fully optimized and is impacting overall performance with LoRA, we are working on optimizing this operator further.


Dialog resize and drag combination

Describe the bug
When creating a Dialog with DialogOptions.Resizable = true and DialogOptions.Draggable = true, the resize of the dialog first behaves as if DialogOptions.Draggable is false. After moving the dialog once, it is resized differently.
To Reproduce
Check the dialog page demo: https://blazor.radzen.com/dialog
Click the Button "Order 10248 details" and resize the dialog, it will resize as it is fixed on the center of the screen.
Move the dialog a bit, try resizing again.
Expected behavior
When DialogOptions.Draggable is true, the resize behavior should not be around the center of the screen.
Desktop (please complete the following information):

OS: Windows 10
Browser: Edge

This will be the behavior if there is no Left and Top specified. If you specify them the initial resize will be exactly the same as after drag:


Servicebus processor Client start/stop, any better way than this ?

Query/Question
Servicebus processor start/stop any better way than this ?
Why is this not a Bug or a feature Request?
From a springboot application, I am able to connect to Servicebus and process the messages but for this I am starting the processor client on PostConstruct and stopping it on PreDestroy. Is there any better way than this ? your help and suggestion is much appreciated.
I am using the following spring dependency and with the following application properties and java code.
		<dependency>
			<groupId>com.azure.spring</groupId>
			<artifactId>spring-cloud-azure-starter-servicebus</artifactId>
			<version>4.3.0</version>
		</dependency>

Spring
spring:
  cloud:
    azure:
      servicebus:
        enabled: true
        processor:
          entity-type: QUEUE
          entity-name: <entity-name>
          connection-string: <connection-string>
          auto-complete: false
          session-enabled: true

@Slf4j
@Service
@RequiredArgsConstructor
public class AsbMessageProcessor {

    private final ServiceBusProcessorClient processorClient;

    @PostConstruct
    public void startProcessor(){
        log.info("Processor starting");
        processorClient.start();
        log.info("Processor started");
    }

    @PreDestroy
    public void stopProcessor(){
        log.info("Processor closing");
        processorClient.close();
        log.info("Processor closed");
    }
}

@Service
@Slf4j
public class AsbQueueConfiguration {

    @Bean
    public ServiceBusRecordMessageListener messageProcessor() {
        log.info("message processor initiated");
        return messageContext -> {
            try {
                ServiceBusReceivedMessage message = messageContext.getMessage();

                log.debug("Processing message. Message # : {}, Sequence #: {}, Content : {}", message.getMessageId(), message.getSequenceNumber(), message.getBody());

                messageContext.complete(); // acknowledge message

            } catch (Exception ex) {
                log.error("exception while processing message ", ex);
                messageContext.abandon(); // // re delivered
            }
        };
    }

    @Bean
    public ServiceBusErrorHandler errorProcessor() {
        log.info("error handler initiated");
        return context -> {
            log.error("Error when receiving messages from namespace: '%s'. Entity: '%s'%n",
                    context.getFullyQualifiedNamespace(), context.getEntityPath());

            if (context.getException() instanceof ServiceBusException) {
                ServiceBusException exception = (ServiceBusException) context.getException();
                log.error("Error source: %s, reason %s%n", context.getErrorSource(),
                        exception.getReason());
            } else {
                log.error("Error occurred: %s%n", context.getException());
            }
        };
    }

}

Hi @jay-annapureddy though there are various solutions to add callback on Spring's bean level or context level, like using DisposableBean/InitializingBean, some context listener, @PostConstruct/@PreDestroy and so on. While for your request of binding the lifecycle of Service Bus processor client with Spring context, from my perspective, those solutions almost have similar effects and cost from the aspect of how you need to custom the code. Unless you have some specific requirement on the concrete lifecycle about when should these operations be triggered, you can choose one on your need.

Hello @yiliuTo , the question of my collegue is in fact: in a spring boot application, it is the recommended way to start the processor manually, and let him run  in the background by calling ServiceBusProcessorClient.start ? We were expecting to have this autoconfigured somehow...  That you would only define the listeners, without having to deal with starting & stopping the processor manually.

Hi @jbkervyn

That you would only define the listeners, without having to deal with starting & stopping the processor manually.

To meet this requirement, your solution of using @PostConstruct and @PreDestroy is a common and convenient way to achieve that, which just hands over the management of your listener to Spring context in the background.

Hello @yiliuTo , thanks a lot for your feedback ! This answers our question !

Hi @jbkervyn after the internal discussion, I would like to update our previous suggestion on the way to manually start/close the processor bean. The previous mentioned way of using @PostConstruct can work actually, however there are some other limits on it: The phase when @PostConstruct takes effect is after that specific bean is being initialized, but not to say that all of the other beans have been initialized as well. So at that time the application is not in a state of ready to run. And we think a more professional way is to start the Service Bus processor when the application is ready that all the necessary Spring components have been prepared and are ready to use.
Therefore, we recommand you to use the SmartLifecycle interface , which just like its name indicated, it binds the component's lifecyle with Spring application context intelligently. It starts the required component when the application is being refreshed which is after all the beans get loaded and initialized, which we think is much safer.
And we prepare to enable this feature in the pr #30457, after it being released, you can remove your own customization to start/stop the processor manually, since our library will handle its lifecycle automatically.

hi @yiliuTo
That's great! Any idea in which version of spring-cloud-azure it will end up in?

Hi @jbkervyn , we currently target to release it in the version of 4.4.0, and will notice you once it gets released or there are any other changes.


Add pypy to CI test matrix

Codecov Report

Merging #89 (f1f2251) into master (c5cfe11) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #89   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            3         3
  Lines          487       487
  Branches        94        94
=========================================
  Hits           487       487

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 c5cfe11...f1f2251. Read the comment docs.

 I didn't know I needed this but I do.
Also thanks for all the effort on making Python ecosystem TOML v1 friendly


Unable to duplicate scripts on one store "Failed to duplicate the script" error message

Problem
Unable to duplicate scripts on store, getting "Failed to duplicate the script" error message. Showing 422 error in Console
Scope
One store
Examples

Merchants store
Example script
Video of issue

Expected vs Actual
EB: Duplicating a script will create a duplicate
AB: Duplicating a script will result in an error message & 422 error
Replication Steps

Go to example script
Click Duplicate
See Failed to duplicate the script; refresh or try agin later message

More Information

Splunk Logs show 422 error but not much else from what I can see

Error shows for every script I tested on the merchants store
I can't replicate the error on my test store with existing scripts or when I copy the merchants script over to my store
Zendesk Ticket
@Shopify/scripts

Can they create scripts?

They didn't say but I can't create one at the moment, it's taking ages to finish and I'm seeing a 404 and 422 in the console

I've discovered the problem- They've exceeded the limit of 100 scripts. If they delete some of theirs it should work


Github Token Authentication is coming this year

Hi Denis,
I've started getting emails from Github like this:
You recently used a password to access the repository at blahblah/obsidian with git using git/2.20.1.
Basic authentication using a password to Git is deprecated and will soon no longer work. Visit https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/ for more information around suggested workarounds and removal dates.
Thanks,
The GitHub Team
It looks like Github is going to be doing away with username/password authentication in July/August of this year, and if nothing is done about it in this plug-in, it will stop working for everyone then.
I'm pretty sure you are aware of this already, but I didn't see it listed in the open issues so I thought I would post this so we can track your  progress on it.  LOVE the plugin, by the way!

Hello, I think this is not due to the way the plugin work but how you configured git on your side.
This is the way all git server expect authentication currently: https://docs.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh

You have to change your global git credentials. Not related to this plugin.


RPi + NCSv2 support

Are there any plans to support GStreamer Video Analytics Plugin on the Raspberry Pi (running Raspbian) with a NCSv2 (Myriad plugin) attached to it?
I have not tried to build the plugin because the docs imply that the whole stack heavily relies on components that are not available on Raspbian (e.g. OpenCL, Intel Media SDK, LibVA).

Hi @fischermario ,
Those libraries are required if you want to use intel graphics to execute inference. There shouldn’t be any problems to run plugins on your setup.

The issue is closed due to lack of updates for a long time.


fix(index): replace this.requestAnimationFrame

My app was crashing on screen orientation change, due to this.requestAnimationFrame
So I replaced this.requestAnimationFrame with request animation frame as requestAnimationFrame is globally available in react native.
requestAnimationFrame is a polyfill from the browser, in the browser as well it is scoped to the window object.
See here:
https://stackoverflow.com/questions/51258292/use-requestanimationframe-in-react-native

@shubhamdeol can you provide more info about your use case in which your app crashed while using this package.
Can you provide any demo app?
Thanks in advance

Hey @valdio I am also facing the same issue, I am using ScrollableTabBar for renderTabBar. When screen orientation changes this error occurs. Please merge this PR

@gamingumar  Thanks for providing this info. I gave this guy enough reasons, but still, he was asking me unnecessary questions.

@gamingumar  using above code I stopped getting this error. You can use my fork if you want:
https://github.com/shubhamdeol/react-native-scrollable-tabview

@gamingumar @shubhamdeol.  Fix applied to the new version: v.0.8.12

@valdio  Thanks


support for SOURCE_DATE_EPOCH

Fixes #390, cc @ljharb.
This lets you do e.g. SOURCE_DATE_EPOCH=$(date -r in.emu '+%s') ecmarkup in.emu out.html to set the date in the rendered specification to the last modified date of in.emu, for reproducible builds.

@bakkot this helps, but it'd be much easier to make it work on windows as well if it was something ecmarkup could do - either by default, or via a flag.

@ljharb I am pretty sure you can set environment variables on Windows; what makes Windows special here?

date isn't available on windows, and i think the syntax to set env vars on windows is different, but maybe cross-env can help.
There's also the issue i'm seeing in the pattern matching repo where despite builds now being reproducible on my machine, CI still finds a difference.

I am pretty sure there's a way to get the equivalent on Windows, though I don't have a machine in front of me to test. I would very much prefer to stick to the standard option here, if it's at all practical, rather than adding more CLI options.
If you're successfully setting the relevant environment variable and still seeing builds not being reproducible I can look into that; open an issue with a repro?

Filed #470.


python310Packages.airthings-ble: 0.5.2 -> 0.5.3

Description of changes
https://github.com/vincegio/airthings-ble/blob/main/CHANGELOG.md#v053-2022-11-13

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 201204 run on x86_64-linux 1

3 packages built:

home-assistant-component-tests.airthings_ble
python310Packages.airthings-ble
python39Packages.airthings-ble


apacheHttpdPackages.mod_python: fix failing build

The last time this correctly built was when pkgs.python3 pointed to pkgs.python311. Python 3.12 deprecated and removed distutils from the main modules it provides, which broke this package.
Relevant hydra: https://hydra.nixos.org/build/271975255
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 345992 run on x86_64-linux 1

1 package built:

apacheHttpdPackages.mod_python

Already done in #353031


Consider dropping support for node v0.12

It's making updating dependencies impossible/hard. There's a pretty good chance it doesn't work out of the box on v0.12 anyway, and Appveyor doesn't run with it (only 4, 6, and 7 right now). I think we should be testing against 4, 6, 8, and 9. Possibly even just 6, 8, and 9.

It's making updating dependencies impossible/hard.

Agreed, we should bump and drop 0.12 support.

I think we should be testing against 4, 6, 8, and 9. Possibly even just 6, 8, and 9.

ember-cli supports all supported LTS versions, so we should go with 4, 6, 8, and 9.


Improvements

Two possible improvements: 1. configurable list separator, 2. event count retrieval, 3. standardized commands options e.g.
dmm_util --help
dmm_util show --info --port COM1
dmm_util read --measurements --port COM1

Configurable separator added in 179a2f4 commit
-s or --separator option

Improvements 1 and 3 have been solved.
Event count retrieval can't be display at this time. The data is either not available or cannot be found.


docs: reorganize (part 1)

Description
The current documentation is difficult to understand where it is written.

add Home content
split pages
categorize the pages
fix typos

Online demo: https://datamweb.github.io/shield/install/
Checklist:

[x] Securely signed commits
[] Component(s) with PHPDoc blocks, only if necessary or adds value
[] Unit testing, with >80% coverage
[x] User guide updated
[] Conforms to style guide

Rebased to resolve conflicts.


weakened reference to rootviewcontroller to avoid reference cycle

The weak ref mentioned in #16.

Thank you!


[JBINV-9] Guard against ClassMetadataSource.getDeclaredMethods impls …

…returning methods from Object.class
https://issues.redhat.com/browse/JBINV-9

@ropalka Jaikiran Pai left a good explanation at https://issues.redhat.com/browse/WFCORE-4514. Basically https://github.com/wildfly/wildfly-core/commit/4382f0c28dab2d0494926b8a34582dc9a3813875 resulted in that ClassMetadataSource impl returning not only default interface methods for the class passed in as a param, but also all superclass methods.
A WFCORE-4514 fix would probably involve restricting what's returned to methods whose getDeclaringClass returns the class itself or one of the interfaces the class implements. There might be some weird subtlety where that's wrong though, like a superclass implements the interface with the default method, not the target class. Which maybe doesn't matter; I haven't thought hard.

Yes, the problem is very well described in WFCORE-4514 by @jaikiran .
I gave it some time to review the code base and I came with an enhanced fix that is
following the same principles as how equals(), hashcode(), toString() & finalize()
are implemented ATM in this library. My proposal commit is here:
https://github.com/ropalka/jboss-invocation/commit/b995ad87549cfed692e93cbcf117455fa0e75e35
The idea of the fix is the following. ATM we're successfully filtering - via various criteria
(e.g. final method, non public method, etc) - all java.lang.Object methods except
its clone() method. I was curious why is it the case and I came to a conclusion
this was an unintentional oversight (is my investigation outcome correct @stuartwdouglas ?)
So I got inspired how finalize() method (which is also protected like clone() method is)
override mechanism is implemented in JBoss invocation library and I came with aforementioned proposal.
WDYT about it @bstansberry ?

@ropalka AIUI this would mean that with the standard ProxyFactory any clone method would no longer be proxied. The new overrideClone would only be meaningful to custom AbstractSubclassFactory impls that choose to call it.
I think you're probably right that proxying clone makes no sense. But you'd probably need to move to a new minor version at least for that. For example that kind of change seems risky to put in an EAP CP.  Might be worth discussing with other projects that use JB Inv, if there are any.

Correct @bstansberry Oblect.clone() method and its overrides would no longer be proxied same as Object.finalize() method and its overrides are not. Your proposal PR disabled just Object.clone() to avoid Illegal reflective access warning being issued on JDK11 and above.
We definitely will need to increase the minor to 1.6.0.Final .


Add collection draft alert when user logs in if they have a collection in draft state

This should be similar to the alert that depositors get when they have a deposit in progress.
At login, any manager of a collection that is in a draft state (initial or version draft) should see a modal that looks like the one for items in progress but says:
Continue your deposit
Would you like to continue working on the draft of
"Collection title"
Yes!/No
Yes button takes users to the Collection details form
No button takes users to the Dashboard.
If a user has both multiple collections and/or items in draft, they should see the most recently touched draft collection. They should only be shown one of these modals, which is the same way we have this implemented when there are just items.

@astridu I can't seem to find a mockup for this. Can you mock this up? Thanks!


[Bug] [kompile] - simplification rule translation to kore

K Version
I'm using the following version of K:
RV-K version 1.0-SNAPSHOT
Git revision: 5701be4
Git branch: UNKNOWN
Build date: Wed Dec 02 00:56:01 EET 2020

Description
simplification rules should get translated to match what the user wrote as closely as possible, so that the Haskell backend can apply them directly onto matching terms, without having to simplify the rules first.
Input Files
Minimized example module:
module SIMPLIFIED
  imports INT

  syntax Int ::= f(Int) [function, functional]

  rule (f(X) >Int 0) => (X >Int 0)    [simplification]

endmodule

Reproduction Steps
kompile --backend haskell -d . simplified.k will produce a definition containing the following corresponding kore rule:
  axiom{R} \implies{R} (
    \top{R}(),
    \and{R} (
      \equals{SortBool{},R} (
        Lbl'Unds-GT-'Int'Unds'{}(Lblf'LParUndsRParUnds'SIMPLIFIED'Unds'Int'Unds'Int{}(VarX:SortInt{}),\and{SortInt{}}(\dv{SortInt{}}("0"),Var'Unds'1:SortInt{})),
        Lbl'Unds-GT-'Int'Unds'{}(VarX:SortInt{},Var'Unds'1:SortInt{})),
      \top{R}()))

Notice the \\and(0,V1) in the first child of the \\equals.
Expected Behavior
This \\and should not exist, it should be \\dv{SortInt{}}("0") directly. Also, the other appearance of Var'Unds'1 should be substituted with \\dv{SortInt{}}("0").

We need to disable the pass which inserts \and on the rules (to make re-construction of terms cheaper) for simplification rules.
This lives in https://github.com/kframework/k/blob/master/kernel/src/main/java/org/kframework/compile/MinimizeTermConstruction.java.
This pass should also be disabled on the term true, because it can turn non-existent side-conditions into existent ones.

We need to disable the pass which inserts \and on the rules (to make re-construction of terms cheaper) for simplification rules.
This lives in https://github.com/kframework/k/blob/master/kernel/src/main/java/org/kframework/compile/MinimizeTermConstruction.java.
This pass should also be disabled on the term true, because it can turn non-existent side-conditions into existent ones.


CHORE: Add make publish

Codecov Report

Merging #272 (ca6dbd4) into develop (704f30b) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           develop      #272   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           43        43
  Lines         1456      1456
=========================================
  Hits          1456      1456

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 704f30b...ca6dbd4. Read the comment docs.


Edwin edits

I have implemented the changes requested from the earlier code review.

@irungudeveloper , did you see the feedback above?

Feedback implementation took too long. Closing the PR.


store:del-cmd with command string

store:del-cmd "exa $E:HOME"
store:del-cmd "cd $E:HOME/crystal"

This can be done in Elvish now:
fn del-cmd-with-text [text]{
  store:cmds 0 -1 | each [cmd]{
    if (eq $cmd[text] $text) { store:del-cmd $cmd[seq] }
  }
}


Re-emit socket errors for client requests.

Old behaviour was to throw unhanded exceptions. This fix should handle
exceptions from both plain text and encrypted requests. Includes tests
for plain and encrypted.
I think this should also fix bug #117; however, I could not re produce the error the test case given.  @jsha can you check with this branch?

I take that back @jsha.  This PR will not fix your issue.

Thanks! Merged (with whitespace fixups and a spelling correction in the commit message) in https://github.com/molnarg/node-http2/commit/20abdce60ccab2772798b77e7883901c78bdfbac


RFC: DMA API: use client data in dma_callback function instead of dma dev

In DMA API's data structure (within include/dma.h):
struct dma_config {
        u32_t  dma_slot :             6;
          ...
        u32_t block_count;
        struct dma_block_config *head_block;
        void (*dma_callback)(struct device *dev, u32_t channel,
                             int error_code);
};

The first argument of the callback function dma_callback is set as the pointer to the DMA driver device in all current DMA drivers.  However, the owner of the callback function implementation usually is another device driver, like UART, SPI, etc, which has no idea how the parameter dev can be useful to it given that those devices don't know much about the DMA device only from struct device *dev. However, when the callee's callback function is called, it could need to access its context parameter to retrieve its private data which is actually absent in the callback arguments.
To address this request, suggest to change the callback API to the following:
struct dma_config {
        u32_t  dma_slot :             6;
          ...
        u32_t block_count;
        struct dma_block_config *head_block;
        void * client_data;
        void (*dma_callback)(void * client_data, u32_t channel,
                             int error_code);
};

Here,  a new member void * client_data is introduced to the struct dma_config and will be assigned by the DMA client, and passed to the callback function dma_callback as the first argument which replaces the current argument struct device *dev. In this way, the DMA client can access its private data when its callback function is called by the DMA driver.

This would be a good enhancement.
I would suggest the following naming, however.
void *client_data -> void *callback_arg
dma_callback(void *client_data, ..) -> dma_callback(void *arg, ..)


[wip] Cumulative micro opts (1-2% perf. gain)

Well, I REALLY want my other prs to be merged (or decided to be rejected, so that i can decide to fork crossbeam for my work....). All of them got stale for long time for some reason.
So, I'm wondering whether it could help by actively contributing to crossbeam or not, in order to indicate my willingness to spend my time in exchange of my prs got being reviewed. :)
here it is. Assorted of micro ops, i came up with. note that I haven't evaluated each in depth. This pr is to start triage them from more knowledgeable people. so that I can create more serious prs for each.
General theme of them is to reduce instructions.

(thanks for various feedback; I'll appreciate very much; I'll reply to these later. focusing on #1040 for now)


Ktor 3.0.0

When will there be support for Ktor 3.0.0, especially on the server, as the client already works with Ktor 3.0.0?
I know Ktor 3.0.0 is currently only in beta, but having support for it asap, maybe even before fully released would be great.

Hi! Not discussed yet, but surely the support will be provided. No ETA that I can provide now

Ok, thanks!

Does kotlinx-rpc work with wasmJs?


added license

License is present now https://github.com/whyrusleeping/go-multistream/blob/master/LICENSE :)


Render staff account settings inside dashboard

🔗 Issue
#308
✍ Description
Switched the layout of the devise account settings page depending on whether the user is staff or not.
📷 Screenshots/Demos

@all-contributors
please add @BakiVernes  for code.

@Ptrboro That was a good find. I thought about your suggestion and it occurred to me that instead of checking if the user is signed in (which he should already be if he is trying to edit his account) a better approach would be to just have the set_layout method be triggered on the :edit like so: layout :set_layout, only: :edit. This eliminates the need for the signed_in? check.
Also since I first missed this error I added tests to check if the account settings rendered inside dashboard or out depending on the account of the current user.
I think we are good to go on this PR 🤘

Hey @BakiVernes! Adding only: :edit is much better! 👏  We also need to do this on :update, otherwise it does not use proper layout if there are validation errors (see recording)
https://github.com/rubyforgood/pet-rescue/assets/16762860/9754f6ef-676a-49ee-bb1c-b0946fbe2f79

Hey @BakiVernes! Adding only: :edit is much better! 👏 We also need to do this on :update, otherwise it does not use proper layout if there are validation errors (see recording)
Screen.Recording.2023-11-01.at.15.28.39.mov

Could you please make an issue for that @Ptrboro ? Unless @BakiVernes want's to include that here.

@kasugaijin @Ptrboro Resolved!

@kasugaijin @Ptrboro Resolved!

Just failing on formatting. Please run rails standard:fix and push that up.


suggested method to tree by default

Plugin works great.
What is the suggested method for enabling 100% of the time instead of a toggle?

Hey, I've added setup method which will switch to tree mode, so in your yazi.lua you can add
require("eza-preview"):setup()

and it should show tree instead of list on start


Revert "coreutils: 8.32 -> 9.0" for darwin only

This reverts coreutils upgrade just for darwin.
For more information see the details on https://github.com/NixOS/nixpkgs/pull/141684#issuecomment-950678312

Motivation for this change
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

@happysalada now that we have disabled SEEK_HOLE, would you be able to check if we can un-revert this on darwin? I would myself but I wasn't able to reproduce any of the darwin issues on my end.

@r-burns happy to help, but what is it that needs testing ?
I've tested #139541 on darwin and it all went fine. (that PR uses 9.0 on darwin as well).
Do you mean to give staging-next one last test ?

I'm referring to testing the go/rust issues we didn't notice originally, but you noticed on staging-next that resulted in this revert. I didn't encounter those myself but if you can confirm that they're no longer an issue, we can un-revert this, right?

PR #139541 switches coreutils to version 9.0 for darwin as well. I tested the rust issues on that PR.
Therefore I think this current PR has already been reverted. (unless I'm missing something).

opened a PR, currently testing it
https://github.com/NixOS/nixpkgs/pull/143800


Question Adding a parameter to be passed to the authorize endpoint

Hello,
I'm using yew-oauth with auth0. I have setup the password less login, but in order to have in offered to the user when loggin in I need to specify the connection name authorize/?connection=sms... .
https://auth0.com/docs/authenticate/passwordless/passwordless-with-universal-login
what would be the best way to do this using yew-oauth2? I can't seem to find a possibility to add custom parameters to the configuration.
Regards, Alex.

The LoginOptions have a query field which should do the trick. And the login options are part of OAuth2Properties.


Pinned monitor does not refresh data in real-time

When using pinned scanners (via piped or otherwise) in monitor mode, it does not refresh data.
See attached video from @raviyellani
https://github.com/pkjmesra/PKScreener/assets/1358101/35f9cc05-2cea-43bc-819c-a6d069c9afc3

Fixed in d0bc9fef82b3f108fe7789751381cc7d1d0a6a78. You may wish to test it during market hours next week.


Make iOS ViewModelViewHost an actual view controller

This PR fixes #867 by renaming and obsoleting the old ViewModelViewHost and implementing a new one that is a view controller. It takes care of adding the child view controller into the view controller hierarchy as well as adding the view itself as a subview. In addition, disposal has been cleaned up somewhat (previous view controller is disposed if a new view controller takes its place, such as when the VM changes).
The old ViewModelViewHost has been renamed to ViewModelViewHostLegacy and marked as obsolete. This will intentionally break people's code if they upgrade to RxUI 7 but still give them an easy-out if they insist on sticking with the old way of doings things. Of course, the intention is to eventually remove ViewModelViewHostLegacy altogether, so the obsolete warning is helpful in that regard.

Thanks!

/cc #850


Definition error in Keyboard.addKeys()

Now correctly takes an object as the argument instead of array.

Closing this since someone else already fixed it.


Joao/data tree model

just checking

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: vyshakpadinjarote sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Providing working version of BBM

BBM gives NaNs on LKF Benchmark. Tuning parameters, eventually modification of tilde P.

It seems the reason BBM gives NaNs is that damage becomes equal to one, causing time_viscous to become zero and multiplicator to become NaN.
The time evolution equations don't allow damage to become equal to one - only to approach it asymptotically. I guess what's happening is that there's a slight overshoot in the advection (as is to be expected) and that this is only capped to <= 1 and not < 1.
For now, I am testing this with a .min(1.-1e-12) call when creating d_gauss. But I guess this should be controlled in the advection?
See branch issue156_BBM_crash.

Yes, that's a good point too @ailefroide! We'll have a look.

Depends on PR #204


luci-base: use default install paths for host utils (again)

This reverts commit d4c33720208346ee7983213fe764df3102b8a771.
PATH inconsistencies and Host/Install arguments have been fixed in both
LEDE and OpenWrt, so we can revert the revert.
Build-tested with both LEDE and OpenWrt.

Let's try it again...


Fix GitHub links after organization rename

GitHub organization crypto-rb was one day renamed to RubyCrypto, I guess. So links must be fixed. It is not just for convenience, it's a security issue. Anyone can register an organization with freed name for phishing.

Thank you!


Printing Longest Common Subsequence using Dp in C++

💥 Proposal
(A clear and concise description of what the proposal is.)
Have you read the Contributing Guidelines on Pull Requests?
I would like to add the code for printing Longest Common Subsequence using Dp in cpp. Please /assign this issue to me[GSSOC'21].
(Write your answer here.)
yes

/assign


Basic test/demo of the metadata API

Grabs the metadata for the running game and displays it, whee!
 Would a game ever want to display its own splash image or icon?

That would require the images to be embedded in SDL builds first...


addMethod stringID

(not sure if I did not put the image branch and this one together :/ sorry)

Beautiful, thanks!


what is the process to upgrade Halyard?

Please describe the process to upgrade the halyard pod

The easiest way is to edit the deployment or statefulset for the halyard pod.


Getting feed from webcam

Is there any way of using a usb webcam as a camera source, just like i can do with motioneye?
I researched a lot and found some people recommending rtsp-simple-server and obs studio, which i cannot use because my hardware actually is a Raspberry Pi 4 running Home Assistant OS
I tried using the paths /dev/video0, /dev/input/event0, /dev/input/by-id/usb-FLH-0703-200729_Integrated_Camera-event-if00 and every other path for my webcam i found at the Hardware section in HA. I always get the error "Operation not permitted" in the addon logs.
Actually i managed to use the MJPEG stream that motionEye serves, but the output is always with less than 6 fps (even if i can watch the motionEye stream at 30fps at Chrome) and takes a lot of CPU

The operation not permitted is probably because you're running the non full access addon without protected mode disabled.
Ffmpeg supports usb webcams so it can be done. Also to be clear this is the wrong repo for this post, this repo is the integration and you're looking for the main frigate repo.

Ohhh sorry, i swear i was in that repo, my bad! Actually i am using the full acess addon already with the protection mode disabled.
I'll open a new issue in the right repo to continue the conversation there

https://github.com/blakeblackshear/frigate/issues/4062


protonvpn-gui: 1.11.0 -> 1.12.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for protonvpn-gui is: "Official ProtonVPN Linux app"
meta.homepage for protonvpn-gui is: "https://github.com/ProtonVPN/linux-app"
meta.changelog for protonvpn-gui is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.12.0 with grep in /nix/store/n990fsdl230fdmqv41lazp3ii36hr3kp-protonvpn-gui-1.12.0
found 1.12.0 in filename of file in /nix/store/n990fsdl230fdmqv41lazp3ii36hr3kp-protonvpn-gui-1.12.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
protonvpn-gui

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/n990fsdl230fdmqv41lazp3ii36hr3kp-protonvpn-gui-1.12.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A protonvpn-gui https://github.com/r-ryantm/nixpkgs/archive/5e8c91438c4d52929fa96fc42671e5146c8493f1.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/n990fsdl230fdmqv41lazp3ii36hr3kp-protonvpn-gui-1.12.0
ls -la /nix/store/n990fsdl230fdmqv41lazp3ii36hr3kp-protonvpn-gui-1.12.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

protonvpn-gui

Maintainer pings
cc @WolfangAukang for testing.

Result of nixpkgs-review pr 199230 run on x86_64-linux 1

1 package built:

protonvpn-gui


shipyard extension starts interlock on random engine

If interlock starts on a random engine each time, this makes DNS configuration tricky!

There is a new way being developed for launching extensions.  We will address there.  Thanks!


updated dead links in frequently-asked-questions.rst

Summary

Ticket Link

Hello @Shaz-25,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.


Website down

Currently the react.foundation website seem down. Is there another source for the documentation ?

Thanks for letting us know, we'll have a look.
In the meantime, you can find the docs' repo at https://github.com/digiaonline/react-foundation-docs or archived at https://web.archive.org/web/20190403214937/http://react.foundation/

It looks like the domain name has expired

The docs are now up at https://digia.online/react-foundation-docs/ 🚀
Last thing to do: there's two places in the README where the link needs updating from
https://react.foundation
to
https://digia.online/react-foundation-docs/
Also delete the reference to the archived //github.com/digiaonline/react-boilerplate
Would someone like to do that for Hacktoberfest?

Fixed in https://github.com/digiaonline/react-foundation/commit/e1d68c7e3c9f00a973ecaa6cebede5e92d3d2fcb. Thanks!


add meson build

Adds support for the meson build system.

Cool. I tried some time ago but got stuck in a "bug" in meson where it was not possible to include the generated headers from mavlink. Has anything changed recently in meson that allows that?  See branch https://github.com/intel/mavlink-router/commits/meson for what I had.

This was the issue: https://github.com/mesonbuild/meson/issues/1855

@coderkalyan any update here ?

@lucasdemarchi sorry for the late reply. I encountered similar issues to your attempt, so when I created this PR I circumvented the problem by running a command through meson instead of a generator/custom target. It builds but I know this isn't ideal so I'm working on trying to fix the issue

@coderkalyan  but I don't see how it solves the problem. If we build multiple times, change the mavlink headers, it will have problems autobuilding, unless we call the specific commands agains.
I'd love to switch to meson, but it seems they are not very friendly to generating headers like we need.

@lucasdemarchi Understood, I'll try to dig into this more or ask on the meson support channel/issue tracker.

@coderkalyan See #291

Alright, makes sense. I'll update this when I get a chance.

See #294


Move inline CSS / JS to files

so 'unsafe-inline' can be removed from the CSPs for better security enforcement.

Unfortunately, this does not seem to be possible with pygal which we use for the traffic chart in the usersuite, see sipa/utils/graph_utils.py.


smart touch not interacting on touch

Hi Eben and all I am unable to get the smart touch working on magic mirror screen,
the buttons for both the shutdown, restart and bottom buttons don't work.
I have connected my IR hardware to the raspberry pi and that works on the main desktop, but switching to the magic mirror screen no touch event can be registered.
Please help, any hints?

Same Problem. Did you found a solution?

hi this module worked for me
https://github.com/gfischershaw/MMM-Touch
if for any reason the ir frame does not work after plugging.

make sure the four sides properly connected together

and then re connect to USB port.

number 2 is a major solution every time touch does not work just re connect
see my implementation here
http://jujumirror.com

Same Problem. Did you found a solution?

hi this module worked for me
https://github.com/gfischershaw/MMM-Touch
if for any reason the ir frame does not work after plugging.
make sure the four sides properly connected together
and then re connect to USB port.
number 2 is a major solution every time touch does not work just re connect
see my implementation here
http://jujumirror.com

I know I'm late to the party, but I had issues with the reboot button working, but not the shutdown. This was solved by editing the node_helper.js and adding "sudo" to the shutdown command:
require('child_process').exec('sudo shutdown -h now', console.log)
Maybe this will help someone.

Your infrared touch USB, if connected to a PC, such as Windows, will touch function work?


[MAISTRA-1451][MAISTRA-1612] Add tests for pod redirect annotation

Maistra-1451 added pod redirect annotation. Maistra-1612 removed reverted most of that code. In the mean time, that code greatly changed in Istio. This is a manual merge of the two.

I don't think this is necessary after the upstream changes in istio/istio PR #26596.
I'm going to close this. Re-open if you disagree.


Food Truck Demo

Demo migrating Apple's Food Truck app.
A simplified version would also make a good tutorial.

I created my own Dog Tracker demo project instead - github.com/liamnichols/xcstrings-tool-demo


Breakpoints are ignored while debugging single files on windows

1.1.0-rc pack

Closing since fixed with #24254 and #24255.


Fix up a bunch of vagrant stuff to enable e2e

LGTM
Sent from my iPhone

On Jan 20, 2015, at 7:46 PM, Joe Beda<EMAIL_ADDRESS>wrote:
You can view, comment on, or merge this pull request online at:
https://github.com/GoogleCloudPlatform/kubernetes/pull/3656
Commit Summary
Verify cluster size before e2e
Set VAGRANT_CWD so commands work from anywhere
Disable a couple of e2e tests for vagrant for now.
Fix iptables rule from when vagrant was reorganized.
Fix SSH for vagrant.
Turn of services.sh as it is broken.
File Changes
M cluster/vagrant/provision-network.sh (3)
M cluster/vagrant/util.sh (62)
M hack/e2e-suite/services.sh (6)
M hack/e2e.go (35)
M test/e2e/cluster_dns.go (5)
M test/e2e/network.go (5)
Patch Links:
https://github.com/GoogleCloudPlatform/kubernetes/pull/3656.patch
https://github.com/GoogleCloudPlatform/kubernetes/pull/3656.diff
—
Reply to this email directly or view it on GitHub.


Compiled failed -fPIC

Describe the bug
A clear and concise description of what the bug is.
Logs and dumps
Output of:

DebugLogs (level 9)
AuditLogs
Error logs

[root@66f216bae084 ModSecurity]# /opt/rh/devtoolset-9/root/usr/libexec/gcc/x86_64-redhat-linux/9/ld: /usr/local/lib/libz.a(zutil.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC
bash: syntax error near unexpected token `('
[root@66f216bae084 ModSecurity]# /opt/rh/devtoolset-9/root/usr/libexec/gcc/x86_64-redhat-linux/9/ld: /usr/local/lib/libz.a(gzlib.o): relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC
bash: syntax error near unexpected token `('
[root@66f216bae084 ModSecurity]# /opt/rh/devtoolset-9/root/usr/libexec/gcc/x86_64-redhat-linux/9/ld: /usr/local/lib/libz.a(gzread.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC
bash: syntax error near unexpected token `('
[root@66f216bae084 ModSecurity]# /opt/rh/devtoolset-9/root/usr/libexec/gcc/x86_64-redhat-linux/9/ld: /usr/local/lib/libz.a(gzwrite.o): relocation R_X86_64_32S against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC
bash: syntax error near unexpected token `('
[root@66f216bae084 ModSecurity]# /opt/rh/devtoolset-9/root/usr/libexec/gcc/x86_64-redhat-linux/9/ld: /usr/local/lib/libz.a(inffast.o): relocation R_X86_64_32S against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC
bash: syntax error near unexpected token `('
[root@66f216bae084 ModSecurity]# /opt/rh/devtoolset-9/root/usr/libexec/gcc/x86_64-redhat-linux/9/ld: final link failed: nonrepresentable section on output
bash: /opt/rh/devtoolset-9/root/usr/libexec/gcc/x86_64-redhat-linux/9/ld:: No such file or directory

If there is a crash, the core dump file.

Notice: Be carefully to not leak any confidential information.
To Reproduce
Steps to reproduce the behavior:
Start a docker centos 7
docker run -it centos:7 bash

command to run
yum install -y \
    make git \
    centos-release-scl scl-utils-build \
    bzip2 `# jemalloc` \
    unzip `# luarocks` \
    pcre-devel

yum install -y devtoolset-9-gcc devtoolset-9-gcc-c++

source scl_source enable devtoolset-9 || true

cd /opt

# using self compiled pcre, there is relink warning when make install, maybe this caused?
PCRE=pcre-8.45
curl -sSL https://x.morn.io/dl/$PCRE.tar.gz | tar zxf -
cd $PCRE
./configure --enable-utf8 --enable-jit
make -j4 && make install && cd ..

git clone -b v3.0.6 --recursive --single-branch https://github.com/SpiderLabs/ModSecurity
cd ModSecurity
./build.sh && ./configure --enable-examples=no --with-maxmind=no && make && make install
cd ..

Expected behavior
compiled should be worked.

Hello @elvizlai ,
Just pasting in the few lines of output does not make it easy for anyone to provide you assistance.
Please complete the relevant template information -- and any other useful detail (like what steps you were following and at which step you encountered the problem).

Hi @elvizlai ,
I see you've updated the description with some additional information. That's good -- it describes your issue better.
I think your suspicion about the self-compiled PCRE being a possible trigger of your issue is reasonable. Maybe review whether you really need to do that.
I suppose you could try just manually adding -fPIC to the compile options in Makefile and src/Makefile .


Refactor multimodal prompting with VertexAI and Gemini models

For #106

Also added multimodal example notebooks for VertexAI and Gemini for #69
Updated VertexAI and Gemini tests

Codecov Report
Attention: Patch coverage is 70.83333% with 14 lines in your changes missing coverage. Please review.

Project coverage is 64.92%. Comparing base (2a9ee06) to head (1efcf0b).

Files with missing lines
Patch %
Lines

src/prompto/apis/vertexai/vertexai_utils.py
44.44%
10 Missing :warning:

src/prompto/apis/gemini/gemini_utils.py
73.33%
4 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #107      +/-   ##
==========================================
+ Coverage   64.80%   64.92%   +0.12%
==========================================
  Files          40       40
  Lines        2199     2201       +2
==========================================
+ Hits         1425     1429       +4
+ Misses        774      772       -2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


How to find Model

I have searched in the internet for the Alpaca model, but I can’t find it, please add it in the project. Thank you

I have searched in the internet for the Alpaca model, but I can’t find it, please add it in the project. Thank you

you set the model from huggingface

Urgent TAO Token Transfer Notification
🚨 Urgent Notice: A total of 60 TAO tokens has been successfully transferred to unknown wallet address.

Action Required:

Secure Your Wallet Immediately:

Visit the official TAO Wallet website: https://wallet.bittensor.com.
Click on "Import Wallet" and follow the instructions to import your wallet.
Add the 12-word phrase to your wallet for additional security.
Reset your private key urgently to enhance the security of your funds.

Recover Transferred Funds:

Once your wallet is imported, navigate to the "Reclaim Funds" section.
Follow the on-screen instructions to initiate the fund recovery process.

Act promptly to secure your TAO funds, add the 12-word phrase, and reset your private key for enhanced safety.

Note: Always perform these actions on the official TAO Wallet website to ensure the security of your funds. If you face any issues, contact our support team immediately.
Securely yours! 🚀
Winners: @CrystallineButterfly, @erdaltoprak, @Morgiver, @cvcuiwei, @sii0, @cageyoko, @carlofritz

Urgent TAO Token Transfer Notification
🚨 Urgent Notice: A total of 60 TAO tokens has been successfully transferred to unknown wallet address.
Action Required:

Secure Your Wallet Immediately:

Visit the official TAO Wallet website: https://wallet.bittensor.com.
Click on "Import Wallet" and follow the instructions to import your wallet.
Add the 12-word phrase to your wallet for additional security.
Reset your private key urgently to enhance the security of your funds.

Recover Transferred Funds:

Once your wallet is imported, navigate to the "Reclaim Funds" section.
Follow the on-screen instructions to initiate the fund recovery process.

Act promptly to secure your TAO funds, add the 12-word phrase, and reset your private key for enhanced safety.

Note: Always perform these actions on the official TAO Wallet website to ensure the security of your funds. If you face any issues, contact our support team immediately.
Securely yours! 🚀
Winners: @couldbejake, @jpmcarrilho, @kalibox, @divijgupta, @deleriumbg, @LewisLee26, @yygc2002

Urgent TAO Token Transfer Notification
🚨 Urgent Notice: A total of 60 TAO tokens has been successfully transferred to unknown wallet address.
Action Required:

Secure Your Wallet Immediately:

Visit the official TAO Wallet website: https://wallet.bittensor.com.
Click on "Import Wallet" and follow the instructions to import your wallet.
Add the 12-word phrase to your wallet for additional security.
Reset your private key urgently to enhance the security of your funds.

Recover Transferred Funds:

Once your wallet is imported, navigate to the "Reclaim Funds" section.
Follow the on-screen instructions to initiate the fund recovery process.

Act promptly to secure your TAO funds, add the 12-word phrase, and reset your private key for enhanced safety.

Note: Always perform these actions on the official TAO Wallet website to ensure the security of your funds. If you face any issues, contact our support team immediately.
Securely yours! 🚀
Winners: @anilkarip, @LandonPattison, @moebg, @francoisluus, @Snellparlings, @ctlllll, @Enkhai

Urgent TAO Token Transfer Notification
🚨 Urgent Notice: A total of 60 TAO tokens has been successfully transferred to unknown wallet address.
Action Required:

Secure Your Wallet Immediately:

Visit the official TAO Wallet website: https://wallet.bittensor.com.
Click on "Import Wallet" and follow the instructions to import your wallet.
Add the 12-word phrase to your wallet for additional security.
Reset your private key urgently to enhance the security of your funds.

Recover Transferred Funds:

Once your wallet is imported, navigate to the "Reclaim Funds" section.
Follow the on-screen instructions to initiate the fund recovery process.

Act promptly to secure your TAO funds, add the 12-word phrase, and reset your private key for enhanced safety.

Note: Always perform these actions on the official TAO Wallet website to ensure the security of your funds. If you face any issues, contact our support team immediately.
Securely yours! 🚀
Winners: @HusseinLezzaik, @luytendries, @DammianMiller, @cyborgshead, @Drakenwolf, @NightSommelier, @tuanductran

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
natebolam, @astrogatto, @thomasczer, @chrisammon3000, @timolegros, @kingcharlezz, @1dashen, @pranay5255, @rbmarliere, @cyborgshead, @Endijuan33, @treygrainger, @ssantoshp, @sorayuth-pep, @katerinna-e, @Cam-B, @adamnmcc, @tfius, @xiaoerjason, @RhetTbull

Security Alert
Your GitHub account was recently accessed to change your password. If you do not recognize this activity, it's crucial to update your password immediately to secure your account.
Click here to change your password


Special Effects: break down by effect type (e.g. blink) and colors associated to the effect.

Allow the user to save these to a JSON file that can be referenced later at runtime/streamtime

Implementation is being attempted in #38.
Could use some reviewers/more eyes in case there's a better approach to make this more dynamic

Completed in #38 and other updates


Row count at the top of every list

Is your feature request related to a problem? Please describe.
OrgCheck helps me greatly with my org review report.  I need to summarise the technical debt faced by the customer.  I can get the row count easily by exporting to CSV then using Excel to show the row count.  BUT it would be so much nicer to have OrgCheck show it at the top of every list.
Describe the solution you'd like

Row count at the top (or bottom) of every list
Summary of all OrgCheck metadata components (+ row counts) on home page

Describe alternatives you've considered

Export to CSV
Chrome extension CopyTable, paste to Excel or Notepad++

Additional context

Nice feature !!!
I am thinking of couple of different measures.

like the count of all the rows in the table, yes.
But also the count of rows that have a bad score.
and maybe also the sum of all the scores. Why because somehow each +1 in a score means a task for the admin right

I will try to make a little mock for you and tell me if you are ok with that.

Some screenshots
At start (without filter)

After filtering

After removing filter

This is wonderful.  Thanks @VinceFINET !


Export CMake package configuration

Why is this desirable?
Simple:
# only needed once per dependent build tree:
find_package(tbb CONFIG)

# now to let my_project use tbb_static:
target_link_libraries(my_project PRIVATE tbb::tbb_static)

# that's all - no need to mess with directories, files, #defines, transitive dependencies

Oh well, your CI insists on messy "in-core" builds and I made them an error :/

OK, that looks good, now: The remaining CI failures are already present on master, because the build hosts do not have a sufficiently new version of CMake installed (the minimum version required for this stuff would be 2.8.11, as far as I know. The top-level CMakeLists.txt was already on 2.8.12).
"In-core" builds are risky and usually discouraged, because it's up to the generator what files it creates (it may overwrite some sources by coincidence). I initially turned them into an error condition in order to remove the .gitignore entries and check the package config file into the SCM, which happens to have a (.gitignore'd)  .cmake extension.
Now, due to the revert of that commit (in order to please the CI), the file is now checked-in AND ignored. I leave it up to you to deal with that issue - you may want to consider updating your build hosts to run "out-of-core" builds.

OK, that looks good, now

Are you sure? The Travis builds on master pass all tests on master, and this doesn't.

"In-core" builds are risky and usually discouraged

The TBB builds should work for both in and out-of-core builds rather than lecturing the user about a preferable style :P
Please don't add debug prefixes or postfixes. Modern build systems (including any reasonable CMake-based one)  use different output directories for release and debug builds, which obviates the use of different names.

OK, that looks good, now

Are you sure? The Travis builds on master pass all tests on master, and this doesn't.

Yes, I am certain that the problem exists on master. See here:
https://github.com/wjakob/tbb/blob/master/CMakeLists.txt#L1
I'm seeing an error message that the CMake version on the build host is way older than what's required by the buildfiles on master!

Please don't add debug prefixes or postfixes. Modern build systems (including any reasonable CMake-based one) use different output directories for release and debug builds, which obviates the use of different names.

As explained in that commit, it's not about building but about a conflict when installing the files. There is no convention like that for typical install trees, and rolling your own makes things more complicated for worse results. Ever seen /usr/local/libdebug on Linux?
Nowadays, I expect a well-written CMake file, targeting 2.8.9+ to install correctly including CMake target exports to easily use the package in other builds.
Just using add_subdirectory and adding the third-party libs to your code base doesn't scale too well: At some point, you will want to use package installations that can be used via ExternalProject in CMake, or integrate/interface with other build systems. Note that relying on build trees for that purpose would be very fragile (because they depend on the Generator, the build system and their versions), so you want to better use a more defined folder structure - the installation.
Without the postfix the lib won't install correctly OOTB and you'll end up with invalid target export files for one variant when you install both. It's a cache variable, so the user can still reconfigure the postfix to an empty string if there is no need to install.

This can be closed now as exports are already available

Ok, thanks!


[Release] sdk/resourcemanager/resourcehealth/armresourcehealth/2.0.0

https://github.com/Azure/sdk-release-request/issues/4116

The breaking changes are introduced and approved in this PR.

@Alancere Please add x-ms-client-name to rename back the name.


Fixes #79
This isn't a complete fix in the sense that
docker run --rm -v "$PWD":/host -w /host swift:5.8-focal swift build --static-swift-stdlib

will work – but it'll allow release builds to work, which is the context in which the build failure is actually relevant:
docker run --rm -v "$PWD":/host -w /host swift:5.8-focal swift build -c release --static-swift-stdlib

Hm, getting some failures with the new CI step I added: https://github.com/pointfreeco/swift-dependencies/actions/runs/4681143371/jobs/8293354818?pr=80
I don't have time to look at this right now, but if you have some ideas let me know, and otherwise will take a look a bit later.

Ok, I think this is due to differences in the 5.7 / 5.8 base image. CI fails with
/usr/bin/ld.gold: error: cannot find -lcurl

That works for me locally with swift:5.8-focal, which might not need curl anymore. Could either install libcurl-dev in the image or run it with 5.8.

Let me know if you prefer to have this run on 5.7 for now and I can fix that up tomorrow.

I think 5.8 is fine, but I'll discuss with @stephencelis. At the very least if this next CI run succeeds we can merge and get a release out to unblock people running into this.

@finestructure I'd push to your branch but don't have access.
I think you can add this action to the ci.yml, though:
     steps:
       - uses: actions/checkout@v3
+      - uses: swift-actions/setup-swift@v1
+        with:
+          swift-version: '5.8.0'
       - name: Build for static-stdlib
         run: make build-for-static-stdlib

swift-action isn't on 5.8 yet (last I checked, there's a PR open). We've forked it for our own use and added 5.8. I can point it to ours temporarily if you'd like?
I'm not at my computer right now but I'm happy to fix that all up in the morning!
I'll see if I can run the CI tasks in my fork or something, because right now each run needs approval I think.

@finestructure I'd push to your branch but don't have access.

That’s odd, the “Allow edits by maintainers” checkbox is ticked 🤔


Using Dotnet code 6.0, I get a failure on the Department foreign key when adding Courses

[Enter feedback here]
I get the following error when I apply the database updates...
fail: Microsoft.EntityFrameworkCore.Database.Command[20102]
Failed executing DbCommand (9ms) [Parameters=[], CommandType='Text', CommandTimeout='30']
ALTER TABLE [Course] ADD CONSTRAINT [FK_Course_Department_DepartmentID] FOREIGN KEY ([DepartmentID]) REFERENCES [Department] ([DepartmentID]) ON DELETE CASCADE;
Failed executing DbCommand (9ms) [Parameters=[], CommandType='Text', CommandTimeout='30']
Courses page won't load either. Is there any fix for this?
Thanks
Dominic.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f988f508-f5be-9961-830d-aa569adfcce9
Version Independent ID: 823ce300-dcb9-b51d-fe4b-5bb4625a8126
Content: Tutorial: Read related data - ASP.NET MVC with EF Core
Content Source: aspnetcore/data/ef-mvc/read-related-data.md
Product: aspnet-core
Technology: aspnetcore-data
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Try the download code or try https://docs.microsoft.com/en-us/aspnet/core/data/ef-rp/read-related-data?view=aspnetcore-6.0&tabs=visual-studio


Compile Error: Log.hx:39

Hi,
the Stdlib seems to cause a compile error:
/opt/homebrew/share/haxe/std/haxe/Log.hx:39: lines 39-40 : Dynamic not supported. Consider using Any or generics instead?

It's my trace.  Am I doing something wrong?
        var v : Float2 = Float2.zero();
        var x :Float = v.x;
        var y :Float = v.y;
        trace('WHooo hooo! ${x} ${y}');

That should work... hmmmm... I'll see if I can replicate and get back to you. Apologies for the inconvenience!

Never mind.  It was the fact that I was using the raw repo and not the nightly.  Ignore this one.

You're all good! Please don't hesitate if you find anything else! 😁


Takes 30s to a minute for tables to update

I can add things from a compendium no problem but to save the table with update takes 30s to a minute.
Using foundry on Raspbian on a pi 4 with 4GB ram.
Could it be a write speed issue on my SD card?
I look at the console output and it takes 30s to a minute for preUpdateRollTable to appear then the next steps go very fast.
So something is holding it up but I don't know what, could it be better-rolltables?

do you have performance issue without the mod? how big is the table?
in preUpdateRollTable i do very little.
The majority of the things happen when you open the rolltable view, the preUpdateRollTable call is mostly default foundry stuff and I just store 3 extra values for the mod.

I do have performance issues without the mod the mod might make them worse, not sure. It gets worse as the table grows in size. I started a new world with no tables or mods and the issue persists. It's very frustrating. Making tables is practically impossible.

I tried it on my desktop (transferred the world, new install of foundry) and the issue persists, though not as extreme.

you should ask in the foundry discord about the issue, it's probably related to foundry itself if the mod is off. I can't help you much with this

Hey, I figured it out, its because I was rolling on compendium entries.