Every call to cargo hakai crashes

Hello,
I don't know, what I did with my project - but it crashes cargo hakari everytime I call it.
It doesn't matter what I do so:
cargo hakari generate

does not work, and so does
cargo hakari manage-deps

and even
cargo hakari disable
# and
cargo hakari remove-deps

I manually removed the workspace-hack crate and tried to re-generate with:
cargo hakari init

But get the same error. This is the backtrace of the error:
The application panicked (crashed).
Message:  at least one dependency instance
Location: guppy/src/graph/build.rs:749

  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
                                ⋮ 6 frames hidden ⋮
   7: core::panicking::panic_display::hd8c516c36ffd47b9
      at <unknown source file>:<unknown line>
   8: core::option::expect_failed::hcf48fdb9c93a315f
      at <unknown source file>:<unknown line>
   9: guppy::graph::build::<impl guppy::graph::graph_impl::PackageLinkImpl>::new::hedf2670bfc5d735a
      at <unknown source file>:<unknown line>
  10: guppy::graph::build::GraphBuildState::process_package::h1e686e1af0aa23dc
      at <unknown source file>:<unknown line>
  11: <core::iter::adapters::map::Map<I,F> as core::iter::traits::iterator::Iterator>::try_fold::h065c206c794d6246
      at <unknown source file>:<unknown line>
  12: <std::collections::hash::map::HashMap<K,V,S> as core::iter::traits::collect::FromIterator<(K,V)>>::from_iter::h005752c8e4328f54
      at <unknown source file>:<unknown line>
  13: guppy::graph::graph_impl::PackageGraph::from_metadata::hd00ea1052109d3b2
      at <unknown source file>:<unknown line>
  14: guppy::metadata_command::MetadataCommand::build_graph::hb4eb386b1a3608c3
      at <unknown source file>:<unknown line>
  15: cargo_hakari::command::Command::exec::h7a5b849e3e609f76
      at <unknown source file>:<unknown line>
  16: cargo_hakari::command::Args::exec::h39f6b998ce719c52
      at <unknown source file>:<unknown line>
  17: cargo_hakari::main::h0114ffb1046d9c78
      at <unknown source file>:<unknown line>
  18: std::sys_common::backtrace::__rust_begin_short_backtrace::h3fea250e0aeb62b9
      at <unknown source file>:<unknown line>
  19: std::rt::lang_start::{{closure}}::h07d4fa1872ec0b13
      at <unknown source file>:<unknown line>
  20: std::panicking::try::h9134436c64049e5f
      at <unknown source file>:<unknown line>
  21: std::rt::lang_start_internal::hf4417b67ea9bae52
      at <unknown source file>:<unknown line>
  22: main<unknown>
      at <unknown source file>:<unknown line>
  23: __libc_start_call_main<unknown>
      at <unknown source file>:<unknown line>
  24: __libc_start_main@@GLIBC_2.34<unknown>
      at <unknown source file>:<unknown line>
  25: _start<unknown>
      at <unknown source file>:<unknown line>

Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.

Please let me know, if you need any additional inforamation.

Hi there --
This looks like an issue that has been resolved. Could you try updating to a newer version of hakari? Thanks.

Could you give me a little bit more information here ? Which version resolves the problem?
I am using
cargo-hakari 0.9.28

which is the newest version, that is available to me via nix-flakes

This issue was resolved in version 0.9.29. Nix packages are community-maintained and might not always be the latest version. Please do try again with the latest version available on crates.io (currently 0.9.30), thanks!

Looks like it was updated in nixpkgs recently: https://github.com/NixOS/nixpkgs/pull/331820
It should be available in nixpkgs-unstable by now, so you might need to run nix flake update. I can confirm that that fixes the issue on my end.

This should be resolved so I'm going to go ahead and close this. Thanks!


Added a command to lint all the libs

@GabrielCTroia
This is the PR to add the command lint-all-libs to the package.json, but there are some errors on a couple of files. I assume that the issues are already created for the failed files. I'd like to move on the issue to solve the error. Please review the PR, this is pretty short and straight-forward!
Thanks

Thank you @seog-jun! This looks good! I’m going to merge it shortly!
And yes, thank you for letting me know about the failing. That issue got introduced by mistake and already is part of pending PR!
**Lastly, could you please give is a star, so we can bump Movex up the #hacktoberfest ladder a bit! 😁🙏 **


[WIP] Refactor code

A new file called logic.py has been created whose purpose is to include all application logic. This file will then be used by torpaste.py to make all decisions in the HTTP level using Flask.

@j11e I am proposing these changes, which may unfortunately break Pull Request #49 . If you like these changes, let me know, so we can find a solution. This is just a heads up. I think it will clean up the codebase a lot, and will help in fixing issue #19 which I will be working on after I finish with this.

BTW, we probably have to come up with a smarter system than the multiple returns in order to convey messages to torpaste.py. Exceptions sure can be one of them, however I did not implement them for simplicity. Will probably do this soon, definitely before merging.

I was away this week-end, I'll take a look tomorrow. No worries about the pull request anyway, I'll just rebase.

I'm ok with the changes. Fun fact: I was thinking of moving the configuration handling code in another file, considering how fast the number of supported variables is increasing. You moved out the other part of the code first :)

Thanks! So yes, I moved the other part as well and I am also considering moving the configuration code, but I have not done this yet. Give me some time to work on this PR a little bit more, and if everything is okay, I'll merge it and then work on Exceptions. You can work on moving the config file if you'd like.. :-)


CID Placeholder - Airtable

Purpose of this pull request
This pull request (PR) ...
Issue number:

Select the type of change:

[ ] Minor Changes - Typos, formatting, slight revisions
[ ] Update Content - Revisions and updating sections
[ ] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - Updates, maintenance, and new packages for the site, Gatsby, React, etc

This is just a placeholder PR.

I've removed the dependencies label. Dependencies are specifically the site package and security contents in package.json and yarn.lock.


New clusters should set the Cloud Platform scope for users

Leo recently added the ability to set the "Cloud Platform" scope on their clusters. This allows users to dispatch jobs to dSub, cloud ML, and other Google cloud products directly from their notebooks. We should ensure that all new clusters we create going forward include this scope.
Leo issue: https://github.com/DataBiosphere/leonardo/issues/542

I filed a related issue a while back - see #998.
Any update on when this would get into Terra?
We've been using it for more and more analyses and a nice case where calling dsub from a notebook came up.

Sorry for missing the connection on these two issues, Matt. I'm closing this as a duplicate and elevating yours

Per discussion in #998, I am reopening this. It is insufficient for dsub and also useful for other things. Brett is working on it now.
@mbookman @deflaux is there a quick (non-dsub) command that Brett could run to test that his change to add the scope is having the desired effect?

In a native GCP project with CloudML Engine enabled, command gcloud --project <YOUR-NATIVE-GCP-PROJECT-ID> ml-engine models list should return Listed 0 items. or something similar.


Add lib/Point.js which exposes a shape for drawing circles

Adds a Point shape which takes parameters: fillStyle, strokeStyle, radius

My fork here adds Point, Line, and Multiline if anyone else is looking for that functionality.

:+1:

@scottyantipa Why did you close this?


haystack in Zend\Validator\Inarray removed after remove other field

steps to reproduce:

define fields: foo and bar
bar field has Zend\Validator\Inarray, as we can't set haystack via GUI, then set manually at module.config.php
remove foo field via GUI

actual result: "haystack" option in bar validator definitions removed.
expected result: "haystack" option in bar validator definitions should not be removed.

@samsonasik I was looking on it, and it seems to be a bit more complex issue. It needs changes also in zf-apigility-admin. Basically we need add option haystack in validator_metadata config:
https://github.com/zfcampus/zf-apigility-admin/blob/master/config/module.config.php#L1400-L1403
but then also in admin-ui we need to add support for array option values (now it works only with bool/int/string)...

This repository has been closed and moved to laminas-api-tools/api-tools-admin-ui; a new issue has been opened at https://github.com/laminas-api-tools/api-tools-admin-ui/issues/5.


PDF.js keyboard shortcuts for editor

The tools in the toolbar are accessible via keyboard shortcuts. Now that the editor annotation functions are added, I would like to request that they are accessible via keyboard shortcuts as well.

They are few already
Ctrl + up arrow key - first page
Ctrl + down arrow key - last page
etc...

This is now tracked on Bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=1853424. Closing as duplicate.


Incorrect tag validation for AWS::Glue::Job resources in cfn-lint 1.4.0

CloudFormation Lint Version
1.4.0
What operating system are you using?
linux
Describe the bug
The cloudformation docs for AWS::Glue::Job are incorrect with respect to tagging. The docs tags as an array of Key/Value dicts, but cloudformation actually expects Tags to be a dictionary of key/values.
In 1.3.7, cfn-lint does not throw an error when you use the correct dictionary tags (maybe it ignores it?)
In 1.4.0 a template will error out with: E3012 {'tag1': 'value2', 'tag2': 'value1'} is not of type 'array'
Expected behavior
Should validate the reproduction template without errors on the reproduction template. This validates correctly in 1.3.7
Reproduction template
This representation of tags is deployable with cloudformation:
---
AWSTemplateFormatVersion: '2010-09-09'
Resources:
  GlueJob:
      Type: 'AWS::Glue::Job'
      Properties:
        GlueVersion: 4.0
        Role: redacted
        Tags:
          tag1: value2
          tag2: value1
        Connections:
           Connections:
            - redacted
        Description: redacted
        SecurityConfiguration: redacted
        Command:
          Name: redcated
          PythonVersion: 3
          ScriptLocation: redacted
        ExecutionProperty:
          MaxConcurrentRuns: 1
        MaxRetries: 0
        WorkerType: G.1X
        Timeout: 60
        NumberOfWorkers: 2
        Name: redacted

In v0 the spec for these are written as
"Tags": {
     "Documentation": "http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-glue-job.html#cfn-glue-job-tags",
     "PrimitiveType": "Json",
     "Required": false,
     "UpdateType": "Mutable"
    },

Patching them to be in the schemas
{
   "format": "json",
   "type": [
    "object",
    "string"
   ]
  }

Also communicating with the docs team if we can get there description fixed.

Hey all, we have successful Glue job deployments using the list of key/value dicts. It seems that both formats may work, and seeing as the docs still suggest the correct format is the list of key/value dicts, can cfn-lint allow both formats?


how to handle DC term

Either column of ones or added in function...

