vulns not working with private registry (protected by basic auth)

Hi, I've setup a private registry with basic auth and successfully managed to list my repositories:
$ reg -d -r registry.example.com list
2017/06/14 12:16:18 registry.ping url=https://registry.example.com/v2/
2017/06/14 12:16:18 registry.catalog url=https://registry.example.com/v2/_catalog
Repositories for registry.example.com
2017/06/14 12:16:18 registry.tags url=...
REPO                               TAGS
organisation/imagename1            latest, 0.1.24
organisation/imagename2            latest

Reg is perfectly using my .docker/config.json to pass Basic Auth header and retrieve my repos.
Then, I installed a coreos clair vulnerability analysis container on localhost:
$ curl http://localhost:6060/v1/namespaces
{"Namespaces":[{"Name":"debian:8","VersionFormat":"dpkg"},...]}

When I try:
$ reg -d -r registry.example.com vulns --clair http://localhost:6060 organisation/imagename1

I get:
2017/06/14 12:15:50 registry.ping url=https://registry.example.com/v2/
2017/06/14 12:15:50 registry.manifests uri=https://registry.example.com/v2/organisation/imagename1/manifests/latest repository=organisation/imagename1 ref=latest
2017/06/14 12:15:50 registry.token url=https://registry.example.com/v2/organisation/imagename1/blobs/sha256:b7...cf
FATA[0000] malformed auth challenge header: 'Basic realm="Registry Realm"'

Does vulns support Basic Auth with a private registry?

No only token. Clair takes a token
On Jun 14, 2017 14:31, "François Maturel"<EMAIL_ADDRESS>wrote:

Hi, I've setup a private registry with basic auth and successfully
managed to list my repositories:
$ reg -d -r registry.example.com list
2017/06/14 12:16:18 registry.ping url=https://registry.example.com/v2/
2017/06/14 https://registry.example.com/v2/2017/06/14 12:16:18 registry.catalog url=https://registry.example.com/v2/_catalog
Repositories for registry.example.com
2017/06/14 12:16:18 registry.tags url=...
REPO                               TAGS
organisation/imagename1            latest, 0.1.24
organisation/imagename2            latest
Reg is perfectly using my .docker/config.json to pass Basic Auth header
and retrieve my repos.
Then, I installed a coreos clair vulnerability analysis container on
localhost:
$ curl http://localhost:6060/v1/namespaces
{"Namespaces":[{"Name":"debian:8","VersionFormat":"dpkg"},...]}
When I try:
$ reg -d -r registry.example.com vulns --clair http://localhost:6060 organisation/imagename1
I get:
2017/06/14 12:15:50 registry.ping url=https://registry.example.com/v2/
2017/06/14 https://registry.example.com/v2/2017/06/14 12:15:50 registry.manifests uri=https://registry.example.com/v2/organisation/imagename1/manifests/latest repository=organisation/imagename1 ref=latest
2017/06/14 12:15:50 registry.token url=https://registry.example.com/v2/organisation/imagename1/blobs/sha256:b7...cf
FATA[0000 https://registry.example.com/v2/organisation/imagename1/blobs/sha256:b7...cfFATA[0000] malformed auth challenge header: 'Basic realm="Registry Realm"'
Does vulns support Basic Auth with a private registry?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jessfraz/reg/issues/27, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABYNbPW_ujsqJf7MSDMY4i8reM5rguo_ks5sD9KXgaJpZM4N5z-h
.

My clair is not secured, my docker registry container is.
And if i tweak some code like in vulns.go
// NewClairLayer will form a layer struct required for a clar scan
func (c *Clair) NewClairLayer(r *registry.Registry, image string, fsLayers []schema1.FSLayer, index int) (*Layer, error) {
    var parentName string
    if index < len(fsLayers)-1 {
        parentName = fsLayers[index+1].BlobSum.String()
    }

    // form the path
    p := strings.Join([]string{r.URL, "v2", image, "blobs", fsLayers[index].BlobSum.String()}, "/")

    return &Layer{
        Name:       fsLayers[index].BlobSum.String(),
        Path:       p,
        ParentName: parentName,
        Format:     "Docker",
        Headers:    map[string]string{
            "Authorization": fmt.Sprintf("Basic %s", "XXX"), // <- FORCED BASIC AUTHENTICATION
        },
    }, nil
}

Then I get an answer from clair:
$ ./reg -d -r registry.example.com vulns --clair http://localhost:6060 organization/imagename1
2017/06/14 14:10:38 registry.ping url=https://registry.example.com/v2/
2017/06/14 14:10:38 registry.manifests uri=https://registry.example.com/v2/organization/imagename1/manifests/latest repository=organization/imagename1 ref=latest
2017/06/14 14:10:38 clair.layers.post url=http://localhost:6060/v1/layers name=sha256:b7...cf
...
Found XX vulnerabilities
CVE-2016-xxx: [Medium]

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-xxx

So it is a matter of registry authentication here i guess?

Submit a PR
On Jun 14, 2017 10:17, "François Maturel"<EMAIL_ADDRESS>wrote:

My clair is not secured, my docker registry container is.
And if i tweak some code like in vulns.go
// NewClairLayer will form a layer struct required for a clar scan
func (c *Clair) NewClairLayer(r *registry.Registry, image string, fsLayers []schema1.FSLayer, index int) (*Layer, error) {
var parentName string
if index < len(fsLayers)-1 {
parentName = fsLayers[index+1].BlobSum.String()
}
// form the path
p := strings.Join([]string{r.URL, "v2", image, "blobs", fsLayers[index].BlobSum.String()}, "/")

return &Layer{
    Name:       fsLayers[index].BlobSum.String(),
    Path:       p,
    ParentName: parentName,
    Format:     "Docker",
    Headers:    map[string]string{
        "Authorization": fmt.Sprintf("Basic %s", "XXX"), // <- FORCED BASIC AUTHENTICATION
    },
}, nil

}
Then I get an answer from clair:
$ ./reg -d -r registry.example.com vulns --clair http://localhost:6060 organization/imagename1
2017/06/14 14:10:38 registry.ping url=https://registry.example.com/v2/
2017/06/14 https://registry.example.com/v2/2017/06/14 14:10:38 registry.manifests uri=https://registry.example.com/v2/organization/imagename1/manifests/latest repository=organization/imagename1 ref=latest
2017/06/14 14:10:38 clair.layers.post url=http://localhost:6060/v1/layers name=sha256:b7...cf
...
Found XX vulnerabilities
CVE-2016-xxx: [Medium]
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-xxx
So it is a matter of registry authentication here i guess?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jessfraz/reg/issues/27#issuecomment-308445391, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABYNbN3yTo1d60KBbbdzxI652mHVh9Xlks5sD-t8gaJpZM4N5z-h
.

Just make it conditional on type of auth
On Jun 14, 2017 10:25, "Jessica Frazelle"<EMAIL_ADDRESS>wrote:

Submit a PR
On Jun 14, 2017 10:17, "François Maturel"<EMAIL_ADDRESS>wrote:

My clair is not secured, my docker registry container is.
And if i tweak some code like in vulns.go
// NewClairLayer will form a layer struct required for a clar scan
func (c *Clair) NewClairLayer(r *registry.Registry, image string, fsLayers []schema1.FSLayer, index int) (*Layer, error) {
var parentName string
if index < len(fsLayers)-1 {
parentName = fsLayers[index+1].BlobSum.String()
}
// form the path
p := strings.Join([]string{r.URL, "v2", image, "blobs", fsLayers[index].BlobSum.String()}, "/")

return &Layer{
    Name:       fsLayers[index].BlobSum.String(),
    Path:       p,
    ParentName: parentName,
    Format:     "Docker",
    Headers:    map[string]string{
        "Authorization": fmt.Sprintf("Basic %s", "XXX"), // <- FORCED BASIC AUTHENTICATION
    },
}, nil

}
Then I get an answer from clair:
$ ./reg -d -r registry.example.com vulns --clair http://localhost:6060 organization/imagename1
2017/06/14 14:10:38 registry.ping url=https://registry.example.com/v2/
2017/06/14 https://registry.example.com/v2/2017/06/14 14:10:38 registry.manifests uri=https://registry.example.com/v2/organization/imagename1/manifests/latest repository=organization/imagename1 ref=latest
2017/06/14 14:10:38 clair.layers.post url=http://localhost:6060/v1/layers name=sha256:b7...cf
...
Found XX vulnerabilities
CVE-2016-xxx: [Medium]
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-xxx
So it is a matter of registry authentication here i guess?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jessfraz/reg/issues/27#issuecomment-308445391, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABYNbN3yTo1d60KBbbdzxI652mHVh9Xlks5sD-t8gaJpZM4N5z-h
.

Not sure how can I get a Registry type of auth in this method

ah gotcha I can make a PR

@fmaturel can you verify that my latest commit fixed it


Adding optimization support for grouped cost function terms

Generalizes Term class into classes for monomial terms and new grouped terms (including SLC)
Supports grouped term inputs in problem and streaming problem interfaces
Includes unit tests for new features

converting to draft since feature is not complete yet.

I would consider getting rid of GroupTerms supporting a regular list of monomials entirely, when there's already the existing mechanism to add ungrouped terms.

The add_terms function now routes away from instantiating a GroupedTerm with type combination; similarly, if a GroupTerm with type combination is initialized, the user receives a warning indicating to use a list of ungrouped monomials instead.

/azp run

/azp run

As discussed yesterday - we want to introduce a new model type before we merge this.

As discussed yesterday - we want to introduce a new model type before we merge this.

In addition, we should add a temporary check in solver.optimize to reject the job for the wrong solver type (if grouped terms are used)... now that we don't need to iterate through all the terms

This is a request from Andres - please elaborate on the feature a bit more in the PR description, customer impact, usage and what the use case is.

/azp run

/azp run

/azp run


PopoverService: Fix DisposeAsync

Description

In Blazor hybrid environments, awaiting a JS interop call may cause the app to hang, such as in: https://github.com/dotnet/maui/issues/7997
I have investigated in this repo and this PR resulted after discussing with @henon.
However, the unit test  MudPopoverService_DisposeAsync_ThrowsExceptionIfNotTaskCancelException needs some work, so if @just-the-benno could take a look, that would be great.
How Has This Been Tested?

Unit tests still need work
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[x] I've added relevant tests.

Looping in @mikes-gh.
@Eilon tagging you in case you have anything to add.

Broadly speaking, JS interop being performed outside of a Blazor context is not a supported scenario for Blazor Hybrid.
However, the bug here appears to be something bigger. Since Windows Forms controls must be disposed synchronously, we synchronously block on the task disposing the service scope. However, this ends up causing a deadlock when a service actually does something asynchronous on disposal (like JS interop). I was able to reproduce a similar hanging bug by reistering a dummy service that implements IAsyncDisposable and awaits Task.Yield().
I'm going to start a discussion on the original thread in https://github.com/dotnet/maui/issues/7997 about potential fixes for this.

Despite the described issue, the reason I implemented IAsyncDisposable in this service was to be able to call a JS method that cleans up the used array and resize and mutation observer. Since Blazor has support for IAsyncDisposable, I thought it is cleaner than relying on AndForget() and implementing it in a "normal" Dispose(). And yes, it makes testing also easier ;)
That said, the functional difference between Dispose() and DisposeAsync() is marginal in this scenario. If you want a way forward, I'd comment on the relevant IAsyncDisposable parts (and tests) and implement an IDisposable version of it.
Hopefully, through the started discussion https://github.com/dotnet/maui/issues/7997 we will know if IAsyncDisposable is even a recommended scenario for Blazor after all.

