[Feature]  Picture Tag Component

Feature Request
Is your feature request related to a problem? Please describe.
The library currently supports CldImage giving developers a simple way to use cloudinary assets.
An alternative image-related element is the picture element which allows for different capabilities.
Having this would allow developers to use Cloudinary in a way that makes more sense for Picture-related usage.
Describe the solution you'd like
A basic usage pulled from MDN is:
<picture>
    <source
        srcset="/media/cc0-images/surfer-240-200.jpg"
        media="(min-width: 800px)">
    <img src="/media/cc0-images/painted-hand-298-332.jpg" alt="">
</picture>

Theoretically, it would make sense that the <img above would be the <CldImg, where <picture becomes a wrapper with an additional <source element, leaving something along hte lines of:
<CldPicture>
    <CldSource
        srcset={[{ src: 'cc0-images/surfer', width: 240, height: 200 }]}
        media="(min-width: 800px)"
    />
    <CldImg width="298" height="332" src="cc0-images/painted-hand" alt="" />
</CldPicture>

This is just an idea and am open to ideas and suggestions.

a few things to think about, Matt Kane just recently tweeted about Unpic support:
https://twitter.com/ascorbic/status/1707494849543327828
Additionally, the way Next Image works is using the native tags:
https://nextjs.org/blog/next-13-5#nextimage-improvements
as much as i find it weird using the native  tag to wrap the custom components, wondering what CldPicture would actually do under the hood?

Closing this for now


nodes sometimes not being stylized

sometimes (like when unpacking them from a redprint on a headless) the nodes will not be stylized. not sure how to fix this

seems to be because im nof the allocated user


docs - Top level Joi.object in samples

With the change to Joi@16 (and the requirement for Joi.object
to be present in the route.validate* options) there were
several docs samples where this was missing. This commit
corrects these instances.
Missing the top level Joi.object is associated with:
UnhandledPromiseRejectionWarning: Error: Invalid schema content

Coverage remained the same at 98.823% when pulling 2db5bc2d71139e66d6425cb636ceb099b2b25acd on momiller121:docs-joi.object into 7078d476252f1570dbb84ecddd5575be06c8e950 on glennjones:master.


[Warning Reporting] Fixing the config parsing error

@pwielders so that you won't forget to merge, as I can't add reviewers


When I type:
demands:

java

It only uses agents with java.
When I try:
demands:

java -equal PATH

It says it can't find any agents at all.  Does the path need t be written in some special form?

@Kazuma52 -- thank you for your feedback and question.  Are you following a particular learn.microsoft.com article?  Meanwhile, please consider these resources:

Azure DevOps Services
Azure DevOps on Stack Overflow


Issue265 airplane series - Added all the Airplane codes, pictures for V1.2

Hey, I added all the Airplane Images that were possible and changed the code for the models. I tried to make the models fairer and even, so every model can get used. So don't be too harsh and crank the efficiency of everything too far down as you did with the a350 for example before. Then no one will use it again. I gave every plane a little pro, like a little more efficient or some more seats in the same class. Feel free to suggest and discuss changes.

Starting to go through the changes :)
Some quick questions:

Wondering why did u remove the imageURL? We need that for the link to norebbo. Can you please get the links please? And restore the links on the existing model?
The change should ideally show only ur changes (so the existing lines should not be changed). This is for the ease of going through the changes
Also we would want to preserve the original ordering for airplanes by capacity , the reason for that is we can easily compare the parameters of airplanes of similar scale, with the new ordering now, it's pretty hard to do it

I understand it will be a lot of work for you to do point 2 and 3. Can you at least get point 1 done? I can fix the 2 and 3 later

Hello, yes I can add the Image URLs back, completely forgot about them. And in terms of 2,3 I restructured that in the thought of going after the airplane families.

hehe thanks for adding the url back!
For 2. it's quite important as we want to make sure no existing airplanes are missing or changed. I noticed that one model was missing and some of the names have been changed? The name of an airplane is quite important as it's used as a key for lookup so it will result as missing airplanes if anything is changed ")

Completely unrelated. But r you interested in becoming game admin? The ONLY duty right now is basically ban the bad apples from chat if you found any. It's super easy u can find the extra option in game screen so just a matter of finding the airline in rivals then select the option.
You will have a star next to you airline if you become the admin :)

Sure, I would be more than happy!


Add Tus-Method-Override

This is a tus-specific version of the X-HTTP-Method-Override header to bing PATCH and DELETE methods to every platform. In reality most HTTP clients support these but not all. Examples are the ActionScript runtime inside the browser (http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/net/URLRequest.html#method) and the Java's HTTPUrlConnection.
@vayam @qsorix comments?

Yes, I agree it is needed in some environments.
Why not just use X-HTTP-Method-Override? Because of the X-? If so then in my humble opinion it would be better to leave it out of the protocol and suggest using X-HTTP-Method-Override in the guidelines. While X- is not standardized, it is more practical to use it.
I feel like we're introducing another header to do the same thing and some clients will end up sending both X- and TUS-. For example because they'll be connecting to more things than just a TUS endpoint, and it will be easier to set all such headers in one place.
Another point of view is that most frameworks support X-HTTP-Method-Override and adding a different header to do the same thing only makes implementing TUS harder. A quote from REST framework's specs:

REST framework also supports method overriding via the semi-standard X-HTTP-Method-Override header.

and some Django middleware's specs.

[django-method-override is a] Django middleware that overrides the HTTP method through either a _method form param (Ruby on Rails style) or the X-HTTP-Method-Override header.

We chose the Tus-Method-Override for a few reasons:

As you said, the X- prefix is "deprecated", if you want to call it so.
Every header is either prefixed with Upload- or Tus- and we wanted to stick with this rule.
The X-HTTP-Method-Override is not standardized, it's more a convention.

I know many frameworks support this option but I believe most of them also allow to configure the name of the header which specifies the overriding method.

Added two wording suggestions.
As for Tus-Method-Override vs X-HTTP-Method-Override, since the whole purpose of this header is to accommodate real-world systems that are crippled in their adhering of standards and apparently hard to change, I would be okay accepting this as our only exception to our "We don't do X- prefixes" rule.

I would be okay accepting this as our only exception to our "We don't do X- prefixes" rule.

+1

Thank you for your feedback :)


Use Modern CMake

Use Modern CMake
Support clients using CMake

Consuming this project is trivial now, see test/CMakeLists.txt

Add CI workflow

There are a lot of errors in the code, like missing CTADs

Thank you so much for the contribution. The whole CI stuff is new to me, so it will take me some time to do some research about how the whole thing work then I can review this PR :)

Can you please edit and push to test branch instead?


materialdrawer:5.6.0 without SNAPSHOT

Thanks.

Is it intended on the branch solution_issue_175 ?


Support for 0.9.7

