articles/techniques/toc.yml
:white_check_mark:Succeeded

articles/techniques/working-with-qubits.md
:white_check_mark:Succeeded
View

articles/user-guide/basics.md
:white_check_mark:Succeeded
View

articles/user-guide/index.md
:white_check_mark:Succeeded
View

articles/user-guide/language/expressions.md
:white_check_mark:Succeeded
View

articles/user-guide/language/toc.yml
:white_check_mark:Succeeded

articles/user-guide/language/types.md
:white_check_mark:Succeeded
View

articles/user-guide/quickref/index.md
:white_check_mark:Succeeded
View

articles/user-guide/quickref/iqsharp.md
:white_check_mark:Succeeded
View

articles/user-guide/quickref/toc.yml
:white_check_mark:Succeeded

articles/user-guide/toc.yml
:white_check_mark:Succeeded

articles/user-guide/using-qsharp/control-flow.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/file-structure.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/operations-functions.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/testing-debugging.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/toc.yml
:white_check_mark:Succeeded

articles/user-guide/using-qsharp/variables.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/working-with-qubits.md
:white_check_mark:Succeeded
View

articles/welcome.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Lowestcategoryscore
Spellingissues
Scorecard
Processed

articles/TOC.yml
100
100
0
link
:white_check_mark:

articles/concepts/Glossary.md
80
58
9
link
:white_check_mark:

articles/concepts/circuits.md
79
57
1
link
:white_check_mark:

articles/concepts/pauli-measurements.md
83
67
4
link
:white_check_mark:

articles/concepts/the-qubit.md
70
40
48
link
:white_check_mark:

articles/contributing/api-design-principles.md
85
69
2
link
:white_check_mark:

articles/contributing/style-guide.md
81
57
2
link
:white_check_mark:

articles/libraries/standard/diagnostics.md
81
64
0
link
:white_check_mark:

articles/machines/resources-estimator.md
87
51
0
link
:white_check_mark:

articles/machines/toc.yml
100
100
0
link
:white_check_mark:

articles/relnotes/0.3-migration.md
78
60
1
link
:white_check_mark:

articles/relnotes/index.md
76
41
16
link
:white_check_mark:

articles/user-guide/basics.md
80
50
0
link
:white_check_mark:

articles/user-guide/index.md
83
65
0
link
:white_check_mark:

articles/user-guide/language/expressions.md
85
52
0
link
:white_check_mark:

articles/user-guide/language/toc.yml
100
100
0
link
:white_check_mark:

articles/user-guide/language/types.md
81
52
0
link
:white_check_mark:

articles/user-guide/quickref/index.md
100
100
0
link
:white_check_mark:

articles/user-guide/quickref/iqsharp.md
90
74
1
link
:white_check_mark:

articles/user-guide/quickref/toc.yml
100
100
0
link
:white_check_mark:

articles/user-guide/toc.yml
100
100
0
link
:white_check_mark:

articles/user-guide/using-qsharp/control-flow.md
79
49
1
link
:white_check_mark:

articles/user-guide/using-qsharp/file-structure.md
83
53
0
link
:white_check_mark:

articles/user-guide/using-qsharp/operations-functions.md
80
57
4
link
:white_check_mark:

articles/user-guide/using-qsharp/testing-debugging.md
80
56
1
link
:white_check_mark:

articles/user-guide/using-qsharp/toc.yml
100
100
0
link
:white_check_mark:

articles/user-guide/using-qsharp/variables.md
80
55
3
link
:white_check_mark:

articles/user-guide/using-qsharp/working-with-qubits.md
75
47
4
link
:white_check_mark:

articles/welcome.md
85
66
0
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Lowestcategoryscore
Spellingissues
Scorecard
Processed

articles/TOC.yml
100
100
0
link
:white_check_mark:

articles/concepts/Glossary.md
80
58
9
link
:white_check_mark:

articles/concepts/circuits.md
79
57
1
link
:white_check_mark:

articles/concepts/pauli-measurements.md
83
67
4
link
:white_check_mark:

articles/concepts/the-qubit.md
70
40
48
link
:white_check_mark:

articles/contributing/api-design-principles.md
85
69
2
link
:white_check_mark:

articles/contributing/style-guide.md
81
57
2
link
:white_check_mark:

articles/libraries/standard/diagnostics.md
81
64
0
link
:white_check_mark:

articles/machines/resources-estimator.md
87
51
0
link
:white_check_mark:

articles/machines/toc.yml
100
100
0
link
:white_check_mark:

articles/relnotes/0.3-migration.md
78
60
1
link
:white_check_mark:

articles/relnotes/index.md
76
41
16
link
:white_check_mark:

articles/user-guide/basics.md
80
50
0
link
:white_check_mark:

articles/user-guide/index.md
83
65
0
link
:white_check_mark:

articles/user-guide/language/expressions.md
85
52
0
link
:white_check_mark:

articles/user-guide/language/toc.yml
100
100
0
link
:white_check_mark:

articles/user-guide/language/types.md
81
52
0
link
:white_check_mark:

articles/user-guide/quickref/index.md
100
100
0
link
:white_check_mark:

articles/user-guide/quickref/iqsharp.md
90
74
1
link
:white_check_mark:

articles/user-guide/quickref/toc.yml
100
100
0
link
:white_check_mark:

articles/user-guide/toc.yml
100
100
0
link
:white_check_mark:

articles/user-guide/using-qsharp/control-flow.md
79
49
1
link
:white_check_mark:

articles/user-guide/using-qsharp/file-structure.md
83
53
0
link
:white_check_mark:

articles/user-guide/using-qsharp/operations-functions.md
80
57
4
link
:white_check_mark:

articles/user-guide/using-qsharp/testing-debugging.md
80
56
1
link
:white_check_mark:

articles/user-guide/using-qsharp/toc.yml
100
100
0
link
:white_check_mark:

articles/user-guide/using-qsharp/variables.md
80
55
3
link
:white_check_mark:

articles/user-guide/using-qsharp/working-with-qubits.md
75
47
4
link
:white_check_mark:

articles/welcome.md
85
66
0
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Docs Build status updates of commit 442928c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

articles/TOC.yml
:white_check_mark:Succeeded
View

articles/concepts/Glossary.md
:white_check_mark:Succeeded
View

articles/concepts/circuits.md
:white_check_mark:Succeeded
View

articles/concepts/pauli-measurements.md
:white_check_mark:Succeeded
View

articles/concepts/the-qubit.md
:white_check_mark:Succeeded
View

articles/contributing/api-design-principles.md
:white_check_mark:Succeeded
View

articles/contributing/style-guide.md
:white_check_mark:Succeeded
View

articles/language/file-structure.md
:white_check_mark:Succeeded
View

articles/language/index.md
:white_check_mark:Succeeded
View

articles/language/statements.md
:white_check_mark:Succeeded
View

articles/language/toc.yml
:white_check_mark:Succeeded

articles/language/type-model.md
:white_check_mark:Succeeded
View

articles/libraries/standard/diagnostics.md
:white_check_mark:Succeeded
View

articles/machines/resources-estimator.md
:white_check_mark:Succeeded
View

articles/machines/toc.yml
:white_check_mark:Succeeded

articles/relnotes/0.3-migration.md
:white_check_mark:Succeeded
View

articles/relnotes/index.md
:white_check_mark:Succeeded
View

articles/techniques/file-structure.md
:white_check_mark:Succeeded
View

articles/techniques/going-further.md
:white_check_mark:Succeeded
View

articles/techniques/index.md
:white_check_mark:Succeeded
View

articles/techniques/local-variables.md
:white_check_mark:Succeeded
View

articles/techniques/operations-and-functions.md
:white_check_mark:Succeeded
View

articles/techniques/putting-it-all-together.md
:white_check_mark:Succeeded
View

articles/techniques/toc.yml
:white_check_mark:Succeeded

articles/techniques/working-with-qubits.md
:white_check_mark:Succeeded
View

articles/user-guide/basics.md
:white_check_mark:Succeeded
View

articles/user-guide/index.md
:white_check_mark:Succeeded
View

articles/user-guide/language/expressions.md
:white_check_mark:Succeeded
View

articles/user-guide/language/toc.yml
:white_check_mark:Succeeded

articles/user-guide/language/types.md
:white_check_mark:Succeeded
View

articles/user-guide/quickref/index.md
:white_check_mark:Succeeded
View

articles/user-guide/quickref/iqsharp.md
:white_check_mark:Succeeded
View

articles/user-guide/quickref/toc.yml
:white_check_mark:Succeeded

articles/user-guide/toc.yml
:white_check_mark:Succeeded

articles/user-guide/using-qsharp/control-flow.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/file-structure.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/operations-functions.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/testing-debugging.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/toc.yml
:white_check_mark:Succeeded

articles/user-guide/using-qsharp/variables.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/working-with-qubits.md
:white_check_mark:Succeeded
View

articles/welcome.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 442928c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

articles/TOC.yml
:white_check_mark:Succeeded
View

articles/concepts/Glossary.md
:white_check_mark:Succeeded
View

articles/concepts/circuits.md
:white_check_mark:Succeeded
View

articles/concepts/pauli-measurements.md
:white_check_mark:Succeeded
View

articles/concepts/the-qubit.md
:white_check_mark:Succeeded
View

articles/contributing/api-design-principles.md
:white_check_mark:Succeeded
View

articles/contributing/style-guide.md
:white_check_mark:Succeeded
View

articles/language/file-structure.md
:white_check_mark:Succeeded
View

articles/language/index.md
:white_check_mark:Succeeded
View

articles/language/statements.md
:white_check_mark:Succeeded
View

articles/language/toc.yml
:white_check_mark:Succeeded

articles/language/type-model.md
:white_check_mark:Succeeded
View

articles/libraries/standard/diagnostics.md
:white_check_mark:Succeeded
View

articles/machines/resources-estimator.md
:white_check_mark:Succeeded
View

articles/machines/toc.yml
:white_check_mark:Succeeded

articles/relnotes/0.3-migration.md
:white_check_mark:Succeeded
View

articles/relnotes/index.md
:white_check_mark:Succeeded
View

articles/techniques/file-structure.md
:white_check_mark:Succeeded
View

articles/techniques/going-further.md
:white_check_mark:Succeeded
View

articles/techniques/index.md
:white_check_mark:Succeeded
View

articles/techniques/local-variables.md
:white_check_mark:Succeeded
View

articles/techniques/operations-and-functions.md
:white_check_mark:Succeeded
View

articles/techniques/putting-it-all-together.md
:white_check_mark:Succeeded
View

articles/techniques/toc.yml
:white_check_mark:Succeeded

articles/techniques/working-with-qubits.md
:white_check_mark:Succeeded
View

articles/user-guide/basics.md
:white_check_mark:Succeeded
View