Maybe there is a way to detect that we are running as Blazor Hybrid and just in that case refrain from awaiting?

I like the idea @henon, but it might be hard to detect given that hybrid apps (at least the winforms ones) run under WebView, which is essentially Microsoft Edge under the hood. I'm not sure we can tell if a "real" browser is involved or not.

Yeah. To be honest, I don't see a problem in either not waiting (.AndForget()) switching to sync dispose. I'd even vote for the first. But let's hear @just-the-benno 's opinion.

Maybe the Navigator in blazor gives info?

@mikes-gh @NavigationManager.Uri and @NavigationManager.BaseUri both return https://<IP_ADDRESS>/ but that's not something we can go off of.

Maybe you can leave this choice to the developer, with a parameter like "IsBlazorHybrid"
(it would be similar to using the parameter "IsDarkMode" in MudThemeProvider).

@cinderbear Sure, if you can give a good reason why.

@henon The reason would be to alert MudBlazor of a hybrid environment to avoid awaiting a JS disposal indefinitely: https://github.com/MudBlazor/MudBlazor/pull/5367#issuecomment-1270231432
However, handling the root issue of .AndForget() is probably best.

Since this issue seems caused by subtle differences in the behavior of webview depending on the underliying platform (like this case that appears to affect winforms) it may be useful to have a parameter to differentiate this kind of usage, given that it's very difficult or impossible to detect automatically.
But if you consider that the fix would not affect any other use cases, it may not be currently needed.

@Mr-Technician how about UA
What does this give on your webview
https://stackoverflow.com/questions/37591279/detect-if-user-is-using-webview-for-android-ios-or-a-regular-browser
var standalone = window.navigator.standalone,
  userAgent = window.navigator.userAgent.toLowerCase(),
  safari = /safari/.test(userAgent),
  ios = /iphone|ipod|ipad/.test(userAgent);

if (ios) {
  if (!standalone && safari) {
    // Safari
  } else if (!standalone && !safari) {
    // iOS webview
  };
} else {
  if (userAgent.includes('wv')) {
    // Android webview
  } else {
    // Chrome
  }
};

@mikes-gh Good lead, but unfortunately the UA isn't distinguishable from a normal browser:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/107.0.1418.52


Refactor to use BasicTask and Operations

This refactors a bunch of Replica methods and the high-level Task/TaskMut to use BasicTask and commit operations to achieve their goals.
I summarize all of the deprecations together in a later commit, with the breaking changes.
This is one of the "boring" bits for #372 - the next is, too, and then we get to the interesting breaking changes.

I'm seeing a few self.task.task in TaskMut and task.task.task in tests which I believe could be reduced by one ".task" due to Deref.

This doesn't work because deref only works for method calls, so self.task.foo() uses the task property on TaskMut, of type Task, and then looks for a foo method on it.  Later PRs will address this, in particular when Task and TaskMut are unified into a single type.

I noticed that clippy is broken in CI again

Oops, thanks for spotting that! A downside of a lot of rebasing.
I have a little more work to do here and will request review.

Looks good. I don't entirely understand all the testing changes in the last commit but I presume they pertain to removing apply in the next PR.

Yeah, a lot of the tests are in terms of SyncOp instead of Operation, and that gets addressed in the next PR ("Prefer Operation instead of SyncOp"). So, for this PR I've kept the SyncOp-related methods as test-only.


Use generic indexes and multi-language lookups

This PR supports https://github.com/ONSdigital/eq-terraform-elasticsearch/pull/3
It adds support to query an index and ability to query by language.
en only searches and returns en results
cy searches and returns both en and cy values

@ajmaddaford i think this will need more work in terms of tuning the queries, i haven't really looked at that in this pr. ive just updated the lists and made the interface more appropriate to what Ben was after

@ajmaddaford It uses the index names so ill update that in the other PR

@ajmaddaford can you re-review?


Ludwig hyperparameter optimization using the hyperopt package

Code Pull Requests
@w4nderlust   This is the 3rd api example.
Jupyter notebook model_hyperopt_example.ipynb demonstrates using the hyperopt package to perform hyperparameter optimization during Ludwig model training. Key features demonstrated in the notebook:

Programmatically building a Ludwig model definition from training data set
Setup hyperparameter search space for optimization
Using hyperopt fmin() function to determine optimal hyper parameters

This is related to two other PR #564 and #578.  All three PR should be merged together.

Thank you so much for this, very thorough!


Imported K3s cluster - not use private registry in air-gap env for upgrading

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):

run Rancher HA in airgap env
provision a 1-node k3s (v1.0.1) cluster in airgap env
import the k3s cluster into Rancher
In Rancher, edit the cluster to upgrade to a newer version v1.16.7-k3s1

Result:

under the system project, the deployment system-upgrade-controller and job apply-k3s-master-plan-on-ip-172-31-22-101-with-b5c244a878-64bad is created

the job apply-k3s-master-plan-on-ip-172-31-22-101-with-b5c244a878-64bad failes to pull images because it does not use the private registy

Other details that may be helpful:

the image rancher/k3s-upgrade:v1.16.7-k3s1 is not in the rancher-images.txt file

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI):
v2.4.0-rc3
Installation option (single install/HA):
HA

This is almost certainly because both of these images are missing from the airgap images tarball:

rancher/k3s-upgrade:v1.16.7-k3s1
rancher/kubectl:v1.17.0

Related K3s documentation issue https://github.com/rancher/k3s/issues/1547

on Rancher v2.4.0-rc3 airgap env

add the missing images to the image-list.txt https://github.com/rancher/k3s/blob/master/scripts/airgap/image-list.txt
push those images to the private registry
upgrade imported k3s cluster from  k3s v1.0.1 (k8s 1.16.3) to  k3s version v1.16.7+k3s1

result:

