ocamlPackages.ocaml_sqlite3: 5.0.1 -> 5.0.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/ocaml4.10.0-sqlite3/versions.
meta.description for ocamlPackages.ocaml_sqlite3 is: "OCaml bindings to the SQLite 3 database access library"
meta.homepage for ocamlPackages.ocaml_sqlite3 is: "http://mmottl.github.io/sqlite3-ocaml/"
meta.changelog for ocamlPackages.ocaml_sqlite3 is: ""
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 5.0.2 with grep in /nix/store/vmh9pb63gf3km6wdh2p5nl2g8jw60b6v-ocaml4.10.0-sqlite3-5.0.2

directory tree listing: https://gist.github.com/8c9fd08b119e9b3de213dbf141ad3db4

du listing: https://gist.github.com/67a92595cb148e6440d1c05553d21de2

Rebuild report (if merged into master) (click to expand)

3830 total rebuild path(s)

1559 package rebuild(s)

1559 x86_64-linux rebuild(s)
1293 i686-linux rebuild(s)
57 x86_64-darwin rebuild(s)
921 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
atlassian-confluence
beancount
bpftool
bumblebee
cargo-flamegraph
chromium
clang_11
cmake-format
colmapWithCuda
crosvm
cryptodev
cudaPackages.cudatoolkit_10
cudaPackages.cudatoolkit_10_0
cudaPackages.cudatoolkit_10_1
cudaPackages.cudatoolkit_10_2
cudaPackages.cudatoolkit_6
cudaPackages.cudatoolkit_6_5
cudaPackages.cudatoolkit_7
cudaPackages.cudatoolkit_7_5
cudaPackages.cudatoolkit_8
cudaPackages.cudatoolkit_9
cudaPackages.cudatoolkit_9_0
cudaPackages.cudatoolkit_9_1
cudaPackages.cudatoolkit_9_2
cudatoolkit
cudatoolkit_10
cudatoolkit_10_0
cudatoolkit_10_1
cudatoolkit_10_2
cudatoolkit_6
cudatoolkit_6_5
cudatoolkit_7
cudatoolkit_7_5
cudatoolkit_8
cudatoolkit_9
cudatoolkit_9_0
cudatoolkit_9_1
cudatoolkit_9_2
cudnn
cudnn6_cudatoolkit_8
cudnn_cudatoolkit_10
cudnn_cudatoolkit_10_0
cudnn_cudatoolkit_10_1
cudnn_cudatoolkit_10_2
cudnn_cudatoolkit_7
cudnn_cudatoolkit_7_5
cudnn_cudatoolkit_8
cudnn_cudatoolkit_9
cudnn_cudatoolkit_9_0
cudnn_cudatoolkit_9_1

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/vmh9pb63gf3km6wdh2p5nl2g8jw60b6v-ocaml4.10.0-sqlite3-5.0.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ocamlPackages.ocaml_sqlite3 https://github.com/r-ryantm/nixpkgs/archive/0b27a6f30a1b602b0f3ae98cf492909ddf486c8d.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/vmh9pb63gf3km6wdh2p5nl2g8jw60b6v-ocaml4.10.0-sqlite3-5.0.2
ls -la /nix/store/vmh9pb63gf3km6wdh2p5nl2g8jw60b6v-ocaml4.10.0-sqlite3-5.0.2/bin

Pre-merge build results
NixPkgs review skipped

Maintainer pings
cc @maggesi @vbgl for testing.

Diff looks fine, and ocaml_sqlite3, sqlexpr, and ocsigen_server all build.


Add Verifier for ReportData

Current dependencies on/for this PR:

main

PR #1

PR #2

PR #3

PR #9

PR #10

PR #11

PR #12
PR #18

PR #20

created #28 to address the partial verification

@samdealy bumped for re-review due to argument docs cleanup


[bug]: LeaderAwareResourceWatcher does not regain leadership after network issues

Describe the bug
I have observed that the LeaderAwareResourceWatcher looses and never regains leadership after network issues.
To reproduce

LeaderAwareResourceWatcher.StartAsync()
Wait for LeaderAwareResourceWatcher to be connected
Create network issue (e.g. reset_peer with toxiproxy)
This instance stopped leading, stopping watcher. will be logged
Resolve network issue
This instance started leading, starting watcher. is not logged again

Expected behavior
This instance started leading, starting watcher. should be logged after network issue is resolved.
Screenshots
No response
Additional Context
Version: 8.0.0-pre.29

I think the LeaderElector.RunAsync() API is very confusing and not documented, but it seems like the OnStoppedLeading event is only called in the finally clause of RunAsync:
https://github.com/kubernetes-client/csharp/blob/15ad5bdfc451debbca2e0d23821cef4393885525/src/KubernetesClient/LeaderElection/LeaderElector.cs#L104-L108
Therefore I guess it is necessary to call RunAsync in a loop until the LeaderAwareResourceWatcher is stopped.

I've run into the same issues and have raised PR #783.

I can confirm this. Network issues completely mess up leader election and high availability, to the point that sometimes both pods run CR processing at the same time, and at other times none of the pods do any processing at all.
thanks @exextatic for looking into this. @buehler could you also have a look and opine please?


Unable to list all extensions installed on an Arc-enabled AKS cluster

Describe the bug
Running the following command in an Azure Cloud Shell produces a runtime error:
Command: az k8s-extension list --cluster-name  --resource-group  --cluster-type managedClusters
Error: ModuleNotFoundError: No module named 'azure.mgmt.relay'
Related command
az k8s-extension list --cluster-name  --resource-group  --cluster-type managedClusters
Errors
The command failed with an unexpected error. Here is the traceback:
No module named 'azure.mgmt.relay'
Traceback (most recent call last):
File "/usr/lib64/az/lib/python3.9/site-packages/knack/cli.py", line 233, in invoke
cmd_result = self.invocation.execute(args)
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/init.py", line 562, in execute
self.commands_loader.load_arguments(command)
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/init.py", line 521, in load_arguments
self.command_table[command].load_arguments()  # this loads the arguments via reflection
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/init.py", line 319, in load_arguments
super(AzCliCommand, self).load_arguments()
File "/usr/lib64/az/lib/python3.9/site-packages/knack/commands.py", line 104, in load_arguments
cmd_args = self.arguments_loader()
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/command_operation.py", line 125, in arguments_loader
op = self.get_op_handler(self.op_path)
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/command_operation.py", line 59, in get_op_handler
handler = import_module(mod_to_import)
File "/usr/lib/python3.9/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 850, in exec_module
File "", line 228, in _call_with_frames_removed
File "/home/john/.azure/cliextensions/k8s-extension/azext_k8s_extension/custom.py", line 30, in
from .partner_extensions.AzureMLKubernetes import AzureMLKubernetes
File "/home/john/.azure/cliextensions/k8s-extension/azext_k8s_extension/partner_extensions/AzureMLKubernetes.py", line 15, in
import azure.mgmt.relay
ModuleNotFoundError: No module named 'azure.mgmt.relay'
Issue script & Debug output
cli.knack.cli: Command arguments: ['k8s-extension', 'list', '--cluster-name', 'hcibox-aks', '--resource-group', 'aks-stackhci-rg', '--cluster-type', 'managedClusters', '--debug']
cli.knack.cli: init debug log:
Enable color in terminal.
cli.knack.cli: Event: Cli.PreExecute []
cli.knack.cli: Event: CommandParser.OnGlobalArgumentsCreate [<function CLILogging.on_global_arguments at 0x7f3a9698a160>, <function OutputProducer.on_global_arguments at 0x7f3a968a3d30>, <function CLIQuery.on_global_arguments at 0x7f3a9683a310>]
cli.knack.cli: Event: CommandInvoker.OnPreCommandTableCreate []
cli.azure.cli.core: Modules found from index for 'k8s-extension': ['azext_k8s_extension']
cli.azure.cli.core: Loading command modules:
cli.azure.cli.core: Name                  Load Time    Groups  Commands
cli.azure.cli.core: Total (0)                 0.000         0         0
cli.azure.cli.core: These extensions are not installed and will be skipped: ['azext_next']
cli.azure.cli.core: Loading extensions:
cli.azure.cli.core: Name                  Load Time    Groups  Commands  Directory
cli.azure.cli.core: ai-examples               0.121         1         1  /usr/lib/python3.9/site-packages/azure-cli-extensions/ai-examples
cli.azure.cli.core: k8s-extension             0.003         2         9  /home/john/.azure/cliextensions/k8s-extension
cli.azure.cli.core: Total (2)                 0.123         3        10
cli.azure.cli.core: Loaded 3 groups, 10 commands.
cli.azure.cli.core: Found a match in the command table.
cli.azure.cli.core: Raw command  : k8s-extension list
cli.azure.cli.core: Command table: k8s-extension list
cli.knack.cli: Event: CommandInvoker.OnPreCommandTableTruncate [<function AzCliLogging.init_command_file_logging at 0x7f3a95cea820>]
cli.azure.cli.core.azlogging: metadata file logging enabled - writing logs to '/home/john/.azure/commands/2024-08-07.04-56-59.k8s-extension_list.1317.log'.
az_command_data_logger: command args: k8s-extension list --cluster-name {} --resource-group {} --cluster-type {} --debug
cli.knack.cli: Event: CommandInvoker.OnPreArgumentLoad [<function register_global_subscription_argument..add_subscription_parameter at 0x7f3a95c93430>]
cli.azure.cli.core.azclierror: Traceback (most recent call last):
File "/usr/lib64/az/lib/python3.9/site-packages/knack/cli.py", line 233, in invoke
cmd_result = self.invocation.execute(args)
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/init.py", line 562, in execute
self.commands_loader.load_arguments(command)
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/init.py", line 521, in load_arguments
self.command_table[command].load_arguments()  # this loads the arguments via reflection
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/init.py", line 319, in load_arguments
super(AzCliCommand, self).load_arguments()
File "/usr/lib64/az/lib/python3.9/site-packages/knack/commands.py", line 104, in load_arguments
cmd_args = self.arguments_loader()
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/command_operation.py", line 125, in arguments_loader
op = self.get_op_handler(self.op_path)
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/command_operation.py", line 59, in get_op_handler
handler = import_module(mod_to_import)
File "/usr/lib/python3.9/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 850, in exec_module
File "", line 228, in _call_with_frames_removed
File "/home/john/.azure/cliextensions/k8s-extension/azext_k8s_extension/custom.py", line 30, in
from .partner_extensions.AzureMLKubernetes import AzureMLKubernetes
File "/home/john/.azure/cliextensions/k8s-extension/azext_k8s_extension/partner_extensions/AzureMLKubernetes.py", line 15, in
import azure.mgmt.relay
ModuleNotFoundError: No module named 'azure.mgmt.relay'
cli.azure.cli.core.azclierror: The command failed with an unexpected error. Here is the traceback:
az_command_data_logger: The command failed with an unexpected error. Here is the traceback:
cli.azure.cli.core.azclierror: No module named 'azure.mgmt.relay'
Traceback (most recent call last):
File "/usr/lib64/az/lib/python3.9/site-packages/knack/cli.py", line 233, in invoke
cmd_result = self.invocation.execute(args)
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/init.py", line 562, in execute
self.commands_loader.load_arguments(command)
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/init.py", line 521, in load_arguments
self.command_table[command].load_arguments()  # this loads the arguments via reflection
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/init.py", line 319, in load_arguments
super(AzCliCommand, self).load_arguments()
File "/usr/lib64/az/lib/python3.9/site-packages/knack/commands.py", line 104, in load_arguments
cmd_args = self.arguments_loader()
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/command_operation.py", line 125, in arguments_loader
op = self.get_op_handler(self.op_path)
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/command_operation.py", line 59, in get_op_handler
handler = import_module(mod_to_import)
File "/usr/lib/python3.9/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 850, in exec_module
File "", line 228, in _call_with_frames_removed
File "/home/john/.azure/cliextensions/k8s-extension/azext_k8s_extension/custom.py", line 30, in
from .partner_extensions.AzureMLKubernetes import AzureMLKubernetes
File "/home/john/.azure/cliextensions/k8s-extension/azext_k8s_extension/partner_extensions/AzureMLKubernetes.py", line 15, in
import azure.mgmt.relay
ModuleNotFoundError: No module named 'azure.mgmt.relay'
az_command_data_logger: No module named 'azure.mgmt.relay'
Traceback (most recent call last):
File "/usr/lib64/az/lib/python3.9/site-packages/knack/cli.py", line 233, in invoke
cmd_result = self.invocation.execute(args)
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/init.py", line 562, in execute
self.commands_loader.load_arguments(command)
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/init.py", line 521, in load_arguments
self.command_table[command].load_arguments()  # this loads the arguments via reflection
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/init.py", line 319, in load_arguments
super(AzCliCommand, self).load_arguments()
File "/usr/lib64/az/lib/python3.9/site-packages/knack/commands.py", line 104, in load_arguments
cmd_args = self.arguments_loader()
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/command_operation.py", line 125, in arguments_loader
op = self.get_op_handler(self.op_path)
File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/command_operation.py", line 59, in get_op_handler
handler = import_module(mod_to_import)
File "/usr/lib/python3.9/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 850, in exec_module
File "", line 228, in _call_with_frames_removed
File "/home/john/.azure/cliextensions/k8s-extension/azext_k8s_extension/custom.py", line 30, in
from .partner_extensions.AzureMLKubernetes import AzureMLKubernetes
File "/home/john/.azure/cliextensions/k8s-extension/azext_k8s_extension/partner_extensions/AzureMLKubernetes.py", line 15, in
import azure.mgmt.relay
ModuleNotFoundError: No module named 'azure.mgmt.relay'
To check existing issues, please visit: https://github.com/Azure/azure-cli/issues
cli.knack.cli: Event: Cli.PostExecute [<function AzCliLogging.deinit_cmd_metadata_logging at 0x7f3a95ceaa60>]
az_command_data_logger: exit code: 1
cli.main: Command ran in 0.382 seconds (init: 0.120, invoke: 0.262)
telemetry.main: Begin splitting cli events and extra events, total events: 1
telemetry.client: Accumulated 0 events. Flush the clients.
telemetry.main: Finish splitting cli events and extra events, cli events: 1
telemetry.save: Save telemetry record of length 7876 in cache
telemetry.main: Begin creating telemetry upload process.
telemetry.process: Creating upload process: "/usr/bin/python3.9 /usr/lib/az/lib/python3.9/site-packages/azure/cli/telemetry/init.py /home/john/.azure"
telemetry.process: Return from creating process
telemetry.main: Finish creating telemetry upload process.
Expected behavior
Expected behaviour is no runtime error, and a list all extensions installed on the cluster to be returned.
Environment Summary
azure-cli                         2.62.0 *
core                              2.62.0 *
telemetry                          1.1.0
Extensions:
acrquery                           1.0.1
ai-examples                        0.2.5
appservice-kube                    0.1.8
connectedk8s                       1.9.0
customlocation                     0.1.3
k8s-configuration                  1.7.0
k8s-extension                      1.4.2
logic                              0.1.7
ml                                2.28.0
ssh                                2.0.5
Dependencies:
msal                              1.28.1
azure-mgmt-resource               23.1.1
Python location '/usr/bin/python3.9'
Extensions directory '/home/john/.azure/cliextensions'
Extensions system directory '/usr/lib/python3.9/site-packages/azure-cli-extensions'
Python (Linux) 3.9.19 (main, Mar 28 2024, 18:56:59)
[GCC 11.2.0]
Legal docs and information: aka.ms/AzureCliLegal
Additional context
No response

