Also release as Firefox Add-on

Now that Firefox supports the (pretty much) same WebExtensions API like Chrome it would be cool if Ressource Override could be migrated to Firefox too ❤
Ressources:

https://developer.mozilla.org/en-US/Add-ons/WebExtensions
https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Porting_a_Google_Chrome_extension

Ah yeah, this has been on my mind.. I'll have to look into it... eventually.
I used to have a lot more free time to do OSS. :sweat:
First need to find out what features are not supported and find workarounds.

Thanks for considering 👍

I used to have a lot more free time to do OSS.

Sounds familiar :-/

First need to find out what features are not supported and find workarounds.

You could use the Extension Compatibility Test for this. Just upload your *.crx file to https://www.extensiontest.com/ and it will scan the source code. Normally, every feature in Chrome should also be available in Firefox (bugs aside ;)

Actually, I ended up looking into it tonight because the number of errors the compatibility checker gave me was low...
I made a "quick-fix" alpha branch here: firefox-alpha
One could (for the time being) download this branch and load it into firefox as a debugging extension... although that's kind of a pain. However, I would appreciate the testing. Here's how: https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Temporary_Installation_in_Firefox
So far, my preliminary testing seems to show most everything working. Only real issue I noticed was the dev tools pane not being able to suggest files (which is because devtools.inspectedWindow.getResources() is not supported in FF yet).
I kinda feel like this extension needs a re-write, but seeing how many people use it, I'm afraid to touch it. I may merge this branch once I have more time to test it, at which point I could release it for FF. Any outside testing would be appreciated. I hope someday I can clean things up though and make this a much more modern code base.

Seems to be working here in FF Developer Edition. You life saver!

@kylepaulsen Since this has been used (tested) by a few people for quite some time could it be released on https://addons.mozilla.org/en-US/firefox/? I know the extension is in maintenance mode but at the moment there's just this branch to install from and that's rather complicated compared to just install from the official textensions site (and also unless one uses Firefox Nightly, you also run into problems as this is then a self-signed extension that also need about:config workarounds...)
So just to have an upload to https://addons.mozilla.org/en-US/firefox/ would be very much appreciated.

@jnachtigall I will try to do this soon. It seems like it shouldn't require too much effort to get it published.

@jnachtigall @ashbryant It's out now. It seems to work fine, but I didn't test very much.
https://addons.mozilla.org/en-US/firefox/addon/resourceoverride/

@kylepaulsen Thank you so much!


Adapt def _assign_imports_to_globals

Hi~
I found we often make multiple imports in one line like below
from keras.layers import LSTM, Dropout, Dense.
Therefore, I rewrote the func., def _assign_imports_to_globals() to make this work.
If you are free, please check it out.

Hi~ Thanks for your reply.
E.g. do you add the "from keras.layers import LSTM, Dropout, Dense" to your personal pyforest imports?
Yes, I did. I knew that in original project,
the normal formats are "import matplotlib.pyplot as plt" or
"from sklearn.ensemble import GradientBoostingRegressor"
However,
I know that we often would like to make the lines shorter,
we usually write imports in one line with comma
if they are in the same module.
We don't write
"from keras.layers import LSTM",
"from keras.layers import Dropout",
"from keras.layers import Dense" repeatedly.
The similar situation also happens when using Python built-in modules.
E.g., "import sys, os, re"
My PR is to create 3 LazyImport instances as the original project,
but users still can add their common use imports
in ~/.pyforest/user_imports.py,
like "from keras.layers import LSTM, Dropout, Dense" in one line.
I also created 2 small personal features in my forked repo.
If you have interest, welcome to glance at them.
I wrote short description in readme file.
I think this project is useful for
the users who often change their workplaces
in different local machines, cloud IDEs, or projects.
Thank you very much!

Thank you for your reply. Please also describe the behavior/spec of pyforest before and after your PR.

Hi @triper1022,
So you mentioned that your PR allows writing import statements like from keras.layers import LSTM, Dropout, Dense to your personal pyforest imports.
Now, I'm wondering: If you open a fresh Notebook (with no imports written yet) and start using keras.layers.Dropout for example (but not LSTM or Dense), what import statement will be added to the top of the Notebook?
Will it be

from keras.layers import LSTM, Dropout, Dense
from keras.layers import Dropout
something else?

Can you describe any other behavioural changes of pyforest coming with your PR?


[question] How to make a lifecycle configuration default for all new notebooks?

Is there a way to make a certain lifecycle configuration default (ideally, also mandatory) for all new notebooks?
auto-stop-idle works great, but only when users do not forget to use it upon notebook creation.
I did some research but found only studio-lcc-defaults, for Studio notebooks not the classic ones.

As of writing, there is no mechanism to have a default lifecycle configuration ran for a notebook instance. The lifecycle configuration needs to be passed into the create notebook instance API call. I am closing this issue for now, thank you.


I got the latest facemesh files from Google ARCore, you can try to put them in your project

facemesh_from_google_arcore.zip

What is the license for this model?

Closed due to lack of progress.


Unable to upload logo image to app registration

This is autogenerated. Please review and update as needed.
Describe the bug
Trying to upload the logo for an Azure app Registration, running into an encoding issue with az rest. (See below)
Command Name
az rest
Errors:
The command failed with an unexpected error. Here is the traceback:
'latin-1' codec can't encode character '\u2030' in position 0: Body ('â€°') is not valid Latin-1. Use body.encode('utf-8') if you want to send it encoded in UTF-8.
Traceback (most recent call last):
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 231, in invoke
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 663, in execute
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 697, in _run_job
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 333, in __call__
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/util/custom.py", line 24, in rest_call
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/util.py", line 974, in send_raw_request
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\requests/sessions.py", line 655, in send
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\requests/adapters.py", line 439, in send
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\urllib3/connectionpool.py", line 699, in urlopen
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\urllib3/connectionpool.py", line 394, in _make_request
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\urllib3/connection.py", line 239, in request
  File "http\client.py", line 1282, in request
  File "http\client.py", line 1327, in _send_request
  File "http\client.py", line 166, in _encode
UnicodeEncodeError: 'latin-1' codec can't encode character '\u2030' in position 0: Body ('â€°') is not valid Latin-1. Use body.encode('utf-8') if you want to send it encoded in UTF-8.

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
$logoBytes = Get-Content ..\logo.png -Raw
 az rest --method PUT --uri "https://graph.microsoft.com/v1.0/applications/$MYAPPID/logo" --headers 'Content-Type=image/png' --body $logoBytes

Expected Behavior
Environment Summary
Windows-10-10.0.22621-SP0
Python 3.10.4
Installer: MSI

azure-cli 2.37.0 *

Extensions:
account 0.2.1
application-insights 0.1.16
containerapp 0.3.7
storage-preview 0.8.3

Dependencies:
msal 1.18.0b1
azure-mgmt-resource 21.1.0b1

Additional Context

@jiasli for awareness

The error above might be due to improper encoding of the stream being sent in.
After correcting the encoding (was not sending the body as stream), encountering a new error:
Script errors out with message "The command line is too long."
$logoBytesWeb = (Invoke-WebRequest "https://purepng.com/public/uploads/medium/purepng.com-microsoft-logo-iconlogobrand-logoiconslogos-251519939091wummo.png").Content
az rest --method PUT --uri "https://graph.microsoft.com/v1.0/applications/$appId/logo" --headers 'Content-Type=image/png' --body $logoBytesWeb --debug

I am now confident I am now sending the proper bytes stream since I can make this work using the Invoke-RestMehod in PowerShell
Script that works:
$token=(az account get-access-token --resource "https://graph.microsoft.com" --query accessToken --output tsv)

$logoBytesWeb = (Invoke-WebRequest "https://purepng.com/public/uploads/medium/purepng.com-microsoft-logo-iconlogobrand-logoiconslogos-251519939091wummo.png").Content

Invoke-RestMethod -Uri "https://graph.microsoft.com/v1.0/applications/$appId/logo" -Method "PUT" -Header @{"Authorization"="Bearer $token";"Content-Type"="image/png";} -Body $logoBytesWeb


Error while doing poetry run pytest

While doing 'poetry run pytest`, I encountered following error.
(py4vasp-env) PS <path>\py4vasp> poetry run pytest
Traceback (most recent call last):
  File "<some_path>\.conda\envs\py4vasp_pymatgne\lib\site-packages\requests\compat.py", line 11, in <module>
    import chardet
ModuleNotFoundError: No module named 'chardet'

During handling of the above exception, another exception occurred:

ImportError: cannot import name 'COMMON_SAFE_ASCII_CHARACTERS' from 'charset_normalizer.constant'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<some_path>\.conda\envs\py4vasp_pymatgne\lib\site-packages\requests\compat.py", line 11, in <module>
    import chardet
