Improvements for the equations plugin

Included in this PR:

Make explanation field focusable with "tab" key
Omit sign field with tab
Add button "add new equation"
Start with two lines of equations
Fix bug with missalignment and \underbrace and \overbrace
Variable length down arrow

TODOS:

[x]  Add "Add new equation" button

@inyono I have got positive feedback. After merging https://github.com/serlo/frontend/pull/1262 this PR can also be merged.


kz_mz has black/purple water texture

ziks's replay viewer doesn't support the refract shader and i'm not gonna add support)))


CSV containing the word REF affects mime type

We are experiencing a similair issue as rasied before by #georgeboot (trail below).
How can this behaviour be prevented?  In our example we are importing CSV files and nboted that certain files fail at import time with the exception "[filename] is an Invalid Spreadsheet file"
Upon investigating the file in question contains text in one of the columns
"TO BE COURIERED - REF MANDY"
After reading the issue posted below - we removed the word "REF" from the column and this resolved the issue.
However, that is not viable - how should this be addressed properly?
It turns out our CSV contained the word REF NO, which made the php function mime_content_type think the file has the mime type text/x-Algol68.
After all, it seems this is a bug in the SPL mime_content_type function, or the magic.mime list it uses.
Originally posted by @georgeboot in https://github.com/Maatwebsite/Laravel-Excel/issues/2107#issuecomment-473815323

Please open a new ticket with the issue template filled in as clearly stated by the issue template you removed.


Correctly handle error with external reference

Fixes #37

@whitlockjc Can you please review it? It significantly blocks me.

Thanks.  I'll get a release out.

v1.1.2 has been released.  Thanks for your help.


merge from konsum-frontend-svelte,template-css,template-svelte-app

package.json

chore(deps): add ^10.10.0 remove ^10.9.2 (devDependencies.npm-pkgbuild)

:tada: This PR is included in version 1.32.0 :tada:
The release is available on:

npm package (@latest dist-tag)
v1.32.0
GitHub release

Your semantic-release bot :package::rocket:


fix: mistake is function call.

there was a mistake which was accidentally introduced while calling the function. The function invocation missed the this keyword.

Oh yes! I accidentally updated the wrong one. Sorry!


Product availability through rule builder

Description
It would be great if we could use the rule builder to define the availability of a product.
Example

Can only be bought if article XYZ is also in cart
Can only be ordered up until a certain date

It would be a really great feature to have this available in the Shopware core. It is possible to implement something like this relatively easily but this should be possible by default.
And it should not only be products but also categories, so one can have categories only shown e.g. if a customer is logged in.
Btw. the product entity actually has two ID list fields for rules that actually does something like this but those fields cannot be set anywhere in the admin interface and the admin interrface would also use it in its listing, so products would disappear there too as the availability rule most likely will not match in the admin interface.

Hello,
Within our company roadmap and work capacity, we try to address each bug or improvement request but admit that not each one will be resolved. To continue our culture of honesty and openness, we are closing this issue to focus on our roadmap on behalf of all Shopware users.
If you feel like this issue is still impacting you, please create a new issue and let us know.
Thank you again for your valuable feedback.


Support @faker js v7.2.0

https://github.com/iendeavor/yup-schema-faker/issues/179
I fix that but not sure about:

version raise (I changed major in because projects with older faker will fail)
changelog update
readme update
fixing seed function for 'yarn build' (it failed before - value needs to be in array which is required by type)

Please just give me advice how to adjust commit or adjust it yourself, so we can use your great library in our project, thanks :)
plus it is maybe more like enhancement than bugfix, so sorry for that

cc @iendeavor could you take a look 🙏?

@Hourglasser23 Please take a look at this 🙏.

@Hourglasser23 Please take a look at this 🙏.

Np, tomorrow I'll check that :)

@iendeavor Should be ready 🙏🏻


Adding GUID generation

This is a node plugin that allows generating GUIDs from flow launcher

I guess you need to extract the .wox file inside the zip file to make this plugin works for flow.

I guess you need to extract the .wox file inside the zip file to make this plugin works for flow.

Thanks, updated the zip to zip the folder instead of the .wox

Hey @cfe84, any updates on this?

Closing due to inactivity. Please feel free to reopen.


Removing render.RenderableNode

Includes and supersedes #1169. Will need a rebase on master.

squashed and rebased up to 8c0fddc20d32c45687ddbd25e9001c17e065241b

Like this a lot.  Some stuff in experimental needs fixing, and I think we need to add some testing for the final, fully rendered NodeSummaries.
Also I think we need to address #836 ASAP.  And we can potentially experiment with not merging in existing metadata when we do a derived node.

Have run against example app, seems to do all the right things.

LGTM on this.

Rebased on 3744f475613f86a9506b1509e56339dec8ba9205


Visualising public type structure of a library

Describe the problem you are trying to solve

I would like to be able to quickly get an overview of the structure of public types and their relationship.
Describe the solution you'd like

I would like to have a cargo subcommand to list all exported types from a library. Basically visualising all the paths a user can "use".
Something like calling cargo export-tree and see a tree of my exported types starting with my crate-name as the root.
Notes

The expected output would look something like this:
my_lib
  |__ MyError
  |__ MyImportantStruct
  |__ my_mod_a
  |    |__ my_fn_a
  |    |__ my_fn_aa
  |
  |__ my_mod_b
       |__ MyStructB
       |__ MyTraitB

I would write the tool myself but I don’t know where to best get the relevant information which I can then traverse and turn into a tree like above.

