Update tensorflow-swift-bindings to one with virtualized interface

This PR also updates the CMakeLists.txt to explicitly list the files in tensorflow/swift-bindings.

@swift-ci please clean test tensorflow

Unfortunately, the use of opaque result types in https://github.com/tensorflow/swift-bindings/commit/f217f40dab006c7de57f64cc3e0cbff86794bff9 causes compilation to fail macOS:
/Users/danielzheng/swift-dev/tensorflow-swift-bindings/RawOpsGenerated.swift:20:49: error: 'some' return types are only available in macOS 9999.0.0 or newer
func makeOp(_ name: String, _ nOutputs: Int) -> some TFTensorOperation {
                                                ^
/Users/danielzheng/swift-dev/tensorflow-swift-bindings/RawOpsGenerated.swift:20:6: note: add @available attribute to enclosing global function
func makeOp(_ name: String, _ nOutputs: Int) -> some TFTensorOperation {
     ^
/Users/danielzheng/swift-dev/tensorflow-swift-bindings/TFTensorOperation.swift:5:65: error: 'some' return types are only available in macOS 9999.0.0 or newer
  public static func makeOp(_ name: String, _ nOutputs: Int) -> some TFTensorOperation {
                                                                ^
/Users/danielzheng/swift-dev/tensorflow-swift-bindings/TFTensorOperation.swift:5:22: note: add @available attribute to enclosing static method
  public static func makeOp(_ name: String, _ nOutputs: Int) -> some TFTensorOperation {
                     ^
/Users/danielzheng/swift-dev/tensorflow-swift-bindings/TFTensorOperation.swift:1:1: note: add @available attribute to enclosing extension
extension _ExecutionContext {
^

I'll revert this PR to unblock progress. I'm happy to test future swift-bindings patches on macOS locally while macOS CI is down.

@dan-zheng that is a bummer. Let me see if I can avoid the opaque result types.


Removed testProperty calls introduced by #2908

This PR removes all Hedgehog deprecation warnings. I used lowercase with hyphens for short test names.
closes #2910

Duplicate of #2924


Bug fix 3.4/fix array sorting

first commit in this PR is unrelated to the problem, just an optimization for which I was too lazy to create a separate PR

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/1665/


#HTML

#HTML
##USER STORY
As a boot camp student
I want the prework notes to be structured on a webpage
So that I can easily find and read the information
##ACCEPTANCE CRITERIA
GIVEN a Prework Study Guide website
WHEN I visit the website in my browser
THEN I see four boxes titled HTML, CSS, Git and JavaScript with associated notes listed

added to main

added


Added a function for tracking request result on additional keys, after successful fetch…

PR Checklist
Please check if your PR fulfills the following requirements:

[ ] The commit message follows our guidelines: https://github.com/ngneat/elf/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[X] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Possible to use new method for tracking request result on additional keys.
Does this PR introduce a breaking change?
[ ] Yes
[X] No

Other information

One last thing, your commits are not based on our guidelines. Please squash your commits and use npm run c

One last thing, your commits are not based on our guidelines. Please squash your commits and use npm run c

Commits squashed, but unable to run git-gz, does not find git whatever I do, not on Windows and not in WSL.

Squashed commits and npm run c used to create proper commit.

Tests failed

Tests failed

Fixed!

@NetanelBasal anything else stopping the PR acceptance? When can we expect a release including this?


Escape brackets/periods/backslashes/quotes in input data

Apparently vega treats these specially. See this page for context.
This is causing a problem with the rank names in the Byrd data example -- trying to switch to a rank that isn't "Intercept" brings up an error.
I guess we have to apply this not only for each column but for every possible string that's passed to Vega: so every feature/sample ID, augmented feature ID, sample metadata, and probably more. sheesh.
ideally we should have tests that verify that our measures to protect against Vega interpreting things wrongly work (#2).

So I think that due to our use of json.dump(), we shouldn't have to worry about most of these aside from the Vega-Lite-specific ones (periods and brackets). But again, it's still a good idea to be sure.

If we want to be 100% safe, we'll need to escape all of the following:

Rank IDs
Feature IDs
Sample IDs
Sample Metadata IDs
Feature Metadata IDs

ahsdfiusdoifjsdfioj
so it looks like even if you escape a rank ID properly for the axis stuff, you still need to use the non-escaped ID in the underlying dataset???? bluhg

@mortonjt small question: is preserving the patsy formulas in rank IDs (e.g. C(Timepoint, Treatment('F'))[T.B] in the Byrd data) helpful when looking at the ranks? It looks like periods, brackets, and quotes all cause problems when you pass them into Vega-Lite as field IDs.
I've implemented a basic solution that converts periods to colons and square brackets to parentheses (along with filtering out quotes and backslashes). This takes care of the problem for now, but if you think it's worth it I can come back to this later (probably after exams are over) and add back in support for some of these weird characters.

note to self: if we go with the solution of filtering out/converting certain special characters in IDs, ensure that they're still unique afterwards.

The special characters don't matter, but the covariates (I. E. Timepoint),
treatment (I. E. F) and control (I. E. B) are all important.
On Wed, Mar 6, 2019, 11:57 PM Marcus Fedarko<EMAIL_ADDRESS>wrote:

@mortonjt https://github.com/mortonjt small question: is preserving the
patsy formulas in rank IDs (e.g. C(Timepoint, Treatment('F'))[T.B] in the
Byrd data) helpful when looking at the ranks? It looks like periods,
brackets, and quotes all cause problems when you pass them into Vega-Lite
as field Is.
I've implemented a basic solution that converts periods to colons and
square brackets to parentheses (along with filtering out quotes and
backslashes). This takes care of the problem for now, but if you think it's
worth it I can come back to this later (probably after exams are over) and
add back in support for some of these weird characters.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fedarko/rankratioviz/issues/66#issuecomment-470384925,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD_a3QJSySl-eYD10nc7cWe7jmrgicejks5vUJw2gaJpZM4bYQGx
.


Automator: update istio/api@master dependency in istio/istio@master

Generated by Automator - 2020-02-18T01:32:00+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-pilot-local-tests_istio

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-pilot-local-tests_istio

integ-galley-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-galley-local-tests_istio

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-pilot-local-tests_istio

integ-galley-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-security-local-tests_istio

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-pilot-local-tests_istio

integ-galley-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-security-local-tests_istio

unit-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test unit-tests_istio

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-pilot-local-tests_istio

integ-galley-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-security-local-tests_istio

unit-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test unit-tests_istio

integ-conformance-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-conformance-local-tests_istio

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-pilot-local-tests_istio

integ-galley-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-security-local-tests_istio

unit-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test unit-tests_istio

integ-conformance-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-conformance-local-tests_istio

release-test_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test release-test_istio

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-pilot-local-tests_istio

integ-galley-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-security-local-tests_istio

unit-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test unit-tests_istio

integ-conformance-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-conformance-local-tests_istio

release-test_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test release-test_istio

integ-distroless-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-distroless-k8s-tests_istio

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-pilot-local-tests_istio

integ-galley-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-security-local-tests_istio

unit-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test unit-tests_istio

integ-conformance-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-conformance-local-tests_istio

release-test_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test release-test_istio

integ-distroless-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-distroless-k8s-tests_istio

integ-security-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-security-k8s-tests_istio

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-pilot-local-tests_istio

integ-galley-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-security-local-tests_istio

unit-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test unit-tests_istio

integ-conformance-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-conformance-local-tests_istio

release-test_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test release-test_istio

integ-distroless-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-distroless-k8s-tests_istio

integ-security-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-telemetry-k8s-tests_istio

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-pilot-local-tests_istio

integ-galley-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-security-local-tests_istio

unit-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test unit-tests_istio

integ-conformance-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-conformance-local-tests_istio

release-test_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test release-test_istio

integ-distroless-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-distroless-k8s-tests_istio

integ-security-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-galley-k8s-tests_istio

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-pilot-local-tests_istio

integ-galley-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-security-local-tests_istio

unit-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test unit-tests_istio

integ-conformance-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-conformance-local-tests_istio

release-test_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test release-test_istio

integ-distroless-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-distroless-k8s-tests_istio

integ-security-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-galley-k8s-tests_istio

integ-mixer-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-mixer-k8s-tests_istio

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-pilot-local-tests_istio

integ-galley-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-security-local-tests_istio

unit-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test unit-tests_istio

integ-conformance-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-conformance-local-tests_istio

release-test_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test release-test_istio

integ-distroless-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-distroless-k8s-tests_istio

integ-security-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-galley-k8s-tests_istio

integ-mixer-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-mixer-k8s-tests_istio

integ-pilot-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-pilot-k8s-tests_istio

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-pilot-local-tests_istio

integ-galley-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-security-local-tests_istio

unit-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test unit-tests_istio

integ-conformance-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-conformance-local-tests_istio

release-test_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test release-test_istio

integ-distroless-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-distroless-k8s-tests_istio

integ-security-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-galley-k8s-tests_istio

integ-mixer-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-mixer-k8s-tests_istio

integ-pilot-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-pilot-k8s-tests_istio

integ-istioio-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-istioio-k8s-tests_istio

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-pilot-local-tests_istio

integ-galley-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-security-local-tests_istio

unit-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test unit-tests_istio

integ-conformance-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-conformance-local-tests_istio

release-test_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test release-test_istio

integ-distroless-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-distroless-k8s-tests_istio

integ-security-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-galley-k8s-tests_istio

integ-mixer-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-mixer-k8s-tests_istio

integ-pilot-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-pilot-k8s-tests_istio

integ-istioio-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-istioio-k8s-tests_istio

integ-conformance-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-conformance-k8s-tests_istio

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-pilot-local-tests_istio

integ-galley-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-security-local-tests_istio

unit-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test unit-tests_istio

integ-conformance-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-conformance-local-tests_istio

release-test_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test release-test_istio

integ-distroless-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-distroless-k8s-tests_istio

integ-security-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-galley-k8s-tests_istio

integ-mixer-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-mixer-k8s-tests_istio

integ-pilot-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-pilot-k8s-tests_istio

integ-istioio-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-istioio-k8s-tests_istio

integ-conformance-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-conformance-k8s-tests_istio

e2e-dashboard_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test e2e-dashboard_istio

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-pilot-local-tests_istio

integ-galley-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-security-local-tests_istio

unit-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test unit-tests_istio

integ-conformance-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-conformance-local-tests_istio

release-test_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test release-test_istio

integ-distroless-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-distroless-k8s-tests_istio

integ-security-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-galley-k8s-tests_istio

integ-mixer-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-mixer-k8s-tests_istio

integ-pilot-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-pilot-k8s-tests_istio

integ-istioio-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-istioio-k8s-tests_istio

integ-conformance-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-conformance-k8s-tests_istio

e2e-dashboard_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test e2e-dashboard_istio

lint_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test lint_istio

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-pilot-local-tests_istio

integ-galley-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-galley-local-tests_istio

integ-security-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-security-local-tests_istio

unit-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test unit-tests_istio

integ-conformance-local-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-conformance-local-tests_istio

release-test_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test release-test_istio

integ-distroless-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-distroless-k8s-tests_istio

integ-security-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-galley-k8s-tests_istio

integ-mixer-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-mixer-k8s-tests_istio

integ-pilot-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-pilot-k8s-tests_istio

integ-istioio-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-istioio-k8s-tests_istio

integ-conformance-k8s-tests_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test integ-conformance-k8s-tests_istio

e2e-dashboard_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test e2e-dashboard_istio

lint_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test lint_istio

e2e-mixer-no_auth_istio
98b3d98e73a42f2f67d8c4647982ca5a9423b1b9
link
/test e2e-mixer-no_auth_istio

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.

updated by another pr


[SPARK-23988][MESOS] Improve handling of appResource in mesos dispatcher when using Docker

Improve/fix handling of appResource for mesos dispatcher when using docker
Tested with new unit tests as well as manually on private mesos cluster

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

@tnachen what do you think?

@tnachen @susanxhuynh @mgummelt @skonto

Can one of the admins verify this patch?

Can one of the admins verify this patch?


Explicitly load the VS assemblies on Dev15 to fix unit test debugging

See issue description in the comment at https://github.com/Microsoft/nodejstools/pull/1524#issuecomment-293761532 .
This may not be the most elegant solution, or the right one long term, but it does work and is simple enough. If in the test executor process, then by loading the assemblies explicitly when it attempts to run tests, but before hitting any code that would cause .NET to try and locate the assemblies, they are already loaded when required.

We should figure out who the owner is for the exe and ask them to update the app.config.

Addressed feedback.


ContributionGraph tile opacity is not evenly distributed based on the radical count values

ContributionGraph tile opacity is not evenly distributed based on the radical count values, which results in tiles with great count value discrepancies to be hardly distinguishable on the chart, which results in a lower user experience

I suggest this PR to fix this


Give the docs a better design

Thinking something like transforming this to a middleman app and using the robots css

Have you considered using softcover.io?
It lets you write markdown and output it as HTML, epub, PDF, mobi.
I've never used it, but it seems good. It was used for the most recent version of the Rails Tutorial (and also written by the author, Michael Hartl)
Could be neat to have this as a PDF!

@cllns I'm not sure we wnt a PDF version. I was more thinking a gh-pages branch with some nice styles.


GetCellType returns numeric value.

Hi, I'm using this code (below). Cell A1 in that sheet is a string containing the words "User ID".
When I run this code I get typ=5 and I am expecting typ="string"
package main
import (
//	"context"
"log"
"github.com/xuri/excelize/v2"
)
func importExcel(xls string) {
f, err := excelize.OpenFile(xls)
if err != nil {
log.Println("could not open file ",xls)
log.Println(err.Error)
return
}
defer f.Close()
// first off, check the file
val,err:=f.GetCellValue("Data","A1")
log.Println("Data A1 is ",val)
typ,err:=f.GetCellType("Data","A1")
log.Println("typ A1 is ",typ)
}

The CellType using itoa data type represents the cell data type enumeration, the value 5 means which is an inline string.

The CellType using itoa data type represents the cell data type enumeration, the value 5 means which is an inline string.

ah ok, it's just all the examples I saw online seemed to return a string result.
Many thanks for speedy reply.


feat: workspace symbols

Current dependencies on/for this PR:

2023-06-25-symbol-table

PR #31   👈

This comment was auto-generated by Graphite.


Documenting JSON:API-style filter and page attributes

So in JSON:API 1.0 specification the filter and page attributes are actually maps.
And the attributes themselves would be filter[attribute_name]=term or page[number]=2.
How to document this with Blueprint? Just keep filter[attribute_name] as attribute name?

Yes, I needed parameters. Great answer thanks a lot, I will try it and then close this issue:)


Absorb exceptions while mapping responses with impure functions

Before submitting pull request:

[x] Check if the project compiles by running sbt compile
[x] Verify docs compilation by running sbt compileDocs
[x] Check if tests pass by running sbt test
[x] Format code by running sbt scalafmt

In certain cases MappedResponseAs will have impure functions embedded within it.
For example getRight is implemented in the following way:
ra.mapWithMetadata { case (t, meta) =>
  t match {
    case Left(a: Exception) => throw a
    case Left(a)            => throw HttpError(a, meta.code)
    case Right(b)           => b
  }
}

The exception will end up getting thrown inside of the map function of the target monad, which is not handled nicely by all effect types that sttp supports. For example for zio, this will result in the fiber dying instead of failing

What is the correct place to place tests for this? I had a brief look but didn't see any test suite dedicated to the various responseas data structures

@mschuwalow Thanks; most of the testing is done on a more integration level, when testing a backend, see HttpTest and its usages

Thanks :)


fix(table): Pagination should not be displayed if the table has no data

Types of changes

[ ] New feature
[x] Bug fix
[ ] Documentation change
[ ] Coding style change
[ ] Component style change
[ ] Refactoring
[ ] Performance improvement
[ ] Test cases
[ ] Continuous integration
[ ] Typescript definition change
[ ] Breaking change
[ ] Others

Background and context

#433
Solution

How is the change tested?

Changelog

Component
Changelog(CN)
Changelog(EN)
Related issues

Table
如果表格没有数据，分页不应该展示 。
Pagination should not be displayed if the table has no data.
Close: https://github.com/arco-design/arco-design/issues/433

Checklist:

[x] Test suite passes (npm run test)
[ ] Provide changelog for relevant changes (e.g. bug fixes and new features) if applicable.
[ ] Changes are submitted to the appropriate branch (e.g. features should be submitted to feature branch and others should be submitted to main branch)

Other information

thx~


Correct behavior of IsTemplate() in Class

Consider a dummy template:
template <typename T>
struct Test {
};

Checking Class.IsTemplate() on the parsed entity returns false.
Apparently the declaration should have IsDependent = true in order to be eligible for checking if being a template.
What is meant by IsDependent?
Are these specific for CSharp?
Thanks.

Well looks like the template semantics needs heavy refactoring then. Is anyone willing to work on this issue because right now template manipulation is so messy/obscure.

I'll probably try to clean this up a bit, but won't do any too heavy refactoring as that would take too much time.
I think getting rid of the duplicated lists and linking Class and ClassTemplate would take care of most of it?

I think this will be sufficient.
The most important thing is to be able to query template parameters accurately and in a universal way.
Maybe adding tests is viable too but requires more time of course.

After stumbling upon TypeAlias which has a DescribedAliasTemplate property, an elegant solution would be adding a DescribedTemplate property in Declaration which can be null if the declaration is not a template, and a property which casts to the adequat type in any templated declaration like: Class, Function, Method, Variable etc...


Fixing secrets in automation.

Automation scrips have been failing due to a breaking change that was introduced from v2.6

Changed the env variable to "environment" and envFrom to "environmentFrom"
Verify for v2.5 and below releases, env and envfrom works
Verify from 2.6 "environment" and "environmentFrom" works

LGTM!

LGTM


Paste images don't work.

I don't really know why it's happening, but I did the test in the incognito tab with the extension turned off:
I can't 'paste' images with control v or by right-clicking and clicking 'paste'.
I use this a lot when I want to paste a quick print that I made, and although the extension is wonderful, I just can't do it with it active.

Which browser and version the extension are you using? I can't think of anything Tweak New Twitter does which should affect this. Do you have any other Twitter extensions active as well?
Pasting both ways is working for me:

Sorry for the delay in responding, I've had a pretty busy week.
My browser was Chrome at 109.0.5414.120, and it just updated to the latest version.
I wanted to make sure the problem was just me. I discovered the extension conflict. I use one called "Absolute Enable Right Click & Copy" that allows you to right click on websites that don't allow it. When it is activated on twitter, combined with the Control Panel, a bug occurs, which does not allow me to do this. When I turn off one of the two, the function works again. I already got it working. Thank you very much for your answer, I hope that if someone has a similar problem, they can do what I did to disable each extension to discover the origin. I have a lot of extensions installed (27 at the moment), so it's always a problem to figure out what's going wrong.


 Multiple goroutines wait on restoreComplete to close in order to proceed, so there are no messages to consume. This goroutine existed purely for ending parallel mode.

/test

/test

/test


Changes m_owners and m_ownerIndex to use address instead of uint.

It is unclear why this code was using uint previously instead of address.  If address is what is intended, address should be used.  Using address not only makes the intent more clear, it allows the static analyzer to validate the code.
Also, tooling will now work better with this contract since the types are correct.
If these variables were intentionally uint, I am curious to know the reason why and at the least there should be a comment in the code indicating why they are uint.

Moved from https://github.com/ethereum/meteor-dapp-wallet/pull/148 per request of @alexvandesande.

ACK on this, any historical reason not to?

It was used for optimization purposes.

Is the optimization still necessary?  If working with an address is slower than working with an int then that sounds like a bug that should be addressed in the VM or compiler, not by the dapp.

Yes, there are several missing features in the optimizer.

Hey Chris, can you shed some light on the impact of making this change and what is unoptimized?
I am creating a seperate diff to add a public interface to the owners, pending approvals etc, but the interfaces should return an address.
I deployed the new contract and it was a little larger in size but not significant (and we can use stubs).

@bencxr the optimizations are probably not worth it. It reduces the code size and execution-time gas costs, but they are probably largely dominated by storage costs anyway.

Other than a rebase, is there anything I can do to move this PR forward?  If it is undesired, let me know so I can close it out.  If more discussion is required, is there anyone else that could be @mentioned to get appropriate visibility?

I think the main problem is that this file is old, complex, yet very important. Since, I believe solidity good practices have made sol files much more readable and understandable since then. So no one is volunteering to take the risk of reviewing and updating this code, because a lot of value can be lost by an accidental bug.
Consensys is working on a new wallet app that has a compatible interface but has a simpler more manageable code and it's the Mist teams intention to migrate to that over time..

Okay, I'll close out this PR then, thanks!


Several instances have head_age = 999

From the data info, this is for head ages that are unknown. If I'm grouping the instances by head age and income, should these instances with head_age = 999 be dropped?

@prrathi If you are using the a pandas.groupby, it will group by all age values, including this indicator for a missing value.  Whether you should drop these values might depend on what you are trying to do, but for most OG-USA calibrations of age-specific values, I'd drop these.  Also, given the few observations above age 80, it maybe best to compute age-specific values for ages 20-80 and then we can interpolate values for ages above 80.

Should the observations above age 80 be combined with age 80, or completely separate? Also same question for the one observation with head age 18 and 36 observations with head age 19

@prrathi for consistency at this point, let's not include those over 80 and under 20.


Add Type to InteractionDataOption

This PR adds the ApplicationCommandOptionType to the InteractionDataOption as defined in SlashCommands#ApplicationCommandInteractionDataOption

Closing as development of Interactions has moved to https://github.com/Discord-Net-Labs/Discord.Net-Labs


Add CPOST Build and test CI stages

Validated locally
[build/build] 🚀  Start image=catthehacker/ubuntu:act-latest
[build/build]   🐳  docker run image=catthehacker/ubuntu:act-latest platform= entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[]
[build/build]   🐳  docker exec cmd=[mkdir -m 0777 -p /var/run/act] user=root
[build/build]   🐳  docker cp src=/Users/elacey/Code/clara-pipeline-operator-sizing-tool/. dst=/Users/elacey/Code/clara-pipeline-operator-sizing-tool
[build/build]   🐳  docker exec cmd=[mkdir -p /Users/elacey/Code/clara-pipeline-operator-sizing-tool] user=
[build/build] ⭐  Run actions/checkout@v2
[build/build]   ✅  Success - actions/checkout@v2
[build/build] ⭐  Run Set up Python 3.8
INFO[0001]   ☁  git clone 'https://github.com/actions/setup-python' # ref=v2
[build/build]   🐳  docker cp src=/Users/elacey/.cache/act/actions-setup-python@v2/ dst=/var/run/act/actions/actions-setup-python@v2/
[build/build]   🐳  docker exec cmd=[mkdir -p /var/run/act/actions/actions-setup-python@v2/] user=
[build/build]   🐳  docker exec cmd=[node<EMAIL_ADDRESS>user=
[build/build]   💬  ::debug::Semantic version spec of 3.8 is 3.8
[build/build]   💬  ::debug::isExplicit:
[build/build]   💬  ::debug::explicit? false
[build/build]   💬  ::debug::evaluating 0 versions
[build/build]   💬  ::debug::match not found
| Version 3.8 was not found in the local cache
[build/build]   💬  ::debug::check 3.10.0-rc.1 satisfies 3.8
[build/build]   💬  ::debug::check 3.10.0-beta.4 satisfies 3.8
[build/build]   💬  ::debug::check 3.10.0-beta.3 satisfies 3.8
[build/build]   💬  ::debug::check 3.10.0-beta.2 satisfies 3.8
[build/build]   💬  ::debug::check 3.10.0-beta.1 satisfies 3.8
[build/build]   💬  ::debug::check 3.10.0-alpha.7 satisfies 3.8
[build/build]   💬  ::debug::check 3.10.0-alpha.6 satisfies 3.8
[build/build]   💬  ::debug::check 3.10.0-alpha.5 satisfies 3.8
[build/build]   💬  ::debug::check 3.10.0-alpha.4 satisfies 3.8
[build/build]   💬  ::debug::check 3.10.0-alpha.3 satisfies 3.8
[build/build]   💬  ::debug::check 3.10.0-alpha.2 satisfies 3.8
[build/build]   💬  ::debug::check 3.10.0-alpha.1 satisfies 3.8
[build/build]   💬  ::debug::check 3.9.6 satisfies 3.8
[build/build]   💬  ::debug::check 3.9.5 satisfies 3.8
[build/build]   💬  ::debug::check 3.9.4 satisfies 3.8
[build/build]   💬  ::debug::check 3.9.3 satisfies 3.8
[build/build]   💬  ::debug::check 3.9.2 satisfies 3.8
[build/build]   💬  ::debug::check 3.9.2-rc.1 satisfies 3.8
[build/build]   💬  ::debug::check 3.9.1 satisfies 3.8
[build/build]   💬  ::debug::check 3.9.1-rc.1 satisfies 3.8
[build/build]   💬  ::debug::check 3.9.0 satisfies 3.8
[build/build]   💬  ::debug::check 3.9.0-rc.2 satisfies 3.8
[build/build]   💬  ::debug::check 3.9.0-rc.1 satisfies 3.8
[build/build]   💬  ::debug::check 3.9.0-beta.5 satisfies 3.8
[build/build]   💬  ::debug::check 3.9.0-beta.4 satisfies 3.8
[build/build]   💬  ::debug::check 3.8.11 satisfies 3.8
[build/build]   💬  ::debug::x64===x64 && darwin===linux
[build/build]   💬  ::debug::x64===x64 && linux===linux
[build/build]   💬  ::debug::x64===x64 && linux===linux
[build/build]   💬  ::debug::matched 3.8.11
| Version 3.8 is available for downloading
| Download from "https://github.com/actions/python-versions/releases/download/3.8.11-113062/python-3.8.11-linux-20.04-x64.tar.gz"
[build/build]   💬  ::debug::Downloading https://github.com/actions/python-versions/releases/download/3.8.11-113062/python-3.8.11-linux-20.04-x64.tar.gz
[build/build]   💬  ::debug::Destination /tmp/7e291122-542d-46dc-961b-77cb1a89729d
[build/build]   💬  ::debug::download complete
| Extract downloaded archive
[build/build]   💬  ::debug::Checking tar --version
[build/build]   💬  ::debug::tar (GNU tar) 1.30%0ACopyright (C) 2017 Free Software Foundation, Inc.%0ALicense GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.%0AThis is free software: you are free to change and redistribute it.%0AThere is NO WARRANTY, to the extent permitted by law.%0A%0AWritten by John Gilmore and Jay Fenlason.
| [command]/usr/bin/tar xz --warning=no-unknown-keyword -C /tmp/747ce601-95bf-4d69-b476-7e021926d4c1 -f /tmp/7e291122-542d-46dc-961b-77cb1a89729d
| Execute installation script
| Check if Python hostedtoolcache folder exist...
| Creating Python hostedtoolcache folder...
| Create Python 3.8.11 folder
| Copy Python binaries to hostedtoolcache folder
| Create additional symlinks (Required for the UsePythonVersion Azure Pipelines task and the setup-python GitHub Action)
| Upgrading PIP...
| Looking in links: /tmp/tmpkznme1z0
| Requirement already satisfied: setuptools in /opt/hostedtoolcache/Python/3.8.11/x64/lib/python3.8/site-packages (56.0.0)
| Requirement already satisfied: pip in /opt/hostedtoolcache/Python/3.8.11/x64/lib/python3.8/site-packages (21.1.1)
[build/build]   ❗  ::error::WARNING: Running pip as root will break packages and permissions. You should install packages reliably by using venv: https://pip.pypa.io/warnings/venv
| Collecting pip
| Downloading pip-21.2.4-py3-none-any.whl (1.6 MB)
| Installing collected packages: pip
| Successfully installed pip-21.2.4
[build/build]   ❗  ::error::WARNING: Running pip as root will break packages and permissions. You should install packages reliably by using venv: https://pip.pypa.io/warnings/venv
[build/build]   ❗  ::error::WARNING: You are using pip version 21.1.1; however, version 21.2.4 is available.%0AYou should consider upgrading via the '/opt/hostedtoolcache/Python/3.8.11/x64/bin/python -m pip install --upgrade pip' command.
| Create complete file
[build/build]   💬  ::debug::isExplicit:
[build/build]   💬  ::debug::explicit? false
[build/build]   💬  ::debug::isExplicit: 3.8.11
[build/build]   💬  ::debug::explicit? true
[build/build]   💬  ::debug::evaluating 1 versions
[build/build]   💬  ::debug::matched: 3.8.11
[build/build]   💬  ::debug::checking cache: /opt/hostedtoolcache/Python/3.8.11/x64
[build/build]   💬  ::debug::Found tool in cache Python 3.8.11 x64
[build/build]   ⚙  ::set-output:: python-version=3.8.11
| Successfully setup CPython (3.8.11)
[build/build]   ❓<EMAIL_ADDRESS>[build/build]   ✅  Success - Set up Python 3.8
[build/build] ⭐  Run Install dependencies
[build/build]   🐳  docker exec cmd=[bash --noprofile --norc -e -o pipefail /Users/elacey/Code/clara-pipeline-operator-sizing-tool/workflow/2] user=
| Requirement already satisfied: pip in /opt/hostedtoolcache/Python/3.8.11/x64/lib/python3.8/site-packages (21.2.4)
| Collecting wheel
|   Downloading wheel-0.37.0-py2.py3-none-any.whl (35 kB)
| Installing collected packages: wheel
| Successfully installed wheel-0.37.0
| WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
| Collecting psutil==5.8.0
|   Downloading psutil-5.8.0-cp38-cp38-manylinux2010_x86_64.whl (296 kB)
     |████████████████████████████████| 296 kB 1.4 MB/s
| Collecting pytest==6.2.4
|   Downloading pytest-6.2.4-py3-none-any.whl (280 kB)
     |████████████████████████████████| 280 kB 1.5 MB/s
| Collecting PyYAML==5.4.1
|   Downloading PyYAML-5.4.1-cp38-cp38-manylinux1_x86_64.whl (662 kB)
     |████████████████████████████████| 662 kB 3.6 MB/s
| Collecting requests==2.25.1
|   Downloading requests-2.25.1-py2.py3-none-any.whl (61 kB)
     |████████████████████████████████| 61 kB 6.3 MB/s
| Collecting tabulate==0.8.9
|   Downloading tabulate-0.8.9-py3-none-any.whl (25 kB)
| Collecting iniconfig
|   Downloading iniconfig-1.1.1-py2.py3-none-any.whl (5.0 kB)
| Collecting attrs>=19.2.0
|   Downloading attrs-21.2.0-py2.py3-none-any.whl (53 kB)
     |████████████████████████████████| 53 kB 3.9 MB/s
| Collecting packaging
|   Downloading packaging-21.0-py3-none-any.whl (40 kB)
     |████████████████████████████████| 40 kB 4.5 MB/s
| Collecting pluggy<1.0.0a1,>=0.12
|   Downloading pluggy-0.13.1-py2.py3-none-any.whl (18 kB)
| Collecting toml
|   Downloading toml-0.10.2-py2.py3-none-any.whl (16 kB)
| Collecting py>=1.8.2
|   Downloading py-1.10.0-py2.py3-none-any.whl (97 kB)
     |████████████████████████████████| 97 kB 8.1 MB/s
| Collecting chardet<5,>=3.0.2
|   Downloading chardet-4.0.0-py2.py3-none-any.whl (178 kB)
     |████████████████████████████████| 178 kB 5.1 MB/s
| Collecting idna<3,>=2.5
|   Downloading idna-2.10-py2.py3-none-any.whl (58 kB)
     |████████████████████████████████| 58 kB 2.0 MB/s
| Collecting urllib3<1.27,>=1.21.1
|   Downloading urllib3-1.26.6-py2.py3-none-any.whl (138 kB)
     |████████████████████████████████| 138 kB 3.4 MB/s
| Collecting certifi>=2017.4.17
|   Downloading certifi-2021.5.30-py2.py3-none-any.whl (145 kB)
     |████████████████████████████████| 145 kB 5.1 MB/s
| Collecting pyparsing>=2.0.2
|   Downloading pyparsing-2.4.7-py2.py3-none-any.whl (67 kB)
     |████████████████████████████████| 67 kB 13.0 MB/s
| Installing collected packages: pyparsing, urllib3, toml, py, pluggy, packaging, iniconfig, idna, chardet, certifi, attrs, tabulate, requests, PyYAML, pytest, psutil
| Successfully installed PyYAML-5.4.1 attrs-21.2.0 certifi-2021.5.30 chardet-4.0.0 idna-2.10 iniconfig-1.1.1 packaging-21.0 pluggy-0.13.1 psutil-5.8.0 py-1.10.0 pyparsing-2.4.7 pytest-6.2.4 requests-2.25.1 tabulate-0.8.9 toml-0.10.2 urllib3-1.26.6
| WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
[build/build]   ✅  Success - Install dependencies
[build/build] ⭐  Run Build
[build/build]   🐳  docker exec cmd=[bash --noprofile --norc -e -o pipefail /Users/elacey/Code/clara-pipeline-operator-sizing-tool/workflow/3] user=
| running sdist
| running egg_info
| creating nvidia_clara_cpost.egg-info
| writing nvidia_clara_cpost.egg-info/PKG-INFO
| writing dependency_links to nvidia_clara_cpost.egg-info/dependency_links.txt
| writing entry points to nvidia_clara_cpost.egg-info/entry_points.txt
| writing requirements to nvidia_clara_cpost.egg-info/requires.txt
| writing top-level names to nvidia_clara_cpost.egg-info/top_level.txt
| writing manifest file 'nvidia_clara_cpost.egg-info/SOURCES.txt'
| adding license file 'LICENSE' (matched pattern 'LICEN[CS]E*')
| reading manifest file 'nvidia_clara_cpost.egg-info/SOURCES.txt'
| writing manifest file 'nvidia_clara_cpost.egg-info/SOURCES.txt'
| running check
| warning: check: missing meta-data: if 'author' supplied, 'author_email' must be supplied too
|
| creating nvidia-clara-cpost-0.0.0
| creating nvidia-clara-cpost-0.0.0/nvidia_clara_cpost.egg-info
| creating nvidia-clara-cpost-0.0.0/src
| creating nvidia-clara-cpost-0.0.0/tests
| copying files to nvidia-clara-cpost-0.0.0...
| copying LICENSE -> nvidia-clara-cpost-0.0.0
| copying README.md -> nvidia-clara-cpost-0.0.0
| copying setup.cfg -> nvidia-clara-cpost-0.0.0
| copying setup.py -> nvidia-clara-cpost-0.0.0
| copying nvidia_clara_cpost.egg-info/PKG-INFO -> nvidia-clara-cpost-0.0.0/nvidia_clara_cpost.egg-info
| copying nvidia_clara_cpost.egg-info/SOURCES.txt -> nvidia-clara-cpost-0.0.0/nvidia_clara_cpost.egg-info
| copying nvidia_clara_cpost.egg-info/dependency_links.txt -> nvidia-clara-cpost-0.0.0/nvidia_clara_cpost.egg-info
| copying nvidia_clara_cpost.egg-info/entry_points.txt -> nvidia-clara-cpost-0.0.0/nvidia_clara_cpost.egg-info
| copying nvidia_clara_cpost.egg-info/requires.txt -> nvidia-clara-cpost-0.0.0/nvidia_clara_cpost.egg-info
| copying nvidia_clara_cpost.egg-info/top_level.txt -> nvidia-clara-cpost-0.0.0/nvidia_clara_cpost.egg-info
| copying src/__init__.py -> nvidia-clara-cpost-0.0.0/src
| copying src/clarac_utils.py -> nvidia-clara-cpost-0.0.0/src
| copying src/cli.py -> nvidia-clara-cpost-0.0.0/src
| copying src/constants.py -> nvidia-clara-cpost-0.0.0/src
| copying src/container.py -> nvidia-clara-cpost-0.0.0/src
| copying src/main.py -> nvidia-clara-cpost-0.0.0/src
| copying src/pipeline_utils.py -> nvidia-clara-cpost-0.0.0/src
| copying src/topology_sort.py -> nvidia-clara-cpost-0.0.0/src
| copying src/triton_utils.py -> nvidia-clara-cpost-0.0.0/src
| copying src/utils.py -> nvidia-clara-cpost-0.0.0/src
| copying tests/__init__.py -> nvidia-clara-cpost-0.0.0/tests
| copying tests/test_clarac_utils.py -> nvidia-clara-cpost-0.0.0/tests
| copying tests/test_cli.py -> nvidia-clara-cpost-0.0.0/tests
| copying tests/test_container.py -> nvidia-clara-cpost-0.0.0/tests
| copying tests/test_main.py -> nvidia-clara-cpost-0.0.0/tests
| copying tests/test_pipeline_utils.py -> nvidia-clara-cpost-0.0.0/tests
| copying tests/test_topology_sort.py -> nvidia-clara-cpost-0.0.0/tests
| copying tests/test_triton_utils.py -> nvidia-clara-cpost-0.0.0/tests
| copying tests/test_utils.py -> nvidia-clara-cpost-0.0.0/tests
| Writing nvidia-clara-cpost-0.0.0/setup.cfg
| creating dist
| Creating tar archive
| removing 'nvidia-clara-cpost-0.0.0' (and everything under it)
| running bdist_wheel
| running build
| running build_py
| creating build
| creating build/lib
| creating build/lib/src
| copying src/topology_sort.py -> build/lib/src
| copying src/main.py -> build/lib/src
| copying src/cli.py -> build/lib/src
| copying src/utils.py -> build/lib/src
| copying src/container.py -> build/lib/src
| copying src/pipeline_utils.py -> build/lib/src
| copying src/triton_utils.py -> build/lib/src
| copying src/clarac_utils.py -> build/lib/src
| copying src/constants.py -> build/lib/src
| copying src/__init__.py -> build/lib/src
| creating build/lib/tests
| copying tests/test_container.py -> build/lib/tests
| copying tests/test_utils.py -> build/lib/tests
| copying tests/test_topology_sort.py -> build/lib/tests
| copying tests/test_pipeline_utils.py -> build/lib/tests
| copying tests/test_triton_utils.py -> build/lib/tests
| copying tests/__init__.py -> build/lib/tests
| copying tests/test_cli.py -> build/lib/tests
| copying tests/test_main.py -> build/lib/tests
| copying tests/test_clarac_utils.py -> build/lib/tests
| installing to build/bdist.linux-x86_64/wheel
| running install
| running install_lib
| creating build/bdist.linux-x86_64
| creating build/bdist.linux-x86_64/wheel
| creating build/bdist.linux-x86_64/wheel/src
| copying build/lib/src/topology_sort.py -> build/bdist.linux-x86_64/wheel/src
| copying build/lib/src/main.py -> build/bdist.linux-x86_64/wheel/src
| copying build/lib/src/cli.py -> build/bdist.linux-x86_64/wheel/src
| copying build/lib/src/utils.py -> build/bdist.linux-x86_64/wheel/src
| copying build/lib/src/container.py -> build/bdist.linux-x86_64/wheel/src
| copying build/lib/src/pipeline_utils.py -> build/bdist.linux-x86_64/wheel/src
| copying build/lib/src/triton_utils.py -> build/bdist.linux-x86_64/wheel/src
| copying build/lib/src/clarac_utils.py -> build/bdist.linux-x86_64/wheel/src
| copying build/lib/src/constants.py -> build/bdist.linux-x86_64/wheel/src
| copying build/lib/src/__init__.py -> build/bdist.linux-x86_64/wheel/src
| creating build/bdist.linux-x86_64/wheel/tests
| copying build/lib/tests/test_container.py -> build/bdist.linux-x86_64/wheel/tests
| copying build/lib/tests/test_utils.py -> build/bdist.linux-x86_64/wheel/tests
| copying build/lib/tests/test_topology_sort.py -> build/bdist.linux-x86_64/wheel/tests
| copying build/lib/tests/test_pipeline_utils.py -> build/bdist.linux-x86_64/wheel/tests
| copying build/lib/tests/test_triton_utils.py -> build/bdist.linux-x86_64/wheel/tests
| copying build/lib/tests/__init__.py -> build/bdist.linux-x86_64/wheel/tests
| copying build/lib/tests/test_cli.py -> build/bdist.linux-x86_64/wheel/tests
| copying build/lib/tests/test_main.py -> build/bdist.linux-x86_64/wheel/tests
| copying build/lib/tests/test_clarac_utils.py -> build/bdist.linux-x86_64/wheel/tests
| running install_egg_info
| Copying nvidia_clara_cpost.egg-info to build/bdist.linux-x86_64/wheel/nvidia_clara_cpost-0.0.0-py3.8.egg-info
| running install_scripts
| adding license file "LICENSE" (matched pattern "LICEN[CS]E*")
| creating build/bdist.linux-x86_64/wheel/nvidia_clara_cpost-0.0.0.dist-info/WHEEL
| creating 'dist/nvidia_clara_cpost-0.0.0-py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it
| adding 'src/__init__.py'
| adding 'src/clarac_utils.py'
| adding 'src/cli.py'
| adding 'src/constants.py'
| adding 'src/container.py'
| adding 'src/main.py'
| adding 'src/pipeline_utils.py'
| adding 'src/topology_sort.py'
| adding 'src/triton_utils.py'
| adding 'src/utils.py'
| adding 'tests/__init__.py'
| adding 'tests/test_clarac_utils.py'
| adding 'tests/test_cli.py'
| adding 'tests/test_container.py'
| adding 'tests/test_main.py'
| adding 'tests/test_pipeline_utils.py'
| adding 'tests/test_topology_sort.py'
| adding 'tests/test_triton_utils.py'
| adding 'tests/test_utils.py'
| adding 'nvidia_clara_cpost-0.0.0.dist-info/LICENSE'
| adding 'nvidia_clara_cpost-0.0.0.dist-info/METADATA'
| adding 'nvidia_clara_cpost-0.0.0.dist-info/WHEEL'
| adding 'nvidia_clara_cpost-0.0.0.dist-info/entry_points.txt'
| adding 'nvidia_clara_cpost-0.0.0.dist-info/top_level.txt'
| adding 'nvidia_clara_cpost-0.0.0.dist-info/RECORD'
| removing build/bdist.linux-x86_64/wheel
[build/build]   ✅  Success - Build
[build/build] ⭐  Run Install
[build/build]   🐳  docker exec cmd=[bash --noprofile --norc -e -o pipefail /Users/elacey/Code/clara-pipeline-operator-sizing-tool/workflow/4] user=
| Processing ./dist/nvidia_clara_cpost-0.0.0-py3-none-any.whl
| Requirement already satisfied: requests==2.25.1 in /opt/hostedtoolcache/Python/3.8.11/x64/lib/python3.8/site-packages (from nvidia-clara-cpost==0.0.0) (2.25.1)
| Requirement already satisfied: pytest==6.2.4 in /opt/hostedtoolcache/Python/3.8.11/x64/lib/python3.8/site-packages (from nvidia-clara-cpost==0.0.0) (6.2.4)
| Requirement already satisfied: psutil==5.8.0 in /opt/hostedtoolcache/Python/3.8.11/x64/lib/python3.8/site-packages (from nvidia-clara-cpost==0.0.0) (5.8.0)
| Requirement already satisfied: tabulate==0.8.9 in /opt/hostedtoolcache/Python/3.8.11/x64/lib/python3.8/site-packages (from nvidia-clara-cpost==0.0.0) (0.8.9)
| Requirement already satisfied: PyYAML==5.4.1 in /opt/hostedtoolcache/Python/3.8.11/x64/lib/python3.8/site-packages (from nvidia-clara-cpost==0.0.0) (5.4.1)
| Requirement already satisfied: packaging in /opt/hostedtoolcache/Python/3.8.11/x64/lib/python3.8/site-packages (from pytest==6.2.4->nvidia-clara-cpost==0.0.0) (21.0)
| Requirement already satisfied: toml in /opt/hostedtoolcache/Python/3.8.11/x64/lib/python3.8/site-packages (from pytest==6.2.4->nvidia-clara-cpost==0.0.0) (0.10.2)
| Requirement already satisfied: iniconfig in /opt/hostedtoolcache/Python/3.8.11/x64/lib/python3.8/site-packages (from pytest==6.2.4->nvidia-clara-cpost==0.0.0) (1.1.1)
| Requirement already satisfied: pluggy<1.0.0a1,>=0.12 in /opt/hostedtoolcache/Python/3.8.11/x64/lib/python3.8/site-packages (from pytest==6.2.4->nvidia-clara-cpost==0.0.0) (0.13.1)
| Requirement already satisfied: attrs>=19.2.0 in /opt/hostedtoolcache/Python/3.8.11/x64/lib/python3.8/site-packages (from pytest==6.2.4->nvidia-clara-cpost==0.0.0) (21.2.0)
| Requirement already satisfied: py>=1.8.2 in /opt/hostedtoolcache/Python/3.8.11/x64/lib/python3.8/site-packages (from pytest==6.2.4->nvidia-clara-cpost==0.0.0) (1.10.0)
| Requirement already satisfied: urllib3<1.27,>=1.21.1 in /opt/hostedtoolcache/Python/3.8.11/x64/lib/python3.8/site-packages (from requests==2.25.1->nvidia-clara-cpost==0.0.0) (1.26.6)
| Requirement already satisfied: chardet<5,>=3.0.2 in /opt/hostedtoolcache/Python/3.8.11/x64/lib/python3.8/site-packages (from requests==2.25.1->nvidia-clara-cpost==0.0.0) (4.0.0)
| Requirement already satisfied: certifi>=2017.4.17 in /opt/hostedtoolcache/Python/3.8.11/x64/lib/python3.8/site-packages (from requests==2.25.1->nvidia-clara-cpost==0.0.0) (2021.5.30)
| Requirement already satisfied: idna<3,>=2.5 in /opt/hostedtoolcache/Python/3.8.11/x64/lib/python3.8/site-packages (from requests==2.25.1->nvidia-clara-cpost==0.0.0) (2.10)
| Requirement already satisfied: pyparsing>=2.0.2 in /opt/hostedtoolcache/Python/3.8.11/x64/lib/python3.8/site-packages (from packaging->pytest==6.2.4->nvidia-clara-cpost==0.0.0) (2.4.7)
| Installing collected packages: nvidia-clara-cpost
| Successfully installed nvidia-clara-cpost-0.0.0
| WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
[build/build]   ✅  Success - Install
[build/build] ⭐  Run Test
[build/build]   🐳  docker exec cmd=[bash --noprofile --norc -e -o pipefail /Users/elacey/Code/clara-pipeline-operator-sizing-tool/workflow/5] user=
| ============================= test session starts ==============================
| platform linux -- Python 3.8.11, pytest-6.2.4, py-1.10.0, pluggy-0.13.1
| rootdir: /Users/elacey/Code/clara-pipeline-operator-sizing-tool
collected 133 items
|
| tests/test_clarac_utils.py ....sss                                       [  5%]
| tests/test_cli.py .......................                                [ 22%]
| tests/test_container.py ........                                         [ 28%]
| tests/test_main.py .                                                     [ 29%]
| tests/test_pipeline_utils.py ...............................             [ 52%]
| tests/test_topology_sort.py .......                                      [ 57%]
| tests/test_triton_utils.py .......................                       [ 75%]
| tests/test_utils.py .........s.......................                    [100%]
|
| ======================== 129 passed, 4 skipped in 6.04s ========================


Add method to get activities list.

This PR adds a method to return the list of activities as a list type. Previously this was only available as a csv export.

Hi @rday I've added this method as I needed the capability for a small tool I am extending: https://github.com/benjmarshall/fit_file_uploader/issues/4
Hopefully you can accept this PR and merge changes so it can be brought into the PyPi version.
Cheers,
Ben

Thanks @benjmarshall ! It has been awhile, so give me another day or so to get this on to PyPI.

Thanks @rday !


HTTP status codes not recorded when not 200.

My type used for storing errors returned by my API hold the http status code so that user's can get more information while debugging their failed requests. However, when writing acceptance tests that the correct status codes are returned, DVR simply returns HTTP status code 0 always.
It looks like the status code is not being recorded in the cassette.
Any chance we can also record the status code?

It appears status codes are not recorded at all anymore.
Also, HTTP headers are now absent for HTTP errors (previously they were present)


[pick][GraphQL] Object DataLoader (#17332)

Description
Implement data loaders for fetching historical object versions, objects bounded by their parent versions, and the latest versions of an object at a given checkpoint.
By implementing an Object DataLoader, we also implicitly get support for data-loading all derived types (MoveObject, MovePackage, MoveModule, DynamicField, Coin, etc).
These implementations (particularly historical queries and queries where the version can be bounded by a parent version) can be made even more efficient with the existence of an index/side table that maps an object's ID and version to the checkpoint it is part of. This change has not been included in this PR, but we will follow up on this as part of Object query benchmarking.
As part of this change, I enabled queries for historical objects outside the available range. Later (with the use of an obj_version index) it will also be possible to enable dynamic field look-ups on historical objects as well.
Test Plan
sui$ cargo nextest run -p sui-graphql-rpc
sui$ cargo nextest run -p sui-graphql-e2e-tests --features pg_integration

Run the following query -- after this change, it takes about 8s to complete on the server, fetching about 80 objects, while previously it would either timeout or squeak in just under the 40s timeout. I expect this number to improve further once we have an efficient way to map object ids and versions to a checkpoint sequence number.
query {
  transactionBlocks(last: 5) {
    nodes {
      effects {
        objectChanges(first: 50) {
          pageInfo { hasNextPage }
          nodes {
            idCreated
            idDeleted
            inputState { asMoveObject { contents { json } } }
            outputState { asMoveObject { contents { json } } }
          }
        }
      }
    }
  }
}

Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.

[ ] Protocol:
[ ] Nodes (Validators and Full nodes):
[ ] Indexer:
[ ] JSON-RPC:
[x] GraphQL: Queries for historical versions of objects will now return data even if that version of the object is outside the available range.
[ ] CLI:
[ ] Rust SDK:

Sorry @amnn, wanted to rebase and pushed the wrong button on the UI, so I ended up reverting my UI merge and rebasing from the command line.


Add solutions for 3 step cryptic master clues (continued from #3352)

This extends the functionality of the clue scroll plugin to include solutions for three step cryptic master clues. The solutions for these clues are already present in the existing CrypticClue class, but before this there was not a way for the clues to be recognized. The ThreeStepCrypticClue class matches the clue scroll text for all three cryptic clues and keeps the matched clue objects as a list, along with their completion status. If a clue has a strikethrough tag when reading the clue, then the plugin will recognize it as complete. The plugin will also detect when a new clue part has been obtained and update the completed status of that clue.
Fixes #2923
Closes #3352
In action: https://streamable.com/ujaar
P.S. This is written by @Eadgars-Ruse continued from #3352, with review fixes written by me as requested.

So looking at this PR, what is the point of LocationClueScroll anymore when rest of multi-value clue scrolls are simply merged with single-value.

@devLotto Implemented your recommended changes. Will squash commits here soon probably.

Any update on this? Also needs rebase

Will be doing updates to this in the next couple days.

Rebased and fixed lotto's recent review comments.

Rebased into one commit now.

All the getNpcs etc methods that are returning new array every time the method is called should not do that, the array should be prepared in constructor probably. Otherwise seems not so bad I guess.

Per Lotto's comment (see L326 of ClueScrollPlugin), getNpcs was changed to use an array instead of a collection to avoid a toArray call when running the NPCQuery.

Cryptic clue fixes are now in a separate commit.


feat: port Logic/Relator

Port logic/relator.lean and add comments in the places where the linter demands them.
Compare to the mathlib3 version: https://github.com/leanprover-community/mathlib/blob/7362d50a80c3e7f7a1fb5adb1c0b6ba593db103d/src/logic/relator.lean

bors merge

Let's try that again.
bors merge


l2 delegated for different clients

@supertestnet  Sir, I hope you will extend your work with more clients, this solution quite innovative .

[ ] Rust
[ ] Go
[ ] Python
[ ] ios
[ ] android

If you're interested in bitcoin devlopment projects or help us to make our dream come true with your service's that we are really appricate both parties win

Hi ali,
I probably won't make a client in Rust or Go as I don't know those languages. I am currently working on a javascript client which, if I finish it, I can probably release it as a progressive webapp for use on android and ios. A python app would be cool too. Please help by making clients in those other languages for me! :D


Add tests for the views.

Once merged, this PR will fix #15.

Current coverage is 26.35%

Merging #32 into master will increase coverage by +4.67% as of 697553e

Powered by Codecov. Updated on successful CI builds.

To-Do:

[ ] Merge in url-handler tests
[ ] Remove expected failure from TestFieldReport.test_context()
[ ] Add tests to TestUrlAdd()


The left position of pinned columns in the sticky table is calculated incorrectly

TanStack Table version
8.19.3
Framework/Library version
18.2.0
Describe the bug and the steps to reproduce it
Hey guys, I found an issue where the offset or size of the pinned column is being calculated incorrectly.
Referring to this example:
https://tanstack.com/table/latest/docs/framework/react/examples/column-pinning-sticky
When we make a change like the one below for any column:

cell: (info) =>
'/devicexxx/devicexxx/devicexxx/devicexxx/devicexxx/devicexxx/ devicexxx/devicexxx/devicexxx/devicexxx/devicexxx/ devicexxx/devicexxx/devicexxx/devicexxx/',

And after pinning two columns as shown in the picture, as a result, we will see empty space between columns.
Your Minimal, Reproducible Example - (Sandbox Highly Recommended)
https://codesandbox.io/p/devbox/distracted-hawking-jsz4r9?file=%2Fsrc%2Fmain.tsx%3A47%2C5
Screenshots or Videos (Optional)

No response
Do you intend to try to help solve this bug with your own PR?
No, because I do not have time to dig into it
Terms & Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

The problem is related to column width. Correctly setting minSize prevents the problem, but I don't know the exact size of the specific data in the column, so I don't think this is a solution. Any ideas on how to handle this?

This isn't a problem with TanStack Table's width calculations, but rather how the table CSS is being applied.
One option is to give a min-width to the column as you said.
Another solution is to add word-break: break-all so that there is no min-width on the column at all. Or use some other kind of flex/grid styles instead of the default table CSS.


Tidy up naming of the scala-hadoop-bad-rows project

The folder is named correctly, but the project files etc are a bit inconsistent with the other Scala projects.

doesn't apply anymore, closing


Couldn't catch exception from Rails controller

Description of the bug
If rails controller has error, then there is no exception_event from span.
For example, below is a sample rails controller, and create_error is not defined from User, so it should create error
class UsersController < ApplicationController
  # curl http://<IP_ADDRESS>:8002/users/new
  def new
    @user = User.new
    @user.create_error
  end
end

The sample span from above call
span_data: #<struct OpenTelemetry::SDK::Trace::SpanData name="UsersController#new",
kind=:server, status=#<OpenTelemetry::Trace::Status:0x0000ffffa17e7588 @code=2, @description="">,
parent_span_id="\x00\x00\x00\x00\x00\x00\x00\x00", total_recorded_attributes=12, total_recorded_events=0,
total_recorded_links=0, start_timestamp=1693241683805542134, end_timestamp=1693241684087133009,
attributes={"http.method"=>"GET", "http.host"=>"<IP_ADDRESS>:8002", "http.scheme"=>"http", "http.target"=>"/users/new",
 "http.user_agent"=>"curl/7.74.0", "code.namespace"=>"UsersController", "code.function"=>"new",
"http.status_code"=>500}, links=nil, events=nil, resource=#<OpenTelemetry::SDK::Resources::Resource:0x0000ffffa4c8bf50
@attributes={"service.name"=>"unknown_service", "process.pid"=>151, "process.command"=>"bin/rails",
"process.runtime.name"=>"ruby", "process.runtime.version"=>"3.1.0", "process.runtime.description"=>"ruby 3.1.0p0 (2021-12-25 revision fb4df44d16) [aarch64-linux]",
"telemetry.sdk.name"=>"opentelemetry", "telemetry.sdk.language"=>"ruby", "telemetry.sdk.version"=>"1.2.0"}>,
instrumentation_scope=#<struct OpenTelemetry::SDK::InstrumentationScope
name="OpenTelemetry::Instrumentation::Rack", version="0.22.1">, span_id="F\x7F#\xA7\x80D\e%",
trace_id="\x83\x14\n\x9D\xB68M\x9B\x00\xD3x\xFE\xDF\xE0)0", trace_flags=#<OpenTelemetry::Trace::TraceFlags:0x0000ffffa5c08bb8 @flags=1>,
tracestate=#<OpenTelemetry::Trace::Tracestate:0x0000ffffa4bd91c0 @hash={"sw"=>"0000000000000000-01"}>>

Even though the status_code is 500, but there is no exception.
I checked the opentelemetry-instrumentation-rack between L81-L82, there is no record_exception even the status is 500.  I added request_span.record_exception(Exception.new) if status == 500 between 81 and 82, and rack span can create exception_event.
I tried to produce error from action_view, and the exception was caught in span.
I am wondering is there particular reason or the error should be handled in somewhere else?
Similar issue I found is https://github.com/open-telemetry/opentelemetry-ruby-contrib/issues/56
Share details about your runtime
Operating system details: Debian GNU/Linux aarch64 GNU/Linux
RUBY_ENGINE: "ruby"
RUBY_VERSION: "3.1.0"
RUBY_DESCRIPTION: "ruby 3.1.0p0 (2021-12-25 revision fb4df44d16) [aarch64-linux]"
Share a simplified reproduction if possible
opentelemetry-version
opentelemetry-api (1.2.2)
opentelemetry-common (0.19.6)
opentelemetry-instrumentation-action_pack (0.5.0)
opentelemetry-instrumentation-action_view (0.4.0)
opentelemetry-instrumentation-active_job (0.4.0)
opentelemetry-instrumentation-active_model_serializers (0.19.1)
opentelemetry-instrumentation-active_record (0.5.0)
opentelemetry-instrumentation-active_support (0.3.0)
opentelemetry-instrumentation-all (0.31.0)
opentelemetry-instrumentation-rack (0.22.1)
opentelemetry-instrumentation-rails (0.25.0)
opentelemetry-registry (0.3.0)
opentelemetry-sdk (1.2.0)
opentelemetry-semantic_conventions (1.10.0)

Thanks for opening this issue.
Would you be interested in opening a PR to add functionality that records handled errors on the rack spans?

Would love to. Just need to find right place to throw the exception.
It seems like from opentelemetry-instrumentation-rack call doesn't give any useful exception object like sinatra's sinatra.error

You may want to have a look at dd-trace-rb or other vendor specific implementations to see if they figured out some way of dealing with this scenario.
I assert that it's one of the Rails libraries that is capturing the exception and reporting it back to rack in some way.
I think that also varies in what mode the rails app is running in, e.g. in development ActionDispatch::DebugExceptions intercepts the raised exception and shows a debugging page.
Error handlers like airbrake or sentry may intercept them and handle them in a different way.
Application developers may also use rescue_from and choose to suppress the exception altogether and they will be difficult to intercept unless rails exposes a hook of some sort.
Please let us know what you find out and thank you again for being willing to help.

If the application is handling the exception (whether using rescue_from, rails mode or third party library), IMHO it's a lesser use case where we don't require the instrumentation to report it.  The main use case that got us looking into this is an unhandled exception, where we are able to show the HTTP status 5xx but unable to provide more details on the error.

resolved in https://github.com/open-telemetry/opentelemetry-ruby-contrib/pull/703


bug in header.php

Line number 48 of the Views/layout/header.php file should be replaced by:
<a href="<?= route_to('logout') ?>" class="btn btn-primary btn-block"><?= lang('boilerplate.global.close') ?>
you currently have an error in:  Logout
in the same file line number 41 should be replaced by:
<?= lang('boilerplate.user.fields.join') ?>
you currently have an error in: lang('user.join')

The error are you mean, not translated, right ?

fixed


use standard config dir path

Hello,
I was upgrading my setup with a new OS. And I had to copy every config file that were in ~, but I didn't want to copy everything in my ~.
I saw a .cointop hanging there and I kept it on the side as a reminder to propose this suggestion to move it to new standard of config dir. So in the future, I could just copy my ~/.config instead of cherry-picking through hundreds of dot files (I don't want to keep .cache for example)

Sorry, just found https://github.com/miguelmota/cointop/commit/3211bd7f5216b97c53dac77ec88f860d3a348d72
I guess I'll have to have the same logic.

@dolanor It's been on my todo list to default the config path to ~/.config/cointop/ . I''ll try to get this implemented in the next few days


An error occurred while initializing the youtube player.

I've added the following code in the RN project, but keep getting the 'An error occurred while initializing the youtube player.' error only on Android (emulator). On iphone it runs beautifully.
<YouTube
ref="youtubePlayer"
videoId="KVZ-P-ZI6W4" // The YouTube video ID
play={true}           // control playback of video with true/false
hidden={false}        // control visiblity of the entire view
playsInline={false}    // control whether the video should play inline
loop={false}          // control whether the video should loop when ended
apiKey={'API_KEY'}
style={{alignSelf: 'stretch', height: 300, backgroundColor: 'black', marginVertical: 10}}
/>
What could be the possible problems causing this error?
Thanks!

I'm also experiencing the same issue on RN0.36. I have followed the readme to the letter and recompiled the app and still have the issue.

same for me.. does it have anything to do with running it on emulator? Is it even possible to make it work in emulator?
#97

@ilyadoroshin I can't remember if I managed to get it to work in android emulator. I think that you need the YouTube app installed on the device for it to function on Android. I am not sure if you can install the app on emulator.
If you have a device to test on definitely try that instead. Otherwise the iOS simulator should work.

@morelazers YouTube app worked splendidly! Thanks!

add the below lines of code into your android AndroidManifest.xml file

add the below lines of code into your android AndroidManifest.xml file
  <queries>
    <intent>
      <action android:name="com.google.android.youtube.api.service.START" />
    </intent>
  </queries>

https://stackoverflow.com/a/66330541/15265413


[SR-15890] [Concurrency] swift_task_alloc crashes on Linux Armv7

Previous ID
SR-15890

Radar
None

Original Reporter
@colemancda

Type
Bug

Status
In Progress

Resolution

Environment
Swift 5.5.3 StdLib cross compiled for Armv7 (Debian 11)

Additional Detail from JIRA

Votes
0

Component/s
Standard Library

Labels
Bug

Assignee
@colemancda

Priority
Medium

md5: 7bf4f333a4be27a31c1af5ff268782fd

Issue Description:
Swift concurrency is crashing on 32-bit ARM.

Process 600680 launched: '/home/coleman/Developer/swift-armv7/build/swift-hello/armv7-unknown-linux-gnueabihf/debug/swift-hello' (arm)
swift-hello: /home/coleman/Developer/swift-armv7/downloads/swift-swift-5.6.1-RELEASE/stdlib/public/Concurrency/../runtime/StackAllocator.h:291: void *swift::StackAllocator<1000, &swift::TaskAllocatorSlabMetadata>::alloc(size_t) [SlabCapacity = 1000, SlabMetadataPtr = &swift::TaskAllocatorSlabMetadata]: Assertion `llvm::isAddrAligned(llvm::Align(alignment), allocation->getAllocatedMemory())' failed.
This version of LLDB has no plugin for the mipsassem language. Inspection of frame variables will be limited.
Process 600680 stopped

thread #1, name = 'swift-hello', stop reason = signal SIGABRT
frame #0: 0xf670bc66 libc.so.6`__libc_do_syscall at libc-do-syscall.S:47
(lldb) thread backtrace'
error: unknown command shorthand suffix: '''
(lldb) thread backtrace
thread #1, name = 'swift-hello', stop reason = signal SIGABRT

frame #0: 0xf670bc66 libc.so.6__libc_do_syscall at libc-do-syscall.S:47 frame #1: 0xf671aea0 libc.so.6__GI_raise at internal-signals.h:86:3
frame #2: 0xf671ae90 libc.so.6__GI_raise(sig=<unavailable>) at raise.c:48 frame #3: 0xf670b7a2 libc.so.6__GI_abort at abort.c:79:7
frame #4: 0xf6716140 libc.so.6__assert_fail_base(fmt="", assertion="llvm::isAddrAligned(llvm::Align(alignment), allocation->getAllocatedMemory())", file=0x00000000, line=291, function="void *swift::StackAllocator<1000, &swift::TaskAllocatorSlabMetadata>::alloc(size_t) [SlabCapacity = 1000, SlabMetadataPtr = &swift::TaskAllocatorSlabMetadata]") at assert.c:92:3 frame #5: 0xf67161ca libc.so.6__GI___assert_fail(assertion=0x00000000, file="", line=291, function="") at assert.c:101:3
frame #6: 0xf76814c0 libswift_Concurrency.soswift::StackAllocator<1000u, &(swift::TaskAllocatorSlabMetadata)>::alloc(this=0x004643d0, size=36) at StackAllocator.h:290:5 frame #7: 0xf768131a libswift_Concurrency.so::swift_task_alloc(size=32) at TaskAlloc.cpp:51:45
frame #8: 0x0043941c swift-hello$sIetH_yts5Error_pIegHrzo_TRTA at <compiler-generated>:0 frame #9: 0xf7675e66 libswift_Concurrency.soswift::runJobInEstablishedExecutorContext(job=0x004643a0) at Actor.cpp:238:11
frame #10: 0xf7676860 libswift_Concurrency.soswift_job_runImpl(job=0x004643a0, executor=ExecutorRef @ 0xfffef4c0) at Actor.cpp:1488:3 frame #11: 0xf767681e libswift_Concurrency.so::swift_job_run(job=0x004643a0, executor=ExecutorRef @ 0xfffef4e0) at CompatibilityOverrideConcurrency.def:76:1
frame #12: 0x00439308 swift-hellomain at Hello.swift:0 frame #13: 0xf670ba20 libc.so.6__libc_start_main(main=(swift-hellomain), argc=1, argv=0xfffef664, init=<unavailable>, fini=(swift-hello__libc_csu_fini + 1), rtld_fini=(ld-2.31.so_dl_fini + 1 at dl-fini.c:30:1), stack_end=0xfffef664) at libc-start.c:308:16 frame #14: 0x004373ac swift-hello_start + 52

@buttaface is this reproducible on Android? It's only reproducible for me with debug builds on Swift 5.5 - 5.6.

I don't build the debug stdlib for armv7 unless I'm debugging something in particular, which I haven't been lately. I will build it and let you know.

Not reproducible with Swift 5.7.1 built with -RA.


Error 10061 - No connection could be made because the target machine actively refused it

I have config TOR in linux with the following information:
tor --RunAsDaemon 1 --CookieAuthentication 0 --HashedControlPassword "xxx" --ControlPort 8541 --PidFile tor10.pid --SocksPort 40612 --DataDirectory data2/new/tor10 --SOCKSListenAddress <IP_ADDRESS>:40612 --ControlListenAddress <IP_ADDRESS>:8541
I have tested with other machine (<IP_ADDRESS>): nc <IP_ADDRESS> 8541, and it's OK.
But when I using this extension in PHP, i got the error:
exception 'TorControl\Exception\IOError' with message '10061 - No connection could be made because the target machine actively refused it.
' in my_web_path\vendors\TorControl\TorControl.php:176

It looks more like a problem in the network configuration than a PHP problem.

No, not about network problem.
I see problem is in your example:
$tc = new TorControl\TorControl(
array(
'server' => 'localhost',
'port'   => 9051,
'password' => 'MySecr3tPassw0rd',
'authmethod' => 1
)
);
But at src/TorControl.php, function connect:
$this->socket = @fsockopen($this->options['hostname'], $this->options['port'], $errno, $errstr, $this->options['timeout']);
It has confused about 'server' and 'hostname'.
I have changed to:
$tc = new TorControl\TorControl(
array(
'hostname' => 'localhost',
'port'   => 9051,
'password' => 'MySecr3tPassw0rd',
'authmethod' => 1
)
);
and I works fine.

Ok so it's a doc problem :) Thank you I'll update the doc.

Have you updated the doc?
I am also having an error

I believe this can be considered closed as of 10d5627928e46e4d2897d8dc2bd80cd13dec7e68.


terminal prompts disabled

Describe the bug
The original issue was https://github.com/argoproj-labs/argocd-image-updater/issues/621 but that's been closed. The newest release does not panic anymore, but as indicated in that now closed issue it left it's place to a new problem :
time="2024-05-29T15:47:24Z" level=error msg="`git fetch origin --tags --force` failed exit status 128: error: cannot run argocd: No such file or directory\nfatal: could not read Username for '<my git repo>': terminal prompts disabled" execID=d3b0c

Downgrading back to 0.12 fixes the issue.
Version
v0.13.1

I'm having the same problem with original issue #621 in v0.13, after update to v0.13.1, I get the "terminal prompts disabled" error.

@jannfis reworked this part completely here, but we planned release it as part of v0.14 , If issue still exists, probably we will cherry pick this change earlier . @jannfis thoughts on it ?

@pasha-codefresh It's a big change, and imho should go into 0.14. We could go ahead and release a 0.14 soon, though. I do not see any issue with that :)

same here. automatic upgrades are completely broken for me in v0.13.1.

Since https://github.com/argoproj-labs/argocd-image-updater/pull/726 is merged, I thought I could build and test the latest master however I ended up with these errors still. I am using GitHub App creds.
Am I missing something alongside changes in that PR? @jannfis  / @pasha-codefresh could you help?

Image Updater Logs
level=trace msg="processing app 'web2' of type 'Helm'" application=web2
level=info msg="Starting image update cycle, considering 1 annotated application(s) for update"
level=debug msg="Processing application web2"
level=debug msg="Considering this image for update" alias=argo-play application=web2 image_name=<redacted>/argo-play image_tag=v1 registry=
level=debug msg="Using no version constraint when looking for a new tag" alias=argo-play application=web2 image_name=<redacted>/argo-play image_tag=v1 registry=
level=trace msg="No sort option found" image_alias=argo-play image_name=<redacted>/argo-play registry_url=
level=trace msg="No match annotation found" image_alias=argo-play image_name=<redacted>/argo-play registry_url=
level=trace msg="No ignore-tags annotation found" image_alias=argo-play image_name=<redacted>/argo-play registry_url=
level=trace msg="Using runtime platform constraint linux/arm64" image_alias=argo-play image_name=<redacted>/argo-play registry_url=
level=trace msg="No pull-secret annotation found" image_alias=argo-play image_name=<redacted>/argo-play registry_url=
level=trace msg="Performing HTTP GET https://registry-1.docker.io/v2/<redacted>/argo-play/tags/list"
level=trace msg="List of available tags found: [v1 v2]" alias=argo-play application=web2 image_name=<redacted>/argo-play image_tag=v1 registry=
level=trace msg="Finding out whether to consider v1 for being updateable" image="<redacted>/argo-play:v1"
level=trace msg="Finding out whether to consider v2 for being updateable" image="<redacted>/argo-play:v1"
level=debug msg="found 2 from 2 tags eligible for consideration" image="<redacted>/argo-play:v1"
level=info msg="Setting new image to <redacted>/argo-play:v2" alias=argo-play application=web2 image_name=<redacted>/argo-play image_tag=v1 registry=
level=debug msg="target parameters: image-spec= image-name=image.repository, image-tag=image.tag" application=web2 image=<redacted>/argo-play
level=info msg="Successfully updated image '<redacted>/argo-play:v1' to '<redacted>/argo-play:v2', but pending spec update (dry run=false)" alias=argo-play application=web2 image_name=<redacted>/argo-play image_tag=v1 registry=
level=debug msg="Using commit message: [skip ci] build: automatic update of web2\n"
level=info msg="Committing 1 parameter update(s) for application web2" application=web2
level=info msg="Initializing https://github.com/srihas619/argocd-local to /tmp/git-web22660430708"
level=info msg="git fetch origin --tags --force --prune" dir=/tmp/git-web22660430708 execID=b2f57
level=error msg="`git fetch origin --tags --force --prune` failed exit status 128: error: cannot run argocd: No such file or directory\nfatal: could not read Username for 'https://github.com': terminal prompts disabled" execID=b2f57
level=info msg=Trace args="[git fetch origin --tags --force --prune]" dir=/tmp/git-web22660430708 operation_name="exec git" time_ms=238.79500000000002
level=error msg="Could not update application spec: `git fetch origin --tags --force --prune` failed exit status 128: error: cannot run argocd: No such file or directory\nfatal: could not read Username for 'https://github.com': terminal prompts disabled" application=web2
level=info msg="Processing results: applications=1 images_considered=1 images_skipped=0 images_updated=0 errors=1"

Thank you!

I am experiencing the same issue on master using GitHub App creds

I'm tracing through the code and I'm bit confused at the error.
```time="2024-06-03T22:03:07Z" level=error msg="git fetch origin --tags --force --prune failed exit status 128: error: cannot run argocd: No such file or directory\nfatal: could not read Username for 'https://github.com': terminal prompts disabled" execID=e7a4a

Why does a call to `git fetch` try to run argocd? Is there some sort of git hook being executed?

https://github.com/argoproj-labs/argocd-image-updater/blob/master/pkg/argocd/git.go#L159

For some reason release 0.13.1 works for me, so looks like #726 is specifically what caused this issue 🤷

Found the issue and have a fix up.

I think this bug hits only if you use an HTTPS based repository configuration. @Sovietaced, are you by chance using SSH connected repositories?

I think this bug hits only if you use an HTTPS based repository configuration. @Sovietaced, are you by chance using SSH connected repositories?

I am using repositories setup with GitHub app credentials with an HTTPS URL.

Is there any workaround for that?
Annotation does not work anymore: argocd-image-updater.argoproj.io/write-back-method: git:secret:argocd/git-creds

Is this fixed anyway? Running the latest build I'm still getting:
level=error msg="Could not update application spec: git fetch origin --tags --force --prune failed exit status 128: time=\"2024-06-18T17:51:35Z\" level=fatal msg=\"ARGOCD_GIT_ASKPASS_NONCE is not set\"\nerror: unable to read askpass response from '/usr/local/bin/argocd-image-updater'\nfatal: could not read Username for 'https://github.xxxx': terminal prompts disabled" application=test-app
Annotations:
  annotations:
   argocd-image-updater.argoproj.io/image-list: app=myrepo/app
   argocd-image-updater.argoproj.io/app.allow-tags: regexp:^[0-9]+.[0-9]+.[0-9]+-[0-9a-f]{7}$
   argocd-image-updater.argoproj.io/app.helm.image-name: app.image.repository
   argocd-image-updater.argoproj.io/app.helm.image-tag: app.image.tag
   argocd-image-updater.argoproj.io/write-back-method: git:secret:argocd-image-updater/git-creds
   argocd-image-updater.argoproj.io/git-repository: https://github.xxxxx
   argocd-image-updater.argoproj.io/write-back-target: "helmvalues:../../values.yaml"
   argocd-image-updater.argoproj.io/git-branch: master:image-updater{{range .Images}}-{{.Name}}-{{.NewTag}}{{end}}

Thanks for testing and reporting, @alexismaior. Will dig into again.

Yep. Tested with both HTTPS and SSH git credentials and the image updater was able to write back to git. Thanks, folks, for working on this.

Are there any plans to release v0.13.2 in the short term with this fix? :D

Are there any plans to release v0.13.2 in the short term with this fix? :D

See https://github.com/argoproj-labs/argocd-image-updater/pull/748#issuecomment-2208757523


Doesnt work "/play"

Doesnt work "/play" command https://service.crazypanda.ru/v/monosnap/2018-12-17-15-00-00-igk4w.png
musicbot.log

Update your dependencies using the update script.

How i need to do that?

the update batch script
just double click it

https://service.crazypanda.ru/v/monosnap/2018-12-17-15-06-44-ywdhv.png This error

The actual error would be above that.

The actual error would be above that.

https://service.crazypanda.ru/v/monosnap/2018-12-17-15-11-19-qloha.png https://service.crazypanda.ru/v/monosnap/2018-12-17-15-12-30-l7jdr.png

Uninstall python and use this version. Remember to check Add to Path.
https://www.python.org/ftp/python/3.5.4/python-3.5.4.exe

Uninstall python and use this version. Remember to check Add to Path.
https://www.python.org/ftp/python/3.5.4/python-3.5.4.exe

i have 3.7 python, still need to reinstall?

Yes. Uninstall it and install the version I linked.

Yes. Uninstall it and install the version I linked.

Last time i have issue - https://github.com/Just-Some-Bots/MusicBot/issues/1741 see that - https://service.crazypanda.ru/v/monosnap/2018-12-17-15-18-38-zzdx8.png wtf?

That’s why they instructed you to use 3.5.4.

That’s why they instructed you to use 3.5.4.

They instructed me to use python 3.7!!!! https://service.crazypanda.ru/v/monosnap/2018-12-17-15-21-46-xdlkk.png

It's a checkbox in the installer, I'm telling you to remember to check it.

Thanks a lot! Works now, Have a nice day!

Normally I told people (that use outdated Python) to use 3.7 because that's the version that the bot is maintained with. But in case that 3.7 doesn't work I also would instruct them to use 3.5.4 instead of 3.7. 3.7 do have habits of breaking on some machine but I generally encourage people to use up-to-date software hence I said 'update to 3.7' to you in that issue.

Normally I told people (that use outdated Python) to use 3.7 because that's the version that the bot is maintained with. But in case that 3.7 doesn't work I also would instruct them to use 3.5.4 instead of 3.7. 3.7 do have habits of breaking on some machine but I generally encourage people to use up-to-date software hence I said 'update to 3.7' to you in that issue.

Got it! Thanks!


Reload page if game fails to load

Sometimes after an automatic refresh, the servers error out on providing a page or script and the game hangs until the next automatic refresh. This causes the script to reload the page again if the game is not functional within 30 seconds.
This may need further adjustments for morning lag compensation when the servers reset as that will probably have everyone's game lagging in unexpected ways.

This feature really should be called "boot to the head".

I've tracked the root of this problem down in Valve's code, if only I knew how to submit a pull request to them! It may be possible for this script to patch Valve's code, I'm looking into that now so hold fire on this PR.

@EdGruberman Here is a better way to do it: https://github.com/wchill/steamSummerMinigame/pull/154

#154 was merged in #161. Closing.


Scott Felske

Latest attempt to submit cucumber calculator assignment

There is 2 versions of subtraction_steps.rb. The one in the features folder should not be there. It is leading to an ambiguous step definition.


Prepare for next SMP release with Mobiliser 5.6.

 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.


add signature verification and unit tests for AWS plugin

Release note:

NONE

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

Test name
Commit
Details
Rerun command

prow/auth-presubmit.sh
23bf9218c8d78b9d83b59c21907988d7038de6c1
link
/test auth-presubmit

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.

/lgtm
/approve


Contributing guidelines

Most repositories contain either:

A Contributing section in the README, or
A Contributing.md file

It would be beneficial to have one here as well.

I would slightly extend it — it would be good to fit into GitHub's vision of a well-defined repo by reaching all Community Standards here: https://github.com/datafold/data-diff/community.

I feel this is done. Feel free to re-open or make suggestions.


Fix variable definition

Before this commit, synchronous_master is defined inside
try-block so if any error happens before the definition and args.sync is true,
"ReferenceError: synchronous_master is not defined" is raised
in the finally-block.
You can reproduce this error when you run python spawn_npc.py --sync without good connection to the server (like RuntimeError: rpc::timeout: Timeout of 10000ms while connecting to <IP_ADDRESS>:2000)

Description

Described above (and in the commit message too)
Where has this been tested?

Platform(s): ...Ubuntu 16
Python version(s): ... python 2.7.13
Unreal Engine version(s): ... 4.24

I am pretty sure this is OS independent.
Possible Drawbacks
None.

This change is

Thanks for the fix shiba24, we are going to merge this in master.
Kind regards