Add new paper in application, active attack and defence in Split Learning

Type of change

[x] Add new papers (Please tell us why you think this paper is awesome!)
[ ] Fix the category of an existing paper/papers (Please tell us the reasons)
[ ] Add a new tool/primitive/application with a new markdown page (Thank you! Also, please tell us more about this awesome thing!)

Description
Add a CCS2021 paper: Unleashing the Tiger: Inference Attacks on Split Learning. This paper exposes novel vulnerabilities of the protocol and demonstrate its inherent insecurity by introducing general attack strategies targeting the reconstruction of clients' private training sets. More prominently, it shows that a malicious server can actively hijack the learning process of the distributed model and bring it into an insecure state that enables inference attacks on clients' data.
We have also developed a passive detection method to detect this kind of active attacks by monitoring the intermedia exchanging parameters.
I have read the CLA Document and I hereby sign the CLA

I have read the CLA Document and I hereby sign the CLA

I have read the CLA Document and I hereby sign the CLA


9384 DEV Update master_integrations.sql to add migration script for adding kubernetesConfig masterIntegration

https://github.com/Shippable/pm/issues/9384

This is complete.
Closing.


Proposal: Help search engines find latest version of a crate

Motivation and Summary
When someone uses a web search engine to find a crate’s documentation, they are likely to wind up on the documentation for a random older version of that crate. This can be confusing and frustrating if they are working on a project that depends on a more recent version of that crate. As an example: in April 2021, a Google search for [rustls serversession] links to version 0.5.5 of that crate, released Feb 2017. A Google search for [rustls clientsession] links to version 0.11.0, released Jan 2019. The latest version is 0.19.0, released Nov 2020.
To fix this, I propose that doc.rs’s URL structure should be more like crates.io: Each crate should have an unversioned URL (docs.rs/rustls/latest) that always shows the docs for the latest version of that crate. There would continue to be versioned URLs like today (https://docs.rs/rustls/0.19.0/rustls/), accessible as defined below. I believe this will, over time, lead search engines to more often find the unversioned URL.
This is a popular request:
https://github.com/rust-lang/docs.rs/issues/1006
https://github.com/rust-lang/docs.rs/issues/854
https://github.com/rust-lang/docs.rs/issues/74
https://github.com/rust-lang/docs.rs/issues/1411

It's also a problem that disproportionately affects new users of the language who haven't gotten in the habit of looking for the "go to latest version" link. I know when I was first learning Rust, this problem was a particular headache for me.
Non-working solutions
<link rel=canonical> is a commonly proposed solution, but it’s not the right fit:

The target (canonical) IRI MUST identify content that is either
duplicative or a superset of the content at the context (referring)
IRI.

Since documentation of different versions is not duplicative, this won’t work. And in fact search engines verify the property, and will disregard canonical links on a site if it does not hold.
Here are some links about Google’s handling of canonical:
https://developers.google.com/search/docs/advanced/guidelines/duplicate-content
https://developers.google.com/search/docs/advanced/crawling/consolidate-duplicate-urls
Proposed Solution
For any given crate, https://docs.rs/<crate>/latest should exist and not be a redirect. It should serve the latest version of that crate. Crates.io should be updated so that the unversioned URL for a crate (e.g. https://crates.io/crates/ureq) links to the unversioned URL on docs.rs.
Sometimes people will want to link to a specific version of the documentation rather than the generic “latest” URL. There will be two ways to do that:

You can navigate explicitly to the versioned URL, using the version selector tools already available in docs.rs.
Additionally, we should follow GitHub’s UI for when you click on a line number in a source file. When you click on an anchor within a doc page, a little “...” should appear with options to either copy the line or copy a permalink. We may even want to mimic the keystroke to go to a permalink for a page (y).

Caching issues
Currently, only static files are cached. The things that change between versions of a crate are its HTML and some JS (containing JSON data used in displaying the pages). The HTML is currently not cached at all, so invalidating its cache is not a current concern. The JS is also not cached, but it has a unique URL per crate version so easily could be cached.
In case we later decide to start caching the HTML: The CloudFront rates for cache invalidation are reasonable: $0.005 per invalidation request, and purging a whole subdirectory (like /crates/<crate>/*) is considered a single invalidation request.
Will it work?
I’m pretty sure it will work. Search engines these days take navigation events heavily into account, so if most navigation events go to an unversioned URL, that will help a lot. Also, once we make this change, the unversioned URLs will start accumulating “link juice,” which will also help a lot.
One good demonstration that it will work is that crates.io already follows a scheme like this, and does not have the "links go to old versions" problem at all.

The only reservation I have is the URL scheme: I'd prefer to have /<crate>/latest instead of /crates/<crate>, as it's consistent with what we have today and doesn't break the workflow of just typing docs.rs/crate-name in the URL bar. Otherwise I'm all for it!

Ah, yep, that URL scheme does make more sense for those reasons.

Hi @jsha , thanks for doing and pushing this!
I general I only have superficial knowledge of SEO / search engines, so really cannot judge on the best approach to optimize search results.
Still some thoughts:

perhaps I'm missing something, but why don't we just index the latest version, and set rel=nofollow for older versions? Of course we could do this later if link juice alone doesn't help. Also, where would link juice come from if the results don't appear high enough in the search results?
due to CSP we cannot cache the HTML anyway, so nothing we have to think about right now. But in general you're right, it's only about active invalidation at the right points. ( I have some ideas to solve this, but that would involve some more changes)
where should our sitemap point to? Base-URL or /latest/?

from @pietroalbini:

I have no problem with giving them access to the webmaster console, but we should do it by having the infrastructure team setup the account and then granting jsha access to it, rather than having jsha setup their own account linked to docs.rs. I'll add that to my todo list.

Done.

Thanks! Here's our coverage report: 1.26M valid URLs, 3.28M excluded. The top reasons are "Crawled - currently not indexed" and "Duplicate without user-selected canonical." Details on those reasons here: https://support.google.com/webmasters/answer/7440203#duplicate_page_without_canonical_tag

Drilling down, here is a sample of "Crawled - currently not indexed" URLs:

And "Duplicate without user-selected canonical":

We can drill down into individual URLs:

What I conclude from this first look is that we probably do need to implement rel="canonical". In its absence, Google is selecting a canonical page for us, and often getting it wrong, thus excluding the page we would like to have indexed. I'll make a proposal on #74.

What I conclude from this first look is that we probably do need to implement rel="canonical". In its absence, Google is selecting a canonical page for us, and often getting it wrong, thus excluding the page we would like to have indexed. I'll make a proposal on https://github.com/rust-lang/docs.rs/issues/74.

A couple things that might be worth trying prior to the sledgehammers of rel=canonical or noindex:

You could include every https://docs.rs/:crate/latest/:crate/** url in the sitemap.xml, not just the crate root. I would expect that to guide Google to the right canonical URL more often, though it increases the size and complexity of the sitemap.

Setting the HTTP Last-Modified header on pages. This is currently passed for crate roots via the sitemap (from some brief googling, outdated crate roots seem to be less of a problem?). But for everything else Google might well be inferring it, potentially wrongly?

Marking all links to specific versions (e.g. the dependencies and versions in the crate overview dropdown, links in doc comments or due to re-exporting) as rel=nofollow. This is just a hint that might minimise "passing along ranking credit to another page", but perhaps worth a shot.

Thank you for the ideas!
I don't know enough about google indexing to judge the ideas, but I have one remark about :

You could include every https://docs.rs/:crate/latest/:crate/** url in the sitemap.xml, not just the crate root. I would expect that to guide Google to the right canonical URL more often, though it increases the size and complexity of the sitemap.

This would definitely increase the sitemap's size quite much, we have crates with > 1 Mio files ( which are probably quite many pages to be added to the sitemap).

Marking all links to specific versions (e.g. the dependencies and versions in the crate overview dropdown, links in doc comments or due to re-exporting) as rel=nofollow. This is just a hint that might minimise "passing along ranking credit to another page", but perhaps worth a shot.

I remember talking to @jyn514 about this. Only concern I would see is someone searching for an element which only exists in an old version of the library.

This would definitely increase the sitemap's size quite much, we have
crates with > 1 Mio files ( which are probably quite many pages to be added
to the sitemap).

We could limit the links per crate to reduce this problem.
Another problem is that sitemaps are limited to 50k URLs. We have a sitemap
index linking to various sitemaps, but that can only be nested one deep.
Still, I like this idea. A related one: link to the crate root and
all.html from the sitemap.

Marking all links to specific versions (e.g. the dependencies and
versions in the crate overview dropdown, links in doc comments or due to
re-exporting) as rel=nofollow. This is just a hint that might minimise "passing
along ranking credit to another page"
https://developers.google.com/search/blog/2019/09/evolving-nofollow-new-ways-to-identify,
but perhaps worth a shot.

I remember talking to @jyn514 https://github.com/jyn514 about this.
Only concern I would see is someone searching for an element which only
exists in an old version of the library.

Fwiw, our current canonicalization plan has this problem too. I suspect we
can solve it with some semver awareness, but first I'd like to see it
working to improve search.
I like the idea of nofollow in the dependencies links. That could reduce
unnecessary crawling too.
By the way, pkg.go.dev and docs.python.org use canonicalization to latest
version.

I frankly don't remember anything about this problem 😅 happy to go with whatever you decide on.

I like the idea of nofollow in the dependencies links. That could reduce unnecessary crawling too.

@jsha @alecmocatta was also talking about setting old versions to nofollow, not only the dependencies.
With a hint which way helps I'm happy to help too. Which links shouldn't be followed?
If we fully exclude old versions that's probably a different discussion since we would completely exclude them from the index.

This would definitely increase the sitemap's size quite much, we have crates with > 1 Mio files ( which are probably quite many pages to be added to the sitemap).
We could limit the links per crate to reduce this problem. Another problem is that sitemaps are limited to 50k URLs. We have a sitemap index linking to various sitemaps, but that can only be nested one deep. Still, I like this idea. A related one: link to the crate root and all.html from the sitemap.

Thinking longer about this, this is a tough nut to crack. We don't have the generated docs in the database but only on S3. So generating the pages for a crate would involve an additional request to S3 for each crate.
I have some ideas how to solve this, but it's only worth the effort as a last option, if I'm not missing something.

I like the idea of nofollow in the dependencies links. That could reduce unnecessary crawling too.

@jsha @alecmocatta was also talking about setting old versions to nofollow, not only the dependencies.
With a hint which way helps I'm happy to help too. Which links shouldn't be followed?
If we fully exclude old versions that's probably a different discussion since we would completely exclude them from the index.

This would definitely increase the sitemap's size quite much, we have crates with > 1 Mio files ( which are probably quite many pages to be added to the sitemap).
We could limit the links per crate to reduce this problem. Another problem is that sitemaps are limited to 50k URLs. We have a sitemap index linking to various sitemaps, but that can only be nested one deep. Still, I like this idea. A related one: link to the crate root and all.html from the sitemap.

Thinking longer about this, this is a tough nut to crack. We don't have the generated docs in the database but only on S3. So generating the pages for a crate would involve an additional request to S3 for each crate.
I have some ideas how to solve this, but it's only worth the effort as a last option, if I'm not missing something.

@jsha @alecmocatta was also talking about setting old versions to nofollow, not only the dependencies.

Thanks for clarifying. I think it makes sense to nofollow links to the old versions too, since #1773 means a search engine would crawl those, only to wind up canonicalizing them. So those are just wasted fetches.

Thinking longer about this, this is a tough nut to crack. We don't have the generated docs in the database but only on S3. So generating the pages for a crate would involve an additional request to S3 for each crate.
I have some ideas how to solve this, but it's only worth the effort as a last option, if I'm not missing something.

Yep, I agree it's not that necessary. Particularly given we have all.html available if we want to help search engines consistently discover all items in each crate. Presumably for an all.html with 1M links, a search engine would disregard links beyond some cutoff.

Thinking longer about this, this is a tough nut to crack. We don't have the generated docs in the database but only on S3. So generating the pages for a crate would involve an additional request to S3 for each crate.
I have some ideas how to solve this, but it's only worth the effort as a last option, if I'm not missing something.

Maybe just add all and the modules, structs and re-exports in the crate root (like bevy::prelude, bevy::app, ...)

Thinking longer about this, this is a tough nut to crack. We don't have the generated docs in the database but only on S3. So generating the pages for a crate would involve an additional request to S3 for each crate.
I have some ideas how to solve this, but it's only worth the effort as a last option, if I'm not missing something.

Maybe just add all and the modules, structs and re-exports in the crate root (like bevy::prelude, bevy::app, ...)

Good idea in general, but in that regard docs.rs is "only" serving static files from rustdoc, so has no detailed knowledge about the documentation files apart from some exceptions (#1781). We have the list of source-files for our source-browser with which we could generate the module list, but this would tightly bind docs.rs to rustdoc implementation details  (its file structure).
So similar effort, so only when it's worth it :)

Update:
Checking the latest data from the Google Search Console, it is still finding many pages that are "duplicate without user-selected canonical", but spot-checking them, they are all crates that have a separate documentation URL and so are not getting the <link rel="canonical"> treatment.
The Search Console allows exporting a report of click-through data, and it turns out to be an interesting way to find examples of URLs with this problem: the pages that have the highest click-through rates tend to be ones that have the "versioned URL" problem. For instance https://docs.rs/rand/0.6.5/rand/fn.thread_rng.html is the page with the single highest click-through rate on docs.rs, presumably because people search for thread_rng or rust thread_rng and it is the top result. Unfortunately, 0.6.5 is out of date: 0.8.5 is the latest version. The same pattern holds for all of the top pages by click-through rate.
I followed the thread_rng example further, and in the Search Console "inspected" the URL. It turns out https://docs.rs/rand/0.6.5/rand/fn.thread_rng.html is considered canonical - it doesn't have a <link rel="canonical">. That surprised me because https://docs.rs/rand/latest/rand/fn.thread_rng.html does have <link rel="canonical"> (the crate's documentation URL is https://docs.rs/rand).
It turns out version 0.6.5 had a different documentation URL: https://rust-random.github.io/rand. Since we don't render <link rel="canonical"> on crates that have a documentation URL, version 0.6.5 has no canonical link, even though the latest version of the crate does have one.
I think we need to provide <link rel="canonical"> on old crates even when they have their own documentation URL. To make things simpler I think it makes sense to remove entirely the exclusion for crates with their own documentation URL. I think that will not make the situation any worse for crates that want their self-hosted documentation to be canonical, and there are possibilities to make the situation better. I'll post on #74 again.

Another interesting result: https://docs.rs/futures/0.1.11/futures/future/type.BoxFuture.html also has a high click-through rate, and that URL does have a <link rel="canonical">. When I "inspect" it in the Search Console, I get:

In other words, Google sees our canonical link, parses it, and chooses to ignore it in favor of considering 0.1.11 to be the canonical URL. It's not clear why that is; perhaps version 0.1.11 has more inbound links, or has a long history of being canonical. 0.3.1 is the latest version for that crate.

I think we need to provide  on old crates even when they have their own documentation URL. To make things simpler I think it makes sense to remove entirely the exclusion for crates with their own documentation URL. I think that will not make the situation any worse for crates that want their self-hosted documentation to be canonical, and there are possibilities to make the situation better. I'll post on https://github.com/rust-lang/docs.rs/issues/74 again.

That makes sense to me; we can treat the self-hosted docs as canonical for the latest version only.

@jsha coming from your last comments regarding the google check:
what do you think about closing this issue, and possibly #74 ?

I have a more recent comment; we still haven't finished a full recrawl. I'm happy to close this issue since the basic proposal is done, but if we wanted to treat it as more of a tracking issue we would keep it open since there's still additional work to do.

On Feb 3 we deployed a change adding noindex to versioned rustdoc URLs. As of today, only 7 of the top 1000 pages visited from Google Search have a version in the URL. Presumably those just haven't been recrawled yet to see the noindex directive. By contrast, as of July 2022, 305 of the top 1000 pages had a version in the URL.
Of those 305 pages, 147 of them have their /latest/ equivalent in today's top 1000. I've spot-checked some of the rest and they have various explanations. For some, it's a different between / vs /index.html at the end of the URL. For one it was a change of module name, since the crate was revised in the meantime. For many of them I think it's either ranking changes - for instance Google now prefers the module page for futures::stream over the trait page for futures::stream::Stream - or popularity changes, such that a given item is not longer a popular enough search to be in the top 1000.
I did stumble across one anomaly: [parse_macro_input], for which we used to rank #1, now points to https://rcos.io/static/internal_docs/syn/macro.parse_macro_input.html, which I assume is not the official documentation because it was generated with an old rustdoc (and has /internal_docs/) in the name. The Docs.rs page doesn't show up in the top 10. Looking at Search Console, Google is still (incorrectly) canonicalizing https://docs.rs/syn/latest/syn/macro.parse_macro_input.html to https://docs.rs/syn/1.0/syn/macro.parse_macro_input.html, which is then excluded due to the noindex directive. I assume this is a temporary inconsistency and will resolve itself in time.
I'm satisfied that this issue is solved. 🎉

Commenting here, because it seems to be relevant, and the current state seems to be worse than it should be.
Right now, Google seems to rank docs.rs quite low, and never the front page of the crate. As a quick example from my experience today:

searching for tokio-postgres:

crates.io, unversioned
next three results are not docs.rs at all
next is https://docs.rs/tokio-postgres-rustls
some other results
last on the first page is https://docs.rs/tokio-postgres/latest/tokio_postgres/config/struct.Config.html

and then: tokio_postgres

crates.io, unversioned
rust-postgres/tokio-posgres/src/lib.rs on GitHub
https://docs.rs/tokio-postgres/latest/tokio_postgres/types/index.html
a 2021 StackOverflow question about the crate
https://docs.rs/tokio-postgres/latest/tokio_postgres/struct.Client.html
more relevant results

This has been a consistent experience for me over the past month or two, and it has gotten to the point that crates.io not having a "latest version" banner is a problem for me.

Thanks for the info! I will look into this.

Some more observations:

it's only for some crates, many work just fine
adding rust  at the start for tokio-postgres (or _) searches didn't change a thing

Off the top of my mind I can name bytes and tokio-postgres as crates with the issue. Considering I worked on implementing a binary protocol for the last four weeks, that would make sense why I got the impression it was more common.
Other crates, like cidr and ipnetwork when searched for with the rust  prefix worked just fine: docs.rs, crates.io, other results.

Thanks for pointing this out, we may have an issue. Google Search Console says https://docs.rs/tokio-postgres/latest/tokio_postgres/ is not indexed because it's a "duplicate without user-selected canonical." And the Google-selected canonical URL is https://docs.rs/tokio-postgres/%5E0.7.7. But also https://docs.rs/tokio-postgres/%5E0.7.7 is not in Google's index because:

'noindex' detected in 'X-Robots-Tag' http header

In general we try to convince Google that it should only index the "latest" version of a given package. We do that by setting that X-Robots-Tag header. In theory that prevents Google from seeing lots of near-duplicate pages (different versions of the same package) and incorrectly choosing one of them as canonical.
In this case, that defense didn't work. I'm not sure yet exactly why or what the fix might be.

@jsha thanks for staying on top of this topic!
Just a thought, and I'm not sure if we never had it, or I accidentally dropped it at some point:
Shouldn't we also set link rel="canonical" in rustdoc pages to make this work? Currently I don't see it in the generated HTML.

digging deeper:

from what I read in the code, on pages like https://docs.rs/crate/rand/latest we have the canonical URL in the HTML, also we should have it in the HTTP header, which I don't see in the response. will test locally if it's perhaps filtered by cloudfront?
that being said, the rustdoc page doesn't have either, digging deeper too

Ah, I see, the canonical link added in 61bca327551b8fa1458bdab52161cc8b16340042 was replaced with noindex on the versioned pages in 27af44b360da9b3281e22574d6b6508aff7dccaf.
I feared one of the many refactors accidentally dropped the header 😅

Now I'm back to: I don't know what the solution to this is :)

Looking at Google Search console's "Duplicate without user-selected canonical" report, this affects about 109k URLs right now, very slightly up from September of this year. That's out of 1M pages indexed and 7M pages not indexed (mainly the versioned URLs, rejected by X-Robots-Tag.
The first page's worth is all URLs like this one, the latest for a given crate. They're in no particular order but here's a sample, along with their Google-selected canonical (for some of them):
https://docs.rs/googleapis-tonic-google-cloud-bigquery-datapolicies-v1/latest/googleapis_tonic_google_cloud_bigquery_datapolicies_v1/
https://docs.rs/googleapis-tonic-google-cloud-bigquery-datapolicies-v1

https://docs.rs/llist/latest/llist/
https://docs.rs/llist

https://docs.rs/aws-sdk-kinesisvideo/latest/aws_sdk_kinesisvideo/
https://docs.rs/aws-sdk-kinesisvideo

https://docs.rs/snitch-protos/latest/protos/
https://docs.rs/snitch-protos

https://docs.rs/mtag-cli/latest/mtag_cli/
https://docs.rs/mtag-cli

https://docs.rs/texture-synthesis/latest/texture_synthesis/
https://docs.rs/texture-synthesis

https://docs.rs/em7180/latest/em7180/
https://docs.rs/em7180

https://docs.rs/midenc-hir-analysis/latest/midenc_hir_analysis/
https://docs.rs/midenc-hir-analysis

https://docs.rs/fat32/latest/fat32/
https://docs.rs/fat32

https://docs.rs/vls-protocol-client/latest/vls_protocol_client/
https://docs.rs/vls-protocol-client

The pattern for these is fairly straightforward: Google seems to prefer the shorter docs.rs/<cratename> URL, which I'm guessing is linked from various places (crates.io?). And in those cases the shorter name URL is actually indexed and everything is fine.
The tokio-postgres example is different because https://docs.rs/tokio-postgres/%5E0.7.7 (aka /^0.7.7) is not indexed (and shouldn't be, because it's blocked by X-Robots-Tag. But how does it get chosen as the canonical?
I don't know if this would fix anything, but I'd love to use robots.txt better. Right now Google has to fetch each URL before determining most of them are noindex. Not the most effective use of whatever crawl time they allocate to us.
It's a little challenging to write an Allow or Disallow rule that does what we want, because we want to basically Disallow: * / Allow: */latest/*, but I can't find any documentation confirming two wildcards works.
We could do something hacky like Disallow: *^, which I think would disallow all URLs that have a ^ in them. It seems like our special version-selector URL syntax does tend to be implicated in some of our weird cases.
It might be nice to have a whole separate URL space that starts with /latest/, e.g. https://docs.rs/latest/tokio-postgres. We could allow that, and disallow the rest. But I think that would be pretty disruptive. Lots of stuff links to the current /latest/ URL scheme.

Google seems to prefer the shorter docs.rs/ URL, which I'm guessing is linked from various places (crates.io?). And in those cases the shorter name URL is actually indexed and everything is fine.

perhaps because we return a 302 on that endpoint, and not 301? But if everything is fine in this case, good :)

I don't know if this would fix anything, but I'd love to use robots.txt better. Right now Google has to fetch each URL before determining most of them are noindex. Not the most effective use of whatever crawl time they allocate to us.
It's a little challenging to write an Allow or Disallow rule that does what we want, because we want to basically Disallow: * / Allow: /latest/, but I can't find any documentation confirming two wildcards works.

It would probably have to include some more pages that are static, but I get the picture.
Is there any way to test this that won't disrupt discoverability if we're wrong?

It might be nice to have a whole separate URL space that starts with /latest/, e.g. https://docs.rs/latest/tokio-postgres. We could allow that, and disallow the rest. But I think that would be pretty disruptive. Lots of stuff links to the current /latest/ URL scheme.

true

Looking again at the Search Console page for https://docs.rs/tokio-postgres/^0.7.7, I see that it has a number of referring pages:
https://docs.rs/datafusion/33.0.0/datafusion/
https://docs.rs/datafusion/36.0.0/datafusion/common/arrow/array/type.Float32BufferBuilder.html
https://docs.rs/postgres/latest/postgres/types/trait.ToSql.html
https://docs.rs/postgres/latest/postgres/transaction/struct.Transaction.html

That probably helps boost its rank, and thus its claim to be the canonical page in Google's estimation.
Looking at some of these, e.g. struct.Transacation.html, the link comes in via the menu item that links to dependencies (and it links to specific versions of those dependencies).
Since we never want search engines to index a non-latest version of docs, we also don't want them to follow these links. I think we should add rel="nofollow" to the menu item links for dependencies. What do you think @syphar?
I'd also like to try:

We could do something hacky like Disallow: *^, which I think would disallow all URLs that have a ^ in them. It seems like our special version-selector URL syntax does tend to be implicated in some of our weird cases.

Among other things, it could generate results faster (since Google only has to fetch robots.txt once, vs recrawling millions of pages to see that those links are nofollow now).

Posted #2695 for the robots.txt change.

Since we never want search engines to index a non-latest version of docs, we also don't want them to follow these links. I think we should add rel="nofollow" to the menu item links for dependencies. What do you think @syphar?
Edit: actually, if we do the robots.txt thing, we don't need to do the rel="nofollow" thing, because robots.txt would have the same effect. All internal links to dependencies use the ^ URL.

Would it be good still to do both?

It's a little challenging to write an Allow or Disallow rule that does what we want, because we want to basically Disallow: * / Allow: /latest/, but I can't find any documentation confirming two wildcards works.

perhaps the mentioned library / CLI can help validating? and writing tests?

Would it be good still to do both? [robots.txt and nofollow on hrefs]

The nofollow on hrefs adds some maintenance burden and some byte size, and blocking those URLs in robots.txt accomplishes exactly the same thing.
That said, one thing this has me thinking about is having the "Dependencies" menu link to the /latest/ versions of packages. The might help give search engines a bit of an "importance" signal by seeing which packages get lots of inbound links (because they are depended on by lots of other packages). That might help get more URLs crawled in the most important pacakges.

Would it be good still to do both? [robots.txt and nofollow on hrefs]

The nofollow on hrefs adds some maintenance burden and some byte size, and blocking those URLs in robots.txt accomplishes exactly the same thing.

👍

That said, one thing this has me thinking about is having the "Dependencies" menu link to the /latest/ versions of packages. The might help give search engines a bit of an "importance" signal by seeing which packages get lots of inbound links (because they are depended on by lots of other packages). That might help get more URLs crawled in the most important pacakges.

Wouldn't that kind of skew the meaning? I mean when I see incompatible major releases in a dependency I probably would want to be linked to the major version that the crate depends on. But since we're blocking the prefixes anyways, it won't matter right now


Create footer component (React version)

Create a Footer component that matches the default app version.

If you're looking for guidance you can check  Header.jsx here.

I'd like to take this issue on!

All yours @ceelo777 😄


Updated install requirements with libsctp

ok good

root@kali:~/SigPloit# python3 sigploit.py
Traceback (most recent call last):
File "sigploit.py", line 16, in
from ss7.tracking import *
File "/root/SigPloit/ss7/tracking.py", line 14, in
import sigploit
File "/root/SigPloit/sigploit.py", line 21, in
from gtpmain import *
File "/root/SigPloit/gtpmain.py", line 12, in
import gtp.info
File "/root/SigPloit/gtp/info.py", line 18, in
from attacks.info import discover_gtp_nodes
ModuleNotFoundError: No module named 'attacks'
can help me

Contact me<EMAIL_ADDRESS>

@odinaka1 , you know about ss7 sms intercept? Can I contact you on mail ? Thanks

eny one pls help me to fix this pls pls pls
raceback (most recent call last):
File "sigploit.py", line 16, in
from ss7.tracking import *
File "/home/linux/SigPloit/ss7/tracking.py", line 14, in
import sigploit
File "/home/linux/SigPloit/sigploit.py", line 21, in
from gtpmain import *
File "/home/linux/SigPloit/gtpmain.py", line 12, in
import gtp.info
File "/home/linux/SigPloit/gtp/info.py", line 18, in
from attacks.info import discover_gtp_nodes
File "/home/linux/SigPloit/gtp/attacks/info/discover_gtp_nodes.py", line 39, in
from gtp_v2_core.utilities.configuration_parser import parseConfigs
File "/home/linux/SigPloit/gtp/gtp_v2_core/utilities/configuration_parser.py", line 38, in
from configobj import ConfigObj, ConfigObjError
ImportError: No module named configobj

Hi all, just paid yesterday at 13:56 to ss7.dev $1000 (got all the proof), nothing happened.
No answer, sent 3-4 emails to them and nobody came back.
In case you stumble upon this website, beware IT IS A SCAM.
If you need ss7 then look elsewhere (don't know yet either).
ss7.dev - SCAM PAGE and money lost!

thanks for that. i am sry for your loss there
On Wed, 19 May 2021, 3:46 pm Pepe Fagoaga, @.***> wrote:

Closed #187 https://github.com/SigPloiter/SigPloit/pull/187.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/SigPloiter/SigPloit/pull/187#event-4764340379, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AQLZD23TRGMEAEHQQ6J6Y63TONGCPANCNFSM4J36OQXA
.


Fixed circular bean references

dev
JIRA

Main JIRA ticket

Code reviewers

[ ] @github_username

Second Level Review

[ ] @github_username

Summary of issue
ToDo
Summary of change
ToDo
Testing approach
ToDo
CHECK LIST

[ ]  СI passed
[ ]  Сode coverage >=95%
[ ]  PR is reviewed manually again (to make sure you have 100% ready code)
[ ]  All reviewers agreed to merge the PR
[ ]  I've checked new feature as logged in and logged out user if needed
[ ]  PR meets all conventions

Останній коміт "Fixed javadoc checkstyle" пов'язаний з незрозуміною помилкою при автоматизованому checkstyle


Update line endings to only "\n" for Linux

When I tried out your coding with a recent Prometheus instance (version 2.44.0 running on Debian Buster 10 Linux) I had to adjust from "\r\n" to just "\n" since otherwise the metric parsing on the Prometheus inbound side would fail.
When using it with a Prometheus on Windows then most likely "\r\n" is however required (not tested by me).
A "proper" solution might therefore be to add a new static member in the class that can be set to either "L" or "W" for Linux or Windows and then let the coding pick the corresponding line endings at runtime.

Looking at the Prometheus docs again, it seems that "\n" is always required, so probably also on Windows, but I have no matching setup to verify:
https://github.com/prometheus/docs/blob/main/content/docs/instrumenting/exposition_formats.md#text-based-format


registry: "staged" publishing

Summary
Users want to be able to create a package without special privileges - for example, in a CI/CD workflow - but do not want to allow that unprivileged identity to perform the final publish of the package without further intervention.

Intended Outcome
A user can set up a CI/CD workflow that creates a package, but the actual mechanism of its publication is still left up to a person.
How will it work?
This is a high level overview to show that there's work that we want to invest in at some point in the future.  This does not constitute a final design or specification.  Terms like "authorization mechanism", "upload" and "download" are intentionally vague so as to not suggest any type of implementation.

A user will be able to create an authorization mechanism that does not have the ability to publish packages, but does have the ability to stage packages.

This authorization mechanism can be used to upload a package.  At this point, the package is not available or visible publicly on the public registry.

A user will need to perform some manual intervention in order to make this package available publicly.

Again, this is a high-level overview.  We'll start fleshing this out more in the future.

At this time staged publishing is not a feature we are continuing to explore. We may revisit this at a future time.


Making tags page consistent with Repositories and Organizations list page (PROJQUAY-4299)

Select dropdown filter

Filtering

Tags Toolbar

Not sure if this is ready yet, but spun it up. A couple things:

Need the select all drop down and the filter drop downs

Need to remove the old select all box from the table header.

@HammerMeetNail - I was still working on it. Should have added Draft : to the PR, Sorry. This is now ready for review.


Unifying Tutorials

[ ] defined default colormaps
[ ] ensure all tutorials use default colormaps
[ ] added thumbnail selection

Thanks @cebirnie92, looks good!


0.5.0 generated xlsx file corrupted on windows/mac os x

Using:
rubyzip (1.1.7)
axlsx (2.1.0.pre)
axlsx_rails (0.5.0)
rails 4.2.5
The file can be opened on Ubuntu and it's just fine (I use 14.04). But it cannot be opened on either windows or mac.
I'm only able to provide screenshot from windows.
Snippet code in my controller to export to excel:
respond_to do |format|
  format.html
  format.xlsx {
    response.headers['Content-Disposition'] = 'attachment; filename="' + @filename + '.xlsx"'
  }
end

Snippet code my xlsx.axlsx file:
require 'axlsx'

wb = xlsx_package.workbook
wb.add_worksheet do |sheet|
  sheet.add_row ["#{@table_title}"]
  sheet.merge_cells("A1:D1")
  sheet.add_row ["Num", "Date", "Articles", "Clicks"]
  index = 1
  @article_count.reverse_each do |key, article|
    sheet.add_row [index, key, article[0], article[1]]
    index += 1
  end
  sheet.column_widths 5, nil, 10, nil
end

Is there any additional configuration that I forget to support cross platform?
Please help.

Would you try passing a name to add_worksheet to see what happens?
wb.add_worksheet(name: "Articles")

Also, downgrade to 0.4.0 and see if that changes things.

ok, will do
I will post the result after I try it
thanks for replying, by the way

Did you happen to try a named sheet with 0.5.0? If you get a chance, I would appreciate it. I've had difficulty reproducing this error.

Thanks for getting back to me by the way.

I've tried what @samuel-christian did but with no success.
I got no log errors and anything like that.
What am I missing?
Gemfile
gem 'rubyzip', '~> 1.1.0'
gem 'axlsx', '2.1.0.pre'
gem 'axlsx_rails', '0.4.0'

And here's my template:
require 'axlsx'
# encoding: UTF-8

wb = xlsx_package.workbook

wb.add_worksheet(name: "Atividades") do |sheet|
  sheet.add_row ["Carga Horária Cumprida", "Carga Horária Validada"]
  sheet.add_row [@done_workload, @validated_workload]
  sheet.add_row
  # this is the head row of your spreadsheet
  sheet.add_row ["STATUS", "JUSTIFICATIVA", "UNIDADE", "TAREFA", "DURAÇÃO(min)", "COMEÇO", "TÉRMINO", "COMEÇOU", "DISTÂNCIA(começo)", "TERMINOU", "DISTÂNCIA(término)", "RELATÓRIO"]

  # each user is a row on your spreadsheet
  @activities.each do |a|
  	if a.done?
  		sheet.add_row [Web::V1::LayoutHelper::Activity::status(a.status), a.justification_text, a.unity.name, a.task.title,
      ((a.checkpoints.last.at - a.checkpoints.first.at) / 60).to_i, I18n.l(a.beginning_at), I18n.l(a.end_at), I18n.l(a.checkpoints.first.at), (a.checkpoints.first.distant ? "DISTANTE" : "PRÓXIMO"), I18n.l(a.checkpoints.last.at), (a.checkpoints.last.distant ? "DISTANTE" : "PRÓXIMO"), Web::V1::SpreadsheetHelper::activity_report(a.report)]
  	elsif a.to_do?
  		sheet.add_row [Web::V1::LayoutHelper::Activity::status(a.status), "", a.unity.name, a.task.title, "", I18n.l(a.beginning_at), I18n.l(a.end_at), "", "", ""]
  	elsif a.canceled?
  		sheet.add_row [Web::V1::LayoutHelper::Activity::status(a.status), a.justification_text, a.unity.name, a.task.title, "", I18n.l(a.beginning_at), I18n.l(a.end_at), "", "", ""]
  	elsif a.lost?
  		sheet.add_row [Web::V1::LayoutHelper::Activity::status(a.status), a.justification_text, a.unity.name, a.task.title, "", I18n.l(a.beginning_at), I18n.l(a.end_at), "", "", ""]
  	end
  end
end

@fabioaraujo121 It is really hard to know what might cause this. It is most likely an issue between Axlsx, what you are putting in the spreadsheet (possibly special characters), and the version of office suite you are using. Here are some ideas to help track down the problem:

Make sure it isn't axlsx_rails: Create a plain ruby script that uses Axlsx to create your sheet. See if it helps.
Make sure it isn't your data: Vary your data, or make it plain vanilla, or remove sections of your sheet, until you find what is causing the problem. It could involve special characters.
Open it with other office suites to see if there are any issues.

All axlsx gems have moved into a community organization. If it appears to be an Axlsx issue consider adding an issue to http://github.com/caxlsx/caxlsx. You will probably have to create a repo of an environment that reproduces your problem for it to be solved.


Apply DI pattern to landscape core classes

Most of the core landscape classes use a static context.
TODO: Refactor such that they are injectable via DI context.

As discussed previously, this refactoring is not necessary anymore. I'm closing this since the static context is not a problem anymore (467932b27b2ac9b40d891c275f50aeb2932b6ff4).


[BUG] New and exciting linking errors with  11 and previously working code

Environment
Win 11
vcpkg based 11.0.0
Visual Studio 2022
Describe the bug
Prior compiles went fine, now I'm getting:
unresolved external symbol "public: static char const * const openvdb::v11_0::GridBase::META_GRID_CLASS"
unresolved external symbol "public: static char const * const openvdb::v11_0::GridBase::META_GRID_NAME"
Is there anything that changed from 10 to 11 for this to suddenly show up?
The only thing I'm doing is:
openvdb::tools::MultiResGridFloatGrid::TreeType mrg(levels + 1, grid;
and commenting out that line builds without any issues.
levels is an int based off voxel count defaulting to 3
grid is a floatgrid
To Reproduce
Build code that worked under 10.x
Expected behavior
A successful build as before
Additional context
Before I get a bunch of did you do this and did you do that, I posted this in the discussion area three weeks ago but never heard anything.  I was asking what changed to cause this so I CAN try to find the issue.  I want to identify and fix the issue no matter where the problem is, not argue about it.

We've not made any changes that I'm aware of to cause the issue you're seeing.
I saw your post but have not had a chance to reply. I also saw your comment in https://github.com/AcademySoftwareFoundation/openvdb/issues/773 about Utils.cc and your old issue about linking errors due to this https://github.com/AcademySoftwareFoundation/openvdb/issues/773. Note that we did not move these defines out of a TU to fix any known linking issues, they were moved because it made better sense for them to be inlined.
Taking both of these into account, and the fact that no one else has reported these issues, the problem seems to be related to your specific build setup. To remove all ambiguity, could you please confirm how you're installing VDB (vcpkg and the toolchain triplet you're using) as well as how the application you're writing that depends on OpenVDB is including/linking against it from your vcpkg installation. Any/all build logs will help with diagnosing the problem

Sorry, life happened before I could reply.
I'm installing with vcpkg triplet :x64-windows
openvdb version 11.0.0
For the build of my stuff I'm working in visual studio 2022
The includes are ..including:
#include <openvdb/openvdb.h>
#include <openvdb/grid.h>
#include <openvdb/tools/MultiResGrid.h>

Here is the log.
build.txt

I've only managed to skim that build log, but neither cl.exe or msbuild.exe seem to be being invoked. Additionally the ClCompile and CL targets seem to be being skipped and it's going straight to linking. Can you confirm that, in updating to VDB 11, you have re-generated the object files for your software? i.e - a complete full clean of the project + a rebuild (and attach such a log if that was not the case above)

Attached are two (less verbose) logs.
The "commented" one is a cleaning and build log with the line
openvdb::tools::MultiResGrid<FloatGrid::TreeType> mrg(1, grid);
Commented out
The "uncommented" one is a cleaning and build log with the line
openvdb::tools::MultiResGrid<FloatGrid::TreeType> mrg(1, grid);
NOT commented out and part of the code.
commented.txt
uncommented.txt

Any other thoughts on this?

I reinstalled the entire vcpkg build and it seems to be working.  I'm not sure what caused it since nothing else changed.


Logging configurations mess up in the presence of multiple bindings for SLF4J

When there are multiple bindings available for SLF4J in the class path, it messes with the logging configuration. According to SLF4J [1], the way a binding is selected is dependent on the JVM and therefore, should be considered a random selection. This issue may be possible to solve with SLF4J 1.8. But currently, it is still in alpha stage.
This will be an issue if a user puts a 3rd party library which has a logging framework embedded in it to the <BALLERINA_HOME>/bre/lib directory.
To further illustrate this issue, the following is a normal log output to the console from a simple Ballerina main program.
2017-06-30 17:00:58,658  INFO  [com.xyz] - Inside package 'com.xyz'
2017-06-30 17:00:58,663  INFO  [com.abc] - Inside package 'com.abc'
2017-06-30 17:00:58,664  ERROR [com.abc] - Error inside package 'com.abc'

Given below is the result of executing the same program, but this time, a library with Log4J embedded in it (activemq-all-5.14.0.jar) was placed in <BALLERINA_HOME>/bre/lib directory.
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/pubudu/products/ballerina-tools-0.89/bre/lib/activemq-all-5.14.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/pubudu/products/ballerina-tools-0.89/bre/lib/slf4j-jdk14-1.7.22.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
 INFO | Inside package 'com.xyz'
 INFO | Inside package 'com.abc'
ERROR | Error inside package 'com.abc'

As it can be seen from the last 3 lines, the log format is not the format we specified.
[1] https://www.slf4j.org/codes.html#multiple_bindings

SLF4J dependency is removed in https://github.com/ballerina-platform/module-ballerina-log/pull/116. Therefore, this issue no longer exisits.

I don't think removing it from just the log module would fix this issue. But removing the dependency on a log library would indeed fix the user log format messing up issue. This is not an std lib issue, rather a general issue in the distribution.


Adding new puzzles

Summary of Changes

Added 3 puzzles

Pull Request Test Coverage Report for Build 675

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

Totals

Change from base Build 514:
0.0%

Covered Lines:
158

Relevant Lines:
180

💛  - Coveralls


chore(deps): update common-dev-assets digest to f1d2dcd

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
40eeed9 -> f1d2dcd

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

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

GitHub release
v2.2.1

Your semantic-release bot :package::rocket:


AVX2 question

So do you need AVX2 instructions to run MKL-DNN? I've ported MKL-DNN to windows and it died at:
0000002D5FD130E7	vfmadd231ps		ymm0,ymm12,ymm15

Saying illegal instruction, so I checked cpuid flags and YMM is enabled in XCR0, but it seems the AVX2 flag is not set. So that means the fused multiply add won't work, is that correct?

Yeah, I answered my own question, judging from the name of some of the files, i.e. jit_avx2_* I guess AVX2 is required. And there is an FMA flag in cpuid results and its off on my cpu, which is strange, I have a fairly recent Core i7 so I don't know why AVX2 wouldn't be in there unless Intel makes some cheaper version missing advanced instructions for big box stores. Such a pain now that all that work porting to windows was for nothing.

I'm sorry you are having troubles with running MKL-DNN after porting it to Windows. What is the brand string of you CPU? Knowing that, it is possible to check if your CPU is supposed to support AVX2 on ark.intel.com. I've looked at that site and I see that all i7 CPUs starting from the 4th gen support AVX2.

So I have an i7-3630QM chip, I'm guessing that it more or less follows the convention that the first number after the dash is the generation. So I think I have a 3rd generation chipset would be my assumption, which would explain the lack of AVX2. Probably whoever manufactured the computer had some old CPU inventory or bought some overstock and decided to unload it. Here is what I did to verify what features were available, modified slightly from some code an Intel employee provided:
void print_intel_features() {
	int *abcd = (int*)calloc(4, sizeof(int));
	int FMA = (1 << 12),
		MOVBE = (1 << 22),
		OSXSAVE = (1 << 27),
		AVX2 = (1 << 5),
		BMI1 = (1 << 3),
		BMI2 = (1 << 8),
		LZCNT = (1 << 5);

	std::ostringstream ss;
	__cpuidex(abcd, 1, 0);
	ss << "FMA       = " << ((abcd[2] & FMA) == FMA ? "yes" : "no") << std::endl;
	ss << "MOVBE     = " << ((abcd[2] & MOVBE) == MOVBE ? "yes" : "no") << std::endl;
	ss << "OSXSAVE   = " << ((abcd[2] & OSXSAVE) == OSXSAVE ? "yes" : "no") << std::endl;

	__cpuidex(abcd, 7, 0);
	ss << "BMI1      = " << ((abcd[1] & BMI1) == BMI1 ? "yes" : "no") << std::endl;
	ss << "BMI2      = " << ((abcd[1] & BMI2) == BMI2 ? "yes" : "no") << std::endl;
	ss << "AVX2      = " << ((abcd[1] & AVX2) == AVX2 ? "yes" : "no") << std::endl;

	__cpuidex(abcd, 0x80000001, 0);
	ss << "LZCNT     = " << ((abcd[2] & LZCNT) == LZCNT ? "yes" : "no") << std::endl;
	free(abcd);

	uint32_t xcr0 = _xgetbv(0);
	ss << "YMM       = " << ((xcr0 & 6) == 6 ? "yes" : "no") << std::endl;
	write("G:/algo/intel.txt", ss.str(), true);
	std::cout << ss.str() << std::endl;

}

And it outputs:
FMA			= no
MOVBE		= no
OSXSAVE		= yes
BMI1		= no
BMI2		= no
AVX2		= no
LZCNT		= no
YMM		= yes

I think maybe it has AVX, otherwise why are the YMM registers there, but not AVX2. So I'm guessing all this points to the fact that I'll probably have to buy a new CPU to keep working on it, and make sure to save the receipt this time so I can return it if I find out later they gipped me with some old stuff.

Right. i7-3630QM is an IvyBridge CPU (http://ark.intel.com/products/71459/Intel-Core-i7-3630QM-Processor-6M-Cache-up-to-3_40-GHz) which has AVX but not AVX2.


Ros2 migration behavior/arm

Conversion was straightforward, with the exception of a few issues that I marked TODO:

arm/tools/arm_tool.cc, line 168: The arm_tool is initialized using the AnonymousName option, which is not yet available in ROS2, although there seems to be active work on it (as of this week).
arm/src/arm_nodelet.cc, lines 491-493: Some functions were not ported, as they no longer seem applicable in ROS2, such as GetPrivateHandle(), Listen function for reconfiguring parameters and its corresponding reconfigure_callback function.
arm/src/arm_nodelet.cc: Line 546: A subscriber for TOPIC_JOINT_GOALS is created, originally with latch=true, however  this topic is not in the LatchedTopic list, so if we use the FF_CREATE_SUBSCRIBER, the topic will not be latched.

arm/tools/arm_tool.cc, line 168: The arm_tool is initialized using the AnonymousName option, which is not yet available in ROS2, although there seems to be active work on it (as of this week).

As far as I understand, the AnonymousName option appends a random number to the end of the node name at initialization time, which we could do manually at [1]. I see you also changed the node name from "control" to "arm_tool", which seems like an improvement.
[1] https://github.com/nasa/astrobee/blob/939adfe9cb50e536800afb6937c21793a64e3e41/behaviors/arm/tools/arm_tool.cc#L195

arm/src/arm_nodelet.cc: Line 546: A subscriber for TOPIC_JOINT_GOALS is created, originally with latch=true, however  this topic is not in the LatchedTopic list, so if we use the FF_CREATE_SUBSCRIBER, the topic will not be latched.

@marinagmoreira and @kbrowne15 recently merged https://github.com/nasa/astrobee/commit/a3ae21283d311fcc9c48d3cf75fb4d76bc41ed07 on develop, which makes this publisher non-latching.
I'm not sure why it was originally marked latching. The latching option would have the effect of automatically resending the joint goals if somehow the arm nodelet joined late after the goals were originally published, but I don't think that's really desired (could lead to an unintended "zombie command").

So I tested the arm behavior in simulation and it works. But let's hold on merging this until we make a decision on the services since it affects it.
I commented out the services test because as a gtest, it's really hard to test it since the server and client are started from the same main, and that opens a can of worms for the sync service problem. That's why the service test passed in the past, even if we couldn't use it for components.
I'll keep on tinkering with the service test to see if I can make it work with a multithreaded executor since we might want to have the server and client under the same container and if this doesn't work, that's just problems down the line.. just don't want to sink even more time into it :(..


add tests

add some test to check non-gui-stuff, to be executed with sbt testOnly or scala-cli test or something similar

first test added: https://github.com/lunduniversity/introprog-scalalib/commit/c80904a2da4899c33d66449eac5e1dc4a01ccec6


Compiled app fails on OSX

Bug/Issue Description:
when I run compile file , It run normal, but It show this error.

Required Information:
Provide the following information to assist with reporting the bug:

Provide a full copy of the command line options you are using, for example:

pyinstaller command
 pyinstaller scenedetect.spec
run compile file command
./dist/scenedetect/scenedetect

Add -v debug -l BUG_REPORT.txt to the beginning of the command, then re-run PySceneDetect and attach the generated BUG_REPORT.txt file.

Expected Behavior:
A clear and concise description of what you expected to happen.
Computing Environment:

OS: OSX
Python Version: 3.9.10
OpenCV Version:4.5.5
Pyinstaller Version: 5.0.1

Additional Information:

Media [Videos/Images/Screenshots]:
Provide any other information you can, including videos/media that can demonstrate the bug you are reporting (even YouTube links are fine). If applicable, add the output images from PySceneDetect, or any screenshots you feel are necessary to help explain your problem.
Remove this section if there is no media associated with the issue/bug report.

Unfortunately I don't have any OSX machines to test/develop on, so I'll need some assistance with debugging this one.
Just to confirm, are you able to run scenedetect if you install the package (either via pip or python -m build)?

Unfortunately I don't have any OSX machines to test/develop on, so I'll need some assistance with debugging this one. Are you able to run scenedetect if you install the package (either via pip or python -m build)?
Can you try using PyInstaller 4.10? (python -m pip install pyinstaller==4.10) This is the current version I'm using to build the Windows app.
Thanks!
Edit: I just tried using both PyInstaller 5.0.1 and the latest (5.1) on Ubuntu 20.04 with Python 3.8 and it seemed to work correctly. Are there any errors in the output of running pyinstaller scenedetect.spec? Could you try running from the root of the repo, e.g. pyinstaller dist/scenedetect.spec?
I found a similar sounding bug in BEEmod/BEE2.4#1585 on Ubuntu, but the outcome was inconclusive.

Hi, I'm very sorry I'm leading in the mistake, I compiled successfully, and  I can run the executable file, But when I run the file  in the command , I always show this message

and I found that there is always such a child process in the system process, the child process has been suspended and restarted

I also  run python scenedetect.py, it's corrected.  and I use 'python setup.py install',  it also normal.

the pyinstaller compile log is here, I hope it can help you
(venv) ➜  ~/workspace/PySceneDetect git:(master) ✗ pyinstaller -v               5.0.1 (venv) ➜  ~/workspace/PySceneDetect git:(master) ✗ pyinstaller scenedetect.spec 169 INFO: PyInstaller: 5.0.1 169 INFO: Python: 3.9.10 183 INFO: Platform: macOS-11.6-x86_64-i386-64bit 189 INFO: UPX is not available. 191 INFO: Extending PYTHONPATH with paths ['/workspace/PySceneDetect',  '/workspace/PySceneDetect'] 486 INFO: checking Analysis 487 INFO: Building Analysis because Analysis-00.toc is non existent 487 INFO: Initializing module dependency graph... 497 INFO: Caching module graph hooks... 508 INFO: Analyzing base_library.zip ... 2863 INFO: Processing pre-find module path hook distutils from '/usr/local/lib/python3.9/site-packages/PyInstaller/hooks/pre_find_module_path/hook-distutils.py'. 2980 INFO: distutils: retargeting to non-venv dir<EMAIL_ADDRESS>6105 INFO: Caching module dependency graph... 6253 INFO: running Analysis Analysis-00.toc 6261 INFO: Analyzing scenedetect/__main__.py 9518 INFO: Processing pre-find module path hook site from '/usr/local/lib/python3.9/site-packages/PyInstaller/hooks/pre_find_module_path/hook-site.py'. 9518 INFO: site: retargeting to fake-dir '/usr/local/lib/python3.9/site-packages/PyInstaller/fake-modules' 12417 INFO: Processing module hooks... 12417 INFO: Loading module hook 'hook-py.py' from '/usr/local/lib/python3.9/site-packages/_pyinstaller_hooks_contrib/hooks/stdhooks'... 12962 INFO: Loading module hook 'hook-cv2.py' from '/usr/local/lib/python3.9/site-packages/_pyinstaller_hooks_contrib/hooks/stdhooks'... 12966 INFO: Loading module hook 'hook-pytest.py' from '/usr/local/lib/python3.9/site-packages/_pyinstaller_hooks_contrib/hooks/stdhooks'... 13197 INFO: Loading module hook 'hook-pkg_resources.py' from '/usr/local/lib/python3.9/site-packages/PyInstaller/hooks'... 99 WARNING: Failed to collect submodules for 'pkg_resources._vendor.pyparsing.diagram' because importing 'pkg_resources._vendor.pyparsing.diagram' raised: ModuleNotFoundError: No module named 'railroad' 13971 INFO: Processing pre-safe import module hook win32com from '/usr/local/lib/python3.9/site-packages/_pyinstaller_hooks_contrib/hooks/pre_safe_import_module/hook-win32com.py'. 14596 WARNING: Hidden import "pkg_resources.py2_warn" not found! 14597 WARNING: Hidden import "pkg_resources.markers" not found! 14601 INFO: Loading module hook 'hook-xml.etree.cElementTree.py' from '/usr/local/lib/python3.9/site-packages/PyInstaller/hooks'... 14602 INFO: Loading module hook 'hook-lib2to3.py' from '/usr/local/lib/python3.9/site-packages/PyInstaller/hooks'... 14620 INFO: Loading module hook 'hook-encodings.py' from '/usr/local/lib/python3.9/site-packages/PyInstaller/hooks'... 14697 INFO: Loading module hook 'hook-distutils.util.py' from '/usr/local/lib/python3.9/site-packages/PyInstaller/hooks'... 14703 INFO: Loading module hook 'hook-setuptools.py' from '/usr/local/lib/python3.9/site-packages/PyInstaller/hooks'... 164 WARNING: Failed to collect submodules for 'setuptools._vendor.pyparsing.diagram' because importing 'setuptools._vendor.pyparsing.diagram' raised: ModuleNotFoundError: No module named 'railroad' 16325 INFO: Loading module hook 'hook-xml.dom.domreg.py' from '/usr/local/lib/python3.9/site-packages/PyInstaller/hooks'... 16326 INFO: Loading module hook 'hook-packaging.py' from '/usr/local/lib/python3.9/site-packages/PyInstaller/hooks'... 16327 INFO: Loading module hook 'hook-pickle.py' from '/usr/local/lib/python3.9/site-packages/PyInstaller/hooks'... 16330 INFO: Loading module hook 'hook-heapq.py' from '/usr/local/lib/python3.9/site-packages/PyInstaller/hooks'... 16333 INFO: Loading module hook 'hook-difflib.py' from '/usr/local/lib/python3.9/site-packages/PyInstaller/hooks'... 16336 INFO: Loading module hook 'hook-multiprocessing.util.py' from '/usr/local/lib/python3.9/site-packages/PyInstaller/hooks'... 16339 INFO: Loading module hook 'hook-sysconfig.py' from '/usr/local/lib/python3.9/site-packages/PyInstaller/hooks'... 16347 INFO: Loading module hook 'hook-xml.py' from '/usr/local/lib/python3.9/site-packages/PyInstaller/hooks'... 16347 INFO: Loading module hook 'hook-numpy.py' from '/usr/local/lib/python3.9/site-packages/PyInstaller/hooks'... 16407 INFO: Import to be excluded not found: 'f2py' 16407 INFO: Loading module hook 'hook-distutils.py' from '/usr/local/lib/python3.9/site-packages/PyInstaller/hooks'... 16410 INFO: Loading module hook 'hook-numpy._pytesttester.py' from '/usr/local/lib/python3.9/site-packages/PyInstaller/hooks'... 16413 INFO: Loading module hook 'hook-setuptools.msvc.py' from '/usr/local/lib/python3.9/site-packages/PyInstaller/hooks'... 16442 INFO: Looking for ctypes DLLs 16495 INFO: Analyzing run-time hooks ... 16499 INFO: Including run-time hook '/usr/local/lib/python3.9/site-packages/PyInstaller/hooks/rthooks/pyi_rth_subprocess.py' 16503 INFO: Including run-time hook '/usr/local/lib/python3.9/site-packages/PyInstaller/hooks/rthooks/pyi_rth_pkgutil.py' 16507 INFO: Including run-time hook '/usr/local/lib/python3.9/site-packages/PyInstaller/hooks/rthooks/pyi_rth_multiprocessing.py' 16510 INFO: Including run-time hook '/usr/local/lib/python3.9/site-packages/PyInstaller/hooks/rthooks/pyi_rth_inspect.py' 16521 INFO: Looking for dynamic libraries /usr/local/lib/python3.9/site-packages/PyInstaller/building/build_main.py:156: UserWarning: The numpy.array_api submodule is still experimental. See NEP 47.   __import__(package) 17548 INFO: Looking for eggs 17548 INFO: Using Python library<EMAIL_ADDRESS>17560 INFO: Warnings written to /workspace/PySceneDetect/build/scenedetect/warn-scenedetect.txt 17620 INFO: Graph cross-reference written to /workspace/PySceneDetect/build/scenedetect/xref-scenedetect.html 17635 INFO: Appending 'datas' from .spec 17640 INFO: checking PYZ 17640 INFO: Building PYZ because PYZ-00.toc is non existent 17640 INFO: Building PYZ (ZlibArchive) /workspace/PySceneDetect/build/scenedetect/PYZ-00.pyz 18415 INFO: Building PYZ (ZlibArchive) /workspace/PySceneDetect/build/scenedetect/PYZ-00.pyz completed successfully. 18427 INFO: EXE target arch: x86_64 18427 INFO: Code signing identity: None 18427 INFO: checking PKG 18427 INFO: Building PKG because PKG-00.toc is non existent 18427 INFO: Building PKG (CArchive) scenedetect.pkg 18441 INFO: Building PKG (CArchive) scenedetect.pkg completed successfully. 18442 INFO: Bootloader /usr/local/lib/python3.9/site-packages/PyInstaller/bootloader/Darwin-64bit/run 18442 INFO: checking EXE 18442 INFO: Building EXE because EXE-00.toc is non existent 18442 INFO: Building EXE from EXE-00.toc 18442 INFO: Copying bootloader EXE to /workspace/PySceneDetect/build/scenedetect/scenedetect 18443 INFO: Converting EXE to target arch (x86_64) 18467 INFO: Removing signature(s) from EXE 18506 INFO: Appending PKG archive to EXE 18510 INFO: Fixing EXE headers for code signing 18521 INFO: Re-signing the EXE 18579 INFO: Building EXE from EXE-00.toc completed successfully. 18583 INFO: checking COLLECT 18583 INFO: Building COLLECT because COLLECT-00.toc is non existent 18583 INFO: Building COLLECT COLLECT-00.toc 20908 INFO: Building COLLECT COLLECT-00.toc completed successfully.

When I use the pyinstall in the version 4.10. It compile successfully, But I run the executable file, it show nothing .
This is the compile log and run log .
(venv) ➜  ~/workspace/PySceneDetect git:(master) ✗ pyinstaller -v
4.10
(venv) ➜  ~/workspace/PySceneDetect git:(master) ✗ pyinstaller scenedetect.py
116 INFO: PyInstaller: 4.10
117 INFO: Python: 3.9.10
130 INFO: Platform: macOS-11.6-x86_64-i386-64bit
132 INFO: wrote ~/workspace/PySceneDetect/scenedetect.spec
136 INFO: UPX is not available.
139 INFO: Extending PYTHONPATH with paths
['~/workspace/PySceneDetect']
312 INFO: checking Analysis
312 INFO: Building Analysis because Analysis-00.toc is non existent
312 INFO: Initializing module dependency graph...
316 INFO: Caching module graph hooks...
324 INFO: Analyzing base_library.zip ...
2591 INFO: Processing pre-find module path hook distutils from '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/PyInstaller/hooks/pre_find_module_path/hook-distutils.py'.
2655 INFO: distutils: retargeting to non-venv dir<EMAIL_ADDRESS>5511 INFO: Caching module dependency graph...
5657 INFO: running Analysis Analysis-00.toc
5666 INFO: Analyzing ~/workspace/PySceneDetect/scenedetect.py
7940 INFO: Processing pre-find module path hook site from '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/PyInstaller/hooks/pre_find_module_path/hook-site.py'.
7940 INFO: site: retargeting to fake-dir '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/PyInstaller/fake-modules'
10506 INFO: Processing module hooks...
10506 INFO: Loading module hook 'hook-py.py' from '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/_pyinstaller_hooks_contrib/hooks/stdhooks'...
10886 INFO: Loading module hook 'hook-cv2.py' from '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/_pyinstaller_hooks_contrib/hooks/stdhooks'...
10890 INFO: Loading module hook 'hook-pytest.py' from '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/_pyinstaller_hooks_contrib/hooks/stdhooks'...
11093 INFO: Loading module hook 'hook-pkg_resources.py' from '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
11417 INFO: Processing pre-safe import module hook win32com from '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/_pyinstaller_hooks_contrib/hooks/pre_safe_import_module/hook-win32com.py'.
11572 WARNING: Hidden import "pkg_resources.py2_warn" not found!
11573 WARNING: Hidden import "pkg_resources.markers" not found!
11577 INFO: Loading module hook 'hook-xml.etree.cElementTree.py' from '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
11578 INFO: Loading module hook 'hook-lib2to3.py' from '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
11599 INFO: Loading module hook 'hook-encodings.py' from '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
11675 INFO: Loading module hook 'hook-distutils.util.py' from '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
11682 INFO: Loading module hook 'hook-setuptools.py' from '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
12258 INFO: Loading module hook 'hook-xml.dom.domreg.py' from '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
12264 INFO: Loading module hook 'hook-packaging.py' from '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
12265 INFO: Loading module hook 'hook-pickle.py' from '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
12269 INFO: Loading module hook 'hook-heapq.py' from '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
12272 INFO: Loading module hook 'hook-difflib.py' from '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
12275 INFO: Loading module hook 'hook-multiprocessing.util.py' from '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
12278 INFO: Loading module hook 'hook-sysconfig.py' from '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
12286 INFO: Loading module hook 'hook-xml.py' from '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
12287 INFO: Loading module hook 'hook-numpy.py' from '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
12341 INFO: Import to be excluded not found: 'f2py'
12359 INFO: Loading module hook 'hook-distutils.py' from '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
12359 INFO: Loading module hook 'hook-numpy._pytesttester.py' from '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
12362 INFO: Loading module hook 'hook-setuptools.msvc.py' from '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/PyInstaller/hooks'...
12389 INFO: Looking for ctypes DLLs
12443 INFO: Analyzing run-time hooks ...
12447 INFO: Including run-time hook '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/PyInstaller/hooks/rthooks/pyi_rth_subprocess.py'
12448 INFO: Including run-time hook '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/PyInstaller/hooks/rthooks/pyi_rth_pkgutil.py'
12450 INFO: Including run-time hook '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/PyInstaller/hooks/rthooks/pyi_rth_multiprocessing.py'
12453 INFO: Including run-time hook '~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/PyInstaller/hooks/rthooks/pyi_rth_inspect.py'
12462 INFO: Looking for dynamic libraries
13168 INFO: Looking for eggs
13168 INFO: Using Python library<EMAIL_ADDRESS>13175 INFO: Warnings written to ~/workspace/PySceneDetect/build/scenedetect/warn-scenedetect.txt
13229 INFO: Graph cross-reference written to ~/workspace/PySceneDetect/build/scenedetect/xref-scenedetect.html
13255 INFO: checking PYZ
13256 INFO: Building PYZ because PYZ-00.toc is non existent
13256 INFO: Building PYZ (ZlibArchive) ~/workspace/PySceneDetect/build/scenedetect/PYZ-00.pyz
13894 INFO: Building PYZ (ZlibArchive) ~/workspace/PySceneDetect/build/scenedetect/PYZ-00.pyz completed successfully.
13910 INFO: EXE target arch: x86_64
13910 INFO: Code signing identity: None
13910 INFO: checking PKG
13910 INFO: Building PKG because PKG-00.toc is non existent
13910 INFO: Building PKG (CArchive) scenedetect.pkg
13933 INFO: Building PKG (CArchive) scenedetect.pkg completed successfully.
13934 INFO: Bootloader ~/workspace/PySceneDetect/venv/lib/python3.9/site-packages/PyInstaller/bootloader/Darwin-64bit/run
13934 INFO: checking EXE
13934 INFO: Building EXE because EXE-00.toc is non existent
13934 INFO: Building EXE from EXE-00.toc
13934 INFO: Copying bootloader EXE to ~/workspace/PySceneDetect/build/scenedetect/scenedetect
13935 INFO: Converting EXE to target arch (x86_64)
13970 INFO: Removing signature(s) from EXE
14017 INFO: Appending PKG archive to EXE
14020 INFO: Fixing EXE headers for code signing
14033 INFO: Re-signing the EXE
14096 INFO: Building EXE from EXE-00.toc completed successfully.
14100 INFO: checking COLLECT
14100 INFO: Building COLLECT because COLLECT-00.toc is non existent
14100 INFO: Building COLLECT COLLECT-00.toc
16510 INFO: Building COLLECT COLLECT-00.toc completed successfully.
(venv) ➜  ~/workspace/PySceneDetect git:(master) ✗ ./dist/scenedetect/scenedetect
(venv) ➜  ~/workspace/PySceneDetect git:(master) ✗ ./dist/scenedetect/scenedetect -h
(venv) ➜  ~/workspace/PySceneDetect git:(master) ✗ ./dist/scenedetect/scenedetect -h
(venv) ➜  ~/workspace/PySceneDetect git:(master) ✗

I noticed you used the command pyinstaller scenedetect.py in your last comment, you need to make sure to use the .spec file for the app to work correctly.   I don't see any issues in the PyInstaller logs, but can you retry with PyInstaller 4.10 and the .spec file?  It would be useful to know if the issue only happens with PyInstaller 5.x or happens on all versions.
Thanks for bringing this up, I'm sorry I can't be more help in debugging the problem.  For now I will mark this as a known issue, and hopefully someone on OSX more familiar with PyInstaller might be able to help out more.

My first time doing any of this. Hope this helps @Breakthrough
What I would like to get is a single file I can include in an Xcode project to call scenedetect. Will this process do it for me?
Here's the log using PyInstaller 4.10:

pyinstaller scenedetect.spec
49 INFO: PyInstaller: 4.10
49 INFO: Python: 3.9.12
59 INFO: Platform: macOS-12.5-arm64-arm-64bit
61 INFO: UPX is not available.
62 INFO: Extending PYTHONPATH with paths
['/Users/x/Downloads/PySceneDetect-master-2',
'/Users/x/Downloads/PySceneDetect-master-2/dist']
132 INFO: checking Analysis
132 INFO: Building Analysis because Analysis-00.toc is non existent
132 INFO: Initializing module dependency graph...
134 INFO: Caching module graph hooks...
138 INFO: Analyzing base_library.zip ...
1317 INFO: Processing pre-find module path hook distutils from '/opt/homebrew/lib/python3.9/site-packages/PyInstaller/hooks/pre_find_module_path/hook-distutils.py'.
1344 INFO: distutils: retargeting to non-venv dir<EMAIL_ADDRESS>2233 INFO: Caching module dependency graph...
2297 INFO: running Analysis Analysis-00.toc
2302 INFO: Analyzing ../scenedetect/main.py
2688 INFO: Processing pre-find module path hook site from '/opt/homebrew/lib/python3.9/site-packages/PyInstaller/hooks/pre_find_module_path/hook-site.py'.
2689 INFO: site: retargeting to fake-dir '/opt/homebrew/lib/python3.9/site-packages/PyInstaller/fake-modules'
3796 INFO: Processing pre-safe import module hook win32com from '/opt/homebrew/lib/python3.9/site-packages/_pyinstaller_hooks_contrib/hooks/pre_safe_import_module/hook-win32com.py'.
3809 INFO: Processing module hooks...
3809 INFO: Loading module hook 'hook-appdirs.py' from '/opt/homebrew/lib/python3.9/site-packages/_pyinstaller_hooks_contrib/hooks/stdhooks'...
3810 INFO: Loading module hook 'hook-cv2.py' from '/opt/homebrew/lib/python3.9/site-packages/_pyinstaller_hooks_contrib/hooks/stdhooks'...
3811 INFO: Loading module hook 'hook-pkg_resources.py' from '/opt/homebrew/lib/python3.9/site-packages/PyInstaller/hooks'...
4046 WARNING: Hidden import "pkg_resources.py2_warn" not found!
4046 WARNING: Hidden import "pkg_resources.markers" not found!
4047 INFO: Loading module hook 'hook-xml.etree.cElementTree.py' from '/opt/homebrew/lib/python3.9/site-packages/PyInstaller/hooks'...
4048 INFO: Loading module hook 'hook-lib2to3.py' from '/opt/homebrew/lib/python3.9/site-packages/PyInstaller/hooks'...
4056 INFO: Loading module hook 'hook-encodings.py' from '/opt/homebrew/lib/python3.9/site-packages/PyInstaller/hooks'...
4082 INFO: Loading module hook 'hook-distutils.util.py' from '/opt/homebrew/lib/python3.9/site-packages/PyInstaller/hooks'...
4084 INFO: Loading module hook 'hook-setuptools.py' from '/opt/homebrew/lib/python3.9/site-packages/PyInstaller/hooks'...
4401 INFO: Loading module hook 'hook-pickle.py' from '/opt/homebrew/lib/python3.9/site-packages/PyInstaller/hooks'...
4402 INFO: Loading module hook 'hook-heapq.py' from '/opt/homebrew/lib/python3.9/site-packages/PyInstaller/hooks'...
4403 INFO: Loading module hook 'hook-difflib.py' from '/opt/homebrew/lib/python3.9/site-packages/PyInstaller/hooks'...
4404 INFO: Loading module hook 'hook-multiprocessing.util.py' from '/opt/homebrew/lib/python3.9/site-packages/PyInstaller/hooks'...
4405 INFO: Loading module hook 'hook-sysconfig.py' from '/opt/homebrew/lib/python3.9/site-packages/PyInstaller/hooks'...
4409 INFO: Loading module hook 'hook-xml.py' from '/opt/homebrew/lib/python3.9/site-packages/PyInstaller/hooks'...
4426 INFO: Loading module hook 'hook-numpy.py' from '/opt/homebrew/lib/python3.9/site-packages/PyInstaller/hooks'...
4443 INFO: Import to be excluded not found: 'f2py'
4453 INFO: Loading module hook 'hook-distutils.py' from '/opt/homebrew/lib/python3.9/site-packages/PyInstaller/hooks'...
4453 INFO: Loading module hook 'hook-numpy._pytesttester.py' from '/opt/homebrew/lib/python3.9/site-packages/PyInstaller/hooks'...
4454 INFO: Loading module hook 'hook-setuptools.msvc.py' from '/opt/homebrew/lib/python3.9/site-packages/PyInstaller/hooks'...
4466 INFO: Looking for ctypes DLLs
4488 INFO: Analyzing run-time hooks ...
4491 INFO: Including run-time hook '/opt/homebrew/lib/python3.9/site-packages/PyInstaller/hooks/rthooks/pyi_rth_subprocess.py'
4491 INFO: Including run-time hook '/opt/homebrew/lib/python3.9/site-packages/PyInstaller/hooks/rthooks/pyi_rth_pkgutil.py'
4492 INFO: Including run-time hook '/opt/homebrew/lib/python3.9/site-packages/PyInstaller/hooks/rthooks/pyi_rth_multiprocessing.py'
4493 INFO: Including run-time hook '/opt/homebrew/lib/python3.9/site-packages/PyInstaller/hooks/rthooks/pyi_rth_inspect.py'
4497 INFO: Looking for dynamic libraries
4635 INFO: Looking for eggs
4635 INFO: Using Python library<EMAIL_ADDRESS>4639 INFO: Warnings written to /Users/x/Downloads/PySceneDetect-master-2/dist/build/scenedetect/warn-scenedetect.txt
4660 INFO: Graph cross-reference written to /Users/x/Downloads/PySceneDetect-master-2/dist/build/scenedetect/xref-scenedetect.html
4668 INFO: Appending 'datas' from .spec
4672 INFO: checking PYZ
4672 INFO: Building PYZ because PYZ-00.toc is non existent
4672 INFO: Building PYZ (ZlibArchive) /Users/x/Downloads/PySceneDetect-master-2/dist/build/scenedetect/PYZ-00.pyz
5029 INFO: Building PYZ (ZlibArchive) /Users/x/Downloads/PySceneDetect-master-2/dist/build/scenedetect/PYZ-00.pyz completed successfully.
5034 INFO: EXE target arch: arm64
5034 INFO: Code signing identity: None
5035 INFO: checking PKG
5035 INFO: Building PKG because PKG-00.toc is non existent
5035 INFO: Building PKG (CArchive) scenedetect.pkg
5041 INFO: Building PKG (CArchive) scenedetect.pkg completed successfully.
5042 INFO: Bootloader /opt/homebrew/lib/python3.9/site-packages/PyInstaller/bootloader/Darwin-64bit/run
5042 INFO: checking EXE
5042 INFO: Building EXE because EXE-00.toc is non existent
5042 INFO: Building EXE from EXE-00.toc
5042 INFO: Copying bootloader EXE to /Users/x/Downloads/PySceneDetect-master-2/dist/build/scenedetect/scenedetect
5044 INFO: Converting EXE to target arch (arm64)
6459 INFO: Removing signature(s) from EXE
6473 INFO: Appending PKG archive to EXE
6474 INFO: Fixing EXE headers for code signing
6478 INFO: Re-signing the EXE
6492 INFO: Building EXE from EXE-00.toc completed successfully.
6494 INFO: checking COLLECT
6494 INFO: Building COLLECT because COLLECT-00.toc is non existent
6494 INFO: Building COLLECT COLLECT-00.toc
8963 INFO: Building COLLECT COLLECT-00.toc completed successfully.

I'm hoping to build a single file scenedetect that contains everything needed to run to embed in my Xcode project. Including all dependencies such as CV, Numpy etc etc. I'm very new to python and all the tools such as pyinstaller. Are you able to provide any advice/point me in the right direction?
Thanks in advance.

@9SL9 All you need to do is run pyinstaller dist/scenedetect.spec from the root of the project source, so it looks like you did the right thing.  What do you see as the output when you run the compiled file?  I'm far from a PyInstaller expert myself, nor do I have access to any OSX machines, but I know it works fine on Linux/Windows (this is how the Windows distributions are built).
The actual build script for Windows builds can be found here, link to line where PyInstaller is invoked:
https://github.com/Breakthrough/PySceneDetect/blob/build-windows/appveyor.yml#L45


Release Google.Cloud.Eventarc.V1 version 2.4.0

Changes in this release:
New features

Change netstandard2.1 target to netstandard2.0 (commit 82bea85)

Created release for Google.Cloud.Eventarc.V1-2.4.0


WinRun4J launcher doesn't detect AdoptOpenJDK

OS : Windows 10 Enterprise b1809
AdoptOpenJDK build: 1.8.0_202_b08 (x64) (installed via MSI installer)
Java software to run: SQLWorkbench (http://www.sql-workbench.net/, http://www.sql-workbench.eu/)
Launching JAR via double-click on JAR : sqlworkbench.jar - OK
Launching JAR with CLI: java -jar sqlworkbench.jar - OK
Launch via EXE : SQLWorkbenhc64.exe Error - No suitable Java version could found. Please make sure you hava 64-bit Java 8 installed
SQLWorkbench64.exe/SQLWorkbench.exe are launchers which are based on WinRun4J (http://winrun4j.sourceforge.net/). It appears this launcher doesn't detect
AdoptOpenJDK properly probably due to a missing registry entry.
Screenshot of the error:

Do you know which entry http://winrun4j.sourceforge.net/ is looking for? Is it hardcoded to Oracle Java or?

https://github.com/poidasmith/winrun4j/blob/master/WinRun4J/src/java/VM.cpp

must be fixed for next installer by https://github.com/AdoptOpenJDK/openjdk-installer/pull/84
re-open if needed


problems regarding access denied

Summary
wherever i navigate to my page,it has this message shown in my web preview : AccessDeniedAccess DeniedZHFDGHG5705WNYASt2Ip9BvQNtrZVFoTVBcc+dthOewyHAdMc0lunmMNHWxwGIcI1lSo0CrFWnCfe5ptVl7uAAcHbBM=
and im stuck to correct page in expo go after few reload
What platform(s) does this occur on?
Web
SDK Version
v47.0.0
Reproducible demo or steps to reproduce from a blank project
i dont know. it happens

hi there! could you share the snack url you tested?

sorry, its already fixed.
turns out i forgot to place {navigation} in props.
sorry for the inconvinient
Pada tanggal Sen, 3 Apr 2023 08.45, Kudo Chien @.***>
menulis:

hi there! could you share the snack url you tested?
—
Reply to this email directly, view it on GitHub
https://github.com/expo/snack/issues/409#issuecomment-1493520570, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AV2ZOWJKV37TMJROZCXUEXDW7ITSRANCNFSM6AAAAAAWP64FGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

cool, i'm going to close this issue. if there's any other problems, please create a new issue for us. thanks!


Crate query result in Job killed

CrateDB version
4.8.2
CrateDB setup information
4 node cluster on a k8s cluster. Crate nodes have 10GB ram and 5gb heap.
Observed behavior
On regular interval I get this message in the PHP application that uses Crate to query devices data.
JobKilledException[Job killed. Received data for job=axxxxxx-xxx-xx-xx but there is no job context present. This can happen due to bad network latency or if individual nodes are unresponsive due to high load

I am not sure if the crate cluster is to busy to handle the request. Because it doesn't looks like the cluster is very busy.
Is there something I can do to improve or make sure the error does't occur?
Steps to Reproduce
It occurs on a select query on the table that holds the last know state of the device.

@rjbaat Sorry for the late response, your issue slipped through.
Can you please check the logs of all nodes for error entries in the same period your application receive that error and share it?
Without any additional information it is almost impossible for us to help you.
CrateDB will create tasks on each node which is participating in a query execution, these tasks are receiving input from other tasks on other nodes. If a task was removed due to an error, a possible late received payload targeted for this task will fail with such an error. Normally this should not happen as we try our best to handle errors gracefully and forward them to all participating task, so they will stop processing and bubbling up the error. But in some situations this isn't always possible and such resulting in the error you've seen.
I will move this issue into a discussion as it looks more like a support question than a bug/feature.


Rebuild homepage

This PR has ended up far larger than I wanted, but it's got a lot.

Rebuild much of the homepage code.

The indentation made it super confusing which section you were in, so I've made it totally consistent.
There's an ID for each section of the page, making it easier to link to.
I've adjusted some of the whitespace in the design, and bumped the font sizes in the intro. In the interest of keeping this short, look at the screenshots in #37.
Render Google Analytics to homepage from the ga.html partial.
The tags are more consistent (section/article/etc). They're not perfect, but definitely an improvement.
Lastly, I've removed a few stray HTML closing tags that were confusing. (Mostly <div>s.) They weren't breaking the layout, but...

Fix indentation of Google Analytics in the partial. Because that's rendered on every page, the PR looks much larger.

If you want me to pull out the analytics chunk, I definitely could, but it's pretty benign.

@mrmrs 😁

Hey @lachlanjc . What do you think about breaking these out into separate PRs? A bit heavy at the moment. All useful - but would prefer if they were separate things we can look at in isolation.

Ah sure thing! Busy with finals right now but I'll get to it soon.


LinkedIn URL in Edit Profile should have validation for '/'  like the rest of other media types

https://staging.fightpandemics.work/
Chrome - Window 10
Login as Individual
Click on Profile =>Edit pen =>Edit Profile
provide all the values for these below and see all except LinkedIn URL give the error validation message when entering /
Facebook URL
Installgram URL
LinkedIn URL
Twitter URL
Github URL
Without providing the error message for LinkedIn URL when entering the / at the end, click on Save Changes button , we have this message on the top
Failed updating profile, reason: error.http.body.urls.linkedin should be null, body.urls.linkedin should match pattern "^[a-zA-Z0-9-]*$", body.urls.linkedin should match some schema in anyOf

Further more , we are unable to save any valid values for the rest of other media types and we have to re-type again.     in Summary
1-LinkedIn URL should have the validation  message for input with / like other media type
2- It is nice to have the page retain the values entered (option)
please see the record attached

Close this one after passing the validation n #1683


CLI build process improvements

We now use a configuration object instead of multiple parameters. This makes the code a little bit cleaner and sets the stage for adding new things to the build process.

I like it, thanks 👍


#22 Add "vendor" top level namespace

PhpParser -> Microsoft\PhpParser
close #22

Hi @mousetraps, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Sara Itani). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;


Remove unused Dmn field on EvalNodeHelper

https://github.com/prometheus/prometheus/pull/13446 removed the last usage of this field, but didn't remove the field.

Ah, right :)


tool_coverage-linux fails with "Signaled to exit!"

Sample build run: https://cirrus-ci.com/task/6308404167704576?command=main#L1047
This has kept the tree closed for 17 hours as of this writing.
/cc @jonahwilliams @zanderso

/cc @gspencergoog

@a-siva Has there been a change in line coverage in the Dart VM? Is there anything we should do on the Flutter side to make coverage work again?

I'm going to see if the OOM is tickled by how we're running coverage

This should be fixed now (see https://github.com/dart-lang/sdk/commit/fcf88fe6faa0b7a63a690a716f914b5400657c2a)


Errors in post_pull Commands Silently Dropped

Errors coming from commands in post_pull (and presumably in post_clone as well) are reportedly being dropped silently. Ensure we error out gracefully as expected.

Issue was actually flipping of post_clone and post_pull (each was being invoked in the other's place).

Fixed in 20220601 release.


It is not possible to disconnect the Bluetooth while it is in the process of connecting.

During the process of connecting Bluetooth (note: at this point the status is "connecting" instead of "connected"), I immediately called the disposable.dispose() function to disconnect. On Android 8.1 system, there may be a situation where Bluetooth cannot be disconnected properly even if I uninstall the App, and the Bluetooth remains connected. This situation almost always occurs.
One solution is to add bluetoothGatt.disconnect() before bluetoothGatt.close() in DisconnectOperation.java, but I am not sure if doing so will cause other problems.

I guess you reference problem described here: https://github.com/dariuszseweryn/RxAndroidBle/wiki/FAQ:-Cannot-connect#calling-bluetoothgattclose-with-wrong-timing
IIRC the library does call disconnect always before closing the bluetoothGatt


Check that all the predefined rules are declared in the all rules acceptance test

Can be seen in action here: https://github.com/voxpupuli/puppet-nftables/pull/54/checks?check_run_id=1537808159

This will be overwritten by modulesync.
Looking at the template https://github.com/voxpupuli/modulesync_config/blob/master/moduleroot/.github/workflows/ci.yml.erb
There is no parameter to add extra tests which there used to be with the old Travis templates I think. (Maybe confusing with our own templates).

Will try and extend the templates.

🤷


three questions about the estimation

Dear Junior Maih:
I was recently using the RISE toolbox you developed to study the MS-DSGE, but there are three questions about the estimation when I run the RISE:

when looking for good enough start values, Matlab shows the massage: Your initial point x0 is not between bounds lb and ub; FMINCON; shifted x0 to strictly satisfy the bounds. So why does Matlab report the massage? Do I need to do something to modify it？
when looking for good enough start values, fmincon stopped because the size of the current step is less than the selected value of the step size tolerance and constraints are satisfied to within the default value of the constraint tolerance. Change in X too small. Fmincon of examples in RISE toolbox stopped after hundreds of times, however, when I run my model, it stopped after several times. How to modify it?
there is a warming that the matrix is close to a singular value, or the scaling is incorrect. The result may be inaccurate. RCOND =  2.229894e-22. And how to modify?

Hope you can take the time to answer my questions.
Best wishes!
Kidd
June 22, 2020

Hi Kidd,

It must be the case that the start value for one (or more) of your
parameters lies outside the bounds you specified. You should check the way
you set your priors and understand the role played by each number
If your start values for estimation are close to a peak, there is no
reason for fmincon to search for a long time. Oftentimes though, it is the
case that optimization stops at a local maximum while what you ideally want
is the global maximum.
The warning that a matrix is singular may come from the fact that the
procedure tries to invert a matrix that is not invertible. Without seeing
exactly what you are doing, I cannot tell you where the problem comes from.

Cheers and Best wishes,
J
On Mon, Jun 22, 2020 at 10:48 AM 55Kidd<EMAIL_ADDRESS>wrote:

Dear Junior Maih:
I was recently using the RISE toolbox you developed to study the MS-DSGE,
but there are three questions about the estimation when I run the RISE:

when looking for good enough start values, Matlab shows the
massage: Your initial point x0 is not between bounds lb and ub; FMINCON;
shifted x0 to strictly satisfy the bounds. So why does Matlab report the
massage? Do I need to do something to modify it？
when looking for good enough start values, fmincon stopped because
the size of the current step is less than the selected value of the step
size tolerance and constraints are satisfied to within the default value of
the constraint tolerance. Change in X too small. Fmincon of examples in
RISE toolbox stopped after hundreds of times, however, when I run my model,
it stopped after several times. How to modify it?
there is a warming that the matrix is close to a singular value, or
the scaling is incorrect. The result may be inaccurate. RCOND =
2.229894e-22. And how to modify?

Hope you can take the time to answer my questions.
Best wishes!
Kidd
June 22, 2020
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jmaih/RISE_toolbox/issues/136, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AATKBT4BIJWZQJFLCTGHLN3RX4LE3ANCNFSM4OELTBFA
.

Dear Junior Maih:
Is the result reliable with only 2 trials？Could you please tell me how to deal with the problems of fmincon and singularity? Here is my code：
1.zip
Many thanks!
Kidd
June 23, 2020

I think I have answered this question in another thread. See #137


[Box, Flexbox, Row, Stack] Create Flexbox, Row, Stack components, DRY out Box types

This PR is WIP — I'm looking for feedback before writing tests and docs for the new components. There are two main points of this work:

DRY out Box types for use in Box-derived components (also removed a couple of types that were no longer used)
Create a Flexbox component
Use FlexBox to compose Row and Stack components, with an additional spacing prop for equal spacing between children

Any and all feedback is wanted please!

[ ] Documentation
[ ] Tests
[ ] Experimental evidence (required for Masonry changes)
[ ] Accessibility checkup

@christianvuerings A few remaining questions/notes:

Should we remove more FlexBox props? I think it could probably be pared down more.
Any additional test cases I should cover? Or additional examples in the docs I should create?
Are the defaults I established in Row/Stack for alignItems and justifyContent good, or should we choose different ones? I picked the ones that feel the most "base case" to me, but very open to adjusting those if needed.


fix: add another way of mounting sim secrets

Description
This PR adds:

a way to use your own secret to log into the SignalFx
reloading pod when signalfxToken/signalfxRealm changes

Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x] Bug fix
[x] Refactor/improvement
[x] This change requires a documentation update

How Has This Been Tested?
Manual tests, integration tests
Checklist

[x] My commit message is conventional
[x] I have run pre-commit on all files before creating the PR
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have checked my code and corrected any misspellings

:tada: This PR is included in version 1.8.2-beta.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


1.14 - Village and Pillage

Updates the API from 1.13 to 1.14

Just, uh... Closing since this can be alive in 1.14 branch which will get merges between 1.13 etc.


create_node cause other nodes redrawed

we use create_node add large quntity  nodes dynamically, it happens every 200 ms, during this time, user can start to check the checkbox before the nodes, the problem is when the tree add the new nodes, looks like other nodes got redraw, it will impact user's selection if the node is redrawing.

Came here with same issue.
Just in my case, I'm not using checkboxes, but I have changeable content inside node text, which resets on create_node.

create_node is not intended for adding huge amounts of nodes to the tree - it is a "user-level" function - its purpose is to visualize a node, that the user is creating via an interaction with the tree. For all other purposes - you should take advantage of the loading functions - load_node \ load_nodes and core.data - you have many options there (AJAX, callback, etc).
v.4 will feature a more optimized redraw mechanism, but it won't be available until spring 2017.


chore(atomic): release v1

The commit messages should explain what is being done, also the Jiras description
https://coveord.atlassian.net/browse/KIT-903

We should remove the mustache and @types/mustache dependencies in Atomic's package.json file. We should also remove the //TODO section in the same file.


Version with Sylius 1.13 support

Hello
The latest version does not support sylius ^1.13 but the master branch does, so it is possible to use sylius ^1.13 and this plugin by requiring dev-master instead of a specific version but it is not ideal.
In the current state of the repository would it be possible to publish a version of master, or are there changes that need to be brought to master before ?

Ah - I'm happy to prepare a tag that allows Sylius 1.13. My project isn't there yet, so it's always slightly harder to test. Can you confirm it does work properly on Sylius 1.13 (using dev-master)?

We tested it and it works with Sylius 1.13, however we only use custom URL providers and don't use the default ones, so that is one thing we did not test

Thanks, @mbenoukaiss

I recall again the issue here, I wanted to make CI work on a range of Sylius / Symfony versions, but that took too much time and then paused it.
I will release the Composer allowance in a bit, and look at CI later again.

Thank you !


Suggestion: make "display MPAA rating" a toggle in Preferences / Issue: CinemaScore not displaying

For aesthetics' sake and personal preference, could MPAA rating become a toggle, able to be turned on and off?
Also: I'm on Firefox on a Mac, and CinemaScore isn't showing up for me when I toggle it on, regardless of the film.
Thank you in advance; this extension is great for all the extra information it provides at a glance.

I will add an option for the MPAA rating for the next release (soon, hopefully)
CinemaScore's API has not been working for a while. I've tried contacting them, but of course I am a nobody so I didn't hear back. I will try again, but for now it's out of my hands.

Toggle for MPAA/MPA added in latest version v.3.7.0