installing 0.21.1 fails using documented install steps

Bug Report
I am following the install steps found here: https://github.com/operator-framework/operator-lifecycle-manager/releases/tag/v0.21.1 where it says to run:
curl -L https://github.com/operator-framework/operator-lifecycle-manager/releases/download/v0.21.1/install.sh -o install.sh
chmod +x install.sh
./install.sh v0.21.1

I did that and I get the following error and OLM fails to install properly:
$ curl -L https://github.com/operator-framework/operator-lifecycle-manager/releases/download/v0.21.1/install.sh -o install.sh
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  1884  100  1884    0     0   8448      0 --:--:-- --:--:-- --:--:--  8448
$ chmod +x install.sh
$ ./install.sh v0.21.1
customresourcedefinition.apiextensions.k8s.io/catalogsources.operators.coreos.com unchanged
customresourcedefinition.apiextensions.k8s.io/installplans.operators.coreos.com unchanged
customresourcedefinition.apiextensions.k8s.io/olmconfigs.operators.coreos.com unchanged
customresourcedefinition.apiextensions.k8s.io/operatorconditions.operators.coreos.com unchanged
customresourcedefinition.apiextensions.k8s.io/operatorgroups.operators.coreos.com unchanged
customresourcedefinition.apiextensions.k8s.io/operators.operators.coreos.com unchanged
customresourcedefinition.apiextensions.k8s.io/subscriptions.operators.coreos.com unchanged
The CustomResourceDefinition "clusterserviceversions.operators.coreos.com" is invalid: metadata.annotations: Too long: must have at most 262144 bytes

Environment

Kubernetes version information:

Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.0", GitCommit:"cb303e613a121a29364f75cc67d3d580833a7479", GitTreeState:"clean", BuildDate:"2021-04-08T16:31:21Z", GoVersion:"go1.16.1", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.3", GitCommit:"c92036820499fedefec0f847e2054d824aea6cd1", GitTreeState:"clean", BuildDate:"2021-10-27T18:35:25Z", GoVersion:"go1.16.9", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:

Minikube v1.24.0:
$ minikube version
minikube version: v1.24.0
commit: 76b94fb3c4e8ac5062daf70d60cf03ddcc0a741b

@jmazzitelli yep we just merged a fix to the install script in #2767. We'll need to cut a v0.21.2, or update that install bash script release artifact.

@timflannagan thanks! Is there an ETA on when 0.21.2 will be released? I am using this in a CI script (running tests on my operator when installed via OLM) so I would need to update that CI script that launches everything. I really don't want to implement a fix to update the OLM install script only to have to rip it out again when 0.21.2 is released - so I could just wait for 0.21.2 if it will be coming soon.

I really don't want to implement a fix to update the OLM install script only to have to rip it out again when 0.21.2 is released - so I could just wait for 0.21.2 if it will be coming soon.

Understandable - I think we'll cut release today so I don't think you need to make any short term workarounds.

@jmazzitelli the install.sh script has been updated for the v0.21.1 release payload, so you should not see that CI failure anymore.

Hi @jmazzitelli, this issue should be resolved by the amended script in v0.21.1. There was also a new v0.21.2 release which incorporates the new script in the payload. Please reopen if you have any additional issues.


Display default error pages for 413 errors

Extending from: https://github.com/ministryofjustice/cloud-platform-infrastructure/pull/327
When a 413 error is produced, for instance by uploading a >50mb file, the error page should be the default GDS styled one.
This can be set by adding 413 to the following line: https://github.com/ministryofjustice/cloud-platform-infrastructure/blob/master/terraform/cloud-platform-components/nginx-ingress-acme.tf#L35
Eg:
    custom-http-errors: 400,403,404,413,502,504

FYI the source of our 413 error is described here: https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/#custom-max-body-size

Deployed to Live-1 this morning.


Package started failing on Web

The package suddenly started failing on Flutter Web giving tons of errors, errors which were not very clear that came from the package. I had to break down the whole app to components, to narrow it down to google fonts. Just by importing it, the app crashes. The project compiles without any errors on mobile.
Below I'll show some screenshots of the errors, hope it helps. Keep in mind the package was working flawlessly till yesterday. I haven't introduced any changes from my part from what I can tell.

Because of the error log being very long i'll show 3-4 lines from each file giving the error.

My yaml file:

I'm also experiencing the same issue as above.

Fixed this by setting path_provider to 1.6.14 instead of 1.6.16:
  path_provider:
    dependency: transitive
    description:
      name: path_provider
      url: "https://pub.dartlang.org"
    source: hosted
    version: "1.6.14"

Fixed this by setting path_provider to 1.6.14 instead of 1.6.16:
  path_provider:
    dependency: transitive
    description:
      name: path_provider
      url: "https://pub.dartlang.org"
    source: hosted
    version: "1.6.14"

Awesome, downgrading path_provider to version 1.6.14 fixed the issue.

Final YAML file:

So is this caused by flutter upgrade or the fonts upgrade ?

Closing this since it's an old issue and path_provider has had a major bump (2.0.8). If this issue crops up again, please file a new issue


Icons does not redirect to social pages [GSSoc 23]

Does not redirect to social pages
The facebook and instagram icons at the bottom of the pages does not redirect to the indented pages.
To Reproduce
Steps to reproduce the behavior:

Go to 'our website'
Scroll down to bottom
Click on the social media icons
See error

Expected behavior
When clicked it must have gone to the social media pages
Screenshots
https://github.com/akshitagupta15june/PetMe/assets/67820811/e737e141-7dc3-4807-a73e-b0af8b2dd122

Can i work on it as part of GSSoc 23

Please assign me this task under GSSoC'23

Can I work on this issue?
please provide me the link of your facebook and instagram.
I will do this task under GSSoC'23

I would like to work on this issue
Please assign me to this task under GSSoc'23
Kindly provide me the link of the facebook and instagram page.

Please assign me this task under GSSOC

Some contributors are already working on this

ohoh


add support for creating Python-based s3 trigger in amplify add storage flow

Is this feature request related to a new or existing Amplify category?
function
Is this related to another service?
No response
Describe the feature you'd like to request
When adding an s3 bucket with amplify add storage we are prompted to create a Lambda Trigger, however upon selecting "yes" we are not prompted with the runtime question prompted in amplify add function thus creating a Node-based Lambda function.
As a workaround we can first create the Python Lambda with amplify add function, and select the existing function in the amplify add storage flow.
Describe the solution you'd like
When choosing to create a new function for the s3 trigger, enter the amplify add function flow starting with the runtime prompt
Describe alternatives you've considered
create the python function first, then choose the existing function in amplify add storage flow
Additional context
No response
Is this something that you'd be interested in working on?

[ ] 👋 I may be able to implement this feature request

Would this feature include a breaking change?

[ ] ⚠ This feature might incur a breaking change

So its been a year, and it is not possible to create S3 or DynamoDB triggers for python runtime..


[Bug]: The order of type definitions influences mapping subtype relation

Description
Consider the following cases,

Case 1

type M map<any>;
type N map<any>;

// @type M1 = M2
type M1 M|record {};

type M2 N|record {};

Case 2

// @type M1 = M2
type M1 M|record {};

type M2 N|record {};

type M map<any>;
type N map<any>;

Case 3

type M map<any>;

// @type M1 = M2
type M1 M|record {};

type M2 map<any>|record {};

Case 4

// @type M1 = M2
type M1 map<any>|record {};

type M2 map<any>|record {};

Although we have defined the same types in all 4 cases. The subtyping relation is different.

Results in M1 <> M2. So, the test fails.
Results in M1 = M2. So, the test passes.
Results in M1 <: M2. So, the test fails.
Results in M1 = M2. So, the test passes.

In cases 2 and 4, the record {} type gets defined first, therefore having a lower index compared to map<any> type. This influences the isEmpty() check on top of the diff().

The BDD for diff(M1, M2) is as follows.
For the failing cases,

For the passing cases,
The tree is same with map<any> and map<anydata> interchanged.

Overriding MappingAtomicType and ComplexSemTypes' equals() and hashCode() solved the issue for the original sample. However the following still fails as deep equality is not considered in subtypeDataList.
type M map<(1|2|3)>;
type N map<(1|2|3)>;

// @type M1 = M2
type M1 M|map<(1|2)>;

type M2 N|map<(1|2)>;

I was able to reproduce the same scenario(for the original sample) in nBallerina by modifying mappingAtom() as follows.
   isolated function mappingAtom(MappingAtomicType atomicType) returns TypeAtom {
       lock {
           TypeAtom? ta = self.atomTable[atomicType];
           if ta != () {
               TypeAtom result = { index: self.atomTable.length(), atomicType };
               return result;
           }
           else {
               TypeAtom result = { index: self.atomTable.length(), atomicType };
               self.atomTable.add(result);
               return result;
           }
       }
   }

The BDD for diff(M1,M2) I get there is different. So there is a bug in diff() in jBallerina.

The root cause was found to be a bug in mappingInhabited() when porting. Both nBallerina and jBallerina produce the same BDDs. The previous BDD explained here turned out to be a mistake.

Fixed in PR #42791


pythonPackages.python-prctl: init at 1.7

Motivation for this change
I want to use this package.
Things done

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

[X] NixOS
[ ] macOS
[X] other Linux distributions

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

@GrahamcOfBorg build pythonPackages.python-ptrcl python3Packages.python-ptrcl

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: pythonPackages.python-ptrcl, python3Packages.python-ptrcl
Partial log (click to expand)
Cannot nix-instantiate `pythonPackages.python-ptrcl' because:
error: attribute 'python-ptrcl' in selection path 'pythonPackages.python-ptrcl' not found

Cannot nix-instantiate `python3Packages.python-ptrcl' because:
error: attribute 'python-ptrcl' in selection path 'python3Packages.python-ptrcl' not found

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: pythonPackages.python-ptrcl, python3Packages.python-ptrcl
Partial log (click to expand)
Cannot nix-instantiate `pythonPackages.python-ptrcl' because:
error: attribute 'python-ptrcl' in selection path 'pythonPackages.python-ptrcl' not found

Cannot nix-instantiate `python3Packages.python-ptrcl' because:
error: attribute 'python-ptrcl' in selection path 'python3Packages.python-ptrcl' not found

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: pythonPackages.python-ptrcl, python3Packages.python-ptrcl
Partial log (click to expand)
Cannot nix-instantiate `pythonPackages.python-ptrcl' because:
error: attribute 'python-ptrcl' in selection path 'pythonPackages.python-ptrcl' not found

Cannot nix-instantiate `python3Packages.python-ptrcl' because:
error: attribute 'python-ptrcl' in selection path 'python3Packages.python-ptrcl' not found