If you are using neuroGLM, you can use the addBiasColumn to add a column of ones to the design matrix. So if matRegress requires a bias column now and later don't need it, this wouldn't be too much change, I suppose? (There's always the danger of backwards compatibility in the API interface though...)


Delete inactivated reactions

Description of the issue:
During the development of Human-GEM, many reactions were inactivated (lower and upper bounds set to zero) based on a lack of evidence and/or violation of mass balances. These reactions were not completely removed from the model to allow time to properly evaluate their removal (as suggested in #44), as undoing the removal can become complicated.
Now that we have had sufficient time to evaluate these 315 inactivated reactions, and because the yaml workflow is in place allowing easier tracking of such changes, I propose that we fully delete these reactions.
I hereby confirm that I have:

[X] Checked that a similar issue does not exist already

It's really cool that the yaml based workflow supports the removal of reactions. I'm wondering, does the reverse process hold, ie adding new content to the yaml file is sufficient to import new information into the model? You maybe see where I'm getting at: a GitHub Action to automatically create pull requests with new content identified from various databases.

It seems rather convenient and smooth to add/remove reactions through yaml, if there is no addition/deletion of metabolites.

Yes, but keep in mind that we also need to update the corresponding annotation JSONs to keep them synced with the model, which at the moment is unfortunately a manual process.


Creating dictionaries via configuration isn't working

The example available here:
https://github.com/Altinity/clickhouse-operator/blob/master/docs/chi-examples/05-settings-02-dictionary.yaml
Or the description here:
https://github.com/Altinity/clickhouse-operator/blob/master/docs/custom_resource_explained.md#specconfigurationfiles
Doesn't seem to be working. I get no dictionaries. In the logs I also see no attempt to create the dictionaries. Could something have changed in the Clickhouse Server which broke this feature?
Or am I doing something wrong?
This is what I see:
chi-settings-02-standard-0-0-0.chi-settings-02-standard-0-0.clickhouse.svc.cluster.local :) show dictionaries;

SHOW DICTIONARIES

Query id: 0f3412ed-b11a-47e7-bc48-5de70db4e331

Ok.

0 rows in set. Elapsed: 0.004 sec.

I appreciate any support

rookie mistake, I was using the dictionary wrong. Apologies


Nested concept failures should be reported with full stacktrace

Expected behavior
When nested concepts are used, more info will make tracing the problem at specification level easier.
Actual behavior
Only the current step failing is shown irrespective of the nesting.
E.g.
Consider a spec file
Admin dashboard should reflect recently created customers
--------------------------------------------------------
tags: dashboard, register

* Delete customer<EMAIL_ADDRESS>
Consider concepts
# Delete customer <customer>
* Open the customer list
* Search for customer by name <customer>
* Delete the customer

# Search for customer by name <name>
* enter search criteria name <name>
* Filter customers

A failure in step enter search criteria name <name> will give the info as
# Track recent events
  ## Admin dashboard should reflect recently created customers

                Failed Step: enter search criteria name <name>
                Specification: specs/TrackRecentEvents.spec
                Error Message: java.lang.NullPointerException
                Stacktrace:
                components.list.Customers.enterCriteriaUserName(Customers.java:23)....

Proposed Behavior
# Track recent events
  ## Admin dashboard should reflect recently created customers
     Failed Step: Delete customer <email>
        Specification: specs/TrackRecentEvents.spec : Line:12
       Failed Step: Search for customer by name <customer>
           Concept: specs/concepts/RegisterCustomer.cpt : Line:12
         Failed Step: enter search criteria name <name>
             Specification: specs/concepts/SearchByCustomerName.cpt
                Error Message: java.lang.NullPointerException
                Stacktrace:
                components.list.Customers.enterCriteriaUserName(Customers.java:23)....

Closing this as an old issue. However, any PR's to fix this will be merged.


install fails on CentOS 7 with missing GLIBCXX_3.4.21

..../node_modules/reason-cli/r/_esyEjectRoot/bin/fastreplacestring.exe: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by ..../node_modules/reason-cli/r/_esyEjectRoot/bin/fastreplacestring.exe)

CentOS 7 provides
strings /usr/lib64/libstdc++.so.6.0.19  | grep GLIBC
GLIBCXX_3.4
GLIBCXX_3.4.1
GLIBCXX_3.4.2
GLIBCXX_3.4.3
GLIBCXX_3.4.4
GLIBCXX_3.4.5
GLIBCXX_3.4.6
GLIBCXX_3.4.7
GLIBCXX_3.4.8
GLIBCXX_3.4.9
GLIBCXX_3.4.10
GLIBCXX_3.4.11
GLIBCXX_3.4.12
GLIBCXX_3.4.13
GLIBCXX_3.4.14
GLIBCXX_3.4.15
GLIBCXX_3.4.16
GLIBCXX_3.4.17
GLIBCXX_3.4.18
GLIBCXX_3.4.19
GLIBC_2.3
GLIBC_2.2.5
GLIBC_2.14
GLIBC_2.4
GLIBC_2.3.2
GLIBCXX_DEBUG_MESSAGE_LENGTH

Does it mean there is no way to use reason-cli on this system?

well, just found a note on the main page... it seems I need to setup a different VM just for reasonml :(

Hi, @108adams!
It's pretty easy to produce either a dev/pack-type release (in that case all deps will be built on the machin which performs the installation) or another bin-type release with a compatible glibc version.
See https://github.com/reasonml/reason-cli#releasing and https://github.com/reasonml/reason-cli#using-pack-to-build-on-isolated-network-host-using-npm--g-on-the-destination for details.
Feel free to ask more questions about this.
cc @jordwalke probably we need to publish pack or dev releases too?

Thanks, I managed to build and install the package on CentOS 7 with custom node 8.8.1 npm 5.3.0.
If the glibc is not actually an issue, why do you constrict the version so tightly? Centos 7 is not an old distro, I know nothing about the other RedHat based ones, have you managed to install cli on Fedora or mandriva?
Anyway, thx for help, my reason  journey has started :)


Fix typo

Closes #
📑 Description

✅ Checks

[ ] My pull request adheres to the code style of this project
[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required
[ ] All the tests have passed

ℹ Additional Information

Can we merge this to master?

cc @DevHaoZi


docs: reference --no-progress option in related environment variable

Summary
Aligns the description of UV_NO_PROGRESS with other env vars that also have a related flag.
--no-progress is a "global option" and exists in every command.

Thanks for the fix! zanieb <3

Np! Thanks for contributing.
For future reference, we generate the reference documentation like that from the code so usually you want to change the code then run cargo dev generate-all


Remove unnecessarily complex Time semantic

There is only one reason for having time.Time in the storage API:
seemingly it makes the API intuitive and "unified". But.
There are many disadvantages:

It hurts to review PRs that operate with time.Time magic.
Zero value needs special treatment.
There are 3(!) different types for time: Golang's time.Time,
protobuf's Timestamp, and MySQL DATETIME. We depend on conversions
between these types to work correctly.
Storage implementations need to do arcane rounding arithmetics with
the timestamp. To me it feels like using float instead of int.
Using time.Time in the API prevents non-Time implementations, e.g.
simple sequence numbers like in Kafka. For the problem that these
timestamps are solving, it actually makes more sense to use
non-timestamp types.

Not a criticism, just thinking out-loud. The cons of this approach:

No standard meaning for watermark objects.

Which means that monitoring will need to be database specific in order to interpret them.
A continual temptation to imply meaning on these opaque objects

Previous objections that have been removed by the work to migrate to time.Time

Spurious leakage of time.Now and time.UnixNano into the code base, effectively granting meaning to these opaque objects even while claiming that they are opaque.

@pavelkalinnikov  Could you

[ ] Update the mysql implementation to be based on microseconds so that a) it matches spanner, and b) ensures that we have a diversity of time granularities in the testable code base?

[ ] I would also request a conversion API in the storage layer to convert the opaque object into a time.Time for monitoring purposes.

@pavelkalinnikov could you

[ ]  Update the mysql implementation to be microsecond based?

This would ensure diversity of time granularities exist in the tested code base
Ensure that external tests exist for a microsecond based implementation.

I made the MySQL implementation in nanoseconds.
Our internal implementation is in microseconds.
The in-memorhy implementation is in sequence numbers.
So we are covering all cases we care about.

[ ]  I would also request a conversion API in the storage layer to convert the opaque object into a time.Time for monitoring purposes.

I am doing this in a follow-up PR. We agreed to do it slightly differently: the LogMessage type will contain a time.Time field which will be used by monitoring.


olecranon bursitis

Bursitis is not a bone disease, the bursa is a fluid-filled sac or saclike cavity, especially one countering friction at a joint.
https://www.ebi.ac.uk/ols/ontologies/mondo/terms?iri=http%3A%2F%2Fpurl.obolibrary.org%2Fobo%2FMONDO_0001557

this is not classified as a bone disease, it is a child of bursitis, limb disorder, and enthesopathy.
I think this can be closed.

Please reopen if needed :)


Adding support for audio_play action

Fixes #383
Changes: Play video from youtube for audio_play action, same as the SUSI Android and Web client.
Screenshots for the change:

@batbrain7 I implemented the same way as SUSI Android. Please review


Add ci

Closes #155

Just a couple of updates to crate descriptions and this is good to go. Also needs a crates.io badge in the header.


Mutual TLS Origination with Egress Gateway Task fails

