[Bug]: kubectl-cnpg v1.23.3 status command broken

Is there an existing issue already for this bug?

[X] I have searched for an existing issue, and could not find anything. I believe this is a new bug.

I have read the troubleshooting guide

[X] I have read the troubleshooting guide and I think this is a new bug.

I am running a supported version of CloudNativePG

[X] I have read the troubleshooting guide and I think this is a new bug.

Contact Details
No response
Version
1.23.2
What version of Kubernetes are you using?
1.28
What is your Kubernetes environment?
Other
How did you install the operator?
Helm
What happened?
Since kubectl-cnpg plugin version 1.23.3 the status command can not extract the status from the postgres-pods
Cluster is running on cnpg v1.23.2
Cluster Summary
Name:                postgres-hedgedoc
Namespace:           hedgedoc
PostgreSQL Image:    cloudnative-pg/postgresql:14.8-6
Primary instance:    postgres-hedgedoc-4
Primary start time:  2024-06-18 14:04:24 +0000 UTC (uptime 1176h32m31s)
Status:              Cluster in healthy state
Instances:           2
Ready instances:     2

Certificates Status
Certificate Name               Expiration Date                Days Left Until Expiration
----------------               ---------------                --------------------------
postgres-hedgedoc-ca           2024-08-17 00:10:20 +0000 UTC  10.40
postgres-hedgedoc-replication  2024-08-17 00:10:36 +0000 UTC  10.40
postgres-hedgedoc-server       2024-08-17 00:10:28 +0000 UTC  10.40

Continuous Backup status
First Point of Recoverability:  2024-07-27T02:01:06Z
No Primary instance found
Physical backups
Primary instance not found

Streaming Replication status
Primary instance not found

Unmanaged Replication Slot Status
No unmanaged replication slots found

Managed roles status
No roles managed

Tablespaces status
No managed tablespaces

Pod Disruption Budgets status
Name                       Role     Expected Pods  Current Healthy  Minimum Desired Healthy  Disruptions Allowed
----                       ----     -------------  ---------------  -----------------------  -------------------
postgres-hedgedoc-primary  primary  1              1                1                        0

Instances status
Name                 Database Size  Current LSN  Replication role  Status              QoS         Manager Version  Node
----                 -------------  -----------  ----------------  ------              ---         ---------------  ----
postgres-hedgedoc-4  -              -            -                 ServiceUnavailable  Guaranteed  -                worker-2
postgres-hedgedoc-5  -              -            -                 ServiceUnavailable  Guaranteed  -                worker-1

Error(s) extracting status
-----------------------------------
the server is currently unable to handle the request (get pods http:postgres-hedgedoc-4:8000)
the server is currently unable to handle the request (get pods http:postgres-hedgedoc-5:8000)

With plugin version 1.23.2 everything is shown as expected.
We have the following networkpolicies in place which are derived from the cnpg-docs example
Clusterwide deny all
---
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: allow-postgres-management
  namespace: hedgedoc
spec:
  egress:
  - {}
  ingress:
  - from:
    - namespaceSelector:
        matchLabels:
          kubernetes.io/metadata.name: postgres-operator
    - namespaceSelector:
        matchLabels:
          kubernetes.io/metadata.name: monitoring
    ports:
    - port: status
      protocol: TCP
    - port: metrics
      protocol: TCP
  podSelector:
    matchLabels:
      cnpg.io/cluster: postgres-hedgedoc
  policyTypes:
  - Ingress
  - Egress
---
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: allow-postgres-cluster
  namespace: hedgedoc
spec:
  ingress:
  - from:
    - podSelector:
        matchLabels:
          cnpg.io/cluster: postgres-hedgedoc
    ports:
    - port: postgresql
      protocol: TCP
  podSelector:
    matchLabels:
      cnpg.io/cluster: postgres-hedgedoc
  policyTypes:
  - Ingress

Maybe this PR broke the status requests https://github.com/cloudnative-pg/cloudnative-pg/pull/4974?
Cluster resource
No response
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@HaveFun83 Yes, now the status it's retrieved using a proxy so the user executing the command needs permissions to proxy the status port, otherwise, it will not be able to get the status

i ran this as cluster-admin and got the error.
I also tried to allow all ingress connection from the kube-system namespace which also not worked.
It only works when i allow allow ingress traffic within the network-policy but this make no sense as this will open the connection from everywhere and we have to stay within our security and compliance rules

@sxd are the new permission requirements documented somewhere?

@achanda no that I remember only the PR that is there https://github.com/cloudnative-pg/cloudnative-pg/pull/4974

@HaveFun83 do you have news on this? adding permission fixed the issue? or it was a network issue ? can you elaborate a bit more here ?

@sxd Thanks for your support. Don't know which permission i need to add to the cluster-admin user?
Currently the status command only works when i allow all ingress traffic towards cluster pods, but this is not possible within our environment.
As workaround i downgrade the plugin to v1.23.2 which work as expected.
Any help or tips are greatly appreciated
I can try to reproduce this issue within an dev environment?

@HaveFun83 well, the ingress part will make sense since the new version doesn't use pod/exec to get into the pod land execute a command but instead proxy the port of the service to restrict the access only to that.
It will be very helpful if you can reproduce the issue so we can look into this reproduce and work in a fix.
On the other hand I'm going to create a ticket to handle the issue mentioned by @achanda that we don't have documentation for the permissions.

As we use calico we implemented the following globalnetworkpolicy to allow the cnpg plugin proxy traffic to every cnpg cluster on the status port
apiVersion: projectcalico.org/v3
kind: GlobalNetworkPolicy
metadata:
  name: allow-cnpg-status
spec:
  order: 1
  namespaceSelector: has(projectcalico.org/name) && projectcalico.org/name not in {"kube-system", "calico-system", "calico-apiserver"}
  types:
    - Ingress
  ingress:
    - action: Allow
      destination:
        selector: has(cnpg.io/cluster)
        ports:
          - 8000
      protocol: TCP
      source:
        nets:
          - "<control-plane projectcalico.org/IPv4IPIPTunnelAddr>/32"
          ...

From our side this issue is resolved.

Had a look at this again this morning, hoping I had overseen something. But haven't found anything so far.

as soon as I remove my own network policy (which includes the operator), the status command is working
when I apply the sample policy, the command is broken

@till can you show your network-policy? Which CNI do you use?

Using Calico, and the network policy is the sample in the repo:
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: allow-operator
spec:
  podSelector:
    matchLabels:
      cnpg.io/cluster: cluster-example # The label value must be the cluster name
  ingress:
    - from:
        - namespaceSelector:
            matchLabels:
              kubernetes.io/metadata.name: cnpg-system # Namespace where the operator is deployed
          podSelector:
            matchLabels:
              app.kubernetes.io/name: cloudnative-pg # Matches the Operator pod
      ports:
        - port: 8000
        - port: 5432

I only changed the db instance name.

Can you double check that the networkpolicy match the right labels?
Is there any default-deny policy in place?
Which cnpg plugin version do you use?

Using Calico, and the network policy is the sample in the repo:
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: allow-operator
spec:
podSelector:
matchLabels:
cnpg.io/cluster: cluster-example # The label value must be the cluster name
ingress:
- from:
- namespaceSelector:
matchLabels:
kubernetes.io/metadata.name: cnpg-system # Namespace where the operator is deployed
podSelector:
matchLabels:
app.kubernetes.io/name: cloudnative-pg # Matches the Operator pod
ports:
- port: 8000
- port: 5432
I only changed the db instance name.

1.23.5 of the operator and the plugin
I tripple checked, the operator has the label the sample policy uses, I updated the name of the db cluster
there's no other network policy in the namespace that could "deny" anything right now

As we use calico we implemented the following globalnetworkpolicy to allow the cnpg plugin proxy traffic to every cnpg cluster on the status port
apiVersion: projectcalico.org/v3
kind: GlobalNetworkPolicy
metadata:
name: allow-cnpg-status
spec:
order: 1
namespaceSelector: has(projectcalico.org/name) && projectcalico.org/name not in {"kube-system", "calico-system", "calico-apiserver"}
types:
- Ingress
ingress:
- action: Allow
destination:
selector: has(cnpg.io/cluster)
ports:
- 8000
protocol: TCP
source:
nets:
- "<control-plane projectcalico.org/IPv4IPIPTunnelAddr>/32"
...
From our side this issue is resolved.

Thanks for the tip, this works for me as well. However this is quite painful to craft the network policies to list the explicit IPv4IPIPTunnelAddr addresses for the control plane nodes.


risingwave ctl scale --workers doesn't support worker_host

Describe the bug
According to risingwave ctl scale vertical --help, the --workers supports all, worker_id and worker_host. But it can only support all and worker_id in the testing. The worker_host will raise an error like Invalid worker input: http://benchmark-risingwave-compute-c-0
      --workers <all or worker_id or worker_host, ...>
          The worker that needs to be scheduled, worker_id and worker_host are both supported

Related code https://github.com/risingwavelabs/risingwave/blob/main/src/ctl/src/cmd_impl/scale/resize.rs#L154-L178
Related document https://docs.risingwave.com/docs/dev/k8s-cluster-scaling/#adjust-the-parallelism-of-a-worker-node-vertical-scaling
Error message/log
No response
To Reproduce
No response
Expected behavior
No response
How did you deploy RisingWave?
No response
The version of RisingWave
nightly-20231123
dev=> select version();
                                     version
----------------------------------------------------------------------------------
 PostgreSQL 9.5-RisingWave-1.3.0-alpha (9ae870545193e9738dcb1f3376849be124f9dd64)
(1 row)

Additional context
No response

It appears that we need to specify the advertise port as well.
https://github.com/risingwavelabs/risingwave/blob/f16fd493303d03b3abf28932bc4be969b15127f5/src/ctl/src/cmd_impl/scale/resize.rs#L146-L152

Seems we need to improve the help message? should be host:port
  --workers <all or worker_id or worker_host, ...>
      The worker that needs to be scheduled, worker_id and worker_host are both supported


tickets/DM-38729: Add fileserver creation

This adds a way to create/destroy a fileserver for a given user.

For the work I've been doing, I also deleted tests.support.kubernetes in favor of using the version from Safir and have started adding the required additional methods to the mock provided in Safir. (https://github.com/lsst-sqre/safir/pull/162 is the first.) You'll want to do the same thing, since we don't want to keep two copies of this mock.

I have (for ticket hygiene reasons) moved the work to DM-38972.  I'm going to PR that one, but address the comments from this one over there.

@rra if that looks like we are up-to-date with respect to DM-38972 and that I have adequately captured the remaining work, please close this PR (without merging).

Replaced with #103.


Fasta, VM, lineStarts and CR

