Investigate use of all trait names vs. preferred trait names in OT evidence generation

Context of issue:
When we do trait mapping (automated and manual), we use only preferred names, but when we annotate we attempt to use all names.  Because we retain previous mappings even if they don't appear (i.e. don't appear among preferred names in current ClinVar), this means obsolete mappings can be not just retained but also used without being updated.
Example - in ClinVar:
    <TraitSet Type="Disease" ID="6307">
      <Trait ID="4675" Type="Disease">
        <Name>
          <ElementValue Type="Preferred">Malignant tumor of urinary bladder</ElementValue>
          <XRef ID="Bladder+cancer/7822" DB="Genetic Alliance"/>
          <XRef ID="399326009" DB="SNOMED CT"/>
        </Name>
        <Name>
          <ElementValue Type="Alternate">Urinary bladder cancer</ElementValue>
          <XRef ID="MONDO:0001187" DB="MONDO"/>
        </Name>
        <Name>
          <ElementValue Type="Alternate">Urinary Bladder Neoplasms</ElementValue>
          <XRef ID="D001749" DB="MeSH"/>
        </Name>
        <Name>
          <ElementValue Type="Alternate">Bladder cancer</ElementValue>
        </Name>
        <AttributeSet>
          <Attribute Type="keyword">Hereditary cancer syndrome</Attribute>
        </AttributeSet>
        <XRef ID="MONDO:0001187" DB="MONDO"/>
        <XRef ID="C0005684" DB="MedGen"/>
        <XRef Type="MIM" ID="109800" DB="OMIM"/>
      </Trait>
    </TraitSet>

In latest mappings:
# preferred name yields up-to-date mapping
$ grep -i '^Malignant tumor of urinary bladder' latest_mappings.tsv
malignant tumor of urinary bladder	http://purl.obolibrary.org/obo/MONDO_0004986	urinary bladder carcinoma

# alternate name yields obsolete mapping
$ grep -i '^Urinary bladder cancer' latest_mappings.tsv
urinary bladder cancer	http://www.ebi.ac.uk/efo/EFO_0000292	bladder carcinoma

In #383 we modified annotated XML generation to use only preferred names, observing that it decreased coverage of traits only slightly while decreasing the number of obsolete EFO terms used significantly.
The goal of this issue is to see what is the impact of making a similar change for OT evidence string generation (which is more complicated due to how it groups and explodes traits), and if it is acceptable make the change.

See also #210


updated odrive (5091)

Thank you for the contribution. It was merged directly as 79412ec4d68392ce3fdc9e6f23aca8968a6cabaf to keep commit history cleaner. Your contribution is still credited to you.


Possible to use transfer learning?

Is it possible to transfer learn from the largest resolution on a new dataset? This was a common trick that worked pretty well in other versions of StyleGAN and saved a ton of compute time.
I tried the following (but may have gotten some of the arguments wrong):
!python train.py --outdir=./training-runs/test --cfg=stylegan3-t --data=./data/my-dataset-256.zip \
  --gpus=1 --batch=64 --mirror=1 --snap 1 --batch-gpu 4 --kimg 10000 --syn_layers 10 --head_layers 4 \
  --resume=./pretrained/pokemon256.pkl --metrics=None

but I got the following error:
RuntimeError: output with shape [12] doesn't match the broadcast shape [12, 12]

aren't you the guy that made fun of our beautiful WordArt logo on Twitter? :joy:
Finetuning is definitely possible, I'll fix this in the near future. Also, you can skip progressive growing and train on the final resolution directly, it just takes longer and the results will not be as good.

I did, and I stand by it 🤪
Thanks! I’m just interested in seeing how "not as good" it is compared to full training—a lot of folks don’t have months to train a project, so even a week or two of time being better than the similar time on sg3 is worth it.

Actually, progressive growing can get you good results faster than standard training because the throughput is much higher at lower resolutions. Check out this figure from the OG progressive growing paper:

If you want to do as few stages as possible, I recommend training a 32x32 or 64x64 stem and then directly train on your final resolution (you need to adjust -up_factor accordingly, as described in the README). Having a fixed pretrained stem helps stability and performance a lot.
That being said, I'll still fix the fine-tuning soon :)

awesome, thanks for all the additional details!

Hi @xl-sr are you still planning to fix this in the future?
ty in advance

hey, sorry for the wait. I'm moved on to another project which needs my full attention atm. I still intend to adress the open issues, it might just take some time :)

Hi @xl-sr,
Thanks for the great work. I'm also working on using your pretrained imagenet256 checkout point for finetuning task.
Also, I met the same error:
RuntimeError: output with shape [12] doesn't match the broadcast shape [12, 12]
After checking out the shape of parameters(line 175, misc.py), I got two small questions:

did you actually use use_radial_filters=True when training with "stylegan3-t" ? (current default: False)
did you actually use conv_kernel=1 when training with "stylegan3-t" ? (current default: 3)

In the line 251,252 of train.py, these two setting only activate when training with "stylegan3-r".
But if I set --cfg=stylegan3-r, then the matched parameters are even less, which didn't look right to me.
If I set --cfg=stylegan3-t and use_radial_filters=True, then the error is gone because now the down_filter will be at the right shape.
conv_kernel=1 doesn't seem to trigger error even though there is a size mismatch ((1,1) <-> (3,3)). I assume because in this case, the network can just do broadcasting when copying the weights. But I'm not sure if this will cause some problems.
Also, do you think these are the reasons for the --resume not working on the Imagenet pretrained checkpoint, or do you think there might also be some parts needed to be fix?
Thank you!
btw, these are the parameters I printed out:

name / checkpoint shape / new init shape
synthesis.input.affine.weight torch.Size([4, 512]) torch.Size([4, 512])
synthesis.input.affine.bias torch.Size([4]) torch.Size([4])
synthesis.L0_36_1024.weight torch.Size([1024, 1024, 1, 1]) torch.Size([1024, 1024, 3, 3])
synthesis.L0_36_1024.bias torch.Size([1024]) torch.Size([1024])
synthesis.L0_36_1024.affine.weight torch.Size([1024, 512]) torch.Size([1024, 512])
synthesis.L0_36_1024.affine.bias torch.Size([1024]) torch.Size([1024])
synthesis.L1_36_1024.weight torch.Size([1024, 1024, 1, 1]) torch.Size([1024, 1024, 3, 3])
synthesis.L1_36_1024.bias torch.Size([1024]) torch.Size([1024])
synthesis.L1_36_1024.affine.weight torch.Size([1024, 512]) torch.Size([1024, 512])
synthesis.L1_36_1024.affine.bias torch.Size([1024]) torch.Size([1024])
mapping.embed.weight torch.Size([1000, 320]) torch.Size([1000, 320])
mapping.embed_proj.weight torch.Size([64, 320]) torch.Size([64, 320])
mapping.embed_proj.bias torch.Size([64]) torch.Size([64])
mapping.fc0.weight torch.Size([512, 128]) torch.Size([512, 128])
mapping.fc0.bias torch.Size([512]) torch.Size([512])
mapping.fc1.weight torch.Size([512, 512]) torch.Size([512, 512])
mapping.fc1.bias torch.Size([512]) torch.Size([512])
synthesis.input.transform torch.Size([3, 3]) torch.Size([3, 3])
synthesis.input.freqs torch.Size([1024, 2]) torch.Size([1024, 2])
synthesis.input.phases torch.Size([1024]) torch.Size([1024])
synthesis.L0_36_1024.magnitude_ema torch.Size([]) torch.Size([])
synthesis.L0_36_1024.up_filter torch.Size([12]) torch.Size([12])
synthesis.L0_36_1024.down_filter torch.Size([12, 12]) torch.Size([12])
synthesis.L1_36_1024.magnitude_ema torch.Size([]) torch.Size([])
synthesis.L1_36_1024.up_filter torch.Size([12]) torch.Size([12])
synthesis.L1_36_1024.down_filter torch.Size([12, 12]) torch.Size([12])
mapping.w_avg torch.Size([1000, 512]) torch.Size([1000, 512])

+1 for transfer learning support

add self.use_radial_filters=False line below this line
it will fix the issue RuntimeError: output with shape [12] doesn't match the broadcast shape [12, 12]

not working ?

add self.use_radial_filters=False line below this line
it will fix the issue RuntimeError: output with shape [12] doesn't match the broadcast shape [12, 12]

not working ?

In my case it is working. Please share the error


Protonation

What does this implement/fix? Explain your changes.
The following code identifies and enumerates the possible protonation sites of SMILES
strings.

@iiitmjay The new file you added here, protonation.py, is a lightly edited version of the file dimorphite_dl.py written by Jacob Durrant. Unfortunately one of the edits that was made along the way was to remove the original copyright statement from the file. How that happened isn't important, but it is clear that this is not your work and that you didn't mention that in the PR, in your commit comments, or in the file itself. Contributing code that you didn't write without making it very clear that this is the case is an absolute no go for us.
I realize that you are trying to help, and I appreciate that, but things like this are not helpful (and can be harmful to the project).
Please do not submit another pull request without discussing it with me via email first.


Monitor collect with Stopwatch

So we can monitor and impute time being passed collecting data for the SEO & Accessibility metrics from the page performances.

Later, we could monitor each of the checkers if we want.

✨ OMG merci @ogizanagi <3


Importing sqlx as .toml dependency failed

Bug Description
I cannot include sqlx in a blank rust project due to "use of unstable library feature 'error_in_core'", unless I pick a really old version namely sqlx=0.3.5.
Info

SQLx version: 0.8.2 (amonst other versions)
SQLx features enabled: None, just sqlx = "0.8.2"
Database server and version: none, I couldn't get that far. It cannot even import
Operating system: Windows 11
rustc --version: rustc 1.77.2 (25ef9e3d8 2024-04-09)

Minimal Reproduction
run cargo new --lib project_name and add sqlx = "0.8.2" to dependencies. Upon saving the toml, then you should get an error. Here is my toml.
[package]
name = "liber"
version = "0.1.0"
edition = "2021"

