Show Installed Chart Source Location or Source Repository URL

Use case: Cluster Admin needs to determine where an installed chart came from purely from querying a running cluster.  i.e Which file location or chart repository or whatever each chart came from.  The given admin may or may not have access to the original chart yaml.
It appears that none of the helm commands are able to return this information, and that said information is probably not recorded in the first place.
It would be useful as an option to the helm list/ls command and the helm get command.
Output of helm version:
Client: &version.Version{SemVer:"v2.7.2", GitCommit:"8478fb4fc723885b155c924d1c8c410b7a9444e6", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.7.2", GitCommit:"8478fb4fc723885b155c924d1c8c410b7a9444e6", GitTreeState:"clean"}
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.6", GitCommit:"6260bb08c46c31eea6cb538b34a9ceb3e406689c", GitTreeState:"clean", BuildDate:"2017-12-21T06:34:11Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.0", GitCommit:"925c127ec6b946659ad0fd596fa959be43f0cc05", GitTreeState:"clean", BuildDate:"2017-12-15T20:55:30Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
AWS

helm get manifest and helm get values both provide information on the manifests submitted to tiller, but not the "origin" of the chart as that's stripped by the helm client.
For example:
><> helm get manifest $(helm last)

---
# Source: traefik/templates/configmap.yaml
apiVersion: v1
kind: ConfigMap
[...]
><> helm get values $(helm last)
{}

Will that work for you, or are you looking for a way to track the origin URL where the chart came from? Given helm's current architecture (helm client fetches the chart from the repo, loads from disk into memory, ships the manifest and supplied values to tiller via gRPC) I'm not sure this is something we can tackle, but feel free to hack on it if you like!

Yes, the origin repository URL (or path etc) is the desire.

get gives some info:
REVISION: 1
RELEASED: Mon Apr 30 08:38:39 2018
CHART: prometheus-operator-0.0.19
USER-SUPPLIED VALUES:
{}

COMPUTED VALUES:

A new meta date field would be needed....

Seems like probably adding to hapi/release/release.proto

+1 This would be very helpful!

Facing the same issue! Tried helm status, helm list, helm get.
Would love to contribute with some guidance. :)

It's really annoying . How is one supposed to know which repo the cart came from, if he hasn't installed it ?
And even for the charts I install I need to keep track where I installed it from . Let's take nginx-ingress for example. There are 5  charts named like that on kubeapps. If I dont know which one ws used exactly, it's a lot of guesswork to find the correct one.

1 Any movement on this?

Nobody from the community has looked into this. Please feel free to investigate the feasibility of this feature request.

cc #6464

+1 This would be really helpful, for now I keep a mapping in a wiki...

Has there been any decision in how this should be implemented? I think adding a label or annotation would be a good enough solution as that seems to be the standard for how Helm tracks resources.
I can implement this is we can agree on how we should store the repository URL.

I would like to see this feature, as it would enable version-checker to also check for Chart versions against upstream. Without this, it has no way of knowing what the latest upstream Chart version is.
I would like to see it added as a field to the Chart metadata, as ChartURL or some such. Blank if no chart repo was used.

(copying from https://github.com/helm/helm/issues/8976#issuecomment-721818055)
A Helm chart is not tied to any remote location. It is entirely possible to take a public chart and copy it into a local location as part of security practices. Some companies do that. Some companies have long kept local copies of packages (like debian and yum ones).
In fact, you can install a release from a chart in one location and upgrade the release from a chart in another location (e.g. a fork).
The sources is something you can find in the Chart.yaml file in a chart. It points to application and/or chart source code.
https://github.com/helm/helm/blob/d675b9c810e7fb4f198486d8dd082dcf35cb118d/pkg/chart/metadata.go#L34-L35
If the chart maintainer populates this field, it can be fetched with helm get manifest.

(copying from #8976 (comment))
A Helm chart is not tied to any remote location. It is entirely possible to take a public chart and copy it into a local location as part of security practices. Some companies do that. Some companies have long kept local copies of packages (like debian and yum ones).
In fact, you can install a release from a chart in one location and upgrade the release from a chart in another location (e.g. a fork).
The sources is something you can find in the Chart.yaml file in a chart. It points to application and/or chart source code.
https://github.com/helm/helm/blob/d675b9c810e7fb4f198486d8dd082dcf35cb118d/pkg/chart/metadata.go#L34-L35
If the chart maintainer populates this field, it can be fetched with helm show chart.

@bacongobbler I think this is the exact reason it is worthwhile to put the original repo in the release. So you can track from where it came from overtime, deteremine if a third party (or some random SRE) manually pushed changes or if it came from the desired repository. From an auditing perspective it would be greatly helpful IMO. Additionally, it'll help close the loop for auditors wanting to verify a helm chart came from an internal repository instead a remote one.
It would also have the added benefit of allowing things (i.e. pipelines, deploy tools, etc) to discover the proper repositories to use instead of passing around global based on the existing cluster.

This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs.

bump

I actually thought it was me and this couldn't be a problem. crazy.
I also have a suggestion: add some metadata field, which carries one of ...

helm://repo-url/a-chart
file://user@/my/file/system/path[?branch=xxx&remoteUrl=xxx]

so you know at a glance whether the chart came from a local file system, or an installed helm repo (and which one). in the first case you are probably able to deduct if it was your local CI/CD chain, came from a checked out company repo or a "rogue" colleague ;) . maybe add a git branch info if the file system path was managed by git.
the differentiator would just be helm install name REPO/CHART vs. helm install name /MY/FILE/PATH
this would be five-stars-perfect in my eyes :) . makes sense?

unstale please :)

unstale please, seems to me @flypenguin makes a very good suggestion.

I also have a suggestion: add some metadata field, which carries one of ...
* `helm://repo-url/a-chart[?version=a.b.c]`

* `file:///my/file/system/path[?branch=xxx&remoteUrl=yyy&user=zzz]`

I'd like to suggest some improvements on this.

Remove version.
It's already clear from the release metadata which chart version it is, so I see no need for including it in this field.

Using proper URI protocol
- helm://repo-url/a-chart
+ oci://repo-url/a-chart
+ # or
+ https://repo-url/a-chart

Specifying OCI or HTTPS (or HTTP?) may lead to different charts, so we better be specific about it since we know all the valid protocols.

Security considerations
I don't have a clear suggestion here, but I want to point out that there might be security concerns if we include the full file path here. Personally, it wouldn't matter to me if I reveal that I released my chart from file:///home/andreas/git/dev/my-chart. But for large organizations with high security standards, revealing the file structure may undesirable since it could help an attacker gain a foothold in a system somehow. Not a huge issue, most likely, but worth keeping in mind.

Remove version

True.
What came to me this morning was that you actually really might want to know which git commit hash has been pushed if you are talking about a local filesystem source, and if the state of that repo was dirty. Maybe you could configure policy systems on the cluster to reject certain deployments under certain conditions.

Using proper URI protocol

True.

Security considerations

@lindhe - if you have those standards in place I'd assume people would not allowed to perform mission critical helm installs from their laptops anyway ;) .
But basically any step in this direction would be a good step, does not need to be 120% maybe.

I've created PR #10369 which would populate the chart release metadata with:
"repoURL": "https://charts.fairwinds.com/stable"

and with OCI registries/repos would display like so (this example is hosted in ECR):
"repoURL": "oci://${ACCOUNT_NUMBER}.dkr.ecr.us-east-1.amazonaws.com/goldilocks"

Would love feedback on the code changes or implementation method. It's my first time contributing to helm, so there may be some edge cases I'm not aware of. My local testing was limited.

After chatting with @mattfarina in the above mentioned PR, I've created a HIP for this: https://github.com/helm/community/pull/224
Any feedback there would be appreciated! 😄

unstale please

unstale, please.

Please, add chart source to the helm ls output as well

I recommend that when helm does an installation, it saves the repo url in an annotation associated with the resources it installs.  Then it will be able to easily print out this data with the helm list -A command.  It could either be printed by default or with an extra argument to ask for a more detailed view. helm list -A --wide or something.

The PR is marked with the next release 3.12. This would be super helpful!

Think of that more as a goal. Whether it gets reviews and merged still depends on a core maintainer having the time. Nobody's paid to work on helm full-time, but as volunteers they're trying their best. :crossed_fingers:

You can get the repo details from an installed helm release by getting the secret for that release stored in your cluster:
1.- Get all helm related secrets from all namepsaces in your cluster with:
kubectl get secrets -A | grep -i helm
2.- Once you find the name of your secret , get the secret metadata with:
kubectl get secret SECRET_NAME -o json | jq .data.release \
  | tr -d '"' | base64 -d | base64 -d | gzip -d \
  | jq '.chart.metadata'

Now you can see all the information regarding the repository used to install the release.

@xeberth nope... that's not resolve issue with repoUrl...
For example, I installed nginx via that chart:
helm install akrugliak-nginx nginx-stable/nginx-ingress
And from cluster I can get only image metadata:
kubectl get secret sh.helm.release.v1.akrugliak-nginx.v1 -o json | jq .data.release \
  | tr -d '"' | base64 -d | base64 -d | gzip -d \
  | jq '.chart.metadata'
{
  "name": "nginx-ingress",
  "home": "https://github.com/nginxinc/kubernetes-ingress",
  "sources": [
    "https://github.com/nginxinc/kubernetes-ingress/tree/v3.3.1/deployments/helm-chart"
  ],
  "version": "1.0.1",
  "description": "NGINX Ingress Controller",
  "keywords": [
    "ingress",
    "nginx"
  ],
  "maintainers": [
    {
      "name": "nginxinc",
      "email"<EMAIL_ADDRESS>    }
  ],
  "icon": "https://raw.githubusercontent.com/nginxinc/kubernetes-ingress/v3.3.1/deployments/helm-chart/chart-icon.png",
  "apiVersion": "v2",
  "appVersion": "3.3.1",
  "kubeVersion": ">= 1.22.0-0",
  "type": "application"
}