I think this would be best implemented as an external command. You can see [cargo-modules](https://crates.io/crates/cargo-modules) as an example. rustc has a variety of unstable flags (see rustc -Zhelp) that can maybe export the information you're looking for. I think I've also seen some people scrape the output from rustdoc, though that can break over time.

Thank you!


RCTRedBox crash

After some JS runtime error (with red box shown) and fixing JS code and press Cmd+R to refresh, iOS app crashes within simulator. It was OK with React Native 0.10 version

I get the same on all my projects now.

Any response? It is really annoying and makes development much slow. I have to use previous version (0.10) to avoid this.

This was happening earlier in the life of React Native, it seemed to have gone away and made an appearance again :(

Solved temporarily just by commented that line ([self resignFirstResponder]). I don't understand why staff doesn't respond...

Can you let me know if this is still happening? We're now 12 versions newer.

Seems no, you thanks!


'followed quick start guide/steps..', but i cannot access <site/admin>

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
You do NOT have to include this information if this is a FEATURE REQUEST
-->
- Do you want to request a feature or report a bug?
report a bug
- What is the current behavior?
when i try to access:
https://miqui-me.netlify.com/admin/#/
I get a "not found" message
- If the current behavior is a bug, please provide the steps to reproduce.
follow quick start guide to publish a new site, in the netlify site configure Oauth app for the new published site, went to: https://miqui-me.netlify.com/admin/#/
..get a not found message...
- What is the expected behavior?
I expected to be able to use netlify CMS tool to edit the site.
- Please link or paste your config.yml below if applicable.
https://github.com/miqui/miqui.me/blob/master/site/config.toml

You'll need to put your own repository info in the config.yml: https://github.com/miqui/miqui.me/blob/master/site/static/admin/config.yml

Seems fixed now :)

Unfortunately, I have the same problem:
My repo
My config.yml
My Netlify site
My Netlify site admin panel - won't even show up - 404 instead

Your admin panel shows up just fine here


Added Server Insights permission

Pull Request Etiquette

[x] I have checked the PRs for upcoming features/bug fixes.
[x] I have read the contributing guidelines.

Changes

[ ] Internal code
[x] Library interface (affecting end-user code)
[ ] Documentation
[ ] Other: _____

Description
Since some months now, Discord has introduced a new feature called Server Insights. For now, this feature - reserved to Verified or Partnered Discord - allows us to track members activities and more. Those statistics who were previously hide are used to determine if a server can be introduced in the server discovery.
Currently, this feature is experimental, but, since a little number of days, the View Server Insights permission has popped out on the developer portal, meaning Discord want's to open this feature (at least to developers).
The goal of this PR is therefore to implement the missing View Server Insights present on the developer portal. The permission integer is 524288 (as shown on the developer portal), which is exactly 1 << 19 (the offset is therefore 19).

One thing tho: How is this usable for bots?
Like what does a bot get from having this permission, if it can even have it at all?

Waiting for discordapp/discord-api-docs#1421


test: sessions coverage

I'm looking around the code and using coveralls to add some tests. The scope will be sessions for this pull request.
The CI would be great for testing what I've done until now

Coverage increased (+0.3%) to 84.746% when pulling 741a8de4df3d1f93a9ef79665bfeb7d4eadef3bd on test/sessions-coverage into ab6834ad5e22fc6da9b89397a6b69a1cfffed885 on master.


new UsbFileWrapper in javafs cost too much time

2023-11-23 14:28:02.334 10589-11529 xptest:UsbFileWrapper   xyz.skybox.player.ovr                D  listFiles5:3
2023-11-23 14:28:02.334 10589-11529 xptest:UsbFileWrapper   xyz.skybox.player.ovr                D  listFiles6:3
2023-11-23 14:28:29.115 10589-11529 xptest:UsbFileWrapper   xyz.skybox.player.ovr                D  listFiles5:4
2023-11-23 14:28:29.115 10589-11529 xptest:UsbFileWrapper   xyz.skybox.player.ovr                D  listFiles6:4
2023-11-23 14:30:27.459 10589-11529 xptest:UsbFileWrapper   xyz.skybox.player.ovr                D  listFiles7
this is my code:
@Override
public UsbFile[] listFiles() throws IOException {
Log.d(TAG, "listFiles1");
if(dir == null) {
throw new UnsupportedOperationException("This is a file!");
}
Log.d(TAG, "listFiles2");
List list = new ArrayList<>();
Log.d(TAG, "listFiles3");
Iterator<? extends FSEntry> iterator = dir.iterator();
Log.d(TAG, "listFiles4");
int i = 1;
while(iterator.hasNext()) {
Log.d(TAG, "listFiles5:"+i);
FSEntry entry = iterator.next();
Log.d(TAG, "listFiles6:"+i);
list.add(new UsbFileWrapper(entry));
i++;
}
Log.d(TAG, "listFiles7");
UsbFile[] array = new UsbFile[list.size()];
array = list.toArray(array);
Log.d(TAG, "listFiles8");
return array;
}
When handling a USB drive with the exFAT file system, if a folder contains 1,000 files, this line of code takes about 30 seconds to execute. For over 2,000 files, it takes about 2 minutes:
list.add(new UsbFileWrapper(entry));
The listFiles method is frequently used in the project, and such long execution times obviously cause serious issues. It would be beneficial to find ways to optimize this time consumption, or to add some form of caching to improve performance.

@magnusja

Yeah the javafs is highly experimental. It wraps around the file system implementations of jnode. And they do not play super well with the buffers in libaums. This can be improved, question is is it better to implement sth like exFAT specifically for libaums. JNODE is under LGPL, which is also unfortunate. This probably takes a couple of weeks to implement. But I dont have any time.

Alright, thanks for getting back to me. I think the main problem is some unnecessary clashes between jnode and libaums. I'm gonna try and tackle it myself first, like saving the previously created usbfilewrapper to avoid creating it multiple times. In my tests, whipping up a usbfile on exfat takes like 60ms, which is quite a bit. I'll try my best to cut down on that. Really appreciate your time and response again. Hope you have an awesome day! @magnusja


--ext option not functional

I find that when an html file is saved without a file extension, http-server serves it with application/octet-stream, even if I set --ext html in the cli options (anyway, html is the default).
Seen on Mac Yosemite; Node v2.0.2

+1

+1

So this has been here since 2015? Hmm... wonder if it's a browser caching thing... I'll have a look on this.

A quick fix would simply be reordering this code and handling the html default extension by also setting text/html as the default media type:
https://github.com/indexzero/http-server/blob/fed98f2dbb87f1ea7a793e48a1975c20c9e970fa/lib/http-server.js#L50-L56
Anyone up for doing that? 😸


Fix failing CI tests on lint

Tests used by this library use a mix of CPython/CircuitPython and do not pass our linter. Added note to the top of file about why we're performing a global disable along with a pylint:disable= for each file with the errors thrown by the linter.
@kattni

@kattni  this is passing so I'll merge


Sandbox

Open an issue here for technical questions on how to implement Attribution Reporting API code, or questions on the docs or demo for this API. For questions on how to fulfil a certain use case with the API, file an issue in the spec repository instead.

Thank you for the information provided regarding where to post technical
questions and use case queries for the Attribution Reporting API. I have
some general feedback about the API that doesn't fall under technical
questions or specific use cases. Could you please advise on the appropriate
place to post this general feedback? Should it be filed in the spec
repository, or is there another preferred forum for such feedback?
Thank you for your guidance.
https://gpt.space/gmail?source=watermark

Thank you for the information on where to post technical questions and use
case queries for the Attribution Reporting API.
I have some general feedback about the API that doesn't fall under
technical questions or specific use cases. Could you please advise on the
appropriate place to post this general feedback? Should it be filed in the
spec repository, or is there another preferred forum for such feedback?
Thank you for your guidance.
https://gpt.space/gmail?source=watermark

Subject: Follow-Up on Project Status
Hi Team,
I hope this email finds you well. I wanted to follow up on the current
status of our ongoing project. Could you please provide an update on the
progress made so far and any potential roadblocks that we should be aware
of?
Additionally, if there are any areas where assistance is needed, please let
me know so that we can address them promptly.
Looking forward to your response.
Best regards,
[Your Name]
https://gpt.space/gmail?source=watermark

All of these responses appear to be spam - closing.


remove snowflake channel, bump up build number

remove snowflake channel, bump up build number in order to push it to defaults

Linter check found the following problems:
The following problems have been found:
WARNING: clone/recipe/meta.yaml:28: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:30: missing_wheel: For pypi packages, wheel should be present in the host section
Errors were found

Why do you remove the snowflake channel? It's a dependency of dbt which is only on snowflake.

Why do you remove the snowflake channel? It's a dependency of dbt which is only on snowflake.

yes, but dbt-extractor 0.4.1 was already on defaults, so if we do updates it goes to defaults

if version 0.5 is new in defaults, do we need to bump the build number? or is it because SF will detect a newer version and pick that one?

yes, we bumping  to shadow the one from snowflake channel

Linter check found the following problems:
The following problems have been found:
WARNING: clone/recipe/meta.yaml:28: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:30: missing_wheel: For pypi packages, wheel should be present in the host section
Errors were found


Details on previewing the message sent via rabbit MQ

https://trello.com/c/KDfyOeS1/331-specialist-publisher-implementation

I think this needs a bit more context since the page is about rabbitmq in general. That command is something you run against the publishing api, if you're interested in whats published to the published_documents exchange. Don't think that's obvious because we use rabbitmq for some other things as well.

@MatMoore updated and added content.

@MatMoore Updated for your viewing pleasure.

This is really useful! We have been using it today in integration. Will wait for @MatMoore  to give the final approval though.


Add ClientRunner for automatic cert rotation with the upstream CA.

Add more description to this PR? What is the 'auto cert rotation' used for?

@wattli Done.


feat: Add Lambda message pump service

Issue #, if available:
DOTNET-6879
Description of changes:
This PR adds the Lambda message pump service to process messages from an SQS queue
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Can this target a feature branch until at least unit tests are added?
Can you add sample applications in this PR? It'd be helpful to see how all of this is configured from the user's perspective during review.

I have targeted my branch to a feature branch for now. I'd prefer to get approvals on the approach that I am taking and then proceed to add unit tests.
I have added a sample Lambda function that uses the proposed design to process messages.

Closing this PR because I started a fair amount of rework separating Lambda into a separate project and other refactoring. I think it will just be easier to start a fresh PR.


add back execute support for miss schedule

This PR implements the backend logic of previous PR of #3218
Add a back execute flag in the missedScheduleManager as to execute the flow immediately if such flag is marked enabled. Once enabled, every miss detection will trigger an execution of flow, even if there are multiple missed schedule in a single detection. The detection reuses the same logic of previous PR #3209 of email notification.

How does this feature work? Will a new execution be triggered for each schedule miss?
Could you please add the explanation to the PR description?

LGTM! If I am right this PR is adding this flag and the usage of it will be in later PRs, please link this PR number to following PRs.

No this is the final PR:)
The trigger to execute flow if already implemented in MissedScheduleManager, I left the parameter "backExecutionEnabled" in there before, this PR gives that parameter the real value.

Actually no. Multiple misses will only trigger a single execution by the time web server realize there is a miss. So this feature is not intended for those frequent flows (e.g. scheduled every minute, usually those flows will have the ability to recover on its own, so this is useless feature for them), but mostly for those hourly/daily flows that a miss is really missing one execution for that single slot data.

LGTM! If I am right this PR is adding this flag and the usage of it will be in later PRs, please link this PR number to following PRs.

No this is the final PR:) The trigger to execute flow if already implemented in MissedScheduleManager, I left the parameter "backExecutionEnabled" in there before, this PR gives that parameter the real value.

LGTM! If I am right this PR is adding this flag and the usage of it will be in later PRs, please link this PR number to following PRs.

No this is the final PR:) The trigger to execute flow if already implemented in MissedScheduleManager, I left the parameter "backExecutionEnabled" in there before, this PR gives that parameter the real value.

Thanks for explaining! This is great! Good job!


:sparkles: keyValue / actions / array

fixes #105
fixes #103
TODOs

[ ] Tests

Coverage increased (+0.02%) to 99.533% when pulling 28b2874ac54df4f526c3a298b0034b1e628285af on arrays into 6dade9eace6bdbd1984990977ce54f4f7263c2c3 on master.


My suggestion: give up this unrealistic idea

As far as I know:

You need to compile it in a case-sensitive volume, which seems like impossible in homebrew.
The scotch in homebrew won't work, unless they agree to remove -DSCOTCH_PTHREAD flag.
zsh support is still buggy, see https://github.com/mrklein/openfoam-os-x/issues/60
CGAL support is also buggy, see https://github.com/mrklein/openfoam-os-x/issues/64
Takes too long time to compile and homebrew guys might be unhappy about it.

