Change terminology to Allowlist and Denylist

Summary
Follow up #6464, #6466, and #6467.
This PR changes a terminology from Whitelist and Blacklist to Allowlist and Denylist.
This change is an obvious breaking change to some cop options. So I'd like to introduce it before RuboCop 1.0 if this change is acceptable.
Other Information
This change has also been made in Rails repository and other repos.
https://github.com/rails/rails/pull/33681

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[ ] Added tests.
[ ] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Run bundle exec rake default. It executes all tests and RuboCop for itself, and generates the documentation.

I agree with the overall premise and the timing of the change, but I think we can do better with the naming - e.g. instead of naming something Allowlist it can be AllowedPatterns or something like this. I'll leave a couple of inline remarks.

@rubocop-hq/rubocop-core Please add your feedback here as well, if you have some. My general point is that we should try to do something more than just auto-replacing the existing problematic names. From my perspective the use of generic names like whitelist/allowlist also has an usability impact, as it's never clear a list of what we're referring to.

Please add your feedback here as well, if you have some. My general point is that we should try to do something more than just auto-replacing the existing problematic names. From my perspective the use of generic names like whitelist/allowlist also has an usability impact, as it's never clear a list of what we're referring to.

I have nothing against replacing whitelist and blacklist, but I agree that there are better contextual options in most cases. 👍

I brushed up this PR. I would be happy to get suggestions if you have other good names :-)

Thanks!


chore(main): release volcano-data-deconvolution 1.0.1

:robot: I have created a release beep boop
1.0.1 (2024-06-03)
Documentation

zenodo: add JSON file for zenodo publication (670431b)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/engeir/volcano-data-deconvolution/releases/tag/volcano-data-deconvolution-v1.0.1 :sunflower:


[nl] update how scraper waits for charts to be loaded

instead of always waiting 5 seconds for charts to load, wait for loading placeholders to disappear, then wait for svgs to be drawn

comparing the time spent waiting between the old and new methods (look for time_taken & the time is in seconds):
old method: https://paste.googleplex.com/5697023377408000
new method: https://paste.googleplex.com/5627238262243328

thanks for the review!


Remove "Numeric" answer type for templates

Related issue reported in Roadmap repo, but it looks like we need to fix it here?
https://github.com/DMPRoadmap/roadmap/issues/1219
below is a screenshot from dmptool-stage that includes a "Numeric" question type, which is clearly not available on roadmap. I assumed it should be the same...? whatever the case it's not working so we should go ahead and fix/remove it from the code wherever it's coming from.

From Jose: The question format combobox it's populated with the question formats present in question_formats table. We should have the following types right now:
["textarea", "textfield", "radiobuttons", "checkbox", "dropdown", "multiselectbox"]
@bhavi will remove the number/date options from our migration script

i made a note of this in the launch checklist. the options are gone from the question type list on dmptool-stg after the most recent migration so i'll consider it closed.


Added profile configuration parameter to ec2_sd_configs

We use federated logins with rotating tokens so configuring Prometheus with tokens is a pain. This PR will allow us to use a profile with rotating tokens for local Prometheus testing.
I upgraded the aws-sdk-go package as part of this, since they improved session handling since it was vendor'd.

@beorn7 @fabxc any thoughts on this?

If it's a valid authentication mechanism and doesn't break any existing use case, this is okay with me.
Can you confirm that it doesn't break any other use case @bigkraig?

Hey @fabxc, I just double checked that everything is still functioning with access_key & secret_key pairs. It looks good to me!

Thanks for the clarification 👍
My delayed response caused a merge conflict. I'll rebase and merge directly into master.

@bigkraig this change has nothing to do with IAMInstanceProfiles, right? Looks to me as if those are not supported at all at the moment, right?

@tobstarr right, this is just for STS. IAM instance profiles were already working, you should just leave all of the variables empty

@bigkraig Thanks for the heads-up. So also leave out the region?
I tried to set that up but nothing showed up in neither the targets, nor the logs. Will try to make the logs a bit more verbose.

I'm not sure about the region but I'd leave that in. You can always run the AWS CLI tools on an instance with the role and test things out too.

Hey!
Is this supposed to work with credentials and config files on .aws folder on home directory?
I have this on .aws/config:
[profile default]
region = us-east-1

[profile super_role]
source_profile = default
role_arn = arn:aws:iam::XXX:role/Prometheus
region = us-east-1

I have on prometheus.yml
- job_name: node-ec2-us-east-1
  ec2_sd_configs:
    - region: us-east-1
      profile: super_role
      port: 9100

But I got this:
ERRO[0000] could not describe instances: NoCredentialProviders: no valid providers in chain. Deprecated.
	For verbose messaging see aws.Config.CredentialsChainVerboseErrors  source="ec2.go:102"

@joaogbcravo yeah that is right, not sure why that isnt working. can you use that with a --profile parameter to awscli?

Hey!
Yes I can.
Something like
aws ec2 describe-instances --profile=super_role
works for me


Refactor rotational transformation for red alliance

state.poseMeters.getRotation().times(-1) will return -PI when PI is inputted, but when the robot is on the opposing alliance, the rotation needs to be 0 degrees if 180 is inputted, to preserve the holonomic rotation facing the grid.
The cpp equivalent for this still needs to be made.
Co-authored-by: Alexander Hamilton<EMAIL_ADDRESS>

I should also mention that #207 should be mirrored on the X axis and not the Y, as seen in this Cheif Delphi post, meaning that I should have included this change in the PR.

I had to include the java docs haha

Hi @PatribotsProgramming, please read discussion #261

rotation needs to be 0 degrees if 180 is inputted

This is not correct. 0 Degrees is facing away from your driver driver station wall.
Also, the alliance transformation stuff is correct, so I will be closing this. If your coordinate system is different from what the WPILib standard is then you will need to implement the transformations yourself, since PPLib will follow the wpilib standards.


Bayes bounds errors when 0 in the energy spectrum

The Bayes bounds break when the energy spectrum extends down to 0 energy. For now, avoid putting a 0 in your energy spectrum. I'll fix this as soon as I find some time

Gave this a temporary fix in PR #231


2024-11-28_01-35-52_master-next_aws-cli

Automatically created.

Backport failed for kirkstone-next, because it was unable to cherry-pick the commit(s).
Please cherry-pick the changes locally and resolve any conflicts.
git fetch origin kirkstone-next
git worktree add -d .worktree/backport-10548-to-kirkstone-next origin/kirkstone-next
cd .worktree/backport-10548-to-kirkstone-next
git switch --create backport-10548-to-kirkstone-next
git cherry-pick -x 51b0d22f3727cc0e6e03aa1eb8c278542dc18945

Successfully created backport PR for scarthgap-next:

#10554

Successfully created backport PR for styhead-next:

#10555


WIP use Arc instead of Arc

This should fix one of clippy errors we started to see with latest stable 1.48.0
https://rust-lang.github.io/rust-clippy/master/index.html#rc_buffer

I would like to wait for #145 merge. I may need to resolve conflict related to this merge

yeah, that was what i was seeing on clippy nightly. i also wonder about that toString recursion issue...

yeah, that was what i was seeing on clippy nightly. i also wonder about that toString recursion issue...

I plan to propose a pull request after the merge of this one

I guess we have to wait a bit, switching CI is never a simple choice.


Package and document analysis code

Bring all code required to create figures into a form that can be re-used and reproduced.

[ ] Prepare Conda environment file with all dependencies
[ ] Organize code
[ ] Document how to run the code
[ ] Publish

The repo for testing can now be found here: https://github.com/zavolanlab/test_htsinfer


[WFLY-12226] Horrible hack to avoid complaints return type for proper…

…ty useseTopologyForLoadBalancing
https://issues.jboss.org/browse/WFLY-12226

Some custom CI runs:
https://ci.wildfly.org/viewLog.html?buildId=157245&tab=buildResultsDiv&buildTypeId=WF_MasterElytron
https://ci.wildfly.org/viewLog.html?buildId=157247&tab=buildResultsDiv&buildTypeId=WF_MasterSecurityManager
https://ci.wildfly.org/viewLog.html?buildId=157249&tab=buildResultsDiv&buildTypeId=WF_MasterIPv6
https://ci.wildfly.org/viewLog.html?buildId=157251&tab=buildResultsDiv&buildTypeId=WF_MasterWindowsJdk11


implement the Red Wedding

The Red Wedding will be implemented in stages. The first stage is implementing DEEP-ALI in #190.


Can't upload from AWS CodeBuild - 400 - Invalid request parameters

Describe the bug
I'm getting an error when trying to upload from AWS CodeBuild:
['error'] There was an error running the uploader: Error uploading to https://codecov.io: Error: There was an error fetching the storage URL during POST: 400 - Invalid request parameters
To Reproduce
Steps to reproduce the behavior:

Create AWS CodeBuild project with aws/codebuild/standard:6.0
Try to upload with ./codecov -t $TOKEN

Expected behavior
Should upload coverage.
Screenshots

An update on this one. Looks like the issue is with the commit parameter.
If I manually change it with -C some_valid_sha it works fine.

@lrodrigo-cluey
https://github.com/codecov/uploader/blob/b2a22e83fdeac797948e93bbffc435df73ee24f2/src/ci_providers/provider_codebuild.ts#L51
It's possible the env we are checking has changed, or is empty in certain cases. Are you able to check?

@drazisil-codecov it is returning some value, you can check that in my screenshot (...&commit=pc5T...)
I believe the issue is that the sha is invalid, because it works fine if I manually set it with -C.

@drazisil-codecov it is returning some value, you can check that in my screenshot (...&commit=pc5T...) I believe the issue is that the sha is invalid, because it works fine if I manually set it with -C.

Can you check and see if there is a better env we can check?

Closing for lack of input. Please reopen with further details if this is still an issue.


Improved the layout of the whiteboard

Hi Weilong,
I simplified the whiteboard and tried to fit it in the window. Please approve if you think the update is fine. Let me know otherwise.
Kind regards,
Prabhav

Perfect!


Switch from PEAR to Composer.

Fixes https://github.com/urlgrey/hsmm-pi/issues/96.
For review @urlgrey @cbegg50
/cc @syelnmh
This change switches from PEAR to Composer, which is CakePHP's only supported install mechanism beginning in version 3. I tested this on a Raspberry Pi 3 and it worked well.

