Concerning Django logs

In the production server, we have this Django logs, repeating every ~5 minutes:
django_1          | RuntimeError: Unexpected ASGI message 'websocket.close', after sending 'websocket.close'.
django_1          | [2023-06-23 13:08:02 +0000] [14] [INFO] ('<IP_ADDRESS>', 43088) - "WebSocket /submission_output/" 403
django_1          | [2023-06-23 13:08:02 +0000] [14] [ERROR] Exception in ASGI application
django_1          | Traceback (most recent call last):
django_1          |   File "/usr/local/lib/python3.8/site-packages/uvicorn/protocols/websockets/websockets_impl.py", line 157, in run_asgi
django_1          |     result = await self.app(self.scope, self.asgi_receive, self.asgi_send)
django_1          |   File "/usr/local/lib/python3.8/site-packages/uvicorn/middleware/proxy_headers.py", line 45, in __call__
django_1          |     return await self.app(scope, receive, send)
django_1          |   File "/usr/local/lib/python3.8/site-packages/uvicorn/middleware/asgi2.py", line 7, in __call__
django_1          |     await instance(receive, send)
django_1          |   File "/usr/local/lib/python3.8/site-packages/channels/sessions.py", line 183, in __call__
django_1          |     return await self.inner(receive, self.send)
django_1          |   File "/usr/local/lib/python3.8/site-packages/channels/middleware.py", line 41, in coroutine_call
django_1          |     await inner_instance(receive, send)
django_1          |   File "/usr/local/lib/python3.8/site-packages/channels/consumer.py", line 58, in __call__
django_1          |     await await_many_dispatch(
django_1          |   File "/usr/local/lib/python3.8/site-packages/channels/utils.py", line 51, in await_many_dispatch
django_1          |     await dispatch(result)
django_1          |   File "/usr/local/lib/python3.8/site-packages/channels/consumer.py", line 73, in dispatch
django_1          |     await handler(message)
django_1          |   File "/usr/local/lib/python3.8/site-packages/channels/generic/websocket.py", line 240, in websocket_disconnect
django_1          |     await self.disconnect(message["code"])
django_1          |   File "/app/src/apps/competitions/consumers.py", line 65, in disconnect
django_1          |     await self.close()
django_1          |   File "/usr/local/lib/python3.8/site-packages/channels/generic/websocket.py", line 226, in close
django_1          |     await super().send({"type": "websocket.close"})
django_1          |   File "/usr/local/lib/python3.8/site-packages/channels/consumer.py", line 81, in send
django_1          |     await self.base_send(message)
django_1          |   File "/usr/local/lib/python3.8/site-packages/channels/sessions.py", line 236, in send
django_1          |     return await self.real_send(message)
django_1          |   File "/usr/local/lib/python3.8/site-packages/uvicorn/protocols/websockets/websockets_impl.py", line 234, in asgi_send
django_1          |     raise RuntimeError(msg % message_type)

@dtuantran Any thoughts on this?


hud: fix a subtle bug in log display

Hello @landism,
Please review the following commits I made in branch nicks/ch1013/logs:
3e1c4977144bacb09256d0bbba9af34e0116f6b7 (2018-12-04 18:25:31 -0500)
hud: fix a subtle bug in log display

also added a bunch of tests


Implement addon loader (CommonJS + RequireJS)

Closes #96

This may not work for some build systems for the web, specifically those that derive which modules to pull in by following requires and then concat sources.

Since RequireJS is not messing with the node path and can work seamlessly with relative paths, requirejs users can stick with the native way of loading these modules.


IConsumer.StoreOffset should call rd_kafka_offset_store instead of rd_kafka_offsets_store

Native library librdkafka has 2 functions for store offsets:
rd_kafka_offsets_store - for list of TopicPartitionOffsets
rd_kafka_offset_store - for only one TopicPartitionOffset
Confluent.Kafka .net library has 1 function for store offsets:
IConsumer.StoreOffset(TopicPartitionOffset offset) - for only one TopicPartitionOffset
But internally, .net implementation always call list-specific function rd_kafka_offsets_store.
See Consumer.cs#L32 function just wraps TopicPartitionOffset with 1-element array and then call native api for list of TopicPartitionOffset
By my opinion, this is not optimal implementation.
.net implementation should not wrap TopicPartitionOffset with array, it should call native api method specific to only one TopicPartitionOffset, which is already exposed by librdkafka.

additionally, it seems that rd_kafka_offset_store acquires rd_kafka_topic_rdlock whereas rd_kafka_offsets_store does not, which is worrying. @edenhill can you comment?
regarding perf., this implementation detail is just a hangover from earlier times when there was a StoreOffsets method and not a StoreOffset method (since we have Linq, the latter is generally more convenient). well pointed out.

additionally, it seems that rd_kafka_offset_store acquires rd_kafka_topic_rdlock whereas rd_kafka_offsets_store does not, which is worrying. @edenhill can you comment?
regarding perf., this implementation detail is just a hangover from earlier times when there was a StoreOffsets method and not a StoreOffset method (since we have Linq, the latter is generally more convenient). well pointed out.

@mhowlett , I am not @edenhill , but I can see that rd_kafka_offsets_store calls function rd_kafka_offset_store0 with parameter lock=1
https://github.com/edenhill/librdkafka/blob/b50e247b77864c595569f7f7e9ec8dde63258210/src/rdkafka_offset.c#L692
I am not familiar with librdkafka, but by my opinion both functions have some locking logic, they are locking something called "toppar" (topic+partition?).
So as for me, I can't see big implementation differences between them, behaviour should be the same.

@maximpashuk Your analysis on locking is correct 👍
It is recommended to use rd_kafka_offsets_store() since it does not require the rd_kafka_topic_t * handle, but just a partition_list_t of topic names and partitions.

Okay, @edenhill, you recomend always to use rd_kafka_offsets_store() function from librdkafka.
kafka-dotnet already uses it, so my issue should be closed without any fixes, am I correct?
Probably @mhowlett has some opinion.

Yes, that's correct.
We're trying to move away from the rd_kafka_topic_t APIs.

okay, I dont know about this fact then create my issue.
Now I close issue and related PR. Thanks.


Left menu

The left menu needs some redesign to make it a bit more logical. There should be a new tab that allows various Cesium display settings to be switched on and off. And we should make the names of the other tabs more logical.
The tabs should be

Select (default)
Data
Display
Publish (?)

The Select tab should show the properties of the selected object.
The Data tab should include the Colour, Extrude, and Filters stuff. This tab is to do with exploring the data using these various options.
The Display tab should contain the Imagery button. The imagery should have a tick box, not a button. Other stuff will be added later.
The Publish tab should contain the UI for published models. But I think this is temporary, once we have an easy way of switching mode between Editor mode and Publish mode, then this tab will no longer be required.

Actually, it is a bit odd to have a imagery setting in the left menu, and selecting the type of imagery with a button in the right menu. I think maybe it is better to get rid of the imagery button in the right top hand corner. Then the imagery setting in the left menu can consist of a drop down menu, where the first item is 'None' (i.e. disable imagery).


[Doc Improvement][Teams Store branding updates - III][3315910]

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/concepts/design/design-teams-app-layout-scaling.md
96
9
link
:white_check_mark:

msteams-platform/concepts/design/design-teams-app-process.md
93
8
link
:white_check_mark:

msteams-platform/concepts/design/enable-app-customization.md
91
2
link
:white_check_mark:

msteams-platform/concepts/design/overview-analytics.md
89
61
link
:white_check_mark:

msteams-platform/concepts/design/personal-apps.md
94
10
link
:white_check_mark:

msteams-platform/concepts/design/plan-responsive-tabs-for-teams-mobile.md
95
5
link
:white_check_mark:

msteams-platform/concepts/design/plan-to-monetize.md
100
0
link
:white_check_mark:

msteams-platform/concepts/design/strategize-measure.md
90
34
link
:white_check_mark:

msteams-platform/concepts/design/understand-use-cases.md
95
3
link
:white_check_mark:

msteams-platform/get-started/choose-what-suits-you.md
98
4
link
:white_check_mark:

msteams-platform/graph-api/proactive-bots-and-messages/graph-proactive-bots-and-messages.md
95
5
link
:white_check_mark:

msteams-platform/includes/get-started/get-started-use-app-studio.md
94
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.

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/concepts/design/design-teams-app-layout-scaling.md
96
9
link
:white_check_mark:

msteams-platform/concepts/design/design-teams-app-process.md
93
8
link
:white_check_mark:

msteams-platform/concepts/design/enable-app-customization.md
91
2
link
:white_check_mark:

msteams-platform/concepts/design/overview-analytics.md
89
61
link
:white_check_mark:

msteams-platform/concepts/design/personal-apps.md
94
10
link
:white_check_mark:

msteams-platform/concepts/design/plan-responsive-tabs-for-teams-mobile.md
95
5
link
:white_check_mark:

msteams-platform/concepts/design/plan-to-monetize.md
100
0
link
:white_check_mark:

msteams-platform/concepts/design/strategize-measure.md
90
34
link
:white_check_mark:

msteams-platform/concepts/design/understand-use-cases.md
95
3
link
:white_check_mark:

msteams-platform/get-started/choose-what-suits-you.md
98
4
link
:white_check_mark:

msteams-platform/graph-api/proactive-bots-and-messages/graph-proactive-bots-and-messages.md
95
5
link
:white_check_mark:

msteams-platform/includes/get-started/get-started-use-app-studio.md
94
6
link
:white_check_mark:

msteams-platform/includes/tabs/dotnet-core-prereq.md
82
7
link
:white_check_mark:

msteams-platform/m365-apps/cards-loop-component.md
94
7
link
:white_check_mark:

msteams-platform/m365-apps/overview.md
93
7
link
:white_check_mark:

msteams-platform/m365-apps/publish.md
88
10
link
:white_check_mark:

msteams-platform/messaging-extensions/design/messaging-extension-design.md
91
14
link
:white_check_mark:

msteams-platform/resources/bot-v3/bot-conversations/bots-conv-proactive.md
86
23
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema-dev-preview.md
91
37
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema.md
91
38
link
:white_check_mark:

msteams-platform/samples/app-templates.md
91
47
link
:white_check_mark:

msteams-platform/samples/integrate-web-apps-overview.md
93
8
link
:white_check_mark:

msteams-platform/samples/teams-low-code-solutions.md
96
3
link
:white_check_mark:

msteams-platform/tabs/tabs-link-unfurling.md
98
2
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/concepts/design/design-teams-app-layout-scaling.md
96
9
link
:white_check_mark:

msteams-platform/concepts/design/design-teams-app-process.md
93
8
link
:white_check_mark:

msteams-platform/concepts/design/enable-app-customization.md
91
2
link
:white_check_mark:

msteams-platform/concepts/design/overview-analytics.md
89
61
link
:white_check_mark:

msteams-platform/concepts/design/personal-apps.md
94
10
link
:white_check_mark:

msteams-platform/concepts/design/plan-responsive-tabs-for-teams-mobile.md
95
5
link
:white_check_mark:

msteams-platform/concepts/design/plan-to-monetize.md
100
0
link
:white_check_mark:

msteams-platform/concepts/design/strategize-measure.md
90
34
link
:white_check_mark:

msteams-platform/concepts/design/understand-use-cases.md
95
3
link
:white_check_mark:

msteams-platform/get-started/choose-what-suits-you.md
98
4
link
:white_check_mark:

msteams-platform/graph-api/proactive-bots-and-messages/graph-proactive-bots-and-messages.md
95
5
link
:white_check_mark:

msteams-platform/includes/get-started/get-started-use-app-studio.md
94
6
link
:white_check_mark:

msteams-platform/includes/tabs/dotnet-core-prereq.md
82
7
link
:white_check_mark:

msteams-platform/m365-apps/cards-loop-component.md
94
7
link
:white_check_mark:

msteams-platform/m365-apps/overview.md
93
7
link
:white_check_mark:

msteams-platform/m365-apps/publish.md
88
10
link
:white_check_mark:

msteams-platform/messaging-extensions/design/messaging-extension-design.md
91
14
link
:white_check_mark:

msteams-platform/resources/bot-v3/bot-conversations/bots-conv-proactive.md
86
23
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema-dev-preview.md
91
37
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema.md
91
38
link
:white_check_mark:

msteams-platform/samples/app-templates.md
91
47
link
:white_check_mark:

msteams-platform/samples/integrate-web-apps-overview.md
93
8
link
:white_check_mark:

msteams-platform/samples/teams-low-code-solutions.md
96
3
link
:white_check_mark:

msteams-platform/tabs/design/tabs-mobile.md
90
7
link
:white_check_mark:

msteams-platform/tabs/tabs-link-unfurling.md
98
2
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/concepts/design/design-teams-app-layout-scaling.md
96
9
link
:white_check_mark:

msteams-platform/concepts/design/design-teams-app-process.md
93
8
link
:white_check_mark:

msteams-platform/concepts/design/enable-app-customization.md
91
2
link
:white_check_mark:

msteams-platform/concepts/design/overview-analytics.md
89
61
link
:white_check_mark:

msteams-platform/concepts/design/personal-apps.md
94
10
link
:white_check_mark:

msteams-platform/concepts/design/plan-responsive-tabs-for-teams-mobile.md
95
5
link
:white_check_mark:

msteams-platform/concepts/design/plan-to-monetize.md
100
0
link
:white_check_mark:

msteams-platform/concepts/design/strategize-measure.md
90
34
link
:white_check_mark:

msteams-platform/concepts/design/understand-use-cases.md
95
3
link
:white_check_mark:

msteams-platform/get-started/choose-what-suits-you.md
98
4
link
:white_check_mark:

msteams-platform/graph-api/proactive-bots-and-messages/graph-proactive-bots-and-messages.md
95
5
link
:white_check_mark:

msteams-platform/includes/get-started/get-started-use-app-studio.md
94
6
link
:white_check_mark:

msteams-platform/includes/tabs/dotnet-core-prereq.md
82
7
link
:white_check_mark:

msteams-platform/m365-apps/cards-loop-component.md
94
7
link
:white_check_mark:

msteams-platform/m365-apps/overview.md
93
7
link
:white_check_mark:

msteams-platform/m365-apps/publish.md
88
10
link
:white_check_mark:

msteams-platform/messaging-extensions/design/messaging-extension-design.md
91
14
link
:white_check_mark:

msteams-platform/resources/bot-v3/bot-conversations/bots-conv-proactive.md
86
23
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema-dev-preview.md
91
37
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema.md
91
38
link
:white_check_mark:

msteams-platform/samples/app-templates.md
91
47
link
:white_check_mark:

msteams-platform/samples/integrate-web-apps-overview.md
93
8
link
:white_check_mark:

msteams-platform/samples/teams-low-code-solutions.md
96
3
link
:white_check_mark:

msteams-platform/tabs/design/tabs-mobile.md
90
7
link
:white_check_mark:

msteams-platform/tabs/tabs-link-unfurling.md
98
2
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/concepts/design/design-teams-app-layout-scaling.md
96
3
link
:white_check_mark:

msteams-platform/concepts/design/design-teams-app-process.md
93
8
link
:white_check_mark:

msteams-platform/concepts/design/enable-app-customization.md
91
2
link
:white_check_mark:

msteams-platform/concepts/design/overview-analytics.md
89
32
link
:white_check_mark:

msteams-platform/concepts/design/personal-apps.md
93
10
link
:white_check_mark:

msteams-platform/concepts/design/plan-responsive-tabs-for-teams-mobile.md
95
5
link
:white_check_mark:

msteams-platform/concepts/design/plan-to-monetize.md
100
0
link
:white_check_mark:

msteams-platform/concepts/design/strategize-measure.md
90
15
link
:white_check_mark:

msteams-platform/concepts/design/understand-use-cases.md
95
3
link
:white_check_mark:

msteams-platform/get-started/choose-what-suits-you.md
98
1
link
:white_check_mark:

msteams-platform/graph-api/proactive-bots-and-messages/graph-proactive-bots-and-messages.md
92
6
link
:white_check_mark:

msteams-platform/includes/get-started/get-started-use-app-studio.md
94
5
link
:white_check_mark:

msteams-platform/includes/tabs/dotnet-core-prereq.md
89
3
link
:white_check_mark:

msteams-platform/m365-apps/cards-loop-component.md
94
3
link
:white_check_mark:

msteams-platform/m365-apps/overview.md
95
4
link
:white_check_mark:

msteams-platform/m365-apps/publish.md
100
0
link
:white_check_mark:

msteams-platform/messaging-extensions/design/messaging-extension-design.md
90
15
link
:white_check_mark:

msteams-platform/resources/bot-v3/bot-conversations/bots-conv-proactive.md
88
13
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema-dev-preview.md
92
28
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema.md
92
27
link
:white_check_mark:

msteams-platform/samples/app-templates.md
90
41
link
:white_check_mark:

msteams-platform/samples/integrate-web-apps-overview.md
93
7
link
:white_check_mark:

msteams-platform/samples/teams-low-code-solutions.md
96
2
link
:white_check_mark:

msteams-platform/tabs/design/tabs-mobile.md
90
7
link
:white_check_mark:

msteams-platform/tabs/tabs-link-unfurling.md
98
2
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/concepts/design/design-teams-app-layout-scaling.md
96
3
link
:white_check_mark:

msteams-platform/concepts/design/design-teams-app-process.md
93
8
link
:white_check_mark:

msteams-platform/concepts/design/enable-app-customization.md
91
2
link
:white_check_mark:

msteams-platform/concepts/design/overview-analytics.md
89
32
link
:white_check_mark:

msteams-platform/concepts/design/personal-apps.md
93
10
link
:white_check_mark:

msteams-platform/concepts/design/plan-responsive-tabs-for-teams-mobile.md
95
5
link
:white_check_mark:

msteams-platform/concepts/design/plan-to-monetize.md
100
0
link
:white_check_mark:

msteams-platform/concepts/design/strategize-measure.md
90
15
link
:white_check_mark:

msteams-platform/concepts/design/understand-use-cases.md
95
3
link
:white_check_mark:

msteams-platform/get-started/choose-what-suits-you.md
98
1
link
:white_check_mark:

msteams-platform/graph-api/proactive-bots-and-messages/graph-proactive-bots-and-messages.md
92
6
link
:white_check_mark:

msteams-platform/includes/get-started/get-started-use-app-studio.md
94
5
link
:white_check_mark:

msteams-platform/includes/tabs/dotnet-core-prereq.md
89
3
link
:white_check_mark:

msteams-platform/m365-apps/cards-loop-component.md
94
3
link
:white_check_mark:

msteams-platform/m365-apps/overview.md
95
4
link
:white_check_mark:

msteams-platform/m365-apps/publish.md
100
0
link
:white_check_mark:

msteams-platform/messaging-extensions/design/messaging-extension-design.md
90
15
link
:white_check_mark:

msteams-platform/resources/bot-v3/bot-conversations/bots-conv-proactive.md
90
10
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema-dev-preview.md
92
28
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema.md
92
27
link
:white_check_mark:

msteams-platform/samples/app-templates.md
90
41
link
:white_check_mark:

msteams-platform/samples/integrate-web-apps-overview.md
93
7
link
:white_check_mark:

msteams-platform/samples/teams-low-code-solutions.md
96
2
link
:white_check_mark:

msteams-platform/tabs/design/tabs-mobile.md
90
7
link
:white_check_mark:

msteams-platform/tabs/tabs-link-unfurling.md
98
2
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/concepts/design/design-teams-app-layout-scaling.md
96
3
link
:white_check_mark:

msteams-platform/concepts/design/design-teams-app-process.md
93
8
link
:white_check_mark:

msteams-platform/concepts/design/enable-app-customization.md
91
2
link
:white_check_mark:

msteams-platform/concepts/design/overview-analytics.md
90
30
link
:white_check_mark:

msteams-platform/concepts/design/personal-apps.md
93
10
link
:white_check_mark:

msteams-platform/concepts/design/plan-responsive-tabs-for-teams-mobile.md
95
5
link
:white_check_mark:

msteams-platform/concepts/design/plan-to-monetize.md
100
0
link
:white_check_mark:

msteams-platform/concepts/design/strategize-measure.md
90
15
link
:white_check_mark:

msteams-platform/concepts/design/understand-use-cases.md
95
3
link
:white_check_mark:

msteams-platform/get-started/choose-what-suits-you.md
98
1
link
:white_check_mark:

msteams-platform/graph-api/proactive-bots-and-messages/graph-proactive-bots-and-messages.md
92
6
link
:white_check_mark:

msteams-platform/includes/get-started/get-started-use-app-studio.md
94
5
link
:white_check_mark:

msteams-platform/includes/tabs/dotnet-core-prereq.md
89
3
link
:white_check_mark:

msteams-platform/m365-apps/cards-loop-component.md
94
3
link
:white_check_mark:

msteams-platform/m365-apps/overview.md
95
4
link
:white_check_mark:

msteams-platform/m365-apps/publish.md
100
0
link
:white_check_mark:

msteams-platform/messaging-extensions/design/messaging-extension-design.md
90
15
link
:white_check_mark:

msteams-platform/resources/bot-v3/bot-conversations/bots-conv-proactive.md
90
10
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema-dev-preview.md
92
28
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema.md
92
27
link
:white_check_mark:

msteams-platform/samples/app-templates.md
90
41
link
:white_check_mark:

msteams-platform/samples/integrate-web-apps-overview.md
93
7
link
:white_check_mark:

msteams-platform/samples/teams-low-code-solutions.md
96
2
link
:white_check_mark:

msteams-platform/tabs/design/tabs-mobile.md
90
7
link
:white_check_mark:

msteams-platform/tabs/tabs-link-unfurling.md
98
2
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/concepts/design/design-teams-app-layout-scaling.md
96
3
link
:white_check_mark:

msteams-platform/concepts/design/design-teams-app-process.md
93
8
link
:white_check_mark:

msteams-platform/concepts/design/enable-app-customization.md
91
2
link
:white_check_mark:

msteams-platform/concepts/design/overview-analytics.md
90
30
link
:white_check_mark:

msteams-platform/concepts/design/personal-apps.md
93
10
link
:white_check_mark:

msteams-platform/concepts/design/plan-responsive-tabs-for-teams-mobile.md
95
5
link
:white_check_mark:

msteams-platform/concepts/design/plan-to-monetize.md
100
0
link
:white_check_mark:

msteams-platform/concepts/design/strategize-measure.md
90
15
link
:white_check_mark:

msteams-platform/concepts/design/understand-use-cases.md
95
3
link
:white_check_mark:

msteams-platform/get-started/choose-what-suits-you.md
98
1
link
:white_check_mark:

msteams-platform/graph-api/proactive-bots-and-messages/graph-proactive-bots-and-messages.md
92
6
link
:white_check_mark:

msteams-platform/includes/get-started/get-started-use-app-studio.md
94
5
link
:white_check_mark:

msteams-platform/includes/tabs/dotnet-core-prereq.md
89
3
link
:white_check_mark:

msteams-platform/m365-apps/cards-loop-component.md
95
3
link
:white_check_mark:

msteams-platform/m365-apps/overview.md
95
4
link
:white_check_mark:

msteams-platform/m365-apps/publish.md
100
0
link
:white_check_mark:

msteams-platform/messaging-extensions/design/messaging-extension-design.md
90
15
link
:white_check_mark:

msteams-platform/resources/bot-v3/bot-conversations/bots-conv-proactive.md
90
10
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema-dev-preview.md
92
28
link
:white_check_mark:

msteams-platform/resources/schema/manifest-schema.md
92
27
link
:white_check_mark:

msteams-platform/samples/app-templates.md
90
41
link
:white_check_mark:

msteams-platform/samples/integrate-web-apps-overview.md
93
7
link
:white_check_mark:

msteams-platform/samples/teams-low-code-solutions.md
96
2
link
:white_check_mark:

msteams-platform/tabs/design/tabs-mobile.md
90
7
link
:white_check_mark:

msteams-platform/tabs/tabs-link-unfurling.md
98
2
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.


handle the same operator existing in multiple OperandRegistry

/kind feature
Describe the solution you'd like
the two OperandRequests including same lite operator were created from two different OperandRegistry(one is from DV and the other one is from WSL), in this case, once the DV is uninstalled,  the lite operator operandrequest created from DV will be removed. and lite operator will also be uninstalled. But we still have WSL operator which depends on lite operator.
Anything else you would like to add:
When there is more than one registry which contains the same operator, the ODLM need to handle the uninstallation of that operator well.
Firstly, we need to think about the installation. How to recognize the operator has been installed from one registry, once the operator is requested by another OperandRequest with different registry. It will not duplicate the installation. Currently the ODLM could handle this case.
Secondly, how do we uninstall the operator when there are more than one OperandRequest with different registry containing the same operator? We need avoid ODLM delete the operator if there is at least one OperandRequest exists.
And How do we consider the uninstallation of Operator's CRs under this situation.

Implementation steps:

add the name of OperandRegistry into the subscription of operator when we the OperandRequest was created.
Deletion case 1: if there is one Registry name in subscription, delete the operator and its resource
Deletion case 2: if there are more than one Registry name in subscription, remove that name and remain the operator and its resource unchanged.


Customising url path

Hey Chris,
Love this library. I was just wondering if the following is possible. If not, that's OK, would it be OK for me to add it?
I would like custom URLs but with prefix at the start.
Let's say we have the following:
class Article < ApplicationRecord
  has_prefix_id :article
end

This will generate the following id:
article.prefix_id = article_d6AgwY7bGQLkPiZprxnm5Mva

I was wondering if it's possible to do the following:
# title: String
class Article < ApplicationRecord
  has_prefix_id :article, custom_path: title
end

article.title ='Hello world'
article.save
article.prefix_id => article_d6AgwY7bGQLkPiZprxnm5Mva_hello-world

Is this possible at the moment or would be OK to add it?

Interesting, what's the use case here? SEO?


Change the csv to readme.md files

Already be able to auto update, pending version control check

able to incremental update


Glucose Values Are Off

First of all, thank you for creating this!
It seems the Glucose values are off by ~1 mmol/l for some reason. I can find anything that would correlate to what is being pulled/pushed from Diasend.
Thanks!

Hey @boethius, thanks for checking out this project. I must admit I only tested the project with mg/dl so far and the blood glucose values are also only fetched from diasend in mg/dl (see https://github.com/burnedikt/diasend-nightscout-bridge/blob/7249e26b534020179be0f5d66896e0eed271dd3b/diasend.ts#L75).
You could try changing that to mmol_l to obtain the values directly from diasend with the correct unit?

I've put up a PR that allows to specify which unit to use for glucose values both on diasend and nightscout: https://github.com/burnedikt/diasend-nightscout-bridge/pull/3.
However, in my tests, there was no discrepancy between the values in mmol/l or mg/dl. Would've also been quite surprising as the conversion is pretty straight forward. Still, you might want to give it a try on your end as well.

Since this doesn't seem to be a mere issue of unit conversions, another thing to look at would be the timings:
The diasend API does not return any timezone information for the CGM readings but nightscout expects a timezone (as it works with ISO8601 formatted date strings). This project therefore simply takes the date and time returned from diasend and stupidly puts it into the "local" timezone, which is the timezone of the machine running the bridge / nodejs code.
This in turn could lead to an offset in the datetimes and since the values are put to wrong times, it could also explain why there's a discrepancy between the values shown in nightscout and diasend as appears to be the case for you:
As an example: Diasend just returns the following information about the date and time of a glucose reading: 2022-08-20T01:03:29. Now if this project / NodeJS is run in timezone Europe/Berlin, it will assume that the reading indeed happened 3 minutes past 1 o'clock in the morning in Berlin timezone and will forward this value to nightscout (now including the timezone). I haven't yet figured out how diasend attempts to figure out the timezone but generally, the timezone in which the glucose readings are returned from diasend could be different. To verify, you could run the bridge in "check"-mode, i.e. not sending anything to nightscout and just outputting the values to the terminal by running yarn test-run, then compare whether the times sent to nightscout appear correct.

reopening this as still awaiting feedback

@burnedikt thanks for the prompt response. The problem was the local time on the server, as that was set to UTC. Normally within this space, the timezone is less important in contrast to what time of day, so sending the values without timezone logic would do the trick. Or just not assuming the timezone of the server is the same as the timezone your are pushing to.

so sending the values without timezone logic would do the trick

Yeah, but sadly, the nightscout API (and generally Javascript) always puts the date and time in the context of the configured timezone, i.e. if you send the date and time as "2022-08-20T12:50:00" to nightscout (because that seems right in your GMT+2 timezone, without specifying a timezone) but nightscout is running configured at UTC, it will assume your date and time are already in UTC time and you'll end up with a local date and time of "2022-08-20T14:50:00" (i.e. 2 hours ahead). If you don't specify a timezone / utc offset, it will just assume you gave the time in UTC. This is actually reasonable behaviour, but diasend does not send the time in UTC but a different timezone which makes it hard.
From the nightscout api docs:

Required timestamp when the record or event occured, you can choose from three input formats

Unix epoch in milliseconds<PHONE_NUMBER>088)
Unix epoch in seconds<PHONE_NUMBER>)
ISO 8601 with optional timezone ('2018-05-03T21:40:10.088Z' or '2018-05-03T23:40:10.088+02:00')

