Logging does not install on .NET 4.5.1

I have the same issue as the closed:  #270 - as reported here: https://github.com/aspnet/EntityFramework/issues/3553

I tried to repro this now by pointing to aspnetcidev feed and I am unable to repro it...
after installing..
<?xml version="1.0" encoding="utf-8"?>
<packages>
  <package id="Microsoft.Framework.DependencyInjection.Abstractions" version="1.0.0-rc1-15654" targetFramework="net451" />
  <package id="Microsoft.Framework.Logging" version="1.0.0-rc1-15654" targetFramework="net451" />
  <package id="Microsoft.Framework.Logging.Abstractions" version="1.0.0-rc1-15654" targetFramework="net451" />
  <package id="Microsoft.Framework.Logging.Console" version="1.0.0-rc1-15654" targetFramework="net451" />
</packages>

On a old school 4,5,1 Class library project?

yeah right...in my case an old school 4.5.1 console application...

@kichalla Wrong package! (It is called .Extensions now)
But removing all previous package references unblocked me... Thanks!

I see this same exact error when trying to update packages in a .NET 4.5.2 class library project. I tried uninstalling and installing the packages but even that doesn't work.
Install-Package Microsoft.Extensions.Logging -Pre -Source https://www.myget.org/F/aspnetcidev/api/v3/index.json -Verbose

Attempting to gather dependencies information for package 'Microsoft.Extensions.Logging.1.0.0-rc2-15835' with respect to project '04 - Data Access\Contexts\DataAccess.Contexts', targeting '.NETFramework,Version=v4.5.2'
...
Added reference 'Microsoft.Extensions.Logging' to project 'DataAccess.Contexts'.
Install failed. Rolling back...
...
Install-Package : Failed to add reference to 'System.Collections.Concurrent'. Please make sure that it is in
the Global Assembly Cache.
At line:1 char:1
+ Install-Package Microsoft.Extensions.Logging -Pre -Source https://www ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Install-Package], Exception
    + FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PackageManagement.PowerShellCmdlets.Instal
   lPackageCommand

Am I missing something?

Have the same problem with .net 4.6 class library...


New Name?

I feel like this name might conflict with https://atmospherejs.com/alt/react-accounts-ui
Since this hasn't been published to Atmosphere yet, maybe you could change the name? Or else, maybe merge both projects somehow?

There being another project with the same name just tells me it is a good choice, it will be very easy to find! :dancer:

Closing this, now that  we've released it.


Update webpage

This PR updates the webpage to provide more user guidance on the rules of fizzbuzz.

woo hoo, now this PR is merged and the patch file and issue are getting created
https://github.com/some-fantastic/lesser-fizzbuzz/actions/runs/5556209207


keystrokes - show multiplier when greater than 2

great tool! holy crap this thing is awesome.
i recently just recorded something where i had to press enter 6 times and displaying the number was important.
I think it would be a better user experience when the same key is pressed to add a multiplier to it rather than showing it side by side

I think it would be a better user experience when the same key is pressed to add a multiplier to it rather than showing it side by side

That's a really cool idea.  I haven't seen that in other tools (including commercial ones) like QiPress that show onscreen keyboard indicators. I tried putting something together for that to describe pressing the spacebar 6x and here's what it looks like...

That said, I'm not sure how the dev would build this functionality.  It might be one moments where you have to create a separate explanation box explaining the next few screen actions.


Building latest development doesn't include basegame assets?

Describe your problem here.
I don't know what I'm doing wrong.
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
Nope.

compile with -D officialBuild, there's also a Project.xml flag for it


Integration broken

Description
When I try to send money from my bank account to m-pesa account, I get an error of 'Sorry, integration service is broken'.
This error also shows up when I check bank account balance and when buying airtime using bank account.
Steps to reproduce

Open Stax
Go to send money
Pay with Equity bank
Recipient network, enter m-pesa
Enter contact number
Enter amount

Expected result
I expect the transaction to go through and money sent from my bank account to m-pesa
Actual result
The transaction is not going through and I get an error 'Sorry, the integration service is broken'
Link to screenshots/screen recordings
https://drive.google.com/drive/folders/1cobIANMUi7LVTX1mp2fiUUO_CbatlMq3?usp=sharing
Device name
Redmi 9
Android OS
10 QP1A. 190711.020
Is your phone dual SIM or single SIM?
Dual SIM
Which telco are you using for this test?
Safaricom
Stax device ID or email address
<EMAIL_ADDRESS>

This has been fixed with the new release that we will be putting out early next week.


misc pkgs: Fewer cross attrs

Motivation for this change
Progress towards #33302
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

Success on x86_64-darwin (full log)
Attempted: SDL, SDL2, freetype
The following builds were skipped because they don't evaluate on x86_64-darwin: libdrm
Partial log (click to expand)
/nix/store/4v2y8wgf6dhdwbi9p6kjnipxkbjbj4cm-SDL2-2.0.8/lib/libSDL2-2.0.0.dylib: fixing dylib
/nix/store/4v2y8wgf6dhdwbi9p6kjnipxkbjbj4cm-SDL2-2.0.8/lib/libSDL2-2.0.0.dylib: fixing dylib
/nix/store/4v2y8wgf6dhdwbi9p6kjnipxkbjbj4cm-SDL2-2.0.8/lib/libSDL2-2.0.0.dylib: fixing dylib
strip is /nix/store/kdff2gim6417493yha769kh00n63lnrw-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/864wsjyy02wy04pzi86qjmm5ngac9v6g-SDL2-2.0.8-dev/lib  /nix/store/864wsjyy02wy04pzi86qjmm5ngac9v6g-SDL2-2.0.8-dev/bin
patching script interpreter paths in /nix/store/864wsjyy02wy04pzi86qjmm5ngac9v6g-SDL2-2.0.8-dev
/nix/store/864wsjyy02wy04pzi86qjmm5ngac9v6g-SDL2-2.0.8-dev/bin/sdl2-config: interpreter directive changed from "/bin/sh" to "/nix/store/r8bx3qf1bpncb14i9gzma4vr089pc3pv-bash-4.4-p19/bin/sh"
/nix/store/8r9y5p25gvr0hpplf1ql8ckmb9zdxij5-SDL-1.2.15
/nix/store/4v2y8wgf6dhdwbi9p6kjnipxkbjbj4cm-SDL2-2.0.8
/nix/store/7xzr0r22z42c931ax7nqg2vvmclyl6ji-freetype-2.9

Failure on x86_64-linux (full log)
Attempted: SDL, SDL2, freetype, libdrm
Partial log (click to expand)

Alternatively, you may set the environment variables I915_CFLAGS
and I915_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
builder for '/nix/store/r6wgs59f06a6imh60fgwiafyqch8p3hz-mesa-noglu-17.3.8.drv' failed with exit code 1
cannot build derivation '/nix/store/wy1hg60im38zxgrq14grvq48c7kb229q-libGL-1.0.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/7dl0lw9a2gkblcfvx5rqyvybwcjib16c-SDL2-2.0.8.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/cfaw35pm71hx63xx4i6g17w5rxzsx9sf-glu-9.0.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/bl7b8nys6bvmgm1rg5ihcl8ggayzgzp2-SDL-1.2.15.drv': 2 dependencies couldn't be built
error: build of '/nix/store/7dl0lw9a2gkblcfvx5rqyvybwcjib16c-SDL2-2.0.8.drv', '/nix/store/bl7b8nys6bvmgm1rg5ihcl8ggayzgzp2-SDL-1.2.15.drv' failed

Success on x86_64-darwin (full log)
Attempted: SDL, SDL2, freetype
The following builds were skipped because they don't evaluate on x86_64-darwin: libdrm
Partial log (click to expand)
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

/nix/store/8r9y5p25gvr0hpplf1ql8ckmb9zdxij5-SDL-1.2.15
/nix/store/4v2y8wgf6dhdwbi9p6kjnipxkbjbj4cm-SDL2-2.0.8
/nix/store/7xzr0r22z42c931ax7nqg2vvmclyl6ji-freetype-2.9

Success on x86_64-linux (full log)
Attempted: SDL, SDL2, freetype, libdrm
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/mcyyvjj9zjaf7r55g5xs39q41sdhzf17-SDL2-2.0.8-dev
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/mcyyvjj9zjaf7r55g5xs39q41sdhzf17-SDL2-2.0.8-dev/lib  /nix/store/mcyyvjj9zjaf7r55g5xs39q41sdhzf17-SDL2-2.0.8-dev/bin
patching script interpreter paths in /nix/store/mcyyvjj9zjaf7r55g5xs39q41sdhzf17-SDL2-2.0.8-dev
/nix/store/mcyyvjj9zjaf7r55g5xs39q41sdhzf17-SDL2-2.0.8-dev/bin/sdl2-config: interpreter directive changed from "/bin/sh" to "/nix/store/xn5gv3lpfy91yvfy9b0i7klfcxh9xskz-bash-4.4-p19/bin/sh"
checking for references to /build in /nix/store/mcyyvjj9zjaf7r55g5xs39q41sdhzf17-SDL2-2.0.8-dev...
/nix/store/8hr6xww9cjrc7lm0k4x0cl44x6qzvvcn-SDL-1.2.15
/nix/store/25crnb1gvf03sf40c51hd83ssiv1aa11-SDL2-2.0.8
/nix/store/3192bm9pzlzj1f4nqf16zvaqr73k2fhc-freetype-2.9
/nix/store/y7xyva8ra4r1frpkz42i7xxacnicyxc8-libdrm-2.4.91