ModuleNotFoundError: No module named 'chardet'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  <some info>
    from poetry.mixology.solutions.providers.python_requirement_solution_provider import (
  <some info>
AttributeError: partially initialized module 'charset_normalizer' has no attribute 'md__mypyc' (most likely due to a circular import)

I performed a pip install chardet in the environment and it resolved the error.

I cannot reproduce this issue. It seems that this originates from somewhere inside poetry. How did you install poetry? Did you change anything compared to the instructions in the README file?

I didn't change anything as instructed in the README file. Following is the step, I followed.

First created the environment : conda create --name py4vasp-env python=3.8
Second cloned the project : git clone https://github.com/vasp-dev/py4vasp.git
Activated the environment: conda activate py4vasp-env
Installed poetry: pip install poetry
Went into the clone repository: cd py4vasp
Did poetry install
Then did conda install -c conda-forge mdtraj
Then did poetry run pytest

Now it worked. I also couldn't reproduce this, either.
I figured out that installation of mdtraj with conda install conda-forge::mdtraj is causing that error.  It is installing some old package along with some extra package.

Brotli (1.0.9) (instead of 1.1.0)
charset-normalizer (2.0.4) (instead of 3.3.2)
idna (3.4) (instead of 3.6)
platformdirs (3.10.0) (instead of 3.11.0)
pooch (1.7.0) (instead of 1.8.1)

Extra packages:

Bottleneck (1.3.7)
mkl-fft (1.3.8)
mkl-random (1.2.4)
mkl-service (2.4.0)


Shell doesn't always process input data when it arrives

The shell doesn't always consume all input data when it arrives.
For example, when several lines worth of data are pasted simultaneously from the host, the shell will act as if it only received the first or second line.  If the host sends even more input, then the shell starts to "catch up" and processes the third original pasted line as if it had just arrived.
Tested on nrf52 with shell over UART but this would affect any transport.
The exact behavior is messy depending on timing and whether the shell_uart RX buffer overflows -- basically the user visible effect is that the shell seems to drop input, then processes old input when new input comes in, etc.
This is fixed by PR https://github.com/zephyrproject-rtos/zephyr/pull/15224

I've added @jimparis as a resolver because he already fixed it ;)


[timing] return internal function timing

internally calculate execution time and return it as a header to the answer.

[x] c
[x] c++
[x] go
[x] js
[x] rb
[ ] rs
[ ] python (doesn't apply)

it's backward compatible

The thing is that some processes are started using Popen, others Subprocess.check_output etc. Could we just start the process using time and parse the output of time ?
Would also allow to see the sys time usage and the user time usage

Oops rust template is wrong, fixing it

The thing is that some processes are started using Popen, others Subprocess.check_output etc. Could we just start the process using time and parse the output of time ?
Would also allow to see the sys time usage and the user time usage

@JulesDT calculating with time would include the environnent bootstrap also, I think it's best to keep it that way to match the pattern with python submissions.

How about printing the duration at the very end, as a footer instead of a header? That way, we are still free to print to stdout directly from the run function

@badouralix we still print stdout freely, it's the same thing header or footer 😄

:shipit:


DateTimeParseException when using $toMillis

When you use $toMillis on a date without time, a DateTimeParseException/EvaluateRuntimeException occurs.
Example input json:
{
  "date": "2021-08-25"
}

Example jsonata:
$toMillis(date)

Expected output as on https://try.jsonata.org/
1629849600000

I just pushed version 1.5.8 to Maven Central (it will take a few hours to show up). Check here for version 1.5.8...
Please close this issue if you believe it has been fixed. Thank you.

I tested with 1.5.8 and the issue has been fixed. Thanks!


Improve test suite

Description

Begin working through the tests.  Pull atm just includes a draft of auth tests. Still need to reduce duplication of describe blocks and use before/after hooks to reduce code duplication
Also adds npm run coverage for a local coverage report. I don't feel the need to put this in CI/CD because I'm probably the only one who's going to be using it.
validate.test.ts  should be removed when we have proper types in backend

Fixes/resolves #97
Type of change
Please delete options that are not relevant.

[x] Improvement (non-breaking change which improves existing functionality)

Checklist:
Leave blank if not applicable
I have completed these steps when making this pull request:

[x] I have checked that the PR is from a forked repository
[x] I have assigned my name to the issue
[x] I have moved the issue to the In Progress column
[x] I have labelled the PR appropriately
[ ] I have assigned people responsible to the PR

Before opening the PR for review:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my code
[x] I have documented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I have moved the linked issue to the Review in Progress column

deploy action has been split to a separate file; no idea if it works or not :cowboy_hat_face:

Please review. I am aware that there are some extensions that are required to be made to the test suite due to new endpoints being introduced. These will be done in a separate PR because we really need some base level tests in the project.

repinging jchad because i suspect it didn't work out of the box because you are on windows? mb. have added crossenv now.

Yeah I am currently on windows 😢. It works well with cross-env, I'm just investigating the issues with the tests that are being skipped


[FEATURE] mass-ban users that match pattern

linked with #304, use same patterns but i would like both of these to exist.  shouldn't be too hard if one is made.
also obviously, should print them all before and have a confirm thing.

alternatively, this can just accept multiple user IDs & a message, ie !massban<PHONE_NUMBER>44262432<PHONE_NUMBER>38270977<PHONE_NUMBER>79003137<PHONE_NUMBER>42947584<PHONE_NUMBER>96229632<PHONE_NUMBER>6804736<PHONE_NUMBER>78047232<PHONE_NUMBER>53730048<PHONE_NUMBER>50893824 literally hitlers

looks like discord doesn't do any additional rate limiting for banning; appears to just be the global rate limit.


Chaotic Feat:  Improve style of home page

Describe your chaotic idea
Hey @vansh-codes I want to recreate the design of home page. It should more interactive for user.
This can improve the UI/UX of the website.
Add Screenshots or Sketches
Currently it is looking so simple and not much attractive.

Could you assign this task to me, so that I can start working on it.
Confirm

[X] I understand that my idea will add to the chaos and I'm okay with it
[X] I agree to follow this project's Code of Conduct
[X] I want to work on this feature
[X] I'm GSSOC'24 Extd registered Contributor
[X] I'm Hacktoberfest registered Contributor

Wait for #2 to be completed and merged, then if required I will ping you then you can improve the UI
Till that time, search for new issues or explore
https://github.com/vansh-codes/Gityzer

You can check the setup now and propose your idea for changes so we can proceed further 🚀

Hey @vansh-codes I am proposed to recreate the design of this testing page. I simply wanted to make the UI better. I wanted to add a attractive background and change the design of existing element like button, Text etc.
I can add some animation also, which is good for the website.
currently this is looks like very simple and not much attractive.

Do check the deployment again, its already updated and changed

check the new UI and then propose me your ideas for modification

Check the deployment brother, if you have already forked then pull the changes first
Check here https://vansh-codes.github.io/ChaosWeb/

Ohh sorry my bad bro, you are asking to modify Testing page
sor sorry
We dont require the testing page, can you integrate the functionality of testing page in all the pages??

Do you still want to work on this or shall I close this issue?

Sure go ahead!

Sure go ahead!

@vansh-codes  Assign this to me..

@vansh-codes ??

Create PR

@vansh-codes okay


Multiple Swapchain example?

Hi,
I'm here to request another example or best practice, multiple swapchain with multiple windows, which present mode to use, how to acquire next swapchain image, single or multiple vkQueueSubmit? Command buffers, one per swapchain?
Thanks in advance.

Hi @amerkoleci - We are considering this but it is more of a niche case so it may take longer versus other sample requests.
Out of curiosity what is your use case?

Nothing specific, just working on vulkan integration in my game engine, having different hlsl shader scenarios would help me out, but I can handle alone this anyway.
Thank you

Imgui has multiple swapchain support but would love to see how the best case is, how to achieve best performance, single vkQueuePresent vs other

I'm looking forward to this too.  I'm trying to create a 3D model editor using Vulkan to render the scene


pbmm2 sequence identity filters

pbmm2 1.2.0
Hi,
I saw on the Github that the default 70% --min-concordance-perc filter is "only appropriate if applied to resequencing data of haploid organisms." Do you have recommendations for which of the two remaining sequence identity filters (--min-id-perc and/or --min-gap-comp-id-perc) would be best for aligning human ccs reads (with short 1.5-3 kb dna inserts)?
Thank you!

Those are experimental and we can't give you any guidance yet. Once we switch over, you'll find more info on the GitHub documentation.


Database provisioning for OHDSI

As architect I would like a way to deploy the OHDSI database automatically if it's not already present

Linking to lsc-sde/lsc-sde#47


v2.0.0 beta.1

Updated Info.plist files and podspec for v2.0.0 beta.1🎉

It should be merged into master, not v1.


Since Intel CPU Azure update, new Azure Disks are not mounting, very critical...

Is this a request for help?:
New azure managed disks are not mouting on the Kubernetes nodes, Azure API slow.
Is this an ISSUE or FEATURE REQUEST? (choose one):
It's an ISSUE
What version of acs-engine?:
ACS Engine version : 0.7.0
Kubernetes version : 1.7.5
kubectl version
Client Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.6", GitCommit:"4bc5e7f9a6c25dc4c03d4d656f2cefd21540e28c", GitTreeState:"clean", BuildDate:"2017-09-14T06:55:55Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.5", GitCommit:"17d7182a7ccbb167074be7a87f0a68bd00d58d97", GitTreeState:"clean", BuildDate:"2017-08-31T08:56:23Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}

After the big update yesterday, i'm seeing a lot of errors about attaching or detaching Azure Managed Disks on kubernetes, espacially the new created ones.
I recreated all my stacks (Elasticsearch/kafka/Zookeeper/...) using a PersistentVolumeClaim with my statefullsets after the big update yesterday.
All my new Azure Disks are not able to be mounted on my workers, but actually it should :

I'm posting the logs of the kube-controller manager :
W0105 10:24:00.133401       1 reconciler.go:267] Multi-Attach error for volume "pvc-4c0b9e2b-a48d-11e7-a344-000d3ab7665a" (UniqueName: "kubernetes.io/azure-disk//subscriptions/3770e200-bb58-4d3b-afcb-66c7ce083c3f/resourceGroups/k8s-fleeters-cluster-preproduction/providers/Microsoft.Compute/disks/fleeters-59cd2dcd-dynamic-pvc-4c0b9e2b-a48d-11e7-a344-000d3ab7665a") from node "k8s-k8sworkers-20163042-3" Volume is already exclusively attached to one node and can't be attached to another
I0105 10:24:00.133439       1 event.go:218] Event(v1.ObjectReference{Kind:"Pod", Namespace:"integration", Name:"grafana-1826545959-8qw5q", UID:"20425f47-f1f7-11e7-92c5-000d3ab769d6", APIVersion:"v1", ResourceVersion:"22791080", FieldPath:""}): type: 'Warning' reason: 'FailedAttachVolume' Multi-Attach error for volume "pvc-4c0b9e2b-a48d-11e7-a344-000d3ab7665a" Volume is already exclusively attached to one node and can't be attached to another
I0105 10:24:00.133458       1 event.go:218] Event(v1.ObjectReference{Kind:"Pod", Namespace:"preproduction", Name:"mongo-0", UID:"5492929f-f1b4-11e7-92c5-000d3ab769d6", APIVersion:"v1", ResourceVersion:"22247369", FieldPath:""}): type: 'Warning' reason: 'FailedAttachVolume' Multi-Attach error for volume "pvc-8743f77c-a472-11e7-b780-000d3ab769d6" Volume is already exclusively attached to one node and can't be attached to another
W0105 10:24:00.233803       1 reconciler.go:267] Multi-Attach error for volume "pvc-8743f77c-a472-11e7-b780-000d3ab769d6" (UniqueName: "kubernetes.io/azure-disk//subscriptions/3770e200-bb58-4d3b-afcb-66c7ce083c3f/resourceGroups/k8s-fleeters-cluster-preproduction/providers/Microsoft.Compute/disks/fleeters-59cd2dcd-dynamic-pvc-8743f77c-a472-11e7-b780-000d3ab769d6") from node "k8s-k8sworkers-20163042-2" Volume is already exclusively attached to one node and can't be attached to another
I0105 10:24:00.233910       1 event.go:218] Event(v1.ObjectReference{Kind:"Pod", Namespace:"preproduction", Name:"mongo-0", UID:"5492929f-f1b4-11e7-92c5-000d3ab769d6", APIVersion:"v1", ResourceVersion:"22247369", FieldPath:""}): type: 'Warning' reason: 'FailedAttachVolume' Multi-Attach error for volume "pvc-8743f77c-a472-11e7-b780-000d3ab769d6" Volume is already exclusively attached to one node and can't be attached to another
W0105 10:24:00.234034       1 reconciler.go:267] Multi-Attach error for volume "pvc-4c0b9e2b-a48d-11e7-a344-000d3ab7665a" (UniqueName: "kubernetes.io/azure-disk//subscriptions/3770e200-bb58-4d3b-afcb-66c7ce083c3f/resourceGroups/k8s-fleeters-cluster-preproduction/providers/Microsoft.Compute/disks/fleeters-59cd2dcd-dynamic-pvc-4c0b9e2b-a48d-11e7-a344-000d3ab7665a") from node "k8s-k8sworkers-20163042-3" Volume is already exclusively attached to one node and can't be attached to another
I0105 10:24:00.234063       1 event.go:218] Event(v1.ObjectReference{Kind:"Pod", Namespace:"integration", Name:"grafana-1826545959-8qw5q", UID:"20425f47-f1f7-11e7-92c5-000d3ab769d6", APIVersion:"v1", ResourceVersion:"22791080", FieldPath:""}): type: 'Warning' reason: 'FailedAttachVolume' Multi-Attach error for volume "pvc-4c0b9e2b-a48d-11e7-a344-000d3ab7665a" Volume is already exclusively attached to one node and can't be attached to another
W0105 10:24:00.334429       1 reconciler.go:267] Multi-Attach error for volume "pvc-8743f77c-a472-11e7-b780-000d3ab769d6" (UniqueName: "kubernetes.io/azure-disk//subscriptions/3770e200-bb58-4d3b-afcb-66c7ce083c3f/resourceGroups/k8s-fleeters-cluster-preproduction/providers/Microsoft.Compute/disks/fleeters-59cd2dcd-dynamic-pvc-8743f77c-a472-11e7-b780-000d3ab769d6") from node "k8s-k8sworkers-20163042-2" Volume is already exclusively attached to one node and can't be attached to another
W0105 10:24:00.334518       1 reconciler.go:267] Multi-Attach error for volume "pvc-4c0b9e2b-a48d-11e7-a344-000d3ab7665a" (UniqueName: "kubernetes.io/azure-disk//subscriptions/3770e200-bb58-4d3b-afcb-66c7ce083c3f/resourceGroups/k8s-fleeters-cluster-preproduction/providers/Microsoft.Compute/disks/fleeters-59cd2dcd-dynamic-pvc-4c0b9e2b-a48d-11e7-a344-000d3ab7665a") from node "k8s-k8sworkers-20163042-3" Volume is already exclusively attached to one node and can't be attached to another
I0105 10:24:00.334462       1 event.go:218] Event(v1.ObjectReference{Kind:"Pod", Namespace:"preproduction", Name:"mongo-0", UID:"5492929f-f1b4-11e7-92c5-000d3ab769d6", APIVersion:"v1", ResourceVersion:"22247369", FieldPath:""}): type: 'Warning' reason: 'FailedAttachVolume' Multi-Attach error for volume "pvc-8743f77c-a472-11e7-b780-000d3ab769d6" Volume is already exclusively attached to one node and can't be attached to another
I0105 10:24:00.334586       1 event.go:218] Event(v1.ObjectReference{Kind:"Pod", Namespace:"integration", Name:"grafana-1826545959-8qw5q", UID:"20425f47-f1f7-11e7-92c5-000d3ab769d6", APIVersion:"v1", ResourceVersion:"22791080", FieldPath:""}): type: 'Warning' reason: 'FailedAttachVolume' Multi-Attach error for volume "pvc-4c0b9e2b-a48d-11e7-a344-000d3ab7665a" Volume is already exclusively attached to one node and can't be attached to another
W0105 10:24:00.434953       1 reconciler.go:267] Multi-Attach error for volume "pvc-8743f77c-a472-11e7-b780-000d3ab769d6" (UniqueName: "kubernetes.io/azure-disk//subscriptions/3770e200-bb58-4d3b-afcb-66c7ce083c3f/resourceGroups/k8s-fleeters-cluster-preproduction/providers/Microsoft.Compute/disks/fleeters-59cd2dcd-dynamic-pvc-8743f77c-a472-11e7-b780-000d3ab769d6") from node "k8s-k8sworkers-20163042-2" Volume is already exclusively attached to one node and can't be attached to another
I0105 10:24:00.434987       1 event.go:218] Event(v1.ObjectReference{Kind:"Pod", Namespace:"preproduction", Name:"mongo-0", UID:"5492929f-f1b4-11e7-92c5-000d3ab769d6", APIVersion:"v1", ResourceVersion:"22247369", FieldPath:""}): type: 'Warning' reason: 'FailedAttachVolume' Multi-Attach error for volume "pvc-8743f77c-a472-11e7-b780-000d3ab769d6" Volume is already exclusively attached to one node and can't be attached to another
W0105 10:24:00.435103       1 reconciler.go:267] Multi-Attach error for volume "pvc-4c0b9e2b-a48d-11e7-a344-000d3ab7665a" (UniqueName: "kubernetes.io/azure-disk//subscriptions/3770e200-bb58-4d3b-afcb-66c7ce083c3f/resourceGroups/k8s-fleeters-cluster-preproduction/providers/Microsoft.Compute/disks/fleeters-59cd2dcd-dynamic-pvc-4c0b9e2b-a48d-11e7-a344-000d3ab7665a") from node "k8s-k8sworkers-20163042-3" Volume is already exclusively attached to one node and can't be attached to another
I0105 10:24:00.435139       1 event.go:218] Event(v1.ObjectReference{Kind:"Pod", Namespace:"integration", Name:"grafana-1826545959-8qw5q", UID:"20425f47-f1f7-11e7-92c5-000d3ab769d6", APIVersion:"v1", ResourceVersion:"22791080", FieldPath:""}): type: 'Warning' reason: 'FailedAttachVolume' Multi-Attach error for volume "pvc-4c0b9e2b-a48d-11e7-a344-000d3ab7665a" Volume is already exclusively attached to one node and can't be attached to another
W0105 10:24:00.535432       1 reconciler.go:267] Multi-Attach error for volume "pvc-4c0b9e2b-a48d-11e7-a344-000d3ab7665a" (UniqueName: "kubernetes.io/azure-disk//subscriptions/3770e200-bb58-4d3b-afcb-66c7ce083c3f/resourceGroups/k8s-fleeters-cluster-preproduction/providers/Microsoft.Compute/disks/fleeters-59cd2dcd-dynamic-pvc-4c0b9e2b-a48d-11e7-a344-000d3ab7665a") from node "k8s-k8sworkers-20163042-3" Volume is already exclusively attached to one node and can't be attached to another
I0105 10:24:00.535472       1 event.go:218] Event(v1.ObjectReference{Kind:"Pod", Namespace:"integration", Name:"grafana-1826545959-8qw5q", UID:"20425f47-f1f7-11e7-92c5-000d3ab769d6", APIVersion:"v1", ResourceVersion:"22791080", FieldPath:""}): type: 'Warning' reason: 'FailedAttachVolume' Multi-Attach error for volume "pvc-4c0b9e2b-a48d-11e7-a344-000d3ab7665a" Volume is already exclusively attached to one node and can't be attached to another
W0105 10:24:00.535692       1 reconciler.go:267] Multi-Attach error for volume "pvc-8743f77c-a472-11e7-b780-000d3ab769d6" (UniqueName: "kubernetes.io/azure-disk//subscriptions/3770e200-bb58-4d3b-afcb-66c7ce083c3f/resourceGroups/k8s-fleeters-cluster-preproduction/providers/Microsoft.Compute/disks/fleeters-59cd2dcd-dynamic-pvc-8743f77c-a472-11e7-b780-000d3ab769d6") from node "k8s-k8sworkers-20163042-2" Volume is already exclusively attached to one node and can't be attached to another
I0105 10:24:00.535715       1 event.go:218] Event(v1.ObjectReference{Kind:"Pod", Namespace:"preproduction", Name:"mongo-0", UID:"5492929f-f1b4-11e7-92c5-000d3ab769d6", APIVersion:"v1", ResourceVersion:"22247369", FieldPath:""}): type: 'Warning' reason: 'FailedAttachVolume' Multi-Attach error for volume "pvc-8743f77c-a472-11e7-b780-000d3ab769d6" Volume is already exclusively attached to one node and can't be attached to another
W0105 10:24:00.636100       1 reconciler.go:267] Multi-Attach error for volume "pvc-8743f77c-a472-11e7-b780-000d3ab769d6" (UniqueName: "kubernetes.io/azure-disk//subscriptions/3770e200-bb58-4d3b-afcb-66c7ce083c3f/resourceGroups/k8s-fleeters-cluster-preproduction/providers/Microsoft.Compute/disks/fleeters-59cd2dcd-dynamic-pvc-8743f77c-a472-11e7-b780-000d3ab769d6") from node "k8s-k8sworkers-20163042-2" Volume is already exclusively attached to one node and can't be attached to another
W0105 10:24:00.636142       1 reconciler.go:267] Multi-Attach error for volume "pvc-4c0b9e2b-a48d-11e7-a344-000d3ab7665a" (UniqueName: "kubernetes.io/azure-disk//subscriptions/3770e200-bb58-4d3b-afcb-66c7ce083c3f/resourceGroups/k8s-fleeters-cluster-preproduction/providers/Microsoft.Compute/disks/fleeters-59cd2dcd-dynamic-pvc-4c0b9e2b-a48d-11e7-a344-000d3ab7665a") from node "k8s-k8sworkers-20163042-3" Volume is already exclusively attached to one node and can't be attached to another
I0105 10:24:00.636168       1 event.go:218] Event(v1.ObjectReference{Kind:"Pod", Namespace:"integration", Name:"grafana-1826545959-8qw5q", UID:"20425f47-f1f7-11e7-92c5-000d3ab769d6", APIVersion:"v1", ResourceVersion:"22791080", FieldPath:""}): type: 'Warning' reason: 'FailedAttachVolume' Multi-Attach error for volume "pvc-4c0b9e2b-a48d-11e7-a344-000d3ab7665a" Volume is already exclusively attached to one node and can't be attached to another
I0105 10:24:00.636183       1 event.go:218] Event(v1.ObjectReference{Kind:"Pod", Namespace:"preproduction", Name:"mongo-0", UID:"5492929f-f1b4-11e7-92c5-000d3ab769d6", APIVersion:"v1", ResourceVersion:"22247369", FieldPath:""}): type: 'Warning' reason: 'FailedAttachVolume' Multi-Attach error for volume "pvc-8743f77c-a472-11e7-b780-000d3ab769d6" Volume is already exclusively attached to one node and can't be attached to another
W0105 10:24:00.736504       1 reconciler.go:267] Multi-Attach error for volume "pvc-8743f77c-a472-11e7-b780-000d3ab769d6" (UniqueName: "kubernetes.io/azure-disk//subscriptions/3770e200-bb58-4d3b-afcb-66c7ce083c3f/resourceGroups/k8s-fleeters-cluster-preproduction/providers/Microsoft.Compute/disks/fleeters-59cd2dcd-dynamic-pvc-8743f77c-a472-11e7-b780-000d3ab769d6") from node "k8s-k8sworkers-20163042-2" Volume is already exclusively attached to one node and can't be attached to another

