[Testing ---- Don't merge]multi v2

Codecov Report
Attention: 21 lines in your changes are missing coverage. Please review.

Comparison is base (319a3d5) 48.86% compared to head (5a32032) 69.13%.
Report is 4 commits behind head on master.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##           master     #193       +/-   ##
===========================================
+ Coverage   48.86%   69.13%   +20.27%
===========================================
  Files          93       93
  Lines        7503     7549       +46
  Branches      974      968        -6
===========================================
+ Hits         3666     5219     +1553
+ Misses       3446     1869     -1577
- Partials      391      461       +70

Files
Coverage Δ

src/include/homestore/btree/btree.hpp
100.00% <100.00%> (ø)

src/include/homestore/btree/detail/simple_node.hpp
77.63% <100.00%> (+8.68%)
:arrow_up:

src/include/homestore/btree/detail/varlen_node.hpp
75.07% <100.00%> (+1.98%)
:arrow_up:

src/include/homestore/homestore.hpp
70.37% <100.00%> (+6.37%)
:arrow_up:

src/include/homestore/homestore_decl.hpp
63.63% <ø> (ø)

src/include/homestore/index/wb_cache_base.hpp
100.00% <100.00%> (ø)

src/include/homestore/replication_service.hpp
100.00% <ø> (+100.00%)
:arrow_up:

src/lib/blkalloc/blk.cpp
75.26% <ø> (+6.45%)
:arrow_up:

src/lib/blkdata_svc/blk_read_tracker.cpp
91.66% <100.00%> (+7.45%)
:arrow_up:

src/lib/homestore.cpp
86.58% <100.00%> (+13.74%)
:arrow_up:

... and 5 more

... and 45 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


The file “InstallAssistant.pkg.integrityDataV1” couldn’t be opened.

:beetle: Description
on Download InstallInfo.plist network error, reopen on Verify InstallAssistant.pkg has The file “InstallAssistant.pkg.integrityDataV1” couldn’t be opened.
:clipboard: Steps to Reproduce

Open Mist.app
Click on Installers -> macOS Sequoia
Retrying multiple times has been this error

:white_check_mark: Expected Behaviour
Automatically remediate errors where the file does not exist
:computer: Environment

Mist version: 0.20
macOS Version: Sonoma 14.5

:camera: Screenshots

:information_source: Additional context
Is there any way to get rid of all the data of the application first?

It's not a software issue, it's my network issue

Why do I keep getting emails of other people’s issues but mine where never logged or addressed?
Sent from my iphone, short but not meant to be impolite
Op 2 okt. 2024 om 11:11 heeft zeromake @.***> het volgende geschreven:

Closed #143https://github.com/ninxsoft/Mist/issues/143 as completed.
—
Reply to this email directly, view it on GitHubhttps://github.com/ninxsoft/Mist/issues/143#event-14485109379, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BLCNQ5NJSAJWNBTMRYB6SWTZZO2EJAVCNFSM6AAAAABPDYWUQCVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJUGQ4DKMJQHEZTOOI.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


[now-cli] Temporarily force TooTallNate/signal-exit#update/sighub-to-sigint-on-windows for "signal-exit" module

Fixes https://github.com/zeit/now/issues/2564.
Upstream fix PR: https://github.com/tapjs/signal-exit/pull/55.

Codecov Report

Merging #3171 into canary will increase coverage by 1.71%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           canary    #3171      +/-   ##
==========================================
+ Coverage   11.52%   13.23%   +1.71%
==========================================
  Files         268      268
  Lines       10092    10291     +199
  Branches     1300     1216      -84
==========================================
+ Hits         1163     1362     +199
- Misses       8843     8869      +26
+ Partials       86       60      -26

Impacted Files
Coverage Δ

src/util/get-files.ts
91.66% <0%> (+3.88%)
:arrow_up:

src/util/dev/router.ts
82.69% <0%> (+4.12%)
:arrow_up:

src/util/dev/yarn-installer.ts
90.74% <0%> (+5.02%)
:arrow_up:

src/util/dev/server.ts
64.48% <0%> (+5.64%)
:arrow_up:

src/util/dev/builder.ts
78.41% <0%> (+5.76%)
:arrow_up:

src/util/output/create-output.ts
66.66% <0%> (+7.29%)
:arrow_up:

Continue to review full report at Codecov.

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


Also filter tables when filtering charts

Expected behavior
Would it be possible to also filter tables when filtering a chart by type (passed, failed, skipped)?
For example in the Suite Overview when we click on the "passed" type to not display it into the chart, it could be cool to also filter the tables and to display only the "failed" and "skipped" scenarios (so it will be consistent with the Test Suite Result Chart).
Could be the same expected behavior for the Scenario details page to display only the step failure in one click and also useful in the Tag Summary page for reporting.
Actual behavior
We can filter a chart by type  but the result in the tables are not filtered.
Reproduction steps
N/A: new feature request
Additional details (Maven version, Java version, etc.)
N/A

Hello @high4life!
Thanks for your suggestion, this sounds like a great idea. I will certainly evaluate if this can be achieved!

Hello @laxersaz,
Thanks to you for this great cucumber reporting plugin !

Development in progress...

Example for new step graph:
        var chart = new Chart(ctx, eval({
            "data": {
                "labels": ["1", "2", "3", "4", "5", "6"],
                "datasets": [{
                    "data": [340.0, 0, 0, 440.0, 340.0, 0],
                    "backgroundColor": "rgba(240,0,0,1.000)",
                    "label": "failed",
                    "stack": "complete"
                }, {
                    "data": [0, 340.0, 440.0, 0, 0, 340.0],
                    "backgroundColor": "rgba(0,240,0,1.000)",
                    "label": "passed",
                    "stack": "complete"
                },]
            },
            "options": {
                "scales": {
                    "yAxes": [{
                        "ticks": {
                            "min": 0,
                        },
                        "stacked": true
                    }]
                }
            },
            "type": "bar"
        }));

Nice, I look forward to use this new "fancy" feature xD

Ready to release.

@high4life version 1.1.0 was just released and should be on Maven Central soon!


Update examples alpine 3.5 (and a few other things)

This PR updates examples and docs to Alpine 3.5,
Besides that, it changes the laravel tutorial to go back to MySql instead of Postgres.
It also adds an example on running the project on Alpine to the Ruby on Rails (Should we change the whole tutorial to Alpine?)

Great job!
One little thing, I think you've added doc folder in examples/sphinx_doc by mistake, right?

Oh, sorry, I'll remove that folder

Good. Thank you a lot for doing this!


One user can only create one token

Describe the bug

Now, one user can only create one token, if i create a token, i can't create another token.
Screenshots

Configuration File (cat ~/.config/verdaccio/config.yaml)
#
# This is the default config file. It allows all users to do anything,
# so don't use it on production systems.
#
# Look here for more config file examples:
# https://github.com/verdaccio/verdaccio/tree/master/conf
#

# path to a directory with all packages
storage: /home/pi/.local/share/verdaccio/storage
# path to a directory with plugins to include
plugins: ./plugins

web:
  title: Verdaccio
  # comment out to disable gravatar support
  # gravatar: false
  # by default packages are ordercer ascendant (asc|desc)
  # sort_packages: asc
  # convert your UI to the dark side
  # darkMode: true

# translate your registry, api i18n not available yet
# i18n:
# list of the available translations https://github.com/verdaccio/ui/tree/master/i18n/translations
#   web: en-US

auth:
  htpasswd:
    file: ./htpasswd
    # Maximum amount of users allowed to register, defaults to "+inf".
    # You can set this to -1 to disable registration.
    max_users: -1

# a list of other known repositories we can talk to
uplinks:
  npmjs:
    url: https://registry.npmjs.org/

packages:
  '@*/*':
    # scoped packages
    access: $all
    publish: $authenticated
    unpublish: $authenticated
    proxy: npmjs

  '**':
    # allow all users (including non-authenticated users) to read and
    # publish all packages
    #
    # you can specify usernames/groupnames (depending on your auth plugin)
    # and three keywords: "$all", "$anonymous", "$authenticated"
    access: $all

    # allow all known users to publish/publish packages
    # (anyone can register by default, remember?)
    publish: $authenticated
    unpublish: $authenticated

    # if package is not available locally, proxy requests to 'npmjs' registry
    proxy: npmjs

# You can specify HTTP/1.1 server keep alive timeout in seconds for incoming connections.
# A value of 0 makes the http server behave similarly to Node.js versions prior to 8.0.0, which did not have a keep-alive timeout.
# WORKAROUND: Through given configuration you can workaround following issue https://github.com/verdaccio/verdaccio/issues/301. Set to 0 in case 60 is not enough.
server:
  keepAliveTimeout: 60

middlewares:
  audit:
    enabled: true

# log settings
logs:
  - { type: stdout, format: pretty, level: http }
  #- {type: file, path: verdaccio.log, level: info}
experiments:
#  # support for npm token command
  token: true

# This affect the web and api (not developed yet)
#i18n:
#web: en-US

listen:
  <IP_ADDRESS>:4873

https://github.com/verdaccio/verdaccio/pull/1427 I find the reason in this PR.
I want to use it to distinguish between publishable and read-only users.
For example, there are three people in the team, A, B, and C. I will create three tokens. A can be published, and B and C can only use packages.

hi @Lpmvb the npm token is experimental and might not cover all scenarios. This feature might change in major releases.  There are few discussions about expire tokens in the PR section.

I think this function should be consistent with npmjs.com to reduce the mental burden of users.

I think this function should be consistent with npmjs.com to reduce the mental burden of users.

That's the goal. I'm open to anyone to help to improve it according to the architecture we have. PRs are open.

Can you please update with the current status of this?


Modify metadata generation scripts for NOM workflow to berkeley-schema-fy24

Dependent on:
https://github.com/microbiomedata/metaMS/issues/57

We will need to make change sheets for the existing metadata as well.  Related to https://github.com/microbiomedata/nmdc-schema/issues/1852 .

@brynnz22 what's the status of this?

Hi Set. This is still being worked on, I tried to move it to the next sprint, but I can never find the next sprint listed, so I just removed. Its part of the Berkeley squad. So its there now.

Hi Set. This is still being worked on, I tried to move it to the next sprint, but I can never find the next sprint listed, so I just removed. Its part of the Berkeley squad. So its there now.
Just as an update:

Biosample functionality is done
Mass Spectrometry functionality is done with the exception of the has_calibration

Thanks Brynn. I moved it to the new sprint. My suspicion is that when you look for the new sprint you are on the 'recent' tab and it won't come up there unless you've already looked at it. Try the organization tab and you should see all the sprints.

@kheal @brynnz22 new estimated completion date?

@mslarae13 I am thinking probably end of september, possibly sooner. Just want to give myself some wiggle room.

Update: Berkeley functionality is pretty much complete and updated for NOM with the exception of a few small details I need to check on with Yuri. The biggest thing left is adding calibration info for MasSpectrometery and/or NomAnalysis.

@brynnz22 any update?
since you mentioned needing till the end of Sept I'll move this to the next sprint

Sorry Set I am so bad about moving these ahead of time. Still working on it,  will hopefully be in Review by the end of next sprint.

Finished and in review.

@brynnz22 are you expecting this review to be completed by Friday?

No. I will move to next sprint

Since @brynnz22 is out today and tomorrow I will move this to the next sprint for review. Who should be reviewing this @brynnz22 ?

Thank you @ssarrafan for moving to the next spring, @corilo is reviewing it. I need to make changes he requested.


Clarify which capacities for which enhanced compute engine can be enabled.

I discovered after much research that enhanced compute engine can not be enabled on A1-A2 Power BI capacities. It does work on A3 and above.

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

ID: 369c84b0-97ef-a750-86cd-5330626c75ac
Version Independent ID: 3af79c25-1e82-ab08-7604-bfaa9ace6128
Content: Use the enhanced compute engine with dataflows - Power BI
Content Source: powerbi-docs/transform-model/service-dataflows-enhanced-compute-engine.md
Service: powerbi
Sub-service: powerbi-service
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Thanks for your investigation @unt1tled and for sharing here. I've added a note so others can benefit, too. Thanks!


[ZEPPELIN-2493] Visualization class should throw an error if an abstract method is not implemented

What is this PR for?
Visualization class should throw an error if an abstract method is not implemented just like SpellBase does.
And I added some comments. In my opinion, though Visualization has a good example, it needs an API documentation page (Spell as well). Visualization class has methods which can be overridden (e.g. refresh, destroy, etc.), but the example doesn't mention them. Therefore, users don't know what and how to implement easily!
What type of PR is it?
Improvement
What is the Jira issue?
ZEPPELIN-2493
How should this be tested?

Inherit Visualization
Don't implement any abstract method
Run getTransformation() and render()
Check they print appropriate errors

Questions:

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

LGTM!

Mostly about documentation. Not necessary to write a new test.
LGTM.

@1ambda Thanks for the review! 😄
I didn't know that you asked me to add a test 😢
Was it added after the editing?
But, since you said it is not necessary, I will just leave this PR 😃
Thanks!

LGTM and merge to master if no further discussions.


bpf: nodeport: trivial cleanups

Two tiny cleanups I've been carrying for a while in a feature branch. Maybe they are helpful to others as well.

/test

/test

The ci-eks fail is https://github.com/cilium/cilium/issues/24774.


About page updates

About page updates

[x]   Kat bio
[x]   Update Mission Statement
[x]   Move Contact Us to header or footer
[x]   Add donate button but comment out until link is provided (PJF)

Completed


chore: mark AREnableNewWorksForYouScreenFeed as not ready for release

Description

We identified some launch-blocking features that should be addressed before release.
cc/ @dariakoko
PR Checklist

[ ] I have tested my changes on iOS and Android.
[ ] I hid my changes behind a feature flag, or they don't need one.
[ ] I have included screenshots or videos, or I have not changed the UI.
[ ] I have added tests, or my changes don't require any.
[ ] I added an app state migration, or my changes do not require one.
[ ] I have documented any follow-up work that this PR will require, or it does not require any.
[ ] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

chore: mark AREnableNewWorksForYouScreenFeed as not ready for release — devon

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Dev changes (chore: mark AREnableNewWorksForYouScreenFeed as not ready for release — devon)

  Generated by :no_entry_sign: dangerJS against 7795fd1bb20ba255a209c5f1ae85f30c1ddd73b6

Closed in favor of a feature revert here.


Connect Azure IoT Edge devices together to create a hierarchy (nested edge)

I tried to configure the downstream device to pull the image from the upstream device, executed "sudo iotedge check --verbose", and found an error（I left all ports open and the downstream device was able to ping the upstream device）

root@child:~# sudo iotedge check --verbose

Configuration checks (aziot-identity-service)
---------------------------------------------
√ keyd configuration is well-formed - OK
√ certd configuration is well-formed - OK
√ tpmd configuration is well-formed - OK
√ identityd configuration is well-formed - OK
√ daemon configurations up-to-date with config.toml - OK
√ identityd config toml file specifies a valid hostname - OK
√ host time is close to reference time - OK
√ preloaded certificates are valid - OK
√ keyd is running - OK
√ certd is running - OK
√ identityd is running - OK
√ read all preloaded certificates from the Certificates Service - OK
√ read all preloaded key pairs from the Keys Service - OK
√ check all EST server URLs utilize HTTPS - OK
√ ensure all preloaded certificates match preloaded private keys with the same ID - OK

Connectivity checks (aziot-identity-service)
--------------------------------------------
√ host can connect to and perform TLS handshake with iothub AMQP port - OK
√ host can connect to and perform TLS handshake with iothub HTTPS / WebSockets port - OK
√ host can connect to and perform TLS handshake with iothub MQTT port - OK

Configuration checks
--------------------
√ aziot-edged configuration is well-formed - OK
√ configuration up-to-date with config.toml - OK
√ container engine is installed and functional - OK
√ configuration has correct parent_hostname - OK
× configuration has correct URIs for daemon mgmt endpoint - Error
    Unable to find image '<IP_ADDRESS>/azureiotedge-diagnostics:1.4.3' locally
    docker: Error response from daemon: error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: "\r\n<title>404 Not Found</title>\r\n\r\n
404 Not Found
\r\n
nginx/1.20.2\r\n\r\n\r\n".
    See 'docker run --help'.
        caused by: Unable to find image '<IP_ADDRESS>/azureiotedge-diagnostics:1.4.3' locally
                   docker: Error response from daemon: error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: "\r\n<title>404 Not Found</title>\r\n\r\n
404 Not Found
\r\n
nginx/1.20.2\r\n\r\n\r\n".
                   See 'docker run --help'.
        caused by: docker returned exit status: 125, stderr = Unable to find image '<IP_ADDRESS>/azureiotedge-diagnostics:1.4.3' locally
                   docker: Error response from daemon: error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: "\r\n<title>404 Not Found</title>\r\n\r\n
404 Not Found
\r\n
nginx/1.20.2\r\n\r\n\r\n".
                   See 'docker run --help'.
× container time is close to host time - Error
    Could not query local time inside container
        caused by: Could not query local time inside container
        caused by: docker returned exit status: 125, stderr = Unable to find image '<IP_ADDRESS>/azureiotedge-diagnostics:1.4.3' locally
                   docker: Error response from daemon: error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: "\r\n<title>404 Not Found</title>\r\n\r\n
404 Not Found
\r\n
nginx/1.20.2\r\n\r\n\r\n".
                   See 'docker run --help'.
‼ DNS server - Warning
    Container engine is not configured with DNS server setting, which may impact connectivity to IoT Hub.
    Please see https://aka.ms/iotedge-prod-checklist-dns for best practices.
    You can ignore this warning if you are setting DNS server per module in the Edge deployment.
        caused by: Container engine is not configured with DNS server setting, which may impact connectivity to IoT Hub.
                   Please see https://aka.ms/iotedge-prod-checklist-dns for best practices.
                   You can ignore this warning if you are setting DNS server per module in the Edge deployment.
        caused by: Could not open container engine config file /etc/docker/daemon.json
        caused by: No such file or directory (os error 2)
‼ production readiness: logs policy - Warning
    Container engine is not configured to rotate module logs which may cause it run out of disk space.
    Please see https://aka.ms/iotedge-prod-checklist-logs for best practices.
    You can ignore this warning if you are setting log policy per module in the Edge deployment.
        caused by: Container engine is not configured to rotate module logs which may cause it run out of disk space.
                   Please see https://aka.ms/iotedge-prod-checklist-logs for best practices.
                   You can ignore this warning if you are setting log policy per module in the Edge deployment.
        caused by: Could not open container engine config file /etc/docker/daemon.json
        caused by: No such file or directory (os error 2)
× production readiness: Edge Agent's storage directory is persisted on the host filesystem - Error
    Could not check current state of edgeAgent container
        caused by: Could not check current state of edgeAgent container
        caused by: docker returned exit status: 1, stderr = Error: No such object: edgeAgent
× production readiness: Edge Hub's storage directory is persisted on the host filesystem - Error
    Could not check current state of edgeHub container
        caused by: Could not check current state of edgeHub container
        caused by: docker returned exit status: 1, stderr = Error: No such object: edgeHub
× Agent image is valid and can be pulled from upstream - Error
    Failed to get edge Agent image
        caused by: Failed to get edge Agent image
        caused by: docker returned exit status: 1, stderr = Error response from daemon: error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: "\r\n<title>404 Not Found</title>\r\n\r\n
404 Not Found
\r\n
nginx/1.20.2\r\n\r\n\r\n"
√ proxy settings are consistent in aziot-edged, aziot-identityd, moby daemon and config.toml - OK

Connectivity checks
-------------------
× container on the default network can connect to upstream AMQP port - Error
    Container on the default network could not connect to <IP_ADDRESS>:5671
        caused by: Container on the default network could not connect to <IP_ADDRESS>:5671
        caused by: docker returned exit status: 125, stderr = Unable to find image '<IP_ADDRESS>/azureiotedge-diagnostics:1.4.3' locally
                   docker: Error response from daemon: error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: "\r\n<title>404 Not Found</title>\r\n\r\n
404 Not Found
\r\n
nginx/1.20.2\r\n\r\n\r\n".
                   See 'docker run --help'.
× container on the default network can connect to upstream HTTPS / WebSockets port - Error
    Container on the default network could not connect to <IP_ADDRESS>:443
        caused by: Container on the default network could not connect to <IP_ADDRESS>:443
        caused by: docker returned exit status: 125, stderr = Unable to find image '<IP_ADDRESS>/azureiotedge-diagnostics:1.4.3' locally
                   docker: Error response from daemon: error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: "\r\n<title>404 Not Found</title>\r\n\r\n
404 Not Found
\r\n
nginx/1.20.2\r\n\r\n\r\n".
                   See 'docker run --help'.
√ container on the default network can connect to upstream MQTT port - OK
    skipping because of not required in this configuration
× container on the IoT Edge module network can connect to upstream AMQP port - Error
    Container on the azure-iot-edge network could not connect to <IP_ADDRESS>:5671
        caused by: Container on the azure-iot-edge network could not connect to <IP_ADDRESS>:5671
        caused by: docker returned exit status: 125, stderr = Unable to find image '<IP_ADDRESS>/azureiotedge-diagnostics:1.4.3' locally
                   docker: Error response from daemon: error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: "\r\n<title>404 Not Found</title>\r\n\r\n
404 Not Found
\r\n
nginx/1.20.2\r\n\r\n\r\n".
                   See 'docker run --help'.
× container on the IoT Edge module network can connect to upstream HTTPS / WebSockets port - Error
    Container on the azure-iot-edge network could not connect to <IP_ADDRESS>:443
        caused by: Container on the azure-iot-edge network could not connect to <IP_ADDRESS>:443
        caused by: docker returned exit status: 125, stderr = Unable to find image '<IP_ADDRESS>/azureiotedge-diagnostics:1.4.3' locally
                   docker: Error response from daemon: error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: "\r\n<title>404 Not Found</title>\r\n\r\n
404 Not Found
\r\n
nginx/1.20.2\r\n\r\n\r\n".
                   See 'docker run --help'.
√ container on the IoT Edge module network can connect to upstream MQTT port - OK
    skipping because of not required in this configuration
23 check(s) succeeded.
2 check(s) raised warnings.
9 check(s) raised errors.
2 check(s) were skipped due to errors from other checks.

config-downstream.toml.txt
config-upstream.toml.txt
There are upstream and downstream IoT Edge profiles。If you still need me to upload files, please contact me. thank you

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

ID: cf391207-5570-8bd5-7093-9ace84259f61
Version Independent ID: 1f885aee-a2bf-2e30-814e-460048ec657b
Content: How to create nested Azure IoT Edge device hierarchies
Content Source: articles/iot-edge/how-to-connect-downstream-iot-edge-device.md
Service: iot-edge
GitHub Login: @PatAltimore
Microsoft Alias: patricka

@Ta-regret
Thanks for your feedback! We will investigate and update as appropriate.

@Ta-regret
Since this channel is for driving improvements towards MS Docs, could you provide the URL of the specific documentation that your feedback is applicable to? That way, we are able to make sure your feedback is addressed by the right team

@Ta-regret
Since this channel is for driving improvements towards MS Docs, could you provide the URL of the specific documentation that your feedback is applicable to? That way, we are able to make sure your feedback is addressed by the right team

@SaibabaBalapur-MSFT Thank you for your reply . The address of the document I refer to is: https://learn.microsoft.com/en-in/azure/iot-edge/how-to-connect-downstream-iot-edge-device?view=iotedge-1.4&tabs=azure-portal
When I configure the downstream Iot edge to enter, “sudo iotedge check --verbose” can succeed.
‘’’
[agent.config]
image: "mcr.microsoft.com/azureiotedge-agent:1.4"
‘’’
But when I configure it like this, it will fail.
‘’’
[agent]
name = "edgeAgent"
type = "docker"
[agent.config]
image: "{Parent FQDN or IP}:443/azureiotedge-agent:1.4"
‘’’

@SaibabaBalapur-MSFT Another very important premise is that due to resource constraints, I can't use cli to create it. I use the azure portal and manual configuration.

I found another problem when I applied the proxy image of the child edge device as follows
[agent]
name = "edgeAgent"
type = "docker"

[agent.config]
image: "{Parent FQDN or IP}:443/azureiotedge-agent:1.4"

I tried to output logs using the command "iotedge system logs" and found the following error：
Dec 29 08:36:27 child aziot-edged[107565]: 2022-12-29T08:36:27Z [INFO] - <-- POST /modules/edgeAgent/prepareupdate?api-version=2022-08-03 {"host": "mgmt.sock:80", "connection": "close", "content-type": "application/json", "content-length": "501"}
Dec 29 08:36:27 child aziot-edged[107565]: 2022-12-29T08:36:27Z [INFO] - Pulling image via tag <IP_ADDRESS>:443/azureiotedge-agent:1.4...
Dec 29 08:36:28 child aziot-edged[107565]: 2022-12-29T08:36:28Z [WARN] - container runtime error
Dec 29 08:36:28 child aziot-edged[107565]: Caused by:
Dec 29 08:36:28 child aziot-edged[107565]:     HTTP 500 Internal Server Error: error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: "\r\n<title>404 Not Found</title>\r\n\r\n
404 Not Found
\r\n
nginx/1.20.2\r\n\r\n\r\n"
Dec 29 08:36:28 child aziot-edged[107565]: 2022-12-29T08:36:28Z [INFO] - --> 500 {"content-type": "application/json"}
Dec 29 08:36:28 child aziot-edged[107565]: 2022-12-29T08:36:28Z [INFO] - <-- POST /modules/edgeAgent/prepareupdate?api-version=2022-08-03 {"host": "mgmt.sock:80", "connection": "close", "content-type": "application/json", "content-length": "501"}
Dec 29 08:36:28 child aziot-edged[107565]: 2022-12-29T08:36:28Z [INFO] - Pulling image via tag <IP_ADDRESS>:443/azureiotedge-agent:1.4...
Dec 29 08:36:28 child aziot-edged[107565]: 2022-12-29T08:36:28Z [WARN] - container runtime error
Dec 29 08:36:28 child aziot-edged[107565]: Caused by:
Dec 29 08:36:28 child aziot-edged[107565]:     HTTP 500 Internal Server Error: error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: "\r\n<title>404 Not Found</title>\r\n\r\n
404 Not Found
\r\n
nginx/1.20.2\r\n\r\n\r\n"
Dec 29 08:36:28 child aziot-edged[107565]: 2022-12-29T08:36:28Z [INFO] - --> 500 {"content-type": "application/json"}

At present, I have been troubled by such problems. I would appreciate it if I could get some help here.

@Ta-regret  As error suggests that, HTTP 500 Internal Server Error: error parsing HTTP 404 response body: invalid character '<' looking for beginning of value:  invalid character is causing the problem. This needs further investigation to find out the root cause.
Please send an email to<EMAIL_ADDRESS>with the below details, we will work closely on this matter.
Thread URL: #
Your Subscription ID:
Email Subject: Attn Ashok Peddakotla
Please let me know once you have done the same
Further Technical help on Microsoft Q&A:
Please feel free to open a new technical thread for further discussion on Microsoft Q&A with service tag #.
please reach out<EMAIL_ADDRESS>with a link to this Issue as well as your subscription ID and we can help get the support ticket opened for this issue.

@Ta-regret As error suggests that, HTTP 500 Internal Server Error: error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: invalid character is causing the problem. This needs further investigation to find out the root cause.
Please file a support request @ https://aka.ms/azsupt? If you do not have access to a support plan, Please send an email to<EMAIL_ADDRESS>with the below details, we will work closely on this matter.
Thread URL: #
Your Subscription ID:
Email Subject: Attn Ashok Peddakotla
Please let me know once you have done the same

Since you are working offline with us, We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


[AuthAgg] Properly handle certs from prev epoch

Close in favor of https://github.com/MystenLabs/sui/pull/5547


Upgrade helm charts too

For this release, it's just a version number change. No difference from the last version in 34.0

No reason except that I was testing it the day before I left for 1.5 weeks and there were no actual changes to the helm charts, just version numbers. :-)
I kept the lower bound just in case there were not actually 35.x helm charts for something.