Which repo I used? Nobody knows...
helm search repo nginx-ingress
NAME                                            CHART VERSION   APP VERSION                             DESCRIPTION
bitnami/nginx-ingress-controller                9.9.2           1.9.3                                   NGINX Ingress Controller is an Ingress controll...
nginx-ingress/nginx-ingress                     1.0.1           3.3.1                                   NGINX Ingress Controller
nginx-stable/nginx-ingress                      1.0.1           3.3.1                                   NGINX Ingress Controller
nginx-ingress/nginx-appprotect-dos-arbitrator   0.1.0           1.1.0                                   NGINX App Protect Dos arbitrator
nginx-ingress/nginx-devportal                   1.7.1           1.7.1                                   A Helm chart for deploying ACM Developer Portal
nginx-ingress/nginx-service-mesh                2.0.0                                                   NGINX Service Mesh
nginx-ingress/nms                               1.11.0          NIM 2.14.0|ACM 1.9.1|ADM 4.0.0-ea.3     A chart for installing the NGINX Management Suite
nginx-ingress/nms-acm                           1.9.1           1.9.1                                   A Helm chart for Kubernetes
nginx-ingress/nms-adm                           4.0.0           4.0.0                                   A Helm chart for ADM
nginx-ingress/nms-hybrid                        2.14.0          2.14.0                                  A Helm chart for Kubernetes

How we can accelerate approve of that PR?
https://github.com/helm/helm/pull/11378
More than year for adding one metadata field, really, guys? :(
How commynity can help with that?

+1

+1
Adding one more case scenario that this is needed:
rancher has several repositories, "rancher-latest" and "rancher-stable", and rancher-alpha
There is no way to know from which repo the chart comes from.
In Rancher docs as a workaround they give instructions to remove the old repo, basically "if you want to change versions, just keep1 repo at a time in your machine", but as i manage more than 1 cluster i do have both repos in my machine...

+1

+1
I need to downgrade a chart that was installed automatically by Rancher (fleet). Wasn't me.
I need to add the origin repo, to search chart versions and specify on helm command to upgrade

+1

+1

+10000


add PGP pub-key of anyway1021<EMAIL_ADDRESS>

+1, please go ahead add the key.

@anyway1021 please go ahead.


Slight refactoring of machine script generation.

Use embedded template instead of format string.
Add test.
Remove use of map pointer - golang maps are already pointers to a maps structure and can be nil.

Have you considered using github.com/sebdah/goldie for template tests, like in other places of this project? E.g.
https://github.com/iterative/terraform-provider-iterative/blob/142cd5b8b1aba9b0deb746b9fc5cfe3b6fecdd39/iterative/testdata/script_template_cloud_aws.golden#L1

Merging with AWS red because of capacity issues; works as expected.


Fixed VirtualViewport child key assignment

VirtualViewport children that lacked keys were all assigned the same null key.
Added an assert that verifies that all of the viewport's materialized children have unique keys.
Fixes https://github.com/flutter/flutter/issues/2830

LGTM

this really should have a test :-)

Yeah, although in some sense the assert is the test.  With just the assert added, lots of tests fail.

oh, that makes sense.


unrecognized option `-background transparent'

Try to run a converter from svg to png.
    command = convert(to: "#{file_name}.png") do
      set '-background transparent'
      image "#{file_name}.svg"
    end
    command.run

But get always error (no difference when i change order of 'image ...' and set '...')
convert: unrecognized option `-background transparent' @ error/convert.c/ConvertImageCommand/853.

When i run the output in the console or with method 'system' (f.e system command.to_s) it works fine.

@RobWu Everything you pass to set is escaped, including spaces, so you gotta separate your arguments. Either of the following will work:
# these 2 are equivalent
set :background, 'transparent'
set '-background', 'transparent'

@RobWu I noticed I still had a couple of outdated examples in the README, so I cleaned it up + added clarification about your case. https://github.com/maxim/skeptick#set

Cool, thanks


python310Packages.env-canada: 0.5.25 -> 0.5.26

Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 212146 run on x86_64-linux 1

2 packages built:

home-assistant-component-tests.environment_canada
python310Packages.env-canada

dependency failing on aarch64-linux

@ofborg build python310Packages.env-canada python310Packages.env-canada.passthru.tests


Android onboarding screen

The app is not really designed to be opened as standalone, it is rather part of an "intent" process (Share with...).

Design an onboarding to explain the concept and invite user to open webpage on desktop computer.

567bfbe236a120c1b6bebfa6f60e3cf2eae7cb35


Provide example for failing the webhook

There is no documented way to fail a webhook. Reading the code I found that exceptions are appropriate here, so added a small example to the README to make that explicit.

Hi,
Thanks for the contribution. I think better documentation around the approach would be that Griddler is itself simply a controller action. Therefore, any side effects that cause an error code other than a 200 in other Rails contexts would also apply to Griddler. What do you think?

Sure.


Testnet billing did not happen

For contract 16914, there was a delay of about 161 hours before the billing happened. Other contracts experienced some similar (though not as long) delays. Investigation showed the contract was not in grace period

Shouldn't that be addressed in 3.9?

@xmonader 3.9 should go live today so I don't know how it's feasible that this is fixed? I'm not really sure what happened and will take a closer look today.

Contract 14595

It also looks like the amount billed in total is correct but that it is maybe skipped every X cycles

We also found at that validator 2 was not running it's offchain worker, it might be related to a contract missing a billing slot

Yesterday we enabled the offchain worker on validator 02 again and the billing frequency has improved. I also found out that Rob's validator was not running an offchain worker, he will fix this now and thus the billing frequency should be normal again.

@coesensbert to solve this issue on testnet, please check if every validator runs an offchain worker, if not enable

Testnet validators updated


Reorganize clients

Reorganizes the client libraries by client. This is a prerequisite for enabling us to release clients independently.

[x] Move google-cloud-[x], grpc-google-cloud-[x]-[version], proto-google-cloud-x-[version] into google-cloud-clients/[x] subfolder with a parent artifact of google-cloud-[x]-parent.
[x] Update synth.py configurations
[x] Move google-cloud-contrib to root folder
[x] Move google-cloud-notification to google-cloud-contrib as it's a higher level client.
[x] Update Kokoro integration test config to look at correct paths
[x] Test that releasetool still updates all version poms for a single release

This is the version range you probably actually want to look at: https://github.com/googleapis/google-cloud-java/pull/5236/files/4c5ad02893582b9c1bf80d731dd8c69ffde19b2d..7d7925d7f4c3acdaf9428deffbe80b7c8795713d


Allow alt=""

This changes the required prop check to just check for undefined values, instead of falsy values, which allows passing alt="", or setting props to false.  I think the required prop check should just ensure that some value is provided.
This builds on top of https://github.com/RafidMuhymin/astro-imagetools/pull/71, because the tests won't pass until that change is made.  So, that should be merged first.

LGTM :+1: !


Running an empty cell should not put an empty cell into the interactive window

For #6839
As shown below, running a code cell containing just a cell marker from either the editor or the input box does not result in the cell being rendered in the interactive window.

Sorry @rchiodo, we discussed this a couple of weeks ago and I forgot to get it merged!


MathGame!!

PR Description 📜
New game: mathgame
Fixes #861

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for website preview in assets/images
[x] I have added entries for my game in main README.md
[x] I have added README.md in my folder
[ ] I have added working video of the game in README.md (optional)
[x] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @Venkat-Vivek ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

Hey @Venkat-Vivek !
you have to add some more features to the game and then you can continue with it for now it is too simple to have on GameZone !!

Thank you  @Venkat-Vivek , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


Dockerfile + build process + daemonset + README updates

Adds:

Updates to readme, showing some sample usage, sample build
Daemonset to build the pod
Dockerfile to build an image
Travis for lint & also to push docker

Some of these things aren't properly namespaced -- due to the CI side of things, and refer to kind of "doug & nfvpe" so, we need to move this to the NFVPE repo to fix those up. I created #7 to follow up on this. However, should work with the Daemonset as advertised in the readme, had a test through that.
Fixes #1
Fixes #6

Just an FYI that because of some wonkiness in how the secrets work, this will have to be merged, and then I'll update the secrets.


CME won't launch

Describe the bug
crackmapexec won't start.
downloaded the latest version via apt, for some reason its throwing the below error.
I'm running kali and its fully updated
Steps to reproduce the behavior:
normally attempt to run the tool
Screenshots
root@kali:~/Desktop/CTF# crackmapexec
Traceback (most recent call last):
  File "/usr/local/bin/crackmapexec", line 11, in <module>
    load_entry_point('crackmapexec==5.0.1.dev0', 'console_scripts', 'crackmapexec')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 489, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2852, in load_entry_point
    return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2443, in load
    return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2449, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/local/lib/python3.8/dist-packages/crackmapexec-5.0.1.dev0-py3.8.egg/cme/__init__.py", line 10, in <module>
    for module in os.listdir(thirdparty_modules):
FileNotFoundError: [Errno 2] No such file or directory: '/usr/local/lib/python3.8/dist-packages/crackmapexec-5.0.1.dev0-py3.8.egg/cme/thirdparty'

Crackmapexec info

OS: kali
Version of CME v5.0.1 dev

Additional context
Add any other context about the problem here.

Try using the lastest release https://github.com/byt3bl33d3r/CrackMapExec/releases

Closing since duplicate of #355


It looks like #883 was supposed to fix this, but we missed the part where we actually did the free’ing. :see_no_evil:
This is only WIP because I’m still trying to make a build so I can test that this fixes the whole problem.

(Also cc https://github.com/atom/atom/issues/10931.)

Yeah, I swore I commented on that exact line saying "These need to be freed" but I can't find it now. /shrug

Oh wow, good catch. Thanks!

That should take care of the problem, the intention of the system as it was before was to do exactly that. I just accidentally a line.

Verified this fixes the issue we were seeing in Atom :+1:

:+1: Thanks @joshaber


error of makefile

when running ./build_and_install_kernel.sh , it show that:
make distclean
make[1]:***Documentation/Kbuild: Is a directory.   Stop.
make: ***[Makefile: 1858: _clean_Documentation] Error 2

The problem seems similar to the one discussed here
Could you please check if you are using a case-insensitive file system?


Add dataset todo

Thanks, very nice idea! I suggest we convert your list into an issue, because then it is easier to cross-link and to tick things off!

Great! I will convert it as an issue.

Closing this since it is now an issue.


Investigate getting rid of PyTorch Lightning

Working on #321, I'm somewhat worried that the cause of the environment's finickiness is PyTorch Lightning and the dependencies it pulls in (torchmetrics, transformers(?!), HuggingFace hub).  It may be worth it to re-roll the trainer first-party to stop depending on them.
Key questions:

[ ]  Is this really the cause of the difficulties?
[ ] Can this be done without affecting performance?

I'm sure I can replicate (or really, improve on) the framework for training (mostly, the inclusion of optimizers and loss functions inside the model's class definition bothers me).