/cc @tylert

👍


Recycle jogging shoes?

Jogging shoes piling up while shoe stores and running experts keep advertising shoes' shock absorption capability diminishes surprisingly quickly, which I kind of agree from experience. So one way to feel less bad about piling up shoes and buying new jogging shoes might be to recycle older shoes.
CoS

[ ] Investigated existing solutions.
[ ] First trials (level of trust about the solution, financial and temporal cost)

Article from Fleet Feet (which is apparently on the commercial side, can be naturally motivated to sell more shoes) suggests TerraCycle and Nike.
After reviewing I decided to give a shot on TerraCycle even though their service actually costs a good amount of money. I'm just trying for a good intention and see what will happen.


Parameter mixin

Moved code from sources-api into the common gem for strong parameter check based on openapi.json

@bdunne @Fryguy
Please review


Cranelift: sdiv.i32x4 panics during codegen on x86_64

.clif Test Case
function u0:0() system_v {
    const0 = 0x000000280000001e000000140000000a
    const1 = 0x00000004000000030000000200000001

block0:
    v0 = vconst.i32x4 const0
    v1 = vconst.i32x4 const1
    v2 = sdiv v0, v1
    return
}

Steps to Reproduce
Script to reproduce the issue (minimized from https://gitlab.com/veloren/dev/veloren/-/blob/5c4a5908f1c996560d7d8fa68a7a1f1cffb50971/world/src/site2/gen/jit.rs#L864-919):
cranelift_sdiv_20220505.rs.txt
Expected Results
Either a sequence of instructions that perform SIMD integer division (since it seems like there's no single instruction that does so on x86_64) or a cranelift verifier error.
Hopefully the former, since sdiv is documented as working on "A scalar or vector integer type" at https://docs.rs/cranelift-codegen/latest/cranelift_codegen/ir/trait.InstBuilder.html#method.sdiv
Actual Results
In debug mode, I get
thread 'main' panicked at 'assertion failed: rc_dst == rc_src', /home/avi/.cargo/registry/src/github.com-1ecc6299db9ec823/cranelift-codegen-0.82.3/src/isa/x64/inst/mod.rs:2710:9
stack backtrace:
   0: rust_begin_unwind
             at /rustc/91a0600a5c22b9d159e3c57526af83e71d1120f8/library/std/src/panicking.rs:498:5
   1: core::panicking::panic_fmt
             at /rustc/91a0600a5c22b9d159e3c57526af83e71d1120f8/library/core/src/panicking.rs:107:14
   2: core::panicking::panic
             at /rustc/91a0600a5c22b9d159e3c57526af83e71d1120f8/library/core/src/panicking.rs:48:5
   3: cranelift_codegen::isa::x64::inst::<impl cranelift_codegen::machinst::MachInst for cranelift_codegen::isa::x64::lower::isle::generated_code::MInst>::gen_move
             at /home/avi/.cargo/registry/src/github.com-1ecc6299db9ec823/cranelift-codegen-0.82.3/src/isa/x64/inst/mod.rs:2710:9
   4: cranelift_codegen::isa::x64::lower::lower_insn_to_regs
             at /home/avi/.cargo/registry/src/github.com-1ecc6299db9ec823/cranelift-codegen-0.82.3/src/isa/x64/lower.rs:2919:22
   5: cranelift_codegen::isa::x64::lower::<impl cranelift_codegen::machinst::lower::LowerBackend for cranelift_codegen::isa::x64::X64Backend>::lower
             at /home/avi/.cargo/registry/src/github.com-1ecc6299db9ec823/cranelift-codegen-0.82.3/src/isa/x64/lower.rs:3700:9
   6: cranelift_codegen::machinst::lower::Lower<I>::lower_clif_block
             at /home/avi/.cargo/registry/src/github.com-1ecc6299db9ec823/cranelift-codegen-0.82.3/src/machinst/lower.rs:752:17
   7: cranelift_codegen::machinst::lower::Lower<I>::lower
             at /home/avi/.cargo/registry/src/github.com-1ecc6299db9ec823/cranelift-codegen-0.82.3/src/machinst/lower.rs:993:17
   8: cranelift_codegen::machinst::compile::compile
             at /home/avi/.cargo/registry/src/github.com-1ecc6299db9ec823/cranelift-codegen-0.82.3/src/machinst/compile.rs:31:9
   9: cranelift_codegen::isa::x64::X64Backend::compile_vcode
             at /home/avi/.cargo/registry/src/github.com-1ecc6299db9ec823/cranelift-codegen-0.82.3/src/isa/x64/mod.rs:53:9
  10: <cranelift_codegen::isa::x64::X64Backend as cranelift_codegen::isa::TargetIsa>::compile_function
             at /home/avi/.cargo/registry/src/github.com-1ecc6299db9ec823/cranelift-codegen-0.82.3/src/isa/x64/mod.rs:64:21
  11: cranelift_codegen::context::Context::compile
             at /home/avi/.cargo/registry/src/github.com-1ecc6299db9ec823/cranelift-codegen-0.82.3/src/context.rs:165:22
  12: cranelift_codegen::context::Context::compile_and_emit
             at /home/avi/.cargo/registry/src/github.com-1ecc6299db9ec823/cranelift-codegen-0.82.3/src/context.rs:115:20
  13: cranelift_sdiv_20220505_30bc7f2d1948e7bde4e87623::main
             at /home/avi/.cache/rust-script/projects/30bc7f2d1948e7bde4e87623/cranelift_sdiv_20220505.rs:64:16
  14: core::ops::function::FnOnce::call_once
             at /rustc/91a0600a5c22b9d159e3c57526af83e71d1120f8/library/core/src/ops/function.rs:227:5

In release mode I get
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', /home/avi/.cargo/registry/src/github.com-1ecc6299db9ec823/cranelift-codegen-0.82.3/src/isa/x64/inst/mod.rs:251:33
stack backtrace:
   0: rust_begin_unwind
             at /rustc/91a0600a5c22b9d159e3c57526af83e71d1120f8/library/std/src/panicking.rs:498:5
   1: core::panicking::panic_fmt
             at /rustc/91a0600a5c22b9d159e3c57526af83e71d1120f8/library/core/src/panicking.rs:107:14
   2: core::panicking::panic
             at /rustc/91a0600a5c22b9d159e3c57526af83e71d1120f8/library/core/src/panicking.rs:48:5
   3: cranelift_codegen::isa::x64::inst::<impl cranelift_codegen::machinst::MachInst for cranelift_codegen::isa::x64::lower::isle::generated_code::MInst>::gen_move
   4: cranelift_codegen::isa::x64::lower::lower_insn_to_regs
   5: cranelift_codegen::machinst::lower::Lower<I>::lower
   6: cranelift_codegen::machinst::compile::compile
   7: <cranelift_codegen::isa::x64::X64Backend as cranelift_codegen::isa::TargetIsa>::compile_function
   8: cranelift_codegen::context::Context::compile
   9: cranelift_codegen::context::Context::compile_and_emit
  10: cranelift_sdiv_20220505_30bc7f2d1948e7bde4e87623::main

Versions and Environment
Cranelift version or commit:
anyhow = "1.0"
cranelift-codegen = "0.82"
cranelift-frontend = "0.82"
target-lexicon = "0.12.3"

Operating system: Gentoo Linux (5.10.68-gentoo-dist kernel)
Architecture:
model name      : Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp pku ospke md_clear flush_l1d arch_capabilities

Extra Info

@aweinstock314, good find! I took a look at your script to generate various patterns and it looked interesting; I'm interested in the details of what you are trying to test (something about the "interpreter vs JIT"). I had the vague thought that some of that could be integrated into Cranelift's fuzz testing but I'm not totally sure what is going on yet.
For this issue, though, this bug highlights fixes at multiple levels. First, we could add an assert/panic into the lowering of sdiv to more clearly state that this instruction is not implemented for vector types; your stack traces highlight how there is no proper error message returned. Secondly, I guess we need to decide what to do about vector sdiv:

implement with a sequence like you mentioned--do you really need the instruction, though, or did you just find the error through random testing?
constrain the type of sdiv to only allow scalar types--I'm actually leaning this way because I don't see this instruction implemented in other backends (@akirilov-arm, @uweigand?) and it is not needed for compiling WebAssembly--I'm leaning this direction

The fuzzer/proptest testing isn't directly related to how I found this bug. The overall context is that there's an interpreted language being used for procedural generation that expresses 3d shapes as compositions of simpler shapes (Constructive Solid Geometry), and when rasterizing the shapes to a voxel grid, it's faster to JIT-compile the test for "is a point contained in this shape" than to interpret the AST that represents the shape. Sdiv is being used in the Repeat instruction, which produces a shape composed of several copies of another shape along a specified vector. The fuzzer is producing random ASTs that represent shapes, and checking that the interpreter agrees with the JIT when rasterizing the shapes in a 64x64x64 volume.
I don't think I need vector sdiv necessarily: the shapes rasterize correctly with scalar division, and I'm not sure that Repeat instructions are frequent enough in actual workloads for it to be performance-critical, and if they are, it would suffice for me to translate libdivide_s32_do_vec128 or libdivide_s32_branchfree_do_vec128 to CLIF manually.
Presumably it to be handled in cranelift, you'd want to handle it for all sizes? (I guess cranelift could also lower it into extractlanes, scalar division, then insertlanes, then have optimizations for particular sizes as needed, but that would have somewhat nonintuitive performance implications).

Cg_clif will need it for a fast implementation of simd integer division.

On s390x we don't yet have any SIMD support, so this hasn't been an issue.  Once we add SIMD, we'll have the problem that the current ISA does not actually provide any SIMD integer divide instructions, so if the back-end had to implement a vector divide, I guess we'd have to scalarize the operation manually.

Given the above (not implemented in any backend, and difficult to support with current hardware), I suspect that the right answer is to say that sdiv takes scalar types only. These are always subjective calls at some level, but I think polyfilling a non-hardware-supported operation with a more involved sequence mostly makes sense either when that sequence is a widely-accepted primitive (e.g., popcount) or is supported on all but a few hardware platforms/configurations. Here that seems not to be the case.
We can always widen our support later; perhaps we can reconsider and add a platform-independent legalization in the future. But for now it seems right to reflect the above difficulties in the opcode type restrictions.
I'm happy to do a quick PR to update the opcode definition!


Constants must be pulled from PDOCrateDB:: namespace?

About
@hlcianfagna discovered that addressing constants through PDO:: is no longer viable, one must use PDOCrateDB:: instead.

https://github.com/crate/crate-pdo/pull/151#discussion_r1447431529

Thoughts
It may have happened on the update to PHP 8.

GH-115

Maybe we can converge the code to actually use constants per PDO::, also to be more compatible with vanilla PDO usage patterns?

Will be resolved by GH-151 already. Thanks, @hlcianfagna.


Change jpg to png

Codecov Report

Merging #56 (cd6a401) into master (bb685aa) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #56   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

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 bb685aa...cd6a401. Read the comment docs.


Parse out V1Status for code 422 on Reconcile loop of ManagedController

Give a little better message for errors returned by k8s (at least for code 422).
K8S api will return a V1Status when the API rejects a call. This can be output to the users in the log

@buehler or @tomasfabian :
Just a simple usability addition that will give the users much more context from a hidden error. The current error message will only mention that the change was a 422 vs giving meaningful responses from the api

Thank you for the contribution :-) What do you think about my input for the log message?

@buehler added a response ... lmk your thoughts and if you still want the change, I will do it

Totally makes sense :-)