Success on aarch64-linux (full log)
Attempted: SDL, SDL2, freetype, libdrm
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/296v36xf4hvq9ffnalwljw7ya23m8zhp-SDL2-2.0.8-dev
strip is /nix/store/gp7fylxwn18b7pl2c18ks89hsiaxyfvf-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/296v36xf4hvq9ffnalwljw7ya23m8zhp-SDL2-2.0.8-dev/lib  /nix/store/296v36xf4hvq9ffnalwljw7ya23m8zhp-SDL2-2.0.8-dev/bin
patching script interpreter paths in /nix/store/296v36xf4hvq9ffnalwljw7ya23m8zhp-SDL2-2.0.8-dev
/nix/store/296v36xf4hvq9ffnalwljw7ya23m8zhp-SDL2-2.0.8-dev/bin/sdl2-config: interpreter directive changed from "/bin/sh" to "/nix/store/a4qslf0yfs44mhnbagarn232sjnckhy0-bash-4.4-p19/bin/sh"
checking for references to /build in /nix/store/296v36xf4hvq9ffnalwljw7ya23m8zhp-SDL2-2.0.8-dev...
/nix/store/g9f18skhgv6gw2nfx811wlr5smyv3rs0-SDL-1.2.15
/nix/store/4qhsr779zzvrq28wv150sxj2slxwdg99-SDL2-2.0.8
/nix/store/ia9b9879xmipfb4xssi8r75ssdwyf2a3-freetype-2.9
/nix/store/2jj6pirxhm1f2f66712zdm42lj9ciwam-libdrm-2.4.91

Success on x86_64-linux (full log)
Attempted: SDL, SDL2, freetype, libdrm, libpng, libssh2
Partial log (click to expand)
/nix/store/8hr6xww9cjrc7lm0k4x0cl44x6qzvvcn-SDL-1.2.15
/nix/store/580y11zq14xag6ybrvzcbr7k93naman4-SDL2-2.0.8
/nix/store/3192bm9pzlzj1f4nqf16zvaqr73k2fhc-freetype-2.9
/nix/store/y7xyva8ra4r1frpkz42i7xxacnicyxc8-libdrm-2.4.91
/nix/store/1n47iy8z04x07ahq8phzdp1bvmqwfmmc-libpng-apng-1.6.34
/nix/store/8kanfjdi2yh998xbinc1m8ywysnf41k6-libssh2-1.8.0

Success on aarch64-linux (full log)
Attempted: SDL, SDL2, freetype, libdrm, libpng, libssh2
Partial log (click to expand)
/nix/store/g9f18skhgv6gw2nfx811wlr5smyv3rs0-SDL-1.2.15
/nix/store/57xsz4ddqhcs5hcq084p68cjd19mabkz-SDL2-2.0.8
/nix/store/ia9b9879xmipfb4xssi8r75ssdwyf2a3-freetype-2.9
/nix/store/2jj6pirxhm1f2f66712zdm42lj9ciwam-libdrm-2.4.91
/nix/store/87s3ak35aq4svj4165lpq2qi5gzs2snm-libpng-apng-1.6.34
/nix/store/7f538fs1b88fssc7qmq8hkc7pbc5cbps-libssh2-1.8.0

Success on x86_64-darwin (full log)
Attempted: SDL, SDL2, freetype, libpng, libssh2
The following builds were skipped because they don't evaluate on x86_64-darwin: libdrm
Partial log (click to expand)
b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

/nix/store/8r9y5p25gvr0hpplf1ql8ckmb9zdxij5-SDL-1.2.15
/nix/store/3f9qv287i405js11zgbdwgcy3c5a8mrd-SDL2-2.0.8
/nix/store/7xzr0r22z42c931ax7nqg2vvmclyl6ji-freetype-2.9
/nix/store/s7ra5sq6na42fj93xw2bay80dhpf68dk-libpng-apng-1.6.34
/nix/store/mwdkj4cakd5dg62ai11g4dfgswk6q0xx-libssh2-1.8.0


v2.0 eta

What is the timescale for an implementation of PACT v2 specification in PACT.NET ?

Hi @paulmarshall
There is no timescale for v2 of Pact .NET. You can follow the conversation https://github.com/SEEK-Jobs/pact-net/issues/9 and if you want to contribute, have a look at https://github.com/SEEK-Jobs/pact-net/pull/79


Use of SPM models for Indic-Indic translation

Hi Team,
I have a Prakrit-Hindi (Devanagiri script) dataset that I wanted to fine-tune one of the pre-trained Indictrans2 models. I am blocked on which SPM model to use as the only available options are En-Indic and Indic-En but my dataset is Indic-Indic.
Also, it seems like HuggingFace interface only allows Indictrans2 models for inference and not fine-tuning. Please clarify these two queries.

The SPM models and Fairseq dicts are already provided along with the checkpoints of the respective models.
Please note that these get downloaded along with the respective checkpoint.
An additional download link has also been provided in the readme.
Regarding HuggingFace interface, we support both inference and fine-tuning.
Please check the HF Readme, where we provide instructions regarding the same. LORA FT script


Add UDP rule hint for QUIC

@feckert QUIC uses UDP and while new, is widespread enough that users may not even be aware it's not over TCP. Adding a rule hint seems less invasive than creating a whole template. Most users who are aware of what QUIC is are probably aware they need to swap the rule to UDP. Perhaps at some point in the future, this would default to UDP.
Closes https://github.com/openwrt/packages/issues/11571
Avinash H. Duduskar<EMAIL_ADDRESS>

Forgot to sign-off correctly and git push --force-with-lease origin patch-3 failed too.

I do not like it.
All other advice items in that mwan3 text are generic, and this would be only app/protocol specific. And the contents are quite unrelated to mwan3.
If you want to use QUIC and need advice about basic TCP/IP protocols, you should search advice from QUIC pages, not from mwan3 documentation.
Other thing is that this should be to the development master first, not to the old stable 19.07
So, NAK from me.


Merge with awesome-icons

Hey there,
how about we merging my awesome-icons into this project ?
https://github.com/mrzmyr/awesome-icons

Sounds good to me. Do you want to expand upon the icons section and make a
pull request?
On Tue, Nov 10, 2015 at 3:40 PM, Moritz<EMAIL_ADDRESS>wrote:

Hey there,
how about we merge my awesome-icons into this project ?
—
Reply to this email directly or view it on GitHub
https://github.com/neutraltone/awesome-stock-resources/issues/41.

--
Tony Phipps
+44(0)7449554534
<EMAIL_ADDRESS>tonyphipps.co.uk

No need to get all of them if they are not good enough though..

True. I can go through the list later and assess.

:+1:

All contents of from mrzmyr/awesome-icons have been merged into the list.


[IMPROVEMENT] fix all todos in the code

see title, lots of error handling todos

Moved to https://github.com/mrjvs/neatojs


Binary Indexed Tree/Fenwick Tree implementation in C++

I would like to work on the above.

Created the PR for this algorithm


mini.files content.postfix

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md

Module(s)
mini.files
Description
I would like to be able to append text in the same manner that you can prefix text with a content.prefix function.
For an example of why this would be useful, this is currently the best git-view that I could achieve using a prefix:

It would be pretty cool if we could add some extra info without breaking the columns :P

Thanks for the suggestion!
I don't think this will be a worthwhile addition. The only use case I can think about is indeed showing some custom indicator, but for that I'd recommend using extmarks with virt_text_pos not equal to 'overlay' (so either 'eol', 'right_align', or 'inline').
Closing as not planned.


[Python] Make the decorator trace support async, await functions

Currently the decorator @trace only support plain functions. Decorating functions with async makes the trace hierarchy incorrect.
        @runnable()
        async def test1(self):
            return '1'

        @runnable()
        async def test2(self):
            return self.test1()

        def test(self):
            asyncio.run(self.test2())

this generates the trace like this

while expectation is

@taskmgr , if you're interested in this, comment here and I can assign to you, FYI @WillemJiang

I 'd like to do this~

I 'd like to do this~

If you need any help, feel free to ping me here or via WeChat direct messages :)


Please improve the update documentation

