Update dependency jakarta.enterprise:jakarta.enterprise.cdi-api to v4

This PR contains the following updates:

Package
Type
Update
Change

jakarta.enterprise:jakarta.enterprise.cdi-api (source)
runtime
major
3.0.1 -> 4.1.0

Release Notes

cdi-spec/cdi (jakarta.enterprise:jakarta.enterprise.cdi-api)
v4.1.0
Compare Source
What's Changed

add BuildServicesResolver.setBuildServices() by @Ladicek in https://github.com/jakartaee/cdi/pull/617
Bump nokogiri from 1.13.4 to 1.13.6 in /docs by @dependabot in https://github.com/jakartaee/cdi/pull/614
Make sure CDI and BuildServicesResolves both guard against repeated i… by @manovotn in https://github.com/jakartaee/cdi/pull/619
Correct GH Pages link in README by @manovotn in https://github.com/jakartaee/cdi/pull/626
Clarify ambiguity resolution during dynamic lookup by @Ladicek in https://github.com/jakartaee/cdi/pull/627
Improve section numbering by @Ladicek in https://github.com/jakartaee/cdi/pull/634
docs/README  by @ekimike in https://github.com/jakartaee/cdi/pull/643
Use a vendor neutral link to the license text by @waynebeaton in https://github.com/jakartaee/cdi/pull/651
Remove vendor notices by @waynebeaton in https://github.com/jakartaee/cdi/pull/654
Remove additional vendor references by @waynebeaton in https://github.com/jakartaee/cdi/pull/655
Explicitly state that classes implementing BuildCompatibleExtension i… by @manovotn in https://github.com/jakartaee/cdi/pull/664
Wording improvements by @Ladicek in https://github.com/jakartaee/cdi/pull/670
Address the javadoc errors under jdk17 by @starksm64 in https://github.com/jakartaee/cdi/pull/672
Introduce BeanContainer.getContexts() to be able to get hold of all context objects, even if inactive by @manovotn in https://github.com/jakartaee/cdi/pull/629
Improve AnnotationLiteral javadoc by @Ladicek in https://github.com/jakartaee/cdi/pull/657
Fix missing wording about priority on stereotypes by @Ladicek in https://github.com/jakartaee/cdi/pull/674
Bump CDI version to 4.1 and place EL integration API in a new supplemental artifact by @Ladicek in https://github.com/jakartaee/cdi/pull/644
Fix two small wording mistakes by @Ladicek in https://github.com/jakartaee/cdi/pull/675
Move the specification of BeanManager.getInjectableReference() to CDI Full by @Ladicek in https://github.com/jakartaee/cdi/pull/676
Add specification text for BeanContainer.getContexts() by @Ladicek in https://github.com/jakartaee/cdi/pull/685
Fix Javadoc for createInstance validity by @Azquelt in https://github.com/jakartaee/cdi/pull/689
Fix guards against repeated external sets of SPI implementations by @Ladicek in https://github.com/jakartaee/cdi/pull/690
Clarify the relationship between CDI Lite and CDI Full specifications by @Ladicek in https://github.com/jakartaee/cdi/pull/692
Specify behavior for sealed types by @Ladicek in https://github.com/jakartaee/cdi/pull/693
Method invokers by @Ladicek in https://github.com/jakartaee/cdi/pull/639
Allow setting CDI SPI implementations repeatedly by @Ladicek in https://github.com/jakartaee/cdi/pull/696
Relax the scope requirement for public fields by @Ladicek in https://github.com/jakartaee/cdi/pull/698
small improvements and clarifications in Build Compatible Extensions and Language Model by @Ladicek in https://github.com/jakartaee/cdi/pull/701
Fix typo in javadoc by @bmscomp in https://github.com/jakartaee/cdi/pull/704
Update CI setup - add JDK 21, bump versions on actions by @manovotn in https://github.com/jakartaee/cdi/pull/706
Specify @Priority on producers by @Ladicek in https://github.com/jakartaee/cdi/pull/699
Remove mention of context activation from AfterDeploymentValidation event by @manovotn in https://github.com/jakartaee/cdi/pull/705
[StepSecurity] Apply security best practices by @step-security-bot in https://github.com/jakartaee/cdi/pull/678
Bump actions/setup-java from 3.13.0 to 4.0.0 by @dependabot in https://github.com/jakartaee/cdi/pull/711

Cleanup in prep for the 4.1.0-M1 release by @starksm64 in https://github.com/jakartaee/cdi/pull/710

Updates for deprecation of the Managed Beans specification, #679 by @starksm64 in https://github.com/jakartaee/cdi/pull/709
Updates for Jakarta Bean Validation to Jakarta Validation name change, #680 by @starksm64 in https://github.com/jakartaee/cdi/pull/708
Bump nokogiri from 1.13.6 to 1.14.3 in /docs by @dependabot in https://github.com/jakartaee/cdi/pull/662
Bump webrick from 1.7.0 to 1.8.1 in /docs by @dependabot in https://github.com/jakartaee/cdi/pull/716
Change Jakarta Server Faces to Jakarta Faces, #681 by @starksm64 in https://github.com/jakartaee/cdi/pull/724
Bump github-pages from 219 to 225 in /docs by @dependabot in https://github.com/jakartaee/cdi/pull/718
Add API for programmatic access to assignability rules for observer methods and typesafe resolution. by @manovotn in https://github.com/jakartaee/cdi/pull/700
Update jakarta.el to 6.0.0-M1 and update osgi manifest export/imports, #732 by @starksm64 in https://github.com/jakartaee/cdi/pull/733
Bump github-pages and jekyll in /docs by @dependabot in https://github.com/jakartaee/cdi/pull/728
Bump org.testng:testng from 7.7.0 to 7.8.0 by @dependabot in https://github.com/jakartaee/cdi/pull/727
Formatting rules by @manovotn in https://github.com/jakartaee/cdi/pull/731
Bump org.apache.maven.plugins:maven-compiler-plugin from 3.8.1 to 3.12.1 by @dependabot in https://github.com/jakartaee/cdi/pull/739
Bump org.testng:testng from 7.8.0 to 7.9.0 by @dependabot in https://github.com/jakartaee/cdi/pull/740
Tweaks to Bean and Event Assignability API by @Azquelt in https://github.com/jakartaee/cdi/pull/742
Improve precision of the bean and event assignability API specification by @Ladicek in https://github.com/jakartaee/cdi/pull/744
Bump org.asciidoctor:asciidoctor-maven-plugin from 2.2.4 to 2.2.5 by @dependabot in https://github.com/jakartaee/cdi/pull/743
Bump org.asciidoctor:asciidoctorj from 2.5.10 to 2.5.11 by @dependabot in https://github.com/jakartaee/cdi/pull/738
Bump org.asciidoctor:asciidoctorj-pdf from 2.3.9 to 2.3.10 by @dependabot in https://github.com/jakartaee/cdi/pull/737
Initial specification text for method invokers by @Ladicek in https://github.com/jakartaee/cdi/pull/697
Remove references to the removed jakarta.annotation.ManagedBean #750 by @starksm64 in https://github.com/jakartaee/cdi/pull/751
Don't delcare overview.html as a resource so it doesn't get included in source jar by @Azquelt in https://github.com/jakartaee/cdi/pull/745
Add missing copyright headers to Java source files by @Ladicek in https://github.com/jakartaee/cdi/pull/747
Add missing copyright header to InvokerFactory.java by @Ladicek in https://github.com/jakartaee/cdi/pull/753
Bump org.apache.rat:apache-rat-plugin from 0.16 to 0.16.1 by @dependabot in https://github.com/jakartaee/cdi/pull/752
Improve specification of BeanManager.isMatchingBean() and isMatchingEvent() by @Ladicek in https://github.com/jakartaee/cdi/pull/748
Set a version for the resources plugin by @Azquelt in https://github.com/jakartaee/cdi/pull/757
Document and add copyright headers by @Azquelt in https://github.com/jakartaee/cdi/pull/756
Initial specification text for invoker lookups by @Ladicek in https://github.com/jakartaee/cdi/pull/749
Simply remove the Jakarta EE feature discussion by @starksm64 in https://github.com/jakartaee/cdi/pull/755
Bump org.asciidoctor:asciidoctorj-pdf from 2.3.10 to 2.3.12 by @dependabot in https://github.com/jakartaee/cdi/pull/761
Bump org.asciidoctor:asciidoctor-maven-plugin from 2.2.5 to 3.0.0 by @dependabot in https://github.com/jakartaee/cdi/pull/765
Bump nokogiri from 1.15.5 to 1.16.2 in /docs by @dependabot in https://github.com/jakartaee/cdi/pull/758
Bring copyright headers into agreement with NOTICE by @Azquelt in https://github.com/jakartaee/cdi/pull/762
Bump github-pages and jekyll in /docs by @dependabot in https://github.com/jakartaee/cdi/pull/764
Bump org.asciidoctor:asciidoctorj-pdf from 2.3.12 to 2.3.13 by @dependabot in https://github.com/jakartaee/cdi/pull/767
Small corrections to project information files by @Azquelt in https://github.com/jakartaee/cdi/pull/766
fix license headers and some other small things in the website by @Ladicek in https://github.com/jakartaee/cdi/pull/773
Revert incorrect change in ambiguity resolution by @Ladicek in https://github.com/jakartaee/cdi/pull/772
Correct the javadoc warnings seen under JDK 17 by @starksm64 in https://github.com/jakartaee/cdi/pull/775
add blog post about what's new in CDI 4.1 by @Ladicek in https://github.com/jakartaee/cdi/pull/774
Allow relaxing invoker lookup rules for asynchronous methods by @Ladicek in https://github.com/jakartaee/cdi/pull/768
improve javadoc by @Ladicek in https://github.com/jakartaee/cdi/pull/776
Bump actions/setup-java from 4.0.0 to 4.1.0 by @dependabot in https://github.com/jakartaee/cdi/pull/778
Update the changes spec section for 4.1 by @Azquelt in https://github.com/jakartaee/cdi/pull/781
Update to EE 11 final api dependencies by @starksm64 in https://github.com/jakartaee/cdi/pull/782
Restore the issue templates by @starksm64 in https://github.com/jakartaee/cdi/pull/784
Move EE dependency version properties to parent pom by @starksm64 in https://github.com/jakartaee/cdi/pull/787
Add a beans_4_1.xsd file and prepare to replace the staged 4.1.0 api jar. by @starksm64 in https://github.com/jakartaee/cdi/pull/793

New Contributors

@ekimike made their first contribution in https://github.com/jakartaee/cdi/pull/643
@waynebeaton made their first contribution in https://github.com/jakartaee/cdi/pull/651
@Azquelt made their first contribution in https://github.com/jakartaee/cdi/pull/689
@bmscomp made their first contribution in https://github.com/jakartaee/cdi/pull/704
@step-security-bot made their first contribution in https://github.com/jakartaee/cdi/pull/678

Full Changelog: https://github.com/jakartaee/cdi/compare/4.0.1...4.1.0
v4.0.1
Compare Source
What's Changed

Clarify handling exceptions during async events by @manovotn in https://github.com/jakartaee/cdi/pull/601
Remove duplicate phrase by @anthonyvdotbe in https://github.com/jakartaee/cdi/pull/604
Remove dependency on JTA API by @manovotn in https://github.com/jakartaee/cdi/pull/609
Bump nokogiri from 1.13.3 to 1.13.4 in /docs by @dependabot in https://github.com/jakartaee/cdi/pull/603
Remove javadoc dependency on EJB by @manovotn in https://github.com/jakartaee/cdi/pull/612