The date is always stored in a normalized form - UTC with zero offset. If UTC offset was present, it is going to be set in the utcOffset field.

So the issue is, that the times provided by diasend do not contain timezone information (which would lead one to assume UTC), but actually, they are in a certain timezone. To not assume the timezone of the server, we'd need to send the date and time as UTC but to do that, we'd need to figure out in which timezone the diasend dates and times are defined so that we convert to UTC and not have a mess.
I might have found one way to make this less painful by checking the Date header returned by the diasend server and identifying its timezone and then putting all dates and times returned by diasend into that timzeone. Will try this out shortly.

I might have found one way to make this less painful by checking the Date header returned by the diasend server and identifying its timezone and then putting all dates and times returned by diasend into that timzeone. Will try this out shortly.

Wasn't successful, sadly. So for now, I am left with diasend sending all dates and times in "local time", but it's unclear how it determines which is the local timezone ... Without that information, any user of this project needs to correctly setup the timezone on the machine that runs this project, otherwise, there will be an offset as soon as pushing the data to nightscout. I will for now add this as a known issue to the documentation as I am out of ideas on how to fix it with the current diasend API.

Documentation made in https://github.com/burnedikt/diasend-nightscout-bridge/commit/3cfb623801d7487c61f47e1eed4eeb58c200d511