By the way it's an issue that the Azure community faced already and me aswell. Someone experienced the same kind of issues yesterday on an other Git thread. https://github.com/Azure/ACS/issues/12
That's really critical, during the updates yesterday the Machines went down in a normal way but the Azure API was really slow and the mounting and detaching too.
Kubernetes was trying to balance my pods with their disks to another worker since the actual one was upgrading (more than 40min per machine), but it was impossible since the disks weren't able to detach from that worker.
I almost waited more than 1 hour to have my 3 mongoDb Azure Disks attached on my ReplicaSet after each machine reboot. I tought that Azure Disks where safe in production but basically it wasn't yesterday.
Conclusion, i'm not able to mount any disks on my statefullsets since yesterday on my Staging cluster.
Rebooted : kube-controller-manager, kubelet on the concerned workers, even restarted the virtual machines, it's always the same detach/attach error.
Please guys do you have any info on that, my Direct Professional Support plan mail is still not answered since 24h...
How to reproduce it (as minimally and precisely as possible):
Apparently someone else experienced that : https://github.com/Azure/ACS/issues/12

❯ az vm update -g k8svl -n k8s-pool01-xxxxx-1
Cannot attach data disk 'k8svl-dynamic-pvc-xxxxx' to VM 'k8s-pool01-11577755-1' because the disk is currently being detached or the last detach operation failed. Please wait until the disk is completely detached and then try again or delete/detach the disk explicitly again.

