Fix #4877 to follow the OpenID Connect Audiences spec

This follows the OpenID Connect spec to support audiences with either a string or an array of strings instead of just a string.
This might want to be on the release branches as well as it is a bug fix, but I personally can use master until then.
I have tested this and am running it on my site now with the OpenID Connect with multiple audiences returned with no issue, the new code is not even run at all unless the old pure-string check fails.
Disclaimer:  I've never used and barely looked at Go thus far, and I was unable to find common functions like filter or so forth (or any higher order functions at all...) and based on some googling it appears that these large and unwieldy loops are the standard way to do this kind of thing in Go, but if any changes are needed please request as such with information on what I should change it to (great learning opportunity!).
And of course any rights or whatever there-of related to this code I give up for whatever use this project currently wants or will want in the future.  Etc... etc...  Commit is signed, etc...

No clue why the CI failed, it looks like it didn't even try to recompile this code....

@OvermindDL1 You have to send a PR to upstream repo github.com/markbates/goth and then push this one again.

@lunny Interesting.  Why is the dependency included 'inside' this repo if it is not actually code for this project itself?  (I'm learning the reasonings as I've never seen someone include the dependents directly in a project short of ancient C and Cobol work 30 years ago...).
What do you mean by push this again, as in push the entire 'goth' repo into it, as a git submodule, with a .git directory, without a .git directory (archived), etc...?  In anything from C++ to the JVM to many others I'm used to just updating a single reference in a single file to pull a new version of a dependent, this including the entire dependent in the repo itself is extremely foreign to me (seems inefficient but I'm guessing there is a reason?).  ^.^;

PR submitted:  https://github.com/markbates/goth/pull/240

@OvermindDL1 We don't want to maintain all the dependency libraries so we will always follow the upstream library's update. If some commit changed the dependency library directly, that maybe make the things more complexly in future.
I'm sorry I mean after upstream PR merged, you could run dep ensure -update github.com/markbates/goth and then commit and push. We use github.com/golang/dep to manage dependency libraries.
Thank you for your effort.

Makes sense, I did not know that the go style is to copy all dependencies into a vendor directory (seems like that would artificially inflate a repository size, a substantial amount...) so didn't know it had any special significance.  I've not seen a language copy in it's dependencies permanently since my old C/Cobal days 25 years ago so it was entirely unexpected for me.  ^.^;
Care if this is left open as a reminder for me when the goth PR gets submitted, the instructions you gave should be great for me to use at that time.  :-)

And https://github.com/markbates/goth/pull/240 was just merged, the goth dependency can now be updated.  :-)
I'm trying to do it myself, but I had to deal with some horror of GOPATH environment variable just to get some message that it didn't know what gopath was, and no gopath worked except for putting gitea in a directory named 'src' for whatever reason, and all that does is print out nothing but this, no matter how I run it, try to update it, verify it, anything:
# dep ensure -update github.com/markbates/goth
dep: WARNING: Unknown field in manifest: prune
The following errors occurred while deducing packages:
  * "code.gitea.io/gitea/modules/highlight": unable to deduce repository and source type for "code.gitea.io/gitea/modules/highlight": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/mailer": unable to deduce repository and source type for "code.gitea.io/gitea/modules/mailer": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/markup/external": unable to deduce repository and source type for "code.gitea.io/gitea/modules/markup": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/process": unable to deduce repository and source type for "code.gitea.io/gitea/modules/process": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/public": unable to deduce repository and source type for "code.gitea.io/gitea/modules/public": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/models": unable to deduce repository and source type for "code.gitea.io/gitea/models": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/base": unable to deduce repository and source type for "code.gitea.io/gitea/modules/base": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/setting": unable to deduce repository and source type for "code.gitea.io/gitea/modules/setting": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/routers/user": unable to deduce repository and source type for "code.gitea.io/gitea/routers": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/httplib": unable to deduce repository and source type for "code.gitea.io/gitea/modules/httplib": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/indexer": unable to deduce repository and source type for "code.gitea.io/gitea/modules/indexer": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/pprof": unable to deduce repository and source type for "code.gitea.io/gitea/modules/pprof": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/routers/api/v1/org": unable to deduce repository and source type for "code.gitea.io/gitea/routers": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/routers/api/v1/swagger": unable to deduce repository and source type for "code.gitea.io/gitea/routers": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/routers/org": unable to deduce repository and source type for "code.gitea.io/gitea/routers": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/test": unable to deduce repository and source type for "code.gitea.io/gitea/modules/test": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/minwinsvc": unable to deduce repository and source type for "code.gitea.io/gitea/modules/minwinsvc": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/routers/api/v1/misc": unable to deduce repository and source type for "code.gitea.io/gitea/routers": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/routers/api/v1/utils": unable to deduce repository and source type for "code.gitea.io/gitea/routers": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/templates": unable to deduce repository and source type for "code.gitea.io/gitea/modules/templates": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/auth": unable to deduce repository and source type for "code.gitea.io/gitea/modules/auth": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/auth/pam": unable to deduce repository and source type for "code.gitea.io/gitea/modules/auth": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/search": unable to deduce repository and source type for "code.gitea.io/gitea/modules/search": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/routers/api/v1/convert": unable to deduce repository and source type for "code.gitea.io/gitea/routers": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/auth/oauth2": unable to deduce repository and source type for "code.gitea.io/gitea/modules/auth": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/context": unable to deduce repository and source type for "code.gitea.io/gitea/modules/context": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/routers/api/v1/user": unable to deduce repository and source type for "code.gitea.io/gitea/routers": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/user": unable to deduce repository and source type for "code.gitea.io/gitea/modules/user": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/validation": unable to deduce repository and source type for "code.gitea.io/gitea/modules/validation": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/notification": unable to deduce repository and source type for "code.gitea.io/gitea/modules/notification": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/recaptcha": unable to deduce repository and source type for "code.gitea.io/gitea/modules/recaptcha": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/routers/private": unable to deduce repository and source type for "code.gitea.io/gitea/routers": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/markup": unable to deduce repository and source type for "code.gitea.io/gitea/modules/markup": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/sync": unable to deduce repository and source type for "code.gitea.io/gitea/modules/sync": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/routers/utils": unable to deduce repository and source type for "code.gitea.io/gitea/routers": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/models/migrations": unable to deduce repository and source type for "code.gitea.io/gitea/models": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/generate": unable to deduce repository and source type for "code.gitea.io/gitea/modules/generate": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/markup/markdown": unable to deduce repository and source type for "code.gitea.io/gitea/modules/markup": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/private": unable to deduce repository and source type for "code.gitea.io/gitea/modules/private": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/routers/admin": unable to deduce repository and source type for "code.gitea.io/gitea/routers": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/routers/api/v1": unable to deduce repository and source type for "code.gitea.io/gitea/routers": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/routers/api/v1/admin": unable to deduce repository and source type for "code.gitea.io/gitea/routers": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/util": unable to deduce repository and source type for "code.gitea.io/gitea/modules/util": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/auth/openid": unable to deduce repository and source type for "code.gitea.io/gitea/modules/auth": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/cron": unable to deduce repository and source type for "code.gitea.io/gitea/modules/cron": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/lfs": unable to deduce repository and source type for "code.gitea.io/gitea/modules/lfs": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/ssh": unable to deduce repository and source type for "code.gitea.io/gitea/modules/ssh": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/routers/dev": unable to deduce repository and source type for "code.gitea.io/gitea/routers": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/avatar": unable to deduce repository and source type for "code.gitea.io/gitea/modules/avatar": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/routers/api/v1/repo": unable to deduce repository and source type for "code.gitea.io/gitea/routers": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/routers/repo": unable to deduce repository and source type for "code.gitea.io/gitea/routers": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/options": unable to deduce repository and source type for "code.gitea.io/gitea/modules/options": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/routers/user/setting": unable to deduce repository and source type for "code.gitea.io/gitea/routers": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/auth/ldap": unable to deduce repository and source type for "code.gitea.io/gitea/modules/auth": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/cache": unable to deduce repository and source type for "code.gitea.io/gitea/modules/cache": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/modules/log": unable to deduce repository and source type for "code.gitea.io/gitea/modules/log": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/routers": unable to deduce repository and source type for "code.gitea.io/gitea/routers": unable to read metadata: go-import metadata not found
  * "code.gitea.io/gitea/routers/routes": unable to deduce repository and source type for "code.gitea.io/gitea/routers": unable to read metadata: go-import metadata not found

validateParams: could not deduce external imports' project roots

What am I doing wrong here...  I'm used to just updating some commit in some dependency file and running something like cmake .. or mix deps.get or cargo build or whatever so I feel like I have to be doing something really wrong...  :-(

I will look into this later when I get home

I will look into this later when I get home

Cool thanks, I'd love to know what I'm doing wrong so I will know how to do it properly in the future.  :-)

Command is correct. Might be you have old golang dep version. Did you try to:
go get -u github.com/golang/dep/cmd/dep

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@8b113cd). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #4878   +/-   ##
=========================================
  Coverage          ?   37.41%
=========================================
  Files             ?      306
  Lines             ?    45334
  Branches          ?        0
=========================================
  Hits              ?    16962
  Misses            ?    25921
  Partials          ?     2451

Continue to review full report at Codecov.

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

Command is correct. Might be you have old golang dep version. Did you try to:

No clue?  It was installed via asdf and it returns:
╰─➤  go version
go version go1.11 linux/amd64

And generally asdf is up-to-date?  Plus, if anything was out of date shouldn't it state to update due to a version check with the internal metadata of the project when ran (at least that is how cmake/mix/cargo/etc all work)?

@OvermindDL1 it is not about GoLang but dep tool. It is hard to tell why it was not working for you

I will move to 1.6.0 milestone as it is just dependency update


Documentation sprint at the DLR meeting.

The following issues were raised by users and core developpers and should be addressed whenever possible.

