API routes with 3rd party dependencies fail the build

Describe the bug
Using third party libraries in nextjs API routes breaks the build. It might be related to netlify-lambda functions not bundling 3rd party libraries like firebase nicely. See the possibly related issue below.
To Reproduce
Steps to reproduce the behavior:

Create an example project
Create an API route /pages/api/form.js
Install firebase-admin and use the library inside the API route
Deploy code on netlify and see a failed build, even when the local build passes.

Expected behavior
The build should not break after adding and using 3rd party dependencies like firebase-admin in the API routes. These libraries should be accessible in the generated lambda functions.
Versions

Next.js: 10

Related issues:, there seems to be a possible workaround for netlify-lambda but not if the project uses nextjs which is the main point of the issue https://github.com/netlify/netlify-lambda/issues/112
Attached logs:
11:10:02 PM: Build ready to start
11:10:04 PM: build-image version: 2cee85eb7f808bf3b6e87378c5307f9411f0a332
11:10:04 PM: build-image tag: v3.8.0
11:10:04 PM: buildbot version: 487f6d01b44481b4d57253f3d6071f198697110f
11:10:04 PM: Fetching cached dependencies
11:10:04 PM: Starting to download cache of 460.3MB
11:10:07 PM: Finished downloading cache in 2.356543225s
11:10:07 PM: Starting to extract cache
11:10:15 PM: Finished extracting cache in 8.59295375s
11:10:15 PM: Finished fetching cache in 11.078571618s
11:10:15 PM: Starting to prepare the repo for build
11:10:16 PM: Preparing Git Reference refs/heads/main
11:10:20 PM: Parsing package.json dependencies
11:10:21 PM: Different publish path detected, going to use the one specified in the Netlify configuration file: 'out' versus '/' in the Netlify UI
11:10:21 PM: Different build command detected, going to use the one specified in the Netlify configuration file: 'npm run build' versus '' in the Netlify UI
11:10:21 PM: Starting build script
11:10:21 PM: Installing dependencies
11:10:21 PM: Python version set to 2.7
11:10:22 PM: Started restoring cached node version
11:10:24 PM: Finished restoring cached node version
11:10:24 PM: v12.18.0 is already installed.
11:10:25 PM: Now using node v12.18.0 (npm v6.14.4)
11:10:25 PM: Started restoring cached build plugins
11:10:25 PM: Finished restoring cached build plugins
11:10:25 PM: Attempting ruby version 2.7.1, read from environment
11:10:26 PM: Started restoring cached ruby version
11:10:26 PM: Finished restoring cached ruby version
11:10:28 PM: Using ruby version 2.7.1
11:10:28 PM: Using PHP version 5.6
11:10:28 PM: Started restoring cached yarn cache
11:10:28 PM: Finished restoring cached yarn cache
11:10:29 PM: No yarn workspaces detected
11:10:29 PM: Started restoring cached node modules
11:10:29 PM: Finished restoring cached node modules
11:10:29 PM: Installing NPM modules using Yarn version 1.22.4
11:10:29 PM: yarn install v1.22.4
11:10:29 PM: warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
11:10:29 PM: [1/4] Resolving packages...
11:10:30 PM: [2/4] Fetching packages...
11:10:47 PM: info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
11:10:47 PM: info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
11:10:47 PM: [3/4] Linking dependencies...
11:10:47 PM: warning "@netlify/plugin-nextjs > @sls-next/lambda-at-edge > @vercel/nft ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>11:10:47 PM: warning "@netlify/plugin-nextjs > @sls-next/lambda-at-edge > @aws-sdk/client-s3 > @aws-sdk/middleware-retry ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>11:10:47 PM: warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>11:10:47 PM: warning "firebase-admin > @firebase/database ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>11:10:47 PM: warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>11:10:47 PM: warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>11:10:47 PM: warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>11:10:54 PM: [4/4] Building fresh packages...
11:10:56 PM: success Saved lockfile.
11:10:56 PM: Done in 27.41s.
11:10:57 PM: NPM modules installed using Yarn
11:10:57 PM: Started restoring cached go cache
11:10:57 PM: Finished restoring cached go cache
11:10:57 PM: go version go1.14.4 linux/amd64
11:10:57 PM: go version go1.14.4 linux/amd64
11:10:57 PM: Installing missing commands
11:10:57 PM: Verify run directory
11:10:57 PM:
11:10:57 PM: ────────────────────────────────────────────────────────────────
11:10:57 PM:   Netlify Build
11:10:57 PM: ────────────────────────────────────────────────────────────────
11:10:57 PM:
11:10:57 PM: ❯ Version
11:10:57 PM:   @netlify/build 15.11.0
11:10:57 PM:
11:10:57 PM: ❯ Flags
11:10:57 PM:   deployId: 60eb501ad664aa00079bcebd
11:10:57 PM:
11:10:57 PM: ❯ Current directory
11:10:57 PM:   /opt/build/repo
11:10:57 PM:
11:10:57 PM: ❯ Config file
11:10:57 PM:   /opt/build/repo/netlify.toml
11:10:57 PM:
11:10:57 PM: ❯ Context
11:10:57 PM:   production
11:10:58 PM:
11:10:58 PM: ❯ Loading plugins
11:10:58 PM:    -<EMAIL_ADDRESS>from netlify.toml and package.json
11:10:58 PM:
11:10:58 PM: ❯ Outdated plugins
11:10:58 PM:    -<EMAIL_ADDRESS>latest version is 3.6.3
11:10:58 PM:      To upgrade this plugin, please update its version in "package.json"
11:10:58 PM:
11:10:58 PM: ────────────────────────────────────────────────────────────────
11:10:58 PM:   1. onPreBuild command from @netlify/plugin-nextjs
11:10:58 PM: ────────────────────────────────────────────────────────────────
11:10:58 PM:
11:10:59 PM: info  - Using webpack 5. Reason: no custom webpack configuration in next.config.js https://nextjs.org/docs/messages/webpack5
11:11:00 PM: Next.js cache restored.
11:11:00 PM:
11:11:00 PM: (@netlify/plugin-nextjs onPreBuild completed in 1.5s)
11:11:00 PM:
11:11:00 PM: ────────────────────────────────────────────────────────────────
11:11:00 PM:   2. build.command from netlify.toml
11:11:00 PM: ────────────────────────────────────────────────────────────────
11:11:00 PM:
11:11:00 PM: $ npm run build
11:11:00 PM: ><EMAIL_ADDRESS>build /opt/build/repo
11:11:00 PM: > next build
11:11:01 PM: info  - Using webpack 5. Reason: no custom webpack configuration in next.config.js https://nextjs.org/docs/messages/webpack5
11:11:01 PM: info  - Checking validity of types...
11:11:01 PM: info  - Creating an optimized production build...
11:11:35 PM: Failed to compile.
11:11:35 PM:
11:11:35 PM: ModuleNotFoundError: Module not found: Error: Can't resolve '@firebase/app' in '/opt/build/repo/node_modules/@firebase/database/dist'
11:11:35 PM: > Build error occurred
11:11:35 PM: Error: > Build failed because of webpack errors
11:11:35 PM:     at /opt/build/repo/node_modules/next/dist/build/index.js:17:924
11:11:35 PM:     at async Span.traceAsyncFn (/opt/build/repo/node_modules/next/dist/telemetry/trace/trace.js:6:584)
11:11:35 PM: npm ERR! code ELIFECYCLE
11:11:35 PM: npm ERR! errno 1
11:11:35 PM: npm ERR<EMAIL_ADDRESS>build: `next build`
11:11:35 PM: npm ERR! Exit status 1
11:11:35 PM: npm ERR!
11:11:35 PM: npm ERR! Failed at the<EMAIL_ADDRESS>build script.
11:11:35 PM: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11:11:35 PM: npm ERR! A complete log of this run can be found in:
11:11:35 PM: npm ERR!     /opt/buildhome/.npm/_logs/2021-07-11T20_11_35_296Z-debug.log
11:11:35 PM:
11:11:35 PM: ────────────────────────────────────────────────────────────────
11:11:35 PM:   "build.command" failed
11:11:35 PM: ────────────────────────────────────────────────────────────────
11:11:35 PM:
11:11:35 PM:   Error message
11:11:35 PM:   Command failed with exit code 1: npm run build
11:11:35 PM:
11:11:35 PM:   Error location
11:11:35 PM:   In build.command from netlify.toml:
11:11:35 PM:   npm run build
11:11:35 PM:
11:11:35 PM:   Resolved config
11:11:35 PM:   build:
11:11:35 PM:     command: npm run build
11:11:35 PM:     commandOrigin: config
11:11:35 PM:     environment:
11:11:35 PM:       - FIREBASE_CLIENT_EMAIL
11:11:35 PM:       - FIREBASE_DATABASE_URL
11:11:35 PM:       - FIREBASE_PRIVATE_KEY
11:11:35 PM:       - NEXT_PUBLIC_FIREBASE_PROJECT_ID
11:11:35 PM:     publish: /opt/build/repo/out
11:11:35 PM:     publishOrigin: config
11:11:35 PM:   plugins:
11:11:35 PM:     - inputs: {}
11:11:35 PM:       origin: config
11:11:35 PM:       package: '@netlify/plugin-nextjs'
11:11:35 PM: Caching artifacts
11:11:35 PM: Started saving node modules
11:11:35 PM: Finished saving node modules
11:11:35 PM: Started saving build plugins
11:11:35 PM: Finished saving build plugins
11:11:35 PM: Started saving yarn cache
11:11:35 PM: Finished saving yarn cache
11:11:35 PM: Started saving pip cache
11:11:35 PM: Finished saving pip cache
11:11:35 PM: Started saving emacs cask dependencies
11:11:35 PM: Finished saving emacs cask dependencies
11:11:35 PM: Started saving maven dependencies
11:11:35 PM: Finished saving maven dependencies
11:11:35 PM: Started saving boot dependencies
11:11:35 PM: Finished saving boot dependencies
11:11:35 PM: Started saving rust rustup cache
11:11:35 PM: Finished saving rust rustup cache
11:11:35 PM: Started saving go dependencies
11:11:35 PM: Finished saving go dependencies
11:11:35 PM: Build failed due to a user error: Build script returned non-zero exit code: 2
11:11:36 PM: Creating deploy upload records
11:11:36 PM: Failing build: Failed to build site
11:11:36 PM: Failed during stage 'building site': Build script returned non-zero exit code: 2
11:11:36 PM: Finished processing build request in 1m31.62083348s