@andyzhangx according to azure portal, the disk is mounted in vm-1 the same one that is failling with the v update command
I rebooted the node, still same problem.

@andyzhangx detached the disk manually (in portal) restarted every kubelet, run vm status in every node (no errors now), deleted the pod, k8s still complainign with same error
@andyzhangx can you confirm to me if this is marked as a critical problem in azure or I need to phone and open a new ticket?
This is critical and is blocking my production environment

Update this thread:
Recently I fixed a race condition issue which could cause Multi-Attach disk error, the fix has been merged into v1.10, I am trying to cherry-pick this fix to other k8s version, you could find details about this issue here:
https://github.com/andyzhangx/Demo/blob/master/issues/README.md#1-multi-attach-disk-error

For the moment i can say that since January it's stable with a cluster on 1.8.5 Kubernetes version. Didn't have any other mount/umount problems...

I'm closing this issue, with Kubernetes 1.10 and the lasts updates there is no more issue about disks on Azure.
Great Thanks to @andyzhangx you did a really good job !

@theobolo that not accurate: https://github.com/Azure/AKS/issues/477 still happening in 10.3

@jalberto Alright, following your case i'm reopening this issue, but i have to say : on a 1.10.2 Kubernetes cluster deployed with the 0.16.2 ACS Engine version, i have 0 problem since 1 month about Mounting and Unmounting disks.
Since you'r on AKS (GA) maybe that the deployement is slightly different, i didn't take a look at it.
I precise that i run more than 150 pods on that Cluster with more than 50% of them mounting "managed disks" with Premium Tier.
@andyzhangx I'll try the @jalberto scenario on my cluster to at least i hope reproduce the issue.
Cheers

@theobolo I agree! this actually was solved already twice as far I can remember (with hard work by @andyzhangx) , but somehow it made a comeback, and actually that worries me as raises lot of concerns about a safe upgrades

@jalberto @andyzhangx Alright guys i managed to reproduce that issue on my cluster (reminder : 1.10.2 and No AKS just ACS)
I did :

helm install stable/grafana (persistence enabled)
wait 5 sec and delete the grafana pod
the new pod is showing the multi-attach error....

Take a look at this gif ;)

But basically as @andyzhangx said, i waited 1 min with the pod in this "error" state and then the pod mounted the PV as expected ... and Grafana went up healthy :

Also i did another test but with the "managed-premium" class for the disks and not the "default" one.
I did manage to reproduce the bug, with the same methodology. But at the same time after 1 or 2 min the pod recover by itseft ... So i don't know if it's a AKS specific issue or something else, because on my cluster it's working fine.


HtmlImage: fix Image.onload() being called immediately instead of later

This PR does the following:

Fix a bug where Image.onload() is processed immediately rather than after the running JS code.

Test cases used
<html>
<head>
<script>
function test() {
    console.log('in');
    var image = new Image();
    image.onload = function () { console.log("Image.onload") };
    image.src = '1x1.png';
    console.log('out');
}
</script>
</head>
<body>
<button onclick="test()">test</button>
</body>
</html>

Real browser: in, out, Image.onload
HtmlUnit: in, Image.onload, out

Thanks


CA-10304 badly detecting delayed methods as delayed jobs

Spec pretty much tells the story but if we delay a method on a class we
do not want that to be detected as the job being already scheduled. This
now does a bit more meaningful job name parsing in ruby and matches on
that. The delayed method handler is no longer getting picked up.

Coverage decreased (-1.3%) to 65.714% when pulling 6009b0967722db3b1ea2301bdd6e9feea196dc30 on charbolt_16_14_healthchecks_in_background_CA-10304 into c3508e95addb5a5818b8da8fecb621fe41a6220c on master.

LGTM


Revert "Update to 0.13.4"

Reverts conda-forge/bioat-feedstock#7

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe/meta.yaml:

ℹ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.

For the host section of the recipe, you should usually use python {{ python_min }} for the python entry.
For the run section of the recipe, you should usually use python >={{ python_min }} for the python entry.
For the test.requires section of the recipe, you should usually use python {{ python_min }} for the python entry.
If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12365898344. Examine the logs at this URL for more detail.

@conda-forge-admin, please rerender


[Feature request] Condition on previous text

Hi,
It's me again. It would be pretty cool to add the condition_on_previous_text flag to whisper-webgpu as in:
https://github.com/openai/whisper/blob/7858aa9c08d98f75575035ecd6481f462d66ca27/whisper/transcribe.py#L278
Setting it to "false" can greatly reduce the failure loop cases. In minority languages is pretty usual.

@Huguet57 Unfortunately, we won't be adding any more features to whisper-turbo until ratchet reaches feature parity.
We are pretty close to running Whisper on the new OSS framework (see PR here).
Once we've done that, we intend to add all sampling methods from the original repo.

Works for me! Even better if OSS.


[1.13.1] Mountpoint for cgroup not found

I am seeing the following on kernel-ml-4.10.0-1.el7.elrepo.x86_64 on CentOS 7.
Additionally, I also see the following when attempting to start any container
Feb 24 08:56:30 ip-172-27-2-34 dockerd: time="2017-02-24T08:56:30.645508188Z" level=error msg="containerd: start container" error="oci runtime error: container_linux.go:247: starting container process caused \"process_linux.go:258: applying cgroup configuration for process caused \\\"mountpoint for cgroup not found\\\"\"\n" id=ac5ae1d8ff85996c406721bf8a0df30f0b56c5112445977ae6f9185aac07fe31
Feb 24 08:56:30 ip-172-27-2-34 dockerd: time="2017-02-24T08:56:30.646958144Z" level=error msg="Create container failed with error: oci runtime error: container_linux.go:247: starting container process caused \"process_linux.go:258: applying cgroup configuration for process caused \\\"mountpoint for cgroup not found\\\"\"\n"

When I try to restart the docker daemon
Feb 24 14:41:16 ip-172-27-2-34 systemd: Failed to create cgroup /user.slice: Read-only file system
Feb 24 14:41:16 ip-172-27-2-34 systemd: Failed to realize cgroups for queued unit user.slice: Read-only file system
Feb 24 14:41:16 ip-172-27-2-34 systemd: Failed to create cgroup /system.slice: Read-only file system
Feb 24 14:41:16 ip-172-27-2-34 systemd: Failed to realize cgroups for queued unit proc-fs-nfsd.mount: Read-only file system
Feb 24 14:41:16 ip-172-27-2-34 systemd: Failed to create cgroup /system.slice: Read-only file system
Feb 24 14:41:16 ip-172-27-2-34 systemd: Failed to realize cgroups for queued unit cloud-init-local.service: Read-only file system
Feb 24 14:41:16 ip-172-27-2-34 systemd: Failed to create cgroup /system.slice: Read-only file system
Feb 24 14:41:16 ip-172-27-2-34 systemd: Failed to realize cgroups for queued unit run-docker-netns-default.mount: Read-only file system
Feb 24 14:41:16 ip-172-27-2-34 systemd: Failed at step CGROUP spawning /usr/bin/dockerd: No such file or directory
...
...
Feb 24 14:41:16 ip-172-27-2-34 systemd: Failed to realize cgroups for queued unit rhel-readonly.service: Read-only file system
Feb 24 14:41:16 ip-172-27-2-34 systemd: docker.service: main process exited, code=exited, status=219/CGROUP
Feb 24 14:41:16 ip-172-27-2-34 systemd: Failed to start Docker Application Container Engine.
Feb 24 14:41:16 ip-172-27-2-34 systemd: Unit docker.service entered failed state.
 Why is this happening? What can a person do if they can't reboot the server?
Output of docker version:
Client:
 Version:      1.13.1
 API version:  1.26
 Go version:   go1.7.5
 Git commit:   092cba3
 Built:        Wed Feb  8 06:38:28 2017
 OS/Arch:      linux/amd64

Server:
 Version:      1.13.1
 API version:  1.26 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   092cba3
 Built:        Wed Feb  8 06:38:28 2017
 OS/Arch:      linux/amd64
 Experimental: false

Output of docker info:
Client:
 Version:      1.13.1
 API version:  1.26
 Go version:   go1.7.5
 Git commit:   092cba3
 Built:        Wed Feb  8 06:38:28 2017
 OS/Arch:      linux/amd64

Server:
 Version:      1.13.1
 API version:  1.26 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   092cba3
 Built:        Wed Feb  8 06:38:28 2017
 OS/Arch:      linux/amd64
 Experimental: false
[root@ip-172-27-2-34 ~]# docker info
Containers: 4353
 Running: 0
 Paused: 0
 Stopped: 4353
