text:
Can't use myzod

Describe the change
Hello,
In the documentation, there is a page about data validation that says it's possible to use myzod. However, parsing params (and body) does not works because of this error:
Cannot read properties of undefined (reading 'Symbol(shapeKeys)')

The reproduction: https://github.com/barbapapazes/myzod-h3
You can start the open with node server.mjs and open you browser localhost:3000 and check the terminal where you launch node. You will see this error, similar to above:
H3Error: Cannot read properties of undefined (reading 'Symbol(shapeKeys)')
    at createError (file:///home/esteban/dev/r/myzod-h3/node_modules/.pnpm/h3@1.11.1/node_modules/h3/dist/index.mjs:79:15)
    at createValidationError (file:///home/esteban/dev/r/myzod-h3/node_modules/.pnpm/h3@1.11.1/node_modules/h3/dist/index.mjs:245:9)
    at validateData (file:///home/esteban/dev/r/myzod-h3/node_modules/.pnpm/h3@1.11.1/node_modules/h3/dist/index.mjs:241:11)
    at getValidatedRouterParams (file:///home/esteban/dev/r/myzod-h3/node_modules/.pnpm/h3@1.11.1/node_modules/h3/dist/index.mjs:272:10)
    at Object.handler (file:///home/esteban/dev/r/myzod-h3/src/app.mjs:21:28)
    at Object.handler (file:///home/esteban/dev/r/myzod-h3/node_modules/.pnpm/h3@1.11.1/node_modules/h3/dist/index.mjs:2196:34)
    at Object.handler (file:///home/esteban/dev/r/myzod-h3/node_modules/.pnpm/h3@1.11.1/node_modules/h3/dist/index.mjs:1962:31)
    at Server.toNodeHandle (file:///home/esteban/dev/r/myzod-h3/node_modules/.pnpm/h3@1.11.1/node_modules/h3/dist/index.mjs:2249:17)
    at Server.emit (node:events:518:28)
    at parserOnIncoming (node:_http_server:1137:12) {
  cause: {
    status: 400,
    statusMessage: 'Validation Error',
    message: "Cannot read properties of undefined (reading 'Symbol(shapeKeys)')",
    data: TypeError: Cannot read properties of undefined (reading 'Symbol(shapeKeys)')
        at parse (/home/esteban/dev/r/myzod-h3/node_modules/.pnpm/myzod@1.11.0/node_modules/myzod/libs/types.js:548:26)
        at validateData (file:///home/esteban/dev/r/myzod-h3/node_modules/.pnpm/h3@1.11.1/node_modules/h3/dist/index.mjs:232:23)
        at getValidatedRouterParams (file:///home/esteban/dev/r/myzod-h3/node_modules/.pnpm/h3@1.11.1/node_modules/h3/dist/index.mjs:272:10)
        at Object.handler (file:///home/esteban/dev/r/myzod-h3/src/app.mjs:21:28)
        at Object.handler (file:///home/esteban/dev/r/myzod-h3/node_modules/.pnpm/h3@1.11.1/node_modules/h3/dist/index.mjs:2196:34)
        at Object.handler (file:///home/esteban/dev/r/myzod-h3/node_modules/.pnpm/h3@1.11.1/node_modules/h3/dist/index.mjs:1962:31)
        at Server.toNodeHandle (file:///home/esteban/dev/r/myzod-h3/node_modules/.pnpm/h3@1.11.1/node_modules/h3/dist/index.mjs:2249:17)
        at Server.emit (node:events:518:28)
        at parserOnIncoming (node:_http_server:1137:12)
        at HTTPParser.parserOnHeadersComplete (node:_http_common:119:17)
  },
  statusCode: 400,
  fatal: false,
  unhandled: false,
  statusMessage: 'Validation Error',
  data: TypeError: Cannot read properties of undefined (reading 'Symbol(shapeKeys)')
      at parse (/home/esteban/dev/r/myzod-h3/node_modules/.pnpm/myzod@1.11.0/node_modules/myzod/libs/types.js:548:26)
      at validateData (file:///home/esteban/dev/r/myzod-h3/node_modules/.pnpm/h3@1.11.1/node_modules/h3/dist/index.mjs:232:23)
      at getValidatedRouterParams (file:///home/esteban/dev/r/myzod-h3/node_modules/.pnpm/h3@1.11.1/node_modules/h3/dist/index.mjs:272:10)
      at Object.handler (file:///home/esteban/dev/r/myzod-h3/src/app.mjs:21:28)
      at Object.handler (file:///home/esteban/dev/r/myzod-h3/node_modules/.pnpm/h3@1.11.1/node_modules/h3/dist/index.mjs:2196:34)
      at Object.handler (file:///home/esteban/dev/r/myzod-h3/node_modules/.pnpm/h3@1.11.1/node_modules/h3/dist/index.mjs:1962:31)
      at Server.toNodeHandle (file:///home/esteban/dev/r/myzod-h3/node_modules/.pnpm/h3@1.11.1/node_modules/h3/dist/index.mjs:2249:17)
      at Server.emit (node:events:518:28)
      at parserOnIncoming (node:_http_server:1137:12)
      at HTTPParser.parserOnHeadersComplete (node:_http_common:119:17)
}

URLs
https://h3.unjs.io/examples/validate-data#utilities-for-validation
Additional information

[ ] Would you be willing to help?

Works as expected if you pass data as explicit argument
Works
const params = await getValidatedRouterParams(event, (data) => validator.parse(data))

Breaks
const params = await getValidatedRouterParams(event, validator.parse)

Works as expected if you pass data as explicit argument
Works
const params = await getValidatedRouterParams(event, (data) => validator.parse(data))

Breaks
const params = await getValidatedRouterParams(event, validator.parse)

https://github.com/Barbapapazes/myzod-h3/pull/2

Interesting 🤔
Do you know why? And we could update the docs to be more explicite about that case.

source: gharchive/issue

authors: Barbapapazes manniL

license: MIT

license_type: permissive

license_source: github-api


text:
Support for vueuse breakpoints

Describe the feature
Support auto import vueuse breakpoints like breakpointsTailwind.
In useBreakpoints API, a breakpoint config is required. Auto import of some commonly used breakpoints would be very convenient.
Additional information

[X] Would you be willing to help implement this feature?

https://github.com/unjs/unimport/pull/328#issuecomment-1952297545

authors: antfu zekunjin

repo: unjs/unimport


text:
Compatibility issues with new SvelteKit version and vite config

SvelteKit no longer has the vite plugin inside svelte.config.js. It now is just inside vite.config.js. This change makes the unocss docs outdated.
Besides that, there is also an issue where if the SvelteKit vite plugin runs BEFORE the unocss plugin, unocss causes SvelteKit to not work. Not sure why though.
You can check the new SvelteKit project structure out by quickly initializing a skeleton project using npm init svelte@next. Then install unocss inside the vite.config.js. Depending on the order of vite plugins as I described above, SvelteKit may not work.

@UltraCakeBakery we need to update the example, PR welcome

@UltraCakeBakery I'll take a look and check what's happening...

@UltraCakeBakery I have SvelteKit plugin before and after UnoCss running in dev and build + preview, what's the error in your side?

build + preview with SvelteKit next.367 and static adapter next.35 (SvelteKit plugin after UnoCSS plugin)
https://streamable.com/2e0k6r ()

@UltraCakeBakery I have SvelteKit plugin before and after UnoCss running in dev and build + preview, what's the error in your side?

There is no error. SvelteKit simply isn't responding as if it is endlessly processing something. I'll put together a reproduction tomorrow.

@UltraCakeBakery https://stackblitz.com/edit/sveltejs-kit-template-default-wnmf33

authors: UltraCakeBakery userquin

repo: unocss/unocss


text:
'unocss' is not recognized as an internal or external command, operable program or batch file

UnoCSS version
latest
Describe the bug
Following the guide in https://unocss.dev/integrations/cli, but turns out it's not working.

Reproduction
This is a minimal repo that's created by create-next-app with uno.config.ts setup. Currently at the stage to generate uno.css by CLI but failed to do so.
https://github.com/xsjcTony/PokeTool
System Info
Windows 11, Chrome 121, Next.js 14

Validations

[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Turns out the doc is incorrect, at least for pnpm.
If only unocss is installed, then the binary file won't be included in the .bin folder:

After installing @unocss/cli explicitly:

@antfu Please confirm whether the above is the expected behaviour. If yes, then we need to update the doc correspondingly.

It seems we don't have bin field in unocss. And we are not deps in @unocss/cli by unocss probably because the deps size - I guess it's better to keep it as-is, and fix the docs. Thanks!

authors: antfu xsjcTony


text:
feat: use templated parent border brush on combo box's elevated view

GitHub Issue: closes #701
PR Type
What kind of change does this PR introduce?

Feature

Description
Instead of forcing the default combo box border brush onto the elevated view, we instead set it as default and let the templated parent set its own border brush.
PR Checklist
Please check if your PR fulfills the following requirements:

Commits must be following the Conventional Commits specification
[x] Tested UWP
[x] Tested iOS
[x] Tested Android
[x] Tested WASM
[x] Tested MacOS
[x] Contains No breaking changes

If the pull request contains breaking changes, commit message must contain a detailed description of the action to take for the consumer of this library. As explained by the Conventional Commits specification

Other information

Internal Issue (If applicable):

Thanks for your contribution!

source: gharchive/pull-request


text:
Contact info

This PR gives us a better way to manage contact info displayed in the app. Fixes #63

ping @ldko, @vphill, @jason-ellis, @jthomale

:+1:

:+1:

authors: jason-ellis ldko somexpert

repo: unt-libraries/django-nomination

license_source: bigquery


text:
Scrollbar nicht immer anzeigen

Das padding auf dem body machte die Seite immer etwas größer als den viewport, indem das padding auf #wrapper gesetzt wird ist dies nicht mehr der Fall.

Guter Vorschlag, wollte ich auch schon mindestens 5x angegangen haben 👍

authors: ZusorCode heinleit

repo: unverantwortli-ch/page


text:
Test cases should have timeouts

Is your feature request related to a problem? Please describe.
Test cases don't fail but run nearly forever.

Describe the solution you'd like
Test cases should have timeouts or a maximum number of retries before they fail.

in case of no network beeing provided, tests time out already
need to wrap chain access with timeout functionality when "successfully" communicating so that waiting for peer response does not cause these extensive waiting times

@this-kramer
Has this already been fixed by the timeout in the networkDescription/connectionProfile?

I think the timeouts in the connection profile do not affect this issue, since they were present when this behavior occured.

authors: NikoBergemann this-kramer


text:
use gcp in trace command instead of aws

Description of your changes

Fixes #
I have: updated the example trace command to refer to gcp instead of aws

[x] Read and followed Upbound's contribution process.
[ ] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR, as appropriate.

How has this code been tested
Manually previewed readme markdown.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: Upbound-CLA trevorackerman

repo: upbound/platform-ref-gcp


text:
resources and resource files can conflict with go-lang reserved keywords

What happened?

Hi,
There a few problems that occur if an imported resource name or field in a resource overlaps with a go-lang reserved keyword.
For example, "range".
This affects the typewriter generated files that are produced as well, and filed here https://github.com/muvaf/typewriter/pull/11
However, several other generated files done by upjet hit this issue in perhaps a more architecturally challenging way.
15:16:19 [ .. ] go generate linux_amd64
panic: cannot run goimports for internal folder: ./controller/ipv6_range/range/zz_controller.go:7:9: expected 'IDENT', found 'range'
./controller/ipv6_range/range/zz_controller.go:9:1: expected ';', found 'import'
: exit status 2

And this is because the package name becomes a reserved keyword in this file
    1 /*
    2 Copyright 2022 Upbound Inc.
    3 */
    4
    5 // Code generated by upjet. DO NOT EDIT.
    6
    7 package range

How can we reproduce it?

The field in question is here:
https://registry.terraform.io/providers/linode/linode/latest/docs/resources/ipv6_range#range
I can provide a provider repo with this error if that is helpful.
Thank you!
Please let me know how I can help resolve this issue.

Hi @srust,
Thank you for reporting this issue. It would be helpful if you could provide the provider repo as you suggested so that we could work together on a workaround.

What you could do as a workaround is to use the resource configuration API to override the generated Kind name and, if needed, the short group name. You can override the generated Kind name with config.Resource.Kind and the short group name with config.Resource.ShortGroup .

Hi @ulucinar thanks!
Indeed the config.Resources.Kind is able to workaround this issue.
The provider we are developing is at https://github.com/linode/provider-linode
All of the available terraform resources are included in that provider now, except for the ipv6_range resource.
I have a branch that includes support for ipv6_range but requires the Kind override in order to generate properly.
This is available at https://github.com/srust/provider-linode/tree/ipv6_range
If the config/ipv6range/config.go is edited to remove the r.Kind specification, then syntax errors occur:
diff --git a/config/ipv6range/config.go b/config/ipv6range/config.go
index f16a5d0..ca62cb0 100644
--- a/config/ipv6range/config.go
+++ b/config/ipv6range/config.go
@@ -7,6 +7,5 @@ func Configure(p *config.Provider) {
        p.AddResourceConfigurator("linode_ipv6_range", func(r *config.Resource) {
                // We need to override the default group that upjet generated for
                // this resource, which would be "linode"
-               r.Kind = "IPv6range"
        })
 }

$ make generate
12:53:31 [ .. ] generating provider schema for linode/linode 1.29.4
12:53:33 [ OK ] generating provider schema for linode/linode 1.29.4
12:53:33 [ .. ] verify go modules dependencies have expected content
all modules verified
12:53:35 [ OK ] go modules dependencies verified
12:53:36 [ .. ] go generate linux_amd64
panic: cannot run goimports for internal folder: ./controller/zz_setup.go:16:1: expected 'STRING', found 'range'
./controller/zz_setup.go:47:2: expected 'STRING', found 'for'
./controller/zz_setup.go:78:3: expected 'STRING', found 'if'
./controller/zz_setup.go:79:4: expected 'STRING', found 'return'
./controller/zz_setup.go:82:2: expected 'STRING', found 'return'
./controller/zz_setup.go:83:3: expected ')', found 'EOF'
./controller/ipv6/range/zz_controller.go:7:9: expected 'IDENT', found 'range'
./controller/ipv6/range/zz_controller.go:9:1: expected ';', found 'import'
: exit status 2

goroutine 1 [running]:
github.com/upbound/upjet/pkg/pipeline.Run(0xc000505800, {0xc000448940, 0x34})
	/Users/srust/go/pkg/mod/github.com/upbound/upjet@v0.8.0-rc.0.0.20221115075453-606a1db65fa2/pkg/pipeline/run.go:126 +0xae5
main.main()
	/Users/srust/go/src/github.com/srust/provider-linode/cmd/generator/main.go:26 +0x74
exit status 2

Thanks!

Thank you @srust for the full context. Because you've already opened an issue in the upstream dependency, I would suggest closing this one. My understanding is that the affected Terraform resources are the ones with a Go reserved keyword suffix. If an upstream fix is introduced, then we can try consuming it in upjet. What do you think?

I am fine closing this. The workaround is to be honest sufficient for our use-case. Perhaps there is some documentation that should be updated to show the config.Resource.Kind workaround, to help some new users. It did take a bit of digging to find the generated code and what was causing the compile failure.

authors: srust ulucinar

repo: upbound/upjet


text:
chore: Plugin "file" allows to use file pattern in the file/files key

Fix #1453
This pullrequest allows to use common file path pattern with the plugin "file"
name: Test file resource without scm

sources:
  adoptersWithFilePattern:
    name: "Get content from each file(s) matching pattern ADOPTE??.md"
    kind: file
    spec:
      file: ADOPTE??.md

Test
To test this pull request, you can run the following commands:
cd pkg/plugins/utils/
go test
go build -o bin/updatecli .
./bin/updatecli diff --config e2e/updatecli.d/success.d/file/noscm.yaml --debug

Additional Information
Tradeoff
Instead of reading a specific file, the change introduce in this pullrequest will try to locate ALL files matching pattern which obviously has performance consequence...
I could think of two options to mitigate this:

Using a flag to enable/disable this behavior such as

sources:
  adoptersWithFilePattern:
    name: "Get content from each file(s) matching pattern ADOPTE??.md"
    kind: file
    spec:
      file: ADOPTE??.md
      filepattern: true

But I find this approach a bit cumbersome

Using a different key such as

sources:
  adoptersWithFilePattern:
    name: "Get content from each file(s) matching pattern ADOPTE??.md"
    kind: file
    spec:
      filepattern: ADOPTE??.md
      filepattern: true

But this would imply more code to write and maintain as I'll need to handle the different combination of file,files,filepath, filespath
I don't think the performance impact is that critical but I am open for suggestion
Potential improvement
Implement similar pullrquest for

[ ] xml
[ ] json
[ ] toml
[ ] yaml
[ ] csv

While the idea remain the same, the broken e2e highlight that the current implementation is wrong. It doesn't handle scm

I updated the e2e tests to cover the additional scenarios

repo: updatecli/updatecli


text:
Rename default branch from master to main

Repo owner can do this easily in GitHub.  More difficult for a contributor.

Done. main is the default branch. I deleted master as well. Thanks @johnwalicki

authors: johnwalicki upkarlidder

repo: upkarlidder/coffee-donut-instructions


text:
🛑 Main Website is down

In 790cc76, Main Website (https://www2.upmin.edu.ph) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Main Website is back up in 1ed006d after 4 hours, 11 minutes.

repo: upmin-dev/UP-time


text:
Add doc linking to main contributor guide

Add document linking to the contributor guide in the main 3box repo.

Closed since it was accidentally targeting master rather than develop.

@christianlundkvist Next time you can just press edit and change the base branch :)

authors: christianlundkvist oed


text:
Add aria-label for accessibility

Since there is no visible text displayed along with the Button icon, adding aria-label will be useful for voiceover users.

thank you @itssiva

authors: ademilter itssiva

repo: upstash/feedback


text:
Update to newest TUF version

From @awwad on December 1, 2016 21:18
The depended-on fork of TUF (awwad/tuf@pinning) is slightly out of date. The TAP 4 modifications and a few other minor tweaks to TUF that Uptane depends on need to be merged into theupdateframework/tuf, and Uptane needs to switch to using TUF proper rather than a fork of TUF.
Copied from original issue: awwad/uptane#16

See also #23

Closed: replaced by more detailed issue #23.

repo: uptane/uptane

license: mit


text:
Use a core flag parser other than stdlib flag to unlock wider range of arg types

tl;dr - By switching away from stdlib flag, we will be able to support a wider range of capabilities with significantly less workaround code.
Much of the code around here is arguably working around stdlib flag, for example:

concept of commands

nesting of commands
commands with aliases

persistent flags (in progress)
flags with aliases
flags of types not already supported in stdlib (via FlagSet.Var)

slice-specific (de)serialization hacks
other inconsistently-implemented (de)serialization hacks

probably other stuff!

By building on top of stdlib flag, we are limited to two categories of string arguments:

flags

must start with -
may accept zero or one argument

non-flag string literals

must not start with -
no additional help from stdlib flag 🤷🏼

There are many other command line argument parsers available in the Go third-party package ecosystem such as:

pflag, a lower-level library that provides a compatibility layer with stdlib flag

typically seen via this fork which isn't being actively maintained

cobra, a holistic command and flag building solution that encourages imperative construction of command contexts (depends on pflag)
kong, a holistic command and flag building solution with strong support for deriving applications from nested struct variables
argparse, an imperative solution which aims to provide functionality like the Python stdlib argparse

(https://github.com/urfave/cli/issues/833#issuecomment-1312834335)

flags: must start with -

This is reasonable imo, I haven't seen any use for not starting (non-argument) flags without -. It also majorly simplifies parsing.

flags: must start with -

This is reasonable imo, I haven't seen any use for not starting (non-argument) flags without -. It also majorly simplifies parsing.

@jtagcat it's a unix-y-centric way of working, imho. For example, in Windows there's strong precedent for / as prefix and : as assignment like /{flag}:{value}, although this also conflicts with the idea of "compound short flags" 🤷🏼  I'd like to provide a flexible way to allow for different argument styles if possible, e.g. how argparse does it.

Ok, fair point.
I'd say multiple prefixes at once gets unreasonably complex. Yet swapping out (not adding to) the prefix and/or the non-space delimiter (=) is doable. Multiple parse calls with different delimiters gets you any result you could want.
For arguments without a key (eg. @file.txt), the caller (or a library wrapping harg) can just do a for range against (parsed) args with strings.HasPrefix() tailored to the use-case.
Performance of multiple parses isn't an issue. First, arguments are only parsed once (on app startup). With modern processors, multiple calls may even be more performant vs a messy monolithic do-all parser.
But I'd not touch the topic right now at all. A bad standard is better than 5 standards. In my opinion, the spec I have in FORMAT.md is fairly good, well-known, and used. Even (new) Microsoft CLI utilities use GNU-like arguments.
Everone is free to fork (and wrap the library or whole cli binary) for their own niche. I want to make the codebase maintainable (and workable) for as many as possible, including myself. One niche use-case just isn't worth it.
I want to keep it as simple as possible. There isn't anything we are removing compared to stdlib flags. Right now, getting v3 released is the priority.

@jtagcat I appreciate the points you're making.
I'd love to see what an integration of harg for the purpose of addressing this issue looks like, if you're up for doing that work.
I'm personally interested in exploring this approach, if only to better understand how the urfave/cli layer can change.

@meatballhat @jtagcat Both of you make good points. I think as software devs we'd like to make software perfect - covers all use cases, very performant, infintely extensible and so on. While a complete new parser is good, we need to see how much we can stretch stdlib flag to the max to cover most of the use cases. We cannot satisfy every user's use cases so its better to list what features beyond what urfave/cli/v2 offers do we want to achieve.

@dearchap Are you suggesting that this issue is not worth pursuing (yet)? 😅 imho the workarounds in place to support nested commands and compound short flags are indications that we've already gone past the point of stretching stdlib flag to the max. Or do I misunderstand what you mean? ❤

@meatballhat What are the most requested features of this library ?

Global/Persistent flags
Help consistency(and with being able to do help without required flags)

if we have those two knocked out, rest of the features are icing on the cake no ?

Requesting for comments, especially about the AlsoBool feature: https://github.com/jtagcat/harg/blob/7c7228774ec1fd7d593c5e24f82a2af1827eb06f/FORMAT.md#requesting-for-comments

update: https://github.com/jtagcat/harg is tested and ready to integrate
@dearchap @meatballhat requesting review, if you have the time

@jtagcat imho https://github.com/jtagcat/harg is lovely as heck and I would very much like to see what an integration with urfave/cli/v3 looks like 😁 Is this work you're planning to do soon?

Soon, but not soon. I have half a workday today, then maybe next Sunday, then longer periods starting around 18. dec.
Honestly, it plays such a major role in the cli package, a complete rewrite (creatively egoistically named hcli) for v3 might be doable.
What components are there?

Flags wrapper:

Help prompt
Shell completions [^notv3]
Default values

In Flag, replace Required bool with Action, renamed to Condition. It is trivial to write common implementations with generic functions. The library can provide commonly used ones, such as NotDefault (must be set by user, --foo="" is valid) and NotEmpty. In most cases, omitted or looking like cli.StringFlag{Name: "foo", Condition: cli.NotEmpty}.
Ideas for changes I've had so far. I've asked around for feedback, and clarifying what Required did come up.

Validation (after type conversion)
Supporting yaml with nested flag definition structure and/or exposing setting flags in context [^notv3]

Context

Signals [^notv3]

Make it clear on how interrupts are expected to be handled

Exit codes [^notv3]

Documenting and handling exit codes: Exit code caller should reference an already-defined code, similar to calling up a flag, not just 'exit 1'. [^notv3]

Commands

Before/After
Subcommands

Flag-dependant subcommands: Quick example: $ app' → ls $(pwd) $ app →cd ` [^

It should also include everything in the v3 milestone. Anything I missed? The only part I would expect to get stuck is shell completions. Though, it is not critical for a v3 beta.
[^notv3]: Not needed for a functional beta release. No changes are necessary for adding it without breaking changes.

@jtagcat do I understand correctly that you are recommending against integrating jtagcat/harg directly with this library, but instead to make a jtagcat/hcli project that uses it, and then use jtagcat/hcli in this library?

@jtagcat could you provide some examples of how users would use the harg library ? Maybe a definition for a int flag and a float slice . Thanks

@jtagcat do I understand correctly that you are recommending against integrating jtagcat/harg directly with this library, but instead to make a jtagcat/hcli project that uses it, and then use jtagcat/hcli in this library?

I meant hcli = urfave/cli@v3, maybe.

@jtagcat could you provide some examples of how users would use the harg library ? Maybe a definition for a int flag and a float slice . Thanks

One way would be to do as it is now: Define flags (and aliases, etc), and then retrieve by string. Just the underlining library differs. I would expect a flag to be available for all subcommands unless explicitly marked as local.
I don't know if it is ergonomically possible to type the lookup string.

What I came up with atm:

One thing maybe needing explaining is Source. It defines the priority (opt overrides env, or other way around).
Value-typing is still available:
var (
  flagFoo = "foo"
)

_ = hcli.Command{
	Flags: []hcli.Flag{
		hcli.StringFlag{Options: []string{flagFoo, "f"}},
	}
	Action: ... {
		ctx.SlString(flagFoo)
	}
	...
}

This provides completion and validation in the IDE, and ctrl-clicking (jump to definition, or show all uses).

I have a chicken and egg problem. It originates from boolean flags not consuming the next argument, thus options in general maybe consuming the next argument, what is a problem when determining whether a subcommand is a value for an option, or a subcommand.
One could expect all of the following to work (using only long options for sake of simplicity):
$ hello subcommand --world val # subcommand with world=val
$ hello subcommand --yes # boolean yes
$ hello --world val subcommand --world val # depending on globals, subcommand:[val val] or global:val, world:val
$ hello --yes subcommand # boolean yes
$ hello --world subcommand # root command with world=subcommand

I would prefer globals to be explicitly defined. Helptext can be managed with categories (and optionally hiding globals in subcommand helptext). This would mean that globals have to be defined in all subcommands (flag definitions can be reused with variables).
Explicit globals would mean that order does not matter ($ hello --world val subcommand --world val, where --world is the same). The problem here is that the parser does not know what subcommand flags it parses against before parsing (--world could be a bollean, like --yes). This could be solved by restricting flags to be allowed only after subcommands ($ hello --world val subcommand would be invalid).
Implicit globals would mean that flags have a recursive flag in their definition, and only ever defined once. While parsing, the arguments are parsed against root command's definitions. When a subcommand (choke) is found, everything until the subcommand is parsed again for only recursive definitions. Next, the subcommand arguments are parsed (recursively). Option order would always matter.
Right now, implicit globals sound better. This might need more examples.

Progress at https://github.com/jtagcat/harg/tree/hcli. It's coming together beautifully imo, needs a workweek more (x2 for unused feature creep).

@jtagcat We have support for persistent flags in v3 right now. So if you mark a flag as persistent it will be available to all subsequent sub commands. if sub command defines same flag it will take precedence over persistent one.

@jtagcat Right now we have 2 competing arg parsers, yours and @meatballhat 's argh. At some point we have to make a decision which path is preferred.

Above is now released,  you can see my tests here: https://github.com/taubyte/tau/blob/main/cli/args/args_test.go

@skelouse sorry for the long delay! I think your requests are accounted for, but I'll definitely want more feedback once this is closer. I've been occupied with other life adventures since ~January-ish but I've got some vacation time coming up 🤞🏼

I have lost focus on this more than once, and IIUC others in threads here have also moved on, so I'd like to propose that this is not a blocker for v3 release. @urfave/cli WDYT?

I agree. We probably handle most of the use cases for a cli utility. Refitting a new parser is a nice engineering project but adds only incremental value

I am closing this as we are able to extend golang flag library to the max extent possible. We have support for pretty much every requirement that was required of a new parser

authors: dearchap jtagcat meatballhat skelouse

repo: urfave/cli


text:
v2 - Fix incorrectTypeForFlagError for pointers

What type of PR is this?

bug

What this PR does / why we need it:
When configs parsed into MapInputSource are looked up, they report type mismatch errors, as expected. However, if the type is mismatched because it somehow ended up becoming a pointer, the error message doesn't actually indicate this. Instead, it reports an "actual type" of '' - the empty string. This is a known limitation of the way reflect works, and is used elsewhere in the code to dereference the pointer to get the actual type. So I'm not sure why it was overlooked in this case.
Testing
A test was added to ensure this change works as expected.
Release Notes
NONE

I'll do a v3 version of this if needed once v3 supports configuration files.

Further exploration reveals this is inaccurate. I need to figure out what type I actually get and provide a fix that way. Closing until then.


text:
Updated git clone URL

My first commit!!!!

Gogogo Johannes!!!

authors: fu johannesmaxkappel

repo: ursgal/ursgal


text:
Integration not listed in GOG Galaxy's list of community integrations

Are there any plans to make this integration available through the client?

Hi yes I would like for that to happen but it is up to the GOG Galaxy team to make that happen. I have been in contact and they've said it is on their list. So I guess we'll just have to wait.
Thanks,
Samit


text:
Feedback for “Bruno CLI”

Does bru run request.bru --reporter-json results.json still work?
I get an error when i try it and i dont see reporter-json amongst the arguments allowed

Hey @costiganAPI
Yes, this should work.
Can you share which version of bru cli you are on - bru --version?

1.22.0

Hey @costiganAPI,
I tested the --reporter-json command on Bruno CLI version 1.22.0 and found that it does not support this command. I recommend upgrading to the latest version of Bruno CLI.
If you encounter any issues with the latest version, please feel free to reach out.

Hey @costiganAPI,
Closing this issue because --reporter-json is working on latest bruno cli version.
I’ve attached a screenshot of the terminal where the command works with the latest version of Bruno CLI to resolve this issue.

authors: costiganAPI ganesh-bruno

repo: usebruno/bruno-docs


text:
Fix: fix population of data when data-urlencode flag is used with G flag i…

Description

fix population of request data field when using the --data-urlencode flag along with the -G or --get flag when importing from curl closes #2010

Contribution Checklist:

[x] The pull request only addresses one issue or adds one feature.
[x] The pull request does not introduce any breaking changes
[x] I have added screenshots or gifs to help explain the change if applicable.
[x] I have read the contribution guidelines.

Note: Keeping the PR small and focused helps make it easier to review and merge. If you have multiple changes you want to make, please consider submitting them as separate pull requests.
Publishing to New Package Managers
Please see here for more information.

Thank you @jwetzell !
This will go out in the 1.13.0 release. Please subscribe to Discord announcement channel to stay notified on the releases.

authors: helloanoop jwetzell

repo: usebruno/bruno


text:
upload module for pawsey

@Slugger70 this puts the upload store in /mnt/user-data because of the recommendation in https://docs.galaxyproject.org/en/master/admin/nginx.html#receiving-files-with-nginx "create a directory in which to store uploads (ideally, for performance reasons, on the same filesystem as Galaxy’s datasets)" but we could potentially be putting this somewhere else.  Initially when I was trying this out on dev I was using another volume mounted from the galaxy server.

no worries
On Fri, 30 Apr 2021 at 11:13, cat-bro @.***> wrote:

Thanks @Slugger70 https://github.com/Slugger70, since it's
read-only-Fri I won't merge this until we are ready to run it
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/usegalaxy-au/infrastructure/pull/234#issuecomment-829729823,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANI3XWXTHMBTPSEFCSQJ33TLH73PANCNFSM4326TY5Q
.

--
*Simon Gladman *| Second Lieutenant
Wyndham Vale Fire Brigade
PO Box 410 Werribee 3030
Mob. 0418 421 077
Email. @.*** @.**>

repo: usegalaxy-au/infrastructure


text:
An error will occur when the file name contains a plus sign.

Describe the bug
I am currently using version 0.13.1. When I use local storage, the file should be in the "year" directory, but instead an extra level of directory is created, causing problems when the original file name has "+".
 "error": "code=500, message=Failed to find resource by ID: 10053, internal=not found",   "message": "Failed to find resource by ID: 10053"
And at that time, clearing unnecessary resources and folders did not result in the deletion of the folder itself; only the contents of the files were deleted. In previous versions, a separate folder was not created for each attachment.
Steps to reproduce

Upload a file with a name that contains a plus sign.
save
An error will occur when clicking to view the attachment.

Screenshots or additional context
No response

You can paste you storage config, such as the storage type and directory. This maybe useful to handle this issue.

this is my local storage config
assets/{year}/{timestamp}_{filename}
I only used this local storage configuration and never changed it, but after using 0.13.1, an additional level of directory was created.

Just replace the {filename} to {publicid} in your config to fix this problem.

According to the docs configuration, I didn't know there was this new configuration option.
In this way, the original file name will be replaced with CID  :(  .
even if the configuration option is changed,Even if there is a plus sign in the file name, it will still result in an error.

This issue will be fixed in #1892 .
And again again again, we do really need to avoid use the original filename from user.

authors: athurg fiifff

repo: usememos/memos


text:
feat etcd: merge etcd driver (shbr)

Base implementation of the etcd driver:

Get
Put
Delete
(with prefix versions)

wip watch version

recheck

repo: userver-framework/userver


text:
Update npm dependencies

Update @docusaurus/core from ^2.0.0-rc.1 to ^2.3.1
Update @docusaurus/preset-classic from ^2.0.0-rc.1 to ^2.3.1
Update react-icons from ^4.4.0 to ^4.7.1

ver2が正式リリースされてから、どんどんアップデートされてますよねー

repo: ut-code/utcode-learn


text:
Consider hosting project under pytest-dev

Have you considered hosting this plugin under @pytest-dev organization? The process can be initiated with a ticket on https://github.com/pytest-dev/meta/issues
I am asking this because I am not keen to add dependency on plugins that can easily become unmaintained. (happened multiple times in the past).
I am also a python plugin author and I did that to make the future of the plugin safer.

:+1: That's a good idea. I'm going to prepare for requirements of transferring repository to pytest-dev (there are no tox configuration or changelog file in this repository now).

@ssbarnea I prepared changelog and tox configuration (I think this plugin is ready to be transferred). Can I submit an issue of migrating this plugin to pytest-dev/meta (or should I do something else more)?

Please create a ticket, I will try to help with it. Is better if owner is proposing it, for obvious reasons.

I see.

I created a ticket https://github.com/pytest-dev/meta/issues/9. Thank you for your help!

authors: ssbarnea utgwkk


text:
When install windows 10 can't uncheck “Import VHDX Image”

Describe the issue
I follow the Windows 10/11 install instructions to install windows 10. When I follow the step 5: Uncheck “Import VHDX Image” and you should see the text above change to “Boot ISO Image”. Press “Browse” and select the ISO you built in step 1., I found I can't uncheck the Import VHDX Image checkbox. So the installation process cannot continue. Please help. Thanks.

Configuration
UTM Version:  3.1.5(53)
OS Version:  mac bigSur 11.4
Intel or Apple Silicon?  Apple Silicon
Crash log
If the app crashed, you need a crash log. To get your crash log, open Console.app, go to Crash Reports, and find the latest entry for either QEMU, QEMUHelper, or qemu-*. Right click and choose Reveal in Finder. Attach the report here.
Debug log
For all issues, including crashes, you should attach a debug log. Open UTM, and open the settings for the VM you wish to launch. Near the top of the QEMU page is Debug Log. Turn it on and save the VM. After you experience the issue, open the VM settings again and select Export Log... and attach it here.
Upload VM
(Optional) If possible, upload the config.plist inside the .utm. If you do not have this, you can upload the entire .utm but note this contains your personal data. Since Github has an attachment size limit, you may want to upload to another service such as Google Drive. Link it here.

This will be fixed in v3.2.x but as a workaround you can select an empty file for the VHDX then open up the VM settings and delete the drive created from your empty file and create a new drive with 64GB and set it to "NVMe" as interface. Then you can save the VM, choose your ISO from the home screen, and boot the VM.

This will be fixed in v3.2.x but as a workaround you can select an empty file for the VHDX then open up the VM settings and delete the drive created from your empty file and create a new drive with 64GB and set it to "NVMe" as interface. Then you can save the VM, choose your ISO from the home screen, and boot the VM.

When I boot the VM, it stop in the boot interface.  How do I continue?

You may need to reorder your drives so the removable CD drive is first (before your created NVMe)

I change the drives order and make the cd drive at the first, but when I start the VM, it still stop in the boot interface.
The ISO file is generated at the step1.

iso file:

when I go into the boot config system, I found the boot order is correct.

Can you post the name of your generated iso file?

Can you post the name of your generated iso file?

The file name is 21390.1_MULTI_X64_EN-US.ISO. The file size is 3.8G.

So you specified that you are on a Apple Silicon computer but you downloaded the x86_64 ISO. Please make sure you are downloading ARM64.

OK. Thanks. I will try the ARM64 ISO later

@osy It works! Thanks.

I hava the same problem, but using the ARM64...

Please use the workaround above https://github.com/utmapp/UTM/issues/3760#issuecomment-1066188688

Actually that's what I did, i also tried created directly by the "custom VM", both ended up at this boot interface.

Can anyone tell me how to export .utm to other format, e.g. supported by Parallels Desktop?

authors: lemessdavi osy skol101 zhaozhiming

repo: utmapp/UTM


text:
VM’s dont boot and crash instantly after updating from 4.0.9 to 4.1.5

i recently updated from 4.0.9 to 4.1.5 and my vms do not work after the update. New vms can be created and work
perfectly.
Configuration (required)

UTM Version: 4.1.5
OS Version: iOS 15.4.1
Device Model: iPhone 7 Plus
Is it jailbroken (name jailbreak used)?
Trollstore not jailbroken
How did you install UTM?
trollstore

Crash log
If the app crashed, you need a crash log. To get your crash log, open the Settings app and browse to Privacy -> Analytics & Improvements -> Analytics Data and find the latest entry for UTM. You should export the text and attach it here.
utm analytic.txt
Debug log
For all issues, including crashes, you should attach a debug log. Open UTM, and open the settings for the VM you wish to launch. Near the bottom of the configuration options (or at the top of the QEMU page) is Debug Log. Turn it on and save the VM. After you experience the issue, quit the VM and re-launch UTM. Open the VM settings again and select Export Log... and attach it here.
debug.log
Upload VM
(Optional) If possible, upload the config.plist inside the .utm. If you do not have this, you can upload the entire .utm but note this contains your personal data. Since GitHub has an attachment size limit, you may want to upload to another service such as Google Drive. Link it here.

Please provide the config.plist from your VM

I've found this happening transferring VMs from devices to each other (airdrop from iPhone to iPad for example) and also moving between apps (UTM SE to UTM)
It hasn't happened taking VMs out of the UTM app dir and putting them back in after it was reinstalled from AltStore (that was on same device whole time)

Please provide config.plist so I can reproduce the issue, thanks.

attach debug log where and how?


text:
Exception at start

Hi Gerwin,
I get the following exception at start related to sunData, and sometimes also later. I merged the old ORTEP scripts using the sst sensor and model workspace with the most recent Demkit. In the ORTEP model the sunData is used to predict PV on both 3-phase and single-line inverters:

pvc = LivePvCtrl("PVCTRL_3P_L"+str(i+1), pv, ctrl, sun, sim)
pvc = LivePvCtrl("PVCTRL_SP_L3", pv, ctrl, sun, sim)

09:24:43 | MESSAGE: Starting
09:24:50 | MESSAGE: Simulating at time: 09-08-2023 09:24:50 CEST+0200
Exception in thread Thread-3 (zCallSingle):
Traceback (most recent call last):
File "/usr/lib/python3.10/threading.py", line 1016, in _bootstrap_inner
self.run()
File "/usr/lib/python3.10/threading.py", line 953, in run
self._target(*self._args, **self._kwargs)
File "/home/dennis/work/ortep/demkit-github/components/core/core.py", line 682, in zCallSingle
return getattr(recv, func)(*args)
File "/home/dennis/work/ortep/demkit-github/components/ctrl/groupCtrl.py", line 225, in initiatePlanning
self.doInitialPlanning(s)
File "/home/dennis/work/ortep/demkit-github/components/ctrl/groupCtrl.py", line 261, in doInitialPlanning
results = self.zCall(self.children, 'doInitialPlanning', s, list(parents))
File "/home/dennis/work/ortep/demkit-github/components/core/entity.py", line 143, in zCall
return self.host.zCall(receivers, func, *args)
File "/home/dennis/work/ortep/demkit-github/components/core/core.py", line 654, in zCall
return self.zCallList(receivers, func, *args)
File "/home/dennis/work/ortep/demkit-github/components/core/core.py", line 671, in zCallList
result[recv] = getattr(recv, func)(args)
File "/home/dennis/work/ortep/demkit-github/components/ctrl/devCtrl.py", line 158, in doInitialPlanning
result = copy.deepcopy(self.doPlanning(signal,  False))
File "/home/dennis/work/ortep/demkit-github/components/ctrl/loadCtrl.py", line 133, in doPlanning
p[c] = self.doPrediction(time-(time%timeBase),  time-(time%timeBase)+timeBaselen(signal.desired[c]))
File "/home/dennis/work/ortep/demkit-github/components/ctrl/live/livePvCtrl.py", line 82, in doPrediction
result = self.predictProduction(sunPrediction, startTime,  endTime)
File "/home/dennis/work/ortep/demkit-github/components/ctrl/live/livePvCtrl.py", line 171, in predictProduction
result.append(min(0, max(sunData[idx]['GHI']*self.model[b][0] + sunData[idx]['DNI']*self.model[b][1], self.maxProduction[b]) ) )
IndexError: list index out of range
Kind regards,
Dennis

I did some debugging, on the arguments of result.length and found the following, apparently self.maxProduction is empty, while it worked fine until 01:00 this morning after I started yesterday. I tried changing solcast
12:17:41 | WARNING: [PVCTRL_3P_L1] livePvCtrl model b=20 idx=0, len(model)=48, len(maxProduction)=0

Apparently not all realized values are available after restarting demkit, had to also change the following om loadCtr.py:

  				self.realized[c][time] = prediction[idx]

  				try:

  					self.realized[c][time] = prediction[idx]

  				except:

  					self.realized[c]={ time : prediction[idx] }

repo: utwente-energy/demkit


text:
printf help page could be improved

https://uutils.github.io/coreutils-docs/user/utils/printf.html
at least a description + the version number

Hello! may I work on this please?

Of course! Go ahead!

authors: ndd7xv sylvestre tertsdiepraam

repo: uutils/coreutils


text:
mv, cp: add support for --update=none

#4627 cover mv/update
test still failing because of diff in err messages

i know it is the draft but don't forget the tests please :)


text:
Rewrite tee to conform to nightly build.

The utility needed a substantial rewrite due to library changes and lifetime issues. I also needed to implement the MultiWriter struct since it was no longer available.

Thanks!

authors: Heather jbcrail


text:
df: fix size column padding

Similarly to the Used column, GNU df pads an extra space to the right of the Size column.

I have to admit I don't understand the reason for this change. Do you have an example where our output differs from the output of GNU df without this change?

Here's the output of df -h with GNU df and uutils df (Arch Linux 6.9.1-arch1-2, if it matters):
GNU:
Filesystem      Size  Used Avail Use% Mounted on
dev             3.7G     0  3.7G   0% /dev
run             3.8G  1.5M  3.8G   1% /run
efivarfs        246K   50K  192K  21% /sys/firmware/efi/efivars
/dev/nvme0n1p3  230G  136G   65G  68% /
tmpfs           3.8G   86M  3.7G   3% /dev/shm
tmpfs           3.8G   34M  3.7G   1% /tmp
/dev/nvme0n1p1  511M  165M  347M  33% /boot
tmpfs           761M   64K  761M   1% /run/user/1000

uutils:
Filesystem     Size  Used Avail Use% Mounted on
dev            3.7G     0  3.7G   0% /dev
run            3.8G  1.5M  3.8G   1% /run
efivarfs       246K   50K  192K  21% /sys/firmware/efi/efivars
/dev/nvme0n1p3 230G  136G   65G  68% /
tmpfs          3.8G   86M  3.7G   3% /dev/shm
tmpfs          3.8G   34M  3.7G   1% /tmp
/dev/nvme0n1p1 511M  165M  347M  33% /boot
tmpfs          761M   64K  761M   1% /run/user/1000

Ah, now I see, good catch!

Thanks!

i wish it was covered by a test :(

@sylvestre it's covered by an invalid test I'm currently fixing ;-)

ok, merci :)

authors: Qelxiros cakebaker sylvestre


text:
Create dependabot.yml

closes #145

Should we limit this to the template only?
Wonder if we need this for event specific sites

Should we limit this to the template only? Wonder if we need this for event specific sites

Hmmm, good point! This would be a good case for a .github/.template-ignore as discussed here (https://github.com/orgs/community/discussions/22183) but isn't implemented yet. Since in reality we mostly update this repository a couple times a year, happy to close this and just stick to manual bumps

authors: jomey scottyhq

repo: uwhackweek/jupyterbook-template


text:
it happens to ask me to inpput gerrit password everytime when I open the IDE

Its a nice plugin. But in idea2020.1, it happens to ask me to inpput gerrit password everytime when I open the IDE, I dont know what`s happen

@rockingGitHub Probably this solution helps in your case? https://github.com/uwolfer/gerrit-intellij-plugin/issues/393

authors: rockingGitHub uwolfer

repo: uwolfer/gerrit-intellij-plugin


text:
DOC: Clear warnings from roxygen build

Description
This PR should clear some warnings that are observed in the CI job that builds the roxygen docs:
/home/vsts/work/1/s/cpp/oneapi/dal/graph/service_functions.hpp:90: warning: argument 'graph' of command @param is not found in the argument list of oneapi::dal::preview::get_edge_value(const Graph &g, vertex_type< Graph > u, vertex_type< Graph > v) -> const edge_user_value_type< Graph > &
/home/vsts/work/1/s/cpp/oneapi/dal/graph/service_functions.hpp:158: warning: The following parameter of oneapi::dal::preview::get_edge_value(const Graph &g, vertex_type< Graph > u, vertex_type< Graph > v) -> const edge_user_value_type< Graph > & is not documented:
  parameter 'g'
/home/vsts/work/1/s/cpp/oneapi/dal/algo/jaccard/common.hpp:148: warning: argument 'in' of command @param is not found in the argument list of caching_builder::operator()(std::int64_t block_max_size)
/home/vsts/work/1/s/cpp/oneapi/dal/algo/jaccard/common.hpp:148: warning: argument 'out' of command @param is not found in the argument list of caching_builder::operator()(std::int64_t block_max_size)
/home/vsts/work/1/s/cpp/oneapi/dal/algo/jaccard/vertex_similarity_types.hpp:40: warning: argument 'graph' of command @param is not found in the argument list of vertex_similarity_input< Graph, Task >::vertex_similarity_input(const Graph &g, caching_builder &builder)
/home/vsts/work/1/s/cpp/oneapi/dal/algo/jaccard/vertex_similarity_types.hpp:40: warning: argument 'in' of command @param is not found in the argument list of vertex_similarity_input< Graph, Task >::vertex_similarity_input(const Graph &g, caching_builder &builder)
/home/vsts/work/1/s/cpp/oneapi/dal/algo/jaccard/vertex_similarity_types.hpp:40: warning: argument 'out' of command @param is not found in the argument list of vertex_similarity_input< Graph, Task >::vertex_similarity_input(const Graph &g, caching_builder &builder)
/home/vsts/work/1/s/cpp/oneapi/dal/algo/jaccard/vertex_similarity_types.hpp:44: warning: The following parameters of oneapi::dal::preview::jaccard::vertex_similarity_input::vertex_similarity_input(const Graph &g, caching_builder &builder) are not documented:
  parameter 'g'
  parameter 'builder'
/home/vsts/work/1/s/cpp/oneapi/dal/spmd/communicator.hpp:254: warning: argument 'send_buf' of command @param is not found in the argument list of communicator< MemoryAccessKind >::allgather(const array< D > &send, const array< D > &recv) const
/home/vsts/work/1/s/cpp/oneapi/dal/spmd/communicator.hpp:254: warning: argument 'send_count' of command @param is not found in the argument list of communicator< MemoryAccessKind >::allgather(const array< D > &send, const array< D > &recv) const
/home/vsts/work/1/s/cpp/oneapi/dal/spmd/communicator.hpp:254: warning: argument 'recv_buf' of command @param is not found in the argument list of communicator< MemoryAccessKind >::allgather(const array< D > &send, const array< D > &recv) const
/home/vsts/work/1/s/cpp/oneapi/dal/spmd/communicator.hpp:254: warning: argument 'recv_count' of command @param is not found in the argument list of communicator< MemoryAccessKind >::allgather(const array< D > &send, const array< D > &recv) const
/home/vsts/work/1/s/cpp/oneapi/dal/spmd/communicator.hpp:254: warning: argument 'dtype' of command @param is not found in the argument list of communicator< MemoryAccessKind >::allgather(const array< D > &send, const array< D > &recv) const
/home/vsts/work/1/s/cpp/oneapi/dal/spmd/communicator.hpp:264: warning: The following parameters of oneapi::dal::preview::spmd::v1::communicator::allgather(const array< D > &send, const array< D > &recv) const are not documented:
  parameter 'send'
  parameter 'recv'
/home/vsts/work/1/

PR should start as a draft, then move to ready for review state after CI is passed and all applicable checkboxes are closed.
This approach ensures that reviewers don't spend extra time asking for regular requirements.
You can remove a checkbox as not applicable only if it doesn't relate to this PR in any way.
For example, PR with docs update doesn't require checkboxes for performance while PR with any change in actual code should have checkboxes and justify how this code change is expected to affect performance (or justification should be self-evident).
Checklist to comply with before moving PR from draft:
PR completeness and readability

[x] I have reviewed my changes thoroughly before submitting this pull request.
[x] Git commit message contains an appropriate signed-off-by string (see CONTRIBUTING.md for details).
[x] I have added a respective label(s) to PR if I have a permission for that.
[x] I have resolved any merge conflicts that might occur with the base branch.

Testing

[x] All CI jobs are green or I have provided justification why they aren't.

Performance
Not applicable.

CI failures in OpenBLAS are unrelated to this PR.

repo: uxlfoundation/oneDAL


text:
Keyboard navigation broken on embedded / inline

On the demo page of the Bootstrap Datepicker, when selecting the embedded / inline mode, the keyboard navigation with the arrows does not work. It does not work either on the website I'm working on. I imagine someone would have reported the issue already but I could not find it in the this issue section.

I am also facing same issue. When i use startDate or data-attribute for this only down arrow works until you select a date and after selection it works but also accepts those date which you excluded initially.

@20v100 I'm facing the same issue. Keyboard navigation seems to be supported only if there is an input having focus. So it's not supported at all for embedded / inline mode and also not working if datepicker is opened other than giving focus to input (e.g. show method, component button).
@anurag1490 That was another bug. Should be fixed by #1687.

Is this fixed yet? The inline datepicker is still not focusable by keyboard even on the demo site.
https://uxsolutions.github.io/bootstrap-datepicker/?markup=embedded&format=&weekStart=&startDate=&endDate=&startView=0&minViewMode=0&maxViewMode=4&todayBtn=false&clearBtn=false&language=en&orientation=auto&multidate=&multidateSeparator=&keyboardNavigation=on&forceParse=on#sandbox

repo: uxsolutions/bootstrap-datepicker


text:
Automatic reconnection [DAVIS 240B]

No need to manually relaunch the driver when camera is disconnected.

tested on my end and looks good to me, thanks @valeriovarricchio!

authors: eliasm valeriovarricchio


text:
Feature request

Is it possible load images from the Documents Folder. More Specifically ones that are put into the app via iTunes sharing?
Thanks

also want picture preview when  selecting photos

Thank you for the suggestions

authors: heyehao2008 kylebuttress uzysjung

repo: uzysjung/UzysAssetsPickerController


text:
🛑 Faucettalk is down

In 6664fb0, Faucettalk (https://www.faucettalk.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Faucettalk is back up in 67f17de.


text:
Updating kubelet to survive node reboot

also added additional calico manifest to be configured in bootkube_env

@larryrensing, I did some playing around and created a calico-2.6.1-v1.7.5.yaml file today, but you will probably want to validate it for yourself. hope it saves some time, but if there are any errors, feel free to make changes.
https://gist.github.com/v1k0d3n/069228bc89e21fda7381ee833562f37b

pushed updates

pulling in so we can work on other bits. i can clean up the remaining variable.


text:
brew services start v2ray-core failed.

The geoip.dat file and geosite.dat file should be placed in the bin folder, otherwise brew services start v2ray-core will fail.
version: 4.33.0
current path of geoip.dat file and geosite.dat file: /usr/local/Cellar/v2ray-core/4.33.0/share/
correct path of geoip.dat file and geosite.dat file: /usr/local/Cellar/v2ray-core/4.33.0/bin/

brew install v2ray

authors: jinmiaoluo kslr