Refactor e2e bookinfo tests

extract a common constant
let the routing rules reside in different directories (required for tests for https://github.com/istio/istio/pull/3940)

@vadimeisenbergibm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
bc06192e1f73b0e9639340510fb80eebf4ff1b5b
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-unit-tests

@vadimeisenbergibm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
bc06192e1f73b0e9639340510fb80eebf4ff1b5b
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
bc06192e1f73b0e9639340510fb80eebf4ff1b5b
link
/test istio-unit-tests

prow/e2e-bookInfoTests.sh
bc06192e1f73b0e9639340510fb80eebf4ff1b5b
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
65cc312bc13c193e8e5923f0ed1b63c02c37ad9f
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Need to rethink this.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
65cc312bc13c193e8e5923f0ed1b63c02c37ad9f
link
/test e2e-bookInfo

prow/istio-unit-tests.sh
13742e053c381cd271556b4346819408ee72e9a8
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
13742e053c381cd271556b4346819408ee72e9a8
link
/test istio-unit-tests

prow/e2e-bookInfoTests.sh
13742e053c381cd271556b4346819408ee72e9a8
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
13742e053c381cd271556b4346819408ee72e9a8
link
/test istio-unit-tests

prow/e2e-bookInfoTests.sh
13742e053c381cd271556b4346819408ee72e9a8
link
/test e2e-bookInfo

prow/istio-pilot-e2e.sh
13742e053c381cd271556b4346819408ee72e9a8
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
13742e053c381cd271556b4346819408ee72e9a8
link
/test e2e-bookInfo

prow/istio-pilot-e2e.sh
d0303693aa8973f9504604472c90dd550207658d
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-pilot-e2e

/retest

@vadimeisenbergibm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
d0303693aa8973f9504604472c90dd550207658d
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-unit-tests

@vadimeisenbergibm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
d0303693aa8973f9504604472c90dd550207658d
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-unit-tests

@ldemailly could you please review and approve? The codecov/project fails, unclear why. codecov/patch succeeds with no change in the coverage.

/test e2e-rbac-auth

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
4615a997a879cd1cdc21acbb70cb96eba5465242
link
/test e2e-bookInfo

prow/istio-unit-tests.sh
2f09e41a655988ca983c7cdf900a06bccfcb671e
link
/test istio-unit-tests

prow/istio-pilot-e2e.sh
2f09e41a655988ca983c7cdf900a06bccfcb671e
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
2f09e41a655988ca983c7cdf900a06bccfcb671e
link
/test istio-pilot-e2e

prow/istio-unit-tests.sh
2f7a3f2d709a175afe6688814d2ae48465fd937a
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
2f7a3f2d709a175afe6688814d2ae48465fd937a
link
/test istio-unit-tests

prow/istio-pilot-e2e.sh
2f7a3f2d709a175afe6688814d2ae48465fd937a
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@vadimeisenbergibm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
2f7a3f2d709a175afe6688814d2ae48465fd937a
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
2f7a3f2d709a175afe6688814d2ae48465fd937a
link
/test istio-pilot-e2e

prow/istio-unit-tests.sh
3706b8d3c0f934909072064d6519088bd7f1b1b3
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-unit-tests

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
2f7a3f2d709a175afe6688814d2ae48465fd937a
link
/test istio-pilot-e2e

prow/istio-unit-tests.sh
3706b8d3c0f934909072064d6519088bd7f1b1b3
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
2f7a3f2d709a175afe6688814d2ae48465fd937a
link
/test istio-pilot-e2e

prow/istio-unit-tests.sh
3706b8d3c0f934909072064d6519088bd7f1b1b3
link
/test istio-unit-tests

prow/e2e-bookInfoTests.sh
3706b8d3c0f934909072064d6519088bd7f1b1b3
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
3706b8d3c0f934909072064d6519088bd7f1b1b3
link
/test istio-unit-tests

prow/e2e-bookInfoTests.sh
3706b8d3c0f934909072064d6519088bd7f1b1b3
link
/test e2e-bookInfo

prow/istio-pilot-e2e.sh
3706b8d3c0f934909072064d6519088bd7f1b1b3
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
3706b8d3c0f934909072064d6519088bd7f1b1b3
link
/test e2e-bookInfo

prow/istio-pilot-e2e.sh
9b8f5a449a544d3f5455a21e6bf636c8b891caf4
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-pilot-e2e

@vadimeisenbergibm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
9b8f5a449a544d3f5455a21e6bf636c8b891caf4
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
9b8f5a449a544d3f5455a21e6bf636c8b891caf4
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
a21a7a6fd5647499d15a3cc598f9b24d6ad5335c
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
a21a7a6fd5647499d15a3cc598f9b24d6ad5335c
link
/test e2e-bookInfo

prow/istio-pilot-e2e.sh
a21a7a6fd5647499d15a3cc598f9b24d6ad5335c
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
a21a7a6fd5647499d15a3cc598f9b24d6ad5335c
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
85929ba95764c6e7ac54515f5d2e899b482615d5
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
85929ba95764c6e7ac54515f5d2e899b482615d5
link
/test e2e-bookInfo

prow/istio-pilot-e2e.sh
85929ba95764c6e7ac54515f5d2e899b482615d5
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
85929ba95764c6e7ac54515f5d2e899b482615d5
link
/test e2e-bookInfo

prow/istio-pilot-e2e.sh
ae6f7c9afc768c6af9123800893308691829ec86
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-pilot-e2e

@vadimeisenbergibm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
ae6f7c9afc768c6af9123800893308691829ec86
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-pilot-e2e

@vadimeisenbergibm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
ae6f7c9afc768c6af9123800893308691829ec86
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-pilot-e2e

@vadimeisenbergibm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
ae6f7c9afc768c6af9123800893308691829ec86
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-pilot-e2e

@vadimeisenbergibm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
ae6f7c9afc768c6af9123800893308691829ec86
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
ae6f7c9afc768c6af9123800893308691829ec86
link
/test istio-pilot-e2e

prow/istio-unit-tests.sh
90874fcd267986b7c6d41ec198825523391db571
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-unit-tests

@vadimeisenbergibm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
90874fcd267986b7c6d41ec198825523391db571
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-pilot-e2e

@vadimeisenbergibm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
90874fcd267986b7c6d41ec198825523391db571
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ldemailly Could you please approve this PR?

/lgtm


(#1065) Add Highlight information to readme

Description Of Changes
This adds information on how to add a new Highlight to both the left sidebar and the home page of docs.chocolatey.org.
Motivation and Context
This process was not documented with the switch to Astro.
Testing
The best way to test this would be to go through the steps added to the readme, and try adding a "hypothetical" Home Highlight and Sidebar Highlight, and note if any of the instructions are not clear or confusing.

[x] I have previewed these changes using the Docker Container or another method before submitting this pull request.

Change Types Made

[x] Minor documentation fix (typos etc.).
[ ] Major documentation change (refactoring, reformatting or adding documentation to existing page).
[ ] New documentation page added.
[ ] The change I have made should have a video added, and I have raised an issue for this.

Issue #

Change Checklist

[ ] Requires a change to menu structure (top or left-hand side)/
[ ] Menu structure has been updated

Related Issue

#1065

Fixes #1065

@AdmiringWorm Would you be able to take a look at this for me? Thanks!

@st3phhays thanks for getting this information added. This should help in the future whenever we need to add highlights.


New Luigi Task: Update the Collections & Targets Solr instance

The original code by @chrispeacockbl needs porting into a Luigi task.
The Solr schema is here, and I've set up a Docker image build to create a containerised version here.

I've created tasks (currently here) that download a copy of the W3ACT data and use it to generate useful artefacts (e.g. annotations for resource-level indexing).
The specific code to update Solr is being added there at the moment.

Now added (e7e136527e5aeeae11bad6f1c2b0f8753076f439) and running against the BETA Collections Solr instance.

Worked fine!


fix: prism highlighted line breaking

The current implementation of line breaking of Prism-highlighted code is incorrect. It first splits code in separate lines and feed these to the highlight method. This does not work correctly for many kinds of code: JavaScript multiline strings and doc comments, XML attributes over multiple lines, etc.
As an alternative this PR sends the whole code to Prism and then splits line by line. A problem that then occurs: a newline can start when one or more tags are still open. In the PR I addressed this by parsing the HTML and closing/reopening tags for each line. I've searched the Prism API to see if there is some way around this, but haven't found it yet.

@antfu Those lint errors were not introduced by my code it seems.


SUPPORTS_EXPRESSION_COMPILE_WITH_PREFER_INTERPRETATION_PARAM

Argument 1: cannot convert from 'bool' to 'System.Runtime.CompilerServices.DebugInfoGenerator'

Sorry hit wrong key

So, is this closed or not?

@dadhi very sorry about this.
I was attempting to use DryIoc as a source code include, however; I got a compilation error:
Severity	Code	Description	Project	File	Line	Suppression State
Error	CS1503	Argument 1: cannot convert from 'bool' to 'System.Runtime.CompilerServices.DebugInfoGenerator'	Connexion.Share	C:\Users\jonre.nuget\packages\dryioc\4.1.0\contentFiles\cs\net45\DryIoc\Container.cs	3767	N/A
It seems as though Visual Studio 2019 is not properly setting NET461 when 461 is the targeted framework version. To work-around this issue I manually set NET461 in the project build "Conditional compilation symbols". A hack for sure. I am using Visual Studio Version 16.4.5 in for your info. Also, when I used NET472 I did not get this error.
I am pretty sure this is not a bug in DryIoc, rather an issue with Visual Studio. As far as I can tell all the compiler directives are correct.

Ah, I see. Thank you for the explanation. Cheers.


Node-problem-detector-app for CAPA

User Story
Currently node-problem-detector-app is working only on Vintage installation. The application acts as exporter where the aws-operator handles the nodes termination as added in: https://github.com/giantswarm/aws-operator/blob/master/CHANGELOG.md#14240---2023-11-20. The app itself has proven to be very effective in terminating problematic nodes with full disks as well as provides a lot of useful information for GS staff and Customers with regards to node health status.
Currently this is not possible on CAPA. We have to review the CAPA capabilities for marking and terminating the node, such that the app can be utilized in the CAPI as well.
Acceptance Criteria

[ ] Discover the CAPA capabilities for marking for deletion and terminating the nodes at will
[ ] Based on discovery, add a feature such that the node-problem-detector-app can be installed and used on CAPA clusters.

Implementation details

Implementation info to be filled out by engineer

Things that happened when node reached 92% kubelet

Something is evicting the pods

All the previous steps node-problem-detector did not act, once I filled 99.5%:
I0618 13:26:12.131911       1 log_monitor.go:78] Finish parsing log monitor config file /config/kernel-monitor.json: {WatcherConfig:{Plugin:kmsg PluginConfig:map] LogPath:/dev/kmsg Lookback:5m Delay:} BufferSize:10 Source:kernel-monitor DefaultConditions:[{Type:KernelDeadlock Status: Transition:0001-01-01 00:00:00 +0000 UTC Reason:KernelHasNoDeadlock Message:kernel has no deadlock} {Type:ReadonlyFilesystem Status: Transition:0001-01-01 00:00:00 +0000 UTC Reason:FilesystemIsNotReadOnly Message:Filesystem is not read-only}] Rules:[{Type:temporary Condition: Reason:OOMKilling Pattern:Killed process \d+ (.+) total-vm:\d+kB, anon-rss:\d+kB, file-rss:\d+kB.*} {Type:temporary Condition: Reason:TaskHung Pattern:task [\S ]+:\w+ blocked for more than \w+ seconds\.} {Type:temporary Condition: Reason:UnregisterNetDevice Pattern:unregister_netdevice: waiting for \w+ to become free. Usage count = \d+} {Type:temporary Condition: Reason:KernelOops Pattern:BUG: unable to handle kernel NULL pointer dereference at .*} {Type:temporary Condition: Reason:KernelOops Pattern:divide error: 0000 \[#\d+\] SMP} {Type:temporary Condition: Reason:Ext4Error Pattern:EXT4-fs error .*} {Type:temporary Condition: Reason:Ext4Warning Pattern:EXT4-fs warning .*} {Type:temporary Condition: Reason:IOError Pattern:Buffer I/O error .*} {Type:temporary Condition: Reason:MemoryReadError Pattern:CE memory read error .*} {Type:permanent Condition:KernelDeadlock Reason:DockerHung Pattern:task docker:\w+ blocked for more than \w+ seconds\.} {Type:permanent Condition:ReadonlyFilesystem Reason:FilesystemIsReadOnly Pattern:Remounting filesystem read-only}] EnableMetricsReporting:0xc00005284e}
I0618 13:26:12.132022       1 log_watchers.go:40] Use log watcher of plugin "kmsg"
I0618 13:26:12.132187       1 log_monitor.go:78] Finish parsing log monitor config file /config/docker-monitor.json: {WatcherConfig:{Plugin:journald PluginConfig:map[source:dockerd] LogPath:/var/log/journal Lookback:5m Delay:} BufferSize:10 Source:docker-monitor DefaultConditions:[{Type:CorruptDockerOverlay2 Status: Transition:0001-01-01 00:00:00 +0000 UTC Reason:NoCorruptDockerOverlay2 Message:docker overlay2 is functioning properly}] Rules:[{Type:temporary Condition: Reason:CorruptDockerImage Pattern:Error trying v2 registry: failed to register layer: rename /var/lib/docker/image/(.+) /var/lib/docker/image/(.+): directory not empty.*} {Type:permanent Condition:CorruptDockerOverlay2 Reason:CorruptDockerOverlay2 Pattern:returned error: readlink /var/lib/docker/overlay2.*: invalid argument.*} {Type:temporary Condition: Reason:DockerContainerStartupFailure Pattern:OCI runtime start failed: container process is already dead: unknown}] EnableMetricsReporting:0xc000052fb0}
I0618 13:26:12.132213       1 log_watchers.go:40] Use log watcher of plugin "journald"
I0618 13:26:12.132418       1 custom_plugin_monitor.go:80] Finish parsing custom plugin monitor config file /custom-config/full-disk-check.json: {Plugin:custom PluginGlobalConfig:{InvokeIntervalString:0xc00055cd00 TimeoutString:0xc00055cd10 InvokeInterval:1m0s Timeout:30s MaxOutputLength:0xc0000535f8 Concurrency:0xc000053608 EnableMessageChangeBasedConditionUpdate:0xc000053610 SkipInitialStatus:0x24fd22e} Source:node-problem-detector DefaultConditions:[{Type:DiskFullKubelet Status: Transition:0001-01-01 00:00:00 +0000 UTC Reason:KubeletDiskIsNotFull Message:/var/lib/kubelet is not full} {Type:DiskFullContainerd Status: Transition:0001-01-01 00:00:00 +0000 UTC Reason:ContainerdDiskIsNotFull Message:/var/lib/containerd is not full} {Type:DiskFullVarLog Status: Transition:0001-01-01 00:00:00 +0000 UTC Reason:VarLogDiskIsNotFull Message:/var/log is not full}] Rules:[0xc000550ee0 0xc000550f50 0xc000551030 0xc000551110 0xc000551180 0xc0005511f0] EnableMetricsReporting:0xc000053611}
I0618 13:26:12.133299       1 k8s_exporter.go:55] Waiting for kube-apiserver to be ready (timeout 5m0s)...
I0618 13:26:12.141375       1 node_problem_detector.go:56] K8s exporter started.
I0618 13:26:12.141562       1 node_problem_detector.go:60] Prometheus exporter started.
I0618 13:26:12.141585       1 log_monitor.go:110] Start log monitor /config/kernel-monitor.json
I0618 13:26:12.141639       1 log_monitor.go:110] Start log monitor /config/docker-monitor.json
I0618 13:26:12.141818       1 log_monitor.go:235] Initialize condition generated: [{Type:KernelDeadlock Status:False Transition:2024-06-18 13:26:12.141817594 +0000 UTC m=+0.022926244 Reason:KernelHasNoDeadlock Message:kernel has no deadlock} {Type:ReadonlyFilesystem Status:False Transition:2024-06-18 13:26:12.14181771 +0000 UTC m=+0.022926351 Reason:FilesystemIsNotReadOnly Message:Filesystem is not read-only}]
I0618 13:26:12.144019       1 custom_plugin_monitor.go:111] Start custom plugin monitor /custom-config/full-disk-check.json
I0618 13:26:12.144089       1 problem_detector.go:77] Problem detector started
I0618 13:26:12.144125       1 log_monitor.go:235] Initialize condition generated: [{Type:CorruptDockerOverlay2 Status:False Transition:2024-06-18 13:26:12.144124855 +0000 UTC m=+0.025233507 Reason:NoCorruptDockerOverlay2 Message:docker overlay2 is functioning properly}]
I0618 13:26:12.144134       1 custom_plugin_monitor.go:300] Initialize condition generated: [{Type:DiskFullKubelet Status:False Transition:2024-06-18 13:26:12.144133845 +0000 UTC m=+0.025242499 Reason:KubeletDiskIsNotFull Message:/var/lib/kubelet is not full} {Type:DiskFullContainerd Status:False Transition:2024-06-18 13:26:12.144133958 +0000 UTC m=+0.025242598 Reason:ContainerdDiskIsNotFull Message:/var/lib/containerd is not full} {Type:DiskFullVarLog Status:False Transition:2024-06-18 13:26:12.144134029 +0000 UTC m=+0.025242665 Reason:VarLogDiskIsNotFull Message:/var/log is not full}]
I0618 13:42:12.153632       1 custom_plugin_monitor.go:280] New status generated: &{Source:node-problem-detector Events:[{Severity:warn Timestamp:2024-06-18 13:42:12.153577368 +0000 UTC m=+960.034686023 Reason:KubeletDiskIsFull Message:Disk /dev/nvme1n1 (mount point /var/lib/kubelet) is full.}] Conditions:[{Type:DiskFullKubelet Status:False Transition:2024-06-18 13:26:12.144133845 +0000 UTC m=+0.025242499 Reason:KubeletDiskIsNotFull Message:/var/lib/kubelet is not full} {Type:DiskFullContainerd Status:False Transition:2024-06-18 13:26:12.144133958 +0000 UTC m=+0.025242598 Reason:ContainerdDiskIsNotFull Message:/var/lib/containerd is not full} {Type:DiskFullVarLog Status:False Transition:2024-06-18 13:26:12.144134029 +0000 UTC m=+0.025242665 Reason:VarLogDiskIsNotFull Message:/var/log is not full}]}
I0618 13:42:12.162703       1 custom_plugin_monitor.go:280] New status generated: &{Source:node-problem-detector Events:[{Severity:warn Timestamp:2024-06-18 13:42:12.16264322 +0000 UTC m=+960.043751902 Reason:KubeletDiskIsFull Message:Node condition DiskFullKubelet is now: True, reason: KubeletDiskIsFull, message: "Disk /dev/nvme1n1 (mount point /var/lib/kubelet) is full."}] Conditions:[{Type:DiskFullKubelet Status:True Transition:2024-06-18 13:42:12.16264322 +0000 UTC m=+960.043751902 Reason:KubeletDiskIsFull Message:Disk /dev/nvme1n1 (mount point /var/lib/kubelet) is full.} {Type:DiskFullContainerd Status:False Transition:2024-06-18 13:26:12.144133958 +0000 UTC m=+0.025242598 Reason:ContainerdDiskIsNotFull Message:/var/lib/containerd is not full} {Type:DiskFullVarLog Status:False Transition:2024-06-18 13:26:12.144134029 +0000 UTC m=+0.025242665 Reason:VarLogDiskIsNotFull Message:/var/log is not full}]}
I0618 13:42:12.171477       1 custom_plugin_monitor.go:280] New status generated: &{Source:node-problem-detector Events:[{Severity:warn Timestamp:2024-06-18 13:42:12.171433173 +0000 UTC m=+960.052541820 Reason:ContainerdDiskIsFull Message:Disk /dev/nvme1n1 (mount point /var/lib/containerd) is full.}] Conditions:[{Type:DiskFullKubelet Status:True Transition:2024-06-18 13:42:12.16264322 +0000 UTC m=+960.043751902 Reason:KubeletDiskIsFull Message:Disk /dev/nvme1n1 (mount point /var/lib/kubelet) is full.} {Type:DiskFullContainerd Status:False Transition:2024-06-18 13:26:12.144133958 +0000 UTC m=+0.025242598 Reason:ContainerdDiskIsNotFull Message:/var/lib/containerd is not full} {Type:DiskFullVarLog Status:False Transition:2024-06-18 13:26:12.144134029 +0000 UTC m=+0.025242665 Reason:VarLogDiskIsNotFull Message:/var/log is not full}]}
I0618 13:42:12.180270       1 custom_plugin_monitor.go:280] New status generated: &{Source:node-problem-detector Events:[{Severity:warn Timestamp:2024-06-18 13:42:12.180236896 +0000 UTC m=+960.061345558 Reason:ContainerdDiskIsFull Message:Node condition DiskFullContainerd is now: True, reason: ContainerdDiskIsFull, message: "Disk /dev/nvme1n1 (mount point /var/lib/containerd) is full."}] Conditions:[{Type:DiskFullKubelet Status:True Transition:2024-06-18 13:42:12.16264322 +0000 UTC m=+960.043751902 Reason:KubeletDiskIsFull Message:Disk /dev/nvme1n1 (mount point /var/lib/kubelet) is full.} {Type:DiskFullContainerd Status:True Transition:2024-06-18 13:42:12.180236896 +0000 UTC m=+960.061345558 Reason:ContainerdDiskIsFull Message:Disk /dev/nvme1n1 (mount point /var/lib/containerd) is full.} {Type:DiskFullVarLog Status:False Transition:2024-06-18 13:26:12.144134029 +0000 UTC m=+0.025242665 Reason:VarLogDiskIsNotFull Message:/var/log is not full}]}

