Silent refesh of the session fails sometimes

Hi!
I have seen this work, but most of the time it fails. I am trying to silently refresh the user login.
I have set:
  silent_redirect_uri: 'http://localhost:8080/silent-renew.html'
  automaticSilentRenew: true

and my silent-renew page looks like:
<!DOCTYPE html>
<html>
  <head>
    <title>Silent Renew Token</title>
  </head>
  <body>
    hallo
    <script src="js/oidc-client.js"></script>
    <script>
      var mgr = new UserManager();
      mgr.signinSilentCallback();
    </script>
  </body>
</html>

For testing purposes, I am triggering the refresh manually by calling:
userManager.signinSilent().then(user => {
      console.log('Did a silent renew: ' + JSON.stringify(user));
});

and sometimes I have seen this work. But most of the times, it fails:
MetadataService.getMetadata: json received oidc-client.min.js:1:1876
MetadataService.getMetadataProperty: metadata recieved oidc-client.min.js:1:1876
OidcClient.createSigninRequest: Received authorization endpoint https://<login-server>/connect/authorize oidc-client.min.js:1:1876
SigninState.toStorageString oidc-client.min.js:1:1876
WebStorageStateStore.set 9197fdd111554ca0a46e0af7d4ce80f3 oidc-client.min.js:1:1876
UserManager._signinStart: got signin request oidc-client.min.js:1:1876
IFrameWindow.navigate: Using timeout of: 10000 oidc-client.min.js:1:1876
GET https://<login-server>/connect/authorize?client_id=c488c904-a1f4-4273-ba94-1d79a6ef081d&redirect_uri=http%3A%2F%2Flocalhost%3A8080%2Fsilent-renew.html&response_type=id_token%20token&scope=openid%20role%20profile%20email%20colleagues%20licnapi%20haumyliebherr&state=9197fdd111554ca0a46e0af7d4ce80f3&nonce=f1541d6818ff4e22a3755066936ba422&prompt=none&id_token_hint=eyJhbGciOiJSUzI1NiIsImtpZCI6IkMyQ0I2MDYwMjhFQkQ5Q0U4Mjk3NDNFRDE4MkM2NkE3MTkyODI0MzYiLCJ0eXAiOiJKV1QiLCJ4NXQiOiJ3c3RnWUNqcjJjNkNsMFB0R0N4bXB4a29KRFkifQ.eyJuYmYiOjE1Njk1ODkxODQsImV4cCI6MTU2OTU4OTQ4NCwiaXNzIjoiaHR0cHM6Ly9sb2dpbnRzdC5saWViaGVyci5jb20iLCJhdWQiOiJjNDg4Yzkwci5leHRyYW5ldCIsImF1dGhfdGltZSI6MTU2OTU4OTE4NCwiaWRwIjoibG9jYWwiLCJhbXIiOlsicHdkIl19.TO9vz21zWLz4uaLJAktI2KOXAC4TUSrIJ_2XT2zGFWtHPvN1jp1BJCml7kGvjSp5t-ViziHkvBQdLFbowjrKYYYLuP1c13wmQU5EdIGWu5_aACNces9Kmz1OE1O2WWPRYeFPbgmhuXvV3cwfbhVJBNE3Gs6kQHMUqM9GOUKiPVOwGUomjfuk_u0ohGoAIBOwATjJNfEZiwaxAlEA8MEuADVM2gWs4JImGwE_1ZdRPEQhVHTwaTzVIChZb3r7yJF-D1n1sc0q6xe_eOVPVjX2LODKKv2M1Hoke5aqDWvECgd0PHit1E9tRd9a0zfppx4ZOM1ie29EcjGA2XGvSDfVwA
[HTTP/1.1 302 Found 40ms]

GET http://localhost:8080/silent-renew.html#error=login_required&state=9197fdd111554ca0a46e0af7d4ce80f3
[HTTP/1.1 304 Not Modified 3ms]

GET http://localhost:8080/js/oidc-client.js
[HTTP/1.1 304 Not Modified 2ms]

unreachable code after return statement
UserInfoService.js:112:12
IFrameWindow.message oidc-client.min.js:1:1876
IFrameWindow: cleanup oidc-client.min.js:1:1876
IFrameWindow: Successful response from frame window oidc-client.min.js:1:1876
OidcClient.processSigninResponse oidc-client.min.js:1:1876
OidcClient.readSigninResponseState oidc-client.min.js:1:1876
WebStorageStateStore.remove 9197fdd111554ca0a46e0af7d4ce80f3 oidc-client.min.js:1:1876
SigninState.fromStorageString oidc-client.min.js:1:1876
OidcClient.processSigninResponse: Received state from storage; validating response oidc-client.min.js:1:1876
ResponseValidator.validateSigninResponse oidc-client.min.js:1:1876
ResponseValidator._processSigninParams: state validated oidc-client.min.js:1:1876
ResponseValidator._processSigninParams: Response was error login_required oidc-client.min.js:1:2135
Error: login_required

I see that "login_required" is passed (by IS?) into my silent renew page.
And I have seen issue #98 from 2016.
Is that still valid? Is there a workaround for this?
I see this error also after logging out and doing a fresh login immediately, so it is hard for me to see how some 8 hours limit is responsible for that.
Is there something that my IT dept. can do on Identity Server side?
Am I doing it wrong?
Thanks in advance. This is really bugging me, and I am at the end of my wits.
Thanks,
Sascha

login_required

This means the token server is telling you that your cookie is no longer valid and the user needs to login again.

But it happens even if I logout and do a new login. The the cookie should be .... "fresh"?
Can my admin do something here?


Typings for select do not cover number as parameter value (SELECT 1 FROM ...)

Environment
Knex version: 1.0.7
Database + version: N/A
OS: Linux
Issue is about TypeScript definitions, tag @lorefnon.
Bug
If I want to do a query like SELECT * FROM products WHERE EXISTS (SELECT 1 FROM variants WHERE product_sku = sku);, Knex enables that with the following syntax:
knex("products").whereExists(
  function () {
    this.select(1).from("variants").where({ product_sku: knex.ref("sku") });
  }
);

However, even though that query runs just fine, the typings do not cover the case where the parameter of select is a number:
No overload matches this call.
  The last overload gave the following error.
    Argument of type 'number' is not assignable to parameter of type 'readonly ColumnDescriptor<products, DeferredKeySelection<products, never, false, {}, false, {}, never>[]>[]'. ts(2769)

@tkalliom how did you fix it?

@tkalliom how did you fix it?

Didn’t really fix it, just had to use @ts-expect-error

Try with this syntax
knex("products").whereExists(
    knex.select(1).from("variants").where({ product_sku: knex.ref("sku") });
);


Custom server?

It's possible to join a custom server? by adding then or editing the a file?
because i want to use it to chat on osu!irc

I think this is a duplicate of #45. I should probably change the drop down to a normal input field for now, and then we can see if there’s a better way to kinda support both.

check out v0.4.0!!


Refactor to agent model

The current implementation isn't very scalable and distributed, since all fetchers need to run in the same container.
Refactor fetchers to create an API for recieving images.
API could be something like:
- Name of the cluster
- Image with tag, digest and name
- Type of fetcher runtime

[ ] Agent for Runtimes
[ ] Watch a cluster/account instead of only fetching once

Problem of this model:
Can't provide a good way for passing image pull credentials of the registry.
Maybe using an external store (like Vault) could solve this.


migadu_mailbox resource fails when there are any identies

When trying to update a mailbox containing identities a following error is thrown:
Error: Error Reading Mailbox

  with module.mail.migadu_mailbox.ajgon,
  on mail/mailboxes.tf line 1, in resource "migadu_mailbox" "ajgon":
   1: resource "migadu_mailbox" "ajgon" {

While calling the API, an unexpected error was returned in the response. Please contact the provider developer if you are unsure how to resolve the error.

Error: GetMailbox: json: cannot unmarshal object into Go struct field Mailbox.identities of type string

I think the problem is, the plugin expects identities to be an array of strings, while API returns objects, i.e.
{
  "mailboxes": [
    {
      ...
      "identities": [
        {
          "name": "Identity",
          "address"<EMAIL_ADDRESS>          "domain_name": "example.com",
          "local_part": "identity",
          "may_receive": true,
          "may_send": true,
          "may_access_imap": true,
          "may_access_managesieve": true,
          "may_access_pop3": true
        }
      ],
      ...
    }
  ]
}

Thanks for opening this ticket & sorry that this is not working right now. Not sure right now why I declared them as strings and will check & change that once I'm back in front of a computer

Ok a fix for this was just released with version 2024.2.9. I have opted to simply remove the identities from mailbox models since we do have separate resources to manage identities anyway..
That said, I think I have found some problems with the identity API provided by Migadu, e.g. creating an identity with a password through the API does not seem to work as expected. I have contacted their support, but I would recommend to create identities using their web UI for now and import them later into terraform.

Awesome, thank you!

Hmm... I'm stilling having the same issue, after upgrade:
Error: GetMailbox: json: cannot unmarshal object into Go struct field Mailbox.identities of type string

I also double-checked that opentofu did proper upgrade:
$ ls .terraform/providers/registry.opentofu.org/metio/migadu/
2024.2.9

Maybe it's a problem with underlying migadu-client library? I'm happy to provide more debug info if you tell me how :)

oops yeah you are right, I was trying multiple ways to work on this and ended up not pulling in the latest version of the client. I'll fix that and release a new version tomorrow. Sorry for the inconvenience!

Ok so lets try this again - release 2024.2.10 contains an updated client. I have tested this locally with a mailbox that has multiple identities and I could import/modify it just fine.
Additionally, I heard back from Migadu support and they told me that they are going to update their documentation wrt. identity creation. The missing piece here was the undocumented password_use parameter which controls how the newly created identity is accessed. I've added some examples in https://registry.terraform.io/providers/metio/migadu/latest/docs/resources/identity in case you are interested in managing identities.
Thanks for taking your taking your time in opening this ticket. It improved not only this provider, but the Migadu docs as well :heart:

Anytime, I'm happy to help :)
Did another set of checks - now everything works like a charm, thank you!
One last question though - does it make sense to make password (in identities) field required when password_use is none? Or is it a limitation of migadu API?

Argh yeah you are right again. I did not realize that password is currently required even though it is only really required if password_use is set to custom. In all other cases, the password can be set, but the Migadu API will ignore it.
I'll open up another PR to fix that :sweat_smile:

The change wrt. password validation was released with 2024.2.11

The change wrt. password validation was released with 2024.2.11

And it works great, thank you! :)

Nice! Thanks for the feedback & all your time improving this provider ^^


Is that your actual API key?!?!

https://github.com/natolambert/interconnects-tools/blob/6c917e46912603a5493d631799336bbef61b3a88/scripts/tts.py#L85
Might be boilerplate example code, but searching for that hash didn't find any results.
Enjoying the blog, BTW.

I turned it off before pushing, was easier than deleting it from git history ;)
Thanks anyways and thanks!


Add support for TLS and self-signed certs

This change enables two things:

TLS encryption, controlled with the config param user.manager.ldap.useTls.
Support for self-signed server-side certs, controlled with the config param user.manager.ldap.disableCertVerification.

👍🏻


Add flag to specify artifact loading only using current stack's artifact store

Added:

a more verbose warning when trying to import an artifact store flavor without all dependencies installed
a boolean flag to specify that you want artifacts loading using only the current stack's artifact store

Pre-requisites
Please ensure you have done the following:

[x] I have read the CONTRIBUTING.md document.
[ ] If my change requires a change to docs, I have updated the documentation accordingly.
[ ] If I have added an integration, I have updated the integrations table and the corresponding website section.
[ ] I have added tests to cover my changes.
[x] I have based my new branch on develop and the open PR is targeting develop. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Other (add details above)

@schustmi the improved error message doesn't help with the fact that I might not want it to assume to use an artifact store other than the one in my current stack. (Agreed though that not having the right dependencies installed is just user error which we can make a bit nicer with a nicer error message).

@schustmi ok you're probably right. The confusion (when using it) came when getting an artifact via the last_successful_run (where potentially this might have been from a different artifact store and which (when getting the artifact) was calling load_artifact under the hood. This flag wouldn't have helped in that case. I'll remove it.

