text:
Introduce runtime2/routing.

Introduces runtime2/routing, a data structure for handling resolution of requests to handlers.

/lgtm

source: gharchive/pull-request

authors: andraxylia ozevren

repo: istio/istio

license_type: permissive

license_source: github-api


text:
Automator: update common-files@master in istio/istio@master

Generated by Automator - 2021-01-21T00:01:48+00:00

/retest

/retest

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

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-pilot-multicluster-tests_istio

integ-multicluster-k8s-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-multicluster-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-security-multicluster-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-pilot-multicluster-tests_istio

integ-multicluster-k8s-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-multicluster-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-security-multicluster-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-security-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-pilot-multicluster-tests_istio

integ-multicluster-k8s-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-telemetry-mc-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-security-multicluster-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-security-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-pilot-multicluster-tests_istio

integ-multicluster-k8s-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-telemetry-mc-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-security-multicluster-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-security-multicluster-tests_istio

integ-multicluster-k8s-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-pilot-multicluster-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-security-multicluster-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-security-multicluster-tests_istio

integ-multicluster-k8s-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-pilot-multicluster-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-multicluster-k8s-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-pilot-multicluster-tests_istio

integ-security-multicluster-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-security-multicluster-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-multicluster-k8s-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-pilot-multicluster-tests_istio

integ-security-multicluster-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-security-multicluster-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-telemetry-mc-k8s-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-pilot-multicluster-tests_istio

integ-security-multicluster-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-security-multicluster-tests_istio

integ-multicluster-k8s-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-multicluster-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-telemetry-mc-k8s-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-pilot-multicluster-tests_istio

integ-security-multicluster-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-security-multicluster-tests_istio

integ-multicluster-k8s-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-multicluster-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-multicluster-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-pilot-multicluster-tests_istio

integ-security-multicluster-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-security-multicluster-tests_istio

integ-multicluster-k8s-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-telemetry-mc-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-multicluster-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-pilot-multicluster-tests_istio

integ-security-multicluster-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-security-multicluster-tests_istio

integ-multicluster-k8s-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-telemetry-mc-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-multicluster-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-pilot-multicluster-tests_istio

integ-multicluster-k8s-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-multicluster-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-security-multicluster-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-multicluster-tests_istio
8394e0a4c7c57af20a24f1d4ed1da9bf3798af07
link
/test integ-pilot-multicluster-tests_istio

integ-multicluster-k8s-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-multicluster-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-security-multicluster-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-multicluster-k8s-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-multicluster-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-security-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-pilot-multicluster-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-multicluster-k8s-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-multicluster-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-multicluster-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-security-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-pilot-multicluster-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-multicluster-k8s-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-multicluster-k8s-tests_istio

integ-security-multicluster-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-security-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
0004a552ac61c0355c08aa02611e5c0683c5a9bb
link
/test integ-telemetry-mc-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-multicluster-k8s-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-multicluster-k8s-tests_istio

integ-security-multicluster-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-security-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
0004a552ac61c0355c08aa02611e5c0683c5a9bb
link
/test integ-telemetry-mc-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-multicluster-k8s-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-multicluster-k8s-tests_istio

integ-security-multicluster-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
0004a552ac61c0355c08aa02611e5c0683c5a9bb
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
0004a552ac61c0355c08aa02611e5c0683c5a9bb
link
/test integ-pilot-multicluster-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-multicluster-k8s-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-multicluster-k8s-tests_istio

integ-security-multicluster-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
0004a552ac61c0355c08aa02611e5c0683c5a9bb
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
0004a552ac61c0355c08aa02611e5c0683c5a9bb
link
/test integ-pilot-multicluster-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-security-multicluster-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
0004a552ac61c0355c08aa02611e5c0683c5a9bb
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
0004a552ac61c0355c08aa02611e5c0683c5a9bb
link
/test integ-pilot-multicluster-tests_istio

integ-multicluster-k8s-tests_istio
0004a552ac61c0355c08aa02611e5c0683c5a9bb
link
/test integ-multicluster-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-security-multicluster-tests_istio
261cfac6058ee64ce2ae5debb04c6f237ea66f85
link
/test integ-security-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
0004a552ac61c0355c08aa02611e5c0683c5a9bb
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
0004a552ac61c0355c08aa02611e5c0683c5a9bb
link
/test integ-pilot-multicluster-tests_istio

integ-multicluster-k8s-tests_istio
0004a552ac61c0355c08aa02611e5c0683c5a9bb
link
/test integ-multicluster-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-telemetry-mc-k8s-tests_istio
0004a552ac61c0355c08aa02611e5c0683c5a9bb
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
0004a552ac61c0355c08aa02611e5c0683c5a9bb
link
/test integ-pilot-multicluster-tests_istio

integ-multicluster-k8s-tests_istio
0004a552ac61c0355c08aa02611e5c0683c5a9bb
link
/test integ-multicluster-k8s-tests_istio

integ-security-multicluster-tests_istio
0004a552ac61c0355c08aa02611e5c0683c5a9bb
link
/test integ-security-multicluster-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-telemetry-mc-k8s-tests_istio
0004a552ac61c0355c08aa02611e5c0683c5a9bb
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
0004a552ac61c0355c08aa02611e5c0683c5a9bb
link
/test integ-pilot-multicluster-tests_istio

integ-multicluster-k8s-tests_istio
0004a552ac61c0355c08aa02611e5c0683c5a9bb
link
/test integ-multicluster-k8s-tests_istio

integ-security-multicluster-tests_istio
0004a552ac61c0355c08aa02611e5c0683c5a9bb
link
/test integ-security-multicluster-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 test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio
8bb1d3ad821e3c2e8095bc12b4c42ef69292aea6
link
/test integ-telemetry-mc-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 test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio
8bb1d3ad821e3c2e8095bc12b4c42ef69292aea6
link
/test integ-telemetry-mc-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.

authors: ericvn istio-testing


text:
Enable building for base images

Now for DOCKER_V2_BUILDER, it does not support the explicit building for
base images, for example, when building with
make dockerx.app_sidecar_base_ubuntu_xenial
it would show some error information for the wrong VM_IMAGE_NAME and
VM_IMAGE_VERSION, now we just fix it here.
And add other base images in the istio-docker.mk in the default list too.
Signed-off-by: trevor.tao trevor.tao@arm.com
Please provide a description of this PR:

Hi @TrevorTaoARM. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

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.

/ok-to-test

authors: TrevorTaoARM ericvn istio-testing


text:
Fix the rbac sample files for Istio 1.0.

The user field is comparing to the original peer certificate which would have a "spiffe://" prefix for the identity.
For #6377.
/cc @liminw

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: yangminzhu
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: vadimeisenbergibm
Assign the PR to them by writing /assign @vadimeisenbergibm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

samples/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

authors: istio-testing yangminzhu


text:
Add contents of install/ansible to release script

Fixes: #4359, istio/issues#223

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: geoand
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: chxchx
Assign the PR to them by writing /assign @chxchx in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

release/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @geoand. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

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.

/assign @costinm

@costinm this went through a long review process in https://github.com/istio/istio/pull/4623 and was approved - however for some reason never merged.  Can you take a look?
Cheers
-steve

/ok-to-test

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
da4fa3a67381de83d64878fc9572264a7fa2fa67
link
/test istio-pilot-e2e-envoyv2-v1alpha3

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

/test istio-pilot-e2e-envoyv2-v1alpha3

authors: geoand istio-testing sdake


text:
Better document developer workflow and options.

Things we need to augment documentation on:

how to use bazel to generate go deps
basic IDE usage
debugging (local and remote)
general best practices.

Nice issue tracker id 🥇
@douglas-reid would you expand on "use bazel to generate go deps"?  I have some docs i'm sorting out locally before submitting a PR to add CentOS support to Istio.  These might touch on the generate go deps and general best practices areas.  I use the makefiles, rather than the technique recommended by @ZackButcher, however, I've honed in on one workflow for local development without waiting for CI/CD to pop out a dependent set of images (which is currently undocumented).
What category above would that fit into?  General best practices?