Node gets conditions KubeletDiskIsFull and ContainerdDiskIsFull
Conditions:
  Type                    Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
  ----                    ------  -----------------                 ------------------                ------                       -------
  KernelDeadlock          False   Tue, 18 Jun 2024 15:42:13 +0200   Tue, 18 Jun 2024 15:26:12 +0200   KernelHasNoDeadlock          kernel has no deadlock
  ReadonlyFilesystem      False   Tue, 18 Jun 2024 15:42:13 +0200   Tue, 18 Jun 2024 15:26:12 +0200   FilesystemIsNotReadOnly      Filesystem is not read-only
  CorruptDockerOverlay2   False   Tue, 18 Jun 2024 15:42:13 +0200   Tue, 18 Jun 2024 15:26:12 +0200   NoCorruptDockerOverlay2      docker overlay2 is functioning properly
  DiskFullKubelet         True    Tue, 18 Jun 2024 15:42:13 +0200   Tue, 18 Jun 2024 15:42:12 +0200   KubeletDiskIsFull            Disk /dev/nvme1n1 (mount point /var/lib/kubelet) is full.
  DiskFullContainerd      True    Tue, 18 Jun 2024 15:42:13 +0200   Tue, 18 Jun 2024 15:42:12 +0200   ContainerdDiskIsFull         Disk /dev/nvme1n1 (mount point /var/lib/containerd) is full.
  DiskFullVarLog          False   Tue, 18 Jun 2024 15:42:13 +0200   Tue, 18 Jun 2024 15:26:12 +0200   VarLogDiskIsNotFull          /var/log is not full
  NetworkUnavailable      False   Tue, 18 Jun 2024 15:03:09 +0200   Tue, 18 Jun 2024 15:03:09 +0200   CiliumIsUp                   Cilium is running on this node
  MemoryPressure          False   Tue, 18 Jun 2024 15:42:10 +0200   Tue, 18 Jun 2024 15:01:40 +0200   KubeletHasSufficientMemory   kubelet has sufficient memory available
  DiskPressure            True    Tue, 18 Jun 2024 15:42:10 +0200   Tue, 18 Jun 2024 15:34:41 +0200   KubeletHasDiskPressure       kubelet has disk pressure
  PIDPressure             False   Tue, 18 Jun 2024 15:42:10 +0200   Tue, 18 Jun 2024 15:01:40 +0200   KubeletHasSufficientPID      kubelet has sufficient PID available
  Ready                   True    Tue, 18 Jun 2024 15:42:10 +0200   Tue, 18 Jun 2024 15:03:12 +0200   KubeletReady                 kubelet is posting ready status