Yes, the flag should maybe be on the last_succesful_run method instead, where people can use it to fetch just the runs on the active stack/artifact store?
But then it's probably too far removed from the artifact loading for anyone to realize its use..


Teste issue

Describe the bug
[A short description of what the bug is.]
Description
[Describe the bug reported.]
Steps to Reproduce
[If applicable, provide detailed steps to reproduce the bug.]
Expected Behavior
[Describe what is expected to happen.]
Current Behavior
[Describe what is currently happening.]
Visual information
[If possible, add screenshots to illustrate this bug.]
Additional Information
[Provide any additional information, such as relevant versions, browser, OS, context, etc.]

Eu quero !!!

EU QUERO!!!

EU QUERO!!!

EU QUERO!!!

eu quero!!!

eu quero!!!

eu quero!!!

eu quero!!!

eu quero!!!


Find a better solution for the circular dependency fix

https://github.com/Manhim/Cervo/commit/215fc98b879b63dcba78e5177c6dc7d397edc243
Reference: #18
Need to find a better solution than that. Maybe streamline things a bit.

I don't think that there is a solution to this problem unfortunately.


return vs return nothing

I don't have a strong preference either way, but I think it would be nice if Runic normalized to one or the other. The only potential issue is that it's technically possible to redefine nothing inside a module or function, but I have yet to see any code in the wild which does this.

See discussion here: https://github.com/fredrikekre/Runic.jl/pull/48#issuecomment-2314947177

Re https://github.com/fredrikekre/Runic.jl/pull/48#issuecomment-2315032885:
I would argue that even in the case of 2., the function still returns a value of nothing, irregardless whether it's used or not, so I would say making that explicit via return nothing is not necessarily bad

FWIW, I'd also vote for normalising to return nothing. In addition to @simeonschaub's point above, to me, the (subtle) communicative aspect of distinguishing between return and return nothing is outweighed by simplicity and consistency.


Replace ".NET Framework" with ".NET" in API summaries

Applies to dotnet-api-docs repo, but want to track it here with my other work.

With these PRs, this issue is resolved.


Fixed High-contrast mode: Breadcrumb separator should match link text…

Fixed issue #7328 According to the Instructions

@surajaiswal13 thanks so much for this, however it looks like the issue of the breadcrumbs 'arrow' and the home icon was already fixed via fb66c1fd1732f462a1983edb5410192a9b8963da
Feel free to pick up another issue though, may I suggest #7453 -> i can confirm that is not yet fixed.


Use errgroup and context

Changes logic from being manual to using errgroup and context.

@bittrance thank you for the great review, as always! The coverage should have increased since there was mostly deleted code (went up with around 2%).
Was thinking about doing more, but then thought that it should be in another PR. Have some linting improvements I want to add as well, but will keep those changes out of this one.


Docs: relation between agenix / git-crypt

This motion suggests clarifying the docs (git-crypt: 'legacy'):
https://github.com/divnix/devos/discussions/185#discussioncomment-851296
We could also deprecate it alltogether.
We should have a discussion if we have a need for (git clean / smudge) implementation, that is, if that's desired or rather harmful.
/cc @cipharius

Actually I would say just remove it all together in the develop branch, so next time we update core its gone. Maybe add a note to the docs that we used to use git-crypt but have now fully switched to agenix.

git-crypt is now removed entirely.


add firewall rules

Ran Plan for project: infrastructure/local/lhr/unifi-firewall-rules dir: infrastructure/local/lhr/unifi-firewall-rules workspace: terragrunt
Show Output
03:57:43.082 INFO   Downloading Terraform configurations from ../../.. into ./.terragrunt-cache/mkhrasI06OR9XnV4Ro7Qdo0yV90/_9kdF_LW_dgT34GSs9p9X3B7TUE
03:57:43.440 STDOUT tofu: Initializing the backend...
03:57:43.643 STDOUT tofu:
03:57:43.643 STDOUT tofu: Successfully configured the backend "s3"! OpenTofu will automatically
03:57:43.643 STDOUT tofu: use this backend unless the backend configuration changes.
03:57:43.721 STDOUT tofu: Initializing provider plugins...
03:57:43.722 STDOUT tofu: - Reusing previous version of cloudflare/cloudflare from the dependency lock file
03:57:43.830 STDOUT tofu: - Reusing previous version of integrations/github from the dependency lock file
03:57:43.876 STDOUT tofu: - Reusing previous version of vexxhost/uptimerobot from the dependency lock file
03:57:43.917 STDOUT tofu: - Reusing previous version of paultyng/unifi from the dependency lock file
03:57:43.971 STDOUT tofu: - Reusing previous version of hashicorp/aws from the dependency lock file
03:57:44.029 STDOUT tofu: - Reusing previous version of backblaze/b2 from the dependency lock file
03:57:45.107 STDOUT tofu: - Installing cloudflare/cloudflare v4.43.0...
03:57:46.646 STDOUT tofu: - Installed cloudflare/cloudflare v4.43.0 (signed, key ID C76001609EE3B136)
03:57:47.652 STDOUT tofu: - Installing integrations/github v6.2.2...
03:57:48.750 STDOUT tofu: - Installed integrations/github v6.2.2 (signed, key ID 38027F80D7FD5FB2)
03:57:49.883 STDOUT tofu: - Installing vexxhost/uptimerobot v0.8.2...
03:57:50.755 STDOUT tofu: - Installed vexxhost/uptimerobot v0.8.2. Signature validation was skipped due to the registry not containing GPG keys for this provider
03:57:51.512 STDOUT tofu: - Installing paultyng/unifi v0.41.0...
03:57:52.344 STDOUT tofu: - Installed paultyng/unifi v0.41.0. Signature validation was skipped due to the registry not containing GPG keys for this provider
03:57:53.852 STDOUT tofu: - Installing hashicorp/aws v5.72.0...
03:58:14.172 STDOUT tofu: - Installed hashicorp/aws v5.72.0 (signed, key ID 0C0AF313E5FD9F80)
03:58:15.318 STDOUT tofu: - Installing backblaze/b2 v0.8.12...
03:58:17.437 STDOUT tofu: - Installed backblaze/b2 v0.8.12. Signature validation was skipped due to the registry not containing GPG keys for this provider
03:58:17.447 STDOUT tofu: Providers are signed by their developers.
03:58:17.447 STDOUT tofu: If you'd like to know more about provider signing, you can read about it here:
03:58:17.447 STDOUT tofu: https://opentofu.org/docs/cli/plugins/signing/
03:58:17.447 STDOUT tofu: OpenTofu has made some changes to the provider dependency selections recorded
03:58:17.447 STDOUT tofu: in the .terraform.lock.hcl file. Review those changes and commit them to your
03:58:17.447 STDOUT tofu: version control system if they represent changes you intended to make.
03:58:17.540 STDOUT tofu: OpenTofu has been successfully initialized!

03:58:29.344 STDOUT tofu: OpenTofu used the selected providers to generate the following execution
03:58:29.344 STDOUT tofu: plan. Resource actions are indicated with the following symbols:
03:58:29.344 STDOUT tofu:   + create
03:58:29.344 STDOUT tofu: OpenTofu will perform the following actions:
03:58:29.344 STDOUT tofu:   # unifi_firewall_rule.this["allow_all_vlans_to_local_dns_server"] will be created
03:58:29.344 STDOUT tofu:   + resource "unifi_firewall_rule" "this" {
03:58:29.344 STDOUT tofu:       + action                 = "accept"
03:58:29.344 STDOUT tofu:       + dst_address            = "<IP_ADDRESS>"
03:58:29.344 STDOUT tofu:       + dst_network_type       = "NETv4"
03:58:29.344 STDOUT tofu:       + dst_port               = "53"
03:58:29.344 STDOUT tofu:       + enabled                = true
03:58:29.345 STDOUT tofu:       + id                     = (known after apply)
03:58:29.345 STDOUT tofu:       + logging                = false
03:58:29.345 STDOUT tofu:       + name                   = "Allow Traffic from All VLANs to Local DNS Server"
03:58:29.345 STDOUT tofu:       + protocol               = "tcp_udp"
03:58:29.345 STDOUT tofu:       + rule_index             = 20000
03:58:29.345 STDOUT tofu:       + ruleset                = "LAN_IN"
03:58:29.345 STDOUT tofu:       + site                   = (known after apply)
03:58:29.345 STDOUT tofu:       + src_firewall_group_ids = [
03:58:29.345 STDOUT tofu:           + "67147f54ff69e4191a972c39",
03:58:29.345 STDOUT tofu:         ]
03:58:29.345 STDOUT tofu:       + src_network_type       = "NETv4"
03:58:29.345 STDOUT tofu:     }
03:58:29.345 STDOUT tofu:   # unifi_firewall_rule.this["allow_iot_private_to_self"] will be created
03:58:29.345 STDOUT tofu:   + resource "unifi_firewall_rule" "this" {
03:58:29.345 STDOUT tofu:       + action                 = "accept"
03:58:29.345 STDOUT tofu:       + dst_firewall_group_ids = [
03:58:29.345 STDOUT tofu:           + "67147f54ff69e4191a972c3d",
03:58:29.346 STDOUT tofu:         ]
03:58:29.346 STDOUT tofu:       + dst_network_type       = "NETv4"
03:58:29.346 STDOUT tofu:       + enabled                = true
03:58:29.346 STDOUT tofu:       + id                     = (known after apply)
03:58:29.346 STDOUT tofu:       + logging                = false
03:58:29.346 STDOUT tofu:       + name                   = "Allow Traffic from IoT Private to itself"
03:58:29.346 STDOUT tofu:       + protocol               = "all"
03:58:29.346 STDOUT tofu:       + rule_index             = 20600
03:58:29.346 STDOUT tofu:       + ruleset                = "LAN_IN"
03:58:29.346 STDOUT tofu:       + site                   = (known after apply)
03:58:29.346 STDOUT tofu:       + src_firewall_group_ids = [
03:58:29.346 STDOUT tofu:           + "67147f54ff69e4191a972c3d",
03:58:29.346 STDOUT tofu:         ]
03:58:29.346 STDOUT tofu:       + src_network_type       = "NETv4"
03:58:29.346 STDOUT tofu:     }
03:58:29.346 STDOUT tofu:   # unifi_firewall_rule.this["allow_iot_public_to_self"] will be created
03:58:29.347 STDOUT tofu:   + resource "unifi_firewall_rule" "this" {
03:58:29.347 STDOUT tofu:       + action                 = "accept"
03:58:29.347 STDOUT tofu:       + dst_firewall_group_ids = [
03:58:29.347 STDOUT tofu:           + "67147f54ff69e4191a972c37",
03:58:29.347 STDOUT tofu:         ]
03:58:29.347 STDOUT tofu:       + dst_network_type       = "NETv4"
03:58:29.347 STDOUT tofu:       + enabled                = true
03:58:29.347 STDOUT tofu:       + id                     = (known after apply)
03:58:29.347 STDOUT tofu:       + logging                = false
03:58:29.347 STDOUT tofu:       + name                   = "Allow Traffic from IoT Public to itself"
03:58:29.347 STDOUT tofu:       + protocol               = "all"
03:58:29.347 STDOUT tofu:       + rule_index             = 20500
03:58:29.347 STDOUT tofu:       + ruleset                = "LAN_IN"
03:58:29.347 STDOUT tofu:       + site                   = (known after apply)
03:58:29.347 STDOUT tofu:       + src_firewall_group_ids = [
03:58:29.347 STDOUT tofu:           + "67147f54ff69e4191a972c37",
03:58:29.348 STDOUT tofu:         ]
03:58:29.348 STDOUT tofu:       + src_network_type       = "NETv4"
03:58:29.348 STDOUT tofu:     }
03:58:29.348 STDOUT tofu:   # unifi_firewall_rule.this["block_iot_private_to_all_vlans"] will be created
03:58:29.348 STDOUT tofu:   + resource "unifi_firewall_rule" "this" {
03:58:29.348 STDOUT tofu:       + action                 = "drop"
03:58:29.348 STDOUT tofu:       + dst_firewall_group_ids = [
03:58:29.348 STDOUT tofu:           + "67147f54ff69e4191a972c39",
03:58:29.348 STDOUT tofu:         ]
03:58:29.348 STDOUT tofu:       + dst_network_type       = "NETv4"
03:58:29.348 STDOUT tofu:       + enabled                = true
03:58:29.348 STDOUT tofu:       + id                     = (known after apply)
03:58:29.348 STDOUT tofu:       + logging                = false
03:58:29.348 STDOUT tofu:       + name                   = "Block Traffic from IoT Private to All VLANs"
03:58:29.349 STDOUT tofu:       + protocol               = "all"
03:58:29.349 STDOUT tofu:       + rule_index             = 20610
03:58:29.349 STDOUT tofu:       + ruleset                = "LAN_IN"
03:58:29.349 STDOUT tofu:       + site                   = (known after apply)
03:58:29.349 STDOUT tofu:       + src_firewall_group_ids = [
03:58:29.349 STDOUT tofu:           + "67147f54ff69e4191a972c3d",
03:58:29.349 STDOUT tofu:         ]
03:58:29.349 STDOUT tofu:       + src_network_type       = "NETv4"
03:58:29.349 STDOUT tofu:     }
03:58:29.349 STDOUT tofu:   # unifi_firewall_rule.this["block_iot_private_to_internet"] will be created
03:58:29.349 STDOUT tofu:   + resource "unifi_firewall_rule" "this" {
03:58:29.349 STDOUT tofu:       + action                 = "drop"
03:58:29.349 STDOUT tofu:       + dst_network_type       = "NETv4"
03:58:29.349 STDOUT tofu:       + enabled                = true
03:58:29.349 STDOUT tofu:       + id                     = (known after apply)
03:58:29.349 STDOUT tofu:       + logging                = false
03:58:29.350 STDOUT tofu:       + name                   = "Block Traffic from IoT Private to Internet"
03:58:29.350 STDOUT tofu:       + protocol               = "all"
03:58:29.350 STDOUT tofu:       + rule_index             = 20620
03:58:29.350 STDOUT tofu:       + ruleset                = "WAN_OUT"
03:58:29.350 STDOUT tofu:       + site                   = (known after apply)
03:58:29.350 STDOUT tofu:       + src_firewall_group_ids = [
03:58:29.350 STDOUT tofu:           + "67147f54ff69e4191a972c3d",
03:58:29.350 STDOUT tofu:         ]
03:58:29.350 STDOUT tofu:       + src_network_type       = "NETv4"
03:58:29.350 STDOUT tofu:     }
03:58:29.350 STDOUT tofu:   # unifi_firewall_rule.this["block_iot_public_to_all_vlans"] will be created
03:58:29.350 STDOUT tofu:   + resource "unifi_firewall_rule" "this" {
03:58:29.350 STDOUT tofu:       + action                 = "drop"
03:58:29.350 STDOUT tofu:       + dst_firewall_group_ids = [
03:58:29.350 STDOUT tofu:           + "67147f54ff69e4191a972c39",
03:58:29.350 STDOUT tofu:         ]
03:58:29.350 STDOUT tofu:       + dst_network_type       = "NETv4"
03:58:29.350 STDOUT tofu:       + enabled                = true
03:58:29.350 STDOUT tofu:       + id                     = (known after apply)
03:58:29.350 STDOUT tofu:       + logging                = false
03:58:29.351 STDOUT tofu:       + name                   = "Block Traffic from IoT Public to All VLANs"
03:58:29.351 STDOUT tofu:       + protocol               = "all"
03:58:29.351 STDOUT tofu:       + rule_index             = 20510
03:58:29.351 STDOUT tofu:       + ruleset                = "LAN_IN"
03:58:29.351 STDOUT tofu:       + site                   = (known after apply)
03:58:29.351 STDOUT tofu:       + src_firewall_group_ids = [
03:58:29.351 STDOUT tofu:           + "67147f54ff69e4191a972c37",
03:58:29.351 STDOUT tofu:         ]
03:58:29.351 STDOUT tofu:       + src_network_type       = "NETv4"
03:58:29.351 STDOUT tofu:     }
03:58:29.351 STDOUT tofu: Plan: 6 to add, 0 to change, 0 to destroy.
03:58:29.351 STDOUT tofu:

:arrow_forward: To apply this plan, comment:atlantis apply -p infrastructure/local/lhr/unifi-firewall-rules

:put_litter_in_its_place: To delete this plan and lock, click here
:repeat: To plan this project again, comment:atlantis plan -p infrastructure/local/lhr/unifi-firewall-rules

Plan: 6 to add, 0 to change, 0 to destroy.

:fast_forward: To apply all unapplied plans from this Pull Request, comment:atlantis apply

:put_litter_in_its_place: To delete all plans and locks from this Pull Request, comment:atlantis unlock

atlantis apply

Automatically merging because all plans have been successfully applied.

Ran Apply for project: infrastructure/local/lhr/unifi-firewall-rules dir: infrastructure/local/lhr/unifi-firewall-rules workspace: terragrunt
Show Output
03:59:06.059 INFO   Downloading Terraform configurations from ../../.. into ./.terragrunt-cache/mkhrasI06OR9XnV4Ro7Qdo0yV90/_9kdF_LW_dgT34GSs9p9X3B7TUE
03:59:06.662 STDOUT tofu: Initializing the backend...
03:59:08.360 STDOUT tofu: Initializing provider plugins...
03:59:08.360 STDOUT tofu: - Reusing previous version of paultyng/unifi from the dependency lock file
03:59:08.459 STDOUT tofu: - Reusing previous version of hashicorp/aws from the dependency lock file
03:59:08.516 STDOUT tofu: - Reusing previous version of backblaze/b2 from the dependency lock file
03:59:08.567 STDOUT tofu: - Reusing previous version of cloudflare/cloudflare from the dependency lock file
03:59:08.617 STDOUT tofu: - Reusing previous version of integrations/github from the dependency lock file
03:59:08.685 STDOUT tofu: - Reusing previous version of vexxhost/uptimerobot from the dependency lock file
03:59:08.764 STDOUT tofu: - Using previously-installed vexxhost/uptimerobot v0.8.2
03:59:08.777 STDOUT tofu: - Using previously-installed paultyng/unifi v0.41.0
03:59:09.323 STDOUT tofu: - Using previously-installed hashicorp/aws v5.72.0
03:59:09.363 STDOUT tofu: - Using previously-installed backblaze/b2 v0.8.12
03:59:09.402 STDOUT tofu: - Using previously-installed cloudflare/cloudflare v4.43.0
03:59:09.418 STDOUT tofu: - Using previously-installed integrations/github v6.2.2
03:59:09.419 STDOUT tofu: OpenTofu has been successfully initialized!
03:59:09.419 STDOUT tofu:
03:59:09.419 STDOUT tofu: You may now begin working with OpenTofu. Try running "tofu plan" to see
03:59:09.419 STDOUT tofu: any changes that are required for your infrastructure. All OpenTofu commands
03:59:09.419 STDOUT tofu: should now work.
03:59:09.419 STDOUT tofu: If you ever set or change modules or backend configuration for OpenTofu,
03:59:09.419 STDOUT tofu: rerun this command to reinitialize your working directory.  Resources: 6 added, 0 changed, 0 destroyed.
03:59:15.202 STDOUT tofu:

Locks and plans deleted for the projects and workspaces modified in this pull request:

dir: infrastructure/local/lhr/unifi-firewall-rules workspace: terragrunt


Add support for Scan Ops in joint_logprob

This PR aims to implements logprob for Scan Ops. Linked Issue: #23
    k = at.iscalar("k")
    A = at.vector("A")
    random_dist = at.random.normal(size=10)

    result, updates = aesara.scan(
        fn=lambda prior_result: prior_result + random_dist,
        outputs_info=at.ones_like(A),
        n_steps=k,
    )

    logp = joint_logprob(result, {A: A.type(), k: k.type()})

Note : I am building this on top of replacement logic from #19

[ ] setting up a general Scan replacement framework.

This PR depends on https://github.com/aesara-devs/aesara/pull/510.

I've added some missing tests from symbolic-pymc.  Also, I imagine we'll need https://github.com/aesara-devs/aesara/pull/534 to go through before this will work, because the automatic cloning that ScanArgs currently performs is not what the borrowed symbolic-pymc code expects.

And the current issue at hand is for some reason, the rv_remapper doesn't update variables other than var itself. (When running the newly added test_scan_logprob_basic the push_out_rvs optimization returns mappings for both S_r and Y_rv but the only one that's updated in this dictionary is Y_rvwhich corresponds to the var for which we're getting log probability for)
https://github.com/aesara-devs/aeppl/blob/37a52281bfd9bcad1ec21e21276b9632158e431b/aeppl/joint_logprob.py#L117
Is that intended ?

The only way I could see this being done without somehow specifying a value variable for terms like S_t is if we never even required value variables. Instead, these logprob-related functions would also return a dict mapping MeasurableVariables to value variables that are automatically generated for them when they're encountered/created by these rewrite functions.

Sure, but we need an alternative to specify conditional relationships. We were doing that implicitly depending on whether RVs in the graph were mapped to a value variable or not (e.g., in the Mixture RVs and ChainedTransform / Censored RVs)

The only way I could see this being done without somehow specifying a value variable for terms like S_t is if we never even required value variables. Instead, these logprob-related functions would also return a dict mapping MeasurableVariables to value variables that are automatically generated for them when they're encountered/created by these rewrite functions.

Sure, but we need an alternative to specify conditional relationships, when there is potential ambiguity. We were doing that implicitly depending on whether RVs in the graph were mapped to a value variable or not (e.g., in the Mixture RVs and ChainedTransform / Censored RVs)

Yes, that is one of the downsides to the approach.

Here are my old notes on this work from symbolic-pymc: scan-log-likelihoods.md.  They were written for Theano, but everything still applies to Aesara.

I just pushed some changes that should put everything in general working order.
The convert_outer_out_to_in tests need to be rewritten so that they test the output of that function directly, and a couple more Scan cases would be nice (e.g. using joint_logprob on the model in test_convert_outer_out_to_in_sit_sot).

Let's say we wanted to compute the log-probability for a simple Markov chain like the following:
import numpy as np

import aesara
import aesara.tensor as at

from aeppl.joint_logprob import joint_logprob

aesara.config.on_opt_error = "raise"

srng = at.random.RandomStream()

S_0_rv = srng.categorical(np.array([0.5, 0.5]), name="S_0")

s_0_vv = S_0_rv.clone()
s_0_vv.name = "s_0"

def step_fn(S_tm1):
    S_t = srng.categorical(np.array([0.5, 0.5]), name="S_t")
    return S_t

S_1T_rv, _ = aesara.scan(
    fn=step_fn,
    outputs_info=[{"initial": S_0_rv, "taps": [-1]}],
    strict=True,
    n_steps=10,
    name="S_0T"
)

S_1T_rv.name = "S_1T"
s_1T_vv = S_1T_rv.clone()
s_1T_vv.name = "s_1T"

If we try to construct the log-probability graph, we get an error:
S_0T_logp = joint_logprob({S_1T_rv: s_1T_vv, S_0_rv: s_0_vv})

---------------------------------------------------------------------------
KeyError                                  Traceback (most recent call last)
/tmp/user/1000/babel-9XUDYv/python-rnH85p in <module>
----> 1 S_0T_logp = joint_logprob({S_1T_rv: s_1T_vv, S_0_rv: s_0_vv})