Redesign or abandon main esmvaltool website.
Re-order the ReadTheDocs page.
Include a gallery page (like Matplotlib) on the ReadTheDocs
Unify the three sets of installation instructions.
Unify and Improve the Running ESMValTool pages. (README.md and ReadTHeDocs)

Explain how and why to change the config files to reflect your local environment.
Add a working example (with common data)
Add a figure that users should be able to reproduce.

Add a page on where to find the data.

This is not technically our responsibility, but it is a big hurdle for new users.
Explain the CMIP directory structure
Link to a page like http://clipc-services.ceda.ac.uk/dreq/index/var.html, which explains all the CMIP variables.

Create a common pitfalls page for errors that we regularly encounter when writing a new recipe.
Create a page about fixes in ESMValTool.

The following pages need to be expanded on our Users guide ReadTheDocs page:

data finder.
ESMValTool output
ESMValTool recipes: This deserves it's own page.
Custom variable derivation.
Most of the preprocessors.
ESMValTool directory structure.

The following sections need to be added to the users guide:

How yaml files work - a brief introduction
...?

A lot of this can be copied from my powerpoint in issue #1122.

I'm going to start by copying as much of the talk in #1122 as possible in the ReadTheDocs page.

A note to the reviewers on the documentation PRs: please focus about the content and correct errors and typos, but do not worry too much about the writing style at this stage.
Everyone writes with his/her own style and this would need to be homogeneized at the end, but now the priority should be to get the documentation in readthedocs.

For the documentation appearing united at ReadTheDocs I would like to propose this:
https://github.com/ESMValGroup/ESMValTool-doc/issues/1

I've added several new documentation omissions that we need to address which have been highlighted at the UKESM LTSM ESMValTool tutorial (today).

I opened a new issue #193 to better match the missing pieces to the current documentation structure on readthedocs and also to set the priorities.
Feel free to close this one if you think the other fully replaces it.

Replaced by  #193.


Some build errors after upgrade Node to v18

JsonToMjml.tsx:20:14 - error TS2339: Property 'children' does not exist on type 'EmailRenderProps'.
JsonToMjml.tsx:33:8 - error TS2322: Type '{ children: ReactNode; dataSource: { [key: string]: any; } | { [key: string]: any; } | undefined; mode: "testing" | "production"; context: IBlockData<any, any> | undefined; }' is not assignable to type 'IntrinsicAttributes & EmailRenderProps'.
Property 'children' does not exist on type 'IntrinsicAttributes & EmailRenderProps'.
TextStyleProps also missing children property.
And many many other components.

The latest version has been upgraded to react 18, please check it out. In addition, our default version is node1-6

Yeas, I updated and works as expected. Sorry.


Bad video quality!?

The example project and my own usage of the lib results in quite bad quality video (pixelation etc).
A bit surprised this has not been mentioned by anyone else. Am I the only one having this problem?

Which device do you use? The quality should be configurable through the bitrate property of videoConfiguration.

hi,@rFlex , I found the issue of the bad  quality in iPhone7, can you tell me what is the exact bitrate in iPhone 7 ? thanks very much

I'm seeing the same problem. I use AVAssetExportPresetHighestQuality but quality video is bad(pixelated). My device iPhone 6s. Have suggestions how to fix it?

@rFlex Problem exist only on iPhone 7. Seems there problem with hardware. Is it possible for you to check?

@rFlex are you alive? :)

@rFlex same here

just set to a better resolution

The same here @rFlex
I tried every resolution and every setting, the video is pixelated each time. Please, help!

Have you guys looked at the PRs or forks? Seems this fork is the most active and advanced.
https://github.com/lucaji/SCRecorder

yeah, I have checked them. I dont know how no one noticed this problem. Its mostly pixelated, and also depending on the light in the room, it gets better or worse. Is it some exposure setting or sth maybe? Please, open the native camera, or to any other video app, and compare the video quality. I am thinking to change the library because of it.

I dont have any problem like this. Go and check your exported videos quality, how is it exported (not the setti gs, the real video file)

Exported video is the same. I use front camera, iPhone7, AVCaptureSessionPresetHigh. And similar settings in the export config. SCPresetHighestQuality, SCContextTypeAuto, AVFileTypeMPEG4.

@freeubi are you using a different fork? and which device?
Pls, see this screenshot from a video file exported. This is obviously not the highest quality video on an iPhone-7.

This is my settings:
assetExportSession.outputFileType = AVFileTypeQuickTimeMovie;

                  assetExportSession.audioConfiguration.preset = SCPresetMediumQuality;

                  assetExportSession.videoConfiguration.bitrate = 250000;
                  assetExportSession.videoConfiguration.maxFrameRate = 24;
                  assetExportSession.videoConfiguration.codec = AVVideoCodecH264;
                  assetExportSession.videoConfiguration.size = CGSizeMake(360, 640);

i dont know wihtch version, because i dont use pods.
From the image i see low bitrate, try check the exported file data.

you can fix it by change default bitrate value "kSCVideoConfigurationDefaultBitrate" to very large number
#define kSCVideoConfigurationDefaultBitrate<PHONE_NUMBER>0000

In my case I had the same problem however, I had a configuration that was responsible for this:
exportSession.videoConfiguration.shouldKeepOnlyKeyFrames = true
When I removed the following the video was agreeably much better.
Also, what might also cause an issue is the maxFrameRate.


Use endpoint with IAM credentials

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
1

Sum
2


Cross-compilation assistence: Incorrect GCC binary used for target aarch64_unknown_linux_musl

In #577 support was added for Linux aarch64, however, the GCC binary name used was aarch64-linux-gnu-gcc rather than the MUSL variant (in this case aarch64-linux-musl-gcc) used by all of the other target/host combinations:
https://github.com/heroku/libcnb.rs/blob/4ec39b6fdf171f4f241f2d1fb3c3443b3cec53e6/libcnb-package/src/cross_compile.rs#L64
I believe this is an unintentional bug. (If instead there is a reason for it, it needs to have a comment added.)

Checking an ARM64 Ubuntu 22.04 image with musl-tools installed, I see that aarch64-linux-musl-gcc does exist, and that it does differ from aarch64-linux-gnu-gcc - which confirms my belief that we should be using the former instead.
The gnu variant is simply a symlink to standard GCC:
root@5d2e9841af3b:/# ls -al /usr/bin/aarch64-linux-gnu-gcc
lrwxrwxrwx 1 root root 6 Aug  5  2021 /usr/bin/aarch64-linux-gnu-gcc -> gcc-11
``

Whereas the `musl` variant is this wrapper script:

root@5d2e9841af3b:/# cat /usr/bin/aarch64-linux-musl-gcc
#!/bin/sh
exec "${REALGCC:-aarch64-linux-gnu-gcc}" "$@" -specs "/usr/lib/aarch64-linux-musl/musl-gcc.specs"


[build] debugging the build_man is hard.

Hello, while pacakging I faced a problem with the build_man target.
The only out put if help2man could not generate the doc is
Can not build the man pages.
It would be nice if insteead of raison the exception, the script could be executed with --help and --version (both)
This way the build log should contain the real problem during the build.
Usually a missing build dependency.
It is also important to change the directory before executing the script since there is a protection against execution of the build_man from the source directory.
Cheers

It would be nice if insteead of raison the exception, the script could be executed with --help and --version (both)

I faced the same problem. The solution you propose is a good idea.
If you know another better tool than help2man, where we can provide our own application output it can also be very nice.

Maybe we need to wait for this
https://bugs.python.org/issue14102

It should be fixed now, as if there is a problem we reexecute the script without help2man to see the problem.


Misc remove 24hr vol fixes

https://github.com/AugurProject/augur/issues/8884
https://github.com/AugurProject/augur/issues/8882
remove 24hr volume on trading page
update Invalid outcome tooltip to be trader minded.

Leaving this open because I wanna make sure the text makes sense to chwy and the tooltip right now doesn't mention that you can find our about the invalid rules.

Closing until we can vet tickets


Prefer the highlight version of the "GuiTabIcon" icon for buttons, and make their width/height equal

The non-highlight version makes the button look disabled. I also made that both the width and height equal in size.
Before:

After:

Thanks!

Cherry-picked for 3.2.3.


1.4.4 Streaming data fetching results in a parsing error

Steps to reproduce
I just tried fetching the streaming data. I don't know anything about InnerTube API, so I'm not sure if this error is normal. It still retrieves the data, but this error concerns me.
Failure Logs
Server error:  ParsingError: Could not transform n-token, download may be throttled.
    at NToken.transform (/home/stas/cathode-tube/build/x86_64-linux-gnu/app/install/yt-ws/node_modules/youtubei.js/lib/deciphers/NToken.js:55:21)
    at /home/stas/cathode-tube/build/x86_64-linux-gnu/app/install/yt-ws/node_modules/youtubei.js/lib/Innertube.js:432:125
    at Array.forEach (<anonymous>)
    at Innertube.#chooseFormat (/home/stas/cathode-tube/build/x86_64-linux-gnu/app/install/yt-ws/node_modules/youtubei.js/lib/Innertube.js:420:13)
    at Innertube.getStreamingData (/home/stas/cathode-tube/build/x86_64-linux-gnu/app/install/yt-ws/node_modules/youtubei.js/lib/Innertube.js:488:46)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async WebSocket.<anonymous> (file:///home/stas/cathode-tube/build/x86_64-linux-gnu/app/install/yt-ws/index.js:203:33) {
  info: {
    original_token: 'YwXptdr-M4sGuFl',
    stack: 'SyntaxError: Unexpected token u in JSON at position 189\n' +
      '    at JSON.parse (<anonymous>)\n' +
      '    at NToken.#getTransformationData (/home/stas/cathode-tube/build/x86_64-linux-gnu/app/install/yt-ws/node_modules/youtubei.js/lib/deciphers/NToken.js:74:17)\n' +
      '    at NToken.transform (/home/stas/cathode-tube/build/x86_64-linux-gnu/app/install/yt-ws/node_modules/youtubei.js/lib/deciphers/NToken.js:20:56)\n' +
      '    at /home/stas/cathode-tube/build/x86_64-linux-gnu/app/install/yt-ws/node_modules/youtubei.js/lib/Innertube.js:432:125\n' +
      '    at Array.forEach (<anonymous>)\n' +
      '    at Innertube.#chooseFormat (/home/stas/cathode-tube/build/x86_64-linux-gnu/app/install/yt-ws/node_modules/youtubei.js/lib/Innertube.js:420:13)\n' +
      '    at Innertube.getStreamingData (/home/stas/cathode-tube/build/x86_64-linux-gnu/app/install/yt-ws/node_modules/youtubei.js/lib/Innertube.js:488:46)\n' +
      '    at processTicksAndRejections (node:internal/process/task_queues:96:5)\n' +
      '    at async WebSocket.<anonymous> (file:///home/stas/cathode-tube/build/x86_64-linux-gnu/app/install/yt-ws/index.js:203:33)'
  },
  date: 2022-08-11T20:11:06.390Z,
  version: '1.4.4'
}