Images: 83
Server Version: 1.13.1
Storage Driver: overlay2
 Backing Filesystem: xfs
 Supports d_type: false
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: aa8187dbd3b7ad67d8e5e3a15115d3eef43a7ed1
runc version: 9df8b306d01f59d3a8029be411de015b7304dd8f
init version: 949e6fa
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.10.0-1.el7.elrepo.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 16
Total Memory: 29.43 GiB
Name: ip-172-27-2-34
ID: VTFK:IZAA:3AOQ:3HFS:73AA:VNYJ:NTDI:X2U5:FQED:GTEC:NROP:JTQH
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false

Docker config
[Unit]
Description=Docker Application Container Engine
Documentation=https://docs.docker.com
After=network.target firewalld.service

[Service]
Type=notify
# the default is not to use systemd for cgroups because the delegate issues still
# exists and systemd currently does not support the cgroup feature set required
# for containers run by docker
ExecStart=/usr/bin/dockerd --storage-driver=overlay2
ExecReload=/bin/kill -s HUP $MAINPID
# Having non-zero Limit*s causes performance problems due to accounting overhead
# in the kernel. We recommend using cgroups to do container-local accounting.
LimitNOFILE=infinity
LimitNPROC=infinity
LimitCORE=infinity
# Uncomment TasksMax if your systemd version supports it.
# Only systemd 226 and above support this version.
#TasksMax=infinity
TimeoutStartSec=0
# set delegate yes so that systemd does not reset the cgroups of docker containers
Delegate=yes
# kill only the docker process, not all processes in the cgroup
KillMode=process

[Install]
WantedBy=multi-user.target

Additional environment details (AWS, VirtualBox, physical, etc.):
AWS

Note that kernel 4.10 is a non-standard kernel for CentOS 7 (CentOS 7 ships with 3.10), which is not supported.
Feb 24 14:41:16 ip-172-27-2-34 systemd: Failed to create cgroup /user.slice: Read-only file system

That error is coming from systemd, not docker.
Feb 24 14:41:16 ip-172-27-2-34 systemd: Failed to realize cgroups for queued unit rhel-readonly.service: Read-only file system

Is that a service you enabled? Looks like that service is intended to make a read-only rootfs? http://www.linuxquestions.org/questions/red-hat-31/read-only-root-file-system-in-rhel-7-a-4175527807/

@thaJeztah It is not something that I enabled. It happened after starting/stopping enough containers.
I'll downgrade my kernel and see if I can reproduce the issue again.

You have not got the cgroup mounts which are needed, the message suggests that they cannot be mounted as the filesystem is read only. I am surprised docker runs at all without the correct mounts.

Yeah, it looks like your system has booted with the tmpfs mount for /sys/fs/cgroup but without any of the actual cgroup mounts. What systemd version are you running / what is your configuration / are there any errors when booting your machine?

It was a Centos7 AMI from AWS. There were no errors when booting the
machine. Containers would start/run/stop just fine until a certain point
thousands of containers down the line. Then these errors started happening.
systemd-219-30.el7_3.7.x86_64

I had the https://elrepo.org/tiki/tiki-index.php kernel-ml installed. The
docker config was using overlay2 driver which was available due to the
kernel upgrade via kernel-ml.
On Sun, Mar 12, 2017 at 11:01 PM, Aleksa Sarai<EMAIL_ADDRESS>wrote:

Yeah, it looks like your system has booted with the tmpfs mount for
/sys/fs/cgroup but without any of the actual cgroup mounts. What systemd
version are you running / what is your configuration / are there any errors
when booting your machine?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/issues/31337#issuecomment-286004908,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACRa5edoq8YjHonhSdPkNl-yFtgkMVhgks5rlLGXgaJpZM4MLTn7
.


completed part 1 of the assignment again

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Submitting completed assignment after having tested the script
What did you learn from the changes you have made?
Wildcards are very important for bulk changes. Pay attention to the relative path.
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
I started with doing smaller steps i.e. cd into each sub-folder and work there. But then I realized I can do it all at once with a complete path.
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
I had to refer back to the scratchpad a few times.
How were these changes tested?
I ran each command individually before pasting in the assignment. In the end I also ran the entire script again.
A reference to a related issue in your repository (if applicable)
Checklist

[x] I can confirm that my changes are working as intended

you did a great job here!
Please go ahead and close this pull request now. Thanks!


Garmin LIDAR-Lite v4 consistently resets without logging any errors after ~60 seconds

I am running an OpenThread application on the LIDAR-Lite v4. This application works completely as expected and without errors on the nRF52840 DK. When I run it on the Garmin device, it consistently resets without logging any errors after about 60 seconds of operation, which is incredibly difficult to debug. It appears to me that there is a conflict between the peripherals required by the sensor driver and the ones required by OpenThread. Can someone please provide me with a complete list of peripherals used by the sensor library?
The only hint available is in this repository on line 36 of lidar_lite_interface.h: TIMER1 is being accessed through register writes. NOTE: If timers are going to be used by third parties TIMER1 cannot be used. What does this mean? Does the SoC communicate with the FPGA via TIMER1? If that's the case then it should have been clearly stated somewhere, because it breaks the 802.15.4 driver in the Nordic Semiconductor SDK.

The TIMER1 peripheral is used by the ANT Library so it cannot be used in your application.
The ANT Library is based on a SoftDevice. Please refer to the section 7 in the following document for SOC resource requirements for peripherals that are occupied by the SoftDevice.
https://www.thisisant.com/assets/resources/Stack Documents/S332_SDS_v2.0.pdf
The ANT Library also uses TIMER1, I2C, SPI, SAADC, and PPI resources.


The term 'Get-WmiObject' is not recognized

Hi ,
I find Getting WMI Objects (Get-WmiObject) ,and try to use it.
But the powershell can not recognize it.
Steps to reproduce
 Get-WmiObject -List

Expected behavior
__SecurityRelatedClass                  __NTLMUser9X
__PARAMETERS                            __SystemSecurity
__NotifyStatus                          __ExtendedStatus
Win32_PrivilegesStatus                  Win32_TSNetworkAdapterSettingError
Win32_TSRemoteControlSettingError       Win32_TSEnvironmentSettingError
...

Actual behavior
Get-WmiObject : The term 'Get-WmiObject' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ Get-WmiObject -List
+ ~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Get-WmiObject:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Environment data

> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      6.0.0-beta
PSEdition                      Core
GitCommitId                    v6.0.0-beta.6
OS                             Microsoft Windows 10.0.10586
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Btw, the command works in  this version,which come with win10
PS C:\Users\clu> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.0.10586.1045
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.10586.1045
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

Get-WmiObject have been deprecated in PowerShell Core. Please use CIM cmdlet.

Docs Issue #1645

@iSazonov  what did you mean by CIM?
It seems  cim can not be recognized too.
PS C:\Program Files\PowerShell\6.0.0-beta.6> cim win32_service -Filter "name='LBS_MONITOR'"
cim : The term 'cim' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the s
pelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ cim win32_service -Filter "name='LBS_MONITOR'"
+ ~~~
    + CategoryInfo          : ObjectNotFound: (cim:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

@iSazonov  thanks,I have google CIM, and find the docs

finally, I come with this command
Get-CimInstance -ClassName Win32_Service -Filter "name='LISA_43_Dev_Batch'" | select Name,DisplayName,StartMode,State,StartName,SystemName,Description |Format-Table -AutoSize

@chucklu - Are you asking a question about this command? Does it work as you expected?
BTW, did you ever work at Novell?

@Liturgist  no problem now, and this issue can be closed.
I am in China, have no idea about Novell.

Tried Get-WmiObject based on web research, got the error that it's not recognized, found this from 2017.
So it's 2021 now, and I'm trying the new thing, Get-CimInstance.
Big surprise: "Get-CimInstance' is not recognized as an internal or external command. Well now, that didn't last long. My search for how to use this stuff continues.

Hi ,
I find Getting WMI Objects (Get-WmiObject) ,and try to use it.
But the powershell can not recognize it.
Steps to reproduce
 Get-WmiObject -List

Expected behavior
__SecurityRelatedClass                  __NTLMUser9X
__PARAMETERS                            __SystemSecurity
__NotifyStatus                          __ExtendedStatus
Win32_PrivilegesStatus                  Win32_TSNetworkAdapterSettingError
Win32_TSRemoteControlSettingError       Win32_TSEnvironmentSettingError
...

Actual behavior
Get-WmiObject : The term 'Get-WmiObject' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ Get-WmiObject -List
+ ~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Get-WmiObject:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Environment data
> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      6.0.0-beta
PSEdition                      Core
GitCommitId                    v6.0.0-beta.6
OS                             Microsoft Windows 10.0.10586
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0


🐛 Torch flashes for a moment after update to 3.4.0-3.5.1 (iOS)

What's happening?
I tried to preview image using torch='on' and at the beginning it flashes for a moment, and after a sec it turns on properly.
Reproduceable Code
const camera = useRef<Camera>(null);
const device = useCameraDevice(props.facing);
const format = useCameraFormat(device, Templates.FrameProcessingYUV);

<Camera
  ref={camera}
  style={styles.container}
  device={device}
  isActive={isActive}
  enableZoomGesture={true}
  zoom={props.zoom ?? 1}
  torch={'on'}
  format={format}
  pixelFormat='yuv'
  photo={true}
/>

Relevant log output
No relevant outputs.

Camera Device
{
  "maxZoom": 16,
  "hasFlash": true,
  "name": "Back Camera",
  "position": "back",
  "hasTorch": true,
  "supportsRawCapture": false,
  "supportsFocus": true,
  "physicalDevices": [
    "wide-angle-camera"
  ],
  "neutralZoom": 1,
  "minZoom": 1,
  "hardwareLevel": "full",
  "id": "com.apple.avfoundation.avcapturedevice.built-in_video:0",
  "supportsLowLightBoost": false,
  "sensorOrientation": "landscape-left",
  "isMultiCam": false
}

Device
iPhone XR (iOS 16.6)
VisionCamera Version
3.5.1
Can you reproduce this issue in the VisionCamera Example app?
Yes, I can reproduce the same issue in the Example app here
Additional information

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

One more thing I noticed:
It only works like this when the value of torch is constant
And this way the torch stays on even after deactivating the camera
if I add it like this:
torch={props.torch && isActive ? 'on' : 'off'}
then it works perfectly

https://github.com/mrousavy/react-native-vision-camera/assets/12185646/da42e678-895f-4b70-8ea1-8eecc98195a9

thanks I'll look into this soon!

Hey! I think this is fixed in the latest VisionCamera version :)


Fix redis tls bench to actually use tls

The non TLS source in redis-tls is removed, I have no idea what its purpose was.
The TLS source is given the default port 6379
The redis tls integration test is changed to use 6379
The redis tls bench is left as 6379 so it now correctly uses TLS

oh I see whats going on, the benches are currently testing shotover <-> db TLS but not client <-> shotover TLS.
While I think the benches should be changed to include TLS both ways, it will require complex redis-rs changes so lets just leave it for now.
I originally thought this issue was blocking the pubsub work but I've now realized it isnt actually.


