Unable to set a non-standard field value if the field name starts with '__'

Unable to set a field value if the field name starts with '__' but the field is not a Standard Field:
using (var db = new Db
  {
    new DbItem("home") { {"__MyField", "expected value"} }
  })
{
  var home = db.GetItem("/sitecore/content/home");
  Assert.Equal("expected value", home["__MyField"]); // fails
}

Done in v1.1.1.


DEV-1438 get expert title from custom texts

solved conflicts, putting the bundle in a separate commit


Adapt to Enzyme breaking change

Incidentally this extension doesn't have any code broken by the breaking change. Nevertheless trying to open / flag early for the ecosystem

Thank you very much, I will merge and tag a patch version.


Export max_retries as an environment variable

What
provider "confluent" {
  cloud_api_key    = var.confluent_cloud_api_key
  cloud_api_secret = var.confluent_cloud_api_secret
  max_retries = 10
}

The ask is to be able to supply a value for max_retries via an environment variable.

This was added in 1.50.0: https://github.com/confluentinc/terraform-provider-confluent/blob/master/CHANGELOG.md#1500-july-21-2023.
In short, one can use TF_PROVIDER_CONFLUENT_MAX_RETRIES env variable to set max_retries variable.


ISSUE-159: Fix the install document

Rename the db name from registry_db to schema_registry, because the registry.yaml  uses schema_registry as the default db name. Or new users will get error.
The step "Run bootstrap scripts" for CentOS/RetHat is missing.
Also added "Download latest Schema Registry binaries" step for CentOS/RetHat.

+1.

Closes #159

Thanks @vesense


Visualization of marginalized posteriors

In the visualization, pair plots are created that plot on the diagonal the marginal distributions and on the off-diagonal elements the bivariate marginal distributions. The plot distinguishes between 2 normal variables (related to parameters in the model) and the other cases assumed to be uncorrelated.

It would be nice to prescribe quantiles to isolines to be plotted. For the bivariate normal this is e.g. alpha/(sqrt((2*pi)**2 det(cov_2). See e.g. this link  with alpha the quantile, and then substituting this in the bivariate pdf to obtain the isolines, i.e in visualize_vb_marginal_matrix this might be added with dist being the bivariate marginal normal posterior of the two variables

levels = (1/ np.sqrt((2 * np.pi) ** 2) / np.linalg.det(dist.cov)) *np.atleast_1d(alpha)
axes[i, j].contour(xj, xi, pdf, colors=[color], linewidths=lw,  levels = levels)

For the case with two correlated noise terms, the assumptions of just multiplying the two univariate gamma pdf seems not correct, since they are actually correlated.
For the case of a normal distributed model parameter and a gamma distributed noise precision, the plot seems not correct, since these are currently ellipsoids, but for gamma being non-symmetric I would expect a non-symmetric joint pdf.

The merge request has solved 1, 3 might be actually correct and for the example I looked into the gamma distr. was close to a normal distribution, but 2 is still unresolved, correct?

Due to the mean field approximation in VB, all noise groups are independent. Only model parameters can be correlated.

True, I somehow thought that the noise terms are also correlated (thus in a single noise group), but I think that is wrong and all noise are a supposed to be uncorrelated.


images: add workaround for smee-client issue 156

Add workaround for [1] by building smee-client from a fork with the fix [2].
[1] https://github.com/probot/smee-client/issues/156
[2] https://github.com/probot/smee-client/pull/162

How to retest a PR or trigger a specific build:

* a pull request please add comment: Jenkins retest this

This is a workaround which needs to be removed as soon as https://github.com/probot/smee-client/pull/162 is merged and a new smee-client released.
Tested on Jenkins.


Update sbt-github-actions to 0.14.0

Updates com.codecommit:sbt-github-actions from 0.12.0 to 0.14.0.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.codecommit", artifactId = "sbt-github-actions" } ]

labels: sbt-plugin-update, early-semver-major, semver-spec-minor

Superseded by #87.


Cannot Access "mask" parameters?

I wanted to use the keepCharPositions prop for the MaskedInput component but I cant figure out how to get the prop down to the component or if it has not been exposed by the DateTextField component yet.
The addtional props could be accepted here: https://github.com/dmtrKovalenko/material-ui-pickers/blob/c02a0f2f68a3c463b3b271378dd80e522363bc72/lib/src/_shared/DateTextField.jsx#L298
or should the props for mask be spread in here?: https://github.com/dmtrKovalenko/material-ui-pickers/blob/c02a0f2f68a3c463b3b271378dd80e522363bc72/lib/src/_shared/DateTextField.jsx#L330
mask documentation: https://github.com/text-mask/text-mask/blob/master/componentDocumentation.md#readme

This method worked for me:
<DatePicker
    ...
    InputProps={{
        inputProps: {
            mask: ...,
            keepCharPositions: true,
        }
    }}
    ...
/>

That mostly works as a workaround, it overrides the localInputProps.inputProps completely which does some checking of keyboard input:
inputProps: {
mask: !keyboard ? null : mask,
readOnly: !keyboard,
},
but it should work for my use case, thank you.

This no longer works with @material-ui/pickers 3.1.0.
For example, in the following code keepCharPositions does not take effect:
    <KeyboardDatePicker
      autoOk={false}
      variant="inline"
      label={"Test"}
      format={"dd/mm/yyyy"}
      inputValue={"12/12/1900"}
      value={null}
      InputAdornmentProps={{ position: "end" }}
      placeholder={"__/__/____"}
      onChange={(_date, value) => {
        console.log(value);
      }}
      InputProps={{
        inputProps: {
          keepCharPositions: true
        }
      }}
    />


Add TestCoin helper class

Similar to the TestMessage helper class, it might be worth having one for coins as well.
We could have a static many function which could generate multiple coins.
const coins: Coin[] = TestCoin.many({
  owner: '0x09c0b2d1a486c439a87bcba6b46a7a1a23f3897cc83a94521a96da5c23bc58db'
}, 4);

May I try to solve this Issue?

Hey @crStiv 👋🏼
Go ahead - let us know if you need anything :)

import { Coin } from '../types';
import { randomBytes } from 'crypto';
export class TestCoin {
/**

Creates a single test coin with given parameters
*/
static create(params: Partial = {}): Coin {
return {
id: randomBytes(32).toString('hex'),
owner: randomBytes(32).toString('hex'),
amount: '1000000000000000000', // 1 ETH by default
...params
};
}

/**

Generates an array of test coins
@param params - Parameters for all generated coins
@param count - Number of coins to generate
*/
static many(params: Partial = {}, count: number): Coin[] {
return Array.from({ length: count }, () => TestCoin.create(params));
}
}

does this one helps in any shape or form, or did I go into the wrong direction?

@crStiv feel free to open a draft PR with this implementation. It is easier for the team to review and collaborate


Some Nix wrappers are not signal-safe

For those syscalls that are signal-safe, their Nix wrappers may not be.
For example, stat(2) is signal-safe, its Nix wrapper uses the NixPath trait, which will allocate if the passed argument has a length greater than MAX_STACK_ALLOCATION, and allocation is not signal-safe, making the wrapper signal-unsafe.
I kinda think we should take a look at those functions that are asked to be signal-safe by the standard, and check if the corresponding Nix wrappers are safe or not, if not, then we should document it so that our users can be aware.

Tried this today, and I am not going to finish this because:

Nix wrappers use std types, and we have no guarantee of signal safety there as this concept is for C, doesn't really apply to the Rust stuff.
It might not be worth to do it as well. When using signal handlers, the only thing one might want to use is libc::write(2), like ctrlc and tokio does,  as this is definitely safe. Trying other things that are in the white list may not be worthwhile.


Chart Repositories are not showing up on Rancher v2.5-head

Rancher Server Setup

Rancher version:v2.5-head (6ff6d08)
Installation option (Docker install/Helm Chart): Docker

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc):

Proxy/Cert Details:Selfsigned

Information about the Cluster

Kubernetes version:v1.20.13-rancher1-1
Cluster Type (Local/Downstream): Downstream 1CP, 1 ETCD, 2 Worker nodes

Describe the bug

Chart Repositories are not showing up on Rancher v2.5-head
To Reproduce

Create a downstream AWS node driver cluster with 2 Worker, 1 ETCD, 1 CP
Result
Navigate to Apps and Market Place of Downstream Cluster ---> Chart Repositories ---> We don't see any chart repositories listed.
If we try to create chart repositories manually, the chart repos remains in "In Progress" state.
Rancher doesn't show any error in log when we add chart repositories manually.
Expected Result

Pre-configured Partners and Rancher chart repositories are listed and in Active state.
We should be able to create new chart repositories.

Screenshots
Rancher doesn't show any error in log when we added chart repositories manually.

Validated the issue again. Results are as follows.
On rancher v2.5-head

Chart repos are visible on local cluster.
Chart repos are not visible on downstream cluster and custom cluster.

On rancher v2.6.2 and v2.6-head

Chart repos are visible on both local and downstream cluster.

This problem doesn't seems to be related to downtime for chart repos. Need to explore the bug/issue in detail.

PASS Charts are back as of 2.5-head Commit ID 9dab145

created downstream cluster
clicked 'explore'
clicked 'Apps & Marketplace'

Charts are available.
Installed apps are correctly showing 3
Chart repositories created (2)
Successfully installed Logging v2 for a smoke test

Reopening to test few more scenarios around hosted Rancher

2.5-head Hosted Rancher managing 2.5-head downstream Rancher
Hosted Rancher upgraded to 2.5-head still can manage 2.5.11 downstream Rancher
Hosted Rancher at 2.5.11 can still manage a downstream Rancher upgraded to 2.5-head
Hosted Rancher at 2.5.11 can successfully add and manage a 2.5-head downstream Rancher

Could not verify the hosted rancher scenarios as rancher-v3_ha_deploy jenkins job is getting stuck. It did not complete even after running for an hour.
Validation steps:

Created k3s ha setup using rancher_v3_create_k3s_ha_cluster jenkins job.
Encoded the kubeconfig to base64
Passed the encoded kubeconfig in RANCHER_HA_KUBECONFIG parameter in rancher-v3_ha_deploy jenkins job and it's getting stuck with below logs:

13:23:03.343  run cmd: 	rke -v | cut -d " " -f 3
13:23:03.343  return code: 	0
13:23:03.343  RKE VERSION: v1.2.14
13:23:03.343  run cmd: 	export KUBECONFIG=/src/rancher-validation/tests/v3_api/resource/kube_config_cluster-ha-filled.yml && kubectl version --short | grep -i server | cut -d " " -f 3
13:23:03.343  return code: 	0
13:23:03.343  KUBERNETES VERSION: v1.21.7+k3s1
13:23:03.343  run cmd: 	export KUBECONFIG=/src/rancher-validation/tests/v3_api/resource/kube_config_cluster-ha-filled.yml && kubectl -n ingress-nginx rollout status ds/nginx-ingress-controller
13:23:03.359  return code: 	1
13:23:03.359  output: 	b'Error from server (NotFound): namespaces "ingress-nginx" not found\n'
13:23:03.360  run cmd: 	export KUBECONFIG=/src/rancher-validation/tests/v3_api/resource/kube_config_cluster-ha-filled.yml && kubectl -n ingress-nginx wait --for=condition=complete job/ingress-nginx-admission-create
13:23:03.360  return code: 	1
13:23:03.360  output: 	b'Error from server (NotFound): namespaces "ingress-nginx" not found\n'

