Minify reconstruction.meshed.py

reconstruction.meshed.py gets too large to be loaded in the browser viewer for large datasets, and minifying this mitigates this. See #126
I wasn't sure exactly how much to minify.  Setting indent to 0 rather than 4 gets most of the space saving gain, and you can still open the files easily in text editors, they just look less nice.  Setting indent to None removes new lines as well, and then you can't open the files easily in text editors and it would be very hard to human read.
For Lund I got size of 7.7mb for indent=4, 2.2mb for indent=0, 1.9mb for indent=None.
Since it's nice to have output human readable unless there is a good reason not to, I gave json_dump an argument to minify, and only activate for this one file at the moment.  But happy to change to minify all files/some other subset.

That's great @BrookRoberts!  It is good to have the option. We can always switch the default to True if we need so.
Thanks, merging.


Wildcard certificate generation with rfc2136: no such host

Do you want to request a feature or report a bug?
Bug
What did you do?
I am trying to get a wildcard certificate for my traefik system. I have my own DNS-Server (Bind) and I want to use the rfc2136 challenge. I added the required ENV variables from the provider table to my traefik container.

What did you expect to see?
The certificates being generated.
What did you see instead?
time="2018-10-31T10:55:16Z" level=error msg="Error obtaining certificate: acme: Error -> One or more domains had a problem:\n[mydomain.online] error presenting token: rfc2136: dial udp: lookup \"mydomain.online\": no such `host\n"
time="2018-10-31T10:55:16Z" level=error msg="Unable to obtain ACME certificate for domains \"*.mydomain.online,mydomain.online\" : unable to generate a certificate for the domains [*.mydomain.online mydomain.online]: acme: Error -> One or more domains had a problem:\n[mydomain.online] error presenting token: rfc2136: dial udp: lookup \"mydomain.online\": no such host\n"

Output of traefik version: (What version of Traefik are you using?)

Version:      v1.7.4
Codename:     maroilles
Go version:   go1.11.1
Built:        2018-10-30_10:44:30AM
OS/Arch:      linux/amd64

What is your environment & configuration (arguments, toml, provider, platform, ...)?
debug = true
defaultEntryPoints = ["https", "http"]

[entryPoints]
  [entryPoints.http]
  address = ":80"
    [entryPoints.http.redirect]
    entryPoint = "https"
  [entryPoints.https]
  address = ":443"
    [entryPoints.https.tls]

[acme]
  email =<EMAIL_ADDRESS>  storage = "acme.json"
  entryPoint = "https"
  acmeLogging=true
  onDemand = false
  [acme.dnsChallenge]
    provider = "rfc2136"
    delayBeforeCheck = 0
  [[acme.domains]]
    main = "*.mydomain.online"
    sans = ["mydomain.online"]

[docker]
  endpoint = "unix:///var/run/docker.sock"
  domain = "mydomain.online"
  exposedByDefault = false
  watch = true
  network = "traefik"

When I try to run lego on my Archlinux (lego-git r692.1151b4e-1) all works fine:
RFC2136_NAMESERVER="mydomain.online" RFC2136_TSIG_KEY="mydomain.online." RFC2136_TSIG_SECRET="removed" RFC2136_TSIG_ALGORITHM="hmac-sha512."

If applicable, please paste the log output in DEBUG level (--logLevel=DEBUG switch)
time="2018-10-31T10:55:09Z" level=debug msg="Building ACME client..."
time="2018-10-31T10:55:09Z" level=debug msg="https://acme-v02.api.letsencrypt.org/directory"
time="2018-10-31T10:55:09Z" level=info msg=Register...
time="2018-10-31T10:55:09Z" level=info msg="legolog: [INFO] acme: Registering account for<EMAIL_ADDRESS>time="2018-10-31T10:55:10Z" level=debug msg="Using DNS Challenge provider: rfc2136"
time="2018-10-31T10:55:10Z" level=info msg="legolog: [INFO] [*.mydomain.online, mydomain.online] acme: Obtaining bundled SAN certificate"
time="2018-10-31T10:55:10Z" level=info msg="legolog: [INFO] [*.mydomain.online] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz/RFqUiXsApBEM6ddV9Km9QJOEOCKDpnTCGVV8iWQ8gsU"
time="2018-10-31T10:55:10Z" level=info msg="legolog: [INFO] [mydomain.online] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz/bviddhzXA1QIV4sBK3IwubX4PHVNGw6ppiVJI9GoVEs"
time="2018-10-31T10:55:10Z" level=info msg="legolog: [INFO] [mydomain.online] acme: Could not find solver for: http-01"
time="2018-10-31T10:55:10Z" level=info msg="legolog: [INFO] [mydomain.online] acme: Preparing to solve DNS-01"
time="2018-10-31T10:55:10Z" level=info msg="legolog: [INFO] [mydomain.online] acme: Preparing to solve DNS-01"
time="2018-10-31T10:55:10Z" level=error msg="Error obtaining certificate retrying in 618.564794ms"
time="2018-10-31T10:55:11Z" level=info msg="legolog: [INFO] [*.mydomain.online, mydomain.online] acme: Obtaining bundled SAN certificate"
time="2018-10-31T10:55:11Z" level=info msg="legolog: [INFO] [*.mydomain.online] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz/bviddhzXA1QIV4sBK3IwubX4PHVNGw6ppiVJI9GoVEs"
time="2018-10-31T10:55:11Z" level=info msg="legolog: [INFO] [mydomain.online] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz/RFqUiXsApBEM6ddV9Km9QJOEOCKDpnTCGVV8iWQ8gsU"
time="2018-10-31T10:55:11Z" level=info msg="legolog: [INFO] [mydomain.online] acme: Could not find solver for: http-01"
time="2018-10-31T10:55:11Z" level=info msg="legolog: [INFO] [mydomain.online] acme: Preparing to solve DNS-01"
time="2018-10-31T10:55:11Z" level=info msg="legolog: [INFO] [mydomain.online] acme: Preparing to solve DNS-01"
time="2018-10-31T10:55:11Z" level=error msg="Error obtaining certificate retrying in 825.533254ms"
time="2018-10-31T10:55:12Z" level=info msg="legolog: [INFO] [*.mydomain.online, mydomain.online] acme: Obtaining bundled SAN certificate"
time="2018-10-31T10:55:16Z" level=info msg="legolog: [INFO] [*.mydomain.online] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz/bviddhzXA1QIV4sBK3IwubX4PHVNGw6ppiVJI9GoVEs"
time="2018-10-31T10:55:16Z" level=info msg="legolog: [INFO] [mydomain.online] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz/RFqUiXsApBEM6ddV9Km9QJOEOCKDpnTCGVV8iWQ8gsU"
time="2018-10-31T10:55:16Z" level=info msg="legolog: [INFO] [mydomain.online] acme: Could not find solver for: http-01"
time="2018-10-31T10:55:16Z" level=info msg="legolog: [INFO] [mydomain.online] acme: Preparing to solve DNS-01"
time="2018-10-31T10:55:16Z" level=info msg="legolog: [INFO] [mydomain.online] acme: Preparing to solve DNS-01"
time="2018-10-31T10:55:16Z" level=error msg="Error obtaining certificate: acme: Error -> One or more domains had a problem:\n[mydomain.online] error presenting token: rfc2136: dial udp: lookup \"mydomain.online\": no such host\n"
time="2018-10-31T10:55:16Z" level=error msg="Unable to obtain ACME certificate for domains \"*.mydomain.online,mydomain.online\" : unable to generate a certificate for the domains [*.mydomain.online mydomain.online]: acme: Error -> One or more domains had a problem:\n[mydomain.online] error presenting token: rfc2136: dial udp: lookup \"mydomain.online\": no such host\n"

I still have this issue. But the log looks now a bit different with Traefik v1.7.8:
The 4 lines in the middle are new.
level=info msg="legolog: [INFO] [mydomain.online] acme: Could not find solver for: http-01"
level=info msg="legolog: [INFO] [mydomain.online] acme: use dns-01 solver"
level=info msg="legolog: [INFO] [*.mydomain.online] acme: Preparing to solve DNS-01"
level=info msg="legolog: [INFO] [*.mydomain.online] acme: Cleaning DNS-01 challenge"
level=info msg="legolog: [WARN] [*.mydomain.online] acme: error cleaning up: rfc2136: failed to remove: could not find the start of authority for _acme-challenge.mydomain.online.: dial udp: lookup \"mydomain.online\": no such host "
level=info msg="legolog: [INFO] [mydomain.online] acme: Preparing to solve DNS-01"

This does not make sense to me because why should it clean DNS-01 challenge directly after preparing it. If I compare to standalone lego it should start with Trying to solve DNS-01 instead of cleaning.

lego 2.2.0 log on Archlinux
2019/02/11 22:19:02 [INFO] [mydomain.online] acme: Could not find solver for: http-01
2019/02/11 22:19:02 [INFO] [mydomain.online] acme: use dns-01 solver
2019/02/11 22:19:02 [INFO] [*.mydomain.online] acme: Preparing to solve DNS-01
2019/02/11 22:19:02 [INFO] [*.mydomain.online] acme: Trying to solve DNS-01
2019/02/11 22:19:02 [INFO] [*.mydomain.online] acme: Checking DNS record propagation using [<IP_ADDRESS>:53]
2019/02/11 22:19:02 [INFO] Wait for propagation [timeout: 1m0s, interval: 2s]
2019/02/11 22:19:02 [INFO] [*.mydomain.online] acme: Waiting for DNS record propagation.
2019/02/11 22:19:11 [INFO] [*.mydomain.online] The server validated our request
2019/02/11 22:19:11 [INFO] [*.mydomain.online] acme: Cleaning DNS-01 challenge
2019/02/11 22:19:11 [INFO] sequence: wait for 1m0s
2019/02/11 22:20:11 [INFO] [mydomain.online] acme: Preparing to solve DNS-01
2019/02/11 22:20:11 [INFO] [mydomain.online] acme: Trying to solve DNS-01
2019/02/11 22:20:11 [INFO] [mydomain.online] acme: Checking DNS record propagation using [<IP_ADDRESS>:53]
2019/02/11 22:20:11 [INFO] Wait for propagation [timeout: 1m0s, interval: 2s]
2019/02/11 22:20:11 [INFO] [mydomain.online] acme: Waiting for DNS record propagation.
2019/02/11 22:20:21 [INFO] [mydomain.online] The server validated our request
2019/02/11 22:20:21 [INFO] [mydomain.online] acme: Cleaning DNS-01 challenge
2019/02/11 22:20:21 [INFO] [mydomain.online, *.mydomain.online] acme: Validations succeeded; requesting certificates
2019/02/11 22:20:22 [INFO] [mydomain.online] Server responded with a certificate.

