vue/multi-word-component-names: 'off' not respected on pages when nuxt srcDir is changed.

Reproduction:
- Operating System: `Linux`
- Node Version:     `v18.5.0`
- Nuxt Version:     `3.0.0-rc.5`
- Package Manager<EMAIL_ADDRESS>- Builder:          `vite`
- User Config:      `ssr`, `srcDir`, `typescript`, `app`, `vite`, `modules`, `css`
- Runtime Modules:  `<EMAIL_ADDRESS>`<EMAIL_ADDRESS>- Build Modules:    `-`
------------------------------

Go to nuxt.config.ts and change srcDir to src/
Move all folders, including layout and pages, under the src/ directory. But keep eslintrc.json in the root directory still.

I face issues that my layout/page components are not multiword components:

I can see this is because the ESLint rule is very particular about the pages/layout directory being at the top level:
https://github.com/nuxt/eslint-config/blob/d4250a6e4d57835d7c9d3c017ab82a1f55383c98/packages/eslint-config/index.js#L130
It's fixable with the following override in eslintrc.json, but feels dirty:
    overrides: [
        {
            files: ['src/pages/**/*.vue', 'src/layouts/*.vue'],
            rules: {
                'vue/multi-word-component-names': 'off',
            },
        },
    ],

Edit: I suppose the issue disappears when moving eslintrc.json in to the src/ directory however obviously this means the top level directory won't have eslintrules. So for the moment I've defined two eslintrc.json files - I don't know if this is the intended way of doing this:
/eslintrc.json:
{
    "env": {
        "browser": true,
        "es2021": true,
        "node": true
    },
    "extends": [
        "eslint:recommended",
        "plugin:@typescript-eslint/recommended",
        "plugin:prettier/recommended"
    ],
    "parserOptions": {
        "ecmaVersion": "latest",
        "parser": "@typescript-eslint/parser",
        "sourceType": "module"
    },
    "plugins": ["@typescript-eslint"]
}

/src/eslintrc.json:
{
    "extends": [
        "eslint:recommended",
        "plugin:vue/essential",
        "plugin:@typescript-eslint/recommended",
        "@nuxtjs/eslint-config-typescript",
        "plugin:prettier/recommended"
    ],
    "plugins": ["vue", "@typescript-eslint"]
}

With the previous config format, it's not possible for us to have rules that aware the project configurations (custom rootDir). #332 should fix it (tho it's for Nuxt 3). Otherwise, I think the workaround is for you to disable it manually with local overrides.


Added Image Captions

Added captions to images

Please check the following:

[ ] Do the tests still pass?[^1]
[ ] Does the code comply with the style guide?

[ ] Run make lint from the Wagtail root.

[ ] For Python changes: Have you added tests to cover the new/fixed behaviour?
[ ] For front-end changes: Did you test on all of Wagtail’s supported environments?[^2]

[ ] Please list the exact browser and operating system versions you tested:
[ ] Please list which assistive technologies [^3] you tested:

[ ] For new features: Has the documentation been updated accordingly?

Please describe additional details for testing this change.
[^1]: Development Testing
[^2]: Browser and device support
[^3]: Accessibility Target

@DokuaAsiedu thanks for taking the time to contribute this. Can you add some description to this PR with the reasoning behind this change and why the alt text and existing content is not suitable enough to deduce what these images are?
I'd this is an issue you are fixing, could you add a link to it.
Also, it really helps if you can also add before / after screenshots for things like this.

@DokuaAsiedu thanks for taking the time to contribute this. Can you add some description to this PR with the reasoning behind this change and why the alt text and existing content is not suitable enough to deduce what these images are?
I'd this is an issue you are fixing, could you add a link to it.
Also, it really helps if you can also add before / after screenshots for things like this.

I initially added it to provide a description to sighted readers on what the images are. However, I did some research and it seems that images with alt text do not need captions.
As this change was not necessary, I'll close this pr now?

Thanks @DokuaAsiedu - yeah I think its best to close this PR then.


phnt kernel store manager additions

Added structures and minimal docs for store manager information classes (except ProcessStoreInfoRequest) that are accessible trough NtQuery/SetSystemInformation. (versions of queries might be outdated as my main reversing IDB is quite old)

Nice, thanks 👍


Rebuild included html per generate

Resolves https://github.com/MarkBind/markbind/issues/127
Problem
Dynamically Included file is built based on whether the include.html exists.
During live reload, dynamically included files that are nested in other dynamically included files will  not reload due to the reason above.
Solution
Do not decide to build file based on whether the include.html exists.
Instead maintain a set of all files built during page.generate().
Considerations
The removed code is actually an optimization for the build process. Introducing the new heuristic only adds around 5- 10s of additional build time. However, live reload works as intended. As a comparison, removing the previous check which works adds 15-20s.
Testing

build site once and save.
make changes to \website-base\book\codeQuality\practices\useNameExplain\text.md
$ markbind serve
undo the change made in 2 while serving and wait for live reload
compare new _site with site in 1.

"5- 10s of additional build time" is large.
Since it was doing fs.statSync, how about checking last modified file date of sourcePath vs resultPath?

Understand the concern for build time. Will work on an optimization for this. I think checking for time may not be so suitable as multiple live reloads in succession may result in files not being regenerated.

On further testing, I realised how i test timing may be quite unreliable. Sometimes one will be faster than the other. However, internally, the changes in this pr will definitely result in more rebuild of pages, may I will try to find a better solution.

I think checking for time may not be so suitable as multiple live reloads in succession may result in files not being regenerated.

How so?

I think checking for time may not be so suitable as multiple live reloads in succession may result in files not being regenerated.

How so?

By using a timing, we must impose some sort of ignore time? Eg: this file was changed 30s ago, we should not rebuild it. But then if we do live reload in quick succession, we may incorrectly choose not to rebuild some files. This timing is also system dependent.
Do let me know if i misunderstood what you said.

I meant last modified file date of sourcePath < last modified file date of resultPath.
But I realised that's not a reliable criteria if any of the static included files are modified.

700/ 709 files are not rebuilt
631 files are not rebuilt

How are those numbers calculated?

How are those numbers calculated

Everytime a fileexists, i will add it to a global count.
Here is some timing i did. (Im not sure if this is very accurate)
What i did was console.time('build') at the start of the build.
When the build finished, i do console.timeEnd('build').

Seems like with the changes the build is faster. Possibly because there are no file operations? But i'm still skeptical because of my lack of experience in profiling. In fact, i realised the build time gets faster with each build... So i'm not too sure if my "experiment" was fair.
I also noticed this weird diff that keeps appearing for
_site/book/principles/openClosedPrinciple/index.html

@nicholaschuayunzhi Can you rebase these commits?

@acjh Sorry i missed your comment! The branch is already on top of master. Did you mean for me to squash commits together?

Yes.

@acjh ok done!

I've made the requested changes. Apologies for missing out the @param variable naming.


Unable to detect UE version from .uproject file on custom UE build

I get the error Cannot detect UE version from .uproject file when loading my project.
In my .uproject file the EngineAssociation field has the value "4.26.2-ABC". It looks like your code assumes the version field will only be 2 parts, in which case even using the standard 4.26.2 engine version would fail: XVersion.cs
Perhaps that code could be updated to only read the first 2 parts of the SemVer and ignore the rest?

Hi @mklierman, thanks for reporting the issue.
I play tested with 4.27.2, 5.0.3 and 5.1 and I always had the pattern MAJOR.MINOR in the .uproject (patch number was never present). So I worked with this assumption.
Anyway I can take into account the custom version pattern as you propose, and make the version parsing less "restrictive".

Now can recognize the following semver pattern: MAJOR.MINOR.PATCH-LABEL where:

MAJOR and MINOR stay mandatory
PATCH is optional
LABEL is optional (separated by ''-")

@mklierman FUnreal v0.0.5 is out and should address your issue

Thanks. I can confirm it worked


insim: upgrade or remove deku

We're a bit behind on a lot of crates. Deku is probably the most problematic.
deku 0.14.0 introduces a breaking change, meaning all our custom DekuRead and DekuWrite implementations are wrong.
deku 0.15.0 upgrades BitVec which changes the bitvec::BitSlice<Msb0, u8> into bitvec::BitSlice<u8, Msb0>
Immediate thoughts:

Remove deku entirely and rely on #[repr(C)] and transmute_copy

Pro: Easier to upgrade in future
Con: Any custom types we've added are almost certainly screwed, we'd need to add all the padding bytes and will probably kill my interest

Remove deku entirely and replace with handwritten rust impl, or some kind of custom serde implementation

Pro: Will probably reduce the compile time
Pro: Less likely to break in future
Pro: Might be easier to solve support multiple versions of insim more easily
Pro/Con: Unknown perf implications - could be worse, could be better.
Con: Thats a lot of code that will need to likely be rewritten

Upgrade deku and leave everything as-is

Pro: It'll work
Con: Thats a still a lot of code that needs some futzing with
Con: Deku is unstable, will this happen again in the future?

Upgrade deku, but remove as many handwritten DekuRead and DekuRead impl in favour of a generic macro

Pro: It'll work
Pro: It'll be easier to upgrade in future
Con: Need to figure out how many we can realistically move into a generic macro

All things considered (fun, likelihood of future breakage and amount of effort), I’m going to try out writing a custom Serde (de)serializer.
We don’t need half of what deku offers, making this is a mid way between writing custom serializer methods for each struct and let’s be honest serde is pulled into so many projects anyway.
Will rough it out to start with in a separate crate (serde_insim?) and go from there.

New plan: serde doesn’t fit amazingly well so it’s a custom trait and a prof macro that’ll do just what’s needed and nothing more.
We need: from and to bytes, skip and pad after/before support, and possibly some way to declare a fixed length. Anything custom we implement the trait by hand. Job done.


Add Blosc2 Compression to ImageData

Currently our program uses an excessive amount of memory as it stores all the image data in an uncompressed manner which leads to big files (a focus of what this API should be able to handle) taking up loads of memory.
An example file which unfortunately cannot be shared is ~6GB on disk but takes up >80GB of memory when decompressing it in release mode. The file contains 170 Image layers (and some more mask layers) and has a bit depth of 16 with a resolution of 9124x6082
The goal of this change would be to bring memory usage on par with, or slightly above what photoshop files store but without sacrificing on performance too much.

From initial testing this seems very promising, the 82 gigabytes of in-memory data get compressed to about 6 gigabyte while also offering a ~2x speed increase due to less memory transfer

While checking on the compression I also implemented AVX2 SIMD support for byteswapping.
Additionally I found that even on my 16 core AMD 5950x I was only experiencing a ~3x speedup in wall time from the current parallel implementation of the ChannelImageData. This turned out to likely be due to the parallel loops accessing data at vastly different locations. The implementation has been improved a lot now, cutting out on loads of memcpy() which brought processing time down from about 2.5 mins on all cores to 45 secs on 4 cores while keeping memory usage around 10 gigabytes. Roughly 1/3 of what photoshop consumes when opening the file.
Unfortunately, what is holding back performance still is the fact that the zip compressed Image data can not trivially be parallelized. I have brought down the rest of the processing as much as possible and will continue to do so gradually

The above mentioned performance numbers is where it will be left for now as that is plenty performant for our needs for the time being


[LLC] Rename Get to GetResource for template-LLC

The generator automatically renames a method named Get to Get<OperationGroupName> or Get<ServiceClientName> if operation group name is empty. In the case of templateLLC, Get is renamed to GetTemplateService using the client name, but that's not a proper name and based on what it really returns (plus the list method is called GetResources), we manually rename it to GetResource in this PR.
This is a follow-up PR for https://github.com/Azure/autorest.csharp/pull/1657 and #25311.
All SDK Contribution checklist:
This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] Please open PR in Draft mode if it is:

Work in progress or not intended to be merged.
Encountering multiple pipeline failures and working on fixes.

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code. (Track 2 only)
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK. Please double check nuget.org current release version.

Additional management plane SDK specific contribution checklist:
Note: Only applies to Microsoft.Azure.Management.[RP] or Azure.ResourceManager.[RP]

[ ] Include updated management metadata.
[ ] Update AzureRP.props to add/remove version info to maintain up to date API versions.

Management plane SDK Troubleshooting

If this is very first SDK for a services and you are adding new service folders directly under /SDK, please add new service label and/or contact assigned reviewer.

If the check fails at the Verify Code Generation step, please ensure:

Do not modify any code in generated folders.
Do not selectively include/remove generated files in the PR.
Do use generate.ps1/cmd to generate this PR instead of calling autorest directly.
Please pay attention to the @microsoft.csharp version output after running generate.ps1. If it is lower than current released version (2.3.82), please run it again as it should pull down the latest version.

Note: We have recently updated the PSH module called by generate.ps1 to emit additional data. This would help reduce/eliminate the Code Verification check error. Please run following command:
  `dotnet msbuild eng/mgmt.proj /t:Util /p:UtilityName=InstallPsModules`

Old outstanding PR cleanup
Please note:
If PRs (including draft) has been out for more than 60 days and there are no responses from our query or followups, they will be closed to maintain a concise list for our reviewers.

API changes have been detected in Azure.Template.LLC. You can review API changes here
API changes
+         public virtual Response GetResource(string resourceId, RequestContext context = null);
+         public virtual Task<Response> GetResourceAsync(string resourceId, RequestContext context = null);
-         public virtual Response GetTemplateService(string resourceId, RequestContext context = null);
-         public virtual Task<Response> GetTemplateServiceAsync(string resourceId, RequestContext context = null);

Thanks for finding and addressing this, @fengzhou-msft!  It would be great to address this in the swagger directly, rather than as readme transforms.  I noticed that the generated client also takes an optional Uri, but for data plane clients, this should be required.  Would you be willing to update this while you're working on this change?

API changes have been detected in Azure.Template.Generated. You can review API changes here
API changes
+         public virtual Response GetResource(string resourceId, RequestContext context = null);
+         public virtual Task<Response> GetResourceAsync(string resourceId, RequestContext context = null);
-         public virtual Response GetTemplateService(string resourceId, RequestContext context = null);
-         public virtual Task<Response> GetTemplateServiceAsync(string resourceId, RequestContext context = null);

Thanks for finding and addressing this, @fengzhou-msft! It would be great to address this in the swagger directly, rather than as readme transforms. I noticed that the generated client also takes an optional Uri, but for data plane clients, this should be required. Would you be willing to update this while you're working on this change?

The template swagger.json uses a hard-coded value for host, that's why Uri is optional in the generated code. Do we want to change it to parameterized host?

Do we want to change it to parameterized host?

Yes, for data plane libraries, we use x-ms-parameterized-host, for example:

https://github.com/Azure/azure-rest-api-specs/blob/main/specification/containerregistry/data-plane/Azure.ContainerRegistry/stable/2021-07-01/containerregistry.json#L8
https://github.com/Azure/azure-rest-api-specs/blob/main/specification/cognitiveservices/data-plane/TextAnalytics/stable/v3.1/TextAnalytics.json#L25

API changes have been detected in Azure.Template.Generated. You can review API changes here
API changes
-         public TemplateServiceClient(TokenCredential credential, Uri endpoint = null, TemplateServiceClientOptions options = null);
+         public TemplateServiceClient(Uri endpoint, TokenCredential credential, TemplateServiceClientOptions options = null);
+         public virtual Response GetResource(string resourceId, RequestContext context = null);
+         public virtual Task<Response> GetResourceAsync(string resourceId, RequestContext context = null);
-         public virtual Response GetTemplateService(string resourceId, RequestContext context = null);
-         public virtual Task<Response> GetTemplateServiceAsync(string resourceId, RequestContext context = null);


Many TLS 1.3 test cases are not executed on the CI

The result analysis on the CI shows that many TLS 1.3 test cases are not executed as of mbedtls-3.1.0. (Example log)
The goal of this task is to analyze why (missing configurations? Missing openssl or gnutls version? …) and either fix the problem or file one or more issues to fix the problem(s).

@ronald-cron-arm notes that some of them are false positives: tests from tests/opt-testcases/tls13-compat.sh are reported as from ssl-opt.sh at runtime, but analyze_outcomes.py treats them as being from tls13-compat.sh. record_outcome in ssl-opt.sh should be amended to report the correct file name.

https://jenkins-mbedtls.oss.arm.com/job/mbed-tls-pr-head/job/PR-5393-head/2/execution/node/5326/log/ shows that all of the not-executed TLS 1.3 test cases were false positives due to the test suite name mismatch.


Can O' Spam: Watch<EMAIL_ADDRESS>

Can O' Spam requests the watch of the watch_keyword mehmudalom726(?#@gmail.com). See the MS search here and the Stack Exchange search in text, in URLs, and in code.

<EMAIL_ADDRESS>has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Update scalafmt-core to 3.0.1

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

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

labels: library-update, semver-major

Superseded by #412.


Error compiling with Strapi 4.3.3

how can i solve this error
when I do "npm run build" it compiles normally, but when I do "npm start" I get that error

I need help thanks

@andrespaucar Check #23


NZBGet as a download client

Name the integration
I use NZBGet for sonarr/radarr and would love to see this supported as a download client
https://nzbget.net/
https://nzbget.net/api/
Please tick the boxes

[X] You've read the docs
[X] You've checked for duplicate issues
[X] You're not just putting an idea out there and actually give usefull information about how to implement your module idea

Another vote for NZBGet. I would need it just to sum its download values to Current Download Speed graph. Currently it shows only from Transmission. I would love if it would sum also values from NZBGet.

+1 for usenet but i use SABnzbd.

Was just coming here to request this integration, so I will instead voice my support here.

Very interested in getting NZBGet support as well! It would be fantastic to have all my apps in one place

Another vote for this one. And sorry for making a duplicate.

This was added in v0.10.4 ! Thanks to @jonjon1123


p5.js website have issues in copy button alignment and position in get-started page

Most appropriate sections of the p5.js website?
Other (specify if possible)
What is your operating system?
Windows
Web browser and version
1.49.120 Chromium: 111.0.5563.64 (Official Build) (64-bit)
Actual Behavior
Issues in copy button alignment :
In Desktop -->

In tablet mode -->

In mobile mode -->

The copy button's user interface is not particularly engaging and makes it difficult for users to distinguish which button corresponds to which code.
You can check on : p5.js website
Expected Behavior
After solving problem website looks like -->
Desktop Mode -->

Tablet mode -->

Mobile mode -->

I hope this helps .
Steps to reproduce
step 1 -->
Open get-started folder -->

step 2 -->
Shifting copy div to before pre tag -->

step 3 -->
Go to all.css file and  change css of edit_space and copy button to -->

Would you like to work on the issue?
Yes ,I want to work on this issue and raised PR for this .

Can I raise PR now ?

i want to work on this one

Thank all for your input on this issue. We have a website redesign project pending in the near future to rethink the overall design of the website. So I will close this issue for organizational purposes, and we can revisit all the issues labeled ‘Web Design’ during the website redesign phase.


added support for event api payload changes

Summary
Fixes #655
Requirements (place an x in each [ ])