Then we use the following library from aws operator to detect nodes with certain conditions and kill them: https://github.com/giantswarm/badnodedetector/blob/a3f3023c84ae3791b06b59dbe2f198a6742d4cdc/pkg/detector/detector.go#L32

According to node-problem-detector we have some options:

Does anyone know of any annotation/label that would delete an instance from a CAPA controller?

taking into consideration listed options above, we have two paths to follow:

Investigate with potentially contributing upstream the MachineHealthChecks implementation for MachinePools: https://github.com/giantswarm/giantswarm/issues/28006

(If first one fails) Implement the cronjob that checks the machine state and removes it directly on AWS if machine is full based on the node-problem-detector status


chore: fix last_value coercion

Which issue does this PR close?
Closes #10781
Rationale for this change

Fix coercion bug in last_value()
What changes are included in this PR?
Support type signature for numeric string
Are these changes tested?
Yes, tests are added
Are there any user-facing changes?
Yes, users will no longer get an error when query with last_value()

The code looks good to me -- I am writing a test for this now.

@alamb Thank you for adding the tests! 💯

Thanks for the review @jayzhan211


ci: test Node.js 6, 8, 10 and 11

What:
All supported Node.js versions should be tested to catch any issues on newer LTS releases.
Why:
To ensure that there are no breaking builds on Node.js 6, 10 and 11.
How:
Updated the Travis CI config.
Checklist:

[ ] Documentation
[ ] Tests
[x] Ready to be merged
[ ] Added myself to contributors table

Node 6 is not supported, but other than that this is a good idea

Node 6 is not supported, but other than that this is a good idea

See the engines field which says node >= 6.

Node 6 is not supported, but other than that this is a good idea

If so, it should be node >= 8 in the engines field.

https://github.com/kentcdodds/dom-testing-library/blob/master/package.json#L24

Thanks!

:tada: This PR is included in version 3.12.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add sonobuoy gen config file and documentation

The Sonobuoy config file is a little mysterious to most
users since the values are only really defined in code
and not well documented.
This change adds a command to output the default config
so that users might tweak the values they need more
easily.
In addition, I updated the documentation to make it more
clear for everyone what the configuration file is and
how each of the files are used.
Fixes #661
Signed-off-by: John Schnake<EMAIL_ADDRESS>Release note:
release-note

Had a few debug items I just removed from the build. I originally built it based on the config.New() function but found that the CLI adds some extra logic (mainly defaulting the plugin selection).
Build/test should pass now. No extra test added as the field ordering and UUIDs will make testing against a goldenfile/configuration difficult. It is just printing out an object so manual testing at this time is OK IMO.

Codecov Report

Merging #680 into master will decrease coverage by 0.17%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #680      +/-   ##
==========================================
- Coverage   32.65%   32.48%   -0.18%
==========================================
  Files          60       61       +1
  Lines        3316     3334      +18
==========================================
  Hits         1083     1083
- Misses       2140     2158      +18
  Partials       93       93

Impacted Files
Coverage Δ

cmd/sonobuoy/app/gen_config.go
0% <0%> (ø)

cmd/sonobuoy/app/root.go
0% <0%> (ø)
:arrow_up:

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 b420055...0c2d0d1. Read the comment docs.


⚠ Bofrost.at has degraded performance

In 61edf09, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1287 ms

Resolved: Bofrost.at performance has improved in b399488 after 13 minutes.


Issue with gtfparse during dataloading