🐛 [Bug] tracer/test_acc_tracer.py::AccTracerTest::test_addmm_0 AssertionError fails on A100 GPU

Bug Description
FX tracer test fails on A100 gpus
To Reproduce
pytest tracer/test_acc_tracer.py
Environment

Build information about Torch-TensorRT can be found by turning on debug messages

Torch-TensorRT Version (e.g. 1.0.0): latest
PyTorch Version (e.g. 1.0):
CPU Architecture:
OS (e.g., Linux):
How you installed PyTorch (conda, pip, libtorch, source):
Build command you used (if compiling from source):
Are you using local sources or building from archives:
Python version:
CUDA version:
GPU models and configuration:
Any other relevant information:

Additional context

cc: @frank-wei

Can you paste the error msg?

Master branch?

Yeah it occured on master branch. Here is the full log
Running FX Tracer tests
nox > pytest tracer/test_acc_tracer.py
nox > Warning: pytest is not installed into the virtualenv, it is located at /usr/local/bin/pytest. This might cause issues!  Thanks !!

The test passed in current main branch. https://app.circleci.com/pipelines/github/pytorch/TensorRT/1817/workflows/c0b2029f-dca7-4661-a72d-be5baebeb74a/jobs/8608/parallel-runs/0/steps/0-122
Thanks.

@frank-wei  This happens only on A100 GPU but passes on other GPUs. That's probably why it's passing in circle CI branch


Update network-mode env var to be consistent with other CLI flags.

The network-mode CLI flag had an env var set to
PLUGIN_TASK_NETWORK_MODE which broken convention with all other
CLI flags and made it confusing to switch between using drone.yaml
config files and running the plugin differently.
This change updates the env var to be consistent so the user
experience is smoother.

Isn't the network mode for the task as a whole and not the container? ie there's cpu container and cpu task env vars. I'm down to change this to not be specific to task but I just want to make sure it would make sense :) if it does we should still keep the old env var with coma separated so that it doesn't break for folks using it :)

@josmo the network mode is related to the task def. as you mention, therefore it's probably correct to keep the envvar as original and update the CLI flag. With this, would you prefer the current flag is updated or a second added to preserve backwards compatibility with both values checked and the original flag taking preference?

Are you meaning updating flag name to task-network-mode instead of network-mode ? in that case there wouldn't be any breaking changes since that would only impact the internals, the ENV vars would still be the same :) if that's what you mean then go for it :)

thanks for your time @josmo, I have pushed the discussed updates.

Thanks @jrasell you'll also need to change c.String("network-mode") to be c.String("task-network-mode") for the variable to get injected in :) it's around line 225 in main

This is been outstanding for a while, Feel free to reopen against main with the changes and I'll merge it in.


Arc 107 gpu fix offloading

This mandatory fix is for offloading from cpu to respective xpu /arc devices .
Since ipex is out of pytorch tree , converting tensors back from cpu to devices must require this fix for xpu/arc graphics card devices (cuda is implicit).
@sgugger @muellerzr

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Yes but in pytorch there is always a scope of implicit conversion to cuda (from or to meta) because pytorch supports cuda by default. But in case of xpu devices alone, (only for intel devices) if there is a need to offload from cpu to xpu devices this is required. Hence updated the check for only xpu devices.

Ok this is a more critical issue related to intel arc gpus (Exclusively) similar to the PR #1615 . Since the device "name" appears as cuda it is throwing the exception. I am working on a proper fix for this and this implies that a condition needs to be applied to check if it is really cuda or not.  Even though arc gpus are xpus, the torch.device(device_id) equals "cuda" . This is an ipex design change following meta's/stock pytorch directives.  Agree the device is automatically specified but a check needs to be there to ensure that it does not break for arc gpus specifically. For core data center gpus (core xpus) it is fine.
@sgugger  just for context. Keeping it in draft state for now.


Ember 2.3 this.container deprecation

See http://emberjs.com/deprecations/v2.x/#toc_injected-container-access

See #382

Sorry! Overlooked it :)


2.90 release notes missing glTF header

https://wiki.blender.org/wiki/Reference/Release_Notes/2.90/IO
^the glTF release notes are there, but as a subheader under "Instances", so they don't appear in the table of contents. Is that easy to fix? I can't seem to sign in to the wiki with my developer account. :/

Fixed!
Thanks :)

Thank you!


iframe not support?

hi,
on iframes tag not work!!!!!!
why? ........

This issue is related to #59


copilot chat can not send message or login in

I can use the github copilot to generate code, but can not send message or  login in the copilot chat！

Copilot Chat Extension Version:0.22.1
VS Code Version: 1.95.1
OS Version: Windows_NT x64 10.0.22000
Logs:
2024-11-01 12:55:00.083 [error] [auth] Client network socket disconnected before secure TLS connection was established
2024-11-01 12:55:11.673 [error] [auth] Retrying auth
2024-11-01 12:55:22.543 [error] [auth] auth: Error: network error
Steps to Reproduce: just open the chat.

@chrmarti this sounds like a proxy related issue so I've passed it to you

@wcool1 Please check the output of F1 > Developer: GitHub Copilot Chat Diagnostics in VS Code and append it here.

@wcool1 Please check the output of F1 > Developer: GitHub Copilot Chat Diagnostics in VS Code and append it here.请 wcool1 检查 VS Code 中 F1 > Developer: GitHub Copilot Chat Diagnostics 的输出，并将其附加在这里。