Hi all,
Is there any planned support for the newest CARLA release (0.9.7)? There is another issue (#430 ) describing a bug due to the new Traffic Manager. I just wanted to check before I get my hands dirty with the wrong CARLA install.
Thanks!

Hi,
you can use the current master with 0.9.7. Yet there are still some issues. As long as you use OpenSCENARIO you should be good to go. Problems mostly occur w.r.t route-based scenarios.


npm run prettier

didn't happen in #669, seeing the change in too many PRs now, fixing :)
Cc @ZitaNemeckova
(And adding backport-4.3 as the change was backported.)

@himdel what happened to our CI prettier check? CI used to fail if the code wasn't styled correctly.

Hmm... any chance that's the test-prettier task? If so, I the problem is probably https://github.com/ansible/ansible-hub-ui/pull/351/files#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519R79
I'll take a look into reenabling it in a separate PR :)

that's the one


Centos 8 -  x509: certificate has expired or is not yet valid

Hello,
I am running onto  the following issue on TASK [openshift-4-cluster : Waiting for bootstrap to complete] when trying to create OCP4 cluster.

Issue 1 :

time="2021-06-24T10:39:35+02:00" level=debug msg="  Loading Install Config..."
time="2021-06-24T10:39:35+02:00" level=debug msg="  Loading Bootstrap Ignition Config..."
time="2021-06-24T10:39:35+02:00" level=debug msg="Using Metadata loaded from state file"
time="2021-06-24T10:39:35+02:00" level=debug msg="Reusing previously-fetched Metadata"
time="2021-06-24T10:39:35+02:00" level=info msg="Ignition-Configs created in: /root/hetzner-ocp4/ocp4three and /root/hetzner-ocp4/ocp4three/auth"
time="2021-06-24T10:39:43+02:00" level=debug msg="OpenShift Installer 4.7.2"
time="2021-06-24T10:39:43+02:00" level=debug msg="Built from commit 98e11541c24e95c864328b9b35c64b77836212ed"
time="2021-06-24T10:39:43+02:00" level=info msg="Waiting up to 20m0s for the Kubernetes API at https://api.ocp4three.namategroup.com:6443..."
time="2021-06-24T10:39:43+02:00" level=debug msg="Still waiting for the Kubernetes API: Get \"https://api.ocp4three.namategroup.com:6443/version?timeout=32s\": x509: certificate has expired or is not yet valid: current time 2021-06-24T10:39:43+02:00 is after 2021-06-23T10:46:26Z"

I have tried to set the machine time to before 2021-06-23T10:46:26Z but then I get another issue

Issue 2 :

time="2021-06-23T09:01:55+02:00" level=debug msg="Still waiting for the Kubernetes API: Get \"https://api.ocp4three.namategroup.com:6443/version?timeout=32s\": x509: certificate signed by unknown authority (possibly because of \"crypto/rsa: verification error\" while trying to verify candidate authority certificate \"kube-apiserver-lb-signer\")"

Do you have any suggestions that can help me with these 2 issues ?

Hello,
what is your hardware sizing? When you start the playbook? You can try to delete the cluster with 99-destroy-cluster.yml and recreate with 02-create-cluster.yml.
Thakns
Robert

Hello,
what is your hardware sizing? When you start the playbook? You can try to delete the cluster with 99-destroy-cluster.yml and recreate with 02-create-cluster.yml.
Thakns
Robert
Thank you for the reply, it worked after I destroyed and created the cluster.


Update running-api-node.md

Corrected the grammar and complex statement.
Description
Describe the changes that were made in this pull request. When possible start with the motivations behind the change. Be sure to also include the following information:

Motivation for change?
What was changed?
Link to relevant issues?

Checklist

[ ] Conventional commits were used
[ ] New links to files and images were verified
[ ] For fixes/refactors: all existing references were identified and replaced
[ ] Style guide was reviewed and applied
[ ] Clear code samples were provided
[ ] People were tagged for review

@Scofield-Idehen, Thanks for your contribution.

I love this project, I will keep contributing to the project.
Best regards.
On Mon, 7 Aug 2023, 21:21 Lavanya Kasturi, @.***> wrote:

@Scofield-Idehen https://github.com/Scofield-Idehen, Thanks for your
contribution.
—
Reply to this email directly, view it on GitHub
https://github.com/hirosystems/docs/pull/430#issuecomment-1668518793,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AT6UJUSKYEKNNWYDQ5V2E4LXUFE3TANCNFSM6AAAAAA3ADBNRE
.
You are receiving this because you were mentioned.Message ID:
@.***>


Turborepo doesn't work with pnpm v9

Verify canary release

[X] I verified that the issue exists in the latest Turborepo canary release.

Link to code that reproduces this issue
https://github.com/issueset/turborepo-pnpm9-graph
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Mac
Which canary version will you have in your reproduction?
turbo 1.13.4-canary.4
Describe the Bug
After I update pnpm from v8.15.8 to v9.1.1, turbo cannot create the dependency graph correctly, which causes the incorrect task executing order.
I first thought this is caused by the default configuration updates in pnpm v9.0. However, I updated .npmrc and reset all changed configuration to the same value as pnpm v8, turbo still doesn't work.
Expected Behavior
In my reproduction repo below, running pnpm turbo build --graph should print the same graph for pnpm v8 and v9.
To Reproduce
$ git clone https://github.com/issueset/turborepo-pnpm9-graph
$ cd turborepo-pnpm9-graph
$ pnpm --version
8.15.8
$ pnpm install
$ pnpm turbo build --graph

digraph {
	compound = "true"
	newrank = "true"
	subgraph "root" {
		"[root] @acme/core#build" -> "[root] @acme/eslint-config#build"
		"[root] @acme/core#build" -> "[root] @acme/tsconfig#build"
		"[root] @acme/docs#build" -> "[root] @acme/core#build"
		"[root] @acme/docs#build" -> "[root] @acme/eslint-config#build"
		"[root] @acme/docs#build" -> "[root] @acme/tsconfig#build"
		"[root] @acme/docs#build" -> "[root] @acme/utils#build"
		"[root] @acme/eslint-config#build" -> "[root] ___ROOT___"
		"[root] @acme/tsconfig#build" -> "[root] ___ROOT___"
		"[root] @acme/utils#build" -> "[root] @acme/eslint-config#build"
		"[root] @acme/utils#build" -> "[root] @acme/tsconfig#build"
	}
}

$ git checkout pnpm9
$ pnpm --version
9.1.1
$ pnpm install
$ pnpm turbo build --graph

digraph {
	compound = "true"
	newrank = "true"
	subgraph "root" {
		"[root] @acme/core#build" -> "[root] ___ROOT___"
		"[root] @acme/docs#build" -> "[root] ___ROOT___"
		"[root] @acme/eslint-config#build" -> "[root] ___ROOT___"
		"[root] @acme/tsconfig#build" -> "[root] ___ROOT___"
		"[root] @acme/utils#build" -> "[root] ___ROOT___"
	}
}

Additional context
No response

This was done in #7993 and will go out with next release.
(If you want to use it sooner, support is on the canary releases today.)

@anthonyshew I still can reproduce this issue with the latest v1.13.4-canary.5. I also found that turbo build --graph outputs different results after I run pnpm install again, which is weird. Here are the reproduce steps.
❯ git clone https://github.com/issueset/turborepo-pnpm9-graph

❯ cd turborepo-pnpm9-graph

❯ git checkout pnpm9-1.13.4-canary.5

❯ pnpm install
Scope: all 6 workspace projects
Lockfile is up to date, resolution step is skipped

devDependencies:
+ @acme/eslint-config 0.0.0 <- packages/eslint-config
+ @changesets/cli 2.27.2
+ eslint 8.57.0
+ prettier 3.2.5
+ turbo 1.13.4-canary.5

Done in 2.3s

❯ pnpm why turbo
Legend: production dependency, optional only, dev only

/private/tmp/turborepo-pnpm9-graph

devDependencies:
turbo 1.13.4-canary.5

❯ pnpm turbo build --graph

digraph {
	compound = "true"
	newrank = "true"
	subgraph "root" {
		"[root] @acme/core#build" -> "[root] @acme/eslint-config#build"
		"[root] @acme/core#build" -> "[root] @acme/tsconfig#build"
		"[root] @acme/docs#build" -> "[root] @acme/core#build"
		"[root] @acme/docs#build" -> "[root] @acme/eslint-config#build"
		"[root] @acme/docs#build" -> "[root] @acme/tsconfig#build"
		"[root] @acme/docs#build" -> "[root] @acme/utils#build"
		"[root] @acme/eslint-config#build" -> "[root] ___ROOT___"
		"[root] @acme/tsconfig#build" -> "[root] ___ROOT___"
		"[root] @acme/utils#build" -> "[root] @acme/eslint-config#build"
		"[root] @acme/utils#build" -> "[root] @acme/tsconfig#build"
	}
}

❯ pnpm install
Scope: all 6 workspace projects
Lockfile is up to date, resolution step is skipped
Already up to date
Done in 584ms

❯ pnpm turbo build --graph

digraph {
	compound = "true"
	newrank = "true"
	subgraph "root" {
		"[root] @acme/core#build" -> "[root] ___ROOT___"
		"[root] @acme/docs#build" -> "[root] ___ROOT___"
		"[root] @acme/eslint-config#build" -> "[root] ___ROOT___"
		"[root] @acme/tsconfig#build" -> "[root] ___ROOT___"
		"[root] @acme/utils#build" -> "[root] ___ROOT___"
	}
}

Will re-open so we don't forget to take another look.

had the same issue, upgrading to<EMAIL_ADDRESS>solved it for me as mentioned in https://github.com/vercel/turbo/issues/7993

@ocavue
Can you make sure you rebuild your lockfile on the upgrade? I just tried your reproduction repo with 1.13.4 and got the correct graph:
[0 olszewski@chriss-mbp] /tmp/turborepo-pnpm9-graph $ turbo build --graph

digraph {
        compound = "true"
        newrank = "true"
        subgraph "root" {
                "[root] @acme/core#build" -> "[root] @acme/eslint-config#build"
                "[root] @acme/core#build" -> "[root] @acme/tsconfig#build"
                "[root] @acme/docs#build" -> "[root] @acme/core#build"
                "[root] @acme/docs#build" -> "[root] @acme/eslint-config#build"
                "[root] @acme/docs#build" -> "[root] @acme/tsconfig#build"
                "[root] @acme/docs#build" -> "[root] @acme/utils#build"
                "[root] @acme/eslint-config#build" -> "[root] ___ROOT___"
                "[root] @acme/tsconfig#build" -> "[root] ___ROOT___"
                "[root] @acme/utils#build" -> "[root] @acme/eslint-config#build"
                "[root] @acme/utils#build" -> "[root] @acme/tsconfig#build"
        }
}

[0 olszewski@chriss-mbp] /tmp/turborepo-pnpm9-graph $ pnpm --version
9.3.0
[0 olszewski@chriss-mbp] /tmp/turborepo-pnpm9-graph $ turbo --version
1.13.4

I can still reproduce this issue with the latest<EMAIL_ADDRESS>Here are the reproduce steps:
/tmp ❯ git clone https://github.com/issueset/turborepo-pnpm9-graph -b pnpm9-2.0.4 test-dir-1
Cloning into 'test-dir-1'...
remote: Enumerating objects: 123, done.
remote: Counting objects: 100% (123/123), done.
remote: Compressing objects: 100% (69/69), done.
remote: Total 123 (delta 52), reused 116 (delta 45), pack-reused 0
Receiving objects: 100% (123/123), 176.74 KiB | 512.00 KiB/s, done.
Resolving deltas: 100% (52/52), done.

/tmp ❯ cd test-dir-1

/tmp/test-dir-1 pnpm9-2.0.4 ❯ pnpm --version
9.4.0

/tmp/test-dir-1 pnpm9-2.0.4 ❯ pnpm install
Scope: all 6 workspace projects
Lockfile is up to date, resolution step is skipped
Packages: +600
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Progress: resolved 600, reused 599, downloaded 0, added 600, done

devDependencies:
+ @acme/eslint-config 0.0.0 <- packages/eslint-config
+ @changesets/cli 2.27.5
+ eslint 8.57.0
+ prettier 3.3.2
+ turbo 2.0.4

Done in 2.6s

/tmp/test-dir-1 pnpm9-2.0.4 ❯ pnpm why turbo
Legend: production dependency, optional only, dev only

turborepo-pnpm9-graph /private/tmp/test-dir-1

devDependencies:
turbo 2.0.4

/tmp/test-dir-1 pnpm9-2.0.4 ❯ pnpm turbo build --graph --log-order grouped

digraph {
	compound = "true"
	newrank = "true"
	subgraph "root" {
		"[root] @acme/core#build" -> "[root] ___ROOT___"
		"[root] @acme/docs#build" -> "[root] ___ROOT___"
		"[root] @acme/eslint-config#build" -> "[root] ___ROOT___"
		"[root] @acme/tsconfig#build" -> "[root] ___ROOT___"
		"[root] @acme/utils#build" -> "[root] ___ROOT___"
	}
}

/tmp/test-dir-1 pnpm9-2.0.4 ❯

I tried clean pnpm-lock.yaml but it doesn't work:
/tmp ❯ git clone https://github.com/issueset/turborepo-pnpm9-graph -b pnpm9-2.0.4 test-dir-2
Cloning into 'test-dir-2'...
remote: Enumerating objects: 123, done.
remote: Counting objects: 100% (123/123), done.
remote: Compressing objects: 100% (69/69), done.
remote: Total 123 (delta 52), reused 116 (delta 45), pack-reused 0
Receiving objects: 100% (123/123), 176.74 KiB | 514.00 KiB/s, done.
Resolving deltas: 100% (52/52), done.

/tmp ❯ cd test-dir-2

/tmp/test-dir-2 pnpm9-2.0.4 ❯ pnpm --version
9.4.0

/tmp/test-dir-2 pnpm9-2.0.4 ❯ rm -rf pnpm-lock.yaml

/tmp/test-dir-2 pnpm9-2.0.4 !1 ❯ pnpm install
Scope: all 6 workspace projects
 WARN  5 deprecated subdependencies found<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Packages: +600
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Progress: resolved 649, reused 599, downloaded 0, added 600, done

devDependencies:
+ @acme/eslint-config 0.0.0 <- packages/eslint-config
+ @changesets/cli 2.27.5
+ eslint 8.57.0 (9.5.0 is available)
+ prettier 3.3.2
+ turbo 2.0.4

Done in 11.2s

/tmp/test-dir-2 pnpm9-2.0.4 11s ❯ pnpm turbo build --graph --log-order grouped

digraph {
	compound = "true"
	newrank = "true"
	subgraph "root" {
		"[root] @acme/core#build" -> "[root] ___ROOT___"
		"[root] @acme/docs#build" -> "[root] ___ROOT___"
		"[root] @acme/eslint-config#build" -> "[root] ___ROOT___"
		"[root] @acme/tsconfig#build" -> "[root] ___ROOT___"
		"[root] @acme/utils#build" -> "[root] ___ROOT___"
	}
}

/tmp/test-dir-2 pnpm9-2.0.4 ❯

I can still reproduce this issue with the latest<EMAIL_ADDRESS>Here are the reproduce steps:
/tmp ❯ git clone https://github.com/issueset/turborepo-pnpm9-graph -b pnpm9-2.0.4 test-dir-1
Cloning into 'test-dir-1'...
remote: Enumerating objects: 123, done.
remote: Counting objects: 100% (123/123), done.
remote: Compressing objects: 100% (69/69), done.
remote: Total 123 (delta 52), reused 116 (delta 45), pack-reused 0
Receiving objects: 100% (123/123), 176.74 KiB | 512.00 KiB/s, done.
Resolving deltas: 100% (52/52), done.

/tmp ❯ cd test-dir-1

/tmp/test-dir-1 pnpm9-2.0.4 ❯ pnpm --version
9.4.0

/tmp/test-dir-1 pnpm9-2.0.4 ❯ pnpm install
Scope: all 6 workspace projects
Lockfile is up to date, resolution step is skipped
Packages: +600
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Progress: resolved 600, reused 599, downloaded 0, added 600, done

devDependencies:
+ @acme/eslint-config 0.0.0 <- packages/eslint-config
+ @changesets/cli 2.27.5
+ eslint 8.57.0
+ prettier 3.3.2
+ turbo 2.0.4

Done in 2.6s

/tmp/test-dir-1 pnpm9-2.0.4 ❯ pnpm why turbo
Legend: production dependency, optional only, dev only

turborepo-pnpm9-graph /private/tmp/test-dir-1

devDependencies:
turbo 2.0.4

/tmp/test-dir-1 pnpm9-2.0.4 ❯ pnpm turbo build --graph --log-order grouped

digraph {
	compound = "true"
	newrank = "true"
	subgraph "root" {
		"[root] @acme/core#build" -> "[root] ___ROOT___"
		"[root] @acme/docs#build" -> "[root] ___ROOT___"
		"[root] @acme/eslint-config#build" -> "[root] ___ROOT___"
		"[root] @acme/tsconfig#build" -> "[root] ___ROOT___"
		"[root] @acme/utils#build" -> "[root] ___ROOT___"
	}
}

/tmp/test-dir-1 pnpm9-2.0.4 ❯

I tried clean pnpm-lock.yaml but it doesn't work:
/tmp ❯ git clone https://github.com/issueset/turborepo-pnpm9-graph -b pnpm9-2.0.4 test-dir-2
Cloning into 'test-dir-2'...
remote: Enumerating objects: 123, done.
remote: Counting objects: 100% (123/123), done.
remote: Compressing objects: 100% (69/69), done.
remote: Total 123 (delta 52), reused 116 (delta 45), pack-reused 0
Receiving objects: 100% (123/123), 176.74 KiB | 514.00 KiB/s, done.
Resolving deltas: 100% (52/52), done.

/tmp ❯ cd test-dir-2

/tmp/test-dir-2 pnpm9-2.0.4 ❯ pnpm --version
9.4.0

/tmp/test-dir-2 pnpm9-2.0.4 ❯ rm -rf pnpm-lock.yaml

/tmp/test-dir-2 pnpm9-2.0.4 !1 ❯ pnpm install
Scope: all 6 workspace projects
 WARN  5 deprecated subdependencies found<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Packages: +600
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Progress: resolved 649, reused 599, downloaded 0, added 600, done

devDependencies:
+ @acme/eslint-config 0.0.0 <- packages/eslint-config
+ @changesets/cli 2.27.5
+ eslint 8.57.0 (9.5.0 is available)
+ prettier 3.3.2
+ turbo 2.0.4

Done in 11.2s

/tmp/test-dir-2 pnpm9-2.0.4 11s ❯ pnpm turbo build --graph --log-order grouped

digraph {
	compound = "true"
	newrank = "true"
	subgraph "root" {
		"[root] @acme/core#build" -> "[root] ___ROOT___"
		"[root] @acme/docs#build" -> "[root] ___ROOT___"
		"[root] @acme/eslint-config#build" -> "[root] ___ROOT___"
		"[root] @acme/tsconfig#build" -> "[root] ___ROOT___"
		"[root] @acme/utils#build" -> "[root] ___ROOT___"
	}
}

/tmp/test-dir-2 pnpm9-2.0.4 ❯

Did you ever get this resolved? Going back to<EMAIL_ADDRESS>causes all sorts of new issues as well, which might be specific to my dependencies, I'm not real sure. Everything was working with<EMAIL_ADDRESS>until I didn't deploy any updates for about a week, and all of a sudden the builds fail without any new dependencies or changes to pnpm or Next configs. This is indescribably frustrating.

I believe this has been fixed in 2.0.6-canary.0 please try it out and reopen if the issue persists.

Unfortunately, this occurs again in 2.2.3

Still having issues with this, sticking to version pnpm version 8 until this is fixed.

@jpmadrigal07 Can you open a new Issue with a reproduction? Thank you!


Don't set XHR content-type if postData is FormData.

Browser will automatically set mime type and boundary.

Thanks for the PR!  Just one comment

Good catch. Thanks for SPF. Excited to get it deployed on my site.


I want to add java program to count mase path in the chessboard

This program is the solution of  very popular question mase path problem.
language used *.
-> Java

Please fill this template properly

Please fill this template properly

@kaustubhgupta how do i fill the template i did not understand . can you please explain .

Edit the template, replace the placeholder text with your words, don't remove the headings.

Edit the template, replace the placeholder text with your words, don't remove the headings.

@kaustubhgupta does it fine ?


change

!bench

!bench

!bench

Wrapping all of rw with transparencyMode := .reducible doesn't seem to yield much benefit


Rideable not working only for players pf2e

I just installed Rideable and am having an issue using the module in a player account, but it works fine on a GM account. Using either the mount hotkey, mount button, or mount macro have no effect when logged in as a player account.
I have disabled all modules other than Rideable, routinglib, and the module for the adventure path I'm using.
I've confirmed that the player is the owner of both the mount and rider actors.
There's no errors in the console logs, but I do notice that if I right click on the mount actor, I see a log from MountingScript.js:455:13 which differs whether I'm logged in as the player or GM. This is from when I have both actors on the same scene, but not mounted.
As a GM I see:
Array [ {…} ]
0: Object { constructed: true, name: "Rosa", displayName: 20, … }
length: 1
<prototype>: Array []

(just the mount actor)
but as a player I see:
Array [ {…}, {…} ]
0: Object { constructed: true, name: "Rosa", displayName: 20, … }
1: Object { constructed: true, name: "Esmera", displayName: 20, … }
length: 2
<prototype>: Array []

(both the mount and the actor)
Module settings:
Player:

GM:

Foundry: version 11.315
Rideable: version 2.19.5

For Rideable to work a GM has to be logged in.

That would explain it. I was testing by myself, switching between player
and GM accounts. Thanks!
On Sun, Feb 11, 2024, 3:47 PM Saibot393 @.***> wrote:

For Rideable to work a GM has to be logged in.
—
Reply to this email directly, view it on GitHub
https://github.com/Saibot393/Rideable/issues/65#issuecomment-1937865286,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABBT5D63I6PK7UXRH6PPPGDYTEU6FAVCNFSM6AAAAABDDZKX32VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZXHA3DKMRYGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Note that a lot of automation modules that allow players to do things they normally couldn't, use similar ways of "outplaying" foundrys permission limitations, and therefore need a GM to be online


Possible to connect to Docker-hosted site on local network?

Hi Mahmoud,
Do you know the best way to access a Docker-hosted site across a local network?
We're running a centralised admin + kiosks system which we'd like to test out on Docker (the admin machine will be hosted, the kiosks connect to it) but have had difficulty accessing from other machines on anything other than the a machine's default localhost.
Browser sync looks like it might be an option, but is there anything built into Docker for this?
Many thanks!
Dave

Hi @davestewart, I never tried that thus I don't know. I would suggest asking this on the Docker repository. Best of luck.


chore(meta): package version

Codecov Report

Merging #32 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #32   +/-   ##
=======================================
  Coverage   99.09%   99.09%
=======================================
  Files          15       15
  Lines         222      222
  Branches       43       45    +2
=======================================
  Hits          220      220
  Misses          2        2

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 73c5c4e...42c1ed1. Read the comment docs.


navBar with search bar

i want to add navbar with search bar in js html and css
GSSOC contributor

I am very interested in solving this issue and add a creative navbar with search bar using html , css and javascript.
GSSOC contributor

@swapnilsparsh yes

@swapnilsparsh this is my work can i make pull request?

@swapnilsparsh yes

Can you explain where you will use JS in this?

@swapnilsparsh if we click on search icon it hides all the list element with animation and display the search bar and vice versa

please assign me


Commented out code that prevents successful build

goal was a clean build and it appears that's what we have. Merging.


Make MatrixClient asynchronous

I haven't tested this yet, and I plan on splitting out the monster commit into
actual bite-size digestible commits, but I'm not entirely sure when I'll get
back working on this again, and there's a chance someone might find it useful.
Also, this is kind of a monstrous PR in scope, so I thought I should let
@Half-Shot know that it was incoming.
I'll sign off on this properly, too once I split out that single commit; don't
worry.
Closes #127

This PR is substantially ready. It's worked in all manual testing I've done, and
it doesn't break any automated tests. I just need to do the following things
before declaring it not a WIP.

[ ] Write some tests for new asynchronous api (not entirely sure how I'll go
about this. Any help/advice appreciated)
[ ] Make this into a nice set of commits for review.

The following will be handled in a later PR.

[ ] Make login and registration apis asynchronous.
[ ] Make syncing multi-threaded rather than single-threaded.

Additionally, I have the following question that maybe @Half-Shot or, I dunno,
@erikjohnston (he does python, right? Please ping other members of core team who
may be better suited to answer questions for this sdk) might be able to help with:

Should I write a series of locks for anything that is get/set from the
matrix homeserver or should that be handled at a higher level? (e.g. if
there's an ongoing request to set displayname, should that stop any
requests to get displayname until it finishes?)

could this PR pave road to automatic (in SDK) reconnection retrying to HS after connection loss?

@4nd3r this could definitely make that easier. #123 is unrelated. Most of
the issues people have with retrying are with the sync thread, which is
actually already supposed to retry, but thanks to the bug in #131, doesn't
really.
But if what you're looking for is automatic retry for all requests, yes,
making the client async means we just have to implement that once within the
queue class.

Note that this will make fixing #6 significantly easier.

Any updates on this ?

@subins2000 so kind of the state of the project right now:
I'm waiting on @Half-Shot (or anyone else familiar with the layout of the project) to review #160. After that, I'm planning on doing a 0.1.0 release, and then after the release, I'll be polishing this up (getting rid of merge conflicts), adding some tests, and then getting this reviewed to potentially merge.


git checkout is failing for this repo, please sort this!

Describe the bug

How to reproduce or log data

Expected behavior

It should checkout properly.
Device/Version information (please complete the following information):

Device: [e.g. EON/EON Gold/comma two]
Dongle ID: [e.g. 77611a1fac303767, can be found in Settings -> Device -> Dongle ID or my.comma.ai/useradmin]
Route: [e.g. 77611a1fac303767|2020-05-11--16-37-07, can be found in my.comma.ai/useradmin]
Version: [commit hash when on a non-release branch, or version number when on devel or release2 (e.g. 0.7.6)]
Car make/model: [e.g. Toyota Prius 2016]

Additional context

$ git clone https://github.com/commaai/openpilot.git                                                                                [14:29:33]
Cloning into 'openpilot'...
remote: Enumerating objects: 1, done.
remote: Counting objects: 100% (1/1), done.
remote: Total 24165 (delta 0), reused 0 (delta 0), pack-reused 24164
Receiving objects: 100% (24165/24165), 1004.47 MiB | 6.08 MiB/s, done.
Resolving deltas: 100% (13003/13003), done.
git-lfs filter-process: git-lfs: command not found
fatal: the remote end hung up unexpectedly
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'
FAIL: 128

$ git clone https://github.com/commaai/openpilot.git [14:29:33]
...
git-lfs filter-process: git-lfs: command not found

You'll need Git Large File Storage (LFS) installed in order to checkout master.

Okay, sorry. I did not know something like that existed. Maybe a note in the README.MD file will help. Thank you for enlightening.

Thank you!
Sincerely,
Rudhisundar Beura
Karama pradhana Biswa Rachi Rakhaa | Jo jas karahi So Tas phal Chakhaa
||Hoi Hai soi jo Raama Rachi Rakha |
*Ko Kari tarak badhavahin Sakha ||   ...Tulsi Das's magnum opus:
RamaCharitManasa, Bala Kanda   *
On Sun, 21 Jun 2020 at 17:04, Jason Young<EMAIL_ADDRESS>wrote:

Closed #1754 https://github.com/commaai/openpilot/issues/1754.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/commaai/openpilot/issues/1754#event-3465584761, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AF5GVFLDHSQS4KMOUVKK6QLRXYOO3ANCNFSM4OD23XIA
.


catalog pre-preprocessing

time-dependent forecasts require special processing in order to compute t- and w-tests along with cumulative versions of the consistency tests. this will need to be incorporated in order to evaluate the forecasts consistently with what was done in csep1.

for the time being we will support cumulative number tests by summing rates in space-magnitude bins. the t and w tests can be made cumulative by adding the likelihood over independent time-periods. both of these do not require changes to the existing csep1 test implementations. im closing now for this reason.


Could not find any resources appropriate for the specified culture or the neutral culture

Hello Guys,
I try to install Glimpse for my MVC2 application. I installed the latest versions of Glimpse, Glimpse.AspNet, Glimpse.MVC2 . It works greatest for my localhost, and I tried to pull Glimpse to our test server. After deployment and tunes web.config I tried to open glimpse.axd page but faced with the following problem:

2015-05-28 14:00:00,489 [11:ERROR(Errors)] System.Resources.MissingManifestResourceException: Could not find any resources appropriate for the specified culture or the neutral culture.  Make sure "Glimpse.AspNet.Resources.resources" was correctly embedded or linked into assembly "Glimpse.AspNet" at compile time, or that all the satellite assemblies required are loadable and fully signed.
at System.Resources.ResourceManager.InternalGetResourceSet(CultureInfo culture, Boolean createIfNotExists, Boolean tryParents)
at System.Resources.ResourceManager.InternalGetResourceSet(CultureInfo culture, Boolean createIfNotExists, Boolean tryParents)
at System.Resources.ResourceManager.InternalGetResourceSet(CultureInfo culture, Boolean createIfNotExists, Boolean tryParents)
at System.Resources.ResourceManager.GetString(String name, CultureInfo culture)
at Glimpse.AspNet.Resources.get_ProcessRequestMissingRuntime()
at Glimpse.AspNet.HttpHandler.ProcessRequest(HttpContextBase context)
at Glimpse.AspNet.HttpHandler.ProcessRequest(HttpContext context)

I googled this error message on the many sites but I haven't found nothing that help me.
May be you can? Thanks.

Unfortunately there isn't much I can do at the moment. That said, the progress is being tracked at #226


[ALLUXIO-2206] Fix a bug in LocalFirstPolicy and RoundRobinPolicy

@peisun1115 thanks for the fix! Could you create a ticket for this?

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/11210/Build result: FAILURE[...truncated 1445 lines...][JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/pom.xml to org.alluxio/alluxio-shell/1.3.0-SNAPSHOT/alluxio-shell-1.3.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/oss/pom.xml to org.alluxio/alluxio-underfs-oss/1.3.0-SNAPSHOT/alluxio-underfs-oss-1.3.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/oss/target/alluxio-underfs-oss-1.3.0-SNAPSHOT.jar to org.alluxio/alluxio-underfs-oss/1.3.0-SNAPSHOT/alluxio-underfs-oss-1.3.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/oss/target/alluxio-underfs-oss-1.3.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-underfs-oss/1.3.0-SNAPSHOT/alluxio-underfs-oss-1.3.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/client/pom.xml to org.alluxio/alluxio-keyvalue-client/1.3.0-SNAPSHOT/alluxio-keyvalue-client-1.3.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/hdfs/pom.xml to org.alluxio/alluxio-underfs-hdfs/1.3.0-SNAPSHOT/alluxio-underfs-hdfs-1.3.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/hdfs/target/alluxio-underfs-hdfs-1.3.0-SNAPSHOT.jar to org.alluxio/alluxio-underfs-hdfs/1.3.0-SNAPSHOT/alluxio-underfs-hdfs-1.3.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/hdfs/target/alluxio-underfs-hdfs-1.3.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-underfs-hdfs/1.3.0-SNAPSHOT/alluxio-underfs-hdfs-1.3.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/swift/pom.xml to org.alluxio/alluxio-underfs-swift/1.3.0-SNAPSHOT/alluxio-underfs-swift-1.3.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/swift/target/alluxio-underfs-swift-1.3.0-SNAPSHOT.jar to org.alluxio/alluxio-underfs-swift/1.3.0-SNAPSHOT/alluxio-underfs-swift-1.3.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/swift/target/alluxio-underfs-swift-1.3.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-underfs-swift/1.3.0-SNAPSHOT/alluxio-underfs-swift-1.3.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/s3a/pom.xml to org.alluxio/alluxio-underfs-s3a/1.3.0-SNAPSHOT/alluxio-underfs-s3a-1.3.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/s3a/target/alluxio-underfs-s3a-1.3.0-SNAPSHOT.jar to org.alluxio/alluxio-underfs-s3a/1.3.0-SNAPSHOT/alluxio-underfs-s3a-1.3.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/s3a/target/alluxio-underfs-s3a-1.3.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-underfs-s3a/1.3.0-SNAPSHOT/alluxio-underfs-s3a-1.3.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/pom.xml to org.alluxio/alluxio-examples/1.3.0-SNAPSHOT/alluxio-examples-1.3.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/pom.xml to org.alluxio/alluxio-core-server/1.3.0-SNAPSHOT/alluxio-core-server-1.3.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/common/pom.xml to org.alluxio/alluxio-keyvalue-common/1.3.0-SNAPSHOT/alluxio-keyvalue-common-1.3.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/pom.xml to org.alluxio/alluxio-underfs/1.3.0-SNAPSHOT/alluxio-underfs-1.3.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/glusterfs/pom.xml to org.alluxio/alluxio-underfs-glusterfs/1.3.0-SNAPSHOT/alluxio-underfs-glusterfs-1.3.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/glusterfs/target/alluxio-underfs-glusterfs-1.3.0-SNAPSHOT.jar to org.alluxio/alluxio-underfs-glusterfs/1.3.0-SNAPSHOT/alluxio-underfs-glusterfs-1.3.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/glusterfs/target/alluxio-underfs-glusterfs-1.3.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-underfs-glusterfs/1.3.0-SNAPSHOT/alluxio-underfs-glusterfs-1.3.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/integration/pom.xml to org.alluxio/alluxio-integration/1.3.0-SNAPSHOT/alluxio-integration-1.3.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/pom.xml to org.alluxio/alluxio-keyvalue/1.3.0-SNAPSHOT/alluxio-keyvalue-1.3.0-SNAPSHOT.pomchannel stopped
Test FAILed.

I don't think this is a bug. For local first, when tiered storage is available and MEM availability is low, we still want to choose the local and evict stale blocks.

I think the available capacity includes tiered storage capacity.  See MasterWorkerInfo.java & line=131 .

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/11211/Failed Tests: 21org.alluxio:alluxio-tests: 21alluxio.client.IsolatedFileSystemIntegrationTest.lockBlockTest1alluxio.client.IsolatedFileSystemIntegrationTest.lockBlockTest2alluxio.client.IsolatedFileSystemIntegrationTest.lockBlockTest3alluxio.client.IsolatedFileSystemIntegrationTest.unlockBlockTest1alluxio.client.IsolatedFileSystemIntegrationTest.unlockBlockTest2alluxio.client.IsolatedFileSystemIntegrationTest.unlockBlockTest3alluxio.client.RemoteBlockInStreamIntegrationTest.remoteReadLock[0]alluxio.client.RemoteBlockInStreamIntegrationTest.readTest4[0]alluxio.client.RemoteBlockInStreamIntegrationTest.readTest5[0]alluxio.client.RemoteBlockInStreamIntegrationTest.readTest6[0]alluxio.client.RemoteBlockInStreamIntegrationTest.remoteReadLock[1]alluxio.client.RemoteBlockInStreamIntegrationTest.readTest4[1]alluxio.client.RemoteBlockInStreamIntegrationTest.readTest5[1]alluxio.client.RemoteBlockInStreamIntegrationTest.readTest6[1]alluxio.shell.command.PinCommandTest.setPinalluxio.worker.BlockServiceHandlerIntegrationTest.evictionalluxio.worker.DataServerIntegrationTest.readMultiFiles[0]alluxio.worker.DataServerIntegrationTest.readMultiFiles[1]alluxio.worker.block.meta.TieredStoreIntegrationTest.pinFilealluxio.worker.block.meta.TieredStoreIntegrationTest.unpinFilealluxio.worker.block.meta.TieredStoreIntegrationTest.promoteBlock
Test FAILed.

Sure. I meant even without tiered storage, we can still evict and discard old blocks in favor for the new ones. @apc999

OK. If that is the case, then it is probably better change the default policy to be a different one? I feel it is confusing to the user when it fails to write to Alluxio though Alluxio has enough capacity. When LocalFirstPolicy is used, Alluxio basically becomes a local buffer cache because it is likely that every worker has enough total capacity to hold a block.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/11213/
Test PASSed.

IMO, a write policy might simply be the order of the following four:
(1) Writing to Local without Eviction
(2) Writing to Local with Eviction
(3) Writing to Remote without Eviction
(4) Writing to Remote with Eviction
And the current local-first realizes (1)&(2) > (3) > (4)
and by this PR, it makes local-first to be (1) > (3) > (4)
I guess there is no right or wrong answer to the policy---both may have legit use cases.
Should we probably just come up with a richer set of policies for users to configure?

I think the current implementation is (1) = (2) > (3) = (4) .
By this PR, (1) > (3) > (2) > (4)
I can keep the current implementation and come up with a different policy.
a. I think it is better to change the default policy. How do you think?
b. I feel the current one is less useful especially when the data is in remote object store such as s3 (the usecase we target most?) . In that sense, maybe we should remove that to make it less confusing. But i have no problem with keeping it there.

I think we should add more policies, and then we can discuss which one should be default. These can be separate tasks.

+1 for what @yupeng9  proposes. @peisun1115 does that sound good to you?
Also, we should have meaningful names and sufficient docs on these policies (including existing ones)

@yupeng9 @apc999 I can close this PR for now given that you two don't think this is a bug and work on adding more policies later.


Report Portal returned error CHILD_START_TIME_EARLIER_THAN_PARENT

Client version 5.0.11
Agent version 5.0.0-RC-1
Some scenarios are not present in RP launch but were run in GitLab job.
Logs contain error:
28-10-2020 07:35:57.204 [rp-io-8] ERROR c.e.r.utils.SubscriptionUtils.onError - Start test item completed with error
com.epam.reportportal.exception.ReportPortalException: Report Portal returned error
Status code: 406
Status message: Not Acceptable
Error Message: Start time of child ['Wed Oct 28 07:35:57 UTC 2020'] item should be same or later than start time ['2020-10-28T07:35:57.085'] of the parent item/launch '15122524'
Error Type: CHILD_START_TIME_EARLIER_THAN_PARENT
at com.epam.reportportal.service.ReportPortalErrorHandler.handleError(ReportPortalErrorHandler.java:85)
at com.epam.reportportal.service.ReportPortalErrorHandler.handle(ReportPortalErrorHandler.java:61)
at com.epam.reportportal.restendpoint.http.HttpClientRestEndpoint$1.subscribe(HttpClientRestEndpoint.java:526)
at io.reactivex.internal.operators.maybe.MaybeCreate.subscribeActual(MaybeCreate.java:45)
at io.reactivex.Maybe.subscribe(Maybe.java:4290)
at io.reactivex.internal.operators.maybe.MaybeSubscribeOn$SubscribeTask.run(MaybeSubscribeOn.java:54)
at io.reactivex.internal.schedulers.ScheduledDirectTask.call(ScheduledDirectTask.java:38)
at io.reactivex.internal.schedulers.ScheduledDirectTask.call(ScheduledDirectTask.java:26)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
Reproduces randomly on different launches.

Fixed: https://github.com/reportportal/agent-java-cucumber6/releases/tag/5.0.1


Update Fluid Mixins.

This is a quick follow up PR with some improvements to Fluid Mixins, mainly based around tighter enforcement of some OOP principles.

Default mixins have been renamed to global mixins (that's what I had originally written in the comments and I think it is a more appropriate name).
Applying named mixins is now done on the object itself via object:apply_mixin('foo').
Objects are now aware of which named mixins have been applied.
It is now possible to check if an object has a named mixin applied by calling object:has_mixin('foo'). It is also possible to check if a global mixin is in place by calling object:has_mixin('global').
Named mixins can only be registered once and cannot be called 'global'.
Properties cannot be overridden with methods and vice-versa.
Errors are now caught and rethrown so that they display at the correct level with the correct line number and the correct method name.
Aliased table.unpack for Lua 5.1 support.

Error handling proved somewhat tricky to get right but it's turned out better than I initially expected. The last remaining small issue with errors is that for methods called with a colon (eg dialog:ExecuteModal()), any 'bad argument' errors will have the argument number off by one (because under the hood the actual function call is not made with a colon). To fix this properly, there would need to be some way of differentiating whether a function was originally called with a dot or a colon but I don't think that's possible. The other option is that I can reduce all bad argument errors by 1, which would fix it for colon calls, but break it for dot calls. I guess it would depend on which type of call is more common. It's a very minor issue, but I thought I'd mention it.

I think the argument numbers being off by 1 for : calls is acceptable. Certainly better than making all the others be off by one.

I've just thought of a further improvement I can make with error handling. Marking as draft for now.

I have updated the error handling for mixins. It should be good to go now.
@rpatters1
Regarding LuaJIT compatibility: mixins should work but I haven't had the time to test it yet. I'll have the time to do that in a week or two. The only question mark in my mind is around how compilation affects error handling, in particular whether the error level information includes both a file and a line number.

I'm cool with it. Just waiting for comment from @Nick-Mazuk.


Update CONTRIBUTING doc

update doc to reflect the fact that
we are going to use a single meeting document
A decision taken place in community meeting
on 12.07.2022
Signed-off-by: Adrian Chiris<EMAIL_ADDRESS>

LGTM


Add steps to get started in README.md

@sfc-gh-afedorov Does this not address the requirement here? https://github.com/Snowflake-Labs/terraform-snowflake-aws-geff/blob/main/README.md#setup-instructions

Let me know what other specific instructions you want added.

yes, iirc the "Setup Instructions" section was added since this and is great, ty

Oh I see. I thought this was new. 👍

Added more SQL specific instructions: https://github.com/Snowflake-Labs/terraform-snowflake-aws-geff


(PUP-5616) fixes to improve error display

adds error display for device commands, which used to fail silently
removes duplicate command input from the error output

This also removes some tests which caused never-achieve-convergence
as it was dropping device properties that could be supplied as input

I just fixed the test failure, and added another test for VLAN description validity. The Cisco specs all say alphanumeric no spaces or special characters, and our regex requires matching \w so this error is more useful than the previous situation which would constantly fail to converge.

Thanks @jorhett - we're having our PR triage tomorrow, and I've added this to the discussion list.

Ping @LuvCurves, we're looking for a way to review this. Do you have any thoughts on this change?

Looks good to me.  We now have VMs in the VMpooler that can be used for verification.

It would be nice to see more testing on this, but I'm not sure what it would look like. @LuvCurves if you think this is correct behavior go ahead and merge it.

@binford2k This didn't make it in time for 4.4.0. You could retarget stable for 4.4.1 or we can merge to master for 4.5.0.

ping @jorhett

Not sure what you want from me, as I can't affect your release targets can I?
Do I need to merge against a different branch?

@jorhett If you want this to go into 4.1.0 retarget the PR against stable, otherwise it will go into 4.5.0. I think @joshcooper  is saying it is up to you.

Forgive my ignorance, but I don't know what "target against stable" means in terms of an actionable process. It's been different at every firm I've worked with, and you guys are much process heavier than most.
As far as I know the rest API feature for this still doesn't work, so I must submit a new PR yes?

"target against stable"
On your branch: git rebase stable
close this PR and open a new that "targets" stable.
We are doing release work a.t.m, so will take a day or two before being ready to merge to stable.

I think at this point this has missed the boat for 4.4.0. Leaving it targeted at master for 4.5.0 is the way to go, and we should be able to get this merged in as soon as we have bandwidth post-4.4.40 release.

@jorhett which means that the way it is now targeting master branch is correct (it is for 4.5.0 now).

Sounds good. Although it has missed 3 releases now, so what can we do to get this included in the next?

Hint: there is a big green "Merge pull request" button on this page. I guess someone should press that :-)
Joking aside - everyone is busy with release of 4.4.0 atm. And it is unclear from the  thread above if everyone involved was +1 on merging.

CLA signed by all contributors.


Cannot destructure property 'vueApp' of 'globalThis.unctx.get(...).tryUse(...)' as it is undefined.

Environment

Operating System: Darwin
Node Version:     v18.18.2
Nuxt Version:     3.6.0
Nitro Version:    2.5.1
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      ssr, app, css, modules, i18n, apollo, runtimeConfig, imports, devtools
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
I simply follow the getting started and this works up until I try to use mountSuspended or renderSuspended. I try a basic test as following:
import { describe, expect, it } from 'vitest';
import { renderSuspended } from '@nuxt/test-utils/runtime';

import { createI18n } from 'vue-i18n';

import nlBE from '@/i18n/nl-BE';
import Landing from<EMAIL_ADDRESS>
const i18n = createI18n({
  locale: 'nl-BE',
  messages: {
    'nl-BE': nlBE
  }
});

const config = {
  global: {
    plugins: [i18n]
  }
};

describe('Landing Page', () => {
  it('renders a webpage', async () => {
    const component = await renderSuspended(Landing, config);
    expect(component.html()).toMatchSnapshot();
  });
});

This returns as error "Cannot destructure property 'vueApp' of 'globalThis.unctx.get(...).tryUse(...)' as it is undefined."
Another issue I sometimes get is the following: (not sure if related)

Describe the bug
While following the getting started for nuxt/test-utils I come across the following error:
Cannot destructure property 'vueApp' of 'globalThis.__unctx__.get(...).tryUse(...)' as it is undefined.
This happens as soon as I try to import anything from @nuxt/test-utils/runtime. Changing environment to jsdom, happy-dom or nuxt does not change anything.
Additional context
No response
Logs
No response

This is no longer an issue and was caused by some package versions that didn't agree with each other.


Pester 4.x support - Allow for new syntax

Pester 4.x adds new assertion syntax and current version of poshspec uses the 3.x syntax.
Describing WhatEver
Context Services
Checking Status
[-] Error occurred in Context block 299ms
RuntimeException: The It command may only be used from a Pester test script.
at Assert-DescribeInProgress, C:\Program Files\WindowsPowerShell\Modules\Pester\4.0.2\Functions\Describe.ps1: line 200
at ItImpl, C:\Program Files\WindowsPowerShell\Modules\Pester\4.0.2\Functions\It.ps1: line 140
at It, C:\Program Files\WindowsPowerShell\Modules\Pester\4.0.2\Functions\It.ps1: line 117
at Invoke-PoshspecExpression, ..\Modules\poshspec\2.1.12\Private\Invoke-PoshspecExpression.ps1:
https://github.com/pester/Pester/issues/683

I have yet to test it, but the Should syntax is provided by you. On the surface, it appears you can update your test scripts to the new syntax if you are using 4.x. Based on that error, it does look like something else about how Pester executes the test has changed that doesn't have to do with the assertion syntax.

I think it was how I was calling the modules.  Both Pester and PoshSpec were being called independently and sure if it was having issues with the built in Pester in Win 10.  Will close the issue for now and let you know if I find anything else.


feat: automatic oracle offline reporting on_initialize

Signed-off-by: Gregory Hill<EMAIL_ADDRESS>

Should we gut the staked-relayer report already? We can't remove it immediately probably, but we can make it always return some error (or even OK). It'll save a little bit of transaction costs, and we can remove the tests & sla changes related to it already

Should we gut the staked-relayer report already? We can't remove it immediately probably, but we can make it always return some error (or even OK). It'll save a little bit of transaction costs, and we can remove the tests & sla changes related to it already

We'll refactor prior to re-genesis of beta.


Installation gets stuck

Hi,
I am trying to run the installation without mamba. However, make install pretrained_models is stuck for hours.
$ make install pretrained_models
make: mamba: Command not found
Collecting package metadata (repodata.json): / WARNING conda.models.version:get_matcher(537): Using .* with relational operator is superfluous and deprecated and will be removed in a future version of conda. Your spec was 1.8.0.*, but conda is ignoring the .* and treating it as 1.8.0
WARNING conda.models.version:get_matcher(537): Using .* with relational operator is superfluous and deprecated and will be removed in a future version of conda. Your spec was 1.6.0.*, but conda is ignoring the .* and treating it as 1.6.0
WARNING conda.models.version:get_matcher(537): Using .* with relational operator is superfluous and deprecated and will be removed in a future version of conda. Your spec was 1.9.0.*, but conda is ignoring the .* and treating it as 1.9.0
WARNING conda.models.version:get_matcher(537): Using .* with relational operator is superfluous and deprecated and will be removed in a future version of conda. Your spec was 1.7.1.*, but conda is ignoring the .* and treating it as 1.7.1
done
Solving environment: \

I am wondering what takes so long...?

Hi there!
Unfortunately, our packages come from a variety of repositories and to make the installation as widely supported as possible, we seldom put constraints - only when our code is really incompatible otherwise.
If your installation of conda is rather old (I think before 2023), the solver that came with conda back then is highly unoptimized and spends unnecessarily long to solve the packages. I would suggest either

updating your solver https://conda.github.io/conda-libmamba-solver/user-guide/
or installing the latest version (that automatically comes with a good solver).
or getting mamba by conda install -c conda-forge mamba

May I learn which conda version you use?

Hi @egaznep, thanks for the reply!
Turns out that my conda version was 4.1.0 -- much older than I thought...
For anyone interested, I first tried to update my conda to the latest version (23.10). But solely doing this does not solve the stuck problem.
I then tried to install mamba by conda install -c conda-forge mamba, and then the installation somehow worked. It still took more than 30 minutes though.
@egaznep I then happened to find a bug in the Makefile -- this cp line does not have a destination.
https://github.com/DigitalPhonetics/VoicePAT/blob/main/Makefile#L40
What was the intention of this line?

Hi @egaznep, thanks for the reply! Turns out that my conda version was 4.1.0 -- much older than I thought...
For anyone interested, I first tried to update my conda to the latest version (23.10). But solely doing this does not solve the stuck problem. I then tried to install mamba by conda install -c conda-forge mamba, and then the installation somehow worked. It still took more than 30 minutes though.

Happy to hear that 🙂 the installation speed may be affected by your download speed and your computer specifications. I will run a test on my workstation to see if I get the same numbers and if it is possible to reduce the installation time.

@egaznep I then happened to find a bug in the Makefile -- this cp line does not have a destination. https://github.com/DigitalPhonetics/VoicePAT/blob/main/Makefile#L40 What was the intention of this line?

I will issue a fix for that line soon, it should not be there. By the way, you might find the vpc branch useful, where a couple of extra developments have been made.

Thanks! Will take a look at the vpc branch and close this issue for now. I do have some other questions -- will ask in a separate issue.

@unilight It seems that having an old, existing Anaconda is the primary reason why the installation drags on. I suggest using miniconda instead (which is not bloated with many packages therefore processes the installation specifications faster)


feat: upgrade dependencies (swc_ecma_parser 0.122.19)

Need to test this out and open downstream prs.

@kitsonk we have these scripts (https://github.com/denoland/deno_ast/tree/main/scripts) for that.
I reported two bugs to swc yesterday after running them:

https://github.com/swc-project/swc/issues/6239 (maybe a question and not a bug)
https://github.com/swc-project/swc/issues/6238


Incorrect link in documentation

The link in number 3 of this section points to a 404:
https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-security-configuration-framework/windows-security-baselines#where-can-i-get-the-security-baselines
It is linked as:
(https://docs.microsoft.com/en-us/mem/intune/protect/security-baseline-settings-mdm-all.md)
I removed the ".md" and got to what I believe is the correct page.

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

ID: c3deb045-565e-169b-ecd4-6f0f07c966e4
Version Independent ID: 1bd84f68-4820-4d11-aafc-da1657bddc80
Content: Security baselines guide - Windows security
Content Source: windows/security/threat-protection/windows-security-configuration-framework/windows-security-baselines.md
Product: m365-security
Technology: windows-sec
GitHub Login: @Dansimp
Microsoft Alias: dansimp

@e0i error link is already fixed , so please close #10320


pod tiller-deploy crashes with permission denied on token

Output of helm version:
# helm version
Client: &version.Version{SemVer:"v2.12.3", GitCommit:"eecf22f77df5f65c823aacd2dbd30ae6c65f186e", GitTreeState:"clean"}
Error: could not find a ready tiller pod

Output of kubectl version:
# kubectl version
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.3", GitCommit:"d2835416544f298c919e2ead3be3d0864b52323b", GitTreeState:"clean", BuildDate:"2018-02-07T12:22:21Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"9+", GitVersion:"v1.9.2-CCE2.0.7-B003", GitCommit:"302f471a1e2caa114c9bb708c077fbb363aa2f13", GitTreeState:"clean", BuildDate:"2018-06-20T03:27:16Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.):
Open Telekom Cloud CCE-2.0 https://docs.otc.t-systems.com/en-us/usermanual2/cce/cce_01_9991.html

Setup with rbac according to the docs.
serviceaccount and clusterrolebinding
# cat rbac-config.yaml
apiVersion: v1
kind: ServiceAccount
metadata:
  name: tiller
  namespace: kube-system
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: tiller
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: cluster-admin
subjects:
  - kind: ServiceAccount
    name: tiller
    namespace: kube-system

Creating rbac binding
# kubectl -n kube-system create -f rbac-config.yaml
serviceaccount "tiller" created
clusterrolebinding "tiller" created

helm init
# helm init --service-account tiller
$HELM_HOME has been configured at /root/.helm.

Tiller (the Helm server-side component) has been installed into your Kubernetes Cluster.

Pod keeps failing
# kubectl -n kube-system describe po tiller-deploy-7c78f74c-lzscm
Name:           tiller-deploy-7c78f74c-lzscm
Namespace:      kube-system
Node:           <IP_ADDRESS>/<IP_ADDRESS>
Start Time:     Wed, 06 Feb 2019 13:29:03 +0000
Labels:         app=helm
                name=tiller
                pod-template-hash=37349307
Annotations:    <none>
Status:         Running
IP:             <IP_ADDRESS>
Controlled By:  ReplicaSet/tiller-deploy-7c78f74c
Containers:
  tiller:
    Container ID:   docker://776e31514297f92d5f33962b1b5ed52c7ca916e64781c81a5a04b6ffe97b1515
    Image:          gcr.io/kubernetes-helm/tiller:v2.12.3
    Image ID:       docker-pullable://gcr.io/kubernetes-helm/tiller@sha256:cab750b402d24dd7b24756858c31eae6a007cd0ee91ea802b3891e2e940d214d
    Ports:          44134/TCP, 44135/TCP
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Wed, 06 Feb 2019 13:30:47 +0000
      Finished:     Wed, 06 Feb 2019 13:30:48 +0000
    Ready:          False
    Restart Count:  4
    Liveness:       http-get http://:44135/liveness delay=1s timeout=1s period=10s #success=1 #failure=3
    Readiness:      http-get http://:44135/readiness delay=1s timeout=1s period=10s #success=1 #failure=3
    Environment:
      TILLER_NAMESPACE:    kube-system
      TILLER_HISTORY_MAX:  0
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from tiller-token-hzntg (ro)
Conditions:
  Type           Status
  Initialized    True
  Ready          False
  PodScheduled   True
Volumes:
  tiller-token-hzntg:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  tiller-token-hzntg
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     <none>
Events:
  Type     Reason                 Age                From                     Message
  ----     ------                 ----               ----                     -------
  Normal   Scheduled              2m                 default-scheduler        Successfully assigned tiller-deploy-7c78f74c-lzscm to <IP_ADDRESS>
  Normal   SuccessfulMountVolume  2m                 kubelet, <IP_ADDRESS>  MountVolume.SetUp succeeded for volume "tiller-token-hzntg"
  Normal   SuccessfulMountVolume  2m (x2 over 2m)    kubelet, <IP_ADDRESS>  Successfully mounted volumes for pod "tiller-deploy-7c78f74c-lzscm_kube-system(2c07142b-2a13-11e9-9ff9-fa163e1c80f4)"
  Normal   Pulled                 1m (x4 over 2m)    kubelet, <IP_ADDRESS>  Container image "gcr.io/kubernetes-helm/tiller:v2.12.3" already present on machine
  Normal   SuccessfulCreate       1m (x4 over 2m)    kubelet, <IP_ADDRESS>  Created container
  Normal   Started                1m (x4 over 2m)    kubelet, <IP_ADDRESS>  Started container
  Warning  BackOffStart           31s (x10 over 1m)  kubelet, <IP_ADDRESS>  Back-off restarting failed container

Log of Pod
# kubectl -n kube-system logs tiller-deploy-7c78f74c-lzscm
[main] 2019/02/06 13:32:16 Cannot initialize Kubernetes connection: failed to read token file "/var/run/secrets/kubernetes.io/serviceaccount/token": open /var/run/secrets/kubernetes.io/serviceaccount/token: permission denied

Secret has token set inside of data (secrets replaced by XX)
# kubectl -n kube-system get secret tiller-token-hzntg -o yaml
apiVersion: v1
data:
  ca.crt: XX
  namespace: a3ViZS1zeXN0ZW0=
  token: XX
kind: Secret
metadata:
  annotations:
    generator: JWT
    kubernetes.io/service-account.name: tiller
    kubernetes.io/service-account.uid: 0e9bd70d-2a13-11e9-ba56-fa163e0a415a
  creationTimestamp: 2019-02-06T13:28:14Z
  enable: true
  name: tiller-token-hzntg
  namespace: kube-system
  resourceVersion: "37224"
  selfLink: /api/v1/namespaces/kube-system/secrets/tiller-token-hzntg
  uid: 0e23f967-2a13-11e9-9ff9-fa163e1c80f4
type: kubernetes.io/service-account-token

I have the same problem. I am also using the CCE product of the Open Telekom Cloud. It is a brand-new CCE instance.
Output of helm version:
Client: &version.Version{SemVer:"v2.12.2", GitCommit:"7d2b0c73d734f6586ed222a567c5d103fed435be", GitTreeState:"clean"}
Error: could not find a ready tiller pod

Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.2", GitCommit:"17c77c7898218073f14c8d573582e8d2313dc740", GitTreeState:"clean", BuildDate:"2018-10-24T06:54:59Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"9+", GitVersion:"v1.9.2-CCE2.0.7-B003", GitCommit:"302f471a1e2caa114c9bb708c077fbb363aa2f13", GitTreeState:"clean", BuildDate:"2018-06-20T03:27:16Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}

I have done some digging and I am convinced that this permission problem is in some way related to the use of the user nobody in the Dockerfile of the image. I found that the .../tokens file is present in the container but not accessible by the user nobody, see below for my step-by-step analysis.
I suspect that this is some bad interplay between the EulerOS linux distribution that the CCE machines use and the mounting mechanism.

I have generated the deployment.yaml from the helm init command using:
$ helm init --service-account tiller --dry-run --debug

and modified it:
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  creationTimestamp: null
  labels:
    app: helm
    name: tiller
  name: tiller-deploy
  namespace: kube-system
spec:
  replicas: 1
  strategy: {}
  template:
    metadata:
      creationTimestamp: null
      labels:
        app: helm
        name: tiller
    spec:
      automountServiceAccountToken: true
      containers:
      - env:
        - name: TILLER_NAMESPACE
          value: kube-system
        - name: TILLER_HISTORY_MAX
          value: "0"
        image: gcr.io/kubernetes-helm/tiller:v2.12.3
        imagePullPolicy: IfNotPresent
        command: [ "sh", "-c", "--" ]
        args: [ "while true; do sleep 30; done;" ]
        name: tiller
      serviceAccountName: tiller

After kubectl create-ing this deployment, I have ssh'd onto the node and entered the pod using docker exec. Doing so allows me to override the linux-user that is used inside the docker container:
# no user supplied -> will use `nobody`
$ docker exec -u user -ti k8s_tiller_tiller-deploy-8cd9fc8d8-sz9q6_kube-system_b44311af-3908-11e9-9727-fa163e88ed1f_0 sh
# user `root` supplied
$ docker exec -ti -u root k8s_tiller_tiller-deploy-8cd9fc8d8-sz9q6_kube-system_b44311af-3908-11e9-9727-fa163e88ed1f_0 sh

I observe that I can't access the .../tokens file as user nobody but, as one might expect, can do so as user root:
# as user `nobody`:
$ cat /var/run/secrets/kubernetes.io/serviceaccount/token
cat: can't open '/var/run/secrets/kubernetes.io/serviceaccount/token': Permission denied

# as user `root`
$ cat /var/run/secrets/kubernetes.io/serviceaccount/token
eyJhbGciOiJSUzI1NiIsInR.............ga

Hi, did you make any progress on this ?
I am running into the exact same problems.
Outputs are matching:

Output of helm version:
Client: &version.Version{SemVer:"v2.12.2", GitCommit:"7d2b0c73d734f6586ed222a567c5d103fed435be", GitTreeState:"clean"}
Error: could not find a ready tiller pod

Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.2", GitCommit:"17c77c7898218073f14c8d573582e8d2313dc740", GitTreeState:"clean", BuildDate:"2018-10-24T06:54:59Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"9+", GitVersion:"v1.9.2-CCE2.0.7-B003", GitCommit:"302f471a1e2caa114c9bb708c077fbb363aa2f13", GitTreeState:"clean", BuildDate:"2018-06-20T03:27:16Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}

We skipped using the OTC2 with their Kubernetes setup.
Using the Baremetal VMs and putting rancher on top to get a recent kubernetes version.


equations on top of each other

Description
The use of tcolorbox package to place a box around a multiple line equation makes equations appear on top of each other in the html rendering.
(Optional:) Please add any files, screenshots, or other information here.
No response
(Required) What is this issue most closely related to? Select one.
Choose One
Internal issue ID
2f50c740-ac58-4a4a-901d-59b37638f911
Paper URL
https://arxiv.org/html/2402.17684v1
Browser
Firefox/123.0
Device Type
Desktop

Dev note: see this section: https://arxiv.org/html/2402.17684v1#S2.SS4.p2


add nf-core NfcoreSchema.groovy updates to SchemaValidator.groovy

As mentioned in nf-core issue #1543, the validation of nextflow_schema.json files from nf-core pipelines is held in the template. The idea is to move it to core Nextflow with this plugin.
The code has been updated to adapt to the current nf-core template.
When the call to parameter validation (NfcoreSchema.validateParameters()) is removed from the pipeline template i.e. ~/.nextflow/assets/nf-core/rnaseq/lib/WorkflowMain.groovy, the validation is done with the plugin.
❯ ./launch.sh run -plugins nf-validation nf-core/rnaseq -r bc9924e2 -params-file ../nf-core-test/test_params.json
N E X T F L O W  ~  version 22.05.0-edge
Launching `https://github.com/nf-core/rnaseq` [fabulous_visvesvaraya] DSL2 - revision: bc9924e2e0427fbd4f31d903bdda9c97b854d551
The following invalid input values have been detected:
* Missing required parameter: --outdir

Added two new parameters to use with the schema validation:

fail_unrecognised_params: unrecognised parameters are reported as errors instead of warnings
lenient_mode: JSON schema validation lenient mode is activated

Functions can be imported to a pipeline with include { paramsHelp, paramsSummaryMap, paramsSummaryLog } from 'plugin/nf-validation'

Nice. Thanks for submitting this. It looks like some testing are failing. You can check in your computer running
./gradlew test

The tests are implemented in this class http://github.com/nextflow-io/nf-validation/blob/bc09ba32bef4a5662422e49c095bb666ecee4212/plugins/validation/src/test/nextflow/validation/SchemaValidatorTest.groovy

Thanks for this PR! it's very valuable.
I think it could be added in the unit testing at least one real nf-core schema, to be sure the validation does not break. Maybe @ewels can help to identify the proper one.

There are some functions required by nf-core schema commands that are not used by the plugin

Regarding this I think those function can be removed since they are not going to be sued any more. @ewels thought?

The simplest valid schema I can think of is probably the one that ships with the nf-core template: https://github.com/nf-core/tools/blob/master/nf_core/pipeline-template/nextflow_schema.json

There are some functions required by nf-core schema commands that are not used by the plugin

I don't understand this. This code has no interaction with nf-core/tools or the nf-core schema command? The two are totally separate.
At least some of the functions you mention are utility functions called by the pipelines. For example, paramsHelp() is used in lib/WorkflowMain.groovy: help_string += NfcoreSchema.paramsHelp(workflow, params, command)

This code has no interaction with nf-core/tools or the nf-core schema command? The two are totally separate.

Exactly, this was my question, as I was adding the changes made in nf-core schema here I wondered if this functions had to be added also.

I'm still not sure I follow sorry. Can you point to the bits of code you're talking about?

Note that it might be worth restructuring the code if you think it makes sense to do so. In the current version of the template the file is called NfcoreSchema.groovy and it does everything to do with the schema, not just validation (such as generating the help output).
Here the file is called SchemaValidator.groovy which sounds a bit more specific. So could potentially break the files up a bit more or just rename it to be less confusing.

So no, providing the paramsHelp() function is kind of the whole point of the plugin

well, well, well 😅 this originated with the idea of schema validation, not to provide new functions, but I'm open to that.
the main problem is that so far, the plugin system allows adding new operators, not arbitrary functions.
@jorgeaguileraseqera do you think it's doable supporting custom function via the include plugin system?

well, well, well 😅 this originated with the idea of schema validation, not to provide new functions, but I'm open to that.

haha, sorry 🙄 Once you've gone to the effort of parsing the schema and parameters, the paramsHelp() bit is fairly easy - seems a shame to miss that 😉 (also paramsSummaryLog() for printing params that have changed from the default when a pipeline launches).
@pditommaso were you thinking that this plugin would automatically validate parameters on load / include? The main issue with that is that sometimes we don't want to validate - for example when printing help with --help (then we don't care that the required param --input wasn't provided). So typically validation would be done by explicitly calling a function from within the pipeline. We do this all in order within an initialise() function with nf-core pipelines.
@jorgeaguileraseqera - syntax looks great! Does it work already or is it hypothetical?

@jorgeaguileraseqera - syntax looks great! Does it work already or is it hypothetical?

recently we implemented the include { sqlInsert } from 'plugin/nf-sqldb' to improve channels so I think probably we can implement something similar for custom functions

were you thinking that this plugin would automatically validate parameters on load / include?

Yes exactly.

The main issue with that is that sometimes we don't want to validate - for example when printing help with --help (then we don't care that the required param --input wasn't provided)

There's too much boilerplate code in nf-core pipelines. I think it's a good opportunity to start rethinking this.
Why not move this kind of stuff at the plugin level, I mean we could make it able to detect the --help option and act consequently

I think it could be added in the unit testing at least one real nf-core schema, to be sure the validation does not break. Maybe @ewels can help to identify the proper one.

@pditommaso do you mean reading a schema from a json file instead of defining the params map inside the test? Or modifying the SCHEMA variable?

we could make it able to detect the --help option and act consequently

Is there an example of another plugin that detects command line parameters?

Hi all,
I have implemented the things that we have been discussing this last days after the merge of #3079 by @jorgeaguileraseqera.
The only thing is that when I try to test the function paramsHelp() in a pipeline, I get the following error and can't use the function.
Plugin 'nf-validation' does not implement any extension point
What am I missing?

Tagging @jorgeaguileraseqera for some help

Hi @mirpedrol
I've been reviewing your PR and you need to make some changes (mainly due lack of documentation from our side, so we need to improve it)

to avoid conflicts and be sure you are using the latest changes update your repo (I can see is behind master a lot)
you are compiling with nextflow v22.0.4 but changes are in a snapshot by the moment, so you need to change compileOnly 'io.nextflow:nextflow:22.04.0' by compileOnly 'io.nextflow:nextflow:22.08.1-edge'
I tried to compile your repo but org.everit.json.schema seems not updated to last version and it complains about a missing class (PrimitiveValidationStrategy) so I've updated to 'com.github.everit-org.json-schema:org.everit.json.schema:1.14.1'

Once updated these libraries, we're able to start with the issue:

You need to extend SchemaValidator from PluginExtensionPoint (class SchemaValidator extends PluginExtensionPoint)
also you need to specify this class in the META-INF/extensions.idx file
functions annotated with @Functions can't be static

I think once fixed this issues you'll be able to see progress, in any case don't hesitate to reach me and we can work together on it

Quick thought: I suspect that people may want to skip validation for a variety of reasons. I think I'm right in staying that currently this is only possible if params.help is true. What about adding a new core flag / config option for this, that could be used in a generic way? Is this possible?

Quick thought: I suspect that people may want to skip validation for a variety of reasons. I think I'm right in staying that currently this is only possible if params.help is true. What about adding a new core flag / config option for this, that could be used in a generic way? Is this possible?

not sure to fully understand your suggestion but what I'm think is something as:

the user writes the pipeline and includes the nf-validation plugin plus the definition of the funtion and call it

   include { validateParameters } from 'plugins/nf-validation`
   validateParameters()

when core load the plugin it initialize it calling init( Session session) so plugin can inspect the configuration and check if params.help is present/true
when the validateParameters() is called this method knows if needs to validate parameters or not

@jorgeaguileraseqera your suggestion looks good 👍🏻 Then the pipeline developer can add the validation call wherever makes most sense for their pipeline.
As I understand it (from discussion with @mirpedrol), the plugin currently runs validation on all pipelines (a) without any import call in the pipeline code and (b) on every launch, unless params.help is true.
See plugins/validation/src/main/nextflow/validation/ValidationObserver.groovy L31-33:
        if (!params.help) {
             validator.validateParameters(params, session.baseDir, schema.text)
         }

I worry that this is too inflexible. On the plus side, it means that just having nextflow_schema.json in the project root is sufficient for parameter validation. But on the down side it means that people cannot skip validation if they want to.

Exactly, with current implementation, the plugin runs the validation "out-the-box" so can be useful for some users but not for other
so my suggestion is to remove from observer (in fact in this plugin I think ValidationObserver can be removed) and export functions
probably we need to review the arguments of the functions and offer the most simple signature for the user. I mean, instead to have a function validateParameters( params, baseDir, schema ) we need to think which of them are accessible via Session (for example) and maybe export a function validateParameters()

Yes, we recently added the ability for plugins to export functions to the pipeline script, also to accommodate this plugin need! 👍

I've tried to compile this pr but has some (102) errors most of them related to the CompileStatic
[Static type checking] - No such property: session for class: nextflow.validation.SchemaValidator
@ line 97, column 9.
this.session = session

I have pushed some changes that fix the compilation errors. There are still some things to fix, some tests failing and importing functions to a workflow is not working for me yet, I'm trying to solve this now.

Hi @ewels @pditommaso,
After some more modifications and all the help from @jorgeaguileraseqera, it seems that the plugin is taking shape.
I also added the changes that the nf-core pipeline template will have here.
Would you mind taking a look and giving your opinions? Thanks!

Ah, just realised you were using the JSON schema from here as a test. This needs to be updated and is incompatible with nf-core/tools so definitely needs to be replaced here and tested before merging. I have already updated the schema on a branch here. However, as I mentioned I guess there is no harm in using a vanilla one created with the latest version of tools.

Thank you for the review @drpatelh!
I will use the schema file from the nf-core template, it was suggested before, but I missed it.


Garbled text at compile in CMD, on Win10 zh_CN

as the pic below.
I tried common Chinese charset, such as UTF-8, GBK, GB2132. And doesn't work.

Hi @hxl9654 ,
Thank you for your interest in the AWS IoT SDK!
This seems to be related to the issues in Visual Studio itself and not with the way the SDK is using CMake. I was able to locate the following two issues being tracked related to the garbled output:
https://github.com/vector-of-bool/vscode-cmake-tools/issues/153
https://github.com/Microsoft/vscode/issues/974
I am closing this issue as it is unrelated to the SDK itself.
Please let us know if you have any more questions and please open another issue if you do as we do not have effective tracking for closed issues.
Thanks!
Varun


improvement: Removed dependency on external template provider

PR o'clock
Description
Removed dependency on the external template provider and instead used the Terraform native templatefile() function. As recommended by the provider itself.
My primary goal was to stop unnecessary recreation of worker launch templates and configurations when certain other resources are modified, for example the aws_eks_cluster. For example, changing the IP whitelist on the cluster public endpoint should not impact worker nodes. Previously:

the resource would be marked as "unknown" in the Refresh stage
the data_template_file userdatas could not be refreshed and so were in an unknown state during Plan stage
thus generating unnecessary pending recreation of launch config/templates

Thought I'd go the full mile and also convert kubeconfig. I moved some of the logic into the template itself to make the terraform easier to read.
Questions for maintainers

The userdata lists are now locals and not data sources. Should they be moved to locals.tf or workers.tf/workers_launch_template.tf? I don't think they should remain in data.tf even if it makes history a little harder to follow.
kubeconfig is a YAML file. Should we use yamlencode, like in aws-auth, instead of a template? It will make the locals messy again but the output YAML should always be valid.

Checklist

[x] CI tests are passing
[x] README.md has been updated after any changes to variables and outputs. See https://github.com/terraform-aws-modules/terraform-aws-eks/#doc-generation

Awesome ❤! This will increase readability and consistency.

The userdata lists are now locals and not data sources. Should they be moved to locals.tf or workers.tf/workers_launch_template.tf? I don't think they should remain in data.tf even if it makes history a little harder to follow.

I'll prefer to have all locals into the locals.tf file.

kubeconfig is a YAML file. Should we use yamlencode, like in aws-auth, instead of a template? It will make the locals messy again but the output YAML should always be valid.

I think we can continue to use templatefile, it make the kubeconfig easily reusable between LT and LC.

@max-rocket-internet any thought ?

@dpiddockcmp would you like to be a maintainer of this module? Your contributions have been outstanding and I am spending less time on this project these days. And I see you're already a member?

Merging. I'll open another PR to remove template in examples.

Oops, I had a couple busy days and was going to do the requested changes today. Thanks for sorting it out.

I'll prefer to have all locals into the locals.tf file.

This change wasn't done either before merging

kubeconfig is a YAML file. Should we use yamlencode, like in aws-auth, instead of a template? It will make the locals messy again but the output YAML should always be valid.

I think we can continue to use templatefile, it make the kubeconfig easily reusable between LT and LC.

I think you're thinking of the userdata 🙂 . Generated kubeconfig is only useful for end users now.

@dpiddockcmp would you like to be a maintainer of this module? Your contributions have been outstanding and I am spending less time on this project these days. And I see you're already a member?
I already asked you this some months back on a PR but perhaps you didn't see it 🙂

@max-rocket-internet I must have missed that. Sure, I'll be a maintainer 😄

PR to update examples https://github.com/terraform-aws-modules/terraform-aws-eks/pull/863

@dpiddockcmp can you email me<EMAIL_ADDRESS>

I'll prefer to have all locals into the locals.tf file.

This change wasn't done either before merging

Oops. I'll move them in #863

Sure, I'll be a maintainer 😄

Done 🚀


Support audio-only channels

Is your feature request related to a problem? Please describe.
I can't play this playlist of radio channels: http://bit.ly/kn-kodi-radio
The list is maintained here: https://github.com/jnk22/kodinerds-iptv
Describe the solution you'd like
It would be awesome, if audio-only channels are supported for streaming radio stations. Instead of a video only the icon of the channel could be displayed.
Describe alternatives you've considered
Additional context
Thank you for this awesome project.

Radio stations are working for me (in Linux LMDE5) only using MPV Player.
However, they cannot be stopped because mpv has no window for audio only.

I added audio player for audio-only streams aka radio (based on radio="true" flag from the m3u file). It will be part of the next release, but could be tested in the PWA now: https://iptvnator.vercel.app/playlists?url=https:%2F%2Fraw.githubusercontent.com%2Fjnk22%2Fkodinerds-iptv%2Fmaster%2Fiptv%2Fkodi%2Fkodi_radio.m3u


sync-bitfield event to know when the bitfield has been written

For multifeed-index, I need an event to know when I can read records from the log. The 'append' event happens before the records are written and the 'sync' event happens before the bitfield is updated after replication. With this additional event, I can tail a hypercore log without subtle timing bugs around replication.

Nice!
Could "written" or "appended" also be a valid name choices? It's not as obvious to me, without deep knowledge of hypercore internals, that "sync-bitfield" means that an entry has been fully written.
cc @mafintosh

Why was this closed?


fix(issue): Fix links to issue comments

Fixes #462.
The regular expression can't match anything if issueURL is a issue comment, like https://github.com/octokit/discussions/issues/7#issuecomment-327616339. It causes [1] throws an error.
const issueNumberRegex = /issues\/([0-9]+)$/;
const { issue, issueURL, isPR, language } = navigation.state.params;
const number = issue ? issue.number : issueURL.match(issueNumberRegex)[1];

Nice catch buddy, but I think you're fixing another unknown bug here.
#462 is a bug happening when reading an issue. There's no navigation problem related there, but an Animated related exception (see my comments on that issue). If I dismiss the red screen, I do see the issue screen along with some of its comments. The bug there is supposedly with a TouchOpacity element. Still haven't investigate it yet.

Oh, actually you fixed a bug happening when clicking on the link I added in my comment :D

Ok, I understood what happened here :D
There is the bug reported in #462, which is still un-resolved.
And there's a new bug you spotted by clicking my comment on #462.

@machour Right. I saw the crash you mentioned for a while, but was attracted by this bug. 😆
I have changed the PR description so that this PR doesn't close #462.


SAFE on map wo/ edges

Not really an issue but rather a question: is it possible to use SAFE on a layout with nodes yet without edges? SAFE runs in this case but does not find any enrichments. So I am wodering whether SAFE it's not working in this case  (because I am having the wrong setting or because I am violating some assumptions) or whether I simply don't have any enrichments in my data set (I do however expect some enrichments).
Thank you in advance,
Christian

Hi Christian,
In principle, yes, absolutely, it's possible. An example is Fig. 3 in a preprint we posted recently: https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>1593v1 Here, a version of SAFE was applied to a UMAP projection. The key is to choose the right node distance metric and calibrate the parameters properly.
In practice, I'm not sure that the safe-java implementation you're using is flexible enough to do it. Would you be open to switching to Python? safepy is a Python implementation of SAFE that is more flexible and adaptable to specific cases. If you're interested, I'd be happy to guide you through the process. Feel free to email me directly (email available at www.baryshnikova-lab.org).
Anastasia

Hi Anastasia,
Thank you for your fast and helpful reply! In fact this is exactly what I want to do (tSNE instead of UMAP but same same). I will give safepy a try. Thank you for offering your help which I am happy to come back to.


Add support for mocking .addScope()

This adds .addScope() sequelize function, and enables the check for it in tests.
Here is a link to Sequelize's implementation of that function.

I'm sorry to bug you, but when could we expect this to be in some release?.. Thanks!


Do not attempt creating ssh config files if ssh_config.d doesn't exist

reported by a user:
INFO[0025] Adding containerlab host entries to /etc/hosts file
INFO[0025] Adding ssh config for containerlab nodes
ERRO[0025] failed to create ssh config file: open /etc/ssh/ssh_config.d/clab-srl01.conf: no such file or directory

this means the path did not exist and this PR ensures the path exists.
It might be that the OS user runs or OpenSSH there won't honor the newly created path either, but it seems still safe to create the path

Hmm my feeling is more like, if that path does not exist, we do not generate the config rather then generating something that is not used anyways.

I will ask the user to create this file and see if his ssh client picks it up

@steiler re-applied the patch to follow the suggested logic, as old ssh clients do not respect the created path.


Typo in Release Note

useEslintLoader maybe change to useEslint
Thank you for your work @LinusBorg

Fixed, thanks!


delete unused DDIC objects

closes #799
enable abaplint rule https://rules.abaplint.org/unused_ddic/

LGTM, thanks! 👍


Allow sync with Enterprise Github

Would be great if we could specify a different URL for enterprise github

It is present,
read this
https://github.com/shanalikhan/code-settings-sync#global-settings


Adding support for BDSMLR

Hello, I wondered if you could add support for the blogging website "bdsmlr.com". It is very close of tumblr, on the way it works.

Hello,
this is a tiny niche blogging site. It has no API and there's no development activity since over a year.
We won't integrate this site.


CLI example missing required --params

In order to run, the CLI "az policy assignment create" command needs --params passed to it for tagName and tagValue.

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

ID: 658b4c0d-c5b7-3859-c669-8476ba2b3020
Version Independent ID: 93fb980c-9db6-e522-a15d-ab28bf26d10c
Content: Azure Policy sample - Apply tag and its default value
Content Source: articles/governance/policy/samples/apply-tag-def-val.md
Service: azure-policy
GitHub Login: @DCtheGeek
Microsoft Alias: dacoulte

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

@gottagetgit Thanks for the feedback!  Most of the samples do need to be updated due to CLI/PS updates, but I'll prioritize this one.
@MicrosoftDocs/azure-cxp-triage #in-progress

@gottagetgit I updated the sample, which is why this got closed.  Please let me know if the changes are less than desired.  Thanks again for the feedback!

Wow, great. Much more useful. :)


can't download package

run go mod tidy got this error
go<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>invalid version: unknown revision<PHONE_NUMBER>00

cloned from scratch, executed the command. not confirmed.


Kubernetes Version Compatibility is unclear

I want to know what version of operator-sdk is compatible with Kubernetes 1.25. I can see the latest version is made for 1.26 but I see no way of finding which version is for 1.25. The compatibility matrix is not helpful: https://sdk.operatorframework.io/docs/overview/#kubernetes-version-compatibility

@emily-zall As mentioned in the docs, the client-go version present in go.mod of operator-sdk determines the k8s version with which the binary is compatible. For example, you can see that operator-sdk version 1.27.0, in its go.mod file (https://github.com/operator-framework/operator-sdk/blob/5cbdad9209332043b7c730856b6302edc8996faf/go.mod#L41), contains client-go 0.25.3. This relates to K8s version 1.25+ (https://github.com/kubernetes/client-go#versioning).
Also, checking the go.mod file of the scaffolded project would be helpful to make sure that the scaffolding supports the k8s version you want. Hope this helps!