Redundant voice assistant sample/quick start app?

I've been researching how to build a voice assistant with the DirectLineSpeech channel and I've run into what looks to be two different version of the same sample app.  The first can be found in the "master/samples" folder in the Speech SDK here and the other can be found in the "master/quickstart" folder in the Speech SDK here.  Are these essentially the same sample app but just slightly different versions?  Why are both needed?  Would one sample be less confusing?

Thanks for raising this issue -- and apologies it's taken so long to get a response!
You're quite right that the difference between the quickstart and sample is subtle. The biggest difference is that the "sample" version has some additional supporting code for cleaner result displays and audio streaming -- this makes getting things running slightly less "quick," hence why it's moved out as a sample.
I agree there's some room for making this more clear and I've opened a work item on our team to either consolidate the two or integrate more changes for a more meaningful difference.
Separately, because you're looking at the UWP sample, we also recently published a much more comprehensive sample that includes upcoming Windows Assistant integration along with Direct Line Speech (you can use pieces just for the latter as needed); you can find this at http://aka.ms/mva/sample. We're making updates to the docs now to cross-link to this and I anticipate that that this newer sample will be the more definitive "sample" resource (versus the quickstart).
Thank you!


Installation failed, node-tmp

When I try to install this package via atom, I always get following error:
Updating to<EMAIL_ADDRESS>failed.Hide output…
npm ERR! Windows_NT 6.2.9200
npm ERR! argv "C:\Users\username\AppData\Local\atom\app-1.9.9\resources\app\apm\bin\node.exe" "C:\Users\username\AppData\Local\atom\app-1.9.9\resources\app\apm\node_modules\npm\bin\npm-cli.js" "--globalconfig" "C:\Users\username\.atom\.apm\.apmrc" "--userconfig" "C:\Users\username\.atom\.apmrc" "install" "C:\Users\username\AppData\Local\Temp\d-11681-16820-bp9g5y\package.tgz" "--target=0.37.8" "--arch=ia32" "--msvs_version=2013"
npm ERR! node v0.10.40
npm ERR! npm  v2.13.3
npm ERR! code E404
npm ERR! 404 Registry returned 404 for GET on https://registry.npmjs.org/node-tmp
npm ERR! 404
npm ERR! 404 'node-tmp' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of 'organized'
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
When I download the package manually and change the dependency in the package.json from "node-tmp" to just "tmp", it works.

Thanks for reporting the problem, doing everything in dev mode, I hadn't noticed it!
It should be fine now in 0.4.2.


Cleanup Kokoro + Microsoft builds.

