CIP-0036 | Adding the deregistration metadata format

Adding the deregistration metadata format to the README.md and the schema.cddl
The deregistration metadata uses the key 61286 and is independent from the registration metadata which uses key 61284
Updating CIP-0010 (metadata datum registry), description for key 61285(witness) and 61286(deregistration)

please everybody see, for prior discussion:

https://github.com/cardano-foundation/CIPs/pull/348#issuecomment-1268721923
https://github.com/cardano-foundation/CIPs/pull/335#issuecomment-1263991634

so, this should now be the final PR hopefully 😄
we had a discussion, and @kevinhammond agreed, that the until now unused but reserved key 61286 could be used to add a deregistration metadata format. this is independent from the registration metadata format and that part of CIP-0036 is untouched. the specification is currently only for the voting_purpose=0 (Catalyst). other voting_purpose values (voting-chains) may use a different way to specify a deregistration. the goal was that to always produce valid registration metadata and not abuse the use of an invalid registration metadata to act like a deregistration. this addition in the PR should now give a clear format if users/tools want to do a de-registration of the stake credentials on the catalyst voting chain.

we had a discussion, and @kevinhammond agreed, that the until now unused but reserved key 61286 could be used to add a deregistration metadata format.

Yes

the specification is currently only for the voting_purpose=0 (Catalyst). other voting_purpose values (voting-chains) may use a different way to specify a deregistration.

Technically, this is specific to Catalyst voting on the corresponding Jormungandr voting chains (it is possible that purpose 0 might also be collated and used by a third party, for example, as a generic/non-specific vote delegation).

The main reason for not wanting to use eg an empty delegation array or second metadata format for deregistration purposes is that this creates complication for hardware wallets (perhaps two apps are needed).

There is no need imo that hardware wallets have to support all features, thats why i wrote the line:
https://github.com/cardano-foundation/CIPs/blame/6e2cf66230bf662b04065ec75098f27695045fcc/CIP-0036/README.md#L154
I don't see a problem if deregistraton would not be supported on hardware wallets.

OK, this all seems in order then 😎


fix: fix formatter adding -- to multiple use statements

This PR fixes #684

Inadvertently stashed my test… For the rename, it's because of a weird formatter bug, I'm going to explicit it

Ok implementing the suggested solution. It turns out that the "struct" renaming was indeed linked to 2 blocks of code being identical and a newline appearing because of it.

It turns out that the "struct" renaming was indeed linked to 2 blocks of code being identical and a newline appearing because of it.

What were the odds lol

I updated the "Temporary workaround" section about formatting, because, as shown by fe5016ce, we actually do format non-compiling code.


Error while parsing pseudopage in cssParser

Pseudo classes for @page don't work.
{% block extra_style %}
    <style type="text/css">
        @page {
            color: black;
        }
        @page :first {
            color:red;
        }
    </style>
{% endblock %}

It raises TypeError:
TypeError: unsupported operand type(s) for +: 'NoneType' and 'str' at xhtml2pdf/w3c/cssParser.py in _parseAtPage, line 726

This is not a supported feature, did you find it in the documentation?
xhtml2pdf is not supposed to render and behave like a browser, rather it should be fast and use the HTML language to easily structure PDF documents in a developer friendly language.
You can solve this problem programatically.
{% for item in objects %}
    {% if forloop.is_first %}
        <pdf:nexttemplate first>
    {% else %}
        <pdf:nexttemplate default>
    {% endif %}
{% endfor %}
{% block extra_style %}
    <style type="text/css">
        @page default {
            color: black;
        }
        @page first {
            color:red;
        }
    </style>
{% endblock %}


Swipe List Error when changing data source

Hi!, i having a problem with swipeable List i couldn't figure out how to resolve
Im using a code like this
list = () => { 		return ( 			<List 				bounces={false} 				dataSource={this.ds.cloneWithRows( 					this.props.trackerData[this.state.category] 				)} 				renderRow={this.renderRow} 				disableRightSwipe 				renderRightHiddenRow={(data, secId, rowId, rowMap) => {...}} 				rightOpenValue={-130} 			/> 		) 	}
Here is an image of my View
Im using list view to render elements from an array of data, an lets say, i render 2 elements in this list, AND swipe LAST element an let it open.

then if i change category in my state, it means it change the data source of the list, and the new list has fewer elements than the previous one, AND SWIPE an element lets say the FIRST ONE, im getting this error.

it happens when the index of the previous opened element, is higher than the length of the actual datalist.
im getting
null is not an object (evaluating 'this._rows[this.openCellld]._root')
i have already tried lot of things like closing the row with rowMap or obtaining reference to inner elements like openCellId, but cant find solution to this.
it does not happen when i delete an element from the list and close it with 		rowMap[${secId}${rowId}].props.closeRow()

an additional validation in safeCloseOpenRow in your List component should do the trick.
safeCloseOpenRow() {
		// if the openCellId is stale due to deleting a row this could be undefined
		if (this._rows[this.openCellId] && this._rows[this.openCellId]._root) {
			this._rows[this.openCellId]._root.closeRow()
		}
	}

Any updates on this?

Here is the snack recreating the bug, https://snack.expo.io/SJqclwuI7
the error is in the following image

however as i said, the the solution is just adding that validation, i already did. Since the method try to access to an index larger than the length of the current dataSource.

yes the validation fixes the issue
Any help needed here?

Hi @SupriyaKalghatgi!
I have the same issue, and forking, adding the fix above and recompiling seemed to have resolved it for me. Any chance we can get it into master and eventually an npm release?
For me, it happens on a swipe list when I delete an element.
Thanks!

@sdacunha Well Thanks for trying the fix and reverting
I will give it a try