On 2.5.12-rc1, verified the following
Deploy Hosted Rancher on 2.5.12-rc1 and Tenant rancher on 2.5.12-rc2

Chart repositories are available on Tenant Rancher cluster and on Downstream clusters on Tenant rancher servers
Was able to deploy Monitoring v1 on Tenant Rancher and Downstream cluster on Tenant rancher. And deployed CIS v2 on both these clusters
Deployed monitoring v2 on local cluster of Hosted Rancher.

Hosted Rancher upgraded to 2.5-head still can manage 2.5.11 downstream Rancher

Created k3s v1.20.13+k3s1 HA cluster and deployed a rancher 2.5.11 on it.
Imported a k3s HA cluster on k8s version v1.20.13+k3s1 and deployed rancher 2.5.11 on it.
Deployed a downstream cluster on tenant rancher.
Installed monitoring v2 on the local and tenant clusters and downstream cluster.

validated the monitoring metrics.

Upgrade Hosted rancher to v2.5.12-rc1
Validated the monitoring metrics. Metrics looks good.
Validated if chart repo is accessible.
Deployed downstream cluster on tenant rancher again and made sure chart repo is accessible.

Deployed a hosted rancher on 2.5.11 - k3s v1.20.13+k3s1
Imported a k3s HA cluster on k8s version v1.20.13+k3s1 and deploy rancher 2.5.11 on it --> Tenant rancher
Deployed a downstream cluster on tenant rancher
Installed monitoring v2 on the local and tenant clusters and downstream cluster
Upgrade Hosted rancher (main rancher server) to 2.5.12-rc1 (using the kubeconfig from Jenkins job)

Results:
On host rancher (rancher v2.5.11)

Monitoring looks good on local cluster.
However, on imported cluster the monitoring is not stable. The monitoring spiral chart is not visible.

On host rancher upgraded to v2.5.12-rc1

The "Monitoring API is not ready" error shows up after v2.5.12-rc1 upgrade on local cluster.
The monitoring on imported cluster is unstable. Either "Monitoring API is not ready" error shows or the monitoring graphs are not visible although all the pods are in active.

On tenant rancher

The monitoring on local cluster is unstable. Either "Monitoring API is not ready" error shows or the monitoring graphs are not visible although all the pods are in active.
The monitoring on downstream looks good.

Tracking monitoring issue in another GH ticket. Closing this one as all validations are complete.


keras Batch Norm Issure

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Centos7
TensorFlow version and how it was installed (source or binary): 2.8.3
TensorFlow-Recommenders-Addons version and how it was installed (source or binary): 0.6.0
Python version: 3.9
Is GPU used? (yes/no): no

Describe the bug
A clear and concise description of what the bug is.
In predict_step, if I set training=False, I would get a very low auc. It seems that, the params of BN in keras were not saved during model save operation.
Code to reproduce the issue
## evaluate
y_pred_ctr, bias = self(features, training=False)
## load model
self.model.load_weights(os.path.join(self.model_dir, 'weights'))
## save model
save_options = tf.saved_model.SaveOptions(namespace_whitelist=['TFRA'])
self.model.save_weights(os.path.join(self.model_dir, 'weights'), options=save_options)

Provide a reproducible test case that is the bare minimum necessary to generate the problem.
Other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

@sunshinenum This issue is solved for the time being, I will close this issue. Turn it back on if necessary.


What is the best way to enable bash completion on nix-on-droid?

I tried to setup programs.bash.enableCompletion = true; but the option isn't available (i guess it's a nixos thing, not nix).
Which way would you guys advise me to enable these? Am I missing something?

With a home-manager option: https://nix-community.github.io/home-manager/options.xhtml#opt-programs.bash.enableCompletion
This has to go into home-manager section of the config. Non-flakes: default config should have instructions on how to enable it. Flakes: there's a template in this repository with an example of how to enable it.

With a home-manager option: https://nix-community.github.io/home-manager/options.xhtml#opt-programs.bash.enableCompletion This has to go into home-manager section of the config. Non-flakes: default config should have instructions on how to enable it. Flakes: there's a template in this repository with an example of how to enable it.

i got some issues with home manager, i tried to enable it but it says that the nix-on-droid flake i'm using, it seems my environment is conflicting or something, the error is weird on it's own, it says a package is conflicting, and that i should run nix-env -q when i do so, it prints nix-on-droid-path and that's about it... what could that be linked to ?
(My home manager config only has a bash.nix file imported, with the lines available in the link you posted above. did that happened to you as well ? Am i missing something here ?)

Hard to say with neither the config you're using (one you've linked to does not have a bash.nix) nor the error message (retelling error messages isn't a great idea overall). Sounds like you have a package installed with several methods at once. Also, using nix-env is pretty much never a good idea.

Hard to say with neither the config you're using (one you've linked to does not have a bash.nix) nor the error message (retelling error messages isn't a great idea overall). Sounds like you have a package installed with several methods at once. Also, using nix-env is pretty much never a good idea.

My apologies, i completely forgot to link the files.
here is my home-manager repo:
https://github.com/SpidFightFR/home-manager-android

this one contains the bash.nix.

This one doesn't define a nix-on-droid configuration (see template for the example), so I'm not sure how are you applying it. Please share the full reproducer. If you have installed home-manager separately (1st set of packages) and are applying it on top of a regular environment (2nd set of packages) where you've also installed something using nix-env (3rd set of packages), then I'm not very surprised you've got some conflicts.

This one doesn't define a nix-on-droid configuration (see template for the example), so I'm not sure how are you applying it. Please share the full reproducer. If you have installed home-manager separately (1st set of packages) and are applying it on top of a regular environment (2nd set of packages) where you've also installed something using nix-env (3rd set of packages), then I'm not very surprised you've got some conflicts.

ngl I think my whole thing is basically trash... Went in too many directions at once, it's a huge mess.
I'll try to refactor the home-mgr branch of my nix-on-droid flake, in order to include home manager, hopefully it will work better.
I'll be right back. thanks for your help

hey again @t184256, sorry for the ping. I made a slight refactor of the home-mgr branch, leading to the deletion of my home-manager repo (useless after what i did on my main nix-on-droid config repo).
After running nix-on-droid switch --flake . it seems like it also applied the home-manager config, is it the case ?

Yeah, that was the idea, one switch for everything.

Yeah, that was the idea, one switch for everything.

Alright, welp imma play a bit with that and see what i can do with it. closing this issue. Thank you man, i appreciate your help (note: i started to learn about flakes 4 days ago lol, i'm still a huge noob with those) :sweat_smile:


Grid: Responsive styles incorrectly applied on large screens

Example:
https://osuresearch.github.io/ui/docs/iframe.html?args=&id=layout-grid--responsive&viewMode=story
Stretch it out to full width - it ends up using the sm style instead of the md.

It's a useScreenSize hook issue. Didn't account for when the screen size is greater than xxl


elasticsearch-ruby downgraded from 5.0.1 to 1.1.2

Elasticsearch: 5.1.1
rails: 5.0.1
elasticsearch-rails: head

s.add_dependency "elasticsearch",       '> 0.4'

s.add_dependency "elasticsearch",       '~> 1.1'

After this commit these gems was downgraded:
elasticsearch-api 1.1.2 (was 5.0.1)
elasticsearch 1.1.2 (was 5.0.1)
elasticsearch-transport 1.1.2 (was 5.0.1)
Readme says elasticsearch-ruby 1.1 gem is compatible only Ealsticsearch 1.x.
How can i use this gem with Ealsticsearch 5.x?

I've recently did some major re-shuffling of versions and fought with dependency hell on Travis, so here might be some side effect.
Can you post more details, as the relevant portion of your Gemfile (or the whole Gemfile) and what change resulted in the problem?

gemfile:
gem 'elasticsearch-model', git: 'https://github.com/elasticsearch/elasticsearch-rails.git'
gem 'elasticsearch-rails', git: 'https://github.com/elasticsearch/elasticsearch-rails.git'
I just ran bundle update.
This commit results the change:
https://github.com/elastic/elasticsearch-rails/commit/db2cd1cccecea678457f90142c0d00240799fb19
-s.add_dependency "elasticsearch", '> 0.4'
+s.add_dependency "elasticsearch", '~> 1.1'

Before elasticsearch was resolved 5.0.1 (because of: '> 0.4')
Now elasticsearch is resolved: 1.1.2 (beacouse of:  '~> 1.1')
Why is this dependency change?

Ah, right, thanks for the details, now I remember.
Yes, this is (unfortunately) expected based on the commit. I'll go and relax the requirement, there's (unfortunately) not a better fix at the moment.
Regarding the reason for the change, it was done in the middle of Travis fixing, so my line of thinking probably went along something like "the Rails integration hasn't been properly upgraded in all corners for Elasticsearch 5.x, so let's pin it to 1.x lineage". Not my brightest moment I think :)

I've just pushed commits with the relaxed dependency specification, can you please check?

Thanx, now installs latest elasticsearch-ruby gem.

@karmi it's normal that elasticsearch-model 2.x depends on elasticsearch 1.x? https://github.com/elastic/elasticsearch-rails/blob/2.x/elasticsearch-model/elasticsearch-model.gemspec#L26

@alepore, it isn't :) There's a PR at https://github.com/elastic/elasticsearch-rails/pull/702 which I'm gonna merge soon. These are some unfortunate side effects of making the support matrix a bit predictable in both the Ruby client and Rails integration...


RHP across the app cannot be closed by ESC key

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.44-0
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause Internal Team
Action Performed:

Go to staging.new.expensify.com
Open any RHP (via FAB > Submit expense, or open Find page).
Press ESC.

Expected Result:
RHP can be closed by ESC key.
Actual Result:
RHP cannot be closed by ESC key.
Workaround:
Unknown
Platforms:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/5b756db3-5732-4f37-93b9-7aa88895bff8

View all open jobs on GitHub

I reproduced on staging v9.0.44-0 and not on prod v9.0.43-6

Confirmed reverting https://github.com/Expensify/App/pull/49457 fixes the issue. Should we just CP https://github.com/Expensify/App/pull/50143?

Yea, I requested the CP

CP is running

Fixed in v9.0.44-2
https://github.com/user-attachments/assets/a55675d6-adab-4494-b794-32e3ecfaebd5


nixos/neovim: fix remote plugin manifest generation

Description of changes
Stops using ex mode when running neovim for remote plugin manifest generation, since that leads to errors in more recent neovim versions with various plugins.
Relevant discussion in and fix for #189804

Things done
Fix personally tested for vim-polyglot and with

currently used in my configuration

nvim-lspconfig
vim-automkdir
vim-vsnip
vim-vsnip-integ
nvim-cmp
cmp-nvim-lsp
cmp-buffer
cmp-path
cmp-calc
cmp-spell
cmp-emoji
cmp-treesitter
cmp-latex-symbols
cmp-omni
cmp-vsnip
vim-grammarous
vim-matchup
NeoSolarized
nerdtree
nerdtree-git-plugin
vim-commentary
camelcasemotion
vim-closetag
vim-polyglot
vim-surround
vim-indent-guides
gruvbox
vim-repeat
vim-airline
rainbow
vim-devicons
nvim-web-devicons
vim-shellcheck
editorconfig-vim
plantuml-syntax
nvim-treesitter
vim-gnupg
base16-vim
base16-vim-airline-themes
vim-ledger
plenary-nvim
telescope-nvim
telescope-fzf-native-nvim
gitsigns-nvim
neorg
trouble-nvim
friendly-snippets

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Fix works in my neovim-flake

Have you a better explanation/the commit responsible for that ? -E doesnt look needed here but still it would be nice to understand. Isn't that a vim-polyglot change ?

Fix works in my neovim-flake

What does that mean ? nightly neovim ? neovim ?

AutoCommands that have the vim special variable "afile" are the ones that are broken like vim-polyglot and neogit when generating the rplugin.vim
Afile is replace with the file name of the current buffer when running the autocommand so running it in ex mode there is nothing to replace it with.
The neovim commit that broke this (references in the issue) was a refactor in this area. I am not fully confident in my understanding of why this is happening now, but the commit looks right so I believe this needs fixed in nixpkgs.
So if the -E command option is not needed I think that is the best solution. This is not just a problem in one plugin but any plugin using afile in autocommands and the neovim conmit that broke it looks correct for neovim

what's blocking this merge? @teto @jonringer

could you try a rebase to fix the ofborg-eval job ?

Done and seems like it did fix the eval job :)