New Contributors

@anthonyvdotbe made their first contribution in https://github.com/jakartaee/cdi/pull/604

Full Changelog: https://github.com/jakartaee/cdi/compare/4.0.0...4.0.1
v4.0.0
What's Changed

Update version to snapshot by @manovotn in https://github.com/jakartaee/cdi/pull/450
Add EJB dependency only as JavaDoc dep. by @manovotn in https://github.com/jakartaee/cdi/pull/449
[Issue-457] Observer resolution - assignability clarification by @gaol in https://github.com/jakartaee/cdi/pull/458
Throw an exception without setting configuredProvider to null when ge… by @benjamin-confino in https://github.com/jakartaee/cdi/pull/462
Fix XML descriptor in documentation example by @Thihup in https://github.com/jakartaee/cdi/pull/463
Refer to Jakarta DI instead of JSR330 by @Cousjava in https://github.com/jakartaee/cdi/pull/466
Removal of deprecated bits for next major version by @manovotn in https://github.com/jakartaee/cdi/pull/473
Change development version to 4.0.0-SNAPSHOT. by @manovotn in https://github.com/jakartaee/cdi/pull/475
cdi-468 Split Spec doc to introduce CDI Lite by @antoinesd in https://github.com/jakartaee/cdi/pull/470
Draft Lite version of BeanManager. by @manovotn in https://github.com/jakartaee/cdi/pull/471
initial Build Compatible Extension API proposal by @Ladicek in https://github.com/jakartaee/cdi/pull/451
Correction to wording of EventMetadata#getInjectionPoint by @manovotn in https://github.com/jakartaee/cdi/pull/499
Add getBeanContainer() method to SeContainer for consistency by @graemerocher in https://github.com/jakartaee/cdi/pull/501
Create GH actions file by @manovotn in https://github.com/jakartaee/cdi/pull/503
Start cleanup of AnnotationTarget by @graemerocher in https://github.com/jakartaee/cdi/pull/507
remove App{Archive,ArchiveConfig,Deployment}, rename AppArchiveBuilder and ContextBuilder by @Ladicek in https://github.com/jakartaee/cdi/pull/506
remove Annotations and add AnnotationBuilder by @Ladicek in https://github.com/jakartaee/cdi/pull/508
remove AnnotationMember and rename AnnotationMemberValue by @Ladicek in https://github.com/jakartaee/cdi/pull/509
add SCM info to the POM by @Ladicek in https://github.com/jakartaee/cdi/pull/510
extension API improvements by @Ladicek in https://github.com/jakartaee/cdi/pull/511
Make AnnotationLiteral lazy by @graemerocher in https://github.com/jakartaee/cdi/pull/514
Cleanup Types interface / add Type.ofClass(String) by @graemerocher in https://github.com/jakartaee/cdi/pull/513
Change definitons of explicit/implicit archive, add notion about back… by @manovotn in https://github.com/jakartaee/cdi/pull/516
improve extension API documentation and resolve some open questions by @Ladicek in https://github.com/jakartaee/cdi/pull/515
Initial beans_4_0.xsd by @starksm64 in https://github.com/jakartaee/cdi/pull/517
improve extension API documentation and resolve some open questions by @Ladicek in https://github.com/jakartaee/cdi/pull/520
fix SyntheticObserverBuilder copy&paste mistake by @Ladicek in https://github.com/jakartaee/cdi/pull/522
Remove TODO referring to singleton as potential bean defining annotat… by @manovotn in https://github.com/jakartaee/cdi/pull/523
Replace BeanManager#getEvents with reference to BeanContainer. by @manovotn in https://github.com/jakartaee/cdi/pull/525
Align wording in unsatisfied and ambig dependencies with that in ambi… by @manovotn in https://github.com/jakartaee/cdi/pull/526
Allow using @Priority within stereotypes. by @manovotn in https://github.com/jakartaee/cdi/pull/524
API changes for allowing @Priority on stereotypes by @Ladicek in https://github.com/jakartaee/cdi/pull/527
Adjust wording of specification and API around @Priority usage on ste… by @manovotn in https://github.com/jakartaee/cdi/pull/531
add BeanConfigurator.priority by @Ladicek in https://github.com/jakartaee/cdi/pull/532
add specification text for BeanConfigurator.priority by @Ladicek in https://github.com/jakartaee/cdi/pull/533
improve extension API by @Ladicek in https://github.com/jakartaee/cdi/pull/529
extension API improvements by @Ladicek in https://github.com/jakartaee/cdi/pull/536
Programmatic lookup improvements, introduce Handle interface. by @manovotn in https://github.com/jakartaee/cdi/pull/534
Address the TODO in preface. by @manovotn in https://github.com/jakartaee/cdi/pull/538
Address TODO in inter-module injection. by @manovotn in https://github.com/jakartaee/cdi/pull/537
Explicitly state that Java SE impl of CDI has to be Full implementation. by @manovotn in https://github.com/jakartaee/cdi/pull/539
Decide on other mentions of Full-only concepts in the CDI Lite spec p… by @manovotn in https://github.com/jakartaee/cdi/pull/541
Address remaining TODOs for passivation mentions. by @manovotn in https://github.com/jakartaee/cdi/pull/542
Introduce observable CDI events representing container state. by @manovotn in https://github.com/jakartaee/cdi/pull/543
improve extension API and resolve all remaining open questions by @Ladicek in https://github.com/jakartaee/cdi/pull/544
Change BeanManager treatment in CDI Lite by @Ladicek in https://github.com/jakartaee/cdi/pull/547
CDI Lite packaging, deployment and lifecycle specification by @Ladicek in https://github.com/jakartaee/cdi/pull/546
Describe in more depth what kind of interception is supported in Lite. by @manovotn in https://github.com/jakartaee/cdi/pull/548
Change headers and nested lists to markdown syntax. by @manovotn in https://github.com/jakartaee/cdi/pull/550
Correct the readme url in 2021-10-25-pages-here.md by @starksm64 in https://github.com/jakartaee/cdi/pull/551
Remove the notion of version from Packaging and deployment for CDI Full by @manovotn in https://github.com/jakartaee/cdi/pull/549
Add a recommendation for bean archive portability between Lite and Full by @Ladicek in https://github.com/jakartaee/cdi/pull/552
Adjust Handle.get() behavior - throw exception if attempting to get()… by @manovotn in https://github.com/jakartaee/cdi/pull/555
Separate the language model to a dedicated module by @Ladicek in https://github.com/jakartaee/cdi/pull/553
Clarify how conflicting default scopes and priorities on stereotypes work by @Ladicek in https://github.com/jakartaee/cdi/pull/557
Language model only returns runtime-retained annotations in build compatible extensions by @Ladicek in https://github.com/jakartaee/cdi/pull/554
Update asciidoc plugins, config by @starksm64 in https://github.com/jakartaee/cdi/pull/559
Language model and build compatible extensions API clarifications by @Ladicek in https://github.com/jakartaee/cdi/pull/560
Fix javadoc by @Ladicek in https://github.com/jakartaee/cdi/pull/561
Allow @Enhancement to not restrict the types based on annotations by @Ladicek in https://github.com/jakartaee/cdi/pull/566
Make the return type of Instance.handles() covariant by @Ladicek in https://github.com/jakartaee/cdi/pull/570
Remove Enhancement.BeanDefiningAnnotations by @Ladicek in https://github.com/jakartaee/cdi/pull/569
Specify that duplicate type discovery is non-portable by @Ladicek in https://github.com/jakartaee/cdi/pull/571
Add a blog post on Build Compatible Extensions by @Ladicek in https://github.com/jakartaee/cdi/pull/572
Specify treatment of invalid @Enhancement and @Registration by @Ladicek in https://github.com/jakartaee/cdi/pull/576
Add module-info to the api artifacts, update to Java SE 11 by @starksm64 in https://github.com/jakartaee/cdi/pull/565
Add ObserverMethod#getDeclaringBean method. by @manovotn in https://github.com/jakartaee/cdi/pull/578
Move getInjectableReference method from BeanContainer to BeanManager by @manovotn in https://github.com/jakartaee/cdi/pull/574
Move the session scope to CDI Full by @Ladicek in https://github.com/jakartaee/cdi/pull/577
Add default implementation of OM#getDeclaringBean() by @manovotn in https://github.com/jakartaee/cdi/pull/579
Invalid parameter combinations in @Enhancement and @Registration meth… by @manovotn in https://github.com/jakartaee/cdi/pull/581
Add explicit notes to APIs that are not required to be present in CDI Lite by @Ladicek in https://github.com/jakartaee/cdi/pull/580
Change parameter type of SkipIfPortableExtensionPresent from String to Class by @manovotn in https://github.com/jakartaee/cdi/pull/586
Update package version by @Emily-Jiang in https://github.com/jakartaee/cdi/pull/590
clarify beans.xml handling in CDI Lite by @Ladicek in https://github.com/jakartaee/cdi/pull/591
Move to final versions of dependencies for 4.0.0 final by @starksm64 in https://github.com/jakartaee/cdi/pull/593
Add a copyright header, #597 by @starksm64 in https://github.com/jakartaee/cdi/pull/598
Bump nokogiri from 1.13.1 to 1.13.3 in /docs by @dependabot in https://github.com/jakartaee/cdi/pull/596

New Contributors

@gaol made their first contribution in https://github.com/jakartaee/cdi/pull/458
@benjamin-confino made their first contribution in https://github.com/jakartaee/cdi/pull/462
@Thihup made their first contribution in https://github.com/jakartaee/cdi/pull/463
@Cousjava made their first contribution in https://github.com/jakartaee/cdi/pull/466
@graemerocher made their first contribution in https://github.com/jakartaee/cdi/pull/501

Full Changelog: https://github.com/jakartaee/cdi/compare/3.0.0...4.0.0

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

jakarta.transaction-api required v3


raft: hide Campaign rules on applying all entries

Fix https://github.com/coreos/etcd/issues/6013.
@LK4D4 can you please give this a try?
Previously we have some rules about when there are configuration changes. It is actually a little bit hard to follow for applications. Now we try to handle it internally inside raft.

LGTM

/cc @siddontang Probably you want to port this to rust too.

@xiang90 sure, will try tomorrow.

@LK4D4 Progress?

@xiang90 I updated to your PR commit and it works perfectly.

@LK4D4 OK. Thanks for confirming this for me!

@gyuho Do not back port this. We need to have this tested by functional testing cluster for a while.

Ok won't. Thanks!


How about support AWSCommit

AppCenter currently supports building apps in Git repositories, I would love to have App center accessing my AWS Code Commit repositories.

I can not wait for it! that would be super helpful

As in this issue, reported some time ago, I think that several people will appreciate if AppCenter could work with other repositories like AWS CodeCommit.

When will this feature be available, is it taken into consideration?

Any update from Microsoft team? Are you planning this feature in the product roadmap?


[New game]: Valorous Rabbit Game - 3D

🎮 Game Request
I want to add a new project using HTML, CSS and JavaScript which is a 3D game of a rabbit and a monster.
Point down the features