Hi,
I hope you are doing well,
When I try installing riboformer using your instruction i seems to run into a problem when it is trying to load the gtf.
It seems like the version of gtfparse and polar given in your setup file have a conflict.
Here is the error message
  File "/opt/conda/envs/ribo/bin/riboformer", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/opt/conda/envs/ribo/lib/python3.11/site-packages/transcript_transformer/riboformer.py", line 84, in main
    process_seq_data(
  File "/opt/conda/envs/ribo/lib/python3.11/site-packages/transcript_transformer/data.py", line 69, in process_seq_data
    data_dict = parse_transcriptome(gtf_path, fa_path)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/ribo/lib/python3.11/site-packages/transcript_transformer/data.py", line 174, in parse_transcriptome
    gtf = read_gtf(gtf_path)
          ^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/ribo/lib/python3.11/site-packages/gtfparse/read_gtf.py", line 254, in read_gtf
    result_df = parse_gtf_and_expand_attributes(
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/ribo/lib/python3.11/site-packages/gtfparse/read_gtf.py", line 189, in parse_gtf_and_expand_attributes
    df = parse_gtf(
         ^^^^^^^^^^
  File "/opt/conda/envs/ribo/lib/python3.11/site-packages/gtfparse/read_gtf.py", line 155, in parse_gtf
    df_lazy = parse_with_polars_lazy(
              ^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/ribo/lib/python3.11/site-packages/gtfparse/read_gtf.py", line 87, in parse_with_polars_lazy
    polars.toggle_string_cache(True)
    ^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: module 'polars' has no attribute 'toggle_string_cache'. Did you mean: 'enable_string_cache'?

Now I tried running it with a modified version correcting this exact deprecation but it seems to cause another error. I have the feeling that if i try fixing the errors other error will keep popping-up. So i was wondering if you could specify the exact version of polar and gtfparse used in your working build.
I also tried running it using the gtfparse branch created by y9c and i get this error
  File "/opt/conda/envs/ribo/bin/riboformer", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/opt/conda/envs/ribo/lib/python3.11/site-packages/transcript_transformer/riboformer.py", line 84, in main
    process_seq_data(
  File "/opt/conda/envs/ribo/lib/python3.11/site-packages/transcript_transformer/data.py", line 69, in process_seq_data
    data_dict = parse_transcriptome(gtf_path, fa_path)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/ribo/lib/python3.11/site-packages/transcript_transformer/data.py", line 175, in parse_transcriptome
    gtf = gtf.with_columns(pl.col("exon_number").cast(pl.Int32, strict=False))
          ^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/ribo/lib/python3.11/site-packages/pandas/core/generic.py", line 6204, in __getattr__
    return object.__getattribute__(self, name)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'DataFrame' object has no attribute 'with_columns'

I dont know if the modification made by y9c changed the returned object from something with a .with_column attribute to a normal pandas dataframe or something.
can you help me fix the problem
Best
Nicolas

update:
I succeded in fixing it by using a cloned version of gtfparse
line 87 was alterted to change toggle_string_cache(True) to enable_string_cache(True)
and line 90 sep was replaced with separator

Thanks for this, looking into fixing this now.

Should be fixed for v0.5.3. Apologies for the inconvenience.

Hi it seems to have indeed fixed this problem but now I run into the same problem as the issue on the riboformer github when using an environement installed from installing pytorch and transcript_tranformer as shown
https://github.com/jdcla/RIBO_former/issues/4
I wanted to share to you that my version of gtfparser(with only the 2 line modified as explained above) seems to be able to run past that problem and create the h5 file
Now i dont know if gtfparse is actually the reason behind the issue when we dont get a traceback to it and if my modifications that seems to solve the problem are going to create more problems down the line
I am right now running into an issues that is caused by me, once i fix it ill keep you updated if anything else comes up
Anyway, Thanks a lot for being proactive in answering and fixing the issues
Nicolas

Hey Nicolas,
I simply suggest you get rid of your gtfparser installation and update the package. I have created gtfparser_transcript_transformer on pypi that is loaded as a dependency.
See the other thread that discusses your issue.
Thanks for the feedback.

Alright will be using this configuration fomr now on.
Thanks for the help, I'll consider this issue resolved :)


How  to use my .ckpt file to fill the sameple_submission.csv file in the dataset?

Thanks a lot for your blog.
I learn a lot!
How can  I fill the sameple_submission.csv automo automatically ？
Thanks~~

sorry~
I have found the issuses that was closed
Thanks~


Update docs with None parameters to use Optional

Closes issue #1561.

@tiangolo We're ready for review.

@Kludex Hey Marcelo! I made the changes requested! Could you take another look at this issue?

Thanks for all the work here @chrisngyn , @YKo20010 , @kx-chen ! :nerd_face: :memo: :clap: :clap: :clap:
And thanks for the help @Kludex ! :bow: :coffee:
I updated a couple of things, a couple of tests and added a couple of extra notes.
Sadly, for some reason, I can't push those changes to your branch (as I normally would :thinking: ) so I created a new branch with all the changes here: https://github.com/tiangolo/fastapi/pull/1644 and I just merged it.
The good news is that all your commits (with authors) are preserved, you can now see your "contributor" badge in your comments on this same thread :smile: :tada:
I'll close this one now as it's all included there. :rocket:
Thanks for your contribution! :cake: :tada:


refactor: adopt new metadata format for compliance mapping

As part of the compliance mappings efforts of Chris, we're introducing a new metadata format for the controls attribute.
opa-rules related changes can be seen in this PR.

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


reference for other species

Hi!
I would like to support other species as well, at least maybe mouse data.
where did you get the tRNA sequences in that format? any way to get the one for mouse in the same format?
thanks!

The way the included human FASTA file was generated was:
Downloaded tRNA FASTA from GtRNAdb (link for mouse: http://gtrnadb.ucsc.edu/genomes/eukaryota/Mmusc10/mm10-tRNAs.fa)
For mature:
a) Reformatted the header of the mature sequences to be >tRNA_name \t predicted_anti-codon_positions
b) Removed predicted introns
c) added CCA to the tail
The GtRNAdb has been updated since I made the FASTA and I don't know where to predicted anti-codon or intron data is. I will let you know when I find out.
For pre-tRNA
a) added 40 nts upstream and downstream of the predicted tRNA sequence and added a "pre" to the name. The naming scheme is described in detail in the "Naming tDRs" section (b) of the README.
Then these two files are combined together into one FASTA file.
While answering the question, I realized how long this process is. I will work on making the scripts available that I used so others can easily make these FASTAs, as well as provide FASTAs for commonly used organisms.
Let me know if you have any other questions.

oh! thanks.
shame they changed the format. I see that you can download the output tRNAscan-se, and there you have the bed file for the pre-tRNA (maybe, since I see introns there).
about the predicted anti-codon ... there i am little lost. sorry I can not help.
If you do the script it would be awesome, I can add that to cloudbiolinux, what we use to install tools and genomic data. I can easy implement you method there as a ggd-recipe (https://github.com/chapmanb/cloudbiolinux/tree/master/ggd-recipes) for each specie we can do.
thanks a lot for your time!!!!

also, i just saw the file mm10-tRNAs.ss.sort has all the information you need. needs more parsing than a fasta file though.


Jsx Yield / generator error

Firstly, It's possible that I've got something mis-configured but for the most part I am running a fresh install of VSCode.
I am running into an error on a .jsx file whenever I use a generator function like the one below. The yeild keyword always produces an error.

';' expected.ts(1005)

Is there something that I am missing?
The error occurs if it is the only file in my project. (not a .tsconfig / .jsconfig issue)
See a sample project at JeremyCarlsten/vsCodeSample
The sample project includes a file "my-settings.json" that contains my settings for vscode (also below)
{     "files.autoSave": "afterDelay",     "editor.suggest.filterGraceful": false,     "emmet.includeLanguages": {         "javascript": "javascriptreact"     } }

VSCode Version: 1.33.1
OS Version: Windows 10
Does this issue occur when all extensions are disabled?: Yes

I've got an Ubuntu Laptop at home. I should be able to check it tonight to see if it's an OS specific issue.

I feel dumb. yield was mis-spelled. Sorry!


Details about resampler/Q-former

Hello, thank you for sharing this impressive work as open source!
In your wiki section, I came across the statement "we use a Q-Former (16 tokens) to extract face features from CLIP image embeddings." Does the Q-former correspond to the resampler structure here? If so, it appears to be a modified Q-former without self-attention. Consequently, there may be no interaction among queries, correct?
I'm also curious about the PerceiverAttention line 63, where it seems that the key and value take both x and latent as input. I'm interested to know the reasoning behind designing a cross-attention like this.
Thank you in advance for your insights!

the keys and values of attention include self feature https://github.com/tencent-ailab/IP-Adapter/blob/main/ip_adapter/resampler.py#L63, hence, there is interaction among queries. You can think that we merge a self-attention and a cross-attention into a attention.


Fix for MSVC 2015, GNUInstallDirs, CPack support, CMake export target Coin::Coin

Original pull request by Markus Rickert (Bitbucket: rickertm, GitHub: rickertm).

This patch includes

Fix extra qualification error in SoHandleEventAction.cpp

Fix math-undefs.h for MSVC 2015

Use GNUInstallDirs variables

${CMAKE_INSTALL_LIBDIR} instead of lib etc. depending on platform

Add CPack and install components

Add Coin target version

Use TARGET_PDB_FILE:Coin for PDB installation in CMake >= 3.1

Add EXPORT target Coin::Coin and linking to simage::simage target

See also matching CMake pull request for simage project that defines simage::simage target

Original comment by Roy Walmsley (Bitbucket: walroy, GitHub: walroy).

Markus,
Thanks for this addition.
My first reaction is that this pull request consists of three disparate items:

The CMake changes being the major component.
The SoHandleEventAction.cpp fix
The math-undefs.h fix

These need to be handled separately.
the SoHandleEventAction.cpp fix needs to target the default branch. I agreed with your comment so I implemented this in my Windows application. All OK. So I committed a fix to the default branch and pushed it up. I'll sync this to the CMake branch. Please can you remove this item from this pull request.
Similarly, I need to look at the math-undefs. I'll let you know when I have done that.
That all said, a welcome contribution.
Roy

Original comment by Markus Rickert (Bitbucket: rickertm, GitHub: rickertm).

Hello Roy,
I agree that the SoHandleEventAction.cpp and math-undefs.h changes should go into default rather than only the CMake branch. I've merged my fork with your latest upstream sync. Let me know if I should do the same for math-undefs.h.
The main changes are the CMake ones. Together with those for simage, SoGui, and SoQt, this makes it much easier to build on MSVC.
Markus

Original comment by Thomas Moeller (Bitbucket: TheHubbit, GitHub: TheHubbit).

Hi Markus,
Your patch description doesn't cover the changes related to the simage library. From the changes it looks like the option for using the static simage library has been removed. Is that the case?
Thanks,
Thomas

Original comment by Markus Rickert (Bitbucket: rickertm, GitHub: rickertm).

Hi Thomas,
the simage patch was missing the flag for position-independent code (PIC) in case of a static build, I just added this.
If you build simage as a static library, Coin will find this version and link it accordingly. The SIMAGE_DLL and SIMAGE_NOT_DLL definitions are set accordingly as target_compile_definitions of simage::simage, together with target_include_directories and link dependencies such as gdiplus.
Markus

Original comment by Bastiaan Veelo (Bitbucket: veelo, GitHub: veelo).

See also pull request #255.

Original comment by Roy Walmsley (Bitbucket: walroy, GitHub: walroy).

This pull request is declined in favour of pull request #255.


Please release 1.0.3

I'm writing as a package maintainer for this repository in Debian and Ubuntu. Both distributions currently ship the most recent public release, which was released in November 2021.
These releases help as important syncronization point across all software packages in Linux software distributions so that consistent versions are being used. This is becoming increasingly and increadibly difficult as upstream such as buildah started to ship their own modified versions that cannot be found in the latest upstream release.
Newer upstream releases make my life significantly easier as then I don't have to disable features / revert commits that require newer fields.
Thank you for your consideration.

Could you give an example of this?

I don't have to disable features / revert commits that require newer fields.

Releasing without any changes seems a bit odd.

This raises the question about the ordering of releases. Frequently we like to be a lagging spec that sees some usage of a new feature before adding the standard, since that usage may reveal issues in the spec changes. That means that other projects will frequently have these newer features before a release, and often before a PR is approved. But the extensibility policy of the spec, to ignore unknown fields, means it should be safe for projects to do that experimentation without impacting a Linux distribution's ability to release that project.

@sajayantony gentle ping. Any chance to see a 1.0.3 release anytime soon?
thank you!

Are you downgrading dependencies in projects to only released versions

I wouldn't call it downgrading, but rather "unvendoring" and using "system-wide" copies of libraries to avoid the number of different version for each component.

we could probably work on a v1.0.3 release that includes everything up to that change.

That would be very helpful and exactly what I'm asking for. Thank you!


Fixed window size comparison being invalid when dictionary contains extra info

Getting window size from selenium driver returns:
{"width":1024,"hCode":4194304,"class":"org.openqa.selenium.Dimension","height":768}

Which compared to:
{"width": 1024, "height": 768}

Returns false.
This PR addresses this by instead directly comparing the height & width components without comparing other fields in  the dictionary (such as class / hCode).  This could be done in other ways as well but this was the least frictional.  This is certainly a defect that has prohibited us @ TE2 from capturing images using Robot-AppEyes on all browser except Chrome (who doesn't include the other information).

Nice catch! Thanks!

The fix is available as part of version 3.5 of eyes-selenium.


fix: allow cockroack to pull with docker creds

Changes

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#920  👈
#904
#903
#740 : 1 other dependent PR (#750 )
#759
#751
#755
#747
#743
#754
#741
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @AngelOnFira and the rest of your teammates on  Graphite


Marks 3rd party test library as private dependency

This change means that consumers of the BulletinBoard library using Carthage will no longer have to take the snapshot test case library as a direct dependency of their own project when using BulletinBoard. The snapshot test case library will still be available to library developers as normal. carthage update, carthage bootstrap, etc. will all still work without change.
More information here: https://github.com/Carthage/Carthage/blob/master/Documentation/Artifacts.md

Checklist

[x] I've tested my changes.
[x] I've read the Contribution Guidelines.
[x] I've updated the documentation if necessary.

Motivation and Context

My project uses Bulletin Board, and it is meant to be consumed by other projects as a framework. I don't want to make my users dependent on the snapshot test case library used in this project. By moving the dependency into the Cartfile.private file, this problem is solved.

This is super thoughtful, thanks! Do I need to do anything for the change to be taken into account (making a new release?)

For my project, I'm currently using my fork aaronbrethorst/BulletinBoard with the private-deps branch. I'm happy to keep using it for the time being, so don't worry about creating a new release for the time being. The next time you make a release, the change should cascade down to all Carthage users automatically.

Sorry, to actually answer your question: for this change to be made available to Carthage users, you will need to publish a new release. Technically, I think this may constitute a breaking change if people are using the implicit dependency on the snapshot test case library to pull it in to their own projects, so it may be worth holding back from a release for the time being.


Option to change which usecases can appear on the GraphQL layer

Description
This issue arose from the need for certain usecases not to be necessarily exposed in the graphQL layer, where only those with types query or mutation could appear.
Example
As the code demonstrates, only the usecase findAllUser would not be present in graphQL because its type has not been defined.
module.exports = [
    { usecase: require('./user/createUser'), tags: { group: 'Users', type: 'mutation'} },
    { usecase: require('./user/findOneUser'), tags: { group: 'Users', type: 'query'} },
    { usecase: require('./user/findAllUser'), tags: { group: 'Users'} }
]

Such an issue could cause only the desired usecases to be exposed to be used, making the application and documentation cleaner and more within the proposed business.

I believe we can implement it with a new validations in this file
for(const obj of usecases){
        if(!obj.tags.type ) continue
        if(obj.tags.type === 'read')
            UCqueries.push(obj.usecase(repositories))
        else
            UCmutations.push(obj.usecase(repositories))
    }

@PedroHaupenthal do you think you'll be working in this issue? If not, can I try to implement the suggested enhancement? Thanks! 😄


Cannot pass library secret into docker task build as an argument

Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name: Docker@2
Environment

Server - Azure Pipelines or TFS on-premises?

Azure Pipelines

Agent - Hosted or Private:

Hosted

Issue Description
code:
variables:
  - group: MyVariablesGroup
  - name:  version
    value: $(Build.BuildId)

trigger:
  - main

pool:
  vmImage: ubuntu-latest

stages:
  - stage: Build
    displayName: Build and push

    jobs:
    - job: Build
      displayName: Build job
      pool:
        vmImage: ubuntu-latest

      steps:
        - task: Docker@2
          displayName: Login to ACR
          inputs:
            command: login
            containerRegistry: MyACR

        - task: Docker@2
          displayName: 'Build'
          inputs:
            command: build
            containerRegistry: MyACR
            repository: function
            tags: |
              $(version)
            arguments: KEY=$(key)

What I'm trying to do is build a container while passing a secret variable from the pipeline library into docker as an argument, but the result I get back is:
/usr/bin/docker build -f /home/vsts/work/1/s/Dockerfile --label
[...] KEY=$(key) -t ***/function:10000 /home/vsts/work/1/s
"docker build" requires exactly 1 argument.
See 'docker build --help'.

Usage:  docker build [OPTIONS] PATH | URL | -

Build an image from a Dockerfile
##[error]"docker build" requires exactly 1 argument.
##[error]See 'docker build --help'.
##[error]Usage:  docker build [OPTIONS] PATH | URL | -
##[error]Build an image from a Dockerfile
##[error]The process '/usr/bin/docker' failed with exit code 1

I'd also like to point out that I've tried like twenty small variations in order to get the variable into docker, and the only one that didn't bonk the pipeline is passing arguments: --secret KEY=$(key), but then the variable is empty so it's not really an improvement.
Is there any solution or hacky fix for this issue?
Error logs
##[error]"docker build" requires exactly 1 argument.

So, not quite sure if that was it, but I found people saying that a double space in the arguments could at time cause this error. I didn't have double spaces in the arguments, but I suspect that having only one tag while declaring the tags after | is the equivalent of adding in a double space, because as soon as I put the tag on the same line as its declaration, the problem was solved.
Closing the issue.


restart must be a string

Docker Compose version v2.9.0-6413-g38f6acd gives the following error: services.create-bucket.restart must be a string

[x] I understand that contributing to this repository will require me to agree with the CLA

Description

What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[x] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings

Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 tech-docs
[x] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?

I have read the CLA Document and I hereby sign the CLA

@any contributor @dyumin tooling


meta: load into Redis cluster

close #1813

Codecov Report

Merging #1815 (23d1c44) into main (8efd06b) will decrease coverage by 0.12%.
The diff coverage is 18.18%.

@@            Coverage Diff             @@
##             main    #1815      +/-   ##
==========================================
- Coverage   62.03%   61.90%   -0.13%
==========================================
  Files         135      135
  Lines       22938    23019      +81
==========================================
+ Hits        14230    14251      +21
- Misses       7116     7175      +59
- Partials     1592     1593       +1

Impacted Files
Coverage Δ

pkg/meta/redis.go
73.06% <18.18%> (-0.53%)
:arrow_down:

pkg/fuse/context.go
56.75% <0.00%> (-10.82%)
:arrow_down:

pkg/chunk/cached_store.go
77.69% <0.00%> (-2.72%)
:arrow_down:

cmd/flags.go
94.02% <0.00%> (-1.46%)
:arrow_down:

pkg/object/swift.go
3.27% <0.00%> (-1.38%)
:arrow_down:

cmd/mount.go
67.09% <0.00%> (-0.87%)
:arrow_down:

cmd/format.go
60.12% <0.00%> (-0.78%)
:arrow_down:

pkg/object/tikv.go
76.00% <0.00%> (-0.12%)
:arrow_down:

pkg/meta/sql.go
66.94% <0.00%> (-0.12%)
:arrow_down:

... and 5 more

Continue to review full report at Codecov.

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


Fix glitch where you can bomb yourself at high stakes chest game to get on top of pyramid/castle.

Since this is not a vanilla glitch, it has to be fixed, as it wasn't intended.

Closing effectively duplicate PR.


Cannot select multiple WAF rule sets in the portal UI for Application Gateway

When configuring the Web Application Firewall in an Application Gateway, only a SINGLE rule set can be chosen on the 'Rules' tab. It's a standard dropdown list as opposed to a multi-select.
I'm confused as to how I would apply the Microsoft_BotManagerRuleSet 0.1 along with the OWASP 3.1 rule set. This doesn't seem possible in the portal UI.

Use with OWASP rulesets
You can use the Bot Protection ruleset alongside any of the OWASP rulesets (2.2.9, 3.0, and 3.1). Only one OWASP ruleset can be used at any given time. The bot protection ruleset contains an additional rule that appears in its own ruleset. It's titled Microsoft_BotManagerRuleSet_0.1, and you can enable or disable it like the other OWASP rules.
[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 5c72c5ad-955d-57b9-25dd-fdebdf475f50
Version Independent ID: 6c07e7c7-4ee4-c7a1-1735-1302e9187a9e
Content: WAF on Azure Application Gateway bot protection overview - Azure Web Application Firewall
Content Source: articles/web-application-firewall/ag/bot-protection-overview.md
Service: web-application-firewall
GitHub Login: @winthrop28
Microsoft Alias: victorh

@andyblack19, thank you for your question. We will investigate and update the thread shortly.

@andyblack19 , the link for the steps on how to configure bot protection for WAF on Azure Application gateway is provided at the end of this article as next steps.

You need to first create a basic WAF policy for Application Gateway by following the instructions described in Create Web Application Firewall policies for Application Gateway.
Post that you can enable bot protection rule set as described in https://docs.microsoft.com/en-us/azure/web-application-firewall/ag/bot-protection
And then you can associate the WAF policy with an existing Application Gateway following the below article: https://docs.microsoft.com/en-us/azure/web-application-firewall/ag/associate-waf-policy-existing-gateway
We are closing this issue for now. If there are further questions regarding this matter, please reply and we will gladly continue the discussion.


Add thiserror

Use thiserror crate for all error reporting (more errors will be needed)
errors are rarely comparable - use matches! instead

Thanks for this. Just a couple of comments.
Could you remove the justfile? It's not linked to the rest of the PR and I feel like it implies an external dependency that doesn't exist.
I also wonder about simplifying the names SpreetError and SpreetResult to plain old Error and Result. This is how std::io does it, and they can always be imported with the Spreet prefix if needed. I think I'd prefer the unprefixed names but that's not a strongly-held opinion. What would your preference be?
Other than that, I'm happy to merge this.

The Error renaming has recently became a big thing because too many projects use it, and it has gotten highly confusing. I am sure if io::Error was implemented today, they would have chosen a different one, but we are stuck with it now :).  See the new clippy lint.
I can remove the justfile, but I would highly recommend adding it as an optional useful tool for those who wants it. I have been using it in a large number of projects, e.g. sqlite-hashes, and together with cargo-husky they make a very easy to use system - pre-push git hook to make sure the code is good even before publishing it,  CI runs the same steps as the users, users never need to know any custom flags for cargo to test things, etc.

The Error renaming has recently became a big thing because too many projects use it, and it has gotten highly confusing. I am sure if io::Error was implemented today, they would have chosen a different one, but we are stuck with it now

Ah, OK, that's good to know. Let's keep the Spreet prefix then


[Excel] (Custom Functions) Removing volatile functions

OPS Build status updates of commit fa02083:
:clock10: Pending: waiting for processors (6 builds ahead of you)
:warning: OPS Build is busy, click here to report any potential performance downgrade issues, or you could view OPS Portal for trend of build queue length.

OPS Build status updates of commit fa02083:
:clock10: Preparing: average preparing time is 45 sec(s)

OPS Build status updates of commit fa02083:
:clock10: Incremental building: average incremental building time is 28 sec(s)

OPS Build status updates of commit fa02083:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/excel/custom-functions-overview.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Test for the Containerfile does not attempt to use skstat/skmanage, misses issues with Proton Python install

$ docker run --name router -itd --rm quay.io/skupper/skupper-router:main
196e2784d48f4e597cf0057e9daca88d6a88c375d75f62fb98959e935308b6db
$ docker exec router skstat -l
Traceback (most recent call last):
  File "/usr/bin/skstat", line 29, in <module>
    from skupper_router.management.client import Node
  File "/usr/lib/python3.9/site-packages/skupper_router/management/client.py", line 22, in <module>
    import proton
ModuleNotFoundError: No module named 'proton'

Reported by @fgiorgetti

@jiridanek this issue seems to have been fixed by you already. Close this issue ?

@ganeshmurthy The job still does not check that skstat/skmanage run, so there is more work to do. (They do run now, but it is not tested there.)

One additional problem; the test does not wait for router to start and open port, so if it starts slowly, test fails. This is also something to be solved here.
See HEALTHCHECK Containerfile instruction, https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/building_running_and_managing_containers/assembly_monitoring-containers_building-running-and-managing-containers#performing-a-health-check-using-a-containerfile_assembly_monitoring-containers
Healthcheck feature is present in the router, https://github.com/skupperproject/skupper-router/commit/1e22255eede6f82828a433839cb25087c2c7b300 hopefully it does what I need it to do (claim Healthy only when all listeners declared in config were opened).


line breaks in tables

Hi
I'm trying to include line breaks in table cells () to make them multi-line. I've tried adding , ,  tags, but they just end up being rendered as text.
Using "n" and "r" kinda works when inspecting table using browser developer tools - I can see that both text and html code is breaking my text correctly, but it is still being rendered in one long line in table.
I have tried adding -Wordbreak to Table and -NewLine to TableOption cmdlets, but they had no effect.
Thanks

If you want to play with Html in the tables you need to use InvokeHTMLTags switch. Otherwise, it treats HTML tags as text.
Natively you can do it using the proper new line PowerShell way.
$Array = @(
    [PSCustomObject] @{
        Test  = "Multiline" + [System.Environment]::NewLine + "Text"
        Test2 = "Multiline" + [System.Environment]::NewLine + "Text"
        Test3 = "Multiline" + [System.Environment]::NewLine + "Text"
    }
    [PSCustomObject] @{
        Test  = "Multiline" + [System.Environment]::NewLine + "Text"
        Test2 = "Multiline" + [System.Environment]::NewLine + "Text"
        Test3 = "Multiline" + [System.Environment]::NewLine + "Text"
    }
)
$Array | Out-HtmlView

Thank you so much, it works great @PrzemyslawKlys
Here's what I ended up using:
@("One", "Two", "Three") -join [System.Environment]::NewLine


Core tests : Block

you need to remove the "do not merge" tag, and also rebase the branch against master.


Fix relative top positioning

Fixes #181

You're amazing for fixing it, but i dont see why he isn't merging it..


Gradle not Respecting Ivy Standard Version Requirement

In my build.gradle file:
compile 'com.android.support:support-v4:[10.0.0,26.0.0['
compile 'com.android.support:appcompat-v7:[10.0.0,26.0.0['

Running gradle dependencies, shows:
sourcesReleaseCompile - Classpath for compiling the sourcesRelease sources.
+--- project :MyProject
|    +--- com.android.support:support-v4:[10.0.0,26.0.0[ -> 26.0.0-alpha1
[...]
|    \--- com.android.support:appcompat-v7:[10.0.0,26.0.0[ -> 26.0.0-alpha1

I want to avoid including 26.0.0-alpha1... Why isn't gradle respecting ivy standard notation here?
Expected Behavior
Resolves to latest v25.
com.android.support:support-v4:[10.0.0,26.0.0[ -> 25.x.x
Current Behavior
Resolves to latest v26.
com.android.support:support-v4:[10.0.0,26.0.0[ -> 26.0.0-alpha1
Context
I was under the impression Gradle honors Ivy standard for dependency resolution. Ivy Standard: http://ant.apache.org/ivy/history/latest-milestone/settings/version-matchers.html
Steps to Reproduce (for bugs)
Test project: https://github.com/benmarten/gradle-dependency-test
Your Environment
macOS latest, gradle via brew latest as of writing.

I think the problem is that we are considering that 26.0.0-alpha1 < 26.0.0 when we order the versions, so that 26.0.0-alpha1 does indeed fall into the version range.
Can you please try with [10.0.0,26[ and see if you get the same result?

Gradle honours a version range in a literal way. We treat versions as ordered, and then we decide if a version fits within a range based on whether it is higher or lower than the bounds of the range.
Given versions 26.1 and 26.1-alpha1, Gradle decides that 26.1-alpha1 comes before (is less than) 26.1. Then the range [1.0, 26.1[ is interpreted as 1.0 <= X < 26.1.  Note that this range would not (and should not) include 1.0-alpha1.
Unfortunately there's no easy way to address this. One option is to make the bounds of a version range "smarter", so that '1.0-alpha1is excluded from _both_[0, 1.0)` and `[1.0, 2.0)`. A better option is probably to provide a mechanism to say "pre-release versions are OK" for a version range, and to omit pre-release versions (alpha, beta, SNAPSHOT, etc) by default.
Note there is a similar problem where [1.0, 2.0) will include 2.0-SNAPSHOT, even though this isn't what most people want, most of the time.
As a workaround, the desired behaviour can be achieved by using [10.0.0, 26[ as the version range.

+1 to this:

provide a mechanism to say "pre-release versions are OK" for a version range

There was a discussion at https://discuss.gradle.org/t/how-to-get-latest-release-version-in-an-range/5814.
resolutionStrategy and some other features were implemented still then.
But they are very burdensome to use if you want to specify status for single dependency.
It would be more convenient to have this syntax like this:
dependencies {
  compile group: 'com.android.support', name: 'support-v4', version '[10.0.0, 26.0.0[', status: 'integration' // or 'release', or 'milestone' if it is from Ivy repo
  compile 'com.android.support:appcompat-v7:[10.0.0,26.0.0[' // 'release' by default
}


Update Travis to run tests on a Linux build

Hopes and dreams will have to wait for now. Consider reopening in the future.


TypeError: e.path is undefined in Firefox

In latest firefox console generating error TypeError: e.path is undefined on clicking to any point in document.
$('.flatpickr').flatpickr({
    time_24hr: true,
    enableTime: true
});

Open console in latest firefox on this site and clicking on document

@rorc This regression was introduced in #510. I started some discussion there, but this is probably a better place.

I opened a PR here: https://github.com/chmln/flatpickr/pull/521


i am put index.d.ts to project of react-native root directory, but notice is not found file of  type declare

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

i am install with "yarn add react-native-cardview"
i am cofigure the react-native-cardview completely in accordance with official document
i am mkdir directory typing in project of react-native and put official index.d.ts in it;
Expected behavior
A clear and concise description of what you expected to happen.
but visual code is still notice not found type declare file;
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):

Device: [e.g. iPhone6]  android api 28
OS: [e.g. iOS8.1] android api 28
Browser [e.g. stock browser, safari]
Version [e.g. 22] latest version  of react-native

Additional context
Add any other context about the problem here.

Can you please create PR? I will look into it?

is ok,
beause i configured android/setings.gradle, android/app/build.gradle, the above error occurs
latest version for react-native is does't need to configured


Render Viewer: Code clipboard button overlapped by markdown TOC trigger area.

Describe the bug:

This issue caused the cursor to be unable to click the code clipboard button.
It happened when the tools > options > appearance > editor maximum width was set to 0.

Screenshots:

This issue also affects the code block and art gallery scrollbar.

The issues have been fixed by the ReMoods v4.3.1.


Improve "place in" box on dev place pages

1) Fix long list of child places on continent place pages
On continent place pages, the list of child places will contain places that are more than one level down in containment (e.g, showing municipalities, not just countries).
Before:

After:

2) Add a "show more" toggle when the list of child places is long
Sometimes the list of child places is very long, which overwhelms the page. This PR also adds a "show more" toggle when the number of child places is greater than 15.
Long lists are truncated initially

Show full list after clicking "show more"

Short lists don't show a toggle

Just from the screenshots -- looks like we are returning Yugoslavia. We should be filtering "deprecated" countries..

Just from the screenshots -- looks like we are returning Yugoslavia. We should be filtering "deprecated" countries..

Agreed-this is already on our task list


Wager a simple bet with caps.

We need basic wagering for a complete and playable game of blackjack.

Yea, just a messagebox for now. Issue #6 has morphed into the fully featured wagering.

Simple betting is completed. The message is as follows.


Typo

There are two typos in the third codeblock. It should be Northwind instead of Northwnd

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a2448ac4-a6d0-e376-36fe-c6279fd606c8
Version Independent ID: 50f1aa4e-8e0e-2bee-db10-9c65c11b4028
Content: How to: Connect to a Database
Content Source: docs/framework/data/adonet/sql/linq/how-to-connect-to-a-database.md
Service: unspecified
Product: dotnet-framework
GitHub Login: @douglaslMS
Microsoft Alias: douglasl

#in-progress

@mairaw Can you help me to locate the separate code snippet files in which these typos are found? I can't find them in the "docs" folder structure.

@douglaslMS Every code snippet whose path starts with "/samples" is in the dotnet/samples repo.


I can not find floonet coins, very high difficulty

The testnet is very scarce, I can not find or mine, I think we need to change the difficulty setting of the testnet as it was done in Bitcoin's Testnet3.
I think that abundant testnet coins are important for development and learning, even more in a new innovative protocol such as grin.

Thanks to Photon, you can ask for some free test Grin coins simply by running this command on your node.
	curl gringod.info
	grin wallet info

<EMAIL_ADDRESS>


fix(text-input): uses search icon

📥 Proposed changes
uses search icon and moves the menu list above help text
☑ Submission checklist

[x] I have read the CONTRIBUTING doc
[x] yarn build works locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)

@all-contributors please add @Mikaila94 for code


Plans for openapi-schema-validator 0.4 support?

Since openapi-schema-validator is now at 0.4.0, are you planning to keep the dependency pinned to ^0.3.0 here and in openapi-spec-validator for some time, or are you planning an updated release that supports the current version of openapi-schema-validator?
https://github.com/p1c2u/openapi-core/blob/6d8f1d962ec61bc077fcd8113d695100fc49dd6f/pyproject.toml#L62

Hi @musicinmybrain  yes, there's no reason to keep it pinned to 0.3.x. Thanks for pointing this out.

Thanks for looking at this!


Code CleanUp

To clean up the code to increase the readability

@nishkarsh800
What you will do under this issue ?
which file will be modified ?

Under this issue I'll reformat the code

@nishkarsh800 You are assigned this issue.
Stay focused while working on because small mistake can cause big problem.
i will decide issue level after seeing your work.

I'm a GSSoC contributor ..
I would like to work on this section...
would you please assign me to this task ??

Are you working on it ? @nishkarsh800

Yes I'm working


Added dict.cc

Account data will be deleted. However, the user name will be blocked to prevent reuse. Hence, I chose "easy" severity. If you dissent, please amend.

Thanks for your contribution!


UniqueValidator on combinations problems

Let say a model has three attributes a1, a2, a3 which can be empty. Lets say all three must constitute a unique combination. Lets say model validators are configured as follows:
['a1', 'makeSureIsValidIfNotEmpty'],
['a2', 'makeSureIsValidIfNotEmpty'],
['a3', 'makeSureIsValidIfNotEmpty'],
[['a1', 'a2', 'a3'], 'unique', 'targetAttribute' => ['a1', 'a2', 'a3']],

Problem 1. When a1, a2, a3 have valid non-empty values UniqueValidator will perform the same validation THREE times. This is completely unnecessary and undesirable considering the validation involves quering the database.
Problem 2. When a1 is valid and non-empty, but a2 is empty and a3 is invalid UniqueValidator will perform validation once (on a1) but using EMPTY value of a2 and INVALID value of a3. This is simply pointless and wrong.
I am not sure how this can be fixed considering the overall design of Yii2 data validation, but the problems are bad. In its current state UniqueValidator is good enough for single attribute validation only.

I think I figured an acceptable (and backwards compatible) solution for most of the problems:
https://github.com/yiisoft/yii2/compare/master...PowerGamer1:patch-12
The validation will still be performed when some of the attributes are empty (which may be needed in some cases).


DROOLS-733 - add jms/ejb support ofr timers and executors for jBPM to…

… properly run on WAS and WLS with background threads

merged into master and 6.3.x


Use the MIRA DKG API to ground model variables & parameters to concepts during Model Card generation

DKG = Domain Knowledge Graph
The task is to ground model variables & parameters to concepts in the DKG if they are missing from the input AMR or plainly wrong according to the input document.
These groundings would be later used with the entity_similarity endpoint to automatically map model quantities to dataset features (as in the Calibrate workflow box).
The API is here:
http://<IP_ADDRESS>:8771/
http://<IP_ADDRESS>:8771/docs

duplicate. not possible due to no parameter groundings present in DKG. Only some state variables have groundings.


Support for include parameter on relationship routes

According to http://jsonapi.org/format/#fetching-includes:

Furthermore, related resources can be requested from a relationship endpoint:
GET /articles/1/relationships/comments?include=comments.author HTTP/1.1
Accept: application/vnd.api+json
In this case, the primary data would be a collection of resource identifier objects that represent linkage to comments for an article, while the full comments and comment authors would be returned as included data.

e.g. Calling /api/v1/matter/1/relationships/contacts?include=address returns a list of resource stubs, without relations or attributes.
Setting $includePaths, $allowedIncludePaths, getIncludePaths() has no effect. getRelationships() seems to be never invoked on the related resource.
Does anyone have an idea how to solve this inclusion problem?

returns a list of resource stubs, without relations or attributes.

That's correct, matter/1/relationships/contact will always return resource identifiers - i.e. just the type and id, no attributes or relationships.
If you want the matter attributes and/or relationships, use matter/1/contact. That does support include paths.
Does that answer the question, or do you want resource identifiers with include paths?

Hi @k8n . If you want your resources to be automatically included without passing the 'include' parameter, you can use getRelationships() in your Schema.php in the following way:
    public function getIncludePaths()
    {
        return [
            'matter.contacts.address'
        ];
    }

I'm assuming that matter, contacts and address are your individual resources/models. Does that help answer your question?

Thank you, gentlemen. Those are good pointers.
@lindyhopchris, I was wondering about that route and it’s purpose!

For people who are missing the include support on relationship routes, there's an open ticket in the parent library @see https://github.com/neomerx/json-api/issues/218
Of what I understood however (by reading some discussions between Chris and neomerx), it will probably take some time before laravel-json-api will switch to v3, as v3 would break quite a bit of our schemas etc.

@Ciaro yeah unfortunately v3 breaks our entire approach. We'll need to make a decision on whether we hack it to use it, or completely remove the neomerx/json-api dependency. Unfortunately both approaches are extremely time consuming, so not sure when we'll be able to move it forward. We'll probably upgrade to v2 of the neomerx package as an interim step.

I am also looking for this feature. Is there some news about it ? In the JSON:API documentation it's a "MAY" feature but it would be useful in some of my projects using laravel-json-api.


Route chaining

Allow chaining of routes, like so:
@get("/")
@query("hello", str)
async def something(hello: str):
    ...

@something.post
@body("a", str)
async def something(hello: str, a: str):
    ...

I would like to work on this project is there any community to discuss?

Not yet, we're using just issues as of now. Would something like a discord server be helpful?

Yes discord server would be helpful, your project concept is awesome

Ok, will set one up later today, let me know if you have any other questions.

Discord up and running: https://discord.gg/tZAfuWAbm2


conrod0.76 glium0.30 winit0.25

I believe I somehow managed to do this migration (finally!).

I add to remove the CPU consumption reading from the example because the psutil crate uses a yanked version of the platforms crate
There seems to be a small glitch left in the example app: sometimes the first data point seems to disappear for a few seconds.

Blockers:

[ ] wait until my changes are in a conrod release (currently using a fork) PistonDevelopers/conrod#1443

Thanks! LMK when its ready.

Merge is blocking for now, as I cannot push to Crates.io a Cargo.toml containing Git dependencies. Will do whenever upstream has merged & published all your PRs.


fix: PXE devnet connectivity

Turn on retries for PXE client talking to Aztec node
turn on pxe_ namespacing by default when running PXE outside of the aztec binary context

Benchmark results
Metrics with a significant change:

note_trial_decrypting_time_in_ms (32): 78.6 (+100%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit 13752339 and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
54,212
214,436
855,332

l1_rollup_calldata_gas
259,892
1,019,768
4,059,956

l1_rollup_execution_gas
354,078
1,139,216
4,281,357

l2_block_processing_time_in_ms
1,277
4,815 (+1%)
19,191 (+1%)

note_successful_decrypting_time_in_ms
214 (-2%)
637 (+6%)
2,279 (+6%)

note_trial_decrypting_time_in_ms
23.7 (-15%)
:warning: 78.6 (+100%)
196 (+5%)

l2_block_building_time_in_ms
21,348
84,769
344,459

l2_block_rollup_simulation_time_in_ms
15,976
63,536
259,727

l2_block_public_tx_process_time_in_ms
5,344 (+1%)
21,154 (+1%)
84,475 (+1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
15,001 (-11%)
32,117

note_history_successful_decrypting_time_in_ms
1,411
2,749 (+1%)

note_history_trial_decrypting_time_in_ms
208 (+28%)
226

node_database_size_in_bytes
18,681,936
35,737,680 (-1%)

pxe_database_size_in_bytes
29,923
59,478

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
335
44,664
27,457

private-kernel-ordering
214
45,777
14,627

base-rollup
1,742
175,344
933

root-rollup
83.5 (+1%)
4,192
825

private-kernel-inner
443
73,099
27,457

public-kernel-app-logic
275
32,254
25,379

merge-rollup
7.90 (+2%)
2,712
933

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
15,388
36,001

Transaction processing duration by data writes.

Metric
0 new note hashes
1 new note hashes

tx_pxe_processing_time_ms
578 (+1%)
1,508 (+1%)

Metric
0 public data writes
1 public data writes

tx_sequencer_processing_time_ms
0.0315 (+8%)
655


Incorrectly formatted .zprintrc file ignored

In the cases where a ~/.zprintrc file (or ~/.zprint.edn file) is incorrectly formatted such that the Clojure reader will throw an exception, the file is ignored instead of causing an exception in zprint.

Fixed in 0.5.4.  Forgot to put this in the CHANGELOG.md.


Implemented missing PING and PONG messages described in https://github.com/enisdenjo/graphql-ws/blob/master/PROTOCOL.md#ping

This PR implements the missing PING and PONG GraphQL WS messages for the client-side "heartbeat / keep alive" function.
Now the system does not close the connection when it receives a PING message, but sends a corresponding (PONG) message back, as specified in the graphql-ws protocol.

@ExidCuter Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@ExidCuter Thank you for signing the Contributor License Agreement!

Hi, I'm not quite sure I understand your comment. Do you mean I should remove handleWebSocketPing and handleWebSocketPong from the WebGraphQlHandler interface and just respond directly with Mono?
I added methods to WebGraphQlHandler because the PING and PONG messages are GraphQL-WS message types and I thought they should be implemented the same way as the others.

Yes, I meant that those methods should be removed from WebGraphQlHandler. They don't serve any purpose and they don't help to handle PING messages. For now we would automatically handle those.

@rstoyanchev

Does server automatically reply to PING messages sent from the client?
Can server send PING messages to the client periodically? Is there any configuration property for this?

Yes the server replies automatically. There isn't a way to send pings.


Dapr does not show tracing in zipkin

Describe the bug
I'm using dapr with .net on my local and set to use zipkin but it doesn't show the trace
end-to-end communication works fine, it returns and receives the data, but the trace is not shown
CLI version: 1.9.1
Runtime version: 1.9.5
.Net 6 / Dapr.Client
Steps to reproduce
Steps to reproduce the behavior:

click on the "show" button
page empty

Screenshots
nuget:

docker

Desktop (please complete the following information):

OS: Windows
Browser  chrome , Edge

@msfussell please migrate this to runtime


Raises Exception when there's whitespace around (loot filter) urls

[2019-03-28 09:12:41] - pypod_launcher.launcher - ERROR - critical on <function Launcher.generate_loot_filter at 0x7f39fee3d268>
Traceback (most recent call last):
[...]
FileNotFoundError: [Errno 2] No such file or directory: ' https:/raw.githubusercontent.com/KarmaNation256/pod-loot-filter/master/item.filter'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
[...]
    raise InvalidURL(url)
aiohttp.client_exceptions.InvalidURL: %20https://raw.githubusercontent.com/KarmaNation256/pod-loot-filter/master/item.filter

Thanks for report. Will fix ASAP.

New release will be rolled in 24 hours.


[DO NOT MERGE] Monitor compile cache utilization

Check if cache is being utilized in jenkins and windows CI

Jenkins, test this please

Jenkins CI test (for commit 106b9caa370206faddc3d4bd6fa083d311cd8d9f, target branch master) failed with status FAILURE.

The cache hit in Windows is surprisingly low...I wonder why? Could it be the hash on Windows is not deterministic?
Jenkins reported failure, but the GitHub UI does not show a link. @kmaehashi maybe this also relates to the GitHub API fix?

Cache stats for windows,
Runtime Statistics
==================
Compile Cache hits 5002
Compile Cache misses 34942
Compile Cache hit ratio 0.13

I also suspect that the hashing in windows has something to do with this, or that we are unpacking the saved cache in the wrong folder.

I checked a cache key. https://github.com/cupy/cupy/blob/v9.0.0b3/cupy/cuda/compiler.py#L479 and noticed that the key includes the full path to the CuPy's source tree.
('70', ('-IC:\\Users\\chainer\\cupy\\cupy\\core\\include', '-IC:\\Users\\chainer\\cupy\\cupy\\core\\include\\cupy\\_cuda\\cuda-10.0', '-IC:\\Program Files\\NVIDIA GPU Computing Toolkit\\CUDA\\v10.0\\include', '-ftz=true'), (10, 0), 'nvrtc') b'//\n// Generated by NVIDIA NVVM Compiler\n//\n// Compiler Build ID: CL-24817639\n// Cuda compilation tools, release 10.0, V10.0.130\n// Based on LLVM 3.4svn\n//\n\n.version 6.3\n.target sm_70\n.address_size 64\n\n\n\n' #include <cupy/complex.cuh>

The problem is that FlexCI checkouts the git repo to a different path for every launch because it includes a execution ID, e.g., C:\Windows\TEMP\flexci\run-00145123\work\src.

I think we can workaround this by pip installing it (ie avoid using pip install -e)

Windows kernel cache issue is resolved via #4970. This helped a lot diagnosing the issue, thanks!


Fix Step 06

Per Eric: Model year and certification will be mandatory in the future.
We need to update the Step to reflect what Eric really wants there.

When it's mandatory, the requirements will change and the code can be adjust then.


Handling VB .NET projects

This is a question, not a bug report although it may be a docup.
We are evaluating options for porting a solution having 20 projects; 11 C# and 9 VB.  Project types include command line, class libraries, ASP.NET, Windows Forms with dataset bindings, and OleDB.
I picked a VB project having no dependencies other than .NET, and ran this command:
upgrade-assistant MyVBapp.vbproj
This is what I received:
Unhandled exception: System.InvalidOperationException: Cannot open project 'D:\Temp\afolder\MyVBapp.vbproj' because the language 'Visual Basic' is not supported.
Perhaps this exception should be handled and a message issued, rather than dumping the stack trace.  In addition, when running the command against the solution, the tool is silently skipping VB projects in Step 1.  It would be helpful to see warnings when that occurs.
Obviously the version I am running does not support VB.   Here are the releases:
try-convert            0.7.212201      try-convert
upgrade-assistant      0.2.212505      upgrade-assistant

There are two possibilities.  I am:

running the an old version where VB is not supported

or...running the latest preview version and VB is still not supported.

In any event, it would be good to find this restriction in the documentation.  Perhaps I missed it.
Should we wait for the tooling to mature?  We're willing to proceed. However we are hoping this tool will reduce our LOE and increase the chances the project will get funded.

Thanks for the report @bigtfromaz. As you've discovered, we don't have support for VB yet. It's on our roadmap, but the tool is just in its early stages and I'm afraid it only supports C# projects, so far.
You're right, though, that the error message can be better in the case where a user runs the tool on a vbproj. Lets use this issue to track making that messaging better and I'll open a separate issue to track implementing support for VB projects.

Let's see if we can get a VB integration project (maybe just a console app right now), and ensure everything but code analyzers will work. Probably just need to bring in the roslyn VB support for that via Microsoft.CodeAnalysis

Sounds good.

Thanks for the report @bigtfromaz. We've modified the approach to start our journey toward supporting Visual Basic .NET projects.
Please note that this is still the beginning of our journey and we're continuing to evolve the upgrade process. While the recent PR adds support to process VB project files (console apps, win forms apps, and class libraries) we found some limitations with try-convert that prevent us from helping with VIsual Basic WPF projects.
Here's a link to the related issue so that you may track that if it impacts your scenario.
#384 Add support for Visual Basic WPF projects
And, a link to another issue we opened to enhance the support for Visual Basic ASP.NET apps
#310
Thanks for your feedback!


Interrupting k3os-upgrade-kernel script breaks server kernel

Version (k3OS / kernel)
0.10.0 but other versions are likely affected as well
Architecture
x86_64
Describe the bug
It is possible to break K3OS server by first triggering kernel upgrade and next interrupting download process before it completed. This destructive behaviour is only possible in scenario when server already uses most up-to-date version of the kernel. Other cases seems to be safe because download is carried out to new location which is linked as current only when download finished successfully.
To Reproduce

Install fresh installation of K3OS 0.10.0
Run /share/rancher/k3os/scripts/k3os-upgrade-kernel script
Interrupt script after Upgrading k3os kernel to ${KERNEL_VERSION} is printed
Restart OS

Expected behavior
Script should compare available version online with version already installed and do not perform update when kernel is already installed.
Actual behavior
Script optimistically redirects kernel that is being downloaded to ${KERNEL_VERSION}/initrd which is linked as current. In case download is interrupted ${KERNEL_VERSION}/initrd will contain interrupted content which in turn will cause kernel panic upon restart.
Additional context
None

The upgrade scripts were deprecated in version 0.9.0 in favour of the upgrade controller. I don't believe Rancher will spend time fixing this, but as I was part of writing the upgrade scripts I would be willing to review any changes to the scripts and maybe @dweomer would consider merging those fixes.

@geek-soft as @zimme says, these scripts have been deprecated (since v0.9.0 or shortly thereafter) and are therefore not supported.


Camera tracking

A python application that connects to a webcam to track the current positions of all the robots and reports back to stdout using the format: id|x|y|r|id|x|y|r|... for all the tracker symbols fond in the picture.
X and Y use the game coordinate of 16 and 9.
Messages sent to stderr will be piped to the robot runner cli.

No longer relevant.


Monitoring sync jobs

created a health-check endpoint and deployed to green. will evaluate for a couple of days.

added to healthcheck