Bug: TypeError: tslib_1.__spreadArray is not a function

Describe the bug
With the latest release (rc.21) test cases using the spread operator will fail because of TypeError: tslib_1.__spreadArray is not a function. The issue is most likely coming directly from tslib (see issue linked below) and was introduced with the latest update of tslib (https://github.com/vuejs/test-utils/commit/8d27843c1522ffad2b1db74565f45c0a00479055).
To Reproduce
A reproduction can be a test case for a piece of code which uses a spread operator. Example:
 const funcToTest () => {
       const arr1 = [1, 2];
       const arr2 = [...arr1, 3];
       console.log(arr2)
}

...
 it('should do nothing' () => {
   ...
    console.log = jest.fn();
    const expectedOutput = [1, 2, 3]

    // invoke funcToTest in some nice way :)

    expect(console.log).toHaveBeenCalledWith(expectedOutput);
   ...
}

TC will fail with TypeError: tslib_1.__spreadArray is not a function
Expected behavior
Test case should pass / using the spread operator shouldn't be an issue.
Related information:

@vue/test-utils version: 2.0.0-rc.21
Vue version: 3.2.33
node version: 18.1.0
npm (or yarn) version: 8.8.0

Additional context
It's probably upstreamed from https://github.com/microsoft/tslib/issues/149

Hey @cexbrayat,
understood, should've looked more closely on the timestamps... :) With that in mind the issue is definitely not coming from VTU.
Thanks alot for your time!

Just in case someone is experiencing the same issue, the broken tslib version is comming from @vue/cli-service:
├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └─┬<EMAIL_ADDRESS>│     ├─┬<EMAIL_ADDRESS>│     │ ├─┬<EMAIL_ADDRESS>│     │ │ ├─┬<EMAIL_ADDRESS>│     │ │ │ ├─┬<EMAIL_ADDRESS>│     │ │ │ │ └──<EMAIL_ADDRESS>deduped
│     │ │ │ └──<EMAIL_ADDRESS>deduped
│     │ │ └──<EMAIL_ADDRESS>deduped
│     │ └──<EMAIL_ADDRESS>│     └─┬<EMAIL_ADDRESS>│       ├─┬<EMAIL_ADDRESS>│       │ └──<EMAIL_ADDRESS>deduped
│       └──<EMAIL_ADDRESS>deduped


Ubuntu 24.04

todo:
~opencl runtime~
~devcontainer~
need to build malibre-native-qt libs on aarch64 on 24.04
make metadrive work  -> kind of done
test for building on 20.04 in CI

I upgraded my workstation at home to 24.04 and didn't notice any issues!

Once this is merged, let's also make sure to update the containers in xx/chffr/.


'TypeError: t is undefined' when main entity is not defined.

I have strange error [TypeError: t is undefined] when I make undefined the main entity:
           - type: custom:room-card
             title: Hallway
             hide_title: false
             icon: mdi:door-closed-lock
            #  entity: sensor.hallway_lumi_weather_temperature
             show_icon: true
            #  tap_action: none
            #  double_tap_action: none
             entities:
               - entity: light.hallway_rgb_bulb
                 show_icon: true
                 state_color: true
                 name: Light
               - entity: binary_sensor.tapo_camera_motion
                 show_icon: true
                 state_color: true
                 hide_unavailable: true
                 name: Motion
               - entity: camera.tapo_camera_sd
                 show_icon: true
                 name: Camera
               - entity: binary_sensor.hallway_entrance_door_contact
                 show_icon: true
                 state_color: true
                 name: Door
             info_entities:
               - entity: sensor.hallway_lumi_weather_humidity
                 format: precision1
               - entity: sensor.hallway_lumi_weather_temperature
                 format: precision1

Originally posted by @aIexus in https://github.com/marcokreeft87/room-card/issues/56#issuecomment-1254637718

Which version do you use?

1.5.1

Sure.
When I  uncomment commented lines - there will be no errors.

I think you need to try some thing by yourself.

After clearing cash - problem disappears.

Yeah HA is weird with cache :(


PermissionManager's PermissionsResultAction List needs to WeakReference its elements

Right now, as it is written, your current PermissionsResultAction list is creating strong references to said elements. This creates issues in that when creating an anonymous callback from an Activity, it implicitly creates a reference to that Activity (according to your example). As a result, it prevents it from garbage collection, until it is eventually removed from that list.
This problem is further compounded if one were to change the device's orientation multiple times, creating multiple adds from previous Activity instances, thus keeping strong refs to them, and thus leaking memory heavily.
My suggestion would be to wrap each PermissionsResultAction element in your List as a WeakReference:
private final List<WeakReference<PermissionsResultAction>> mPendingActions = new ArrayList<>(1);

Then, when adding new actions, you would simply do the following:
mPendingActions.add(new WeakReference<PermissionsResultAction>(action));

And finally, when calling back to them, you would simply check if there's currently a valid reference to them:
while (iterator.hasNext()) {
	final WeakReference<PermissionsResultAction> callbackRef = iterator.next();
	final PermissionsResultAction callback= callbackRef.get();
	if (callback != null && callback.onResult(permissions[n], results[n])) {
		iterator.remove();
	}
	mPendingRequests.remove(permissions[n]);
}

As a result, you create a clean break from your observers that may otherwise not exist when it comes time to call them, and enable their references to get GC'd quickly.
Note that iterator block was my best guess in handling when to remove that Iterator's element given this new model. You may have to polish it slightly to determine when it gets removed given the valid state of a callback reference.

I've been thinking of using WeakReferences as a way to prevent this potential memory leak, what you have is good, thank you. The only problem would be that since there is no hard reference to the PermissionsResultAction, if garbage collection were to occur between the the initial request and the response, then the action would be lost to garbage collection.
An alternative I've been thinking about would be to use a Map of Activity/Fragments to the PermissionsResultAction(s) that they request. Then there would be a notifyDestroy(Activity/Fragment) method that would be called from the onDestroy of the requesting Activity/Fragment that would remove any references that still exist in the list. Further, if a WeakHashMap<Activity, List<PermissionsResultAction> is used, then this would ensure that if the enclosing class is not an Activity but is just some generic class, that the PermissionsResultActions and enclosing class will be able to be garbage collected when the Activity/Fragment is destroyed even if notifyDestroy was not called. Using a WeakHashMap seems optional though if the user is expected to properly notify the PermissionsManager in onDestroy.
So I see two options:

Ensures that the enclosing instance of the calling class does not leak without any change from the user of the library. Risks losing an action if the system gc's the reference between request and callback.
Require the user to notify the PermissionsManager of the onDestroy event. Risks leaking references if the user forgets to notify the PermissionsManager.

thoughts?

Looking at ActivityCompat.java and Activity.java from both support 23.0 and Marshmallow respectively, onRequestPermissionsResult() gets called similarly to onActivityResult() in the same method that dispatches the Activity's result. In the support library, it calls it from the Main handler, which only runs posted Runnables right after onStart(), since by that point, the UI is about to display in onResume().
With that said, if someone were to always register a weak-ref'd callback in onCreate(), then it'll be valid by the time the callback is invoked through the PermissionManager after an orientation change (i.e. activity ref -> weak-ref'd callback in onCreate -> onStart -> onResume -> config change calling onPause, onStop, and onDestroy and thus freeing the callback to GC -> new activity ref -> new weak-ref'd callback in onCreate -> onStart -> onRequestPermissionsResult with a valid ref, onResume).
In other words, we shouldn't concern ourselves with a dead Activity reference that contained an anon callback. We should instead only callback to what can be called back. The first option is always the path of least resistance because it always assumes the worst that a dev can do, which in this case, acts as an insurance policy against memory leaks caused by devs copy-pasting the snippet and nothing else.

Those are good points, I'm going to switch to using WeakReferences instead of hard references.

Fixed in https://github.com/anthonycr/Grant/releases/tag/v1.1


nerdctl images appears to be racy / fail in certain circumstances

Description
Seen on the CI:
=== Failed
=== FAIL: cmd/nerdctl/image TestRemove/Remove_image_with_running_container_-_with_-f (0.93s)
    image_remove_test.go:306: ======================== Pre-test cleanup ========================
    command.go:112: /usr/local/bin/nerdctl --namespace=testremove-private-a0b107b8 rm -f testremove-remove-image-with-running-container-with-f-e9c3b26f
    command.go:112: /usr/local/bin/nerdctl --namespace=testremove-private-a0b107b8 rmi -f
    image_remove_test.go:306: ======================== Test setup ========================
    command.go:112: /usr/local/bin/nerdctl --namespace=testremove-private-a0b107b8 run --pull always -d --name testremove-remove-image-with-running-container-with-f-e9c3b26f ghcr.io/stargz-containers/alpine:3.13-org sleep 3600
    command.go:112: /usr/local/bin/nerdctl --namespace=testremove-private-a0b107b8 image inspect ghcr.io/stargz-containers/alpine:3.13-org
    image_remove_test.go:306: ======================== Test Run ========================
    command.go:112: /usr/local/bin/nerdctl --namespace=testremove-private-a0b107b8 rmi -f ghcr.io/stargz-containers/alpine:3.13-org
    command.go:112: /usr/local/bin/nerdctl --namespace=testremove-private-a0b107b8 images
    command.go:112: assertion failed: expression is false: strings.Contains(stdout, compare): Output does not contain: "<none>"
        Command:  /usr/local/bin/nerdctl --namespace=testremove-private-a0b107b8 images
        ExitCode: 0
        Stdout:   REPOSITORY    TAG    IMAGE ID    CREATED    PLATFORM    SIZE    BLOB SIZE

        Stderr:   time="2024-12-02T22:04:46Z" level=warning msg="content digest sha256:ec14c7992a97fc11425907e908340c6c3d6ff602f5f13d899e6b7027c9b4133a: not found"

        Env:
        HOSTNAME=cd6946756de5
        SYSTEMD_EXEC_PID=47
        container=docker
        HOME=/root
        LANG=C.UTF-8
        INVOCATION_ID=c7ba162bd0dd405697721433a973325e
        TERM=xterm
        SHLVL=3
        CGO_ENABLED=0
        _=/usr/local/bin/gotestsum
        PATH=/usr/local/go/bin:/usr/local/go/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
        ***
        DOCKER_CONFIG=/tmp/TestRemoveRemove_image_with_running_container_-_with_-f268936920/001
        NERDCTL_TOML=/tmp/TestRemoveRemove_image_with_running_container_-_with_-f268936920/001/nerdctl.toml
    image_remove_test.go:306: ======================== Processing subtests ========================
    case.go:164: ======================== Post-test cleanup ========================
    command.go:112: /usr/local/bin/nerdctl --namespace=testremove-private-a0b107b8 rm -f testremove-remove-image-with-running-container-with-f-e9c3b26f
    command.go:112: /usr/local/bin/nerdctl --namespace=testremove-private-a0b107b8 rmi -f ec14c799

So, nerdctl images does output a content digest sha256:ec14c7992a97fc11425907e908340c6c3d6ff602f5f13d899e6b7027c9b4133a: not found, which may suggest that it first retrieved the full image list, then tried to do some lookup on one of the images, and failed.
It is unclear if this prevents other images from being listed, or if this is a different problem entirely.
Must be investigated.
Steps to reproduce the issue

Describe the results you received and expected
na
What version of nerdctl are you using?
main
Are you using a variant of nerdctl? (e.g., Rancher Desktop)
None
Host information
No response

This appears more and more.
Could it be a recent regression?
https://github.com/containerd/nerdctl/actions/runs/12131315521/job/33823232239

Confirming this is hitting a good number of builds:
https://github.com/containerd/nerdctl/actions/runs/12322888864/job/34397435860?pr=3739


[ZEPPELIN-4387] Run travis_check.py using Github Actions instead of Jenkins

What is this PR for?
Full CI migration to Github Actions will take time. (ZEPPELIN-4385)
Meanwhile, we can make Github Actions do the same job Jenkins used to do, so we can have CI status in all contributors pull requests.
What type of PR is it?
Improvement
What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-4387
Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? no

Hmm.. This does not brings Github Actions on, and I still see

Looks like we can not use Github Actions?

@Leemoonsoo I can see github action on pull request for my repo, but unable to trigger github action for apache repo. I think github action is enabled for apache project, so I suspect maybe it is due to zeppelin itself. Do you know how the jenkins job is triggered before ? Maybe it causes the github action untouched.

we are using Github Actions now. Closed.


Support Workspace Trust

Filed here https://github.com/microsoft/vscode-python/issues/16126
I'm filing this in case they forget our extension.
Hello :wave: I'm from the VS Code team.
Recently, we have been exploring a security feature we refer to as Workspace Trust. This feature is intended to centralize and unify a security conscious decision required by a variety of VS Code features. With workspace trust, the user will be able to declare whether or not they trust the folder that is opened in VS Code before these features are executed.
Why you should care
Your extension is incredibly popular with VS Code users! We want to make sure that those users have a delightful experience with workspace trust and that includes extension authors deciding how much of their extension is supported in an untrusted workspace.
Workspace Trust experience
You can enable the feature with the following setting security.workspace.trust.enabled. Once enabled, you will see the following dialog when opening folders in VS Code.

This dialog is important for allowing the user to make a decision early and understand the impact of their decision. Once you understand the feature, you may want to customize when to display the dialog using the setting security.workspace.trust.startupPrompt.
You can follow the development of Workspace Trust and provide feedback in issue #106488.
Workspace trust API
First off, all of what I am about to say can be found in issue #120251. That issue will include discussion of the feature and any updates to the feature.
The Workspace Trust extension API is now in stable. This allowed us to release the first cut of our guide for onboarding your extension to Workspace Trust. The API is small, so here is a quick look.
You can declare your extension to provide complete, partial or no support in untrusted workspaces using the untrustedWorkspaces capability in package.json.
The following example declares that the extension is supported completely in untrusted workspaces. In this case, the extension is enabled in untrusted workspaces.
"capabilities": {
  "untrustedWorkspaces": {
    "supported": true
  }
}

The next example declares that the extension is not supported in untrusted workspaces. In this case, the extension is disabled in untrusted workspaces.
"capabilities": {
  "untrustedWorkspaces": {
    "supported": false
  }
}

The third option is to declared limited support. There are three tools provided to you when you select the limited option.
First, if you have a setting that can be configured in the workspace but requires the workspace to be trusted in order to apply the workspace value, then you can include the setting using restrictedConfigurations array property in untrustedWorkspaces object. Doing so, VS Code will ignore the workspace value of these restricted settings when your extension reads these settings values using the VS Code Workspace Configuration API.
The following example declares the settings that are restricted in untrusted workspaces.
"capabilities": {
  "untrustedWorkspaces": {
    "supported": "limited",
    "restrictedConfigurations": [
      "markdown.styles"
    ]
  }
}

Next, you can also check and listen if the current workspace is trusted or not programmatically using the following API:
export namespace workspace {
  /**
   * When true, the user has explicitly trusted the contents of the workspace.
   */
  export const isTrusted: boolean;
  /**
   * Event that fires when the current workspace has been trusted.
   */
  export const onDidGrantWorkspaceTrust: Event<void>;
}

Lastly, you can hide commands or views declaratively with the isWorkspaceTrusted context key in your when clauses.
A far more detailed guide on how to onboard which will be updated as we receive feedback can be found in issue #120251.
Rollout plan
Workspace Trust will remain disabled for the month of May, but we are planning on enabling this by default in the future. To prepare for that day, we would love for you to try it out and provide feedback.
We'd love your feedback
Since this issue was created in an automated fashion, we won't be monitoring the responses in this issue (our notifications would explode!). Instead we ask you to drop questions, and feedback in issue #120251 as we've mentioned above.
We're excited to see what you do with workspace trust!

The API/workflow could change.
We'll need to discuss with VS Code before working on this.

@rebornix Please see comments here https://github.com/microsoft/vscode-jupyter/issues/5938#issuecomment-847119136

I think there's still customer development work to be done even when the workspace is trusted. Do users understand that opening a notebook could execute code?

Do users understand that opening a notebook could execute code?

Not sure what you mean.
By execution of code, I'm assuming you mean execution of rendered output

Yes the javascript in the rendered output (as well as markdown, although I think we should just scrape that even in trusted notebooks like collab? does)
Do customers even think that a notebook can do something nasty just by opening it.

I mean maybe there's a 2nd option for notebooks. Trust but don't let any javascript run or something like that.

If workspace is not trusted:

We support partial trusted workspaces (to allow opening & viewing notebooks)
Interactive window

Hide run cell (debug) & similar code lenses that run code
Ensure interactive window cannot be opened when not trusted

WebView notebooks

Hide the trusted icon
Disable changing kernels
Hide run & related buttons in webview notebooks
Do we render the output by using old trust functionality (i.e. if worksapce is not trusetd, assume notebook is not trusted and use old code to achieve laoding of notebooks & hiding output) - easier than refactoring everything.
When a workspace is trusted, trigger trusting of the notebook model (easier than refactoring everything)

Native Notebooks

Hide trust icon (remove old implementation of trust for native notebooks)
No need to do anything special in Native Notebooks

Miscellaneous

Disable opening interactive window (in case we miss something, e.g. we miss a command)
Hide run commands in command palette (Use appropriate when clauses)
Disable auto start
Native notebooks - Disable kernel fetching (return empty list).
Once trusted, trigger fetching kernels for native notebooks.

Python Extension API

They will not load when workspace is not trusted.
If user trusts a worksapce, then extension gets activated later (hence some of our code might have to change, e.g. fetching kernels, etc).

When workspace is trusted, re-enable the stuff that was disabled

Basically we should ensure users don't have to re-load window
Re-enable code lenses
Re-enable commands (this will happen automatically via when clauses, hence no changes to support this)
Re-enable run buttons in webviews

This still doesn't address the question of whether a user will expect javascript code to run just on open. Even when trusted. I suspect most people don't realize this fact. They don't worry at all about opening notebooks because, hey I'm just opening it.
Trusted workspaces is basically making this even more obtuse because the decision is on a whole workspace. They might have not even realized they had trusted the workspace 3 weeks ago and now they open a notebook.
Maybe you're referring to this?

We support partial trusted workspaces (to allow opening & viewing notebooks)

What's a partially trusted workspace? What does Jupyter do for 'untrusted' notebooks? Do they scrape javascript from outputs until you run them?

They might have not even realized they had trusted the workspace 3 weeks ago and now they open a notebook.

Same applies to other extensions.
E.g. i might have trusted a worksapce 3 weeks ago, and now I just open a workspace and open the test explorer for  python, that ends up running code (automatically).
Or i could trust a worksapce 3 weeks ago and do a git pull on some repo that ends up pulling some malicious python code..

Either way, this is a generic problem that needs to be addressed by the core VS Code product.

Either way, this is a generic problem that needs to be addressed by the core VS Code product.

Or we could handle it for notebooks at least. I think it wouldn't be horrible if notebooks didn't run javascript until you ran a cell.

we could handle it for notebooks at least. I think it wouldn't be horrible if notebooks didn't run javascript until

I believe this is what VS Code products hopes to avoid, have a unified experience for all. If something doesnt work, then tweak their product to handle such cases.

Can't run cells, open interactive window, commands and code lenses are hidden when the workspace is untrusted.
Validated


net/netip: Is4In6 should return true for well-known prefixes used in IPv4/IPv6 translation

Go version
go1.22-20240109-RC01  linux/amd64
Output of go env in your module/workspace:
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/usr/local/google/home/furry/.cache/go-build'
GOENV='/usr/local/google/home/furry/.config/go/env'
GOEXE=''
GOEXPERIMENT='fieldtrack,boringcrypto'
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/usr/local/google/home/furry/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/usr/local/google/home/furry/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/usr/lib/google-golang'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/usr/lib/google-golang/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.22-20240109-RC01 cl/597041403 +dcbe772469 X:fieldtrack,boringcrypto'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='clang'
CXX='clang++'
CGO_ENABLED='0'
GOMOD='/dev/null'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -fno-caret-diagnostics -Qunused-arguments -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build3244063302=/tmp/go-build -gno-record-gcc-switches'

What did you do?
https://go.dev/play/p/FwpGyqH1hio
package main
import (
"fmt"
"net/netip"
)
func main() {
// An IPv4-mapped IPv6 Address (RFC4291).
ipv4Mapped := "::ffff:<IP_ADDRESS>"

// An IPv6 address synthesized from a "Well-Known Prefix" (64:ff9b::/96, RFC6052)
nat64WKP := "64:ff9b::<IP_ADDRESS>"

// An IPv6 address synthesized from a Local-Use IPv4/IPv6 Translation Prefix
// (64:ff9b:1::/48, RFC8215) and <IP_ADDRESS>
rfc8215WKP := "64:ff9b:1::<IP_ADDRESS>"

// Printing the addresses in their canonical text representation,
// rfc5952#section-5
fmt.Printf("IPv4-mapped address: %s\n", netip.MustParseAddr(ipv4Mapped).String())
fmt.Printf("NAT64 address: %s\n", netip.MustParseAddr(nat64WKP).String())
fmt.Printf("RFC8215 address: %s\n", netip.MustParseAddr(rfc8215WKP).String())

}
What did you see happen?
The output:
IPv4-mapped address: ::ffff:<IP_ADDRESS>
NAT64 address: 64:ff9b::c000:201
RFC8215 address: 64:ff9b:1::c000:201
Only the first address is printed in mixed notation (https://datatracker.ietf.org/doc/html/rfc5952#section-5). That indicates that Is4In6() only recognizes ::ffff:0:0/96 as a well-known prefix, used for embedding IPv4 addresses into IPv6 ones.
Both 64:ff9b::/96 (RFC6052) and 64:ff9b:1::/48 (RFC8215) prefixes are not recognized as used for having IPv4 addresses embedded in the lower 32 bits.
As both prefixes are well-known and reserved by IANA (https://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-special-registry.xhtml), I believe Is4In6() shall be updated (happy to write that code, indeed).
P.S. I'd also argue that for backwards compatibility it would be beneficial to recognize ::/96 as a Well-Known Prefix, despite its deprecation, as there are still systems around which might be using it.
What did you expect to see?
All 3 addresses shall be represented using mixed notation, as per https://datatracker.ietf.org/doc/html/rfc5952#section-5
"mixed notation is RECOMMENDED if the following condition is met: the address can be distinguished as having IPv4 addresses embedded in the lower 32 bits solely from the address field through the use of a well-known prefix.
Such prefixes are defined in [RFC4291] and [RFC2765] at the time of this writing."

@ianlancetaylor @neild if you could give this a look.

My 2 cents: I like this proposal, but I hope we can create a new function (if needed) instead of changing the current Is4In6. I believe we should keep Is4In6 and Unmap in sync, and it seems nice that the current Unmap is reversible, which means Is4In6 probably should not recognize more translations.

I believe that Is4In6 should not be deprecated. IPv4-mapped IPv6 addresses are essentially IPv4 addresses represented in IPv6 format, without any additional significance. They are, in essence, IPv4 addresses, and many systems will treat them as such. For instance, sending a packet with an IPv4-mapped IPv6 address on a dual-stack machine will result in an IPv4 packet being sent. Therefore, Is4In6 is valuable in determining whether an IPv4 packet will be transmitted. It is also useful for checking whether an IPv6 address is suitable for AAAA records in DNS.
This distinction is crucial when compared to other protocols, which aim to send genuine IPv6 packages with an embedded address. The need for a different prefix in these cases arises from this fundamental difference. For example, IPv4-embedded IPv6 addresses are designed to be used in AAAA records, while IPv4-mapped ones should never appear in them. Therefore we should avoid conflating IPv4-mapped IPv6 addresses with other IPv4-translatable or IPv4-embedded IPv6 addresses. We could potentially have Unmap handle all prefixes specified by RFCs, but there should be a clear way to differentiate between them.

netip.Addr.Is4In6 is documented as reporting whether an address is "an IPv4-mapped IPv6 address".
RFC 4291, section <IP_ADDRESS> defines an IPv4-mapped IPv6 address as in the subnet ::ffff:0:0/96. RFC 5156, section 2.2 has a more concise definition.
Since "IPv4-mapped IPv6 address" is a term of art with a specific definition, Is4In6's current behavior is correct and should not change. https://go.dev/cl/617835 makes the Is4In6 documentation more explicit.
A separate question is whether we should use mixed notation when formatting RFC6052 and RFC8215 addresses. That seems like it would be reasonable, but I haven't thought about it in detail.


scintling goo wont harvest when using a shovel

Issues that do not follow this template will be closed
Describe the Bug:
nothing will harvest the slime left behind, having to kill them for the goo but making it difficult to set up a farm with them because of this am i missing something the quest does say use a shovel

Well that was about as unhelpful as you cna get, any comment would have been helpful


[FLINK-20345][table-planner-blink] Adds an Expand node only if there are multiple distinct aggregate functions in an Aggregate when executes SplitAggregateRule

What is the purpose of the change
An Expand node is only necessary when multiple aggregate function with different distinct keys appear in an Aggregate. However an unnecessary Expand node will be generated under some special cases, like the following sql.
SELECT COUNT(c) AS pv, COUNT(DISTINCT c) AS uv FROM T GROUP BY a.
This pull request aims to avoid generate unnecessary Expand node.
Brief change log

SplitAggregateRule check only need expand  if there are multiple distinct aggregate functions in an Aggregate

Verifying this change
This change is already covered by existing tests, such as SplitAggregateITCase, DistinctAggregateTest, SplitAggregateRuleTest . Besides, this change added IT and UT in SplitAggregateITCase and SplitAggregateRuleTest
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)

@JingsongLi Done. please have a look, thanks.


Berlin Hackathon 2023 Device Management

Description

Documentation for the updated private device management features.
Motivation and Context

Updates to Private Device Management.
Redirect all App, System App, and Account Allow List references to a single page.
Moved page out of Team Management and into Private Device Management section.
Moved How to find Bundle ID from MDM into a separate page.

Types of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[X] Documentation fix (typos, incorrect content, missing content, etc.)

Do you have any suggestions to fix the deployment to the dev bucket step?

Re deploy to dev failure: The workflow doesn't set (for me) the environment variables for the deploy to bucket step. Local docusaurus build looks OK.
ALGOLIA_APP_ID:
ALGOLIA_KEY:

Build steps don't like merging from a fork.


fix(linter-formatter): escape  XML control characters in ruleId

Please refer to #746.
This PR is make escape XML control characters in ruleId.

Nice catch! Thanks!


Updating Fastclick

Hi, I´m having this issue as described here: http://stackoverflow.com/questions/32034503/links-and-clicks-fail-to-open-with-cordova-on-ios-8-4-1
A suggested solution seems to be updating Fastclick.
How can I update it to the latest version in maui?

@mcasimir This is REALLY important. Mobile Angular UI is basically broken on the latest version of iOS. How can we update the version of fastclick used with Mobile Angular UI?

I concur. This has rendered an app completely useless on iOS.

In my case it could be fixed with css, but I guess that´s not the best way to do it ...
a, button { opacity:1 !important; }

Strange but worked:

That MAY fix it for a and button elements, but any other element with ng-click behavior would still be broken.

Sure, just wanted to share it as it´s a lifesafer when your app is going to go live tomorrow.

i also need a fixed version of MobileAngularUI very quick! our app is currently useless...

For now, I installed the latest version of Fastclick via bower ON TOP of maui, and it solved my problem.

so is it enough to change the bower.json to
"fastclick": "1.0.6"
and rebuild the current sources?

I have been having the same problem and I installed FastClick on top of MAUI.  I would love to see MAUI's dependencies (font-awesome, bootstrap, fastclick, and overthrow), included as runtime dependencies instead of compile time ones.  This would give me a lot more customizability for dealing with issues like this on my own.

Any update on this issue. @lylepratt can you share how you configure FastClick with MAUI? Which version of MAUI?

I just overrode the MAUI included with my own bundled version and made sure it loaded AFTER MAUI.

I found that removing 'mobile-angular-ui.plugins.ui-router' on bower and updating to MAUI 1.2.0 works. But the view is screwed up (need to reskin). I don't fully understand why we need this module or how to get around it

Any update on this?  I would love to remove extra version of fastclick from our project.


Blog post for the Prometheus OpenCost Exporter

New integration adding it to the blog, docs to follow

Dropped comments on work doc draft!

Like the screenshot addition, but should you show a metric actually tried to cost (e.g. node_hourly_cost) vs resource allocation? That seems more relevant.
Also, I could go either way on Prom logo... don't feel it's required.

Like the screenshot addition, but should you show a metric actually tried to cost (e.g. node_hourly_cost) vs resource allocation? That seems more relevant.

Updated to node_cpu_hourly_cost against a GKE node

Also, I could go either way on Prom logo... don't feel it's required.

Removed

Looking good to me. Maybe worth getting one more set of eyes on it?
When are you hoping to launch?


Privacy Policy

Hi Your Privacy Policy states that you are using the EU US Privacy shield which has been invalidated by the ECJ. Surely  you are using another safeguard such as the Standard Contractual Clauses. Please confirm this in writing as we may need to put a stop on use of this product and look into other products from Microsoft we have in place to ensure they are compliant.
Thank you
RejaneC2023
[Enter feedback here]

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

ID: cd0e0f68-d088-d0b7-cbb7-56bb16e4026f
Version Independent ID: 8a107028-31a6-6821-a150-1ebdd7a7d440
Content: Microsoft Teams Privacy - Microsoft Teams
Content Source: Teams/teams-privacy.md
Service: msteams
GitHub Login: @MicrosoftHeidi
Microsoft Alias: heidip

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.
As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.
If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.
With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.
Here's what the new experience looks like.
Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.
First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful
Article was unhelpful

Finally, select Submit and you're done!


input[number] does not initialize when ng-model is a string ("123")

When you have an <input type="number" ng-model="value"/> and the value is a string containing a numeric value (e.g. "123"), the input control is blank.  If a value is a numeric (e.g. 123) the control value is properly initialized.
I would expect that both a model number 123 and a string "123" would initialize the input the same.
http://jsfiddle.net/nonplus/23SJ9/3/
Reproducable in Chrome and FF against AngularJS 1.2.10.
BTW, this looks like a duplicate of #1126 although that one seems to be also dealing with formatting.

  Was surprised this coercion was not handled since it is so pervasive in javascript.

Figured out a way to pull this off: https://gist.github.com/rizen/5f76357f6758dd8f6f74

How is this still an issue in 2016?

It's not an issue - it is expected behavior :smiley:
Fortunately, Angular is flexible enough to let you change it, using an appropriate custom directive (if you absolutely need to).

Clearly that behavior wasn't expected by me and others on this thread, otherwise I wouldn't have filed a case.  Though apparently it is now documented behavior as of Angular 1.3.1.
@rizen, thanks for your fix, works great.
FWIW, I don't want to be casting stones here since I've used the "it's not a bug, it's a feature" excuse myself and told clients of my code to RTFM and "work around it".  But "fixing" unexpected behavior via documentation always made me feel a bit dirty. ;-)

You're welcome @nonplus

If it was/is intended behaviour, that's fine, it's just that it seems a little funky and not obvious until something bad happens. Sure you get a console message but 99.99999% of users don't even know what the console is. All they end up saying is "where is my data?" It would have been nice if the value would end up in the field but trigger validation and ng-messages.
Anyway there is a work around, so thanks @rizen


Rework scripts task to be more dynamic

For each folder in the scripts folder, use the folder name as the file name, and concatenate all scripts within it.

This is mostly done, but the scripts don't recompile correctly upon save.

Done!


Not an issue thread - 19+ Stable Diffusion Tutorial Videos

Hello dear Daniel Schosser, I hope you let this thread stay to help newcomers
Here the list of videos to with the order to follow
All videos are very beginner friendly - not skipping any parts and covering pretty much everything
Playlist link on YouTube: Stable Diffusion Tutorials, Automatic1111 and Google Colab Guides, DreamBooth, Textual Inversion / Embedding, LoRA, AI Upscaling, Pix2Pix, Img2Img
1.) Automatic1111 Web UI - PC - Free
Easiest Way to Install & Run Stable Diffusion Web UI on PC by Using Open Source Automatic Installer

2.) Automatic1111 Web UI - PC - Free
How to use Stable Diffusion V2.1 and Different Models in the Web UI - SD 1.5 vs 2.1 vs Anything V3

3.) Automatic1111 Web UI - PC - Free
Zero To Hero Stable Diffusion DreamBooth Tutorial By Using Automatic1111 Web UI - Ultra Detailed