Not going to be looking at this right now.


How to import pallet-evm & pallet-ethereum with default-features disabled.

Question
I am trying to import pallet-evm & pallet-ethereum as below.
pallet-evm = { git = "https://github.com/polkadot-evm/frontier", default-features = false, branch = "polkadot-v1.11.0"}
pallet-ethereum = { git = "https://github.com/polkadot-evm/frontier", default-features = false, branch = "polkadot-v1.11.0"}

But it seems that even after setting default-features=false. It still pulls the underlying dependecies, example sp-io, frame-support etc. Which are already declared in my toml file with version v1.15.0.
I see in Cargo.lock that 2 names of packages exist, one of which is coming from here.
How to disable such flow?
Thanks.!

You'd better not mix the dependencies in your repo, whether using GitHub branches or crate versions. I suggest changing all of them to GitHub branches, as I have never tested the crate versions yet.

@boundless-forest Those are coming from Github branch of polkadot-sdk, not importing crates directly.

Would you be willing to share your code base? It's difficult to identify the issue based on the information provided above.

@boundless-forest
https://github.com/dhiway/cord is the substrate based chain for which I am building Ethereum capability.


[Bug] Numeric type audit in transaction and block structs and provider methods, remove gratuitous U256s

Component
consensus, eips, genesis
What version of Alloy are you on?
No response
Operating System
None
Describe the bug
Noticed discrepancy while implementing From<TypedTransaction> for TransactionRequest
all types should have the following (with options as necessary)
applies to
consensus
rpc
providers return values
etc
block_number: u64

transaction_index: u64

gas_price: u128

// make sure names are consistent here too. these are the same field
gas: u128
gas_limit: u128

max_fee_per_gas: u128

max_priority_fee_per_gas: u128

max_fee_per_blob_gas: u128

value: U256

closed by 454


chore: removing Druid from front- and back- end

SUMMARY

This is the first pass at the Druid specific conditionals.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

@AAfghahi I did a quick smoke test on the ephemeral and found that some dashboards are broken:

that's odd. Will look into it, thank you @eschutho

/testenv up

@AAfghahi the superset-ui/core should make 100% code coverage. the  #58 in processFilters.ts needs some test coverage. Oneline checks code coverage locally
$ npx jest --coverage --collectCoverageFrom='["packages/**/src/**/*.{js,ts}", "!packages/superset-ui-demo/**/*"]' packages

QA tested and verified. LGTM


Include all primary data in the cube

Need

As a user I want the scex feature to show me all (included) primary data

Approach

[ ] Update db query to include 'PRIMARY' and 'BOTH' for is_primary_data enum
[ ] when generating the integrated corpus, filter out any non primary data

DOD

[ ] corpus and cube contain all primary data stored in the data portal

Waiting until Q4 so that all of the cellxgene Data Resource is behind SOMA API.

@signechambers1 is this still needed?

@dsadgat ill close for now - not a priority.

Reopening as a priority so GE matches census


buoyboy.streamlit.app is broken

App appears to be down?

@binarymist working on my end. Sometimes streamlit will put apps in a sleep mode if there is a lack of activity. This project has taken the backseat of late. Wuld love to hear your thoughts though!

I waited several minutes yesterday for it, but it didn't seem to work. Seems to be up today though.

@binarymist I can add them for you! What are the buoys you want to see?

What are the buoys you want to see? That's part of the problem, I'm not yet sure which buoys exist for our neck of the woods.


Crashes, when parsing fails for image with is not a network image or something else

https://github.com/sur950/any_link_preview/blob/a47f45237905fd802979d3572ceb75c3dc9726d3/lib/src/helpers/link_preview.dart#L336
If the parsing for the image fails, then no error image is displayed.

Hi @mariomurrent-softwaresolutions,
This is fixed now and will be available from 3.0.1

Awesome thanks


3.1  Complete template mediterranean

[ ] download HydroATLAS
[ ] compare and harmonize with CCM
[ ] test integration with CCM


Scrollbar for Extensions tab

I've riced my shell to the point where the number of extensions surpasses the amount of screen space on my machine. You can neither scroll using a mouse, touchpad nor Down arrow/Page down.
The cutoff is clear when you compare the maximized and standard windows:

Another QOL feature related to Extensions tab I'd love to see in the next version is Escape button acting as the top left back button in the Install New and View Extension sections.

Added support for scrolling in Extensions page. The escape button and other shortcuts will be added too soon. Not just on the Extensions page but everywhere else.


Component, Service and Pipe generators don't comply with opinionated naming conventions

https://github.com/cmelion/generator-ng2-webpack/wiki/I-hate-that-all-the-files-are-named-index.ts,-style.scss-and-template.html

closing with 7e630419a25b7c54580f40ef4df0af5e2c928b81


Added 'state'/'physical-channel-status' columns to 'adapter list' output

coverage: 33.944%. first build when pulling cee2d45f134b898082fb16f14541d91dac1a6025 on andy/adapter-status into 0a99218b59b7cf4093209a2216bbe06ac8f7fe57 on master.


Documentation - Update Release Checklist Following JAN CPU

A number of amendments are required to the Release Checklist to allow for the process improvements made for the January CPU.

Raised in incorrect repo.


CRAM support