[x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.

Thanks for the review @seratch! I ended up committing your suggested change


Boot order for floppy disks is not respected

Describe the issue
I can not install Win95b because after partitioning the hard disk I can not boot from floppy disk anymore. I think the cause is that the qemu bootindex command line parameter for the floppy disk is missing and so has the least boot order priority.
Configuration

UTM Version: 2.0.27
OS Version: Big Sur
Intel or Apple Silicon? M1

Can you please try reordering the drives in the Drives Configuration? It is supposed to try booting from the topmost drive first, and so on. So your floppy drive should be at the top of the list. Note that rearranging the drives clears any selected removable drives, so you need to browse to the files again.

Hello @conath, I already tried that and the floppy drive is at the first position of the list. But it does not get a bootindex parameter (see screenshot). Perhaps that is the problem?


Improve population stabalization

This makes the population stabilization more subtle by

Introducing fewer new mice
Introducing new mice as babies near other mice of their color, to make it seem like a normal birth

Note, this is just from Fix how agents are added to new environment onwards, other commits will be rebased out once #162 is merged.


BioData Catalyst Open Access UI implementation

[ALS-4794] Update UI to support no login
[ALS-4811] BDC Open Access Landing Page
[ALS-4850] BDC Go to Authorized PIC-SURE Pop-up
[ALS-4814] BDC Open Access Data Dashboard

Duplicate PR. Changes already exist in open/release/0001.


add a unique uuid to each IP

on every acquire even the same ip will have a unique uuid.
This will make it possible to identify if this ip belongs to the same entity as before and allows hardening deletion in upper levels such as metal-api.

Codecov Report

Merging #28 into master will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #28      +/-   ##
==========================================
+ Coverage   81.53%   81.56%   +0.03%
==========================================
  Files           8        8
  Lines         509      510       +1
==========================================
+ Hits          415      416       +1
  Misses         50       50
  Partials       44       44

Impacted Files
Coverage Δ

ip.go
87.50% <ø> (ø)

prefix.go
82.63% <100.00%> (+0.06%)
:arrow_up:

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 e27e442...52d56b0. Read the comment docs.

An IP can only be allocated once and has a unique allocation ID? So it is up to the caller/user of this library to store this UUID too (beside the IP address)?
This library does not check the UUD when releasing an IP?

I thought about storing the uuid as well and deny deletion if given UUID does not match, sounds like a reasonable addition

I'm not sure what i get with this PR. when doing an AquireIP i get an *IP which now contains a UUID. As a caller of this function i have to store this *IP or at least the UUID in my database too.
Is there any way to query the IP (and the current UUID) from the go-ipamer? So the caller could do some consistency checks before releasing an IP? I do not see a method in the Ipamer interface.
When using this library in the metal-api the IP-service has to store this UUID, correct? So the go-ipamer is only a sugared UUID-generator?
Our pain in the past was, that we release IP addresses in an async way. So we thought it would be a good idea to have some unique identifier for the IP entity to make sure no one deletes an IP (in the async future, because we retry it in some cases) which was already allocated by another one. but i don't understand how i could do a consistency check if neither the library does this check nor i have the chance to query the current UUID of a given IP. i simply can release the IP by its address and can only hope that it was allocated with the same UUID i (the caller) have stored in my database.
or i do not see the advantage ...

You are right ! But addressing this issue is still important. The main failure from the beginning was to treat the Prefix/Cidr as primary key for the whole design. Therefore i didn't choose UUIDs.
Adding them now is more difficult, without breaking things.
Have to think a bit deeper, make a draft out of this.

Closing because we implemented this in metal-api


pipeline does not create images correctly

the image created by the pipeline is not a multiarch image:

This is how it should appear instead (showing a multiarch images, with three supported architectures):

@raffaelespazzoli are we good to close this issue?


Syntax highlighting breaks with # in source code mode (line indented)

Exemple:
Install RVM along with the latest version of Ruby:
$ curl -#L https://get.rvm.io | bash -s stable --autolibs=3 --ruby

RVM will download and build the Ruby language.
Asciidoctor ignores a # in source code mode (indenting lines), however the syntax highlighter expexts a closing #, but doesn't find it.

Could you please check with the latest extension version ? (I was unable to reproduce)

Thanks, seems OK now


Invalid AES key length

➜ echo UFlZUEBLRkBISEZa |base64
VUZsWlVFQkxSa0JJU0VaYQo=
do_decrypt :: Invalid AES key length: 17 bytes

requests need urlencode/decode and response do not need  urlencode/decode in some  cases

➜ echo UFlZUEBLRkBISEZa |base64
VUZsWlVFQkxSa0JJU0VaYQo=
do_decrypt :: Invalid AES key length: 17 bytes

key is not correct in this case

requests need urlencode/decode and response do not need urlencode/decode in some cases

you have to customize the current code for that


TBDeviceMqttClient may be slow

Have you done any performance tests for TBDeviceMqttClient itself? I may suspect it can't generate more then 10000 requests/second?

Hi @
Thank you for your interesting and your question.
in my case I’m using multithreading in the testing code ( a thread for each client), and codes are running on 10 machines (VMs hosted in the cloud) and as first test configuration I have a total of 2500 (250 on each machine) device publishing a message every 10 seconds I know this is very basic test  but the tool still under development, and I will attempt to increase the load exponentially till I get fail results.
for better control I use Docker containers to run the code and Ansible as automation tool for the VMs
a future work is to create a distributed load test system ( very similar to a DDoS attack  but for the good case of use)
I hope that we are in the right path, also any suggestion is appreciated.


support multi-arch images and update to debian bullseye

There are 4 workflows building images:

integration-tests.yml
k8s-testing.yml
new-release-tag-docker.yml
unit-tests.yml

However, only new-release-tag-docker.yml pushes to a registry, the rest is local use. If one tries to buildx multi-arch images when not directly pushing, one gets the following error:
/usr/bin/docker buildx build --tag defectdojo/defectdojo-django:latest --platform linux/amd64,linux/arm64 --output type=docker,dest=django_img --iidfile /tmp/docker-build-push-wsVRG2/iidfile --metadata-file /tmp/docker-build-push-wsVRG2/metadata-file --cache-from type=local,src=/tmp/.buildx-cache-django --cache-to type=local,dest=/tmp/.buildx-cache-django --file Dockerfile.django .
error: docker exporter does not currently support exporting manifest lists
Error: buildx failed with: error: docker exporter does not currently support exporting manifest lists

So only new-release-tag-docker.yml was touched.
Closes #5525

Locally, two things to mention:

When building the django image, the pyNacl wheel takes 50m to build in my machine. This can be circumvented by installing libsodium-dev previously to running the wheels for requirements.txt (https://github.com/pyca/pynacl/issues/654). I have the idea this won't happen just locally, but the solution is trivial and works for both amd and arm.
When building the nginx image, we suffer from a known issue (https://githubmemory.com/repo/laravel/sail/issues/159) when executing curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -. This can by solved by: a) moving this link to http, which is not good; b) using debian bullseye instead of buster

Thanks @tiagoposse for the PR and suggestions, will take a look. What do about think about the fact that we build and push arm64 images without testing them? I haven't looked, but it's probably hard to deploy/test arm64 with GitHub Actions? Or maybe it isn't: https://github.com/uraimo/run-on-arch-action?

IMO arm64 has come a long way and with the m1s, this will become better and better, So I don't think pushing without testing is that bad. Additionally, considering the actual state of the dockerfiles, there is no http/ftp/etc download of binaries, so if everything builds, it should work.

Did you test the workflow in your fork, for example by pushing to your personal docker hub account?

I did not test the github workflows, but I am running these images in my company's cluster, under arm64, and so far have experienced no issues. I've uploaded scan reports successfully.
defectdojo.pdf

It's more about if they build well and upload well from GHA. To prevent any errors during our release process.

I was able to complete the build for django but not for nginx as I faced the error described above. What would be your preferred solution:
a) use http://dl.yarnpkg.com/debian/pubkey.gpg instead of https
b) try with a python image that is based on debian bullseye, instead of buster

We can upgrade to bullseye in 2.6.0, first we want to release 2.5.0 on December 7th.

@tiagoposse I upgraded to bullseye, but the uwsgi wheel won't build. Do you have any idea? https://github.com/DefectDojo/django-DefectDojo/runs/4718480444?check_suite_focus=true#step:4:1674

sorry for the delay on this, lots of personal things to take care this month. It seems that uwsgi needs gcc to be built on bullseye. Since this is being built on a stage, I guess this wouldn't pose issues?

uwsgi won't build on bullseye if you use pip wheel uwsgi as you can see in the PR that I linked.

I understand that :)
it is possible to build it by installing gcc, here's me installing it on the image in your pr:
tiagoposse@admins-MBP django-DefectDojo % docker run -ti --entrypoint bash --rm python:3.8.12-slim-bullseye@sha256:3d3edc52cfae3ed6fb8303559f10184f962a8069194b2dee93baaac66ebedeb5
root@20aeba31192f:/# pip wheel uwsgi
Collecting uwsgi
  Downloading uwsgi-2.0.20.tar.gz (804 kB)
     |████████████████████████████████| 804 kB 5.7 MB/s