@sdake this was an issue I filed during the community call on thursday. someone requested that we better document how to develop with go tooling, etc.  so, by "use bazel to generate go deps", i meant we should clearly spell out what happens when running bazel build //... and how the generated files from such an action are symlinked into the mixer repo dirs and vendor/.
A developer's guide is being polished at the moment and that should help a bit with some of this as well.
It sounds like you are using some of the cloud builder stuff and doing testing/debugging/validation with images. I use a similar (undocumented) workflow, and I believe @ZackButcher has been using (or at least, used to use) a workflow based on pushing images to a local repository (which, iirc, is/was documented somewhere).
Thanks for taking a shot at documenting that flow!

source: gharchive/issue

authors: douglas-reid sdake

repo: istio/mixer


text:
Move away from HandlerConfig.

Here's what the new model looks like. If this is reasonable, I'll rip through the adapters.
Release note:

This change is

/lgtm

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

Test name
Commit
Details
Rerun command

prow/mixer-presubmit.sh
8c23327a533c043a9361e72a551a689a1f8d893d
link
/test mixer-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.

/test all

authors: geeknoid guptasu istio-testing


text:
Implementierung von Referendumvorlagen laden

Akzeptanzkriterien

[ ] für eine Wahl und einen Wahlbezirk können Referendumsvorlagen geladen werden
[ ] sind lokal keine Daten vorhanden werden diese Importiert
[ ] Zugriffsrechte sind gepflegt
[ ] Erstellung Swagger-Beschreibung
[ ] DB-Schema mittels Flyway aktualisiert

Umsetzungshinweise

Controller -> Service -> Repo

#144 als Abhängigkeit aufgenommen um die Erfahrung mit der Anbindung zum Fremdservice zu sammeln. Methodisch und vom Datenmodell sind #143 und #144 nahezu identisch.

repo: it-at-m/Wahllokalsystem

license: MIT


text:
[test] mock_process에서 전체 process 정보 가리기

현재 mock_process 에서 process table에 실제 process를 가지고 있습니다.
하지만 이 경우 전체 네트워크에 대한 정보를 프로세스가 가지고 있어 이를 네트워크 매니저가 담당하게 하여
프로세스는 다른 프로세스들에 대한 정보를 가지지 않도록 해야 합니다.
#553

진행중입니다.

repo: it-chain/engine


text:
Pbft state api refactory

resolved: #886 #973
Prevote 과정을 끝내기 전 Precommit 메시지를 모두 받아, Prevote 과정이 끝난 후 Precommit을 진행하지 않는 문제

어벤져스 테스트 필요

#992


text:
good start

I was unable to use this as is. There are a lot of hard coded urls in the building of the container and seems for everything to run on one host
Maybe if I get time I can look into fixing the containers. but eod the container names should be vars and not hard coded.

Hi @stephenc01,
thanks for your feedback.

There are a lot of hard coded urls in the building of the containe

Could you please add a list of URLs that are hardcoded? Our idea was, to make all hostnames adjustable through the environment file. For example:
OITC_NAEMON_HOSTNAME=naemon
SE_GRAPHITE_ADDRESS=carbon-c-relay
CCR_CARBON_CACHE_1=carbon-cache1:2003

Could be possible that we have missed one or two.
I have build a distributed setup using Docker Swarm, you can find my notes about this here: https://gist.github.com/nook24/75b8a07d19989de6fcc122c78044ce82

Happy new Year @RedBeardDotDev - thanks for reporting.
I found a few places where hardcoded hostnames where used instead of dynamic values from the openitcockpit.env file.
I nuked my docker test environment and pushed a new nightly version. I also prefixed all my containers with oitc- and I'm using this openitcockpit.env file
MYSQL_ROOT_PASSWORD=root_password
MYSQL_DATABASE=openitcockpit
MYSQL_USER=openitcockpit
MYSQL_PASSWORD=openitcockpit_password
MYSQL_HOST=oitc-mysql
OITC_REDIS_HOST=oitc-redis
OITC_GEARMAN_ADDRESS=oitc-gearmand
OITC_GRAPHITE_WEB_ADDRESS=oitc-graphite-web
OITC_GRAFANA_ADMIN_PASSWORD=bGsPMxURCjg4esgJ
OITC_GRAFANA_URL=http://oitc-grafana:3033
OITC_PUPPETEER_ADDRESS=http://oitc-puppeteer:8084/
OITC_NAEMON_HOSTNAME=oitc-naemon
OITC_STATUSENGINE_WORKER_HOSTNAME=oitc-statusengine-worker
OITC_MAIL_RELAYHOST=oitc-postfix
MOD_GEARMAN_GEARMAN_SERVER=oitc-gearmand:4730
MOD_GEARMAN_WORKER_GEARMAN_SERVER=oitc-gearmand:4730
SE_GEARMAN_ADDRESS=oitc-gearmand
SE_REDIS_ADDRESS=oitc-redis
SE_MYSQL_HOST=oitc-mysql
SE_GRAPHITE_ADDRESS=oitc-carbon-c-relay
SE_BROKER_GEARMAN_SERVER=oitc-gearmand:4730
VICTORIA_METRICS_HOST=oitc-victoriametrics
GF_SECURITY_ADMIN_PASSWORD=bGsPMxURCjg4esgJ
CCR_CARBON_CACHE_1=oitc-carbon-cache1:2003
CCR_CARBON_CACHE_2=oitc-carbon-cache2:2003

[Ubuntu][15:10]root@dziegler-docker~/openITCOCKPIT-ee-docker# docker compose config --services
oitc-carbon-c-relay
oitc-carbon-cache1
oitc-carbon-cache2
oitc-checkmk
oitc-gearmand
oitc-grafana
oitc-graphite-web
oitc-mod_gearman_worker
oitc-mysql
oitc-naemon
oitc-redis
oitc-openitcockpit
oitc-postfix
oitc-puppeteer
oitc-statusengine-worker
oitc-victoria-metrics

Would be good if you could also give it a shot

Thanks @nook24 .. I don't have a ton of time (busy moving house) but I've spun up a quick stack with the :latest images. It's looking pretty good so far.
The only message I'm getting is from oitc-naemon:
oitc-naemon               | 2024-01-02 23:23:59,663 INFO exited: naemon (exit status 1; not expected)
oitc-naemon               | 2024-01-02 23:24:00,665 INFO spawned: 'naemon' with pid 11860
oitc-naemon               | 2024-01-02 23:24:00,724 INFO exited: naemon (exit status 1; not expected)
oitc-naemon               | 2024-01-02 23:24:02,726 INFO spawned: 'naemon' with pid 11879
oitc-naemon               | 2024-01-02 23:24:03,786 INFO success: naemon entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

That might be something else, so I'm not too worried about it.

You need to use the :nightly tag for (at least) this 3 images:
openitcockpit/naemon:nightly
openitcockpit/victoria-metrics:latest
openitcockpit/openitcockpit-ce:nightly

Also please make sure you have set all environment variables from this comment https://github.com/it-novum/openITCOCKPIT-ce-docker/issues/1#issuecomment-1874075900 in your openitcockpit.env - as some of them are completely new.
oitc-naemon               | 2024-01-02 23:23:59,663 INFO exited: naemon (exit status 1; not expected)
oitc-naemon               | 2024-01-02 23:24:00,665 INFO spawned: 'naemon' with pid 11860
oitc-naemon               | 2024-01-02 23:24:00,724 INFO exited: naemon (exit status 1; not expected)
oitc-naemon               | 2024-01-02 23:24:02,726 INFO spawned: 'naemon' with pid 11879
oitc-naemon               | 2024-01-02 23:24:03,786 INFO success: naemon entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

This is the Naemon process which is crashing right away - not so good. That's probably because you are using the current stable version (latest tag) where the environment variable was missing.
As soon as you switch to nightly, this should be fixed.

Hi @nook24 ,
I'm having the same issue where openitcockpit service doesn't connect to mysql.
The content of the file /opt/openitc/etc/mysql/mysql.cnf is correct and I can see the same values I put in my openitcockpit.env.
How can I make this stack working?
Thanks, ENx

@vic-pic
what values of  openitcockpit.env did you change? also what platform are you on amd64 (Desktop Intel or AMD CPU) or arm64 (like Raspberry Pi)?

Hi @nook24 ,
I changed the following variables:

MYSQL_ROOT_PASSWORD
MYSQL_PASSWORD
OITC_ADMIN_EMAIL
OITC_ADMIN_PASSWORD
OITC_ADMIN_FIRSTNAME
OITC_ADMIN_LASTNAME
OITC_GRAFANA_ADMIN_PASSWORD
GF_SECURITY_ADMIN_PASSWORD
CC_CARBON_STORAGE_SCHEMA
CC_WHISPER_FALLOCATE_CREATE