[dependencies]
sqlx = "0.8.2"

Here is the error message.
Running cargo test --no-run --lib --package=liber --message-format=json --color=always...
Blocking waiting for file lock on package cache
Blocking waiting for file lock on package cache
Blocking waiting for file lock on package cache
Blocking waiting for file lock on package cache
Blocking waiting for file lock on build directory
Compiling stable_deref_trait v1.2.0
Compiling cfg-if v1.0.0
Compiling writeable v0.5.5
Compiling litemap v0.7.4
Compiling smallvec v1.13.2
Compiling icu_locid_transform_data v1.5.0
Compiling once_cell v1.20.2
Compiling icu_properties_data v1.5.0
Compiling utf8_iter v1.0.4
Compiling icu_normalizer_data v1.5.0
Compiling memchr v2.7.4
Compiling write16 v1.0.0
Compiling utf16_iter v1.0.5
Compiling typenum v1.17.0
Compiling windows_x86_64_msvc v0.52.6
Compiling crossbeam-utils v0.8.20
Compiling zerofrom v0.1.5
Compiling scopeguard v1.2.0
Compiling zerocopy v0.7.35
Compiling pin-project-lite v0.2.15
Compiling windows-targets v0.52.6
Compiling futures-core v0.3.31
Compiling serde v1.0.216
Compiling lock_api v0.4.12
Compiling minimal-lexical v0.2.1
Compiling yoke v0.7.5
Compiling cpufeatures v0.2.16
Compiling futures-sink v0.3.31
Compiling percent-encoding v2.3.1
Compiling parking_lot_core v0.9.10
Compiling allocator-api2 v0.2.21
Compiling tracing-core v0.1.33
Compiling slab v0.4.9
Compiling num-traits v0.2.19
Compiling log v0.4.22
Compiling equivalent v1.0.1
Compiling unicode_categories v0.1.1
Compiling futures-io v0.3.31
Compiling zerovec v0.10.4
Compiling form_urlencoded v1.2.1
Compiling ahash v0.8.11
Compiling parking_lot v0.12.3
Compiling parking v2.2.1
Compiling concurrent-queue v2.5.0
Compiling hashbrown v0.15.2
Compiling crc-catalog v2.4.0
Compiling nom v7.1.3
Compiling futures-task v0.3.31
Compiling hashbrown v0.14.5
Compiling pin-utils v0.1.0
Compiling futures-intrusive v0.5.0
Compiling tracing v0.1.41
Compiling event-listener v5.3.1
Compiling futures-util v0.3.31
Compiling crc v3.2.1
Compiling generic-array v0.14.7
Compiling crossbeam-queue v0.3.11
Compiling thiserror v1.0.69
Compiling futures-channel v0.3.31
Compiling byteorder v1.5.0
Compiling bytes v1.9.0
Compiling hex v0.4.3
Compiling windows-sys v0.59.0
Compiling atoi v2.0.0
Compiling indexmap v2.7.0
Compiling hashlink v0.9.1
Compiling block-buffer v0.10.4
Compiling crypto-common v0.1.6
Compiling tinystr v0.7.6
Compiling icu_collections v1.5.0
Compiling digest v0.10.7
Compiling icu_locid v1.5.0
Compiling sha2 v0.10.8
Compiling tempfile v3.14.0
Compiling icu_provider v1.5.0
Compiling sqlformat v0.2.6
Compiling icu_locid_transform v1.5.0
Compiling icu_properties v1.5.1
Compiling either v1.13.0
Compiling serde_json v1.0.133
Compiling icu_normalizer v1.5.0
Compiling idna_adapter v1.2.0
Compiling idna v1.0.3
error[E0658]: use of unstable library feature 'error_in_core'
--> C:\Users\flem1.cargo\registry\src\index.crates.io-6f17d22bba15001f\idna-1.0.3\src/lib.rs:78:6
|
78 | impl core::error::Error for Errors {}
|      ^^^^^^^^^^^^^^^^^^
|
= note: see issue #103765 https://github.com/rust-lang/rust/issues/103765 for more information
error: aborting due to 1 previous error
For more information about this error, try rustc --explain E0658.
error: could not compile idna (lib) due to 2 previous errors
warning: build failed, waiting for other jobs to finish...
Error: Cargo invocation failed.
at t.Cargo.getCargoArtifacts (c:\Users\flem1.vscode\extensions\vadimcn.vscode-lldb-1.11.1\extension.js:1:10993)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Object.open (c:\Users\flem1.vscode\extensions\vadimcn.vscode-lldb-1.11.1\extension.js:1:9296)
Caused by: Error: exit code: 101.
at ChildProcess. (c:\Users\flem1.vscode\extensions\vadimcn.vscode-lldb-1.11.1\extension.js:1:12660)
at ChildProcess.emit (node:events:518:28)
at maybeClose (node:internal/child_process:1104:16)
at ChildProcess._handle.onexit (node:internal/child_process:304:5)

The terminal process terminated with exit code: 1.
Terminal will be reused by tasks, press any key to close it.

This bug disappears, when updagrading to the latest stable version of rust. XD
rustc 1.83.0 (90b35a623 2024-11-26)
Perhaps the sqlx readme should specify compatible rust versions?
Anyhow, for me the problem is solved.


[stable/atlantis] v0.7.1

What this PR does / why we need it:

Ability to pass the new flags on v0.7.1: --default-tf-version, --repo-config-json
Ability to pass --allow-fork-prs

Which issue this PR fixes
Special notes for your reviewer:
My first time contributing to this repo,
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

Just found out about this #13253. Closing this one. Will create another PR to incorporate the --allow-fork-prs flag


Update key-vault-ovw-storage-keys.md

Changed Protocol to HttpsOnly from HttpsOrHttp.

@fhokholdMSFT,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@BrucePerlerMS Please take a look at this and approve. Ritesh pointed this out as a necessary change.

@fhokholdMSFT : Thanks for your contribution to the Azure documentation! The author, @BrucePerlerMS, has been notified to review your proposed change.

thanks for the update Frank.
#sign-off


depricated react-apollo-hooks

react-apollo-hooks is now deprecated in favor of @apollo/react-hooks

we should reopen this for tracking, original PR was reverted


Custom type "extends" Input type but not "extends" Input features

I'm submitting a ...  (check one with "x")
[ ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ x ] support request

Current behavior

I follow the example
https://plnkr.co/edit/b0TOg5IYPCDp6fZFyNes?p=preview
I can see name: 'datepicker', component: FormlyDatePicker, extends: 'input'
But I dont know what configs/functions that 'datekicker' will inherit from Input type
I put keyup event in
this.fields =  [       {         key: 'date',         type: 'datepicker',         templateOptions: {           label: 'Username',           required: true           keyup: () => {             debugger;           }         }       }     ];
But it never being called
Expected behavior

when extends from base component, should bring all methods/configs/events across
Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Windows 10, Visual Studio Code

Angular version: 2.0.X

4.0.2

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Chrome

Language: [all | TypeScript X.X | ES6/7 | ES5]
TypeScript
Node (for AoT issues): node --version =   7.6.0

DatePicker is a custom type that is created in that plnkr, you will have to add the methods that ngbDatepicker provides to the FormlyDatePicker using how FieldTypes are defined and use them


Add precision to Includes, IncludedIn, ProperlyIncludes and ProperlyIncludedIn operators

The aforementioned operators do not account for precision.

Resolved in release 1.2.20


Update required icon for labels for dynamic enablement

Pull Request Test Coverage Report for Build 375555159

0 of 14 (0.0%)  changed or added relevant lines in 2 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.004%) to 41.218%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sql/workbench/api/common/extHostModelView.ts
0
2
0.0%

extensions/resource-deployment/src/ui/modelViewUtils.ts
0
12
0.0%

Files with Coverage Reduction
New Missed Lines
%

extensions/resource-deployment/src/ui/modelViewUtils.ts
2
4.2%

Totals

Change from base Build 375546592:
0.004%

Covered Lines:
21792

Relevant Lines:
48505

💛  - Coveralls


Bump MHLO rev version

Bump to 062222f21c7534b5fdde232d91418a9f792973d4 and update post
renaming of CHLO dialect class.
FIX: 8881

Actually I have https://github.com/google/iree/pull/8942 for today's LLVM bump. I think it contains the MHLO changes you want here?

Awesome, I can wait for it.


cannot run ios js demo (Error: Building UI from XML)

Hi, I am trying to run the demo (non angular) on ios.
after npm install and tns run ios
it gives an error
JS ERROR Error: Building UI from XML. @file:///app/main-page.xml:12:9

which is referring to this line
<bottomBar:BottomNavigation class="bottom-nav"

I think I am missing some setup here. Sorry for being a novice

Well... I recommend you to clone the repository go to src folder an then run this command
npm run demo.ios
Is not necessary to run npm install the command does.
Tell me if it works

Great... it works!
So I think the trick is to tns run ios --syncAllFiles
I found syncAllFiles to be an undocumented switch in man page

No, the first time didn't work because in this case you need to build the
plugin(ts to js).
You can read more about how the plugins work in nativescript docs.
Happy coding
On Oct 15, 2017 3:21 AM, "Chris Tsang"<EMAIL_ADDRESS>wrote:

Closed #3
https://github.com/henrychavez/nativescript-bottom-navigation/issues/3.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/henrychavez/nativescript-bottom-navigation/issues/3#event-1293665156,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF0NmZ6l7kq5Zh8rUaTSVnxEnWb21aORks5sscCVgaJpZM4P5bc-
.


K8SPXC-1071 - Add percona-scheduler-admin for proxysql

Depends on:

https://jira.percona.com/browse/PSQLADM-413 (percona-scheduler-admin fails because of missing my_print_defaults in docker)
https://github.com/percona/percona-docker/pull/647

Test results: https://cloud.cd.percona.com/view/PXC/job/pxc-operator-gke-version/lastCompletedBuild/testReport/

