OMP: Error #13: Assertion failure at z_Linux_util.cpp(2361).

When trying to use multithread, the following error occurs:
OMP: Hint Please submit a bug report with this message, compile and run commands used, and machine configuration info including native compiler and ope│··································
rating system versions. Faster response will be obtained by including all program sources. For information on submitting this issue, please see http://│··································
www.intel.com/software/products/support/.                                                                                │··································
OMP: Error #13: Assertion failure at z_Linux_util.cpp(2361).                                                                                │··································
OMP: Hint Please submit a bug report with this message, compile and run commands used, and machine configuration info including native compiler and ope│··································
rating system versions. Faster response will be obtained by including all program sources. For information on submitting this issue, please see http://│··································
www.intel.com/software/products/support/.                                                                                │··································
OMP: Error #13: Assertion failure at z_Linux_util.cpp(2361).                                                                                │··································
OMP: Hint Please submit a bug report with this message, compile and run commands used, and machine configuration info including native compiler and ope│··································
rating system versions. Faster response will be obtained by including all program sources. For information on submitting this issue, please see http://│··································
www.intel.com/software/products/support/.                                                                                │··································
OMP: Error #13: Assertion failure at z_Linux_util.cpp(2361).                                                                                │··································
OMP: Hint Please submit a bug report with this message, compile and run commands used, and machine configuration info including native compiler and ope│··································
rating system versions. Faster response will be obtained by including all program sources. For information on submitting this issue, please see http://│··································
www.intel.com/software/products/support/.                                                                                │··································
OMP: Error #13: Assertion failure at z_Linux_util.cpp(2361).                                                                                │··································
OMP: Hint Please submit a bug report with this message, compile and run commands used, and machine configuration info including native compiler and ope│··································
rating system versions. Faster response will be obtained by including all program sources. For information on submitting this issue, please see http://│··································
www.intel.com/software/products/support/.                                                                                │··································
OMP: Error #13: Assertion failure at z_Linux_util.cpp(2361).                                                                                │··································
OMP: Hint Please submit a bug report with this message, compile and run commands used, and machine configuration info including native compiler and ope│··································
rating system versions. Faster response will be obtained by including all program sources. For information on submitting this issue, please see http://│··································
www.intel.com/software/products/support/.                                                                                │··································
OMP: Error #13: Assertion failure at z_Linux_util.cpp(2361).                                                                                │··································
OMP: Hint Please submit a bug report with this message, compile and run commands used, and machine configuration info including native compiler and ope│··································
rating system versions. Faster response will be obtained by including all program sources. For information on submitting this issue, please see http://│··································
www.intel.com/software/products/support/.                                                                                │··································
OMP: Error #13: Assertion failure at z_Linux_util.cpp(2361).                                                                                │··································
OMP: Hint Please submit a bug report with this message, compile and run commands used, and machine configuration info including native compiler and ope│··································
rating system versions. Faster response will be obtained by including all program sources. For information on submitting this issue, please see http://│··································
www.intel.com/software/products/support/.                                                                                │··································
Traceback (most recent call last):                                                                                │··································
  File "tool/train.py", line 456, in <module>                                                                                │··································
    main()                                                                                │··································
  File "tool/train.py", line 106, in main                                                                                │··································
    mp.spawn(main_worker, nprocs=args.ngpus_per_node, args=(args.ngpus_per_node, args))                                                                │··································
  File "/home/lzx/.conda/envs/pytorchseg10/lib/python3.7/site-packages/torch/multiprocessing/spawn.py", line 171, in spawn                             │··································
    while not spawn_context.join():                                                                                │··································
  File "/home/lzx/.conda/envs/pytorchseg10/lib/python3.7/site-packages/torch/multiprocessing/spawn.py", line 107, in join                              │··································
    (error_index, name)                                                                                │··································
Exception: process 2 terminated with signal SIGABRT

This will happen when multiprocessing_distributed and use_apex are True.
Configuration details:
TRAIN:
  arch: psp
  layers: 101
  sync_bn: False  # adopt syncbn or not
  train_h: 585
  train_w: 585
  scale_min: 0.5  # minimum random scale
  scale_max: 2.0  # maximum random scale
  rotate_min: -10  # minimum random rotate
  rotate_max: 10  # maximum random rotate
  zoom_factor: 8  # zoom factor for final prediction during training, be in [1, 2, 4, 8]
  ignore_label: 255
  aux_weight: 0.4
  train_gpu: [0, 1, 2, 3, 4, 5, 6, 7]
  workers: 16  # data loader workers
  batch_size: 16  # batch size for training
  batch_size_val: 8  # batch size for validation during training, memory and speed tradeoff
  base_lr: 0.01
  epochs: 200
  start_epoch: 0
  new_epoch: 300  # for resume, how many new epochs to train
  power: 0.9
  momentum: 0.9
  weight_decay: 0.0001
  manual_seed: 520
  print_freq: 10
  save_freq: 1
  save_path: exp/cityscapes/pspnet101/model
  weight:  # path to initial weight (default: none)
  resume:  # path to latest checkpoint (default: none)
  evaluate: True # evaluate on validation set, extra gpu memory needed and small batch_size_val is recommend
Distributed:
  dist_url: tcp://<IP_ADDRESS>:6789
  dist_backend: 'nccl'
  multiprocessing_distributed: True
  world_size: 1
  rank: 0
  use_apex: True
  opt_level: 'O0'
  keep_batchnorm_fp32:
  loss_scale:

I have tried to do some search but they are not working.
Could you please give me some advice?
Thanks a lot!

When trying to use multithread, the following error occurs:
OMP: Hint Please submit a bug report with this message, compile and run commands used, and machine configuration info including native compiler and ope│··································
rating system versions. Faster response will be obtained by including all program sources. For information on submitting this issue, please see http://│··································
www.intel.com/software/products/support/.                                                                                │··································
OMP: Error #13: Assertion failure at z_Linux_util.cpp(2361).                                                                                │··································
OMP: Hint Please submit a bug report with this message, compile and run commands used, and machine configuration info including native compiler and ope│··································
rating system versions. Faster response will be obtained by including all program sources. For information on submitting this issue, please see http://│··································
www.intel.com/software/products/support/.                                                                                │··································
OMP: Error #13: Assertion failure at z_Linux_util.cpp(2361).                                                                                │··································
OMP: Hint Please submit a bug report with this message, compile and run commands used, and machine configuration info including native compiler and ope│··································
rating system versions. Faster response will be obtained by including all program sources. For information on submitting this issue, please see http://│··································
www.intel.com/software/products/support/.                                                                                │··································
OMP: Error #13: Assertion failure at z_Linux_util.cpp(2361).                                                                                │··································
OMP: Hint Please submit a bug report with this message, compile and run commands used, and machine configuration info including native compiler and ope│··································
rating system versions. Faster response will be obtained by including all program sources. For information on submitting this issue, please see http://│··································
www.intel.com/software/products/support/.                                                                                │··································
OMP: Error #13: Assertion failure at z_Linux_util.cpp(2361).                                                                                │··································
OMP: Hint Please submit a bug report with this message, compile and run commands used, and machine configuration info including native compiler and ope│··································
rating system versions. Faster response will be obtained by including all program sources. For information on submitting this issue, please see http://│··································
www.intel.com/software/products/support/.                                                                                │··································
OMP: Error #13: Assertion failure at z_Linux_util.cpp(2361).                                                                                │··································
OMP: Hint Please submit a bug report with this message, compile and run commands used, and machine configuration info including native compiler and ope│··································
rating system versions. Faster response will be obtained by including all program sources. For information on submitting this issue, please see http://│··································
www.intel.com/software/products/support/.                                                                                │··································
OMP: Error #13: Assertion failure at z_Linux_util.cpp(2361).                                                                                │··································
OMP: Hint Please submit a bug report with this message, compile and run commands used, and machine configuration info including native compiler and ope│··································
rating system versions. Faster response will be obtained by including all program sources. For information on submitting this issue, please see http://│··································
www.intel.com/software/products/support/.                                                                                │··································
OMP: Error #13: Assertion failure at z_Linux_util.cpp(2361).                                                                                │··································
OMP: Hint Please submit a bug report with this message, compile and run commands used, and machine configuration info including native compiler and ope│··································
rating system versions. Faster response will be obtained by including all program sources. For information on submitting this issue, please see http://│··································
www.intel.com/software/products/support/.                                                                                │··································
Traceback (most recent call last):                                                                                │··································
  File "tool/train.py", line 456, in <module>                                                                                │··································
    main()                                                                                │··································
  File "tool/train.py", line 106, in main                                                                                │··································
    mp.spawn(main_worker, nprocs=args.ngpus_per_node, args=(args.ngpus_per_node, args))                                                                │··································
  File "/home/lzx/.conda/envs/pytorchseg10/lib/python3.7/site-packages/torch/multiprocessing/spawn.py", line 171, in spawn                             │··································
    while not spawn_context.join():                                                                                │··································
  File "/home/lzx/.conda/envs/pytorchseg10/lib/python3.7/site-packages/torch/multiprocessing/spawn.py", line 107, in join                              │··································
    (error_index, name)                                                                                │··································
Exception: process 2 terminated with signal SIGABRT