Thank you for opening this issue, we will look into it.


Make this project a pytest plugin

Codecov Report

Merging #11 into master will decrease coverage by 48.52%.
The diff coverage is 30.00%.

@@             Coverage Diff              @@
##            master      #11       +/-   ##
============================================
- Coverage   100.00%   51.47%   -48.53%
============================================
  Files            1        2        +1
  Lines           38       68       +30
============================================
- Hits            38       35        -3
- Misses           0       33       +33

Impacted Files
Coverage Δ

src/pytest_stepfunctions/plugin.py
30.00% <30.00%> (ø)

src/pytest_stepfunctions/services/aws_lambda.py
68.42% <0.00%> (-31.58%)
: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 542e0a2...2dd1770. Read the comment docs.


az containerapp create resets images for existing apps

This issue is a: (mark with an x)

[x] bug report -> please search issues before submitting
[x] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)

Issue description
Calls to az containerapp create without an explicit --image argument change the image of an existing container app to a k8s hello world image. We use this in our infrastructure scripts to set up container apps, configure their secrets and environment variables, and configure access with managed identities. We handle deploying revisions and images separately as part of a different deployment process. Ideally we would be able to just use az containerapp create to ensure our container app exists in a desired state before making further calls to containerapp secret set --secrets, containerapp update --set-env-vars, containerapp registry set, or whatever else we have going on for our apps.
Workaround
We invoke az containerapp show to decide if a call to az containerapp create is required.
Steps to reproduce

Invoke az containerapp create --name .. --environment .. as part of idempotent infrastructure automation, omitting --image
Invoke az containerapp update --image to deploy the application as part of our deployment automation
Invoke az containerapp create --name .. --environment .. as part of idempotent infrastructure automation, omitting --image

Expected behavior [What you expected to happen.]
Our application is still running.
Actual behavior [What actually happened.]
The k8s hello world sample has replaced our application.
Additional context
Nerds can debate idempotent vs effectively idempotent, if --image is implicitly included in what would be considered idempotent on a create invocation or not, and if Azure CLI even should be idempotent. I would like to keep any discussion human centric and focused on how a call to create replacing an existing and running app with a Hello World image would be surprising behavior that would be problematic for users just trying to get through their day.
Maybe az containerapp up has the desired intent, but it requires an image to be specified, which we handle during application deployment.

Hi, A create is doing a PUT operation and update is doing a PATCH.  The put will overwrite the existing values.

Yeah that makes sense as the technical cause of the behavior but as a user of az containerapp the outcome of invoking this command is surprising and I don't have an alternative command to use for this case.

To add some context to this with respect to expectations set by existing parts of the Azure CLI, azure webapps will not overwrite an existing deployment with a "Hello World" equivalent when az webapp create is invoked for an existing webapp.
https://learn.microsoft.com/en-us/cli/azure/webapp?view=azure-cli-latest#az-webapp-create

I kind of have the same problem, but I'm using Bicep.

I create the initial version of the container app using Bicep, for both staging and production. Like you, I would love to not specify a docker image, but the image is required, and so is the tag. So, I point it to the docker image, and use the latest tag.
Later I make an update to the container app and tag it with v2. I don't want to redeploy Bicep just to push a new version (it's slow and might push other infrastructure changes). So here I use az containerapp update ... -image:xxx:v2. So far so good.
But, the problem is that the next time I update the infrastructure (using Bicep) it will roll back this change to the latest tag.

It seems to me that there should be a way to update an existing app without changing the active version (both using Bicep or Azure CLI).
My workaround is to have a script that reads the tag of the current version and pass it as a parameter to Bicep. But this is complex, and there is a potential race condition.


Error when parsing  book with nested chapters

