[BUG] Assumptions are (silently) ignored

----- MODULE Bar ----
CONSTANT
    \* @type: Bool;
    P

\* Should "catch" P = FALSE
ASSUME P = TRUE

VARIABLE
   \* @type: Bool;
    x

Init ==
    x = P

Next ==
    UNCHANGED x

Inv ==
    x = TRUE
=====

CONSTANT
    P = FALSE
INIT
    Init
NEXT
    Next
INVARIANT
    Inv

markus@avocado:~$ apalache check --config=Bar.cfg Bar
# Tool home: /home/markus/src/TLA/_community/apalache
# Package:   /home/markus/src/TLA/_community/apalache/mod-distribution/target/apalache-pkg-0.15.9-SNAPSHOT-full.jar
# JVM args:  -Xmx4096m -DTLA-Library=/home/markus/src/TLA/_community/apalache/src/tla
#
# APALACHE version 0.15.9-SNAPSHOT build v0.15.8-3-g6a26844
#
# WARNING: This tool is in the experimental stage.
#          Please report bugs at: [https://github.com/informalsystems/apalache/issues]
#
# Usage statistics is ON. Thank you!
# If you have changed your mind, disable the statistics with config --enable-stats=false.

Checker options: filename=Bar, init=, next=, inv=                 I@15:54:36.199
Tuning:                                                           I@15:54:36.650
PASS #0: SanyParser                                               I@15:54:36.652
Parsing file /home/markus/src/TLA/_specs/models/tutorials/BlockingQueueTLA/Bar.tla
PASS #1: TypeCheckerSnowcat                                       I@15:54:37.310
 > Running Snowcat .::.                                           I@15:54:37.311
 > Your types are great!                                          I@15:54:37.450
 > All expressions are typed                                      I@15:54:37.450
PASS #2: ConfigurationPass                                        I@15:54:37.481
  > Bar.cfg: Loading TLC configuration                            I@15:54:37.485
  > Using the init predicate Init from the TLC config             I@15:54:37.562
  > Using the next predicate Next from the TLC config             I@15:54:37.562
  > Bar.cfg: found INVARIANTS: Inv                                I@15:54:37.562
  > Set the initialization predicate to Init                      I@15:54:37.564
  > Set the transition predicate to Next                          I@15:54:37.565
  > Set an invariant to Inv                                       I@15:54:37.566
  > Replaced CONSTANT P with FALSE                                I@15:54:37.569
PASS #3: DesugarerPass                                            I@15:54:37.606
  > Desugaring...                                                 I@15:54:37.607
PASS #4: UnrollPass                                               I@15:54:37.639
  > Unroller                                                      I@15:54:37.656
PASS #5: PrimingPass                                              I@15:54:37.685
  > Introducing InitPrimed for Init'                              I@15:54:37.692
PASS #6: CoverAnalysisPass                                        I@15:54:37.722
PASS #7: InlinePass                                               I@15:54:37.724
  > InlinerOfUserOper                                             I@15:54:37.728
  > LetInExpander                                                 I@15:54:37.729
  > FoldOperLetinizer                                             I@15:54:37.730
  > InlinerOfUserOper                                             I@15:54:37.731
Leaving only relevant operators: CInitPrimed, Init, InitPrimed, Inv, Next I@15:54:37.735
PASS #8: VCGen                                                    I@15:54:37.764
  > Producing verification conditions from the invariant Inv      I@15:54:37.765
  > VCGen produced 1 verification condition(s)                    I@15:54:37.777
PASS #9: PreprocessingPass                                        I@15:54:37.794
  > Before preprocessing: unique renaming                         I@15:54:37.794
 > Applying standard transformations:                             I@15:54:37.827
  > PrimePropagation                                              I@15:54:37.828
  > Desugarer                                                     I@15:54:37.843
  > UniqueRenamer                                                 I@15:54:37.858
  > Normalizer                                                    I@15:54:37.876
  > Keramelizer                                                   I@15:54:37.893
  > After preprocessing: UniqueRenamer                            I@15:54:37.907
PASS #10: TransitionFinderPass                                    I@15:54:37.923
  > Found 1 initializing transitions                              I@15:54:37.941
  > Found 1 transitions                                           I@15:54:37.942
  > No constant initializer                                       I@15:54:37.943
  > Applying unique renaming                                      I@15:54:37.944
PASS #11: OptimizationPass                                        I@15:54:37.956
 > Applying optimizations:                                        I@15:54:37.963
  > ConstSimplifier                                               I@15:54:37.964
  > ExprOptimizer                                                 I@15:54:37.966
  > ConstSimplifier                                               I@15:54:37.967
PASS #12: AnalysisPass                                            I@15:54:37.983
 > Marking skolemizable existentials and sets to be expanded...   I@15:54:37.988
  > SkolemizationMarker                                           I@15:54:37.989
  > ExpansionMarker                                               I@15:54:37.990
 > Running analyzers...                                           I@15:54:37.993
  > Introduced expression grades                                  I@15:54:38.007
  > Introduced 0 formula hints                                    I@15:54:38.007
PASS #13: PostTypeCheckerSnowcat                                  I@15:54:38.008
 > Running Snowcat .::.                                           I@15:54:38.008
 > Your types are great!                                          I@15:54:38.048
 > All expressions are typed                                      I@15:54:38.048
PASS #14: BoundedChecker                                          I@15:54:38.064
State 0: Checking 1 state invariants                              I@15:54:38.469
State 0: state invariant 0 violated. Check the counterexample in: counterexample1.tla, MC1.out, counterexample1.json E@15:54:38.502
Found 1 error(s)                                                  I@15:54:38.508
The outcome is: Error                                             I@15:54:38.509
Checker has found an error                                        I@15:54:38.509
It took me 0 days  0 hours  0 min  2 sec                          I@15:54:38.510
Total time: 2.387 sec                                             I@15:54:38.510
EXITCODE: ERROR (12)

Yep, the corresponding issue has a two-digit number: #69


Automator: update proxy@master in istio/istio@master

Generated by Automator - 2021-03-15T17:22:01+00:00

@istio-testing: PR needs rebase.

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.

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

Test name
Commit
Details
Rerun command

unit-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
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

unit-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test unit-tests_istio

integ-pilot-multicluster-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
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

unit-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test unit-tests_istio

integ-pilot-multicluster-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-operator-controller-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

unit-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test unit-tests_istio

integ-pilot-multicluster-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-operator-controller-tests_istio

integ-security-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
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

unit-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test unit-tests_istio

integ-pilot-multicluster-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-operator-controller-tests_istio

integ-security-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-security-multicluster-tests_istio

integ-ipv6-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-ipv6-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

unit-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test unit-tests_istio

integ-pilot-multicluster-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-operator-controller-tests_istio

integ-security-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-security-multicluster-tests_istio

integ-ipv6-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
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

unit-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test unit-tests_istio

integ-pilot-multicluster-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-operator-controller-tests_istio

integ-security-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-security-multicluster-tests_istio

integ-ipv6-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-multicluster-k8s-tests_istio

analyze-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test analyze-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

unit-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test unit-tests_istio

integ-pilot-multicluster-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-operator-controller-tests_istio

integ-security-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-security-multicluster-tests_istio

integ-ipv6-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-multicluster-k8s-tests_istio

analyze-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test analyze-tests_istio

lint_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
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

unit-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test unit-tests_istio

integ-pilot-multicluster-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-operator-controller-tests_istio

integ-security-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-security-multicluster-tests_istio

integ-ipv6-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-multicluster-k8s-tests_istio

analyze-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test analyze-tests_istio

lint_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test lint_istio

integ-helm-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-helm-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

unit-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test unit-tests_istio

integ-pilot-multicluster-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-operator-controller-tests_istio

integ-security-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-security-multicluster-tests_istio

integ-ipv6-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-multicluster-k8s-tests_istio

analyze-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test analyze-tests_istio

lint_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test lint_istio

integ-helm-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-helm-tests_istio

release-notes_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test release-notes_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

unit-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test unit-tests_istio

integ-pilot-multicluster-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-operator-controller-tests_istio

integ-security-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-security-multicluster-tests_istio

integ-ipv6-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-multicluster-k8s-tests_istio

analyze-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test analyze-tests_istio

lint_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test lint_istio

integ-helm-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-helm-tests_istio

release-notes_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test release-notes_istio

integ-pilot-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
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

unit-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test unit-tests_istio

integ-pilot-multicluster-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-operator-controller-tests_istio

integ-security-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-security-multicluster-tests_istio

integ-ipv6-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-multicluster-k8s-tests_istio

analyze-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test analyze-tests_istio

lint_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test lint_istio

integ-helm-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-helm-tests_istio

release-notes_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test release-notes_istio

integ-pilot-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-pilot-k8s-tests_istio

gencheck_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test gencheck_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

unit-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test unit-tests_istio

integ-pilot-multicluster-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-operator-controller-tests_istio

integ-security-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-security-multicluster-tests_istio

integ-ipv6-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-multicluster-k8s-tests_istio

analyze-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test analyze-tests_istio

lint_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test lint_istio

integ-helm-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-helm-tests_istio

release-notes_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test release-notes_istio

integ-pilot-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-pilot-k8s-tests_istio

gencheck_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test gencheck_istio

integ-distroless-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
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

unit-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test unit-tests_istio

integ-pilot-multicluster-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-operator-controller-tests_istio

integ-security-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-security-multicluster-tests_istio

integ-ipv6-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-multicluster-k8s-tests_istio