Remove "open : no such file or directory" message during crash report

Add an empty string check to the path argument of addFile(). Send()
method of BugsnagCrashReporter calls addFile() passing err.LogFilePath
as the path argument, which is an empty string if the driver is not
virtualbox.
Fixes #3559
Signed-off-by: KOBAYASHI Shinji<EMAIL_ADDRESS>

LGTM -- thanks Shinji!
Although I am not sure why we are sending empty string to this method in the first place?

Thanks @nathanleclaire for merging the PR quickly.
The empty string comes from vBoxLog in the function cmdCreateInner() in commands/create.go. It is initialized to an empty string and is set to "VBox.log" when the driver is virtualbox.
                vBoxLog := ""
                if h.DriverName == "virtualbox" {
                        vBoxLog = filepath.Join(api.GetMachinesDir(), h.Name, h.Name, "Logs", "VBox.log")
                }

                return crashreport.CrashError{
                        Cause:       err,
                        Command:     "Create",
                        Context:     "api.performCreate",
                        DriverName:  h.DriverName,
                        LogFilePath: vBoxLog,
                }

So my guess is that there is no appropriate log file to attach to the crash report for the drivers other than virtualbox.


Add support for function breakpoints in debugger

Add breakpoint setting/unsetting tests

@axelson can you have a look?


Updated for Micronaut 4

Description
Updated for Micronaut 4
Fixes # (issues)
New samples # (demos / Illustrations )
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[Y] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?

[ ] Free Tier
[ ] Always Free
[Y] Paid

Checklist:

[Y] My code follows the style guidelines of this project
[Y] I have performed a self-review of my code
[Y] I have commented my code, particularly in hard-to-understand areas
[Y] I have made corresponding changes to the documentation
[Y] My changes generate no new warnings.
[Y] All the sensitive informations are masked or removed.
[Y] All the links mentioned are valid and tested.
[Y] Image names are seperated only with '-'.
[Y] Added instruction to clone only this sample and links to other common sample pages.

Thank you, @ashok-cm.


NVD mirror to dependency check

Hello,
Usually I have this error  : Fatal exception(s) analyzing Core RH: Unable to continue dependency-check analysis.
[ERROR] Unable to connect to the database
So I think to mirrir the CPE/CVE to have local access
But I don't unterstand how can I add it ! help please
(what is the utility of the database H2 in dependency check , ii contain just the CVE to check the vulnerability ?? )

java -jar nist-data-mirror.jar  what's mean  !! help please

nist-data-mirror is only required if you want to create a duplicate data feed of the NVD inside a corporate firewall. This is completely optional and not required by Dependency-Check. This project has no affect on Dependency-Checks ability to connect to the database.

Thanks @stevespringett  but  what's mean corporate firewall please, Can I unterstand the mecanism to utilize the database H2 and the NVD ??

This project does not use a database. It mirrors files from the NVD to your local filesystem.

this project you mean dependency check !! because when I check the code source , it utilize H2 database (contains the CVE )

This isn't the dependency-check project. This is the nist-data-mirror project which can optionally be used with dependency-check.


feat: upgrade to terraform 13

Fixes #296

The versions.tf is standard terraform syntax now in TF 0.13. Thanks to the new provider source feature all non-hashicorp modules need to have a source defined in the code and it's good practice to also define the source for the hashiscorp modules. The upgrade tool did this automatically so I figured it was worth leaving in.


Splunk Plugin

We already support splunk via our TCP/UDP logging plugins. How would a splunk plugin be different?

There is now a 3rd party Kong splunk plugin:
https://docs.konghq.com/hub/optum/kong-splunk-log/
So I am thus closing this.


Automations - infinity loop issue (MEGH-4304)

It is simple to make infinity loop with Automation feature.
https://user-images.githubusercontent.com/34368502/217755451-d7d65bcd-406d-4e34-844b-877b2da14925.mp4
It can take place because of logic mistake or deliberate action. The result will be generating a lot of traffic on AWS.
It is more probable with complex Automation scenarios and can be unintended and accidentally made by end customer.
I think that there should be some kind of prevention.
I suggest to add some configuration parameters for Automation module:
CONFIG_AUTOMATION_CNT_MAX_VAL - maximum ammount of the_same_Automation_event triggers allowed
CONFIG_AUTOMATION_CNT_TIME_WINDOW - time window for counting Automation triggers
CONFIG_AUTOMATION_INACTIVE_TIME -  Automation inactive time after to much Automation events detection
if too much automation events is detected, it is disabled for a certain amount of time, which will break the infinite loop. Also notification in app appreciated.
E.g.:
CONFIG_AUTOMATION_CNT_MAX_VAL=20
CONFIG_AUTOMATION_CNT_TIME_WINDOW=60
CONFIG_AUTOMATION_INACTIVE_TIME=10
if Automation X occured 20 times per 60 sec., disable Automation X for 10 sec.

@jacek12345 , we will definitely take this up on priority in the cloud backend.


gh-308 - Rename DataRequest to DataSpecification

Rename every instance of 'data request' to 'data specification' throughout all files.

Comments addressed and pr-checks is happy :).


Elasticsearch get / delete / set performance issue

Hi,
I've found that docarray using elasticsearch backend have performance issue when we want to access the attributes or delete using IDs/offsets. When we try to set the logging level at INFO, it shows that whenever we want to invoke slicing/get multiple data, it's not using the ES bulk API but instead call the individual docs API.
E.g. using this script
from docarray import Document, DocumentArray
import logging
import sys

logging.basicConfig(
    level=logging.INFO,
    format="%(asctime)s : %(levelname)s : %(message)s",
    stream=sys.stdout,
)

da = DocumentArray(
    storage="elasticsearch",
    config={
        "n_dim": 3,
        "index_name": "test-docarray",
    },
)

with da:
    da.extend(
        [
            Document(id=f"{i}") for i in range(5)
        ]
    )

with da:
    del da[["2","4"]]

da[:,"id"]

on deletion example the log will show like this
2022-07-11 10:57:03,858 : INFO : HEAD localhost:9200/test-docarray/_doc/2 [status:200 duration:0.034s]
2022-07-11 10:57:03,895 : INFO : DELETE localhost:9200/test-docarray/_doc/2 [status:200 duration:0.037s]
2022-07-11 10:57:03,935 : INFO : POST localhost:9200/test-docarray/_refresh [status:200 duration:0.039s]
2022-07-11 10:57:03,966 : INFO : HEAD localhost:9200/test-docarray/_doc/4 [status:200 duration:0.031s]
2022-07-11 10:57:04,002 : INFO : DELETE localhost:9200/test-docarray/_doc/4 [status:200 duration:0.035s]
2022-07-11 10:57:04,043 : INFO : POST localhost:9200/test-docarray/_refresh [status:200 duration:0.041s]

on retrieving id attribute, the log will show like this
2022-07-11 11:01:12,560 : INFO : GET localhost:9200/test-docarray/_doc/0 [status:200 duration:0.035s]
2022-07-11 11:01:12,594 : INFO : GET localhost:9200/test-docarray/_doc/1 [status:200 duration:0.034s]
2022-07-11 11:01:12,630 : INFO : GET localhost:9200/test-docarray/_doc/3 [status:200 duration:0.035s]

this is not scalable even if the size of the docarray is only 2k, our system endpoint keep getting timeout because of this behavior ( we want to check if list of ids is exist in the doc array, we query the id using da[:,"id"] instead of using private attribute _offset2ids.ids )
if compared to the other method behavior, the extend and _update_offset2ids_meta method have already good implementation using parallel_bulk , or _get_offset2ids_meta which use mget
However, I notice that this behavior is coming from the BaseGetSetDelMixin ( just realized that we can override the method for better implementation ). The base implementation of get multiple documents expressed by iterating item one by one, rather than utilizing the bulk function
    def _get_docs_by_offsets(self, offsets: Sequence[int]) -> Iterable['Document']:
        """This function is derived from :meth:`_get_doc_by_offset`
        Override this function if there is a more efficient logic

        :param offsets: the offsets used for indexing
        :return: an iterable of document
        """
        return (self._get_doc_by_offset(o) for o in offsets)

    def _get_docs_by_ids(self, ids: Sequence[str]) -> Iterable['Document']:
        """This function is derived from :meth:`_get_doc_by_id`
        Override this function if there is a more efficient logic

        :param ids: the ids used for indexing
        :return: an iterable of document
        """
        return (self._get_doc_by_id(_id) for _id in ids)

    def _del_docs_by_ids(self, ids):
        """This function is derived from :meth:`_del_doc_by_id`
        Override this function if there is a more efficient logic

        :param ids: the ids used for indexing
        """
        for _id in ids:
            self._del_doc_by_id(_id)

    def _set_docs_by_ids(self, ids, docs: Iterable['Document'], mismatch_ids: Dict):
        """This function is derived from :meth:`_set_doc_by_id`
        Override this function if there is a more efficient logic

        :param ids: the ids used for indexing
        """
        for _id, doc in zip(ids, docs):
            self._set_doc_by_id(_id, doc)