I get error when trying to pase tis book: https://www.kosmas.cz/knihy/257693/ostre-stribro/
/usr/local/lib/python3.11/site-packages/bs4/builder/__init__.py:545: XMLParsedAsHTMLWarning: It looks like you're parsing an XML document using an HTML parser. If this really is an HTML document (maybe it's XHTML?), you can ignore or filter this warning. If it's XML, you should know that using an XML parser will be more reliable. To parse this document as XML, make sure you have the lxml package installed, and pass the keyword argument `features="xml"` into the BeautifulSoup constructor.
  warnings.warn(

Could it be connectet to nested chapters ?

Hi @GamerClassN7. Looks like your error log is not completed for me.
I can only see the bellow log from your post which is normal warning from the underlying dependencies.

/usr/local/lib/python3.11/site-packages/bs4/builder/init.py:545: XMLParsedAsHTMLWarning: It looks like you're parsing an XML document using an HTML parser. If this really is an HTML document (maybe it's XHTML?), you can ignore or filter this warning. If it's XML, you should know that using an XML parser will be more reliable. To parse this document as XML, make sure you have the lxml package installed, and pass the keyword argument features="xml" into the BeautifulSoup constructor.
warnings.warn(

Hi @GamerClassN7. Looks like your error log is not completed for me.
I can only see the bellow log from your post which is normal warning from the underlying dependencies.

/usr/local/lib/python3.11/site-packages/bs4/builder/init.py:545: XMLParsedAsHTMLWarning: It looks like you're parsing an XML document using an HTML parser. If this really is an HTML document (maybe it's XHTML?), you can ignore or filter this warning. If it's XML, you should know that using an XML parser will be more reliable. To parse this document as XML, make sure you have the lxml package installed, and pass the keyword argument features="xml" into the BeautifulSoup constructor.
warnings.warn(

Sorry, for insufficient description @p0n1, in thee end it seems that problem is only half there since after converting the book all chapters are saved in incorrect order, ant that was the thing which mislead me that the XML parsing warning is root cause of the problem.  I can buy a book for testing purposes to help you troubleshoot the issue


Upgrade nanomsg binaries to version 0.8

Original NanoMsg is version 0.8 already:
http://nanomsg.org/download.html
It would be great to update your C# binding to the current version of native lib.
Thank you in advance!

I've been working on a 1.0 release, I'll close this when it is available.


Remove power-assert

power-assert is super useful tool, but:

It's sometimes mantainance burden on upgrade babel.
We're moving to ava.

So I'll remove it to make our build pipeline simple.
If we abandan to move to ava, then we may recover power-assert.

This change is

bors r+


Request: ability to write Blazor component libraries

One feature I'd love to see is the ability to write Blazor component libraries, where the code and UI (using the Razor pages) can be compiled to a DLL which can be packaged (e.g. Nuget) and re-used as a library.
This would
1 Make application development more modular than it currently is
1 Encourage an ecosystem of web components (both open source and commercial tools) which would also then foster greater adoption of Blazor
Hence it would be good to see both a Blazor web application template and a Blazor library template.

I think that's somewhat possible already on the new preview builds of the Razor engine. If I remember the new Razor Engine now allows to be compiled to a .Net standard library along with all its pages/cshtml and assets. The best part about the new build for that engine is that you have the ability to override the library page/views for more possibilities on how a vendor would make his component flexible.
Here's the ASP.NET Video discussing the it.
So I do think i'd be possible here since it uses the Razor engine for it's rendering for Blazor.

This is already the case. When Blazor's build system compiles your .cshtml files, they just turn into types in the application's .NET assembly. At runtime we don't see .cshtml as a concept at all - it's all just .NET types.
So if some of those .NET types happen to be in referenced assemblies (e.g., from NuGet packages), it makes no difference - that just works equally well.

Thanks for the clarification - is there a reason I could not see the generated types in a unit test assembly? All I could see was Program.cs.
Good work on Blazor by the way - I might have to stop using KnockoutJS if this becomes a product!

Do we need to "register" a component coming from a library into the Blazor app for it to be discoverable? or are all components found automatically at runtime?
I am trying to access a sample component from a library and cannot.

Currently it's necessary to add the following to your root _ViewImports.cshtml if you want components from external projects/packages to show up:
@addTagHelper *, AssemblyNameOfProjectOrPackage


Kubernetes Jobs

If this is the wrong place for a feature request, please comment on the best place to leave a feature request then close this issue.
I would love to be able to run a kubectl job (and wait until the job completes) via this plugin.
Let me know if that makes sense, thanks!

Hi @richardpringle, this is definitely the place to leave a feature request.
Currently it is already possible to use this plugin to run your job. Supply a manifest with kind: Job such as in this example, and it will run.
The part we currently don't support is waiting until the job is complete, but this can be added to the verification we already have for other kubernetes objects. Thanks for letting us know!

Ah, I guess I'm having issues since I have to delete the job first.
@stephenashank , do you have any recommendations for deleting a job from jenkins?
My main issue that I don't know how to configure kubectl on jenkins without using the gke-plugin (along with the gcloud oauth plugin).
Do you have any tips?

After authenticating with gcloud, it is possible to generate a kubeconfig entry as shown here: https://cloud.google.com/kubernetes-engine/docs/how-to/cluster-access-for-kubectl#generate_kubeconfig_entry
Then you can run any kubectl command and it should use your credentials. If you run those commands in the same shell script build step then it should work.


Apply hlint suggestions.

Issue Number
None.
Overview
This PR applies suggestions made by hlint.

bors try


Fix plaits~ compilation.

cf. https://github.com/porres/pd-else/pull/1503#issuecomment-1434831805

Hi, if I build with my regular make install objectsdir=../ command on the toplevel make file with pdlibbuilder, I don't build plaits~ I guess I need something special, like sfont~ needs, right? BTW, I never really tried compiling with [sfont~], sorry, it's vacation/summer time as you know and I've been also busy doing ELSE/Cyclone things. Since this new release seems ready to go I'd like to close the gates and try to see if I can compile it all and call it a release.
Now, if I go into the plaits~ directory, I can build it with the changes

It's all described in the updated README. Note that a relative objectsdir doesn't work for the subdir installs, so you must use an absolute path there now if you want to install sfont~ and/or plaits~ with the toplevel make. (Same goes for the pdincludedir if you need to set that.)
The TLDR is:

make all sfont plaits to build everything. (Can be skipped if you run the command below afterwards, because the install targets also make sure that everything is built first.)
make install sfont-install plaits-install objectsdir=$(pwd)/.. to install everything in the parent directory. Don't skip the $(pwd), or it won't work. Also, those trailing slashes aren't needed and actually may cause trouble on Windows in certain situations, cut that habit.

I should maybe send you another update of the README which also covers plaits~. Stay tuned.

There you go: #1516.

awesome, works like a charm. Will see now how it may or may not work with the script provided by @emviveros in my VM

ok, it seems I was able to edit and run the script by emviveros and it's going now... it should include plaits and sfont
BUT.......... I now see that the build I have done before here on the mac includes sfont~ exernal but it doesn't include the differently specified folders for each platform including the statically linked dependencies separately. Shouldn't it have done that?

I've not seen those scripts you're using on the VM, so I don't know how they're supposed to work and can't help you with this. You will have to ask emviveros for help. All I can tell you is that the Makefile targets I created do their job exactly as intended, if you use them correctly, as documented in the README.


The "new unidirectional limit 0 decreases the current limit: 3" error

Hello quicly community,
Very sorry for interrupting! I am a newbie of both QUIC and quicly. I built quicly master branch code successfully, and tried to connect google and Akamai QUIC servers, but met following errors:
$ ./cli quic.rocks 4433
transport close:code=0xa;frame=6;reason=163:new unidirectional limit 0 decreases the current limit: 3
$ ./cli ietf.akaquic.com 443
transport close:code=0xa;frame=0;reason=163:new unidirectional limit 0 decreases the current limit: 3

Can anyone give some advice on this issue? Thanks very much in advance!
Best Regards
Nan Xiao

I think this is an issue when you use a "generic" QUIC client that only supports one bidirectional stream to connect to a HTTP/3 server that assumes HTTP/3 is used even when the client does not send an ALPN.
cli is not a HTTP/3 client. Rather, it is a generic client that can request the use of any ALPN using -a option. But because it is a command line program (that uses stdin / stdout as bidirectional stream I/O), the command does not enable use of unidirectional streams; the advertised limit is zero.
OTOH, HTTP/3 requires use of unidirectional streams.
When the cli program is invoked without -a option, it does not send ALPN. But by looking at the error message sent from the servers, it looks like they are assuming that the protocol to be used is HTTP/3 when the client does not specify any, and complain that the properties required for HTTP/3 is not met.


Bug: On open, comics show download icon for already downloaded comics

When the application opens, the download comic icon is displayed for comics that have already been downloaded. Scrolling the table causes it to disappear, but it will reappear when the application is started again.

Fixed in #71.


OpenBSD support

OpenBSD doesn't have native rollup support. I don't know if this is the right way. Seems to work with very light testing on OpenBSD 7.5 with node 18.19.1 and Ubuntu 22.04 with node 20.16.0.

I was hoping there was some way to use it conditionally. No particular use case, but now I'm trying to use the compiled package with npm, npx and yarn methods and none work on OpenBSD. Running directly with node seems to work:
$ pwd
/home/ansible
$ doas pkg_add yarn
$ yarn add blossom-server-ts
$ yarn run blossom-server-ts
yarn run v1.22.21
warning package.json: No license field
$ /home/ansible/node_modules/.bin/blossom-server-ts
/bin/sh: /home/ansible/node_modules/.bin/blossom-server-ts: No such file or directory
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
$ ls -l /home/ansible/node_modules/.bin/blossom-server-ts
lrwxr-xr-x  1 ansible  ansible  35 Aug 18 11:42 /home/ansible/node_modules/.bin/blossom-server-ts -> ../blossom-server-ts/build/index.js
$ ls -l /home/ansible/node_modules/blossom-server-ts/build/index.js
-rwxr-xr-x  1 ansible  ansible  2515 Aug 18 11:42 /home/ansible/node_modules/blossom-server-ts/build/index.js
$ node /home/ansible/node_modules/.bin/blossom-server-ts
  blossom-server Dashboard started with admin XXX +0ms
  blossom-server Started app on port 3000 +12ms


Push to context can fail on entities

A very rare situation but it has been observed. This is likely caused by the way multithreaded access of ECS is currently handled.

Related to #10


Can't find a way to run ACTION_MANAGE_ALL_FILES_ACCESS_PERMISSION

How can I run e ACTION_MANAGE_ALL_FILES_ACCESS_PERMISSION intent
I checked out this page https://developer.android.com/reference/android/content/Intent#intent-structure but can't find it.
I need to figure out what to put as the action argument
I tried
android.settings.MANAGE_APP_ALL_FILES_ACCESS_PERMISSION
ACTION_MANAGE_ALL_FILES_ACCESS_PERMISSION
action_manage_all_files_access_permission
all of them failed with No Activity found to handle Intent
Sorry, I'm not an Android developer and I don't know all the Android-specific stuff.

    const String ACTION_MANAGE_APP_ALL_FILES_ACCESS_PERMISSION =
        'android.settings.MANAGE_APP_ALL_FILES_ACCESS_PERMISSION';

    final intent = AndroidIntent(
        action: ACTION_MANAGE_APP_ALL_FILES_ACCESS_PERMISSION,
        data: Uri.encodeFull('package:com.example.connectivity_test'));

    intent.launch();

Here is a link to the page from the android developer site:
https://developer.android.com/reference/android/provider/Settings#ACTION_MANAGE_APP_ALL_FILES_ACCESS_PERMISSION
A few things to note as you search for these actions. The actual string value of the action is specified in the documentation like this:
Constant Value: "android.settings.MANAGE_APP_ALL_FILES_ACCESS_PERMISSION"
The other part to note is that data is expected to be a Uri. Therefore I used the Uri.encodeFull method. I tested this on my phone and it worked. I hard-coded my package name, but I could have used the package_info_plus plugin to retrieve it.
https://pub.dev/packages/package_info_plus
PackageInfo packageInfo = await PackageInfo.fromPlatform();

Uri.encodeFull('package:${packageInfo.packageName}')


Handle Connection of an Additional Account

Scenario:

You are connected to a dapp with 2 accounts of your wallet of choice
You enable inside the wallet to allow a third account to interact with the dapp.

=> As of now nothing happens for the "useExtension" hook. Is there a way to observe new accounts getting enabled in the users wallet and refresh the useExtension hook?

talisman-connect has a wallet subscription function. It looks like we could use that.

This was solved here https://github.com/paritytech/useink/pull/56 via subscriptions


Refactor PrototypeClass

Refactor and cleanup PrototypeClass. We don't want this to be JS specific, although we can provide a subclass which does provide JS-alike behaviors.

The prototype library is basically dead right now, until I think of a direction I want to take it in. I'm closing this ticket.


Error in

Describe the bug
A clear and concise description of what the bug is.
Attempt nixos-rebuild switch and get an error
Steps To Reproduce
Steps to reproduce the behavior:

nixos-rebuild switch --verbose
...
...

Expected behavior
A clear and concise description of what you expected to happen.
Expect a nixos-rebuild switch
Log goes through entire process, but at end get an error:
$ nix-env -p /nix/var/nix/profiles/system --set /nix/store/fsj47fa8cnx8wvqaxyks2w69vbk40vyx-nixos-system-nixos-23.11pre541036.63678e9f3d3a
error: creating symlink from '/nix/var/nix/profiles/.0_system' to 'system-83-link': Permission denied
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.

system: "x86_64-linux"
host os: Linux 6.1.58, NixOS, 23.11 (Tapir), 23.11pre537656.7c9cc5a6e5d3
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.17.1
channels(root): "23.05-23.05, nixos, nixpkgs"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
output here

Have you attempted using sudo?

The boot or switch subcommands must be run as root or with --use-remote-sudo for obvious reasons.

Sorry, guys! Apologies for the obvious question...forgot to do that.
As a clearly non-technical NixOS user, I'm super happy and grateful for your work on this!


feat: Sync users with algolia

https://trello.com/c/57EivHKQ/1795-prepare-sync-of-users-between-squidex-and-algolia

i love it how nobody noticed that this is introducing two different indices where we clearly said it would be just one

apologies -  @kmaid noticed


License missing from repo

Without a license, this project isn't open source and no one can use the code.
Please use something like http://choosealicense.com/ to decide what license to use. I recommend MIT or GPL.

thanks for your interest.  I'll add a license.


Make ebuild template configurable

Currently template is rather inflexible. We need to make in possible to load custom templates.

Once #10 lands we could provide default templates for:

Crates that have system-dep in their deptree, we set the env-vars, add a dependency on pkg-config, potentially we came up with a list of external dependencies to match with the ebuild names. Here we could even autodetect it.
Crates that use cargo-c to build C-libraries
Crates that use clap

Support autocompletion in one of the common ways
Build manuals in one of the common ways

Do you know of other common patterns we could partially automate I'm forgetting of?


Unexpected behaviour of connections for Reg defined within when context

Type of issue: bug report
Impact:  unknown
Development Phase: request
Other information: see example below
If the current behavior is a bug, please provide the steps to reproduce the problem:
Simple code example of a Reg defined and connected within a when context:
@chiselName
class BadWhenContext() extends MultiIOModule {
  val en = IO(Input(Bool()))
  val in = IO(Input(UInt(3.W)))
  val out = IO(Output(UInt(3.W)))

  val rin = Reg(chiselTypeOf(in))
  val rout = Reg(chiselTypeOf(in))

  when(en){
    i := in
    val inner1 = Reg(chiselTypeOf(i))
    inner1 := i + 1.U
    rout := inner1
  }
  out := rout
}

What is the current behavior?
when context is ignored for embedded Reg connections as shown below (trimmed verilog):
reg [2:0] rin;
reg [2:0] rout;
reg [2:0] inner1;
assign out = rout;
always @(posedge clock) begin
  if (en) begin
    rin <= in;
  end
  if (en) begin
    rout <= inner1;
  end
  inner1 <= rin + 3'h1; // expecting this statement to also be surrounded with its own if(en) block
end

What is the expected behavior?
when context applied to connections of embedded Reg, such as below (trimmed verilog):
reg [2:0] rin;
reg [2:0] rout;
reg [2:0] inner1;
assign out = rout;
always @(posedge clock) begin
  if (en) begin
    rin <= in;
  end
  if (en) begin
    rout <= inner1;
  end
  if (en) begin
    inner1 <= rin + 3'h1;
  end
end

Please tell us about your environment:
- version: 3.4-20200728-SNAPSHOT
- OS: Darwin 17.7.0 Darwin Kernel Version 17.7.0: Mon Aug 31 22:11:23 PDT 2020;
What is the use case for changing the behavior?
Consistency: why isn't the when context applied to registers defined within himself?
Note: the actual use case is to be able to surround with a when context a function declaring and using Reg within its body.

You may already have resolved this issue, but, just in case, as a reference, chipsalliance/firrtl#1862.
In summary, this is a expected behavior as firrtl spec (details at 5.10.2).
I don't know whether this spec is appropriate or not though.

Hi @Soya-Onishi
Sorry for this late answer, I missed the notification...!
I am quite sorry to read a definite answer about this, @jackkoenig to answer your comment:

what does it mean for the declaration of a register to be conditional?

it simply means that the condition (whenContext) of this register declaration is a pre-requisite to all affectation to this register.
Intended usage is quite simple : gate a whole block (typically a function) with a when(ready){ ... }
If the block contains Reg declaration then the synchronization of other elements wouldn't be lost.
@Soya-Onishi to circumvent this limitation, in practice we use a custom transform to do exactly what I described above : all affectations to registers declared at a given whenContext are gated with this whenContext, simply &&-ed with existing conditions if any.

I ran into this issue, and I am surprised that it is actually intended behavior since it is not intuitive. What worked for me is to create a method with the following general form:
def :@=(that: => Data): Unit = when(when.cond){data.:=(that)}

Now whenever I need an update to a locally defined Reg to respect all current when's, I use :@= instead of :=.

Nice hack @dbear496
It's a great use of when.cond which has been introduced by https://github.com/chipsalliance/chisel3/commit/cdb7bb27bd675a8a114701b97a45c56e26ef42b5 in January 2021 (a few months after I ran into this issue)


make isPromise support null as a parameter

Description of the Change
isPromise would crash if given null, so I made it check for null too.

This is an enhancement.

Not saying won't accept, but don't see how this could have caused a problem for Mocha.
Only usage I find is here, which was already guarded in the if condition.

@fabiosantoscode
Thanks for the PR.  This would need the CLA to be signed as well a corresponding unit test.

@plroebuck 	This is the problem with public APIs. 😝

Good thing that I added a test, if the value was null, the function would return null!

Signed CLA, tested and fixed :) and yes, I got this crash because of a public API.