@cdcordobaa  Please check with latest NB(2.11.0). It seems to be working fine without any error


Spurious error on DB setup

DB setup has been observed to fail in the hosted service with the following error logs:
2022-03-16T19:29:16.264973019Z stderr F thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: JoinError::Panic(...)', /graph-node/store/postgres/src/connection_pool.rs:513:10
2022-03-16 19:29:16
2022-03-16T19:29:16.264648288Z stderr F Mar 16 19:29:16.264 CRIT migrations failed, error: store error: failed to find plan for subquery ss, pool: main, shard: blocks_a, component: ConnectionPool
2022-03-16 19:29:16
2022-03-16T19:29:16.264640948Z stderr F note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
2022-03-16 19:29:16
2022-03-16T19:29:16.264553508Z stderr F thread 'tokio-runtime-worker' panicked at 'migrations failed: store error: failed to find plan for subquery ss', store/postgres/src/connection_pool.rs:987:13

This causes graph node to crash, until it the setup eventually succeeds for all shards. It's been observed on both PG 13 and PG 14 shards.

The error comes from this line in the Postgres sources.
From PG logs, the query where that happens is
select c.column_name::text, c.data_type::text,
           c.udt_name::text, c.udt_schema::text, e.data_type::text as elem_type
      from information_schema.columns c
      left join information_schema.element_types e
           on ((c.table_catalog, c.table_schema, c.table_name, 'TABLE', c.dtd_identifier)
            = (e.object_catalog, e.object_schema, e.object_name, e.object_type, e.collection_type_identifier))
     where c.table_schema = $1
       and c.table_name = $2
     order by c.ordinal_position

I've manually run this query with all possible values for the bind variables that are used in the code, without getting an error. e.g., $1 = 'public', $2 = 'chains and $1 = 'subgraphs', $2 = 'subgraph' without getting this error.

checking here @lutter are you saying that this isn't a Graph Node issue, or is more investigation required?

It's not a graph-node issue; I've raised that with some external parties, but everybody seems to be stumped as to what causes that.

In my case, this error occurs when I try to use the information_schema.element_types table in a LEFT JOIN, I used this table to get the type of a field when it was for example integer[], because in these types the data_type column of the information_schema.columns table was just ARRAY.
I could not find out the reason for the error when querying this table, for this reason I replaced the query table with pg_catalog.pg_attribute, as shown below, and with that I had no more problems:
SELECT c.table_schema, c.table_name, c.column_name, pg_catalog.format_type(a.atttypid, a.atttypmod) as data_type
FROM information_schema.columns c
INNER JOIN information_schema.tables t ON (c.table_schema = t.table_schema and c.table_name = t.table_name)
INNER JOIN pg_catalog.pg_attribute a ON ((c.table_schema||'.'||c.table_name)::regclass = a.attrelid and a.attname = c.column_name)
WHERE c.table_name = 'checkouts'
AND c.column_name in ('payment_methods_accepted', 'status')
ORDER BY 1, 2


Add Visual Studio 2019 to AppVeyor configuration matrix

Coverage remained the same at 96.586% when pulling edd8398fa9241bf502881c353a2d65c3918c9d88 on vs2019 into 11fab0f4b6dff37a0022e6fa11a5a4a4f3680da8 on master.

moving this task to the new 3.x branch


Set default zoom order to 1

Somehow default zoom order was set to 3 instead of a much better default of 1! Goes against the docstring too.

Just as a curiosity, it's critical for nan-containing inputs, such as a matrix made from default expected with NaN'ed first two diagonals - https://github.com/Phlya/coolpuppy/issues/18


Configure resource type sort

Codecov Report

Merging #896 (a9a60b0) into 8.x (f6ab4f3) will decrease coverage by 0.01%.
The diff coverage is 95.00%.

@@             Coverage Diff              @@
##                8.x     #896      +/-   ##
============================================
- Coverage     62.74%   62.72%   -0.02%
- Complexity    11586    11592       +6
============================================
  Files          1711     1711
  Lines         55310    55319       +9
  Branches       5303     5305       +2
============================================
- Hits          34703    34701       -2
- Misses        18402    18411       +9
- Partials       2205     2207       +2

Impacted Files
Coverage Δ

...owl/core/request/ResourceSearchRequestBuilder.java
75.00% <ø> (ø)

...al/snowowl/core/request/ResourceSearchRequest.java
92.30% <91.66%> (-0.55%)
:arrow_down:

...nowowl/core/rest/resource/ResourceRestService.java
96.00% <100.00%> (-0.97%)
:arrow_down:

...src/com/b2international/snowowl/core/Resource.java
98.21% <100.00%> (+0.03%)
:arrow_up:

...ernational/snowowl/core/ResourceTypeConverter.java
100.00% <100.00%> (ø)

...owowl/core/bundle/BundleResourceTypeConverter.java
100.00% <100.00%> (ø)

...re/codesystem/CodeSystemResourceTypeConverter.java
100.00% <100.00%> (ø)

...tional/snowowl/core/internal/ResourceDocument.java
93.44% <100.00%> (+0.03%)
:arrow_up:

...al/snowowl/core/request/SearchResourceRequest.java
68.85% <0.00%> (-9.02%)
:arrow_down:

...onal/snowowl/snomed/core/tree/TerminologyTree.java
85.71% <0.00%> (-2.05%)
:arrow_down:

... and 4 more

Continue to review full report at Codecov.

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


Getting the add worker nodes script with parameters after installation is completed

At the end of the installation using kURL we get a nice reference on how to add worker nodes, i.e
To add worker nodes to this installation, run the following script on your other nodes
    curl -sSL https://kurl.sh/xxx/join.sh | sudo bash -s ...