Need help understanding

Hi Guys,
Thanks for the valuable contributions and codes. There are really very few helpful sources on lightstreamer in IG.
I hope someone can be kind enough to guide me on the codes. I am new to python, pandas, kivy, etc. I have coded my kivy GUI, REST for login, dealing, etc. But I am really very lost when it comes to lightstreamer. Hope someone can help with my queries.
I have look at:
https://github.com/ig-python/ig-markets-api-python-library/blob/master/trading_ig/lightstreamer.py
https://github.com/ig-python/ig-markets-api-python-library/blob/master/trading_ig/stream.py
https://github.com/ig-python/ig-markets-api-python-library/blob/master/sample/stream_ig.py
Would like to ask a few questions.

Why are there 3 different codes on steaming, what's the difference between the 3?

Do I import them as library or do I copy paste the codes in my GUI.

on lightstreamer.py, below indicates 12 items. does this mean that I can only have 12 subscriptions to IG where IG allowed us 40 concurrent subscriptions? Do I need to change this?

    # Making a new Subscription in MERGE mode
    subscription = Subscription(
        mode="MERGE",
        items=["item1", "item2", "item3", "item4", "item5", "item6", "item7", "item8", "item9", "item10", "item11", "item12",
        ],
        fields=["stock_name", "last_price", "time", "bid", "ask"],
        adapter="QUOTE_ADAPTER",
    )

Can I have multiple subscriptions from different items different fields in one line of code?

If can, does IG treat it as many subscriptions or treat it as one subcriptions?

Let's say if I am keen in the below data, how do I add it?
IX.D.NASDAQ.IFG.IP - OFFER, Latest 5 min candle OFR_HIGH, the previous latest 5 min candle OFR_HIGH (which is the second candle)
IX.D.SPTRD.IFG.IP - OFFER, Latest 5 min candle OFR_HIGH, the previous latest 5 min candle OFR_HIGH (which is the second candle)
Account Equity

I dont really understand lightstreamer fully, can all these different data item and field can be in one subscription? or I need to code multiple subscription.
Hope someone can help me with the questions.
Thank you.
Sincerely
Shaun

The three codes shown are related to each other. The first one is a basic access library; the second one uses the first one to setup a connection; the third one uses the previous two to setup a connection and perform a subscription.

The subscription shown in the first code is just a sample subscription for Lightstreamer's demo installation and should be disregarded.

I have no answer for more specific questions. In general terms, Lightstreamer interface allows you to perform multiple subscriptions, with different choices of items and fields, within a single connection. You can collect multiple items in the same subscription provided that the requested fields are the same.

Hi Dario,
Thanks for the guidance, I managed to figure it out. Seems like all the class and methods in ightstreamer.py are valid.
Just that to make it work in IG, need to change the way how we connect and subscribe. I roughly know how to connect. Just need to play around around with the subscription as I'm subscribing to quite a few items.
Thank you for the help! :)


Remove class variables

In the client class (and some other classes) I have seen variables defined in the class body. Those are class variables, and a client instance per se should not share any variables with another client instance. This would, for example, be really bad for APIs security-wise).
class Foo:
    x: int = 1    # class variable

class Bar:
    def __init__():
        x = 1    # instance variable

You don't use the class variables as you define instance variables in the init shadowing the class variables.
However, this still feels a bit insecure to me, leaving room for error.
So, I'd like to suggest two things:

Remove all class variables that should not be shared between client instances (e.g. AuthStore)
Check for certain class variables if they are defined and do not initialize them with default value. For example, setting Client.base_url="..." would be neat, but is currently shadowed by instance variable.

Further Explanation: https://stackoverflow.com/a/43921843

looks like you have a valid point.
as you already mention, more or less all the static variables are "shadowed" already during the object init. The class variables do not hold any value in any scenario. I am also not really aware of a use-case of this library where this could even theoretically be a security issue.
maybe @vaphes can comment on why the static variables were defined in the first place. If i would make a guess this originally may have been done for type hinting purposes. (there are obviously other/better ways to do the type hinting directly on the instance variables.)
@simon-lund  feel free to propose a Pull Request on this issue if you have some time to work on this

@simon-lund I agree, this was probably done when I was translating the pocketbase js lib to python and went I bit braindead on the perks of each lang.
If you propose a pull request I will promptly verify it.
As always @m29h thx a lot for the work on this lib.


group query causes "Can't find materialized set"

EdgeDB Version: 3.3+d5734dd
EdgeDB CLI Version: 3.5.0+e1ad387
OS Version: macOS 13.5.2

Steps to Reproduce:

Apply the schema below
Run the query specified below

Expected: result or a user-fixable error
Observed: error: Can't find materialized set ns~11@ns~51@ns~52@ns~53@ns~54@@(__derived__::submissions@w~3).>elements[IS default::Message]

Schema:
module default {
  scalar type MessageType extending enum<amplify>;

  type Message {
    required identity: str;
    required type: MessageType;
    required href: str;

    required title: str;
    required timestamp: int64;

    required signer: str;
    required signature: str {
      constraint exclusive;
    }

    constraint exclusive on ((.identity, .href, .type));
    index on ((.href, .timestamp));
  }
}

Query:
with
  groups := (
    group Message by .href
  ),
  submissions := (
    select groups {
      id,
      keyMessage := (select .elements order by .timestamp asc limit 1),
      points := count(.elements),
      upvoters := array_agg(.elements.identity),
      minTimestamp := min(.elements.timestamp)
    }
  )
select submissions {
  id,
  keyMessage: {
    id,
    href,
    title,
    identity,
    timestamp,
    signature,
  },
  points,
  upvoters,
  minTimestamp
}
order by .minTimestamp desc

Related to https://github.com/edgedb/edgedb/issues/6019


Re adding the preview of modified pictures

Is your feature request related to a problem? Please describe.
I recently upgraded to 2.6.0. I'm not a fan of the new UI placements, which I find less intuitive than before.
However my problem isn't here. Before, when I wanted to rescale a photo, I could see live what the modified photo would look like, as a preview.
It doesn't seem to work anymore.
Also it looks like the button to enable "Ratio keeping" for rescaling a picture isn't even there anymore.
The solution?
Enable again live preview of modified pictures.

Live preview is here, isn't it? Could you check on the latest pre release please?

Ratio keeping is flexible resize


Unable to create UDP and TCP sockets

I'm trying to create two listening sockets, one UDP and one TCP, with the following code:
    let mut udp_rx_payload = [0; 128];
    let mut udp_rx_metadata = [PacketMetadata::EMPTY; 1];
    let mut udp_tx_payload = [0; 128];
    let mut udp_tx_metadata = [PacketMetadata::EMPTY; 1];
    let udp_socket = UdpSocket::new(
        UdpSocketBuffer::new(udp_rx_metadata.as_mut(), udp_rx_payload.as_mut()),
        UdpSocketBuffer::new(udp_tx_metadata.as_mut(), udp_tx_payload.as_mut()),
    );

    let mut tcp_rx_payload = [0; 128];
    let mut tcp_tx_payload = [0; 128];
    let tcp_socket = TcpSocket::new(
        TcpSocketBuffer::new(tcp_rx_payload.as_mut()),
        TcpSocketBuffer::new(tcp_tx_payload.as_mut()),
    );

    let mut sockets = [None, None];
    let mut socket_set = SocketSet::new(sockets.as_mut());
    let udp_handle = socket_set.add(udp_socket);
    let tcp_handle = socket_set.add(tcp_socket);

When I try to build this, I get the following error:
error[E0597]: `udp_rx_payload` does not live long enough
   --> src/main.rs:117:56
    |
117 |         UdpSocketBuffer::new(udp_rx_metadata.as_mut(), udp_rx_payload.as_mut()),
    |                                                        ^^^^^^^^^^^^^^ borrowed value does not live long enough
...
167 | }
    | - borrowed value only lives until here
    |
    = note: borrowed value must be valid for the static lifetime...

error[E0597]: `udp_tx_payload` does not live long enough
   --> src/main.rs:118:56
    |
118 |         UdpSocketBuffer::new(udp_tx_metadata.as_mut(), udp_tx_payload.as_mut()),
    |                                                        ^^^^^^^^^^^^^^ borrowed value does not live long enough
...
167 | }
    | - borrowed value only lives until here
    |
    = note: borrowed value must be valid for the static lifetime...

If I comment out either of the calls to socket_set.add, it builds and runs.
I'm using rustc 1.28.0-nightly (c2d46037f 2018-05-24).

The lifetimes of all sockets unify with each other, so you need to group them like this:
    let mut udp_rx_payload = [0; 128];
    let mut udp_tx_payload = [0; 128];
    let mut tcp_rx_payload = [0; 128];
    let mut tcp_tx_payload = [0; 128];
    let mut udp_tx_metadata = [PacketMetadata::EMPTY; 1];
    let mut udp_rx_metadata = [PacketMetadata::EMPTY; 1];
    let udp_socket = UdpSocket::new(
        UdpSocketBuffer::new(udp_rx_metadata.as_mut(), udp_rx_payload.as_mut()),
        UdpSocketBuffer::new(udp_tx_metadata.as_mut(), udp_tx_payload.as_mut()),
    );
    let tcp_socket = TcpSocket::new(
        TcpSocketBuffer::new(tcp_rx_payload.as_mut()),
        TcpSocketBuffer::new(tcp_tx_payload.as_mut()),
    );

    let mut sockets = [None, None];
    let mut socket_set = SocketSet::new(sockets.as_mut());
    let udp_handle = socket_set.add(udp_socket);
    let tcp_handle = socket_set.add(tcp_socket);

cf. #48

That gives me the same error as before:
error[E0597]: `udp_rx_payload` does not live long enough
   --> src/main.rs:119:56
    |
119 |         UdpSocketBuffer::new(udp_rx_metadata.as_mut(), udp_rx_payload.as_mut()),
    |                                                        ^^^^^^^^^^^^^^ borrowed value does not live long enough
...
166 | }
    | - borrowed value only lives until here
    |
    = note: borrowed value must be valid for the static lifetime...

error[E0597]: `udp_tx_payload` does not live long enough
   --> src/main.rs:120:56
    |