I'm on an amd64 platform on a remote server.
Thanks, ENx

I was able to reproduce this.
Changing the MYSQL_ variables will currently break the compose. I have create a new issue for this so we can fix this:
https://github.com/it-novum/openITCOCKPIT-ce-docker/issues/8

repo: it-novum/openITCOCKPIT-ce-docker


text:
[UBS_Prod. Orders_Admin] The orders table doesn't support the width change of every column

Environment: Mac OS Ventura 13.3.1 (a), browser Safari Version 16.4 (18615.1.26.110.1)..
Reproducible: always.
Build found: 06.06.2023
Preconditions

The User should be logged in as a Super Admin.
Orders page is opened.

Steps to reproduce

Go to https://www.pick-up.city/#/ubs-admin/orders;
Click the mouse on the border of any column and try to move it left/right

Actual result
The order table column is dragged to another position.
https://github.com/ita-social-projects/GreenCity/assets/128076020/4842db39-a7bb-4ef1-acef-e29004b806d8
Expected result
The width of the order table column changes, while the column itself does not change its position.
User story and test case links
E.g.: "User story #2536

We change the width with the column's borders, not the headers. The header swapping changes the position as on the video
https://github.com/ita-social-projects/GreenCity/assets/101433204/e314c976-14eb-4caf-91cc-c992b6be7409

repo: ita-social-projects/GreenCity


text:
Operazione non effettuabile

Ambiente di Test
ID operazione ANPR : 18973988
tentando di fare l'operazione 18973988 ci compare l'errore 999 Operazione non effettuabile
Potete verificare?
Grazie

Salve, dovrebbe essere possibile riprovare.

Ora funziona,
Grazie

authors: SAlberto mttfranci

repo: italia/anpr


text:
[EN024 EN092] errore di validazione del file di subentro per le convivenze

Durante la messa a punto e la creazione del file di subentro, ricevo una serie di errori nella validazione del file, da parte del tool scaricato dalla web-app, in "Strumenti di supporto", dalla sezione: "Validazione dei file di subentro".
Ricevo diverse segnalazioni, per cui non ne comprendo la ragione. Vi allego qui di seguito il file del subentro, contenente una sola convivenza (ho provveduto ad offuscare i dati reali pur lasciandoli "realistici").
In particolare mi viene segnalato:

TYPE:EN024,LEVEL:errore,MESSAGE:Totale schede convivenza 1 dichiarato per l'intera fornitura 0 incongruente con quello calcolato @
TYPE:ES092,LEVEL:errore,MESSAGE:Soggetto senza scheda famiglia/convivenza associata[[soggetto-APR:34326]]
TYPE:ES092,LEVEL:errore,MESSAGE:Soggetto senza scheda famiglia/convivenza associata[[soggetto-APR:34332]]

Come potete vedere dal file (in allegato, rinominato ".txt" per uplodarlo, in realtà è un file XML), entrambi i soggetti sono collegati alla convivenza riepilogata nella parte finale del file, non vi è ragione (apparentemente, per me) per cui non venga individuato il collegamento tra soggetto e famiglia/convivenza per cui non riesco a comprendere e poi risolvere la segnalazione ES092. La stessa cosa per la segnalazione ES024.
Vi pregherei di darmi indicazioni a riguardo. Buona giornata e buon lavoro, Carmine Paternoster
sub1.txt

Salve il file che avete postato aveva problemi diversi da quello voi descritti (probabilmente in fatto all'editing manuale successivo), ad esempio un campo senzaNome impostato con un nome
CATERINA
Una volta corretti gli errori formali XML è stato validato senza problemi.
Eccolo :
000000_SUBAPR_1_1_1.gz
Alcune possibili cause delle segnalazioni potrebbero essere :

Avete indicato come file da validare una cartella, in quel caso tutti i file contenuti sono stati validati come una unica fornitura e le quadrature potrebbero essere saltate (vi consigliamo di creare una cartella con i soli file della/e forniture da validare e rilancaire il tool putnando a tale cartella).
Non avete usato la versione piu recente del tool (che è disponibile dagli strumenti di supporto in ambiente di test comuni).

Se dopo queste verifiche ancora il file dovesse presentare dei problemi, scriveteci di nuovo.
Saluti
Assistenza ANPR

Salve, grazie innanzitutto per la risposta e per la disponibilità, ho purtroppo commesso degli errori durante l'editing per l'offuscamento dei dati, ma al di la di quest'aspetto, pur provando a validare il file da voi postato mi restituisce i seguenti errori:
[2019-07-26 09:13:41,448] - classe: - metodo: - esito KO, errori fatali : 0 , errori : 5
[2019-07-26 09:13:41,448] - classe: - metodo: - TYPE:EN009,LEVEL:errore,MESSAGE:Il formato del file APR decompresso non e' XML[cvc-complex-type.2.3: l'elemento "famiglie" non deve avere [children] di tipo carattere perché il tipo di contenuto è di soli elementi.],ROW:263,COLUMN:41
[2019-07-26 09:13:41,448] - classe: - metodo: - TYPE:EN023,LEVEL:errore,MESSAGE:Totale schede convivenza 1 dichiarato nel file 077014_SUBAPR_1_1_1.gz incongruente con quello calcolato 0
[2019-07-26 09:13:41,448] - classe: - metodo: - TYPE:EN024,LEVEL:errore,MESSAGE:Totale schede convivenza 1 dichiarato per l'intera fornitura 0 incongruente con quello calcolato @
[2019-07-26 09:13:41,448] - classe: - metodo: - TYPE:ES092,LEVEL:errore,MESSAGE:Soggetto senza scheda famiglia/convivenza associata[[soggetto-APR:34326]]
[2019-07-26 09:13:41,448] - classe: - metodo: - TYPE:ES092,LEVEL:errore,MESSAGE:Soggetto senza scheda famiglia/convivenza associata[[soggetto-APR:34332]]
Il tool di subentro (oltre ad avere nel nome della cartella 5.3.1 riporta anche nel pom.xml 5.3.1 che è la versione a cui facevo riferimento). Il tool l'ho scaricato stamattina e continua a darmi gli errori sopra elencati sul file da voi postato

Potreste provare in primo luogo a risolvere gli errori di tipo EN009?
Questi sono sintomo di un problema formale nell'xml rispetto agli XSD distribuiti.
Quindi è possibile che gli altri errori ne siano una conseguenza.
Ad esempio per l'errore :
[2019-07-26 09:13:41,448] - classe: - metodo: - TYPE:EN009,LEVEL:errore,MESSAGE:Il formato del file APR decompresso non e' XML[cvc-complex-type.2.3: l'elemento "famiglie" non deve avere [children] di tipo carattere perché il tipo di contenuto è di soli elementi.],ROW:263,COLUMN:41
Potete verificare se alla riga 263, colonna 41 forse un valore è stato messo esternamente agli elementi?
Ad esempio se nel file di prova che vi abbiamo girato ieri modifichiamo un blocco convivenza in questo modo :
        `<convivenza>**11134C**`
        `    <idFamConvComune>111</idFamConvComune>`
        `    <legameSoggetto>`
        `        <tipoLegame>4</tipoLegame>`
        `        <dataDecorrenza>1981-10-12+01:00</dataDecorrenza>`
        `        <codiceLegame>25</codiceLegame>`
        `    </legameSoggetto>`
       ` </convivenza>`

000000_SUBAPR_1_1_1.gz
Otteniamo errori simili a quelli da voi descritti :
[2019-07-26 11:13:22,082] - classe: - metodo: - esito KO, errori fatali : 0 , errori : 2
[2019-07-26 11:13:22,082] - classe: - metodo: - TYPE:EN009,LEVEL:errore,MESSAGE:Il formato del file APR decompresso non e' XML[cvc-complex-type.2.3: l'elemento "convivenza" non deve avere [children] di tipo carattere perch▒ il tipo di contenuto ▒ di soli elementi.],ROW:119,COLUMN:26
[2019-07-26 11:13:22,082] - classe: - metodo: - TYPE:ES092,LEVEL:errore,MESSAGE:Soggetto senza scheda famiglia/convivenza associata[[soggetto-APR:34326]]
[2019-07-26 11:13:22,083] - classe: - metodo: - Tempo totale : 0s 624ms

authors: carminepat mttfranci