maybe we can override for ES directly the _set_docs_by_ids  and _del_docs_by_ids without requiring the simple.

Closing in favour or #475


Edit metadata OSM buildings/3D tiles

Hi,
Is it possible to edit metadata about buildings in the OSM buildings dataset e.g. if I want to add a field for 'for-sale' & consequently style the buildings accordingly on the map.

This isn't currently possible without regenerating the 3D Tileset, but it is a feature we've considered. Let's move this discussion to the Cesium community forum. Can you create a new post there with a bit more background about your use case? There's a few different approaches you can take depending on what you're trying to do.

I was wrong, it's possible to edit feature properties in a 3D Tileset in a number of ways. This forum thread explains how to add new properties and style then on the fly, as well as how to make those changes persist: https://community.cesium.com/t/edit-metadata-osm-buildings-3d-tiles/10540/2?u=omar


Improved: bluelight - simplified uris (OFBIZ-11794)

adjusted the main menu ftl to work with simplified uris

Closing here, we can't push related PRs one by one. We need the whole thing for OFBiz to correctly work with the related changes. In other words, it's all or nothing. It seems possible....


Enhance HomePage

Separated original Themes and high-contrast Themes options.
Added a new  theme: ThemeToggleSwitch.
Should we consider removing or redesign ButtonToggleSwitch from Semi.Avalonia? It seems unnecessary and is not used in Semi Design.
Made the left TabControl collapsible.

for button toggleswitch , I think it is still useful. We don't have any button like controls to switch display content.

I assume you want to improve the usability on phones. can you provide a screenshot?

https://github.com/user-attachments/assets/057cc10c-9316-4912-8d78-3f180d293cce


Enhancement Request

Hi, i added states = "[\"" + input("States: ") + "\"]" as an input, and "and geolocation["region"] in states" (line 89) however, it isn't working and tries to launch nothing.   Can this be an enhancement to include cities (called regions) in the US?  Thanks!

Okey.


Update AWS-SDK packages

What
@aws-sdk/client-cloudwatch-node and @aws-sdk/client-resource-groups-tagging-api-node have been deprecated and replaced with @aws-sdk/client-cloudwatch and @aws-sdk/client-resource-groups-tagging-api respectively
This updated the packages and imports where required
Modular AWS SDK for JavaScript
How to review

deploy to a dev env
check affected metrics have data

Who can review
not @kr8n3r

🚨⚠ Please do not merge this pull request via the GitHub UI ⚠🚨

turns out we have a v2 of the sdk and these two packages are v3, so there might be an API or payload discrepancy

somewhere in rebasing from main  metrics tests started to fail ....


Verify RAML implementation in 1.0

Hi,
I started using this library to validate my Spring MVC implementation against a RAML definition. It works pretty well, thanks a lot.
I have found a couple of issues I would like to ask if they are some bugs or it is worked as intended for some reason.
RamlVerifier class hardcodes the creation of the factory to use always version 0.8. I changed it to detect the version depending on RAML file header and it worked.
Some methods in class RJP10V2RamlQueryParametere raise an UnsupportedOperationException in case the type of the parameter is different from expected one. But the class that uses this methods expects they return a null value if the validation does not apply. Therefor, I got this exception for any parameter. I tried returning null values instead of throwing the exception and everything works as expected.
This is a very useful libraty. Good job.
Regards,
Félix.

The hardcoding of 0.8 was intentional since at present we can only go from RAML -> code with 1.0 support.  With the file you tested, did you also include any Raml Types (1.0)?
Changing the QueryParameter to return null instead of throwing an exception makes sense

Yes, I have some types definition, and it is working.

Cool! :) good to know :)
i'll apply these changes to 0.10.3


Writing a generic usb hid module

I'm trying to start to write a keyboard firmware in embassy and I'd really like it to be target-angostic (nrf, rp and esp)
My problem right now is that I can't understand how to make the USB HID generic
The target that I test on right now is an nrf52840
First, I'm not 100% sure what's going on with the tasks.
If I do embassy_usb::UsbDevice::run() does it start a task? Does it block? Is it async?
Second, I'm trying to make a USB HID struct. I want the constructor to do all the setup (reports, descriptors, etc.) in one function and return Self with the HidWriter and UsbDevice. I got around it by creating a target-specific type alias but it doesn't feel super intuitive
The problem that I'm stopped by right now is that both objects refer to references of variables that are created inside the function - even though I pass them to the resulting struct.
I'd like help to solve this problem and have a generally better grasp on how to write target-agnostic modules as I'm going to need a bunch of them
Here's the struct - commented out previous attempts:
pub type UsbDriver<'a> = Driver<'a, peripherals::USBD, HardwareVbusDetect>;

pub struct UsbHid<'a> {
	// hid: HidReaderWriter<'a, T, 1, 8>,
	// reader: HidReader<'a, T, 1>,
	// writer: Box<HidWriter<'a, UsbDriver<'a>, 8>>,
	// usb: Box<UsbDevice<'a, UsbDriver<'a>>>,
	// writer: &'a HidWriter<'a, dyn Instance, 8>,
	// usb: &'a UsbDevice<'a, dyn Instance>,
	writer: HidWriter<'a, UsbDriver<'a>, 8>,
	usb: UsbDevice<'a, UsbDriver<'a>>,
	remote_wakeup: Signal<CriticalSectionRawMutex, bool>,
	// state: Box<State<'a>>,
}

and here's the setup code:
impl<'a> UsbHid<'a> {
	fn setup() -> Self
	where
		Self: Sized,
	{
		let p = embassy_nrf::init(Default::default());
		let driver = Driver::new(p.USBD, Irqs, HardwareVbusDetect::new(Irqs));

		let mut usb_config = Config::new(0xc0de, 0xcafe);
		usb_config.manufacturer = Some("DZervas");
		usb_config.product = Some("RustRover");
		usb_config.serial_number = Some(env!("CARGO_PKG_VERSION"));
		usb_config.max_power = 100;
		usb_config.max_packet_size_0 = 64;
		usb_config.supports_remote_wakeup = true;

		// let mut device_descriptor = [0; 256];
		// let mut config_descriptor = [0; 256];
		// let mut bos_descriptor = [0; 256];
		// let mut msos_descriptor = [0; 256];
		// let mut control_buf = [0; 64];
		let request_handler = MyRequestHandler {};
		// let mut device_handler = MyDeviceHandler::new();

		let mut builder = Builder::new(
			driver,
			usb_config,
			// &mut device_descriptor,
			// &mut config_descriptor,
			// &mut bos_descriptor,
			// &mut msos_descriptor,
			// &mut control_buf,

			&mut make_static!([0; 256])[..],
			&mut make_static!([0; 256])[..],
			&mut make_static!([0; 256])[..],
			&mut make_static!([0; 128])[..],
			&mut make_static!([0; 128])[..],
		);

		// builder.handler(&mut device_handler);

		// Create classes on the builder.
		let hid_config = embassy_usb::class::hid::Config {
			report_descriptor: KeyboardReport::desc(),
			request_handler: Some(&request_handler),
			// request_handler: None,
			poll_ms: 60,
			max_packet_size: 64,
		};

		let mut state = State::new();
		// let hid = HidReaderWriter::<_, 1, 8>::new(&mut builder, &mut state, hid_config);
		// let reader = HidReader::<_, 1>::new(&mut builder, &mut state, hid_config);
		let writer = HidWriter::<_, 8>::new(&mut builder, &mut state, hid_config);

		// Build the builder.
		let usb = builder.build();

		let remote_wakeup: Signal<CriticalSectionRawMutex, bool> = Signal::new();

		// Run the USB device.
		// let usb_fut = async {
		// 	loop {
		// 		usb.run_until_suspend().await;
		// 		match select(usb.wait_resume(), remote_wakeup.wait()).await {
		// 			Either::First(_) => (),
		// 			Either::Second(_) => unwrap!(usb.remote_wakeup().await),
		// 		}
		// 	}
		// };

		// let (reader, mut writer) = hid.split();

		// let usb_fut = usb.run();

		// self.reader = reader;
		// self.writer = writer;

		Self {
			writer,
			usb,
			remote_wakeup,
			// state
		}
	}
}

I got it! For anyone else:

the name of the game is tasks and channels. There are many types of them
the construction of structs should most probably done in a synced manner
task objects should most probably made static. the make_static macro helps (A TON!)
for usb stuff, construct all your class-objects before build()


Please confirm these before moving forward

[X] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
[X] I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue
Installation issue.
Brief description of your issue
Cant upgrade .net sdk 6.0 through winget
Steps to reproduce

Actual behavior
It cant find package even though its installed on computer
Expected behavior
To upgrade package
Environment
Windows Package Manager v1.3.2091
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22621.608
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.18.2091.0

Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Screenshots and Logs
WinGet-2022-10-03-04-39-51.120.log

What happens when you run winget list '.NET SDK'

The issue is happening because it is detecting that you have two versions installed, and thinks the older version needs to be upgraded, but then upgrade fails because you already have the newer version. Removing the older version should fix the issue

Removing the older version should fix the issue

Just a note that this is a mitigation, not a fix. Many .NET shops have their projects pinned to a specific minor/patch version of the SDK, so you need to have multiple installed at once for the compiler not to complain at you about global.json.

Thank you for taking the time to report this issue. In the amount of time the issue has been open, there have been several updates to the WinGet CLI which may have helped mitigate some of these concerns. I encourage you to try out the latest pre-release of the CLI and see if your problem still persists.
There is a new experimental feature for Side-By-Side installs which may help with this case. As there are many similar issues for side by side open on the CLI repo, I'll be closing this one to keep things clean.
Close with reason: Tracked at winget-cli; Experimental feature available


Cannot create a Xata branch without a remote

Describe the bug
xata branches create dev, in a git repo at a specific branch (main in this case) fails to infer the base branch and complains about "No git remotes found". Given that HEAD is already main here, a remote should not be required.

To Reproduce
Run xata branches create dev in a repo with no remotes.
Expected behavior
A branch with the specified name is created in git and in Xata.
Software version
@xata.io/cli/0.6.0 darwin-arm64 node-v16.15.1