@MKrupauskas hello! can you try adding target: "experimental-serverless-trace" to your next.config.js? that was the solution for some older issues (https://github.com/netlify/next-on-netlify/issues/68 and https://github.com/netlify/next-on-netlify/issues/66) on this plugin's predecessor.

Hi! Thanks for the help, it solved the issue. Makes me wonder why this is not the default then?

@MKrupauskas of course! and yeah, good question. the original next-on-netlify author and i once discussed defaulting to e-s-t, and we ultimately chose not to because it increased bundle sizes for people a lot. now we have esbuild as a node_bundler option in our docs to alleviate that symptom. there's also a chance we could be switching off target: serverless in the future (to target: server), which would hopefully solve some of the root issues we see with serverless.


"CheckpointLoaderSimpleWithNoiseSelect" not loading

CheckpointLoaderSimpleWithNoiseSelect node is not loading with any workflow. Using the latest version of Comfy and ComfyUI-AnimateDiff.

Are there any errors reported in your command prompt?

The comfyui-animtediff loads up fine with no errors in the command line but these are the only nodes that show up under Animatediff

Hmm, I'm unable to replicate this locally on the latest version of ComfyUI and this AnimateDiff fork. However, all the nodes you see are the ones from the original fork of this repo, and in the same order as the original fork of this repo - they should look like this in this exact order:

I know it may sound silly, but can you double check that you cloned this repo and not the original? Or that the other version is not also in your custom nodes directory?

Looking at them again, their names are also different (mine don't have spaces between Animate and Diff) - I'm now 99.99% sure you accidentally cloned the original repo instead of this fork. You can remove your current comfyui-animatediff folder and clone https://github.com/Kosinkadink/ComfyUI-AnimateDiff instead. Let me know if afterwards the nodes load fine!

I used the Comfy Manager to install this so it must not be updated yet. Thank you for chasing the issue down!

No problem! Hmm, do you know how Comfy Manager determines which repos to add to their list? My fork is a lot farther along than the original (I started working on this because I wanted it fully functional), they might just not know this exists lol

Looks like you can modify the database and then request a push request
"If you want to maintain a new DB channel, please modify the channels.list and submit a PR."

Gotcha, I'll try to replace the original AnimateDiff link in their db with mine and submit a PR. I'll mark this issue as closed for the time being, thank you for letting me know!


Failure to link with LTO: undefined reference to `libsinsp::cri::cri_interfacelibsinsp::cri::cri_api_v1alpha2::get_cri_runtime_type()

Describe the bug
I recently updated sysdig in Gentoo to 0.38.x (with libs-0.17.2) and wanted to see how it fares with LTO. I know that there are several merged/open/in-progress issues slated for 0.18 but I didn't see this one yet, so here it is.
In summary it's a failure to link the final sysdig/csysdig executables:
/usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../../x86_64-pc-linux-gnu/bin/ld: /tmp/portage/dev-debug/sysdig-0.38.1/temp/ccQH9U47.ltrans25.ltrans.o: in function `libsinsp::container_engine::cri_async_source::container_type(libsinsp::cgroup_limits::cgroup_limits_key const&) const':
<artificial>:(.text+0x220): undefined reference to `libsinsp::cri::cri_interface<libsinsp::cri::cri_api_v1>::get_cri_runtime_type() const'
/usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../../x86_64-pc-linux-gnu/bin/ld: <artificial>:(.text+0x235): undefined reference to `libsinsp::cri::cri_interface<libsinsp::cri::cri_api_v1alpha2>::get_cri_runtime_type() const'
/usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../../x86_64-pc-linux-gnu/bin/ld: /tmp/portage/dev-debug/sysdig-0.38.1/temp/ccQH9U47.ltrans26.ltrans.o: in function `libsinsp::container_engine::container_async_source<libsinsp::cgroup_limits::cgroup_limits_key>::lookup_sync(libsinsp::cgroup_limits::cgroup_limits_key const&, sinsp_container_info&)':
<artificial>:(.text+0x5385): undefined reference to `libsinsp::cri::cri_interface<libsinsp::cri::cri_api_v1>::get_cri_runtime_type() const'
/usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../../x86_64-pc-linux-gnu/bin/ld: <artificial>:(.text+0x54a1): undefined reference to `libsinsp::cri::cri_interface<libsinsp::cri::cri_api_v1alpha2>::get_cri_runtime_type() const'

How to reproduce it
Build sysdig-0.38.x+libs-0.17.2 with LTO (compile with '-O2 -flto', link with '-fuse-linker-plugin -flto=auto')
Expected behaviour
Successful link stage of the final executables.
Environment
Gentoo Linux, ~amd64 (testing)

Kernel:

6.10.0 :)

Installation method:

From source - I am the package maintainer
Additional context
This depends on optimization (likely inlining), as building with -O (instead of -O2) seems to produce executables that work. :shrug:

Hi! Thanks for opening this issue! I think this might get fixed in 0.18.0: #1895

Wonderful, thanks! I missed that PR because of the name, but I can confirm that this makes building with -O2 using gcc+LTO succed. :tada:

/milestone 0.18.0

@hhoffstaette: You must be a member of the falcosecurity/libs-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your maintainers of falcosecurity/libs and have them propose you as an additional delegate for this responsibility.

In response to this:

/milestone 0.18.0

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-sigs/prow repository.

Apparently I cannot set the milestone, so please do and close. Thanks! :heart_hands:

/milestone 0.18.0
/close

@FedeDP: Closing this issue.

In response to this:

/milestone 0.18.0
/close

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-sigs/prow repository.

/milestone 0.17.3


Fix AttributeError when sysconfig does not supply platsubdir

resolves #86

Confirm after applying this patch for v60.0.4, OBS packaging for deb/rpm with multiple OS looks good, see https://build.opensuse.org/package/show/home:alvistack/pypa-setuptools-60.0.4


enhancement: letters for DE=german

great that you did a new release.
works well with my romanian language, as i asked for by the other issue.
but: my mothertongue is german.
if someone works with an english/french/islandic/... system he may need full german letterset.
so:
may i propose to add the 4 non-english letters for german language?
here they are:
äöüß
https://en.wikipedia.org/wiki/German_language#Orthography
thank you in advance.
regards, andy

Hello, Which version are you using? German is already implemented and propose the characters you are proposing from a previous version.

Hello, no problem. Sorry I still trying to understand.
So PowerToys v0.63.0 have an issue, which Dutch as a German behavior. So it should be rename as German for the next release.
https://github.com/microsoft/PowerToys/issues/20996
Second, sorry I don't understand when you are saying because i am working on an austrian=german language system. Can you please explain that?

hello again,
(sorry for late answer)
somewhere at the WINDOWS installations process or start of system you are asked to define your system language and country:
https://support.microsoft.com/worldwide
(this is not the exact page for this question at system installation/start but similar)
after this you have defined country, language and then used keyboard of your system. this is visible by some code inside brackets looking like (xx-yy).
examples:
1- i am sitting at an system in austria with german language and keyboard showing (de-at)
2- an us-guy might sit at us-system with english language and his usual keyboard (en-us)
3- an english man will be characterized by (en-gb)
4- an canadien by (en-ca)
to 1- as long as is just use german language only i am fine. but when i need to write some romanian words i will use PowerAccent to write original romanian letters (not on austrian/german keyboards) ăâîșț
to 4- if an canadian wants to write german words he may want to use PowerAccent to be able to write äöüß
sorry for this lengthy description. now at midnight i may get complicated to explain.....
so, to answer your questions:
question 2:  answered above (i hope).
question 1:  no, everything is fine. the dutch language uses the 26 latin (=english) letters only. german uses 26 latin and the additional 4 letters, i talked....
ok, sorry, i hope you dont feel mad by such explanation (i just tried to be selected to next Nobel Price - JOKE).
regards, andy

Hello, I came back!
So the tool is not related to the choosen layout in Windows. Whenever the language, the OS...
The please confirm it, if I understand well you want to change the PowerAccent language when the layout is changed?
Also, I didn't checked this point but, if you install it and go to a different windows account, you may be able to select a different configuration.

hello,
thanks for your question. this will clear up my confusing last post.....
NO, i dont want a change of P.A. language when windows/sytem language/layout is changed.
independent of country and system language/layout and independent of keyboard-layout
(e.g. france, belgium, germany and US use different keyboards)
P.A. will just react on the selected language inside PA - a fine solution.
i do hope i made my point clear......
and YES, different accounts will/can have different settings.
i tested even multiple PA languages (consecutive used at same account) works well.
thank you very much.

Ok, so everything is ok! :)
And thanks a lot for all theses explanations.
Which you the best


Update badges to point to main, not master

Codecov Report

Merging #38 (b943a3d) into main (c48db8d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #38   +/-   ##
=======================================
  Coverage   80.99%   80.99%
=======================================
  Files           5        5
  Lines         121      121
=======================================
  Hits           98       98
  Misses         23       23

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 c48db8d...b943a3d. Read the comment docs.


[cherry-pick]  Fix recursion issue on Skip

Changes
Fix recursion issue on Skip
The pipelinerun state is made of resolved pipelinerun tasks (rprt),
which are build from the actual status of the associated taskruns.
It is computationaly easy to know if a taskrun started, or completed
successfully or unsuccessfully; however determining whether a taskrun
has been skipped or will be skipped in the pipeline run execution,
requires evaluating the entire pipeline run status and associated dag.
The Skip method used to apply to a single rprt, evaluate the entire
pipeline run status and dag, return whether the specific rprt was
going to be skipped, and throw away the rest.
We used to invoke the Skip method on every rprt in the pipeline state
to calculate candidate tasks for execution. To make things worse,
we also invoked the "Skip" method as part of the "isDone", defined as
a logical OR between "isSuccessful", "isFailed" and "Skip".
With this change we compute the list of tasks to be skipped once,
incrementally, by caching the results of each invocation of 'Skip'.
We store the result in a map to the pipelinerun facts, along with
pipelinerun state and associated dags. We introdce a new method on the
pipelinerun facts called "IsTaskSkipped".
This solution manages to hide some of the details of the skip logic from
the core reconciler logic, bit it still requires the cache to be
manually reset in a couple of places. I believe further refactor could
help, but I wanted to keep this PR as little as possible.
I will further pursue this work by revining #2821
This changes adds a unit test that reproduces the issue in #3521, which
used to fail (with timeout 30s) and now succeedes for pipelines roughly
up to 120 tasks / 120 links. On my laptop, going beyond 120 tasks/links
takes longer than 30s, so I left the unit test at 80 to avoid
introducing a flaky test in CI. There is still work to do to improve
this further, some profiling / tracing work might help.
Breaking large pipelines in logical groups (branches or pipelines in
pipelines) would help reduce the complexity and computational cost for
very large pipelines.
Fixes #3521
Co-authored-by: Scott<EMAIL_ADDRESS>Signed-off-by: Andrea Frittoli<EMAIL_ADDRESS>(cherry picked from commit fda7a81)
(cherry picked from commit 719e304)
/kind bug
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[ ] Includes tests (if functionality changed/added)
[ ] Includes docs (if user facing)
[x] Commit messages follow commit message best practices
[x] Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
Fix and issue in the pipeline state resolution which lead to very long or failed start times and high controller CPU in case of pipelines with a large number of dependencies between tasks (40+).

/approve

/lgtm


clarification on the 90-day price change

Is the 90-day applicable to existing customers only or new customers too?
Is there a way for publishers to make the price effective from today for all their new customers?

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

ID: 2ec14bb4-2e18-75a8-dffe-e96ad1ba3a7d
Version Independent ID: b684c95a-290d-1e90-63c5-e3c04e9697ed
Content: Learn about changing the prices of offers in the commercial marketplace (Partner Center)
Content Source: articles/marketplace/price-changes.md
Service: marketplace
Sub-service: partnercenter-marketplace-publisher
GitHub Login: @keferna
Microsoft Alias: keferna

@santhoshb-msft
Thanks for your feedback! We will investigate and update as appropriate.

@santhoshb-msft Thanks for your feedback.
Assigning to content author  @keferna for review.

#reassign:sarahsnow-msft

@santhoshb-msft
Is the 90-day applicable to existing customers only or new customers too? The 90 day policy is appliable to both new and existing customers. For contract-based offers, existing customers maintain their contract price for the length of the term. On renewal, their contract will us the price in effect at that time. (Link here)
Is there a way for publishers to make the price effective from today for all their new customers? No, the 90-day policy is standard for all price increases. (Link here)

Thanks @sarahsnow-msft ! #please-close


Cloudconfigupdate

Provide parameter for cnsVmSize
Added support for single master and single infra
Cleaned up Azure Cloud Provider configuration

Deployment succeeded in eastus.


[Feature Request] Please add support for font ligatures when previewing text

As far as I'm aware this is currently active in Type Ramp view


fix(engine): fix warning about redundant std::move

Signed-off-by: Luca Guerra<EMAIL_ADDRESS>
What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area engine

What this PR does / why we need it:
Fixes the following:
falco/userspace/engine/falco_engine.cpp: In member function ‘std::unique_ptr<falco::load_result> falco_engine::load_rules_file(const string&)’:
falco/userspace/engine/falco_engine.cpp:240:19: error: redundant move in return statement [-Werror=redundant-move]
  240 |   return std::move(res);
      |          ~~~~~~~~~^~~~~
falco/userspace/engine/falco_engine.cpp:240:19: note: remove ‘std::move’ call

Necessary when compiling with warnings as errors.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
I could've sworn that I saw this fix already in another PR but I can't find it and it's not in master, so if there is already another PR open please tell me and I'll close this one.
Does this PR introduce a user-facing change?:

NONE

@LucaGuerra: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: LucaGuerra
Once this PR has been reviewed and has the lgtm label, please assign andreagit97 for approval by writing /assign @andreagit97 in a comment. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 241da0d759ae4e4e0266e1485fd5d99d9f104bfc

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Enable option for gradual expanding of large children arrays

angular-tree-control has good performance on large data-sets partially because it onlyrenders children when the parent is toggled open. But it is very slow when a parent has many children (I have on the order of 500 in some instances). On top of that, when I use ng-include for each of the children labels, it causes the browser to freeze for >5 seconds while angular is compiling all 500 of the children nodes
This commit adds a 3 extra options that allow for better rendering. They are turned off by default so original behavior remains the default. The 3 options are:
    enableIntervalToggle: //allow for gradual rendering of the children. false by default
    childrenTimeInterval: //how many ms between renders
    childrenLimitInterval: //how many children to add for each render

For Example, if these were the option values:
    enableIntervalToggle: true
    childrenTimeInterval: 10
    childrenLimitInterval: 10

when a parent node is expanded, it will append 10 children nodes every 10 ms. This will not freeze the screen, and allow the user to still interact with stuff while the children are being added.
I call it enableIntervalToggle because it adds children nodes on an interval when the parent is toggled open.

Bravo on this pull request!!  Just stumbled on it today as we've been having lots of problems loading large trees.  After some trial and error with the childrenTimeInterval and childrenLimitInterval settings, we have trees loading steadily, providing visual cue to the user while still remaining responsive enough if the user wishes to do something else while the tree finishes loading.  Good stuff!


First pass at adding std deviation to measure-object

Fix https://github.com/PowerShell/PowerShell/issues/2358

Added the issue

@dfinke Thanks for your contribution!
The tests file contains multiple formatting issue. We should split code and formatting changes. So I open #4972 - please rebase after it will be merged.
We should think about optimizations. Currently we do multiple checks _measureSum, _measureAverage, _measureStdDeviation - can we refactor and optimize?

I noticed that the property StdDeviation doesn't show up in help measure. Do the maml files need to get updated and rebuilt? I tweaked one of the maml files, but no luck.

@dfinke the MAML files are generated.  You need to update the help found in https://github.com/powershell/powershell-docs

@dfinke #4972 was merged.

Maybe not for this PR - but the output of Measure-Object is not great - most of the properties are $null, and adding a new property will make it slightly worse.
I was going to propose something like what I use in my profile (see here), but that is messy and not quite right (doesn't support strict mode properly), so I might actually want a new formatting feature to make it simpler to specify optional properties, something like:
<ListItem>
    <PropertyName WhenPresent="true">Average</PropertyName>
</ListItem>

This could test if the property is present and non-null before selecting the item.

Can we create a custom PSObject with non-null properties in the cmdlet?

Another option might be to calculate average when std deviation is specified. Or use the already calculated average if the -Average switch was passed.

I'm confused. I checked the type etc. In the .cs file I took out the Math.Round.

@dfinke Please remove Math.Round because we should return honest double - the round is only formatting. We have separate formatting engine as @lzybkr mentioned above. If we want better formatting we should make it there. I believe we can skip this in the PR.
Please resolve merge conflict and address feedbacks.

@dfinke Could you please continue?

@iSazonov sorry, my free time got pulled in a different direction. I also got blocked testing. Returning the double from the cmdlet and testing it in Pester. The number looked correct from the cmdlet and in Pester to several decimal places.
I won't be able to get back to this in the near future.

@dfinke  Very sorry. Welcome back with new ideas and contributions!


window[LOADABLE_STATE] is not working

I'm trying to use this lubrary with SSR, but I keep receiving this error loadable-components state not found. You have a problem server-side. Please verify that you have calledloadableState.getScriptTag() server-side. I dive into the module and I put a console.log(window) in the loadComponents() function, the result contains this:

but if I do  console.log(window[LOADABLE_STATE]); is returning undefined.
Do you have any clue about what is happening?

@neoziro  I think I found a possible solution:
basically I change the loadComponents() to this:
function loadComponents() {   if (typeof window === 'undefined') {     throw new Error('loadable-components: loadComponentsmust be called client-side:windowis undefined');   }      return new Promise(function (resolve, reject) {     window.onload = function() {       var state = window[LOADABLE_STATE];       if (!state) {         throw new Error('loadable-components state not found. ' + 'You have a problem server-side. ' + 'Please verify that you have calledloadableState.getScriptTag()` server-side.');
}
  resolve(loadState(state));
}

});
}
`
The function has to wait for the window to be fully loaded and then I have to wrap it in a Promise, in order to return only when the window is loaded.
Do you think this is a bug or do you think I  might missing something somewhere?

Ah good workaround. In fact loadableState.getScriptTag() must be called before your loadComponents() and it should work without having to rewrite the loadComponents method.

Thanks for the reply, I moved the loadableState.getScriptTag() before importing my main js file and it is working now. By the way, I'm not 100% sure the window is gonna be loaded every time, do you think might be useful to wrap it on a promise and wait for onload event before resolving the promise?

No I don't think so. You should add scripts at the end of the body, this is the way to setup all React stuff so I think it is OK like that.


(ASC-162) Create py.test Plug-in Using Cookiecutter

Created a py.test plug-in using the following documentation:
https://github.com/pytest-dev/cookiecutter-pytest-plugin

Full disclosure, I reverted the pytest constrain commit because it turns out that I was reading the wrong requirements file. 🤦♂


Tracking Management Commands

How I would go about to track management commands and their queries too?
I'm interested of tracking the queries made by scripts, Celery workers, etc. All of these are Django standard management commands.
Do I need to run some kind of internal tracker in a parallel thread?
Here's a benchmark that I would like to see show up in the interface:
/manage.py shell -c "from django.contrib.auth.models import User; [print(list(x.username for x in User.objects.all())) for _ in range(1000)]"

This would show 1000 queries for the shell command (preferrably under a separate list in the UI).

I found the tracker.start() method from the dj-tracker middleware. I added it to my script and it seems to do something:
./manage.py shell -c "from django.contrib.auth.models import User; from dj_tracker import tracker; tracker.start(); [(list(x.username for x in User.objects.all())) for _ in range(1000)]"

'dj_tracker - INFO - Collector running
'dj_tracker - INFO - Saving latest trackings...
'dj_tracker - INFO - Collector stopped: 1000 queries tracked.

But there is nothing logged in the webpage.

Hey @gabriel-v, a way to make this happen is to call tracker.start() right before doing the queries, and optionally tracker.stop().
That's how the middleware does it but also the custom test runner (which you could use to track queries for your test suite).
So, I think:
/manage.py shell -c "from django.contrib.auth.models import User; from dj_tracker import tracker; tracker.start(); [print(list(x.username for x in User.objects.all())) for _ in range(1000)]; tracker.stop()"

should do it. Please let me know if it doesn't.
In this case, all the queries will be shown under the DummyRequest section which is more of a placeholder. We'll need a better way to distinguish where the queries come from when running the tracker outside a request.

This would show 1000 queries for the shell command (preferrably under a separate list in the UI).

That'd definitely be great.

Ah, DummyRequest! They're all there, thanks!
Another couple of questions:

how come they don't show up in the "Queries" main section?
the " Model attributes accessed " field does not expand when "Show" is clicked

how come they don't show up in the "Queries" main section?

You may be referring To this line where they're filtered out from the queryset. I feel it adds a lot of noise as it associate all queries outside a request in there and I'd have thousands of them in some situations and it's hard to find anything useful with that much data. As I mentioned earlier, we'll need a more granular way to group those queries e.g say these queries come from this test suite or from this task or just find a way to label them.

the " Model attributes accessed " field does not expand when "Show" is clicked

It means no model attributes were accessed in the sense of custom attributes or methods and such. In the script above, it seems that you're only accessing the username field which should be shown in the Field stats section when you click on the query link.

should be shown in the Field stats section when you click on the query link.

Yes, on real code it works perfectly. The table header is also a link - it's obvious now. Thanks!

You may be referring to this line

Ah, so I could patch the tracker some way after starting it, to overwrite the request path? I could set some dummy path for it, based on the management command ID & args...


Allow PipelineRuns to provide extra parameters

Expected Behavior
Imagine you have a system creating PipelineRuns automatically, and each PipelineRun uses a different Pipeline which has a different set of parameters. The system has a number of parameters it knows how to provide, e.g. the service account and url of a bucket the Pipelines can push to (but not all Pipelines need to push to a bucket).
It would be very convenient if the system creating the PipelineRuns could provide all the parameters it has available to all PipelineRuns, and the Pipelines could use the ones they need and ignore the rest.
Actual Behavior
If a PipelineRun provides extra params to a Pipeline, it will fail (99% sure!). This means that the system creating the PipelineRuns described above will need to look at each Pipeline, see what params it needs, and only provide the correct params. This feels like a level of complication that doesn't add much.
Additional Info

You can use TriggerBindings + TriggerTemplates to accomplish this today; TriggerBindings can provide params that TriggerTemplates do not use, but you have to involve an EventListener to make it work
The specific use case which is motivating me to suggest this is designing the test infrastructure fo the Tekton catalog (some details in this design doc). The proposal is using TriggerBindings + TriggerTemplates because they allow this functionality, but beyond that there is no reason to use Triggers for this and it would be nice to simplify the design by removing that component.
This might be an incremental improvement of the situation described in https://github.com/tektoncd/pipeline/issues/1294

/kind feature

/remove-lifecycle rotten
/remove-lifecycle stale
/reopen

Oh I think this is actually completed! Turns out there was NO validation at all XD in #2708  @jerop improved this so that we now check that AT LEAST the required params are provided, but the current state should be that you can provide extra
/assign jerop

Similarly, @bobcatfish does it make sense to allow TaskRuns to provide extra parameters?
We currently disallow TasksRuns from providing extra parameters -- can open a separate PR for it

We currently disallow TasksRuns from providing extra parameters -- can open a separate PR for it

my personal feeling is to avoid adding that until someone has a compelling use case for it - maybe im wrong to draw a distinction between pipelineruns and taskruns but i feel like the use case we have, where a system is generating pipelineruns, is more likely than taskruns

my personal feeling is to avoid adding that until someone has a compelling use case for it - maybe im wrong to draw a distinction between pipelineruns and taskruns but i feel like the use case we have, where a system is generating pipelineruns, is more likely than taskruns

sounds good 👍


Update the README.md with what engine metadata does

Discussed in https://github.com/rubyatscale/stimpack/discussions/14

Originally posted by iMacTia July 21, 2022
The README says that you can make your package an engine, but it's unclear what difference that actually makes.
Could this be clarified and/or documented?
Task
Update README.md

@ngan Should we describe in a bit more detail what this does?


HDDS-8828. Adapt TestBlockTokens to build with Hadoop 3.3

What changes were proposed in this pull request?
TestBlockTokens uses methods that are removed in Hadoop 3.3. This prevents ozone to build with later versions of Hadoop.
INFO    : [ERROR] /grid/0/jenkins/workspace/workspaceSOURCES/ozone/hadoop-ozone/integration-test/src/test/java/org/apache/hadoop/ozone/TestBlockTokens.java:[243,14] cannot find symbol
INFO    :   symbol:   method setID(byte[])
INFO    :   location: variable token of type org.apache.hadoop.security.token.Token<org.apache.hadoop.hdds.security.token.OzoneBlockTokenIdentifier>
INFO    : [ERROR] /grid/0/jenkins/workspace/workspace/SOURCES/ozone/hadoop-ozone/integration-test/src/test/java/org/apache/hadoop/ozone/TestBlockTokens.java:[262,14] cannot find symbol
INFO    :   symbol:   method setPassword(byte[])
INFO    :   location: variable token of type org.apache.hadoop.security.token.Token<org.apache.hadoop.hdds.security.token.OzoneBlockTokenIdentifier>

What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-8828
How was this patch tested?
Standard CI.

Thanks @swamirishi @swagle for the review.

@duongkame Ozone is built with Hadoop 3.3.5:
https://github.com/apache/ozone/blob/8ac62eb954099bb41cc90cdf9db2a664f23b739f/pom.xml#L66
Token.setID and setPassword were added by HDFS-14611 in 3.3.0.
Did you mean build with Hadoop older than 3.3?


How to install the binaries from GitHub

 Issue by 1liminal1
Tuesday Sep 05, 2017 at 02:18 GMT
Originally opened as https://github.com/plietar/librespot/issues/244

Hi guys,
How do I install this, found a fork with the compiled binaries, but no idea how to get this install on a headless Pi Zero
Thanks

i'm also trying to know this??
Anyone please share how to install i=binaries in github??

We don't provide precompiled binaries. If this ever worked by getting the artefacts from the test workflow, than that is something we don't support.


run features through encoder once or n times?

Hi @ruotianluo. Regarding this part of the code below in Transformer:
    def _prepare_feature_forward(self, att_feats, att_masks=None, seq=None):
        att_feats, att_masks = self.clip_att(att_feats, att_masks)

        att_feats = pack_wrapper(self.att_embed, att_feats, att_masks)

        if att_masks is None:
            att_masks = att_feats.new_ones(att_feats.shape[:2], dtype=torch.long)
        att_masks = att_masks.unsqueeze(-2)

        if seq is not None:
            # crop the last one
            seq = seq[:,:-1]
            seq_mask = (seq.data > 0)
            seq_mask[:,0] = 1 # bos

            seq_mask = seq_mask.unsqueeze(-2)
            seq_mask = seq_mask & subsequent_mask(seq.size(-1)).to(seq_mask)

            seq_per_img = seq.shape[0] // att_feats.shape[0]
            if seq_per_img > 1:
                att_feats, att_masks = utils.repeat_tensors(seq_per_img,
                    [att_feats, att_masks]
                )
        else:
            seq_mask = None

        return att_feats, seq, att_masks, seq_mask

    def _forward(self, fc_feats, att_feats, seq, att_masks=None):
        if seq.ndim == 3:  # B * seq_per_img * seq_len
            seq = seq.reshape(-1, seq.shape[2])
        att_feats, seq, att_masks, seq_mask = self._prepare_feature_forward(att_feats, att_masks, seq)

        out = self.model(att_feats, seq, att_masks, seq_mask)

        outputs = self.model.generator(out)
        return outputs
        # return torch.cat([_.unsqueeze(1) for _ in outputs], 1)

Why don't you run the features to the encoder first, and then duplicate them? What I mean is that the function below:
            if seq_per_img > 1:
                att_feats, att_masks = utils.repeat_tensors(seq_per_img,
                    [att_feats, att_masks]

can be placed once we finish from the encoder. That would be more computationally efficient, which is better than running the same image 5 times through the encoder. Am I right?

You are right. That should be more efficient.


Add ability to clear transaction history

Description
As a user, I want to be able to clear the transaction history, so that I can reduce clutter or reflect a new slate.
Tasks

[ ] Delete transaction history
[ ] Implement command and parser

Moving to v2.0


v02 loading

Working wrapper script to load dataproc and ES nodes.
Changes

Ported over load_dataset.py to load_dataset_v02.py with minor changes so we can make progress. Will evaluate whether it's worth it to re-write. (changes usually have v02 in name of function or in comment.

different functions to spin up and submit to dataproc using cloudtools
in v02 all args sent to load_dataset.py is sent to load_dataset_to_es.py, but with config files in v02, we only send what's needed (es_host and es_port)

Minor changes

added es_host and es_port to es task
minor bug fixes

FYI @bw2 @hanars @mike-w-wilson

@bw2 I tried downsizing the instance by changing https://github.com/macarthur-lab/hail-elasticsearch-pipelines/blob/889bd9cbc96d4a95db56972c96904e09e4c489d6/luigi_pipeline/load_dataset_v02.py#L271 to n1-highmem-2' and n1-standard-1but the script got stuck ates-data[1].is_running = None`. My guess is that it's configured somewhere to only be deployed to highmem-4 or bigger?