Can I re-create this script command on demand? If not, would it be possible to plot it to some reference file in the first place during installation script?

The script can be re-generated by running the install script again. It's not persisted by default because it includes tokens with a 24 hour lifetime (or 2 hours for masters).


LICENSE file

I think there would better be a LICENSE file same with toml-lang/toml, at least in specs folder. If not, no one can use the whole translation docs in the futhur, because the default copyright belongs to all translators self.

Indeed! Thanks for flagging this @LongTengDao! ^>^
I do agree that at least the specs/ needs to have the same LICENSE as the original repository.
@cannikin You wrote the bulk of this repository's source code (everything other than the specs/ directory). How do you think we should license those?

Oh boy, the license stuff goes into legal territory and I'm not comfortable recommending anything in that area! That being said, if the original spec is MIT, then it makes sense that all translations are also MIT? Can you just put one in the parent specs directory and then covers all the translations automatically?

Yes, that sounds like how we should be handling the specs/ directory. What about the rest of the codebase though? :P

If everyone is cool with MIT I can just slap one in there. How does the copyright work? Should it be Tom's name in there?

I think toml.io's site files (layout, color scheme, etc.) should not be used by other individuals or organizations without authorization, because there should be only one official website.
I'm not sure who would better be the copyright name of site files (exclude spec files), but it should be the site files' license's primary purpose to always allow and only allow official use.

Is there any update on this? I was openning an issue to ask if I could use some code of this repo to make a site but I realised that there's no license. Have you considered to add a LICENSE file to the repo?


[Doc Improvement][Prerequisites and build environments for TTK]

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/tools-prerequisites.md
90
13
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 010fc88:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/toolkit/tools-prerequisites.md
:bulb:Suggestion
View
Details

msteams-platform/toolkit/tools-prerequisites.md

Line 4, Column 14: [Suggestion: duplicate-descriptions - See documentation] Attribute 'description' with value 'In this module, Learn how to prepare accounts to build Teams apps with Microsoft 365 account and developer program. Azure account to host backend resources' is duplicated in 'toolkit/accounts.md(4,14)', 'toolkit/tools-prerequisites.md(4,14)'.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/tools-prerequisites.md
90
13
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/tools-prerequisites.md
93
18
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 8097de8:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/toolkit/tools-prerequisites.md
:warning:Warning
View
Details

msteams-platform/toolkit/tools-prerequisites.md

Line 52, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
Line 93, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
Line 100, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/tools-prerequisites.md
92
16
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 71da7fe:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/toolkit/tools-prerequisites.md
:warning:Warning
View
Details

msteams-platform/toolkit/tools-prerequisites.md

Line 48, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 6bb7084:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/toolkit/tools-prerequisites.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/tools-prerequisites.md
93
16
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 58bc75b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/toolkit/tools-prerequisites.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
96
2
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
93
16
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
96
2
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
93
16
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/toolkit/build-environments.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/tools-prerequisites.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
85
3
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
93
6
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 88c8890:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/toolkit/tools-prerequisites.md
:warning:Warning
View
Details

msteams-platform/toolkit/build-environments.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/tools-prerequisites.md

Line 98, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
Line 109, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
85
3
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
92
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/toolkit/build-environments.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/tools-prerequisites.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
82
4
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
91
13
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 4fa2c6a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/toolkit/build-environments.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/tools-prerequisites.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
82
4
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
92
13
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/toolkit/build-environments.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/tools-prerequisites.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
78
8
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
94
13
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
90
3
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
98
10
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 09d6d20:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/toolkit/tools-prerequisites.md
:warning:Warning
View
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/personal-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/work-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/toolkit/build-environments.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/tools-prerequisites.md

Line 69, Column 7: [Warning: file-not-found - See documentation] Invalid file link: '../assets/images/teams-toolkit-v2/teams toolkit fundamentals/personal-account-icon'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 722cb5a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/personal-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/work-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/toolkit/build-environments.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/tools-prerequisites.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
90
3
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
98
11
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 98c48cf:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/personal-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/work-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/toolkit/build-environments.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/tools-prerequisites.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
90
3
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
97
12
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 7a365d3:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/toolkit/build-environments.md
:warning:Warning
View
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/personal-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/work-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/toolkit/tools-prerequisites.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/build-environments.md

Line 17, Column 3: [Warning: bookmark-not-found] Cannot find bookmark '#blazor-or-csharp' in 'toolkit/build-environments.md'.
Line 55, Column 1: [Warning: file-not-found - See documentation] Invalid file link: '../../assets/images/tdp/tdp_home_1.png'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 0b31086:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/personal-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/work-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/toolkit/build-environments.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/tools-prerequisites.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
79
11
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
97
12
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
79
11
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
97
12
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
75
18
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
97
12
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 90b9b66:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/personal-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/work-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/toolkit/build-environments.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/tools-prerequisites.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
75
18
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
97
12
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/personal-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/work-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/toolkit/build-environments.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/tools-prerequisites.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
89
8
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
97
12
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/personal-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/work-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/toolkit/build-environments.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/tools-prerequisites.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
89
8
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
97
12
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 00bd62b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/personal-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/work-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/toolkit/build-environments.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/tools-prerequisites.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
89
8
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
97
12
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 1d5a4d5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/personal-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/work-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/toolkit/build-environments.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/tools-prerequisites.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
89
8
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
97
12
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit adeee37:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/toolkit/build-environments.md
:warning:Warning
View
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/personal-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/work-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/toolkit/tools-prerequisites.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/build-environments.md

