cmd/go: 'go get' fails to track a branch which contains a /

What version of Go are you using (go version)?

$ go version

go version go1.14.2 darwin/amd64

Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/grellyd/Library/Caches/go-build"
GOENV="/Users/grellyd/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GONOPROXY="go.company.io"
GONOSUMDB="go.company.io"
GOOS="darwin"
GOPATH="/Users/grellyd/wrk/go"
GOPRIVATE="go.company.io"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/Cellar/go/1.14.2_1/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.14.2_1/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/grellyd/wrk/go/src/go.company.io/repo/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/34/mxhn7dp54z9fp1phcl1t0mr80000gn/T/go-build088434320=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?
I was attempting to test changes in a branch of a vendored dependency on a private repository. Having never done this before using go modules, I found the docs (https://golang.org/cmd/go/#hdr-Add_dependencies_to_current_module_and_install_them) which indicated I should go get the associated repo and have the default version overridden by adding an @version suffix to the package argument, as in 'go get<EMAIL_ADDRESS>I assumed from there that I should add the branch as the checkout point. This resulted in the error below, indicating the version string was disallowed. Our company namespaces our github branches before doing the proper branch name. For us, slashes in the branch name are a common workflow. We occasionally also use multiple sub-namespaces for organisation.
Upon further research, I found a docs issue (https://github.com/golang/go/issues/30851), and an associated issue (https://github.com/golang/go/issues/36902). After commenting on the final issue, I opened this one.
A workaround at this time is to git log the sha of the HEAD of the namespaced branch and then go get using that sha. EG: go get github.com/org/repo@sha
An ideal configuration would download new commits upon a subsequent go get, which the sha checkout would not.
What did you expect to see?
go get github.com/org/repo@namespace/branch downloading and checking out that go module at that branch sha.
What did you see instead?
go get github.com/org/repo@namespace/branch: github.com/org/repo@namespace/branch: invalid version: version "branch" invalid: disallowed version string

notice that vscode default branch naming policy is with a slash, therefore, the issue is systematic with this configuration.
https://github.com/microsoft/vscode-pull-request-github/blob/main/package.json
		"githubIssues.issueBranchTitle": {
        			"type": "string",
        			"default": "${user}/issue${issueNumber}",
        		},

I‘ve tried quoting the branch name, but that doesn‘t help either.

Oh, still not fixed :(

See https://github.com/golang/go/issues/32955

Thank you @tonglil - this is indeed a duplicate of the older issue, which has had more discussion. My guess is that this issue got more thumbs up reactions because the title is closer to what the user's situation tends to be: git branches containing slashes.
I'm going to close this as a duplicate for now. For updates, please subscribe to https://github.com/golang/go/issues/32955.
As a temporary workaround in case any of you are blocked, you can use GOPROXY=direct go get in the meantime. The bug is in the proxy.golang.org software, not in cmd/go itself.

Is it a dup? #32955 is focused on proxy behaviors. I'd swear I encountered this before the proxy

I am pretty sure, and just ran a test:
$ go get mvdan.cc/garble@test/with/slashes
go: mvdan.cc/garble@test/with/slashes: invalid version: version "test/with/slashes" invalid: disallowed version string
$ GOPROXY=direct go get mvdan.cc/garble@test/with/slashes
go: downloading mvdan.cc/garble v0.7.1-0.20220711113617-8bc971e0a284

Thanks for the link to the underlying issue @mvdan. For what is worth, I never set GOPROXY  myself: it remained the default value of GOPROXY="https://proxy.golang.org,direct".
Am I correct in understanding the workaround for this issue is to remove the Golang proxy from GOPROXY and instead only prefer direct? In other words, set GOPROXY=direct in our environment.

Correct. Just don't set GOPROXY=direct permanently or globally, because that would greatly slow down Go modules in general.


[GHSA-v3px-6cc8-f8j3] Path traversal in servey

Updates

Source code location

Comments
add source code  location

Hi @r3kumar, it would seem that that repo no longer exists and redirects to a different repo.


migrate and refactor metadata() function

This PR reimplements the metadata() to add columns to the metadata table, taking pd.Series, lists, ints or str's.
Depends on PR #9 for general refactoring and the PR into gidden:refactor_step3 concerning the changed (wrong) behaviour of the validate() function.

unit tests fail because the validate() function does not work as expected after refactoring.

closing in favor of #12


Signature verification failed for repomd.xml

Seems like yum repository messed up again. Take a look...

Operating System: openSUSE Tumbleweed

Steps to Reproduce:
sudo zypper ref
Output :
Warning: File 'repomd.xml' from repository 'Visual Studio Code' is signed with an unknown key ''.

    Note: Signing data enables the recipient to verify that no modifications occurred after the data
    were signed. Accepting data with no, wrong or unknown signature can lead to a corrupted system
    and in extreme cases even to a system compromise.

    Note: File 'repomd.xml' is the repositories master index file. It ensures the integrity of the
    whole repo.

    Warning: We can't verify that no one meddled with this file, so it might not be trustworthy
    anymore! You should not continue unless you know it's safe.

Retrieving repository 'Visual Studio Code' metadata ...........................................................................[error]
Repository 'Visual Studio Code' is invalid.
[code|https://packages.microsoft.com/yumrepos/vscode] Valid metadata not found at specified URL
History:
 - Signature verification failed for repomd.xml
 - Can't provide /repodata/repomd.xml

Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'Visual Studio Code' because of the above error.

just ran this:
$ sudo zypper refresh --force vscode
[sudo] password for root:
Forcing raw metadata refresh
Retrieving repository 'vscode' metadata ................................................................................................................................................................................................................................[done]
Forcing building of repository cache
Building repository 'vscode' cache .....................................................................................................................................................................................................................................[done]
Specified repositories have been refreshed.

I dont see the issue either.
(Previously, I encountered #199006, which was a duplicate of this)

We closed this issue because we are unable to reproduce the problem with the steps you describe. Chances are we've already fixed your problem in a recent version of VS Code. If not, please ask us to reopen the issue and provide us with more detail. Our issue reporting guidelines might help you with that.
Happy Coding!

I tried updating just now on my Fedora VM and was not able to reproduce the issue, so it might have resolved upstream over the weekend or with today's VS Code Insiders release. @riarsdev are you still seeing the issue?

Just did zypper ref. It is fixed now. Thanks.


fog-dnsimple's executable "console" conflicts with fir-cli

Updating fog
Fetching: fog-core-1.45.0.gem (100%)
Successfully installed fog-core-1.45.0
Fetching: fog-digitalocean-0.3.0.gem (100%)
Successfully installed fog-digitalocean-0.3.0
fog-dnsimple's executable "console" conflicts with fir-cli
Overwrite the executable? [yN]  n
ERROR:  Error installing fog:
	"console" from fog-dnsimple conflicts with installed executable from fir-cli

What is the recommendation to solve this?
fog is from https://github.com/fog/fog

According to fog, it is an issue with fir-cli: https://github.com/fog/fog-dnsimple/issues/2.

@jicheng1014 thank you for closing without leaving any comment. ;)


Server crashes on startup

log: http://pastebin.com/RLcdBwdg
Crash: http://pastebin.com/3qzz3ccn
after saying the maps that are wrong, it stops for 3 minutes, and crashes afterwards
maybe it has to do with java 8_51

Puedes pasar el crash report que dice que ha creado.
Can you pass the crash report that says that was created.

We need to crash report..

It looks like an invalid map error to me. Possible corrupt chunks?

@dentmaged any map with problems just gets skipped, (or used to), I've always gotten that warns when opening the server and never gave any errors

@Pablete1234 well, you may have one map or a corrupt world. But you really need to specify more information.

@dentmaged I actually have more than 1 map that doesn't work, and all from A to Z (the ones that don't work) showed the warn, i have the feeling it does pass thru the loading repo stage

Try loading the world in single player.  If it crashes try using older versions of Minecraft and see if it works there.

Try @CoWinkKeyDinkInc 's suggestion. Try removing the first map from your repository and see if that changes anything. I feel this is more of a map issue than a Cardinal issue.

@twizmwazin @CoWinkKeyDinkInc I tried to open the server with only 1 map on the repo (one that i know that works), and the problem is still the same, the server stops after deleting old match files, and crashes afterwards

I think the problem is servers crash because they try to load the author's names, and because the mojang servers are down it can't load them, and  because of the time it took for the plugin to wait for mojang servers' respones, it crashes

Pablete go to bukkit.yml allow-end: false | server.PROPERTIES allow-nether=false | Delete world, delete rotation and try.

@Prodigy4532 this is something that only happens when mojang servers are down, do you think i can test it?

You can use AlwaysOnline.

@Prodigy4532 cardinal is thought to work by itself, without external plugins.

When servers are down Mojang is better to have something outside who can help.

This server for example: Node42.Minecrafted.net:25593

@Prodigy4532 i don't care about your servers, my localhost for testing purposes should be able to load when mojang servers are down, and simply not load author names, let them be "null" and done, and if i set it to offline-mode, i should be able to join

offline-mode ignore the mojang server login, you can enter whit not problem.

@Prodigy4532 you are not understeanding the issue, even if you set your server to offline-mode, cardinal will not be able to load if mojang servers are down, it will crash on startup

How much memory is dedicated to your server, i have 1024 mb and ofline mode and i dont have this issue :/ | https://gyazo.com/a6913ea7c00a156d7431f55f8aa8ccce

@Prodigy4532 again, you are not understeanding the issue, cardinal can't load because it waits a mojang response for the authors on startup

Another crash report http://pastebin.com/jKBvqpfv

@Pablete1234 Offline mode should be a good recreation of Mojang's servers being down, or atleast I think so. I haven't done Bukkit in ages.

@dentmaged i belive cardinal crashes on startup because it tries to get mapmakers' names from the mojang api, if mojang is down, it waits for a response, and 10 seconds later or so, the request times out and the server continues doing other stuff.
The problem is that the downloading was expected to be done in 1 tick, but it took more than the "max-tick-lenght" (or some name like that) and considers itself crashed.

fixed in cca5fa4


Do not prepare oauth2 config if it is not enabled, do not write config in some sub-commands

Ref:

https://github.com/go-gitea/gitea/issues/25377#issuecomment-1609757289

And some sub-commands like "generate" / "docs", they do not need to use the ini config

Kindly remind: made more changes after approval

I was unable to create a backport for 1.20. @wxiaoguang, please send one manually. :tea:
go run ./contrib/backport 25567
...  // fix git conflicts if any
go run ./contrib/backport --continue


[SPARK-36007][INFRA] Failed to run benchmark in GA

What changes were proposed in this pull request?

When I'm running the benchmark in GA, I met the below error.
https://github.com/pingsutw/spark/runs/2867617238?check_suite_focus=true
java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.j
ava:1692)java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:175)
21/06/20 07:40:02 ERROR SparkContext: Error initializing SparkContext.java.lang.AssertionError: assertion failed:
spark.test.home is not set! at scala.Predef$.assert(Predef.scala:223) at org.apache.spark.deploy.worker.Worker.<init>
(Worker.scala:148) at org.apache.spark.deploy.worker.Worker$.startRpcEnvAndEndpoint(Worker.scala:954) at
org.apache.spark.deploy.LocalSparkCluster.$anonfun$start$2(LocalSparkCluster.scala:68) at
org.apache.spark.deploy.LocalSparkCluster.$anonfun$start$2$adapted(LocalSparkCluster.scala:65) at
scala.collection.immutable.Range.foreach(Range.scala:158) at
org.apache.spark.deploy.LocalSparkCluster.start(LocalSparkCluster.scala:65) at
org.apache.spark.SparkContext$.org$apache$spark$SparkContext$$createTaskScheduler(SparkContext.scala:2954) at
org.apache.spark.SparkContext.<init>(SparkContext.scala:559) at org.apache.spark.SparkContext.<init>
(SparkContext.scala:137) at
org.apache.spark.serializer.KryoSerializerBenchmark$.createSparkContext(KryoSerializerBenchmark.scala:86) at
org.apache.spark.serializer.KryoSerializerBenchmark$.sc$lzycompute$1(KryoSerializerBenchmark.scala:58) at
org.apache.spark.serializer.KryoSerializerBenchmark$.sc$1(KryoSerializerBenchmark.scala:58) at
org.apache.spark.serializer.KryoSerializerBenchmark$.$anonfun$run$3(KryoSerializerBenchmark.scala:63)

Why are the changes needed?

Set spark.test.home in the benchmark workflow.
Does this PR introduce any user-facing change?

No
How was this patch tested?

Rerun the benchmark in my fork.
https://github.com/pingsutw/spark/actions/runs/996067851

Can one of the admins verify this patch?

ok to test

Looks good otherwise

Test build #140615 has started for PR 33203 at commit e635b8e.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45128/

Test build #140616 has started for PR 33203 at commit ba54bd2.

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45128/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45129/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/45128/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45129/

Test build #140615 has finished for PR 33203 at commit e635b8e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140615/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/45129/

Test build #140616 has finished for PR 33203 at commit ba54bd2.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140616/

Benchmark workflow has run successfully.
https://github.com/pingsutw/spark/actions/runs/997616866

Merged to master.

I merged to branch-3.2 too


Readme is out of date

The current version of the package on Maven is 1.1.4, but the readme still details using 1.1.2.

updated


[Bug]  $ gets converted to [$] for snowflake column descriptions

Is this a new bug in dbt-snowflake?

[X] I believe this is a new bug in dbt-snowflake
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
The "$" is getting converted to "[$]" and our usual escape mechanisms (", ', >, . , markdown) aren't working for it. I can create descriptions with "$" directly in Snowflake, so it seems to be a dbt thing. The column descriptions are being persisted to the database.  The dbt documentation is generated as expected.
According to @mikealfare "https://github.com/dbt-labs/dbt-snowflake/blob/29467c32c005de99fdce868fa551e728928a50bf/dbt/include/snowflake/macros/adapters.sql#L12"
Expected Behavior
The $ should show up as $ in the column description in snowflake.
Steps To Reproduce
My writeup is in the dbt notion .
Essentially you need a yml file for the column description with a $ in the comments.
Then,
+persist_docs:
columns: true
Relevant log output
No response
Environment
- OS:running in dbt cloud
- Python: whatever cloud runs
- dbt-core: latest version of dbt
- dbt-snowflake: latest version

Additional Context
No response

This was also discussed in an internal slack channel.  https://dbt-labs.slack.com/archives/C067EUS2D7S/p1721830759272439


Add Item Freeze

As an item owner, I want to be able to set my item to unavailable manually at any time, so the item stays in the system, but cannot be borrowed anymore. This allows me to keep the item to myself, e.g. to fix something or to handle errors in the lending process.
I can revert the asset freeze at any time, so the item can be borrowed again. The waiting list persists during the asset freeze. If an item is currently borrowed and I click the freeze button, it will be frozen when returned.
Dependencies

#8
#16
#30
#18

Acceptance Criteria

[ ] Simple button on item details page to freeze or defreeze the asset (only if I am the owner)
[ ] Frozen items cannot be borrowed but stay in the system
[ ] If item is currently borrowed and owner freezes, it will be frozen when returned

Maybe we can implement this using reservations and waiting lists. Asset freezing is like creating an infinite reservation by the owner. If the item is currently borrowed, we will create this infinite reservation when returned, this functionality will look very similar to the waiting list

If a user has a reservation while the owner freezes the item, the reservation should be cancelled.
Item Freeze Button should remain on the overview page.

If item is currently reserved, the reservation should be cancelled

Features:

[ ] Add column is_frozen to item of type boolean or enum
[ ] Add function freeze to item model
[ ] Add function unfreeze to item model, that creates a new reservation from waitlist
[ ] Add items_freeze_path to items controller for button functionality
[ ] Change create_reservation_from_waitlist method to return if item is frozen
[ ] Add button Freeze that can be seen by everybody having can_manage rights if item is not frozen
[ ] Change button text to Unfreeze when item is frozen
[ ] Show the borrow and reserve button only when item is not frozen
[ ] Show the return button independent of freezing status
[ ] Update status badge to show "Frozen" or "Not Available"

Test cases:
Item is not borrowed and not reserved

[ ] freezing is possible
[ ] unfreezing is possible
Item is reserved, but not borrowed
[] freezing is possible and reservation is cancelled
Item is borrowed and owner clicks on freeze
[ ] The item is frozen when being returned

Questions:

What happens to the persons reservation that is being canceled by the owner when freezing the item? Is it added to the top of the waiting list or does the person simply have bad luck?

Hi @Daniel, when creating an item, what should be the freezing status right after creation? Should it be frozen, so that the owner has to manually allow others to borrow the item? Or should borrowing be allowed right after item creation?

 Is it added to the top of the waiting list or does the person simply have bad luck?

Feedback from Daniel:

when item was created, the status should be active (not frozen)
when item is frozen by owner then reservation should be canceled and the person simply had bad luck. we don't need to add him/her to the waitlist.


Testing, please ignore. (sypgva)

Bug bounty test - please ignore.... Please DO NOT APPROVE THIS! (sypgva)

Spambot, closing PR.


Investigate error message: "The transaction was rejected......"

Can the exact parameters / criteria for this error message be investigated. When and why does this error message occur?
https://imgur.com/e9SDaSa
https://github.com/spectrecoin/spectre/blob/738567c0d3c34e663e5859e23a29b06aa1595406/src/wallet.cpp#L2434

@spectrecoin possible to send me the logs? of when this happens.

Technically this error happens when a TRX is not accepted by other nodes. The concrete problem is your case cannot be evaluated. I close this issue for now.


Rus translation

Not tested

I have checked it and few descriptions need to be fixed:
Champ's Fancy Footwork description has wrong variable.
Guardian's *Time Bomb" description has wrong variable.
It appears that Guardian's *Shield Spikes" have received Temporal Shield's  description leaving both cards with wrong descriptions.
Also I have noticed that Gem cards don't have a Gem keyword in their description, I assume that it had to do with the sub types, which have been removed since last update, so I would suggest re-adding that line at the top of the description.


[V3] Garbage collection

PR #1482 but rebased on v3
I've started on a proposal how we could implement garbage collection to clean up packages no longer needed in the packages folder (and if possible the same for paket-files). Addresses #1416.
Since the packages folder is typically excluded from version control, we do not always have explicit information about a package being removed. What we do know is what packages are currently extracted in the packages folder, and what packages we actually expect to be there according to the lock file.
The proposed algorithm essentially goes through the subdirs of the packages folder, tries to imply group and package names, and drops all of these folders which we identify as a extracted package but are not known by the lock file (ignoring the version).
Questions:

Is it safe to assume that the name of the extracted nuspec file matches the package id, or do we need to parse it to be sure? We could also interpret the folder name instead, which we do construct ourselves (with or without version).
When/where would we want to do this? Should it be explicit? Only on demand? Currently it is rather aggressive: always after add, remove and install, unless --no-install is set, and always after restore. I expect this to be too aggressive in practice.

Is it really necessary to perform garbage collection that aggresively? I would prefer a paket gc command which one could issue when needed.
Git has a similar command, and performs GC from time to time itself. But it doesn't do so on every commit, rebase or whatever.

Aggressive GC has some advantages when you do stuff like automatic tool
detection with fake. Do you have a specific issue in mind?
On Feb 29, 2016 8:42 PM, "Ilja Nosik"<EMAIL_ADDRESS>wrote:

Is it really necessary to perform garbage collection that aggresively? I
would prefer a paket gc command which one could issue when needed.
Git has a similar command, and performs GC from time to time itself. But
it doesn't do so on every commit, rebase or whatever.
—
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/pull/1491#issuecomment-190350992.

The first thing I have in mind is hopping between branches in Git repos. Maybe some more things which I'm not aware of right now.
I can't say much about issues with FAKE, I never noticed a significant performance impact.
But if I see it right, after this PR, Paket performs GC on every restore. Building in VS (or vanilla MSBuild) causes a restore for every project in a solution, if you do <Import Project="paket.targets" />. This might be a problem, I think.


jottacloud: add device registration

Fixes #2995
I have added an additional step when creating the remote that enables the user to create a machine specific. Documentation updated as well

Do you want me to merge this for v1.47 which I plan to push out at the weekend?

Actually yes.
I don't foresee any big hurdles with the PR. Old remotes will continue to work and newly setup ones have to opt-in. So if worse comes to worse, there will always be a fallback.

OK!  I rebased the branch on master and added a comment to silence the linter - hopefully the tests will pass now - I'll merge if they do.

Tests good (except for GolangCI which is broken) so will merge - thank you.


Document and test ability to specify next/throw form in handleActions

See https://github.com/acdlite/redux-actions/issues/102

https://github.com/yangmillstheory/redux-standard-actions/commit/115d89d3e5d3445796fda1a95e8902493a02f40b


Added alt tag to magazine covers for SEO.

Just a little helping hand towards slightly better SEO :)

:tada: thanks Damien!
Now I look at it, we could make it:
{`The front cover of ${title}`}

Ah yes! ${title} works much better!


Figure out what to do about ProblemDetails::Type

Today we're just putting in about:blank because we don't have a good URI for this. We should see if there is something smarter we can do.

For generic status code details, I've just used links to httpstatus.es in the past 😝

@danroth27 FYI

@glennc @rynowak is Problem Details in scope for 2.2?

It is now.

Talked to @glennc regarding this. The intent here is to redirect to some manageable link if the destination is external, so we can control it if necessary.
@pranavkm, if this is not done, can you please handle this? Thanks!

The intent here is to redirect to some manageable link if the destination is external, so we can control it if necessary.

We default to pointing to IETF RFCs and have a way to customize it at startup via options. Addressed as part of https://github.com/aspnet/Mvc/issues/8289


This leethub extension is not working with recently new Update by leetcode.

Please review previous closed issues before filling out a new one! Duplicate issues will be closed without comment.
Describe the bug
This leethub extension is not working with recently new Update by leetcode.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

This leethub extension is not working with recently new Update by leetcode.


feat: RadioItem descriptions

Angular:

React:

Angular code:
<goa-radio-group
  name="color"
  goaValue
  [formControl]="reactiveFormCtrl"
  value="reactiveFormCtrl.value"
>
  <goa-radio-item
    name="color"
    value="red"
  >

      Content description
       Another test?

        Help test

  </goa-radio-item>
  <goa-radio-item
    name="color"
    value="blue"
    description="Item description"
  ></goa-radio-item>
  <goa-radio-item name="color" value="orange"></goa-radio-item>
</goa-radio-group>

.customized-description-title {
  font-size: 14px;
  font-style: italic;
}

@Component({
  selector: "abgov-radio",
  templateUrl: "./radio.component.html",
  styleUrls: ["./radio.component.css"],
})
export class RadioComponent {
reactiveFormCtrl = new FormControl();
}

React code:
<GoARadioGroup name="color" value="orange" onChange={onChange}>
        <GoARadioItem value="red"></GoARadioItem>
        <GoARadioItem value="blue" description="Blue is blue"></GoARadioItem>
        <GoARadioItem value="orange" description={
          <>
          Content description
           Another test?

          Help test

          </>
        }></GoARadioItem>
      </GoARadioGroup>

Checkbox
React:

Code:
<GoACheckbox
      name={"desserts"}
      value={"ice cream"}
      text={"Ice cream"}
      checked={false}
      description={
        <>
          Content description
           Another test?

            Help test

        </>
      }/>

Angular:

<goa-checkbox
  goaChecked
  name="description"
  text="Checkbox with description"
  description="Lorem ipsum dolor sit amet consectetur adipisicing elit. Aliquam dolor"
>

    Content description
     Another test?

      Help test

</goa-checkbox>

Tested Radio and Checkbox for React and Angular for Text, Html, Html Encoding, Inline Styling,

:tada: This PR is included in version 1.17.0-alpha.22 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 4.17.0-alpha.17 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 3.0.0-alpha.4 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Unnecessary kwags['network']='1,2' on station_list() call?

Hi,
I was experimenting with MesoWest API directly on Oahu Island and noticed the following API request:
http://api.mesowest.net/v2/stations/metadata?bbox=-158.42,21.18,-157.63,22.26&token=1234567890
which imposes a bounding box on the island had a different amount of stations than my call on station_list(). Specifically it narrowed down to 22.
Further inspection on the MesoPy code made me realize the hard-coded parameter:
kwags['network']='1,2'
Which is optional on the API call (http://mesowest.org/api/docs/) but apparently required on the code. Commenting the following parameter fixed the issue. Is there any particular reason for this restriction?

Hi @carlosandrade!
Good catch on that. I think originally when I was testing the library I set that to filter out some inactive stations and such to cut down on response time and the amount of data being returned. Anyway, I've removed it and updated the func docstring. Expect MesoPy to gain a ton of features soon...we're working on adding a great deal of new ways to play with the API right now.


Fixed get_cluster() method

Issue link

Closes #431
What changes have been made

Ingresses have the label ingress-owner: appwrapper which is used to identify them.
When mcad=True the SDK gets the the ownership reference from the ingress object to identify and check it is a match with the appwrapper name.
When mcad=False the ingresses are listed and the domain is gathered from the ingress with the ingress-owner label.
For both scenarios the ingress domain is extracted from the host of the ingress.
Fixed missing ingress creation steps for the _component_resources_up and _component_resources_down functions for cases when mcad=False.
Verification steps

Run through a demo notebook and create a Ray Cluster on Kind and OpenShift.
run cluster = get_cluster(name, namespace)
cluster.down() and other cluster. commands should work.
Create a Ray cluster with mcad=False an ingress should be created now and get_cluster() should work too.
Checks

[ ] I've made sure the tests are passing.
Testing Strategy

[x] Unit tests
[x] Manual tests
[ ] Testing is not required for this change

The get_cluster() function now asks for ingress_domain for the case of Kind clusters. It defaults at None and is not required on OpenShift clusters.

Why does get_cluster() function need to know Ingress domain? The cluster already exists, Ingress was applied when cluster was created.

@sutaakar

Why does get_cluster() function need to know Ingress domain? The cluster already exists, Ingress was applied when cluster was created.

The get_cluster() function uses the from_k8_cluster_object(rc, mcad=True) function to create a new Cluster Configuration
We use the Ray cluster spec rc to gather info like image, name, machine_types, etc.
Unfortunately we cannot gather the domain name which was used originally to create the cluster because it is not included in the Ray cluster spec and was put in place when the ingress object was created in the AppWrapper.
This is necessary as we plan to reintroduce routes in #407 and we will not be supplying domains for them as OpenShift does so automatically.
Alternatively we could go under the assumption that the ingress is created successfully and use list_namespaced_object to gather the ingress and extract the domain from the host that way. If that doesn't work we can ask the user to supply the ingress name in get_cluster WDYT?

@Bobbins228 I am still not sure what do you need the domain for when calling get_cluster().
If you create a cluster then you need this value to create Ingress resource. But for get_cluster(), the Ingress already exists, you don't need to create it any more. So, why is the value needed?
Do you need domain to compute what is the Dashboard URL, or is there any other reason?

@sutaakar
When from_k8_cluster_object creates that new ClusterConfiguration an appwrapper is created the exact same way we would create one before calling cluster.up() see ClusterConfiguration init here
To create this app wrapper we need all required fields to be fulfilled in the case of Kind clusters ingress_domain is required despite the fact the cluster and ingresses have already been created previously.
from_k8_cluster_object does most of the job filling in the appwrapper for us but ingress_domain is not as simple to fill in automatically.

@Bobbins228 What will happen in case user fills some random value as ingress_domain, i.e. "abcde.com"?
From your description it looks like the value is solely needed to fulfill internal implementation requirements without any functionality overlaps.

@sutaakar
I see your point in the case the user provides the wrong ingress_domain I think you could still use it for any cluster. functions but ultimately the aw is wrong in that scenario.
It is not ideal hence the suggestion to first check for the ingress in the namespace and gather the domain from the host before asking for the ingress_domain.

Yeah, I'm not a huge fan of this either. Could you add an annotation to the ray-cluster that has the ingress domain and then get it directly from there?

Another option could be to assign an owner for Ingress/Route (if it doesn't have) and use it to query for Ingress belonging to the AppWrapper or Ray cluster.

@KPostOffice @sutaakar
I have updated the PR,
We now get the appwrapper object and extract the domain from the ingress Host when mcad=True and in the opposite case we get the ingress object that has the ingress-owner: cluster_name label and extract the domain from the host there.
You no longer have to provide the ingress_domain for get_cluster

@sutaakar I was able to apply the owner functionality in relation to ray clusters created with app wrappers but ingresses created when mcad=False do not have an owner so I have kept in the label for that case.

When does the mcad=False case happen?

@sutaakar
Yes it is a parameter of the cluster configuration.
By setting mcad=False an appwrapper is not created instead a yaml file featuring the RC, Ingress and secret.
The SDK will use KubeRay to create the ray cluster and individually create the ingress and secrets which would make them have no owner in the traditional sense.

hmm, so SDK creates RayCluster CR directly. Would it have sense to add owner for Secret and Ingress pointing to RayCluster CR?

@sutaakar To add a owner reference I need to add in the uid of the ray cluster right?

@Bobbins228 Right, uid is required.

@sutaakar We won't be able to apply the uid of the Ray Cluster to the ingress because it is created when the rc is up. Ingresses and secrets are created at the same time.
For the case of mcad=False we will have to keep the ingress-owner label

/lgtm

@Srihari1192 do you want to review the PR too?

un cluster = get_cluster(name, namespace)

Sure will take a look

@Srihari1192 do you want to review the PR too?

Sure will take a look

@Bobbins228 @sutaakar I have noticed below error when testing with this changes in this PR at step get_cluster('mnist',namespace)
Traceback (most recent call last):   File "mnist_rayjob.py", line 12, in <module>     cluster = get_cluster('mnist',namespace)   File "/codeflare-sdk/codeflare-sdk/src/codeflare_sdk/cluster/cluster.py", line 710, in get_cluster     ingress_domain = ingress_host.split(".", 1)[1] IndexError: list index out of range

@Srihari1192
Have you set your ingress up with ingress_domain or ingress_options?

@Bobbins228 Yes the Ingress_options is set same as in sdk test here and also i tried verifying existing sdk tests same error here aswell https://github.com/project-codeflare/codeflare-operator/actions/runs/7406823001/job/20151892482?pr=424

@Srihari1192 What is put in place of the host for CLUSTER_HOSTNAME?
https://github.com/project-codeflare/codeflare-operator/pull/424/files#diff-1031535ceb5f0388a7c0f2806f2b424d4d28f6ebade12641003801701662e695R11

@Srihari1192 What is put in place of the host for CLUSTER_HOSTNAME? https://github.com/project-codeflare/codeflare-operator/pull/424/files#diff-1031535ceb5f0388a7c0f2806f2b424d4d28f6ebade12641003801701662e695R11

It will be set based on the cluster type here https://github.com/project-codeflare/codeflare-operator/pull/424/files#diff-572dd9104509ce659f6f38075e4ad54935cb91373ab4a03c3a05eaa91f4c39c8R190-R206

@Srihari1192
Okay there is an issue here with the way we get the ingress domain from the host.
Here we get the host from the ingress associated with the Ray Cluster and try to get the domain by extracting the string after a .
I will have a look further to see if there is a better way to extract the ingress domain from the host.


Add device discovery

Discovery should be implemented, in order to detect the Google Home device's IP. By using the pychromecast API, this can be achieved, for example, with the following snippet:
import pychromecast

VALID_GOOGLE_HOME_MODELS = [
    "Google Home",
    "Google Home Mini",
    "Lenovo Smart Clock"
]

def discover_google_home():
    print("Discovering Google Homes...")
    services, browser = pychromecast.discovery.discover_chromecasts()
    for service in services:
        model = service[2]
        name = service[3]
        ip = service[4]
        access_port = service[5]
        if model in VALID_GOOGLE_HOME_MODELS:
            print(f"{name} ({ip}:{access_port}) - {model}")
            print()

The port is more or less useless, since as far as I know, for every Google Home the port is the same: 8009, but, who knows.
This should be added to the integration in the discovery.py file, as stated by the Home Assistant documentation.
I will start working on that, and see if we can make the device configuration easier.

I like the idea of auto discovery! I guess for now we can simply utilize glocaltokens package to get IP addresses (See https://github.com/leikoilja/ha-glocaltokens/issues/16#issuecomment-776796188), but auto discovery would be a whole new level 😎

Nice, that solves the problem then. I also tried to find it in homegraph but couldn't, do you have some information on how?

I will try digging in tonight, will keep you posted if I ll find a way how to. Will probably implement it into glocaltoken right away, if I ll be able to find those :)

what about hostnames? can we compare hostname in homegraph to a hostname found with pychromcast? or are there other identifiers?

I ll try to dig deeper tomorrow into homegraph, because somehow I remember seeing the IP addresses of devices somewhere 😄  I can't just let it go now

what about hostnames? can we compare hostname in homegraph to a hostname found with pychromcast? or are there other identifiers?

I think in that case it's easier to simply show the user a list of devices from pychromecast, and then create a relation between the "display name" in pychromecast and in Homegraph, since they should be the same.

I ll try to dig deeper tomorrow into homegraph, because somehow I remember seeing the IP addresses of devices somewhere 😄 I can't just let it go now

By looking at the RPC API docs I can't find anything about an IP address...

Using mDNS(pychromecast) we can make an reverse lookup and get the IP from that. If we can find I'd string in homegraph. Then we can make an reverse lookup with socket.gethostbyname in python by adding ._tcp.local afterwards. But I don't know if this will work or if homegraph has this string included

I've implemented some code at the glocaltokens repository. Did some testing and it seems to work pretty well.

For now, will move the conversation to glocaltokens and once it's implemented there, we will start working at ha-glocaltokens. Will reopen as soon as it's ready there.

Waiting for glocaltokens to merge device discovery. See here

@DurgNomis-drol, device discovery in glocaltokens is merged, thanks to @ArnyminerZ. Now we should look deeper into whether we can use that functionality straight from glocaltokens or we should utilize HA build-in mechanisms as described here: https://developers.home-assistant.io/docs/creating_integration_manifest/#zeroconf

I don't think there is any reason to duplicate his work. The only reason that we need discovery in the first place was because of the IP address. I have already made sure that dev branch should work, we just have to delete 1 line and we are done.

Sounds good, @DurgNomis-drol. Do you want to take a lead on this one? (If so, please just assign yourself to the ticket) 💥

Yes I will do that
Off topic, do we only aim to implement this as a custom component or do we aim to get it include in the official release?

@DurgNomis-drol, device discovery in glocaltokens is merged, thanks to @ArnyminerZ. Now we should look deeper into whether we can use that functionality straight from glocaltokens or we should utilize HA build-in mechanisms as described here: https://developers.home-assistant.io/docs/creating_integration_manifest/#zeroconf

I think that shouldn't be needed, unless we want to do like chromecast does, which detects devices in the network without having to search for them, which would be quite useful.

It already does this :smile:

@DurgNomis-drol, do you mean that it already detects chromecasts as well?

Everytime it updates it self, it checks if glocaltokens have found a new google home device and then adds it and create sensor, or it removes it if it know longer exists

Right! Nevermind, I think i got confused for a second.
Anyways, do you guys think we should leave "utilizing HA zeroconf" for later as a "future enhancement"?

Closed in https://github.com/leikoilja/glocaltokens/pull/13


KAFKA-15114: Minor: Update help in StorageTool for creating SCRAM credentials for KRaft bootstrap.

The choice of using name vs. user as a parameter is because internally the record uses name, all tests using the StorageTool use name as a parameter, KafkaPrincipals are created with name and because creating SCRAM credentials is done with --entity-name
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

The author has proposed to backport this to 3.5 and it looks like a harmless change to me. Will backport to 3.5 branch (to be released in 3.5.1)


Add Galley into Finch Codebase

In order to ease downstream integrations, this PR adds the codebase from Galley.jl into the Finch.jl codebase as a sub-module. This means that all users which call using Finch will have access to Galley as an optimizer without additional deps. This should simplify the user experience and allow for the possibility of Galley as a default in the future.
Necessary Changes:

[x] Remove galley backtests from CI
[x] Add galley sub-module
[x] Merge galley tests into one file and add to runtests.jl
[x] Add galley deps to project.toml
[x] Add documentation for Galley in Array API

The documentation in the array API section is likely to get moved around in https://github.com/finch-tensor/Finch.jl/pull/640

Perhaps we can merge both of these, then do an update which improves the docs.

These windows failures look like they are from expecting UInt == UInt64 somewhere, or similar, but I can't find where


I can't open the bash when I use the sublime_terminal to launch the powershell

Please use the following bug reporting template to help produce actionable and reproducible issues:

A brief description
I report the problem in here :https://github.com/wbond/sublime_terminal/issues/126#issuecomment-237084448

Expected results

Actual results (with terminal output if applicable)
can't use the bash in the powershell

Your Windows build number:14393.10

Steps / commands required to reproduce the error
my sublime_terminal user setting:
{
"terminal": "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe",
"parameters": []
}
when I open the terminal ,it show the result:

Hi @czmecho -- are you able to run bash directly (the start-menu shortcut)?  Or at a regular Windows Command prompt?
I don't have any problems launching it via PowerShell; the above works fine for me.

Hi @aseering
I can run the bash  in the powershell or in the cmd normally.
but it will happen like above when I use the sublime_terminal to call the powershell.

@czmecho I think if it's working in powershell and cmd, you should probably send a bug report to the guys at sublime?

@czmecho out of curiosity, does it work if you do C:\Windows\System32\bash.exe?  (Or whatever the correct absolute path is to bash.exe on your machine.)
If so, I'm guessing that sublime is removing some entries from the PATH environment variable for some reason.

@aseering

I think you are right.

@czmecho Can you echo your $env:PATH in both environments to see if your path is being modified?

@wbond http://ww4.sinaimg.cn/large/7df5111fgw1f6hfq307c1j21bx0m57lj.jpg
I have po some picture in https://github.com/wbond/sublime_terminal/issues/126

If so, I'm guessing that sublime is removing some entries from the PATH environment variable for some reason.

@aseering It seems that @czmecho's path is the same in both cases.
The Terminal package for Sublime Text doesn't mess with the path.
I'm not familiar with Bash on Windows – is it really installed on the path by default? Some of the websites I saw that referenced it showed clicking a link in the start menu.

Hm...  Well, it looks like it's installed to C:\WINDOWS\System32\ on this machine.  (It's in the same place on my laptop, for what it's worth.)  And that folder appears to be in PATH, based on those screenshots.
That is an important system directory.  Maybe that directory is treated specially in some contexts?  Can sublime find other executables in it?
There is also a Start-menu shortcut.  I have used both to launch bash.exe; they both seem to work...
(I'm not a WSL developer, just another person using it.  Someone on the WSL team would probably know more than I.  But, I mean, bash.exe starts off as just an executable; maybe it would error out, but if it's in PATH, I feel like sublime really ought to at least find it...)

Apparently the issue was with execution policies.

@wbond I thinks it's a better way to solve the problem when I put the c:\Windows\sysnative\ in the PATH environment variable .
while I found after I change the execution policies,it can't work whatever I change it back to unrestricted.


Tailwind Configuration

Added tailwind css to the project.
Added colors, typography, and shadows to tailwind config.

I approve this too!


gymValidDataLimit doesn't work right

When Gym wasn't updated within days given in gymValidDataLimit it disappears from the map. It should go blank instead

Fixed in #425


fix RestRouterHandler function return type 'const &' error

PR checklist:

Did you run ClangFormat ?
Did you run CheckStyle ?
Did you check the comment / log / exception conventions in Engineering code process wiki page ?
Did you import unnecessary headers ?
Did you surround Daisy : starts/ends for new code in existing ClickHouse code base ?

Please write user-readable short description of the changes:
**remove RestRouterHandler function return type 'const &' to resolve the temporary variable default_value ref error **

What's the problem here ?


Animation problem of card and tabbar

How to fix the problem of card and tabbar?

@walterkyo Exactly.
You can solve this by hiding the tabbar before the animation in the Animator file so the snapshot in the animation context will be TabBar-free.
Apple anyway solves this by presenting a new tab bar in the animation context.


nio server eats up 100% of CPU

Running nio server seems to eat up almost 100% of CPU (on OSX at least), where run_nio seems fine

Oh, I see that now too. These 8 cores Macbook Pro CPUs make it less obvious that you're using a whole core. When running with --backround it's fine, but the problem is the way it prints the logs out.


Merge JupyterCAD "Object Properties"  panel with Notebook Cell Properties panel

Both panels have a very similar UI and are (at least partially) based on react-jsonschema-form to produce the content.
I wonder if (given some changes upstream in this panel), we could reuse it for JupyterCAD.

Thinking more about this. The solution might actually be to create a more generic property inspector that could be usable by the notebook instead.

Closed in favor of  https://github.com/jupytercad/JupyterCAD/pull/554


[RFC] Structured data for non-built in commands

Summary of the new feature / enhancement
Hi,
I am looking at coming up with a portable way to tell programs that they can output structured data, and telling the shell that the said data is structured according to the given format. For this I have a draft proposal write-up at https://github.com/KoviRobi/structured-shell-stdio but I would like some feedback. Especially as I don't have much experience with PowerShell or Windows, I come from a Linux/nushell background.  I don't know how well the file-descriptor idea could be applied to Windows, so please leave feedback either here or on the proposal.
Thanks,
Robert
Proposed technical implementation details (optional)
A way to communicate to external programs that they can output JSON, and for the program to communicate to PowerShell that it is receiving JSON, without having to guess.
This should avoid having to define aliases for all the commands that support e.g. JSON, for example
ip --json addr | ConvertFrom-Json

could become just
ip addr

From your specification

Tell the called program to output JSON
Tell the shell that the output isn't just plain text but actually JSON

What it sounds like you really want is that the programs support the HTTP protocol over their stdin and stdout so that you can pass in headers like Content-Type and Accepts, and get Content-Type along with the response body.
Alternatively you could look at the Common-Gateway-Interface which uses environment variables to pass the same data.

The program should ensure the file descriptor is valid at the start,

I am not sure what you mean by valid here. Unless you are running a suid program if you have the rights to read or write then you have the rights to read or write, that does not become an attack. If you fail to read or write then you terminate the program with an error as normal.

I don't know how well the file-descriptor idea could be applied to Windows

Windows uses file handles rather than file descriptors. In order to share them with another process you normally use DuplicateHandle, including when using CreateProcess in order to indicate the permissions the other process has.

I would like to focus on the JSON_STDOUT environment variable in the POSIX environment. So assuming everyone has their first edition copy of UNIX Network Programming by W Richard Stevens we should be able to say that.

File descriptors, unless you do something (eg set CLOEXEC) are inherited by child processes.
Environment variables are also generally inherited, although it does depend on which form of exec you use.

So lets say we have a JSON_STDOUT aware shell, and it wants to use JSON everywhere so it passes JSON_STDOUT with a new pipe to every program that it runs in the hope that it returns JSON.
Those that do write the the JSON_STDOUT file descriptor work, and so do those that don't because the shell can tell the difference.
So the shell happily calls the updated program A which now writes JSON output to the shell. All well and good.
But the shell also calls program B which is not aware of JSON_STDOUT and does nothing with it, it writes its output to stdout. Shell is happy because it knows this is not JSON.
Now, program B uses program A. When program B forks then execs A, it will inherit the original JSON_OUTPUT and file-descriptor from the shell. So now program B no longer gets the output from program A, because program A is writing it to the shell using the pipe that was opened to get the JSON output of program B.

This is to avoid potential attacks where an attacker will inject the JSON_STDOUT for a shell which doesn't support this

This is exactly what the JSON aware shell did, and now program B passed the JSON_STDOUT to program A because that's how the system works.

This is very timely as this is exactly a problem we've been thinking about and I was planning on publishing a proposal for this later this month.  I'll summarize the current thinking and it aligns with some of the thoughts you already have:

The shell (PowerShell in this case, but can work with any shell) would have an env var called SHELL_STDOUT_PREFERRED_OUTPUT that commands would look for.  A value of json would tell the command to emit JSON without needing any switches/parameters.  We decided to keep this open ended rather than JSON specific.
JSON emitted this way would be per line per object.  Any lines that are not valid JSON would be re-emitted to the pipeline as-is (same as it would work today w/o JSON).
There is nothing in our proposal that is PowerShell specific as we hope other shells and commands adopt this idea

Given that there is other interest in this, I'll make it a priority to have a spec published by middle of this month.

The shell (PowerShell in this case, but can work with any shell) would have an env var called SHELL_STDOUT_PREFERRED_OUTPUT that commands would look for.

Wouldn't this have the same environment variable inheritance problem? A shell executes program B with SHELL_STDOUT_PREFERRED_OUTPUT, but program B does not know about SHELL_STDOUT_PREFERRED_OUTPUT and executes program A which does, then B will not get the format of data it used to get when SHELL_STDOUT_PREFERRED_OUTPUT is not set.

A value of json would tell the command to emit JSON without needing any switches/parameters.  We decided to keep this open ended rather than JSON specific.

If the goal is to be open ended then I suggest using MIME types, eg application/json etc would be better.

As an example of a tool supporting something similar ( but not through environment variables )
AWS CLI Output format
It is an example of a configuring a default output format for when it is not specified on the command line. So this is a tool specific user/installation based default. The supported format as json, yaml, yaml-stream, text and table.
This actually suggests that if you want a reliable portable script you should always specify the format on the command line because any installation could have a different default output format.

@rhubarb-geek-nz in your B->A use case, that's no different than if A changes its text output and the regex used by B gets broken.  So if B is taking a dependency on A, it needs to be aware of the output.  And if JSON becomes the common output of command-line tools, then it's better for B because it structured than text.
The AWS solution is application specific and also requires the user to manage it which is not ideal for adoption.  Outside of PowerShell, tools like jq is already gaining some popularity for tools that can emit JSON.  The difference here is how to inform tools to do it by default.
Reliable scripts already have a problem today if the version of the tool changes and the text output changes.  I understand the transition challenges for tooling expectations of moving from text to JSON, but scripts can also unset that env var.

@rhubarb-geek-nz in your B->A use case, that's no different than if A changes its text output and the regex used by B gets broken. So if B is taking a dependency on A, it needs to be aware of the output. And if JSON becomes the common output of command-line tools, then it's better for B because it structured than text.

This reminds me of the PSModulePath story. A lot of headaches as it was and still is. (If we also assume a utility that hosts PowerShell...)

Reliable scripts already have a problem today if the version of the tool changes and the text output changes.

I'll remind you of that again #13428
Users accept and use ready-made things with simple and clear concepts but ignore what takes effort to understand and implement.
For PowerShell to work fully, it needs meta-information which is missing from native apps. This information is best provided in PowerShell concepts. I would suggest the PowerShell SDK for native apps so that developers can replace Console.Write() with PSNativeSDK.WriteSerializedPSObject(). (And it doesn't matter if it's XML or Json or whatever.) Without that, you need a PowerShell-inspired wrapper, and a processing type - PSNativeCmdlet. In particular it allows us to specify output parsers for any version-aware utility.

@iSazonov requiring a SDK means that tools will have to develop for a specific shell which would impact adoption completely.  Also, PSModulePath has specific problems because it's not treated as a pure env var and the host does manipulation to it assuming what the user wanted.

in your B->A use case, that's no different than if A changes its text output and the regex used by B gets broken. So if B is taking a dependency on A, it needs to be aware of the output.

Which is why we don't do it. The UNIX/POSIX/Linux command line tools are incredibly conservative and resistant to change precisely to prevent breaking other scripts. Extensions are typically enabled explicitly by command line options if the output will change.

And if JSON becomes the common output of command-line tools, then it's better for B because it structured than text.

JSON is good for somethings but it is not the solution to everything. Being simple means it is easy to parse, but likewise has no conventions for dates, for how to include binary data. It has no schema mechanism to validate that all data are present and has no standard for digital signatures to ensure integrity. It is not good for continuous streaming.

The difference here is how to inform tools to do it by default.

Unfortunately the mechanisms that have been presented are fundamentally flawed. It means the behaviour of the programs will change depending on the environment variable and any application or script that does not handle that environment variable will break. If I have a script C that behaves one way when it is invoked by bash but a different way when invoked by some json-shell then I now have an unreliable script.

I understand the transition challenges for tooling expectations of moving from text to JSON, but scripts can also unset that env var.

So your proposal is that every program that already optionally supports JSON has to recognise this environment variable, and every other batch file, shell script, Python/Perl/C/C++/PLI/Pascal/Cobol program that already uses those first set of programs has to be modified and/or recompiled? That isn't "tooling expectations" that is "breaking entire ecosystems".
As it is, it is more likely to be a case of "everything breaks when I try to run it with json-shell therefore I won't use json-shell".
The cost of not doing this is just having to use existing programs command line options to select JSON output. The cost of implementing this is chaos.

I understand the transition challenges for tooling expectations of moving from text to JSON

I am going the play the Devil's Advocate and challenge the idea that using structured data is automatically better.
Although this example is XML rather than JSON, the principles are the same, and it should look pretty familiar.
SQLite.Interop.Static.2017.vcxproj
So that's a Visual Studio project file, it describes a project, how to build it and the various compiler options. It looks fairly modern, as far as I can tell it's the most recent in the file set. It is for Visual Studio 2017 and builds both x86 and x64.
Let's have a look at the equivalent Makefile.
SQLite.Interop.mak
So that looks like it comes from the 1980s, it does not cater for all the build scenarios in the Visual Studio project and looks pretty primitive.
So why bring that up and what has it got to do with PowerShell anyway?
This
This is a PowerShell script that downloads the source, validates it, patches the source and builds four architectures; x86, x64, arm32 and arm64 using Visual Studio 2022 and the simple makefile.
In my opinion the purpose of PowerShell is to orchestrate new and existing tools to solve problems, not demand that all programs change in order to somehow become simpler to use with PowerShell.

Tell the shell that the output isn't just plain text but actually JSON

SHELL_STDOUT_PREFERRED_OUTPUT

The first proposal suggests that it handles both original format and JSON, the second proposal use the term preferred which suggests this is optional. What is the behaviour of the shell if the output is not JSON?
If we revisit our good friend the AWS CLI tool ...
$ aws --output xml apigateway get-rest-apis
usage: aws [options] <command> <subcommand> [<subcommand> ...] [parameters]
To see help text, you can run:

  aws help
  aws <command> help
  aws <command> <subcommand> help
aws: error: argument --output: Invalid choice, valid choices are:

json                                     | text
table

It is explicit and fails if you ask for a format it does not understand. Do you have to handle multiple formats for each output?

First of all, thank you for your interesting points, I want to make it clear that a discussion is what I am after, rather than my solution already being a fully formed one :)

With stdin/stdout there is nothing that says it plain text at all, they are normally byte streams.

Yeah I agree I phrased it badly, I didn't mean to say it's printable characters/7-bit clean etc, I just meant that usually CLI programs output information for human consumption, which is why the line-oriented format is so pervasive I think, as it's a compromise between human readable, but also for some simple cases not too difficult to manipulate by grep/sed/awk etc.
I also value the mime-type suggestion, I chose JSON because it's output by a fair few of the programs I happen use, but there's downsides to JSON too, plus if you allow me a bit of a segue the other day I was just wanting to transfer a public SSH key to my phone, for which qr-codes should be fine, in fact you can even get phone virtual keyboards that support that, but on the other side, in the shell while I can run qrencode 'Hello, world!' -o - it just dumps out a PNG, instead of having something that can be displayed, though

❯ qrencode 'Hello, world!' -o - -t utf8
█████████████████████████████
█████████████████████████████
████ ▄▄▄▄▄ █▀▀ ▄ █ ▄▄▄▄▄ ████
████ █   █ █▀▀▄▄ █ █   █ ████
████ █▄▄▄█ █▀▄█▀▄█ █▄▄▄█ ████
████▄▄▄▄▄▄▄█▄▀▄█▄█▄▄▄▄▄▄▄████
████ ▄▄▄ ▀▄▄ █▀▄▀ █▄▀ ▀▄▀████
████▄ ▀▄▄▀▄▀ █▄▀  ▄▀█  ▄█████
██████▄▄▄▄▄█ ▀██▄▀  ▀▀██▄████
████ ▄▄▄▄▄ █▄▀██  ▄ █▀  █████
████ █   █ █ ▀ ▄▄▄▄▀ ▀█▄▄████
████ █▄▄▄█ █ ▀▀▄ ▀▄▄▀▀ ██████
████▄▄▄▄▄▄▄█▄▄█▄██▄█▄██▄█████
█████████████████████████████
█████████████████████████████

does kind of work. But this got me thinking more about what I am after, which is an ability to have smarter terminals/shells that support graphs, images, structured data etc. Kind of like jupyter notebooks I guess, so I should look into how they work too.
Given this, I think I need a better name than structured data, any suggestions.
The comment about A -> B -> C where A and C support this protocol, B doesn't, is very insightful and shows a fundamental weakness, thank you! In my mind, it was only using it as an extra output channel, but even with that it has a problem. Just to translate it to my words, this is bad because supposing you do PowerShell -> bash -> C (where the bash -> C could be just due to running a bash script, e.g. bash gets run transparently due to the shebang), then all the information of your bash script will leak into your powershell which is the very least undesirable, especially if the script C produces a lot of output. For normal shells this would just get lost in the shell history, but the behaviour here could be out of memory which is bad.
I think the SDK could be a good solution, I raised the environment variable as one that I could think of but it is not necessarily the way forward and for me the discussion of that does fall under all of this/the structured shell stdio. I think for the SDK important points are

portable across systems -- different SDKs for different systems is fine I imagine, as you have different executables anyway
portable across shells within the same system -- it would be mad to have several different executables depending on the shell, e.g. iproute2-ps and iproute2-nu would just make systems a bit broken. I think this is doable though, I am only envisioning this communication to the calling shell, so the SDK could perhaps just look that up in the process hierarchy?
small/fast, as I imagine people will only use it if this is the case
reasonably easy to use for the software/external commands wanting to output more than just byte-streams of unknown data. Of course software will have to have changes to support this, and existing software shouldn't be broken if it doesn't, otherwise we cause chaos. I guess I want the software making use of this SDK to not have much more difficulty than just adding a --json flag (or whatever, JSON is just on the tip of my tongue but XML, or SQLite etc work) and then outputting that to stdout (probably via some deserialisation code).

And in some way I wanted to go towards the SDK solution even with my env. var solution, I just thought of it as consistent and easy to use, but if the SDK abstracts away all the platform/shell dependencies then that's grand
So I guess any ideas about how this SDK might work? I don't know how well the discovering parent process to see if it supports this channel works, but I guess it avoids the A->B->C problem as in this case C's parent process is B not A. And if we do want to create a child process C that does structured outputting all the way back to A, then we need to do some extra steps (hopefully small) to do this, which is the right way around, in that defaults should do existing behaviour.
Also apologies for my delayed response, and tendency to ramble, this is a highly speculative side project so I don't always have time for this, and when I do it's often in the evening when I'm a bit lower on energy so my inner editor isn't here to cut things down

Going back to CGI, the HTTP Accept header is more than a suggestion, if a server can't provide what is requested then it would return 406 Not Acceptable.

I've been trying to understand how CGI is applicable, in some ways I see the superficial similarities, but to my understanding CGI is mostly a way to just pass HTTP query parameters, and it expects the output to be HTML?
I guess environment variables would have the same A->B->C problem.
And it wouldn't solve the second part of the communication, communicating back to the shell that the data is more than just a byte-stream? I think CGI has the expectation that every command outputs HTTP, here as you pointed out we cannot be sure there is more to the outputs than byte-streams, some way of communicating back to the shell would be much better than just guessing/libmagic.

but to my understanding CGI is mostly a way to just pass HTTP query parameters, and it expects the output to be HTML?

Far from it! With CGI you can implement any HTTP verb and can return any format of data. Its response is a set of headers and the body.

| I am going to play the Devil's Advocate and challenge the idea that using structured data is automatically better or necessary.
It's not necessary in that PowerShell already works with non-structured output today already.  However, structured data (whether XML, JSON, or something else) means you can get better discovery (a la Get-Member) and consistent access (a la dot-notation).  You can already see this via ConvertFrom-Json or using [xml] accelerator.
| What is the behaviour of the shell if the output is not JSON?
This was described above in that it behaves like it does today.  By having JSON per line, it's easy to detect if it's valid JSON or not.  Commands that emit JSON via something like --json tend to emit pretty print JSON so wouldn't be treated as JSON for the purpose of this discussion.
Also, this behavior would be opt-in (whether via the env var or other means) so existing scripts continue to work as they do today.
| If the goal is to be open ended then I suggest using MIME types, eg application/json etc would be better.
The goal is to standardize on JSON, but allow for other types to be more future proof.  Supporting literal MIME types I think can lead to misunderstanding of what is actually supported.

This was described above in that it behaves like it does today. By having JSON per line, it's easy to detect if it's valid JSON or not. Commands that emit JSON via something like --json tend to emit pretty print JSON so wouldn't be treated as JSON for the purpose of this discussion.

So the idea is to standardise on JSON by using "JSON per line" which isn't JSON, and existing tools which already support JSON output wouldn't be counted as JSON.
So an existing tool that uses "JSON per line" but writes just one line, wouldn't be counted as JSON because it is identical to JSON?

I've have a spec posted here that includes a proposal for structured data for native commands: https://github.com/PowerShell/PowerShell-RFC/pull/348/files


Figure out best printing format for status bar

Over in #90, @sofroniewn, @kne42, and I were discussing the formatting of numbers in the Napari status bar. No format string produces satisfactory results for all input types, so we need to write a function that picks the right format string for the right situation. See https://github.com/Napari/napari-gui/pull/90#discussion_r247782298

As noted by @royerloic in #372 - when changing the dims sliders

The status bar should display something like:
[3, 5, :, :], layer_name, value ...
where 3 or 5 are changing depending on the dim slider being moved.
the ':' are there because we are not hovering over a pixel, so in some sense
we have nothing relevant to give there.

With #485 this has been dramatically improved. We now have a consolidated all our status formatting to one function inside the utils folder that can be tested / improved independently.


Performance/Casecmp not equivalent to string.downcase==string

Although, casecmp is a faster way to do case-insensitive string comparison than applying a case function, not all cased-comparisons are case insensitive.  Take the example string.downcase==string.  We are actually asking: is the string lowercase?  There are alternatives like regexes, however they are far less clear in code and can have annoying corner cases.

This ought to be fixed on master now

Cool.  It might be worth adding the following tests.  Otherwise, I look forward to using the next version of master.
    it "doesn't report an offense for str.#{selector} == str" do
      inspect_source(cop, "str.#{selector} == str")
      expect(cop.offenses).to be_empty
    end

    it "doesn't report an offense for str == str.#{selector}" do
      inspect_source(cop, "str == str.#{selector}")
      expect(cop.offenses).to be_empty
    end

If tests like you show are not there, please open a PR. I can't remember if
I already added them or not.
On Feb 27, 2016 12:51 AM, "aarondcohen"<EMAIL_ADDRESS>wrote:

Cool. It might be worth adding the following tests. Otherwise, I look
forward to using the next version of master.
it "doesn't report an offense for str.#{selector} == str" do
  inspect_source(cop, "str.#{selector} == str")
  expect(cop.offenses).to be_empty
end

it "doesn't report an offense for str == str.#{selector}" do
  inspect_source(cop, "str == str.#{selector}")
  expect(cop.offenses).to be_empty
end

—
Reply to this email directly or view it on GitHub
https://github.com/bbatsov/rubocop/issues/2893#issuecomment-189515608.

Equivalent tests are already there. This can be closed.


Fix syntax bug

Coverage remained the same at 51.885% when pulling f08de79bc3e4c94e00de4e3a1ea172dd1b4b83ba on toymachiner62:patch-1 into d82ecf0cc41467703c0e448dbcd5666728ed42d1 on cornerstonejs:master.


add link to beta downloads (commented out)

We have enough horizontal space to simply duplicate the download buttons for all platforms in a second column.

So what would be the process of uncommenting?

Unwrap the contents of the $(COMMENT ...) block.

We have enough horizontal space to simply duplicate the download buttons for all platforms in a second column.

Right, will work on that.


Appstudio update test-pac-component-hello-world3

Pipelines as Code configuration proposal

Pipelines as Code CI/test-pac-component-hello-world3-on-pull-request has failed.

StatusDurationName

✅ Succeeded
8 seconds
appstudio-init

✅ Succeeded
19 seconds
clone-repository

✅ Succeeded
9 seconds
appstudio-configure-build

❌ Failed
17 seconds
build-container

✅ Succeeded
7 seconds
show-summary

Pipelines as Code CI/test-pac-component-hello-world3-on-pull-request has failed.

StatusDurationName

✅ Succeeded
9 seconds
appstudio-init

✅ Succeeded
17 seconds
clone-repository

✅ Succeeded
9 seconds
appstudio-configure-build

❌ Failed
17 seconds
build-container

✅ Succeeded
8 seconds
show-summary


Add AuthenticationMixin to Vm

Today, the ConversionHost includes the AuthenticationMixin mixin to perform authentication check. The ConversionHost is associated to a resource: a Host or a Vm. The Host class also includes the AuthenticationMixin mixin. It seems logical that the Vm could also have authentications and that ConversionHost delegates authentication related code to its resource.
This would also allow other use cases for VM authentication, such as Ansible playbooks. If the VM class includes the AuthenticationMixin mixin, it allows us to define many purposes authentication. One of them would be transformation (or v2v) for VMs acting as conversion hosts. Another one could be ansible to store the machine credentials along with the managed object.

@miq-bot add-label enhancement, transformation
@miq-bot add-reviewer @djberg96
@miq-bot add-reviewer @agrare
@miq-bot add-reviewer @Fryguy

Model part of https://github.com/ManageIQ/manageiq/issues/19501


Expose domains & origins in bootstrap endpoint

Changes

Current dependencies on/for this PR:

main

PR #293   👈

This stack of pull requests is managed by Graphite.

Merge activity

Dec 23, 10:17 PM: @@NathanFlurry started a stack merge that includes this pull request via Graphite.


Cordova Build - unable to find the sax module

Build Error with Cordova Project
Error : BLD00401 :
Could not find module 'sax'.
Please Go to Tools --> Options --> Tools for Apache Cordova --> Cordova Tools --> Clear Cordova Cache
and try building again.

Error troubleshooting link:
https://msdn.microsoft.com/query/dev14.query?appId=Dev14IDEF1&l=EN-US&k=k(BLD401);k(TargetOS-8.1)&rd=true

I am working on this


[Slider] Problem in the Slider with Two Handles

In the slider with Two Handles, there is a problem:
On moving the first handles down to the "0" and after this moving the second handles, the fill slider does not work well.

The problem is also visible on the site:
http://foundation.zurb.com/sites/docs/slider.html#two-handles
P.S. Ciao & thank you all, for all the great work you do

Ah, bugger. Thanks for pointing this out, cant believe I missed this.


Test full FD teardown/dispose + setup/(re)initialize

Should be fail proof and tested, maybe in a separate Flutter test repo (along with performance testing there?).
Explore destroying local storage instead of clearing.

Following on main.data.dart is useless:
    ref.onDispose(() {
      for (final repository in _repoMap.values) {
        repository.dispose();
      }
    });

Wait until https://github.com/flutterdata/flutter_data/issues/93 ?

Fixed in v2


New release

We've been on 0.2.2 for a fairly long time I would like to be able to use:

bugfix for moving window to active workspace
option to lock numlock
fixing drag on fullscreen window
fix for https://github.com/vaxerski/Hyprland/issues/157
fix for https://github.com/vaxerski/Hyprland/issues/147
fixing the typo in https://github.com/vaxerski/Hyprland/commit/0f28d2ae5515c5f8f6f50cad743f049ce1fda584

"fairly long time"
sir its been one day

done


Minitest support

It took me a while but I think I finally have something worth discussing. This PR builds upon my proof of concept mentioned in #88, streamlines the code a little bit and adds tests.
Notable changes

Handling the records created from the examples run is identical between both integrations. I opted for creating a new class, ResultRecorder to move that code into so it can be shared. This makes the actual integrations a lot slimmer, which I think is very nice.
I need to hook into minitest in two very different ways. As such I cannot use a local outer variable as the rspec hooks do. So I created another attribute on the RSpec::OpenAPI module to collect the path_records. (A nice side-effect of the point mentioned above is that error_records has moved to the ResultRecorder class and is not needed as a global variable anymore.)

Unsolved issues

In contrast to my initial PoC I re-added the dependency on rspec in the .gemspec file. I had initially hoped that some kind of "soft dependency" would be possible, but there are a couple of issues with that. One is that rspec-openapi depends on and requires the rspec meta gem. rspec-rails on the other hand does not depend on that, so in many typical rails apps using rspec you will not find it in the gem bundle. I tried a couple of things but to no avail. If anyone has any ideas how one could remove the hard dependency, so minitest users will not have to install rspec, without any breaking changes for existing users, I would be thankful.
I tried to mirror the existing specs for the rspec integration as much as possible. And initially I was very pleasantly surprised that I was able to generate almost the same openapi files using minitest. But I was never able to get the exact same output, because with the way rspec-openapi works the output heavily depends on the order in which the tests are executed. This is a problem with minitest, as it orders tests randomly during execution. The only other option is to order them alphabetically, which sadly does not match the order in the rspec request specs either. I had to patch minitest and reorder the tests to get the exact same output, which is not ideal imho. It makes the current tests very brittle. OTOH I love that they prove that both integrations can produce the exact same output. So maybe it is OK.

Missing features
My goal was to produce something usable that can serve as a basis for discussion so there are a couple of features I intentionally did not implement. Most notably:

Per test-case metadata to override e.g. the description is not possible right now. Minitest has no concept of per test-case metadata, so this is rather hard to add. There are a couple of plugins for minitest that add similar functionality (e.g. tags), so it could be done, but as stated I intentionally left this out for now.
A custom description_builder will not work with minitest and I believe it never could because minitest has no concept of nested examples.
Using a Proc to construct the path will not currently work. This is actually not an intentional omission, but something I overlooked and only just noticed. I might still look into adding support for this.

I tried to mirror the existing specs for the rspec integration as much as possible. And initially I was very pleasantly surprised that I was able to generate almost the same openapi files using minitest. But I was never able to get the exact same output, because with the way rspec-openapi works the output heavily depends on the order in which the tests are executed. This is a problem with minitest, as it orders tests randomly during execution. The only other option is to order them alphabetically, which sadly does not match the order in the rspec request specs either. I had to patch minitest and reorder the tests to get the exact same output, which is not ideal imho. It makes the current tests very brittle. OTOH I love that they prove that both integrations can produce the exact same output. So maybe it is OK.

Judging from the failed checks, I still do not have a way to guarantee a stable execution order of tests :frowning_face:

Judging from the failed checks, I still do not have a way to guarantee a stable execution order of tests frowning_face

I made the ordering of tests explicit now, so it is 100% static. That should solve this issue.
Also, I added support for constructing the path dynamically using a Proc.


Ubuntu 16.04 compatibility fix

Hi all,
I had some trouble using this out of the box the other day on a fresh 16.04 customer install and for such a simple script this should be much easier to use. Two changes:

Use Python from the Path instead of enforcing the use of python3 as it is still widely used on 16.04 and there is nothing stopping it from working with python2 out of the box.

Added readme instructions for installing missing libraries and binaries to run the script.

Cheers

Hi @CalvinHartwell . Thank you for the PR can you please rebase?

I have concerns:

Ubuntu 18.04 comes with python3 installed, not python. So this "fixes" an older release but "breaks" the newer one.
You're adding instructions to install python 2 and several packages anyway, so what's the point of reverting? Why not instruct them to install python3 and python3 libs?

Something else you should be aware @CalvinHartwell is that this project was not meant to provide the released bundles. For example, from now and the next week the master head of this project will produce bundles for 1.11 kubernetes but the officially released cdk is with 1.10.
If you intent to use this project in the field we should create branches in a timely fashion.

Ubuntu 18.04 comes with python3 installed, not python. So this "fixes" an older release but "breaks" the newer one.
You're adding instructions to install python 2 and several packages anyway, so what's the point of reverting? Why not instruct them to install python3 and python3 libs?

Python3 is installed by default on 16.04, but just like RHEL6/7, it is not the default python release used by the OS. Usually this is because some OS utilities and binaries require the use of Python2.

Something else you should be aware @CalvinHartwell is that this project was not meant to provide the released bundles. For example, from now and the next week the master head of this project will produce bundles for 1.11 kubernetes but the officially released cdk is with 1.10.
If you intent to use this project in the field we should create branches in a timely fashion.

What do mean by this? Are you basically saying that the master branch should no longer be used for customer deployments and 1.11 is not supported yet? Do you want to us to deploy $currentversion-1 in the field instead of the most recent version? Please explain.

What do mean by this? Are you basically saying that the master branch should no longer be used for customer deployments and 1.11 is not supported yet? Do you want to us to deploy $currentversion-1 in the field instead of the most recent version? Please explain.

This project is used to produce bundles that will go through our CI process and if they pass all testing they get released to the charm store. Our release ends with placing charms & bundles on the charm store we do not release by patching this repository to build the latest bundles. This project was always an internal tool used in the late stages of our release process.
My opinion on what the field should do is to get the bundles from the store directly since this is where charms & bundles are released. Then write any pre and post-deploy scripts as spells. I know that conjure-up does not fit your needs so just call your scripts directly. Yet, if you code your deployments in a structured way (eg spells) we could have a common ground where field and engineers could collaborate. Ultimately we would want to get your pre/post deploy scripts regularly tested through our CI.
Let me understand something, you are using this project to produce the bundles you juju deploy. If conjure-up was working in headless mode (no user interface) and would just output the bundle.yaml (no deployment no post/pre deploy steps) would the field consider it as an alternative to this project?

Since this hasn't been updated or asked for in over 2 years, I think Konstantinos's comment that this is intended for internal use by our CI / build system stands, and so I'm closing this.  Feel free to re-open if there's still some need to use this outside of the CI / build system that I'm not aware of.


Build failure: gamescope

Steps To Reproduce
Steps to reproduce the behavior:
In my flake.nix:
{ ... }:

{
  programs.steam = {
    enable = true;
    gamescopeSession.enable = true;
    # remotePlay.openFirewall = true; # Open ports in the firewall for Steam Remote Play
    # dedicatedServer.openFirewall = true; # Open ports in the firewall for Source Dedicated Server
  };

  programs.gamescope.enable = true;
  # programs.gamescope.capSysNice = true;

  programs.gamemode.enable = true;
}

Build log
building '/nix/store/icz0i0znnzf5yx3vrjki8g1h056h8sdj-gamescope-3.14.2.drv'...
gamescope> Running phase: unpackPhase
gamescope> unpacking source archive /nix/store/9qjg2vpnnk4abkc5zasfz2c8pbpj2dqr-source
gamescope> source root is source
gamescope> Running phase: patchPhase
gamescope> applying patch /nix/store/6n6fp7n4yjhi7nrzq80jwhvxq5lf9hkf-use-pkgconfig.patch
gamescope> patching file meson.build
gamescope> applying patch /nix/store/fbijw6qf0b1h2frv275x36wa9vavasbx-shaders-path.patch
gamescope> patching file src/reshade_effect_manager.cpp
gamescope> substituteStream(): WARNING: '--replace' is deprecated, use --replace-{fail,warn,quiet}. (file 'src/reshade_effect_manager.cpp')
gamescope> Running phase: updateAutotoolsGnuConfigScriptsPhase
gamescope> Running phase: configurePhase
gamescope> mesonConfigurePhase flags: --prefix=/nix/store/ns708l1yam9d849fwd131c4prxl04jmk-gamescope-3.14.2 --libdir=/nix/store/ns708l1yam9d849fwd131c4prxl04jmk-gamescope-3.14.2/lib --libexecdir=/nix/store/ns708l1yam9d849fwd131c4prxl04jmk-gamescope-3.14.2/libexec --bindir=/nix/store/ns708l1yam9d849fwd131c4prxl04jmk-gamescope-3.14.2/bin --sbindir=/nix/store/ns708l1yam9d849fwd131c4prxl04jmk-gamescope-3.14.2/sbin --includedir=/nix/store/ns708l1yam9d849fwd131c4prxl04jmk-gamescope-3.14.2/include --mandir=/nix/store/ns708l1yam9d849fwd131c4prxl04jmk-gamescope-3.14.2/share/man --infodir=/nix/store/ns708l1yam9d849fwd131c4prxl04jmk-gamescope-3.14.2/share/info --localedir=/nix/store/ns708l1yam9d849fwd131c4prxl04jmk-gamescope-3.14.2/share/locale -Dauto_features=enabled -Dwrap_mode=nodownload --buildtype=plain -Denable_gamescope=true -Denable_gamescope_wsi_layer=false
gamescope> The Meson build system
gamescope> Version: 1.3.1
gamescope> Source dir: /build/source
gamescope> Build dir: /build/source/build
gamescope> Build type: native build
gamescope> Project name: gamescope
gamescope> Project version: undefined
gamescope> C compiler for the host machine: gcc (gcc 13.2.0 "gcc (GCC) 13.2.0")
gamescope> C linker for the host machine: gcc ld.bfd 2.40
gamescope> C++ compiler for the host machine: g++ (gcc 13.2.0 "g++ (GCC) 13.2.0")
gamescope> C++ linker for the host machine: g++ ld.bfd 2.40
gamescope> Host machine cpu family: x86_64
gamescope> Host machine cpu: x86_64
gamescope> Compiler for C++ supports arguments -Wno-unused-parameter: YES
gamescope> Compiler for C++ supports arguments -Wno-missing-field-initializers: YES
gamescope> Compiler for C++ supports arguments -Wno-c99-designator: NO
gamescope> Compiler for C++ supports arguments -Wno-invalid-offsetof: YES
gamescope> Compiler for C++ supports arguments -Wno-unused-const-variable: YES
gamescope> Compiler for C++ supports arguments -Wno-volatile: YES
gamescope> Compiler for C++ supports arguments -Wno-deprecated-volatile: NO
gamescope> Compiler for C++ supports arguments -Wno-ignored-qualifiers: YES
gamescope> Compiler for C++ supports arguments -Wno-missing-braces: YES
gamescope> Compiler for C++ supports arguments -ffast-math: YES
gamescope> Found pkg-config: YES (/nix/store/knxv5h4hsh86c649rabd6dqfd97kwp5d-pkg-config-wrapper-0.29.2/bin/pkg-config) 0.29.2
gamescope> Run-time dependency libpipewire-0.3 found: YES 1.0.3
gamescope> Library rt found: YES
gamescope> Run-time dependency hwdata found: YES 0.378
gamescope> Run-time dependency x11 found: YES 1.8.7
gamescope> Run-time dependency wayland-client found: YES 1.22.0
gamescope> Run-time dependency vulkan found: YES 1.3.275
gamescope> Run-time dependency openvr found: YES 2.2.3
gamescope> Check usable header "vulkan/vulkan.h" with dependency vulkan: YES
gamescope> Build-time dependency wayland-scanner found: YES 1.22.0
gamescope> Program /nix/store/2kncw17a1k3jsni4n45qyz1xvjx94nc1-wayland-1.22.0-bin/bin/wayland-scanner found: YES (/nix/store/2kncw17a1k3jsni4n45qyz1xvjx94nc1-wayland-1.22.0-bin/bin/wayland-scanner)
gamescope> Run-time dependency wayland-protocols found: YES 1.33
gamescope> Run-time dependency xdamage found: YES 1.1.6
gamescope> Run-time dependency xcomposite found: YES 0.4.6
gamescope> Run-time dependency xcursor found: YES 1.2.1
gamescope> Run-time dependency xrender found: YES 0.9.11
gamescope> Run-time dependency xext found: YES 1.3.5
gamescope> Run-time dependency xfixes found: YES 6.0.1
gamescope> Run-time dependency xxf86vm found: YES 1.1.5
gamescope> Run-time dependency xtst found: YES 1.2.4
gamescope> Run-time dependency xres found: YES 1.2.2
gamescope> Run-time dependency xmu found: YES 1.1.4
gamescope> Run-time dependency xi found: YES 1.8.1
gamescope> Run-time dependency libdrm found: YES 2.4.120
gamescope> Run-time dependency wayland-server found: YES 1.22.0
gamescope> Dependency wayland-protocols found: YES 1.33 (cached)
gamescope> Run-time dependency xkbcommon found: YES 1.5.0
gamescope> Run-time dependency threads found: YES
gamescope> Run-time dependency libcap found: YES 2.69
gamescope> Did not find CMake 'cmake'
gamescope> Found CMake: NO
gamescope> Run-time dependency epoll-shim found: NO (tried pkgconfig and cmake)
gamescope> Run-time dependency glm found: YES <IP_ADDRESS>
gamescope> Run-time dependency sdl2 found: YES 2.28.5
gamescope> Run-time dependency stb found: YES 1
gamescope> Run-time dependency libavif found: YES 1.0.3
gamescope> Dependency wlroots found: NO found 0.18.0-dev but need: '< 0.18.0' ; matched: '>= 0.17.0'
gamescope> Run-time dependency wlroots found: NO (tried pkgconfig and cmake)
gamescope> Looking for a fallback subproject for the dependency wlroots
gamescope> Executing subproject wlroots
gamescope> wlroots| Project name: wlroots
gamescope> wlroots| Project version: 0.17.0
gamescope> wlroots| C compiler for the host machine: gcc (gcc 13.2.0 "gcc (GCC) 13.2.0")
gamescope> wlroots| C linker for the host machine: gcc ld.bfd 2.40
gamescope> wlroots| Compiler for C supports arguments -Wundef: YES
gamescope> wlroots| Compiler for C supports arguments -Wlogical-op: YES
gamescope> wlroots| Compiler for C supports arguments -Wmissing-include-dirs: YES
gamescope> wlroots| Compiler for C supports arguments -Wold-style-definition: YES
gamescope> wlroots| Compiler for C supports arguments -Wpointer-arith: YES
gamescope> wlroots| Compiler for C supports arguments -Winit-self: YES
gamescope> wlroots| Compiler for C supports arguments -Wstrict-prototypes: YES
gamescope> wlroots| Compiler for C supports arguments -Wimplicit-fallthrough=2: YES
gamescope> wlroots| Compiler for C supports arguments -Wendif-labels: YES
gamescope> wlroots| Compiler for C supports arguments -Wstrict-aliasing=2: YES
gamescope> wlroots| Compiler for C supports arguments -Woverflow: YES
gamescope> wlroots| Compiler for C supports arguments -Wmissing-prototypes: YES
gamescope> wlroots| Compiler for C supports arguments -Walloca: YES
gamescope> wlroots| Compiler for C supports arguments -Wno-missing-braces: YES
gamescope> wlroots| Compiler for C supports arguments -Wno-missing-field-initializers: YES
gamescope> wlroots| Compiler for C supports arguments -Wno-unused-parameter: YES
gamescope> wlroots| Compiler for C supports arguments -fmacro-prefix-map=/prefix/to/hide=: YES
gamescope> wlroots| Dependency wayland-server found: YES 1.22.0 (cached)
gamescope> wlroots| Dependency libdrm found: YES 2.4.120 (cached)
gamescope> wlroots| Dependency xkbcommon found: YES 1.5.0 (cached)
gamescope> wlroots| Run-time dependency pixman-1 found: YES 0.43.2
gamescope> wlroots| Library m found: YES
gamescope> wlroots| Library rt found: YES
gamescope> wlroots| Dependency wayland-protocols found: YES 1.33 (cached)
gamescope> wlroots| Dependency wayland-scanner found: YES 1.22.0 (cached)
gamescope> wlroots| Program /nix/store/2kncw17a1k3jsni4n45qyz1xvjx94nc1-wayland-1.22.0-bin/bin/wayland-scanner found: YES (/nix/store/2kncw17a1k3jsni4n45qyz1xvjx94nc1-wayland-1.22.0-bin/bin/wayland-scanner)
gamescope> wlroots| Has header "linux/dma-buf.h" : YES
gamescope> wlroots| Dependency pixman-1 found: YES 0.43.2 (cached)
gamescope> wlroots| Run-time dependency libudev found: YES 255
gamescope> wlroots| Run-time dependency libseat found: NO (tried pkgconfig and cmake)
gamescope> wlroots| Looking for a fallback subproject for the dependency libseat
gamescope> wlroots| Message: Required for session support.
gamescope> subprojects/wlroots/backend/session/meson.build:3:10: ERROR: Neither a subproject directory nor a seatd.wrap file was found.
gamescope> A full log can be found at /build/source/build/meson-logs/meson-log.txt

Additional context
Add any other context about the problem here.
Notify maintainers

cc @nrdxp @PedroHLC @Scrumplex @zhaofengli @K900
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.7.4-zen1, NixOS, 24.05 (Uakari), 24.05.20240215.a4d4fe8`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Add a :+1: reaction to issues you find important.

gamescope> Dependency wlroots found: NO found 0.18.0-dev but need: '< 0.18.0' ; matched: '>= 0.17.0'

Do you have an overlay for wlroots or something?

find out what happened. I'm using https://github.com/nix-community/nixpkgs-wayland , sorry for bothering.
solved by
programs.gamescope = {
    enable = true;
    package = pkgs.gamescope.override { wlroots = pkgs.wlroots_0_17; };
  };

Is it good to replace https://github.com/NixOS/nixpkgs/blob/71b65d1bc48ff7ace2f31ab162370255bb393c6e/pkgs/applications/window-managers/gamescope/default.nix#L25 with wlroots_0_17 ?

Generally I think nixpkgs-wayland should not be overriding wlroots in nixpkgs itself.


Fixed bug for Html Editor(summernote)

Hi @vmtco,
I think we have this fixed in master, but not released yet. Could you please test with the version in master and see if the issue persist. You can grab the dist file from this gist: https://gist.github.com/Arkni/495730a47b52b570b150d4375bfbb7c7
Thanks!

@Arkni : This fix is not contained in your gist. I also tested and it does not work. With the bugfix by @vmtco, everything works fine. Please merge and release.

Hi @markussc,
Thanks for the feedback. I'll try to analyse the issue more and will offer feedback as soon as I get some free time.

@Arkni
Ouch, something that could already be fixed for years, but isn't. I get it, free time is hard for me too. 😅
It would fix it for Trumbowyg which we just tested, and also CKEditor, and probably a lot more alternative WYSIWIG editors.

Thanks (in advance)! 😇

It would be very nice if this could be published in a new release that will be on npm so it will be fixed for everyone. Thanks in advance.

@KoalaBear84 npm i<EMAIL_ADDRESS>


Remove extra CATEGORIES in feed and add test for multiple categories.…

… Closes #63.

Thank you for the fix 👍

This has been released as part of version 1.9.1 now available on PyPI


Update deps

(Note: This is based on the other "add tests" PR)

Upgraded several of the dev dependencies in package.json to their latest versions
Updated .babelrc to work with babel v6
Removed 'use strict' per latest eslint defaults

Thank you very much!


test1--9-main

Please pull this in!

 Quality gate: Failed
26 Issues

 24 Code issues
 2 Anti-patterns

Details

 Quality gate: Failed
26 Issues

 24 Code issues
 2 Anti-patterns

Details

 Quality gate: Failed
26 Issues

 24 Code issues
 2 Anti-patterns

Details


Real Time Processing

Hi,
I would like to know if it is possible to use this library during a real time process from a microphone input
Thank you

yes ... if you have a stable pyaudio like library