Is there any documentation for pspec and cspec files?

There are some refs at here. But I'm also kind of feeling confused here, as many fields are not documented..

Completely agree. I'd love to see some more extensive documentation on all of the processor-related files. The SLEIGH docs are great, but could use some more practical examples in-line vs. having to stare at the *sinc/*slaspec files for other architectures, and parse through a very large source tree to get the answers. This works, and does help with understanding the overall structure of the project, but would be much quicker if there were just a tad bit more documentation and perhaps a step-by-step overview that covers an outline for the derivation of one of the simpler existing architectures.

 I had to install docbook-xsl to get the needed files for the conversion and I also changed the path in cspec_html.xsl. Then I ran xsltproc cspec_html.xsl cspec.xml.

Thanks @rkfg
Not sure if i was just missing a package or not, but on Debian I had to modify cspec_html.xsl.  Not sure if this change is correct, but it did produce html.
-<xsl:import href="/usr/share/sgml/docbook/xsl-stylesheets/html/chunk.xsl"/>
+<xsl:import href="/usr/share/xml/docbook/stylesheet/docbook-xsl/html/chunk.xsl"/>

Yep, I did the same (and mentioned it, though it was pretty vague I admit).

Double thanks @rkfg !
On a Mac I had to just install docbook-xsl via brew and fix up the import path:
-<xsl:import href="/usr/share/sgml/docbook/xsl-stylesheets/html/chunk.xsl"/>
+<xsl:import href="/usr/local/Cellar/docbook-xsl/1.79.1/docbook-xsl/html/chunk.xsl"/>