A remote is needed in git to calculate the default branch. Here's an article that explains how to get the value.
Note: when opening bugs, could you remove the template instructions? It's hard to know what's your text and what's the template text.

A remote is needed in git to calculate the default branch. Here's an article that explains how to get the value.

Why do we base a new branch on the default branch instead of the current branch? git checkout -b new is automatically based on whatever is currently checked out instead of the default branch. I'd expect Xata branches to work the same.

Why do we base a new branch on the default branch instead of the current branch? git checkout -b new is automatically based on whatever is currently checked out instead of the default branch. I'd expect Xata branches to work the same.

Git is more flexible because there are many types of software you can do with it. For example you can work on different versions of the same software and release them at the same time (1.x, 2.x,..., being some of them in maintenance).
However in our use case you typically will only have one production branch and db branches are much less often used than git branches. So, the use case of branching off an existing branch that is not main, in my opinion will be a lot less common than the case of branching off main.
But we can discuss this with Tudor.

Great idea not pinging him because vacation.gif 🙌

I think that we don't need to provide all the flexibility of git, however needing A <- B <- C doesn't seem that unlikely specially if you use git.

I think we should allow changing base branch when creating a new one.

We allow that with the --from flag. I think the discussion is more about which one is the default.

Yeah, my only suggestion is to follow git 1:1 since that's what developers are more familiar with. :)

Sorry for the delay here, if I understand correctly, the options are:

we default to fork from main if no --form is specified
we use the resolve endpoint to figure out if there is a Xata branch linked to the current git branch, and if there is, we use it as the default to fork from. If it isn't, we still use main as the default.

Would option 2 be difficult from an implementation PoV? If not, I think I like it, because if you have just created the git feature branch and do xata branches create, it still defaults to main. But if you are in a feature branch and that is already created , then it's more likely that you want to branch from it.
Btw, are we automatically linking the git branch with the xata branch if you do xata branches create while in a git branch?

Will be revamped as part of #p-worflow


[TODO]

list the features
what are we doing
Add laws 2 and 3

we added law 2 one more to do

done just adding finishing steps


Automatically create unique cache directories

Tell us more about this new feature.
We have an application that benefits a lot from mountpoint caching. To support mounting multiple S3 buckets on the same host, we have to create independent cache directories on the host to avoid conflicts among multiple mountpoint processes. This has become a big chore to maintain the cache directories on our EC2 instances.
Currently, on the mount-s3 command-line, we pass in a top-level folder as the "parent" path for caching. Then, mountpoint creates a "mountpoint-cache" subfolder. Instead of a static subfolder name, is it possible to create a unique one? This would let me specify just the parent path for caching on all mountpoint instances on the same host, and have mountpoint take care of creating a unique subfolder to avoid conflict.
This would also make it easier to deploy to Kubernetes using the CSI driver. Multiple Persistent Volumes (PVs) can specify the same parent cache directory, and independent subfolders are created per mount.

Thanks for opening this issue @alan113696. We'll discuss this internally and assign it a priority relative to other issues we have open and report back on next steps.

This would be a fantastic feature to have. Currently there's tight coupling between the mountpoint-s3-csi-driver and any cache-enabled PVs that might be created with it, where for each $CACHE_DIR a process must be run somewhere (currently by a human, outside of source control) to create the cache directory. It's possible to automate this to an extent, but in the end you're sharing magic strings across two otherwise orthogonal contexts.
It would be much cleaner to only have to know (and require the existence of) the parent directory for the cache and have the mountpoint-s3 software (or perhaps the CSI driver?) automatically create a PV-unique cache directory for you beneat it.


Monad.ipynb

Hey, could you please explain what this specific snippet of code does? in particular, I am not able to understand the use of the limits 10, 54, and 6.

That particular snippet of code is to clean the generated output, so for example if in a given window of 10 frames less than 6 have an increase, then most likely those are false alarms. The first and third for loops are basically the same, you can remove one of them.

Thanks for the clarification


Skin the "Sign In" Modal Window

Currently the SIGNIn page looks like this:

Would be great If we can achieve this:

On some point we need a dropdown anyway (ledger / trezor / ...)

should i also include the tabs and the stepper steps? not sure for what they are needed for on logging in
what are the dimensions of the modal? i would guess minWidth:50vw and minHeight: 50vh

As a user can have multiple eos accounts I guess he can have multiple eosdac member accounts, so in my opinion I would show the Tabs.
What happens if the InternetConnection is interrupted, propably there is an error message "could not connect to Endpoint" or something like this, so I would show the API Endpoint "Step" in Status "green".
Yes an additional "close" Button makes sense too.
On Desktop I would set the max height to 610px and max width to 900px. Do you adjust the size  by viewport?
https://alligator.io/vuejs/vue-media-queries/

so you mean the tabs should also act as a stepper that gets activated when the user logs in and isnt a member?
i use the default quasar grid system with breakpoints like bootstrap.
https://quasar-framework.org/components/flex-css.html
The modal is just as big as the content that they hold. i didnt give them any size but now i can give them the ones you just gave me

? No Tabs should never act as a stepper, But I think the "RegisterAsaMember" Tab should always be available.

Looks very good nano!!! Only 3 little things. On the Sign in Tab (Stepper)  the "Registration Step" should not be visible. Can the Close button float right?

For testing I chose Register as A Member Tab and chose the same identity then this modal came up:

Can we give the Status Message the same Padding as the other forms? And Mybe the wording in this case. "You are already registered as a eosDAC Member".
In my opinion the Login/Register Process looks super slick now!!


Add a branch verification  on startup

Is your feature request related to a problem? Please describe.
Currently, there can be a confusion between using main branch or debian-main branch, as using main branch for configuring Seapath Debian and inversely.
Describe the solution you'd like
A task in the beginning of configuration to make sure the correct branch is used with the correct Seapath flavor.
For example, with uname -a on Seapath Debian, we can detect we are using Seapath Debian:
Linux machine1 6.5.0-0.deb12.1-rt-amd64 #1 SMP PREEMPT_RT Debian 6.5.3-1~bpo12+1 (2023-10-08) x86_64 GNU/Linux
Describe alternatives you've considered
A  subsection has been added in README file: https://github.com/seapath/ansible/pull/432 and https://github.com/seapath/ansible/pull/433

For main branch, fixed with #446


udemy dsa course added

best dsa couse

@Rahul-chaurasiya Multiple merges to the same repo will be considered spam by hacktoberfest team so I am not merging this but if this is a genuine pull request tell me ill merge it


ActiveMQ Integration

Is there a plan for a ActiveMQ target?
There is an commit on https://github.com/jkowalski/NLog/pull/20 which could be the solution. Is an integration planned?

It think it should be added to the NLog Contrib repository
Don't know if we can easily move the PR

I'll try to move the code to the Contrib repository

A pull request for the ActiveMQ target have been created in the contrib repository.

link: https://github.com/NLog/NLog-Contrib/pull/19

moved to https://github.com/NLog/NLog.Contrib.ActiveMQ
closing out


ceph-osd: Remove jinja2 delimiters from when

Modern versions of Ansible throw a warning when jinja2 delimiters
are used in when: keys:
[WARNING]: when statements should not include jinja2 templating delimiters
such as {{ }} or {% %}. Found: ceph_release_num.{{ ceph_release }} >=
ceph_release_num.luminous

This patch sets a fact for current_ceph_release_num in the
ceph-osd role that can be re-used throughout the role.

Closing in favor of https://github.com/ceph/ceph-ansible/pull/2043.


docs: Add heading, turn others into sub-headings in README.md

Is capitalization as "Emma" ok/desired in the title? Or rather "emma"?
Should the other headings not be sub-headings?

I just use emma as a normal word, i.e., capitalize it where it makes sense.


PUB-903 - update to new Key Vault

JIRA link (if applicable)
PUB-903
Change description
update to use the new Key Vault to store details
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ X ] No

Removed as removed the server in another PR


[Archlinux plugin] name masking

For example yaourt -Syua and yay -Syu have the same alias yaupg.
Possible fix: prefix all yay alias by yay instead of ya.

alias masking is intentional, related to #6867.


Error create components in js file

Hi,
php artisan ng:component create_post_form
in create_post_form.component.js error app.components
angular.module('app.components').directive('createPostForm', createPostFormComponent);
replace in app.controllers
angular.module('app.controllers').directive('createPostForm', createPostFormComponent);
Thanks

Hi @franklupo
Thanks for opening an issue
Unfortunately I can't understand what the issue is..
Can you please provide more information?

The generated js files has a 'app.components' error.
I replece manual in 'app.controllers'

@franklupo so you didn't have an app.components in your main.js file?
I suspect this is the switch to the newer version of laravel-generators..
You can downgrade it in your composer.json if you'd like - just like in #161

No, in main.js the content is

(function(){
"use strict";
angular.module('app',
[
'app.controllers',
'app.filters',
'app.services',
'app.directives',
'app.routes',
'app.config',
'partialsModule'
]);
angular.module('app.routes', []);
angular.module('app.controllers', ['ui.router', 'ngMaterial', 'ngStorage', 'restangular', 'angular-loading-bar']);
angular.module('app.filters', []);
angular.module('app.services', []);
angular.module('app.directives', []);
angular.module('app.config', []);
})();

oh okay, thanks a lot for reporting it
This has been fixed as of 3.1 (unstable)


Upgrade to core13.4

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 89.098%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
3032

Relevant Lines:
3403

💛  - Coveralls


Insecure DP and normal distribution backed by Box-Muller transform

This builds on top of #702 and contains mostly cosmetic changes, polishing and more tests. The core idea remains the same - use Box-Muller transform to implement normal distribution (alternatively num_distr/statsrs could've been used) and build a simple DP application mechanism to apply noise in the clear.
Note that this mechanism is general, i.e. without any specifics related to how aggregates are represented. It does allow negative values after noise is applied. The idea is that the further transformation can be done outside of DP.

A big ticket item: we should be sampling from a discrete distribution, not a (basically) continuous one. That is how any MPC will report results. That means rounding.

If we want to have noise from a discrete Gaussian or discrete Laplace, this paper looks promising.  It has also been implemented in python which could make for a helpful reference implementation.