Bug description
Following the task for "Perform mututal TLS origination with an Egress Gateway" seems to result in an invalid configuration that doesn't achieve the desired outcome. I'm referencing this task: Perform Mutual TLS Origination with an Egress Gateway
The config documented in the task resulted in the cluster configs for the istio-ingressgateway and sleep pods to go into STALE status because Envoy believes the pods need TLS certificates, specified by a destination rule in the documentation, that they shouldn't require and don't have presented to them in their pod configs.
This seems to affect both 1.4.x and 1.3.x (using the archived task documentation, which is exactly the same outside of using Helm to deploy the egress gateway instead of istioctl).
[ ] Configuration Infrastructure
[ X ] Docs
[ ] Installation
[ X ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
I'd expect istioctl proxy-status to show synced configuration for all sidecars in the mesh after the configuration in the task documentation is applied.
Steps to reproduce the bug
Follow the procedure in the documentation for Perform Mutual TLS Origination with an Egress Gateway.
When you run the command in step 3 in the section titled "Configure mutual TLS origination for egress traffic", the command returns a no healthy upstream error.
Additionally, when you run istioctl proxy-status you'll see that the sleep and istio-ingressgateway pods are reporting stale cluster configurations. If you look at the Envoy logs for those pods, you find that the cluster config is failing to apply because of missing certs. Going a bit further, a istio proxy-status run on the affected pods shows the following config diffs between Pilot and Envoy:
+++ Envoy Clusters
@@ -3094,44 +3094,17 @@
             "circuitBreakers": {
                "thresholds": [
                   {
                      "maxRetries": 1024
                   }
                ]
             },
-            "tlsContext": {
-               "commonTlsContext": {
-                  "tlsCertificates": [
-                     {
-                        "certificateChain": {
-                           "filename": "/etc/nginx-client-certs/tls.crt"
-                        },
-                        "privateKey": {
-                           "filename": "/etc/nginx-client-certs/tls.key"
-                        }
-                     }
-                  ],
-                  "validationContext": {
-                     "trustedCa": {
-                        "filename": "/etc/nginx-ca-certs/ca-chain.cert.pem"
-                     }
-                  }
-               },
-               "sni": "nginx.example.com"
-            },
             "dnsRefreshRate": "300s",
             "respectDnsTtl": true,
-            "dnsLookupFamily": "V4_ONLY",
-            "metadata": {
-               "filterMetadata": {
-                  "istio": {
-                        "config": "/apis/networking/v1alpha3/namespaces/default/destination-rule/originate-mtls-for-nginx"
-                     }
-               }
-            }
+            "dnsLookupFamily": "V4_ONLY"
          }
       },
       {
          "cluster": {
             "name": "outbound|443||traffic-claim-enforcer-webhook.istio-system.svc.cluster.local",
             "type": "EDS",
             "edsClusterConfig": {

Listeners Match
Routes Match

NAME                                                  CDS        LDS        EDS        RDS          PILOT                            VERSION
istio-egressgateway-fd99fdc54-pvdnw.istio-system      SYNCED     SYNCED     SYNCED     SYNCED       istio-pilot-58f7cc886f-q7hj7     1.3.6
istio-ingressgateway-777d8db49-fsf9v.istio-system     STALE     SYNCED     SYNCED     NOT SENT     istio-pilot-58f7cc886f-q7hj7     1.3.6
sleep-78777bf478-j5qlv.default                        STALE     SYNCED     SYNCED     SYNCED       istio-pilot-58f7cc886f-q7hj7     1.3.6

Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
Istio:
citadel version: 1.3.6
egressgateway version: 1.3.6
galley version: 1.3.6
ingressgateway version: 1.3.6
pilot version: 1.3.6
policy version: 1.3.6
sidecar-injector version: 1.3.6
telemetry version: 1.3.6

Kubernetes:
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.7", GitCommit:"6c143d35bb11d74970e7bc0b6c45b6bfdffc0bd4", GitTreeState:"clean", BuildDate:"2019-12-11T12:34:17Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}

Helm:

How was Istio installed?
Installed using Helm 3
Environment where bug was observed (cloud vendor, OS, etc)
kops cluster running on AWS EC2 instances

It appears this has been an issue for quite a while, as #9500 looks very similar to what I'm seeing, and was logged in Oct. 2018.

I have the exactly same issue, mTLS example with mesh-external.nginx works perfectly, but trying to replicate the same thing when nginx is outside the cluster (Public IP) it fails.
Interesting part i found that it brakes only when adding the last DestinationRule
kind: DestinationRule
metadata:
  name: originate-mtls-for-nginx
spec:
  host: myhost.example.com
  trafficPolicy:
    loadBalancer:
      simple: ROUND_ROBIN
    portLevelSettings:
    - port:
        number: 443
      tls:
        mode: MUTUAL
        clientCertificate: /etc/nginx-client-certs/tls.crt
        privateKey: /etc/nginx-client-certs/tls.key
        caCertificates: /etc/nginx-ca-certs/ca-chain.cert.pem
        sni: myhost.example.com```

```NAME                                                   CDS                            LDS        EDS              RDS          PILOT                            VERSION
istio-egressgateway-5d5ffb4df-7cfsw.istio-system       SYNCED                         SYNCED     SYNCED (95%)     SYNCED       istio-pilot-575c975655-qtvnp     1.2.10
istio-ingressgateway-5fd9d4bc48-mfm2p.istio-system     STALE (Never Acknowledged)     SYNCED     SYNCED (95%)     NOT SENT     istio-pilot-575c975655-qtvnp     1.2.10-gke.0
sleep-9d9fcbf4-h7vfq.default                           STALE (Never Acknowledged)     SYNCED     SYNCED (49%)     SYNCED       istio-pilot-575c975655-qtvnp     1.2.10-gke.0```

Exact same messages are present in both Pilot discovery and sleep pod(istio-proxy container)

```[2020-02-06 17:53:37.056][12][warning][config] [external/envoy/source/common/config/grpc_mux_subscription_impl.cc:73] gRPC config for type.googleapis.com/envoy.api.v2.Cluster rejected: Error adding/updating cluster(s) outbound|443||myhost.example.com: Invalid path: /etc/nginx-client-certs/tls.crt```

When trying to run curl with same certs from egressgateway pod itself everything works fine.
Tried mounting certificates/CA/Key to sleep container (curl works when bypassing egress gateway)

As per my understanding this error comes that there is no certificate on Sidecar container itself. Any workaround how i could add them even manually? (I'm running on GKE 1.15)

I have the exactly same issue, mTLS example with mesh-external.nginx works perfectly, but trying to replicate the same thing when nginx is outside the cluster (Public IP) it fails.

Thanks for adding your feedback @AlbertasG, glad to know I'm not alone! I'm not sure about the public IP scenario as I haven't tested it (will do so when able), but it definitely results in an invalid cluster config (unable to be applied by Envoy) for the client service when implemented with an in-cluster (but mesh external) service as the destination, which is what's used in the docs.

Ignoring the error, does the communication work? If it does, then you can continue to ignore that error.

At least for for now it doesn't work. I'll try to replicate this again next
week and post the results.
On Mon, 10 Feb 2020, 23:00 Shriram Rajagopalan<EMAIL_ADDRESS>wrote:

Ignoring the error, does the communication work? If it does, then you can
continue to ignore that error.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/20856?email_source=notifications&email_token=AGRFSEEUOEBZLBHWP4IM5PTRCG55JA5CNFSM4KP6V5T2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELKH47A#issuecomment-584351356,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGRFSEENSKTP6V4HLHKF263RCG55JANCNFSM4KP6V5TQ
.

@rodalli
So previously when i tested the "outside of Cluster" nginx it was 3rd party service with mTLS.
I've tried to follow the steps with nginx mTLS on GCP separate compute instance and it worked fine.
I still see that CDS are STALE, but RDS are SYNCED for sleep pods.
istio-egressgateway-5d5ffb4df-9mt8p.istio-system       SYNCED                         SYNCED     SYNCED (95%)     SYNCED       istio-pilot-5889bbb5c5-ns28v     1.2.10
istio-ingressgateway-7d6f7d85df-jrtnz.istio-system     STALE (Never Acknowledged)     SYNCED     SYNCED (95%)     NOT SENT     istio-pilot-5889bbb5c5-ns28v     1.2.10-gke.0
sleep-74f6459479-jt6qg.default                         STALE (Never Acknowledged)     SYNCED     SYNCED (49%)     SYNCED       istio-pilot-5889bbb5c5-ns28v     1.2.10-gke.0
sleep2-88d94fb74-zzs9m.default                         STALE (Never Acknowledged)     SYNCED     SYNCED (49%)     SYNCED       istio-pilot-5889bbb5c5-ns28v     1.2.10-gke.0

I tried to adjust the same config to 3rd party service again, and it did not work.
First hidden issue:
sleep container from example was using OpenSSL 1.0.1 and there was a problem with protocol negotiation from curl part. Upgrading to other container resolved issue that i was able to curl while providing certificates/keys manually sleep => istio-proxy
Second hidden issue:
Egress gateway mTLS origination was still not working, what resolved the issue for me was changing specific file path of CACert to absolute directory path in  DestinationRule caCertificates
  name: originate-mtls-for-nginx
  ...
  trafficPolicy:
    loadBalancer:
      simple: ROUND_ROBIN
    portLevelSettings:
    - port:
        number: 443
      tls:
        **caCertificates: /etc/nginx-ca-certs/**
        clientCertificate: /etc/nginx-client-certs/tls.crt
        mode: MUTUAL
        privateKey: /etc/nginx-client-certs/tls.key
        sni: some.sni.example.com

I don't know if this will be applicable to your setup, but hope it helps.
Another thing to mention i used example for my exact version from documentation archive Try to see if example between latest 1.4 and your version differs.

Same issue! @AlbertasG . In my case I am calling an external service. I was also referring the same documentation.
below is my destination rule.
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
...
trafficPolicy:
portLevelSettings:
- port:
number: 443
loadBalancer:
simple: ROUND_ROBIN
tls:
caCertificates: /etc/com-ca-certs/
clientCertificate: /etc/com-client-certs/tls.crt
mode: MUTUAL
privateKey: /etc/com-client-certs/tls.key
sni: my domain here
even though the certificates are provided the result ended up as below (Please note: the certificates are mounted and available in the path)

ALPN, offering h2
ALPN, offering http/1.1
successfully set certificate verify locations:
CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: none
TLSv1.3 (OUT), TLS handshake, Client hello (1):
TLSv1.3 (IN), TLS handshake, Server hello (2):
TLSv1.2 (IN), TLS handshake, Certificate (11):
TLSv1.2 (OUT), TLS alert, unknown CA (560):
SSL certificate problem: unable to get local issuer certificate

Did anyone actually got this working??

Make sure you can curl external service from egress gateway pod when
providing CA/Cert/Key directly.
This will confirm that certificates are loaded correctly. Next you could be
dumping tcp traffic on egress gateway and istio-sidecar to check if traffic
goes through.
On Tue, 10 Mar 2020, 22:29 Razeel Mohammed<EMAIL_ADDRESS>wrote:

Same issue! @AlbertasG https://github.com/AlbertasG . In my case I am
calling an external service. I was also referring the same documentation.
below is my destination rule.
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
...
trafficPolicy:
portLevelSettings:

port:
number: 443
loadBalancer:
simple: ROUND_ROBIN
tls:
caCertificates: /etc/com-ca-certs/
clientCertificate: /etc/com-client-certs/tls.crt
mode: MUTUAL
privateKey: /etc/com-client-certs/tls.key
sni: my domain here

even though the certificates are provided the result ended up as below
(Please note: the certificates are mounted and available in the path)

ALPN, offering h2
ALPN, offering http/1.1
successfully set certificate verify locations:
CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: none
TLSv1.3 (OUT), TLS handshake, Client hello (1):
TLSv1.3 (IN), TLS handshake, Server hello (2):
TLSv1.2 (IN), TLS handshake, Certificate (11):
TLSv1.2 (OUT), TLS alert, unknown CA (560):
SSL certificate problem: unable to get local issuer certificate

Did anyone actually got this working??
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/20856?email_source=notifications&email_token=AGRFSEHMVKWAOD5ET4YK2I3RG2PLXA5CNFSM4KP6V5T2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEONA5DI#issuecomment-597298829,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGRFSEBUXPWDG7ITGWUSOULRG2PLXANCNFSM4KP6V5TQ
.

Make sure you can curl external service from egress gateway pod when providing CA/Cert/Key directly. This will confirm that certificates are loaded correctly. Next you could be dumping tcp traffic on egress gateway and istio-sidecar to check if traffic goes through.
…
On Tue, 10 Mar 2020, 22:29 Razeel Mohammed, @.***> wrote: Same issue! @AlbertasG https://github.com/AlbertasG . In my case I am calling an external service. I was also referring the same documentation. below is my destination rule. apiVersion: networking.istio.io/v1alpha3 kind: DestinationRule ... trafficPolicy: portLevelSettings: - port: number: 443 loadBalancer: simple: ROUND_ROBIN tls: caCertificates: /etc/com-ca-certs/ clientCertificate: /etc/com-client-certs/tls.crt mode: MUTUAL privateKey: /etc/com-client-certs/tls.key sni: my domain here even though the certificates are provided the result ended up as below (Please note: the certificates are mounted and available in the path) - ALPN, offering h2 - ALPN, offering http/1.1 - successfully set certificate verify locations: - CAfile: /etc/ssl/certs/ca-certificates.crt CApath: none - TLSv1.3 (OUT), TLS handshake, Client hello (1): - TLSv1.3 (IN), TLS handshake, Server hello (2): - TLSv1.2 (IN), TLS handshake, Certificate (11): - TLSv1.2 (OUT), TLS alert, unknown CA (560): - SSL certificate problem: unable to get local issuer certificate Did anyone actually got this working?? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#20856?email_source=notifications&email_token=AGRFSEHMVKWAOD5ET4YK2I3RG2PLXA5CNFSM4KP6V5T2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEONA5DI#issuecomment-597298829>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGRFSEBUXPWDG7ITGWUSOULRG2PLXANCNFSM4KP6V5TQ .

curl with params is working fine. Even the logs(both sleep-sidecar and egress) are showing outbound request. I tried with and without egress. And if I remove mtls everything is working.

Does curl work for you when connecting to http:80 endpoint?
Can you share your full configuration? ServiceEntry, VirtualService, DestinationRule, Gateway?
I've seen similar issue on my side when traffic exited cluster on side-car rather than Egress Gateway due to broken config.

Does curl work for you when connecting to http:80 endpoint?
Can you share your full configuration? ServiceEntry, VirtualService, DestinationRule, Gateway?
I've seen similar issue on my side when traffic exited cluster on side-car rather than Egress Gateway due to broken config.

Hi @AlbertasG the issue is fixed now and is working end to end. However I noticed something strange that when I am mounting secrets in the egress gateway, then my application sidecar was failing.
kubectl create -n istio-system secret tls nginx-client-certs --key nginx.example.com/4_client/private/nginx.example.com.key.pem --cert nginx.example.com/4_client/certs/nginx.example.com.cert.pem kubectl create -n istio-system secret generic nginx-ca-certs --from-file=nginx.example.com/2_intermediate/certs/ca-chain.cert.pem
The error was the side car cannot find the path(nginx.example.com/4_client/private/) even though I applied it to egress gateway. As a work around I injected the volume mount in the side car through the annotation as in the deployment file given below.
...   template:     metadata:       annotations:         sidecar.istio.io/userVolumeMount: '[{"name":"nginx-client-certs", "mountPath":"nginx.example.com/2_intermediate/certs/", "readonly":true}, {"name":"nginx-ca-certs", "mountPath":"nginx.example.com/4_client/private/", "readonly":true}]'         sidecar.istio.io/userVolume: '[{"name":"nginx-client-certs", "secret":{"secretName":"nginx-client-certs", "optional": true}}, {"name":"nginx-ca-certs", "secret":{"secretName":"nginx-ca-certs", "optional": true}}]'       labels:         app: sleep ...
Optional parameter is specified so it is not necessary to provide the certificate in the default namespace(where the application is deployed) as well. But still I am figuring out when I mount the secrets on egress gateway and apply the destination rule then my application sidecar(istio-proxy) was also demanding the same mount!!
Also the subsets given the destination rule is not getting applied properly (Might be my yaml formatting issue will update after confirmation).

I've got the same errors, but as mentioned above if connection works you
can ignore the error log.
On Fri, 13 Mar 2020, 16:13 Razeel Mohammed<EMAIL_ADDRESS>wrote:

Does curl work for you when connecting to http:80 endpoint?
Can you share your full configuration? ServiceEntry, VirtualService,
DestinationRule, Gateway?
I've seen similar issue on my side when traffic exited cluster on side-car
rather than Egress Gateway due to broken config.
Hi @AlbertasG https://github.com/AlbertasG the issue is fixed now and
is working end to end. However I noticed something strange that when I am
mounting secrets in the egress gateway, then my application sidecar was
failing.
kubectl create -n istio-system secret tls nginx-client-certs --key
nginx.example.com/4_client/private/nginx.example.com.key.pem --cert
nginx.example.com/4_client/certs/nginx.example.com.cert.pem kubectl
create -n istio-system secret generic nginx-ca-certs --from-file=
nginx.example.com/2_intermediate/certs/ca-chain.cert.pem
The error was the side car cannot find the path(
nginx.example.com/4_client/private/) even though I applied it to egress
gateway. As a work around I injected the volume mount in the side car
through the annotation as in the deployment file given below.
... template: metadata: annotations: sidecar.istio.io/userVolumeMount:
'[{"name":"nginx-client-certs", "mountPath":"
nginx.example.com/2_intermediate/certs/", "readonly":true},
{"name":"nginx-ca-certs", "mountPath":"nginx.example.com/4_client/private/",
"readonly":true}]' sidecar.istio.io/userVolume:
'[{"name":"nginx-client-certs",
"secret":{"secretName":"nginx-client-certs", "optional": true}},
{"name":"nginx-ca-certs", "secret":{"secretName":"nginx-ca-certs",
"optional": true}}]' labels: app: sleep ...
Optional parameter is specified so it is not necessary to provide the
certificate in the default namespace(where the application is deployed) as
well. But still I am figuring out when I mount the secrets on egress
gateway and apply the destination rule then my application
sidecar(istio-proxy) was also demanding the same mount!!
Also the subsets given the destination rule is not getting applied
properly (Might be my yaml formatting issue will update after confirmation).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/20856#issuecomment-598739858, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AGRFSEGHRUBJXTBJECUS23TRHI5RFANCNFSM4KP6V5TQ
.

I've got the same errors, but as mentioned above if connection works you can ignore the error log.
…
On Fri, 13 Mar 2020, 16:13 Razeel Mohammed, @.***> wrote: Does curl work for you when connecting to http:80 endpoint? Can you share your full configuration? ServiceEntry, VirtualService, DestinationRule, Gateway? I've seen similar issue on my side when traffic exited cluster on side-car rather than Egress Gateway due to broken config. Hi @AlbertasG https://github.com/AlbertasG the issue is fixed now and is working end to end. However I noticed something strange that when I am mounting secrets in the egress gateway, then my application sidecar was failing. kubectl create -n istio-system secret tls nginx-client-certs --key nginx.example.com/4_client/private/nginx.example.com.key.pem --cert nginx.example.com/4_client/certs/nginx.example.com.cert.pem kubectl create -n istio-system secret generic nginx-ca-certs --from-file= nginx.example.com/2_intermediate/certs/ca-chain.cert.pem The error was the side car cannot find the path( nginx.example.com/4_client/private/) even though I applied it to egress gateway. As a work around I injected the volume mount in the side car through the annotation as in the deployment file given below. ... template: metadata: annotations: sidecar.istio.io/userVolumeMount: '[{"name":"nginx-client-certs", "mountPath":" nginx.example.com/2_intermediate/certs/", "readonly":true}, {"name":"nginx-ca-certs", "mountPath":"nginx.example.com/4_client/private/", "readonly":true}]' sidecar.istio.io/userVolume: '[{"name":"nginx-client-certs", "secret":{"secretName":"nginx-client-certs", "optional": true}}, {"name":"nginx-ca-certs", "secret":{"secretName":"nginx-ca-certs", "optional": true}}]' labels: app: sleep ... Optional parameter is specified so it is not necessary to provide the certificate in the default namespace(where the application is deployed) as well. But still I am figuring out when I mount the secrets on egress gateway and apply the destination rule then my application sidecar(istio-proxy) was also demanding the same mount!! Also the subsets given the destination rule is not getting applied properly (Might be my yaml formatting issue will update after confirmation). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#20856 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGRFSEGHRUBJXTBJECUS23TRHI5RFANCNFSM4KP6V5TQ .

I used istio version 1.5 and the connection was not working. But my colleague who was using 1.4.5 got connection with out making the above change. In his case the error message was in the log but the sidecar was up and running.

You should check on 1.5X current issues about crashing of side-car pods. If
there isn't any yet consider creating a new one.
On Fri, 13 Mar 2020, 16:47 Razeel Mohammed<EMAIL_ADDRESS>wrote:

I've got the same errors, but as mentioned above if connection works you
can ignore the error log.
… <#m_5541115903302081791_>
On Fri, 13 Mar 2020, 16:13 Razeel Mohammed, @.***> wrote: Does curl
work for you when connecting to http:80 endpoint? Can you share your full
configuration? ServiceEntry, VirtualService, DestinationRule, Gateway? I've
seen similar issue on my side when traffic exited cluster on side-car
rather than Egress Gateway due to broken config. Hi @AlbertasG
https://github.com/AlbertasG https://github.com/AlbertasG the issue is
fixed now and is working end to end. However I noticed something strange
that when I am mounting secrets in the egress gateway, then my application
sidecar was failing. kubectl create -n istio-system secret tls
nginx-client-certs --key
nginx.example.com/4_client/private/nginx.example.com.key.pem --cert
nginx.example.com/4_client/certs/nginx.example.com.cert.pem kubectl
create -n istio-system secret generic nginx-ca-certs --from-file=
nginx.example.com/2_intermediate/certs/ca-chain.cert.pem The error was
the side car cannot find the path( nginx.example.com/4_client/private/)
even though I applied it to egress gateway. As a work around I injected the
volume mount in the side car through the annotation as in the deployment
file given below. ... template: metadata: annotations:
sidecar.istio.io/userVolumeMount: '[{"name":"nginx-client-certs",
"mountPath":" nginx.example.com/2_intermediate/certs/", "readonly":true},
{"name":"nginx-ca-certs", "mountPath":"nginx.example.com/4_client/private/",
"readonly":true}]' sidecar.istio.io/userVolume:
'[{"name":"nginx-client-certs",
"secret":{"secretName":"nginx-client-certs", "optional": true}},
{"name":"nginx-ca-certs", "secret":{"secretName":"nginx-ca-certs",
"optional": true}}]' labels: app: sleep ... Optional parameter is specified
so it is not necessary to provide the certificate in the default
namespace(where the application is deployed) as well. But still I am
figuring out when I mount the secrets on egress gateway and apply the
destination rule then my application sidecar(istio-proxy) was also
demanding the same mount!! Also the subsets given the destination rule is
not getting applied properly (Might be my yaml formatting issue will update
after confirmation). — You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#20856 (comment)
https://github.com/istio/istio/issues/20856#issuecomment-598739858>, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AGRFSEGHRUBJXTBJECUS23TRHI5RFANCNFSM4KP6V5TQ
.
I used istio version 1.5 and the connection was not working. But my
colleague who was using 1.4.5 got connection with out making the above
change. In his case the error message was in the log but the sidecar was up
and running.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/20856#issuecomment-598755989, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AGRFSEBKUANMFXL7K6MUFWLRHJBPVANCNFSM4KP6V5TQ
.

Hi guys,
I'm following the same document and also seeing the same behaviour - when the destination rule is applied with:
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  name: originate-tls-for-external
spec:
  host: external.mtls.com
  trafficPolicy:
    loadBalancer:
      simple: ROUND_ROBIN
    portLevelSettings:
    - port:
        number: 443
      tls:
        mode: MUTUAL
        clientCertificate: /etc/istio/external-client-certs/tls.crt
        privateKey: /etc/istio/external-client-certs/tls.key
        caCertificates: /etc/istio/external-ca-certs/
        sni: external.mtls.com

I get sidecars failing with Invalid path: /etc/istio/external-ca-certs/.
As per doco, the patch for these client certs were applied to the egressgateway which is all OK.
Are you guys saying that ALL pods need this annotation in order to get this to work?
I found this guys solution here: https://stackoverflow.com/questions/57343583/how-can-i-use-custom-client-certificate-for-external-service-with-istio/57347134#57347134
and he did something similar in adding the annotation to the pod that needed it.
I also find if this destinationRule is applied (while broken), all my sidecars fail, so I'm guessing the annotation has to be for ALL pods?

Hi guys,
There's another issue open on Istio documentation: https://github.com/istio/istio.io/issues/7063.

Ran into the same issue today and spent a significant amount of time debugging. I have a work around for now which is to scope the DestinationRule as only exported to the namespace of the egress gateway and also deploy the egress gateway to its own namespace.
Not sure if this is related to: #12234 but i have read through a long list of historical issues it seems that Istio treats the istio-system namespace differently when applying DestinationRules and seems to ignore them if they are marked as not exported.

This issue is very old and mutual TLS origination task has been fixed ever since. It is now covered in automated doc tests too-  The fix was cherrypicker to 1.6, so I am closing this issue


Imported THORChain Styles, Fonts

Styles have been already included by using @thorchain/asgardex-theme. Fonts will be imported as part of #60 .
Closing now...


Slack for Apple Silicon, too

Even Slack universal was added on v0.4.5, I'm on v10.2 and my Silicon mac keeps downloading Intel version.
v10.3 changes does not include anything for Slack.


docs: Add Port Range Information

~- SCTP and Port Ranges are now supported, both are removed from the unsupported features table.~

DNS rules and L7 rules do not support port ranges yet. Notes are added to call attention to this.
Add a Port Range example.

Edit:

SCTP support will be addressed in a different PR.

/test


go-callvis for quorum packages

git clone https://github.com/jpmorganchase/quorum.git
Iam trying this command
go-callvis -focus upgrade -group pkg,type -limit github.com/jpmorganchase/quorum github.com/jpmorganchase/quorum
output-
go-callvis: cannot find package "upgrade" in any of:
/usr/local/go/src/upgrade (from $GOROOT)
/home/ubuntu/go/src/upgrade (from $GOPATH)

incidentally I also stumbled on the same issue!! Any thoughts on how to resolve this?

Target needs to be a program. github.com/jpmorganchase/quorum doesn't seem to be a program. Try one of the programs in cmd folder.

@TrueFurby any plan to support libraries ?

Main package (program) is required for the analysis used, because all the calls in the callgraph tree begins in main (and inits).
In package you don't really know what will be called, since it's just a package without some start point. Program that will use the package can call anything or nothing.

Instead of a single entry point (main()) you could have multiple entry points (every exported function).
But I understand it might not be easy or even possible depending on the code you have. Just stating that it would be very helpful to understand a codebase.

You easily do that by creating a simple program and placing all the calls you are interested in, for example exported functions of some package, and running go-callvis on that program.


508 Fixes some financial aid feedback

[x] Python Experience Level: Should be a dropdown.
[x] Sorting only sorts the names on the current page in review financial aid appellations page, not all.
[x] Sorting doesn't sort correctly (we tried sorting date by see screenshot. Date field is being sorted lexicographically) (even when sorting just the names on the current page.)
[x] "Grant letter sent" should have a drop-down Yes/No menu
[x] "Cash check" should be called payment type
[x] Travel Cash Check should go away.

Looks mostly good, but a few issues:

"Cash check" still shows up, though now it has help text below it that reads "Payment type". Perhaps the field name needs to be changed in the models file
"Grant letter sent" is a checkbox, not a drop-down menu.

The rest looks good

@dchukhin I've updated this.

:dart:


⚠ Bofrost.de has degraded performance

In 137f1b3, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1152 ms

Resolved: Bofrost.de performance has improved in ab945cb after 6 minutes.


add ability to configure Autofac nested container

ability to configure nested container inside Autofac scope

Rebased/merged.


Fetch Olivia's pubkey

At the moment we hardcode the pubkey, we should fetch it instead.

Hardcoded is fine for now, otherwise we have to prevent MITM attacks.
Can make configurable at some point if needed.


Add --wait functionality to acorn run

When we run acorn apps, we find ourselves doing:
watch acorn ps

to wait until the app becomes healthy. Want to add  --wait flag so that the run command blocks until the cotainers are all reporting healthing and (maybe?) the endpoint is out of pending.

acorn run --wait already exists and is enabled by default.
However, it may not wait for absolutely everything to be 100% functional.
Here's an example:
acorn run --wait .local
[+] Building 2.4s (5/5) FINISHED
 # ...
 => => pushing manifest for <IP_ADDRESS>:5000/acorn/acorn:latest@sha256:ce248997aac1268a0a70a7f275d3f64f39b2116311aa32452323362078fe824c                                                                          0.0s
autumn-meadow
STATUS: ENDPOINTS[] HEALTHY[] UPTODATE[]
STATUS: ENDPOINTS[] HEALTHY[0] UPTODATE[0] pending
STATUS: ENDPOINTS[] HEALTHY[0/1] UPTODATE[1] [containers: autumn-meadow is not ready; my-webapp ContainerCreating]
STATUS: ENDPOINTS[http://my-webapp.autumn-meadow.local.on-acorn.io => my-webapp:80] HEALTHY[0/1] UPTODATE[1] [containers: autumn-meadow is not ready; my-webapp ContainerCreating]

So the output doesn't end with a success and if watching the pod status at the side, one can see that the pod is still in ContainerCreating state as the acorn command returns. That may even be correct as the Acorn in this example doesn't specify any probes.
Is the current behavior good enough or should we define more strict rules on when an Acorn App is considered ready?

@ibuildthecloud what's up here? What status are you waiting on with the --wait behavior?

@cjellick @iwilltry42 It just waits for app.Status.Ready to be true.  If that is true and the app is not in fact ready then the controller that updates the status should be modified.  One issue with the Ready check is that it won't consider "Uptodate"  so it is possible if you are updating an app it will be considered ready when it has updated.  We should probably add another field status.UpToDate to indicates that the spec and status match.
I believe there is probably another issue in that when spec.Stop = true we should be setting ready to false.


modify README and hbase-sql since the name of JAR has changed

Since the name of JAR has been changed in POM.XML, we have to Synchronize changes to other files.

Can one of the admins verify this patch?

test this please

yes ,i test this.it is ok.
hbase-sql need to use the new jar package(astro-project-0.10.0.jar),not spark-sql-on-hbase-1.0.0.jar.

The version number got changed to 0.1.0, so please update as per that.

ok to test

@ravipesala  Update has been completed.

retest this please

@ravipesala  Test what? Nothing changed but README...

@Zhangshunyu  I am asking Jenkins to test, not you. And also @WangTaoTheTonic review comment is valid.Please consider it.

The Astro v0.1.0 you released 3 days ago had sth wrong with it‘s boot script "bin/hbase-sql", you'd better merge this PR first to avoid the mistake.

@Zhangshunyu  if you are facing any problem in fixing the review comment, please let me know. I can help you. But this is not the proper way of communicating in community. Any way I am merging this PR.

@Zhangshunyu  I agree ravipesala's comments, it would be better if you could please pay attention to the communication words.

@ravipesala @chenliang613 I feel sorry for my tone of voice, and I will pay attention in the future.
I am very sincere to say sorry to you,thanks for your understanding.


Start several servers from config file

Allow to exec forever giving as parameter a config file (for example in JSON format, ideally the same one as ndm or based on it) so several services can be launch at the same time. The purpose of this is to use forever as daemon manager for NodeOS on boot time.
As a bonus, the config file would have an enabled field to allow to omit the start of a service if it's not set.

Fixed in `0.15.0


ready Promise should resolve only changed parts of state

Currently ready Promise resolves with a full app state.

This issue requires much more refactoring than I thought. Moving to 3.0


ARM support

  File "/home/kot/.local/share/virtualenvs/chatGPT-discord-bot-BNM29DVl/lib/python3.11/site-packages/revChatGPT/revChatGPT.py", line 4, in <module>
    import tls_client
  File "/home/kot/.local/share/virtualenvs/chatGPT-discord-bot-BNM29DVl/lib/python3.11/site-packages/tls_client/__init__.py", line 15, in <module>
    from .sessions import Session
  File "/home/kot/.local/share/virtualenvs/chatGPT-discord-bot-BNM29DVl/lib/python3.11/site-packages/tls_client/sessions.py", line 1, in <module>
    from .cffi import request
  File "/home/kot/.local/share/virtualenvs/chatGPT-discord-bot-BNM29DVl/lib/python3.11/site-packages/tls_client/cffi.py", line 15, in <module>
    library = ctypes.cdll.LoadLibrary(f'{root_dir}/dependencies/tls-client{file_ext}')
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/kot/.asdf/installs/python/3.11.0/lib/python3.11/ctypes/__init__.py", line 454, in LoadLibrary
    return self._dlltype(name)
           ^^^^^^^^^^^^^^^^^^^
  File "/home/kot/.asdf/installs/python/3.11.0/lib/python3.11/ctypes/__init__.py", line 376, in __init__
    self._handle = _dlopen(self._name, mode)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^
OSError: /home/kot/.local/share/virtualenvs/chatGPT-discord-bot-BNM29DVl/lib/python3.11/site-packages/tls_client/dependencies/tls-client-amd64.so: cannot open shared object file: No such file or directory

arch is aarch64, amd64 will not work here.

Same here

I've opened a PR that hopefully resolves this. Would be great if people can confirm this works for them to make it easier to merge.

for my use-case a fix was to use this image: FROM --platform=amd64 python:3.9-slim instead of default one, but in case you want to start it only in a particular architecture, it would be great to have bigger support

@Kidsan Raspberry has officially moved to arm64

@arnav7633 interesting, I knew it was possiblebut hadn't known that it was a fully adopted architecture.  Do you know if it returns aarch64 if we call platform.machine() or armv8b or what? Perhaps we need to account for multiple variations.

Its aarch64.  More info here

I've pushed an update, please lmk if this resolves your issues


[BUG] - When the Button color is set to danger, the color is not displaying correctly.

NextUI Version
2.4.8
Describe the bug
component: "Button"
variant: "ghost"
color: "danger"
the color is not displaying correctly.
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
Left button is "danger"

Left button hover

Right button hover

Expected behavior
The behavior of "danger" and "primary" should be consistent.
Screenshots or Videos
No response
Operating System Version
MacOS
Browser
Chrome

Fixed in https://github.com/nextui-org/nextui/pull/3764. you may use canary version at this moment or add data-[hover=true]:!text-danger-foreground.


Possible issues with multiple requests from the same domain

Are you aware of any issues with multiple requests from the same domain?
I have two notify endpoints:

https://colinwalker.blog/notify/
https://colinwalker.blog/php-mst/notify/

handling notifications for different apps.
Both apps are able to subscribe via /pleaseNotify and the request shows in the logs on rpc.rsscloud.io but notifications do not seem to be getting sent when the server is pinged.
The same code as https://colinwalker.blog/php-mst/notify/ is installed at https://colinwalker.me.uk/php-mst/notify/ and works fine so that leads me to think the issue is with the two endpoints being on the same domain.
Any thoughts?
Thanks.

It’s not a case I tested for so it’s possible. I’ll take a look and see what’s happening.

Thanks Andrew.
It seems a bit inconsistent. Typically, just after I raised that I got a notification to the second endpoint  but it doesn't always seem to be the case and wasn't working during testing earlier. 😆

I just looked into it, and we're tracking subscribers by the full URL of the subscriber endpoint. I wrote a test to verify that it works, and it does. What is the URL you're trying to ping for? The server does verify that the URL (feed) has changed since the last time it checked. You also need to make sure that each subscription is renewed daily. See http://walkthrough.rsscloud.co/#ta
I looked in the database and saw both of your specified endpoints subscribed to feeds. I do not see any errors. For the feed "https://colinwalker.blog/dailyfeed.xml" I see that you currently have "https://colinwalker.blog:443/notify/" and "http://feedland.org:80/feedupdated" getting updates. The endpoint "https://colinwalker.blog:443/notify/notify.php" expired 2022-11-28T04:35:24Z and is no longer getting updates.
So as far as I can tell, things are working. It's on my to-do list to overhaul the log page, as it really sucks. I'm looking in the event log database, and I see both of your specified endpoints getting notified recently.
If you have a specific feed that you're not getting notifications for, let me know the feed/subscriber combo, and I'll see what's in the database.

Thanks for all that.
The main problem I was having this morning was not getting notifications from https://colinwalker.me.uk/php-mst/feed.xml to https://colinwalker.blog/php-mst/notify/notify.php
The notification was appearing in the logs but there was no subsequent notification.
I have just re-done the subscription and received a notification correctly so not entirely sure what was going on.
Thanks for looking.


bug: 'table-pin-rows' is not present

What version of daisyUI are you using?
3.0.25
Describe your issue
I pasted the example from the documentation exactly on a Fresh Install of DaisyUI (v3.0.25) and TailwindCSS (v3.3.2).
There doesn't seem to be a class with the name table-pin-rows in DaisyUI. Using it doesn't apply any styling to my table.
It's present in the documentation for the version I'm using, is this implemented yet?
Thanks, awesome work!
What browsers are you seeing the problem on?
No response
Reproduction URL (optional)
No response

By default, table has no width or height limit and if the table content will fit the available space. (This is the default HTML bahaviour, not a daisyUI design decision)
But if you set a width or height, you can see the sticky rows or column.
See this example: https://play.tailwindcss.com/5bvndLAknD


Improve Github documentation page for "Getting Started: Deploy to AWS"

When I followed the documentation about how to deploy data.all to AWS I came along the requirement to bootstrap also the us-east-1 region besides the actual deployment region. As stated this is required for the integration of Cloudfront with ACM.
What I would suggest though is to more clearly state that this feature is only required for the internet facing setup of data.all and thus the us-east-1 region does not need to be bootstrapped when using the vpc facing setup.

I realized that there a more features which require cross region setup.


Cant get dynamic limit to work

Question
Ok, so I'm trying to dynamically adjust 2 charging robots, so that the hourly consumption stays below a certain kWh during the last hour. I have figured out the trigger/condition part I think, but struggle with actually limit the chargers current draw. To do a quick test I wanted to see if I could limit the charging current of my two chargers to 6A (Which I understand is the minimum required to start the charger).
This is the code I use:
action:
  - service: easee.set_circuit_dynamic_limit
    data:
      charger_id: EHXXXXXX
      currentP1: 6
      currentP2: 6
      currentP3: 6
  - service: easee.set_circuit_dynamic_limit
    data:
      charger_id: EHXXXXXX
      currentP1: 6
      currentP2: 6
      currentP3: 6

This does not change the amount of amperes the chargers draw, and they draw whatever the cars are set to as max (24A and 12A). In the Easee app I see no change in the "Dynamic limit for Chargingrobot" which I presume should be showing 6A.
If I try the following:
action:
  - service: easee.set_charger_circuit_dynamic_limit
    data:
      charger_id: EHXXXXXX
      currentP1: 6
      currentP2: 6
      currentP3: 6
  - service: easee.set_charger_circuit_dynamic_limit
    data:
      charger_id: EHXXXXXX
      currentP1: 6
      currentP2: 6
      currentP3: 6

I do see that the "Dynamic limit for Chargingrobot" changes in the Easee app, but only if the charger is not currently charging. If it starts to charge it seems to overwrite this value, and goes to the car limit again. Also, If I run the automation while the car is charging, the charging stops, and just says "In que - Load balancing", never to start charging again.
Any Ideas as to what I'm doing wrong here?
What version of the integration are you using?
0.9.45
Anything in the logs that might be useful for us?
No response
Additional information
No response

First, easee.set_circuit_dynamic_limit and easee.set_charger_circuit_dynamic_limit are the exact same thing in the sense that they end up calling the same API in the end.
The only difference is that with  easee.set_circuit_dynamic_limit you are supposed to provide the circuit id instead of the charger id. So this is most likely why your call to easee.set_circuit_dynamic_limit does not work, your input is simply wrong. Remove charger_id and add circuit_id instead if you want to use that version of the service.
(Circuit ID can be found by looking at the attributes for the xxxx_status sensor).
Second, and here I am guessing a bit since I do not know how your system is set up, but if I assume that you have 2 chargers, both connected to the same circuit and one is set up as master and one as slave.
And, disclaimer, I do not have such a system myself so I have no actual experience about how it works.
If your system is set up differently you can stop reading here and instead tell me how it is set up so we can have a better discussion :)
In any case, What I think happens is:
The circuit limit is for the circuit (aka fuse group), so it is shared between the 2 chargers.
(Which means you do not have to set it separately for each charger, it applies to all chargers on the same circuit. The actual API call uses the circuit ID, we just translate internally from charger ID to circuit ID for user convenience).
Setting it to 6A, means you allow totally 6A for both chargers combined. I.e. that would only be enough for 1 charger to be active at 6A and the other one would need to pause since there is in fact 0A left to use. 12A would in theory allow both chargers to charge at 6A, but we have no control or knowledge about how the priority between the 2 chargers will play out, it could be that it still pauses one and allows charging on the other at 12A until that car does not need to charge anymore.
Also worth noting that there apparently are a few cars out there that require more than 6A to start charging, Renault Zoe requires 7A I believe, so it is not universally true that charing starts at 6A, but it is always true that it stops when set to 5A or lower.
Regarding that problem with limits changing when you plug in/start charging, it kind of sound like you have used the easee.set_charger_dynamic_limit service instead of easee.set_charger_circuit_dynamic_limit like you are stating above?
easee.set_charger_dynamic_limit operates on charger level instead of circuit level, and it will in fact reset when you plug in a car. The circuit limit is supposed to stay valid unless you reboot the charger basically.
So please check what it is that you have used when testing.
This is a good place to read a bit about all the different limits and which ones you are supposed to use for what: https://developer.easee.cloud/docs/current-limits-and-control

Forgot to say, since you say that the limit that changes is the app is "Dynamic limit for Chargingrobot", that too points to that you have accidentally actually used the easee.set_charger_dynamic_limit service, since that would change that limit.
The limit changed by easee.set_circuit_dynamic_limit or easee.set_charger_circuit_dynamic_limit is the circuit limit. Not sure what the english translation is, but something like "Dynamic limit for circuit" and it would be shown as 6/6/6 in the app.

Thanks!
Completely missed that it should be circuit_id, and not charger_id when using easee.set_circuit_dynamic_limit. Changed to circuit_id now, and now the app shows "Dynamic limit for circuit" set to 6A for both chargers. They are as you said connected to the same circuit with one master and one slave unit. Will report back when I find out how the inbuilt load balancing works with a circuit limit set below 12A, i.e. if set to for example 11A, if it uses 11A on the first car, and waits for it to be finished before charging the next car, since it cant charge both at 6A, or if it somehow accepts below 6A for one charger when the other one is in use. (So one charges at 6A and the other at 5A). I'm guessing the first logic is used, but will report back.
And for anybody else that has never set this up before, when displaying the circuit_ID in the "CHARGERNAME_sensor status" attributes, it shows with a decimal character (example 123,456). You have to remove the decimal when using it in the circuit_ID YAML script, so it will be 123456. :)