adding shared memory support.

Following changes has been made to support shared memory:

added a new command line option : -a if set with any value it will enable shared memory mode. ex: afl-fuzz.exe -a yes
used createfilemapping calls for shared memory.
modified options if shared memory then output file will be shmem.
will be unmapped at exit.

@ifratric hopefully it should pass review and can be merged!


add aalto workshop page and map coords

please confirm that dates are correct. Location is currently TBA

Looks good to me, several comments in there.

thanks Richard! i've updated the page. I'll merge it


Put current coroutine in sleep on failed locking

Refactoring over mutex and mpsc channel implementation.
The new mutex implementation blocks the current coroutine if unable to acquire lock for SPIN_COUNT times (by default 32), which saves some CPU.
The same thing has been done for mpsc Receiver.
Resolves #2 for me.
I'm open for discussing.

Thanks for your contribution!
But here is the problem, coroutines are running in multiple threads, so

What if a coroutine A is trying to lock the mutex, and it is going to add itself to the wait list, but it does not finished yet. And in the meantime, the coroutine B who got the lock are going to release it and have already  tried to wakeup the coroutines in the wait list. Then no one will going to wake up the A, because the B has already tried, but A just add itself into the wait list.

The same problem also exists in the channel implementation. What if the consumer is going to add itself into the wait list but one of the producers has already produced data and tried to waked up the coroutines in the wait list?

