Rancher 2.4 browser keeps asking to accept the self-signed certificates

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

Install Rancher 2.4 commit id used: 8a68bd75a
Try Login with Chrome

Result:
The login page will loop asking to accept the certificates
I tried Chrome Incognito mode, but it also keep showing the certificate warning.
Firefox too, I was able to navigate a bit more but then the warning shows after some time. In Privacy mode too.
Other details that may be helpful:

Environment information

Rancher version: 2.4 master-head (02/20/2020) 8a68bd75a
Installation option (single install/HA): single

Workaround is to close the browser entirely and reopen it, it alleviates the issue.

This hasn't been experienced on latest Rancher releases 2.6.x and 2.7.x


Modernize plugin configuration

Here I'm proposing some project configuration update to modernize the plugin configuration.
This is following https://docs.google.com/document/d/1PKYIpPlRVGsBqrz0Ob1Cv3cefOZ5j2xtGZdWs27kLuw/edit#heading=h.7t10u6t7ctab for more details.
This still requires to open a pull request on https://github.com/jenkins-infra/repository-permissions-updater/ to edit the permissions/crowdstrike-security-plugin.yml file and add the
cd:
  enable: true

as described in https://www.jenkins.io/doc/developer/publishing/releasing-cd/#enable-cd-permissions.
One thing: the plugin has 80 potential bugs reported by Spotbugs. It would be great to attend to them as soon as possible.
cc @jshcodes @crwd-etatarevic

[x] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
[x] Ensure that the pull request title represents the desired changelog entry
[x] Please describe what you did
[x] Link to relevant issues in GitHub or Jira
[ ] Link to relevant pull requests, esp. upstream and downstream changes
[ ] Ensure you have provided tests - that demonstrates feature works or fixes the issue

There are other spotbugs fix to add but this is a good start to improve the plugin health.

@crwdsmullz are you working on this plugin? If so, could you please review this PR? Thanks


How to use?

Hello,
I am using Immutables with Javalin in my project so I am trying to use your library to generate OpenAPI schema for my models but I don't know how to use your library. Could you show an example for usage in maven annotation processor?

Hey @macabrus - I'm not familiar with Javalin, but it looks like https://github.com/javalin/javalin-openapi may be better suited for your needs. This library processes annotations like @POST and @Path("/...") on Controller/Resource classes and methods to generate OpenAPI documents - I'm not sure how it could be adapted to handle the Javalin style of generation


Fix pagination when searching karaoke for #

The pagination URLs for karaoke were not URLEncoding the # when searching for #. This PR fixes it.

Technically, yes. When the search param is an empty string, the user will be brought to the karaoke landing page. The ?? "" is only really there because that's the only way I could get swift to stop complaining about the string being optional in the interpolation. If there's a better way to do it, I'm all ears.

I suggest something akin to https://github.com/jocosocial/swiftarr/blob/31052eb4f71d4bf4a0b471be803a460190ea593e/Sources/App/configure.swift#L152
IIRC the guard test has to be Optional but you can do multiple conditions hence the second check for an empty sting here.

After a bit more evaluation, I think I'd like to keep  the ?? "". In the previous implementation, searchStr was allowed to be an empty string, interpolated into the URL. So I think it's fine.

Bit late to this conversation, but in the case of String.addingPercentEncoding(), that function only fails to encode when given very strange non-unicode Strings as input. If someone manages to type such a string into the search field, getting a results page without the search is fine.


Error in Unity 5.2.1p1

