How to stop the extract_info execution before returning the result?

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm asking a question and not reporting a bug or requesting a feature
[X] I've looked through the README
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've searched known issues and the bugtracker for similar questions including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Please make sure the question is worded well enough to be understood
Using the extract_info method on a url, is there a way to set the execution timeout? I tried, but after reaching the timeout, extract_info still seems to be running, how do I stop it? This is my current code:
def get_info_yt_dlp(url, timeout=config.sort_timeout):
    """
    Get the url info by yt_dlp
    """
    ydl_opts = {
        "socket_timeout": timeout,
        "skip_download": True,
        "quiet": True,
        "no_warnings": True,
        "format": "best"
    }
    with yt_dlp.YoutubeDL(ydl_opts) as ydl:
        return ydl.sanitize_info(ydl.extract_info(url, download=False))

async def get_speed_yt_dlp(url, timeout=config.sort_timeout):
    """
    Get the speed of the url by yt_dlp
    """
    try:
        start_time = time()
        info = await asyncio.wait_for(
            asyncio.to_thread(get_info_yt_dlp, url, timeout), timeout=timeout
        )
        speed = int(round((time() - start_time) * 1000)) if len(info) else float("inf")
        return speed
    except:
        return float("inf")

Provide verbose output that clearly demonstrates the problem

[ ] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[ ] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
No response

You would use socket_timeout (as you are doing). If using it doesn't seem to be working, then there's likely something else going on instead of the host being unresponsive. You would have to provide a verbose log of the issue, and make sure any and all URLs in the log are legitimate or you will be blocked from the repository for spam.

I found that downloading the m3u8 url containing playlist caused a timeout, I will close this issue, thank you.


Read vector example

Description
This adds a snippet to examples/search-knn.js that clarifies how one would read a vector back out of Redis after having stored it.
I had to do this myself in my app logic, after having gotten the vector similarity search basically working, as a means of checking whether a given vector had already been computed.
Closes the documentation issue #2566
Checklist

[ ] Does npm test pass with this change (including linting)?
[ ] Is the new or changed code fully tested?
[ ] Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?

Closing as malformed git history - my bad


Allow bevy_color use without bevy support

Objective
Allow the use of color definitions from Bevy in other contexts than pure Bevy apps, e.g. outside ECS use.
In those cases it's nice to not have more dependencies than you need.
Solution
Hide use of reflection behind a feature flag.
Defaults to on.
Points to consider

This was straightforward except for the crates/bevy_color/src/lib.rs change where I removed Reflect as a bound. That is awkward to have feature gated since features should be additive. If the bound was added as part of the feature flag, the result would be more restrictive, and disable impls which did not have the impl. On the other hand having the reflect bound there unconditionally would defeat the purpose of the PR. I opted to remove the bound since it seems overly restrictive anyway.
It's possible to hide encase and bytemuck behind the new feature flag too (or a separate one). I'm thinking if bevy-support is not desired then it's unlikely that the user has need of those.

Strongly agree with the core intent here. However, this should follow the same strategy as bevy_math. See
https://github.com/bevyengine/bevy/blob/aaccbe88aa0d591c9c741f690ab472785c7bac09/crates/bevy_math/Cargo.toml#L23
for the implementation.

I made this PR more similar: Renamed the feature to bevy and made it opt-in.
Were there other things you were thinking of too?

A couple more changes. The exact mechanics of this are fiddly, which is part of why I'm being insistent on standardization <3

A couple more changes. The exact mechanics of this are fiddly, which is part of why I'm being insistent on standardization <3

100% agree, I welcome all nits!


examples?

Can you share some examples with different collections?
Will it work w/o requireJS, for example, using Marionette modules etc?

Hi, I think this module has to be rewritten because of deprecated Marionette.Module and also using it not only with requireJS.
Any suggestions or PR's will be very welcome)

Unfortunately I don't have much time to rebuild this module...

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1500 in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @polyskalov, @besthanzo, @ExTeeP, @m0rtyn, @Seryoga-Nosik, @juwain, @kalushko26, @Hakobian1, @shospodarets, @stefantsova, @selincodes, @shamio, @dorakov, @MaxCharlington, @dmitrymorozoff, @Flargoin, @amikha1lov, @Nova16888, @weisbrem, @data-scientist-dude, @wrgraff, @zavsievich, @stoked-zz, @jjnanthakumar, @kyzinatra, @xm4dn355x, @suberg, @dotiful, @gwdcodeteam, @sergkrasivskyi, @denislituev, @Patosha, @ArtSoulSpace, @levaleks, @ruhollahjafari1994, @desigens, @xthirtysix, @DagimTizazu, @AnastasiaRakh3, @kurokikaze, @Odisseya, @MagicUnderHood, @adeleke5140, @AlexeyBritvin, @ILoveCodingUpAStorm, @NikitaPr0705, @Imangazaliev, @scerka, @bourbakis, @HaNdTriX


Separated clean documentation for model-builder.

Can you please provide separated doc based on model-builder example ? I think it will cover enough cases  , that will help to start for beginners. Or if you have some videos / books on another resources, please, provide links. Current state of documentation is not enough for comfortable start with your awesome framework.

I have heard more examples are coming in the next few months. I have a beginners page of examples in Javascript with some videos, including a fully Javascript simplified version of the model builder called jj07-mnist.html. I agree that the more documentation and examples the better. I would really like to see examples of every main machine learning algorithm demonstrated using deeplearnjs.
https://hpssjellis.github.io/deeplearnjs-javascript-examples/

@hpssjellis OMG, its awesome !!! This is a light at the end of the tunnel !!! I highly appreciate your work, thanks!

Yep we are definitely working on some new examples and docs. Stay tuned!

@hpssjellis OMG, its awesome !!! This is a light at the end of the tunnel !!! I highly appreciate your work, thanks!

https://hpssjellis.github.io/deeplearnjs-javascript-examples/

I think there are about 1 million people who would love to be able to use Machine Learning, and Javascript is definitely the platform to learn it with. I can teach the Javascript, just a bit lacking in Machine Learning. The problem is that until Deeplearnjs becomes stable (version 1.0), spending hours and hours and hours on teaching it, using examples, is a bit of a waste of time as the examples get deprecated.
I hope it doesn't take too long to get examples working, of the approximately 10 Machine Learning platforms using Javascript, I definitely want to stay with the Google PAIR supported Deeplearnjs, but I need working examples to make my Curriculum.
It would also be good to work with a machine learning expert, but my persistence and multiple silly questions tend to scare them away. Doesn't matter how much I learn in Tensorflow, Python, Scikit-Learn, Jupiter Notebook (iPython), it is not easy converting the examples to Javascript
Thanks for the kind words @up-to-you. Might take a while, but I think we can do this.


feat(deployer): new tool to test the control plane

Deploys all (configurable) control plane components in a local docker
cluster.
For more details please use the help argument and have a look at the
README.md.

This looks good! In your description of the PR it suggests there will be README.md updates? Are those in a future PR?

This looks good! In your description of the PR it suggests there will be README.md updates? Are those in a future PR?

This looks good! In your description of the PR it suggests there will be README.md updates? Are those in a future PR?

Thanks! Oh no sorry, it's probably badly worded, I meant to tell the reader: if you want to know more, go use the --help and read the README.md 😁

This looks good! In your description of the PR it suggests there will be README.md updates? Are those in a future PR?

Thanks! Oh no sorry, it's probably badly worded, I meant to tell the reader: if you want to know more, go use the --help and read the README.md 😁

Ok! :)

Ok! :)

bors merge

bors merge

bors r-

bors r-

bors merge

bors merge

bors merge

bors merge

bors merge

bors merge


trigger build

@h1alexbel thank you for your Pull Request. I'll assign someone to review it soon.
If this PR solves a todo from the code, please don't forget to remove it.


Merge pull request #3 from whynotisnotavail/new_users_checklist

Implement User Onboarding Checklist Feature
onboarding_checklist.rb
Implemented a user onboarding checklist feature to help new users get started on the forum.
Changes Introduced:

User Onboarding Checklist:

Onboarding Tasks:

Fill out profile
Make first post
Read community guidelines

Progress Tracking:

Tracks the completion of each task.
Uses user profile bio, post count, and a custom field for reading guidelines.

Notifications:

Sends reminders to users about their onboarding progress.
Uses private messages to inform users about their progress and remaining tasks.

Benefits:

Improved User Experience:

Helps new users get acquainted with the forum and encourages them to complete important tasks.

Increased Engagement:

Ensures that new users are actively participating and getting the most out of the community.
Personalized messages make users feel welcomed and guided through their initial steps.

Testing:

Checklist Creation and Progress Tracking:

Tested by creating new user accounts and performing the tasks.
Verified that users receive notifications about their onboarding progress.

User Activity Listeners:

Listeners for user updates and post creations to update and notify users about their progress.

Scheduled Notifications:

Daily scheduled job to check user progress and send reminders.

How It Works:

Define Onboarding Tasks:

A list of tasks such as filling out their profile, making their first post, and reading community guidelines.

Track User Progress:

Implement logic to check which tasks a user has completed.

Notify Users:

Send private messages to users with their progress and remaining tasks.

Schedule Progress Checks:

Daily job to check user progress and send notifications.

This feature provides new users with a clear path to getting started on the forum, ensuring they complete essential tasks and engage with the community effectively.

why dont you close this pull request by merging it @importstring?

Done

k great!


rootfs: Stop building and shipping OPA

Merge Checklist

[x] Followed patch format from upstream recommendation: https://github.com/kata-containers/community/blob/main/CONTRIBUTING.md#patch-format

[x] Included a single commit in a given PR - at least unless there are related commits and each makes sense as a change on its own.

[x] Aware about the PR to be merged using "create a merge commit" rather than "squash and merge" (or similar)
[x] genPolicy only: Ensured the tool still builds on Windows
[x] genPolicy only: Updated sample YAMLs' policy annotations, if applicable
[x] The upstream-missing label (or upstream-not-needed) has been set on the PR.

Summary

Cherry pick from https://github.com/kata-containers/kata-containers/pull/9559
Note: No need to worry about https://github.com/kata-containers/kata-containers/pull/9559/commits/7dd2fde22d9b5056e4b36931ee8f45edb2309c75 since we don't have the original commit that this commit is trying to revert
Since OPA binary was replaced by the regorus crate, we can finally stop building and shipping the binary.
Test Methodology

image build https://dev.azure.com/mariner-org/mariner/_build/results?buildId=560521&view=results

https://dev.azure.com/mariner-org/mariner/_build/results?buildId=561904&view=results: Passed all internal e2e, except for 3 that use busybox sample. Verified busybox sample just needs to be updated


Add compatibility check.

Similar to https://github.com/librariesio/license-compatibility and https://github.com/HansHammel/license-compatibility-checker.
As wikipedia explains:

different licenses can contain contradictory requirements, rendering it impossible to legally combine source code from separately-licensed software in order to create and publish a new program

This extension adds a check to ensure that the most restrictive license does not conflict with the least restrictive. Example (based on changing the license in legally locally in node_modules):

This could also be expressed using SPDX, however, that would probably add an additional layer of complexity.

Hi @phillbaker,
Nice to meet you, thanks for your PR!
Can you please provide a concrete example of two licenses that contradict each other and are therefore incompatible? And what is the exact wording or requirement stated in both of these licenses that contradicts each other?