When the wait list is dropped, the waiting coroutines may just be forgotten?

One suggestion, after you got the lock of the wait list, check the mutex again (by compare_and_exchange), if it succeeded, then the current coroutine won't need to add itself to the wait list.
There may be a more efficient solution ...

Thanks for reviewing.
1-2. Agree, I think we need more elegant (and correct) solution here.
3. Good catch.
I'll think about it a bit more.

I have already implemented this feature in latest commit. So I am going to close this PR.


Make sure it works with django-storages...

...especially with AWS S3

What is the status of this?

@lifenautjoe I will answer raised questions by @escaped and update this PR. Right now I am too busy...

You are absolutely right on this one @bashu .
The library indeed does not work with django storages.

The PR https://github.com/escaped/django-video-encoding/pull/19 fixes this, also processing :-)


Add required files to allow building sample  net/wifi sample for XIAO ESP32C3

Describe the bug
issuing the build command for xiao_esp32c3 for the samples/net/wifi fails to compile - although it build fine for xiao_esp32s3
In file included from /Users/robert/src/west/xiaoC32/demo/zephyr/include/zephyr/net/net_if.h:29,
                 from /Users/robert/src/west/xiaoC32/demo/zephyr/include/zephyr/net/net_pkt.h:30,
                 from /Users/robert/src/west/xiaoC32/demo/zephyr/include/zephyr/net/ethernet.h:22,
                 from /Users/robert/src/west/xiaoC32/demo/zephyr/drivers/wifi/esp32/src/esp_wifi_drv.c:14:
/Users/robert/src/west/xiaoC32/demo/zephyr/include/zephyr/net/net_l2.h:83:32: error: '_net_l2_ETHERNET_L2' undeclared here (not in a function)
   83 | #define NET_L2_GET_NAME(_name) _net_l2_##_name
      |                                ^~~~~~~~
/Users/robert/src/west/xiaoC32/demo/zephyr/include/zephyr/net/net_if.h:2831:25: note: in expansion of macro 'NET_L2_GET_NAME'
 2831 |                 .l2 = &(NET_L2_GET_NAME(_l2)),                          \
      |                         ^~~~~~~~~~~~~~~
/Users/robert/src/west/xiaoC32/demo/zephyr/include/zephyr/net/net_if.h:2875:9: note: in expansion of macro 'NET_IF_INIT'
 2875 |         NET_IF_INIT(dev_id, 0, l2, mtu, NET_IF_MAX_CONFIGS)
      |         ^~~~~~~~~~~
/Users/robert/src/west/xiaoC32/demo/zephyr/include/zephyr/net/net_if.h:2921:9: note: in expansion of macro 'Z_NET_DEVICE_INIT'
 2921 |         Z_NET_DEVICE_INIT(node_id, Z_DEVICE_DT_DEV_ID(node_id), \
      |         ^~~~~~~~~~~~~~~~~
/Users/robert/src/west/xiaoC32/demo/zephyr/include/zephyr/net/net_if.h:2934:9: note: in expansion of macro 'NET_DEVICE_DT_DEFINE'
 2934 |         NET_DEVICE_DT_DEFINE(DT_DRV_INST(inst), __VA_ARGS__)
      |         ^~~~~~~~~~~~~~~~~~~~
/Users/robert/src/west/xiaoC32/demo/zephyr/drivers/wifi/esp32/src/esp_wifi_drv.c:653:1: note: in expansion of macro 'NET_DEVICE_DT_INST_DEFINE'
  653 | NET_DEVICE_DT_INST_DEFINE(0,
      | ^~~~~~~~~~~~~~~~~~~~~~~~~

Environment
West version: v1.1.0

Page: boards/riscv/xiao_esp32c3/doc/index
Version: main
SHA-1: 7bc822df041b4a7ca316640f3f9b589a08e692c6

That was fast :) -- and excellent, thanks in advance!

Pleasure! PR submitted - thank you for the quick reply!  I just got the boards in this afternoon, so I haven’t had time to play just yet!

On Dec 5, 2023, at 2:46 PM, Benjamin Cabé @.***> wrote:
That was fast :) -- and excellent, thanks in advance!
—
Reply to this email directly, view it on GitHub https://github.com/zephyrproject-rtos/zephyr/issues/66189#issuecomment-1841509947, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABB2J6CT46L6ATNZH6MAJVDYH522LAVCNFSM6AAAAABAIHAINWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBRGUYDSOJUG4.
You are receiving this because you were mentioned.

Can you assist me on the “check-warns” failure on the PR? Let me know what needs to be done to pass this and I’ll update the PR…On Dec 5, 2023, at 2:46 PM, Benjamin Cabé @.***> wrote:
That was fast :) -- and excellent, thanks in advance!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

You need to fix the issues listed at https://github.com/zephyrproject-rtos/zephyr/actions/runs/7105827573/job/19343990483#step:9:1
So basically amending your commit message to follow the guidelines from https://docs.zephyrproject.org/latest/contribute/guidelines.html#commit-message-guidelines, making sure you have a proper sign-off entry that matches your "author" email address, and then force pushing the amended commit to your branch. Thanks!


S3 backed AWS Config server does not read default property file

Describe the bug
I created a Cloud Config Server that is backed by S3, but when I curl for the properties, it does not read the content of the default (application.yml) file. With the Git version, it reads the content of application.yml and {application-name}-{profiles}.yml one after the other. I looked at the code (AwsS3EnvironmentRepository) and I don't think it has functionality to read any files from S3 other than what than the {application-name}-{profiles}.yml file that it is being requested. Does anyone have a solution for this? The goal is to avoid common properties to be replicated per clients. Any help will be great appreciated. Thanks!

I am also facing the same issue.  We are trying to switch from using a Git-backed config service to an S3-backed service, and this is causing us issues.  It would be great if the AwsS3EnvironmentRepository could behave in the same way as the Git one.
Also - the AwsS3EnvironmentRepository does not throw any sort of exception when the bucket name is wrong, or cannot be accessed.  This is because it swallows all exceptions in the getS3ConfigFile method without logging anything and eventually just returns an empty environment.  This is not super helpful when trying to figure out environmental / permissions issues in AWS.  Could this also be improved?  Let me know if I should open a separate request.  Thanks!

This is especially important for people who are migrating from Git based configurations to S3 based configurations and they are not compatible.

I am also facing the same/similar issue where it behaves differently from NativeEnvironmentRepository. For NativeEnvironmentRepository, if a {label} is included as part of the client request the config server will return a union of configuration that is from the default properties (application.yml), service properties (service.yml) and the labelled version of those files ({label}/application.yml, {label}/service.yml). For AwsS3EnvironmentRepository it just returns the labelled version of the service properties ( {label}/service.yml ).

I am also facing the same/similar issue where it behaves differently from NativeEnvironmentRepository. For NativeEnvironmentRepository, if a {label} is included as part of the client request the config server will return a union of configuration that is from the default properties (application.yml), service properties (service.yml) and the labelled version of those files ({label}/application.yml, {label}/service.yml). For AwsS3EnvironmentRepository it just returns the labelled version of the service properties ( {label}/service.yml ).

I am also having this problem - is anyone working on this ?

I also see this problem. Is someone working to solve this bug ?! it's totally wrong behaviour and it's different than the git behaviour

Yes we're also seeing this issue, would be great to have this fixed, as the behavior is different from GIT-based.
In the meantime we are running our app with both profiles default,something and having an appName-default.yml file in S3.

Can you share sample code at least to read {application}-{profile}.properties/yml?. Thanks in advance.
No proper documentation from spring team.

Sorry I didn’t understand.. is there any sample or need to implement?.
it seems some body already done

Hello, i saw the PR still not merged. This issue still prevents us to keep configuration files in AWS S3.
Tried with current latest version 2022.0.1.
Is there any other solution?


Improve alert for failed audit logging of the shoot's kube-apiserver

How to categorize this PR?

/area audit-logging monitoring
/kind enhancement
/priority normal
What this PR does / why we need it:
Improve alert for failed audit logging of the shoot's kube-apiserver.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
/invite @wyb1 @istvanballok
Release note:

/ok-to-test


Layout Toggle?

First off, thanks for creating this plugin! It's been a great help in making my symbols page more approachable and organized.
I have an idea if you are open to it? Provide a toggle that would allow you to switch between the current 'vertical' layout and create a new 'horizontal' layout. Horizontal layout would position the symbols from left to right first, then top to bottom.

Ask and you shall receive. :)

Thanks @sonburn this is awesome!


Moved typedlist iter into njit code instead of just getitem

This is a very small change rewriting typed.List.__iter__ to use a new function _iter that implements the entire loop in njit code, creating a speed-up of 30x (probably because of less calls across the compilation boundaries).
I didn't create new unittest because I assume that typed List is already well tested and I am not changing any user facing behaviour/adding new features.

@MegaIng thank you for your contribution! The CI failure is probably unrelated so you can ignore that for now and I assume that the code is probably fine.

@MegaIng I have added it to the queue for review.

@esc No, it apparently isn't unrelated. I can reproduce this on my local machine that the change I made breaks this. I still have to figure out why. Somehow the changed implementation creates a memory leak (or it exposes an already existing leak).

@MegaIng oh good, I recently saw someone mention "master is broken b/c of pickle" so I assume this was it. Memory leaks in Numba are often caused by exceptions. Exceptions still leak memory, which is why we deactivate the leak checker explicitly in tests that check exceptions. IIRC using an iterator raises a StopIteration exception, so that may be one avenue to explore.

@esc Yes generators raise StopIteration . But as far as I can tell, this isn't a problem in test_generators.py. Is there any info somewhere on how I could debug this further?

@MegaIng there is, yes, but it is very minimal:
https://numba.pydata.org/numba-doc/dev/developer/numba-runtime.html#debugging-leaks
PS: I'm signing off now for the day.