Did a shot test, and it seems that nomatter what the dynamic limit is set to, it first charges one car, and then the other. But come to think about it, I think that was the default behavior before as well for my port, as one car charges using 3-phase, while the other charges using single phase. Doesn't matter much to me, as the total time to get both cars charge will be about the same anyways.
but, I thought I had a cunning plan to optimize the charging current, but alas, I have failed :)
So, this is what I'm trying to achieve:

I have a live feed of the total kW drawn at the main braker (Tibber). Also, the Tibber API provides a "Estimated Consumption current hour" sensor. That sensor tries to estimate, based on the current usage, and I guess som moving averaging what the total consumption will be at the end of the hour. SO for example it says 5.3kWh, which tells Home Assistant that it guesses that at the end of the hour (for example at 21:00) the total consumption in the period from 20:00 to 21:00 will be 5,3kWh. This is important, as the tarrifs here are calculated partly by the amount of energy used per hour, an if you exceed for instance 10kWh during a singel hour, you will be charged for the next tier compared to if you used 9,9 kWh in the same hour.

Naturally I want to charge the cars as fast as possible, but still stay within the max 10kWh per hour limit I'm aiming for. To do this I want to dynamicaly change the current of the car chargers based on what the rest of the house is using. So if my hous is using 8kWh during a single hour, I have 2 kWh "to spare" that I want to use for charging the car.