Hi! Another Mac & OpenFOAM user here who's also been attempting something like this. From what I've tried, I have to agree with your points 1 & 4. OTOH, I've managed to successfully compile and run v2112 using Homebrew's scotch. On the zsh front, I haven't run into any major issues (yet).
With what I got, I took a slightly different approach and have managed to package OpenFOAM into a cask (https://github.com/gerlero/openfoam2112-app), which contains a (read-only) case-sensitive DMG where OpenFOAM has been built from source. I'm using the unpatched v2112 sources plus all dependencies from Homebrew (except of course no CGAL).
Back to your first point, I think if there were a way to create the DMG within Homebrew's formula build sandbox, I guess that could make for a viable (though not sure if up to homebrew-core standards) formula; but for now I'm quite content with having been able to turn OpenFOAM into an installable cask. In any case, I wanted to let you and @apjanke know about my project (and I'm open to contributions).

I've managed to successfully compile and run v2112 using Homebrew's scotch.

I know scotch is OK but have you tried any pt-scotch case, like the motorbike case?

On the zsh front, I haven't run into any major issues (yet).

Sometimes when running scripts, zsh can't load OpenFOAM libraries. Happened on both my x86 hackintosh and M1.

I don't have a strict requirement to use Homebrew's scotch if your repo (and/or mrklein's) has a fix for that.

The fix is very simple: drop -DSCOTCH_PTHREAD flag. https://github.com/BrushXue/OpenFOAM-AppleM1/blob/c7fc31aba8ad1779116d94b73ad2e55d853ad5de/scotch.rb#L41
Is there any way to automatically follow and patch the latest homebrew script?

I think it's caused by https://develop.openfoam.com/Development/openfoam/-/issues/1661 and https://develop.openfoam.com/Development/openfoam/-/issues/1664.

Now I know why it's not happening all the time. Sometimes when I play around my hackintosh I turn off SIP. Didn't even think about it.

The fix is very simple: drop -DSCOTCH_PTHREAD flag. https://github.com/BrushXue/OpenFOAM-AppleM1/blob/c7fc31aba8ad1779116d94b73ad2e55d853ad5de/scotch.rb#L41 Is there any way to automatically follow and patch the latest homebrew script?

I see you proposed this change to homebrew-core, but it was never merged.. are they not in favor of making this change in core?

Now I know why it's not happening all the time. Sometimes when I play around my hackintosh I turn off SIP. Didn't even think about it.

Right now I'm trying a quick fix/workaround (https://github.com/gerlero/openfoam2112-app/pull/6).

The fix is very simple: drop -DSCOTCH_PTHREAD flag. https://github.com/BrushXue/OpenFOAM-AppleM1/blob/c7fc31aba8ad1779116d94b73ad2e55d853ad5de/scotch.rb#L41 Is there any way to automatically follow and patch the latest homebrew script?

I see you proposed this change to homebrew-core, but it was never merged.. are they not in favor of making this change in core?

Now I know why it's not happening all the time. Sometimes when I play around my hackintosh I turn off SIP. Didn't even think about it.

Right now I'm trying a quick fix/workaround (gerlero/openfoam2112-app#6).

I proposed this change in the PR. But homebrew maintainers said it's too old and shouldn't be enabled unless more people complain about it. So maybe if you start an issue they'll listen.

So, after learning more about the OpenFOAM build & install process and thinking about this some more, I'm afraid I'm in agreement with @BrushXue here: the case-sensitive-volume issue seems like pretty much a showstopper in terms of working with core Homebrew or most user Homebrew installations, the Scotch pthreads thing is also a problem I don't have an answer for (aside from just making a custom scotch formula), and hoo boy that compile time. Plus, there's just a lot of outstanding smaller issues in terms of getting this to compile and install "cleanly" on macOS (or, IMHO, "standard" Unix in general), and upstream doesn't seem enthusiastic about supporting Mac in this way. And if there's no hope of getting this in to Homebrew core where people can make use of binary bottles, there's a lot less of a win scenario here.
FWIW, I think the zsh issue is totally tractable: The usual way to do zsh support like this isn't to ship serious zsh support in the main package itself, but to create a separate third-party whatever-szh-support project, like openfoam-zsh-support, and all the zsh users of openfoam install that. Most software makers are not zsh experts, and vice versa, and it's fine to have "bindings" and shell support for a tool be a separate project, IMHO. Mostly works just fine in practice.
I'm afraid I don't have the spare juice to spend on this effort, given these constraints. So I'm gonna throw in the towel here. Maybe what's in this repo will be useful to somebody else who's more ambitious here. Feel free to copy or fork it, or if you want, I'll just hand over ownership of the repo to someone who'll actually do something with it.
@gerlero feel free to gank any code here you find useful for your project, with my blessing, and godspeed! FWIW, I think your cask approach is probably a better idea than what I've got here.
Sorry folks! This was my bad for getting too excited too soon.


Is there any way to update the name of the outer transaction span at the end of a request?

Using axum I have a very early middleware that attaches a span with a propegated request id from a header.
          let span = info_span!("request", %request_id);
          next.run(req).instrument(span).await

Since this is the first outermost span it becomes the Transaction for elastic APM, so it shows up as simply request in the UI for Elastic Observability.
From Elastic examples it seems usually these out transaction spans are annotated as HTTP 5xx POST /service/endpoint but much of that information is not known unitl after next.run(req).instrument(span).await has run.
Is there any way to update the transaction name?
I was about to try something like the following
            let span = info_span!("request", %request_id);
            let _enter = span.enter();
            let res = next.run(req).in_current_span().await;
            if let Some(id) = span.id() {
                let mut extensions = req.extensions_mut();
                if let Some(mut transaction) = extensions.get_mut::<tracing_elastic_apm::model::Transaction>() {
                    transaction.name= Some(.../*rest of logic here*/);
                }
            };
            res
 ``

but since Transaction is not `pub` outside the `tracing_elastic_apm` crate a gave up fairly quickly.
Any thoughts?

I can make all the model structs public. Would that solve your use case?

I think so. Let me try it locally with a cloned instance of the crate so you dont waste your time in case it doesnt work

With the APMLayer made public, and the model structs (particularly Transaction), I was able to add a new layer that implements the logic I was looking for.
Essentially i had to Wrap APMLayer in a new layer that mostly just sent the function calls through to APMLayer, but modified Transaction.name in some cases.
I'm not sure if thats too much to ask for (or if its the right way to do this. I am somewhat new to Rust, new to tracing-subscriber, and to APM).
Code below

pub struct ApmAugmentLayer {
    inner_layer: ApmLayer,
}

impl ApmAugmentLayer {
    pub fn new(layer: ApmLayer) -> Self {
        ApmAugmentLayer { inner_layer: layer }
    }
}

struct MatchStrVisitor {
    field: String,
    value: Option<String>,
}

impl Visit for MatchStrVisitor {
    fn record_debug(&mut self, _field: &Field, _value: &dyn Debug) {}
    fn record_str(&mut self, field: &Field, value: &str) {
        if field.name() == self.field {
            self.value = Some(value.to_string());
        }
    }
}

struct NameOverrideValue(String);

impl<S> Layer<S> for ApmAugmentLayer
where
    S: Subscriber + for<'lookup> LookupSpan<'lookup>,
{
    fn on_new_span(&self, attrs: &Attributes<'_>, id: &Id, ctx: Context<'_, S>) {
        self.inner_layer.on_new_span(attrs, id, ctx);
    }

    fn on_record(&self, span: &Id, values: &Record<'_>, ctx: Context<'_, S>) {
        {
            let spanref = ctx.span(span).expect("Span not found!");
            let mut extensions = spanref.extensions_mut();
            let mut visitor = MatchStrVisitor {
                field: "name_override".to_string(),
                value: None,
            };
            values.record(&mut visitor);
            if let Some(name_override) = visitor.value {
                extensions.insert(NameOverrideValue(name_override.to_string()));
            };
        };
        self.inner_layer.on_record(span, values, ctx);
    }

    fn on_event(&self, event: &Event<'_>, ctx: Context<'_, S>) {
        self.inner_layer.on_event(event, ctx);
    }

    fn on_enter(&self, id: &Id, ctx: Context<'_, S>) {
        self.inner_layer.on_enter(id, ctx);
    }

    fn on_exit(&self, id: &Id, ctx: Context<'_, S>) {
        self.inner_layer.on_exit(id, ctx);
    }

    fn on_close(&self, id: Id, ctx: Context<'_, S>) {
        {
            let span = ctx.span(&id).expect("Span not found!");
            let mut extensions = span.extensions_mut();
            if let Some(name_override) = extensions.remove::<NameOverrideValue>() {
                if let Some(transaction) = extensions.get_mut::<Transaction>() {
                    transaction.name = Some(name_override.0)
                }
            }
        };
        self.inner_layer.on_close(id, ctx);
    }
}

Usage in middleware
pub async fn wrap_request(
    req: Request<axum::body::Body>,
    next: Next,
) -> Result<Response<axum::body::Body>, Infallible> {
    let request_id = req
        .headers()
        .get(X_PURE_REQUESTID)
        .and_then(|value| value.to_str().ok())
        .map(ToString::to_string);

    let response = match request_id {
        Some(request_id) => {
            let span = info_span!("request", %request_id, name_override = field::Empty);
            let _enter = span.enter();
            let (path, method) = {
                let path = if let Some(path) = req.extensions().get::<MatchedPath>() {
                    path.as_str()
                } else {
                    req.uri().path()
                };
                let method = req.method().clone();
                (path.to_owned(), method)
            };
            let res = next.run(req).in_current_span().await;
            let summ_status = match res.status().as_u16() {
                200..=299 => "2xx",
                300..=399 => "3xx",
                400..=499 => "4xx",
                500..=599 => "5xx",
                _ => "Unk",
            };

            span.record(
                "name_override",
                format!("HTTP {} {} {}", summ_status, method, path),
            );

            res
        }
        None => next.run(req).await,
    };

    Ok(response)
}

Tracing layers
    let apm_layer = tracing_elastic_apm::new_layer(
        service_name.to_owned(),
        tracing_elastic_apm::config::Config::new(url.clone()).with_authorization(
            tracing_elastic_apm::config::Authorization::ApiKey(
                tracing_elastic_apm::config::ApiKey::new(id, key),
            ),
        ),
    )
    .expect("Bad APM Config");

    tracing_subscriber::registry()
        .with(ApmAugmentLayer::new(apm_layer)

Created this https://github.com/krojew/tracing-elastic-apm/pull/20 , currently using it in production and it solved my issues


skipChown by default

What happened?
In the helm charts, there is a step to chown /var/lib/redpanda/data to the redpanda user. This requires privileged access which adds complexity for locked down environments. It also appears to be not necessary, though some research needs to happen to track down why the code made it in...
What did you expect to happen?
Default install of helm charts should not attempt to chown
How can we reproduce it (as minimally and precisely as possible)?. Please include values file.

$ helm get values <redpanda-release-name> -n <redpanda-release-namespace> --all
# paste output here

Anything else we need to know?
No response
Which are the affected charts?
No response
Chart Version(s)

$ helm -n <redpanda-release-namespace> list
# paste output here

Cloud provider

This is basically a duplicate of #370.


What's the best way to fix the failing Travis build?

I'm looking to add support for another geocoding service to Geopy, but I'm kind of afraid to do it until the master project is passing its CI tests with Travis.
For me, It's that I want my PR to be accepted without a problem, and not passing all the tests is a surefire way to ensure my PR never gets merged.
But at the same time, I also love the Geopy project (been building tools with Geopy long before I started working on a geocoder project) and don't want to scare folks away from adopting it and instead toward more vendor-specific implementations.
So what's the best way forward?

@jqnatividad Done. I noticed you had an invite to join the "Committer" team to get commit access to the repo (I think ijl sent it). Anyway, I re-sent it. I don’t remember how to make that happen, but once you accept you’ll also be able to weed through the PRs yourself.

@mtigas thanks!  Will be sure to weed thru PRs judiciously. :)


Why don't we have an IMiddleware interface ?

I was reading the documentation about the middleware, and I saw something really strange : to create a Middleware, we can write a class with an Invoke method
public async Task Invoke(HttpContext context)

But we don't have an interface to define this.
https://docs.asp.net/en/latest/fundamentals/middleware.html#writing-middleware
The interface would be just something like this :
public interface IMiddleware
{
    Task Invoke(HttpContext context);
}

The problem is that we can call the function UseMiddleware with any class, and if the class doesn't contains the correct method we get the error at runtime instead of compilation. And I think the reflection code will be less performant than calling an interface method (didn't benchmark, I will trust you if you say no)
After browsing the source code I understood that we can use dependency injection in the Invoke method (like in the constructor), and it may be the reason we don't have a IMiddleware.
But this is not documented, and I don't think it will be used by many people. I even looked at several default aspnet middlewares, and I didn't see Dependency injection used there (it is always used in the constructor)
Is it really a good idea to loose the benefits of having an Interface in favor of an undocumented barely used functionnality ? Are there other benefits that I didn't see ?

The core abstraction is RequestDelegate. https://github.com/aspnet/HttpAbstractions/blob/dev/src/Microsoft.AspNetCore.Http.Abstractions/RequestDelegate.cs#L13
Classes with an Invoke method are only one pattern on top of the core abstraction. Inline lamdas are another common pattern:
https://github.com/aspnet/HttpAbstractions/blob/dev/src/Microsoft.AspNetCore.Http.Abstractions/Extensions/UseWhenExtensions.cs#L46
The DI scenario does discourage the use of interfaces, and the reflection perf hasn't been a concern since the reflection is resolved once at startup rather than per request.

Duplicate of #754


Building on FreeBSD fails

Bug Report

error[E0425]: cannot find function `is_library_file` in this scope
   --> src/coprocessor_v2/plugin_registry.rs:133:24
    |
133 |                     if is_library_file(file) {
    |                        ^^^^^^^^^^^^^^^ not found in this scope

error[E0425]: cannot find function `is_library_file` in this scope
   --> src/coprocessor_v2/plugin_registry.rs:248:20
    |
248 |                 if is_library_file(&file) {
    |                    ^^^^^^^^^^^^^^^ not found in this scope

For more information about this error, try `rustc --explain E0425`.

What version of TiKV are you using?

What operating system and CPU are you using?

FreeBSD 14.0
Steps to reproduce

What did you expect?
What did happened?

/severity minor


KV storage

[ ] KV Commands
[ ] KV queries: update stateful validation
[ ] Cache (permissions, etc)

#954


haskell: Don't use package-qualified and non-package-qualified grep

Description of changes
Using grep in 2 different ways can cause confusion and increase the closure, especially if it's not the same grep.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Or we merge this into staging…

I mean in the end that will likely also trigger another rebuild (unless we are careful with the timing) only advantage is it doesn’t happen on our branch. So I suggest we just wait for the merge impending merge and then merge it here.

No rush from my side. It was just a drive-by cleanup.

@ofborg build haskell.compiler.ghc948.hello

@ofborg haskell.packages.ghc948.microlens

@ofborg build haskell.packages.ghc948.microlens

Why test 948 specifically?

GHC >= 9.6 needs to be rebuilt.


Undefined left/right camera in WebXR observables

From: https://github.com/BabylonJS/Babylon.js/issues/7239#issuecomment-571075600
https://www.babylonjs-playground.com/#LUYXFU
I would expect that the state BABYLON.WebXRState.IN_XR is only set after everything WebXR related is set and ready.

Merged, will soon be available in the playground. Please reopen if there is any problem with it


[WIP] Clean code // Remove unnecessary props -- PART 1

Over time, WebView has evolved a lot and has gone through many updates, resulting today in a hard and messy code to maintain.
In order to keep the webview API as clean as possible, we are going to remove some props and do some code refactoring. But keep in mind that this will not affect what you can achieve with WebView.
Affected props:

originWhitelist: this prop is used to limit the URLs that webview can actually load.

Motivations

This prop can be completely emulated with onShouldStartLoadWithRequest().

Current code is
({ nativeEvent }: WebViewNavigationEvent) => {
    let shouldStart = true;
    const { url, lockIdentifier } = nativeEvent;

    if (!passesWhitelist(compileWhitelist(originWhitelist), url)) {
      Linking.openURL(url);
      shouldStart = false;
    }

    if (onShouldStartLoadWithRequest) {
      shouldStart = onShouldStartLoadWithRequest(nativeEvent);
    }

    loadRequest(shouldStart, url, lockIdentifier);
  };

The future code will be something like
({ nativeEvent }: WebViewNavigationEvent) => {
	const { url, lockIdentifier } = nativeEvent;

    if (
      onShouldStartLoadWithRequest
      && !onShouldStartLoadWithRequest(nativeEvent)
    ) {
      loadRequest(false, url, lockIdentifier);
    }
    loadRequest(true, url, lockIdentifier);
  };

This means that if you want to limit URLs, you'll need to do it directly inside your onShouldStartLoadWithRequest prop.

Removing it will even improve the current API by giving the user control over what should happen when the whitelist does not match, (So instead of doing #423 and adding a prop we can actually remove one) right now the webview forces Linking.openURL()

I agree with this removal. If people want to emulate it, they could provide a subclass of the WebView that implements onShouldStartLoadWithRequest and emulate the originWhitelist behavior.
👍

Discussed this yesterday with you but for public visibility, I also agree with this removal. There's no point in having 2 features where one can also provide what the other does anyway.

Could we provide a warning if that prop is used? And say something like "originWhitelist has been removed; use onShouldStartLoadWithRequest instead".

this is planned actually 👍


rubocop: don’t allow word arrays.

These save a little syntax but they are more confusing to non-Rubyists and the previous, inconsistent rule isn’t helpful.
I realise I’ve changed my mind here. Sorry!
I've not fixed up the uses of this yet because there's a fair few, they can't all be autocorrected and I'd rather discuss this change first.

If this goes in at all, I think it should be restricted to Homebrew/brew to preserve some flexibility in formulae.

I think that there is a fair amount of use in Hombrew/core of the percent-literal word array syntax, because it is one way of producing denser, but still readable, blocks of code.
Personally, I find it much easier to easily read and understand code that makes use of interpolation enabled word arrays, particularly when it is used in creating an array of arguments.

If this goes in at all, I think it should be restricted to Homebrew/brew to preserve some flexibility in formulae.
Personally, I find it much easier to easily read and understand code that makes use of interpolation enabled word arrays, particularly when it is used in creating an array of arguments.

I don't mind changing it just in Homebrew/brew but I do think that in Homebrew/homebrew-core we have more non-Rubyists than Homebrew/brew. If you're not experienced in Ruby: wtf does %w() do? [""] is more verbose but it's more obvious to more language that that's an array with a string in it. My thinking with this latest batch of Rubocop changes is avoiding the "there's more than one way to do it" and making our code more readable for non-Rubyists. Now we have Rubocop we also have autocorrection for this stuff, too.

I don't think the tradeoff is worth it.

@ilovezfs That's cool with me 👍. Will make this Homebrew/brew only.

Going to just leave this as-is; I think the Homebrew/brew vs. homebrew-core inconsistency will be confusing.


Idea: Extension for VS Code

I just created https://ideas.intersystems.com/ideas/DPI-I-602 to gauge interest in a possible VS Code extension for a more visual UX. Upvotes there are welcome, as are comments.

I have created https://openexchange.intersystems.com/package/IPM-in-VS-Code and entered it into the current contest. I'm continuing to add features, and contest voting is open!

Amazing - great to see, thank you @gjsjohnmurray !


fix: Fix domain resolution on client side

🔗 Linked issue
https://github.com/nuxt-modules/i18n/issues/2364
❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Thank you for your contribution!
Just the same PR as yours came one before, #2363
So close due to duplicate.
Thanks!


Update Compiler.cs

This fixes the exception:
System.InvalidOperationException: 'Collection was modified; enumeration operation may not execute.'

This occurs in cases where multiple requests for the same file occurs, via different threads as both could be running the AppendImportedSassFiles function and adding files at different states, where one has exited while the other is still processing because the short-circuiting of previously appended files to the _addedImports variable.
There is still a chance that when there are multiple request occurring in tandem that the 2nd request will exit first with a different key, without an exception but I haven't been able to reproduce it in my testing, to fix this there needs to be some sort of locking mechanism that allows the processing to occur only on a single thread while holding the other threads up, as a possible approach.

Thanks


Example not working: Logging not serializing arguments

Please tell us about your environment:

_winston version?_3.2.1

[ ] winston@2
[x ] winston@3

_node -v outputs:_v10.16.0
Operating System? (Windows, macOS, or Linux) Linux
Language? (all | TypeScript X.X | ES6/7 | ES5 | Dart) TypeScript 3.4.5

What is the problem?
    const log = createLogger({
        level: logLevel,
        format: format.json(),
        defaultMeta: { service: 'user-service' },
        transports: [
            new transports.File({ filename: 'logs/error.log', level: 'error' }),
            new transports.File({ filename: 'logs/combined.log' })
        ]
    });
        log.add(
            new transports.Console({
                format: format.simple()
            })
        );

Console transport is not serializing the arguments.
Expecting all arguments
What do you expect to happen instead?
According to https://github.com/winstonjs/winston/blob/master/README.md#usage the above states: ${info.level}: ${info.message} JSON.stringify({ ...rest })  instead the following code         log.debug('hello', { there: 1 }); results in the following: debug: hello [object Object] {"service":"user-service"}. My Object has not been serialized.
Other information

Hmm, I believe the issue I filed, #1933 is related to this. It seems like whenever two or more transports are in use, the first transport listed gets the full info object, but the second transport only receives an info object with Winston "known" properties, i.e. level', message, timestamp, and the [Symbol(splat)]` property.

There is a comment on #1430 which resolves the issue with info "losing data" between transports.


Update Go Swagger to pull from master

Description
After talking to contributors on the go swagger slack it has become clear that cutting timely releases is not a priority for them and they recommended living on master. There are a heap of good fixes that have been made since the last release last december, many of which around improving validations. One concrete fix is that previously poorly formed UUIDs were still sent into handlers, now they are bounced by swagger like any other poorly formatted parameter.
Reviewer Notes
Unfortunately, most all of our tests are at the handler level, (we have chosen to to validate swagger's behaviors) so it is probably worth trying to hit some some of our APIs with invalid data and make sure that you get back the expected swagger error.
Verification Steps

[ ] All tests pass.
[ ] Code follows the guidelines for Logging
[ ] Uploading a file still works (the only breaking api change I had to update for)
[ ] Swagger still returns errors for invalid data

Will this work properly with our automatic dependency updater?

@jim yes, our automatic dependency updater will pull from master every time instead of looking for the latest release. It will be locked to that version until the dependency updater runs again.


Buildkite fixes

Issue Number
Found during ADP-1062.
Overview

Improve display of section headers in logs
Don't run integration tests on every PR (caused by #2789)

bors r+

bors r+


Why are we recommending to remove ciphers and modify the default cipher location in public AD FS documentation?

Why are we recommending to remove ciphers and modify the default cipher location in public AD FS documentation???
https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/operations/manage-ssl-protocols-in-ad-fs#enabling-or-disabling-additional-cipher-suites
We should be indicating that –
There are two Microsoft supported methods of configuring cipher suites:
Via GP: https://msdn.microsoft.com/en-us/library/windows/desktop/bb870930(v=vs.85).aspx
Via cmdlets: https://technet.microsoft.com/en-us/library/dn296632.aspx
Is there some AD FS needful that needs to have the value as REG_MULTI_SZ
As opposed to the GP location which is REG_SZ?

#label:"doc-enhancement"


PySide6: could not load the Qt platform plugin "xcb" in "" even though it was found

This problem started appearing after version 2.3, so with Nuitka versions 2.3.1 and 2.3.2. The conditions are the same for all tests, and with Nuitka 2.3, the application that makes use of PySide6 is correctly compiled and runs smoothly.
# nuitka --version
2.3
Commercial: None
Python: 3.11.9 (main, May  9 2024, 14:13:06) [GCC 9.4.0]
Flavor: GitHub Actions Python
Executable: /opt/hostedtoolcache/Python/3.11.9/x64/bin/python
OS: Linux
Arch: x86_64
Distribution: Ubuntu (based on Debian) 20.04.6
Version C compiler: /usr/bin/gcc (gcc 9).

When compiling with Nuitka 2.3.1 or 2.3.2, the application is not launching and the problem is related to the following error:
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

The app.dist folders generated by Nuitka 2.3 and 2.3.1 include the same files and plugin and as stated above, the working conditions are the same in both cases (excluding a different version of Nuitka):
# nuitka --version
2.3.1
Commercial: None
Python: 3.11.9 (main, May  9 2024, 14:13:06) [GCC 9.4.0]
Flavor: GitHub Actions Python
Executable: /opt/hostedtoolcache/Python/3.11.9/x64/bin/python
OS: Linux
Arch: x86_64
Distribution: Ubuntu (based on Debian) 20.04.6
Version C compiler: /usr/bin/gcc (gcc 9).

Something that caught my attention is present in Nuitka-Inclusion during the compilation:
Nuitka 2.3
Nuitka-Inclusion: Setting 'RPATH' value '$ORIGIN/../../..' for 'app.dist/PySide6/qt-plugins/platforms/libqxcb.so'
Nuitka 2.3.1 and later
Nuitka-Inclusion: Setting 'RPATH' value '$ORIGIN/../../..:$ORIGIN/../..:$ORIGIN/..' for 'app.dist/PySide6/qt-plugins/platforms/libqxcb.so'
Might be something related to this commit?
I'm available for any other useful tests or any other details

The longer RPATH should not be an issue, or so I am thinking.

mmm, I'm still investigating...let's see if I'm able to provide some more useful information by running the same tests on my local machine

The 2.3.1 release has had an issue that was regression, using 2.3.3 would be advised. However, on Linux right now it segfaults for me in shiboken C++ DLL code with PySide 6.7.1, I am trying to eliminate your hunch that it could be that.

I am getting this:
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff6ede80c in Shiboken::Module::create(char const*, void*) () from /home/hayen/repos/Py2C/PySideQmlPolarchartTest.dist/shiboken6/../libshiboken6.abi3.so.6.7
#0  0x00007ffff6ede80c in Shiboken::Module::create(char const*, void*) () from /home/hayen/repos/Py2C/PySideQmlPolarchartTest.dist/shiboken6/../libshiboken6.abi3.so.6.7
#1  0x00007ffff6f113f1 in PyInit_Shiboken () from /home/hayen/repos/Py2C/PySideQmlPolarchartTest.dist/shiboken6/Shiboken.so
#2  0x00005555556519dd in callIntoExtensionModule (tstate=0x555555c969a8 <_PyRuntime+459656>, full_name=0x555555bd24be "shiboken6.Shiboken", filename=0x7fffffff80e0 "/home/hayen/repos/Py2C/PySideQmlPolarchartTest.dist/shiboken

Even with the change reverted. You will be very welcome to try it independently, I might be having a 3.12 specific issue there.

Nuitka 2.3
# nuitka --version
2.3
Commercial: None
Python: 3.11.9 (main, Apr 17 2024, 00:00:00) [GCC 14.0.1 20240411 (Red Hat 14.0.1-0)]
Flavor: Fedora Python
Executable: /home/marco/Downloads/.venv/bin/python
OS: Linux
Arch: x86_64
Distribution: Fedora 40
Version C compiler: /usr/lib64/ccache/gcc (gcc 14).

Nuitka 2.3.1 (with a fresh environment)
# nuitka --version
2.3.1
Commercial: None
Python: 3.11.9 (main, Apr 17 2024, 00:00:00) [GCC 14.0.1 20240411 (Red Hat 14.0.1-0)]
Flavor: Fedora Python
Executable: /home/marco/Downloads/.venv1/bin/python
OS: Linux
Arch: x86_64
Distribution: Fedora 40
Version C compiler: /usr/lib64/ccache/gcc (gcc 14).

Both versions provide a working application on my local machine...now I'm quite confused

I am not seeing which runner you use, nor what Nuitka options used to compile, so I don't think you provided nearly enough input yet.

Yep, the github runner was ubuntu-20.04 and the input is:
python -m nuitka app.py \
  --standalone \
  --show-modules \
  --assume-yes-for-downloads \
  --enable-plugin=pyside6 \
  --noinclude-dlls=libQt6Charts* \
  --noinclude-dlls=libQt6Quick3D* \
  --noinclude-dlls=libQt6Sensors* \
  --noinclude-dlls=libQt6Test* \
  --noinclude-dlls=libQt6WebEngine* \
  --include-qt-plugins=sensible \
  --include-qt-plugins=styles \
  --include-qt-plugins=qml \
  --include-qt-plugins=multimedia \
  --force-stderr-spec="{TEMP}/artemis.err.log" \
  --force-stdout-spec="{TEMP}/artemis.out.log"

I'll try with the 2.3.3 as you suggested

Also, RPATH vs. RUNPATH, wasn't there lately a sort of hiccup, because systems dropped support of one older method, and it broke games and steam even.
There is this
       --force-rpath
              Forces the use of the obsolete DT_RPATH in the file instead of DT_RUNPATH.  By
              default DT_RPATH is converted to DT_RUNPATH.

Maybe there is no such conversion on older systems.

The manpage for patchelf is the same there, so that should be ruled out.

Okay, so I tried again with Nuitka 2.3.3, removing sensible (thanks for the hint) and all the --noinclude-dlls but unfortunately the compiled application is not working and the error is always the same. Yep, I checked patchelf as well...the problem is not there unfortunately...
ldd on PySide6/qt-plugins/platforms/libqxcb.so on the github runners gives this result:
 	linux-vdso.so.1 (0x00007ffc534e8000)
	libQt6XcbQpa.so.6 => /home/runner/work/Artemis_DEV/Artemis_DEV/app.dist/PySide6/qt-plugins/platforms/../../../libQt6XcbQpa.so.6 (0x00007f7f9a5ac000)
	libQt6Gui.so.6 => /home/runner/work/Artemis_DEV/Artemis_DEV/app.dist/PySide6/qt-plugins/platforms/../../../libQt6Gui.so.6 (0x00007f7f99bb3000)
	libGL.so.1 => /lib/x86_64-linux-gnu/libGL.so.1 (0x00007f7f99b1c000)
	libQt6Core.so.6 => /home/runner/work/Artemis_DEV/Artemis_DEV/app.dist/PySide6/qt-plugins/platforms/../../../libQt6Core.so.6 (0x00007f7f99439000)
	libxkbcommon.so.0 => /lib/x86_64-linux-gnu/libxkbcommon.so.0 (0x00007f7f993f7000)
	libxkbcommon-x11.so.0 => not found
	libxcb-cursor.so.0 => not found
	libxcb-icccm.so.4 => not found
	libxcb-image.so.0 => not found
	libxcb-keysyms.so.1 => not found
	libxcb-randr.so.0 => not found
	libxcb-render-util.so.0 => not found
	libxcb-shm.so.0 => /lib/x86_64-linux-gnu/libxcb-shm.so.0 (0x00007f7f993ee000)
	libxcb-sync.so.1 => /lib/x86_64-linux-gnu/libxcb-sync.so.1 (0x00007f7f993e4000)
	libxcb-xfixes.so.0 => /lib/x86_64-linux-gnu/libxcb-xfixes.so.0 (0x00007f7f993da000)
	libxcb-render.so.0 => /lib/x86_64-linux-gnu/libxcb-render.so.0 (0x00007f7f993cb000)
	libxcb-shape.so.0 => not found
	libxcb-xkb.so.1 => not found
	libxcb.so.1 => /lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f7f9939f000)
	libX11-xcb.so.1 => /lib/x86_64-linux-gnu/libX11-xcb.so.1 (0x00007f7f9939a000)
	libX11.so.6 => /lib/x86_64-linux-gnu/libX11.so.6 (0x00007f7f9925d000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f7f99257000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f7f99232000)
	libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f7f99050000)
	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f7f98f01000)
	libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f7f98ee6000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f7f98cf4000)
	libxcb-cursor.so.0 => not found
	libxcb-icccm.so.4 => not found
	libxcb-image.so.0 => not found
	libxcb-keysyms.so.1 => not found
	libxcb-randr.so.0 => not found
	libxcb-render-util.so.0 => not found
	libxcb-shape.so.0 => not found
	libxcb-xkb.so.1 => not found
	libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007f7f98bc6000)
	libxkbcommon-x11.so.0 => not found
	libgthread-2.0.so.0 => /lib/x86_64-linux-gnu/libgthread-2.0.so.0 (0x00007f7f98bc1000)
	libEGL.so.1 => not found
	libfontconfig.so.1 => /lib/x86_64-linux-gnu/libfontconfig.so.1 (0x00007f7f98b78000)
	libQt6DBus.so.6 => /home/runner/work/Artemis_DEV/Artemis_DEV/app.dist/PySide6/qt-plugins/platforms/../../../libQt6DBus.so.6 (0x00007f7f98aaf000)
	libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f7f98a93000)
	libfreetype.so.6 => /lib/x86_64-linux-gnu/libfreetype.so.6 (0x00007f7f989d4000)
	libGLdispatch.so.0 => /lib/x86_64-linux-gnu/libGLdispatch.so.0 (0x00007f7f9891a000)
	libGLX.so.0 => /lib/x86_64-linux-gnu/libGLX.so.0 (0x00007f7f988e6000)
	libicui18n.so.73 => /home/runner/work/Artemis_DEV/Artemis_DEV/app.dist/PySide6/qt-plugins/platforms/../../../libicui18n.so.73 (0x00007f7f98597000)
	libicuuc.so.73 => /home/runner/work/Artemis_DEV/Artemis_DEV/app.dist/PySide6/qt-plugins/platforms/../../../libicuuc.so.73 (0x00007f7f9837f000)
	libicudata.so.73 => /home/runner/work/Artemis_DEV/Artemis_DEV/app.dist/PySide6/qt-plugins/platforms/../../../libicudata.so.73 (0x00007f7f964f1000)
	librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f7f964e5000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f7f9a66c000)
	libXau.so.6 => /lib/x86_64-linux-gnu/libXau.so.6 (0x00007f7f964df000)
	libXdmcp.so.6 => /lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007f7f964d7000)
	libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f7f96464000)
	libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007f7f96436000)
	libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007f7f9642b000)
	libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007f7f963da000)
	libpng16.so.16 => /lib/x86_64-linux-gnu/libpng16.so.16 (0x00007f7f963a2000)
	libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0 (0x00007f7f96388000)
	libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x00007f7f962d9000)
	liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007f7f962ae000)
	liblz4.so.1 => /lib/x86_64-linux-gnu/liblz4.so.1 (0x00007f7f9628d000)
	libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007f7f9616f000)
	libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007f7f9614c000)