Ok, I found the problem. It is actual not related to the code in this PR, but on how numba handles generators in general. I will create  an issue.

On the basis that this PR requires likely involved fixes to generators, I'm going to move this out of 0.54. If upstream issues are fixed then am happy to move it back into the milestone.


Servers Section not working with openapi 3.. version

When switching to OpenApi 3.0.2, it is not possible to use servers section inside specification.
https://swagger.io/docs/specification/api-host-and-base-path/

In OpenAPI 3.0, you use the servers array to specify one or more base URLs for your API. servers replaces the host, basePath and schemes keywords used in OpenAPI 2.0. Each server has an url and an optional Markdown-formatted description.

It would be nice if we can add this one (or any other OAS3 field) to swagger configuration.
Something like https://github.com/flasgger/flasgger/issues/318  can be done or even better add OPTIONAL_OAS3_FIELDS similar to OPTIONAL_FIELDS in https://github.com/flasgger/flasgger/blob/master/flasgger/constants.py.
Something like this:
in base.py:
instead of:
# enable 'components' when openapi_version is 3.*.*
if is_openapi3() and self.config.get("components"):
    data["components"] = self.config.get(
        'components'
    )

->
# enable oas3 fields when openapi_version is 3.*.*
optional_oas3_fields = self.config.get('optional_oas3_fields') or \
    OPTIONAL_OAS3_FIELDS
for key in optional_oas3_fields:
    if is_openapi3() and self.config.get(key):
        data[key] = self.config.get(key)

in constants.py:
OPTIONAL_OAS3_FIELDS = [
    'components', 'servers'
]

Does anybody know how to bypass this issue until some change is introduced to the code base?

Hi, @aleksvidak . The solution you offered seems good to me! Would you like to submit a pull request for that? I'll definitely merge it.

Sure, could you grant me rights to push to the repo?

I can definitely grant that if you want to continue to work on features related to OpenAPI 3. You can submit this pull request for now and then we can see where to go from there ☺

Merged in https://github.com/flasgger/flasgger/commit/d630b77ea53b960b0a9119af9f242d93b6e94272

hey @aleksvidak can you describe a bit how to use this? i know it's been a while, but my configuration isn't working. i'm using this:
    swagger_config = {         "openapi": "3.0.2",         "title": title,         "description": "",         "termsOfService": "",         "version": "",         "swagger_ui": True,         "servers": [             {                 "url": "https://api.example.com/v1",                 "description": "Production server (uses live data)"             },             {                 "url": "https://sandbox-api.example.com:8443/v1",                 "description": "Sandbox server (uses test data)"             }         ],         "headers": [             ('Access-Control-Allow-Origin', '*')         ],         # some UI configurations         "footer_text": "",         "hide_top_bar": True,         "doc_expansion": "list",         "components": {             "securitySchemes": {                 "authorization": {                     "type": "apiKey",                     "in": "header",                     "name": "Authorization"                 }             }         }     }
but the "servers" label doesn't show up in my apispec_1.json. when i change it to "host", it shows up (but that's swagger 2.0). curiously enough, "components" still shows up, so i'm wondering why servers doesn't.

hey @aleksvidak can you describe a bit how to use this? i know it's been a while, but my configuration isn't working. i'm using this:
    swagger_config = {         "openapi": "3.0.2",         "title": title,         "description": "",         "termsOfService": "",         "version": "",         "swagger_ui": True,         "servers": [             {                 "url": "https://api.example.com/v1",                 "description": "Production server (uses live data)"             },             {                 "url": "https://sandbox-api.example.com:8443/v1",                 "description": "Sandbox server (uses test data)"             }         ],         "headers": [             ('Access-Control-Allow-Origin', '*')         ],         # some UI configurations         "footer_text": "",         "hide_top_bar": True,         "doc_expansion": "list",         "components": {             "securitySchemes": {                 "authorization": {                     "type": "apiKey",                     "in": "header",                     "name": "Authorization"                 }             }         }     }
but the "servers" label doesn't show up in my apispec_1.json. when i change it to "host", it shows up (but that's swagger 2.0). curiously enough, "components" still shows up, so i'm wondering why servers doesn't.


please delete this issue (can't delete it)

Sorry, but Github is not advanced enough to delete issues!
https://github.com/isaacs/github/issues/253

Hehe. No worries ;-)


Build images

Added code to build a multi-arch image
Updated README and docs with info about said image (already published)

It closes #11

https://github.com/vmware-labs/wasm-workers-server/issues/11


feat:Commit Lint, Husky, ESLint, and Prettier for Code Quality and Consistency

Fixes Issue
#1075
Changes proposed
I have Install Commitlint then I have added the config file of commitlint.config.js
module.exports = {
    extends: [
        "@commitlint/config-conventional"
    ],
}

init the Eslint and  .prettierrc

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation as needed.
[x] All new and existing tests passed.

Hey @MonalikaPatnaik  I have fixed the Issue Please Review it


added custom RC server test

also ran black on the one file so that the code I wrote isn't a total mess

I guess black doesn't like single quotes

Nope, it doesn't.  One of it's opinions that I disagree with.  On the other hand, you can type single quotes and black will change them for you :wink:

Azure failed to provision an ubuntu18 runner. I'm re-running the pipeline.


[Feature request] Ability to set properites via custom links and/or data type appropriate UI elements in "Edit data" dialog

[x] I agree to follow the Code of Conduct that this project adheres to.

[x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Is your feature request related to a problem? Please describe.
This is unrelated to any problem.
Describe the solution you'd like
It would be nice if they could be used to set an element's properties (data) too.
I understand that the UI for manipulating properties is separate on purpose, but some simple manipulation would be very useful: for example a way to increment/decrement numerical values at the click of a button, or to update a certain property to contain the current date.
Reason being: give the user a quick and easy way to change document version numbers, last update dates, etc.
Describe alternatives you've considered

The only viable alternative, currently, is to click "Edit data" and replace the entire value, which is rather error prone.
A possible alternative to shapes calling custom links which, in turn, change properties would be to allow data types for properties, and display appropriate controls  in the "Edit data" UI  (e.g. date picker or increment/decrement arrows).

Additional context
Screencap of the document properties

Screencap of the properties being used in text labels and refresh/increment buttons (desired feature)

Mockup of possible alternative

Yes Please!
Since i've not found any issues or discussions on the topic, may I piggy back on this request to also include an "IMPORT" button that provides the user a dialog box that allows data fields to be pasted in and imported in the same format it can be exported?
Thank you!

What about embed mode protocol that would allow host app to provide custom dialog?


chore(deps): upgrade runtime dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-runtime-dependencies-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2276

Questions ?
Please refer to the Backport tool documentation


BOT

I know this is petty, but can you add an if statement during client loading to check if it's a bot and set it to a citizen. (I'm trying some animations:))

Look through these two functions. Both have checks that stop them from running at all if the player is a bot. The gamemode is not designed to support bots.
https://github.com/LouisK130/Orange-Cosmos-Roleplay/blob/master/ocrp/gamemode/server/player.lua#L272-L413


[beta] the second flexbox challenge also has an issue

I just completed the second flexbox challenge
Css Flexbox: Adding Flex Superpowers to the Tweet Embed
http://beta.freecodecamp.com/en/challenges/css-flexbox/adding-flex-superpowers-to-the-tweet-embed
However it doesnt make any sense as to what the lesson is exactly...
I guess what I am saying is it should have been a different or simple demonstration on the phone