Test name
Status

big-data
passed

haproxy
failed

scheduled-backup
failed

storage
failed

upgrade-haproxy
passed

scaling
passed

cross-site
passed

recreate
passed

scaling-proxysql
passed

security-context
failed

restore-to-encrypted-cluster
passed

self-healing
passed

self-healing-chaos
failed

upgrade-proxysql
failed

init-deploy
failed

demand-backup
passed

self-healing-advanced
passed

self-healing-advanced-chaos
failed

limits
failed

operator-self-healing
passed

operator-self-healing-chaos
failed

smart-update
failed

monitoring-2-0
passed

pitr
failed

affinity
failed

one-pod
passed

demand-backup-encrypted-with-tls
passed

upgrade-consistency
failed

auto-tuning
passed

proxysql-sidecar-res-limits
failed

users
failed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

proxy-protocol
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1198/commits/3cd8fd8731984e0393008a84eb21215f7fe2c388
image: perconalab/percona-xtradb-cluster-operator:PR-1198-3cd8fd87

Test name
Status

We run 0 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1198/commits/9ba4227ce3b395cc7e7a564209642f7d8a8640fe
image: perconalab/percona-xtradb-cluster-operator:PR-1198-9ba4227c

Test name
Status

We run 0 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1198/commits/9ba4227ce3b395cc7e7a564209642f7d8a8640fe
image: perconalab/percona-xtradb-cluster-operator:PR-1198-9ba4227c

Test name
Status

We run 0 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1198/commits/0740fb78b7c2dc3f29af9924c8384c33fa085951
image: perconalab/percona-xtradb-cluster-operator:PR-1198-0740fb78

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: tplavcic:x: inelpandzicYou have signed the CLA already but the status is still pending? Let us recheck it.

Test name
Status

We run 0 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1198/commits/5a924a1de45c959c3e22d50281a5c1bb61560032
image: perconalab/percona-xtradb-cluster-operator:PR-1198-5a924a1d

Test name
Status

recreate
failed

cross-site
passed

haproxy
failed

upgrade-haproxy
passed

big-data
failed

storage
failed

scheduled-backup
failed

scaling
failed

upgrade-proxysql
failed

init-deploy
failed

self-healing
passed

scaling-proxysql
failed

limits
failed

restore-to-encrypted-cluster
failed

self-healing-chaos
failed

smart-update
failed

self-healing-advanced
passed

self-healing-advanced-chaos
failed

operator-self-healing
passed

operator-self-healing-chaos
failed

demand-backup
failed

security-context
failed

upgrade-consistency
failed

pitr
failed

demand-backup-encrypted-with-tls
failed

We run 25 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1198/commits/e77f84d21429767a4945afae16596502574764e0
image: perconalab/percona-xtradb-cluster-operator:PR-1198-e77f84d2

Test name
Status

We run 0 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1198/commits/d46f66d415626468c5f832828c6fbefd7f5064d7
image: perconalab/percona-xtradb-cluster-operator:PR-1198-d46f66d4

Test name
Status

upgrade-haproxy
passed

haproxy
failed

big-data
passed

scaling
passed

storage
failed

scheduled-backup
failed

cross-site
passed

recreate
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

security-context
failed

self-healing
passed

self-healing-chaos
passed

upgrade-proxysql
failed

init-deploy
failed

demand-backup
passed

self-healing-advanced
passed

self-healing-advanced-chaos
passed

limits
failed

monitoring-2-0
passed

operator-self-healing
passed

operator-self-healing-chaos
passed

affinity
failed

pitr
failed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
failed

demand-backup-encrypted-with-tls
passed

smart-update
failed

users
failed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

proxy-protocol
passed

upgrade-consistency
failed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1198/commits/0e6b2c57fcf92b414d61bd4397066ad1fdca32be
image: perconalab/percona-xtradb-cluster-operator:PR-1198-0e6b2c57

Test name
Status

storage
passed

upgrade-haproxy
passed

recreate
passed

big-data
passed

cross-site
passed

scheduled-backup
failed

scaling
passed

haproxy
failed

scaling-proxysql
passed

self-healing
passed

self-healing-chaos
passed

restore-to-encrypted-cluster
passed

security-context
passed

upgrade-proxysql
failed

self-healing-advanced
passed

self-healing-advanced-chaos
failed

init-deploy
failed

demand-backup
failed

operator-self-healing
passed

operator-self-healing-chaos
failed

limits
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

pitr
failed

proxysql-sidecar-res-limits
passed

demand-backup-encrypted-with-tls
passed

users
failed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

proxy-protocol
passed

We run 34 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1198/commits/12f9b1e66c940493ff88cf5189c5e7c9f912a7a9
image: perconalab/percona-xtradb-cluster-operator:PR-1198-12f9b1e6

Test name
Status

scaling
passed

upgrade-haproxy
passed

recreate
passed

scheduled-backup
failed

storage
passed

haproxy
failed

cross-site
passed

big-data
passed

scaling-proxysql
passed

self-healing
passed

self-healing-chaos
passed

restore-to-encrypted-cluster
passed

security-context
passed

upgrade-proxysql
failed

self-healing-advanced
passed

self-healing-advanced-chaos
passed

init-deploy
failed

demand-backup
passed

operator-self-healing
passed

operator-self-healing-chaos
passed

limits
passed

monitoring-2-0
passed

smart-update
failed

pitr
failed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

demand-backup-encrypted-with-tls
passed

upgrade-consistency
failed

users
failed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

proxy-protocol
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1198/commits/26368ac34b34be774456d1e145127c24efdedca6
image: perconalab/percona-xtradb-cluster-operator:PR-1198-26368ac3

Test name
Status

storage
passed

upgrade-haproxy
passed

big-data
passed

recreate
passed

cross-site
passed

scaling
passed

haproxy
failed

scheduled-backup
failed

scaling-proxysql
passed

self-healing
passed

self-healing-chaos
passed

restore-to-encrypted-cluster
passed

security-context
passed

init-deploy
failed

self-healing-advanced
passed

self-healing-advanced-chaos
passed

upgrade-proxysql
failed

demand-backup
passed

operator-self-healing
passed

operator-self-healing-chaos
passed

limits
passed

monitoring-2-0
passed

smart-update
passed

affinity
passed

pitr
failed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
failed

demand-backup-encrypted-with-tls
passed

users
failed

tls-issue-self
passed

tls-issue-cert-manager
passed

upgrade-consistency
failed

tls-issue-cert-manager-ref
passed

validation-hook
passed

proxy-protocol
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1198/commits/75fb24c1589adac871505c6ace088e245e75e38f
image: perconalab/percona-xtradb-cluster-operator:PR-1198-75fb24c1

Test name
Status

We run 0 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1198/commits/6d1cb958687c91e316e3699694321e5e23b61fca
image: perconalab/percona-xtradb-cluster-operator:PR-1198-6d1cb958

Test name
Status

scaling
passed

big-data
passed

cross-site
passed

recreate
passed

storage
passed

upgrade-haproxy
passed

haproxy
failed

scheduled-backup
failed

scaling-proxysql
passed

self-healing
passed

self-healing-chaos
passed

security-context
passed

restore-to-encrypted-cluster
passed

upgrade-proxysql
failed

self-healing-advanced
passed

self-healing-advanced-chaos
passed

init-deploy
passed

demand-backup
passed

limits
passed

operator-self-healing
passed

operator-self-healing-chaos
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

pitr
failed

smart-update
passed

auto-tuning
passed

proxysql-sidecar-res-limits
failed

demand-backup-encrypted-with-tls
passed

users
failed

tls-issue-self
passed

tls-issue-cert-manager
passed

upgrade-consistency
failed

tls-issue-cert-manager-ref
passed

validation-hook
passed

proxy-protocol
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1198/commits/be4e197993617f8f69a908a9399b3fa4d17101ed
image: perconalab/percona-xtradb-cluster-operator:PR-1198-be4e1979

Test name
Status

users-5-7
failed

scheduled-backup-8-0
passed

big-data-8-0
passed

scaling-8-0
passed

recreate-8-0
passed

haproxy-8-0
failed

storage-8-0
passed

upgrade-haproxy-8-0
passed

cross-site-8-0
passed

self-healing-8-0
passed

scaling-proxysql-8-0
passed

self-healing-chaos-8-0
passed

restore-to-encrypted-cluster-8-0
passed

security-context-8-0
passed

one-pod-5-7
passed

init-deploy-8-0
passed

self-healing-advanced-8-0
passed

self-healing-advanced-chaos-8-0
passed

upgrade-proxysql-8-0
failed

scheduled-backup-5-7
passed

demand-backup-8-0
passed

limits-8-0
passed

operator-self-healing-8-0
passed

operator-self-healing-chaos-8-0
passed

monitoring-2-0-8-0
passed

init-deploy-5-7
passed

affinity-8-0
passed

haproxy-5-7
failed

one-pod-8-0
passed

pitr-8-0
failed

smart-update-8-0
passed

auto-tuning-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

users-8-0
failed

demand-backup-encrypted-with-tls-8-0
failed

upgrade-consistency-8-0
failed

tls-issue-self-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

validation-hook-8-0
passed

proxy-protocol-8-0
passed

We run 41 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1198/commits/048c372ce5273e1c826543e3b832b7474f7bc08a
image: perconalab/percona-xtradb-cluster-operator:PR-1198-048c372c

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-8-0
passed

demand-backup-cloud-8-0
passed

haproxy-5-7
failed

init-deploy-5-7
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-8-0
passed

scaling-proxysql-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
failed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
failed

users-5-7
failed

users-8-0
failed

validation-hook-8-0
passed

We run 29 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1198/commits/49a5b87ddef3c7a24037fbdaa4600bce7d6d4e88
image: perconalab/percona-xtradb-cluster-operator:PR-1198-49a5b87d

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-8-0
passed

scaling-proxysql-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
failed