Thank you, Eric.
FYI @eachristgr, please confirm if we have the new charts with --ignore_availability

Thank you Eric.
The changes where propagated to the cluster. https://github.com/dmwm/rucio-flux/pull/337 should append --ignore-availability to conveyor-preparer.


Add clangtidy fixer

This pull request adds a clangtidy fixer using clang-tidy -fix.
I based the tests on the clang-format tests.
Edit: force-pushed to try and fix the tests.
For some reason, the second test keeps failing with
(2/2) [EXECUTE] (X) Vim(return):E716: Key not present in Dictionary: ale_c_build_dir
      > function ale#fixers#clangtidy#Fix[2]..ale#fixers#clangtidy#GetCommand[2]..ale#c#GetBuildDirectory[8]..ale#Var, line 4

How do I adapt the ale#Set calls based on the filetype? Or should I just duplicate them?

You can create the keys to set like l:language . '_clangtidy_options', with l:language set to 'cpp' or defaulting to 'c'.

Cheers! :beers:


[WIP] build-script-impl: Partial implementation for a "quick" xctoolchain

Building an xctoolchain for use in Xcode is hard. utils/build-toolchain makes it easy, but it's not so great for actively working on swiftc because it always does a clean build and makes copies of the build products. Add support to build-script-impl (hopefully to be exposed in a pretty way elsewhere) for building a fake xctoolchain out of symlinks.
Only swiftc/SourceKit and LLDB are supported right now; someone else can do the work for playgrounds.
To play with this, try these commands with build-script:
  --darwin-toolchain-build-symlink
  --install-destdir=$PWD
  --toolchain-prefix=test.xctoolchain
  --darwin_toolchain_bundle_identifier=org.swift.MASTER
  --darwin-toolchain-display-name "Swift master"