@tommygebru - I think the original point of this challenge was partly to introduce the 'real world' tweet embed example (which has a lot of code), and partly to apply the display: flex concept introduced in the prior 'box' challenge. (You probably noticed the alternating pattern of these first challenges.) The change campers make here would be more obvious if the code loaded with the challenge, and updated when they added their changes. Right now, the mobile phone output only loads when the tests are run (this is a known issue tracked over in #12807).
If you reset your code, run tests (to show the initial view of the tweet embed), make changes, and run tests again, it's a bit more clear what's happening. It's not an ideal workflow, but hopefully the code loading issue is addressed soon 👍


VPS Ram requirement with 1.4

RancherOS Version: (ros os version)
1.4
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
Vultr.com 1GB VPS instance
Using iPXE boot for ROS 1.3 works as expected and leads to a functioning VPS. Doing the same using the latest build or 1.4 leads to a Kernel panic during init expansion that I believe stems from too high Ram usage for a 1G instance. I am unable to SSH in (obviously), and the console screen is too small to capture the relevant text exactly.

We added more features in 1.4, which caused it to need more memory when booting up.
The next release will optimize this memory problem.
Current memory requirements are mentioned here: https://rancher.com/docs/os/v1.x/en/#hardware-requirements


Compilation Warning with Visual Studio C++ v142 (2019)

We are getting the following compilation warnings 200+ times:
C:\Program Files (x86)\Windows Kits\10\Include\10.0.17763.0\ucrt\corecrt_memory.h(76,5): warning C5105: macro expansion producing 'defined' has undefined behavior (compiling source file D:\a\1\bld\ITK\Modules\ThirdParty\ZLIB\src\itkzlib-ng\chunkset.c) [D:\a\1\bld\ITK-build\Modules\ThirdParty\ZLIB\src\itkzlib-ng\zlib.vcxproj] [D:\a\1\bld\ITK.vcxproj]
C:\Program Files (x86)\Windows Kits\10\Include\10.0.17763.0\ucrt\corecrt_memory.h(76,5): warning C5105: macro expansion producing 'defined' has undefined behavior (compiling source file D:\a\1\bld\ITK\Modules\ThirdParty\ZLIB\src\itkzlib-ng\adler32.c) [D:\a\1\bld\ITK-build\Modules\ThirdParty\ZLIB\src\itkzlib-ng\zlib.vcxproj] [D:\a\1\bld\ITK.vcxproj]
C:\Program Files (x86)\Windows Kits\10\Include\10.0.17763.0\ucrt\corecrt_wstring.h(573,5): warning C5105: macro expansion producing 'defined' has undefined behavior (compiling source file D:\a\1\bld\ITK\Modules\ThirdParty\ZLIB\src\itkzlib-ng\chunkset.c) [D:\a\1\bld\ITK-build\Modules\ThirdParty\ZLIB\src\itkzlib-ng\zlib.vcxproj] [D:\a\1\bld\ITK.vcxproj]
These warnings are occurring on the SimpleITK Dashboard with "Visual Studio 16 2019" and the "v142" toolset.
I don't seem to be able to find VS 2019 v142 on the ITK dashboard.

I normally use VS2019, and ITK compiles without these warnings. Maybe you have a different warning level? I took a look at chunkset.c, which is pretty small, and I could not find a possible offender. Do you have a direct link to that dashboard entry? I could not find it.

Is v141 or v142 the default with VS2019?
I unaware of additional warning flags being passed to ITK. The external project file is here: https://github.com/SimpleITK/SimpleITK/blob/master/SuperBuild/External_ITK.cmake
Here are the warnings:
https://open.cdash.org/viewBuildError.php?type=1&buildid=7583963
And the two builds which get the warnings are in the continuous section:
https://open.cdash.org/index.php?project=SimpleITK&date=2021-11-20

v142 is the default for VS2019.
@N-Dekker did you encounter something like this?

I haven't seen this warning before. But it appears reproducible at https://godbolt.org/z/E3nWod3xz
Having the example code from https://docs.microsoft.com/en-us/cpp/error-messages/compiler-warnings/c5105?view=msvc-170 as follows:

// C5105.cpp
// To demonstrate the warning,
// compile by using: cl /EHsc /experimental:preprocessor /DTEST C5105.cpp
// To fix the warning, change the DEFINED_TEST
// definition to the commented version.

#include <iostream>

#define DEFINED_TEST defined TEST
//#if defined TEST
//#define DEFINED_TEST 1
//#else
//#define DEFINED_TEST 0
//#endif

int main()
{
#if DEFINED_TEST  // C5105
    std::cout << "TEST defined\n";
#else
    std::cout << "TEST not defined\n";
#endif
}

Hope that helps!

But I don't see where such a pattern occurs in zlib. Can you point me to that please?

Not sure, but maybe the following line of code triggered the warning:

#if defined(_CRT_INTERNAL_NONSTDC_NAMES) && _CRT_INTERNAL_NONSTDC_NAMES

It's at line 76 of corecrt_memory.h and line 573 of corecrt_wstring.h at C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\ucrt on my laptop.

Yes, but which line in zlib triggers that?

This CMake issue looks similar:
https://gitlab.kitware.com/cmake/cmake/-/issues/21446
It may be issues related to the Windows SDK version 10.0.17763.0.  This is the version which Azure DevOps is using currently.
I could not reproduce with a new VM with a download of VS2022 ( assuming it is using a very new SDK ).

Yes, but which line in zlib triggers that?

@dzenanz  According to the message reported by Bradley:

compiling source file D:\a\1\bld\ITK\Modules\ThirdParty\ZLIB\src\itkzlib-ng\chunkset.c

A newer version of corecrt_memory.h, from C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\ucrt says at line 18:

#pragma warning(disable: _UCRT_DISABLED_WARNINGS)

I guess that may have disabled their own warning!

I am going to consider a bug in the "10.0.17763.0" version of the Windows 10 Kit, which is resolved by latter versions, and not an ITK bug.


Convert URL.pathname to proper File Path

Could not get this plugin to work on Windows and I got the following error:
11:47:01 [ERROR] [redirect-from] ENOENT: no such file or directory, mkdir 'C:\C:\dev\docs\node_modules\.astro'

Seems like config.cacheDir.pathname is used directly but this is unfortunatly not a valid file path in Windows.
The value config.cacheDir is a URL and pathname for me in this case is \C:\dev\docs\node_modules\.astro, which isn't correct since it starts with a leading backslash.
I added a conversion to a proper file path with with url.fileURLToPath and now it works as expected.
Was unfortunatly not able to run the the npm scripts since they seemed to be expecting a unix environment.

Awesome, thank you for this. Had a go at fixing the respective test, would you mind updating your branch with those changes in test/index.test.ts and push again? That shoud male that test succeed.
Need to update the options mock like so:
const hookOptionsMock = {
  logger: mockLogger,
  config: {
    cacheDir: new URL('file:///node_modules/.astro/')
  },
  command: 'dev',
  updateConfig: vi.fn()
} as unknown as HookOptions

And the should handle redirects found scenario test needs those fs mocks as it looks like, right before calling await initPlugin(hookOptionsMock):
vi.spyOn(fs, 'existsSync').mockReturnValue(false)
vi.spyOn(fs, 'mkdirSync').mockImplementation(() => undefined)

There we go, the tests are updated and they pass locally for me at least.
Had to change the file path in hookOptionsMock to file://node_modules/.astro/ (with two slashes instead of three), but it should still be a valid file URI in unix?

haha, gotta love OS differences. We have to construct that cache path better for the mock:
const cacheDirPath = url.pathToFileURL(path.resolve('node_modules/.astro/')).href

const hookOptionsMock = {
  ...
  config: {
    cacheDir: new URL(cacheDirPath)
  },
...
}

Totally fine to just get tests to pass if you say that actual implementation works properly. More holistic approach would be to unify implementation & mock with utility methods but that quickly gets out of scope and this whole cache dir was not supposed to be configurable anyway

Third time's a charm!

Excellent, that's perfect now! Will be part of v1.3.0. Thanks again for the patience and your contribution.
(coverage task failure can be ignored as it's caused by secrets not passed to forks)


Usage of goreleaser and godownloader

Just my curious question
Why not use go releaser for

Automated generation of platform specific binaries
Automated generation of change log

And go downloader for

Automated generation of install script
Publishing in CDN

IMHO makes managing releases a lot easier. Also several repos are now using
it (Eg golangci-lint)

sure but we already have a solution that predates go releaser and works.
I looked into their toolset and the nfpm tool they have I want to look into closer because it might be able to get rid of the ruby dependency in our build, which is always welcome

@casualjim Looks like you've just started using goreleaser with v0.21.0. Can we close this?

I should remove that file, I didn't use it I was just giving it another go but forgot the file was still there

ok. I thought it could be a possible cause to why v0.21.0 failed to push our artifacts on bintray....


Updating external dependencies

New versions:
SystemReflectionMetadataPackageVersion
SystemThreadingChannelsPackageVersion
SystemRuntimeCompilerServicesUnsafePackageVersion
SystemDataSqlClientPackageVersion
SystemSecurityCryptographyCngPackageVersion
SystemServiceProcessServiceControllerPackageVersion
SystemDiagnosticsEventLogPackageVersion
SystemSecurityPrincipalWindowsPackageVersion
SystemNumericsVectorsPackageVersion
SystemCollectionsImmutablePackageVersion
SystemBuffersPackageVersion
SystemDiagnosticsDiagnosticSourcePackageVersion
MicrosoftNETCoreDotNetAppHostPackageVersion
SystemNetHttpWinHttpHandlerPackageVersion
SystemIOPipelinesPackageVersion
SystemThreadingTasksExtensionsPackageVersion
SystemValueTuplePackageVersion
SystemSecurityPermissionsPackageVersion
MicrosoftNETCoreAppPackageVersion
SystemComponentModelAnnotationsPackageVersion
MicrosoftExtensionsDependencyModelPackageVersion
MicrosoftCSharpPackageVersion
SystemMemoryPackageVersion
SystemThreadingTasksDataflowPackageVersion
SystemTextEncodingsWebPackageVersion
SystemNetWebSocketsWebSocketProtocolPackageVersion
SystemSecurityCryptographyXmlPackageVersion
MicrosoftWin32RegistryPackageVersion

This version causes a bunch of compiler errors in .NET Framework projects, such as
error CS0012: The type 'Object' is defined in an assembly that is not referenced.

This is why: https://github.com/dotnet/core-setup/pull/4060#issuecomment-384368199

I've opened https://github.com/aspnet/Universe/issues/1120 to track the work on our side before we can take this.

Closing this in favor of the maestro one.


Make the home page dynamic

Dynamic home page the shows our doctors, articles, departments
Dynamic links based on user types to go to portals
Dynamic login/register, profile links based on logged in state

Estimated time: 1 Day


Related projects with graphical interfaces

https://github.com/gmiaslab/ClassificaIO also wraps scikit-learn
https://orange.biolab.si/ is a full data mining toolkit

Microsoft has drag and drop machine learning interfaces, described here:

https://docs.microsoft.com/en-us/azure/machine-learning/service/how-to-create-portal-experiments
https://studio.azureml.net/

Turi Create doesn't seem to have a graphical interface, but it was recommended to me by a machine learning novice.  This could be a potential resource for someone who can write Python code and wants more wrappers and assistance than scikit-learn provides.

DataChat: https://datachat.ai/

A good summer exercise may be to spend a little time with each of these tools to see whether we would recommend them to participants once they have learned basic ML concepts.

anaconda just released Voilà - according to the one line summary

Voilà turns Jupyter notebooks into standalone web applications.

Here are the links https://blog.jupyter.org/and-voilà-f6a2c08a4a93
and
https://anaconda.org/conda-forge/voila

I looked at Voilà briefly, and my first impression is that this is different from Binder because it strips away all of the code and displays only the output of code cells.  That output can include interactive plots and widgets, creating a simple interactive interface for users who do not want to see the code.  The example also looks like it is running locally (as opposed to Binder running the notebook remotely), but I didn't check carefully.
Voilà could be appealing for our demo notebook.  It would be an intermediate layer between the ml4bio GUI and the full notebook with scikit-learn code.
If Voilà runs locally, we would still need users to configure a conda environment on their machine.  One appealing aspect of Binder and similar services is they do not have any local dependencies.

Yes, it looks like it runs locally.
Makes sense! I will play around with some of these this week.

@cmilica found https://www.streamlit.io/  It builds interactive machine learning apps with compact Python scripts.  The gallery has lots of cool examples.

Milica has also been looking into interactive visualizations that teach machine learning concepts, such as https://thomas-tanay.github.io/post--L2-regularization/

Galaxy-ML is a relevant resource:

Preprint: https://doi.org/10.1101/2<IP_ADDRESS>445
Website with training: https://galaxyproject.org/community/machine-learning/
GitHub: https://github.com/goeckslab/Galaxy-ML

Gradio generates GUIs for machine learning models

Intro at https://twitter.com/abidlabs/status/1281385978507206662
https://www.gradio.app/

PennAI has a graphical interface and supports AutoML:

http://epistasislab.github.io/pennai
https://doi.org/10.1093/bioinformatics/btaa698

Thought this was really cool https://climateprimer.mit.edu/

@cmilica found http://www.r2d3.us/ with great visualizations for decision trees and bias-variance tradeoffs.


LXC not starting after clone

Hello!
have a problem with resource "proxmox_lxc".
Seems to be that after clone LXC not starting. Also no errors.
Even "start = true" is set.
But its working with
ostemplate   = "local:vztmpl/alpine-3.14-default_20210623_amd64.tar.xz" and it starts normally
my config:
resource "proxmox_lxc" "vms" {
  target_node  = "home"
  hostname     = "lxc-basic${count.index+1}"
  password     = "dfgdgffdg$"
  unprivileged = true
  clone = "104"
  count = 1
  full = true
  start = true
}

#711 related


Long-Range Scanners

I have Imperial Veterans Expansion Pack with 2 of the Long-Range Scanners cards set up in my inventory. When highlighted, it shows that I have two of them, but when trying to include them on a ship, they are greyed out.

What ship are you trying to equip it to?  It can only be equipped on ships that have both a Torpedo and a Missile slot.

You're right ... when I picked a ship with both, it worked. Thanks for your
trouble! Love the site.
On Wed, Jul 27, 2016 at 2:36 PM, Geordan Rosario<EMAIL_ADDRESS>wrote:

What ship are you trying to equip it to? It can only be equipped on ships
that have both a Torpedo and a Missile slot.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/geordanr/xwing/issues/345#issuecomment-235695707, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ATuvRosVEe3C5QRcOH1hJIQTwZwPlHpfks5qZ7NFgaJpZM4JWgT_
.

--
Don Vicha
675 Western Ave
Glen Ellyn, Illinois 60137
630-346-4217
My personal blog http://greathotshave.tumblr.com
My professional blog http://diehard03.blogspot.com/


🐛 In the demo, using the navigation.navigate('CodeScannerPage') to enter the page will not scan the content

What's happening?
Navigation.navigate ('CodeScannerPage ') method will not immediately work when entering the scanning page. If the screen is locked and the page is re-entered from the background, it will trigger an update to initiate scanning recognition
pdating CameraSession Configuration...
Reproduceable Code
type Props = NativeStackScreenProps<Routes, 'CodeScannerPage'>
export function CodeScannerPage({ navigation }: Props): React.ReactElement {
  // 1. Use a simple default back camera
  const device = useCameraDevice('back')

  // 2. Only activate Camera when the app is focused and this screen is currently opened
  const isFocused = useIsFocused()
  const isForeground = useIsForeground()
  const isActive = isFocused && isForeground && isCameraInitialized

  // 3. (Optional) enable a torch setting
  const [torch, setTorch] = useState(false)
  const [isCameraInitialized, setIsCameraInitialized] = useState(false);
  // 4. On code scanned, we show an aler to the user
  const isShowingAlert = useRef(false)
  const onCodeScanned = useCallback((codes: Code[]) => {
    console.log(`Scanned ${codes.length} codes:`, codes)
    const value = codes[0]?.value
    if (value == null) return
    if (isShowingAlert.current) return
    showCodeAlert(value, () => {
      isShowingAlert.current = false
    })
    isShowingAlert.current = true
  }, [])

  // 5. Initialize the Code Scanner to scan QR codes and Barcodes
  const codeScanner = useCodeScanner({
    codeTypes: ['qr', 'ean-13'],
    onCodeScanned: onCodeScanned,
  })

  const onInitialized = useCallback(() => {
    setIsCameraInitialized(true);
}, []);

  return (
    <View style={styles.container}>
      {device != null && (
        <Camera
          style={StyleSheet.absoluteFill}
          device={device}
          isActive={ isFocused && isForeground && isCameraInitialized}
          codeScanner={codeScanner}
          torch={torch ? 'on' : 'off'}
          onInitialized={onInitialized}
          enableZoomGesture={true}
        />
      )}

      <StatusBarBlurBackground />

      <View style={styles.rightButtonRow}>
        <PressableOpacity style={styles.button} onPress={() => setTorch(!torch)} disabledOpacity={0.4}>
          <IonIcon name={torch ? 'flash' : 'flash-off'} color="white" size={24} />
        </PressableOpacity>
      </View>

      {/* Back Button */}
      <PressableOpacity style={styles.backButton} onPress={navigation.goBack}>
        <IonIcon name="chevron-back" color="white" size={35} />
      </PressableOpacity>
    </View>
  )
}

Relevant log output
2023-12-26 15:55:26.054 12468-12585 CameraSession           com.mrousavy.camera.example          I  Updating CameraSession Configuration...
2023-12-26 15:55:26.055 12468-12585 CameraSession           com.mrousavy.camera.example          I  Updating CameraSession Configuration...
2023-12-26 15:55:26.060 12468-12585 CameraSession           com.mrousavy.camera.example          I  Successfully configured Camera #0!
2023-12-26 15:55:26.063 12468-12585 CameraSession           com.mrousavy.camera.example          I  Configuring Session for Camera #0...
2023-12-26 15:55:26.067 12468-12585 CameraSession           com.mrousavy.camera.example          I  Adding 1280 x 720 CodeScanner Output in Format #35...
2023-12-26 15:55:26.164 12468-12585 CameraSession           com.mrousavy.camera.example          I  Camera Session android.hardware.camera2.impl.CameraCaptureSessionImpl@dab1a73 has been closed!
2023-12-26 15:55:26.164 12468-12585 CameraSession           com.mrousavy.camera.example          I  Successfully configured Session with 1 outputs for Camera #0!
2023-12-26 15:55:26.165 12468-12585 CameraSession           com.mrousavy.camera.example          I  Successfully updated CameraSession Configuration! isActive: false
2023-12-26 15:55:26.166 12468-12585 CameraSession           com.mrousavy.camera.example          I  Configuring Session for Camera #0...
2023-12-26 15:55:26.169 12468-12585 CameraSession           com.mrousavy.camera.example          I  Adding 1920 x 1080 Preview Output...
2023-12-26 15:55:26.173 12468-12468 CameraView              com.mrousavy.camera.example          I  Updating CameraSession...
2023-12-26 15:55:26.386 12468-12585 CameraSession           com.mrousavy.camera.example          I  Updating CameraSession Configuration...
2023-12-26 15:55:26.387 12468-12585 CameraSession           com.mrousavy.camera.example          I  Successfully configured Session with 1 outputs for Camera #0!
2023-12-26 15:55:26.387 12468-12585 CameraSession           com.mrousavy.camera.example          I  Successfully updated CameraSession Configuration! isActive: false
2023-12-26 15:55:26.393 12468-12585 CameraSession           com.mrousavy.camera.example          I  Successfully updated CameraSession Configuration! isActive: true

Camera Device
{"minFps": 1, "minISO": 100, "photoHeight": 3024, "photoWidth": 4032, "pixelFormats": [Array], "supportsDepthCapture": false, "supportsPhotoHdr": false, "supportsVideoHdr": false, "videoHeight": 96, "videoStabilizationModes": [Array], "videoWidth": 160}], "hardwareLevel": "full", "hasFlash": true, "hasTorch": true, "id": "0", "isMultiCam": false, "maxExposure": 200, "maxZoom": 10, "minExposure": -200, "minZoom": 1, "name": "BACK (0)", "neutralZoom": 1, "physicalDevices": ["wide-angle-camera"], "position": "back", "sensorOrientation": "landscape-right", "supportsFocus": true, "supportsLowLightBoost": false, "supportsRawCapture": true}