Now that vcpkg has the same version of googletest that we use we can simplify the ci/kokoro/*.ps1 scripts. No need to use an external project.

Fixed in #2103.


function of split and combine

the plugin is amazing
I want to beg you developing function like this:
1.when I write node of paragraphs, with run commend of spliting to many nodes, every node within only one paragraph, and delete orignal one(quickly split)
2.when I select many nodes, with run commend of combining to one node, the node within all the paragraphs, and delete those orignals(quickly merge)
3.select many nodes, choise last one, with commend that can link last one to those nodes(quickly connect)
4.select many codes, with commend that all the codes selected align one another left and top together. I think it's a fast way to arrange the page(quickly align)
That's very important to deal with datas like mindmap, especially when the codes always changes. Thank you

Thank you @Juan-hwt for your comment and suggestions.
However, I think your suggestions would belong to another plugin, more a "refactoring" plugin than a "cleaning" one like optimize-canvas-connections. I would also love to have these functionalities, but unfortunately I don't have time to develop these.
For your point 4, there is already an align tool builtin Obsidian, but I guess it's not what you talk about.
Anyway, thank you for your comment!

ok thanks
I want to know where can get docs about canvas development, I have readed the official files, but woo... I even don't know how to create/delete a node, now only print x,y,width,text and nothing.
As you see, I'm a debut about this, can you give me some advisces such as how to change and fit the height?


Minor Design Changes to Make Menu Hierarchy Clear

The best way to do this is probably to branch off of Master in Abstract.

Dupe of #291


Change default brain orientation and adjust opacities

Addresses issue #35.
I also changed the default opacities of the left and right hemispheres and the grey fiber bundles. I thought these opacities gave a nice "first impression" but I'm not heavily invested in them so @arokem and @jyeatman if you feel the old opacities were more effective for researchers, just let me know.

This looks good to me (including changed opacities). I'll let others take a look before merging.

Is there a way to set the default lighting location as well? For me, the light looks like it is positioned behind the brain until I click somewhere and then it illuminates properly

@jyeatman Good catch. Thanks. I just added a commit that sets the initial lighting to the camera position.

That looks much better! I messed around a bit with the opacity settings and
my vote is full opacity for the right hemi. Zero for the left hemi. And 0.2
for the fibers. But I don't feel strongly if others have a different
preference for the aesthetics
Jason D. Yeatman, PhD
Assistant Professor, Institute for Learning & Brain Sciences (I-LABS)
Department of Speech & Hearing Sciences
University of Washington
http://brainandeducation.com
On Wed, Sep 28, 2016 at 5:11 PM, Adam Richie-Halford <
<EMAIL_ADDRESS>wrote:

@jyeatman https://github.com/jyeatman Good catch. Thanks. I just added
a commit that sets the initial lighting to the camera position.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/yeatmanlab/AFQ-Browser/pull/39#issuecomment-250337347,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABsYytrC2GxgZd4p-7tD_2q2Y3xjVVBmks5quwIpgaJpZM4KJYpT
.


Support setting whitelist, without setting default redirect_url

Error:
Redirect to '' not allowed
Steps to reproduce

set redirect_whitelist (to ['google.com'], for example)
don't set default_confirm_success_url
Try and create a new user via POST /

Expected outcome
A successful registration
Actual outcome
You should get Redirect to '' not allowed
This change resolves the issue.

👍

Thanks, guys!

@zachfeldman Any chance we can get a version bump soon for this?

@dkniffin We're testing the last code in master in order to release a new version soon

Coming soon https://github.com/lynndylanhurley/devise_token_auth/issues/972 @lynndylanhurley has the keys to Rubygems :)


Enable Estimate EMOS Coefficients CLI to take additional predictors

Addresses #1869
Acceptance Tests Branch: impro_1869_additional_predictors_estimate_EMOS_CLI
Description
Adds functionality to estimate emos coefficients CLI to use additional predictors. This required a change to split_forecasts_and_truth so that it could split out forecast, truth, land-sea mask, and additional predictors. As this function is used in other CLI, updates to those were required to ensure compatibility.
Adds tests for new/updated functionality.
I think a small suite change will be required if/when this PR is approved to ensure compatibility as the CLI inputs when using a land-sea mask have changed to require the land-sea mask name to be input.
Testing:

[x] Ran tests and they passed OK
[x] Added new tests for the new feature(s)

In order to maintain a backlog of relevant PRs, we automatically label them as stale after 60 days of inactivity.
If this PR is still important to you, then please comment on this PR and the stale label will be removed.
Otherwise this PR will be automatically closed in 30 days time.

Commenting to remove 'Stale' label


Unittesting

How about to write some tests for this app?

@Alkalit First, I appreciate you expressing interest in making a contribution. You can never have to many tests I always say.
We currently have about 110 tests passing thus far.
If you make a pull request with any tests you write I can be happy to take a look and pull them into the master branch.

@avelis Deal.

Addressed in pull request: #93


[Proposal] Strictly define OS version in GHA

Is your feature request related to a problem? Please describe.
Now all GHA workflows use ubuntu-latest runners. The version of OS might be changed in future which might cause failures or crashes.
See example:
https://github.com/opensearch-project/OpenSearch/blob/9b2202aeb3a881c0c2ad72522fa1e2656d5d4d1e/.github/workflows/gradle-check.yml#L13
Describe the solution you'd like
I propose to strictly define the OS version which should be used there. Currently ubuntu-latest = ubuntu-20.04 (link). The proposed fix should change all references to ubuntu-latest by ubuntu-20.04.
Describe alternatives you've considered
Do nothing until GH publish OS version change for ubuntu-latest. There will be a few month period to update and fix all workflows if needed.
Additional context
Tags: GHA, CI, ubuntu, ubuntu-latest, runner, OS version
I can to the fix (a PR) on my own, but I need an approval to that idea first.

@Yury-Fridlyand thanks for the proposal.
Would it be better if we test against new and old versions, instead of just being static with the versions we know it works with? (GHA supports running with a matrix)[1]
[1] https://devblogs.microsoft.com/premier-developer/github-actions-overview/#matrix-builds

@Yury-Fridlyand are you open to contributing the change?

Yes. I'll run tests first.

@Yury-Fridlyand i'll assign it to you, as you are working on it. If not let me know.

@saratvemulapalli,
I see that GHA works on all ubuntu versions: https://github.com/Yury-Fridlyand/OpenSearch/pull/2
It is OK if I will try to update ubuntu-latest to ubuntu-22.04 or ubuntu-20.04 (no update actually)?

picture of tumbleweed

Sounds OK to me!

ubuntu-latest was bumped recently from 20.04 to 22.04, and fortunately nothing was broken (unlike python 3.5 projects).
I tried to implement my proposal in #5612, which is closed, because it is irrelevant anymore.


unable to vitedge build

Repo: https://github.com/hrgui/pokedex-vitedge
warning package.json: No license field
$ rm -rf dist && vitedge build
(node:10381) UnhandledPromiseRejectionWarning: Error: Transform failed with 1 error:
/Users/hrgui/projects/pokedex-viteedge/node_modules/esbuild/lib/main.js:239:12: error: Invalid option in transform() call: "jsx"
    at failureErrorWithLog (/Users/hrgui/projects/pokedex-viteedge/node_modules/esbuild/lib/main.js:1443:15)
    at /Users/hrgui/projects/pokedex-viteedge/node_modules/esbuild/lib/main.js:1288:20
    at /Users/hrgui/projects/pokedex-viteedge/node_modules/esbuild/lib/main.js:606:9
    at handleIncomingPacket (/Users/hrgui/projects/pokedex-viteedge/node_modules/esbuild/lib/main.js:703:9)
    at Socket.readFromStdout (/Users/hrgui/projects/pokedex-viteedge/node_modules/esbuild/lib/main.js:573:7)
    at Socket.emit (events.js:315:20)
    at addChunk (_stream_readable.js:309:12)
    at readableAddChunk (_stream_readable.js:284:9)
    at Socket.Readable.push (_stream_readable.js:223:10)
    at Pipe.onStreamRead (internal/stream_base_commons.js:188:23)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:10381) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:10381) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
✨  Done in 0.71s.

I am also getting this issue on this repo: https://github.com/subhendukundu/vitedge-react-template
yarn run v1.22.10
warning package.json: No license field
$ rm -rf dist && vitedge build
building for production...
✓ 62 modules transformed.
dist/client/assets/logo.ecc203fb.svg    2.61kb
dist/client/index.html                  0.46kb
dist/client/manifest.json               0.78kb
dist/client/ssr-manifest.json           7.19kb
dist/client/assets/About.3a223546.js    0.19kb / brotli: 0.12kb
dist/client/assets/index.10d42577.js    2.69kb / brotli: 1.13kb
dist/client/assets/Home.b57b4c20.js     0.41kb / brotli: 0.21kb
dist/client/assets/index.e9904e82.css   0.46kb / brotli: 0.21kb
dist/client/assets/vendor.9557a7b8.js   166.09kb / brotli: 47.07kb
building SSR bundle for production...
✓ 18 modules transformed.
dist/ssr/main.js   24.62kb
(node:10830) UnhandledPromiseRejectionWarning: Error: Transform failed with 1 error:
/Users/hrgui/projects/vitedge-react-template/node_modules/esbuild/lib/main.js:239:12: error: Invalid option in transform() call: "jsx"
    at failureErrorWithLog (/Users/hrgui/projects/vitedge-react-template/node_modules/esbuild/lib/main.js:1443:15)
    at /Users/hrgui/projects/vitedge-react-template/node_modules/esbuild/lib/main.js:1288:20
    at /Users/hrgui/projects/vitedge-react-template/node_modules/esbuild/lib/main.js:606:9
    at handleIncomingPacket (/Users/hrgui/projects/vitedge-react-template/node_modules/esbuild/lib/main.js:703:9)
    at Socket.readFromStdout (/Users/hrgui/projects/vitedge-react-template/node_modules/esbuild/lib/main.js:573:7)
    at Socket.emit (events.js:315:20)
    at addChunk (_stream_readable.js:309:12)
    at readableAddChunk (_stream_readable.js:284:9)
    at Socket.Readable.push (_stream_readable.js:223:10)
    at Pipe.onStreamRead (internal/stream_base_commons.js:188:23)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:10830) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:10830) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
✨  Done in 5.37s.

@hrgui Thanks for reporting! Looks like it's an ESBuild version incompatibility. It was updated to 0.12 in latest Vite but Vitedge still uses 0.11.
Try adding this to your package.json (remove yarn.lock and node_modules before installing everything again):
  "resolutions": {
    "esbuild": "0.12.6"
  },

I'll release a fix soon.

Thanks, the resolutions did help.

Should be fixed in 0.13.1

Thanks, confirmed it was working.


The user does not have any hints after playing again

Steps to reproduce:
Under the start round do the following steps

Ask user if wants to play again
Choose a year
Choose a song/s
Round starts
Hint count did not reset

Actual result:
Total hints available: 0
Expected result:
The user will have another set of Three (3) Hints if he wants to play again.

Fixed: hint is 0 when playing again


Remove --variant option when meltano add --custom is used

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/3458
Originally created by @tayloramurphy on 2022-05-02 20:59:38

Pat brought this up in https://gitlab.com/meltano/hub/-/issues/247+, but the --variant option doesn't make sense when a user is adding a custom plugin.
We should either disallow that option or ignore the input and print a warning.

View 2 previous comments from the original issue on GitLab

Still relevant


Request for safe mkfifo function

As far as I know, mkfifo(3) is just a wrapper around mknod(3). Regardless, a FIFO can be created with mknod.
I think a wrapper function (placed in stat.rs) would look something like this:
pub fn mkfifo<P: ?Sized + NixPath>(path: &P, perm: Mode) -> Result<()> {
    let res = try!(path.with_nix_path(|cstr| {
        unsafe {
            ffi::mknod(cstr.as_ptr(), nix::sys::stat::S_IFIFO.bits() as mode_t | perm.bits() as mode_t, 0)
        }
    }));

    Errno::result(res).map(drop)
}

Alternatively, you could also wrap nix's existing safe mknod function like I did in this code:
use nix;
use nix::sys::stat::{mknod, Mode, S_IFIFO};
use nix::NixPath;

pub fn mkfifo<P: ?Sized + NixPath>(path: &P, perm: Mode) -> nix::Result<()> {
    mknod(path, S_IFIFO, perm, 0)
}

Only on Linux is mkfifo a wrapper around mknod.  Your proposed implementation would be unnecessarily unportable.  What's wrong with using the regular mkfifo function?  That one is standardized.

Only on Linux is mkfifo a wrapper around mknod.

Come to think of it, that does sound familiar. My mistake.

What's wrong with using the regular mkfifo function? That one is standardized.

Probably nothing; I'm just being forgetful and/or ignorant.

@sector-f Would you be willing to contribute a PR adding a safe wrapper for mkfifo? libc already has the FFI definition for it, so all it takes is adding a function for it here in nix. I'd be happy to mentor you through it.

Closed by #774


API calls need to return the time that the api limit will reset

TLDR
I want to be a good citizen with respect to API limit. Because my app has both internal and external concurrency, I can't unless I know when the api limit will reset.
Detailed description
Without knowing when the api limit will reset I can't avoid spamming you, in any customer-facing app functionality (example: shipping calculation)
If I'm making requests in a single threaded single user tool, I can keep track of API usage & timing and it will more or less work (although I'll still occasionally spam you when another app is using up calls)
But for the things like shipping rate calculation, I can't get away with sequential calls to the api, it adds too much latency to a process that already typically has 3-7 seconds latency. To be a good citizen I want to fire 1 api request, check the limit, then fire the rest in parallel. Thus my app has internal concurrency
I used typhoeus/hydra to do this, setting the concurrency to 20 instead of the default 200 and adding an on-complete to each request to pause/cancel the hydra if any request hits the api limit.
However, if there is not enough requests left, I have no idea how long to sleep. Even if I always bail on requests instead of sleeping and retrying, the web app itself still has however much external concurrency we buy on heroku -- the minimum is 3-4 for a free app, using unicorn. So if 2 or 3 requests overlap, some of them will end up spamming you (unless I wanted to make it so my whole web app stalls for 5 minutes whenever I bump against the api limit, which my clients would not be very happy with)
If you were to tell me in a header in each api response the time the api limit is going to reset, I could track that globally using memcached, and be a good citizen. All incoming requests to my app could check the api call headroom & the time when it will reset and decide whether to wait for the reset or bail. I would occasionally spam you when some other app bumped against the api limit, but usually with only 1 request in a 5 minute block (occasionally with a parallel block of requests when the other app used up the limit in between my checking and firing my parallel block of requests)
My clients (who are also your clients) would benefit, because the app will seem faster under load (requests only bail when they have to, and only stall as long as they need to)
If you add this header, I promise to package & publish on github my typhoeus-based client that uses it to be a good, mostly non-spamming fast api consumer.

This would be an appreciated feature. I believe the limits are now 500 requests / 5 minutes. I tried using https://github.com/Fivell/activeresource-response but had no luck.

The API call limit is a leaky bucket algorithm with a bucket size of 40 and a leak rate of 2/sec. The number of calls remaining are represented in an HTTP header value.

I see. I'll look closer into accessing the headers via this gem later.
Thanks!
On Mon, Apr 24, 2017 at 8:40 PM Jamie Dwyer<EMAIL_ADDRESS>wrote:

The API call limit is a leaky bucket algorithm with a bucket size of 40
and a leak rate of 2/sec. The number of calls remaining are represented in
an HTTP header value.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Shopify/shopify_api/issues/51#issuecomment-296867361,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHRjwhe6XADJlKXyekQeYxGiQYW0cb8ks5rzU7vgaJpZM4AtJed
.


[PR][CLOSED] Fix and update how to set-up CI Server

 Issue by geunsik-lim
Thursday Jun 07, 2018 at 05:40 GMT
Originally opened as https://github.sec.samsung.net/STAR/TAOS-CI/pull/4

It's trivial.
This PR is to update the existing instruction guide to set-up CI server.
Changes proposed in this PR:

Updated the existing CI server manual

Self assessment:

Updated document
Fxied typos

Signed-off-by: Geunsik Lim<EMAIL_ADDRESS>
geunsik-lim included the following code: https://github.sec.samsung.net/STAR/TAOS-CI/pull/4/commits

:octocat: cibot: Thank you for posting issue #21. The person in charge will reply soon.


[hash] Remove hash optimizations

Spoke to discord staff about icon hashes and they said not to rely on it being a hex string. This means our optimizations will break when converting to bigint, should they ever change their hash algo. This should get addressed and be left as a string.

Nevermind, discord has decided to mark it as a hex string to allow us to keep optimizations


Fix update PR to 3.7.12

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Closes #16

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge/ccache Ready for review. I've fixed the update bot's PR by adding sed and a trivial patch.
I'll open a PR try and upstream the patch shortly.


design discussion: goal for per-dependency license enforcement

I have a need at my company which I think is somewhat common, and think this feature would fit well into the maven-license-plugin.
Feature:

take a java resource uri with a list of allowed package/version/regexes and licenses
optionally warn/list/fail a build on license matching against those packages

This should not conflict with the existing check goal which ensure that all your source files have your license, this is about ensuring your dependencies have licenses which don't put your project at legal risk.
CNCF already does something similar for Golang here , and I think SPDX may be an acceptable format, but what we serialize the data into doesn't matter so here as whether you think this would be a good fit to be a new goal for this plugin or not. What I foresee is just including some default of 'allow all permissive open source licenses and warn if your dependencies/transitives have proprietary ones', and allow organizations like mine to just provide a resource jar with our own special cases.
I'm happy to take on this work, just wanted to discuss design with you all before opening a big PR.

Hi @rremer !
This need already popped up in the past, not described as good as you are describing it right now but it was a similar need.
Of course this would be a nice addition to the plugin and if you are willing to take on the work I am opened for that.
I will be able to review PRs and also release as needed if your testing require to have some released artifacts from central.
Regarding the new goal... I don't know... I like the idea of having just one check goal. But to keep backward compatibility, we could add more options to the plugin to enable additional checks. I foresee that there could be more than 1 additional check that we could eventually enable and each new "check" could perhaps need some new parameters also.
I'll let you think about it :-)
Thanks for the help! Really appreciated!

Hello @rremer !
I have read your answer 2 days ago but forgot to answer. Sorry!
I agree with you that the hierarchy of the mojos right not does not fit what you need to do because the abstract class is heavily doing pre processing stuff related to license and scanning and passes the execution to the sub-plugins, either a check or format...
So yes indeed, to be able to reuse some of the parameters in the abstract class this would be a good idea to rename it and extract code in a new super class (or in a more specialized abstract class as you prefer).
If I understand your config correctly, you would define in the <dependencies> section the list of compatible licenses allowed for the dependencies, and then you could add some exceptions in case a dependency has a another license that is acceptable ?
Questions:

I guess you would need also to support some include / exclude sections with the commonly used pattern for dependencies ? (i.e. org.slf4j:*, org.slf4j:slf4j-api, etc)  ?
what about dependency scopes ? How you would determine which dependency to include by default ? Would it be limited to runtime ones ? or compile ones ? what about this weird system scope also ?

re: Abstract refactor, my thinking exactly
re: scope - interesting point. Yeah that should definitely be a configuration param, although provided would obviously not be an option, and system could be an option and just up to the dev to ensure that their CI or local had the same jars that they'd be running with. Obviously compile and test would be the only interesting and generally-useful options here. I'm thinking that compile AND test would be the defaults
re: splat/regex, I was actually thinking not to support complex regex here, as it erodes your confidence that you're letting dangerous licenses through. For complex usecases, it could be a handy syntactic sugar, but I think being explicit is safer (how would seeing an exception for com.* make you feel? Or how about com.oracle.*?).
re: codehaus - I was actually surprised to see new commits there, and it seems you had the opposite feeling about 'the Codehaus banner' than I did... I thought codehaus was sunsetted? At least, all the major plugins/libs I used had been ferride off to other orgs and there were several announcements about shutting down the website, etc.

I am sceptical about the test scope... I.e. where I work, we are really checking licenses of what we put inside our distributed zip file (packaged application). But what is used for testing is less strict and we do not check licenses there, except for example in the case where a license would prevent commercial use. What I mean is that the license check for the distributed application might be usually more restrictive to the license check required for the test scope (if it is even required).
Maven already has a widely known and accepted pattern to declare dependencies and patterns. I would prefer that pattern gets reused because this is what users are used to. Note: I am taking about patterns to filter goupIds and artifactIds here, not patterns relative to imports. I think your example was about being able to filter dependencies.
For example with the maven assembly plugin you can have such syntax for the patterns. This is a known and supported pattern.
    <dependencySet>
      <includes>
        <include>org.terracotta.statistics:statistics</include>
        <include>com.fasterxml.jackson.datatype:*</include>
        <include>org.terracotta:*</include>
      </includes>
    </dependencySet>

For the test scope, we're just discussing the default here which I'm on the fence about. I don't think we disagree about it needing to be a configuration parameter in the mojo, and that it would need to be a list of scopes it took. I realized also that I think most folks care about runtime more than anything, it implies what your app/lib is shipping which is when you'd get into legal trouble (e.g. what is published).
For the exceptions configuration, I considered the single-line-per-exception approach. It is indeed common, I just personally think it's less legible while being more compact. Either syntax could support splat *. I'll support that either way, and it would just be up to the user whether to condone use of the syntax or not (similar to like you say package import splats, some folks do it and that's their choice). Internally, the list of dependencies to check will be its own function, so I don't mind if we change our minds on how to parse various syntaxes as we go. I'm uncertain what public apis maven exposes for parsing syntax like either of these, so maybe that could help inform your decision as to what I should implement.

For the test scope, we're just discussing the default here which I'm on the fence about. I don't think we disagree about it needing to be a configuration parameter in the mojo, and that it would need to be a list of scopes it took. I realized also that I think most folks care about runtime more than anything, it implies what your app/lib is shipping which is when you'd get into legal trouble (e.g. what is published).

Exactly 👍

For the exceptions configuration, I considered the single-line-per-exception approach. It is indeed common, I just personally think it's less legible while being more compact. Either syntax could support splat *. I'll support that either way, and it would just be up to the user whether to condone use of the syntax or not (similar to like you say package import splats, some folks do it and that's their choice). Internally, the list of dependencies to check will be its own function, so I don't mind if we change our minds on how to parse various syntaxes as we go. I'm uncertain what public apis maven exposes for parsing syntax like either of these, so maybe that could help inform your decision as to what I should implement.

I don't know either for the api: because I have only used them in xml. But if several plugins are supporting such pattern, this should be already in the api I guess. Probably this should be similar to the include exclude rules in this project that are using the maven api and ant-like pattern. All of this is part of the maven api. The goal is to not disrupt the user experience with a new concept people will have to learn when they already know something that exists and is already used "by convention" in several plugins :-)
I would perhaps have a look at the assembly plugin for filtering. They have a quite complex use case so all our answers should be there.


Camera viewport can capture mouse while modal dialog is active

MCEdit version: <IP_ADDRESS> (commit d6d125f3713c6aced5cdc9fda00a6833939a8e5b)
MC version: 1.8.1
Python 2.7.10
pygame 1.9.2b8
Gentoo Linux, XFCE4 with xfwm4 window manager
Steps to reproduce:

Load a level, find or place a block that opens a modal dialog when double-clicked (e.g. sign or chest)
Hold right mouse button to capture the mouse for camera control
Double-click the aforementioned block to open the modal dialog. Keep the right mouse button pressed still
Move the mouse cursor outside the modal dialog
Release the right mouse button

Expected result:

Nothing. The camera viewport shouldn't be able to capture the mouse while a modal dialog is open.

Actual result:

The camera viewport captures the mouse. At this point MCEdit essentially becomes unusable. The mouse cursor is hidden and even though it can be moved, button presses do nothing, so the modal dialog can't even be closed. The only solution seems to be to quit MCEdit (which is actually difficult while the mouse is captured; one option is to kill the process from another user's session, another option is to press F6 to open the screenshot dialog, which releases the mouse temporarily, and close the MCEdit window).

Although the last few reproduction steps might seem a bit convoluted, it's quite easy (for me at least) to trigger this bug unintentionally. This causes me to have to restart MCEdit often.
EDIT: Found a potential fix: #725.

I can't reproduce this on my side on Ubuntu (Gnome and Unity environments).
Mint 17.2 (Cinnamon desktop) does not have this behaviour, nor openSuSE 13.2 (KDE).
Note that we have a support for moving/resizing MCEdit window on some Linux desktop environments (Cinnamon, Unity, Gnome and KDE), but XFCE4 is not yet implemented. (I need room on my machine for that...) The console shall display the message: Your desktop environment is not yet supported for window sizing/moving.
Also, the ideal pygame version for MCEdit is 1.9.1. Later versions may work.
IMO, the behaviour shall be not opening the widget when the camera control is requested, since the camera control came first in the event queue.
Anyway, thank you for the report (and the fix proposal) :smile:


Feat: Force Push UI

Problem
There are two scenarios where this is applicable:

BinSync messes up and did not track a change you made to a function or struct
You did not have BinSync open when you made changes to something

Now you need to force push some data to the BinSync repo since it was not tracked. The first problem is that the current UI of BinSync only shows functions and globals (including structs) that were changed by someone... so how could you click force-push on it if it's not shown in the table.
Proposal
To fix these issues, we need to make a Functions and Globals table that looks just like the BinSync Control Panel tables in a popup.
These two tables should show all the functions and globals in the whole program. You should be able to select each many functions/globals. Then after selecting them you should be able to click a Force Push button. Something like this:

The backend does not need to be completed in this task. Instead, proving that selecting the functions/globals returns a list of all the selected objects.

I would like to also request a "Push current function" button for convenience :)

Closed with #161


gandi: fixed versions errors

getRecords() now uses the last active version (in case something hapenned in the meantime).
Should fix : rancher/rancher#9122

LGTM 👍


[SUPPORT] Hudi table COW taking up significant space for a small table

Describe the problem you faced
Hey guys, I tried to run DeltaStreamer on EMR to capture changes in MySQL through AWS DMS and store them COW on S3. I tried to run it for a table with 30,000 rows and 9 columns, which takes up ~6M on MySQL, but on S3 the Hudi table's folder takes up >10 GB... Did I configure something wrong?

To Reproduce
Steps to reproduce the behavior:

Follow basic setup described in this blog
Insert 30,000 rows into MySQL and wait until AWS DMS captures the changes with an additional column "timestamp" added for ordering
Use this command to start Hudi:

spark-submit
  --jars /usr/lib/spark/external/lib/spark-avro.jar,/usr/lib/hudi/hudi-spark-bundle.jar,/usr/lib/hudi/hudi-utilities-bundle.jar
  --class org.apache.hudi.utilities.deltastreamer.HoodieDeltaStreamer
  --packages org.apache.hudi:hudi-spark-bundle_2.12:0.11.0,org.apache.spark:spark-avro_2.12:3.2.1
  --master yarn
  --deploy-mode client
/usr/lib/hudi/hudi-utilities-bundle.jar
  --table-type COPY_ON_WRITE
  --source-ordering-field timestamp
  --source-class org.apache.hudi.utilities.sources.ParquetDFSSource
  --target-base-path s3://mysql-data-replication/hudi_HAT/CUSTOMER
  --target-table CUSTOMER
  --transformer-class org.apache.hudi.utilities.transform.AWSDmsTransformer
  --continuous
  --hoodie-conf hoodie.datasource.write.recordkey.field=C_CUSTKEY
  --hoodie-conf hoodie.datasource.write.partitionpath.field=C_CUSTKEY
  --hoodie-conf hoodie.deltastreamer.source.dfs.root=s3://mysql-data-replication/HAT/CUSTOMER
  --payload-class org.apache.hudi.payload.AWSDmsAvroPayload

Expected behavior
The table takes up 6M on MySQL, so I expect the Hudi table to be <30M on S3.
Environment Description

Hudi version : 0.11.0

Spark version : 3.2.1

Hive version : should be irrelevant, but 3.1.3

Hadoop version : 3.2.1

Storage (HDFS/S3/GCS..) : S3

Running on Docker? (yes/no) : no

likely a lot of small files were created. @Xiaohan-Shen how many files were created in S3? and what do the file sizes look like?
cc @zhangyue19921010 @yihua this can be a good point for diagnositc reporter to capture, as in how file sizes distribution look like, to help diagnose parquet size setting issues for example.

I just figured out the problem: I used the primary key field for partitioning, so it was creating one partition for every row. My bad.


glow: 1.2.0 -> 1.2.1

Motivation for this change
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

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

Result of nixpkgs-review pr 104832 run on x86_64-linux 1

1 package built:

glow


python312Packages.trimesh: 4.4.1 -> 4.4.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.trimesh is: Python library for loading and using triangular meshes
meta.homepage for python312Packages.trimesh is: https://trimsh.org/
meta.changelog for python312Packages.trimesh is: https://github.com/mikedh/trimesh/releases/tag/4.4.2
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.4.2 with grep in /nix/store/hlxafwggvr4lc4h6c8f3wj0amhac3b0p-python3.12-trimesh-4.4.2
found 4.4.2 in filename of file in /nix/store/hlxafwggvr4lc4h6c8f3wj0amhac3b0p-python3.12-trimesh-4.4.2

Rebuild report (if merged into master) (click to expand)

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath

python311Packages.pyrender
python311Packages.trimesh
python312Packages.pyrender
python312Packages.trimesh

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hlxafwggvr4lc4h6c8f3wj0amhac3b0p-python3.12-trimesh-4.4.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.trimesh https://github.com/r-ryantm/nixpkgs/archive/9167fc1f136887ba952bf29e78ae1a7d1be977b2.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/9167fc1f136887ba952bf29e78ae1a7d1be977b2#python312Packages.trimesh

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hlxafwggvr4lc4h6c8f3wj0amhac3b0p-python3.12-trimesh-4.4.2
ls -la /nix/store/hlxafwggvr4lc4h6c8f3wj0amhac3b0p-python3.12-trimesh-4.4.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

8 packages built:

python311Packages.pyrender
python311Packages.pyrender.dist
python311Packages.trimesh
python311Packages.trimesh.dist
python312Packages.pyrender
python312Packages.pyrender.dist
python312Packages.trimesh
python312Packages.trimesh.dist

Maintainer pings
cc @gebner @pbsds for testing.

opened first: https://github.com/NixOS/nixpkgs/pull/325939


#fix： glc use example error

hello xuri ....  不小心赚了你的一波star

Codecov Report

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

@@          Coverage Diff           @@
##           master      #1   +/-   ##
======================================
  Coverage    73.8%   73.8%
======================================
  Files           1       1
  Lines          42      42
======================================
  Hits           31      31
  Misses          7       7
  Partials        4       4

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 6b2677e...7776a0e. Read the comment docs.


perf(computed): avoid updates when source signal value is restored

This PR relies on changes from #14.
Consider the following situation:
const s = signal(false);
const c = computed(() => s.get());
c.get();
s.set(true);
s.set(false);
c.get(); // <-- should not recalculate

In the last line c.get() should not cause computed to perform the getter because the value of s is restored.

Close due to #19 changes, the solution is no longer feasible.


Some clicks (changes) in popover closes it when it's used inside a dialog

Bug report
Current Behavior

having a form with popover inside dialog
form has selected tags list, popover allows to select/remove tags
adding tags from popover works fine (setState([...tags, tag]))
removing tag makes popover close (setState(tags.filter((t) => t !== tag)))
works fine outside of the dialog

Expected behavior
Removing case should not close popover that is inside a dialog
Reproducible example
https://codesandbox.io/s/little-hill-l9fmdl?file=/src/App.tsx
Suggested solution

Additional context

removing tags list before popover fixes the issue
adding modal to popover fixes the issue

Your environment

Software
Name(s)
Version

Radix Package(s)
@radix-ui/react-dialog
1.0.4

Radix Package(s)
@radix-ui/react-popover
1.0.6

React
n/a
18.2.0/17.0.2

Browser
Chrome
114.0.5735.198

Assistive tech

Node
n/a
18.6.0

npm/yarn
npm
9.5.1

Operating System
MacOS
13.4.1

Hi man, have you solved it? I have same problem.

Used modal=true on popover

Used modal=true on popover

Thank you so much!

@artaommahe I love you so much.

Hey, the issue seems to be the same as https://github.com/radix-ui/primitives/issues/2180. Upgrade to the RC version should work
Codesandbox

Duplicate of #2180


Test CLA

Testing CLA functionality.
DO NOT MERGE.

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


Usercentric custom UI issue (iOS)

Describe the bug
recently in our team, we started to build our custom UI for the user-consent using the SDK in flutter, but when we want to render the widgets based on the cmpData of the UserCentric, just in iOS the format of the data is wrong, the category object holds a description field which should contain a simple text but in this case, is like the image below:

To Reproduce
Steps to reproduce the behavior:

use the Usercentric to implement a simple custom UI on iOS
check the category object-> description field

I would appreciate it if you take a look and see what could be wrong.

hi @bahag-roostap
sorry for the delay in answering.
we have just released a new version (2.7.10) of the SDK that solves this issue.
Could you please try it out and see if things are working as expected?
If not, please do let us know so we can have a look.
Thanks!

Thanks for the response, I'll check and let you know ASAP :-)


⚠ Bofrost.be has degraded performance

In 40087ff, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 984 ms

Resolved: Bofrost.be performance has improved in 31b18ad after 8 minutes.


FIXME: filtering source languge from language tag list doesn't refresh tag picker in UI

https://github.com/aws-samples/aws-media-insights-content-localization/blob/9a489fd6187b16c46948656c40198ebfa76c0aab/src/views/UploadToAWSS3.vue#L472
//FIXME: filtering source languge from language tag list doesn't refresh
// tag picker in UI.  So, if source language is English to start, English is
// removed from the translation target languages.  When source language
// is changed to Spanish, Engish is added back to the tags on the Vue
// Translation component but Engish tag is still missing on the tag
// picker.  For now, leave the source language in the list.
//.filter(x => x.text !== this.sourceLanguageCode)

this has been fixed


Question on Scheduler with specific start date

I have a question regarding a schedule that has a specific start date.
For instance if I schedule an action below:
MyRegistry.Schedule(Task).ToRunOnceAt("27/11/2014 11:30").AndEvery(5).Minutes()
Does the above code mean that the scheduler will execute once on that day at 11:30 and every five minutes from then (11:35, 11:40, 11:45 etc), or does it mean it will run once on that start date and every five minutes from when the schedule was created?
I ask because I seem to notice that the code for .OnEvery(x).Minutes() seems to be based off the time the schedule was created as opposed to the date set in the .ToRunOnceAt(xxx) value.

Yep, it will run at 11:30 and then every 5 minutes from then


Inserting into TES4 archives

hey so I see that TES4 archives are a bit different and I cannot figure out how to do this properly. I create the key like this
pub(super) fn create_key<'a>(path: MaybeWindowsPath) -> Result<ArchiveKey<'a>> {
    path.0
        .into_bytes()
        .conv::<BString>()
        .conv::<ArchiveKey>()
        .pipe(Ok)
}

but I when I try to insert by it it says that it doesn't implement Into<Bytes<'a>>

Post the full compiler error

I have figured it out, I will later post examples from my code into this issue for future user reference


Creating PWA for the website

PWA is intended to work on any platform that uses a standards-compliant browser, including both desktop and mobile devices.
Refer this video - https://youtu.be/E8BeSSdIUW4

PWA is intended to work on any platform that uses a standards-compliant browser, including both desktop and mobile devices.
Refer this video - https://youtu.be/E8BeSSdIUW4

I would link to pick this one

I would link to pick this one

Assigned!
Keep me updating!
Also, you can join our Discord for any queries!


⚠ Bofrost.be has degraded performance

In 37d85c9, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2386 ms

Resolved: Bofrost.be performance has improved in c970af5.


added basic validation for validateMeasurement

What type of PR is this?
/kind feature

What this PR does / why we need it:
This PR implements valideMeasurement function
Which issue(s) this PR fixes:

Part of #1746
Special notes for your reviewer:
WIP
Does this PR introduce a user-facing change?:

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

go test .
package k8s.io/perf-tests/clusterloader2/api
        imports k8s.io/perf-tests/clusterloader2/pkg/measurement
        imports k8s.io/perf-tests/clusterloader2/api: import cycle not allowed

/assign @marseel

@rahulii So measurement package is importing api package. What we could do is to move validation.go to separate package so we don't have import cycle. For example moving "api/validation.go" to api/validation/validation.go" and changing package from "api" to "validation" should help.

@rahulii So measurement package is importing api package. What we could do is to move validation.go to separate package so we don't have import cycle. For example moving "api/validation.go" to api/validation/validation.go" and changing package from "api" to "validation" should help.

Okay and then maybe change the import path of all the places where validation maybe be used?

Ah , @marseel there's an issue! validation.go uses types.go for all the Types and config(eg Namespace,etc) which is in api package , and many files use types.go as well!
./validation.go:123:45: undefined: Object
./validation.go:135:54: undefined: NamespaceRange
./validation.go:146:49: undefined: TuningSet
./validation.go:184:51: undefined: Measurement


Adding feedback button on side nav / issue #401

Going to switch sv

Working with jman to get proper canny icon, will reopen briefly


GUI does not load

When I try to open the GUI using python -m cellpose using the environment given in the environment.yml file the GUI is simply a white window.

is there any error message on the command line? what operating system are you using?

this was related to cv2 conflicts on mac, solved with downgrading cv2


Add coordinates of features to pop-ups

It would be nice if when you click on any feature it provides the precise coordinates in the pop-up (not required fo modification or mutant as these are already in the description)

I've added the coordinates to the tooltip when you mouse-over a feature.  Adding a separate popup when you click was tricky.  Is this OK?:

It's easy to re-format.

perfect!


Ability to add private registries

I would like to pull container images from private hubs but currently there is no way to do that.

Thanks @rmb938 .
This is a duplicate of #23 ! Moving the convo there.

Private registries would be great.  Should rename issue or maybe this isn't what @rmb938 meant?

@jeffdm Initially just private registries but both would be nice

+1

For the record, what's the issue with private registries?  Is there a work-around to enable?  I tried just opening a cli (by clicking the whale) and doing a docker login.  But it errors out.

docker login -e  -u  -p  my-docker-registry-url
FATA[0042] An error occurred trying to connect: Post https://<IP_ADDRESS>:2376/v1.17/auth: dial tcp <IP_ADDRESS>:2376: i/o timeout

+1

Maybe this can shed some light on the error you're seeing, @dskyberg http://stackoverflow.com/questions/26710153/remote-access-to-a-private-docker-registry

:+1:

Moving the discussion over to #232

Focusing this issue on private registries

+1 for private registries

+1

+1

+1

+1

+1

+1

+1

+1 for private registries. This is necessary for my organization.

+1 This would be a huge benefit to our organisation

Is there a workaround for pulling images from private registries ?

+1

:+1:

+1

This is the only reason I can't really use kitematic in my organization.

+1 on this. We'd love to use kitematic, but definitely not without private registry support.

+1 would love to be able to have my company use kitematic with our private registry.

+1

+1

+1

+1

+1

+1

+1

+1

+1

Probably should be merged with: https://github.com/kitematic/kitematic/issues/232

@FrenchBen this issue has lower number #232 then duplicate?

@KostyaSha Yup and why I commented on here- #232 should be merged here is what I meant to say :+1:

+1

For those calling to merge #232 into this issue, note that the owner of this issue specifically created #232 to separate out the two related concerns.

@dannc not sure if I follow.
#210 - Ability to add private registry (OP comment: I would like to pull container images from private hubs )
#232 - Allow pulling images from private repositories
How are these not related?

I believe the breakdown is like this:
#210 (this issue) is now focused on providing for the ability of kitematic to interact with a private registry (i.e. one that you installed in your own local environment)
I'm guessing other hosted registries (hubs) such as Quay.io and Google Container Registry would also be covered under #210 as well.
#232 Is focused on providing for the ability of kitematic to interact with a private repository.   A private repository is different than a private registry in that a private repository is just like any other image repository on DockerHub save for the fact that it's not publicly searchable and is only accessible to the organization that owns it.
These are certainly related issues but not the same issue.  I believe one could solve either of these issues separately without solving the other.

@dannc I believe the latest Kitematic currently works the private user/org repos. Should this issue be closed then?

@FrenchBen this issue is about repos hosted on private hub, not private repos hosted on docker hub. We still can't use a private hub.

@stefanhong do you have a private hub I can look at?

@FrenchBen just install https://hub.docker.com/_/registry/ on your own server

@dannc @stefanhong There is a misunderstanding here.

For example for you to get an image from CDN you need to know the exact image name, otherwise you get nothing.
Registry is the same thing, you need to know the exact name of the image before you can pull it.

I guess I'm quite confused.  This issue started out with a request that seemed a bit vague.  Through a few questions @jeffdm clarified a bit more and changed the title to  Ability to add private registries and private hub repos.  After some time, he then further refined the title to be Ability to add private registries and his subsequent comment in this issue read:
Focusing this issue on **private registries**, for private DockerHub repos, please see #232

In #232 you created a PR ( #1076) to be able to set and use a "private Repo URL" and then subsequently closed it for not being applicable at the moment.
In the screenshot included of how the setting would look, you have a new field for "Docker Registry URL"  which defaults to https://hub.docker.com/v2 (which I believe is the base URL on DockerHub from which you can search for repositories).
What I think #232 was meant to address was something different.  Say I created a private repo on DockerHub for an image that I didn't want to share.  Being able to access that repo would at least require that a user of KiteMatic would be able to login so that login credentials could be matched up with the permissions of the private repo there.  There's probably more that needs to be done to enable access to private repos on DockerHub but I can't really speak to that as I'm not familiar enough with the code.
The concern in this issue request is now left being that I want to access my images/repositories hosted in my local registry (not hub.docker.com).  Looking at your PR, it seems right on target as a potential fix for this issue!  In it, I could specify 'https://localhost/v2" and I believe I would be able to search for images in my locally hosted registry and create containers with them.
That's what I think most people are asking for in the current definition of this issue.  I'm sure they'd also like to be able to search for and create containers for privately repositories hosted within DockerHub, but that's what I think #232 was created to address.

@dannc is correct. Most of us host our own Registry, and want to be able to access images on that Registry. It does not have to do with accessing private images/repos on Docker Hub.

@dannc The PR you mentioned was closed as it was created without much knowledge of the CMS/CDS mentioned above. I had the exact same idea as you did regarding pointing Kitematic to the https://localhost/v2 url when the PR was created. The issues mentioned in the comparison of CMS/CDS is what makes it very difficult and makes the PR unusable.
@jbw91 @dannc maybe what would help is the current usage of your local registry? How do you 'view' images stored? Do you just 'know' what to pull?
Registry being a simple CDS, has no Auth, no Search, no list of User images. This is the 'magic' that a CMS (Hub) adds.

@FrenchBen, Docker Trusted Registry adds the same functionality as Docker Hub with users, search, etc. The old Registry didn't have all that, this is true.

@FrenchBen Now I understand the discussion about CMS/CDS better.  Thanks for that.
Mostly just 'know' what to pull.  I hadn't realized that search wasn't implemented in the private registry.  That's unfortunate.
I have been able to list tags for a specific image:
curl -k -X GET https://localhost:5000/v2/<repo_name>/tags/list

That doesn't give you image/repository list capabilities like you'd have on docker hub but at least it would give a way for someone to search for a specific image and create a container from it using KM.

@jbw91 Now you're talking about a different product - Docker Trusted Registry vs Private Registry (discussed in this thread)
@dannc that's exactly it, glad the discussion made more sense. :)
The tags list would only show the tags for a specific image, you'd have to specify the exact image name first or get an image not found if you made a typo!

@FrenchBen In my case we know exactly what images we have on PR, and the tags we need.  While being also to search from a CMS is nice, we will be very happy just being able to add images manually so we don't have to type commands all the time.

@stefanhong How do you envision Kitematic knowing about this list of available images, so they could be displayed on the Create/New page?

@FrenchBen Maybe an "Add" button under "My Repos" section to add a specific image url manually?

For knowing about the list of available images that can be displayed on the create/new page, I'd be OK with having to search for the exact image name and having an empty list if they don't specify the image name correctly.
Not ideal really but better than nothing I would think.  Of course checking the specified private registry to see if it responds to e.g. /v2/_catalog (Docker Trusted Registry or some third-party registry such as Quay.io or such) would be helpful.
Our organization is actually using an Artifactory version which also serves as a docker private registry (as well as has authentication/etc).  The current version doesn't have search capabilities but it doesn't mean that they wouldn't offer it in a future release...

Sorry if I am missing something, but it looks like the v2 api for the docker registry does support listing available images.  https://docs.docker.com/registry/spec/api/#listing-repositories
Even just listing the local repository with something like 'docker images' would be an improvement.

@lhorne That's correct it lists the images, but you cannot search them. As an application we cannot add half-working features, as it would break the current flow.
Additionally you would also be missing the authentication part of it.

+1

+1 for Kitematic to support private registries

Would love this as well.

+1

+1 for Kitematic to support private registries.

+1

Please use the 👍 feature of Github - Having these +1 added all over the place does not help - Locking the conversation until a proper proposal has been drafted.

similar issue in Dockerfile. See issue #1733

+1

This issue has been open for over a year and is basically preventing enterprise from adopting kitematic as most of their registries are on premise. @FrenchBen and you will not add a "half-baked" feature? Why aren't you baking it? You would think enterprise are Docker's most important customers.

@clatko Would you accept, at the enterprise level, a half-bake product where things work only 1/2 way?
As mentioned a few comments above (https://github.com/docker/kitematic/issues/210#issuecomment-156210361 & https://github.com/docker/kitematic/issues/210#issuecomment-156252142) the issue is not with the registry but handling all of the components that go with it, such as authentication.
See:
https://docs.docker.com/registry/spec/auth/token/
ps: The best way to see it implemented is to do it yourself. Please open a PR with what you believe is the bare minimum. I'll be happy to review it and merge it if appropriate.

since i'm not trying to sell it, yes, i would take a half baked solution. i forked the repo and am trying to get authentication working. i'll probably not have the time to see this through.

Any help is appreciated @clatko - thanks for taking a shot at it :)

+1

+1

+1

+1

+1

+1

+1

+1 for private registry access

+1

I am in need of this feature as well.  We would like to adopt this technology but need the ability to use Kitematic to access the private regitry

+1

+1

+1

+1
We spun up https://docs.docker.com/registry/, added username/password authentication (tied into an internal authentication database, which is why we cannot use DockerHub.com), but then could not work out how to make Kitematic work with it. Unfortunate.

@alankent the user/pass auth you specify are tied to a certain internal auth endpoint that may be different for each.
If you want to write up exactly what it should expect and how you're making it work and that users are happy to have that EXACT same internal auth db, I'm happy to provide the changes needed for it to work.
The biggest issue is that no-one can agree on that internal auth db thus making it very difficult for Kitematic to be flexible enough to auth against it.

Kitematic should be able to authenticate, search and pull from Docker Trusted Registry.  Will it ever be possible?

+1

+1

+1

+1

+1 Any update progress with this?

+1 Absolutely :-), any alternatives available yet ? Sounds like a serious 'need' for the users

+1

+1

+2

+1

+1 Any updates on this?

+1

+1

+1
See issue #3175 for further issue (even if you manually pull from private registry, can't start container)

+1

+1

+1

There is a reason Github added Emoji reactions. Please don't spam +1 and trigger useless notifications for watchers.

+1

second most liked feature ever

+1
Need pull from private registries.

We need this feature!

+1

How is this coming along?..

4 years. Really?

+1

Any updates guys?

If you look at the repo, you will notice that this is not being developed any longer. In the last two years all changes were bumping dependencies version and nothing else. Which means that most likely there are no updates.


Actually support and test the ucontext code path

TBR - I have dependent changes, and I need to figure out whether our CI builds all changes that land into main or just the tip of the multi-change merge.


Shiny app improvements

Small things, for consistency:

In the environmental covariates, "Where do these covariates come from?" would be better under the map (as it is for the species intensities)
Ideally the maps should all have the same size & margin sizes. Putting the labels for the species occurrences below the map would help here

Fixed in the latest run


Config plugin for AWS

Provide an implementation of IConfigPlugin, adding support for a protocol named "s3" loading configurations from AWS S3 buckets. The plugin should support argument based key authentication.

Welcome :-)
For this task, could you make trac-plugins/aws-config as a new sub-module and add a flag in gradle/plugins.gradle to turn it on and off. There is an example in trac-libs/sql-drivers of enabling plugins with these flags.


Register event type decorator example

Added example of the other way to register an event - using a class decorator.

Looks good. Would it be possible to add a short docstring at the top of the file, that explains what's going on? Something that explains that  when you create your own EventDispatcher classes, you can use this class decorator as an alternative way of registering events.

Done!

Thanks Tony!


[BUG] Publishing with "all artifacts" option does not support subtractive changes

Release version
v5.1.4
Describe the bug
When running the publisher, my expectation is that artifacts that do not exist in the source, should be deleted from the remote APIM instance if they exist. This does not seem to be the case. After making multiple changes and then publishing "all artifacts" artifacts that were removed n commits ago remain in the remote instance.
Expected behavior
I expect that artifacts that are in the remote APIM instance but not the artifact repo, should be removed.
Actual behavior
The artifacts are not removed from the remote instance.
Reproduction Steps

Create a commit that deletes a named value
Make another commit that changes something else
Publish all artifacts
Observe that the named value has not been deleted

If you delete an item as part of the commit then it will be deleted from the target environment that the publisher is publishing to. Remember that the publisher picks up the last commit.

I see. Thank you for the quick response. Are there any plans to support a full-sync with the remote instance? We have also encountered situations where resources with dependencies on other resources are not deleted in the correct order if we want to delete both at once, which requires a multi-stage deployment and is not ideal. This is especially problematic when doing deployments that require deletion of sensitive resources (consider deleting a product and an API route that uses that product).

@windy1 - we unfortunately don't support this. Will add to our roadmap for investigation, but it's going to be low on our priority list. See #154 for options, will close this issue in favor of that one.


feat: Define features associated with dependencies

Closes https://github.com/kstasik/schema-tools/issues/71

I will merge it because it's an improvement but i'm not sure about feature names. For example:
semver = ["schematools/semver"]

Semver is needed during openapi merging process. I'm wondering if features shouldn't be more like functionality oriented with few exceptions like git2 registry support. So i'm considering changing semver to something like bump_openapi in the future. It's also worth considering splitting project further to separate packages: codegen, process, validate hmmm...

There are functional feature and there are dependency features.  Functional feature are hard requirements for users - they need a certain functionality, but dependency features are the cause of larger build times and additional dependency hell / risks.  IMO the feature matrix should define both.  Dependency features map directly to real things - added dependencies.  Feature dependencies are more vague, and usually map to a few dependency features- "you cant do X without these dependencies".  This PR defined one functional feature "codegen", and a lot of dependency features, because we want to be avoiding certain dependency subtrees which are unnecessary risk for our need.  I expect we'll eventually define functional features for each of the major schematools commands, but at the moment the biggest risks were the codegen subsystem which we are not using.


what ipe in npiperelay stands for?

I'm wondering what IPE in project name stands for? I imagine that np is for named pipe and relay is self explanatory, but I couldn't decipher ipe?

daft question, it's not np, but npipe as in Named PIPE


Create Dockerfile and build instructions

Create a Dockerfile, Docker images for released version. This can be a manual process for this image for purposes of a Kubecon release. Another release process automation issue will be created.

Can we close this? Imo we have everything of this issue addressed in

Dockerfile: https://github.com/kudobuilder/kudo/blob/master/Dockerfile
Process for docker images for released version: https://github.com/kudobuilder/kudo/blob/master/RELEASE.md (https://github.com/kudobuilder/kudo/pull/120)


Issue uploading files (resumable) through drive API

I'm experience issue uploading files through drive API (resumable mode). Everything was working till the last Wednesday.
googleapis: ^1.0.0

First, bump that dependency to ^10.0.0

I can't update to latest version. I tried with ^8.1.0 version but issue was the same.
Frankly I don't think that will help me because both ^1.0.0 and ^10.0.0 will make same API call for resumable upload.

Is that URL deprecated and if it is will somebody make a patch?

Check out the example here to see if it helps: https://github.com/google/googleapis.dart/blob/master/test_integration/test/storage_test.dart
it's for storage, but the resumable bits should be similar.

It was issue with Drive API which Google back end developer resolved over the weekend.


Fixed Typos

Summary
The UPGRADE.md file contains some spelling mistakes
Full changelog

[Fixed Typos]

Issues resolved
Fixed spelling mistakes improving document

Thanks


Training failed after increasing the number of images in the dataset

Hardware gpu:3070 cpu:i7-10700 memory:96gb power supply: 750W
The image resolution in my dataset is 1280*720 Previously, it worked well when there were 850 images in the dataset. When the number of images in the dataset is increased to 1900, an error will occur in the training. You can see that you can train normally at the beginning, but the Ubuntu system will restart immediately when the PTH file (the first one) is generated. Why?

Could you please provide any other information about this error?

I guess the memory is out of bounds, use htop to monitor the memory.


Don't mix config with docs.

The way config is merged into the rootDocs now results in invalid properties in the resulting swagger.json. This change will also open the door to more configuration (for things like overriding the definition of operation 'id' fields.).
Consider this a 'request for discussion'. If you agree, I'll comb through and fix any tests and documentation.

Hey @cpsubrian I saw all your great PRs for this repository. Would you be interested in taking on a more active role in maintaining it? If you would like more info feel free to ping me on Slack or via email.

Separation was introduced with version 1.0.0


fix: offset and limit params not being passed to the search pipeline

[x] Changes to this PR can be deployed immediately.

https://github.com/Saebasol/Heliotrope/issues/271

All arguments to this function must be required.
https://github.com/Saebasol/Heliotrope/blob/d99e7cd7152b9f1838b29394b3c4166abad20790/heliotrope/database/odm/__init__.py#L113
And can you help me with the commit convention?

would this do ?

Thank you so much for your contribution!

Thank you for being patient with me


Add file_stream response handler

For streaming large static files
Like file() but breaks the file into chunks and sends it with a StreamingHTTPResponse
Chunk size is configurable, but defaults to 4k, this seemed to be the sweet spot in my testing.
Also supports ContentRange same as file() does.

I think it is necessary to add test for file_stream().

There is a test in try_everything.py
Here: https://github.com/channelcat/sanic/pull/733/commits/181977ad4ed8dac3443f5906a44883e035971f2c#diff-b9137c4a6c19839608462a8314657683R68
It just looked what file() does and did the same in regards to tests.
Should he have a better test or more tests?

Is try_everything.py  example?
A test exists in tests directory.

Oh. I see.
There is no test for file() in the tests/ directory either.
That is why I didn't add a test for file_stream() in the tests/ directory.
Should I add a test for both file_stream() and file()?

IMHO,
I think that it is only necessary to test your deliverables.

Added real tests for file() and file_stream() response helpers.

If file_stream() is able to substitute file(), I think it would be better to replace file() to file_stream() in future.

I would like to see performance comparisons for smaller files that don't require streaming before we consider removing file().

Can we move all of the tests to test_response.py? They're both response types so it makes sense to consolidate them there.
Ok, Done.

If file_stream() is able to substitute file(), I think it would be better to replace file() to file_stream() in future.
If file() will be replaced to file_stream(), it is need to post document about replacing.

No, file_stream() is not a direct replacement for file() and is not intended to replace file() in any way.
In my other PR https://github.com/channelcat/sanic/pull/734 the static() helper is modified to have the option of using file_stream() (but only for large files), but it is off by default.

I would like to see performance comparisons for smaller files that don't require streaming before we consider removing file().
As would be expected, performance is decreased for small files that do not require streaming.


Improve graphs for "tight races" between individuals

Introduction
In another issue @SuperTux88 commented on the recent updates to graphs where the "Logged in User" (if known) gets highlighted with a bit thicker line. They said:

I still have one leaderboard where I was racing with another person and we were pretty close for multiple days, but the new percentage view also already improves the visibility with close lines and it's visible as soon as we are 2 or more points apart. So probably good enough.

But continues:

I just had another idea: what if the highlighted line is done with hovering over the names/lines? That could help to also quickly highlight other lines in a big board (without needing to disable everybody else). But I also don't know how easy that is and what it does to performance on big boards? 🤔 So not sure if it's worth it, but if you think it is doable and could be useful, I can create a separate issue about it.

I think it's fair to put in some extra effort for users who are part of a "tight race". I think they are the "Power Users" of this browser extension: perhaps a small part of the user base, but also those who use it the most or to the max.
The Issue
Could we improve the situation for folks in a "tight race"? Can we somehow undo the fact that "only a thicker line for logged in users" now overshadows such a tight race? Without giving up the benefits of the extra highlight?
There's plenty of options to investigate, including but not limited to:

(as per commenter's suggestion) doing the highlight by hovering over legend items and/or lines
(the original suggestion) making this a per-user setting after all
detecting "tight races" and highlighting everyone involved in that tight race
investigate if the Chart.js samples and features offer another way to handle this
introduce extra graphs or graph types (e.g. the "tight race" graph?)
etc.

I welcome input and suggestions, either written or as proof of concepts. Take care however not to go overboard with a PR before we know if a direction is one we want to end up going in.

TBD if this can and should be part of #79 (2023 udpates), which also depends on whether a 2023 edition of AoC will happen at all.


license ?

what's the license of this library ? MIT license ? (https://opensource.org/licenses/MIT)

Yep, MIT!
HxNet was MIT, and some HxNet code is still lying around, so that definitely makes it MIT. I think stuff like this ought to be open and free.

On 9 Mar 2016, at 9:43 pm, yannsucc<EMAIL_ADDRESS>wrote:
what's the license of this library ? MIT license ? (https://opensource.org/licenses/MIT)
—
Reply to this email directly or view it on GitHub.

It would be handy if there was a LICENSE file in the repo. Without seeing one, I assume I cannot use the code (see https://help.github.com/articles/open-source-licensing/#what-happens-if-i-dont-choose-a-license), and can just look at it.

Thanks for the info! I've added one, I think it's in the correct format. Thanks for raising the issue!

On 10 Mar 2016, at 6:46 am, Kenton Hamaluik<EMAIL_ADDRESS>wrote:
It would be handy if there was a LICENSE file in the repo. Without seeing one, I assume I cannot use the code (see https://help.github.com/articles/open-source-licensing/#what-happens-if-i-dont-choose-a-license), and can just look at it.
—
Reply to this email directly or view it on GitHub.


Count characters instead of bytes

For queries such as SELECT "なにか" FROM Y WHERE "なにか" = 'test; which are using UTF-8 characters as column names, counting lengths as byte counts (which len() does) may cause bugs.
For instance, the above query would produce an error Unterminated string literal at Line: 1, Column 47, while the correct column number is 35.
So, simply use .chars().count() instead. Replacing len() with this produces correct output.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

5 of 5 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 89.782%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
8769

Relevant Lines:
9767

💛  - Coveralls


Ps5 revision

The baselines need to be updated to account for the improved labeling of the contour level color bar.
BTW, I checked for compatibility with my recent changes, and there's no problem there.


Hooks installed to global core.hooksPath and enabled in all repos

Description of the bug
When core.hooksPath is set to a path outside the local Git repository (e.g. ~/.config/git/hooks), git branchless init places hooks in the global hooks path which are then applied to all Git repositories.
I don't think core.hooksPath is commonly changed by users, so this is probably a low priority issue. And this may be more of a problem with how core.hooksPath works with non-relative paths, and not git-branchless. Regardless, I thought I'd mention it.
Expected behavior
git-branchless hooks were installed in the repository-local hooks directory (.git/hooks) and applied to the current Git repository only.
Actual behavior
git-branchless hooks were installed in my global core.hooksPath directory (~/.config/git/hooks) and applied to Git repositories where I hadn't run git branchless init.
Version of git-branchless
9861d7093093ae2a92ff087a44ffd273ae051d37
Version of rustc
No response

Hi @evanrelf , thanks for reporting!
From the documentation (https://git-scm.com/docs/githooks), it seems to imply that the hooks at core.hooksPath are the repository-local hooks, because by default this value is $GIT_DIR/hooks, where $GIT_DIR refers to the repo's .git directory. You probably don't want to set core.hooksPath globally; instead, you might want to use a template directory with git init to install a set of base hooks (which could be symlinks, I suppose).
From the documentation, it sounds like if we install the hooks to somewhere other than core.hooksPath, they won't be respected at all. Maybe instead we could surface a warning if core.hooksPath appears to be an absolute path, or is set in a global Git configuration file?

I see that the same issue happens for Git LFS: https://github.com/git-lfs/git-lfs/issues/3240. There doesn't seem to be a compelling solution for this use-case.

You probably don't want to set core.hooksPath globally; instead, you might want to use a template directory with git init to install a set of base hooks

The global hooksPath has been useful for me to ensure my pre-push hook always takes effect, without any manual installation or init template required...

From the documentation, it sounds like if we install the hooks to somewhere other than core.hooksPath, they won't be respected at all.

...but this part ^ seems to indicate there's no way for git-branchless to support this use case (without adding a lot of complexity and assumptions for this edge case) ☹ ...

Maybe instead we could surface a warning if core.hooksPath appears to be an absolute path, or is set in a global Git configuration file?

...so I think a warning is the right thing to do here. If core.hooksPath isn't inside of $GIT_DIR, issue a warning that the hooks may take effect in other repositories. Or something like that.

FYI (mostly for @evanrelf), I think Git's new "config-based hooks" will solve this once they're available. See this discussion.

@martinvonz Thanks for sharing; I wasn't aware of that. That sounds like exactly what I want 🙂


Fix deprecation warnings

This is to fix the deprecation warnings becoming errors from https://github.com/rapidsai/cudf/pull/12548

build

build


Fedora 34 - No package policycoreutils-python

I am installing on Fedora 34 and ran the installer as ./nextcloud.yml -e 'ansible_python_interpreter=/usr/bin/python3' and am receiving this error:
TASK [prep_os : install needed packages] ******************************************************
Thursday 13 May 2021  17:20:14 +0000 (0:00:07.270)       0:00:31.809 **********
fatal: [localhost]: FAILED! => changed=false
  failures:
  - No package policycoreutils-python available.
  msg: Failed to install some of the specified packages
  rc: 1
  results: []

This package is not available but python3-policycoreutils IS already installed but is not being used.

try again. 55c0446e7dcbd
but i'm not shure that this is the only problem.

Thank you very much!
There are other problems, actually.  Trying to sort this out now.  I will provide more feedback and/or diffs as I can get them to work.

There is a minor change in the postgres source and there were missing packages after running prepare_system.sh.
I will submit a PR for the postgres changes.
Another note on Fedora, for some reason, even though the firewall stuff was done with ansible, https was NOT actually open on the firewall.  I had to do a firewall-cmd --add-service https --permanent in order to get the webserver to actually return a page.  See below for the open firewall ports status.
TASK [prep_nginx : open firewall ports 22/80/443] *********************************************
Friday 14 May 2021  20:57:25 +0000 (0:00:04.866)       0:00:23.012 ************
ok: [localhost] => (item=22/tcp)
ok: [localhost] => (item=80/tcp)
ok: [localhost] => (item=443/tcp)

@ReinerNippes:

try again. 55c0446
but i'm not shure that this is the only problem.

AFAICT the package has been renamed to policycoreutils-python-utils. CentOS 8 and similar distros are affected aswell.


Default key bindings not replicated from OS X

There are a couple of keybindings missing from OS X which you'd expect to exist within the editor.
For example:
Ctrl + Left/Right - Jump to start/end of line
Ctrl + Shift + Left/Right - Jump+select to start/end of line

I'm not sure what you mean - Cmd-Left/Right and Cmd-Shift-Left/Right are the standard keyboard shortcuts for this behavior on OS X, which should work in Atom. What OS X apps use Ctrl for this? I just tested with Xcode, and it doesn't use Ctrl for this behavior.

Hmm I'm not sure why you're not able to reproduce this, I've just tried this in Xcode and I was able to use Ctrl for this behaviour. I don't have any keybinding modifications either. I'm using "British - PC" input if that makes any difference

By default (as far as I know) Ctrl+Left and Ctrl+Right are bound to "Move left a space" and "Move right a space" in Mission Control:

After I disabled that behavior, in XCode the Ctrl versions were not jump to the start/end of line, they were move to left/right word boundary.
You can always change the behavior of these keys in your copy of Atom, but I don't feel your suggestions should be defaults.

Sorry, in XCode they call it "Move subword backward/forward":

No worries, thanks for the quick replies!

You can add these keyboard shortcuts in your keymap.cson to get that behavior though:
'.platform-darwin atom-text-editor':
  'ctrl-left': 'editor:move-to-first-character-of-line'
  'ctrl-right': 'editor:move-to-end-of-screen-line'
  'ctrl-shift-left': 'editor:select-to-first-character-of-line'
  'ctrl-shift-right': 'editor:select-to-end-of-line'


chore: bumped langchain version

Pull Request Type

[ ] ✨ feat
[ ] 🐛 fix
[ ] ♻ refactor
[ ] 💄 style
[x] 🔨 chore
[ ] 📝 docs

Relevant Issues

resolves #2604
What is in this change?
The versions of langchain, langchain/community and langchain/core have been bumped to get rid of a security issue. Some code has been moved in the bumped versions, therefore some require statements have been changed.
Additional Information

Developer Validations

[ ] I ran yarn lint from the root of the repo & committed changes
[x] Relevant documentation has been updated
[x] I have tested my code functionality
[x] Docker build succeeds locally

There is very little chance doing this did not break some LLM providers who use a part of some Langchain library. Were you able to test this comprehensively where LC libraries are used?


gnomeExtensions: auto-update

I don't know why the ordering changed of the collisions.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Closing since I'm using an old version without GNOME 47

Hello, when is the extentions update next? How does it work?
There is a new https://extensions.gnome.org/extension/4170/home-assistant-extension/ version, i hope that will work with Gnome 47 (missing that extension).

Hi, just run the update-extensions.py more info here: https://github.com/NixOS/nixpkgs/blob/master/pkgs/desktops/gnome/extensions/README.md


Unpin cryptography  Python dep for Ansible Operators

We've got this version pinned
https://github.com/operator-framework/operator-sdk/blob/master/images/ansible-operator/Pipfile#L13-L16
It looks like the rust toolkit is available for UBI 8 now, so I think we can start bumping this dep.
Might affect https://github.com/operator-framework/operator-sdk/issues/5619

This should be pretty easy if anyone wants to pick it up, I'd be willing to coach.

/assign

Hi @rudradevpal thank you for picking this up!
For this one, you can start by updating the pipfile and then using pipenv to update the .lock file. (Let me know if you need some docs links to figure that out.)
From there, you can use make image-build ansible-operator to build the image.
https://github.com/operator-framework/operator-sdk/blob/9762aa24be11521165ebf7568b674146c6a7da32/Makefile#L84
Try out the new image with any ansible-based operator (Memcached tutorial is fine) to make sure it all works.
Repeat for Ansible 2.11 preview image.
Let me know if you could use any assistance!

@asmacdo can you please share docs for

pipenv to update the .lock file
for testing

@asmacdo can you please help on this

Let's unpin for now.
Use pipenv to install dependencies (from the pipfile) into a temp virtualenv, and it should update the lock file.
https://pipenv.pypa.io/en/latest/

For building and testing, take a look at the makefile. make image-build ansible-operator (also ansible-operator-2.11-preview) will build the images.
Once the images are building, you should be ok to push a PR and let CI run.

@rudradevpal Would you like still pick up this issue. If not feel free to unassigned yourself.


etcd-operator with restore option does not execute init.py in vault initializer

Following this repo for deploying vault. Based on this document, I have deployed vault and it works fine. Set etcd cluster backup as S3. Now I am trying to implement restore option of etcd-cluster from S3 as below.
apiVersion: "etcd.coreos.com/v1beta1"
kind: "Cluster"
metadata:
  name: "vault-etcd-cluster"
  namespace: vault
spec:
  size: 3
  version: "3.1.4"
  backup:
    backupIntervalInSecond: 3600
    maxBackups: 5
    storageType: "S3"
  restore:
    backupClusterName: "vault-etcd-cluster"
    storageType: "S3"

Since it has the secrets vaules restored  from S3, vault initializer does not start init.py (added code below). Due to that it does not create "vault-secret-config' secret. When I found this issue, I manually created this config from the backup. Now vault initializer is up, but kubernetes-vault is not starting and it throws some certificates issue. This is related to vault initializer, because of restore initializer does not run.
Expectation : If we restore secrets from S3, init.py script in initializer should be executed only with necessary steps(now nothing is executing and it is causing issue.). what are the steps need to be executed from init.py during restore and let me know what needs to be adjusted in the script.
init.py from initializer
import subprocess
import traceback
import os
import requests
import json
from time import sleep
import logging

logging.basicConfig(level=logging.DEBUG,
                    format='%(asctime)s %(name)-12s %(levelname)-8s %(message)s',
                    datefmt='%m-%d %H:%M',
                    filename='/tmp/vault.log',
                    filemode='w')

console = logging.StreamHandler()
console.setLevel(logging.INFO)

formatter = logging.Formatter('%(name)-12s: %(levelname)-8s %(message)s')
console.setFormatter(formatter)
logging.getLogger('').addHandler(console)

logger = logging.getLogger("vault-initializer")

def qexec(cmd):
    logger.info("[exec] %s" % " ".join(cmd))
    try:
        return subprocess.Popen(cmd, stdout=subprocess.PIPE, stderr=subprocess.PIPE)
    except Exception, e:
        logger.info("ERROR executing %s" % " ".join(cmd))
        logger.error(e)
    except:
        traceback.print_exc()
        logger.error("ERROR executing %s" % " ".join(cmd))

def bash_exec(script_location):
    os.system(script_location)

def unseal_vault(response):
    logger.info("Unsealing Started: ")
    creds = json.loads(response.text)
    qexec(["vault", "unseal", creds['keys'][0]])
    qexec(["vault", "unseal", creds['keys'][1]])
    qexec(["vault", "unseal", creds['keys'][2]])

def auth_vault(response):
    logger.info('Authenticating: ')
    creds = json.loads(response.text)
    qexec(["vault", "auth", creds['root_token']])

def init_vault():
    url = os.getenv('VAULT_ADDR')+'/v1/sys/init'
    data = "{\"secret_shares\":5, \"secret_threshold\":3}"
    return requests.put(url, data, verify=False)

def create_root_secret(response):
    logger.info("Creating vault root secret ")
    creds = json.loads(response.text)
    qexec(["kubectl", "create", "secret", "generic", "vault-secret-config", "--from-literal=unseal_key_1="+creds['keys'][0], "--from-literal=unseal_key_2="+creds['keys'][1], "--from-literal=unseal_key_3="+creds['keys'][2], "--from-literal=unseal_key_4="+creds['keys'][3], "--from-literal=unseal_key_5="+creds['keys'][4], "--from-literal=root_token="+creds['root_token'], "--namespace=vault"])

def configure_vault_controller():
    logger.info("Creating kubernetes-controller secret...")
    bash_exec('sh ./update_load_configmap.sh')

def configure_certificate():
    bash_exec('sh ./configure_certificate.sh')

def main():
    response = init_vault()
    logger.info(response.status_code)
    if response.status_code == 200:
        logger.info(response.content)
        with open('/tmp/vault_token.json', 'w') as outfile:
            json.dump(response.content, outfile)

        unseal_vault(response)
        auth_vault(response)
        create_root_secret(response)
        configure_certificate()
    return response

if __name__ == '__main__':
    response = main()
    configure_vault_controller()
    while True:
        logger.info("Vault already initialize")
        sleep(30)

Not looking for any solution now, because moved away from etcd storage.


drop support for React17

context
With nextJs 13 also requiring React18, it makes sense to follow suit. All new features are build on top of react18. This means we can also drop the useSyncExternalStore shim, which has caused troubles in the past with react-native and ESM, and also adds a bit of bundle size.
proposal

set the required peer dependency of react to ">=18.2.0"

Late to the party, but this is disappointing to hear. We won't be able to switch to React 18 for quite some time so we'll be stuck on v4 for a while. I was looking forward to all of the v5 updates (especially regarding infinite queries) and I was hoping to make react-query standard across our microservices. Continuing to use v4 across our codebase and knowing it will all be tech debt to replace it with v5 is a bit disheartening.

We won't be able to switch to React 18 for quite some time

@parkm can you let me know why you won't be able to switch to react18? It's been out for over a year now. The updates in 18 are mostly non-breaking - the most issues we've had when upgrading were around the TypeScript changes. Arguably, the framework you're building your software with is your most important dependency. As more and more new hooks will come out (think use or useEffectEvent), I expect many libraries to draw the line here and follow suite. NextJs has done the same thing - you can only use next13 if you have react18 ...

At the moment it's due to Enzyme not supporting React 18 and we have a ton of tests that would need to be converted to jest. It's an unfortunate tech debt that we've inherited. Sounds like we've kicked that can far enough though and we should prioritize upgrading.


Convert website from Gatsby to Eleventy

Decided in today's DTCG monthly meeting was that the website would be moved from Gatsby to Eleventy for a few reasons

Easier to set up and get involvement
Adding Images and other content will be easier to manage

The website is in a good state at the moment to convert to another platform, so we should do that as we continue defining our content strategy.

I'll be trying out Eleventy in the next few days. If it's easy enough as it seems, I'll give the conversion a shot

I'll be trying out Eleventy in the next few days. If it's easy enough as it seems, I'll give the conversion a shot


remove the link temporarily to make the test project build properly

This is a temporary solution until we find a better way to solve https://github.com/microsoft/typespec/issues/3727

API change check
API changes are not detected in this pull request.


APNS.send_notification failing silently in Delayed_job

All push notifications work fine from my webserver and from irb, however, when I try to send one from a Delayed Job task, the notifications never get sent out.

Are you seeing this fail quietly after hanging for four hours?


Uncaught ReferenceError: NativeClass is not defined

Uncaught ReferenceError: NativeClass is not defined is still appearing? I thought this has been resolved, unless I have got something wrong.
Im using version 3.0.2 google maps and 8.0.11 nativescript core

@liamcharmer  Any update on this?

i have this issue, any solution for this?

@liamcharmer  any update on this?


feat(gatsby-source-strapi): Support plugin prefixes

Plugins such as i18n include their own content types such as locale that can be queried via the api as well.
Those are exposed on sub paths of the form /api/{plugin}/{pluralName}.
When trying to fetch e.g. the locale type, currently the request is made to /api/locales as it is resolved through the fetched schema but the plugin prefix is not used although it can be derived from the plugin field in the schema.
Why is this useful?
Especially in the example case with locales, it can be used to query a list of all locales and their names in order to build e.g. a language switcher component.

This has been fixed in https://github.com/gatsby-uc/gatsby-source-strapi/pull/289


VLC support

Would like to see VLC added as a supported player as it can now decode Side-By-Side (SBS) VR videos as long as the video is encoded with the correct metadata. MPC-HC does great with 2D videos but can't decode SBS VR and displays both right and left video. VLC displays the video correctly and allows looking around and zooming in and out like you would with a head set.

Added, build here: https://github.com/Yoooi0/MultiFunPlayer/actions/runs/6060662125
Let me know if you find any issues.

Sorry for late reply. Downloaded both the debug and release linked in the closed issue. Both are giving me a .NET error.
You must install or update .NET to run the application.

Framework: 'Microsoft.NETCore.App', version '7.0.0' (x64)
Learn about framework resolution:
https://aka.ms/dotnet/app-launch-failed

Would you like to download it now?

I select Yes and install. Try and run MFP again and get same error. Tried a reboot, same error.

Did some further troubleshooting and I was able to get it to work with leaving all the files in the 1.26.1 stable release and replacing only the MultiFunPlayer.exe and MultiFunPlayer.dll files from this release. After that, VLC was in the devices list. Took me a bit to figure out the configuration in VLC as far as setting the host:port and password but got it to work. Haven't been able to test as far as scripts or devices but will let you know. A quick test with restim showed promising, though.

I tested in clean win11 sandbox and it prompted me to install 7.0.11, after installing it ran fine.
So no idea why you had issues.

Did some further troubleshooting and I was able to get it to work with leaving all the files in the 1.26.1 stable release and replacing only the MultiFunPlayer.exe and MultiFunPlayer.dll files from this release. After that, VLC was in the devices list. Took me a bit to figure out the configuration in VLC as far as setting the host:port and password but got it to work. Haven't been able to test as far as scripts or devices but will let you know. A quick test with restim showed promising, though.

I'm having a heck of a time connecting VLC and haven't been able to find any content on point. Could you outline how you got VLC configured?

@toulon99 try this: https://osr.wiki/books/funscript-playback/page/play-funscripts-using-vlc-and-multifunplayer

Thanks! I had tried adding the password, but didn't restart VLC. bahhh


Fixed forms_tests.tests.test_renderers with Jinja 3.1.0+.

See https://github.com/pallets/jinja/pull/1621.

@carltongibson Thanks for checking :+1:

Just saw this reported elsewhere, I'll fix this in Jinja so the final filename gets normalized, and then release 3.1.1.

And sorry, but the fix is going to cause this fix in your tests to fail again.

@davidism No problem, we will revert, it's just a test fix. Thanks for your efforts :1st_place_medal:

See #15545.