text:
Produzione Certificazioni fallita

Buonasera,
il servizio di produzione delle certificazioni fallisce perchè non riconosce l'intestatario del quale ho recuperato l'id tranite il servizio di consuoltazione evento:
REQUEST CONSULTAZIONE EVENTO:
{
"criteriRicercaEvento": {
"idAnsc": "2023-1110050-32-108028",
"idEvento": "1110050"
},
"testataRichiesta": {
"idComune": 5000,
"idOperazioneComune": "21",
"dataOraRichiesta": "2023-07-14T13:45:12.142+02:00",
"nomeApplicativo": "urbi",
"versioneApplicativo": "0.1.0",
"fornitoreApplicativo": "padigitale"
}
}
RESPONSE CONSULTAZIONE EVENTO:
{
"testataRisposta": {
"idComune": 5000,
"idOperazioneComune": "21",
"idOperazione": "1609149",
"idEsito": 0
},
"modelEventoDTO": [{
"id": 1110050,
"idAnsc": "2023-1110050-32-108028",
"idTipoEvento": "1",
"idtipocontenuto": "1",
"idUsecase": "11111000",
"stato": "ANNULLATO",
"dataformazione": "2023-06-30",
"ora": "10",
"minuto": "15",
"annoAtto": "2023",
"numeroatto": "32",
"tipoDichiarante": "1",
"ausilioInterprete": "false",
"idComuneRegistrazione": "5000",
"nomeComuneRegistrazione": "LISSONE",
"idProvinciaRegistrazione": "108",
"siglaProvinciaRegistrazione": "MB",
"operatore": "DLCNTN57L67A064W",
"operatoreNome": "MARTINA",
"operatoreCognome": "GORI",
"allegati": [{
"id": 2110265,
"idTipoAllegato": 1,
"hashAllegato": "kNYDvFimmQjjMhobd63N8lXP9CLtscUSgUrDd1Qp8Vc=",
"descrizione": "Attestazione di nascita",
"idStatoAllegato": 3
}
],
"intestatari": [{
"id": "2110267",
"cognome": "ROBA",
"nome": "MASSIMO",
"sesso": "M",
"dataNascita": "1955-12-07",
"idComuneNascita": "16449",
"nomeComuneNascita": "GENOVA",
"idProvinciaNascita": "10",
"siglaProvinciaNascita": "GE",
"idStatoNascita": "90",
"nomeStatoNascita": "ITALIA",
"documentoRiconoscimento": {}
}
],
"madre": {
"cognome": "ROBA",
"nome": "MAMMA",
"sesso": "F",
"dataNascita": "1931-05-06",
"idComuneNascita": "20499",
"nomeComuneNascita": "UDINE",
"idProvinciaNascita": "30",
"siglaProvinciaNascita": "UD",
"idStatoNascita": "90",
"nomeStatoNascita": "ITALIA",
"idComuneResidenza": "10323",
"nomeComuneResidenza": "UDINE",
"idProvinciaResidenza": "30",
"siglaProvinciaResidenza": "UD",
"idStatoResidenza": "90",
"nomeStatoResidenza": "ITALIA",
"idNazionalita": "90",
"nazionalita": "ITALIANA",
"flagDichiarante": false,
"flagComparente": false,
"flagFirmatario": false,
"documentoRiconoscimento": {}
},
"padre": {
"cognome": "ROBA",
"nome": "BABBO",
"sesso": "M",
"dataNascita": "1925-04-02",
"idComuneNascita": "18610",
"nomeComuneNascita": "TARANTO",
"idProvinciaNascita": "73",
"siglaProvinciaNascita": "TA",
"idStatoNascita": "90",
"nomeStatoNascita": "ITALIA",
"idComuneResidenza": "18610",
"nomeComuneResidenza": "TARANTO",
"idProvinciaResidenza": "73",
"siglaProvinciaResidenza": "TA",
"idStatoResidenza": "90",
"nomeStatoResidenza": "ITALIA",
"idNazionalita": "90",
"nazionalita": "ITALIANO",
"flagDichiarante": true,
"flagComparente": false,
"flagFirmatario": true,
"documentoRiconoscimento": {}
},
"datiDichiarante": {
"comprensione": "0"
},
"datiDiNascita": {
"luogoFiliazione": "ospedale del comune di GENOVA",
"oraNascita": "5",
"minutoNascita": "5",
"tipoAccertamento": "1"
},
"composizioneCompleta": " L'anno duemilaventitre addi' ventisette del mese di giugno alle ore dieci e minuti quindici nella casa comunale. Avanti a me, GORI MARTINA, , Ufficiale dello stato civile del Comune di QUARRATA per delega avuta e' comparso ROBA BABBO nato in TARANTO li 02.04.1925 residente in TARANTO, il quale mi ha dichiarato quanto segue: Il giorno SETTE del mese di DICEMBRE dell'anno MILLENOVECENTOCINQUANTACINQUE alle ore CINQUE e minuti CINQUE nel ospedale del comune di GENOVA da ROBA MAMMA nata in UDINE il 06.05.1931 cittadina ITALIANA residente in UDINE moglie del dichiarante, cittadino ITALIANO e' nato un bambino di sesso MASCHILE. A detto bambino che non mi viene presentato, ma della cui nascita io mi sono accertato a mezzo della attestazione di nascita rilasciata dall'ostetrica il dichiarante dà il nome di MASSIMO . ----------------------------------------------------------------------------------------------- Il presente atto viene letto all' intervenuto, il quale insieme con me, lo sottoscrive.                                                                                L'UFFICIALE DI STATO CIVILE:",
"datains": "2023-07-13T11:16:01.237248",
"dataultimoagg": "2023-07-13T15:18:02.845472"
}
],
"datiPaginazione": {
"numPagina": 1,
"numRecordPagina": 30,
"numRecordTotali": 1
}
}
REQUEST:
{
"idAnsc": "2023-1110050-32-108028",
"richiedente": {
"codiceFiscale": "GROMTN86D46G999I",
"cognome": "GORI",
"nome": "MARTINA",
"sesso": "F",
"dataNascita": "1986-04-06",
"idComuneNascita": "7631",
"nomeComuneNascita": "PRATO",
"idProvinciaNascita": "48",
"siglaProvinciaNascita": "FI",
"idStatoNascita": "90",
"nomeStatoNascita": "ITALIA",
"idComuneResidenza": "7630",
"nomeComuneResidenza": "PRATO",
"idProvinciaResidenza": "100",
"siglaProvinciaResidenza": "PO",
"idStatoResidenza": "90",
"nomeStatoResidenza": "ITALIA",
"indirizzoResidenza": "",
"idNazionalita": "90",
"nazionalita": "ITALIANA"
},
"intestatario": {
"id": "2110267"
},
"idEvento": "1110050",
"idTipoCertificato": "1",
"testataRichiesta": {
"idComune": 5000,
"idOperazioneComune": "21",
"dataOraRichiesta": "2023-07-14T13:45:14.314+02:00",
"nomeApplicativo": "urbi",
"versioneApplicativo": "0.1.0",
"fornitoreApplicativo": "padigitale"
}
}
RESPONSE:
{
"testataRisposta": {
"idComune": 5000,
"idOperazioneComune": "21",
"idOperazione": "1609150"
},
"errors": [{
"code": "400001",
"severity": "E",
"text": "Soggetto intestatario non trovato"
}
]
}

Salve @biadanpad
Chiudiamo la issue. Nel caso la nuova release non dovesse aver risolto il problema la invitiamo a riaprire la issue.
Cordiali Saluti.
Supporto ANSC.

authors: amusarra biadanpad

repo: italia/ansc


text:
Feature/navscroll progress

Descrizione
Aggiunta la possibilità di collegare una o più Progress Bar al componente Nav Scroll, per mostrare l'avanzamento dello scorrimento dei contenuti. Nella pagina di esempio del Nav Scroll è stata inserita sia per la visualizzazione mobile che nel desktop.

Checklist

[x] Le modifiche sono conformi alle linee guida di design.
[x] Il codice è coerente con le indicazioni di progetto.
[x] Le modifiche sono state verificate sui Browser supportati e per diverse risoluzioni dello schermo.
[x] Sono stati effettuati test di accessibilità in ottemperanza a quanto descritto nell'area "Accessibilità" delle linee guida di design.
[x] La documentazione è stata aggiornata.

Great work @mzampetti 🙌 thank you!