The monster chases the rabbit and as a user you have to control the rabbit and save yourself from the monster.
The rabbit jumps on click of the mouse and saves from the obstacles.
The game also has sound effects to provide a seamless experience to the user.
Overall 3D experience will be included along with levels.

Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @abhinav-m22 , You can't have another issue before completing the previous one 😀
you already have the following 1 open issues 👀 ! :
#1791

Hey @abhinav-m22 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹


sqlx 0.5.10 install problem

I am attempting to use sqlx with actix, but got stuck immediately at an installation bug related to https://github.com/launchbadge/sqlx/issues/1604
I'm running MacOS Big Sur 11.6.2
$ rustc --version
rustc 1.58.0 (02072b482 2022-01-11)

I initially tried to install with just the 'postgres' feature, based on the instructions in this tutorial and got an error.
$ cargo install sqlx-cli --no-default-features --features postgres
...
error: one of the features ['runtime-actix-native-tls', 'runtime-async-std-native-tls', 'runtime-tokio-native-tls', 'runtime-actix-rustls', 'runtime-async-std-rustls', 'runtime-tokio-rustls'] must be enabled
  --> /Users/edmurphy/.cargo/registry/src/github.com-1ecc6299db9ec823/sqlx-rt-0.5.10/src/lib.rs:9:1
   |
9  | / compile_error!(
10 | |     "one of the features ['runtime-actix-native-tls', 'runtime-async-std-native-tls', \
11 | |      'runtime-tokio-native-tls', 'runtime-actix-rustls', 'runtime-async-std-rustls', \
12 | |      'runtime-tokio-rustls'] must be enabled"
13 | | );
   | |_^

error: could not compile `sqlx-rt` due to previous error
warning: build failed, waiting for other jobs to finish...
error: failed to compile `sqlx-cli v0.5.10`, intermediate artifacts can be found at `/var/folders/hx/2g4wddts0mb9f3tbg471c75m0000gn/T/cargo-installiHvI4w`

So I then retried the install, including an actix runtime, but I still got an error,
$ cargo install sqlx-cli --no-default-features --features runtime-actix-rustls,postgres
    Updating crates.io index
  Installing sqlx-cli v0.5.10
error: failed to compile `sqlx-cli v0.5.10`, intermediate artifacts can be found at `/var/folders/hx/2g4wddts0mb9f3tbg471c75m0000gn/T/cargo-installnOGGPg`

Caused by:
  Package `sqlx-cli v0.5.10` does not have the feature `runtime-actix-rustls`

I then also tried with actix native tls
$ cargo install sqlx-cli --no-default-features --features runtime-actix-native-tls,postgres
    Updating crates.io index
  Installing sqlx-cli v0.5.10
error: failed to compile `sqlx-cli v0.5.10`, intermediate artifacts can be found at `/var/folders/hx/2g4wddts0mb9f3tbg471c75m0000gn/T/cargo-installiPw3bH`

Caused by:
  Package `sqlx-cli v0.5.10` does not have the feature `runtime-actix-native-tls`

The intermediate artifacts are just a .rustc_info.json with the following contents;
{
  "rustc_fingerprint":91532511382400490,
  "outputs":{
    "931469667778813386":{
      "success":true,
      "status":"",
      "code":0,
      "stdout":"___\nlib___.rlib\nlib___.dylib\nlib___.dylib\nlib___.a\nlib___.dylib\n/Users/edmurphy/.rustup/toolchains/stable-x86_64-apple-darwin\ndebug_assertions\nproc_macro\ntarget_arch=\"x86_64\"\ntarget_endian=\"little\"\ntarget_env=\"\"\ntarget_family=\"unix\"\ntarget_feature=\"fxsr\"\ntarget_feature=\"sse\"\ntarget_feature=\"sse2\"\ntarget_feature=\"sse3\"\ntarget_feature=\"ssse3\"\ntarget_os=\"macos\"\ntarget_pointer_width=\"64\"\ntarget_vendor=\"apple\"\nunix\n",
      "stderr":""
    },
    "2797684049618456168":{
      "success":true,
      "status":"",
      "code":0,
      "stdout":"___\nlib___.rlib\nlib___.dylib\nlib___.dylib\nlib___.a\nlib___.dylib\n",
      "stderr":""
    },
    "17598535894874457435":{
      "success":true,
      "status":"",
      "code":0,
      "stdout":"rustc 1.58.0 (02072b482 2022-01-11)\nbinary: rustc\ncommit-hash: 02072b482a8b5357f7fb5e5637444ae30e423c40\ncommit-date: 2022-01-11\nhost: x86_64-apple-darwin\nrelease: 1.58.0\nLLVM version: 13.0.0\n",
      "stderr":""
    }
  },
  "successes":{

  }
}

I'm not sure how to proceed.

See the new install instructions here: https://github.com/launchbadge/sqlx/tree/master/sqlx-cli#with-rust-toolchain
The ones shown on crates.io are out of date.


SQL template: create VIEW in PostgreSQL database for iRedMail

Here's SQL template used to create VIEW in PostgreSQL for iRedMail, tested with Roundcubemail-1.1.0 with PostgreSQL-8.4.20 on CentOS 6 (iRedMail-0.9.0).
-- RHEL/CentOS 6.
-- CREATE LANGUAGE plpgsql;
-- \i /usr/share/pgsql/contrib/dblink.sql;

-- RHEL/CentOS 7
-- CREATE EXTENSION dblink;

CREATE VIEW global_addressbook AS
    SELECT * FROM dblink('host=<IP_ADDRESS> port=5432 user=xxx password=xxxx dbname=xxx', 'SELECT extract(epoch FROM created), name, username, domain FROM mailbox WHERE active=1')
    AS global_addressbook ("ID" BIGINT, name VARCHAR(255), email VARCHAR(255), domain VARCHAR(255));

ALTER TABLE global_addressbook OWNER TO roundcube;

Notes:

if you're running RHEL/CentOS 6 or 7, don't forget to uncomment the first lines to create dblink function.
of course you should replace xxx in above sample SQL command by the real SQL username/password/database name.
on iRedMail server, it's better to use SQL user vmail which has read-only permission to vmail database. Don't use vmailadmin or root user.

Mind creating a fork and pull request for this, also any chance of you creating an Alias Compatible one? On the MySQL Side it uses a subquery on the e-mail address.


Having trouble with complex use case

I've been working on a reporting system web app to replace an obsolete system on our intranet. My first version had a custom file upload directive but has some limitations that aren't worth troubleshooting so I decided to use ng-file-upload instead.
Along with files I have to collect a lot of information to store in the database for the report. The problem I'm running into is that I can't seem to figure out how to:
A.) get the file queue to send along with my other data to the mediator that's doing the storing of files and db data.
OR
B.) send the rest of the form data along with the file uploads.
Part of the file upload process is to create a folder using the auditor's user id and then place the files in a folder with the name of the timestamp for the form submission.
I'm assuming I should be able to do this with this module but I can't figure out how. I'm not seeing anything in the documentation about getting file data to send with another method or sending other form data along with the file uploads.

Post it on SO since it is a question. The example with form sends data along with file


docs: add iQIYI to ADOPTERS.md

Description
add iQIYI to ADOPTERS.md

The lint is failed, can you fix it?
ADOPTERS.md:97:71 MD047/single-trailing-newline Files should end with a single newline character

The lint is failed, can you fix it?
ADOPTERS.md:97:71 MD047/single-trailing-newline Files should end with a single newline character

fixed


Scons w/ Python3 fails in osx's detect.py

Operating system or device, Godot version, GPU Model and driver (if graphics related):
OSX, Godot version master (195b122)
Issue description:
Running the compile for osx runs into an error due to legacy usage of has_key which no longer exists in python3.
Steps to reproduce:
Using python 3.X (I used Python 3.6.0 :: Anaconda 4.3.1 (x86_64))
scons platform=osx
Link to minimal example project:
N/A

Fixed by #11904.


data-repeater-create not working

I wanted to take advantage of repeaterVal() so I dropped in the latest version from this repo. Prior to that I had the plugin working fine using the older version on the jQuery website.
Everything works fine with the new version except the data-repeater-create button no longer creates any repeating items. Everything else looks to be working: it's renaming the name attributes fine and I can delete the first row using data-repeater-delete. And it's throwing no console errors.
Have you come across this issue before?

I have recreated the issue here: http://jsbin.com/fuvuhutahe/edit?html,js,output
Please click 'Run with JS' before attempting. Deleting the item works but I cannot create a new one.

Hey thanks for the jsbin, this makes things easier.
looks like the problem is that the repeater method needs to be called on the immediate parent of the data-repeater-list
I changed the code to target the class .jumbotron instead of the class .repeater
JSBin Here
$(document).ready(function () {
	$('.jumbotron').repeater();
});

Hello, I'm having issues and I don't know how to go about it. I'm using angular data-ng-options to populate my select(dropdown) from the server and for everytime I try to Add(Repeat the Form), It does not populate the Items in the dropdown. Please how can I go about this. Thanks in Advance


Clarify files to edit & not edit to ease upgrade

Type of question
Are you asking about community best practices, how to implement a specific feature, or about general context and help around the operator-sdk?
Best practices
Question
In reading the docs, it's clear that the operator developer should modify the *_types.go and *_controller.go files for their CRDs. What isn't as clear is what other files should or should not be modified.
Presumably as the SDK evolves, the template code that is created by operator-sdk new will change. What are good recommendations for operator developers to keep in mind so that it remains easy to upgrade the SDK? For example:

Should we consider all *.go files to be owned by the SDK and avoid modifying them (with the exception of the two mentioned above)?
What about the Dockerfile and the various yamls?

For reference here's what a simple go operator project looks like with a single added api and controller.
$ tree ./ -I vendor
./
├── build
│   └── Dockerfile
├── cmd
│   └── manager
│       └── main.go
├── deploy
│   ├── crds
│   │   ├── example_v1alpha1_app_crd.yaml
│   │   └── example_v1alpha1_app_cr.yaml
│   ├── operator.yaml
│   ├── role_binding.yaml
│   ├── role.yaml
│   └── service_account.yaml
├── Gopkg.lock
├── Gopkg.toml
├── pkg
│   ├── apis
│   │   ├── addtoscheme_example_v1alpha1.go
│   │   ├── apis.go
│   │   └── example
│   │       └── v1alpha1
│   │           ├── app_types.go
│   │           ├── doc.go
│   │           ├── register.go
│   │           └── zz_generated.deepcopy.go
│   └── controller
│       ├── add_app.go
│       ├── app
│       │   └── app_controller.go
│       └── controller.go
└── version
    └── version.go

Since the SDK is still alpha, it's hard to answer this question with a strong guarantee.
To answer your specific questions:

Should we consider all *.go files to be owned by the SDK and avoid modifying them (with the exception of the two mentioned above)?

Using the example about, I think the following are expected to be changed by an operator developer:

cmd/manager/main.go
pkg/apis/example/v1alpha1/app_types.go
pkg/apis/example/v1alpha1/doc.go
pkg/apis/example/v1alpha1/zz_generated.deepcopy.go
pkg/controller/app/app_controller.go
version/version.go

Outside of those, do you have a use case for changing the other *.go files?

What about the Dockerfile and the various yamls?