4.) Automatic1111 Web UI - PC - Free
DreamBooth Got Buffed - 22 January Update - Much Better Success Train Stable Diffusion Models Web UI

5.) Automatic1111 Web UI - PC - Free
How to Inject Your Trained Subject e.g. Your Face Into Any Custom Stable Diffusion Model By Web UI

6.) Automatic1111 Web UI - PC - Free
How To Do Stable Diffusion LORA Training By Using Web UI On Different Models - Tested SD 1.5, SD 2.1

7.) Automatic1111 Web UI - PC - Free
8 GB LoRA Training - Fix CUDA & xformers For DreamBooth and Textual Inversion in Automatic1111 SD UI

8.) Automatic1111 Web UI - PC - Free
How To Do Stable Diffusion Textual Inversion (TI) / Text Embeddings By Automatic1111 Web UI Tutorial

9.) Automatic1111 Web UI - PC - Free
How To Generate Stunning Epic Text By Stable Diffusion AI - No Photoshop - For Free - Depth-To-Image

10.) Python Code - Hugging Face Diffusers Script - PC - Free
How to Run and Convert Stable Diffusion Diffusers (.bin Weights) & Dreambooth Models to CKPT File

11.) NMKD Stable Diffusion GUI - Open Source - PC - Free
Forget Photoshop - How To Transform Images With Text Prompts using InstructPix2Pix Model in NMKD GUI