authors: astagi mzampetti

repo: italia/bootstrap-italia-next


text:
Titolo e descrizione pagina non editabili in modifica

Il paragraph type Titolo e descrizione nel contenuto Pagina
non risultano più editabili in fase di Modifica.
E' un comportamento  atteso e previsto?
Il Drupal in uso è la versione 9.5.1

Buongiorno @bit-mmontuschi ci sono novità dopo le ultime release in merito a questa issue?

authors: astagi bit-mmontuschi

repo: italia/design-comuni-drupal-theme


text:
404 bottone sorgente

Ciao @francescozaia @pdavide vi segnalo che se provo ad accedere ai sorgenti delle linee guida tramite il pulsante apposito, atterro sulla pagina 404 di github.

Grazie @danielaiozzo. Problema risolto.
@francescozaia il problema era dovuto al fatto che il tag 2019.1 era un tag di tipo annotated, quindi con un suo checksum sha-1. Questo crea qualche problema a Docs che linka le pagine della versione relativa a un URL che contiene il checksum del tag e non quello del commit corrispondente. Il modo migliore per evitare questo errore è quello di creare le release dalla UI di GitHub e non da linea di comando.

Grazie, io avevo lanciato una build per provare e poi me n'ero già dimenticato #noMultitasking.

authors: danielaiozzo francescozaia pdavide

repo: italia/design-linee-guida-docs


text:
add/1 implementation defeats its purpose

In gojq, add/1 is currently defined as:
def add(f): [f] | add;

This requires a memory allocation and thus defeats its purpose, as illustrated by jqlang's def:
def add(f): reduce f as $x (null; . + $x);

Prove it with profiling.

@itchyny wrote:

Prove it with profiling.

$ cat add.jq
def add(s): reduce s as $x (null; . + $x);
add(range(0;$n) | 1)

$ /usr/bin/time -lp gojq -n --argjson n 10000000 -f add.jq
10000000
real 3.62
user 3.33
sys 0.07
            10428416  maximum resident set size

               10060  involuntary context switches
         26967136530  instructions retired
         11536134259  cycles elapsed
             7876608  peak memory footprint

$ /usr/bin/time -lp gojq -n --argjson n 10000000 '[range(0;$n)|1] | add'
10000000
real 3.16
user 3.93
sys 0.30
           445923328  maximum resident set size

               34947  involuntary context switches
         28779583533  instructions retired
         14178228753  cycles elapsed
           443813888  peak memory footprint

The surprise here, I think, is that the u+s time for add/0 is significantly higher, no?

Can you exclude the time for constructing the array for add/0? Typical use case is adding the values from an array in given JSON. Also, please profile with various types.

Typical use case is adding the values from an array

Certainly it's a typical use case, but not in the stream-oriented style, e.g. [inputs | add].  One of the strengths of jq (like awk and many others) is its support for the stream-oriented style.  Conversely one of the weaknesses of various tools is that they want to load everything into memory.  gojq has enough memory-related issues that it seems to me one would want to seize every opportunity to alleviate them.
Anyway, I've provided the evidence you asked for and explained the rationale.  If you want to experiment further, please be my guest.

authors: itchyny pkoppstein

repo: itchyny/gojq


text:
Bump to latest version of maia

This includes the released version of secp256k1-zkp.

Superseded by #814.

authors: luckysori thomaseizinger

repo: itchysats/itchysats


text:
[Documentation Request] Create documentation files aligned with CNCF guidelines

Description:

CNCF recommends this template for project repos. Align all of Iter8 repos in accordance with this recommendation. In particular, ensure the following three files are present in the main Iter8 repos.

LICENSE
README.md
CONTRIBUTING.md

The main Iter8 repos are:

iter8
iter8-install
iter8-analytics
etc3
handler
iter8ctl
metrics-mock

Done.


text:
changes for merged repos

Modifications to iter8 necessary to support merged etc3/iter8ctl/handler repos.
Signed-off-by: Michael Kalantar kalantar@us.ibm.com

@sriumcp I don't think we envisioned this to be merged with master. Rather it was meant as proof of concept; that the etc3 changes would work once they were merged. This PR will need to be modified to refer to the tag once we merge and create.
Could you have a look at this in terms of whether or not there is anything missing or if this is sufficient motivation to move forward with the etc3 changes.

@kalantar All checks have passed which IMO is sufficient motivation to move forward with etc3 changes.

@sriumcp one thing I noticed is that we need to update the etc3 version in each test file. There are more places to make sure it is right. Is there a way we can simplify this?  Perhaps a manually executed wf to create PR or something?

You mean due to go get iter8ctl?
I think we may be able to drop the version specification altogether and simply go with the latest. Please create an issue in anycase. I feel we don't need yet another workflow (I would like to get rid of a few of them if possible).

authors: kalantar sriumcp


text:
warnings and errors in prod deployment

E.g.
warning code block language not specified in markdown. applying generic code block

lscpu: failed to determine number of CPUs: /sys/devices/system/cpu/possible: No such file or directory

warning Query takes too long: ...  # Several of these

error Command failed with exit code 1. ...
Error: Command failed: yarn build ...
Retrying with a cleared cache:

error Building static HTML failed for path "/community"

warning Deprecation warning - adding inferred resolver for field CommunityEvent.date. In Gatsby v3, only fields with an explicit directive/extension will get a resolver.

warning There are expired Nodes in community.json!

Taken from the latest deploy log, https://dashboard.heroku.com/apps/dvc-org/activity/builds/598f8b63-09f9-4ce9-aa37-f7545a8d8a45

Cc @rogermparent 🙂

I can clear a lot of the easy ones right off, like the inferred resolvers and expired events. I'll have a fix for those up within the hour.
warning code block language not specified in markdown. applying generic code block is part of gatsby-remark-prismjs, and I was able to squash locally by making a language extension for text, which is the keyword for code blocks with no specified language. That'll be in the quick fix.
The one that broke the build here on /community is a hard-to-pin-down caching issue that occasionally happens with our custom cache re-use, it's kind of difficult to pin down, but I've been able to re-create a similar issue by stopping a Heroku build and running the cache restore script locally. I think if I focus on it I can find a way to induce the problem in a controlled way on another branch, and then find a way to improve the Community schema so that it stops happening.
The warning: Query takes too long ones are primarily related to image generation, particularly on thumbnail pages since they currently generate two slightly differently cropped source sets for each of the eight of so thumbnails on each page. I would think the most obvious fix here would be to use a single image set for everything, doing slight crops via CSS if needed.
I don't know what's up with the lscpu one, other than it seems to only show up in the Heroku environment.

Hey thanks @rogermparent ! No need to fix everything but it's good to keep an eye on these logs now and then, since like you mention, builds fail occasionally (on PR review apps mostly).
About the image cropping, please open a separate issue if you guys think it's worth it cc @shcheklein

authors: jorgeorpinel rogermparent


text:
Problem with flyio deployment

If you follow https://iterative.ai/blog/mlem-cv-model-deployment/, but remove --server.ui_port 8080, --server.server_port 8081 from mlem deploy run, so it looks like this:
$ mlem deploy run flyio cv-app \
    --model torch_resnet \
    --app_name mlem-cv \
    --scale_memory 1024 \
    --server streamlit \
    --server.request_serializer torch_image

then the deployment fails and you get some errors in flyio logs (something with ports, "nothing available on 8080 port" IIUC).

reproduced. logs:
2023-03-13T09:24:03.437 app[d8126c1d] lax [info] Checkout openapi docs at <http://0.0.0.0:8081/docs>
2023-03-13T09:24:03.464 app[d8126c1d] lax [info] INFO: Started server process [527]
2023-03-13T09:24:03.464 app[d8126c1d] lax [info] INFO: Waiting for application startup.
2023-03-13T09:24:03.465 app[d8126c1d] lax [info] INFO: Application startup complete.
2023-03-13T09:24:03.465 app[d8126c1d] lax [info] INFO: Uvicorn running on http://0.0.0.0:8081 (Press CTRL+C to quit)
2023-03-13T09:24:04.214 app[d8126c1d] lax [info] Collecting usage statistics. To deactivate, set browser.gatherUsageStats to False.
2023-03-13T09:24:04.269 app[d8126c1d] lax [info] You can now view your Streamlit app in your browser.
2023-03-13T09:24:04.269 app[d8126c1d] lax [info] URL: http://0.0.0.0:80
2023-03-13T09:24:10.906 health[d8126c1d] lax [error] Health check on port 8080 has failed. Your app is not responding properly. Services exposed on ports [80, 443] will have intermittent failures until the health check passes.