The SDK is primarily concerned that these files exist in their scaffolded location and that they are valid syntactically.
For deploy/role.yaml, the SDK will automatically add new rules as new APIs and CRDs are added. But if your operator needs different permissions than what are in the default role.yaml, it should be okay to update it to add or remove them.
For the Dockerfile, operator-sdk build builds your operator image using ./build/Dockerfile. So it needs to be there. However, operator developers can modify it to install dependencies, run setup commands, etc. There are some changes in the works to be aware of though (#782 and #431)

Thanks for the reply. I don't currently have a good reason to change the other files.
My big concern is getting a feel for what it will mean to "upgrade" the sdk version and trying to make sure merging changes into the operator is as simple as possible.
I think this is sufficient for my purposes.

@JohnStrunk once we reach non-alpha status, only major version changes, ex. v1.x.x -> v2.x.x, will break compatibility with old operator projects. Because we're in alpha, changes to operator project file structure can still occur with minor version changes, ex. v0.1.x -> v0.2.x. We will be sure to make documentation available for migration when we make breaking changes, like we did for v0.0.x -> v0.1.0.

That works for me. My takeaway is...
Non-breaking upgrades amount to:

using the latest sdk release
running print-deps to update Gopkg

Breaking upgrades will have specific documentation, but in general, I can expect to re-run operator-sdk new and merge in my current operator code.
Assuming this is approximately correct, I'm good w/ closing this.


feat: Automatically opt into sharing collected artists with galleries

This PR resolves ONYX-400
Description
Automatically opt into sharing collected artists with galleries.
PR Checklist

[ ] I have tested my changes on iOS and Android.
[ ] I hid my changes behind a feature flag, or they don't need one.
[ ] I have included screenshots or videos, or I have not changed the UI.
[ ] I have added tests, or my changes don't require any.
[ ] I added an app state migration, or my changes do not require one.
[ ] I have documented any follow-up work that this PR will require, or it does not require any.
[ ] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

Warnings

:warning:

❌ An error occurred while validating your changelog, please make sure you provided a valid changelog.

  Generated by :no_entry_sign: dangerJS against 80cbad0e06721ab9392114d5b95f866f3d6893ca


DID Net source code

@xiaojie1017 thanks for open-sourcing  the dataset i have few queries
1.can yo please share the dataset on google drive ?
2. can you let us knw link of DID net source code
THanks in adavance

@xiaojie1017 would be great to have this dataset on google drive or another source because I'm having trouble downloading from the current source.


Compiler Warning (level 4) C4706 and "<="

For a newbie, if you forget the "<", you will get Compiler Warning (level 4) C4706
for (i = 2; i = n / 2; ++i)
for (i = 2; i <= n / 2; ++i)
It's not immediately noticeable as the compiler can still run the project.
If this a good example, could you kindly add it as an example?

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

ID: 3bf067a7-3f30-3d37-dbee-856d00a42f82
Version Independent ID: 0d46c95c-a0d1-fcc3-d6f6-5484d0142721
Content: Compiler Warning (level 4) C4706
Content Source: docs/error-messages/compiler-warnings/compiler-warning-level-4-c4706.md
Product: visual-cpp
Technology: cpp-diagnostics
GitHub Login: @corob-msft
Microsoft Alias: corob

Thank you for your patience as we work through our backlog. We have received more issues than we can manage at this time. We are closing issues based on their severity, how broadly applicable they are, and whether there is enough information provided to act on the issue. If you believe that this issue should not have been closed, please add a comment explaining why by 3/8/2024. We appreciate your contribution and encourage you to propose changes using public PRs, or submit feedback through our updated control at the top of the page, as we phase out Git Issues for this repo. For more information on our feedback systems, see https://aka.ms/ContentUserFeedback.


Install App from Store

How would one install an App from the Microsoft store? (A non-business app)
The below sample code always returns 500. Why is the skuID required if we're only trying to install store apps?
<Exec>    <CmdID>1</CmdID>           <Item>             <Target>               <LocURI>./User/Vendor/MSFT/EnterpriseModernAppManagement/AppInstallation/{PackageFamilyName}/StoreInstall</LocURI>             </Target>             <Meta>                 <Format xmlns="syncml:metinf">xml</Format>             </Meta>             <Data><Application id="{ProductID}" flags="0" skuid=" "/></Data>           </Item> </Exec>
For example, just trying to install the AnyConnect VPN agent.
<Add> 			<CmdID>|SamplePathCreateApp</CmdID> 			<Item> 				<Target>					<LocURI>./User/Vendor/MSFT/EnterpriseModernAppManagement/AppInstallation/CiscoSystems.AnyConnect_edjcgkw48dhxt</LocURI> 				</Target> 			</Item> 		</Add> 		<Exec> 			<CmdID>|XMLInstallApp</CmdID> 			<Item> 				<Target> 					<LocURI>./User/Vendor/MSFT/EnterpriseModernAppManagement/AppInstallation/CiscoSystems.AnyConnect_edjcgkw48dhxt/StoreInstall</LocURI> 				</Target> 				<Meta> 					<Format xmlns="syncml:metinf">xml</Format> 				</Meta> 				<Data><Application id="9wzdncrdj8lh" flags="1" skuid="CiscoSystems.AnyConnect_edjcgkw48dhxt"/></Data> 			</Item> 		</Exec>
Would anyone be able to help out with a new sample of installing regular store apps that doesn't required AD?

Resolved by using skuID of "0010"


fix(index): add ouputPath only when publicPath is not set

Issues

Closes #249

Notable Changes

publicPath not set => __webpack_public_path__ + "output_path/file.ext"
publicPath set => __webpack_public_path__ + "public_path/file.ext"
fix broken useRelativePath and tests

What about the issue where the result of {Function}  gets appended to the path instead of replacing it ?  Assuming this is fixed by https://github.com/webpack-contrib/file-loader/pull/250#discussion-diff-169345588R49 but better double check :)

@michael-ciniawsky can you give example config?

I try to provide an example, just one sec I got distracted

file-loader >= v1.1.7
{
  loader: 'file-loader',
  options: {
    name: '[name].[ext]',
    outputPath (url) {
      return url
    }
  }
}

file.svgfile.svg

@michael-ciniawsky let's fix this

@michael-ciniawsky just add tests, all works as expected here :+1:

@michael-ciniawsky all done :+1:

The commit message isn't quite correct anymore, any suggestions for a better one ? :)

@michael-ciniawsky no idea, big bug fix? :smile: Feel free to change commit message

publicPath set => webpack_public_path + "public_path/file.ext"
publicPath not set => webpack_public_path + "output_path/file.ext"
What happens if both publicPath && outputPath options are set ?

@michael-ciniawsky for output we use outputPath + url, for public we use publicPath + url (without concat output path)

Could you split them please so I can rebase merge instead ?
fix(index): normalize and concat paths via `path.join()`
fix(index): don't append `outputPath` to the original `url` (`options.outputPath` `{Function}`)
fix(index): `context` takes precedence over `issuer.context` (`options.useRelativePath`)
```

@michael-ciniawsky done


You have to change the status to "Informationsupdate" to be able to update the incident

If you don't change the status to "Informationsupdate" you get an second "Eröfnungsmeldung" instead of an "Updatemeldung". For every change in the incident, you have to change the status otherwise you should get an error message.

Fixed the whole template selection etc. So this one should also be fixed...


Give user feedback that repo is deleted

With response to issue #518 , when repo got deleted the second time,
[root@chai /]# pachctl list-repo
NAME                CREATED             SIZE
filter102           About an hour ago   0 B
test009             18 hours ago        0 B
test008             18 hours ago        0 B
[root@chai /]# pachctl delete-repo test 009
[root@chai /]# pachctl list-repo
NAME                CREATED             SIZE
filter102           About an hour ago   0 B
test008             18 hours ago        0 B
Suggestion - Feedback can be given regarding deletion of the repo

For now we're relying on exit codes to denote success or failure.
If you do:
pachctl delete-repo something
echo $?

And the result is 0, that means it succeeded. If its non-zero that means it erred.


Can $SYS message result Contains the topic name?

such as
$SYS/brokers/${node}/clients/count  : the result should be : clients/count:100.
this is useful , so I  not need subscribe a lot of $SYS topics,to get the specified result

This feature is invalid. Messages published to client contain topic name.

ok,,I forgot it,hehe.


Deep vs Shallow Copy

This is my trial submission. I would have done it differently, i.e., had a single commit instead of 3 because of downstream pulls, but this PR won't be merged anyway. Thanks!

Closed it as it is just a tutorial submission.


Can't slide when clicking dots

I can't slide the slider when clicking a Dot. The Dot shos when it's active - but the onClick handler doesn't work.
Any Idea?
File looks like this:
https://jsfiddle.net/20bumb4g/4815/

This could be an issue with older versions. Newer versions of react-slick don't have any related probelms.

Using the latest version available now, this problem persists. But when I use custom dot class other than 'slick-dots', it wroks

there is pseudo element (:before and :after) on dot element (li), remove that by css, and will work fine:
.slick-dots li:before,.slick-dots li:after{display:none}


authid value returns "anonymous" no matter.

No matter how I defined it in the javascript (autobahn-js) client in browser, authid always returns "anonymous". Any ideas?
I register the topic like this:
  $session->register('com.myapp.hello', [$this, "fetchUser"], ['disclose_caller' => true]);
and I get it in function:
   function fetchUser($args, $kwArgs, $details){             echo $details->authid;      }
my javascript (browser) spits the authid  like this:
...
 var connection = new autobahn.Connection({
   url: 'ws://xxx.xxx.xx.x:8080/',
   realm: 'realm1',
   authmethods: ["wampcra"],
   authid: "Mickey",
   onchallenge: onchallenge

});
...

my router is defined like this (whole code)
<?php

require 'bootstrap.php';
require 'InternalClient.php';

use Thruway\Peer\Router;
use Thruway\Transport\RatchetTransportProvider;

$realm = "realm1";
$router = new Router();
$InternalClient = new InternalClient($realm, $router->getLoop());

$transportProvider = new RatchetTransportProvider("<IP_ADDRESS>", 8080);

$router->registerModule($transportProvider);
$router->addInternalClient($InternalClient);

$router->start();

?>

Thank you in advance !

You're trying to use WAMPCRA authentication on the client but you don't have any authentication configured in the router.


Merge most recent version of STLink into the fork.

Commits are included in PR #822 & #825 instead.


Week2 Group1

Submissions for Week2 VQE
Group 1
Members (Alphabetical Order)

Eduard Smetanin
Ho Nam Nguyen
Oscar Javier Hernandez
Quang Nguyen
Shumpei Kobayashi

Abstract

BusinessApplication.pdf is attached
README.md has been modified
S*_solution.ipynb has been created for each step
exited_state.ipynb has been created for further challenge

Thanks for the nicely organized results.  Very interesting work on the SSVQE


Fix using PQs with subscriptions

See #6276

Make it possible to use PQs with subscriptions.
Make release-3.x compile now that jcenter is dead.
Fix https://github.com/apollographql/apollo-kotlin/pull/5894#pullrequestreview-2117767392 (subscriptions may do a partial read)

See test here

Sadly the release-3.x CI has flakes. The integration tests "run on my machine" though so I'm tempted to merge anyways.


Updated SP of iSCSI servers from 15 SP3 to 15 SP5

Stopped being lazy and tested it. Worked great, thanks.


Deletion of Account error message is not clear

Environment info

NooBaa Version: 5.15
Platform: Standalone

Actual behavior

node /usr/local/noobaa-core/src/cmd/manage_nsfs account delete --name accout1 --uid 0 --gid 0 --accessKey
ERRO[2023-11-27T07:03:44+01:00] Execute command failed
info:
Error accrued while getting the data from /etc/noobaa-server/jwt: Error: ENOENT: no such file or directory, open '/etc/noobaa-server/jwt'
Error accrued while getting the data from /etc/noobaa-server/server_secret: Error: ENOENT: no such file or directory, open '/etc/noobaa-server/server_secret'
Error accrued while getting the data from /etc/noobaa-auth-token/auth_token: Error: ENOENT: no such file or directory, open '/etc/noobaa-auth-token/auth_token'
2023-11-27 07:03:44.619025 [PID-664252/TID-664252] FS::GPFS GPFS_DL_PATH=NULL, fs_napi will call default posix system calls
init_rand_seed: starting ...
read_rand_seed: opening /dev/random ...
Nov-27 7:03:44.762 [/664252]   [LOG] CONSOLE:: read_rand_seed: reading 32 bytes from /dev/random ...
Nov-27 7:03:44.763 [/664252]   [LOG] CONSOLE:: NSFS config root dir exists: /etc/noobaa.conf.d
Nov-27 7:03:44.766 [/664252]   [LOG] CONSOLE:: read_rand_seed: got 32 bytes from /dev/random, total 32 ...
Nov-27 7:03:44.766 [/664252]   [LOG] CONSOLE:: read_rand_seed: closing fd ...
Nov-27 7:03:44.767 [/664252]   [LOG] CONSOLE:: NSFS config root dir exists: /etc/noobaa.conf.d/buckets
Nov-27 7:03:44.776 [/664252]   [LOG] CONSOLE:: init_rand_seed: seeding with 32 bytes
rand_seed: OpenSSL 3.0.10+quic 1 Aug 2023 seeding randomness
Nov-27 7:03:44.776 [/664252]   [LOG] CONSOLE:: NSFS config root dir exists: /etc/noobaa.conf.d/accounts
Nov-27 7:03:44.777 [/664252]   [LOG] CONSOLE:: NSFS config root dir exists: /etc/noobaa.conf.d/access_keys
Nov-27 7:03:44.781 [/664252] [ERROR] CONSOLE:: NSFS Manage command: Could not find account to update { name: 'accout1', creation_date: '2023-11-27T06:03:44.777Z', access_keys: [ { access_key: undefined, secret_key: undefined } ], nsfs_account_config: { distinguished_name: undefined, uid: 0, gid: 0, new_buckets_path: undefined } } [Error: ENOENT: no such file or directory, open '/etc/noobaa.conf.d/accounts/accout1.json'] { errno: -2, code: 'ENOENT', syscall: 'open', path: '/etc/noobaa.conf.d/accounts/accout1.json' }
Nov-27 7:03:44.781 [/664252]  [WARN] CONSOLE::
Help:
"nsfs" is a noobaa-core command runs a local S3 endpoint on top of a filesystem.
Each sub directory of the root filesystem represents an S3 bucket.
manage nsfs will provide a command line interface to create new accounts and map existing directories
to Noobaa as buckets. For more information refer to the noobaa docs.

Nov-27 7:03:44.781 [/664252]  [WARN] CONSOLE:: Usage:
node src/cmd/manage_nsfs <type> <action> [options...]

Nov-27 7:03:44.781 [/664252]  [WARN] CONSOLE:: Arguments:
<type>    Set the resource type such as accounts and buckets
<action>  Action could be add, update, list, status and delete for accounts/buckets.

Nov-27 7:03:44.782 [/664252]  [WARN] CONSOLE:: Account Options:
# Read account details from the JSON file, there is no need to mention all the properties one by one in the CLI
--from_file <dir>                       (default none)                  Set account schema full path.
                                                                        Get account details from JSON file
--config_root_backend <none | GPFS >    (default none)                  Set the config_root FS type to be GPFS

# required for add, update
--name <name>               (default none)                              Set the name for the account.
--email <email>             (default none)                              Set the email for the account.
--new_name <name>           (default none)                              Set a new name for the account (update).
--uid <uid>                 (default as process)                        Send requests to the Filesystem with uid.
--gid <gid>                 (default as process)                        Send requests to the Filesystem with gid.
--secret_key <key>          (default none)                              The secret key pair for the access key.
--new_buckets_path <dir>    (default none)                              Set the filesystem's root where each subdir is a bucket.

# required for add, update, and delete
--access_key <key>          (default none)                              Authenticate incoming requests for this access key only (default is no auth).
--new_access_key <key>      (default none)                              Set a new access key for the account.
--config_root <dir>         (default config.NSFS_NC_DEFAULT_CONF_DIR)   Configuration files path for Noobaa standalon NSFS.

# Used for list
--wide                      (default none)                              Will print the list with details (same as status but for all accounts)

error: exit status 1
ERRO[2023-11-27T07:03:44+01:00] failed to execute command. stderr:exit status 1
ERRO[2023-11-27T07:03:44+01:00] Failed to delete account!!
Expected behavior

If account doesnot exist it should throw account does not error
If access key is invalid then the respective key error should be thrown

Steps to reproduce

More information - Screenshots / Logs / Other output

@ramya-c3 Please provide the exact version and revision that it was tested on (5.15-)

@ramya-c3 Adding request validation, should be clearer after the errors/responses refactoring https://github.com/noobaa/noobaa-core/pull/7655


Show more context?

I'd like to see the entire string sent (using past vs. current).
Is there any way to ensure the entire file is shown?

@switz You can setting outputFormat type by configuration.
The format of the output data: line-by-line or side-by-side.

@switz Did you mean entire file content? If true, diff2html doesn't support.

If have any question, feel free reopen this issue.

The author seems to think it relies on upstream modules https://github.com/rtfpessoa/diff2html/issues/139
Sent from my phone

On Sep 19, 2018, at 10:36 PM, Peng Jie<EMAIL_ADDRESS>wrote:
Closed #81.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@switz react-gh-like-diff depend on unifiedDiff by difflib, seems need adjust n parameter to control context line, check out here.

Can you expose difflib options? If you don't have time, I can send you a PR.

I will work for this but feel free send your PR.


The 'unit' keyword is not highlighted

In the following (pointless) code:
unit sub MAIN;

The unit keyword is not highlighted:

Currently, I've taken the syntax highlighting definition from https://github.com/Raku/atom-language-perl6 mostly unchanged. That repo powers the Atom extension and is used for Github highlighting so is fairly important. Unfortunately, it has not been updated in a couple years and the prior maintainer was seeking a new one. If we begin to find many syntax issues that entirely break highlighting, I would consider starting a fork of that repo, but ideally all changes should be centralized somewhere. For now, I'll close this as "won't fix", but I appreciate the reports and encourage you to submit more or comment syntax issues here or back at the atom-language-perl6 repo to keep track of them.


Added cache-control: private headers for all link redirects

ref https://linear.app/tryghost/issue/ENG-883/add-cache-control-private-headers-to-the-link-redirects

Link redirects shouldn't be cached because we record which member clicked the link on the redirect
This PR adds cache-control: private headers to all link redirects to prevent them from being cached

PR ready to go, just waiting to merge because I have a larger change in the same area going in soon and I don't want to skew my validation results by making two changes at the same time.

Closing for now as this would just add fuel to our redirect problem at the moment.


Race condition in router

Currently we have multiple routes which require fully registered users. Since we have to fetch the profile of users to check if they fully registered there's always a delay between when the route-guard is activated and when we actually know whether the user is fully registered or not.
This is easily seen when navigating to a page that requires a fully completed profile and then refreshing the page. This will redirect the user to the profile edit page whether they have completed their profile or not.
There's two ways to prevent this:

Wait for profile to be loaded before proceeding with routing.
Removing the "fully registered"-guards and instead have validation when an action happens that requires the profile.

I personally prefer option 2, because there's really no need to not let users without a fully completed profile go to certain routes. We can still check if they're fully registered if they, for example, try to create an event and if they're not, we could have a popup where they insert their name. There's also the fact that the route-guards don't prevent anyone from accessing the routes and there's nothing stopping them from actually creating events when they are not fully registered.

As per @stefnotch 's suggestion we should save the profile in localstorage. That way we do not have to fetch it from the database and would eliminate the race condition.
We should figure out when it is necessary to refetch the profile or if we should refetch the profile occasionally, since users might change their profile info on another device which would make the localstorage stale.
We should also consider the possibility that users may delete localstorage which would reintroduce the race condition for them.

As a test I implemented this using localstorage and it works, but it still doesn't feel good. The biggest problem is that we can't trust the data in localstorage to be up to date, so there needs to be some kind of expiration date after which the profile has to be refetched and when that happens this solution does not work.
I think the best way to handle this and keep our current login/sigin flow is to remove the "registered" routeguards and only prompt the user to set their full name once they want to take an action that actually requires the registered status.

Hehe: but we can easily set stuff to expire
https://www.sohamkamani.com/javascript/localstorage-with-ttl-expiry/

The problem isn't making it expire, it's that if it expires, localstorage doesn't help because we have to refetch anyways, which reintroduces the race condition.

Maybe we should just not care about the full name?
We could have a reminder somewhere that informs the user that they haven't set their name yet and have them decide whether they're going to set it or not.
Ultimately it's not like it breaks the functionality of the site. The only time we ever show the name is in the matches and there's still nothing stopping anyone from just putting a random name if they want to. If someone hasn't set a name we could just display them as "Anonymous" or something.
Constantly redirecting users and being vulnerable to race conditions is way worse than someone being displayed as Anonymous because they couldn't be bothered to change their profile when prompted.

Yeah you're right - this seems like a REALLY great solution.
We want to create value for the user and not force some super useless features into the app that make it janky asf

Time to yeet out the entire "registered" part of the routing if it messes up the applications state management.
I'm in favor of having as little states as possible, even if it comes at the cost of sending slightly more requests to the server because the reliability of the app should come first if the performance gains with these tricks are so minimal.

Is this completed?

Is this completed?

Since we "yeeted" the registered part, there isn't really any possibility for a race condition anymore

I'll probably make a new issue for caching the profile, so we don't have to refetch every 5 seconds though


⚠ Samsung has degraded performance

In bddae9c, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2466 ms

Resolved: Samsung performance has improved in 233c11a.


JS / TS Client library

Is your feature request related to a problem? Please describe.
We want to generate as much of the code as possible from the OpenAPI. This will help us to stay up to date with the protocol and in the same time it improves development speed and limits possible bugs in implementation.
Describe the solution you'd like

It should be in TypeScript
Add makefile with generate command generate, which will regenerate the code

Additional context
I would recommend using of the OpenAPI codegens.
Feel free to come with something else

Hey @jakubno,
I've been playing with making calls to agent-protocol in TypeScript and hacked together a simple client for it. It is pretty basic and it has no error handling, but I can work on improving it if that's something you'd be interested in adding to the repo. Let me know, I'd like to contribute! Cheers!

Wow @alchaplinsky that looks awesome! I'd love to make a new repo for it and transition it over, although I do have some concerns. Mainly in that it doesn't look like it uses the Open API generator for the spec (which means you wrote it all manually right?)
I did the same thing with the TS SDK early on :laughing:
If you want to keep improving it and base it on the openapi.yml spec, I'd be happy to bring it into the fold :+1:

@jzanecook Yeah, it's not generated, it's something that I put together while playing with SDK. I'll look closer into openapi.yml spec, definitely better to have based on certain standards. I'd love to keep improving and evolving it and hopefully contribute to other repos as well!

@alchaplinsky That sounds great! Are you also on our Discord by any chance? Feel free to ask questions in there as well.
Honestly, if you can get it to generate based on the spec and it's working then I'd love to get it into its own repository and we can improve it from there.

@jzanecook Yes, I am on AIEF Discord. Sounds good, I'll work on it and will let you know when it's ready!

It looks like the python client was generated using @openapitools/openapi-generator-cli

The OpenAPI Generator is a Java project. openapi-generator-cli will download the appropriate JAR file and invoke the java executable to run the OpenAPI Generator. You must have the java binary executable available on your PATH for this to work.

I'm not crazy about needing Java. Would it be ok to instead require devs to have docker (just for client generation)?
https://www.npmjs.com/package/@openapitools/openapi-generator-cli#use-docker-instead-of-running-java-locally
There's also openapi-type-codegen ("we do not want to use JAVA codegen in our builds"😅), but then we're using different tooling for the python and js clients...

I'm also wondering if there should be single script (in the root package.json?) to regenerate all clients and sdks based on the current OpenAPI specs.
You could then have husky and/or a GitHub Actions workflow validate that everything's up to date.

~OpenAI~ Microsoft is also here to help
https://github.com/microsoft/kiota


Strange behavior after upgrading to cirq 0.1.0

After upgrading to cirq v0.1.0 the following code doesn't work (runs forever):
circuit = cirq.Circuit(cirq.H.on(cirq.LineQubit(0)))
circuit.append(circuit)

It used to work with cirq v0.15.0  .
Not sure if this is an actual bug since appending a mutable object to itself ( `circuit.append(circuit) ) it's probably a bad idea and one should probably avoid it in the first place.
Still, I am reporting this fact here since that code used to work before upgrading.
FYI: the following code works as expected:
circuit = cirq.Circuit(cirq.H.on(cirq.LineQubit(0)))
circuit.append(circuit.copy())