Sorry, typo'd in the commit message and PR name

Rebase needed.

@GrahamcOfBorg build python2.pkgs.python-ptrcl python3.pkgs.python-ptrcl

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: python2.pkgs.python-ptrcl, python3.pkgs.python-ptrcl
Partial log (click to expand)
Cannot nix-instantiate `python2.pkgs.python-ptrcl' because:
error: attribute 'python-ptrcl' in selection path 'python2.pkgs.python-ptrcl' not found

Cannot nix-instantiate `python3.pkgs.python-ptrcl' because:
error: attribute 'python-ptrcl' in selection path 'python3.pkgs.python-ptrcl' not found

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: python2.pkgs.python-ptrcl, python3.pkgs.python-ptrcl
Partial log (click to expand)
Cannot nix-instantiate `python2.pkgs.python-ptrcl' because:
error: attribute 'python-ptrcl' in selection path 'python2.pkgs.python-ptrcl' not found

Cannot nix-instantiate `python3.pkgs.python-ptrcl' because:
error: attribute 'python-ptrcl' in selection path 'python3.pkgs.python-ptrcl' not found

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: python2.pkgs.python-ptrcl, python3.pkgs.python-ptrcl
Partial log (click to expand)
Cannot nix-instantiate `python2.pkgs.python-ptrcl' because:
error: attribute 'python-ptrcl' in selection path 'python2.pkgs.python-ptrcl' not found

Cannot nix-instantiate `python3.pkgs.python-ptrcl' because:
error: attribute 'python-ptrcl' in selection path 'python3.pkgs.python-ptrcl' not found

@GrahamcOfBorg build python2.pkgs.python-prctl  python3.pkgs.python-prctl

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: python2.pkgs.python-prctl, python3.pkgs.python-prctl
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: python2.pkgs.python-prctl, python3.pkgs.python-prctl
Partial log (click to expand)
Test manipulation of the timestamp counter flag ... ok
test_unalign (test_prctl.PrctlTest)
Test manipulation of the unaligned access setting ... ok

----------------------------------------------------------------------
Ran 26 tests in 0.005s

OK (skipped=4)
/nix/store/a9hvh8w3fwnysc91vna0zlqrija8pvhv-python2.7-python-prctl-1.7
/nix/store/jfhm4909ndmswkcjqjcpsfk462bbqdrm-python3.6-python-prctl-1.7

Success on aarch64-linux (full log)
Attempted: python2.pkgs.python-prctl, python3.pkgs.python-prctl
Partial log (click to expand)
Test manipulation of the timestamp counter flag ... ok
test_unalign (test_prctl.PrctlTest)
Test manipulation of the unaligned access setting ... ok

----------------------------------------------------------------------
Ran 26 tests in 0.022s

OK (skipped=4)
/nix/store/81vnh7ffwrxv9j1ya8y71128f79zrw4y-python2.7-python-prctl-1.7
/nix/store/wsdv08dhs9cjb9bd7sgmi7h0aw5v34bc-python3.6-python-prctl-1.7


gridsst: k8s 1.22 to 1.25, core node from m5 to r5, dask nodes from 4 different m5 to one r5.4xlarge

Changes seen in PR files
k8s upgrade
I saw that the victor cluster wasn't actively used, to I took the opportunity to perform an upgrade from k8s 1.22 to 1.25.
core node from m5.xlarge to r5.xlarge
I also transitioned the core node pool from a m5.xlarge (4CPU/16GB) to a r5.xlarge (4CPU/32GB) machine for more RAM without too much additional cost. I think all daskhub clusters ought to have at least 32 GB of memory as prometheus-server is likeley to need a memory request bump if dask-gateway is used, and the m5.xlarge just provides 16GB of memory.
dask nodes provided reduced from 4 m5 types to one r5.4xlarge (16CPU/128GB)
These are meant to perform heavier computations not possible on a single machine, and the users are not specifying what machine to startup on. Due to that, it doesn't make sense to provide four kinds of nodes matching those provided as user nodes. So, I'm fixing it in this PR just in case.
Outside PR - cleanup in cloud console
It seems that the eksctl configuration template eksctl/gridsst.jsonnet declared the name gridSST initially, created misc resources, and then renamed to gridsst.
There were some resources associated with the gridSST cloudformation stack, and some with the gridsst cloudformation stack. It seems though only one EKS cluster is created - by the gridsst cloudformation stack. I investigated if it was safe to remove those, believed so, and then did so.
This cleanup was partially needed at least, as there were older gridSST nodepools around conflicting with the gridsst nodepools I were managing via the eksctl-config.
I never got through to cleaning up everything related to gridSST. Failing to remove some VPC related resources. See here for the failing deletion.
ClusterSharedNodeSecurityGroup | sg-0ce65bf98832f5de4 | AWS::EC2::SecurityGroup | DELETE_FAILED

UPDATE: I managed to clean up it all up by manually removing: a ELB load balancer, EFS NFS server, misc security groups made for the ELB and EFS stuff, and I think another small thing I've forgot now.

Thanks for doing all the clean up, @consideRatio!!


Build from source - Raspberry Pi - 64-bit OS aarch64: configure.py returns IndexError: list index out of range

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Raspbian aarch64 "Debian GNU/Linux 10 (buster)"
TensorFlow version and how it was installed (source or binary): binary
TensorFlow-Addons version and how it was installed (source or binary): source
Python version: 3.7.3
Is GPU used? (yes/no): no

Describe the bug
While trying to build addons from source, running python3 ./configure.py returns  IndexError: list index out of range
./configure.py function is_raspi_arm() doesn't recognize that os.uname()[4] is aarch64 under 64-Bit Raspberry Pi OS (Raspbian).
Code to reproduce the issue
Under 64-Bit Raspberry Pi OS follow instructions to build addons from source.  python3 ./configure.py will fail as follows:
pi@myrpi4-8gb:~/addons $ python3 ./configure.py

Configuring TensorFlow Addons to be built from source...
Traceback (most recent call last):
  File "./configure.py", line 179, in <module>
    create_build_configuration()
  File "./configure.py", line 126, in create_build_configuration
    write_action_env("TF_SHARED_LIBRARY_DIR", get_tf_shared_lib_dir())
  File "./configure.py", line 94, in get_tf_shared_lib_dir
    return tf.sysconfig.get_link_flags()[0][2:]
IndexError: list index out of range

Other info / logs
Fix is to update configure.py to recognize aarch64 as follows:
diff --git a/configure.py b/configure.py
index 0ceb902..5126f6d 100644
--- a/configure.py
+++ b/configure.py
@@ -49,7 +49,7 @@ def is_linux():

 def is_raspi_arm():
-    return os.uname()[4] == "armv7l"
+    return os.uname()[4] == "armv7l" or os.uname()[4] == "aarch64"

 def is_linux_ppc64le():

./configure.py then completes normally:
pi@myrpi4-8gb:~/addons $ python3 ./configure.py

Configuring TensorFlow Addons to be built from source...
> Building only CPU ops

Build configurations successfully written to .bazelrc :

build --action_env TF_HEADER_DIR="/usr/local/lib/python3.7/dist-packages/tensorflow/include"
build --action_env TF_SHARED_LIBRARY_DIR="/usr/local/lib/python3.7/dist-packages/tensorflow/python"
build --action_env TF_SHARED_LIBRARY_NAME="_pywrap_tensorflow_internal.so"
build --action_env TF_CXX11_ABI_FLAG="1"
build --spawn_strategy=standalone
build --strategy=Genrule=standalone
build -c opt
build --cxxopt=-std=c++14
build --host_cxxopt=-std=c++14

Can you send a PR?


Build and publish Python 3.13 and 3.13t wheels

Request description
Python 3.13 is currently in prerelease and will be released soon. It also includes a "free threaded" (no Global Interpreter Lock) variant. We should start building the iree-compiler and iree-runtime packages for each of these versions.

https://docs.python.org/3.13/whatsnew/3.13.html
https://realpython.com/python313-new-features/
https://py-free-threading.github.io/

What component(s) does this issue relate to?
Python
Additional context
For Python 3.12, see https://github.com/iree-org/iree/issues/15856.
We are starting to use Python 3.13 and free-threaded support downstream in the shortfin package/project under https://github.com/nod-ai/SHARK-Platform/ (see https://github.com/nod-ai/SHARK-Platform/issues/130).
For free-threaded support, we'll likely need to update and/or change our usage of pybind11 (for the compiler) and nanobind (for the runtime)

We could wait until Python 3.13 is fully released (on 2024-10-07), but https://www.python.org/downloads/release/python-3130rc3/ actually encourages early adoption:

We strongly encourage maintainers of Python projects to prepare their projects for 3.13 compatibilities during this phase, and where necessary publish Python 3.13 wheels on PyPI to be ready for the final release of 3.13.0. Any binary wheels built against Python 3.13.0rc1 and later will work with future versions of Python 3.13.

I was able to build release packages on Linux (manylinux_2_28) for Python 3.13 and 3.13t with some dockerfile updates: https://github.com/iree-org/base-docker-images/pull/15. No changes to IREE source code or our pybind/nanobind deps needed. Not sure if the build on its own is enough though, may need to run some tests too.