Coverage increased (+0.04%) to 90.638% when pulling f6d0372b7a24f70d1eb790649cf08a2ffc9dea00 on fabiosantoscode:patch-1 into 6df0e84dc873167456c2b4a384f464190ad1a540 on mochajs:master.

LGTM, thanks


POLO - Ham2K Portable Logger

What Resources are you wanting to add/modify to the Repo?

Polo
Update Typo for UV5R

Checklist

[X] Please make sure that uncommon words are added to the dictionary located in the wordlist
[X] Does each item have a proper linked reference?

Thanks :)


Doesn't work with GoogleTranslate

Hi,
Thanks for the amazing plugin!
However we have an issue when Chrome's Google Translate is being used.
Reproducible here https://clx8h.csb.app/ (Source: https://codesandbox.io/s/react-truncate-markup-google-translate-clx8h)
The root caused seems to be deriving from https://github.com/facebook/react/issues/11538#issuecomment-390386520 Not sure if there's a fix for this?

Any update?

Any update?

Unfortunately I am not able to do much here as it's a Google Translate issue. I tried out wrapping both the content and ellipsis in spans (as suggested as a possible workaround) and that worked in terms of actually rendering something in Google Translate, but I won't be adding that to the library as it adds unnecessary/potentially unwanted HTML tags into the page, potentially breaking styling.
But it's something users can do themselves for both the content and ellipsis (ellipsis prop) if they want to.
Another solution for the time being (until the issue is fixed by GT team) would be ignoring these errors by monkeypatching removeChild/insertBefore https://github.com/facebook/react/issues/11538#issuecomment-417504600

Unfortunately I am not able to do much here as it's a Google Translate issue. I tried out wrapping both the content and ellipsis in spans (as suggested as a possible workaround) and that worked in terms of actually rendering something in Google Translate, but I won't be adding that to the library as it adds unnecessary/potentially unwanted HTML tags into the page, potentially breaking styling.
But it's something users can do themselves for both the content and ellipsis (ellipsis prop) if they want to.
Another solution for the time being (until the issue is fixed by GT team) would be ignoring these errors by monkeypatching removeChild/insertBefore https://github.com/facebook/react/issues/11538#issuecomment-417504600


X11 crashes while holding C-+ to increase font size

Hi, I know that alacritty is in early stage of development, but it already looks and works just awesome for the most part.
Which operating system does the issue occur on?
Arch Linux
If on linux, are you using X11 or Wayland?
I hold Ctrl plus to increase my font, and I suppose it goes beyond scaling limit at some point, so X11 crashes entirely forcing me to type startx again :)
X11 traceback looks more or less like this:
Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 72: non-double matrix element
Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 80: saw unknown, expected number

Since this 10-scale-bitmap-fonts.conf is not that big, I'll post it here too, just in case. Its value is default one:
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>

<!--
  If font is bitmap, calculate scale factor.
  Note that color bitmap fonts have scalable=true, while
  non-color ones have scalable=false.  Both groups have outline=false.
  -->
<match target="font">
  <test name="outline" compare="eq">
    <bool>false</bool>
  </test>
  <edit name="pixelsizefixupfactor" mode="assign">
    <divide>
      <name target="pattern">pixelsize</name>
      <name target="font"   >pixelsize</name>
    </divide>
  </edit>
</match>
<!--
  For non-scalable bitmap fonts (ie. non-color), skip
  minor scaling if hinting is enabled.
  -->
<match target="font">
  <test name="outline" compare="eq">
    <bool>false</bool>
  </test>
  <test name="scalable" compare="eq">
    <bool>false</bool>
  </test>
  <test name="hinting" compare="eq">
    <bool>true</bool>
  </test>
  <edit name="scalingnotneeded" mode="assign">
    <and>
      <less>
        <name>pixelsizefixupfactor</name>
        <double>1.2</double>
      </less>
      <more>
        <name>pixelsizefixupfactor</name>
        <double>0.8</double>
      </more>
    </and>
  </edit>
</match>
<match target="font">
  <test name="scalingnotneeded" compare="eq">
    <bool>true</bool>
  </test>
  <edit name="pixelsizefixupfactor" mode="assign">
    <double>1.0</double>
  </edit>
</match>
<!--
  If we *are* going to scale, go ahead and do it.
  -->
<match target="font">
  <test name="outline" compare="eq">
    <bool>false</bool>
  </test>
  <test name="pixelsizefixupfactor" compare="not_eq">
    <double>1.0</double>
  </test>
  <edit name="matrix" mode="assign">
    <times>
      <name>matrix</name>
      <matrix>
        <name>pixelsizefixupfactor</name> <double>0</double>
        <double>0</double> <name>pixelsizefixupfactor</name>
       </matrix>
    </times>
  </edit>
  <edit name="size" mode="assign">
    <divide>
      <name>size</name>
      <name>pixelsizefixupfactor</name>
    </divide>
  </edit>
</match>

</fontconfig>

I've checked termite and kitty terminals just in case it's something with my setup and they both work fine. Maybe there is some missing boundary check?

Sounds like an extreme case of #842

Yes, indeed! I even saw something similar to
Size(24)
Size(28)
Size(30)
Size(32)
Size(38)
Size(44)
Size(48)
Size(50)
Size(54)
Size(56)
Size(58)
Size(62)

part, but cluttered with X11 trace. I've tried to look for a similar issue, but haven't found #842 for some reason.

@valentjedi is there a backtrace generated for Alacritty when this happens? Perhaps you can start Alacritty in a tmux session so that the tty survives the X11 crash. Make sure to run with RUST_BACKTRACE=1 to get the full trace.

RUST_BACKTRACE=1 is an environment variable right?

Duplicate of https://github.com/jwilm/alacritty/issues/842


Yc/add localized perturbation

Earth-2 MIP Pull Request
Description
This MR adds a notebook for preforming a perturbation response experiment in earth2mip. In this experiment a perturbation to the input is added at t=0 and the model's development is observed from it.
Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.
[X] The CHANGELOG.md is up to date with these changes.
[X] An issue is linked to this pull request.

Dependencies