Hey @modocache I finally did it. ;-)
I don't really want to own this. I just want to implement the bottom piece of it so someone else can take it and make it pretty. I don't care what any of it's named either.

I don't love having it in build-script-impl, but it seems wrong to put it in CMake at the moment when it also deals with LLDB. It can't go in a standalone script either because it needs to know where the build products are going to end up.

It's not just the build product directory (build/$BUILD_SUBDIR); there's also an extra level of subdirectory for Xcode builds (including all LLDB builds) based on the build mode. You could use the swift_build_support stuff to parse that out from command-line arguments or a preset, though.

Neat, this can hopefully obsolete a script that I'm using 😃 I have a few more paths that I'm handling that come from llvm/clang:
bin/clang
lib/libclang.dylib
lib/clang
lib/libIndexStore.dylib
include/indexstore ## comes from source directory, not build

Any problem including these as well? I'm happy to add them myself next time I want this functionality.

I was unsure if we wanted to handle those, since we don't include them in the downloadable toolchains. Then again, it's clearly necessary for people working on SourceKit on cross-language-boundary features.

Hmm, I guess we should do our best to match whatever build-toolchain does.  We could add a separate build option that includes the additional products that I need.

Can one of the admins verify this patch?

@jrose-apple Now that we have the ability to have CI build us toolchains, do you think we should keep this around?