12.) Google Colab Free - Cloud - No PC Is Required
Transform Your Selfie into a Stunning AI Avatar with Stable Diffusion - Better than Lensa for Free

13.) Google Colab Free - Cloud - No PC Is Required
Stable Diffusion Google Colab, Continue, Directory, Transfer, Clone, Custom Models, CKPT SafeTensors

14.) Automatic1111 Web UI - PC - Free
Become A Stable Diffusion Prompt Master By Using DAAM - Attention Heatmap For Each Used Token - Word

15.) Python Script - Gradio Based - ControlNet - PC - Free
Transform Your Sketches into Masterpieces with Stable Diffusion ControlNet AI - How To Use Tutorial

16.) Automatic1111 Web UI - PC - Free
Sketches into Epic Art with 1 Click: A Guide to Stable Diffusion ControlNet in Automatic1111 Web UI

17.) RunPod - Automatic1111 Web UI - Cloud - Paid - No PC Is Required
Ultimate RunPod Tutorial For Stable Diffusion - Automatic1111 - Data Transfers, Extensions, CivitAI

18.) Automatic1111 Web UI - PC - Free
Fantastic New ControlNet OpenPose Editor Extension & Image Mixing - Stable Diffusion Web UI Tutorial

19.) Automatic1111 Web UI - PC - Free
Automatic1111 Stable Diffusion DreamBooth Guide: Optimal Classification Images Count Comparison Test