I wrote down the following formulas:

10 kWh consumption limit * 230 /1000 = should give the amount of Amperage I could draw continuously during the hour to reach a consumption og 10kWh. This equates to approx 43A.
I would then figure out how many Amps I have "to spare" based on the estimated consumption per hour from Tibber. So I wrote the following: "Estimated consumption current  hour(kWh) / 230 *1000. This should give the average amperage pulled during the hour to reach the estimated consumption usage. So if Tibber estimates 6kWh usage, that should equate to 26A
Subtract 26 from 43, and that should give me 17A "to spare". This is the dynamic current limit I set in the charger circuit.

Based on this I wrote the following code:
elbil_lader_begresning:
        friendly_name: "Ladebegrensning Elbil"
        value_template: "{{ (43 - (states('sensor.estimated_consumption_current_hour_jensvollia_19') | float/230*1000)) | int }}"
        unit_of_measurement: "A"
        device_class: current

This code works, and in the example above I can see that the dynamic circuit limit is set correctly at the charger, and updates while the car charges. I would then expect to se that the "Estimated consumption current hour" would climb and approach, but never reach 10kWh. (Red line)
However what I see is the "Estimated consumption current hour" climb but level of at about 7kWh. (Blue line, ignore the downward spike at approx 1610.)

I am assuming my logic isfaulty, but cant pinpoint what is wrong...