users-8-0
failed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1198/commits/a5fc590e221bf4109a31f9c9b7650b320444831b
image: perconalab/percona-xtradb-cluster-operator:PR-1198-a5fc590e

@tplavcic please check tests

@hors test results: https://cloud.cd.percona.com/view/PXC/job/pxc-operator-gke-version/lastCompletedBuild/testReport/
I have executed chaos tests locally and they pass, other self healing tests failed because they have been removed.

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-8-0
passed

scaling-proxysql-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
failed

users-8-0
failed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1198/commits/7d4e5cebaa4e1e90531adbf1b48ac193375f7632
image: perconalab/percona-xtradb-cluster-operator:PR-1198-7d4e5ceb

Test name
Status

cross-site-8-0
passed

haproxy-5-7
failed

haproxy-8-0
failed

init-deploy-8-0
failed

proxysql-sidecar-res-limits-8-0
failed

recreate-8-0
failed

restore-to-encrypted-cluster-8-0
failed

scaling-8-0
passed

scaling-proxysql-8-0
passed

scheduled-backup-8-0
failed

security-context-8-0
failed

smart-update1-8-0
failed

storage-8-0
failed

tls-issue-self-8-0
failed

upgrade-haproxy-8-0
failed

upgrade-proxysql-8-0
failed

We run 16 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1198/commits/8535d08fc4bf755ef90797bbe6012029f1f9ed8b
image: perconalab/percona-xtradb-cluster-operator:PR-1198-8535d08f

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
failed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-8-0
passed

scaling-proxysql-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1198/commits/333cf068e8d10e4c35afc135f4fe674c970d8649
image: perconalab/percona-xtradb-cluster-operator:PR-1198-333cf068

@tplavcic please fix conflicts

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-8-0
passed

scaling-proxysql-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
failed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
failed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1198/commits/71298a34ec81634606aaa140c55173151cd0ae0d
image: perconalab/percona-xtradb-cluster-operator:PR-1198-71298a34

Test name
Status

cross-site-8-0
passed

haproxy-5-7
failed

haproxy-8-0
failed

init-deploy-8-0
failed

pitr-8-0
failed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
failed

restore-to-encrypted-cluster-8-0
passed

scaling-8-0
passed

scaling-proxysql-8-0
passed

scheduled-backup-8-0
failed

security-context-8-0
failed

smart-update1-8-0
failed

storage-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
failed

tls-issue-self-8-0
failed

upgrade-consistency-8-0
failed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
failed

We run 20 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1198/commits/49a07092718a823dd6ce630588198f425dd80e38
image: perconalab/percona-xtradb-cluster-operator:PR-1198-49a07092

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-8-0
passed

demand-backup-cloud-8-0
failed

demand-backup-encrypted-with-tls-8-0
passed

haproxy-5-7
passed

haproxy-8-0
failed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-8-0
passed

scaling-proxysql-8-0
passed

scheduled-backup-5-7
failed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
failed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1198/commits/e40e8344e4f2d7181a11e14a88f52354d94d08aa
image: perconalab/percona-xtradb-cluster-operator:PR-1198-e40e8344

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

haproxy-5-7
failed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
failed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-8-0
passed

scaling-proxysql-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1198/commits/1bafb5ce4d90453182e75670a826635bd89dc515
image: perconalab/percona-xtradb-cluster-operator:PR-1198-1bafb5ce

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
failed

cross-site-8-0
failed

demand-backup-8-0
passed

demand-backup-cloud-8-0
passed

haproxy-5-7
passed

haproxy-8-0
failed

init-deploy-5-7
failed

init-deploy-8-0
failed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-8-0
passed

scaling-proxysql-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
failed

smart-update1-8-0
failed

smart-update2-8-0
failed

storage-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
failed

validation-hook-8-0
passed

We run 35 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1198/commits/3c583081ab427a71037966b9b4b008efe37dc7ea
image: perconalab/percona-xtradb-cluster-operator:PR-1198-3c583081

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-8-0
passed

demand-backup-cloud-8-0
failed

demand-backup-encrypted-with-tls-8-0
passed

haproxy-5-7
failed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-8-0
passed

scaling-proxysql-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
failed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
failed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1198/commits/6f56ee0308c678035e551d4774e214c652bd1090
image: perconalab/percona-xtradb-cluster-operator:PR-1198-6f56ee03


Update .sh folders to match structure

Updating the the folders in the Copy directories section to reflect the file structure within the repository

Good catch @colts45s this was a copy error on our part.
Unfortunately we have internal requirements for contribution credit and a change this small isn't per say what we're looking for.
However, we did make the change here.
https://github.com/simeononsecurity/FireFox-Privacy-Script/commit/1c445d531204c271668fafebe46a2bad8543a130

Now worries. I don't particularly need any credit, but I also did not see a contribution note on a process. Thanks for taking a look at this though 👍

Unfortunately we have internal requirements for contribution credit and a change this small isn't per say what we're looking for

* per se

Unfortunately we have internal requirements for contribution credit and a change this small isn't per say what we're looking for

per se

VTT still isn't perfect.


Subaru: remove Impreza CAN fingerprints

We've had two Ascent users so far report that their cars are mis-fingerprinting on 0.8.13. I have one of their dongle IDs, and there are no FW versions in the logs, which implies their comma power is unplugged. In that case, the CAN fingerprinting fallback identifies them as Imprezas.
@martinl should we remove any other CAN fingerprints or is this the only known overlap? Since we can't trust the CAN fingerprinting, I think we'll need to manually add the FW versions for the Impreza and Ascent.

AFAIK, only Impreza and Ascent FPv1 are very similar and have caused identification issues in the past. I think we can also remove the remaining FPv1 fingerprints if you can get and add fw versions of current Subaru users still fingerprinting using FPv1 from logs. Would we also need to provide new FPv2 test routes for each model?

Nope, no new routes necessary.

I'm having the same issue- this time the comma power is connected and there's FW versions in my logs.

I'm having the same issue- this time the comma power is connected and there's FW versions in my logs.

Great, we'll get your FW versions upstreamed and remove the Impreza fingerprints from the 0.8.13 release so others don't hit the same issue.


执行celery命令出错

安装完依赖并且配置好mysql、redis之后，执行命令celery -A tasks.workers -Q login_queue,search_crawler worker -l info -c 1 报错，堆栈信息如下（我的python版本是3.5，celery版本是4.1.0）
Traceback (most recent call last):
File "/usr/local/python3/bin/celery", line 11, in
sys.exit(main())
File "/usr/local/python3/lib/python3.5/site-packages/celery/main.py", line 14, in main
_main()
File "/usr/local/python3/lib/python3.5/site-packages/celery/bin/celery.py", line 326, in main
cmd.execute_from_commandline(argv)
File "/usr/local/python3/lib/python3.5/site-packages/celery/bin/celery.py", line 488, in execute_from_commandline
super(CeleryCommand, self).execute_from_commandline(argv)))
File "/usr/local/python3/lib/python3.5/site-packages/celery/bin/base.py", line 281, in execute_from_commandline
return self.handle_argv(self.prog_name, argv[1:])
File "/usr/local/python3/lib/python3.5/site-packages/celery/bin/celery.py", line 480, in handle_argv
return self.execute(command, argv)
File "/usr/local/python3/lib/python3.5/site-packages/celery/bin/celery.py", line 412, in execute
).run_from_argv(self.prog_name, argv[1:], command=argv[0])
File "/usr/local/python3/lib/python3.5/site-packages/celery/bin/worker.py", line 221, in run_from_argv
return self(*args, **options)
File "/usr/local/python3/lib/python3.5/site-packages/celery/bin/base.py", line 244, in call
ret = self.run(*args, **kwargs)
File "/usr/local/python3/lib/python3.5/site-packages/celery/bin/worker.py", line 255, in run
**kwargs)
File "/usr/local/python3/lib/python3.5/site-packages/celery/worker/worker.py", line 99, in init
self.setup_instance(**self.prepare_args(**kwargs))
File "/usr/local/python3/lib/python3.5/site-packages/celery/worker/worker.py", line 122, in setup_instance
self.should_use_eventloop() if use_eventloop is None
File "/usr/local/python3/lib/python3.5/site-packages/celery/worker/worker.py", line 241, in should_use_eventloop
self._conninfo.transport.implements.async and
File "/usr/local/python3/lib/python3.5/site-packages/kombu/transport/base.py", line 125, in getattr
raise AttributeError(key)
AttributeError: async

请问是如何解决的


Refactor file system options

What changes are proposed in this pull request?
Refactor file system options
Why are the changes needed?
Avoid overloading Alluxio property key when need to add new filesystem options.
Some path has deterministic file system options.
e.g. FUSE sdk will take user CLI input and set file system options directly. no need to expose global configuration. This can also prevent users use UFSBaseFileSystem when going through clients other than FUSE SDK.
Does this PR introduce any user facing changes?
na

Main changes:

rename original "FileSystemOptions" to "FileSystemOptionsUtils"
add a new "FileSystemOptions" with field metadataCacheEnabled and dataCacheEnabled

alluxio-bot, merge this please


fix: :bug: Fix unecessary warning-level messages

fix: #24

The files got renamed along the way, so the pull request would create a new file, however, I have applied all the changes to the logs.
Thank you!


Support Python 3.11

pyqrcode has not received a single commit since 2016. It still uses nosetests, and after being abandoned for equally as long they no longer work on Python 3.11. This effectively means this dependency is a lot of pain for distributions that can't test these packages properly.

I've just tested pyqrcode on Python 3.11, works:

Yes, pyqrcode should probably move to pytest or similar, a "standard" Python test tool. Please report to upstream.

Apart from that, the real issues pop up with pip install autobahn[all]:

A couple of Cython related issues since the CPy ABI changed: fatal error: longintrepr.h not found