great

ty for comment
we got 6 new videos
updated first thread


Does this method work for Yolo-based detectors as well?

First of all, immense thank you for your amazing paper and huge contribution to the community.
I am wodnering if you personally applied your proposed method on Yolo-based detectors (either yolo HBB or yolo OBB), or other yolo-like object detectors (e.g., RTMDet) that do not use region proposal.
My intuition is that the proposed representation is so general that it can actually be applied to any type of regressor.

Thank you for your comment!
We only did a very simple experiment on RTMDet, but the RotatedIoULoss used in this kind of method conflicts with our representation approach, so we didn’t pursue it further.
Intuitively, our method might work well with Yolo-based methods that use L1Loss, but unfortunately, we didn't have the time to test it.


Fix Kconfig warnings for hwmv2 docs building.

Fixes following warnings for doc building:
warning: BOARD_MPS2 (defined at boards/arm/mps2/Kconfig:4) defined without a type
warning: BOARD_MPS3 (defined at boards/arm/mps3/Kconfig:4) defined without a type
warning: BOARD_NRF9160DK (defined at boards/nordic_nrf/nrf9160dk/Kconfig:6) defined without a type
....

and:
WARNING: toctree contains reference to nonexisting document 'boards/*/index'

please drop the index.rst changes, I'm about to open a PR fixing all that stuff. Ref #69031