Please update the base branch to main by Oct 5th otherwise the pull request will be closed automatically.

How to change the base branch: (Link)
More detail about the branch update: (Link)


[Android]CHIP_ERROR should be handled by Long in Java/Kotlin

-- CHIP_ERROR should be handled by Long in Java since CHIP_ERROR is uint32_t and Java Int cannot hold it up , fix across jni/java/kotlin
fixes: https://github.com/project-chip/connectedhomeip/issues/32560

In Java, due to the lack of native unsigned types, converting from native unsigned numbers often requires using larger signed types to accurately represent the same range of values. However, Kotlin introduces native support for unsigned types, eliminating the need for such workarounds. It's important to ensure that Kotlin's unsigned types are correctly aligned with their native counterparts to maintain data integrity during conversions.


[Style] - Different width Buttons in Home Page

What happened?
Hi, I am a contributor in GSSOC'23
I want to work on Improving styling of these buttons.
problem - buttons are of not equal width.
solution - I will Improve the width and styling.
please assign me this task under label gssoc'23

How can we reproduce this bug?
I will Improve the style and set equal width to both the buttons.
Desktop Information (Optional)
No response
Urgency (Optional)
None

Hi @agamjotsingh18, any issue available which Is not assigned yet, I can work on that. please consider assigning me a issue,
I am a contributor in GSSOC'23


Add flag to treat enums as strongly-typed option sets

This draft adds support for strong-typing of built in enums. In the process, it refactors Option Sets to declare what the backing value type is.
I'll be splitting this up into a Refactor PR and then a Feature PR, since this change wound up a little larger than intended.

✅ No public API change.

✅ No public API change.

✅ No public API change.

✅ No public API change.

✅ No public API change.

✅ No public API change.

✅ No public API change.

✅ No public API change.

✅ No public API change.


Layout is mess up

Do you want to request a feature or report a bug?
BUG
What's the current behavior?
The layout is mess up

My setting
        <BigCalendar
          events={[]}
          startAccessor="startDate"
          endAccessor="endDate"
        />

Like @Jmenache says, you have to import the styles. If you still have a problem, please provide a codesandbox so that we can see what's wrong.

Thank you!

Note: If you're using style-loader and css-loader and you have modules:true enabled on css-loader, make sure to import it as global CSS like such:
import '!style-loader!css-loader!react-big-calendar/lib/css/react-big-calendar.css'.
P.S. big calendar devs adding this to the docs you muppets
https://github.com/intljusticemission/react-big-calendar/issues/234


App version is being reported incorrectly in the title bar

It doesn't update when the file version is incremented.

Fixed with commit 777be86e179136ec705809be1cc7921004b9990c


Link unfurling in Slack not working consistently

Is your feature request related to a problem? Please describe.
Slack unfurls links by default (providing a thumbnail). I have slack-slack bridge and a link was not unfurled in one case (it was in another). The link was not highlighted as a link in the first case.
Describe the solution you'd like
It would be great if it would work consistently.
I don't see it as a major issue though.
Additional context
Original channel:

Forwarded:

Have found the probable root-cause of this behaviour:
https://api.slack.com/docs/message-link-unfurling#classic_unfurling

By default we unfurl all links in any messages posted by users. For messages posted via incoming webhooks, the chat.postMessage API method or chat.postEphemeral, we will unfurl links to media, but not other links.

I'll add the override flags in a PR given that we use the chat.postMessage method.


Fix ExecInPod implementation for antctl check

The function was not returning the contents of stdout / stderr in case of a command error, making troubleshooting impossible.

I have seen another failure in CI for the antctl check installation job. Still not sure why, because the contents of stderr were not being returned in case of error.


[feature request] dumping color file into parsable format

It would be great if we can dump the color file into a text format or something easier to parse so we can analyze the graph.

This would be useful for creating phylogenies based on k-mer sharing between colours using metrics like Jaccard distance.

The right solution to this is to use the Bifrost API.
I have made an attempt here, maybe it is useful to others:
https://github.com/cgroza/bifrost_jaccard

Hi everyone,
@cgroza Thank you for your implementation!
There is now another very simple solution to do this:

Make a FASTA file of each k-mer in the segments of the GFA file. Assuming k=31:

zcat mygraph.gfa.gz | awk 'BEGIN {K=31} {if ($1=="S"){LEN_KM_UNITIG=length($3)-K+1; for (i=1; i<=LEN_KM_UNITIG; i+=1){print ">" $2 "_" i "\n" substr($3,i,K)}}}' > mygraph.kmers.fasta

Every record in the generated FASTA file has the form >x_y where x is the ID of the unitig the k-mer is from in the GFA and y is the position of the k-mer within that unitig in the GFA.

Query the colored graph using the previously generated GFA

Bifrost query -v -t 16 -e 1.0 -g mygraph.gfa.gz -C mygraph.bfg_colors -q mygraph.kmers.fasta -o mygraph.colors

The output file will be mygraph.colors.tsv which is a matrix (k-mers x colors). The intersection of a row (k-mer) and column (color) contains a binary value indicating whether the corresponding k-mer has the corresponding color (1) or not (0).
Given that Bifrost graphs are now fully indexed (.bfi file output alongside the gfa) and are very fast to load in memory, this solution should take no time.


[AuthZ] Consider short circuiting when a handler fails?

@blowdart @divega @lodejard
For our default authorization service implementation, should we short circuiting running any more handlers if any handler fails the context?  Do we care about any side effects of the handlers running?  They won't be able to undo the failure, so Authorize will definitely fail even if they run.

I had suggested this before, I can't remember why there were objections.

@lodejard do you have thoughts on whether it's ok to short-circuit authZ providers after one already rejected the person?

I'd suggest letting them run. We don't know what the user might be trying to do in them, like log denials, or even something simple like setting a breakpoint in their code. It would seem like the their condition wasn't being tripped based on the order the rules were being evaluated.

Ok leaving this behavior unchanged for now


fqdn proxy: fix data race by using separate sessionUDPFactories

PR #25309 introduced a data race by sharing the sessionUDPFactory between the DNS server instances for the different IP families (IPv4 & IPv6). This has been detected by #27979.
This commit fixes the data race by using dedicated instances of the sessionUDPFactory.
In addition the global response UDP connections (IPv4 & IPv6) variables have been replaced with fields in the SessionUDPFactory. This way the connections can already be setup during construction of the factory and the sync.Onces (global vars) can be removed.
Fixes: #28156

/test

/test

/test

/test

Just a minor thing related to an error string, apart from that LGTM!

Thanks, i adapted the error messages


Installing cert manager throws error

Error: namespaces "kube-system" is forbidden: User "system:serviceaccount:kube-system:default" cannot get namespaces in the namespace "kube-system"
I have followed all the instructions up to this point. I have ran them twice and gotten confirmation that they were properly installed.

Are you on GKE? Do you have owner permissions on the cluster?