the k3s cluster is upgraded successfully

Stil waiting for a new RC to validate the fix

@jiaqiluo v2.4.0-rc6

Validated in v2.4.0-rc8
Steps:

Add the proper images, including the missing ones, to a txt file in bastion server:

docker.io/coredns/coredns:1.6.3
docker.io/library/traefik:1.7.19
docker.io/rancher/klipper-helm:v0.2.3
docker.io/rancher/klipper-lb:v0.1.2
docker.io/rancher/local-path-provisioner:v0.0.11
docker.io/rancher/metrics-server:v0.3.6
docker.io/rancher/pause:3.1
rancher/k3s-upgrade:v1.16.7-k3s1
rancher/kubectl:v1.17.0
rancher/k3s-upgrade:v1.17.3-k3s1

Push those images to the private registry
Upgrade imported k3s from k3s v1.0.1 (k8s 1.16.3) to k3s version 1.16.7+k3s1 (success!)
Upgrade again to k3s version 1.17.3+k3s1 (success again!)


The custom_command should not be required on unix

Currently the stream configuration has to contain a certain custom_command to allow the serial communication to work properly. The command currently stated in the echo.php example isn't final, as it still does not work under certain circumstances, see #1.
https://github.com/machinateur/phpduino/blob/b4b6b469ad7ab2bf6e1cb31636e802875efb05df/echo/echo.php#L41-L62
This overhead could be avoided by moving that command and configuration to the concrete implementation for linux/mac, once the command properties are finalized and verified to work on all supported systems (that includes windows, mac and linux).
To ease testing, it should be possible to create a debian based docker container. Mounting the serial port to the container should give it access to the Arduino device, so the communication can be tested properly (I don't currently have linux installed on any of my computers). See this StackOverflow question for a good starting point on how to give docker access to a serial device.

The custom command is final since 0.1.2.
The next step is to move the options to the library context, to make everything work out-of-the-box.
It also makes sense to provide sufficient documentation with that step, for the command syntax/synopsis.
Also, since the chunk size was recently found to be an important part of the configuration, check if there is a way to access the real $length parameter in streamWrapperAbstract::stream_read(), which would be more elegant that having a dependency on a certain fixed chunk size. Debugging one of th  example scripts will suffice to find out about that.


Add support for radial gradients

Is your feature request related to a problem? Please describe.
Currently figmagic seems to pass over or omit a color token if it has a radial gradient fill type. Linear gradients appear to work fine.
Describe the solution you'd like
It would be great if a color had a radial gradient that figmagic could support that as a token output value.

Hey @tjmusser.
Correct, only linear gradients were supported. This was documented in the dedicated elements README but seemingly not in the main one.
However, I did just release support for radial gradient in 4.2.7, so do try it out.

Hey thanks @mikaelvesavuori ! This is just what I needed

@mikaelvesavuori one thing I did notice is that the gradient doesn't appear to be an exact match.
Figma shows this as the CSS for a gradient
radial-gradient(129.7% 129.7% at 37.96% -17.61%, #6284F8 0%, #5276EB 22.51%, #5276EB 56.92%, #D2A1C5 100%);

While figmagic has that same gradient output as:
radial-gradient(circle, rgba(98, 132, 248, 1) 0%, rgba(82, 118, 235, 1) 23%, rgba(82, 118, 235, 1) 57%, rgba(210, 161, 197, 1) 100%)

The circle size and co-ordinates appear to change.

Hi again, it seems my naive implementation falls on the first part where we need to calculate the shape and size of the gradient. It was hardcoded to circle, but this is of course broken given a shape where the gradient does not originate from the center.
My remaining piece now seems to be to figure out how we can calculate the first two values (129.7% 129.7 in your example) from Figma since those do not seem to be directly present in the JSON we pull from the API. The secondary couple of values however is present.
See https://developer.mozilla.org/en-US/docs/Web/CSS/radial-gradient()

@mikaelvesavuori I'm not sure if this helps but I'm including the json from the files API for this exact gradient. It's speculatioon on my part but perhaps it is calculated in some way using the gradientHandlePositions values as a ratio compared against the height/width of the absoluteBoundingBox in the json response.
Also included is a screenshot of this same gradient in Figma. It expands outside the box uniformly in a circle.
{
  "id": "2631:9025",
  "name": "Backgrounds/Core Gradient",
  "type": "RECTANGLE",
  "blendMode": "PASS_THROUGH",
  "absoluteBoundingBox": {
    "x": -1650.0,
    "y": -1033.0,
    "width": 120.0,
    "height": 120.0
  },
  "preserveRatio": true,
  "constraints": {
    "vertical": "TOP",
    "horizontal": "LEFT"
  },
  "fills": [
    {
      "blendMode": "NORMAL",
      "type": "GRADIENT_RADIAL",
      "gradientHandlePositions": [
        {
          "x": 0.37963923004588951,
          "y": -0.17608905954948240
        },
        {
          "x": 0.53427832078498128,
          "y": 1.1209453230683617
        },
        {
          "x": -0.91739525745239492,
          "y": 0.32380704136536220
        }
      ],
      "gradientStops": [
        {
          "color": {
            "r": 0.38431373238563538,
            "g": 0.51764708757400513,
            "b": 0.97254902124404907,
            "a": 1.0
          },
          "position": 0.0
        },
        {
          "color": {
            "r": 0.32156863808631897,
            "g": 0.46274510025978088,
            "b": 0.92156863212585449,
            "a": 1.0
          },
          "position": 0.22509866952896118
        },
        {
          "color": {
            "r": 0.32156863808631897,
            "g": 0.46274510025978088,
            "b": 0.92156863212585449,
            "a": 1.0
          },
          "position": 0.56917303800582886
        },
        {
          "color": {
            "r": 0.82352942228317261,
            "g": 0.63137257099151611,
            "b": 0.77254903316497803,
            "a": 1.0
          },
          "position": 1.0
        }
      ]
    }
  ],
  "strokes": [],
  "strokeWeight": 1.0,
  "strokeAlign": "INSIDE",
  "styles": {
    "fill": "701:3247"
  },
  "effects": [],
  "cornerRadius": 4.0,
  "rectangleCornerRadii": [
    4.0,
    4.0,
    4.0,
    4.0
  ]
}

This should now be improved and will be released shortly in 4.2.8.

Thank you @mikaelvesavuori ! I will have to check it out :)


Ingredients and Plutos package manager

Currently, when I have an ingredient that imports a package, then I have to import that package also manually in each notebook that uses that ingredient. Would it be possible for Pluto to automatically add those packages to the environment of the notebook that includes the ingredient?
Even better for reproducibility would be of course if both keep their own environment, but that probably isn't possible.

I am not sure I understand what you mean by package here. Are you using @ingredients on:

Another Pluto notebook with its own environment
A plain Julia file
The entry point of a package (Package.jl/src/Package.jl)

The first one, another Pluto notebook with its own environment

So I have a notebook that has some cell using SomePackage. When I want to use that notebook as an ingredient in another notebook I manually have to also add a Cell containing using SomePackage.

This is a really good question @karlwessel ! And a larger project that we still need to figure out.
Ideally, the other notebook's env will be added as a Pkg dependency to the main notebook. That way, the dependencies of the other notebook will be made available, respecting constraints in the embedded Project.toml of the other notebook (which Pluto automatically writes).
The basic idea is to create a temporary folder containing the Project.toml (with some additions) and Manifest.toml from the notebook and a file src/SomeName.jl containing something like module SomeName $(notebook code) end. Then in the main notebook, this folder would be added as dependency using Pkg.develop.
But this leads to a reproducibility problem: we want someone else to be able to open the notebook. So far, our reproducibility has always focused on a single file, but in this case, you also need the other notebook file, and the temporary package files need to be generated before instantiating the notebook's environment. Maybe the other notebook's contents should be embedded in the file of the main notebook? Tricky tricky
cc @pankgeorg  @dralletje


[WIP] Support $ projection query operator

Closes #361.

Waiting for https://github.com/FerretDB/FerretDB/pull/539 to be merged

We decided to postpone projection support


add gulp task runner

Add gulp task runner
Add task to minify CSS
Improve filestructure

Gulp task runner is already there and improvements were made in: https://github.com/ciar4n/imagehover.css/commit/122a99b52b80ae5bbcca7c5e644d3faef6e4691a


Unit testing fails for factory_spec.js

Testing doesn't work with Plotly. The file was renamed as factory_spec_FIX.js so that Jasmine will ignore it.

we will have to mock document, element, and window objects for testing, including some properties.
At the factory_spec part that is failing only test a few lines, and we are not testing the UI at all.
I will remove the failing test for now.


[prometheus-blackbox-exporter] Allow to enable kube-rbac-proxy for prometheus-blackbox-exporter

What this PR does / why we need it
Allow to enable kube-rbac-proxy for prometheus-blackbox-exporter
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer
Checklist

[ ] DCO signed
[ ] Chart Version bumped
[ ] Title of the PR starts with chart name (e.g. [prometheus-couchdb-exporter])

https://github.com/kubesphere/issues/issues/1527


Transition required props unexpected behaviour

Hello !
Thank you very much the the library, it's awesome how ridiculous simple animations can be achieved.
I'm working on a project that can't upgrade to latest version of React, so I need to work with react-spring/renderprops. After reading the Transition component docs I found out some unexpected behaviour if you don't supply the non-required props from and enter.
You can check it on this sandbox.
Very straightforward examples:

        // Doesn't work
        <Transition
          items={this.state.open}
          leave={{
            from: {
              backgroundColor: "#FFF"
            },
            backgroundColor: "#000"
          }}
        >
          {open =>
            open &&
            (props => (

Hello CodeSandbox

Start editing to see some magic happen!

            ))
          }
        </Transition>

        // Works
        <Transition
          items={this.state.openGood}
          from={{
            visibility: "visible"
          }}
          enter={{
            visibility: "visible"
          }}
          leave={{
            from: {
              backgroundColor: "#FFF"
            },
            backgroundColor: "#000"
          }}
        >
          {open =>
            open &&
            (props => (

Hello CodeSandbox

Start editing to see some magic happen!

            ))
          }
        </Transition>

The first one doesn't work as expected and the second one is working as expected but I need to add useless values for the from and enter props.
Am I doing something wrong ?

Hi @drcmda ! Thanks for the comment. Two things come to my mind then:

Why is from inside leave still working then ? If it's not allowed (by the way I couldn't find any of that in the docs), I think it shouldn't work.
How would you then animate a component that only needs an onUnmount animation ?