done.


Send Unit results to Harbormaster

Fixes #34

@jjx

NOTE: there is a UI bug around the "No Unit Test Coverage" which is an issue in Phabricator, not with this plugin: https://secure.phabricator.com/T9365

Also @audriusm to review if you have some time

merging after verbal +1 from @jjx


no root after patch boot.img

tried with -fs 1 and -fs 2 but no root premission

Hi, I need more details. Which device ? And do you get an adb shell ?

Hi, I need more details. Which device ? And do you get an adb shell ?


Iteration Plan for July 2019

This plan captures our work in July. This is a 5-week iteration. We will ship our July Update in early August.
During this iteration, we make last polishing changes to our new icons so that you can enjoy them in Insiders and Stable. We'll keep improving the minimap and add additional controls to the settings editor. The biggest chunk of our work though goes into engineering and improvements for extensions such as multi-selection in custom views, improving LSIF and DAB, and finalizing the custom data support in our HTML and CSS support.
Also it's July. As usual, we start to see members of our team to take time off. So, if you don't get responses from us as quickly as you're used to, imagine white ocean beaches or beautiful mountains.
Endgame

July 29, 2019: Endgame begins
August 2, 2019: Endgame done

The endgame details for this iteration are tracked in tbd.
Plan Items
Below is a summary of the top level plan items.
Legend of annotations:

Mark
Description

:runner:
work in progress

:hand:
blocked task

:muscle:
stretch goal for this iteration

:red_circle:
missing issue reference

:large_blue_circle:
more investigation required to remove uncertainty

:black_circle:
under discussion within the team

UX

[ ] :runner: Iconography re-design (including main extensions) https://github.com/Microsoft/vscode/issues/8017 @misolori

Workbench

[ ] Implement workbench layout using grid widget https://github.com/Microsoft/vscode/issues/50853 @sbatten @joaomoreno
[ ] :red_circle: Support multi-selection in Custom Views @alexr00
[ ] Provide built-in support for settings with values that are lists of strings https://github.com/Microsoft/vscode/issues/62440 @octref
[ ] :red_circle: :muscle: Explore support for custom editors @mjbvz @jrieken

Accessibility

Fix actionable issues, see also https://github.com/microsoft/vscode/issues/75840 @isidorn

Editor

[ ] :red_circle: Support multi-line decorations in the minimap @rmacfarlane
[ ] :red_circle: Explore improving presentation of search results in minimap (size, theme color) @rmacfarlane
[ ] :red_circle: Revisit the tokenization implementation with the end goal to support asynchronous semantic coloring @alexandrudima
[ ] :red_circle: Explore theming support for semantic colors @aeschli
[ ] :muscle: Provide setting for visually indicating whitespace in selections https://github.com/microsoft/vscode/issues/1477 @rmacfarlane

Terminal

[ ] Add commands to focus the previous/next row when in screenreader mode https://github.com/microsoft/vscode/issues/76050 @tyriar

Languages
LSP

[ ] :red_circle: Finalize LSIF spec v0.4 with support for partitioned index updating @dbaeumer

CSS/HTML/JSON

[ ] :red_circle: :runner: Improve navigation for sass import statements @octref
[ ] :red_circle: Finalize experimental custom data support @octref

Debug

[ ] Investigate VS Code UI for data breakpoints https://github.com/microsoft/vscode/issues/76864 @weinand

API

API finalization: query
API proposals: query

Extension Contributions

[ ] :runner: Improve getting started experience with the TS Lint extension https://github.com/microsoft/vscode-typescript-tslint-plugin/issues/99 @mjbvz
[ ] :runner: Improvements to the Remote extensions (see plan here) team

Engineering

[ ] Address electron 4.0 regressions (see query) @deepak1556
[ ] :runner: Continue exploring upgrade to electron 6.0 https://github.com/microsoft/vscode/issues/76069 @deepak1556
[ ] :red_circle: Increase automation for upgrading to newer electron versions @deepak1556
[ ] :runner: Improve build performance https://github.com/microsoft/vscode/issues/75983 @joaomoreno
[ ] Adopt new Tree implementation in Custom Views https://github.com/microsoft/vscode/issues/63566 @alexr00 @sandy081
[ ] Support flattened rendering of empty nodes to enable https://github.com/Microsoft/vscode/issues/41627 @joaomoreno
[ ] :runner: Provide tooling for GDPR code annotation extraction https://github.com/microsoft/vscode/issues/75524 @lramos15
[ ] :runner: Migrate tasks to use TerminalVirtualProcess https://github.com/microsoft/vscode/issues/76492 @alexr00
[x] :runner: Finish resolveTask support https://github.com/microsoft/vscode/issues/33523 @alexr00
[ ] :red_circle: :runner: Provide a solid engineering system for vscode-ripgrep @roblourens
[ ] :runner: Remove suppressImplicitAnyIndexErrors https://github.com/microsoft/vscode/issues/76442 @mjbvz team
[ ] :red_circle: :muscle: Investigate slow emmet activations @octref

Deferred Items

none

For the following 2 minimap enhancement, I believe there issue reference is #21404 that I mentioned in last month iteration.

🔴 Support multi-line decorations in the minimap @RMacfarlane
🔴 Explore improving presentation of search results in minimap (size, theme color) @RMacfarlane

Awesome!

Can we get  white ocean beaches or beautiful mountains as the background of the Welcome screen?...
Also, Aug 2nd is by birthday (the same as when Endgame ends) so maybe in time?

Awesome can't wait to see the finished product 😁

I do not know if this is the correct place but could please check the ticket #73828
It is impossible to work with quotes and International keyboard as system language, specially with multicolumn selection.

The new icon looks good.

The related endgame is #78131. Maybe update the tbd in the issue description?


Fix reset account history

@keybase/react-hackers

CC @mmaxim

Can't we use the b64 lib we already have

Also do we have to handle this in multiple cases or should we just make a new function we call once. Like will other code call this and now do the wrong thing

Agree, maybe the safer change is to just un-base64 the convID's on the supersedes fields. I am pretty sure that is the only time this will happen. Seems like a less risky change.


SLFJ4-579: Export client packages of slf4j-api in version 1

Fixes https://jira.qos.ch/browse/SLF4J-579
This allows to use the slf4j-api version 2 artifact as drop-in replacement for slf4j-api version 1 in OSGi environments as well.
slf4j-api can now be wired to bundles that require packages of slf4j-api in version 1 or 2.
At the moment the first commit of this PR is actually handled in #330, but since it would otherwise conflict I included that as well. Once #330 is resolved, this only consists of a single, small commit (which is the second one a.t.m.).
@ceki can you please state if besides org.slf4j the packages org.slf4j.event and org.slf4j.helpers were considered part of the API in slf4j-1? You already told that some classes in org.slf4j.event were considered internal, but did that also apply for the package as a whole or where clients supposed to access some classes?