This test file uses CR as line endings: tests/lib_2/mirrors/method_mirror_source_line_ending_cr.dart.
And fasta generates a dill file with line endings for the file being specified as [0, 372, 373].
So basically, fasta inteprets it as one big line.
The VM, on the contrary sees it as many lines:
https://github.com/dart-lang/sdk/blob/3df126c4972e8d41d85e4e43cb27f45450660a23/runtime/vm/object.cc#L10050-L10061
This means that (assuming #33271 is fixed) if I ask the VM for the sources for a function in the file, the VM translates the token position to line 1 some high column and tries to find that, but cannot since it actually sees it as line > 1 (e.g. 9 for function oneLineCR).
I assume the better behavior would be that fasta accepts CR as a line break to - at least when creating the lineStarts array.
It will probably also have an effect on the error messages from fasta if theres a warning or error in such a file...
/cc @peter-ahe-google

(On my system, both vim and emacs see the file as a single line too though, so maybe someone should make a decision about what we actually want here --- there is a test though tests/lib_2/mirrors/method_mirror_source_line_ending_test.dart).
/cc @lrhn ..?

That decision was made, and we want CR+LF, CR, or LF to act as line terminators.
There are two places in the specification where line terminators matter (other than as whitespace):

Single-line comments, and
Multi-line strings.

For the former, it doesn't matter whether you recognize CR+LF as a single line terminator, but you must recognize both CR and LF, otherwise the rest of the program is swallowed by the comment.
For the latter, each line terminator introduces a single LF (U+000A) character into the string.
So, as a test, try inserting a // comment or multi-line string in the code and see how it is treated.


Clone failed: Cloning into 'management-state/catalog-cache/380859f1003fe7603cddc6c15b34b7263f1f0deaa92ddcde465811d032ee7078'... fatal: unable to access 'https://git.rancher.io/charts/': gnutls_handshake() failed: Error in the pull function. : exit status 128

What kind of request is this (question/bug/enhancement/feature request):
Steps to reproduce (least amount of steps as possible):
Result:
Other details that may be helpful:
rancheruser@kubernetes1:~$ git ls-remote https://git.rancher.io/charts
13abc1a70140c01357754ae2dcc972ec45d82161        HEAD
28cb367ac24077aad3d667db7bc9c59002b03ad1        refs/heads/dev
a8e4969e7d1e97ced8592e6b9cfcdf9a8c76941d        refs/heads/helm3
3af9098b47f0a53da237ade4a9e634aeadbf30ae        refs/heads/k8s-1.16
13abc1a70140c01357754ae2dcc972ec45d82161        refs/heads/master
rancheruser@kubernetes1:~$ ./kubectl --namespace cattle-system get pods
rancheruser@kubernetes1:~$ ./kubectl --namespace cattle-system get pods
NAME                                    READY   STATUS             RESTARTS   AGE
cattle-cluster-agent-5cb9b6cfd9-8jbcb   1/1     Running            0          44h
cattle-node-agent-2g945                 1/1     Running            0          44h
cattle-node-agent-7fr4s                 1/1     Running            0          44h
cattle-node-agent-jr7n8                 0/1     CrashLoopBackOff   536        44h
cattle-node-agent-r2wnz                 1/1     Running            0          44h
cattle-node-agent-xgp8b                 1/1     Running            0          44h
cattle-node-agent-znxsx                 1/1     Running            0          44h
rancher-7745c8fdbb-pxfdv                1/1     Running            1          44h
rancher-7745c8fdbb-wh44z                1/1     Running            1          44h
rancher-7745c8fdbb-z6z4s                1/1     Running            2          44h
rancheruser@kubernetes1:~$ ./kubectl --namespace cattle-system exec -it rancher-7d769c47d6-9knfj  -- /bin/bash
root@rancher-7d769c47d6-9knfj:/var/lib/rancher# git ls-remote https://git.rancher.io/charts
fatal: unable to access 'https://git.rancher.io/charts/': gnutls_handshake() failed: Error in the pull function.
root@rancher-7d769c47d6-9knfj:/var/lib/rancher#
**E

nvironment information**

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.3.5
Installation option (single install/HA):
HA

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): custom
Machine type (cloud/VM/metal) and specifications (CPU/memory): VM
Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.3", GitCommit:"06ad960bfd03b39c8310aaf92d1e7c12ce618213", GitTreeState:"clean", BuildDate:"2020-02-11T18:14:22Z", GoVersion:"go1.13.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.2", GitCommit:"59603c6e503c87169aea6106f57b9f242f64df89", GitTreeState:"clean", BuildDate:"2020-01-18T23:22:30Z", GoVersion:"go1.13.5", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version):

Client: Docker Engine - Community
 Version:           19.03.6
 API version:       1.39 (downgraded from 1.40)
 Go version:        go1.12.16
 Git commit:        369ce74a3c
 Built:             Thu Feb 13 01:28:06 2020
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.9
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.11.13
  Git commit:       039a7df
  Built:            Wed Sep  4 16:19:38 2019
  OS/Arch:          linux/amd64
  Experimental:     false

our cluster is behind corporate proxy and firewall. it turns out that our proxy config on the machine works but unfortunately even we set proxy for docker it doesnt work in some cases. we removed all proxy definitions and give access to image repositories through corp firewall. now everything is working as expected


Remove _get_node_error from Result

_get_node_error is an internal getter in Result which connects to a DB to return a value. It is called once in execution.py. This must be removed from Result since client side object can't be aware of the DB. execution.py needs it own logic to get the value from the DB.
Acceptance Criteria

[ ] _get_node_error is removed from Result
[ ] logic added in execution.py to get error value from DB

In this issue I will just be cleaning up some docstrings in get_node_error and nearby similar methods


Use<EMAIL_ADDRESS>for all CI builds (and brings windows at par with macos and linux)

Pre-flight Checklist

Please remember that if you are logging a bug for some service that has stopped working or is working incorrectly, please log the bug here
If you are requesting support for a new service in Ferdi, please log it here
Please remember to read the self-help documentation - in case it helps you unblock yourself for issues related to older versions of recipes that were installed on your machine. (These will get automatically upgraded when you upgrade to the newer versions of Ferdi, but to get new recipes between Ferdi releases, this documentation is quite useful.)
Please consider supporting Ferdi!
👉  https://github.com/sponsors/getferdi
👉  https://opencollective.com/getferdi/donate
Please ensure you've completed all of the following.

[x] I have read the Contributing Guidelines for this project.
[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Description of Change
Made the GH build on windows OS to specifically use<EMAIL_ADDRESS>Motivation and Context
This was somehow not consistent between macos, linux and windows - only for CI builds.
Screenshots

Checklist

[x] My pull request is properly named
[x] The changes respect the code style of the project ($ npm run lint && npm run reformat-files && npm run manage-translations && npm run apply-branding)
[x] npm test passes
[x] I tested/previewed my changes locally

Release Notes

Based on errors while getting this consistency across OSes, I had to upgrade node-gyp from 8.0.0 to 8.1.0


Associated constants for One and Zero

Any reason we can't have ONE and ZERO implemented as constants rather than methods? Given that num_traits is a low level crate, it effectively forbids any higher level constructs with associated constants atm.

Unless there are objections, I'm giving this a try (affecting way more traits than I expected, but still).

It would be a breaking change to both users and implementors, which we strongly avoid, and associated constants require a newer rustc than our conservative 1.8.  Also, some types which implement these traits can't have constant values at all, like BigInt.

@cuviper  thanks for the answer!

It would be a breaking change to both users and implementors, which we strongly avoid,

The way I see it is adding the associated consts first, using them internally where possible, marking the old methods with #[deprecated] and then removing the old ones in 0.3. So I don't think this is an issue.

associated constants require a newer rustc than our conservative 1.8

I'm curious about this. Why 1.8 in particular? What are the guidelines/schedule for updating this base requirement?

some types which implement these traits can't have constant values at all, like BigInt

This is truly unfortunate, and it's a real blocker.

Following up on  the last one - there does appear to be some light at the end of the tunnel, see https://github.com/rust-num/num-bigint/issues/36

The way I see it is adding the associated consts first

Even that is a breaking change for third-party implementations of the traits.  The only non-breaking way to expand a trait is with a default implementation of new items, which we can't do here.

I'm curious about this. Why 1.8 in particular? What are the guidelines/schedule for updating this base requirement?

It used to be 1.0, then other factors forced us to raise it to 1.8 -- rust-num/num#257.  I treat raising the minimum rustc as a breaking change, but the community has mixed opinions on this -- rust-lang-nursery/api-guidelines#123.  I don't have a schedule, but I just keep it conservative, since num-traits is a common dependency, often even in other crates' public API.  Increasing num-traits' minimum rustc will force that decision on all of its dependents too.

Following up on the last one - there does appear to be some light at the end of the tunnel, see rust-num/num-bigint#36

Maybe, but this is just one example.  We don't control all possible implementations of these traits.

Of course, nothing stops you from implementing your own One trait with different trade-offs.  The ubiquity of num-traits is a benefit to its use, but also constrains its ability to change.

Even that is a breaking change for third-party implementations of the traits.

Indeed.

Increasing num-traits' minimum rustc will force that decision on all of its dependents too.

ok, thanks for the links!

Maybe, but this is just one example. We don't control all possible implementations of these traits.

While true, you do control the goals of this crate's traits. There is a value in restricting the functionality a bit at the exchange of having nice associated constants use (which makes a big part of this crate's API much more elegant). It's hard to move forward if you have "all possible implementations" in scope. Even rustc has utilities to check all the crates.io contents for breaking changes.
For making this bold move, I'd think all we need is to ask the clients (are there any communication channels for this project other than the GH issues?) for whether or not this is going to be a showstopper for them.

BTW, this comment is outdated:
// FIXME (#5527): This should be an associated constant

This issue number is outdated and it is not so clear whether it should be an associated constant, if bignums are supposed to be able to implement it.

Yeah, that FIXME is an old issue from when this was still in rust-lang/rust.  We should remove it.

Yeah, that FIXME is an old issue from when this was still in rust-lang/rust. We should remove it.

See #62.

If you want a way forward here, I suggest something new like trait OneConst: One with a compiler-probed cfg guard, like we do for cfg(has_i128).

As discussed in #91, the better long term solution is to use impl const in https://github.com/rust-lang/rfcs/pull/2632. Folks can define their own traits for OneConst etc. as a stop-gap measure, but I don't think we want to be stuck with that API in num-traits.


Implement GitHub Actions to test the package automatically upon each new release

We have implemented a GitHub Action that is triggered by the publication of a new release to test the installation of SDePER across PyPI, Conda, and Docker. This action specifically tests Python versions 3.9.12 and the latest 3.10, and is limited to the Ubuntu OS due to observed installation failures on Windows and macOS.


A pull request to fix all unittest issues

Previously the unittests expected a dummy healthcheck to be already in place in the /tmp directory, have modified the test setup function to copy a dummy healthcheck to the /tmp/ location before each test

Thanks @sarathsreedharan

is this fixed ?
i am still seeing the error:
for module in sys.modules.itervalues():
RuntimeError: dictionary changed size during iteration

Are you seeing this issue while running unittest?
Can you tell me which unittest is producing this error and what version of python you are using?

Looks like this is the same issue as #6, will raise a pull request to update the document to reflect the use nosetests.


Add emotes to chat

add emotes to chat mapper
display rank before name (preview)