https://www.react-spring.io/docs/hooks/useTransition see additional notes on multistage transitions. You need at least from, to give it base values, otherwise it will not animate new values because it wouldn’t know from where to animate. For instance you say: animate green, that doesn’t make sense to it, should it start black, blue,...? If you say animate from yellow to green, that is better.

Right, but once again in the docs you referenced it states that the from prop is optional. On the other hand you are telling me it's needed to know from where to animate, so I'm confused 😅 That's why a created a from key in the leave prop value, and it actually works as you can see in my codesandbox 🤷♂

no, what i mean is that if you optionally supply base values, it has something to animate towards. if you do not have from and just give it "enter", that is valid, but the state will simply appear, without animation. sometimes you want it to be like that.


Remove assertions for lambda retry count

Ref: https://github.com/aws/aws-xray-sdk-java/pull/299
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #107 (e3de316) into main (a988866) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main     #107   +/-   ##
=========================================
  Coverage     65.10%   65.10%
  Complexity      193      193
=========================================
  Files            17       17
  Lines           854      854
  Branches        132      132
=========================================
  Hits            556      556
  Misses          229      229
  Partials         69       69

Continue to review full report at Codecov.

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


[Feature Request] show message when cloud-init is finished

Problem:
When using cloud-init it is hard to know when cloud-init is finished setting everything up.
Solution:
If you could implement some way to show a message in the console, this would be more convenient.
Options implemented in cloud-init are:

cloud-init status
call-a-url-when-finished
completion message

For Reference:
As far as I remember Docker for example only starts the container when the Dockerfile has finished.
Alternatives/Enhancements:

only show container as ready when cloud-init is finished
A progress bar would be even more convenient, though probably (very) difficult to implement (and also out of scope of this project)
Console/log of cloud-init (the idea is to show it in the host console)

IMHO it would be great to report the container's status as 106 Starting while cloud-init is running, so its more obvious when the container is 100% ready.

That's out of scope for LXD. LXD works quite hard not to care about anything that's running in the container.
Doing something like this would require LXD poke all containers, monitor files, ... which is all quite expensive, extremely distro-specific and even release specific at times.
It could also be used as an attack vector by having the container provide bogus output to LXD.
There are cloud-init commands you can run for yourself which will wait until cloud-init is complete. I'd recommend using those.

Ok, but just to mention it, you provide images which explicitely provide cloud-init, so cloud-init might be seen as a "core"-feature.
Maybe a more generic way of passing a message from the container to LXD could be implemented, that can only activate specific messages and would be encrypted/signed (or protected in some other way), so only specific applications can use it (like cloud-init).
All of this could also be optional, so the message is only shown if the user chooses it in LXD (per container start).
That said I understand and respect your decision, just wanted to mention it :slightly_smiling_face: .


Fix wording in description of store_line and store_string

As pointed out by https://github.com/godotengine/godot-docs-user-notes/discussions/200#discussioncomment-10941053, using "Append" here creates confusion. It was changed in #42442.
This PR changes it back to "Store", like how other store_*() methods are described.

Not sure if your merge process includes cache invalidation but even after clearing browser cache:
class_fileaccess.html
date:
Wed, 16 Oct 2024 19:25:20 GMT
last-modified:
Fri, 04 Oct 2024 03:31:29 GMT
The old store_line() doc entry is there


Unskip --binstubs flag deprecation

What was the end-user problem that led to this PR?
The problem was that some deprecation specs were still skipped.
What was your diagnosis of the problem?
My diagnosis was that I should get all of them passing.
What is your fix for the problem, implemented in this PR?
My fix is to uncomment the spec and get it passing. The only fix was to include the full deprecation message so that it matches the assertion.
Why did you choose this fix out of the possible options?
I could've regexp-matched the existing message but I preferred to use the full message in the assertion instead. I chose this fix because although it makes it more brittle since changing the message will break the test, having the whole messages inside the deprecation specs makes it easier to get a quick view and understand the stuff that we are deprecating and the quality of the existing deprecation messages.

Thanks @colby-swandale!
@bundlerbot r=colby-swandale


Warning when using std::unique_ptr<T[N]>

MSVC will emit a warning when compiling std::unique_ptr<T[N]> because default_delete<T[N]> has undefined behavior. See https://github.com/boostorg/hana/blob/master/test/tuple/smart_ptr.cpp for details.
Other compilers don't complain likely because warnings are suppress for system headers.
All compilers give warning if it is used in user code:
#include <memory>

void f(char(*p)[5])
{
	std::default_delete<char[5]> d;
	d(p); // no warning in clang/gcc

	delete p; // warning
}

There is an ongoing discussion in LWG on whether a partial specialization should be added for 'T[N]'.
But in the current state, we believe the warning is legit.

Thanks for the report -- will fix.


Empty dropdown list causes a reboot, tested on 86s

Sorry but it looks like I found another issue -  this payload causes a reboot - {
"tiles": [
{
"screen": 1,
"tile": 7,
"dropDownList": []
}
]
}

Yes, that's a bug. The FW should be able to handle this correctly (at least no reboot).
Out of curiosity, what was the reason for sending the empty payload?


update sample policies

added usage for sample policies
removed categories from markdown
added logic to use title annotation if present
added instructions on rendering markdown

I also changed the search to use a local search.
You can try it at: https://deploy-preview-56--kyverno.netlify.app/

I also changed the search to use a local search.
You can try it at: https://deploy-preview-56--kyverno.netlify.app/

Some comments noted here.

@chipzoller - here is a corresponding PR for the policies (titles, descriptions, etc.): https://github.com/kyverno/policies/pull/7.


Nuxt 2 compatibility

Environment
Local
Reproduction
In Nuxt config:
gtag: {
  id: "AW-***************",
  initialConsent: false,

  config: {
    page_title: "********",
    pageTrackerScreenviewEnabled: true,
  },
},

modules: [
  "nuxt-gtag",
],

In Vue File (Nuxt):
const { gtag } = useGtag();

gtag("event", "conversion", {
send_to: "AW-****************/FdYvCL6qm90YEMW-v_wp",
});

Describe the bug
Error when using the nuxt-gtag.
Error is - ReferenceError: useGtag is not defined
Please, how can I use the plugin successfully? I keep getting the error.
Additional context
This is a Nuxt project. With the following version numbers:
"nuxt": "^2.15.8",
"vue": "^2.6.14",

"nuxt-gtag": "^1.1.0"

Logs
This is the long when I attempt to mount on the page where I import and use useGtag():