Line 12, Column 3: [Warning: bookmark-not-found] Cannot find bookmark '#javascript' in 'toolkit/build-environments.md'.
Line 13, Column 3: [Warning: bookmark-not-found] Cannot find bookmark '#sharepoint-framework-spfx' in 'toolkit/build-environments.md'.
Line 14, Column 3: [Warning: bookmark-not-found] Cannot find bookmark '#blazor' in 'toolkit/build-environments.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
90
5
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
97
13
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
90
5
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
97
13
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit e0b3f29:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/toolkit/build-environments.md
:warning:Warning
View
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/personal-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/work-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/toolkit/tools-prerequisites.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/build-environments.md

Line 12, Column 3: [Warning: bookmark-not-found] Cannot find bookmark '#javascript' in 'toolkit/build-environments.md'.
Line 13, Column 3: [Warning: bookmark-not-found] Cannot find bookmark '#sharepoint-framework-spfx' in 'toolkit/build-environments.md'.
Line 14, Column 3: [Warning: bookmark-not-found] Cannot find bookmark '#blazor' in 'toolkit/build-environments.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
91
2
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
97
12
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 04bbce3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/personal-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/work-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/toolkit/build-environments.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/tools-prerequisites.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
91
2
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
97
12
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/personal-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/work-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/toolkit/build-environments.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/tools-prerequisites.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
91
2
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
97
12
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/personal-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/work-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/toolkit/build-environments.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/tools-prerequisites.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
91
2
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
97
12
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 2ea78ce:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/personal-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/work-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/toolkit/build-environments.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/tools-prerequisites.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
91
2
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
98
11
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/personal-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/work-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/toolkit/build-environments.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/tools-prerequisites.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
100
0
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
98
10
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit e7db0ea:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/toolkit/tools-prerequisites.md
:warning:Warning
View
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/personal-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/work-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/toolkit/build-environments.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/tools-prerequisites.md

Line 181, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
100
0
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
98
10
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
100
0
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
98
10
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/personal-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/work-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/toolkit/build-environments.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/tools-prerequisites.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/build-environments.md
100
0
link
:white_check_mark:

msteams-platform/toolkit/tools-prerequisites.md
98
10
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 326f37a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/personal-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/work-account-icon.PNG
:white_check_mark:Succeeded
View

msteams-platform/toolkit/build-environments.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/tools-prerequisites.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Closing the PR as the content has been merged with #6470


Question : how to use logging only for 1 instance from the DbContext ?

As described on the wiki page: http://docs.efproject.net/en/latest/miscellaneous/logging.html, when a logger is attached, all instances share it.
Note
You only need to register the logger with a single context instance. Once you have registered it, it will be used for all other instances of the context in the same AppDomain.
How to avoid this ?
In my unit-tests, I only want logging for a specific unit-test, not for all tests.

The only way to do this at the moment would be to use a service provider to control the scope of logging. It would be the same as controlling the scope of the InMemory database - as shown in http://docs.efproject.net/en/latest/miscellaneous/testing.html.
We are going to bring back DbContext.Database.Log so that this is easier to do in the future.

@StefH @rowanmiller As of RC2, you should be able to do something like this:
public class MyContext : DbContext
{
    protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
        => optionsBuilder.UseLoggerFactory(new LoggerFactory());
}

Every time we create a new context instance we will call OnConfiguring, at which point the new LoggerFactory will be created and will be used for just that context instance.

@ajcvickers nice, I'll make sure we include that in the docs when we update to RC2 😄

Any timeline for rc2?

@StefH nothing to share yet, but we will have a timeline shortly.

Thats good to know.
Can I find / download and build the latest code from here (github)  in an easy way?

@StefH you can try getting the packages from http://myget.org/Gallery/aspnetrelease. Just make sure you get the new package names (Microsoft.EntityFrameworkCore.SqlServer etc.). You may have issues installing some of the packages until an updated version of NuGet becomes available.


angular 2 and polymer dart

it seems that angular 2 switched from dart:js to package:js with version beta.19.
polymer dart still seems to use dart:js.
not surprisingely, this breaks angular2 <-> polymer interop in many ways.

Can you clarify what you mean? AFAIK, dart:js and package:js don't invalidate each other.

