Uncaught Error: The specified module could not be found./?~\AppData\Local\Temp\Rar$EXa1244.38...

[Enter steps to reproduce:]

...
...

Atom: 1.57.0 ia32
Electron: 9.4.4
OS: Unknown Windows version
Thrown From: Atom Core
Stack Trace
Uncaught Error: The specified module could not be found.
\?\C:\Users\iana.dandis\AppData\Local\Temp\Rar$EXa1244.38812\Atom\resources\app.asar.unpacked\node_modules\keyboard-layout\build\Release\keyboard-layout-manager.node
At electron/js2c/asar.js:140

Error: The specified module could not be found.
\\?\C:\Users\iana.dandis\AppData\Local\Temp\Rar$EXa1244.38812\Atom\resources\app.asar.unpacked\node_modules\keyboard-layout\build\Release\keyboard-layout-manager.node
    at process.func [as dlopen] (electron/js2c/asar.js:140:31)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:1034:18)
    at Object.func [as .node] (electron/js2c/asar.js:149:18)
    at Module.load (internal/modules/cjs/loader.js:815:32)
    at Module._load (internal/modules/cjs/loader.js:727:14)
    at Function.Module._load (electron/js2c/asar.js:769:28)
    at Module.require (/app.asar/static/index.js:72:46)
    at require (internal/modules/cjs/helpers.js:74:18)
    at customRequire (~/AppData/Local/Temp/Rar$EXa1244.38812/Atom/resources/app/static/<embedded>:1:802772)
    at get_KeyboardLayoutManager (~/AppData/Local/Temp/Rar$EXa1244.38812/Atom/resources/app/static/<embedded>:14:2893541)
    at get_manager (~/AppData/Local/Temp/Rar$EXa1244.38812/Atom/resources/app/static/<embedded>:14:2893643)
    at Object.getCurrentKeyboardLayout (~/AppData/Local/Temp/Rar$EXa1244.38812/Atom/resources/app/static/<embedded>:14:2893769)
    at e.keystrokeForKeyboardEvent (~/AppData/Local/Temp/Rar$EXa1244.38812/Atom/resources/app/static/<embedded>:14:1118316)
    at KeymapManager.keystrokeForKeyboardEvent (~/AppData/Local/Temp/Rar$EXa1244.38812/Atom/resources/app/static/<embedded>:11:1224088)
    at KeymapManager.handleKeyboardEvent (~/AppData/Local/Temp/Rar$EXa1244.38812/Atom/resources/app/static/<embedded>:11:1222073)
    at WindowEventHandler.handleDocumentKeyEvent (~/AppData/Local/Temp/Rar$EXa1244.38812/Atom/resources/app/static/<embedded>:11:286551)

Commands

Non-Core Packages

Thanks for taking the time to contribute!
We noticed that this is a duplicate of https://github.com/atom/atom/issues/21285. You may want to subscribe there for updates.
Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.


Compatibility with Bazel 0.8

Starting from Bazel 0.8 support for set constructors will be removed completely. Currently one of the dependencies, grpc, is not compatible with this: tensorflow uses an old version of it. grpc has already been fixed, please update your dependencies to use grpc with the following commit included: https://github.com/grpc/grpc/pull/12571/commits/759c7029b18f8bbcf6a6399d512abed8b6e12436
grpc is loaded as a patched_http_archive, you can also update the file third_party/grpc/grpc.patch to include the one-line patch from the commit above if it's more convenient.
Just updating grpc to head or to to the commit that has the fix is not trivial because third_party/grpc/grpc.patch then has to be updated as well. and as I don't know why those changes were necessary I don't know if I should keep, update or delete them when I update grpc.

@gunan @yifeif can you update GRPC or include the patch?

Looks to me like @jhseu created this patch file.
Jonathan, if we upgrade grpc to head, do we still need the patch file?
What is your recommendation here?

My understanding is that we no longer need the patch if we upgrade gRPC. @vjpai was going to look at upgrading it, but if someone wants to work on it, feel free (but please chat with me since there are a few things to keep in mind).

An update: Bazel 0.7 has been released, the next version (0.8) will be cut in the beginning of November (probably November 6th) and it will be incompatible with the version of GRPC currently used by Tensorflow. It would be nice to update it before November so that repositories that depend on Tensorflow (for example, TF_serving and TF_models) can be updated too.

Please internally reach out to @jhseu to discuss how we should upgrade.

The grpc upgrade is in progress at #13958

It seems that grpc has already been updated, therefore I'm closing this pull request.


fix(auth): clean all storage when logging out

fix #4546

Original issue closed via https://github.com/portainer/portainer/issues/4546#issuecomment-781630855


[AIRFLOW-1227] Remove empty column on the Logs view

Dear Airflow maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following

AIRFLOW-1227 Remove empty column on the Logs view

Description

[x] Here are some details about my PR, including screenshots of any UI changes:
First column on the Logs view is redundant and should be removed.
Before:

Now:

Tests

[ ] All existing tests passing.

Codecov Report

Merging #2310 into master will increase coverage by 0.03%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2310      +/-   ##
==========================================
+ Coverage    69.2%   69.24%   +0.03%
==========================================
  Files         144      144
  Lines       11024    11025       +1
==========================================
+ Hits         7629     7634       +5
+ Misses       3395     3391       -4

Impacted Files
Coverage Δ

airflow/www/views.py
68.09% <100%> (+0.02%)
:arrow_up:

airflow/jobs.py
74.51% <0%> (+0.4%)
:arrow_up:

Continue to review full report at Codecov.

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


1-0-17 MC1.19.4 Incompat with Physics Mod

Indium keep rendering the "original" block models while Physics Model adds "new".
It looks like you have two blocks one over the other.
E.G. When you open a door, the default model and behaviour happens, but also the Physics Mod model and behavior.

Which version of Physics Mod are you using? 3.0.4 added support for Sodium 0.4.11.

Please downgrade to Sodium 0.4.10 and Indium 1.0.15.


Web Application throws Errors on Submit

