Convert Intel GNA driver to devicetree

Convert drivers/neural_net/intel_gna.c to be devicetree based.

@nashif not sure who to assign this to, so started with you :).

@dcpleung  can you please take a look?

@dcpleung  can you please take a look?


using token as variable in postman

i just wanted to use access_token as a variable........................... give me some solution.

Our documentation is located at https://www.getpostman.com/docs/. Is there any specific use-case that you're facing a problem with?

i want this access_token as variable how can i do this..................................

You can try setting an environment variable as explained in the documentation. It'll then be available to use as {{access_token}}, or whatever you name your variable.

i have try this but it is not working can u send me one screen shot for
this issue
On Mon, May 25, 2015 at 3:11 PM, Abhijit Kane<EMAIL_ADDRESS>wrote:

You can try setting an environment variable as explained in the
documentation. It'll then be available to use as {{access_token}}, or
whatever you name your variable.
—
Reply to this email directly or view it on GitHub
https://github.com/a85/POSTMan-Chrome-Extension/issues/1074#issuecomment-105184886
.

Hope this helps and is what you are looking for ...

This is setting the same environment variable but it will only be set when that particular endpoint is run. Because it is set in the Pre-request script, it will be set before the endpoint is executed.

in 1 st fig i have just created one schema for my response body and in
postamn i want to comapre the schema with my response Body i am not able to
solve this issue can u solve my issue and send me one screenshot for this
On Tue, Jun 2, 2015 at 8:32 PM, dhoyt<EMAIL_ADDRESS>wrote:

This is setting the same environment variable but it will only be set when
that particular endpoint is run. Because it is set in the Pre-request
script, it will be set before the endpoint is executed.
[image: image]
https://cloud.githubusercontent.com/assets/10944880/7939027/c8f86e06-0916-11e5-9c61-b1228255d10e.png
—
Reply to this email directly or view it on GitHub
https://github.com/a85/POSTMan-Chrome-Extension/issues/1074#issuecomment-107984515
.

Can you show what you have done and we can go from there ?

i have send request from postman and get the response body
this is my response Body
{

"studentId": "1",
"studentName": "Rohith",
"fromDate": "01-4-2015",
"toDate": "30-4-2015",
"absent_dates": [ ],
"total_absent_days": "0",
"total_working_days": "22",
"present_days": "22"

}
which i get after sending the request
now i have generated schema for it from here http://jsonschema.net/#/
now i want to compare this schema with my response body
i am using tiny validator for json Data
is it correct ..............
or just tell me how to compare this and what is the use of this tiny
validator for json data i have search it but i can't get the
solution..............
On Wed, Jun 3, 2015 at 6:24 PM, dhoyt<EMAIL_ADDRESS>wrote:

Can you show what you have done and we can go from there ?
—
Reply to this email directly or view it on GitHub
https://github.com/a85/POSTMan-Chrome-Extension/issues/1074#issuecomment-108388159
.

In the Pre-request script window ...
var yourSchema =
{
YOUR SCHEMA STUFF GOES HERE
}

postman.setEnvironmentVariable("yourSchema", JSON.stringify(yourSchema));

In the Tests window ...
var jsonresponseData = JSON.parse(responseBody);

var validJSON = tv4.validate(jsonresponseData, JSON.parse(environment.yourSchema));

if(!validJSON) {
    tests["TEST FAILED - your JSON Schema"] = validJSON;
    tests["TEST FAILED - tv4 error Code = "+tv4.error.code] = validJSON;
    tests["TEST FAILED - tv4 dataPath = "+tv4.error.dataPath] = validJSON;
    tests["TEST FAILED - tv4 message = "+tv4.error.message] = validJSON;
    tests["TEST FAILED - tv4 schemaPath = "+tv4.error.schemaPath] = validJSON;
}
else {
    tests["TEST PASSED - your JSON Schema"] = validJSON;
}

console.log(tv4.error);

thanku sir
i have one more issue
The JSON file needs to be an array of key/value pairs. The keys are used as
variable names while the values are replaced inside requests.
sir i want to compare my response body with variables is it possible to do
so
On Thu, Jun 4, 2015 at 6:31 PM, dhoyt<EMAIL_ADDRESS>wrote:

In the Pre-request script window ...
var yourSchema =
{YOUR SCHEMA STUFF GOES HERE
}
postman.setEnvironmentVariable("yourSchema", JSON.stringify(yourSchema));
In the Tests window ...
var jsonresponseData = JSON.parse(responseBody);
var validJSON = tv4.validate(jsonresponseData, JSON.parse(environment.yourSchema));
if(!validJSON) {
tests["TEST FAILED - your JSON Schema"] = validJSON;
tests["TEST FAILED - tv4 error Code = "+tv4.error.code] = validJSON;
tests["TEST FAILED - tv4 dataPath = "+tv4.error.dataPath] = validJSON;
tests["TEST FAILED - tv4 message = "+tv4.error.message] = validJSON;
tests["TEST FAILED - tv4 schemaPath = "+tv4.error.schemaPath] = validJSON;
}else {
tests["TEST PASSED - your JSON Schema"] = validJSON;
}
console.log(tv4.error);
—
Reply to this email directly or view it on GitHub
https://github.com/a85/POSTMan-Chrome-Extension/issues/1074#issuecomment-108889219
.

i am currently testing Api in postman  i have one api
/app/getHomework/student/$studentId/$dateAssigned
and these two variables $studentId and $dateAssigned  this will take values
like
/app/getHomework/student/1/04-06-2015
/app/getHomework/student/2/06-06-2015
at one time we r sending only for student having id 1
at a time it is possible that lots of user can hit this api so i want to
make it dynamically so that every user while hitting this url will get
corresponding data
On Sat, Jun 6, 2015 at 4:32 PM, abhinay kumar<EMAIL_ADDRESS>wrote:

thanku sir
i have one more issue
The JSON file needs to be an array of key/value pairs. The keys are used
as variable names while the values are replaced inside requests.
sir i want to compare my response body with variables is it possible to do
so
On Thu, Jun 4, 2015 at 6:31 PM, dhoyt<EMAIL_ADDRESS>wrote:

In the Pre-request script window ...
var yourSchema =
{YOUR SCHEMA STUFF GOES HERE
}
postman.setEnvironmentVariable("yourSchema", JSON.stringify(yourSchema));
In the Tests window ...
var jsonresponseData = JSON.parse(responseBody);
var validJSON = tv4.validate(jsonresponseData, JSON.parse(environment.yourSchema));
if(!validJSON) {
tests["TEST FAILED - your JSON Schema"] = validJSON;
tests["TEST FAILED - tv4 error Code = "+tv4.error.code] = validJSON;
tests["TEST FAILED - tv4 dataPath = "+tv4.error.dataPath] = validJSON;
tests["TEST FAILED - tv4 message = "+tv4.error.message] = validJSON;
tests["TEST FAILED - tv4 schemaPath = "+tv4.error.schemaPath] = validJSON;
}else {
tests["TEST PASSED - your JSON Schema"] = validJSON;
}
console.log(tv4.error);
—
Reply to this email directly or view it on GitHub
https://github.com/a85/POSTMan-Chrome-Extension/issues/1074#issuecomment-108889219
.


Review fetch strategy

A problem example: Keeping enemies updated.
To find an approach that can be applied to other similar issues.
To see if The Graph usage can improve blockchain fetching.

Duplicated https://github.com/marcelomorgado/fyght/issues/14


affected/package: Slices do not cut correctly.

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

go version go1.18rc1 darwin/arm64

Does this issue reproduce with the latest release?
Yes: https://go.dev/play/p/9Xyqfj22OlK
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="arm64"
GOBIN=""
GOCACHE="/Users/jcowwell/Library/Caches/go-build"
GOENV="/Users/jcowwell/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/jcowwell/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/jcowwell/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_arm64"
GOVCS=""
GOVERSION="go1.18rc1"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/jcowwell/Local Github Projects/github.com/Jcowwell/go-algorithm-club/go.mod"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/c8/v4pc4g9d35n8slx7m825npgc0000gn/T/go-build1603233430=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?
Created a Function to slice elements at a specific index:
// Initially Tested with Generic Function but also made a non-Generic Function to be sure.
func GenericRemoveElementAtIndexFromSlice[T any](slice []T, index int) {
	if index >= len(slice) {
		return
	}
	slice = append(slice[:index], slice[index+1:]...)
}

based on this StackOverFlow response: https://stackoverflow.com/a/37335777/6427171
I noticed in the comments that a bug occurs like so: https://go.dev/play/p/9Xyqfj22OlK

My program: https://go.dev/play/p/UxCOi9YKCD8?v=gotip
What did you expect to see?
Expected to see a slice with an element removed with no duplicate elements at the end.
EX:
a := []int{1,2,3,4,5,6,7,8}
RemoveElementAtIndex(a, 0)
> a
[2,3,4,5,6,7,8]

What did you see instead?
EX:
a := []int{1,2,3,4,5,6,7,8}
RemoveElementAtIndex(a, 0)
> a
[2,3,4,5,6,7,8,8]

According to the Wiki in SliceTricks, one should be able to cut a value from a slice like so: https://github.com/golang/go/wiki/SliceTricks#cut,
but when doing so the last value is duplicated. I've provided a Go Playground code snippet to demonstrate this. Thinking of wiring a quick loop to see if there's a minimum/maximum for this occurrence.

I think there is some confusion here about how slices work. Please read https://go.dev/blog/slices-intro
In particular, you have to assign the result of GenericRemoveElementAtIndex back to a in order to change the length of a.
There's nothing about generics here - the same problem occurs if you replace T with int.


add support for tiled images

Fixes #104

Codecov Report
Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (474e468) 91.90% compared to head (5082930) 91.93%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #124      +/-   ##
==========================================
+ Coverage   91.90%   91.93%   +0.03%
==========================================
  Files          13       13
  Lines         902      918      +16
==========================================
+ Hits          829      844      +15
- Misses         73       74       +1

Files
Coverage Δ

src/ifds.jl
98.28% <100.00%> (-0.01%)
:arrow_down:

src/load.jl
98.33% <100.00%> (+0.37%)
:arrow_up:

src/layout.jl
90.00% <90.90%> (-0.75%)
:arrow_down:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Do you mind dropping the version number to v0.7.1? I know VersionVigilante will complain, but I rather this with #122 in one release.
Technically since this is a major feature update this would've made more sense to include in a minor release (i.e. v0.8.0) instead of a patch release. Honestly, with your contributions here and with #116, TiffImages.jl is rapidly approaching what I would consider sufficient for a first 1.0 release.
Are you planning on tackling any other major PRs soon? Because we could stack them and release them all as TiffImages v1.0.0.
Thanks for all your hard work!

I have PRs for #119, #58, and support for "planar" images

Perfect! I'll release v0.7.1 as a patch release and then we can batch all of those PRs as v0.8.0

For 1.0, I think it makes sense to try supporting most if not all of the LibTIFF test images (JPEG might be a tall order)


Add Dialog.fullscreen and example

fixes https://github.com/flutter/flutter/issues/104961
This PR adds Dialog. fullscreen, which allows the creation of a fullscreen dialog.
https://user-images.githubusercontent.com/48603081/192535668-ea5d16fd-75af-4167-aeab-6be88ede8318.mov
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@guidezpl
Created Dialog.fullscreen based on our discussion https://github.com/flutter/flutter/issues/104961#issuecomment-1185734993

