Update to Microsoft 365 and Outlook for Windows connectivity

Hello - there was a recent Message Center notification (MC229143) in the M365 Admin Center with the details below.
Wondering if this could be added to this page?

To ensure that we meet performance expectations, we are updating the supported versions of Outlook for Windows that can connect to Microsoft 365 services.
Effective November 1, 2021, the following versions of Outlook for Windows, as part of Office and Microsoft 365 Apps, will not be able to connect with Office 365 and Microsoft 365 services.
Office and Microsoft 365 Apps  |  Outlook   for Windows Version
Office 2013 > 15.0.4970.9999   and older
Office 2016 > 16.0.4599.9999 and older
Microsoft 365 Apps for enterprise (formerly Office 365 ProPlus) > 1705   and older
Microsoft 365 Apps for business (formerly Office   365 Business) > 1705 and older
Versions that are newer than minimum version requirements listed above, but are not the currently supported version, may experience connectivity issues.

Thank you,
TC

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

ID: 51e6edce-5c6a-5792-8a17-ee581414e190
Version Independent ID: a91cd251-f9cb-9c1c-311c-6720c738a063
Content: End of support resources for Office - Deploy Office
Content Source: DeployOffice/endofsupport/resources.md
Service: o365-proplus-itpro
GitHub Login: @DHB-MSFT
Microsoft Alias: danbrown

@tcfinney -- Thanks for the suggestion. We already have plans to add it to this article -- Office versions and connectivity to Office 365 services. We're just following up with the Outlook team about some of the details.

@tcfinney -- Thanks for the suggestion. We already have plans to add it to this article -- Office versions and connectivity to Office 365 services. We're just following up with the Outlook team about some of the details.

Many thanks, @DHB-MSFT!  Any estimate on when it will be published?  Thanks again!

Many thanks, @DHB-MSFT!  Any estimate on when it will be published?  Thanks again!

@tcfinney -- We're hoping to have it added by the end of January, at the latest. Just waiting to hear back from the Outlook team. Thanks.

@tcfinney -- We're hoping to have it added by the end of January, at the latest. Just waiting to hear back from the Outlook team. Thanks.

@tcfinney We've added this information to the article:  https://docs.microsoft.com/deployoffice/endofsupport/office-365-services-connectivity#minimum-version-requirements-for-outlook-for-windows.  Apologies for the delay.


saver.html

Is your feature request related to a problem? Please describe.

Describe the solution you'd like:

Describe alternatives you've considered:

Additional context:

howto recieve user information

Hi there,
could you please explain more what you are trying to do? We're at a loss what you mean.


Experimental support for Stack-22

Hey there,
I noticed that <IP_ADDRESS>.pre.jammy was released sometime ago. I wonder how you feel about releasing a non-pre version of it?
Did you get some feedback about this version? Are there any known issues? Or would you consider it production ready, and can you recommend using it?

Hi 👋🏻
Thanks - I haven't seen any feedback / comments regarding that version - however at the same time I haven't had a chance to test it thoroughly myself.
At this moment I'm not sure how to release this as it's not backward compatible with Heroku 20 or 18 - it's probably going to be a major version bump.
I think it's fine to use this in production as long as you have sufficiently tested your use cases - results from wkhtmltopdf are often heavily depend on how the pages are implemented.

Hey, I just wanted to let you know that we have been using <IP_ADDRESS>.pre.jammy for the last 10 days in production on stack22 on Heroku. No issues at all. Works fine and as expected. Thank you!

Also using <IP_ADDRESS>.pre.jammy in production for a few days and haven't noticed any issues yet.

Hi all - thank you for the responses!
I've pushed a new major version for jammy support:
https://rubygems.org/gems/wkhtmltopdf-heroku/versions/3.0.0.pre.rc0
Changelog: https://github.com/rposborne/wkhtmltopdf-heroku/blob/main-v3/CHANGELOG.md#300prerc0---2023-02-07
It's exactly the same as <IP_ADDRESS>.pre.jammy - just a major version bump. I will make a prod release once I get a chance to test it myself. Thanks again

Do we expect that this will remain compatible with 18/20 or is this 22 only?

I haven't tested them in 18/20 but my impression is it only works in heroku-22 due to the underlying dependency changes.

@pallymore thanks for the heads up, appreciate it!

Gave this a shot in a review app on Heroku-22 and seemed to be working fine and will be using it to upgrade our pipeline

thanks!

from a quick test on our app, <IP_ADDRESS>.pre.jammy is not getting styling or images that were working previously.

Hi - sorry I haven't been checking Github for a while. Sounds like everyone is happy with 3.0.0.pre.rc0 😁 I can publish 3.0.0 later today

Hi all - 3.0.0 is out. thanks!


Command capitalization