I have a branch nearly ready to test: https://github.com/ScottTodd/iree/tree/infra-python3.13
Need to land https://github.com/iree-org/base-docker-images/pull/15 first to get Python 3.13 in our manylinux dockerfile.
Building for more versions will increase nightly release CI time, and we should be testing against these versions too (see https://github.com/iree-org/iree/issues/15856#issuecomment-1947134679 and other comments there).

Got a mostly successful test release build last night: https://github.com/iree-org/iree/actions/runs/11156205488 using this branch: https://github.com/iree-org/iree/tree/users/scotttodd/python3.13.
I tried installing python 3.13t on macOS and Windows but need to do more troubleshooting. Each installer requires some extra options for the free-threaded support and puts the binary on a different path, so the existing scripts need some changes:

build_tools/python_deploy/install_macos_deps.sh
build_tools/python_deploy/build_macos_packages.sh
build_tools/python_deploy/install_windows_deps.ps1
build_tools/python_deploy/build_windows_packages.ps1

Stashing some work before vacation / if someone else wants to help or follow along:

Branch with script changes / debugging: https://github.com/ScottTodd/iree/tree/infra-python3.13

For 3.13t, see https://docs.python.org/3.13/using/mac.html#installing-free-threaded-binaries and https://docs.python.org/3.13/using/windows.html#installing-free-threaded-binaries. There are scripts floating around in GitHub issues linked on that branch to set the Include_freethreaded option on Windows and -applyChoiceChangesXML ./choicechanges.plist on macOS
Debugging via github actions is slow. Next step is to run the scripts locally to debug what they are doing and where the packages are going on disk

Testing the runtime release builds with compiler builds and arm64 builds commented out on my fork using workflow_dispatch of https://github.com/ScottTodd/iree/actions/workflows/oneshot_candidate_release.yml, then watching the builds at https://github.com/ScottTodd/iree/actions/workflows/build_package.yml and checking the uploaded release artifacts at https://github.com/ScottTodd/iree/releases

This process should work for anyone, on their fork.

The (minimal!) changes that are need for IREE itself are in #18770.

@ScottTodd do we want to run tests with 3.13t as part of this issue as issue or can we close and add tests in a follow up?

@ScottTodd do we want to run tests with 3.13t as part of this issue as issue or can we close and add tests in a follow up?

Testing can be separate. I want to keep this open until we build 3.13t on all platforms (macOS + Windows) though.


fix: compatibility of php8.1 for slim3

function explod and preg_replace_callback
PHP message: PHP Deprecated:  xxxx(): Passing null to parameter #n ($xxx) of type xxx is deprecated /.../vendor/slim/slim/Slim/.../xxx.php on line nnn
See: https://www.php.net/manual/en/migration81.deprecated.php

@l0gicgate Can we disable phpunit with php8 for slim3? The phpunit that slim3 depends on is not compatible with php8

@l0gicgate I just disable phpunit test in matrix.php >= 8 and pull request target branch or pushed branch is 3.x in tests.yml

We are not doing any more releases besides security fixes to Slim 3. It's a rabbit hole to try and make this happen.

We are not doing any more releases besides security fixes to Slim 3. It's a rabbit hole to try and make this happen.

Ok, I will maintain in my own fork, thank you, close this PR


[CT-1529] [Feature] Support Python 3.11

Is this your first time submitting a feature request?

[X] I have read the expectations for open source contributors
[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt-snowflake functionality, rather than a Big Idea better suited to a discussion

Describe the feature
Main issue:
https://github.com/dbt-labs/dbt-core/issues/6147
Describe alternatives you've considered
No response
Who will this benefit?
No response
Are you interested in contributing this feature?
No response
Anything else?
No response

FYI: Seems to depend on package python-snowflake-connector upgrade to support 3.11:
https://github.com/snowflakedb/snowflake-connector-python/issues/1289
https://github.com/snowflakedb/snowflake-connector-python/issues/1345

FYI @dbt-labs/core-adapters, snowflake-connector-python==3.0.0 is now live (PyPI | GitHub)!

Any updates on this please ?

It's currently in review to be put into the 1.5 beta. It's stuck behind this ticket: https://github.com/dbt-labs/dbt-snowflake/pull/476, though we expect little work once that is approved. @Fleid can speak more to the timing.


Nuxt3 support?

Empty issues with no description will be automatically closed as no information is provided whether you are reporting a bug, feature request or something similar.
Next time, please take a minute and provide the appropriate information. If you have a question, feel free to use the official Discussions.


add test for interactive prompt

Add test for interactive prompt
Stop forcing host variable to localhost on all platforms
Make prompting actually work

Codecov Report

Merging #12 into master will decrease coverage by 6.09%.
The diff coverage is 49.33%.

@@            Coverage Diff             @@
##           master      #12      +/-   ##
==========================================
- Coverage   66.09%   60.00%   -6.10%
==========================================
  Files           2        2
  Lines         174      165       -9
==========================================
- Hits          115       99      -16
- Misses         59       66       +7

Impacted Files
Coverage Δ

pgsu/cli.py
0.00% <0.00%> (ø)

pgsu/__init__.py
65.13% <50.00%> (-6.75%)
:arrow_down:

Continue to review full report at Codecov.

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


Upgrade IntegrationTesting version to prevent hang during "dotnet publish"

Addresses https://github.com/aspnet/Hosting/issues/1451

There was a test failure on the debug build. Could be more flaky startup issues?

@dotnet-bot test Windows x64_debug

@dotnet-bot test Windows Debug x64 Build


Possibility to select filter style in the DataGrid

Feature request type
Enhance component
Component name
MudDataGrid
Is your feature request related to a problem?
The data grid has many powerful features that I really enjoy. However, I would love for the filtering options to be more customizable. From what I can tell, the type of filter applied to each column is determined by the data type passed into that column. For example, enums are assigned a dropdown filter, while strings receive a free-text filter. However, there are instances where a dropdown would be more useful in situations where my projects require me to use a string, resulting in a free-text filter instead of a dropdown. From what I can tell, and correct me if I am wrong, there is no convenient way to change the filter type on the Data Grid component(?).
I'm aware that it's possible to create a custom column with a custom filter, but this feels cumbersome when I need a dropdown for, say, 3 out of 4 columns. In such cases, I might feel like I could do without the DataGrid due to the lack of customizability. I believe that the ability to change the filter type would significantly improve the DataGrid component.
Describe the solution you'd like
I would love to see a default filter setting for each column, along with a property like "FilterType" or something similar, where users could specify whether they for example want the default, a dropdown select, or a free-text filter. I understand that certain filters, like incremental ones, would not work with strings or enums, but I think it would be fantastic if the dropdown option were more widely available.
Have you seen this feature anywhere else?
No response
Describe alternatives you've considered
No response
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

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

I was working on this prototype: https://github.com/MudBlazor/MudBlazor/pull/6626, which would allow the addition of UIs for new types, whether they are custom objects or types we currently do not have (TimeOnly, DateOnly, etc). It would also allow to replace existing filter UI for types. There were many problems, some were resolved, while others not. The main issue is that sometimes on re-rendering, Blazor throws an internal error: System.InvalidOperationException: 'The render handle is not yet assigned.' I didn’t use any "hacks," just the first-party component DynamicComponent from Microsoft, so I have no idea what the problem might be. If anyone has a better idea on how to implement this, please feel free to create a pull request.


Failed to build the required terminology resources

Here is the building output:
[root@foo76 onc-certification-g10-test-kit-3.1.0]# docker-compose -f terminology_compose.yml up --build
INFO[2022-09-19T02:22:48.697961729-07:00] parsed scheme: ""                             module=grpc
INFO[2022-09-19T02:22:48.698003127-07:00] scheme "" not registered, fallback to default scheme  module=grpc
INFO[2022-09-19T02:22:48.698022250-07:00] ccResolverWrapper: sending update to cc: {[{localhost   0 }]  }  module=grpc
INFO[2022-09-19T02:22:48.698033477-07:00] ClientConn switching balancer to "pick_first"  module=grpc
[+] Building 0.0s (0/0)
WARN[2022-09-19T02:22:48.794681961-07:00] grpc: addrConn.createTransport failed to connect to {localhost   0 }. Err :connection error: desc = "transport: Error while dialing only one connection allowed". Reconnecting...  module[+] Building 0.0s (0/0)
INFO[2022-09-19T02:22:48.890677924-07:00] parsed scheme: ""                             module=grpc
INFO[2022-09-19T02:22:48.890732946-07:00] scheme "" not registered, fallback to default scheme  module=grpc
INFO[2022-09-19T02:22:48.890753421-07:00] ccResolverWrapper: sending update to cc: {[{localhost   0 }]  }  module=grpc
WARN[2022-09-19T02:22:52.339076070-07:00] grpc: addrConn.createTransport failed to connect to {localhost   0 }. Err :connection error: desc = "transport: Error while dialing only one connection allowed". Reconnecting...  module=grpcinternal] load build definition from Dockerfile.terminology                                                                                0.1s
[+] Building 2.4s (16/16) FINISHED
 => [internal] load build definition from Dockerfile.terminology                                                                                0.1s
 => => transferring dockerfile: 44B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.1s
 => => transferring context: 35B                                                                                0.0s
 => [internal] load metadata for docker.io/library/ruby:2.7.2                                                                                1.4s
 => [internal] load build context                                                                                0.1s
 => => transferring context: 10.83kB                                                                                0.0s
 => [ 1/11] FROM docker.io/library/ruby:2.7.2@sha256:1dd0106849233fcd913b7c4608078fa1a53a5e3ce1af2a55e4d726b0d8868e2f                                                                                0.0s
 => CACHED [ 2/11] RUN mkdir -p /opt/inferno/                                                                                0.0s
 => CACHED [ 3/11] WORKDIR /opt/inferno/                                                                                0.0s
 => CACHED [ 4/11] RUN apt-get -y update &&     apt-get -y upgrade &&     apt-get install -y sqlite3                                                                                0.0s
 => CACHED [ 5/11] ADD *.gemspec /opt/inferno/                                                                                0.0s
 => CACHED [ 6/11] ADD Gemfile* /opt/inferno/                                                                                0.0s
 => CACHED [ 7/11] ADD lib/onc_certification_g10_test_kit/version.rb /opt/inferno//lib/onc_certification_g10_test_kit/version.rb                                                                                0.0s
 => CACHED [ 8/11] RUN gem install bundler                                                                                0.0s
 => CACHED [ 9/11] RUN bundle install                                                                                0.0s
 => CACHED [10/11] ADD . /opt/inferno/                                                                                0.0s
 => CACHED [11/11] RUN rm /bin/sh && ln -s /bin/bash /bin/sh                                                                                0.0s
 => exporting to image                                                                                0.3s
 => => exporting layers                                                                                0.0s
 => => writing image sha256:a74606fac89c2712df3cb9023766f20b6b7500164256cf1851234e94b29c3a92                                                                                0.0s
 => => naming to docker.io/library/onc-certification-g10-test-kit-310-terminology_builder                                                                                0.0s
WARN[0003] Found orphan containers ([onc-certification-g10-test-kit-310_inferno_run_4da0e574dca0 onc-certification-g10-test-kit-310-nginx-1 onc-certification-g10-test-kit-310-worker-1 onc-certification-g10-test-kit-310-inferno-1 onc-certification-g10-test-kit-310-redis-1 onc-certification-g10-test-kit-310_inferno_run_0ba7925efe18 onc-certification-g10-test-kit-310-validator_service-1]) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.
[+] Running 1/0
 ⠿ Container onc-certification-g10-test-kit-310-terminology_builder-1  Created                                                                                0.0s
Attaching to onc-certification-g10-test-kit-310-terminology_builder-1
time="2022-09-19T02:22:53.019087760-07:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
time="2022-09-19T02:22:53.019147522-07:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
time="2022-09-19T02:22:53.019161331-07:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
time="2022-09-19T02:22:53.019307328-07:00" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/cd201cbc5ec66889d89f36c2f0f75ebede767266e9343576e0e3d555f5533553 pid=106626 runtime=io.containerd.runc.v2
onc-certification-g10-test-kit-310-terminology_builder-1  | Prepare version 2019
onc-certification-g10-test-kit-310-terminology_builder-1  | 2019 UMLS Zip already exists; skipping UMLS download Rake task.
onc-certification-g10-test-kit-310-terminology_builder-1  | rake aborted!
onc-certification-g10-test-kit-310-terminology_builder-1  | Zip::Error: File tmp/terminology/2019/umls.zip has zero size. Did you mean to pass the create flag?
onc-certification-g10-test-kit-310-terminology_builder-1  | /usr/local/bundle/gems/rubyzip-2.3.2/lib/zip/file.rb:103:in `initialize'
onc-certification-g10-test-kit-310-terminology_builder-1  | /usr/local/bundle/gems/rubyzip-2.3.2/lib/zip/file.rb:121:in `new'
onc-certification-g10-test-kit-310-terminology_builder-1  | /usr/local/bundle/gems/rubyzip-2.3.2/lib/zip/file.rb:121:in `open'
onc-certification-g10-test-kit-310-terminology_builder-1  | /opt/inferno/lib/inferno/terminology/tasks/unzip_umls.rb:18:in `run'
onc-certification-g10-test-kit-310-terminology_builder-1  | /opt/inferno/Rakefile:42:in `block (2 levels) in '
onc-certification-g10-test-kit-310-terminology_builder-1  | /usr/local/bundle/gems/rake-13.0.6/exe/rake:27:in `'
onc-certification-g10-test-kit-310-terminology_builder-1  | /usr/local/bundle/gems/bundler-2.3.22/lib/bundler/cli/exec.rb:58:in `load'
onc-certification-g10-test-kit-310-terminology_builder-1  | /usr/local/bundle/gems/bundler-2.3.22/lib/bundler/cli/exec.rb:58:in `kernel_load'
onc-certification-g10-test-kit-310-terminology_builder-1  | /usr/local/bundle/gems/bundler-2.3.22/lib/bundler/cli/exec.rb:23:in `run'
onc-certification-g10-test-kit-310-terminology_builder-1  | /usr/local/bundle/gems/bundler-2.3.22/lib/bundler/cli.rb:486:in `exec'
onc-certification-g10-test-kit-310-terminology_builder-1  | /usr/local/bundle/gems/bundler-2.3.22/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
onc-certification-g10-test-kit-310-terminology_builder-1  | /usr/local/bundle/gems/bundler-2.3.22/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
onc-certification-g10-test-kit-310-terminology_builder-1  | /usr/local/bundle/gems/bundler-2.3.22/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
onc-certification-g10-test-kit-310-terminology_builder-1  | /usr/local/bundle/gems/bundler-2.3.22/lib/bundler/cli.rb:31:in `dispatch'
onc-certification-g10-test-kit-310-terminology_builder-1  | /usr/local/bundle/gems/bundler-2.3.22/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
onc-certification-g10-test-kit-310-terminology_builder-1  | /usr/local/bundle/gems/bundler-2.3.22/lib/bundler/cli.rb:25:in `start'
onc-certification-g10-test-kit-310-terminology_builder-1  | /usr/local/bundle/gems/bundler-2.3.22/exe/bundle:48:in `block in '
onc-certification-g10-test-kit-310-terminology_builder-1  | /usr/local/bundle/gems/bundler-2.3.22/lib/bundler/friendly_errors.rb:120:in `with_friendly_errors'
onc-certification-g10-test-kit-310-terminology_builder-1  | /usr/local/bundle/gems/bundler-2.3.22/exe/bundle:36:in `'
onc-certification-g10-test-kit-310-terminology_builder-1  | /usr/local/bundle/bin/bundle:23:in `load'
onc-certification-g10-test-kit-310-terminology_builder-1  | /usr/local/bundle/bin/bundle:23:in `'
onc-certification-g10-test-kit-310-terminology_builder-1  | Tasks: TOP => terminology:unzip_umls
onc-certification-g10-test-kit-310-terminology_builder-1  | (See full trace by running task with --trace)
INFO[2022-09-19T02:22:55.096635154-07:00] ignoring event                                container=cd201cbc5ec66889d89f36c2f0f75ebede767266e9343576e0e3d555f5533553 module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
INFO[2022-09-19T02:22:55.096847832-07:00] shim disconnected                             id=cd201cbc5ec66889d89f36c2f0f75ebede767266e9343576e0e3d555f5533553
WARN[2022-09-19T02:22:55.096914874-07:00] cleaning up after shim disconnected           id=cd201cbc5ec66889d89f36c2f0f75ebede767266e9343576e0e3d555f5533553 namespace=moby
INFO[2022-09-19T02:22:55.096929608-07:00] cleaning up dead shim
WARN[2022-09-19T02:22:55.135270551-07:00] cleanup warnings time="2022-09-19T02:22:55-07:00" level=info msg="starting signal loop" namespace=moby pid=106718 runtime=io.containerd.runc.v2
onc-certification-g10-test-kit-310-terminology_builder-1 exited with code 1

In the Terminology prerequisites setction, Prerequisites says "A copy of the Inferno repository, which contains the required Docker and Ruby files".
Can someone tell me what's the "Inferno repository"? And how to check that "setup.sh to initialize Inferno's database" is successful?

Also, I always get zero size umls.zip, is anything wrong?
[root@foo76 onc-certification-g10-test-kit-3.1.0]# ll tmp/terminology/*/umls.zip
-rw-r--r-- 1 root root 0 Sep 19 01:22 tmp/terminology/2019/umls.zip
-rw-r--r-- 1 root root 0 Sep 19 02:51 tmp/terminology/2021/umls.zip

If setup.sh was unsuccessful, you'd see database-related failures. This is the only repository you need to build the terminology.
If umls.zip has zero size, that means it is not downloading correctly. The logs you provided don't show a download attempt since the file already existed.

Thank @Jammjammjamm for the response.
I think setup.sh is successful, no error found. It seems the 12G memory is not enough. I extended the memory to 16G, and the building works. Thanks again.

Also, I always get zero size umls.zip, is anything wrong? [root@foo76 onc-certification-g10-test-kit-3.1.0]# ll tmp/terminology/*/umls.zip -rw-r--r-- 1 root root 0 Sep 19 01:22 tmp/terminology/2019/umls.zip -rw-r--r-- 1 root root 0 Sep 19 02:51 tmp/terminology/2021/umls.zip

It seems related to slow network. I'm starting to download the umls.zips manually.

@kiwisky
We published a new terminology build process with release v3.2.0. Could you verify if the new process works in your testing environment?
Thank you
~ Yunwei


Parameter template utilities.

A fuller implementation of PARAMS_TEMPLATE as per #9266.

[x] documentation is added or updated
[x] tests are added or updated

Very much WIP, this probably doesn't compile yet and certainly won't work.  There are mistakes in the PTR types e.g.

The more I'm looking at this, the more I like the idea (well, kinda sorta...  this is kind of a meta OSSL_PARAM, and I worry about further performance implications, but looking at the code, I imagine that I might worry too much).
I would like to see a variant where the caller can provide a block of memory to be used instead of dynamic allocation, as well as a template->param that populates a OSSL_PARAM array provided by the caller.  I don't imagine that should be very hard, apart from having to handles issues with the memory block or the provided OSSL_PARAM array being too small.
Also, documentation...  I assume we'll see that further on.
Another thing: naming.  These is a public API within libcrypto (libcrypto-private otherwise), and we have consistently prefixed those with ossl_ (and OSSL_ for types), I think that applies here as well.  With that, however, we're getting very long names, so I wonder if shorter names would be possible, such as OSSL_PARAMDEF instead of PARAM_DEFINITION and OSSL_PARAMTMPL instead of PARAM_TEMPLATE.
I'm also wondering if we should consider making these entirely public...  I'm not entirely sure about that idea, but it's worth giving it some thought.

Also, documentation... I assume we'll see that further on.

Currently outstanding.  I'd like to fixate the functionality to try to avoid have to make gratuitous changes.
I was following @mattcaswell's naming in #9266 to some extent.  The functions there are private so I agree about the nomenclature and will update.

would like to see a variant where the caller can provide a block of memory to be used instead of dynamic allocation, as well as a template->param that populates a OSSL_PARAM array provided by the caller. I don't imagine that should be very hard, apart from having to handles issues with the memory block or the provided OSSL_PARAM array being too small.

This is an interesting alternative.  I worry about the space management a little.  My alignment code is a bit coarse grained which could result in a fair bit of padding.  It could easily be refined so that strings and BN's are packed.

I'm also wondering if we should consider making these entirely public... I'm not entirely sure about that idea, but it's worth giving it some thought.

I had the same thought and had reservations as well.

It would be useful for 3rd party providers.

It would be useful for 3rd party providers.

Agreed, it would be useful.
My concerns are around what the long term costs would be for exposing them.  Once exposed, they effectively become permanent and immutable.  They'd also make public some structures that might be better left hidden -- the alignment and allocation hacks e.g.

We can always choose to expose things later but once exposed we can't retract them.

How are they useful for providers?

The 3rd party providers might wrap other providers for example?

But I of course agree that the API can start as private one and be converted to public when the need is really there.

The 3rd party providers might wrap other providers for example?

Ah, so for the need to "translate" parameters.  Yeah ok, that kind of makes sense.  It might be a bit extreme, though, as an incoming array of parameters already form a "template" to pass further down, unless there's a serious need to change data types.

Nomenclature changes addressed.
Test case completed.
Documentation to come.

Documentation added.

Why is the word "template" used?

I'm still missing variants with caller provided memory.

I think it's just one call that changes:
OSSL_PARAM *ossl_paramtmpl_to_param(OSSL_PARAMTMPL *tmpl, OSSL_PARAM *params, size_t params_n, void *buf, size_t buf_n);

Why is the word "template" used?

It's what @mattcaswell used :)

the non-allocating conversion function is done.

I think it's just one call that changes:

Because pushing material to the template doesn't allocate a data block?

Exactly, the data block is only allocated once the final size is known.
This avoids lots of mallocs and reallocs.
I decided to split the allocating and non-allocating calls into separate functions.  It kept things simple.

Exactly, the data block is only allocated once the final size is known.

... it seems I can't read code.  You're right, of course.

Ok, looks good to me so far.  I'll do another read through later today, just to be safe.

Even if Matt uses the word, I think it's a misnomer, or I am misunderstanding something.  What about this is re-used?  It's not even like a printf string.

This avoids lots of mallocs and reallocs.

This is really a premature optimization.  Are we really worried about this at this time ?

I decided to split the allocating and non-allocating calls into separate functions. It kept things simple.

I don't think anything that adds more than two dozen functions to the API (even if internal) can use the word simple.
Is there a demand for this?  Will future PR's be built on it, and can those authors post here to correct me?
Sorry if I sound too harsh, but sprouting up of the param stuff is starting to look a lot like Java API's in terms of completion for its own sake rather than for it's utility.

This is really a premature optimization. Are we really worried about this at this time ?

If someone thinks about it (I did) and it's simple to add (it obviously was), then I don't see why not.

Is there a demand for this?

This was inspired from @mattcaswell's #9266, so there's at least one demand. I can see using this as well...

If you don't like "template", please suggest something better.
I actually agree that "template" doesn't feel quite right, but I haven't been able to come up with anything better, so...

Just drop the word and call it parameter utilities.

Just drop the word and call it parameter utilities.

Is it the description that you want changed, or is it also the symbol names?  Are you asking for the API to be ossl_paramutil_* rather than ossl_paramtmpl_*?  Should the type OSSL_PARAMTMPL be renamed to OSSL_PARAMUTIL?
Trying to understand what you're saying...

Just drop the word and call it parameter utilities.

Is it the description that you want changed, or is it also the symbol names?

Well, yes, of course rename everything to remove the word template. If you think of a better word than template, then rename everything to use that word.

I said this before:

... but I haven't been able to come up with anything better, so...

Since neither of us can't figure out anything better, it's not likely to change. I can live with that

I did think of something better: utils.  If you don't like that, I think just removing the misleading word template is also better.

I've renamed everything to PARAM_BLD for parameter builder.  I also sqaushed the commit since most lines changed.
I'm unsure about raising specific errors from the calls.  As mentioned, there aren't many failure points.  None of the related code is raising "real" errors (which could be an issue in the other code rather than an example of what to do).

The open questions are about raising errors and using a caller allocated array for collation.  I'm not particularly in favour of either but would welcome other's input.

I'm unsure about raising specific errors from the calls.

What I worry about is for an error being signalled back all the way to the application without any suitable error number / message.  (note: I'm guilty of the same thing, so this is a reminder that I need to fix my own code as well)

I've raised proper errors in all places they can occur.

Regarding secure heap, I think there's a bit of an over reaction.  Let's think about this for a moment, when will it be used?  For transferring private keys, right?  How much non-private data do you expect to transfer in the same OSSL_PARAM?  I'm ready to assume that it's the public bits and nothing more.  Is that bad?  Also, I expect the allocated memory to be very short lived, i.e. that it will be freed directly after the appropriate _set_params has been called, which I expect will happen very soon after the OSSL_PARAM has been constructed.  Can we live with that amount of allocated secure heap for that short while?

No, it's a bug in this code. Having a flag to set other behavior is wrong. There's the risk that the flag won't get restored and the 'template' re-used. There's fragmentation of the secure heap, it is really designed for private keys sized power-of-two.
I feel strongly about this because Akamai had the same thing approach and we got burned, badly because we could not understand the code after the author left years ago. We spent millions to get new keys for all our customers.
It's very straightforward to fix this, just add a new "private bignum" type.  It is clean, consistent with the rest of the uses, and obvious what is going on.

What you suggest, though, leads to allocation of two blocks, one for private key material and the other for the rest. The final call that creates the params array will be less elegant.
On the other hand, this is internal functionality...

What you suggest, though, leads to allocation of two blocks, one for private key material and the other for the rest.

Well, yes.  That's the way everything else works.  You cannot have a single block of memory if private keys are being passed around, and it's wrong to dump everything into the secure heap if only one of the parameters is key material. To do it properly, without exposing keys and without putting public stuff where it doesn't belong, requires two blocks.  No way around it.

I agree with @richsalz, the use and implementation (limited, locked and on-swappable) of secure memory really restricts it's use to (some) secret and to private keys.

Ok, so if we go with a separate secure memory where only private bits are stored, that requires passing a reference to a secure memory pointer at the end, so the final builders could look like this:
OSSL_PARAM *ossl_param_bld_to_param(OSSL_PARAM_BLD *bld, void **secdata);
OSSL_PARAM *ossl_param_bld_to_param_ex(OSSL_PARAM_BLD *bld, void **secdata,
                                       OSSL_PARAM *params, size_t param_n,
                                       void *data, size_t data_n);

That final call would then look like this:
OSSL_PARAM_BLD bld;
void *secmem = NULL;
OSSL_PARAM *params = NULL;

... /* leave out all the pushes and stuff */

params = ossl_param_bld_to_param(&bld, &secmem);

... /* calling whatever _get_params or _set_params functions */

OPENSSL_free(params);
OPENSSL_secure_free(secmem);

Regardless of which variant is called, secure memory would always be allocated if there are private bits to transfer.
Let's see what @paulidale thinks of this idea.

I could live with Richard's suggestions but they are complicating things.  I'd prefer some variant of #9254, where each piece of memory is allocated independently in the appropriate location(s).  We'd lose the one free to get rid of everything but a function could be created to do this.

Yes, I suggested a free routine a day ago; https://github.com/openssl/openssl/pull/9305#discussion_r302326820

Out of curiosity, how much more complicated does it become with my suggestion? You need to keep track of two data blocks (so selective calculations), and you'd keep the allocated OSSL_PARAM in the unsecured data block. Or so I assume. Am I missing something?

I've updated #9254 to include secure memory (documentation and tests lacking still).

Updated to use secure storage, but lacking finished tests and documentation.

Travis is relevant, I'll fix tomorrow unless the alternative is preferred.

I'm lost on the sequence of events here...  is this essentially ready for approval or are you still working out some details, @paulidale?

After fixing the conflicts, this should be ready to go.
There will be changes to sync up  #9266 with this, but nothing should break because it wasn't done.

Conflicts fixed, open for final reviews.

Спасибо товарищ.  Merged to master.
I'm assuming that #9254 will now be closed without a merge.
The functionality there isn't exactly overlapping but it is close.


Make Gradle and all files Integrated into FlutterSDK in Android Folders Offline without additional download

When Create Project Flutter without having Internet Connection.
It say downloading gradle in first time and some files from Internet.
My Suggestion is Integrating Gradle and all files needed downloaded from Internet into Flutter SDK.
so it help create project and run your project without internet connection

@YahyaAtta There was an issue that has been partially mentioned at https://github.com/flutter/flutter/issues/118162. I'm closing this issue in favor of #22429 which has been discussed there.
You can leave there your comment and react an upvote to the original comment will help to raise the issue. Thank you!


feat: add a bug report feedback form

What does this PR do?
In this PR, a new feedback form template had been added, the developers and GitHub issue (new form added in this PR) feedback forms were refactored to use the new template, and SendFeedback.svelte, was updated to include the new feedback components of DevelopersFeedback and GitHubIssueFeedback
Screenshot / video of UI
Screencast from 2024-11-12 12-36-45.webm

What issues does this PR fix or reference?
Closes https://github.com/podman-desktop/podman-desktop/issues/9584

How to test this PR?

[X] Tests are covering the bug fix or the new feature

That's looking really promising @SoniaSandler !
How does that behave when the user doesn't have a github account or is not authenticated?
(I'm also guessing, the management of the system info + logs will come along later on)

@slemeur It looks like you have to have a GitHub account to open an issue, so if you are not connected to GitHub in your browser, the link from PD will direct you to the GitHub sign in page. From what I understood in the issue, this bug template will only help create a GitHub issue and nothing more, so without a GitHub account, there is not much this template can do.

we might want to include the os, install (version),

this is already tracked on each telemetry event

@benoitf the current collect info buttons don't do anything, they're just there as part of the design. There is already a separate issue to add the info collection code https://github.com/podman-desktop/podman-desktop/issues/9585
@axel7083 those are some good ideas, thanks! I'll probably use them in a separate PR as per Florent's suggestion

the current collect info buttons don't do anything,

If they do nothing, better to not have them.

@benoitf for now I'm done with this PR until additional reviews. The info collection buttons are not included here and the most recent commits focused on separating the different feedback templates into smaller components.

As for the GitHub submission, I can remove it from this PR, and add in a new one

I think it would help if you split with smaller chunks / other PRs
First one being just about refactoring ( nothing related to GitHub issue submission)
Same functionality/ feature, it should behave as before but will ease the addition of new changes
And then another one that will bring this part

removed GitHub submission from this PR, so for now, the Preview on GitHub button opens the issues page

for the description too?


Use src.elv.sh/pkg/rpc instead of net/rpc.

The net/rpc was removed (72fc2dbe4ac8f783f45f317326382880fcd5e431) but added again (8e117a287586bbce63ed132f21fafcff0c0e8344).
This PR removes it again to reduce binary size. (about 9,605 KB -> 8,391 KB, with go build cmd\elvish\main.go, on Windows)

Thanks, it seems that goimports was being a bit too helpful here...


The search bar only searches for pages

The search bar in the navigation on the left only searches for pages by default. When a page is found, the option to search in other sections (images, documents) is shown. However, this functionality is hidden when no page is found.
To me, this sounds backwards. No pages are found, so chances are the user wasn't searching for a page in the first place. Displaying other areas to be searched would be very helpful.
The same holds for images and documents: if there is a match, the other sections are shown. If there is no match, they are hidden. In my opinion they should be shown at all times, making search more user friendly.

Makes sense - thanks for the suggestion!

Do snippets get searched too?

Implemented in #1800


Add HttpRequestExample.scala

I'v implemented the HttpRequest example used in Beyond scala Lens
This example shows

how to use GenPrism to create Prism with case object. I found #219 but it seems outdated. (GenIso.obj instead of GenIso.unit)

sealed trait HttpMethod
case object GET   extends HttpMethod
case object POST  extends HttpMethod

val get: Prism[HttpMethod, Unit] = GenPrism[HttpMethod, GET.type] composeIso GenIso.unit[GET.type]
val post = GenPrism[HttpMethod, POST.type] composeIso GenIso.unit[POST.type]

how to use at and index to achieve the same result, and how they are different
Gen* macro, filterIndex usage

good idea! In a second step, I think we could move this example to the website and use tut to show the results

@aoiroaoino I removed the debug code. Thanks :)
@julien-truffaut The hop means Network Hop (distance between nodes). Since the r1 is a simulation of network Ping request , I used hop as a query string parameter.
// localhost:8080/ping?hop=5

val r1 = HttpRequest(
  GET,
  URI("localhost", 8080, "/ping", Map("hop" -> "5")),
  Map("socket_timeout" -> "20", "connection_timeout" -> "10"),
  "")

No it makes sense to show two different options, maybe it will be clearer if we would say something like
at("hop") composePrism some is equivalent to index("hop") because at returns Lens[S, Option[A]] while index returns Optional[S, A]

Thanks @1ambda for this contribution! I will merge it and I or someone else can try to turn this example into some tut examples later on.

Thanks :)


land sorting messed up

I did a draft today on drafts.in and added some lands (4x forest, 4x swamp, 4x island) while waiting for the next packs. I then realized that the basics use different art and are mixed up between basics and special:

I'm not excatly sure how drafts.in works and how the new Fate-Booster do with the extra gainlands and sometimes fetchlands.
But this is just wrong... :)

pr welcome

I can't help with that, I'm sorry. All I can do is to point out!

https://github.com/aeosynth/draft/commit/4006d3e5#diff-d3bb143777a80346d955f51c1f92568dR49

these lands are special because they are guaranteed to show up in the last slot of a booster

So in KTK these would still be considered 'common'?

yes. they are now common in frf as well, and only 'special' for the purposes of booster creation. the 'special' rarity is not shown to the client.

Hmm. This still leaves the basic lands from the set in cards.json:
  "mountain": {
    "color": "colorless",
    "name": "Mountain",
    "type": "Land",
    "cmc": 0,
    "sets": {
      "FRF": {
        "rarity": "basic",
        "url": "http://gatherer.wizards.com/Handlers/Image.ashx?multiverseid=391885&type=card"
      }
    }
  },

yes it does. we add basic lands to frf packs. the alternative is to not do so, in which case packs are not guaranteed to have the same amount of starting cards. we could add unhinged lands, but i like this better.

Yea, I just got it. Thanks!


Release OpenEBS provsioner v0.1.0 and add CHANGELOG for openebs-provisioner

Please add git tag openebs-provisioner-v0.1.0
@wongma7 & @humblec please review :)

/lgtm
/area openebs
Do we want to mirror the image at quay? i.e. create a repo quay.io/external-storage/openebs-provisioner:v0.1.0. if so I'll create the repo and we need to add something to https://github.com/kubernetes-incubator/external-storage/blob/master/deploy.sh so that git tag` causes a push.

Hi @wongma7,

Do we want to mirror the image at quay? i.e. create a repo quay.io/external-storage/openebs-provisioner:v0.1.0. if so I'll create the repo and we need to add something to https://github.com/kubernetes-incubator/external-storage/blob/master/deploy.sh so that git tag causes a push.

Yes, That would be great! Please do it. :)