This is the PR  that causes it: https://github.com/quantumlib/Cirq/pull/5332. Specifically this change: https://github.com/quantumlib/Cirq/pull/5332/files#r940546694. Pinging @daxfohl.

I see, looks like passing the circuit into itself would cause the iterator to infinite loop there. Wrapping in a list should fix it: for moment_or_op in list(ops.flatten_to_ops_or_moments(moment_or_operation_tree)):. Feel free to make the change; my time for cirq is limited these days.

Thanks for the quick reply and fix!


Open troubleshoot dialog with core-signal.

Inside instance.ts, opening the troubleshoot dialog should require calling:
this.fire('core-signal', {name: 'open-troubleshoot'});

But for some reason, if this line is inside the then() or catch() block of a promise, the dialog doesn't open. I've tried moving the line into an external function, confirmed the function was being called, but the dialog still wouldn't open. If I put the same line outside the then() or catch() blocks of instance.ts, the dialog does open.
Right now in it's place, the dialog is opened with a querySelector, which isn't the cleanest.

This looks like it is happening because the uproxy-instance node is getting removed from the DOM shortly after calling core.start, I'm going to try to look into this a bit more and see if there is a way we can avoid doing that.


Clangd 12 doesn't seem to see headers in /usr/include

Dev host was just upgraded to Redhat 8 from Redhat 7. Clangd 12 now doesn't seem to find anything in /usr/include anymore. For instance, get an error "sys/types.h file not found", which is located in /usr/include. This was working fine before on Redhat 7.
I added the query-driver directive, and I can see that some built-in paths are discovered, but /usr/include is not among them:
I[19:46:22.045] System includes extractor: successfully executed /opt/rh/gcc-toolset-10/root/usr/bin/gcc
	got includes: "/opt/rh/gcc-toolset-10/root/usr/lib/gcc/x86_64-redhat-linux/10/../../../../include/c++/10, /opt/rh/gcc-toolset-10/root/usr/lib/gcc/x86_64-redhat-linux/10/../../../../include/c++/10/x86_64-redhat-linux, /opt/rh/gcc-toolset-10/root/usr/lib/gcc/x86_64-redhat-linux/10/../../../../include/c++/10/backward, /opt/rh/gcc-toolset-10/root/usr/lib/gcc/x86_64-redhat-linux/10/include, /opt/rh/gcc-toolset-10/root/usr/include"