I think what you are calculating is not the actual limit to set, but the error, i.e. how much you need to change your setting.
So if you already have set 10A charging limit and you get 17A out from your formula you should set 10+17=27A limit.
If you get a negative number it would be lowered (i.e. 10+(-5)=5A).
Then, next time you run the algorithm you should ideally get 0A out of it and no change would be needed.
I do not know how often the tibber sensor for estimated energy in current hour you are using updates, but it would not make sense to run this algoritm more often than when it updates.
It might have very long delays, I do not know.
Another way to do this is to look at power instead and keep the total power of the "house" slightly below 10kW at all times.
But that of course depends on what loads you have in your house, some other things that you can not control may consume more than 10kW and then it does not help to keep only the car charging below 10kW...

@Sleepy81

10 kWh consumption limit * 230 /1000 = should give the amount of Amperage
I could draw continuously during the hour to reach a consumption og 10kWh.

That formula does not make any sense.
10000 * 230 / 1000 = 2300, not 43.
Try to add the units into your formula to see what you get.
The power, measured in Watts, is the current, measured in Ampére,
multiplied by the voltage, measured in Volts.
The power consumption is voltage multiplied by ampére, P = I * V.
Your limit is 10kWh, which means you draw 10000 W in 1 hour
(3600 seconds) on average.
Also, remember to calculate for each phase and add the numbers together.
E.g. for 3-phase:
P = I_L1 * V_L1 + I_L2 * V_L2 + I_L3 * V_L3 = I_per_phase * (V_L1 + V_L2 + V_L3)
If you have a Norwegian IT system (no dedicated neutral line), you have 115V from phase to ground.
If you, however, have a Norwegian TN system (with dedicated neutral line), you have 230V from phase to ground.
So, if you assume you have 115V on each phase (with respect to ground), you get:
P = I_per_phase * (3 * 115)
P_limit = I_per_phase * (V_per_phase / number_of_phases)
I_per_phase = P_limit / ((V_L1 + V_L2 + V_L3) / 3)
E.g:
I_per_phase = (10000 Wh  / (115V + 121V + 109V)) / 3 =  9.66 A
If your limit is P_limit and you have t_seconds_remaining left of the hour, and already used P_used, then it would be:
(P_limit - P_used) * (3600 / t_seconds_remaining) = I_per_phase * (V_per_phase / number_of_phases)
I_per_phase = (P_limit - P_used) * (3600 / t_seconds_remaining) / ((V_L1 + V_L2 + V_L3) / 3)
I_per_phase [A] = 10000 [W] - P_used [W] * (3600 [s] / t_seconds_remaining [s]) / 115 [V]
As the voltage per phase tends to vary over time, you might want to add some margin.
Also note that the voltage drop in your charging cable (all the way from the breaker box), depends on how
much current you draw, so make sure to use the Voltage reported from your Tibber device.