analyze-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test analyze-tests_istio

lint_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test lint_istio

integ-helm-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-helm-tests_istio

release-notes_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test release-notes_istio

integ-pilot-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-pilot-k8s-tests_istio

gencheck_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test gencheck_istio

integ-distroless-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-distroless-k8s-tests_istio

release-test_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
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

unit-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test unit-tests_istio

integ-pilot-multicluster-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-operator-controller-tests_istio

integ-security-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-security-multicluster-tests_istio

integ-ipv6-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-multicluster-k8s-tests_istio

analyze-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test analyze-tests_istio

lint_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test lint_istio

integ-helm-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-helm-tests_istio

release-notes_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test release-notes_istio

integ-pilot-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-pilot-k8s-tests_istio

gencheck_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test gencheck_istio

integ-distroless-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-distroless-k8s-tests_istio

release-test_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test release-test_istio

integ-telemetry-mc-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
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

unit-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test unit-tests_istio

integ-pilot-multicluster-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-operator-controller-tests_istio

integ-security-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-security-multicluster-tests_istio

integ-ipv6-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-ipv6-k8s-tests_istio

integ-multicluster-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-multicluster-k8s-tests_istio

analyze-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test analyze-tests_istio

lint_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test lint_istio

integ-helm-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-helm-tests_istio

release-notes_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test release-notes_istio

integ-pilot-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-pilot-k8s-tests_istio

gencheck_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test gencheck_istio

integ-distroless-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-distroless-k8s-tests_istio

release-test_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test release-test_istio

integ-telemetry-mc-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
link
/test integ-telemetry-mc-k8s-tests_istio

integ-telemetry-k8s-tests_istio
d34a82f503b7c314792f6be6eeb8af261edbc053
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.


Update cache-troubleshoot-timeouts.md

Document the impact of virus scanning on server load for C0 and C1 caches.

@flang-msft

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

emailed author


How to do a no-cors request to flickr open api?

This is more of a question than an issue. A question to you but an issue to me. I'm trying to use fetch to hit the flicker open api, or to make cross origin requests in general, and can't. I've gathered that I should use mode: 'no-cors' but that results in an "opaque" response, which doesn't provide me the json data I need.
Even though I can see in the network tab that the JSON was sent back with the response, in fact.
Any help would be a big help!?
Here's a codepen. The request works with jquery. Not with fetch.
http://codepen.io/morgs32/pen/OMGEpm

Flickr does not support CORS headers on api.flickr.com, so fetch and XMLHttpRequest will not work.
jQuery is sending a JSONP request and evaluating the JavaScript served in Flickr's response with an injected <script> element.

The issue claims that the fetch is unsuccessful in general. I have tried to do a simple fetch of github.com, as the example demonstrates, and I have been unsuccessful. Is there some trick not included in the example code?

Cross-origin resource sharing requires the participation of the server via the Access-Control-Allow-Origin response header. We don't serve that header from the github.com domain, but we do support CORS from api.github.com.
Compare the results of the following requests:
fetch('https://github.com')
fetch('https://api.github.com')

Thanks, I thought this might be the case, but since the example uses github.com. rather than api.giuthub.com, I thought it might be the case that it was supposed to work. I'll put in a pr to change the example.


there is an error on the top of http://outdatedbrowser.com/en

A PHP Error was encountered
Severity: Warning
Message: fopen(./public/stats-files/browser-ww-monthly-201702-201703-bar.csv): failed to open stream: No such file or directory
Filename: views/home.php
Line Number: 64

Hi @sajjad-shirazy, thank you for your input...
We already corrected the issue :)


Set-Owner.ps1

Hello! Good work!
How about long path support?

I'll have to take a look at that one. It won't be as simple as what I am doing right now but definitely not impossible either!


Add files via upload

@Xevispl First stage of verification passed, official domain is krasiniak.pl as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@Xevispl v


Move instantiation logic to composition_root.py

Currently, protostar_cli.py mixes logic specific to the Protostar CLI and class instantiation logic.
Proposal
Protostar CLI should accept commands as constructor arguments.  The composition_root.py can contain a function with the following signature:
def startup(script_root: Path) -> `ProtostarCLI`:
    ...

https://freecontent.manning.com/dependency-injection-in-net-2nd-edition-understanding-the-composition-root/

Done


Madlibs generator

Develop a Javascript madlibs app.

The Mad Libs project is a fun and interactive program that allows users to create humorous and often nonsensical stories by filling in the blanks with their own words or phrases it is a great way to practice user input, string manipulation, and basic programming concepts while providing an entertaining and creative experience for the users
The project typically involves the following components:
Story Template: Start by creating a story template that includes a narrative with specific placeholders for different parts of speech (e.g., nouns, verbs, adjectives, adverbs).
Requirements:

Prompt the user to provide words or phrases for each placeholder. Collect and store these user inputs.
Replace the placeholders in the story template with the user-provided words or phrases, creating a customized and often comical story.
Present the final generated story to the user, complete with their input, and let them enjoy the humorous results.

Bonus:

Allow the user to play again with a different template or share the generated story with others.

Any number of people can work on a single issue,
This issue is open to all.
Project location 👉🏻 MadStory/{USERNAME}/...yourfiles
👨🏻💻 Happy Coding 👩🏻💻

assign this to me.

assign this to me.
Hi,
The issue is open to all, please go through the readme file and raise your PR.
Thank You.

Ok sure.


bjosse ceda-cc report for CNRM-MOCAGE v20210414