Full debug log
time="2019-02-11T20:56:38Z" level=debug msg="Building ACME client..."
time="2019-02-11T20:56:38Z" level=debug msg="https://acme-v02.api.letsencrypt.org/directory"
time="2019-02-11T20:56:38Z" level=info msg=Register...
time="2019-02-11T20:56:38Z" level=info msg="legolog: [INFO] acme: Registering account for<EMAIL_ADDRESS>time="2019-02-11T20:56:39Z" level=debug msg="Using DNS Challenge provider: rfc2136"
time="2019-02-11T20:56:39Z" level=info msg="legolog: [INFO] [*.mydomain.online, mydomain.online] acme: Obtaining bundled SAN certificate"
time="2019-02-11T20:56:39Z" level=info msg="legolog: [INFO] [*.mydomain.online] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz/YvRveVp3fi6uPg79OQ21FkBlUC8OOd8GlRYDeh-N_uI"
time="2019-02-11T20:56:39Z" level=info msg="legolog: [INFO] [mydomain.online] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz/qlNizNtXK2HuGuFgSfaBULSCtKt88tjmbMPcD8QN07Y"
time="2019-02-11T20:56:39Z" level=info msg="legolog: [INFO] [*.mydomain.online] acme: use dns-01 solver"
time="2019-02-11T20:56:39Z" level=info msg="legolog: [INFO] [mydomain.online] acme: Could not find solver for: tls-alpn-01"
time="2019-02-11T20:56:39Z" level=info msg="legolog: [INFO] [mydomain.online] acme: Could not find solver for: http-01"
time="2019-02-11T20:56:39Z" level=info msg="legolog: [INFO] [mydomain.online] acme: use dns-01 solver"
time="2019-02-11T20:56:39Z" level=info msg="legolog: [INFO] [*.mydomain.online] acme: Preparing to solve DNS-01"
time="2019-02-11T20:56:39Z" level=info msg="legolog: [INFO] [*.mydomain.online] acme: Cleaning DNS-01 challenge"
time="2019-02-11T20:56:39Z" level=info msg="legolog: [WARN] [*.mydomain.online] acme: error cleaning up: rfc2136: failed to remove: could not find the start of authority for _acme-challenge.mydomain.online.: dial udp: lookup \"mydomain.online\": no such host "
time="2019-02-11T20:56:39Z" level=info msg="legolog: [INFO] [mydomain.online] acme: Preparing to solve DNS-01"
time="2019-02-11T20:56:39Z" level=info msg="legolog: [INFO] [mydomain.online] acme: Cleaning DNS-01 challenge"
time="2019-02-11T20:56:39Z" level=error msg="Error obtaining certificate retrying in 440.457005ms"
time="2019-02-11T20:56:39Z" level=info msg="legolog: [WARN] [mydomain.online] acme: error cleaning up: rfc2136: failed to remove: could not find the start of authority for _acme-challenge.mydomain.online.: dial udp: lookup \"mydomain.online\": no such host "
time="2019-02-11T20:56:40Z" level=info msg="legolog: [INFO] [*.mydomain.online, mydomain.online] acme: Obtaining bundled SAN certificate"
time="2019-02-11T20:56:40Z" level=info msg="legolog: [INFO] [*.mydomain.online] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz/qlNizNtXK2HuGuFgSfaBULSCtKt88tjmbMPcD8QN07Y"
time="2019-02-11T20:56:40Z" level=info msg="legolog: [INFO] [mydomain.online] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz/YvRveVp3fi6uPg79OQ21FkBlUC8OOd8GlRYDeh-N_uI"
time="2019-02-11T20:56:40Z" level=info msg="legolog: [INFO] [mydomain.online] acme: Could not find solver for: tls-alpn-01"
time="2019-02-11T20:56:40Z" level=info msg="legolog: [INFO] [mydomain.online] acme: Could not find solver for: http-01"
time="2019-02-11T20:56:40Z" level=info msg="legolog: [INFO] [mydomain.online] acme: use dns-01 solver"
time="2019-02-11T20:56:40Z" level=info msg="legolog: [INFO] [*.mydomain.online] acme: use dns-01 solver"
time="2019-02-11T20:56:40Z" level=info msg="legolog: [INFO] [mydomain.online] acme: Preparing to solve DNS-01"
time="2019-02-11T20:56:40Z" level=info msg="legolog: [INFO] [mydomain.online] acme: Cleaning DNS-01 challenge"
time="2019-02-11T20:56:40Z" level=info msg="legolog: [WARN] [mydomain.online] acme: error cleaning up: rfc2136: failed to remove: could not find the start of authority for _acme-challenge.mydomain.online.: dial udp: lookup \"mydomain.online\": no such host "
time="2019-02-11T20:56:40Z" level=info msg="legolog: [INFO] [*.mydomain.online] acme: Preparing to solve DNS-01"
time="2019-02-11T20:56:40Z" level=info msg="legolog: [INFO] [*.mydomain.online] acme: Cleaning DNS-01 challenge"
time="2019-02-11T20:56:40Z" level=info msg="legolog: [WARN] [*.mydomain.online] acme: error cleaning up: rfc2136: failed to remove: could not find the start of authority for _acme-challenge.mydomain.online.: dial udp: lookup \"mydomain.online\": no such host "
time="2019-02-11T20:56:40Z" level=error msg="Error obtaining certificate retrying in 759.599408ms"
time="2019-02-11T20:56:41Z" level=info msg="legolog: [INFO] [*.mydomain.online, mydomain.online] acme: Obtaining bundled SAN certificate"
time="2019-02-11T20:56:42Z" level=info msg="legolog: [INFO] [*.mydomain.online] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz/qlNizNtXK2HuGuFgSfaBULSCtKt88tjmbMPcD8QN07Y"
time="2019-02-11T20:56:42Z" level=info msg="legolog: [INFO] [mydomain.online] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz/YvRveVp3fi6uPg79OQ21FkBlUC8OOd8GlRYDeh-N_uI"
time="2019-02-11T20:56:42Z" level=info msg="legolog: [INFO] [mydomain.online] acme: Could not find solver for: tls-alpn-01"
time="2019-02-11T20:56:42Z" level=info msg="legolog: [INFO] [mydomain.online] acme: Could not find solver for: http-01"
time="2019-02-11T20:56:42Z" level=info msg="legolog: [INFO] [mydomain.online] acme: use dns-01 solver"
time="2019-02-11T20:56:42Z" level=info msg="legolog: [INFO] [*.mydomain.online] acme: use dns-01 solver"
time="2019-02-11T20:56:42Z" level=info msg="legolog: [INFO] [mydomain.online] acme: Preparing to solve DNS-01"
time="2019-02-11T20:56:42Z" level=info msg="legolog: [INFO] [mydomain.online] acme: Cleaning DNS-01 challenge"
time="2019-02-11T20:56:42Z" level=info msg="legolog: [WARN] [mydomain.online] acme: error cleaning up: rfc2136: failed to remove: could not find the start of authority for _acme-challenge.mydomain.online.: dial udp: lookup \"mydomain.online\": no such host "
time="2019-02-11T20:56:42Z" level=info msg="legolog: [INFO] [*.mydomain.online] acme: Preparing to solve DNS-01"
time="2019-02-11T20:56:42Z" level=info msg="legolog: [INFO] [*.mydomain.online] acme: Cleaning DNS-01 challenge"
time="2019-02-11T20:56:42Z" level=info msg="legolog: [WARN] [*.mydomain.online] acme: error cleaning up: rfc2136: failed to remove: could not find the start of authority for _acme-challenge.mydomain.online.: dial udp: lookup \"mydomain.online\": no such host "
time="2019-02-11T20:56:42Z" level=error msg="Error obtaining certificate: acme: Error -> One or more domains had a problem:\n[*.mydomain.online] [*.mydomain.online] acme: error presenting token: rfc2136: failed to insert: could not find the start of authority for _acme-challenge.mydomain.online.: dial udp: lookup \"mydomain.online\": no such host\n[mydomain.online] [mydomain.online] acme: error presenting token: rfc2136: failed to insert: could not find the start of authority for _acme-challenge.mydomain.online.: dial udp: lookup \"mydomain.online\": no such host\n"
time="2019-02-11T20:56:42Z" level=error msg="Unable to obtain ACME certificate for domains \"*.mydomain.online,mydomain.online\" : unable to generate a certificate for the domains [*.mydomain.online mydomain.online]: acme: Error -> One or more domains had a problem:\n[*.mydomain.online] [*.mydomain.online] acme: error presenting token: rfc2136: failed to insert: could not find the start of authority for _acme-challenge.mydomain.online.: dial udp: lookup \"mydomain.online\": no such host\n[mydomain.online] [mydomain.online] acme: error presenting token: rfc2136: failed to insert: could not find the start of authority for _acme-challenge.mydomain.online.: dial udp: lookup \"mydomain.online\": no such host\n"

Are you using Traefik binary or Docker image?
The error is related to the nameserver: the SOA query failed.

I use the docker image.
When I do a SOA lookup on mydomain.online it says:
mydomain.online.	600	IN	SOA	ns1.mydomain.online. hostmaster.mydomain.online.<PHONE_NUMBER><PHONE_NUMBER> 600

I use the docker image.
When I do a SOA lookup on mydomain.online it says:
;; ANSWER SECTION:
mydomain.online.	214	IN	SOA	ns1.mydomain.online. hostmaster.mydomain.online.<PHONE_NUMBER><PHONE_NUMBER> 600