client.js:103 ReferenceError: useGtag is not defined
    at eval (completed-form.vue:8:1)
    at ./node_modules/babel-loader/lib/index.js?!./node_modules/vue-loader/lib/index.js?!./node_modules/string-replace-loader/index.js?!./pages/contact/completed-form.vue?vue&type=script&lang=js& (completed-form.js:22:1)
    at __webpack_require__ (runtime.js:854:30)
    at fn (runtime.js:151:20)
    at eval (completed-form.vue:1:1)
    at ./pages/contact/completed-form.vue?vue&type=script&lang=js& (completed-form.js:80:1)
    at __webpack_require__ (runtime.js:854:30)
    at fn (runtime.js:151:20)
    at eval (completed-form.vue:1:1)
    at ./pages/contact/completed-form.vue (completed-form.js:68:1)

This module is made for Nuxt 3.
For Nuxt 2, you can use google-analytics-module.

Please, add "Nuxt 3" requirement somewhere on homepage.
Just wasted some time trying to figure out why this module doesn't work in my project.

Sorry to hear that you ran into the trouble. Generally speaking, you can check compatibility in the Nuxt modules table. I will keep the description as-is. On December 31st, 2023, Vue 2 will reach End of Life (EOL), and Nuxt 2 will follow on June 30th, 2024. Not much time left. I already consider Nuxt 3 the “standard” and intend to keep it that way. 🙂

midleware com o código:
janela.dataLayer = janela.dataLayer || [];
função gtag(){dataLayer.push(argumentos);}
gtag('js', nova Data());
gtag('config', 'G-XXXXXX');
E crie algum evento em midleware
gtag('evento', 'nome_do_evento', {...opção})
dessa forma vc não precisa de nenhuma lib. As do nuxt 2 estão desatualizadas e não funcionam.

550 / 5.000
Resultados de tradução
Resultado da tradução
If anyone needs a library for gtag in nuxt 2, I recommend adding the script link "src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXX" in the head of nuxt.config.js and then create middleware with the code:
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'G-XXXXXX');

And create some event in middleware
gtag('event', 'event_name', {...option})
That way you don't need any libs. The nuxt 2 ones are outdated and don't work.

This module is made for Nuxt 3.
For Nuxt 2, you can use google-analytics-module.

Well that's unfortunate indeed because google-analytics-module is using Universal analytics under the hood it seems and Google is going to shut it down soon. The alternative vue-gtag listed in the thread doesn't work on SSR effectively leaving 0 libraries for Nuxt 2 users who haven't migrated yet


Import from IPFS causes error: Failed to load resource: the server responded with a status of 500 (Internal Server Error)

Problem description
This issue happens when a user tries to import a policy from IPFS, providing a timestamp
Step to reproduce
Steps to reproduce the behavior:

Go to the 'Policy' tab
Click on the 'Import' button
Select 'Import from IPFS' option
Enter hedera message timestamp<PHONE_NUMBER>.111298000)
Click the 'Ok' button
See the 500 error that occurred

Expected behavior
A user should be able to import a policy from IPFS without errors
Screenshots

[Uploading... Screen Recording 2022-03-18 at 8.06.47 AM.mov]

[Uploading... Screen Recording 2022-03-18 at 8.06.47 AM.mov]

QA PASSED. It works as expected.

This ticket was closed on March 18th


feat: update to eye v2.5.0

feat: update to eye v2.5.0

:tada: This PR is included in version 2.7.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release
v2.7.0

Your semantic-release bot :package::rocket:


Add support for Gitlab Job and Pipelines events.

These events are ready to be supported but right now there is no implementation.
A clean webhook for jobs and pipeline would be optimum:
https://docs.gitlab.com/ee/user/project/integrations/webhooks.html#pipeline-events
https://docs.gitlab.com/ee/user/project/integrations/webhooks.html#job-events

closing in favor of #12


Macbook Pro M1 - Monterey 12.4 - no tests showing

Describe the Bug
After performing a clean installation of Visual Studio Code on macOS, with only limited extensions, no tests appear when opening any project. When doing the same thing on a Windows machine it works without an issue.
When trying to use other addons for Test Explorer UI, such as Python addon, it is loaded properly
Steps to Reproduce the Behavior

Create a new project, 'ng create test-units'
Install Karma Test Explorer and Test Explorer UI
Add any unit test
Open Test Explorer UI tab
No plugin loaded/no tests shown

Describe the Expected Behavior
I expected to see all of the tests.
Provide Debug Logs
[2022-07-25 13:22:43.598] [DEBUG] [ProjectFactory]: Inspecting workspace folder for testing: /Users/antoniomikulic/Documents/Test projects/test-units
[2022-07-25 13:22:43.598] [DEBUG] [ProjectFactory]: Including projects in workspace folder '/Users/antoniomikulic/Documents/Test projects/test-units' - 'karmaTestExplorer.enableExtension' is set to true
[2022-07-25 13:22:43.598] [DEBUG] [ProjectFactory]: Including projects in workspace folder - One or more inclusion conditions were satisfied: /Users/antoniomikulic/Documents/Test projects/test-units
[2022-07-25 13:22:43.598] [DEBUG] [ProjectFactory]: Angular projects found for workspace folder /Users/antoniomikulic/Documents/Test projects/test-units: ["test-units"]
[2022-07-25 13:22:43.598] [INFO] [ProjectFactory]: Using angular project type for workspace folder '/Users/antoniomikulic/Documents/Test projects/test-units' (auto-detected)
[2022-07-25 13:22:43.598] [DEBUG] [ConfigChangeManager]: Creating config change subscription
[2022-07-25 13:22:43.598] [DEBUG] [Main]: Subscribing for workspace config changes

Please also capture and attach the logs from the Karma Server Output channel when the issue occurs.

Screenshots

Please Provide the Following Information

OS: macOs Monterey 12.4
Environment:  just visual studio code and zsh. VS Code is set up and not in quarantine/read-only
Node Version: v18.6.0
VS Code Version: 1.69.2, was on the older one but tried a complete reinstall
Karma Version: 6.3.0
Frameworks: Angular

Additional Context
Doing the same on Windows machine works. I tried this for couple repos, where project is in root, subfolder, etc, nothing seemed to work.

Your detailed report is helpful. Can you also:

Attach the full debug logs from the other Karma Test Explorer (...) and Karma Server (...) channels in the VS Code Output panel?
Try it on an Intel Macbook variant to see if you experience the same issue

Maybe I'm missing something, but I cannot see the Karma Server (...) output channel using VS Code.
This is using when I select VS Code -> Output -> Karma Test Explorer (workspace), its the only one I see that mentions Karma
[2022-07-26 06:35:13.905] [DEBUG] [ProjectFactory]: Inspecting workspace folder for testing: /Users/antoniomikulic/Documents/Test projects/test-units
[2022-07-26 06:35:13.905] [DEBUG] [ProjectFactory]: Including projects in workspace folder '/Users/antoniomikulic/Documents/Test projects/test-units' - 'karmaTestExplorer.enableExtension' is set to true
[2022-07-26 06:35:13.905] [DEBUG] [ProjectFactory]: Including projects in workspace folder - One or more inclusion conditions were satisfied: /Users/antoniomikulic/Documents/Test projects/test-units
[2022-07-26 06:35:13.905] [DEBUG] [ProjectFactory]: Angular projects found for workspace folder /Users/antoniomikulic/Documents/Test projects/test-units: ["just-todo-it"]
[2022-07-26 06:35:13.905] [INFO] [ProjectFactory]: Using angular project type for workspace folder '/Users/antoniomikulic/Documents/Test projects/test-units' (auto-detected)
[2022-07-26 06:35:13.905] [DEBUG] [ConfigChangeManager]: Creating config change subscription
[2022-07-26 06:35:13.905] [DEBUG] [Main]: Subscribing for workspace config changes
[2022-07-26 06:39:15.233] [INFO] [ConfigChangeManager]: Configuration changed
I will check if someone has Intel MacBook for testing

I am experiencing the same in the same environment. Unfortunately, I cannot add anything more, the logs are also the same.

Additional frobbing found that if I add "src" as a project, it will start the Karma server, but the server complains that it cannot find the karma.conf.js file.
Error: Cannot find module '/Users/Home/BSI/repos/artemis-portal/src/karma.conf.js'

If I specify "../karma.conf.js" as the path for the config file, then the server complains that:
Server start failed on port 9976: Error: The '@angular-devkit/build-angular/plugins/karma' karma plugin is meant to be used from within Angular CLI and will not work correctly outside of it.

I'm able to reproduce this, which seems to be an issue for new Angular projects for which the angular.json config does not specify a defaultProject - which has been deprecated. Karma Test Explorer also deprecated its defaultAngularProjects extension setting in v0.7.0.
I've made a fix in the beta branch - download the .vsix from the CI build or build it yourself directly from the branch, and test to confirm if it resolves the issue for you.

Hey, that did manage to fix it for me!

Great, released in v0.7.2.
Don't hesitate to open a new issue if you experience any other problems.

Yes, v0.7.2 works for me as well! Thank you!