Device
Android 11
VisionCamera Version
3.6.17
Can you reproduce this issue in the VisionCamera Example app?
I didn't try (⚠ your issue might get ignored & closed if you don't try this)
Additional information

[ ] I am using Expo
[ ] I have enabled Frame Processors (react-native-worklets-core)
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

Android 11

which phone?

Android 11

which phone?

honor  play5
android 12

Same here, xiaomi redmi note 10. Delaying the setIsCameraInitialized(true); for 2000 ms works, but seems hacky.

Working on a fix for this issue here: https://github.com/mrousavy/react-native-vision-camera/pull/2494 👀
Still in development, so don't test yet. Long way to go, this is a really complicated issue (as you can see in the changes/Files of that PR)...

Just released VisionCamera 3.9.0-beta.1, which includes the big PersistentCaptureSession PR that aims to fix all the blackscreen issues.... :eyes::tada:
You can try that new beta out yourself and let me know if you still encounter blackscreen issues. I'll continue to test on more devices in the meantime, organize the code a bit better, and then I'll tackle the preview stretching, focus, and flash issues!
If that fixes the blackscreen issues for you, please consider sponsoring me on GitHub to say thanks! ❤


[core] add autonumber_reset (closes #29158)

Before submitting a pull request make sure you have:

[x] Searched the bugtracker for similar pull requests
[x] Read adding new extractor tutorial
[x] Read youtube-dl coding conventions and adjusted the code to meet them
[ ] Covered the code with tests (note that PRs without tests will be REJECTED)
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[ ] Improvement
[ ] New extractor
[x] New feature

Autonumber Reset
I encountered an issue while attempting to use autonumber recently. I was attempting to download some playlists from the YouTube channel Crash Course. For each series, they have a preview video that functions as an "Episode 00". With one playlist, this is simple enough to fix. You simply add --autonumber-start 0 and use %(autonumber)02d for episode indexing.
However, issues arise when passing in multiple playlists. Youtube-DL supports a variable number of URL's to be processed. When multiple playlists are passed in, the autonumber does not reset between operands. This makes sense if you're passing in individual video URL's and want them to be indexed, but for me it is important that each series have it's own indexing starting from 00.
For additional context, I am downloading these videos to be used with a media server that references TVDB. Having the "first" episode (i.e. the second video in the playlist) indexed as 01 is important to ensure that the metadata is mapped properly. So, %(playlist_index)02d doesn't satisfy my use case, and %(autonumber)02d in its current state requires me to pass in each playlist as a separate youtube-dl command.
I could have solved this problem by creating a PowerShell wrapper that batched a series of playlists and sent separate youtube-dl commands for each, but it seemed like others might benefit from having the ability to reset this counter in the future. I tested the reset functionality via local execution, but did not see an applicable space for autonumber tests in the current suite.
This is my first open-source PR submission, so feedback and advice would be appreciated. Thank you!

@dstftw Hi there! Is there something else I should be doing before this PR is further reviewed? Should it be closed and another be opened? I'm not sure what the feedback process is for this repo


BaseUri is not initialized in some constructors of SubscriptionClient (ARM)

Some of the ARM SubscriptionClient constructors leave the baseUri null while others set it to a default value of "https://management.azure.com/".
Shouldn't all constructors that don't accept baseUri as a parameter set it to a default value?  Since the BaseUri property is read-only there's no other way to specify a value.

@bvirkler The underlyingissue is that the constructors which do not take required parameters (credentials) should be protected.  This is fixed in the newly generated clients using autorest https://github.com/Azure/autorest, you should see new clients using the new generator in the coming months that will solve the issue.