SVG icons doesn't render properly on Safari

Hello,
Is it possible that this library does not support Safari?
SVG icons are rendering perfectly on every browser, but when I view it using my iPhone, the SVG icon becomes black & white.
However, using:

works.
Example:

Chrome:

Safari:

Any ideas?

@jayzienS If you open just the SVG file in Safari outside of Angular, does it display the shading? It may be an issue with the SVG for Safari than the library. The library looks like it is displaying the SVG, just not the shading.
Please attach the SVG if you want further help.

@jayzienS If you open just the SVG file in Safari outside of Angular, does it display the shading? It may be an issue with the SVG for Safari than the library. The library looks like it is displaying the SVG, just not the shading.
Please attach the SVG if you want further help.

Yeah, I just ran a test on a local server and it seems like displaying the SVG on a blank page outside the framework works properly.
Any idea what the issue could be?
There is the SVG file -
iostestsvg.zip
or
https://pastebin.com/sihnB0Nk

I've not been able to reproduce this. I just added use of your icon to the library's demo app for my test. I loaded the SVG using the library without any issue with Safari on a MacOS desktop, iPad, and iPhone. Here it is on Safari on an iPhone:

This is the HTML I used:

    <svg-icon src="images/testicon1.svg"></svg-icon>

Maybe there is a style in your app that is interfering with it?