"error count 3" example
2021-07-05 17:19:10,369 INFO Starting batch -- number of file: 1
2021-07-05 17:19:10,369 INFO Source: /datacentre/arrivals/users/bjosse/ccmi-2022/v20210414/r1i1p1f1/Amon/o3stratdep_Amon_CNRM-MOCAGE_refD1_r1i1p1f1_gn_196201-196212.nc
2021-07-05 17:19:10,369 INFO Command: /home/badc/miniconda3/envs/ingest_py3/bin/ceda-cc -p ccmi2022 -f /datacentre/arrivals/users/bjosse/ccmi-2022/v20210414/r1i1p1f1/Amon/o3stratdep_Amon_CNRM-MOCAGE_refD1_r1i1p1f1_gn_1
96201-196212.nc
2021-07-05 17:19:10,378 INFO Python netcdf: netCDF4
2021-07-05 17:19:10,378 INFO Starting: o3stratdep_Amon_CNRM-MOCAGE_refD1_r1i1p1f1_gn_196201-196212.nc
2021-07-05 17:19:10,378 INFO Starting file o3stratdep_Amon_CNRM-MOCAGE_refD1_r1i1p1f1_gn_196201-196212.nc
2021-07-05 17:19:10,378 INFO C4.001.001: [parse_filename]: OK
2021-07-05 17:19:10,379 INFO C4.001.002: [parse_filename_timerange]: OK
2021-07-05 17:19:10,379 INFO C4.001.004: [file_name_extra]: OK
2021-07-05 17:19:10,571 INFO C4.002.001: [global_ncattribute_present]: OK
2021-07-05 17:19:10,571 INFO C4.002.003: [variable_type]: OK
2021-07-05 17:19:10,571 ERROR C4.002.004: [variable_ncattribute_present]: FAILED:: Required variable attributes missing: ['standard_name']
2021-07-05 17:19:10,572 INFO C4.002.005: [variable_ncattribute_mipvalues]: OK
2021-07-05 17:19:10,572 INFO C4.002.005: [variable_ncattribute_mipvalues]: OK
2021-07-05 17:19:10,572 INFO C4.002.005: [variable_ncattribute_mipvalues]: OK
2021-07-05 17:19:10,572 ERROR C4.002.006: [global_ncattribute_cv]: FAILED:: Global attributes do not match constraints: [('nominal_resolution', '2x2 degree', "['0.5 km', '1 km', '10 km', '100 km']"), ('source_id', 'CNR
M-MOCAGE', "['ACCESS-CM2-Chem', 'CCSRNIES-MIROC32', 'CESM2-WACCM', 'CMAM']")]
2021-07-05 17:19:10,572 ERROR C4.002.007: [filename_filemetadata_consistency]: FAILED:: File name segments do not match corresponding global attributes: [(4, 'grid_label'), (5, 'variant_label'), (6, '@variant:5:')]
2021-07-05 17:19:10,572 INFO C4.003.001: [time_attributes]: OK
2021-07-05 17:19:10,572 INFO Done -- error count 3

"variable_ncattribute_present"
This ceda-cc error appears for ccmi-2022 variables that don't have standard names.
The standard name attribute should be present but left empty, e.g.
o3stratdep:standard_name = ""

[global_ncattribute_cv]: FAILED:: Global attributes do not match constraints:
[('nominal_resolution', '2x2 degree', "['0.5 km', '1 km', '10 km', '100 km']"
"2x2 degree" is not part of the controlled vocabulary for the nominal_resolution attribute.
I'll email David Plummer about this, it could be that we can extend the nominal_resolution controlled vocabulary to include "2x2 degree"

[global_ncattribute_cv]: FAILED:: Global attributes do not match constraints:
('source_id', 'CNRM-MOCAGE', "['ACCESS-CM2-Chem', 'CCSRNIES-MIROC32', 'CESM2-WACCM', 'CMAM']")
"CNRM-MOCAGE" is not part of the controlled vocabulary for the source_id attribute.
The source_id provided for CNRM-CERFACS is "CNRM-MOCAGE-1-HR"

[filename_filemetadata_consistency]: FAILED:: File name segments do not match corresponding global attributes
This does not need to be corrected.
I believe that this error is due to a problem with how the ceda-cc quality control software is processing the ccmi-2022 filenames.

[global_ncattribute_cv]: FAILED:: Global attributes do not match constraints
('nominal_resolution', '2x2 degree', "['0.5 km', '1 km', '10 km', '100 km']"
"2x2 degree" is not part of the controlled vocabulary for the nominal_resolution attribute.
I will email David Plummer about this, it could be that we can extend the nominal_resolution controlled vocabulary to include "2x2 degree"

David has replied and says he'll look into extending the CV list for nominal_resolution to include "2x2 degree"

tar ball of the full ceda-cc output
v20210414ceda-cc.tar.gz

[global_ncattribute_cv]: FAILED:: Global attributes do not match constraints
('nominal_resolution', '2x2 degree', "['0.5 km', '1 km', '10 km', '100 km']"
"2x2 degree" is not part of the controlled vocabulary for the nominal_resolution attribute.
I will email David Plummer about this, it could be that we can extend the nominal_resolution controlled vocabulary to include "2x2 degree"

David has replied and says he'll look into extending the CV list for nominal_resolution to include "2x2 degree"

From David:
"I just double-checked and the list of options for nominal_resolution in CCMI2022_CV.json is identical to the list for CMIP6_CV.json. There is one entry in degrees (1x1 degree), but all of the other entries are in km. I am not sure of the reasoning, but I would assume the resolution should be expressed as a rough equivalent in km. Using the usual rule of thumb that 1 degree is roughly equivalent to 100 km, 2 degrees would be closest to 250 km. I suggest to leave the CV as it is and request nominal_resolution be expressed in km."


Include MR Feature Tool step by step instructions for Beginner HL2 tutorial

"Importing Mixed Reality Toolkit" section of "Beginner MRTK Tutorials" > "2. Initializing your project and deploying your first application" should include step by step instructions for importing the MRTK Foundation packages using the Mixed Reality Feature Tool in addition to downloading github packages.
The MR Feature Tool should be highlighted as supporting Windows only and that mac support is coming.
Mac users should be directed to use the traditional way of individually downloading/importing MRTK unity packages.

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

ID: 24d36428-004c-e29f-ac5a-602bcbabdb25
Version Independent ID: 01015fb5-d01b-c738-6671-9a0ca9af000e
Content: Initializing your project and deploying your first application - Mixed Reality
Content Source: mixed-reality-docs/mr-dev-docs/develop/unity/tutorials/mr-learning-base-02.md
Product: mixed-reality
Technology: mr-dev
GitHub Login: @jessemcculloch
Microsoft Alias: jemccull

@varunsiddaraju Did this get fixed in the latest tutorial update PR?

Yes, @hferrone This is included in the latest tutorial update PR.


Introspection in serde

Hello,
I think that introspection is a real need, and I was thinking about making a crate for type introspection. I personally want to use that for OpenAPI spec generation (in the paperclip crate), but it will be a general crate I think.
Introspection is needed in many use cases, especially to facilitate interoperability with other languages. Most such use cases are connected to serde - we want to generate a specification of the format we use to communicate with other components, not the Rust struct itself. (these two differ when we use serde attributes like rename, flatten, tag).
As such I found it fitting to ask for a discussion here.
Following https://github.com/serde-rs/serde/issues/345, the conclusion seems to be that any such functionality has to come from some other crate.
So what I have in mind is a crate which is really general, and gives information that can be useful to any application. Maybe it should not treat serde attributes specially but preserve and present all attributes in the runtime schema. As such, usage in conjunction with serde is one use case.
What do I mean with "runtime schema": the approach I'm thinking is some derive macro e.g. Introspection that has a function that returns a struct describing everything about the Rust struct/enum definition. This struct is the "runtime schema".
So I am wondering whether you envision any support for introspection in serde.
Can I design this crate in a way such that you want to include support for it in serde? Thinking something like: If some feature is enabled in serde, then #[derive(Serialize, Deserialize)] will also derive Introspection. Perhaps serde will make its own "runtime schema" struct which takes into account serde's attributes to flatten, rename etc... many possibilities.
Or any other thoughts?

This isn't something that would be accepted into Serde (so I'll close the issue) but it could be implemented on top of Serde, either based on the type information present in Deserialize trait impls:

https://github.com/facebookincubator/serde-reflection

or based on a macro that uses serde_derive_internals to process #[serde(...)] attributes:

https://crates.io/crates/schemars_derive
https://crates.io/crates/typescript-definitions-derive
https://crates.io/crates/reflection_derive
https://crates.io/crates/serde_schema_derive
https://crates.io/crates/wasm-typescript-definition


Premium ZRS Support

Should Premium_ZRS be added to the list of available Azure storage redundancies for creating a storage class?

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

ID: a57e48b4-dc33-0b9d-b773-42ce7d2bffd0
Version Independent ID: e912ac2d-cf6a-0b54-4697-1940b1270874
Content: Dynamically create Azure Files share - Azure Kubernetes Service
Content Source: articles/aks/azure-files-dynamic-pv.md
Service: container-service
GitHub Login: @mlearned
Microsoft Alias: mlearned

Thanks for the issue, I'll take a look.

@Gryczka ,
I've made a PR adding Premium_ZRS to that list of available redundant storage options. Once that PR is approved by the doc author this issue should close. Thanks!


Do not use entrypoint for cp-utility

Description of changes: The operator uses the command property for Init containers, which overrides the ENTRYPOINT the definition inside the docker image.
https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/#entrypoint
https://github.com/open-telemetry/opentelemetry-operator/blob/20ea43a43bbe5ba4a512ffc7742a92d14cc3d7d9/pkg/instrumentation/javaagent.go#L71
This change makes the cp-utility behave exactly like the cp command, not requiring an ENTRYPOINT meaning that cp will not be an argument of the cp-utility anymore.
I simulated what the operator does end to end with the following:
apiVersion: apps/v1
kind: Deployment
metadata:
  name: java-sample-app
  namespace: java-sample-app
spec:
  selector:
    matchLabels:
      app.kubernetes.io/name: java-sample-app
  template:
    metadata:
      name: java-sample-app
      namespace: java-sample-app
      labels:
        app.kubernetes.io/name: java-sample-app
    spec:
      containers:
        - name: java-sample-app
          image: xxxx.dkr.ecr.us-west-2.amazonaws.com/java-sample-app:latest-auto
          imagePullPolicy: Always
          env:
            - name: "OTEL_EXPORTER_OTLP_ENDPOINT"
              value: "http://collector-serv.collector.svc.cluster.local:4317"
            - name: "LISTEN_ADDRESS"
              value: "<IP_ADDRESS>:4567"
            - name: "JAVA_TOOL_OPTIONS"
              value: "-javaagent:/otel-auto-instrumentation/javaagent.jar"
          volumeMounts:
            - name: instrumentation-volume
              mountPath: "/otel-auto-instrumentation"
      serviceAccountName: java-sample-app-serv-acc
      initContainers:
        - name: autoinstrumentation
         # This was created manually
          image: xxxx.dkr.ecr.us-west-2.amazonaws.com/adot-auto-instrumentation:latest
          command: ["cp", "/javaagent.jar", "/otel-auto-instrumentation/javaagent.jar"]
          volumeMounts:
            - name: instrumentation-volume
              mountPath: "/otel-auto-instrumentation"
      volumes:
        - name: cache-volume
          emptyDir:
            sizeLimit: 100Mi

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #377 (c173932) into main (2c581b7) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff            @@
##               main     #377   +/-   ##
=========================================
  Coverage     85.71%   85.71%
  Complexity       19       19
=========================================
  Files             3        3
  Lines            49       49
  Branches          5        5
=========================================
  Hits             42       42
  Misses            3        3
  Partials          4        4

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Wrong generalized inverse masses in solve_vel

I am pretty sure that the generalized inverse masses calculated in solve_vel should be based on the delta_v direction not the collision normal?

Thanks, I believe you're right. I probably just used the normal when I implemented restitution and forgot to change it to the delta_vel direction when I added dynamic friction.
I'll fix this soon, probably as a part of fixing #2 if it ends up being related in any way.

You were right, it's supposed to use the normalized delta_v. Just using normal causes explosive friction in many cases, as can be seen in #47. Thanks for spotting the issue and sorry for fixing it so late 😅


[BUG] -gcflags all="..." option remove all imports for test package

Version of orchestrion
Running main version
Describe what happened:
The compilation of the folder _integration_tests/tests fails when running with some debugger flags.
Command: go test -toolexec "orchestrion toolexec" -tags integration -gcflags all='' ./_integration_tests/tests
Output:

# orchestrion/integration/tests [orchestrion/integration/tests.test]
./suite_test.go:22: undefined: testing
./suite_test.go:23: undefined: require
./suite_test.go:24: undefined: require
./suite_test.go:26: undefined: agent
./suite_test.go:27: undefined: require
./suite_test.go:32: undefined: testing
./suite_test.go:42: undefined: require
./suite_test.go:45: undefined: require
./suite_test.go:47: undefined: trace
./suite_test.go:48: undefined: require
./suite_test.go:48: too many errors
exit status 2
FAIL	orchestrion/integration/tests [build failed]
FAIL

Running with -work created the following file, without the right imports:

// Unless explicitly stated otherwise all files in this repository are licensed
// under the Apache License Version 2.0.
// This product includes software developed at Datadog (https://www.datadoghq.com/).
// Copyright 2023-present Datadog, Inc.

//go:build integration

package tests

//dd:orchestrion-enabled
const orchestrionEnabled =
//line <generated>:1
true

//line ./suite_test.go:22
func Test(t *testing.T) {
	require.True(t, orchestrionEnabled, "this test suite must be run with orchestrion enabled")
	require.NotEmpty(t, suite, "no test case registered")

	mockAgent, err := agent.New(t)
	require.NoError(t, err)
	defer mockAgent.Close()

	for name, tc := range suite {
		tc := tc
		t.Run(name, func(t *testing.T) {
			t.Log("Running setup")
			tc.Setup(t)

			defer func() {
				t.Log("Running teardown")
				tc.Teardown(t)
			}()

			sess, err := mockAgent.NewSession(t)
			require.NoError(t, err)
			defer func() {
				jsonTraces, err := sess.Close(t)
				require.NoError(t, err)

				var traces trace.Spans
				require.NoError(t, trace.ParseRaw(jsonTraces, &traces))
				t.Logf("Received %d traces", len(traces))

				for _, expected := range tc.ExpectedTraces() {
					expected.RequireAnyMatch(t, traces)
				}
			}()

			t.Log("Running test")
			tc.Run(t)
		})
	}
}

Describe what you expected:
I would expect the tests to compile as they do without the -gcflags
Steps to reproduce the issue:
go test -toolexec "orchestrion toolexec" -tags integration -gcflags all='' ./_integration_tests/tests
Additional environment details (Version of Go, Operating System, etc.):

Confusion happened: this is not caused by orchestrion


Discord link is dead

The link to join the discord is dead

This invite may be expired, or you might not have permission to join.

Thanks so much, updating it right now!

Should be good now, I updated the invite to never expire and copied the new link. It looks like the UID is the same, so I'm guessing something got reset on my end for the invite link, but I copied over the new link format anyways.


Use top bar for all confirmation dialogs

UX: currently, VS Code uses two styles of confirmation dialogs:
1. The top bar

2. System dialog

It would be nice to unify those, I think that the first style fits the overall UI much better.

My 2 cents: we should move away from using the message bar as a way to ask for user input. This should only be used for information purpose.

The real problem might be with modality, the message bar probably don't blocks the UI. (I generally dislike modal dialogs but understand some scenarios are "modal" by nature.)
Just from the perception point of view, the message bar UI feels much more pleasant and in-line with the rest of VSCode's UI.

While it is not blocking, the current UI is very bad as it overlaps with the editor-tabs row and typically always is in the way.

Duplicate of https://github.com/Microsoft/vscode/issues/1135


react-toastr version causing duplicate react packages in bundle

Currently, allenfeng/react-toastr locks in React like so:
"react": "^0.14.0 || <15.4.0"

However, I am currently using react 15.4.1, so I have duplicate React packages in my bundle. Thus, react-toastr comprise 5.65% of my bundle. Funnily enough, I don't even use the toastr parts of this package :/
font-awesome: 1.42 MB (13.0%)
lodash: 688.56 KB (6.14%)
@allenfang/react-toastr: 633.7 KB (5.65%)
  react: 580.18 KB (91.6%)
  fbjs: 32.93 KB (5.20%)
  react-dom: 63 B (0.00971%)
  <self>: 20.53 KB (3.24%)

Can you upgrade the dep to allow for newer versions of react?

I saw you comment on https://github.com/AllenFang/react-bootstrap-table/issues/838, close this one and answer there

please check #1216, if you have any concern or question, let me know in #1216


Difficult To Find How to Open the Markdown Editor

Category
Feature Request / Enhancement
What is the current behavior?
My computer got re-imaged so I had to re-install the GitBook Editor.  It took me quite a while to figure how to bring back the Edit Markdown window.
None of the menus at the top have anywhere to choose the Markdown editor.  The drag and drop editor is by default the only window displayed.
I eventually found it under the "?" in the lower right corner. It should be somewhere else in the menu structure such as under "Window" - Toggle Markdown Editor maybe.
What is the desired behavior?
By default, the Markdown Editor should be open or at least it should be easy to find.
Additional information
Windows 10, Chrome

And one more related to this one, could you please allow someone to set as default view the Edit Markdown, to avoid clicking every time on load ? > Edit Markdown

I don't want the markdown editor by default. I need full space for the viewer. How do I turn the MD editor off???

Here is what I am seeing ...

 I don't know what's going on in your case.

I don't want the markdown editor by default. I need full space for the viewer. How do I turn the MD editor off???

☝ ⚠ This UI is communicating that's not possible (!?)
This is a big usability issue...

is anything html writen in your markdown mode ? delete they and save then you can close markdown mode


ChannelName RBAC for executors

Description
Changes proposed in this pull request:

Support of ChannelName RBAC for executors

Testing
Use executors:

helm
kubectl

Sources:

kubernetes
cm-watcher

sources:
  'cm':
    displayName: "Events based on plugin"
    botkube/cm-watcher:
      enabled: true
      config:
        configMap:
          name: cm-watcher-trigger
          namespace: botkube
          event: ADDED
      context: *default-plugin-context

Self-host plugins
make gen-plugins-index
PLUGIN_SERVER_HOST=http://host.k3d.internal go run test/helpers/plugin_server.go
plugins:
  repositories:
    botkube:
      url: http://host.k3d.internal:3000/botkube.yaml

Install botkube:

Add ClusterRole and ClusterRoleBinding
Add channelName RBAC config to your plugins

botkube/helm:
  context: &default-executor-plugin-context
    defaultNamespace: "default"
    rbac:
      group:
        type: ChannelName
        prefix: ""

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: {{ .Values.rbac.channelGroupName }}
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: {{ .Values.rbac.channelGroupName }}
subjects:
- kind: Group
  name: {{ .Values.rbac.channelGroupName }}
  apiGroup: rbac.authorization.k8s.io
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: {{ .Values.rbac.channelGroupName }}
rules:
- apiGroups:
  - '*'
  resources:
  - '*'
  verbs:
  - get
  - watch
  - list

.Values.rbac.channelGroupName is your slack channel name, in which you intend to test this PR.
# executor kubectl
kubectl get pod -n botkube
# source kubernets
kubectl run nginx --image=nginx
# source cm-watcher
kubectl create cm cm-watcher-trigger -n botkube
# executor helm
helm list
helm install --namespace botkube --repo https://charts.bitnami.com/bitnami psql postgresql

During testing add create/update/delete verbs to ClusterRole {{ .Values.rbac.channelGroupName }}.
Check that you don't have permissions when running botkube in a different channel.
Scenario: 2 channels with different RBAC
Create two socketSlack channels and invite Botkube
socketSlack:
  enabled: true
  channels:
    'ch-1':
      name: ch-1
      bindings:
        executors:
          - helm-1
    'ch-2':
      name: 'ch-2'
      bindings:
        executors:
          - helm-2

Define helm executors
executors:
  'helm-1':
    botkube/helm@v1:
      enabled: true
      context:
        defaultNamespace: "botkube"
        rbac:
          group:
            type: Static
            static:
              values: [*static-group-name]
  'helm-2':
    botkube/helm@v1:
      enabled: true
      context:
        defaultNamespace: "botkube"
        rbac:
          group:
            type: Static
            static:
              values: [helm-editor]

helm-1 uses default read only configuration.
helm-2 uses a custom rbac definition helm-editor:
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: helm-editor
rules:
  - apiGroups: ["*"]
    resources: ["*"]
    verbs: ["get", "watch", "list", "update", "create", "delete"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: helm-editor
  labels:
    app.kubernetes.io/name: helm-editor
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: helm-editor
subjects:
- kind: Group
  name: helm-editor
  apiGroup: rbac.authorization.k8s.io

In channel ch-1 list helm targets @Botkube helm list - this should work, as helm-1 has read scope.
Try to apply a target @Botkube helm install --repo https://charts.bitnami.com/bitnami psql postgresql - this should not work.
Try the same in ch-2 - it should work, because helm2 has create scope.
With @Botkube helm list in ch-1 you should see the postgresql target.
Related issue(s)
https://github.com/kubeshop/botkube/issues/934

FYI I used the following config for channel-name based mapping:
communications:
  "default-group":
    socketSlack:
      enabled: true
      appToken: "xapp-"
      botToken: "xoxb-"
      notification:
        type: "short"
      channels:
        "default":
          name: botkube-demo
          bindings:
            executors:
              - helm-3
            sources:
              - k8s-all-events
              - k8s-recommendation-events
        "secondary":
          name: priv-channel
          bindings:
            executors:
              - helm-3
            sources:
              - k8s-recommendation-events
              - k8s-err-events

executors:
  'helm-3':
    botkube/helm@v1:
      enabled: true
      context:
        defaultNamespace: "default"
        rbac:
          group:
            type: ChannelName
    botkube/kubectl:
      enabled: true
      # -- Custom kubectl configuration.
      # @default -- See the `values.yaml` file for full object including optional properties related to interactive builder.
      context:
        defaultNamespace: "default"
        rbac:
          group:
            type: ChannelName

plugins:
  repositories:
    botkube:
      url: https://storage.googleapis.com/botkube-plugins-latest/plugins-index.yaml

helm install botkube -n botkube --create-namespace \
--set image.repository=kubeshop/pr/botkube \
--set image.tag=1023-PR \
-f ~/rbac-testing.values.yaml ./helm/botkube

Resources:
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: priv-channel
rules:
  - apiGroups: ["*"]
    resources: ["*"]
    verbs: ["get", "watch", "list", "update", "create", "delete"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: priv-channel
  labels:
    app.kubernetes.io/name: helm-editor
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: priv-channel
subjects:
- kind: Group
  name: priv-channel
  apiGroup: rbac.authorization.k8s.io
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: reader
rules:
  - apiGroups: ["*"]
    resources: ["*"]
    verbs: ["get", "watch", "list"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: reader
  labels:
    app.kubernetes.io/name: helm-editor
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: reader
subjects:
- kind: Group
  name: botkube-demo
  apiGroup: rbac.authorization.k8s.io

CC @huseyinbabal


Programming a T-Echo with PlatformIO under Windows 10

Do you have a tutorial that shows how to program a T-Echo under Windows 10 and Platformio environment?

https://github.com/Xinyuan-LilyGO/LilyGO-T-Echo#use-platformio

I need more than just a link. At first glance, some explanation is missing.
I may not have installed the correct version of J-Link??!!

The J-link tool is required. As shown in figure https://github.com/Xinyuan-LilyGO/LilyGO-T-Echo/tree/main/bootloader#use-j-link-flash

Thank you for the informations. Which model of SWD interface are you using?

reference.  Article 5 Firmware can be downloaded via USB


How to use with Sapper and SSR?

Hi! I try to use in Sapper app and get this message:

 is not a valid SSR component. You may need to review your build config to ensure that dependencies are compiled, rather than imported as pre-compiled modules

Are any options to use this great component with Sapper and SSR?

I believe it's because flatpickr itself references window. While I'd love to support this directly in this component if we can find a clean way, you should be able to workaround the issue using the dynamic import method detailed in the Sapper docs here: https://sapper.svelte.technology/guide#making-a-component-ssr-compatible

As I can see, you initialize flatpickr only inside onMount hook which shouldn't work on the server, I guess. So, basically, this is the correct way to implement browser-specific things inside the components.
I'm not sure the problem in this, because yesterday I created simple flatpickr action and it's work perfectly with SSR, because actions are also not running on the server.
Should I close this issue or you're interested to provide SSR support for this component?

I'm interested! I think you're right, I can probably switch to using a dynamic import in onMount. I'll take a look soon!

Okay actually, I think the dynamic import isn't required, it looks like svelte-loader and rollup-plugin-svelte just aren't respecting the svelte field in this component's package.json. I have no idea why.
An explicit import 'svelte-flatpickr/src/Flatpickr.svelte' seems to work until this gets figured out.

Okay, I believe it should work if svelte-flatpickr is specified as a devDependency instead of a dependency, assuming you're using the default sapper template. I think this all boils down to loader configuration and there isn't anything that can be changed in this package. I've run into this problem myself in the past, and I had no idea that this was the cause. If this doesn't seem to be the cause of your issue please write back.
https://github.com/sveltejs/sapper-template#using-external-components-with-webpack

I'm gonna close this because I think it's fundamentally a usage configuration issue and not anything I can do in this library. Feel free to write back if I'm mistaken!


Update badges

Fix broken workflow badge (Build, Test, Lint for Master -> Main)
Update all contributors badge

Use updated badge url (ref: https://allcontributors.org/docs/en/bot/faq)
Match style as flat just like other badges
Change color as #ec4815 (I guess it's Tina's main color, right? :) )

Github license badge currently displays not identifiable by github, and I didn't know how to change it, so I left it as is.

 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.


MathJax 2.7.1  test example sample-mml.html  not working on IE 6-8

SCRIPT1028:Expected identifier, string or number
MML_HTMLorMML-full.js，line: 57，colume: 387
IE9+ is fine

Thanks for the report. This is due to https://github.com/mathjax/MathJax-a11y/issues/202 and is fixed in 2.7.2-beta1 (and thus will be fixed in the next release). You can disable the accessibility extensions  to work around the problem, cf. http://docs.mathjax.org/en/latest/options/extensions/a11y-extensions.html.


fix: backup recovery was linking incorrectly dids with private keys

Signed-off-by: Cristian G<EMAIL_ADDRESS>Description:
This PR fixes an issue with the recovery process. QA detected that peer dids where lost and unit tests did not detect that problem.
This is related to ATL-6607
Checklist:

[x] My PR follows the contribution guidelines of this project
[x] My PR is free of third-party dependencies that don't comply with the Allowlist
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have checked the PR title to follow the conventional commit specification

Pull Request Test Coverage Report for Build<PHONE_NUMBER>8
Details

0 of 0   changed or added relevant lines in 0 files are covered.
33 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.04%) to 43.106%

Files with Coverage Reduction
New Missed Lines
%

org/hyperledger/identus/walletsdk/pluto/PlutoRestoreTask.kt
33
69.48%

Totals

Change from base Build<PHONE_NUMBER>2:
0.04%

Covered Lines:
3007

Relevant Lines:
6113

💛  - Coveralls


Fix Dockerfile to avoid error at container run-time.

Hello!
Sending this PR to attempt at solving #17 .
Let me know what you think 💭
Cheers 🍻

Something else that came to my attention is that the app is asking for a user's input (namely hitting the enter key) after a successful login through email. Is this a mandatory process for the app to work?
https://user-images.githubusercontent.com/42075938/194713675-8af926e5-c2a3-4bdf-8d0d-f81439f07866.mov

I have update the docker file with yarn
Now, it should work 😉


Router version（controller version）

Is it possible to add a uniform public version to the router, or use V1ContactList directly?
// src/controllers/contact/list.ts
import { BaseController, get, Context } from "daruk";

export default class V1ContactList extends BaseController {
  @get("/")
  public async getContactList(ctx: Context, next: Function) {
    ctx.body = "contact list";
    return next();
  }
}

Is there any other way to achieve it? such as
// src/controllers/contact/list.ts
import { BaseController, get, Context, version } from "daruk";

@version('/v1')
export default class ContactList extends BaseController {
  @get("/")
  public async getContactList(ctx: Context, next: Function) {
    ctx.body = "contact list";
    return next();
  }
}

it like a prefix controller decorator.
// src/controllers/contact/list.ts
import { BaseController, get, Context, version } from "daruk";

@prefixPath('/v1')
export default class ContactList extends BaseController {
  @get("/")
  public async getContactList(ctx: Context, next: Function) {
    ctx.body = "contact list";
    return next();
  }
}

the router path use with @prefixPath decorator will be /v1/contact/list,  it's should be better ?

someone could change this line to
this._prefix + method and add a new decorator named "prefix" which add _prefix to target class
https://github.com/daruk-framework/daruk/blob/ef2e002d2feb48575f02587e36fb67720b49260a/src/decorators/http_methods.ts#L68

someone could change this line to
this._prefix + method and add a new decorator named "prefix" which add _prefix to target class
https://github.com/daruk-framework/daruk/blob/ef2e002d2feb48575f02587e36fb67720b49260a/src/decorators/http_methods.ts#L68

https://github.com/daruk-framework/daruk/commit/7a48705c7fa5768030c7902980f5748aa62ed472
@Chersquwn  next version will be available


runtime: windows/amd64 crash in -buildmode=c-shared library

What version of Go are you using (go version)?

$ go version
go version go1.20.3 linux/amd64

Does this issue reproduce with the latest release?
Yes.
It is actually a regression compared to 1.19.8. Where this crash is not happening.

Cross compiling with -buildmode=c-shared from linux/amd64 for windows/amd64 with cgo enabled.
For cgo, regular MinGW/GCC as well as MinGW/LLVM compiler have been tried.
https://github.com/fzwoch/obs-teleport (project's code)
What did you expect to see?
The resulting .dll file is a plugin for https://github.com/obsproject/obs-studio
I expected that application to successfully load the shared library.
It does so when the plugin is compiled with go1.19.8 linux/amd64.
What did you see instead?
Getting the following runtime crash when loading the library in OBS Studio.
Unfortunately no more details. I have no particular good knowledge on how to produce proper debug versions/stack traces with MSVC.

Closing as duplicate of https://github.com/golang/go/issues/59213.


refactor: split tests into multiple steps

Description, Motivation and Context
https://x.com/housecor/status/1816867564796117228
Types of changes

[x] 🛠 Tool
[x] 🧪 Test
[x] 🧠 Refactor

I am confused (even after reading the tweet) about why it improves performance, as you were already using page.goto() only once per test.
How does test.step improves things ? Reading the doc I think it only improves readability by splitting long tests into smaller tests. Am I right that our tests were already performant because page was already loaded only once ?


App crashes while loading

Avoid duplicates

[X] Bug is not mentioned in the FAQ
[X] Bug is specific for iOS only, for general issues / questions that apply to iOS and Android please raise them in the documentation repository
[X] Bug is not already reported in another issue

Technical details

Device name: iPhone XR
iOS version: 15.4.1
App version: 2.21.2

Describe the bug
The CWA crashes (only shows a black screen) if it is in the loading screen and is closed. Here's a screen recording:
https://user-images.githubusercontent.com/67682506/166123014-1011cf2e-7cab-408b-a5c0-2aa18671bfe3.mp4
Steps to reproduce the issue

Open the app so that it shows the loading screen
Close the app (don't swipe out of memory)
Open the app again
See that only a black screen is shown until the app is hard closed and re-opened

Expected behaviour
The app should continue to load as normal and not crash/hang.
Internal Tracking ID: EXPOSUREAPP-

Thanks for your report @Ein-Tim. We have created an internal ticket for it and will raise this topic internally.
Internal Tracking ID: EXPOSUREAPP-12982

Corona-Warn-App Open Source Team

FYI https://github.com/corona-warn-app/cwa-app-ios/pull/4507

I saw the same today.
Details:

I opened cwa. WLAN was available, but internet connection was down.
cwa saw the WLAN and started an attempt to download the keys.
I did't wait for any timeout but closed cwa to disable WLAN and force internet connection via mobile / over-the-air.
then I started cwa again - but it was blackscreen only

cwa 2.22.1 / iOS 15.4.1 / iPhone 13 Pro

I'll try following my steps to reproduce and check if this is still an issue with version 2.23.

Good morning @Ein-Tim , indeed, feedback is appreciated!


[Firebase Analytics] setAnalyticsCollectionEnabled(false) has no effect on iOS

Describe the bug
FirebaseAnalytics().setAnalyticsCollectionEnabled(false); does not deactivate data collection on iOS.
To Reproduce
Call setAnalyticsCollectionEnabled(false) on your instance of FirebaseAnalytics. The Xcode log prints [Firebase/Analytics][I-ACS023012] Analytics enabled. All events are transmitted to the Firebase console.
Expected behavior
Transmission of events stops.
Additional context
The platform channel invokes the native iOS method in FirebaseAnalyticsPlugin.m:
} else if ([@"setAnalyticsCollectionEnabled" isEqualToString:call.method]) {
  NSNumber *enabled = [NSNumber numberWithBool:call.arguments];
  [FIRAnalytics setAnalyticsCollectionEnabled:[enabled boolValue]];
  result(nil);
}

call.arguments is of type __NSCFBoolean and the subsequent lines always convert the value that is passed to FIRAnalytics to true.
Add this code to the else if:
if ((int)call.arguments == 279097312) { // if passed false: 279097336
  NSLog(@"TRUE ARGUMENT WILL SET COLLECTION TO %@", [[NSNumber numberWithBool:call.arguments] boolValue] ? @"TRUE" : @"FALSE");
} else {
  NSLog(@"FALSE ARGUMENT WILL SET COLLECTION TO %@", [[NSNumber numberWithBool:call.arguments] boolValue] ? @"TRUE" : @"FALSE");
}

It prints
Runner[8875:2258309] TRUE ARGUMENT WILL SET COLLECTION TO TRUE
or
Runner[8875:2258309] FALSE ARGUMENT WILL SET COLLECTION TO TRUE.

flutter --version
Flutter 1.8.3 • channel beta • https://github.com/flutter/flutter.git
Framework • revision e4ebcdf6f4 (6 weeks ago) • 2019-07-27 11:48:24 -0700
Engine • revision 38ac5f30a7
Tools • Dart 2.5.0 (build 2.5.0-dev.1.0 0ca1582afd)

This code works:
} else if ([@"setAnalyticsCollectionEnabled" isEqualToString:call.method]) {
  [FIRAnalytics setAnalyticsCollectionEnabled:[call.arguments boolValue]];
  result(nil);
}

I just skipped the first conversion step.

@ToniTornado would you be willing to produce a PR with that change? Seems to be a pretty quick fix.

@kroikie Yes it is a quick fix but I'm not sure about any implications?
There are similar code fragments for InAppMessaging (that I'm not using) in FirebaseInAppMessagingPlugin.m:
} else if ([@"setMessagesSuppressed" isEqualToString:call.method]) {
  NSNumber *suppress = [NSNumber numberWithBool:call.arguments];
  FIRInAppMessaging *fiam = [FIRInAppMessaging inAppMessaging];
  fiam.messageDisplaySuppressed = [suppress boolValue];
  result(nil);
} else if ([@"setAutomaticDataCollectionEnabled" isEqualToString:call.method]) {
  NSNumber *enabled = [NSNumber numberWithBool:call.arguments];
  FIRInAppMessaging *fiam = [FIRInAppMessaging inAppMessaging];
  fiam.automaticDataCollectionEnabled = [enabled boolValue];
  result(nil);
}

I changed these lines too.

The main bug has now been fixed in master v5.0.2. But I still recommend to fix the other plugin too. I updated my PR.

still see the analytics reports the "first_open" event when the flag is set as "false" in debug mode with iOS simulator. but doesn't report other events if the app is opened once.
  firebase_core: ^0.4.0+6
  firebase_crashlytics: ^0.1.0+3
  firebase_analytics: ^5.0.2

class GrowSState extends State<GrowS> {
FirebaseAnalytics analytics = FirebaseAnalytics();

  @override
  void initState() {
    super.initState();

    if (sys_utils.buildMode == sys_utils.BuildMode.release) {
      analytics.setAnalyticsCollectionEnabled(true);
    } else {
      analytics.setAnalyticsCollectionEnabled(false);
    }
  }

@moroumo setAnalyticsCollectionEnabled is meant to update the analytics collection mode of the app. If analytics is enabled before setAnalyticsCollectionEnabled is used to disable analytics events will be logged till execution of setAnalyticsCollectionEnabled is complete.
To see how to configure the initial state of analytics collection see the docs
@ToniTornado I'm closing this issue, setAnalyticsCollectionEnabled now works on iOS.


Remove print-init subcommand from swift-parser-cli

debugInitCall, which is the backbone of swift-parser-cli is defined in _SwiftSyntaxTestSupport, which links against XCTest. If swift-parser-cli links against _SwiftSyntaxTestSupport, it also links against XCTest, causing its execution to fail with a dyld error outside of Xcode.
The solution would be to move debugInitCall into a new module that swift-parser-cli can link against but IMHO the print-init subcommand doesn’t provide sufficent value for that since you most likely want to use it in test cases where you can use a debugger command to get the debugInitCall result: e print(tree.debugInitCall).

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test macOS

@swift-ci Please test

Unfortunate. I'd still be fine with it being a part of SwiftSyntax (behind SPI if you really care) - it seems like a generally useful function to me 🤷.

It can’t be part of SwiftSyntax because it uses SwiftSyntaxBuilder. We could add it to the SwiftSyntaxBuilder module but that also really doesn’t seem like the right place to put it.


fix: macos toolbar button not hidden

before:

after:

hidden these button

@bitsdojo  wants to merge

it is not work, please confirm it. thanks!

it is not work, please confirm it. thanks!

@friday-s @luo10
The buttons are not supposed to be hidden 👀 🚨


(maint) Update acceptance config of OSX/Win for puppet-strings 2.9

Following up on 806852ae, two of our internal acceptance test platforms, osx12 and windows19 have older Rubies and Rubygems (2.6, 2.5) that are neither compatible with puppet-strings 3, nor capable of recognizing that they need to downshift to 2.x. So this commit updates the presuite to force installation of puppet-strings 2.9.0 ahead of installing the test bolt gem on those platforms.

This cleared up our two acceptance failures installing the bolt gem in my local manual testing.


Given no tournament exists in the tenant, when all tournaments are requested, an empty array should be returned.

@DanielLarsenNZ - Just pulled my hair out as to why I was getting error 204 - No Content on GET /tournaments. Isn't a 200 response with an empty array more suited in this scenario?
Given no tournaments exist for the tenant, when GET /tournaments is called, then we should get a 200 - OK and empty array because we are not saying it is an error that no data exists, there is just nothing there (hence []).

On it


UK ordering

set the order for UK contacts
rename resources files (but leave ids unchanged so that translation files are unaffected)
move 1 record from 'england' folder
add Local Chapter, Twitter, and London Twitter

The resource file renaming changes the order that some of the keys appear in /i18n/en.yml

Thanks for these updates and welcome! 👋


Remove locations with no space from consideration for interventions

In certain cases it seems the MCDA is selecting locations with no available space for seeding deployments.
This PR ensures such locations are removed from consideration.

@Rosejoycrocker I'm going to merge directly but tagging you here so you are aware of this change.


R markdown code chunk not executable after saving

Describe the bug
The code chunk works perfectly before I named and saved the file. The following code, without naming and saving, can be linted and produce the right plot in vs code plot pane. But the same chunk will be no longer executable, and not linted, after I gave the file a name (such as test.Rmd) and saved the file.
To Reproduce
Steps to reproduce the behavior:

press ctrl+N, choose file type as .Rmd
type in the following code

test <- rnorm(1000)
plot(test)

the code chunk was linted and if you run the code chunk, it works perfectly with a plot pane shows up
save the file with name "test.Rmd"
the lint disappeared,  and the code chunk was no longer executable.

Do you want to fix by self? (We hope your help!)
No
Expected behavior
I would like the code executable after the .Rmd file is named and saved.
Screenshots
when unsaved, everything works fine.

after naming and saving, the code chunk is not executable

Environment (please complete the following information):

OS: Windows 10
VSCode Version: 1.65.2
R Version: 4.1.2
vscode-R version: 2.4.0

additional information
This is my first time raising an issue, please let me know if there is anything improper in my request.

Looks like the file language is misspecified. What if you choose rmd language explicitly?

Mr. Ren, thanks for your reply! And I love your book Learning R Programming.
I did specified the file language as r markdown, and vs code automatically assign the file name untitled.rmd to the file. I made another screenshot to show my problem as following.
The left editor pane shows the file named as test.Rmd, the middle pane is file Untitled with no suffix, the right pane is what I did as in the original post: Ctrl +N, click "select a language", chose r markdown, and vs code automatically name the file asUntitled-2.Rmd. And again, once I saved the file in the right pane, the linting and executability disapeared.

I do think there may be some configuration problems on my side, but I searched the whole web without finding a solution. Please help me.
Thanks!

Looks like the file language is misspecified. What if you choose rmd language explicitly?

Is there anything set in settings.json regarding RMarkdown?

Thanks eitsupi. Yes, there are.  I made a minor change and solve the problem partly.
I think the relative settings are as following:
{
    "files.associations": {
        "*.rmd": "markdown"
    },
    "[markdown]": {
        "editor.defaultFormatter": "yzhang.markdown-all-in-one"
    "markdown-preview-enhanced.pandocPath": "C:\\Program Files\\Pandoc\\pandoc.exe",
    "r.rmarkdown.chunkBackgroundColor": "rgba(128, 128, 128, 0.1)",
    "r.rmarkdown.knit.defaults.knitWorkingDirectory": "workspace root",
    "r.rmarkdown.knit.openOutputFile": true,
}

I changed the above settings into this:
{
    "files.associations": {
        "*.rmd": "rmarkdown"  # I changed it to "rmarkdown"
    },
    "[markdown]": {
        "editor.defaultFormatter": "yzhang.markdown-all-in-one"
    "markdown-preview-enhanced.pandocPath": "C:\\Program Files\\Pandoc\\pandoc.exe",
    "r.rmarkdown.chunkBackgroundColor": "rgba(128, 128, 128, 0.1)",
    "r.rmarkdown.knit.defaults.knitWorkingDirectory": "workspace root",
    "r.rmarkdown.knit.openOutputFile": true,
}

And some good things happened that I can run the code chunk after naming and saving the .Rmd file! as following screenshot shows.

However, another problem still exists. After I save and close the editor pane and reopen the same rmarkdown file, the linting and executability are gone, as following.

    "files.associations": {
        "*.rmd": "markdown"
    },

    "files.associations": {
        "*.rmd": "rmarkdown"  # I changed it to "rmarkdown"
    },

Undoubtedly the problem is these lines. These lines are unnecessary.

Confirmed! It worked on my PC.
Actually I did not touch the .jason files, I have no idea where they came from....
Many thanks!

The problem was caused by opening an R Markdown file as a Markdown file.
If you remove the offending setting, the default setting will be applied and it should work as normal.

Rmd rendering and codelens only works for me with the below 1 line settings.json.
{ "files.associations": {  "*.Rmd":"rmd"  }}

Rendering/odelens does not work with empty settings.json. Rmd associates w/ R Markdown in both cases.  This setting seems to fix everything, maybe add it to docs?

@tomule https://github.com/REditorSupport/vscode-R/wiki/R-Markdown#file-association is added to the wiki.


Adding LESFMIP and Automating CV generation

Added LESF MIP related items
Automated CV creation on push.
Reorganisation of the CVs and their structure.
Additional metadata added.

Update: some old version headers remain (e.g. CMIP6Plus_experiment_id)

Versioning implementation functional: awaiting comments or review.
@durack1 @matthew-mizielinski

Nice work @wolfiex. I'm happy for you to tag and release at your leisure.


OC-409 ~ Updated default value for firmware.domain

This pull request makes the build fail.

All is well.


As a key stakeholder, I want to be able to receive periodical e-mails of user feedback so that I can complete the feedback loop and figure out who has been commenting what.

[ ] Break this up into smaller tasks

Heads up: This one will probably be a doozy and will consist of a bunch of smaller tasks which will need to be hammered out. We may need to push some of those tasks to a bunch of future sprints where necessary.

i was envisioning add a question where the customer will select from the below sections and that feedback record would route to the emails associated (i have those, just not listing here:
Health
Fire
Contractor Licensing (Boards and Code)
Building
Electrical
Plumbing
Mechanical
Zoning
Neighborhood Compliance / Code Violations
Environmental Resources Management (DERM)
Cashier
Permit Application Intake and Information
Microfilm

Ernie to start break this up into smaller tasks

#298 is related.


Attribute to upload the file

def index() -> xt.Component:
    layout = xt.box(
        # xt.title("Resume Search App"),
        xt.file_uploader("Upload your resume", on_change=on_file_upload),
        xt.text_input("Enter the text which you want to search: ", bind="search_text"),
        xt.button("Search", on_click=search_resume),
        xt.stack(
            [xt.box(result, style={"margin_bottom": "10px"}) for result in xt.bind("search_results")]
        ),
    )
    return layout

May I kindly request that someone inform me of the appropriate attribute to upload the pdf or document file?

For this you can use the xt.upload component . Added reference for the component
xt.upload
What's it do?

Lets users upload files from their device to your app.
You can customize xt.upload's appearance and behavior to fit your needs.

How to Use It:

Add it to your view:
Create a simple upload area in your app:
xt.upload(
    xt.text("Drag and drop files here or click to select files"),
),

Customize its look and feel (optional):

Content: Add informative text, buttons, or other components within it.
Styling: Apply borders, padding, and colors to align with your app's design.

xt.upload(
    xt.text("Drag and drop files here or click to select files"),
    border="1px dotted rgb(107,99,246)",
    padding="2em",
),

Control what's uploaded:

Accepted file types: Specify using the accept property (e.g., accept={'image/*': ['.png', '.jpg', '.jpeg', '.gif']}).
File limits: Set maximum file size and number of files using max_size and max_files.
Multiple files: Enable simultaneous uploads with multiple=True.

xt.upload(
    accept={'image/*': ['.png', '.jpg', '.jpeg', '.gif']},
    max_files=5,
    max_size=10*1024*1024,  # 10MB
    multiple=True
)

Handle file uploads:

Event handler creation: Craft a function to process the selected files.
Trigger binding: Attach this function to a trigger, such as a button's on_click event.
File access: Retrieve uploaded files within the handler using xt.upload_files().

import nextpy as xt

class State(xt.State):
    """The app state."""

    img: list[str]  # The images to show.

    async def handle_upload(self, files: list[xt.UploadFile]):
        """Handle the upload of file(s).

        Args:
            files: The uploaded files.
        """
        for file in files:
            upload_data = await file.read()
            outfile = xt.get_asset_path(file.filename)

            # Save the file.
            with open(outfile, "wb") as file_object:
                file_object.write(upload_data)

            # Update the img var.
            self.img.append(file.filename)

def index():
    """The main view."""
    return xt.vstack(
        xt.upload(
            xt.text("Drag and drop files here or click to select files"),
            border="1px dotted rgb(107,99,246)",
            padding="2em",
            multiple=True,
            accept={
               "application/pdf": [".pdf"],
               "image/jpeg": [".jpg", ".jpeg"],
               "image/gif": [".gif"],
               "image/png": [".png"],
               "image/webp": [".webp"],
               "text/html": [".html", ".htm"],
            },
            max_files=5,
        ),
        xt.hstack(xt.foreach(xt.selected_files, xt.text)),
        xt.button(
            "Upload",
            on_click=lambda: State.handle_upload(xt.upload_files()),
        ),
        xt.button(
            "Clear",
            on_click=xt.clear_selected_files,
        ),
        xt.foreach(
            State.img,
            lambda img: xt.image(src=img)
        ),
    )

# Create the app.
app = xt.App()
app.add_page(index)

Customizable Properties:
Properties Table

Prop Name
Type
Description

accept
Dict[str, List]
Specifies the types of files that the server accepts.

disabled
bool
If True, disables the component.

max_files
int
Maximum number of files that can be uploaded at once.

max_size
int
Maximum size for a file in bytes.

min_size
int
Minimum size for a file in bytes.

multiple
bool
Allows multiple files to be selected if True.

no_click
bool
Disables the click event to trigger file upload.

no_drag
bool
Disables the drag-and-drop feature.

no_keyboard
bool
Disables keyboard interaction for triggering file upload.

style
Style
Custom CSS styles for the component.

Event Triggers

on_drop: Triggered when files are dropped into the dropzone.
on_click: Triggered when the component is clicked.
More event triggers can be implemented based on the app's requirements.

Notes

Ensure that the accept prop follows the correct format for specifying MIME types.
For security reasons, it's essential to validate the uploaded files on the server side.

Best Practices

Always use the UploadFilesProvider to wrap around areas where files will be uploaded to manage the state properly.
Customize the appearance of the upload area with CSS to align with your application's theme.
Provide feedback to the user upon successful or failed uploads through event handlers.

Thanks!

After clicking the upload button, I see this

Hey Anirudh, Can you share your code?

Hey Anirudh, Can you share your code?

import nextpy as xt
class State(xt.State):
"""The app state."""
img: list[str]  # The images to show.

async def handle_upload(self, files: list[xt.UploadFile]):
    """Handle the upload of file(s).

    Args:
        files: The uploaded files.
    """
    for file in files:
        upload_data = await file.read()
        outfile = xt.get_asset_path(file.filename)

        # Save the file.
        with open(outfile, "wb") as file_object:
            file_object.write(upload_data)

        # Update the img var.
        self.img.append(file.filename)

def index():
"""The main view."""
return xt.vstack(
xt.upload(
xt.text("Drag and drop files here or click to select files"),
border="1px dotted rgb(107,99,246)",
padding="2em",
multiple=True,
accept={
"application/pdf": [".pdf"],
"image/jpeg": [".jpg", ".jpeg"],
"image/gif": [".gif"],
"image/png": [".png"],
"image/webp": [".webp"],
"text/html": [".html", ".htm"],
},
max_files=5,
),
xt.hstack(xt.foreach(xt.selected_files, xt.text)),
xt.button(
"Upload",
on_click=lambda: State.handle_upload(xt.upload_files()),
),
xt.button(
"Clear",
on_click=xt.clear_selected_files,
),
xt.foreach(
State.img,
lambda img: xt.image(src=img)
),
)
Create the app.
app = xt.App()
app.add_page(index) As you mentioned, any errors please suggest me

Hey Anirudh, Can you share your code?

import nextpy as xt

class State(xt.State):
    """The app state."""

    img: list[str]  # The images to show.

    async def handle_upload(self, files: list[xt.UploadFile]):
        """Handle the upload of file(s).

        Args:
            files: The uploaded files.
        """
        for file in files:
            upload_data = await file.read()
            outfile = xt.get_asset_path(file.filename)

            # Save the file.
            with open(outfile, "wb") as file_object:
                file_object.write(upload_data)

            # Update the img var.
            self.img.append(file.filename)

def index():
    """The main view."""
    return xt.vstack(
        xt.upload(
            xt.text("Drag and drop files here or click to select files"),
            border="1px dotted rgb(107,99,246)",
            padding="2em",
            multiple=True,
            accept={
               "application/pdf": [".pdf"],
               "image/jpeg": [".jpg", ".jpeg"],
               "image/gif": [".gif"],
               "image/png": [".png"],
               "image/webp": [".webp"],
               "text/html": [".html", ".htm"],
            },
            max_files=5,
        ),
        xt.hstack(xt.foreach(xt.selected_files, xt.text)),
        xt.button(
            "Upload",
            on_click=lambda: State.handle_upload(xt.upload_files()),
        ),
        xt.button(
            "Clear",
            on_click=xt.clear_selected_files,
        ),
        xt.foreach(
            State.img,
            lambda img: xt.image(src=img) please suggest the changes
        ),
    )

# Create the app.
app = xt.App()
app.add_page(index)

Looks like the code's running smoothly on my end. Maybe giving Nextpy an update could help? Just run pip install --upgrade nextpy and see if that does the trick.


Config panel: support min and max value for integer inputs

I think the config manager should also return the appropriate values as well to avoid checks like this in the plugins. In the current state of this PR, people making new plugins would assume that the config manager does the validation already, so they wouldn't put in validation code.
This is also in case people manually change the settings file. Or in the current live case, where people have their GPU draw distance greater than 90.

ConfigManager isn't aware of the ConfigItem when configurations are fetched. When the panel is opened again, it will be constrained.

I haven't looked into how the config is rendered much so I don't know how easy this is to implement but, I think a better way to show this in the UI is a JSlider rather than a JSpinner


May I ask what your file directory looks like?

please see this doc.

If you want to inference the pretrained model, you can directly download the google drive folder to the current directory.

i have read readme,but "pretrain_path='MiCo-g'" made me confused

You can directly download the google drive folder to the current directory, the pretrained models are zipped in the "MiCo-g" folder on my google drive.

Sorry, I cannot find ‘MiCo-g’ folder on google driver, although I find ‘MiCo-g’ in your code.

Sorry, I just found that it's named "MiCo" on the google drive...You can simply rename the folder and run the inference code.

ohh,i got it. thanks for your answer

Thanks for your efforts! I will also update this in the README.md soon


.slugignore file is not used to ignore certain file(s)

I deployed latest Flynn to DO with CLI v20160107.0.
I deploy a java app with package.json file at the root. I also have .slugignore file at the root to ignore package.json file so Heroku will not detect the app as NodeJS app.
However, Flynn failed to use .slugignore file to exclude package.json file before detect app type (and detected as NodeJS app).
Work around is to specify custom buildpack
However, I am not sure whether Flynn is going to support .slugignore file or not. If no, this no longer valid issue.

This is a bug, we expect .slugignore to work.
Generally speaking Heroku compatibilities are considered bugs and we really appreciate reports.
Thanks for bringing to our attention we will get it patched.

Ok, looks like what needs to happen here is .slugignore functionality needs to move from being a tar exclude to actually deleting the files before the buildpacks are run. Unfortunately it also seems to support paths with leading slashes, blank lines and comments so will require a little bit of processing. Some old discussion here: https://github.com/flynn-archive/slugbuilder/issues/1


Network inspection for OkHttp + Retrofit issue

Hi Guys,
First of all, thanks for your job, great project!
I'm trying to setup Stetho, but I don't see any network calls in Network tab.
Here is my OkHttpClient initialization:
...
OkHttpClient client = new OkHttpClient();
client.networkInterceptors().add(new StethoInterceptor());

Then I create RestAdapter with this client
return new RestAdapter.Builder()
                .setEndpoint(endpoint)
                .setClient(new OkClient(okHttpClient))
                ...

I use 2.2.0:
compile 'com.squareup.okhttp:okhttp:2.2.0'

This is in my Application class:
Stetho.initialize(
                Stetho.newInitializerBuilder(this)
                        .enableDumpapp(Stetho.defaultDumperPluginsProvider(this))
                        .enableWebKitInspector(Stetho.defaultInspectorModulesProvider(this))
                        .build());

If I open console I see "Powered by Stetho", but I don't see any network calls.
But Retrofit display full logs fine.
What I'm doing wrong? :)
Thanks.

You need to pass the client (with interceptors) into the RestAdapter Builder:
setClient(new OkClient(okHttpClient))
should read:
setClient(client)

@fingertricks, that's exactly how it works. I just use dagger, so client just returned from @Provides method. And Injects as okHttpClient.
I can't use setClient(client), as Retrofit requires OkClient, inside it I can pass my custom OkHttpClient.

Are you using Retrofit <= 1.8?  According to
https://github.com/square/okhttp/wiki/Interceptors, it won't work on that older version without some additional effort.

Interceptors he is using were not available in Retrofit 1.8.
I'm having the same issue. In the logs I see:
W/System.err﹕ java.io.IOException: Address already in use
W/System.err﹕ at android.net.LocalSocketImpl.bindLocal(Native Method)
W/System.err﹕ at android.net.LocalSocketImpl.bind(LocalSocketImpl.java:303)
W/System.err﹕ at android.net.LocalServerSocket.(LocalServerSocket.java:52)
W/System.err﹕ at com.facebook.stetho.server.LocalSocketHttpServer.bindToSocket(LocalSocketHttpServer.java:278)
W/System.err﹕ at com.facebook.stetho.server.LocalSocketHttpServer.listenOnAddress(LocalSocketHttpServer.java:138)
W/System.err﹕ at com.facebook.stetho.server.LocalSocketHttpServer.run(LocalSocketHttpServer.java:134)
W/System.err﹕ at com.facebook.stetho.Stetho$1.run(Stetho.java:80)
E/stetho﹕ Could not bind to socket.

@antonkrasov let me spin up a quick Retrofit 1.9 + OkHttp 2.2.0 sample app to see if I can debug through the problems locally.
@Tremelune that error is unrelated (but still a bug).  It's a harmless issue but is unintentionally noisy.  I'll fix it soon.

@jasta wow, thanks! I really forgot to update Retrofit, updated OkHttp to 2.2.0, but continue using Retrofit 1.7.0

Same issue, with OkHttp 2.2.0 and Retrofit 1.9.

@Tremelune, seems like I need to reopen then.

@Tremelune I tested this locally and cannot see an issue with Retrofit 1.9.  Can you try adding the logging interceptor mentioned in https://github.com/square/okhttp/wiki/Interceptors.  I'm curious if that is working.  If no, I think your issue is just with interceptors in general.

Yup, I'll see what I can do. I'm hoping for the ol' "clean build" fix...

Updating Retrofit to 1.9.0 didn't help, trying to add logging interceptor.

@jasta LoggingInterceptor from https://github.com/square/okhttp/wiki/Interceptors works fine for me. But Network tab still doesn't show anything.

I confirmed my sample app is working correctly with Retrofit 1.9 and OkHttp 2.2.0.  Source is here: https://github.com/jasta/retrofit-okhttp-stetho-demo
Here's the modified GitHubClient: https://github.com/jasta/retrofit-okhttp-stetho-demo/blob/master/app/src/main/java/com/example/retrofit/GitHubClient.java
Screenshot to prove it :)

@jasta cloning your demo app :) will check it now

@jasta yeah, your demo app works for me. Hmm, let me compare with my project and try to find the reason.

@jasta Wooohoo, thank you :) I found the issue, and it's quite simple: Proguard.
I fixed this for my project by adding:
-keep class com.facebook.stetho.**{ *; }

W/System.err﹕ java.io.IOException: Address already in use
W/System.err﹕ at android.net.LocalSocketImpl.bindLocal(Native Method)
W/System.err﹕ at android.net.LocalSocketImpl.bind(LocalSocketImpl.java:254)
W/System.err﹕ at android.net.LocalServerSocket.<init>(LocalServerSocket.java:52)
W/System.err﹕ at com.facebook.stetho.server.LocalSocketHttpServer.bindToSocket(LocalSocketHttpServer.java:278)
W/System.err﹕ at com.facebook.stetho.server.LocalSocketHttpServer.listenOnAddress(LocalSocketHttpServer.java:138)
W/System.err﹕ at com.facebook.stetho.server.LocalSocketHttpServer.run(LocalSocketHttpServer.java:134)
W/System.err﹕ at com.facebook.stetho.Stetho$1.run(Stetho.java:80)

Just run https://github.com/jasta/retrofit-okhttp-stetho-demo