i have a polymer element that wraps iron-list.
i pass a pretty nested dart object, describing the iron-list  format, to to this element.
dart object:
DataRowModel orderRows = new DataRowModel([
new Paragraph([
new DataRow([
new DataColumn('name', style: "font-weight: bold"),
new DataColumn('contact'),
new DataColumn('phone' ),
new DataColumn('pickupDate',
style: "float: right", callback: dateFormat)
where callback "dateFormat" is a static function.
there are diifferent callbacks in the class hierarchy - it works in beta.18.
in beta.19 i get "xxx.get$callback is not a function" for the different callbacks.

If this is the same issue as #32 can we please close this one to avoid confusion?

of course.


[Bug]: Activation: schema review page is not shown by default when user saves DB config

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When a user saves a database [PostgreSQL, MongoDB or MySQL], we should redirect them to the data preview page, where we show them the schema of their database and a preview of the databases tables/collection that they select from the schema.
However, the behaviour we are seeing is that users are instead redirected to the configurations tab on saving, which is incorrect.
reference
Steps To Reproduce
reference
Public Sample App
No response
Environment
Production
Issue video log
No response
Version
cloud, self hosted

As per my investigation:

The issue is reproducible only on production, not on release or latest dev setup.
The image hosted on prod is undergoing some changes due to investigation for stability issue that recently came up - i.e. the behaviour is expected to be temporary till. Once the stability issue is resolved or post the next promotion from release to prod, we should see this issue fixed on prod as well.

Moving this PR to monitoring status for now because of the two pts above. If the issue on prod is fixed, we might want to close it then.

not reproducible - will reopen if the error comes back

Re-opening because of : https://www.notion.so/appsmith/5c8aa998aa94429995a6e0825ca2df05?v=14883d075b6649be9a8748938dcc224b&p=25a341ee5b0f41748293f69b774564b6&pm=s


Info on type of component parameters

It's not clear if Blazor can support custom types for the component parameters or not. Provided examples use built-in primitive types string and int.  It's not stated what type of a property tagged with [Parameter] attribute could be.

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

ID: b211df59-e1c9-86c0-c904-31fa3c361e6d
Version Independent ID: 3f912dfc-5ba5-6c6c-ba93-1ae78508a5cc
Content: ASP.NET Core Blazor data binding
Content Source: aspnetcore/blazor/components/data-binding.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @vborovikov ... Great :question: ... Answer: Yes! ... and as you suggest, we need to surface that information.
I'd like to add it where component parameters are defined in the Component params section of the Components overview topic, and I'd like to cross-link "component parameter" here to that section.
@captainsafia ... Are u aware of any restrictions, limitations, or gotchas?
We currently say that they are ...

... public properties on the component class with the [Parameter] attribute ...

... so if there aren't any restrictions, the wording would go something like the following. Note that the C# doc on propeties uses the word "simple" over "primitive," so we probably should go that way.

... public simple or complex properties on the component class with the [Parameter] attribute ...

I can't recall any restrictions that are worthy of documenting in this way so I think that language works well!

Initially I wanted to investigate what are requirements for these custom types are because my code works if I use a parameter with string type but when I use my custom struct for the parameter type it stops working. So I assumed that I'm missing some traits like specific interface implementation in my custom type or some kind of initialization code. This kind of information I was looking for on this page.

custom struct

Structs are supported types for parameters with the usual struct characteristics, so I think it's specific to some kind of struct condition in your scenario. Open a product unit issue at ...
https://github.com/dotnet/aspnetcore/issues
... and show them your struct, your parent component, and your child component with the parameter. I suspect that they'll uncover something about your struct that does break parameters.
Please add a cc: @guardrex to your opening issue comment or return here and post a comment with the answer. It might be something that we need to call out in the topic.
In the meantime, I'm going to make that small change that I pointed out :point_up: now. This issue will close automatically, but it's ok if you come back later and post the answer on the struct situation here. I'll re-open this for more work if that's what we need to do.


Use cases

Can a cloud management gateway be used on non-domain joined computers? We have a number of workgroup servers in our DMZs we'd like to provide security updates to.  Azure AD join isn't an option for us at the moment as our domain functional level is 2003.
If you're using a CMG for software updates, are you charged for data egress on software updates (e.g. OS patches)?

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

ID: 778368d0-1054-678c-4d74-5dce1b5826c8
Version Independent ID: aaac7308-66e6-66f0-8248-14e1505c11a6
Content: Plan for cloud management gateway - Configuration Manager
Content Source: sccm/core/clients/manage/cmg/plan-cloud-management-gateway.md
Product: configuration-manager
Technology: configmgr-client
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

Hi @parabolic123,

CMG supports workgroup clients. There's some mention in the article on certificates. The main issue with workgroup clients is configuring the certificates, as there's no centralized way to do that. For more information on managing workgroup clients, see Workgroup computers

In the Cost section of this planning article, see the first bullet under Content storage:

Internet-based clients get Microsoft software update content from Windows Update at no charge. Don't distribute update packages with Microsoft update content to a cloud distribution point, otherwise you may incur storage and data egress costs.

In both instances, I think this planning article can probably include some more explicit information on these two points. Thanks for the feedback!

I just submitted a change. Once the pull request merges, this issue will automatically close. The change is in our 2002 release branch, so it won't be live until that publishes, which should be soon 😉


Link hover preview doesn't work following a code block with a backtick (`) in it

Please select the area your Bug applys to. (Multiple selections are Possible)

[ ] Onboard. Initial vault setup and import/export pods
[ ] Create. Note creation, lookup, snippets and templates
[ ] Retrieve. Backlinks, references, graph view
[ ] Structure. Refactoring, multi-vault and schemas
[ ] Publish. Sharing your repo with the world
[x] Misc (Choose this if your not sure)

Describe the bug
If there is an escaped backtick (`) in the note, the hover preview no longer works for links following it. Also such a link can no longer be opened with Ctrl + Click, only with Ctrl + Enter.

To Reproduce
Steps to reproduce the behavior:

Write the following:

[[blah.link]]

`code`

[[blah.link]]

`` code with a backtick (`) ``

[[blah.link]]

Try hovering over the links to get a preview
Notice that the last link doesn't trigger a preview

Expected behavior
All links should trigger a hover preview.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information)

OS: Windows 10
Version 0.52

Dendron Log file
Dendron doesn't log anything when hovering over links that come after an escaped backtick.

Thank you for the bug report.
I can repro this. We'll get this sorted out and let you know 🙂


[edpm_deploy]Fix a bug when cifmw_edpm_deploy_env is undefined

As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running
[x] Appropriate documentation exists and/or is up-to-date:

[x] README in the role
[x] Content of the docs/source is reflecting the changes

/approve
/lgtm

recheck
  msg: 'Failed to download metadata for repo ''repo-setup-centos-appstream'': Yum repo downloading error: Downloading error(s): repodata/d939eeb79750e57ef256f1e7052892dd3732252e2e4ac3c15e7eab8cbb558430-primary.xml.gz - Cannot download, all mirrors were already tried without success; repodata/2065f741dbfc4268c6cd106e201b8f1cc50498a7681bd7872960ff2ec9de2287-filelists.xml.gz - Cannot download, all mirrors were already tried without success; repodata/edd78dfecb6501eedf110d6c0221ef9e79729d03182b3211daeb6413aafdf4fc-modules.yaml.xz - Cannot download, all mirrors were already tried without success'

recheck
post_failure due to an issue with vexxhost (500 when trying to detach a port )


Enhance multi-module conflict check for dev mode

With this change we are:

Determining the upstream and final downstream projects that are relevant to dev mode.
Skipping final downstream projects that are jar projects
Honoring the "skip" configuration in the plugin to apply to sub-modules.

A couple high-level thoughts:

Should we do this for 'run' too?
Can we add a simple test for this?


Server is up but pages do not load - please help

Browsers and versions affected
chrome/ff/safari/all
Description
The Collider service is up and running.
The App engine is up and running.
When i load the web page i get "Invalid path: /"
on the server in my terminal window, if I use "lynx http://localhost:8080" .  I do see the https://appr.tc webpage...
Please let me know if you need any code files here, I just don't know what or where my issue is!?
Steps to reproduce
I followed this guide and all the tests are OK
https://github.com/webrtc/apprtc
Expected results
I assumed I would see something more like this...
https://appr.tc/
Actual results
at the uri, i get "Invalid path: /"

Have you started apprtc using GAE dev appserver?

@KaptenJansson no. I am using a Ubuntu 16.04 server ec2 instance. Would you recommend that I use Google App Engine?

You have to use Google app engine dev server in order to run it locally, when hosting it, yes you need to deploy it to Google app engine, it's a Google app engine app.


tests: apply workarounds to known bugs

Before running tests apply workarounds to known
distribution bugs so we reduce the amount of
test failures.

/packit retest-failed

F41 test failures is due to a known bug https://bugzilla.redhat.com/show_bug.cgi?id=2297927


Fork: the app refreshes before starting working correctly

Steps to reproduce:

Create fork chat
Continue to chat with AI asking for app changes

On the 2nd, 3rd and following changes

generated app works incorrectly only during the first use
the app preview is refreshed
then it works normally

Video: (промотать в середине, генерация долгая)
https://www.loom.com/share/d5d857cf4f0447b58fbfea4430dba071

The issue is reproduced not in Fork chat only.
It is reproduced in any chat


OpenBLAS on docker hub

Hi there! I was browsing docker hub and saw that there is an openblas/alpine image published by the openblas org that has not been updated in a while. Is this maintained by you? If so, are you seeking to build it out at all? It would be nice to have official & automated builds of OpenBLAS images for different OSs

I suspect you are looking at the base build environment image (prepared by @aytekinar for issue #1861/PR #1864) that was used in the Travis Ci tests for the (emulated) ARM architecture until we moved them to native builds on Drone. The idea of providing images has some merit but I am not sure if there is both sufficient demand and capacity.

I suppose that's what it could be? I did not delve too deeply because it appeared to be out of maintenance.
The reason I ask is not because of alpine - they get regular enough releases that I imagine most people can get away with just installing via apk. We use debian images though, and have need of recent version of OpenBLAS on those images. We've been working on a minimum OpenBLAS Dockerfile that should work with the automated docker hub builds - would there be any interest in integrating that here?

Hi @dpraul. As @martin-frbg has already pointed out, openblas/alpine is a multi-architecture alpine image that only contains the toolchain needed to build OpenBLAS from source, and is only used in the unit testing of OpenBLAS in (emulated) ARM architectures.
The reason why I cannot have automated Docker builds is that I need some sort of CI environment (such as Travis) to build the multi-architecture images. That is the very reason why the images are old --- I cannot bind hookups from Docker's alpine repository to my Travis account.
You can check what exactly I am doing under my repository, if you want.
PS: I am the owner of openblas Docker Hub group, and if you would like to integrate your solution there, I am happy to add you as a member there, too.

I see what you mean now, thanks for clarifying.
It seems I moved too quickly on opening this issue, as our priorities have changed and we no longer need to build our own version of OpenBLAS in Docker, so there's no use in integrating our solution if we won't be able to maintain it. Thanks again for taking the time to respond, though.


add abstract etcd name resolver

@lburgazzoli I just add AbstractEtcdNameResolver ptal. If any problem, we can discuss.

I'm unsure about the multiple uri provided as constructor arg as NameResolver.Factory::newNameResolver expects a single uri, am I wrong?

Yes, newNameResolver expects a single target uri, which name resolver will resolve this target uri to specific addresses, I think in our case, the target uri would be: dns+srv://_etcd-server._tcp.example.com for dns based name resolver, and etcd://etcd.v3.cluster for simple name resolver.

So I guess we should remove the multiple uri pram, isn't it ?

Actually the reason I put multiple uri param here is users have to provide specific endpoints addresses when they use simple name resolver. For dns based name resolver, this info can be resolved through dns SRV records, for simple name resolver, this info must be configured manually.

Maybe not a very good usage, if you have better suggestion, we can change this.

I see the reason but I think abstract classes should stick to the interface contract/expected behavior, then simple resolver is free to change it.

Yes, this sounds more reasonable, I will change in when I am near computer.

Would it make sense, in the future, to contribute AbstractEtcdNameResolver and dns-srv discovery to o grpc-java ?

@lburgazzoli I am not sure about this, maybe you can open an issue on grpc-java repo.

@lburgazzoli I just update this, ptal. I am going to merge it if everything ok, thus you can reuse it.

Fine with me, we can change it later on if needed

@lburgazzoli I just merged this, please update PR #25

@AdoHe done


DCO rejects commits because it's not my user handle (new!)

Today DCO bot rejected my commits but it was working fine until yesterday

Commit sha: 88f6339, Author: darksylinc, Committer: GitHub; Expected "darksylinc<EMAIL_ADDRESS>but got "Matias N. Goldberg<EMAIL_ADDRESS>
It expects my github handle instead of my full name. I noticed my Github name wasn't set to my real name in my profile so I fixed it and resubmitted the commits. However it's still rejecting the commits.
Perhaps a temporary error?
Did something change in the API?
Did I do something wrong?
Did I misunderstood the error msg?

I'm closing this because the error didn't repeat. It must've been something silly I missed.


Create a PR to solve windows users problems with paths

Possible solution (thanks to @Nircode at issue https://github.com/acacha/adminlte-laravel/issues/267):
Found the solution for windows users!
Open Filesystem.php and replace the getpath() function with the following:
protected function getPath($file)
{
if(strtoupper(substr(PHP_OS, 0,3)) == "WIN")
return $file;
else
return $this->root . '/' . $file;

}

The function now checks whether the OS is windows or something else and provides with appropriate path information. In case of windows it just forwards the file which contains the full path, in case of linux, the function will add "//" as prefix to the file path.

Solved on https://github.com/acacha/filesystem/issues/1

Update acacha/filesystem package with composer update


Pagination controls for mat-tab-group do not appear when used with the mat-sidenav

I am trying to use the mat-sidenav with the mat-tab-group and there appears to be an issue with the pagination controls for the mat-tab-group. The test app will create 3 default tabs. If you add enough tabs so that there is just enough space to show the tabs without the tab pagination controls being displayed (based on your screen width), then open the sidenav by clicking the Toggle Sidenav button, the pagination controls do not appear in the tab control. Clicking the Add Tab button to add one more tab will force the tab control to reevaluate the horizontal space and then display the pagination controls for the tab control.
It appears that that the tab control is not aware that the horizontal space has decreased, because the sidenav is open, and does not show the pagination controls. The opposite is also true that if the pagination controls are displayed when the sidenav is open, when the sidenav is closed and there is enough horizontal space that the tab control no longer needs the pagination controls they do not disappear.
The desired behavior would be that the tab control will display or not display its pagination controls when necessary as the sidenav is open and closed.
  <mat-sidenav-container fxFill>
    <mat-sidenav #sidenav mode="side">

Sidenav

    </mat-sidenav>
    <mat-sidenav-content>

          <button mat-stroked-button (click)="sidenav.toggle()">Toggle Sidenav</button>
          <button mat-stroked-button (click)="addTab()">Add Tab</button>

          <mat-tab-group>
            <mat-tab *ngFor="let tab of tabs" label="{{tab.label}}">
              Tab content for {{tab.label}}
            </mat-tab>
          </mat-tab-group>

    </mat-sidenav-content>
  </mat-sidenav-container>

import { Component } from '@angular/core';

@Component({
  selector: 'app-root',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.css']
})
export class AppComponent {
  tabs: any[] = [{label: "tab1"}, {label: "tab2"}, {label: "tab3"}]

  addTab() {
    this.tabs.push({label: "tab" + (this.tabs.length + 1)})
  }
}

@epaitz can you share a stackblitz with this setup?

@jelbourn
It might take a bit of playing around with it, and reloading between attempts, but here is the StackBlitz.
https://angular-material-mat-tab-with-sidenav.stackblitz.io
Here are the two scenarios as best I can describe them.

Have enough tabs so that the width does not need to show the pagination controls, with the sidenav closed but will need them when the sidenav is open, and then open the sidenav. The tabs will run off the screen and the pagination controls will not show unless another tab is added by clicking the Add Tab button.
Open the sidenav so that the pagination controls are visible (this should require clicking Add Tab once after the sidenav is open). Now close the sidenav so that there is enough space to show the tabs without the pagination controls…but they do not disappear. If there is still enough space to add one more tab, and not need the pagination controls, then click Add Tab and the pagination controls will disappear.

This can be fixed if we expose the updatePagination method through the tab group. Then it can be called after the sidenav state changes, which already has events that output. Should be a trivial thing to add to the public API

@andrewseguin seems strange that that would be something the user would have to do at the application level.

Has there been any progress related to this issue?

Hello,
I'm having the same problem, I think we can solve it if in the MatTabGroupBaseHeader interface (tab-group.ts:72), we add the "updatePagination" method, so we can call it from the viewChild of MatTabGroup.
I have a sidebar with a button to make it full screen or half screen so there are times when the arrows disappear.
But by calling the updatePagination method they reappear.
What do you think?

I think it's worth making the change of exposing the API. I believe the alternative is that the group is overzealous with calling it when potential changes occur. Also I'm not sure it'd ever pick up that the sidenav changes. This would be great as a community change - feel free to open a PR and we can discuss it there

It looks like #13539 was supposed to "fix" this, inasmuch as the developer can know when the container width is supposed to change and manually run updatePagination.  The docs only list that method as being available on MatTabNav, though, not the mat-tab-header (owned by MatTabGroup).  As suggested elsewhere, this does actually work:
class MyComponent {
  @ViewChild(MatTabGroup, {static: false}) tabGroup: MatTabGroup;

  toggle() {
    // ... change width

    (this.tabGroup?._tabHeader as MatTabHeader).updatePagination();
  }
}

but as you can see, I have to explicitly cast _tabHeader to MatTabHeader because it's typed as MatTabGroupBaseHeader which doesn't have an updatePagination method, as Juanfran points out above.


FE: Allow to edit active topic message filter

[ ] Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)
Is there anything you'd like reviewers to focus on?
How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

[ ] No need to
[x] Manually (please, describe, if necessary)
[ ] Unit checks
[ ] Integration checks
[ ] Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
[x] My changes generate no new warnings (e.g. Sonar is happy)
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged

Check out Contributing and Code of Conduct
A picture of a cute animal (not mandatory but encouraged)

@Haarolean, what is @QaseId() annotation used for? I wrote a test for the new functionality, but I need to figure out the value of the id.

it's a test id within our qase.io integration. Unfortunately, it doesn't allow anonymous access right now. We'll fix e2e tests ourselves, that's fine.

@Haarolean, what is @QaseId() annotation used for? I wrote a test for the new functionality, but I need to figure out the value of the id.

it's a test id within our qase.io integration. Unfortunately, it doesn't allow anonymous access right now. We'll fix e2e tests ourselves, that's fine.

All right then, from my side, the work is done. Currently, the pipeline fails because of the qaseid todo comment. Once resolved it should pass successfully.
btw. the implementation of "doesFilterCodeFieldMatchValue" is a little bit hacky because of the editor component. Apparently, it's not that easy to e2e test it using underlying HTML elements.

@michal-cesek we'll take a look at the tests once we're done with frontend review :)
That might take some time

@Haarolean fixed

@michal-cesek thanks for your contribution! The PR will get merged soon.

The filter function doesn't seem to work on 0.7.2 (I mainly used for header field).
Need to fallback to 0.7.1 to get it works.
headers.market=="XXX" or headers["market"] == "XXX"
Return no result even if data does exist.

@Zeeeeta this repo is not maintained, please see https://github.com/kafbat/kafka-ui

@Zeeeeta this repo is not maintained, please see https://github.com/kafbat/kafka-ui

Oh really, since it has release last week, didn't realize that.
Will check the kafbat repo out, thanks.


feat: add unit tests for array contains all and not contains all

Description
Introducing unit tests for Array.ContainsAll and Array.NotContainsAll. This resolves issue #237.

Coverage: 95.229% (+0.4%) from 94.859% when pulling 337b9fb04a57aff9275f08a630e68d3c26c37a0a on rrhodes:feature/237-add-unit-tests-for-array-contains-all-and-not-contains-all into c0c15b99a3951d9e667ed782e3888b0a1c2db752 on gavv:master.

Hey @gavv, I don't appear to have permission to assign reviewers - this should be ready for review now. 🙂 Happy to address any required changes or next steps shortly, thanks in advance.

Thanks for PR! The test cases looks good.
A few minor issues:

Usually we group checks for Xxx and NotXxx, interleaved together in one test. See, for example, TestArray_Contains. So ideally it should be one test TestArray_ContainsAll, for consistency.

Methods that accept value argument should have a test checking that the value is converted to its canonical form. See "canonization" subtest in TestArray_Contains. You can find details in this issue: https://github.com/gavv/httpexpect/issues/288

Tests are usually have the same order as original method. So please place new test between TestArray_Contains and TestArray_ContainsAny.

Thanks for this feedback - I'll update the PR shortly based on those suggestions.

Hi @gavv, that's your suggested changes pushed now for review.

Thanks! Small follow-up commit: 224a48a7ddf3db0f6576b4f9bc5eae23127b2235

Also welcome to discord chat :)


Testing quantile rolling windows cruncher

At the moment this is untested and raises warnings whenever it's used. Before it goes into production, we need to address this.

Fixed as of #48


No data in secret for EC2 connectionDetails

Is there an existing issue for this?

[X] I have searched the existing issues

Affected Resource(s)
ec2.aws.upbound.io Instance
Resource MRs required to reproduce the bug
Hey team
I am exploring creating ec2 instances using crossplane. I am creating a managed resource below but am encountering issues when trying to read connectionDetails about the provisioned resource. I can see the resources is synced and ready successfully and the secret is created. However there are no fields in the secret and it is completely empty. I don't see any relevant logs in the pods or events that can help explain which is leads me here. Am I doing something wrong, missing something, or is this expected?
The manifest I am using to create the instance:
apiVersion: ec2.aws.upbound.io/v1beta1
kind: Instance
metadata:
   name: test-2
spec:
  deletionPolicy: Delete
  forProvider:
    region: us-west-2
    ami: ami-01cd4de4363ab6ee8
    availabilityZone: us-west-2b
    instanceType: t2.micro
    subnetId: <some_subnet>
  providerConfigRef:
    name: aws-irsa
  publishConnectionDetailsTo:
    name: test-secret-2
  writeConnectionSecretToRef:
    namespace: crossplane
    name: test-secret-2

 kubectl get instances
NAME     SYNCED   READY   EXTERNAL-NAME         AGE
test-2   True     True    i-05da3c7201316daa4   11m

kubectl describe secret test-secret-2 -n crossplane
Name:         test-secret-2
Namespace:    crossplane
Labels:       <none>
Annotations:  <none>

Type:  connection.crossplane.io/v1alpha1

Data
====

Steps to Reproduce
Create resource using manifest above and inspect created secret
What happened?
I expected the created secret to have data about the created resource
Relevant Error Output Snippet
N/A

Crossplane Version
1.3.1
Provider Version
1.15.2
Kubernetes Version
1.28.8
Kubernetes Distribution
EKS
Additional Info
No response

@turkenf thanks for the response. The field I need is the private IP address of the provisioned instance. To support this I would have to:

Create an MR with similar changes you mentioned above
Once merged, wait for a new version to be published with my changes
Update my provider
Newly created instances should now populate the secret with the private IP

How long would a turn around for 1 & 2 typically take?

How long would a turn around for 1 & 2 typically take?

We have a regular release schedule, aiming for the last Thursday of each month, except for exceptional cases. If you open your PR and it is merged during this time, the planned date is June 27, 2024


Add naming for Synapse

Add naming for Synapse

@Nepomuceno : Could we merge this one?

This was approved some time ago.  Is there an ETA for when this will get merged/released?