articles/user-guide/index.md
:white_check_mark:Succeeded
View

articles/user-guide/language/expressions.md
:white_check_mark:Succeeded
View

articles/user-guide/language/toc.yml
:white_check_mark:Succeeded

articles/user-guide/language/types.md
:white_check_mark:Succeeded
View

articles/user-guide/quickref/index.md
:white_check_mark:Succeeded
View

articles/user-guide/quickref/iqsharp.md
:white_check_mark:Succeeded
View

articles/user-guide/quickref/toc.yml
:white_check_mark:Succeeded

articles/user-guide/toc.yml
:white_check_mark:Succeeded

articles/user-guide/using-qsharp/control-flow.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/file-structure.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/operations-functions.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/testing-debugging.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/toc.yml
:white_check_mark:Succeeded

articles/user-guide/using-qsharp/variables.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/working-with-qubits.md
:white_check_mark:Succeeded
View

articles/welcome.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Lowestcategoryscore
Spellingissues
Scorecard
Processed

articles/TOC.yml
100
100
0
link
:white_check_mark:

articles/concepts/Glossary.md
80
58
9
link
:white_check_mark:

articles/concepts/circuits.md
79
57
1
link
:white_check_mark:

articles/concepts/pauli-measurements.md
83
67
4
link
:white_check_mark:

articles/concepts/the-qubit.md
70
40
48
link
:white_check_mark:

articles/contributing/api-design-principles.md
85
69
2
link
:white_check_mark:

articles/contributing/style-guide.md
81
57
2
link
:white_check_mark:

articles/libraries/standard/diagnostics.md
81
64
0
link
:white_check_mark:

articles/machines/resources-estimator.md
87
51
0
link
:white_check_mark:

articles/machines/toc.yml
100
100
0
link
:white_check_mark:

articles/relnotes/0.3-migration.md
78
60
1
link
:white_check_mark:

articles/relnotes/index.md
76
41
16
link
:white_check_mark:

articles/user-guide/basics.md
80
50
0
link
:white_check_mark:

articles/user-guide/index.md
83
65
0
link
:white_check_mark:

articles/user-guide/language/expressions.md
85
52
0
link
:white_check_mark:

articles/user-guide/language/toc.yml
100
100
0
link
:white_check_mark:

articles/user-guide/language/types.md
81
52
0
link
:white_check_mark:

articles/user-guide/quickref/index.md
100
100
0
link
:white_check_mark:

articles/user-guide/quickref/iqsharp.md
90
74
1
link
:white_check_mark:

articles/user-guide/quickref/toc.yml
100
100
0
link
:white_check_mark:

articles/user-guide/toc.yml
100
100
0
link
:white_check_mark:

articles/user-guide/using-qsharp/control-flow.md
79
49
1
link
:white_check_mark:

articles/user-guide/using-qsharp/file-structure.md
83
53
0
link
:white_check_mark:

articles/user-guide/using-qsharp/operations-functions.md
80
57
4
link
:white_check_mark:

articles/user-guide/using-qsharp/testing-debugging.md
80
56
1
link
:white_check_mark:

articles/user-guide/using-qsharp/toc.yml
100
100
0
link
:white_check_mark:

articles/user-guide/using-qsharp/variables.md
80
55
3
link
:white_check_mark:

articles/user-guide/using-qsharp/working-with-qubits.md
75
47
4
link
:white_check_mark:

articles/welcome.md
85
66
0
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Lowestcategoryscore
Spellingissues
Scorecard
Processed

articles/TOC.yml
100
100
0
link
:white_check_mark:

articles/concepts/Glossary.md
80
58
9
link
:white_check_mark:

articles/concepts/circuits.md
79
57
1
link
:white_check_mark:

articles/concepts/pauli-measurements.md
83
67
4
link
:white_check_mark:

articles/concepts/the-qubit.md
70
40
48
link
:white_check_mark:

articles/contributing/api-design-principles.md
85
69
2
link
:white_check_mark:

articles/contributing/style-guide.md
81
57
2
link
:white_check_mark:

articles/libraries/standard/diagnostics.md
81
64
0
link
:white_check_mark:

articles/machines/resources-estimator.md
87
51
0
link
:white_check_mark:

articles/machines/toc.yml
100
100
0
link
:white_check_mark:

articles/relnotes/0.3-migration.md
78
60
1
link
:white_check_mark:

articles/relnotes/index.md
76
41
16
link
:white_check_mark:

articles/user-guide/basics.md
80
50
0
link
:white_check_mark:

articles/user-guide/index.md
83
65
0
link
:white_check_mark:

articles/user-guide/language/expressions.md
85
52
0
link
:white_check_mark:

articles/user-guide/language/toc.yml
100
100
0
link
:white_check_mark:

articles/user-guide/language/types.md
81
52
0
link
:white_check_mark:

articles/user-guide/quickref/index.md
100
100
0
link
:white_check_mark:

articles/user-guide/quickref/iqsharp.md
90
74
1
link
:white_check_mark:

articles/user-guide/quickref/toc.yml
100
100
0
link
:white_check_mark:

articles/user-guide/toc.yml
100
100
0
link
:white_check_mark:

articles/user-guide/using-qsharp/control-flow.md
79
49
1
link
:white_check_mark:

articles/user-guide/using-qsharp/file-structure.md
83
53
0
link
:white_check_mark:

articles/user-guide/using-qsharp/operations-functions.md
80
57
4
link
:white_check_mark:

articles/user-guide/using-qsharp/testing-debugging.md
80
56
1
link
:white_check_mark:

articles/user-guide/using-qsharp/toc.yml
100
100
0
link
:white_check_mark:

articles/user-guide/using-qsharp/variables.md
80
55
3
link
:white_check_mark:

articles/user-guide/using-qsharp/working-with-qubits.md
75
47
4
link
:white_check_mark:

articles/welcome.md
85
66
0
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Docs Build status updates of commit d363481:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

articles/TOC.yml
:white_check_mark:Succeeded
View

articles/concepts/Glossary.md
:white_check_mark:Succeeded
View

articles/concepts/circuits.md
:white_check_mark:Succeeded
View

articles/concepts/pauli-measurements.md
:white_check_mark:Succeeded
View

articles/concepts/the-qubit.md
:white_check_mark:Succeeded
View

articles/contributing/api-design-principles.md
:white_check_mark:Succeeded
View

articles/contributing/style-guide.md
:white_check_mark:Succeeded
View

articles/language/file-structure.md
:white_check_mark:Succeeded
View

articles/language/index.md
:white_check_mark:Succeeded
View

articles/language/statements.md
:white_check_mark:Succeeded
View

articles/language/toc.yml
:white_check_mark:Succeeded

articles/language/type-model.md
:white_check_mark:Succeeded
View

articles/libraries/standard/diagnostics.md
:white_check_mark:Succeeded
View

articles/machines/resources-estimator.md
:white_check_mark:Succeeded
View

articles/machines/toc.yml
:white_check_mark:Succeeded

articles/relnotes/0.3-migration.md
:white_check_mark:Succeeded
View

articles/relnotes/index.md
:white_check_mark:Succeeded
View

articles/techniques/file-structure.md
:white_check_mark:Succeeded
View

articles/techniques/going-further.md
:white_check_mark:Succeeded
View

articles/techniques/index.md
:white_check_mark:Succeeded
View

articles/techniques/local-variables.md
:white_check_mark:Succeeded
View

articles/techniques/operations-and-functions.md
:white_check_mark:Succeeded
View

articles/techniques/putting-it-all-together.md
:white_check_mark:Succeeded
View

articles/techniques/toc.yml
:white_check_mark:Succeeded

articles/techniques/working-with-qubits.md
:white_check_mark:Succeeded
View

articles/user-guide/basics.md
:white_check_mark:Succeeded
View

articles/user-guide/index.md
:white_check_mark:Succeeded
View

articles/user-guide/language/expressions.md
:white_check_mark:Succeeded
View

articles/user-guide/language/toc.yml
:white_check_mark:Succeeded

articles/user-guide/language/types.md
:white_check_mark:Succeeded
View

articles/user-guide/quickref/index.md
:white_check_mark:Succeeded
View

articles/user-guide/quickref/iqsharp.md
:white_check_mark:Succeeded
View

articles/user-guide/quickref/toc.yml
:white_check_mark:Succeeded

articles/user-guide/toc.yml
:white_check_mark:Succeeded

articles/user-guide/using-qsharp/control-flow.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/file-structure.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/operations-functions.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/testing-debugging.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/toc.yml
:white_check_mark:Succeeded

articles/user-guide/using-qsharp/variables.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/working-with-qubits.md
:white_check_mark:Succeeded
View

articles/welcome.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Lowestcategoryscore
Spellingissues
Scorecard
Processed

articles/TOC.yml
100
100
0
link
:white_check_mark:

articles/concepts/Glossary.md
80
58
9
link
:white_check_mark:

articles/concepts/circuits.md
79
57
1
link
:white_check_mark:

articles/concepts/pauli-measurements.md
83
67
4
link
:white_check_mark:

articles/concepts/the-qubit.md
70
40
48
link
:white_check_mark:

articles/contributing/api-design-principles.md
85
69
2
link
:white_check_mark:

articles/contributing/style-guide.md
81
57
2
link
:white_check_mark:

articles/libraries/standard/diagnostics.md
81
64
0
link
:white_check_mark:

articles/machines/resources-estimator.md
87
51
0
link
:white_check_mark:

articles/machines/toc.yml
100
100
0
link
:white_check_mark:

articles/relnotes/0.3-migration.md
78
60
1
link
:white_check_mark:

articles/relnotes/index.md
76
41
16
link
:white_check_mark:

articles/user-guide/basics.md
80
50
0
link
:white_check_mark:

articles/user-guide/index.md
83
65
0
link
:white_check_mark:

articles/user-guide/language/expressions.md
85
52
0
link
:white_check_mark:

articles/user-guide/language/toc.yml
100
100
0
link
:white_check_mark:

articles/user-guide/language/types.md
81
52
0
link
:white_check_mark:

articles/user-guide/quickref/index.md
100
100
0
link
:white_check_mark:

articles/user-guide/quickref/iqsharp.md
90
74
1
link
:white_check_mark:

articles/user-guide/quickref/toc.yml
100
100
0
link
:white_check_mark:

articles/user-guide/toc.yml
100
100
0
link
:white_check_mark:

articles/user-guide/using-qsharp/control-flow.md
79
49
1
link
:white_check_mark:

articles/user-guide/using-qsharp/file-structure.md
83
53
0
link
:white_check_mark:

articles/user-guide/using-qsharp/operations-functions.md
80
57
4
link
:white_check_mark:

articles/user-guide/using-qsharp/testing-debugging.md
80
56
1
link
:white_check_mark:

articles/user-guide/using-qsharp/toc.yml
100
100
0
link
:white_check_mark:

articles/user-guide/using-qsharp/variables.md
80
55
3
link
:white_check_mark:

articles/user-guide/using-qsharp/working-with-qubits.md
75
47
4
link
:white_check_mark:

articles/welcome.md
85
66
0
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Docs Build status updates of commit e58e3f5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

articles/TOC.yml
:white_check_mark:Succeeded
View

articles/concepts/Glossary.md
:white_check_mark:Succeeded
View

articles/concepts/circuits.md
:white_check_mark:Succeeded
View

articles/concepts/pauli-measurements.md
:white_check_mark:Succeeded
View

articles/concepts/the-qubit.md
:white_check_mark:Succeeded
View

articles/contributing/api-design-principles.md
:white_check_mark:Succeeded
View

articles/contributing/style-guide.md
:white_check_mark:Succeeded
View

articles/language/file-structure.md
:white_check_mark:Succeeded
View

articles/language/index.md
:white_check_mark:Succeeded
View

articles/language/statements.md
:white_check_mark:Succeeded
View

articles/language/toc.yml
:white_check_mark:Succeeded

articles/language/type-model.md
:white_check_mark:Succeeded
View

articles/libraries/standard/diagnostics.md
:white_check_mark:Succeeded
View

articles/machines/resources-estimator.md
:white_check_mark:Succeeded
View

articles/machines/toc.yml
:white_check_mark:Succeeded

articles/relnotes/0.3-migration.md
:white_check_mark:Succeeded
View

articles/relnotes/index.md
:white_check_mark:Succeeded
View

articles/techniques/file-structure.md
:white_check_mark:Succeeded
View

articles/techniques/going-further.md
:white_check_mark:Succeeded
View

articles/techniques/index.md
:white_check_mark:Succeeded
View

articles/techniques/local-variables.md
:white_check_mark:Succeeded
View

articles/techniques/operations-and-functions.md
:white_check_mark:Succeeded
View

articles/techniques/putting-it-all-together.md
:white_check_mark:Succeeded
View

articles/techniques/toc.yml
:white_check_mark:Succeeded

articles/techniques/working-with-qubits.md
:white_check_mark:Succeeded
View

articles/user-guide/basics.md
:white_check_mark:Succeeded
View

articles/user-guide/index.md
:white_check_mark:Succeeded
View

articles/user-guide/language/expressions.md
:white_check_mark:Succeeded
View

articles/user-guide/language/toc.yml
:white_check_mark:Succeeded

articles/user-guide/language/types.md
:white_check_mark:Succeeded
View

articles/user-guide/quickref/index.md
:white_check_mark:Succeeded
View

articles/user-guide/quickref/iqsharp.md
:white_check_mark:Succeeded
View

articles/user-guide/quickref/toc.yml
:white_check_mark:Succeeded

articles/user-guide/toc.yml
:white_check_mark:Succeeded

articles/user-guide/using-qsharp/control-flow.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/file-structure.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/operations-functions.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/testing-debugging.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/toc.yml
:white_check_mark:Succeeded

articles/user-guide/using-qsharp/variables.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/working-with-qubits.md
:white_check_mark:Succeeded
View

articles/welcome.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Lowestcategoryscore
Spellingissues
Scorecard
Processed

articles/TOC.yml
100
100
0
link
:white_check_mark:

articles/concepts/Glossary.md
80
58
9
link
:white_check_mark:

articles/concepts/circuits.md
79
57
1
link
:white_check_mark:

articles/concepts/pauli-measurements.md
83
67
4
link
:white_check_mark:

articles/concepts/the-qubit.md
70
40
48
link
:white_check_mark:

articles/contributing/api-design-principles.md
85
69
2
link
:white_check_mark:

articles/contributing/style-guide.md
81
57
2
link
:white_check_mark:

articles/libraries/standard/diagnostics.md
81
64
0
link
:white_check_mark:

articles/machines/resources-estimator.md
87
51
0
link
:white_check_mark:

articles/machines/toc.yml
100
100
0
link
:white_check_mark:

articles/relnotes/0.3-migration.md
78
60
1
link
:white_check_mark:

articles/relnotes/index.md
76
41
16
link
:white_check_mark:

articles/user-guide/basics.md
80
50
0
link
:white_check_mark:

articles/user-guide/index.md
83
65
0
link
:white_check_mark:

articles/user-guide/language/expressions.md
85
52
0
link
:white_check_mark:

articles/user-guide/language/toc.yml
100
100
0
link
:white_check_mark:

articles/user-guide/language/types.md
81
52
0
link
:white_check_mark:

articles/user-guide/quickref/index.md
100
100
0
link
:white_check_mark:

articles/user-guide/quickref/iqsharp.md
90
74
1
link
:white_check_mark:

articles/user-guide/quickref/toc.yml
100
100
0
link
:white_check_mark:

articles/user-guide/toc.yml
100
100
0
link
:white_check_mark:

articles/user-guide/using-qsharp/control-flow.md
78
51
1
link
:white_check_mark:

articles/user-guide/using-qsharp/file-structure.md
83
53
0
link
:white_check_mark:

articles/user-guide/using-qsharp/operations-functions.md
80
57
4
link
:white_check_mark:

articles/user-guide/using-qsharp/testing-debugging.md
80
56
1
link
:white_check_mark:

articles/user-guide/using-qsharp/toc.yml
100
100
0
link
:white_check_mark:

articles/user-guide/using-qsharp/variables.md
80
55
3
link
:white_check_mark:

articles/user-guide/using-qsharp/working-with-qubits.md
75
47
4
link
:white_check_mark:

articles/welcome.md
85
66
0
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Docs Build status updates of commit 8a7aa79:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

articles/TOC.yml
:white_check_mark:Succeeded
View

articles/concepts/Glossary.md
:white_check_mark:Succeeded
View

articles/concepts/circuits.md
:white_check_mark:Succeeded
View

articles/concepts/pauli-measurements.md
:white_check_mark:Succeeded
View

articles/concepts/the-qubit.md
:white_check_mark:Succeeded
View

articles/contributing/api-design-principles.md
:white_check_mark:Succeeded
View

articles/contributing/style-guide.md
:white_check_mark:Succeeded
View

articles/language/file-structure.md
:white_check_mark:Succeeded
View

articles/language/index.md
:white_check_mark:Succeeded
View

articles/language/statements.md
:white_check_mark:Succeeded
View

articles/language/toc.yml
:white_check_mark:Succeeded

articles/language/type-model.md
:white_check_mark:Succeeded
View

articles/libraries/standard/diagnostics.md
:white_check_mark:Succeeded
View

articles/machines/resources-estimator.md
:white_check_mark:Succeeded
View

articles/machines/toc.yml
:white_check_mark:Succeeded

articles/relnotes/0.3-migration.md
:white_check_mark:Succeeded
View

articles/relnotes/index.md
:white_check_mark:Succeeded
View

articles/techniques/file-structure.md
:white_check_mark:Succeeded
View

articles/techniques/going-further.md
:white_check_mark:Succeeded
View

articles/techniques/index.md
:white_check_mark:Succeeded
View

articles/techniques/local-variables.md
:white_check_mark:Succeeded
View

articles/techniques/operations-and-functions.md
:white_check_mark:Succeeded
View

articles/techniques/putting-it-all-together.md
:white_check_mark:Succeeded
View

articles/techniques/toc.yml
:white_check_mark:Succeeded

articles/techniques/working-with-qubits.md
:white_check_mark:Succeeded
View

articles/user-guide/basics.md
:white_check_mark:Succeeded
View

articles/user-guide/index.md
:white_check_mark:Succeeded
View

articles/user-guide/language/expressions.md
:white_check_mark:Succeeded
View

articles/user-guide/language/toc.yml
:white_check_mark:Succeeded

articles/user-guide/language/types.md
:white_check_mark:Succeeded
View

articles/user-guide/quickref/index.md
:white_check_mark:Succeeded
View

articles/user-guide/quickref/iqsharp.md
:white_check_mark:Succeeded
View

articles/user-guide/quickref/toc.yml
:white_check_mark:Succeeded

articles/user-guide/toc.yml
:white_check_mark:Succeeded

articles/user-guide/using-qsharp/control-flow.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/file-structure.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/operations-functions.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/testing-debugging.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/toc.yml
:white_check_mark:Succeeded

articles/user-guide/using-qsharp/variables.md
:white_check_mark:Succeeded
View

articles/user-guide/using-qsharp/working-with-qubits.md
:white_check_mark:Succeeded
View

articles/welcome.md
:white_check_mark:Succeeded
View

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

Where:
Once upon a time we all worked together. Birds of a feather, but this feather can't support all your weight. Wait, what was I saying? Quit playing. Quantum Reality Shifting begins.
https://etherpad.tools.ietf.org/p/SJm5R1rRQd


Use background tasks to notify users about expired position

Periodically check whether the user has an open position and alert the user when the position is about to expire or has already expired, so that they can open the app and react to it appropriately.

If this works, we can replace https://github.com/get10101/10101/issues/1070