Ahh, I just noticed you're not using the library in your example. You are loading it with the  tag not the <svg-icon> tag that is from the library.

I've not been able to reproduce this. I just added use of your icon to the library's demo app for my test. I loaded the SVG using the library without any issue with Safari on a MacOS desktop, iPad, and iPhone. Here it is on Safari on an iPhone:

This is the HTML I used:

    <svg-icon src="images/testicon1.svg"></svg-icon>

Maybe there is a style in your app that is interfering with it?

Ahh, I just noticed you're not using the library in your example. You are loading it with the  tag not the <svg-icon> tag that is from the library.

I gave the  element as a working example, when I use <svg-icon> it doesn't work unfortunately.
However, I ran a test on a fresh angular app using your library and indeed it renders properly, which leads me to the conclusion that something in my app is interfering.
I will do some deep researching into this, thanks for your assistance anyway!


Updated json for Ruby 2.2.2 compatibility

Running bundle install against Ruby 2.2.2, brings up this error:
    too few arguments provided to function-like macro invocation
This was happening because the old version of json, 1.8.0 is
incompatible with Ruby version 2.2.0 and up.
Github issues documentation of incompatibility:
https://github.com/flori/json/issues/229
This commit upgrades json to 1.8.3

This is no longer an issue!  Gemfile.lock should not have been committed in the first place!