@TahaTesser thank you for the great work! Do you know if this feature made it into any flutter releases? It seems that there's no Dialog.fullscreen in the last stable release - 3.3.10, but it's also not in the latest beta version - 3.7.0-1.2.pre. Do you know when this feature is planned to be released? Is there a way to track it?

Hi @OlegBezr
It should be available on the beta channel.  You can track the commit here and version tags associated with the commit.

I can also see the source code in beta


cmd/go: build ./... tries to traverse the entire filesystem when outside a module but with a potential config file to convert to go.mod

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

$ go version
go version go1.14 linux/amd64

Does this issue reproduce with the latest release?
Yes.
It also reproduces with go1.13 but not with go1.12.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN="/home/manlio/.local/bin"
GOCACHE="/home/manlio/.cache/go-build"
GOENV="/home/manlio/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GONOPROXY="github.com/perillo/go-init"
GONOSUMDB="github.com/perillo/go-init"
GOOS="linux"
GOPATH="/home/manlio/.local/lib/go:/home/manlio/src/go"
GOPRIVATE="github.com/perillo/go-init"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
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 -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build500333414=/tmp/go-build -gno-record-gcc-switches"
GOROOT/bin/go version: go version go1.14 linux/amd64
GOROOT/bin/go tool compile -V: compile version go1.14
uname -sr: Linux 5.5.5-arch1-1
/usr/lib/libc.so.6: GNU C Library (GNU libc) stable release version 2.31.
gdb --version: GNU gdb (GDB) 9.1

What did you do?
By accident I typed go build ./... from inside my home directory, and I notice that it took a lot of time, spinning my hard disk.
$ sync
$ sudo sh -c 'echo 3 >/proc/sys/vm/drop_caches'
$ time go build ./...
go: cannot find main module, but found .git/config in /home/manlio
	to create a module there, run:
	go mod init
go build ./...  13.39s user 14.64s system 19% cpu 2:20.65 total

Called again, with warm cache:
$ time go build ./...
go: cannot find main module, but found .git/config in /home/manlio
	to create a module there, run:
	go mod init
go build ./...  5.18s user 3.44s system 112% cpu 7.647 total

This only happens from inside my home directory, where there is a .git/config file.
Also, go build traverse the filesystem the entire filesystem only when the ./... pattern is specified.
$ time go build
go: cannot find main module, but found .git/config in /home/manlio
	to create a module there, run:
	go mod init
go build  0.02s user 0.04s system 6% cpu 1.031 total

(with no cached data in the kernel).

Heh, that's odd. I can reproduce it as well. Thanks for the report!

CC @jayconrod @matloob

It also reproduces with go1.13 but not with go1.12.

I'm also seeing a very slow go build ./... with go1.12 when in GOPATH mode. So I suspect that what's happening here is that somehow the module-mode go build is trying to resolve ./... before it realizes that it isn't even in a module.

You are right.
It has nothing to do with a potential config file to convert.  The issue title should be changed.
Thanks.

Unfortunately go can not simply ignore the pattern, as an example with go list std.

Here is another example where a using a ... pattern will cause go list to return a confusing warning, instead of reporting an error since the current working directory is not part of a module:
go list github.com/perillo/...
go: warning: "github.com/perillo/..." matched no packages
``

That go list pattern is arguably correct: you can go list packages in the standard library when outside of a module, and no package in the standard library matches the pattern github.com/perillo/....

But the first path element has a dot, so it can not be a standard library package.

That's true. At any rate, it is clearly not the same issue as the unnecessary filesystem walk for ./..., so to the extent that it is worth addressing at all, it should be a separate issue.


C-u C-x = command not working

I want to use the agda feature of displaying the required input for a certain unicode symbols, but couldn't find it anywhere in the available commands of agda-mode-vscode, the normal "ctrl-u ctrl-x =" command is not working and google does not have a single answer to this
The feature in emacs agda is described here: https://agda.readthedocs.io/en/latest/tools/emacs-mode.html#ok-but-how-can-i-find-out-what-to-type-to-get-the-character

Implemented in v0.2.16!
To lookup a symbol, select a symbol in the editor and then press C-x C-=
Or you can just press C-x C-= and there will be a prompt asking you for the symbol


Hi, can i train a binary problem?

Dear author, thanks for sharing so wonderful work. I have a question to ask you. In my case, I only focus on smile expression. Can I train a binary problem based on your work? Can you give some help or advice? Thanks!

In my opinion, you can separate the smile data and other data into two categories. In addition, you should add more neutral facial expressions. You may encounter data imbalance. Remember to use some techniques of data imbalance.


Transition source code to be an ES module

TDLR; allow Node.js and Deno to use this package as a native ECMAScript module.
Up until now, we've very deliberately held back on introducing any kind of build step to this project. Personally think that's been a wise decision as the benefits up doing so has not been obvious in terms of the complexity such a build step usually introduces in a project. Keeping everything in one .js file in good old fashioned ES3 has worked out really well so far.
That changes with what's introduced in this PR.
Why on earth should we suddenly change what has worked well all these years?? To me it's about following along with how both Node.js & JavaScript evolves and reacting to new related runtimes emerging, like Deno is a great example of.
Node.js, Deno and several modern browsers has built-in ES module support. Hence it's only natural to consider following along and make this package an ES module, rather than holding back just for the sake of not introducing a build step for the purity it.
Ofcourse backwards compatibility with non-ES module systems are kept as is, this is where a build step comes into play. The source code is now put inside the mustache.mjs file, and mustache.js | mustache.min.js is the build step output.
Tried my best creating a sensible commit history with some in-depth reasoning for each of them. Hopefully they'll shed some more light on the rationale and be of some help going forward (if we decide to merge this).

Missing pieces being worked on:

[ ] type: module in package.json as described in Node.js ECMAScript Modules docs
[ ] try making a CI module-systems test for Node.js using it as an ES module

Fixes https://github.com/janl/mustache.js/issues/698

@zekth & friends; a few weeks has passed since I ran CI, and after re-running the test that verifies mustache.js works with deno now, it exploded with what seems like TypeScript errors to me;
$ deno test --allow-net=deno.land test/module-systems/deno-test.ts

...

Compile file:///home/runner/work/mustache.js/mustache.js/test/module-systems/deno-test.ts
Download https://deno.land/std/testing/mod.ts
Download https://deno.land/std/testing/asserts.ts
Download https://deno.land/std/fmt/colors.ts
Download https://deno.land/std/testing/diff.ts
Download https://deno.land/std/testing/format.ts
error TS2371: A parameter initializer is only allowed in a function or constructor implementation.

► https://deno.land/std/testing/asserts.ts:132:39