I do have permissions.   After searching around quite a bit I found that if I do this before it works
'''bash
kubectl create serviceaccount -n kube-system tiller
kubectl create clusterrolebinding tiller-binding
--clusterrole=cluster-admin
--serviceaccount kube-system:tiller
helm init --service-account tiller
kubectl create clusterrolebinding add-on-cluster-admin --clusterrole=cluster-admin --serviceaccount=kube-system:default
helm repo update

so I had to create that extra role binding.  My understanding is weak at this point but this did allow me to go on with the tutorial. You may want to add that to the docs.

Thanks.

No the instructions were not enough in that when it came to install the cert manager I got the permission error. My GKE version is 1.10.9-gke.5

I just tried this on a clean 1.10.6-gke.11 cluster (technically the same as yours since both are 1.10) and it didn't require me to do anything with  --serviceaccount=kube-system:default.
I'll open this issue as others may also run into it, but as far as I can tell, it doesn't warrant a change.

OK. For some reason I had to do that.

I bumped into this same issue on GKE 1.11.5-gke.4. @timuckun solution worked for me.

Don't we have the same steps listed in that comment already in https://github.com/ahmetb/gke-letsencrypt/blob/master/10-install-helm.md ? I don't really understand where the problem comes from (existing helm installations?)


Implement EXTEND_PCR command

CI is trying to fetch the wrong golang apt package:

CI trying to fetch: http://security.ubuntu.com/ubuntu/pool/universe/g/golang-1.20/golang-1.20-go_1.20.3-1ubuntu0.1~20.04_amd64.deb
The one that actually exists: http://security.ubuntu.com/ubuntu/pool/universe/g/golang-1.20/golang-1.20-go_1.20.3-1ubuntu0.1~20.04.1_amd64.deb

(diff is ubuntu 20.04 vs 20.04.1)
This seems like it's maybe an ubuntu bug. Will poke around a bit more


Adapter for dual 27c256? (For IBM 5140)

So I'm a fairly green electronics hobbyist, and I was wondering if it would be easy to make this work on the IBM 5140's dual socket interface, probably with some form of daughter/adapter board.
I found references to the original roms here, and they're listed as 27c256
http://www.minuszerodegrees.net/rom/rom.htm
I haven't confirmed that, but I assume since there's a dumped rom file there, it's probably accurate.
Any thoughts?

A bit more information
This page:
http://ohlandl.ipv7.net/5140/5140.html
Lists the roms as "SMM6326CBK"

Hi,
I'm not that familiar with the 5140 but when I see two ROM it will either
mean:

They used two x 27256 as this was the max size that was cheap enough to
fit the code into - in that case you can just use a single emulator
(utilizing the 64k memory it can emulate) and probably a simple adapter to
get the signals decoded into the right place.
they used two chips because they want to get the 16bit data bus. In that
case, you will need two emulators, to give you the 16bit data bus. They
show up on your computer as serial ports and you can control them
individually, we could even modify the control script to manage two
emulators from a single command or something like that.

Hope that helps
Kris
On Wed, 24 Feb 2021 at 13:19, Prozacgod<EMAIL_ADDRESS>wrote:

So I'm a fairly green electronics hobbyist, and I was wondering if it
would be easy to make this work on the IBM 5140's dual socket interface,
probably with some form of daughter/adapter board.
I found references to the original roms here, and they're listed as 27c256
http://www.minuszerodegrees.net/rom/rom.htm
I haven't confirmed that, but I assume since there's a dumped rom file
there, it's probably accurate.
Any thoughts?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Kris-Sekula/EPROM-EMU-NG/issues/6, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFTKLJBTRKLBJEPBSQOI5XDTAVUM5ANCNFSM4YFISCHQ
.

Oh, that's a good point about the bus size - I just pulled some of the code into a debugger, and it's looking like it's flat data just on 2 rom files, so that's good.
I'm guessing here, but bear with me - if I need to make this "larger eprom" fit the smaller eprom, I need to tie the CS lines from both sockets through an or gate, into the emulators CS line, and the CS line from the eprom higher in address space into the a15 address line on the emulator?
this ... sounds close?
P.S. - Thanks for such a fast reply!

"I'm guessing here, but bear with me - if I need to make this "larger
eprom" fit the smaller eprom, I need to tie the CS lines from both sockets
through an or gate, into the emulators CS line, and the CS line from the
eprom higher in address space into the a15 address line on the emulator?"
spot on! without the schematic diagram to confirm, I would take the exact
same assumption...CS lines from both sockets via an OR gate (you could use
a two diode OR gate approach instead of an actual OR gate) and A15 from one
of the sockets CS signal ... Depending on implementation they might be
controlling the OE and/or the CS in the 27C256...Try to dig out the actual
schematic diagram so we can confirm the best approach.
Kris
On Wed, 24 Feb 2021 at 14:04, Prozacgod<EMAIL_ADDRESS>wrote:

Oh, that's a good point about the bus size - I just pulled some of the
code into a debugger, and it's looking like it's flat data just on 2 rom
files, so that's good.
I'm guessing here, but bear with me - if I need to make this "larger
eprom" fit the smaller eprom, I need to tie the CS lines from both sockets
through an or gate, into the emulators CS line, and the CS line from the
eprom higher in address space into the a15 address line on the emulator?
this ... sounds close?
P.S. - Thanks for such a fast reply!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Kris-Sekula/EPROM-EMU-NG/issues/6#issuecomment-785415333,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFTKLJCV3YWV46DVOLDOOC3TAVZYBANCNFSM4YFISCHQ
.


Add new sendTypingIndicator action dispatcher

Feature Request
Is your feature request related to a problem? Please describe.
No.
Describe the suggestion or request in detail
Today, we have multiple send actions:

sendEvent
sendFiles
sendMessage

But we don't have sendTypingIndicator, we should add one.
But unfortunately, we already used BasicWebChat.props.sendTypingIndicator as a true/false value to indicate if we should send typing indicator to the bot.
We need a better plan to rename it to shouldSendTypingIndicator or find a better way for the action dispatcher.
Describe alternatives you have considered
Additional context
[Enhancement]

Right now, it looks like we are using postActivity to send a typing indicator to the bot. We could add one called postTypingActivity or sendTypingActivity. @corinagum @compulim  thoughts?

I think we settled on using emitTypingIndicator. Reassigning to @compulim since this falls in line with his work on migrating to React Hooks.

addressed in https://github.com/microsoft/BotFramework-WebChat/pull/2364


Pr en us 3209

Added TDP to What's New.

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

File
Status
Preview URL
Details

msteams-platform/apps-in-teams-meetings/create-apps-for-teams-meetings.md
:bulb:Suggestion
View
Details

msteams-platform/bots/design/bots.md
:bulb:Suggestion
View
Details

msteams-platform/bots/how-to/authentication/add-authentication.md
:bulb:Suggestion
View
Details

msteams-platform/build-your-first-app/build-and-run.md
:bulb:Suggestion
View
Details

msteams-platform/build-your-first-app/build-bot.md
:bulb:Suggestion
View
Details

msteams-platform/build-your-first-app/build-channel-tab.md
:bulb:Suggestion
View
Details

msteams-platform/build-your-first-app/build-messaging-extension.md
:bulb:Suggestion
View
Details

msteams-platform/build-your-first-app/build-personal-tab.md
:bulb:Suggestion
View
Details

msteams-platform/concepts/build-and-test/test-data.md
:bulb:Suggestion
View
Details

msteams-platform/concepts/deploy-and-publish/apps-publish-overview.md
:bulb:Suggestion
View
Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/create-partner-center-dev-account.md
:bulb:Suggestion
View
Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md
:bulb:Suggestion
View
Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/submission-checklist.md
:bulb:Suggestion
View
Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/teams-store-validation-guidelines.md
:bulb:Suggestion
View
Details

msteams-platform/concepts/deploy-and-publish/appsource/publish.md
:bulb:Suggestion
View
Details

msteams-platform/concepts/deploy-and-publish/appsource/resolve-submission-issues.md
:bulb:Suggestion
View
Details

msteams-platform/concepts/deploy-and-publish/appsource/submit-your-app.md
:bulb:Suggestion
View
Details

msteams-platform/concepts/device-capabilities/location-capability.md
:bulb:Suggestion
View
Details

msteams-platform/includes/tabs/node-js-yeoman-prereq.md
:bulb:Suggestion
View
Details

msteams-platform/overview.md
:bulb:Suggestion
View
Details

msteams-platform/resources/bot-v3/bots-text-formats.md
:bulb:Suggestion
View
Details

msteams-platform/samples/integrating-web-apps.md
:bulb:Suggestion
View
Details

msteams-platform/tabs/design/tabs-mobile.md
:bulb:Suggestion
View
Details

msteams-platform/tabs/how-to/using-teams-client-sdk.md
:bulb:Suggestion
View
Details

msteams-platform/task-modules-and-cards/cards/Universal-actions-for-adaptive-cards/Overview.md
:bulb:Suggestion
View
Details

msteams-platform/task-modules-and-cards/cards/Universal-actions-for-adaptive-cards/Up-To-Date-Views.md
:bulb:Suggestion
View
Details

msteams-platform/task-modules-and-cards/cards/Universal-actions-for-adaptive-cards/Work-with-Universal-Actions-for-Adaptive-Cards.md
:bulb:Suggestion
View
Details

msteams-platform/task-modules-and-cards/cards/cards-actions.md
:bulb:Suggestion
View
Details

msteams-platform/task-modules-and-cards/cards/cards-format.md
:bulb:Suggestion
View
Details

msteams-platform/task-modules-and-cards/what-are-cards.md
:bulb:Suggestion
View
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/apps-in-teams-meetings/design/designing-apps-in-meetings.md
:white_check_mark:Succeeded
View

msteams-platform/assets/icons/vsc-toolkit.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/.DS_Store
:white_check_mark:Succeeded

msteams-platform/assets/images/adaptive-cards/current-teams-outlook-action-model.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/adaptive-cards/universal-action-model.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/adaptive-cards/universal-bots-catering-bot.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/adaptive-cards/universal-bots-incident-management.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/adaptive-cards/universal-bots-teams-outlook.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/adaptive-cards/universal-bots-up-to-date-views-1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/adaptive-cards/universal-bots-up-to-date-views-2.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/adaptive-cards/universal-bots-up-to-date-views-3.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/adaptive-cards/universal-bots-up-to-date-views.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/authentication/sample-app-demo-bot-configuration.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/Cateringbotstates.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/Newuniversalactionmodel.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/Rolebasedviews.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/TeamsandOutlook.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/contextual-views.png
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.

msteams-platform/apps-in-teams-meetings/create-apps-for-teams-meetings.md

Line 313, Column 346: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/framecontext?view=msteams-client-js-latest&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 321, Column 34: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/overview/msteams-client?view=msteams-client-js-latest&preserve-view=true' will be broken in isolated environments. Replace with a relative link.

msteams-platform/bots/design/bots.md

Line 149, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/luis/artificial-intelligence' will be broken in isolated environments. Replace with a relative link.

msteams-platform/bots/how-to/authentication/add-authentication.md

Line 30, Column 16: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/bot-service/bot-builder-basics?view=azure-bot-service-4.0&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 30, Column 46: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/bot-service/bot-builder-concept-state?view=azure-bot-service-4.0&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 30, Column 83: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/bot-service/bot-builder-concept-dialog?view=azure-bot-service-4.0&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 30, Column 130: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/bot-service/bot-builder-dialog-manage-conversation-flow?view=azure-bot-service-4.0&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 124, Column 142: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/active-directory/azuread-dev/azure-ad-endpoint-comparison' will be broken in isolated environments. Replace with a relative link.

msteams-platform/build-your-first-app/build-and-run.md

Line 182, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/microsoftteams/platform/concepts/build-and-test/prepare-your-o365-tenant' will be broken in isolated environments. Replace with a relative link.

msteams-platform/build-your-first-app/build-bot.md

Line 149, Column 75: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/bot-service/channel-connect-teams?view=azure-bot-service-4.0&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 151, Column 169: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/bot-service/bot-service-channels-reference?view=azure-bot-service-4.0&preserve-view=true' will be broken in isolated environments. Replace with a relative link.

msteams-platform/build-your-first-app/build-channel-tab.md

Line 158, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/?view=msteams-client-js-latest&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 163, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/graph/teams-concept-overview' will be broken in isolated environments. Replace with a relative link.

msteams-platform/build-your-first-app/build-messaging-extension.md

Line 110, Column 92: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/bot-service/channel-connect-teams?view=azure-bot-service-4.0&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 112, Column 169: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/bot-service/bot-service-channels-reference?view=azure-bot-service-4.0&preserve-view=true' will be broken in isolated environments. Replace with a relative link.

msteams-platform/build-your-first-app/build-personal-tab.md

Line 156, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/?view=msteams-client-js-latest&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 158, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/context?view=msteams-client-js-latest&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 162, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/graph/teams-concept-overview' will be broken in isolated environments. Replace with a relative link.

msteams-platform/concepts/build-and-test/test-data.md

Line 27, Column 212: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/microsoftteams/teams-custom-app-policies-and-settings' will be broken in isolated environments. Replace with a relative link.

msteams-platform/concepts/deploy-and-publish/apps-publish-overview.md

Line 23, Column 27: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/MicrosoftTeams/manage-apps?toc=%2Fmicrosoftteams%2Fplatform%2Ftoc.json&bc=%2FMicrosoftTeams%2Fbreadcrumb%2Ftoc.json' will be broken in isolated environments. Replace with a relative link.

msteams-platform/concepts/deploy-and-publish/appsource/prepare/create-partner-center-dev-account.md

Line 10, Column 60: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/office/dev/store/open-a-developer-account' will be broken in isolated environments. Replace with a relative link.

msteams-platform/concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md

Line 17, Column 112: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/legal/marketplace/certification-policies#11404-functionality' will be broken in isolated environments. Replace with a relative link.

msteams-platform/concepts/deploy-and-publish/appsource/prepare/submission-checklist.md

Line 175, Column 25: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/office/dev/store/prepare-localized-solutions' will be broken in isolated environments. Replace with a relative link.
Line 191, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/office/dev/store/add-in-submission-guide' will be broken in isolated environments. Replace with a relative link.

msteams-platform/concepts/deploy-and-publish/appsource/prepare/teams-store-validation-guidelines.md

Line 10, Column 175: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/legal/marketplace/certification-policies' will be broken in isolated environments. Replace with a relative link.
Line 34, Column 277: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/legal/marketplace/certification-policies#10010-inappropriate-content' will be broken in isolated environments. Replace with a relative link.
Line 50, Column 5: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/microsoft-365-app-certification/overview' will be broken in isolated environments. Replace with a relative link.
Line 426, Column 22: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/graph/teams-send-activityfeednotifications' will be broken in isolated environments. Replace with a relative link.

msteams-platform/concepts/deploy-and-publish/appsource/publish.md

Line 27, Column 4: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/office/dev/store/add-in-submission-guide' will be broken in isolated environments. Replace with a relative link.
Line 42, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/office/dev/store/' will be broken in isolated environments. Replace with a relative link.

msteams-platform/concepts/deploy-and-publish/appsource/resolve-submission-issues.md

Line 10, Column 185: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/legal/marketplace/certification-policies' will be broken in isolated environments. Replace with a relative link.
Line 68, Column 164: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/legal/marketplace/certification-policies' will be broken in isolated environments. Replace with a relative link.

msteams-platform/concepts/deploy-and-publish/appsource/submit-your-app.md

Line 14, Column 64: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/office/dev/store/open-a-developer-account' will be broken in isolated environments. Replace with a relative link.
Line 18, Column 34: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/office/dev/store/add-in-submission-guide' will be broken in isolated environments. Replace with a relative link.

msteams-platform/concepts/device-capabilities/location-capability.md

Line 55, Column 54: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/locationprops?view=msteams-client-js-latest&preserve-view=true' will be broken in isolated environments. Replace with a relative link.

msteams-platform/includes/tabs/node-js-yeoman-prereq.md

Line 5, Column 230: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/office/developer-program/microsoft-365-developer-program' will be broken in isolated environments. Replace with a relative link.

msteams-platform/overview.md

Line 77, Column 29: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/graph/teams-concept-overview' will be broken in isolated environments. Replace with a relative link.
Line 155, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/?view=msteams-client-js-latest&preserve-view=true' will be broken in isolated environments. Replace with a relative link.

msteams-platform/resources/bot-v3/bots-text-formats.md

Line 13, Column 26: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/bot-framework/dotnet/bot-builder-dotnet-create-messages#customizing-a-message' will be broken in isolated environments. Replace with a relative link.

msteams-platform/samples/integrating-web-apps.md

Line 55, Column 26: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/MicrosoftTeams/teams-standalone-static-tabs-using-spo-sites' will be broken in isolated environments. Replace with a relative link.
Line 60, Column 42: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/sharepoint/dev/spfx/integrate-with-teams-introduction' will be broken in isolated environments. Replace with a relative link.
Line 72, Column 364: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/graph/teams-concept-overview' will be broken in isolated environments. Replace with a relative link.
Line 108, Column 323: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/graph/teams-proactive-messaging' will be broken in isolated environments. Replace with a relative link.
Line 118, Column 27: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/microsoftteams/sharepoint-onedrive-interact' will be broken in isolated environments. Replace with a relative link.

msteams-platform/tabs/design/tabs-mobile.md

Line 151, Column 216: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/settings?view=msteams-client-js-latest#functions' will be broken in isolated environments. Replace with a relative link.
Line 151, Column 216: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/javascript/api/@microsoft/teams-js/settings?view=msteams-client-js-latest#functions. Otherwise, remove the view parameter.

msteams-platform/tabs/how-to/using-teams-client-sdk.md

Line 38, Column 113: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/microsoftteams?view=msteams-client-js-latest#initialize-any-&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 39, Column 160: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/microsoftteams?view=msteams-client-js-latest#getcontext--context--context-----void-&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 39, Column 341: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/context?view=msteams-client-js-latest&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 40, Column 135: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/microsoftteams.framecontext?view=msteams-client-js-latest&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 40, Column 416: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/microsoftteams?view=msteams-client-js-latest#initializewithframecontext-framecontext--------void--string---&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 41, Column 95: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/microsoftteams.framecontext?view=msteams-client-js-latest&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 41, Column 376: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/microsoftteams?view=msteams-client-js-latest#setframecontext-framecontext-&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 42, Column 168: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/microsoftteams?view=msteams-client-js-latest#registerfullscreenhandler--isfullscreen--boolean-----void-&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 42, Column 369: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/microsoftteams?view=msteams-client-js-latest#registerFullScreenHandler__isFullScreen__boolean_____void_&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 43, Column 159: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/microsoftteams?view=msteams-client-js-latest#registerchangesettingshandler-------void-&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 44, Column 270: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/microsoftteams?view=msteams-client-js-latest#gettabinstances--tabinfo--tabinformation-----void--tabinstanceparameters-&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 44, Column 486: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/tabinformation?view=msteams-client-js-latest&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 45, Column 285: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/microsoftteams?view=msteams-client-js-latest#getmrutabinstances--tabinfo--tabinformation-----void--tabinstanceparameters-&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 45, Column 504: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/tabinformation?view=msteams-client-js-latest&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 45, Column 649: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/tabinstanceparameters?view=msteams-client-js-latest&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 46, Column 217: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/microsoftteams?view=msteams-client-js-latest#sharedeeplink-deeplinkparameters-&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 46, Column 393: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/deeplinkparameters?view=msteams-client-js-latest&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 47, Column 250: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/microsoftteams?view=msteams-client-js-latest#executedeeplink-string---status--boolean--reason---string-----void-&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 48, Column 193: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/microsoftteams?view=msteams-client-js-latest#navigatetotab-tabinstance-&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 48, Column 362: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/tabinstance?view=msteams-client-js-latest&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 54, Column 276: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/authentication?view=msteams-client-js-latest&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 54, Column 418: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/authenticateparameters?view=msteams-client-js-latest&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 55, Column 217: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/authentication?view=msteams-client-js-latest&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 56, Column 210: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/authentication?view=msteams-client-js-latest&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 62, Column 174: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/settings?view=msteams-client-js-latest&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 63, Column 171: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/settings?view=msteams-client-js-latest&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 63, Column 307: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/_settings?view=msteams-client-js-latest&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 64, Column 221: [Suggestion-docs-link-absolute] Absolute link '/https://docs.microsoft.com/en-us/javascript/api/@microsoft/teams-js/settings?view=msteams-client-js-latest' will be broken in isolated environments. Replace with a relative link.
Line 65, Column 244: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/settings?view=msteams-client-js-latest&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 66, Column 240: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/settings?view=msteams-client-js-latest&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 72, Column 264: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/tasks?view=msteams-client-js-latest&preserve-view=true' will be broken in isolated environments. Replace with a relative link.
Line 72, Column 397: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/taskinfo?view=msteams-client-js-latest&preserve-view=true' will be broken in isolated environments. Replace with a relative link.

msteams-platform/task-modules-and-cards/cards/Universal-actions-for-adaptive-cards/Overview.md

Line 89, Column 349: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/adaptive-cards/authoring-cards/universal-action-model' will be broken in isolated environments. Replace with a relative link.

msteams-platform/task-modules-and-cards/cards/Universal-actions-for-adaptive-cards/Up-To-Date-Views.md

Line 20, Column 27: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/microsoftteams/platform/bots/how-to/update-and-delete-bot-messages?tabs=dotnet#update-cards' will be broken in isolated environments. Replace with a relative link.

msteams-platform/task-modules-and-cards/cards/Universal-actions-for-adaptive-cards/Work-with-Universal-Actions-for-Adaptive-Cards.md

Line 50, Column 27: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/adaptive-cards/authoring-cards/universal-action-model#actionexecute' will be broken in isolated environments. Replace with a relative link.
Line 58, Column 27: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/adaptive-cards/authoring-cards/universal-action-model#refresh-mechanism' will be broken in isolated environments. Replace with a relative link.
Line 70, Column 147: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/microsoftteams/platform/bots/how-to/get-teams-context?tabs=dotnet#fetch-the-roster-or-user-profile' will be broken in isolated environments. Replace with a relative link.
Line 83, Column 27: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/adaptive-cards/authoring-cards/universal-action-model#request-format' will be broken in isolated environments. Replace with a relative link.
Line 85, Column 27: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/adaptive-cards/authoring-cards/universal-action-model#response-format' will be broken in isolated environments. Replace with a relative link.
Line 97, Column 27: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/adaptive-cards/authoring-cards/universal-action-model#teams' will be broken in isolated environments. Replace with a relative link.

msteams-platform/task-modules-and-cards/cards/cards-actions.md

Line 226, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/adaptive-cards/authoring-cards/universal-action-model#actionexecute' will be broken in isolated environments. Replace with a relative link.

msteams-platform/task-modules-and-cards/cards/cards-format.md

Line 126, Column 178: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/microsoftteams/platform/bots/how-to/conversations/send-proactive-messages?tabs=dotnet#get-the-user-id-team-id-or-channel-id' will be broken in isolated environments. Replace with a relative link.

msteams-platform/task-modules-and-cards/what-are-cards.md

Line 36, Column 285: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/adaptive-cards/authoring-cards/universal-action-model#actionexecute' will be broken in isolated environments. Replace with a relative link.

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

test PR


Android Version Bump to 10

@thomchop there's a ticket for the About Mattermost scene that should include that info


[MB] Switch from default workers to manually registered workers

Closes #1915

cc @mpoiriert Could you review?

@TomasVotruba Can you inform me when you are done so I don't review commit per commit ;)

I didn't know you'll be here now :D
It's ready now

Good point. I'll provide a test case to verify the worker order.


Update tutorial-discover-physical.md

Hash value for downloaded script seems to be incorrect. I computed has for zip file downloaded from portal as well as MS doc and it came to 277c53620db299f57e3ac5a65569e9720f06190a245476810b36bf651c8b795b.

@Vikram1988

Can you review this PR?

IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@rakeshvarade89 thanks for bringing this to our notice. I checked and realized that the Hash value was correct at all other places in the docs but this one article for physical server discovery tutorial. I will sign off on the change you have proposed as the Hash value you have shared is the right one

#sign-off


nixos/hdaps: automatically enable the hdapsd kernel module

patch by hpoussin via
https://discourse.nixos.org/t/hdapsd-automatically-enable-the-hdapsd-kernel-module/2183
Motivation for this change
Motivation provided by hpoussin:
Without the patch (or with “hdaps” as you suggest), I get
dmesg | grep -i hdaps
[ 15.086633] hdaps: supported laptop not found!
[ 15.086635] hdaps: driver init failed (ret=-19)!
[ 24.204814] audit: type=1130 audit(1551030602.203:74): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=hdapsd@sda comm=“systemd” exe="/nix/store/kinpd6wss80pf2d04jnvvmw25lzkrlbq-systemd-239/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’

With this patch, I get:
dmesg | grep -i hdaps
[ 16.093667] hdaps: LENOVO ThinkPad X220 detected, setting orientation 4
[ 16.093764] hdaps: initial mode latch is 0x05
[ 16.093907] hdaps: setting ec_rate=250, filter_order=2
[ 16.094130] hdaps: device successfully initialized.
[ 16.094192] input: ThinkPad HDAPS joystick emulation as /devices/virtual/input/input6
[ 16.094220] input: ThinkPad HDAPS accelerometer data as /devices/virtual/input/input7
[ 16.094221] hdaps: driver successfully loaded.
[ 24.919059] audit: type=1130 audit(1551029327.917:73): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=hdapsd@sda comm=“systemd” exe="/nix/store/kinpd6wss80pf2d04jnvvmw25lzkrlbq-systemd-239/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’

Joystick and accelerometers are available, and hard disk protection is enabled.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

This pull request has been mentioned on Nix community. There might be relevant details there:
https://discourse.nixos.org/t/hdapsd-automatically-enable-the-hdapsd-kernel-module/2183/4

I think the right solution is to rename the module from hdapsd to hdaps.
This is the expected name by hdapsd:
https://github.com/evgeni/hdapsd/blob/3ca4b1a9150514f8e92190d3b43da5aab1244ef9/src/hdapsd.c#L662
The renaming is purely artificial:
https://github.com/NixOS/nixpkgs/blob/e2474d714c010f31b874e146a3781b6cd1c08207/pkgs/os-specific/linux/tp_smapi/default.nix#L29
installs hdaps.ko as hdapsd.ko.
It could even be a typo.

Thanks for pointing out those details @symphorien. It looks like the module renaming was done by @woffs in https://github.com/NixOS/nixpkgs/pull/28962 to avoid naming collisions.

It looks like the collision is intended:
https://github.com/evgeni/tp_smapi/blob/master/README#L38
mentions that this module is a patched version of the upstream one with improved functionality which is
meant to replace the upstream one.

@symphorien Okay, are you okay with opening a follow-up issue where we address the naming collision issue?

This pull request has been mentioned on Nix community. There might be relevant details there:
https://discourse.nixos.org/t/nixos-19-03-feature-freeze/1950/44


God please i'm making a mess of things just let me update my map

About the PR: some basic fixes and implementation of new things to ovni. Hope this one works
:cl:

add: fixed wiring
add: added solars
add: fixed doors
add: added condimaster and the new chefdrobe
remove: Removed more jank!

I believe Rane's said changelogs pertaining to maps should be kept succinct. They should probably also refer to the specific map, since otherwise this will just show up in the changelog as "Added: fixed wiring." Maybe "tweak: Updated Ovni with solars, CondiMaster, and new ChefDrobe." would be better?

Hmmm, alright, will change it next time i update the map, thank you!

You can edit your changelog entry in the original post here, and it will work just fine. The changelog isn't updated until the branch is fully merged.


[Feature]: Option to change Default mode colors -fan_only color (blue-grey) is too similar to disabled color (disabled)

Is your feature request related to a problem?
Below is an image of 2 climate cards where one entity is off, and the other is using fan only.
At a glance, especially if there are several entities on one card, these are difficult to distringuish, and I think a different colour for fan_only would make sense.

Describe the solution you'd like
I can think of two reasonable solutions:

Change the default color to something more visually different.
Offer users the option to select their own colours for each mode.

Describe alternatives you've considered

Perhaps I've selected a theme that just happens to be a poor combination with this card.
I'm at least a little colourblind, so that could be contributing to my difficulty

Additional context
These cards are so great and I love the work you've been doing.
Thank you for making something awesome.

Yep fan-only color can be changed 🙂
It's already possible de change the colors using themes : https://github.com/piitaya/lovelace-mushroom-themes#build-your-own.
But I agree with you, default color can be better 🙂 What color do you suggest ? Purple ? Yellow ? Teal ?

It's already possible de change the colors using themes : https://github.com/piitaya/lovelace-mushroom-themes#build-your-own.

I wasn't aware of this. Very cool.
The idea of creating my own palette to have available globally is awesome.

default color can be better 🙂 What color do you suggest ? Purple ? Yellow ? Teal ?

By making adjustments to the fan_only colour, it felt necessary to adjust the others to keep them all different, so I've gone a bit beyond to scope of the original question.
My objectively correct (jokes) colour choices would be:

heat_cool -Purple (mixing hot and cold makes purple. Green feels strange, though seems to be widely used)
cool 	  -Blue
heat 	  -Deep-Orange (Red feels like too much here, so I like this decision)
dry 	  -Lime (the current Orange feel too similar to deep-orange)
fan 	  -Teal

All the colors are HA climate colors to avoid confusion with other card. But I agree for the fan color. I will update it to teal by default.


Android: Retrofit2 javax.net.ssl.SSLHandshakeException

What kind of issue is this?
D/OkHttp: <-- HTTP FAILED: javax.net.ssl.SSLHandshakeException: javax.net.ssl.SSLProtocolException: SSL handshake aborted: ssl=0x58a65308: Failure in SSL library, usually a protocol error
09-15 11:30:31.868 1911-2237/com.capitalone.sparkpay D/OkHttp: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version (external/openssl/ssl/s23_clnt.c:741 0x40e5679c:0x00000000)
We have been using Retrofit 1.9 SDK and works perfectly fine on Android devices min OS Version 16 and above. However when I tried updating Retrofit SDK to latest (2.3.0 version), I get javax.net.ssl.SSLHandshakeException on devices running Android 4.x (Jellybean to Kitkat). I've tried both default Okhttp as well latest Okhttp (3.9.0 version) and still same exception. Can you please suggest what's the best solution here? I've been following various threads and one solution is to use SSLSocketFactory with 'private SSLSocketFactory delegate', however it still uses deprecated following method, ideally we would want to use non-deprecated methods (with ssl socket including tsl):
public Builder sslSocketFactory(SSLSocketFactory sslSocketFactory)

[ ] Question. This issue tracker is not the place for questions. If you want to ask how to do
something, or to understand why something isn't working the way you expect it to, use Stack
Overflow. https://stackoverflow.com/questions/tagged/okhttp

[ ] Bug report. If you’ve found a bug, spend the time to write a failing test. Bugs with tests
get fixed. Here’s an example: https://gist.github.com/swankjesse/981fcae102f513eb13ed

[ ] Feature Request. Start by telling us what problem you’re trying to solve. Often a solution
already exists! Don’t send pull requests to implement new features without first getting our
support. Sometimes we leave features out on purpose to keep the project small.

@swankjesse this is open for long time, can you please take a look or assign to right contact/team. Thanks.

Thanks for your question. This issue tracker is only for bug reports with test cases and feature requests. Please ask usage questions on Stack Overflow.
https://stackoverflow.com/questions/tagged/okhttp

What's most likely going on is OkHttp has removed support for obsolete HTTPS configurations and the host you’re trying to reach needs to be updated.
If you don't want to do that you can configure cipher suites and TLS versions in OkHttp to support this obsolete server.
https://github.com/square/okhttp/blob/master/samples/guide/src/main/java/okhttp3/recipes/CustomCipherSuites.java


api: implement debug endpoint that can stream tortoise internal state

implementation details tbd
it is important to make it efficient so that it doesn't block consensus for long time

i will reopen with more details later


Support for VSCode Web

Thank you so much for this extension! I use it everyday and all my shortcuts are stored conveniently in my which-key config. Recently I tried installing it in GitHub Codespaces, and thought it might be nice to have which-key support there too.
Problem
When trying to install this extension on something like GitHub Codespaces (https://github.dev), this error appears:

Solution
I'm not sure why this happens, but my guess is the package needs a "browser" entrypoint in addition to "main" in package.json.

Interestingly, VSpaceCode and WhichKey can works in Codespaces when it has a container attached to it (has terminal access); however, it doesn't work when it is the browser only editor like github.dev.
The learn more link from the screenshot will take me to https://code.visualstudio.com/docs/remote/codespaces#_why-is-an-extension-not-installable-in-the-browser.
After some digging, your are right that we will need additional entry point "browser" as outlined in the Web Extensions guide. I will look into it a little bit more later this week.

Fixed on 3eb1d5e4379e0ac0e98f59e38fc1280019b7864c, and released with v0.9.3.
Opened a tracker https://github.com/VSpaceCode/VSpaceCode/issues/230 for VSpaceCode as well.

This is fantastic - thank you so much!


Setup travis

We need to set up a travis task to run on each PR as happens with other projects.
Related with #27

Done!


Support import convention: Use import statements for packages and modules only, not for individual classes or functions.

There's a style guideline in Google  recommending against direct imports of symbols from a module that would be nice to support in terms of autocompletion capability.
What this would mean is that autocompletion for imports would prefer to import by module as opposed to the class directly, and autocompletions for subclasses, etc. would also use the module.
For example,  typing @dataclass would offer an import suggestion that would autocomplete
import dataclasses

@dataclasses.dataclass

instead of current behavior
from dataclasses import dataclass

@dataclass

For autcompletion in subclasses:

import numbers

class BaseClass(Protocol):
    def my_method(self, number: numbers.Number):
        pass

 class SubClass(BaseClass):
    def my_method

where my_method should autocomplete to my_method(self, number: numbers.Number) instead of currently my_method(self, number: Number)

Hi @BaconPancakes, thanks for the issue. We have moved this issue to discussion as an enhancement request for comments and upvotes. Please upvote the idea if you'd like to see it being supported.
The second example you listed seems like a bug. Pylance is supposed to add import statement when auto-completing my_method. I will look into it.

Closing this one as duplicate of https://github.com/microsoft/pylance-release/issues/4948


Not working with special characters like ===

Hi
I use alternate-toggler with NVIM v0.8.0.
I have added a rule to toggle === to !== the way you have commented here.
This does work for normal characters like in yes and no but not in "special" characters like === or !==.
The reason for that is that <cword> by default does not capture these characters, instead it seems to capture the next valid characters.
							*word*
A word consists of a sequence of letters, digits and underscores, or a
sequence of other non-blank characters, separated with white space (spaces,
tabs, <EOL>).  This can be changed with the 'iskeyword' option.  An empty line
is also considered to be a word.
							*WORD*
A WORD consists of a sequence of non-blank characters, separated with white
space.  An empty line is also considered to be a WORD.

I noticed that my solution has other drawbacks. For example toggling true inside if(something === true) will capture true) and will therefore also not work.
Do you have a better solution?

Hey, thanks for looking into this! I'm not sure there would be an easy way to do it without changeing iskeyword.
Although maybe something that would mitigate issues that modifying iskeyword might have would be:

Copy iskeyword

Thank you for your response! You pointed me at the right direction.
But I found a more suitable solution on stackoverflow. I created a PR that implements this.
It now passed the same text content to the LuaAlternateToggle function as you get with yiw.
This changes the behavior to what it was originally intended without the sideffects of messing with iskeyword.

@schoero I've put some code in a PR inspired by yours that I think should achieve the desired result and I've also made some improvements. Maybe test the branch out before I merge it? I'll likely merge it in in the next 24 hours.
Thanks a ton for putting in the work to figure this out!

I installed your branch fix-special-characters and tested it quickly. It works in all the cases I tested. I also like that it doesn`t change the cursor position anymore 👍.
Another nice thing is that it now works inside quotes, which  I think was not possible before.
I let you know if I notice anything, otherwise it seems good to go.


Improve command line interface

Summary
These changes were implemented following the integration of https://github.com/Slicer/Slicer/pull/7063 contributed by @jhlegarreta. These are intended to streamline the integration of project already using the checker provided by "codespell-project".

By default, search files in current directory
Initialize default list of suffixes
Clarify --dict help string, and support --ignore-words and -I alternative
Add support for excluding files specifying glob patterns
Improve help string associated with the --exclude argument
Add regular Python docstrings

Use in Slicer
mkvirtualenv codespell
python -m pip install git+https://github.com/jcfr/SimpleITKSpellChecking@improve-command-line-interface

Then apply this patch
diff --git a/Utilities/Scripts/runCodespell.sh b/Utilities/Scripts/runCodespell.sh
index 6cfe638836..283606868d 100755
--- a/Utilities/Scripts/runCodespell.sh
+++ b/Utilities/Scripts/runCodespell.sh
@@ -33,4 +33,5 @@ if [[ ! -e ${ignore_words_file} ]]; then
   exit 1
 fi

-codespell -w -q6 --skip="${skip}" -I ${ignore_words_file}
+codespell --skip="${skip}" -I ${ignore_words_file} \
+  --miss --verbose --prefix "vtkSlicer" --prefix "qSlicer" --prefix "vtkITK" --prefix "qMRML" --prefix "vtkMRML"

.. and run the script:
/path/to/Slicer/Utilities/Scripts/runCodespell.sh

cc: @lassoan @jamesobutler

@jamesobutler @jhlegarreta

https://github.com/SimpleITK/SimpleITKSpellChecking/pull/26


Design login/sigup form

@utnapischtim please make sketches on how the form should look like.

login page
login to repository - add an underline or a break line.
signup page
also break line-