I tried to add "-isystem /usr/include" manually to all commands in the compile_commands.json, and then it seems to find the /usr/include headers, but then I run into this problem here: https://llvm.discourse.group/t/in-included-file-stdlib-h-file-not-found/1694/6. So that is not a solution either.

Can you provide verbose logs for an example failure, with & without the query-driver option?
Is this a release from this github repo, from llvm.org, or somewhere else?
It looks like your GCC is using a nonstandard sysroot and that's why query-driver didn't work. Can gcc find these headers?
Possible workaround might be -isysroot/ if clangd has been compiled with weird options or env variables are set...

I think I got the problem, your sysroot suggestion got me on the right path.
We are using bazel as our build system, it creates a symlink to the actual sysroot and passes it to gcc as as a --sysroot compile flag.
However, for some reason it doesn't pass the first directory in the path. So let's say our relative location of the sysroot from the build directory is x/y/z, bazel only passes --sysroot=y/z to gcc, and for some reason gcc seems to be okay with that. But that causes clangd not being able to find the sysroot.
After creating a .clangd config file in the build directory that does the following:
CompileFlags:   Remove: [--sysroot=y/z]   Add: [--sysroot=x/y/z]
clangd works now as expected.


Roll engine 3496156bd9bf..e88573aef75d (3 commits)

https://github.com/flutter/engine/compare/3496156bd9bf...e88573aef75d
git log 3496156bd9bfe61788bf64ce3ca3cf1bc2663f95..e88573aef75d3bb906512ad35ce7ab547cb4d9a2 --no-merges --oneline
e88573aef Roll src/third_party/skia d7d93001ead2..4273a150f84d (1 commits) (flutter/engine#8224)
be9067cc7 Roll src/third_party/skia 37a9294d2eb9..d7d93001ead2 (2 commits) (flutter/engine#8223)
ee4abba58 Roll src/third_party/skia 2894d13a0d9b..37a9294d2eb9 (1 commits) (flutter/engine#8222)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (liyuqian@google.com), and stop
the roller if necessary.

Trybots failed. These were the failed builds: https://cirrus-ci.com/task/6592444610117632

AutoRoller is stopped; closing the active roll.


Incorporate Mapbox Search API into backend search results

As in Atlas v1, Atlas v2's map searches should incorporate results from the Mapbox Search API's map.places endpoint. Results should always be of the feature type currently being displayed, e.g. SA2s for the South Australia dataset.
For example, the results for "point pass" should include the SA2 "Goyder", as Point Pass is a town in that SA2.

Resolved by #239


[Feature request] Add environment variables for Anisotropic Filtering / various anti aliasing / Pre-rendered frames control

I'm sorry for creating an issue for a feature request, I wanted to do it on Valve Proton's github but since this is Vulkan specific I'd rather do it here.
As probably many knows, one of the biggest drawbacks of Vulkan (even in modern native implementations) is that the GPU driver has no control whatsoever on some aspects of the rendering, meaning if the developer didn't implement ingame options for altering texture filtering quality, antialiasing, or the render queue latency, there is no way the user can improve this, as opposed to OpenGL and all DirectX versions except 12, which will support GPU driver level overrides for AF, various forms of antialiasing, or pre-rendered frames / ultra low latency for example.
This is a huge problem that affects all Vulkan games even on Windows!
For example in games like STALKER Shadow of Chernobyl, the engine has a problem that creates massive stutters around campfires and dense vegetation, that can be easily avoided in DX9 by enabling low latency / render queue reductions in both AMD and Nvidia control panels, same goes for anti aliasing, which does not work in DX9 from the game's options but does work extremely well from the GPU drivers.
This was just one game but the problem can be observed for an insane number of games, especially for texture filtering!
I know this is asking a lot... but if it would be possible to have entry points in Vulkan's DXVK implementation, with environment variables to control and force some aspects like texture filtering or render queue latency (MSAA/SSAA options might be too hard/specific, though I'd love it too), it would be a huge improvement and make the linux experience on par or event better than what windows is offering.
Thank you for reading this.

Some of the things you're requesting are already possible using the DXVK config file. https://github.com/doitsujin/dxvk/blob/master/dxvk.conf

driver level overrides for AF

# d3d11.samplerAnisotropy = -1
# d3d9.samplerAnisotropy = -1

Keep in mind that this can cause issues.

pre-rendered frames / ultra low latency for example.

# dxgi.maxFrameRate = 0
# d3d9.maxFrameRate = 0

antialiasing

You can force MSAA for d3d9 games using # d3d9.forceSwapchainMSAA = -1. MSAA is fundamentally incompatible with the way most games work though.

Oh! I had no idea sorry, I've been experimenting with DXVK for a couple of weeks but just quickly read through the readme. I'll try this as soon as possible thanks a lot!
Maybe that could be worth mentioning in the readme (or maybe I missed it too sorry if that's the case).
Anyways, that's really great and I'll definitely give it a try :)

I have a technical question though, when you enable d3d9.forceSwapchainMSAA for example, does it uses a Vulkan feature? Or does it allows the GPU driver to take control of this particular part of the rendering?

Not sure what you mean, of course it's using a Vulkan feature and that Vulkan feature is implemented in the GPU driver.

For example there are several ways to control MSAA in nvidia's control panel, edge anti aliasing, transparency multisampling, transparency supersampling, etc... the d3d9.forceSwapchainMSAA will only allow edge smooth style of AA or everything MSAA related supported by the GPU driver?

Just regular edge anti aliasing.

That's just me being greedy thanks for clarifying this! I suppose D3D9 MSAA transparency supersampling support is not in the priority list as there might be much more important things to consider first :D

So, I've been trying all those things, everything works very well, MSAA is broken in STALKER but thats because the game's implementation wasn't finished back in the days.
However it is super impressive how on Windows, even if DXVK isn't the intended platform, the framerate jumps from 190 in DX9 to 230 FPS in Vulkan (the gap can be even more in CPU bottlenecked areas), your framerate limiter is also a godsend, at 140 FPS on 144 Hz with Vsync off Adaptive Sync is rock solid stable with no stutter or tearing whatsoever and the inputlag is nowhere to be seen (and I am very inputlag sensitive), this is extremely good stuff.
On Linux it's more like 200 FPS on the same savefile and game config, probably a bit of performance loss because of the obligatory Proton layer (Wine's fault, most certainely), but still very impressive nontheless.
Thinking of antialiasing, I wonder if Vulkan supports a good old brute force SSAAx4 method of supersampling (4 pixels to 1), that maybe doesn't require specific game implementation. One would just increase the game's resolution and downsample, but on some games that makes the HUD unreadable, a necessary evil probably.

Thinking of antialiasing, I wonder if Vulkan supports a good old brute force SSAAx4 method of supersampling (4 pixels to 1), that maybe doesn't require specific game implementation. One would just increase the game's resolution and downsample, but on some games that makes the HUD unreadable, a necessary evil probably.

You can try rendering the game at higher resolution and scale it down, on Windows with GeDoSaTo and on Linux with gamescope. :)


slow clapping

Managed to fix the config being written to the same folder as sniper.py.