Hello,
Thanks for the software. I was able to successfully run this on a several BAM files, but I was wondering if there are plans to include support for CRAM format?
I receive the following error when trying to run a CRAM file and looks like a modification of bamUtils will be required:
Error in bamUtils::bam.cov.tile(bam, window = as.numeric(window), chunksize = 1e+06,  :
  Cannot open BAM. A valid BAM for 'bam.file' must be provided.
Calls: fragCounter -> PrepareCov -> <Anonymous>
In addition: Warning message:
In readChar(check_gz, 4) :
  text connection used with readChar(), results may be incorrect
Execution halted

Hi @ppararaj ,
Thank you for your interest in our tool. We don't currently have support for CRAM files and we don't have immediate plans to add this support (at least for now). What we do plan is to add an options for users to provide coverage counts from 3rd party tools and then just apply our GC and mappability correction (hoping to post updates here soon: #12 ). An (often superior) alternative to the coverage correction offered by fragCounter is using dryclean. Dryclean works well with uncorrected read depth counts.
There are many tools that offer fast coverage depth computations, for example: megadepth
If you are using fragCounter because you wish to use JaBbA, then you can use a tool of your choice for coverage depth calculation and supply that as input for JaBbA (with or without dryclean processing).

We're working with @mskilab on a meta-analysis of lymphomas. This is a show-stopper for us at the moment. Any thoughts on when this new functionality will become available?

Hi Ryan- I think cram support should be pretty easy to implement.   I think can have it by Monday?
Marcin

From: rdmorin @.***>
Sent: Thursday, July 8, 2021 11:53 AM
To: mskilab/fragCounter
Cc: Marcin Imielinski Laboratory; Mention
Subject: Re: [mskilab/fragCounter] CRAM support (#11)
We're working with @mskilabhttps://github.com/mskilab on a meta-analysis of lymphomas. This is a show-stopper for us at the moment. Any thoughts on when this new functionality will become available?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/mskilab/fragCounter/issues/11#issuecomment-876553060, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC73JEIZRCYNN4LLAIYSNB3TWXCWVANCNFSM477N3RIA.

That would be great. Thanks Marcin!

hi all - just added cram support and pushed to master --> please give it a spin and let us know!  You will need to reinstall mskilab/bamUtils as well.    Best-Marcin

Hello,
I've tested the new feature on a some GRCh37 CRAM files and it appear to work without issue. Thank you.

Great
On Sat, Jul 10, 2021 at 12:12 PM Prasath Pararajalingam <
@.***> wrote:

Hello,
I've tested the new feature on a some GRCh37 CRAM files and it appear to
work without issue. Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mskilab/fragCounter/issues/11#issuecomment-877662456,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC73JEOO5RCV4LGD5RG6VUDTXBWOPANCNFSM477N3RIA
.


Feature/certification page

📝 Summary

Why is this Pull Request necessary? Provide a concise explanation of the change or feature.
For example: "Fixes a bug", "Implements a new feature", or "Bumping package version".

📝 Summary
This Pull Request introduces the Certification Management feature. It implements several pages and functionalities: Create, Edit, Register, Detail, and List certifications. These additions allow users to manage certification details, register for courses, and view certification information, providing a streamlined experience for both users and admins in managing certifications.
📊 Impact

Scope: These changes apply primarily to the certification pages and components, including CertificationList, CertificationDetail, CertificationCreateForm, CertificationEditForm, and CertificationRegister. Each component and page has specific Vue and Vuex store integrations to handle user interactions, data validation, and persistence.

Affected parties: Only users interacting with certification features are impacted. Admins benefit from streamlined create and edit workflows, while general users can view and register for certifications.

Risk Assessment: Minimal risk, as these changes are contained within the certification feature and do not impact other parts of the system. The workflow is cohesive, starting from the CertificationList page (which links to individual CertificationDetail pages) and allowing authorized users to navigate to the CertificationCreate and CertificationEdit pages. Validation and state management are robustly handled, minimizing potential side effects.

✅ Testing

What testing have you done and verified? If you can't test, please say why that is.
If testing is not possible, explain why and how it will be handled later (manual verification, etc.).
**Manual Testing has been conducted. **

🔗 References

Supporting Information: Add relevant documentation, discussions, or background for this Pull Request.
This could include:

Links to issue trackers (e.g., GitHub issues)
API Documentation
External resources (StackOverflow, Notion pages, third-party package documentation)
The dayjs package has been added for time keeping which is a great alternative for moment.js. But this might be removed in the future if we do not require a library to handle the time aspect strictly on this project.
dayjs

The Certification Integration is depicted in the flow chart v1.0 here in the below image.

Here is the contract issue fixes.


docs: Add an example of a http server

Threw together a super simple http server example for fun. I'd like to extend it a bit more and add comments but I think this could make a decent example (though it is an example that requires some pretty hefty dependencies unfortunately).

An unfortunate side effect of f92534c is that gluon_vm now depends on gluon_check but there is unfortunately no way to avoid this without splitting out unification into a separate crate.

@brendanzab Any thoughts?
This might be better of somewhere also due to the dependencies it pulls in. Possibly it could be its own crate as I think it would be rather neat if we try_gluon used this implementation, I don't think it would take to much to implement what little that site needs. (Just thinking of doing it for dogfooding and not full fledged server).

r?


[WIP\proposal] use hparam plugin in tensorboard

I tried logging some of the hyperparameters used when training a model, along with the "usual" summaries that get written.
This enables a nice and cool feature in TensorBoard (yep, I'm always up for data analysis), that allows to have a quick comparison between models trained on the same dataset (hopefully) but with different hyperparameters.
This is only a proof-of-concept, and might not be so useful (well... it's not completely unuseful either, and it should only be polished prior to merging it), but it still has some potential. I'm currently using this to compare "big" changes in the overall parameters, but would like a lot to extend it to map also common parameters I tweak, such as resnet size, dropout value, fc_layer_sizes and so on.
I am currently fixed on the only measure of combined/epoch_loss, and I know that's suboptimal (there's a TODO exactly for that), and when present a combined/epoch_accuracy would be great too (but it hasn't been reimplemented yet).
Also, multiple measures can be added, cycling through all the various output features and tracking each epoch_loss as an output measure (along with epoch_accuracy when present, or mean_absolute_error, and so on... you get the reasoning).
This is the current result sample:

A detail shown when drilling down into the actual measures that resulted from that training

A graphical representation "cause-effect" like

Logging everything would clutter the interface (the menu on the left shows all the hyperparameters you have logged), and by design works by specifying the hyperparameter range (which is a think I don't want to do, that would force us in defining the hyperparameter range prior to training, as opposed to just logging and plotting the results).
I tought of everything I could in terms of having a way to automatically choose the best yaml parameters to track, but something that is very important to me might be absolutely of no use for someone else.
The only thing that could resolve this in my opinion is to have a yaml "flag" for each actual parameter that toggles hparam logging on\off, like below.
Do you have any ideas about this? Not being able to log\map\track the dropout of an input\output feature (for example) is a huge dealbreaker for me, since the parameters I "play" with the most during optimization are exactly those linked to the input features, and I also might want to just track some and not all of them.
Of course this would mean that you should track always the same parameter values, to be consistent in the output\analysis that would follow.
yaml sample:
input_features:
-
name: in
type: numerical
dropout: 0.2
hparam_logging: true
output_features:
-
name: out
type: numerical
preprocessing:
force_split: true
split_probabilities: [0.8, 0.2, 0.0]
training:
batch_size: 5
hparam_logging: true
learning_rate: 0.01
hparam_logging: true
epochs: 1000
early_stop: 1000
reduce_learning_rate_on_plateau: 100
reduce_learning_rate_on_plateau_patience: 5
hparam_logging: true
reduce_learning_rate_on_plateau_rate: 0.5
hparam_logging: true
learning_rate_warmup_epochs: 10

This is nice. You can achieve a similar visualization using hiplot in the visualization module, but having it integrated in the TensorBoard is cool too. let me thing of a way to make it more generic / compatible with the hyperopt we are doing now, but thanks for starting this!

There are many native modules in tensorboard, and some way cooler graphical visualizations, but they often apply to a specific task/data type (like a running spectrogram visualization with epochs on the time (depth) axis and accuracy per category/domain on the x,y axis)
I hoped you would be interested in implementing this specific one :)


DCJ-620: Add timing to TDR endpoints

Addresses
https://broadworkbench.atlassian.net/browse/DCJ-620
Summary
Add timing to interesting TDR specific endpoints to eventually track in https://grafana.dsp-devops.broadinstitute.org/d/8OxKprrSk/duos-dashboard?orgId=1

Have you read CONTRIBUTING.md lately? If not, do that first.

Label PR with a Jira ticket number and include a link to the ticket
Label PR with a security risk modifier [no, low, medium, high]
PR describes scope of changes
Get a minimum of one thumbs worth of review, preferably two if enough team members are available
Get PO sign-off for all non-trivial UI or workflow changes
Verify all tests go green
Test this change deployed correctly and works on dev environment after deployment

Thanks!
I know that Consent is not a Spring Boot project (if it were its REST endpoints would be instrumented for free) but just double-checking -- is there a way for timing to automatically be enabled for Consent's endpoints by default?

Not that I'm aware of. Dropwizard does do a ton of instrumentation for other things like database calls, but not for endpoints, unfortunately. There could be a way to hack the jersey annotations that DW uses, but I haven't tried looking into that.


chore: Skip building wheels

Codecov Report

Merging #39 into kite3 will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            kite3      #39   +/-   ##
=======================================
  Coverage   77.04%   77.04%
=======================================
  Files           3        3
  Lines         305      305
  Branches       36       36
=======================================
  Hits          235      235
  Misses         62       62
  Partials        8        8

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 b668125...f5df96d. Read the comment docs.


Fixes stack overflow recursive call.

Replaces the make request method overloads with a proper forwarding chain
that exposes all of the possible overloads for MakeRequest,
MakeRequestForStream, MakeRequestForHijackedResponse
Resolves: #170

@pauldotknopf - This should fix your issue. Want to give me a quick review?


Android badge number

Hi,
On my android app, the badge number is fixed to 3 each time receiving the push notification. Any idea? Thank.

I cannot get any badge number at all on my test device ( Asus zenfone 5Q with Android 9 ) .
Can someone help ?


Files missing in CocoaPods?

I just did a Pod Update and my build now gets the error:
/Users/gavin/montherly/Montherly/Pods/ALPValidator/ALPValidator/ALPValidator.h:31:9: 'UIView+ALPValidator.h' file not found
I checked the Pod file and noticed it in fact was not included (but did notice it in this repo) - was there a mistake with the cocoapod?

I take it back - this was a local CocoaPods bug.


Fixed ReactNative >= 0.59 compatibility

Looks like the reactNativeTransformer has been moved out of metro and into its own package called metro-react-native-babel-transformer in RN versions >= 0.59.
This small patch updates the require() to the correct path.

can anyone merge it?

Thank you! :heart:

Released in 1.2.12 :tada:


Creating image over non-rectangular grid

This is probably more of a help-wanted request than issue, but I wanted to visualize a large spectrogram. The spectrogram is plotted over a 2D non-rectangular grid (n_frequencies, n_timepoints) for a total of about 2 billion data points. For reference, here is my code (using matplotlib). I'm hoping to use datashader since my existing solution is very slow to render.
time, freq = np.meshgrid(timevec, freqvec)
# data is an array of shape (len(freqvec), len(timevec))
# whose values are the magnitude of the spectrogram
ax.contourf(time, freq, data)

I'm a newcomer and didn't find an example notebook that matched this application directly, so I'd definitely appreciate it if you could help or point me to the right resource. Thanks!

Without being able to run it I can't quite see what makes that non-rectangular, but whatever it is, seems like it's likely to be covered by a QuadMesh.  If so, there's Datashader-based rendering for Quadmeshes via Datashader's trimesh support, and we will eventually add faster quadmesh-specific support.

We can aggregate QuadMeshes as the input via the trimesh renderer but we do not output QuadMeshes except for log-axes, which I think is what is being asked for here. Once we have a real QuadMesh rendering we should also make sure that at least the log-axis rendering works, which I think is currently not supported for trimesh and raster aggregations either.

Here's a file with sample data if you'd like to see for yourself.
npzfiles = np.load('spectrogram.npz')
data = npzfiles['data']
timevec = npzfiles['timevec']
freqvec = npzfiles['freqvec']

Most commonly the plot is either with log-linear or linear-linear for the frequency and time axes, respectively. Which renderer do you recommend for speed? (For reference, an older issue https://github.com/pyviz-topics/EarthSim/issues/151 seemed to indicate that quadmesh rendering was slow, but this was a while ago and may have been addressed by now?)


Crashing when crouch+rightclick to edit placed signs

Log: https://paste.ee/p/FJayB
Any more details you want that aren't in the log?

oop- I was using v0.6.1 let me try updating.


Scaffolding for exercise stages and application statuses

Initial views for all exercise stages and editing application status

THis is ready to merge


Fix- Issue 1421- PeoplePicker Control - Shows wrong value in Dynamic Form when null is provided

Q
A

Bug fix?
[x]

New feature?
[ ]

New sample?
[ ]

Related issues?
fixes #1421 #1578

What's in this Pull Request?
Fixing the issue 1421, Validating the Null in the user's name or email.
Fixing issue 1578, Error on save when clearing person from Person or Group field and leaving it blank.
Solution for Issue #1421
I have created a few users in my tenant, with the below mentioned names and email's

Added two columns in my test list, one as multi user, and single user respectively, and added the users to the list item as below.

I have also added extra validation at SPService.ts for the methods, getUsersUPNFromFieldValue & getUserUPNFromFieldValue to get the output as below.

Solution for Issue #1578
When the user is updating the people picker column, for a single user, Dynamic form is throwing error while saving the list item. The issue occurs at method onSubmitClick
The object formed with an empty user and is being submitted to update the item
          else if (fieldType === "User") {
            objects[`${columnInternalName}Id`] = val.newValue;
          }

And the error is caught here,
let newETag: string | undefined = undefined;
if (listItemId) {
  try {
    const iur = await sp.web.lists.getById(listId).items.getById(listItemId).update(objects, this.state.etag);
    newETag = iur.data['odata.etag'];
    if (onSubmitted) {
      onSubmitted(iur.data, this.props.returnListItemInstanceOnSubmit !== false ? iur.item : undefined);
    }
  }
  catch (error) {
    if (onSubmitError) {
      onSubmitError(objects, error);
    }
    console.log("Error", error);
  }

By validating the null check as below, the issue is resolved.
else if (fieldType === "User") {
    objects[`${columnInternalName}Id`] = val.newValue.length === 0 ? null : val.newValue;
}

I have also corrected a spelling mistake at onSubmitClick
from, 'val.newValue.lenght'
          else if (fieldType === "UserMulti") {
            objects[`${columnInternalName}Id`] = { results: val.newValue.lenght === 0 ? null: val.newValue };
          }

To, 'val.newValue.length' as below.
else if (fieldType === "UserMulti") {
            objects[`${columnInternalName}Id`] = {
              results: val.newValue.length === 0 ? null : val.newValue,
            };
          }

Thanks,
Nishkalank Bezawada

Hello @joelfmrodrigues & @AJIXuMuK
I have created a new PR fixing the Issue 1421 & Issue 1578
Kindly review,
Nishkalank Bezawada

@NishkalankBezawada many thanks! Awesome work and super detailed explanation on the issues 👏👏👏

esome work and super detailed explanation on the issue

Thanks alot Joel @joelfmrodrigues


moves google cloud java bom out of our bom

fixes #456

I'm actually not sure we should do this based on the comment from @snicoll on the issue:

This BOM is providing support for the Google platform and, as such, should provide versions for Google-related artifacts.

ok then let's close this as well as the underlying issue that's a blocker for M3 ? @joaoandremartins @meltsufin

I'm OK with what this PR proposes due to my argument in #456.
Just wanted to hear other people's opinions before.
@meltsufin @artembilan @balopat if you agree that this is a good thing, I think we should merge it in.

Well, as far as all our modules provide the proper transitive dependencies from that Google BOM and our Boot starters have a good opinionated set set of dependencies, I think this is the way to go - merge this PR and reconsider if there are some concerns.

due to my argument in #456.

I don't think that's right. There is a difference between you providing a version (because you're using the bom internally) and enforcing a set of consistent versions (that's what dependency management does.
If the Google BOM has been cleaned and doesn't leak 3rd party artifacts, I think we should include it in the bom.

I guess if a user wants to force a version, setting it explicitly in their pom is still closer to the root than our BOM, so I don't have issues either way.

@joaoandremartins or they can just provide the version rather than no version at all. This is how it works in Spring Boot since day 1.


Countdown Timer Displaying -18275 Days for March 9th 2020

Hi
Unsure if this is a result of an incorrect config by myself, however the module is displaying -18275 Days for the 9th March 2020. Please see my config below
{
module: 'MMM-CountDown',
position: "bottom_left",
config: {
// See configuration options
event: "Dissertation Due",
date: 2020-03-09,
showHours: false,
showMinutes: false,
showSeconds: false,
}
},
Thanks
James

It took awhile to get through this, and I'm a noob with under 10 hours in js, but I had to make a few changes to the MMM-CountDown.js file in the module's folder.
At the top of the file, change
defaults: { 		event: "New Millenium:", 		date: "3000-01-01",
to:
defaults: { 		event: "New Millenium:", 		date: "2020-07-01",
next go down to lines 35-37 and update them to say
		var today = new Date().getTime(); 		var target = new Date(this.config.date); 		var timeDiff = target - today;


Revert "fix crash when deleting more than 21 vouchers"

Reverts mirumee/saleor-dashboard#1263

Task linked: SALEOR-3967 Dashboard error on removing multiple vouchers


feat: add container entity in explore page

Describe your changes :

I worked on the ..... because ...
Added container tab in Explore page

Type of change :

[x] Improvement
[x] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Frontend Preview (Screenshots) :
For frontend related change, please link screenshots of your changes preview! Optional for backend related changes.

![image](https://user-images.githubusercontent.com/33024356/225658364-cefe6033-c02c-4644-921a-9de778fd2c12.png)

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers

Frontend: @open-metadata/ui


Add support for audioworklet

When I'm trying to extend audioworkletnode in my react app,

Unhandled Rejection (TypeError): Failed to construct 'AudioWorkletNode': Please use the 'new' operator, this DOM object constructor cannot be called as a function.

And my code is
class InputWorkletNode extends window.AudioWorkletNode {
	constructor(context) {
		super(context, 'input-processor');
	}

	get recBuffers() {
		return ['test', 'test!'];
	}
}

Someone pointed out it might be an issue with babel, which prohibits us from extending native classes.
So is there any way to write vanilla JS inside the src folder?
How could I solve this issue?

Solved by putting the code into the public folder and changing it to
`window.InputWorkletNode = class InputWorkletNode extends window.AudioWorkletNode {
constructor(context) {
super(context, 'input-processor');
}
get recBuffers() {
	return ['test', 'test!'];
}

}`


Documentation of owns

The documentation of the "New Ownership API" has a flaw.  If you search the page for "$owns" there is one occurene in the code.  It is only occurence of "owns" also.  Unless a huge screen and a small font it is impossible to tell you are in the section documenting "$owns".  So put an example directly below the h3
Like
$owns = <array of class names>
but in the style you like.
Would hjhave saved at least one question on slack!

PR https://github.com/silverstripe/silverstripe-framework/pull/7604


hotfix: update variable name

Hi, the frontend was crashing for me, I am guessing due to a rename. I debugged it and found this variable which seemed like it could be fitting.

ty <3


about the encoder

Hi! Is the pre-trained encoder for RGB images and depth images the same one?

Yes, we use the standard KL-regularized autoencoder from stable diffusion.


Query param to filter out "fee" transactions

Bank transactions include a field for fee which can either be:

"BANK"
"VALIDATOR"
""

The blank string means no fee/normal transaction. We need a query param that allows the user to retrieve the results for all non-fee bank transactions.
Example response for GET /bank_transactions - https://gist.github.com/buckyroberts/2365050d1c93da83fff75dd52e387be0

Can I take this?

@DucPhamTV all yours


Activity recognition using your model

Hi there,
Is it possible to detect activity using you model? If yes, could you please provide a script to run detection? What would be the input data (rgb video/picture or skeleton data)?

Hi @ywang0218,
Thanks for your interest! Unfortunately, action detection is out of the scope of this work, but it would be an interesting future direction.


add riemman integration v2'

I fix the documentation by changing docstring of the function.

And thanks for reviewing, @uncomfyhalomacro! Your work is greatly appreciated. 😄


Why test files do have their own package (cli_test)

Hi, I have forked this repo to add some features that I needed.
I was wondering why test files does have their own package. It is annoying, it took me some time to realize ( as this is not the usual way of doing things in go ).
To write some new code I did have to either change all import clauses in test files to point to my package instead of github.com/codegangsta/cli or rename package cli_test to cli. Either way this is additional work every time i want to fork something, and then when i want to create pull request.
I haven't seen such setup anywhere else. I would appreciate if you could please tell me why it is like this, and if I can raise a pull request to clean this up?
Best regards,
Maciej

@szank It's a good way to see how your package works when imported. When you have a test package that is "local" to your package then you have access to unexported variables and struct values that might not need to be exported (or shouldn't be). By putting your tests in a different package you can test the behavior your users will be experiencing.

Hi @polds
This was a pain point when I first forked this project, I wasn't expecting to be forced to search and replace "import github.com/codegangsta/cli" into github.com/szank/cli before i run my code, and then do the reverse when I want to submit a pull request, then again to continue working on my fork
Unit tests are not meant to be a black box tests anyway, but I will respect your decision.
I would like to suggest an improvement to this solution.
Here https://golang.org/src/bufio/bufio_test.go for example package bufio is imported as
package bufio_test
import . "bufio"

This provides the solution you need without drawback I have just outlined. This is a needed improvement for anyone who forks this project imho.

@szank, it isn't entirely obvious, but you don't have to change the imports. What you can do is add your fork as a remote to the git repo at ${GOPATH}/src/github.com/codegangsta/cli. This way, you can make your changes in your branch, but you still have the paths of the canonical repo.

Indeed, the typical workflow for forking a Go project is to fork it into the canonical path within your $GOPATH and add your fork as an upstream.
I.e.
git clone git@github.com:codegangsta/cli  ${GOPATH}/src/github.com/codegangsta/cli
cd ${GOPATH}/src/github.com/codegangsta/cli
git remote add fork git@github.com:szank/cli

Hi,
I will use this approach then. Thanks for clearing it up !
Regards,
Maciej


Fix Release() arrow callbacks

Our usage of Release of arrow records during callback is inconsistent. If operators are utilized they won't release the callback record, but will create a new one which the final callback can release.
However if there is no operators and it's just straight iteration then a release on the final callback will cause too many releases to occur.
This is easy to reproduce by running unit tests with -tags assert
The final callback should always be able to safely release the given record.
We should detect this automatically but adding -tags assert to our github workflow.

Oh cool didn’t know about the assert tag!

I could take a look at it

@thorfour I think the issue we're having is us calling HashAggregate's Close() method multiple times (as that's where it releases its arrow records).
For a query like this:
err = engine.ScanTable("simple_table").
Aggregate(
	[]logicalplan.Expr{
		logicalplan.Sum(logicalplan.Col("value")),
	},
	[]logicalplan.Expr{
		logicalplan.Col("names.first_name"),
	},
).

We end up w/ a physical plan like this:
     1                           2                                           3                 4
TableScan [concurrent] - HashAggregate (sum(value) by names.first_name) - Synchronizer - HashAggregate (sum(value) by names.first_name)
                       - HashAggregate (sum(value) by names.first_name) -
   multiple plans ->   ... for each TableScan.plan
                       - HashAggregate (sum(value) by names.first_name) -

We end up calling the Close() method for each of tablescan's plans (2)
https://github.com/polarsignals/frostdb/blob/de942d0ce46e8ca34b3f08cc96f3ce61da96f26a/query/physicalplan/physicalplan.go#L125-L129
This in turn will call Synchronizer's (3) Close multiple times, which will call HashAggregate's (4) Close method mulitple times.
I think it's reasonable for a given step in the physical plan to expect to only have its Close() method called once, with the exception of possibly synchronizer. To that end, I think it's reasonable for us to add some logic into synchronizer to call next.Close() only once.
What do you think of that plan?

I think that makes a lot of sense. The synchronizer should have the logic to only call close once.
I think when I first wrote this issue there was also an issue with performing a query with no operators. So that may be something to look into as well.

You were thinking something like this?
err = engine.ScanTable("simple_table").
  Execute(context.Background(), func(ctx context.Context, r arrow.Record) error {
	  fmt.Printf("%v", r)
	  return nil
  })

That actually seems to work alright.
We have a number of tests that seem to release the record in the  table iterator callback, which I'll clean up as well
https://github.com/polarsignals/frostdb/blob/de942d0ce46e8ca34b3f08cc96f3ce61da96f26a/table_test.go#L176


contribute: deprecate NIN and replaced with vNIN as instructed by NIMC

Thanks for the contribution

Please add the function to the README.md file for documentation. You can also add yourself as a contributor


update README steps for updating the base ecosystem page - categories/subcategories

What changed? Why?
Updated the steps in the README file related to the Updating the Base Ecosystem Page
 to reflect the change from tags to categories and subcategories!
Notes to reviewers
I've also fixed the ecosystem.json entry for MADNFT which was using the previous tags key.
How has it been tested?
See screenshot of the updated README below:

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/2

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
1

Sum
2

ACK
@dry-tortuga Epic, thank you 🥇

Happy to help!


Support for sparse secondary indices

Dynamo doesn't require every record to have a value in a table's global secondary index (this is known as a sparse index).
It would be helpful to be able to define a table type with
type TableRecord = {
  gsiPk?: string;
  gsiSk?: string;
};

And then refer to gsiPk and gsiSk as the sort keys.  Right now optional string types are not acceptable as valid key types, so to create a sparse index you need to leverage multiple table definitions.  This is a fairly common pattern (it's used in AWS's examples extensively) so it would be nice to see it reflected in this package!

Hey @quinnromanek Thanks for the suggestion, this is definitely on our radar as something we would like to implement. If you think you could do it yourself, please submit a PR, we would love to see it! Otherwise we will be happy to implement soon.

@quinnromanek The latest version v6.0.187 now opens up the keys you can use for secondary indexes, hope this works for you


store the custom model file into correct path

if pepole modified models.namespace in config/voyager.php, then add new database table with option 'Create model for this table'  and save it. The model file can save into  a correct path that I configed.

Thanks! 👍


[Documentation] Update C# example of tween_method in Tween class with a parameter to the lambda method.

Closes this issue: https://github.com/godotengine/godot-docs/issues/7738
In the C# example the lambda method is missing a parameter which causes an error since the tween_method expects a method with a pass in parameter, this updates the documentation to reflect that and also uses the parameter in the lambda to match the GDScript example.
I hope I haven't messed anything, it's my first PR so please have mercy.

@RedworkDE thanks for the suggestion, the original comment felt a bit off so I just tried to suggest something but honestly wasn't sure what to do with it either heh. Is there anything I need to do now, please? I'm not familiar with this process.

Check https://github.com/godotengine/godot/blob/master/CONTRIBUTING.md and its linked docs pages for more general information about contributing.
You need to squash the two commits into one by following these instructions: https://docs.godotengine.org/en/latest/contributing/workflow/pr_workflow.html.

@RedworkDE Thanks, I tried to follow it but I'm not sure if it's ok like this or if I messed something up? Really thank you for your time.

Thanks!


No tests?

I know that this library may be considered "just" a wrapper. Yet the lack of tests disturbs me a little.
Should they be included?

Should be a must for every PR.

I would have to agree. Does anyone feels like having a go at it..?

@radmen @szepeviktor @nkkollaw what about Kahlan? It allows to stub on php function so it will be easy to test whether functions are proxing the valid php functions. I can wrote some tests today

Fine with me. :-)

@damian-dziaduch-gforces Kahlan looks like an interesting choice. I've no experience with this tool, yet if you will prepare an example I'd gladly use it ;)

PHPUnit might work as well..?

AFAIR PHPUnit is not able to mock native functions.
As I see it we have two options

find something that can mock native functions and write tests based on that (eg. Kahlan)
write tests which simply compare results of wrapper with native functions

Ad. 1
I think this is safer - if mocking library works as intended we will make sure that wrapper function calls the correct function with correct arguments passed.
Ad. 2
This option is less secure - we're checking only results of calls, so it's possible that wrapper function may work in a different matter as wrapped function.

I vote for option 1.

So, this is where we got to so far:
@damian-dziaduch-gforces  says: Kahlan stubs on php functions works only when you test psr0 / psr4 classes - it mocks composer autoloader. So it will not work with functions
@radmen says: In this case, we can simply create a class with static methods instead of separate functions.
@radmen , that would mean that you like \PHP\PHP::str_pos() better than \PHP\str_pos(), or would you create a wrapper class that just called the function to make Kahlan work?

that would mean that you like \PHP\PHP::str_pos() better than \PHP\str_pos(), or would you create a wrapper class that just called the function to make Kahlan work?

I'd create wrapper class only to make Kahlan work :)
Yet, writing a god class (with lots of LOC) is not a good idea. After some time it may be hard to maintain.
Regarding limitations of Kahlan I'm suggesting to keep writing plain wrapper functions and test them with PHPUnit (comparing results of wrapper and wrapped function).
As I imagine the code will go through code-review so we can assume that reviewer will take care of checking if the wrapper is calling the correct function.

@radmen : That sounds good to me. Can you create a stub/example and add it to a CONTRIBUTE.md file? You know more about tests than I do.

@nkkollaw I'm not very good at writing docs. If possible I'd like to leave writing CONTRIBUTE.md to you :)
However, I can create a simple foundation for development - basic structure, one (or two) functions with tests etc.

Also, should I add you as a collaborator?

That's much of responsibility ;) I don't know for now if I'll have enough time for such thing. IMO let's keep things as they are right now.

However, I can create a simple foundation for development - basic structure, one (or two) functions with tests etc.

That would be absolutely great. I'll then write the documentation.

Closing this since we now have tests thanks to @radmen (https://github.com/nkkollaw/php/pull/89).


Total approved cost shows as £0.00 even when approved for a higher amount

See https://test-apvs-internal-web.kainos.com/claim/116. Is there any reason for this?
Thank you

@userresearcher No, this is a bug that we'll have to fix

@userresearcher please check if this problem is fixed and close this issue.


Supporting the Interchain ecosystem and current Hermes users

Background
This issue keeps track of the work that contributes to the objective to "Support the Interchain ecosystem and current Hermes users".
The work here mainly revolves around maintaining the current Hermes architecture, though we expect to have migrated to the next iteration of Hermes' architecture by v1.5. The scope of this objective also includes adopting upstream changes that align with the goals of Tendermint and the Cosmos SDK, as well as fielding questions / requests from ecosystem users.
Tasks

[ ] #2788
[x] #2970
[ ] #2809 Moved to Q2
[ ] #2971
[ ] #3005
[ ] #3040

Closing this issue as we'll be tracking OKRs directly in the Hermes project board instead of as issues.


Clay embeddings on Sentinel-1 data

Added notebook to demonstrate use of Clay embeddings on Sentinel-1 imagery for earthquake detection

Thanks @srmsoumya for your inputs. I have updated the notebook. Request you to please review


Created NLP in Thai section

In reference to Issue #118 , I have created a small NLP in Thai section in the awesome list

@the-ethan-hunt this is a good PR! Thanks for the effort.
I've made some suggestions to make it the best we can do. Ready to discuss as per your opinions.


Tree elements (TreeNode) should be in a separate file from alogorithms (DecisionTree)

Closed with CART implementation in #32, #38, #44, #50, #55.


help editing camera settings

Hello,
I'm trying this plugin and I cannot find camera settings, is there a way to change values such as distance between the eyes, ratio or camera rotation? Thanks

Hi, unfortunately no. But with new official plugin in 4.12 support IPD changing :)


Problem with string escaping when joining by Browser

When joining a Teams-Meeting as a Guest in the Browser there seems to be problems with string escaping. Sadly i can't exactly tell how to reproduce. Happened with different attendees with different browsers on different days it happened to different people.
Day 1:

Day 2:

Having the same issue.
Only happening as a guest and everytime you enter a room its add another string scape, and eventually having a name, like so: \“\”\“\”\“\”\“\”\“\”\“\”\“\”\“\”\“\”\“Name` (Guest)\“\”\“\”\“\”\“\”\“\”\“\”\“\”\“\”\“\”\“

@StayFN - Could you please confirm if your issue has resolved or still looking for any help?


Android signing issues

One note, if you generate the Android signing files from code it'll generate a new signing file for every build
Which means that if you have the app installed on your Android device you won't be able to update to a new version
It'll be treated as a separate app, or the install will be rejected
Unless you uninstall the already installed version first
Code signing for android is even worse than for iOS
Because there's no way of regenerating the same keystore
If you lose it you won't be able to push an update to Play Store
We had this issue once, and the only solution is to upload the new version as a completely new app..
We researched this for days, as we didn't believe that there's no other way
But we found no other solution, even after contacting Google
So the keystore file is really really important in case of Android
At least when you publish to Google play store

bitrise now has a sign-apk step so you can upload your key and use that to sign the app.  This means you can get rid of the second build.gradle, the workflow steps to copy it and the step to create the key.

Can you do a PR?

I create PR #76 It was a manual merge of the bitrise.yml that works for my project (which has now diverged too much from your repo to actually be useful as a base for pull requests.)
It should work if you drop it in, but some tweaks may be needed.  I don't think it is something I can actually test.

Thanks @larubbio !  I'll look at this later in the afternoon

I am really having trouble with this part of getting snowflake to build from bitrise. What exactly do we put in the secret variables for android?

In your BitRise Secret Env Vars you should have the following assuming you used the default values when building the certificate.

SNOWFLAKE_RELEASE_STORE_FILE = my-release-key.keystore
SNOWFLAKE_RELEASE_KEY_ALIAS = my-key-alias
SNOWFLAKE_RELEASE_STORE_PASSWORD = whatever password you provided for the store
SNOWFLAKE_RELEASE_KEY_PASSWORD = whatever password you provided for the release
PARSE_APP_ID = If you're using PARSE, enter it's APP ID
PARSE_REST_API_KEY - If you're using PARSE, enter the REST API Key

I appreciate your response ~
That makes sense since I never built a certificate. I followed your youtube tutorials and only saw you create a cert for the iOS version. I'm on a linux machine so I couldn't do any of the XCode things. I'm not sure how to do the certificate or the keys for the store/release. (noob here)

@austynpember you may want to look at Exponent. The goal of the project (one of them, anyway) is never open Xcode or Android Studio. As for those having issues with Bitrise give Buddybuild a try. It was super easy to setup a cross-platform RN app and start distributing test builds whereas Bitrise wasn't. YMMV
https://habd.as/beta-testing-react-native-buddybuild/

Not addressing


refactoring

@vfdev-5 this is not complete yet , but I'd like your opinion on the current changes. , I think it's not testable on Colab due to huge computational requirements.

@ahmedo42 thanks for the update ! I'll take a look a bit later.

Thanks for the feedback , Now the code works on Colab without any issues , I suspect there is something wrong with progress bars as they are not displayed correctly


mac os ffmpeg:version 4.2.1

zhanglu@MacBook-Pro example % go run tutorial01.go
github.com/giorgisio/goav/swscale
cgo-gcc-prolog:50:2: warning: 'sws_addVec' is deprecated [-Wdeprecated-declarations]
/usr/local/Cellar/ffmpeg/4.2.1_2/include/libswscale/swscale.h:267:1: note: 'sws_addVec' has been explicitly marked deprecated here
/usr/local/Cellar/ffmpeg/4.2.1_2/include/libavutil/attributes.h:94:49: note: expanded from macro 'attribute_deprecated'
cgo-gcc-prolog:84:35: warning: 'sws_cloneVec' is deprecated [-Wdeprecated-declarations]
/usr/local/Cellar/ffmpeg/4.2.1_2/include/libswscale/swscale.h:270:1: note: 'sws_cloneVec' has been explicitly marked deprecated here
/usr/local/Cellar/ffmpeg/4.2.1_2/include/libavutil/attributes.h:94:49: note: expanded from macro 'attribute_deprecated'
cgo-gcc-prolog:100:2: warning: 'sws_convVec' is deprecated [-Wdeprecated-declarations]
/usr/local/Cellar/ffmpeg/4.2.1_2/include/libswscale/swscale.h:266:1: note: 'sws_convVec' has been explicitly marked deprecated here
/usr/local/Cellar/ffmpeg/4.2.1_2/include/libavutil/attributes.h:94:49: note: expanded from macro 'attribute_deprecated'
cgo-gcc-prolog:129:35: warning: 'sws_getConstVec' is deprecated [-Wdeprecated-declarations]
/usr/local/Cellar/ffmpeg/4.2.1_2/include/libswscale/swscale.h:264:1: note: 'sws_getConstVec' has been explicitly marked deprecated here
/usr/local/Cellar/ffmpeg/4.2.1_2/include/libavutil/attributes.h:94:49: note: expanded from macro 'attribute_deprecated'
cgo-gcc-prolog:165:35: warning: 'sws_getIdentityVec' is deprecated [-Wdeprecated-declarations]
/usr/local/Cellar/ffmpeg/4.2.1_2/include/libswscale/swscale.h:265:1: note: 'sws_getIdentityVec' has been explicitly marked deprecated here
/usr/local/Cellar/ffmpeg/4.2.1_2/include/libavutil/attributes.h:94:49: note: expanded from macro 'attribute_deprecated'
cgo-gcc-prolog:196:2: warning: 'sws_printVec2' is deprecated [-Wdeprecated-declarations]
/usr/local/Cellar/ffmpeg/4.2.1_2/include/libswscale/swscale.h:271:1: note: 'sws_printVec2' has been explicitly marked deprecated here
/usr/local/Cellar/ffmpeg/4.2.1_2/include/libavutil/attributes.h:94:49: note: expanded from macro 'attribute_deprecated'

same issue. how to fix it?

@woodandfire fork this repo. replace the deprecated apis with new ffmpeg apis

any news on this issue ?

ffmpeg 4.0.3 is ok


Update to 1.19.4

This pull request fixes all of the GUI buttons for the config options, as well as adding support for 1.19.4.

tysm for updating :D


Deauthentication Script

This should be pretty easy. Follow this guide without copying the code too much. Reference cite anyway because he is a cool dude.
http://raidersec.blogspot.com/2013/01/wireless-deauth-attack-using-aireplay.html

Added in commit 37e4727d0a96683a1d6cee670cff382ceb3e08c6


Does adftools publishing support both data factories connected to DevOps Git repos

Hello,
we have a setup with two data factories - both of them being connected to their individual Azure Git repo.
I created a deployment process with DevOps pipelines. According to the logs all works fine, but there are no changes visible in the target factory.
Is this setup supported? If yes, how do I make it work?
Rgds,
Markus

I think you need to provide more details.


masterpdfeditor: 5.1.12 -> 5.1.60

Motivation for this change
masterpdfeditor: 5.1.12 -> 5.1.36
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Fits CONTRIBUTING.md.

I thought we no longer needed makeWrapper due to some trick.

@CMCDragonkai The "trick" must be this one: https://github.com/NixOS/nixpkgs/issues/24256#issuecomment-300481034, which unfortunately isn't enough - see https://github.com/NixOS/nixpkgs/pull/44047.
I poked through other changes referring to that issue, and am fine with adding the wrapper, with a comment above like in https://github.com/NixOS/nixpkgs/pull/43390/files#diff-c2877cd32bac930d3156eb07aa8821fdR62
(Although we should use ${lib.getBin qtbase}/${qtbase.qtPluginPrefix} as mentioned by @ttuegel (and probably fix that in other places where the wrapping is done in a separate PR too))
@apeyroux can you update your PR with the comment and proper wrapping path?

@apeyroux can you prefix "masterpdfeditor" on the first commit msg of this PR? Apart from that, ready to be merged :-)

Thanks!

backported to release-18.09 in c5dee016270aa463286cff8a1b0ae81620407788, 79c8e369bb44c6761d098d1923a71d30ab053ea1 and 0267a5a33e2083ccd90d8d6dc6f1ccf8ceb56d53.
Merry Christmas!

Thanks! Sadly, it seems like now they released 5.2.20 and 5.1.60 is 404ing.
Does anyone have any contact with upstream? Their behavior is really annoying.

up to 5.2.20 -> #52871


Modify and run experiment not working as expected with dvclive params

When I try to modify and run an experiment, it looks like the extension tries to modify all parameters, including those which haven't changed and those which are not dependencies of the pipeline (results/train/params.yaml are outputs of dvclive). This is from a fresh clone of https://github.com/iterative/example-get-started-experiments:
https://github.com/iterative/vscode-dvc/assets/2308172/90315710-9cfb-4183-b159-57a100420927
Here's the error output:
Running: dvc exp run -S params.yaml:train.img_size=1025 -S params.yaml:train.batch_size=512 -S results/train/params.yaml:model=DynamicUnet -S results/train/params.yaml:batch_size=8 -S results/train/params.yaml:batch_per_epoch=8 -S results/train/params.yaml:frozen=false -S results/train/params.yaml:frozen_idx=0 -S results/train/params.yaml:transforms=[Pipeline: PILBase.create, Pipeline: partial -> PILBase.create] -S params.yaml:base.random_seed=42 -S params.yaml:data_split.test_pct=0.15 -S params.yaml:train.valid_pct=0.1 -S params.yaml:train.arch=shufflenet_v2_x2_0 -S params.yaml:train.fine_tune_args.epochs=8 -S params.yaml:train.fine_tune_args.base_lr=0.01 -S params.yaml:evaluate.n_samples_to_save=10

ERROR: unexpected error - LexerNoViableAltException: transforms=[Pipeline: PILBase.create, Pipeline: partial -> PILBase.create]
                                                                                ^
See https://hydra.cc/docs/1.2/advanced/override_grammar/basic for details

Besides this error, we should not show results/train/params.yaml parameters in the dropdown at 0:05 since these are not modifiable dependencies of the pipeline.

it looks like the extension tries to modify all parameters,

All of the parameters are passed to exp run as that is how we reflect the experiment that was used as a base. This is how we get around having to apply the experiment before kicking off a run. Do you have any suggestions on how to workaround that problem? Applying the experiment first would mean that the data from the base would also be used (related to https://github.com/iterative/vscode-dvc/issues/2394). WDYT?

Besides this error, we should not show results/train/params.yaml parameters in the dropdown at 0:05 since these are not modifiable dependencies of the pipeline.

How would we exclude these? We are currently using the exp show data to grab all of the parameters for an experiment.

I can fix the error by making sure that I wrap all string values in single quotes. E.g the command for example-get-started-experiments becomes something like:
dvc exp run -S params.yaml:base.random_seed=43
-S results/train/params.yaml:model='DynamicUnet'
-S results/train/params.yaml:batch_size=8
-S results/train/params.yaml:batch_per_epoch=8
-S results/train/params.yaml:frozen=false
-S results/train/params.yaml:frozen_idx=0
-S results/train/params.yaml:transforms='[Pipeline: PILBase.create, Pipeline: partial -> PILBase.create]'
-S params.yaml:data_split.test_pct=0.15
-S params.yaml:train.valid_pct=0.1
-S params.yaml:train.arch='shufflenet_v2_x2_0'
-S params.yaml:train.img_size=256
-S params.yaml:train.batch_size=8
-S params.yaml:train.fine_tune_args.epochs=8
-S params.yaml:train.fine_tune_args.base_lr=0.01
-S params.yaml:evaluate.n_samples_to_save=10

Still unsure of how to exclude the unmodifiable dependencies of the pipeline.

I never thought enough about it before, but this seems dangerous since the baseline may have changes that aren't just different hyperparameters. How important is this functionality? I'm wondering if we should drop it and only allow the current workspace as the baseline like the CLI does. If it's crucial for something, we could think about whether we can handle this correctly inside the CLI.

Only 60 users have used the 2 commands (modify and run + modify and queue) in the last 90 days:

We can drop the functionality for all non-workspace records and consider bringing it back later. I still need to correctly handle strings as if a user wants to modify a param like results/train/params.yaml:transforms they'll currently run into issues.
I'll raise a couple of PRs.

Besides this error, we should not show results/train/params.yaml parameters in the dropdown at 0:05 since these are not modifiable dependencies of the pipeline.

I guess this becomes less of a priority?

I guess this becomes less of a priority?

Yeah, it's less severe then, although I still think it is confusing for users (here and in Studio), so I'd like for the DVC team to take a look at how to do this. I'll open an issue.


Automate publication of the TFL issue DAG to a stable public URL

What is the problem?
We use a tool to track a DAG of issues related to TFL, but that's not easily visible publicly.
Do you recommend a solution?
Automate publication of the DAG.

I just learned in the http://zcasharborist.org call that the TFL-scoped dag should already be published at https://zcash.github.io/developers/zcash-tfl-dag


Scala 2.12.6 and other dependencies

sbt 1.1.4
Scala 2.12.6
ScalaCheck 1.14.0
ScalaTest 3.0.5
Contraband 0.4.0

To validate this pull request against other sbt modules, please visit this link.


build with rust-nightly passing tests

Note to get the working build with passing tests I had to comment out the mutable_json.

@ttdonovan big thanks for the PR! I am waiting for a first success build of iron on nightly to update rustless and all it deps. But if you interested it jsonway itself, I will find some time today (GMT+3) to merge this.

Merged with a few fixes, thanks @ttdonovan!


Feediron stop working on Tiny Tiny RSS v17.1 (ecab435)

Today, I've reset the TTRSS preferences for fresh and re-configs. But after enable feediron, it's disappeared from the Preferences Tabs

Hmm, I'm very sorry I hadn't updated a long time ago and I'm currently not able to maintain it. I'm sorry.

Thanks for your reply, I will fixing by myself, thank again for great job, I'm still using Tiny Tiny RSS until now because you plugin 😄

If you fix it please share your results.

OK, I'll trying to rewrite it from scratch but if I have time :D
I've rolled back my database and lost for 10 days but it's worth to bring feedion back temporaty.

@shoeper @m42e I've cloned ttrss and replace my old ttrss source with fresh new. With just only feediron plugins, it's activable again and the Feediron tab appeared.
It's fixed temporary.


Immediately closes when called within Modal

When I call DocumentPicker.pickMultiple within a Modal it immediately closes and returns no results whatsoever and no error.

I have the same problem. When I open the Document Picker from Modal immediately closes.

Faced a similar problem. I found out that if you do not close modal, then picker will not close. Or close modal after selecting a file.


Implement a percentile function

The pth percentile of a list is the smallest number that is at least as large as p% of the numbers in the list.
That means: sort the list from low to high, go p% up the list from the bottom. If you're at a place on the list, take its value. Else take the next one.

By the way, this has different behavior from the np.percentile built-in function because it does not interpolate between values.


hyprpm: fix hyrpm sometimes returning 0 despite errors occuring

Describe your PR, what does it fix/add?
This PR changes hyprpm's return codes in a couple of misusage situations, mainly when hyprpm reload fails because of headers being out of date. This, alongside with being a behavior most people would expect, as the command did not, in fact, execute successfully, makes some basic scripting like hyprpm reload 2>&1 | grep "not up-to-date" && hyprpm update easier (the example can be reduced to hyprpm reload || hyprpm update)
Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
no.
Is it ready for merging, or does it need work?
should be good to go, as it doesn't really change anything significant. Still, lmk if you'd like anything to act differently

mhhhh wdym

fixed. However, take a look at it. I changed it because it was horrible and inconsistent (literally the following lines use a different and more readable style). idk why clang-format wants that, it honestly sucks, but whatever. if you want clang-format to pass, it does now

sure


Handle \wj markers plus start on Bible front matter plus other small improvements

Pull Request Test Coverage Report for Build 134

203 of 217 (93.55%)  changed or added relevant lines in 9 files are covered.
592 unchanged lines in 11 files lost coverage.
Overall coverage decreased (-5.8%) to 68.767%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

tx_usfm_tools/support/contextRenderer.py
0
1
0.0%

tx_usfm_tools/support/singlehtmlRenderer.py
0
1
0.0%

resource_container/ResourceContainer.py
8
12
66.67%

tx_usfm_tools/verifyUSFM.py
21
29
72.41%

Files with Coverage Reduction
New Missed Lines
%

tx_usfm_tools/support/singlehtmlRenderer.py
1
55.67%

resource_container/ResourceContainer.py
3
77.0%

tx_usfm_tools/support/csvRenderer.py
13
0.0%

tx_usfm_tools/support/asciiRenderer.py
33
0.0%

tx_usfm_tools/support/mdRenderer.py
42
0.0%

tx_usfm_tools/support/loutRenderer.py
54
0.0%

tx_usfm_tools/support/mediawikiPrinter.py
69
0.0%

tx_usfm_tools/support/contextRenderer.py
77
0.0%

tx_usfm_tools/support/readerise.py
78
0.0%

tx_usfm_tools/support/htmlRenderer.py
85
0.0%

Totals

Change from base Build 130:
-5.8%

Covered Lines:
5969

Relevant Lines:
8680

💛  - Coveralls


Prepare for meeting with David Man on project handoff

Making preparations  to present on project handoff requirements with David Man. Next call on the schedule with him is 9/23 so aiming to have it ready by then.
By end of next week (9/13) try to confirm with David that we want to keep the 9/23 meeting. @jkarpen will reach out after confirming status with Jason next week.

Closing this issue, we met with David Man today and discussed next steps for the handoff and IAA. We also agreed to switch to a monthly cadence for meetings with him instead of bi-weekly.


Method to unload an adapter, to allow the memory to be freed

Feature request
Add a PeftModel.delete_adapter(adapter_id) method. The method should delete the specified adapter and release all references to the adapter's weights, so that the adapter's weights can be garbage collected.
Motivation
I am taking advantage of the small size of a PEFT adapter to quickly evaluate many adapter in succession. This can be done quickly even on a single GPU, because loading an adapter is very fast, much faster the loading the full weights of the base model.
I am essentially doing something like this:
for adapter_in in adapter_ids:
    peft_model.load_adapter(...)
    evaluate(peft_model)

The problem with this naïve implementation is that while adapters are fast to load, they are never garbage collected. A naïve implementation of this loop will quickly exhaust your GPU memory.
Your contribution
I already have code to do this, complete with unit tests. I am happy to post it here, or submit a PR, if you think this feature is worth having.

Thanks for investigating. Could you post the main changes, or explain where the memory leak happens and how you solved it? That way, we can check if that would work as a PR.

Hello, delete_adapter(adapter_id) is already introduced in PR https://github.com/huggingface/peft/pull/695 and find the related docs here: https://huggingface.co/docs/peft/conceptual_guides/lora#utils-for-lora


Added --metadata option, allows the user to specify key/value pairs for encoding metadata.

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[ x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x ] Searched the bugtracker for similar pull requests
[ ] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x ] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[ ] Improvement
[ ] New extractor
[ x] New feature

Description of your pull request and other information
Explanation of your pull request in arbitrary form goes here. Please make sure the description explains the purpose and effect of your pull request and is worded well enough to be understood. Provide as much context and examples as possible.

Added --metadata option, which allows the user to specify key/value pairs for encoding metadata, separated by equal sign. Example: --metadata "album = Movie Title artist = Various artists year = "2010"'. Also tries to capture artist information from the file description, if otherwise not available'

Verified with flake8, no errors.

Have you even tried to check your changes? It does not work since it's not wired into the code.
It must not do anything apart from taking user provided metadata. No extraction from description, etc.
Core tests are broken.
Duplicate of #6064.

Sorry, it will work if you used --add-metadata option as well. Since this --metadata is just providing additional metadatas, so I thought it would be better in that way.
Same as above, it will extract 'artist's name from the file description. More option should be added if required
But it is not still added to the main.


Error message in samples.demux.summary.qzv of PacBio 16S ccs reads

Hi,
I got this error message when importing PacBio 16S ccs reads
Danger: Some of the forward PHRED quality values are out of range. This is likely because an incorrect PHRED offset was chosen on import of your raw data. You can learn how to choose your PHRED offset during import in the importing tutorial.
The code that I use is
qiime tools import --type 'SampleData[SequencesWithQuality]'
--input-path manifest.txt
--output-path samples.qza
--input-format SingleEndFastqManifestPhred33V2
Any help, please!
Thanks!

Hi @emankhalaf , all user support questions should be directed to the QIIME 2 forum. Thanks!


Split extras jobs tests to multiple files to allow better parallelization

Proposed Changes
Split the file https://github.com/nautobot/nautobot/blob/develop/nautobot/extras/tests/test_jobs.py into multiple files.
Justification
The current test_jobs.py file consumes a significant amount of time to complete tests. By dividing it into multiple files, we can take advantage of parallel processing across multiple cores. This will lead to faster and more streamlined unittests execution when parallelized.
For detailed information on the parallelization process, please refer to PR #4112.

Django's built in unittest parallelization (which we nowadays use) partitions by TestCase subclass, rather than by file. The file in question is already well-subdivided along those lines.


Wip Multiple Engines

For the elo rating for multiple engines what cutechess does is it sums up the total win-draw-loss of each engine and calculate the elo from there. In fastchess the same can be done but this time by summing up the pentanomials

For the elo rating for multiple engines what cutechess does is it sums up the total win-draw-loss of each engine and calculate the elo from there. In fastchess the same can be done but this time by summing up the pentanomials

the current state should already have this

This is the current output
Rank Name                             Elo        +/-       nElo        +/-      Games      Score       Draw
   1 engine1                        46.60      39.76     148.15     124.33         30      56.7%      73.3%
   2 engine3                        23.20      44.30      65.66     124.33         30      53.3%      73.3%
   3 engine4                       -23.20      44.30     -65.66     124.33         30      46.7%      73.3%
   4 engine2                       -46.60      39.76    -148.15     124.33         30      43.3%      73.3%

anything else which needs to be changed?

Perhaps display the summed pentanomials in the ratings output?

Rank Name                             Elo        +/-       nElo        +/-      Games      Score       Draw           Ptnml(0-2)
   1 engine4                        23.20      55.06      52.98     124.33         30      53.3%      60.0%      [0, 2, 9, 4, 0]
   2 engine2                        -0.00      56.08       0.00     124.33         30      50.0%      60.0%      [0, 3, 9, 3, 0]
   3 engine1                       -11.59      39.08     -37.04     124.33         30      48.3%      80.0%     [0, 2, 12, 1, 0]
   4 engine3                       -11.59      39.08     -37.04     124.33         30      48.3%      80.0%     [0, 2, 12, 1, 0]

I just noticed nelo error bars always stay the same as long as the number of games is the same, pretty cool