The color value of rendered image will exceed 1.0

Hello, I found that the color of predicted gaussian splatting will exceed 1.0.
I test re10k data, and add a break point here:
https://github.com/cvg/NoPoSplat/blob/5af8e16e8a5810a92c629c2eea7beb90ded278b1/src/model/model_wrapper.py#L231
I run the following code to check the maximum color value:
output.color.max()
tensor(1.0807, device='cuda:0')

The max color is 1.0807 > 1.0
What caused it? Is it because the coefficient of SHs is not being constrained?
And how to avoid this?

Hi, thanks for pointing this out. I am directly using the RGB values rasterized by this cuda implamention. I am not sure if this is the expected behavior, I will check further and let you know.


Add course averages

This PR adds the course averages using McGill Enhanced's crowdsourced sheet. The use was okay'ed by Koz and credits are given within the Class Average component.
The data is accessed using the Google Sheets API and a python script in /tools. It gets written as a Json in /assets and will be periodically updated (I am thinking every month or two). I chose to have to as a static asset instead of seeding it in the db because its a relative light file and it doesn't need to be updated by anyone else than the maintainers. This choice consistent with McGill Enhanced.
I'm still not sure if I can make the UI better tho, here is what it looks like right now:

Nice work!

What about folding the averages to max 5-6 most recent then having a "show all" button to expand it? It feels like it can get a bit long if you show all of them by default

(also, thoughts on making the font weight on the grades slightly more bold? i gave it font-medium in this screenshot)

Another useful thing I just thought of, it might be cool to put the instructor that taught during that term for each course average, can't think of a good way to fit it into the UI at the moment though, maybe just some really small text under the course term in the list?

What about folding the averages to max 5-6 most recent then having a "show all" button to expand it? It feels like it can get a bit long if you show all of them by default.
(also, thoughts on making the font weight on the grades slightly more bold? i gave it font-medium in this screenshot)

yesss good idea i'll hop on this

Another useful thing I just thought of, it might be cool to put the instructor that taught during that term for each course average, can't think of a good way to fit it into the UI at the moment though, maybe just some really small text under the course term in the list?

That's a really great idea yeah, I too struggle to think of the UI for now

Also one more thing, the text should scale better on mobile (too big)

I addressed most comments except the one except the one about showing the prof of each semester, we may need some brainstorming for that hmmm
Maybe its better in a different PR? up to you guys

I addressed most comments except the one except the one about showing the prof of each semester, we may need some brainstorming for that hmmm
Maybe its better in a different PR with some time for brainstorm? up to you guys

I just added it, what do you think?


Deprecate tpl funcs naming conflicts

If any.
See https://github.com/spf13/hugo/pull/3177

This is all good now.


Error when running storyblok pull-components with valid SPACE_ID and token.

Current behavior:
On the current version (3.32.3), running storyblok pull-components --space SPACE_ID is failing:
Error Output
- Executing pull-components task
X An error ocurred in pull-components task when load components data
X An error occurred when executing the pull-components task: Error: Error: TypeError: e.headers.entries is not a function

Expected behavior:
Script should create the components.SPACE_ID.json file.
Steps to reproduce:

Run storyblok login and log in to your account.
Run storyblok pull-components --space SPACE_ID with the current version (3.32.3) and it should fail.

Other information:
Running the exact same command, but pointing to version 3.28.1 works fine:
bunx<EMAIL_ADDRESS>pull-components --space SPACE_ID

+1, am running into the same issue

+1, Same problem here with 3.32.3

+1
I also tried version 3.31.1 and 3.30.0 without any success.
Version 3.25.3 seems to work for me.

+1 3.28.1 does seem to work however

+1

Version 3.29 of storyblok-cli did some major rewrites, including an upgrade of storyblok-js-client without any mentions about it in changelog. 👏

Thanks for reporting the issue guys, i will check this now

Hi everyone, thanks for raising this and for the information available on the issue. We are currently investigating where this error comes from.
I will keep you updated.

@mllustosa  Potential fix https://github.com/storyblok/storyblok-js-client/pull/852, once is merged I will release a new patch for the CLI that hopefully will solve this issue.

thanks @alvarosabu!

@thatzacdavis @mllustosa could you please try out the latest path v3.33.1 and confirm for me if the error is gone please?
Thank you 🙏🏻

@alvarosabu I've confirmed this new version is working for me. Thanks for the quick turnaround!

@alvarosabu works for me, thanks!

@alvarosabu Thanks for the quick reaction there, I confirm it is working as expected now also from my side. All the best!

@alvarosabu Thanks everyone for the fix. Have a great day.


Fix missing header  for std::sort

Hi, all
I am the maintainer of vcpkg. I found an issue in our latest vs preview (Visual Studio 2022 v17.12) test.
I think the change here is by design, it only needs to add a header file. You will easily reproduce this problem locally.
C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Tools\MSVC\14.41.34120\include\functional(31): note: see declaration of 'std'
D:/b/daxa/src/3.0.2-e19dccb089.clean/src/impl_instance.cpp(194): error C3861: 'sort': identifier not found

The issue occurred when trying to use std::sort without including the necessary <algorithm> header file. This PR adds the required include to ensure proper compilation.
And I also submitted a PR https://github.com/microsoft/vcpkg/pull/41461 to vcpkg to pay attention to this issue. :)
Thanks,
Frank

Hi Frankie! Thank you for your PR. We have experienced several of these header issues in the past due to our Linux support catching inconsistencies between Visual Studio and GCCs standard library internal inclusions. I really appreciate your help in fixing another!

@GabeRundlett
Thank you very much for your quick response and reply.  We will keep paying attention to and maintaining the construction and use of Daxa. For any questions about vcpkg, please contact me. :)


127 add df to download function

Closes #127
Closes #121
Closes #119

Created df_to_download function which returns csv formatted data
Added UID to results
Adjusted the record_no index to start at 1 instead of 0
Updated pytests
Added --download to cli.py

test_download_output.csv


Create delete trigger flow

Add to routes
Add to controller
Add to docs ( readme )

closed by #30


Added Interactable enabled check to PhysicalPressEventRouter - fix for 5833

Overview
Fix for issue #5833 where near interaction events were triggered when Interactable was disabled.
Added the fix by Julia to PhysicalPressEventRouter which only sets states and triggers near interaction events if Interactable is enabled.
Video of HandInteractionExample scene after the fix:
Issue 5833 Fix
Changes

Added CanRouteInput() to PhysicalPressEventRouter
Added doc comments to public methods
Added a test to PressableButtonTests

Verification

As a reviewer, it is possible to check out this change locally by using the following
commands (substituting {PR_ID} with the ID of this pull request):
git fetch origin pull/{PR_ID}/head:name_of_local_branch
git checkout name_of_local_branch

/azp run


Performance issues with luxonLocalizer

report a bug
What's the current behavior?
Luxon localizer seems to be having some performance problems.
In the following codesandbox I've set up the luxonLocalizer in the demo and added a console log. That console.log is happening very often. The performance seems to be much much worse in a project that i'm working on but this is a reproducable demo of the same thing happening.
https://codesandbox.io/s/admiring-forest-70cyh

What's the expected behavior?
Should perform a lot better and not be rerendering so often.

@cutterbl @olafur164
I'm experiencing the same problems with Luxon and was just wondering if there are any workarounds for the time being. I'm also using react-big-calendar with many slots, and it's starting to get slow...