132 export function assert(expr: unknown, msg = ""): asserts expr {
                                          ~~~~~~~~

error TS2304: Cannot find name 'asserts'.

...

https://github.com/janl/mustache.js/pull/728/checks?check_run_id=316803283#step:5:44
Any thoughts what might be causing this? Would be great to know we don't merge an unstable test that might fail if it hasn't run for a while..
I wouldn't be surprised at all if it's because I'm doing something wrong, either in the related deno CI setup or executing the test via deno.

Ahh! I'm assuming what I'm doing is not best practice in terms of importing
without a hint of version number anywhere. Should it be part og the import
or some external file, like package.json for npm projects?
On Sat, 23 Nov 2019 at 10:25, Vincent LE GOFF<EMAIL_ADDRESS>wrote:

@zekth commented on this pull request.
In test/module-systems/deno-test.ts
https://github.com/janl/mustache.js/pull/728#discussion_r349865647:

@@ -0,0 +1,17 @@
+import { test } from "https://deno.land/std/testing/mod.ts";
+import { assertEquals } from "https://deno.land/std/testing/asserts.ts";

You're not aiming the version in here.
CI is running using 0.21.0 let's try using<EMAIL_ADDRESS>here?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/janl/mustache.js/pull/728?email_source=notifications&email_token=AAJMWE2EIZSAIJLKXETKHDLQVDZJTA5CNFSM4JJ5P3B2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCMX5O7A#pullrequestreview-321902460,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJMWE6PCMJD4DT73HJGYVDQVDZJTANCNFSM4JJ5P3BQ
.

By this way you import the Latest version which is not recommended because your runtime and your imports may have incompatibility. Like using node 8 with node std lib of node 12

Yupp, that struck me too with your first answer.
So currently this is always controlled by specifying the version in each
and every import in a project, or is there some kind module management
alternative as well that I should be aware of?
On Sat, 23 Nov 2019 at 12:47, Vincent LE GOFF<EMAIL_ADDRESS>wrote:

By this way you import the Latest version which is not recommended because
your runtime and your imports may have incompatibility. Like using node 8
with node std lib of node 12
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/janl/mustache.js/pull/728?email_source=notifications&email_token=AAJMWE3WGC2XFE3EJOYEKJLQVEJ6JA5CNFSM4JJ5P3B2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEE7TQCY#issuecomment-557791243,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJMWEYSDDBQCVPBWAU2423QVEJ6JANCNFSM4JJ5P3BQ
.

Yes you can use import maps: https://github.com/denoland/deno/issues/3268#issuecomment-551859728

Thanks, much appreciate your quick replies on this! I'll have a look at
improving it later tonight.
On Sat, 23 Nov 2019 at 12:58, Vincent LE GOFF<EMAIL_ADDRESS>wrote:

Yes you can use import maps: denoland/deno#3268 (comment)
https://github.com/denoland/deno/issues/3268#issuecomment-551859728
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/janl/mustache.js/pull/728?email_source=notifications&email_token=AAJMWEYBPWEGDCS23QXKVI3QVELFDA5CNFSM4JJ5P3B2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEE7TVNA#issuecomment-557791924,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJMWE3OG6EXBT3RFQEM3CDQVELFDANCNFSM4JJ5P3BQ
.

🛑 found after having a Node.js test in place, with v13.2.0 that has .mjs support enabled by default: esm-usage test result.
That CI test result points to a big difference compared to how the module resolution in Node.js has worked until now; .json files cannot be imported directly. This is outlined in the Node.js / ESM / Experimental JSON Modules docs section, but doesn't help much as of writing this, because that is experimental and therefore opt-in with CLI flags. Personally would really appreciate if we wouldn't end up having to tell Node.js ES Modules users to remember to enable experimental features.
Therefore also worth consider other ways to getting the current version number into the source code. Or even ask ourselfs if having that .version property is really valuable to anyone.
Personally feel we need to sort this out before merging to master & publishing anything to npm.

Personally would really appreciate if we wouldn't end up having to tell Node.js ES Modules users to remember to enable experimental features.

Definitely agree.
Is injecting the version in the build process thinkable ? (it's a bit ugly compared to importing from package.json)

Also considering that even if Node.js ES modules would have .json support, I noticed the docs or some GitHub issue I stumbled upon, said that named imports would not be supported. In practise that would mean that we would have to import the entire contents of package.json, which for the built output is not ideal, when the only thing we really want is the rather simple version field value.
I'm not too familiar with rollup.js to be honest, might be a very natural way of doing that as part of the build process as you suggest 🤷♂

I'm not too familiar with rollup.js to be honest, might be a very natural way of doing that as part of the build process as you suggest 🤷♂

We can use this in the build process: https://github.com/rollup/plugins/tree/master/packages/replace

Nice!
That definitively looks like what we need to make sure old the .version field is kept for non-ES module systems. Although won't have much effect for the ones using the .mjs version 🤔 Which makes question the added value of that field to be honest.
Maybe there's some traces of the reason it was introduced in the first place if we dig into the git history / GitHub PRs.

On second thought, we've managed to survive all these years with the .version field value being hard coded in the source file (mustache.js). It has been kept in sync by a git pre-commit hook: https://github.com/janl/mustache.js/blob/e52478c14bcc035c09595cedffed5b2b870d8e17/hooks/pre-commit#L27-L32
Maybe we should keep that ad-hoc tool for now. ESm-ifying isn't really about refactor that .version anyways, so I realise I might have jumped that gun prematurely.

With all known issues fixed, commits cleaned up and PR no longer marked as a draft, this is very close to getting merged.
No objections has been made and we've got a handful of tests in place verifying usage from module systems we want to officially support.

For the sake of testing the pre-commit in practise, v3.2.0-beta.0 has been published to npm. Tweaks had to be made to that pre-commit, so good to have that checked off before merging as well.
Will be verifying the contents of that beta version as the last frontier before pressing the o-mighty-merge button.
Sorry for being slow, I just want to be as certain as possible this won't cause havoc knowing this is a big change in terms of how this module is glued together. Quite surprised we have 1.3 million downloads a week from npm these days, that deserves respect when pushing new versions IMO 😃

Publish to npm as v3.2.0, with updated CHANGELOG.md.
@zekth thanks for pushing this forward and being incredibly patience! Hoping the deno community will get some value of this going forward 🤞


Process substitution with bash 5.2.0 (Build 551)

bash 5.2.0 (Build 551) (bash-5.2.20230215_173052.zos.pax.Z)
look like process substitution is not yielding proper results
RC=(0) [SYSD] bash-5.2$ echo <(date)
<EMAIL_ADDRESS>RC=(0) [SYSD] bash-5.2$ cat <(date)
▒▒̀▒▒�▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒RC=(0) [SYSD] bash-5.2$
RC=(0) [SYSD] bash-5.2$ wc -l <(ssh l98misdb491 "cat *Yum")
0<EMAIL_ADDRESS>--
Expecting something like this
$ echo <(date)
/dev/fd63
$ cat <(date)
Thu Feb 16 13:29:25 CST 2023
$ wc -l <(ssh l98misdb491 "cat *Yum")
4    /dev/fd63

GNU bash, version 5.2.0(1)-release (i370-ibm-openedition)
RC=(0) [SYSA] bash-5.2$ cat <(date) | xxd
00000000: e8cd c180 282f ca80 9194 8091 969a 9590  ▒▒▒..ʀ▒▒▒▒▒▒▒▒
00000010: 9a90 9180 e4e0 e880 1690 1693 8e         ▒▒▒▒▒▒▒.▒.▒▒
RC=(0) [SYSA] bash-5.2$ cat <(date) | od -hc
0000000000    E8  CD  C1  80  28  2F  CA  80  91  94  80  91  96  9A  95  90
Y 315   A 200 050  \a 312 200   j   m 200   j   o 232   n 220
0000000020    9A  90  04  80  E4  E0  E8  80  16  90  16  93  8E
232 220 004 200   U   \   Y 200  \b 220  \b   l 216
0000000035

bashport_768/bash-5.2.20230319_200518.zos.pax.Z
This is now working as expected
bash-5.2$ cat <(date)
Mon Mar 20 18:18:27 CDT 2023
Is this working as expected?  Should there be a /dev/fdxx returned?
bash-5.2$ echo <(date)
<EMAIL_ADDRESS>Getting the correct line count. Should there be a /dev/fdxx returned?
bash-5.2$ wc -l <(ssh l98misdb491 "cat *Yum")
4<EMAIL_ADDRESS>

I think there's two things going on here.

It appears that our CI machines are not consistently setting HAVE_DEV_FD, not setting this triggers an alternate path to be used which create temporary files using mktemps. This is determine by the check test -r /dev/fd/0 which returns 0 on some of our CI machines and 1 on others.
zoslib does not appear to handle untagged character devices properly, such as /dev/fd*. I'll look into this

bash-5.2$ bash --version | head -n1
GNU bash, version 5.2.15(1)-release (i370-ibm-openedition)
bash-5.2$ cat <(date)
cat: /dev/fd/63: EDC5135I Not a directory.
looks good
bash-5.2$ echo <(date)
/dev/fd/63
bash-5.2$ wc -l <(ssh l98misdb491 "cat *Yum")
wc: /dev/fd/63: EDC5135I Not a directory.

We noticed there's an inconsistency on some of our z/OS machines /dev/fd is a character device and not a directory. So we made a change to use FIFO special files and to also tag them as such:
[ITODORO@ZOSCAN2B ~/zopen/prod/bash/bin]$  ls -lT <(date)
t ISO8859-1   T=on  prw-------   1 ITODORO  SUDOGRP        0 Mar 24 11:28 /tmp/sh-np.ghEFxQ
[ITODORO@ZOSCAN2B ~/zopen/prod/bash/bin]$ /home/itodoro/zopen/prod/coreutils/bin/cat <(date)
Fri Mar 24 11:28:48 EDT 2023
[ITODORO@ZOSCAN2B ~/zopen/prod/bash/bin]$ /bin/cat  <(date)
Fri Mar 24 11:28:55 EDT 2023

Are these the final results to be expected?  If so, I will close.
thanks
bash 5.2.15 (Build 799)
RC=(0) [SYSA] bash-5.2$ cat <(date)
Fri Mar 24 11:34:28 CDT 2023
RC=(0) [SYSA] bash-5.2$ echo <(date)
<EMAIL_ADDRESS>RC=(0) [SYSA] bash-5.2$ wc -l <(ssh l98misdb491 "cat *Yum")
4<EMAIL_ADDRESS>

Yes, for now at least. At some point I'll revisit the /dev/fd issue as it may result in better performance. Opened issue https://github.com/ZOSOpenTools/bashport/issues/59


[FAQ] understanding nearest value

Hi,
I am using leaflet-knn as below.
var myLines = [{
"type": "Point",
"coordinates": [[-105, 40], [-110, 45], [-101, 55]]
}];
var gj = L.geoJson(myLines);
var nearest = leafletKnn(gj).nearest(L.latLng(38, -78), 2);
console.log(nearest );
The result nearest coordinates are as shown in screenshot: [-105, 40],  [-101, 55]
Why it did not pick [-110, 45] ?
Since its lat value is less than 55.
Please help me to understand the behaviour.

Thanks.

var myLines = [{
"type": "Point",
"coordinates": [[-105, 40], [-110, 45], [-101, 55]]
}];

This calls the geometry a 'Point', but then provides multiple positions. A point is one position: please consult the geojson spec and provide an example that uses well-formed data.

My usecase is I want to load multiple lat/lng, so do I need to say then type as "Multipoint" ?

If you're trying to represent multiple points, use multiple points in a FeatureCollection.

Sir, my concern is about understanding output that I am getting right or wrong.

Indeed, but in order to diagnose an issue, I need to eliminate other errors. One can only really debug one issue at once, and only with complete information: if you're triggering a bug in another library by providing invalid data, then I'll end up spending more time trying to find a bug in leaflet-knn that isn't there. If you can provide a complete example of working code that demonstrates a potential but, please do so.

Closing: happy to diagnose this issue if given a complete working example. The provide example contains an error.


VSCode error reporting support stopped working in Version 2.1.0-dev.20160813

VSCode error reporting support stopped working in Version 2.1.0-dev.20160813
Here is the screenshot:

The same for Version 2.1.0-dev.20160812:

is this still an issue?

@mhegazy with latest @next version it is ok now, thanks


Fix: Allow private bolt-standard-configs

This fixes finding private dependencies for any bolt-standard-* configs.

LGTM


error while trying to start winpayloads

running kali rolling 2016.1
/Winpayloads# ./WinPayloads.py
Traceback (most recent call last):
File "./WinPayloads.py", line 2, in
from lib.main import *
File "/root/tools/Winpayloads/lib/main.py", line 19, in
from progress.bar import Bar
ImportError: No module named progress.bar

Ah, forgot to add that to the setup file, You just need to pip install progress

awesome its fixed much much thanks.
i found out i cant use dns for the ip why is that?

I can implement this when I have some time. It shouldn't take too long. But for now... Get the IP address from your DNS by either doing a nslookup or pinging the DNS

i have a dynamic ip address so it changes like once a day so i cant get persistence

Can you test the new dns payload, i don't have an environment to test it right now

yes i can, i was not home for 2 days...
On Mon, Mar 14, 2016 at 5:41 PM, Charlie Dean<EMAIL_ADDRESS>wrote:

Can you test the new dns payload, i don't have an environment to test it
right now
—
Reply to this email directly or view it on GitHub
https://github.com/Charliedean/Winpayloads/issues/5#issuecomment-196403588
.

How could i exploit a windows 7... is there a remote exploit or something
for windows 7? i tried everything from beef+metasploit-porershell
mitmf and everything is there some windows 7 bufferoverflow or sometihng?

root@vultr:~/Winpayloads# ./WinPayloads.py
Traceback (most recent call last):
File "./WinPayloads.py", line 2, in
from lib.main import *
File "/root/Winpayloads/lib/main.py", line 8, in
import blessed
ImportError: No module named blessed
root@vultr:~/Winpayloads#

./WinPayloads.py
Traceback (most recent call last):
File "./WinPayloads.py", line 2, in
from lib.main import *
File "/root/Winpayloads/lib/main.py", line 8, in
import blessed
ImportError: No module named blessed

./WinPayloads.py
Traceback (most recent call last):
File "./WinPayloads.py", line 2, in
from lib.main import *
File "/root/Winpayloads/lib/main.py", line 8, in
import blessed
ImportError: No module named blessed

pip install blessed


[Bug]: popover can not be showing

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
just balck scrrens
Expected Behavior
No response
What operating system are you seeing the problem on?
Linux
Relevant log output
bhvoiu

Anything else?
jjlojhpuoui
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@minikin Any suggestions?

For me it fixed when I created a seprated widget for the button to be shown.
I copied the same code from example but with no seprated button widget and it wasn't showing the dialog but when I made the button part another widget it appeared on the screen.
I think it's something related to the widget tree


Implement snyk-recommended security fixes.

DEVOPS PULL REQUEST
Related Issue

This addresses a multitude of existing issues in Snyk, including all "High"-priority issues that exist from package versions in the backend and frontend configurations.

Changes Proposed

Upgrades dependencies in multiple areas
Closes several holes in TF app service declarations
Closes a password authentication possibility in bastion VMs.

Additional Information

Additional fixes are forthcoming for high priority vulnerabilities found by static analysis.

Testing

Please deploy and verify functionality surrounding a standard workflow. At time of PR creation, no environment was available that had a full okta setup with proper facilities; I would like to ensure I'm not introducing any bugs with these changes.

Checklist for Primary Reviewer
Infrastructure

[ ] Consult the results of the terraform-plan job inside the "Terraform Checks" workflow run for this PR. Confirm that there are no unexpected changes!

Security

[ ] Changes with security implications have been approved by a security engineer (changes to  authentication, encryption, handling of PII, etc.)
[ ] Any dependencies introduced have been vetted and discussed

Cloud

[ ] Oncall has been notified if this change is going in after-hours
[ ] If there are changes that cannot be tested locally, this has been deployed to our Azure test, dev, or pentest environment for verification

I don't fully understand how to read the output of terraform_plan or what to expect, but I'm seeing some changes to other things than what was explicitly updated in your PR (like # module.metric_alerts.azurerm_monitor_diagnostic_setting.collect_appserviceconsolelogs will be updated in-place for example). what would generally be an expected change vs an unexpected change?

Good question! You don't traditionally have to worry about translating the terraform plan...that checklist item is primarily for a devops engineer to ensure that we aren't about to wipe out a change that someone made by hand in Azure without adding it as part of the codebase. Usually, the appserviceconsolelogs entry, items involving load balancers, and general app service information tend to change outside of Terraform's control. In this case, what we're looking for is making sure the changes I made to the TF files are reflected correctly.
I don't see any hand-rolled changes in here, so I think we're good to go!

Thank you all so much for helping me increase our security going into the long weekend! It's greatly appreciated! ❤


boundaryGap: [percent, percent] is not forced strictly

Version
4.6.0
Reproduction link
https://jsfiddle.net/9xr4ma21/
Steps to reproduce
When I define boundaryGap for x axis as [percent, percent] it's not applied exactly that way and the current algorithm adds further gaps only to arrive at the next tick values.
option = {
    "xAxis": {
        "show": true,
        "type": "value",
        "scale": true,
        "boundaryGap": ["1%", "1%"],
    },
    "yAxis": {
        "show": true,
    },
    "series": [{
        "type": "bar",
        "data": [
            ["2019", "600"],
            ["2020", "600"],
            ["2032", "600"],
        ]
    }]
};

What is expected?
In the JS fiddle I shared, I expect 2016 and 2034 values not to be on the x axis.
What is actually happening?
Current algorithm adds more space than I defined only to add 2016 and 2034 to the x axis.

Note: I'm not sure if this is a bug but I'm opening this issue because I can't find a fix for the case.
Note: #5458 is slightly related to this issue.

Hi, the ticks will be calculated to be nice numbers after added boundaryGap. So the boundaryGap is not an accurate value by default. If you want them to be accurate.  Try:
xAxis: {
  min: 'dataMin',
  max: 'dataMax'
}

I'm not sure what's your purpose of using boundaryGap. For the bar chart. I will suggest you use category type axis.

Thanks for the comment. If you go to the JSFiddle in the OP and remove boundaryGap line, you get this overflow:

dataMinand dataMax doesn't fix it. In order to fix it I wanted to use boundaryGap. Or maybe it should be fixed by the echarts algorithm? Here is another discussion on the issue. My humble opinion is, if there is no conflicting reason, boundaryGap should be absolute. Or maybe there may be a config option to make it absolute?

I will suggest you use category type axis.

Yes, bar charts are usually used with category axis, but surely there may be cases where it's better a value axis.


Error "Process finished with exit code 135 (interrupted by signal 7: SIGEMT)" when I import sam_model_registry, SamPredictor from segment_anything

Hi, what amazing work. However, when I try to use it in my project. I met some issues.
when I import your package,
from segment_anything import sam_model_registry, SamPredictor

The program is interrupted with this error:
Process finished with exit code 135 (interrupted by signal 7: SIGEMT)

My os system is ubuntu20.04 with cuda version12.1.
And, this is the package list from my venv
Package                  Version
------------------------ ----------
certifi                  2022.12.7
charset-normalizer       3.1.0
cmake                    3.26.3
coloredlogs              15.0.1
contourpy                1.0.7
cycler                   0.11.0
filelock                 3.12.0
flatbuffers              23.3.3
fonttools                4.39.3
humanfriendly            10.0
idna                     3.4
importlib-resources      5.12.0
Jinja2                   3.1.2
kiwisolver               1.4.4
lit                      16.0.1
MarkupSafe               2.1.2
matplotlib               3.7.1
mpmath                   1.3.0
networkx                 3.1
numpy                    1.24.2
nvidia-cublas-cu11       <IP_ADDRESS>
nvidia-cuda-cupti-cu11   11.7.101
nvidia-cuda-nvrtc-cu11   11.7.99
nvidia-cuda-runtime-cu11 11.7.99
nvidia-cudnn-cu11        <IP_ADDRESS>
nvidia-cufft-cu11        <IP_ADDRESS>
nvidia-curand-cu11       <IP_ADDRESS>
nvidia-cusolver-cu11     <IP_ADDRESS>
nvidia-cusparse-cu11     <IP_ADDRESS>
nvidia-nccl-cu11         2.14.3
nvidia-nvtx-cu11         11.7.91
onnx                     1.13.1
onnxruntime              1.14.1
opencv-python            <IP_ADDRESS>
packaging                23.1
Pillow                   9.5.0
pip                      20.0.2
pkg-resources            0.0.0
protobuf                 3.20.3
pycocotools              2.0.6
pyparsing                3.0.9
python-dateutil          2.8.2
requests                 2.28.2
segment-anything         1.0
setuptools               44.0.0
six                      1.16.0
sympy                    1.11.1
torch                    2.0.0
torchaudio               2.0.1
torchvision              0.15.1
triton                   2.0.0
typing-extensions        4.5.0
urllib3                  1.26.15
wheel                    0.40.0
zipp                     3.15.0

Looking forward to your help!

Fix eventually. The error happen because of torch version.
Torch =2.0 is not supportable.


Type hinting

I've added type hints to this package, so that static type checkers like mypy will work.
I thought that it would be a simple change, but it turned out to require reorganizing a lot of the package structure. I couldn't figure out a way to avoid doing this unfortunately.
I also altered the travis.yml to fix an unrelated build failure.

Hello @ckp95
That is a lot of work you have put in! I appreciate that.
Do we really need this? I am trying to keep the code base as simple as possible, to ensure
it works for anyone no matter what Python version there are using, and to keep
dependencies as few as possible. I am able to do this, since the underlying code
is simple and uses nothing more that arithmetic and trigonometric functions.
So my opinion is that we don't merge this PR.
I would like to hear your opinion before I close this.
Thanks again for your contribution.

There are no problems wrt Python versions -- I made sure to use the comment version of type hints so that it works on everything back to Python 2.7, you can see this in the CI tests.
It introduces no further external dependencies for users of the package. All the typing stuff comes from the standard library. There is the addition of mypy for the build/release process, but that will not affect users.
I think this is an improvement to the package, and will benefit projects that rely on jdcal as a dependency since IDEs can provide the correct type information, and static type checkers will behave properly.

FWIW, I'm in favor of seeing type hints added. Using the comment syntax ensures the code can remain compatible with legacy EOL Pythons.

@ckp95 @jdufresne
You have convinced me that this is a good thing!
@ckp95

Can you get the changes made in master since you cloned the repository
into this PR? This includes changes such as deleting travis,
setting up Github workflow, adding CONTRIBUTORS.txt and so on. This
should cause this PR to be tested on Github actions instead of travis
(at-least I think it will since actions are configured to run on PRs).

One Python question: looking at setup.py it seems that the typing backport
module will get installed for all Python versions. So, when importing typing,
in jdcal or other libraries the user has installed,  in Python versions that
already have typing in stdlib, which version of typing will be imported? And
could this cause any issues?

I will look at this on the weekend.

Ah I was actually wrong earlier about the lack of introduced dependencies, I forgot that the typing module isn't native to Python<3.4 and has to be installed. However I don't think this is a huge issue: first, it is maintained by the PSF so it could still be considered as part of the standard library but one step removed, and second, it is a dependency of many other packages so it is unlikely that users of old Python versions would not already have it installed. As for conflicts on newer versions: this is not a problem, as the docs for the typing module state:

NOTE: in Python 3.5 and later, the typing module lives in the stdlib, and installing this package has NO EFFECT, because stdlib takes higher precedence than the installation directory.

If you want, you should be able to avoid the typing dependency by using the if False: trick:
if False:
     from typing import Tuple

mypy understands this and will recognize the Tuple type but at runtime, the import is skipped. This is a common pattern when adding types to Python 2 code bases.


Multiprocessing fails for ImageDataLoaders with multiple inputs

Describe the bug
When using multiple inputs in a CNN, the Learner gets stuck at the start.
To Reproduce
Steps to reproduce the behavior:
d = pd.read_csv('../data/radiopaedia_cases.csv')
dls = ImageDataLoaders3D.from_df(d,
                                 fn_col = [0,1],
                                size_for_resampling = (112, 112, 20),
                                 label_col = 2, # in sample data 0: series, 1: segmentation mask, 2: random binary label
                                 bs = 2,
                                 val_bs = 2
                                 )

learn = cnn_learner_3d(dls, r3d_18, pretrained=False)

learn.fine_tune(1, 0.001)

Screenshots
Traceback shows that the model gets stuck at the dataloader,

Workaround until issue is fixed is to set num_workers=0, but this makes the training longer.

Setting sitk.ProcessObject_SetGlobalDefaultNumberOfThreads(1) solves the issue. it is now automatically set when loading data.


./configure: error: no /usr/build/ngnix-rtmp-module/config was found

Hi,
I met the problem when building nginx on my Mac Pro.
The nginx version I got is 1.4.1, and the ngnix-rtmp-module is  the latest from git.
Please kindly remind me what I may miss in the build steps.
Thanks
./configure --add-module=/usr/build/ngnix-rtmp-module --with-http_ssl_module
adding module in /usr/build/ngnix-rtmp-module
./configure: error: no /usr/build/ngnix-rtmp-module/config was found

check permissions of file "config"

I am using docker container for that
https://github.com/terbooter/LVK-server/blob/master/Dockerfile

Perhaps you not seeing the full path, go inside the module folder and to "readlink -f config" without the "" that should give you the full path to the config file, make sure you don't add config when adding the module just the path to the folder.

You need add the prefix path where you installed. such as --prefix=/usr/local/nginx
I solved the same problem by doing this.


bug fix - meta -> query

bugfix - when attempting to use list_by_query, meta is undefined.

Thanks for fixing!


Resizing causes svg attribute error

When it the Game view, trespassing the 1000px view-port threshold causes SVG attribute errors in the console.

Closed as old, and most likely not up to do date with recent code changes.


Clarify hotReloadCapable field

What does this PR do?
this PR clarifies the meaning of the HotReloadCapable field for a command.
Which issue(s) does this PR fix
https://github.com/redhat-developer/odo/issues/6697
PR acceptance criteria
Testing and documentation do not need to be complete in order for this PR to be approved. We just need to ensure tracking issues are opened.

Open new test/doc issues under the devfile/api repo
Check each criteria if:
There is a separate tracking issue. Add the issue link under the criteria
or
test/doc updates are made as part of this PR
If unchecked, explain why it's not needed

[ ] Unit/Functional tests

[ ] QE Integration test

[ ] Documentation

[ ] Client Impact

How to test changes / Special notes to the reviewer

/lgtm


nodePackages.vscode-json-languageserver: init at 1.3.1

Motivation for this change
Add vscode-json-languageserver as alternative to vscode-json-languageserver-bin which hasn't been updated in a while.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/287


New error found

[08/07/2024 8:10:15] Loading personal info from environment variables.
[08/07/2024 8:10:15] WARNING -> Invalid date in config.yml, using current date
[08/07/2024 8:10:15] Texas Scheduler v4.1.0 is starting...
[08/07/2024 8:10:15] Requesting Available Location....
[08/07/2024 8:10:15] No captcha token found! Will try to get one....
[08/07/2024 8:10:16] Refreshed auth token: mZqurXtDSzwu6nuC883rrjztZPwQod381Qxq08TFTFAobG0ApMIBI/ZZMxArRCGX48UiznUPM2SzizugoZyDbt5T28F5DKi71UUk2qF88uGJhK9rlsMnR9G2DJkxlsdE5xDkIVYBANd3vwDR0aWoW+mfobLq16nEorpj1Qxxj9pWf2dm0Z8nGBJdVYP9sPQQ
[08/07/2024 8:10:16] WARNING -> No location found for zipcode: 75010
/home/runner/texas-dps-scheduler-1/src/Client/index.ts:163
log.error(No Available location found! Nearest location is ${response[0].Distance} miles away! Please change your config and try again!);
^
TypeError: Cannot read properties of undefined (reading 'Distance')
at TexasScheduler.requestAvailableLocation (/home/runner/texas-dps-scheduler-1/src/Client/index.ts:163:87)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at async TexasScheduler.run (/home/runner/texas-dps-scheduler-1/src/Client/index.ts:68:9)
npm notice
npm notice New minor version of npm available! 10.5.0 -> 10.8.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.8.2
npm notice Run npm install -g<EMAIL_ADDRESS>to update!
npm notice

Try adding some of the other nearby zipcodes. I used 75075 and got same error, but when i added an additional zipcode (75080) it worked for me

Adding more zip codes will work. I will fix to show the error more useful

Just put in about 10 different zip codes it is still giving me the error.

@yusufqxzi does it show logs like this format ```
WARNING -> No location found for zipcode: 12345

Just put in about 10 different zip codes it is still giving me the error.

Hmm, I put a zipcode outside of my city and it worked just fine. But, zipcodes within my area was not working. Maybe have a a little distance or try the next town over.

Try putting the city name instead of the zipcode to get better results. Mentioned here


Initial commit.

Before submitting this PR, please make sure:

[ ] Your code builds clean without any errors or warnings
[ ] You are using approved title ("feat/", "fix/", "docs/", "refactor/")

A description of the changes proposed in the pull request:
Tests performed by the developer:
Tips for QA testing:

hi @Shannanigans, please check and follow the contribution guidelines and submit the PR when it's ready: https://hummingbot.org/developers/contributions/


fix(controller): prevent notifying listeners after being disposed

Fixes:
flutter: ERROR ubuntu_desktop_installer: Unhandled exception
_AssertionError: 'package:wizard_router/src/controller.dart': Failed assertion: line 119 pos 14: 'index < routeNames.length - 1': `Wizard.next()` called from the last route /security-key.
controller.dart:119
#0      _AssertionError._doThrowNew (dart:core-patch/errors_patch.dart:51:61)
#1      _AssertionError._throwNew (dart:core-patch/errors_patch.dart:40:5)
#2      WizardController._getNextRoute.nextRoute
controller.dart:119
#3      WizardController._getNextRoute
controller.dart:124
<asynchronous suspension>
#4      WizardController._loadRoute
controller.dart:26
<asynchronous suspension>
#5      WizardController.next
controller.dart:88
<asynchronous suspension>
#6      WizardButton.next.<anonymous closure>.<anonymous closure>
wizard_button.dart:87
<asynchronous suspension>

Close: #53

I thought everyone dislikes pulling in dependencies, especially for such small things. :) In this case, it's our own package though so perhaps not a big deal. Should we switch because it's definitely a cleaner solution?

I don't mind either way, maybe it helps promote safe_change_notifier if we use it here


Apple search ads?

Describe the bug
I believe this may be a documentation error / conflicting documentation
I am going through setup documention again while updating from 1.45.2 to 2.2.0 (while also switching from Cocoapods to SPM at the same time for integration)
I am encountering the following issue:
https://help.branch.io/developers-hub/docs/ios-full-reference#apple-search-ads
This document says i need to implement:

You must add the iAd.framework to your project to enable Apple Search Ad checking.
and Branch.getInstance().delayInitToCheckForSearchAds

Now I had Branch.getInstance().delayInitToCheckForSearchAds this as part of my setup for 1.45.2, however, i am now getting xcode error:
Value of type 'Branch' has no member 'delayInitToCheckForSearchAds'
Finally, in the instructions for SPM integration, there doesn't appear to be any mention of iAd.framework integration like the document above describes.
Steps to reproduce

Be integrated with 1.45.2 via Cocoapods
migrate to SPM integration and update to 2.2.0

Expected behavior
Clearer instructions or sdk notes about the function being deprecated or something
SDK Version
2.20
XCode Version
14.2 (14C18)
Device
NA
OS
NA
Additional Information/Context
No response

@mmdock Sorry about that, we had intended to remove that documentation about the old Apple Search Ads. I'll inform docs that it's still up.

Yes. Apple deprecated the old version and it doesn't return anything. The new version uses a token and s2s integration, so no delay is necessary with it.


Add social links.

Made minor (self contained) refactors to add social-links to header.

Migrated from google fonts to font-awesome (social icon support)
Slightly reordered header.

Code looks good. I don't see this in the deployed version though.

Lots of different deployed versions floating around...this must have gotten replaced by a parallel build :(


Error after upgrading to Preact 8

After updating Preact to 8.1.0 (I was on 6!), I'm seeing this error:
preact-router.es.js?b6d5:58 Uncaught TypeError: Cannot read property 'attributes' of null
    at pathRankSort (eval at <anonymous> (http://localhost:3000/bundle.js:148:1), <anonymous>:67:12)
    at Array.sort (native)
    at Router.getMatchingChildren (eval at <anonymous> (http://localhost:3000/bundle.js:148:1), <anonymous>:304:27)
    at Router.render (eval at <anonymous> (http://localhost:3000/bundle.js:148:1), <anonymous>:325:21)
    at renderComponent (eval at <anonymous> (http://localhost:3000/bundle.js:73:1), <anonymous>:263:38)
    at renderComponent (eval at <anonymous> (http://localhost:3000/bundle.js:73:1), <anonymous>:275:25)
    at renderComponent (eval at <anonymous> (http://localhost:3000/bundle.js:73:1), <anonymous>:275:25)
    at renderComponent (eval at <anonymous> (http://localhost:3000/bundle.js:73:1), <anonymous>:275:25)
    at setComponentProps (eval at <anonymous> (http://localhost:3000/bundle.js:73:1), <anonymous>:244:103)
    at buildComponentFromVNode (eval at <anonymous> (http://localhost:3000/bundle.js:73:1), <anonymous>:331:13)
pathRankSort @ preact-router.es.js?b6d5:58
getMatchingChildren @ preact-router.es.js?b6d5:295
render @ preact-router.es.js?b6d5:316
renderComponent @ VM2730:263
renderComponent @ VM2730:275
renderComponent @ VM2730:275
renderComponent @ VM2730:275
setComponentProps @ VM2730:244
buildComponentFromVNode @ VM2730:331
idiff @ VM2730:134
diff @ VM2730:110
render @ VM2730:363
(anonymous) @ index.jsx?a49b:25
(anonymous) @ bundle.js:873
__webpack_require__ @ bundle.js:20
(anonymous) @ bundle.js:66
(anonymous) @ bundle.js:69

I'm using version 2.5.1 of preact-router. Has anyone seen this issue before?
Thanks!

I noticed that this is only an issue when adding conditional rules. This works:
return (
  <Router history={history}>
    <HomeView path="/" authenticate />
  </Router>
)

This doesn't:
return (
  <Router history={history}>
    {condition &&
        <HomeView path="/" authenticate />
    }
  </Router>
)

Not really an issue as I can get around that on my app, so feel free to close, but here it is in case someone else faces the same problem.

I've seen this Uncaught TypeError: Cannot read property 'attributes' of null with preact 8.1.0 on other packages (react-tooltip), but not with my usage of preact-router so far. @eduardoboucas

Hmm. That should have been fixed by c4ee6c8. Must have missed a case.

with preact 8.1 https://github.com/developit/preact/issues/751 it tends to have unexpected children,
which is causing the vNode here to be null/undefined https://github.com/developit/preact-router/blob/master/src/index.js#L215 which in turn causes the error mentioned above.
There is no fix for that yet. the link pasted above https://github.com/developit/preact-router/commit/c4ee6c8829af89d7d57c437a05c022d3055dca41 does not fix it since it accesses vNode.attributes > null.attributes

Can someone suggest a work-around for not rendering/hiding routes until this issue is resolved.

One solution would be to save the routes into an array and concat them on the condition.
const routesA = [
	(<PageA ...>),
	(<PageB ...>)
];

const routesB = [
	(<PageC ...>)
];

const routes = routeBAllowed ? routesA.concat(routesB) : routesA;

<Router>
	{...routes}
</Router>


document all RPC calls

I wish to set rpcwhitelist for only certain calls to the sparrow rpc user.
Can you please document all RPC calls so I can use as reference?

Also please consider separating the wallet commands of watching-only vs hot wallets, but this is not necessary, I can check manually, would just be good if separated.

Can you please document all RPC calls so I can use as reference?

Simplest way to get this info is to turn on DEBUG logging  (-l DEBUG) and filtering for the relevant bwt bitcoincore_rpc logging lines. See FAQ for details on command line arguments.
e.g.
DEBUG bitcoincore_rpc                   > JSON-RPC request: estimatesmartfee [1]
DEBUG bitcoincore_rpc                   > JSON-RPC request: getrawmempool [true]
DEBUG bitcoincore_rpc                   > JSON-RPC request: getmempoolinfo []

I mean, I've already been doing that, the problem is I don't want to miss anything and that method is prone to mistakes as if I don't do ever wallet action, maybe one command is not included in my list.
I've already tried that with Fulcrum and missed some commands. It also seems more logical to connect to electrum server as it requires less RPC calls and don't require wallet RPC calls.
Just to add to the debuggining process, on bitcoin.conf user debug=rpc, it shows accepted and denied calls per user.

I'm a little confused - Sparrow does not connect to Bitcoin Core if an Electrum server like Fulcrum is configured. The commands that Fulcrum issues to Bitcoin Core are of course specific to that project, not Sparrow.
Regarding Bitcoin Core connections via BWT, as I'm not the author of that project I can't offer better guidance than what I've suggested above, other than a search through https://github.com/bwt-dev/bwt for calls using the rust-bitcoincore-rpc library.

I'm a little confused - Sparrow does not connect to Bitcoin Core if an Electrum server like Fulcrum is configured. The commands that Fulcrum issues to Bitcoin Core are of course specific to that project, not Sparrow.

I was comparing RPC calls of connecting Sparrow to an electrum server, which then already has a limited number of calls that don't involve wallet commands, to connecting Sparrow directly to bitcoin core rpc, which then has more commands that need to be allowed.

Regarding Bitcoin Core connections via BWT, as I'm not the author of that project I can't offer better guidance than what I've suggested above, other than a search through https://github.com/bwt-dev/bwt for calls using the rust-bitcoincore-rpc library.

Closing the issue as completed, will see what I can get from upstream bwt.


Wrapping an account with Box causes a compilation error when using the owner constraint

Description
The following code fails to compile:
#[derive(Accounts)]
pub struct MultisigCreateTransaction<'info> {
	pub multisig: Box<Account<'info, MultisigData>>,
	#[account(zero, signer, owner = program.key())]
	pub transaction: Box<Account<'info, MultisigTransactionData>>,
	pub proposer: Signer<'info>,
	pub program: Program<'info, Launchpad>,
}

The error produced is as follows.
the trait bound `std::boxed::Box<anchor_lang::prelude::Account<'_, multisig::MultisigTransactionData>>: derive_more::AsRef<anchor_lang::prelude::AccountInfo<'_>>` is not satisfied
the trait `derive_more::AsRef<anchor_lang::prelude::Account<'_, multisig::MultisigTransactionData>>` is implemented for `std::boxed::Box<anchor_lang::prelude::Account<'_, multisig::MultisigTransactionData>>`
for that trait implementation, expected `anchor_lang::prelude::Account<'_, multisig::MultisigTransactionData>`, found `anchor_lang::prelude::AccountInfo<'_>`

The problem is caused by the derive(Accounts) macro which produces the following for both boxed and unboxed values.
let my_owner = AsRef::<AccountInfo>::as_ref(&transaction).owner;
let owner_address = launchpad_program.key();
if my_owner != &owner_address {
	return Err(anchor_lang::error::Error::from(
		anchor_lang::error::ErrorCode::ConstraintOwner,
	)
	.with_account_name("transaction")
	.with_pubkeys((*my_owner, owner_address)));
}

A fix would be to generate different code if the account is wrapped with Box.
Changing the first line of the macro output to the following resolves the issue.
let my_owner = AsRef::<AccountInfo>::as_ref(&*ctx.accounts.transaction).owner;

Current Workaround
For those looking for a temporary workaround, you can use the constraint in the following way to replicate the behaviour.
#[derive(Accounts)]
pub struct MultisigCreateTransaction<'info> {
	pub multisig: Box<Account<'info, MultisigData>>,
	#[account(
		zero,
		signer,
-		owner = program.key()
+ 		constraint = *transaction.to_account_info().owner = program.key()
	)]
    #[account(zero, signer, constraint = program.key())]
	pub transaction: Box<Account<'info, MultisigTransactionData>>,
	pub proposer: Signer<'info>,
	pub program: Program<'info, Launchpad>,
}

Fixed the compilation error in https://github.com/coral-xyz/anchor/pull/3087. However, note that using the owner constraint with the Account type is redundant because Account<T> already checks T::owner() == account.owner.


Openapi

Coverage remained the same at 73.077% when pulling 5f0d8d9c611ee998044bb221d4dba6eac2ec4b2a on openapi into c5810ade473d44ad4bf87ef78352fe8a6fed190b on master.


Fix External Controller

Once an external controller was exiting the INFO: 'extern' controller exited successfully. message was never displayed, it was not possible to re-launch the external controller and the simulation was blocked (because waiting for ht controller).

:+1:


Confusing behavior in get_lbry_file_by_uri()

This problem was introduced in https://github.com/lbryio/lbry/pull/485
Let's say you have two files (A and B) associated with two different claims for the same name "test". File A is currently associated with the winning claim. You call get_lbry_file_by_uri() and you get file A. Someone overtakes name "test" with some random file that you have not downloaded. You call get_lbry_file_by_uri() and you will either get file A or B depending on which one shows up first in the file manager. This is a very arbitrary behavior that's going to confuse the user.
We need a separate function, something like get_lbry_file_by_name() that does not attempt to resolve the name through the blockchain, an just looks up the name in the file manager. get_lbry_file_by_uri() should be for the winning claim, and if you don't have the winning claim it should return nothing.
We should also return a list of files that is associated with a description whether it be sd_hash, name, or filename, instead of returning whatever is the first one in the file manager.

Work in progress: https://github.com/lbryio/lbry/pull/492

We need a separate function, something like get_lbry_file_by_name() that does not attempt to resolve the name through the blockchain

We can get rid of the name resolution in the file manager altogether - it was only necessary to populate the metadata, which is stored in the new db. In addition, the db tracks the state of the associated claim (whether it be active but not winning, active and winning, pending, abandoned or updated over).

We should also return a list of files that is associated with a description whether it be sd_hash, name, or filename, instead of returning whatever is the first one in the file manager.

Will do - I think the json returned should also include a status code for the state of the associated claim (from the db).

Closing as fixed in https://github.com/lbryio/lbry/pull/512


PHP 8.4 support?

I would be happy to add PHP 8.4 support, but there are issues.
First, we would need to drop support for any version below 7.1, since that is when nullable types were introduced.  There are only two minor changes to support PHP 8.4, constructors in Basic and File need nullable types. Usage of PHP below 7.1 is virtual non-existant. Also those users can continue to use the existing version.
Also I think we should convert to GitHub Actions and drop Travis CI.
Let me know if this makes sense.

Makes sense, please do! You can drop all suport for 7.*, it's outdated anyways.

Awesome. Thanks. So many maintainers are not responding.

I am getting this when running tests in two places:
Error: Call to undefined method Unit\FustyRequestTest::getMock()

Any ideas what I should replace this with?  I don't see it referenced in the git history either, so not sure how it ever worked.

Apparently getMock is from PHPUnit, but now called createMock.  Closing as there is now a PR to review.


Explore adding tests for riders index

This is a draft PR on exploring the start of what additional live view tests could look like. I'm not sure how valuable testing certain functionality is for LiveView as I don't want to make refactoring too much of a pain where it might feel like you have to maintain a lot of tests as you go (or end up deleting them.)
I used the riders page as an example demo since it seems straight-foward. The test I added:

updated the table core component to be able to take a row_class, so that we can...
enable getting those values  with Floki (so, technically could also use a data-test-* html attribute instead of a class if desired)
wrote a test that checks that pagination is working as expected.

Some other example tests I imagine would be useful:

test that multiple users can be selected and then when navigating to "bulk message" they are all listed in the modal
test that clicking on a user takes you to the user page
test the table can sort properly by sortable headings

Let me know if you think this would be useful!

Ready for re-review


repo is over 100 MB of Go source code and growing

For vgo I put in a limit of 100 MB of uncompressed source code for any module, thinking surely that would be plenty. (There must be some limit, of course, or else we fill people's disks when receiving a zip bomb.)
It looks like this project recently crossed the 100 MB line, just for the go sources in it:
$ git clone https://github.com/Azure/azure-sdk-for-go
$ cd azure-sdk-for-go
$ ls -lR | grep '\.go$' | awk '{s+=$5}END{print s}'
116335208
$

Sizes for recent major versions:
v14.0.0 66,432,773
v15.0.0 80,010,402
v16.0.0 114,745,301
v17.0.0 116,277,454

I am going to raise the limit to 500 MB but I wanted to file this issue to let you know about the problem, so that you can look to see if the rate of growth here is really intentional and/or think about whether to break this repo into multiple modules.

Thanks for letting us know @rsc. This will be a consideration for us as we adopt modules here.

Howdy @rsc, thanks for thinking of us!
We've been thinking about splitting up this repository for sometime, but have balked at the overhead of managing a repository per Azure Resource Provider. Modules present a solution that we're excited about. Tentatively, we intend on shipping each of the subfolders in "services" and "profiles" as its own module with its own semver.

related: https://github.com/golang/vgo/commit/0cf06bb651c56f86ec7b7685f39092ddb7daba39

Work to split each RP/API version tuple into modules is in progress, tracked in https://github.com/Azure/azure-sdk-for-go/issues/2993

x-post: https://github.com/Azure/azure-sdk-for-go/issues/18209

Indeed. If it was thought that 100MB was too big 3 years ago, how did it end up at 512MB+ today?


Migrate machine api libraries to openshift/api

What this PR does / why we need it:
This PR aligns with the work to move machine api libraries to openshift/api. This work updates the machine-api-operator dependency, removes AWS and Azure dependencies, and simplifies the go.mod.
Special notes for your reviewer:
0 code changes introduced. Migrating libraries to openshift/api in order to clean up go.mod dependencies and align with the latest branches.
Release note:
Migrating machine api libraries to openshift/api

Follow up to https://github.com/openshift/cluster-api-provider-openstack/pull/206

I can't remember what state the e2e tests are in, but basically as long as this compiles it
/lgtm

I can't remember what state the e2e tests are in, but basically as long as this compiles it
/lgtm

They do not work yet


Front Matter doesn't hot reload

The front matter of a markdown file doesn't hot reload when running nuxt in dev mode.
For example if I have post.md
---
title: example
---

# Title

Lorem Ipsum

and change the title field in the front matter, it will not update on the website without restarting the development server.

I can confirm this. Updating the content will reload but updating the frontmatter doesn't.

Hopefully, this should be an easy fix by using the watch property.


Impossible to configure shm_size when launching a CommandJob with AzureML SDK v2

Describe the bug
I get an Validation error when I want to launch a CommandJob with a custom shm_size
Related command
az ml job create --file file.yaml
Errors
Configured default 't-bs-mf-explore-iris2-phd' for arg resource_group_name
Configured default 'aml-dcy-int-iris2-phd' for arg workspace_name
Met error <class 'marshmallow.exceptions.ValidationError'>:Validation for CommandJobSchema failed:
{
"resources": {
"shm_size": [
"Unknown field."
]
}
}
If you are trying to configure a job that is not of type command, please specify the correct job type in the 'type' property.
For a more detailed breakdown of the CommandJob schema, please see: https://aka.ms/ml-cli-v2-job-command-yaml-reference.
The easiest way to author a specification file is using IntelliSense and auto-completion Azure ML VS code extension provides: https://code.visualstudio.com/docs/datascience/azure-machine-learning
To set up: https://docs.microsoft.com/azure/machine-learning/how-to-setup-vs-code
Please check log in debug mode for more details.
Command ran in 2.107 seconds (init: 0.441, invoke: 1.666)
Issue script & Debug output
Traceback (most recent call last):
File "/opt/az/extensions/ml/azext_mlv2/manual/vendored_curated_sdk/azure/ai/ml/entities/_util.py", line 143, in load_from_dict
return schema(context=context).load(data, **kwargs)
File "/anaconda/envs/torch12/lib/python3.8/site-packages/marshmallow/schema.py", line 722, in load
return self._do_load(
File "/anaconda/envs/torch12/lib/python3.8/site-packages/marshmallow/schema.py", line 909, in _do_load
raise exc
marshmallow.exceptions.ValidationError: {'resources': {'shm_size': ['Unknown field.']}}
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/az/extensions/ml/azext_mlv2/manual/custom/job.py", line 60, in ml_job_create
job = load_job(path=file, params_override=params_override)
File "/opt/az/extensions/ml/azext_mlv2/manual/vendored_curated_sdk/azure/ai/ml/entities/_load_functions.py", line 74, in load_job
return load_common(Job, path, **kwargs)
File "/opt/az/extensions/ml/azext_mlv2/manual/vendored_curated_sdk/azure/ai/ml/entities/_load_functions.py", line 59, in load_common
return cls._load(data=yaml_dict, yaml_path=path, params_override=params_override, **kwargs)
File "/opt/az/extensions/ml/azext_mlv2/manual/vendored_curated_sdk/azure/ai/ml/entities/_job/job.py", line 235, in _load
return job_type._load_from_dict(
File "/opt/az/extensions/ml/azext_mlv2/manual/vendored_curated_sdk/azure/ai/ml/entities/_job/command_job.py", line 166, in _load_from_dict
loaded_data = load_from_dict(CommandJobSchema, data, context, additional_message, **kwargs)
File "/opt/az/extensions/ml/azext_mlv2/manual/vendored_curated_sdk/azure/ai/ml/entities/_util.py", line 146, in load_from_dict
raise ValidationError(decorate_validation_error(schema, pretty_error, additional_message))
marshmallow.exceptions.ValidationError: Validation for CommandJobSchema failed:
{
"resources": {
"shm_size": [
"Unknown field."
]
}
}
If you are trying to configure a job that is not of type command, please specify the correct job type in the 'type' property.
For a more detailed breakdown of the CommandJob schema, please see: https://aka.ms/ml-cli-v2-job-command-yaml-reference.
The easiest way to author a specification file is using IntelliSense and auto-completion Azure ML VS code extension provides: https://code.visualstudio.com/docs/datascience/azure-machine-learning
To set up: https://docs.microsoft.com/azure/machine-learning/how-to-setup-vs-code
cli: None
cli: Traceback (most recent call last):
File "/opt/az/extensions/ml/azext_mlv2/manual/vendored_curated_sdk/azure/ai/ml/entities/_util.py", line 143, in load_from_dict
return schema(context=context).load(data, **kwargs)
File "/anaconda/envs/torch12/lib/python3.8/site-packages/marshmallow/schema.py", line 722, in load
return self._do_load(
File "/anaconda/envs/torch12/lib/python3.8/site-packages/marshmallow/schema.py", line 909, in _do_load
raise exc
marshmallow.exceptions.ValidationError: {'resources': {'shm_size': ['Unknown field.']}}
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/az/extensions/ml/azext_mlv2/manual/custom/job.py", line 60, in ml_job_create
job = load_job(path=file, params_override=params_override)
File "/opt/az/extensions/ml/azext_mlv2/manual/vendored_curated_sdk/azure/ai/ml/entities/_load_functions.py", line 74, in load_job
return load_common(Job, path, **kwargs)
File "/opt/az/extensions/ml/azext_mlv2/manual/vendored_curated_sdk/azure/ai/ml/entities/_load_functions.py", line 59, in load_common
return cls._load(data=yaml_dict, yaml_path=path, params_override=params_override, **kwargs)
File "/opt/az/extensions/ml/azext_mlv2/manual/vendored_curated_sdk/azure/ai/ml/entities/_job/job.py", line 235, in _load
return job_type._load_from_dict(
File "/opt/az/extensions/ml/azext_mlv2/manual/vendored_curated_sdk/azure/ai/ml/entities/_job/command_job.py", line 166, in _load_from_dict
loaded_data = load_from_dict(CommandJobSchema, data, context, additional_message, **kwargs)
File "/opt/az/extensions/ml/azext_mlv2/manual/vendored_curated_sdk/azure/ai/ml/entities/_util.py", line 146, in load_from_dict
raise ValidationError(decorate_validation_error(schema, pretty_error, additional_message))
marshmallow.exceptions.ValidationError: Validation for CommandJobSchema failed:
{
"resources": {
"shm_size": [
"Unknown field."
]
}
}
If you are trying to configure a job that is not of type command, please specify the correct job type in the 'type' property.
For a more detailed breakdown of the CommandJob schema, please see: https://aka.ms/ml-cli-v2-job-command-yaml-reference.
The easiest way to author a specification file is using IntelliSense and auto-completion Azure ML VS code extension provides: https://code.visualstudio.com/docs/datascience/azure-machine-learning
To set up: https://docs.microsoft.com/azure/machine-learning/how-to-setup-vs-code
cli.azure.cli.core.azclierror: Traceback (most recent call last):
File "/opt/az/extensions/ml/azext_mlv2/manual/vendored_curated_sdk/azure/ai/ml/entities/_util.py", line 143, in load_from_dict
return schema(context=context).load(data, **kwargs)
File "/anaconda/envs/torch12/lib/python3.8/site-packages/marshmallow/schema.py", line 722, in load
return self._do_load(
File "/anaconda/envs/torch12/lib/python3.8/site-packages/marshmallow/schema.py", line 909, in _do_load
raise exc
marshmallow.exceptions.ValidationError: {'resources': {'shm_size': ['Unknown field.']}}
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/az/extensions/ml/azext_mlv2/manual/custom/job.py", line 60, in ml_job_create
job = load_job(path=file, params_override=params_override)
File "/opt/az/extensions/ml/azext_mlv2/manual/vendored_curated_sdk/azure/ai/ml/entities/_load_functions.py", line 74, in load_job
return load_common(Job, path, **kwargs)
File "/opt/az/extensions/ml/azext_mlv2/manual/vendored_curated_sdk/azure/ai/ml/entities/_load_functions.py", line 59, in load_common
return cls._load(data=yaml_dict, yaml_path=path, params_override=params_override, **kwargs)
File "/opt/az/extensions/ml/azext_mlv2/manual/vendored_curated_sdk/azure/ai/ml/entities/_job/job.py", line 235, in _load
return job_type._load_from_dict(
File "/opt/az/extensions/ml/azext_mlv2/manual/vendored_curated_sdk/azure/ai/ml/entities/_job/command_job.py", line 166, in _load_from_dict
loaded_data = load_from_dict(CommandJobSchema, data, context, additional_message, **kwargs)
File "/opt/az/extensions/ml/azext_mlv2/manual/vendored_curated_sdk/azure/ai/ml/entities/_util.py", line 146, in load_from_dict
raise ValidationError(decorate_validation_error(schema, pretty_error, additional_message))
marshmallow.exceptions.ValidationError: Validation for CommandJobSchema failed:
{
"resources": {
"shm_size": [
"Unknown field."
]
}
}
If you are trying to configure a job that is not of type command, please specify the correct job type in the 'type' property.
For a more detailed breakdown of the CommandJob schema, please see: https://aka.ms/ml-cli-v2-job-command-yaml-reference.
The easiest way to author a specification file is using IntelliSense and auto-completion Azure ML VS code extension provides: https://code.visualstudio.com/docs/datascience/azure-machine-learning
To set up: https://docs.microsoft.com/azure/machine-learning/how-to-setup-vs-code
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/anaconda/envs/torch12/lib/python3.8/site-packages/knack/cli.py", line 233, in invoke
cmd_result = self.invocation.execute(args)
File "/anaconda/envs/torch12/lib/python3.8/site-packages/azure/cli/core/commands/init.py", line 663, in execute
raise ex
File "/anaconda/envs/torch12/lib/python3.8/site-packages/azure/cli/core/commands/init.py", line 726, in _run_jobs_serially
results.append(self._run_job(expanded_arg, cmd_copy))
File "/anaconda/envs/torch12/lib/python3.8/site-packages/azure/cli/core/commands/init.py", line 697, in _run_job
result = cmd_copy(params)
File "/anaconda/envs/torch12/lib/python3.8/site-packages/azure/cli/core/commands/init.py", line 333, in call
return self.handler(*args, **kwargs)
File "/anaconda/envs/torch12/lib/python3.8/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
return op(**command_args)
File "/opt/az/extensions/ml/azext_mlv2/manual/custom/job.py", line 77, in ml_job_create
log_and_raise_error(err, debug)
File "/opt/az/extensions/ml/azext_mlv2/manual/custom/raise_error.py", line 117, in log_and_raise_error
raise cli_error
knack.util.CLIError: Met error <class 'marshmallow.exceptions.ValidationError'>:Validation for CommandJobSchema failed:
{
"resources": {
"shm_size": [
"Unknown field."
]
}
}
If you are trying to configure a job that is not of type command, please specify the correct job type in the 'type' property.
For a more detailed breakdown of the CommandJob schema, please see: https://aka.ms/ml-cli-v2-job-command-yaml-reference.
The easiest way to author a specification file is using IntelliSense and auto-completion Azure ML VS code extension provides: https://code.visualstudio.com/docs/datascience/azure-machine-learning
To set up: https://docs.microsoft.com/azure/machine-learning/how-to-setup-vs-code
Please check log in debug mode for more details.
cli.azure.cli.core.azclierror: Met error <class 'marshmallow.exceptions.ValidationError'>:Validation for CommandJobSchema failed:
{
"resources": {
"shm_size": [
"Unknown field."
]
}
}
If you are trying to configure a job that is not of type command, please specify the correct job type in the 'type' property.
For a more detailed breakdown of the CommandJob schema, please see: https://aka.ms/ml-cli-v2-job-command-yaml-reference.
The easiest way to author a specification file is using IntelliSense and auto-completion Azure ML VS code extension provides: https://code.visualstudio.com/docs/datascience/azure-machine-learning
To set up: https://docs.microsoft.com/azure/machine-learning/how-to-setup-vs-code
Please check log in debug mode for more details.
az_command_data_logger: Met error <class 'marshmallow.exceptions.ValidationError'>:Validation for CommandJobSchema failed:
{
"resources": {
"shm_size": [
"Unknown field."
]
}
}
If you are trying to configure a job that is not of type command, please specify the correct job type in the 'type' property.
For a more detailed breakdown of the CommandJob schema, please see: https://aka.ms/ml-cli-v2-job-command-yaml-reference.
The easiest way to author a specification file is using IntelliSense and auto-completion Azure ML VS code extension provides: https://code.visualstudio.com/docs/datascience/azure-machine-learning
To set up: https://docs.microsoft.com/azure/machine-learning/how-to-setup-vs-code
Please check log in debug mode for more details.
cli.knack.cli: Event: Cli.PostExecute [<function AzCliLogging.deinit_cmd_metadata_logging at 0x7fd1e33cb040>]
az_command_data_logger: exit code: 1
cli.main: Command ran in 1.322 seconds (init: 0.568, invoke: 0.753)
telemetry.main: Begin splitting cli events and extra events, total events: 1
telemetry.client: Accumulated 0 events. Flush the clients.
telemetry.main: Finish splitting cli events and extra events, cli events: 1
telemetry.save: Save telemetry record of length 4340 in cache
telemetry.check: Returns Positive.
telemetry.main: Begin creating telemetry upload process.
telemetry.process: Creating upload process: "/anaconda/envs/torch12/bin/python /anaconda/envs/torch12/lib/python3.8/site-packages/azure/cli/telemetry/init.py /home/azureuser/.azure"
telemetry.process: Return from creating process
telemetry.main: Finish creating telemetry upload process.
Expected behavior
The job should be launched
Environment Summary
azure-cli                         2.50.0
core                              2.50.0
telemetry                          1.0.8
Extensions:
ml                                 2.5.0
Dependencies:
msal                              1.22.0
azure-mgmt-resource             23.1.0b2
Python location '/anaconda/envs/torch12/bin/python'
Extensions directory '/opt/az/extensions'
Python (Linux) 3.8.15 (default, Nov 24 2022, 15:19:38)
[GCC 11.2.0]
Legal docs and information: aka.ms/AzureCliLegal
Additional context
$schema: https://azuremlschemas.azureedge.net/latest/commandJob.schema.json

experiment_name: model_run_semantic_v2
display_name: DUAT_model_run

resources:
  shm_size: 28g

environment_variables:
  DATASET_MOUNT_CACHE_SIZE: '50 GB'
  DATASET_MOUNT_FILE_CACHE_PRUNE_TARGET: '0'

code: ../../../../ # Relative from yaml file in order to get the root directory.
command: >-
  python pipelines/scripts/04_model_run_segmentation.py
  --input_data ${{inputs.input_data}}
  --input_labels ${{inputs.input_labels}}
  --input_model_root ${{inputs.input_model_root}}
  --pretrained_model_path ${{inputs.pretrained_model_path}}
  --label_version ${{inputs.label_version1}}
  --n_channels ${{inputs.n_channels}}
  --zones_camera ${{inputs.zones_cameras}}
  --separate_all_cameras ${{inputs.separate_all_cameras}}
  --log_dir ${{outputs.output_dir}}
  --alpha_fce ${{inputs.alpha_fce}}
  --input_height ${{inputs.input_height}}
  --input_width ${{inputs.input_width}}
  --detection_mode ${{inputs.detection_mode}}
  --include_metadata ${{inputs.include_metadata}}
  --model_seg_type ${{inputs.model_seg_type}}
  --lb_model_run_name ${{inputs.lb_model_run_name}}
  --tyre_type ${{inputs.tyre_type}}
  --usines ${{inputs.usine1}}
  --dataset_mode ${{inputs.dataset_mode}}
  --thresholds_model_run ${{inputs.thresholds_model_run}}
  --input_model_segmentation_path ${{inputs.input_model_segmentation_path}}
  --lb_model_name ${{inputs.lb_model_name}}

inputs:
  input_data:
    type: uri_folder
    path: azureml://datastores/ara_b2b_qualif_data/paths/
    mode: ro_mount

  input_labels:
    type: uri_folder
    path: azureml://datastores/ara_b2b_qualif_label/paths/
    mode: ro_mount

  input_model_root:
    type: uri_folder
    path: azureml://datastores/workspaceblobstore/paths/
    mode: ro_mount

outputs:
  output_dir:
    type: uri_folder
    path: azureml://datastores/workspaceblobstore/paths/semantic_seg
    mode: rw_mount

environment: azureml:torch@latest
compute: azureml:T4-TC-light-illimited

I have removed personnal arguments

Thank you for opening this issue, we will look into it.

@tmignot63 Thanks for reaching out to us and reporting this issue. Could you please update your ml extension by running the below command and check if that helps ?

az extension update -n ml

Awaiting your reply.

Hello,
It's working now with the update,
many thanks,
Thomas
Le ven. 28 juil. 2023, 06:30, navba-MSFT @.***> a
écrit :

@tmignot63 https://github.com/tmignot63 Thanks for reaching out to us
and reporting this issue. Could you please update your ml extension by
running the below command and check if that helps ?
az extension update -n ml
Awaiting your reply.
—
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-cli-extensions/issues/6571#issuecomment-1654984988,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APH6W6BM22CUMAWCPUJSG73XSM56TANCNFSM6AAAAAA22KKRR4
.
You are receiving this because you were mentioned.Message ID:
@.***>

@tmignot63 Thanks for getting back. We will now proceed with closure of this GitHub issue. If you need any further assistance on this issue in future, please feel free to reopen this thread. We would be happy to help.


ARTEMIS-4502 Support core messages crossing broker connection links

Allow for core messages to be tunneled over broker connection links used for AMQP Federation and for broker mirroring. This eliminates the need to convert from Core to AMQP and from loading core large messages fully into memory for that conversion.

LGTM


ARKit.Model is not working

I successfully added art.scnassets folder and added ship.scn image. But image doesn't appeared in the app. Please explain the steps to add images. And also to add .dae image file

What file path did you use in the model definition. It needs to include the folder i.e "i.e: file:'art.scnassets/file_name.scn',"

I am having the same issue, I am using the same path: art.scnassets/ship.scn
And I added the folder and file under my iOS App

Turns out the code in the example does not work, but this one does:
<ARKit.Model
model={{ file: 'art.scnassets/iphone6.dae' }}
position={{ x: 0, y: -2.0, z: -3.0 }}
eulerAngles={{ x: 0, y: Math.PI * 2.0, z: 0 }}
/>


NO-ISSUE: Synchronize From Upstream Repositories

The downstream repository has been updated through the following upstream commit:

Date
Commit
Author
Message

2024-08-02 20:54:29
operator-framework/operator-controller@cb9ea00
Joe Lanford
helm: use chunking release driver in systemNamespace (#1057)

upstream commit list

The vendor/ directory has been updated and the following commits were carried:

Date
Commit
Author
Message

2024-08-02 00:02:23
openshift/operator-framework-operator-controller@3928ed0
dtfranz
UPSTREAM: : Add OpenShift specific files

2024-08-02 00:02:24
openshift/operator-framework-operator-controller@ebee561
Alexander Greene
UPSTREAM: : Drop commitchecker

2024-08-02 00:02:25
openshift/operator-framework-operator-controller@6f9fe2d
AOS Automation Release Team
UPSTREAM: : Updating ose-olm-operator-controller-container image to be consistent with ART Reconciling with https://github.com/openshift/ocp-build-data/tree/4022cd290f00a44d667dda03f2d78d84a488c7ed/images/ose-olm-operator-controller.yml

2024-08-02 00:02:25
openshift/operator-framework-operator-controller@bbd6a7f
Mikalai Radchuk
UPSTREAM: : update owners

2024-08-02 00:02:26
openshift/operator-framework-operator-controller@37cd896
Brett Tofel
UPSTREAM: : Add pointer to tooling README

2024-08-02 00:02:27
openshift/operator-framework-operator-controller@b399f1b
Mikalai Radchuk
UPSTREAM: : Disable Validating Admission Policy APIs downstream

2024-08-02 00:02:27
openshift/operator-framework-operator-controller@7de1ca0
AOS Automation Release Team
UPSTREAM: : Updating ose-olm-operator-controller-container image to be consistent with ART for 4.16 Reconciling with https://github.com/openshift/ocp-build-data/tree/6250d54c4686a708ca5985afb73080e8ca9a1f7f/images/ose-olm-operator-controller.yml

2024-08-02 00:02:28
openshift/operator-framework-operator-controller@457ba8a
Mikalai Radchuk
UPSTREAM: : Enable Validating Admission Policy APIs downstream

2024-08-02 00:02:29
openshift/operator-framework-operator-controller@4746830
Ilias Rinis
UPSTREAM: : manifests: set required-scc for openshift workloads

2024-08-02 00:02:30
openshift/operator-framework-operator-controller@df26eb9
AOS Automation Release Team
UPSTREAM: : Updating ose-olm-operator-controller-container image to be consistent with ART for 4.17 Reconciling with https://github.com/openshift/ocp-build-data/tree/4c1326094222f9209876f06833179a1b9178faf7/images/ose-olm-operator-controller.yml

2024-08-02 00:02:30
openshift/operator-framework-operator-controller@1e7a713
everettraven
UPSTREAM: : add everettraven to approvers+reviewers

2024-08-02 00:02:31
openshift/operator-framework-operator-controller@32bbcdf
everettraven
UPSTREAM: : add openshift kustomize overlay

This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.
/cc @openshift/openshift-team-operator-runtime
/cc @openshift/openshift-team-operator-ecosystem

/approve
/lgtm


Added qr code to pr comments

Description
I wrote an additional script to the .yml file that publishes our app to an Expo CDN and then comments a QR code into the PR. This makes it easier to test the app manually on code review.
How to test
On each PR scan the QR code and make sure it opens on your phone's Expo Go app.
Notes

There isn't an easy way to test this locally so there may be multiple PRs regarding this issue until I get it right.
Also added dependency caching to increase the speed of the CI checks

Issue tracking

Don't merge until successful checks

Published to https://exp.host/@heartbleed/quick-bagel?release-channel=pr13

Published to https://exp.host/@heartbleed/whimsical?release-channel=pr13

 Published to https://exp.host/@heartbleed/whimsical?release-channel=pr13

up and running and looks great. my pixel 2 just always cuts off the dashboard when i log in lol


DOC: fix alert example code

basic_match_alert doesn't seem to exist anymore, instead there's a class BasicMatchString with its own str().

Thanks! I always forget about the examples when I make changes :/


你好，想问下node用的哪个版本，一直运行不起来，谢谢

https://www.npmjs.com/package/node-sass
according to this website, the Node version is 14.


ESLint returns "import/no-extraneous-dependencies" with Electron

ESLint gives this error when Electron is under dependencies instead of devDependencies which is inaccurate.

By default, everything is assumed to only be allowed to import runtime deps. You need to configure which files are allowed to reference dev deps.


increase timeout for not found after deletion

This check is flaky in some of our CI jobs. It stands to reason that it may take longer for the RepoSync to be NotFound after deletion due to the introduction of a finalizer. This change increases the timeout accordingly in an attempt to reduce flakiness of the associated tests.
Impacted tests:

TestDeleteRepoSync_Centralized_AndRepoSyncV1Alpha1
TestDeleteRepoSync_Delegated_AndRepoSyncV1Alpha1

/assign @karlkfi
/cc @nan-yu

https://oss.gprow.dev/view/gs/oss-prow-build-kpt-config-sync/pr-logs/pull/GoogleContainerTools_kpt-config-sync/389/kpt-config-sync-presubmit-e2e-multi-repo-test-group1/1622699014271012864
managed_resources_test.go:229: ERROR: expected *v1.ConfigMap object bookstore/test-cm1 to be not found

This error seems to be unrelated to this change, possibly a flake? I tried reproducing locally but the test passed. Seems like it might be related to the recent WatchForNotFound change @karlkfi
/retest

https://oss.gprow.dev/view/gs/oss-prow-build-kpt-config-sync/pr-logs/pull/GoogleContainerTools_kpt-config-sync/389/kpt-config-sync-presubmit-e2e-multi-repo-test-group1/1622699014271012864
managed_resources_test.go:229: ERROR: expected *v1.ConfigMap object bookstore/test-cm1 to be not found

This error seems to be unrelated to this change, possibly a flake? I tried reproducing locally but the test passed. Seems like it might be related to the recent WatchForNotFound change @karlkfi

Correct. Should be fixed with https://github.com/GoogleContainerTools/kpt-config-sync/pull/391

Now that WatchForNotFound works, this Retry block should probably be replaced with WatchForNotFound.


write missing mobile E2E tests for forget Password

Missing tests for e2e breakpoints

[x] reset-password
[x] forget-password

PR https://github.com/SAP/cloud-commerce-spartacus-storefront/pull/4315

Won't need those tests since there's no difference with the desktop viewport.


Explicitly convert inMediaType json to outMediaType yaml

CRDs currently can be read with --output=json and that is generally how it is encoded in k8s as well. I think there are discussions regarding other encoders for CRDs. Until that changes, we do not really need to worry about that. However we do need to add better documentation of how to decode CRDs.

Since you mentioned in #33  that CRDs can be read using --output=json, I believe this indicates that auger is functionally capable of correctly accessing data in the application/json format (similarly for other data types like CRDs which are also in application/json format). Therefore, I think that when attempting to read this data without the --output=json parameter, the output error decoding from application/json: xxxx is an unfriendly of program logic, because this data can indeed be accessed normally and should not throw an error.
I modified the logic in encoding.go so that when inMediaType is json and outMediaType is yaml(the default case), it explicitly converts the json data to yaml format for output.

Thank you @Deathstr0ke1 for improving auger! Can you run some local tests to see if this works for CRDs?

Sorry about signoff and Developer Certificate of Origin (DCO), I'm new to this. I want to open a new PR to solve the problem