The implementation of the function looks somewhat involved, at least if we're looking to implement in MPC.  "requires a constant number of operations in expectation" is a term they use in a couple of places.  Their Bernoulli function has a cap on the number of recursions (not iterations, sadly, which will complicate things); but their discrete Laplace implementation does not: "the number N of iterations of the outer loop needed to output a value Z is geometrically distributed".  Note that we operate obliviously, so we have to perform all computations.  That means compromise if we are going to implement that.  It's probably not a big deal, but it introduces error that would need analysis.

Of course, if you want the simple (non-MPC) implementation, the algorithms are very simple to execute.

For the short term we decided to get to discrete using a rounded Gaussian.  Unless epsilon is very small, the variance of the noise between a rounded Gaussian and continuous Gaussian is not much.  See Figure 2 of the above paper and the following computed values:

merging with a thought in mind that DiscreteDp may need to operate on integers. I guess I will know better once we have code that applies this DP to aggregates


Add API to track R200 camera movement in 3D space with 6 DOF

Required Info

Camera Model
R200

Firmware Version
ToT

Operating System & Version
Ubuntu 16.04

Kernel Version (Linux Only)
v4.4

Build System
Makefile

Intel R200 introduction says

The R200 tracks the camera movement in 3D space with 6 DOF (degrees of freedom). 3 Degrees from the Front/Back/Up/Down/Left/Right and 3 degrees from Yaw/Pitch/Roll movements.

However, librealsense doesn't provide the API.

Hi @ds-hwang as noted in the Readme of librealsense, this project is not the RealSense SDK and doesn't contain the middleware stack (scene reconstruction, 6dof, background segmentation, etc). It's lower level and meant to be used directly be algorithms developers. Hope that helps!

Ah, thx for explaining. I thought the camera has IMU sensor, rather than guessing 6dof from depth data. I agree.

I think all of the devices with integrated R200 also have a built in IMU so
it would be redundant to put one in the camera module.

@teknotus indeed, at least, R200 has IMU sensor, according to intel article
As the 6dof data comes from IMU sensor, not estimation, it makes sense to expose the data via API. I guess ROS community really wants the IMU data.

@teknotus @ds-hwang Bad documentation.
The R200 does not have any IMU, nor the F200, nor the SR300.

@ddiakopoulos ok, thx for verifying. I saw several intel realsense docs mentioning IMU sensor. Someone continuously says not true..

hi all, can any one suggest me any person tracking algorithm for ros using R200 camera
thanks


[Bug] - Exception when trying to change theme in wide view desktop mode

I noticed an exception when trying to change theme. This exception is present only when application is running on desktop and in "Wide view" when full HamburgerMenu is visible (icons with contents). When the menu is collapsed everything is fine.

Can you be more specific as to the location of the above code? Project? Sample?
My guess is it's a ...\.Services.SettingsServices.cs file but which one and used with which project?

Hi, it`s a hamburger template project and SettingsServices.cs.

@marcinmarkiewicz -- I cannot repro this error. Are you sure that this is the original code? My suspicion is that you may have changed something in the Styles\Custom.xaml file.
I checked with the latest unmodified  Hamburger project and in wide mode as you described and no problem. Compare with the original source code and see if any modifications by you contributed to this error. Double check the the Styles\Custom.xaml file.

I checked Cusom.xaml - it`s ok. I notticed that this problem exists when I have my own brushes defined in my HamburgerMenu - directly in Shell.xaml, not in Custom.xaml. It has a sense now. RefreshStyles method of SettingsService can not refresh brushes defined my way. Thanks @dg2k


SHA Restriction not working

When I restrict the API key from Google Cloud to an Android app with my current SHA key, request are not working.

My PR #89 has been approved and merged where you can specify your own headers when making the Google API calls.
Once it's updated on pub.dev (or you can use the master branch on GitHub straightaway), you can use it with the plugin google_api_headers to get the required headers and you should be able to use app restricted API keys. See below for an example:
import "package:google_maps_webservice/geocoding.dart";
import 'package:google_api_headers/google_api_headers.dart';

final headers = await GoogleApiHeaders().getHeaders();
final geocoding = new GoogleMapsGeocoding(apiKey: "<API_KEY>", apiHeaders: headers);

Hope this solves your issue and Happy New Year!

Available in last version :) (0.0.19)


Replace Coveralls by Code Climate as code quality measuring tool

Hello, I hope it is not a problem to open an issue out of the blue like this.
Lately, @lipemorais was showing me this project and, as a way to try to start contributing to it, I thought it would be interesting to replace Coveralls by another quality measuring tool. My reasons behind such suggestion are in the fact that the Coveralls UI is very confusing, I can't quickly get a picture of what is actually going on in the project when looking at its dashboard. Besides, it is showing a quite imprecise metric at this moment, since it's also considering third-party libraries in its analysis, lowering the metrics to only 25%.
I believe that CodeClimate would be a better option to solve this problem. I've forked this project and configured its forked copy to be analyzed by CodeClimate. Below, it's possible to see a result of the first analysis:

Besides the code styling, it's also possible to harvest some metrics about testing coverage:

I've also noticed that Jarbas makes use of both Coveralls and CodeClimate. Maybe, CodeClimate could be configured to be used as a test coverage reporter, replacing Coveralls there as well.
I would like to apologize in advance if this is not the right way to open a new issue.

Hi @othman853,
Many thanks for you suggestion. Unfortunately I tend to disagree.

Coveralls UI is very confusing

This is a quite subjective matter — I use it a lot so I feel familiar in their dashboard.

it is showing a quite imprecise metric at this moment, since it's also considering third-party libraries

This is not a Coveralls problem, it's lack of configuration. We added it only 6 days ago and so we haven't fine tuned it yet. If we configure it in a similar way we did in Jarbas, this doesn't happen.
In spite of that Code Climate doesn't offer an analysis as complete as Landscape.io in terms of style, code smell and errors — specially when using it with veryhigh strictness: it help us with docstrings (important for #23 as I noted elsewhere), unused imports, thing accessed before creation, line breaks etc.
Anyway. I'm really glad you pointed is toward to some flaws in the configuration of our CI services, but I do not agree that changing would be better: after all the same settings needed now for Coveralls will also be needed with for Code Climate.
I'll let this issue open for debate for a while, but feel free to open an issue or PR fine tuning or Coveralls ; )

Hello! Thanks for the answer! I believe that a Coveralls tuning would end up being more appropriate then. I'll check how it can be fixed and open a PR. Sounds good?
Do you believe that a new issue should be open or we could open a PR to solve this current issue?
Once again, thank you very much! :)

I'll check how it can be fixed and open a PR. Sounds good?

That's awesome ; )

Do you believe that a new issue should be open or we could open a PR to solve this current issue?

If you don't mind I can edit the title of this one — I think keeping the new issue togather with this discussion could be helpful. May I?

Absolutely! Thank you for all the help!


tag a new version in METADATA.jl ?

Changing symbol() to Symbol() last October 20 was sufficient to keep Julia 0.6 happy, but no METADATA.jl updates have been tagged to reflect the change.

https://github.com/JuliaLang/METADATA.jl/pull/9393


fix(clerk-js): Avoid throwing error for missing an active organization when no user is signed in

Description
Avoid throwing error for missing an active organization when no user is signed in
fixes #3236

Checklist

[ ] npm test runs as expected.
[ ] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

!snapshot

Hey @panteliselef - the snapshot version command generated the following package versions:

Package
Version

@clerk/chrome-extension
1.0.3-snapshot.vfc5e305

@clerk/clerk-js
5.2.0-snapshot.vfc5e305

@clerk/clerk-expo
1.0.3-snapshot.vfc5e305

@clerk/fastify
1.0.3-snapshot.vfc5e305

gatsby-plugin-clerk
5.0.0-beta.45

@clerk/localizations
2.3.0-snapshot.vfc5e305

@clerk/nextjs
5.0.4-snapshot.vfc5e305

@clerk/clerk-react
5.0.2-snapshot.vfc5e305

@clerk/remix
4.0.3-snapshot.vfc5e305

@clerk/testing
1.0.2-snapshot.vfc5e305

@clerk/themes
2.1.1-snapshot.vfc5e305

@clerk/types
4.2.0-snapshot.vfc5e305

Tip: Use the snippet copy button below to quickly install the required packages.
@clerk/chrome-extension
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-js
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-expo
npm i<EMAIL_ADDRESS>--save-exact

@clerk/fastify
npm i<EMAIL_ADDRESS>--save-exact

gatsby-plugin-clerk
npm i<EMAIL_ADDRESS>--save-exact

@clerk/localizations
npm i<EMAIL_ADDRESS>--save-exact

@clerk/nextjs
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-react
npm i<EMAIL_ADDRESS>--save-exact

@clerk/remix
npm i<EMAIL_ADDRESS>--save-exact

@clerk/testing
npm i<EMAIL_ADDRESS>--save-exact

@clerk/themes
npm i<EMAIL_ADDRESS>--save-exact

@clerk/types
npm i<EMAIL_ADDRESS>--save-exact


Added Cross mark and Clears the console

Messages in the console are cleared and an indication of closing is added where user can  click to delete the note.

You didn't added the hacktoberfest label to it☹

I want to work on this. Please assign me this.


Acces to entities

Hello!
Thank you for a very useful integration.
Is it possible to access enteties?
For example
Changing target temperature from an automation script or using target temperature as a sensor.

I am not author. But I'll try answer this. Target temperature is a number you define yourself. It doesn't involve a sensor. This uses pyfujitsu library, which I recall doesn't have api for sensors. But, for automation, you could use another external sensor and use node red to define some logic yourself.

Thanx for the reply:
Here is my configuration and it is working fine:
climate:
  - platform: fglair_heatpump_controller
    username: ******************
    password: ***********
    region: 'eu'
    tokenpath: 'token.txt'

Available attributes for the platform:
hvac_modes:
  - heat
  - cool
  - auto
  - dry
  - fan_only
  - 'off'
min_temp: 16
max_temp: 30
target_temp_step: 1
fan_modes:
  - auto
  - low
  - medium
  - high
  - diffuse
swing_modes:
  - 'off'
  - 'on'
  - vertical
  - horizontal
current_temperature: 22.8
temperature: 22
fan_mode: high
swing_mode: 'off'
icon: mdi:air-conditioner
friendly_name: FujiElectric
supported_features: 41

