HTTP headers not in the correct format when using Azure.Storage.Blobs v12.8.x

Which service(blob, file, queue, table) does this issue concern?
Blob.
Which version of the Azurite was used?
Pulled from master on 2021-05-31, version 3.9.0.
Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
Run with npm having pulled from Github.
What's the Node.js version?
v10.15.3
What problem was encountered?
When I try to connect to a Blob storage container, an exception is thrown (below). This only occurs when using Azure.Storage.Blobs nuget package greater than v12.7.0. The issue does not occur with v12.7.0.
System.AggregateException
HResult=0x80131500
Message=One or more errors occurred. (The value for one of the HTTP headers is not in the correct format.
RequestId:25352f9e-abaf-44bd-bdc7-eb538bc842f8
Time:2021-05-31T12:28:36.521Z
Status: 400 (The value for one of the HTTP headers is not in the correct format.)
ErrorCode: InvalidHeaderValue
Additional Information:
HeaderName: x-ms-version
HeaderValue: 2020-04-08
Headers:
Server: Azurite-Blob/3.9.0
x-ms-error-code: InvalidHeaderValue
x-ms-request-id: 25352f9e-abaf-44bd-bdc7-eb538bc842f8
Date: Mon, 31 May 2021 12:28:36 GMT
Connection: keep-alive
Transfer-Encoding: chunked
Content-Type: application/xml
)
Source=System.Private.CoreLib
StackTrace:
at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at System.Threading.Tasks.Task.Wait()
at OddsFactory.Propaganda.Infrastructure.Blob.DelayedMessageArchive..ctor(ILogger logger, IStorageAccountConfiguration config, IBlobSerializer serializer) in C:\Code\OddsFactory.Propaganda\src\OddsFactory.Propaganda.Infrastructure.Blob\DelayedMessageArchive.cs:line 44
This exception was originally thrown at this call stack:
[External Code]
Inner Exception 1:
RequestFailedException: The value for one of the HTTP headers is not in the correct format.
RequestId:25352f9e-abaf-44bd-bdc7-eb538bc842f8
Time:2021-05-31T12:28:36.521Z
Status: 400 (The value for one of the HTTP headers is not in the correct format.)
ErrorCode: InvalidHeaderValue
Additional Information:
HeaderName: x-ms-version
HeaderValue: 2020-04-08
Headers:
Server: Azurite-Blob/3.9.0
x-ms-error-code: InvalidHeaderValue
x-ms-request-id: 25352f9e-abaf-44bd-bdc7-eb538bc842f8
Date: Mon, 31 May 2021 12:28:36 GMT
Connection: keep-alive
Transfer-Encoding: chunked
Content-Type: application/xml
Steps to reproduce the issue?
Install Azure.Storage.Blobs v12.8.x, and write any code that tries to write to access the blob emulator.
Example:
var blobClient = new BlobServiceClient(/* connection string */);
var container = blobClient.GetBlobContainerClient(/* container name */);
container.CreateIfNotExistsAsync().Wait(); // throws exception

Have you found a mitigation/solution?
Lock the Azure.Storage.Blobs package to v12.7.0

@lyallguiney
Would you please share the Azurite debug log for this failed request?
It looks some new header in 12.8.0 is still not supported by Azurite, but we need the debug log to get the details.

Ah, apologies. Yes, updating to the latest Azurite version works. I thought I had pulled and re-built the code, but evidently not. :(
All good, thanks! :)

@lyallguiney
It's good to know your issue is resolved.
I will close the issue.
Feel free to contact us again if you need any further assistance of Azurite.


DNN 9348 Recalculate Search Results page's input box on window resize

Recalculate the input field and close icon's CSS attributes when the window has been resized.

Changes looks good and merged.


HAWQ-1460. WAL Send Server process should exit if postmaster on maste…

…r is killed

@jiny2 @linwen Could you please take a look at this?

+1

+1 LGTM. Thanks.


Show "did you mean?" when an asset doesn't exist

Closed by https://github.com/luckyframework/web/blob/master/src/run_macros/missing_asset.cr#L15


Glitch in "A Bug's Lynx"

Tested the ROM with the 0.5.0 version and it seems the glitch is no more here

great. So closing, as it was only this visual issue here.


[PROPOSAL] Add SPDX License header and checker

What/Why
What are you proposing?
All source code should have an SPDX license header.
What users have asked for this feature?
Standard org-wide practice.
What problems are you trying to solve?
Org-wide practice says we need SPDX license headers everywhere.
What is the developer experience going to be?
CI fails if a source file (e.g. .ts) is missing a license header.

License headers added to TypeScript files in https://github.com/opensearch-project/opensearch-api-specification/pull/311, but we still need them in the YAMLs I think.


dotnet-sdk : init at 2.0.3

Motivation for this change
Introduce dotnet-sdk package (dotnet client utility).
Things done
Wrapped pre-built linux binaries.

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

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

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

@copumpkin, @Mic92, @obadz please review.

@adisbladis thanks for review, addressed

Does anything refer to this file?

@copumpkin not yet. Would you suggest adding it to top level packages?

Yeah, or if not, explain somewhere how to use it.

@copumpkin done

@GrahamcOfBorg dotnet-sdk

Looks good, thanks!

@kuznero in general, I've seen no space between the colon and the package name, so I think the more common formatting would have been "dotnet-sdk: init at ..."
Also, do you have any plans/ideas about a source build of this? It'd be nice to get it on Darwin too, as well as get the usual patchability benefits we get with source builds.

@copumpkin, I have tried it in the first place, but it has a big number of nuget dependences which will only make it more difficult for creating sandboxed package. On the other hand, there is a pre built version of sdk also for Windows and Mac OS, so it should be possible to pull it to and patch (probably differently for Darwin).
Even though it is doable to build sources, I simply thought that it is not practical to spend so much time on it now.
Can you please name benefits for doing it, granted that we will end up downloading many more pre built packages for that? If not download then build with mono, which is not in the perfect condition either in NixOS at the moment.

@kuznero it's just generally a preference we have in nixpkgs. If you look, the vast majority of our packages (I'd bet over 99%) are built from source because it affords us more flexibility (we can apply on-the-fly patches to them, they're more pleasant to audit, less trust of other people's build infrastructure, etc.), even if it's more up-front work. Not saying you need to do the work, TBC, but at some point I'd want us to get some good automation around .NET package dependencies so that it isn't much work to make a build like this work. For now this is definitely fine 😄

@copumpkin get your point, agree.


Tests aren't running in TravisCI

Are you able to setup tests in TravisCI?
Otherwise I have a feeling things will go stale.
It also means potential breaks with PRs / etc can be caught automatically without you pulling down the repo and running the tests.

This is something I'm keen to do across all my modules, thanks for the reminder!

If this issue still applies, can you please open it on https://github.com/symbiote/silverstripe-extensible-search which will be the source of truth moving forwards.

If this issue still applies, can you please open it on https://github.com/symbiote/silverstripe-extensible-search which will be the source of truth moving forwards.


App crashes on launch.

I am able to get the project compiling but it crashes as soon as it launches. I've tested this on a physical Samsung Galaxy S8 and an emulated Pixel 3. Both produce the same results.
It seems to be crashing on line 15 in AGApplication.java.
mWorkerThread.start();

It produces the error:
E/AndroidRuntime: FATAL EXCEPTION: Thread-6
    Process: io.agora.openlive.voice.only, PID: 13997
    java.lang.RuntimeException: NEED TO check rtc sdk init fatal error
    java.lang.IllegalArgumentException: cannot initialize Agora Rtc Engine, error=101
        at io.agora.rtc.internal.RtcEngineImpl.nativeObjectInit(Native Method)
        at io.agora.rtc.internal.RtcEngineImpl.<init>(RtcEngineImpl.java:185)
        at io.agora.rtc.RtcEngine.create(RtcEngine.java:65)
        at io.agora.openlive.voice.only.model.WorkerThread.ensureRtcEngineReadyLock(WorkerThread.java:183)
        at io.agora.openlive.voice.only.model.WorkerThread.run(WorkerThread.java:97)

        at io.agora.openlive.voice.only.model.WorkerThread.ensureRtcEngineReadyLock(WorkerThread.java:186)
        at io.agora.openlive.voice.only.model.WorkerThread.run(WorkerThread.java:97)

I have tried integrating the SDK through JCenter using the provided Gradel configuration as well as manually integrating the SDK that I downloaded from Agora.

My key was incorrect.


Bugfix - docker_rpmbuild.sh doesn't run to completion

There are a few issues with specs/default/cluster-init/files/00-build-slurm.sh which prevent the wrapper script from running to completion. I've tried to split these changes out into individual commits but it didn't make sense to have several PRs. The below changes lead to all the 20.11.7 .rpm/.deb files building successfully.

The function install_pmix is invoked before the yum command installing its dependencies is run. Causing it to fail. Addressed in afdd7b07fcb27dab8882f5710820cde245bfd393.
The flex library is needed in order to install pmix. Fixed in 8941b602d6556ab8f97e45bbd94932f6e338979e.
The install_pmix function ends in ../../install/v3/ rather than ~/. This is breaking as this context persists through to the download and extraction of slurm, causing the tar command to fail and preventing the building of the cyclecloud plugin. Fixed in 877665ef755d085a54800001881107001bf576fb.
https://github.com/Azure/cyclecloud-slurm/blob/6c788e1f11fd6ffa4c66b29aa9e6cb35074a6e25/specs/default/cluster-init/files/00-build-slurm.sh#L42-L49
Centos 8 passed End of Life on Dec 31st 2021, and the yum mirrors built in to the latest image no longer exist. Following the instructions here, we can point to vault.centos.org instead. This change is incompatible with the change in 3e6005fdd98d78210a1d8de6cf71aa0a2471efbb so the change made in that commit is reverted.
Implemented in 7c4edf756513d760101b3272b2e97ab9df84185d.

Closing as has been separately implemented in 49cecb3d4aee8c01e81c2d36d3be44359d9a595e.


Error while go-getting: use of internal package not allowed

Go get returns this error:
$ go get github.com/GoogleCloudPlatform/go-endpoints/endpoints
package github.com/GoogleCloudPlatform/go-endpoints/endpoints
imports google.golang.org/appengine/internal: use of internal package not allowed
package github.com/GoogleCloudPlatform/go-endpoints/endpoints
imports google.golang.org/appengine/internal/user: use of internal package not allowed