I found also this one https://bugreports.qt.io/browse/PYSIDE-2283, they have the same problem but i don't think it's super useful. They just mention missing dependencies and documentation...they also mention an issue posted here on the first part of 2023 (https://github.com/Nuitka/Nuitka/issues/2138)

Well, Nuitka does not include the system DLLs needed by Qt in the distribution, because well, they are never portable in any good way. Make sure to install them on the systems you run your application on.

Well, still I firmly don't think this is due to system DLLs for a simple reason: in my first post the only thing that changes between the two tests is the version of Nuitka. In one case the compiled application works fine, in the other is not...

After few other investigations, using QT_DEBUG_PLUGINS, this could be the real reason:
qt.core.plugin.factoryloader: checking directory path "/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/../PySide6/qt-plugins/platforms" ...
qt.core.plugin.factoryloader: looking at "/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/../PySide6/qt-plugins/platforms/libqeglfs.so"
qt.core.plugin.loader: Failed to find metadata in lib /home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqeglfs.so: '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqeglfs.so' is not a Qt plugin (metadata not found)
qt.core.plugin.factoryloader: "Failed to extract plugin meta data from '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqeglfs.so': '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqeglfs.so' is not a Qt plugin (metadata not found)"
         not a plugin
qt.core.plugin.factoryloader: looking at "/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/../PySide6/qt-plugins/platforms/libqlinuxfb.so"
qt.core.plugin.loader: Failed to find metadata in lib /home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqlinuxfb.so: '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqlinuxfb.so' is not a Qt plugin (metadata not found)
qt.core.plugin.factoryloader: "Failed to extract plugin meta data from '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqlinuxfb.so': '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqlinuxfb.so' is not a Qt plugin (metadata not found)"
         not a plugin