Expected behavior
I expected this to fetch the data without any errors.
Current behavior
It fetches the data correctly but gives this parsing error.
Version
Default
Anything else?
No response
Checklist

[X] I am running the latest version.
[X] I checked the documentation and found no answer.
[X] I have searched the existing issues and made sure this is not a duplicate.
[X] I have provided sufficient information.

Yup, YouTube updated their n token algorithm. I'm gonna update the NPM version later today.
Thanks.


side-by-side histogram count off

looks like the number of bins or their alignment is off-by-one


"No module named 'chromadb'" — add chromadb as dependency?

Trying to follow the guides:

https://langchain.readthedocs.io/en/latest/modules/indexes/getting_started.html
https://langchain.readthedocs.io/en/latest/modules/indexes/vectorstore_examples/chroma.html

But when I run:
db = Chroma.from_documents(texts, embeddings)

I get:
ModuleNotFoundError                       Traceback (most recent call last)
File ~/Library/Caches/pypoetry/virtualenvs/docs-bot-z8dlOdVH-py3.10/lib/python3.10/site-packages/langchain/vectorstores/chroma.py:40, in Chroma.__init__(self, collection_name, embedding_function, persist_directory)
     39 try:
---> 40     import chromadb
     41     import chromadb.config

ModuleNotFoundError: No module named 'chromadb'

In my Poetry dependencies, I only had langchain and openai.
I'd suggest adding a line somewhere in the docs that this is an optional dependency and should be installed?
Once I do:
poetry add chromadb

It works.

Interestingly I did not hit this exception path:
https://github.com/hwchase17/langchain/blob/4b5e850361bd4b47ac739748232d696deac79eaf/langchain/vectorstores/chroma.py#L32-L46
Using v0.0.98.

Make sure that it's installed in the same site packages directory. You may have used a different version of pip from a different python environment.

pip 22.0.2 from /usr/lib/python3/dist-packages/pip (python 3.10)
I don't think so it's a pip problem.
I have noticed that during pip install chromadb , torch process gets killed maybe memory issue.

with this pip install torch --no-cache-dir

What's the chromadb package size?

This is the size:
~/Library/Caches/pypoetry/virtualenvs/docs-bot-z8dlOdVH-py3.10
➜ du -hs lib/python3.10/site-packages/chromadb/
376K	lib/python3.10/site-packages/chromadb/

~/Library/Caches/pypoetry/virtualenvs/docs-bot-z8dlOdVH-py3.10
➜ du -hs lib/python3.10/site-packages/chromadb-0.3.10.dist-info
 32K	lib/python3.10/site-packages/chromadb-0.3.10.dist-info

For me using the following pyproject.toml was enough, using Poetry:
[tool.poetry]
name = "test"
version = "0.1.0"
description = ""
authors = [""]
readme = "README.md"
packages = [{include = "test"}]

[tool.poetry.dependencies]
python = "^3.10,<3.11"
langchain = "^0.0.98"
openai = "^0.27.0"
chromadb = "^0.3.10"

[tool.poetry.group.dev.dependencies]
flake8 = "^6.0.0"
mypy = "^1.0.1"
isort = "^5.12.0"
jupyter = "^1.0.0"
notebook = "^6.5.2"
black = "^23.1.0"

[build-system]
requires = ["poetry-core"]
build-backend = "poetry.core.masonry.api"

Then run poetry install. I generally prefer to use Poetry over user or system library installations.
(Make sure to update to the most recent version of the packages; the above are a bit outdated.)

Thanks,
Well my main issue was memory.
With combination of larger instance and poetry ,I am able to resolve my problem.

Thanks, Well my main issue was memory. With combination of larger instance and poetry ,I am able to resolve my problem.

Can you please help me out with how you took care of the situation. I am also facing the same issue...will be really helpful if you could elaborate the steps

Did you restart the terminal after the installation. try that it worked for me.

Hi everyone, this is how you can fix this error.

Did you restart the terminal after the installation?
I have tried lot of different combination like install with pip, conda etc but it solved with just restarting kernel

After restart  it worked for me

Close this issue for now.

I will close this issue once the chromadb dependency is properly documented. I'm not sure if this has been done in the meantime.

I found this was a version mismatch - langchain expected version 1.5.6. Pinning "chromadb": "1.5.6" in my package.json sorted the issue in my node project, i assume you will need to just align the version in python as well :)

chromadb.py

In my case, it is because I named a file with chromadb.py. Python tries to import from this file instead installed package.

Restart the terminal.It worked for me

chromadb

refer this link for solution:
https://stackoverflow.com/questions/64261546/how-to-solve-error-microsoft-visual-c-14-0-or-greater-is-required-when-inst

Tho I installed chromadb, still have this issue
pls help anyone

pip install chromadb


Added PHP page, added to contributor list

PHP page and small tutorial
A small page of my own
Added to contributor list

For future PRs :

Tag the issue being reference like : Addresses #0
Unless the multiple files are linked, submit different PRs for changes in different files.

Nice to know, thanks!


Transfer Learning

Goal(s)

Transfer knowledge from a well-labeled domain to a similar but different domain with limited or no labels

Input(s)

Model weights trained on one task

Output(s)

Model weights trained on another task

Objective Function(s)

TBD

I have used CRAFT network in my current company for OCR project. i can integrate the same if you want.

@p9anand Can you share a link to the CRAFT network you mentioned?

Initial work by @cfmusoles: #90

https://github.com/clovaai/CRAFT-pytorch

@p9anand Feel free to upload an implementation of CRAFT under the following folder:
tasks/computer-vision/scene-text-detection
You can use PyTorch or other implementations of CRAFT, including:

https://github.com/guruL/Character-Region-Awareness-for-Text-Detection-
https://github.com/autonise/CRAFT-Remade
https://github.com/backtime92/CRAFT-Reimplementation
https://github.com/namedysx/CRAFT-tensorflow
https://github.com/inouetaka/CRAFT

While CRAFT achieves state-of-the-art on MSRA-TD500 dataset, consider training your model on other datasets:

CTW
ICDAR 2019 Robust Reading Challenge

Cheers!


Allow ml-models/model_listing to publish without version

Description
Allow ml-models/model_listing model to bypass the version
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #158 (2539c84) into main (5bba4a6) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main     #158   +/-   ##
=======================================
  Coverage   90.67%   90.67%
=======================================
  Files          36       36
  Lines        3989     3989
=======================================
  Hits         3617     3617
  Misses        372      372


An account is not created when registering on the site.

For some reason, an account is not created when registering on the site. No registration data is displayed in the database. When you register, you simply redirect to the next section of the site without authorization. Everything else seems to work, but it is the authorization itself that does not. I can easily walk through the rest of the site, but without authorization. Where the captcha is in the code, I changed it, but it's not about it. What's wrong?

Are you sure that the .sql file has been correctly imported, and that the tables are not locked?

Are you sure that the .sql file has been correctly imported, and that the tables are not locked?

If you create an account manually through the database, you can then log into the account. but before that it was necessary to remove the exclamation mark in line 114 in the login.php. But if you register through the site, then an account is not created. I tried several times to reinstall the database on different hosting, but the result is the same


Remove ability to delete therapies or diseases in the admin console.

It was already disabled almost everywhere, disabled it remaining places except for orgs and users in 2c2bbcc


Enums aren't canonicalized when sent over a port in a compound object

When sending an enum constant directly on a port, the enum constant is canonicalized correctly in the receiving isolate. However, if the enum constant is part of an object, for example, a list or a user-defined class, the enum object isn't canonicalized in the receiving isolate.
import 'dart:async';
import 'dart:isolate';
enum Fisk {
  torsk,
}
isolate1(SendPort port) {
  port.send(Fisk.torsk);
}
isolate2(SendPort port) {
  port.send([Fisk.torsk]);
}
main() async {
  var port = new ReceivePort();
  await Isolate.spawn(isolate1, port.sendPort);
  Completer completer = new Completer();
  port.listen((message) {
    print("Received $message");
    port.close();
    expectTorsk(message);
    completer.complete();
  });
  await completer.future;
  port = new ReceivePort();
  await Isolate.spawn(isolate2, port.sendPort);
  port.listen((message) {
    print("Received $message");
    port.close();
    expectTorsk(message[0]);
  });
}
expectTorsk(Fisk fisk) {
  if (fisk != Fisk.torsk) {
    throw "$fisk isn't a ${Fisk.torsk}";
  }
}

https://codereview.chromium.org/1260033004/ was submitted to address this issue.

This is fixed in the VM, but not in dart2js. I think the test language/issue23244_test wasn't actually verifying the condition. Now it is, and is suppressed.  @rakudrama