When I tried to run the demo in Unity 5.2.1p1 in Unity Editor, it said:
UNetWeaver error: Exception :System.ArgumentException: An element with the same key already exists in the dictionary.
at System.Collections.Generic.Dictionary2[System.UInt32,System.UInt32].Add (UInt32 key, UInt32 value) [0x0007e] in /Users/builduser/buildslave/mono-runtime-and-classlibs/build/mcs/class/corlib/System.Collections.Generic/Dictionary.cs:404    at Mono.Cecil.MetadataSystem.SetReverseNestedTypeMapping (UInt32 nested, UInt32 declaring) [0x00000] in <filename unknown>:0    at Mono.Cecil.MetadataReader.AddNestedMapping (UInt32 declaring, UInt32 nested) [0x00000] in <filename unknown>:0    at Mono.Cecil.MetadataReader.InitializeNestedTypes () [0x00000] in <filename unknown>:0    at Mono.Cecil.MetadataReader.InitializeTypeDefinitions () [0x00000] in <filename unknown>:0    at Mono.Cecil.MetadataReader.ReadTypes () [0x00000] in <filename unknown>:0    at Mono.Cecil.ModuleDefinition.<get_Types>b__8 (Mono.Cecil.ModuleDefinition _, Mono.Cecil.MetadataReader reader) [0x00000] in <filename unknown>:0    at Mono.Cecil.ModuleDefinition.Read[ModuleDefinition,TypeDefinitionCollection] (Mono.Cecil.TypeDefinitionCollection& variable, Mono.Cecil.ModuleDefinition item, System.Func3 read) [0x00000] in :0
at Mono.Cecil.ModuleDefinition.get_Types () [0x00000] in :0
at Unity.UNetWeaver.Weaver.Weave (System.String assName, IEnumerable1 dependencies, IAssemblyResolver assemblyResolver, System.String unityEngineDLLPath, System.String unityUNetDLLPath, System.String outputDir) [0x0006a] in /Users/builduser/buildslave/unity/build/Extensions/Networking/Weaver/UNetWeaver.cs:1546    at Unity.UNetWeaver.Weaver.WeaveAssemblies (IEnumerable1 assemblies, IEnumerable1 dependencies, IAssemblyResolver assemblyResolver, System.String outputDir, System.String unityEngineDLLPath, System.String unityUNetDLLPath) [0x00062] in /Users/builduser/buildslave/unity/build/Extensions/Networking/Weaver/UNetWeaver.cs:1637  UnityEngine.Debug:LogError(Object) Unity.UNetWeaver.Log:Error(String) (at /Users/builduser/buildslave/unity/build/Extensions/Networking/Weaver/Program.cs:20) Unity.UNetWeaver.Weaver:WeaveAssemblies(IEnumerable1, IEnumerable1, IAssemblyResolver, String, String, String) (at /Users/builduser/buildslave/unity/build/Extensions/Networking/Weaver/UNetWeaver.cs:1644) Unity.UNetWeaver.Program:Process(String, String, String, String[], String[], IAssemblyResolver, Action1, Action`1) (at /Users/builduser/buildslave/unity/build/Extensions/Networking/Weaver/Program.cs:34)
UnityEditor.Scripting.Serialization.Weaver:WeaveUnetFromEditor(String, String, String, String, Boolean)
and
Failure generating network code.
UnityEditor.Scripting.Serialization.Weaver:WeaveUnetFromEditor(String, String, String, String, Boolean)
I can run it in 5.1.3 in Unity Editor perfectly without a problem.

I had tried, but there is nothing problem.

You had to download from here:
http://unity3d.com/unity/qa/patch-releases
Unity 5.2.1p1 - Unity 5.2.1p2. It's a pre-release feature before Unity 5.2.2 release. It included some convenience feature like build & run for XCode 7. You can wait until 5.2.2 come out to fix if you want. Just let you know.

@pangweiwei ping in case if you did not see it.

I found that you put slua/script folder to "Standard Assets" folder let unity generate "Assembly-CSharp-firstpass.dll", UNetWeaver may be need this dll to generate RPC code, if so unity not report error you posted.
I don't know whether it's a bug of unity or not.

refer "http://wiki.unity3d.com/index.php/Special_Folder_Names_in_your_Assets_Folder"

Remove add(typeof(List<int>), "ListInt") in CustomExport.cs can avoid this issue.
The reason is unknow.

Also you should remove this file if exist: Lua_System_Collections_Generic_List_1_int.cs

我测试发现一个文件里，self里的方法被调用种类达到19种，就会报这个错。

yongkangchen, does this link help you? http://forum.unity3d.com/threads/unity-5-1-unetweaver-errors.332268/
The forum post says "This is a bug (701313) caused by UNetWeaver processing Editor scripts when it should not be. The fix for this will be in an upcoming patch release (probably 5.1p2 as 5.1p1 is in 2 days)."
Although it says the fix will be with 5.1p2, I still have the same bug with 5.3f1.

I had pushed a fix


Doesn't work for dashboards

I find when I try to create a short URL for a dashboard I just end up with the normal URL - (which is a bummer because it has a GUID attached to it). It would be awesome it there was some way to shorten the URL like with the other areas and to add the dashboard name (separated by hyphens) as the end part of the URL

Yep, dashboards aren't supported right now. Not sure if you can access a dashboard by name though?


Add support for skipping validation annotations

Trying to get this generator to work on Android and needed a way to turn off the validation annotations since javax.validation and jakarta.validation aren't supported. Could also add some validations from the androidx.annotation package instead, if you'd prefer that approach.
Let me know if this seems acceptable

LGTM, I'll try and cut you a new release later today


Tag new release

Hi @gajus,
I'm using this amazing library to make project that uses the svg elements. The PR that fixes bugs related with this kind of elements has been merged months ago, but it does not exist any tag that contains the #23 PR.
So, can you tag a new release that allows to use the last merged improvements? :)

I haven't used Composer for couple of years now. Is adding a git tag sufficient to create a new release?

@gajus No, you have to add a new Git tag and then, you have to click Update button in Packagist. https://packagist.org/packages/gajus/dindent

I've created two tags:

https://github.com/gajus/dindent/tree/2.3.0
https://github.com/gajus/dindent/tree/v2.3.0

and hit Update, but nothing is changing. Anything else I should do?

I am guessing I need to update https://github.com/gajus/dindent/blob/master/composer.json#L3.

Nop. Even after updating the git tags and updating the composer.json, the packagist.org does not pick up the change.

Sorry,
Composer does not use the version directive to determine the current tag. So, you can safely remove this directive from composer.json because it's useless in its workflow.
To make work, only you have to tag a new git release in GitHub and hit the packagist Update button. You do not need to do anything in your codebase to publish a new release in Packagist.

@gajus is it something that can I help you?

@gajus ping

@gajus No, you have to add a new Git tag and then, you have to click Update button in Packagist. https://packagist.org/packages/gajus/dindent

I have already done that and Packagist does not pick up the new tag. There isn't much else I can do.

FIY, you can use the zip directly from github as a workaround:
composer.json:
...
"require" : {
	"gajus/dindent" : "2.3.0",
},
"repositories" : [{
	"type" : "package",
	"package" : {
		"name" : "gajus/dindent",
		"version" : "2.3.0",
		"dist" : {
			"url" : "https://github.com/gajus/dindent/archive/2.3.0.zip",
			"type" : "zip"
		}
	}
}]
...

I have already done that and Packagist does not pick up the new tag. There isn't much else I can do.
Packagist does not provide any debugging information in response to the Update the action. The network request results in 200.

That's because when you check contents of composer.json for tags v2.3.0 and 2.3.0, the version is still 2.0.2:
https://github.com/gajus/dindent/blob/df486a42dc092105100a48a6c8ae7aa7db1aa61a/composer.json#L3
Those tags get ignored as the version in composer.json doesn't match with the tag:

(I set this GitHub repository as a VCS repository in composer.json before running that command)


Move all decode routines to _test.

This was supposed to be in the pr-pfx-encode PR, but I failed to properly rebase my changes into the PR.  This PR includes the following changes.

Remove all top-level decode methods.
Move lower level decode methods to _test files to further discourage their use.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-k8s-23-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1614

Questions ?
Please refer to the Backport tool documentation


Update JudgementCut.java

A crash is happened by this code,so I had fixed a code that cause it.
Crash-log:https://mclo.gs/diCqh79

Thanks


Paragraph style not functioning

Good Day,
I have looked through the documentation and the example apps and can not get the paragraphSpacingBefore to work in a UILabel.
I have the following style defined:
    let li = Style {
        $0.paragraphSpacingBefore = textStyle.font.lineHeight / 2
        $0.firstLineHeadIndent = textStyle.font.lineHeight
        $0.headIndent = textStyle.font.lineHeight * 1.71
    }

But the list is displayed on the same line as the rest of the text and not on a new line.
I am using the latest 3.0.1 release

It seems you're trying to use the font property of your UI control (textStyle I suppose) inside the style, but probably it's not the same of the font inside the li style.
I've tried with this code where the font is defined externally as reference and it seems works fine.
let usedFont = UIFont.boldSystemFont(ofSize: 15)
let headerStyle = Style {
            $0.font = usedFont
            $0.paragraphSpacingBefore = usedFont.lineHeight / 2
            $0.firstLineHeadIndent = usedFont.lineHeight
            $0.headIndent = usedFont.lineHeight * 1.71
}


Fix golint warnings.

Signed-off-by: ChengTiesheng<EMAIL_ADDRESS>

Hi @jonboulle, I have fixed the golint warnings in CNI project, can you review it, thanks:-)

Thanks! I've commented on a handful of things -- typos and a moderate misunderstanding of a type. I think we'll be good to go once those are fixed up.

@squaremo, thanks so much for your review, and I have fixed the errors:-)

Hi, @squaremo @jonboulle, I've added golint check in test script. Looking forward to your review:-)

@jonboulle What do you think, does CNI like golint? I'll merge if so.

took a first pass...
overall, I highly approve of documenting a lot of these things, but I'm not 100% sold on mandating golint everywhere, seems like some silly false positives..

@jonboulle, thanks so much for your careful review, and I have fixed the bugs.
Agree, sometimes, golint has false positives, and it is just a reminder for the programmer, on this occasion, we can change our coding style to bypass the golint warnings.

Took another pass - the PR also needs a rebase.
Thanks for your patience :-)

@jonboulle Thanks so much for your kind and patient review, I have fixed it:-)

Thanks @ChengTiesheng for your hard work. Your PR has collected quite an amount of commits, please squash them before we can merge this.

Hi @steveeJ , I make a new PR to squash the commits: https://github.com/appc/cni/pull/136 , thanks for your reminder.
This PR will be closed later:)

Please refer to the new PR:
Fix golint warnings. #136


Add initial gnn pipeline

Disabled isort --recursive in  .githooks/pre-commit for now as causing error.
See https://github.com/point-cloud-radar/bird-cloud-gnn/issues/20

Yes.
On Wed, Mar 1, 2023, 16:03 Olga Lyashevska @.***> wrote:

Thanks Abel. Can this be merged? I will do black formatting in a separate
commit.
—
Reply to this email directly, view it on GitHub
https://github.com/point-cloud-radar/bird-cloud-gnn/pull/22#issuecomment-1450299638,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIE5UD2ZGK7JTOUZULGAXLWZ5QNTANCNFSM6AAAAAAU3NSO3M
.
You are receiving this because you commented.Message ID:
@.***>

Fixes https://github.com/point-cloud-radar/bird-cloud-gnn/issues/9


working MVP

Working MVP code.
https://drive.google.com/file/d/1vSdDrYJQ7nVTDfEEVq7X_bg6d97PV68Q/view?usp=sharing

Changes are resolved in MVP-extension pull request.

I've noticed you resolving a lot of comments without actually fixing them. In previous PR's as well. Please correct this behavior, as it's leading to a lot of extra work on my end to double check comments you've resolved.

Also just noticed that you don't have approval from your peers yet. Please do not add me and Jess as reviewers until they approve.


[CI] Add node comparison badge

Adds a badge to README that shows what percentage of games supported by node-gamedig are supported by us (it doesn't check whether we have a game but use the wrong name for it: it works by checking whether the game ID from node-gamedig exists in are game definitions file). And CI that should automatically update this badge.

Very cool little addition, thanks :D

Ooops, please rebase to satisfy CI.


requires android.permission.ACCESS_COARSE_LOCATION

it seems missing
02-04 02:17:55.281  1791  1841 W ActivityManager: Permission Denial: Accessing service ComponentInfo{org.microg.nlp.backend.apple/org.microg.nlp.backend.apple.BackendService} from pid=24299, uid=10123 requires android.permission.ACCESS_COARSE_LOCATION
android 6.0

I am also experiencing this on CM 13 (which is based on Android 6.0).

i can see this is fixed in source, hope there will be release or pre-release soon

Have you tried the latest version?


"muted" config option seems to be ignored

Expected behaviour
When the "muted" config option is set to true the player should be muted
Actual behaviour
The player ist not muted
Steps to reproduce
Set player to muted via config options
Environment

Browser: Tested in latest Safari, Chrome & FF

Link to where the bug is happening
https://codepen.io/anon/pen/MMZrxO

Got it working.
Apparently you have to disable the storage option - makes somehow sense, but this should definitely be mentioned in the documentation.
One could also argue that storage should be ignored if the muted option is explicitly set to true.

@danielvonmitschke I just stumbled upon this and I think it would make more sense to use user settings if config params are undefined. I have a player with autoplay and only play/pause and progress controls. It took me a while to figure out why the audio wasn't playing. When I re-enabled all the controls (including mute) I realized the player was keeping the mute even though I explicitly set autoplay: true, muted: false, and volume: 1.

Tested in latest Chrome (84), this issue also occurs if you set the attribute "muted" in the HTML video tag as well, and it is solved by the same solution setting the option storage: {enabled: false}

As a result of this, autoplay doesn't work; muted must be true.
Adding the Chrome error here for search engine indexing / Github error searching as it wasn't obvious where in the issues to find a solution:
DOMException: play() failed because the user didn't interact with the document first.

https://github.com/sampotts/plyr/issues/1495#issuecomment-659735226
this works, thanks!
but still with default parameters, muted: true not working..


Empty subsections of plot controls should not be displayed?

An example currently is HistogramVisualization but this may change when https://github.com/VEuPathDB/web-eda/issues/43 is done.
My preference is to plan ahead for future circs when control sections are empty, however.  Remove question tag if you agree!
Implementation options have already been discussed/tested here
https://github.com/VEuPathDB/web-components/pull/87#discussion_r610698692

This is solved if you use the new <LabelledGroup> widget/component.


Performance evaluation and profiling

Description
Evaluate the performance of Java, GO and the core.
Profile bottlenecks.
Checklist

[ ] Task item 1
[ ] Task item 2
[ ] Task item 3

Additional Notes
No response

EE is unknown. Depends on the initial status assessment which will require running benchmarks for all the supported bindings and analyze the results


Support translation

Would be nice too if we can define what language to use when constructing satpam.
I'll do it later if approved.

I think it would be better to provide a way to specify custom error message per validation. I'm open for feedback though

I'm closing this since now we can set custom validation messages per satpam instance or globally.
https://github.com/sendyhalim/satpam/pull/10


Feature request: Expose the config

I think it would be great to have a function .getConfig() that gives the actual config ran by puppeteer.
That's useful to detect headless mode and execute different function based on that.
I posted this question on SO : https://stackoverflow.com/questions/51845207/how-do-i-get-actual-config-in-puppeteer and there is an answer but in my case (and I think a lot of people do it this way), I have multiple files for the tests, so having a function to retrieve the config would be useful.

Why isn't browser.process().spawnargs enough?

@HRK44 ah, yes, I'd use raw protocol (see CDPSession) and call Browser.getBrowserCommandLine method.
Is this good enough?

@aslushnikov I managed to retrieve the config through the CDPSession, thanks for your help !
What do you think about adding a more 'streamlined' function .getConfig() or .getSpawnArgs() ?

@HRK44 this looks like a very exotic scenario. Can you share your usecase? How come you don't know if the instance you connect to is headless or not?

@aslushnikov I need this information in my test files, a simple example is :

when I use the .type function, if it is running with headless: true, I don't want any delay. Else, add some { delay: 200 }.

Note that this is just for the 'headless' case but maybe other people would use other configurations params.
Also my connection is done is some other file than my test files (I found this file structure in some official docs if I recall correctly), so in my test file I'm not aware of the configuration used to connect - unless using the code in the previous comment via getBrowserCommandLine.

@HRK44 I'm still not sure I follow - aren't you in control how's the chrome browser is launched?

@aslushnikov I am, I manually change the config passed to the .launch({headless: true}) function before running some tests. But the .launch({headless: true}) or .connect() are in some setup files and the tests in their own folder - which is the structure described in most of the docs/tutorials online.
I guess I could extract the config in a file and import it where I need it, but my first thought was to find an existing API retrieving me this config.

I guess I could extract the config in a file and import it where I need it, but my first thought was to find an existing API retrieving me this config.

@HRK44 I see, thanks for the explanation. This would be the right thing to do here; you might have many more properties in your config that are unrelated to the chrome headless/headful mode.
I don't think we should add a designated top-level API to fetch browser command-line unless there's a more convincing usecase; the posted workaround using raw devtools protocol should satisfy most of the occasional needs here.


Camera turned off default if we have user.UserName and RoomName by default

We have already a room name and a user name (external) and we want to reuse them in Twilio app. We want to skip a step by entering userName and room name and we want to start from the second screen:

With passing user name and room name we're skipping the first step, but we don't ask permission for the camera (by default) in this case. We're asking only for microphone permission.
We need to use the camera by default ( and request camera permission by default ).
To Reproduce
Steps to reproduce the behavior:

Use mock user.displayName and roomName (pass it in PreJoinScreens.tsx)
Open app, skip the first step and see the screen with choosing devices (turn on\off camera, turn on\off microphone).

Expected behavior
Permissions for camera and microphone were requested, the camera turned on by default.
Current behavior
Permissions requested only for the microphone. The camera turned off by default.
Screenshots
Case 1 [Problem]
Used mocked user.displayName and URLRoomName
No request for Camera permissions:

Case 2 [Ok]
Used default code, displayName and roomName entered by hand in the 1st screen
Permission for camera was requested:

Environment:

OS: Windows 10
Browser: Chrome Version 88.0.4324.150 (Official Build) (64-bit)
App Version: 0.2.1
Twilio-video: 2.9.0
Node.js version: 14.15.1

Thanks for the detailed bug report @artem-gorokhovskii!
I've seen this issue myself - and I merged in a fix for it in a previous pull request: #401
Looks like you are on version 0.2.1 of the app, and the fix is in version 0.2.2. Can you please try using the newer version of the app to see if it resolves the issue for you?

@timmydoza  thank you for your response.
As I can see - currently we have only 0.2.2-prerelease tag (which was created on Dec 8, 2020).
Could you please say when you're going to create release 0.2.2?

Hey @artem-gorokhovskii!
Sorry about that. Looks like I never made a release for 0.2.2. I created one today: https://github.com/twilio/twilio-video-app-react/releases/tag/v0.2.2
I hope it does the trick for you!

@timmydoza thanks for response!
I checked it in 0.2.3 version and it asks for camera permission also [OK].
Thank you!

Didn't reproduce in 0.2.3


How to use prometheus-postgres-adapter to connect prometheus to RDS PostgresSQL?

I am using prometheus-operator in Kubernetes, and am currently using EBS as a backing store. However I would like to move all prometheus data to Amazon RDS PostgresSQL. Any ideas how to do it? The examples given in the repo landing page seems to assume we are running the database ourselves.

@Sriharivignesh Amazon RDS is currently unsupported as we rely on extensions being present in PostgreSQL that aren't yet available on RDS. This might change in the future.

bummer

@erimatnor besides filing an issue asking for support in RDS of pg_prometheus, are there any other things we can do to help make this happen?

@erimatnor has there been any movement on this?

@Sriharivignesh Amazon RDS is currently unsupported as we rely on extensions being present in PostgreSQL that aren't yet available on RDS. This might change in the future.

which extensions?

As far as I've read in the documentation of CoreOS/prometheus-operator, they are recommending the TimescaleDB extension. That one is requested for two years now and I don't think that it'll come. AWS has announced their own timeseries database, why should they support another one then?


Updated yum -y install yum-utils to yum -y upgrade

Docker requires more updated libraries than yum-utils. I've tested yum-utils in a new Virtual Machine without updating any libs, and couldn't get docker working. For new environments this is a better command and for any environment.

Proposed changes

Unreleased project version (optional)

Related issues (optional)

closing this, as I don't think this change is needed per my comment above


Add additional HashEngine types

Currently we are using a type alias for a few of the hash engines.
Type alias' allow for potential mixing of types, a struct can better serve our users with not much additional complexity or maintenance burden.

As preparation add const constructors where possible to hash engines (excl. HmacEngine).
Add a sha256d::HashEngine struct
Add a hash160::HashEngine struct

If this goes in we can improve the sha256t::HashEngine in a similar manner.

I'd prefer to leave it till #2918 please.


Add IP SAN to the swarm-node certificate

The swarm-node.crt certificate under /var/lib/docker/swarm/certificates is created on a per-node basis. Now that each node can be uniquely represented by an IP in info.Swarm.NodeAddress, adding that as an IP SAN to these certificates would enable users with access to these certificates to reuse them in other contexts.
One example use case would be to establish mutual TLS authentication between applications running on top of swarm-mode nodes, effectively reusing the trusted channel established by swarm.

This sounds like excessive coupling. I don't see a good reason to couple the IP and the certificate, as it prevents one from changing the IP without changing the certificate. It also requires the node to know its IP at CSR time. The assertion that IP can provide a unique identity is also a poor assumption. We really want to avoid coupling identity to IP as the model is fragile and inflexible.
Could specify the actual use cases for existing certificate?
cc @diogomonica

IPs are irrelevant. You can just do what we do, and validate that this is indeed a valid node by simply verifying the DNS:swarm-worker as the ServerName, or (and) that this is indeed the right node, by verifying the CN=6zxfw4xa1g1lys5orfktyi6ur

The use case is that we'd like to use that cert as a server cert against a docker CLI client which uses another cert signed by the external CA used in swarmkit. In that case it's not possible to hack together the client-side certificate verification logic.
I understand that this is excessive coupling for swarmkit, I was just hoping for a silver bullet that would reduce system complexity for software that sit on top of swarm-mode, as there is already a trusted channel in place. Without the IP SAN, the alternative is passing CA Certs as environment variables in service definitions to perform CSR over mTLS across nodes.

Can you try hacking the server-name component of it? Connecting to swarm-worker or the NodeID? Change the DNS entry to point to the correct IP.
echo <IP_ADDRESS> swarm-worker >> /etc/hosts
Then connect to swarm-worker?

Connecting to NodeID does not work, but setting the /etc/hosts entry for swarm-worker does work for non-managers. Setting it for swarm-ca seems to work in the general case. Thanks for the help, but it looks like using an external CA is a simpler solution at this point.

I don't see why connecting to the NodeID wouldn't work. The client should try the CN first.
You can also connect to managers by connecting to swarm-manager

Apparently the client does not try the CN first:
An error occurred trying to connect: Get https://eicgzr4i2qslgad8ipm2max4e:12376/v1.24/info: x509: certificate is valid for swarm-manager, swarm-ca, not eicgzr4i2qslgad8ipm2max4e
The cert does have the correct CN:
  Subject:
    CN:eicgzr4i2qslgad8ipm2max4e
    ID:1d48b2df4060a0afc4ba583e0b84f596a4bf03ed
    O:[33b2zcsw5oe5619qtv212tayp]
    OU:[swarm-manager]
    Serial:78d5c98036fd59fb6b96dd6e4a04d6f6f98028df
    Valid between 2016-07-27 21:21:00 +0000 UTC and 2016-10-25 21:21:00 +0000 UTC (VALID)
    SANs: [swarm-manager swarm-ca]

Thanks again for all your help!

Do we need to put the nodeID in the SAN?

Yup. @alexmavr mind opening an issue and assign it to me? Thanks!


Unable to Build

I have set everything up as your instructions state to.  However when I attempt to build I am getting the following error:
The terminal process terminated with exit code: 2

Terminal will be reused by tasks, press any key to close it.

Under the Problems tab I see this
A fatal error occurred. Error checking has been disabled, except for simple syntax problems.

asconfig.json
{
	"config": "flex",
	"compilerOptions": {
		"output": "bin/manufacturer.swf"
	},
	"files":
	[
		"./manufacturer.mxml"
	]
}

settings
"nextgenas.java": "/usr/local/bin/java",
"nextgenas.sdk.framework": "/Applications/Adobe Flash Builder 4.7/sdks/3.6.0"

Any assistance would be appreciated as I cannot seem to get Flash Builder to run without locking up on my system so it is completely unusable.  I would love for the ability to build using vs-code
Building the project works fine in Flash Builder, however editing files in Flash Builder leads to the application hanging so currently I am editing in VSCode and building in Flash Builder, would be nice to get this to work in VSCode so I could just blow away Flash Builder.

Is it error after running adt ? if yes, error 2 description is:
2 | Usage error | Check the command-line arguments for errors
Check Terminal lines when running build.

Could you try moving the source code, like manufacturer.mxml, into a sub-folder like src? Maybe it doesn't like your code in the root folder like that.

Unfortunately the project is rather large and poorly coded by a previous developer it would take quite a bit of effort to do what you requested.  Is it possible to provide the path somewhere so that it knows to check the root project and not /src?

You could try adding "." to the source-path compiler option. I don't know if it will work for sure, but it's worth a try.
You should also double check that asconfig.json is in the root and not somewhere like .vscode/. Sometimes, people accidentally put it there.

The *.mxml file with <s:Application> or <mx:Application> at its root is your main class. That's the file that you want to put into the files section of asconfig.json.

Perfect that is what I was thinking and that is how I have it setup.  I cannot seem to figure out how to see the actual build command in Flash Builder since there is no terminal component and trying to install one has proven to be difficult since the adobe repo cannot be read.  I am guessing because it is not supported software anymore.
Any other ideas how I can either see more errors or how I can get this to compile through using vscode?

Ahhh so I went through all the warning output and saw one specific Error line: Error: unable to resolve 'images/import_export_outlook.gif' for transcoding I fixed the path to this and building is now working properly :)
Thanks for all of your assistance on this issue.

If you ever want to see exactly whwich compiler options Flash Builder is using, you can add the dump-config compiler option. It will create a config file that can even be passed to the command line compiler with load-config.
-dump-config=my-dumped-config.xml

out of curiosity is there anyway to make your plugin open the html page for the build in the browser automatically?

See the **
Build automatically before debugging** section in Debug a SWF embedded in HTML with Visual Studio Code. It's kind of the opposite idea. You tell VSCode to debug (which launches the HTML file in the browser), but preLuanchTask tells it will build first.

The only issue i am seeing with that is I get the following error
User defined identifiers are deprecated. For custom task used the name as a reference and for tasks provided by extensions use their defined task identifier.

I'm not seeing that error in VSCode 1.27.2. Strange!

ah I am using insiders so that might be why.  it may be something that is coming soon.

Yeah, it's probably a change in Insider's. It sounds like they're going to let me define an identifier in the extension that you can reference in launch.json without also adding it to tasks.json manually. That should be a good improvement!

I assume there is no way to launch a debug without hitting the green arrow?  I would like to hit something like Command+Shift+B (or D) and just have it build and open.  Currently I have to click the green arrow and it will build and open but it requires an extra click after hitting Command+Shift+D

I will have to look into how to use F5 as fn-F5 does not appear to work and if I click F5 it dims my backlit keyboard on mac.
If I run your quick debugger builds then it compiles once and then runs the compile again and debugs so it does open but it requires 2 compiles.

You need to remove the preLaunchTask when using the quick compile & debug.

I should have mentioned that I tried that, all that happens is that it builds the project but does not launch in the browser.

What I have found is that if I close Code and then reopen it and run the Quick Compile it does in-fact compile and open a browser tab for me.  However when I close that tab and run quick compile a second time it does not open in the browser.


Add no_avx2 to FAISS vector store

Add no_avx2 to FAISS vector store
This PR adds the no_avx2 argument and FAISS_NO_AVX2 environment variable to dependable_faiss_import function to not load FAISS vector store with AVX2 optimization.
This option comes in handy when the developer wants to save the vector store to a file and load it on somewhere else. Most modern CPUs have AVX2 optimization but there are situations where the hardware is old, the faiss-cpu pypi package is not compiled with AVX2 flag or this feature is disabled for some reason.
I encountered this issue on a PaaS where FAISS pickle and database files created by save_index in Colab could not be loaded inside the Docker containers due to the platform not supporting AVX2.
@dev2049

lgtm, thanks @AliMirlou!

fixed lint and merged in #4895!

@dev2049 Too bad though that my name didn't make it to the releases 😅

Can I ask to become a collaborator? I'm deeply involved into LangChain now and I like to contribute more.

We're really trying to keep the collaborator team small and tight-knit at the moment, so we're only considering folks who have made a good number of contributions. Definitely open to it as time goes on, but want to work with you some more first.
But we really do appreciate contributions from anyone and everyone and will do our best to review asap!


vsphere: Add command line argument checking

Fixes #415
Signed-off-by: Cathy Avery<EMAIL_ADDRESS>

Thanks! IIUC you can have the same result by simply passing these vars to the test_vars function here (and if datacenter & datastore are mandatory i'd also remove them from being passed as "optionals" Having said that, i think checking these in the code would also make sense but only if there's a way to make it more cloud-provider generic

OK accidentally closed the PR.
@snir911
If I add all of these to test_vars then they become mandatory? What happens if they are not included meaning what kind of error is seen?
The code is generic for all cloud providers. if hypProvider == "vsphere" . Each provider can add their own checking section. If you notice all of main.go provides this type of customization per specific provider. However I can move all the missing stuff within the  if hypProvider == "vsphere" brackets as that is what vpshere cares about. Or each can call a separate checking function

@caavery @snir911 does it make sense to do the check here - https://github.com/confidential-containers/cloud-api-adaptor/blob/staging/cmd/parse.go#L11 ?

@snir911 @bpradipt
It does except for I could not check these values until after
defaultToEnv(&vspherecfg.UserName, "GOVC_USERNAME")
defaultToEnv(&vspherecfg.Password, "GOVC_PASSWORD")

@caavery it would not even start the cloud-api-adaptor (container will fail to start with var not set error


ref(draft): reduce code duplication setting up kube client and config

@michelleN,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

Codecov Report

Merging #305 into master will increase coverage by 0.1%.
The diff coverage is 0%.

@@           Coverage Diff            @@
##           master    #305     +/-   ##
========================================
+ Coverage    29.5%   29.6%   +0.1%
========================================
  Files          30      30
  Lines        1871    1871
========================================
+ Hits          552     554      +2
+ Misses       1240    1238      -2
  Partials       79      79

Impacted Files
Coverage Δ

cmd/draft/draft.go
7.76% <0%> (ø)
:arrow_up:

pkg/linguist/linguist.go
34.61% <0%> (+1.28%)
:arrow_up:

Continue to review full report at Codecov.

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


Change My Account Settings Button not in right state

When logged in as a server admin, if you go to "My Account" the button defaults to white. If you select to change email address it stays white. if you select to "Change My Password To" it stays white as well. However if you select to change "My Description" it turns grey, whats you type in this field it turns white again. Seems that they all should stay grey untill a change is made.

This is better in 2.11.1, but still not quite right. Will make it perfect in 2.11.2, maybe.

I think this is fixed for real now in master... maybe


Error when click breadcrumb of BREAD edit page

Version information

Laravel: v5.5
Voyager: v1.1
PHP: 7.1.0
Database: [mysql] [5.7.16]

Description

Error will display when click "Pages" in breadcrumb of BREAD edit page.
Steps To Reproduce
Steps to reproduce the behavior:

Login to admin backend.
Go to 'Tools' -> 'BREAD'.
Click on 'Pages' in breadcrumb of Edit 'Pages'
See error
'Symfony \ Component \ HttpKernel \ Exception \ MethodNotAllowedHttpException
No message'

Expected behavior
No error display
Screenshots
If applicable, add screenshots to help explain your problem.

Click here

After click it will show error.

This looks like a duplicate of https://github.com/the-control-group/voyager/issues/3434


Feeling helpless...

:joy: feeling helpless.

😄 damn, would love to be able to fix this issue with code.

Did you catch the point which make me helpless?
The issue can be fixed by update the map data :joy:

Are you referring to the fact that the label "Republic of China" is being shown next to the island of Taiwan?

More of a political issue....
Just go ahead and edit the OSM data, as I don't think there is anything that can be done within this project...

Just go ahead and edit the OSM data, as I don't think there is anything that can be done within this project...

First of all, there's plenty of discussion in the OSM community around politically debated borders & states, not only in China. Please make sure you comply with the conventions the OSM community has decided on, specifically with those regarding PRC/ROC.
A long-term solution might be to do it like Google Maps does it: show different maps, depending on where you access them from.

Sorry for this political issue.

I'm not asking you to apologise for this issue, just not to out-of-the-blue edit OpenStreetMap. 😉


How To: Build a JABOD

Create a new page that outlines the creation of a "Just A Box Of Dirt" style forge. Include pictures and videos where possible.

fixed with #23


Restore "Open in modelviewer" link to model preview modal.

I've never tried to create a second pull request while one is still active, and when I committed the second bunch of changes (to add a menu link to keyinfo), it just added it to my open pull request. I hope that's ok :/
It looks like every html page has its own copy of the menu, so I had to modify all of them.


Afos/test strategy

A dependency is missing in pyproject.toml used for tests
You should add it manually or with poetry

Oh I see the problem, since the group is named tests pytest collect the files in it to run tests (which should not be the case)


SyntaxWarning Nautobot-server migrate

Environment
*Ubuntu Server 22.04 (Jammy)
*postgreSQL 14.4

Python version: 3.10.4
Nautobot version: 1.3.9

Steps to Reproduce

Install dependencies
Run installation up until Nautobot-server migrate

Expected Behavior

Observed Behavior

@Jpickle779 This seems to be throwing an error around the configuration. Can you provide a sanitized config?

Unable to reproduce.


Add text/image into Polygon

Hello,
I wanted to write text/image into polygon, but I think it is not now possible.
Could you provide some feature to do this?

I don't have a plan to this.
Because native google maps API does not support it.


Fix build issue on OSX

NOTE:
I couldn't figure out why this workaround works like a charm...

Fix #64


JP injection

With GL injection patched. Is JP injection possible?

yes

Is it possible to inject with this tool in jp?

I just answered the same question earlier from you.

Thank you very much. I works.


Update Mojo to v0.5.0

Fixed error happen on run with Mojo v0.5.0:
$ mojo -v
mojo 0.5.0 (6e50a738)
$ mojo llama2.mojo stories15M.bin -s 100 -n 256 -t 0.5 -i "Mojo is a language"
./llama2.mojo/read/__init__.mojo:99:24: error: 'DTypePointer[ui8]' value has no attribute 'as_scalar_pointer'
            buffer.data.as_scalar_pointer(), sizeof[UInt8](), BUF_SIZE, self.handle
            ~~~~~~~~~~~^~~~~~~~~~~~~~~~~~
mojo: error: failed to parse the provided Mojo

Thanks @camegone for taking time to add support for 050. We just had another PR that removes dependency on read module. I merged it just now, so you should be able to run inference safely on 0.5.0


Revert "Enable database native tests"

Reverts quarkus-qe/quarkus-test-framework#714
We are building native executable and then running DEV mode test. The tests we are running has absolutely nothing to do with a native mode, the PR doesn't actually run database tests in native mode as it claims (doesn't use native executable) and we should revert it as it waste running time and resources.

hey @gtroitsk , just fyi - that's not a criticism, this one is easy to miss :-)

Could you add a comment (or a disable reason) that explains why these tests are disabled in order to avoid this missunderstood in the future? @michalvavrik

Sure, will do @pjgg .


Upgrade Kubernetes to 1.14.8

Hi,
We update k8s from 1.11.3 to 1.14.8.
But We get the error message.

Oct 18 08:40:32 ip-10-0-1-86.us-west-2.compute.internal sh[1942]: W1018 08:40:32.950098    1942 options.go:267] unknown 'kubernetes.io' or 'k8s.io' labels specified with --node-labels: [kubernetes.io/role node-role.kubernetes.io/master]
Oct 18 08:40:32 ip-10-0-1-86.us-west-2.compute.internal sh[1942]: W1018 08:40:32.950899    1942 options.go:268] in 1.16, --node-labels in the 'kubernetes.io' namespace must begin with an allowed prefix (kubelet.kubernetes.io, node.kubernetes.io) or be in the specifically allowed set (beta.kubernetes.io/arch, beta.kubernetes.io/instance-type, beta.kubernetes.io/os, failure-domain.beta.kubernetes.io/region, failure-domain.beta.kubernetes.io/zone, failure-domain.kubernetes.io/region, failure-domain.kubernetes.io/zone, kubernetes.io/arch, kubernetes.io/hostname, kubernetes.io/instance-type, kubernetes.io/os)
Oct 18 08:40:32 ip-10-0-1-86.us-west-2.compute.internal sh[1942]: F1018 08:40:32.952137    1942 server.go:194] failed to load Kubelet config file /etc/kubernetes/config/kubelet.yaml, error failed to decode, error: v1beta1.KubeletConfiguration.KubeReserved: ReadMapCB: expect { or n, but found ", error found in #10 byte of ...|eserved":"cpu=100m,m|..., bigger context ...|i"},"kind":"KubeletConfiguration","kubeReserved":"cpu=100m,memory=100Mi,storage=2Gi","rotateCertific|...

In our cluster.yaml,  I set :
kubelet:
  kubeReserved: "cpu=100m,memory=100Mi,ephemeral-storage=2Gi"
  systemReserved: "cpu=100m,memory=100Mi,ephemeral-storage=2Gi"

Anyone have any suggestion?
Thanks for your help

I just came across this as well.  The template for /etc/kubernetes/config/kubelet.yaml is rendering the string as is.
kubeReserved: "cpu=100m,memory=100Mi,ephemeral-storage=2Gi"
This may have worked in the past but I think the reservations are suppose to be rendered like:
kubeReserved:     cpu: 1000m     memory: 1024Mi     ephemeral-storage: 1024Mi


Please improve migrate command to work same as rollback when target is set to an old migration ID

Currently migrate command does not respect version_order:execution config or breakpoints like rollback command does.
I have a CD environment for our main codebase. I'm using phinx in a separate codebase to manage its database. I'm using the version_order:execution config. For each CI build that triggered by a code merge, I store the Migration ID in the artifact. Then during deployment, I want to run migrate -t {Migration ID} together with the main artifact deployment. Please note this need to support rolling back the entire system to an old artifact.
Right now, when if I run migrate -t {Migration ID}, where {Migration ID} is in the past when I do a system roll back, phinx will rollback all the migrations that are created after that {Migration ID} and disregard any existing breakpoint. I think this is wrong, it should detect the {Migration ID} is in the past then perform same behaviour as rollback -t {Migration ID}, which respect the version_order:execution config and any breakpoint.
For the CD environment I described above, this is very important because I can then have a consistent method to handle database migrations for my deployments, doesn't matter if it is a new release or a rollback.
My workaround right now is that in the deployment process, I have to check if the {Migration ID} is up or down. If it is down, I call phinx migrate -t {Migration ID}; if it is up, I will have to call phinx rollback -t {Migration ID}.
Thanks.

OOI, could you not just use rollback?

@rquadling Yes I could. That would be my workaround for now.
Since migrate command does not only support migrate forward, but also supports migrating to a Migration ID in the past, then users would expect it behaves the same as rollback, which respects the version_order:execution setting and any breakpoints.
In my case, it it important to have one consistent way to migrate to a point (i.e. a given Migration ID) that is associated to a release artifact. That point might be the latest migration, and might be anywhere in the execution history.
Hope that makes sense. Thanks.

I can certainly see the issue you are having.
My concern is how to deal with migrating to a point in the past that still has unmigrated migrations.
If the migration target is in the past, it may well be easiest internally if we first call 'rollback' and then 'migrate' command to the same target.
For the time being, maybe a simple shell script that does both of these commands.

It is still migrating forward when migrating to a point in the past that still has unmigrated migrations. So I guess phinx would apply the oldest unmigrated migration first. That shouldn't be a problem.

Is this still an issue?

@dereuromark I actually haven't been using it since August. So I couldn't validate it at this point. Unless an improvement has been merged in, I assume it is still an issue.


Send only CONFIG and depending config types when securityconfig is requested

opendistro-for-elasticsearch/security pull request intake form
Please provide as much details as possible to get feedback/acceptance on your PR quickly

Category: (Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation)

Github Issue # or road-map entry, if available:

Description of changes:

Why these changes are required?

What is the old behavior before changes and new behavior after changes? (Please add any example/logs/screen-shot if available)

Testing done: (Please provide details of testing done: Unit testing, integration testing and manual testing)

TO-DOs, if any: (Please describe pending items and provide Github issues# for each of them)

Is it backport from master branch? (If yes, please add backport PR # and commits #)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

The solution should cover not only security config but all other CTypes as well.

I understand that. The follow-up changes will be made before the PR gets published for review.

The solution should cover not only security config but all other CTypes as well.

I understand that. The follow-up changes will be made before the PR gets published for review.


/status information not found in PowerMTA

I'm using v0.0.4 of the plugin and I noticed the script does not find any metrics on http://pmtahost/status?format=xml. We're running Power MTA 4.0r9-201211271658.
I noticed that the webserver (pmtahttp) is responding with the wrong content-type for the status URL, so that might throw of the XML-parsing. This does not happen with the other request (domains and queues):
# curl -I "http://<host>/status?format=xml"
HTTP/1.1 200 Ok
Content-Type: text/html
Cache-Control: no-cache
Connection: close

latest version powermta / pmta available with lifetime license key.

another tools available
Skype: salimrezabd04
Telegram: salimrezabd
Telegram: salimrezabd1


Add requirements with exact version numbers

To avoid installation problems we need to add all of dependencies along with their exact version numbers to requirement files. This can be achieved by running pip freeze after a fresh install in a new virtualevn.

@mehdisadeghi ,  addressed by #18


Inline loaders are ignore in webpack 5

Bug report

What is the current behavior?
Inline loaders are ignored if webpack configuration has rules for these files.
const testImage = require('!file-loader!./images/test-image.png');
const testIcon = require('!html-loader!image-webpack-loader!./images/test-icon.svg');

console.log('> testImage', testImage);
console.log('> testIcon', testIcon);

// from storybook's webpack configuration
{
  test: /\.(svg|ico|jpg|jpeg|png|apng|gif|eot|otf|webp|ttf|woff|woff2|cur|ani|pdf)(\?.*)?$/,
  type: 'asset/resource',
  generator: { filename: 'static/media/[path][name].[ext]' }
}

results in
> testImage file:///D:/projects/tests/webpack-5-inline-loaders/dist/static/media/src/images/test-image..png
> testIcon file:///D:/projects/tests/webpack-5-inline-loaders/dist/static/media/src/images/test-icon..svg

If the current behavior is a bug, please provide the steps to reproduce.
https://github.com/artaommahe/webpack-5-inline-loaders
code https://github.com/artaommahe/webpack-5-inline-loaders/blob/main/src/index.js
webpack config https://github.com/artaommahe/webpack-5-inline-loaders/blob/main/webpack.config.js

git clone
yarn install
yarn webpack
open dist/index.html
see undefined for images and this in console> testImage file:///D:/projects/tests/webpack-5-inline-loaders/dist/static/media/src/images/test-image..png
> testIcon file:///D:/projects/tests/webpack-5-inline-loaders/dist/static/media/src/images/test-icon..svg

comment out images rule in webpack config
yarn webpack
see expected result as> testImage Module {__esModule: true, Symbol(Symbol.toStringTag): "Module"}default: "file:///D:/projects/tests/webpack-5-inline-loaders/dist/6af9ab209f7be65032e1462798741a97.png"
> testIcon Module {__esModule: true, Symbol(Symbol.toStringTag): "Module"}default: "<svg ..."

Same if !! is used.
What is the expected behavior?
Expected result is overriding rule with the inline loaders as it worked in webpack 4.x.

Other relevant information:
webpack version:  5.41.1
Node.js version: 12.18.1
Operating System: Win10
Additional tools:
"file-loader": "^6.2.0",
"html-loader": "^2.1.2",
"html-webpack-plugin": "^5.3.2",
"image-webpack-loader": "^7.0.1",
"webpack": "^5.41.1",
"webpack-cli": "^4.7.2"

first found in https://github.com/storybookjs/storybook/issues/15438, than narrowed to the clean webpack's issue

Works as expected file-loader is not compatibility with asset modules

Also [ext] includes . (dot), you should not specify . when you use [ext]

image-webpack-loader should be used as pre loader, because it is compression and not affected on output format (i.e. commonjs or es modules) https://webpack.js.org/configuration/module/#ruleenforce

@alexander-akait Are inline loaders going to be deprecated soon?
I maintain an internal library of React components where SVG icons are imported like this:
import(`!!babel-loader?{"plugins":["module:@ci/atoms/babel.cjs"],"presets":["@babel/preset-env","@babel/preset-react"]}!@svgr/webpack?+titleProp,+ref,+icon,-babel!./assets/${type}.svg`);

It's really ugly, but it allows the library to be used in any Webpack application without needing to rely on some specific config, so it's one less thing to track in a plethora of different applications. The SVG icons are thus plug'n'play in both Storybook and Gatsby (well, not anymore), as well as applications with a custom Webpack config.
What do you believe is the best solution? Should Storybook not use any convenience asset module rules? We are currently doing this (so we don't break all the other applications):
config.module.rules.forEach(rule => {
  if (rule.type === 'asset/resource') {
    // https://github.com/storybookjs/storybook/issues/15438
    rule.test = new RegExp(rule.test.source.replace('svg|', ''), rule.test.flags);
  }
});

Maybe Webpack could consider !! at the start of the import so the asset module rules won't take effect at all? Since it already kinda means "I'll handle it myself".

We have !=! syntax for complex cases, look at here https://github.com/webpack/webpack/issues/11074#issuecomment-648658214

Also we prepare new version of image-minimizer-webpack-pluginhttps://github.com/webpack-contrib/image-minimizer-webpack-plugin/`  and describe a lot of cases, so you can migrate from image-webpack-loader on good, full featured and cachable version

@alexander-akait Thanks a lot for the response. I've managed to get a single icon working:
`calendar.js!=!@svgr/webpack!./assets/calendar.svg`

SVGR now correctly transforms the SVG file to a React component and no .svg rules apply. The issue comes with using an expression to import the icons.
`${type}.js!=!@svgr/webpack!./assets/${type}.svg`

This doesn't work for me, the resulting file contains
(self["webpackChunk_cbs_instance_lka"] = self["webpackChunk_cbs_instance_lka"] || []).push([["shared-libs_atoms_src_components_Icon_assets_calendar_svg"],{

/***/ "../../shared-libs/atoms/src/components/Icon/assets/calendar.svg":
/*!***********************************************************************!*\
  !*** ../../shared-libs/atoms/src/components/Icon/assets/calendar.svg ***!
  \***********************************************************************/
/***/ (function(module) {

module.exports = "data:image/svg+xml;base64,PHN...

/***/ })

}]);

Is it possible to use the !=! syntax somehow with these expressions?
I'm thinking about ditching .svg altogether and using some random extension instead, but I'm still curious if this is possible somehow, because it'd be easier to inspect the icon assets manually.

Is it possible to use the !=! syntax somehow with these expressions?

Can you clarify? Maybe you can create small repo with example what do you want to achieve and I will help you

Sure, I'll prepare a repo and get back to you, thanks!

@alexander-akait https://github.com/wafflepie/reproduction-svgr-webpack yarn && yarn start
For some reason, this reproduction throws an error instead of emitting a file with a data URI, but the fully static import works fine.

Hm, works fine:
import { renderToString } from "react-dom/server";
import { createElement } from "react";

const importFooAsset = () => import(`!@svgr/webpack!./assets/foo.svg`);

const importDynamicAsset = (type) =>
  import(`!@svgr/webpack!./assets/${type}.svg`);

(async () => {
  const foo = await importFooAsset();
  console.log(renderToString(createElement(foo.default))); // React component, renders an SVG element.

  const bar = await importDynamicAsset("bar"); // Error: Cannot find module 'bar.js!=!@svgr/webpack!./assets/bar.svg'
  console.log(renderToString(createElement(foo.default)));
})();

yarn run v1.22.10
$ rimraf dist && webpack && node dist/main
asset main.js 220 KiB [emitted] (name: main)
asset node_modules_svgr_webpack_lib_index_js_assets_bar_svg.js 2.31 KiB [emitted]
asset node_modules_svgr_webpack_lib_index_js_assets_baz_svg.js 1.77 KiB [emitted]
asset node_modules_svgr_webpack_lib_index_js_assets_foo_svg.js 1.61 KiB [emitted]
runtime modules 2.05 KiB 6 modules
cacheable modules 213 KiB
  modules by path ./node_modules/ 210 KiB
    modules by path ./node_modules/react-dom/ 137 KiB 3 modules
    modules by path ./node_modules/react/ 70.6 KiB
      ./node_modules/react/index.js 190 bytes [built] [code generated]
      ./node_modules/react/cjs/react.development.js 70.5 KiB [built] [code generated]
    ./node_modules/object-assign/index.js 2.06 KiB [built] [code generated]
  modules by path ./assets/*.svg 2.79 KiB
    ./node_modules/@svgr/webpack/lib/index.js!./assets/foo.svg 679 bytes [built] [code generated]
    ./node_modules/@svgr/webpack/lib/index.js!./assets/bar.svg 1.31 KiB [optional] [built] [code generated]
    ./node_modules/@svgr/webpack/lib/index.js!./assets/baz.svg 839 bytes [optional] [built] [code generated]
  ./index.js 591 bytes [built] [code generated]
./assets/ lazy<EMAIL_ADDRESS>^\.\/.*\.svg$ namespace object 160 bytes [built] [code generated]
external "stream" 42 bytes [built] [code generated]
webpack 5.42.1 compiled successfully in 589 ms
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 42.52 42.52" data-reactroot=""><circle cx="21.26" cy="21.26" r="21.26"></circle></svg>
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 42.52 42.52" data-reactroot=""><circle cx="21.26" cy="21.26" r="21.26"></circle></svg>
Done in 0.90s.

webpack config:
module.exports = {
  entry: "./index.js",
  mode: "development",
  target: "node",
  devtool: false,
  module: {
    rules: [
      {
        test: /\.svg$/,
        loader: "url-loader",
        type: 'javascript/auto'
      },
    ],
  },
};

but you can safely remove url-loader:
module.exports = {
  entry: "./index.js",
  mode: "development",
  target: "node",
  devtool: false,
};

I am missing something?
And sorry for delay

@alexander-akait I can't use !@svgr/webpack!./assets/${type}.svg because we're trying to avoid the asset/resource rule.
I've updated the reproduction repository to include the original issue we're trying to avoid, here's a quick recap:

Some existing application (whose Webpack config I don't want to modify) uses asset/resource for SVGs.
I want to skip this rule and instead supply my own set of loaders in the import expression (doesn't work with just ! at the start).
Apparently, this is possible using !=! which works well for "static" imports, i.e. foo.js!=!@svgr/webpack!./assets/foo.svg.
Once I need to use dynamic expressions, i.e. ${type}.js!=!@svgr/webpack!./assets/${type}.svg, this fails.

All applications in our ecosystem use Webpack and have arbitrary configs. I want to have a component which is usable in any of them, because it configures its own loaders and is thus fully plug'n'play.

Why not register svgr loader on resourceQuery and using ./assets/foo.svg?type=svgr? It is real weird, we try to avoid inline syntax and strongly recommend do not use it, it is old legacy stuff, we are on es modules, so we can use query or assert (will be in near future)

we try to avoid inline syntax and strongly recommend do not use it, it is old legacy stuff, we are on es modules, so we can use query or assert (will be in near future)

For us the main issue is tooling and different webpack configs. E.x. angular and storybook for angular use different loaders at least for images. For consistent behavior we have to use inline loaders, but now they are ignored by assets modules rules and we have to fine-tune storybook's webpack config... It doesn't look like scalable solution.

@alexander-akait Sure, I can find a workaround and this would probably work pretty well. I was just hoping/asking if there is a supported solution where it wouldn't be necessary to modify the Webpack config at all, because this would require modifying 5 of them on our side if we dropped the inline loaders completely (just because of a single React component with specific requirements).
If this is not planned/supported, that's fine. I just wanted to raise awareness of my particular use case (which doesn't seem that unreasonable to me).

To be honestly inline loader syntax is hack from the past, when dreamed about ES modules, now we have them and even more we have import foo from './something.ext' assert { type: "something" }, of course we can probably see how improve inline syntax for as context requests, but I think we need to get away from this syntax as soon as possible in favor import something from './something?query' and in future in favor import assertion. I can open this problem, but again, most likely it will not be fixed in the near future and perhaps never...

Also we merged https://github.com/webpack/webpack/pull/12278, so you can try it on the next release, I think it is great syntax/feature :star:


System.NullReferenceException: Object reference not set to an instance of an object.

OK so I know that this issue has been posted before but they didn't provide info and they are all closed, and id like to try to use and test this feature on VS code
So information on my current enviroment

OS
Version

Windows10
Build 17134

VSCode Version: 1.33.1
Current Extensions installed and versions

Extension
Version

Beautify
1.4.11

Document This
0.7.1

Git Lens - Git supercharged
9.6.0

jshint
0.10.20

Live Share
1.0.45

Material Icon Theme
3.7.0

Minify
0.4.3

node-readme
3.0.2

Node.js Modules Intellisense
1.5.0

npm
0.3.5

npm intellisense
1.3.0

One Dark Pro
2.21.0

Discord Presence
3.4.0

ftp-sync
0.3.9

SQLite
0.6.0

SSH FS
1.14.7

Attached below are full error logs but here is a snip of the actual error that occurred:
[2019-04-13 17:57:37.011 Agent.Rpc.Workspace E] Exception in workspace.shareWorkspace request handler: System.NullReferenceException: Object reference not set to an instance of an object.
   at Microsoft.Cascade.Common.ProtocolConverter.SystemUriConverter.MapPathsToUrisAsFolders(String path, Int32 index) in E:\A\_work\202\s\src\Common\ProtocolConverter\SystemUriConverter.cs:line 45
   at System.Linq.Enumerable.SelectIterator[TSource,TResult](IEnumerable`1 source, Func`3 selector)+MoveNext()
   at Microsoft.Cascade.Common.CollectionExtensions.AddRange[T](ICollection`1 collection, IEnumerable`1 range) in E:\A\_work\202\s\src\Common\CollectionExtensions.cs:line 12
   at Microsoft.Cascade.Common.ProtocolConverter.SystemUriConverter..ctor(String scheme, IEnumerable`1 rootFolders, SystemUriConverterPrefixMode prefixMode, Boolean isHost, IFileService fileService) in E:\A\_work\202\s\src\Common\ProtocolConverter\SystemUriConverter.cs:line 67
   at Microsoft.Cascade.Agent.WorkspaceService.ShareWorkspaceAsync(WorkspaceShareInfo shareInfo, CancellationToken cancellationToken) in E:\A\_work\202\s\src\Agent\WorkspaceService.cs:line 357
   at Microsoft.Cascade.Rpc.RpcDispatcher`1.<>c__DisplayClass24_2.<<CreateDispatchMethod>b__4>d.MoveNext() in E:\A\_work\202\s\src\Rpc\RpcDispatcher.cs:line 309
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.Cascade.Rpc.RpcDispatcher`1.HandleRequestAsync(RequestMessage request, IProgress`1 progress, CancellationToken cancellationToken) in E:\A\_work\202\s\src\Rpc\RpcDispatcher.cs:line 102
   at Microsoft.Cascade.Rpc.RpcSession.RequestAsync(IRpcService service, RequestMessage message, CancellationToken cancellation) in E:\A\_work\202\s\src\Rpc\RpcSession.cs:line 636
[2019-04-13 17:57:37.012 Agent.Rpc.Workspace V] < #1 {Result=<null> Id=26 Error={Code=-32098 Message=Object reference not set to an instance of an object. Data=(StackTrace=System.NullReferenceException: Object reference not set to an instance of an object.
   at Microsoft.Cascade.Common.ProtocolConverter.SystemUriConverter.MapPathsToUrisAsFolders(String path, Int32 index) in E:\A\_work\202\s\src\Common\ProtocolConverter\SystemUriConverter.cs:line 45
   at System.Linq.Enumerable.SelectIterator[TSource,TResult](IEnumerable`1 source, Func`3 selector)+MoveNext()
   at Microsoft.Cascade.Common.CollectionExtensions.AddRange[T](ICollection`1 collection, IEnumerable`1 range) in E:\A\_work\202\s\src\Common\CollectionExtensions.cs:line 12
   at Microsoft.Cascade.Common.ProtocolConverter.SystemUriConverter..ctor(String scheme, IEnumerable`1 rootFolders, SystemUriConverterPrefixMode prefixMode, Boolean isHost, IFileService fileService) in E:\A\_work\202\s\src\Common\ProtocolConverter\SystemUriConverter.cs:line 67
   at Microsoft.Cascade.Agent.WorkspaceService.ShareWorkspaceAsync(WorkspaceShareInfo shareInfo, CancellationToken cancellationToken) in E:\A\_work\202\s\src\Agent\WorkspaceService.cs:line 357
   at Microsoft.Cascade.Rpc.RpcDispatcher`1.<>c__DisplayClass24_2.<<CreateDispatchMethod>b__4>d.MoveNext() in E:\A\_work\202\s\src\Rpc\RpcDispatcher.cs:line 309
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.Cascade.Rpc.RpcDispatcher`1.HandleRequestAsync(RequestMessage request, IProgress`1 progress, CancellationToken cancellationToken) in E:\A\_work\202\s\src\Rpc\RpcDispatcher.cs:line 102
   at Microsoft.Cascade.Rpc.RpcSession.RequestAsync(IRpcService service, RequestMessage message, CancellationToken cancellation) in E:\A\_work\202\s\src\Rpc\RpcSession.cs:line 636)} HandlingTimes=[1760] Size=0 MessageId=0 AckId=0}

Steps to reproduce:
I simply installed the extension and tried to click 'Start a Collaboration Session'
I get a popup stating that its in the process of starting then shortly after i get a popup that states that error
If more information is needed I will try to provide, id like to see if i can run this plugin so I can potentially collaborate with my coding projects, but it would also help anyone else who is currently running into this issue with no solution. Because from my quick skimming from past issues they where all closed with no solution.
LiveShareLogs.zip

Thanks for the detailed issue report, @Seth177 ! I'll look into this. In the meantime, could you try disabling all other extensions and seeing if that resolves your problem?

@nandiniYeltiwar @cait1inhennessy could you take a look?

E:\A_work\202\s\src\Agent\WorkspaceService.cs:line 357

I just disabled all extensions and still getting the error, So it appears that an extension isn't the root cause of the issue.
LiveShareLogs.zip

Also i tried tested using both a github account sign in and a microsoft account sign in and that doesn't seem to affect the issue

Thanks for the extra diagnostics! We're looking into it.

It seems like Live share v1.0.07 seems to have fixed this issue, i just tried today to Start a Live share session and it didn't give  a error and correctly generated a live share session, I hope the info i gave you guys helped fix this as the issue is now gone. I don't know what you guys did to fix it but it seems to have worked. Thanks for your hard work.
I am going to manually close this issue thread, thanks for the help

Coming back to this this issue was actually related to an extension, the extension being SSH FS
I just encountered this issue and figured out it was the issue when i added a workspace that was created using the SSH FS extension. It seems these two extensions are incompatible with each other, as soon as i removed the workspace created by SSHFS it worked fine

@Seth177 Thanks for the update!


Add SparseArrays forEach extensions

feature #223

In my opinion, it should follow the iterator implementation, not for(i in 0..size()-1), as that would prevent possible discrepancies if the said array modifies itself.
That said, current implementation does seem to be prone to IndexOutOfBoundsException if the former happens by self modification as well as ConcurrentModificationException

I think this implementation is OK, because SparseArrays have no iterators and thus it will be impossible to check for comodification fast and clearly. Unlike iterators, given extensions do not use any extra allocations, which is much appreciated in Android.
Also:
— you can use 0 until size instead of 0 .. size-1, this is less error-prone and more self-explanatory;
— it is also possible to implement forEachKey and forEachValue;
— there are also SparseArrayCompat and SimpleArrayMap, they could be iterated this way too.

Merged. Thank you!


Update documentation after nativeAutomation's deprecation

Steps to reproduce
It concerns readme + https://pub.dev/documentation/patrol/latest/ + https://patrol.leancode.co/
Actual results
Hello
the documentation doesn't seem to be up to date with the depreciation of nativeAutomation
Logs
no comment
Patrol version
patrol 2.2.3
Patrol Doctor output
no comment
Flutter Doctor output
no comment

Hi @redDwarf03, we will update the documentation soon. We had a bit of miscommunication here, that's why those changes got released :) Please don't close this issue, we will track this task here

Hi @jBorkowska @redDwarf03 nativaeAutomation is going to be deprecated? sorry If I misunderstood this issue incorrectly. I use nativeAutomation in my tests and using latest patrol_cli 2.1.3

nativeAutomation flag is not marked deprecated anymore, we will remove this flag in next major release


make hypothesis aware of conlist length constraints

Change Summary
This change should make hypothesis respect min_items and max_items in conlist.
But it doesn't currently, and I can't figure out why. I need help finishing this PR off.
Related issue number
#2875
Checklist

[ ] Unit tests for the changes exist
[ ] Tests pass on CI and coverage remains at 100%
[x] Documentation reflects the changes where applicable - n/a
[x] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)
[x] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

please review

@Zac-HD can you please help me make this PR work?
I'm trying to make hypothesis understand conlist.

Ah, I just saw the note up the top of _hypothesis_plugin.py.
# conlist() and conset() are unsupported for now, because the workarounds for
# Cython and Hypothesis to handle parametrized generic types are incompatible.
# Once Cython can support 'normal' generics we'll revisit this.

What's the status of those Cython changes?
And if I can't modify pydantic to make hypothesis understand conlist, is there an easy workaround to add to my end-user code to make it work? I couldn't get register_type_strategy to work. It kept throwing errors about registering a function instead, but when I did that the strategy wasn't invoked. Is this the same issue described in that comment above?

I'm sorry, but I can't help make this work.  Believe me, if I could it would already be done!
Based on https://github.com/cython/cython/issues/3537 and https://github.com/cython/cython/pull/4005, it looks like the relevant changes to Cython have been made, but not yet released.  I haven't actually tried building anything with Cython master (or 3.0a7) though, so there's a nontrivial chance that it's still broken.
It does sound like the same issue - if you have time (unfortunately I don't at the moment), you could try this patch and/or register_type_strategy under the Cython alpha.  If you can share the register_type_strategy code I might be able to diagnose that, too.
Re: workarounds, registering a strategy for the model you want using st.builds() should work - and pass a st.lists() strategy for the conlist argument.

Those links are for cython, but I'm using cpython. My understanding is that they are competing interpreters, so any user is going to use just one or the other. So why does it still not work for me in cpython?
For the workaround, you're saying to register the class whose attribute is a conlist?
class Model(BaseModel):
    x: conlist(int, min_items=1)
register_type_strategy(Model, something)

Oh boy. My real model's going to have about 20 or 30 different conlist attributes. I'll see if I can automate that.

Those links are for cython, but I'm using cpython. My understanding is that they are competing interpreters, so any user is going to use just one or the other. So why does it still not work for me in cpython?

Cython is not an interpreter, it's used to compile libraries such as Pydantic as native-code extensions for CPython.  See this code in setup.py.

Oh boy. My real model's going to have about 20 or 30 different conlist attributes. I'll see if I can automate that.

Shouldn't be too hard, since you have access to the Model object and can call typing.get_type_hints() on it 🙂

Ah I see.
So if I'm using pydantic, then I'm using cython, even if I'm not aware of it.
Once those other issues are resolved, is the code in this PR sufficient to to resolve #2876 ?

Here's my workaround script.
Zac, can you please tell me the best way to do the if statement condition? I couldn't find anything better than if 'ConstrainedListValue' in str(t):, since the types library doesn't have a ConstrainedListValue class that can be imported.
import pydantic
from pydantic import conlist
from typing import Type, List, Optional, get_type_hints
from hypothesis import strategies as st
from hypothesis import given

class Problem(pydantic.BaseModel):
    x: int
    y: List[str]
    z: conlist(str, min_items=4, max_items=5)
    a: conlist(conlist(float, min_items=1, max_items=2), max_items=1)

def strat_from_type(t: Type) -> st.SearchStrategy:
    #if isinstance(t, types.ConstrainedListValue): # doesn't work this way
    if 'ConstrainedListValue' in str(t):
        return st.lists(strat_from_type(t.item_type), min_size=t.min_items or 0, max_size=t.max_items)
    else:
        return st.from_type(t)

strat = st.builds(build, **{k: strat_from_type(t) for (k,t) in get_type_hints(Problem).items()})

@given(strat)
def test(data):
    Problem.parse_obj(data)
test()

Shorter workaround - note use of issubclass, omitting arguments instead of from_type(), etc.
import pydantic
from pydantic import conlist
from typing import List, get_type_hints
from hypothesis import given, strategies as st

class Problem(pydantic.BaseModel):
    x: int
    y: List[str]
    z: conlist(str, min_items=4, max_items=5)
    a: conlist(conlist(float, min_items=1, max_items=2), max_items=1)

kwargs = {
	k: st.lists(strat_from_type(t.item_type), min_size=t.min_items or 0, max_size=t.max_items)
	for k, t in get_type_hints(Problem).items()
	if issubclass(t, ConstrainedListValue)  # let builds() handle the others
}
strat = st.builds(Problem, **kwargs)

st.register_type_strategy(Problem, strat)  # you can work out other integrations or helper functions

As a more general tip, it looks like you should check out st.fixed_dictionaries():
- def build(**kwargs):
-     return kwargs
- strat = st.builds(build, **{ ... })
+ strat = st.fixed_dictionaries({ ... })

I already tried something similar.
That approach doesn't work.
Traceback (most recent call last):
  File "test.py", line 12, in <module>
    kwargs = {
  File "test.py", line 15, in <dictcomp>
    if issubclass(t, ConstrainedListValue)  # let builds() handle the others
NameError: name 'ConstrainedListValue' is not defined

ConstrainedListValue is a special class. It seems to not be importable from any library.
I think it comes from here.
return new_class('ConstrainedListValue', (ConstrainedList,), {}, lambda ns: ns.update(namespace))

Where new_class is from typing.
How do I make issubclass work with new_class?

Ah, sorry - we'll need to check issubclass(t, ConstrainedList) - that's the "grandparent" type, ConstrainedListValue is the parent type but not directly accessible.

Hi @mdavis-xyz
What is the status of this PR? Do you need some help on this?
IMO it can wait for after 1.9 (I try to review everything to make a release this month). Do you agree?

The status is that the PR doesn't work because of a bug/limitation with cython. We need to wait until Cython releases a version with those patches.

If this is now working, we can review it and consider merging, if it's still blocked by cython, let's close it and wait for V2 when this stuff should be fixed, partly via annotated-types.

Still failing :-(.
Let's wait to fix the problem in V2.


chore(github): install dependencies from lockfile

I think it's a good idea to install dependencies from lockfile – especially in CI/CD processes to ensure consistency. Thoughts, @lambrohan?

@kylejb couldn't agree more!


Tendermint / Ethereum Staking

We need to design and link up staking and economic model in the tendermint backend, and have that interoperate with an ERC20 staking / gas token.

Out of date.


///  Doesn't work when upgrading to v0.26.3.

Describe the bug
When upgrading to version v0.26.3, my vite.config.ts files are showing type errors:

Reproduction
Can share access to the repo when / if required.
System Info
System:
    OS: macOS 12.3.1
    CPU: (8) arm64 Apple M1 Pro
    Memory: 132.13 MB / 32.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node
    Yarn: 1.22.18 - /usr/local/bin/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm
  Browsers:
    Chrome: 108.0.5359.124
    Firefox: 98.0.2
    Firefox Developer Edition: 99.0
    Safari: 15.4
  npmPackages:
    vitest: 0.26.3 => 0.26.3

### Used Package Manager

pnpm

### Validations

- [X] Follow our [Code of Conduct](https://github.com/vitest-dev/vitest/blob/main/CODE_OF_CONDUCT.md)
- [X] Read the [Contributing Guidelines](https://github.com/vitest-dev/vitest/blob/main/CONTRIBUTING.md).
- [X] Read the [docs](https://vitest.dev/guide/).
- [X] Check that there isn't [already an issue](https://github.com/vitest-dev/vitest/issues) that reports the same bug to avoid creating a duplicate.
- [X] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/vitest-dev/vitest/discussions) or join our [Discord Chat Server](https://chat.vitest.dev).
- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.

Upgrade your Vite package so versions match with Vitest.

for anyone landing here too:
i'm on "vite": "^4.1.1" and "vitest": "^0.28.3" and my vite config is still broken just like in OPs case.
my lock file says i have version "4.0.4" and version 4.1.1 of vite installed.
yarn why vite gives me this:
[1/4] Why do we have the module "vite"...?
[2/4] Initialising dependency graph...
[3/4] Finding dependency...
[4/4] Calculating file sizes...
=> Found<EMAIL_ADDRESS>info Has been hoisted to "vite"
info This module exists because it's specified in "dependencies".
info Disk size without dependencies: "3.16MB"
info Disk size with unique dependencies: "6.7MB"
info Disk size with transitive dependencies: "7.19MB"
info Number of shared dependencies: 12
=> Found<EMAIL_ADDRESS>info This module exists because "vitest" depends on it.
info Disk size without dependencies: "3.15MB"
info Disk size with unique dependencies: "6.68MB"
info Disk size with transitive dependencies: "7.17MB"
info Number of shared dependencies: 12
=> Found<EMAIL_ADDRESS>info This module exists because "vitest#vite-node" depends on it.
info Disk size without dependencies: "3.15MB"
info Disk size with unique dependencies: "6.68MB"
info Disk size with transitive dependencies: "7.17MB"
info Number of shared dependencies: 12

output of yarn why vitest:
[1/4] Why do we have the module "vitest"...?
[2/4] Initialising dependency graph...
[3/4] Finding dependency...
[4/4] Calculating file sizes...
=> Found<EMAIL_ADDRESS>info Has been hoisted to "vitest"
info Reasons this module exists
   - Specified in "dependencies"
   - Hoisted from "@vitest#coverage-istanbul#vitest"
info Disk size without dependencies: "6.98MB"
info Disk size with unique dependencies: "22.93MB"
info Disk size with transitive dependencies: "29.98MB"
info Number of shared dependencies: 53

why is vitests dev dependency specified with ^3 but the pnpm override at ^4?
do the vitest and vite versions again not match? should I create a new issue?

why is vitests dev dependency specified with ^3 but the pnpm override at ^4?

This doesn't matter to the end user.

do the vitest and vite versions again not match? should I create a new issue?

They do match. Vitest specifies Vite version as "^3.0.0 || ^4.0.0". Yarn sees that you previously had 4.0.4 and doesn't update it when you install Vite 4.1.1, since it matches the version.

thats what i initially assumed,
but why does typescript then not accept the test block in my vite.config.js? its identical to the docs: https://vitest.dev/config/

it says Object literal may only specify known properties, and 'test' does not exist in type 'UserConfigExport' so for some reason the tripple slash does not do anything at all.

Because you have two separate versions installed. Vitest depends on the 4.0.4 one and your tsconfig uses 4.1.1, because it's in your dependencies.
This is how yarn resolved this, I am not sure what Vitest can do to tell the package manager to use your installed version. Specify as "peerDependency"? Most package managers won't install it then, but it's required for projects not using Vite, for example, so 🤷🏻

but that means that<EMAIL_ADDRESS>does not work with<EMAIL_ADDRESS>as it needs<EMAIL_ADDRESS>right? what i mean is that if the highest version of vite vitest currently works with is @4.0.4, it should be stated somewhere.
edit: i just checked and 4.1.0 and 4.1.1 released today / in the last 3 hours. so it's just bad timing.

but that means that<EMAIL_ADDRESS>does not work with<EMAIL_ADDRESS>as it needs<EMAIL_ADDRESS>right?

Why do you think that? The current version covers 4.1.1: https://semver.npmjs.com

i did not fully understand your last reply, as it seemed to me that according to my lock file the dependencies should be exactly as they should be. when i had<EMAIL_ADDRESS>and<EMAIL_ADDRESS>installed, i received the mentioned type error on my vite.config. this led to my conclusion that these two package version apparently dont work together.
especially because yarn why printed that my installed vite version depended on<EMAIL_ADDRESS>=> Found<EMAIL_ADDRESS>info This module exists because "vitest" depends on it.

i've now upgraded to<EMAIL_ADDRESS>and<EMAIL_ADDRESS>and somehow yarn has now resolved the dependencies correctly, and removed the dependency to<EMAIL_ADDRESS>the type error is now gone. but even then I dont understand why I received a type error in the first place. because if I understand your statement correctly<EMAIL_ADDRESS>should work with any vite version in the range  "^3.0.0 || ^4.0.0".
but I've already taken up much of your time, and my issue is resolved. thank you.

Sorry to bump this, but after upgrading from<EMAIL_ADDRESS>/<EMAIL_ADDRESS>to<EMAIL_ADDRESS>/<EMAIL_ADDRESS>I'm now getting this error as well. I bumped both of these at the same time.
=> Found<EMAIL_ADDRESS>info Has been hoisted to "vite"
info This module exists because it's specified in "devDependencies".
info Disk size without dependencies: "3.16MB"
info Disk size with unique dependencies: "6.59MB"
info Disk size with transitive dependencies: "7.12MB"
info Number of shared dependencies: 10
=> Found<EMAIL_ADDRESS>info This module exists because "vitest" depends on it.
info Disk size without dependencies: "3.14MB"
info Disk size with unique dependencies: "6.58MB"
info Disk size with transitive dependencies: "7.1MB"
info Number of shared dependencies: 10
=> Found<EMAIL_ADDRESS>info This module exists because "vitest#vite-node" depends on it.
info Disk size without dependencies: "3.14MB"
info Disk size with unique dependencies: "6.58MB"
info Disk size with transitive dependencies: "7.1MB"
info Number of shared dependencies: 10

Something feels like this is a VSCode or Typescript engine issue. I see similar issues with Vite and import.meta.env ...


Mac OS Release 0.12 rc-2 causes popup dialog "LLDB provided no error string"

Same issue as 532.
The cause and solution are included here
(I pulled the link from @BradLarson 's pull request, I couldn't wait :) )

Per the solution here, running
sudo install_name_tool -add_rpath /Applications/Xcode.app/Contents/Developer/Library/Frameworks/ <toolchain path>/System/Library/PrivateFrameworks/LLDB.framework/Versions/A/LLDB
lets you run with the Xcode 12.2 beta 3 specified on Installation.md, or a normal Xcode 12 installation (not beta). Seems worth inserting one rpath so that people don't have to go find and install a new Xcode beta to try the toolchain.

Thanks for the workaround. I can confirm it works with 0.12 release (not RC) on macOS Big Sur 11.0.1 and Xcode 12.2 (non-beta) and also 12.2 Beta 3.
I have notice a tricky thing which could explain why some people couldn't reproduce the issue in #532. Xcode exhibits a different behavior for a SPM project (i.e. opening the Package.swift manifest) and Xcode project (obtained by running swift package generate-xcodeproj from the manifest).
Without the rpath fix above, an executable built by a SPM project works fine but the generated Xcode project fails to launch LLDB per #522.

It was happening to me with a Metal App, but I just had to change the Toolchain to the Xcode 12.2 default and it worked (I was using the " Swift for TensorFlow 0.12 release".
after all, sharing is caring... :)


babelHelpers is not defined, after updating react-native from 0.59.2 to 0.59.8

I'm trying to  updating react-native from 0.59.2 to 0.59.8.
error : babelHelpers is not defined

I cannot run on android device anymore (not tested on Ios or emulator yet )
React Native version:
 React Native Environment Info:
	System:
	  OS: Windows 10
	  CPU: (8) x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
	  Memory: 6.33 GB / 15.79 GB
	Binaries:
	  Node: 10.15.2 - D:\work\nodejs\node.EXE
	  Yarn: 1.13.0 - C:\work\Yarn\bin\yarn.CMD
	  npm: 6.9.0 - D:\work\nodejs\npm.CMD

this was my previous package.json
 {
 	"name": "myApp",
 	"version": "0.0.1",
 	"private": true,
 	"scripts": {
 		"start": "node node_modules/react-native/local-cli/cli.js start",
 		"test": "jest"
 	},
 	"dependencies": {
 		"@react-native-community/async-storage": "^1.3.0",
 		"@react-native-community/netinfo": "^1.4.0",
 		"react": "16.8.6",
 		"react-native": "0.59.2",
 		...
 	},
 	"devDependencies": {
 		"babel-core": "7.0.0-bridge.0",
 		"babel-jest": "24.4.0",
 		"babel-plugin-transform-remove-console": "^6.9.4",
 		"jest": "24.4.0",
 		"metro": "^0.53.1",
 		"metro-react-native-babel-preset": "0.53.0",
 		"react-test-renderer": "16.6.3"
 	},
 	"jest": {
 		"preset": "react-native"
 	}
 }

previous .babelrc
  {
    "env": {
  	"production": {
  	  "plugins": ["transform-remove-console"]
  	}
    }
  }

previous index.android.js
  import { AppRegistry } from 'react-native';
  import App from './src/App'
  AppRegistry.registerComponent('PlantNet', () => App);

i updated package.json
  {
  	"name": "myApp",
  	"version": "0.0.1",
  	"private": true,
  	"scripts": {
  		"start": "node node_modules/react-native/local-cli/cli.js start",
  		"test": "jest"
  	},

  	"dependencies": {
  		"@babel/plugin-proposal-decorators": "^7.0.0-beta.47",
  		"@babel/runtime": "7.0.0-beta.47",
  		"@react-native-community/async-storage": "^1.3.0",
  		"@react-native-community/netinfo": "^1.4.0",
  		"react": "16.8.6",
  		"react-native": "0.59.8",
  		...
  	},
  	"devDependencies": {
  		"babel-core": "7.0.0-bridge.0",
  		"babel-jest": "24.8.0",
  		"babel-plugin-transform-remove-console": "^6.9.4",
  		"babel-preset-react-native": "^4.0.1",
  		"jest": "^24.8.0",
  		"metro": "^0.53.1",
  		"metro-react-native-babel-preset": "0.53.0",
  		"react-test-renderer": "16.6.3"
  	},
  	"jest": {
  		"preset": "react-native"
  	}
  }

i updated .babelrc
  {
  	"env": {
  		"production": {
  			"plugins": ["transform-remove-console"]
  		}
  	},
  	"presets": ["module:metro-react-native-babel-preset"],
  	"plugins": [
  		["@babel/plugin-transform-react-jsx-source"],
  		[
  			"@babel/plugin-proposal-decorators",
  			{
  				"legacy": true
  			}
  		]
  	]
  }

i update index.android.js :
  import {AppRegistry} from 'react-native'

  import applyDecoratedDescriptor from '@babel/runtime/helpers/es6/applyDecoratedDescriptor'
  import initializerDefineProperty from '@babel/runtime/helpers/es6/initializerDefineProperty'

  Object.assign(babelHelpers, {applyDecoratedDescriptor, initializerDefineProperty})

  AppRegistry.registerComponent('PlantNet', () => require('./src/App').default)

Steps To Reproduce
update react-native from 0.59.2 to 0.59.8
I'm lost between pre processing, babel, jest, metro etc. Not sure about anything i do her.
Any tips or working config are welcomed. Thanks

Hello there 👋 this issue seems to be related to your experience upgrading between versions. We know this has been a long lasting pain for the community so starting v0.59 we have introduced a new flow via the new CLI.
I'd suggest you use rn-diff-repo to double check that you did all the necessary steps/changes while upgrading.
Also, maybe it's just a matter of some cache not being cleaned properly? Try running:
rm -rf node_modules;
rm -rf $TMPDIR/react-native-packager-cache-*;
rm -rf $TMPDIR/metro-*;
rm -rf $TMPDIR/react-*;
rm -rf $TMPDIR/haste-*;
watchman watch-del-all;
yarn;
yarn start --reset-cache; (for starting the bundler)

Given that this is not strictly a bug with the library itself I'll close this, but if you can create a repro that has this issue with a freshly created react-native init project we can reopen it and investigate it further 🤗

@alainib did you find a solution for this?

try to use @babel/plugin-transform-runtime


Insufficient CUDA driver version error on CPU-only system

Hi! I am using dali_backend as a image pre-processing model in my pipeline. While when deploying on a system with GPUs it works as expected, when I launch the server in a CPU-only system I have the following error; dali_backend.cc:438 | CUDA runtime API error cudaErrorInsufficientDriver (35).

Hello @ioangatop !
Thank you for your report. I confirm I was able to reproduce your problem. We'll take care of it asap.

@ioangatop ,
I've merged the bugfix. It's going to be included in tritonserver:21.06-py3. Should you like to try it out beforehand, please build dali_backend from upstream, following docker build instructions

Thanks @szalpal!


Running "sh demo.sh" on Colab

Hi, I'm trying to run the demo.sh script on colab (GPU environment) but i get the following error:
loading from ./pretrained/models/topology0
loading from epoch 20000......
load succeed!
loading from ./pretrained/models/topology1
loading from epoch 20000......
load succeed!
Fixing foot contact using IK...
0% 0/50 [00:00<?, ?it/s]
Traceback (most recent call last):
File "demo.py", line 46, in
example('Aj', 'BigVegas', 'Dancing Running Man.bvh', 'intra', './examples/intra_structure')
File "demo.py", line 42, in example
height)
File "/content/deep-motion-editing/retargeting/models/IK.py", line 139, in fix_foot_contact
ik_solver.step()
File "/content/deep-motion-editing/retargeting/models/Kinematics.py", line 172, in step
loss.backward()
File "/usr/local/lib/python3.7/dist-packages/torch/_tensor.py", line 255, in backward
torch.autograd.backward(self, gradient, retain_graph, create_graph, inputs=inputs)
File "/usr/local/lib/python3.7/dist-packages/torch/autograd/init.py", line 149, in backward
allow_unreachable=True, accumulate_grad=True)  # allow_unreachable flag
RuntimeError: one of the variables needed for gradient computation has been modified by an inplace operation: [torch.FloatTensor [324, 3, 3]], which is output 0 of ViewBackward, is at version 37; expected version 35 instead. Hint: enable anomaly detection to find the operation that failed to compute its gradient, with torch.autograd.set_detect_anomaly(True).
[2]
Any clue about what could it be the problem?
Thanks a lot for your time

Hi, I've received similar issue recently in #166 (though in Chinese). I wasn't able to reproduce this error in my environment. You may try to follow this Hint: enable anomaly detection to find the operation that failed to compute its gradient, with torch.autograd.set_detect_anomaly(True). You could also provide more details on your environment (such as python, pytorch version) so I can fix it on my machine.

I'm running into this problem even with the fixed code.  I solved it by downgrading pytorch to 1.4.


Add xvfb to default image so that pyvista can work

Description
https://docs.pyvista.org/user-guide/jupyter/panel.html#configuration-considerations

@iameskild , seems this should be a 5 min operation, no?  Would love to try pyvista out.

Completed here: https://github.com/nebari-dev/nebari-docker-images/pull/20


1.23.1 Broken Intellisense for jscheck type checking for Javascript

VSCode Version:
Version 1.23.1
Commit d0182c3417d225529c6d5ad24b7572815d0de9ac
Date 2018-05-10T17:11:38.209Z
Shell 1.7.12
Renderer 58.0.3029.110
Node 7.9.0
Architecture ia32

OS Version:
Windows 10

Steps to Reproduce:

Start a project with jsconfig and checkJs flag.
My full jsconfig:
 {
 	"compilerOptions": {
 		"target": "ES6",
 		"lib": ["es2017"],
 		"noLib": false,
 		"charset": "utf8",
 		"module": "es6",
 		"checkJs": true
 	},
 	"include": [
 		"typings/**/*",
 		"typings/cpcs.d.ts"
 	],
 	"exclude": [
 		"game/node_modules",
 		"game/gameview.js",
 		"game/gamecore.js",
 		"node_modules",
 		"**/node_modules/*"
 	]
 }