The SOA query fail (that's the error you see in the logs), it seems like a network error inside the container.
You need to check that there are no network errors or latency when you are inside Docker.

Could you try with Docker image of lego?
https://hub.docker.com/r/xenolf/lego/

You are right, I get the same error when I try Lego in Docker.
I have no idea why this is happening. It is also the same error if I try it with Docker on my Laptop

You are right, I get the same error when I try Lego in Docker.
I have no idea why this is happening. It is also the same error when I try Lego with Docker on my Laptop
@marzzzello I have the same issue, I have my own DNS-Server (Bind) It can update the lets encrypt cert using rfc2136 but I want to use the rfc2136 challenge in my traefik deployment, Did you get that solve? I want that traefik use my bind9 server as a provider.

@recarmona I run lego via a cronjob outside of docker as a workaround.

Removing the quotes in the docker env file helped. :rofl: :facepalm:


feature Add log and metric to improve the observability of journal batch

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Disable night mode is not working

EpubViewer.setConfig(
nightMode: false,
identifier: "test",
scrollDirection: EpubScrollDirection.ALLDIRECTIONS,
allowSharing: false,
enableTts: false);
on adding the config as nightMode: false the option for switch to night and day mode is not hiding

vocsy_epub_viewer: ^1.0.1
Update Latest Version

hi @kaushikgodhani after updating the version with ^1.0.1 still facing same issue

please explain more information about you issue to track issue

shared on your mail box<EMAIL_ADDRESS>


How to delete a workspace

Hi,
I've be click all menu's and options to see if there is a delete there is not. I would be nice to have a section on how to delete a workspace

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 11357d2a-97f6-c5d6-2a62-0d5cae1a1c3d
Version Independent ID: 51900b79-f5ed-25b8-ee89-9078129bdb15
Content: Create the new workspaces - Power BI - Power BI
Content Source: powerbi-docs/service-create-the-new-workspaces.md
Service: powerbi
Sub-service: powerbi-service
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Hi @YvonneArnoldus , thanks for reaching out to us. You have to be a workspace admin to delete a workspace. But try looking here: https://docs.microsoft.com/en-us/power-bi/service-delete#delete-a-workspace. Basically, in the left hand pane you hover over the name of the workspace, select the three dots you see, and then choose Workspace settings. At the bottom of the Workspace settings window that appears on the right, you will see a delete button, if you have the admin permissions. Let me know if this helped.

Thank you it is hidden well but I found it.


No resources found in knative-build namespace.

I followed the instructions till https://github.com/IBM/knative101/tree/master/workshop/exercise-2
knative-build does not have pods, it seems.
$ kubectl get pods --namespace knative-build
No resources found in knative-build namespace.

I used the cluster for another workshop before, so I wonder if I should clean it up somehow.

got a warning "memory pressure", so deleting the cluster


reactivate modern skins graphql

added https://webamp.org
const allowList = [
  /https:\/\/skins\.webamp\.org/,
  /https:\/\/api\.webamp\.org/,
  /https:\/\/webamp\.org/,
...

I'll need to deploy this to our server before it will take effect


Define custom component scan annotation

For specific kinds of tests, e.g. resource (REST API controller) tests, we always need a common subset of all available classes of a service. Currently we define ourselves a special annotation for this, e.g. @ResourceTest and we annotate every relevant class with it. This includes MVC configuration, JSON, logging, tracing, security,... you name it.
Our tests then usually do this:
@Configuration
@ComponentScan(basePackages = "org.example", useDefaultFilters = false,
        includeFilters = @Filter(ResourceTest.class))
@Import(ExampleResource.class)
public class TestConfiguration {

It would be nice to have a shorter version of the component scan annotation, i.e. something that disables default filters already and maybe defaults to the main package of the application (possible?):
@Configuration
@SelectiveScan(@Filter(ResourceTest.class))
@Import(ExampleResource.class)
public class TestConfiguration {

or even shorter:
@SelectiveScan(ResourceTest.class)

The first approach should be possible with this:
@ComponentScan(useDefaultFilter = false)
@Target(ElementType.TYPE)
@Retention(RetentionPolicy.RUNTIME)
public @interface SelectiveScan {
    @AliasFor(annotation = ComponentScan.class, attribute = "excludeFilters")
    Filter[] value() default {};
}

Turns out relying on the current package as a base package for the scan won't work in most non-trivial cases. Which means a usual call would look like this:
@SelectiveScan(package = "org.example", include = @Filter(ResourceTest.class))

It's shorter, but is it really worth the trouble?


Dependencies documentation

CAIRIS supports the ability to add asset/task dependencies between roles, but this isn't documented.

Superseded by Issue #113


Periodical support and jitter

Discussion continued from https://github.com/joshmn/caffeinate/issues/21#issuecomment-1511365139
This is an interesting use case I didn't quite fully think through!
I wonder if it would make sense to support something like:
drip :random_long_term, mailer: ClientMailer, periodical: true, at: :set_time

def set_time
  index = subscriber.mailings.sent.count
  subscriber.morning_delivery((index * 2).weeks.from_now + rand(0..2).days) + rand(0..180).minutes
end

I can't quite remember where/how periodical determines time. It's poorly documented (if that) because I haven't quite used it yet myself... hehe. It could also probably be reworked to hook into the callbacks as well if it's not already.
@jon-sully thoughts?

Under the hood periodical just clones the was-just-sent mailing and essentially calls
previous_mailing.send_at + params[:every] # e.g. 2.weeks

Which, is already pretty close to being jitter-able, but currently :every has to be a static, set value; it doesn't get re-computed on every clone. If it did, (if :every supported a Proc) then jitter could already be built in 🤔

Ah, and one other note about your API thought there ^ (a separate issue we should open) is that calling drip multiple times with the same action name only yields a single mailing based on the way drips are registered into the drip collection! So
drip :welcome, repeat: true, at: :set_time
drip :welcome, repeat: 5, at: :set_time
drip :welcome, repeat: :repeat?, at: :set_time

Would effectively ignore/skip the first two calls and only that third drip would actually register.

I think the ideal periodical API ought to support a dynamic every and an until arg, (optionally). IMO these should all work:
# these wouldn't be used together, they're just examples
drip :follow_up, every: 2.weeks, until: 10.weeks.from_now
drip :follow_up, every: -> { 2.weeks + rand(0..2).days + rand(0..100).minutes }, start: -> { recipient.next_appropriate_messageable_time }
drip :follow_up, every: -> { recipient.drip_frequency }, until: -> { recipient.out_of_drips? }

(Note that start: already supports a Proc)
There's enough difference here from the standard drip call that I wonder if periodical support ought to be broken out to a periodical_drip call rather than a drip call. Could even combine them.
drip :initial_follow_up, class_name: UserMailer, delay: 10.minutes
periodic_drip :new_post_round_up, class_name: UserMailer, every: -> { recipient.summary_email_frequency }

but I'm not sure if that's better or worse 😛

Ah, to my last idea, I think that's already the case. I didn't realize it before but I think that while the every: key is supported in the basic drip call, it won't actually work — you must use the periodical call to get the every: key working right (it's in the implementation of periodical that sends up the after_send callback that creates the next mailing). So in actuality, this is already the required API:
class SomeDripper
  drip :initial_follow_up, class_name: UserMailer, at: 10.minutes.from_now
  periodical :new_post_round_up, class_name: UserMailer, every: 10.days
end

That's a big note! 😅

Ah, and one other note about your API thought there ^ (a separate issue we should open) is that calling drip multiple times with the same action name only yields a single mailing based on the way drips are registered into the drip collection! So
drip :welcome, repeat: true, at: :set_time
drip :welcome, repeat: 5, at: :set_time
drip :welcome, repeat: :repeat?, at: :set_time

Would effectively ignore/skip the first two calls and only that third drip would actually register.

Ah, sorry — should clarify: that was just one example for welcome where you could "max repeat".
Do you have any instance where you have a mix of periodic and regular one-off drips in a Dripper?

Do you have any instance where you have a mix of periodic and regular one-off drips in a Dripper?

I don't know that my app has that at the moment, but it's definitely something I could see us doing

I'm starting down the track of supporting a Proc for the every: key + adding until: support, since I think that would cover 90% of the bases with much less work than some other ideas I've suggested, but I'm seeing some interesting logic in start: to begin with. Given the following code:
# lib/caffeinate/schedule_evaluator.rb

      if periodical?
        start = mailing.instance_exec(&options[:start])
        start += options[:every] if mailing.caffeinate_campaign_subscription.caffeinate_mailings.count.positive?
        date = start.from_now
      elsif options[:on]
        date = OptionEvaluator.new(options[:on], self, mailing).call
      else
        date = OptionEvaluator.new(options[:delay], self, mailing).call
        if date.respond_to?(:from_now)
          date = date.from_now
        end
      end

And the idea that I have a dripper setup like so:
periodical :round_up, every: 5.days, start: -> { 3.hours }

Let's say I subscribe the user to the dripper at 9am on 2/1/23. start = mailing.instance_exec(&options[:start]) will run and return the value of 3 hours. start += options... won't do anything because no mailings have been filed yet. And date = start.from_now will file the message for 12pm on the same day, 2/1/23. This makes sense as this is the first message.
But then we skip ahead to 12:05pm — the message is sent. The after_ hook runs and sets up the cloned/new/second periodical message. This time through the Schedule Evaluator though, start = mailing.instance_exec(&options[:start]) will still come back as 3.hours. start += options... will run and offset the next message by five days, and ultimately the second message will get filed for sending at 2/6/23 at 3:05pm.
I think that's unexpected? 🤔 I'd expect the start value to only offset the first message in the periodical sequence, not be an every-message delay factor, relative to its prior 🤔. Maybe this is better described as "start relative to prior message"? I'm not sure.
That said, technically, that means we can already introduce 'jitter' by using start: that way:
periodical :round_up, every: 14.days, start: -> { rand(0..2).days + rand(0..60).minutes }

In the above, we setup a "jitter amount" of 0-2 days + 0-1 hours. The first message will send after the random jitter amount, then every subsequent message will send (2 weeks + the jitter amount) later — which is the goal! 😆
Interesting.


[usecase-wrt] Add test for CSP to usecase

Impacted TCs num(approved): New 1, Update 0, Delete 0
Unit test Platform: Android
Android test result summary: Pass 1, Fail 0, Block 0

where is the samples/CSP/res ?


support limit property (post filter/sort)

refactor __limit to __chunkLimit
add limit property and observer
constrain instance generation by __chunkLimit AND limit
clone limit tests to ensure chunk and limit both work independently

Reference Issue
Fixes #4720

Please let me know if i'm barking up the wrong tree with this solution.

Closing this, pending discussion.


/dynamic-resolution is broken

The dynamic resolution feature is broken. Resizing windows results in unforeseen resize behavior. Especially at switching from fullscreen to smaller window and back.
One behavior are the drawing artifacts coming from resizing window from fullscreen to small resolution. So the screen content of fullscreen will stay in background
Other behavior is resizing from small resolution to fullscreen or other direction several times. Sometimes it will result in  a behavior FreeRDP will resize back to previous size without interaction

Start with xfreerdp /u:user /p:password /d:DO /dynamic-resolution /v:hostname
Switch to fullscreen and back several times
Resizing window manually
Steps 2 and 3 will result in described errors after some tries

Expected behavior
Resize should stay as choosen.
No screen artefacts should be visible. I have just removed some internal icons
Screenshots
This shows the behavior after resize from fullscreen to smaller resolution

Version of FreeRDP
Latest master : Commit e90184cc593d722eaabbad8a7e53b252c18462c2
Command line used
xfreerdp /u:user /p:password /d:DO /dynamic-resolution /v:hostname
output of /buildconfig
buildconfig.log
OS version connecting to
Windows 10 Enterprise 64Bit
Version 1703
Build 15063.1088
xfreerdp_screenartifact.log
xfreerdp_wrongresize.log

`
Desktop (please complete the following information):

OS: Linux

Could you check if this is indeed a client error?
I've seen such a screenshot once and the reason was that the server side graphics driver was in a faulty state.
(we might have to tune the frequency of resolution updates if that is the case)

If I disable the the timer in xf_disp.c  and so I always call the  xf_disp_sendResize then I would get a much better behavior and display will be not distorted. The only problems then are :

the slow performance
if I cause a lot of resizing and then do fullscreen this event will come not as the last resize event

I fear the order of the x-events ( fullscreen and resize) is not garantueed.

and if you remove the timer it may also crash win2k12 (the server itself) when we send too many resizes.

I see one bug now.
All events within the timeout will be blocked. And the problem is that all events after the last accepted resize events will be not done.  E.g. Resizing the the window several times and then press fullscreen --- very often the fullscreen will be ignored because it will be within the ignore timeout

@andicheesi yes I was not completely happy with the way I've managed resizes (so that we don't get too many of them). I guess I should have a look again on this.

I just did a rough prototype where I changed 3 things:

When I get a ConfigureNotify I do a XCheckTypedWindowEvent for this windows and just send out only the last one
I disabled all checks for timer and disabled all "delayed resize" code
I just sleep for 200ms after each xf_disp_sendResize if I am within the RESIZE_MIN_DELAY
Then everything works fine

I wanted to hear about your opinion about such approach. And I have no clue what is "delayed resize" implementation is good for.
The problem with my solution is I will sleep always after getting a resize notification.


Add condition for CodeModuleVersion and ProcessModuleConfig

Description
First Conditions related PR, review it in a way that following Conditions should follow the same pattern.
Adds 2 Conditions:

CodeModuleVersion, which is for the version-reconciler

A bit of a hacky solution because of the version reconciler structure, but it works
Only serves as more info, not used directly for anything

ProcessModuleConfig which is for the process-module-config-secret reconciler

Secret creation/update related, so I moved these Conditions into a utils package.
⚠ Replaces the timestamp for the Dynatrace API request limit feature

"Basic" rule: A "transition" has (True => False, False=>True) for the timestamp to change, that is why there is an Empty Reason, so this transition happens, also its a nice failsafe

How can this be tested?
Deploy a dynakube that uses the CodeModules.

Check the status for the Conditions

Checklist

[x] Unit tests have been updated/added
[x] PR is labeled accordingly with a single label
[x] I have read and understood the contribution guidelines

Codecov Report
Attention: Patch coverage is 53.17460% with 59 lines in your changes are missing coverage. Please review.

Project coverage is 67.12%. Comparing base (0d0225e) to head (f724fa1).
Report is 6 commits behind head on main.

Files
Patch %
Lines

pkg/api/v1alpha1/dynakube/zz_generated.deepcopy.go
0.00%
27 Missing :warning:

...s/dynakube/processmoduleconfigsecret/reconciler.go
68.00%
11 Missing and 5 partials :warning:

pkg/api/v1beta1/dynakube/zz_generated.deepcopy.go
0.00%
13 Missing :warning:

...g/api/v1alpha1/activegate/zz_generated.deepcopy.go
0.00%
2 Missing :warning:

pkg/api/v1beta1/dynakube/properties.go
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2816      +/-   ##
==========================================
+ Coverage   66.97%   67.12%   +0.15%
==========================================
  Files         249      250       +1
  Lines       13624    13693      +69
==========================================
+ Hits         9125     9192      +67
- Misses       3695     3697       +2
  Partials      804      804

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


Allow Cross-Origin Requests

A few of us are interested in developing complimentary (and just regularly extending) sites. In order for those people to do this, cross-origin requests need to be allowed (These are requests that DO NOT come from the domain the server is being hosted on).
This would be really appreciated.
Harrison

Done! Sorry for the delay in implementing


Implement GET /bulk-data/:id

Closes #47.

Codecov Report

Merging #80 (ad7d868) into main (510241b) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #80   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           48        48
  Lines          937       951   +14
=========================================
+ Hits           937       951   +14

Impacted Files
Coverage Δ

lib/src/scryfall_api_client.dart
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Passing extra arguments after "help (verb)" causes an InvalidOperationException

Using CommandLineParser <IP_ADDRESS> beta, I can cause an InvalidOperationException by simply running "my-cmd.exe help verb foo" instead of "my-cmd.exe help verb". "my-cmd.exe help verb" produces the expected help text, but "my-cmd.exe help verb foo" produces the following exception:
Unhandled Exception: System.InvalidOperationException: Sequence contains more than one element
   at System.Linq.Enumerable.SingleOrDefault[TSource](IEnumerable`1 source)
   at CommandLine.Core.InstanceChooser.<>c__DisplayClass0_0.<Choose>b__0()
   at CommandLine.Core.InstanceChooser.Choose(Func`3 tokenizer, IEnumerable`1 types, IEnumerable`1 arguments, StringComparer nameComparer, CultureInfo parsingCulture, IEnumerable`1 nonFatalErrors)
   at CommandLine.Parser.<>c__DisplayClass13_0.<ParseArguments>b__0()
   at CommandLine.Parser.MakeParserResult[T](Func`1 parseFunc, ParserSettings settings)
   at TryOutCommandLineParser.Program.Main(String[] args) in c:\src\try\TryOutCommandLineParser\Program.cs:line 17

Running "my-cmd.exe verb foo --help" works, sort of (I don't like the "Option 'help' is unknown) error, but I can live with it. But I'm pretty sure that users will at one point try replacing "my-cmd.exe verb foo bar -v" with "my-cmd.exe help verb foo bar -v" to get help usage, and I'd like this to be handled. So when the "help" verb is invoked, I'd like it to ignore any further arguments, but not throw an exception if they are present.

@rmunn, thanks for detailed reporting, I'll try fix both issues  (the exception and help unknown).
I'll update you here.
Thanks, again!

When you invoke your app with:
my-cmd.exe verb foo --help

--help is enumerated as an option because the canonical help request, requires you to put "--help" as first argument. In this case the help screen is showed not because you added "--help" but because the command line syntax rules are not respected.
I need reason a little more on this... The main issue anyway is fixed, in seconds I'll merge to master...

Version 2.0.239-beta fixes the issue (just released to NuGet), if this works can you please close the issue?
Thanks, @rmunn.

Regarding --help, the logic I've come to expect from a verb-using command-line program like git is the following:

Scan all the arguments (up to the -- argument, if present) for a -h or --help argument.
If it was present, display appropriate help for the verb (or, if no verb was present, for the program as a whole).
If no -h or --help was present, process the verb's normal arguments.

For example:
$ git pull -v --ff-only --help
usage: [...]

Whereas:
$ git pull -v --ff-only --bad-argument
error: unknown option `bad-argument'
usage: [...]

But the --help argument, and how to treat it, should probably be discussed in a separate issue.

I've tested version 2.0.239-beta, and it works the way I want now (barring the "Option 'help' is unknown" error). This issue is fixed.

@rmunn, after some reasoning I'm agree with you that listing help as unknown option is senseless.
This is now fixed in version 2.0.241-beta on master and released to NuGet.
Anyway an eventual -h will not be removed because, this is not a built-in command for requesting help.
If you're interested in internals:
this is the test -> https://github.com/gsscoder/commandline/blob/master/tests/CommandLine.Tests/Unit/ParserTests.cs#L542
this is the fix -> https://github.com/gsscoder/commandline/blob/master/src/CommandLine/ErrorExtensions.cs#L23
Bye! :)


Added log2, loge function

also added log base e (default) function

Thanks for contributing @DeepeshnotCool .


Detect IT_IDENTITY_CARD

Identifying and safeguarding PII from IT identity cards, such as employee or contractor IDs, is crucial for several reasons. It ensures privacy protection by preventing unauthorized access or misuse of sensitive data like names, photos, and contact details. Detecting and securing IT identity card PII also helps mitigate security risks related to data breaches, identity theft, and insider threats. Additionally, it demonstrates a commitment to data security and industry standards, contributing to a positive organizational reputation. Implementing effective measures to protect IT identity card PII is essential for safeguarding both individual privacy and organizational integrity.
To learn more about identifying this PII, visit this webpage.
This detection method will identify a number in the format 000-00-0000. For testing purposes, the number 900-00-1234 is used, as it cannot be a real IT identity card number per the guidelines. No attempt is made to determine the validity of IT identity card numbers.

Looks good

I agree with your points on the importance of safeguarding Personally Identifiable Information (PII) from IT identity cards. Your emphasis on privacy protection, mitigating security risks, and demonstrating commitment to data security and compliance is crucial. It highlights the significance of prioritizing the identification and safeguarding of IT identity card PII for both individual privacy and organizational integrity.


Change annotation managed-by for Keptn namespace

In testing out the new 0.8.0-alpha release, concerns about the name of the label/annotation for the namespace arose.
The name of the annotation/label, which is managed-by, is misleading. The reason is that the recommendation of Kubernetes (see:
https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/#labels) says:

app.kubernetes.io/managed-by : The tool being used to manage the operation of an application

In the namespace in which Keptn is installed, no application is deployed.
To-be-discussed:

What is a proper name for the label?

For which deployments is this the case?
Keptn itself is installed using the following labels:
app.kubernetes.io/component=mongodb app.kubernetes.io/instance=keptn app.kubernetes.io/managed-by=Helmapp.kubernetes.io/name=mongodb app.kubernetes.io/part-of=keptn-keptn app.kubernetes.io/version=1 helm.sh/chart=mongodb-0.1.0

app.kubernetes.io/component=control-plane app.kubernetes.io/instance=keptn app.kubernetes.io/managed-by=Helm app.kubernetes.io/name=bridge app.kubernetes.io/part-of=keptn-keptn app.kubernetes.io/version=0.8.0-alphahelm.sh/chart=control-plane-0.1.0

And in my opinion this is exactly what it should be.

For which deployments is this the case?
Keptn itself is installed using the following labels:
app.kubernetes.io/component=mongodb app.kubernetes.io/instance=keptn app.kubernetes.io/managed-by=Helmapp.kubernetes.io/name=mongodb app.kubernetes.io/part-of=keptn-keptn app.kubernetes.io/version=1 helm.sh/chart=mongodb-0.1.0

app.kubernetes.io/component=control-plane app.kubernetes.io/instance=keptn app.kubernetes.io/managed-by=Helm app.kubernetes.io/name=bridge app.kubernetes.io/part-of=keptn-keptn app.kubernetes.io/version=0.8.0-alphahelm.sh/chart=control-plane-0.1.0

And in my opinion this is exactly what it should be.

I think I need to clarify, it is not about the namespaces we create for a deployed application, but rather for the namespace we create for a Keptn deployment. The corresponding col is here: https://github.com/keptn/keptn/blob/master/cli/cmd/install.go#L215
There we set: managed-by: keptn for the Keptn namespace and this is not right.

I think I need to clarify, it is not about the namespaces we create for a deployed application, but rather for the namespace we create for a Keptn deployment. The corresponding col is here: https://github.com/keptn/keptn/blob/master/cli/cmd/install.go#L215
There we set: managed-by: keptn for the Keptn namespace and this is not right.

Okay, I see. Though I still think that's okay, because we create the namespace using the keptn cli.
But let's discuss this topic, I can see two discussion points here:

Why are we using keptn.sh/managed-by instead of app.kubernetes.io/managed-by?
Should we set managed-by to keptn when we install it via the keptn CLI?

Okay, I see. Though I still think that's okay, because we create the namespace using the keptn cli.
But let's discuss this topic, I can see two discussion points here:

Why are we using keptn.sh/managed-by instead of app.kubernetes.io/managed-by?
Should we set managed-by to keptn when we install it via the keptn CLI?

I think I was always a little bit blinded because I thought that we are using the label app.kubernetes.io/managed-by but in fact we are setting keptn.sh/managed-by. @christian-kreuzberger-dtx thanks for the hint!

I think that we can leave the label as it is since we are using the prefix keptn.sh and not app.kubernetes.io

For me, two additional points arise:

How can we set the flag, when installing Keptn via Helm chart? (see: https://keptn.sh/docs/0.8.x/operate/advanced_install_options/#advanced-install-options-install-keptn-using-the-helm-chart)

When possible, should we move the label management from the CLI to the Helm chart (to cover both install options)?

We need documentation for that feature.

I think I was always a little bit blinded because I thought that we are using the label app.kubernetes.io/managed-by but in fact we are setting keptn.sh/managed-by. @christian-kreuzberger-dtx thanks for the hint!

I think that we can leave the label as it is since we are using the prefix keptn.sh and not app.kubernetes.io

For me, two additional points arise:

How can we set the flag, when installing Keptn via Helm chart? (see: https://keptn.sh/docs/0.8.x/operate/advanced_install_options/#advanced-install-options-install-keptn-using-the-helm-chart)

When possible, should we move the label management from the CLI to the Helm chart (to cover both install options)?

We need documentation for that feature.


ARROW-5463: [Rust] Add AsRef trait for Buffer.

This is useful when using Buffer as typed slices. @sunchao @nevi-me @andygrove Please help to review when you get a chance.

@nevi-me  I also tried and couldn't figure out a fancy way to it, so just used macro.

I think the problem is the u8 case which will cause a conflict. As an alternative, we can instead implement a function similar to the existing data, but returns an slice of T instead of u8:
pub fn typed_data<T: ArrowNativeType>(&self) -> &[T] { ... }

This will save from the macros and in terms of usage it should be similar.

@sunchao There are two conflict cases.

AsRef<[u8]> will add another From implementation for Buffer, since we already have impl<T: AsRef<[u8]>> From<T> for Buffer implementation.
I don't how to implement AsRef<[bool]> for Buffer since the implementation logic is not trivial.

@liurenjie1024 In that case maybe you can change the above code to:
pub fn typed_data<T: ArrowNativeType + num::Num>(&self) -> &[T] { ... }

The problem against macros is that whenever someone adds a new type he/she needs to know all the places to modify to cover the places that the type is used.

@sunchao It helps with bool type. But if we need to add support for u8, we need to remove this piece of code:
/// Creating a `Buffer` instance by copying the memory from a `AsRef<[u8]>` into a newly
/// allocated memory region.
impl<T: AsRef<[u8]>> From<T> for Buffer {
    fn from(p: T) -> Self {
        // allocate aligned memory buffer
        let slice = p.as_ref();
        let len = slice.len() * mem::size_of::<u8>();
        let capacity = bit_util::round_upto_multiple_of_64(len);
        let buffer = memory::allocate_aligned(capacity);
        unsafe {
            memory::memcpy(buffer, slice.as_ptr(), len);
        }
        Buffer::from_raw_parts(buffer, len)
    }
}

Hmm.. why is that? this only happens if you implement AsRef[u8] for Buffer right? if you use the typed_data approach you should not need it.

Yes, you are right. Changed function name to typed _data.


SSD Information

I removed the SSD today and confirmed the model number, so I share the information here.
TS128GMTS800
https://us.transcend-info.com/products/Product_detail.aspx?no=644

This issue will be closed since there were no actions for a while. You can reopen this issue to show this issue to the users whenever. Thanks.


module cava: Unknown module: cava

so I copy-pasted the cava config from the wiki to my config file and when I start waybar, it says that the module is not found. I am using hyprland with waybar-hyprland-git from aur

seems an aur package problem or am I wrong?
https://aur.archlinux.org/cgit/aur.git/log/?h=waybar-hyprland-git

It might depend on whether aur contain particular waybar package. Cava was released a couple of days ago.

don't know why they did it, but I will just install the non-git version. Also does the default waybar arch repository works without any problems in hyprland? Thanks!

seems an aur package problem or am I wrong?
https://aur.archlinux.org/cgit/aur.git/log/?h=waybar-hyprland-git
*edit: last edit message is: Remove cava module

Thank you, at least now the reason is clear for me. I'll check next week how to handle the issue properly

I tried to build, but I was getting these errors. I installed Cava, but I still kept getting the error:
44:16: ERROR: C++ shared or static library 'cava' not found.
I had to modify line 345 in the meson.build file:
cava = compiler.find_library('cava',
                             required: false)

distro opensuse - hyprland.

for waybar-hyprland-git version at aur arch linux, during installation/compile, you can see a line mentioned that cava been disable.
Not sure related to this or not.

for waybar-hyprland-git version at aur arch linux, during installation/compile, you can see a line mentioned that cava been disable.
Not sure related to this or not.

This log exact means waybar was built without cava module support

why did they left cava out though? and also the waybar package from official repo does not work fully. Like the workspaces module.

@XxRiKxX if your WM is under hyprland and your config is using wlr/workspaces than you need waybar-hyprland-git version to make the workspaces work, but if your workspace is under sway (not with wlroots), than you need only waybar-git. i think they separate it for cover up wlroot and others, instead that they can combine into one, to have a mode setting for wlroot or others.


Error please remove it

Error please remove it

Only dynamic binaries are supported by psyscall.

I can mmap memory to process , but how can I insert data to that memory?

Open a file descriptor to a file containing the data, and then read from
it into the address returned by mmap. Alternatively, you could use the
fildes parameter of mmap to directly map the data from the file to the
memory without reading (see the man pages for more information).


[PackageLoading] Make sure JSON-encoded rule keys are stable

JSONEncoder does not guarantee stable element ordering unless we specifically ask for the keys to be sorted.
This gets especially important as we plan to enable per-instance hash seeding for Dictionary, which breaks llbuild's rule keys on Linux without this change.

@swift-ci please test

@swift-ci smoke test

@swift-ci test with toolchain

/Users/buildnode/jenkins/workspace/swift-package-manager-with-xcode-PR-osx/swiftpm/Sources/SPMLLBuild/llbuild.swift:201:34: error: 'sortedKeys' is only available on OS X 10.13 or newer

Oops, yeah, this needs an availability check on macOS. (Sorting is only critical for Linux, where JSONEncoder uses native Swift dictionaries.)

Yep. And sorry for stomping on your commit 😅

@swift-ci test with toolchain

@swift-ci smoke test

@swift-ci smoke test

@swift-ci test with toolchain


Wrong reported App version

Please remove this template if you only have a question or do not want to create a new issue.
Describe what you wanted to do
Check MobilePass with Exodus and get a version number
https://github.com/Exodus-Privacy/exodus/issues/449
Describe what you expected
a proper number like 8.4.5
Describe what actually happened
The tool reported @7F0C0011 , which looks like a memory offset
[INFO    ] androguard.axml: Styles Offset given, but styleCount is zero. This is not a problem but could indicate packers.
[WARNING ] androguard.axml: Name 'android:versionName' starts with 'android:' prefix! The Manifest seems to be broken? Removing prefix.
[WARNING ] androguard.axml: Name 'android:UNKNOWN_SYSTEM_ATTRIBUTE_01010572' starts with 'android:' prefix! The Manifest seems to be broken? Removing prefix.
[WARNING ] androguard.axml: Name 'android:UNKNOWN_SYSTEM_ATTRIBUTE_01010573' starts with 'android:' prefix! The Manifest seems to be broken? Removing prefix.
[WARNING ] androguard.axml: Name 'android:minSdkVersion' starts with 'android:' prefix! The Manifest seems to be broken? Removing prefix.
[WARNING ] androguard.axml: Name 'android:targetSdkVersion' starts with 'android:' prefix! The Manifest seems to be broken? Removing prefix.
[WARNING ] androguard.axml: Name 'android:name' starts with 'android:' prefix! The Manifest seems to be broken? Removing prefix.
[WARNING ] androguard.axml: Name 'android:name' starts with 'android:' prefix! The Manifest seems to be broken? Removing prefix.
[WARNING ] androguard.axml: Name 'android:theme' starts with 'android:' prefix! The Manifest seems to be broken? Removing prefix.
[WARNING ] androguard.axml: Name 'android:label' starts with 'android:' prefix! The Manifest seems to be broken? Removing prefix.
[WARNING ] androguard.axml: Name 'android:allowClearUserData' starts with 'android:' prefix! The Manifest seems to be broken? Removing prefix.
[WARNING ] androguard.axml: Name 'android:contentDescription' starts with 'android:' prefix! The Manifest seems to be broken? Removing prefix.
[WARNING ] androguard.axml: Name 'android:allowBackup' starts with 'android:' prefix! The Manifest seems to be broken? Removing prefix.
[WARNING ] androguard.axml: Name 'android:UNKNOWN_SYSTEM_ATTRIBUTE_0101057a' starts with 'android:' prefix! The Manifest seems to be broken? Removing prefix.
[WARNING ] androguard.axml: Name 'android:label' starts with 'android:' prefix! The Manifest seems to be broken? Removing prefix.
[WARNING ] androguard.axml: Name 'android:taskAffinity' starts with 'android:' prefix! The Manifest seems to be broken? Removing prefix.
[WARNING ] androguard.axml: Name 'android:launchMode' starts with 'android:' prefix! The Manifest seems to be broken? Removing prefix.
[WARNING ] androguard.axml: Name 'android:screenOrientation' starts with 'android:' prefix! The Manifest seems to be broken? Removing prefix.
[WARNING ] androguard.axml: Name 'android:configChanges' starts with 'android:' prefix! The Manifest seems to be broken? Removing prefix.
[WARNING ] androguard.apk: XML Seems to be packed, operations on the AndroidManifest.xml might fail.
[WARNING ] androguard.apk: Failed to get the attribute 'name' on tag 'uses-permission' with namespace. But found the same attribute without namespace!
[WARNING ] androguard.apk: Failed to get the attribute 'name' on tag 'uses-permission' with namespace. But found the same attribute without namespace!
<manifest xmlns:android="http://schemas.android.com/apk/res/android" android:versionCode="84500" versionName="@7F0C0011" UNKNOWN_SYSTEM_ATTRIBUTE_01010572="28" UNKNOWN_SYSTEM_ATTRIBUTE_01010573="9" package="securecomputing.devices.android.controller" platformBuildVersionCode="84500" platformBuildVersionName="@7F0C0011">
  <uses-sdk minSdkVersion="21" targetSdkVersion="28"/>
  <uses-permission name="android.permission.INTERNET"/>
  <uses-permission name="android.permission.ACCESS_WIFI_STATE"/>
  <application theme="@7F0D0006" label="@7F0C00AF" android:icon="@7F070068" allowClearUserData="false" contentDescription="" allowBackup="false" UNKNOWN_SYSTEM_ATTRIBUTE_0101057a="android.support.v4.app.CoreComponentFactory">
    <activity label="@7F0C00AF" android:name=".AndroidToken" taskAffinity="" launchMode="2" screenOrientation="1" configChanges="0x00000020">
      <intent-filter>
        <action android:name="android.intent.action.MAIN"/>
        <category android:name="android.intent.category.LAUNCHER"/>
      </intent-filter>
      <intent-filter>
        <action android:name="com.safenet.mpsdk.core.AUTO_ENROLL_ACTION"/>
        <category android:name="android.intent.category.DEFAULT"/>
        <category android:name="android.intent.category.BROWSABLE"/>
      </intent-filter>
    </activity>
    <activity android:name="com.safenet.tests.TestActivity"/>
  </application>
</manifest>

The application seems protected with dexguard which might confuse androguards parsing.

Another affected app:
https://reports.exodus-privacy.eu.org/reports/com.umouse.clear/latest

Given that the issue is old and the project is substantially different nowadays, I will be closing this.
Please feel free to reopen it in case it still stands.


No notifictions

So i have been using winotify from my other pc and i was getting the notification pop up but on this one i run the same script and it doent work. Firts i thought it was the icon that was making it not show up but it wasnt i even used the test.py(modified the code) to try and make a notification to show up? Is it that i was using python 1.9 and now i am using python 1.10( the problem is that i dont get any errors the code just works)...

Hey! I have thesame issue!
The code runs without errors, but no notification is shown on my PC.
I have windows 10 and use python 3.11.
Let me please know how I could solve this issue please.


Add funding.yml file & Consider adding github sponsors

funding.yml file
https://docs.github.com/en/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository
github sponsors
https://github.blog/2020-03-24-getting-started-with-github-sponsors/
In another project IMMORTAN under btcontract a FUNDING.yml exists in:
https://github.com/btcontract/IMMORTAN/blob/master/.github/FUNDING.yml
which point to FUNDING.md file:
https://github.com/btcontract/immortan/blob/master/FUNDING.md

Thanks, added.


[Marker.io] Text under “our solutions” is not shown properly

Steps to reproduce:go to our solutions section on home page
2) notice the text below the heading
Actual result: not shown properly
Expected result: it should be displayed properly

Reported by: Vinod<EMAIL_ADDRESS>- Contact via Marker.io
Source URL: https://proav-stg.webflow.io/
Issue details: Open in Marker.io
Device typemobileBrowserSafari 17.6Screen Size375 x 812OSiOS 17.6.1Viewport Size375 x 710Pixel Ratio@3x

stil seeing same behaviour:
https://drive.google.com/file/d/1M-Af3DjQcd-Kl-klkUWRfhpWlSixoSl0/view?usp=sharing

🤖 Marker.io bot - This issue was marked as ✅ Resolved in Marker.io


Shutdown using voice

Script Title - Shutdown using voice
Brief - This method can automate your work of shut downing your computer.
I'll be using the combination of os module + Speech recognition + win32.client module which can automate this method.
Instructions

Create a new folder for your script and file/folder name should be appropriate.
Create a README.md in your folder for program Instructions
add requirements.txt if needed

Programming Language

[x] Python

Happy Coding

Kindly assign this isseu to me @pawangeek


Symmetrization layer

I am doing that for single species case, after confirming it works fine I will then do that for multi-specices case.
A minor issue is that currently RepLieGroups is using P4ML so there is a circular dependency issue. However in RepLieGroups/src we do not need P4ML and we should remove that from deps.

I agree. RepLieGroups only needs to be assured that the basis transforms as expected.
However, I'm not convinced that P4ML should depend on RepLieGroups. For now can we please work in a separate "drafting repo"? I will create that now.

Just done a first draft on this and I will wait for the 2023MitacsDV  to repo to set up before I push the code.

We should think about how we can do the synmetrisation layer for real SH. Probably not hard, probably can be reduced to specifying the CG for rSH which should be a trivial linear transformation.

@CheukHinHoJerry  -- I talked to @zhanglw0521 about creating another package called EquivariantLux.jl in which we make available utility functions to build equivariant models from RepLie and P4ML. We can also develop some example models in that package. It could be a sort of intermediate layer between RepLie, P4ML and ACE.

Sorry, I should have mentioned this earlier - so now we have an elementary version in this regard, which might be served as a starting point.

Ah yes - thanks for noticing this.

I believe this is already implemented - I will close this now.
Ref https://github.com/ACEsuit/RepLieGroups.jl/pull/7#issue-1768116439


k8s.ReplaceNamespacedCustomObject() extension isn't working

The k8s.ReplaceNamespacedCustomObject() extension method is failing with UnprocessableEntity errors.  This is probably happening with the cluster custom objects as well.  This is impacting our Upsert related methods when the resource already exists.  The base k8s.ReplaceNamespacedCustomObject() isn't documented anymore for .NET and is barely documented for other languages.
Perhaps we can use one of the patch related methods instead.

Here's a simple repro (an existing cluster is required):
using k8s;
using k8s.Models;

using Neon.Kube;
using Neon.Kube.K8s;
using Neon.Kube.Resources.Istio;

namespace test
{
    internal class Program
    {
        static async Task Main(string[] args)
        {
            var k8s       = new Kubernetes(KubernetesClientConfiguration.BuildDefaultConfig());
            var telemetry = new V1Telemetry()
            {
                Metadata = new V1ObjectMeta()
                {
                    Name              = "upsert-test",
                    NamespaceProperty = "default"
                },
                Spec = new V1TelemetrySpec()
                {
                    Tracing = new List<Tracing>()
                    {
                        new Tracing()
                        {
                            Providers = new List<TracingProvider>()
                            {
                                new TracingProvider()
                                {
                                    Name = "opencensus"
                                }
                            },
                            RandomSamplingPercentage = 1.0
                        }
                    }
                }
            };

            // This creates the resource.

            await k8s.CustomObjects.UpsertNamespacedCustomObjectAsync<V1Telemetry>(telemetry, name: telemetry.Name(), namespaceParameter: telemetry.Namespace());

            // This should update the resource, but fails.

            telemetry.Spec.Tracing[0].RandomSamplingPercentage = 100.0;

            await k8s.CustomObjects.UpsertNamespacedCustomObjectAsync<V1Telemetry>(telemetry, name: telemetry.Name(), namespaceParameter: telemetry.Namespace());
        }
    }
}

...and here's the error:
Operation returned an invalid status code 'UnprocessableEntity', response body {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"telemetries.telemetry.istio.io \"upsert-test\" is invalid: metadata.resourceVersion: Invalid value: 0x0: must be specified for an update","reason":"Invalid","details":{"name":"upsert-test","group":"telemetry.istio.io","kind":"telemetries","causes":[{"reason":"FieldValueInvalid","message":"Invalid value: 0x0: must be specified for an update","field":"metadata.resourceVersion"}]},

Looks like we need to pass the original resource's resourceVersion.  I spent a couple minutes playing around with that but then set it aside to look  at later.
I noticed this when single-stepping through the V1Telemetry creation in namespaces code during cluster setup, when I quite debugging after one resource was created and then restarted setup and I expected that it would just update the first existing resource and then finish creating the other resources.  But the upsert call failed on that existing resource.
I've worked around this by using CreateNamespacedCustomObjectAsync() and protecting each with an InvokeIdempotentAsync().


Scanner is not scanning CVE-2021-4104  related files

Hi Support
It is noticed that scanner is not scanning CVE-2021-4104 files on the server.
log4j versions on 1.X
Regards
Sunil S

@sunilsrinivas93 Use --scan-log4j1 switch. :D

hello,
I just noticed that .jar files that are vulnerable to CVE-2021-4104 seem to have a problem when exporting out to .csv or .json.
I run log4j-scan.exe with the parameter --fix --Report-csv --report-json. The console shows that there are findings and that they have been fixed. This is also written to the log file.
If I then run the scan again to check whether everything is OK, the console shows that the files were found but have already been mitigated. However, a different status is written in the report, namely "Potentially vulnerable". This only happens with files that are affected by CVE-2021-4101. All other files are correctly written in the log with "Mitigated".
I can reproduce this on any computer with this CVE.
Thanks for all your work!
Regards, Markus

@markus8899 Oh.. I reproduced bug. Would you open new issue?

done


windows drive casing causes - TypeError: Cannot read properties of undefined (reading 'test')

Describe the bug
When adding vitest to an existing project & all tests are failing with TypeError: Cannot read properties of undefined (reading 'test').
Looks like this is due to my windows cmd line having a lower-case drive letter.   Tests successfully run in powershell, & vs code console.
Adding a vitest.config.ts file w/ a normalized root property worked around the issue.
export default mergeConfig(
  viteConfig,
  defineConfig({
    test: {
      environment: 'jsdom',
      exclude: [...configDefaults.exclude, 'e2e/*']

      // including this line, it works, commenting out, it fails
      // , root: fileURLToPath(new URL('./', import.meta.url))
    }
  })
)

Below is the stack from the test exception getting thrown - note the varying drive letters:
TypeError: Cannot read properties of undefined (reading 'test')
    at Object.<anonymous> (file:///c:/github/vue/vitest-repro/node_modules/@vitest/runner/dist/index.js:256:22)
    at Module.chain2 (file:///c:/github/vue/vitest-repro/node_modules/@vitest/runner/dist/chunk-tasks.js:98:17)
    at c:\github\vue\vitest-repro\src\components\__tests__\HelloWorld.spec.ts:7:1
    at VitestExecutor.runModule (file:///C:/github/vue/vitest-repro/node_modules/vite-node/dist/client.mjs:362:5)
    at VitestExecutor.directRequest (file:///C:/github/vue/vitest-repro/node_modules/vite-node/dist/client.mjs:346:5)
    at VitestExecutor.cachedRequest (file:///C:/github/vue/vitest-repro/node_modules/vite-node/dist/client.mjs:189:14)
    at VitestExecutor.executeId (file:///C:/github/vue/vitest-repro/node_modules/vite-node/dist/client.mjs:165:12)
    at collectTests (file:///C:/github/vue/vitest-repro/node_modules/@vitest/runner/dist/index.js:578:7)
    at startTests (file:///C:/github/vue/vitest-repro/node_modules/@vitest/runner/dist/index.js:908:17)
    at file:///C:/github/vue/vitest-repro/node_modules/vitest/dist/chunks/runtime-runBaseTests.9RbsHRbU.js:114:7

Reproduction
Using the default example on StackBlitz
Download to a local folder on windows - i.e. C:\repro\vitest-repro.
From a windows cmd line (not powershell or vs code console), make sure your drive prompt is lower-case.
cd c:\repro\vitest-repro

Run tests
npm run test

 DEV  v1.3.1 c:/work/vite-repro

 ❯ test/suite.test.ts (0)
 ❯ test/basic.test.ts (0)

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Suites 2 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

 FAIL  test/basic.test.ts [ test/basic.test.ts ]
TypeError: Cannot read properties of undefined (reading 'test')
 ❯ test/basic.test.ts:6:1

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/2]⎯

 FAIL  test/suite.test.ts [ test/suite.test.ts ]
Error: No test suite found in file C:/work/vite-repro/test/suite.test.ts
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[2/2]⎯

 Test Files  2 failed (2)
      Tests  no tests
   Start at  11:53:59
   Duration  847ms (transform 107ms, setup 0ms, collect 208ms, tests 0ms, environment 1ms, prepare 475ms)

If you add a vitest.config.ts w/ the root property as above, it resolves
System Info
System:
    OS: Windows 11 10.0.22621
    CPU: (8) x64 Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
    Memory: 4.73 GB / 15.92 GB
  Binaries:
    Node: 18.13.0 - C:\Program Files\nodejs\node.EXE
    npm: 8.10.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 121.0.6167.185
    Edge: Chromium (121.0.2277.128)
    Internet Explorer: 11.0.22621.1

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Note that while adding root: fileURLToPath(new URL('./', import.meta.url))) does fix the issue for a vitest run, it does not fix the issue for a plain vitest. Any updated tests that cause a watch to trigger will run a cached version of the test file and not the updated one.

I've also lost several hours because of this.
In my case, my beforeAll(...) threw a
TypeError: Cannot read properties of undefined (reading 'on')
in a seemingly random way (it worked inside a VsCode cmd terminal, but not in my plain cmd terminal)
It took me a while (i had to dig inside beforeAll source to guess that to discover that getCurrentSuite() was returning undefined, and then that it had to do with the case of my Windows drive letter.
It think that it would be good practice to FAIL FAST here: I've check that the callers to getCurrentSuite() never expect to get undefined, hence, it should inside throw a descriptive error (and perhaps, if inside windows, warn about drive letter in lowercase?).


Highlight all the connections associated with a given cortical area

In Circuit Builder, when a single cortical area is selected, highlight all the associated efferent links in a different color.

resolved


Configure large file workflow on QA

Configure the FileSystem in browse everything so large files can be uploaded on QA

https://github.com/psu-stewardship/scholarsphere/blob/develop/config/sample/browse_everything_providers.yml#L3
We should match what is being done in production and staging

I've updated QA to point to /dlt/scholarsphere/upload_qa/browse_everything_file_system with the same file size limitations as staging and production.


drafting "slacklist" function, fixing various typos along the way

i forgot to quote some stuff, and im bad at bash
i'm cool with giving write access for this branch out, since im basically going to be doing a bunch of trial and error this out until i get something that works
this will fix #28
im trying to list everything after "FILE LIST:" as shown here

i cant handle basic githubbing, so i'm re-forking. oops, i guess.


Declare Python 3.11 support

Describe your changes
The Python versions badge in the README is missing Python 3.11, and I believe this is what's needed to add it.
Testing performed
None whatsoever 😄

This also needs a release.


Image has some scrollbars around it that fades away after a few seconds

Every time the screen loads, the svg image has some kind of scrollbars that fades away after 1 or 2 seconds. I't doesn matter if the width and height is fixed or auto.
<Image style={{ width: 125, height: 125 }} source={require('./img/user.svg')} />
Link to github project: https://github.com/lucaspinheirogit/PratoPratico
I'm using the latest version (2.0.3) with react-native-webview linked and working normally

A workaround solution i found is to directly change the source code to import {WebView} from 'react-native' instead of 'react-native-webview'

Can you add overflow: hidden; to the html/body tag style and that would make sure scrollbar is not shown.


podman & buildah errors on redhat systems

An error of this sort will pop up on rhel8/centos8/centosstream because podman and buildah are installed and try to replace docker. Making sure those packages are uninstalled on a server will prevent this from happening:
TASK [geerlingguy.docker : Ensure containerd.io is installed.] ************************
fatal: [<IP_ADDRESS>]: FAILED! => {"changed": false, "failures": [], "msg": "Depsolve Error occured: \n Problem: problem with installed package buildah-1.15.1-2.module+el8.3.0+8221+97165c3f.x86_64\n  - package buildah-1.15.1-2.module+el8.3.0+8221+97165c3f.x86_64 requires runc >= 1.0.0-26, but none of the providers can be installed\n  - package buildah-1.5-3.gite94b4f9.module+el8+2769+577ad176.x86_64 requires runc >= 1.0.0-26, but none of the providers can be installed\n  - package buildah-1.5-3.gite94b4f9.module+el8.0.0+2958+4e823551.x86_64 requires runc >= 1.0.0-26, but none of the providers can be installed\n  - package buildah-1.5-3.gite94b4f9.module+el8.0.0+4017+bbba319f.x86_64 requires runc >= 1.0.0-26, but none of the providers can be installed\n  - package buildah-1.5-3.gite94b4f9.module+el8.0.0.z+3525+56c076c3.x86_64 requires runc >= 1.0.0-26, but none of the providers can be installed\n  - package buildah-1.9.0-5.module+el8.1.0+4240+893c1ab8.x86_64 requires runc >= 1.0.0-26, but none of the providers can be installed\n  - package buildah-1.11.6-7.module+el8.2.0+5856+b8046c6d.x86_64 requires runc >= 1.0.0-26, but none of the providers can be installed\n  - package buildah-1.11.6-6.module+el8.1.1+5865+cc793d95.x86_64 requires runc >= 1.0.0-26, but none of the providers can be installed\n  - package buildah-1.11.6-4.module+el8.1.1+5259+bcdd613a.x86_64 requires runc >= 1.0.0-26, but none of the providers can be installed\n  - package buildah-1.14.9-1.module+el8.2.1+6689+748e6520.x86_64 requires runc >= 1.0.0-26, but none of the providers can be installed\n  - package buildah-1.11.6-8.module+el8.2.0+6368+cf16aa14.x86_64 requires runc >= 1.0.0-26, but none of the providers can be installed\n  - package containerd.io-1.4.3-3.1.el8.x86_64 conflicts with runc provided by runc-1.0.0-68.rc92.module+el8.3.0+8221+97165c3f.x86_64\n  - package containerd.io-1.4.3-3.1.el8.x86_64 obsoletes runc provided by runc-1.0.0-68.rc92.module+el8.3.0+8221+97165c3f.x86_64\n  - package containerd.io-1.4.3-3.1.el8.x86_64 conflicts with runc provided by runc-1.0.0-54.rc5.dev.git2abd837.module+el8+2769+577ad176.x86_64\n  - package containerd.io-1.4.3-3.1.el8.x86_64 obsoletes runc provided by runc-1.0.0-54.rc5.dev.git2abd837.module+el8+2769+577ad176.x86_64\n  - package containerd.io-1.4.3-3.1.el8.x86_64 conflicts with runc provided by runc-1.0.0-55.rc5.dev.git2abd837.module+el8.0.0+3049+59fd2bba.x86_64\n  - package containerd.io-1.4.3-3.1.el8.x86_64 obsoletes runc provided by runc-1.0.0-55.rc5.dev.git2abd837.module+el8.0.0+3049+59fd2bba.x86_64\n  - package containerd.io-1.4.3-3.1.el8.x86_64 conflicts with runc provided by runc-1.0.0-55.rc5.dev.git2abd837.module+el8.0.0.z+3525+56c076c3.x86_64\n  - package containerd.io-1.4.3-3.1.el8.x86_64 obsoletes runc provided by runc-1.0.0-55.rc5.dev.git2abd837.module+el8.0.0.z+3525+56c076c3.x86_64\n  - package containerd.io-1.4.3-3.1.el8.x86_64 conflicts with runc provided by runc-1.0.0-56.rc8.dev.git425e105.module+el8.0.0+4017+bbba319f.x86_64\n  - package containerd.io-1.4.3-3.1.el8.x86_64 obsoletes runc provided by runc-1.0.0-56.rc8.dev.git425e105.module+el8.0.0+4017+bbba319f.x86_64\n  - package containerd.io-1.4.3-3.1.el8.x86_64 conflicts with runc provided by runc-1.0.0-60.rc8.module+el8.1.0+4081+b29780af.x86_64\n  - package containerd.io-1.4.3-3.1.el8.x86_64 obsoletes runc provided by runc-1.0.0-60.rc8.module+el8.1.0+4081+b29780af.x86_64\n  - package containerd.io-1.4.3-3.1.el8.x86_64 conflicts with runc provided by runc-1.0.0-61.rc8.module+el8.1.0+4873+4a24e241.x86_64\n  - package containerd.io-1.4.3-3.1.el8.x86_64 obsoletes runc provided by runc-1.0.0-61.rc8.module+el8.1.0+4873+4a24e241.x86_64\n  - package containerd.io-1.4.3-3.1.el8.x86_64 conflicts with runc provided by runc-1.0.0-64.rc9.module+el8.1.1+5259+bcdd613a.x86_64\n  - package containerd.io-1.4.3-3.1.el8.x86_64 obsoletes runc provided by runc-1.0.0-64.rc9.module+el8.1.1+5259+bcdd613a.x86_64\n  - package containerd.io-1.4.3-3.1.el8.x86_64 conflicts with runc provided by runc-1.0.0-65.rc10.module+el8.2.0+5762+aaee29fb.x86_64\n  - package containerd.io-1.4.3-3.1.el8.x86_64 obsoletes runc provided by runc-1.0.0-65.rc10.module+el8.2.0+5762+aaee29fb.x86_64\n  - package containerd.io-1.4.3-3.1.el8.x86_64 conflicts with runc provided by runc-1.0.0-65.rc10.module+el8.2.0+6368+cf16aa14.x86_64\n  - package containerd.io-1.4.3-3.1.el8.x86_64 obsoletes runc provided by runc-1.0.0-65.rc10.module+el8.2.0+6368+cf16aa14.x86_64\n  - package containerd.io-1.4.3-3.1.el8.x86_64 conflicts with runc provided by runc-1.0.0-66.rc10.module+el8.2.1+6465+1a51e8b6.x86_64\n  - package containerd.io-1.4.3-3.1.el8.x86_64 obsoletes runc provided by runc-1.0.0-66.rc10.module+el8.2.1+6465+1a51e8b6.x86_64\n  - cannot install the best candidate for the job\n  - package runc-1.0.0-55.rc5.dev.git2abd837.module+el8+2794+c81bb0a1.x86_64 is filtered out by modular filtering\n  - package runc-1.0.0-55.rc5.dev.git2abd837.module+el8.0.0+2956+30df4692.x86_64 is filtered out by modular filtering\n  - package runc-1.0.0-55.rc5.dev.git2abd837.module+el8.0.0+4014+8662b6b2.x86_64 is filtered out by modular filtering\n  - package runc-1.0.0-55.rc5.dev.git2abd837.module+el8.1.0+3468+011f0ab0.x86_64 is filtered out by modular filtering\n  - package runc-1.0.0-56.rc5.dev.git2abd837.module+el8.1.0+4908+72a45cef.x86_64 is filtered out by modular filtering\n  - package runc-1.0.0-64.rc10.module+el8.2.0+5728+ac3aae00.x86_64 is filtered out by modular filtering\n  - package runc-1.0.0-56.rc5.dev.git2abd837.module+el8.2.0+6370+6fb6c8ca.x86_64 is filtered out by modular filtering\n  - package runc-1.0.0-64.rc10.module+el8.2.0+6369+1f4293b4.x86_64 is filtered out by modular filtering\n  - package runc-1.0.0-64.rc10.module+el8.3.0+8233+627fbb78.x86_64 is filtered out by modular filtering\n  - package runc-1.0.0-56.rc5.dev.git2abd837.module+el8.3.0+8236+8e428216.x86_64 is filtered out by modular filtering\n  - package runc-1.0.0-64.rc10.module+el8.3.0+8377+eff33c85.x86_64 is filtered out by modular filtering", "rc": 1, "results"

I'm not seeing that error on the CI runs though—it seems like podman/buildah aren't in the default minimal server installs of RHEL8 or CentOS8 at this time.

I'm not seeing that error on the CI runs though—it seems like podman/buildah aren't in the default minimal server installs of RHEL8 or CentOS8 at this time.

I'm not seeing that error on the CI runs though—it seems like podman/buildah aren't in the default minimal server installs of RHEL8 or CentOS8 at this time.

Yeah i cant comment on that, this is using something like normal/general server w/ only guest agent as additional software.

I'm not seeing that error on the CI runs though—it seems like podman/buildah aren't in the default minimal server installs of RHEL8 or CentOS8 at this time.

Yeah i cant comment on that, this is using something like normal/general server w/ only guest agent as additional software.

I'm not seeing that error on the CI runs though—it seems like podman/buildah aren't in the default minimal server installs of RHEL8 or CentOS8 at this time.

Yeah i cant comment on that, this is using something like normal/general server w/ only guest agent as additional software.

Indeed, saw the same thing when using this role today.
Initially complained about podman -
TASK [geerlingguy.docker : Ensure containerd.io is installed.] *************************************************************************************************************************************************************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "failures": [], "msg": "Depsolve Error occured: \n Problem: problem with installed package podman-2.0.5-5.module_el8.3.0+512+b3b58dca.x86_64\n  - package podman-2.0.5-5.module_el8.3.0+512+b3b58dca.x86_64 requires runc >= 1.0.0-57, but none of the providers can be installed\n  - package containerd.io-1.4.3-3.1.el8.x86_64 conflicts with runc provided by runc-1.0.0-68.rc92.module_el8.3.0+475+c50ce30b.x86_64\n  - package containerd.io-1.4.3-3.1.el8.x86_64 obsoletes runc provided by runc-1.0.0-68.rc92.module_el8.3.0+475+c50ce30b.x86_64\n  - cannot install the best candidate for the job\n  - package runc-1.0.0-64.rc10.module_el8.3.0+479+69e2ae26.x86_64 is filtered out by modular filtering", "rc": 1, "results": []}
Removed that and then it complained about buildah -
TASK [geerlingguy.docker : Ensure containerd.io is installed.] *************************************************************************************************************************************************************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "failures": [], "msg": "Depsolve Error occured: \n Problem: problem with installed package buildah-1.15.1-2.module_el8.3.0+475+c50ce30b.x86_64\n  - package buildah-1.15.1-2.module_el8.3.0+475+c50ce30b.x86_64 requires runc >= 1.0.0-26, but none of the providers can be installed\n  - package containerd.io-1.4.3-3.1.el8.x86_64 conflicts with runc provided by runc-1.0.0-68.rc92.module_el8.3.0+475+c50ce30b.x86_64\n  - package containerd.io-1.4.3-3.1.el8.x86_64 obsoletes runc provided by runc-1.0.0-68.rc92.module_el8.3.0+475+c50ce30b.x86_64\n  - cannot install the best candidate for the job\n  - package runc-1.0.0-56.rc5.dev.git2abd837.module_el8.3.0+569+1bada2e4.x86_64 is filtered out by modular filtering\n  - package runc-1.0.0-64.rc10.module_el8.3.0+479+69e2ae26.x86_64 is filtered out by modular filtering", "rc": 1, "results": []}
Removed buildah and it progressed past this. Got stuck somewhere else but thats a different problem.

I'm not seeing that error on the CI runs though—it seems like podman/buildah aren't in the default minimal server installs of RHEL8 or CentOS8 at this time.

Yeah i cant comment on that, this is using something like normal/general server w/ only guest agent as additional software.

Indeed, saw the same thing when using this role today.
Initially complained about podman -
TASK [geerlingguy.docker : Ensure containerd.io is installed.] *************************************************************************************************************************************************************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "failures": [], "msg": "Depsolve Error occured: \n Problem: problem with installed package podman-2.0.5-5.module_el8.3.0+512+b3b58dca.x86_64\n  - package podman-2.0.5-5.module_el8.3.0+512+b3b58dca.x86_64 requires runc >= 1.0.0-57, but none of the providers can be installed\n  - package containerd.io-1.4.3-3.1.el8.x86_64 conflicts with runc provided by runc-1.0.0-68.rc92.module_el8.3.0+475+c50ce30b.x86_64\n  - package containerd.io-1.4.3-3.1.el8.x86_64 obsoletes runc provided by runc-1.0.0-68.rc92.module_el8.3.0+475+c50ce30b.x86_64\n  - cannot install the best candidate for the job\n  - package runc-1.0.0-64.rc10.module_el8.3.0+479+69e2ae26.x86_64 is filtered out by modular filtering", "rc": 1, "results": []}
Removed that and then it complained about buildah -
TASK [geerlingguy.docker : Ensure containerd.io is installed.] *************************************************************************************************************************************************************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "failures": [], "msg": "Depsolve Error occured: \n Problem: problem with installed package buildah-1.15.1-2.module_el8.3.0+475+c50ce30b.x86_64\n  - package buildah-1.15.1-2.module_el8.3.0+475+c50ce30b.x86_64 requires runc >= 1.0.0-26, but none of the providers can be installed\n  - package containerd.io-1.4.3-3.1.el8.x86_64 conflicts with runc provided by runc-1.0.0-68.rc92.module_el8.3.0+475+c50ce30b.x86_64\n  - package containerd.io-1.4.3-3.1.el8.x86_64 obsoletes runc provided by runc-1.0.0-68.rc92.module_el8.3.0+475+c50ce30b.x86_64\n  - cannot install the best candidate for the job\n  - package runc-1.0.0-56.rc5.dev.git2abd837.module_el8.3.0+569+1bada2e4.x86_64 is filtered out by modular filtering\n  - package runc-1.0.0-64.rc10.module_el8.3.0+479+69e2ae26.x86_64 is filtered out by modular filtering", "rc": 1, "results": []}
Removed buildah and it progressed past this. Got stuck somewhere else but thats a different problem.


[ISSUE #4072] fix totalPollingNum count error

What is the purpose of the change
Fix #4072
Brief changelog
XX
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage increased (+0.06%) to 47.278% when pulling 39d5a593f6eb80af6b5a00a00ffe7f2377150bcc on Git-Yang:5.0.0-beta-pop-fix1 into 52482d4e0d610f45c139dc35b8d2d8784452331e on apache:5.0.0-beta.

@ayanamist Can you help to check?

@ayanamist Can you help to check?


Typescript's CFA is not working when using redirect() returned from createSharedPathnamesNavigation

Description
When I use next/navigation's redirect, the type of userId is successfully narrowed to string because if userId is undefined it calls redirect() whose return type is never.

But when I use redirect from createSharedPathnamesNavigation, it's not working.

This is because of typescript's designed limitation. https://github.com/microsoft/TypeScript/issues/36753
So I'm using redirect like this on my project. I re-declared redirect as a function not a const.
// navigation.ts
const navigation = createSharedPathnamesNavigation({
  locales,
  localePrefix,
});

export const { Link, usePathname, useRouter: useIntlRouter } = navigation;

export function redirect(...params: Parameters<typeof navigation.redirect>): never {
  return navigation.redirect(...params);
}

I think it should work by default when using next-intl's redirect as next's default redirect does.
Mandatory reproduction URL (CodeSandbox or GitHub repository)
https://codesandbox.io/p/devbox/next-intl-bug-template-app-forked-fp6873
Reproduction description
Steps to reproduce:

Open reproduction
Click on the file ./src/app/[locale]/intl/page.tsx
See error: Type 'string | undefined' is not assignable to type 'string'. Type 'undefined' is not assignable to type 'string'. on userId2
But when you check default/page.tsx, intl2/page.tsx, it works fine,

Expected behaviour
The type error should not be occurred like other files.

That's really strange, thanks for the report. Do you have an idea why this works for next/navigation and how this can be fixed in next-intl?
I've added a reproduction in #824.

https://github.com/amannn/next-intl/pull/149#issuecomment-1753211290
The weirdest issue and the weirdest solution!

maybe because Typescript's skipLibCheck: true?

You can refer to this issue. https://github.com/microsoft/TypeScript/issues/36753
For example, if there is a function test1() which returns never, typescript says 'unreachable code detected' after calling test1(). (console.log line is grayed out)
// Function declaration
function test1(): never {
  throw new Error('test');
}

function main1() {
  test1();
  console.log('test');
}

But if you declare a function using arrow function like test2(), the warning is not showing because typescript's control flow analysis is not working. But it's intended behavior because test2() does not satisfy the third condition here. https://github.com/microsoft/TypeScript/pull/32695#issue-476462173

A function call is analyzed as an assertion call or never-returning call when

the call occurs as a top-level expression statement, and
the call specifies a single identifier or a dotted sequence of identifiers for the function name, and
each identifier in the function name references an entity with an explicit type, and
the function name resolves to a function type with an asserts return type or an explicit never return type annotation.

An entity is considered to have an explicit type when it is declared as a function, method, class or namespace, or as a variable, parameter or property with an explicit type annotation. (This particular rule exists so that control flow analysis of potential assertion calls doesn't circularly trigger further analysis.)

// Arrow function
const test2 = (): never => {
  throw new Error('test');
};

function main2() {
  test2();
  console.log('test');
}

But CFA works when you explicit type like test3(). The reason is this (excerpt from quote above)

An entity is considered to have an explicit type when it is declared as a function, method, class or namespace, or as a variable, parameter or property with an explicit type annotation.

// Arrow function with type annotation
const test3: () => never = () => {
  throw new Error('test');
};

function main3() {
  test3();
  console.log('test');
}

@A7med3bdulBaset Your solution here https://github.com/amannn/next-intl/pull/149#issuecomment-1753211290 looks good! The lines on my example can be changed like this.
// From this
export function redirect(...params: Parameters<typeof navigation.redirect>): never {
  return navigation.redirect(...params);
}

// To this
export const redirect: typeof navigation.redirect = navigation.redirect;

@amannn Also, the reason why next/navigation works is next's redirect is declared like this. It's a function not an arrow function.
export declare function redirect(url: string, type?: RedirectType): never;

I've already tried to fix and create PR for it, but I couldn't find any simple solution 🥲
The original redirect is declared as a function declaration but we use redirect returned from createLocalizedPathnamesNavigation so it's not anymore function declaration maybe.
export const {Link, redirect, usePathname, useRouter} =
  createLocalizedPathnamesNavigation({
    locales,
    localePrefix,
    pathnames
  });

At most, it's a Typescript bug

Seems like this gets reported time and time again on the TypeScript issue tracker:

https://github.com/microsoft/TypeScript/issues/59138
https://github.com/microsoft/TypeScript/issues/58582
https://github.com/microsoft/TypeScript/issues/56049

I guess the best for the time being is the approach mentioned by @AhmedBaset and @MinSeungHyun from above:
const {redirect: _redirect} = createNavigation(routing);

// Help TypeScript detect unreachable code
export const redirect: typeof _redirect = _redirect;


QUOTED_IDENTIFIER error

As of today I've been getting the following error:
Msg 1934, Level 16, State 1, Procedure sp_generate_merge, Line 764 [Batch Start Line 1] SELECT failed because the following SET options have incorrect settings: 'QUOTED_IDENTIFIER'. Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations.
The error itself seems to arise from line 778 in the file here, and MIGHT be an issue with FOR XML PATH or AS XML  (somebody on the internet mentioned XML as the culprit).
 BEGIN
  SET @output += 'VALUES' + CAST((SELECT @b + val FROM @tab ORDER BY ID FOR XML PATH('')) AS XML).value('.', 'NVARCHAR(MAX)');
 END

The initial problem was on SQL 2016.  Order of troubleshooting:

ran flavors of SET QUOTED_IDENTIFIER ON, against the DB and as an ALTER DATABASE statement
dropped and re-created the database
tried running sp_generate_merge against another database, which failed
installed current version of sp_generate_merge
stopped and started services, rebooted, etc.
repaired SQL 2016
uninstalled SQL 2016
uninstalled SSMS
installed SQL 2019
installed SSMS
verified problem still exists
someone mentioned XML, so tried asking for text exec sp_generate_merge @table_name = 'Employees', @results_to_text = 1
installed current version of sp_generate_mergeinto the database itself, with no luck.

At this point, I'm thinking that something in the OS must have changed, or something's left behind with the uninstall / install of 2016 / 2019.  If it's a change or a patch, I don't have any idea when it happened, because I usually only run sp_generate_merge on a production server, to bring data back for test / dev purposes.
I would love it if someone told me this was my fault ... and how to fix it?
OS: Windows 10 Pro, Version	10.0.19044 Build 19044
MSSQL Versions: 2016 and 2019
SSMS Version: 15.0.18410.0
Possibly affecting this is that a junior engineer's test database is one which was scripted from their development machine and then run on their sandbox.  I've listed the ALTER DATABASE statements from that script below.