@NickGeneva thanks for the help the changes work with fcnv2_sm but not with pangu
if you run the notebook you get:
INFO:inference:ensemble members 1-1/1
Traceback (most recent call last):
  File "/usr/lib/python3.10/runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/lib/python3.10/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/usr/local/lib/python3.10/dist-packages/earth2mip/inference_ensemble.py", line 421, in <module>
    main()
  File "/usr/local/lib/python3.10/dist-packages/earth2mip/inference_ensemble.py", line 229, in main
    run_inference(model, config, perturb, group)
  File "/usr/local/lib/python3.10/dist-packages/earth2mip/inference_ensemble.py", line 395, in run_inference
    run_ensembles(
  File "/usr/local/lib/python3.10/dist-packages/earth2mip/inference_ensemble.py", line 135, in run_ensembles
    iterator = model(time, x, normalize=False)
TypeError: PanguInference.__call__() got an unexpected keyword argument 'normalize'

Let's hold off no merging this until I return next week.
We should not be adding new methods/properties to earth2mip.networks.Inference. see #14.

Also, the notebook needs to be removed. It has outputs and experimental stuff should not go here.

I propose these changes since the config handling is not straightforward.

combine #42 and #33.
rename “noise_injection” to something more general perhaps just “perturb”.
delete any config handling/construction logic
make two examples in examples/workflows/ as an alternative to the config stuff.
Add tests for the noise injection feature of networks.Inference and pangu.PanguWeather


mysql create index error

the sql is :
CREATE INDEX idx_operationlog_operatetime_regioncode USING BTREE ON operation_log (operate_time,region_biz_code);

Greetings.
You best chance to get this solved  was to sponsor or provide an implementation or fix.


Interrupting while resolving a promise from go looks like nothing went wrong

If you have a promise that gets resolved on the event loop, and that resolve leads to an interrupt, this is never reported.
This is due to three specific things within goja/Sobek.
But first some general background: JS is single threaded and at any point only 1 js code is being executed. This also means that if you have a resolution of a promise (among anything else) it will wait until there is nothing and then it will be ran. This is done in goja in different places, but usually after any other running of js code (for a very wide definition of code) goja will check if it needs to run any resolutions.
This all is great, but the three specific things are that:

resolving a promise does not return an error. In practice it actually specifically will eat the error for both in resolution and rejection.
the resolve of a promise will trigger actually running it resolves if the js stack is empty - which it will be unless you call it within a js function.
the interrupt will be cleared when it is returning to an empty stack

So at this point if you interrupt goja and this happens during a resolve from go, that was queued on an event loop, UNLESS that resolve was called within some other js code execution:

you will not get the interrupt error
the interrupt error will be cleared and consequently even running something will not help you.

A fairly small example test to illustrate this.
func TestInterruptWithPromises(t *testing.T) {
	rt := New()
	rt.SetMaxCallStackSize(5)
	// this test panics as otherwise goja will recover and possibly loop
	rt.Set("abort", rt.ToValue(func() {
		// panic("waty")
		rt.Interrupt("abort this")
	}))
	var queue = make(chan func(), 10)
	rt.Set("myPromise", func() Value {
		p, resolve, _ := rt.NewPromise()
		queue <- func() {
			resolve("some value")
		}

		return rt.ToValue(p)
	})

	_, err := rt.RunString(`
		let p = myPromise()
		p.then(() => { abort() });
	`)
	if err == nil {
		t.Fatal("expected error but got no error")
	}
	f := <-queue
	f()
	t.Log(err)
	var soErr *InterruptedError
	if !errors.As(err, &soErr) {
		t.Fatalf("Wrong error type: %T", err)
	}
}

I did start with goja_nodejs's eventloop, but it has absolutely no way of reporting errors from the event loop, so that seemed pointless. But it works with it as well.
Now at this point again you either need to do
rt.Set("actuallyDoTheResolve", resolve)
_, err := rt.RunString(`actuallyDoTheResolve()`)

Or some other similar thing in order to have js stack to prevent resolve to be the thing running the resolution and consequently eating the interrupt.
Few things I tried:
Doing the above without running js code
I tried Try and I tried AssertFunction  on a ToValue(func() {resolve()}). Both of those skip creating a js stack so both will not stop resolve from running the resolution.
Not clearing interrupt
I tried making the interrupt not getting cleared, but that basically requires that you also run additional code after every resolve/reject. To potentially check if something was interrupted. I also have not tried any example in which there were multiple promise resolution jobs queued which might make this even worse.
panicking in resolve
Doing a direct panic in the wrapPromiseReaction + AssertFunction on a ToValue(func() ... resolve()). This worked best and I can argue I can do it as part of an event loop.  Using Try did not work, but I expect that is because I literally just called panic, so that might the better way, making it work with Try
Other ideas
resolve and reject returning errors
That will mean that any code using it will need to return an error, which might be cleaner 🤷♂
But also will require more work and will not be obvious something is broken for older codebases.
But might be the more correct and obvious way to go with.
edit: PR with one of the solutions hacked on top of k6 as part of a testing what is going on.

Hi.
Resolving a Promise , as you said, happens on the loop, Interrupt() on the other hand, is meant to be called in another goroutine to interrupt the vm. Why do you need to call it during resolving? If you instead panic with a Value, that should be returned as the error either from a function call, or from one of the Run* methods, depending on how you run the JS code.

@dop251 I don't think that is relevant.
The interrupt is captured during the resolve. Calling from within or outside, it still will have the same problem when it is captured and propagated during a resolve.
On the concrete why we use interrupt instead of a panic ... well this mechanism is supposed to stop the execution in k6, and interrupt is the way to stop a runtime, so it seems perfectly fitting. We also already handle interrupts for different reasons, while we do not panics. Goja does as part of its normal execution - yes, but does never go up to k6.

Interrupt was never meant to be 'captured' or 'propagated'. It solves a specific problem: how to interrupt a currently running VM from the outside. When you're inside you're already controlling the execution flow and have other means to stop it.

Looking further into this, the reason why wrapPromiseReaction ignores the error is because 'normal' exceptions thrown in a handler are never propagated, instead they cause the promise to be rejected.
However, this applies to 'normal' exceptions, not to uncatchable ones, such as StackOverflowError or InterruptedError. This makes it a strong case for making the resolve and reject of NewPromise return an error. I wouldn't mind it, even though it would break existing code. But the refactoring is trivial and thanks to Go modules the change won't be sudden and disruptive.
Another piece of the puzzle would be adding an ability to construct UncatchableErrors from Go code, for instance by adding Runtime.NewInterruptedError(). It should then be used instead of calling Interrupt().

However, this applies to 'normal' exceptions, not to uncatchable ones, such as StackOverflowError or InterruptedError. This makes it a strong case for making the resolve and reject of NewPromise return an error. I wouldn't mind it, even though it would break existing code.

This sounds okay. Do you want me to make a PR with that? There doesn't really seem to be any questionable thing there apart from whether to also return errors on "normal" extensions or not.
Given that there is mechanism to catch "normal" exceptions in async code that seems like the thing that should be left.

Yes please, raise a PR. The function should just return whatever error is returned from the wrapped function. Normal exceptions are already handled and turned into Promise rejections.


Back-port commit 20dbeb5 for 5.5 branch, to support GZIP compression

Closes #2097

Abandoning as this is no longer required


Update README.md

this will be a helpful change

Summary

Ticket Link

Hello @nikita812,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.
Per the Mattermost Contribution Guide, we need to add you to the list of approved contributors for the Mattermost project.
Please help complete the Mattermost contribution license agreement?
Once you have signed the CLA, please comment with /check-cla and confirm that the CLA check is green.
This is a standard procedure for many open source projects.
Please let us know if you have any questions.
We are very happy to have you join our growing community! If you're not yet a member, please consider joining our Contributors community channel to meet other contributors and discuss new opportunities with the core team.

Thanks for the PR! We appreciate your contribution but these changes aren't applicable at this time.


Make gateway metrics name prefix configurable

Problem Statement
When emitting metics to an observability tool such as Wavefront or Prometheus/Grafana, there is a potential conflict in metric names with other products/tools when using the prefix gateway.requests.*. This makes it difficult to create dashboards focused on metrics coming from Spring Cloud Gateway as opposed to those other products/tools in larger organizations.
Proposed Solution
In the GatewayMetricsFilter it would be nice to make the metrics name prefix configurable at line:
https://github.com/spring-cloud/spring-cloud-gateway/blob/master/spring-cloud-gateway-server/src/main/java/org/springframework/cloud/gateway/filter/GatewayMetricsFilter.java#L86
This configuration could be named something like spring.cloud.gateway.metrics.prefix.
Alternative Options
Another option is to change the default metrics name prefix from gateway.requests to spring.cloud.gateway.requests which is in alignment with Spring Cloud Data Flow. The problem with this change is that it would be a breaking change for backward compatibility. Also, the use case for Spring Cloud Gateway is not necessarily the same as for Spring Cloud Data Flow and so it could be argued that the current default naming convention for metrics is appropriate.

We'll make it configurable in hoxton and change the default in ilford.


k3s pods are  unable to reaching to the GCP Buckets

Environmental Info:
K3s Version:

k3s version v1.24.4+k3s1 (c3f830e9)
go version go1.18.1
Node(s) CPU architecture, OS, and Version:

Linux ctm-ubantu-vm 5.4.0-1087-gcp #95~18.04.1-Ubuntu SMP Mon Aug 22 03:26:39 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:

It's  a single node cluster where i have installed the k3's service and running the application on top of it
Describe the bug:

i have created one ubuntu VM in the gcp cloud and i install k3 service and deployed my application helm chart on top of it however
some of the pods need to connect to the GCP bucket and pull the  images however it is not happening instead it is throwing the below error
ERROR: gcloud crashed (ConnectionError): HTTPSConnectionPool(host='oauth2.googleapis.com', port=443)
Steps To Reproduce:

Installed K3s:
$ export CLUSTER_CIDR=<IP_ADDRESS>/24
$ export SERVICE_CIDR=<IP_ADDRESS>/24
$ export EXTERNAL_IP=<Your_VM_External_IP>
$ export K3S_KUBECONFIG_MODE="644"
$ export INSTALL_K3S_EXEC="--cluster-cidr $CLUSTER_CIDR --service-cidr $SERVICE_CIDR --node-external-ip $EXTERNAL_IP"
$ curl -sfL https://get.k3s.io | sh -
$ k3s -v
$ systemctl status k3s.service

Expected behavior:

All pods need to be up&running
Actual behavior:

pods are not running
Additional context / logs:

root@ctm-ubantu-vm:~# kubectl get pods -n store
NAME                                          READY   STATUS                  RESTARTS         AGE
jarvis-scoxcashdelegate-6c4bf57d76-p85g2      0/1     Init:0/2                0                56m
jarvis-scoxcashservice-ddbbdcd46-d9245        0/1     Init:0/1                0                56m
jarvis-scoxprinter-b4577cf87-l9htt            0/1     Init:0/1                0                56m
jarvis-scoxdoc-bddcfd-5kms9                   0/1     Init:0/1                0                56m
jarvis-rediscache-69d48468dc-sgxcd            1/1     Running                 0                56m
jarvis-hivemqce-5888d55bf6-xwlhc              1/1     Running                 0                56m
jarvis-mongodb-5f6bf5d859-48jc4               1/1     Running                 0                56m
jarvis-jarvisconfigservice-784889995b-28klj   0/1     Init:CrashLoopBackOff   15 (3m4s ago)    56m
jarvis-scoxresources-7b5977bdd8-kqcvk         0/1     Init:CrashLoopBackOff   15 (3m1s ago)    56m
jarvis-scoxerrorlookup-5b5499d866-4h9m5       0/1     Init:CrashLoopBackOff   15 (2m45s ago)   56m
jarvis-scoxauthentication-846dcc684c-m968j    0/1     Init:CrashLoopBackOff   15 (2m33s ago)   56m
root@ctm-ubantu-vm:~# kubectl logs -p jarvis-jarvisconfigservice-784889995b-28klj -n store --all-containers
Initializing from GCS...
Version: gc://scox-configservice-assets/assets/assets-1.6.0.zip
Checking if file, assets-1.6.0.zip, is already in the destination path, /var/lib/ncr_scot/jarvisconfigservice/.
OVERWRITE_LOCAL_COPY is set to false.
Downloading from GCS
ERROR: gcloud crashed (TransportError): HTTPSConnectionPool(host='oauth2.googleapis.com', port=443): Max retries exceeded with url: /token (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fa61e401ee0>: Failed to establish a new connection: [Errno -3] Try again'))

Can you successfully access the GCP bucket from the node itself?

yes I am able to access the GCP buckets from the node and list the files from inside of the buckets

I see that you have a bunch of other pods that are also stuck in Init or crashing. Are the pods for the packaged components running correctly? Can you attach the output of:

kubectl get pods -A -o wide
cat /var/lib/rancher/rke2/agent/containerd/containerd.log
journalctl --no-pager -u k3s

cat /var/lib/rancher/rke2/agent/containerd/containerd.log :-
`root@ctm-ubantu-vm:~# tail -f  /var/lib/rancher/k3s/agent/containerd/containerd.log -n 100
time="2022-09-10T18:50:34.132811340Z" level=info msg="CreateContainer within sandbox "082af4a2e679b6fb3a37cfd1f0bcbb5398bfecf69e73532416a0911231dbd02c" for container &ContainerMetadata{Name:init-assets,Attempt:281,}"
time="2022-09-10T18:50:34.154947029Z" level=info msg="CreateContainer within sandbox "082af4a2e679b6fb3a37cfd1f0bcbb5398bfecf69e73532416a0911231dbd02c" for &ContainerMetadata{Name:init-assets,Attempt:281,} returns container id "0474e577c33bf62902aa57e40d8a6de26a159541e0fc7a50a264e0c952fe2eb7""
time="2022-09-10T18:50:34.155875968Z" level=info msg="StartContainer for "0474e577c33bf62902aa57e40d8a6de26a159541e0fc7a50a264e0c952fe2eb7""
time="2022-09-10T18:50:34.268465329Z" level=info msg="StartContainer for "0474e577c33bf62902aa57e40d8a6de26a159541e0fc7a50a264e0c952fe2eb7" returns successfully"
time="2022-09-10T18:50:40.581987348Z" level=info msg="shim disconnected" id=0474e577c33bf62902aa57e40d8a6de26a159541e0fc7a50a264e0c952fe2eb7
time="2022-09-10T18:50:40.582114644Z" level=warning msg="cleaning up after shim disconnected" id=0474e577c33bf62902aa57e40d8a6de26a159541e0fc7a50a264e0c952fe2eb7 namespace=k8s.io
time="2022-09-10T18:50:40.582131513Z" level=info msg="cleaning up dead shim"
time="2022-09-10T18:50:40.603404578Z" level=warning msg="cleanup warnings time="2022-09-10T18:50:40Z" level=info msg="starting signal loop" namespace=k8s.io pid=23065 runtime=io.containerd.runc.v2\n"
time="2022-09-10T18:50:41.494122804Z" level=info msg="RemoveContainer for "05f9d88c630d002c6089100d909e0a22720c9475a8ca9489d3b5d124fe3e5c0d""
time="2022-09-10T18:50:41.495003385Z" level=info msg="RemoveContainer for "05f9d88c630d002c6089100d909e0a22720c9475a8ca9489d3b5d124fe3e5c0d""
time="2022-09-10T18:50:41.495098372Z" level=error msg="RemoveContainer for "05f9d88c630d002c6089100d909e0a22720c9475a8ca9489d3b5d124fe3e5c0d" failed" error="failed to set removing state for container "05f9d88c630d002c6089100d909e0a22720c9475a8ca9489d3b5d124fe3e5c0d": container is already in removing state"
time="2022-09-10T18:50:41.501627122Z" level=info msg="RemoveContainer for "05f9d88c630d002c6089100d909e0a22720c9475a8ca9489d3b5d124fe3e5c0d" returns successfully"
time="2022-09-10T18:50:51.128388103Z" level=info msg="CreateContainer within sandbox "3dc02879c19bbc8425e2b5e56fdc6f7d05c1aded31d856fbe713611ed4e04360" for container &ContainerMetadata{Name:init-authentication-db,Attempt:281,}"
time="2022-09-10T18:50:51.149462374Z" level=info msg="CreateContainer within sandbox "3dc02879c19bbc8425e2b5e56fdc6f7d05c1aded31d856fbe713611ed4e04360" for &ContainerMetadata{Name:init-authentication-db,Attempt:281,} returns container id "607811eb01d9565a00dca0ef1c2a86f2b818875c578d7a831c43e931dd688bfe""
time="2022-09-10T18:50:51.150461017Z" level=info msg="StartContainer for "607811eb01d9565a00dca0ef1c2a86f2b818875c578d7a831c43e931dd688bfe""
time="2022-09-10T18:50:51.262399734Z" level=info msg="StartContainer for "607811eb01d9565a00dca0ef1c2a86f2b818875c578d7a831c43e931dd688bfe" returns successfully"
time="2022-09-10T18:50:57.479591387Z" level=info msg="shim disconnected" id=607811eb01d9565a00dca0ef1c2a86f2b818875c578d7a831c43e931dd688bfe
time="2022-09-10T18:50:57.479669965Z" level=warning msg="cleaning up after shim disconnected" id=607811eb01d9565a00dca0ef1c2a86f2b818875c578d7a831c43e931dd688bfe namespace=k8s.io
time="2022-09-10T18:50:57.479687217Z" level=info msg="cleaning up dead shim"
time="2022-09-10T18:50:57.492937317Z" level=warning msg="cleanup warnings time="2022-09-10T18:50:57Z" level=info msg="starting signal loop" namespace=k8s.io pid=23212 runtime=io.containerd.runc.v2\n"
time="2022-09-10T18:50:57.559277775Z" level=info msg="RemoveContainer for "9e2121be4ce820764ea3c0fe1b39f71aaf0c100d55e320f3ea408465bec7e016""
time="2022-09-10T18:50:57.560090533Z" level=info msg="RemoveContainer for "9e2121be4ce820764ea3c0fe1b39f71aaf0c100d55e320f3ea408465bec7e016""
time="2022-09-10T18:50:57.560241464Z" level=error msg="RemoveContainer for "9e2121be4ce820764ea3c0fe1b39f71aaf0c100d55e320f3ea408465bec7e016" failed" error="failed to set removing state for container "9e2121be4ce820764ea3c0fe1b39f71aaf0c100d55e320f3ea408465bec7e016": container is already in removing state"
time="2022-09-10T18:50:57.567562941Z" level=info msg="RemoveContainer for "9e2121be4ce820764ea3c0fe1b39f71aaf0c100d55e320f3ea408465bec7e016" returns successfully"
time="2022-09-10T18:51:08.132073080Z" level=info msg="CreateContainer within sandbox "5539cc28c9cab6895f94bc51cc119956e94b95479caf1bff8ceff25ce3510828" for container &ContainerMetadata{Name:init-scoxerrorlookup-db,Attempt:282,}"
time="2022-09-10T18:51:08.153324375Z" level=info msg="CreateContainer within sandbox "5539cc28c9cab6895f94bc51cc119956e94b95479caf1bff8ceff25ce3510828" for &ContainerMetadata{Name:init-scoxerrorlookup-db,Attempt:282,} returns container id "fc1ba4404be1a8e75a1590bf144a4e3be55be4e973fda5a4135d77ab9d6d73f0""
time="2022-09-10T18:51:08.154214658Z" level=info msg="StartContainer for "fc1ba4404be1a8e75a1590bf144a4e3be55be4e973fda5a4135d77ab9d6d73f0""
time="2022-09-10T18:51:08.270926634Z" level=info msg="StartContainer for "fc1ba4404be1a8e75a1590bf144a4e3be55be4e973fda5a4135d77ab9d6d73f0" returns successfully"
time="2022-09-10T18:51:14.512246839Z" level=info msg="shim disconnected" id=fc1ba4404be1a8e75a1590bf144a4e3be55be4e973fda5a4135d77ab9d6d73f0
time="2022-09-10T18:51:14.512475963Z" level=warning msg="cleaning up after shim disconnected" id=fc1ba4404be1a8e75a1590bf144a4e3be55be4e973fda5a4135d77ab9d6d73f0 namespace=k8s.io
time="2022-09-10T18:51:14.512493435Z" level=info msg="cleaning up dead shim"
time="2022-09-10T18:51:14.524803301Z" level=warning msg="cleanup warnings time="2022-09-10T18:51:14Z" level=info msg="starting signal loop" namespace=k8s.io pid=23384 runtime=io.containerd.runc.v2\n"
time="2022-09-10T18:51:14.619694434Z" level=info msg="RemoveContainer for "4762a60e930950756853860a8374b10a7eceff51e2b65014b8b0031a556cd444""
time="2022-09-10T18:51:14.621881282Z" level=info msg="RemoveContainer for "4762a60e930950756853860a8374b10a7eceff51e2b65014b8b0031a556cd444""
time="2022-09-10T18:51:14.622097198Z" level=error msg="RemoveContainer for "4762a60e930950756853860a8374b10a7eceff51e2b65014b8b0031a556cd444" failed" error="failed to set removing state for container "4762a60e930950756853860a8374b10a7eceff51e2b65014b8b0031a556cd444": container is already in removing state"
time="2022-09-10T18:51:14.628377259Z" level=info msg="RemoveContainer for "4762a60e930950756853860a8374b10a7eceff51e2b65014b8b0031a556cd444" returns successfully"
time="2022-09-10T18:55:17.128501362Z" level=info msg="PullImage "us-docker.pkg.dev/ret-sco-cug01-stg/jarvis-stg/jarvis-init-db:1.6.0-42""
time="2022-09-10T18:55:17.301371472Z" level=info msg="ImageUpdate event &ImageUpdate{Name:us-docker.pkg.dev/ret-sco-cug01-stg/jarvis-stg/jarvis-init-db:1.6.0-42,Labels:map[string]string{io.cri-containerd.image: managed,},XXX_unrecognized:[],}"
time="2022-09-10T18:55:17.304577185Z" level=info msg="ImageUpdate event &ImageUpdate{Name:sha256:5040f257e4cbfc8a5878a346a81c0369021fee094e62b411ebed0032de4384e3,Labels:map[string]string{io.cri-containerd.image: managed,},XXX_unrecognized:[],}"
time="2022-09-10T18:55:17.307185279Z" level=info msg="ImageUpdate event &ImageUpdate{Name:us-docker.pkg.dev/ret-sco-cug01-stg/jarvis-stg/jarvis-init-db:1.6.0-42,Labels:map[string]string{io.cri-containerd.image: managed,},XXX_unrecognized:[],}"
time="2022-09-10T18:55:17.310151531Z" level=info msg="ImageUpdate event &ImageUpdate{Name:us-docker.pkg.dev/ret-sco-cug01-stg/jarvis-stg/jarvis-init-db@sha256:26044753c8f8f7730a5cec272fbf848139900d0e5cab1937b1af4de940e07ae2,Labels:map[string]string{io.cri-containerd.image: managed,},XXX_unrecognized:[],}"
time="2022-09-10T18:55:17.310800774Z" level=info msg="PullImage "us-docker.pkg.dev/ret-sco-cug01-stg/jarvis-stg/jarvis-init-db:1.6.0-42" returns image reference "sha256:5040f257e4cbfc8a5878a346a81c0369021fee094e62b411ebed0032de4384e3""
time="2022-09-10T18:55:17.317456492Z" level=info msg="CreateContainer within sandbox "f240eafcd442ea37a22b5cac36a0be479a904b6f4c1210fe165dfe1361726f0f" for container &ContainerMetadata{Name:init-resources-db,Attempt:283,}"
time="2022-09-10T18:55:17.344129906Z" level=info msg="CreateContainer within sandbox "f240eafcd442ea37a22b5cac36a0be479a904b6f4c1210fe165dfe1361726f0f" for &ContainerMetadata{Name:init-resources-db,Attempt:283,} returns container id "2def59725b98f637ab78f7c1be314ca44e9515074352f6c594e506ccce701e7c""
time="2022-09-10T18:55:17.344980486Z" level=info msg="StartContainer for "2def59725b98f637ab78f7c1be314ca44e9515074352f6c594e506ccce701e7c""
time="2022-09-10T18:55:17.448266016Z" level=info msg="StartContainer for "2def59725b98f637ab78f7c1be314ca44e9515074352f6c594e506ccce701e7c" returns successfully"
time="2022-09-10T18:55:24.547322208Z" level=info msg="shim disconnected" id=2def59725b98f637ab78f7c1be314ca44e9515074352f6c594e506ccce701e7c
time="2022-09-10T18:55:24.547405673Z" level=warning msg="cleaning up after shim disconnected" id=2def59725b98f637ab78f7c1be314ca44e9515074352f6c594e506ccce701e7c namespace=k8s.io
time="2022-09-10T18:55:24.547417646Z" level=info msg="cleaning up dead shim"
time="2022-09-10T18:55:24.559150448Z" level=warning msg="cleanup warnings time="2022-09-10T18:55:24Z" level=info msg="starting signal loop" namespace=k8s.io pid=24280 runtime=io.containerd.runc.v2\n"
time="2022-09-10T18:55:25.449038122Z" level=info msg="RemoveContainer for "7ffc60068fd319d1fdd594442b3c01bfa921a1c3038051c632b87c482b469e8b""
time="2022-09-10T18:55:25.450003828Z" level=info msg="RemoveContainer for "7ffc60068fd319d1fdd594442b3c01bfa921a1c3038051c632b87c482b469e8b""
time="2022-09-10T18:55:25.450219724Z" level=error msg="RemoveContainer for "7ffc60068fd319d1fdd594442b3c01bfa921a1c3038051c632b87c482b469e8b" failed" error="failed to set removing state for container "7ffc60068fd319d1fdd594442b3c01bfa921a1c3038051c632b87c482b469e8b": container is already in removing state"
time="2022-09-10T18:55:25.455982957Z" level=info msg="RemoveContainer for "7ffc60068fd319d1fdd594442b3c01bfa921a1c3038051c632b87c482b469e8b" returns successfully"
time="2022-09-10T18:55:45.129697845Z" level=info msg="CreateContainer within sandbox "082af4a2e679b6fb3a37cfd1f0bcbb5398bfecf69e73532416a0911231dbd02c" for container &ContainerMetadata{Name:init-assets,Attempt:282,}"
time="2022-09-10T18:55:45.150422794Z" level=info msg="CreateContainer within sandbox "082af4a2e679b6fb3a37cfd1f0bcbb5398bfecf69e73532416a0911231dbd02c" for &ContainerMetadata{Name:init-assets,Attempt:282,} returns container id "09c9d36fc3dfa2ef2e2bae7eb2be7fc7a586f1f14ba48879413b40122f72a0ed""
time="2022-09-10T18:55:45.152315490Z" level=info msg="StartContainer for "09c9d36fc3dfa2ef2e2bae7eb2be7fc7a586f1f14ba48879413b40122f72a0ed""
time="2022-09-10T18:55:45.260080124Z" level=info msg="StartContainer for "09c9d36fc3dfa2ef2e2bae7eb2be7fc7a586f1f14ba48879413b40122f72a0ed" returns successfully"
time="2022-09-10T18:55:51.461906959Z" level=info msg="shim disconnected" id=09c9d36fc3dfa2ef2e2bae7eb2be7fc7a586f1f14ba48879413b40122f72a0ed
time="2022-09-10T18:55:51.461987825Z" level=warning msg="cleaning up after shim disconnected" id=09c9d36fc3dfa2ef2e2bae7eb2be7fc7a586f1f14ba48879413b40122f72a0ed namespace=k8s.io
time="2022-09-10T18:55:51.462001484Z" level=info msg="cleaning up dead shim"
time="2022-09-10T18:55:51.474254777Z" level=warning msg="cleanup warnings time="2022-09-10T18:55:51Z" level=info msg="starting signal loop" namespace=k8s.io pid=24517 runtime=io.containerd.runc.v2\n"
time="2022-09-10T18:55:51.539185464Z" level=info msg="RemoveContainer for "0474e577c33bf62902aa57e40d8a6de26a159541e0fc7a50a264e0c952fe2eb7""
time="2022-09-10T18:55:51.539850606Z" level=info msg="RemoveContainer for "0474e577c33bf62902aa57e40d8a6de26a159541e0fc7a50a264e0c952fe2eb7""
time="2022-09-10T18:55:51.539972826Z" level=error msg="RemoveContainer for "0474e577c33bf62902aa57e40d8a6de26a159541e0fc7a50a264e0c952fe2eb7" failed" error="failed to set removing state for container "0474e577c33bf62902aa57e40d8a6de26a159541e0fc7a50a264e0c952fe2eb7": container is already in removing state"
time="2022-09-10T18:55:51.545860535Z" level=info msg="RemoveContainer for "0474e577c33bf62902aa57e40d8a6de26a159541e0fc7a50a264e0c952fe2eb7" returns successfully"
time="2022-09-10T18:56:07.129138051Z" level=info msg="CreateContainer within sandbox "3dc02879c19bbc8425e2b5e56fdc6f7d05c1aded31d856fbe713611ed4e04360" for container &ContainerMetadata{Name:init-authentication-db,Attempt:282,}"
time="2022-09-10T18:56:07.150708481Z" level=info msg="CreateContainer within sandbox "3dc02879c19bbc8425e2b5e56fdc6f7d05c1aded31d856fbe713611ed4e04360" for &ContainerMetadata{Name:init-authentication-db,Attempt:282,} returns container id "493706f7683190b0f3771bc79536530d75d400396447d238066945dca0c333ef""
time="2022-09-10T18:56:07.151388168Z" level=info msg="StartContainer for "493706f7683190b0f3771bc79536530d75d400396447d238066945dca0c333ef""
time="2022-09-10T18:56:07.256322532Z" level=info msg="StartContainer for "493706f7683190b0f3771bc79536530d75d400396447d238066945dca0c333ef" returns successfully"
time="2022-09-10T18:56:13.536146504Z" level=info msg="shim disconnected" id=493706f7683190b0f3771bc79536530d75d400396447d238066945dca0c333ef
time="2022-09-10T18:56:13.536221320Z" level=warning msg="cleaning up after shim disconnected" id=493706f7683190b0f3771bc79536530d75d400396447d238066945dca0c333ef namespace=k8s.io
time="2022-09-10T18:56:13.536235871Z" level=info msg="cleaning up dead shim"
time="2022-09-10T18:56:13.548197459Z" level=warning msg="cleanup warnings time="2022-09-10T18:56:13Z" level=info msg="starting signal loop" namespace=k8s.io pid=24702 runtime=io.containerd.runc.v2\n"
time="2022-09-10T18:56:13.613966601Z" level=info msg="RemoveContainer for "607811eb01d9565a00dca0ef1c2a86f2b818875c578d7a831c43e931dd688bfe""
time="2022-09-10T18:56:13.615084599Z" level=info msg="RemoveContainer for "607811eb01d9565a00dca0ef1c2a86f2b818875c578d7a831c43e931dd688bfe""
time="2022-09-10T18:56:13.615247608Z" level=error msg="RemoveContainer for "607811eb01d9565a00dca0ef1c2a86f2b818875c578d7a831c43e931dd688bfe" failed" error="failed to set removing state for container "607811eb01d9565a00dca0ef1c2a86f2b818875c578d7a831c43e931dd688bfe": container is already in removing state"
time="2022-09-10T18:56:13.620445913Z" level=info msg="RemoveContainer for "607811eb01d9565a00dca0ef1c2a86f2b818875c578d7a831c43e931dd688bfe" returns successfully"
time="2022-09-10T18:56:22.129454642Z" level=info msg="CreateContainer within sandbox "5539cc28c9cab6895f94bc51cc119956e94b95479caf1bff8ceff25ce3510828" for container &ContainerMetadata{Name:init-scoxerrorlookup-db,Attempt:283,}"
time="2022-09-10T18:56:22.155585261Z" level=info msg="CreateContainer within sandbox "5539cc28c9cab6895f94bc51cc119956e94b95479caf1bff8ceff25ce3510828" for &ContainerMetadata{Name:init-scoxerrorlookup-db,Attempt:283,} returns container id "aee58c216f9d59fdc32fac84b5f7bd63d980d4e44d76686fd4c981a84887e8ae""
time="2022-09-10T18:56:22.158503305Z" level=info msg="StartContainer for "aee58c216f9d59fdc32fac84b5f7bd63d980d4e44d76686fd4c981a84887e8ae""
time="2022-09-10T18:56:22.274396187Z" level=info msg="StartContainer for "aee58c216f9d59fdc32fac84b5f7bd63d980d4e44d76686fd4c981a84887e8ae" returns successfully"
time="2022-09-10T18:56:28.592657831Z" level=info msg="shim disconnected" id=aee58c216f9d59fdc32fac84b5f7bd63d980d4e44d76686fd4c981a84887e8ae
time="2022-09-10T18:56:28.592757894Z" level=warning msg="cleaning up after shim disconnected" id=aee58c216f9d59fdc32fac84b5f7bd63d980d4e44d76686fd4c981a84887e8ae namespace=k8s.io
time="2022-09-10T18:56:28.592775119Z" level=info msg="cleaning up dead shim"
time="2022-09-10T18:56:28.604988053Z" level=warning msg="cleanup warnings time="2022-09-10T18:56:28Z" level=info msg="starting signal loop" namespace=k8s.io pid=24826 runtime=io.containerd.runc.v2\n"
time="2022-09-10T18:56:28.671780240Z" level=info msg="RemoveContainer for "fc1ba4404be1a8e75a1590bf144a4e3be55be4e973fda5a4135d77ab9d6d73f0""
time="2022-09-10T18:56:28.672316138Z" level=info msg="RemoveContainer for "fc1ba4404be1a8e75a1590bf144a4e3be55be4e973fda5a4135d77ab9d6d73f0""
time="2022-09-10T18:56:28.672395887Z" level=error msg="RemoveContainer for "fc1ba4404be1a8e75a1590bf144a4e3be55be4e973fda5a4135d77ab9d6d73f0" failed" error="failed to set removing state for container "fc1ba4404be1a8e75a1590bf144a4e3be55be4e973fda5a4135d77ab9d6d73f0": container is already in removing state"
time="2022-09-10T18:56:28.678304212Z" level=info msg="RemoveContainer for "fc1ba4404be1a8e75a1590bf144a4e3be55be4e973fda5a4135d77ab9d6d73f0" returns successfully"
time="2022-09-10T18:59:00.037563136Z" level=info msg="shim disconnected" id=3a995a0d1d0bee75a3d9652c29d2bd97950d2c9633c25ab987d56386c1887525
time="2022-09-10T18:59:00.037663327Z" level=warning msg="cleaning up after shim disconnected" id=3a995a0d1d0bee75a3d9652c29d2bd97950d2c9633c25ab987d56386c1887525 namespace=k8s.io
time="2022-09-10T18:59:00.037679486Z" level=info msg="cleaning up dead shim"
time="2022-09-10T18:59:00.060521512Z" level=warning msg="cleanup warnings time="2022-09-10T18:59:00Z" level=info msg="starting signal loop" namespace=k8s.io pid=25246 runtime=io.containerd.runc.v2\n"
time="2022-09-10T18:59:00.156799987Z" level=info msg="RemoveContainer for "d567f742f6d6e8da20333037d3413502e37fad38ab074244407b7da897a803b0""
time="2022-09-10T18:59:00.157614572Z" level=info msg="CreateContainer within sandbox "753a60e3c78ba4ace712d5e9f5cf0a1f4194789791020917d9e23d37903f9fe1" for container &ContainerMetadata{Name:gcloud,Attempt:7,}"
time="2022-09-10T18:59:00.163429156Z" level=info msg="RemoveContainer for "d567f742f6d6e8da20333037d3413502e37fad38ab074244407b7da897a803b0" returns successfully"
time="2022-09-10T18:59:00.196690816Z" level=info msg="CreateContainer within sandbox "753a60e3c78ba4ace712d5e9f5cf0a1f4194789791020917d9e23d37903f9fe1" for &ContainerMetadata{Name:gcloud,Attempt:7,} returns container id "f266503e090f50650e8abdd3a950e88d7e420cf007a814c38d070df649d03e24""
time="2022-09-10T18:59:00.197859431Z" level=info msg="StartContainer for "f266503e090f50650e8abdd3a950e88d7e420cf007a814c38d070df649d03e24""
time="2022-09-10T18:59:00.314703960Z" level=info msg="StartContainer for "f266503e090f50650e8abdd3a950e88d7e420cf007a814c38d070df649d03e24" returns successfully"
journalctl --no-pager -u k3s :-
resources-7b5977bdd8-kqcvk" podUID=be1316a1-d68d-4da0-8d3e-d4d4ea3b92c9
Sep 10 19:02:14 ctm-ubantu-vm k3s[22432]: E0910 19:02:14.127800   22432 pod_workers.go:951] "Error syncing pod, skipping" err="failed to "StartContainer" for "init-scoxerrorlookup-db" with CrashLoopBackOff: "back-off 5m0s restarting failed container=init-scoxerrorlookup-db pod=jarvis-scoxerrorlookup-5b5499d866-4h9m5_store(7c272b41-f479-45ab-8018-4176cb20c013)"" pod="store/jarvis-scoxerrorlookup-5b5499d866-4h9m5" podUID=7c272b41-f479-45ab-8018-4176cb20c013
Sep 10 19:02:14 ctm-ubantu-vm k3s[22432]: E0910 19:02:14.127796   22432 pod_workers.go:951] "Error syncing pod, skipping" err="failed to "StartContainer" for "init-authentication-db" with CrashLoopBackOff: "back-off 5m0s restarting failed container=init-authentication-db pod=jarvis-scoxauthentication-846dcc684c-m968j_store(7d10cc48-c5f1-4ce6-b9ed-96fb5a9d43cb)"" pod="store/jarvis-scoxauthentication-846dcc684c-m968j" podUID=7d10cc48-c5f1-4ce6-b9ed-96fb5a9d43cb
Sep 10 19:02:16 ctm-ubantu-vm k3s[22432]: I0910 19:02:16.293644   22432 event.go:294] "Event occurred" object="store/scoxpicklist-pvc" fieldPath="" kind="PersistentVolumeClaim" apiVersion="v1" type="Normal" reason="WaitForFirstConsumer" message="waiting for first consumer to be created before binding"
Sep 10 19:02:24 ctm-ubantu-vm k3s[22432]: E0910 19:02:24.126813   22432 pod_workers.go:951] "Error syncing pod, skipping" err="failed to "StartContainer" for "init-assets" with CrashLoopBackOff: "back-off 5m0s restarting failed container=init-assets pod=jarvis-jarvisconfigservice-784889995b-28klj_store(612763ca-8629-41ef-8908-1807e11fad82)"" pod="store/jarvis-jarvisconfigservice-784889995b-28klj" podUID=612763ca-8629-41ef-8908-1807e11fad82
Sep 10 19:02:25 ctm-ubantu-vm k3s[22432]: E0910 19:02:25.125907   22432 pod_workers.go:951] "Error syncing pod, skipping" err="failed to "StartContainer" for "init-authentication-db" with CrashLoopBackOff: "back-off 5m0s restarting failed container=init-authentication-db pod=jarvis-scoxauthentication-846dcc684c-m968j_store(7d10cc48-c5f1-4ce6-b9ed-96fb5a9d43cb)"" pod="store/jarvis-scoxauthentication-846dcc684c-m968j" podUID=7d10cc48-c5f1-4ce6-b9ed-96fb5a9d43cb
Sep 10 19:02:25 ctm-ubantu-vm k3s[22432]: E0910 19:02:25.126594   22432 pod_workers.go:951] "Error syncing pod, skipping" err="failed to "StartContainer" for "init-resources-db" with CrashLoopBackOff: "back-off 5m0s restarting failed container=init-resources-db pod=jarvis-scoxresources-7b5977bdd8-kqcvk_store(be1316a1-d68d-4da0-8d3e-d4d4ea3b92c9)"" pod="store/jarvis-scoxresources-7b5977bdd8-kqcvk" podUID=be1316a1-d68d-4da0-8d3e-d4d4ea3b92c9
Sep 10 19:02:29 ctm-ubantu-vm k3s[22432]: E0910 19:02:29.125896   22432 pod_workers.go:951] "Error syncing pod, skipping" err="failed to "StartContainer" for "init-scoxerrorlookup-db" with CrashLoopBackOff: "back-off 5m0s restarting failed container=init-scoxerrorlookup-db pod=jarvis-scoxerrorlookup-5b5499d866-4h9m5_store(7c272b41-f479-45ab-8018-4176cb20c013)"" pod="store/jarvis-scoxerrorlookup-5b5499d866-4h9m5" podUID=7c272b41-f479-45ab-8018-4176cb20c013
Sep 10 19:02:31 ctm-ubantu-vm k3s[22432]: I0910 19:02:31.293966   22432 event.go:294] "Event occurred" object="store/scoxpicklist-pvc" fieldPath="" kind="PersistentVolumeClaim" apiVersion="v1" type="Normal" reason="WaitForFirstConsumer" message="waiting for first consumer to be created before binding"
Sep 10 19:02:38 ctm-ubantu-vm k3s[22432]: E0910 19:02:38.127052   22432 pod_workers.go:951] "Error syncing pod, skipping" err="failed to "StartContainer" for "init-resources-db" with CrashLoopBackOff: "back-off 5m0s restarting failed container=init-resources-db pod=jarvis-scoxresources-7b5977bdd8-kqcvk_store(be1316a1-d68d-4da0-8d3e-d4d4ea3b92c9)"" pod="store/jarvis-scoxresources-7b5977bdd8-kqcvk" podUID=be1316a1-d68d-4da0-8d3e-d4d4ea3b92c9
Sep 10 19:02:39 ctm-ubantu-vm k3s[22432]: E0910 19:02:39.126370   22432 pod_workers.go:951] "Error syncing pod, skipping" err="failed to "StartContainer" for "init-assets" with CrashLoopBackOff: "back-off 5m0s restarting failed container=init-assets pod=jarvis-jarvisconfigservice-784889995b-28klj_store(612763ca-8629-41ef-8908-1807e11fad82)"" pod="store/jarvis-jarvisconfigservice-784889995b-28klj" podUID=612763ca-8629-41ef-8908-1807e11fad82
Sep 10 19:02:39 ctm-ubantu-vm k3s[22432]: E0910 19:02:39.126464   22432 pod_workers.go:951] "Error syncing pod, skipping" err="failed to "StartContainer" for "init-authentication-db" with CrashLoopBackOff: "back-off 5m0s restarting failed container=init-authentication-db pod=jarvis-scoxauthentication-846dcc684c-m968j_store(7d10cc48-c5f1-4ce6-b9ed-96fb5a9d43cb)"" pod="store/jarvis-scoxauthentication-846dcc684c-m968j" podUID=7d10cc48-c5f1-4ce6-b9ed-96fb5a9d43cb
Sep 10 19:02:44 ctm-ubantu-vm k3s[22432]: E0910 19:02:44.127179   22432 pod_workers.go:951] "Error syncing pod, skipping" err="failed to "StartContainer" for "init-scoxerrorlookup-db" with CrashLoopBackOff: "back-off 5m0s restarting failed container=init-scoxerrorlookup-db pod=jarvis-scoxerrorlookup-5b5499d866-4h9m5_store(7c272b41-f479-45ab-8018-4176cb20c013)"" pod="store/jarvis-scoxerrorlookup-5b5499d866-4h9m5" podUID=7c272b41-f479-45ab-8018-4176cb20c013
Sep 10 19:02:46 ctm-ubantu-vm k3s[22432]: I0910 19:02:46.294585   22432 event.go:294] "Event occurred" object="store/scoxpicklist-pvc" fieldPath="" kind="PersistentVolumeClaim" apiVersion="v1" type="Normal" reason="WaitForFirstConsumer" message="waiting for first consumer to be created before binding"
Sep 10 19:02:50 ctm-ubantu-vm k3s[22432]: E0910 19:02:50.126805   22432 pod_workers.go:951] "Error syncing pod, skipping" err="failed to "StartContainer" for "init-authentication-db" with CrashLoopBackOff: "back-off 5m0s restarting failed container=init-authentication-db pod=jarvis-scoxauthentication-846dcc684c-m968j_store(7d10cc48-c5f1-4ce6-b9ed-96fb5a9d43cb)"" pod="store/jarvis-scoxauthentication-846dcc684c-m968j" podUID=7d10cc48-c5f1-4ce6-b9ed-96fb5a9d43cb
Sep 10 19:02:51 ctm-ubantu-vm k3s[22432]: E0910 19:02:51.126640   22432 pod_workers.go:951] "Error syncing pod, skipping" err="failed to "StartContainer" for "init-resources-db" with CrashLoopBackOff: "back-off 5m0s restarting failed container=init-resources-db pod=jarvis-scoxresources-7b5977bdd8-kqcvk_store(be1316a1-d68d-4da0-8d3e-d4d4ea3b92c9)"" pod="store/jarvis-scoxresources-7b5977bdd8-kqcvk" podUID=be1316a1-d68d-4da0-8d3e-d4d4ea3b92c9
Sep 10 19:02:53 ctm-ubantu-vm k3s[22432]: E0910 19:02:53.126490   22432 pod_workers.go:951] "Error syncing pod, skipping" err="failed to "StartContainer" for "init-assets" with CrashLoopBackOff: "back-off 5m0s restarting failed container=init-assets pod=jarvis-jarvisconfigservice-784889995b-28klj_store(612763ca-8629-41ef-8908-1807e11fad82)"" pod="store/jarvis-jarvisconfigservice-784889995b-28klj" podUID=612763ca-8629-41ef-8908-1807e11fad82
Sep 10 19:02:59 ctm-ubantu-vm k3s[22432]: E0910 19:02:59.127069   22432 pod_workers.go:951] "Error syncing pod, skipping" err="failed to "StartContainer" for "init-scoxerrorlookup-db" with CrashLoopBackOff: "back-off 5m0s restarting failed container=init-scoxerrorlookup-db pod=jarvis-scoxerrorlookup-5b5499d866-4h9m5_store(7c272b41-f479-45ab-8018-4176cb20c013)"" pod="store/jarvis-scoxerrorlookup-5b5499d866-4h9m5" podUID=7c272b41-f479-45ab-8018-4176cb20c013
Sep 10 19:03:01 ctm-ubantu-vm k3s[22432]: I0910 19:03:01.294810   22432 event.go:294] "Event occurred" object="store/scoxpicklist-pvc" fieldPath="" kind="PersistentVolumeClaim" apiVersion="v1" type="Normal" reason="WaitForFirstConsumer" message="waiting for first consumer to be created before binding"
Sep 10 19:03:02 ctm-ubantu-vm k3s[22432]: E0910 19:03:02.127131   22432 pod_workers.go:951] "Error syncing pod, skipping" err="failed to "StartContainer" for "init-authentication-db" with CrashLoopBackOff: "back-off 5m0s restarting failed container=init-authentication-db pod=jarvis-scoxauthentication-846dcc684c-m968j_store(7d10cc48-c5f1-4ce6-b9ed-96fb5a9d43cb)"" pod="store/jarvis-scoxauthentication-846dcc684c-m968j" podUID=7d10cc48-c5f1-4ce6-b9ed-96fb5a9d43cb
Sep 10 19:03:04 ctm-ubantu-vm k3s[22432]: E0910 19:03:04.127892   22432 pod_workers.go:951] "Error syncing pod, skipping" err="failed to "StartContainer" for "init-resources-db" with CrashLoopBackOff: "back-off 5m0s restarting failed container=init-resources-db pod=jarvis-scoxresources-7b5977bdd8-kqcvk_store(be1316a1-d68d-4da0-8d3e-d4d4ea3b92c9)"" pod="store/jarvis-scoxresources-7b5977bdd8-kqcvk" podUID=be1316a1-d68d-4da0-8d3e-d4d4ea3b92c9
Sep 10 19:03:06 ctm-ubantu-vm k3s[22432]: E0910 19:03:06.126792   22432 pod_workers.go:951] "Error syncing pod, skipping" err="failed to "StartContainer" for "init-assets" with CrashLoopBackOff: "back-off 5m0s restarting failed container=init-assets pod=jarvis-jarvisconfigservice-784889995b-28klj_store(612763ca-8629-41ef-8908-1807e11fad82)"" pod="store/jarvis-jarvisconfigservice-784889995b-28klj" podUID=612763ca-8629-41ef-8908-1807e11fad82

logfiles.zip
Uploaded the files in zip.....PFA

Although they appear to be currently running, the logs show that many of the pods for packaged components (such as metrics-server) were stuck crashlooping from the beginning of the log at Sep 02 15:35:06 until Sep 02 19:48:45, just after a restart of the k3s service. It looks like you made some changes to the system configuration that allowed the pods to work. Can you provide more information on how you configured K3s (any CLI flags or configuration files you added) as well as information on what you changed around that time?

I have configured the k3's service using the below steps
$ export CLUSTER_CIDR=<IP_ADDRESS>/24
$ export SERVICE_CIDR=<IP_ADDRESS>/24
export EXTERNAL_IP=
you can get it by running: ifconfig
$ export EXTERNAL_IP=<Your_VM_External_IP>
$ export K3S_KUBECONFIG_MODE="644"
$ export INSTALL_K3S_EXEC="--cluster-cidr $CLUSTER_CIDR --service-cidr $SERVICE_CIDR --node-external-ip $EXTERNAL_IP"
$ curl -sfL https://get.k3s.io | sh -
$ k3s -v
$ systemctl status k3s.service
Just for a quick workaround, i have performed the below troubleshooting steps in order to find the root cause

i have disabled the os firewalls (getenforce,iptables,firewalld)
In inorder to check the connectivity.i have deployed one gcloud pod in the same ubuntu VM(where k3s is running) and logged in inside of the pod and ran the gcloud auth login    however it has thrown the same error like below

ERROR: gcloud crashed (TransportError): HTTPSConnectionPool(host='oauth2.googleapis.com', port=443): Max retries exceeded with url: /token (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fa61e401ee0>: Failed to establish a new connection: [Errno -3] Try again'))
It seems something is blocking the pod network  due to that it is unable to authenticate to the gcloud services

Yeah, it looks like container networking is not working for some reason. Can I ask why you've changed the container and service CIDR ranges? Do your custom ranges overlap with any of the subnets that the node is on? Can you confirm that there are no GCP-level security group rules that are interfering with outbound connections?

No David,
i have checked all the egress and ingress rules in gcp which is allowed the connectivity to all my subnets
And coming to the CIDR ranges configuration yes we use above configurations for all our dev environments.  we had setup the same environment in centos vm there we didn't face any challenges all pods are seamlessly communicating to the GCP services
I think there might be some additional network configurations required in ubuntu machines for rancher k3s setup  or else some bridge has to be established between the network interfaces

There isn't generally any special setup necessary on Ubuntu. Is there anything else installed on this node that might be interfering with this traffic? Docker, additional software managing firewall configuration or iptables, etc?

No we haven't install anything otherrhan k3s

There isn't generally any special setup necessary on Ubuntu. Is there anything else installed on this node that might be interfering with this traffic? Docker, additional software managing firewall configuration or iptables, etc?

No we haven't install anything otherrhan k3s

There isn't generally any special setup necessary on Ubuntu. Is there anything else installed on this node that might be interfering with this traffic? Docker, additional software managing firewall configuration or iptables, etc?

no we haven't installed anything other than k3s

I have this issue too. Fresh install k3s v1.24.4+k3s1 on Ubuntu 18.04 with the ufw disabled by default, and iptables version 1.6.1 . Look like the network has an issue. From pod, I can ping to the host IP, but cannot ping to the host network default gateway. Changed the host OS to Ubuntu 20.04, and everything work fine.