Hello team!
The documentation in this section https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/deployment/updateenvironment-newinfrastructure#production-environment does not appear accurate any longer with the current structure of a self-service environment.
According to a good explanation posted from a Partner here https://www.yammer.com/dynamicsaxfeedbackprograms/#/threads/show?threadId=727603441950720 :
"When you update a production self-service environment it's not being updated with the deployable package you apply, but the state of a sandbox environment.
Based on recent customer and internal team feedback, what is described above appears to be a more accurate description of the update process. Meaning that steps such as step #4 "In the grid, select the update to apply to the production environment. This grid shows only updates that have been marked as release candidates." is not correct and leads to confusion why a customer cannot select a previous package.
Please update the documentation to provide customers with an improved explanation of how updating production is performed along with appropriate steps.
Please let me know if you have any questions.
Thanks!

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

ID: 5f5ff8cf-5739-86d9-26e2-2804b2f37973
Version Independent ID: 5ca5612d-f4ec-5e7d-222c-678962aa2da7
Content: Update an environment - Finance & Operations | Dynamics 365
Content Source: articles/fin-ops-core/dev-itpro/deployment/updateenvironment-newinfrastructure.md
Service: dynamics-ax-platform
Product: ****
Technology: ****
GitHub Login: @laneswenka
Microsoft Alias: laswenka

Thank you for your feedback. @laneswenka can you please review?

BUG 535336 created to track the issue.


fix merkle proof conversion

Description
The rgb-node produces an incorrect merkle proof anchor when compiled in release mode.
This problem occurs because the conversion of the merkle block into a merkle proof was inside the debug_assert method.
Closes:

https://github.com/LNP-BP/nodes/issues/16
https://github.com/RGB-WG/rgb-core/issues/113

Related:

https://github.com/RGB-WG/rgb-node/issues/197

Released v0.8.1 of commit_verify. You need to do cargo update in the projects using RGB to get the fix in.
@crisdut can you also pls open a PR against the master branch to ensure the next version wouldn't get the same bug again?


Refactor controls to use transparent pointers