This will happen when multiprocessing_distributed and use_apex are True.
Configuration details:
TRAIN:
  arch: psp
  layers: 101
  sync_bn: False  # adopt syncbn or not
  train_h: 585
  train_w: 585
  scale_min: 0.5  # minimum random scale
  scale_max: 2.0  # maximum random scale
  rotate_min: -10  # minimum random rotate
  rotate_max: 10  # maximum random rotate
  zoom_factor: 8  # zoom factor for final prediction during training, be in [1, 2, 4, 8]
  ignore_label: 255
  aux_weight: 0.4
  train_gpu: [0, 1, 2, 3, 4, 5, 6, 7]
  workers: 16  # data loader workers
  batch_size: 16  # batch size for training
  batch_size_val: 8  # batch size for validation during training, memory and speed tradeoff
  base_lr: 0.01
  epochs: 200
  start_epoch: 0
  new_epoch: 300  # for resume, how many new epochs to train
  power: 0.9
  momentum: 0.9
  weight_decay: 0.0001
  manual_seed: 520
  print_freq: 10
  save_freq: 1
  save_path: exp/cityscapes/pspnet101/model
  weight:  # path to initial weight (default: none)
  resume:  # path to latest checkpoint (default: none)
  evaluate: True # evaluate on validation set, extra gpu memory needed and small batch_size_val is recommend
Distributed:
  dist_url: tcp://<IP_ADDRESS>:6789
  dist_backend: 'nccl'
  multiprocessing_distributed: True
  world_size: 1
  rank: 0
  use_apex: True
  opt_level: 'O0'
  keep_batchnorm_fp32:
  loss_scale:

I have tried to do some search but they are not working.
Could you please give me some advice?
Thanks a lot!

Hi, are you following the recommend installing steps of apex?
https://github.com/NVIDIA/apex
$ git clone https://github.com/NVIDIA/apex
$ cd apex
$ pip install -v --no-cache-dir --global-option="--cpp_ext" --global-option="--cuda_ext" ./

git clone https://github.com/NVIDIA/apex.git && cd apex && pip install -v --no-cache-dir --global-option="--cpp_ext" --global-option="--cuda_ext" .

Thanks for your reply, I have installed following the same command as you.
And I have checked the following matters:
Please check torch._C._GLIBCXX_USE_CXX11_ABI is False at first.

$ python
>>> import torch
>>> torch._C._GLIBCXX_USE_CXX11_ABI
False

Still having this error.
I have run your code with multi-thread function open successfully on the other machine, and this machine newly bought.
Maybe my apex version is too new?
Thanks for your reply!!

This configuration has no bug (but slow):
Distributed:
  dist_url: tcp://<IP_ADDRESS>:6789
  dist_backend: 'nccl'
  multiprocessing_distributed: False
  world_size: 1
  rank: 0
  use_apex: True
  opt_level: 'O0'
  keep_batchnorm_fp32:
  loss_scale:

I have searched for many documents but never seen this bug...
The most related one says that it's the problem of the intel cpu...
It's hard to believe that.
BTW, the configuration of this machine:

CPU: Intel Xeon Silver 4110
GPU: 8 x 2080TI

Could you please tell me your apex version? THX
@hszhao

It's not related with apex version.
The solution is add export KMP_INIT_AT_FORK=FALSE to train.sh.
Such as:
#!/bin/sh
PARTITION=gpu
PYTHON=python

dataset=$1
exp_name=$2
exp_dir=exp/${dataset}/${exp_name}
model_dir=${exp_dir}/model
result_dir=${exp_dir}/result
config=config/${dataset}/${dataset}_${exp_name}.yaml
now=$(date +"%Y%m%d_%H%M%S")

mkdir -p ${model_dir} ${result_dir}
cp tool/train.sh tool/train.py ${config} ${exp_dir}

export PYTHONPATH=./
export KMP_INIT_AT_FORK=FALSE
#sbatch -p $PARTITION --gres=gpu:8 -c16 --job-name=train \
$PYTHON -u tool/train.py \
  --config=${config} \
  2>&1 | tee ${model_dir}/train-$now.log

Reference:
https://github.com/ContinuumIO/anaconda-issues/issues/11294
And the training speed is really very fast. The predicted training time is about 8 hours for psp101 on cityscapes dataset.
Thanks for your code again, it's really helpful!


GVRVideoSceneObject::new GVRVideoSceneObject(GVRContext, float, float, MediaPlayer, int) - Error message

The message when passing an invalid videoType in GVRVideoSceneObject creation could be more user friendly.
public void testSetVideoTypeInvalid() {
        MediaPlayer mediaPlayer = new MediaPlayer();

        try {
            new GVRVideoSceneObject(TestDefaultGVRViewManager.mGVRContext, 100f, 100f, mediaPlayer, 320);

        } catch (IllegalArgumentException e) {
            assertEquals(e.getMessage(), "IllegalArgumentException for videoType. Types supported: " +
                    "GVRVideoSceneObject.GVRVideoType.MONO, " +
                    "GVRVideoSceneObject.GVRVideoType.HORIZONTAL_STEREO, " +
                    "GVRVideoSceneObject.GVRVideoType.VERTICAL_STEREO");
        }
}

It does throw an IllegalArgumentException and the docs do say that that means "an invalid videoType parameter" - that sure seems like enough, to me.
Beyond that, your proposed exception message seems wrong, to me: it's going to show the decimal values of the constants, not their symbolic names.


config to remove pre-encoder bias

Following SAELens, AutoEncoder config is given a boolean apply_b_dec_to_input, that decides whether decoder bias should be subtracted from the input.
When loading a model trained with SAELens, this variable is read from the SAELens model config. The default value is set to True.
I have checked that the code passes all the tests with make check-all.

lgtm, thanks!

Unfortunately this hasn't worked - see link. Do you think you could sort this out by fixing the formatting?

I think I can sort it out. I will work on it later today. Thanks!

I tried replicating this error on my computer, but I had no success.
poetry run ruff format --check passed all tests, returning 9 files already formatted.
Perhaps there is a subtle difference between GitHub CI configurations and my installations, even though I couldn't see any differences with a quick look. I will dig deeper into this over the weekend.
If I need to do anything more urgently, please let me know.
Thank you!


feat: alpha 6

Codecov Report
Base: 72.99% // Head: 73.93% // Increases project coverage by +0.93% :tada:

Coverage data is based on head (f037de1) compared to base (277db01).
Patch coverage: 76.74% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #30      +/-   ##
==========================================
+ Coverage   72.99%   73.93%   +0.93%
==========================================
  Files          21       21
  Lines        1459     1500      +41
==========================================
+ Hits         1065     1109      +44
+ Misses        394      391       -3

Impacted Files
Coverage Δ

src/unit/domain.rs
70.31% <76.74%> (+17.43%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Loading indicator

Implement a loading indicator for asynchronous tasks, just like how the Android version does.

Please don't make it "like in Android."
The one in the Android app displays a WHOLE WHITE PAGE with an indicator on it in between loads. It's jarring for apps that are not mostly white, and it makes apps feel like browsers from 20+ years ago where the whole page was blanked and redisplayed.
A transparent indicator (with maybe some translucency to minimally occlude the current page), would be better.
In my apps I already implemented a default background to match the rest of the app so that the jarring whole-blank-page for two to 5 seconds (in the case of access via data network) does not make it look so bad.

@cpg yes will probably use some widely used nice looking library. On Android I honestly couldn't find any non-obtrusive loading indicator library. The official Android one that I ended up choosing was the best looking of them all actually.
However on iOS.... it's pretty hard to find bad looking UI libraries haha

Closed with https://github.com/Jasonette/JASONETTE-iOS/pull/87


Feat:Add a blog

Describe the feature
I want to add a blog related to effect of smoking on body.Can you assign this task to me?
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'23 contributor
[X] I want to work on this issue

@MonalikaPatnaik Can you assign this task to me?


Swift 3 Update

I updated whole project to Swift 3 which is required as of Xcode 8.3 (I
guess)

This is Relese build from latest Swift version 68a9c94:
Goofy.zip
Ignore Sparkle error about signing and available update. AFAIK this version worked well.

Alright thanks!

@arainot You can now also use mine new Swift 4 fork: https://github.com/hrubymar10/goofy_swift

@hrubymar10 Ok thanks, but do you have built versions on it? I can't build the app on my machine for some reason


easy download feature request

when playing a song from the email section (without the emulator installed, by the way) a link is generated in the network section when inspecting element. if you open the link in a new tab and save the page you can save the entire song in an mp3 with all the stems. hopefully this would be a simple feature to add to make every song download from a single button press

i know this and it's a planned feature: https://github.com/krystalgamer/stem-player-emulator/issues/20
With the album stems it was easy to download because the track was downloaded in advance, I could grab the buffer and download it.
Here as you soon you press play there's a bunch of requests being fired to fill the metadata for the tracks and then the track you've chosen is played via MediaSession. As you can see it does by ranged downloads which is great to save bandwidth but is annoying if you want the full track.
The feature is planned I'v been just thinking the best way to implement it that is update prone.

feature added, update the emulator to use the "Download on play" feature :)


TestAuthorization_Audit does not check logs

Bug Description
While working on https://github.com/istio/istio/pull/37914, it appears that the audit test doesn't really test the AUDIT function properly. To test auditing, the logs would have to be checked to confirm that a given request either was or was not logged.
Version
master (head)

Additional Information
No response