will use some code later. But this isn't how it's intended to function. I might actually change it's way of functioning in the future.


add multihash message datatype

#63

Could you fix merge conflicts?

@akru, please check that conflict resolution consistent with https://github.com/airalab/robonomics_comm/commit/646b1d5e326cca120f918b48c551460948554210


TensorFlow/XLA reports an internal error "Duplicate variable passed tp XLA cluster" when build and run BERT

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):

Linux Ubuntu 16.04.3

Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary):

source

TensorFlow version (use command below):

ToT

Python version:

3.6

Bazel version (if compiling from source):

19.04

GCC/Compiler version (if compiling from source):

5.4.0

CUDA/cuDNN version:

10.0/7.4

GPU model and memory:

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with: 1. TF 1.0: python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)" 2. TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"
Describe the current behavior
When XLA is off,  the BERT compiles fine.
Describe the expected behavior
Code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate the problem.
The following code pattern in the TF graph will expose the problem,
op0:  Node "VarHandleOp"
op1:  Node "Switch" op0, pred
op2:  Node "ReadVariableOp" op0
op3:  Node "ReadVariableOp" op1
Whem op2 and op3 are clustered together in XLA,  the inputs op0 and op1 are
considered resource arguments, and they happen to map the the same resource
op0, and lead to the error  "Duplicate variable passed to XLA cluster" reported at
line 135, xla_launch_util.cc.
I am worarounding the problem by placing constraint on clustable nodes in
mark_for_compilation_pass.cc, so that nodes with resource input from a "Switch"
node be rejected for clustering.  Some people suggest that it may be better to fix
the problem where the problem is reported.
Other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

This is a current limitation of XLA (not allowing the same resource variable to flow into a cluster twice). There is a change in flight that will make XLA fall back to normal tensorflow execution but that probably is not what you are looking for.
The change you are proposing might fix the immediate issue at hands but does not really solve the problem. There are other ways that a resource variable might end up aliasing. But as a workaround for your problem it is possibly fine.
I have to check up on XLA semantics around resource variables to see whether this is a limitation of the runtime or rather a conceptual mismatch with XLA semantics.

Thanks for your quick response.  I would think fall back to TF-native is not a good option for the case,
though it is a way to avoid the problem going forward, but it may cause potential performance
issue, too.
I thought "Switch" may be a special case causing the problem, not sure if you could provide
examples of other cases with the same problem (duplicated resources passing to the same cluster),
On the workaround, do you think I should file a PR to get it into the ToT ?

@jlebar

@sherhut works on XLA and appears to be on it?

The following code pattern in the TF graph will expose the problem,
op0: Node "VarHandleOp"
op1: Node "Switch" op0, pred
op2: Node "ReadVariableOp" op0
op3: Node "ReadVariableOp" op1

This seems suspicious to me -- op2 and op3 should not be in the same cluster because they have different deadness.

Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!


Force CSV quoting for all non-numeric values

I used to get some invalid CSVs (hard to reproduce since --user option doesn't support time ranges). This explicit quoting strategy fixed that.
Looking forward for comments!

@petrbel  Looks like an simple addition which can fix issues for people writing to CSV!
Thanks


Add explicit no shutdown and switchport config

Change Summary

Ensure that configurations for no shutdown and switchport are rendered explicitly
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[X] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes)
[ ] Documentation content changes
[ ] Other (please describe):

Related Issue(s)

Component(s) name
eos_cli_config_gen
Proposed changes

Shutdown

If shutdown: false we now render no shutdown
If shutdown: true we still render shutdown
If shutdown is not defined we still don't render anything.

This will enable future support for flipping the EOS default to shutdown, protecting unconfigured ports.
Switchport

If type: routed we still render no switchport
If type: switched we now render switchport
If type is not defined we now render switchport

This will enable future support for flipping the EOS default to no switchport, protecting unconfigured ports.
How to test

Tested port-channels, members, switchports, routed ports, shutdown, no shutdown combinations.
Test result here:
https://github.com/ClausHolbechArista/claus-l3ls-dev/commit/39f715e132639b775069c001dc04131b3225dbf5
Checklist:

[ ] I have read the CONTRIBUTING document.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed (pre-commit, make linting and make sanity-lint).
[ ] I have updated molecule CI testing accordingly

Working on new CI artifacts...

@titom73 I am updating CI again with the latest l3ls changes.


use bitset in the structMeta other than uint64

But in the my project.The number of one struct fields is 103 , larger than 64.So I think using a bitset struct in structMeta other than uint64 may be better.

Thanks for the patch. Just a couple of small issues if you could look into.


Refractor the code of 'Chat.jsx' in linkup-frontend

Hi, Can I contribute to this?

Hello @femzy123, I have assigned you the issue, you may start working on it

@arpittyagi102 What type of refactoring do you need ?

@anmol111pal, I want to seperate the socket events to a seperate file


Describe more detail on 1) Zowe and z/OSMF on different LPARS and 2) purpose of >1 instance directory

Is your request for enhancement related to a problem? Please describe.
Customer query on slack channel.
In a shared file system setup, I can only have z/OSMF up on one member of the sysplex
at a time ... which has been perfectly fine for us. (1) It appears that Zowe requires z/OSMF
 to be active, therefore I have an assumption the Zowe can only be active on whichever
LPAR z/OSMF is currently active. Is that correct? (2) Statements in the Zowe install doc refer
 to multiple instances of Zowe sharing the keystore. I understand that concept and can see
that if I brought Zowe (and z/OSMF) down on LPAR 1 and started it up on LPAR 2, the same
 keystore could be used. So if that is a different instance of Zowe, I'm good. But other
readings of the install doc imply that I might want multiple instances active at the same
 time on a single LPAR. Why? Security controls? Other?

Describe the solution you'd like
Better doc to describe

Zowe and z/OSMF on separate LPARs
What scenarios >1 instance directory make sense

Hello,
I am also interested by a clarification : I have a sysplex with 4 lpars, zOSMF on only 1. If I want ZOWE on the 4 lpars, should I have a zOSMF on all of them ?
Regards

Hello,
I am also interested by a clarification : I have a sysplex with 4 lpars, zOSMF on only 1. If I want ZOWE on the 4 lpars, should I have a zOSMF on all of them ?
Regards

If all the LPARs are on the same sysplex, then one z/OSMF is enough.


Feature/tx status

requires https://github.com/trustlines-protocol/relay/pull/455
Based on https://github.com/trustlines-protocol/clientlib/pull/312 for first commit

Codecov Report

Merging #322 into master will decrease coverage by 0.37%.
The diff coverage is 42.55%.

@@            Coverage Diff             @@
##           master     #322      +/-   ##
==========================================
- Coverage   62.39%   62.02%   -0.38%
==========================================
  Files          20       20
  Lines        1242     1277      +35
  Branches      240      247       +7
==========================================
+ Hits          775      792      +17
- Misses        406      424      +18
  Partials       61       61

Flag
Coverage Δ

#integration
34.69% <38.29%> (+0.31%)
:arrow_up:

#unit
62.02% <42.55%> (-0.38%)
:arrow_down:

Impacted Files
Coverage Δ

src/typings.ts
100% <100%> (ø)
:arrow_up:

src/wallets/EthersWallet.ts
60.39% <23.07%> (-4.05%)
:arrow_down:

src/wallets/IdentityWallet.ts
58.55% <36.84%> (-0.89%)
:arrow_down:

src/signers/Web3Signer.ts
57.89% <50%> (-0.6%)
:arrow_down:

src/providers/RelayProvider.ts
61.11% <50%> (-1.39%)
:arrow_down:

src/Transaction.ts
97.82% <50%> (-2.18%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 13aded2...c44f3eb. Read the comment docs.


I understand that the brief description for the recipse comes from the metadata.rb file. I've got this working, but I wonder whether there is a way to also get a more detailed description, which would be documented within the recipe file probably at the top of the file.
Is this somehow possible?

can you try this with 2.0?


System.SObjectException: SObject row was retrieved via SOQL without querying the requested field

I upgraded from 1.5.53 to 1.5.66 and one of our tests breaks with this exception:
05:52:24.438<PHONE_NUMBER>3)|FATAL_ERROR|System.SObjectException: SObject row was retrieved via SOQL without querying the requested field: Utility_Account_Subscription__c.Opportunity__r
Class.RollupRelationshipFieldFinder.areParentFieldsAlreadySet: line 752, column 1
Class.RollupRelationshipFieldFinder.getFullRecalcParents: line 729, column 1
Class.RollupRelationshipFieldFinder.getParents: line 189, column 1
Class.RollupAsyncProcessor.getCalcItemsByLookupField_rMap$$lString$$cRollup$$dCalcItemBag$$r_0RollupAsyncProcessor_1Set$$lString$$r: line 832, column 1
Class.RollupAsyncProcessor.process_rvoid_0List$$lRollupAsyncProcessor$$r: line 658, column 1
Class.RollupAsyncProcessor.performWork: line 345, column 1
Class.RollupAsyncProcessor.QueueableProcessor.execute: line 434, column 1
I downgraded to 1.5.63 and the test worked, so it looks like a more recent change caused this?
Here is the debug log at 1.5.66:
debug log.txt

Thanks, that did it!

No problem, glad to hear it!


Install fails on Ubuntu: bad config line 1

In a script I am running:
RUN curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.34.0/install.sh | bash

But get the following errors:
=> Downloading nvm from git to '/root/.nvm'
=>
Cloning into '/root/.nvm'...

fatal: bad config line 1 in file /root/.gitconfig

Failed to clone nvm repo. Please report this!

Any ideas?

Sounds like your gitconfig is broken, which is unrelated to nvm.
Closing, but if you post the contents of that file i can try to help you figure it out.

Hmm, the entire gitconfig is as follows (made up email address):
[user]
        email =<EMAIL_ADDRESS>

Seems fine but if git’s complaining then I’m not sure what to do.


Added CLI command to deploy selected services/modules in production

Can one of the admins verify this patch?

test this please

test this please

test this please


Added MultiplexedStreamReader

Added a simple reader for the multiplexed stream used for getting logs from containers which can read lines as strings. Also works with the service logs pull request i've made.
Ideally the multiplex stream would extend the stream class or something so we can use the normal stream reader but this is working for me.

@galvesribeiro I have updated this one with cancellation support.


adding Deployment Metric to DB

Changes for adding the Deployment Metric to DB with GORM

Our initial plan was to create the EndStatus function in the handler status.go but we were not able due to circular imports that on handler common.go we're already importing the "server/engine" thus not able to import the "handler/status" in the engine.go.
Apart from that, we decided also to duplicate the function GetLatestExecution into telemetry.go due not able to import the "handler/status" as well.

I faced something similar when trying to create a new file telemetry.go in the api package. It seems like api and handler packages are not usable when it comes to calling something in engine.go, so the only packages we can use now are model and/or engine for our changes. These changes might not all be the "right fit" for a "model" or "engine" package, but that's about the only option we have.

I took a look but thought I'd wait for updates due to Tomas' comment to look again.

Reopening


Release on crates.io

I want to publish NLPRule on crates.io. A couple of things that need to be done:

[x] Clear distinction between public / private API in Rust
[x] Minimum acceptable documentation for the public API
[x] Fix dependencies, specifically NLPRule depends on an unreleased version of serde-xml-rs (https://github.com/RReverser/serde-xml-rs/issues/145).
[x] Find a way to rename the rust crate to nlprule from nlprule_core without clashing with bindings/python/Cargo.toml.
Make rayon (and related dependencies) optional. No easy way to do this, so will not be done unless needed.

Done as of Release v0.3.0

Done as of Release v0.3.0


GelfAppender::close() throws NPE on update if Graylog was not available before

in case Graylog server wasn't available and now the log4j property file changes (with "watch"), the close method will fail on NPE. Here's the fix:
public class MyGelfAppender extends GelfAppender {

    @Override
    public void close() {
        GelfSender x = this.getGelfSender();
        if (x != null) {
            x.close();
        }
    }
}

Version 1.1.14 with fixed released.


Universal Sentence Encoder for embedding

Openai embedding is quite weak, proprietary and token hungry. Lets move to USE. PDFGPT has an implementation of USE we can modify and build upon.

The project seems like that it uses scikit KNN retriever. Qdrant's cosine similarity search will be more powerful than KNN. The main feature i can get from it is how I get the embedding vectors.
I already implemented Transformer embedding, which uses embedding model from Huggingface.
This requires pytorch library, and your link requires tensorflow.
I will add both as seperate modules and add some requirements.txt files.
BTW, both local embeddings require a lot of computing resources. Make sure your environment is strong enough.
I tested intfloat/e5-large-v2 and it almost freezed my 13600K, handling 20 pages of PDF.


enhancement(plugin/datadog) Added response size as metric

New metric response_size added to log request size to statsd server

Look good but maybe we want to wait after 0.6 release since there shouldn't be any new RC before it.

Just finished changes you advised, pushing it now

Done, need to be reviewed


When searching for "fin", "dorsal fin fold" appears before "fin" in the ZFA ontology

The results are correct, here's the hierarchy:

zebrafish anatomical entity
anatomical structure
multi-tissue structure

I can't seem to find any relationship to include that would establish the order we want.

It might make little sense to use the depth when two terms are not topologically related. We'd probably be better off relying on the full-text similarity.


The "Install the Azure VM Agent on Linux VMs" link points to Log Analytics Extension page.

Hello.
"Install the Azure VM agent on Linux VMs" redirects reader to the Log Analytics Agent page. The Azure VM Agent handles reporting on the health of installed Extensions (e.g. Azure Log Analytics agent-extension) as well changes to the Log Analytics agent. One of the references below would be a good fit though:
How to update the Azure Linux Agent on a VM
https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/update-linux-agent
WALinuxAgent
https://github.com/Azure/WALinuxAgent
Daniel
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b3253bbe-28a6-7852-af56-7899380e84d9
Version Independent ID: 6fba630c-4017-46ba-0305-39361f4ebf43
Content: Troubleshoot Azure Log Analytics VM Extension - Azure Monitor
Content Source: articles/azure-monitor/platform/vmext-troubleshoot.md
Service: azure-monitor
Sub-service: logs
GitHub Login: @bwren
Microsoft Alias: bwren

@InformTechPro Thanks for your comment! We will review and provide an update as appropriate.

@InformTechPro Good catch! I have review the document and I realize that this document is more suitable than this because the title of it contains "Update" but not "Install".  So I have verified and updated the referred document as required. The update should go live in some time i.e., in less than 24 hours. Thanks for the feedback!


UTA NO PRINCE SAMA REPEAT LOVE SCRIPT

PLease I am begging on my knees, can I have the script for Uta no prince repeat love on ryujjinx

+1!

Only on yuzu


Integration is using deprecated DEVICE_CLASS_* constants

Version of the custom_component

Any.
Describe the bug
This custom integration uses deprecated DEVICE_CLASS_* constants in its codebase.
The DEVICE_CLASS_* constants have been deprecated and replaced in Home Assistant Core 2021.12 (over a year ago). I would highly suggest updating/migrating this integration to the new enums.
For example, for the device classes supported by the sensor platform, there is now a SensorDeviceClass enum. So if a sensor previously used the DEVICE_CLASS_ENERGY constant, it should now use SensorDeviceClass.ENERGY. Other platforms (like binary_sensor, and number) provide similar enumerations for their supported device classes.
The migration thus only consists of replacing constants with an enumeration member and is, therefore, very low impact and should be fairly straightforward.
If I can help resolve any questions regarding this change or migration, feel free to ask or respond to this issue. I'm happy to help!
Kindest regards,
../Frenck
Debug log

n/a

Thanks for pointing that out, I overlooked it.

No problem! Thanks for updating the implementation @DeerMaximum 👍
../Frenck


Updated keyserver README.md and .travis.yml

Problem:

The keyserver used is not available any more.

Proposed Changes
Changed keyserver to existing one

Might been a hickup... Works now again...


Command Use module not working in docker container

Command Use module not working in docker container and all modules set disabled how I can set Enabled all modules with one command?

I try call command inside container but nothing

Both of these features are depending on a disk, a file is written.
I'm guessing something could be wrong with the setup of your docker container.
There's no command to set all modules to enabled built in. It's easy for you to create it however. Loop over all modules, and set them to enabled.

Command  module:use writes to modules_statuses.json in storrage / app?

No that file is written by the activator.
Module used, writes in storage/app/modules/module.used

@nWidart strange, but I don't have this folder in my project

That's weird, I just used it again locally and the file was created.


crash at forge loading screen

Mod Version:
<IP_ADDRESS>
Forge Version:
<IP_ADDRESS>54
Link to client log:
https://hastebin.com/lubugupoci.md
Link to crash log:
https://hastebin.com/uyajodegun.sql
Description:
it crashes when i have the mod in my mods folder

You need to update Dynamic Surroundings to either <IP_ADDRESS> or <IP_ADDRESS>.

You need to update Dynamic Surroundings to either <IP_ADDRESS> or <IP_ADDRESS>.

its fixed now thanks


Fields on interface fragment spreads don't get resolved

Describe the bug
When resolving fields defined on an interface, if the field is defined within a fragment spread, then it is omitted from the output.
I'm happy to work on a fix for this, but will need some guidance on where to look (and whatever other tips/hints you could give me).
To Reproduce
Using the schema defined in juniper/src/tests/fixtures/starwars/ (I ran the juniper_rocket_async example to reproduce):
Working
A simple query returns the expected result (id and name fields are populated).
query {
  hero {
    id
    name
  }
}

{
  "data": {
    "hero": {
      "id": "2001",
      "name": "R2-D2"
    }
  }
}

Broken
But this query, using a fragment spread on the Character interface, is broken (id and name fields are omitted in the response):
{
  hero {
    ... on Character {
      id
      name
    }
  }
}

{
  "data": {
    "hero": {}
  }
}

Expected behavior
The second query above should return the exact same output as the first query.
Additional context
I encountered this problem using Relay in my UI, as parts of the query being generated by Relay use this pattern. Which leads me to believe that these queries should definitely be valid.

This is clearly a regression from 0.15.3. I downgraded juniper and all related crates from 0.15.4 to 0.15.3 and it helped.
Also this bug can be reproduced with unions.

@ArsileLuci I just tried downgrading to 0.15.3 and am still seeing the issue. If this is a regression in 0.15.4 though, I'd be willing to bet it's related to this PR: https://github.com/graphql-rust/juniper/pull/907

@LucasPickering Found the issue. As You've pointed out the problem comes partially from #907
Bug was in typename matching, at this two rows.
fragment.type_condition.item is the name of interface, and it was compared with instance.concrete_type_name(sub_exec.context(), info) which is actually exact name of the type that implements interface.
I have a fix for this, and now preparing tests to eliminate all possibilities of this reoccurring

@ArsileLuci nice find! thank you so much for finding+fixing that, much appreciated

@tyranron looks like regression again. Tested in 0.15.7 - 0.15.10.

@nikis05 hmm...
git checkout juniper-v0.15.11
cargo test -p juniper_tests issue_922

This works just fine.
Maybe the test is not good enough? Could you provide repro code?

@tyranron I put together a minimum reproduction https://github.com/nikis05/juniper-bug/blob/master/src/lib.rs

@nikis05 thanks for crafting MRE. This is a bit of a different issue there, caused by spreading interface fragment on interface (... on Character where Character is an interface, not an object). This is a known issue for juniper 0.15, and unlikely will be fixed there. However, this works OK on master. I advise switching to it. There shouldn't be any major breaking changes for the current master until it gets released, which I plan to do shortly in a near future.

I covered your MRE in master to prove that it works.


Remove unnecessary renaming during dereferencing

I think there is actually a bug/typo in the test, the command is to rename comon to common, but the expected name is still comon. @EricWittmann wdyt?


MLNCustomStyleLayer + Metal example

Rename MLNOpenGLStyleLayer to MLNCustomStyleLayer
implement example Metal Custom Layer

Oh but there are plenty... I'm in the process of resolving them. :)


Question: Possible to mimic Google embedded look

Hello people, thanks for your good work on this lib.
We were looking to do something similar to this but on the mobile, is this something which can easily be accomplished through the use of this library? Alternatively anyone know the most appropriate way to achieve something like this? Basically a pre-set place shown on a map, rather than just a marker.
Thanks!

I'm not aware of any API to do something like this natively. If you do some research and find anything though, let me know and we might be able to bake it in.


How to Enable TEGRA_DRM? ( for wayland )

Hi
Now I am build AGL with meta-tegra layer.
So, I get AGL image for jetson-tx1 EVK  successfully Thanks.
But When I boot AGL on jetson-tx1 EVK, I can't see weston-launcher screen.
So, I excuted weston-laucher manually and get follow errors.
root@jetson-tx1:~# /usr/bin/weston-launch --tty /dev/tty1 --user root -- --idle-time=4294967
Date: 2017-06-02 UTC
[03:34:31.978] weston 1.11.0
               http://wayland.freedesktop.org
               Bug reports to: https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland
component=weston&version=1.11.0
               Build: 1.10.93-2-g2d825ed configure.ac: bump to version 1.11.0 for the official release (2016-05-31 17:10:40 -0700)
[03:34:31.978] OS: Linux, 3.10.96+, #14 SMP PREEMPT Mon Jun 5 18:42:52 KST 2017, aarch64
[03:34:31.979] Using config file '/etc/xdg/weston/weston.ini'
[03:34:31.979] Output repaint window is 7 ms maximum.
[03:34:31.979] Loading module '/usr/lib/weston/drm-backend.so'
[03:34:31.982] initializing drm backend
[03:34:31.982] logind: failed to get session seat
[03:34:31.982] logind: cannot setup systemd-logind helper (-61), using legacy fallback
[03:34:31.983] no drm device found
[03:34:31.983] fatal: failed to create compositor backend
failed to restore keyboard mode: Bad file descriptor
failed to set KD_TEXT mode on tty: Bad file descriptor

I think that I need DRM for executing weston-launcher.
So, I added TEGRA_DRM using 'make menuconfig'.
But Still I got same error as well. I think DRM is not working very well.
Can I get some information about that?
Thanks,

My knowledge of this is limited, but as far as I know, NVIDIA does not provide the binary bits needed to use the DRM backend for weston on the Jetson boards, so no, you can't use weston-launcher. You should be able to use XWayland - I think the NVIDIA-supplied libraries provide enough support for that.

Official kernel version for jetson-tx1 is 3.10.
If I upgrade kernel version, Can I use DRM?
Because I saw another github which try to enable DRM.
But kernel is not official, 4.9.2
Thank you for your response!