You're running "go get" from the wrong path.
But the bug is this package should have that more explicitly declared so you get a good error message.
/cc @okdave @rakyll @gmlewis

Do you mean I'm using the wrong version of go, or my cwd is wrong?

Francesc, can you handle this? Both answering the question and adding import comments if needed?  (aren't we using cloud.golang.org/... custom import path for these?)

The path is correct, but you need to use goapp get instead of go get
To install goapp download the Go SDK for App Engine here

looks like goapp doesn't work either as of the App Engine update to 1.6. Looks like there are a couple issues and PRs out there. #101 #114 #131


In for-await-of, only call return() for an abrupt completion in user code

This wraps user code in a for-await-of statement so that we only call iter.return() when user code exits abruptly. This better aligns with ForIn/OfBodyEvaluation which only calls IteratorClose when there is an abrupt completion in the body.
Fixes #50525

Basically, the only step of ForIn/OfBodyEvaluation that should trigger IteratorClose is an abrupt completion during the evaluation of the iterator statement body. This just adds a variable that is set to true when entering the loop, temporarily set to false only while evaluating the body statement.
Here's a (hopefully) easier to read version where the temp variables have been renamed to indicate their purpose:
// source
for await (const x of y) {
  ...
}

// output
var _done, _value, _errorFromLoopBody, _returnFunction, _result;
try {
    var _nonUserCode = true; // start non-user code section
    for (var _iter = y[Symbol.asyncIterator](); _result = await _iter.next(), _done = _result.done, !_done;) {
        _value = _result.value;
        _nonUserCode = false; // end non-user code
        // start user code
        try {
            const x = _value;
            ...
        }
        finally {
            // end user code
            _nonUserCode = true; // start non-user code
        }
    }
}
catch (error) {
    _errorFromLoopBody = { error };
}
finally {
    try {
        if (!_nonUserCode && !_done && (_returnFunction = _iter.return)) {
            yield _returnFunction.call(_iter);
        }
    }
    finally {
        if (_errorFromLoopBody) throw _errorFromLoopBody.error;
    }
}
// end non-user code

Looks like this works with main locally.


deno docker

Adds a container image based on deno runtime
Fixes the virtualenv issue reported here

@cerrussell, Could you kindly help review and test this fix? Thank you.

:pray:
but still waiting for dependency-track and grype to support cdx 1.5 :cry:


Adds eslint and fixes all resulting errors

I'll try my best to summarize all the fixes that occurred:

the parser has a bug, it cannot parse <div>() => thisIsExampleCode</div>, so I had to change each => into a =>
forgot the key's to some .maps (they help react re-render)
removed and fixed lots of // @ts-ignore's (for shame 🤣)
removed the type Function
some spacing, and some things that eslint did automatically.

TODO:

installed eslint-plugin-jsx-a11y to help make the doc's more accessible... unfortunately there are 49 errors, and it could take me some time to go through them as they need to be done well or they wont be accessible, they'll just pass the tests. Leaving it for a future commit

Fun Fact:

Started out with ~200 errors
ended with 0 errors and 510 warnings 😱 (alot of the a11y errors are emoji... screen readers need some help with emoji's)

lol! awesome stuff! love this, we can improve over the time anyhow 👍


insertRule is exponentially much slower in development mode

Environment
System:

OS: macOS 12.0.1
CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
Memory: 294.21 MB / 16.00 GB
Shell: 3.3.1 - /usr/local/bin/fish

Binaries:

Node: 16.11.1 - /usr/local/bin/node
Yarn: 1.22.15 - /usr/local/bin/yarn
npm: 8.0.0 - /usr/local/bin/npm

React version: 17
Styled Components: 5
Build: Webpack 5
Reproduction
Sadly, this is a very complex proprietary project so I cannot provide a runnable example. Instead I will provide a snippet of the JS profile:

The above is taken when running in development mode locally. When running in production mode, renders are extremely fast and inserting styles takes less than a few percent of the total render. In development, inserting styles takes 60% of the total runtime.
Expected Behavior
Renders should be fast in development mode
Actual Behavior
Renders is exponentially much slower in development mode as opposed to production mode.

This actually looks like CSSOM i.e. insertRule isn't enabled for you. I haven't quite checked that, since in V6 we'll likely get rid of our TextNode-based shim, but if you provide your bundler with this env var to be replaced with "false" you can force enable it in development: https://github.com/styled-components/styled-components/blob/9b3457036cfedf1d5336f654f3171657630a9fd8/packages/styled-components/src/constants.js#L17

That did the trick, thanks!


Index only adds 12 items at a time (Python)

Hi Ash,
great library!
I'm having some trouble:
My indices contain fewer items than I add.
In fact, I'm having this issue even when running the sample Python code from your README.md.
import numpy as np
import usearch

index = usearch.Index(
    dim=256, # Define the number of dimensions in input vectors
    metric='cos', # Choose the "metric" or "distance", default = 'ip', optional
    dtype='f16', # Quantize to 'f16' or 'i8q100' if needed, default = 'f32', optional
    connectivity=16, # How frequent should the connections in the graph be, optional
    expansion_add=128, # Control the recall of indexing, optional
    expansion_search=64, # Control the quality of search, optional
)

n = 100
labels = np.array(range(n), dtype=np.longlong)
vectors = np.random.uniform(0, 0.3, (n, index.ndim)).astype(np.float32)

# check for duplicate vectors
vectors_deduped = np.unique(vectors, axis=0)
assert len(vectors_deduped) == len(vectors), "Duplicate vectors found"

# ensure we have n labels and vectors
assert len(vectors) == len(labels) == n, "Number of vectors and labels must match"

# You can avoid copying the data
# Handy when build 1B+ indexes of memory-mapped files
index.add(labels, vectors, copy=True)
assert len(index) == n, f"Index should contain {n} items, but contains {len(index)}"

Output:
`AssertionError: Index should contain 100 items, but contains 12``
Curiously:

I'm getting 12 items, no matter whether I add 100 items or 1_000. If I add 12 or fewer, the assertion passes. As soon as I pass 13, only 12 are added.
If I re-run the index.add() line, the index size increments by 12 every time.
I tried initializing the index with capacity=100, but that also didn't change things.
The parameter copy=True also apparently doesn't influence this behavior. I tried it both True and False.

My questions:

What am I doing wrong?

What does copy=True actually do? I didn't find any further documentation. It allows the index to just reference the label/vector data as long as it's stored in, say, an numpy array? Also, does copy=True mean "Yes, copy the data", or does it mean "Avoid copying the data"? Since you're explicity passing it when stating "You can avoid copying the data", it's a bit ambiguous.

Thank you!

Yes, you are right, there is a bug in the Python wrapper layer. I noticed it yesterday, will share a patch later today.
Copy is True by default. If you pass False, the index will be storing a pointer to some external vector. It’s useful when you want to construct an index of a memory-mapped binary file and you don’t have enough RAM for both index and vectors.

It was solved with caee311. The new image should reach PyPi in 30m.


Use SymbolFinder.FindDerivedClassesAsync inside "find implementations" endpoint

Replace the hand-rolled code used to find derived named type symbols with SymbolFinder.FindDerivedClassesAsync. That API didn't exist at the time of writing that feature - it was only added, I believe, for VS15.
Also enabled the find implementations code to run on CSX files.

thanks a lot for the comments!
Would you mind having a look again?
I pushed a new commit now, where I renamed the extension methods to Add and AddRange (makes total sense), and removed all asynchronicity on all these quick fix related methods. Since we always construct the QuickFix from a Location instance, that old async call to get the syntax tree can really be simply replaced by the .SourceTree property of the Location. As such I renamed QuickFixHelper to a LocationExtensions as it makes more logical sense to me.
I left the workspace in there, because the helper looks up the document based on the location and attaches the project information to the QuickFix object. Since we don't have these documents or their SourceText earlier (these locations are results of SymbolFinder operations and can be scattered all over solution) I wasn't sure what we could replace it with to make it more efficient.

@DustinCampbell I pushed one additional change to this PR, to include the original location of a non-abstract symbol in the result set. This is the same behavior as VS currently has and that didn't exist in OmniSharp (for example go to implementation on a variable should take you to the declaration of the variable).


Simplify code in Jinja templates

We have lot of code duplication in our Jinja templates.
This PR simplifies it.

I am not sure about this one. I like it to be explicit more - or to be fully automated i.e deserialisable.
We also have created an issue to look into this. I can link it tomorrow morning (I am on the phone right now).

I feel this is explicit and reduces the surface area of errors when copy/pasting but I will leave it up to you to check tomorrow when you are back on laptop

I am not sure about this one. I like it to be explicit more - or to be fully automated i.e deserialisable.
We also have created an issue to look into this. I can link it tomorrow morning (I am on the phone right now).

@feluelle The ticket #1284 is related to this PR, right?
https://github.com/astronomer/astro-sdk/issues/
I remember us talking about this and that there are possibly other approaches you'd like to try out - including what @dimberman did with the Databricks implementation.
I think we have two ways of moving forward:

We merge this change, and we revisit it after - as part of #1284 (if we think it has more pros than the current implementation)
We don't merge this change and review the approach as part o #1284 (I'm adding it to the milestone 0.4)

I'm happy for @kaxil and @feluelle to make a call on this - or we can discuss as a team in the next session if we don't converge before :)

I am in favor of 2 - not merging and reviewing it as part of ticket 1284.
In the current state it would even break existing functionality, see my https://github.com/astronomer/astro-sdk/pull/1367#discussion_r1041064284. So we would have to be more careful on the type per loop. We basically need a loop for strings & raw values such as booleans. That's why I am in favor of being explicit here.

In the current state it would even break existing functionality, see my https://github.com/astronomer/astro-sdk/pull/1367#discussion_r1041064284.

Fixed the breaking change :) but no strong opinion

Closing it for now, you can always re-open it if needed when someone picks up that task


WIP: Re-enable e2e tests

What type of PR is this?
/kind failing-test
What this PR does / why we need it:
https://github.com/actions/runner-images/issues/8730 seems to have resolved, so we now re-enable the e2e tests.
Which issue(s) this PR fixes:

None
Does this PR have test?
None

Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

None

The issue still exists.


Fix for download URL for Xee 3.4

Adapted for changes to Xee download URL.

Thank you for the contribution. It was merged directly as 16a193af17a17bb01fe9b1d6fd0bb10875710ab4 to keep commit history cleaner. Your contribution is still credited to you.


Fix invocation of StandardSession#exclude method

Fixed invocation of StandardSession#exclude method so that it works even
with older Tomcat versions where only the one parameter version of this
method was present.
If only the legacy one parameter method is detected, it is invoked via
reflection, otherwise the new two parameter variant is invoked in
standard manner.
This fix was tested with Tomcat 8.0.14 (which only has the one parameter
exclude method) and 8.0.36 (which has both one and two parameter exclude
methods).
Fixes #303

Thanks for the PR! I just released 1.9.7 with this fix.

Thanks.


JAV-409 Automate the signing of release on tagged commit

Coverage decreased (-0.007%) to 86.204% when pulling d22c1b5457710108490db62bcead8e79c3e74ba8 on asifdxtreme:master into 5baf774b555fe713e608a03572f0f58dca1db031 on ServiceComb:master.

/cc @liubao68 @wujimin @seanyinx @WillemJiang


Fix a typo in README

This fixes a typo in the README.

 You should sign our Contributor License Agreement in order to get your pull request merged.

Merged as 74a7afd


Improve accessibility in the demo app

Pull request
Description
Improve accessibility in the demo app itself. These are mostly navigation-related changes. The player will be handled separately.
Changes made

Add language information to DemoItems so TalkBack can use the proper voice when reading information.
Add collection info on lists.
Add some missing content descriptions.

Checklist

[ ] APIs have been properly documented (if relevant).
[ ] The documentation has been updated (if relevant).
[ ] New unit tests have been written (if relevant).
[x] The demo has been updated (if relevant).

Some little adjustement maybe, Shouldn't we not focus automatically the top when user choose an item in the bottom navigation bar ?

I've checked in multiple Google apps, and the behavior is always the same: when we select a tab in the bottom navigation, the focus remains there.


[Sonar Cloud]: Add constants for duplicated strings

Addressing these SonarCloud issues.
Signed-off-by: Itamar Holder<EMAIL_ADDRESS>What this PR does / why we need it:
Clear SonarCloud issues
Release note:

NONE

/retest

@iholder-redhat  is this jira ticket public https://issues.redhat.com/browse/CNV-10474 ? I didn't think it was.

@davidvossel thanks very much for your review!
I've fixed and re-pushed.

@kubevirt-bot, why do you detect this as an kind/api-change? :-)
Anyone has an idea?

@ashleyschuett @zcahana Thanks for the review :) re-pushed.

@kubevirt-bot, why do you detect this as an kind/api-change? :-)
Anyone has an idea?

+1.
Indeed a mystery.

/retest

Looks good and all review comments have been addressed. Thanks @iholder-redhat!
/lgtm

/approve


Service is reconstructed on each effect execution

What version of Effect is running?
3.10.19
What steps can reproduce the bug?
Playground: https://effect.website/play#6bcf7700ba43
import { Context, Effect, Layer } from "effect"

export class Vite extends Context.Tag("Vite")<Vite, number>() {}

let i = 0

export const ViteDev = Layer.effect(
  Vite,
  Effect.sync(() => {
    console.log("Creating Vite service...", i)

    return i++
  }),
)

const processRequest = Effect.gen(function*() {
  yield *Vite
  console.log("Processing request")
}).pipe(
  Effect.provide(ViteDev)
)

Effect.runSync(processRequest)
Effect.runSync(processRequest)
Effect.runSync(processRequest)

What is the expected behavior?
Service Vite is constructed only once ("Creating Vite service…" is only logged once)
What do you see instead?
Creating Vite service... 0
Processing request
Creating Vite service... 1
Processing request
Creating Vite service... 2
Processing request

Additional information
No response

This is the expected behavior. You can use ManagedRuntime https://effect.website/docs/runtime/#managedruntime

Indeed, with ManagedRuntime I get desired behavior:
https://effect.website/play#6bcf7700ba43
import { Context, Effect, Layer, ManagedRuntime } from "effect"

export class Vite extends Context.Tag("Vite")<Vite, number>() {}

let i = 0

export const ViteDev = Layer.effect(
  Vite,
  Effect.sync(() => {
    console.log("Creating Vite service...", i)

    return i++
  }),
)

const runtime = ManagedRuntime.make(ViteDev)

const processRequest = Effect.gen(function*() {
  yield *Vite
  console.log("Processing request")
})

runtime.runSync(processRequest)
runtime.runSync(processRequest)
runtime.runSync(processRequest)


Integration with existing click CLIs

Hi, first of all, thank you this project looks really interesting. I've always struggled with Hydra as I find it a bit too intrusive to my taste, and difficult to integrate to an existing code base. I rather prefer your API's philosophy for my configuration.
There is however an issue that prevents me from using this library in an already existing project: I cannot see a way to integrate the CLI generated by sp.cli in my existing CLI. I already have a click CLI and in the current design, sp.cli generates a standalone CLI that cannot be integrated to an existing CLI.
click allows to arbitrarily nest various command line utilities so it would be very nice if springs was able to be nested in an existing CLI.

Hi @bilelomrani1 ,
I have a work-in-progress PR at #12 . It does require a bit of re-factoring, but it should be possible to support click.


Skype Bot Running Wrong Dialog

Not sure this is the right place to post this, but I'll try.
I have a bot that have recently updated to V3. Everything is working fine, and the Bot is running my standard StartUpDialog when a message is received, no problem.
if (activity != null)             {                 switch (activity.GetActivityType())                 {                     case ActivityTypes.Message:                         await Conversation.SendAsync(activity, () => new StartUpDialog());                         break;
I've created a new dialog within my Bot, RelayBot, which is just a simple relay. I've modified the code as follows
if (activity != null)             {                 switch (activity.GetActivityType())                 {                     case ActivityTypes.Message:                         await Conversation.SendAsync(activity, () => new RelayBot());                         break;
I've republished the Bot to Azure and the test web client works exactly as expected, as does the DirectLine test client I have. However, the Skype bot is still running the original StartUpDialog. I've used remote debugging and it is jumping into the StartUpDialog from Skype, but going into RelayBot from Directline and web chat. I have no idea whats going on.
If I change the StartUpDialog, without changing the above code, that change is reflected when using Skype.
Any ideas would be appreciated.

Contacted @IanBoggs and he confirmed the issue got resolved within hours. However I was able to reproduce that and it looks like Azure Bot Service sometimes simply takes longer to deploy the changes.

Closing the loop on this--
There are a few operations within the Azure Bot Service that can cause code not to be updated, such as refactoring the code into a new folder. This doesn't completely explain why the code was working differently in two channels. However, we don't have a repro for this anymore.
If you see this issue or a similar problem, please open a new issue so it shows up on our radar. Thanks


Unable to share GAs in production. The share via link and email does not work.

Unable to share GAs in production. The share via link and email does not work.

Link share: https://www.legalnav.org/share/591546D

@KellyeDC Ready for review on Dev, Stage and Prod environments except unsharing and removing the link


Managed Identities for App Service to App Service communication

Is it possible to use managed identities to grant access to communication between two app services?
Similar to how we get access to key vaults.
E.g. todo service needs access to email service. Using arm templates or azure portal, todo service has been given access to the email service using it's managed identity. Todo service sends a token generated using the managed identity with it's requests to the email service which validates the token and grants access.

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

ID: f57d3177-ce9e-ebfa-03a7-45beb8ca3212
Version Independent ID: a59df23d-f3ac-9809-61d3-5741e31f020a
Content: Managed identities - Azure App Service
Content Source: articles/app-service/overview-managed-identity.md
Service: app-service
GitHub Login: @mattchenderson
Microsoft Alias: mahender

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

Hey @reginbald, currently app services doesn't support this type of workflow. If you want to restrict access to emailservice for only authenticated users; such as the todoservice, the way to do it currently is to use AAD app registrations through EasyAuth as outlined here.
I know it may not be the response you were looking for but I hope it helps.

Thanks for the quick reply @RyanHill-MSFT. Do you know if it will be supported in the future?

There is some exploratory work with managed identities being able to use RBAC but there isn't any notion of an ETA currently. I would advise submitting feedback showing interest in such a feature.

https://feedback.azure.com/forums/34192--general-feedback/suggestions/40422157-managed-identities-for-app-service-to-app-service


REQUEST: New membership for kinzhi

GitHub Username
@kinzhi
Organization you are requesting membership in
Karmada
Requirements

[x] I have reviewed the community membership guidelines
[x] I have read the Contributor Guide
[x]  I have enabled 2FA on my GitHub account
[x]  I have subscribed to the Karmada mailing list
[x]  I am actively contributing to 1 or more Karmada subprojects

Sponsor 1
@RainbowMango
Sponsor 2
@kerthcet
Sponsor 3
@kevin-wangzefeng
List of contributions to the Karmada project
PRs authored: https://github.com/karmada-io/karmada/pull/2145

Hi, Thank you for your interest in becoming a member of the Karmada community and for your contributions thus far. We appreciate your efforts and the time you have invested in our community.
However, it appears that there has been no recent activity from you since the application. In order to maintain an activity and engage membership, we need to ensure that members continue to participate and contribute to the community.
Given the lack of recent engagement, we will be closing the application for now. Please feel free to re-open at any time you wish to become more involved again. We would be delighted to welcome you back!
/close


Clubhouse API V2

I just wanted to let you know that we've released Clubhouse V2. While V1 will continue to be supported, V2 exposes endpoints for several new features such as Teams, Milestones, and Categories.

Thanks, @camilleacey ... to be honest, we haven't been using Clubhouse lately; it might be good to find this project a new maintainer.


Docs: Title issue with the Algolia SearchBox

Environment
Hi this issue appeared on the nuxt 3 documentation website. This is a very small issue.
Reproduction
Go on :
https://v3.nuxtjs.org/
And try to search something using the Algolia searchbox.
Describe the bug

Most of the titles are being duplicated (Advanced Advanced, Going Further Going Further).
Additional context
No response
Logs
No response

Can confirm this still happens, and they are leading to different urls, one with and one without trailing slash.

Transferring to (currently) private https://github.com/nuxt/nuxt.com repo to track there.


Incorrect reportGeneralType "unknown symbol import" errors when type checking is enabled

Environment data

Language Server version: 2010.10.0
OS and version: Ubuntu Xenial
Python version (& distribution if applicable, e.g. Anaconda): 3.5

Expected behaviour
from production import foo
from production import generated

Files production/foo.py and bazel-bin/production/generated.py exist.
If "python.analysis.extraPaths": [] then pylance should report "unknown symbol import" on generated.
If "python.analysis.extraPaths": [ "bazel-bin"] then pylance should not report an error.
Actual behaviour
If "python.analysis.extraPaths": [] then pylance reports "unknown symbol import" on generated
If "python.analysis.extraPaths": [ "bazel-bin"] then pylance reports "unknown symbol import" on foo
If "python.analysis.extraPaths": [ ".", "bazel-bin"] then pylance reports "unknown symbol import" on generated
If "python.analysis.extraPaths": [ "bazel-bin", "."] then pylance reports "unknown symbol import" on foo
Logs
Code Snippet / Additional information
I thought this was a PEP420 issue, but it when type checkings disabled the problem goes away. Maybe type checking doesn't implement PEP420 correctly.

Thanks for reporting the issue.
When typeCheckingMode is set to "off", many diagnostic rules are disabled. The error is still detected, but it's suppressed. That explains why the issue apparently goes away.
A couple of follow-up questions for you.
Am I correct in assuming that these are namespace packages — i.e. there is not an __init__.py file within the top-level production directory?
Also, your problem description talks about the symbol bar, but this isn't mentioned in the sample you provided. Can you explain where bar is defined and how it's imported or referenced?

Also, it looks like your extraPaths don't include the correct path to the bazel-bin directory. Try the following and see if it works.
"python.analysis.extraPaths": ["production/bazel-bin/"]
Note that you don't need to specify "." because that path is already assumed.

I made some typos in the original bug reports, this example is a namspace package.
Attached is a workspace that demonstrates the issue. It includes a log file which clearly shows the example case where having python.analysis.extraPaths set results in pylance not even looking for production/foo.py.
pylance-bug-471.zip

Thanks for providing the example. Very helpful. I was able to repro the bug and find a fix.
The issue is that pylance aggressively caches any package import resolutions. This is a big performance boost, so it's important to do. In general, it's safe to cache imported packages because the Python interpreter also does so. However, there's a catch. With namespace packages, the Python interpreter isn't able to cache the results. Pylance was still doing aggressive caching for namespace package resolutions. After the first successful import from "production", all subsequent attempts to import from "production" resolved to the same namespace package even if it couldn't provide the imported symbol. That explains the behavior you were seeing.
I've made the caching mechanism in Pylance smarter so it can detect this situation and deal with it appropriately. This fix will be in the next release.

This issue has been fixed in version 2020.10.1, which we've just released. You can find the changelog here: https://github.com/microsoft/pylance-release/blob/master/CHANGELOG.md#2020101-14-october-2020


Overlay ports tree doesn't work with distclean or options

I originally reported this on bugzilla (for distclean only, not options), not realizing that this repo might be more appropriate.
Prerequisites

[x] Have you checked for an existing issue describing your problem?
[x] Are you running the latest version?
[x] Is your ports tree recent?
[x] Is your FreeBSD Host on a supported release?

Describe the bug
I can build a port using an overlay:
poudriere bulk -vv -C -j 123amd64 -p default -O mine devel/ex_ample

But I can't distclean it. It appears that distclean doesn't account for overlays.
# poudriere distclean devel/ex_ample
[00:00:01] Loading MOVED for /usr/local/poudriere/ports/default
[00:00:02] Gathering all expected distfiles for ports tree 'default'
[00:00:02] Error: Nonexistent origin listed: devel/ex_ample
[00:00:02] Error: Fatal errors encountered gathering distfiles metadata

# poudriere distclean -p mine devel/ex_ample
[00:00:00] Gathering all expected distfiles for ports tree 'mine'
[00:00:00] Warning: (devel/ex_ample): make: "/usr/share/mk/bsd.port.mk" line 32: Cannot open /usr/local/poudriere/ports/mine/Mk/bsd.port.mk
[00:00:00] Gathering list of actual distfiles
[00:00:00] Error: Something went wrong. All distfiles would have been removed.

I also can't set options for my port:
# poudriere options devel/ex_ample
[00:00:00] Working on options directory /usr/local/etc/poudriere.d/options
[00:00:00] Error: Nonexistent origin listed: devel/ex_ample

# poudriere options -p mine devel/ex_ample
[00:00:00] Working on options directory /usr/local/etc/poudriere.d/mine-options
make: "/usr/share/mk/bsd.port.mk" line 32: Cannot open /usr/local/poudriere/ports/mine/Mk/bsd.port.mk
make: Fatal errors encountered -- cannot continue
make: stopped in /usr/local/poudriere/ports/mine/devel/ex_ample
make: "/usr/share/mk/bsd.port.mk" line 32: Cannot open /usr/local/poudriere/ports/mine/Mk/bsd.port.mk
make: Fatal errors encountered -- cannot continue
make: stopped in /usr/local/poudriere/ports/mine/devel/ex_ample

How to reproduce

Create a default ports tree.
Create an overlay ports tree with a single port.
Run distclean or options on the port from the overlay tree.

Expected behavior
distclean and options run successfully.
Environment

Host OS: 12.3 amd64
Jail OS: 12.3 amd64
Poudriere Version: <IP_ADDRESS>11130
Ports branch and revision: main / 563cab2f328c435da939267cc40c233147bce197

Additional context
There are a couple previous PRs that add overlay support to other commands:

#876
#790

Depends on #487 and #214


Include repository display names in sensor.hacs repositories attribute

Is your feature request related to a problem? Please describe.
The repositories attribute of the HACS sensor just contains the repository path rather than the display name (e.g. "keatontaylor/alexa_media_player" rather than "Alexa Media Player"). This makes it difficult to create a nicely formatted card in Lovelace with the details.
Describe the solution you'd like
Include both the repository name as well as the path in the repositories attribute (maybe keep name as it is now and have the name in a property like display_name).
Describe alternatives you've considered
Additional context
A screenshot of what I see when I use the sensor in my Home Feed card

With this extra property it could look more like this (mocked up):

Added in https://github.com/custom-components/hacs/releases/tag/0.14.0b0


Search demo is underwhelming, terms not found; due to apostrophe?

I tried https://olivernn.github.io/moonwalkers and was quite underwhelmed: e.g. I searched for NASA, and... it didn't highlight NASA's, nor did I find any way to get that to highlight.
This is even more striking when search for Casper which gives zero hits. Yet the entry for "Charles Duke"  says:

The latter feat was accomplished by Mattingly when he ventured out to "Casper's" SIM-bay for the retrieval [...]

Though the demo site showcases additional functionality that is not part of lunr.js (the search front-end), there could indeed be some lunr.Pipeline finetuning or front-end search string pre-processing.


Unable to connect to server

I set up itzg/minecraft-server for my fabric server and everything seemed to be working. But If I try to connect i get:
io.netty.channel.AbstractChannel$AnnotatedConnectException: syscall:getsockopt(..) failed: Connection refused:
But in the Server preview it looks normal

Can provide more info about the container setup?

I'm using compose:
survival:
  image: itzg/minecraft-server:latest

  ports:
    - "25599:25565"
    - "25589:25575"

  environment:
    FORCE_REDOWNLOAD: "TRUE"
    EULA: "TRUE"
    TYPE: FABRIC
    VERSION: "1.16.5"

    OVERRIDE_SERVER_PROPERTIES: "TRUE"

  volumes:
    - /home/paulj/dockermc/survival:/data

  tty: true
  stdin_open: true
  restart: always```

Linux manjaro 5.9.16-1-MANJARO #1 SMP PREEMPT Mon Dec 21 22:00:46 UTC 2020 x86_64 GNU/Linux
Docker version 20.10.3, build 48d30b5b32
docker-compose version 1.28.2, build unknown

What host/connection string are you using in the client? Since you're using a non-standard port then that will be important.

0:25599

Sorry for the incident it works fine with localhost:25599


autotrace: mark as insecure

Motivation for this change
This is both a PR but also a question about policy of when it' appropriate to mark a package as insecure as I wasn't able to find any documentation or guidance on this topic. Please feel free to close this if it's not in line with said policy.
The package in question doesn't appear to be maintained upstream (no release in well over a decade) and I wasn't able to locate any patches from other distributions. As a single data point Gentoo dropped support for the package. At this time I'm not aware of any working exploits related to the CVE's listed.
/cc maintainer @Hodapp87
Things done

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

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

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

Errors out by default as expected:
error: Package ‘autotrace-0.31.1’ in /home/sam/nixpkgs/master/pkgs/applications/graphics/autotrace/default.nix:65 is marked as insecure, refusing to evaluate.

Known issues:

 - CVE-2017-9200
...

With insecure enabled for the package, builds fine. I'm merging. Thanks for the update!

OK, thank you for the decision. The problem is that it opens the possibility for the build of this package to silently break in the future, while whether autotrace is considered vulnerable or not depends on its use.

Yes, the knownVulnerabilties will introduce silent breakage, but an unmaintained application with 52 related CVE's I think is a good reason to use that attribute. I also think we should just remove this completely after 18.03.

Why? It is not a network application. It may run arbitrary code from a specially crafted malformed file, but it is certainly safe to use on the images I draw myself or on the pictures that I take, and it is reasonably likely safe to use on images that were displayed without errors by a browser or another program.

Do you want me to revert and we can open it up for discussion with security team?

No, unless any other user complains; so far either decision about this issue seems acceptable. (Personally I use the vectorizer built into Inkscape.)


Shortcuts not working.. Project generator and VSC

hi, im quite new but the Shortcut CMD commands aren't working for me, due to the double ampersand && in both the project generator and VSC for pico. removing the double ampersand works though, unless it modifies the desired output
Project generator

C:\WINDOWS\system32\cmd.exe cmd /c call "C:\Users\_username_\Desktop\Pico\pico-env.cmd" &&python "C:\Users\_username_\Desktop\Pico\pico-project-generator\pico_project.py" --gui
Start in : C:\Users\_username_\Desktop\Pico\pico-project-generator

VSC for pico

C:\WINDOWS\system32\cmd.exe /c call "C:\Users\_username_\Desktop\Pico\pico-env.cmd" &&code
Start in : C:\Users\_username_\Desktop\Pico

I'm not sure how removing the double ampersand would work. It's just saying "run this command when the last one succeeds." Did you replace the double ampersands with single ampersands?

Closing because I haven't heard back from the issue author.


Use port from marathon locathion.

Add support to use port from marathon location in leader discovery logic so can support port other than 8080
Based on #264

Changes Unknown when pulling 7c61b0d8613332f87930d000f3370b865b6db8fb on fix_264 into ** on master**.

Changes Unknown when pulling 9a348d1b93a6a1eac05adc7bd9a7b35d84e2522f on fix_264 into ** on master**.


Revise PPE matching process

Overview
Discuss how PPE fields are handled and modify how they are copied from FacilityListItem to Facility if needed.

Superseded by #1050


arp-scan: 1.9.8 -> 1.10.0

Description of changes
Release Notes
make install now tries to set the setuid on the installed binary, which we don't allow in the Nix store. Developer suggests removing the relevant code in Makefile.am, which we do with a patch.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Thanks!


Error: Cannot find module 'internal/fs'

I am trying to install an authoring_tool and I am getting this error when I run 'node install' after following this tutorial https://github.com/adaptlearning/adapt_authoring/wiki/Developer's-Install

I don't understand what this has to do with windows-build-tools. Perhaps you should contact the author of that project<EMAIL_ADDRESS>


Roll Engine from d97a81c88983 to cdc44862e72f (11 revisions)

https://github.com/flutter/engine/compare/d97a81c88983...cdc44862e72f
2020-11-12<EMAIL_ADDRESS>Make CkPath resurrectable (flutter/engine#22446)
2020-11-12<EMAIL_ADDRESS>Upgrades to felt (running on multiple modes, multiple backends, single test target option) (flutter/engine#22260)
2020-11-12<EMAIL_ADDRESS>Roll Skia from 70eba23828a3 to 59bafeeaa7de (3 revisions) (flutter/engine#22458)
2020-11-12<EMAIL_ADDRESS>Make PlatformDispatcher.locale and locales return consistent values (flutter/engine#22267)
2020-11-11<EMAIL_ADDRESS>[web] Refactor _measureSubstring to better suit rich text measurement (flutter/engine#22443)
2020-11-11<EMAIL_ADDRESS>[web] Reuse the existing font string builer in TextStyle (flutter/engine#22444)
2020-11-11<EMAIL_ADDRESS>[web] Better data structure to prepare for rich text measurement (flutter/engine#22442)
2020-11-11<EMAIL_ADDRESS>Roll Skia from 869eb97f6c29 to 70eba23828a3 (20 revisions) (flutter/engine#22452)
2020-11-11<EMAIL_ADDRESS>fuchsia: Update buildroot (flutter/engine#22445)
2020-11-11<EMAIL_ADDRESS>Fix typo in documentation for FlPlatformPlugin (flutter/engine#22426)
2020-11-11<EMAIL_ADDRESS>Roll Dart SDK from 8749fdff07f5 to 40a4d9b44d72 (1 revision) (flutter/engine#22450)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

AutoRoller is stopped; closing the active roll.


Dev

add vectorized logo
change primary color to "black"
fix 404 page by adding canonical URL

after merge we should point from MiyooCFW.wiki to these "MiyooCFW docs" by changing all markdown files there.

after merge we should point from MiyooCFW.wiki to these "MiyooCFW docs" by changing all markdown files there.

Yea, i have some other stuff pending regarding structure and file-naming on this before linking on old wiki, i guess we could point all files to a single url, but i prefer to update one by one


Kafka ACLs

We can get list of all ACLs added for principal(users) on the given topic whether they have permission or not.
Say I have 2 users

User:Reader: this user is having read permission.
User:Writer: this user is having write permission.

From the above example can we come to a conclusion that User-Reader is a consumer and user-writer is a producer for topic "A"? Also, is getting information about ACLs users correct?
Thanks,
Surbhi

Hello,
Any help would be appreciated.

I'm not quite sure I understand the question. If a user has write permissions, they can produce to the topic (but might not have). If a user has read permissions, they can consume from the topic (but might not have).
Note that the .net client doesn't yet allow you to work with ACLs. To do that, you can either use REST Proxy
https://docs.confluent.io/platform/current/kafka-rest/api.html#acl or call out to the ./bin/kafka-acls.sh command.

Hi Matt,
My question was if a user has write permission, can we conclude he is a producer for a topic "A"? Similarly, if a user has read permission, can we conclude that user is consumer for a topic "A"?

no, just because a user has permission to do something, it doesn't mean they have done that thing.


Update governance.md

Noted that David Hassell is now officially the secretary of the Conventions Committee

Hi @davidhassell - I have a few more changes to the governance.md file. Since this PR hasn't made it onto the master branch yet, I thought I would add my changes here. However, it looks like other unrelated changes have made there way into this PR. So, I have pulled your governance.md changes and mine into a new branch and made a new PR (#70). Are you OK with closing this PR in favor of the new PR (#70)?
 I think this is one of the reasons standard practice is to always work on a branch, and only make changes to master with pulls from upstream (i.e., origin:master).
Also, its not obvious or intuitive but, once a PR is made, any changes pushed to the PR branch become part of the PR. A really handy feature that allows improvements to be made to a PR with a simple push. However, it does require that each PR branch only contain changes for that PR. (This is how all the changes not dealing with governance.md made there way into this PR.)

Hi @ethanrd, Thank you for explaining why this is the way it is (it sounds like working in master was my biggest error...). This is an excellent example of why we spell out the practical procedure needed to do this kind of thing!
The main purpose of this one was to introduce the new rules for the CF data model, but I'll redo another one for that, in a branch. I'm am totally fine with your #70, and I'll close this one once I have a new one that I can reference from the data model issue.

#71 has now been created for the CF data model rules, closing this issue as per precious comments


fix: ledger verification when swapping to manual receive address

Description

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #
Risk

Testing

Engineering

Operations

Screenshots (if applicable)

Current dependencies on/for this PR:

develop

PR #5634   👈

This stack of pull requests is managed by Graphite.


VTS L1 Enhancement - Code Cleanup - Device Setting - VideoDevice

This issue needs to be addressed

Clean up unnecessary code in L1
Zero warnings during compilation will cause the removal of unused functions, variables, and macros.
FATAL use in all tests must be removed except for init and term/close APIs.
Review the usage of casting:
Eg: from SupportedDFCs= ut_kvp_getUInt32Field(ut_kvp_profile_getInstance(), key_string);
to SupportedDFCs = (dsVideoZoom_t)ut_kvp_getUInt32Field(ut_kvp_profile_getInstance(), key_string);

2 Re-check if any new API interface has been added recently and requires an L1 test case. A separate issue shall be raised if there are any missing API L1 Test implementations.
Acceptance Criteria:
Zero Warnings
Let us know if any new test APIs need to be introduced based on the latest interface file.
Remove the use of FATAL macros all functions must fall through if any.

Changes are now available at #125

all changes are now available in tag 3.1.0


javacard-devkit: allow overriding the java binary

Motivation for this change
This is required for debugging.
Things done

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

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

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

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: javacard-devkit
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

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

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: javacard-devkit
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

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


Add support in REST handler for HTTP PATCH

Adding PATCH support would allow for a cleaner separation of duties between POST and PUT, allowing the user to update an existing resource using HTTP PATCH, create a new resource using POST, and add or replace a new resource at a specific location using PUT.

The spec talks about partial updates, as opposed to full updates from PUT. I'll let this open for a while to get people's idea on the best ways to implement this.

Yes, exactly.  Most people right now are using POST to do partial updates, but this would just make things cleaner IMO.

I'm with aberman, I think patch would be a welcome addition for doing partial updates to existing resources.

Well this is actually quite a nice idea.
Today we have:

POST when post_is_create returns false which is used to update an existing resource.
POST when post_is_create returns true which is used to create a resource whose identity is unknown by the client.
PUT to overwrite a possibly previously existing resource whose name we know. This is either create or update with the complete resource given in the request body.

But post_is_create is just a special case needed because PATCH doesn't exist (and I guess because browsers don't know anything other than GET and POST for normal requests).
So we could add PATCH to do the same as POST would when post_is_create returns false. Now this would mean that PATCH does the same as process_post, which would end up being quite an awkward name.
Ultimately I think we want to replace process_post with a patch_resource callback (possibly even having different handlers there like for PUT that vary depending on the request content), and have POST either send to the put_resource route or the patch_resource route depending on whether post_is_create returns true. We don't really need a post_is_create since semantically it should always create, but it is a convenience I suppose some people need.
What do you think?

I think post_is_create and process_post should stay the same for people that wish to support clients that do not support PATCH and to keep the REST API backwards compatible. They should not in any way be tied to PATCH.
That said, I think patch should work very much like PUT in that content types are handled differently by different callbacks and of course where the resource exists!
I would like to have function callbacks that look like...
update_from_json
update_from_qs
etc
That would be perfect!

Yeah I suppose for now process_post should stay but I'll mark it as deprecated so we can later move on to a better API (before Cowboy gets to 1.0 preferably). I get that backwards compatible is important but cleanliness is even more so and should be pushed onto people in a few simple steps at a time, while we can.

I agree with you, @essen.  The Webmachine API is not perfect and I'd much rather have a clean, very understandable API than something that just follows an older API for compatibility sake (especially since Cowboy hasn't hit the 1.0 version yet).  I've used Webmachine extensively and I always actually hated the post_is_create function.  The reason is because that function requires that you pass back an id for the new resource since its sole purpose is to just set the Location header.  In every case I've ever dealt with, I never have the id until I actually do the save itself so I just return some random term instead and modify the Location header manually in my process_post.  I've seen many other people do exactly the same thing and so there's clearly an issue with that function.
I like where you're going @essen, but POST on a new resource cannot simply call the PUT functions as it really does need to set the Location header.  Of course it can be set manually, but then you're looking at putting a case statement in the PUT function to test if it's a POST or something to that effect.  If we want to call the PUT functions, we would need to be able to return the new id at the end of the function.  Maybe if you see that an id is returned in the function then you mod the Location header, otherwise you don't?

Well yeah we do set the Location header when post_is_create returns true, after create_path is called. Then and only then it goes on to be like PUT. This is pretty much what Webmachine is doing really.
I feel that we need to write down how Cowboy does things currently (probably in a diagram) and then we can work out how to improve things.

That would be great!  Sorry, in my previous post, I meant that post_is_create forces you to return an id in create_path which is what I don't like.

Yeah I figured. You're right though, there are cases where you can know the ID before, and others where you need to process/save the request body before you do. We should take that into account.


Change items order of menu in tree view

In the context menu , the checkout item is below the Add+Commit item and some times the checkout item clicked and all changes lost.
Please move this item to the end of list.

That menu is sorted in alphabetical order for ease of navigation. I'll add a confirmation dialog so users have a chance to cancel if it was accidental

Are you sure?? It don't show any confirmation dialog at all. I tested it but but just show me a success message!

I haven't released the changes yet

I will reinstall the package and will sent you the feedback.

I reinstalled the package but checkout command not show me any dialog again!

I still haven't released the changes

I just pushed a new release with the fixes

Excellent! Now it is working!


GET /cdns/routing

Implement feature parity with the same Traffic Ops Mojolicious endpoint

Note: This route is probably getting deprecated so you might not want to move it to Golang

sounds like this might actually be implemented in golang. please consult @elsloo

Hopefully this fixes #902 at the same time. Just adding for reference.

this endpoint is addressed in #2232


add image info

Describe what this PR does / why we need it
Add  a valid image list
Does this pull request fix one issue?

Describe how you did it
Describe how to verify it
Special notes for reviews

Codecov Report
Base: 21.12% // Head: 21.12% // No change to project coverage :thumbsup:

Coverage data is based on head (435ec9e) compared to base (145eb4c).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1862   +/-   ##
=======================================
  Coverage   21.12%   21.12%
=======================================
  Files          74       74
  Lines        6760     6760
=======================================
  Hits         1428     1428
  Misses       5146     5146
  Partials      186      186

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


libkeyfinder: 2.2.4 -> 2.2.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/libkeyfinder/versions.
meta.description for libkeyfinder is: "Musical key detection for digital audio (C++ library)"
meta.homepage for libkeyfinder is: "https://mixxxdj.github.io/libkeyfinder/"
meta.changelog for libkeyfinder is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 2.2.5 with grep in /nix/store/603r3f17w447msrr52wcsbr2wjaxxqfz-libkeyfinder-2.2.5

found 2.2.5 in filename of file in /nix/store/603r3f17w447msrr52wcsbr2wjaxxqfz-libkeyfinder-2.2.5

directory tree listing: https://gist.github.com/880c0383eeea77f5ec6def55df78e799

du listing: https://gist.github.com/0c4e5928c6c610386dfc277d19e218b8

Rebuild report (if merged into master) (click to expand)

108 total rebuild path(s)

35 package rebuild(s)

35 x86_64-linux rebuild(s)
33 i686-linux rebuild(s)
7 x86_64-darwin rebuild(s)
33 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
adapta-gtk-theme
arc-theme
beets
beetsExternalPlugins.alternatives
beetsExternalPlugins.copyartifacts
beetsExternalPlugins.extrafiles
chrome-gnome-shell
equilux-theme
gh
github-cli
gnome.gnome-session
gnome.gnome-shell
gnome.gnome-terminal
gnome.gnome-tweak-tool
gnome.gnome-tweaks
gnome.gnome_session
gnome.gnome_shell
gnome.gnome_terminal
gnome.pomodoro
gnomeExtensions.easyScreenCast
gnomeExtensions.gsconnect
gnomeExtensions.night-theme-switcher
keyfinder
keyfinder-cli
kmon
libkeyfinder
lounge-gtk-theme
materia-theme
mixxx
nixos-install-tools
pantheon.elementary-session-settings
phosh
terracognita
tests.nixos-functions.nixos-test
tfsec

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/603r3f17w447msrr52wcsbr2wjaxxqfz-libkeyfinder-2.2.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libkeyfinder https://github.com/r-ryantm/nixpkgs/archive/d374ba7445a3857bcd6b3b2b9af311127a086345.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/603r3f17w447msrr52wcsbr2wjaxxqfz-libkeyfinder-2.2.5
ls -la /nix/store/603r3f17w447msrr52wcsbr2wjaxxqfz-libkeyfinder-2.2.5/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

7 packages built:

beets
beetsExternalPlugins.alternatives
beetsExternalPlugins.copyartifacts
beetsExternalPlugins.extrafiles
keyfinder-cli
libkeyfinder
mixxx

Maintainer pings

Result of nixpkgs-review pr 130908 at d374ba74 run on aarch64-linux 1

1 package marked as broken and skipped:

keyfinder

7 packages built successfully:

beets
beetsExternalPlugins.alternatives
beetsExternalPlugins.copyartifacts
beetsExternalPlugins.extrafiles
keyfinder-cli
libkeyfinder
mixxx


Istio sidecar crashed after applying gRPC ALS envoyfilter

I'm applying the following envoyfilter for grpc access logs on a cluster (als.default.svc.cluster.local:9001) which is running as a deployment and service in default namespace;
apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
  name: access-log-listener
spec:
  workloadSelector:
    labels:
      app: productpage
  configPatches:
  - applyTo: CLUSTER
    patch:
      operation: ADD
      value: # cluster specification
        name: als_cluster
        connect_timeout: 5s
        type: STRICT_DNS
        http2_protocol_options: {}
        # Comment out the following line to test on v6 networks
        dns_lookup_family: V4_ONLY
        lb_policy: ROUND_ROBIN
        load_assignment:
          cluster_name: als_cluster
          endpoints:
          - lb_endpoints:
            - endpoint:
                address:
                  socket_address:
                    address: "als.default.svc.cluster.local"
                    port_value: 9001
  - applyTo: NETWORK_FILTER # http connection manager is a filter in Envoy
    match:
      # context omitted so that this applies to both sidecars and gateways
      listener:
        filterChain:
          filter:
            name: "envoy.filters.network.http_connection_manager"
    patch:
      operation: MERGE
      value:
        name: "envoy.filters.network.http_connection_manager"
        typed_config:
          "@type": "type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager"
          access_log:
          - name: envoy.access_loggers.http_grpc
            typed_config:
              "@type": "type.googleapis.com/envoy.extensions.access_loggers.grpc.v3.HttpGrpcAccessLogConfig"
              common_config:
                grpc_service:
                  envoy_grpc:
                    cluster_name: als_cluster
                log_name: accesslog

But my sidecar crashed with some errortrace;
2020-11-15T05:03:26.502540Z	critical	envoy backtrace	Caught Segmentation fault, suspect faulting address 0x0
2020-11-15T05:03:26.502699Z	critical	envoy backtrace	Backtrace (use tools/stack_decode.py to get line numbers):
2020-11-15T05:03:26.502711Z	critical	envoy backtrace	Envoy version: 745f989e4024e8e839de05f3c01b516fad69c278/1.15.0/Clean/RELEASE/BoringSSL
2020-11-15T05:03:26.531565Z	info	sds	resource:ROOTCA connection is terminated: rpc error: code = Canceled desc = context canceled
2020-11-15T05:03:26.531730Z	error	sds	Remote side closed connection
2020-11-15T05:03:26.536054Z	info	sds	resource:default connection is terminated: rpc error: code = Canceled desc = context canceled
2020-11-15T05:03:26.536115Z	error	sds	Remote side closed connection
2020-11-15T05:03:26.543957Z	error	Epoch 0 exited with error: signal: segmentation fault
2020-11-15T05:03:26.544828Z	info	No more active epochs, terminating

I am pretty sure this is not legal, the cluster must be static. I am not sure if its intended it crashes rather than rejects the config, please open an issue in envoyproxy/envoy for this as this is not an Istio bug. thanks!

+1
  meshConfig:     defaultConfig:       envoyAccessLogService:         address: skywalking-oap.istio-system.svc:11800
Proxy crashes during performance testing
ISTIO Version: 1.6.14


Example not working & outdated

You should probably update the example or remove it cause it is not working anymore with the current version.

Fix with d07fc27b99dcb41633ff614f60fba7d3a2034083


⚠ Fortnite has degraded performance

In cdd09ea, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1409 ms

Resolved: Fortnite performance has improved in 3d65b01.


next in a row

Added support to add multiple next

@tony-go fail because https://github.com/tinylibs/tinyspy/pull/39

It will be better, but right now I don't even see an example of using nextResult/nextError
I think it is necessary to open an issue for documentation

It will be better, but right now I don't even see an example of using nextResult/nextError
I think it is necessary to open an issue for documentation

Then it is fine 👍🏻

Are there any blocks for the merge?

@sheremet-va


Project Governance and Working Group

BR&SRI Center Project Governance
Humanoid Robotics Working Group

@RonaldsonBellande Currently, the way to get on the TSC, and to make an "official" working group, is to submit an application to the TSC.  If you'd like to do that, please follow the instructions at the bottom of the table in http://docs.ros.org/en/rolling/The-ROS2-Project/Governance.html#technical-steering-committee-tsc .
The good news is that you don't need to be an "official" working group to get things done.  Feel free to setup your meeting and meet with like-minded people.
With that said, I'm going to close this one out.


Support HDFS in docker (and other complex distributed systems)

Creating an HDFS instance on a single process container should be trivial and supported now.
A more interesting use case would be to support more complex PaaS use cases such as spinning up a cluster of HDFS nodes that are configured and operate with each other in isolation of other HDFS clusters. (process container containers, or process container clusters).
Pushing this a step further, we should be able to orchestrate multiple docker hypervisors (for lack of a better word) across multiple systems to support a single cluster. Basically a distributed cluster of process containers that share run-time configuration to interoperate in a non-trivial way.
Once we have docker provisioning HDFS in complex scenarios, we should be able to generalize the techniques to help bootstrap other complex systems, including HDFS, mesos, spark, sql clusters, memcache, etc... with minimal changes to configurations.
I'm hoping to use this thread more like an epic instead of an issue to centralize discussion on these topics. We can spin off more specific issues to add functionality.

I am interesting on this topic @shykes


Add some indicator of renderer version outside of Meta panel

It might be nice to have some visual cue as to the renderer version that is more apparent than the checkbox in the metadata panel.  I was thinking that maybe the "text editor" menu in the snippet menu could read "V3 Text Editor" or "Legacy Text Editor"?
Or just "V3" or "Legacy" written anywhere on the screen.
This idea came up when trying to troubleshoot another users brew from a posted screenshot, and just wondering which editor they were using.  Based on the fact they had some html tags, I'm assuming it's Legacy, but that may not necessarily be the case.  If the screenshot doesn't happen to include wherever this renderer indicator is located, then i'll be out of luck anyway, but it would have a higher chance of being included than the metadata panel.
I also think it would just be more clear to users as they work.

My first thought is that we could modify the BrewRenderer.jsx to add a
${this.props.renderer}
, and then add the class to BrewRender.less to give it position:fixed so it floats above the rendered brew. We could also add the class visibility:hidden to @media print or some other form of hiding on print detection so that it does not appear on the PrintPage.

I created a branch for this, just adding the renderer down by the page counter.

It shows on the Share page, too, which I'm not sure is desirable.
Another option is show it in the snippet bar above the editor:

Finally, if either is approved, is it a good idea to make it a toggle button between legacy and v3?

and just wondering which editor they were using

sometimes you can spot this from the content:
in V3, single apostrophes are rendered as curly, in Legacy they remain raw straight.

Yeah, and sometimes it's just clear from how it 'feels'.  And going forward, since it is now the default renderer, my presumption is going to be mostly v3.  But it's still nice to have an indicator on the screen because we still get reports with "i dunno" in the "Renderer?" field.
Also, I think the HB version can be confusing:

Bottom right corner looks fine to me. :+1:

Do you think it should be a bit grayed out, to indicate it can't be changed by clicking there?
Or alternatively, should it be possible to change renderer down in the pageInfo?

I lean towards not having it changeable from there. We can treat it as just an info panel. I don't think it needs to be grayed out either.

Okay, will submit the PR in a few minutes.


Application doesn't stop when headphones get unplugged

I have a habit of unplugging headphones instead of pausing music apps properly, so I noticed that the app doesn't pause when you unplug the headphones. You can't close the notification control panel if that happens. What's worse,  it used 259MB of data today, while I listened for something like 30 minutes. That's about 6 times more than a 192kbps cbr audio stream would take. All that data and resources on both sides wasted for something I wasn't using.

I just listened to it today while walking to work. Unplugged the headphones, checked the notification center and it was paused.
Afterwards I just closed the app as usual via the overview.

Just tried it, the app pauses just fine. Check you're on the latest version and try opening the app with your headphones plugged in > pressing play > unplugging headphones and let us know if it works as intended.

Also maybe mention android version, app version (if possible) and phone 🤔

Also check if the setting is enabled (assuming you're on the latest version).

I can't replicate the bug now. I guess that was one off instance of this happening. Probably my phone's fault, actually.
App version: 1.4.0
Android Version: 6.0
Phone: HTC U Play
Software number: 1.30.401.4


Vite failed to resolve entry for package problem

Problem:
Package imported smoothly on nextjs side gets import error on nuxt or vite side.
Code:
import { createClient } from "@postiva/client";

export const postivaClient = createClient({
  apiKey: process.env.VITE_POSTIVA_API_KEY as string,
  workspaceId: process.env.VITE_POSTIVA_WORKSPACE_ID as string,
});

Problem:

fixed


question: usb-c to hdmi support?

Does this windows thing supports usb-c hdmi out for devices that has the hardware support (that worked with android)

It should

nope, it requires per-device ACPI fix

ok. thank u


New version: CUDAdrv v6.2.2

Registering package: CUDAdrv
Repository: https://github.com/JuliaGPU/CUDAdrv.jl
Created by: @maleadt
Version: v6.2.2
Commit: a002293c65caa642920e5b9c31bd622b9df5818b
Reviewed by: @maleadt
Reference: https://github.com/JuliaGPU/CUDAdrv.jl/commit/a002293c65caa642920e5b9c31bd622b9df5818b#commitcomment-38054044

cc @ararslan [noblock]


Improved documentation

Coverage remained the same at 99.518% when pulling 4a4cc52adf50d264b214ec295f3725218e59014d on JorgeMartinezG:master into 281cfb1f277d42c341040a5986d2a490c15a0391 on boundlessgeo:master.

Thanks @JorgeMartinezG


Protocol error (Target.setDiscoverTargets): Target closed when puppeteer.launch fails with pipe: true

Similar to #4374, it appears that puppeteer.launch fails with a different error messaging depending on the pipe option. The error messaging for pipe: true is confusing.
Steps to reproduce

Happy Path - Attempt Launch Puppeteer `pipe: false` in Docker, missing runtime dependencies:

$ docker run --rm -it node:erbium-slim sh -c 'yarn add puppeteer; node -e "const puppeteer = require(\"puppeteer\"); puppeteer.launch({pipe: false})"'
yarn add v1.22.4
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
success Saved 51 new dependencies.
info Direct dependencies
└─<EMAIL_ADDRESS>info All dependencies
├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>└─<EMAIL_ADDRESS>Done in 90.98s.
(node:40) UnhandledPromiseRejectionWarning: Error: Failed to launch the browser process!
/node_modules/puppeteer/.local-chromium/linux-782078/chrome-linux/chrome: error while loading shared libraries: libgobject-2.0.so.0: cannot open shared object file: No such file or directory

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

    at onClose (/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:193:20)
    at Interface.<anonymous> (/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:183:68)
    at Interface.emit (events.js:327:22)
    at Interface.close (readline.js:416:8)
    at Socket.onend (readline.js:194:10)
    at Socket.emit (events.js:327:22)
    at endReadableNT (_stream_readable.js:1221:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:21)
(node:40) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:40) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Sad Path - Same as above, except with `pipe: true`
docker run --rm -it node:erbium-slim sh -c 'yarn add puppeteer; node -e "const puppeteer = require(\"puppeteer\"); puppeteer.launch({pipe: true})"'
yarn add v1.22.4
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
success Saved 51 new dependencies.
info Direct dependencies
└─<EMAIL_ADDRESS>info All dependencies
├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>└─<EMAIL_ADDRESS>Done in 40.60s.
(node:41) UnhandledPromiseRejectionWarning: Error: Protocol error (Target.setDiscoverTargets): Target closed.
    at /node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:71:63
    at new Promise (<anonymous>)
    at Connection.send (/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:70:16)
    at Function.create (/node_modules/puppeteer/lib/cjs/puppeteer/common/Browser.js:95:26)
    at ChromeLauncher.launch (/node_modules/puppeteer/lib/cjs/puppeteer/node/Launcher.js:106:56)
(node:41) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:41) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Tell us about your environment:

Puppeteer version: 5.2.1
Platform / OS version: Docker node:erbium-slim
URLs (if applicable):
Node.js version: v12.18.2

What steps will reproduce the problem?
Please see above.

Launch puppeteer in Docker environment with pipe: true and a missing OS runtime dependency

What is the expected result?
I was expecting to see a clean stacktrace including this debug message:
Error: Failed to launch the browser process!
/node_modules/puppeteer/.local-chromium/linux-782078/chrome-linux/chrome: error while loading shared libraries: libgobject-2.0.so.0: cannot open shared object file: No such file or directory

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

What happens instead?
Instead, I received a confusing stacktrace referencing the protocol, which I am not intended to interact with directly:
Error: Protocol error (Target.setDiscoverTargets): Target closed.
    at /node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:71:63
    at new Promise (<anonymous>)
    at Connection.send (/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:70:16)
    at Function.create (/node_modules/puppeteer/lib/cjs/puppeteer/common/Browser.js:95:26)
    at ChromeLauncher.launch (/node_modules/puppeteer/lib/cjs/puppeteer/node/Launcher.js:106:56)

I'm getting the same error, except with --disable-dev-shm-usage arg instead of pipe: true

Any update on this ??

Having this exact problem

+1

I have the same issue but on AWS Lambda (runtime: provided.al2) with Serverless.
I'm using:

puppeteer ~5.5.0
chrome-aws-lambda ~5.5.0
chrome args --disable-dev-profile --user-data-dir=/dev/null (+ all args defined here https://github.com/alixaxel/chrome-aws-lambda/blob/1395ee60ad1625d08306a4aad8b7b851b73a9a83/source/index.js#L84-L122)
pipe: true

I have the same issue but on AWS Lambda (runtime: provided.al2) with Serverless.
I'm using:

puppeteer ~5.5.0
chrome-aws-lambda ~5.5.0
chrome args --disable-dev-profile --user-data-dir=/dev/null (+ all args defined here https://github.com/alixaxel/chrome-aws-lambda/blob/1395ee60ad1625d08306a4aad8b7b851b73a9a83/source/index.js#L84-L122)
pipe: true

Any idea how to run it on docker (locally)? I get same error when I'm trying to run puppeteer. I have pipe: true.

Any idea how to run it on docker (locally)? I get same error when I'm trying to run puppeteer. I have pipe: true.

I have the same issue with the following arguments:
  const browser = await puppeteer.launch({
    headless: true,
    args: [
      '--no-sandbox',
    ]
  });

The strange thing is that I only have the issue when running inside a docker container on Apple Silicon. Any ideas?

I have the same issue with the following arguments:
  const browser = await puppeteer.launch({
    headless: true,
    args: [
      '--no-sandbox',
    ]
  });

The strange thing is that I only have the issue when running inside a docker container on Apple Silicon. Any ideas?

I have the same issue with the following arguments:
  const browser = await puppeteer.launch({
    headless: true,
    args: [
      '--no-sandbox',
    ]
  });

The strange thing is that I only have the issue when running inside a docker container on Apple Silicon. Any ideas?

same here apple silicon and not always

+1
Same error with Docker
Error: Failed to launch the browser process!
/node_modules/puppeteer/.local-chromium/linux-856583/chrome-linux/chrome: error while loading shared libraries: libgobject-2.0.so.0: cannot open shared object file: No such file or directory

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

to fix this issue you need to set additional arg and delete pipe:true property:
const browser = await puppeteer.launch({
  headless: true,
  // pipe: true, <-- delete this property
  args: [
    '--no-sandbox',
    '--disable-dev-shm-usage', // <-- add this one
    ],
});

so it works for me with this setup

+1  still having issue.

+1 having the same problem

I had the same issue. I fixed it by using the following to launch.
 const browser = await puppeteer.launch({     headless: true,     args: [       '--no-sandbox',       '--disable-setuid-sandbox',       '--disable-dev-shm-usage',       '--single-process'     ]   });

I have the same issue here. It is working in my Ubuntu local machine but it fails on both remote dedicated server and local raspberry pi 3+. The local pi board expected to work, but it also failed which is odd!!
I've tried all the suggested solution here, did not work :(
Any ideas?

I had the same issue. I fixed it by using the following to launch.
 const browser = await puppeteer.launch({
    headless: true,
    args: [
      '--no-sandbox',
      '--disable-setuid-sandbox',
      '--disable-dev-shm-usage',
      '--single-process'
    ]
  });

This worked perfectly in my Lambda Docker instance too.  Thanks for the suggestion.

I had to install some more (more than explicitly required) libraries, and worked afterwards.
This list -maybe more than required- but worked https://gist.github.com/winuxue/cfef08e2f5fe9dfc16a1d67a4ad38a01#gistcomment-3832668

@manadan999 wdyt about adding this option --no-zygote ?
--no-zygote: Disables the use of a zygote process for forking child processes. Instead, child processes will be forked and exec'd directly. Note that --no-sandbox should also be used together with this flag because the sandbox needs the zygote to work.
[source]

I had the same issue on debian os. I solved it installing chrome:
sudo apt install libnss3 libatk1.0-0 libatk-bridge2.0-0 libcups2 libgbm1 libasound2 libpangocairo-1.0-0 libxss1 libgtk-3-0
https://gist.github.com/tavinus/7effd4b3dac87cb4366e3767679a192f

+1 having the same problem.

I had this problem and solved it late 2023 on Amazon Linux 2 for Lambda, using tips from this issue and other sources.
See my Dockerfile for all the dependencies that work on AWS Lambda's provided.al2 base layer.

'--no-sandbox',
'--disable-setuid-sandbox',
'--disable-dev-shm-usage',
'--single-process'

Love you for this solution

it worked for me
this.browser = await puppeteer.launch({
  headless: true,
  args: ['--no-sandbox', '--disable-gpu', '--disable-dev-shm-usage'],
});


Dancing Page added

I have added the dancing page. Here is snapshot of it!:

On which issue did you worked? Please share the issue link


Can we retain untouched ttf hints?

Would it be possible to export to TTF retaining existing TTF hints, overwriting only the glyph hints that have been touched by ygt?  I'm thinking of a workflow that allows me to use ttfauothint and only manually hint the glyphs that need improvement.

Funny you should mention that. Xgridfit (the backend for Ygt) has a thing called "merge mode," which adds hints to a font that already has them, appending new instructions after the ones already in the font, new control program code after the existing code, and new CVs after the existing ones. It's meant for exactly the situation where ttfautohint does a good job in general, but you want to replace certain glyph programs that aren't cutting it. Sooner or later I'll implement "merge mode" from within Ygt, but even now you can use it. Just hint the glyphs you want to hint and save in a YAML file (or copy the file data/org.ygthinting/source out of your UFO). Run Xgridfit against the YAML file like this:
xgridfit -y myfile.yaml myfile.xgf

Xgridfit will produce a file myfile.xgf in its own native language. Then run the file myfile.xgf against the autohinted .ttf font in merge mode:
xgridfit -m myfile.xgf

Xgridfit will produce a .ttf font with your hints layered on top of the ones that ttfautohint added to the font.
I should mention that Ygt can't edit glyph programs added by ttfautohint: their ways of doing things are just too different. Ygt can only replace glyph programs.
I'll make this much easier when I can. In the meantime, the procedure I've outlined should work.

Thank you.


[IMPROVEMENT] rename Delete to Delete Snapshot in the Snapshot and Backup section

In the latest version, under Snapshot and Backup visualized chain section, user can see the delete option from the action menu when click on the snapshot circle on the timeline.
However, when the snapshot becomes green, it indicates it had backup. The action menu still says Delete, which might confuse and imply that the user can delete the backup from the Volume UI. But the backup items are solely managed under the backup page.

To avoid confusion, and with the minimum change, we can rename the action option to Delete Snapshot. And further enhancement can have a tooltip to display that "the backup will not be deleted and the selected snapshot will be removed".
Related issues and discussion:

https://github.com/longhorn/longhorn/issues/1311
https://github.com/longhorn/longhorn/issues/2231
https://github.com/longhorn/longhorn/issues/2997
https://github.com/longhorn/longhorn/issues/3033
https://github.com/longhorn/longhorn/issues/3349

A quick UI mockup example to explain the idea to have a bit more context in the action menu:


AccessViolation in ASIO module

When opening an ASIO control panel twice, the second time it produces an access violation exception. It cannot be caught by Visual Studio, so I had to use windbg to get this information.
ModLoad: 00000001`80000000 00000001`80077000   C:\Program Files\M-Audio\Fast Track Pro\DeviceInterface.dll
ModLoad: 00000000`53860000 00000000`53929000   C:\WINDOWS\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9680_none_88e394a52fab6222\MSVCR80.dll
ModLoad: 00000000`52860000 00000000`52969000   C:\WINDOWS\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9680_none_88e394a52fab6222\MSVCP80.dll
ModLoad: 00000000`526c0000 00000000`5285b000   C:\WINDOWS\WinSxS\Fusion\amd64_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_none_758c8a477f89a995\8.0\8.0.50727.6195\MFC80U.DLL
ModLoad: 0000022b`bf870000 0000022b`bf87d000   C:\WINDOWS\WinSxS\Fusion\amd64_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_none_eeb8165fbcb9c171\8.0\8.0.50727.6195\MFC80ENU.DLL
ModLoad: 0000022b`bf870000 0000022b`bf87d000   C:\WINDOWS\WinSxS\Fusion\amd64_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_none_eeb8165fbcb9c171\8.0\8.0.50727.6195\MFC80ENU.DLL
(81a4.139c): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
MMDevAPI!CDeviceEnumerator::OnPropertyValueChanged+0x1d3:
00007ffa`d99e35e3 488b4038        mov     rax,qword ptr [rax+38h] ds:00000000`00000038=????????????????

Call stack:
[0x0]   MMDevAPI!CDeviceEnumerator::OnPropertyValueChanged + 0x1d3
[0x1]   MMDevAPI!CLocalEndpointEnumerator::OnMediaNotification + 0x118
[0x2]   MMDevAPI!CMediaNotifications::OnMediaNotificationWorkerHandler + 0x24e
[0x3]   ntdll!TppSimplepExecuteCallback + 0xa3
[0x4]   ntdll!TppWorkerThread + 0x8f6
[0x5]   KERNEL32!BaseThreadInitThunk + 0x1d
[0x6]   ntdll!RtlUserThreadStart + 0x28

Device: M-Audio Fast Track Pro with driver version 6.1.11 on Windows 11.
NAudio version: 2.1.0

that looks like code in the WASAPI APIs rather than anything to do with ASIO. Are you using any other parts of NAudio?

I query all possible sources, including WASAPI. But I didn't use WASAPI for playback.


Cleans up setup.py and migrates to pyproject.toml

Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.

[x] Make sure you are requesting to pull a topic/feature/bugfix branch (right side). Don't request your main!
[x] Make sure you are making a pull request against the main branch (left side). Also you should start your branch off our main.
[x] Check your code additions will fail neither code linting checks nor unit test.

Description
While looking at adding the license info, I added a lot more information and migrated to pyproject.toml for a more modern approach.

I'll try it out and merge if it worked correctly.

Good call, it did not. Just tested and verified I fixed it.


Adopt native TOML tox support

Is Your Feature Request Related to a Problem? Please Describe
Following https://github.com/tox-dev/tox/issues/3353 https://github.com/ymyzk/tox-gh-actions/discussions/197, it will at some be possible to have full native TOML support. I tried this for now and couldn't get it to work, so we might need to wait a bit. This would involve removing the lecacy INI format.
Describe the Solution You'd Like
No response
Describe Alternatives You've Considered
No response
Additional Context
No response

https://tox.wiki/en/4.21.0/config.html#pyproject-toml-native You should be able to do it all, in case you're running into problems, please feel free to tag me.

https://github.com/tox-dev/tox-gh?tab=readme-ov-file#examples

@gaborbernat got this working in #460 😄


ADIN2111 OA mode fixes

Fix the issue that eth_adin2111_oa_data_read returning error would cause the offload thread to exit and hence RTOS crash, as the offload thread is an essential one. It looks like this was a result of invalid merge or copy paste, the break statements in lines 705 and 711 were meant for internal loop that keeps reading the RX FIFO until is empty. Added the missing loop. Also refactored the code so it is common with OA and non-OA access and the FIFOs are read sequentially port 1 / port 2.
Fix the issue in eth_adin2111_send_oa_frame with improper EBO calculation. Sending more than 1472 byte packet would cause the frame to exceed maximum Ethernet frame size and cause the packet to be dropped. Without this fix the TCP communication did not work unless TCP send window was lowered with CONFIG_NET_TCP_MAX_SEND_WINDOW_SIZE, but that caused poor TCP performance.

Needs rebase

@panekmaciej will you be able to come back to this to address the merge conflicts?

@panekmaciej will you be able to come back to this to address the merge conflicts?

Yes, but after the new year.


Tweak animation editor icon colors for easier visual grepping

This makes the Linear and Cubic icons in particular easier to distinguish from each other.
The Cubic interpolation icon's curve was also changed to be more distinguishable from the Linear icon's curve.
This PR can be remade for 3.x once we agree on the changes here.
Preview
Dark theme

Before
After

Light theme
Some icon color conversions are not working correctly – I don't know why.

Before
After

I think that merging the new colours as is an improvement. The categories versus types of a category can be debated but not blocking. @TokageItLab Thoughts?

@fire In any case, it's better than the current state. It is mergeable.

Thanks!