When using commands, they are case insensitive. When using the help command, however, you must use exact case for the command you want help on.
Where the prefix is +:
+Ping
(Works)
+Help Ping
(It can't find the command...not that it tells you that. It sends you the entire list of commands, but I digress)
I am proposing that the cmd ArgResolver be changed to allow this.

I and others have complained about that before, but we were rejected 🤷 You're free to change your own help command, however.


Update 24-game.md

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

Hey @iamsandipanbera
Thank you for opening this pull request.
This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Thank you and happy coding.


Add analysis script variant to integrate and weight protonation/tautomer states

We should add a variant of the perses/examples/new-cli/ analysis script that zips up the appropriate protonation/tautomer microstates that have been expanded with state penalties.

We should have the script in examples. Check and close.

Related to https://github.com/choderalab/perses/issues/1136

We have a an example script here, but #1136 will supercede this with a more integrated analysis tool.


Ruby Wrapper

There's a Ruby tutorial but it's pretty low level, having to set up the faye server and listen on callbacks is tedious.

Hey @gmaliar, not sure if still relevant to you, but I'm working on this: https://github.com/ostera/switchboard.rb

@ostera awesome -- I like the API. When it's ready lets get it included in the documentation and close this issue.

There's been more work on this front: https://github.com/ostera/switchboard.rb/blob/master/README.md
Feel free to chip in @gmaliar if you have any ideas or proposals, I'll be adding tests to this in the following weeks but PR's and feedback are always welcomed :smile:


Feature/enhance add identity

Explanation

More Information

Screenshots/Screencaps

Before

After

Manual Testing Steps

Pre-Merge Checklist

[ ] PR template is filled out
[ ] IF this PR fixes a bug, a test that would have caught the bug has been added
[ ] PR is linked to the appropriate GitHub issue
[ ] PR has been added to the appropriate release Milestone

+ If there are functional changes:

[ ] Manual testing complete & passed
[ ] "Extension QA Board" label has been applied

PR template source from github.com/MetaMask

Closed since this PR is moved to this branch: https://github.com/privacy-scaling-explorations/crypt-keeper-extension/tree/feature/convert-mv3


Proposal: Surveillance proof proxy connection with plausible deniability.

I was thinking about implementing a new transport, so that an observer will identify connection it create as valid TLS connection to an well-known site.
This transport consists of two parts, the first one will harvest the certifications from other sites, the content harvested also include offered encryption methods, signatures for key exchange if connection have perfect forward secrecy.
The rest part will integrated with your program, which will utilize content we have harvested. Before key change, both client and server will replay the content is harvested, incuding SNI, preferred encryption method and more if possible.  As for key exchange, for connections without PFS, server will use the pre-shared key as content it decrypted by its server private key as if it own the key. The client will also use the pre-shared key as content it encrypted with server's public key. Both side will compute the session key from client random, server random and pre-shared key. An observer will not be able to notice that server does not actually own the private key for the certificate it provided to client. For connections with FPS, we will send the the DH or ECDH info with harvested signature(both info and signature are harvested), both client and server will ignore the key from DH and use pre-shared key as key exchange result. The computation of session key is similar to that of non-PFS connections. The observer might notice the DH or ECDH info never change or have a limited possibility, but have no way to deduce if server have the private key.
Currently, the use of TLS connection in v2ray is more complicated than an ordinary user can accept, as the issue of valid certificate follows a secure routine which can be hard to follow. The certificate user used is often self-signed which can be easy to detect or block. Even using the certificate from valid CA can raise notice as the observer can discover the user of V2Ray is accessing a uncommon site. In both case, the surveillance system can detect unusual event and could trigger an alert to authority.  With the use of certificate harvested, government might think twice before block our connection.

If I understand correctly, this proposal is similar to tls1.2_ticket_auth in SSR, with more options in domains and encryption keys.
There are 2 concerns with this approach:

The server can't perform a real TLS handshake. It is easily detectable by others, by just asking for a standard TLS handshake.
Performance-wise (speed) it will not be better than a real TLS connection. If a real TLS connection gets blocked, the fake one will also be blocked, and vise-versa.

I didn't considered about active probe. This is a fatal shortcoming of this method.
I believe that the better way to ensure plausible deniability is to implement websocket transport proposed at #83. Which can behave as a ordinary HTTPS server unless client knocked correctly.

This issue will focus on implement a proxy transport with plausible deniability, not the way I have proposed previously.

I don't think it is necessary to be in the transport layer, but you may draft some design first in order to discuss further.

Websocket transport spec:
Configure :
Stream type : Websocket
Websocket settings, located near tls settings :
Listening address(inbound only) : (string) the  path this inbound listening.
Destination url (Outbound only) : (string)  the Websocket uri this Outbound is connecting.
Bind address(inbound only) : the tcp address http listener will listen to.
Since Websocket is almost a drop in replacement for tcp what we need to do is very little.
Once listen is called, it will set itself as the handler of corresponding path, and start http server.
The handler will simply pass the connection to the handler listener specified.
Connection reuse should be implemented as the complete handshake could be as expensive as two tls(one at forwarder, the other one will be v2ray tls) , one Websocket over http and one tcp over Internet combined.
This transportation is designed for user that have a regular website which support tls,  and live in an area that the Internet is being not only surveillance but also regularly examined by experts. User could be disconnected from the Internet if be discovered to use proxy, or face more severe penitentiary.
Currently, the regular vmess connection will be recognized as unknown by surveillance device(at least we wish it to be recognize as unknown).  However if a end user's majority of traffic is unrecognizable, it is very likely to trigger alert if the traffic have been manually reviewed. The most of traffic from a submissive Internet user can be recognized, while a user using v2ray won’t. This could be used to identify to whether a user have used a way to avoid censorship or surveillance.
The user should use balancer(nginx) to forward Websocket traffic to v2ray. The website will show normal content if the url given is not appropriate, and will not be forwarded to v2ray by nginx. This can prevent almost all active probe as it will be very hard to guess the url.
If the network operators detected such a connection it will be impossible for them to know if such a connection is a ordinary https traffic or encapsulated v2ray traffic.

I prefer to do this in HTTP proxy. WebSocket is based on HTTP. Both client and server need to understand HTTP protocol. HTTP proxy is more suitable because it already handles CONNECT. WebSocket is just another a GET request with Upgrade header.
The advantage with a transport is, the transport can carry other format of payload, say socks. However, assuming WebSocket is always used with HTTPS, it doesn't make sense to embed another encrypted format inside.
My plan was to implement the HTTP client proxy after socks client, and then expand it with WebSocket. If you wanna take over the WebSocket part. I can assign the issue to you.

I insist that VMess over Websocket should be implement as transport.
We are not talking about ask V2Ray to relay Websocket connection but asking Websocket to relay a VMess connection.
HTTP proxy and a HTTP server are different.  The typical usage of VMess over Websocket will be forwarding the corresponding to the port Websocket is listening. It is unlikely that anyone make a reverse proxy for a HTTP proxy and most of people will prefer to keep HTTP proxy private.

Websocket is similar to KCP not socks.

What's more, Websocket transport can use  net.http Golang provided and act as a normal HTTP server not HTTP proxy.

Ok. You are talking about a real (or compatible) WebSocket implementation. Yes that is doable in transport layer. You can continue with your proposal.
However, I don't see any benefit from WebSocket as a transport, in terms of speed and obfuscation. V2Ray will not prevent you from implementing it. It just seems not going to have much usage.

I am not implementing WebSocket, just considering to use Websocket as a transport to discourage recognize. The websocket is already available as a official repo.

I am implementing it as a last resort. If a ISP block all unknown traffic and active probe all unsure service, it will be the very transport to use.

I am thinking about integrate meek into this proposing transport along with websocket, which can provide similar functionality and don't conflict with each other.

Tracked by https://trello.com/c/3uCCeBkC/8-add-websocket-transport


Emit error without line number

How do you emit an error which is not tied to a specific line number? For example, "File not found".

There's not currently a way to do this, unfortunately. It would be relatively trivial to change this though: just make the initial offset field optional, and then wrap the error location code in an if let, I'd think.

Does it also mean that it is not possible to generate a report not tied to any source but rather the file itself?
For instance, in my language file names have to be valid identifiers, so I would like to print a ariadne-style error diagnostic if a file name is not that. Is that possible?

That should be possible, yes: just use an offset pointing at the start of the file and don't include any labels.


There is a vulnerability in Apache Avro 1.10.0,upgrade recommended

https://github.com/apache/hudi/blob/8ff17b047091b4b90e6e972d8b43d416714a0613/hudi-flink-datasource/hudi-flink/pom.xml#L218-L224
CVE-2021-43045
Recommended upgrade version：1.11.0

Filed a tracking ticket https://issues.apache.org/jira/browse/HUDI-4248
thanks for reporting.
upgrading apache avro version in general may not be easy.


GitHub: Invite members to ng for product-puris

Who should be invited to Catena-X ng
GitHub Users:

f-zimmer
MercedesG-8020
ReneSchroederLJ
denis8020

Vouching person: Me and @mhellmeier. I guess me requesting this is sufficient.
target team: product-puris

Cheers, invitations have been sent.

Since all 4 have accepted their invitations I will close the ticket.


[GUI] Device details

Just if you have  view permisson you can view details of device.
Actually, If you have modifer and/or view, this option should be able

Now there're 2 wrapper functions over Ability class: CanView and canModify, i.e:
const canView = ability.canView('device');
const canEdit = ability.canModify('device');

Inside canView is been checking viewer and modifier permission.

When the Device Modifier option is selected, the permission associated with this profile is "all_device", that is, the user can create, read, update and delete the devices.
Note: As in creating a device you need the list of templates, this permission is also added.

profile

permissions associated with the profile

permissions associated with the user of this profile

Through the API, a user with this permission (all_device) can read the device data.

So, it makes no sense for me to add the ro_device permission to view the device data. This permission only makes sense for a user who can only view devices.

Test OK.

grupoA: all_devices permission

view template:

view device details:

edit device:

grupoB: ro_device permission

view device details:

Tested in version: 63.1-20190705


MINOR: system test fix for 3 co-located KRaft controllers

This patch adds a sanity-check bounce system test for the case where we have 3 co-located KRaft controllers and fixes the system test code so that this case will pass.  We were not testing this case previously, and it would not pass because the first Kafka node would never be considered started.  We start the Kafka nodes serially, and we decide that a node has successfully started when it logs a particular message.  This message is not logged until the broker has identified the controller (i.e. the leader of the KRaft quorum).  There cannot be a leader in the KRaft case until a majority of the KRaft quorum has started, so with 3 co-located controllers the first node could never be considered "started" by the system test.  This patch skips that log message check when a majority of the controllers have not yet started.  It also sends SIGKILL to any running nodes when a majority of co-located controllers have been stopped -- otherwise they do not shutdown, and we spin for the 60 second timeout.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

LGTM.
The new test works for me with : ./tests/docker/ducker-ak  test tests/kafkatest/sanity_checks/test_bounce.py
I had to make a small fix to our Dockerfile due to python's usual version compatibility mess. PR here: https://github.com/apache/kafka/pull/10995/files
Incidentally, even if you want to use the branch builder instead of Jenkins, you can just choose to run a single test through the web UI. That will be a lot quicker than a full test run.

The idea is that if the controller portion of the combined node is up, it's reasonable to proceed

That's a good idea.  I think the diff above has a problem in that we would emit the message too early for the case where process.roles=broker, but I think the idea in general is sound.
Maybe we emit a different message when there is a controller role and that starts, and we emit the same message we emit now after we start the broker (if any).  So it might look like this (Im typing this free-form, so ignore any typos -- it's just to get the point across):
     raftManager.startup()
     controller.foreach { c =>
        c.startup()
        info(KafkaBroker.CONTROLLER_STARTED_MESSAGE) // something that doesn't match the regex in the system test
     }
     broker.foreach(_.startup())
     AppInfoParser.registerAppInfo(Server.MetricsPrefix, config.brokerId.toString, metrics, time.milliseconds())
     info(KafkaBroker.STARTED_MESSAGE)

And then in the system test code, where we check for the log message, we check for the CONTROLLER_STARTED_MESSAGE when the roles include the controller role -- otherwise we check for the standard message.
WDYT?

Just realized that one potential problem with the log message approach is that the last broker in a 3-broker cluster with 3 co-located controllers dos not shut down cleanly.  The current approach deals with this by sending SIGKILL instead of SIGTERM.  The log message approach doesn't deal with it, so the shutdown in the system test would end up timing out after 60 seconds and then sending SIGKILL later as part of the cleanup (the test would still pass).  Not sure if this adds credence to the current approach?

In case we want to stick with the current solution:
================================================================================
SESSION REPORT (ALL TESTS)
ducktape version: 0.8.1
session_id:       2021-07-07--001
run time:         177 minutes 18.294 seconds
tests run:        878
passed:           669
failed:           12
ignored:          197
================================================================================

Failures are the familiar culprits and unrelated to this change.
https://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/2021-07-07--001.1625698454--rondagostino--minor_systests_colocated_kraft_startup_fix--21f01e440/report.html

That's a good idea. I think the diff above has a problem in that we would emit the message too early for the case where process.roles=broker, but I think the idea in general is sound.

How about something like this?
diff --git a/core/src/main/scala/kafka/server/KafkaRaftServer.scala b/core/src/main/scala/kafka/server/KafkaRaftServer.scala
index 8e77357383..310aed8253 100644
--- a/core/src/main/scala/kafka/server/KafkaRaftServer.scala
+++ b/core/src/main/scala/kafka/server/KafkaRaftServer.scala
@@ -106,10 +106,15 @@ class KafkaRaftServer(
   override def startup(): Unit = {
     Mx4jLoader.maybeLoad()
     raftManager.startup()
-    controller.foreach(_.startup())
-    broker.foreach(_.startup())
+    controller.foreach { controller =>
+      controller.startup()
+      info(KafkaBroker.STARTED_MESSAGE + " controller")
+    }
+    broker.foreach { broker =>
+      broker.startup()
+      info(KafkaBroker.STARTED_MESSAGE + " broker")
+    }
     AppInfoParser.registerAppInfo(Server.MetricsPrefix, config.brokerId.toString, metrics, time.milliseconds())
-    info(KafkaBroker.STARTED_MESSAGE)
   }

   override def shutdown(): Unit = {

Maybe we emit a different message when there is a controller role and that starts, and we emit the same message we emit now after we start the broker (if any). So it might look like this (Im typing this free-form, so ignore any typos -- it's just to get the point across) [...] And then in the system test code, where we check for the log message, we check for the CONTROLLER_STARTED_MESSAGE when the roles include the controller role -- otherwise we check for the standard message.

Hmm, what's the advantage of checking for two different strings?
It seems like if we have the broker emit "Kafka Server started broker" and have the controller emit "Kafka Server started controller" we can check for different messages if we want later, but still have simple code now.

Just realized that one potential problem with the log message approach is that the last broker in a 3-broker cluster with 3 co-located controllers dos not shut down cleanly. The current approach deals with this by sending SIGKILL instead of SIGTERM. The log message approach doesn't deal with it, so the shutdown in the system test would end up timing out after 60 seconds and then sending SIGKILL later as part of the cleanup (the test would still pass). Not sure if this adds credence to the current approach?

I think you do need to special case this and send SIGKILL to the last n / 2 (round down) combined nodes. But at least we can avoid special-casing startup, right?

TL;DR: my preference is to skip the regex check rather than adding a new message and carefully/appropriately grepping for it.

I think you do need to special case this and send SIGKILL to the last n / 2 (round down) combined nodes

Yeah, we have to keep track of the number of co-located controllers that are running in order to send SIGKILL to brokers when there are less than a majority of controllers available.  For completeness, I will note here that co-located controller nodes will always be the lowest-numbered nodes in the cluster given the way the system test code is written (https://github.com/apache/kafka/blob/trunk/tests/kafkatest/services/kafka/kafka.py#L724-L729), and that means those nodes will be started and stopped first given the way ducktape is written.  So upon shutdown of a co-located cluster, once we don't have a majority of controllers, the rest of the nodes will have to be killed.  For example, if we were to have 5 brokers and only 3 co-located nodes, the first 2 nodes will be controllers and can be shutdown normally, but then the last 3 will have to be killed due to lack of quorum (I discovered a minor bug in the current PR, which I am fixing with a small commit, while testing locally for the shutdown of a cluster with 3 co-located controllers out of 5 total nodes).
For starting up nodes, the question becomes whether we wait for a log message or not when starting a broker with less than a majority of co-located controllers running.  It gets a bit tricky because we have to wait for both the controller and the broker to start when starting a node with process.roles=broker,controller would result in a majority, but if we wouldn't have a majority with this node started then we would have to grep for just the controller log message.  Furthermore, any controller-related message must not match the grep that identifies both the broker and controller being started.
Finally, it generally would not be the case that we would start a node with process.roles=broker in the system tests with less than a majority of co-located controllers because of the startup order described above -- typically all co-located controllers are started before anything without a co-located controller starts.   But if we wanted to deal with it accurately in case it were to happen, then we would have to know to skip the regex altogether here.
Assume for a moment that we skip the regex check if the node to be started wouldn't get us to a co-located quorum.  With 3 co-located controllers this means we skip the regex check until we start the second controller node, and at that point and thereafter we wait for the broker to be fully started with the current regex check.  And if there were any problems previously that we didn't catch due to not explicitly checking for a controller-specific startup message (e.g. the first node didn't start properly) then this next controller would not start and the regex would not be satisfied -- and the test would fail.  This isn't ideal -- we would like to have known about the failure when the previous controller did not start properly -- but it seems like a reasonable tradeoff to be able to avoid the messiness of expanding our grep-based paradigm.

https://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/2021-07-14--001.system-test-kafka-branch-builder--1626231208--rondagostino--minor_systests_colocated_kraft_startup_fix--27f60380f/report.html
================================================================================
SESSION REPORT (ALL TESTS)
ducktape version: 0.8.1
session_id:       2021-07-14--001
run time:         169 minutes 1.441 seconds
tests run:        878
passed:           669
failed:           12
ignored:          197
================================================================================

We would expect this to be a bit faster since we start brokers in parallel instead of serially, and  recent run with the same number of workers (https://github.com/apache/kafka/pull/10982#issuecomment-875181066) took 177 minutes, so this is about 5% faster.

Thanks, @rondagostino ! I like the concurrent-start solution a lot better than any of the previous ones we were discussing. LGTM.


Changed Reports to be Offline

Removed mention of accessing CSS files from the internet within the html report as this would cause a delay in loading times.
I originally, created an option for a user to choose the output to be online or offline, but from advice given by @Johann-PLW, I made it offline by default with no option for online version.
Additionally, I copied code from iLEAPP that places files needed for the final report to be in the _elements folder as this tidies the ALEAPP folder, and now only the elements folder is copied to final report folder as opposed to several individual files.

I don't really know how Git works, but after generating the previous pull request, I have added additional features. It would appear these new features have been added to the previous pull request, rather than the need to create a new request. The changes for the new features are as follows:
Identified new way to decode encoded strings found within com.sec.android.app.myfiles OperationHistory.db and com.sec.android.gallery3d local.db. These provide greater insight into user interactions. Have implemented this decoding within script titled gallery3DLog.py and have updated smyfilesOpHistory.
Added another entry to decode dictionary within smyfilesOpHistory.
Added icon_mappings for the MyFiles scripts where there were none.
Updated galleryTrash to use latest version of artefacts introduction. Added this to Gallery3D category, so now shows alongside records for Gallery3D Log results.

Hi @PensiveHike ,
I did not push your PR as there is a bug with the ascending/descending symbol in the column headers.

As I mentioned previously, I am not familiar with Github. Making changes,and then reversing thesegoing back on it to then do further work made the chain messy. Therefore, I cloned Brig's ALEAPP repository again and made the changes on this fresh copy. I have tried to overwrite my repository with this cleaner version and it appears to have worked, but perhaps you can check this?
I found the filter function wasn't working due to css links, so this has been amended.


ReSending request

Hi,
Is there a way to force a re-send ?
Or send  a custom request maybe ?
Thanks a lot, great job

Yes, you can send any custom request from the event handlers. Just use the .NET's WebClient (or any similar) class.
You can also re-send a request, there is a property for it in the event argument: ReRequest


[Doc Improvement][Handling errors in conversation events][2466517]

handling errors in conversation events

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
95
6
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
95
6
link
:white_check_mark:

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

Docs Build status updates of commit 9fb0655:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
92
11
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:bulb:Suggestion
View
Details

msteams-platform/assets/images/error-msg.PNG
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md

Line 1461, Column 133: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL.  Otherwise, remove the view parameter. URL: /azure/bot-service/bot-builder-howto-handle-user-interrupt?view=azure-bot-service-4.0&tabs=csharp

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md

link
:warning:

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

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

File
Status
Preview URL
Details

msteams-platform/assets/images/error-msg.PNG
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
92
11
link
:white_check_mark:

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

Docs Build status updates of commit 09fb268:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/error-msg.PNG
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
95
7
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

msteams-platform/assets/images/error-msg.PNG
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
95
7
link
:white_check_mark:

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

Docs Build status updates of commit 1833e24:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/error-msg.PNG
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
95
6
link
:white_check_mark:

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

Docs Build status updates of commit 2870ba4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/error-msg.PNG
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
95
6
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

msteams-platform/assets/images/error-msg.PNG
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
95
6
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

msteams-platform/assets/images/error-msg.PNG
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
95
6
link
:white_check_mark:

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

Docs Build status updates of commit 80bd2f0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/error-msg.PNG
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
95
6
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

msteams-platform/assets/images/error-msg.PNG
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
95
6
link
:white_check_mark:

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

Docs Build status updates of commit 091fad1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/error-msg.PNG
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
95
6
link
:white_check_mark:

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

Docs Build status updates of commit 9c1415e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/error-msg.PNG
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
95
7
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

msteams-platform/assets/images/error-msg.PNG
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
95
7
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

msteams-platform/assets/images/error-msg.PNG
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
95
7
link
:white_check_mark:

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

Docs Build status updates of commit 152bde6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/error-msg.PNG
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
94
8
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

msteams-platform/assets/images/error-msg.PNG
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
94
8
link
:white_check_mark:

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

Docs Build status updates of commit 5dc3d3e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/error-msg.PNG
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

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

@aosolis Request you to please review and approve this PR.

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
94
8
link
:white_check_mark:

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

Docs Build status updates of commit 561a57d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/error-msg.PNG
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
94
8
link
:white_check_mark:

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

Learn Build status updates of commit a26b8e5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/error-msg.PNG
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
94
8
link
:white_check_mark:

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

Learn Build status updates of commit d2522af:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/error-msg.PNG
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
95
6
link
:white_check_mark:

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

Learn Build status updates of commit 3b52653:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/error-msg.PNG
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
95
6
link
:white_check_mark:

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

Learn Build status updates of commit 64274dc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/error-msg.PNG
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
95
6
link
:white_check_mark:

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

Learn Build status updates of commit eeda17b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/error-msg.PNG
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

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

@aosolis  Request you to please review and approve this PR.

Learn Build status updates of commit f4d2af6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

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

Doc enhancement label removed from this git issue and Wajeed team will look into this git issue.

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
95
7
link
:white_check_mark:

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
95
7
link
:white_check_mark:

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
95
9
link
:white_check_mark:

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
81
79
link
:white_check_mark:

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
81
78
link
:white_check_mark:

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
81
78
link
:white_check_mark:

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
93
10
link
:white_check_mark:

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
92
13
link
:white_check_mark:

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
92
13
link
:white_check_mark:

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
93
13
link
:white_check_mark:

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
93
13
link
:white_check_mark:

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
93
13
link
:white_check_mark:

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
93
13
link
:white_check_mark:

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
92
14
link
:white_check_mark:

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
92
14
link
:white_check_mark:

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
92
14
link
:white_check_mark:

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


Update aws-java-sdk-dynamodb to 1.12.779

About this PR
📦 Updates com.amazonaws:aws-java-sdk-dynamodb from 1.11.1034 to 1.12.779
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.amazonaws", artifactId = "aws-java-sdk-dynamodb" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.amazonaws", artifactId = "aws-java-sdk-dynamodb" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #628.


Appsec unable to register when using tls

When trying to enable AppSec the wait-for-lapi-and-register container fails with the following log entry
level=fatal msg="api client register: api register (http://crowdsec-service.crowdsec:8080/) http 400 Bad Request: API error: http code 400, response: Client sent an HTTP request to an HTTPS server.\n"

I am using the tls configuration:
        tls:
          enabled: true
          bouncer:
            reflector:
              namespaces: ["traefik"]

My AppSec values are:
appsec:
  enable: true
  env:
    - name: COLLECTIONS
      value: "crowdsecurity/appsec-virtual-patching crowdsecurity/appsec-crs crowdsecurity/appsec-generic-rules"
    - name: APPSEC_CONFIGS
      value: "crowdsecurity/appsec-default crowdsecurity/crs"

  strategy:
    type: Recreate

  metrics:
    enable: true
    serviceMonitor:
      enable: true

I did not see any tls-options in the default values.yaml. Probably tls activation is missing for the appsec deployment?

/kind bug

@pfaelzerchen I encountered this as well. It looks like appsec doesn't support TLS / https yet and only offers an Http port. I dropped tls in my implementation and went for auto registration of both the agent and appsec, and a fixed bouncer_key for the Traefik bouncer.
Hope that appsec will support tls in a later phase.

Thanks for the explanation. I'll probably wait for tls support. I like not having to do much key-management (except for the enroll key).


[1.10.2] Cardboard Box deletes inventory of Quark Chests

Using a Mekanism Cardboard Box to pickup Quark chests deletes the entire inventory of the chest and turns the texture of the chest into this when placed, https://i.gyazo.com/a3cbc105aa0967736247c29d74bfed48.png

This is an example of something you should use the Box Blacklist for.  I'm afraid I don't have enough time to add compatibility for all unique mod blocks.


dbeaver: 6.2.3 -> 6.2.4

Motivation for this change
https://dbeaver.io/2019/11/03/dbeaver-6-2-4/
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
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 nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)

/nix/store/abdyh1cf1prqn17ff2agnjpp0zgv1wrq-dbeaver-ce-6.2.3<PHONE_NUMBER>
/nix/store/fwb21q1bvaasphkj5chrr14cj5yjc3gc-dbeaver-ce-6.2.4<PHONE_NUMBER>

[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @

Looks good to me.
Built and tested locally.
Thanks for the PR!


[WIP] deps: update to tokio 0.3

I made these changes in service of removing old Tokio versions from our dep tree.  Until Hyper 0.14 is released I'm not sure whether you'd want to merge them and accept the git dependency on Hyper.

Sorry, very delayed response to this.
I would fundamentally be against depending on a specific commit for Hyper, as I dislike Git-based dependencies.  We leave the overall PR open, though, to track upgrading to Hyper 0.14 in general, once they finally publish 0.14.0.

@hdevalence  Hyper 0.14 was released with tokio 1.0 support. I don't think there were more major changes from 0.3 to 1.0 which would require more code changes here.

@hdevalence  Hyper 0.14 was released with tokio 1.0 support. I don't think there were more major changes from 0.3 to 1.0 which would require more code changes here.

It looks like tokio has been already updated to 1.0, so this can be closed.


Fix handling of missing values

if the values for a condition needing a value cannot be parsed, the condition is now ignored
fixes #20
add handling of a few more simple conditions

Codecov Report

Merging #21 (6ce341a) into main (2f092af) will decrease coverage by 0.12%.
The diff coverage is 94.11%.

@@            Coverage Diff             @@
##             main      #21      +/-   ##
==========================================
- Coverage   87.94%   87.83%   -0.12%
==========================================
  Files          14       14
  Lines        1369     1381      +12
==========================================
+ Hits         1204     1213       +9
- Misses        165      168       +3

Impacted Files
Coverage Δ

dicom_validator/spec_reader/condition.py
97.93% <50.00%> (-2.07%)
:arrow_down:

dicom_validator/spec_reader/condition_parser.py
98.85% <100.00%> (-0.36%)
:arrow_down:

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


asp.net 3.5 run get 500 server error, how get the app detail infos?

@shhsu
i pull microsoft/aspnet:3.5 image , then build aspnetap image like below,
FROM microsoft/aspnet:3.5
RUN mkdir C:\aspnet35
RUN powershell -NoProfile -Command
Import-module IISAdministration;
New-IISSite -Name "ASPNET" -PhysicalPath C:\aspnet35 -BindingInformation "*:8000:"
EXPOSE 8000
ADD containerImageNet35/ /aspnet35
after image build and run.
i navigate asp.net page in browser, will get
500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.
may i get the app detail error messages?
thanks.

Can you try adding this Dockerfile to containerImageNet35
FROM microsoft/aspnet:3.5
ARG site_root=.
ADD ${site_root} /inetpub/wwwroot
build
docker build -t mysite1 .
and then launch
docker run -p=80:80 mysite1
hit the default website

@shhsu
thank for your help.
default website run well.
my i change ${site_root}  to my application folder,
like
FROM microsoft/aspnet:3.5
Next, this Dockerfile creates a directory for your application
RUN mkdir C:\aspnet35
ARG site_root=.

ADD ${site_root} /inetpub/wwwroot
ADD net35/ /inetpub/wwwroot
after run ,
i will get 500 error
There is a problem with the resource you are looking for, and it cannot be displayed.
may i get the app detail error messages?
thanks.

@shhsu
if i put my web.config will cause 500 error.
my web.config is below,

<system.webServer>

</system.webServer>

@shhsu
if my web.config contains
section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"
will cause 500 error.
do you have  any ideas ?

is your ${site_root} relative path?
absolute path would not work in docker file. I would that the files you add to the docker context be in the same folder or sibling to the docker file because the docker would include the entire directory you referred to the build context.

@shhsu
yes.
it will get 500 error, if web.config include configSections session.
should we remove configSections session from web.config ?
my config like web.config.txt.
Web.config.txt
thank for your help.

Not sure what the problem could be.
To find the reason of 500 error, there are a few places you can look

Your applications log file directory
%SystemDrive%\Windows\System32\LogFiles\HTTPERR
%SystemDrive%\Windows\System32\winevt\logs

@shhsu
Thank for your help.
I have a question.
How can i copy container's files to host machine after docker run?
Thanks.

@rainmakerho docker cp should do the trick.

@janvorli
Thank for your help.
I use docker cp , after docker run.
i have problem below,
docker cp f4:C:\inetpub\wwwroot .\mysite1
Error response from daemon: hcsshim::ActivateLayer failed in Win32: The process cannot access the file because it is being used by another process.
(0x20) id=f47aa0b21b9b9a43e3e01c9f82e3ea22c7f7a33998ac9f58544a2671684a2b24 flavour=1

This error looks a little vague. It's hard to tell what the issue is. Do you know which IIS feature is required by your website? You might need to install them in your container.
We have something like this in our docker file for ASP.NET tests. Note that this is for .NET 45 but it might include some feature that you are missing. You can go over these features and see if any of these is what you need
RUN start /w dism /online /enable-feature /featurename:IIS-WebServerRole /featurename:WAS-WindowsActivationService /featurename:WAS-ProcessModel /featurename:NetFx4Extended-ASPNET45 /featurename:WAS-NetFxEnvironment /featurename:WAS-ConfigurationAPI /featurename:IIS-ApplicationDevelopment /featurename:IIS-NetFxExtensibility /featurename:NetFx3 /featurename:IIS-ASPNET /featurename:IIS-ASPNET45 /featurename:IIS-NetFxExtensibility /featurename:IIS-NetFxExtensibility45 /featurename:IIS-DefaultDocument /featurename:IIS-NetFxExtensibility /featurename:IIS-ISAPIExtensions /featurename:IIS-ISAPIFilter /featurename:IIS-RequestFiltering /featurename:IIS-Metabase /featurename:IIS-WMICompatibility /featurename:IIS-LegacyScripts /featurename:IIS-IIS6ManagementCompatibility /featurename:IIS-WebServerManagementTools /featurename:IIS-HttpTracing

@shhsu
ok. Thanks for you help.


:bug: Allow creating archetype without tags

Resolves: https://github.com/konveyor/tackle2-ui/issues/1999

After the fix


Switch to Flat

Pre-submit checklist:

Branch

[ ] Commit sequence broadly makes sense
[ ] Key commits have useful messages
[ ] Relevant tickets are mentioned in commit messages

PR

[ ] Self-reviewed the diff
[ ] Useful pull request description
[ ] Reviewer requested

If you updated any cabal files or added Haskell packages:

[ ] $(nix-build default.nix -A pkgsLocal.updateMaterialized) to update the materialized Nix files
[ ] Update hie-*.yaml files if needed

If you changed any Haskell files:

[ ] $(nix-shell shell.nix --run fix-stylish-haskell) to fix any formatting issues

If you changed any Purescript files:

[ ] $(nix-shell shell.nix --run fix-purty) to fix any formatting issues

Pre-merge checklist:

[ ] Someone approved it
[ ] Commits have useful messages
[ ] Review clarifications made it into the code
[ ] History is moderately tidy; or going to squash-merge

I wanted some quick feedback on this. At the moment there are still some tests failing, so there is a bit more work that needs to be done, but everything compiles and most tests pass.

Switch to flat, surely? :upside_down_face:

(If it's not done I recommend making it a draft PR)

We need to decide if we will keep the CBOR instance. Based on this decision, here is how you should interpret this change.

If we remove CBOR, then we remove all comments.
If we keep CBOR, I will remove all commented code and make sure that everything has both CBOR and Flat instances.

I say keep the CBOR for now.

Okay, let's do this now, we can worry about the fun later.


in_browser_session doesn't work properly when using do

Whenever in_browser_session is used with do (i.e. in_browser_session "some_session" do ... end), functions inside the do block will be executed in the current_session, not the specified session. Furthermore,  a BadFunctionError is always raised in the end.
I believe this is because the functions inside the do block are evaluated before calling in_browser_session and so it receives the result of the do block as its parameter instead of the functions themselves.
An example to illustrate:
iex(1)> use Hound.Helpers
nil
iex(2)> change_session_to("session A") #will be the default session
"b2e814010ed31a312fd850a00b6cf5db"
iex(3)> change_session_to("session B")
"dbadb7ea57cf542985530a6169d50804"
iex(4)> Hound.Helpers.Session.current_session_id #currently in session B
"dbadb7ea57cf542985530a6169d50804"
iex(5)> navigate_to("http://elixir-lang.org")
nil
iex(6)> current_url #session B current url should be "http://elixir-lang.org"
"http://elixir-lang.org/"
iex(7)> in_browser_session "session A" do
...(7)>   navigate_to("http://github.com")
...(7)> end
** (BadFunctionError) expected a function, got: [do: nil]
    (hound) lib/hound/helpers/session.ex:44: Hound.Helpers.Session.in_browser_session/2
iex(7)> change_session_to("session A")
"b2e814010ed31a312fd850a00b6cf5db"
iex(8)> current_url # session A url should be http://github.com but will be data;,
"data:,"
iex(9)> change_session_to("session B")
"dbadb7ea57cf542985530a6169d50804"
iex(10)> current_url # session B url should remain http://elixir-lang.org but will be http://github.com instead
"https://github.com/"

I think the best approach is to make in_browser_session a macro, so the do block isn't evaluated until the session has changed, im willing to work on this and make a PR.
Otherwise, in_broswer_session needs to be used with a function:
in_browser_session "other_session", fn ->
    navigate_to(http:example.com)
end

so the docs should be updated to reflect the proper usage (current example in the docs uses in_browser_session ... do ... end)

@msambarino Thank you for reporting!
As I said in #108,

I have no strong opinion about using a function or do
but to avoid making a breaking change let's keep
the function for now and change the docs to reflect this.


Script for performance testing a new test suite

@ehildenb provided a test suite of 130 proofs here: https://runtimeverification.slack.com/archives/CC360GUTG/p1645750056420389
We should write a script for performance testing it, similar to the KEVM performance test script.

Add instructions on how to run these, and what should happen: optimize performance, output shouldn't change. Move tests to Google Drive so that they can have access to them.

The bug reports have been uploaded to a google drive folder which requires access. I included a simple script that runs all the proofs (without doing individual-level profiling) as well as a README describing the contents and linking to the instructions for setting up the Haskell backend. I am happy to include anything else that is missing or otherwise needed.
Because of how the bug report scripts are formatted, the easiest way to change the kore-exec command itself for profiling is to put a different command with that name first on your path, such as a script containing timeout 30 kore-exec "$@".

I've added the bug reports for KEVM on commit 9855ffbd to the google drive as well.

More tests: https://drive.google.com/file/d/1iu6PoELlApktAKHbR2cGTWZqvsZzSx7Z/view?usp=sharing


Problems with passing arguments to Python object

Revision 0
I'm able to import pyvisa by following along with the documentation but I'm running into errors when trying to build the object:
require 'pycall/import'
include PyCall::Import
pyimport :pyvisa

rm = pyvisa.ResourceManager('/lib64/libiovisa.so')

error output:
<class 'pyvisa.highlevel.ResourceManager'>2020/02/25 11:26:19.424 (py_test.rb:10):
ERROR: PyError : <class 'TypeError'>: list_resources() missing 1 required positional
argument: 'self'

#55  explains that this error is caused by using Python's syntax for instantiation instead of Ruby's.
Revision 1
require 'pycall/import'
include PyCall::Import
pyimport :pyvisa

rm = pyvisa.ResourceManager('/lib64/libiovisa.so').new()

error output:
ERROR: PyError : <class 'TypeError'>: a bytes-like object is required, not 'str'

Now using the Ruby syntax for instantiation seems to work but the argument for sourcing the library fails. I've tried a number of ways to pass the argument using both Python and Ruby syntax and none of them have worked. I'd appreciate any advice on working with Python objects in Ruby.

@mrkn I have some additional information that might be useful. I'm testing the same code shown in rev 1 but now the error message is different. This is almost definitely an issue with my test environment - my ruby script is running inside an open source tool that's sometimes unstable for some reason.
The code (same as rev 1):
require 'pycall/import'
include PyCall::Import
pyimport :pyvisa

rm = pyvisa.ResourceManager('/lib64/libiovisa.so').new()

error output:
ERROR: PyError : <class 'ValueError'>: Could not locate a VISA implementation. Install either
the NI binary or pyvisa-py.

This error message is more relevant than the one shown in my original comment. I'm unsure why the path I'm providing is failing to find the library. I verified that the .so exists at that location and I ran the native Python version just to confirm that pyvisa is able to source the shared object:
>>> import pyvisa
>>> rm = pyvisa.ResourceManager('/lib64/libiovisa.so')
>>> rm.list_resources()
('GPIB0::4::INSTR',)

The "GPIB0::4::INSTR" print out means that it was able to source the library and therefore able to provide the resource listing method. Any idea why the path argument isn't working in Ruby?

If ResourceManager is a class, you must write pyvisa.ResourceManager.new('/lib64/libiovisa.so').
Could you try this form?

@mrkn I have investigated this issue thoroughly and located the cause of these behaviors. Here are the results:
Syntax Option 1
rm = pyvisa.ResourceManager('/lib64/libiovisa.so')
# or
rm = pyvisa.ResourceManager('/lib64/libiovisa.so').new()

Error Output:
ERROR: PyError : <class 'ValueError'>: Could not locate a VISA implementation. Install either
the NI binary or pyvisa-py.

As previously mentioned in my earlier comments and in issue #55, this syntax doesn't work. The string argument passed to ResourceManager() is discarded and only string arguments passed to new() make it to python.
Syntax Option 2
rm = pyvisa.ResourceManager.new('/lib64/libiovisa.so')

Error Output:
ERROR: PyError : <class 'TypeError'>: a bytes-like object is required, not 'str'

This required a fair bit more debugging. This TypeError occurs for any string argument passed from Ruby to any Python 3.x method expecting a string.
Results
This problem turned out to be caused by the way Ruby, Python 2.x, and Python 3.x handle strings, and the way pycall converts strings from Ruby to Python:
/* in pycall.c */
PyObject *
pycall_pystring_from_ruby(VALUE obj)
{
    int is_binary, is_ascii_only;

    if (RB_TYPE_P(obj, T_SYMBOL)) {
        obj = rb_sym_to_s(obj);
    }

    StringValue(obj);

    is_binary = (rb_enc_get_index(obj) == rb_ascii8bit_encindex());
    is_ascii_only = (ENC_CODERANGE_7BIT == rb_enc_str_coderange(obj));

    if (is_binary || (!python_is_unicode_literals && is_ascii_only)) {
        return Py_API(PyString_FromStringAndSize)(RSTRING_PTR(obj), RSTRING_LEN(obj));
    }
    return Py_API(PyUnicode_DecodeUTF8)(RSTRING_PTR(obj), RSTRING_LEN(obj), NULL);
}

To understand this problem we need to understand how text is handled:

Ruby string literals are ASCII-8BIT
Python 2.x string literals are ASCII-7BIT
Python 3.x string literals are Unicode code points and encoding defaults to UTF-8

With this in mind, it follows that pycall_pystring_from_ruby() will enter into the conditional return statement when normal Ruby string literals are used because is_binary will be true since Ruby string literals are ASCII-8BIT. The problem arises when PyString_FromStringAndSize is invoked. This is a python 2.x method and is aliased in Python 3.x to return a bytes-like object, not the Python 3.x concept of a string. When Python 3.x tries to operate on this bytes-like object with a string method (Unicode code points), it fails because there is no automatic coercion.
Workaround
The workaround for this is actually quite simple:
rm = pyvisa.ResourceManager.new('/lib64/libiovisa.so'.encode("utf-8"))

By converting the string argument to UTF-8 encoding (instead of the default ASCII-8BIT) before passing the argument, pycall_pystring_from_ruby() reaches the return statement with PyUnicode_DecodeUTF8 which cleanly decodes to Python 3.x's idea of a string, Unicode code points.
Solution
To resolve this issue permanently, pycall_pystring_from_ruby() should be more explicit about Python version checking (using python_is_unicode_literals) in all cases and ensure that the proper decoding methods are used. I'd be happy to work on a pull request if you think it's appropriate.


Adding GitHub Action Tests

WIP As I am still figuring out how some of the testing works, but this at least has python, molecule, and ansible installing on the latest ubuntu.

Closed and re-opened to debug GH Actions not running

/lgtm

/lgtm


[2.0.0] Fix to #9202 - Query: Exception when using Include on collection navigation for models also containing owned types

Problem was that when processing include collection we clone the query model, which changes references of the individual query sources inside. In case of owned types we rely on the references to determine which entity type corresponds with a given query source (using a dictionary).
However, after cloning we were not populating the dictionary with the additional entries, so the owned types corresponding to those clones query sources could not be found.
Fix is to populate the QuerySourceEntityTypeMapping with entries for the cloned query sources - like we do in other places.

Justification:
Impact: High - it affects all queries that perform include on collection navigation, when the query model also contains a query source pointing to an owned type, especially now that owned types are included automatically.
Risk: Very low - fix is a one-liner, adding missing entries to the dictionary that we used to determine which type corresponds with which query source. We do this already in other places (e.g.SubQueryMemberPushDownExpressionVisitor)

Looks good to me but I would like at least one of @smitpatel or @anpete to review as well.
Sent bang email to @Eilon and @DamianEdwards to get 2.0 approval.

@maumar This is approved for 2.0. Please make sure the fix gets into both branches.


2705 - logging unused request fields during serialization for JsonCallParameter class

PR description

used the @JsonAnySetter marker annotation to catch unused request fields and log their values and class type for JsonCallParameter.java domain class.

Fixed Issue(s)

fix for #2705
Changelog

[x] I thought about the changelog and included a changelog update if required.

@SivaTharun it was just missing keyword final on the parameters to the method you added. I've fixed it up and pushed a new PR - your commits are included over there. https://github.com/hyperledger/besu/pull/2993