HI @eladnava thanks for getting back, I should have mentioned, this is a follow up to my earlier PR: https://github.com/eladnava/tldrlegal/pull/7.
I'm not a lawyer, so it's hard for me to point to specific terms in the licenses, but we're primarily interested in two types of incompatibilities:

a library is licensed so that it does not allow use by the organization using it (common examples would be software that requires a commercial license, e.g. highcharts or the JSON license)
a library is licensed under a "network copyleft" license such as any version of the AGPL which forces disclosure of source code for any "derived" or "combined" software using the library. Examples of NPM libraries licensed this way include: https://www.npmjs.com/package/jbus-common-util, https://www.npmjs.com/package/@verady/veranet, https://www.npmjs.com/package/hatchjs.

The second example it seems like would be covered under the obligations to disclosure source however.

@phillbaker After reading up on the JSON license it appears this is just the same as the MIT license but with an additional line Software shall be used for Good, not Evil. Where does it mention a commercial use requirement?
And in the case of highcharts, their npm module and GitHub repo don't actually reference any well-known license SPDX, so tldrlegal can't help you with that module's license requirements anyway. Upon examining their license page, they do have a non-commercial license (CreativeCommons Attribution-NonCommercial):
https://shop.highsoft.com/highcharts
Could you please provide other examples that this PR addresses?

Hi @eladnava, thanks for the reply.
We've now come to the understanding that "compatibility" is the higher level concept of whether any obligations have not been met. So the current approach already answers the question of compatibility. I'll close this PR as redundant.
A couple of issues coming out of this PR - how would you feel about adding to the existing license list?

Hi @phillbaker,
Absolutely, adding information about additional licenses and their obligations to this module would be a great idea. Which missing licenses are you referring to? "JSON" and "CreativeCommons Attribution-NonCommercial"?
Would you like to submit a PR to support these licenses?


DoS risk: small regex gives: panicked at 'tried to unwrap expr from HirFrame, got: Concat'

Hi @BurntSushi ,
Sorry to bother you :-) another one!
regex::Regex::new("(?i)(?i)*?");

thread 'main' panicked at 'tried to unwrap expr from HirFrame, got: Concat', /root/.cargo/registry/src/github.com-1ecc6299db9ec823/regex-syntax-0.5.3/src/hir/translate.rs:203:18

playground
@robertswiecki : honggfuzz is really good! libFuzzer has been unable to find those even though I'm sure many people ran it for many hours/days on this code.

Interesting! Seems like we (libfuzzer, afl, honggfuzz) might be using complementary strategies after all.

I guess so. I'll try to help on the rust front to make it easier to fuzz with all three.

Thanks! This is another good one, and I thought I had a test case for this. I'll look into it, but won't be able to fix it until tomorrow.
Is it possible to batch these bugs? I wouldn't be surprised if you found more, and it'd make more sense to just throw as many as you can over the wall so I can fix them in one go.

libFuzzer has been unable to find those even though I'm sure many people ran it for many hours/days on this code.

To be clear, the regex crate got a rewrite of its regex-syntax crate a few months ago. So if you're the first to run a fuzzer against that rewrite (I haven't), then you'll be the first to pick at the low hanging fruit. :-)

Is it possible to batch these bugs?

Yes, of course, it's just that I didn't know there was a recent rewrite so I didn't expect to find many bugs if any.
I ran the fuzzer for a couple of hours and it just found another one:
regex::Regex::new("(?i)?");
// thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', libcore/option.rs:335:21

I think that's it for the most obvious ones. But I'll improve a bit the process and continue to fuzz for a small while.
Do you have any recommendation of APIs that might need more scrutiny than others?

Do you have any recommendation of APIs that might need more scrutiny than others?

Traditionally, fuzzers have found bugs by comparing the outputs of the different execution engines, but it requires dealing with internal APIs. There are a few open issues detailing bugs in that space.
With respect to the parser rewrite though, no, I think Regex::new is exactly the thing you want to test. The other piece is printing the error message returned by Regex::new when given an invalid pattern, but it looks like your setup already accounts for this. If you test those two things, then that should cover most or all of the rewrite.

I will let this issue sit for a few days before diving into bug fixing mode. :-)

Ok, I'll leave it to fuzz for a few days then.
Could you confirm that this code is enough to cover the code rewrite?
pub fn fuzz_regex(data: &[u8]) {
    if let Ok(data) = std::str::from_utf8(data) {
        let _ = regex::Regex::new(data);
    }
}

It seems to me that it's not mandatory to display the error (if any) because I didn't see any real logic in the Debug and Display implementation of regex::Error. I guess the new code printing the message is executed while constructing the regex::Error so if it panics, we'll see it.
I've also configured the fuzzer to generate input with a maximum size of 20bytes, does it looks like a good size to you?

Yup, that code looks good to me. And yes, the formatter is indeed run when the regex::Error is built.
20 bytes is probably good. At least, I can't think of any specific reason to go bigger.
You might also consider adding (?x) to the beginning of patterns, if that's easy to do. Alternatively, enable ignore_whitespace, which should accomplish the same thing. I bet that will uncover more bugs. :-)

Great, I'll do that.


Azure Monitor Datasource not working on container instance

When trying to add/update an Azure Monitor data source, and poll the subscription to choose one, it doesn't populate.  It's running on a (Linux) ACI with the grafana/grafana image.    Here's the logs I'm seeing:
t=2019-11-15T21:07:04+0000 lvl=info msg="Request Completed" logger=context userId=2 orgId=1 uname=******@********* method=GET path="/api/datasources/proxy/3/[object Object]/subscriptions" status=502 remote_addr=<IP_ADDRESS> time_ms=29 size=0 referer=https://**********:3000/datasources/edit/3/
2019/11/15 21:07:04 http: proxy error: unsupported protocol scheme ""

Still no comments on this one? I'm experiencing the same issue


Inconsistent default preact imports

// signals must be imported from preact with a @
import { useSignal } from "@preact/signals";
// while hooks don't require the @
import { useEffect } from "preact/hooks";

fresh version: v1.3.1

The naming is correct. These are two different packages that are originally published to npm. Deviating from the official naming would only cause confusion. In npm land there are two kind of package names:

"normal" package names  have the format <name> like preact, express, etc
Scoped packages must start with an @ character and have the format @<scope>/<name>

This gives us:

preact -> The main preact package
preact/hooks -> The hooks entry point of the preact package
@preact/signals -> The @preact/signals package.


Update contributors

@all-contributors please add @bradleysryder for code

https://github.com/all-contributors please add @bradleysryder for code

@all-contributors please add @bradleysryder for code


A method to break through the limit of tokens per conversation.

Let gpt summarize and shorten the current conversation after every few questions and answers, so that we don't have to manually choose and delete the contents frequently.
Make it a settings switch option so we still have the precise control version.

Can have a menu to 'squash' the conversation too.

Not that important, just a bit annoying when having a long chat, because don't want to start over as well as selecting which one to delete.
For the UX flow, currently it behaves like this:

I think we can still give this token length warning, but then start a 'KeyMemory' mode automatically.
It should be similar to the autoTitle feature, but allow it to be somewhat longer.
Summarize the current chat history in a limited token length which can be adjusted in the settings modal.
(Because a shorter limit -> worse memory quality, larger limit -> shorter future available tokens)
I haven't dived into the store-chats.ts, but a rough idea is to control the whole chat history displayed on the UI in a new place of the store. Then we deal with each short chat history with OpenAI API internally.
The delete message feature is still useful for users to manually delete meaningless content (before triggering an auto-summary).
Overall, the chat thread could be a long non-editable history concatenated with a latest editable short history.
The first message of latest editable short history is the auto-summary result of the last editable short history.
(Treat the summary as a normal 'user' message but allow toggling display and editing like a ‘system’ message)
(Maybe make the non-editable history a different bgcolor)
(Or still make all history editable for 'export conversation' feature but give a note that editing old history has no effect on auto-summary result)

I like your description/idea of different resolutions for the messages. Meaning to keep the originals and the summary. There are a few things that need to figure out (the summarization operation will be slow, and affecting UX), but in theory history can be managed much better.

Putting also this on the roadmap, because like #216 but not exactly.


Allow the user to extract a specific glyph

I wanted to extract an emoji from a vector font at high resolution, and didn't want to dump the every glyph, so I wrote this.
I was able to test that the SVG code correctly tried to extract the right glyph from an SVG font, but I was unable to get the extraction itself to work correctly to verify. Perhaps my example font was corrupt.
Usage:
$ python extract_glyphs.py input/NotoEmoji-VariableFont_wght.ttf --glyph 😍
😍 -> 0x1f60d.png

Thanks for the PR! I've checked it, and it works fine on my Mac - the glyph was extracted to PNG successfully. I've used the font NotoEmoji-VariableFont_wght.ttf from https://fonts.google.com/noto/specimen/Noto+Emoji. I think it's the same font as yours, so I'm wondering why it doesn't work for you.


[QoI] offer typo correction for platform conditionals

Improves parse errors for conditional compilation tests by offering up the best match as a typo correction.
warning: unknown operating system for build configuration 'os'
#if os(macos)
       ^
note: did you mean 'macOS'?
#if os(macos)
       ^~~~~
       macOS

(I looked at using @rjmccall's TopCollection for this, but ran into problems with it: when it received more than MaxSize entries in order of increasing (worsening) score but with some duplicates, the insert operation would end up emptying it so I couldn't get results out. I might have been using it wrong, but I think it merits unit-testing.)

@swift-ci smoke test

@swift-ci smoke test

@swift-ci smoke test linux

Provisionally assigning @bitjammer who wrote a lot of this LangOptions stuff.

TopCollection drops entire tiers of values with the same bad score if including them would make the set exceed MaxSize.  That's by design under the assumption that we don't want to just pick representatives of the tier at random because we happened to see them first.
Now, if you're seeing values with better scores get dropped at the same time, that's a bug.

OK, perhaps I just got unlucky with a bunch of values that all had the same score.

@jtbandes Ping

Heh...

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

Typo correction for types would be great :)

Do we not have that already? Hmmm...... 🤔

I believe we have typo correction for associated types of protocols, and non-type members, but not types. I could be wrong though.

BTW, will this and #6703 be in Swift 3.1, or should I make a PR for swift-3.1-branch? The blog post said that changes on master would go into 3.1 until Jan 16, but it looks like the 3.1 branch has already been made.


Make sure there is a break after an #endif.

You wouldn't normally allow a line break just before the comma in a parameter list, but if the preceding line is an #endif, we have to be sure to include the break or we'll generate invalid code. Fix #705.

Wow, I guess I've never used postfix-#if in a comma-delimited list before; having to put a newline before the comma is super unfortunate 😞  Thanks for the fix!


Correctly dispose local tracks when hanging up

Do not remove local tracks on JitsiConferenceEvents.TRACK_REMOVED event, instead dispose and remove them separately in hangup() method.
Fix missing import of participant's actionTypes.
Signal local participant left after hanging the conference.
Remove un-necessary cases in participant's reducer.

This PR appears to be contained within https://github.com/jitsi/jitsi-meet-react/pull/51. Since I've reviewed & commented on this & my comments are supposedly addressed, I'll close this PR & review the new 1 instead.