See the comment: TestAuthorization_Audit tests that the AUDIT action does not impact allowing or denying a request, TestAuthorization_Audit explicitly does not cover the logging part.
The logging part is checked in the telemetry test: https://github.com/istio/istio/blob/1ade7ec2e569c2302d90a5f6b2bd86872e2314ad/tests/integration/telemetry/stackdriver/stackdriver_filter_audit_test.go.

See the comment: TestAuthorization_Audit tests that the AUDIT action does not impact allowing or denying a request, TestAuthorization_Audit explicitly does not cover the logging part.

@yangminzhu then the audit test serves no purpose AFAICT. Should it just be removed?

No, the test is to check the audit action does NOT impact the allow/deny behavior, it applies different combinations of the audit action and makes sure it does NOT change the final access control decision.

@yangminzhu a negative test is effectively useless. You might as well test that it also doesn't re-route traffic ... or pour you a cup of tea. Since you already are testing the audit function with telemetry tests (do you have a link, BTW?), I strongly suggest we get rid of this test since it's not actually testing the function it's supposed to be testing.

@nmittler It is a negative test but I do not think it's useless. It covers corner cases when combining audit actions with other actions (allow/deny) with different workload selectors and paths. The test makes sure the AUDIT action won't negatively impact (break) the ALLOW/DENY actions.
This is important because the AUDIT and  ALLOW/DENY actions shares a significant amount of common code path/state/logic to generate the Envoy config using the same RBAC filter. A bug in the common code path for RBAC filter generation could cause very different behaviors, for example, An AUDIT action might cause the RBAC config to be generated in a way such that the ALLOW action to always allow (never denies).
We do NOT need such negative tests for authorization policy and re-routing traffic because they do not share much common code path/state/logic in terms of the Envoy config generation (re-routing does not use RBAC filter at all).
Please see the telemetry test link in above comment, it tests a much simple case (there is only AUDIT action, no other actions) and checks the stackdriver log to verify the audit result.

@yangminzhu understand ... however, do we have unit tests for this? This seems like the sort of thing better tested thoroughly by unit tests rather than an e2e test.

Please see the telemetry test link in above comment, it tests a much simple case (there is only AUDIT action, no other actions) and checks the stackdriver log to verify the audit result.

If that test is too simple to fully test AUDIT, should we just expand that one, rather than having 2 separate audit tests?

Re-opening, since I don't think the central issue here is resolved.

We do have unit tests but it is not enough, it does not cover the runtime behavior so we still need the real e2e tests.
The 2 tests are checking different aspects of the AUDIT action so they are not duplicate. We put one test in the telemetry test suite to reuse the common code and support for the stackdriver logging backend, and I think it's better to split the tests like this because the AUDIT feature supports different logging backend, stackdriver is just one example of supported backend.
The authz test suite checks the basic AUDIT feature is working and the extra telemetry test checks the logging part is working with the stackdriver backend. In the sure, if we support another logging backend, we can just add it as a new test in the telemetry test suite without duplicating the basic AUDIT feature test.

@yangminzhu could you point me to the logic that is covered by these e2e tests but is not covered by either unit tests or the telemetry e2e tests?

@nmittler
it's for the end-to-end and runtime behavior coverage, make sure the config is distributed to Envoy correctly and the RBAC filter also enforces it correctly by sending real request.
Without the end-to-end and runtime coverage, we could convert almost all e2e tests to unit tests by just checking the Envoy generated config statically. The risk is even if we are generating the right Envoy config, it might not work due to a lot reasons (e.g. generated but not distributed correctly to Envoy or Envoy not enforcing it correctly).

@yangminzhu just coming back to this ...

We put one test in the telemetry test suite to reuse the common code and support for the stackdriver logging backend, and I think it's better to split the tests like this because the AUDIT feature supports different logging backend, stackdriver is just one example of supported backend.

Are you saying that telemetry only tests against SD today?
@douglas-reid do you have any insight into the current audit testing in the telemetry tests?

@nmittler The current audit tests are SD-only, afaict. they involve setting a policy with three different audit rules and validating log entries are generated. The amount of shared stackdriver code is minimal, and looks to only use exported functions from the package.
e2e telemetry tests are funky, in that, ultimately, they are a testing a bunch of other features by their very nature -- so deciding what goes belongs within them is a bit of an art. However, it feels difficult for me to separate AUDIT into a non-telemetry and a telemetry component. What is AUDIT if it doesn't generate an observable artifact?
I think we should probably refactor the Audit tests. I understand the idea behind the split. However, it would make sense, to me at least, to have them live alongside the security tests and have the audit behavior checked there -- especially if audit logs can go to more than just Google Cloud Logging. I guess that's because I'd rather not have the only test for the full Auditing behavior live in the telemetry/ test hierarchy.
The feature for the existing Audit telemetry test is currently: observability.telemetry.stackdriver. That feels wrong because if something about Audit policy behavior is broken, it will only show up as "stackdriver" being broken.  The feature itself feels like it should be something like: security.authorization.audit -- with gcp cloud logging as the implementation detail of the test. If there are other exports (like stderr), it seems like those should be added as well.

@douglas-reid

That feels wrong because if something about Audit policy behavior is broken, it will only show up as "stackdriver" being broken. The feature itself feels like it should be something like: security.authorization.audit -- with gcp cloud logging as the implementation detail of the test. If there are other exports (like stderr), it seems like those should be added as well.

+1 ... that sounds right to me. I had asked a while (years?) back to have a telemetry/logs abstraction so that tests could be written that were agnostic to the particular implementation. Is any/all of that abstraction in place? If not, maybe we should prioritize that work?

The feature for the existing Audit telemetry test is currently: observability.telemetry.stackdriver. That feels wrong because if something about Audit policy behavior is broken, it will only show up as "stackdriver" being broken.

yeah I think we can update the test name to be more accurate like security.authorization.audit.
@liwenhao0810 please take a look, I think one way is to move the stackdriver_filter_audit_test.go to the security folder and consolidate with the TestAuthorization_Audit.

@yangminzhu +1 to merging the tests. Honestly I don't care where it lives, just so long as there's only one test that does everything.
@liwenhao0810 will you be working on this?

After looking at comments history, agreed with to merge and have the test in the security to fully test the functionalities.
I can take a look and see what I could help with on this.


BigR[bigr.connect]: Required library 'BigRResultSet' could not be found

Getting following error running BigR example. Where should lib path be set?
:Example
running
  '/Library/Frameworks/R.framework/Versions/3.2/Resources/bin/R --slave --no-restore --file=/Users/pierreregazzoni/biginsight-examples/examples/BigR/example.r'

Loading required package: rJava
Loading required package: methods
Error: BigR[bigr.connect]: Required library 'BigRResultSet' could not be found.
Execution halted
:Example FAILED

The lib dir is set in the build.gradle file:
environment 'libdir', "${projectDir}/lib"

https://github.com/snowch/biginsight-examples/blob/master/examples/BigR/build.gradle#L59
https://github.com/snowch/biginsight-examples/blob/master/examples/BigR/build.gradle#L73
Would you be able to test on a pristine virtual environment so that I can see if the issue is with the cluster or your client machine?

install virtualbox
install vagrant
open a terminal
ensure you are in the top level directory that contains Vagrantfile
run vagrant up

Yeah I saw libdir in build.gradle but somehow BigRResult jar is not getting picked up. Will try a clean report. Not familiar with vagrant but i assume should be straight forward.

test on ubuntu (via vagrant) worked:
==> default: Running BigX tests
==> default: Test passed  ./examples/BigR
so need to figure out what is diff on my MBP.

@pregazzoni
Hi pregazzoni, I have the same issue in my MBP. Do you have any idea how to fix that? Thanks!

@zhaol2046 can you do a git pull and try running:
cd examples/BigR
./gradlew clean
./gradlew Connect -PdebugBigR 2>&1 > debug.output

Can you add a comment with debug.output attached?

@pregazzoni @zhaol2046  it's a long shot, but does adding this before library(bigr) in connect.r help:
jars <- list.files(pattern="\\.jar$", ignore.case=TRUE, recursive=TRUE, path="lib/")
for (j in jars) {
    .jaddClassPath(j)
}

ensure you do a git pull to get the latest updates

@snowch I run the following commends in R and get the same error

jars <- list.files(pattern="\.jar$", ignore.case=TRUE, recursive=TRUE, path="lib/")
for (j in jars) {

.jaddClassPath(j)

}

library(bigr)
Loading required package: rJava
bigr.connect(host="ehaasp-577-master-3.bi.services.bluemix.net", user="user10", password="temp4now", ssl = TRUE, trustStorePath = "/tmp/alex-truststore.jks", trustStorePassword = "mypassword", keyManager = "SunX509")
Error: BigR[bigr.connect]: Required library 'BigRResultSet' could not be found.

@snowch The following is what I got after running ./gradlew clean and ./gradlew Connect -PdebugBigR 2>&1 > debug.output
`FAILURE: Build failed with an exception.

What went wrong:
Task 'Connect' not found in root project 'biginsight-examples'.

Try:
Run gradlew tasks to get a list of available tasks. Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.`

I attach a screenshot of "debug.ouput" as follows...

@zhaol2046  You need to change into the BigR example directory before running ./gradlew ...

See also: http://stackoverflow.com/questions/37954159/error-bigrbigr-connect-required-library-bigrresultset-could-not-be-found which I just posted.

@snowch Thanks, waiting for solutions..

I've created a new target which will create a complete r script for you:
cd examples/BigR
./gradlew GenerateSampleScript