Building wheels for collected packages: uwsgi
  Building wheel for uwsgi (setup.py) ... error
  ERROR: Command errored out with exit status 1:
   command: /usr/local/bin/python -u -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-wheel-igq1clph/uwsgi_6c5650649c1a4edeaf0724b5b7fa5d24/setup.py'"'"'; __file__='"'"'/tmp/pip-wheel-igq1clph/uwsgi_6c5650649c1a4edeaf0724b5b7fa5d24/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-712uy3z8
       cwd: /tmp/pip-wheel-igq1clph/uwsgi_6c5650649c1a4edeaf0724b5b7fa5d24/
  Complete output (42 lines):
  /usr/local/lib/python3.8/distutils/dist.py:274: UserWarning: Unknown distribution option: 'descriptions'
    warnings.warn(msg)
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build/lib
  copying uwsgidecorators.py -> build/lib
  installing to build/bdist.linux-x86_64/wheel
  running install
  using profile: buildconf/default.ini
  detected include path: ['/usr/include', '/usr/local/include']
  Traceback (most recent call last):
    File "/tmp/pip-wheel-igq1clph/uwsgi_6c5650649c1a4edeaf0724b5b7fa5d24/uwsgiconfig.py", line 750, in __init__
      gcc_version_components = gcc_version.split('.')
  AttributeError: 'NoneType' object has no attribute 'split'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "<string>", line 1, in <module>
    File "/tmp/pip-wheel-igq1clph/uwsgi_6c5650649c1a4edeaf0724b5b7fa5d24/setup.py", line 117, in <module>
      setup(
    File "/usr/local/lib/python3.8/site-packages/setuptools/__init__.py", line 153, in setup
      return distutils.core.setup(**attrs)
    File "/usr/local/lib/python3.8/distutils/core.py", line 148, in setup
      dist.run_commands()
    File "/usr/local/lib/python3.8/distutils/dist.py", line 966, in run_commands
      self.run_command(cmd)
    File "/usr/local/lib/python3.8/distutils/dist.py", line 985, in run_command
      cmd_obj.run()
    File "/usr/local/lib/python3.8/site-packages/wheel/bdist_wheel.py", line 335, in run
      self.run_command('install')
    File "/usr/local/lib/python3.8/distutils/cmd.py", line 313, in run_command
      self.distribution.run_command(command)
    File "/usr/local/lib/python3.8/distutils/dist.py", line 985, in run_command
      cmd_obj.run()
    File "/tmp/pip-wheel-igq1clph/uwsgi_6c5650649c1a4edeaf0724b5b7fa5d24/setup.py", line 77, in run
      conf = uc.uConf(get_profile())
    File "/tmp/pip-wheel-igq1clph/uwsgi_6c5650649c1a4edeaf0724b5b7fa5d24/uwsgiconfig.py", line 758, in __init__
      raise Exception("you need a C compiler to build uWSGI")
  Exception: you need a C compiler to build uWSGI
  ----------------------------------------
  ERROR: Failed building wheel for uwsgi
  Running setup.py clean for uwsgi
Failed to build uwsgi
ERROR: Failed to build one or more wheels
WARNING: You are using pip version 21.2.4; however, version 21.3.1 is available.
You should consider upgrading via the '/usr/local/bin/python -m pip install --upgrade pip' command.
root@20aeba31192f:/# apt update > /dev/null && apt install -y gcc > /dev/null

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

debconf: delaying package configuration, since apt-utils is not installed
root@20aeba31192f:/# pip wheel uwsgi
Collecting uwsgi
  Using cached uwsgi-2.0.20.tar.gz (804 kB)
Building wheels for collected packages: uwsgi
  Building wheel for uwsgi (setup.py) ... done
  Created wheel for uwsgi: filename=uWSGI-2.0.20-cp38-cp38-linux_x86_64.whl size=510247 sha256=378226b3d7ed028d25cfaa590d7007a559edcc4567caa88e40a1221bd6e996e3
  Stored in directory: /root/.cache/pip/wheels/cb/4d/54/002a215100a8c4e125654600f0a4304dae742442ddc4ba6ea1
Successfully built uwsgi

You'll notice it fails without gcc, but succeeds with. I am able to build the django image successfully by adding gcc to the "build" stage (first line of apt install):
FROM base as build
WORKDIR /app
RUN \
  apt-get -y update && \
  apt-get -y install --no-install-recommends \
    gcc \
    build-essential \
    dnsutils \
    default-mysql-client \
    libmariadb-dev-compat \
    postgresql-client \
    xmlsec1 \
    git \
    uuid-runtime \
    && \
  apt-get clean && \
  rm -rf /var/lib/apt/lists && \
  true

Since this is not the final stage of the image, the final image is not bloated by the change.
I was able to build both defecdojo-django and defectdojo-nginx locally for both platforms after adding gcc to the respective apt install steps. I can provide an MR to your branch if needed.
I can also confirm that both issues specified in my post above no longer happen after updating to bullseye:

Locally, two things to mention:

When building the django image, the pyNacl wheel takes 50m to build in my machine. This can be circumvented by installing libsodium previously to running the wheels for requirements.txt (Pynacl on Apple Silicon/ARM64 pyca/pynacl#654). I have the idea this won't happen just locally, but the solution is trivial and works for both amd and arm.
When building the nginx image, we suffer from a known issue (https://githubmemory.com/repo/laravel/sail/issues/159) when executing curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -. This can by solved by: a) moving this link to http, which is not good; b) using debian bullseye instead of buster

I would also be able to push these updates to this MR if you'd prefer.

hmm I though I had gcc installed. I followed the steps from https://uwsgi-docs.readthedocs.io/en/latest/Install.html. The result was that I could run pip install uwsgi which worked fine. But pip wheel uwsgi didn't work. Also I didn't get any clear error message like the one you have, I am just seeing "command exited with code 1". Nothing else. I will do another test on my branch.

OK, seems to work now with gcc, didn't think of that as pip install also seemed to compile the wheel.
Can you add all your changes to the PR so we can review? Can you rebase against the dev branch?

FYI Build still fails, even with gcc added: https://github.com/DefectDojo/django-DefectDojo/runs/4963310430?check_suite_focus=true

I'm seeing the same behaviour now. Works locally but fails on github actions

Rebasing to dev added a few conflicts

Locally it's a hit and miss, I can build several successfully several times in a row and then hit errors another several times in a row.
It seems though that I've finally worked around it. I found this post and comment: https://github.com/unbit/uwsgi/issues/1318#issuecomment-542238096, which puts CPUCOUNT=1 before the wheel installation. this seems to fix it and a successful run can be seen here: https://github.com/tiagoposse/django-DefectDojo/runs/4964232859?check_suite_focus=true

still fails at https://github.com/DefectDojo/django-DefectDojo/runs/4964457401?check_suite_focus=true

The build you linked fails for defectdojo-nginx, for which you didn't add CPUCOUNT=1 (nginx image also builds the wheel so it also needs this)
I've cleaned up this MR as well after all the trash that got mixed in the rebase.

ah thanks, doing too many things at the same time. Can you add the comments from my PR to your PR? If all gets green, we'll merge yours for 2.8.0.

totally understandable. Comments added, fingers crossed :D

Thanks for working with us on this. Could you update the description a little bit to reflect what the PR does/changes?

my pleasure. Done

I've finally managed to get around testing the deployment of this version in arm64 today and it didn't work. The pinned SHA digest seems to be for amd64 only. I'll provide a fix shortly.

Friendly bump - any chance this can be pulled in? I noticed the original issue here: https://github.com/DefectDojo/django-DefectDojo/issues/5525#issuecomment-1165802732.

Would also love to see this merged :)

No point in merging something that doesn't work. If anybody knows how to make it work in combination with base image pinning by hash and renovate/dependabot, please help 🙂

hah I seem to have missed the SHA problem post, sorry about that. I'll take a look again

@tiagoposse, thank you for this PR. In our PR review this week discussed, and we do think that there is a strong argument for this use-case given M1 chips. We're going to discuss this more internally. I apologize for the delay on this. Will update you via this PR as we discuss more internally.

Great to see this gaining traction :+1:. I've found a workaround for now but definitely still interested. Unfortunately due to personal reasons I have lost most of the free time I had, so it's hard to contribute further, but happy to help where possible


Structs use comma now

In IDE I keep getting: WGSLTokenType.SEMICOLON expected, got ',' at the end of a struct field.
WGSL standard now defines shader structs with a comma rather than a semicolon.

This is a duplicate of #18 . I am currently working on a fix


LUNA support

Support LUNA as a backend: https://github.com/greatscottgadgets/luna/issues/151

Available here: https://github.com/greatscottgadgets/Facedancer/blob/master/facedancer/backends/moondancer.py


UIControl slider inside content view

Hi,
in contentViewController i have a view slider (TTRangeSlider) and it's not working when I try to move slider, the floating panel always try to dismissed, but the slider working when i set filterPanelVC.panGestureRecognizer.isEnabled = false
I've tried add this in delegate method but still not working :
func floatingPanel(_ vc: FloatingPanelController, shouldRecognizeSimultaneouslyWith gestureRecognizer: UIGestureRecognizer) -> Bool {
        switch vc {
        case filterPanelVC:
            return (vc.contentViewController as? CategoryFilterVC)?.priceSlider.gestureRecognizers?.contains(gestureRecognizer) ?? false
        default:
            return false
        }
    }

Any idea to make both swipe to dismiss and the slider working ?
Thank you

Thanks for your report, @mnizar! TTRangeSlider handles touches directly without any gesture recognizers. Therefore, could you please try this setting?
filterPanelVC.panGestureRecognizer.cancelsTouchesInView = false

If it works, I'm going to modify the library to support the settings by default.

Hi,
it's work with set panGestureRecognizer.cancelsTouchesInView = false
but the panel always bouncing when i try to change slider, and sometimes the panel is closed
here's attached example project
Thank you
FloatingPanelSlider.zip

I'm sorry to be late for my reply. Thanks for your example code!
This issue will be resolved by using  floatingPanelShouldBeginDragging(_:) delegate method to control moving a panel. It's developing on improve-operability branch. I will be merged when I release on v1.4.0.

Ref #193


Sender don't recieve hard fail messages

Is there any way, that bounce messages and hard fail notifications get back to the original sender?

Please read https://github.com/atech/postal/wiki/Auto-Responders-&-Bounces but note your return path is probably psrp.yourdomain.com and they can only be sent via HTTP webhook endpoints

Ok thanks for your answer. Is #255 still open? In my opinion an smtp endpoint should work also.

It looks to still be open but whether it will receive any work, I'm not sure.

In my opinion hardfails should be returned / notify to the sender, like any other platform would do.


Move the creation of bootstrap beans into create function

The change I made in #317 which registered a new ConfigSeverInstanceProvider.Function only partially worked.  All the beans that were registered in the initialize method really didn't do anything anymore.  They all check if the right properties are enabled but that always resulted in false because the properties are not set in the environment when Boot initially load configuration.
Further more the new ConfigServerInstanceProvider.Function did not check if existing beans were already registered. I attempted to fix that in #325 but that fix did not work as I thought it did.
This fix should truly fix #324

@pantherdd would appreciate your eyes on this as well.  My last fix didn't end up working, I think this ultimately solves #324

@ryanjbaxter Sure, I'll try to find some time for it this week.

For the record, this was superseded by #328 as the final solution to #324.


[WIP] HEP: Gracefully Shutdown Harvester Cluster [CI SKIP]

IMPORTANT: Please do not create a Pull Request without creating an issue first.
HEP: Gracefully Shutdown Harvester Cluster

Signed-off-by: Jian Wang<EMAIL_ADDRESS>
Problem:

How to gracefully shutdown an running Harvester cluster? no clear answer yet.
Solution:

Add to a new feature to accomplish this.
Related Issue:
https://github.com/harvester/harvester/issues/3261
One previous DOC PR: docs: add cluster shutdown and restart
Test plan:

BTW: all review comments are welcome, thanks.

reopening, this is still meant to be active

ping, keeping this PR active


Put @prisma/sdk version in lockstep with prisma2

And at the same time lock down the version of the binaries delivered with that package, the same way we do it in prisma2. The reason is very simple: Tools that depend on @prisma/sdk right now need a complex setup to pin the binary version.

Fixed in latest version.


Equals implementation of IPath

Hi,
Could you review the implementation of Equals ?
It fails in my code (e.g a file retrieved from the IAbsoluteDirectoryPath.GetChildFiles() method and another one from the regular ParseAbsolute() method ... referring to the same file obviously).
I've taken a look at source code, and in my mind, the implementation does not make sense (when the other.PathDisplay is tested ?)

Seems fine to me. Is the casing of the path the same in both cases? We don't attempt to figure out if paths with different cases point to the same file or not, that's a whole complex issue that has no reliable solution.

(With the exception of the drive letter in Windows - we treat c:\ as the same as C:\. The rest of the path has to have matching casing).

Oh wait, you're right that there may be a bug there, but the problem appears to be the opposite of what you're describing: it will match as equals when they aren't.

Fix pushed to nuget as v1.0.1, should be available in a few minutes. I'll close the issue as I believe that should resolve any equality issue you were having but if you still have a problem let me know and I'll reopen.

Closed via https://github.com/Singulink/Singulink.IO.FileSystem/commit/63905e4a6e05546b182ea84d2fe37b198bbbaff7
Nuget package v1.0.2 posted, should be available in a few mins.

It works. Thanks for your quick fixes.


Add capability to scan sub-directories to find_licenses()

I needed to add some functionality to LicenseCheck to allow my package PkgToSoftwareBOM to easily search a package's source code, not just for the overall license but for any other licenses that may be attached to particular files.
A new keyword is added to find_licenses(), scan_subdir, that allows the function to search through all the sub-directories of the specified target directory.
To support this capability, the keyword preserve_path was added to license_table, find_licenses_by_list_intersection, and find_licenses_by_bruteforce.
Tests have been added to demonstrate the new capability and documentation updated.
If this PR is accepted I would request that a new version be released soon so that I can use it with my package.

I've decided to withdraw this PR for now.  May break this apart and submit in a couple of PRs in the future.


Feature request: introduce ALBRouter, etc. to set the type of current_event in the REST API Router

Use case
In #761, APIGatewayRestResolver, APIGatewayHttpResolver, ALBResolver, and LambdaFunctionUrlResolver were created to access all properties from current_event.
I would like to access all properties from current_event in router as well.
Solution/User Experience
router = ALBRouter()

@router.get("/todos")
def get_todos():
    router.current_event.request_context.elb_target_group_arn

Alternative solutions
No response
Acknowledgment

[X] This feature request meets Lambda Powertools Tenets
[ ] Should this be considered in other Lambda Powertools languages? i.e. Java, TypeScript

hey @kt-hr, did you run into any issue when accessing current_event from a Router instance?
It should work, please let us know otherwise with a snippet we can reproduce - Test, Docs Example, API reference

Ahhh that makes more sense now - thanks for clarifying and updating the title. Let's do it - it should be fairly trivial as you can simply subclass, override the type like we did for each explicit resolver class (ALBResolver), and call out in the docs that each corresponding resolver has a Router for accurate static typing.
Feel free to create a PR and we can review in January after we're back from winter holidays.
Thank you!

Hi @kt-hr just so I can understand this problem better, why are you not using ALBResolver in your code in the first place? Why are you using the bare Router when you know you're processing ALB events?

Hi, @rubenfonseca thank you for checking.
In my use case, I want to access properties such as router.current_event.request_context.authorizer.principal_id when I split it into separate modules as in the Split routes with Router example.
Cast as typed_event = cast(APIGatewayProxyEvent, router.current_event) to enable IDE completion.
_router in APIGatewayRestResolver APIGatewayHttpResolver ALBResolver is List[Route], but _router in Router is Dict[tuple, Callable], so I think they are incompatible.

Great, I now get the problem! Will work on this today :)

@kt-hr I opened a PR to fix the UX above, please feel free to leave your comment before we merge!

@rubenfonseca thank you very much. Very helpful.
I have nothing to add to that.


Exercise14.43: Confusion with the exercise description

Exercise information
Exercise 14.43

Using library function objects, determine whether a given int value is divisible by any element in a container of ints..

Question or Bug
The answer for English version is right. "Any element in a containner", definitely we should use any_of function. But in Chinese version ( 第五版), the exercise becomes:

使用标准库函数对象判断一个给定的int值是否能够被int容器中的所有元素整除。

The translation is wrong. But under that condition, all_of function should be used.
Just for a discussion.

Yes,I think so.  感觉all_of才对


[C++][Parquet] Out of bounds access in statistics UpdateSpaced when writing optional list with null list slots

Bug that arose in https://github.com/apache/arrow/pull/3074
Reporter: Wes McKinney / @wesm
Assignee: Wes McKinney](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=wesm) / @wesm
PRs and other links:

GitHub Pull Request #3114

Note: This issue was originally created as PARQUET-1471. Please see the migration documentation for further details.

Wes McKinney / @wesm:
Issue resolved by pull request 3114
https://github.com/apache/arrow/pull/3114


Strange problem with Qt5 (QTableView class) installed by vcpkg and Windows 10

Describe the bug
This small demo Qt GUI program https://github.com/embeddedmz/QTableViewAdjustPolicyNotWorkingProperly is not showing properly under Windows 10 + vcpkg. On the same system when built using Qt Creator it does show properly (Qt version 5.15.2) : the QTableView adjust policy is working. I have also built that program under Windows 8.1 and vcpkg and it does show properly too !
I created that github demo repo because the adjust policy is not working in my application. Please look at this StackOverflow question I have posted back then : https://stackoverflow.com/questions/69042445/adjust-qtableview-height-to-its-content-few-lines
Yesterday, I removed all Qt5 packages and reinstalled them using vcpkg. I thought with the last Qt version (5.15.3) this issue will disappear but it is still there !
Environment

OS: Windows 10 Professional (up to date !)
Compiler: Visual Studio 2019 - version 16.11.11 (up to date !)
CMake: 3.19.6

To Reproduce
Steps to reproduce the behavior:

Ensure that you have Qt5 installed with vcpkg
Clone https://github.com/embeddedmz/QTableViewAdjustPolicyNotWorkingProperly
Use CMake-GUI to generate a Visual Studio solution and tell CMake to use the vcpkg toolchain file
Build the solution. The StackOverflow URL I have mentionned before contain screenshots of what you should have.

Expected behavior
The dimensions of QTableView should fit its content like the result obtained with Qt Creator or using vcpkg with Windows 8.1.

Is this correct?
qtcreator + 5.15.2 + windows 10 = OK
vcpkg + 5.15.2 + windows 10 = FAIL
vcpkg + 5.15.3 + windows 10 = FAIL
vcpkg + 5.15.2 + Windows 8 = OK
I'd say this is a Qt bug.
PS: Do you, by chance, use multi-monitor/hidpi setup?

@Osyotr Yes, that's correct.
What's a hidpi setup ? I have deployed my program build using vcpkg packages (not the little demo program) on 2 other computers (laptop and desktop) using Windows 10 and the adjust policy of the table view is not working.

@Osyotr I have just tested qtcreator + 5.15.2 + windows 8 = FAIL
:laughing:

What's a hidpi setup ?

QtCreator and CMake may use different manifests for dpiAwareness, but it is only noticable if you enabled resolution scaling in windows.
At this point I would just step into Qt code and debug it. Also, search for it in Qt bug tracker.

OK I will close this issue.

I share with you these screenshots I have made :

I have reported the bug here : https://bugreports.qt.io/browse/QTBUG-101874
To be continued...

@FrankXie05 it's better to close it after my recent discovery that this is a Qt only problem.

@embeddedmz I will continue to pay attention to the upstream feedback. :)


Package Request: Belarc Advisor

Package Requested
See https://www.belarc.com/products_belarc_advisor
Belarc Advisor v9.0 is available from downloads.com.
See https://download.cnet.com/Belarc-Advisor/3000-2094_4-10007277.html
Manifest:
Fill out as much of the manifest as you can:
Id: string # publisher.package format
Publisher: Belarc
Name: Belarc Advisor
Version: 9.0
License: Free for personal home use only
InstallerType: exe
Installers:
  - Arch: string # enumeration of supported architectures
    Url: https://files.downloadnow.com/s/software/16/32/54/74/advisorinstaller.exe?token=1599740424_f047f450d2a954ec3e2bc88f93098405&fileName=advisorinstaller.exe
    Sha256: e7cb8844770840dc36964471580aabfc8f7893432e5efc56e4b839d51a6beb6a
# ManifestVersion: 0.1.0

@BookWorm0
Hi there,
Your manifest needs some corrections.

Id: string

This part has to be Id: Belarc.Advisor

License

This part is about EULA.  If you read agreement part of setup you can see that its clearly need to be set License: Copyright to Belarc Inc.

Arch:

I think that its Arch: x86.

Sha256: e7cb8844770840dc36964471580aabfc8f7893432e5efc56e4b839d51a6beb6a

After this part we need to add Switches.
Sha256: e7cb8844770840dc36964471580aabfc8f7893432e5efc56e4b839d51a6beb6a
    Switches:
      Silent: /s
      SilentWithProgress: /s

Wise Installer only use silent switch and don't have any silent with progress switch as I'm aware of.
If you can add these you are good to go except one part. Url part have tokens. That means that after some time token expires and download link is become invalid. If you can find any direct link, you manifest file is gonna be approved when you pr. Otherwise, it's gonna be rejected probably.
Lastly, when you pr your file needs to be at this location manifests\Belarc\Advisor\9.0.yaml. Belarc\Advisor part is needs to be identical to Id part and filename must be identical to Version.
If you have any question, please ask. Have a nice day! 🥂

Thank you very much! I'm not up to speed on the mechanics of GitHub pull requests, so I wonder if it would be possible for me to put the text of the yaml here for someone more knowledgeable to push through the process.
I did find that Softpedia has a direct link to the publisher's download URL (which is also for an upgraded version), so I substituted that for the one from downloads.com.
Id: Belarc.Advisor
Publisher: Belarc
Name: Belarc Advisor
Version: 9.6
License: Copyright to Belarc Inc.
InstallerType: exe
Installers:
  - Arch: x86
    Url: https://downloads.belarc.com/advisor/advisorinstaller.exe
    Sha256: 4745abb1f4bdffce61978e47c86d4f68b14cc75335f754e94fc3760ac8874950
    Switches:
      Silent: /s
      SilentWithProgress: /s
# ManifestVersion: 0.1.0

Thanks again for all your help.

yigitemres,
I didn't see that you had created a pull request before I tried to figure out how to do one of my own. Between the two of them, I hope one gets through.
Again, many thanks for your help.

@BookWorm0 If you look at my pr and add missing keywords like description, appmoniker etc. (except homepage, homepage part cause false positive) I will happily cancel my pr. 😄
No thanks needed for me. Thanks for your contribution. 👍  Have a nice day! 🥂

@ yigitemres, After I integrate your changes, do I cancel my pending request and submit a new pull request which squashes my first commit with the changes you mentioned? Or do I submit a second pull request that is a child of the pending commit?