~/projects/code/python/aeppl/aeppl/joint_logprob.py in joint_logprob(sum, *args, **kwargs)
    218
    219     """
--> 220     logprob = factorized_joint_logprob(*args, **kwargs)
    221     if not logprob:
    222         return None

~/projects/code/python/aeppl/aeppl/joint_logprob.py in factorized_joint_logprob(rv_values, warn_missing_rvs, extra_rewrites, **kwargs)
    157         q_rv_value_vars = [
    158             replacements[q_rv_var]
--> 159             for q_rv_var in outputs
    160             if not getattr(q_rv_var.tag, "ignore_logprob", False)
    161         ]

~/projects/code/python/aeppl/aeppl/joint_logprob.py in <listcomp>(.0)
    158             replacements[q_rv_var]
    159             for q_rv_var in outputs
--> 160             if not getattr(q_rv_var.tag, "ignore_logprob", False)
    161         ]
    162

KeyError: 'for{cpu,scan_fn}.0\n

The following two sections summarize the two main features we need to implement before merging.
Add MeasurableVariable detection for Subtensor Scan output
The first issue is that S_1T_rv is actually the output of a Subtensor:
print(S_1T_rv.owner)

Subtensor{int64::}(for{cpu,S_0T}.0, ScalarConstant{1})

In other words, S_1T_rv = S_0T_rv[1:] for some S_0T_rv that effectively represents at.concatenate([at.atleast_1d(S_0_rv), S_1T_rv]).
It is possible to (partially) work around the error above by manually extracting the direct output of the Scan node–i.e. the output corresponding to S_0T_rv (e.g. via S_1T_rv.owner.inputs[0]); however, we still need to support the joint_logprob arguments/usage demonstrated in the example above, since it's considerably more intuitive. Also, there are some issues with this work-around that will be described below.
We should be able to make some updates to find_measurable_scans so that it checks for Subtensors acting on Scan outputs and somehow checks these Subtensors against the Scan's TAPS configuration (i.e. attempt to confirm that the Subtensor is the output of the aesara.scan helper function).
Support initial values
The second issue is that the initial TAPS values (i.e. the "initial" values specified in a call to aesara.scan) are not currently included in the resulting log-probability graphs.
If we extract the underlying S_0T_rv variables and use that in a call to joint_logprob, we can get a log-probability graph:
S_0T_rv = S_1T_rv.owner.inputs[0]

s_0T_vv = S_0T_rv.clone()
s_0T_vv.name = "s_0T"

S_0T_logp = joint_logprob({S_0T_rv: s_0T_vv, S_0_rv: s_0_vv})

aesara.dprint(S_0T_logp, depth=4)

Sum{acc_dtype=float64} [id A] ''
 |MakeVector{dtype='float64'} [id B] ''
   |Sum{acc_dtype=float64} [id C] ''
   | |Assert{msg='0 <= p <= 1'} [id D] 's_0_logprob'
   |Sum{acc_dtype=float64} [id E] ''
     |for{cpu,scan_fn} [id F] 's_0T_logprob'

Inner graphs of the scan ops:

for{cpu,scan_fn} [id F] 's_0T_logprob'
 >Assert{msg='0 <= p <= 1'} [id G] 'S_t_vv_logprob'
 > |Elemwise{switch,no_inplace} [id H] ''
 > | |Elemwise{and_,no_inplace} [id I] ''
 > | | |Elemwise{le,no_inplace} [id J] ''
 > | | |Elemwise{lt,no_inplace} [id K] ''
 > | |Elemwise{log,no_inplace} [id L] ''
 > | | |Subtensor{int64} [id M] ''
 > | |TensorConstant{-inf} [id N]
 > |All [id O] ''
 > | |Elemwise{ge,no_inplace} [id P] ''
 > |   |Elemwise{true_div,no_inplace} [id Q] ''
 > |   |InplaceDimShuffle{x} [id R] ''
 > |All [id S] ''
 >   |Elemwise{le,no_inplace} [id T] ''
 >     |Elemwise{true_div,no_inplace} [id Q] ''
 >     |InplaceDimShuffle{x} [id U] ''

As this output demonstrates, there is a log-probability term for S_0_rv prior (i.e. the sub-graph labeled "s_0_logprob") and another log-probability term for the Scan/state sequence–labeled "s_0T_logprob"–that depends on the s_0_vv vector; however, the corresponding (outer-)input for the Scan doesn't depend on s_0_vv in any way.
Let's take a look at the inputs of the model's Scan node:
import pprint

from aesara.scan.utils import ScanArgs

## Prevent `dict` sorting
pprint.sorted = lambda arg, *a, **kw: arg

scan_args = ScanArgs.from_node(S_1T_rv.owner.inputs[0].owner)

def labeled_outer_inputs(scan_args):
    """Get ordered, labeled outer inputs for a `Scan`."""
    outer_inputs = [
        "n_steps",
        "outer_in_seqs",
        "outer_in_mit_mot",
        "outer_in_mit_sot",
        "outer_in_sit_sot",
        "outer_in_shared",
        "outer_in_nit_sot",
        "outer_in_non_seqs",
    ]

    return {
        name: getattr(scan_args, name)
        for name in outer_inputs
        if getattr(scan_args, name, None)
    }

model_outer_inputs = labeled_outer_inputs(scan_args)
pprint.pprint(model_outer_inputs)

{'n_steps': TensorConstant{10},
 'outer_in_sit_sot': [IncSubtensor{Set;:int64:}.0],
 'outer_in_shared': [RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7F9D44833D70>)]}

The 'outer_in_sit_sot' input is the one that corresponds with the state sequence, and it is a vector with its first input set to s_0_vv:
aesara.dprint(model_outer_inputs["outer_in_sit_sot"])

IncSubtensor{Set;:int64:} [id A] ''
 |AllocEmpty{dtype='int64'} [id B] ''
 | |Elemwise{add,no_inplace} [id C] ''
 |   |TensorConstant{10} [id D]
 |   |Subtensor{int64} [id E] ''
 |     |Shape [id F] ''
 |     | |Rebroadcast{0} [id G] ''
 |     |   |InplaceDimShuffle{x} [id H] ''
 |     |     |categorical_rv{0, (1,), int64, False}.1 [id I] 'S_0'
 |     |       |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7F9D44A1B6E0>) [id J]
 |     |       |TensorConstant{[]} [id K]
 |     |       |TensorConstant{4} [id L]
 |     |       |TensorConstant{(2,) of 0.5} [id M]
 |     |ScalarConstant{0} [id N]
 |Rebroadcast{0} [id G] ''
 |ScalarFromTensor [id O] ''
   |Subtensor{int64} [id E] ''

Our convert_outer_out_to_in needs to identify the original full-sequence variable (i.e. the AllocEmpty with ID B) and replace it with its value variable.

I just added a commit that handles the first remaining issue (i.e. the section in https://github.com/aesara-devs/aeppl/pull/24#issuecomment-922369850 titled "Add MeasurableVariable detection for Subtensor Scan output")

I just added the functionality for the last missing feature.  It needs more testing, but at least seems to work for the one simple implemented test case.


Add JSON u() for type casting to an uint64_t, Fix all compiler warning (with gcc 4.9.2)

Add JSON u() for type casting to an uint64_t
Add explicit operator uint64_t()
Remove all compiler warning. (done with gcc 4.9.2)

Thank you for your work. I applied this manually.


add storeTrans like rttov interface to give user option of not storin…

…g transmission on layers.

closes #73

closes #73

closes #73


Check if ipv4 and ipv6 format checkers work correctly

Seems like described checkers don't work.
Here are several examples:
In[13]: from jsonschema import validate, Draft4Validator
In[14]: schema = {'oneOf': [{'format': 'ipv4'}, {'format': 'ipv6'}]}

In[15]: Draft4Validator(schema).validate('ffff.ffff.ffff.ffff.fff.ff.fff.f.ff.sdfgsdgdsfgdsfg')
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/IPython/core/interactiveshell.py", line 2883, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)
  File "<ipython-input-15-ac8c552ed724>", line 1, in <module>
    Draft4Validator(schema).validate('ffff.ffff.ffff.ffff.fff.ff.fff.f.ff.sdfgsdgdsfgdsfg')
  File "/usr/local/lib/python2.7/dist-packages/jsonschema/validators.py", line 123, in validate
    raise error
ValidationError: 'ffff.ffff.ffff.ffff.fff.ff.fff.f.ff.sdfgsdgdsfgdsfg' is valid under each of {'format': 'ipv6'}, {'format': 'ipv4'}

Failed validating 'oneOf' in schema:
    {'oneOf': [{'format': 'ipv4'}, {'format': 'ipv6'}]}

On instance:
    'ffff.ffff.ffff.ffff.fff.ff.fff.f.ff.sdfgsdgdsfgdsfg'

In[16]: Draft4Validator(schema).validate('<IP_ADDRESS>')
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/IPython/core/interactiveshell.py", line 2883, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)
  File "<ipython-input-16-d2d01d6e7e5d>", line 1, in <module>
    Draft4Validator(schema).validate('<IP_ADDRESS>')
  File "/usr/local/lib/python2.7/dist-packages/jsonschema/validators.py", line 123, in validate
    raise error
ValidationError: '<IP_ADDRESS>' is valid under each of {'format': 'ipv6'}, {'format': 'ipv4'}

Failed validating 'oneOf' in schema:
    {'oneOf': [{'format': 'ipv4'}, {'format': 'ipv6'}]}

On instance:
    '<IP_ADDRESS>'

In[17]: Draft4Validator(schema).validate('')
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/IPython/core/interactiveshell.py", line 2883, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)
  File "<ipython-input-17-1599ec0eea0c>", line 1, in <module>
    Draft4Validator(schema).validate('')
  File "/usr/local/lib/python2.7/dist-packages/jsonschema/validators.py", line 123, in validate
    raise error
ValidationError: '' is valid under each of {'format': 'ipv6'}, {'format': 'ipv4'}

Failed validating 'oneOf' in schema:
    {'oneOf': [{'format': 'ipv4'}, {'format': 'ipv6'}]}

On instance:
    ''

Some additional info:
Python 2.7.10 (default, Oct 14 2015, 16:09:02)
Type "copyright", "credits" or "license" for more information.

IPython 2.3.0 -- An enhanced Interactive Python.
?         -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help      -> Python's own help system.
object?   -> Details about 'object', use 'object??' for extra details.
PyDev console: using IPython 2.3.0

import sys; print('Python %s on %s' % (sys.version, sys.platform))
sys.path.extend(['***'])

Python 2.7.10 (default, Oct 14 2015, 16:09:02)
[GCC 5.2.1 20151010] on linux2

~$ pip show jsonschema

---
Name: jsonschema
Version: 2.5.1
Location: /usr/local/lib/python2.7/dist-packages
Requires: functools32

And it's OK, i forgot to specify format_checker kwarg.
That was not very smart, sorry.

So how to check if ipv4 or ipv6

Can anybody tell us how we can check on the ip address ipv4 format and ipv6 format


Starrocks queries

Hi,

can we use starrocks on ubuntu? Should we build from source or can we use the release from https://starrocks.com/download/community?hsLang=en (StarRocks-2.2.0.tar.gz)
Should we use oracle-jdk? or open-jdk

Thanks

@sridhard

Yes you can run starrocks on ubuntu, and you don't need to build yourself. you can use the binary directly.
both are OK. just make sure use JDK not JRE.


Support await syntax for async methods

This should be possible with Rust's coroutines support, see https://doc.rust-lang.org/nightly/unstable-book/language-features/generators.html and https://github.com/rust-lang/rust/issues/43122.
We might need to provide our own macros similar to https://github.com/alexcrichton/futures-await.

I got a proof of concept running in a branch: I started working on this in a branch: https://github.com/Boddlnagg/winrt-rust/tree/futures-preview
I must say that it feels quite nice!


Miniconda setup error

Reference: https://github.com/PMEAL/OpenPNM/actions/runs/968168785
# >>>>>>>>>>>>>>>>>>>>>> ERROR REPORT <<<<<<<<<<<<<<<<<<<<<<

    Traceback (most recent call last):
      File "/usr/share/miniconda/lib/python3.8/site-packages/urllib3/response.py", line 436, in _error_catcher
        yield
      File "/usr/share/miniconda/lib/python3.8/site-packages/urllib3/response.py", line 763, in read_chunked
        self._update_chunk_length()
      File "/usr/share/miniconda/lib/python3.8/site-packages/urllib3/response.py", line 693, in _update_chunk_length
        line = self._fp.fp.readline()
      File "/usr/share/miniconda/lib/python3.8/socket.py", line 669, in readinto
        return self._sock.recv_into(b)
      File "/usr/share/miniconda/lib/python3.8/ssl.py", line 1241, in recv_into
        return self.read(nbytes, buffer)
      File "/usr/share/miniconda/lib/python3.8/ssl.py", line 1099, in read
        return self._sslobj.read(len, buffer)
    ConnectionResetError: [Errno 104] Connection reset by peer

    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
      File "/usr/share/miniconda/lib/python3.8/site-packages/requests/models.py", line 751, in generate
        for chunk in self.raw.stream(chunk_size, decode_content=True):
      File "/usr/share/miniconda/lib/python3.8/site-packages/urllib3/response.py", line 571, in stream
        for line in self.read_chunked(amt, decode_content=decode_content):
      File "/usr/share/miniconda/lib/python3.8/site-packages/urllib3/response.py", line 792, in read_chunked
        self._original_response.close()
      File "/usr/share/miniconda/lib/python3.8/contextlib.py", line 131, in __exit__
        self.gen.throw(type, value, traceback)
      File "/usr/share/miniconda/lib/python3.8/site-packages/urllib3/response.py", line 454, in _error_catcher
        raise ProtocolError("Connection broken: %r" % e, e)
    urllib3.exceptions.ProtocolError: ("Connection broken: ConnectionResetError(104, 'Connection reset by peer')", ConnectionResetError(104, 'Connection reset by peer'))

    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
      File "/usr/share/miniconda/lib/python3.8/site-packages/conda/exceptions.py", line 1079, in __call__
        return func(*args, **kwargs)
      File "/usr/share/miniconda/lib/python3.8/site-packages/conda/cli/main.py", line 84, in _main
        exit_code = do_call(args, p)
      File "/usr/share/miniconda/lib/python3.8/site-packages/conda/cli/conda_argparse.py", line 83, in do_call
        return getattr(module, func_name)(args, parser)
      File "/usr/share/miniconda/lib/python3.8/site-packages/conda/cli/main_install.py", line 20, in execute
        install(args, parser, 'install')
      File "/usr/share/miniconda/lib/python3.8/site-packages/conda/cli/install.py", line 261, in install
        unlink_link_transaction = solver.solve_for_transaction(
      File "/usr/share/miniconda/lib/python3.8/site-packages/conda/core/solve.py", line 114, in solve_for_transaction
        unlink_precs, link_precs = self.solve_for_diff(update_modifier, deps_modifier,
      File "/usr/share/miniconda/lib/python3.8/site-packages/conda/core/solve.py", line 157, in solve_for_diff
        final_precs = self.solve_final_state(update_modifier, deps_modifier, prune, ignore_pinned,
      File "/usr/share/miniconda/lib/python3.8/site-packages/conda/core/solve.py", line 262, in solve_final_state
        ssc = self._collect_all_metadata(ssc)
      File "/usr/share/miniconda/lib/python3.8/site-packages/conda/common/io.py", line 88, in decorated
        return f(*args, **kwds)
      File "/usr/share/miniconda/lib/python3.8/site-packages/conda/core/solve.py", line 425, in _collect_all_metadata
        index, r = self._prepare(prepared_specs)
      File "/usr/share/miniconda/lib/python3.8/site-packages/conda/core/solve.py", line 1020, in _prepare
        reduced_index = get_reduced_index(self.prefix, self.channels,
      File "/usr/share/miniconda/lib/python3.8/site-packages/conda/core/index.py", line 276, in get_reduced_index
        new_records = SubdirData.query_all(spec, channels=channels, subdirs=subdirs,
      File "/usr/share/miniconda/lib/python3.8/site-packages/conda/core/subdir_data.py", line 120, in query_all
        result = tuple(concat(executor.map(subdir_query, channel_urls)))
      File "/usr/share/miniconda/lib/python3.8/concurrent/futures/_base.py", line 611, in result_iterator
        yield fs.pop().result()
      File "/usr/share/miniconda/lib/python3.8/concurrent/futures/_base.py", line 439, in result
        return self.__get_result()
      File "/usr/share/miniconda/lib/python3.8/concurrent/futures/_base.py", line 388, in __get_result
        raise self._exception
      File "/usr/share/miniconda/lib/python3.8/concurrent/futures/thread.py", line 57, in run
        result = self.fn(*self.args, **self.kwargs)
      File "/usr/share/miniconda/lib/python3.8/site-packages/conda/core/subdir_data.py", line 112, in <lambda>
        subdir_query = lambda url: tuple(SubdirData(Channel(url), repodata_fn=repodata_fn).query(
      File "/usr/share/miniconda/lib/python3.8/site-packages/conda/core/subdir_data.py", line 125, in query
        self.load()
      File "/usr/share/miniconda/lib/python3.8/site-packages/conda/core/subdir_data.py", line 189, in load
        _internal_state = self._load()
      File "/usr/share/miniconda/lib/python3.8/site-packages/conda/core/subdir_data.py", line 259, in _load
        raw_repodata_str = fetch_repodata_remote_request(
      File "/usr/share/miniconda/lib/python3.8/site-packages/conda/core/subdir_data.py", line 499, in fetch_repodata_remote_request
        resp = session.get(join_url(url, filename), headers=headers, proxies=session.proxies,
      File "/usr/share/miniconda/lib/python3.8/site-packages/requests/sessions.py", line 543, in get
        return self.request('GET', url, **kwargs)
      File "/usr/share/miniconda/lib/python3.8/site-packages/requests/sessions.py", line 530, in request
        resp = self.send(prep, **send_kwargs)
      File "/usr/share/miniconda/lib/python3.8/site-packages/requests/sessions.py", line 685, in send
        r.content
      File "/usr/share/miniconda/lib/python3.8/site-packages/requests/models.py", line 829, in content
        self._content = b''.join(self.iter_content(CONTENT_CHUNK_SIZE)) or b''
      File "/usr/share/miniconda/lib/python3.8/site-packages/requests/models.py", line 754, in generate
        raise ChunkedEncodingError(e)
    requests.exceptions.ChunkedEncodingError: ("Connection broken: ConnectionResetError(104, 'Connection reset by peer')", ConnectionResetError(104, 'Connection reset by peer'))

`$ /usr/share/miniconda/condabin/conda install --name base mamba=*`

  environment variables:
                 CIO_TEST=<not set>
                    CONDA=/usr/share/miniconda
           CONDA_PKGS_DIR=/home/runner/conda_pkgs_dir
               CONDA_ROOT=/usr/share/miniconda
           CURL_CA_BUNDLE=<not set>
      DEPLOYMENT_BASEPATH=/opt/runner
        GITHUB_EVENT_PATH=/home/runner/work/_temp/_github_workflow/event.json
              GITHUB_PATH=/home/runner/work/_temp/_runner_file_commands/add_path_9c73a400-b1a4-4
                          d6e-829b-30f49e9129a1
          LD_LIBRARY_PATH=/opt/hostedtoolcache/Python/3.8.10/x64/lib
                     PATH=/usr/share/miniconda/condabin:/opt/hostedtoolcache/Python/3.8.10/x64/b
                          in:/opt/hostedtoolcache/Python/3.8.10/x64:/home/linuxbrew/.linuxbrew/b
                          in:/home/linuxbrew/.linuxbrew/sbin:/home/runner/.local/bin:/opt/pipx_b
                          in:/usr/share/rust/.cargo/bin:/home/runner/.config/composer/vendor/bin
                          :/usr/local/.ghcup/bin:/home/runner/.dotnet/tools:/snap/bin:/usr/local
                          /sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/loc
                          al/games:/snap/bin
       REQUESTS_CA_BUNDLE=<not set>
        SELENIUM_JAR_PATH=/usr/share/java/selenium-server-standalone.jar
            SSL_CERT_FILE=<not set>
               SWIFT_PATH=/usr/share/swift/usr/bin
           pythonLocation=/opt/hostedtoolcache/Python/3.8.10/x64

     active environment : None
       user config file : /home/runner/.condarc
 populated config files : /home/runner/.condarc
          conda version : 4.9.2
    conda-build version : not installed
         python version : 3.8.5.final.0
       virtual packages : __glibc=2.31=0
                          __unix=0=0
                          __archspec=1=x86_64
       base environment : /usr/share/miniconda  (writable)
           channel URLs : https://conda.anaconda.org/conda-forge/linux-64
                          https://conda.anaconda.org/conda-forge/noarch
                          https://repo.anaconda.com/pkgs/main/linux-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/linux-64
                          https://repo.anaconda.com/pkgs/r/noarch
          package cache : /home/runner/conda_pkgs_dir
       envs directories : /usr/share/miniconda/envs
                          /home/runner/.conda/envs
               platform : linux-64
             user-agent : conda/4.9.2 requests/2.24.0 CPython/3.8.5 Linux/5.8.0-1033-azure ubuntu/20.04.2 glibc/2.31
                UID:GID : 1001:121
             netrc file : None
           offline mode : False

An unexpected error has occurred. Conda has prepared the above report.

Never mind, the error was from the CI machine. Fixed now.


Make getInitialProps in _app.tsx more type safety

We should follow the guide in this https://github.com/vercel/next.js/discussions/36832 discuss and add return type to getInitialProps method.

It seems to be already type safe enough – all used variables have correct type

OK


Add KCD Bengaluru talk to README

Add the recent KCD Bengaluru talk to the list of k8gb presentations
..

HOW TO RUN CI
---
By default, all the checks will be run automatically. Furthermore, when changing website-related stuff, the preview will be generated by the netlify bot.
Heavy tests
Add the heavy-tests label on this PR if you want full-blown tests that include more than 2-cluster scenarios.
Debug tests
If the test suite is failing for you, you may want to try triggering Re-run all jobs (top right) with debug logging enabled. It will also make the print debug action more verbose.

Good job @tamilhce 🚀 !


Improper rendering of header links when using sort_th in django-sorting-bootstrap

I discovered a bug in the link rendering while updating to the latest version of django-sorting-bootstrap. I see that the project is archived so I'm not sure if you are accepting changes but I'd be more than happy to create a pull request to fix it. It's just missing a closing tag in the template so it's creating three of the glyphicon links instead of one. Thanks.

@rmassoth go ahead, I just unarchived it. We can publish a release after that.

@rmassoth thanks for the patch, are you interested in being the maintainer of this package? Otherwise I will archive it again after releasing the bugfix version.


Unexpected values within code-style input table

🐞 Problem
The code-style actions is not properly rendering the inputs table. The logic implemented in the conf.py file for generating the table works fine. After some investigation with @Revathyvenugopal162, it looks like this issue is coming from the tabulate.tabulate function.

Note this is not affecting the actions. It is just a bug in a tool we use in our documentation.

Adding this to v6.1. So far, we are using tabulate for generating the RST tables. We could explore other options like prettytable or even rendering by our own.

Looks like prettytable does not support RST formatting. After trying with pytablewriter, the error is still present. This is really strange...


r (replace) throws Uncaught Type Error

Whenever I use r to replace a character vim-state throws Uncaught Type Error.

OS: OSX 10.9.3
Atom: 0.103.0
Vim-mode: 0.11.0

is this bug still there?

no, haven't noticed it for the last 1-2 months :)
On 5 April 2015 at 20:55, Jacek Kopecký<EMAIL_ADDRESS>wrote:

is this bug still there?
—
Reply to this email directly or view it on GitHub
https://github.com/atom/vim-mode/issues/320#issuecomment-89831942.

Just tried reproducing this and wasn't able to, and seems like other folks haven't seen this problem for a few months at least. Also, the autocomplete-plus package replaced the default autocomplete package and lots of issues were fixed, so I'm guessing this was fixed at some point.
Let me know if anyone can still reproduce the problem and please provide an example.


Fail run on windows using SDK 470.0.0 with pyhton 39

From CMD i'm trying this:

Install Python39 con Path C:\python39 (Version 3.9.13)
Install Python39 con Path C:\python27 (Version 2.7.18)
Install Google SDK with version Google Cloud SDK 470.0.0, app-engine-python 1.9.111
Download your copy of the file from the 'src' folder and overwrite the original file
Set CLOUDSDK_DEVAPPSERVER_PYTHON  with python 2 Path, using set CLOUDSDK_DEVAPPSERVER_PYTHON=C:\Python27\python.exe
try run dev_appserver usign a simple hello_world example, using dev_appserver.py app.yaml

When i tried this its generate the next exception:
Traceback (most recent call last):
File "C:\CloudSDK\google-cloud-sdk\bin\dev_appserver.py", line 13, in
from bootstrapping import bootstrapping
File "C:\CloudSDK\google-cloud-sdk\bin\bootstrapping\bootstrapping.py", line 24, in
from . import setup  # pylint:disable=g-import-not-at-top
File "C:\CloudSDK\google-cloud-sdk\bin\bootstrapping\setup.py", line 57, in
from googlecloudsdk.core.util import platforms
File "C:\CloudSDK\google-cloud-sdk\lib\googlecloudsdk_init_.py", line 23, in
import importlib.util
ImportError: No module named util
I Searched this and found that it's cause the version of python, but i'm not sure how to deal with that, can someone help me?

Hi,
Some breaking changes have been introduced into the newer versions of gcloud SDK. I'm yet to upgrade the patch to work with these newer versions (currently working on it, & hope to get it done in April).
I have gcloud SDK v429.0.0 on my windows machine and the patch works on it. I think someone said they're on v431.0.0 and it works for them (see this).
So, you can either wait for the updated patch or downgrade to one of the mentioned gcloud SDK versions.

A new version of the patch to support gcloud SDK v470.0.0 is now available here.
There is a known issue with the -python_virtualenv_path flag. When you use the flag, it gives an error on subsequent runs of your App (there's a permission denied error on the specified -python_virtualenv_path). The solution for now is to not use the flag until I come up with a fix for it.


Support for optional chaining?

According to the change log TypeScript 3.7 is bundled. Are all new features of 3.7 supported?
I'm trying to use optional chaining and get Expression expected error.
Atom TypeScript: 13.4.8
TypeScript: 3.7.4
Atom: 1.42.0 x64
OS: macOS Catalina 10.15.2

Remember that Atom-TypeScript will use whatever TypeScript installation it can find in the project's node_modules, and will only default to the bundled version if it can't find any. It reports which version it's currently using in the status bar, e.g.

Also, be aware that you likely need to restart Atom after updating TypeScript for it to pick up on the new version.
FWIW, everything works exactly as expected on my end:

Same issue for me.
Atom TypeScript: 13.4.8
TypeScript: 3.7.2
Atom: 1.42.0 x64
OS: macOS 10.15.1

As you see, the picked up version is 3.7.4 and the issue still persists. Are there any compiler options I should provide in tsconfig.json?

Please share apm list output, just to make sure we're not hunting ghosts. One particular thing to look out for is ide-typescript package being installed and enabled, because it does not support optional chaining, and will report it as error, and it also calls itself "typescript" in the IDE interface.
In case it's not some other package interfering, here's a minimal project that optional chaining should (i.e. it does on my end) work with: https://gist.github.com/lierdakil/d60962913651781250f7312b497d144a (you can git clone this URL).

ide-typescript was the actual problem!
Disabled the package, restarted Atom, and it's working now. Thanks for the help.


Crash when using any release mode but Debug

Hey there! I gave z_impact a go today with zig 0.13.0 and it works fine in debug mode, but the sample crashes when trying to compile release mode.
I built it like this:
zig build run -Dplatform=sokol -Doptimize=ReleaseSafe

Before I enabled symbols in release mode like that:
    // zimpact module
    mod_zi = b.addModule("zimpact", .{
        .root_source_file = .{ .cwd_relative = sdkPath("/src/zimpact/zimpact.zig") },
        .target = options.target,
        .optimize = options.optimize,
+        .strip = false,
    });

Here is the stacktrace:
>>> bt
#0  0x0000000000000000 in ?? ()
#1  0x00000000010558ca in entity.entityUpdate (
    entity=0x12bee28 <engine.entities_storage>)
    at /home/oka/dev/repos/z_impact/src/zimpact/entity.zig:210
#2  entity.entitiesUpdate () at /home/oka/dev/repos/z_impact/src/zimpact/entity.zig:459
#3  engine.Engine.sceneBaseUpdate ()
    at /home/oka/dev/repos/z_impact/src/zimpact/engine.zig:250
#4  0x0000000001054dc6 in scenes.game.update ()
    at /home/oka/dev/repos/z_impact/samples/zdrop/scenes/game.zig:97
#5  0x0000000001035b53 in engine.Engine.update ()
    at /home/oka/dev/repos/z_impact/src/zimpact/engine.zig:180
#6  0x000000000107b443 in _sapp_call_frame ()
    at /home/oka/.cache/zig/p/1220f044556b4cbe92f797dece26d1418bbf67f8d7311e1b0040049690d1
044b66e8/src/sokol/c/sokol_app.h:3013
#7  _sapp_frame ()
    at /home/oka/.cache/zig/p/1220f044556b4cbe92f797dece26d1418bbf67f8d7311e1b0040049690d1
044b66e8/src/sokol/c/sokol_app.h:3214
#8  _sapp_linux_run (desc=<optimized out>)
    at /home/oka/.cache/zig/p/1220f044556b4cbe92f797dece26d1418bbf67f8d7311e1b0040049690d1
044b66e8/src/sokol/c/sokol_app.h:11164
#9  0x000000000102ef00 in app.run ()
    at /home/oka/.cache/zig/p/1220f044556b4cbe92f797dece26d1418bbf67f8d7311e1b0040049690d1
044b66e8/src/sokol/app.zig:548
#10 platform_sokol.run ()
    at /home/oka/dev/repos/z_impact/src/zimpact/platform_sokol.zig:318
#11 engine.Engine.run () at /home/oka/dev/repos/z_impact/src/zimpact/engine.zig:113
#12 main.main () at main.zig:46
#13 start.callMain () at /usr/lib/zig/std/start.zig:514
#14 start.callMainWithArgs () at /usr/lib/zig/std/start.zig:482
#15 start.main (c_argc=1, c_argv=<optimized out>, c_envp=<optimized out>)
    at **/usr/lib/zig/std/start.zig:497**

It seems like the vtables for the entities don't get initalized properly in release mode. I wanna get back into zig again at some point and might try to fix it later, but not sure when that would be.
I printed the vtab really quickly before update is called and it seems to be null(0) in release mode:
Update entity entity.EntityVtab{ .load = fn () void@0, .init = fn (*entity.Entity) void@0,
 .settings = fn (*entity.Entity, array_hash_map.ArrayHashMap([]const u8,json.dynamic.Value
,array_hash_map.StringContext,true)) void@0, .update = fn (*entity.Entity) void@0, .draw =
 fn (*entity.Entity, types.Vec2) void@0, .kill = fn (*entity.Entity) void@0, .touch = fn (
*entity.Entity, *entity.Entity) void@0, .collide = fn (*entity.Entity, types.Vec2, ?trace.
Trace) void@0, .damage = fn (*entity.Entity, *entity.Entity, f32) void@0, .trigger = fn (*
entity.Entity, *entity.Entity) void@0, .message = fn (*entity.Entity, ?*anyopaque, ?*anyop
aque) void@0 }

BTW: I am pretty excited about high_impact and z_impact. Thanks for working on it!

Thanks for this detailed issue, that's quite interesting.
I made different tests:

it works with z_biolab, all release modes
it works if I modify this:

pub const UEntity = union(EntityKind) {
    coin: struct { foo: bool },
    player: struct { bar: bool },
};

It doesn't work with:
pub const UEntity = union(EntityKind) {
    coin: struct {},
    player: struct {},
};

I suppose this is due to optimization.
I'll try to fix this (if I can, I'm still new to zig).

Thanks to the zig community, this issue has been fixed.


Improve license metadata

The license is not clearly communicated in the project. This PR attempts to improve that. When I found some other long-hanging fruits with metadata, I fixed them as well.
The largest part of the work was making the project REUSE compliant and thereby also marking which files are under the MIT license and a different copyright holder.

Also we should reinstate proper CI testing before we engage in any changes.

Max, since there are 571 pending PRs I wonder if we should not review these first to avoid creating a merge conflict problem?

Looking at the PRs, most of them are version upgrades. But you are right, going through the list is a good idea. I'm fine with keeping this PR open for a while.


Access blocked: project-367116221053’s request is invalid

Hope this is not an error from the application. But I'm getting this when trying to init the session after opening the link:
Error 400: invalid_request
The out-of-band (OOB) flow has been blocked in order to keep users secure. Follow the Out-of-Band (OOB) flow migration guide linked in the developer docs below to migrate your app to an alternative method.
Request details: redirect_uri=urn:ietf:wg:oauth:2.0:oob
Related developer documentation

I think this is helpful:
https://groups.google.com/g/omegaup-soporte/c/kwF1Zu_xfow

same error

2 months later this issue is still not yet fixed it seems 😂😂😂 I'm also facing it rn

issue still not fixed :(

Just encountered the same issue

+1

+1

wow, I came to report this issue thinking it was a recent problem but as far as I can see this problem has been around for almost a year now... is the project abandoned at this point?

Facing issue now as well

Still facing this issue. Any idea of other libraries that can be used instead?

same error
Maybe google changed their API. :(

A +1 as I am still seeing this. Given the silence I presume gshell is now effectively dead.

A +1 as I am still seeing this. Given the silence I presume gshell is now effectively dead.

I am using rclone now btw.

+1


Check readline feature by require

Windows can have readline library, and non-Windows may not have
it.

This looks good but unfortunately readline specs don't seem to work well on Windows.
The CI seems to get stuck, to know where you can change -ff by -fs in appveyor.yml.

Maybe appveyor fails causes rb-readline bundled in RubyInstaller.


Fix defcustom for straight-check-for-modifications

A :type of '(list ...) fixes the number of elements, so anything other than a singleton list resulted in (mismatch) in the Custom buffer.  So change to '(repeat ...) to allow a variable number of symbols in the list.

I wonder if there is a tool that checks all your defcustoms to see if the default values meet the :type specifications. It would not be perfect, but it would catch some of these bugs.

That's an interesting idea. I do some simple type checking for doct's functions with a kind of light fuzzing:
https://github.com/progfolio/doct/blob/dabb30ebea866ef225b81561c8265d740b1e81c3/tests/doct-test.el#L148-L165


internal import issues with libv4l feature

I was having trouble with the default feature setting (v4l2). When I tried to use the libv4l feature instead, it seems that some necessary internals were configured out. (I suggest setting up CI with cargo-all-features - helps a lot with these kinds of problems!)
In any case, I'm using Fedora 40 with the newest packages. The Fedora package libv4l-devel is installed. Please let me know if you need any more info about the system configuration.
Here's the issue:
Cargo.toml
[package]
name = "test_v4l_backend"
version = "0.1.0"
edition = "2021"

[dependencies]
anyhow = "1.0.86"
image = "0.25.2"
tracing = "0.1.40"
tracing-subscriber = "0.3.18"
v4l = { version = "0.14.0", features = ["libv4l"] }

cargo run output:
barrett@farts ~/D/p/s/test_v4l_backend (main) [101]> cargo clean
     Removed 1961 files, 925.5MiB total
barrett@farts ~/D/p/s/test_v4l_backend (main)> cargo run
   Compiling proc-macro2 v1.0.86
   Compiling unicode-ident v1.0.12
   Compiling cfg-if v1.0.0
   Compiling autocfg v1.3.0
   Compiling memchr v2.7.4
   Compiling minimal-lexical v0.2.1
   Compiling glob v0.3.1
   Compiling rustix v0.38.35
   Compiling prettyplease v0.2.22
   Compiling libc v0.2.158
   Compiling regex-syntax v0.8.4
   Compiling linux-raw-sys v0.4.14
   Compiling lazy_static v1.5.0
   Compiling bitflags v1.3.2
   Compiling bitflags v2.6.0
   Compiling bindgen v0.65.1
   Compiling libloading v0.8.5
   Compiling either v1.13.0
   Compiling home v0.5.9
   Compiling crossbeam-utils v0.8.20
   Compiling once_cell v1.19.0
   Compiling log v0.4.22
   Compiling shlex v1.3.0
   Compiling lazycell v1.3.0
   Compiling peeking_take_while v0.1.2
   Compiling rustc-hash v1.1.0
   Compiling simd-adler32 v0.3.7
   Compiling anyhow v1.0.86
   Compiling thiserror v1.0.63
   Compiling adler2 v2.0.0
   Compiling num-traits v0.2.19
   Compiling lock_api v0.4.12
   Compiling clang-sys v1.8.1
   Compiling paste v1.0.15
   Compiling rayon-core v1.12.1
   Compiling built v0.7.4
   Compiling aligned-vec v0.5.0
   Compiling nom v7.1.3
   Compiling scopeguard v1.2.0
   Compiling arrayvec v0.7.6
   Compiling miniz_oxide v0.8.0
   Compiling quote v1.0.37
   Compiling crossbeam-epoch v0.9.18
   Compiling crc32fast v1.4.2
   Compiling rav1e v0.7.1
   Compiling syn v2.0.76
   Compiling adler v1.0.2
   Compiling crossbeam-deque v0.8.5
   Compiling bytemuck v1.17.1
   Compiling simd_helpers v0.1.0
   Compiling flate2 v1.0.33
   Compiling miniz_oxide v0.7.4
   Compiling spin v0.9.8
   Compiling itertools v0.12.1
   Compiling tracing-core v0.1.32
   Compiling maybe-rayon v0.1.1
   Compiling num-integer v0.1.46
   Compiling v_frame v0.3.8
   Compiling imgref v1.10.1
   Compiling new_debug_unreachable v1.0.6
   Compiling weezl v0.1.8
   Compiling bitstream-io v2.5.3
   Compiling noop_proc_macro v0.3.0
   Compiling num-bigint v0.4.6
   Compiling smallvec v1.13.2
   Compiling quick-error v2.0.1
   Compiling regex-automata v0.4.7
   Compiling loop9 v0.1.5
   Compiling flume v0.11.0
   Compiling rgb v0.8.48
   Compiling avif-serialize v0.8.1
   Compiling zune-inflate v0.2.54
   Compiling which v4.4.2
   Compiling fdeflate v0.3.4
   Compiling half v2.4.1
   Compiling cexpr v0.6.0
   Compiling zune-core v0.4.12
   Compiling overload v0.1.1
   Compiling jpeg-decoder v0.3.1
   Compiling lebe v0.5.2
   Compiling byteorder-lite v0.1.0
   Compiling color_quant v1.1.0
   Compiling bit_field v0.10.2
   Compiling zune-jpeg v0.4.13
   Compiling png v0.17.13
   Compiling nu-ansi-term v0.46.0
   Compiling image-webp v0.1.3
   Compiling gif v0.13.1
   Compiling exr v1.72.0
   Compiling tracing-log v0.2.0
   Compiling rayon v1.10.0
   Compiling qoi v0.4.1
   Compiling num-rational v0.4.2
   Compiling thread_local v1.1.8
   Compiling tiff v0.9.1
   Compiling sharded-slab v0.1.7
   Compiling pin-project-lite v0.2.14
   Compiling av1-grain v0.2.3
   Compiling regex v1.10.6
   Compiling tracing-subscriber v0.3.18
   Compiling thiserror-impl v1.0.63
   Compiling profiling-procmacros v1.0.15
   Compiling arg_enum_proc_macro v0.3.4
   Compiling num-derive v0.4.2
   Compiling tracing-attributes v0.1.27
   Compiling profiling v1.0.15
   Compiling tracing v0.1.40
   Compiling v4l-sys v0.3.0
   Compiling v4l2-sys-mit v0.3.0
   Compiling ravif v0.11.10
   Compiling image v0.25.2
   Compiling v4l v0.14.0
error[E0428]: the name `detail` is defined multiple times
  --> /home/barrett/.cargo/registry/src/index.crates.io-6f17d22bba15001f/v4l-0.14.0/src/v4l2/api.rs:59:1
   |
8  | mod detail {
   | ---------- previous definition of the module `detail` here
...
59 | mod detail {
   | ^^^^^^^^^^ `detail` redefined here
   |
   = note: `detail` must be defined only once in the type namespace of this module

error[E0252]: the name `v4l_sys` is defined multiple times
  --> /home/barrett/.cargo/registry/src/index.crates.io-6f17d22bba15001f/v4l-0.14.0/src/lib.rs:74:9
   |
71 | pub use v4l_sys;
   |         ------- previous import of the module `v4l_sys` here
...
74 | pub use v4l2_sys as v4l_sys;
   |         ^^^^^^^^^^^^^^^^^^^ `v4l_sys` reimported here
   |
   = note: `v4l_sys` must be defined only once in the type namespace of this module
help: you can use `as` to change the binding name of the import
   |
74 | pub use v4l2_sys as other_v4l_sys;
   |                  ~~~~~~~~~~~~~~~~

error[E0425]: cannot find function `v4l2_open` in this scope
  --> /home/barrett/.cargo/registry/src/index.crates.io-6f17d22bba15001f/v4l-0.14.0/src/v4l2/api.rs:14:9
   |
14 |         v4l2_open(path, flags)
   |         ^^^^^^^^^ not found in this scope
   |
help: consider importing this function
   |
9  +     use v4l_sys::v4l2_open;
   |

error[E0425]: cannot find function `v4l2_close` in this scope
  --> /home/barrett/.cargo/registry/src/index.crates.io-6f17d22bba15001f/v4l-0.14.0/src/v4l2/api.rs:17:9
   |
17 |         v4l2_close(fd)
   |         ^^^^^^^^^^ not found in this scope
   |
help: consider importing this function
   |
9  +     use v4l_sys::v4l2_close;
   |

error[E0425]: cannot find function `v4l2_ioctl` in this scope
  --> /home/barrett/.cargo/registry/src/index.crates.io-6f17d22bba15001f/v4l-0.14.0/src/v4l2/api.rs:27:9
   |
27 |         v4l2_ioctl(
   |         ^^^^^^^^^^ not found in this scope
   |
help: consider importing this function
   |
9  +     use v4l_sys::v4l2_ioctl;
   |

error[E0425]: cannot find function `v4l2_mmap` in this scope
  --> /home/barrett/.cargo/registry/src/index.crates.io-6f17d22bba15001f/v4l-0.14.0/src/v4l2/api.rs:44:9
   |
44 |         v4l2_mmap(
   |         ^^^^^^^^^ not found in this scope
   |
help: consider importing this function
   |
9  +     use v4l_sys::v4l2_mmap;
   |

error[E0425]: cannot find function `v4l2_munmap` in this scope
  --> /home/barrett/.cargo/registry/src/index.crates.io-6f17d22bba15001f/v4l-0.14.0/src/v4l2/api.rs:54:9
   |
54 |         v4l2_munmap(start, length.try_into().expect("usize -> c size_t failed"))
   |         ^^^^^^^^^^^ not found in this scope
   |
help: consider importing this function
   |
9  +     use v4l_sys::v4l2_munmap;
   |

Some errors have detailed explanations: E0252, E0425, E0428.
For more information about an error, try `rustc --explain E0252`.
error: could not compile `v4l` (lib) due to 7 previous errors
warning: build failed, waiting for other jobs to finish...
barrett@farts ~/D/p/s/test_v4l_backend (main) [101]>

Also, please note that Cargo's features are intended to be additive. If you have two incompatible features, you may wish to add a compile_error! case when both are enabled: https://doc.rust-lang.org/cargo/reference/features.html#mutually-exclusive-features

This is somewhat documented at https://github.com/raymanfx/libv4l-rs?tab=readme-ov-file#dependencies. A compile_error!() would be nice to have (PR welcome!), but the "additive feature requirement" is a known cargo limitation for crate setups like this that have to pick one or the other.

Thanks - I'll look into a PR in the coming days!
For now, note that adding default-features = false alleviates the problem. That could be clear for experienced users, but just wanted to write it down for clarity. :)

Feel free to shoot a PR to implement the compile_error!() :)


Fix opening bottom right version link in external browser

Resolves https://github.com/KittyCAD/modeling-app/issues/3632

do we also need this on links to kcl docs etc


confused about the point_triangle_sq_unsigned function

I don't quite understand this function. Can you give me some information on its principles?
static double tmd::point_triangle_sq_unsigned（）.

Hi,
I documented the function in the original source code. When you give a point in space and the three vertices of a triangle, this function will return the squared distance from the point to the triangle and also which was the nearest feature of the triangle to the point and also the coordinates of the closest point on the triangle to your original query point.
I hope this helps :)

Thanks a lot for your reply and sorry for the delay,  I read your code and I found that your method of dividing the seven areas of the triangle according to the extension lines of the sides is too complicated. I learned that the seven areas can be divided according to the perpendiculars of the sides of the triangle, so that the code should be simpler, I'm not sure if this is possible, can you help me figure it out? In the article you mentioned, they are also divided according to vertical
（Generating Signed Distance Fields From Triangle Meshes）
http://www2.imm.dtu.dk/pubdb/edoc/imm1289.pdf
（iquilezles triangle distance）
https://iquilezles.org/articles/distfunctions/
@JoseAntFer

The code you refer to was inherited from a different project and I did not write it myself. It has been extensively tested and used in this and other applications, but I sadly cannot help you untangling it. Also, I don't really have spare time to simplifying it or improving it in any way at the moment.
In any case, thank you for pointing it out. I will have it in mind.

The code you refer to was inherited from a different project and I did not write it myself. It has been extensively tested and used in this and other applications, but I sadly cannot help you untangling it. Also, I don't really have spare time to simplifying it or improving it in any way at the moment.
In any case, thank you for pointing it out. I will have it in mind.

Thank you for your replying! I will try to do this work.

The code you refer to was inherited from a different project and I did not write it myself. It has been extensively tested and used in this and other applications, but I sadly cannot help you untangling it. Also, I don't really have spare time to simplifying it or improving it in any way at the moment.
In any case, thank you for pointing it out. I will have it in mind.

Thank you for your replying! maybe I will do this work.


Graph connectivities metric

Hi there,
shouldnt graph connectivity use adata.obsp["distances"] or some sort of shared nearest neighbors as the graph, since that adata.obsp["connectivities"] might connect distant nodes together to ensure that the whole graph is connected and lead to spurious edges?

Hi @Chengwei94,
If you check the connectivities matrix you will see that only the nearest neighbours of any node have a non-zero connectivity (the same nodes that also have a reported distance). Thus, the whole graph will not necessarily be connected when using connectivities. Connetivities are a function of distance (I would have to look up exactly what that function is) that is scaled between 0 and 1 and is inversely related to distance. Thus, it is more fitting than distances here.


Dismiss loading dialog on authentication method picker when authentication fails

We do not correctly dismiss the loading dialog on the authentiation method picker screen if a chosen authentication method fails, here. Ensure that on failure the dialog is dismissed, the pertinent details of the failure are logged, and that the user is notified via a toast / snackbar what happened.

Fixed by b605f0c6cc7b1db1808bb59c5c3cc20d90d0a209

This issue is now fixed in version 0.4.1, please update your dependencies and thanks for the patience!


when installing jiti: Deprecation Warning: punycode module usage

Environment
node v22.4.0
jiti version: 1.21.6
Reproduction
npm install jiti
Describe the bug
below deprecation warning is displayed
(node:722838) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead. (Use "node --trace-deprecation ..." to show where the warning was created)
Additional context
This warning suggests that the punycode module, which is being used either directly by jiti or by one of its dependencies, is deprecated in Node.js.
Logs
No response

Can you please provide a reproduction?


Turn 404s into 403s?

In the specific parameter checking sections, rather than returning 404: Not Found, it would be better to return 403: Forbidden.

@sstults think this can be closed?

Yep!


feat: Bytes

Implementing BytesLib in Huff

is for https://github.com/pentagonxyz/huffmate/issues/25

this looks great to me, really cool actually.  would like to get another set of eyes on this before merging.
https://github.com/pentagonxyz/huffmate/pull/88#issuecomment-1407740584


Added retrolambda support

Added retrolambda support and replaced all the possible retrolambda code

Can one of the admins verify this patch?

Thanks for the pull request but we decided not to use retrolambda. We are aware the resulting code is nicer using lambda expressions but adding this unsupported language feature via retrolamda can sometimes cause problems.
Also, generally we don't accept pull requests that change the current project architecture and/or include new libraries or tools.

@ivacf Could you quickly explain what kind of problems do you have in mind?


Implement fill opacity for shading patterns in the SVG back-end

In the PDF file from the issue below, the fill alpha (ca) is set before drawing the circles using the setGState operator. Doing so causes the global alpha to be set on the canvas' context for the canvas back-end, but this was not handled in the SVG back-end. This patch fixes that by taking the fill opacity into account when drawing shading patterns in the same way as done elsewhere so it is only included if the value is non-default.
Fixes #11812.

You can test this by opening the preview viewer below and running PDFViewerApplication.preferences.set('renderer', 'svg'); in the console. If you refresh the page and open the file from the issue, you'll see three circles with different opacities now.

/botio-linux preview

Good point; I have amended the commit and PR message. Thanks!

Good point; I have amended the commit and PR message.

Thank you; as an aside you do have to wonder why anyone thought it'd be a good idea to specify two separate operators with the same name and differing only in their casing...


Won't run

No matter how I try to run it, I used your installation instructions but I get an error:
File "bot.py", line 120
except ValueError, KeyError:
^
SyntaxError: invalid syntax

Or if I use ./bot.py instead of python bot.py, I get
Traceback (most recent call last):
File "./bot.py", line 6, in
import queue
ImportError: No module named queue

@reallat This software should be run by python2

Still doesn't work. Running in python 2.7.14 I get
File "/Users/developeraccount/Desktop/HQBot-master/bot.py", line 4, in
import six
ImportError: No module named six

Actually, I fixed it but I got
./bot.py -v -i test_question2.png
[~] Filename: ./test_question2.png
[*] Found 10 blocks
[?] Question: What is the act of performing music in public places for tips?
[-] <HttpError 400 when requesting https://www.googleapis.com/customsearch/v1?q=What+is+the+act+of+performing+music+in+public+places+for+tips%3F&alt=json&cx=011154592724722453140%3Achwi_oz7tzq&num=10&key=7d8b1da0be71de6027dea83c84e43bc368824dc3 returned "Bad Request">
[-] NameError: global name 'queue' is not defined

I just fixed this issue in the latest commit


Adds waiter files (kitchen to come in separate PR)

This is the initial push of waiter source, docs, tests, etc. We are deliberately putting this in a waiter sub-directory. A separate PR will introduce the kitchen sub-directory.

Spot checked the last commit. Looks good!


the Haste package 'react-native-vector-icons'

error: bundling failed: Error: While resolving module react-native-vector-icons /Ionicons, the Haste package react-native-vector-icons was found. However the
module Ionicons could not be found within the package.

Dup of #626
it's an RN issue https://github.com/facebook/react-native/issues/17610
Will be fixed by https://github.com/facebook/react-native/pull/17672
Workaround https://github.com/oblador/react-native-vector-icons/issues/626#issuecomment-362386341

Thanks @MoOx for the helpful summary.  :)

@MoOx

Will be fixed by facebook/react-native#17672 is it permanent fix?

@mtt87 Thanks it worked for me.

@Yandamuri yes it will. Nothing is wrong in this package. It's RN repo that contains the name of this package (and it should not).

thanks @mtt87 .It works like a charm
💯

4 months later and this still isn't fixed in React Native 0.53.3.
Quick fix as others point out is to run rm ./node_modules/react-native/local-cli/core/__fixtures__/files/package.json but you'll need to do this after every fresh npm install.
So, to run this automatically, you can add it to your package.json as a postinstall script:
package.json
"scripts": {
  "postinstall": "rm ./node_modules/react-native/local-cli/core/__fixtures__/files/package.json"
}

I found the solution.Delete this file.
rm ./node_modules/react-native/local-cli/core/fixtures/files/package.json
Delete file package.json

I delete this file but error continued. :c

@13ArturBruno if on RN0.52+ you need ``rm node_modules/react-native/local-cli/core/fixtures/files/package.json`


Switch submodules to use https instead of ssh

This pull requests modifies git modules to use HTTPS instead of SSH. Since these repositories are public it makes CI systems happy whenever they do not need to use SSH for cloning the repositories.

Thanks!


[e2e] update centos7 AMIs

What does this PR do?

Update CentOS 7 AMIs in 7.54.x branch
Motivation

incident-28477
On June 30th CentOS 7 reached EOL and dropped their legacy mirror list. These AMIs are custom and have the new supported mirror list properly configured.
Additional Notes

Partial backport of https://github.com/DataDog/datadog-agent/pull/27197
I had to bumo test-infra-definitions as we release images only from main currently. This changed some APIs, changes are minimal.
Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Does Meltdown and Spectre affect this paradigm ?

Is this the best advice info-sec professionals should provide ?

By avoiding logic altogether, nocode does not trigger any branch prediction, or any other insecure processing maneuver.


fix assertion failure when database is specified with no URL path

Scope & Purpose
Fix assertion failure when database is specified without URL path (e.g. /_db/system). In this case, in maintainer mode an assertion failure was triggered, but it didn't have any effect in non-maintainer
mode.

[x] :hankey: Bugfix (requires CHANGELOG entry)

Backports:

[x] No backports required

Testing & Verification

[x] This change is a trivial rework / code cleanup without any test coverage.
[x] The behavior in this PR was manually tested

Link to Jenkins PR run:
http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/13076/

Tests blue


Automated backport of #3156: Explicitly disable BGP export for Calico IPPools

Backport of #3156 on release-0.18.
#3156: Explicitly disable BGP export for Calico IPPools
For details on the backport process, see the backport requests page.

cc @aswinsuryan @vthapar


drivers: flash: stm32h7: fix clearing of erased sector number

This fixes the logic in erase_sector() for clearing the previous
sector number. The logic was reversed, clearing bits it should not
clear and keeping previous bits of the sector number. In practice this
does not seem to have had any effect on the current functionality, but
it will start to matter later if e.g. flash interrupts are enabled.

@nicovince, can you have a look ?

Ok for me.

@nvincent-vossloh Could you approve formally ?

@nvincent-vossloh Could you approve formally ?

Just did, but apparently it requires an authorized reviewer :)

@nvincent-vossloh Could you approve formally ?

Just did, but apparently it requires an authorized reviewer :)

Thanks, that will do.


Support Swift Package Manager

Hello, I checked the "Aquaman" framework and added it because it does not support "SPM".
Check it out and if there's no problem, merge and release it.
Have a nice day.

@bugkingK If you want to use menuview quickly, you can take a look at https://github.com/bawn/Aquaman/blob/0.0.6/Aquaman-Demo/MenuItemView.swift


msg.args() is not intuitive

It's weird behavior that the following command:
/cmd
msg.args() returns "" correctly, but when you try to split it, msg.args(2) returns ['']. It should return [], as there are no arguments.

That behaviour is consistent with String#split(...).
Yeah, I suppose it would be more intuitive to return [], I'll change it.

Just realized -- maybe it's an idea to keep the msg.args() consistent with string.split() and provide a msg.argv as an array with the intuitive argument list?

No, I think this is good.
msg.args(N) could be understood as msg.text.split(" ").slice(1),
so if msg.text = "/cmd" it makes sense to return [].


Date time conversion happening automatically

Hello,
I'm seeing a problem when sending a Page event with the library.
Inside the properties object I pass a property with a value like this one: 2020-01-16 14:10:59 which should be kept as a string, but on the debugger I see a different value 2020-01-16T13:10:59.000Z so it seems like there is a conversion happening in the background.
Is it possible to keep the string as the original?
Thank you.

@matteopey if still an issue, does this happen to specific properties or every custom property you set?

After looking into this, there is an intentional conversion happening on strings that can be parsed to a date to keep the semantic meaning of the date value.


Update Pages “home”

Automatically generated by Netlify CMS

👷 Deploy Preview for strong-beijinho-c4d917 processing.

Name
Link

🔨 Latest commit
41b50f5b97d7ec1b37b1b808f38de2bf95fddfd8

🔍 Latest deploy log
https://app.netlify.com/sites/strong-beijinho-c4d917/deploys/65ebabdec7b6270008806002


gifski: 1.10.3 -> 1.11.0, add figsoda as a maintainer

Diff: https://github.com/ImageOptim/gifski/compare/1.10.3...1.11.0
Changelog: https://github.com/ImageOptim/gifski/releases/tag/1.11.0
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 229508 run on aarch64-darwin 1

1 package built:

gifski


Create Napkin Diagram

Use tools like Draw.io

Please find the attached image for the napkin diagram. Feedbacks are most welcome.

@shanki07 , Good work.
Some concerns:-

As discussed during planning, we decided to provide an example of "Open Weather Data" like NEXRAD, please try to put it in there.
We have an idea that parameters will be more than only date for selection, so you can use parameters as:-
- Radar-Station
- Date & Time
- Property(Let's say reflectivity)
Perhaps we should use these.
In the Visualization window, if we can also add map with land and sea visible, here it feels like all the representation is weather data representation without mapping it on Earth Map.

Please feel free to disagree on the concerns.
@niravraje , Do you agree?

@shanki07 Looks simple and good!
I agree with @rajdeepc2792's suggestions.
I had initially also thought of having a box/container around "parameter selection" and "visualization" denoting our client-side. But this looks good as well and serves the purpose.
Some sample user icons we might want to use:

@rajdeepc2792 @shanki07 Just wanted to update our napkin diagram as the images were a bit blurry. Also changed a few icons here and there which I found on draw.io. Could you both review and LMK if this looks good?


Error when running AudioWhisper inference

I did a fine-tune and training for audioWhisper but get following error when running the /generate endpoint.
The attention mask and the pad token id were not set. As a consequence, you may observe unexpected behavior. Please pass your input's `attention_mask` to obtain reliable results.
Setting `pad_token_id` to `eos_token_id`:2 for open-end generation.
The attention mask is not set and cannot be inferred from input because pad token is same as eos token. As a consequence, you may observe unexpected behavior. Please pass your input's `attention_mask` to obtain reliable results.
ERROR:serve_model:Exception on /generate [POST]
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/dist-packages/flask/app.py", line 1473, in wsgi_app
    response = self.full_dispatch_request()
  File "/usr/local/lib/python3.10/dist-packages/flask/app.py", line 882, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/usr/local/lib/python3.10/dist-packages/flask/app.py", line 880, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/local/lib/python3.10/dist-packages/flask/app.py", line 865, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)  # type: ignore[no-any-return]
  File "/workspace/multi_token/scripts/serve_model.py", line 46, in generate
    output_ids = model.generate(
  File "/usr/local/lib/python3.10/dist-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/transformers/generation/utils.py", line 2024, in generate
    result = self._sample(
  File "/usr/local/lib/python3.10/dist-packages/transformers/generation/utils.py", line 2982, in _sample
    outputs = self(**model_inputs, return_dict=True)
  File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1527, in _call_impl
    return forward_call(*args, **kwargs)
  File "/workspace/multi_token/multi_token/language_models/mistral.py", line 85, in forward
    ) = self.prepare_inputs_labels_for_multimodal(
  File "/workspace/multi_token/multi_token/language_models/base_model.py", line 101, in prepare_inputs_labels_for_multimodal
    past_key_values is None
AssertionError: We shouldn't have cached keys if this is the first instruction pass

I am using
python scripts/serve_model.py \
    --model_name_or_path mistralai/Mistral-7B-Instruct-v0.1 \
    --model_lora_path sshh12/Mistral-7B-LoRA-AudioWhisper \
    --port 7860

I have set the model name to my pretrained checkpoint model without any change in error.

Hey! I'm not super sure what's happening here. Did it work with a model that was already trained in the model zoo from the readme?
Potentially try use_cache=False in the serving script.


Merge pull request #1 from dangdangdotcom/master

update from origin

update

Coverage remained the same at 90.15% when pulling c6fb2d8219e20230d8cb969d765f714cae141950 on xydaxia0:master into 70b8581ffd4dbe0dedc9132e6d44aae7d7b10516 on dangdangdotcom:master.

Coverage remained the same at 90.15% when pulling c6fb2d8219e20230d8cb969d765f714cae141950 on xydaxia0:master into 70b8581ffd4dbe0dedc9132e6d44aae7d7b10516 on dangdangdotcom:master.

您的误操作给我们带来了困扰，请不要提交无意义的pull request


Fix borked detail elements in documentation.

What's this PR do?
This pull request fixes some formatting on the documentation pages that broke a while back.
How should this be reviewed?
📚
Checklist

[ ] Documentation added for changed endpoints.
[ ] Tests added for new features/bug fixes.
[ ] Post a message in #api if this includes something that causes a rebuild!

Looks like some <strong> changes 💪


Initialization Exception [1.16.4] [4.4.1]

Hi, It's me again but this time Apotheosis failed to load during common_setup. Here's the crash report and log.
Crash report:
crash-2021-01-11_04.37.55-fml.txt
Log:
latest.log
Also can you please take a look at my first report even tho it's totally different than this one? That'll be much appreciated if you do but before that could you fix this issue? Or else I'll have to stop playin with Apotheosis till this issue has been resolved....

This is an issue in MoreVanillaWeapons

This is an issue in MoreVanillaWeapons


Migrate to pnpm

This pull request migrates the package manager from yarn to pnpm.

coverage: 100.0% (+0.1%) from 99.866%
when pulling e4d750e743de83d813b8cb1e351f8128ffcd024b on migrate_to_pnpm
into 0b2eb9768239604c9b5a3221b3c8c27bd2206819 on master.