120 |         UdpSocketBuffer::new(udp_tx_metadata.as_mut(), udp_tx_payload.as_mut()),
    |                                                        ^^^^^^^^^^^^^^ borrowed value does not live long enough
...
166 | }
    | - borrowed value only lives until here
    |
    = note: borrowed value must be valid for the static lifetime...

Is there something in the surrounding code that I need to check? All of this code exists in main.

Oh sorry, I didn't go far enough. You need...
    let mut udp_rx_payload = [0; 128];
    let mut udp_tx_payload = [0; 128];
    let mut tcp_rx_payload = [0; 128];
    let mut tcp_tx_payload = [0; 128];
    let mut udp_tx_metadata = [PacketMetadata::EMPTY; 1];
    let mut udp_rx_metadata = [PacketMetadata::EMPTY; 1];
    let udp_rx_buffer = UdpSocketBuffer::new(udp_rx_metadata.as_mut(), udp_rx_payload.as_mut());
    let udp_tx_buffer = UdpSocketBuffer::new(udp_tx_metadata.as_mut(), udp_tx_payload.as_mut());
    let tcp_rx_buffer = TcpSocketBuffer::new(tcp_rx_metadata.as_mut(), tcp_rx_payload.as_mut());
    let tcp_tx_buffer = TcpSocketBuffer::new(tcp_tx_metadata.as_mut(), tcp_tx_payload.as_mut());
    let udp_socket = UdpSocket::new(udp_rx_buffer, udp_tx_buffer);
    let tcp_socket = TcpSocket::new(tcp_rx_buffer, tcp_tx_buffer);

    let mut sockets = [None, None];
    let mut socket_set = SocketSet::new(sockets.as_mut());
    let udp_handle = socket_set.add(udp_socket);
    let tcp_handle = socket_set.add(tcp_socket);

(There is a small typo above. TcpSocketBuffer::new doesn't need metadata). I still get the same error :(

Can you post your project somewhere? In any case, here's a working example: https://github.com/m-labs/ionpak/blob/master/firmware/src/main.rs#L158-L194.

I just made it public. Here is the code in question (without the suggested changes): https://github.com/crawford/PoE/blob/95d11340f3e2025f3930e5bd4fa4108acaf96968/firmware/src/main.rs#L112.

@crawford Hmm, I can compile your code with the nightly compiler. (Maybe thanks to the NLL?)

@ProgVal Did you uncomment line 131?

@whitequark I'm now getting an eerily similar error after (refactoring my Device implementation](https://github.com/crawford/PoE/blob/78817d4dbcb2d0a1bc981238a184996b5029b3c2/firmware/src/main.rs#L109). This code fails with the following error message:
error[E0597]: `tx_buffer` does not live long enough
   --> src/main.rs:111:18
    |
111 |             &mut tx_buffer,
    |                  ^^^^^^^^^ borrowed value does not live long enough
...
178 | }
    | - `tx_buffer` dropped here while still borrowed
    |
    = note: values in a scope are dropped in the opposite order they are created

I wonder if both this failure and the original actually stem from the type definition of Interface and InterfaceBuilder. Both of these structs dictate that DeviceT is a Device of any lifetime (including 'static), but my Device does not implement 'static (unlike the Device in IonPak). I've been trying to modify smoltcp to lift that restriction, but I haven't been able to satisfy the borrow checker yet.

Does it change anything if you move rx_buffer/tx_buffer above the creation of neighbor_cache and ip_addrs?

@birkenfeld Unfortunately, no.

This has been fixed by https://github.com/m-labs/smoltcp/pull/304.


empty Result

when i run the search result is empty and
i get this error on wrapper.ErrorReceived:
Results View = Expanding the Results View will enumerate the IEnumerable
Method = {Void b__2(Nager.AmazonProductAdvertising.Model.AmazonErrorResponse)}

:) you must expand the list with the errors, the error is behind this

I expanded alot it gave me the same error. Maybe im expanding wrong. Which one should i expand?

The AmazonErrorResponse.

No :)
Please add your code example

@tinohager Hello Tino.im using your code.
`var authentication = new AmazonAuthentication();
authentication.AccessKey = "accesskey";
authentication.SecretKey = "secretkey";
var wrapper = new AmazonWrapper(authentication, AmazonEndpoint.US, "nager-20");
var result = wrapper.Lookup("B00BYPW00I");`

@tinohager would you please Remote and see what happend?

@tinohager Hello?


Create histogram for numerical and Categorical in Filter Dialog

Current Status:

Let's discuss the filter histograms in our meeting today.

Current State:


fix(language-core): correctly infer union props to options

fix vuejs/core#12012 , fix vuejs/core#12110

Thanks, I've tested your patch and it fixed my issue.

@KazariEX I think this would be a great addition. Currently there are typescript errors when you do the following:
<script setup lang="ts">
import { useCssModule } from 'vue';

const styles = useCssModule();

defineProps<
  | {
      option: 'a';
      aValue: string;
    }
  | {
      option: 'b';
      bValue: number;
    }
>();
</script>

<template>
  <div :class="styles.example">Option: {{ option }}</div>
</template>

<style lang="css" module>
.example {
  color: red;
}
</style>

As soon as you add the style module tag, vue and typescript are unable to properly see props and things like imported components. I tested your code locally and it seemed to have made the typescript errors in the template tag go away immediately. Do you think it makes sense to reconsider this PR?

According to Johnson's suggestion, a better approach is to place union types into generics to skip redundant type inferring and directly use the original types, which avoids injecting too much difficult to maintain code.

There are many issues with that approach. I started writing a comment about that but then I stumbled upon an even bigger bug regarding union props and unfortunately I still have to file it.

I did try the generics approach as well, but that does cause other issues for me as well. I'll try to create a minimal component reproduction of the errors I'm encountering with it and post it here.


Icon over crowding in Bot menu

The error icons that appear on Bot navigation hide the more icon.

Version

Browser

[ ] Electron distribution

OS

[ ] macOS

To Reproduce
Steps to reproduce the behavior:

Add a new skill to the bot project
Choose a skill with Luis
See the error icons appear in front of the Skill name

Expected behavior
I do not expect 2 error icons to appear. Showing me just one icon is enough to indicate that I need to take more action to activate this skill.
I also expect core 'actions' of the menu to be visible on hover.

Looks like this has been fixed:

Name truncates to make room for error/warning icon and ... (more button) remains visible at rest when this happens.


Crash with Witcher Horses Expansion

Describe the bug
The witcher horse expansion CTDs if this mod is enabled with xpsme lite or full.
To Reproduce
Go to the storm altar which is next to Shrine of Akatosh in falkreath hold
Expected behavior
The game continues to run as it does without HDT-SMP.
Desktop (please complete the following information):
Windows 10
** FSMP**

Installed version
CUDA: No_CUDA
AVX: AVX2

SKSE

installed version
2.2.3

Skyrim
1.6.640
Required files
hdtSMP64.log
crash-2023-04-05-01-18-37.log
configs.txt

I would like to mention the debug version of 1.50.4 doesn't load
loading plugin "HDT-SMP Force Fields"
registering plugin listener for SKSE at 35 of 117
plugin HDT-SMP Force Fields.dll (00000001 HDT-SMP Force Fields 00090000) loaded correctly (handle 35)
loading plugin "hdtSMP64"
plugin hdtSMP64.dll (00000001 hdtSMP64 00019A2C) disabled, fatal error occurred while loading plugin 0 (handle 36)

This crash was fixed on the mods side(still probably should fail gracefully if it meets a similar issue)
I found the cause. Among the nodes attached to Thunder's horn, EnbParticleLight02 was the problem. Just delete EnbParticleLight02 from the node and the crash won't happen.I'm glad it's a problem that can be easily solved without changing the skeleton.

Thanks. Since it's a particle light node, it's probably a non standard node so may be missing some data expected for physics.


Increment version for synapse releases

Increment version for synapse releases

Can one of the admins verify this patch?

Closing, as this version has been manually updated.


how to use formik and react-simple-keyboard together

I am using formik to handle form my react project and i need to use react-simple-keyboard. How can I use both libraries together? Any idea or demo will help. Thank you

Hello @darda-ergo,
That's probably a question you'd have to ask to the mantainers of Formik. I'm personally not quite familiar with it.
As far as simple-keyboard is concerned:

It outputs through onKeyPress, onChange and keyboard.getInput().
It takes input through keyboard.setInput() and keyboard.replaceInput()

You would need to investigate whether Formik also provides a way (methods or props) to send in input and receive updated input programmatically, so you can do the syncing. The following would apply to any library you'd like to integrate, not just Formik.
Regards,
Francisco Hodge


Doesn't work on reference.

I will use block reference for todos to keep clean of checkbox (leave with only one checkbox). I found it doesn‘t work on block reference as it didn’t show the confirmation option when I click on the checkbox of block reference.

That's correct. As we rely on the UUID information of the task blocks, it is necessary to take a detour in order to display the confirmation dialog. It is possible to implement processes such as automatically opening it in the right sidebar and then displaying it.

I will include it in the release. In the case of a reference, if changes are made to the original block, I will detect it and assign the DONE property. If you want to display it, you need to either make the block a task without referencing it or embed it using 'embed'.


using inbox.stream() results in erroneus unread message count indicator

Describe the bug
when using inbox.stream() the streamed messages are NOT marked as read (correct), but unfortunately the unread messages counter (on reddit.com) is decreased by one.
To Reproduce
Steps to reproduce the behavior:

go to reddit.com/message/unread
observe the number of messages shown is equal to the count shown in the little letter indicator
use some code that uses inbox.stream()
reload the unread page from above
observe the unread message indicator is now 0, yet unread messages are shown on the page

Expected behavior
inbox.stream() should not change the unread messages count on reddit page
Other info
made a post on r/bugs: https://www.reddit.com/r/bugs/comments/n9re1a/message_indicator_count_of_unread_messages_shows/ because I actually think this is a reddit bug
System Info

OS: archlinux
Python: Python 3.9.4
PRAW Version: 7.2.0

I believe this is controlled by a user setting:

If that checkbox is left unchecked then I don't think the count will decrease upon opening.

I'm going to close the issue assuming that user setting provides the expected behavior. Please follow up with the r/bugs post if that doesn't resolve the issue.

No, that user setting does not resolve the issue. will go to r/bugs now

a Note: this dosn't happen when using inbox.unread(), which is strange to me because it appears from skimming the code that the stream() function essentially just polls the same api call as unread()?

@molecular my mistake. I conflated automatically marking the messages as read as the same as the unread count.
Either way, however, this is an issue on Reddit's end. You should be able to verify this bug via the web interface. If you find a way to fetch the inbox without causing the issue let us know.

Either way, however, this is an issue on Reddit's end.

agreed.

You should be able to verify this bug via the web interface

wouldn't know how to. Everything works fine from the web interface.