@ceki can you please have a look at this after #330?
@bjhargrave @timothyjward @stbischof do you want to have a share your opinion about the second commit (first one is in #330) from a OSGi point of view?

Thank you for the work, Hannes! Would be cool if this could be merged and released soon as it solves a lot of dependency issues.

@HannesWell  Regarding compatibility, classes/interfaces that a user can be reasonable expected to use is guaranteed to be backward-binary-compatible. On the other hand, classes/interfaces which are used by logging back-ends implementing the SLF4J API, are not offered this guarantee but the changes are usually have quite a minimal impact.
Having said this, at the scale of SLF4J distribution, no change has minimal impact.

@HannesWell  We has to rebuild the jira.qos.ch server from backups. This led to some data loss.  If you would like to
follow issues on the Jira, please register with jira.qos.ch a second time.  My apologies for the inconvenience.

@HannesWell Regarding compatibility, classes/interfaces that a user can be reasonable expected to use is guaranteed to be backward-binary-compatible. On the other hand, classes/interfaces which are used by logging back-ends implementing the SLF4J API, are not offered this guarantee but the changes are usually have quite a minimal impact.
Having said this, at the scale of SLF4J distribution, no change has minimal impact.

Yes, I understand and agree.
But the purpose of this change is to allow that one can use slf4j 2 with a logging back-end for slf4j-2 in conjunction with a consumer of the slf4j-1 API. For example there are libraries that use the slf4j-api for logging but only import the package org.slf4j with a version range of (1.7,2] MANIFEST.MF and therefore in OSGi you cannot use them with slf4j-2.
The purpose is not to let a logging backend targeted for slf4j-1 be used with the slf4j-2 api artifact.
That's the reasons why the org.slf4j.spi package is not exported in version 1.x so that a backend for slf4j-1 does not accidentally get wired to slf4j-api version 2.

What is the goal that we are trying to achieve?
@HannesWell  If the goal is to ensure backward compatibility for regular clients, than exporting "org.slf4j;version=1.7.36" makes sense.
However, by the same token, I think it would make sense to export org.slf4j.spi, org.slf4j.helpers,  org.slf4j.event version 2.0.7 for the sake of logging back-ends.  I don't think a back-end can be implemented without importing org.slf4j.spi.

@HannesWell What is the goal that we are trying to achieve?
If the goal is to ensure backward compatibility for regular clients, then exporting "org.slf4j;version=1.7.36" makes sense.

Yes, the goal is only to support clients that are programmed against slf4j-1 and only import org.slf4j with range [1.x,2) even with slf4j version two.

I don't think a logging back-end can be implemented without importing org.slf4j.spi. Moreover, given that there are very few such implementations, at least comparatively, it is reasonable to ask of them to upgrade to slf4j 2.0.x.
Thus, I think it would make sense to export org.slf4j.spi, org.slf4j.helpers, org.slf4j.event version 2.0.7 for the sake of logging back-ends.

Yes. Sorry I think my previous comments were misleading. This change only adds new exports with version 1.7.36. All previously existing exports of packages in version 2.0.7 are not changed so that the slf4j-api module exports the user/client facing packages in version 1.7.36 and 2.0.7 and the back-end facing packages are only exported in version 2.0.7.
So before this change the Export-Package entry was:
Export-Package:
 org.slf4j;uses:="org.slf4j.event,org.slf4j.helpers,org.slf4j.spi";version="2.0.7",
 org.slf4j.event;uses:="org.slf4j,org.slf4j.helpers";version="2.0.7",
 org.slf4j.helpers;uses:="org.slf4j,org.slf4j.event,org.slf4j.spi";version="2.0.7",
 org.slf4j.spi;uses:="org.slf4j,org.slf4j.event,org.slf4j.helpers";version="2.0.7"

with the current state of the change it is
Export-Package:
 org.slf4j;uses:="org.slf4j.event,org.slf4j.helpers,org.slf4j.spi";version="2.0.7",
 org.slf4j.event;uses:="org.slf4j,org.slf4j.helpers";version="2.0.7",
 org.slf4j.helpers;uses:="org.slf4j,org.slf4j.event,org.slf4j.spi";version="2.0.7",
 org.slf4j.spi;uses:="org.slf4j,org.slf4j.event,org.slf4j.helpers";version="2.0.7",
 org.slf4j;version="1.7.36";uses:="org.slf4j.event,org.slf4j.helpers,org.slf4j.spi",
 org.slf4j.event;version="1.7.36";uses:="org.slf4j,org.slf4j.helpers",
 org.slf4j.helpers;version="1.7.36";uses:="org.slf4j,org.slf4j.event,org.slf4j.spi"

So the only difference is that the packages org.slf4j org.slf4j.event and org.slf4j.helpers are additionally exported in version 1.7.36.

I don't think a logging back-end can be implemented without importing org.slf4j.spi. Moreover, given that there are very few such implementations, at least comparatively, it is reasonable to ask of them to upgrade to slf4j 2.0.x.

Yes, that makes sense. I'm update to update this PR to only export the package org.slf4j in version 2.0.7 and 1.7.36 and export the other packages in the module only with version 2.0.7.
If some artifact requires a sub-package of org.slf4j it should be encoded in that artifact's OSGi metadata with which versions of slf4j it is compatible.

Good. Thank you.
You mentioned previously that the PR could optimize for "minimal diff" or for "simplicity of understanding/maintenance". In principle, I think the latter is a better choice.

Done.
Now the exports are:
Export-Package:
 org.slf4j;uses:="org.slf4j.event,org.slf4j.helpers,org.slf4j.spi";version="2.0.7",
 org.slf4j.event;uses:="org.slf4j,org.slf4j.helpers";version="2.0.7",
 org.slf4j.helpers;uses:="org.slf4j,org.slf4j.event,org.slf4j.spi";version="2.0.7",
 org.slf4j.spi;uses:="org.slf4j,org.slf4j.event,org.slf4j.helpers";version="2.0.7",
 org.slf4j;uses:="org.slf4j.event,org.slf4j.helpers,org.slf4j.spi";version="1.7.36"

You mentioned previously that the PR could optimize for "minimal diff" or for "simplicity of understanding/maintenance". In principle, I think the latter is a better choice.

Do you mean regarding the use of the maven-bundle-plugin vs. the bnd-maven-plugin and the use of Manifest.MF files committed into this git repo?

@HannesWell  Whatever is easier to maintain on the long run.

@HannesWell Whatever is easier to maintain on the long run.

The maven-bundle-plugin uses the bnd-maven-plugin under the hood, consequently the latter receives updates earlier.
Besides that I think on the long run it is easier to have only one and the same source for OSGi metadata for all slf4j modules. Yes therefore I think it would be good to move all configuration into the bundle/bnd-plugin and get rid of the MANIFEST.MF files.
But I think this should be done in follow up PRs, so that this can land earlier. I can create corresponding small PRs for the migration if you agree. :)

Thanks a lot @ceki for your review, merge and immediate release of slf4j 2.0.7.
This will allow immediate adoption of slf4j-2 in the OSGi world. Already prepared the changes to update the Eclipse Platform to the new release.


Getting value when contenteditable is true

For example
smth
, so that we don't need to change the style of divs or texts block if we need to edit it

when contenteditable is set, can get its value from the event handler arg.
type Event Struct {
    InnerText string
}

func (c *MyComponent) Render() string {
    return `<p contenteditable onkeyup="OnKeyUp">Edit me</p>`
}

func (c *MyComponent) OnKeyUp(e Event) {
    // Your code
}

You can also use a app.MouseEvent or app.KeyboardEvent as handler argument.


Doc issue: Process.PrivateMemorySize64 Property

The example code documenting the use of Process.PrivateMemorySize64 Property does not even demonstrate PrivateMemorySize64.

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

ID: ca9b1cbd-fea8-24c5-2141-29d95503a99d
Version Independent ID: 568fb704-6832-56b2-ddec-91bdc7c48614
Content: Process.PrivateMemorySize64 Property (System.Diagnostics)
Content Source: xml/System.Diagnostics/Process.xml
Product: dotnet-api
GitHub Login: @dotnet-bot
Microsoft Alias: dotnetcontent

Thanks for pointing out that the example doesn't actually retrieve the value of Process.PrivateMemorySize64, @JesseChisholm. We've added the issue to the backlog and to the community contributor's project.


license?

Hi @kmxz. Would it be possible to add a license file into this repo? I plan to create an APK package for your software. Thanks.

I got no idea what kind of license to use.
GPL-family license is a bit too strong.
Maybe I'll put WTFPL. Is that okay?

Added.


Implement Selection Sort in Python

Algorithm/Data Structure: Selection Sort
Programming Language: Python
Difficulty: ⭐⭐
Description:
Implement the Selection Sort algorithm in Python. Selection Sort is a simple comparison-based sorting algorithm that repeatedly selects the minimum element from an unsorted portion of the list and swaps it with the first element in that unsorted portion. Your task is to correctly sort a given list of elements in ascending order using Selection Sort in Python.
Additional Information:
If you are new to Selection Sort or need guidance on implementing it in Python, feel free to ask questions or seek help in the comments. This is a great opportunity for contributors to gain experience in sorting algorithms and algorithmic optimizations in Python.
Note:
Before starting to work on this issue, please comment below to express your interest and let us know if you have any questions or need clarification on the task.

I want to work on this issue. Can you assign this to me?

@parag477 assigned. let me know if you need any help!

Can you please assign this to me

I have added the algorithm please check it and merge my PR.

Hey please merge my PR

Hi, I would like to work on this Issue, can you assign it to me please.

Hey @DIPANSHI-10 and @MeetD99,
Issues are FCFS basis only. You can choose another issue or can create your own!

hey @sobhanbera
I would like to work on this issue,so please assign it to me


add possibility to run a local instance of the explorer

as discussed recently

still think we cannot do this as long we rely on middleware and can't run the node with devmode + middleware activated 🤔
but assuming it's possible, should we directly aim to integrate with new explorer? @thepiwo

is there a plan for supporting devmode along with middleware? @jyeshe @sborrazas
would be awesome to spawn mdw (incl. devmode) along with an instance of aeScan (cc @michele-franchi)

is there a plan for supporting devmode along with middleware? @jyeshe @sborrazas
would be awesome to spawn mdw (incl. devmode) along with an instance of aeScan (cc @michele-franchi)

We currently support adding tests and contracts execution together with devmode for better middleware testing, but this requires special steps to be run when building the middleware image. We can improve the workflow to be able to do this and add better instructions on how to use the middleware together with devmode

We can improve the workflow to be able to do this and add better instructions on how to use the middleware together with devmode

this would require a special build, right? I guess we would need a published bundle image similar to what's done with the node right now. I don't think we will see it adopted if we do not have a image for it.

That's right, we would need to publish a new image that contains both mdw + devmode


Scalebar is missing

Hi,
I am using Bing maps to generate a static image and I am not able to find property to enable scalebar. Is it available if I use Bing maps to get the request and stream using Service Manager. Please find the details below:
Workflow:

Get request using BingMapsRESTToolkit.ImageryRequest

Use the request from #1 and call service manager to return stream

Get background map image out of stream

Below is the sample output which is missing scale bar.

Please let me know if I am not using the correct settings or function call or is it not supported yet. Thank you in advance!!

The Bing Maps static image service doesn't have an option to add a scalebar, thus this service wrapper doesn't expose such a feature. (Docs: https://docs.microsoft.com/en-us/bingmaps/rest-services/imagery/get-a-static-map)
That said, if you know the zoom level and center coordinate of the map image, a scale could be calculated and a scalebar added using a drawing library. If you want to explore this route, here is an old blog I wrote that does something similar via WPF: https://rbrundritt.wordpress.com/2014/10/09/multiple-measurement-scale-bar-in-wpf/ The drawing/UX part would be different, but the math would be the same.

rbrundritt - thank you so much for your reply and help!!

Not sure on that one. It would depend on how you are creating the scale bars. If doing this in XAML, it's possible there is some "best fit" scaling happening of the control.