the texture pack must be updated to see the emotes ⚠
Big tanks to Watich for lending me an account (what a bro)

Bug: bad font when a none existing emote

please rebase your branch

we have to add the emote json into the data submodules

Also this PR require merging:

#aresrpg/data#3
#aresrpg/ressourcepacks#7

/merge

lol nice try hard

but the 4th commit is still not conventional

/merge


make self-hosted service free

Or let me save state to my local instead of Pulumi SAAS.

Hi @arash-bizcover
We have a number of open source backends you can already use to save your state with Pulumi
You would 'pulumi logout' of the SaaS and then 'Pulumi login' to one of the other backends like in this doc
https://www.pulumi.com/docs/reference/cli/pulumi_login/
Paul

@stack72 thanks man 👍 👍 .
Since last year, whenever I searched Pulumi self managed I was seeing only enterprise version and was going back to my Terraform disappointed.
Now I can ditch Terraform harder than brick loops for good old js 😁.


PrimoBO: "Take from last occurrence"

Primo back office has the "Take from last occurrence" transformation built in out of the box. Can this be replicated in XML?
For example, when there are multiple dc.type fields, import and display only the last one: For instance:
OAI Metadata:
dc:typeDataset</dc:type>
dc:typePreprint</dc:type>
Should return just dc:type\Preprint</dc:type>

Using [last()] should work. So for the above, you can use this:
rule "copy last type"
when
	true
then
	copy "//*[name()='dc:type'][last()]" to "dc"."type"
end

Hi Mike,
I'm just getting back to this after working on another project. This worked for me.
Thank you.
Craig.

Moved to Wiki.


Added refactored glide support to new makefile

Work in progress for makefile refactoring. This PR has improved support for running containerized glide using a named volume.
Verification
$ rm -rf vendor
$ make -f Makefile.refactor.make install-deps

👍 Yep, that's the plan. update-deps is a different problem.


Add new Kanister function WaitV2

Change Overview
This PR adds new function WaitV2 improved version of existing Wait function which simplifies the condition definition.
Instead of Jsonpath to fetch K8s object value, we can use go-template syntax which can be validated with kubectl.
e.g To check if the deployment is ready, once can form following go-template which can be validated with kubectl -
$ kubectl get deploy -n kanisterwaittest-b58j2 test-deployment-tntfb -o go-template='{{ $available := false }}{{ range $condition := $.status.conditions }}{{ if and (eq .type "Available") (eq .status "True")  }}{{ $available = true }}{{ end }}{{ end }}{{ $available }}'
true

The same go-template can be used in the WaitV2 function arg to define condition
apiVersion: cr.kanister.io/v1alpha1
kind: Blueprint
metadata:
  name: wait-blueprint
actions:
  backup:
    phases:
    - func: WaitV2
      name: waitForRestoreReady
      args:
        timeout: 5m
        conditions:
          anyOf:
          - condition: '{{ $available := false }}{{ range $condition := $.status.conditions }}{{ if and (eq .type "Available") (eq .status "True") }}{{ $available = true }}{{ end }}{{ end }}{{ $available }}'
            objectReference:
              apiVersion: "v1"
              group: "apps"
              name: "{{ .Object.metadata.name }}"
              namespace: "{{ .Object.metadata.namespace }}"
              resource: "deployments"

Pull request type
Please check the type of change your PR introduces:

[ ] :construction: Work in Progress
[ ] :rainbow: Refactoring (no functional changes, no api changes)
[ ] :hamster: Trivial/Minor
[ ] :bug: Bugfix
[ ] :sunflower: Feature
[ ] :world_map: Documentation
[ ] :robot: Test

Issues

fixes #1583

Test Plan

[ ] :muscle: Manual

[ ] :zap: Unit test

[ ] :green_heart: E2E

Added unit tests

Manually validated the BP mentioned in the PR description on a deployment

Rebased and fixed conflicts. @pavannd1 could you please take a look?


Documentation for Hermes v0.2

Codecov Report

Merging #792 (4518f2c) into master (b1b37f5) will increase coverage by 30.6%.
The diff coverage is n/a.

:exclamation: Current head 4518f2c differs from pull request most recent head 47ca66d. Consider uploading reports for the commit 47ca66d to get more accurate results

@@            Coverage Diff            @@
##           master    #792      +/-   ##
=========================================
+ Coverage    13.6%   44.2%   +30.6%
=========================================
  Files          69     167      +98
  Lines        3752   11471    +7719
  Branches     1374       0    -1374
=========================================
+ Hits          513    5081    +4568
- Misses       2618    6390    +3772
+ Partials      621       0     -621

Impacted Files
Coverage Δ

...application/ics20_fungible_token_transfer/error.rs
0.0% <ø> (ø)

...ion/ics20_fungible_token_transfer/msgs/transfer.rs
22.2% <ø> (ø)

..._transfer/relay_application_logic/send_transfer.rs
85.7% <ø> (ø)

modules/src/events.rs
0.0% <ø> (ø)

modules/src/handler.rs
100.0% <ø> (ø)

modules/src/ics02_client/client_consensus.rs
55.8% <ø> (ø)

modules/src/ics02_client/client_def.rs
32.3% <ø> (ø)

modules/src/ics02_client/client_state.rs
65.1% <ø> (ø)

modules/src/ics02_client/client_type.rs
79.1% <ø> (+31.5%)
:arrow_up:

modules/src/ics02_client/context.rs
90.4% <ø> (ø)

... and 268 more

Continue to review full report at Codecov.

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


Password Generated After Prompts

**WHEN all prompts are answered
THEN a password is generated that matches the selected criteria
**

This is being done successfully.

Just need to get it to display in the window.


fix https_client bug

I fixed a bug described in this issue in which the body variable in the  test_https_client() is set to an empty buffer which prevents the user of the demo from seeing the actual HTTP response.

I've fixed it directly in the newly-published embedded-svc increment. The original code should now work fine.


person.deleteFace promise doesnt resolve to any result

const res = await api.face.person.deleteFace(personGroupId, personId, persistedFaceId)
console.log('removeFaceFromPerson result ->', res)

console log prints nada
removeFaceFromPerson result ->

it is just and empty string, it seems

That's what the API returns, so that's by design.  What would you rather it return?

Aha. I understand. I was confused by the comments in the code. I thought it might return some kind of success message.

Fair point.  I believe that's called cut and past 😄

Should it be this ?
A successful call returns an empty response body.
If there is an error, it wouldnt be as a return value, it would reject the promise, right ?

or empty string, maybe. :)

Ah, just found this a tiny bit above, hehe


tests: addition of mock dependency

Adds forgotten mock dependency for tests.

Signed-off-by: Tibor Simko<EMAIL_ADDRESS>

LGTM


error from chrome.

the error :
Manifest version 2 is deprecated, and support will be removed in 2023. See https://developer.chrome.com/blog/mv2-transition/ for more details.
{
"manifest_version": 2,
"name": "Big Tech Detective",
"version": "1.0.0",
"background": {
"scripts": [
"background.js",
"reload.js"
]
},
"content_scripts":[
{
"matches": ["<all_urls>"],
"js": ["lib/d3.min.js", "content.js"],
"css": ["pagecss.css"]
}],
"browser_action": {
"default_icon": "btd_icon_logo_128x128.png"
},
"permissions": [
	"<all_urls>",
	"tabs",
	"webRequest",
	"storage"
],
"web_accessible_resources":["assets/icons/unlock_icon.png","assets/icons/lock_icon.png", "assets/icons/copy_clipboard.png","assets/fonts/basis-grotesque-mono.otf","assets/fonts/GT-Walsheim-Regular.otf","assets/fonts/GT-Walsheim-Bold.otf","assets/fonts/GT-Walsheim-Black.otf"]

}

any fixes?


Cannot copy/paste lucidchart diagram into draw.io empty diagram

Preflight Checklist

[ x] I agree to follow the Code of Conduct that this project adheres to.
[ x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Describe the bug
Cannot import lucidchart diagram into draw.io as following the steps described here:
https://desk.draw.io/support/solutions/articles/16000063693-how-to-import-lucidchart-diagrams-into-draw-io
To Reproduce
Steps to reproduce the behavior:

have a lucidchart diagram open
select all with ctr-a
copy with ctr-c
paste into a draw.io blank diagram with ctr-v

Expected behavior
lucidchart diagram will be imported into blank draw.io document
Screenshots
If applicable, add screenshots to help explain your problem.
draw.io version (In the Help->About menu of the draw.io editor):
in-browser, browser: chrome

draw.io version [e.g. 12.6.7]

Desktop (please complete the following information):
chrome 83

draw.io version not provided

@alderg i'm using in browser, chrome 83

Fixed in 13.1.13.


Add Speech bubble tip

Allo @yeoman,
I finally found the time to finalize this PR which will close #11.
It’s ready for review :octocat:
Let me know what you think.
Could the code be written more beautiful? Because it introduces mad conditions and weird numbers :grin:

Found an issue:
❯ echo '1\n2\n2\n3\n4\n5\n6\n7\n8' | yosay

    ╭──────────────────────────╮
     _-----_     │             1            │
    |       |    │             2            │
    |--(o)--|    │             2            │
   `---------´   │             3            │
    ( _´U`_ )    │             4            │
    /___A___\   /│             5            │
     |  ~  |     │             6            │
   __'.___.'__   │             7            │
 ´   `  |° ´ Y ` │             8            │
                 ╰──────────────────────────╯

// @SBoudrias @stephenplusplus

Found an issue:

Oops. Just fixed that 😊

Opps. Travis failed because of a linting error. Just fixed that and force pushed 1nce again.

@sindresorhus I’m done for now :octocat: Need some Feedback to some outdated diff comments.

Answered

Thanks. I’m done for now. Did the constants thingie.

I like your new profile pic by the way 😻
</offtopic>

🔔 @SBoudrias @stephenplusplus @sindresorhus
😘

Looks great! 🎉
Thanks for this awesome addition @mischah :)

My pleasure 😊


Using partial with declare class doesn't work as expected

Summary
I wanted to validate on a DeepPartial, but the validation doesn't work as expected when using a type via declare class. It seems to work as expected if I use an interface. I included a repl that shows the issue. However, I'm trying to use a type from a third party package that defines its types via declare class.
Code occuring the bug
Reproducible demo:
<EMAIL_ADDRESS>import TSON from "typescript-json";

type DeepPartial<T> = T extends object ? {
  [P in keyof T]?: DeepPartial<T[P]>;
} : T;

const input = { a: 'valid' }

console.log('Works with interface:')

interface TestInterface {
  a: string;
}

const res = TSON.validateEquals<TestInterface>(input);
console.log('valid:', res)

const res2 = TSON.validateEquals<Partial<TestInterface>>(input);
console.log('valid:', res2)

const res3 = TSON.validateEquals<DeepPartial<TestInterface>>(input);
console.log('valid:', res3)

console.log('')
console.log('---------------------------')
console.log('')

console.log('Does not work with declare class:')

declare class TestClass {
  a: string;
}

const res4 = TSON.validateEquals<TestClass>(input);
console.log('valid:', res4)