https://github.com/aio-libs/aiohttp/issues/6600
https://github.com/aio-libs/yarl/issues/673
https://github.com/aio-libs/yarl/issues/706
These can be worked around with
export AIOHTTP_NO_EXTENSIONS=1
export FROZENLIST_NO_EXTENSIONS=1
export YARL_NO_EXTENSIONS=1

eth-typing limits to python 3.10

Created a PR for that https://github.com/ethereum/eth-typing/pull/29
Similar for web3.
At this point, I gave up for now ... lots of projects are only just now adjusting to py 3.11, and I don't need it now

I'm sorry but I left my time machine in the other pants.

Part of the deps of autobahn[all] install web3, and of the web3 deps
pip install "aiohttp>=3.7.4.post0,<4"
pip install "eth-abi>=3.0.0,<4.0.0"
pip install "eth-account>=0.6.0,<0.7.0"
pip install "eth-hash[pycryptodome]>=0.2.0,<1.0.0"
pip install "eth-typing>=3.0.0,<4.0.0"
pip install "eth-utils>=2.0.0,<3.0.0"
pip install "hexbytes>=0.1.0,<1.0.0"
pip install "ipfshttpclient==0.8.0a2"
pip install "jsonschema>=4.0.0,<5"
pip install "lru-dict>=1.1.6,<2.0.0"
pip install "protobuf>=3.10.0,<4"
pip install "requests>=2.16.0,<3.0.0"
pip install "typing-extensions>=<IP_ADDRESS>,<5;python_version<'3.8'"
pip install "websockets>=10.0.0,<11"

this one fails
pip install "eth-account>=0.6.0,<0.7.0"

as does this
pip install git+https://github.com/ethereum/eth-account.git

with the same error
      bitarray/_bitarray.c:3276:33: error: lvalue required as left operand of assignment
       3276 |     Py_TYPE(&BitarrayIter_Type) = &PyType_Type;

I;m sorry but why did you hijack my bug report? pyqrcode is the real problem for us. We won't package something in Gentoo that hasn't had any activity since 2015 and doesn't have a working test suite anymore.

I;m sorry but why did you hijack my bug report?

Because Autobahn should run on Python 3.11 - and it doesn't, but not because of pyqrcode, but because of above.

We won't package something in Gentoo that hasn't had any activity since 2015 and doesn't have a working test suite anymore.

I don't use Gentoo, and from my point of view, the whole approach of distributing Python packages as OS packages is "wrong" - but sure, I am aware, this is probably non-mainstream opinion.
I agree about pyqrcode btw: it could need a maintainer, proper refresh etc. - or, indeed, replacing it with sth else - if s.o. comes up with a PR ..
We still need a bug to track autobahn[all] on Python 3.11 .. sorry for hijacking!

Made #1573 for that.

I think we can close this now as 3.11 support was fixed for asyncio. Didn't test twisted though

This works now, so issue can be closed.


Improve the error checking and reporting

Previously it would silently fail, generating report
Now also passes through golangci-lint run

@vakenbolt


feat: add security group id with scheduler cluster (#1354)

feat: add security group id with scheduler cluster

Signed-off-by: Gaius<EMAIL_ADDRESS>
feat: update swagger

Signed-off-by: Gaius<EMAIL_ADDRESS>
Description

Related Issue

Motivation and Context

Screenshots (if appropriate)
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation Update (if none of the other choices apply)

Checklist

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.

Codecov Report

Merging #1356 (6195cfe) into main (a12ef5f) will decrease coverage by 0.16%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1356      +/-   ##
==========================================
- Coverage   45.67%   45.51%   -0.17%
==========================================
  Files         140      140
  Lines       11978    11981       +3
==========================================
- Hits         5471     5453      -18
- Misses       5881     5904      +23
+ Partials      626      624       -2

Flag
Coverage Δ

Object-compatibility-e2etests
?

e2etests
?

unittests
45.51% <ø> (-0.17%)
:arrow_down:

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

Impacted Files
Coverage Δ

client/daemon/peer/peertask_piecetask_poller.go
30.43% <0.00%> (-16.67%)
:arrow_down:

pkg/util/net/iputils/ip_utils.go
59.37% <0.00%> (-2.93%)
:arrow_down:

client/daemon/peer/piece_broker.go
92.30% <0.00%> (+2.56%)
:arrow_up:

cdn/supervisor/progress/progress.go
96.87% <0.00%> (+6.25%)
:arrow_up:


Mobilenetv2 & MobilenetV3 pretrained models !

Dear authors:
Thanks for the beneficial research work! everyone doing cv will gain a lot from your pretrained models.
AFAK, lots of friends from industry are inteseted in these mobile-friendly models. It would be great if you could publish some edge-device pretrained models, such as mobilenetv2 and mobilenetv3, which is the son of Google! Thank you!

Hi, thanks for the interest.
In the paper, we show that unfortunately small models benefit less from big pre-training. We are actively working in the direction of more edge-friendly models, but as this is research, I cannot promise anything :)

Yes, it's helpful! THank you.


add AI4Chem example IFM(nips2023)

PR types

New features
PR changes

Others : Add new AI4Chem example.
Describe

Add new AI4Chem example including code and docs.

 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.

这里测试有报错，辛苦确认一下

@leeleolay 已添加pgl依赖


[BUG] When exposing the api-docs (options.exposeApiDocs) there's a host flag which is not openapi3.0 valid

Describe the bug
When accessing the swagger page, a host parameter is added to the SwaggerObject. This parameter is then shown on the api-docs page which is not OpenApi3.0 complient. Which means we can't copy the api-docs into a client generator.
To Reproduce
Go on the swagger page, and afterwards on the api-docs page. It will be the last paramenter at the bottom.
If you go directly on the api-docs page without passing by the swagger page first the parameter will not be there (On server start)
Expected behavior
The host parameter should not be there in the api-docs page.
Screenshots
http://localhost:3000/v3/api-docs

Swagger io validator [https://editor.swagger.io/]

If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Windows

Hi @Blacklegions,
Oh, you mean with the export in the endpoint. We normally get that info using the event emitter https://brikev.github.io/express-jsdoc-swagger-docs/#/eventEmitter but I think we can solve your 🐛
We will keep this issue updated. It should not be hard, we have to filter the object we exposed.

Thank you for your quick response. I will take a look

I will do a release now I hope that solves the issue. Please don't hesitate to re-open in case it is not fixed.


Move to new Docker package repository

Docker seems to have changed the format & versioning of their APT repo as part of "Project Moby" - this should catch things up to the most recent layout.

CNCF agreement signed & submitted.

ci check this

Thanks for the PR, few comments to be fixed then we can merge if CI is green

Closing since this new apt repo doesn't support 17.03 and 17.11+ seems to disagree with k8s


[release-4.14] HOSTEDCP-1322: NodeUpgradeType defaulted by provider

Manual backport from https://github.com/openshift/hypershift/pull/3273
Which issue(s) this PR fixes:
Fixes #HOSTEDCP-1322

/jira cherrypick HOSTEDCP-1322

/lgtm

/retest


Make auth-flow example work again

I know you guys are still working on the rewrite, I just wanted to make this example work again :)
Thanks

thanks! didn't see this before and its already fixed.


JUnit Foundation does not fire any listeners in case of  PowerMock usage (@RunWith(PowerMockRunner.class))

Hello,
When someone uses a PowerMock runner in tests JUnit Foundation does not fire any events in listeners.
E.G.:
import org.apache.commons.lang3.RandomStringUtils;
import org.junit.Test;
import org.junit.runner.RunWith;
import org.powermock.core.classloader.annotations.PrepareForTest;
import org.powermock.modules.junit4.PowerMockRunner;

import static org.hamcrest.MatcherAssert.assertThat;
import static org.hamcrest.Matchers.equalTo;
import static org.mockito.Mockito.when;
import static org.powermock.api.mockito.PowerMockito.mockStatic;

@RunWith(PowerMockRunner.class)
@PrepareForTest(StaticClass.class)
public class SimplePowermockTest {
	@Test
	public void testPowerMock() {
		String rndStr = RandomStringUtils.randomAlphanumeric(10);
		mockStatic(StaticClass.class);
		when(StaticClass.staticMethod()).thenReturn(rndStr);
		assertThat(StaticClass.staticMethod(), equalTo(rndStr));
	}
}

I've prepared two Test Cases to reproduce the issue:

https://github.com/reportportal/agent-java-junit/blob/develop/src/test/java/com/epam/reportportal/junit/features/powermock/SimplePowermockTest.java
https://github.com/reportportal/agent-java-junit/blob/develop/src/test/java/com/epam/reportportal/junit/features/powermock/SimplePowermockFailureTest.java

And here are corresponding tests, which catch the issue (currently disabled):

https://github.com/reportportal/agent-java-junit/blob/develop/src/test/java/com/epam/reportportal/junit/powermock/PowerMockPositiveTest.java
https://github.com/reportportal/agent-java-junit/blob/develop/src/test/java/com/epam/reportportal/junit/powermock/PowerMockNegativeTest.java

@HardNorth - The Java agent specification in the agent-java-junit build file should be revised to match the example shown in the README. Also, there's no need to override the transitive dependency of JUnit Foundation 12.3.0, as it already includes JUnit 4.13.1.
One thing that confuses me completely is the specification of JUnit Jupiter references (JUnit 5) in testImplementation entries of the agent-java-junit build file. This agent is very specifically targeted at JUnit 4. I don't know that this version mismatch is causing problems, but it certainly looks wrong.

@HardNorth - Sorry, I'm referring to the Gradle project file example. The agent specification for JUnit Foundation has been greatly simplified and avoids some issues that were caused by the prior formulation.
Referring to exclusion of JUnit transitive dependency, this is unnecessary and potentially problematic. JUnit Foundation works by installing hooks into JUnit 4 core classes via runtime code generation. This is performed by the Java agent and only affects test flows that are executed by these dynamically modified classes. If any of the classes that need to be hooked get loaded prior to the execution of the JUnit Foundation agent, the unmodified versions of these classes will be used instead. This means that the associated test lifecycle events will not fire.
You should be able to trace the execution of your test methods through JUnit Foundation.  Set a breakpoint on RunAnnouncer.testStarted(Description) and debug an affected PowerMock test to see if this ever gets called.