qt.core.plugin.factoryloader: looking at "/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/../PySide6/qt-plugins/platforms/libqminimal.so"
qt.core.plugin.loader: Failed to find metadata in lib /home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqminimal.so: '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqminimal.so' is not a Qt plugin (metadata not found)
qt.core.plugin.factoryloader: "Failed to extract plugin meta data from '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqminimal.so': '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqminimal.so' is not a Qt plugin (metadata not found)"
         not a plugin
qt.core.plugin.factoryloader: looking at "/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/../PySide6/qt-plugins/platforms/libqminimalegl.so"
qt.core.plugin.loader: Failed to find metadata in lib /home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqminimalegl.so: '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqminimalegl.so' is not a Qt plugin (metadata not found)
qt.core.plugin.factoryloader: "Failed to extract plugin meta data from '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqminimalegl.so': '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqminimalegl.so' is not a Qt plugin (metadata not found)"
         not a plugin
qt.core.plugin.factoryloader: looking at "/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/../PySide6/qt-plugins/platforms/libqoffscreen.so"
qt.core.plugin.loader: Failed to find metadata in lib /home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqoffscreen.so: '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqoffscreen.so' is not a Qt plugin (metadata not found)
qt.core.plugin.factoryloader: "Failed to extract plugin meta data from '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqoffscreen.so': '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqoffscreen.so' is not a Qt plugin (metadata not found)"
         not a plugin