Support GHC >= 9.6

Also require mtl >= 2.3
Bump to version 1.5 (feel free to change this to a minor bump if preferred)

Thanks!


[Bug] Devtools shortcut is ctrl+shift+i on MacOS

Before Reporting

[X] I found no existing issues matching my bug
[X] My issue is not caused by a plugin or theme

Describe the Bug
On MacOS, the keyboard shortcut for opening the devtools is ctrl+shift+i (⌃⇧i)
Expected Behavior
Like most browsers on MacOS, the keyboard shortcut should be cmd+shift+i (⌘⇧i)
Steps To Reproduce

be on macos
turn on DevTools setting
try ⌘⇧i (doesn't do anything)
try ⌃⇧i (opens devtools)

Operating System
MacOS
Discord Version
Stable
BetterDiscord Version
v1.8.2
Anything else?
No response

I would not say this is a bug, as this was the intention. This could be a feature request though.


Deadlock issue caused by timeout mutex locks

Hello,
I'm experiencing issues with the mutex locks, as it appears to be causing a deadlock. Here's the code snippet that triggers the problem:
https://github.com/embassy-rs/teleprobe/blob/6eb24c3182ef94665fe3a17fb10acd85a3c9cda2/teleprobe/src/server.rs#L196-L200
To resolve the issue, I made the following change:
let default_timeout = cx.lock().config.default_timeout;
let max_timeout = cx.lock().config.max_timeout;
let timeout_secs = args.timeout.unwrap_or(default_timeout).min(max_timeout);

This modification seems to fix the problem. Would you like me to open a pull request to implement this change?

Yes please.
Strange that it works for me though. Huh.

fixed in 0099ddaeacde7e5d9b0930a4c6e029e89c308982


Add moorhen prefix to Redux slice names

As we discussed, it'd be very helpful for embedding Moorhen in other React applications if the slice names could include moorhen as a prefix, to avoid name collisions with the slice names in the embedding app and make it clear when the Moorhen state is being accessed directly.

Dear Colin,
Sorry, I have not been monitoring this forum at all. Filo used to do it. I will look into this asap.


Rc/3.1.0

Description
LEARNER-8713

Created https://github.com/openedx/edx-app-ios/pull/1605 to merge the rc/3.1.0 into master after resolving the conflicts.


accept button isn't clickable

settings.chatButtons.rpsInviteAcceptButton isn't clickable on MC 1.21.1. I use v1.2.3 of the plugin.
There is no console error nor warning. Also message seems good but we can't click to the message.

sorry I just see you changed the default configuration file


[Feature Request]: Support searching hex strings

Describe the problem
I have a text, which stores some information about an ethereum contract, the contract address is in hex, I try to search for the contract
import chromadb

client = chromadb.Client()
collection = client.create_collection("all-my-documents")

collection.add(
    documents=['dune assigns label "Chainlink: Aggregator" to contract "0xefcbea1e97888793896458dc79fce7ad36a70fef" ',
               'dune assigns label "Convex_finance: BaseRewardPool" to contract "0x22ee18aca7f3ee920d01f25da85840d12d98e8ca" ',
               'dune assigns label "Convex_finance: BaseRewardPool" to contract "0x4a866fe20a442dff55faa010684a5c1379151458" ',
               'dune assigns label "Curvefi: usdp_deposit" to contract "0x3c8caee4e09296800f8d29a68fa3837e2dae4940" '
               ],
    ids=["doc1", "doc2", "doc3", "doc4"],  # unique for each doc
)

results = collection.query(
    query_texts=['"0xefcbea1e97888793896458dc79fce7ad36a70fef"'],
    n_results=1
)
print(results['documents'])

but I get incorrect results :

[['dune assigns label "Convex_finance: BaseRewardPool" to contract "0x22ee18aca7f3ee920d01f25da85840d12d98e8ca" ']]

does not contain the contract address "0xefcbea1e97888793896458dc79fce7ad36a70fef"
my guess is that chroma thinks the address "0xefcbea1e97888793896458dc79fce7ad36a70fef" is not a word
Describe the proposed solution
How can I do a search for an hex address?
Alternatives considered
No response
Importance
i cannot use Chroma without it
Additional Information
No response

@myfjdthink ah - this is going through embeddings, which is probably not what you really want to do. .query does fuzzy search/matching - that is the whole power of embedding search.
if you just want to get it, you can do this...
import chromadb

client = chromadb.PersistentClient()
collection = client.create_collection("all-my-documents")

collection.add(
    documents=[
        'dune assigns label "Chainlink: Aggregator" to contract "0xefcbea1e97888793896458dc79fce7ad36a70fef" ',
        'dune assigns label "Convex_finance: BaseRewardPool" to contract "0x22ee18aca7f3ee920d01f25da85840d12d98e8ca" ',
        'dune assigns label "Convex_finance: BaseRewardPool" to contract "0x4a866fe20a442dff55faa010684a5c1379151458" ',
        'dune assigns label "Curvefi: usdp_deposit" to contract "0x3c8caee4e09296800f8d29a68fa3837e2dae4940" ',
    ],
    ids=["doc1", "doc2", "doc3", "doc4"],  # unique for each doc
)

results = collection.get(
    where_document={"$contains": "0xefcbea1e97888793896458dc79fce7ad36a70fef"}
)
print(results["documents"])

Closing this - search for hashes should be accomplished through text search (which chroma also supports) - and not through embeddings.


Error: Command failed: npm install cgb-scripts --save --save-exact --silent

Bug Report
Expected Behavior
I wanted to install create-guten-blocks by running the npx create-guten-blocks my-block command.

Actual Behavior
I expected to install the create-guten-block plugin, but when I try to run the "npx create-guten-block my-block" It throws me the next error after a while:
Error: Command failed: npm install cgb-scripts --save --save-exact --silent
at makeError (/home/vagrant/.npm/_npx/4487/lib/node_modules/create-guten-block/node_modules/execa/index.js:169:9)
at Promise.all.then.arr (/home/vagrant/.npm/_npx/4487/lib/node_modules/create-guten-block/node_modules/execa/index.js:274:16)
at processTicksAndRejections (internal/process/next_tick.js:81:5)
I am sorry if im not able to provide further information, this is as far as I got into the plugin, I cant seem to be able to install it at all, let alone use it!!

Steps to Reproduce

(Write your steps here:)

Go to the plugins directory on the project.
Open the command line
Run "npx create-guten-block my-block"

node -v: 6.9.0

npm -v:   v11.10.1

yarn --version (if you use Yarn):  N/A

npm ls cgb-scripts (if you haven’t ejected):  N/A

Operating system:  Ubuntu 18.04.1 LTS

Browser and version (if relevant):   N/A

Possible Solution

It seems to me that the error is when Im installing all the cgb-scripts, but I dont know what is causing the issue.
I would appreciate any help to start working on the plugin as fast as possible, Thank you in advance!

I have exactly the same issue occurring on Windows 10 64-bit.
I'm using:

node -v 8.15.0
npm -v 6.4.1

Any help would be greatly appreciated!

I have exactly the same issue occurring on Windows 10 64-bit.
I'm using:

node -v 8.15.0
npm -v 6.4.1

Any help would be greatly appreciated!

I was very dissapointed to not have any sort of support from this plugin after almost ten days of posting my issue, and I found out a way to create my own blocks from scratch in this very in-depth and well explained video, it helped me to create my own block and also showed me a little JSX / React (which is what gutenberg blocks uses), I hope you find it useful:
https://www.youtube.com/watch?v=Mv68Sa-iHyo&list=LL22-OvuLQevpuSFPWrwXcTA&t=1686s&index=15

I'm happy for you.
Don't expect support for free and Open source software that 99% people who use it never contribute to or support monetarily.
I wish I had ten more like me to help with everything.

Thanks @mauricionieto1994 I'll definitely take a look at the video!
@ahmadawais I understand your point! I was wondering, is there any way we could help to make it work on Windows and Ubuntu?

It is open source. Try to test and figure out what's wrong and then contribute the fix. That's how you can help with code. Otherwise, support me or someone else by monetary donation to devote some time to this project and fix this for you. Both forms of contributions are welcomed.

This is an error related to the vagrant guest not allowing the creation of symbolic links (which is attempted by a dependency of create-guten-block) on a synced folder.
After a long trip down the rabbit hole, I had success by setting SharedFoldersEnableSymlinksCreate: true in the Vagrantfile for my box and running vagrant up as an administrator.

I'm having the exact same problem. On macOS Catalina.
@avb100 : I'm not familiar with Vagrant. Is this something related to a Windows box?
Here's my output:
✔ 1. Creating the plugin directory called →  custom-image-block
⠋ 2. Installing npm packages.../Users/bf/.npm/_npx/23001/lib/node_modules/create-guten-block/index.js:60
	throw err;
	^

Error: Command failed: npm install cgb-scripts --save --save-exact --silent

    at makeError (/Users/bf/.npm/_npx/23001/lib/node_modules/create-guten-block/node_modules/execa/index.js:169:9)
    at /Users/bf/.npm/_npx/23001/lib/node_modules/create-guten-block/node_modules/execa/index.js:274:16
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async /Users/bf/.npm/_npx/23001/lib/node_modules/create-guten-block/app/npmInstallScripts.js:48:3 {
  code: 1,
  stdout: '',
  stderr: '',
  failed: true,
  signal: null,
  cmd: 'npm install cgb-scripts --save --save-exact --silent',
  timedOut: false,
  killed: false
}

My node is at 12.13.1
My nom is at 6.12.1

I'm also having this problem.
Mac OS 10.15.3
node 10.16.3
npm 6.5.0
Here's my output:
✔ 1. Creating the plugin directory called →  radicati-accordion
⠏ 2. Installing npm packages.../Users/noxlady/.npm/_npx/32679/lib/node_modules/create-guten-block/index.js:60
	throw err;
	^

Error: Command failed: npm install cgb-scripts --save --save-exact --silent

    at makeError (/Users/noxlady/.npm/_npx/32679/lib/node_modules/create-guten-block/node_modules/execa/index.js:169:9)
    at Promise.all.then.arr (/Users/noxlady/.npm/_npx/32679/lib/node_modules/create-guten-block/node_modules/execa/index.js:274:16)
    at process._tickCallback (internal/process/next_tick.js:68:7)

Wow, I've fallen down a series of rabbit holes trying to figure this out...

It looks like the problem involves installing cgb-scripts, so I tried to install it outside of create-guten-block. The command npm install cgb-scripts fails with error codes that look like:

$ npm install cgb-scripts
npm WARN deprecated<EMAIL_ADDRESS>This package has been deprecated, please use @wordpress/eslint-plugin or @wordpress/scripts
npm WARN deprecated<EMAIL_ADDRESS>This package has been deprecated, please use @wordpress/eslint-plugin or @wordpress/scripts
npm WARN deprecated<EMAIL_ADDRESS>Deprecated. Please use https://github.com/webpack-contrib/mini-css-extract-plugin
npm WARN deprecated<EMAIL_ADDRESS>Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated<EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm ERR! code EINTEGRITY
npm ERR! sha1-c7Xuyj+rZT49P5Qis0GtQiBdyWU= integrity checksum failed when using sha1: wanted sha1-c7Xuyj+rZT49P5Qis0GtQiBdyWU= but got sha512-gTBHf/fKC0j390N1nuWbhSEdD/9LhOvNWIBya741p6nfghKZNKLqpXuYQMZSLEz9w76IFaScG87s6Py/lwd4Hg== sha1-skgI4K473oZs1le1FkEy83v2Zag=. (277859 bytes)

I've tried changing my npm registry and force clearing my cache, as per reactjs - Installing create-react-app gives npm ERR! shasum check failed and npm ERR! Unexpected end of JSON input while parsing near '...mojOzGIEI2rg0m24Yb5Oq' - Stack Overflow. No dice -- the specific "Unexpected end of JSON input while parsing near" bit changes, but the error is still basically the same :(

I tried updating node (nvm install 12 since I'm using nvm) and that didn't work, and that's when I found out that updating Mac OS Catalina did weird stuff to my receipts, since the error included:

No receipt for 'com.apple.pkg.CLTools_Executables' found at '/'.

No receipt for 'com.apple.pkg.DeveloperToolsCLILeo' found at '/'.

No receipt for 'com.apple.pkg.DeveloperToolsCLI' found at '/'.

Google led me to Is this an Issue with MACOS catalina? · Issue #1927 · nodejs/node-gyp · GitHub, which led me to Installation notes for macOS Catalina (v10.15) and I followed their troubleshooting. Confirmed that I failed both parts of "the acid test", and ended up manually installing XCode Command Line Tools via the Apple developer website. (I tried xcode-select --install and got an error telling me it was already installed and I needed to update via "Software Update" :P)
That fixed my receipts, so then I was able to nvm install 12, which took forever...
So with bated breath, I tried npm install cgb-scripts again... AAAARRGHH -- I'm still getting the same error!
Here's the error log:
2020-02-14T05_37_23_052Z-debug.log
My node is now version 12.16.0 and npm is version 6.13.4
@ahmadawais, is there anything else I can do to try to help you troubleshoot this?

Error: Command failed: npm install cgb-scripts --save --save-exact --silent
have same problem anyone can fix?

Error: Command failed: npm install cgb-scripts --save --save-exact --silent
have same problem anyone can fix?

For anyone looking...

At first delete package-lock.json file and node_modules/ folder.
Open Windows PowerShell as Administrator.
Run npm install --global windows-build-tools
Run the command npm i -g<EMAIL_ADDRESS>After that, go to the project folder and run npm install

Hello,
I had the same error : Error: Command failed: npm install cgb-scripts --save --save-exact --silent
I succeed by install cgb-scripts globally : npm install -g cgb-scripts
(I am on Windows 10 with Linux subsystem Debian)

2021, same exact error on mac os Big sur........ Is this project completely dead, did anybody manage to fix this problem?

Anyone managed to fix this?

On macOS Catalina, using nvm with v14.17.0 node version, it worked for me.
My problem was with the node version of the system v16.2.0 and the incompatibility with node-sass. I hope this helps someone

@evabelpeq You made my day! Works for me too! Thanks for sharing!

This also worked for me as well!

@evabelpeq I change the node v14.17.0 node version, it worked for me. Thanks for sharing!

Sadly the error still persists for me while using node v14.17.0 (npm v6.14.13) via nvm. (Big Sir: 11.6.2 (20G314)) M1 Chip.

Thank you @evabelpeq . I'm on Windows 10. So I installed NVM for Windows.  I than installed and use node.js 14.17.0 and now my package errors are gone.
Many thanks!

Sadly the error still persists for me while using node v14.17.0 (npm v6.14.13) via nvm. (Big Sir: 11.6.2 (20G314)) M1 Chip.

work for me:
MacOs Monterey
Node v14.17.0
Apple M1
#i use n
npm install -g n
n 14.17.0

On macOS Catalina, using nvm with v14.17.0 node version, it worked for me. My problem was with the node version of the system v16.2.0 and the incompatibility with node-sass. I hope this helps someone

-------------worked--------------
windows 11
node version v14.17.0
thanks

I had that same issue on my Ubuntu environment while I had activated the Node version 16.14.2.
When I changed the Node version down to 14.12.0 and I run the command npx create-guten-block my-block it worked without problem.
Hope that helps some of you :)

When I changed the Node version down to 14.12.0 and I run the command npx create-guten-block my-block it worked without problem.

Thanks!

Macos, node 17, didn't  work. downgraded node to 14, just got a different error.
I'm done. I get free software and whatever but the number of posts on this suggests it's quite an issue and worthy of more developer attention. At the risk of getting shouted at, this should be better and i'm done.

Downgrading to node 14 with nvm helped me (Win10 - WSL Debian)

@ahmadawais Thanks for putting together this package. Sorry for all the negativity from other posters. Have you looked into replacing deprecated node-sass with sass?


Add non-goals section documenting should vs expect

This will hopefully reduce the number of issues asking for non-goals of RuboCop RSpec. Addresses what was suggested in https://github.com/rubocop-rspec/rubocop-rspec/issues/587#issuecomment-376343881

@dgollahon any feedback?

Just to be clear: I pinged @dgollahon because he is a native English speaker (I assume).

because he is a native English speaker (I assume)

Yup! 🇺🇸

@sauloperez If you're inclined to go the extra mile, it wouldn't hurt to add an extra bullet point to the contributing guidelines saying they should check if the feature is a non-goal of rubocop-rspec.
Not a requirement though :)