Hoist version string to namespace level

Why the raw string and not the std::string?

I wanted as low-level a type as possible: a pointer into the read-only segment of the executable will always be accessible from all contexts, including a core file. A std::string may not.

Why the raw string and not the std::string?

If we use std::string at file scope, that means we need to construct that std::string at run time prior to main.  This isn't a huge deal, but the fewer run time initializations we have the better.  The raw string will be laid down in ROM at compile time.
We then construct a std::string from the raw string exactly once when the version is first actually requested at run time (lazy initialization).

👍

Not sure what's up with the coverage build failure - I've restarted it twice and it's failed twice.

Merged as 08ea2451013052fbeeb9ed2ccf894cc56668dfd8


UI root nodes are impossible to order

Bevy version
main (0.12-dev)
What you did
Spinning this issue off from testing in #9764.
use bevy::prelude::*;

fn main() {
    App::new()
        .add_plugins(DefaultPlugins)
        .add_systems(Startup, setup)
        .add_systems(Update, add_another_component)
        .run();
}

fn setup(mut commands: Commands) {
    let style = Style {
        width: Val::Percent(33.33),
        ..Default::default()
    };

    commands.spawn(Camera2dBundle::default());

    commands.spawn((
        NodeBundle {
            style: style.clone(),
            background_color: Color::RED.into(),
            ..Default::default()
        },
        AnotherComponent,
    ));

    commands.spawn(NodeBundle {
        style: style.clone(),
        background_color: Color::GREEN.into(),
        ..Default::default()
    });

    commands.spawn((
        NodeBundle {
            style: style.clone(),
            background_color: Color::BLUE.into(),
            ..Default::default()
        },
        AnotherComponent,
    ));
}

What went wrong
Nodes appear in order R-B-G. There's no ordered storage for them like Children for non-root nodes. They are added to taffy in the order of query iteration.
Additional information
This could be fixed by something like #8574.

https://github.com/bevyengine/bevy/pull/9637 makes root nodes render entirely independently of each other (with Taffy.compute_layout called separately on each root), which I reckon is the way to go here. Then the order doesn't matter, except for z-order.

Yeah this a priority issue I think. It might seem trivial but it's natural for users to assume the ordering of UI entities is stable. It would be easy for someone to waste hours and hours debugging a layout where nodes get reordered when they add a marker component. Especially if the reordering causes a UI node to render underneath another node and disappear.

Now that #9637 has landed, the example (adding height: Val::Percent(100.0) to make it render anything at all) renders as follows:
Before:

After:

So the nodes render on top of one another, and x/y layout is unaffected by node order. The z-ordering is still affected and unstable due to this issue, but this can be overridden using the ZIndex component.

#9637 definitely fixes or at least makes this redundant in my eyes.


Change Assignments per Registration

For the demo environment only.
!!! WARNING: !!!
This requires a hack to the local ``~/product-photos/0.processor/node_modules/kinesis-handler/lib/kinesisHandler.js`, adding:
              parsed.eventId = record.eventID // TODO hack to be fixed by using stream syndication

at line 166 (just after the payload is parsed)

Perhaps the right thing to do in order to control the behavior of the kinesis-handler code would be to quickly add a "feature flag" environment variable. One that is only set when you want the above "hack" in place? Or perhaps to effectively control the order guarantee (sync or async message handling)?

Kinesis-handler already does asynch vs synch handling, and that's not really part of the problem here, though I guess it means I'd only have to fix it for the async handler.  Anyhow, I'd rather not knock one hack out with another, so I'll soend a few hours trying to come up with a slightly slicker change to kinesis-handler that will allow the photo-processor to basically convert from ingress to egress schema, which seems to be what's really going on here.

Given that @laurwang has provided another mechanism, is this PR still applicable?

Hi @gwsii, there are two concerns here.  The configurability change that this PR is about and the septate need to augment the event with the eventID provided by Kinesis.  Pretty sure the original purpose of the PR (to allow assignments power registration to be configurable) is still valid unless I'm missing something...

Thanks @laurwang for un-hacking this!  Should be ready for actual merge now but please take a look and test it out a bit.


Revert "update reason1 field per sofort request"

Reverts Shopify/offsite_payments#81
Reverting until we can figure out what's up with this

@girasquid @louiskearns


add ruby query

Add query for Ruby language referenced from:
https://github.com/tree-sitter/tree-sitter-ruby/blob/master/queries/tags.scm

Thanks for the PR! Before we merge it there are a couple changes we'd need to get the standard tags query up to par with our internal queries:

Parameter capture (@codeium.parameter), for example: https://github.com/Exafunction/codeium-parse/blob/f30eafb76ba18d1014ec454147aaa8dde7082bb8/queries/javascript_functions.scm#L10
Function/class body capture (@body), to help us distinguish declarations and definitions. Not super familiar with Ruby but it seems to not have declarations, so we would need @body` captures for all class/method/function queries. For example: https://github.com/Exafunction/codeium-parse/blob/f30eafb76ba18d1014ec454147aaa8dde7082bb8/queries/javascript_functions.scm#L11

And then the last thing is a test file so we can generate golden query results: https://github.com/Exafunction/codeium-parse/tree/main/test_files
Happy to answer questions here or on our Discord.


x/blog: survey2018 fig25 incorrect title

In the 2018 survey results, fig25 has an erroneously copied title:

act: Please rank the top 5 resources you use to get answers to your Go related questions:
exp: Please rank the top 5 resources you use to get your Go related news:
note: This is embedded within an SVG.

@spf13

Thanks for the report! This was resolved as part of 169977 on Mar 29.


Uglify throws Parse error

Ran into the same problem as others and after two days discovered the problem. Turns out the error was not a typo but caused by "Unexpected token: operator (>)" and the code turned out to be: workingFiles.find(x => x.selectedFile == selectedFiles[i].name). I remove the > and the file passes. This is a problem but I didn't see anyone else mentioning it. At this point I’m removing the > character and uglifying then editing the > back into the uglified file. It’s a real pain and sure to cause confusion and errors in the future.

Please see the README for instructions on how to use the alpha ES6 support,
or use Babel to transform to ES5.
On May 31, 2016 4:01 AM, "McVanS"<EMAIL_ADDRESS>wrote:

Ran into the same problem as others and after two days discovered the
problem. Turns out the error was not a typo but caused by "Unexpected
token: operator (>)" and the code turned out to be: workingFiles.find(x =>
x.selectedFile == selectedFiles[i].name). I remove the > and the file
passes. This is a problem but I didn't see anyone else mentioning it. At
this point I’m removing the > character and uglifying then editing the >
back into the uglified file. It’s a real pain.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/terinjokes/gulp-uglify/issues/185, or mute the thread
https://github.com/notifications/unsubscribe/AAQsZV72hFZeQPs7g4DXNfsU5fn5HnR0ks5qHBUWgaJpZM4Iqahu
.

@terinjokes Which README.md? I don't see ES6 mentioned...

@danactive The very bottom, right about here

Ah thx

Thanks.


Source files without license headers

Hi,
All java source files are without license headers.
Please, confirm the licensing of code and/or content/s, and add license headers
https://fedoraproject.org/wiki/Packaging:LicensingGuidelines?rd=Packaging/LicensingGuidelines#License_Clarification
Thanks in advance
Regards

@puntogil sure, why is the fedoraproject related to this issue ?

hi
We need to know if you can add the license headers before you import your in RPM format libraries in our repository.  Some Fedora guis are interested to import Vert.X lang-js and lang-rhino. I want use Vert.X (core) in Apache Camel
Regards

this code is licensed under ASL : https://github.com/vert-x3/vertx-codegen/blob/master/LICENSE.txt


Update azure-functions-lab.md

Updated the Free Azure Subscription link to point to a page more relevant to the user
(You can replace all of this text with your description.)
Before creating your pull request, please check your content against these quality criteria:

Did you consider search engine optimization (SEO) when you chose the title in the metadata section and the H1 heading (i.e. the displayed title that starts with a single #)?
For new articles, did you add it to the table of contents?
Did you update the "ms.date" metadata for new or significantly updated articles?
Are technical terms and concepts introduced and explained, and are acronyms spelled out on first mention?
Should this page be linked to from other pages or Microsoft web sites?

For more information about creating content for docs.microsoft.com, see the contributor guide at https://docs.microsoft.com/contribute/.

@cmatskas - can you sign the CLA? thanks.

@cmatskas : Thanks for your contribution! The author(s) have been notified to review your proposed change.

You can only sign off in the main PR conversation, not in review comments. In general, the creator of the PR should sign off, not the tech reviewer.

How? I don’t see that option anywhere...

From: Jak Koke<EMAIL_ADDRESS>Sent: Thursday, December 12, 2019 10:08
To: MicrosoftDocs/visualstudio-docs
Cc: Christos Matskas; Mention
Subject: Re: [MicrosoftDocs/visualstudio-docs] Update azure-functions-lab.md (#4478)
Merged #4478https://github.com/MicrosoftDocs/visualstudio-docs/pull/4478 into master.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/visualstudio-docs/pull/4478?email_source=notifications&email_token=AA7PQHRM7WN5LLRIGBRDZALQYJ42TA5CNFSM4JZV5WV2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOVOMEN7Q#event-2878883582, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AA7PQHWVMP3W7G2A24ZBMZTQYJ42TANCNFSM4JZV5WVQ.

Christie, just leave a comment here with the text #sign-off like I did above.


Fix failures due to delete experiment

Description
This PR adds rm flag for the delete experiment API and corresponding test file changes
Fixes # (issue)
Type of change

[ ] Bug fix
[ ] New feature
[ ] Docs update
[ ] Breaking change (What changes might users need to make in their application due to this PR?)
[ ] Requires DB changes

How has this been tested?
Please describe the tests that were run to verify your changes and steps to reproduce. Please specify any test configuration required.

[ ] New Test X
[ ] Functional testsuite

Test Configuration

Kubernetes clusters tested on:

Checklist :dart:

[ ] Followed coding guidelines
[ ] Comments added
[ ] Dependent changes merged
[ ] Documentation updated
[ ] Tests added or updated

Additional information
Include any additional information such as links, test results, screenshots here

@khansaad - local monitoring fault tolerant test also needs to be updated


fix: async build plugins

DO NOT MERGE, Testing only.

What type of PR is this?

[ ] Feature
[x] Bug Fix
[ ] Refactor
[ ] Documentation Update

Description
related to #36
Added unit tests?

[ ] No, I want help in writing tests.
[x] No, I want someone else to write tests.
[ ] No, The addition does not need tests.
[ ] Yes

[optional] Random GIF to +1 someone's day

Hi @anuraghazra, are you working on this? if no then I can take this into separate branch and continue with your code.

hi @saurabhdaware, sorry didn't really got the time to look into this further. you can make this into a branch and continute the development if you want :D.

no issues! already a huge help! yes I will continue with your code in separate branch. Thanks!


Changed the pages based on feedback

Fixed:
Typo on gov template https://prototype-kit.service-manual.nhs.uk/how-tos/build-basic-prototype/use-components-2

Before
After

Typo with content page naming on https://prototype-kit.service-manual.nhs.uk/how-tos/build-basic-prototype/branching

Before
After

Missing details on changing the components text to Yes and No https://prototype-kit.service-manual.nhs.uk/how-tos/build-basic-prototype/use-components

Before
After

Added note about back links not being in this tutorial - this seems too much to add as an entire thing (and ideally the default link can be changed?)  https://prototype-kit.service-manual.nhs.uk/how-tos/build-basic-prototype/link-pages-together

Before
After

New changes based on @anandamaryon1's comments

The back links in your pages don't go to the correct places yet. If you want, you can try and change the links in the back links by using the back link component guidance.


Nuget Package Install Can't Find package Chaos.NaCl

I have tried for 2 days in futility to install the dotnetcore-stellar-sdk package and it keeps failing to successfully restore with the following error message:
"Unable to find package Chaos.NaCl. No packages exist with this id in source(s): Microsoft Visual Studio Offline Packages, nuget.org"
Kindly check it out.

Interesting, that reference should be included in the project internally. I
will take a look and see why the nuget package is treating it as an
external dependency.
On Tue, Dec 5, 2017, 3:58 AM Oswald Umeh<EMAIL_ADDRESS>wrote:

I have tried for 2 days in futility to install the dotnetcore-stellar-sdk
package and it keeps failing to successfully restore with the following
error message:
"Unable to find package Chaos.NaCl. No packages exist with this id in
source(s): Microsoft Visual Studio Offline Packages, nuget.org"
Kindly check it out.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/elucidsoft/dotnetcore-stellar-sdk/issues/3, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AANRUCAHQmO1Wrzk9FceMZT0qAdalB_Vks5s9QWzgaJpZM4Q18P6
.

Ok I found the problem, will be uploading a new nuget package shortly. I am also uploading a new version of Chaos.Nacl to Nuget for core that way all dependencies are on nuget, so I'll be separating that out and creating its own repo.

That's great to hear. Looking forward to this update cause I am currently using in on a project.

https://www.nuget.org/packages/stellar-dotnetcore-sdk/1.0.3
Should resolve all of your issues, please let me know!

Package installs and restores just fine now.
Thanks.

Good to hear!


Update sgx crates to 0.6.0

Current dependencies on/for this PR:

main

PR #59   👈

This comment was auto-generated by Graphite.

replaced by #62


Cast does not auto-generate column names

First of all, thanks for the awesome library.  However, I can't get "cast" to work as it does in the Reshape package for R, namely, I can't figure out how to name columns based on the values of the fields of the input data.
As you can see at the bottom of this R Reshape example:
http://www.statmethods.net/management/reshape.html
"x1" and "x2" were values of field "variable" before casting and after casting "x1" and "x2" become column names. Is it possible to do this with "cast" in melt.js? If so, how? Thank you very much.

I also can't get this to work. I think "cast" in this library is more of a "group by." Cast to me means how it is described in that R documentation.


Token and Sign in once on a device?

Describe the issue
This doesnt work once it leaves the editor. Is it possible to even run on a device? This works fine in the editor by manually getting a token and signing in but after that it doesnt work on any builds. I have tried to manipulate the test config with out the unity tests because it doesnt seem to work in 2020.
Steps to reproduce the problem
use the testconfig
Unity version
2020.1
Operating system
windows

@iiidefektiii  Did you find any solution to this issue ?

@zicas2000    Yes it was user error. I was also working with some player prefs and resetting those will also reset your vimeo token and need to go through the token process again.


chore: Added script to run both frontend and backend at same time and…

Summary

Added script to run both frontend and backend at same time
Added script to install dependencies in frontend, backend and app level at app level installation (npm i)

Description

Here, I have used concurrently package to run frontend and backend at same time at same time
Hence, added node_modules in .gitignore file to be untracked

Images
Console after (npm start) at app level

Issue(s) Addressed
Closes #11

Hi @hemant14050, Thank you for the PR.
Unfortunately as i didn't hear reply from you in linkendIn, I decided to close this issue by merging the PR of https://github.com/krishnaacharyaa/wanderlust/pull/27
But I really don't want your efforts to go waste, so I have a nice fix for the situation, I personally liked the color addition you added in the script, can you kindly create a enhancement issue and then get it assigned to you, and raise the PR with the addition of color changes in the script ?

Hi @hemant14050, Thank you for the PR. Unfortunately as i didn't hear reply from you in linkendIn, I decided to close this issue by merging the PR of #27
But I really don't want your efforts to go waste, so I have a nice fix for the situation, I personally liked the color addition you added in the script, can you kindly create a enhancement issue and then get it assigned to you, and raise the PR with the addition of color changes in the script ?

I apologize for not responding on LinkedIn earlier. I'm glad to hear that you liked the color addition in the script. I'll create the enhancement issue as you suggested and submit the updated PR soon.


⚠ Secret Website 3 has degraded performance

In 30d4483, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 3093 ms

Resolved: Secret Website 3 performance has improved in e0e3390.


WIP - Keystone ldap integration

Aside from using the OpenStack foundation's domain in our tests, my only concern duplicating the keystone config into two files. Could we use an additional file and config_dir instead?

Looks okay to me, just odd that the one part I have an objection to is done in a different PR.

This now looks good to me. :+1:

this may not have actually passed tests ... got run by the new jenkins server I'm to test via PR.

This is mostly obviated by the LDAP support we've added. We don't have an LDAP setup in vagrant at the moment, feel free to narrow the scope and re-open.


Support coin-type 60 when restoring and adding keys

When restoring a key, the flag --coin-type is not currently wired up to anything and Coin-type 118 is hard coded throughout Lens.
Need to pass through and implement --coin-type args

This issue was brought to light here:
https://github.com/cosmos/relayer/issues/588


dashboard is not rendering links or namespace

Bug Description
Deployed CKF from latest/edge (see status below) and the dashboard in the following state

Taking a look at its logs,we see:
2024-07-24T07:38:24.063Z [pebble] Service "kubeflow-dashboard" starting: /sbin/tini -- npm start
2024-07-24T07:38:24.073Z [kubeflow-dashboard] [WARN  tini (15)] Tini is not running as PID 1 and isn't registered as a child subreaper.
2024-07-24T07:38:24.074Z [kubeflow-dashboard] Zombie processes will not be re-parented to Tini, so zombie reaping won't work.
2024-07-24T07:38:24.074Z [kubeflow-dashboard] To fix the problem, use the -s option or set the environment variable TINI_SUBREAPER to register Tini as a child subreaper, or run Tini as PID 1.
2024-07-24T07:38:25.179Z [pebble] GET /v1/changes/1/wait?timeout=4.000s 1.108564355s 200
2024-07-24T07:38:28.245Z [kubeflow-dashboard]
2024-07-24T07:38:28.245Z [kubeflow-dashboard] ><EMAIL_ADDRESS>start
2024-07-24T07:38:28.245Z [kubeflow-dashboard] > npm run serve
2024-07-24T07:38:28.245Z [kubeflow-dashboard]
2024-07-24T07:38:33.099Z [kubeflow-dashboard] npm WARN logfile Error: EACCES: permission denied, scandir '/root/.npm/_logs'
2024-07-24T07:38:33.099Z [kubeflow-dashboard] npm WARN logfile  error cleaning log files [Error: EACCES: permission denied, scandir '/root/.npm/_logs'] {
2024-07-24T07:38:33.099Z [kubeflow-dashboard] npm WARN logfile   errno: -13,
2024-07-24T07:38:33.099Z [kubeflow-dashboard] npm WARN logfile   code: 'EACCES',
2024-07-24T07:38:33.099Z [kubeflow-dashboard] npm WARN logfile   syscall: 'scandir',
2024-07-24T07:38:33.099Z [kubeflow-dashboard] npm WARN logfile   path: '/root/.npm/_logs'
2024-07-24T07:38:33.099Z [kubeflow-dashboard] npm WARN logfile }
2024-07-24T07:38:33.203Z [kubeflow-dashboard]
2024-07-24T07:38:33.203Z [kubeflow-dashboard] ><EMAIL_ADDRESS>serve
2024-07-24T07:38:33.203Z [kubeflow-dashboard] > node dist/server.js
2024-07-24T07:38:33.203Z [kubeflow-dashboard]
2024-07-24T07:38:33.848Z [kubeflow-dashboard] npm ERR! code EACCES
2024-07-24T07:38:33.852Z [kubeflow-dashboard] npm ERR! syscall mkdir
2024-07-24T07:38:33.852Z [kubeflow-dashboard] npm ERR! path /root/.npm/_cacache/tmp
2024-07-24T07:38:33.852Z [kubeflow-dashboard] npm ERR! errno -13
2024-07-24T07:38:33.853Z [kubeflow-dashboard] npm ERR!
2024-07-24T07:38:33.853Z [kubeflow-dashboard] npm ERR! Your cache folder contains root-owned files, due to a bug in
2024-07-24T07:38:33.853Z [kubeflow-dashboard] npm ERR! previous versions of npm which has since been addressed.
2024-07-24T07:38:33.853Z [kubeflow-dashboard] npm ERR!
2024-07-24T07:38:33.862Z [kubeflow-dashboard] npm ERR! To permanently fix this problem, please run:
2024-07-24T07:38:33.862Z [kubeflow-dashboard] npm ERR!   sudo chown -R 1000:1000 "/root/.npm"
2024-07-24T07:38:33.893Z [kubeflow-dashboard]
2024-07-24T07:38:33.893Z [kubeflow-dashboard] npm ERR! Log files were not written due to an error writing to the directory: /root/.npm/_logs
2024-07-24T07:38:33.893Z [kubeflow-dashboard] npm ERR! You can rerun the command with `--loglevel=verbose` to see the logs in your terminal
2024-07-24T07:38:34.066Z [kubeflow-dashboard] npm notice
2024-07-24T07:38:34.066Z [kubeflow-dashboard] npm notice New major version of npm available! 8.19.4 -> 10.8.2
2024-07-24T07:38:34.066Z [kubeflow-dashboard] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.8.2>
2024-07-24T07:38:34.066Z [kubeflow-dashboard] npm notice Run `npm install -g<EMAIL_ADDRESS>to update!
2024-07-24T07:38:34.067Z [kubeflow-dashboard] npm notice
2024-07-24T07:38:38.903Z [pebble] Service "kubeflow-dashboard" stopped unexpectedly with code 243
2024-07-24T07:38:38.903Z [pebble] Service "kubeflow-dashboard" on-failure action is "restart", waiting ~500ms before restart (backoff 1)
2024-07-24T07:38:39.478Z [pebble] Service "kubeflow-dashboard" starting: /sbin/tini -- npm start

To Reproduce
1.Deploy CKF from latest/edge
Environment
Juju 3.4.4
Microk8s 1.29
Relevant Log Output
Model     Controller  Cloud/Region        Version  SLA          Timestamp
kubeflow  microk8s    microk8s/localhost  3.4.4    unsupported  08:46:56Z

App                      Version                  Status   Scale  Charm                    Channel       Rev  Address         Exposed  Message
admission-webhook                                 active       1  admission-webhook        latest/edge   339  <IP_ADDRESS>  no
argo-controller                                   waiting      1  argo-controller          latest/edge   538  <IP_ADDRESS>   no       installing agent
dex-auth                                          active       1  dex-auth                 latest/edge   522  <IP_ADDRESS>  no
envoy                                             active       1  envoy                    latest/edge   258  <IP_ADDRESS>  no
istio-ingressgateway                              active       1  istio-gateway            latest/edge  1048  <IP_ADDRESS>  no
istio-pilot                                       active       1  istio-pilot              latest/edge  1013  <IP_ADDRESS>  no
jupyter-controller                                active       1  jupyter-controller       latest/edge  1018  <IP_ADDRESS>  no
jupyter-ui                                        active       1  jupyter-ui               latest/edge   941  <IP_ADDRESS>  no
katib-controller                                  active       1  katib-controller         latest/edge   707  <IP_ADDRESS>  no
katib-db                 8.0.37-0ubuntu<IP_ADDRESS>  active       1  mysql-k8s                8.0/edge      164  <IP_ADDRESS>  no
katib-db-manager                                  active       1  katib-db-manager         latest/edge   669  <IP_ADDRESS>   no
katib-ui                                          active       1  katib-ui                 latest/edge   672  <IP_ADDRESS>   no
kfp-api                                           active       1  kfp-api                  latest/edge  1483  <IP_ADDRESS>  no
kfp-db                   8.0.37-0ubuntu<IP_ADDRESS>  active       1  mysql-k8s                8.0/edge      164  <IP_ADDRESS>  no
kfp-metadata-writer                               active       1  kfp-metadata-writer      latest/edge   543  <IP_ADDRESS>  no
kfp-persistence                                   active       1  kfp-persistence          latest/edge  1490  <IP_ADDRESS>  no
kfp-profile-controller                            active       1  kfp-profile-controller   latest/edge  1448  <IP_ADDRESS>  no
kfp-schedwf                                       active       1  kfp-schedwf              latest/edge  1501  <IP_ADDRESS>  no
kfp-ui                                            active       1  kfp-ui                   latest/edge  1484  <IP_ADDRESS>  no
kfp-viewer                                        active       1  kfp-viewer               latest/edge  1516  <IP_ADDRESS>  no
kfp-viz                                           active       1  kfp-viz                  latest/edge  1434  <IP_ADDRESS>  no
knative-eventing                                  active       1  knative-eventing         latest/edge   449  <IP_ADDRESS>  no
knative-operator                                  active       1  knative-operator         latest/edge   424  <IP_ADDRESS>  no
knative-serving                                   active       1  knative-serving          latest/edge   450  <IP_ADDRESS>  no
kserve-controller                                 active       1  kserve-controller        latest/edge   593  <IP_ADDRESS>  no
kubeflow-dashboard                                active       1  kubeflow-dashboard       latest/edge   628  <IP_ADDRESS>  no
kubeflow-profiles                                 active       1  kubeflow-profiles        latest/edge   409  <IP_ADDRESS>  no
kubeflow-roles                                    active       1  kubeflow-roles           latest/edge   238  <IP_ADDRESS>  no
kubeflow-volumes                                  active       1  kubeflow-volumes         latest/edge   331  <IP_ADDRESS>   no
metacontroller-operator                           active       1  metacontroller-operator  latest/edge   302  <IP_ADDRESS>   no
minio                    res:oci-image@5102166    active       1  minio                    latest/edge   342  <IP_ADDRESS>   no
mlmd                                              active       1  mlmd                     latest/edge   209  <IP_ADDRESS>  no
oidc-gatekeeper                                   active       1  oidc-gatekeeper          latest/edge   407  <IP_ADDRESS>   no
pvcviewer-operator                                active       1  pvcviewer-operator       latest/edge   142  <IP_ADDRESS>   no
tensorboard-controller                            active       1  tensorboard-controller   latest/edge   325  <IP_ADDRESS>   no
tensorboards-web-app                              active       1  tensorboards-web-app     latest/edge   313  <IP_ADDRESS>   no
training-operator                                 active       1  training-operator        latest/edge   490  <IP_ADDRESS>   no

Unit                        Workload     Agent  Address     Ports          Message
admission-webhook/0*        active       idle   <IP_ADDRESS>
argo-controller/0*          maintenance  idle   <IP_ADDRESS>                 [container:argo-controller] Execution pending - waiting on kubernetes:crds-cm-and-secrets (BlockedStatus("Not all res...
dex-auth/0*                 active       idle   <IP_ADDRESS>
envoy/0*                    active       idle   <IP_ADDRESS>
istio-ingressgateway/0*     active       idle   <IP_ADDRESS>
istio-pilot/0*              active       idle   <IP_ADDRESS>
jupyter-controller/0*       active       idle   <IP_ADDRESS>
jupyter-ui/0*               active       idle   <IP_ADDRESS>
katib-controller/0*         active       idle   <IP_ADDRESS>
katib-db-manager/0*         active       idle   <IP_ADDRESS>
katib-db/0*                 active       idle   <IP_ADDRESS>                 Primary
katib-ui/0*                 active       idle   <IP_ADDRESS>
kfp-api/0*                  active       idle   <IP_ADDRESS>
kfp-db/0*                   active       idle   <IP_ADDRESS>                 Primary
kfp-metadata-writer/0*      active       idle   <IP_ADDRESS>
kfp-persistence/0*          active       idle   <IP_ADDRESS>
kfp-profile-controller/0*   active       idle   <IP_ADDRESS>
kfp-schedwf/0*              active       idle   <IP_ADDRESS>
kfp-ui/0*                   active       idle   <IP_ADDRESS>
kfp-viewer/0*               active       idle   <IP_ADDRESS>
kfp-viz/0*                  active       idle   <IP_ADDRESS>
knative-eventing/0*         active       idle   <IP_ADDRESS>
knative-operator/0*         active       idle   <IP_ADDRESS>
knative-serving/0*          active       idle   <IP_ADDRESS>
kserve-controller/0*        active       idle   <IP_ADDRESS>
kubeflow-dashboard/0*       active       idle   <IP_ADDRESS>
kubeflow-profiles/0*        active       idle   <IP_ADDRESS>
kubeflow-roles/0*           active       idle   <IP_ADDRESS>
kubeflow-volumes/0*         active       idle   <IP_ADDRESS>
metacontroller-operator/0*  active       idle   <IP_ADDRESS>
minio/0*                    active       idle   <IP_ADDRESS>  9000-9001/TCP
mlmd/0*                     active       idle   <IP_ADDRESS>
oidc-gatekeeper/0*          active       idle   <IP_ADDRESS>
pvcviewer-operator/0*       active       idle   <IP_ADDRESS>
tensorboard-controller/0*   active       idle   <IP_ADDRESS>
tensorboards-web-app/0*     active       idle   <IP_ADDRESS>
training-operator/0*        active       idle   <IP_ADDRESS>

Additional Context
No response

FWIW

another deployment from latest/edge using the same dashboard revision was working fine (juju status), so this could be intermittent.
Happened once on latest/beta as well latest/beta where the charm hasn't been published since 9th of July (revision 600)

Debugging
A wild guess is that it could be related to stini since the charm is using pebble, thus tini could not be working as expected
2024-07-24T08:17:03.308Z [kubeflow-dashboard] [WARN  tini (2120)] Tini is not running as PID 1 and isn't registered as a child subreaper.
2024-07-24T08:17:03.308Z [kubeflow-dashboard] Zombie processes will not be re-parented to Tini, so zombie reaping won't work.
2024-07-24T08:17:03.308Z [kubeflow-dashboard] To fix the problem, use the -s option or set the environment variable TINI_SUBREAPER to register Tini as a child subreaper, or run Tini as PID 1.

I was able to reproduce the issue with the following revisions:

628 from latest/edge
610 from latest/edge
600 from latest/beta <-- I do not think this is intermittent
My logs:

2024-07-24T09:24:43.769Z [pebble] Service "kubeflow-dashboard" stopped unexpectedly with code 243
2024-07-24T09:24:43.769Z [pebble] Service "kubeflow-dashboard" on-failure action is "restart", waiting ~30s before restart (backoff 24)
2024-07-24T09:24:46.128Z [pebble] GET /v1/notices?timeout=30s 30.001478073s 200
2024-07-24T09:25:16.129Z [pebble] GET /v1/notices?timeout=30s 30.000966433s 200
2024-07-24T09:25:16.457Z [pebble] Service "kubeflow-dashboard" starting: /sbin/tini -- npm start
2024-07-24T09:25:16.459Z [kubeflow-dashboard] [WARN  tini (738)] Tini is not running as PID 1 and isn't registered as a child subreaper.
2024-07-24T09:25:16.459Z [kubeflow-dashboard] Zombie processes will not be re-parented to Tini, so zombie reaping won't work.
2024-07-24T09:25:16.459Z [kubeflow-dashboard] To fix the problem, use the -s option or set the environment variable TINI_SUBREAPER to register Tini as a child subreaper, or run Tini as PID 1.
2024-07-24T09:25:16.676Z [kubeflow-dashboard]
2024-07-24T09:25:16.676Z [kubeflow-dashboard] ><EMAIL_ADDRESS>start
2024-07-24T09:25:16.676Z [kubeflow-dashboard] > npm run serve
2024-07-24T09:25:16.676Z [kubeflow-dashboard]
2024-07-24T09:25:16.891Z [kubeflow-dashboard] npm WARN logfile Error: EACCES: permission denied, scandir '/root/.npm/_logs'
2024-07-24T09:25:16.891Z [kubeflow-dashboard] npm WARN logfile  error cleaning log files [Error: EACCES: permission denied, scandir '/root/.npm/_logs'] {
2024-07-24T09:25:16.891Z [kubeflow-dashboard] npm WARN logfile   errno: -13,
2024-07-24T09:25:16.891Z [kubeflow-dashboard] npm WARN logfile   code: 'EACCES',
2024-07-24T09:25:16.891Z [kubeflow-dashboard] npm WARN logfile   syscall: 'scandir',
2024-07-24T09:25:16.891Z [kubeflow-dashboard] npm WARN logfile   path: '/root/.npm/_logs'
2024-07-24T09:25:16.891Z [kubeflow-dashboard] npm WARN logfile }
2024-07-24T09:25:16.909Z [kubeflow-dashboard]
2024-07-24T09:25:16.909Z [kubeflow-dashboard] ><EMAIL_ADDRESS>serve
2024-07-24T09:25:16.909Z [kubeflow-dashboard] > node dist/server.js
2024-07-24T09:25:16.909Z [kubeflow-dashboard]
2024-07-24T09:25:16.995Z [kubeflow-dashboard] npm ERR! code EACCES
2024-07-24T09:25:16.995Z [kubeflow-dashboard] npm ERR! syscall mkdir
2024-07-24T09:25:16.995Z [kubeflow-dashboard] npm ERR! path /root/.npm/_cacache/tmp
2024-07-24T09:25:16.995Z [kubeflow-dashboard] npm ERR! errno -13
2024-07-24T09:25:16.995Z [kubeflow-dashboard] npm ERR!
2024-07-24T09:25:16.995Z [kubeflow-dashboard] npm ERR! Your cache folder contains root-owned files, due to a bug in
2024-07-24T09:25:16.995Z [kubeflow-dashboard] npm ERR! previous versions of npm which has since been addressed.
2024-07-24T09:25:16.995Z [kubeflow-dashboard] npm ERR!
2024-07-24T09:25:16.996Z [kubeflow-dashboard] npm ERR! To permanently fix this problem, please run:
2024-07-24T09:25:16.996Z [kubeflow-dashboard] npm ERR!   sudo chown -R 1000:1000 "/root/.npm"
2024-07-24T09:25:16.996Z [kubeflow-dashboard]
2024-07-24T09:25:16.996Z [kubeflow-dashboard] npm ERR! Log files were not written due to an error writing to the directory: /root/.npm/_logs
2024-07-24T09:25:16.996Z [kubeflow-dashboard] npm ERR! You can rerun the command with `--loglevel=verbose` to see the logs in your terminal
2024-07-24T09:25:17.341Z [kubeflow-dashboard] Initializing Kubernetes configuration
2024-07-24T09:25:17.359Z [kubeflow-dashboard] Unable to fetch Application information: 404 page not found
2024-07-24T09:25:17.359Z [kubeflow-dashboard]
2024-07-24T09:25:17.361Z [kubeflow-dashboard] "other" is not a supported platform for Metrics
2024-07-24T09:25:17.361Z [kubeflow-dashboard] Using Profiles service at http://kubeflow-profiles.kubeflow:8081/kfam
2024-07-24T09:25:17.365Z [kubeflow-dashboard] [SEVERE] uncaughtException Error: listen EADDRINUSE: address already in use :::8082
2024-07-24T09:25:17.365Z [kubeflow-dashboard]     at Server.setupListenHandle [as _listen2] (node:net:1463:16)
2024-07-24T09:25:17.365Z [kubeflow-dashboard]     at listenInCluster (node:net:1511:12)
2024-07-24T09:25:17.365Z [kubeflow-dashboard]     at Server.listen (node:net:1599:7)
2024-07-24T09:25:17.365Z [kubeflow-dashboard]     at Function.listen (/usr/src/app/node_modules/express/lib/application.js:635:24)
2024-07-24T09:25:17.365Z [kubeflow-dashboard]     at /usr/src/app/dist/server.js:83:13
2024-07-24T09:25:17.365Z [kubeflow-dashboard]     at Generator.next (<anonymous>)
2024-07-24T09:25:17.365Z [kubeflow-dashboard]     at fulfilled (/usr/src/app/dist/server.js:5:58)
2024-07-24T09:25:17.365Z [kubeflow-dashboard]     at processTicksAndRejections (node:internal/process/task_queues:96:5) {
2024-07-24T09:25:17.365Z [kubeflow-dashboard]   code: 'EADDRINUSE',
2024-07-24T09:25:17.365Z [kubeflow-dashboard]   errno: -98,
2024-07-24T09:25:17.365Z [kubeflow-dashboard]   syscall: 'listen',
2024-07-24T09:25:17.365Z [kubeflow-dashboard]   address: '::',
2024-07-24T09:25:17.365Z [kubeflow-dashboard]   port: 8082
2024-07-24T09:25:17.365Z [kubeflow-dashboard] }
2024-07-24T09:25:17.372Z [pebble] Service "kubeflow-dashboard" stopped unexpectedly with code 243
2024-07-24T09:25:17.372Z [pebble] Service "kubeflow-dashboard" on-failure action is "restart", waiting ~30s before restart (backoff 25)

Two weeks ago I performed a series of tests using those exact versions, but in my case there was no issue. I was able to log into the dashboard and into each component.
Workaround (does not work)
I tried using the latest image just in case I saw a difference, but the issue persisted.
$ juju refresh kubeflow-dashboard --resource oci-image=docker.io/kubeflownotebookswg/centraldashboard:v1.9.0

Rock
Tried refreshing to charm from here (has fix that is WIP) using rock from here (update to 1.9 + fix that is WIP) and it looks like the service doesn't restart anymore although there are still the access denied errors on start
╰─$ kl -n kubeflow kubeflow-dashboard-0 -c kubeflow-dashboard -f
2024-07-24T11:30:52.806Z [pebble] HTTP API server listening on ":38813".
2024-07-24T11:30:52.806Z [pebble] Started daemon.
2024-07-24T11:30:55.852Z [pebble] GET /v1/plan?format=yaml 490.399µs 200
2024-07-24T11:30:55.876Z [pebble] POST /v1/layers 281.953µs 200
2024-07-24T11:30:55.896Z [pebble] POST /v1/services 6.988879ms 202
2024-07-24T11:30:55.905Z [pebble] Service "kubeflow-dashboard" starting: npm start
2024-07-24T11:30:56.414Z [kubeflow-dashboard]
2024-07-24T11:30:56.414Z [kubeflow-dashboard] ><EMAIL_ADDRESS>start
2024-07-24T11:30:56.414Z [kubeflow-dashboard] > npm run serve
2024-07-24T11:30:56.414Z [kubeflow-dashboard]
2024-07-24T11:30:56.914Z [pebble] GET /v1/changes/1/wait?timeout=4.000s 1.017299043s 200
2024-07-24T11:30:56.935Z [kubeflow-dashboard] glob error [Error: EACCES: permission denied, scandir '/root/.npm/_logs'] {
2024-07-24T11:30:56.935Z [kubeflow-dashboard]   errno: -13,
2024-07-24T11:30:56.935Z [kubeflow-dashboard]   code: 'EACCES',
2024-07-24T11:30:56.935Z [kubeflow-dashboard]   syscall: 'scandir',
2024-07-24T11:30:56.935Z [kubeflow-dashboard]   path: '/root/.npm/_logs'
2024-07-24T11:30:56.935Z [kubeflow-dashboard] }
2024-07-24T11:30:56.939Z [kubeflow-dashboard] npm WARN logfile Error: EACCES: permission denied, scandir '/root/.npm/_logs'
2024-07-24T11:30:56.939Z [kubeflow-dashboard] npm WARN logfile  error cleaning log files [Error: EACCES: permission denied, scandir '/root/.npm/_logs'] {
2024-07-24T11:30:56.939Z [kubeflow-dashboard] npm WARN logfile   errno: -13,
2024-07-24T11:30:56.939Z [kubeflow-dashboard] npm WARN logfile   code: 'EACCES',
2024-07-24T11:30:56.939Z [kubeflow-dashboard] npm WARN logfile   syscall: 'scandir',
2024-07-24T11:30:56.939Z [kubeflow-dashboard] npm WARN logfile   path: '/root/.npm/_logs'
2024-07-24T11:30:56.939Z [kubeflow-dashboard] npm WARN logfile }
2024-07-24T11:30:56.943Z [kubeflow-dashboard]
2024-07-24T11:30:56.943Z [kubeflow-dashboard] ><EMAIL_ADDRESS>serve
2024-07-24T11:30:56.943Z [kubeflow-dashboard] > node dist/server.js
2024-07-24T11:30:56.943Z [kubeflow-dashboard]
2024-07-24T11:30:58.138Z [kubeflow-dashboard] Initializing Kubernetes configuration
2024-07-24T11:30:58.180Z [kubeflow-dashboard] Unable to fetch Application information: 404 page not found
2024-07-24T11:30:58.180Z [kubeflow-dashboard]
2024-07-24T11:30:58.190Z [kubeflow-dashboard] "other" is not a supported platform for Metrics
2024-07-24T11:30:58.190Z [kubeflow-dashboard] Using Profiles service at http://kubeflow-profiles.kubeflow:8081/kfam
2024-07-24T11:30:58.196Z [kubeflow-dashboard] Server listening on port http://localhost:8082 (in production mode)
2024-07-24T11:31:02.406Z [pebble] GET /v1/plan?format=yaml 378.805µs 200

Hey @orfeas-k this is what I have found. I think we are facing two issues here:
Using the upstream image

Logs will not be saved - we get a permission denied error and then a message that says logs will not be saved.

2024-07-24T13:15:57.228Z [pebble] Service "kubeflow-dashboard" starting: npm start
2024-07-24T13:15:57.456Z [kubeflow-dashboard]
2024-07-24T13:15:57.456Z [kubeflow-dashboard] ><EMAIL_ADDRESS>start
2024-07-24T13:15:57.456Z [kubeflow-dashboard] > npm run serve
2024-07-24T13:15:57.456Z [kubeflow-dashboard]
2024-07-24T13:15:57.666Z [kubeflow-dashboard] npm WARN logfile Error: EACCES: permission denied, scandir '/root/.npm/_logs'
2024-07-24T13:15:57.666Z [kubeflow-dashboard] npm WARN logfile  error cleaning log files [Error: EACCES: permission denied, scandir '/root/.npm/_logs'] {
2024-07-24T13:15:57.666Z [kubeflow-dashboard] npm WARN logfile   errno: -13,
2024-07-24T13:15:57.666Z [kubeflow-dashboard] npm WARN logfile   code: 'EACCES',
2024-07-24T13:15:57.666Z [kubeflow-dashboard] npm WARN logfile   syscall: 'scandir',
2024-07-24T13:15:57.666Z [kubeflow-dashboard] npm WARN logfile   path: '/root/.npm/_logs'
2024-07-24T13:15:57.666Z [kubeflow-dashboard] npm WARN logfile }
2024-07-24T13:15:57.685Z [kubeflow-dashboard]
2024-07-24T13:15:57.685Z [kubeflow-dashboard] ><EMAIL_ADDRESS>serve
2024-07-24T13:15:57.685Z [kubeflow-dashboard] > node dist/server.js
2024-07-24T13:15:57.685Z [kubeflow-dashboard]
2024-07-24T13:15:57.800Z [kubeflow-dashboard] npm ERR! code EACCES
2024-07-24T13:15:57.800Z [kubeflow-dashboard] npm ERR! syscall mkdir
2024-07-24T13:15:57.800Z [kubeflow-dashboard] npm ERR! path /root/.npm/_cacache/tmp
2024-07-24T13:15:57.800Z [kubeflow-dashboard] npm ERR! errno -13
2024-07-24T13:15:57.801Z [kubeflow-dashboard] npm ERR!
2024-07-24T13:15:57.801Z [kubeflow-dashboard] npm ERR! Your cache folder contains root-owned files, due to a bug in
2024-07-24T13:15:57.801Z [kubeflow-dashboard] npm ERR! previous versions of npm which has since been addressed.
2024-07-24T13:15:57.801Z [kubeflow-dashboard] npm ERR!
2024-07-24T13:15:57.801Z [kubeflow-dashboard] npm ERR! To permanently fix this problem, please run:
2024-07-24T13:15:57.801Z [kubeflow-dashboard] npm ERR!   sudo chown -R 1000:1000 "/root/.npm"
2024-07-24T13:15:57.801Z [kubeflow-dashboard]
2024-07-24T13:15:57.801Z [kubeflow-dashboard] npm ERR! Log files were not written due to an error writing to the directory: /root/.npm/_logs
2024-07-24T13:15:57.801Z [kubeflow-dashboard] npm ERR! You can rerun the command with `--loglevel=verbose` to see the logs in your terminal

This error message is not causing the service to exit, though, so I think it is not as critical.

There is a collision between two processes trying to use port 8082 - after showing the message about the logs, the service tries to start and returns the following:

2024-07-24T13:15:58.104Z [kubeflow-dashboard] Initializing Kubernetes configuration
2024-07-24T13:15:58.126Z [kubeflow-dashboard] Unable to fetch Application information: 404 page not found
2024-07-24T13:15:58.126Z [kubeflow-dashboard]
2024-07-24T13:15:58.127Z [kubeflow-dashboard] "other" is not a supported platform for Metrics
2024-07-24T13:15:58.127Z [kubeflow-dashboard] Using Profiles service at http://kubeflow-profiles.kubeflow:8081/kfam
2024-07-24T13:15:58.131Z [kubeflow-dashboard] [SEVERE] uncaughtException Error: listen EADDRINUSE: address already in use :::8082
2024-07-24T13:15:58.131Z [kubeflow-dashboard]     at Server.setupListenHandle [as _listen2] (node:net:1463:16)
2024-07-24T13:15:58.131Z [kubeflow-dashboard]     at listenInCluster (node:net:1511:12)
2024-07-24T13:15:58.131Z [kubeflow-dashboard]     at Server.listen (node:net:1599:7)
2024-07-24T13:15:58.131Z [kubeflow-dashboard]     at Function.listen (/usr/src/app/node_modules/express/lib/application.js:635:24)
2024-07-24T13:15:58.131Z [kubeflow-dashboard]     at /usr/src/app/dist/server.js:83:13
2024-07-24T13:15:58.131Z [kubeflow-dashboard]     at Generator.next (<anonymous>)
2024-07-24T13:15:58.131Z [kubeflow-dashboard]     at fulfilled (/usr/src/app/dist/server.js:5:58)
2024-07-24T13:15:58.131Z [kubeflow-dashboard]     at processTicksAndRejections (node:internal/process/task_queues:96:5) {
2024-07-24T13:15:58.131Z [kubeflow-dashboard]   code: 'EADDRINUSE',
2024-07-24T13:15:58.131Z [kubeflow-dashboard]   errno: -98,
2024-07-24T13:15:58.131Z [kubeflow-dashboard]   syscall: 'listen',
2024-07-24T13:15:58.131Z [kubeflow-dashboard]   address: '::',
2024-07-24T13:15:58.131Z [kubeflow-dashboard]   port: 8082
2024-07-24T13:15:58.131Z [kubeflow-dashboard] }
2024-07-24T13:15:58.137Z [pebble] Service "kubeflow-dashboard" stopped unexpectedly with code 243

Which suggests two processes are trying to open/use the same port. After closer inspection, I can see that the upstream image is indeed setting EXPOSE 8082 while at the same time our charm opens that port using the k8s service patch. These two seem to be colliding.
Using the rock

Logs are still failing to be saved, I get exactly the same error.
The conflict with the port goes away - this is expected because the container image from the rock will not attempt to open any port.

After closer inspection, I can see that the upstream image is indeed setting EXPOSE 8082 while at the same time our charm opens that port using the k8s service patch. These two seem to be colliding.

I think this is not accurate. The EXPOSE instruction does not actually do anything, or try to open a port

The application fails at this line https://github.com/kubeflow/kubeflow/blob/14e242de0799452910c891e66a5693dd8b06a637/components/centraldashboard/app/server.ts#L89-L92.

Permissions when running in the rock (in the charm)
root@kubeflow-dashboard-0:/# ls -ld /root/.npm/_logs/
drwxr-xr-x 2 root root 4096 Jul 24 13:51 /root/.npm/_logs/
Permission when running with upstream image (in the charm)
/usr/src/app # ls -ld /root/.npm/_logs/
drwxr-xr-x    1 root     root          4096 Jul 24 16:38 /root/.npm/_logs/

Workload container using upstream image
It doesn't look like there are any leftover processes running
╰─$ juju ssh --container kubeflow-dashboard kubeflow-dashboard/0
/usr/src/app # ps aux
PID   USER     TIME  COMMAND
    1 root      0:00 /charm/bin/pebble run --create-dirs --hold --http :38813 --verbose
   39 node      0:01 node dist/server.js
  258 root      0:00 sh
  265 root      0:00 ps aux

Logs error in rock
Resolving the logs error in rock is as simple as adding the required permissions to the directory /root/.npm, similar to what we already do in the rock. This can be done by adding the following lines
      mkdir -p ${CRAFT_PART_INSTALL}/root/.npm
      chown 584792:584792 ${CRAFT_PART_INSTALL}/root/.npm
      chmod 755 ${CRAFT_PART_INSTALL}/root/.npm

Tried this and it resulted in the following logs
2024-07-25T00:58:07.547Z [pebble] HTTP API server listening on ":38813".
2024-07-25T00:58:07.547Z [pebble] Started daemon.
2024-07-25T00:58:09.907Z [pebble] GET /v1/plan?format=yaml 679.937µs 200
2024-07-25T00:58:09.935Z [pebble] POST /v1/layers 261.457µs 200
2024-07-25T00:58:10.000Z [pebble] POST /v1/services 55.977274ms 202
2024-07-25T00:58:10.001Z [pebble] Service "kubeflow-dashboard" starting: npm start
2024-07-25T00:58:10.405Z [kubeflow-dashboard]
2024-07-25T00:58:10.405Z [kubeflow-dashboard] ><EMAIL_ADDRESS>start
2024-07-25T00:58:10.405Z [kubeflow-dashboard] > npm run serve
2024-07-25T00:58:10.405Z [kubeflow-dashboard]
2024-07-25T00:58:10.822Z [kubeflow-dashboard]
2024-07-25T00:58:10.822Z [kubeflow-dashboard] ><EMAIL_ADDRESS>serve
2024-07-25T00:58:10.822Z [kubeflow-dashboard] > node dist/server.js
2024-07-25T00:58:10.822Z [kubeflow-dashboard]
2024-07-25T00:58:11.010Z [pebble] GET /v1/changes/1/wait?timeout=4.000s 1.008423579s 200
2024-07-25T00:58:11.873Z [kubeflow-dashboard] Initializing Kubernetes configuration
2024-07-25T00:58:11.910Z [kubeflow-dashboard] Unable to fetch Application information: 404 page not found
2024-07-25T00:58:11.910Z [kubeflow-dashboard]
2024-07-25T00:58:11.915Z [kubeflow-dashboard] "other" is not a supported platform for Metrics
2024-07-25T00:58:11.915Z [kubeflow-dashboard] Using Profiles service at http://kubeflow-profiles.kubeflow:8081/kfam
2024-07-25T00:58:11.922Z [kubeflow-dashboard] Server listening on port http://localhost:8082 (in production mode)
2024-07-25T00:58:15.010Z [pebble] GET /v1/plan?format=yaml 253.228µs 200
2024-07-25T00:58:15.024Z [pebble] POST /v1/layers 254.62µs 200

Root cause
Redeployed and from the full logs , we notice that:

On first startup, there is no [SEVERE] uncaughtException Error: listen EADDRINUSE: address already in use :::8082 error. Rather, the service exits with a code 243.
Updating the charm's container service command and appending --loglevel=verbose as instructed in the ERROR logs,
2024-07-25T01:47:35.746Z [kubeflow-dashboard] npm ERR! You can rerun the command with `--loglevel=verbose` to see the logs in your terminal

it turns out that IIUC the 243 comes from the last "logs not written" error. This means that the service exits due to the permissions the process has in the /root/.npm directory:
2024-07-25T02:15:46.984Z [kubeflow-dashboard] npm ERR! Log files were not written due to an error writing to the directory: /root/.npm/_logs
2024-07-25T02:15:46.984Z [kubeflow-dashboard] npm ERR! You can rerun the command with `--loglevel=verbose` to see the logs in your terminal
2024-07-25T02:15:46.992Z [kubeflow-dashboard] npm timing command:run-script Completed in 535ms
2024-07-25T02:15:46.992Z [kubeflow-dashboard] npm timing command:start Completed in 539ms
2024-07-25T02:15:46.993Z [kubeflow-dashboard] npm notice
2024-07-25T02:15:46.993Z [kubeflow-dashboard] npm notice New major version of npm available! 8.19.4 -> 10.8.2
2024-07-25T02:15:46.993Z [kubeflow-dashboard] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.8.2>
2024-07-25T02:15:46.993Z [kubeflow-dashboard] npm notice Run `npm install -g<EMAIL_ADDRESS>to update!
2024-07-25T02:15:46.993Z [kubeflow-dashboard] npm notice
2024-07-25T02:15:46.994Z [kubeflow-dashboard] npm verb exit 243
2024-07-25T02:15:46.994Z [kubeflow-dashboard] npm timing npm Completed in 580ms
2024-07-25T02:15:46.995Z [kubeflow-dashboard] npm verb code 243

On following restarts, the node dist/server.js command fails with  EADDRINUSE: address already in use :::8082. This is caused by the fact that when the service is stopped with code 243, the node dist/server.js process is not killed along with the others and instead remains running in the container.
Running ps aux consecutively, we see that at some point we have two processes node dist/server.js running:
/usr/src/app # ps aux
PID   USER     TIME  COMMAND
    1 root      0:00 /charm/bin/pebble run --create-dirs --hold --http :38813 --verbose
   14 root      0:00 sh
  136 node      0:01 node dist/server.js
  161 root      0:00 /sbin/tini -- npm start
  162 root      0:00 npm start
  177 node      0:00 npm run serve
  192 node      0:00 node dist/server.js
  198 root      0:00 ps aux

This also explains some cases where  the service was constantly restarted but the dashboard was somewhat functional.

What we need to understand now is

Why the running process doesn't have the appropriate permissions? What's bugging me about this is that

This is intermittent. We 've seen the workload functioning in the same exact setup sometimes. In those cases, the logs indeed do not contain the last "logs not written" error
It was not the case in the past, even with the same image.

Why the node dist/server.js is not killed when the service is stopped?

Workaround
With all that in mind, I think it is safe enough to go with a rock which has the proper permissions for /root/.npm/, as described in the previous comment.

Why the node dist/server.js is not killed when the service is stopped?
Discussing with team, it looks like when a parent process exits (npm run serve), its child process (node dist/server.js) becomes an orphan process (not zombie) which means that they are put under PID 1. In the case of init, it looks like:

Init will eventually perform the wait system call for these orphans so they can die.

while it could be the Pebble handles those cases differently (?! really not sure about this - asked pebble team if they have any context).
Why the running process doesn't have the appropriate permissions?
Looking at ps aux output:
/usr/src/app # ps aux
PID   USER     TIME  COMMAND
    1 root      0:00 /charm/bin/pebble run --create-dirs --hold --http :38813 --verbose
  161 root      0:00 /sbin/tini -- npm start
  162 root      0:00 npm start
  177 node      0:00 npm run serve
  192 node      0:00 node dist/server.js
  198 root      0:00 ps aux

it looks like it's npm start that's changing which user is running npm run serve. Looking at npm docs, indeed

When npm is run as root, scripts are always run with the effective uid and gid of the working directory owner.

which means that the working-directory (usr/src/app) is owned by user node. Indeed, execing into the image:
/usr/src $ ls -l
total 4
drwxr-xr-x    1 node     node          4096 Jul 16 17:47 app

Thus, in order to fix this, we 'd need to give node user read/write permissions to /root/.npm/_logs and all of this before starting the service.

Since using the rock has solved our issue and we also have a workaround for using the upstream image, we 'll close this. #232 has been filed in order to track the permissions issue with using the upstream image.


Generate an nginx conf via an executable

Maybe also apache in the future

No point anymore, haha.


Vagrant: Fix Pandas installation

Don't merge yet, I haven't tested this on a clean box, will do tonight. Just putting this here in case anyone has hit the same issue.

OK, seems to work. Ready to merge if it looks good to you.


Error doing a custom build

Trying to do a custom build with the logstash adaptor from looplab: https://github.com/looplab/logspout-logstash
docker build .

...in a directory with a minimal dockerfile...
FROM gliderlabs/logspout:master

and modules.go...
package main

import (
        _ "github.com/gliderlabs/logspout/transports/udp"
        _ "github.com/looplab/logspout-logstash"
)

The build mostly succeeds but ultimately fails with...
ln: /var/run/docker.sock: File exists

Running Docker 1.5.

Thanks for reporting. Fixed in master just now.
https://github.com/gliderlabs/logspout/commit/103afb52311b4cb101b6ea2325ff1350371b606e


Update _common.yaml

Grammar

Hey, you made 2 PRs, which one should I look at? Either way, both are showing errors.

Duplicated


Cherry pick #1600 to release-v1.26

Description

https://github.com/tigera/operator/pull/1600
For PR author

[ ] Tests for change.
[ ] If changing pkg/apis/, run make gen-files
[ ] If changing versions, run make gen-versions

For PR reviewers
A note for code reviewers - all pull requests must have the following:

[ ] Milestone set according to targeted release.
[ ] Appropriate labels:

kind/bug if this is a bugfix.
kind/enhancement if this is a a new feature.
enterprise if this PR applies to Calico Enterprise only.

dependent on https://github.com/tigera/operator/pull/1836

/merge-when-ready delete-branch

OK, I will merge the pull request when it's ready, leave the commits as is when I merge it, and delete the branch after I've merged it.

I'm sorry but I failed delete the branch after merging the pull request.


json to txt files

Hi @bpbond
Could we go over converting json files to txt files?

Tomorrow at GCREW?

perfect - thanks!


📝 Update includes for docs/tutorial/fastapi/update-extra-data.md

Related to https://github.com/fastapi/sqlmodel/issues/1150

Thanks for the effort! This was covered in another PR, so I'll close this one now. :coffee: :cake:


Middleware resets req.url on res.send() and prevents further middleware to execute

Check this repository for details
Not related to express itself

I have the exact same issue. Middlewares after res.send/res.json don't execute in some cases, but not all. Took forever to find what the issue was.


Regenerate AdExchangeBuyer client

This PR was generated using Autosynth. :rainbow:
Here's the log from Synthtool:
synthtool > Executing /tmpfs/src/git/autosynth/working_repo/synth.py.
synthtool > Cloning https://github.com/googleapis/elixir-google-api.git.
synthtool > Running: docker run --rm -v/home/kbuilder/.cache/synthtool/elixir-google-api:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir16 scripts/generate_client.sh AdExchangeBuyer
synthtool > Wrote metadata to clients/ad_exchange_buyer/synth.metadata.

Whoops, do we need separate otp_app names if there are two different versions? @chingor13 any thoughts?

It looks like, in most cases of multiple versions, the various versions probably have identical or near-enough expectations regarding the configuration (see e.g. #1857). But this one is an exception.

Decided to let this through since it restores the original names. We may need to revisit it later if it actually becomes an issue.


pyspark 3.0.0 support?

noticed this in setup.py
  install_requires=[
          'bs4',
          'tornado',
          'pyspark<3.0.0',
          'jupyterlab>=2.0.0'
      ],

Is there any reason why you've pinned to < 3.0.0 for pyspark? I'm in a 3.0.0 env.
Great tool ... hope I get to use it! Thank you! :-)

Is it stands, the extension fails to run with pyspark 3 so I've pinned < 3 as a requirement. When I get time, I will be taking a look and what changes need to be made in order to migrate the extension to be compatible with newer versions of pyspark

🆒  thank you for the quick reply. eagerly watching!

@itsjafer  can we help with Spark3 support, this is a great tool!

It seems that the changes needed are not so big if you just look to support Spark 3, the main issue is that StageInfo.attemptId() has been renamed to StageInfo.attemptNumber() inside Spark API (https://spark.apache.org/docs/2.4.0/api/java/org/apache/spark/scheduler/StageInfo.html). This change could be hidden inside the listener.jar component itself, by exporting the old attemptIds.
I did a quick ad-hoc patch here (but it will break the compatibility with some older Spark versions) https://gist.github.com/footplus/22339282854630698d0af88dd7488192 ; perhaps it may be of some use while designing a complete patch.
Also, the packages adds pyspark as a dependency, which may not be very practical if pyspark is already provided in some way (via setting PYTHONPATH e.g.) not understandable by pip (it results in installing Spark's jars twice, and less control over Spark versions).

Thanks much @footplus  we ended up getting it working on 3. Happy to PR back.

@ianferreira can you?

@ianferreira Any plans on having this released?

@mtracy can you submit a PR

@ianferreira will do. Will be submitting on my other public account. @millertracy

Hey everyone, sorry I’ve been so busy with school lately, I will happily review a PR when it’s made :)

This is now resolved. jupyterlab-sparkmonitor 4.X is now pyspark 3.X compatible cc: @ianferreira @88manpreet @yosit @lhayhurst. I implemented the solution proposed by @footplus, thank you for the contribution!


'Lazy Pirate' Reliability pattern

Hi
Trying to implement the 'Lazy Pirate' Reliability pattern in the Unity client.
Any chance this has been implemented somewhere?
http://zguide.zeromq.org/cs:lpclient

This repo only provides the basic usage of ZeroMQ. If you want to use the advanced pattern you can definitely use it if you know how to implement it.


Add missing donation options

A. https://www.paribu.com/#/afet-destek
B. https://www.paribu.com/blog/en/news/about-our-disaster-support-plan-and-the-cryptocurrency-donation-system/
C. https://earthquaketurkey.notion.site/Turkiye-Earthquake-Donations-330ba83b6a93442b92fd46a414a928db
D?

D: https://twitter.com/TheBullduck/status/1624389815016751105

This issue can remain open.
Even though #88 have covered most of the missing donation options, there are still missing options from Paribu and BTCTurk.


add global and per-resource toggles for resource cloning behavior

let us turn on and off resource cloning

still need to think through the behavior of notifications and should probably add a warning to notifications when it finds more than one resource and be a bit more verbose about which one gets picked.
also need to add a couple more tests

I don't think offering a global option is helpful. Cookbook code will be written expecting one behavior or the other and changing it in a way the cookbook author can't control seems bad :-/

Lets you toggle it though and see what breaks in order to fix it (I'll certainly run with that setting and see what explodes).

The problem is the person toggling it is very rarely the person that could or will fix things. If, right before Chef 13, we wanted to have some kind of "send me to the future to see what happens" feature flag I could get more behind that but I don't think this has more value than the existing deprecation warnings and the ability to make deprecation warnings into errors.

So I sorta view the Chef::Config option here as exactly the 'send me to the future' option...  I'll set it on my runs, I can set it to run it through internal CI acceptance testing, etc.  Even if its literally just an option for me to test with, i kinda want that option for me...

apparently @thommay just told me i volunteered to write another RFC...  sigh...   to the thursday meeting then....

In a lightning change of mind, let's just land this so we can use it for testing.

We really need a way to turn cloning off so we can perform some extensive testing across the cookbook ecosystem including private customer cookbooks. This is a pretty big change and I'm afraid we're going to push it out with good intentions, but cause a huge amount of customer pain by accident. We don't need to document the flag for general usage. We just need to enable the ability to turn off cloning so we can test community cookbooks and customer support teams can test private cookbooks.

let me look through it again before mashing merge...

simplified PR, added scarier banner, we can also add a deprecation warning or remove the toggle entirely in Chef 13.


The engine "node" is incompatible with this module.

Yarn install output:
➜  playwright-record-example yarn add -D playwright-video
yarn add v1.21.1
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">= 12.13 <13". Got "13.0.1"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

I would only set it to >= 12.13, or what do you think? So that 13.x is also allowed.

Will fix this

Thanks for reporting @mxschmitt!

Should be fixed in 0.1.5


Whether the const keyword can be removed from compiler-core exported NodeTypes

Version
3.2.33
Reproduction link
github.com
Steps to reproduce
// 1
pnpm i

// 2
pnpm test compiler.demo

so  you can see the above error
the reason is:
// vue3/compiler-core/src/ast.ts

export const enum NodeTypes {
  ROOT,
  ELEMENT,
  TEXT,
  ……

because "const" keyword  , see link const enum in Typescript

compiler-core exports the enum NodeType
But because of the const keyword, there's really no way to use this NodeType if you want to
So I wonder if it is possible to remove the const keyword for NodeType
Then it makes sense to export the NodeType so that it can be used externally
What is expected?
The NodeType type can be used
What is actually happening?
The NodeType type can not be used now

Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the forum, the Discord server or StackOverflow.

@edison1105  but I think this is an API defect
because '@vue/compiler-core' is released as A separate package
it exports "NodeTypes" API, but outside can not be used.
What do you think?
or about API defects we can where discuss？

@cuixiaorui
as you can see const enum has no code associated with it after compilation, so it is relatively memory efficient and only serves as a syntax hint. And it's an internal enum for compiler-dom and compiler-sfc etc.


[BLOCKED] invitation: title not changing after updating the role

If you change the role of an invitation the title will stay the same, that is very confusing for the user.
example:

change a invitation with role "curator" to role "reader"
title will still say that the invitation is to join the community as a "curator"

Changing the Role in the members view changes the communities_members table/index, however it needs to be propagated to requests_metadata.

The role is hardcoded when the request is created:
            title = _('Invitation to join "{community}" as {role}.').format(
                community=community.metadata["title"],
                role=role.title,
            )

Even with a customized change notification workflow (update on DB instead of just reindex) this cannot be achieved if the role is merely hardcoded in the title (there is no way to replace/format/obtain the new one).
Can we display it somehow different? Shall we remove the role for now?


Filtering on vulnerabilities pages

It would be good if we had filtering options on the vulnerability pages, so we can hide/show vulnerabilities, look for a specific host, filter by CVSS score, status, risk etc.

Duplicate suggestion of

Hi @Ned-Flanders ; Just FYI; I have added some filters to the vulnerabilities page. More to come. Thanks!


Propose James Hewitt as a new reviewer

James has been an active member of the community for a while now, being very involved with many issues on this repo and in the Slack channel and has a number of contributions here.
Although I myself am new, I'm happy to propose him as a new reviewer on this project so that we can ramp up the activity.
As per Governance process, this must be approved by 4 of the existing maintainers.
CC: @Jamstah

Codecov Report
Patch and project coverage have no change.

Comparison is base (6ccc551) 55.85% compared to head (e51cfa6) 55.85%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3994   +/-   ##
=======================================
  Coverage   55.85%   55.85%
=======================================
  Files         110      110
  Lines       11069    11069
=======================================
  Hits         6183     6183
  Misses       4193     4193
  Partials      693      693

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

@waynr I dont know what the exact process is, but I think you need to open a PR removing yourself from the maintainers list announcing you're stepping down IIRC. Would you mind doing that?


Fix run_tempest.sh

The concurrency variable wasn't being set properly, as well as the check if the concurrency was set, making tempest jobs start to fail. This patch fixes it, and also set the shell to show the output of all commands, making it easier in the future to debug any failure.

/lgtm
thanks for the fix

/approve
fixes the issue with latest promoted tempest container.