Allow for openapi files to be accepted with .yaml extensions

We currently only accept .yml files.

@alexthemayers I'm unable to reproduce this?


problem with coreml model on nnvm

when i run my coreml on nnvm, i encountered one issue:
AttributeError: 'module' object has no attribute 'concat'
then i check symbol.py in nnvm/python/nnvm folder, there is no concat definition in Symbol class.
i notice concat is defined in onnx.py, so, do i need to import onnx by myself? or what can i do it for this issue? thanks a lot.

Both Concat and concat can be used to make concatenation layers in mxnet but for coreml it's not the case. There is ConcatLayerParams for concatenation in coreml.py yet it has another name. What defined in onnx.py is for onnx, they are not the same thing. Both Concat and concat can be used to make concatenation layers in mxnet but for coreml it's not the case.

could you please explain a little about your first sentence "...for coreml it's not the case".  does it mean that coreml didn't support concat ?
my problem is:
my original model is a caffe model. I  use coremltools, convert caffe model to coreml model, then when i run it on the nnvm, it said that" AttributeError: 'module' object has no attribute 'concat'" .
The problem is in line 251 (ret = _sym.concat(ret, insyms[i], dim=1) ) in coreml.py. it is in def ConcatLayerParams. based on my understanding, _sym.concat is not implemented in symbol.py. that's the reason why i get this issues.  if i'm wrong, please correct me.
could you please tell me how to handle this issue? thanks in advance.

I see the problem. The concatenation op is registered as concatenate but is not used as-is. It's called concat in coreml.py instead of the correct one, concatenate. Rename it and it should work fine. I will PR that.

thanks @PENGUINLIONG for fixing this issue


Add extension context to context

I thought I would need it, but it doesn't look like it, so I will just postpone this until I do.


Debian (Jessie) install error

Full Log => npm-debug.txt
ric@Zbox:~$ npm install steem --save
npm WARN engine<EMAIL_ADDRESS>wanted: {"node":">=4.0"} (current: {"node":"0.10.29","npm":"1.4.21"})
\

<EMAIL_ADDRESS>postinstall /home/ric/node_modules/steem
cross-env scripts/post-install.js

/home/ric/node_modules/steem/node_modules/cross-env/dist/variable.js:14
var pathLikeEnvVarWhitelist = new Set(['PATH', 'NODE_PATH']);
^
ReferenceError: Set is not defined
at Object. (/home/ric/node_modules/steem/node_modules/cross-env/dist/variable.js:14:35)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (/home/ric/node_modules/steem/node_modules/cross-env/dist/index.js:11:17)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian
npm ERR<EMAIL_ADDRESS>postinstall: cross-env scripts/post-install.js
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
npm ERR! This is most likely a problem with the steem package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     cross-env scripts/post-install.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls steem
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 3.16.0-4-amd64
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install" "steem" "--save"
npm ERR! cwd /home/ric
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.21
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /home/ric/npm-debug.log
npm ERR! not ok code 0

Update your node and npm version. Your version is very old

The minimal supported version is v4, as stated in cross-env's warning message


remove superpixels of the background in 3d partitioning app

App pull request

[ ] This is a new app
[x] I am improving an existing app (redesigns/code "makeovers")

About

Current gallery app URL: https://dash-gallery.plotly.host/dash-3d-image-partitioning/

This PR removes superpixels of the background, which gives a cleaner look.
New:

Current:

Thanks @nicholas-esterer !


Cannot profile during reload

run from master ./scripts/code.sh
open dev tools
start CPU profiling (more tools > JavaScript profiler)
(alternatively start performance profiling from the performance tab)
reload the window via ctrl+r
profiling doesn't work, reload does work

This is somewhat severe because it doesn't allow us to profile startup properly

Cannot reproduce on macOS 10.15.6, possibly Big Sur related?

related to https://github.com/microsoft/vscode/issues/111827?

Seems to be an issue with MSFT Defender ATP for mac...

I reported this to them, lets see what we hear back

Closing as issue is not with the runtime.


[AAP-12383] Standalone RQ scheduler

Install rq-scheduler.
Add all-in-one management command scheduler, that performs cleanup of previously scheduled jobs, adds jobs specified in settings and executes RQ scheduler.
Add new service to the docker development environment and K8S environment.
Fix existing delated jobs.

Hi @cutwater, as we agreed, I take the ownership of this PR. thanks for everything.
Closed in favor of: https://github.com/ansible/eda-server/pull/321


Set Device Plugin Image at controller level

Previously the device plugin image would be set per Onload CR, this could potentially lead to confusion since (we expect) most users won't need to change the device plugin image nor have fine-grained control of the image. Additionally, since we have built the controller with certain assumptions of the device plugin image it should lower the chances that a user sets this to an incompatible value.
I have left a field for the ImagePullPolicy in the DevicePluginSpec struct, though I'm wondering how necessary that is.
Testing done
Tested in virtualised cluster, when an onload CR is created it creates the device plugin correctly.
Since the value of the device plugin image is set at operator deploy time, I have found that the best way to deploy the operator is with the command
make deploy IMG=... DEVICE_IMG=...