Include typings for your project

See that VSCode does not check typings with JS at all.

Does this issue occur when all extensions are disabled?: Yes
Prior to updating to this version, checkJs and JS with JSDoc annotations + Typescript .d.ts files will allow type checking with JS.
After updating, this is no longer the case. Intellisense no longer detects typings throughout an open file (all variables are any). Enabling checking js through user settings will cause Intellisense to fail finding the typings.

Not sure if this is related but after including "**/*.js",in the include glob pattern the issue seems to be resolved. Possibly undocumented behavior in the updated version?

Try running the JavaScript: Go to project configuration command from a js file in vscode. This should open your jsonfig.json
I suspect the issue is that you have only included files under typings in the current project. Adding **/*.js under include would ensure that all js files as also included in the project (so long as they are not specifically excluded)


Learn a direct application for unique_key

Description & motivation

Closing as this page has been moved and information/examples similar to what has been added here have been updated https://docs.getdbt.com/docs/build/incremental-models#configuring-incremental-strategy


Doesn't log on using the correct computer name after renaming computer

I am renaming the computer and I am passing this for username in the pscredential: new-computer-name\administrator but according to the logs it is storing it as:
[2017-05-17T17:21:04.5294000+00:00:::PID 800] Boxstarter: Securely Storing old-computer-name\Administrator credentials for automatic logon
Is there a way to get around this when launching install-boxstarterscript?

Duplicate of #233.