This refactors reference types with lifetimes (i.e. ControlListRef<'a>) into transparent pointers, which can be cast into references.
Important changes:

Immutable<ControlListRef<'a>> becomes &ControlList
ControlListRef<'a> becomes &mut ControlList
ControlList can only exist as a reference so new lists are created with ControlList::new() -> UniquePtr<ControlList>. UniquePtr<T> implements Deref<Target = T>.

Fixes #2

I'm merging this since it conflicts a lot with other PRs. We will resolve any problems later if they arise.


Can we use nopecha in Selenium headless mode?

I think I was scammed. I wish I had read this before.

Yes, both the Chrome extension and Firefox Add-on works with Selenium and all other browser automation tools.
Please refer to the documentation and guide for more information.


Allow Helm users to specify sds secrets lookup namespace

The TLS Secrets lookup namespace is currently hard coded to look for TLS secrets in the same namespace as the gateway. This PR allows users to define a specific namespace to lookup secrets that isn't necessarily in the same namespace as the gateway. This will allow users to create specific namespaces to specifically store certificates that have tightly controlled access via RBAC and automation, while still allowing users to deploy gateways in their own namespaces.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: mmckane
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: gyliu513
If they are not already assigned, you can assign the PR to them by writing /assign @gyliu513 in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS

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

Hi @mmckane. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

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

/assign @gyliu513

/ok-to-test

@mmckane: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
845f4e4b825f5bb1287dafc5473cd0b80165976b
link
/test e2e-simpleTests

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

@mmckane: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
845f4e4b825f5bb1287dafc5473cd0b80165976b
link
/test e2e-simpleTests

prow/istio-unit-tests.sh
845f4e4b825f5bb1287dafc5473cd0b80165976b
link
/test istio-unit-tests

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

@mmckane: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
845f4e4b825f5bb1287dafc5473cd0b80165976b
link
/test istio-unit-tests

prow/istio-pilot-multicluster-e2e.sh
845f4e4b825f5bb1287dafc5473cd0b80165976b
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
845f4e4b825f5bb1287dafc5473cd0b80165976b
link
/test istio-integ-k8s-tests

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

/retest

@mmckane: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
845f4e4b825f5bb1287dafc5473cd0b80165976b
link
/test istio-unit-tests

prow/istio-integ-k8s-tests.sh
845f4e4b825f5bb1287dafc5473cd0b80165976b
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
845f4e4b825f5bb1287dafc5473cd0b80165976b
link
/test istio-pilot-multicluster-e2e

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

@mmckane: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
845f4e4b825f5bb1287dafc5473cd0b80165976b
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
b5adbf1134eba174452293f2f1e7439364dc6781
link
/test istio-pilot-multicluster-e2e

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

/retest

Is anyone available to review this?

/retest

@mmckane: PR needs rebase.

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

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: mmckane
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: mandarjog
If they are not already assigned, you can assign the PR to them by writing /assign @mandarjog in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS

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

@mmckane: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
b5adbf1134eba174452293f2f1e7439364dc6781
link
/test istio-pilot-multicluster-e2e

prow/codecov.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test istio-codecov-master

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

@mmckane: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
b5adbf1134eba174452293f2f1e7439364dc6781
link
/test istio-pilot-multicluster-e2e

prow/codecov.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test istio-codecov-master

prow/integ-istioctl-local-presubmit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test integ-istioctl-local-presubmit-tests-master

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

@mmckane: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
b5adbf1134eba174452293f2f1e7439364dc6781
link
/test istio-pilot-multicluster-e2e

prow/codecov.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test istio-codecov-master

prow/integ-istioctl-local-presubmit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test integ-istioctl-local-presubmit-tests-master

prow/integ-mixer-k8s-k8s-presubmit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test integ-mixer-k8s-k8s-presubmit-tests-master

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

@mmckane: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
b5adbf1134eba174452293f2f1e7439364dc6781
link
/test istio-pilot-multicluster-e2e

prow/codecov.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test istio-codecov-master

prow/integ-istioctl-local-presubmit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test integ-istioctl-local-presubmit-tests-master

prow/integ-mixer-k8s-k8s-presubmit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test integ-mixer-k8s-k8s-presubmit-tests-master

prow/racetest.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test istio-racetest-master

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

@mmckane: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
b5adbf1134eba174452293f2f1e7439364dc6781
link
/test istio-pilot-multicluster-e2e

prow/codecov.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test istio-codecov-master

prow/integ-istioctl-local-presubmit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test integ-istioctl-local-presubmit-tests-master

prow/integ-mixer-k8s-k8s-presubmit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test integ-mixer-k8s-k8s-presubmit-tests-master

prow/racetest.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test istio-racetest-master

prow/e2e-dashboard.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test e2e-dashboard-master

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

@mmckane: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
b5adbf1134eba174452293f2f1e7439364dc6781
link
/test istio-pilot-multicluster-e2e

prow/codecov.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test istio-codecov-master

prow/integ-istioctl-local-presubmit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test integ-istioctl-local-presubmit-tests-master

prow/integ-mixer-k8s-k8s-presubmit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test integ-mixer-k8s-k8s-presubmit-tests-master

prow/racetest.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test istio-racetest-master

prow/e2e-dashboard.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test e2e-dashboard-master

prow/integ-istioctl-k8s-presubmit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test integ-istioctl-k8s-presubmit-tests-master

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

@mmckane: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
b5adbf1134eba174452293f2f1e7439364dc6781
link
/test istio-pilot-multicluster-e2e

prow/codecov.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test istio-codecov-master

prow/integ-istioctl-local-presubmit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test integ-istioctl-local-presubmit-tests-master

prow/integ-mixer-k8s-k8s-presubmit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test integ-mixer-k8s-k8s-presubmit-tests-master

prow/racetest.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test istio-racetest-master

prow/e2e-dashboard.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test e2e-dashboard-master

prow/integ-istioctl-k8s-presubmit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test integ-istioctl-k8s-presubmit-tests-master

prow/e2e-mixer-no_auth.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test e2e-mixer-no_auth-master

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

@mmckane: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
b5adbf1134eba174452293f2f1e7439364dc6781
link
/test istio-pilot-multicluster-e2e

prow/codecov.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test istio-codecov-master

prow/integ-istioctl-local-presubmit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test integ-istioctl-local-presubmit-tests-master

prow/integ-mixer-k8s-k8s-presubmit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test integ-mixer-k8s-k8s-presubmit-tests-master

prow/racetest.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test istio-racetest-master

prow/e2e-dashboard.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test e2e-dashboard-master

prow/integ-istioctl-k8s-presubmit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test integ-istioctl-k8s-presubmit-tests-master

prow/e2e-mixer-no_auth.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test e2e-mixer-no_auth-master

prow/release-test.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test release-test-master

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

@mmckane: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
b5adbf1134eba174452293f2f1e7439364dc6781
link
/test istio-pilot-multicluster-e2e

prow/codecov.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test istio-codecov-master

prow/integ-istioctl-local-presubmit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test integ-istioctl-local-presubmit-tests-master

prow/integ-mixer-k8s-k8s-presubmit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test integ-mixer-k8s-k8s-presubmit-tests-master

prow/racetest.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test istio-racetest-master

prow/e2e-dashboard.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test e2e-dashboard-master

prow/integ-istioctl-k8s-presubmit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test integ-istioctl-k8s-presubmit-tests-master

prow/e2e-mixer-no_auth.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test e2e-mixer-no_auth-master

prow/release-test.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test release-test-master

prow/istio-unit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test istio-unit-tests-master

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

@mmckane: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
b5adbf1134eba174452293f2f1e7439364dc6781
link
/test istio-pilot-multicluster-e2e

prow/codecov.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test istio-codecov-master

prow/integ-istioctl-local-presubmit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test integ-istioctl-local-presubmit-tests-master

prow/integ-mixer-k8s-k8s-presubmit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test integ-mixer-k8s-k8s-presubmit-tests-master

prow/racetest.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test istio-racetest-master

prow/e2e-dashboard.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test e2e-dashboard-master

prow/integ-istioctl-k8s-presubmit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test integ-istioctl-k8s-presubmit-tests-master

prow/e2e-mixer-no_auth.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test e2e-mixer-no_auth-master

prow/release-test.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test release-test-master

prow/istio-unit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test istio-unit-tests-master

prow/e2e-simpleTests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test e2e-simpleTests-master

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

@mmckane: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/codecov.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test istio-codecov-master

prow/integ-istioctl-local-presubmit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test integ-istioctl-local-presubmit-tests-master

prow/integ-mixer-k8s-k8s-presubmit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test integ-mixer-k8s-k8s-presubmit-tests-master

prow/racetest.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test istio-racetest-master

prow/e2e-dashboard.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test e2e-dashboard-master

prow/integ-istioctl-k8s-presubmit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test integ-istioctl-k8s-presubmit-tests-master

prow/e2e-mixer-no_auth.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test e2e-mixer-no_auth-master

prow/release-test.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test release-test-master

prow/istio-unit-tests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test istio-unit-tests-master

prow/e2e-simpleTests.sh
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test e2e-simpleTests-master

e2e-bookInfoTests-trustdomain_istio
cb7de2fa3f9b914f92e0153bb97b7f7a12187a45
link
/test e2e-bookInfoTests-trustdomain_istio

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

I am not sure if this is still relevant, but unfortunately I don't think this is going to be reviewed as its so old it has been forgotten


How to remap keys?

First of all, thanks for bringing your wonderful creation onto my radar. I recently have to deal with some projects that have so many TODO's from external teams, so that I benefit from the regex feature of this plugin to filter all my TODO's. It's such a powerful tool, but I don't know how to change the keymaps, such as t for toggle.
Also I think some documentation would be preferred. It took me a while to figure out t. It also took me a while to figure out that hlGroup is compatible with values listed at :h coc-highlight.

@hexh250786313 Ah, thanks a lot. A lot of people consider CoC for it's simpler entry, I haven't explored every nuance of the plugin so far, so your guide is super helpful. I appreciate it a lot, thanks.

@martin-braun

I guess this is a CoC problem and has nothing to do with your plugin?

Yes, limitation from CoC. But I'm not really sure if there's a simple way to override these keymaps. I will try to figure it out in coming days.

@martin-braun https://github.com/hexh250786313/coc-todo-tree/commit/30c0ec85de43defe7998be0b1dd647cf8a8e84e0 Custom keymap for toggle expand and jump. :CocUpdate and try todo-tree.invokeKey.


Access violation crash

Hi,
I'm experiencing occasional access violation crashes, these only seem to happen in the build of the app, not in editor, they also don't always happen but once they have happened once they continue even through restarts of the application. I'm unable to find a way to reproduce the issue on demand.
Output from Visual Studio when attached to the process:
Unhandled exception at 0x00007FFCCA904240 (d3d11.dll) in OVR Toolkit.exe: 0xC0000005: Access violation writing location 0x00000000000000E0. occurred
error.log
uDesktopDuplication.log
Any help is appreciated, thanks!

If it's of any use, this is the error.log from someone else's system who had the same issue happen, in their case it happened on initializing the desktop not on switching to a different one. But I suppose that's the same thing really, loading a desktop.
error.log
Hope this can help!

If a fix isn't planned for soon, do you have any idea of a temporary workaround to avoid this issue? If you know what the issue is yet!
If not, that's fine!

Sorry for my late reply.
I've checked the provided log, but I couldn't find the reason of the crash..., if possible, could you check what the last API call is? The way to do it is written here:
https://github.com/hecomi/uDesktopDuplication/issues/14#issuecomment-442515768
From the error.log, it seems that you are using uWindowCapture, too. So if you do not identify the API in uDesktopDuplication, could you try it also with uWindowCapture?
Thank you for your cooperation.


Point http://docs.minio.io/minio to minio-quickstart-guide

Assigned to deekoder.

@GarimaKapoor  will confirm. Discussed.

Behaves as we need it to.


The RfExample plug-in has a remote code execution vulnerability

We found a remote command execution vulnerability in the RfExample plugin in the official plugin market.
In the actionCutImage() function of VideoController.php, the load method in the Modle class gets the post data:

Then $modle->video is parsed in getLocalFilePath; video is also CutImageForm['video'], which is discovered by debugging
CutImageForm['video'] is controllable and a malicious user can write malicious commands on the front end by controlling this value

Here are the results：

邮件已收到。


Support Shared Journal

This is a tracking issue for implementing the shard journal(Single Write Journal in former references).
The design can be found in #280.

[ ] Prototype & Basic traits:

[ ] trait of shared journal: #283
[ ] basic framework and structures
[ ] design journal master

The task list currently only includes sub-tasks that focus on the skeleton of a shared journal; more sub-tasks must be added. I'll update and add the detail implementation as sub-tasks once the skeleton is complete.

@w41ter-l I think one of the subtask is bringing back grpc journal client & server - they are currently broken.

According to the discussion https://github.com/engula/engula/discussions/293#discussioncomment-2013238, you may think of what mapping engine:kernel is - 1:1 or n:1?
If engine always runs with kernel both in memory, the leader elections procedure may be different.


Error: Command failed: in Windows Powershell

Error while executing in windows.
fatal: ':(exclude)package-lock.json': no such path in the working tree.
Use 'git <command> -- <path>...' to specify paths that do not exist locally.
node:internal/errors:863
  const err = new Error(message);
              ^

Error: Command failed: git diff --cached . ':(exclude)package-lock.json' ':(exclude)yarn.lock'
fatal: ':(exclude)package-lock.json': no such path in the working tree.
Use 'git <command> -- <path>...' to specify paths that do not exist locally.

This is because https://github.com/Nutlope/aicommits/blob/b48683755b0a43e35ce1eeeba69c37d83fc33ab0/aicommits.ts#L31
Windows does not like single quote in execSync
I will create a PR soon

@yusefren Great catch, would very much welcome a PR! I didn't test it on Windows so this is great info. Thank you!

Closing since this is now fixed!


Move to ts-proto

Move proto message generation to ts-proto
https://github.com/chainapsis/keplr-wallet/tree/master/packages/proto-types
https://github.com/confio/cosmjs-types
Ts-proto creates typescript files, but protobufjs creates javascript files. Because of this, in a typescript environment ts-proto creates more idiomatic code.
One big reason to move away from protobufjs is golang's protobuf compiler returns a different result in json encode, which can lead to potential issues when creating signDoc.
This can be resolved by migrating to ts-proto.

Why not use telescope 👀


Refactor toolchain test scripts

I refactored the existing toolchain FVT test scripts to separate test pod creation from test setup and execution. This should make spinning up separate test pods for different types of tests (like performance) a bit easier without needing to copy/paste a bunch of the setup code.
tests/create-taurus-pod.sh will create a test pod built on top of the Taurus image and set up some of the common requirements across test types (provide access to the shaded jar, create the trust store).
tests/run-fvttests.sh creates a test pod using the creation script. It then performs the fvt-test-specific setup steps and overwrites relevant files in the test pod. Finally, it executes its tests and retrieves  the results.
I also refactored parts of the original scripts. Some changes include:

Replace some duplicated sed steps with a  function.
Change sed syntax to use different  delimiters, remove the need for escaping the / character, and use " around entire expressions.
Remove cd statements and instead refer to files using the path to the file.

Aside from my two comments. Everything else looks good as long as you have tested it in umbrella repo and have verified fvt tests are still working and the final DevOps Insights Console is recording them successfully.


Replace #unadornedText with proper use of Win32 functions in OwnerDrawnButton

All drawing functions used accept the DSS_HIDEPREFIX flag, make use of it instead of stripping out &s ourselves.

Fine with me - don't think I was aware of the flag hence the manual implementation.

Any suggestion on how to test it? If this code were to break, the only thing that would be noticeable is incorrect rendering on the screen—nothing with a return value or the like that I can check.

Without looking in depth, I would generally agree that where the effects are purely visual testing can be hard and may not be justifiable. Where that is the case the PR should explain why as I don't necessarily have the time to work it out for myself.
As this is an improvement rather than a bug fix as such, my main concern would be automatically detecting that the enhancement is not lost or broken in future. It would be reasonable to test just that the text does actually draw in the two modes, which I would think could be done using the same trick as I used in my recent PR #993. See the method TabViewXPTest>>#testLabelWithAmpersand.


CI not testing oldest supported python version

Description
Right now the CI tests on version 3.11. Thus, it guarantees nothing about correctness or compatibility for versions less than 3.11.
Steps to reproduce the bug
No response
Environment
GitHub actions CI
Additional context
If you only run tests on a single python version, the oldest supported version is probably the best idea. This is what angr does. While there can be compatibility issues on newer versions, they are generally less and more obvious than the reverse. Of course, if you want to be thorough, consider running tests for each supported version.
Related: #365

#367 addresses this PR, but, unfortunately, wouldn't have caught the bug mentioned in #365 because we don't have an code coverage for the IDA code, since we need a private CI for that.

A possible option you could use that may help is using a linter. ruff I believe will report if syntax is invalid for the minimum supported python version, without needing to actually import or run the code.


add zoraTestnet to README

Description
Added zoraTestnet to README
Additional Information

[x] I read the contributing docs (if this is your first contribution)

Your ENS/address: skillet.eth

would love to get the previous zoraTestnet addition released, should I add a changeset for this or let y'all handle?
also nit but wondering if the docs could use some help regarding adding new networks, adding to README & exporting from index


support passing extra build flags

go 1.20 support a new build flag -cover which we'd like to use for integration test, currently the only way to pass that is through buildFlags parameter, but it trigger a warning.
I suggest we either remove the warning or support new method to customize build flags.

I have a similar problem, but with -buildmode pie.


New-SSHSession does not work in NonInteractive mode

I am running New-SSHSession on a build server (VSTS) and this runs PowerShell steps in -Noninteractive mode. This causes my Pester tests which work fine on my dev machine to fail on the build server with:

2017-12-12T15:53:05.2873148Z Describing Linux Container tests
2017-12-12T15:53:36.0097374Z New-SSHSession : Windows PowerShell is in NonInteractive mode. Read and Prompt functionality is not available.
2017-12-12T15:53:36.0097374Z At line:52 char:17
2017-12-12T15:53:36.0097374Z + ...     $sesh = New-SSHSession -ComputerName $DockerHost -Credential $cre ...
2017-12-12T15:53:36.0097374Z +                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2017-12-12T15:53:36.0097374Z     + CategoryInfo          : InvalidOperation: (Renci.SshNet.SshClient:SshClient) [New-SSHSession], PSInvalidOperatio
2017-12-12T15:53:36.0097374Z    nException
2017-12-12T15:53:36.0097374Z     + FullyQualifiedErrorId : SSH.NewSshSession

More than likely it is https://github.com/darkoperator/Posh-SSH/blob/master/PoshSSH/PoshSSH/NewSessionBase.cs#L413 if it is that and -AcceptKey or -Force do not work then I would need to re-engineer the session creations and SCP cmdlets and do to it being a mayor version since it would be a big change.

Thanks, they both worked fine. The -Force gave me warnings WARNING: Host key is not being verified since Force switch is used. and -AcceptKey didn't so I went with -AcceptKey. Great work!


add host_id field to CassandraNode

I need the nodes to have a unique id for token aware routing and using the socket address is probably going to end up badly so I've added this field.

Most drivers I've seen use the UUID for keys in a map of Nodes, haven't seen any using the socket address for that purpose.


Is it any plan to support Visual studio 2013?

Is it any plan to support Visual studio 2013? Thanks

I don't have VS 2013 for now.

For now I don't know how add some

GoToDnSpy use Roslyn for code analysis, some features has breaking changes in Project System
I think it's hard to port to older VS. (maybe easy to port to VS 2015)

Thanks. Maybe the best way is to update may visual stuido.


refactor/speed-up BkgErrFilt

Description
This PR is the first of several that convert our linear variable changes into proper saber outer blocks. (Once this is merged, a cleaned-up Saber-ified parametric bkgerr stddev will be next!)

BkgErrFilt is converted into a saber outer block, with no change in its behavior
This is done purely with C++, which speeds it up since it no longer has to deal with the C++/Fortran field synchronization

[!NOTE]
Do we need BkgErrFilt?? I think its functionality can be handled by a combination of 1) the new diffusion
operator (which will mask out land and thin layers) and 2) tweaking the background error stddev. Regardless, I converted it as is and we can delete it later if we don't need it.