The test language/issue23244_test is passing on content_shell in checked mode, but failing on dartium.  We don't know if if passes in content_shell in unchecked mode, since that isn't run on the buildbots.
Updating the status file to say it only fails in dartium, not content_shell.  This difference should be investigated.

There was a comment in the status file language.status for this failure, saying "spawnFunction cannot be run in dartium".  This seems strange, if the test is passing in content_shell.

I think the restriction is really that spawn (spawnFunction is the old name) cannot be used from Dart code running in Dartium. If you use spawn in dart2js to spawn JS (or compiled Dart code) it works, and the test in question was running in Dartium but compiled to JS. So the suppression is correct, I just missed that case.

@alan-knight since you reopened this for dart2js or Dartium I am assigning this over to you. I don't think there anything for Siva to do here.

I think I've encountered this issue multiple times while working with isolates. Enums that are sent (wrapped in an object) to the isolate retain the correct index but something is broken and you cannot compare them anymore (e.g. a switch with that enum won't work anymore). This is a pretty serious bug for me because now I have to 'recast' all enums in my isolate everytime (using var value = MyEnum.values[value.index];).

@hermanbergwerf: on which platform do you encounter this issue?

Never mind. I just saw the other issue: it's dart2js.

@rakudrama: since dart2js can't canonicalize at runtime, we have to send the JS-name (the name of the variable that contains the constant) to the other side. This means that every constant needs to have a way to know it's own name.
Alternatively, the isolate-send function could run through all possible constants and check for identity. Things get more complicated for nested constants, though.

I'm still not convinced that sending a const-created object through a SendPort shouldn't copy it like any other object. The object is just an object like any other created with the same constructor.
Enums are different and should be treated specially. If we had value-types, enums would be such, then there wouldn't be any problems with object identity.

But maybe dart2js should have the ability to canonicalize at runtime? For value types we would presumably need to support referential transparency anyway, and canonicalization may be a good choice in some situations.

So far runtime-canonicalization wasn't needed, and I would definitely not want to add it.

The implicit copy of canonicalized objects breaks programs and adds no value to users.
If copying can't be avoided, it would be simpler if only a few object types can be sent on ports. As implicit copy semantic completely breaks invariants, and we're forced to use JSON serialization anyway. Given that you're forced to use JSON, preventing certain object types from being transferred isn't going to be a problem, and will only serve to help users identify problems in their programs.