I'm actually already removed dependency exclusion. And I'm going to update readme file soon.
Ok. I'll post you back with the investigation details.

@HardNorth - I added PowerMock unit tests to the JUnit Foundation project, and it works as expected. The tests are declared as JUnit 4 @Test methods in a class that gets executed by a JUnitCore runner created by a TestNG @Test method in a different class.
I strongly suspect that the trouble you're experiencing is caused by the inclusion of the JUnit 5 API into your project to execute the JUnit 4 tests. This is either preventing JUnit Foundation from installing altered versions of core JUnit classes or bypassing the actual JUnit classes altogether.

@sbabcoc, OK, got you. Please give me few days on the next week, I need to investigate the case.

@sbabcoc Hello again.
I've prepared a very simple example project with two tests (one with PowerMock and one without):
https://github.com/HardNorth/junit-powermock-check
If i run it with: ./gradlew test
The result will be:
JUnitTestPowerMock > testPowerMock FAILED
    java.lang.AssertionError at JUnitTestPowerMock.java:23

2 tests completed, 1 failed

The assert which fails indicates that a test with PowerMock fire no events in a dummy listener.
So, the issue not in dependencies. Since there is almost no dependencies in this project.

@HardNorth  - Sorry for the inaccurate feedback. I swear I got this running, but I had a few errors in my execution. I now have a unit test the reproduces the issue, and the core challenge is the PowerMock is using a runner model that has been deprecated since JUnit 4.5 - which was released more than 12 years ago! This is a completely different API than JUnit Foundation was designed to support, and it would take a tremendous amount of effort to handle for this deprecated mechanism for running tests. There was actually a span of 6 years where these deprecated classes were pulled out of JUnit, but they were added back in to restore backward compatibility.

@sbabcoc NP, I understand your troubles. I just need a proper reason to my users. If no - than no. The reason seems legit to me. It's for you to decide whether it worth to support.

@HardNorth - There may be a way to do this via the @PowerMockRunnerDelegate annotation. I'm investigating this now.

Try adding this to your test class:
@PowerMockRunnerDelegate(Parameterized.class)

@HardNorth - This change gets things to start working, but execution blows up with a very confusing configuration error in the Settings API. I'll see if I can dig into this a bit more in the next few days to see if I can fix this configuration failure.

@HardNorth - OK, I found an easy fix... I'll have a new build posted later today.

@HardNorth - New release 12.5.0 has been published. Pay special attention to the NOTE and code example in the release description regarding the @PowerMockRunnerDelegate annotation.
Also, the verification in your example project still doesn't work, but this is due to a threading issue in your implementation. Your RUNNER_COUNTER needs to be thread-local (specifically InheritableThreadLocal) to avoid unintended instantiation of a new counter in the new thread spawned by PowerMockRunner.

Duplicating here our conversation:
@sbabcoc For PowerMock I have no success. So I wanted to clarify, what exact I need to update in tests? Just add @PowerMockRunnerDelegate(BlockJUnit4ClassRunner.class) ?
I did that in my tests: https://github.com/reportportal/agent-java-junit/commit/d17757e2394bb8ac79eb2f057e2c30a38f414891
But they fail if I run them :(
I’m seeing this in my console:
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.powermock.reflect.internal.WhiteboxImpl (file:/Users/vadzim_hushchanskou/.gradle/caches/modules-2/files-2.1/org.powermock/powermock-reflect/2.0.9/4bb9ed43e5221926fb86cae44b445de110a51d05/powermock-reflect-2.0.9.jar) to method java.lang.Object.clone()
WARNING: Please consider reporting this to the maintainers of org.powermock.reflect.internal.WhiteboxImpl
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
12:51:39.943 DEBUG c.n.a.j.Run - main - runFinished: org.junit.runners.BlockJUnit4ClassRunner@37df14d1
Exception in thread "main" java.lang.Error: org.apache.commons.configuration2.ex.ConfigurationRuntimeException: Incompatible result object: org.apache.commons.configuration2.PropertiesConfiguration@62b790a5
	at org.powermock.modules.junit4.internal.impl.DelegatingPowerMockRunner.run(DelegatingPowerMockRunner.java:158)
	at org.powermock.modules.junit4.common.internal.impl.JUnit4TestSuiteChunkerImpl.run(JUnit4TestSuiteChunkerImpl.java:117)
	at org.powermock.modules.junit4.common.internal.impl.AbstractCommonPowerMockRunner.run(AbstractCommonPowerMockRunner.java:57)
	at org.powermock.modules.junit4.PowerMockRunner.run(PowerMockRunner.java:59)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
	at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:69)
	at com.intellij.rt.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:33)
	at com.intellij.rt.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:220)
	at com.intellij.rt.junit.JUnitStarter.main(JUnitStarter.java:53)
Caused by: org.apache.commons.configuration2.ex.ConfigurationRuntimeException: Incompatible result object: org.apache.commons.configuration2.PropertiesConfiguration@62b790a5
	at org.apache.commons.configuration2.builder.BasicConfigurationBuilder.checkResultInstance(BasicConfigurationBuilder.java:728)
	at org.apache.commons.configuration2.builder.BasicConfigurationBuilder.createResultInstance(BasicConfigurationBuilder.java:448)
	at org.apache.commons.configuration2.builder.BasicConfigurationBuilder.createResult(BasicConfigurationBuilder.java:417)
	at org.apache.commons.configuration2.builder.BasicConfigurationBuilder.getConfiguration(BasicConfigurationBuilder.java:285)
	at org.apache.commons.configuration2.builder.fluent.Configurations.properties(Configurations.java:318)
	at com.nordstrom.automation.settings.SettingsCore.<init>(SettingsCore.java:136)
	at com.nordstrom.automation.junit.JUnitConfig.<init>(JUnitConfig.java:73)
	at com.nordstrom.automation.junit.JUnitConfig$1.initialValue(JUnitConfig.java:59)
	at com.nordstrom.automation.junit.JUnitConfig$1.initialValue(JUnitConfig.java:55)
	at java.base/java.lang.ThreadLocal.setInitialValue(ThreadLocal.java:195)
	at java.base/java.lang.ThreadLocal.get(ThreadLocal.java:172)
	at com.nordstrom.automation.junit.JUnitConfig.getConfig(JUnitConfig.java:82)
	at com.nordstrom.automation.junit.Run.fireRunStarted(Run.java:141)
	at com.nordstrom.automation.junit.Run.intercept(Run.java:57)
	at org.junit.runners.BlockJUnit4ClassRunner.run(BlockJUnit4ClassRunner.java)
	at org.powermock.modules.junit4.internal.impl.DelegatingPowerMockRunner$2.call(DelegatingPowerMockRunner.java:149)
	at org.powermock.modules.junit4.internal.impl.DelegatingPowerMockRunner$2.call(DelegatingPowerMockRunner.java:141)
	at org.powermock.modules.junit4.internal.impl.DelegatingPowerMockRunner.withContextClassLoader(DelegatingPowerMockRunner.java:132)
	at org.powermock.modules.junit4.internal.impl.DelegatingPowerMockRunner.run(DelegatingPowerMockRunner.java:141)
	... 8 more
Process finished with exit code 1

Duplicating here our conversation:
@sbabcoc For PowerMock I have no success. So I wanted to clarify, what exact I need to update in tests? Just add @PowerMockRunnerDelegate(BlockJUnit4ClassRunner.class) ?
I did that in my tests: https://github.com/reportportal/agent-java-junit/commit/d17757e2394bb8ac79eb2f057e2c30a38f414891
But they fail if I run them :(
I’m seeing this in my console:
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.powermock.reflect.internal.WhiteboxImpl (file:/Users/vadzim_hushchanskou/.gradle/caches/modules-2/files-2.1/org.powermock/powermock-reflect/2.0.9/4bb9ed43e5221926fb86cae44b445de110a51d05/powermock-reflect-2.0.9.jar) to method java.lang.Object.clone()
WARNING: Please consider reporting this to the maintainers of org.powermock.reflect.internal.WhiteboxImpl
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
12:51:39.943 DEBUG c.n.a.j.Run - main - runFinished: org.junit.runners.BlockJUnit4ClassRunner@37df14d1
Exception in thread "main" java.lang.Error: org.apache.commons.configuration2.ex.ConfigurationRuntimeException: Incompatible result object: org.apache.commons.configuration2.PropertiesConfiguration@62b790a5
	at org.powermock.modules.junit4.internal.impl.DelegatingPowerMockRunner.run(DelegatingPowerMockRunner.java:158)
	at org.powermock.modules.junit4.common.internal.impl.JUnit4TestSuiteChunkerImpl.run(JUnit4TestSuiteChunkerImpl.java:117)
	at org.powermock.modules.junit4.common.internal.impl.AbstractCommonPowerMockRunner.run(AbstractCommonPowerMockRunner.java:57)
	at org.powermock.modules.junit4.PowerMockRunner.run(PowerMockRunner.java:59)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
	at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:69)
	at com.intellij.rt.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:33)
	at com.intellij.rt.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:220)
	at com.intellij.rt.junit.JUnitStarter.main(JUnitStarter.java:53)