const res5 = TSON.validateEquals<Partial<TestClass>>(input);
console.log('should be valid:', res5)

const res6 = TSON.validateEquals<DeepPartial<TestClass>>(input);
console.log('should be valid:', res6)

res5 is bug, but res6 is not.
I'll fix this bug soon.

Out of curiosity why is res6 not a bug? Partial and DeepPartial should be the same for the example.

@tjhiggins Ah, its bug, right. I misunderstood the DeepPartial type (I understood that non-object type be never).
Anyway, I've fixed the bug what you've reported. Thanks for your good point advising reporting.
Update to 3.3.7 version, then the bug would be fixed like below:
Jeongho Nam@JH-DESKNOTE MINGW64 /d/github/samchon/typescript-json (v3.3)
$ npm run issue 226

><EMAIL_ADDRESS>issue
> node test/issue "226"

Works with interface:
valid: { success: true, errors: [] }
valid: { success: true, errors: [] }
valid: { success: true, errors: [] }

---------------------------

Does not work with declare class:
valid: { success: true, errors: [] }
should be valid: { success: true, errors: [] }
should be invalid: { success: true, errors: [] }

🎉 thanks @samchon!
I wanted to point out that this test will never fail:
https://github.com/samchon/typescript-json/pull/227/files#diff-c52ef86833d1f670e4fe94a60b94a79c294cdf3c206e3d9b182cad97cb8dba2dR42


Cumsum treats null values as zeros

Bug description
Fix #26429 broke our charting because it now treats null values as zeros for the sake of the cumulative sum function.  This causes an issue where future time periods that have yet to occur will have data and gaps in data are now being filled instead of showing as gaps.
When the data is null it should be reflected as null NOT zero.  If the user wants to fill in or interpolate here that should be a separate option like in other reporting platforms and Excel.  It is also easier for the user to insert a IfNull into their query than it is to replicate cumulative sum in a query, particularly if they need to show two different variables with two different rolling functions.

How to reproduce the bug
Create a line chart and use the cumulative sum function.
Screenshots/recordings
No response
Superset version
3.1.1
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist

[ ] I have searched Superset docs and Slack and didn't find a solution to my problem.
[ ] I have searched the GitHub issue tracker and didn't find a similar bug report.
[ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

@JohnDietrich-Pepper I see the issue.. When implementing this fix in #26429 , we didn't consider the case where values are expected to terminate early, only how to deal with interim values.
I wonder if there's some middle ground here? For instance, automatically interpolating zeros until the last defined value, and then leaving the rest null? This would ensure continuous series, but also make sure they terminate when expected. While I understand the problem described in this issue, the problem described in #21093 is IMO also quite problematic, and likely more common than this one..

@JohnDietrich-Pepper I see the issue.. When implementing this fix in #26429 , we didn't consider the case where values are expected to terminate early, only how to deal with interim values.
I wonder if there's some middle ground here? For instance, automatically interpolating zeros until the last defined value, and then leaving the rest null? This would ensure continuous series, but also make sure they terminate when expected. While I understand the problem described in this issue, the problem described in #21093 is IMO also quite problematic, and likely more common than this one..

That would probably work but I dispute the notion that #21093 is problematic.  The issue in #21093 can be solved in the query with a IFNULL and the solution is disingenuous to the end user because it implies data is in a particular X value when the reality is no data is present.  Consider a case of a sensor (for a car, weather, etc...) there is a big difference between the sensor returned no data and the sensor returned a zero value.  The solution takes the position that 0 and null are the same.
Real world example.  In my day job one of the data sets my data engineering team works with is sensor data that comes off commercial airline flights looking for anomalies in mechanical parts.  If we had implemented Superset we would have been in a world of hurt with this change because we need to track the cumulative sum of defects and also periods when the sensor is offline.  The original view is correct and what we have implemented in our reporting platform (Tableau)

@villebro Any updates?

@villebro That would probably work but I dispute the notion that #21093 is problematic. The issue in #21093 can be solved in the query with a IFNULL and the solution is disingenuous to the end user because it implies data is in a particular X value when the reality is no data is present. Consider a case of a sensor (for a car, weather, etc...) there is a big difference between the sensor returned no data and the sensor returned a zero value. The solution takes the position that 0 and null are the same.

Actually I'm not so sure using an IFNULL would work here. The whole reason why these gaps appear is because the particular combination of grouping keys doesn't exist. Adding an IFNULL(0) would still leave a NULL value due to the pivot operation. Note, that there has been talk of doing away with the pivot operation for these charts, and that would likely make it easier to offer richer customization options. However, this requires very heavy redesigning of the charting system, and will likely not happen any time soon.

Real world example. In my day job one of the data sets my data engineering team works with is sensor data that comes off commercial airline flights looking for anomalies in mechanical parts. If we had implemented Superset we would have been in a world of hurt with this change because we need to track the cumulative sum of defects and also periods when the sensor is offline. The original view is correct and what we have implemented in our reporting platform (Tableau)

While I understand your need for terminating the cumulative graph, I'm not convinced the common expectation is to see gaps in a cumulative graph where values are missing. I fired a quick "cumulative graph" in Google, and picked the first hit:

source: https://blogs.sas.com/content/iml/2020/03/25/read-cumulative-frequency-graph.html
I feel this is a very typical cumulative distribution chart, and leaving a gap in it would IMO not be the expected result. Or maybe I'm misinterpreting what you're saying.
Having said all this, I would still like to see if we can somehow achieve what you're after. Would you be able to share some redacted screenshots of the Tableau chart you mentioned so I can understand how the expected chart should look?

I will close this, but @JohnDietrich-Pepper please feel free to reopen the issue if you disagree with my latest comment.


Weird error message when installling.

Platform: Ubuntu 16.04, Windows Linux Subsystem
I got the following error message when downloading the training data:
alex@AlexanderPC:/mnt/c/Users/Alexander$ mhcflurry-downloads fetch
Using Theano backend.
Traceback (most recent call last):
  File "/home/alex/anaconda3/bin/mhcflurry-downloads", line 7, in <module>
    from mhcflurry.downloads_command import run
  File "/home/alex/anaconda3/lib/python3.5/site-packages/mhcflurry/__init__.py", line 15, in <module>
    from .class1_allele_specific.class1_binding_predictor import (
  File "/home/alex/anaconda3/lib/python3.5/site-packages/mhcflurry/class1_allele_specific/__init__.py", line 3, in <module>
    from .class1_binding_predictor import Class1BindingPredictor
  File "/home/alex/anaconda3/lib/python3.5/site-packages/mhcflurry/class1_allele_specific/class1_binding_predictor.py", line 32, in <module>
    from .class1_allele_specific_kmer_ic50_predictor_base import (
  File "/home/alex/anaconda3/lib/python3.5/site-packages/mhcflurry/class1_allele_specific/class1_allele_specific_kmer_ic50_predictor_base.py", line 31, in <module>
    from ..ic50_predictor_base import IC50PredictorBase
  File "/home/alex/anaconda3/lib/python3.5/site-packages/mhcflurry/ic50_predictor_base.py", line 24, in <module>
    from .dataset import Dataset
  File "/home/alex/anaconda3/lib/python3.5/site-packages/mhcflurry/dataset.py", line 32, in <module>
    from .imputation_helpers import (
  File "/home/alex/anaconda3/lib/python3.5/site-packages/mhcflurry/imputation_helpers.py", line 23, in <module>
    from fancyimpute.knn import KNN
  File "/home/alex/anaconda3/lib/python3.5/site-packages/fancyimpute/__init__.py", line 4, in <module>
    from .nuclear_norm_minimization import NuclearNormMinimization
  File "/home/alex/anaconda3/lib/python3.5/site-packages/fancyimpute/nuclear_norm_minimization.py", line 15, in <module>
    import cvxpy
  File "/home/alex/anaconda3/lib/python3.5/site-packages/cvxpy/__init__.py", line 21, in <module>
    from cvxpy.atoms import *
  File "/home/alex/anaconda3/lib/python3.5/site-packages/cvxpy/atoms/__init__.py", line 20, in <module>
    from cvxpy.atoms.affine_prod import affine_prod
  File "/home/alex/anaconda3/lib/python3.5/site-packages/cvxpy/atoms/affine_prod.py", line 20, in <module>
    from cvxpy.atoms.atom import Atom
  File "/home/alex/anaconda3/lib/python3.5/site-packages/cvxpy/atoms/atom.py", line 21, in <module>
    from .. import utilities as u
  File "/home/alex/anaconda3/lib/python3.5/site-packages/cvxpy/utilities/__init__.py", line 24, in <module>
    from .quadratic import QuadCoeffExtractor
  File "/home/alex/anaconda3/lib/python3.5/site-packages/cvxpy/utilities/quadratic.py", line 24, in <module>
    import canonInterface
  File "/home/alex/anaconda3/lib/python3.5/site-packages/canonInterface.py", line 16, in <module>
    import CVXcanon
  File "/home/alex/anaconda3/lib/python3.5/site-packages/CVXcanon.py", line 28, in <module>
    _CVXcanon = swig_import_helper()
  File "/home/alex/anaconda3/lib/python3.5/site-packages/CVXcanon.py", line 24, in swig_import_helper
    _mod = imp.load_module('_CVXcanon', fp, pathname, description)
  File "/home/alex/anaconda3/lib/python3.5/imp.py", line 242, in load_module
    return load_dynamic(name, filename, file)
  File "/home/alex/anaconda3/lib/python3.5/imp.py", line 342, in load_dynamic
    return _load(spec)
ImportError: /home/alex/anaconda3/lib/python3.5/site-packages/_CVXcanon.cpython-35m-x86_64-linux-gnu.so: undefined symbol: _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEED1Ev

I'm getting the exact same error message on native Ubuntu 16.10 as well:
alexander@alexander-HP-ENVY-m7-Notebook-PC:~$ mhcflurry-downloads fetch
Using TensorFlow backend.
I tensorflow/stream_executor/dso_loader.cc:128] successfully opened CUDA library libcublas.so locally
I tensorflow/stream_executor/dso_loader.cc:128] successfully opened CUDA library libcudnn.so locally
I tensorflow/stream_executor/dso_loader.cc:128] successfully opened CUDA library libcufft.so locally
I tensorflow/stream_executor/dso_loader.cc:128] successfully opened CUDA library libcuda.so.1 locally
I tensorflow/stream_executor/dso_loader.cc:128] successfully opened CUDA library libcurand.so locally
Traceback (most recent call last):
File "/home/alexander/anaconda3/bin/mhcflurry-downloads", line 7, in
from mhcflurry.downloads_command import run
File "/home/alexander/anaconda3/lib/python3.5/site-packages/mhcflurry/init.py", line 15, in
from .class1_allele_specific.class1_binding_predictor import (
File "/home/alexander/anaconda3/lib/python3.5/site-packages/mhcflurry/class1_allele_specific/init.py", line 3, in
from .class1_binding_predictor import Class1BindingPredictor
File "/home/alexander/anaconda3/lib/python3.5/site-packages/mhcflurry/class1_allele_specific/class1_binding_predictor.py", line 32, in
from .class1_allele_specific_kmer_ic50_predictor_base import (
File "/home/alexander/anaconda3/lib/python3.5/site-packages/mhcflurry/class1_allele_specific/class1_allele_specific_kmer_ic50_predictor_base.py", line 31, in
from ..ic50_predictor_base import IC50PredictorBase
File "/home/alexander/anaconda3/lib/python3.5/site-packages/mhcflurry/ic50_predictor_base.py", line 24, in
from .dataset import Dataset
File "/home/alexander/anaconda3/lib/python3.5/site-packages/mhcflurry/dataset.py", line 32, in
from .imputation_helpers import (
File "/home/alexander/anaconda3/lib/python3.5/site-packages/mhcflurry/imputation_helpers.py", line 23, in
from fancyimpute.knn import KNN
File "/home/alexander/anaconda3/lib/python3.5/site-packages/fancyimpute/init.py", line 4, in
from .nuclear_norm_minimization import NuclearNormMinimization
File "/home/alexander/anaconda3/lib/python3.5/site-packages/fancyimpute/nuclear_norm_minimization.py", line 15, in
import cvxpy
File "/home/alexander/anaconda3/lib/python3.5/site-packages/cvxpy/init.py", line 21, in
from cvxpy.atoms import *
File "/home/alexander/anaconda3/lib/python3.5/site-packages/cvxpy/atoms/init.py", line 20, in
from cvxpy.atoms.affine_prod import affine_prod
File "/home/alexander/anaconda3/lib/python3.5/site-packages/cvxpy/atoms/affine_prod.py", line 20, in
from cvxpy.atoms.atom import Atom
File "/home/alexander/anaconda3/lib/python3.5/site-packages/cvxpy/atoms/atom.py", line 21, in
from .. import utilities as u
File "/home/alexander/anaconda3/lib/python3.5/site-packages/cvxpy/utilities/init.py", line 24, in
from .quadratic import QuadCoeffExtractor
File "/home/alexander/anaconda3/lib/python3.5/site-packages/cvxpy/utilities/quadratic.py", line 24, in
import canonInterface
File "/home/alexander/anaconda3/lib/python3.5/site-packages/canonInterface.py", line 16, in
import CVXcanon
File "/home/alexander/anaconda3/lib/python3.5/site-packages/CVXcanon.py", line 28, in
_CVXcanon = swig_import_helper()
File "/home/alexander/anaconda3/lib/python3.5/site-packages/CVXcanon.py", line 24, in swig_import_helper
_mod = imp.load_module('_CVXcanon', fp, pathname, description)
File "/home/alexander/anaconda3/lib/python3.5/imp.py", line 242, in load_module
return load_dynamic(name, filename, file)
File "/home/alexander/anaconda3/lib/python3.5/imp.py", line 342, in load_dynamic
return _load(spec)
ImportError: /home/alexander/anaconda3/lib/python3.5/site-packages/_CVXcanon.cpython-35m-x86_64-linux-gnu.so: undefined symbol: _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEED1Ev

I fixed this problem by downloading cvxpy using conda instead of pip. I guess the pip installation breaks somewhere.

From googling around this seems to be a linking problem related to compiler
versions, but I'm really not sure what the fix would be.
One idea: try "pip install --upgrade --force-reinstall --ignore-installed
CVXcanon" to try reinstalling (and recompiling) the CVXcanon package.
If that doesn't work the maintainers of CVXcanon may have better ideas. If
you sort it out please let us know what the fix was.
On Sat, Feb 4, 2017 at 2:13 AM, alexanderwhatley<EMAIL_ADDRESS>wrote:

I'm getting the exact same error message on native Ubuntu 16.10 as well:
alexander@alexander-HP-ENVY-m7-Notebook-PC:~$ mhcflurry-downloads fetch
Using TensorFlow backend.
I tensorflow/stream_executor/dso_loader.cc:128] successfully opened CUDA
library libcublas.so locally
I tensorflow/stream_executor/dso_loader.cc:128] successfully opened CUDA
library libcudnn.so locally
I tensorflow/stream_executor/dso_loader.cc:128] successfully opened CUDA
library libcufft.so locally
I tensorflow/stream_executor/dso_loader.cc:128] successfully opened CUDA
library libcuda.so.1 locally
I tensorflow/stream_executor/dso_loader.cc:128] successfully opened CUDA
library libcurand.so locally
Traceback (most recent call last):
File "/home/alexander/anaconda3/bin/mhcflurry-downloads", line 7, in
from mhcflurry.downloads_command import run
File "/home/alexander/anaconda3/lib/python3.5/site-packages/mhcflurry/
init.py", line 15, in
from .class1_allele_specific.class1_binding_predictor import (
File "/home/alexander/anaconda3/lib/python3.5/site-packages/
mhcflurry/class1_allele_specific/init.py", line 3, in
from .class1_binding_predictor import Class1BindingPredictor
File "/home/alexander/anaconda3/lib/python3.5/site-packages/
mhcflurry/class1_allele_specific/class1_binding_predictor.py", line 32,
in
from .class1_allele_specific_kmer_ic50_predictor_base import (
File "/home/alexander/anaconda3/lib/python3.5/site-packages/
mhcflurry/class1_allele_specific/class1_allele_
specific_kmer_ic50_predictor_base.py", line 31, in
from ..ic50_predictor_base import IC50PredictorBase
File "/home/alexander/anaconda3/lib/python3.5/site-packages/
mhcflurry/ic50_predictor_base.py", line 24, in
from .dataset import Dataset
File "/home/alexander/anaconda3/lib/python3.5/site-packages/mhcflurry/dataset.py",
line 32, in
from .imputation_helpers import (
File "/home/alexander/anaconda3/lib/python3.5/site-packages/
mhcflurry/imputation_helpers.py", line 23, in
from fancyimpute.knn import KNN
File "/home/alexander/anaconda3/lib/python3.5/site-packages/fancyimpute/
init.py", line 4, in
from .nuclear_norm_minimization import NuclearNormMinimization
File "/home/alexander/anaconda3/lib/python3.5/site-packages/
fancyimpute/nuclear_norm_minimization.py", line 15, in
import cvxpy
File "/home/alexander/anaconda3/lib/python3.5/site-packages/cvxpy/init.py",
line 21, in
from cvxpy.atoms import *
File "/home/alexander/anaconda3/lib/python3.5/site-packages/cvxpy/atoms/
init.py", line 20, in
from cvxpy.atoms.affine_prod import affine_prod
File "/home/alexander/anaconda3/lib/python3.5/site-packages/cvxpy/atoms/affine_prod.py",
line 20, in
from cvxpy.atoms.atom import Atom
File "/home/alexander/anaconda3/lib/python3.5/site-packages/cvxpy/atoms/atom.py",
line 21, in
from .. import utilities as u
File "/home/alexander/anaconda3/lib/python3.5/site-packages/
cvxpy/utilities/init.py", line 24, in
from .quadratic import QuadCoeffExtractor
File "/home/alexander/anaconda3/lib/python3.5/site-packages/cvxpy/utilities/quadratic.py",
line 24, in
import canonInterface
File "/home/alexander/anaconda3/lib/python3.5/site-packages/canonInterface.py",
line 16, in
import CVXcanon
File "/home/alexander/anaconda3/lib/python3.5/site-packages/CVXcanon.py",
line 28, in
_CVXcanon = swig_import_helper()
File "/home/alexander/anaconda3/lib/python3.5/site-packages/CVXcanon.py",
line 24, in swig_import_helper
_mod = imp.load_module('_CVXcanon', fp, pathname, description)
File "/home/alexander/anaconda3/lib/python3.5/imp.py", line 242, in
load_module
return load_dynamic(name, filename, file)
File "/home/alexander/anaconda3/lib/python3.5/imp.py", line 342, in
load_dynamic
return _load(spec)
ImportError: /home/alexander/anaconda3/lib/python3.5/site-packages/_CVXca
non.cpython-35m-x86_64-linux-gnu.so: undefined symbol:
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEED1Ev
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hammerlab/mhcflurry/issues/77#issuecomment-277425087,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAcjuMhwHtz3dgO0niqxzTVtF6epnlfGks5rZCUjgaJpZM4L3EYu
.

Yeah, I fixed this by downloading cvxpy separately. Will close.

Great, thanks. I added a note to the README about this.


Should we switch to the integrated view in book & pg?

We now have https://prql-lang.org/book_integrated/ & https://prql-lang.org/playground_integrated/
I like the playground one (another TODO is to improve the formatting here)

The book one is decent; maybe too many headings with both "PRQL" and "PRQL Language Book" (but we could change that to just "Book"

If people agree, I'm happy to merge these *_integrated into the main version

I think the *_integrated is definitely better than the current state. +1.0 for merging.
I don't mind the mildly redundant "Book" in the heading followed by "PRQL Language Book" directly below. "Book" standing alone is a little cryptic, at least until you get into the PRQL ethos.
That "PRQL Language Book" row also contains other useful stuff: the Search field, print, link to github, themes, etc.

If people agree, I'm happy to merge these *_integrated into the main version

What do you mean with this? Aren't link in the website topbar already pointing to *_integrated?
I personally dislike the iframe for the book, because I cannot copy or link to subpages, as all pages have url https://prql-lang.org/book_integrated/
I don't mind it for the playground.

What do you mean with this? Aren't link in the website topbar already pointing to *_integrated?

Yes but not links from elsewhere; lots still have prql-lang.org/book

I personally dislike the iframe for the book, because I cannot copy or link to subpages, as all pages have url https://prql-lang.org/book_integrated/

Ah, I hadn't realized this; that is indeed much worse. Maybe we should revert that unless there's a way of getting that to work....

Ah, I hadn't realized this; that is indeed much worse. Maybe we should revert that unless there's a way of getting that to work....

I hadn't realized that either. In my mind, the lack of links into separate pages of the Book outweighs the benefits of having the unified site.


Update Mondoo Logo (Black Text)

Re-Update of Logo to use more visible black workmark.
Pre-submission checklist:
Please check each of these after submitting your pull request:

[x] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[x] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[x] Have you picked the single best (existing) category for your project?
[x] Does it follow the other guidelines from the new entries section?
[x] Have you added your SVG to hosted_logos and referenced it there?
[x] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[x] Does your project/product name match the text on the logo?
[x] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[x] ~30 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

Killing this and creating a clean PR without conflicts.


Added Supported Source button

Added a Supported Source button to the readme

Thanks for opening an issue. Although this is an interesting idea for a business, it's not something I'm willing to add to the project's README.

We're not taking any fees from it... literally just connecting people, and if the job looks interesting, I might respond to the lead myself.

One issue I see is that when you say "I" that's coming from an account named @SupportedSource and that GitHub profile doesn't have a name of a person.
I also feel the same as the people commenting here: https://github.com/sympy/sympy/pull/9754
Good luck with your idea.


invalid generated js for (a ?? {}) && ""

Describe the bug:
Compiles invalid JS
Config and Small code sample
Config:
{
  target: "node",
  preset: "high"
}

Code:
(a ?? {}) && ""

Expected behavior
Compiles to (a??{})&&''
Actual behavior
Compiles to a??{}&&'' which is invalid.

Fixed in 2.0 (Currently 2.0.0-alpha.2). The 2.0 version nows uses Babel's parser and generator and is more suited for modern JavaScript syntax.


Static extension points not rendering on plus stores

Please list the package(s) involved in the issue, and include the version you are using
 "dependencies": {
    "@shopify/app": "3.42.0",
    "@shopify/checkout-ui-extensions-react": "^0.24.0",
    "@shopify/cli": "3.42.0",
    "react": "^17.0.2"
  },

$ shopify version
> Current Shopify CLI version: 3.42.0

Describe the bug
When working in development mode, I have a static extension point and have the following structure in my index.jsx file:
// index.jsx
import { ComponentA } from "./components/ComponentA.jsx";

render("Checkout::DeliveryAddress::RenderBefore", () => (
   <ComponentA />
));

When I npm run build and npm run deploy my extension to multiple plus stores, there are no changes to the statically defined extension points
Steps to reproduce the behavior:

Define a static extension point within index.jsx
Include the extension point within shopify.ui.extension.toml (extension_points = [])
Deploy app to plus store(s) npm run build & npm run deploy
Increase the app extension version
Publish the app
Customise the draft checkout and include the published app within the GUI (not too sure if this step is required for static extension points but for extensions that include dynamic extensions the step is required)
Convert the draft checkout to live

Expected behavior
ComponentA should be statically rendered within Checkout::DeliveryAddress::RenderBefore

@jamesvidler Thanks for the above. Which version of the shopify app are you using?

@Jay-Plumb I was using the latest version at the time when I generated it 3.44.1. The version of the @shopify/checkout-ui-extensions-react I was using was "@shopify/checkout-ui-extensions-react": "^0.24.0".

Thanks @jamesvidler, that might explain the discrepancy. I don't have the bandwidth to confirm if the issue is resolved or not so will leave it to you to close out the issue

I don't think any of those console errors were related to your extension not rendering. It wasn't rendering previously because there was never any corresponding render() method being called with Checkout::Dynamic::Render.
You'll likely need to re-configure your extension within the checkout editor now that you've changed the support extension targets. It will still be installed at the Checkout::Dynamic::Render extension point, so you'll need to move it to Checkout::Contact::RenderAfter. Easiest way to do this is just re-add the extension in the checkout editor.

Orignally the code looked something like this, and still it didn't render anything
import React from 'react';
import {
  useExtensionApi,
  render,
  Banner,
  useTranslate,
} from '@shopify/checkout-ui-extensions-react';

render('Checkout::Dynamic::Render', () => <App />);

function App() {
  const {extensionPoint} = useExtensionApi();
  const translate = useTranslate();
  return (
    <Banner title="checkout-ui-extension">
      {translate('welcome', {extensionPoint})}
    </Banner>
  );
}

I reconfigured but nothing changed.
Also, is it normal for a console.log in the index.jsx file to not appear in the console? Because mine didn't.

Hi @itse4elhaam, glad to see you got your initial issue resolved.

I'm creating a new page in the app which will have a form, the form will have give me the text (on submit) which i want to render in Checkout UI extension

I'm assuming that the merchant is entering this text with the admin and you want to use that in your extension? If that's the case, there are generally two ways to do this:

Using an app page within the admin, save the value to a metafield which can be read by the checkout ui extension.
Use settings for the checkout ui extensions, these are fields you can set up which show within the checkout editor when the merchant is configuring the extension.

Can I create something like an API endpoint and call it from the extension. How is this possible?

If you are using metafields or ui extension settings, then you shouldn't need to make a call to an API endpoint. In fact, metafields and settings are designed to remove the need for any network calls. That being said, you can always call an API endpoint using fetch() to get dynamic data.

If you've deployed the extension with that configuration, it should show the fields for it when you add the extension to your checkout within the editor.
If that's still not working, could you share your entire configuration file?

Here you go
type = "checkout_ui_extension"
name = "contactInfo"

extension_points = [
  'Checkout::Dynamic::Render',
]

# [[metafields]]
# namespace = "my-namespace"
# key = "my-key"

# [[metafields]]
# namespace = "my-namespace"
# key = "my-key-2"

# Read more on extension settings at https://shopify.dev/api/checkout-extensions/checkout/configuration
# [settings]
#   [[settings.fields]]
#   key = "banner_title"
#   type = "single_line_text_field"
#   name = "Banner title"
#   description = "Enter a title for the banner"

[extensions.settings]
[[extensions.settings.fields]]
key = "checkout_phone_number"
type = "single_line_text_field"
name = "phonenumber_value"
description = "Enter your desired number."
[[extensions.settings.fields.validations]]
name = "min"
value = "5"
[[extensions.settings.fields.validations]]
name = "max"
value = "20"


FEATURE: Add support for mxbai-embed-xsmall-v1 embedding model

Add mxbai-embed-xsmall-v1 as an embedding model.

As we talked in Meta, this needs migrations to address indexes and an unique ID.
It will be addressed by configurable embedding soon, so let's wait on that.


kong 0.9.9  Seems to have upsteam's cache, keep reporting connect () failed (111: Connection refused) while connecting to upstream

kong 0.9.9
Seems to have upsteam's cache, keep reporting connect () failed (111: Connection refused) while connecting to upstream。。
The upstream is found to be up-to-date, but the Kong request is the old upstream. Why is this happening?
After restarting Kong, it will recover, but this problem will occur again after some time.

Experts help me

I think on 0.9.9 you will need to migrate to one of the more modern Kong versions for proper support, lots has been fixed between those early releases and the soon to officially release 2.x Kong series now.

@jeremyjpj0916 emmm. history problem.can not upgrade.

@iver3on We will provide a command for automated APIs to Routes and Services migration and deprecate all the supports for pre 1.0 versions, see https://github.com/Kong/kong/pull/5176
I hope it might help, closing this for now.

@guanlan    The upstream is found to be up-to-date, but the Kong request is the old upstream. Why is this happening?
After restarting Kong, it will recover, but this problem will occur again after some time.

@guanlan Isn't this Kong cache issue a known issue? 1. * version has resolved it?


jade and coffee  compile issue

slide
    .image-slide(each='{url,index in imgList}')
            img.slider-item(src="{url}")
    script(type='text/coffeescript').
        @imgList = ['abc','bdc']

each in   will compile error

+1 I am having the same issue. I tried to run the todo.tag demo with jade and receive errors as well.

I compiled locally and got following:

riot.tag('slide', '

', function(opts) {

  this.imgList = ['abc', 'bdc'];

});

with following command:
var js = riot.compile(jade_source, { template: 'jade' })

Looks good to me. I bet there is something different on my environment.
How exactly are you compiling?

Closing this since it seems to be working. Please make a new issue if you find something. Thank you!


Adjust the Mesos task path util

Align the util with the latest Mesos API advancements as the "pod" task data changed which resulted in wrong paths. It also no longer necessary to iterate over the list of tasks as we already have all the bits to construct the paths.
Closes DCOS-10807

I ran a one-off DC/OS build with this PR and it works great, thanks @orlandohohmeier! 🚢

Looks good to me! I also share the same feeling with @rcorral , but I don't really think there is going to another type any time soon.
Thanks for addressing this so quickly! 💯 ✨

@rcorral @wavesoft I've introduced an executor type constant, hope that's what you guys had in mind.


mod_md does not renewal certificates since 05/2019

I have been using apache httpd (2.4.29) with md_module for more than 1 year without problem, everything was working fine (renewals certs too), but now (since may 2019) I have a problem with renewals certs.
Till now:
[md:notice] [pid 856:tid 1324] AH10051: testserver.company.com: has been renewed successfully and should be activated at Mon, xx xx 2019 12:15:04 GMT (this requires a server restart latest in 23:00:06 hours)
[md:notice] [pid 856:tid 1324] AH10059: The Managed Domain testserver.company.com has been setup and changes will be activated on next (graceful) server restart.
But now:
[md:error] [pid 6980:tid 512] (70007)The timeout specified has expired: AH10056: processing testserver.company.com
5 times in a row after 1 min
... and follow:
(70013)Missing parameter for the specified command line option: acme problem urn:acme:error:rateLimited: Error creating new cert :: too many certificates already issued for exact set of domains: testserver.company.com: see https://letsencrypt.org/docs/rate-limits/
I haven't changed anything in httpd.conf. Could you please give me advice, what is wrong? Thanks a lot!

My reply here: https://www.apachelounge.com/viewtopic.php?p=38303#38303
I am using mod_md with Apache 2.4.39 with success. The latest scheduled renewal with Apache VC9 x86 (OpenSSL 1.0.2) happened to be on July 3rd. And I just tested the same with Apache 2.4.39 VC15 x64 + OpenSSL 1.1.1: renewal OK as well.

Yes, I can confirm that when I tried to run 2.4.39 version apache with included version of mod_md, renewals are OK. So I have to migrate to new version of apache with newer version mod_md...
Thanks @Jan-E

OK. Please close this issue.


Add more callysto admin users

Requested via slack

Requested via slack

Do you have a reference/link? I guess I missed that request... or maybe lives in a dedicated slack I am not part of...

It was requested though a private slack message. I provided more info about the<EMAIL_ADDRESS>in response to it though.

Thanks for the additional info, @GeorgianaElena


Now you can view the illustrations in non-preview mode

Should modify docker image ->>> image: godmountain/pppixiv:latest to image: godmountain/pppixiv:v0.0.1


Remove python version restriction

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

LGTM. Is this ready to be merged?

Ha, just as the build finished.  Yep!

I was waiting for it! ;-)
El 27/11/17 a las 17:16, Steven Silvester escribió:

Ha, just as the build finished. Yep!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/conda-forge/winpty-feedstock/pull/8#issuecomment-347347210,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAWS7TMzY3yqlDu1qJrO5r9BpoKClzZgks5s6zTIgaJpZM4QsGSh.


StdErr from ShellExec, Did not find path entry

We have written the needed data into your clipboard because it was too large to send. Please paste.

Thanks for the bug report, but unfortunately we need some more information from you in order to triage this issue appropriately. Please edit your opening comment by providing a filled-in copy of our issue template. Once you are done please leave a comment to that effect.


What does the Coefficient of Performance attribute of HHP's display

The screenshot below show that for the space heating part of the HHP the coefficient of performance is 2.72 in present an 2.17 in the future.

What does this attribute mean?
How is it calculated? My guess was input share/ambient heat. However 63.2/18.01=3.5

In this case, ETEngine calculates COP as 1 / (1 - share_of_ambient_heat). I don't think it makes any sense in the context of the HHP:
https://github.com/quintel/etengine/blob/1447a70a9774c5cc04e6307fb05e0674137746a6/app/models/qernel/converter_api/capacity_production.rb#L55-L60

n this case, ETEngine calculates COP as 1 / (1 - share_of_ambient_heat). I don't think it makes any sense in the context of the HHP:

This is the definition:
COP = input_of_electricity / output_of_heat

but that is only valid at times when the heat pump is working.
BTW: The above simplifies as follows:
COP = output_of_heat / input_of_electricity
    = (input_of_electricity + input_of_ambient_heat) / input_of_electricity
    = 1 / (1 - input_of_ambient_heat)

when you set input_of_electricity + input_of_ambient_heat = 1.

This is the definition: [...]

What I mean is that ETE does not respect that the HHP has more than two carriers as inputs; this has always been the case. The COP calculation makes sense if the gas and electric components were separate nodes (as on normal electric heat pumps), but not when the HHP is modelled as a single node.
For what it's worth, there isn't a single reference to the coefficient_of_performance attribute in ETSource.

For what it's worth, there isn't a single reference to the coefficient_of_performance attribute in ETSource.

I think this average COP when the electric part of the HHP is working is an interesting value to display. Especially when the threshold is set in a scenario.
The following equation also holds and will for HHP give the average COP for the HP-part:
COP = (input_of_electricity + input_ambient) / input_of_electricity

Because:
HHP:
output.useable_heat.ambient_heat = 1
output.useable_heat.electricity = 1
electric and ground HP:
output.useable_heat = 1.0

On the other hand like @antw says:

For what it's worth, there isn't a single reference to the coefficient_of_performance attribute in ETSource.

So we can also not change the equation. In that case I would propose not to display Coefficient of performance in the converter summary of HHP's.

For what it's worth, there isn't a single reference to the coefficient_of_performance attribute in ETSource.

closing as no priority at all


Hybracter v0.11.0 - Error during LRGE step (Too few reads)

Hi @gbouras13 ,
We encountered an error while running Hybracter v0.11.0 with this command:
hybracter long-single -l 02_fastq/BA00000001.fastq.gz -s BA00000001 -c 1900000 -o 03_assembly/03.1_hybracter/BA00000001 -t 64 --subsample_depth 120 --min_depth 100 --medakaModel r1041_e82_400bps_bacterial_methylation --medaka_override
However, we encountered an error during the lrge step:
[2024-12-04T23:43:21Z INFO  lrge] Running two-set strategy with 10000 target reads and 5000 query reads
Error: Failed to generate estimate

Caused by:
    Too few reads requested: Number of reads in FASTQ file (1) is <= query number of reads (5000)
[Thu Dec  5 07:43:21 2024]
Error in rule lrge:
    jobid: 4
    input: 02_fastq/BA00000001.fastq.gz
    output: 03_assembly/03.1_hybracter/BA00000001/processing/chrom_size/BA00000001_lrge_estimated_chromosome_size.txt
    log: 03_assembly/03.1_hybracter/BA00000001/stderr/lrge/BA00000001.log (check log file(s) for error details)
    conda-env: /home/gilmansiu3/miniforge3/envs/hybracter-v0.11.0/lib/python3.12/site-packages/hybracter/workflow/conda/024e350392d5612938570ada6f9b3299_
    shell:

        if [[ 02_fastq/BA00000001.fastq.gz =~ \.gz$ ]]; then
        INPUT_CMD="zcat 02_fastq/BA00000001.fastq.gz"
        else
        INPUT_CMD="cat 02_fastq/BA00000001.fastq.gz"
        fi

        # Now run the awk command on the decompressed file
        if $INPUT_CMD | awk '{if (NR % 4 == 1) count++} END {exit count > 10000 ? 0 : 1}'; then
            # There are more than 10,000 reads, run lrge with defaults
            lrge -t 8 -s 42 02_fastq/BA00000001.fastq.gz -o 03_assembly/03.1_hybracter/BA00000001/processing/chrom_size/BA00000001_lrge_estimated_chromosome_size.txt
        else
            # There are less than 10,000 reads, use the all-vs-all strategy with all available reads
            lrge -t 8 -s 42 -n 10000 02_fastq/BA00000001.fastq.gz -o 03_assembly/03.1_hybracter/BA00000001/processing/chrom_size/BA00000001_lrge_estimated_chromosome_size.txt
        fi

        (one of the commands exited with non-zero exit code; note that snakemake uses bash strict mode!)
Logfile 03_assembly/03.1_hybracter/BA00000001/stderr/lrge/BA00000001.log not found.

Removing output files of failed job lrge since they might be corrupted:
03_assembly/03.1_hybracter/BA00000001/processing/chrom_size/BA00000001_lrge_estimated_chromosome_size.txt
Shutting down, this might take some time.
Exiting because a job execution failed. Look above for error message
Complete log: .snakemake/log/2024-12-05T074308.272662.snakemake.log
WorkflowError:
At least one job did not complete successfully.
[2024:12:05 07:43:21] ERROR: Snakemake failed

We have also attached the log file for your reference:
hybracter.log
This sample processed successfully in v0.10.1, suggesting the input file is valid. Could you help us resolve this issue?
Thank you very much!
Best regards,
Eddie

Hi @llk578496 - apologies for this, the v0.11.0 clearly has some bugs.
Do you know how many reads the input FASTQ has (clearly not 1!)? And would you be able to share the FASTQ (or a subset of it if it also breaks hybracter) with me and/or @mbhall88 so we can reproduce the error<EMAIL_ADDRESS>is my email too.
George

Yes if you could somehow share the FASTQ file so we can debug this it would be most appreciated

Hi @gbouras13 and @mbhall88 ,
Here are the statistics for the FASTQ file:
BA00000001.stats.txt
I've also shared the FASTQ file with George's email.
Thank you very much!
Best regards,
Eddie

Dear George and Michael,
Attached is the OneDrive link for the FASTQ file.
[https://res.cdn.office.net/assets/mail/file-icon/png/folder_16x16.png]#110https://connectpolyu-my.sharepoint.com/:f:/g/personal/20113427r_connect_polyu_hk/ElzNkuE5wDlGg0sRxtqb5qYBcfwUDgyzHzZXVOOSMuzxdg?e=eVXdEX
Thank you very much!
Best regards,
Lee Lam Kwong Eddie

From: Michael Hall @.>
Sent: Thursday, December 5, 2024 10:01 AM
To: gbouras13/hybracter @.>
Cc: LEE, LAMKWONGEDDIE [Student] @.>; Mention @.>
Subject: Re: [gbouras13/hybracter] Hybracter v0.11.0 - Error during LRGE step (Too few reads) (Issue #110)
CAUTION: This email is not originated from PolyU. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Yes if you could somehow share the FASTQ file so we can debug this it would be most appreciated
—
Reply to this email directly, view it on GitHubhttps://github.com/gbouras13/hybracter/issues/110#issuecomment-2518923095, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASXQ3WZGGYV24L3EFXQOO532D6XZLAVCNFSM6AAAAABTBJI4KGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJYHEZDGMBZGU.
You are receiving this because you were mentioned.Message ID: @.***>
[https://www.polyu.edu.hk/emaildisclaimer/PolyU_Email_Signature-v2.jpg]
Disclaimer:
This message (including any attachments) contains confidential information intended for a specific individual and purpose. If you are not the intended recipient, you should delete this message and notify the sender and The Hong Kong Polytechnic University (the University) immediately. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited and may be unlawful.
The University specifically denies any responsibility for the accuracy or quality of information obtained through University E-mail Facilities. Any views and opinions expressed are only those of the author(s) and do not necessarily represent those of the University and the University accepts no liability whatsoever for any losses or damages incurred or caused to any party as a result of the use of such information.

Hi @llk578496 ,
If you urgently need to run this, I believe the error is to do with the way lrge parsed the compression of the FASTQ file.
Therefore, try unzipping and gzipping the file - this worked for me
e.g.
gunzip BA00000001.fastq.gz
gzip BA00000001.fastq
lrge BA00000001.fastq.gz
[2024-12-05T05:16:51Z INFO  lrge] Running two-set strategy with 10000 target reads and 5000 query reads
[2024-12-05T05:17:37Z WARN  liblrge::twoset] 338 (6.76%) query read(s) did not overlap any target reads
[2024-12-05T05:17:37Z INFO  lrge] Estimated genome size: 1.95 Mbp (IQR: 1.58 Mbp - 2.10 Mbp)
1950278
[2024-12-05T05:17:37Z INFO  lrge] Done!

Michael has identified the error and will work on a fix, so if it isn't urgent, feel free to wait. Thank you so much for picking up the error.
George

Hi @gbouras13 and @mbhall88,
Thank you for your help! The file compression fix worked successfully. We'll wait for the new update.
Best regards,
Eddie

I have fixed lrge in v0.1.3 which is now up on conda. So if you remove the lrge conda env that hybracter created and rerun, it should use that latest version.
thank you very much for reporting the bug

Closing this issue now as lrge seems to have solved the issue


Dependency build problem

Hi Meisterschueler, I have a similar problem trying to build the 2 jar files. Running Maven install on them yields the following error:
I'm new to Maven builds, so I might miss something. Any help would be appreciated.
Thanks
[ERROR] Failed to execute goal on project ogn-client-java: Could not resolve dependencies for project org.ogn:ogn-client-java:jar:1.1.0-SNAPSHOT: Failed to collect dependencies at org.ogn:ogn-commons-java:jar:[,2.0.0): No versions available for org.ogn:ogn-commons-java:jar:[,2.0.0) within specified range -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project ogn-client-java: Could not resolve dependencies for project org.ogn:ogn-client-java:jar:1.1.0-SNAPSHOT: Failed to collect dependencies at org.ogn:ogn-commons-java:jar:[,2.0.0)
Originally posted by @Gosa7777 in https://github.com/Meisterschueler/ogn-viewer-android/issues/12#issuecomment-746678779

Hi @Gosa7777 ,
Please read the "Dependencies" paragraph in the readme file of this project.

The app uses two repositories from Meisterschueler:
https://github.com/Meisterschueler/ogn-commons-java
and
https://github.com/Meisterschueler/ogn-client-java
Clone the Java7 files from "Android" branch!
You need Eclipse and Maven to build the jar files.
Use "maven install" to build them.

Please let us know if your problem is solved!
We will then close this issue.

Hi Dominik,
That is what I‘ve done: downloaded the packages from github and ran mvn install -e on it.
It fails with the messages I put into the issue.
Not sure if it is a connection problem to ogn.org or some bad config.
I can ping the ogn.org address ok.
Any help is greatly appreciated.
Kudos for the work on the ogn project!
Thanks
Claude

On 18 Dec 2020, at 09:02, Dominik Prikril<EMAIL_ADDRESS>wrote:

Hi @Gosa7777 ,
Please read the "Dependencies" paragraph in the readme file of this project.
The app uses two repositories from Meisterschueler:
https://github.com/Meisterschueler/ogn-commons-java
and
https://github.com/Meisterschueler/ogn-client-java
Clone the Java7 files from "Android" branch!
You need Eclipse and Maven to build the jar files.
Use "maven install" to build them.
Please let us know if your problem is solved!
We will then close this issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hi, @Gosa7777
please check that you don't use the "master" branches.
The error message from your first post can only appear if you are on the wrong branch.
You must use the the "android" branches of both repositories.
FYI: Maven does not connect to ogn.org but just to GitHub
org.ogn is just the namespace
You will find org/ogn/ogn-commons-java/2.0.0-SNAPSHOT in your local maven directory (.m2) after successful mvn install.

Thanks Prikril,
missed that line about the android branches, sorry about that: RTFM, I know...
I've got another error though on both packages:
[ERROR] Failed to execute goal on project ogn-client-java: Could not resolve dependencies for project org.ogn:ogn-client-java:jar:2.0.0-SNAPSHOT: Failed to collect dependencies at com.fasterxml.jackson.core:jackson-databind:jar:2.9.1:

The version should be available:
https://mvnrepository.com/artifact/com.fasterxml.jackson.core/jackson-databind/2.9.1
Did you get any download errors?
Please try to set the <optional>true</optional> to false or remove the line.
I cannot reproduce the error because the dependency is cached on my main system and I don't want to remove it.
Maybe I can test the process on another computer the next days....

Yes, I get this
Caused by: org.apache.maven.wagon.TransferFailedException: Transfer failed for https://repo.maven.apache.org/maven2/com/fasterxml/jackson/core/jackson-databind/2.9.1/jackson-databind-2.9.1.pom
It might be a firewall issue, I can't ping https://repo.maven.apache.org or https://mvnrepository.com from a prompt although I can access it through a browser.

So, I guess you can open https://repo.maven.apache.org/maven2/com/fasterxml/jackson/core/jackson-databind/2.9.1/jackson-databind-2.9.1.pom in your browser?
I can ping repo.maven.apache.org and mvrepository.com
Did you try it like this (without https)?
ping repo.maven.apache.org
ping mvnrepository.com
This just checks if your DNS resolution is working
Your firewall must allow the maven and java process to access your internet connection.

Pings works like that.
I've used Maven through Android Studio, no proxies configured

you can close the issue, I was able to build the jar files on a non-firewalled PC

you can close the issue, I was able to build the jar files on a non-firewalled PC

Thanks for your feedback!

Thanks for your feedback!

Unfortunately, I have a new problem:
The App crashes soon after starting with the following:
     Caused by: java.lang.ClassNotFoundException: Didn't find class "org.slf4j.LoggerFactory" on path: DexPathList[[zip file "/data/app/com.meisterschueler.ognviewer-2/base.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]
Any suggestions?
On Friday, January 22, 2021, 04:24:35 PM GMT+1, Dominik Prikril<EMAIL_ADDRESS>wrote:
Thanks for your feedback!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Unfortunately, I have a new problem:
The App crashes soon after starting with the following:
     Caused by: java.lang.ClassNotFoundException: Didn't find class "org.slf4j.LoggerFactory" on path: DexPathList[[zip file "/data/app/com.meisterschueler.ognviewer-2/base.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]
Any suggestions?
On Friday, January 22, 2021, 04:24:35 PM GMT+1, Dominik Prikril<EMAIL_ADDRESS>wrote:
Thanks for your feedback!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


AutoRest.ClientRuntime Install fails for UWP

Getting the error below trying to add the AutoRest.ClientRuntime v.2.3.4 package into a UWP app targeting Build 14393. I have been told dotnet rest runtime client is owned sdk-for-net project.  https://github.com/Azure/autorest/issues/1737#issuecomment-273825921
Restoring packages for C:\path\project.json...
System.Reflection.Emit.ILGeneration 4.0.1 provides a compile-time reference assembly for System.Reflection.Emit.ILGeneration on UAP,Version=v10.0, but there is no run-time assembly compatible with win10-arm-aot.
One or more packages are incompatible with UAP,Version=v10.0 (win10-arm-aot).
System.Reflection.Emit.ILGeneration 4.0.1 provides a compile-time reference assembly for System.Reflection.Emit.ILGeneration on UAP,Version=v10.0, but there is no run-time assembly compatible with win10-x64-aot.
One or more packages are incompatible with UAP,Version=v10.0 (win10-x64-aot).
System.Reflection.Emit.ILGeneration 4.0.1 provides a compile-time reference assembly for System.Reflection.Emit.ILGeneration on UAP,Version=v10.0, but there is no run-time assembly compatible with win10-x86-aot.
One or more packages are incompatible with UAP,Version=v10.0 (win10-x86-aot).
This looks related; https://github.com/StefH/System.Linq.Dynamic.Core/issues/33

This should be fixed in the latest runtime packages.

It is fixed! Thanks.


Faild to execute plugin in IDA 7.1

When running the plugin I get the following error:

Same problem in IDA 7.0

Same problem in 7.2

ok --- @confile @orzubek I figured it out.. if you are still wondering.

First, make sure you have LLVM toolset: https://releases.llvm.org/. Download and install.
Thenpip install clang to get the clang bindings for python.

Make sure you use the pip.exe located in c:\python27\Scripts or wherever you have python installed for IDA.
The author does point out that you need these to correctly work with plugin. The only thing that caught me off guard was the lack of errors showing the console. So to see what was going on I modified is Python init slightly to print the error since for some reason the import error was not giving me all these details.

@ax330d  you can probably close this.

Okay two steps are needed to fix that error:

Get python clang. That's easy open cmd.exe and run:
c:\python27\Scripts\pip.exe install clang
Get that libclang.dll and copy it into c:\Program Files\IDA 7.3
Take care for ida64.exe requires a 64-bit version while ida.exe needs a 32-bit version.
Use Everything or some other search tool - maybe it's already somewhere hidden on your harddisk.
Else well there is llvm but it's f**king big. So llvm 11 installation is 1,5 GB. but all you need from it is that libclang.dll that is just 70MB. So don't install it instead open LLVM-11.0.0-win64.exe in 7-Zip. Go to /bin and extract
libclang.dll to the IDA folder. And you are done.
To elaborated that 32-bit vs 64-bit thing. Extract 32-bit version to C:\Windows\SysWOW64 and 64-bit version to C:\Windows\System32.

Use an old version like https://releases.llvm.org/download.html#3.7.0. Smaller and works as well.
To get over that  "Please ensure that your python bindings are compatible with your libclang.so version." Error
Open  C:\python27-x64\lib\site-packages\clang\cindex.py
search for 'compatibility_check' and chance
compatibility_check = True to compatibility_check = False
and ya done.
Well since there is no doc so far - there is some config file:
c:\Program Files\IDA 7.3\plugins\hrdev_plugin\data\config.ini
The shortcut Alt-F5 is not well chosen - it is very close to Alt+F4 that will just close IDA. And also clashes with
Repeat_RTTI_command               bdescr       Alt-F5   of the standard plugins.cfg
I changed it to Alt+F6 by editing hrdev.py
Okay finally seeing hrdev in action I was a little disappointed. All that interactivity got lost. :(
Click on a function to open it doesn't work anymore. Rename stuff also got lost.
So what is the point of that plugin? A little bit sugar candy in syntax highlighting?
Copy and paste the actual function to your favorite editor will probably accomplish the same.
Despite the hex number all the time and highlighting probably exploitable string functions like strcpy it won't make it into my toolkit because it is just decreasing usability.


Option of nullable enum type failing to parse

Hi,
First, I want to really thank the author(s) for their wonderful work on this framework!
But, I have one small issue that is really annoying. I have an option of nullable enum type:
[Option("delayif", HelpText = "Sets the delay application trigger")]
public StartMode? DelayIF { get; set; }

StartMode is an enum. I want DelayIF property to be null if argument is not passed in command line.
I actually do NOT want to have a default value, but really have a null value.
When executing, calling myapp.exe --delayif none results with an error:
Option 'delayif' is defined with a bad format.

Removing the nullable type resolves the issue.
So, I'm using the workaround of adding a "NotSet" value in the Enum, and using it as a default in the options class, but this causes the help screen to show (Default: NotSet), which I do not want.
Would be really helpful if this bug could be addressed, thanks!

I believe this is a known issue. Might even be a PR that is submitted to address it. I’m currently a bit tied up so if you could look through older issues and PRs and make a reference to them here would be very helpful.
I’m actually targeting a new release sometime end of may

Would love to see a nullable enum working.

Can this be fixed please?

It's resolved in v2.6.0


Enhancement/UpdateChartsSnacks

What needs to be done
Change old snackbar to the new one in the charts page
What should it look like
N/A
Checklist

[ ] Charts page old snackbars removed
[ ] Charts page new snackbars added

This issue depends on #16 and should be implemented at the same time.


Updates for mne 0.13 + adjust dimension reduction in OCARTA

@jdammers , @dongqunxi , @pravsripad , @ebeich , @fboers
In mne_0.13 some functions are not longer available and must be
replaced:

raw.index_as_time(idx) —> raw.times[idx]
mne.time_frequency.compute_raw_psd —> mne.time_frequency.psd_welch
raw.drop_channels(…, copy=True) —> raw.copy().drop_channels()

In OCARTA some additional dimension reduction methods were added.
Before dimension reduction was always performed using 'explVar'. Now
one can choose between 'AIC', 'BIC', 'GAP', 'MDL', 'MIBS', 'explVar‘.
More information about these methods can be found in „Adaptive Blind
Signal and Image Processing“, Cichoki & Amari, 2002 (Jürgen has this
book)

Merging this, thanks @lukasbreuer .


Is there a safe was to get what's before the snippet?

I'm trying to get what's before the cursor before expanding the snippet. In this specific case I'm trying to get what's before the keyword. But I think the context before, trigger and after could be of interest.
This would allow to create context aware snippets. As an example check #238 for such an example (a lua function snippet which doesn't insert local when there is something before the cursor).
Currently I use this code but I'm not very happy with it:
function before(snippet)
	return snippet.env.TM_CURRENT_LINE:match('^(.*)' .. snippet.dscr[1], 1)
end

Regex matching is used
Can dscr be empty?
Can dscr contain more than one string?

Is there a better way to do this currently?
What do you think about adding a snippet.context?

You can just use snippet.trigger, it is updated with the actual string that triggered the snippet.
local before = snippet.env.TM_CURRENT_LINE:sub(1, -(#snippet.trigger+1))

should get you the line without the trigger.
dscr contains an optional description of the snippet, it just defaults to trig and may have multiple lines.

snippet.trigger sounds much better - will use that instead of dscr 👍
The sub however will only work if the snippet is triggered at the end of the line. Not if there is text after the trigger.
With match it should work unless the trigger is twice in the current line.

Ahhh true, hadn't considered that.
Making it completely foolproof would require getting the line up to the point where the snippet begins directly after expansion, but match should always work  :ok_hand:
I'll add a note on trig in DOC.md, I'm not sure it's mentioned anywhere (except this issue, now :D)

match wouldn't work for this line trigger trigger since it's unclear which trigger was expanded when using match.
But this case is probably neglectable 👍


Match more closely axum's API for MethodRouter

I have noticed some differences between aide's ApiMethodRouter and axum's MethodRouter which made composing services from several routers (created in different scopes) frustrating. AFAIK the changes I have made are all additive and non-breaking.  This is related to axum 0.6 release which made routers carry state in their types.

LGTM, thank you!