Having the same issue 500 events and using resources. Switching the calendar format takes up to a few seconds.

I switched to date-fns for the time being.

@bu6n Thanks a lot, date-fns is a lot faster.


Update Workload code for Microsoft.Data.SqlClient.AzureManagedIdentityAuthenticationProvider

Current workload identity code authenticates fine against SQL Server but requires an DbConnectionInterceptor to inject the bearer token into the connection string.  Pod Identities do not have this requirement.  All that is required for Pod Identities is to set Authentication = SqlAuthenticationMethod.ActiveDirectoryManagedIdentity in the connection string.
Currently, setting Authentication = SqlAuthenticationMethod.ActiveDirectoryManagedIdentity in the connection string will result in:
Connection id "0HML5CDKNRKK5", Request id "0HML5CDKNRKK5:00000001": An unhandled exception was thrown by the application.
System.AggregateException: One or more errors occurred. (One or more errors occurred. (Received a non-retryable error. Identity Response Code: BadRequest, Response: {"error":"invalid_request","error_description":"Identity not found"}))
---> System.AggregateException: One or more errors occurred. (Received a non-retryable error. Identity Response Code: BadRequest, Response: {"error":"invalid_request","error_description":"Identity not found"})
---> Microsoft.Data.SqlClient.SqlException (0x80131904): Received a non-retryable error. Identity Response Code: BadRequest, Response: {"error":"invalid_request","error_description":"Identity not found"}
at  Microsoft.Data.SqlClient.AzureManagedIdentityAuthenticationProvider.AcquireTokenAsync(SqlAuthenticationParameters parameters)
ClientConnectionId:00000000-0000-0000-0000-000000000000

Using Workload Sidecar
Entity Framework Core 6.0.9 initialized 'TodoDbContext' using provider 'Microsoft.EntityFrameworkCore.SqlServer:6.0.9' with options: None
fail: Microsoft.EntityFrameworkCore.Database.Connection[20004]
An error occurred using the connection to database 'todo' on server 'tcp:cockatoo-20167-sql.database.windows.net,1433'.
fail: Microsoft.EntityFrameworkCore.Query[10100]
An exception occurred while iterating over the results of a query for context type 'TodoDbContext'.
System.AggregateException: One or more errors occurred. (One or more errors occurred. (Received a non-retryable error. Identity Response Code: BadRequest, Response: The client_id parameter is required.
))
---> System.AggregateException: One or more errors occurred. (Received a non-retryable error. Identity Response Code: BadRequest, Response: The client_id parameter is required.
)
---> Microsoft.Data.SqlClient.SqlException (0x80131904): Received a non-retryable error. Identity Response Code: BadRequest, Response: The client_id parameter is required.
     at Microsoft.Data.SqlClient.AzureManagedIdentityAuthenticationProvider.AcquireTokenAsync(SqlAuthenticationParameters parameters)
  ClientConnectionId:00000000-0000-0000-0000-000000000000

Closed by PR#4


An animated Landing page for website on opening

Is your feature request related to a problem? Please describe.
The landing page looks very normal
Want to add an animation effect in it such that the text "book finder" will animate and come like in this website
https://ak-shat-jain.github.io/FoodGenix/
that's also created by me
Describe the solution you'd like
create an CVG on figma and animate it using css
Describe alternatives you've considered
after animation landing page automatically redirects to index page after 3.5 seconds
Additional context
No response

Hey @devwasim @wasimreja I would like to work in this issue under JWOC 2023. Would be glad if you could assign this issue to me. Thanks. :)

Hello @wasimreja,
It will look great as a landing page
I first create an SVG from figma and import it into landing page and animate it using css

I want to work on this issue under JWOC @wasimreja

Hello @wasimreja Sr
I have created SVG image of text from figma

and I am looking to work in a Background same as that of Dark mode so as to match the theme with a white border

@wasimreja
I would like to work on this under JWOC.

Its Done already @Awesomeasma
@wasimreja Sr please review the PR


Switch to python-volapi  instead of running whole browser under the hood

Volafile exposes a websocket API (engine.IO to be more specific) which makes interaction with it quite easy. I'm currently maintaining python-volapi. It covers everything you need for interacting with volafile rooms and getting files' download links. I wrote simple download script that utilizes wget2 as download program (works only on Unix-like systems so far). There is no documentation for python-volapi atm but most of the functions are commented. If you'd be interested in a rewrite, fell free to ask me for help.

https://github.com/kadranel/python-volafile-downloader ;)


import esm vendors

In this diff I changed babel helpers imports to esm versions for
esm/es/umd bundles. For example
@babel/runtime/helpers/extends -> @babel/runtime/helpers/esm/extends

is-plain-object is upgraded to version with esm support.

[X] I have followed (at least) the PR section of the contributing guide.

The size is bigger because of cjs babel helpers in react-event-listener. @oliviertassinari maybe it's time to bring esm back to it?

@TrySound We are removing react-event-listener. The last usage of this module is in withWidth higher-order component. There is an effort to modernize it: #15678.

Ok, let's wait til that PR merged.

@TrySound What do you think of splitting the pull request in two. One for the update of the dependencies, one for the babel config? The update of the dependencies seems to be interesting on its own<EMAIL_ADDRESS>

is-plain object becomes a bit smaller<EMAIL_ADDRESS>convert-css-length is bigger because of interop around parse-unit dependency. I submitted PR there too. Let's see if it will be resolved. https://github.com/mattdesl/parse-unit/pull/1

@TrySound I have rebased the pull request on the master branch.


Combine generalized getSystem#() in a backward compatible manner

For example, 1 and 5 are the same if only up to quadratic, so just combine
Use syntax [A,B,C,N,f,g,h] = getSystem#()
Then use runExample to differentiate them

system1/5 done

Finished all systems, now fixing runExamples
Using runExample#P for polynomial and runExample#B for bilinear


Accessing Embedded Entries

Hi there,
I have a content type that has entries embedded inside of it, anywhere from 1 and above.  How to I access these?  I'm having difficulty getting to the fields of the entries, For example if I do
{{ page.contentful_fields.references | first }}
This gives me a #, joining with commas gives me #, # (assuming I have 2 references.
if I convert to JSON, I see this,
..."references":["#Contentful::Entry:0x00000002bf70f0","#Contentful::Entry:0x00000002ee3480"]...
I want to be able to enumerate the entries and get their fields.  Many thanks.

This plugin does not handle references at the moment. Sorry.


IDisposable on ILoggerProvider

Based on some of the discussions of this issue why is the ILoggerProvider interface marked as IDisposable? I understand there was a need for a "flushing" mechanism before application termination, but why has that become an obligation for the providers?
An example of this would be in the console logger provider or the debug logger provider.
Can this not be implemented similar to the DI pattern?

This would be a breaking change before 2.0.0, so putting this in Backlog milestone for now.

Removing IDisposable from ILoggerProvider would be a breaking change without much benefit.


implement server side rendering for viewing files

get file name
display that in the head meta tags

file link embed


Blog page has no margin from bottom also it needs some styling

Hello, @MonalikaPatnaik , i wolud like to work on this issue  as the GSSOC'23, could you please assign this to me

Heyy..are you done with your changes?? I suggest you to submit your PR soon!

I have already done it , pull request also!


Add plugin for linting

Why this change?

There is no linter included in kickstart.
Fixes #698

What was changed?

Add https://github.com/mfussenegger/nvim-lint as the choice of linter. This is a popular linter that is the default linter in nvim distros such as LazyVim.

I wonder why they decided not to do none-ls

What do you think about including this as an optional "kickstart.plugins.lint"? I don't think everyone needs an additional linter plugin, lots of languages provide all the linting you need through the LSP (so I think it just adds noise and confusion for people who are starting off and don't realize the LSP usually gives enough info for a lot of languages).

@tjdevries sure, could do that. 👍

@tjdevries have another look now! 😄

Great PR! Linter as an optional is really the way to go! :)

Thanks for your contribution. This is what Teej suggested so I'm gonna merge it.


Fix: Report third party time out error as warning

Fix https://github.com/sonarwhal/sonar/issues/627

@qzhou1607 there are issues in the build. Can you please fix them?

@molant  Done.


Adding tokenriot info

Adding the mainnet contract information for Token Riot. The JSON validates with npm run validate.

@logicalmechanism
plz do not include package-lock and yarn lock changes

@logicalmechanism
plz do not include package-lock and yarn lock changes

I will remove them and push the changes right now.

I meant you must not edit them (also not delete them from the code). leave them as is. You will need to force push the commits after reverting your changes locally

I meant you must not edit them (also not delete them from the code). leave them as is. You will need to force push the commits after reverting your changes locally

OK, only file to change is my addition now.

@ashisherc Is the PR good now or do I need to change anything else?


matrix-synapse: 1.88.0 -> 1.89.0

Description of changes
https://github.com/matrix-org/synapse/releases/tag/v1.89.0

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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

Currently deploying to my homeserver to test it. If everything goes well, I'd merge after that :)


add webhook handler for Travis CI

Travis CI provides some nice webhook payload. Customers should be able to simply specify a webhook handler URL of Lagoon to be able to trigger deploys after Travis tests pass.
https://docs.travis-ci.com/user/notifications/#configuring-webhook-notifications

No further interest in this, will be looking at CI integrations more broadly later this year


[feat] Add Proxy to core declarations

This PR adds Proxy to the standard Javascript library declarations provided by Flow.
Note:
I did not include tests with this PR (yet) as I am unaware how/where I should add them. Also, any testing guidelines you have for the project would be useful as well. Once somebody gets back to me with this information I would be happy to add tests for this.
--
Great work on the project btw. Flow is awesome! 😃

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at<EMAIL_ADDRESS>Thanks!

Glad you're enjoying using Flow and thanks for the contribution! If you'd like to add tests, I recommend using our new test framework, which works like
cd flow # From inside the flow repo
npm install # Tool is built using Flow
./tool new-test lib/proxy # Creates a new empty test
./tool test lib/proxy # Runs the new test
$EDITOR newtests/lib/proxy/test.js # Edit the test

It's documented a little bit in https://github.com/facebook/flow/blob/master/newtests/README.md and https://github.com/facebook/flow/blob/master/newtests/tool_test_example/test.js is an example test.
It's up to you if you'd like to add a test. Obviously, we'd love tests, but we haven't been requiring them thus far for library definitions (though flow-typed is planning on requiring them). So let me know what you'd like to do!  I'm also afraid I can't merge this until the CLA is signed either way.
Thanks again!

No problem! I appreciate the info.
Before submitting this PR I signed the CLA but it hasn't added a CLA Signed label to this PR. I sent an email to<EMAIL_ADDRESS>2 days ago regarding this.

Oh weird, sorry about that! I'll ping the opensource people @ FB and get this fixed!

No worries! 😃

hello bot.

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

@facebook-github-bot import

Thanks for importing. If you are an FB employee go to Phabricator to review internal test results.