What i want is to create a sensor (or alias) for some of the attributes for example current_temperature and use it directly in graphs, automations and so one ...


Get-AzureADDevice -searchstring should validatenotnullorempty

If I am passing a variable to the -searchstring parameter, and the variable happens to be null, then the cmdlet should error instead of returning everything in the tenant. For example, if I have some code like this:
$intunedevice = get-intunemanageddevice -filter "devicename eq '$devicename'"
get-azureaddevice -searchstring $intunedevice.devicename | remove-azureaddevice

The above will erase all the devices (along with their bitlocker recovery keys and other crucial info) from the tenant if $intunedevice happens to be null. Very dangerous! Also the fact that remove-azureaddevice removes everything without asking for confirmation is also dangerous. It seems like to me if I'm passing nulls around, that shouldn't result in the erasure of all the devices in your tenant.

Hi @einbahn
Thank you for your issue submission. Unfortunately, this appears to be a problem with the cmdlt and a support issue. Issues in this repo are for documentation issues. You can try one of the following links for additional help.
Microsoft Support: https://support.microsoft.com/
Azure AD forums: https://social.technet.microsoft.com/Forums/en-US/home?forum=windowsazureaditpro
Stackoverflow: https://stackoverflow.com/
Bill


Update inpad to 0.1.0

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

The homepage doesn't currently work, but the project's Github page says it is currently undergoing "revival", so I assume the homepage will be fixed in the near future.


Fixes user-defined sass includePaths from being overwritten

Fixes https://github.com/fuse-box/fuse-box/issues/278

Thanks, man, now i need to check what's wrong with tests ;-)


Primers contributing to Clean.Tot.cons

We have examples where there is an amplicon with two right-hand primers. Neither primer is excluded at the primer/amplicon identification stage, and both are provided to cylon.
Observed behaviour: in all_stats.tsv, at the "inner" (or left most, whatever you want to call it) right-hand primer position, the reads from the "inner primer" are contributing to Clean.Tot.cons.
Expected behaviour: those reads do not contribute to Clean.Tot.cons.
An example is #99 , in amplicon SARS-CoV-2_76.
This may be confounded by the adjacent amplicon 77 being dropped, I don't know. The behaviour below may also be happening when the adjacent amplicon is not dropped - this needs checking.
For the sample in #99 this is what happens:

no primers for amplicon SARS-CoV-2_76 are excluded (a separate issue to this one)
all the reads arise from the leftmost primer SARS-CoV-2_76_RIGHT (coords 23029-23057).
therefore the only read coverage at 23029-23057 is from reads ending with primer SARS-CoV-2_76_RIGHT . The primer is not (as far as the code knows) at the end of the amplicon - the decision earlier was to also keep SARS-CoV-2_76_RIGHT_alt1 (coords 23121-23141).
all_stats.tsv reports non-zero Clean.Tot.cons values at 23029-23057 - they are fairly close to the values in RawDepth.

The primer id stage before cylon is different than what is used for masking the consensus. When an adjacent amplicon is dropped the overhanging primer bases will be considered, so we would expect those reads to contribute to Clean.Tot.cons.
Are there examples where this happens when the adjacent amplicon is not dropped?