qt.core.plugin.factoryloader: looking at "/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/../PySide6/qt-plugins/platforms/libqvkkhrdisplay.so"
qt.core.plugin.loader: Failed to find metadata in lib /home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqvkkhrdisplay.so: '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqvkkhrdisplay.so' is not a Qt plugin (metadata not found)
qt.core.plugin.factoryloader: "Failed to extract plugin meta data from '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqvkkhrdisplay.so': '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqvkkhrdisplay.so' is not a Qt plugin (metadata not found)"
         not a plugin
qt.core.plugin.factoryloader: looking at "/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/../PySide6/qt-plugins/platforms/libqvnc.so"
qt.core.plugin.loader: Failed to find metadata in lib /home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqvnc.so: '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqvnc.so' is not a Qt plugin (metadata not found)
qt.core.plugin.factoryloader: "Failed to extract plugin meta data from '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqvnc.so': '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqvnc.so' is not a Qt plugin (metadata not found)"
         not a plugin
qt.core.plugin.factoryloader: looking at "/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/../PySide6/qt-plugins/platforms/libqwayland-egl.so"
qt.core.plugin.loader: Failed to find metadata in lib /home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqwayland-egl.so: '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqwayland-egl.so' is not a Qt plugin (metadata not found)
qt.core.plugin.factoryloader: "Failed to extract plugin meta data from '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqwayland-egl.so': '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqwayland-egl.so' is not a Qt plugin (metadata not found)"
         not a plugin
qt.core.plugin.factoryloader: looking at "/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/../PySide6/qt-plugins/platforms/libqwayland-generic.so"
qt.core.plugin.loader: Failed to find metadata in lib /home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqwayland-generic.so: '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqwayland-generic.so' is not a Qt plugin (metadata not found)
qt.core.plugin.factoryloader: "Failed to extract plugin meta data from '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqwayland-generic.so': '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqwayland-generic.so' is not a Qt plugin (metadata not found)"
         not a plugin
qt.core.plugin.factoryloader: looking at "/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/../PySide6/qt-plugins/platforms/libqxcb.so"
qt.core.plugin.loader: Failed to find metadata in lib /home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqxcb.so: '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqxcb.so' is not a Qt plugin (metadata not found)
qt.core.plugin.factoryloader: "Failed to extract plugin meta data from '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqxcb.so': '/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/PySide6/qt-plugins/platforms/libqxcb.so' is not a Qt plugin (metadata not found)"
         not a plugin
qt.core.plugin.factoryloader: checking directory path "/home/marco/Downloads/Artemis-Linux-x86_64-4.0.0/platforms" ...
qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in ""
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

With Nuitka 2.3.1-2.3.3 the qt-plugins are present but are not recognized anymore as a Qt plugin because of some lacking metadata. I don't think this issue should be closed

It cannot load the DLLs due to missing dependencies. Nuitka used to include system DLLs in previous versions, checkout the changelog for when that changed. Nuitka is NOT going to provide the X11 client libraries, so the X plugin of Qt will have to find them on the system. If it does not, it's not going to run. Nuitka is also NOT going to provide wayland libraries, or audio likes, or things the file dialog would like to see from system.
It's not feasible to run old X11 on newer systems anymore, that is why this was discovered and stopped. Before, only selectively the most system-dependent DLLs were included. But nowadays for a PyPI package, not including them is the norm. If you want to change that, you have to manually edit the Nuitka package configuration and use an internal flag that we may not even document yet, not sure now. Basically we only deliver PyPI included DLLs these days.
Yours,
Kay

Thanks a lot, Kay for the detailed explanation! Now, the origin of the problem is much more clear to me.
Best regards,
Marco


cmd/cue: add yaml support to export command

Eventhough json is a subset of the yaml specification from a end-user perspective who is reading wants to read yaml files it might make sense to support for "pretty" yaml as well in the export command.
It probably is also easy to implement as cue already has support for marshaling yaml in the encoding package.
cue version
$ cue version
cue version 0.0.14 linux/amd64

There is already flag for this (--out), it just needs add support for yaml, which already exists indeed.
It currently packages do not output comments, but that is a separate topic (requires port to go-yaml v3, which has additional benefits as well).

What are the other benifits of using go-yaml v3 besides comments ?

@xinau: it supposedly has an AST that allows extracting position information, which means I can get rid of internal/yaml (and remove a maintenance burden). It would also allow getting raw anchor and translate them into equivalent CUE constructs.

Done. Does not output comments yet, but that is a different issue.

This issue has been migrated to https://github.com/cue-lang/cue/issues/182.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.


Explore Travis CI Integration for repo

Prefer to enable this plugin in order to make new team/contributors onboarding smoother

@devsatishm tried to enable Travis CI, went to the Sawtooth NEXT Contributors space and updated to "maintainer". But that didn't work.

We'll need better permissions to enable Travis or any other plugin in this repo in the future.
I see this -
"You don't have sufficient rights to enable this repo on Travis.
Please contact the admin to enable it or to receive admin rights yourself."

On it! Bear with me...

.travis.yml is pushed to master.  Travis CI should kick in whenever we enable the integration.

Anyway we can get this tested to confirm this is working as expected?

Next steps: Repo admin need to test. Will defer to Chris for help

will reach out to Chris. Then will get on chat forum to find the owner for the Git NEXT repo.

This looks good now! Travis is now enabled!

https://github.com/hyperledger/sawtooth-next-directory/pull/42  should enable this integration.


extern decorators

Implementation of extern decorators
Decorator accessor syntax
New keyword for defining decorators and accessor:

dec: Declare a decorator
fn: Declare a function
extern: Mark decorator as implemented in TS

extern dec doc(target: entity, value: string, data?: Record<string, string>);
extern fn getDoc(target: entity): string;

Add new reflection namespace
To be able to support decorator signature in Cadl we need a way to specify a cadl Type as a type in cadl(Enum, Interface, etc.).
Create a new reflection.cadl containing a model for each one of the Cadl Type
namespace Cadl.Reflection;

model Entity {};
model Model {}
model Interface {}

TS Interface Name
Cadl reference

Type
Type

Model
Model

ModelProperty
ModelProperty

Interface
Interface

Enum
Enum

EnumMember
EnumMember

Namespace
Namespace

Operation
Operation

StringLiteral
StringLiteral

NumericLiteral
NumericLiteral

BooleanLiteral
Boolean

Tuple
Tuple

Union
Union

UnionVariant
UnionVariant

IntrinsicType
N/A

FunctionType
N/A

ObjectType
N/A

TemplateParameter
N/A

Projection
N/A

pri: 1
est: 13

This is interesting.  Is the extern syntax primarily for feeding symbols and signatures to tooling such as the language server?  Could this be implemented as a JavaScript-side API instead?  What advantages are offered by having an explicit extern declaration in Cadl?

The extern decorator is part of the bigger decorator in cadl picture described in this design issue #996. It is a way to declare the decorator definition for a decorator written in JS/TS and get type checking and IDE support(signature help, autocomplete, etc.)
This would be inline with having decorators defined in pure Cadl as described in the issue above. The other advantage is that JS files in cadl just gets imported, not parsed, so we don't have any information on where decorators are defined which makes diagnostic reporting or going to definition a little tricky. There is of course ways we could overcome this this particular js import problem but as we see having the ability to define some decorators in pure Cadl in the future this is a step towards it.
I however did think it would still be valuable to have a way to define that decorator in pure JS, it would just not be very clean looking. Something maybe like this:
setSignature($doc, target: "Any", [{name: "doc", kind: "String"}]);
export function $doc(context, target, doc) {

}

@timotheeguerin Yes, this is exactly what I was thinking.
With the current state, the compiler (and therefore the language server) has a hard dependency on JavaScript, as JS files can be imported into Cadl.  Using extern could offer a way out of that hard dependency (a future breaking change), but it seems like that should be part of a separate strategy not directly related to improving decorator support.
To that point, I think extern could be advantageous in scenarios where the source Cadl files have no a priori knowledge of the implementations providing the symbols, instead having those libraries passed in compiler flags (essentially, a linking phase).


fix(communicationmapping): ClientLN handling for LNs reside in AccessPoint

Closes #172

Closes #172

I don't think this really closes #172 . Which ticket does this close instead?


fix bug spec._suite._failures not defined

Currently there is a bug when running the Junit reporter with Phantomjs and Gulp.
/vagrant/node_modules/jasmine-reporters/src/junit_reporter.js:274
            if (isFailed(spec)) { spec._suite._failures += spec.failedExpectations.length; }
                                             ^