https://github.com/Xilinx-CNS/kubernetes-onload/blob/master/DEVELOPING.md refers to devicePluginImage: also needs updating.


Automatic metrics instrumentation

Hello,
currently in a discovering phase of this project and noticed one thing. We have automatic instrumentation in case of tracing for http/grpc and some other stuff. But they only provide tracing for now and not any auto generated metrics (Like http request count for example). I also couldn't find any information regarding this, but I noticed, that it's always called automatic tracing. So now my question is, if this is something that is up to the plugin to provide, currently not supported, or left out by design?

[ ] This only affects the JavaScript OpenTelemetry library
[x] This may affect other libraries, but I would like to get opinions here first

It has been requested in the past there: https://github.com/open-telemetry/opentelemetry-js/issues/955 and https://github.com/open-telemetry/opentelemetry-js/issues/623, there is currently this PR (https://github.com/open-telemetry/opentelemetry-js/pull/1305) that tries to add metrics support in OT plugins

@vmarchaud
Thanks, apparently I just searched for the wrong terms, sorry😢
Will close this, and it is a duplicate of #623 and #955


feat: add support for Kong Enterprise RBAC resources

This takes the patch from #271 and adds in some machinery to avoid any potential breakage for existing users.
Please see https://github.com/Kong/deck/pull/271#issuecomment-785917323 for reasoning behind additional commits on top of the initial patch.
Please review commit-by-commit.
Fix #270

cc @tjrivera

Issues and points of interest found in user/black box testing:

Endpoint permissions with a non-existent workspace simply fail and no _workspace simply fail:while processing event: {Create} rbac-endpointpermission 22021df1-864f-42db-a477-74860a659c87-nonono-* failed: HTTP status 404 (message: "Workspace nonono does not exist")