@BookWorm0 I look to your pr and I have to say something about it. Before creating pr, it is good practice to creating branch.
For example, if I want to add something (like Belarc Advisor) to microsoft/winget-pkgs master branch I do the following:
(I'm using magit very long time but its something like this)
cd winget-pkgs
git branch belarc-advisor-9.6
git checkout belarc-advisor-9.6
git add .\manifests\belarc\advisor\9.6.yaml
git commit
git push origin belarc-advisor-9.6

After push, you go to https://github.com/microsoft/winget-pkgs/pulls and creating your pr.

After I integrate your changes, do I cancel my pending request and submit a new pull request which squashes my first commit with the changes you mentioned? Or do I submit a second pull request that is a child of the pending commit?

Normally, you just to do changes, commit the changes and push to your origin (while in correct branch).
I put some links about branch and how to do pr:
https://www.atlassian.com/git/tutorials/using-branches
https://www.atlassian.com/git/tutorials/making-a-pull-request

Thanks for the tips. I've closed the existing request and will create a new one over the weekend.


Controlled MultiSelect Acting Up

For some reason when using a controlled multiselect the cursor in the input field gets all sort of messed up. And the values are not removed when you add a tag. https://cl.ly/0E1P0h2h1a1t
code
<MultiSelect
   placeholder="Select Roles"
   options={system && SystemAndRoles[system].map(valueToOptions) || []}
   values={roles && roles.map(valueToOptions) || []}
   disabled={!!!system}
   filterOptions={filterOptions}
   onValuesChange={(options) => sendChange('roles', options.map(o => o.value))}
   transitionEnter
   transitionLeave
   tether
/>

Not entirely sure about the big picture there, Not able to reproduce the issue here:
http://codepen.io/furqanZafar/pen/bZaBBa

@furqanZafar I know I am getting a lot of event.persist() errors do you think it could have something to do with that? I know there has been a change for that, that hasn't been pushed to NPM.

Try release 2.0.3 though I doubt that was causing any serious issues

@furqanZafar testing 2.0.3 did #80 but it did not help here sadly.

Update So as seen in the video if i type in Admin it isn't removed from the input -- i just noticed that if i click outside of the component it will then be removed? Any ideas?

I am wondering if its an issue similar to the React Input issue where when the controlled input is controlled by an outside state i.e. a store and passed as props the cursor moves. For more context I am using the FLUX arch. And storing all the changes in a store which this components parent is subscribed to.

I had a similar issue when using the multiselect advanced tags example. In my case the search text was not initially removed from the input when it was added. I'd have to click out of the input to clear it. Adding the uid function (unique id) to the multiselect component solved the issue. I overlooked that but it's in the documentation. I wonder if that will help any with your issue?

Thanks nikkipurcell I was having the exact same issue and was trying to fix it using the search and onSearchChange options (with a strange behavior).. but adding the uid function fixed all.

@nikkipurcell i am basically haveing that same issue i just tried to add the uid use this as a prop
uid={(o) => o.value + system} but it didnt seem to work @nikkipurcell  @thombuchi what did you do for your uid?

I just used uid={(item) => return item.value}  and all started working like a charm.

Can somebody explain that on what depends if the search is cleared after selecting an element from the drowdown list on the MultiSelect component.
I'm using 2.0.3 and I have a MultiSelect component for which there is a predefined option list but you can also create new "tags" and everything is working well, except that when I type in some characters into the searchbar and then select an option from the menu (or create a new tag) the search doesn't get cleared.
I tried to debug it, but I only found out that here: https://github.com/furqanZafar/react-selectize/blob/master/src/ReactSelectize.ls#L504 the @props.values does not contain the newly added tag so that find is bound to fail.
I also tried using the uid property but didn't solve it.

Ok, I found out what was my problem. Adding the initial values triggered this behavior.
There is a contradiction between the documentation and the examples. For the Multiselect API it says it has a defaultValues property but all the examples use the values property instead which is also working but triggers this side-effect I explained above.

@gergely-ujvari if you use defaultValues are you still able to clear the values via state?

No, not always for some strange reasons. Using backspace to clear an item from the search bar works fine, but I also wanted to add a little x button to all tags to be able to clear them with a click (like in the emoji example) but that doesn't work with defaultValue.

These comments finally helped me to get my MultiSelect working correctly. I wanted to have an "X" to remove options onClick as shown in the emoji example and as mentiones in several issues here.
I added a renderValues function. For me it only worked after using values instead of defaultValues. This is not well documented so I wasted a lot of hours on tracking this down.
I would suggest providing a better documentation/example for this use case. I feel a lot of people want to have a standard MultiSelect with an X button on each option.

FWIW I was seeing same behavior as OP and it was fixed (as suggested previously) by adding
uid={(i) => i.label}

to the component invocation.


skopeo: 1.0.0 -> 1.1.0

https://github.com/containers/skopeo/releases/tag/v1.1.0

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg test docker-tools


Dashboard gives an error on delegation.

On delegation, the dashboard gives an error toast notification with the following text:
gas required exceeds allowance (10000000) or always failing transaction
The number varies, but is always around 10mm.

💥🍻😬
Thanks for posting an issue!
Handful of questions:

Has this account already delegated?
Is the out-of-gas before or after submitting? (Guessing after as I don't see any failed delegation transactions, but worth checking heh.)
Is it possible the operator address has already received a delegation? (This should give a clearer error, so if it isn't it's still unexpected.)
Any chance you could pass along the transaction data for the failing transaction? Can take it via telegram/discord/keybase/email if you're not comfortable posting it here.

Conclusion (reached offline) here was that it was an operator reuse issue. We're going to need to check for that + display a proper error, preferably before hitting Metamask in the first place. May make sense as a field validation. /cc @liz-shinn @r-czajkowski @dimpar


Failed to start Docker Application Container Engine

Unit docker.service entered failed state.
Jan 14 23:37:04 VM_215_206_centos systemd[1]: docker.service failed.
Jan 14 23:49:42 VM_215_206_centos systemd[1]: Starting Docker Application Container Engine...
Jan 14 23:49:42 VM_215_206_centos dockerd[19232]: time="2017-01-14T23:49:42.976923901+08:00" level=info msg="libcontainerd: new containerd process, pid: 19239"
Jan 14 23:49:43 VM_215_206_centos dockerd[19232]: time="2017-01-14T23:49:43.995724225+08:00" level=error msg="[graphdriver] prior storage driver "devicemapper" failed: devmapper: Unable to find loopback mount for: /var/lib/docker/devicemapper/devicemapper/data"
Jan 14 23:49:43 VM_215_206_centos dockerd[19232]: time="2017-01-14T23:49:43.995872303+08:00" level=fatal msg="Error starting daemon: error initializing graphdriver: devmapper: Unable to find loopback mount for: /var/lib/docker/devicemapper/devicemapper/data"
Jan 14 23:49:43 VM_215_206_centos systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Jan 14 23:49:44 VM_215_206_centos systemd[1]: Failed to start Docker Application Container Engine.
Jan 14 23:49:44 VM_215_206_centos systemd[1]: Unit docker.service entered failed state.
Jan 14 23:49:44 VM_215_206_centos systemd[1]: docker.service failed.

Hello @xumm4011 Can we have a little bit of context here?

Which version of docker are you using? And how did you install it?
In which OS are you trying to run it?
Do you get this error in a fresh environment?

@gianarb, thanks，I uninstall the reboot of the machine has been solved

Can you close the issue @xumm4011 ? thanks


Bug: XGBoost sometimes does not use GPU when using gpu_hist.

Dear colleagues,
I have implemented a two part model for handling zero inflated continuous data. One part of my training pipeline trains an XGBoost Classifier in order to classify which of our customers are going to make an action or not (binary classification). Then a second model is trained with all of the data of customers which make an to predict the value of the action (regression). We have successfully implemented this approach and our system is already deployed in our Azure cloud environment.
We have decided to extend this system for a different use case. This time our data is a bit bigger (800K rows x 250 columns). When training my classifier I am using the following hyperparameters:
param_grid_clf = {
  'n_estimators': arguments.clf_n_estimators,
  'max_depth': arguments.clf_max_depth,
  'max_bin': arguments.clf_max_bin,
  'learning_rate': arguments.clf_learning_rate,
  'gamma': arguments.clf_gamma,
  'colsample_bytree': arguments.clf_colsample_bytree,
  'colsample_bylevel': arguments.clf_colsample_bylevel,
  'reg_alpha': arguments.clf_reg_alpha,
  'reg_lambda': arguments.clf_reg_lambda,
  'subsample': arguments.clf_subsample,
  'random_state': arguments.random_seed,
  'tree_method': 'gpu_hist',
  'single_precision_histogram': True,
  'use_label_encoder': False,
  'objective': 'binary:logistic',
  'eval_metric': 'logloss'
}

And then for the regression:
param_grid_reg = {
    'n_estimators': arguments.reg_n_estimators,
    'max_depth': arguments.reg_max_depth,
    'max_bin': arguments.reg_max_bin,
    'learning_rate': arguments.reg_learning_rate,
    'gamma': arguments.clf_gamma,
    'reg_alpha': arguments.reg_reg_alpha,
    'reg_lambda': arguments.reg_reg_lambda,
    'colsample_bytree': arguments.reg_colsample_bytree,
    'colsample_bylevel': arguments.reg_colsample_bylevel,
    'subsample': arguments.reg_subsample,
    'random_state': arguments.random_seed,
    'tree_method': 'gpu_hist',
    'single_precision_histogram': True,
    'tweedie_variance_power': arguments.reg_tweedie_variance_power,
    'objective': 'reg:tweedie',
}

To train XGBoost I am using the scikit learn API:
def build_pipeline(model, one_hot_features, numerical_features, x_paid_features, arguments, type,
                   reg_transform):

...

numeric_transformer = Pipeline(
            steps=[
                ("imputer", SimpleImputer(strategy="mean")),
                ("scaler", StandardScaler()),
                ("variance_selector", VarianceThreshold(threshold=0.03))
            ]
        )
        x_paid_transformer = Pipeline(
            steps=[
                ("scaler", StandardScaler()),
                ("variance_selector", VarianceThreshold(threshold=0.03))
            ])

        logging.info("Joining numerical and categorical transformer")

        preprocessor = ColumnTransformer(
            transformers=[
                ("numeric_normal", numeric_transformer, numerical_features),
                ("numeric_x_paid", x_paid_transformer, case_paid_features),
                ("get_dummies", categorical_transformer, one_hot_features)], remainder='drop'
        )

        pipeline = Pipeline(
            [
                ('preprocessor', preprocessor),
                ('estimator', model)
            ]
        )
return pipeline

And Im training my models as:
pipeline_hist_boost_reg = build_pipeline(xgb.XGBRegressor(**param_grid_reg),
                                        one_hot_features=one_hot_columns,
                                        numerical_features=numerical_columns,
                                        x_paid_features=historical_payments_features,
                                        arguments=arguments,
                                        type="regression",
                                        reg_transform=arguments.reg_log_transform)

scores_reg = cross_validate(pipeline_hist_boost_reg,
                                    X_train_reg,
                                    y_train_reg,
                                    n_jobs=-1,
                                    verbose=1,
                                    cv=arguments.cv_splits,
                                    error_score='raise')

The problem Im having is that when training the classifier XGBoost seems to behave properly, finalizing training in approx 40s (which is the expected order of magnitude).
2022-03-17 16:06:51,552 - __main__ - INFO - Training and cross-validating classification model
[Parallel(n_jobs=-1)]: Using backend LokyBackend with 6 concurrent workers.
572a814d2e9e4992966f31c738e88dfa000000:363:363 [0] NCCL INFO Bootstrap : Using [0]eth0:<IP_ADDRESS><0>
572a814d2e9e4992966f31c738e88dfa000000:363:363 [0] NCCL INFO NET/Plugin : No plugin found (libnccl-net.so).
572a814d2e9e4992966f31c738e88dfa000000:363:363 [0] NCCL INFO NCCL_IB_DISABLE set by environment to 1.
572a814d2e9e4992966f31c738e88dfa000000:363:363 [0] NCCL INFO NET/Socket : Using [0]eth0:<IP_ADDRESS><0>
NCCL version 2.4.8+cuda10.1
572a814d2e9e4992966f31c738e88dfa000000:361:361 [0] NCCL INFO Bootstrap : Using [0]eth0:<IP_ADDRESS><0>
572a814d2e9e4992966f31c738e88dfa000000:361:361 [0] NCCL INFO NET/Plugin : No plugin found (libnccl-net.so).
572a814d2e9e4992966f31c738e88dfa000000:364:364 [0] NCCL INFO Bootstrap : Using [0]eth0:<IP_ADDRESS><0>
572a814d2e9e4992966f31c738e88dfa000000:364:364 [0] NCCL INFO NET/Plugin : No plugin found (libnccl-net.so).
572a814d2e9e4992966f31c738e88dfa000000:361:361 [0] NCCL INFO NCCL_IB_DISABLE set by environment to 1.
572a814d2e9e4992966f31c738e88dfa000000:361:361 [0] NCCL INFO NET/Socket : Using [0]eth0:<IP_ADDRESS><0>
NCCL version 2.4.8+cuda10.1
572a814d2e9e4992966f31c738e88dfa000000:364:364 [0] NCCL INFO NCCL_IB_DISABLE set by environment to 1.
572a814d2e9e4992966f31c738e88dfa000000:364:364 [0] NCCL INFO NET/Socket : Using [0]eth0:<IP_ADDRESS><0>
NCCL version 2.4.8+cuda10.1
572a814d2e9e4992966f31c738e88dfa000000:362:362 [0] NCCL INFO Bootstrap : Using [0]eth0:<IP_ADDRESS><0>
572a814d2e9e4992966f31c738e88dfa000000:362:362 [0] NCCL INFO NET/Plugin : No plugin found (libnccl-net.so).
572a814d2e9e4992966f31c738e88dfa000000:362:362 [0] NCCL INFO NCCL_IB_DISABLE set by environment to 1.
572a814d2e9e4992966f31c738e88dfa000000:362:362 [0] NCCL INFO NET/Socket : Using [0]eth0:<IP_ADDRESS><0>
NCCL version 2.4.8+cuda10.1
572a814d2e9e4992966f31c738e88dfa000000:363:363 [0] NCCL INFO Setting affinity for GPU 0 to 3f
572a814d2e9e4992966f31c738e88dfa000000:359:359 [0] NCCL INFO Bootstrap : Using [0]eth0:<IP_ADDRESS><0>
572a814d2e9e4992966f31c738e88dfa000000:359:359 [0] NCCL INFO NET/Plugin : No plugin found (libnccl-net.so).
572a814d2e9e4992966f31c738e88dfa000000:361:361 [0] NCCL INFO Setting affinity for GPU 0 to 3f
572a814d2e9e4992966f31c738e88dfa000000:359:359 [0] NCCL INFO NCCL_IB_DISABLE set by environment to 1.
572a814d2e9e4992966f31c738e88dfa000000:359:359 [0] NCCL INFO NET/Socket : Using [0]eth0:<IP_ADDRESS><0>
NCCL version 2.4.8+cuda10.1
572a814d2e9e4992966f31c738e88dfa000000:364:364 [0] NCCL INFO Setting affinity for GPU 0 to 3f
572a814d2e9e4992966f31c738e88dfa000000:365:365 [0] NCCL INFO Bootstrap : Using [0]eth0:<IP_ADDRESS><0>
572a814d2e9e4992966f31c738e88dfa000000:363:363 [0] NCCL INFO Using 256 threads, Min Comp Cap 7, Trees enabled up to size -2
572a814d2e9e4992966f31c738e88dfa000000:365:365 [0] NCCL INFO NET/Plugin : No plugin found (libnccl-net.so).
572a814d2e9e4992966f31c738e88dfa000000:361:361 [0] NCCL INFO Using 256 threads, Min Comp Cap 7, Trees enabled up to size -2
572a814d2e9e4992966f31c738e88dfa000000:362:362 [0] NCCL INFO Setting affinity for GPU 0 to 3f
572a814d2e9e4992966f31c738e88dfa000000:365:365 [0] NCCL INFO NCCL_IB_DISABLE set by environment to 1.
572a814d2e9e4992966f31c738e88dfa000000:365:365 [0] NCCL INFO NET/Socket : Using [0]eth0:<IP_ADDRESS><0>
NCCL version 2.4.8+cuda10.1
572a814d2e9e4992966f31c738e88dfa000000:364:364 [0] NCCL INFO Using 256 threads, Min Comp Cap 7, Trees enabled up to size -2
572a814d2e9e4992966f31c738e88dfa000000:363:363 [0] NCCL INFO comm 0x562fe0932f30 rank 0 nranks 1 cudaDev 0 nvmlDev 0 - Init COMPLETE
572a814d2e9e4992966f31c738e88dfa000000:361:361 [0] NCCL INFO comm 0x558d2358e970 rank 0 nranks 1 cudaDev 0 nvmlDev 0 - Init COMPLETE
572a814d2e9e4992966f31c738e88dfa000000:364:364 [0] NCCL INFO comm 0x5647261cfef0 rank 0 nranks 1 cudaDev 0 nvmlDev 0 - Init COMPLETE
572a814d2e9e4992966f31c738e88dfa000000:359:359 [0] NCCL INFO Setting affinity for GPU 0 to 3f
572a814d2e9e4992966f31c738e88dfa000000:362:362 [0] NCCL INFO Using 256 threads, Min Comp Cap 7, Trees enabled up to size -2
572a814d2e9e4992966f31c738e88dfa000000:362:362 [0] NCCL INFO comm 0x5631bc3bb1b0 rank 0 nranks 1 cudaDev 0 nvmlDev 0 - Init COMPLETE
572a814d2e9e4992966f31c738e88dfa000000:359:359 [0] NCCL INFO Using 256 threads, Min Comp Cap 7, Trees enabled up to size -2
572a814d2e9e4992966f31c738e88dfa000000:359:359 [0] NCCL INFO comm 0x56288329a540 rank 0 nranks 1 cudaDev 0 nvmlDev 0 - Init COMPLETE
572a814d2e9e4992966f31c738e88dfa000000:365:365 [0] NCCL INFO Setting affinity for GPU 0 to 3f
572a814d2e9e4992966f31c738e88dfa000000:365:365 [0] NCCL INFO Using 256 threads, Min Comp Cap 7, Trees enabled up to size -2
572a814d2e9e4992966f31c738e88dfa000000:365:365 [0] NCCL INFO comm 0x55660581ab70 rank 0 nranks 1 cudaDev 0 nvmlDev 0 - Init COMPLETE
[Parallel(n_jobs=-1)]: Done   2 out of   6 | elapsed:   19.8s remaining:   39.7s
[Parallel(n_jobs=-1)]: Done   6 out of   6 | elapsed:   19.9s finished
2022-03-17 16:07:11,631 - __main__ - INFO - Refitting to all training data
572a814d2e9e4992966f31c738e88dfa000000:97:97 [0] NCCL INFO Bootstrap : Using [0]eth0:<IP_ADDRESS><0>
572a814d2e9e4992966f31c738e88dfa000000:97:97 [0] NCCL INFO NET/Plugin : No plugin found (libnccl-net.so).
572a814d2e9e4992966f31c738e88dfa000000:97:97 [0] NCCL INFO NCCL_IB_DISABLE set by environment to 1.
572a814d2e9e4992966f31c738e88dfa000000:97:97 [0] NCCL INFO NET/Socket : Using [0]eth0:<IP_ADDRESS><0>
NCCL version 2.4.8+cuda10.1
572a814d2e9e4992966f31c738e88dfa000000:97:97 [0] NCCL INFO Setting affinity for GPU 0 to 3f
572a814d2e9e4992966f31c738e88dfa000000:97:97 [0] NCCL INFO Using 256 threads, Min Comp Cap 7, Trees enabled up to size -2
572a814d2e9e4992966f31c738e88dfa000000:97:97 [0] NCCL INFO comm 0x55a40a9c6140 rank 0 nranks 1 cudaDev 0 nvmlDev 0 - Init COMPLETE
2022-03-17 16:07:19,276 - train - INFO - Logging CV classifier metrics in AzureML
['non-paid' 'paid' 'non-paid' ... 'non-paid' 'non-paid' 'non-paid']
2022-03-17 16:07:21,260 - train - INFO - Rescoring classifier in blind set
2022-03-17 16:07:21,262 - root - INFO - sklearn.metrics.roc_auc_score: running accelerated version on CPU

However, when training the regressor:

[Parallel(n_jobs=-1)]: Using backend LokyBackend with 6 concurrent workers.
572a814d2e9e4992966f31c738e88dfa000000:362:362 [0] NCCL INFO Setting affinity for GPU 0 to 3f
572a814d2e9e4992966f31c738e88dfa000000:362:362 [0] NCCL INFO Using 256 threads, Min Comp Cap 7, Trees enabled up to size -2
572a814d2e9e4992966f31c738e88dfa000000:362:362 [0] NCCL INFO comm 0x5631bc3bb150 rank 0 nranks 1 cudaDev 0 nvmlDev 0 - Init COMPLETE
572a814d2e9e4992966f31c738e88dfa000000:359:359 [0] NCCL INFO Setting affinity for GPU 0 to 3f
572a814d2e9e4992966f31c738e88dfa000000:359:359 [0] NCCL INFO Using 256 threads, Min Comp Cap 7, Trees enabled up to size -2
572a814d2e9e4992966f31c738e88dfa000000:359:359 [0] NCCL INFO comm 0x56288329a4f0 rank 0 nranks 1 cudaDev 0 nvmlDev 0 - Init COMPLETE
[Parallel(n_jobs=-1)]: Done   2 out of   6 | elapsed: 21.8min remaining: 43.6min
572a814d2e9e4992966f31c738e88dfa000000:361:361 [0] NCCL INFO Setting affinity for GPU 0 to 3f
572a814d2e9e4992966f31c738e88dfa000000:361:361 [0] NCCL INFO Using 256 threads, Min Comp Cap 7, Trees enabled up to size -2
572a814d2e9e4992966f31c738e88dfa000000:361:361 [0] NCCL INFO comm 0x558d23f1bb00 rank 0 nranks 1 cudaDev 0 nvmlDev 0 - Init COMPLETE
572a814d2e9e4992966f31c738e88dfa000000:364:364 [0] NCCL INFO Setting affinity for GPU 0 to 3f
572a814d2e9e4992966f31c738e88dfa000000:364:364 [0] NCCL INFO Using 256 threads, Min Comp Cap 7, Trees enabled up to size -2
572a814d2e9e4992966f31c738e88dfa000000:364:364 [0] NCCL INFO comm 0x5647266c9830 rank 0 nranks 1 cudaDev 0 nvmlDev 0 - Init COMPLETE
572a814d2e9e4992966f31c738e88dfa000000:365:365 [0] NCCL INFO Setting affinity for GPU 0 to 3f
572a814d2e9e4992966f31c738e88dfa000000:365:365 [0] NCCL INFO Using 256 threads, Min Comp Cap 7, Trees enabled up to size -2
572a814d2e9e4992966f31c738e88dfa000000:365:365 [0] NCCL INFO comm 0x556605d60ae0 rank 0 nranks 1 cudaDev 0 nvmlDev 0 - Init COMPLETE
572a814d2e9e4992966f31c738e88dfa000000:363:363 [0] NCCL INFO Setting affinity for GPU 0 to 3f
572a814d2e9e4992966f31c738e88dfa000000:363:363 [0] NCCL INFO Using 256 threads, Min Comp Cap 7, Trees enabled up to size -2
572a814d2e9e4992966f31c738e88dfa000000:363:363 [0] NCCL INFO comm 0x562fe0e37830 rank 0 nranks 1 cudaDev 0 nvmlDev 0 - Init COMPLETE
[Parallel(n_jobs=-1)]: Done   6 out of   6 | elapsed: 24.6min finished
572a814d2e9e4992966f31c738e88dfa000000:97:97 [0] NCCL INFO Setting affinity for GPU 0 to 3f
572a814d2e9e4992966f31c738e88dfa000000:97:97 [0] NCCL INFO Using 256 threads, Min Comp Cap 7, Trees enabled up to size -2
572a814d2e9e4992966f31c738e88dfa000000:97:97 [0] NCCL INFO comm 0x55a409b89290 rank 0 nranks 1 cudaDev 0 nvmlDev 0 - Init COMPLETE
2022-03-17 16:32:08,245 - train - INFO - Logging CV regression metrics in AzureML

Training takes ages!!!!
I have looking to the instance metrics and it seems there is definetely something wrong with the XGBoost regressor. For some reason when starting to train the regressor the GPU energy and usage remains flat:

With my previous training dataset (exactly same code). The usage profile was looking much different:

I am puzzled by this issue and I have trying to fix for several days now but it is very hard to understand why this is failing. Is this a problem with XGBoost? Is this problem caused maybe by the high CPU utilization?
Details of my system are as follows:
Base Container Image: mcr.microsoft.com/azureml/openmpi4.1.0-cuda11.1-cudnn8-ubuntu20.04
Python Version: 3.8.1
Conda File
channels:
  - anaconda
  - conda-forge
  - defaults
dependencies:
  - python=3.8.10
  - pip=20.1.1=py38_1
  - pip:
      - azureml-core==1.37.0.post1
      - azureml-dataset-runtime==1.37.0
      - azureml-sdk==1.37.0
      - azure-cli==2.31.0
      - azure-cli-core==2.31.0
      - azure-cli-telemetry==1.0.6
      - azure-common==1.1.27
      - azure-core==1.20.1
      - daal==2021.5.1
      - daal4py==2021.5.1
      - imbalanced-learn==0.9.0
      - joblib==1.0.1
      - numba==0.53.1
      - numpy==1.18.5
      - onnx==1.7.0
      - pandas==1.3.0
      - scikit-learn==1.0.2
      - scikit-learn-intelex==2021.5.1
      - scikit-plot==0.3.7
      - scipy==1.5.2
      - seaborn==0.11.2
      - xgboost==1.5.2

Hi, could you please share your training script that we can run and some statistic of your dataset, like the shape and sparsity?
I'm not entirely sure why are you sharing the NCCL logs?  Are you using distributed training?

Hi @trivialfis
The NCCL logs are shown automatically when I train my model. The instance Im using has 1 NVIDIA Volta V100 so I am not sure why they appear.
Regarding the statistics.
#sparsity after fit_transform and scikit learn preprocessor
>>> from numpy import count_nonzero
>>> sparsity = 1.0 - ( count_nonzero(test_a) / float(test_a.size) )
>>> sparsity
0.347205973858547

test_a.shape
(536772, 200)

Data and scripts can not be shared but I will try to get some syntetic dataset and a small version of the full code. Will that work?
BR
E

I will try to get some syntetic dataset and a small version of the full code

That would be helpful as we have to run the script before making any guess.

The NCCL logs are shown automatically when I train my model.

That's odd.  Someone set the NCCL_DEBUG environment variable.  You might want to verify other variables like CUDA_LAUNCH_BLOCKING are not being set for debugging.

I will try to get some syntetic dataset and a small version of the full code

That would be helpful as we have to run the script before making any guess.

The NCCL logs are shown automatically when I train my model.

That's odd.  Someone set the NCCL_DEBUG environment variable.  You might want to verify other variables like CUDA_LAUNCH_BLOCKING are not being set for debugging.

Hi @trivialfis,
Locking to the base image:
https://github.com/Azure/AzureML-Containers/blob/master/base/gpu/openmpi4.1.0-cuda11.1-cudnn8-ubuntu20.04/Dockerfile
Seems that you nailed with the NCCL_DEBUG, but no CUDA_LAUNCH_BLOCKING is mentioned.
One detail that I omitted is that I am using scikit learn intelex. Instead of the default functions of scikit. Should I assume that this could be a potential point of friction?

Instead of the default functions of scikit. Should I assume that this could be a potential point of friction?

I don't know.  Will take a deeper look once there's a reproducible example.

Closing as stalled. Feel free to reopen if there's any new info.


Change Deme.id to Deme.name

I think we should change the current id attribute on Deme to name. There's two main reasons for this:

Using id is intrusive for downstream implementations as they will already have some concept of a population/deme ID, and it's unlikely to match up with what we're requiring here. For example, msprime/tskit have zero-indexed integers as population IDs, and SLiM has one-indexed integers as population IDs. Neither can map the concept of "Deme id" directly into their data models, requiring icky workarounds where we add a "name" which corresponds to the Demes ID. This is both messy and will confuse users.
It's not as descriptive. "ID" has connotations of some unique, opaque identifier for a thing. We don't want people to give demes IDs, we want people to name then, in meaningful, memorable ways. Calling it a name gets this idea across much better.

Thoughts/objections?

Unfortunately, I think you're right. name would fit in better in a lot of ways.

This seemingly simple change will likely need lots of changes for related variable names and docs.

Yes, sorry. This will only get worse over time though - who wants to rip off the bandaid? I'll do the spec repo if you do demes-python?

Yes, sorry. This will only get worse over time though - who wants to rip off the bandaid? I'll do the spec repo if you do demes-python?

Deal!

OK - @molpopgen, @apragsdale any objections?

Makes sense to me.

No objections here.

On 19 Mar 2021, at 7:23, Kevin R. Thornton @.***> wrote:

Makes sense to me.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

OK, I'll sort this out here when I get a chance.


flow is confused when functions are annotated with imported types

Here is my example that works fine:
/* @flow */

export type Dictionary <value> = {[key:string]: value}
export type dictionary <value> = (data:?{[key:string]: value}) =>
  Dictionary<value>

export const dict:dictionary = data => {
  const value = Object.create(null)

  if (data != null) {
    for (let key in data) {
      if (data.hasOwnProperty(key)) {
        value[key] = data[key]
      }
    }
  }

  return value
}

const xs:Dictionary<number> = dict({x: 1})
xs.y = 3

And an example that makes flow choke:
./type.js
/* @flow */

export type Dictionary <value> = {[key:string]: value}
export type dictionary <value> = (data:?{[key:string]: value}) =>
  Dictionary<value>

./impl.js
/* @flow */

import type {dictionary, Dictionary} from "./type"

export const dict:dictionary = data => {
  const value = Object.create(null)

  if (data != null) {
    for (let key in data) {
      if (data.hasOwnProperty(key)) {
        value[key] = data[key]
      }
    }
  }

  return value
}

const xs:Dictionary<number> = dict({x: 1})
xs.y = 3

With a confusing error:
flow status
src/type.js:5
  5:   Dictionary<value>
       ^^^^^^^^^^^^^^^^^ property `y`. Property not found in possibly null value
  6:   const value = Object.create(null)
                                   ^^^^ null. See: src/impl.js:6

Found 1 error

Turns out this reduces to the same underlying issue as one of your earlier issues: #813. Fixing that one will fix this, so, closing.


bug: fix data to string from buffer for output channel

output from the testing run being printed as buffer not string for the testing rewrite.

Can you provide some steps for a Python noob to verify this?

create a test with print output
have the test be one that fails
run the test
check "python test logs"
make sure you can read the output

def test_add():
    print("text here,text here,text here,text here,text here,")
    assert add(1,2) == 4

How do you instantiate a test in python? also, are there steps to run as a test?

once you are in a python file you should see the test explorer icon come up on the side! Make sure your file is named "test_*" so it gets discovered.

you will then see all the tests found on that panel, you can click run on tests from there.


added MIT license

Seems like we should have a license file, partly because we've already been asked once for an attestation of free use (because we didn't have a license file).
A license is appropriate for software and specifications, whereas copyright (like creative commons) is more appropriate for documentation. Perhaps we need both?
I chose MIT for permissiveness. Agreed?
@jtdendunnen @ifokkema @ahwagner

This looks good to me. I agree we would also want something to specify that the documentation generated by our site code is available for free reuse. A CC0 public domain attestation in-text would be sufficient IMO.

I agree with both of you. I added CC0 to this PR. Please see PR notes at top for details and re-review.

@ifokkema and @ahwagner: I accepted your suggestions, made a minor tweak, and copied verbatim to README.md so that they were identical.  Please re-review.

Thanks all. I agree with this license. ClinGen has the same one and I think it makes the most sense.


Automator: update common-files@master in istio/istio@master

Generated by Automator - 2022-03-22T23:27:54+00:00

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

Test name
Commit
Details
Required
Rerun command

lint_istio
a4c787264064b691803cc678515f75dce5d1d0bf
link
unknown
/test lint_istio

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

/test lint_istio


Feature/41 authentication setup

#41 Authentication Setup
I've worked on the first bullet point mentioned by Duncan.
A user can log in via the button. It redirects to Auth0, and once successfully logged in the user is returned to the app. The logged in user now has a valid session and token.
The react-auth0-spa.tsx file is provided by Auth0, and creates the Auth0 client and gives access to various hooks. These are accessed by `import { useAuth0 } from './react-auth0-spa'.
I've not looked at different roles yet, but I'm assuming by assigning roles through the Auth0 API we can work out what role a user has via their token.

Apologies for the amount of commits made in order to pass the GitHub checks. It's my first time dealing with those, and next time I'll do more checks locally before creating a PR!

not had a chance to look through your whole PR yet, but something about this:

Apologies for the amount of commits made in order to pass the GitHub checks. It's my first time > dealing with those, and next time I'll do more checks locally before creating a PR!

Don't worry about number of commits, it'll force you to squash and merge here on the PR before you merge to master, so it'll be completely fine

If you want the checks to run automatically before any local commit, we've set up git pre-commit hooks that are easy to configure, there should be the instructions of 2 ways to do on the readme in the root directory. It just requires 1-2 lines to point git to the right location of the hooks

Sorry - had to fix conflicts before merge.


How to keep osb-starter-pack in sync with this library

Right now we have a lot of features developing, and I feel like the osb-starter-pack is serving as an example implementation for this library, so with that in mind we should keep the the osb-starter-pack in sync when developing new features.
We should also, as agreed here highlight breaking changes better.
I would say we write some Development section in the README. Any other suggestions are welcome!

make the osb-broker-lib project semver compliant and this will be clear to adopters. It also means you have to let go of the idea that the major and minor versions mean anything. Likely the project will get to version 52.4.0... etc


flutter pub get fails when updating flutter & dart version

To use fingerprints & biometrics, my Dart sdk version needs to be updated (>2.13.0).
flutter pub get fails for dart sdk 2.1.3  with local_auth: ^1.1.8
output:
Resolving dependencies...
The current Dart SDK version is 2.12.3.
Because encointer_wallet requires SDK version >=2.14.0 <3.0.0, version solving failed.
updating sdk version > 2.14.0 results in following error:
Because mockito 4.1.4 depends on test_api ^0.2.19-nullsafety and no versions of mockito match >4.1.4 <5.0.0, mockito ^4.1.4 requires test_api ^0.2.19-nullsafety.
And because every version of flutter_driver from sdk depends on test_api 0.4.2, mockito ^4.1.4 is incompatible with flutter_driver from sdk.
So, because encointer_wallet depends on both mockito ^4.1.4 and flutter_driver any from sdk, version solving failed.

Finally closed by #678


stop BroadcastMessage repeat CORE-3137

@maxtaco @oconnor663
This patch includes a bunch of changes to Gregor in the vendor directory as well. The point here is to use State to check for BroadcastMessage on a message already in the client's local state. We also get rid of the itemsByID map in gregorHandler and instead use the State instead. Note the use of FastLookupState, which should make it all go quickly.

@mmaxim looks like this PR makes protocol changes without regenerating the protocol files (caught by JS tests)

@cjb I didn't make any protocol changes, but I vendored in Gregor which may have changed it's own protocol since the last time we updated it. Would that affect the tests?

@mmaxim Think so (but not sure) -- cd protocol && make && git diff should show you if there are changes that need to be committed.

👍


Get_user_function_2_state - set to supported None while most likely should be all

This feature is the second relay switch available on many (if not all) Nilan units, to allow triggering from external devices, such as kitchen hoods and similar
    "get_user_function_2_state": {
        "entity_type": "binary_sensor",
        "min_bus_version": 2,
        "min_hps_bus_version": 1,
        "supported_devices": (None,),

It's currently listed as supported by NONE but I would recommend switching to all, which in a worse case scenario would be disabled as sensor by user.

Hi,
Good to know, you are probably correct. I will try to add this feature in the next release.


Cppgraphqlgen

Describe the pull request

What does your PR fix? Fixes issue #

I had a pending change to update to version 3.2.0, and I rolled in the fix for #10407 by upping the commit ID to add the source package fix.

Which triplets are supported/not supported? Have you updated the CI baseline?

I've tested x64-windows with MSVC and x64-linux with gcc 7.5.0 and 8.3.0.

Does your PR follow the maintainer guide?

Yes.

Looks like the failure for vcpkg-windows-PR-test was in an unrelated port/project (libpq).

@wravery
The CI system has some issues recently and we are fixing it.
Could you please modify the line 25 of ports/cppgraphqlgen/portfile.cmake as below:
file(INSTALL ${SOURCE_PATH}/LICENSE DESTINATION ${CURRENT_PACKAGES_DIR}/share/${PORT} RENAME copyright)

Ok

/azp run

@wravery thanks for the PR!


Potential bug found after updating to Spring Boot 3.2.X

Hi,
while updating from Spring Boot 3.1.11 to Spring Boot 3.2.5 we noticed one of our tests started failing. Looking through the changelog I haven't found anything about this behaviour change.
This is a simplified model and it seems like balance_account_sweep is not fetched after being saved.

I have created a minimal example here.
I have gone through the logs and it seems like the wrong parameter is set when the SQL statement to fetch balance account sweep is being run.

I have tried 3.3.0 (SNAPSHOT) version but the same issue still occurs.

Bummer. I'll take a look.

Turns out the problem is fixed by #1775
See my fork of your reproducer https://github.com/schauder/issue-relational-1774, especially https://github.com/schauder/issue-relational-1774/commit/f485ad4bdca4f7686fa3d919d9fa02f748ddae1d
So this is a duplicate of #1684 (potentially confunded with other issues)

Thanks for the quick help!