Then open the sample script `connect_template.r' in R or RStudio and run it manually.

@snowch Thanks for your efforts Chris. All the lines work fine except the bigr.connect...still get the same error...
`> connected <- bigr.connect(

host = hostname,

user = username,

password = password,

ssl = TRUE,

trustStorePath = paste(projdir, "/truststore.jks", sep=""),

trustStorePassword = "mypassword",

keyManager = "SunX509"

)
Error: BigR[bigr.connect]: Required library 'BigRResultSet' could not be found.`

BTW testing with new IOP version and don't see this issue anymore on my MBP ...
:Connect
running
  '/Library/Frameworks/R.framework/Versions/3.2/Resources/bin/R --slave --no-restore --vanilla --file=/Users/pierreregazzoni/biginsight-examples/examples/BigR/connect.r'

Loading required package: rJava
Loading required package: methods
[1] "Successfully connected to BigR"
:KMeans
running

Ah, interesting.  Thanks @pregazzoni

@zhaol2046  you could try the virtualmachine that is included with this project.  The steps to try it are as follows:

install virtualbox
install vagrant
open a terminal
ensure you are in the top level directory that contains Vagrantfile
run vagrant up on your client machine
run vagrant ssh -c "hostname -I | cut -d' ' -f2-"
open a web browser using the IP address from the previous step and the port 8787 - http://youripaddress:8787
login using username: vagrant, password: vagrant
in rstudio file navigator, open biginsight-examples/examples/BigR/connect_template.r
execute this file in rstudio to connect to your cluster

cc @pregazzoni - rsudio server added to the vagrant project ^


add supported environments to Enterprise documentation

add a table of all supported environments to Enterprise documentation
There are mentions in the installation instructions, but nothing comprehensive.

+1


Repl: If we don't have a TTY, don't use Readline

The failure of this test on OpenBSD was due to some differences in Readline/TTY handling which caused Readline to not echo the input back to the output when not on a TTY.  I spent some time trying to figure out why and how to force the echoing by using a PTY in ReplWrapper, but I couldn't get it to work properly.
In the end, I'm not sure it's that useful to test Readline's behavior anyway, so maybe the REPL should just print its output when STDOUT isn't a TTY, and the test can just check for the expected output.
🎄 🎁 🎅
Finished in 496.087667s, 0.4334 runs/s, 0.5826 assertions/s.

215 runs, 289 assertions, 0 failures, 0 errors, 54 skips

OMG I didn't see this PR until just now. I actually tackled this in f6a94701f8ef60f2c2ad7871cf45136bbb4429ce, but took a slightly different approach. I think I like your work better, so I'll be merging this shortly. Thanks!


Restructure Lightning Docs

🚀 Feature
Restructure Lightning documentation to make it easier to read, find, and use.
Motivation
Lightning has grown a lot, and so did the docs. We should do a massive clean up.

Can you please links to github source code?
For example in here: https://pytorch-lightning.readthedocs.io/en/latest/extensions/generated/pytorch_lightning.callbacks.Callback.html#pytorch_lightning.callbacks.Callback
I cannot jump to Github page exploring the source code. I just jump to another docs page.

@oplatek Jumping to the source code in the docs (which is the same as the PyTorch docs) isn't enough for you? e.g. https://pytorch-lightning.readthedocs.io/en/latest/_modules/pytorch_lightning/callbacks/base.html#Callback

@akihironitta do not take it as a criticism ... it is a nice feature for sure! Just want more always :)
However, linking directly to GitHub would be really awesome for several use-cases I use very frequently:

exploring history on GitHub and comparing it with my version to debug the differences
GitHub supports jumps to references / jump to definitions - one can use a web browser almost like an IDE.

When I am thinking about it would be enough to put a single link to a python module/file on GitHub from the top of each page in the docs:
e.g. for https://pytorch-lightning.readthedocs.io/en/latest/_modules/pytorch_lightning/callbacks/base.html
put a link to https://github.com/PyTorchLightning/pytorch-lightning/blob/master/pytorch_lightning/callbacks/base.py
I always search for the Github code anyway based on the docs.


Remove callback annotations

Remove callback annotations from recipes, as it requires custom code in SRO and right now there arent any. This is currently dead code.
Callbacks may be superseded by helm hooks.

/cc @qbarrand @pmtk @yevgeny-shnaidman @enriquebelarte

/lgtm


Enforce AWS_PROFILE choices on publish-draft-services

https://trello.com/c/ui2WdVFw/148-05-make-publish-draft-services-jenkins-job-dos-friendly
I did a quick local test for DOS, and while the AWS_PROFILE isn't needed for that framework, if a malformed value is provided (e.g. bananas-infrastructure) then the script will fail. So I've enforced the available values as choices on the job and clarified that either value can be used for DOS.

Does an empty value cause the script to crash? Then we could have the empty string as the first choice?

Does an empty value cause the script to crash for DOS frameworks? Then we could have the empty string as the first choice?

We have to put something, otherwise we get: The config profile () could not be found


[BUG] Enum values with 0 are ignored in writable properties

Using a PnP model using an enum in a writable property (below one example).
When updating the writable property from IoT Explorer, the value with 0 is not sent in the payload. (all other values work).
{
  "@context": "dtmi:dtdl:context;2",
  "@id": "dtmi:rido:settings;1",
  "@type": "Interface",
  "contents": [
    {
      "@type": "Component",
      "name": "Settings",
      "schema": {
        "@type": "Interface",
        "@id": "dtmi:rido:settings;1",
        "contents": [
          {
            "@type": "Property",
            "name": "DeviceHealthTelemetryConfiguration",
            "schema": {
              "@type": "Enum",
              "valueSchema": "integer",
              "enumValues": [
                {
                  "name": "None",
                  "enumValue": 0
                },
                {
                  "name": "Required",
                  "enumValue": 1
                },
                {
                  "name": "Optional",
                  "enumValue": 2
                }
              ]
            },
            "writable": true
          }
        ]
      }
    }
  ]
}

Hi @rido-min
We are aware of this issue, which has exist for a long time.
Unfortunately, javascript treats 0 as false, and there is no yet a good way to fix it.

Thanks @YingXue, how can I help to find a valid workaround? Can you point to the code where JS converts the 0 to false?

Hi @rido-min
A possible workaround is, since Enum takes in both integer and string type in DTDL, define "@type": "Enum", "valueSchema": "string", and provide Enum value as '0', '1' and so on.
From the code side, this is what I've been tracking down for so long but have not get it working properly: https://github.com/Azure/azure-iot-explorer/blob/master/src/app/devices/shared/components/dataForm.tsx#L127

we cannot ask users to use valueSchema: string when they intend to use an int .  This might be a bug in the json schema form library. (wondering how Central solved this problem).

Fixed released in https://github.com/Azure/azure-iot-explorer/releases/tag/v0.15.8. Closing.


Events passed to enhance are not correctly destroyed

[✓] Before posting an issue, read the FAQ and search the previous issues.

Description
When events are added to use:enhance, if the form element is created and destroyed multiple times (for example, the form is in a sheet or dialog or, even simpler, in an if like in the MRE below), the events are pushed multiple times to formEvents but never destroyed.
MRE
In that example, if you toggle the form multiple times, you can see that onUpdated is called multiple times
Possible solution
Instead of returning kitEnhance here :
https://github.com/ciscoheat/sveltekit-superforms/blob/1b7a1585c2661034d71d6f1d6ed39c3d992f5eee/src/lib/client/superForm.ts#L1605
it could be something like this :
const enhance = kitEnhance("...");
return {
  destroy: () => {
    // same as in onDestroy()
    for (const events of Object.values(formEvents)) {
      events.length = 0;
    }
    // call native enhance destroy
    enhance.destroy();
  }
}

What are your thoughts?
By the way, thank you again for this awesome library.

Thank you, will take a look and hopefully it will be included in the next release. Glad you like Superforms. :)

I've added a fix for the next release. Do you have any good reason not to put the event(s) directly in the options when calling superForm? I'm considering deprecating this "add events in enhance" feature, as I have never found a really good use case for it.

I'm not sure I understand still, since onUpdated looks like a simple toast notification (maybe you've simplified it), what prevents you from adding it directly?
let sfUpsert = superForm(data.svUpsert, {
  validators: zodClient(projectUpsertSchema),
  onUpdated: () => toast.success("...")
})

As you said , I simplified it 🙂. In fact, I use it for multiple interactions on the generic page (closing the sheet, updating some data, etc...). But even if it was a simple toast, I want the toast to be on the generic page as I don't want, if I have 10 collections, to define the same behavior 10 times (hence the generic crud component 🙂).

Right, but if you use it in multiple locations, it will append the events to the others as well, and there are internal state that may cause problems too. That's why I'm not sure it's the best to keep. It's was a very early feature.


gc: Add --time flag to dvc gc and dvc exp gc

related to PR: https://github.com/iterative/dvc/pull/7970

You may disregard these recommendations if you used the Edit on GitHub button from dvc.org to improve a doc in place.

❗ Please read the guidelines in the Contributing to the Documentation list if you make any substantial changes to the documentation or JS engine.
🐛 Please make sure to mention Fix #issue (if applicable) in the description of the PR. This causes GitHub to close it automatically when the PR is merged.
Please choose to allow us to edit your branch when creating the PR.
Thank you for the contribution - we'll try to review it as soon as possible. 🙏

Thanks!


Replace starscream with URLSessionWebSocketTask

@IceTrae I squashed your changes into #3 and merged. I’ll release that as 0.0.4.


[Redesign] Add Dropdown Menu

Desktop
Closed Dropdown

Opened Dropdown

Mobile
Closed Dropdown

Opened Dropdown

NOTE: There is a known accessibility issue with the link that opens the dropdown: focusing this link will not have an outline. This is caused by line 25-27 of dropdowns.less, and apparently, this is necessary for mouse users.
For more information, see this issue.

When using the dropdown it feels like it disappears too easily. For example, if I click any non-link space in the dropdown, e.g. the profile picture, the dropdown disappears. I think it should only disappear if someone clicks outside of the dropdown.
Related to this is a more minor issue. When you click one of the links in the dropdown, the dropdown immediately collapses. I feel lilke it should stay open until the page navigates away. This is important so if someone accidentally clicks the wrong dropdown open, they should be able to click a different one until the point in time that the page navigate completes (this would make it consistent with other anchor clicks).

:bell: Fixed merge conflicts and addressed feedback.


Go 1.21

Ⅰ. Describe what this PR does
Ⅱ. Does this pull request fix one issue?

fixes #XXXX
Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (1c7e395) 64.40% compared to head (2fff72d) 64.40%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master       #7   +/-   ##
=======================================
  Coverage   64.40%   64.40%
=======================================
  Files         474      474
  Lines       28336    28336
=======================================
  Hits        18249    18249
  Misses       7913     7913
  Partials     2174     2174

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


Don't log a trace if EventWriter::send_batch is empty

Objective
Fix #5026.
Solution
Only make a trace! log if the event count changed.

Changelog
Changed: EventWriter::send_batch will only log a TRACE level log if the batch is non-empty.

bors r+


libacl.h is required for installation but missing in documentation

Required information
When trying to build iceoryx2 with cargo, bindgen requires the libacl.h headers in linux. So we should introduce a feature flag that enable acl explicitly and describe in the readme how to install the library.

This was fixed in #43


Create Blank Module Diagram: Memory

Define the inputs and outputs needed by the memory controller for the top level design, create blank verilog stub, and create blank drawio representation of module.

Finished with stubs and diagrams, last step is to create wiki with definitions for IO


Getting artefacts when using the portal gun with sildur shader

According to your testing, does the issue occur with ONLY Portal Gun mod and Immersive Portals mod and Farbic API?
Yes
Describe the issue
The Portal itself works fine, no issues with my shader so far. When placing a portal with the gun it looks like this (TAA and motion blur are off):

I'm using MC 1.19.3 with fabric 0.14.19 and the latest version of both mods:
immersive-portals-2.5.4-mc1.19.3-fabric.jar
portalgun-5.0.0-mc1.19.3-fabric.jar
Post the log here
No response

Disable the motion blur, it doesn't work with Immersive Portals properly

Aus = Off - It's already disabled!

Do these artifacts appear only when you're looking at a portal?

Yes, if i walk away and the portal gets out of sight, the artifacts are gone!

Sorry, I don't think I know how to fix it then

The artifacts seems to be the light sources which the other portal sees.

You are using a resourcepack so I don't know what thing is in the portal. A horse?

You are using a resourcepack so I don't know what thing is in the portal. A horse?

Looks like an Iron Golem to me

It's a golem ;) I'm using the PureBDcraft 128x Texturepack.

As I tested, ImmPtl with sildurs vibrant shader is kind of broken. It's recommended to use BSL shader for now.

It looks quite different with the BSL shader, but i think it will be normal after several days ;) The artifacts are now completly gone so far.


Syntax hilighting view is different than example picture at overview page

How can I make it like example?
Sorry for pour English.

What color theme for Visual Code are you using?
I noticed that when I use "Dark (Visual Studio)" it looks like what you are seeing , but when I select "Dark+ (default dark)" then it does work and looks like the example I provided.

You're right.
My theme was Dark (Visual Studio).
I changed theme to default.
Thanks @BattleBas .


HIVE-28564: AssertionError for jdbc queries when JDBCExpandExpression…

…sRule produces non flat Filter conditions

What changes were proposed in this pull request?

https://issues.apache.org/jira/browse/HIVE-28564
Simplify filter/join condition in JDBCExpandExpressionsRule so that they are flat
Why are the changes needed?

Without these changes, sometimes the new conditions are not flat and we get an AssertionError as shown in the ticket.
Does this PR introduce any user-facing change?

No
Is the change a dependency upgrade?

No
How was this patch tested?

mvn test -pl itests/qtest  -Pitests -Dtest=TestMiniLlapLocalCliDriver -Dtest.output.overwrite=true -Dqfile=jdbc_non_flat_filter_condition.q

Hi @zabetak, could you please review this?


Update ForgeRock_CEF.json

now that we have the ForgeRock parser at https://github.com/Azure/Azure-Sentinel/blob/master/Parsers/ForgeRockParser.txt, we've added a 3rd sample query that leverages it
Fixes #
Proposed Changes

I'm retracting this PR given it seems opening it delayed us in the publishing queue


Design menu contribution system

We need to add a way to add to the menus in Paranext. It would be best to create a static data structure for extensions to list what menu additions they want in their manifest.json in order to support lazy loading extensions (#104). For now, this could be a simple design similar to VSCode's menu contributions design but significantly dumbed down.
Essentially, people would define menu items in their manifest.json files which would inform Paranext of a few details:

Which menu
Submenu(s)
Display name
Command to run
[Later?] Icon
[Later] Some kind of context in which to run

The extension host would aggregate all these menu items and send them to the renderer to create its menu with (maybe we could have a data provider on the extension host or something?).
The renderer would build out the menus with this information. When a user clicks a menu item, the renderer fires off that command.
Menu design doc

I believe Eric Gamma (one of the Gang of Four) really went to town using Design Patterns on VS Code's menu system. My guess would be the Composite pattern for the structure and the Command pattern when you click an item. Here is what ChatGPT had to say:

The Composite pattern is a structural design pattern that allows you to treat individual objects and groups of objects uniformly. In the context of menus, it allows you to represent menu items and submenus in a hierarchical structure.
Here's how the Composite pattern can be applied to menus:
Component: Define an abstract base class or interface called Component that represents both individual menu items and submenus. It should provide common operations such as display() for rendering the menu item/submenu and add() and remove() for adding or removing child components.
Leaf: Implement the Component interface for individual menu items. These are the basic building blocks of the menu and cannot have any children. They provide the specific functionality for each menu item, such as executing a command when selected.
Composite: Implement the Component interface for submenus. These are containers that can hold multiple menu items and submenus. The composite maintains a list of child components and delegates the display(), add(), and remove() operations to its children.
By using the Composite pattern, you can create nested menus with varying levels of complexity. Each menu item can be treated uniformly, regardless of whether it is an individual item or a submenu. This pattern promotes code reusability, flexibility, and the ability to add new menu items or submenus without modifying the existing code.
It's worth mentioning that this is just one possible design pattern for menus, and depending on your specific requirements, other patterns such as the Command pattern or the Builder pattern might also be applicable. The choice of pattern depends on the specific needs and complexity of your menu system.

Drive-by comment:
It may be worth thinking about how we decide to allow users to modify menus, specifically in Paratext.

Will all menus be customizable?
Will some menus be immutable? (because it's hard to train people to use a tool if half the classroom's menus are different to the rest).
Will almost all menus be immutable and there is a "plugins" menu which is a free for all playground?

I can imagine it being really annoying for someone who develops a "Super Find" plugin to find they can't put it in the Edit menu (because Find is almost always in the Edit menu). Likewise I can imagine it being really annoying for someone trying to support a user who has installed several plugins that have changed the whole landscape of the menus in Paratext. Food for thought, hopefully!

Another thing we need to consider is localization and how that works with defining where menus/sub menus should be.

From Ian:

if someone has localized the vanilla Paratext UI and someone adds a plugin, we'd either need to say at plugin install "This plugin isn't localized in Telegu it could look heckin' weird in your UI".

Ian suggested we add a warning when installing a plugin that isn't localized in your language.

After a few moments of thought, I'm thinking more along the lines of:

Make it clear to a user what languages any plugin is available in when they're browsing plugins.
Make "localization language" part of the filtering for the plugin browser
... Warnings ought to be preventable here.

Incidentally, this is another reason that it would be great to be able to localize in-situ (maybe with some machine translation assistance, and maybe also report localizations back to the developers of Paratext/plugins). That way people might download a plugin, knowing that they may need to localize it, but in doing so they help other people working in their language.

Proposal:

The core platform and all extensions will provide JSON documents that are combined into a single document.  The core platform's document has highest priority (i.e., is loaded first).  Any conflicts between documents should be resolved as best as possible (e.g., if some extension tries to create a duplicate menu item that already exists, that extension fails to load).
The final JSON document must conform to the given schema document attached here.  JSON schema validation cannot perform all checks, but it's a good start.  Lots of libraries and tool already exist that do this.  The platform will need to perform additional checks (e.g., all IDs in the JSON document must be unique, all localization IDs have associated localization strings, etc.).  All of those checks are not enumerated here and will require thought/input from the implementor(s).
Once the final JSON document is loaded, a resource file (exact syntax still TBD, but some sort of key:value pairs) will be loaded that is used to replace all locID values in the JSON document.
Once the JSON document is loaded with all of the localized strings, the platform should use it to render menus as needed based on UI actions.

I'm attaching a sample JSON file that includes a few menus and menu items for an example.  It's not complete, but it does validate against the schema.  Here are a few additional comments about the sample and schema:

The file names end with .txt here because GitHub doesn't allow uploading .json files for whatever reason.
Note that position numbers of menu items and menu groups don't have to be integers or sequential.  The idea is to just use them for sorting, and if someone wants to insert something in between menu items they can always pick a floating point number that is in between.  If we want to be picky about where items can be added, we can adjust the constraints.  I suspect UX will have opinions about this, and those opinions may or may not align with how extensibility works in Paratext now.
I am enforcing a specific syntax for locIDs to make sure they are clearly called out.  Also, I am considering all locIDs to be in a global namespace.  I am against the idea of automatically generating those IDs based on other properties because it could cause all resource files to break with a very small code change.  Although the proposal is a bit tedious, it makes localization less likely to break on us later.
I am expecting the only strings that will be displayed from the JSON file are the localized IDs.  Everything else is intended to be for internal use only within the platform.

Other comments:

See the Paranext Extension Architecture doc for examples of the various kinds of menus listed in the JSON schema.
If JSON schema validation proves to be onerous/confusing to implement, it isn't technically required.  JSON schema is being used to convey the ideas and properties needed, and I thought it might be helpful to include in the implementation.  If it's more of a pain than a help to include in the implementation, don't get hung up on it.
There are several online JSON schema validators.  I found https://json-everything.net/json-schema to be the most helpful of the bunch to use.  Error messages aren't always intuitive to find the problem, unfortunately.
Keyboard navigation of menu items (e.g., making "E&xit" associated with the "x" key when navigating a menu by keyboard) is not addressed by this proposal.  I don't know if that is really important.  Even if it is, it might be easy enough to achieve by looking for ampersands in the localized strings and using the letter there as is how Windows native UI menus normally work.
Ira's comments above apply at the level of how the menu system is written in code.  This proposal is about how menus can be contributed by extensions and how that can all work together with localization.  It's higher level than the code.
What to do when a locID is encountered in the JSON document but doesn't have a corresponding resource for the UI language is not addressed in this proposal.  There are a lot of possibilities that include some of those listed above.  I would argue that while it is important, this design does not preclude most/all of those ideas and can move forward now to address the core, common case first.

menu-schema.txt
menu-sample.txt

I am expecting the only strings that will be displayed from the JSON file are the localized IDs

Would tooltips describing the menu item and/or keyboard shortcuts be stored in the JSON file or elsewhere? For example, "Show/hide Unicode" in the Edit menu in Paratext 9 has the tooltip and shortcut below:

Toggle between Unicode character and Unicode number code
Alt+X

The tooltip needs to be localizable. It would be nice if keyboard shortcuts were editable (currently they're not). I expect many people would keep the defaults, but there must be a whole host of anglo-centric shortcuts that make less sense once the UI is localized. I suspect that's something which we wouldn't rush to add immediately, but planning with it in mind would be wise.

(e.g., if some extension tries to create a duplicate menu item that already exists, that extension fails to load).

What do you mean by a duplicate menu item? Do you mean one that has the same text? Are we then going to check all languages? How does that work?

TJ had enough feedback that I moved all proposal updates to https://docs.google.com/document/d/1N9BVj5w1b3H90Sjjc1lRN2zbalL-beDHmh4jxxExtiw/edit?usp=drive_link.
@ianhewubs I added tooltips to the latest proposal.  Good thought, and it was trivial to add.  Keyboard shortcuts are not part of the spec right now, though.  While I can't say for certain until the a shortcut design is done, I think the framework I'm proposing could be extended since we're providing objects for each menu item.  For example, we could have "localizable" values for shortcuts just like the menu item strings.  I don't really know what all the goals are for customization, though.  For example, do we want users to be able to set their own?  That would have an impact to the design beyond different defaults for different languages.  All that being said, I'm going to consider it out of scope for the time being unless we simply can't ignore it.
@FoolRunning I was talking about this in terms of menu item IDs, but those are mostly gone in the latest design.  The only case where they remain in the design is that menu items that are anchors for submenus still have IDs in the latest spec.  There is also some language about what to do about ID collisions in the updated proposal.


Markdown language provider

It would be useful to be able to create markdown documentation from JSON Schema.
There are other (excellent) tools in the wild but they have a number of deficiencies or limitations, including one or more of:

They don't provide universal tools that "just work" on Windows/Linux/MacOS without a containerload of dependencies
They don't support all keywords in all drafts from Draft 4 to 2020-12.
They don't link back to canonical documentation
They don't allow you to add additional documentation in external files to target particular schema or elements within the schema (if you are not the owner of the schema itself.)
They don't perform semantic analysis on the types, allowing us to document common patterns e.g. tuple, strongly-typed map, strongly-typed array.

In order to support this we should

Create a MarkdownLanguageProvider implementing ILanguageProvider
Refactor the unnecessary "capabilities" out of ILanguageProvider in the same way as IHierarchicalLanguageProvider so that we don't need NOP implementations of things we don't need (like validation).
Create the provider's Options type that gives us the ability to provide external documentation files
Add a canonical documentation uri to the IKeyword interface (or possibly to a new "documented keyword" interface, and link to the appropriate docs. e.g. https://www.learnjsonschema.com/2019-09/, https://www.learnjsonschema.com/2020-12
Implement the single code file provider
i. Title
ii. Description
iii. Semantic detail
iv. keywords by classification (e.g. applicator, validation), with hyperlinks to the relevant schema

There are two motivations to provide this:

To encourage better schema documentation and understanding
To illustrate how to build a custom language provider leveraging the output of the type analysis.

The MD provider does not need to support hierarchy, validation or naming, so it is comparatively simple.
But we can illustrate how we can make the provider extensible so it can support new capabilities.


Document features

This tool looks great! I hope to see it continue to improve and reach feature parity with Coverage.py.
It would be really useful to have each of the features you support explicitly documented, with instructions on how to use them. Currently I feel like I have to dig through the issues and source code to understand what's possible/supported.

Thank you!  I think currently running python -m slipcover --help would be your best source.

Maybe that should be in the README?


Stingy argument: TextInput & TextArea components

http://stingy-argument.glitch.me/#StoryTextInput

are there any other visual styles of text inputs that I'm missing here?
are there cases where TextArea shouldn't auto-size? or should that be built in?

These look about right to me. I think autosizing textareas should be the default, but I noticed that the autosizing textarea in this example still becomes scrollable:

Yeah, my implementation was pretty hacky; i was trying to avoid actually pulling in that dependency but I guess there's no reason to avoid it.

Updated with autosizing on by default.

I think the transition style should be removed from the autosized textareas. Here's a textarea as it is now vs. one w/o a transition:

w/ transition
w/o transition

:rocket: PR was released in v0.19.0 :rocket:


Unable to provide full path to .xccoverage file

There is error output here that states that you can provide a full path to the .xccoverage file:
https://github.com/nakiostudio/xcov/blob/b4d00172e7277adae5f28f8fe36c19af33600499/lib/xcov/error_handler.rb#L12
However there is no mechanism to provide a full path to the .xccoverage file that I can see within: manager.rb

@raven Not sure if you are using Xcode 9.2 or Xcode 9.3, if you are using Xcode 9.2 with the latest version of Xcov 1.4. You can set the legacy_support parameter to xccoverage in your fastfile to parse the coverage reports generated by Xcode 9.2. No need to specify a path.
@nakiostudio Maybe you can update the README for the legacy_support parameter, so it explains the legacy_support parameter is a string value, containing either: xccoverage or the default value xccovreport.

I used below command as i am using Xcode 9.2:
xcov --legacy_support xccoverage [Path_to_coverage_file]
But getting below error:
[14:53:06]: Unable to find any .xccoverage file.
[14:53:06]: Make sure you have enabled 'Gather code coverage' setting on your scheme settings.
[14:53:06]: Alternatively you can provide the full path to your .xccoverage file.
Looking for related GitHub issues on fastlane/fastlane...
Found no similar issues. To create a new issue, please visit:
https://github.com/fastlane/fastlane/issues/new
Run fastlane env to append the fastlane environment to your issue
Traceback (most recent call last):
13: from /usr/local/bin/xcov:23:in <main>' 	12: from /usr/local/bin/xcov:23:in load'
11: from /usr/local/lib/ruby/gems/2.5.0/gems/xcov-1.4.0/bin/xcov:6:in <top (required)>' 	10: from /usr/local/lib/ruby/gems/2.5.0/gems/xcov-1.4.0/lib/xcov/commands_generator.rb:15:in start'
9: from /usr/local/lib/ruby/gems/2.5.0/gems/xcov-1.4.0/lib/xcov/commands_generator.rb:46:in run' 	 8: from /usr/local/lib/ruby/gems/2.5.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in run!'
7: from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.92.1/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:75:in run!' 	 6: from /usr/local/lib/ruby/gems/2.5.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in run_active_command'
5: from /usr/local/lib/ruby/gems/2.5.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in run' 	 4: from /usr/local/lib/ruby/gems/2.5.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in call'
3: from /usr/local/lib/ruby/gems/2.5.0/gems/xcov-1.4.0/lib/xcov/commands_generator.rb:41:in block (2 levels) in run' 	 2: from /usr/local/lib/ruby/gems/2.5.0/gems/xcov-1.4.0/lib/xcov/manager.rb:30:in run'
1: from /usr/local/lib/ruby/gems/2.5.0/gems/xcov-1.4.0/lib/xcov/manager.rb:45:in parse_xccoverage' /usr/local/lib/ruby/gems/2.5.0/gems/xcov-1.4.0/lib/xcov/error_handler.rb:20:in handle_error': [!] Error creating your coverage report - see the log above (RuntimeError)

@cisum-la I think the path is not needed. So the command is: xcov --legacy_support xccoverage Xcov then uses the old way of finding and collecting information from .xccoverage file.

This was resolved by https://github.com/fastlane-community/xcov/pull/150


docs: 📚 fix typos in values and readme

What does this PR do?
Fix typos in values and readme
Motivation
Correct indentation and correct language
More

[ ] Yes, I updated the tests accordingly
[ ] Yes, I updated the schema accordingly
[ ] Yes, I ran make test and all the tests passed

cc @sheddy-traefik


Potential bug in senseLogic or MMM: chat function is overwritten with undef

Try this:

In our TEST game, select two tokens with standard senses, e.g. Yorric MacRathgar and Yerrick MacRothgar.
From the character sheet "MacroSheet", execute the ability "senseSeeManual". Accept both input prompts unchanged.

My output:
Sehen
Yorric MacRathgar 17
💬 Deinen Augen fällt nichts besonderes auf hier.
Yerrick MacRothgar 14
💬 Deinen Augen fällt nichts besonderes auf hier.
(From Mych's Macro Magic):
🔎 "/w \"Yorric MacRathgar\" Deinen Augen fällt nichts besonderes auf hier." undef
(From Mych's Macro Magic):
During execute, unknown function in expression in script: !mmm do chat❌(playerMessage)

The last bit is the original error message we stumbled over during the game last night. The second to last bit is debug code I just added: the value of playerMessage and the value of chat, the latter of which should be provided in a debug chat context as (...args) => symbolValue.apply(symbolContext, args), I learned.
Why is this happening? I went through the code (abilities senseSeeManual and senseLogic in the MacroSheet "character", for the above test case) and there are only very simple combine chat and chat: commands before the line that throws the error.
With MMM 1.19, the script worked without a hitch -- though we admittedly didn't have it around for very long, so there may be a special set of conditions that just didn't come up before last night.

Thanks for the comprehensive report! Having a reliable repro case will make this a whole lot easier to fix.
MMM 1.20.0 completely replaced the inner workings of the expression engine, which I'm sure has something to do with this. I'll check it out as soon as possible.

Minimal repro case:
!mmm script
!mmm     combine chat
!mmm     end combine
!mmm     do chat("foo")
!mmm end script

(From Mych's Macro Magic):
During execute, unknown function in expression in script: !mmm do chat❌("foo")

So it's apparently a failure of end combine to properly un-register its temporary replacement of the chat function, which it puts into the variables stash.

The root cause is a subtle change in how context shadowing behaves after the MychExpression rewrite: Previously, an undef-valued variable wouldn't have shadowed the corresponding context member – now, it does.
This change triggers the bug because end combine never quite cleaned up after itself entirely correctly: Regardless of whether the chat variable was undef or entirely didn't exist, it left the variables stash with an undef-valued chat variable in the end. This bit should definitely be fixed, if just to be completely clean about it.
This leaves the question though whether the new context-shadowing behavior should be considered a bug or a bugfix compared to the old behavior. There's currently no way to delete a variable – you can only set it to undef.
But arguably, when you do that, you'd expect it to remain undef much rather than suddenly have some other value appear in place of the undef you set (from context). So I'd argue that the new shadowing behavior has much less potential of being surprising or introducing sudden bugs due to a new MMM context symbol being introduced in a new version. (For example, when the selected context symbol was introduced recently, an existing MMM script that used selected as a regular variable would still behave predictably even after setting selected to undef.)

The !mmm chat: command remained unaffected because its context fallback mechanism is separate from the expression engine's (and still looked for undef instead of existence).
I can't come up with a particularly compelling reason why I should change this except for consistency with the chat() function.
The only possible outcome of aligning the context fallback mechanism of the chat: command with symbol lookup in the expression engine is more crashes in case someone sets a variable named chat. Maybe a better choice is to make the chat: command more robust by allowing only functions to shadow the default context chat() function.

By the way: This...
!mmm script
!mmm     set chat = whisperback
!mmm     chat: Whisper!
!mmm end script

...does, and should do, exactly what it sounds like. Not sure if it's useful anywhere. (Maybe if we ever get custom functions?)


@CrystalChadburn Started looking at this today. Clarification question: Do we want to share the instance Mussels already has? (https://metabase-7068ad-prod.apps.silver.devops.gov.bc.ca/) and setup our own content within here or provision a separate instance? Additionally, do we want a vanity domain for this or is the .silver.devops.gov.bc.ca domain ok?.

Hi Rob,
We need a separate instance than the mussel app please.   I think we would prefer a vanity URL but wondering how long that would take?
Thanks!
Crystal
From: Robert Johnstone @.>
Sent: April 10, 2022 7:18 PM
To: bcgov/invasivesbc @.>
Cc: Chadburn, Crystal FLNR:EX @.>; Mention @.>
Subject: Re: [bcgov/invasivesbc] Get PROD version of metabase standing up (Issue #1761)
[EXTERNAL] This email came from an external source. Only open attachments or links that you are expecting from a known sender.
@CrystalChadburnhttps://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FCrystalChadburn&data=04|01|crystal.chadburn%40gov.bc.ca|8773f4c000484d76e13608da1b616eaf|6fdb52003d0d4a8ab036d3685e359adc|0|0|637852402520258263|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=%2F2cLRelaSgz5%2FzplarB1nsTJyBwCiWgEiJOlI%2FqqyNg%3D&reserved=0 Started looking at this today. Clarification question: Do we want to share the instance Mussels already has? (https://metabase-7068ad-prod.apps.silver.devops.gov.bc.ca/) and setup our own content within here or provision a separate instance? Additionally, do we want a vanity domain for this or is the .silver.devops.gov.bc.ca domain ok?.
—
Reply to this email directly, view it on GitHubhttps://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbcgov%2Finvasivesbc%2Fissues%2F1761%23issuecomment-1094474826&data=04|01|crystal.chadburn%40gov.bc.ca|8773f4c000484d76e13608da1b616eaf|6fdb52003d0d4a8ab036d3685e359adc|0|0|637852402520258263|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=%2B75Rnzde0kb3DTuCTfunWh3ComtaB%2FKZYdaGafR1VwQ%3D&reserved=0, or unsubscribehttps://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FATTA6WLAO7ZXQTSVW3PPHS3VEODTVANCNFSM5SJI3YDA&data=04|01|crystal.chadburn%40gov.bc.ca|8773f4c000484d76e13608da1b616eaf|6fdb52003d0d4a8ab036d3685e359adc|0|0|637852402520258263|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=RL%2Fdi5z1LyQQP3HRU08CL1sTxbFgT9Tiuvp1y2XPkDs%3D&reserved=0.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>


Spring annotation Enhance

Please answer these questions before submitting a pull request

Why submit this pull request?

[ ] New feature provided

Related issues

New feature or improvement

Describe the details and related test reports.

Because spring annotation only match spring bean by annotation.So is would be facing so many question when using on production system.
so add a second condition regex expression to match spring bean

Please use a clean branch to do a new pull request. Thanks.


Using specific version of python

I am trying to use a specific version of python in /usr/bin/gluepython3
So, I tried:
in init.vim
luafile $HOME/.config/nvim/plugins.lua

and have lua file as below.
$ cat plugins.lua
local iron = require('iron')

iron.core.add_repl_definitions {
    python = {
        mycustom = {
            command = {"/usr/bin/gluepython3"}
        }
    }
}

iron.core.set_config {
    preferred = {
        python = "python"
    }
}

I tried various combinations:
1st tried
command = {"/usr/bin/gluepython3"}

realized that only send custom command so:
cat ~/.config/nvim/plugins.lua
local iron = require('iron')

iron.core.set_config {
    preferred = {
        python = "gluepython3"
    }
}

and tried replacing above file with      python = "/usr/bin/gluepython3"
but both times I get memory errors.
multiline w/ "/usr/bin/gluepython3"

multiline w/ "gluepython3"

This seems like simple setting issue. Pls let me know how I can fix. I have been in the docs, but not finding the correct info.
BTW: It works if
python = "python"
Thanks,

In file  lua/iron/fts/python.lua. I see:
local pyversion  = executable('python3') and 'python3' or 'python'
...
(snip)
...
python.ptipython = def({"ptipython"})
python.ipython = def({"ipython", "--no-autoindent"})
python.ptpython = def({"ptpython"})
python.python = {
  command = {pyversion},
  close = {""}
}

I attempted to change it to: local pyversion  = executable('gluepython3')
&  local pyversion  = executable('/usr/bin/gluepython3')
but no avail.
I get
[Process exited 0]


Broken in PHPUnit 7.0

https://github.com/Sempro/phpunit-pretty-print/blob/214fe4e342f0402e642a8c24f04896b50aaa3700/composer.json#L10
This definition is wrong, because package isn't working in PHPUnit 7.0

The package should be working with phpunit 7 now.


Avoid copies

The temporaries here prevented the move version of push_back from being used.

Oh. I thought making them const references would trigger move. Does it move only when you construct in place?


⚠ Auth has degraded performance

In 05ca495, Auth (https://auth.k2lin.com) experienced degraded performance:

HTTP code: 200
Response time: 5549 ms

Resolved: Auth performance has improved in affb75a.


Port change to match with Server

:-)

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


Ability to pass in protected headers to sign_compact.

Signatures may not validate if multiple (protected) headers are fed in. This
is related to sign_compact computing the b64 representation of the protected
headers (xargs) outside of the jwt, and then using jwt.pack() which would
re-serialize the protected headeres, potentially changing the way the json is
formatted.

Please note that test_private_key_from_jwk fails because jwk_private_key.json has not been committed.

23 jul 2015 kl. 20:39 skrev Arjun Sharma<EMAIL_ADDRESS>Please note that test_private_key_from_jwk fails because jwk_private_key.json has not been committed.

It is now.

Roland

”Capitalism is the extraordinary belief that the nastiest of men for the nastiest of motives will somehow work for the benefit of all" - John Maynard Keynes.


"Error parsing provisioning profile" when running fastlane on cron job

I'm trying to run a cron job with my fastlane actions, but I get this "Error parsing provisioning profile" error after running sigh. I looked into the code, and it seems to me that the cron job can't run the command "security cms -D -i #{path}" from provisioning_profile.rb to parse the provisioning profile. The path to the profile is correct. Is there a way to fix this?
It works fine when I run on the terminal.

Ok, here's what I found:
I ran security cms from the cronjob, and changed some stuff to make it work

I need to add some certificates (not sure which ones yet, but I copied my login keychain and it worked) to my System.keychain, to be available to the cron job so it can decode it
I need to use 'sudo' when running the security command, so I don't get a "security: cert import failed: write permissions error"

but I don't want to add the sudo... anyway I can fix this?

It looks like there hasn’t been any recent activity on this issue in some time, so I’m closing it. If this is still a problem, feel free to re-open a new issue and I’d be happy to help :+1:


WIP cfn2py enhanced with cfn2pyclass. Creates tree structure of python classes for manageable json creation

WIP - DO NOT MERGE -
Currently: cfn2py prints to console a large python file. This file is difficult to manage/enhance programmatically.
GOAL
Create a more manageable system that can be version controlled with easing future changes in mind
WORK DONE SO FAR

cfn2pyclass enhances cfn2py -  instead of printing the python code to console, the python code is saved into individual python classes within a regional tree structure (this will be argument input by user).
jinja2 templating is used for file creation
base object (not included) handles iterating through the created region/aws_instance file structure and creates the json file
enhanced the securitygroups (ingress and egress)

WORK STILL TO DO

better way to import necessary modules
Parameterize necessary user inputs
Allow users to change all IP's upon json creation
Pep8
Fix some bugs....

Closed in preference to:
https://github.com/cloudtools/troposphere/pull/267


Dependencies outdated: @sentry/angular

Environment
How do you use Sentry?
Sentry SaaS (sentry.io)
Which SDK and version?

<EMAIL_ADDRESS>ionic 5.6
angular 12

Steps to Reproduce

run npm outdated
check: @sentry/angular  current:  6.11.0   wanted: 6.13.3
run npm install @sentry/angular@lates

Expected Result
The npm install ... or even npm update command should update all packages to the "wanted" version
Actual Result
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@sentry/angular
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@sentry/capacitor
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/@sentry/angular
npm ERR!   peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@sentry/capacitor
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@sentry/angular
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>

the mentioned dependency was updated on https://github.com/getsentry/sentry-capacitor/pull/159 and will be available on the next release.


why use deepspeed zero2 for pretrain but use zero3 for finetune?

Are there any other considerations besides saving GPU memory?

It's from LLaVA.
BTW, the pretrain stage of Bunny-v1.1-Llama-3-8B-V is under zero3.

thx


Add light automation and effect for Ghost Lantern

I considered an aura effect to apply the ghost touch effect, but the sentence "If an affected weapon or attack is magical and already has the maximum number of property runes, the wielder can choose one to suppress to gain ghost touch." made that dubious.


Standardize the layout of the http _response property in output types

Existing consistencies
There are a few inconsistencies regarding how do we define the _response property in our output types. Those inconsistencies are discussed below:
Not every package supports the _response property
List of packages that do support the _response property:

Form Recognizer
Tables
App Configuration
Storage File Datalake
Storage File Datashare
Storage Queue

List of packages that do not:

Identity
Text Analytics
Key Vault
Event Hub
Service Bus
Search
Cosmosdb
Core (well, obviously!)

The shape of the _response property varies between packages
On one hand, App Configuration has the following type that is extended by output types:
export interface HttpResponseField<HeadersT> {
    _response: HttpResponse & {
        parsedHeaders: HeadersT;
        bodyAsText: string;
    };
}

On the other hand, all other packages mirror the generated response type in some sense and change the type that is being intersected with to be the corresponding one from the convenience layer alongside other convenience changes. For instance, Tables has the following generated response type (located at sdk/tables/azure-tables/src/generated/models/index.ts):
/**
 * Contains response data for the query operation.
 */
export type TableQueryOperationResponse = TableQueryHeaders &
  TableQueryResponse & {
    /**
     * The underlying HTTP response.
     */
    _response: coreHttp.HttpResponse & {
      /**
       * The response body as text (string format)
       */
      bodyAsText: string;

      /**
       * The response body as parsed JSON or XML
       */
      parsedBody: TableQueryResponse;
      /**
       * The parsed HTTP response headers.
       */
      parsedHeaders: TableQueryHeaders;
    };
  };

and in the convenience layer, it has the following corresponding response type (located at sdk/tables/azure-tables/src/models.ts):
export type ListTableItemsResponse = Array<TableResponseProperties> & {
  /**
   * This header contains the continuation token value.
   */
  nextTableName?: string;
  /**
   * The underlying HTTP response.
   */
  _response: HttpResponse & {
    /**
     * The response body as text (string format)
     */
    bodyAsText: string;

    /**
     * The response body as parsed JSON or XML
     */
    parsedBody: TableQueryResponse;
    /**
     * The parsed HTTP response headers.
     */
    parsedHeaders: TableQueryHeaders;
  };
};

Which looks similar to the App Configuration's one but has the extra property parsedBody that is typed using the generated type TableQueryResponse which is fully static in the sense that it does not have any any members.
What is the best shape for _response anyway?
From the JS SDK weekly team meeting on 8/26/2020, the proposed shape is to mirror the response generated types but if the parsedBody property exist, type it as any, so the Tables's ListTableItemsResponse  would become:
export type ListTableItemsResponse = Array<TableResponseProperties> & {
  /**
   * This header contains the continuation token value.
   */
  nextTableName?: string;
  /**
   * The underlying HTTP response.
   */
  _response: HttpResponse & {
    /**
     * The response body as text (string format)
     */
    bodyAsText: string;

    /**
     * The response body as parsed JSON or XML
     */
    parsedBody: any;
    /**
     * The parsed HTTP response headers.
     */
    parsedHeaders: TableQueryHeaders;
  };
};

How to move forward?
I suggest that the _response property should be added to all output types in all packages according to the approach we agreed on. Furthermore, I suggest to change the typing of parsedBody property in packages that already support the _response property to be any and no longer expose the generated type if it is not needed elsewhere.
It is yet to be checked if there is any customer who relies on the type of parsedBody. I will reach out to the .Net SDK team asking for such scenarios if any.

Related to discussion in https://github.com/Azure/azure-sdk-for-js/pull/10602#discussion_r474340862
There was debate about whether it should be typed at all, but if it is typed, I agree that parsedBody: any is fine. Leaking all the generated goo into the typing for an escape hatch scenario would be too much.  I think _response: HttpOperationResponse as I had it matches your proposal concisely and is also used in other places (I borrowed it from somewhere). I think it could be the standard that could be used everywhere should it be decided that it must be typed.
cc @xirzec @bterlson

Widening to any has a tendency to virally cause other inferred types to become any as well. If there's any client user for an existing _response using parsedBody and allowing inference based on its stronger type, then that could cause any to suddenly start appearing in many places. I don't think it would be breaking, though, in the sense that the code would continue to function as normal but more type information than just this parsedBody could be lost in a consuming program.
I like unknown better here, since it will force appropriate casting, but we definitely can't widen to unknown without a break.

Stepping around the "is this a breaking change?" issue, I think ultimately it's better to get out of the business of typing/guaranteeing intermediate request pipeline goop.
Right now parsedBody is just the unflattened contents of the response object itself and doesn't add anything useful (it is NOT the raw response from the server.) Parsed headers is equally useless, since our headers collection is simply a case insensitive dictionary of whatever we got back from the server. bodyAsText is questionably useful, but probably annoying for a developer to work with.
I would rather standardize around _request providing access to known useful things, such as the HTTP status code and all headers returned. For cases where folks want to debug our mappers or see the raw server payload, we should provide better logging/debuggability of the HTTP pipeline itself instead of pushing the work off onto whomever called a ServiceClient method wanting a specific shape.
While we're at it, we should revisit what we want to expose on RestError. Today it exposes the full response object, including parsedBody, parsedHeaders, etc. Whatever we decide for _request should probably match what is exposed by RestError.

Closing this in favor of https://github.com/Azure/azure-sdk-for-js/issues/12009. In particular, fixing https://github.com/Azure/azure-sdk-for-js/issues/12009 means we will need to change the way we return the meta data in _response which most likely will be done by a callback to ask for that information on-demand.