This issue has nothing to do with cylon. It's about when primer parts of reads are used to contirbute to good or bad coverage for masking, and in the stats.
We have sequence chunks like this in the amplicon from left to right:
L = left chunk (I don't care about left primers here)
P1 = primer1.
Q = sequence between primer1 and primer2
P2 = primer2.
and the subsequent amplicon is dropped.
I would expect that the P1 part of the reads that were made during PCR from P1 do not count towards the good depth, since there should be reads that arose from P2 during PCR. Those reads from P2 should also include the P1 sequence and can be relied upon for their P1 sequence.

I'm sorry I don't quite understand. How does this differ from what we're doing right now?

Current behaviour:
Reads originating from primer P1 contribute to good coverage in the P1 region of the consensus.
Reads originating from primer P2 contribute to good coverage in the P1 region of the consensus consensus.
Expected behaviour:
Reads originating from primer P1 do not contribute to coverage in the P1 region of the consensus.
Reads originating from primer P2 contribute to good coverage in the P1 region of the consensus consensus.

this simulation is the example @jeff-k

In #99's example we are adjacent to a missing amplicon. This means that primer bases will be considered no matter what. I'm not sure how we can determine that the current behaviour is deviating from the expected behaviour.


Resolve primitive data types for the path parameter values in low-resource-service binding option --without-data-binding

Description:
Parent issue: https://github.com/wso2-enterprise/internal-support-ballerina/issues/528

PR: https://github.com/ballerina-platform/openapi-tools/pull/1581


Facilitate parallel build directories for meson-enabled commands?

While making scikit-image compatible with NumPy 2 I often had to switch back and forth between 2 environments with NumPy 1.x and 2 installed. I had to use spin build --clean each time I switched which even with ccache available took a bit of time. From the initial introduction of meson and it "breaking" inplace editable installs I remember that one of the arguments was that meson would allow having multiple build directories in parallel. Perhaps I missed an obvious way to achieve this with existing capabilities of spin?
If not and going forward, can we facilitate this workflow a bit more in spin? For my scenario I imagined something like a -t, --target TARGET switch. If not specified the default setup with build/skimage and build-install is used. With -t np2 meson-enabled spin commands would use build/np2/skimage and maybe build-install/np2?
UI and paths are of course up for discussion but I think it get's the workflow across that I'd like to have. It would enable faster switching and debugging with multiple environments that require recompilation.

This would require either storing some state ("last used build dir"), or specifying the builddir on each run. If you think the latter is acceptable, I can add it.

or specifying the builddir on each run

SciPy's dev.py does it this way, with a --build-dir flag that comes before the subcommand. It's quite usable when combined with a shell alias. E.g.:
$ alias dev="python dev.py --build-dir build"
$ alias dev-clang="python dev.py --build-dir build-clang"
$ # run the same tests for the two different builds:
$ dev test -s linalg
$ dev-clang test -s linalg

I'd suggest doing it the same way for spin, including documenting the alias trick.

Yeah, even a simple toggle would help with the workflow so it's not really worth it for spin to worry about saving state suddenly. There's also the option to use an environment variable in addition. But probably not worth it since the alias-approach also allows to configure the build dir per shell session or even longer.

We're releasing 0.10 today, aiming to get this into 0.11.

I'd suggest doing it the same way for spin, including documenting the alias

Thanks, Ralf, I've included this tip in the documentation in #221


Use "v" prefix for tag names

All releases (tags) in this repository use semantic versioning consisting from 3 numbers, e.g. 0.10.1.
However, Golang standards require the v prefix in the tag name, e.g. v0.10.1.
As a consequence, currently, it is not possible to reference a release via version in this repository from another go module. Only pseudo-versions allowed, so we always end up in something like v0.0.0-20220622161720-2a6007e17200.
It would be great to have this fixed, so we can use
github.com/openshift-pipelines/pipelines-as-code v0.10.1

instead of
github.com/openshift-pipelines/pipelines-as-code v0.0.0-20220622161720-2a6007e17200

yeah we talked a bit about it internally, and we acknowledge that is some tech debut we need to clean up, that may look like a simple change but there is a lot of plumbing we need to fix to get there..

Thank you for the quick fix!


No description is visible for additional nutrients in edit mode

Describe the bug
Additional nutrients don't show any description as soon as a value is entered, the description of common nutrients is visible as expected. This happens with dark theme as well as with light theme.
To reproduce
Steps to reproduce the behavior:

Go to any product with some additional nutrients (e.g.<PHONE_NUMBER>341)
Click on 'Edit'
Swipe to last page with nutrients
Scroll down and compare common and additional nutrients

Expected behavior
Descriptions should be visible in the editbox as long as no value was entered and be visible above the editbox when a value is given.
Screenshots

OS: LineageOS 17.1
Version 3.6.8 (F-Droid)

@ForGorNorPor do you have the specific nutrient which caused this ?

This happens for all nutrients which have to be added manually. I could not reproduce it in the dev version two months ago.


404 at: /engine/installation/linux/repo_files/centos/docker.repo/

URL: /engine/installation/linux/repo_files/centos/docker.repo/
Using old documentation to install Docker Engine from 1.13 repo fails with 404.
Related to https://github.com/docker/docker.github.io/issues/2081

Hi @daniel-ng  , sorry you are running into this 404. The installation instructions have changed in the master docs and these files are no longer used. In fact, they are only used for Docker 1.13.0 and Docker 1.13.1. If you want to install 1.13, you can use the archived installation instructions at https://docs.docker.com/v1.13/engine/installation/linux/rhel/. The URL to the docker.repo in that file is currently incorrect too, because #2133 has not yet been published (expected it within half an hour). In the meantime, the correct URL to the docker.repo is:
https://docs.docker.com/v1.13/engine/installation/linux/repo_files/centos/docker.repo

I'm going to go ahead and close this because the fix has already been pushed.


(REPLATS-425) Update conftest version

Updating conftest to 0.27.0 to get regex support.

Did you mean to make this against our fork?

Did you mean to make this against our fork? This change was made against the original, so can close this PR.

This was my initial step when I found I needed to update conftest.  I later ended up just re-writing the tests to avoid the need for the updated version.


ConnectivityChecker (connectivityManager?.activeNetworkInfo is deprecated)

see:
https://developer.android.com/reference/android/net/ConnectivityManager.html#getActiveNetworkInfo()

Please review the PR


Update the handling of joins in DFA to use correct tuple indexes

This also adds a couple of tests with claims on components of a tuple.

/gcbrun

/gcbrun

/gcbrun


Need detailed explanations on executing file path scripts

The error on the "hosted" agent is: ##[warning]Executable bit is not set on target script, sourcing instead of executing. More info at https://github.com/Microsoft/azure-pipelines-tasks/blob/master/docs/bashnote.md
However, that link is not very informative, and telling people to leave well-alone if they don't understand, is not really a satisfactory answer.
Even when the "execution bit" is set I still get the warning.
Please provide detailed steps on how to set the execution bit so your agent doesn't raise the warning.
The following doesn't work:
git config core.filemode false
chmod -x <file>
git update-index --chmod=+x <file>
chmod +x <file>

#check
git ls-files -s

I've confirmed in the _work directory that the file has the right permissions.
(Windows agent with git bash installed)

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

ID: fb215324-b1a0-93b5-5022-4bcc7da93bb7
Version Independent ID: 9eb2977b-ac34-9d53-670e-04fa027bc8e4
Content: Azure PowerShell task - Azure Pipelines
Content Source: docs/pipelines/tasks/deploy/azure-powershell.md
Product: devops
Technology: devops-cicd-tasks
GitHub Login: @RoopeshNair
Microsoft Alias: ronai

Wrong page.


Get-AADGroupmember doesn't work on groups that have a source of Windows Server AD

If you have a group that is synced from on prem and has a source attribute of "Windows Server AD" getting the membership doesn't return as expected.
@odata.context, @odata.nextLink, and value are returned as custom powershell objects rather than arrays.
@odata.context https://graph.microsoft.com/v1.0/$metadata#directoryObjects
@odata.nextLink contains https://graph.microsoft.com/v1.0/groups/groupId I am trying to query/members//$ref?$skiptoken=tokenstuff
value contains the urls to all the members, but not in a parsable array
{@{@odata.id=https://graph.microsoft.com/v2/unkown id formated as xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/directoryObjects/ObjectID of a device in the group/Microsoft.DirectoryServices.Device;groupId=groupId I am trying to query; memberODataType=microsoft.graph.directoryObject}, @{@odata.id=https://graph.microsoft.com/v2/unkown id formated as xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/directoryObjects/ObjectID of a device in the group/Microsoft.DirectoryServices.Device;groupId=groupId I am trying to query; memberODataType=microsoft.graph.directoryObject},
Removed all the object ids and token info.

Paging docs helped resolve issue. Having a -All parameter would make life much easier https://learn.microsoft.com/en-us/graph/paging


[2773] Add interstitial step to confirm course for apply draft course…

Context

https://trello.com/c/I42FIUkY/2773-m-add-a-confirm-this-is-still-the-course-page

Changes proposed in this pull request
Previously, we would confirm the course when the user clicked continue on the apply confirm course page. This prevented the user from actually changing any of the values as they weren't persisted so would appear empty in the edit form if they went to change.
This PR introduces an interstitial step before hand so we can copy over all of the course details which allows them to change any of these values if they choose to do so on the confirm page.

Guidance to review

Go to trainees index
Filter by apply
Choose a trainee and click course details
Have a play

 [M] Add a ‘confirm this is still the course page’

A couple issues with this:

The grid system of the page is broken - I think it's missing a grid column - govuk-grid-column-two-thirds-from-desktop
Please can it have the error message Select yes if this is the correct course

A couple issues with this:

The grid system of the page is broken - I think it's missing a grid column - govuk-grid-column-two-thirds-from-desktop
Please can it have the error message Select yes if this is the correct course

Fixed


Customizable Keybindings for Flutter Console Interactivity

Use case
When running flutter run in an interactive console, pressing certain keys can trigger actions that may be unintentionally invoked during regular development work. For example, in my case, pressing J accidentally results in the creation of jank metrics. While these metrics are useful, they can interfere with the workflow, especially when working in an environment like Vim where the terminal is frequently focused.
Currently, there's no way to customize or disable specific keybindings without turning off interactivity altogether, which would also disable essential features like r for hot reload and R for hot restart.
Proposal

Provide a way for developers to either disable or customize specific keybindings (e.g., J for jank metrics) within the Flutter interactive console.
Ensure that essential keybindings like r (hot reload) and R (hot restart) remain intact while allowing specific actions to be muted or reassigned.

This can be achieved either by adding an optional configuration file or environment variable where developers can specify which keys they want to disable or remap.

Increased flexibility and customization for developers using the Flutter CLI.
Prevention of accidental key presses that can disrupt the development workflow.
Allow developers to maintain essential interactivity features while avoiding unwanted commands.

Labeling as a proposal to customize the keybindings for the flutter interactive console that is shown when a flutter app is run using fluttter run
Following are the commands supported as of latest stable 3.27.1
Flutter run key commands.
r Hot reload. 🔥🔥🔥
R Hot restart.
v Open Flutter DevTools.
s Save a screenshot to flutter.png.
w Dump widget hierarchy to the console.                                               (debugDumpApp)
t Dump rendering tree to the console.                                          (debugDumpRenderTree)
L Dump layer tree to the console.                                               (debugDumpLayerTree)
f Dump focus tree to the console.                                               (debugDumpFocusTree)
S Dump accessibility tree in traversal order.                                   (debugDumpSemantics)
U Dump accessibility tree in inverse hit test order.                            (debugDumpSemantics)
i Toggle widget inspector.                                  (WidgetsApp.showWidgetInspectorOverride)
p Toggle the display of construction lines.                                  (debugPaintSizeEnabled)
I Toggle oversized image inversion.                                     (debugInvertOversizedImages)
o Simulate different operating systems.                                      (defaultTargetPlatform)
b Toggle platform brightness (dark and light mode).                        (debugBrightnessOverride)
P Toggle performance overlay.                                    (WidgetsApp.showPerformanceOverlay)
a Toggle timeline events for all widget build methods.                    (debugProfileWidgetBuilds)
M Write SkSL shaders to a unique file in the project directory.
g Run source code generators.
h Repeat this help message.
d Detach (terminate "flutter run" but leave application running).
c Clear the screen
q Quit (terminate the application on the device).


PR: Added Interface term to single stage finitebeta

The single stage optimization, up to now, has minimized the squared flux corrected for the target magnetic field.
According to texts on free boundary [add reference], an extra term is needed that minimizes the squared of the magnetic field just outside the plasma boundary and the square of magnetic field just inside the boundary.
Added that term here to the optimization.

@f0uriest Could you help with the reference here so that we can compare the terms added here with the ones in the literature?

I haven't seen any particularly clear explanation in the literature, the least bad is probably Hirshman's 1986 paper on free boundary VMEC (doi:10.1016/0010-4655(86)90058-5).
That was using NESTOR to compute the total B outside the plasma due to the coils + plasma field. The equations implemented here are similar but using the virtual casing code to get B_plasma.
One possible extra complication is the presence of a sheet current on the plasma boundary. This is needed when pressure at the edge is nonzero, but is also in general allowed even when edge pressure is zero (at least I haven't been able to prove it's not there). Physically this is just because the plasma itself is a conductor immersed in a magnetic field, so you can get a sheet current that causes a jump in the tangential component of B. In practice it seems like this is usually negligible (for all of the equilibria I've tested in free boundary DESC the field due to the sheet current ends up being < 1e-8x smaller than the field from other sources)


PHP 7 compatibility

Actually, I need to do some more work on this. Please ignore!

Ok! But you best put your effort patch this repo instead: https://github.com/symphonists/importcsv


Bad autodocumentation

The "All Available Options" link under the table of contents points to "https://www.npmjs.com/package/request#requestoptions-callback" when it should actually point to "https://www.npmjs.com/package/request#request-options-callback".

Yep, that's a known issue https://github.com/request/request/pull/1624
Unfortunately this breaks them here (GitHub). I think there were a couple of issues reported in https://github.com/npm/newww, feel free to open up another there, and let them know that's still an issue.


Fix the path from Receive() so it returns an amqp.DetachError

Fix the path from Receive() so it returns an amqp.DetachError if the link is detached.
Fixes #127

Talking about this more with @jhendrixmsft and a few interesting points came up, which might make a fix for this seem more involved.
This particular error is coming from a bit deeper in the stack, from connReader. Currently, the expectation for the code is that an error that deep in the stack will result in the connection actually being reset, which means, ultimately, what we should get back here is ErrConnClosed, not detached.
One disadvantage of ErrConnClosed (or any of our sentinel errors) is that they no longer preserve the inner error that caused the condition. This is particularly useful when logging and debugging from the user's error perspective, so we we'll want to consider how/when this data can be returned.

(closing - @jhendrixmsft has a more general fix for this)


Add Vertex to Ecosystem page

What changed? Why?
ecosystem.json was updated to include the relevant data and a logo was added to public/images/partners.
Notes to reviewers
This information was also previously submitted via the legacy Google Forms process.

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1

@tmns
Hi there! Thanks for this PR! We require that defi apps linked to from base.org include a terms of service / terms and conditions page for users. It doesn't appear that this is present on the linked page. In order to continue the review, could you all please update and resubmit?


nice game

nice game, can you add license details

Sorry, was a little busy, will be sure to add it.


App has just started crashing for no apparent reason.

Hello, today, the manager no longer works and will not allow me to save the cfg/game list and when clicking open steam, it just entirely crashes the process and neither GL nor Steam start loading in the background. GL itself is fine, can launch manually and steam is fine. Something broke in this app as of yesterday.

solution for this? after click play the game steam simply crash...


Read-only connection

An ideas on how to create a read-only connection (only allow get + readStream)?

Good idea! We should add an option to the server stream to support only readonly mode.

added in 2.2.0


Suggest adding sdk version to global.json when deployment fails due to version mismatch

Sometimes an app deployment can fail because the dotnet core buildpack does not supply a version (of the dotnet runtime?? idk) that the app requires. In cases like these it can help to add a global.json file with this entry:
"sdk": {
    "version": "6.0.201",
    "rollForward": "latestFeature"
  }

I'm betting users of this extension would really appreciate a message offering this advice when a deployment fails for this reason

While this would be nice to include in the extension from a user perspective, the real solution is to fix it with one of the open issues for the buildpack:

https://github.com/cloudfoundry/dotnet-core-buildpack/issues/458
https://github.com/cloudfoundry/dotnet-core-buildpack/issues/520


wip dual

Change-Id: I4bef49c6a3e79786e95cf4e1670f39b8c9202974

Codecov Report
Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (9880faa) 97.24% compared to head (020fdf7) 96.91%.
Report is 1 commits behind head on main.

Files
Patch %
Lines

geometry/src/algebra.hpp
90.00%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #36      +/-   ##
==========================================
- Coverage   97.24%   96.91%   -0.33%
==========================================
  Files          12       13       +1
  Lines         145      162      +17
  Branches        4        6       +2
==========================================
+ Hits          141      157      +16
- Misses          0        2       +2
+ Partials        4        3       -1

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