Caused by: org.apache.commons.configuration2.ex.ConfigurationRuntimeException: Incompatible result object: org.apache.commons.configuration2.PropertiesConfiguration@62b790a5
	at org.apache.commons.configuration2.builder.BasicConfigurationBuilder.checkResultInstance(BasicConfigurationBuilder.java:728)
	at org.apache.commons.configuration2.builder.BasicConfigurationBuilder.createResultInstance(BasicConfigurationBuilder.java:448)
	at org.apache.commons.configuration2.builder.BasicConfigurationBuilder.createResult(BasicConfigurationBuilder.java:417)
	at org.apache.commons.configuration2.builder.BasicConfigurationBuilder.getConfiguration(BasicConfigurationBuilder.java:285)
	at org.apache.commons.configuration2.builder.fluent.Configurations.properties(Configurations.java:318)
	at com.nordstrom.automation.settings.SettingsCore.<init>(SettingsCore.java:136)
	at com.nordstrom.automation.junit.JUnitConfig.<init>(JUnitConfig.java:73)
	at com.nordstrom.automation.junit.JUnitConfig$1.initialValue(JUnitConfig.java:59)
	at com.nordstrom.automation.junit.JUnitConfig$1.initialValue(JUnitConfig.java:55)
	at java.base/java.lang.ThreadLocal.setInitialValue(ThreadLocal.java:195)
	at java.base/java.lang.ThreadLocal.get(ThreadLocal.java:172)
	at com.nordstrom.automation.junit.JUnitConfig.getConfig(JUnitConfig.java:82)
	at com.nordstrom.automation.junit.Run.fireRunStarted(Run.java:141)
	at com.nordstrom.automation.junit.Run.intercept(Run.java:57)
	at org.junit.runners.BlockJUnit4ClassRunner.run(BlockJUnit4ClassRunner.java)
	at org.powermock.modules.junit4.internal.impl.DelegatingPowerMockRunner$2.call(DelegatingPowerMockRunner.java:149)
	at org.powermock.modules.junit4.internal.impl.DelegatingPowerMockRunner$2.call(DelegatingPowerMockRunner.java:141)
	at org.powermock.modules.junit4.internal.impl.DelegatingPowerMockRunner.withContextClassLoader(DelegatingPowerMockRunner.java:132)
	at org.powermock.modules.junit4.internal.impl.DelegatingPowerMockRunner.run(DelegatingPowerMockRunner.java:141)
	... 8 more
Process finished with exit code 1


Collect release notes

Collect PATCH and MINOR release notes from Travis CI when build is successfully merged into master and create new file with collected changelog in release_notes/ folder with name {TYPE}-{VERSION}.
Example:
release_notes:
-- PATCH-0.2.21
-- PATCH-0.2.22
-- MINOR-0.3.0
-- PATCH-0.3.1

There is a proposal to save release notes not in a file but as a git tag message

We need to have a simple way to collect a lot of release notes (200+ commits) for each release. Do you think git tag message can simplify this action?
Also it will be good thing collect notes by MAJOR version. For example: release_notes/1.0.0/PATCH-1.1.0


update broken link on ipc-main-process page

Oh, good catch, thank you!
Actually the docs now pull webContents into its own doc so the url should be:
https://github.com/atom/electron/blob/master/docs/api/web-contents.md#webcontentssendchannel-args

Started with this branch and went ahead and took care of all the web-contents links in #2757. Thanks @destan! :boom:


Listmonk fixing wrong types

Description of changes
Listmonk saves its config in the postgres as json. This pull request removes useless type restrictions that hinder to represent the config.

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

What config are you trying to represent? Would it be feasible to complete the type instead?


Update testcontainers-scala-dynalite, ... to 0.40.10

Updates

com.dimafeng:testcontainers-scala-dynalite
com.dimafeng:testcontainers-scala-scalatest

from 0.40.9 to 0.40.10.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.dimafeng" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "com.dimafeng" }
}]

labels: library-update, early-semver-minor, semver-spec-patch, commit-count:1

Superseded by #349.


Consider setting no server-description by default

Currently we set SERVER_DESCRIPTION="Powered by DST Academy." and although it seemed to be a nice default value in the beginning, some minor problems arise with this decision.
First, people might don't want a server description, which doesn't reflect their intention for the server. Simply said, they don't want to have DST:A associated with their server.
Second, it happens people run servers, we don't want to be related to. In other words, we don't want to be connected to people/servers, which reflect thoughts and/or values on us we don't belong to.
Setting no server description by default seems a better choice after all.

I think that it's a good way to get a bit of impcat. If you care about your server you are going to set a description. If you don't care... well, the people is goint to see that there's something called "DST Academy".


feat: support fax

Coverage decreased (-0.1%) to 37.187% when pulling 0ad7b0d7053b4c8aaea34171aab5f96734808bb2 on ele828:sync-3-3 into 93216221f9f6f9dec88eb4dbd1ef377b7b3cb551 on ringcentral:master.

Something went wrong. Investigate!


[Admin] Publish

Learn Build status updates of commit e3491a5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/create-sso-office-add-ins-aspnet.md
:white_check_mark:Succeeded
View

docs/images/SelectHost.JPG
:white_check_mark:Succeeded
n/a (file deleted or renamed)

docs/images/select-host.png
:white_check_mark:Succeeded
View

docs/includes/register-sso-add-in-aad-v2-include.md
:white_check_mark:Succeeded
View

docs/includes/sso-tutorial-prereqs.md
:white_check_mark:Succeeded
n/a (file deleted or renamed)

docs/outlook/get-or-set-the-location-of-an-appointment.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Last.fm albums with no artwork are being shown.

This issue only occurs on Last.fm. I assume this is because Spotify always returns album artwork and Last.fm does not.
See the attached screenshot for an example of empty slots when using Last.fm top albums. Can these slots either be prioritised for artwork updates or retried upon first loading.

Thanks for the work on such a cool screensaver!

Yes indeed. Last.fm Image catalogue is not as rich as from Spotify. I can take a look at adding this feature, when I got time.

Try out 1.1.3. It should fix this issue.

Yep, perfect. Thanks very much. Will also update the homebrew repo.


axistream_expect times out immediately (questasim 2019.1)

Hello,
I am trying to make a testbench for an entity that generates AXI stream packages (32b + 4b tuser).
The problem I am struggling with is that axistream_expect times out immediately with the following message axistream_expect(8B) while executing axistream_receive=> Failed. Timeout while waiting for valid data. 'expecting axi stream data'  [1]
This message happens while absolutely nothing happened yet on axistream_vvc_if. (tready is '0', clock is running).
Some relevant code snippets:
signal axistream_vvc_if : t_axistream_if(tdata(31 downto 0), tkeep(3 downto 0), tuser(3 downto 0), tstrb(3 downto 0), tid(0 downto 0), tdest(0 downto 0)) := init_axistream_if_signals(false, 32, 4, 1, 1);
checker : process
begin
    checker_done <= false;
    await_uvvm_initialization(VOID);
    axistream_expect(AXISTREAM_VVCT, 0, TESTDATA0,  "expecting axi stream data");
    await_completion(AXISTREAM_VVCT, 0, 1200 * C_CLK40_PERIOD);
    checker_done <= true;
    wait;
end process;

The VVC
            axi_stream_vvc_I: entity bitvis_vip_axistream.axistream_vvc
                generic map (
                    GC_VVC_IS_MASTER => false,
                    GC_DATA_WIDTH => 32,
                    GC_USER_WIDTH => 4,
                    GC_ID_WIDTH => 1,
                    GC_DEST_WIDTH => 1,
                    GC_INSTANCE_IDX => 0,
                    GC_AXISTREAM_BFM_CONFIG => GC_AXISTREAM_BFM_CONFIG
                )
                port map (
                    clk => m_axis_aclk,
                    axistream_vvc_if => axistream_vvc_if
                );

Here is a screenshot of the axistream VVC waveform. It times out on the right of the waveform, while nothing on the axi stream interface has happened yet.

Hi,
From what I can see in the waveform it looks like your checker process executes axistream_expect() (tready = '1') but there is no data coming in (tvalid = '0') so it times out.
The default timeout in the Axistream BFM config is 100 cycles (max_wait_cycles), you can try increasing it accordingly to your test.
Best regards,
Erick

Hello Eric,
tready was '1' because I set that as the default value in the BFM config. Increasing max_wait_cycles solved the issue.
Thanks!


Dot notation on where-bound identifier fails

example : Nat :=
  let n := 0
  -- last one fails
  n.succ + (m |>.succ) + m.succ
where
  m := 1

We currently disable dot notation for (potentially) recursive declarations being defined. Recall that where is sugar for let rec.
The reason for this restriction are examples such as
def foo.aux := 1
def foo : Nat → Nat
  | n => foo.aux -- We don't want `foo.aux` to be interpreted as `(foo).aux`

The example above looks artificial, but we had the following issue in the past
namespace Precategory
  inductive Arity : Type
    | left | right | mul | bottom

  def signature : Sum Arity 𝟎 → Nat := ...
end Precategory

def Precategory : Type (u + 1) :=
  Alg.{0, 0, u, 0} Precategory.signature  --- HERE

Possible improvement: instead of disallowing dot notation for potentially recursive declarations being defined, we just stop the local name resolution if there is a global name that would be shadowed. Cons: some users may find it confusing.

Thanks for the explanation, I didn't even consider this interaction.

Cons: some users may find it confusing.

I'm relatively certain it would be an improvement in the eyes of a majority, users do not think of foo as a local variable. On the flip side, users may not think of a where-bound name as something that eventually becomes a global decl, but in that case collisions with the environment seem incredibly unlikely anyway.


Use files in package.json

Fixes #1033
Before:

After:

Difference is .editorconfig, .babelrc, CNAME, CODE_OF_CONDUCT and PATRONS. Can add back if you want. I'm also guessing dist is supposed to be included for npmcdn etc.
A whitelist is much easier to manage than a blacklist, as can be seen in the diff of this PR

Looks good to me, thank you.


use gcp metadata for all the cases

Please provide a description of this PR:
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ ] Ambient
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@aryan16: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
fc450e196153fd8520768a0870dbb822528da7ae
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test unit-tests-arm64

@aryan16: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
7c97c1cd41a291d0a3c71b0fa76fbd9b82c05932
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@aryan16: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
7c97c1cd41a291d0a3c71b0fa76fbd9b82c05932
link
true
/test gencheck

lint_istio
7c97c1cd41a291d0a3c71b0fa76fbd9b82c05932
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