@sauloperez Sorry, but you need to rebase as well, to get the last (required) CircleCI job running. It was added to master after you opened this PR.

cool guys. On it right now.

🎉


Fixes issue 2627: Use cache db for BanManager

Replace file storage with database tables in cache db.

I will add fix for integration failure :
 >>CI: nnode-2_1  | 2021-11-07 21:25:09,63 Warn [agora.common.BanManager] - BanManager: failed to insert whitelisted into cache database: error 19: UNIQUE constraint failed: whitelisted.url


Review task priorities under high system load

When the system load is very high (close to 100%) the scheduling priorities might not pan out optimally. The system data flow should be reviewed and priorities adjusted where necessary.

I already fixed the commander scheduling.

I think its fine according to our current experience.


Mocha 6 fails with pnpm: Cannot find module 'semver'

Prerequisites

[x] Checked that your issue hasn't already been filed by cross-referencing issues with the faq label
[x] Checked next-gen ES issues and syntax problems by using the same environment and/or transpiler configuration without Mocha to ensure it isn't just a feature that actually isn't supported in the environment in question or a bug in your code.
[x] 'Smoke tested' the code to be tested by running it outside the real test suite to get a better sense of whether the problem is in the code under test, your usage of Mocha, or Mocha itself
[x] Ensured that there is no discrepancy between the locally and globally installed versions of Mocha. You can find them with: node node_modules/.bin/mocha --version(Local) and mocha --version(Global). We recommend that you not install Mocha globally.