Thanks.
Hello, sir. when i want to check and open the Developer: GitHub Copilot Chat Diagnostics, it just shows that the plugin is activating, but there is no response.
But i can give you the errors in the console of developer tools ,i don`t know whether it matters .if there is anything  i can help ,just let me know :
[Extension Host] Error fetching remote message TypeError: fetch failed
at node:internal/deps/undici/undici:13185:13
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at globalThis.fetch (file:///d:/all%20kinds%20of%20tools/Microsoft%20VS%20Code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:158:3389)
at c:\Users\86131.vscode\extensions\divyanshuagrawal.competitive-programming-helper-2024.11.1730722547\dist\extension.js:1:178352
Failed to load resource: net::ERR_CONNECTION_CLOSED
log.ts:439   ERR [network] #22: https://az764295.vo.msecnd.net/extensions/chat.json - error GET Failed to fetch
log.ts:429  WARN Failed to fetch chat participant registry TypeError: Failed to fetch
at i$s (request.ts:24:21)
at requestService.ts:31:44
at prt.c (request.ts:81:25)
at prt.request (requestService.ts:31:15)
at PPe.l (chatAgents.ts:651:45)
at PPe.k (chatAgents.ts:644:8)
at chatAgents.ts:647:21
request.ts:24
GET https://az764295.vo.msecnd.net/extensions/chat.json net::ERR_CONNECTION_CLOSED
log.ts:439   ERR [network] #23: https://az764295.vo.msecnd.net/extensions/chat.json - error GET Failed to fetch
log.ts:429  WARN Failed to fetch chat participant registry TypeError: Failed to fetch
at i$s (request.ts:24:21)
at requestService.ts:31:44
at prt.c (request.ts:81:25)
at prt.request (requestService.ts:31:15)
at PPe.l (chatAgents.ts:651:45)
at PPe.k (chatAgents.ts:644:8)
at chatAgents.ts:647:21

having the same issue with the same versions of VS Code and Copilot

having the same issue with the same versions of VS Code and Copilot遇到与 VS Code 和 Copilot 相同版本的问题

I finally found the problem :there is  an AI plugin called AIDE in my vscode ,when i closed it  ,it make sense. so just have a try to close the other AI plugin to avoid conflict. maybe it can work!


Add example(s) for leaflet_graph

Tagging @joyliujoyliu, @jdpye for possible interest.

Closed by 38409a3f04779068edd1e4fe14eeca1f4bfbb62e


Extension is not installable on any currently installed product

Computer (please complete the following information):

Windows Version: Windows 11 Pro
Visual Studio Version: Visual Studio 2022 Preview 17.4.0 Preview 4.0
AWS Toolkit for Visual Studio Version: AWS Toolkit v17

Install log
10/21/2022 1:22:07 PM - Microsoft VSIX Installer
10/21/2022 1:22:07 PM - -------------------------------------------
10/21/2022 1:22:07 PM - vsixinstaller.exe version:
10/21/2022 1:22:07 PM - 17.4.2116
10/21/2022 1:22:07 PM - -------------------------------------------
10/21/2022 1:22:07 PM - Command line parameters:
10/21/2022 1:22:07 PM - C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\ServiceHub\Services\Microsoft.VisualStudio.Setup.Service\VSIXInstaller.exe,\Mac\Home\Downloads\AWSToolkitPackage.v17.vsix
10/21/2022 1:22:07 PM - -------------------------------------------
10/21/2022 1:22:07 PM - Microsoft VSIX Installer
10/21/2022 1:22:07 PM - -------------------------------------------
10/21/2022 1:22:12 PM - Initializing Install...
10/21/2022 1:22:13 PM - Extension Details...
10/21/2022 1:22:13 PM - 	Identifier         : 0B82CB16-0E52-4363-9BC0-61E758689176
10/21/2022 1:22:13 PM - 	Name               : AWS Toolkit for Visual Studio 2022
10/21/2022 1:22:13 PM - 	Author             : Amazon Web Services
10/21/2022 1:22:13 PM - 	Version            : <IP_ADDRESS>
10/21/2022 1:22:13 PM - 	Description        : The AWS Toolkit for Visual Studio is an extension for Microsoft Visual Studio on Windows that makes it easier for developers to develop, debug, and deploy .NET applications using Amazon Web Services.
10/21/2022 1:22:13 PM - 	Locale             : en-US
10/21/2022 1:22:13 PM - 	MoreInfoURL        : https://aws.amazon.com/visualstudio/
10/21/2022 1:22:13 PM - 	InstalledByMSI     : False
10/21/2022 1:22:13 PM - 	SupportedFrameworkVersionRange : [4.5,)
10/21/2022 1:22:13 PM -
10/21/2022 1:22:17 PM - 	SignatureState     : ValidSignature
10/21/2022 1:22:17 PM - 	SignedBy           : Amazon.com, Inc.
10/21/2022 1:22:17 PM - 	Certificate Info   :
10/21/2022 1:22:17 PM - 		-------------------------------------------------------
10/21/2022 1:22:17 PM - 		[Subject]       : CN="Amazon.com, Inc.", O="Amazon.com, Inc.", L=Seattle, S=Washington, C=US
10/21/2022 1:22:17 PM - 		[Issuer]        : CN=DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1, O="DigiCert, Inc.", C=US
10/21/2022 1:22:17 PM - 		[Serial Number] : 0E4D3D377B5756257402C169EEED0D47
10/21/2022 1:22:17 PM - 		[Not Before]    : 9/26/2022 8:00:00 PM
10/21/2022 1:22:17 PM - 		[Not After]     : 9/27/2023 7:59:59 PM
10/21/2022 1:22:17 PM - 		[Thumbprint]    : ACFA520F8944C9B926BCDB567215434CD0201FDC
10/21/2022 1:22:17 PM -
10/21/2022 1:22:17 PM - 	Supported Products :
10/21/2022 1:22:17 PM - 		Microsoft.VisualStudio.Community
10/21/2022 1:22:17 PM - 			Version : [17.0,18.0)
10/21/2022 1:22:17 PM - 			ProductArchitecture : amd64
10/21/2022 1:22:17 PM -
10/21/2022 1:22:17 PM - 	References         :
10/21/2022 1:22:17 PM - 	Prerequisites      :
10/21/2022 1:22:17 PM - 		-------------------------------------------------------
10/21/2022 1:22:17 PM - 		Identifier   : Microsoft.VisualStudio.Component.CoreEditor
10/21/2022 1:22:17 PM - 		Name         : Visual Studio core editor
10/21/2022 1:22:17 PM - 		Version      : [17.0,18.0)
10/21/2022 1:22:17 PM -
10/21/2022 1:22:17 PM - Signature Details...
10/21/2022 1:22:17 PM - 	Extension is signed with a valid signature.
10/21/2022 1:22:17 PM -
10/21/2022 1:22:17 PM - Searching for applicable products...
10/21/2022 1:22:17 PM - Found installed product - Global Location
10/21/2022 1:22:17 PM - Found installed product - Visual Studio Community 2022 Preview
10/21/2022 1:22:17 PM - VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products.
at VSIXInstaller.ExtensionService.GetInstallableDataImpl(IInstallableExtension extension, String extensionPackParentName, Boolean isRepairSupported, IStateData stateData, IEnumerable`1& skuData)
at VSIXInstaller.ExtensionService.GetInstallableData(String vsixPath, String extensionPackParentName, Boolean isRepairSupported, IStateData stateData, IEnumerable`1& skuData)
at VSIXInstaller.ExtensionPackService.IsExtensionPack(IStateData stateData, Boolean isRepairSupported)
at VSIXInstaller.ExtensionPackService.ExpandExtensionPackToInstall(IStateData stateData, Boolean isRepairSupported)
at VSIXInstaller.App.Initialize(Boolean isRepairSupported)
at VSIXInstaller.App.Initialize()
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
Any other information
I am using M1 Macbook Pro and using Parallels to use VS Studio 2022 Preview. The machine is newly built and no previous installment of AWS Toolkit

Hi @mlvncnxx , two things to look into:

are you able to install other extensions without issue?
are you running with administrative privileges on Windows? The Toolkit extension requires this in order to install

If you launch the Visual Studio Installer from the start menu, it might be worth trying to run a "Repair" to see if it adjusts anything, then rebooting, and trying to install the Toolkit again.

Hi @awschristou I've tried repairing the visual studio but nothing happened and still the same error. for other extensions, I actually just need the AWS Toolkit so I have not tried it. For my Windows, I'm running with administrative privileges as well.
I actually tried asking my other colleagues that are using m1 mac and parallel and they didn't encounter this error.

Checking if another extension installs successfully could help see if there is an issue with your Visual Studio installation. You might want to try uninstalling, then reinstalling Visual Studio, and restarting Windows, then try to install the AWS Toolkit again.
If installing the Toolkit continues to fail, please attach the whole log provided by the VSIX installer. Maybe there are some more clues in there.

Same issue.  Looks like the VSIX installer needs the ARM64 to be part of the productarchitecture in the extensions file.  It was working previously, but look like it's getting enforced with the latest install process.
See https://learn.microsoft.com/en-us/visualstudio/extensibility/arm64/target-arm64-visual-studio-extension?view=vs-2022

It looks like there is a requested use case using the Toolkit from Arm based MacBooks running (Arm based) Windows on Parallels.
The Toolkit does not support Arm64 Visual Studio at this time. The Toolkit's feature set needs to be tested using an Arm based system in order to determine which features do and do not work out of the box. For features that do not work, we will have to figure out what changes are required in order to support Arm.
I have created a more generalized feature request #302 to collect interest in Arm support. Please add a reaction to that request.
I will close this issue to avoid having duplicated issues open.

Same issue. Looks like the VSIX installer needs the ARM64 to be part of the productarchitecture in the extensions file. It was working previously, but look like it's getting enforced with the latest install process.
See https://learn.microsoft.com/en-us/visualstudio/extensibility/arm64/target-arm64-visual-studio-extension?view=vs-2022

This is easy. Enough.   Bump +1 here


Competitive Programming: Min-Max Algorithm In Game Theory

Description
I will explain the working and implementation of min-max algorithm in python alongwith its advantages and limitations.
Domain
Competitive Programming
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign

/assign


add support for protobuf and avro schema

Resolves #35.
@Raynos @malandrew

:clap: (shipit)

LGTM

:+1:


Extract package_index as third-party package

In #2089, @gotcha indicates that zc.buildout is using setuptools.package_index through its API.
I took a quick look at pip and its package index functionality is tucked carefully inside _internal.
To support use-cases like zc.buildout and other libraries that wish to interact programmatically with the package index, and to separate that functionality from setuptools' primary mission, perhaps setuptools.package_index should become a package in its own right. To avoid forking the behavior, setuptools could vendor an initial, compatible release.
Oh, there is already something called package-index which purports to do some of the things that setuptools' module does. That's too bad, because I'm all but certain that module won't be compatible with what setuptools needs or even what zc.buildout needs.
It looks like @mdrachuk created that package last year and hasn't yet made a non-pre-release. Misha, is that package in active use? How would you feel about merging our efforts and supporting a package that (at least initially) supports the setuptools.package_index API, but ultimately has the features/designs you require?

I am not sure how long zc.buildout will depend on setuptools.package_index.
zc.buildout depends on it deeply and I was not smart enough to remove both setuptools.easy_install and package_index dependencies.
I plan to look if the dependency on package_index can be removed when the release without easy_install is done.

Nevertheless, if extracting package_index is not too much work, it might help maintenance of zc.buildout.


How are asynchronous events handled?

How do you mean? They are all posted on the main thread.

How do you mean? They are all posted on the main thread.

When I have not yet obtained data from the network, the button is not available at this time, and the remote operation is invalid.

It causes a crash? All Remote does is forward events. It has know way of knowing if they are valid.


ci(vault): Use the correct vault for macos runners

What does this PR do?
Update the fetch_secret script to fetch secrets from the correct vault when running on macos runners.
Motivation
macos runners are not k8s runners, they can't reach the kv/k8s/gitlab-runner/datadog-agent vault leading to timeouts in after_script. Their access to vault is through a dedicated path, so:

We changed the vault policy for agent-devxinfra team to be an admin of this vault.
We put the codecov token and created a dedicated api_key on org2 for macos runners.
https://datadoghq.atlassian.net/browse/ACIX-497

Describe how to test/QA your changes

No more timeout error in the after_script for macos_runner jobs

WIP for macos_tests here

No error/timeout on other jobs

ok for codecov token here

Possible Drawbacks / Trade-offs
Additional Notes

/merge


Make match.router available from hooks

Feature Request
match.path is not available through any hook. I can access it by using withRouter, but if I am using hooks the idea (I believe) is not to use HOC anymore
I need it because  my routes are something of the line like
<Route path='/company/:companyId/dashboard/:mode'>
  <Component1 />
</Route>
<Route path='/dairy/:dairyId/dashboard/:mode'>
  <Component2 />
</Route>

both <Component1> and <Component2> use a commont <CommonComponent> which, among its lines, has
const onCallback = () => {
  // match.path has "/company/:companyId/dashboard/:mode" or "/dairy/:dairyId/dashboard/:mode" which is what I need
// but match is not available with the new router hooks, only from withRouter HOC
  const createUrl = match
      .path
      .replace(/:mode/, 'create') // I am in mode, let's say "view" and I navigate to "create"
      .replace(knowVariableWithRegexForIntermediateParameter, id) // replacing :companyId or :dairyId
  history.push(createUrl)
}

history is accessed with useHistory

Why don't you use the useRouteMatch() hook?

unless I misinterpreted the docs, useRouteMatch() requires me to pass the URL to match a parameter. But I do not want to match a parameter, but the url. I would have to know the URL in advance in order to pass it as a parameter, but that is what I want to access instead

If you don't pass a parameter the path of the closes parent route will be used.

I see, cool. That made it work. Thanks!
Is it documented anywhere? I couldn't find that behaviour on docs.
Closing, btw

Not sure about the documentation part, but I think that the code is documentation is enough: https://github.com/ReactTraining/react-router/blob/master/packages/react-router/modules/hooks.js#L43

It's not quite the same, especially because useRouteMatch can be used outside of a Route.
The Typescript defs for it reflect this (it returns a the match object or null), which makes it difficult to use.
https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/react-router/index.d.ts#L160


Make spelling for Thearian consistent.

I think Thearian is better than Therian but I guess it could go either way? 🤷

@phuff thanks for these edits!  are you also able to recompile the PDFs (pdflatex) to go along with these changes?  then i can merge them in directly.  And I agree-- Thearian is a better spelling ("Earth" re-arranged)

Oh snap.  I didn't think about the pdfs. Sorry.  I don't have a functioning latex on my work machine.  I promise to not make any more PRs without an accompanying pdf.  Sorry again.

oh, no problem-- i'll compile this one.  you could probably get them to compile on overleaf if you wanted.  it's fine if you want to edit the tex files alone (it just might take me longer to merge them in if i have to clean up the pull requests)

and i really appreciate your corrections!


Error 400: redirect_uri_mismatch

Full steps to reproduce the issue:

Download and extract https://github.com/jay0lee/got-your-back/releases/download/v1.37/gyb-1.37-linux-x86_64-glibc2.27.tar.xz
Run gyb --action create-project --email<EMAIL_ADDRESS>It completes smoothly.
Run gyb --email<EMAIL_ADDRESS>--action estimate

Actual outcome (what errors or bad behavior do you see instead?):
Select the actions you wish GYB to be able to perform for<EMAIL_ADDRESS>
[ ]  0)  Gmail Backup And Restore - read/write mailbox access
[*]  1)  Gmail Backup Only - read-only mailbox access
[ ]  2)  Gmail Restore Only - write-only mailbox access and label management
[ ]  3)  Gmail Full Access - read/write mailbox access and message purge
[ ]  4)  No Gmail Access

[ ]  5)  Groups Restore - write to G Suite Groups Archive
[ ]  6)  Storage Quota - Drive app config scope used for --action quota

      7)  Continue
7

Go to the following link in your browser:

        https://gyb-shortn.jaylee.us/xxxxxx

Enter verification code:

When I go to the said link, it says:

Found the solution: https://groups.google.com/d/msg/got-your-back/zi8tSfgXSPY/X8hCQc7cBwAJ
We need to choose Desktop app as the Application Type during creating an OAuth Client ID.


Validate and refactor PnP-Responsive-UI.js

Hi,
This PR is mainly code improvements. Fixed some issues I found on JSHint and refactored sideNavToggle.

Enable Strict Mode

Fix missing semicolon

Declare multiple variables with a single comma-delimited 'var' for better readability.

Declare FixRibbonAndWorkspaceDimensions function before it's assigned.

Refactor sideNavToggle block into one line instead of assigning multiple attributes and class.

Hi @populationtwo, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

Hi Edwin,
thx for this. We'll have a closer look soon and get things processed.

The undefined check is wrong, in most browsers this will just result in the error of currentScriptUrl being undefined in the console.
typeof currentScriptUrl  != "undefined"
Is the correct comparison, != is used as both sides are strings and type inference won't occur.
Sorry I was passing and I noticed this. Runs before Paulo makes me pull request

@populationtwo, your edits have modified the indentation, which results in every line being different. This makes it very difficult to see what changes you have made.

@HughAJWood @SPDoctor
Thank you for reviewing the PR. I'll update the PR.
I wasn't intentionally changed the indentation. It was a result of wrapping the JavaScript with self-invoking anonymous function.

@populationtwo - yeah, that makes sense :-)

Hi Edwin,
Thanks for your submission, and thanks to @HughAJWood and @SPDoctor for their reviews. I will wait for you to update the PR accordingly to their suggestions and then I will evaluate it again.
Thanks,
Paolo

@PaoloPia
Hi Paolo,
I have updated the PR. I will make a separate PR for the PnP-Sites-Core since it's on a different repo.
Thanks

Fix for undefined check is still incorrect:
typeof currentScriptUrl != "undefined"

Any updates on this one? - Just want to ensure that we get things moving around this as well. thx.

@VesaJuvonen
Sorry, haven't got a chance to update this. Got sidetracked with other stuff. I'll update it sometime next week.

@VesaJuvonen
I have updated the PR. Please review.
Thanks

thx Edwin, we'll have a look and process the change during upcoming days. Unfortunately we just missed October release, but let's get this processed for the November one.

Please remember that SP-Responsive-UI.js in this repo file is actually a copy of https://github.com/OfficeDev/PnP-Sites-Core/Core/OfficeDevPnP.Core/Resources/SP-Responsive-UI.js.

@SPDoctor
I created a separate PR here
Thanks

Let's close this one as a duplicate based on following entry in Sites-Core - https://github.com/OfficeDev/PnP-Sites-Core/pull/726


Added CORTX Drive for 2022 Hackathon

Added my project cortx-drive to /docs/integrations as submission for the 2022 Hackathon

View rendered doc/integrations/cortx-drive/README.md

@mukul-seagate11 please merge this hackathon entry.


automatic resting "oversight"?

If you have the auto rest timer quite low, say 30 seconds theres a good chance that it will override the current animation of say, woodcutting.
do you think its possible to check that only the idle animation is playing before intiating the resting animation?

Yep, definite oversight. I've submitted a new PR through for review, so hopefully you'll see it fixed in the next couple days

Should be fixed now


h2childchan: Investigate usage of RecvByteBufAllocator

The RecvByteBufAllocator API doesn't make much sense in the context of child channels. It was designed to help control the process of reading bytes from a socket, size the buffer when a read is done, and determine if we should keep reading. In this case the child channel is handed objects after this point. I think we should revisit this as a followup. Consider putting a TODO and creating a followup issue.
https://github.com/netty/netty/pull/6896#discussion_r132092664
https://github.com/netty/netty/pull/6896#discussion_r132091784

The RecvByteBufAllocator API could address inbound flow control (like in #7078) more precisely on a subchannel. The parent's reads will probably be "good enough" already, but I'd be prone to using RecvByteBufAllocator simply to reduce number of special cases ("oh, the child channel ignores X").


chore: Release v1.9.44

This is a promotion branch for the release v1.9.44

/ok-to-test

/ok-to-test

/build-deploy-preview

/build-deploy-preview

/build-deploy-preview skip-tests=true

/ok-to-test

/ok-to-test

/ok-to-test


Confusion about linearized state-space model

Dear all,
I'm working on the wind turbine model linearization now. I have read the theoretical paper and some posted questions in the discussion forum about the linearization process of OpenFAST. But I still have a major confusion about how to set the initial state and input of the linear state space model.
Below is the main setting when I perform the linearization (NREL 5.0 MW Baseline Wind Turbine) :
-I used OpenFAST with the input file attached below to linearize the NREL 5MW Onshore turbine in Region 2 about an 6 m/s wind speed.
-The linearization options CalcSteady is true; TrimCase is 2; TrimTol is 0.0001; TrimGain is 100; NLinTimes is 36.
-In the ServoDyn input file, the following sets were used: PCMode=0; VSContrl=1; VS_RtTq=43093.55; VS_RtGnSp=VS_Rgn2K=VS_Rgn2K=999e-9.
-2 DOFs were activated: GenDOF, and TwFADOF1 (first fore-aft mode); that is a total of 4 continuous states.
The linearization was performed successfully at 36 azimuth steps using GenTq trimming. The MBC transformation was performed by fx_mbc3 script afterward for the 36 output linearization file, and the resulting averaged A, B, C, D matrices for the state space model.
A Simulink model was then built with the state-space matrices and the response of the system was simulated. The simulink model is shown in the figure below. There is no input or state in the rotation frame, so inverse MBC transition is not included in the model. The output was observed by executing the simulation.

The encountered issues are the following:
(1) The output of the state-space model is not steady state. Fig. (1) shows the result for 100s calculation. The rotor speed and generator speed slowly decrease over time. The TTDspFA is the same. Fig. (2) shows the result for 10000s calculation. The rotor speed and generator speed decrease more. The TTDspFA is also. But after 800s, the TTDspFA is periodic steady. I am not sure whether these results are correct.

(2) I expect the output to be steady or periodically steady at the start of the calculation. So I use the initial states and inputs from the linear output file of OpenFAST at first azimuth (i.e. u_op and x_op data at first azimuth). Is this correct? Or should I use other initial states and inputs?
I’m sorry for the lengthy post, I wanted to make sure that everything is clear. I appreciate the help and am extremely thankful.

(3) There is another result that also bothers me. I noticed that the GenTq in outputfile (*.out) for the case mentioned above.  But the GenTq is 0 in every time step. I am very confused why this value is always zero. Under the 6 m/s wind speed and 0 pitch angle condition. The GenTq should be a value greater than zero to be able to stabilize.
By the way, I am not new to OpenFAST but new to the linearization function. So I'm sorry I might be asking something that lacks common sense.

Dear @jjonkman,
I found a confusing phenomenon during OpenFAST linearization.
When I enable both Variable speed generator DOF and Drivetrain rotational-flexibility DOF, the sensitity of generator torque to "ED Second time derivative of Variable speed generator DOF (internal DOF index = DOF_GeAz), rad/s" is -1.930157185050000e-05.
When I enable Variable speed generator DOF with  Drivetrain rotational-flexibility DOF disabled, the sensitity of generator torque to "ED Second time derivative of Variable speed generator DOF (internal DOF index = DOF_GeAz), rad/s" is -2.219550724349999e-06.
It is easy to understand the value of  -2.219550724349999e-06 = gearbox ratio/drivetrain inertia. But The value of  -1.930157185050000e-05 confused me a lot.
I used to think whether or not enable Drivetrain rotational-flexibility DOF would not largely affect the sensitities. I performed the simulation under different wind speeds, and found that the value of  -1.930157185050000e-05 did not vary with wind speeds. Please help me with the confusion.
Best regards,

Dear @ietqlw,
When the drivetrain DOF is enabled, the element of the input (B) matrix relating generator acceleration relative to the low-speed shaft (that is, ED Second time derivative of Variable speed generator DOF) and generator torque relative to the high-speed shaft should equal -GBRatio/(GenInerGBRatio^2) = -1/(GenInerGBRatio), where GenIner*GBRatio^2 is the generator inertia expressed relative to the low-speed shaft.
Best regards

Dear @jjonkman,
Your answer is very clear. Thank you very much for your kind reply.
Best regards,

Dear @ietqlw,
When the drivetrain DOF is enabled, the element of the input (B) matrix relating generator acceleration relative to the low-speed shaft (that is, ED Second time derivative of Variable speed generator DOF) and generator torque relative to the high-speed shaft should equal -GBRatio/(GenInerGBRatio^2) = -1/(GenInerGBRatio), where GenIner*GBRatio^2 is the generator inertia expressed relative to the low-speed shaft.
Best regards

Dear @jjonkman,
Thank you very much for your patient answer.  Could you please tell me the case when the drivetrain DOF is disabled? I used to think that the element of the input (B) matrix relating generator acceleration relative to the low-speed shaft and generator torque relative to the high-speed shaft should equal GBRatio/(GenIner_GBRatio^2+RotIner) . As for NREL 5MW wind turbine, the value should be -2.219550724349999e-06 whether other flexible DOFs are enabled or not. However, the linearization result shows that the value will be different from -2.219550724349999e-06 if I enable flexible DOFs such as FlapDOF1. Could you please help me analyze the reason?
Best regards,
liangwen qi

Dear @ietqlw,
I agree with your formulation if the rotor and drivetrain are completely rigid.  However,  if the rotor is flexible, then a step change in generator torque will result in deformation of the blades in addition to a change in generator acceleration, and this effect will be represented within the linearized matrices generated by OpenFAST.
Best regards,


doc: Use --reuse-values option for helm upgrade

Otherwise values set during helm install get wiped out.
Signed-off-by: Michi Mutsuzaki<EMAIL_ADDRESS>

Coverage increased (+0.002%) to 37.034% when pulling 48b4fb7a55225bcb716f8d24ff0cb36ba77624c8 on pr/michi/helmupgrade into f6d62b568cac0292f0ba01af8a2932bc3b0786e5 on master.

test-me-please


[2d] newrelic-cli recipe

create recipe
specify pre-req
write install steps via brew (brew manages the version)

https://github.com/newrelic/open-install-library/pull/478
from the spike 🔽

Create newrelic-infra recipe:
To create a new recipe, you need to create a PR to the open-install-library repository. Existing recipes to install the agent in linux can be used as reference.

Contributing recipes docs
Example: Agent install on ubuntu

Blocked until brew formula PR is merged