This is probably expected--decK normally requires you handle all transactions on a per-workspace basis. This poses a bit of a challenge since roles with permissions in multiple workspaces are supported, albeit not perfectly (the GUI doesn't really handle them effectively).
reset lacks the --rbac-resources-only flag. It does not reset RBAC resources when run without it.
Roles with no name cause a segfault: no-name.yaml.txt
Permissions with no workspace cause a segfault: no-workspace.yaml.txt

Some of the above are easy to fix: https://github.com/Kong/deck/pull/278

Roles without names segfaulting isn't easy to address within the existing structure of file/builder.go. We don't have any existing pattern of logging and skipping invalid resources or returning errors when this happens, and other resources, e.g. services appear to have a similar segfault path. We could do something like this:        for _, r := range b.targetContent.RBACRoles {
                r := r
                if utils.Empty(r.ID) {
+                       if utils.Empty(r.Name) {
+                               b.err = errors.New("RBAC role lacks name")
+                               return
+                       }
                        role, err := b.currentState.RBACRoles.Get(*r.Name)

though that's not particularly graceful, since it just fails state building entirely and doesn't proceed onward. Functionally that's equivalent to the segfault, though it's a bit less ugly.
DELETEs not working is due to some odd admin API behavior. Permission admin API endpoints include the permission endpoint in the path, and the permission sometimes includes a leading slash (e.g. /acls) and sometimes does not (* is the only such endpoint AFAIK). Calls from Manager omit the leading slash, e.g. DELETE /rbac/roles/a79bdf2b-8844-424d-b6fc-97490cc6fe1d/endpoints/default/acls/*, whereas we include it DELETE /rbac/roles/a79bdf2b-8844-424d-b6fc-97490cc6fe1d/endpoints/default//acls/*. Our PATCHes also use the double slash, but for some reason, those succeed, whereas DELETEs do not (rather, they 204, but the permission remains). We can't just chop that leading slash off entirely with something like:@@ -18,6 +19,8 @@ func rbacEndpointPermissionFromStruct(arg diff.Event) *state.RBACEndpointPermiss
                panic("unexpected type, expected *state.RBACEndpointPermission")
        }

+       trimmed := strings.TrimLeft(*ep.Endpoint, "/")
+       ep.Endpoint = &trimmed
        return ep
 }

since that makes PATCHEs start 404ing--they require the //. DELETEs succeed, though they do throw a spurious while post processing event: entity not found after. POSTs succeed, since Kong accepts a body like {"workspace":"*","endpoint":"wat","actions":"delete,create,update,read"} (it automatically appends the leading /). The discrepancy in the verb behaviors suggests we'd need to handle this in go-kong with endpoint-specific logic. We apparently already have that for GETs, but not for DELETEs.

Thanks for the great feedback @rainest!

Endpoint permissions with a non-existent workspace simply fail and no _workspace simply fail

As you said, we can't do anything about this.

Roles with no name cause a segfault

Permissions with no workspace cause a segfault

We can take care of this using https://github.com/Kong/deck/pull/278#discussion_r583425002

Permission deletes do not work

This is solvable. We need to change the endpoint when it is passed on to go-kong and not in the FromStruct method. That will delete the permission in Kong and not cause the postProcess error.

@tjrivera Would you mind taking this PR for a spin and letting us know if it works for your environment and use-case?
@rainest Any other comments?

I was able to build and test this branch today. Everything works as expected. Thanks, @hbagdi, and @rainest for the help in getting this over the finish line!

Amazing, thanks for all your hard work and making this possible, @tjrivera!

@tjrivera FYI, we will have a release of decK with a few other features in a couple of weeks and this will be included then.

Awesome! great to see! Thanks @hbagdi and @rainest!


forward_t for BatchNorm printing wrong value?

https://docs.rs/tch/latest/src/tch/nn/batch_norm.rs.html#92-111
at line 95 why not print the dim and nd over size()?  I am new to rust so I am not sure if im missing something here.
I ran into this error message
thread 'main' panicked at 'expected an input tensor with 2 or 3 dims, got [2]
and was wondering if this was intended.

I've pushed some small changes to make the error message slightly more explicit (dim is just the length of size() so size() gives more information and could be useful to locate the actually problematic tensor but mentioning both sounds reasonable).


Can you add some option for "Spesific Language" to option "Export/Import txt/json file"

Hello, could you please make an additional Specific Language selection option for the Export/Import process of txt/json files.
Like during the Export process to a txt file, it can only be in English, without having to load other languages. Including the import process as well.
Thanks for help.

Owh... I gonna test it... Thanks for answering.


Adds  field binding for filters

@PascalSenn  can you fix the two formatting issues? I will merge after that.


ShowFilterIcon does not work on PropertyColumn

Bug type
Component
Component name
MudDataGrid - Columns - PropertyColumn
What happened?
Given the following HTML configuration, the ShowFilterIcon seemingly does not work.
<MudDataGrid @ref="_dataGrid" ColumnResizeMode="ResizeMode.Column" Items="_servicesData"
             Bordered="true" Striped="true" Hover="true" Dense="true" Filterable="true"
             Groupable="false"<EMAIL_ADDRESS>FilterMode="DataGridFilterMode.ColumnFilterRow"
             ServerData="ServiceRowsDataHandler">
    <ToolBarContent>
        <MudText Typo="Typo.h6">Services</MudText>
    </ToolBarContent>
    <Columns>
        <PropertyColumn Property="x => x.ServiceId" Title="Id" CellStyle="width:100px;" ShowFilterIcon="false" ShowColumnOptions="false" />
        <PropertyColumn Property="x => x.ServiceName" Title="Name" ShowFilterIcon="false" />

        <TemplateColumn Filterable="false" Sortable="false">
            <CellTemplate>
                <MudStack Row>
                    <MudIconButton OnClick="() => UpdateService(context.Item.ServiceId)" Icon="fas fa-edit" Title="Update"<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>                </MudStack>
            </CellTemplate>
        </TemplateColumn>
    </Columns>
    <PagerContent>
        <MudDataGridPager T="ServiceRowDto" PageSizeOptions="new []{ 10, 25, 50, 100}" />
    </PagerContent>
</MudDataGrid>

Expected behavior
The expected behavior is that the Filter Icons should not be shown.  The only thing I expect to see on the filter row is the Search input box with the placeholder of "Filter Value" displayed.
The reason I want this is because the ID column is very narrow and if I want to have the row filter, I am being forced to make it wide enough to accommodate the search input and search icons when all I really want is the search input.  Currently, the icons overlay the input making it not possible to access unless I extend the width of that column dramatically.
Reproduction link
https://try.mudblazor.com/snippet/mOQRPPkwdGRKflEq
Reproduction steps
It's immediately obvious once the component renders
Relevant log output
No response
Version (bug)
6.10.0
Version (working)
No response
What browsers are you seeing the problem on?
Chrome
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

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

I think this is important too: I've made a similar repro where you can see that ShowFilterIcons is not working even if it's put in the MudDataGrid declaration: https://try.mudblazor.com/snippet/wkmSOMuXyXJrkRyx.
Please note this happens only when you have FilterMode="DataGridFilterMode.ColumnFilterRow".
This is important since in some scenarios you don't want the user to be able to choose which kind of filter should be applied (contains rather then equal etc, for strings).
Furthermore, the documentation says Shows icons for each column filter. Defaults to true. Can be overridden for individual columns via ShowFilterIcon, so there is no mention of the FilterMode.
Workaround: as a temporary workaround, it is possible to hide the element with CSS, adding the following CSS only in the interested component:
<style>
/* Hide buttons and mud-menu only in the last row of the table head */
.mud-table-head .mud-table-row:last-child button,
.mud-table-head .mud-table-row:last-child .mud-menu {
  display: none;
}
</style>


Suggestion to add step

Lab Name: Create a composite model
Task: Set up Power BI Desktop
Step: 5-6
Issue Type: blocking
Description of issue: Step needed between the current steps 5 & 6
Repro steps (please include screenshot if applicable):

After selecting load (Step #5), I am asked to select the connection before the encryption window appears (Step #6). I suggest adding a step: "On the Windows tab, select Use my current credentials and select Connect".

Thank you @sherzyang - this has been updated!


Please report these packages: zeromq32

ping @staticfloat.
INFO: Building ZMQ
WARNING: The following packages do not have relocatable bottles, installation may fail!
Please report these packages to https://github.com/JuliaLang/Homebrew.jl:
  staticfloat/juliadeps/zeromq32

The build looks like it succeeded:
INFO: Building ZMQ
WARNING: The following packages do not have relocatable bottles, installation may fail!
Please report these packages to https://github.com/JuliaLang/Homebrew.jl:
  staticfloat/juliadeps/zeromq32
==> Installing libpgm from staticfloat/juliatranslated
==> Downloading https://homebrew.bintray.com/bottles/libpgm-5.2.122.sierra.bottle.1.tar.gz
######################################################################## 100.0%
==> Pouring libpgm-5.2.122.sierra.bottle.1.tar.gz
🍺  /Users/solver/.julia/v0.5/Homebrew/deps/usr/Cellar/libpgm/5.2.122: 27 files, 823.2K
Warning: Already linked: /Users/solver/.julia/v0.5/Homebrew/deps/usr/Cellar/libpgm/5.2.122
==> Installing zeromq32 from staticfloat/juliadeps
==> Installing dependencies for staticfloat/juliadeps/zeromq32: pkg-config
==> Installing staticfloat/juliadeps/zeromq32 dependency: pkg-config
==> Using the sandbox
==> Downloading https://pkgconfig.freedesktop.org/releases/pkg-config-0.29.1.tar.gz
######################################################################## 100.0%
==> ./configure --prefix=/Users/solver/.julia/v0.5/Homebrew/deps/usr/Cellar/pkg-config/0.29.1_2 --disable-host-tool --with-internal-glib --with-pc-path=/Users/solver/.julia/v0.5/Homebrew/
==> make
==> make check
==> make install
🍺  /Users/solver/.julia/v0.5/Homebrew/deps/usr/Cellar/pkg-config/0.29.1_2: 10 files, 627.5K, built in 1 minute 32 seconds
==> Installing staticfloat/juliadeps/zeromq32
==> Downloading http://download.zeromq.org/zeromq-3.2.5.tar.gz
==> Downloading from https://ia600403.us.archive.org/10/items/zeromq_3.2.5/zeromq-3.2.5.tar.gz
######################################################################## 100.0%
Warning: Cannot verify integrity of zeromq32-3.2.5.tar.gz
A checksum was not provided for this resource
For your reference the SHA256 is: 09653e56a466683edb2f87ee025c4de55b8740df69481b9d7da98748f0c92124
==> ./configure --prefix=/Users/solver/.julia/v0.5/Homebrew/deps/usr/Cellar/zeromq32/3.2.5 --with-system-pgm
==> make
==> make install
🍺  /Users/solver/.julia/v0.5/Homebrew/deps/usr/Cellar/zeromq32/3.2.5: 55 files, 2.2M, built in 33 seconds
Warning: Already linked: /Users/solver/.julia/v0.5/Homebrew/deps/usr/Cellar/zeromq32/3.2.5
INFO: Building IJulia
…

the ping @staticfloat needs to have the backticks taken off, should adjust the issue and pr templates

I think the root cause is you upgraded to Sierra before Elliot has had a chance to build juliadeps bottles for it.

Yep, this is the price of being an early adopter.  I've got the disk image for Sierra all ready, next I need to set the buildbot up and build all the bottles on it.

This should be addressed now, please let me know if you have any further issues.


Fix the bug in the allemp contact that can lead to unexpected error

In the addemp function, the _wallet_ddress parameter is passed as an argument, but it is not used anywhere within the function. This can cause confusion and potential issues when trying to store or access the wallet address of an employee.
To fix this bug, I removed the _wallet_ddress parameter from the function if it is not needed, also updated the logic to store and utilize the wallet address appropriately within the contract.
Additionally, please note that the allemp contract doesn't implement any access control mechanisms, allowing anyone to call the addemp function and deploy a new Sal contract.

Hi @Vikash-8090-Yadav assign me this, so I could raise a Pr

You raised  the pr fro this , if yes please linked the pr no. Thanks


📥 Add downloads to page/project frontmatter and site config

Previously, when you built a MyST site, all the exports defined on a page became Downloads and there was no other way to define additional or different downloads.
This PR adds downloads to page/project frontmatter as a place to specify (1) paths to local files and/or (2) export id values. Then, when you build your site, no longer do all the exports show up as downloads but only the specific downloads you specify.
This also makes improvements to site actions outlined here: https://github.com/executablebooks/mystmd/pull/1048

TODO: Enable assigning a title to download, as an alternative to the file name. We do not currently allow this for page exports, so maybe it can be an enhancement in a separate PR? But we do allow it for site actions so there is some precedent.

Adding a title is defintiely a good idea, currently with just exports themes are left to guess at what to put on the UI (https://github.com/executablebooks/myst-theme/blob/ef36c695035ae6895e7d022c9d00c5016d6c6c8e/themes/article/app/components/Downloads.tsx#L4) and with arbitrary downloads adding the filename is not a good option. So a title will benefit the themes well in both cases 👍

One last thing this needs is differentiation between downloads: undefined and downloads: [] - Pretty sure currently those both coerce to [] on the site config; we need to make sure we keep the differentiation.


Vue 3 support

Hey! Are you aware that this library doesn't work with vue 3 and do you have plans to fix it?
I'm getting this error:

I believe this is because you can't extend Vue anymore, which is happening here: https://github.com/NightCatSama/vue-slider-component/blob/master/lib/vue-slider.tsx#L48
Let me know if there's anything I can do to help - although I'm completely unfamiliar with this library's code.

Sorry, it is not yet compatible with Vue3.
It will be compatible when the stable version of vue3 is released.

The next version with vue3 support has been released, but it's still in beta, if you find any bugs you can report back to me!
$ yarn add vue-slider-component@next
# npm install vue-slider-component@next --save


⚠ Bofrost.be has degraded performance

In f0bf7d1, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1111 ms

Resolved: Bofrost.be performance has improved in d7e1caf after 29 minutes.


Running Passport install during installation

Thanks for the great package. 👍
I am looking to add extra artisan command to the installation process, I couldn't find it anywhere. For eg php artisan passport:install
I tried hacking into package and in DatabaseManager.php I have added like following
try{
            Artisan::call('passport:install', ["--force"=> true], $outputLog);
            Artisan::call('migrate', ["--force"=> true], $outputLog);
        }

but I get the following error
There are no commands defined in the "passport" namespace.

Can someone answer this? not sure why it was closed. I tried the documentation too but couldn't find anything.

Hi,
Pull in the last version 4.0.1.
I have just added an event that fires when the install is done RachidLaasri\LaravelInstaller\Events\ LaravelInstallerFinished. Create a listener for that and run whatever code you want to.

Thanks a lot for the reply, yeah its working. Now I have a problem when installing, it fires migration but it is not migrating vendor migrations.

Can you explain more?

I am closing this because it seems inactive. If you still facing the same issue, feel free to reopen it.
Thank you.

since am new to laravel , can u please provide more detail about adding a listener to your event ??  i need the passport install to be executed at last ?? can anyone help ?

@alshoja
Adding a listener after the installer finishes is very simple. Follow the instructions on the Laravel documentations  and listen for when this event is raised: RachidLaasri\LaravelInstaller\Events\LaravelInstallerFinished.

I tried to create a listener and it was successful but the event is raised in the events folder that is in the vendor folder, so how could the listener catch the event raised from vendor section? and also I just put the passport artisan command in the constructor that is on the LaravelInstallerFinished class and it worked but I need it to be enabled in the listener folder on App\listeners,

Exactly, you should be able to listen for the event even if it’s inside the vendor folder.
Just put the full class namespace (like you did above) and attach your listener to it and it’ll work.

Thank you so much for the package, it is very helpfull for easy installation, it could be better if you add validations for database credentials for connection check

I will have a look into that in the future. Thank you for the suggestion.

No mention, can you please look into the issue #176 because even am to getting the same error?


refactor (utils.rs): revised some functions and added comments

added some functions
added comments to functions
added data-types to variables to avoid ambiguous-warnings

This isn't commented in the latest version
https://github.com/hypertensor-blockchain/hypertensor/blob/16a03dc32ee3ae85ad25745b0782478b5f642504/pallets/network/runtime-api/src/lib.rs#L8

i uncommented it as get_model_peers_submittable and get_model_peers_included have different purposes
one uses MinRequiredPeerConsensusInclusionEpochs while the other usesMinRequiredPeerConsensusSubmitEpochs


MaxViT's MbConv doesn't match article.

According to article, this block should be F -> 4 F -> F channel mapping, as authors use 4 for InvertedBottleneck's expansion.
But here hidden_dim is not used at all, and dim_in/dim_out are only used.
Given that you call this like MBConv(layer_dim, layer_dim), you actually use 1 for effective expansion rate (i.e. no expansion), which is likely undesired.
Also, original article uses GELU activation instead of SiLU, but I don't know whether this should be fixed too.
It should be
def MBConv(
    dim_in,
    dim_out,
    *,
    downsample,
    expansion_rate = 4,
    shrinkage_rate = 0.25,
    dropout = 0.
):
    hidden_dim = int(expansion_rate * dim_out)
    stride = 2 if downsample else 1

    net = nn.Sequential(
        nn.Conv2d(dim_in, hidden_dim, 1),
        nn.BatchNorm2d(hidden_dim),
        nn.GELU(),
        nn.Conv2d(hidden_dim, hidden_dim, 3, stride=stride, padding=1, groups=hidden_dim),
        nn.BatchNorm2d(hidden_dim),
        nn.GELU(),
        SqueezeExcitation(hidden_dim, shrinkage_rate=shrinkage_rate),
        nn.Conv2d(hidden_dim, dim_out, 1),
        nn.BatchNorm2d(dim_out),
    )

    if dim_in == dim_out and not downsample:
        net = MBConvResidual(net, dropout=dropout)

    return net

@arquolo Hi Paul and thank you for catching this error! https://github.com/lucidrains/vit-pytorch/commit/2c6dd7010af59a4e09c97104ccc54fca46eae42d


Pressing escape twice  and  A or B adds cell to the top of the notebook

Current behavior:
Press escape once from edit mode to leave edit mode but current cell is selected.
Press escape second time and the whole document is selected.
Press a or b -> adds a cell at the top of the note book.
Issue:
I find this behavior annoying because I inadvertently press escape twice (especially with a theme where the highlight is not very pronounced) and press a/b to add a cell on top of the notebook instead of before/after the cell as I intended
Proposed behavior:
Keep the current cell selected even with multiple escape keys

This should be solved in VS Code itself: https://github.com/microsoft/vscode/issues/121129

Resolved via https://github.com/microsoft/vscode/issues/121129