repo: iterative/mlem


text:
Private registry login info

I followed all the written steps except for step #2 which requires login to the private registry, which login info is not provided.
Is there a way to get the login info or to get the required images ?

@Abdulrahman-Almutlaq For our on-premise installation, it would be great for one of our internal experts to speak with you to better understand your needs and suggest a suitable set up, as well as provide you test credentials for Studio on-premise. You can also use https://studio.iterative.ai/ to try out all the features of Studio for free.
Pls share some date/time that would work for you for a call.
cc @mnrozhkov @jurv11

@Abdulrahman-Almutlaq  - did you talk to our GTM team and got an answer?
To be clear - self-hosting Studio is not part of the free tier, and requires a payed plan.
Please mention if you need further assistance and if the original question is still relevant

authors: Abdulrahman-Almutlaq omesser tapadipti

repo: iterative/studio-onpremise


text:
Orchestrator/Enhancement: Enable editing triggers after creation

Currently it does not seem possible to edit a trigger after it has been created. Enabling the option to edit a trigger after creation would be an obvious benefit.

Triggers can be edited by double clicking

Using SQLite, I get the error below when double-clicking a trigger.
Running Windows 10 and using the connection string "sqlite:///C:\OpenOrchestratorDB\test_database.db"
Exception in Tkinter callback
Traceback (most recent call last):
File "C:\Users\AZ41832\AppData\Local\Programs\Python\Python311\Lib\site-packages\sqlalchemy\engine\base.py", line 1814, in _execute_context
context = constructor(
^^^^^^^^^^^^
File "C:\Users\AZ41832\AppData\Local\Programs\Python\Python311\Lib\site-packages\sqlalchemy\engine\default.py", line 1455, in _init_compiled
l_param: List[Any] = [
^
File "C:\Users\AZ41832\AppData\Local\Programs\Python\Python311\Lib\site-packages\sqlalchemy\engine\default.py", line 1456, in
flattened_processorskey
File "C:\Users\AZ41832\AppData\Local\Programs\Python\Python311\Lib\site-packages\sqlalchemy\sql\sqltypes.py", line 3651, in process
value = value.hex
^^^^^^^^^
AttributeError: 'str' object has no attribute 'hex'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "C:\Users\AZ41832\AppData\Local\Programs\Python\Python311\Lib\tkinter_init_.py", line 1948, in call
return self.func(*args)
^^^^^^^^^^^^^^^^
File "C:\Users\AZ41832\AppData\Local\Programs\Python\Python311\Lib\site-packages\OpenOrchestrator\orchestrator\trigger_tab.py", line 83, in
si_table.bind('', lambda e: double_click_trigger_tables(sc_table, q_table, si_table))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\AZ41832\AppData\Local\Programs\Python\Python311\Lib\site-packages\OpenOrchestrator\orchestrator\trigger_tab.py", line 224, in double_click_trigger_tables
trigger = get_selected_trigger(sc_table, q_table, si_table)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\AZ41832\AppData\Local\Programs\Python\Python311\Lib\site-packages\OpenOrchestrator\orchestrator\trigger_tab.py", line 212, in get_selected_trigger
return db_util.get_trigger(trigger_id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\AZ41832\AppData\Local\Programs\Python\Python311\Lib\site-packages\OpenOrchestrator\database\db_util.py", line 56, in inner
result = func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\AZ41832\AppData\Local\Programs\Python\Python311\Lib\site-packages\OpenOrchestrator\database\db_util.py", line 101, in get_trigger
return session.scalar(query)
^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\AZ41832\AppData\Local\Programs\Python\Python311\Lib\site-packages\sqlalchemy\orm\session.py", line 2358, in scalar
return self._execute_internal(
^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\AZ41832\AppData\Local\Programs\Python\Python311\Lib\site-packages\sqlalchemy\orm\session.py", line 2190, in _execute_internal
result: Result[Any] = compile_state_cls.orm_execute_statement(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\AZ41832\AppData\Local\Programs\Python\Python311\Lib\site-packages\sqlalchemy\orm\context.py", line 293, in orm_execute_statement
result = conn.execute(
^^^^^^^^^^^^^
File "C:\Users\AZ41832\AppData\Local\Programs\Python\Python311\Lib\site-packages\sqlalchemy\engine\base.py", line 1416, in execute
return meth(
^^^^^
File "C:\Users\AZ41832\AppData\Local\Programs\Python\Python311\Lib\site-packages\sqlalchemy\sql\elements.py", line 516, in _execute_on_connection
return connection._execute_clauseelement(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\AZ41832\AppData\Local\Programs\Python\Python311\Lib\site-packages\sqlalchemy\engine\base.py", line 1639, in _execute_clauseelement
ret = self._execute_context(
^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\AZ41832\AppData\Local\Programs\Python\Python311\Lib\site-packages\sqlalchemy\engine\base.py", line 1820, in _execute_context
self._handle_dbapi_exception(
File "C:\Users\AZ41832\AppData\Local\Programs\Python\Python311\Lib\site-packages\sqlalchemy\engine\base.py", line 2343, in _handle_dbapi_exception
raise sqlalchemy_exception.with_traceback(exc_info[2]) from e
File "C:\Users\AZ41832\AppData\Local\Programs\Python\Python311\Lib\site-packages\sqlalchemy\engine\base.py", line 1814, in _execute_context
context = constructor(
^^^^^^^^^^^^
File "C:\Users\AZ41832\AppData\Local\Programs\Python\Python311\Lib\site-packages\sqlalchemy\engine\default.py", line 1455, in _init_compiled
l_param: List[Any] = [
^
File "C:\Users\AZ41832\AppData\Local\Programs\Python\Python311\Lib\site-packages\sqlalchemy\engine\default.py", line 1456, in
flattened_processorskey
File "C:\Users\AZ41832\AppData\Local\Programs\Python\Python311\Lib\site-packages\sqlalchemy\sql\sqltypes.py", line 3651, in process
value = value.hex
^^^^^^^^^
sqlalchemy.exc.StatementError: (builtins.AttributeError) 'str' object has no attribute 'hex'
[SQL: SELECT "Triggers".id, "Triggers".trigger_name, "Triggers".process_name, "Triggers".last_run, "Triggers".process_path, "Triggers".process_args, "Triggers".process_status, "Triggers".is_git_repo, "Triggers".is_blocking, "Triggers".type
FROM "Triggers"
WHERE "Triggers".id = ?]
[parameters: [{}]]

Hmm seems that SQLite and OpenOrchestrator doesn't work as well as I hoped...

https://github.com/itk-dev-rpa/OpenOrchestrator/issues/75

authors: ghbm-itk hbpe-aarhus

repo: itk-dev-rpa/OpenOrchestrator


text:
Ретивов Д.О. Лаб. 1 Группа 6312

ФИО: Ретивов Данила Олегович
Номер группы: 6312
Номер лабораторной: 1
Краткое описание исходного кода: Я взял исходный код, реализующий текстовый редактор, из интернета. Вот ссылка на него: https://github.com/Mihey-Melnikov/text_editor.
Краткое описание проделанной работы: Я привёл код к стандартам PEP8.

из за кривых рук удалил пол кода в предпоследнем коммите, поэтому продублировал

repo: itsecd/prog-instruments-labs


text:
Add ttf-dejavu to package list

Some Spigot plugins (namely BannerBoard and InteractiveBoard that I've tested) use the Java2D graphics library to render in-game maps from images, text, etc. server side. Unfortunately Java2D will crash if it can't find at least one system font when it calls sun.java2d.HeadlessGraphicsEnvironment.getAvailableFontFamilyNames() causing any plugin that uses this API to fail to load.
This isn't a problem on most systems as almost every distro's openJRE package marks fontconfig or dejavu as a dependency to prevent issues like this, however openJDK's alpine images don't for some reason (presumably  because you wouldn't normally need font access in a headless environment except for extreme edge cases).
This change simply adds ttf-dejavu to the APK list which solves this issue for both of these plugins (and presumably others that exist that use this method).

This is now pushed to Docker Hub

authors: itzg toboshii

repo: itzg/docker-minecraft-server


text:
Broken highlight for go language

Code highlight was broken after installing this extension:
With extension:

Without extension:

@Dancheg97, the highlight starts with UPPERCASE keyword should have a ;  at the end of the query.

repo: iuyoy/highlight-string-code


text:
change_keys method in ConfigurationManager not working for python 3.8 and over

This method works well for python 3.7 and under, but this error occurs when using python3.8:
RuntimeError: dictionary keys changed during iteration

This could be fixed by passing the keys (copy) and the context (reference), instead of getting the keys from the context.

This error usually occurs when you add to or remove elements from an iterable while looping over it. It is a better practice to make a copy of the original container and modify that one. Can you include where this is happening in code?

The error occurs here: https://github.com/ivadomed/ivadomed/blob/master/ivadomed/config_manager.py#L110.
I know / understand why there is an error. It currently works so I simply opened an issue (it's on my todo list). Passing a copy defies the purpose of the method which is to modify the dictionary (if I pass a copy the object won't be modified). Passing a copy of the keys should solve the problem.

authors: andreanne-lemay ssinad

repo: ivadomed/ivadomed


text:
Pipe will never be connected in debug mode

If you run afl-fuzz with "-debug" you will never be able to connect to the named pipe.
afl-fuzz.c will try to ConnectNamedPipe in create_target_process().
but winafl.dll will:
if(!options.debug_mode) {
    setup_pipe();
    setup_shmem();
} else {
    winafl_data.afl_area = (unsigned char *)dr_global_alloc(MAP_SIZE);
}

(in dr_client_main, winafl.c)
so if you pass "-debug" - winafl will never connect the pipe. And that happens to cause me timeouts and "cannot kill process -1" message.
Thats because afl-fuzz will extract the pid after ConnectNamedPipe will finish, so I guess what happens is that meanwhile another thread realize there is timeout and try to kill it with the global var child_pid which is still "-1".
I temporary changed it to:
setup_pipe();
setup_shmem();
if(!options.debug_mode) {
} else {
    winafl_data.afl_area = (unsigned char *)dr_global_alloc(MAP_SIZE);
}

And that solved it

Correct, with -debug flag, winafl.dll will never connect to the pipe.
the -debug flag is only meant to be used with drrun.exe and should never be used in combination with afl-fuzz.

authors: ivanfratric uriyay

repo: ivanfratric/winafl

license_source: bigquery


text:
Catalog service basic API

To develop basic API for the catalog service.

in progress...

done

repo: ivolynets/wide-cart


text:
Separate prometheus labels creation from migrateCloudwatchToPrometheus

No changes to actual functionality.
First I wanted to simplify promLabels handling on apigateway by putting dimension_Stage, dimension_Resource and dimension_Method (and get rid of promLabelExists function). Then I wanted to put name and region labels next to each others and at the end decided it wouldn't hurt to split whole labeling stuff into separate function.

Love it thanks!

authors: jylitalo thomaspeitz

repo: ivx/yet-another-cloudwatch-exporter


text:
🛑 NATURCOIFFEUR.EU is down

In 0bd3343, NATURCOIFFEUR.EU (https://www.naturcoiffeur.eu) was down:

HTTP code: 500
Response time: 700 ms

Resolved: NATURCOIFFEUR.EU is back up in 0cd8ace after 18 minutes.

repo: iwhp/upptime


text:
🛑 21Eurkon is down

In 686b926, 21Eurkon (https://blog.eurkon.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 21Eurkon is back up in d1ae1db after 20 minutes.

repo: iwyang/check


text:
🛑 Takagi is down

In ca5cdfc, Takagi (https://lixingyong.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Takagi is back up in 171d7c9.


text:
🛑 05Takagi is down

In 7826d3a, 05Takagi (https://lixingyong.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 05Takagi is back up in f9efcd7 after 1 hour, 22 minutes.


text:
🛑 21Eurkon is down

In 516c32b, 21Eurkon (https://blog.eurkon.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 21Eurkon is back up in b665a1c after 9 minutes.


text:
[RFC] Deprecation decorator

This is a Request For Comments on the idea of introducing a decorators that would mark either a class, function methods or a specific kwarg within any of these callables as deprecated. After input I will make a more polished PR. What I need input on is this:

The implementation has both the notion of soft and hard deprecation, where the former issues a warning and the latter raises and exception. Personally, I think that is nice, but I need input on whether you think it is overkill
The periods where a feature is soft or hard deprecated in given as a time interval since last supported release. I.e "the feature is soft deprecated for all releases for 3 months after version '1.2.3' and hard deprecated an additional 3 months after that". Is this the way you prefer to work with these intervals? One might also list those intervals as a number of releases i.e. "the feature is soft deprecated 2 releases after version '1.2.3' and hard deprecated an additional 2 releases after that"
EDIT How clever do we want it to be? In principle we could of course give it a "last supported time stamp" and well defined time deltas and then we could calculate when it would move from soft deprecation to hard, as opposed to the suggested implementation when you will need to flip the hard_deprecation boolean by hand. I didn't do it because it is my view that it will not be worth the extra code complexity and because I don't want peoples code to all of a sudden hard deprecate with them having upgraded.

The feature is used like this:
import sys
from time import sleep

from ixdat.tools import deprecate

@deprecate("1.2.3", "1 month", "1 month", "Please use `MyNewClass` instead")
class MyClass:
    pass

my_obj = MyClass()

# This is just a bit of trickery to make the warnings appear in order with the printed
# separator
sys.stderr.flush()
sleep(0.1)
print("\n\n===\n\n", flush=True)

class MyClass:

    @deprecate("1.2.3", "1 month", "1 month", "Please use `mynewmethod` instead")
    def mymethod(self):
        ...

    @classmethod
    @deprecate(
        "1.2.3",
        "1 month",
        "1 month",
        "Please use `kwargb` instead",
        kwarg_name="kwarga",
        hard_deprecate=True
    )
    def myothermethod(cls, arg, kwarga=None, kwargb=None):
        ...

my_obj = MyClass()
my_obj.mymethod()  # Will warn

sys.stderr.flush()
sleep(0.3)
print("\n\n===\n\n", flush=True)
sleep(0.3)

my_obj.myothermethod(1, kwarga=7)

which outputs something like this:
/home/kenneth/venv/ixdat/ixdat/test.py:12: DeprecationWarning: The class 'MyClass' is deprecated, its last supported version being 1.2.3.
This means that:
* It is soft deprecated (issuing warnings) in all releases for 1 month after the last supported release
* It is hard deprecated (raising exceptions) in all releases for an additional 1 month after that
* After the hard deprecation period ends, it will be removed

See instruction below on how to update your code to avoid this message:
Please use `MyNewClass` instead
  my_obj = MyClass()

===

/home/kenneth/venv/ixdat/ixdat/test.py:40: DeprecationWarning: The method 'MyClass.mymethod' is deprecated, its last supported version being 1.2.3.
This means that:
* It is soft deprecated (issuing warnings) in all releases for 1 month after the last supported release
* It is hard deprecated (raising exceptions) in all releases for an additional 1 month after that
* After the hard deprecation period ends, it will be removed

See instruction below on how to update your code to avoid this message:
Please use `mynewmethod` instead
  my_obj.mymethod()  # Will warn

===

Traceback (most recent call last):
  File "/home/kenneth/venv/ixdat/ixdat/test.py", line 48, in <module>
    my_obj.myothermethod(1, kwarga=7)
  File "/home/kenneth/venv/ixdat/ixdat/src/ixdat/tools.py", line 211, in inner_function
    raise DeprecationError(compound_message)
ixdat.exceptions.DeprecationError: The property named 'kwarga' in method 'MyClass.myothermethod' is deprecated, its last supported version being 1.2.3.
This means that:
* It is soft deprecated (issuing warnings) in all releases for 1 month after the last supported release
* It is hard deprecated (raising exceptions) in all releases for an additional 1 month after that
* After the hard deprecation period ends, it will be removed

See instruction below on how to update your code to avoid this message:
Please use `kwargb` instead

Hi Kenneth,
I think all of this is awesome! The useage syntax is simple and easy enough that I would indeed use it all over the place!
The only thing I think is overkill is the timed moving from soft to hard depreciation. I think it would be better to do that by versions. That gives us more flexibility, important since ixdat is not anyone's full job. If, say, we set up a depreciation in an ixdat release but then no one has time for ixdat for a few months and, in the meanwhile it is revealed that the thing should not have been depreciated, we'd have shot ourselves in the foot with the timer but have caused approx. zero damage with the versions.
So maybe the code could be
class MyClass:
    @deprecate("1.2.3", "1.3.0", "Please use `kwargb` instead", kwarg_name="kwarga", )

to soft depreciate use of kwarga after 1.2.3 and hard depreciate after 1.3.0... something like that?
I also like the only_one_of decorator, and agree that could clear up some complex kwarg interpreting at the start of a number of methods.

@ScottSoren It's a good point about avoiding the timed hard deprecation. I will change it. Only thing is, if you provide a specific version number as opposed to say "3 minor/major releases after" then you are a little locked in with what the next versions will be. It might not be a problem in reality, what do you think?

Ah. I think there is a small terminology difference here. I refer to the second digit as "minor", as per semver. In any case, since you are primary maintainer, if you would prefer a specific version to be listed, I think we should do that.
Making the deprecation thresholds optional is a good idea. I will change the implementation to accommodate this. What this means is that:

Applying the decorator means the feature is immediately (in practice only noticed from next release) soft deprecated
The developer may optionally list at which versions the feature will be hard deprecated
The developer may optionally list at which version the feature will be removed entirely

Since we are to go ahead with version numbers I think I will also change the implementation to automatically hard deprecate by comparing version numbers, if the hard deprecate version number is given. This change will then mean that the hard deprecate argument disappears and that a developer, for a deprecation where the entire schedule is known, will not have to touch the decorator between initial deprecation and deletion.
Thanks for the good suggestions.
Plan now is to split the only_one_of decorator out into a separate branch, implement the changes and remove the draft tag from this.

authors: KennethNielsen ScottSoren

repo: ixdat/ixdat


text:
How to send signed transaction with private key on ruby on rails

Hi everyone.
I am going to send transaction with my private key using web3-eth gem.
But i can't find correct solution anywhere.
Please help me!
Best regards!

I can do it with nodejs and python.
But i want do it with ruby on rails.
for example I can find this solution in nodejs
var count = web3.eth.getTransactionCount("0x26...");
var abiArray = JSON.parse(fs.readFileSync('mycoin.json', 'utf-8'));
var contractAddress = "0x8...";
var contract = web3.eth.contract(abiArray).at(contractAddress);
var rawTransaction = {
"from": "0x26...",
"nonce": web3.toHex(count),
"gasPrice": "0x04e3b29200",
"gasLimit": "0x7458",
"to": contractAddress,
"value": "0x0",
"data": contract.transfer.getData("0xCb...", 10, {from: "0x26..."}),
"chainId": 0x03
};
var privKey = new Buffer('fc3...', 'hex');
var tx = new Tx(rawTransaction);
tx.sign(privKey);
var serializedTx = tx.serialize();
web3.eth.sendRawTransaction('0x' + serializedTx.toString('hex'), function(err, hash) {
if (!err)
console.log(hash);
else
console.log(err);
});
How can i do it in ruby on rails?
Please help me.

Any update on this?

authors: dpgailey noydarly


text:
new where clause functions

hi @izniburak
how about having clean whereNull and whereNotNull

  public function whereNull($where)
  {
    $where = $where . ' is null';
    if (is_null($this->where))
      $this->where = $where;
    else
      $this->where = $this->where . ' ' . 'and ' . $where;
    return $this;
  }

// will produce ``` where tbl.colmn is null```

  public function whereNotNull($where)
  {
    $where = $where . ' is not null';
    if (is_null($this->where))
      $this->where = $where;
    else
      $this->where = $this->where . ' ' . 'and ' . $where;
    return $this;
  }

// will produce ``` where tbl.colmn is not null```

Actually, I really missed these functions in my last project, so i had to extend your class.
Thanks !

Why is it closed if it's not implemented? Current where doesn't offer any IS NULL support. I'd argue that such functionality should be implemented in current where.

authors: KrzysztofMadejski jagroop

repo: izniburak/pdox


text:
🛑 Nexterm is down

In 1afc8c4, Nexterm (https://ssh.j551n.com) was down:

HTTP code: 530
Response time: 69 ms

Resolved: Nexterm is back up in 4bbd2d6 after 16 hours, 31 minutes.


text:
updated README.md

updated README.md

update


text:
Error opening .jpa file when using NetBeans dark metal look and feel

Message : org.netbeans.modeler.scene.vmd.AbstractPModelerScene.init(AbstractPModelerScene.java:150)
StackTrace :
java.lang.NullPointerException
at org.netbeans.modeler.scene.vmd.AbstractPModelerScene.init(AbstractPModelerScene.java:150)
at org.netbeans.jpa.modeler.specification.model.scene.JPAModelerScene.init(JPAModelerScene.java:329)
at org.netbeans.modeler.specification.model.file.action.ModelerFileActionListener.openModelerFile(ModelerFileActionListener.java:145)
at org.netbeans.modeler.specification.model.file.action.ModelerFileActionListener.openModelerFile(ModelerFileActionListener.java:72)
at org.netbeans.modeler.specification.model.file.action.ModelerFileActionListener.openModelerFile(ModelerFileActionListener.java:64)
at org.netbeans.modeler.specification.model.file.action.ModelerFileActionListener.lambda$actionPerformed$0(ModelerFileActionListener.java:59)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
at org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:159)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
ModelerFile :

Hi @pedrohidalgo,
Issue is not re-producible with this http://plugins.netbeans.org/plugin/62424/darcula-laf-for-netbeans plugin. Can you please help and guide to re-produce the issue.

authors: jGauravGupta pedrohidalgo

repo: jGauravGupta/JPAModeler


text:
Create a candidate role with related permissions.

Is your feature request related to a problem? Please describe.
As a candidate I should have a candidate user role with relevant permissions. I should not be able to access the Admin side and should be able to see all my applications and the vacancies.
Describe the solution you'd like
A candidate user to be created with the following permissions. If all current user on Apply could be given this role before Assessors start accessing the platform that would be ideal:

Ability to create an account and amend their profile details at any time
Ability to create and save an application up until submission
Ability to see their submitted application
Ability to download their submitted or previous application
Ability to download templates from the platform
Ability to upload completed templates to the platform

Describe alternatives you've considered
Having only candidates on this side but we need Assessors for references.
Additional context
Nothing.
https://docs.google.com/spreadsheets/d/1hkI1vlIC89AII4MgiK9qYtAXRoa27bCOM9Ric1oWdSQ/edit#gid=1158262271

There's nothing to implement in Admin for this however the ticket is useful reference for testing.

repo: jac-uk/admin


text:
Lint Issue Reporting

Rust has a linting tool known as Clippy that uses an interesting strategy for keeping track of and developing new lints.
Clippy has several categories of lints, that can be enabled individually including one called "nursery". The "nursery" category is for many kinds of experimental lints that probably have mistakes in them, users can opt into this category to get potentially helpful lints at the possibility that they may be wrong or annoying. Clippy also encourages users that encounter bugs in the experimental lints to submit bug reports on their issues page, and as a result, most of the issues are about lints themselves.
Clippy's issue system has labels to keep track of the different kinds of issues with lints including "false positive" (the lint shows up when it shouldn't), "false negative" (the lint doesn't show up when it should), and "suggestion causes error" (where the suggested change is incorrect).
They also have a series of issue templates to make reporting these bugs even easier to users. Resyntax could also include a link to the "false positive" template issue creation page that the user may click on if they believe the suggestion is incorrect (as discussed on discord). Making bug reporting about suggestions very easy to users will get you much more helpful information without the need for anonymous information sharing like was suggested.

Putting the adoption barrier label on this because I think it's a mandatory feature before putting Resyntax in the langserver (jeapostrophe/racket-langserver#40).
One thing I'm wary of is configuration that lives in the tool instead of the code. I don't think Resyntax will be useful if it ships with a million rules of varying quality and asks users to pick and choose which to enable and disable. I want to put this in front of students who are using Racket for the very first time, which means a zero-configuration approach is mandatory. Therefore, I think that the distinction between "experimental" rules and "production-ready" rules will be in where and when they show up. For instance, running experimental rules only on pull requests instead of when resyntax is run manually on the command line, to prevent people from creating large refactoring changes and merging them with broken changes from experimental rules included. We could also adopt some sort of gradual rollout strategy, where experimental rules start out as enabled for only 10% of users somehow.

Related: #281.

repo: jackfirth/resyntax