TypeError: Cannot read property '_failures' of undefined

The cause is that _suite would be missing on getSpec(spec).
A simple redefine spec._suite to currentSuite would fix this error.
and generate the Xml like intended.

Are there any other interesting aspects of your test environment or the specs you are running when you encounter this problem (e.g. xit / xdescribe or fit / fdescribe, etc.) or does it happen every time you encounter a failing test?
I'm slightly concerned by this change because it seems to indicate specDone is being called without specStarted having been called first—are they being called out of order, or is specStarted just never being called? Is there a condition that causes specDone to be called without ever starting a spec? Etc.
I'd just like to understand what is causing this behavior before applying a change that should be unnecessary under normal operation (due to the fact that this exact code happens in the specStarted callback).

i made a project where its was going wrong here: https://github.com/edgehero/jasmine-testcase

Will this PR be merged eventually?

Hopefully so, but to be honest it is low on my priority list (personally, not for the project itself). I'm not comfortable merging until I understand the answers to the questions mused about above, and I haven't gotten around to investigating the particulars yet. If there's something else going on that can be targeted as a more accurate fix, it may be preferable to pursue a different avenue instead.
If you feel up to some sleuthing—discovering the answers to the questions in my last comment by reproducing with the provided testcase, tracing through what is actually happening, etc.—it may lead to this PR being merged sooner.


portainer pull mirror prompt information does not match the problem

When pulling the mysql image from the portainer web interface, the message "Image successfully pulled mysql" is displayed, but in fact the image is not pulled successfully, and when pulling from the terminal using the command line (docker pull mysql) is also unsuccessful, it will report "no matching manifest for linux/arm64/v8 in the manifest list entries" message
The reason for the problem: the image exists on dockerhub, but it does not support the aarch64 architecture, so the pull fails
Expectation: The error message "Mirror pulling unsuccessful" will be reported when the image is pulled unsuccessfully, in line with the terminal
Error portainer version: 2.0.1
Bug recurrence architecture: aarch64 (arm64)

This will involve the modification of the source code, I hope the big brothers can provide a modification plan or submit a patch to solve the problem, thank you!


JavaScript CS Intro course 3

Marking as draft pull request due to .travis.yml changes needed to build on my fork. Probably will remove that before merging? See https://github.com/Microsoft/pxt-arcade/issues/747

Adds CS Intro course 3
Minor fixes in course 1 and 2

Notes

Travis build time is getting a bit long, approximately 14 minutes with this PR
(Most) sections have a {section}-problems file, which is linked from the section and includes a handful of extra problems for teachers / students to choose from
Lots of gifs coming soon

Imo , let’s merge this (without Travis change) and keep iterating.

Sounds good
Here's the passing travis build for the most recent commit prior to the revert: https://travis-ci.org/jwunderl/pxt-arcade/builds/496240769


Not Initializing Hub Correctly on Ubuntu

I am launching grid with below configuration:
What is the default Role of this computer? (1 - node | 2 - hub | 3 - hub & node)
Default Value: 1
3
'3' was set as your value
What is the HOST for the Selenium Grid Hub?
Default Value: <IP_ADDRESS>
'<IP_ADDRESS>' was set as your value
What is the PORT for the Selenium Grid Hub?
Default Value: 4444
8080
'8080' was set as your value
What is node Platform? (WINDOWS|XP|VISTA|WIN8|WIN8_1|WIN10|MAC|LINUX|UNIX|ANDROID)
Default Value: LINUX
'LINUX' was set as your value
Will this node run 'Firefox' (1-yes/0-no)
Default Value: 0
1
'1' was set as your value
What version of 'Firefox' is installed?
Default Value:
47
'47' was set as your value
Will this node run 'InternetExplorer' (1-yes/0-no)
Default Value: 0
0
'0' was set as your value
Will this node run 'Edge' (1-yes/0-no)
Default Value: 0
0
'0' was set as your value
Will this node run 'Chrome' (1-yes/0-no)
Default Value: 0
1
'1' was set as your value
What version of 'Chrome' is installed?
Default Value:
51
'51' was set as your value
Will this node run 'Safari' (1-yes/0-no)
Default Value: 0
0
'0' was set as your value
Will this node run 'PhantomJs' (1-yes/0-no)
Default Value: 0
0
'0' was set as your value
Would you like this Node to auto update browser versions? (1-yes/0-no)
Default Value: 0
1
'1' was set as your value
Will this node run 'Appium' (1-yes/0-no)
Default Value: 0
0
'0' was set as your value
Maximum days to keep log file
Default Value: 10
'10' was set as your value
Would you like WebDriver, IEDriver and ChromeDriver to auto update (1-yes/0-no)
Default Value: 1
1
'1' was set as your value
Current Selenium Driver Version: 2.53.1
Current IE Driver Version: null
Current Chrome Driver Version: 2.22
Current Chrome Driver Bit: 32
Should this Node record test runs? (1-yes/0-no)
Default Value: 1
1
'1' was set as your value
How many videos should node keep in threads?
Default Value: 40
'40' was set as your value
Thank you, your answers were recorded to 'selenium_grid_extras_config.json'
But At Last the message displayed is:
Selenium Grid Extras has been started!
Navigate to http://null:3000 for more details
Note: Tried the same configuration with windows and it is working fine.
For ubuntu it always showing null as IP for any Role(Hub, Node, HUb and Node).
Showing null instead of IP of HUB.

What version of Ubuntu ? Also can you post the selenium grid extras config file and the hub and node config files ?

Hi Shawn,
I am using xubuntu 14.04 LTS distribution. Unfortunately I
can't send you the config files as it deleted.
Regards,
Saurabh Shukla
On 7 Jul 2016 6:30 p.m., "Shawn McCarthy"<EMAIL_ADDRESS>wrote:

What version of Ubuntu ? Also can you post the selenium grid extras config
file and the hub and node config files ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/groupon/Selenium-Grid-Extras/issues/242#issuecomment-231070156,
or mute the thread
https://github.com/notifications/unsubscribe/AEaAfXqk3WvSpmkV2hTwsejj_cqkvTBZks5qTPhQgaJpZM4JGzAk
.

@saurabh8346 version of grid extras ?

Latest one which is with the tag(non windows fixes).
On 7 Jul 2016 7:45 p.m., "Shawn McCarthy"<EMAIL_ADDRESS>wrote:

@saurabh8346 https://github.com/saurabh8346 version of grid extras ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/groupon/Selenium-Grid-Extras/issues/242#issuecomment-231090320,
or mute the thread
https://github.com/notifications/unsubscribe/AEaAff_TU-4AaQFKvH_m7B6N1vArrraOks5qTQnogaJpZM4JGzAk
.

@saurabh8346  Ok thanks. I had an issue with my XUbuntu install, and haven't had time to fix it. Btw, there was a new release yesterday 1.12.3 (one newer than the one you have). This probably won't fix your issue, but maybe its worth a shot.

Thanks Shawn,
Let me try this version.
On Fri, Jul 15, 2016 at 10:40 PM, Shawn McCarthy<EMAIL_ADDRESS>wrote:

@saurabh8346 https://github.com/saurabh8346 Ok thanks. I had an issue
with my XUbuntu install, and haven't had time to fix it. Btw, there was a
new release yesterday 1.12.3 (one newer than the one you have). This
probably won't fix your issue, but maybe its worth a shot.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/groupon/Selenium-Grid-Extras/issues/242#issuecomment-233010635,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEaAfZKxp9dT3IlsIP2Em7nIXajdVJH6ks5qV77_gaJpZM4JGzAk
.

--
Thanks & Regards
Saurabh Shukla

Hi Shawn,
I have tried 1.12.3(Newer version as suggested), but unfortunately it doesn't solved the problem.
Thanks
Saurabh

@saurabh8346 Ok, something does seem off. I get this :
Navigate to http://<IP_ADDRESS>:3000 for more details
Notice its not <IP_ADDRESS>
Is yours a VM?

I see same issue with my Ubuntu machine when configuring as node. Configuring as hub worked fine.

Here are the configs -
selenium_grid_extras_config.json
{
"theConfigMap": {
"auto_update_browser_versions": "1",
"hub_config_files": [],
"auto_start_hub": "0",
"iedriver": {
"version": "3.3.0"
},
"default_role": "node",
"unregisterNodeDuringReboot": "true",
"chromedriver": {
"bit": "64",
"version": "2.28"
},
"auto_update_drivers": "1",
"video_recording_options": {
"videos_to_keep": "40"
},
"auto_start_node": "1",
"hub_config": {},
"geckodriver": {
"version": "0.15.0"
},
"log_maximum_age_ms": 8.64E8,
"reboot_after_sessions": "10",
"grid_extras_port": "3000",
"webdriver": {
"version": "3.3.1"
},
"node_config_files": [
"node_5555.json"
]
}
}
selenium-node-config.json
{
"capabilities":
[
{
"browserName": "firefox",
"maxInstances": 10,
"seleniumProtocol": "WebDriver"
},
{
"browserName": "chrome",
"maxInstances": 10,
"seleniumProtocol": "WebDriver"
}
],
"proxy": "org.openqa.grid.selenium.proxy.DefaultRemoteProxy",
"maxSession": 10,
"port": 5555,
"register": true,
"registerCycle": 5000,
"hub": "http://:4444/grid/register",
"nodeStatusCheckTimeout": 5000,
"nodePolling": 5000,
"role": "node",
"unregisterIfStillDownAfter": 60000,
"downPollingLimit": 2,
"debug": false,
"servlets" : [],
"withoutServlets": [],
"custom": {}
}
selenium-hub-config.json
{
"port": 4444,
"newSessionWaitTimeout": -1,
"servlets" : [],
"withoutServlets": [],
"custom": {},
"capabilityMatcher": "org.openqa.grid.internal.utils.DefaultCapabilityMatcher",
"throwOnCapabilityNotPresent": true,
"cleanUpCycle": 5000,
"role": "hub",
"debug": false,
"browserTimeout": 60,
"timeout": 1800
}

I figured out what my problem was. The hostname was not mapped to ip address properly. I just had to run this once
Try this if you see this kind of warnings on your linux machine - sudo: unable to resolve host ip-XXXXXXXXXX
sudo sed -i /etc/hosts -e "s/^<IP_ADDRESS> localhost$/<IP_ADDRESS> localhost $(hostname)/"


Code autocompletion stop working after specify SDK

Describe the bug
As long as I specify the SDK to iOS in settings or use "Select target platform" to select iOS, then code completion is stop working. Seems currently only MacOS SDK is working for me....
To Reproduce
Steps to reproduce the behavior:

create a swift package by using xcode. And then create a simple swiftui view:

// Sources/MyLibrary/MyLibrary.swift

import SwiftUI

public struct MyLibraryView: View {
  public init() {}  // Add an initializer if needed