So just to make sure I understand the workflow here:

If the GCP_METADATA env variable is set, use that env variable
If unset, fall back to discovery to query the metadata server for information
If that fails, go with default values (unset?)

Is that correct?
One gap I think I might see is -- how does this code handle GCP_METADATA if the root code runs the discovery bit and identifies the platform as AWS (as an example)? Will it still use GCP_METADATA or will it just use the AWS discovery code and ignore the env variable?

Yeah the flow is correct
And, I don't think this code will ever run for any other platform other than GCP. Previously it was calling Metadata() which was doing something similar under the hood (parsing GCP_METADATA).

So just to make sure I understand the workflow here:

If the GCP_METADATA env variable is set, use that env variable
If unset, fall back to discovery to query the metadata server for information
If that fails, go with default values (unset?)

Is that correct?
One gap I think I might see is -- how does this code handle GCP_METADATA if the root code runs the discovery bit and identifies the platform as AWS (as an example)? Will it still use GCP_METADATA or will it just use the AWS discovery code and ignore the env variable?

Yeah the flow is correct And, I don't think this code will ever run for any platform other than GCP. Previously it was calling Metadata() which was doing something similar under the hood (parsing GCP_METADATA).


Gui cns

@salvadord @joewgraham we need this for the release
cc: @ddelpiano @filippomc

looks ok to me ... @joe?


Rustup

Ah, I should probably do this with a josh sync. I'll do that in the morning.

Thanks!
@bors r+

:pushpin: Commit 010f2dc0491e8f51fceb66a8f31120cdf4eba463 has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit 010f2dc0491e8f51fceb66a8f31120cdf4eba463 with merge 0ba1f4a0a62f02cefaeaa15bf55b1d890fb60a68...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing 0ba1f4a0a62f02cefaeaa15bf55b1d890fb60a68 to master...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing 0ba1f4a0a62f02cefaeaa15bf55b1d890fb60a68 to master...


npm install got error on vagrant

NPM version: 3.10.2
NODE version: v4.4.0
I got this error when run npm install:
npm ERR! Linux 3.13.0-85-generic
npm ERR! argv "/home/vagrant/.nvm/versions/node/v4.4.0/bin/node" "/home/vagrant/.nvm/versions/node/v4.4.0/bin/npm" "install"
npm ERR! node v4.4.0
npm ERR! npm  v3.10.2
npm ERR! path /vagrant/mern-starter/node_modules/nyc/node_modules/foreground-child/node_modules/which/bin/which
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod

npm ERR! enoent ENOENT: no such file or directory, chmod '/vagrant/mern-starter/node_modules/nyc/node_modules/foreground-child/node_modules/which/bin/which'
npm ERR! enoent ENOENT: no such file or directory, chmod '/vagrant/mern-starter/node_modules/nyc/node_modules/foreground-child/node_modules/which/bin/which'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! Please include the following file with any support request:
npm ERR!     /vagrant/mern-starter/npm-debug.log

then I try to run npm start
And get this
/vagrant/mern-starter/node_modules/babel-core/lib/transformation/file/index.js:591
      throw err;
      ^

Error: /vagrant/mern-starter/server/server.js: Cannot find module '../features'
    at Function.Module._resolveFilename (module.js:325:15)
    at Function.Module._load (module.js:276:25)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (/vagrant/mern-starter/node_modules/caniuse-api/dist/index.js:19:32)
    at Module._compile (module.js:409:26)
    at Module._extensions..js (module.js:416:10)
    at Object.require.extensions.(anonymous function) [as .js] (/vagrant/mern-starter/node_modules/babel-register/lib/node.js:166:7)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
[nodemon] app crashed - waiting for file changes before starting...

Try running
npm cache clean
rm -rf node_modules
npm install

Let me know if this solves your problem.

I manage to get it to work for my Vagrant on Windows while running Git Bash with adminstrative right on this config

Linux 3.13.0-65-generic
node v4.4.7
npm  v3.10.5

Then I try to reproduce this problem by cloning the repo into a new folder and do npm install
Then I got this error:
npm ERR! Linux 3.13.0-65-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v4.4.7
npm ERR! npm  v3.10.5
npm ERR! path /vagrant/node_modules/nyc/node_modules/test-exclude/node_modules/read-pkg-up/node_modules/read-pkg/node_modules/normalize-package-data/node_modules/semver/bin/semver
npm ERR! code ENOENT
npm ERR! errno^C -2
npm ERR! syscall chmod

npm ERR! enoent ENOENT: no such file or directory, chmod '/vagrant/node_modules/nyc/node_modules/test-exclude/node_modules/read-pkg-up/node_modules/read-pkg/node_modules/normalize-package-data/node_modules/semver/bin/semver'
npm ERR! enoent ENOENT: no such file or directory, chmod '/vagrant/node_modules/nyc/node_modules/test-exclude/node_modules/read-pkg-up/node_modules/read-pkg/node_modules/normalize-package-data/node_modules/semver/bin/semver'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent

So I try to do
npm cache clean
rm -rf node_modules
npm install

and I got the exact same error that @khietvovan got
I have tried cleaning the cache and removing node_modules repeatedly. I got different error and eventually come back to npm ERR! enoent ENOENT: no such file or directory, chmod '/vagrant/mern-starter/node_modules/nyc/node_modules/foreground-child/node_modules/which/bin/which'

Could this be relevant?
https://github.com/Hashnode/mern-cli/issues/16

@amoshydra Glad, you figured it out. @khietvovan Even after trying @amoshydra suggestion, you are getting the error, feel free to open it.

Thank you. I'm moving to use Mern in Docker. But I will try with Vagrant again.

I had a similar problem but the error was related to syscall open rather than syscall chmod. There is some problem with shared folder as stated above. I followed @amoshydra's steps above, without running chmod, and modules installed. Thanks @amoshydra!
Still the root cause of this issue is not known! Hope someone can find it.


Grid layout quirks

The new grid layout from Bootstrap 5.3 works well in most cases, but I've noticed a few minor issues we may want to resolve before releasing a new version of the plug-in.
Narrow ToC area
The current grid layout leaves little room for the ToC (even at large desktop resolutions), so long headings often break to several lines. This clipping sometimes also affects the ToC link focus frame, which is cut off on the right edge:

Focus frame
🎗 That focus frame seems to appear unnecessarily at times (rather than when invoked with TAB) but that's a separate issue.
Empty right column
At desktop resolutions, the current grid layout includes an empty right column, presumably inherited from the Bootstrap docs layout, which uses that space for local “On this page” navigation:

Since we don't generate that local navigation layer by default, it seems odd to reserve the space, particularly when the left ToC sidebar is so constrained.
I'm aware of the need to balance the layout on the page, and keep body content line lengths readable on large screens, but we can probably improve this a bit without breaking anything.
(I can look into these issues myself at some point, but I need to focus on the docs for DITA-OT 4.1 right now, so might not get to it until after that's released.)

a9a98b12 fixes the reserved whitespace. The relevant CSS should only be added if scrollspy is in use.

@infotexture - I think this can also be closed.

While https://github.com/infotexture/dita-bootstrap/commit/a9a98b12fbbe27a3331873554b1ea1079f0969e9 fixes the whitespace reserved for the scroll spy navigation area per https://github.com/infotexture/dita-bootstrap/issues/89#issuecomment-1582237274, we might want to consider re-centering the content below the navigation header if no scroll spy ToC is enabled.
This happens automatically at larger desktop breakpoints, but we might want to use that same approach at earlier breakpoints to keep content and menu bar better aligned, and line lengths readable.
Note how menu bar width changes at various breakpoints, but content doesn't follow:

Another minor quirk is that at wider mobile screen sizes (when the TOC is collapsed), there is a considerable left margin in the content area:

It stems from the CSS setting a max-width: 760px and margin-inline: auto on .bs-main.
Not sure if this intentional, and it doesn't even look that bad, honestly. Just thought I'd mention it.

Thanks to @lakokkonen for reporting and to @jason-fox for fixing this in #161. 🙏

This is a closed issue, but continuing on this subject a bit:
I've experimented with adding a parameter that would let the user determine the size of the content container. The available options are the Bootstrap container, container-fluid and sized containers sm-xxl. That way the user could match the main layout's sizing and behaviour with the one on a custom header.
And by using container-fluid it would be easier to achieve a layout where the TOC is always on the left:

The parameter also controls the size of the menubar-TOC, so that everything is aligned.

Sounds like a good idea - updateplugin.xml and insertParameters.xml to add a new parameter and then add new <xsl:param> with the select matching the existing default to allow for overrides. I did something similar with <note> elements in #83

@jason-fox Yes, that's how I got it working. And the default could be container-xxl, so everything should by default work as before.
Any preferences about the parameter name? Currently it's content.container.size.
I can do a pull request over the weekend at some point so you can check it out.

I'd go for something like bootstrap.css.container.size - most of the CSS parameters have a  bootstrap.css. prefix and as you said, its not just the id="content" which is the chapter body, but the parameter affects the Sub Menu as well (if present).
I wouldn't change the  hard-coded defaults in the navbar includes, but may be add a comment line to

hdr.navbar.default.xml
hdr.navbar.example.xml
hdr.topbar.example.xml

Explaining that they need to be changed if you alter the container size too.


feedback: Didnt complete the request

Version
v1.2.2
Areas for Improvement

[ ] UI/UX
[ ] Onboarding
[ ] Docs
[ ] Chat
[ ] Commands
[ ] Context
[X] Response Quality
[ ] Other

What needs to be improved? Please describe how this affects the user experience.
It was 50% right on the answer it gave, but it seemed to give up halfway through the code it was creating.
Describe the solution you'd like to see
Id like it to do the whole request
Describe any alternatives that could be considered
It may have to do with the size of the file, it wasn't an insane amount of code so I would have expected it to be able to do it.
Additional context
No response

thanks for the feedback! we're aware of this issue and is working on expanding the context token output, going to close this for now