After quite a bit of research and experimenting, these are my findings:
I managed to have a solution that stored position expiry time (if there was one) inside shared preferences (which can be accessed from a separate isolate in a background handler), which was checked inside a handler that was triggered by the "background fetch" mechanism that iOS supports and then display a notification to the user.
Unfortunately, this is just not reliable enough for our use-case :( background fetches can be scheduled "at some point, but not more often than 15 mins" by the device, and depending on how quickly you've completed your previous one (and some other undisclosed factors), next one might be scheduled sometime soon.
This was a rather frustrating debugging experience; I couldn't get it to be triggered reliably outside of XCode 😭 (only sometimes it would be triggered)
Note that this problem only concerns  iOS, Android is super chilled; one can schedule periodic tasks that do whatever you'd like.

I was hoping to at least have a data message being sent once every 12h or so from FCM to trigger the data task, but alas only notifications can be sent when an app is force-closed on iOS, not data messages.

I'm closing this issue in favour of https://github.com/get10101/10101/issues/1070 , because I actually managed to reliably de-risk and de-scope the other one.


Updated mlx-lm kvcache creation

Updated to match the latest version of mlx-lm (and updated requirements to mlx-lm>=0.19.2)
Also wrote a short test file.
See this commit in mlx-lm where the KVCache was updated: https://github.com/ml-explore/mlx-examples/pull/1015
This fixes #1225

I confirm, it fix https://github.com/dottxt-ai/outlines/issues/1225

I confirm, it fix #1225

Same, I had the same problem, and this small update was an immediate fix.

Thank you for your contribution. Really appreciate you adding tests!

The tests fail for unrelated reasons. Could you use pre-commit to format your code?


Add a progress bar for cli based hashing

Adds a simple progress bar for the command line utility.

I think the generate_clk_from_csv function should expose a better api for progress for other callers though - maybe a progress queue, or callback function?

Thanks for the code review Wilko, I think I've addresses all your requested changes.
The only piece I'm not happy with in the generate_clks function is we should probably split by "executor" and leave it up to the user to decide - and only go back to the if Python version > 3 decision if the user didn't provide a preference. There is of course no reason that Python2 users can't have parallel execution either - I just wanted to use the nicer concurrent api when it exists for Python 3.


Error: error: Expected ';', got 'assert' when trying to deploy on Vercel

Summary
When trying to deploy on vercel a NextJs project with contentlayer installed I get this error message on vercel build:

Click to expand
[21:20:00.600] Cloning github.com/zaniluca/zaniluca.com (Branch: blog-setup, Commit: fac6d7f)
[21:20:01.007] Cloning completed: 406.525ms
[21:20:01.837] Looking up build cache...
[21:20:02.294] Build Cache not found
[21:20:02.518] Running "vercel build"
[21:20:02.993] Vercel CLI 25.2.0 build (beta) — https://vercel.com/feedback
[21:20:03.270] Installing dependencies...
[21:20:03.610] yarn install v1.22.17
[21:20:03.682] [1/4] Resolving packages...
[21:20:03.882] [2/4] Fetching packages...
[21:20:19.529] [3/4] Linking dependencies...
[21:20:19.530] warning "contentlayer > @contentlayer/source-files ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[21:20:19.532] warning "contentlayer > @contentlayer/utils > @opentelemetry/exporter-trace-otlp-grpc ><EMAIL_ADDRESS>has incorrect peer dependency "<EMAIL_ADDRESS><1.1.0".
[21:20:19.532] warning "contentlayer > @contentlayer/utils > @opentelemetry/exporter-trace-otlp-grpc ><EMAIL_ADDRESS>has incorrect peer dependency "<EMAIL_ADDRESS><1.1.0".
[21:20:19.534] warning "contentlayer > @contentlayer/utils > @opentelemetry/exporter-trace-otlp-grpc ><EMAIL_ADDRESS>has incorrect peer dependency "<EMAIL_ADDRESS><1.1.0".
[21:20:19.551] warning Workspaces can only be enabled in private projects.
[21:20:19.552] warning Workspaces can only be enabled in private projects.
[21:20:19.555] warning Workspaces can only be enabled in private projects.
[21:20:33.527] [4/4] Building fresh packages...
[21:20:36.513] Done in 32.91s.
[21:20:36.542] Detected Next.js version: 12.1.0
[21:20:36.544] Running "yarn run build"
[21:20:36.817] yarn run v1.22.17
[21:20:36.848] $ next build
[21:20:39.931] Generated 1 documents in .contentlayer
[21:20:39.967] Attention: Next.js now collects completely anonymous telemetry regarding usage.
[21:20:39.967] This information is used to shape Next.js' roadmap and prioritize features.
[21:20:39.967] You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
[21:20:39.967] https://nextjs.org/telemetry
[21:20:39.967]
[21:20:40.021] info  - Checking validity of types...
[21:20:46.627] warn  - No ESLint configuration detected. Run next lint to begin setup
[21:20:46.630] info  - Creating an optimized production build...
[21:20:57.127] Failed to compile.
[21:20:57.127]
[21:20:57.128] ./.contentlayer/generated/index.mjs
[21:20:57.128] Error: error: Expected ';', got 'assert'
[21:20:57.128]
[21:20:57.128]   |
[21:20:57.128] 7 | import allBlogPosts from './BlogPost/_index.json' assert { type: 'json' }
[21:20:57.129]   |                                                   ^^^^^^
[21:20:57.129]
[21:20:57.129] Caused by:
[21:20:57.129]     0: failed to process js file
[21:20:57.129]     1: Syntax Error
[21:20:57.129]
[21:20:57.129] Import trace for requested module:
[21:20:57.129] ./pages/blog/[slug].tsx
[21:20:57.129]
[21:20:57.129]
[21:20:57.129] > Build failed because of webpack errors
[21:20:57.196] error Command failed with exit code 1.
[21:20:57.197] info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
[21:20:57.223] Error! Command "yarn run build" exited with 1
[21:20:57.322] Error: Command "vercel build" exited with 1

When trying to run build locally it works fine.
I'm using:

"next": "12.1.0"
"next-contentlayer": "^0.2.5"
"contentlayer": "^0.2.5"

what node version do you have configured on vercel?

what node version do you have configured on vercel?

16.x

Can you please verify (e.g. by adding a node -v log statement to your build step on Vercel) that the actual used Node version is indeed 16.x?

Thanks. Could you please share a link to the repo so I can try to reproduce the problem?

https://github.com/zaniluca/zaniluca.com/tree/blog-setup this repo on blog-setup branch

Thanks a lot @zaniluca. This seems a bit odd. I was just able to reproduce the problem you described locally when running yarn build.

However, the problem disappeared after upgrading to Next.js 12.2. So I assume it was a bug in Next.js that was fixed.

Please let me know if you need further help!

@schickling yep, it worked! thank you again!


camel-cxf-transport: make CxfMessageHelperTest pass on windows operat…

…ing systems

Thanks for the PR it has been merged. Do you mind closing this?


PDF Viewer Component for PDF Asset

Is your feature request related to a problem? Please describe.
When we open a PDF Asset it shows just the first page, only on download user can have a look at all the pages. But with this feature without downloading we can have a View of all pages along with scroll bar, Annotate the text , Search for a text. It has 3 variations Full Window, Sized Container, In Line. With the use of this component user's saves lot of time and resources  as downloading of pdf is not needed.
Describe the solution you'd like
For this PDF Viewer component we can leverage PDF Viewer Core Component and make MimeType Changes so PDF asset would open in "/content/asset-share-commons/en/light/details/pdf.html" instead of "/content/asset-share-commons/en/light/details/document.html" page. For Rendering this component user can have Document Cloud View SDK Integration . This would need implementation of Context Aware Configuration / OSGI Configuration / Combined approach of both configurations
Describe alternatives you've considered
On absense of this integration user can download the asset using Download action button. A Message is shown in this component to configure Document Cloud View SDK Integration ID
Additional context
Full Window Variation

In Line Variation

Hi David and Daniel
@davidjgonzalez @godanny86 could you please share your thoughts on this Feature Request.

@vineelakarnati @davidjgonzalez  @godanny86
Any updates on the above ? Was this implemented by any chance ?
@vineelakarnati , if not, what did you end up doing for your use-case that needed this implementation.

Any hope on this?

@davidjgonzalez wanted to see if there has been anythign on this. I think this reader would hold a lot of value as a feature, not just for PDF's but for PowerPoints as well. Do you know of anything that already exists, or would this feature need to be designed from Scratch.

@Robedean - i have an old branch with this - let me see if i can find it and PR it in.

Hows this look?
https://github.com/adobe/asset-share-commons/pull/1060

This has been released in 3.7.0


[1.26] update pause image from 'kubernetes/pause' to 'registry.k8s.io/pause'

Backporting https://github.com/kubernetes-sigs/descheduler/pull/1166 to 1.26

/approve
/lgtm


refactor: fix minor comments: docs, bugs

Description
Fixes #25
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[x] Documentation updated

Checklist:

[x] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works

[ ] Correct demonanalysis package in binder


Cascade behaviour not as I expected

Steps to reproduce
Here's a model with an optional relationship between Property and Tenant:
public class LettingsContext : DbContext
{
    public DbSet<Property> Properties { get; set; }
    public DbSet<Tenant> Tenants { get; set; }

    protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
    {
        optionsBuilder.UseSqlServer(@"Server=(localdb)\mssqllocaldb;Database=Lettings;Trusted_Connection=True;MultipleActiveResultSets=true");
    }
}

public class Tenant
{
    public int TenantId { get; set; }
    public string Name { get; set; }
    public string Email { get; set; }
    public int? PropertyId { get; set; }
    public Property Property { get; set; }
}

public class Property
{
    public int PropertyId { get; set; }
    public string Address { get; set; }
    public List<Tenant> Tenants { get; set; }
}

The issue
When I create a migration, I would expect to see the ReferentialAction set to SetNull for the onDelete parameter of the PropertyId foreign key in the Tenants table, but it is defined as Restrict:
migrationBuilder.CreateTable(
    name: "Tenants",
    columns: table => new
    {
        TenantId = table.Column<int>(nullable: false)
            .Annotation("SqlServer:ValueGenerationStrategy", SqlServerValueGenerationStrategy.IdentityColumn),
        Email = table.Column<string>(nullable: true),
        Name = table.Column<string>(nullable: true),
        PropertyId = table.Column<int>(nullable: true)
    },
    constraints: table =>
    {
        table.PrimaryKey("PK_Tenants", x => x.TenantId);
        table.ForeignKey(
            name: "FK_Tenants_Properties_PropertyId",
            column: x => x.PropertyId,
            principalTable: "Properties",
            principalColumn: "PropertyId",
            onDelete: ReferentialAction.Restrict);
    });

Which then translates to NO ACTION for SQL Server:
CONSTRAINT [FK_Tenants_Properties_PropertyId]
FOREIGN KEY ([PropertyId])
REFERENCES [Properties] ([PropertyId])
ON DELETE NO ACTION

My expectation is based on the docs here: https://ef.readthedocs.io/en/latest/modeling/relationships.html#cascade-delete. Why doesn't this work as I expect? Is some additional configuration required? Or have I misunderstood something?
Exception message:
Stack trace:

Further technical details
EF Core version: 1.0
Microsoft.EntityFrameworkCore.Tools version: 1.0.0-preview2-final

@mikebrind The documentation is not correct. We had originally intended to do this, but the problem is that it causes errors in so many cases when using SQL Server. See this PR: #3311

So the behaviour, and possible solutions, are the same as for EF6?

Sorry, I thought the docs said this, but I don't see it. EF Core supports the SetNull behavior:
modelBuilder.Entity<Tenant>()
    .HasOne(p => p.Property)
    .WithMany(b => b.Tenants);
    .OnDelete(DeleteBehavior.SetNull);

It just isn't on by default. It should work fine with your posted code. If you are using SQL Server and have other relationships, then SQL Server might start complaining about cycles. In those cases the workaround is the same as for EF6--switch it off in the database and always make sure all related entities are loaded so that the cascade behavior is all done client-side.

I was beginning to question my sanity. The PR you referenced appeared to show that it had been included, but I was expecting it to show that it had been removed (or canned or something other than included) based on your earlier comment. Consequently, it made no sense to me at all.
Thanks for the update.

Re-opening as there is a documentation bug.

@rowanmiller this is a docs bug.

It might be a good idea to include intellisense describing what the enum ReferentialAction does, too.

PR for docs is out https://github.com/aspnet/EntityFramework.Docs/pull/308

Fixed n https://github.com/aspnet/EntityFramework.Docs/commit/fdddb6ab55ae31ac82f5333add30bbfbea5717b0


Midule 1.2 Assignment

What module is your suggestion regarding?
Ex 1.2
What is your suggestion for improving this module?
Update GitHub to provide all CLI that are typically used in Bash
Since Atom is no longer supported... replace it with another commonly used IDE (i.e. Netbeans, VS, VSC, Eclipse, etc.)
Additional context
Add any other context or screenshots about the suggestion here.


New version: CompatHelper v1.16.4

Registering package: CompatHelper
Repository: https://github.com/JuliaRegistries/CompatHelper.jl
Created by: @DilumAluthge
Version: v1.16.4
Commit: 7ca0fdb5c7d80055804c1fe600a8dd5a5633da7c
Reviewed by: @DilumAluthge
Reference: https://github.com/JuliaRegistries/CompatHelper.jl/commit/7ca0fdb5c7d80055804c1fe600a8dd5a5633da7c#commitcomment-48301777

cc: @timholy
[noblock]


feat(datasets): adding new variant annotation model

✨ Context
Variant representation replaced from the GnomAD variant annotation to a schema tailored with the Platform variant representation in mind. The data for the new  variant model is derived from VEP output. Essentially the idea is that we'll run VEP for every variant we have phenotypic data for every release for the most up to date Ensembl version.
🛠 What does this PR implement
New variant index

[x] New data model.
[x] New schema.
[x] Relevant dataset specific methods migrated to new data model from old variant index and the old variant annotation.
[x] To be consistent with the rest of the Platform design, instead of variant consequence terms, we are using sequence ontology identifiers. To do the mapping, a mapping file had to be added as a static asset.

Removal of variant annotation - A number of steps were required to eradicate variant annotation from gentropy. There's no need for it anymore, as the variant index data model will contain all required annotation.

[x] Removing schema.
[x] Removing dataset module.
[x] Removing dataset documentation.
[x] Walked through most of the code and documentation to remove references to variant annotation. This effort might not be complete.

Migrating variant annotation to variant index - As there are multiple dependencies on Variant Annotation dataset, these steps needed to be reviewed and amended to make sure no downstream process would fail.

[x] GnomAD ingestion step now produces variant index dataset, which can be picked up by the variant index step to bring in cross references to GnomAD and allele frequencies.
[x] V2G generation now depends on the new variant index.
[x] The ingestion of GWAS Catalog curated dataset picks up the variant index generated from GnomAD variants.

New data source - Variant annotation is parsed from Ensembl's VEP output. Therefore we can consider Ensembl as a separate datasource, where potentially other parsers can be added (eg. parser for rs id to variant id).

[x] New datasource added to gentropy with the logic to parse JSON formatted VEP output.
[x] Documentation was added.
[x] As the VEP output json can be very big but also can miss all columns where no data is available, it makes sense to load the data with providing the schema. Providing the schema ensures parsing methods to not fail. The schema was put to static assets.

Pipelining

[x] All relevant configuration was updated to remove variant annotation and use the new variant index wherever it was necessary.
[x] Step was added to generate variant index based on the Ensembl VEP output.
[x] All configuration was removed related to variant annotation.
[x] GWAS Catalog ingestion DAGs were also updated to use the GnomAD variant set.

Tests

[x] Tests were updated to point to the new  classes and new tests were written to test the VEP parser.
[x] Airflow steps and configs were tested: GnomAD variant ingestion. Variant index generation, V2G generation.

Other refactoring along the way

[x] Removal of unused sample dataset in the tests folder.
[x] Updating doc strings when found inaccuracies.
[x] I have added a line to VSCode config to suppress extension recommendations, as I found them overly annoying.
[x] The vep_consequences.tsv file got extended with new consequence terms and changed the format slightly to no transformation is required when used.
[x] As there's no variant annotation, I removed the step, but at the same time, I put together the two GnomAD preprocess step into one single DAG.

🙈 Missing

!! This PR doesn't include logic or workflow to generate the variant list for the index
!! The logic and workflow to generate VEP annotation for the variant is also in a separate PR.
!! The current place for VEP output (vep_output_path: gs://genetics_etl_python_playground/vep/full_variant_index_vcf) is not tidy. This needs to be refactored.

🚦 Before submitting

[ ] Do these changes cover one single feature (one change at a time)? - not really.
[x] Did you read the contributor guideline?
[x] Did you make sure to update the documentation with your changes?
[x] Did you make sure there is no commented out code in this PR?
[x] Did you follow conventional commits standards in PR title and commit messages?
[x] Did you make sure the branch is up-to-date with the dev branch?
[x] Did you write any new necessary tests?
[x] Did you make sure the changes pass local tests (make test)?
[x] Did you make sure the changes pass pre-commit rules (e.g poetry run pre-commit run --all-files)?

Thanks for the thorough review. I think I could answer most of your questions and implement the suggestions where I could.


Importing many games at once on initial connection may not import all games into galaxy

Importing many games at once on initial connection may not import all games. It appears to be on Galaxy's end since the games will show up if you force send the data to it again by deleting the cache and repopulating without disconnecting the plugin.

It looks like the api allows you to send streaming updates before galaxy is actually capable of accepting them. It looks like waiting for the handshake to complete first helps with the issue. See the current version in dev for an early test build if you are having issues with this. https://github.com/AndrewDWhite/GalaxyGenericImporterPlugin/releases/tag/Prototype_ef2deba40c7a3bf0e8efa4d6b48383782be4377f

It looks like the latest versions of galaxy reintroduce the issue under some conditions. If this happens as a work around, close and reopen galaxy and it will force a re-import without having to wait for everything. This may be required multiple times.


several differences found during setup

As the other issue said, this 'Copy the ServiceNow Homepage value, and paste it in Sign-on URL in the ServiceNow Basic SAML Configuration section of the Azure portal.' shouldn't be done and Sign-on URL in Azure should be kept as https://.service-now.com/login_with_sso.do?glide_sso_id=<sys_id of the sso configuration>
My Single Sign-on Script is not this one after setup, and it will not work until I change it to this one

My auto provisioning is not working. I have to use azure's

As a result of the above step, the provisioned accounts do not have email, I then use user_name instead:

What might be the cause of these? Thanks

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

ID: d507f0ce-f27f-1ffd-7129-7bb4e37b07ff
Version Independent ID: ec9f7c43-e967-d2e7-cde7-111c5897a798
Content: Tutorial: Azure Active Directory single sign-on (SSO) integration with ServiceNow
Content Source: articles/active-directory/saas-apps/servicenow-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @jeevansd
Microsoft Alias: jeedes

@xieofxie Thank you for your query . We will investigate and update the thread further.

@xieofxie Sign on url has to be initially set to https://instance.service-now.com/login_with_sso.do?glide_sso_id=<sys_id of the sso configuration>and later during configuration, needs to be changed to https://instance.service-now.com/navpage.do.
Since you are provisioning user from Azure AD, do you have mail attribute configured for Azure AD users and if mail attribute have a value, do you have mail to email mapping in the attribute mapping section of user provisioning?

@amanmcse Oh, thanks! I changed the Sign on url and it worked.
For the azure provision part, I just use the default settings and it seems email is not set.
My question for provision is what should I do to make auto provisioning working? Or azure provision is just fine? Thanks

@xieofxie I would suggest you to use Azure Provisioning with provisioning mode set to automatic (as highlighted below) so that you don't have to maintain the matching attributes manually.

@xieofxie I am closing this thread for now.
Feel free to tag me in your reply if you have any further questions.


Bridge.fn.bind produce a memory leaks

http://deck.net/cb3d8869609e9184beb85ad401227711
Bridge.fn.bind(obj, method) save reference to the "obj" into "method.$$bind" and keep it forever. This can produce huge memory leaks.
Solution:
#before
Bridge.fn.bind(obj, obj.method)

#after
(obj.method = Bridge.fn.bind(obj, obj.method))

this will replace instance method property with a new bounded function.

Hi @AndreyZM, it is a nice finding, thank you.
We are going to apply this fix #1952.


Add non-interactive mode for align_guidescope

The align_guidescope program currently requires some user interaction to confirm that it's doing the right thing, but this prevents more complete automation.

[x] Make these interactive checks optional such that the entire program can run unattended.
[ ] Consider whether it's okay to just bypass the checks or if robust automated checks need to be developed.

I realized that the current approach may require some inter-process communication for synchronization to make the script fully automated. The bright star is held at the center of the main camera by means of a subprocess which performs a spiral search followed by bringing the star to the center of the camera once it is found. While that subprocess continues running to hold the star at camera center, a still image is taken with the guidescope camera for plate solving. The user provides the synchronization event by answering a prompt when the star is centered in the main camera preview window. Without user interaction, the subprocess will need to somehow inform the parent process that the star is centered, which will indicate to the parent script that it's time to proceed.
I think the logic to detect when the star is centered already exists, but normally that logic is used to terminate the controller. In this case we don't want the controller to stop; we instead want it to inform another process that this condition has been satisfied.

I attempted to implement the multiprocessing approach but ran into a number of challenges:

It's apparently impossible (or at least difficult) to import stuff from __main__.py, so I had to move the contents of that over to track.py. Not a huge deal; doesn't really change anything.
The same sys.argv of the parent process is inherited by the child process, naturally, so had to add an optional args parameter to track.main() so it could take arguments passed to it via the multiprocessing.Process() constructor. Also not a huge deal.
For some reason click raises an exception in the child process. I don't understand why. The child process clearly has access to stdout since logging still works; maybe it doesn't inherit access to stdin? Ended up just commenting out the single yes/no prompt about stale model params figuring I'd deal with that later.
For some reason the child process is printing log messages to stdout in identical pairs. This does not seem to affect log messages written to files.

The more I use it the more disenchanted I become with multiprocessing. It seems like it's built on a bunch of fragile hacks that only work for trivial use cases. All I need is for one process to send a one-way signal to another process. Maybe I'd be better off reverting to subprocess.run and passing it the PID of the parent process so it can just send a signal like SIGUSR1, and the parent can wait for that signal with signal.sigtimedwait().

I just realized that the approach I'm using in the control module to determine if the mount is converged on the target only checks if the separation angle between the mount position and the target position is small, but this isn't the right criterion.

[ ] Modify the event such that it fires when the star has been located and is centered in the camera frame.

Problem: How to specify how close to center of frame is close enough.
What should determine this:

The Target object ideally should not decide this, since it has no idea of the requirements or application. Perhaps it would be okay if it has a reasonable default, but depending on defaults to be correct for a given application is fragile.
The track main() function should not decide this for the same reason.
This should come from the align_guidescope program, since that code is aware of the objective.

What units should be used for the threshold:

It's tempting to make the threshold be in camera height units, but this is an unusual unit and would not generalize to other target types.
It should be an Angle.

How:

The actual threshold could be passed to the track program via program arguments, like all of the other configuration.
It would be useful if align_guidescope could calculate the threshold angle as a fraction of the main camera frame height, since ultimately the objective is to keep the target object reasonably close to the center of this camera's field of view. However, normally align_guidescope does not have direct access to the main camera so it doesn't know about its field of view.

I suppose it could construct an instance of the main camera solely for the purpose of extracting this information, using a with: statement so it gets closed / cleaned up before creating a subprocess that will then re-open that same camera. Then the problem becomes how to construct this object. This might require awkwardly parsing arguments from a different config file (the one passed to the subprocess)...ugh. I've worked hard to avoid making the main() function of these programs responsible for constructing most objects directly. In fact normally the main() functions don't interact with cameras directly at all, but it seems like I need to violate that separation of concerns in this case.
Perhaps this should just be a value stored in a config file or passed on the command line. That way align_guidescope doesn't need to do elaborate contortions to compute it. The more I think about it, the more this seems like the right approach. Ultimately the accuracy of the guidescope alignment should be configurable and not hard-coded anywhere.

The problem I'm dealing with now is that the program arguments I'm adding to track's main() function are very specific to CameraTarget and do not work for any other target. So when I add a program argument specifying the separation angle below which SIGUSR1 should be sent I have to write an awkward and lengthy help message that points out how it only applies under very limited circumstances and so on.
I realized that I should just move these program arguments into the target module under the camera subparser, and furthermore the code that actually sends the signal can then just be moved into the CameraTarget class eliminating the need for any callbacks from main(). That seems like it ought to be much cleaner and avoids cluttering up main() with these concerns.

[ ] Move program arguments for the PID and separation angle threshold into target.add_program_arguments()
[ ] Move code to send the signal from main() to targets.CameraTarget

After sleeping on it, I've changed my mind about the previous comment. I'd rather main() be responsible for unusual side effects like sending signals to other processes, even if it clutters up main() a bit, such that none of the Target objects including CameraTarget need to be directly involved in inter-process communication concerns.
This is the best I can think of for now. It's not super pretty, but it will get the job done and I think the coupling introduced is as minimal as it can be while solving the problem.

The basics have been implemented, but still need to be tested outside since I don't have a way to do a full integrated test of align_guidescope indoors.
Thinking through some checks that could be automated:

The interactive version waits for the user to indicate that the star is centered in the main camera. This has been automated.
Spiral search could lock onto the wrong star. In the interactive version, in theory the user could recognize this and abort the program, but in practice aside from brightness its unclear how a human could easily tell whether the right star was present or not. Unfortunately plate solving doesn't seem to work well with the main camera. The best I can think of is to point at a second bright star after the whole process is complete, but this adds a lot of complexity and suffers from its own problems (What if the second star is obscured from view? What if there are two false identifications in a row?). For now I'll assume that this happens rarely enough to not be a major problem.
Plate solver could identify the wrong star in the guidescope image. I think the likelihood of this is quite small; since align_guidescope has existed with manual checks I've never seen it mark the wrong location. I don't think any additional automated checks are needed. I already trust Astrometry.net to work in other contexts like initial alignment.


setup scripts are very slow

One resone is the serial start of each server after configuration update.
This is the result of
serial: 1

in prepare_scylla.yaml
This was originally introduce for adding nodes to existing, working cluster, but is not required when starting a new cluster from scratch.

fix by https://github.com/scylladb/cassandra-test-and-deploy/pull/41
other slowdown issues still pending.
One is https://github.com/scylladb/scylla-ami/issues/1


DOC: Fix vale warnings

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 83.02%. Comparing base (44b66e3) to head (5560ebd).
Report is 5 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #226      +/-   ##
==========================================
- Coverage   83.04%   83.02%   -0.03%
==========================================
  Files         105      105
  Lines       17579    17605      +26
==========================================
+ Hits        14599    14617      +18
- Misses       2980     2988       +8

@SMoraisAnsys I already fixed the warning. But feel free to use this version to overwrite my fix content. Up to you.
Otherwise, we can close it.

Closing following #235.
@MaxJPRey No worries, the quick changes are understandable.


issue with DPOTrainer class

I am encountering issues with the last three parameters in the DPOTrainer configuration. The problem seems related to the version I am using. To work around the issue and proceed with fine-tuning, I had to comment out the following parameters:
trainer = DPOTrainer(     # The model to be trained     model=model,     # Training configuration from above     args=training_args,     # Dataset containing preferred/rejected response pairs     train_dataset=dataset,     # Tokenizer for processing inputs     processing_class=tokenizer,     # DPO-specific temperature parameter that controls the strength of the preference model     # Lower values (like 0.1) make the model more conservative in following preferences     #beta=0.1,     # Maximum length of the input prompt in tokens     #max_prompt_length=1024,     # Maximum combined length of prompt + response in tokens     #max_length=1536, )
Will omitting these parameters (i.e., commenting them out) affect the quality or performance of the fine-tuned model?
https://colab.research.google.com/github/huggingface/smol-course/blob/main/2_preference_alignment/notebooks/dpo_finetuning_example.ipynb#scrollTo=eIIzGIKZtKcq&line=1&uniqifier=1

I ran into this on stream today. Which version of TRL should I use?

I had a similar issue on Google Colab. A workaround is to install trl==0.12.1 instead of trl on Colab.

After some quick research, I discovered that in the latest version of TRL (0.13.0), these parameters have been moved to the DPOConfig class.
To resolve the issue, the parameters causing errors need to be moved to the DPOConfig definition.
config = DPOConfig(     ...     beta=0.1,  # DPO-specific temperature parameter     max_prompt_length=1024,  # Maximum length of the input prompt in tokens     max_length=1536  # Maximum combined length of prompt + response in tokens )
https://github.com/huggingface/trl/blob/4c71daf461d86226ee36c30531d481c33c3e618e/trl/trainer/dpo_trainer.py#L149


Proposal: Adding instructions to connect PySpark to DuckDB and read a PySpark DataFrame via JDBC

This took a while to figure out and there doesn't appear to be documentation that lists all the steps. Since I've figured out how to do this, I'd like to share with the community the code I had to write in order to read a DuckDB table as a PySpark DataFrame. I propose that this code sample gets added to the documentation. This is an example using the DuckDB JDBC version 0.8.1 but can be replaced by any version. The database file name in this example is my-duckdb-database.db and the table name in this example is 'MyTable'. Please let me know if there is interest for this and I could make a pull request.
The DuckDB .jar file of any version can be downloaded from the Maven repository.
import pyspark.sql as psql
spark = psql.SparkSession.builder.config('spark.jars', 'path/to/duckdb_jdbc-0.8.1.jar').getOrCreate()
url = 'jdbc:duckdb:path/to/my-duckdb-database.db'
# The dataframe can be read like this:
reader = spark.read.format('jdbc').option('url', url)
df = reader.option('dbtable', 'MyTable').option('driver', 'org.duckdb.DuckDBDriver').load()
# ... or like this:
reader = psql.DataFrameReader(spark)
df = reader.jdbc(table='MyTable', url=url, properties={'driver': 'org.duckdb.DuckDBDriver'})

Surely this is better off living in the pyspark docs? There's nothing here specific to DuckDB

@Mause it uses the duckdb JDBC. And the current documentation doesn't make it clear how to connect a pyspark session to a duckdb database via JDBC.

Hi @erikhuck thanks for opening this issue. As @Mause pointed out, this doesn't really belong to the DuckDB documentation: in general, tools that use DuckDB should not fit in the DuckDB documentation. Reading via the JDBC driver is also rather slow – if you have alternative options, like exporting to/importing from Parquet, consider using those.

@szarnyasg Thank you for the information. I could possibly propose this in the awesome-duckdb repo instead. But I don't understand why the JDBC would be slow? DuckDB is very fast when you load a pandas DataFrame via con.sql(). So why would loading a spark DataFrame via the JDBC be different?
I understand DuckDB has an export to parquet option but my table has over a million rows and over 20,000 columns (it's a machine learning dataset so it's big) and when I try to export it to parquet, it runs out of memory. Would you happen to know how to configure DuckDB to prevent running out of memory (i.e. reading a subset of the table, appending subset to parquet file, then reading the next subset of the table, etc.)? If not, it would appear I'd have to use PySpark to at least convert to parquet?

@erikhuck

But I don't understand why the JDBC would be slow?

JDBC returns rows line-by-line, which adds a lot of overhead if you have many rows.
For Parquet export, did you try setting the preserve_insertion_order to false?
SET preserve_insertion_order = false;

@szarnyasg would ODBC be better?
I will try setting preserve row order to false

ODBC would have the same problem. ADBC is your best bet

It still ran out of memory after SET preserve_insertion_order = false;. It appears that DuckDB is not able to export large data sets. Looks like something more heroic is necessary.

Depending on your exact configuration, you may need to limit the number of threads as well (DuckDB can try to be too fast sometimes)


#2657 Feature/ alphabetic ordered i18n

Related issues

closes #2657
Short description and why it's useful

When developer wants to commit changes including csv translations, lint-staged will automatically sort staged i18n files alphabetically.
Which environment this relates to
Check your case. In case of any doubts please read about Release Cycle
Feature

[x] Test version (https://test.storefrontcloud.io) - this is a new feature or improvement for Vue Storefront. I've created branch from develop branch and want to merge it back to develop
[ ] RC version (https://next.storefrontcloud.io) - this is a stabilisation fix for Release Candidate of Vue Storefront. I've created branch from release branch and want to merge it back to release
[ ] Stable version (https://demo.storefrontcloud.io) - this is an important fix for current stable version. I've created branch from hotfix or master branch and want to merge it back to hotfix

Upgrade Notes and Changelog

[x] No upgrade steps required (100% backward compatibility and no breaking changes)
[ ] I've updated the Upgrade notes and Changelog on how to port existing VS sites with this new feature

@defudef please update the changelog

It would be nice, if all commits will be squashed. It's better to read history with more descriptive commit message.

@krecik thats good point, we should consider it @filrak @lukeromanowicz @patzick we we’re not squashing commits since the very beginning of the project therefore I’m not sure about starting it right now as it will be not fair regarding contribution statistics for newcomers however not sure if anybody takes care

Squashing should be done also properly - not only take all commits and make one.
But this one is small, so there should be one commit, and also all should be rebased on top of develop - cause in PR there are 2 merge commits (just to update codebase - it can be easily removed). In large projects, where code is changing frequently, this only pollute history, and making it harder to read.
@pkarw contribution statistics can be a problem, but i think better is to keep good quality, rather than large volume of commits :) Volume of contribution can be checked by changed lines of code, rather than number of commits.
My proposition for commit message for this change is:
Feature: Sorting alphabetically I18N tranlations

Configure lint to sort translations files before commit.
Initial sort of translations files.

A a rule of thumb always should be squashed commits like: "improvments after CR", "fix", "fix issue", "updated XXX.js" (what file is updated we see in commit, better is to add info what was changed - ex. i'm updating readme - better is to add: "Change info about number of intergrations", etc.) - there are not descriptive in any way.

I love the idea too!
IMO It could perfect fit with commit conventions as I mentioned in other issue.
I'm not a fan of long commit messages (event if they're squashed). Better short description and linked issue.

I love the idea too!

Nice :D So just do it now :) Be the first one to implement the change and show others how this should look like.

@krecik please create an RFC with this proposition. It needs to be discussed within community. With this occasion would be great to add a generator for changelog from commits, like conventional changelog or something like this :)


FIx the footer

On some pages footer is not working properly

On some pages its working fine so you have to make the footer look like this on every page.

Can I work on it?

Can I work on it?

Hey @swapnilsparsh,
I would like to work on this issue

Hey @swapnilsparsh,
I would like to work on this issue


Drop down filters above the table.

Hello, much as I am new to react nothing has made my work easier than this amazing repo.
However am kind in need to learn how best I can have the The Column Filters for example the drop down  above the table and not in that specific column.
Thank you again for the amazing work.

for the column filter, we have text, regex, number, date and select filter, how about this example? I think it's match your requirement, http://allenfang.github.io/react-bootstrap-table/example.html#column-filter have some filter examples.
Let me know if you still have any questions. thanks

Hello Allen,
Thank you again. Probably my explanation was not that clear. What I seek to learn is how I can have the select filter on top of the table and not within that specific column.
So that on the table I can have
ADD Content Button , Search Form and the Also Select to Filter.

@leonkalema, sorry for misunderstand your requirement, actually, we dont have this kind of feature, but you can custom it by yourself and call the filter or search function exposed by react-bootstrap-table
check this to learn how to custom toolbar
check this to search table
check this to filter by column
For me, I guess, you need to have a custom component and when use select some value, you need to do the search/filter, you can call handleSearch or handleFilterData, but you can also filter your data in your application.
Please let me know if you still have any question, thanks 👍

@leonkalema, hello, even I have a similar requirement as you mentioned, did you implement it by any chance? Thanks in advance.

@smilingpigs, please check https://github.com/AllenFang/react-bootstrap-table/blob/master/examples/js/column-filter/custom-filter.js to learn how to custom column filter


Broken link: Professor Frisby's Mostly Adequate Guide to Functional Programming

The Link Professor Frisby's Mostly Adequate Guide to Functional Programming in the Practices section is broken.
Expected behaviour:
The link is not broken and I can find the resource.
Maybe this is the correct link: https://mostly-adequate.gitbook.io/mostly-adequate-guide/

This issue will get fixed with #177


VC-35568: Feature: Send errors to the pod's event to increase visibility

Ref: VC-35568
This feature aims at giving the user another way of knowing when the Agent isn't sending data to the VCP API. With this PR, the user will have two ways of noticing that the Agent isn't properly working:

By looking at the logs (but hard since the logs are overwhelming (cf. VC-33564),
By looking at the Kubernetes events on the Agent pod.

POSSIBLE BREAKING CHANGE 1: Previously, --install-namespace was only needed when using the VenafiConnection mode (i.e., using --venafi-connection). Starting with this PR, all modes will require knowing what the pod's namespace is. For context, ~the namespace is looked up in /var/run/secrets/kubernetes.io/serviceaccount/namespace if the pod has a service account mounted to it (always the case for the agent)~ it looks for the contents of POD_NAMESPACE defined in the deployment; otherwise, it uses the contents of --install-namespace (meant for running the agent out-of-cluster for testing purposes).
Is this really a breaking change? Very low chance of breakage since POD_NAMESPACE has been added to the Helm chart regardless of the auth mode.

POSSIBLE BREAKING CHANGE 2: Previously, the namespace would be loaded from the file /var/run/secrets/kubernetes.io/serviceaccount/namespace. Now, it is loaded from the env var POD_NAMESPACE. The Helm chart has been updated with this env var.
Is this really a breaking change? Low chance of breakage since folks will upgrade using the updated Helm chart which will contain POD_NAMESPACE.
Testing
There are no automated tests for this change.
I tested the "events" feature with the following:
I've used the tenant https://ven-tlspk.venafi.cloud/. To access the API key, use the user<EMAIL_ADDRESS>and the password is visible in the page Production Accounts (private to Venafi). Then go to the settings and find the API key.
export APIKEY=...

I've then deployed the agent to a Kind cluster:
kind create cluster
venctl iam service-account agent create --name "$USER temp" \
  --vcp-region US \
  --output json \
  --owning-team $(curl -sS https://api.venafi.cloud/v1/teams -H "tppl-api-key: $APIKEY" | jq '.teams[0].id') \
  --output-file /tmp/agent-credentials.json \
  --api-key $APIKEY
make oci-push-preflight oci_preflight_image_name=ttl.sh/mael/venafi-agent oci_preflight_image_tag=v0.0.0-dev oci_platforms=linux/arm64,linux/amd64
make helm-chart oci_preflight_image_tag=v0.0.0-dev helm_chart_version=0.0.0-dev oci_preflight_image_name=ttl.sh/mael/venafi-agent
helm push _bin/scratch/image/venafi-kubernetes-agent-0.0.0-dev.tgz oci://ttl.sh/mael/charts
helm upgrade -i -n venafi --create-namespace venafi-kubernetes-agent oci://ttl.sh/mael/charts/venafi-kubernetes-agent --version 0.0.0-dev \
  --set config.clusterName="$USER temp" --set config.clientId="$(jq -r .client_id /tmp/agent-credentials.json)"
kubectl create secret generic -n venafi agent-credentials --from-literal=privatekey.pem="$(jq -r .private_key /tmp/agent-credentials.json)" \
  --dry-run=client -o yaml | kubectl apply -f -

Now, cause an error by re-deploying with a broken client ID, for example:
helm upgrade -i -n venafi --create-namespace venafi-kubernetes-agent oci://ttl.sh/mael/charts/venafi-kubernetes-agent --version 0.0.0-dev \
  --set config.clusterName="$USER temp" --set config.clientId=bogus

You should see in the pod's events:
$ k describe -n venafi pod -l app.kubernetes.io/name=venafi-kubernetes-agent
Events:
  Type     Reason      Age   From                     Message
  ----     ------      ----  ----                     -------
  Normal   Scheduled   65s   default-scheduler        Successfully assigned venafi/venafi-kubernetes-agent-585989f47-4kj5g to kind-control-plane
  Normal   Pulled      65s   kubelet                  Container image "ttl.sh/mael/venafi-agent:v0.0.0-dev" already present on machine
  Normal   Created     65s   kubelet                  Created container venafi-kubernetes-agent
  Normal   Started     65s   kubelet                  Started container venafi-kubernetes-agent
  Warning  PushingErr  59s   venafi-kubernetes-agent  retrying in 31.071441118s after error: post to server failed: failed to execute http request to Venafi Control Plane. Request https://api.venafi.cloud/v1/oauth/token/serviceaccount, status code: 400, body: [{"error":"invalid_grant","error_description":"Not found"}
]
  Warning  PushingErr  28s  venafi-kubernetes-agent  retrying in 1m4.430613764s after error: post to server failed: failed to execute http request to Venafi Control Plane. Request https://api.venafi.cloud/v1/oauth/token/serviceaccount, status code: 400, body: [{"error":"invalid_grant","error_description":"Not found"}
]

By the way, Olu and I maintain this unofficial API documentation for the clusterdata endpoint: API Documentation for /v1/tlspk/upload/clusterdata.

I moved away from using /var/run/secrets/kubernetes.io/serviceaccount/namespace to load the namespace. The namespace is now loaded from POD_NAMESPACE.
I finished testing (see instructions in description) and was able to show that the events feature works.

It should be good to go.

I stumbled upon this Kubernetes Event Style guide, and the Events you're adding in this PR seem to match their guidance:

https://github.com/kubernetes/community/blob/master/contributors/devel/sig-instrumentation/event-style-guide.md

I'm somewhat unhappy with the if os.Getenv("POD_NAME") condition since it might not be enough (we might also want to make sure other env vars are set, such as POD_UID).
That said, POD_NAME is the only mandatory field needed on the object for the event to be successfully received, it seems. That said, I'm unsure of which fields of the object need to be present on the event to be "correct".
Regardless, I think this PR is good to go.


Deepstream WebSocket support

Is there any work on updating this to work over DS WebSockets instead of the HTTP interface?

Hello codyaray, there isn't any work happening on that front. Happy to provide advise to anyone who wants to give it a shot!

Can this provide RPCs and such then? I haven't looked at the DS HTTP interface yet.

It can't provide RPCs no, just make them currently. Having a webhook RPC aspect is certainly interesting but the server doesn't currently allow it.


button docs are incorrect

As per https://github.com/driftyco/ionic/commit/938864e8d0d82a131089119b896a91006947fda6
Button docs still suggest
<button>Button</button>

This should be
<button ion-button>Button</button>

Hello, thanks for using Ionic! We are currently in the process (literally as im typing this haha) of updating the docs site to the latest release, RC.0, which includes the correct button docs. Thanks!


[Forms] input-group and ABIDE form-error are incompatible

FOUNDATION 6
This doesnt work:
<form data-abide novalidate>

    <input class="input-group-field" type="text" name="first_name" required placeholder="your name">

  * This field is required

</form>

This works but not with input-group:
<form data-abide novalidate>

  <input class="input-group-field" type="text" name="first_name" required placeholder="your name">
  * This field is required

</form>

What did you expect to happen?
Show error message when the field is empty.
What happened instead?
Abide can not display the error message because it can not find the element span class="form-error"
Test case:
Give us a link to a CodePen or JSFiddle that recreates the issue.
http://codepen.io/ingedgarmorales/pen/OXWLyN

This is a duplicate of #7802.


undefined method `log' for nil:NilClass

Hi,
I have a sinatra app that tries to log some messages in the controller, here is some sample code:
get '/foo' do
   logger.info('foo')
end

And here is the exception I got from the stacktrace. Do I miss anything on piping sinatra's logger to trinidad? I found a trinidad plugin here and wondering whether I need to add it to the stack (https://github.com/trinidad/trinidad_logging_extension).
Error: Couldn't handle error: response committed
org.jruby.exceptions.RaiseException: (NoMethodError) undefined method `log' for nil:NilClass
	at JRuby::Rack::ServletLog.write(file:/Users/oou/.rvm/gems/jruby-1.6.6/gems/jruby-rack-1.1.3/lib/jruby-rack-1.1.3.jar!/jruby/rack/servlet_log.rb:18)
	at Rack::CommonLogger.log(/Users/oou/.rvm/gems/jruby-1.6.6/gems/rack-1.4.1/lib/rack/commonlogger.rb:39)
	at Rack::CommonLogger.call(/Users/oou/.rvm/gems/jruby-1.6.6/gems/rack-1.4.1/lib/rack/commonlogger.rb:22)
	at org.jruby.RubyProc.call(org/jruby/RubyProc.java:258)
	at Rack::BodyProxy.close(/Users/oou/.rvm/gems/jruby-1.6.6/gems/rack-1.4.1/lib/rack/body_proxy.rb:17)
	at JRuby::Rack::Response.write_body(file:/Users/oou/.rvm/gems/jruby-1.6.6/gems/jruby-rack-1.1.3/lib/jruby-rack-1.1.3.jar!/jruby/rack/response.rb:111)
	at JRuby::Rack::Response.respond(file:/Users/oou/.rvm/gems/jruby-1.6.6/gems/jruby-rack-1.1.3/lib/jruby-rack-1.1.3.jar!/jruby/rack/response.rb:50)
Error: Couldn't handle error: response committed
org.jruby.exceptions.RaiseException: (NoMethodError) undefined method `log' for nil:NilClass
	at JRuby::Rack::ServletLog.write(file:/Users/oou/.rvm/gems/jruby-1.6.6/gems/jruby-rack-1.1.3/lib/jruby-rack-1.1.3.jar!/jruby/rack/servlet_log.rb:18)
	at Rack::CommonLogger.log(/Users/oou/.rvm/gems/jruby-1.6.6/gems/rack-1.4.1/lib/rack/commonlogger.rb:39)
	at Rack::CommonLogger.call(/Users/oou/.rvm/gems/jruby-1.6.6/gems/rack-1.4.1/lib/rack/commonlogger.rb:22)
	at org.jruby.RubyProc.call(org/jruby/RubyProc.java:258)
	at Rack::BodyProxy.close(/Users/oou/.rvm/gems/jruby-1.6.6/gems/rack-1.4.1/lib/rack/body_proxy.rb:17)
	at JRuby::Rack::Response.write_body(file:/Users/oou/.rvm/gems/jruby-1.6.6/gems/jruby-rack-1.1.3/lib/jruby-rack-1.1.3.jar!/jruby/rack/response.rb:111)
	at JRuby::Rack::Response.respond(file:/Users/oou/.rvm/gems/jruby-1.6.6/gems/jruby-rack-1.1.3/lib/jruby-rack-1.1.3.jar!/jruby/rack/response.rb:50)

Thanks,
Owen

I am running other environment other than development.

dejavu jruby/jruby-rack#88


Catch error from http.get and skip tests

This PR adds proper error handling if the http.get call fails. This was happening when https://packages.fhir.org had the invalid cert error. When this happened, the app would throw an error that was not handled. This caused the indexedDB in the browser to be set up incorrectly, so it could never later successfully download the same package it failed on. It also caused the loading spinner in the "To JSON" button to never stop spinning.
This PR catches the error, logs an error, and resolves the promise with the typical "empty" set of packages we use in other places. This means that the app no longer throws an error, it properly cleans up indexedDB, the spinner stops, and the console pops open with the error message. It also means we can properly download the package later on. The majority of these changes are whitespace changes.
To test this locally with this branch, since https://packages.fhir.org is working again, I've been testing with a URL that doesn't exist, like https://test.packages.fhir.org. On master, if you clear out your indexedDB database, you'll get an error logged in the web console and the app will look like it is hanging. On this branch, the app's console will open with an error message. You should also be able to replace the original url and the packages should download as expected.
I have no idea how to test this. If anyone reviewing this has some brilliant insight into it, please save me from myself. Otherwise, the tests are skipped.

Those tests were tricky!
In the process of doing so, I ran into two issues.  I don't know why we did not see this before, but apparently if you are issuing requests to an https site, you are supposed to use the https module (not http).  I discovered this because when I got nock working, I started getting the error discussed in this StackOverflow question.  The other issue I fixed, after discussing with @jafeltra, was to add the failed package to emptyDependencies after the error is caught.

Ugh. Wow. Thank you for your brilliance and patience in figuring this out. I definitely feel much better knowing there is a way to test the functionality we actually want.
And thanks for catching that missing line! I think I must have had it on some stash and completely forgot that I had changed it. I approve of your changes/my own PR! Woo!


Ensure environment variables are read

So must require env before require webpackConfig and jestConfig, otherwise, the environment-specific settings will not work, see create-react-app

LGTM.
Great catch. Missed this point in my cleanup PR's series

@timarney  When will it be released?

<EMAIL_ADDRESS>


Workaround TD.net bug

see https://github.com/aspnet/PlatformAbstractions/issues/2
cc @bricelam

I might just wrap the whole method in a try..catch. If anything goes wrong, assume it's not DNX.


question about creating a CosMx object

Hi I have been trying to create a CosMx object using the spateo.io.nanostring.read_nanostring function. I firstly encountered an error

I fixed it by rounding the coordinates to integers.
I then encountered the following error:

Not sure if this error raised by the argument label_columns, buy my cell names are strings in the format c_1_1_1. Also do you have a good guideline of how to use spateo on CosMx data?
Thank you so much!

Hi,
Sorry for the delayed response and thank you for using the package! I suspect the coordinates being passed to CV2 may not be tuples. If this is still an issue, would you mind showing the formatting of the spatial coordinates in your AnnData object?


Can't execute

When I click to Execute it got to error page
There has been an error processing your request
Exception printing is disabled by default for security reasons.
Error log record number:<PHONE_NUMBER>631
I saw in report<PHONE_NUMBER>631 and this is error message:

{
"0":"Area code is already set",
"1":"
#1 Magento\Framework\App\State\Interceptor->___callParent() called at [vendor/magento/framework/Interception/Interceptor.php:138]\n#2 Magento\Framework\App\State\Interceptor->Magento\Framework\Interception\{closure}() called at [vendor/magento/framework/Interception/Interceptor.php:153]\n#3 Magento\Framework\App\State\Interceptor->___callPlugins() called at [generated/code/Magento/Framework/App/State/Interceptor.php:26]\n#4 Magento\Framework\App\State\Interceptor->setAreaCode() called at [vendor/magemojo/m2-ce-cron/Model/Schedule.php:492]\n#5 MageMojo\Cron\Model\Schedule->executeImmediate() called at [vendor/magemojo/m2-ce-cron/Controller/Adminhtml/Reports/Execute.php:32]\n#6 MageMojo\Cron\Controller\Adminhtml\Reports\Execute->execute() called at [generated/code/MageMojo/Cron/Controller/Adminhtml/Reports/Execute/Interceptor.php:24]\n#7 MageMojo\Cron\Controller\Adminhtml\Reports\Execute\Interceptor->execute() called at [vendor/magento/framework/App/Action/Action.php:108]\n#8 Magento\Framework\App\Action\Action->dispatch() called at [vendor/magento/module-backend/App/AbstractAction.php:231]\n#9 Magento\Backend\App\AbstractAction->dispatch() called at [vendor/magento/framework/Interception/Interceptor.php:58]\n#10 MageMojo\Cron\Controller\Adminhtml\Reports\Execute\Interceptor->___callParent() called at [vendor/magento/framework/Interception/Interceptor.php:138]\n#11 MageMojo\Cron\Controller\Adminhtml\Reports\Execute\Interceptor->Magento\Framework\Interception\{closure}() called at [vendor/magento/module-backend/App/Action/Plugin/Authentication.php:143]\n#12 Magento\Backend\App\Action\Plugin\Authentication->aroundDispatch() called at [vendor/magento/framework/Interception/Interceptor.php:135]\n#13 MageMojo\Cron\Controller\Adminhtml\Reports\Execute\Interceptor->Magento\Framework\Interception\{closure}() called at [vendor/magento/framework/Interception/Interceptor.php:153]\n#14 MageMojo\Cron\Controller\Adminhtml\Reports\Execute\Interceptor->___callPlugins() called at [generated/code/MageMojo/Cron/Controller/Adminhtml/Reports/Execute/Interceptor.php:39]\n#15 MageMojo\Cron\Controller\Adminhtml\Reports\Execute\Interceptor->dispatch() called at [vendor/magento/framework/App/FrontController.php:159]\n#16 Magento\Framework\App\FrontController->processRequest() called at [vendor/magento/framework/App/FrontController.php:99]\n#17 Magento\Framework\App\FrontController->dispatch() called at [vendor/magento/framework/Interception/Interceptor.php:58]\n#18 Magento\Framework\App\FrontController\Interceptor->___callParent() called at [vendor/magento/framework/Interception/Interceptor.php:138]\n#19 Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception\{closure}() called at [app/code/Ess/M2ePro/Plugin/HealthStatus/Magento/Framework/App/FrontController.php:79]\n#20 Ess\M2ePro\Plugin\HealthStatus\Magento\Framework\App\FrontController->processDispatch() called at [app/code/Ess/M2ePro/Plugin/AbstractPlugin.php:43]\n#21 Ess\M2ePro\Plugin\AbstractPlugin->execute() called at [app/code/Ess/M2ePro/Plugin/HealthStatus/Magento/Framework/App/FrontController.php:42]\n#22 Ess\M2ePro\Plugin\HealthStatus\Magento\Framework\App\FrontController->aroundDispatch() called at [vendor/magento/framework/Interception/Interceptor.php:135]\n#23 Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception\{closure}() called at [vendor/magento/framework/Interception/Interceptor.php:153]\n#24 Magento\Framework\App\FrontController\Interceptor->___callPlugins() called at [generated/code/Magento/Framework/App/FrontController/Interceptor.php:26]\n#25 Magento\Framework\App\FrontController\Interceptor->dispatch() called at [vendor/magento/framework/App/Http.php:136]\n#26 Magento\Framework\App\Http->launch() called at [generated/code/Magento/Framework/App/Http/Interceptor.php:24]\n#27 Magento\Framework\App\Http\Interceptor->launch() called at [vendor/magento/framework/App/Bootstrap.php:258]\n#28 Magento\Framework\App\Bootstrap->run() called at [pub/index.php:40]\n</pre>",
"url":"/magemojocron/reports/execute/jobcode/sales_grid_order_creditmemo_async_insert/key/60c251d5681a53088e0ae300163841241baaeca9c7822bf0eebba1f216468ac5/",
"script_name":"/index.php"
}

Same here.

Issue was fixed in https://github.com/magemojo/m2-ce-cron/commit/01ed9d91b8a6a2d78c220381dad05997fa657d40#diff-16f39d85ba47492ad0b58a52ae4c2a41