Couldn't keep myself from digging in. That stream() function just wraps the unread() call into stream_generator. All that does is poll unread() using exponential backup of some more things I don't quite get (everything with "before" I don't fully understand)
But I just made a discovery: The problem does not occur when I pass exclude_before=True to inbox.stream() function.

Anyway, I just made the following discovery: The problem does not occur when I pass exclude_before=True to inbox.stream() function.

That's fascinating. Perhaps calling the inbox with before: message_id automatically decreased the unread count in the inbox.

That's fascinating. Perhaps calling the inbox with before: message_id automatically decreases the unread count in the inbox on Reddit's end.

that would also match the observation that the decreasing of the count happens at the "end", when stream() for the first time returns a None item. I'm guessing the first call to unread() gets the full unread() list and subsequent calls are passed the before argument (set to attribute of newest received item). Oh damn: yes, and then "someone" (reddit api "unread" endpoint logic probably) thinks it's smart to use the item count from that internal unread call (some db query or whatever) to update the message counter (to "0" in my case). It's speculation, but I'm going with that. Only strange thing is that counter isn't fixed by a simple call to unread() (neither by using anything on reddit.com).

I just produced the bug using just unread() calls (no stream_generator or stream() call), pseudocode:
for item in reddit.inbox.unread():
  latest_fullname = item.fullname

# message counter still > 0

kwargs["params"] = {"before": latest_fullname}
reddit.inbox.unread(**kwargs)

# message counter now falsely 0

this will reset the message counter to 0
sorry about weird passing of kwargs (is it correct?), didn't know how else, not a python guy.


specific libpng version missing ubuntu 24.04.4

Missing lib dependencies for very specific versions cause fluxgym to fail to start training with the following exceptions:

[2024-09-08 12:06:21] [INFO] Running bash "/pinokio/api/fluxgym.git/train.sh"
[2024-09-08 12:06:24] [INFO] The following values were not passed to accelerate launch and had defaults used instead:
[2024-09-08 12:06:24] [INFO] --num_processes was set to a value of 2
[2024-09-08 12:06:24] [INFO] More than one GPU was found, enabling multi-GPU training.
[2024-09-08 12:06:24] [INFO] If this was unintended please pass in --num_processes=1.
[2024-09-08 12:06:24] [INFO] --num_machines was set to a value of 1
[2024-09-08 12:06:24] [INFO] --dynamo_backend was set to a value of 'no'
[2024-09-08 12:06:24] [INFO] To avoid this warning pass in values for each of the problematic parameters or run accelerate config.
[2024-09-08 12:06:26] [INFO] Traceback (most recent call last):
[2024-09-08 12:06:26] [INFO] File "/pinokio/api/fluxgym.git/sd-scripts/flux_train_network.py", line 13, in
[2024-09-08 12:06:26] [INFO] from library import flux_models, flux_train_utils, flux_utils, sd3_train_utils, strategy_base, strategy_flux, train_util
[2024-09-08 12:06:26] [INFO] File "/pinokio/api/fluxgym.git/sd-scripts/library/flux_train_utils.py", line 17, in
[2024-09-08 12:06:26] [INFO] from library import flux_models, flux_utils, strategy_base, train_util
[2024-09-08 12:06:26] [INFO] File "/pinokio/api/fluxgym.git/sd-scripts/library/flux_utils.py", line 12, in
[2024-09-08 12:06:26] [INFO] from library.utils import setup_logging, MemoryEfficientSafeOpen
[2024-09-08 12:06:26] [INFO] File "/pinokio/api/fluxgym.git/sd-scripts/library/utils.py", line 13, in
[2024-09-08 12:06:26] [INFO] import cv2
[2024-09-08 12:06:26] [INFO] File "/pinokio/api/fluxgym.git/env/lib/python3.10/site-packages/cv2/init.py", line 181, in
[2024-09-08 12:06:26] [INFO] bootstrap()
[2024-09-08 12:06:26] [INFO] File "/pinokio/api/fluxgym.git/env/lib/python3.10/site-packages/cv2/init.py", line 153, in bootstrap
[2024-09-08 12:06:26] [INFO] native_module = importlib.import_module("cv2")
[2024-09-08 12:06:26] [INFO] File "/pinokio/bin/miniconda/lib/python3.10/importlib/init.py", line 126, in import_module
[2024-09-08 12:06:26] [INFO] return _bootstrap._gcd_import(name[level:], package, level)
[2024-09-08 12:06:26] [INFO] ImportError: libpng16-1bde1c40.so.16.43.0: cannot open shared object file: No such file or directory
[2024-09-08 12:06:26] [INFO] Traceback (most recent call last):
[2024-09-08 12:06:26] [INFO] File "/pinokio/api/fluxgym.git/sd-scripts/flux_train_network.py", line 13, in
[2024-09-08 12:06:26] [INFO] from library import flux_models, flux_train_utils, flux_utils, sd3_train_utils, strategy_base, strategy_flux, train_util
[2024-09-08 12:06:26] [INFO] File "/pinokio/api/fluxgym.git/sd-scripts/library/flux_train_utils.py", line 17, in
[2024-09-08 12:06:26] [INFO] from library import flux_models, flux_utils, strategy_base, train_util
[2024-09-08 12:06:26] [INFO] File "/pinokio/api/fluxgym.git/sd-scripts/library/flux_utils.py", line 12, in
[2024-09-08 12:06:26] [INFO] from library.utils import setup_logging, MemoryEfficientSafeOpen
[2024-09-08 12:06:26] [INFO] File "/pinokio/api/fluxgym.git/sd-scripts/library/utils.py", line 13, in
[2024-09-08 12:06:26] [INFO] import cv2
[2024-09-08 12:06:26] [INFO] File "/pinokio/api/fluxgym.git/env/lib/python3.10/site-packages/cv2/init.py", line 181, in
[2024-09-08 12:06:26] [INFO] bootstrap()
[2024-09-08 12:06:26] [INFO] File "/pinokio/api/fluxgym.git/env/lib/python3.10/site-packages/cv2/init.py", line 153, in bootstrap
[2024-09-08 12:06:26] [INFO] native_module = importlib.import_module("cv2")
[2024-09-08 12:06:26] [INFO] File "/pinokio/bin/miniconda/lib/python3.10/importlib/init.py", line 126, in import_module
[2024-09-08 12:06:26] [INFO] return _bootstrap._gcd_import(name[level:], package, level)
[2024-09-08 12:06:26] [INFO] ImportError: libpng16-1bde1c40.so.16.43.0: cannot open shared object file: No such file or directory
[2024-09-08 12:06:27] [INFO] [2024-09-08 12:06:27,384] torch.distributed.elastic.multiprocessing.api: [ERROR] failed (exitcode: 1) local_rank: 0 (pid: 318821) of binary: /pinokio/api/fluxgym.git/env/bin/python
[2024-09-08 12:06:27] [INFO] Traceback (most recent call last):
[2024-09-08 12:06:27] [INFO] File "/pinokio/api/fluxgym.git/env/bin/accelerate", line 8, in
[2024-09-08 12:06:27] [INFO] sys.exit(main())
[2024-09-08 12:06:27] [INFO] File "/pinokio/api/fluxgym.git/env/lib/python3.10/site-packages/accelerate/commands/accelerate_cli.py", line 48, in main
[2024-09-08 12:06:27] [INFO] args.func(args)
[2024-09-08 12:06:27] [INFO] File "/pinokio/api/fluxgym.git/env/lib/python3.10/site-packages/accelerate/commands/launch.py", line 1097, in launch_command
[2024-09-08 12:06:27] [INFO] multi_gpu_launcher(args)
[2024-09-08 12:06:27] [INFO] File "/pinokio/api/fluxgym.git/env/lib/python3.10/site-packages/accelerate/commands/launch.py", line 734, in multi_gpu_launcher
[2024-09-08 12:06:27] [INFO] distrib_run.run(args)
[2024-09-08 12:06:27] [INFO] File "/pinokio/api/fluxgym.git/env/lib/python3.10/site-packages/torch/distributed/run.py", line 797, in run
[2024-09-08 12:06:27] [INFO] elastic_launch(
[2024-09-08 12:06:27] [INFO] File "/pinokio/api/fluxgym.git/env/lib/python3.10/site-packages/torch/distributed/launcher/api.py", line 134, in call
[2024-09-08 12:06:27] [INFO] return launch_agent(self._config, self._entrypoint, list(args))
[2024-09-08 12:06:27] [INFO] File "/pinokio/api/fluxgym.git/env/lib/python3.10/site-packages/torch/distributed/launcher/api.py", line 264, in launch_agent
[2024-09-08 12:06:27] [INFO] raise ChildFailedError(
[2024-09-08 12:06:27] [INFO] torch.distributed.elastic.multiprocessing.errors.ChildFailedError:
[2024-09-08 12:06:27] [INFO] ============================================================
[2024-09-08 12:06:27] [INFO] sd-scripts/flux_train_network.py FAILED
[2024-09-08 12:06:27] [INFO] ------------------------------------------------------------
[2024-09-08 12:06:27] [INFO] Failures:
[2024-09-08 12:06:27] [INFO] [1]:
[2024-09-08 12:06:27] [INFO] time      : 2024-09-08_12:06:27
[2024-09-08 12:06:27] [INFO] host      : printer
[2024-09-08 12:06:27] [INFO] rank      : 1 (local_rank: 1)
[2024-09-08 12:06:27] [INFO] exitcode  : 1 (pid: 318822)
[2024-09-08 12:06:27] [INFO] error_file: <N/A>
[2024-09-08 12:06:27] [INFO] traceback : To enable traceback see: https://pytorch.org/docs/stable/elastic/errors.html
[2024-09-08 12:06:27] [INFO] ------------------------------------------------------------
[2024-09-08 12:06:27] [INFO] Root Cause (first observed failure):
[2024-09-08 12:06:27] [INFO] [0]:
[2024-09-08 12:06:27] [INFO] time      : 2024-09-08_12:06:27
[2024-09-08 12:06:27] [INFO] host      : printer
[2024-09-08 12:06:27] [INFO] rank      : 0 (local_rank: 0)
[2024-09-08 12:06:27] [INFO] exitcode  : 1 (pid: 318821)
[2024-09-08 12:06:27] [INFO] error_file: <N/A>
[2024-09-08 12:06:27] [INFO] traceback : To enable traceback see: https://pytorch.org/docs/stable/elastic/errors.html
[2024-09-08 12:06:27] [INFO] ============================================================
[2024-09-08 12:06:27] [ERROR] Command exited with code 1
[2024-09-08 12:06:27] [INFO] Runner:

It doesn't look super obvious on how to solve this without installing the dependency manually?

This seems like an installer issue? I have other pinokio projects that have this lib:
/pinokio/api/triposr.git/app/env/lib/libpng16.so.16.43.0

Turns out its an issue with Pinokio installing manually has no issues with this.

Where should be installed?

Where should it be installed?

honestly it worked fine once I manually installed the github repo. try following the instructions in the read me it should work unless your distro is actually missing the libs.


Make contexts visible in tests

Description
Introduce the following test decorators:

for_all_test_contexts parametrizes a test to run on all test contexts, by passing a test_context parameter to the test. The parametrized test are annotated in pytest output, so that if an error occurs, (1) it is easy to track down the contexts where the error occurred, (2) one context failing still allows the tests to run on the remaining contexts. Finally, what will be useful for xtrack/xpart is that in case of a test being retried, only the offending context needs to
be rerun.
requires_context skips the test if the specified context is unavailable

Closes xsuite/xsuite#167.
Closes xsuite/xsuite#228.
Part of the solution for xsuite/xsuite#190.
Checklist
Mandatory:

[ ] I have added tests to cover my changes
[x] All the tests are passing, including my new ones
[x] I described my changes in this PR description

Optional:

[x] The code I wrote follows good style practices (see PEP 8 and PEP 20).
[x] I have updated the docs in relation to my changes, if applicable
[x] I have tested also GPU contexts

add a possibility of skipping certain context classes


InMemory provider increments row id property even when saving throws an exception

If an entity has a primary and a property mapped to use UseSqlServerIdentityColumn(), adding two instances with same key using different dbContext instances will result in an exception being thrown (as expected). However,calling context.Add() pre-emptively increments the id so that after both calls the entity has an id of 2 instead of 1.

This is by design. It's similar to if you use the Hi-Lo generator on SQL Server, we don't make any attempt to return keys that are not ultimately saved.
BTW calling UseSqlServerIdentityColumn() has no impact when running against InMemory, that metadata is only processed by the SQL Server provider.


benchmark to exercise genji / sys-accounts

Commit the existing bench.
Main thing right now is working out if its out code or genji code.
So we can give quality feedback to the genji team.
Lets not use TLS yet, as per other Issue: https://github.com/getcouragenow/sys/issues/34
We can discuss how best to get the benchmark code working with sys accounts then.

Can be closed now

Next steps
Make the Users and Concurrent DB connections a flag param.
Wire up the make file

Then after that we will make the benchmark part of the CLI

SO can run many clients onto many servers ( v2 and v3). The CLI has no knowledge of where the DB is, and the Server


DateTime Column with @default(now()) is not using database level time when insert query is generated.

Bug description
When I check the query produced by the prisma client when creating data, I expected that the column which its default is set to @default(now()) does not appear in the INSERT INTO column queries so that it could use the columns default value, which is actually the database level time.
But it seems that even if @default(now()) is set to that column, the query generates the time from the Prisma Engine level and includes it in the INSERT INTO statement.
How to reproduce

This is a simple schema that I use to reproduce:
generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model Jack {
  id        String   @id @default(uuid()) @db.Uuid()
  name      String   @db.VarChar()
  createdAt DateTime @default(now())
}

Create a data using the generated client

await prisma.jack.create({
  data: {
    name: 'jack'
  }
});

// This is the produced query event from the above create statement:
{
  timestamp: 2024-12-06T04:22:08.874Z,
  query: 'INSERT INTO "public"."Jack" ("id","name","createdAt") VALUES ($1,$2,$3) RETURNING "public"."Jack"."id", "public"."Jack"."name", "public"."Jack"."createdAt"',
  params: '["fb3685f6-5a56-4c9a-b814-617b58fe28c8","jack","2024-12-06 04:22:08.866 UTC"]',
  duration: 6,
  target: 'quaint::connector::metrics'
}

Expected behavior
I expected that createdAt will not be included in the INSERT INTO statement because

column is explicitly omitted from the prisma.jack.create statement's data
it has a default value in the schema

expected query:
{
  timestamp: 2024-12-06T04:22:08.874Z,
  query: 'INSERT INTO "public"."Jack" ("id","name") VALUES ($1,$2) RETURNING "public"."Jack"."id", "public"."Jack"."name"',
  params: '["fb3685f6-5a56-4c9a-b814-617b58fe28c8","jack"]',
  duration: 6,
  target: 'quaint::connector::metrics'
}

Prisma information

// Add your schema.prisma

// Add your code using Prisma Client

Environment & setup

OS: macOS, Ubuntu
Database: PostgreSQL
Node.js version: 20.15.0

Prisma Version
Environment variables loaded from .env
prisma                  : 6.0.1
@prisma/client          : 6.0.1
Computed binaryTarget   : darwin-arm64
Operating System        : darwin
Architecture            : arm64
Node.js                 : v20.15.0
Query Engine (Node-API) : libquery-engine 5dbef10bdbfb579e07d35cc85fb1518d357cb99e (at<EMAIL_ADDRESS>Schema Engine           : schema-engine-cli 5dbef10bdbfb579e07d35cc85fb1518d357cb99e (at node_modules/@prisma/engines/schema-engine-darwin-arm64)
Schema Wasm             : @prisma/prisma-schema-wasm 5.23.0-27.5dbef10bdbfb579e07d35cc85fb1518d357cb99e
Default Engines Hash    : 5dbef10bdbfb579e07d35cc85fb1518d357cb99e
Studio                  : 0.503.0

Hi @JackCme, you can use @default(dbgenerated("NOW()")) so that Prisma matches the behavior you'd expect.
Btw, I'm closing this issue as a duplicate in favor of https://github.com/prisma/prisma/issues/1831.
Can I please ask you the use case? What is the current @default(now()) behavior preventing you to do? Thanks


PARTITION LIKE

Background: https://airtable.com/tblD3oZPLJgGhCmch/viwINAgXA5on9pr2T/receDBx8soBOvT3Hr
PRs:

Dup of https://github.com/cockroachdb/docs/issues/2024


fix(ansible): add custom https port

Thanks a LOT for all your effort ! We did it !

https://github.com/lyrgard/ffbeEquip/issues/124


Update faucet.md

Added the Telegram faucet bot maintained by Binstep

The Faucet ui hardly works, providing an option for developers and users to get Test Move without waiting for the official faucet coming back online


revokeAllPermissions in not work on Android

I followed all the settings in the document and other functions can be used normally.
But only the revokeAllPermissions function has no effect in Android 14
But in Android 13, it has normal removal permissions.
Environment:

Health Connect Version: 2.0.3
React Native Version: 0.71.16
New architecture enabled: Yes/No
Using Expo: No

import { initialize, requestPermission, getGrantedPermissions, readRecords, revokeAllPermissions, getSdkStatus, SdkAvailabilityStatus } from 'react-native-health-connect';
<TouchableOpacity style={styles.button} onPress={revokeAllPermissions}>             <Text style={styles.text}>revokePermissions</Text>           </TouchableOpacity>

I noticed this as well,
What happened on my end though is that when i close the app after revoking app permissions,
the permissions on the health connect app reflected. but only after I closed the app after revoking all permissions

Same here - couldn't get this function to work

This function hasn't been changed for a while and it can be due to changes from Google. So, expect these behaviours in alpha version.

Finally I got some time to check this out!
This can be related to permission delegate API not being fully compatible with RN. Can everyone verify closing and opening the app would show the changes?

Same here - I don't get the changes applied even on app close/re-open.

Finally I got some time to check this out!
This can be related to permission delegate API not being fully compatible with RN. Can everyone verify closing and opening the app would show the changes?

Please let us know if revokePermissions works now or what we should do as I have to close the entire app and reopen it for permissions to be taken away. Thank you.

It still does persist. Have to close and restart the app.


Simplify code around latest state change map updates

Updates xsync to v2 and simplifies the code slightly.

[x] read the CONTRIBUTING guidelines
[ ] raised a GitHub issue or discussed it on the projects chat beforehand
[ ] added unit tests
[ ] added integration tests
[ ] updated documentation if needed
[ ] updated CHANGELOG.md

The failed build looks unrelated, but I may be wrong.

Yes I’ll fix it and then it should be good Sent from Proton Mail for iOS On Fri, Oct 28, 2022 at 07:43, Andrei Pechkurov @.***> wrote:
The failed build looks unrelated, but I may be wrong.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because your review was requested.Message ID: @.***>

The failed test (TestPingAllPeersByAddress) seems to be timing out on main as well.

The failed test (TestPingAllPeersByAddress) seems to be timing out on main as well.


Rename exec?

As it depends of the target type whether or not something is actually executed, the name exec is a bit confusing.
There is already the precedent of the method run used by Kleisli, StateT and WriterT in Cats (and in all(?) the monad transformers in Scalaz) and this also doesn't "run" something, but if we can come up with a better name, we don't have to follow these bad practices.

Is it interpret?

Is it transform as it transforms from Coproduct to another Monad ?

I like interpret as @ShaneDelmore mentioned and also like a shorter version program.to[Future]. transform also works but is widely used as a combinator name in cats for potentially other purposes https://github.com/typelevel/cats/blob/c1dcd408a9f5af9387280cee88beb9f475f08a3c/core/src/main/scala/cats/data/Kleisli.scala#L51 so no sure if it could create confusion when you are interpreting to something such as Kleisli and you may end up with program.transform[Kleisli[M, D, ?]].transform(...)

Agree with you @raulraja, interpret seems to be a good choice as its actually doing the interpretation.


CVE-2007-4559 Patch

Patching CVE-2007-4559
Hi, we are security researchers from the Advanced Research Center at Trellix. We have began a campaign to patch a widespread bug named CVE-2007-4559. CVE-2007-4559 is a 15 year old bug in the Python tarfile package. By using extract() or extractall() on a tarfile object without sanitizing input, a maliciously crafted .tar file could perform a directory path traversal attack. We found at least one unsantized extractall() in your codebase and are providing a patch for you via pull request. The patch essentially checks to see if all tarfile members will be extracted safely and throws an exception otherwise. We encourage you to use this patch or your own solution to secure against CVE-2007-4559. Further technical information about the vulnerability can be found in this blog.
If you have further questions you may contact us through this projects lead researcher Kasimir Schulz.

Thanks for the PR.
I tested the decompress action that uses this code, confirmed the new code ran and worked as expected. This fix also seems to be the same as in https://github.com/explosion/spaCy/pull/11746.
Since this workflow is designed only to be used with a few specific files I don't think there was ever really any risk in this specific instance, but I'll go ahead and merge this.


Feature Request: clear drawable property, ability to select none

Currently when customizing a style's properties, it is not possible to remove a drawable. Say, for my ButtonStyle I choose a drawable for the property "checked". Later I regret that and want to remove it, but I can't.
I suggest one of the following:

Next to the drawable property, add a button, that when click clears the property.

When selecting a drawable, and the first drawable in the list will be a sqaure that says "None", and when choosing this, the property will be cleared.

Number 2 is probably easiest to implement. This feature would also be relevant for fonts or colors, but default color is white anyway.

Hello. You can select "clear drawable" at the very bottom of the "Select a Drawable" dialog. This is very similar to your #2 suggestion. Admittedly, your idea is a little more user friendly, but I'm not willing to add it at this time. Thanks for the contribution.

My bad. Must have missed it or thought it cleared ALL drawables. Thanks!


Allow easy customization of adlists.list file

I have been meaning to add this in at some point so it's easy to configure out of the box... but basically, the /etc/pihole/adlists.list file controls what ad lists Pi hole uses. There's also a custom.list to configure DNS... maybe I'll add that in a future issue.
But basically, add a variable like pihole_adlists and have it be a list with one adlist URL per line.
If the variable is not empty, write the contents line by line to a file named adlists.list inside the pi-hole/etc-pihole directory.

Huh... well, after a good deal of work and testing, apparently in Pihole 5 and later, the adlists are stored in the gravity database itself, and the adlists.list file on disk (in /etc/pihole/adlists.list) is just an artifact of an old installation.
Who knew?
It doesn't seem like there's a simple way to programmatically alter the adlist outside of maybe an API request somehow?

Still pushed one minor change to make working with relative-path config dirs easier.


Add a lib function to extract nixosConfigurations from raw flake

This PR adds a function to load colmena hive from the flake.
Use case:
If I have a flake output like this:
  outputs = {}: {
    colmena = {
      systemA = {...};
      systemB = {...};
    };
  }

Currently I have no way to obtain the nixosConfiguration associated to systemA and systemB. With this new function, I can now do for instance
  inputs.colmena = "github:zhaofengli/colmena";
  outputs = { colmena }: {
    nixosConfiguration = (colmena.fromRawFlake self).nodes;
    colmena = {
      systemA = {...};
      systemB = {...};
    };
  }

And this nixosConfiguration will contain the same system as the one that would be built by colmena. This is incomplete (keys are not uploaded), but it is still useful in (at least) two situations:

If I want to test the configuration in a VM (or anywhere)
If I want to bootstrap the machine with for instance https://github.com/numtide/nixos-anywhere

This function roughly adds the same content as what "colmena repl" gives access to, but in a nix evaluation context.

@otavio : we could indeed have two functions to do it both ways (colmena -> nixosConfiguration and nixosConfiguration -> colmena)

Note however that in your case (nixosConfiguration -> colmena) you don’t get the exact same output between colmena build and nix build .#nixosConfiguration.hostName.system.build.toplevel, since colmena adds its own local changes. The other way around ensures that colmena’s additions get included too

I'm working around this by having an extra nix file that just duplicates the information and doesn't require any evaluation, but I'd love to get rid of it.

Why not use that extra file as single source of truth and import it onto the flake(s) instead?

Why not use that extra file as single source of truth and import it onto the flake(s) instead?

It’s not sufficient if you have configuration that depends on other nodes (i.e. if you use the nodes parameters in some places). That’s why I introduced that change: it comes after the resolution

I'm working around this by having an extra nix file that just duplicates the information and doesn't require any evaluation, but I'd love to get rid of it.

Why not use that extra file as single source of truth and import it onto the flake(s) instead?

That's basically what I'm doing, but I don't like it.  As in, I'd much rather write config.some.option = "<IP_ADDRESS>" then config.some.option = (import ./machines.nix)."${hostname}".ipAddress.
The thing that makes me dislike the above is that the IP address string I have is the input of some potentially complicated expression.  For example, my machines file specifies ipAddreess, lanIpAddress, and wgIpAddress for most hosts.  Which of these is used in different configuration options depends on whether the machine is a VM in a cloud, a physical server in the cloud, or some machine in my home network.  I've already written modules to figure out what to use and where, but if I want to write a script that uses this information, I have to duplicate the logic from my modules.

I made a PR that documents how to install NixOS with Colmena, https://github.com/zhaofengli/colmena/pull/209
Hopefully this helps!

@itslychee That's a nice tutorial, but I'm struggling to see how it relates to anything here.
This PR is about getting the generated nodes configuration out of colmena so that it can be used in other nix expressions.  Your PR is about installing on a new machine.

@itslychee That's a nice tutorial, but I'm struggling to see how it relates to anything here.
This PR is about getting the generated nodes configuration out of colmena so that it can be used in other nix expressions.  Your PR is about installing on a new machine.

you're right, i should read more. Personally was having issues with this and was seeing if anyone else was confused so i could help out in any way!


Change copy for georeference CTA

Fixes #4908

@javierarce can you review, please?
cc @gfiorav @saleiva

Frontend tests were OK :+1: (details)

@javierarce :eyes: bump

Frontend tests were OK :+1: (details)

retest this please

Frontend tests were OK :+1: (details)

:+1:


Feature/jdb/windows installer improvements

Don't merge yet as using this to trigger AppVeyor builds
Brings Windows installer improvements.  Namely:

Hyper-V install support
Use 1.1.0 multipass
Try to handle multipass failures
Test for available disk space

 MicroK8s Installer - Windows 10 restrictions

Definitely squash-merge this


🐛  Remove trailing slash for<EMAIL_ADDRESS>

closes #8569
Remove the trailing slash for<EMAIL_ADDRESS>data in theme middleware.

Today I stumbled on an oddity with my bespoke favicon URLs, eg.
/content/themes/beebletheme/favicons/apple-touch-icon.png?v=18a
The enforced trailing slash hasn't previously been a problem for me – if I want to publish an URL without the trailing slash I can; Ghost will just tack one on upon arrival and by that point the marketing has worked.
In the favicon URL however, the app chews on that URL in the template and I get served a console error because the processed URL doesn't exist, eg.
/content/themes/beebletheme/favicons/apple-touch-icon.png/?v=18a
I can work around it but if it helps further the work of this issue, there ya go.

@pjfdirect Hey!
The asset url for themes would be

/assets/favicons/apple-touch-icon.png/?v=18a

Hiya - thanks! Ghost does appear to provide rudimentary support for favicons, touch icons, etc. and I expect the blog engine expects and adapts to their urls. Because I customise and apply additional icon assets, I think they're getting trodden on.
I'll have a look at the path you shared; perhaps Ghost is generating a full complement and I can just finesse the art Ghost mechanically spun up from the single image I supplied to the dashboard.
Thanks again.


Videojs IMA SDK get/set volume and mute/mute on player volume change

Hi,
I have tried a lot but not able to find the solution where I can do change volume of player and same need to update on vidoejs ima sdk ads volume along with mute/unmute.
However I have tried below two params and it is doing unmute video but controlbar UI not updating.
player.ima..controller.onAdMuteClick(); // Button changes from mute to unmute but yellow bar not increased as per volume.
player.ima.controller.setVolume(0.8); // Nothing changes on controlbar UI.
Please advise main methods where I can do mute/unmute and set/get volume for Videojs IMA Ads.
Thanks

Hi,
Our Videojs-IMA plugin samples has volume change, mute and unmute already implemented, you can take a look and play around with them here

Hi,
Thanks a lot for your valuable time and support. Can you please advise the
function name where I can update mute and unmute to ads along with videojs
player instance. i.e. player.ima(options); player.volume=0.6; can this
volume be changed to ads also.
One more things, I have added tap to unmute button on top video player so
when ever user click on tap to unmute button it should unmute both videojs
and ads ima so please share the function/methods name where I can do
control both volume from one common function.
Also can you please advise how to serve custom midroll? i.e. on 30 seconds
of video play back I want to request midroll ads so please advise on this.
Best regards,
Sunil
On Tue, Apr 21, 2020 at 2:58 AM Arnaud Casamé<EMAIL_ADDRESS>wrote:

Hi,
Our Videojs-IMA plugin samples has volume change, mute and unmute already
implemented, you can take a look and play around with them here
https://googleads.github.io/videojs-ima/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/googleads/videojs-ima/issues/901#issuecomment-616819544,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAS2BSLGFINXLL7I2QH7FDTRNS5BBANCNFSM4MG3BZ5Q
.

Hi @sunilstg,
The videojs-ima plugin already takes care of muting and unmuting the ad playback when a user tap on the speaker icon.
You can use VMAP  to serve midroll but you would have to configure your timeOffset attribute so that your mid-roll can show after 30 seconds. Feel free to reach out to the Ad Manager Support team so they can help you with the server-side settings.


update add key to be compatible with new Cadence api

Cadence is removing addPublicKey and removePublicKey in the secure-cadence version, so the sdk needs to no longer use these functions.

For contributor use:

[ ] Targeted PR against master branch
[X] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[X] Code follows the standards mentioned here.
[X] Updated relevant documentation
[X] Re-reviewed Files changed in the Github PR explorer
[X] Added appropriate labels

Thank you for addressing this issue, but I believe it's solved by the PR I made here https://github.com/onflow/flow-go-sdk/pull/255

Oh great! How soon can we merge that PR? We are currently blocked on this from releasing a secure-cadence test build in flow-go.


Add ability to save figure as multiple filetypes simultaneously

I often want to save a .pdf and .png file for each figure I make, which results in a lot of duplicate lines of code where the only thing I've changed is the extension. It would be great to have an option in save_figure that allows you to save both filetypes (or more, if people use other extensions) at the same time. Something like:
def save_figure(fname: str, fname_types: list = ["pdf, png"], context: str = "web", **savefig_kwargs: dict[Any, Any]) -> None:
    "Save the current figure with the default settings for web."
    kwargs = SAVEFIG_KWARGS_WEB if context == "web" else SAVEFIG_KWARGS_PRINT
    kwargs.update(**savefig_kwargs)  # type: ignore
    for fname_type in fname_types:
        plt.savefig(fname = fname + fname_type, **kwargs) #type: ignore

Addressed by #51


deis run fails with "No space left on device"

$ deis run -a ordering -- rake db:migrate
Running `rake db:migrate`...
400 BAD REQUEST
[Errno 28] No space left on device

deis scale cmd=1 -a ordering
Scaling processes... but first, coffee!
400 BAD REQUEST
[Errno 28] No space left on device

Everything seems to fail. Looks like I have plenty of disk space.

I have just had this issue with Google Compute, running df -h did appear to show space as not such an issue but when I looked closer I saw that the drive was actually full. So after speak with @bacongobbler on IRC I've removed a few images (old and not needed) and it seems to work again.
Filesystem                                     Size  Used Avail Use% Mounted on
/dev/sdb                                        32G   31G  564M  99% /var/lib/docker
/dev/sdb                                        32G   31G  564M  99% /var/lib/docker/btrfs

Maybe a fix isn't necessary but maybe a warning before getting to this misleading error?


Assets: remove CLI --assets flag

Assets now would be displayed in CLI by default. Remove --assets flag.

--assets flag is removed, --asset_id is still present (show info about particular asset)
--enable_assets removed for cli (assets on by default), still present and false by default for API
Changes are discussed with Romanov.

Remove "--enable_assets"  parameter from  cli helper

As I've described above
--enable_assets removed for cli (assets on by default), still present and false by default for API
Removing the flag can break existing scripts. It is made 1 (true) by default.

checked


docs: update README, add license

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


README link broken

Hi,
Is it possible to fix the link in the README:
Script your first Adobe Generator plugin for Photoshop -> http://tomkrcha.com/?p=3896

Yes, I'd like to see this tutorial as well!

That blog post may have been lost to the sands of time, but a fork of the sample plugin it referenced is here: https://github.com/adobe-photoshop/generator-getting-started

My problem is I can't even figure out how to get it show up in the Menu, even though it says it is working.  And the generator-assets example is confusing me with its dummy-menu explanation.

Removed stale link.  RIP tomkrcha blog.


What does 1000m CPU resource mean ?

When deploying a solution, it often asks for the flavour. Clear for memory and storage, but what does "1000m", "2000m", ... compute units mean ? 1 core, 2 cores, ... ? why put 1000 ?

duplicate: https://github.com/threefoldtech/js-sdk/issues/2353

This is the official resource units for kubernetes : https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#resource-units-in-kubernetes


fix: minor changes

Some minor changes which allow application to run
Fix typo in error message

I'd love to merge the spelling fix in so please remove all other changes and provide the other changes in a separate PR so we can discuss if/how to merge them in there.
Please keep PRs focused on one aspect in the future so it's easier to accept them.
The title of the PR should be able to express the feature added or bug it fixed.
If the title ends up being something like various/misc fixes/features or similar then that indicates that it's not focused enough.

I pulled in the spelling fix since I needed to publish a new version.
We can discuss here regarding those other changes ... however if you agree with what I said above please close this PR.
Thanks!

The reason I open the PR was not my personal preference of styling, how to check properties and certainly not looking for typos.
Let me explain the problem:
Create the project, install @metaplex-foundation/amman, add configuration file .ammanrc with contents you gave me before
$ ls -la
drwxr-xr-x  3 oleg oleg  4096 Dec 10 15:21 ./
drwxr-xr-x 22 oleg oleg  4096 Dec 10 12:04 ../
-rw-r--r--  1 oleg oleg   965 Dec 12 00:12 .ammanrc.js
drwxr-xr-x 81 oleg oleg  4096 Dec 12 00:10 node_modules/
-rw-r--r--  1 oleg oleg   158 Dec 12 00:10 package.json
-rw-r--r--  1 oleg oleg 29033 Dec 12 00:10 yarn.lock

$ cat package.json
{
  "name": "amman-tmp",
  "version": "1.0.0",
  "main": "index.js",
  "license": "MIT",
  "dependencies": {
    "@metaplex-foundation/amman": "^0.0.3"
  }
}

$ cat .ammanrc.js

// @ts-check
'use strict';
const path = require('path');

const localDeployDir = path.join(__dirname, 'target', 'deploy');

const programIds = {
  metadata: 'metaqbxxUerdq28cj1RbAWkYQm3ybzjb6a8bt518x1s',
  vault: 'vau1zxA2LbssAUEF7Gpw91zMM1LvXrvpzJtmZ58rPsn',
  auction: 'auctxRXPeJoc4817jDhf4HbjnhEcr1cCXenosMhK5R8',
  metaplex: 'p1exdMJcjVao65QdewkaZRUnU6VPSXhus9n2GzWfh98',
};

function localDeployPath(programName) {
  return path.join(localDeployDir, `${programName}.so`);
}
const programs = {
  metadata: { programId: programIds.metadata, deployPath: localDeployPath('mpl_token_metadata') },
  vault: { programId: programIds.vault, deployPath: localDeployPath('mpl_token_vault') },
  auction: { programId: programIds.auction, deployPath: localDeployPath('mpl_auction') },
  metaplex: { programId: programIds.metaplex, deployPath: localDeployPath('mpl_metaplex') },
};

const validator = {
  verifyFees: true
};

module.exports = {
  programs,
  validator,
};

After these steps, I run the command:
$ npx amman validator

And I get errors:
npx amman validator
TypeError: Cannot read properties of undefined (reading 'length')
    at handleValidatorCommand (/home/oleg/meta/amman-tmp/node_modules/@metaplex-foundation/amman/dist/cli/commands/validator.js:23:82)
    at async main (/home/oleg/meta/amman-tmp/node_modules/@metaplex-foundation/amman/dist/cli/amman.js:23:30)
Having trouble loading amman config from [object Object] which resolved to /home/oleg/meta/amman-tmp/.ammanrc.js
amman validator [config]

Launches a solana-test-validator

Positionals:
  config  File containing config with `validator` property.

Options:
  --version  Show version number                                       [boolean]
  --help
              amman validator <config.js>

              The config should be a JavaScript module exporting 'validator'
              with any of the below properties:

              killRunningValidators: if true will kill any
              solana-test-validators currently running on the system.

              programs: bpf programs which should be loaded into the test
              validator

              jsonRpcUrl: the URL at which the test validator should listen for
              JSON RPC requests

              websocketUrl: for the RPC websocket

              ledgerDir: where the solana test validator writes the ledger

              resetLedger: if true the ledger is reset to genesis at startup

              verifyFees: if true the validator is not considered fully started
              up until it charges transaction fees
                                                                       [boolean]

That's it. @thlorenz I would be grateful if you would point out the solution to the problem, which is more suitable for you.
I don't insist on merging the PR, I just want to run amman - needed for job :)

I can help you out more on Monday, but mainly your problem is that your config doesn't match the type of 'programs` of the amman config. Please consult this example closely to see what I mean.
Namely this is an object hash:
const programs = {
  metadata: { programId: programIds.metadata, deployPath: localDeployPath('mpl_token_metadata') },
  vault: { programId: programIds.vault, deployPath: localDeployPath('mpl_token_vault') },
  auction: { programId: programIds.auction, deployPath: localDeployPath('mpl_auction') },
  metaplex: { programId: programIds.metaplex, deployPath: localDeployPath('mpl_metaplex') },
};

but the config expects an array.
I feel like you tried to change amman to make up for that discrepancy when you ran into issues. I pointed that out as well. Instead you should make your config (namely programs) be of the type that amman expects.

Thanks. That's all wanted to know, that the config I used does not meet the requirements


make "latests" latest release, and create a new "last-successful-build" or something like that.

latest-pr. done.


JS: fix FPs in UselessConditional

Fixes these false positives.
For a code snippet like this,
let obj = (x && {}) || y;

we would report that {} always evaluates to true, but {} also gets stored in obj, so the alert is moot.
We now distinguish between conditionals that only use the expression for the purpose of a branch from those that also use it for something else.

I've started an evaluation in case we want to (safely) retarget to rc/1.19.

Merging (C++ QL Tests failure is irrelevant).


Bug: no able to deploy on a specific pipeline that migrated to helm from gitops deployment

📜 Description
no able to deploy any new deployment on a specific pipeline that migrated to helm from gitops deployment .
having error-: pg: multiple rows in result set
👟 Reproduction steps
none
👍 Expected behavior
it should be worked fine
👎 Actual Behavior

not working
☸ Kubernetes version
1.24
Cloud provider

aws
🌍 Browser
Chrome
🧱 Your Environment
No response
✅ Proposed Solution
No response
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

AB#5398

Potential duplicates:

[#3863] Bug: Gitops replicas sync into the deployment/rollout on commits made to same repo + same folder (42.41%)

[#3845] Bug: multiple entries for helm charts for every releases in Helm deployment (42.6%)

Potential duplicates:

[#3863] Bug: Gitops replicas sync into the deployment/rollout on commits made to same repo + same folder (42.41%)

[#3845] Bug: multiple entries for helm charts for every releases in Helm deployment (42.6%)

Potential duplicates:

[#3863] Bug: Gitops replicas sync into the deployment/rollout on commits made to same repo + same folder (42.41%)

[#3845] Bug: multiple entries for helm charts for every releases in Helm deployment (42.6%)

Potential duplicates:

[#3863] Bug: Gitops replicas sync into the deployment/rollout on commits made to same repo + same folder (42.41%)

[#3845] Bug: multiple entries for helm charts for every releases in Helm deployment (42.6%)


Conversion to categorical makes None "None"

I was trying to use categorical labels where some samples don't get a label and ran into this. I think that we should allow having null labels, and visualizing shouldn't meaningfully mutate the object.
import scanpy as sc
import numpy as np

pbmc = sc.datasets.pbmc68k_reduced()
some_subset = np.random.choice(
    pbmc.obs_names, int(pbmc.shape[0] / 2), replace=False
)
pbmc.obs["has_nulls"] = None
pbmc.obs.loc[some_subset, "has_nulls"] = "a value"
pbmc.obs["has_nulls"].isnull().sum()
# 350
sc.pl.pca(pbmc)
pbmc.obs["has_nulls"].isnull().sum()
# 0

yikes, definitely. do categoricals support “nan” or some other not-set value?

I suspect this: https://github.com/theislab/anndata/blob/34f4eb63710628fbc15e7050e5efcac1d7806062/anndata/base.py#L1419
and that ‘is_string_dtype’ doesn’t work is to blame.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Here's a test-case:
Actual behaviour
import numpy as np
from anndata import AnnData
adata = AnnData(
    obs=pd.DataFrame().assign(
        str_with_nan=["foo", "bar", None, np.nan, "foo"],
        booelan_with_nan=[True, False, np.nan, None, True],
    )
)
adata._sanitize()

... storing 'str_with_nan' as categorical
... storing 'booelan_with_nan' as categorical

adata.obs["str_with_nan"].values

['foo', 'bar', 'None', 'nan', 'foo']
Categories (4, object): ['None', 'bar', 'foo', 'nan']

adata.obs["booelan_with_nan"].values

['True', 'False', 'nan', 'None', 'True']
Categories (4, object): ['False', 'None', 'True', 'nan']

Expected behaviour

boolean_with_nan is not converted to categorical (bool stays bool)
str_with_nan is converted to categorical, but nan and None are treated as special values.

Thanks for the example @grst! I've got a fix opened up.
About the boolean arrays, we don't quite have a solution ready for nullable booleans. I've put some thoughts on this here #504.


Refactor cli

This PR completes the CLI interface for each of the remaining stages -- VAE encoding and Dimensionality reduction.
It also adjusts dependencies to hardcode specific versions of tensorflow and segmentation_models that we've confirmed will properly predict segmentations on our microglia data.
I have included a configuration file:
configs/bryant_rubella_experiments.yml that points to a small subset of data on ESS.  You can use this configuration to test each component of the pipeline.  All CLI's should follow this format:
run_preproc.py -c ./configs/bryant_rubella_experiments.yml

run_segmentation.py -m "segmentation" -c ./configs/bryant_rubella_experiments.yml

run_segmentation.py -m "instance_segmentation" -c ./configs/bryant_rubella_experiments.yml

etc...

Summary of behavior 7-8-2021:
config file
The configuration file now accepts a list of input, output full paths to directories.  The file_name_prefixes is a list of string prefixes.  The weights_dir is a single directory in which pca_model.pkl is written as a result of PCA fitting (fit_model = True).  The conditions is a list of strings describing experimental conditions.  This value is only used during plotting after fitting.
details
For fit_model: True:

loops over all directories listed in config's input_dirs
loops over all prefixes in config's file_name_prefixes
[aggregate all data]: searches for <prefix>_latent_space_after.pkl files in the input dirs and concatenates them in a vector list for subsequent PCA fitting
Fitting will write a model pca_model.pkl to the config's weights_dir directory.
Fitting will write a figure PCA.png to the config's weights_dir directory
finally, will loop over all pairs of input_dirs and output_dirs in the config:
will run inference on all individual <prefix>_latent_space_<suffix>.pkl in input_dir folder, where suffix='after' hardcoded.  And where the supplied model is the one generated from step 4 above.
output of each inference is <prefix>_latent_space_after_PCAed.pkl and saved to each corresponding output_dir from 6

For fit_model: False:

loops over all pairs of directories listed in config's input_dirs / output_dirs
loops over all prefixes in config's file_name_prefixes
assumes the weights_dir supplied in the config is a directory, and looks for the pca_model.pkl file there.
runs inference on <prefix>_latent_space_<suffix>.pkl where suffix=after is hardcoded.
writes the transformed vectors to <prefix>_latent_space_<suffix>_PCAed.pkl in the corresponding output_dir directory

The PR looks good now! Feel free to merge when you think is ready.


pom.xml templating

maybe pom.xml is more custom file than general

@h1alexbel I was thinking about pom.xml but I have no idea which one should be, say, `common', if you know what that might be, go ahead and send pr


Update feature request to include acceptance criteria

Signed-off-by: Paul Bastide<EMAIL_ADDRESS>

My one concern with this one is that we expect our users to open feature requests using this template and I'm not sure whether its appropriate for them to add "Acceptance Criteria" to those.
As a develop, I do like having AC on issues that I work on.  But as an open source maintainer, it just feels a little odd.
That said, I'm fine with updating the template and seeing how it goes.

My one concern with this one is that we expect our users to open feature requests using this template and I'm not sure whether its appropriate for them to add "Acceptance Criteria" to those.
As a develop, I do like having AC on issues that I work on. But as an open source maintainer, it just feels a little odd, because we need to think very critically about what any user is asking for.
That said, I'm fine with updating the template and seeing how it goes.

I acknowledge your concerns and have many of the same.  If you are OK, we probably can merge, or if you prefer we can update the template to put, dev team only


Run file_sync test in GHA CI

Closes #308.

This change is

Well, the test works...

Does the EOL fix need to be a separate PR?