I agree that copying objects without calling a constructor is basically broken. There are already problems with hash-based collections (because cloned objects doesn't necessarily have the same hash code as the original) and with any object that has invariants or external state (e.g., using expandos).
It would be safer to restrict to only sending "value objects" (which we don't have, so some approximation). JSON-encodable data plus capabilities can be sent to any isolate, so this is only about which other values can be sent to spawn-created isolates. Restricting that to static functions and enums would probably handle most cases. You have to encode your object to List/Map/primitive data, but you also avoid accidentally sending a large chunk of data that your object is pointing to internally.
On the other hand, isolate communication is already hard enough, so do we want to make it harder?

On the other hand, isolate communication is already hard enough, so do we want to make it harder?

My point is that the current state of affairs is making isolate communication harder than it needs to be: you have to be aware of implicit copies and take great care to avoid that they happen. By restricting the set of types that can be sent on a port, we would make it easier to avoid hard-to-debug problems.

The Dart2js issue is #21817.

Apparently, the connection between this issue and the test language_2/issue23244_test is slightly complicated, but it may still be relevant for this issue that an error occurred in that test; cf. #32043 for details.


Queue Trigger > Allow 'none' encoding on a single function Queue Trigger

Description
We have an outside service that is able to push directly to our Azure Queue, which eliminates the need for us to run a seperate HTTP function to receive messages. However, they do not base64 encode their message. It would be helpful to allow a single queue trigger to receive a non-encoded message (rather than changing the host.json and changing it for the entire function app). Is this possible, or am I perhaps missing some feature that already exists?

Do you want the queue trigger function to receive the encoded message?

No, we would like the queue trigger to receive the un-encoded message. We want the rest of the functions in the app to use base64 encoding, as is standard.


Day61

Resolves #132.

Pull Request Test Coverage Report for Build 282

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 277:
0.0%

Covered Lines:
24

Relevant Lines:
24

💛  - Coveralls


CLI Plug-in command section not manageable

With new commands constantly being developed, it can be hard to maintain the "Commands" section of a plug-in doc. Furthermore, the command help is minimal and doesn't show available command options.
For example:
https://zowe.github.io/docs-site/latest/user-guide/cli-cicsplugin.html#commands
Resolution - instead of manually documenting commands, remove the entire commands section and from each plug-in doc and link to the CLI Online Command Reference instead. Link https://zowe.github.io/docs-site/latest/web_help/index.html

This is resolved and published - https://zowe.github.io/docs-site/latest/user-guide/cli-cicsplugin.html#commands


README: update tmux.conf snippet for tmux 3 support

This snippet was taken from @l-qing in https://github.com/christoomey/vim-tmux-navigator/issues/243.
Tested on tmux 2.1 and 3.0a.

@christoomey Sure I can add those to this PR when I have a few minutes 👍

@JayThomason
I used tmux shortly, and I'm not familiar with the syntax of tmux script.
These lines also took hours to complete.
I also tried using else, a little less judgment, but no success.
So, the rest is up to you. Thank you!

@christoomey I updated the snippets and README and re-tested on v3.0a and v2.1. I did not test the tpm plugin, but the snippets should be the same now.

Thanks for the work here @JayThomason!


[FBX][3.2.4 beta2][by design: compatibility] Additional RootNode added to scene, inside of the actual root node.

Godot version:
3.2.4 beta2
OS/device including version:
Windows 10.0.19041.630
NVidia GeForce RTX 2080 Ti 452.06
Issue description:
Because Godot scenes are already rooted at a node, the extra level RootNode is pointless and may break paths for no reason.
If an argument is made about transforms of top level objects in the FBX file, I would like to make a counter-argument that glTF and other formats dealt with this issue fine and do not need an extra root node.

Steps to reproduce:

Open the attached project.
Click Bunny_Farmer.fbx and click Reimport in the import panel.
Open the imported scene.
Notice that an extra RootNode was created and sits between the actual root node of the scene (named Bunny_Farmer) and the contents of the scene.

Minimal reproduction project:
fbx_issues.zip

This is to prevent compatibility breaking from assimp to the new fbx importer. for 4.0 it's planned to be removed, this is not a bug this is by design since the old importer created this node it could not just be removed as all inherited subscenes would be broken.

So since this is for 4.0 as it entirely breaks compatibility with inherited subscenes this can't be done for 3.2 beta.

To keep any compatiblity with existing user scenes this must remain in the importer until 4.0 I will move this to 4.0.

for 4.0 the goal would be: remove /RootNode/ compatibility since Reduz is working on replacing the Importer / inherited subscene to be unable to cause this problem.

I just ran into this using Godot 3.3.3-stable. I used to import an FBX as instanced Sub-Scenes. But now I get a single scene called RootNode.scn making me unable to proceed work on my project. I think this was already pointed out by @RevoluPowered but I don't understand what 3.3.3 users are supposed to do now. Is the option "instanced Sub-Scenes" (for now) useless and is there a workaround or should I just export all meshes from Blender as seperate FBX files?

I see you are using Blender.  If you are using Blender in your pipeline, you may benefit by switching to glTF 2.0 now. Plus, if you play your cards right, you may be able to re-export as glTF, and setup your gltf document to generate instanced subscenes, and perhaps it will work as fbx used to! (I even suspect that the references will automatically match up with your old FBX version from 3.2, and you won't break compatibility)
generally speaking, Blender FBX currently have some breaking bugs which Revolu knows about but hasn't fixed yet. So I'd expect more breaking changes in the future once blender support is made official. That's another reason to try glTF.
About this issue...
I filed this issue originally because the change to the new FBX importer broke compatibility (namely, the RootNode was not there before).
I believe the RootNode is a mistake, and I'm looking forward to improvements in the FBX importer that get rid of it.
The argument about backwards compatibility is well past moot at this point. The backwards compatibility boat sailed a long time ago when 3.3 was released, so Godot should focus on fixing bugs and moving forward. Maybe an import option to remove the top-level node would solve this pretty cleanly. (And it can double-up as a compatibility setting.)

Thanks, I can confirm using glTF 2.0 works as workaround!

This is probably fixed with the new FBX importer using FBX2glTF.
You can test it in Godot 4.0 alpha 6: https://godotengine.org/article/dev-snapshot-godot-4-0-alpha-6
This new importer might also be backported for the 3.x branch eventually.
If you still find issues with these models using the new importer, we suggest opening a new issue with details about the problems in Godot 4.0 alpha 6 or later.


How can I get the username from gitea system instead of git local  customization userName in API

Gitea version (or commit ref):
Git version:
Operating system:
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[ ] Not relevant

Log gist:

Description
i can get commit informations with a commit hash in gitea API, but the message returned shows the username that printed in git logs,the username doesn't exist in gitea system,it's comes from git local user's setting , like this "git config --global user.name 'xxx'",how can i get the username in gitea system?
...
Screenshots

You can get that on your sever via git config.


Extract a PriceRoundingInterface

The promised PR dedicated to @mitelg and Holger

Hi @JoshuaBehrens,
looks good to me. I will import it at Monday.
Fyi: We will remove the precision parameter and replace it with the Context object for more flexibility.

Nice to hear that. I must admit I was confused how "unflexible" it was

thanks for your contribution @JoshuaBehrens :+1: :tada: :blue_heart:
we will refactor it later, to you will get the context as parameter :wink:


CLI Auth Compatibility

Description
This PR adds CLI auth compatibility
We check for configuration from:

env vars
CLI config
defaults

It is compatible with the old Roboflow(api_key="") and now a new Roboflow() object
You can test functionality with the CLI roboflow auth and then
from roboflow import Roboflow

rf = Roboflow()

dangit. i left a bunch of feedback on the wrong PR i think, haha. you can see those comments here: https://github.com/roboflow-ai/roboflow-python/pull/61

@Jacobsolawetz what's the status of this PR?

Closing since this was absorbed in quickstart backbones


chore: Update kotlin to 1.9.10

Pull request checklist

[x] Please read our contributor guide
[ ] Consider creating a discussion on the discussion forum
first
[x] Make sure the PR doesn't introduce backward compatibility issues
[x] Make sure to have sufficient test cases

Pull Request type

[ ] Bugfix
[ ] Feature
[ ] Refactoring (no functional changes, no api changes)
[x] Build related changes
[ ] Other (please describe):

Changes in this PR
Bumps Kotlin version to 1.9.0
Alternatives considered
N/A

The kotlin version being managed in a Kotlin file in buildSrc means that tools like dependabot cannot issue PRs to bump the version. I think it's possible to use a versions.toml to manage it and still force alignment, if you're interested in something like that.


Some documentation needed.

At least some examples are needed. I can not understand how to use this crate convert Rust image into opencv, for example.

I just made a PR #5, hope this would help you.
You can convert the Rust image to opencv Mat by, for example,
use anyhow::Result;
use cv_convert::{TryFromCv, TryIntoCv};
use opencv::{self as cv, highgui, imgcodecs};

fn main() -> Result<()> {
    let path = "YOUR_IMAGE_PATH";
    let img = image::io::Reader::open(&path)?.decode()?;
    let mat: cv::core::Mat = img.try_into_cv()?;
    highgui::imshow("Image-to-OpenCV", &mat)?;
    highgui::wait_key(0)?;
    Ok(())
}

Now the API doc (link) includes a working example.


ReferenceError: primordials is not defined

Currently on osx 10146, grunticon 232, node 12141.

When I launch the grunt command on a grunticon folder, I keep getting ReferenceError: primordials is not defined. Also

Warning: Task "grunticon:icons" not found. Use --force to continue.

how to solve?

Also getting the same issue, seems to be on Node versions 12+

Seems devs doesn't look here too much :)

Anyone happen to know a good alternative? Hopefully one that I could migrate easily to 😂

I found this SO answer

I hit the same error. I suspect you're using node 12 and gulp 3. That combination does not work: https://github.com/gulpjs/gulp/issues/2324
A previous workaround from Jan. does not work either: https://github.com/gulpjs/gulp/issues/2246
Solution: Either upgrade to gulp 4 or downgrade to an earlier node.

So gulp and not grunt?

@stratboy  Oh, the same happend for me with grunt and the fixes worked as well. :+1:

Guys we had the same problem and we used the same workaround that @rulrok mentioned.  This works with NPM and shrinkwrap.  Alternatively a node downgrade to < v12 also works.
The problem for us is that we use Yarn w/workspaces and Monorepos and the only real solution was to go back to a version of node < 12 or use NPM instead of yarn.  We'd prefer to use all the new shiny things and we'd love to see grunticon keep on being a first class member of the grunt world.
If the team here at could (pretty please) just update their dependencies so that they're compatible with Node >= 12 then that would be completely awesome and it would give life to Grunticon for many years. @zachleat @scottjehl @toddparker

Guys we had the same problem and we used the same workaround that @rulrok mentioned.  This works with NPM and shrinkwrap.  Alternatively a node downgrade to < v12 also works.
The problem for us is that we use Yarn w/workspaces and Monorepos and the only real solution was to go back to a version of node < 12 or use NPM instead of yarn.  We'd prefer to use all the new shiny things and we'd love to see grunticon keep on being a first class member of the grunt world.
If the team here at could (pretty please) just update their dependencies so that they're compatible with Node >= 12 then that would be completely awesome and it would give life to Grunticon for many years. @zachleat @scottjehl @toddparker

Guys we had the same problem and we used the same workaround that @rulrok mentioned.  This works with NPM and shrinkwrap.  Alternatively a node downgrade to < v12 also works.
The problem for us is that we use Yarn w/workspaces and Monorepos and the only real solution was to go back to a version of node < 12 or use NPM instead of yarn.  We'd prefer to use all the new shiny things and we'd love to see grunticon keep on being a first class member of the grunt world.
If the team here at could (pretty please) just update their dependencies so that they're compatible with Node >= 12 then that would be completely awesome and it would give life to Grunticon for many years. @zachleat @scottjehl @toddparker

Guys we had the same problem and we used the same workaround that @rulrok mentioned.  This works with NPM and shrinkwrap.  Alternatively a node downgrade to < v12 also works.
The problem for us is that we use Yarn w/workspaces and Monorepos and the only real solution was to go back to a version of node < 12 or use NPM instead of yarn.  We'd prefer to use all the new shiny things and we'd love to see grunticon keep on being a first class member of the grunt world.
If the team here at could (pretty please) just update their dependencies so that they're compatible with Node >= 12 then that would be completely awesome and it would give life to Grunticon for many years. @zachleat @scottjehl @toddparker

Hi! This seems fine and reasonable. I'll set a reminder to take a look in the morning.
That aside, we need to give this pattern/project a look for moving forward. In our projects, we're typically embedding SVG directly or externally from sprites or direct files now and not necessarily using workflows to generate fallback images since svg browser support is very good.
This project, while still not totally ready for distribution, has been a decent alternative for us recently https://github.com/filamentgroup/iconoclash

Hi! This seems fine and reasonable. I'll set a reminder to take a look in the morning.
That aside, we need to give this pattern/project a look for moving forward. In our projects, we're typically embedding SVG directly or externally from sprites or direct files now and not necessarily using workflows to generate fallback images since svg browser support is very good.
This project, while still not totally ready for distribution, has been a decent alternative for us recently https://github.com/filamentgroup/iconoclash

thank you @scottjehl  that would be great!

thank you @scottjehl  that would be great!

@troylutton happy to fix it up. Could you help clarify for me the extent of the change? I'd like to get a PR to test and I'm seeing some notes about gulp, which shouldn't be a dependency for this... Just want to get the change right. thanks!

@troylutton happy to fix it up. Could you help clarify for me the extent of the change? I'd like to get a PR to test and I'm seeing some notes about gulp, which shouldn't be a dependency for this... Just want to get the change right. thanks!

@rulrok fix worked for me!

Just had this myself with an old legacy project. For me the fix was from the same StackOverflow post but the newer npm syntax:
{
  // Your current package.json
  "overrides": {
    "graceful-fs": "^4.2.9"
  }
}


Added a link to a .NET implementation of the multihash protocol

I've created a .NET implementation of the multihash protocol. I've added a link to the readme.

Sorry, can rebase? i merged another and markdown doesnt merge well. i will do it manually in a few days if not.

Np. Will do as soon as I am home later today...

Rebase done...

I merged this, because it was outstanding.
But could we rename it to "net-multihash", at least in the listing, to follow the convention? <lang>-<thing> is not always correct according to each <lang> but it makes for a cleaner <thing>.


Appstudio update hacbs-test-project-e6i8

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI has failed.There was an error creating the PipelineRun: hacbs-test-project-e6i8-on-pull-request-
creating pipelinerun hacbs-test-project-e6i8-on-pull-request- in namespace rhtap-demo-koyu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: hacbs-test-project-e6i8-on-pull-request-
creating pipelinerun hacbs-test-project-e6i8-on-pull-request- in namespace rhtap-demo-vtak-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: hacbs-test-project-e6i8-on-pull-request-
creating pipelinerun hacbs-test-project-e6i8-on-pull-request- in namespace rhtap-demo-cjlz-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request


explore use of danish disease trajectories

http://www.nature.com/articles/ncomms5022

Is there an update on getting the data @iandunham ?

No, nothing more but you could investigate whether there is any updated supplemental information

Low priority versus other data sources.  On backlog for data.


Policy deletion

Support for deleting Kuadrant policies (AuthPolicy, DNSPolicy, TLSPolicy, RateLimitPolicy) via the UI.

In the Developer perspective, users should be able to delete: AuthPolicy, RateLimitPolicy
In the Administrator perspective, users should be able to delete all types of policy

Will add to the Policies List kebab menu


Revamped the UI for URL shortener (Closes #1)

This PR revamps the UI of the URL shortener. The changes include:

Improved layout for the main page.
New color scheme and typography for better usability.
Added animations for aesthetic UX

This PR closes issue #1.
Initial:

updated:
https://github.com/user-attachments/assets/8b7ddea1-fd34-48c3-82ac-1f4a15db94df
linting and building successfully

@ShivanshPlays dude. you done a great work.. try to fix the conflicts

Hi @muruga21 , please check I have resolved the merge conflicts

@ShivanshPlays merged !


create api

what should i type on  'Application URL' and 'Application Name' option？

I'm not sure which 'Application URL' and 'Application Name' you are referring to? Could you explain better whats the issue

I'm not sure which 'Application URL' and 'Application Name' you are referring to? Could you explain better whats the issue

i solved this problem already~~~~tks

I'm not sure which 'Application URL' and 'Application Name' you are referring to? Could you explain better whats the issue

i solved this problem already~~~~tks


[LLVMCPU] Move ARM GEMMs codegen to use upstream tileFuseAndVectorize.

It retires LLVMCPUTileFuseAndVectorize pass in IREE, and renames the pipeline to CPUAArchDoubleTilingExpert.
The L1TileSizes are splitted into two tiling sizes. One is for parallel dims, and the other is for reduction dims.

Thanks for looping me in! I'll assess the performance impact very soon, but even before I do I think I know something that needs to be done to allow merging this without regressing mmt4d performance: drop the custom vectorization pattern that we had for mmt4d and use generic linalg vectorization instead. I was working on it anyway and now I'll prioritize finishing this asap.

Thanks for looping me in! I'll assess the performance impact very soon, but even before I do I think I know something that needs to be done to allow merging this without regressing mmt4d performance: drop the custom vectorization pattern that we had for mmt4d and use generic linalg vectorization instead. I was working on it anyway and now I'll prioritize finishing this asap.

This is mostly NFC. It keeps the same logic in the PR, i.e., we're still using custom vectorization pattern. I added a TODO to you for retiring custom vectorization patterns.
I think the regression is noise. I uploaded some NFC commits and got different results. If the regression does not show up on both pixel-4 and pixel-6, I usually assume them noise. Please also help verify it before I land the PR, thanks!

Note: the generic linalg vectorization breaks VectorContractCustomKernels. I did not investigate the reason. Probably some checks stop it. The PR is mostly NFC to mmt4d path.

Ah sorry, I had assumed that "upstread" tileFuseAndVectorize would imply not using custom VectorizeMMt4d.
I'll leave it to @MaheshRavishankar to verify that this really is NFC.

Note: the generic linalg vectorization breaks VectorContractCustomKernels. I did not investigate the reason. Probably some checks stop it. The PR is mostly NFC to mmt4d path.

Yes, I've seen that. That's most of the difficulty in dropping VectorizeMMt4d. The reason is that generic linalg vectorization produces vector shapes with extra unit dimensions. Part of the fix is to add an upstream pattern to drop as many of those as possible, and after that's done, there still remains some extra unit dimension and the fix is to generalize a bit the logic in VectorContractCustomKernels. I'm taking care of it.


Text Field is white with white background when dark mode is active

Oh, user needs to change Text Editor Theme also.

Thanks for the issue! I will develop the following solution: When the user open the app on the first time, I will default the text editor theme to the user theme, but after that, the user can override both app and editor theme.

I'm sorry @qrhfz, I will leave this issue open because I have an impediment. As a workaround, you can just set your text editor theme at settings.
To get the user theme settingsProvider would need BuildContext.

To use the context here:
      textEditorTheme: _settingsBox.get("textEditorTheme",
          defaultValue: Theme.of(context).brightness == Brightness.dark
              ? "vs2015"
              : "vs"),

If anyone with Riverpod knowledge knows how to access the BuildContext inside a Provider, I will be grateful.


-march=native causing segfault

Hi all,
Robot_dart compiles, but when I run the examples (on a 18.04 + Dart 7.0 compiled from sources), I get a segfault. Removing -march=native from the wscript fixes the problem.
Do you want a PR removing -march=native?
Best regards,

Do you want a PR removing -march=native?

No! I PR that makes it optional would be nice though! I did the same for limbo.
Did you compile DART with -march=native enabled? I am saying it in the instructions: https://github.com/resibots/robot_dart/blob/master/docs/installation.md

arf... I read this too quickly apparently, and missed the SIMD activation. Works with this activated. Sorry for the spam.

I am leaving this open in order to add some catch around it and an optional argument to disable it..

Fixed in #17 ...


Updating CPP producer to latest C producer and PIC

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #443   +/-   ##
=======================================
  Coverage   63.24%   63.24%
=======================================
  Files          32       32
  Lines        1276     1276
=======================================
  Hits          807      807
  Misses        469      469

Continue to review full report at Codecov.

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


[webapi] Add RealSense tests

Add tests for Photo, PhotoCapture API
Add tests for new API: getInternalCameraIntrinsics,
getVolumePreview

Impacted TCs num(approved): New 20, Update 0, Delete 0
Unit test Platform: Crosswalk Project for Windows 19.48.498.0
Unit test result summary: Pass 20, Fail 0, Blocked 0
BUG=https://crosswalk-project.org/jira/browse/XWALK-6345
BUG=https://crosswalk-project.org/jira/browse/XWALK-6545

Please reference the task id in your commit msg.

Will have an offline talk to improve these tests.

Tomorrow morning, it's ok?


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-26-main" workflow

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

Questions ?
Please refer to the Backport tool documentation


Navigating to existing screens without adding to stack

I'm having trouble understanding if it's possible to have singleton/static versions of screens.
StackNavigator
  - LoggedIn
    - DrawerNavigator
      - Main
        - StackNavigator (1)
          - Home
            - TabNavigator
  - Notifications (2)

Notes:
(1) - This stack navigator provides my main header which needs the drawer to cover it when open.
(2) - The Notifications screen is outside of the drawer because I don't want the drawer to be available from within it. I can't see a way of disabling the slide in ability per screen.
StackNavigator (1) has a notifications button on it which opens the Notifications (2) screen. When navigating from the Notifications screen to a tab in the TabNavigator there are two issues:

I need to first specify the LoggedIn route before specifying a tab route.
(main issue) When the app navigates to the tab from the Notifications screen it recreates the entire hierachy of views, placing them on top of the stack. I understand why this is but I'd like to be able to have "static" views that do not get created again, because now I am forced to either:

deal with an app slowing down as multiple instances of the app live on top of each other OR
use the reset action which solves the multiple instance problem but still recreates the views, therefore firing all the componentDidMount events and other various startup events.

I'd like to be able to say something like: this screen is static and should only ever exist once.
Now this could be problematic to deal with within the backstack so maybe we could enable you to say something like: close this screen (Notifications in this example) and open this one (everything under LoggedIn) but don't recreate it, just navigate to a part inside of it.
I realise this could be solved by using the back action on the Notifications screen before issuing the navigate to tab action. However I'd like my screens to not have to care where they are in the navigation stack, in my mind they should just tell the root navigator where they want to go and not have to implement any specific logic wherein they need to know how the stack is structured.

In Android native dev you can set a screen to be "singleTask", this is essentially what I'm trying to do here.

The system creates a new task and instantiates the activity at the root of the new task. However, if an instance of the activity already exists in a separate task, the system routes the intent to the existing instance through a call to its onNewIntent() method, rather than creating a new instance. Only one instance of the activity can exist at a time. https://developer.android.com/guide/components/activities/tasks-and-back-stack.html#ManagingTasks

I will probably end up extending the Router to deal with this.

My issue was closed because it is related to this one. But have we got any advancement/ideas on how to do this ?

@michaelduminy i think i made it work but looking deep into the source code to see how routers were working. I'll update when im sure everything is working correctly :)!

@wilomgfx yes! Please let me know, even if it doesn't work 100%. It'll still help.

Ill write a more detailed example on how it works but essentially i keep the index of the route i want kept open in the stack, and then with a custom redux action i navigate by that index.
The animations are quite clunky when using the StackRouter, which is understandable because its used to route either one index above or under itself. It also makes it so the BACK action adds my home screen every time on time.  Which is obviously unnecessary.
Probably will end up needing to create a custom router or something of that sort with the Router API.

This would be fixed by adding a key to the navigate action. Tracking that feature in https://github.com/react-community/react-navigation/issues/135

@ericvicenti great, indeed that's what i was aiming for.
I will look into #135

is there any news about this ? i got a stacknavigator, and in one of its screens a webview, each time i call the screen to sho, the webview gets recreated, i would like to reuse the screen instance, is there a way to achieve this ? thx

@PerspectivesLab yep it's exactly my use case too.


lmax option in gaussian_covariance()

I got error in using "gaussian_covariance" funcion as:
Traceback (most recent call last):
File "MakeCovariance.py", line 79, in
w22, wb=w22
File "/home/cmb/yminami/.pyenv/versions/anaconda3-5.1.0/envs/fgenv/lib/python2.7/site-packages/pymaster/covariance.py", line 223, in gaussian_covariance
wa.wsp, wb.wsp, cla1b1, cla1b2, cla2b1, cla2b2, len_a * len_b
RuntimeError: Coupling coefficients only computed up to l=4096, but you requirelmax=6143. Recompute this workspace with a larger lmax
I'd like to use lmax to be 2nside, and nside =2048.
I prepared coupling coefficients in NmtCovarianceWorkspace with lmax=nside2, set NmtWorkspace.lmax=nside2 by hand, and cls with lmax=nside2.
Though I think these are all arguments which have lmax information, it fails.
Could you please tell me the best way to set lmax in the calculation of covariance matrix?

I'm sorry I overlooked another closed issue and setting lmax in NmtBin solved all.

Great, thanks for reporting this @YutoMinami . Which issue helped you (just thinking it'd be good to have a reference here).

It's in this issue, https://github.com/LSSTDESC/NaMaster/issues/18.
It  seems, in "gaussian_covariance", ell_max variable in wsp.bin is used and I assume this bin is from NmtBin, even though there is a lmax variable direct below wsp.

Ah, great. Thanks again!


feat(IAM Policy Management): add support for policy templates

PR summary

Added feature support for Enterprise IAM work, policy templates and get template assigments.
Issue: https://github.ibm.com/IAM/AM-issues/issues/1346
PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

Current vs new behavior

SDK adopters will be able to call policy template and assignment APIs.
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

API defintion:
Staging
Prod
Test information:
Example Tests:
...
deletePolicyTemplateVersion() response status code: 204
deletePolicyTemplate() response status code: 204
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  22.478 s
[INFO] Finished at: 2023-05-18T15:49:44-05:00
[INFO] ------------------------------------------------------------------------

Integration Tests:
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running com.ibm.cloud.platform_services.iam_policy_management.v1.IamPolicyManagementIT
[INFO] Tests run: 24, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 15.397 s - in com.ibm.cloud.platform_services.iam_policy_management.v1.IamPolicyManagementIT
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 24, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] --- maven-failsafe-plugin:3.0.0-M7:verify (default) @ iam-policy-management ---
[INFO]
[INFO] --- maven-install-plugin:2.4:install (default-install) @ iam-policy-management ---
[INFO] Installing /Users/shaunsmacibm/Desktop/cloud-platform/iam/sdk/platform-services-java-sdk/modules/iam-policy-management/target/iam-policy-management-99-SNAPSHOT.jar to /Users/shaunsmacibm/.m2/repository/com/ibm/cloud/iam-policy-management/99-SNAPSHOT/iam-policy-management-99-SNAPSHOT.jar
[INFO] Installing /Users/shaunsmacibm/Desktop/cloud-platform/iam/sdk/platform-services-java-sdk/modules/iam-policy-management/pom.xml to /Users/shaunsmacibm/.m2/repository/com/ibm/cloud/iam-policy-management/99-SNAPSHOT/iam-policy-management-99-SNAPSHOT.pom
[INFO] Installing /Users/shaunsmacibm/Desktop/cloud-platform/iam/sdk/platform-services-java-sdk/modules/iam-policy-management/target/iam-policy-management-99-SNAPSHOT-javadoc.jar to /Users/shaunsmacibm/.m2/repository/com/ibm/cloud/iam-policy-management/99-SNAPSHOT/iam-policy-management-99-SNAPSHOT-javadoc.jar
[INFO] Installing /Users/shaunsmacibm/Desktop/cloud-platform/iam/sdk/platform-services-java-sdk/modules/iam-policy-management/target/iam-policy-management-99-SNAPSHOT-sources.jar to /Users/shaunsmacibm/.m2/repository/com/ibm/cloud/iam-policy-management/99-SNAPSHOT/iam-policy-management-99-SNAPSHOT-sources.jar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  38.420 s
[INFO] Finished at: 2023-05-18T16:01:23-05:00
[INFO] ------------------------------------------------------------------------

Tests passed after latest commit fix:
Examples:
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  21.978 s
[INFO] Finished at: 2023-05-22T17:07:36-05:00
[INFO] ------------------------------------------------------------------------

Integration:
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  38.166 s
[INFO] Finished at: 2023-05-22T17:07:10-05:00
[INFO] ------------------------------------------------------------------------

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: padamstx:white_check_mark: swcolley:x: vivekj3You have signed the CLA already but the status is still pending? Let us recheck it.

:tada: This PR is included in version 0.40.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


deploy kstone dashboard

I have one etcdcluster only, which is small. Can I just use dashboard to view etcdcluster status.

@fyqls If you want to view the etcdcluster status, you need to deploy at least three components: kstone-dashboard, kstone-api, and kstone-etcdcluster-controller, and then import the cluster to kstone in the console.

3U


Fix passing Organization ID param

Current dependencies on/for this PR:

main

PR #18   👈

This comment was auto-generated by Graphite.


Optimization: Exclude non-sort/filter relevant fields in reduce-extraction-to-projection

My Environment

ArangoDB Version:        3.4
Storage Engine:             RocksDB
Deployment Mode:       Single Server
Deployment Strategy:   Manual Start
Infrastructure:               local
Operating System:        Windows 10

Component, Query & Data
Affected feature: AQL query optimizer
AQL query (if applicable):
for m in businessMessages
filter m.tray == "IN"
sort m.updatedAt
limit 10
let d = m//DOCUMENT(m._id)
return [d.metadata, d.createdAt, d.updatedAt, d._key, d._id]

AQL explain (if applicable):
Query String:
 for m in businessMessages
 filter m.tray == "IN"
 sort m.updatedAt
 limit 10
 let d = m//DOCUMENT(m._id)
 return [d.metadata, d.createdAt, d.updatedAt, d._key, d._id]

Execution plan:
 Id   NodeType                   Est.   Comment
  1   SingletonNode                 1   * ROOT
  2   EnumerateCollectionNode   25467     - FOR m IN businessMessages   /* full collection scan */
  3   CalculationNode           25467       - LET #2 = (m.`tray` == "IN")   /* simple expression */   /* collections used: m : businessMessages */
  4   FilterNode                25467       - FILTER #2
  5   CalculationNode           25467       - LET #4 = m.`updatedAt`   /* attribute expression */   /* collections used: m : businessMessages */
  6   SortNode                  25467       - SORT #4 ASC
  7   LimitNode                    10       - LIMIT 0, 10
  9   CalculationNode              10       - LET #6 = [ m.`metadata`, m.`createdAt`, m.`updatedAt`, m.`_key`, m.`_id` ]   /* simple expression */   /* collections used: m : businessMessages */
 10   ReturnNode                   10       - RETURN #6

Indexes used:
 none

Optimization rules applied:
 Id   RuleName
  1   move-calculations-up
  2   move-filters-up
  3   remove-unnecessary-calculations
  4   move-calculations-up-2
  5   move-filters-up-2

Dataset:
25 000 documents in "businessMessages" which are rather large (contain a long text field)
Steps to reproduce
Problem:
The given query takes a lot of memory to execute because it loads 25 000 full documents in memory, sorts them, and then only returns 10.
Expected result:
If I add an indirection as indicated in the comment in the AQL statement (let d = DOCUMENT(m._id)), the query executes ~4 times faster and takes a lot less memory - just because the reduce-extraction-to-projection optimization kicks in and reduces the document size in memory significantly. In the original query, this optimization is not applied because more than 5 fields are accessed. However, those are only accessed in the RETURN clause, so it's way more efficient to just fetch them for the 10 documents we requested instead of for all of them.
Thus, the expection would be that ArangoDB sees the filter will return a lot more documents than the RETURN statement will process and in turn introduces this indirection I added in the query automatically.

To me this sounds much of a duplicate of @jsteemann explained here: https://github.com/arangodb/arangodb/issues/7782#issuecomment-448384616

@dothebart that issue / comment actually describes a different problem I currently encounter, so thanks for the link. However, I don't see how it is related to this issue - I'm not using or intending to use an index here.

I don't have a problem with ArangoDB looking at the document. My problem is that it loads the full documents into memory and not only the fields that are needed for sorting. More specifically, that the reduce-extraction-to-projection optimization does not apply.
To explain our use case: We have a million largish documents (a few kilobytes) which we sometimes need to sort without an index, and then return the first 10 items. When the query in total only reads 5 fields of the documents, it takes a few seconds, but finishes fine. When the query reads more than 5 fields of the documents, we run out of memory because basically the whole collection is read into memory and sorted there. This can be "fixed" by introducing the indirection via DOCUMENT(m._id) I mentioned in the issue.
My suggestion would be that ArangoDB should do this indirection automatically if the LIMIT value is significantly lower than the collection length.
A whole different question is why ArangoDB even needs to keep all the documents in memory for the sort if we're only intersted in the top 10 documents anyway. I asked that on slack yesterday (https://arangodb-community.slack.com/archives/C5L3P6SUF/p1545319824123700), I can create a separate issue for that if it's not just something I'm doing wrong. Anyway, I think this issue here would still apply because I would guess that a projected index scan is still faster than one that loads the whole documents, regardless of the memory usage.
But maybe I'm jumping wrong conclusions here, so please correct me if I'm wrong. I'm trying to understand what ArangoDB can do and where the limitations are. By the way, we (AEB) now also bought developer support from January onwards, so maybe that would provide a better framework for that.

Ok, let me explain a bit about the basics here first.
With document stores vs. table based stores you have the tradeoff that the document is stored as a blob, so the position of random attributes actually is random; while the table-store knows the definitive place on disk where one row of a column can be located.
This means that in order to access an attribute of a document you have to parse the document. Indices keep a copy of the attribute they index, so they don't have to re-parse.
Now another part of the Basics - AQL implementation. AQL is implemented as a stream of operators, similary as you would do on a unix shell with pipes if you use sed and grep. So, Documents come in at the left, are reduced by filters, or sub-attribute accesses and no further use of the document.
The optimizer now tries to re-order this pipe stream to make it as efficient as possible, to reduce the number of documents as quick as possible in the chain. One way to achieve this is instead of a full collection scan and manually filter have an index used to only give you as many documents as you need.
The current behaviour of the sort block is to keep all documents, sort them, return as many as demanded.
This is pretty simple, and quick - can use ready made sort algorithms etc.
Now one could add an optimizer rule that inspects LIMIT nodes, copies it over to the sort node, so it may only keep skip+limit documents, pull in documents, push documents out that are over the limit, throw pulled documents away instantly if they are above the limit. While this may be more memory efficient, its most probably not faster in most cases.
Plus in your case you do a full collection scan, so it will still load all documents, parse them, etc., so this can't become fast either.
So, there may be other solutions, like splitting the documents, putting the big parts into another collection, etc, or even the document() approach you took.

@dothebart I agree with almost everything you wrote, but I do think that this would be a very useful optimization that would not only reduce memory requirements but also improve performance - at least in cases where the limit is significantly smaller than the collection size (which I would consider a very frequent case).
Let's assume we have a collection with n documents and a LIMIT k.  This could be efficiently done using a heap with a fixed size k. An update of the heap has complexity O( log k), so the total complexity would be O(n log k), while a sort of all documents would have complexity O(n log n).

@Yogu : All the above comments aside, I think the situation can also be improved by adding a combined index on the two fields ["tray", "updatedAt"]. This should also make the query a lot faster without any change in the server-side code.
In addition I think that @mpoeter 's suggestion sounds very sensible, because it should also help in most situations.

@jsteemann yes obviously an index would avoid this problem, but it would be good if the database would not blow up on queries that don't use an index :)

@yogu: the problem here is that this is also a kind-of-difficult decision for the optimizer.
The "reduce-extraction-to-projection" rule is currently limited to 5 attributes code-wise, and the above query uses more attributes from the document, so it does not kick in.
While the threshold for the rule could easily be adjusted to any other number of attributes, it is not 100% clear if increasing the number of attributes may make some queries perform worse.
For example, let's say we increased the threshold to 8 attributes. Now, this particular query may be fine, but queries that deal with small documents (small document size, few attributes contained in the documents) may actually get slower after this change, because the optimization may lead to the individual document attributes being copied out of the documents one by one - which in sum may be slower than copying out the entire document in one go.
Still assuming a threshold of 8, when encountering a document with just 8 attributes would make the rule search for the desired 8 attributes inside the document and then copy the 8 attributes out one by one. That means 8 binary searches plus 8 times memcpy. Whereas without the optimization it would mean no binary searches and just a simple memcpy.
That means the optimization may decrease performance in the worst case. However, it should never do any harm in terms of memory usage (in the worst case, the memory usage is the same as without the optimization kicking in). And in the best case, the optimization may save a lot of memory.
Obviously the sweet spot depends a lot on how big the documents are and how many attributes are contained in them. The problem is that the optimizer doesn't know anything about this when planning queries, so its assumptions must be somewhat generic and conservative.
That leaves the question if there are some additional cases in which we can more or less safely apply the "reduce-extraction-to-projection" rule without making the performance of simple/small document queries worse.
Apart from that, I think @mpoeter's suggestion is still good here, because it will help in many cases to keep memory usage down. I can't yet estimate its performance effects for real-world queries, but it can be given a try.


Initial docs

There is still a ton of room for improvement, but it's slightly better than what we currently have. So, lets take it one step at the time...
That being said, @voliva could you please help me improve this?

It might be worth putting the API docs in a specific format, such as:
Description:
When this is useful:
Returns:
Parameters:

Most definitely! However, the only purpose of this PR is to have something more "decent" than what we currently have. So, I've taken most of your feedback and I'm merging this for now because I can't sleep at night knowing that the "coming soon" joke is still no the "Docs" section of the current README.

@all-contributors please add @bhavesh-desai-scratch for review


Publish js as asset

Related Issue
#31
Description
When I was pushing my code to my production server (Nginx, Laravel 8.70, PHP 8.0.12, Laravel Octane) I was getting an interesting 404 not found error. This had happened before and after I added octane by the way.
To Reproduce
I actually fixed this issue by moving the tall-toasts.js to /public/toast/tall-toasts.js
Expected behavior
The Laravel RouteFacade to actually load it in production. It worked fine in development.
Additional context
This is a similar issue that gets experienced in Livewire. I'd like to open a PR and add an artisan command called toasts:publish that would allow users to move the JavaScript to a /public/toast/tall-toasts.js file. We could then call this in the post-autoload-dump, for example, in composer.json if we wish so it could stay updated as we update our projects.

branch put on hold, awaiting further reports on 404 issue with JS.


what if some Deployment PODS do not want to inject kum-init sidecar,how to set?

apiVersion: v1
kind: Namespace
metadata:
name: kuma-demo
namespace: kuma-demo
annotations:
kuma.io/sidecar-injection: enabled

By default we set the namespace and add the annotation kuma.io/sidecar-injection: enabled so that each POD of the k8s namespace  is injected kum-init sidecar. But what if some Deployment PODS do not want to inject kum-init sidecar,how to set?

Hi, It is available in docs - https://kuma.io/docs/1.0.1/documentation/dps-and-data-model/#kubernetes

apiVersion: apps/v1
kind: Deployment
metadata:
name: example-app
namespace: kuma-example
spec:
...
template:
metadata:
...
annotations:
# indicate to Kuma that this Pod doesn't need a sidecar
kuma.io/sidecar-injection: disabled
spec:
containers:


README is out of date

There are a few things in the README file which may confuse potential users. Below is an (incomplete) list of things that need considering. I will submit a new PR to cover some of the easy points.

[x]  Some links are out of date (pointing to my old repo, which has now been renamed) (see PR #9)
[ ] The version number hasn't been updated since this fork started. It would be good to have a new version number to identify library versions based on this repo.
[ ]  PyPI links to an old version (kevinpt's). This is confusing because when users run pip install hdlparse they won't get the version from this repo.

For the last point we could try a few solutions:

We could try to get in touch with kevinpt to see if we can get the PyPI hdlparse package to point to this repo
If we cannot reach kevinpt, perhaps PyPI could transfer ownership?
We could bump the version to 2.0.0, then make a new hdlparse2 package on PyPI?
We could use a different name altogether for a new PyPI package?

Looking forward to hearing your thoughts on this topic.
Cheers,
Wouter

With regard to naming and pip, see https://github.com/hdl/pyHDLParser/pull/2#issuecomment-926547629.


Add support for PHP8

This PR adds support for PHP8, which gdaisy doesn't currently have. minicli supports PHP8 though, so gdaisy doesn't have any requirements that interfere with PHP8.
I did run the test suite on PHP 8.0.7 and got all greens, also symlinked this branch locally and went through requiring it and generating an image, and everything went smoothly there. 👍

That's awesome, thank you @thinkverse ! 🥇


net/frr register_sas script/setkey add SAD entries for both IPv6 and IPv4

OPNsense supports BGP on both IPv4 and IPv6, but the current frr/setkey script implementation only adds SAD entries for IPv4. Changing -4 to -n keeps filtering on numeric addresses, but adds SAD entries for both IPv4 and IPv6 instead of only IPv4.
Tested working on a Vultr VM with BGP enabled and MD5 password on the Vultr side.

@as8net looks good indeed, thanks!


Check SECURE_ELEMENT_PREPROVISIONED

Double-check whether SECURE_ELEMENT_PREPROVISIONED really needs to be set.

Does not need to be set, but does not harm. When set, SecureElementInit will NOT derive DevEui from MCU's serial if DevEui is all zeroes (unset). We perform the same operation after restoring state from NVM after LoRaMacInitialization anyway, so our code will perform the initialization even if SecureElementInit does not.


what's the story with busser-infrataster?

https://twitter.com/rubygems/status/542563567896367104
:)

:+1:


Need new supported release of 3.0.0

3.0.0.pre is a much needed update that addresses some security concerns. If there is no reason not to release, this candidate should become the latest gem released version.
thanks - for dragging this out of mothballs!

Ditto. :)
In the meantime, this is what we're doing to work around it- gem 'axlsx', '3.0.0.pre' # TODO: Unpin when a non-pre version without the ruby-zip vuln is released

@randym, do you want some kind of help with the maintenance? I absolutely love this gem and use it extensively, I will be happy to contribute.

See also #599

Also see #536

Since we get no response, I'm taking over the maintenance in my personal fork:
https://github.com/fernandoluizao/axlsx-alt
https://rubygems.org/gems/axlsx-alt
I merged some PRs and released a new version with a new name. I haven't changed the gem's namespace, so it should be easy to migrate.
Please, note that this isn't a hard fork... If someone wants to help, ping me.

@fernandoluizao You may want to release a fix to the 2.x major version as well. I prepared such a backport in #536.

I'm not intending to support older versions... sorry :disappointed:

There's now https://github.com/caxlsx/caxlsx which has released 3.0.0 (and 3.0.1 and also 2.0.2 with a backport for the rubyzip dependency).

There's now https://github.com/caxlsx/caxlsx which has released 3.0.0 (and 3.0.1 and also 2.0.2 with a backport for the rubyzip dependency).

So, should this be considered the preferred solution?

Going with caxlsx as a solution where there is some community support - thanks @noniq !


Remove deprecated admission plugin flag

As of kubernetes 1.10 --admission-control has been deprecated in favor of --enable-admission-plugins
This new flag is already in place for the bootstrap rendered manifest
https://github.com/kubernetes-incubator/bootkube/blob/master/pkg/asset/internal/templates.go#L227
This PR also sets that flag for the apiserver template
Note: trying 1.9 clusters won't work using the new flag, this could be fixed doing just the opposite, replacing the new flag at the rendered bootstrap manifest with the old one, since it is still working. I'd stick to the new flag, and let 1.9 users modify the rendered manifests if using bootkube > 0.12.0

@coreosbot test this please

@rphillips this LGTM but can you confirm? It looks like you updated the bootstrap apiserver; wanted to make sure it wasn't intentional that the real apiserver was left with the older flag.

missed that... lgtm


content(rxjs): fix typo

Minor typo fix 😄

Hey,
Thanks for the update!
Feel free to create another big PR with all the typo's that you've found!


[WIP] Prototype of ECharts time axis rebuild to fix x axis bucketing

Allows x axis to be rounded to more intuitive values than before by using ECharts 'time' axis type instead of 'category'
TODO

[ ] Sync branch and fix merge conflicts from table legend PRs and tooltip / highlighting PRs
[ ] Plan for a gradual roll out (feature flag in our app's plugin registry or a duplicate ExperimentalTimeSeriesChart?)

Could even be a URL param to switch between the legacy 'category' implementation and new 'time'

[ ] Fix timezones

hopefully this approach will work: https://github.com/apache/echarts/issues/14453#issuecomment-800163920

[ ] Fix thresholds convertPercentThreshold
[ ] Fix types in new TimeChartTooltip getNearbySeries function
[ ] Confirm no regressions in null values logic
[ ] Cleanup components/src/model/graph.ts types
[ ] Additional stories and docs for legacy LineChart and new TimeChart

Screenshots
Last 1 hour

Last 7 days

Performance Benchmarks

Total series
Category axis (ms)
Time axis (ms)

1000
1707, 2083, 2239
1378, 1679, 1707, 1364

2000
3734, 3860, 4082
2949, 2758

3000
5830, 5872, 5744
5516, 5019, 4989

4000
8828, 8856, 8707
8202, 7621, 7616

Closing prototype branch, time axis rewrite should work out but this branch is out of date and a separate PR for future updates will be better


form_for form_tag + rails 4 doesn't get bootstrap 3 styles

When I use bootstrap-sass and rails 4 the forms doesn't take the rails styles, what I'm doing wrong?
<%= form_tag do %>
<%= label :aportacion, "Aportación" %>
<%= text_field :aportacion, placeholder: "Cantidad total" %>
<% end %>
and the html rails render:

Aportación

Thanks for the help

Thank you @wyaeld, It was very helpful!


README: Add epel-relesse install to centos

@roydahan @syuu1228 he had an issue open about the need to install epel, I'm not sure this is needed, can you comment?