Description
mocha 6 fails to run under pnpm
Steps to Reproduce

pnpm install mocha
pnpx mocha --version or npx mocha --version

Expected behavior:
6.1.2 is displayed in the console
Actual behavior:
Cannot find module 'semver' is displayed in the console
Reproduces how often:
100%
Versions
6.1.2

The output of mocha --version and node node_modules/.bin/mocha --version:
Cannot find module 'semver'
The output of node --version:
v8.15.1
Your operating system

name and version: Ubuntu 14, Windows 10
architecture (32 or 64-bit): 64, 64

Your shell (e.g., bash, zsh, PowerShell, cmd): bash, Powershell, git bash
Your browser and version (if running browser tests):  N/A
Any third-party Mocha-related modules (and their versions):  N/A
Any code transpiler (e.g., TypeScript, CoffeeScript, Babel) being used (and its version):  N/A

Additional Information
A mocha dependency, node-environment-flags, requires semver, but does not list it as a dependency in package.json.  See issue: boneskull/node-environment-flags#2 and pull request:  boneskull/node-environment-flags#4.

Workaround is to add semver as a dependency of my project.


color only theme changes

requested by darren

I don't think this is really what you're going for in light...


PVRTC compression and decompression code license is missing in generated LICENSE file

I am using Flutter version v1.5.4-hotfix.2.
The LICENSE asset generated by Flutter build (build/app/intermediates/flutter/release/flutter_assets/LICENSE) includes license of PVRTC:
===============================================================================
The PVRTC compression and decompression code is ported from Jeffrey Lam's
PvrTcCompressor:
https://bitbucket.org/jthlim/pvrtccompressor
===============================================================================
There are two issues with this generated output:

The name of the author is incorrect -- should be Jeffrey Lim.
The full body of the license (https://bitbucket.org/jthlim/pvrtccompressor/src/default/LICENSE.TXT) is missing.

Looks like this license comes from the image package, not from Flutter itself.
See https://pub.dev/packages/image and https://github.com/brendan-duncan/image/blob/master/LICENSE

@filiph Could you mark this with "customer: solaris"?

@jason-simmons Thanks! Could you please confirm flutter does not have direct dependency on it? I am going to contact the image owner in the meantime.

https://github.com/brendan-duncan/image/issues/121

Thanks for catching that. I updated the license file.

It is now part of the Flutter licenses so this ticket can be closed


Unable to cf push large jar file with mcafee antiviurs software

when pushing a jar file that has 50k small files cf cli has to extract the jar file, perform resource matching, and zip up for upload.
After running perf when the cf push was generating the resource_match request we observed that cf was only consuming about 3 % cpu and the kernel was consuming about 25%. Further investigation found that the kernel usage was a result of antivirus software that is scanning on reads and writes which means the 50k files get scanned during extraction and during chksum. This is the cause for the delay.
this is impacting a CI pipeline because it takes more than 1 hour to push a single app like this witch does not allow us to perform constant builds
some workarounds we considered:

Disabling the antivirus allows the app to be pushed in just couple minutes.

this is not a valid workaround as per our security policy

Excluding the $TMPDIR form the antivirus scan could help

This will be difficult to implement because we have to modify a lot of existing CI pipeline to use these methods and a lot of jobs are run as all different users.

Deploy a local maven repository to store all the application dependencies and exclude dependencies from the jar file

This is possible however that would mean changing of internal development processes and updating existing applications. This would take a lot of time to implement

Would it be possible to have an option to skip resource matching and unpacking of the jar file?

Hi @randomtask1155
Thanks for those details.
We are about to refactor our push command, and explore what it's doing exactly and why.
As part of that we can look at addressing this issue.
Cheers,
Dies Koper
CF CLI PM

We have a similar issue with our node app which has lot of dependencies ( 17K files together). On some environments, CF push fails at the resource matching step. So having a CLI flag to disable resource matching would be helpful to ensure our node app can be successfully pushed to all CF environments.

@mgadiya what do you mean it's failing at the resource matching step? If resource matching is failing, we should fix it- not introduce a flag to skip it.
Maybe you can open a new issue about that with the CF trace of the failing response and matching request?

@dkoper apologies for the confusion. I meant to say that cf push timed out when it called CC's /resource_match endpoint because it is trying to do the resource match for all the files of our app. We discovered it by looking at CF Trace output.

@mgadiya Please submit a new issue and include that error response (and request, although you can omit the lengthy body). The solution we're exploring for the issue in the issue description will not resolve the issue you raised. Many thanks.

@dkoper Thanks for your response. I created a new issue here - https://github.com/cloudfoundry/cli/issues/1042

Is there an update on this specific issue? The last update on this issue was 11/23/2016 by Dies. It looks like issue #1042 is fixed in the current CLI version 6.23.1, according to that one's latest update but am wondering about this one specifically and whether the previously mentioned 'push command refactor' effort addressed it or not (since the case is still in 'open' status).

@shouah We have started the refactor of push by refactoring the cf app and cf start commands that push orchestrates. push is our biggest command so will take many weeks to complete.
At the same time, we've done some explorations to reduce file I/O when pushing an app, which I believe will resolve this issue. Those will be implemented and evaluated during the refactor of the app upload part of push.
I will update this issue as soon as we have something, even experimental, for you to try and see if it helps with your app in your environment.

@shouah @mgadiya @randomtask1155
We are refactoring the push command to greatly reduce file I/O when resource matching and uploading the app. Although not ready to replace the current push implementation yet, maybe you can give it a go and report here whether it improves your push performance and reduces timeouts?
Use a recent release (e.g. cf CLI 6.30.0) - it has an experimental v2-push command that is not included in cf help output.
This command does not yet support manifest inheritance, promoted ("global") variables and route declarations in the app manifest. Other than that it should be equivalent in usage compared to current push.
Cheers,
Dies Koper
CF CLI PM

Here is the java executable file stats:

56,786,944 bytes with 2,217 directories and 40,580 files
issue is around the 'Binding...' step and 'Uploading...' step taking huge amount of time.

Using 64-bits CLI 6.30.0 on Windows 7 Enterprise 64-bits to push the jar file with --no-start option:

cf push with no AV exclusion = ~21 min
cf v2-push with no AV exclusion = ~4 min
cf push with AV exclusion filter enabled = ~9 min
cf v2-push with AV exclusion filter enabled = ~5 min

It looks like nearly a 700% improvement with standard AV setup between push and v2-push. There doesn't seem to be a major difference in v2-push without AV exclusion or with AV exclusion because it seems that the majority of the time is taken by the network upload operation itself so subject to traffic load.

Thanks @shouah - great feedback!


Autocomplete scrolling bug

Have problems with scrolling when using acutocomplete component:

Open autocomplete from demo:

Try to scroll down:

Try to scroll up:

duplicate of #3219

Closing as dupe of #3219


fix: swaps test and others

Try out this version of Leather — Extension build, Test report

This PR changes to test swaps on mainnet bc we hide swaps on testnet. The broadcast is caught and aborted, so it should be ok. I also just did some clean up of the locators and handled if there happens to be a pending tx (which means we needed to catch the Hiro api post route).

Fixed a few other failing tests here.


Add setting option to restrict IPs Threadfin will listen to

Overall improvement of the source
Add network as a setting category
Add new setting option to restrict access to Webserver through user defined IP addresses

Closing this as it was fixed in 1.1.13


Find_Day_of_a_given_Date.md

Description 📜Find_Day_of_a_given_Date.md
Fixes #8438

Type of change 📝Find_Day_of_a_given_Date.md

[X] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[X] C/CPP

Checklist ✅

[X] I follow Contributing Guidelines & Code of conduct of this project.
[X] I have performed a self-review of my own code or work.
[X] I have commented my code, particularly in hard-to-understand areas.
[X] My changes generates no new warnings.
[X] I'm GWOC'21 contributor

@vasu-1 I have made the necessary changes and added the file link in readme.md . Can u please review if its okay and merge.

can't merge this much of commits

kindly fetch your repo and do change in another saperate branch