Hi,
I am running the Web App (app.yml) and whenever I´ve uploaded a file and click on submit I can see the following output at the webserver:
Traceback (most recent call last):
  File "/opt/resemble-enhance/.venv/lib/python3.11/site-packages/gradio/queueing.py", line 456, in call_prediction
    output = await route_utils.call_process_api(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/resemble-enhance/.venv/lib/python3.11/site-packages/gradio/route_utils.py", line 232, in call_process_api
    output = await app.get_blocks().process_api(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/resemble-enhance/.venv/lib/python3.11/site-packages/gradio/blocks.py", line 1522, in process_api
    result = await self.call_function(
             ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/resemble-enhance/.venv/lib/python3.11/site-packages/gradio/blocks.py", line 1144, in call_function
    prediction = await anyio.to_thread.run_sync(
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/resemble-enhance/.venv/lib/python3.11/site-packages/anyio/to_thread.py", line 56, in run_sync
    return await get_async_backend().run_sync_in_worker_thread(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/resemble-enhance/.venv/lib/python3.11/site-packages/anyio/_backends/_asyncio.py", line 2134, in run_sync_in_worker_thread
    return await future
           ^^^^^^^^^^^^
  File "/opt/resemble-enhance/.venv/lib/python3.11/site-packages/anyio/_backends/_asyncio.py", line 851, in run
    result = context.run(func, *args)
             ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/resemble-enhance/.venv/lib/python3.11/site-packages/gradio/utils.py", line 674, in wrapper
    response = f(*args, **kwargs)
               ^^^^^^^^^^^^^^^^^^
  File "/opt/resemble-enhance/app.py", line 24, in _fn
    wav1, new_sr = denoise(dwav, sr, device)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/resemble-enhance/.venv/lib/python3.11/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/opt/resemble-enhance/resemble_enhance/enhancer/inference.py", line 29, in denoise
    enhancer = load_enhancer(run_dir, device)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/resemble-enhance/resemble_enhance/enhancer/inference.py", line 16, in load_enhancer
    run_dir = download()
              ^^^^^^^^^^
  File "/opt/resemble-enhance/resemble_enhance/enhancer/download.py", line 40, in download
    run_command(["git", "-C", str(REPO_DIR), "lfs", "pull"], "Failed to pull latest changes, please try again.")
  File "/opt/resemble-enhance/resemble_enhance/enhancer/download.py", line 17, in run_command
    raise RuntimeError(msg) from e
RuntimeError: Failed to pull latest changes, please try again.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/opt/resemble-enhance/.venv/lib/python3.11/site-packages/gradio/queueing.py", line 501, in process_events
    response = await self.call_prediction(awake_events, batch)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/resemble-enhance/.venv/lib/python3.11/site-packages/gradio/queueing.py", line 465, in call_prediction
    raise Exception(str(error) if show_error else None) from error
Exception: None

How can I solve this?
Thanks in advance.

It seems git-lfs is missing, you may install it here.
You may also update to the latest version: pip install resemble-enhance --upgrade --pre, which no longer uses git-lfs.

Thanks, I´ve upgraded to the pre version, but there is a new error:
Traceback (most recent call last):
  File "/opt/resemble-enhance/.venv/lib/python3.11/site-packages/gradio/queueing.py", line 456, in call_prediction
    output = await route_utils.call_process_api(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/resemble-enhance/.venv/lib/python3.11/site-packages/gradio/route_utils.py", line 232, in call_process_api
    output = await app.get_blocks().process_api(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/resemble-enhance/.venv/lib/python3.11/site-packages/gradio/blocks.py", line 1522, in process_api
    result = await self.call_function(
             ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/resemble-enhance/.venv/lib/python3.11/site-packages/gradio/blocks.py", line 1144, in call_function
    prediction = await anyio.to_thread.run_sync(
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/resemble-enhance/.venv/lib/python3.11/site-packages/anyio/to_thread.py", line 56, in run_sync
    return await get_async_backend().run_sync_in_worker_thread(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/resemble-enhance/.venv/lib/python3.11/site-packages/anyio/_backends/_asyncio.py", line 2134, in run_sync_in_worker_thread
    return await future
           ^^^^^^^^^^^^
  File "/opt/resemble-enhance/.venv/lib/python3.11/site-packages/anyio/_backends/_asyncio.py", line 851, in run
    result = context.run(func, *args)
             ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/resemble-enhance/.venv/lib/python3.11/site-packages/gradio/utils.py", line 674, in wrapper
    response = f(*args, **kwargs)
               ^^^^^^^^^^^^^^^^^^
  File "/opt/resemble-enhance/app.py", line 24, in _fn
    wav1, new_sr = denoise(dwav, sr, device)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/resemble-enhance/.venv/lib/python3.11/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/opt/resemble-enhance/resemble_enhance/enhancer/inference.py", line 29, in denoise
    enhancer = load_enhancer(run_dir, device)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/resemble-enhance/resemble_enhance/enhancer/inference.py", line 16, in load_enhancer
    run_dir = download()
              ^^^^^^^^^^
  File "/opt/resemble-enhance/resemble_enhance/enhancer/download.py", line 40, in download
    run_command(["git", "-C", str(REPO_DIR), "lfs", "pull"], "Failed to pull latest changes, please try again.")
  File "/opt/resemble-enhance/resemble_enhance/enhancer/download.py", line 17, in run_command
    raise RuntimeError(msg) from e
RuntimeError: Failed to pull latest changes, please try again.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/opt/resemble-enhance/.venv/lib/python3.11/site-packages/gradio/queueing.py", line 501, in process_events
    response = await self.call_prediction(awake_events, batch)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/resemble-enhance/.venv/lib/python3.11/site-packages/gradio/queueing.py", line 465, in call_prediction
    raise Exception(str(error) if show_error else None) from error
Exception: None

what's the output of pip show resemble-enhance?

This is the output:
Name: resemble-enhance Version: 0.0.2.dev240104122303 Summary: Speech denoising and enhancement with deep learning Home-page: https://github.com/resemble-ai/resemble-enhance Author: Resemble AI Author-email<EMAIL_ADDRESS>License: Location: /opt/resemble-enhance/.venv/lib/python3.11/site-packages Requires: celluloid, deepspeed, gradio, librosa, matplotlib, numpy, omegaconf, pandas, ptflops, resampy, rich, scipy, soundfile, tabulate, torch, torchaudio, torchvision, tqdm Required-by:
currently I am installing the app like python3 -m pip install resemble-enhance --upgrade --pre and I am starting the web app like python3 app.py. Can the missing .venv cause this problem?

oic, you are running under the repo folder and it uses the old code (not the one newly installed with pip). you can try to git pull the latest version, or goto another folder.

Sorry, it´s not clear for me already. I´ve used git pull now and restarted the webserver, but it´s throwing the same error. How can I run the app in a different folder after git pull?

Are there any folder, which I have to create manually, where the files are stored?

This solution does not work for me, I have the same problem. Is there any update regarding this issue?


advisor: Extend Vulnerability by the properties summary and description

Add the properties and implement the mapping for all advise providers where applicable.
See individual commits.
Context: #5593.

@oheger-bosch due to the revert commit, your approval should be mendatory to merge this as per our discussion about Bosch's internal setup.


[ci:component:github.com/gardener/hvpa-controller:v0.2.5->v0.3.0]

Release Notes:
Minor bug fix: Use vpa scale policies correctly

Change handling of LimitsRequestsGapScaleParams: Use `max` of value and percentage gaps, instead of `min`

Now HVPA doesn't take VPA recommendations into account if VPA condition has `ConfigUnsupported`, `ConfigDeprecated` or `LowConfidence` set to `true`

Removing "Temporary/fast fix to enable scale down even if vpaWeight == 0" as we have better ways to optimise cost now

Ignore `minChange` configuration while overriding scale up stabilisation. This ensures that full VPA recommendations are applied in case the target pods are OOMKilled or restarted due to livenessProbe failure, no matter what.

Consider HPA to be limited if we have seen oomkill or liveness probe fails already. This change makes HVPA controller scale the app vertically more actively, ignoring the HPA's status condition type `ScalingLimited`.

Consider HPA scale out to be limited in case, overrideScaleUpStabilization is set in the status and hpa weight is 0 so that full VPA recommendation is immediately applied.

Add ci master build status and go report card badges

/invite @ggaurav10 @amshuman-kr

#2521 should go with this

I was about to ask this. Wouldn't it be better to update #2521 with this PR's changes to make the commits atomic?

good idea. updated #2521
we can close this once #2521 is merged.

good idea. updated #2521
we can close this once #2521 is merged.

#2521 already supersedes this PR. I am closing this one.

@rfranzke Should i copy the release notes there too?

Yep, I copied them.

/close


SystemLoad?

What does the number in System Load actually mean/represent? and what is considered a high number? Thanks!

Hi,
multiply the number by 100 and you get the load percentage.


fix update-to-head script with correct make target for zz_fileystem_generated.go

This PR is to accommodate this upstream change:
https://github.com/knative/func/pull/1554/files#diff-76ed074a9305c04054cdebb9e9aad2d818052b07091de1f20cad0bbac34ffb52L91

/approve
/lgtm


Experiment with Travis

Please don't accept this yet, it is not done.
I am experimenting with fixing #18 and #19.

This should be done now. Feel free to merge @brinchj.


devicelab mac-28  bot is down

The host is non-responsive. ssh is down. Hard rebooted the host, and it seems to be up and running.


Integration Test - Release - 2019/05/08 12:56:50

Auto create for integration test. IssueCommandFlow

#pri1

Just type '#backlog'

#pri2

#backlog

#assign PRMergerTest1

#assign NonAllowedUser

NonAllowedUser is not a valid GitHub ID, or is not a collaborator on this repo.

#reassign PRMergerTest2

GitHub user PRMergerTest1 has been removed from the MicrosoftDocs organization, so they were automatically removed as an assignee.

#reassign NonAllowedUser

NonAllowedUser is not a valid GitHub ID, or is not a collaborator on this repo.

#please-close


Forces

Dear developpers
Is there a method implemented in ferminet to calculate the interatomic forces? For example, as explained in https://doi.org/10.1063/5.0112344.
Kind regards
Tom

I recommend you to use https://github.com/bytedance/netobs. Besides, some new force estimators are introduced in https://doi.org/10.1039/D4FD00071D.
(I'm the author of https://github.com/bytedance/netobs and if you have any problems, feel free to raise issues there.)

Sorry, we don't have forces implemented right now. Pull requests are always welcome.


Limit concurrent requests to prevent OOM (ACM-3065)

Related Issue: https://issues.redhat.com/browse/ACM-3065
Description of changes

Adds middleware to check for pending requests and available resources before accepting a new request.
Add SlowLog to log slow requests and adjust logs verbosity.

/lgtm
/hold

/unhold

/lgtm


Write "What do i do next text"

https://docs.google.com/document/d/16Bc1iw8-pxCfTL2aqNHATDuPD1DsgllLc7iwv5WNS4Q/edit

love love love this idea. I'm not sure about moving it up on the page (since i like the idea that it happens after you scroll through the results) but I think let's move on implementing it and seeing what we think.
Another question I have is about layout - maybe we lay it out more in bullet points than as a paragraph of text - but let's take a look first and then we can do design.
Assigning to Jay for implementation - Jay let us know if you have questions.

all set except for the couple things i left comments on


Initial attempt at documenting public quinn-proto API

This is just an initial kick to make the docs for quinn-proto a bit more friendly (motivated in part by comments about this comparing us to quiche) for folks that need/want the lower-level API.

Squashed everything and hid the EndpointEvent variants. Can you reapprove?


Mot Redesign

Here is the behemoth rework of MOT aiming to resolve many issues. (See https://docs.google.com/presentation/d/1bNXGpQdqgWz-IgGOfJATT5zYnNhfSuKW-RWNk4eQrck/edit#slide=id.g2a76d4f4e02_0_0)
A separate PR for the configs will be made in that repo.
MOT is coded as a set of frame chunks. Each chunk is a series of frames. A frame can be an image frame (e.g., instructions) or a trial frame. A trial can be an example trial, a practice trial, or a test trial. This design was inherited from the previous version of MOT but is hopefully more clear/explicit now.
The task has been split out into three modules: task, frame, and animate. Task controls the overall flow and is what actually inherits from the task class. Frame is responsible for visual presentation to the screen. Animate is the logical model of the movement of circles in a trial frame. In other words, frame should handle flashing circles and actually drawing them to the screen whereas animate handles the logical model of each circle and manages HOW their positions update.
The old code for generating circle paths for a trial has been refactored into animate.StepwiseAnimator. I think it makes sense to keep this around in case we ever want to write a script to generate new trials. Or, at the very least we should preserve it until the PR is squashed and merged before removing it so that it remains in the commit history.
The creation of an update script to update old outcome/result CSV files can be handled as a separate PR.

LGTM. I have some concerns about the compatibility of the task param logging with the coming changes since the new model is quite different, but we will see how it goes when it's time to merge my code.

I agree. The current approach is to log the contents of the complex/nested types as JSON.


Bump addressable version

Addressable 2.5+ adds support for ruby 2.4 which also is a dependency in other gems.

@mogox how does previous constraint '>= 2.3.6' prevent your form using Addressable 2.5?

It didn't! Sorry about that, it was another dependency that was stopping my bundle.  Thanks for the quick response


Moving the contributing.md file to the docs/ directory

refs #573

[x] Changelog amended
[x] Tests in @brunobord's fork.

A contributing.md file at the root or in .github/ will trigger a specific display for contributors.
https://docs.github.com/en/free-pro-team@latest/github/building-a-strong-community/setting-guidelines-for-repository-contributors

right from this page:

To help your project contributors do good work, you can add a file with contribution guidelines to your project repository's root, docs, or .github folder.

I've tested it on my personal copy and apparently it shows the same interface: https://github.com/brunobord/workalendar/issues/new

Damn, I think my brain just forgot how to brain for a minute :D
Sorry about that :)


handle 0 futures in all()

if we pass in 0 futures to an AllOfAdapter, we should complete immediately
@ijuma @cmccabe

Good PR @norwood


Allow lowercase protein sequences

Done in https://github.com/Lab41/hypothesis-bio/commit/27f821bd6eba0b03f4dd235a7261c47b5e292cfb


Support for DIA-NN output from FragPipe

added support for DIA-NN output from FragPipe (always named diann-output/diann-output.tsv; NB the msfragger-diann test is not actually from FragPipe, it's a copy of the diann-swath test files with different names)

@brendanx67 Need this for FragPipe to be able to use SkylineCmd.


nsfw image check

This pull request is related to issue #2 - Add support for disallowing people from uploading NSFW pictures with the help of NSFWJS library.
Implementation: The idea is to use this client-side library to check the file being uploaded and verify whether the image has any NSFW content in it. The NSFW model predicts the class and if the predicted class has NSFW content, the file should be stopped from getting uploaded.
The Upload.io React Uploader didn't have a onValidate hook before and I got in touch with the founder @ljwagerfield who was super quick to add the onValidate hook and release the feature to production in a matter of a couple of hours (now that is quick product delivery!)
Using the onValidate hook and the NSFWPredictor.isSafeImg() in case there is a file that is not safe, it will not get uploaded to UploadIo and the user will receive a message stating "Detected an NSFW image"

Previously before the onValidate hook was added to the Upload-io uploader, I was using a Tailwind Class to showcase an error for the detection of NSFW images. I can still add that if you think it is needed @Nutlope

About the model: The ML model files (the model weights + model.json ) are currently hosted on an AWS S3 bucket, if needed I can share those with you and you could host them on Upload.io. Let me know if that works. The model URL is used in the nsfwCheck.ts file.
'https://nsfw-model-1.s3.us-west-2.amazonaws.com/nsfw-predict-model/',

This is great work @shivaylamba 🎉
We're looking into adding NSFW filtering server-side to Upload.io later this year, and this is an excellent stopgap solution.
Thank you again for the feature suggestion re. onValidate: file => Promise<string | undefined> for async custom file validation pre-upload 💪
All the best!

I have tested the NSFW image check on my website, https://restorephotos.app/, and it appears to be functioning properly.

Excellent work @shivaylamba, I'd like to merge this. Mind addressing the conflicts and we can get it merged?

This is now merged as a part of #24. Thanks all!


[ASTGen] Introduce nullable variants of bridging wrappers

Based on top of #69325
For nullable nodes, introduce both a non-null and nullable variant of the bridging wrapper. This allows us to annotate the necessary parameters as nullable, but keep the returns of the bridged createParsed methods non-null.

@swift-ci please test


Enhancement and update version

Install all dependencies inside a node_modules folder inside of grunt-twig-render folder, instead of installing on the root?
Can you update to the latest version of twig?
Thanks in advance. :+1:

Hi, I've just released v1.7.3 that uses twig 0.8.8.
What do you mean by installing inside the grunt-twig-render directory? How do you do that? What's the benefit?

Hi, thanks for the quick response :airplane: and update :smiley:

What do you mean by installing inside the grunt-twig-render directory?

I was wrong thinking that had to do with installing the plugin, but I have seen figuring out which is the npm@3 new version behavior http://blog.npmjs.org/post/110924823920/npm-weekly-5
Once again, thank you very much per create and maintaining this plugin.


jfrparser-cli: add cli that formats json

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@korniltsev addressed comments and more


Typo in first paragraph

In the first paragraph, the link "declarative access to a wide variety of Azure and and third-party services" contains twice the word "and". Should be replaced by "declarative access to a wide variety of Azure and third-party services".
Thanks!

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

ID: a8a0ac96-e410-b481-9fdb-90d827a98935
Version Independent ID: 6a133cdf-a66a-9807-d431-2e0ae43b253b
Content: Azure Functions Overview
Content Source: articles/azure-functions/functions-overview.md
Service: azure-functions
GitHub Login: @mattchenderson
Microsoft Alias: glenga

@benbeaudry Thanks for the feedback! We are currently investigating and will update you shortly.

@benbeaudry Thanks for reporting this and helping us drive improvements towards MS Docs! I have created a PR that corrects the typo.
We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Improve & update intrinsics documentation

Trying to navigate the docs for intrinsics can be difficult, especially for trying to write portable intrinsics code. Here are a list of suggested improvements:

[ ] Make relation between /arch:AVX2 and FMA more explicit; it is mentioned only in passing here.
[ ] Mention conditions / implications for emitting F16C / POPCNT instructions. @walbourn clarified here that F16C has no direct relation to /arch:AVX2 (while  the only previous reference I found - also by him - seemed to imply that)
[ ] Specify SSE-support detection on 64-bit targets. This page explains that just for  _M_IX86_FP, which is however only applicable to 32bit targets
[ ] Update intrinsics support page. The page wrongly claims [2] (=supported only on Intel processors) for everything upwards of (and including) AVX.
[ ] Mention lack of operator overloads (+, -, *, / etc.) for __m128 / __m256.

Background: trying to get an existing unix-y library using intrinsics (e.g. __SSEx__, __FMA__, __F16C__, -mpopcnt, etc.) is painful.

@h-vetinari
I appreciate that you've had some difficulty finding the information you need. You've got a large list of suggestions and improvements here, in content that is little visited, and hence a low priority for us. Only two people work on the C/C++ and Assembler docs, and we're pretty busy just keeping up with the regular changes in the tools and libraries. Frankly, the fastest way to see the changes you want in this content is to make them yourself. Fortunately, it's not terribly difficult to edit the markdown sources and make a pull request. We're delighted to review and edit such contributions. And thanks for your suggestions on improving the content.

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


Implemented client side send operation

Implemented send operation for client side, send operation was introduced with the LwM2M 1.1 standard.
This PR is based on work from @sbertin-telular, specifically on send branch: https://github.com/sbertin-telular/wakaama/tree/send
In this PR a bug that caused a memory leak has been fixed: https://github.com/sbertin-telular/wakaama/pull/1

I'm closing this PR because I deleted a part of the history of this branch that shouldn't have been deleted, I'll send a new PR


[FlatButton] Expose enhancedButton as RaisedButton does.

Raised Button access their internal enhancedButton object exposing it trough "container" variable.
Flat button should do the same as well.

Exposing EnhancedButton by "enhancedButton" object. EnhancedButton does the same with the actual button node. In order to be able to access Enhanced button to setKeyboardFocus() or EnhancedButton.button to focus().

[no ] PR has tests / docs demo, and is linted.
[ yes] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[ ] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

Thanks for your time. From my perspective you are trying to access an internal API. I won't consider removing a ref/renaming it a breaking change.
We need another approach. I can think of providing a callback ref property. I'm wondering if you can't already do it.

I partially agree.
Look, currently you have this in RaisedButton:
/* RaisedButton */
    ref="container"

/*Then to access it you need, which is odd */
    this.refs.myRaisedButton.refs.container.setKeyboardFocus();
    this.refs.myRaisedButton.refs.container.button.focus();

see it here: https://github.com/callemall/material-ui/blob/master/src/RaisedButton/RaisedButton.js#L427
With the changes I'm proposing you will have this:
// To access the component, to me is a little less odd,
// because you're not accessing the refs of the refs
    this.refs.myFlatButton.enhancedButton.setKeyboardFocus();
    this.refs.myFlatButton.enhancedButton.button.focus();

So basically this is to give the same level of access to EnhancedButton component for FlatButton as RaisedButton has.
Making a callback ref property will break consistency between components even more. ( consistency is already broken ). If we change the way to access internals for all buttons references ( as it should be), then it will break any current implementation.
This is not a new feature, its already available for RaisedButton, but it's missing for FlatButton, This PR is to make both components equally inconsistent as they already are, but with the same level of access.
So as I see there are 4 possible ways:

Make a callback ref property for each button, for consistency (breaking current implementations).
Give the exact same kind of access to FlatButton ( ref="container").
Give the access to FlatButton but a little less odd (this PR).
Do nothing but FlatButton can't programmatically be focused as RaisedButton is.

@oliviertassinari do you agree?

I'm adding #3008 to the conversation.


[wiki migration] Web team pages

This puts the wiki pages owned by the Web team into the docs/platforms/web directory as planned in flutter.dev/go/migrate-flutter-wiki-spreadsheet
It also adds the web team label to the label bot for future PRs.
Changes to the content were only updating cross links, or link to refer to the main branch rather than master.
Remaining links to the wiki will be updated once all other pages have finished moving, they still work in the meantime.
Part of https://github.com/flutter/flutter/issues/145009
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] I followed the breaking change policy and added Data Driven Fixes where supported.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

The tree has been green for a while now, but it is not updating on Github. I am going to land this docs only change to see if it just needs a kick.


[virtualization management] standard user is missing access to multiple pages

tested as a standard user on v2.6-head (06e19b0):

projects/namespaces are not listing in the UI TypeError: Cannot read properties of undefined (reading 'namespace')

RBAC page is not populating users (expecting it to at least show current user viewing the project)

create page for cloud config templates shows the raw type, config map . This title should match the type, cloud config template

hosts page is also not displaying any information for the user

@yasker I'm pushing this out to the next version since we're out of time. Is there anything we should release note for 2.6.1?

This should be fixed by https://github.com/harvester/dashboard/pull/131 and the commit is in the upstream dashboard.


Use RethinkDB F# Driver

The RethinkDB F# driver is nearing RC; use it for data access.

This is complete; however, this work will not be released, but will serve as the starting point for v3.


Support for LSPGet API in the client interface as well as configuration of dynamic addresses on LSP

This pull request adds support for

the LSPGet API in the client's interface. The implementation is already present, but the API was not being exposed.

dynamic address configuration for the logical switch port.

Signed-off-by: Aniket Bhat<EMAIL_ADDRESS>

Also, @noah8713 is there a slack/irc channel where folks working on the library communicate?

Also, @noah8713 is there a slack/irc channel where folks working on the library communicate?

Not yet. @hzhou8  can comment if there are plans to start one.

@noah8713 thanks for the reviews. Also, added support for configuring the external_ids for the LSP. PTAL.

Thanks for the improvement. In addition to the inlined comments, it seems the 3rd commit is a fix (and tests) for the previous ones. Please consider squashing them in previous commits before merge.

Will squash commits if everything else looks good.

LGTM except squashing 3rd commit to 1st and 2nd.

LGTM except squashing 3rd commit to 1st and 2nd.

Done. Please merge as appropriate. Also, unrelated, do you/your team hang out on any ovn/ovs IRC/Slack channels to get more "real time" feedback and help with PRs?

LGTM @noah8713 @vtolstov could any of you confirm as well?

do you/your team hang out on any ovn/ovs IRC/Slack channels to get more "real time" feedback and help with PRs?

Yes there is a slack channel, but only me and @vtolstov used it for quite a short while. Feel free to join: https://join.slack.com/t/go-ovn/shared_invite/zt-ddsmtvza-ePqwvAXXzip3HBO62Z1yzA

Squashed commits and addressed the last review comments from @noah8713. PTAL and merge as appropriate. As mentioned above, I will add empty string checks for LSP name in other API implementation methods in a separate PR.

lgtm, i think that other improvements can be in separate pr


Feature parsing

Coverage increased (+10.58%) to 47.84% when pulling 03dc64c9058c9cde2ac9e7d4f69557c3154a9212 on FeatureParsing into 11ad8f53609fd1041a048525ffc2b19bd591885c on master.


Typo on "about" page

<EMAIL_ADDRESS>writes in:

in the english version of the open data portal you state that: "Freely available open government data can contribute to: - simulating the economy" (https://opendata.riik.ee/en/about/)
Do you mean simulating or stimulating?

This is probably the latter. To be confirmed and, if so, fixed.

will fix, definitely a typo.


Upd notify - add edit availability url

-NOT SURE ABOUT MYSELF-
It is supposed to add a message that explain how to set yourself available (for the common case where someone has been late and want to stop the alternate search and play this round.)
I had to create the url via abs_url(reverse()) and if I got it right: edit_availability needs no argument.
I hope the syntax is correct though (meaning the 3 elements in  will not require 3 elements in <args=> cause I put only two.)
Please check that I've been a good boy. Thanks.

Based on a cursory review, I don't see any reason why this won't work.

I'm not sure how to test it easily, so I don't have time to test it today, but I'll look into it as soon as I can.

This is only applicable for the team league, but the method is also used for lonewolf. You'll want to put this behind a condition (like allow_continue below).

Thanks!


Unable to install Microk8s on Raspberry Pi 4

Summary

Installing using snap gives me an error about not being able to install on architecture armhf
error: snap "microk8s" is not available on stable for this architecture (armhf) but exists on other
architectures (amd64, arm64).
What Should Happen Instead?

It should install as normal
Reproduction Steps

sudo snap install microk8s —classic

Introspection Report

Can you suggest a fix?

Are you interested in contributing with a fix?

Hi @thgust, MicroK8s is not available on armhf it is however available for arm64.
Please try to install the 64bit version of your OS, you probably have the 32bit one.


There are times where the db instantiation takes a few seconds... in that case, just run the line again, and it should setup. If that doesn't solve the issue, please let me know.


[TC-CC-3.3] Step 2e is skipping in UI, Because of  &&  operator is missing in between the PICS.

Description:
TC-CC-3.3
Step 2e is skipping in UI, Because in script &&  operator is missing  in between the CC.S.A0000 and PICS_SKIP_SAMPLE_APP PICS.
Steps to reproduce:
Step 2e
Logs:
TC-CC-3.3.log
Screen shot:

Yaml References:

https://github.com/project-chip/connectedhomeip/blob/master/src/app/tests/suites/certification/Test_TC_CC_3_3.yaml

Additional Info:
TH Version: main - dev
Sha: f17efc4

@Ashwinigrl fixed in PR 30951 please verify it and close the ticket.

Issue Fixed


Error populating test data when starting with non-root url

If you start at http://localhost:4200/grants/1/submissions there will be a failure like:
Error: Assertion Failed: 'grant' was saved to the server, but the response returned the new id '1', which has already been used with another record.'
Somehow record gets created before application route is run? Does the model for that route get run first which creates an empty record in the store?

Fixed. Application route needed to return a promise to load the test data.


Multiple device support using upstart or systemd

This is a re-work of my earlier pull request (now closed) regarding startup scripts for systems that need to support more than one DALI USB device being plugged in at a time, with stable mapping between physical device and TCP port number.
This pull request alters the Debian packaging rules to generate three separate binary packages: daliserver, daliserver-upstart and daliserver-systemd.
The daliserver package is unchanged, i.e. it contains the sysvinit startup script.
The daliserver-upstart package has an upstart configuration file.  This configuration file runs an instance of daliserver when a DALI USB device is plugged in, and stops it when the device is unplugged.  A lookup table in /etc/default/daliserver-upstart enables daliserver options to be set based on the serial number of the device that is plugged in.
The daliserver-systemd package has a systemd unit template file and a udev rule that runs an instance of daliserver when a DALI USB device is plugged in, and stops it when the device is unplugged.  A lookup table in /etc/default/daliserver-systemd enables daliserver options to be set based on the serial number of the device that is plugged in.  A helper script in /usr/lib/daliserver-systemd looks up the serial number, bus number and device number based on the systemd template instance name.

Woah, nice work.
I'll still have to review and test it, but it looks like this is a good solution.
I wonder though if separate packages are really needed. Isn't it common to ship startup scripts for all supported init systems within a single package?
There may be conflicts though, as systemd picks up sysvinit scripts and automatically creates corresponding units internally.

I couldn't figure out how to make a single package that did everything.  systemd automatically creating a unit for the sysvinit script is one issue; having a systemd dependency in the udev rules file (which isn't required for systems using upstart or sysvinit) is another.

You can have a choice of requirements in your dependency list, for example:
sysvinit-core | systemd | upstart
I'm not sure how other projects handle this, but it's likely something similar.

Fiddling with the Debian package dependencies won't help in this case.  Having /etc/init.d/daliserver in the package at the same time as<EMAIL_ADDRESS>and the udev rule would mean that daliserver would be started with the default arguments by the sysvinit script (trying to drive the first device it found) and would also be started with appropriate arguments to -u for each DALI USB device attached to the system.  The ordering of what would happen here is not well-defined, and at least one of those invocations of daliserver would fail.

Good point - I came to the same conclusion after contemplating it a bit.
I still think splitting init scripts out into separate packages is wrong, though.
How about using debconf to present a dialogue to the user?

If you can figure out how to make it work, go ahead.  What questions would debconf ask, and what would it do after they were answered?

My suggestion is something like this:

Would you like to run a separate instance of daliserver for each connected DALIUSB device?
Note that you need to configure a different TCP port for each instance.

If selecting yes, it could then ask for the port or something.

I think that question is pointless because the answer will universally be "yes" - and then on a sysvinit system you would have to say "sorry, not possible".

I've updated this pull request: I've rebased to current master, and I've fixed an escaping-related issue that stopped the systemd support working sometime after systemd release 229.  See systemd#7109 and systemd#10321 for details.

Hi @sde1000 , I just pushed a new branch that adds a basic systemd unit.
I'd like to release this first, so we get support for the common case with only one USB adapter.
Once that's merged, we can revisit your proposal of multi-device support.
One option I'm contemplating is dropping SysV init support altogether. I get that Devuan users won't be happy, but I don't want to keep special-casing new features. Are you using something else than systemd?
With only a systemd unit in place, I think it would be much simpler to just document how to create multiple versions of the unit that match different USB adapters, and configure the TCP in each of them statically. I'd also drop /dev/default/daliserver in this case.

I'm using systemd; I think I'm still using packages generated according to this pull request.

Having /etc/init.d/daliserver in the package at the same time as<EMAIL_ADDRESS>and the udev rule would mean that daliserver would be started with the default arguments by the sysvinit script (trying to drive the first device it found) and would also be started with appropriate arguments to -u for each DALI USB device attached to the system.

The creation of a daliserver.service unit from systemd-sysv-generator can be prevented if daliserver.service is shipped as a masked unit (i.e. a symlink to /dev/null).
Another option would be to ship daliserver.service as a dummy unit running /bin/true, and have the template units bind to it. This would e.g. also provide the option to start or stop all daliserver instances. This approach is not uncommon, from the top of my head I can think at least of the openvpn package doing this.

The systemd.unit man page says that an empty unit (size 0) is also treated as masked.
That could be an alternative to creating symlinks via debian/daliserver.links.
In lack of a better (read: more modern) approach, I'm inclined to accept your proposal of using /etc/default/daliserver to map device serial numbers to TCP ports, however I'd like to have some modifications to the PR:

Remove the upstart units. I think upstart has run its course, and I don't want to support many different init systems.
Remove the separate packages. There should be only one daliserver package that contains all files.
Rename the debian/daliserver-systemd* files to debian/daliserver*
Remove the extra debian/*.postint etc. maintainer scripts. I've upgraded the compat level to 10, and that will automatically take care of setting up the init scripts/units.
Likewise, remove the overrides from debian/rules. compat=10 will already take care of everything.
Rebase on the current master branch.
Merge the comments in debian/daliserver.default and remove the log file parameter from DALISERVER_OPTS. The default should be to use the systemd journal, not extra log files. If someone wants them, they can customize the defaults on their system as needed. Your serial number case example is good, please keep that part.
Install daliserver-systemd-start to /usr/libexec/daliserver/ instead of /usr/lib - the EFS designates this directory for package-internal scripts.

I get that producing journals based on the unit instances (which may not have persistent IDs) is somewhat suboptimal, but I really don't like log files if they can be avoided. It would be perfect if we could use the serial number as instance ID instead, but libusb doesn't make it easy to filter by device attributes without opening each device.
Please let me know if you'd prefer that I make these modifications myself instead, I'll rebuild the PR in that case.


fixed some clippy warnings

Mostly this is to make the code more readable, but you may like the usage of the Entry API in src/iota/keymap.rs and the use of an iterator instead of indexing  in src/iota/view.rs.
Cheers!

Thanks for submitting this! I appreciate it.
Didn't know about the entry api, so thanks for showing me that!
I left a comment on the iterator part you added...
Other than that, I'd be happy to merge this!

I backed out the iterator change.

@llogiq sweet, thank you!

You're welcome.


terratests - Possible race condition

The pictures below show the result of two consecutive test runs. Very often it happens that TestK8gbIngressAnnotationFailover, TestK8gbIngressAnnotationRR do not pass. Please investigate and fix the issue. Because the tests sometimes pass, and sometimes don't, I think the issue is race condition. I must add it that both kind and k3d errors occur.

Do you have full error logs? It's hard to say from the screenshots but the failures seem to happen in different places


[TOB-OPYN-005] emit MarginCalculator events

Audit-fix: [TOB-OPYN-005] emit MarginCalculator events
High Level Description
This PR add emit the following events:

OracleDeviationUpdated()
MaxPriceUpdated()
CollateralDustUpdated()
TimeToExpiryAdded()
MaxPriceAdded()
SpotShockUpdated()

Code

[x] Unit test 100% coverage
[x] Does your code follow the naming and code documentation guidelines?

Documentation

[x] Is your code up to date with the spec?
[x] Have you added your tests to the testing doc?

🧨
Update docs?

I will update docs in separate PR once for all, trying to keep the fixes PR will less changes so it is easier to review by ToB.


Can a Runtime be reused in parallel and across multiple mutually-untrusted modules?

I've tried to find this information in the docs, and comments in the code, but I couldn't find anything clarifying this. For full context, I'm using the Compiler engine with the latest wazero release, and using WASI with it.
Question 1: Can a single runtime be used concurrently across many goroutines? Can I compile modules in parallel, and then instantiate those compiled modules in parallel?
Question 2: I'm building a system where users can provide their own wasm modules for me to run. A single instance might need to simultaneously run modules for multiple users. Is it safe to instantiate modules from multiple users (who don't trust each-other, and could be trying to attach each-other) at the same time on a single Runtime?
Or should separate runtimes be used in these cases?

Question 1: yes.
You can definitely instantiate concurrently, and I'm pretty sure you can compile concurrently as well.
Question 2: no.
Use different runtimes. If one module exports its memory, another can import it. If one module exports functions, another can import them. Etc.
Share the compilation cache. Maybe. If you're sure it's useful to do so.

Thanks a lot for the prompt response, that makes sense!


NavBar UI improved

'Closes #447'
🛠 Fixes Issue
1> Improved UI of NavBar
2> FIxed hacktoberfest button in Mobile view

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📷 Screenshots
1> Before

viewers if applicable -->
2>After

3> Added hover effects

@SauravMukherjee44 may I know why this was closed?


We don't currently support --mac-address

Make this clear in the docs and Command.

Should we make the option hidden so people don't accidentally stumble on them?

bot, retest this please.

bot, retest this please


ENH: add Pascal VOC annotations, fix #15

add voc/ sub-package with object.py module
have all StimMakers return RectTuple with list of VOCObjects

add voc_objects field to abstract_stim_maker.RectTuple
have the _make_stim method of all StimMakers return
a list of VOCObject instances, one for each target +
distractor in the image
this list then becomes the voc_objects field in the RectTuple
returned by make_stim
which the make function will use to save Pascal VOC annotation

DEV: add jinja2 as dependency
add Writer class to voc sub-package,
that actually creates Pascal VOC .xml annotations
modify utils.make_csv so csv will have an xml_file column
rewrite make function to save Pascal VOC .xml file
for each search display created, and add that file to the csv
TST: fix test_utils.test_make_csv so it correctly
tests .csv with xml_file column added

Need to fix unit tests so the properly test the .xml files are actually saved


torch JIT extensions should go into python env and not shared ~/.cache/

Perhaps this should be resolved on pytorch level, but I have multiple conda environments and there is only one
~/.cache/torch_extensions/cpu_adam/
~/.cache/torch_extensions/utils/

these can't be reused by different builds.
So getting errors like:
  File "./finetune_trainer.py", line 367, in <module>
    main()
  File "./finetune_trainer.py", line 304, in main
    train_result = trainer.train(
  File "/home/stas/hf/transformers/src/transformers/trainer.py", line 766, in train
    model, optimizer, lr_scheduler = init_deepspeed(self, num_training_steps=max_steps)
  File "/home/stas/hf/transformers/src/transformers/integrations.py", line 402, in init_deepspeed
    model, optimizer, _, lr_scheduler = deepspeed.initialize(
  File "/home/stas/hf/deepspeed/deepspeed/__init__.py", line 110, in initialize
    engine = DeepSpeedEngine(args=args,
  File "/home/stas/hf/deepspeed/deepspeed/runtime/engine.py", line 174, in __init__
    self._configure_optimizer(optimizer, model_parameters)
  File "/home/stas/hf/deepspeed/deepspeed/runtime/engine.py", line 549, in _configure_optimizer
    basic_optimizer = self._configure_basic_optimizer(model_parameters)
  File "/home/stas/hf/deepspeed/deepspeed/runtime/engine.py", line 612, in _configure_basic_optimizer
    optimizer = DeepSpeedCPUAdam(model_parameters,
  File "/home/stas/hf/deepspeed/deepspeed/ops/adam/cpu_adam.py", line 72, in __init__
    self.ds_opt_adam = CPUAdamBuilder().load()
  File "/home/stas/hf/deepspeed/deepspeed/ops/op_builder/builder.py", line 180, in load
    return self.jit_load(verbose)
  File "/home/stas/hf/deepspeed/deepspeed/ops/op_builder/builder.py", line 195, in jit_load
    assert_no_cuda_mismatch()
  File "/home/stas/hf/deepspeed/deepspeed/ops/op_builder/builder.py", line 56, in assert_no_cuda_mismatch
    raise Exception(
Exception: Installed CUDA version 11.0 does not match the version torch was compiled with 10.2, unable to compile cuda/cpp extensions without a matching cuda version.

So the only way currently to overcome this is to pre-build the extensions during deepspeed package build, but on this particular machine it doesn't seem to work, only run-time jit seems to build -
So ideally these extensions should go somewhere in the python env and not ~/.cache/torch_extensions.
A much older related issue is this https://github.com/microsoft/DeepSpeed/issues/599 so one day they could probably be tackled together.

I filed this with the pytorch upstream as this most likely should be solved there https://github.com/pytorch/pytorch/issues/51892

This is a duplicate of another ticket I opened earlier: https://github.com/microsoft/DeepSpeed/issues/599


index 104 out of string (IndexError)

Describe the problem
While attempting to view the markdown from this repository: https://github.com/paulbouwer/hello-kubernetes/blob/main/docs/deploy-using-helm.md
I got this error :
/var/lib/gems/3.1.0/gems/strings-0.2.1/lib/strings/wrap.rb:158:in `insert': index 104 out of string (IndexError)
        from /var/lib/gems/3.1.0/gems/strings-0.2.1/lib/strings/wrap.rb:158:in `block in insert_ansi'
        from /var/lib/gems/3.1.0/gems/strings-0.2.1/lib/strings/wrap.rb:142:in `reverse_each'
        from /var/lib/gems/3.1.0/gems/strings-0.2.1/lib/strings/wrap.rb:142:in `insert_ansi'
        from /var/lib/gems/3.1.0/gems/strings-0.2.1/lib/strings/wrap.rb:111:in `format_line'
        from /var/lib/gems/3.1.0/gems/strings-0.2.1/lib/strings/wrap.rb:30:in `block in wrap'
        from /var/lib/gems/3.1.0/gems/strings-0.2.1/lib/strings/wrap.rb:29:in `map'
        from /var/lib/gems/3.1.0/gems/strings-0.2.1/lib/strings/wrap.rb:29:in `wrap'
        from /var/lib/gems/3.1.0/gems/strings-0.2.1/lib/strings.rb:109:in `wrap'
        from /var/lib/gems/3.1.0/gems/tty-markdown-0.7.2/lib/tty/markdown/converter.rb:441:in `block in max_row_height'
        from /var/lib/gems/3.1.0/gems/tty-markdown-0.7.2/lib/tty/markdown/converter.rb:440:in `map'
        from /var/lib/gems/3.1.0/gems/tty-markdown-0.7.2/lib/tty/markdown/converter.rb:440:in `with_index'
        from /var/lib/gems/3.1.0/gems/tty-markdown-0.7.2/lib/tty/markdown/converter.rb:440:in `max_row_height'
        from /var/lib/gems/3.1.0/gems/tty-markdown-0.7.2/lib/tty/markdown/converter.rb:430:in `block in max_row_heights'
        from /var/lib/gems/3.1.0/gems/tty-markdown-0.7.2/lib/tty/markdown/converter.rb:429:in `each'
        from /var/lib/gems/3.1.0/gems/tty-markdown-0.7.2/lib/tty/markdown/converter.rb:429:in `reduce'
        from /var/lib/gems/3.1.0/gems/tty-markdown-0.7.2/lib/tty/markdown/converter.rb:429:in `max_row_heights'
        from /var/lib/gems/3.1.0/gems/tty-markdown-0.7.2/lib/tty/markdown/converter.rb:359:in `convert_table'
        from /var/lib/gems/3.1.0/gems/tty-markdown-0.7.2/lib/tty/markdown/converter.rb:37:in `convert'
        from /var/lib/gems/3.1.0/gems/tty-markdown-0.7.2/lib/tty/markdown/converter.rb:56:in `block in inner'
        from /var/lib/gems/3.1.0/gems/tty-markdown-0.7.2/lib/tty/markdown/converter.rb:50:in `each'
        from /var/lib/gems/3.1.0/gems/tty-markdown-0.7.2/lib/tty/markdown/converter.rb:50:in `each_with_index'
        from /var/lib/gems/3.1.0/gems/tty-markdown-0.7.2/lib/tty/markdown/converter.rb:50:in `inner'
        from /var/lib/gems/3.1.0/gems/tty-markdown-0.7.2/lib/tty/markdown/converter.rb:70:in `convert_root'
        from /var/lib/gems/3.1.0/gems/tty-markdown-0.7.2/lib/tty/markdown/converter.rb:37:in `convert'
        from /var/lib/gems/3.1.0/gems/kramdown-2.4.0/lib/kramdown/converter/base.rb:107:in `convert'
        from /var/lib/gems/3.1.0/gems/tty-markdown-0.7.2/lib/tty/markdown.rb:144:in `parse'
        from /var/lib/gems/3.1.0/gems/tty-markdown-0.7.2/lib/tty/markdown.rb:163:in `parse_file'
        from /var/lib/gems/3.1.0/gems/tty-markdown-cli-0.1.0/exe/tty-markdown:58:in `<top (required)>'
        from /usr/local/bin/tty-markdown:25:in `load'
        from /usr/local/bin/tty-markdown:25:in `<main>'

Steps to reproduce the problem
I am running Raspberry Pi OS Lite (64-bit) on a raspberry pi 4 with 4Gb of ram
I tried running it via the pipe and via argument but the error was the same.
I installed ruby on the system
Then run the gem install tty-markdown-cli to install the program
Actual behaviour
The program crashes
Expected behaviour
A coloured and parsed markdown
Describe your environment

OS version: Raspberry Pi OS Lite (64-bit)
Ruby version: ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [aarch64-linux-gnu]
TTY::Markdown CLI version: 0.1.0 (tty-markdown 0.7.2)

Hi @HenraL 👋
Thanks for using the tty-markdown-cli gem and reporting this issue.
I can confirm the error. It only happens at certain widths though.
To display the content without error you can specify the terminal width:
ttymarkdown -w 180 docs/deploy-using-helm.md

It would be good to find the actual markdown line that causes the error. I managed to zero in on the culprit being somewhere inside the table. I'd appreciate it if you could investigate further and provide a minimal example of were the wrapping breaks. Ideally, a string that can be replicated with the Strings.wrap(text) call.

Dear @piotrmurach ,
Unfortunatly, i tried to see if I could provide more help, but maybe add a debug flag so that you could get more details.
I am afraid I have provided what I could as a non  ruby programmer.
I think I remember even providing the file that I was using when the error occured
I hope that knowing the terminal was over an ssh connection (the main way used to connect to raspberry pies that are meant to be used as servers) and that the terminal was half the size (on the height) of an average monitor screen could help you.
I wish you a good luck in your debugging, I can always re-run or run updated versions of your program if you need (I am in an englosh time-zone)

Thanks for the replay. I have used the provided file in my original response. That's why I showed you an example of how to run it so that you don't get the error and demonstrate how to view any markdown documents when you find failures. I hoped you would have time to find out which line causes the issue as I'm struggling for time. I need to prioritise my limited time. Also, the string wrapping functionality will be rewritten from scratch at some point in future.


Responsive Demo

I love working with this component, but it took me a while to finally get up and running.
So my humble request: It would be awesome if one of the many SUIT [Sages|Wizards|Magicians|Ninjas|Unicorns] could throw together a fully responsive demo of components-grid in action (and/or point to real-world examples or online tutorials?), utilizing best practices. The readme has a passive note about responsiveness:

Cell widths and offsets can be controlled using the responsive sizing utilities and responsive offset utilities, respectively.

Which meant a bit of trial and error and jumping around to the different plugin readmes.
A demo could also help avoid a few common pitfalls, like if I was new to SUIT and I wanted to use a copy-paste from some of the documentation, I might end up with a simple setup like this:

...where one might have to bang their head against the wall for an hour before figuring out that the Grid--fit modifier might override all of the sizing utilities placed on Grid-cell descendants -- breaking the responsiveness of the Grid.
🦄  ❤

@simonsmith
I think grid is one of the more powerful and useful components.
We had trouble with people not understanding the concepts behind it as well.
Having better documentation and demos that help its adoption rate would be great.
I could recreate the responsive demo using the current syntax, then we'd link that in a prominent location.
What do you think?

Here's a responsive grid demo - Obviously feel free to copy it back to suit.  Rendered test link (It's test 2):
https://superflycss.github.io/component-grid/target/test/html/
{% set when1 %}
Grid  is applied.
{% endset %}
{% call Test.component( 'Grid', when1, 'Cells are rendered with the sizing utility applied when the viewport is large otherwise they are full width.' ) %}

1

2

3

4

{% endcall %}

I could recreate the responsive demo using the current syntax, then we'd link that in a prominent location.

@mlnmln Yeah, I think a real world example as opposed to a test page is the way forward here

Could be this simple:
<EMAIL_ADDRESS>


Accessory with two services not handled correctly

Describe The Bug:
Added an accessory with two 'Outlet' services ('Out' and 'Out2'). Used cflurin's homebridge-mqtt to do so. The accessory displays correctly on iPhone 'Home' app (one button, that opens to a window showing two switches to toggle the outlets). When toggling any of the switches, the state is correctly transferred to the HW accessory (which is  living on an ESP8266 controller driving a MQTT client).
When changing the state of any service inside the HW accessory the new state is also transferred to the Home app correctly. So everything seems to be OK on the foundation level.
The BUG: The accessory is shown in the homebridge-config-ui-x website as two separate buttons. The first works as expected, on state change (by toggling from the website or from the HW accessory) the the display state is updated correctly (On/Off). The second DOESN'T gets updated; neither when toggling the button in the website, nor when toggling the state form HW accessory side. Only a website refresh updates the button to the correct state. Im using Safari Version 13.0.4 on a Mac.
To Reproduce:
Create an accessory with two 'Outlet' services
Expected behavior:
The button for the second service should display the current state of the second accessory correctly.
Logs:
How to create logs; found nothing in the 'Contribution Guidelines'...
Show the Homebridge / Homebridge Config UI X logs here.

Homebridge Config:
{
            "platform": "config",
            "name": "Config",
            "port": 8080,
            "sudo": true,
            "restart": "sudo -n systemctl restart homebridge",
            "log": {
                "method": "systemd",
                "service": "homebridge"
            }
        },

Screenshots:

Environment:

Node.js Version: v11.15.0
NPM Version: 6.13.0
Homebridge Version: homebridge API version: 2.4
Homebridge Config UI X Version: homebridge-config-ui-x v4.6.3
Operating System: Raspberry
Process Supervisor: Systemd

Thanks for the report @LaborEtArs, I'll investigate this.

This is just a thought.
I modify the "aid" for each accessory, and add a .1, .2, etc to the "aid".
For example a nest thermostat has multiple accessories, and they all have an "aid" of 54.
Then the JSON will have 3 accessories
54.1 -> thermostat
54.2 -> Fan
54.3 -> Home/Away
Then to get the actual "aid" i just run Math.floor(aid);

According to the HAP specification, an accessory id, as well as the service id, should be a number in the range of [1,<PHONE_NUMBER>3709551615] (see extract below). @mkells: Are your modified ids visible to the Homekit (HAP) side of 'Homebridge', or 'only' used internaly?
From 'HomeKit Accessory Protocol Specification R2':

2.6.1 Instance IDs
instance IDs are numbers with a range of [1,<PHONE_NUMBER>3709551615] for IP accessories (see ”<IP_ADDRESS> Instance IDs” (page 122) for BLE accessories). These numbers are used to uniquely identify HAP accessory objects within an HAP accessory server, or uniquely identify services, and characteristics within an HAP accessory object. The instance ID for each object must be unique for the lifetime of the server/client pairing.
<IP_ADDRESS> Accessory Instance IDs
Accessory instance IDs, aid, are assigned from the same number pool that is global across entire HAP accessory server. For example, if the first Accessory object has an instance ID of “1”, then no other Accessory object can have an instance ID of “1” within the Accessory Server.
<IP_ADDRESS> Service and Characteristic Instance IDs
Service and Characteristic instance IDs, iid, are assigned from the same number pool that is unique within each Ac- cessory object. For example, if the first Service object has an instance ID of “1”, then no other Service or Characteristic objects can have an instance ID of “1” within the parent Accessory object. The Accessory Information service must have a service instance ID of 1.

Hi @LaborEtArs,
Once again, thanks for reporting this. I was able to replicate this issue and have fixed it in v4.6.6.

THX :-) Good job!


Fix status banners

This commit changed job names, and the banners stopped working.

@DaniilShmelev Ah, thanks for fixing that.

@DaniilShmelev Ah, thanks for fixing that.


Many to Many filter doesnt work in my case

One to many filter works for me see below query.
For ManyToMany the query doesnt recognize the filter i assigned. What am i doing wrong?
employee.ts
 @Field(() => [Benefit], { nullable: true })
  @ManyToMany(() => Benefit)
  public benefits?: Collection<Benefit> = new Collection<Benefit>(this);

  @Field(() => [DayOff], { nullable: true })
  @OneToMany({
    entity: () => DayOff,
    mappedBy: 'employee',
    orphanRemoval: true,
  })
  public dayOffs = new Collection<DayOff>(this);

dayoff.ts
@Filter({
  name: FILTERS.CURRENT_DAY_OFF,
  cond: (args) => ({
    dateTo: { $eq: null },
  }),
  default: false,
})
export class DayOff extends Base<DayOff> {

  @Field({ nullable: true })
  @Property({ nullable: true })
  public dateTo?: Date;
}

benefit.ts
@Filter({
  name: FILTERS.IS_ACTIVE,
  cond: (args) => ({
    benefitStatus: { $eq: STATUS.ACTIVE },
  }),
  default: true,
})
@Unique({ properties: ["benefitCode", "tenantId"] })
export class Benefit extends Base<Benefit> {

  @Field(() => STATUS)
  @Enum(() => STATUS)
  @Property({ columnType: "text" })
  public benefitStatus: STATUS;
}

const employee = await employeeRepository.findOneOrFail(
     readInput.employeeId,
     {
       strategy: LoadStrategy.SELECT_IN,
       filters: [FILTERS.CURRENT_DAY_OFF, FILTERS.IS_ACTIVE],
       populate: ["dayOffs", "benefits"],
     }
   );

[query] select "e0".* from "tbl_day_off" as "e0" where "e0"."employee_id" in ('00000000-0000-0000-0000-000000000001') and "e0"."tenant_id" = '1' and "e0"."date_to" is null order by "e0"."employee_id" asc [took 3 ms]
[query] select "e0".*, "e1"."benefit_id", "e1"."employee_id" from "tbl_benefit" as "e0" left join "tbl_employee_benefits" as "e1" on "e0"."id" = "e1"."benefit_id" where "e1"."employee_id" in ('00000000-0000-0000-0000-000000000001') [took 2 ms]

Filters are never applied to the pivot table, only to the entity tables - is that what you want? Also you are querying employee entity, and it has only one filter (CURRENT_DAY_OFF), the other one can't be applied like this.
Hard to say, as you totally ignored the issue template and I also failed to understand what you actually want. You are talking about a filter, but your example defines 2 filters.
Please provide minimal executable reproduction (so no graphql involved, working entity definitions, as well as some data), and don't forget some assertions.
https://github.com/mikro-orm/mikro-orm/tree/master/tests/issues

Hi @B4nan,
thank you for your fast reply. And sorry for not following the template.
i think youve answered my question with this the other one can't be applied like this
What i wanna achieve is query in employee entity and also filter the benefit status to only active.
So get all benefits with employee id = 1 and status = active something like that.
thanks :)

Currently filters are applied only for the root entity, but you can filter the relation from there too. One of your filters is enabled by default - that is why it works, and that filters: [FILTERS.CURRENT_DAY_OFF, FILTERS.IS_ACTIVE], line in your query has no effect on that.
You could either enable both of them by default (and disable where needed), or specify the filters on the employee entity:
@Filter({
  name: 'IS_ACTIVE',
  cond: {
    benefits: { benefitStatus: { $eq: STATUS.ACTIVE } },
  },
})
@Filter({
  name: 'CURRENT_DAY_OFF',
  cond: {
    dayOffs: { dateTo: { $eq: null } },
  },
})
export class Employee {

  @ManyToMany(() => Benefit)
  public benefits?: Collection<Benefit> = new Collection<Benefit>(this);

  @OneToMany({
    entity: () => DayOff,
    mappedBy: 'employee',
    orphanRemoval: true,
  })
  public dayOffs = new Collection<DayOff>(this);

}

Then you can enable them when querying the employee:
const employee = await employeeRepository.findOneOrFail(
     readInput.employeeId,
     {
       strategy: LoadStrategy.SELECT_IN,
       filters: ['CURRENT_DAY_OFF', 'IS_ACTIVE'],
       populate: ["dayOffs", "benefits"],
     }
   );

Hi @B4nan,
Thanks for clarifying...
My mistake was i added the filter in benefit.ts instead of adding it inside the employee class.
surpisingly though for dayoff class it works even tho i added it inside dayoff.ts not in the employee class as well.

Nothing surprising, as I already mentioned, you had it enabled by default - that is why it worked for that filter.

i also tried for benefit entity and it didnt work. I added it in the benefit class. Ill try to make a sample test file

Also when i try to add the filters in the Employee entity it gives me a one whole query.
select "e0".* from "tbl_employee" as "e0" left join "tbl_employee_deductions" as "e2" on "e0"."id" = "e2"."employee_id" left join "tbl_deduction" as "e1" on "e2"."deduction_id" = "e1"."id" left join "tbl_employee_benefits" as "e4"
on "e0"."id" = "e4"."employee_id" left join "tbl_benefit" as "e3" on "e4"."benefit_id" = "e3"."id" where "e0"."id" = '00000000-0000-0000-0000-000000000001' and "e0"."tenant_id" = '1'  limit 1

What i wanna achieve is that get the employee and then filter the benefits that has an active status. If its not possible i can just call another query.

Yes, that is how filters work. Maybe global filters would work better for you, they are all enabled by default and can be defined for multiple entities at once.
https://mikro-orm.io/docs/filters/#global-filters
Or you can leverage the fact that filters are defined only by their name, so if multiple entities define filter with same name, you can control it also for relations via FindOptions:
https://mikro-orm.io/docs/filters/#naming-of-filters

Hi @B4nan,
can you give me any document on how to run a test script? im sorry im new to the open source world :D i would like to provide an executable test. I forked the mikroorm and i created a test script but i dont know how to run it nor to connect to the database.
I really think this is a bug with ManyToMany. Even with global filters it seems the filter is not applied.
thank you very much for your time and effort

https://github.com/mikro-orm/mikro-orm/blob/master/CONTRIBUTING.md
And keep in mind I already told you filters are never applied to the join table. As well as I already told you why your filter for 1:m was working (as it was enabled by default), while the other for m:n was not (as that one was disabled by default - and you can't control that via FindOptions as you were trying).

ohhh, i thought with this strategy: LoadStrategy.SELECT_IN it is treated as per query per table.
also what do you mean by enabled by default? i just want to clarify cos for 1:m (dayOff.ts) default: false and for benefit.ts I used default: true.

strategy: LoadStrategy.SELECT_IN is the default

also what do you mean by enabled by default? i just want to clarify cos for 1:m (dayOff.ts) default: false and for benefit.ts I used default: true.

I mean exactly that. If you put default: true on both, they will be both applied.

thats the case, even if i put true it doesnt work haha

Interesting, let's wait for the repro.

Hi @B4nan,
I created a pr with the failed test, is this the correct way of doing things? thanks

FYI your repro was not 100% correct, it will never work like that as the collection was already loaded in the memory - you need to clear the EM before you load the entity again to replicate new request. Also you were not populating the collection at all, so if you would actually clear, it would not be even loaded.
Here is a fixed repro:
    const benefit = new Benefit();
    benefit.benefitStatus = 'IA';
    const employee = new Employee();
    employee.benefits.add(benefit);
    await orm.em.persistAndFlush(employee);
    orm.em.clear();

    const b1 = await orm.em.find(Benefit, {});
    expect(b1).toHaveLength(0);
    orm.em.clear();

    const e1 = await orm.em.findOneOrFail(Employee, employee.id, ['benefits']);
    expect(e1.benefits).toHaveLength(0);


[Policy] "Apply changes to devices" is shown even when there are no devices enrolled

Create couple of policies and publish them. When the policies are in published state, on the top menu "Apply changes to devices" is shown.
Ideally this should be shown only if there are devices enrolled at the time of creating a policy.

Labels -  3.1.0-M7, bug, medium


Explain the benefits and reasoning behind using this vs Materialize directly?

Hi. This looks very good. My question is: what are the benefits to using this ng2 wrapper for Materialize over using Materialize directly. I see we get some directives (sugar syntax) for each component, but does this add any major benefit that can't be done with Materialize used directly in angular?
Thanks for any explanations.

Hi @IAMtheIAM,
The main purpose of this library is to simplify the usage within the Angular framework which make it more dynamic. To illustrate what I mean, go ahead and play with the "Playground" sections of components like MzInput or MzSelect in demo app.
Initialization
One thing that Materilize ask you to do for pretty much every components is to initialize it using JQuery. In our implementation, the initializations are done automatically without you to even know that you have to do so.
Quirks
Materialize does not work perfectly "out of the box" when used with Angular, we had to fix a lot of "quirks".
For instance, for mz-input we handle the label so it can animate when the value is changed programmatically.
As another example, using mz-select, the communication between the dropdown created by Materialize and the native select HTML element is handle by our implementation otherwise there is a desynchronization between the value of NgModel/NgControl and the select element. This is just some examples of many more.
Injection
Materialize modals ask you to put the modal HTML directly into the DOM while we offer the possibility to inject a component on the fly using MzModalService.
MediaService
We added the MediaService that allow you to customize some behavior according to the view port size.
Reactive Form support
Another nice advantage that we added to our implementation is the Form Validation. Materialize only provide HTML5 validation while we added support for Reactive Form allowing a more flexible way to do form validation following the same Material Design guidelines.
We haven't wrapped everything ...
Although we didn't wrapped everything yet, you still have all the Materialize library available for you to use when using our package. Some of the CSS classes have not been wrapped into directive as it already does the work pretty well!
I hope it answers your question :)

@jfcere Very excellent response! Thanks for the explanation. I think I will switch and try to use this ng2-materialize wrapper, it does seem to provide some good benefits for working with angular. :-D


To follow this EKS workshop in own environment, how much cost it can take?

To follow this EKS workshop in own environment, how much cost it can take? Any idea?

I am planning to practice entire workshop in my own AWS Account


[nrf fromtree] fs: fcb: add option to disable CRC for fcb entries

Add option to disable CRC for fcb entries. This improves the write throughput significantly at the cost of not detecting corrupted data in flash. This is beneficial for aplications that needs the extra write throughput, where error detection is done elsewhere.
Allow the FCB entries in flash to have a valid CRC when CRC is disabled in the FCB. This allows existing solutions to disable CRC checking, while keeping the CRC areas intact. Note that this is a one-way option.
Fixes #53707
Signed-off-by: Eivind Jølsgard<EMAIL_ADDRESS>(cherry picked from commit cfa1ba1)

We'll need this in sdk-zephyr for NCS v2.3.0 !

Opened to nRF Connect (https://github.com/nrfconnect/sdk-zephyr/pull/1051)


Parallel builds of crate dependencies leads to intermittent linker errors

Summary
While cargo is compiling dependencies I'm seeing intermittent linker errors. It appears the issue is caused by how cargo uses job objects on windows detailed in this issue: rust-lang/rust#33145
Cargo issue is here: https://github.com/rust-lang/cargo/issues/3161
@alexcrichton mentioned that rustup.rs uses job objects, may be affected by this issue as well and that I should open an issue here too.
System info
Windows 10 x64

rustc 1.12.0 (3191fbae9 2016-09-23)
binary: rustc
commit-hash: 3191fbae9da539442351f883bdabcad0d72efcb6
commit-date: 2016-09-23
host: i686-pc-windows-msvc
release: 1.12.0

rustup 0.6.3 (a0e2132 2016-08-28)

cargo 0.13.0-nightly (109cb7c 2016-08-19)

I posted a diagnosis (https://github.com/rust-lang/cargo/issues/3161#issuecomment-251508290) in Cargo, but I think we'll just want to copy https://github.com/alexcrichton/rustjob into Cargo and then copy that into rustc

er, copy it into rustup*

I've posted a PR to fix this issue -- https://github.com/rust-lang-nursery/rustup.rs/pull/984


template for new password files

Provision of a new password template should be possible. Placeholder tag for password name should be supported.
An optional default could look like:
e.g.
===================================================
= Passwort for: $PASSWORD
===================================================
url:
user:
mail:
pass:

Already implemented a while ago ...


Question：Why [UInt8] for request.body?

I try to upload files by WLAN, but the speed is not as fast as expected.
It looks like let rv = [UInt8](buffer[0..<bytesRead]) which located in Socket.swift cost much time. And the [UInt8] is for request.body.
I wonder why [Uint8] is used as the type of request.body?
And will there be potential problem if I use another type(like Data) instead of [UInt8]?
I'm new for Swift and not good at English. Wish I have expressed my question properly.

`[UInt8] is just another way of representing a data blob. You can wrap it in a Data object and it will work fine, see this issue
TLDR: Data(request.body) will do what you want


Use SpringJUnitConfig instead of ExtendWith and ContextConfiguration

Came across an outdated .sdkmanrc file that's not been updated since the switch to Java 17; but as that's not enough to warrant a pull request I figured also pick up some quick automated fixes to the test context setup, based on https://github.com/openrewrite/rewrite-spring/issues/296.

If desired these changes can be applied to a few more Spring projects, but in that case it's probably best to pair up with anyone interested to skip the async review. Happy to help out or show you around, whatever works best.

I've processed the changes to the test classes, but not to the .sdkmanrc, opting to set it to Java 17.

For changes to other projects, you'll probably have to work with each one individually.


Add support for "Add or update a list member"

It's documented here:
http://developer.mailchimp.com/documentation/mailchimp/reference/lists/members/#edit-put_lists_list_id_members_subscriber_hash
This operation looks quite convenient because it's idempotent: it allows you to put a user in a list safely, regardless of whether the user was already in that list.
The API could be:
mailchimp.member.create_or_update(list_id, email, data)

The library would compute the hash per MailChimp's spec:
subscriber_hash = hashlib.md5(email.lower().encode()).hexdigest()

Hi @aaugustin, I have created a new pull request which adds support for "create_or_update". Please check it out and vote up it here: https://github.com/charlesthk/python-mailchimp/pull/31
Thanks!

Thanks for this PR, I have just merged it into the master !


Hospitalization

I am wondering whether hospitalization is included or not. I guess not...
Is that possible to include hospitalization as you did in a former Report 9? This is from the society perspective very important because I guess that measures is only driven by the projection (maximum) of the hospitalization.

I think you can model the counts of hospitalized in a similar way way as deaths are in the paper. You just need to substitute the prior for pi, to a reasonable distribution for the sum of time from infection to symptoms and time from symptoms to hospitalization. Also switch from ifr to ihr (infected-to-hospitalized-ration). The estimates of unadjusted ihr are also in the reference [11].

As said @nlhuong  we could do it. However, right now we are not able to take this because of work load and availability of data. We might come back to it later.

In France we have pretty good Data https://www.data.gouv.fr/en/datasets/donnees-hospitalieres-relatives-a-lepidemie-de-covid-19/


network: guest network interface support NOARP

According to the host link rawflags, setting link NOARP when needed
Fixes: kata-containers#492
Signed-off-by: Zha Bin<EMAIL_ADDRESS>

/test

@jodh-intel - like the parallel PR over in the runtime, this has failed the 'Fixes' check, even though I can see one - I wonder if maybe it could be a character encoding issue?
 See the document below for help on formatting
commits for the project.

Any ideas?

Ah - I have see it now! The "raw" commit shows:
Fixes: kata-containers#492

... but github unhelpfully in this case renders it as:
Fixes: #492

The problem is that our checkcommits tool doesn't understand that syntax.
@zhabinecho - please could you change the "Fixes" line of you commit to be exactly as follows:
Fixes: #492

Ah - I have see it now! The "raw" commit shows:
Fixes: kata-containers#492

... but github unhelpfully in this case renders it as:
Fixes: #492

The problem is that our checkcommits tool doesn't understand that syntax.
@zhabinecho - please could you change the "Fixes" line of you commit to be exactly as follows:
Fixes: #492

OK, I will fixed it. Thanks

/test

@sboeuf - please can you re-review?

LGTM


Proposals accordion should allow multiple open

This should be a small change, mostly just noting it here. It'd be nice to be able to expand any proposal and leave it open, which helps if comparing information side-by-side. Each can still be closed by clicking its title.

Fixed in ebbf96c


Fix some production mode issues

Fixes some issues that occure in production mode only.
Also fixes a typo that prevented permission checks from
working

fixes #4298


Using identity metadata in token roles

We're looking to get this setup in the next few weeks, though I've played with in the past. I'm trying to figure out how I might allow users to authenticate to Vault and then get an API token through Vault for their specific account in Artifactory. For example some templated policy like:
path "artifactory/users/{{identity.entity.id}}" {
  capabilities = [ "read" ]
}

That would allow users to use their authenticated identity in Vault to get an API token for JFrog for their account. Is this doable somehow? The way the roles path is structured now it looks like I could only map devs to some shared role and not their exact identity in Artifactory.

@davidcorrigan714 AFAIK the plugin does not current support what you suggest. This is an excellent feature to add though. We will add this to our backlog.

Sounds good, mostly making sure I hadn't missed anything in the configuration. I think I'll have time to work on this later this quarter myself as it's something we were prototyping with a stand-alone service before deciding to stand up Vault. Happy to collaborate to make sure it meets code standards and makes sense with how you all would want it to work so that our work can be upstreamed.

@davidcorrigan714 Sounds good. When you're ready to contribute, the process is pretty standard so please open a PR and we can work through any comments, feedback, etc.

@TJM not quite sure what you're getting at, have an example of what you have in mind? I just hacked together a proof-of-concept to play with the idea it seemed to work, though maybe not as fine-grained as I might like as far as the policy or configuration which might be what you're getting at.
I created a path at /user/* where it takes the path and issues a token for the user, like so:
func (b *backend) pathUserTokenCreatePerform(ctx context.Context, req *logical.Request, data *framework.FieldData) (*logical.Response, error) {
	b.rolesMutex.RLock()
	b.configMutex.RLock()
	defer b.configMutex.RUnlock()
	defer b.rolesMutex.RUnlock()

	user := strings.TrimPrefix(req.Path, "user/")

	config, err := b.fetchAdminConfiguration(ctx, req.Storage)
	if err != nil {
		return nil, err
	}

	if config == nil {
		return logical.ErrorResponse("backend not configured"), nil
	}

	var ttl time.Duration = 1 * time.Hour

	maxLeaseTTL := b.Backend.System().MaxLeaseTTL()
	maxTTL := 1 * time.Hour

	if maxTTL == 0 {
		maxTTL = maxLeaseTTL
	} else if maxTTL > maxLeaseTTL {
		maxTTL = maxLeaseTTL
	}

	if maxTTL > 0 && ttl > maxTTL {
		ttl = maxTTL
	}

	b.Logger().Warn("Path: " + user)

	role := &artifactoryRole{
		GrantType:  "client_credentials",
		Username:   user,
		Scope:      "applied-permissions/user",
		Audience:   "*@*",
		DefaultTTL: time.Duration(ttl.Seconds()),
	}
	roleName := user

	resp, err := b.createToken(*config, *role)
	if err != nil {
		return nil, err
	}

	response := b.Secret(SecretArtifactoryAccessTokenType).Response(map[string]interface{}{
		"access_token": resp.AccessToken,
		"role":         roleName,
		"scope":        resp.Scope,
		"token_id":     resp.TokenId,
	}, map[string]interface{}{
		"role":         roleName,
		"access_token": resp.AccessToken,
		"token_id":     resp.TokenId,
	})

	response.Secret.TTL = ttl
	response.Secret.MaxTTL = maxTTL

	return response, nil
}

I created a policy:
path "artifactory/user/{{identity.entity.name}}" {
  capabilities = [ "read" ]
}

I then added the OIDC provider to log me in through the corporate SSO, which aligns with our federated user names into Artifactory, so I could get a token for myself from<EMAIL_ADDRESS>but not<EMAIL_ADDRESS>.

Hah, see I was trying to make it more difficult. I was looking at creating a role, for example named "my-account" ... which would lookup the user identity (somehow) and then use the username during the b.CreateToken process... you are creating a new path with the username in it... nice.

Initial PR for feedback: #113


What threadx need to do when power down/up slave cores in arm Cortex-R8 SMP SOC

We are running threadx in arm cortex-r8 smp soc, when power down the slave cores ,what need to do for master core and slave cores in threadx, I only find leaveSMP in file v7.S. and also what to do when power up the slave cores? Thanks.

You would have to exclude all threads/timers from executing on core X before powering down core X. Once you bring up core X, you could remove that exclusion.


MINOR: Make KStreamSessionWindowAggregate public.

When using the processor API it is useful to leverage existing Kafka streams processors. KStreamSessionWindowAggregate cannot be used with the processor API because it is package private. KStreamWindowAggregate is public however.
No tests were written as this is only a visibility change.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@guozhangwang thanks for taking a look. Understood I can use the high level DSL with low level processors. Out of curiosity why is KStreamWindowAggregate public?

KStreamWindowAggregate should be package private as well. I think it is overlooked.


Support AppSync custom domains

Environment information
System:
  OS: macOS 14.5
  CPU: (12) arm64 Apple M3 Pro
  Memory: 51.98 MB / 18.00 GB
  Shell: /bin/zsh
Binaries:
  Node: 20.15.1 - ~/.nvm/versions/node/v20.15.1/bin/node
  Yarn: undefined - undefined
  npm: 10.7.0 - ~/.nvm/versions/node/v20.15.1/bin/npm
  pnpm: undefined - undefined
NPM Packages:
  @aws-amplify/auth-construct: 1.2.0
  @aws-amplify/backend: 1.0.4
  @aws-amplify/backend-auth: 1.1.0
  @aws-amplify/backend-cli: 1.2.1
  @aws-amplify/backend-data: 1.1.0
  @aws-amplify/backend-deployer: 1.0.2
  @aws-amplify/backend-function: 1.3.0
  @aws-amplify/backend-output-schemas: 1.1.0
  @aws-amplify/backend-output-storage: 1.0.2
  @aws-amplify/backend-secret: 1.0.0
  @aws-amplify/backend-storage: 1.0.4
  @aws-amplify/cli-core: 1.1.1
  @aws-amplify/client-config: 1.1.1
  @aws-amplify/deployed-backend-client: 1.1.0
  @aws-amplify/form-generator: 1.0.0
  @aws-amplify/model-generator: 1.0.2
  @aws-amplify/platform-core: 1.0.3
  @aws-amplify/plugin-types: 1.1.0
  @aws-amplify/sandbox: 1.1.1
  @aws-amplify/schema-generator: 1.2.0
  aws-amplify: 6.4.3
  aws-cdk: 2.150.0
  aws-cdk-lib: 2.150.0
  typescript: 5.5.4
AWS environment variables:
  AWS_STS_REGIONAL_ENDPOINTS = regional
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_SDK_LOAD_CONFIG = 1
No CDK environment variables

Description
A custom domain name and an API mapping can be created using CDK, however, the amplify_outputs.json always contains the original generated version of the GraphQL endpoint even if a custom domain is attached.
This is not ideal to use this URL, especially for mobile applications since it can happen that the stack needs to be recreated for some reason, and the previously generated endpoint will be no longer available.
I tried to override the value by backend.addOutput({ data: { url: 'my-custom-url' } }), but this is not supported in this way.
Is there any other way to somehow automate this step?
Thanks

Hey @otottkovacstibor :wave: thanks for raising this! I think this is a great idea to introduce first-class support for custom domains in Amplify resources. Marking as a feature request


Better match to the old release annotations deployment task

Replace
-aiResourceId "<aiResourceId>" `
    -releaseName "<releaseName>" `
    -releaseProperties @{"ReleaseDescription"="<a description>";
         "TriggerBy"="<Your name>" }

with
-aiResourceId "<aiResourceId>" `
-releaseName "$(Release.ReleaseName)" `
-releaseProperties @{
 "BuildNumber"="$(Build.BuildNumber)";
 "BuildRepositoryName"="$(Build.Repository.Name)";
 "BuildRepositoryProvider"="$(Build.Repository.Provider)";
 "ReleaseDefinitionName"="$(Build.DefinitionName)";
 "ReleaseDescription"="Triggered by $(Build.DefinitionName) $(Build.BuildNumber)";
 "ReleaseEnvironmentName"="$(Release.EnvironmentName)";
 "ReleaseId"="$(Release.ReleaseId)";
 "ReleaseName"="$(Release.ReleaseName)";
 "ReleaseRequestedFor"="$(Release.RequestedFor)";
 "ReleaseWebUrl"="$(Release.ReleaseWebUrl)";
 "SourceBranch"="$(Build.SourceBranch)";
 "TeamFoundationCollectionUri"="$(System.TeamFoundationCollectionUri)" }

and it would be a better match to what the old release annotations deployment task did

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

ID: ee1eec15-6783-f8a2-81c0-ffa9d1b40dc2
Version Independent ID: ab875981-7b0d-95be-dc5b-91f87acbe477
Content: Release annotations for Application Insights - Azure Monitor
Content Source: articles/azure-monitor/app/annotations.md
Service: azure-monitor
Sub-service: application-insights
GitHub Login: @lgayhardt
Microsoft Alias: lagayhar

@funkysi1701 Thanks for your feedback.
Assigning to content author @lgayhardt for review.

@funkysi1701 Thank you for the feedback and the code snippet. Engineering wants to keep the script simple so instead we are going to use your script as a separate example for releaseProperties. The changes should go live in a few days.
Thank you
#please-close

#please-close

#please-close


Check(demon!=nullptr) before accessing demon->

Hi! Just pointing out that the dev branch is master instead of stable

Rebased and pushed on master...
https://github.com/google/or-tools/commit/8232d39b6989a44fdea831d89418b29d8d7f899a
closing this PR


Fresh Nuxt 3 install on Vercel: The package "esbuild-linux-64" could not be found

Reproduction:

Repo: https://github.com/birdlavv/vue-email-reproduction
Vercel deploy: https://vue-email-repro.vercel.app/api/test

The reproduction was made by

Creating a blank Nuxt 3 project
Installing vue-email
Adding WelcomeEmail.vue
Adding /api/test.ts

export default defineEventHandler(async (event) => {
  const template = await useCompiler('WelcomeEmail.vue')
  return template
})

Any assistance/insight into what is causing this would be greatly appreciated.
Possible related issues:

https://github.com/vercel/vercel/issues/7287
https://github.com/evanw/esbuild/issues/1819

Yes @Dave136 , it works as expected in development but breaks at deployment runtime. There don't seem to be any build warnings or errors. I do not yet know if this is a cross-platform error or if it is specific to Vercel.

@birdlavv I test the nuxt implementation, npm and yarn throw error, it seems it's a issue with esbuild.
I suggest you use pnpm, it resolves as well.
I created a repo, where i tested the functionalities, open the terminal, click the button and you can see the result.
Here i left you the repo and production link:

Repo github
Prod working example

I can confirm that using pnpm as a workaround works on Vercel.
Thanks, @Dave136!

Hi guys, how do you get Vercel to use pnpm?