  public var body: some View {
    VStack {
      Text("Hello, iOS!")
        .frame(width: 100, height: 100, alignment: .center)
    }
  }
}

specify the sdk path to simulator sdk or use "Select target platform" to select iOS
All the code completion is stop working
I am not seeing any errors in output

Expected behavior
The code completion should always working not matter what sdk are using.
Environment

OS: macOS Sonoma version 14.4.1 (I am using m2 macbook pro laptop)
Swift version (output of swift --version)
swift-driver version: <IP_ADDRESS> Apple Swift version 5.10 (swiftlang-<IP_ADDRESS> clang-15<IP_ADDRESS>)
Target: arm64-apple-macosx14.0
Visual Studio Code version: Version: 1.89.1
vscode-swift version: 1.9.0

Additional context
NA

Synced to Apple’s issue tracker as rdar://132484681

VS Code adds the following parameters to sourcekit-lsp when launching it
-Xswiftc -sdk -Xswiftc /Applications/RainbowE.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS17.4.sdk -Xswiftc -target -Xswiftc arm64-apple-ios17.4

This generates build settings like the following
…
-sdk /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.4.sdk
-F /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Frameworks
-I /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/usr/lib
-L /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/usr/lib
-g
-sdk /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS17.4.sdk
-target arm64-apple-ios17.4
-Xcc
-isysroot
-Xcc /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.4.sdk
-Xcc
-F
-Xcc /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Frameworks
-Xcc
-fPIC
-Xcc
-g

Setting aside that the compiler arguments still contain the macOS SDK, which will get overwritten, it is missing -F, -I, -L, -Xcc -isysroot, and -Xcc -F` search paths into the iOS SDK.
The proper solution here is that VS Code shouldn’t pass additional command line options to SourceKit-LSP and instead SourceKit-LSP needs some way of configuring the iOS SDK to be used.

Hello, is there any updates for the issue? Thanks.

The VSCode extension's "Select Target Platform" is somewhat hacky at the moment — I'm thinking of making a PR to have it initialize SourceKit-LSP the right way instead. Try resetting the VSCode SDK setting and saving the following file as .sourcekit-lsp/config.json (see also: Configuration File docs):
{
    "swiftPM": {
        "triple": "arm64-apple-ios",
        "swiftCompilerFlags": [
            "-sdk",
            "/var/db/xcode_select_link/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk"
        ],
        "cCompilerFlags": [
            "-isysroot",
            "/var/db/xcode_select_link/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk"
        ]
    }
}

This should be able to handle most iOS packages. Further the need for {swift,c}CompilerFlags would go away if we landed https://github.com/swiftlang/swift-package-manager/pull/6828 (and potentially made some changes in this repo too) but this should do the trick for now.

I think GitHub was a bit trigger-happy about automatically closing this issue after #1643 landed — we'd actually also need https://github.com/swiftlang/swift-package-manager/pull/6828 in order to avoid the explicit compiler flag settings. That said this can be considered resolved if setting the compiler flags is okay.

saving the following file as .sourcekit-lsp/config.json
I've been poking around this config file for a while, but your suggestion finally made it work for me in Zed, thanks a lot!


Incorrect date on episode 609

Description
As part of this pull request #1667 I noticed what might be an incorrect date on episode 609 as it doesn't align with the date published on Spotify (May). You can see this highlighted and demonstrated in the screenshot.
Screenshot

thanks! fixed https://github.com/syntaxfm/website/pull/1716


fix: suppression insee et recherche entreprise nom commercial

Correction d'un bug
Zones impactées : ./models/core/unite-legal.ts.
Détails :

Nettoyage à la volée de la mention "suppression du nom commercial"

closes #1228

The fix is now at the client level.
Is it the correct approach ?
I thought maybe you were referring to an empty field ?

I fixed the ‘recherche entreprise’ result, but this might be redundant with the upcoming fix from Hajar.

In the example I was using, only “enseigne1Etablissement” was affected, but in case the others can be affected as well, I applied the format function to all three.


Update README w/ install instructions for v2.0

I see the release notes for v2.0 mention that the new direction is to release binaries (including bundled linters).
What’s not clear to me is how this change impacts the recommended way to install gometalinter.  Is go get going to be deprecated?  Should we just download the binaries and place them on our $PATH?  Does the linters directory also need to be in the path or is gometalinter smart enough to look there for tools to exec?
It would be nice if we could update the install and quick start sections of the README to reflect the latest recommendations.

Yes, good call.

Please post the new instructions? Also, would you be able to include how to install this using Gradle? I'm using Gradle for build process using following gogradle plugin.
https://github.com/gogradle/gogradle
I'd like to include gometalinter into the overall build process. But, not sure how to set it up. In our CI/CD process, I won't have access to "install" this on the build machines. Even golang is being setup by the build process using gogradle in a temporary location.

@amimas I can't provide instructions on how to install gometalinter with every CI, that is impractical.

Definitely agree that it's impractical to provide instructions for every CI. I mentioned about Gradle because that's a very robust build tool than Ant or Maven. It's not necessarily CI.
Maybe I'll be able to figure out how to use it with Gradle once the updated instructions for v2 is available. Thanks

Hopefully this is helpful, https://github.com/goreleaser/godownloader
Also, IIRC, goreleaser makes it easy to make and automatically update a homebrew tap repository, if interested.  That way folks can use homebrew to automatically install and keep things up-to-date easily.

I did look at goreleaser but had some issues with environment variables. I have subsequently made it work, so I'll switch to that soon.
godownloader looks interesting, but doesn't support multiple binaries :(

https://github.com/goreleaser/goreleaser/issues/540#issuecomment-362870152

That's very sick. So now it's recommended to use precompiled binaries BUT there's no generic instructions for installation and usage.
And how we are supposed to use it? Go tooling was always easy to use as "copy-paste & go" and now metalinter became opposite of that.

@gudvinr The old way still works fine, but thanks for your constructive input.

@alecthomas Thanks for the reply.
Yes, it definetely works fine for now but since this is deprecated way to install I guess it will be eliminated in future. So people think that newer way should be used whenever possible.
I'm sorry that my response sounds rude a bit. But to be honest it's really annoying that one should digging into setup process of tools that supposed to make development process easier.

There will be instructions added once there's an automated solution. Until then you can continue to use the instructions in the README.

for those who might want a godownloader script - i used the generator and then hacked it. which i realize is bad practice, but yeah.
https://github.com/flyinprogrammer/godownloaders/blob/master/download_gometalinter.sh#L52-L58

The simplest hack, if you need one:
curl -sLo- https://github.com/alecthomas/gometalinter/releases/download/v2.0.5/gometalinter-2.0.5-linux-amd64.tar.gz|tar -xzC "$GOPATH/bin" --exclude COPYING --exclude README.md --strip-components 1 -f-

@alecthomas

godownloader looks interesting, but doesn't support multiple binaries :(

It does now. See the discussion in https://github.com/goreleaser/godownloader/issues/52

@autarch That's awesome, though it looks like there are still a couple of kinks. Once those are fixed I'll make a downloader available. Thanks for creating that issue BTW.

Is there a way to always download the latest release of the binary package? Due to the version encoding in the file name I wouldn't know how.

goreleaser/godownloader now both support multiple binaries. I've added the script. Please test with:
$ export BINDIR=<directory-in-your-$PATH>
$ curl https://raw.githubusercontent.com/alecthomas/gometalinter/master/scripts/install.sh | bash


Invalid height for animated gif files

Possible bug
Is this a possible bug in a feature of sharp, unrelated to installation?

[x] Running npm install sharp completes without error.
[x] Running node -e "require('sharp')" completes without error.

Are you using the latest version of sharp?

[x] I am using the latest version of sharp as reported by npm view sharp dist-tags.latest.

What is the output of running npx envinfo --binaries --system --npmPackages=sharp --npmGlobalPackages=sharp?
  System:
    OS: Windows 10 10.0.22000
    CPU: (12) x64 Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz
    Memory: 876.36 MB / 15.84 GB
  Binaries:
    Node: 16.18.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.11 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 8.19.2 - ~\AppData\Roaming\npm\npm.CMD

What are the steps to reproduce?
const img = sharp('./sample.gif', { pages: -1 });
const { height } = await img.metadata();

console.log(height);

What is the expected behaviour?
Should return correct height.
Please provide a minimal, standalone code sample, without other dependencies, that demonstrates this problem
Visit https://codesandbox.io/p/sandbox/adoring-euclid-cuc041?file=%2Findex.js
Run yarn start
Please provide sample image(s) that help explain this problem

GIF used for reference:

height is the total height of all pages/frames. Multi-page/animated images provide pageHeight, which might be what you need.

Ah got it, thanks!


pyup_dirs crashes with an ImportError

Description
Running pyup_dirs crashes with the latest pyupgrade (2.9.0) version.
Using a fresh install of pyupgrade and pyupgrade-directories, the tool doesn't even start and crashes because of an ImportError
Steps to Reproduce
$ virtualenv python=python3.6 /tmp/venv
$ source /tmp/venv/bin/activate
$ pip install pyupgrade-directories
[snip]
$ pyup_dirs
Traceback (most recent call last):
  File "/tmp/venv/bin/pyup_dirs", line 5, in <module>
    from pyupgrade_directories.__main__ import main
  File "/tmp/venv/lib/python3.6/site-packages/pyupgrade_directories/__main__.py", line 21, in <module>
    from pyupgrade import _fix_file  # type: ignore
ImportError: cannot import name '_fix_file'

Expected result:
The application checks my source files.
Reproduces how often:
All the time.
Version

Operating System: Linux (Ubuntu)
Python: Tested with Python 3.6, 3.7. Doesn't looks like it's related to the python version
pyupgrade-directories: 0.0.3
Important note: I've tested with downgraded versions of pyupgrade ; it looks like the latest "working" version is the 2.7.4, so it means that the ImportError happens with versions 2.8.0 & 2.9.0 of pyupgrade

Seems pyupgrade-directories needs to be adopted to the latest pyupgrade library and make a new release 0.0.4 with supporting <2.8 and 0.0.5 adopted to the latest pyupgrade version.

I see 0.1.0 version is almost ready with fix and import checks. @domdfcoding can you please make a release and upload to pypi?

Hi @brunobord and @aleksandr-kotlyar .
Terribly sorry, I completely forgot about this. I have made a new release (v0.1.1) which sets the maximum version of pyupgrade to 2.7.4 and so will run correctly. I am working on supporting newer pyupgrade versions right now.

I have made a new release (v0.1.1) which sets the maximum version of pyupgrade to 2.7.4 and so will run correctly.

@domdfcoding thank you very much! I have tested reinstallation of pyupgrade-directories on the top lvl pyupgrade, and it works fine - reinstalling newer pyupgrade to the 2.7.4.

I am working on supporting newer pyupgrade versions right now.

Cool! If will need you any help just dive us into the details through issues.

looks like it's solved, yes! Thank you very much!