[!IMPORTANT]
Dear users, there is an associated change to the yamls now. See the 3dvar.yaml test for an example of the change. (I'll update skylab soon-ish)

Testing
The only real answer change is the diagnostic Jb calculated at the end. I'm not sure why. The actual results are all the same.
There is a small performance improvement. Testing on my machine (1/4 deg grid, 1 SST and 1 ADT source, 10 iterations of 3DVAR, 24 cores ):
before (current develop)
OOPS_STATS Name                                                :   total (ms)   count    time/call (ms)
OOPS_STATS soca::BkgErrFilt::BkgErrFilt                        :      2074.13       1         2074.1309
OOPS_STATS soca::BkgErrFilt::multiply                          :      7305.63      12          608.8025
OOPS_STATS soca::BkgErrFilt::multiplyAD                        :      6121.60      12          510.1333

with this PR
OOPS_STATS Name                                                :   total (ms)   count    time/call (ms)
OOPS_STATS soca::BkgErrFilt::BkgErrFilt                        :        31.05       1           31.0507
OOPS_STATS soca::BkgErrFilt::multiply                          :      1423.83      24           59.3262

Apart from my 1 comment, the code looks fine and ctests run fine on orion with GNU. 🎉
PS I can't wait to rerun my experiments for quarter degree given so many "speed ups" PR

Do we still need this test?

ha, nope. It turns out that test was not setup correctly for the past 3 years, the yaml was wrong. it wasn't running BkgErrFilt. Oops


Eval-only AMP

🚀 Feature
A trainer flag to enable Automatic Mixed Precision only during Validation/Testing.
Motivation
Some models cannot be trained with AMP because of peculiarities in their loss functions (e.g. Weakly Supervised methods based on WSDDN, which require the use of F.binary_cross_entropy which does not work under AMP). This doesn't prevent such models from running under AMP during evaluation though since the incompatible functions are in the loss. Especially for validation where the most precise accuracy metrics may not be necessary, this would be very useful.
Pitch
Add a new flag (or flags) on Trainer along the lines of use_amp_val.

cc: @williamFalcon

is this still an issue??


不算子更新

PR Type

[ ] Bugfix.
[ ] Feature.
[ ] Code style update (formatting, local variables).
[ ] Refactoring (no functional changes, no api changes).
[ ] Build & CI related changes.
[ ] Documentation.
[ ] Translation.
[ ] Other... Please describe:

Description

Others

Issue resolved:

Screenshots with this changes:

Link to demo site with this changes:

手动合并


Error Plugin unavailable when trying to save and test data source

Error Plugin unavailable when trying to save and test data source.

Grafana-Docker-Log
logger=context traceID=00000000000000000000000000000000 userId=1 orgId=1 uname=admin t=2022-07-29T14:29:00.794365614Z level=error msg="Plugin unavailable" error="plugin unavailable" remote_addr=<IP_ADDRESS> traceID=00000000000000000000000000000000
logger=context traceID=00000000000000000000000000000000 userId=1 orgId=1 uname=admin t=2022-07-29T14:29:00.794732911Z level=error msg="Request Completed" method=GET path=/api/datasources/1/health status=503 remote_addr=<IP_ADDRESS> time_ms=8 duration=8.528612ms size=77 referer=http://<IP_ADDRESS>:3001/datasources/edit/dpxzCIzVz traceID=00000000000000000000000000000000

Run via docker
Browser: chrome
Grafana Version: 9.0.5
Plugin Version: 3.1.1
Plugin installed via: grafana-cli plugins install frser-sqlite-datasource or Grafana/Plugins -> Install

Notice: In Grafana 8.4.1 the tool works

Grafana Version: 9.0.5
Plugin Version: 3.1.1
Plugin installed via: grafana-cli plugins install frser-sqlite-datasource or Grafana/Plugins -> Install

Notice: In Grafana 8.4.1 the tool works

While the plugin is not (yet) officially tested against Grafana version 9 I just ran it locally and everything worked for me. Since you see it working against a different Grafana version I would be interested if the two environments (with the different Grafana versions) are differing in some regards.
If that does not solve the issue, could you provide some more logs? A whole log from startup from Grafana on DEBUG level would be best

ok, i check it again

I can't find any mistake.
All file rights checked
Grafana container restarted multiple times
maybe this error message will help
Log
2022-08-01T16:58:46.905453147+02:00 logger=plugin.manager t=2022-08-01T14:58:46.904520501Z level=error msg="Could not start plugin" pluginId=frser-sqlite-datasource err="Unrecognized remote plugin message: \n\nThis usually means that the plugin is either invalid or simply\nneeds to be recompiled to support the latest protocol.",
2022-08-01T16:58:46.905536719+02:00 logger=plugin.manager t=2022-08-01T14:58:46.904894789Z level=error msg="Could not start plugin" pluginId=frser-sqlite-datasource err="plugin frser-sqlite-datasource is already registered",
2022-08-01T16:58:46.907390398+02:00 logger=secrets t=2022-08-01T14:58:46.906974404Z level=info msg="Envelope encryption state" enabled=true currentprovider=secretKey.v1,
2022-08-01T16:58:46.929960813+02:00 logger=query_data t=2022-08-01T14:58:46.929297549Z level=info msg="Query Service initialization",

Installed the tool(frser-sqlite-datasource) in locally Grafana on my Windows: is working

2022-08-01T16:58:46.905453147+02:00 logger=plugin.manager t=2022-08-01T14:58:46.904520501Z level=error msg="Could not start plugin" pluginId=frser-sqlite-datasource err="Unrecognized remote plugin message: \n\nThis usually means that the plugin is either invalid or simply\nneeds to be recompiled to support the latest protocol."
2022-08-01T16:58:46.905536719+02:00 logger=plugin.manager t=2022-08-01T14:58:46.904894789Z level=error msg="Could not start plugin" pluginId=frser-sqlite-datasource err="plugin frser-sqlite-datasource is already registered"
2022-08-01T16:58:46.907390398+02:00 logger=secrets t=2022-08-01T14:58:46.906974404Z level=info msg="Envelope encryption state" enabled=true currentprovider=secretKey.v1, 2022-08-01T16:58:46.929960813+02:00 logger=query_data t=2022-08-01T14:58:46.929297549Z level=info msg="Query Service initialization",

That does look like a problem indeed. Could you share the whole debug log from start until you try in the Grafana UI? This could give some more context

I need the tool in Docker, what else can I check?

The tool should definitely work in Docker. Could you maybe share your docker setup so I can try to reproduce the issue (e.g. Dockerfile, docker-compose.yaml, startup command of the container, etc.)?

Here are the portainer-settings

It looks like you are using some UI, sadly. If you can provide me with a Dockerfile and/or a docker-compose.yaml, that reproduces the issue it would help immensely. Without that and further logs I don't think I have any other clues.

Hello Sergey,
unfortunately I don't have access to docker on the smart home server. I can only create the containers using Portainer GUI.
Which logs do you mean? I only have the log entries in Grafana Portainer.

Hello Sergej, unfortunately I don't have access to docker on the smart home server. I can only create the containers using Portainer GUI.

That makes recreating the issue a bit more difficult but can't be helped I assume. How do you install the plugin in the container, though? Can you log into the container?

Which logs do you mean? I only have the log entries in Grafana Portainer.

Those are the logs I mean. But it would help to have the full logs from startup up at the DEBUG level (and above) instead of just the two lines you provided.

How do you install the plugin in the container, though? Can you log into the container?
Option 1:  Portainer-Console

Option 2: Grafana GUI
up at the DEBUG level
I only have this option

Here is the log file
Grafana_9.0.5.log
Grafana_9.0.5_With_Deinstall_and_Install_SQL-Plugin.log.txt

The log files are not actually at debug level I believe. You can check this link for details how to enable debug logging: https://grafana.com/docs/grafana/latest/setup-grafana/configure-grafana/#log
Can you also try another version of Grafana (inside the docker environment). I would like to find out if the version of Grafana/the plugin is the problem or if it is because it is running in the docker environment.

Here are two log files.
Grafana Docker Version 8.4.1: Everything works there
Grafana Docker Version 9.0.5: Error Plugin unavailable
Grafana_Docker_8.4.1_Level_Debug_OK_13.08.2022.txt
Grafana_Docker_9.0.5_Level_Debug_Error_13.08.2022.txt

Thank you for the log files! Sadly I don't have any more clues from those.
Can you do the following:

Uninstall the plugin from the container (if it is still installed) and install it using the environment variable GF_INSTALL_PLUGINS=frser-sqlite-datasource 3.1.0 (see link)

Could you give me some more information about your setup, so I can try reproducing it.

What is the operating system/machine of the host PC (are you running on a windows laptop, raspberry pi, ...)
You are running something called "portainer". I am not familiar with the tool. Is it running any abstractions? E.g. running the docker container in some virtual machine?

Notice
I have tested up to version 9.1.0.
Everything is fine up to Grafana version 9.0.4
The error occurs from Grafana version 9.0.5 to 9.1.0
Uninstall the plugin from the container (if it is still installed) and install it using the environment variable
Here are the logs from grafana-installing with
GF_INSTALL_PLUGINS = frser-sqlite-datasource 3.1.0
GF_LOG_CONSOLE_LEVEL = debug
Log_Grafana_Install_V9.0.4_Level_Debug_OK_17.08.2022.txt
Log_Grafana_Install_V9.0.7_Level_Debug_Error_17.08.2022.txt
Line: 3733
2022-08-17T11:48:04.596905051+02:00 logger=plugin.manager t=2022-08-17T09:48:04.595991268Z level=error msg="Could not start plugin" pluginId=frser-sqlite-datasource err="Unrecognized remote plugin message: \n\nThis usually means that the plugin is either invalid or simply\nneeds to be recompiled to support the latest protocol."
What is the operating system/machine of the host PC (are you running on a windows laptop, raspberry pi, ...)
host op: Debian Stretch (9.13)
host machine cpu: 64 Bit Quad-Core 1 GHz
host Docker version: 19.03.15
host portainer version: 1.17.1
You are running something called "portainer". I am not familiar with the tool. Is it running any abstractions? E.g. running the docker container in some virtual machine?
https://hub.docker.com/r/portainer/portainer
https://docs.portainer.io/

I'm facing the same problem for the official grafana Alpine images... I believe this plugins needs a precompile alpine version to work.

I'm facing the same problem for the official grafana Alpine images

That is an interesting observation. I'll try that out and see what might be the issue there.

I'm facing the same problem for the official grafana Alpine images... I believe this plugins needs a precompile alpine version to work.

Hello @danieltdt, I couldn't reproduce the issue. Could you share your setup so I can see the problem you are facing?
@sensej-j : On the off chance that is it alpine related could you try this grafana image "grafana/grafana:9.0.5-ubuntu" instead of "grafana/grafana:9.0.5"

I tried the grafana/grafana:9.1.4-ubuntu version today and everything works as before

I'm facing the same problem for the official grafana Alpine images... I believe this plugins needs a precompile alpine version to work.

Hello @danieltdt, I couldn't reproduce the issue. Could you share your setup so I can see the problem you are facing?

Don't know exactly how, but now the latest docker alpine version is working for me too 🤷🏼


Remove IData

no unused classes that i am aware of - idata is one i would consider removing (along with data) but it is not necessary and it would have potential implications elsewhere.
Originally posted by @HenryGeorgist in https://github.com/HydrologicEngineeringCenter/fda-statistics/issues/42#issuecomment-1010302098

fixed with #57


Bump dependencies

For some reason fixes #15, even though the package-lock.json changes don't seem to be related.
d03ebbe1321586f95694c982624330b92199beb6 disables the new "vue/multi-word-component-names" rule, but you might want to keep it and rename components instead.

@tcitworld I updated most of the other dependencies as well and renamed my demo components. Thank you!


Fixed spelling and grammar mistakes in README

Also, changed a few phrases to make it easier to read.

looks good

looks good


blazor.boot.json - don't set physicalpath

#10068

Thanks, @nicksull123!
I agree it shouldn't be hardcoded to "/_framework/blazor.boot.json". What I'm less sure of is whether it makes a different whether it has the value null or whether we pass in a value for PhysicalPath to the constructor.
@javiercn You have a lot of background knowledge in this area. Do you know whether it makes a difference to the static files middleware whether a given IFileInfo has a valid PhysicalPath or not?

Seems like a valid concern to me. @Tratcher for confirmation.

Thanks for confirming, @Tratcher!
Also thanks for the contribution, @nicksull123! It's now merged.


Static Search with PageFind

What problem will this feature address?
static export cannot use built-in search
Describe the solution you'd like
Use https://pagefind.app, it looks promising and Nextra is using it.
Describe alternatives you've considered
N/A
Additional context
No response

Could I work on this as it will also help my website further?

using Orama instead


Should NatsExport.Type be a string rather than an int?

Observed behavior
When creating an account the NSC tool uses a string for type when doing an export
"nats": {
    "exports": [
      {
        "name": "account-monitoring-streams",
        "subject": "$SYS.ACCOUNT.*.>",
        "type": "stream",
        "account_token_position": 3,
        "description": "Account specific monitoring stream",
        "info_url": "https://docs.nats.io/nats-server/configuration/sys_accounts"
      },

Currently in this library it's defined as an int
   /// <summary>
    /// Gets or sets the type property.
    /// </summary>
    [JsonPropertyName("type")]
    [JsonIgnore(Condition = JsonIgnoreCondition.WhenWritingDefault)]
    public int Type { get; set; }

Expected behavior
Should be able to set a string for export type.
Library version
1.0.0 preview 3
Host environment
No response
Steps to reproduce
No response

Looks like it should've been an enum: https://github.com/nats-io/jwt/blob/ed3fbfa49a16cf4aced84aed9d527be532730ad4/v2/types.go#L55-L64
// ExportType defines the type of import/export.
type ExportType int

const (
	// Unknown is used if we don't know the type
	Unknown ExportType = iota
	// Stream defines the type field value for a stream "stream"
	Stream
	// Service defines the type field value for a service "service"
	Service
)

That's great - many thanks.


Unable to login to EC2 instance with key created using cli

Hi,
I am unable to connect to an EC2 instance whose key has been created using CLI. I have tried creating the key and the EC2 instance twice but it always fails saying Load key invalid format.

However it works fine when I use a console created key.
Is there anything wrong with my create key command?
PS E:\Keys> aws ec2 create-key-pair --key-name CliKey --output text --query KeyMaterial > CliKey.pem
Kindly let me know where the issue is.
Regards
Ramesh

Note that for Windows PowerShell, the > file redirection defaults to UTF-8 encoding, which cannot be used with some SSH clients.
So, you must explicitly specify ASCII encoding in the out-file command.
---> $aws ec2 create-key-pair --key-name MyKeyPair --query 'KeyMaterial' --output text | out-file -encoding ascii -filepath MyKeyPair.pem
Ex:   aws ec2 create-key-pair --key-name CliKey --output text --query KeyMaterial | out-file -encoding ascii -filepath CliKey.pem
(or)
If you want to login using the key which is created in the format of utf-8( using the above command that you've used) you need to convert it into ascii.
Ex :
step 1   $aws ec2 create-key-pair --key-name CliKey --output text --query KeyMaterial > CliKey.pem
step 2  $ cat .\CliKey2.pem | out-file -encoding ascii -filepath<EMAIL_ADDRESS>note: Don't convert the file within the same directory. Specify different path for output( -filepath )

Thanks a lot Malli.
Exactly what I suspected.
I will close this issue as soon as I get a chance to verify this.
Currently struggling with issue #123


Library will not compile

NSData.hexString should be NSData.toHexString() when generating the signature

/cc @hamchapman

Will update this today. Thanks for the spot


chore: Helm chart reconfiguration

Changing wadm and config positions in values.yaml
When bringing in wadm as a subchart, the resulting values.yaml stutters. Ex:
nats:
  config:
   ...

wadm:
  wadm:
    config:

Further example in https://github.com/wasmCloud/wasmCloud-contrib/pull/19
Increasing release from 0.2.5 to 0.3.0 due to this config change.
Templating in nats.server
Allows dynamic values, helpful in automated installs. Example:
config:
  wadm:
   nats:
    server: "{{ .Release.Name }}"

I think this is a valid change still, not sure if you wanted to try to bring this up to date with the latest chart version so we can maybe get it merged in?


rpm install fails on ubuntu 20.14

trying to install from git
simons@simons:~/Google-Play-Music-Desktop-Player-UNOFFICIAL-$ npm install
npm WARN deprecated<EMAIL_ADDRESS>🙌  Thanks for using Babel: we recommend using babel-preset-env now: please read https://babeljs.io/env to update!
npm WARN deprecated<EMAIL_ADDRESS>Removed event-stream from gulp-header
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated<EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated<EMAIL_ADDRESS>gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated<EMAIL_ADDRESS>gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated<EMAIL_ADDRESS>please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated<EMAIL_ADDRESS>Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated<EMAIL_ADDRESS>Please use the native JSON object instead of JSON 3
npm WARN deprecated<EMAIL_ADDRESS>gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated<EMAIL_ADDRESS>This module is no longer maintained, try this instead:
npm WARN deprecated   npm i nyc
npm WARN deprecated Visit https://istanbul.js.org/integrations for other alternatives.
npm WARN deprecated<EMAIL_ADDRESS>This package is unmaintained. Use @sinonjs/formatio instead
npm WARN deprecated<EMAIL_ADDRESS>this package is now deprecated
npm WARN deprecated<EMAIL_ADDRESS>This package has been deprecated in favour of @sinonjs/samsam
npm WARN deprecated<EMAIL_ADDRESS>This is a stub types definition. form-data provides its own type definitions, so you do not need this installed.
npm WARN deprecated<EMAIL_ADDRESS>outdated version, please use @next
npm WARN deprecated<EMAIL_ADDRESS>This is a stub types definition. p-cancelable provides its own type definitions, so you do not need this installed.
npm WARN deprecated<EMAIL_ADDRESS>This is a stub types definition. p-retry provides its own type definitions, so you do not need this installed.
npm WARN deprecated<EMAIL_ADDRESS>This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated<EMAIL_ADDRESS>wrench.js is deprecated! You should check out fs-extra (https://github.com/jprichardson/node-fs-extra) for any operations you were using wrench for. Thanks for all the usage over the years.
npm WARN deprecated<EMAIL_ADDRESS>This package has been deprecated in favour of @sinonjs/samsam
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated<EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated<EMAIL_ADDRESS>cross-spawn no longer requires a build toolchain, use it instead
npm WARN deprecated<EMAIL_ADDRESS>This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated<EMAIL_ADDRESS>CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated<EMAIL_ADDRESS>This module relies on Node.js's internals and will break at some point. Do not use it, and update to<EMAIL_ADDRESS>npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Use uuid module instead
npm WARN deprecated<EMAIL_ADDRESS>ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js

><EMAIL_ADDRESS>install /home/simons/Google-Play-Music-Desktop-Player-UNOFFICIAL-/node_modules/abstract-socket
> node-gyp rebuild

make: Entering directory '/home/simons/Google-Play-Music-Desktop-Player-UNOFFICIAL-/node_modules/abstract-socket/build'
  CXX(target) Release/obj.target/bindings/src/abstract_socket.o
In file included from ../src/abstract_socket.cc:5:
../../nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker*)’:
../../nan/nan.h:2294:62: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
 2294 |     , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
      |                                                              ^
In file included from ../../nan/nan.h:56,
                 from ../src/abstract_socket.cc:5:
../src/abstract_socket.cc: At global scope:
/usr/include/nodejs/src/node.h:573:43: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
  573 |       (node::addon_register_func) (regfunc),                          \
      |                                           ^
/usr/include/nodejs/src/node.h:607:3: note: in expansion of macro ‘NODE_MODULE_X’
  607 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
      |   ^~~~~~~~~~~~~
../src/abstract_socket.cc:181:1: note: in expansion of macro ‘NODE_MODULE’
  181 | NODE_MODULE(abstract_socket, Initialize)
      | ^~~~~~~~~~~
In file included from /usr/include/nodejs/src/node.h:63,
                 from ../../nan/nan.h:56,
                 from ../src/abstract_socket.cc:5:
/usr/include/nodejs/deps/v8/include/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)]’:
/usr/include/nodejs/src/node_object_wrap.h:84:78:   required from here
/usr/include/nodejs/deps/v8/include/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<node::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
 9502 |                reinterpret_cast<Callback>(callback), type);
      |                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/nodejs/deps/v8/include/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)]’:
../../nan/nan_object_wrap.h:65:61:   required from here
/usr/include/nodejs/deps/v8/include/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<Nan::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
  SOLINK_MODULE(target) Release/obj.target/bindings.node
  COPY Release/bindings.node
make: Leaving directory '/home/simons/Google-Play-Music-Desktop-Player-UNOFFICIAL-/node_modules/abstract-socket/build'

><EMAIL_ADDRESS>install /home/simons/Google-Play-Music-Desktop-Player-UNOFFICIAL-/node_modules/fs-xattr
> node-gyp rebuild

make: Entering directory '/home/simons/Google-Play-Music-Desktop-Player-UNOFFICIAL-/node_modules/fs-xattr/build'
  CXX(target) Release/obj.target/xattr/src/async.o
In file included from ../src/async.cc:2:
../../nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker*)’:
../../nan/nan.h:2294:62: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
 2294 |     , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
      |                                                              ^
../src/async.cc: In member function ‘virtual void XattrWorker::HandleErrorCallback()’:
../src/async.cc:35:27: warning: ‘v8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::Value>*) const’ is deprecated [-Wdeprecated-declarations]
   35 |     callback->Call(1, argv);
      |                           ^
In file included from ../src/async.cc:2:
../../nan/nan.h:1742:3: note: declared here
 1742 |   Call(int argc, v8::Local<v8::Value> argv[]) const {
      |   ^~~~
../src/async.cc: In constructor ‘SetWorker::SetWorker(v8::Local<v8::Value>, v8::Local<v8::Value>, v8::Local<v8::Value>, Nan::Callback*)’:
../src/async.cc:52:55: warning: ‘v8::Local<v8::Object> v8::Value::ToObject() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
   52 |     v8::Local<v8::Object> bufferObj = value->ToObject();
      |                                                       ^
In file included from /usr/include/nodejs/src/node.h:63,
                 from ../src/async.cc:1:
/usr/include/nodejs/deps/v8/include/v8.h:10046:15: note: declared here
10046 | Local<Object> Value::ToObject() const {
      |               ^~~~~
../src/async.cc: In member function ‘virtual void GetWorker::HandleOKCallback()’:
../src/async.cc:129:27: warning: ‘v8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::Value>*) const’ is deprecated [-Wdeprecated-declarations]
  129 |     callback->Call(2, argv);
      |                           ^
In file included from ../src/async.cc:2:
../../nan/nan.h:1742:3: note: declared here
 1742 |   Call(int argc, v8::Local<v8::Value> argv[]) const {
      |   ^~~~
../src/async.cc: In member function ‘virtual void ListWorker::HandleOKCallback()’:
../src/async.cc:186:27: warning: ‘v8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::Value>*) const’ is deprecated [-Wdeprecated-declarations]
  186 |     callback->Call(2, argv);
      |                           ^
In file included from ../src/async.cc:2:
../../nan/nan.h:1742:3: note: declared here
 1742 |   Call(int argc, v8::Local<v8::Value> argv[]) const {
      |   ^~~~
In file included from /usr/include/nodejs/src/node.h:63,
                 from ../src/async.cc:1:
/usr/include/nodejs/deps/v8/include/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)]’:
/usr/include/nodejs/src/node_object_wrap.h:84:78:   required from here
/usr/include/nodejs/deps/v8/include/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<node::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
 9502 |                reinterpret_cast<Callback>(callback), type);
      |                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/nodejs/deps/v8/include/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)]’:
../../nan/nan_object_wrap.h:65:61:   required from here
/usr/include/nodejs/deps/v8/include/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<Nan::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
  CXX(target) Release/obj.target/xattr/src/error.o
In file included from ../src/error.cc:3:
../../nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker*)’:
../../nan/nan.h:2294:62: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
 2294 |     , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
      |                                                              ^
../src/error.cc: In function ‘v8::Local<v8::Value> MakeXattrError(int)’:
../src/error.cc:109:79: warning: ‘v8::Local<v8::Object> v8::Value::ToObject() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
  109 |   v8::Local<v8::Object> err = Nan::Error(errorDescriptionForGet(e))->ToObject();
      |                                                                               ^
In file included from /usr/include/nodejs/src/node.h:63,
                 from ../src/error.cc:2:
/usr/include/nodejs/deps/v8/include/v8.h:10046:15: note: declared here
10046 | Local<Object> Value::ToObject() const {
      |               ^~~~~
/usr/include/nodejs/deps/v8/include/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)]’:
/usr/include/nodejs/src/node_object_wrap.h:84:78:   required from here
/usr/include/nodejs/deps/v8/include/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<node::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
 9502 |                reinterpret_cast<Callback>(callback), type);
      |                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/nodejs/deps/v8/include/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)]’:
../../nan/nan_object_wrap.h:65:61:   required from here
/usr/include/nodejs/deps/v8/include/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<Nan::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
  CXX(target) Release/obj.target/xattr/src/sync.o
In file included from ../src/sync.cc:2:
../../nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker*)’:
../../nan/nan.h:2294:62: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
 2294 |     , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
      |                                                              ^
../src/sync.cc: In function ‘Nan::NAN_METHOD_RETURN_TYPE xattr_set_sync(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/sync.cc:58:55: warning: ‘v8::Local<v8::Object> v8::Value::ToObject() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
   58 |   v8::Local<v8::Object> bufferObj = info[2]->ToObject();
      |                                                       ^
In file included from /usr/include/nodejs/src/node.h:63,
                 from ../src/sync.cc:1:
/usr/include/nodejs/deps/v8/include/v8.h:10046:15: note: declared here
10046 | Local<Object> Value::ToObject() const {
      |               ^~~~~
/usr/include/nodejs/deps/v8/include/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)]’:
/usr/include/nodejs/src/node_object_wrap.h:84:78:   required from here
/usr/include/nodejs/deps/v8/include/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<node::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
 9502 |                reinterpret_cast<Callback>(callback), type);
      |                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/nodejs/deps/v8/include/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)]’:
../../nan/nan_object_wrap.h:65:61:   required from here
/usr/include/nodejs/deps/v8/include/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<Nan::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
  CXX(target) Release/obj.target/xattr/src/util.o
In file included from ../src/util.cc:2:
../../nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker*)’:
../../nan/nan.h:2294:62: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
 2294 |     , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
      |                                                              ^
In file included from /usr/include/nodejs/src/node.h:63,
                 from ../src/util.cc:1:
/usr/include/nodejs/deps/v8/include/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)]’:
/usr/include/nodejs/src/node_object_wrap.h:84:78:   required from here
/usr/include/nodejs/deps/v8/include/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<node::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
 9502 |                reinterpret_cast<Callback>(callback), type);
      |                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/nodejs/deps/v8/include/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)]’:
../../nan/nan_object_wrap.h:65:61:   required from here
/usr/include/nodejs/deps/v8/include/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<Nan::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
  CXX(target) Release/obj.target/xattr/src/xattr.o
In file included from ../src/xattr.cc:2:
../../nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker*)’:
../../nan/nan.h:2294:62: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
 2294 |     , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
      |                                                              ^
In file included from ../src/xattr.cc:1:
../src/xattr.cc: At global scope:
/usr/include/nodejs/src/node.h:573:43: warning: cast between incompatible function types from ‘void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)’ {aka ‘void (*)(v8::Local<v8::Object>)’} to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
  573 |       (node::addon_register_func) (regfunc),                          \
      |                                           ^
/usr/include/nodejs/src/node.h:607:3: note: in expansion of macro ‘NODE_MODULE_X’
  607 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
      |   ^~~~~~~~~~~~~
../src/xattr.cc:27:1: note: in expansion of macro ‘NODE_MODULE’
   27 | NODE_MODULE(xattr, Initialize)
      | ^~~~~~~~~~~
In file included from /usr/include/nodejs/src/node.h:63,
                 from ../src/xattr.cc:1:
/usr/include/nodejs/deps/v8/include/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)]’:
/usr/include/nodejs/src/node_object_wrap.h:84:78:   required from here
/usr/include/nodejs/deps/v8/include/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<node::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
 9502 |                reinterpret_cast<Callback>(callback), type);
      |                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/nodejs/deps/v8/include/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)]’:
../../nan/nan_object_wrap.h:65:61:   required from here
/usr/include/nodejs/deps/v8/include/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<Nan::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
  SOLINK_MODULE(target) Release/obj.target/xattr.node
  COPY Release/xattr.node
make: Leaving directory '/home/simons/Google-Play-Music-Desktop-Player-UNOFFICIAL-/node_modules/fs-xattr/build'

><EMAIL_ADDRESS>install /home/simons/Google-Play-Music-Desktop-Player-UNOFFICIAL-/node_modules/mdns
> node-gyp rebuild

make: Entering directory '/home/simons/Google-Play-Music-Desktop-Player-UNOFFICIAL-/node_modules/mdns/build'
  CXX(target) Release/obj.target/dns_sd_bindings/src/dns_sd.o
In file included from ../src/dns_sd.cpp:1:
../src/mdns.hpp:32:10: fatal error: dns_sd.h: No such file or directory
   32 | #include <dns_sd.h>
      |          ^~~~~~~~~~
compilation terminated.
make: *** [dns_sd_bindings.target.mk:168: Release/obj.target/dns_sd_bindings/src/dns_sd.o] Error 1
make: Leaving directory '/home/simons/Google-Play-Music-Desktop-Player-UNOFFICIAL-/node_modules/mdns/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/share/nodejs/node-gyp/lib/build.js:194:23)
gyp ERR! stack     at ChildProcess.emit (events.js:198:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
gyp ERR!  You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of register-scheme@github:devsnek/node-register-scheme but none is installed. You must install peer dependencies yourself.

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!

You need to install the libavahi-compat-libdnssd-dev package with apt.

Thank you fixed!


Adding Privacy Statement

This adds the first text sample to the site for our privacy policy.
Closes #2149

Got address from @tonysurma. Closing this for now, but obviously still open for feedback and we can update with a future commit/PR.


Clarification Needed - Registry Change Tracking

In the older version of the document, a column in the table under Change Tracking data collection details section mentioned the agent does not send different when Registry changes are detected. That column has now been removed. Does that mean the limitation has been lifted?

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

ID: 6b338aff-04ac-4867-2aea-e9e12bb750cc
Version Independent ID: 4dc5a70f-90db-de1b-78bd-c1af42d3a89f
Content: Track changes with Azure Automation
Content Source: articles/automation/automation-change-tracking.md
Service: automation
GitHub Login: @georgewallace
Microsoft Alias: gwallace

@zhusulai Thank you very much for your interest in Azure product and services. We are currently investigating this and will update you shortly.

@georgewallace any ideas on this please?

@MicrosoftDocs/azure-cxp-triage #please-close

does it work with NTFS SMB share file