allow custom cache control settings for requests

Currently, the publisher server only allows for three options when setting cache-control settings: extended (one year), never (no-store), and null, which skips setting the cache-control header.
At the same time, the implementation for serving local content prevents mutation of the backend response after receiving it (e.g., to add a custom cache-control header based on a path), as the act of catching the response to modify it strips the original Response headers. This is contrary to the documentation[1] which indicates the headers can be mutated in this fashion. (i.e., by passing beresp.body through pipeThrough) with a transform stream. From my testing, it's not possible to mutate the headers along with (or without) the content.
This change modifies the serveRequest method to add an optional cache parameter which allows the user to set a custom cache-control string. Although there are other ways to solve this (such as allowing serveRequest to accept arbitrary headers which will be appended/merged, or figuring out if the broken example is the result of a bug or old documentation), this method solves my current needs.
[1] https://www.fastly.com/documentation/guides/compute/javascript/#parsing-and-transforming-responses

looking at this again, I think the 'right' thing to do is accept a CacheOveride like the js-runtime does. will look at that in the morning


Improving SARIF with HelpUri, full description, specific rule name

[x] You've read the Contributor Guide and Code of Conduct.
[ ] You've included unit or integration tests for your change, where applicable.
[ ] You've included inline docs for your change, where applicable.
[ ] There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.

PR Title
Summary of the changes (Less than 80 chars)
PR Description
Detail 1
Detail 2
Addresses #bugnumber (in this specific format)

This looks like a great change! Thanks for improving the experience here :)

Sure, no problem.
Just moved to ready to review.
Once we merge this, we can focus on the next "type".


OP: enable Resize/Prelu/Sigmoid, modified Reshape

Hi @jackwish ,
The main contributions in this PR are listed below:

Enable three new operators: Resize, Prelu, Sigmoid(seems that Sigmoid has been developed in another pull request, sorry for this redundant work..)
Modified Reshape to adapt cases with one attribute
Produce test models for three new operators (seems the model files are list in the .gitignore, so I excluded them from this PR )

Thanks for your awesome code review in advance :)

Hi @erizmr thanks for your contribution! It seems you forget to include the TFLite model file of resize_bilinear in this PR :)

For adding TFLite model files, you may need to use git add -f {file} as *.tflite is ignored by default.

Thanks! Have uploaded the missing models.

Hi @jackwish , thanks for your review! Please check again.


"RequirementParseError" On doing pip upgrade

Error

/usr/bin/pip run on Wed Aug  3 04:36:30 2016
Exception:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/pip/basecommand.py", line 122, in main
status = self.run(options, args)
File "/usr/lib/python2.7/dist-packages/pip/commands/install.py", line 283, in run
InstallRequirement.from_line(name, None))
File "/usr/lib/python2.7/dist-packages/pip/req.py", line 173, in from_line
return cls(req, comes_from, url=url, prereleases=prereleases)
File "/usr/lib/python2.7/dist-packages/pip/req.py", line 71, in init
req = pkg_resources.Requirement.parse(req)
File "/home/dibyendu/.local/lib/python2.7/site-packages/pkg_resources/init.py", line 2863, in parse
req, = parse_requirements(s)
File "/home/dibyendu/.local/lib/python2.7/site-packages/pkg_resources/init.py", line 2811, in parse_requirements
yield Requirement(line)
File "/home/dibyendu/.local/lib/python2.7/site-packages/pkg_resources/init.py", line 2820, in init
raise RequirementParseError(str(e))
RequirementParseError: Invalid requirement, parse error at "'\xe2\x80\x94upgra'"
Steps to Reproduce
pip install —upgrade -r requirements.txt
Other Information
OS: Ubuntu 15.04
Git Commit: bdf2e7d9cc0b2fa5fb04bb9dc4f9f09f967cd9ea
Python Version: Python 2.7.9

Try to run dos2unix on your file.  This looks like a formatting error, tbqh.


CipherSuitesPolicy for Kestrel cipher suite filter

Fixes #15095

Is it ok to go with ConfigureKestrel over UseKestrel here?
While here, let me fix up something that's been bugging me for a while ... no need to show extra code around webBuilder in these examples. The overall layout of the CreateHostBuilder method is covered at the top of the doc.

@Tratcher Double-check the updates. I put the lambda example in here, too. It's all down at the bottom of the diff ... scroll to the end.

@Tratcher Ready for :eyes:.


[GROUP] Comcast

Comcast

[X] The group has more than 20 brands.
[ ] There is a website listing all the brands, with respective name and logo.

Website: N/A
Wikipedia page: https://wikiless.org/wiki/List_of_assets_owned_by_Comcast?lang=en
https://www.sec.gov/Archives/edgar/data/902739/000119312511139191/dex21.htm
https://wikiless.org/wiki/List_of_assets_owned_by_NBCUniversal?lang=en
As for Sky Group Limited, which is the third biggest child company, I could only ever find list of subsidiaries at the bottom of the "list of assets owned by Comcast"
The list is so astronomical to the point where it has multiple Wikipedia pages.

Thanks for the suggestion, I'll have a look at it.


UX: "Code for 64-bit Windows is now available"

This always comes back, no matter how many times I dismiss it:

I click to learn more, as it requests:

Ok, uninstalling one thing and then installing another is kind of only a loose interpretation of "upgrading", but maybe I'm nitpicking. Crossing my fingers that uninstalling won't remove my settings...

Ok, now I'm feeling really uncertain. Windows says related info will be removed. Aren't my settings "related info"? If your page says my settings will be preserved, why does Windows claim otherwise?
At this point I'm bailing because I'm too busy to mess around with possibility of losing my settings. My suggestion is that the wording could be improved, and/or the installer could be improved so as to automate the process of uninstalling one and installing the other. The fact that one is 32 bit and the other is 64 bit... should this matter if one process is simply launching another process when it is done?

It should keep your settings.
If you aren't sure yourself, you can always open settings.json  select all and copy into a notepad or smth, then uninstall, then reopen settings.json and paste it in
Regardless of which version, 32 bit or 64 bit, your extensions will keep since they both use the .vscode folder in your user directory.

Classic Desktop Apps like Code manage their data by themselves, they can put anything anywhere, so what is deleted when uninstalling is decided by the app itself.
But Universal Windows Apps have their data managed by Windows, so uninstalling will delete all data as well.
Most new Windows settings are designed mainly for Universal Windows Apps, they just are "compatible" with Classic Desktop Apps.
So maybe you can report this inaccuracy wording in the Feedback Hub app and let Windows team fix it.

Yes, it should keep your settings. Thanks @beastdestroyer and @yume-chan for the details


adding terragrunt-read-config after hook

#1020

Looks like the build failed with:
--- FAIL: TestTerragruntBeforeAndAfterHook (8.34s)
    integration_test.go:2269: Copying fixture-hooks/before-and-after to /tmp/terragrunt-test615422508
    integration_test.go:358:
        	Error Trace:	integration_test.go:358
        	Error:      	Not equal:
        	            	expected: 1
        	            	actual  : 2
        	Test:       	TestTerragruntBeforeAndAfterHook
        	Messages:   	Hooks on terragrunt-read-config command executed more than once

I fixed the test

@yorinasub17 Could you help rerun the ci please?

Thanks for adding that comment! Since the last build passed, I'm going to go ahead and merge + release this. Thanks for your contribution!

https://github.com/gruntwork-io/terragrunt/releases/tag/v0.21.12
Binaries will show up shortly (~10 mins).


MrKnow URL resolver update failed

Please follow the guide below / Podążaj za przewodnikiem

Put an "x" into all boxes [ ] relevant to your issue (Wstaw "x" w każde pole [ ], które dotyczy twojego zgłoszenia)
Use Preview tab to see how your issue will actually look like (Użyj Perview aby sprawdzić, czy wszystko wygląda dobrze)

Kodi & OS

Kodi verison: x_
OS version: _____

Addon / Wtyczka

[ ] Filmy online - Mrknow
[ ] MrknowTV
[ x] Specto
[ ] FanFILM
Version / Wersja: _____

Issue / Zgłoszenie

[ ] Bug report / Błąd
[ ] Site request / Prośba o nową stronę
[ ] Feature request / Prośba o nową funkcję
[ ] Question / Pytanie
[x ] Other / Inne

Descryption / Opis
Put here every imported thing such logs, how to reproduce etc.
Wstaw tutaj każdą ważna rzecz, taką jak logi, jak wywołać błąd itp.
Just letting you know that I was watching when this latest URL resolver update came though, it failed. It appears to have had some serious effects as well. Programs I watch such as How the Universe Works (a semi popular show) now only displays a few links, all of which don't work. And much.more popular shows such as The Simpsons now display maybe ten links as opposed to the usual dozens of links. They all seem to be HQ links, with no MQ or LQ links to choose from. So I think we may have a problem here.

I'm surprised no one else has mentioned this yet. Hope it's not just me. I'm having to watch a large portion of my TV viewing (all except the newest, most popular shows) on Exodus. I just don't get links or links that work for anything other than the newest, most popular shows, and I don't get many links for those even. I wouldn't know how to rectify a MrKnow url resolver issue. Hope you can help. I know it's not even been 24 hours since I posted this, so I'm not trying to rush anything, just thought I would give an update.

I'm having the same problem. He said that he would fix it 4 months ago. Smh. How do I uninstall all of his mess since he can't fix it??

Really eh? That blows. Mine was fine til a few days ago, but it's bad. I
really can't watch most of what I used to watch on Specto.
On Feb 13, 2017 3:20 AM, "mslavishlyfe"<EMAIL_ADDRESS>wrote:

I'm having the same problem. He said that he would fix it 4 months ago.
Smh. How do I uninstall all of his mess since he can't fix it??
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mrknow/filmkodi/issues/758#issuecomment-279320899,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUPc7NlV-V3en85XEVuRWD_xirLEY2REks5rcBI8gaJpZM4L9SBQ
.

MrKnow, is there anything you can tell me about this? Is it likely to fix itself with next update? Or will I have to delete everything and start over? I would really like to fix this so I can keep my viewing within Specto where all my favorites are.

MrKnow I'm pleading with you, please, please give me some guidance on this issue. As things currently stand, Specto is lost to me. Almost completely useless. I don't want to go elsewhere, this is my favorite, and in my opinion, THE best add-on there is when it's working. I'm not very computer savvy and I don't have a clue what steps to take to rectify this url resolver issue.

Hi MrKnow. Hope you're well. Let me start by saying, I know you're busy. You have lots of issues to deal with in respect to Specto, and no doubt a life outside of Specto also demanding your time. That said, I'm going to respectfully ask again, if you could provide me with some information on what a person can do to fix a broken MrKnow url resolver? Right now Specto is not much use to me, and that's extremely disappointing. I LOVE SPECTO. If you can't fix it, could you suggest anything I could do?
1 - will sitting tight and waiting for another url resolver update work?
2 - When is the next url resolver update rolling out? I don't want to start uninstalling things until Specto has had the opportunity to fix itself with an update.
3 - If I have to uninstall, would I have to uninstall the repository as well?
4 - Is there anything else, anything at all that you can inform me of that might help me resolve this?
I know my last issue about the changelog was kind of trivial, and I was really just offering my opinion, and I will refrain from posting such issues in the future, but this one is a big, serious issue for me and I really need your help.
Thanking you in advance for this and thanks again for all your past efforts...
BankruptEd

Hi,
I'm just wondering,
Why is the URLresolver of yours is not working? I just updated mine and all seems to work fine.
Can you share what machine configuration are you on. May be I can help you a bit.
Sent from my iPhone

On 17 Feb 2017, at 22:20, BankruptEd<EMAIL_ADDRESS>wrote:
Hi MrKnow. Hope you're well. Let me start by saying, I know you're busy. You have lots of issues to deal with in respect to Specto, and no doubt a life outside of Specto also demanding your time. That said, I'm going to respectfully ask again, if you could provide me with some information on what a person can do to fix a broken MrKnow url resolver? Right now Specto is not much use to me, and that's extremely disappointing. I LOVE SPECTO. If you can't fix it, could you suggest anything I could do?
1 - will sitting tight and waiting for another url resolver update work?
2 - When is the next url resolver update rolling out? I don't want to start uninstalling things until Specto has had the opportunity to fix itself with an update.
3 - If I have to uninstall, would I have to uninstall the repository as well?
4 - Is there anything else, anything at all that you can inform me of that might help me resolve this?
I know my last issue about the changelog was kind of trivial, and I was really just offering my opinion, and I will refrain from posting such issues in the future, but this one is a big, serious issue for me and I really need your help.
Thanking you in advance for this and thanks again for all your past efforts...
BankruptEd
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I run and inl3d ultra android box. I would have to check the version (not
at home right now) using the latest Kodi, the latest Specto. I was actually
in Specto when the update came through, and it simply said MrKnow url
resolver update failed. Ever since then, it can't find any sources for a
whole multitude of shows. And only seems to find HD and HQ sources when it
does find some. And this only seems to pertain to the newest, most popular
shows. So I just don't have a clue what I should do.
On Feb 17, 2017 6:00 PM, "Azrin Aris"<EMAIL_ADDRESS>wrote:

Hi,
I'm just wondering,
Why is the URLresolver of yours is not working? I just updated mine and
all seems to work fine.
Can you share what machine configuration are you on. May be I can help you
a bit.
Sent from my iPhone

On 17 Feb 2017, at 22:20, BankruptEd<EMAIL_ADDRESS>wrote:
Hi MrKnow. Hope you're well. Let me start by saying, I know you're busy.
You have lots of issues to deal with in respect to Specto, and no doubt a
life outside of Specto also demanding your time. That said, I'm going to
respectfully ask again, if you could provide me with some information on
what a person can do to fix a broken MrKnow url resolver? Right now Specto
is not much use to me, and that's extremely disappointing. I LOVE SPECTO.
If you can't fix it, could you suggest anything I could do?
1 - will sitting tight and waiting for another url resolver update work?
2 - When is the next url resolver update rolling out? I don't want to
start uninstalling things until Specto has had the opportunity to fix
itself with an update.
3 - If I have to uninstall, would I have to uninstall the repository as
well?
4 - Is there anything else, anything at all that you can inform me of
that might help me resolve this?
I know my last issue about the changelog was kind of trivial, and I was
really just offering my opinion, and I will refrain from posting such
issues in the future, but this one is a big, serious issue for me and I
really need your help.
Thanking you in advance for this and thanks again for all your past
efforts...
BankruptEd
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mrknow/filmkodi/issues/758#issuecomment-280789968,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUPc7F-pCm5UFjv-RUnDCCysrTIcbVIwks5rdiaHgaJpZM4L9SBQ
.

Any particular movies or shows that I can help to test?
Sent from my iPhone

On 18 Feb 2017, at 09:26, BankruptEd<EMAIL_ADDRESS>wrote:
I run and inl3d ultra android box. I would have to check the version (not
at home right now) using the latest Kodi, the latest Specto. I was actually
in Specto when the update came through, and it simply said MrKnow url
resolver update failed. Ever since then, it can't find any sources for a
whole multitude of shows. And only seems to find HD and HQ sources when it
does find some. And this only seems to pertain to the newest, most popular
shows. So I just don't have a clue what I should do.
On Feb 17, 2017 6:00 PM, "Azrin Aris"<EMAIL_ADDRESS>wrote:

Hi,
I'm just wondering,
Why is the URLresolver of yours is not working? I just updated mine and
all seems to work fine.
Can you share what machine configuration are you on. May be I can help you
a bit.
Sent from my iPhone

On 17 Feb 2017, at 22:20, BankruptEd<EMAIL_ADDRESS>wrote:
Hi MrKnow. Hope you're well. Let me start by saying, I know you're busy.
You have lots of issues to deal with in respect to Specto, and no doubt a
life outside of Specto also demanding your time. That said, I'm going to
respectfully ask again, if you could provide me with some information on
what a person can do to fix a broken MrKnow url resolver? Right now Specto
is not much use to me, and that's extremely disappointing. I LOVE SPECTO.
If you can't fix it, could you suggest anything I could do?
1 - will sitting tight and waiting for another url resolver update work?
2 - When is the next url resolver update rolling out? I don't want to
start uninstalling things until Specto has had the opportunity to fix
itself with an update.
3 - If I have to uninstall, would I have to uninstall the repository as
well?
4 - Is there anything else, anything at all that you can inform me of
that might help me resolve this?
I know my last issue about the changelog was kind of trivial, and I was
really just offering my opinion, and I will refrain from posting such
issues in the future, but this one is a big, serious issue for me and I
really need your help.
Thanking you in advance for this and thanks again for all your past
efforts...
BankruptEd
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mrknow/filmkodi/issues/758#issuecomment-280789968,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUPc7F-pCm5UFjv-RUnDCCysrTIcbVIwks5rdiaHgaJpZM4L9SBQ
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Well off the top of my head, "how the universe works" and "autopsy" are two
of them. These are shows that I was working my way through the seasons on
Specto, but for which I now get no sources at all. On the other end of
things, The Simpsons is a show that like with most people, I used to get
oodles of sources, in the hundreds sometimes. Now I might get 15. So that
is a good example of what's going on.
On Feb 17, 2017 11:36 PM, "Azrin Aris"<EMAIL_ADDRESS>wrote:

Any particular movies or shows that I can help to test?
Sent from my iPhone

On 18 Feb 2017, at 09:26, BankruptEd<EMAIL_ADDRESS>wrote:
I run and inl3d ultra android box. I would have to check the version (not
at home right now) using the latest Kodi, the latest Specto. I was
actually
in Specto when the update came through, and it simply said MrKnow url
resolver update failed. Ever since then, it can't find any sources for a
whole multitude of shows. And only seems to find HD and HQ sources when
it
does find some. And this only seems to pertain to the newest, most
popular
shows. So I just don't have a clue what I should do.
On Feb 17, 2017 6:00 PM, "Azrin Aris"<EMAIL_ADDRESS>wrote:

Hi,
I'm just wondering,
Why is the URLresolver of yours is not working? I just updated mine and
all seems to work fine.
Can you share what machine configuration are you on. May be I can help
you
a bit.
Sent from my iPhone

On 17 Feb 2017, at 22:20, BankruptEd<EMAIL_ADDRESS>wrote:
Hi MrKnow. Hope you're well. Let me start by saying, I know you're
busy.
You have lots of issues to deal with in respect to Specto, and no
doubt a
life outside of Specto also demanding your time. That said, I'm going
to
respectfully ask again, if you could provide me with some information
on
what a person can do to fix a broken MrKnow url resolver? Right now
Specto
is not much use to me, and that's extremely disappointing. I LOVE
SPECTO.
If you can't fix it, could you suggest anything I could do?
1 - will sitting tight and waiting for another url resolver update
work?
2 - When is the next url resolver update rolling out? I don't want to
start uninstalling things until Specto has had the opportunity to fix
itself with an update.
3 - If I have to uninstall, would I have to uninstall the repository
as
well?
4 - Is there anything else, anything at all that you can inform me of
that might help me resolve this?
I know my last issue about the changelog was kind of trivial, and I
was
really just offering my opinion, and I will refrain from posting such
issues in the future, but this one is a big, serious issue for me and I
really need your help.
Thanking you in advance for this and thanks again for all your past
efforts...
BankruptEd
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/mrknow/filmkodi/issues/758#issuecomment-280789968
,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AUPc7F-pCm5UFjv-
RUnDCCysrTIcbVIwks5rdiaHgaJpZM4L9SBQ>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mrknow/filmkodi/issues/758#issuecomment-280821311,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUPc7DM-Nq-A3jYAYd2uyPW4x0AbOb6Nks5rdnVagaJpZM4L9SBQ
.

I can give you lots more if you want, just not sure how many you would
like. Say so, and I can get tons more examples.
On Feb 17, 2017 11:36 PM, "Azrin Aris"<EMAIL_ADDRESS>wrote:

Any particular movies or shows that I can help to test?
Sent from my iPhone

On 18 Feb 2017, at 09:26, BankruptEd<EMAIL_ADDRESS>wrote:
I run and inl3d ultra android box. I would have to check the version (not
at home right now) using the latest Kodi, the latest Specto. I was
actually
in Specto when the update came through, and it simply said MrKnow url
resolver update failed. Ever since then, it can't find any sources for a
whole multitude of shows. And only seems to find HD and HQ sources when
it
does find some. And this only seems to pertain to the newest, most
popular
shows. So I just don't have a clue what I should do.
On Feb 17, 2017 6:00 PM, "Azrin Aris"<EMAIL_ADDRESS>wrote:

Hi,
I'm just wondering,
Why is the URLresolver of yours is not working? I just updated mine and
all seems to work fine.
Can you share what machine configuration are you on. May be I can help
you
a bit.
Sent from my iPhone

On 17 Feb 2017, at 22:20, BankruptEd<EMAIL_ADDRESS>wrote:
Hi MrKnow. Hope you're well. Let me start by saying, I know you're
busy.
You have lots of issues to deal with in respect to Specto, and no
doubt a
life outside of Specto also demanding your time. That said, I'm going
to
respectfully ask again, if you could provide me with some information
on
what a person can do to fix a broken MrKnow url resolver? Right now
Specto
is not much use to me, and that's extremely disappointing. I LOVE
SPECTO.
If you can't fix it, could you suggest anything I could do?
1 - will sitting tight and waiting for another url resolver update
work?
2 - When is the next url resolver update rolling out? I don't want to
start uninstalling things until Specto has had the opportunity to fix
itself with an update.
3 - If I have to uninstall, would I have to uninstall the repository
as
well?
4 - Is there anything else, anything at all that you can inform me of
that might help me resolve this?
I know my last issue about the changelog was kind of trivial, and I
was
really just offering my opinion, and I will refrain from posting such
issues in the future, but this one is a big, serious issue for me and I
really need your help.
Thanking you in advance for this and thanks again for all your past
efforts...
BankruptEd
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/mrknow/filmkodi/issues/758#issuecomment-280789968
,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AUPc7F-pCm5UFjv-
RUnDCCysrTIcbVIwks5rdiaHgaJpZM4L9SBQ>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mrknow/filmkodi/issues/758#issuecomment-280821311,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUPc7DM-Nq-A3jYAYd2uyPW4x0AbOb6Nks5rdnVagaJpZM4L9SBQ
.

Here's an interesting thing. For the newest Simpsons, I get no sources at
all. The show just before it, I get like five sources. It's like I'm
getting no new sources, and the old ones are running out kind of. I'm
getting less all the time. Eventually none I'm guessing.
On Feb 17, 2017 11:36 PM, "Azrin Aris"<EMAIL_ADDRESS>wrote:

Any particular movies or shows that I can help to test?
Sent from my iPhone

On 18 Feb 2017, at 09:26, BankruptEd<EMAIL_ADDRESS>wrote:
I run and inl3d ultra android box. I would have to check the version (not
at home right now) using the latest Kodi, the latest Specto. I was
actually
in Specto when the update came through, and it simply said MrKnow url
resolver update failed. Ever since then, it can't find any sources for a
whole multitude of shows. And only seems to find HD and HQ sources when
it
does find some. And this only seems to pertain to the newest, most
popular
shows. So I just don't have a clue what I should do.
On Feb 17, 2017 6:00 PM, "Azrin Aris"<EMAIL_ADDRESS>wrote:

Hi,
I'm just wondering,
Why is the URLresolver of yours is not working? I just updated mine and
all seems to work fine.
Can you share what machine configuration are you on. May be I can help
you
a bit.
Sent from my iPhone

On 17 Feb 2017, at 22:20, BankruptEd<EMAIL_ADDRESS>wrote:
Hi MrKnow. Hope you're well. Let me start by saying, I know you're
busy.
You have lots of issues to deal with in respect to Specto, and no
doubt a
life outside of Specto also demanding your time. That said, I'm going
to
respectfully ask again, if you could provide me with some information
on
what a person can do to fix a broken MrKnow url resolver? Right now
Specto
is not much use to me, and that's extremely disappointing. I LOVE
SPECTO.
If you can't fix it, could you suggest anything I could do?
1 - will sitting tight and waiting for another url resolver update
work?
2 - When is the next url resolver update rolling out? I don't want to
start uninstalling things until Specto has had the opportunity to fix
itself with an update.
3 - If I have to uninstall, would I have to uninstall the repository
as
well?
4 - Is there anything else, anything at all that you can inform me of
that might help me resolve this?
I know my last issue about the changelog was kind of trivial, and I
was
really just offering my opinion, and I will refrain from posting such
issues in the future, but this one is a big, serious issue for me and I
really need your help.
Thanking you in advance for this and thanks again for all your past
efforts...
BankruptEd
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/mrknow/filmkodi/issues/758#issuecomment-280789968
,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AUPc7F-pCm5UFjv-
RUnDCCysrTIcbVIwks5rdiaHgaJpZM4L9SBQ>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mrknow/filmkodi/issues/758#issuecomment-280821311,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUPc7DM-Nq-A3jYAYd2uyPW4x0AbOb6Nks5rdnVagaJpZM4L9SBQ
.

just tested simpson season 28, s28e01 gives me 167 and s28e02 gives me 200+ links
Autopsy however only gives me between 8-38 links
For me as long as I got links and is playable, its good enough for me.
May be what you can do is to of to Specto->Tools and elect clear cache and clear sources.

On 18 Feb 2017, at 12:58 PM, BankruptEd<EMAIL_ADDRESS>wrote:
Here's an interesting thing. For the newest Simpsons, I get no sources at
all. The show just before it, I get like five sources. It's like I'm
getting no new sources, and the old ones are running out kind of. I'm
getting less all the time. Eventually none I'm guessing.
On Feb 17, 2017 11:36 PM, "Azrin Aris"<EMAIL_ADDRESS>wrote:

Any particular movies or shows that I can help to test?
Sent from my iPhone

On 18 Feb 2017, at 09:26, BankruptEd<EMAIL_ADDRESS>wrote:
I run and inl3d ultra android box. I would have to check the version (not
at home right now) using the latest Kodi, the latest Specto. I was
actually
in Specto when the update came through, and it simply said MrKnow url
resolver update failed. Ever since then, it can't find any sources for a
whole multitude of shows. And only seems to find HD and HQ sources when
it
does find some. And this only seems to pertain to the newest, most
popular
shows. So I just don't have a clue what I should do.
On Feb 17, 2017 6:00 PM, "Azrin Aris"<EMAIL_ADDRESS>wrote:

Hi,
I'm just wondering,
Why is the URLresolver of yours is not working? I just updated mine and
all seems to work fine.
Can you share what machine configuration are you on. May be I can help
you
a bit.
Sent from my iPhone

On 17 Feb 2017, at 22:20, BankruptEd<EMAIL_ADDRESS>wrote:
Hi MrKnow. Hope you're well. Let me start by saying, I know you're
busy.
You have lots of issues to deal with in respect to Specto, and no
doubt a
life outside of Specto also demanding your time. That said, I'm going
to
respectfully ask again, if you could provide me with some information
on
what a person can do to fix a broken MrKnow url resolver? Right now
Specto
is not much use to me, and that's extremely disappointing. I LOVE
SPECTO.
If you can't fix it, could you suggest anything I could do?
1 - will sitting tight and waiting for another url resolver update
work?
2 - When is the next url resolver update rolling out? I don't want to
start uninstalling things until Specto has had the opportunity to fix
itself with an update.
3 - If I have to uninstall, would I have to uninstall the repository
as
well?
4 - Is there anything else, anything at all that you can inform me of
that might help me resolve this?
I know my last issue about the changelog was kind of trivial, and I
was
really just offering my opinion, and I will refrain from posting such
issues in the future, but this one is a big, serious issue for me and I
really need your help.
Thanking you in advance for this and thanks again for all your past
efforts...
BankruptEd
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/mrknow/filmkodi/issues/758#issuecomment-280789968
,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AUPc7F-pCm5UFjv-
RUnDCCysrTIcbVIwks5rdiaHgaJpZM4L9SBQ>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mrknow/filmkodi/issues/758#issuecomment-280821311,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUPc7DM-Nq-A3jYAYd2uyPW4x0AbOb6Nks5rdnVagaJpZM4L9SBQ
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/mrknow/filmkodi/issues/758#issuecomment-280822185, or mute the thread https://github.com/notifications/unsubscribe-auth/AE-KrApmoR5FkPb1Jf-bymjm9BcvBmNAks5rdnpbgaJpZM4L9SBQ.

I cleared sources once already but not cache I don't think. I will give it
a shot. That's the only thing I don't like about kodi, I'm always kind of
living in fear of these problems cause I just don't know enough about it
and it's hard to find people willing to help like yourself and even then it
can still be difficult.
Ok I did it and still no go. I keep hoping another url resolver update will
come through and fix it but I haven't seen any Specto updates come through
some it happened. Hope thats not compromised too. Well I appreciate you
efforts anyhow.
On Feb 18, 2017 12:56 AM, "Azrin Aris"<EMAIL_ADDRESS>wrote:

just tested simpson season 28, s28e01 gives me 167 and s28e02 gives me
200+ links
Autopsy however only gives me between 8-38 links
For me as long as I got links and is playable, its good enough for me.
May be what you can do is to of to Specto->Tools and elect clear cache and
clear sources.

On 18 Feb 2017, at 12:58 PM, BankruptEd<EMAIL_ADDRESS>wrote:
Here's an interesting thing. For the newest Simpsons, I get no sources at
all. The show just before it, I get like five sources. It's like I'm
getting no new sources, and the old ones are running out kind of. I'm
getting less all the time. Eventually none I'm guessing.
On Feb 17, 2017 11:36 PM, "Azrin Aris"<EMAIL_ADDRESS>wrote:

Any particular movies or shows that I can help to test?
Sent from my iPhone

On 18 Feb 2017, at 09:26, BankruptEd<EMAIL_ADDRESS>wrote:
I run and inl3d ultra android box. I would have to check the version
(not
at home right now) using the latest Kodi, the latest Specto. I was
actually
in Specto when the update came through, and it simply said MrKnow url
resolver update failed. Ever since then, it can't find any sources
for a
whole multitude of shows. And only seems to find HD and HQ sources
when
it
does find some. And this only seems to pertain to the newest, most
popular
shows. So I just don't have a clue what I should do.
On Feb 17, 2017 6:00 PM, "Azrin Aris"<EMAIL_ADDRESS>wrote:

Hi,
I'm just wondering,
Why is the URLresolver of yours is not working? I just updated
mine and
all seems to work fine.
Can you share what machine configuration are you on. May be I can
help
you
a bit.
Sent from my iPhone

On 17 Feb 2017, at 22:20, BankruptEd<EMAIL_ADDRESS>wrote:
Hi MrKnow. Hope you're well. Let me start by saying, I know
you're
busy.
You have lots of issues to deal with in respect to Specto, and no
doubt a
life outside of Specto also demanding your time. That said, I'm
going
to
respectfully ask again, if you could provide me with some
information
on
what a person can do to fix a broken MrKnow url resolver? Right now
Specto
is not much use to me, and that's extremely disappointing. I LOVE
SPECTO.
If you can't fix it, could you suggest anything I could do?
1 - will sitting tight and waiting for another url resolver
update
work?
2 - When is the next url resolver update rolling out? I don't
want to
start uninstalling things until Specto has had the opportunity to
fix
itself with an update.
3 - If I have to uninstall, would I have to uninstall the
repository
as
well?
4 - Is there anything else, anything at all that you can inform
me of
that might help me resolve this?
I know my last issue about the changelog was kind of trivial,
and I
was
really just offering my opinion, and I will refrain from posting
such
issues in the future, but this one is a big, serious issue for me
and I
really need your help.
Thanking you in advance for this and thanks again for all your
past
efforts...
BankruptEd
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the
thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/mrknow/filmkodi/issues/758#
issuecomment-280789968
,
or mute the thread
<https://github.com/notifications/unsubscribe-
auth/AUPc7F-pCm5UFjv-
RUnDCCysrTIcbVIwks5rdiaHgaJpZM4L9SBQ>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/mrknow/filmkodi/issues/758#issuecomment-280821311
,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AUPc7DM-Nq-
A3jYAYd2uyPW4x0AbOb6Nks5rdnVagaJpZM4L9SBQ>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <
https://github.com/mrknow/filmkodi/issues/758#issuecomment-280822185>, or
mute the thread <https://github.com/notifications/unsubscribe-
auth/AE-KrApmoR5FkPb1Jf-bymjm9BcvBmNAks5rdnpbgaJpZM4L9SBQ>.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mrknow/filmkodi/issues/758#issuecomment-280824596,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUPc7NWs0toNzLZHUF0qXb7Nhuz6qEXQks5rdogcgaJpZM4L9SBQ
.

To mslavishlyfe - not sure if your problem is exactly the same as mine, but I did manage to get my url resolver up and running. Had to go to "add-on information" then "update" then obviously to MrKnow update selection.  So u might wanna try that even if you do auto updates as I do. It still fixed it up for me.

Same prob hun. I appreciate that! Going to give it a go later today.
On Feb 21, 2017 1:26 PM, "BankruptEd"<EMAIL_ADDRESS>wrote:

To mslavishlyfe - not sure if your problem is exactly the same as mine,
but I did manage to get my url resolver up and running. Had to go to
"add-on information" then "update" then obviously to MrKnow update
selection.  So u might wanna try that even if
you do auto updates as I do. It still fixed it up for me.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mrknow/filmkodi/issues/758#issuecomment-281452554,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYi636sLKq1lkzxjS7M6AUHHBT7ZaB2Mks5rezpdgaJpZM4L9SBQ
.


Fix/remove printing html

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@f1e74c1). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #2   +/-   ##
=======================================
  Coverage        ?   54.76%
=======================================
  Files           ?        7
  Lines           ?       84
  Branches        ?        2
=======================================
  Hits            ?       46
  Misses          ?       38
  Partials        ?        0

Continue to review full report at Codecov.

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


nova test policy

Hello, it is my redic problem in that when you do tests with a user who does not have permissions, ak runs my test only passes the one that cannot create but those to update and but it does not happen because this error is due
namespace Tests\Feature;
use App\User;
use NovaTesting\NovaAssertions;
use Illuminate\Support\Facades\Config;
use Tests\TestCase;
class UserNovaTest extends TestCase
{
use NovaAssertions;
/* function __construct()
{
    parent::setUp();
} */

public function PolicyCannot($index)
{
    $user = User::where('name', 'roberto')->first();
    $this->actingAs($user)->withSession(['business_center_id' => 1]);
    Config::set('testing.viewAny', false);
    Config::set('testing.create', false);
    Config::set('testing.update', false);
    Config::set('testing.delete', false);
    Config::set('testing.restore', false);
    Config::set('testing.forceDelete', false);
    $response = $this->novaIndex($index);
    $response->assertStatus(403);
    $response->assertCannotCreate();
    $response->assertCannotUpdate();
    $response->assertCannotDelete();
    $response->assertCannotForceDelete();
    $response->assertCannotRestore();
}
public function test_user_nova()
{
    $this->PolicyCannot('offices');
    $this->PolicyCannot('patients');
    $this->PolicyCannot('appointments');
    $this->PolicyCannot('promotions');
    $this->PolicyCannot('medical-services-categories');
    $this->PolicyCannot('appointment-statuses');
    $this->PolicyCannot('professionals');
    $this->PolicyCannot('medical-services');
    $this->PolicyCannot('symptom-categories');
    $this->PolicyCannot('records');
    $this->PolicyCannot('medical-records');
}

}

error
Time: 00:00.402, Memory: 34.00 MB
There was 1 failure:

Tests\Feature\UserNovaTest::test_user_nova
Unable to find JSON fragment:

[{"authorizedToUpdate":false}]


AWQ Quantization padding error

Line 474 in weight_only.py is trying to pad the the tensor so that the first dimension is divisible by the block size. The problem is that instead of passing the shape of the transposed tensor, org_w_shape is used to calculate the number of blocks, which is the shape of the tensor before it gets transposed. This results in the pad_tensor function padding the smaller dimension to be equal to the, instead of padding to a multiple of the block size.
Take the example where you have a tensor with shape [8192, 3072] and a block size of 32:

org_w_shape will be set [8192, 3072]
We transpose the weight tensor on line 473 and its shape becomes [3072, 8192].
We compute the number of blocks on line 474 by doing (org_w_shape[0] + group_size - 1) // 32, which gives us (8192 + 32 - 1) // 32 =  256.
Inside pad_tensor, we calculate padded_rows = k_blocks * group_size = 8192 and pad_len = 8192 - 3072 = 5120

The expected behavior is that the padding would do nothing, but because we use the wrong dimension, we will end up padding the 3072 dimension to be equal to the 8192 dimension, resulting in a tensor fo shape [8192, 8192]. It will then fail later on when we reshape the tensor since the sizes don't match.

thank you for your comments, we will fix it soon.


add remaining autogenerated files to gitignore

as discussed during the last lecture. This results in a clean tree after doing the default compile with make.

Thanks!


Allows derivation fallback messages to be suppressed

Fixes #718
Need to update compiler targets as they are falling with newer Scala/Java versions.

Rather than blanket-disabling these, we should probably have a flag on the Reader/Writer type that declares whether it is for hot-reloading purposes or for external components. Because we don't want to suppress this warning for externals, since that could lead to broken behavior.


overload transform / transformToUni / transformToMulti

It's annoying that the UniOnItem.transformXxxxx() methods don't have overloaded versions that accept Supplier instead of Function, just like call() already does.
(By adding these overloads we alleviate the need for v or ignore parameters in the argument anonymous functions.)

I faced the same issue over the weekend! So +1.

But it's not really a transform anymore, it's more a replace.

Indeed Supplier drops the item. so a Supplier here does not follow the transform semantics.

@gavinking would UnOnEvent::replaceWith(Supplier<T/Uni<?>>) work for you?

That kinda reflects a bit of a deeper confusion over the organization of these methods. See the discussion in https://github.com/smallrye/smallrye-mutiny/issues/319.
I think we need to clarify our thinking on exactly how the names map to semantics.
One could, for example, make the same criticism of one of the overloads of chain() on Uni.

I'm collecting thoughts regarding #319 👍

@gavinking would UnOnEvent::replaceWith(Supplier<T/Uni<?>>) work for you?

and forget this, because it clashes for the compiler

I'm moving the discussion to #319


--all doesn't use configured file extensions

#163 introduced configurable file extensions however --all only selects **/*.js files. We could generate that pattern for all configured extensions and then use globby to load the files.

@lloydcotten perhaps you'd be interested in improving this? No obligation of course :smiley_cat:

Hmm... I see.  Yes, perhaps I could look at that.


Keep x and y values

Would be cool if you could set a frame or layout and tell it to keep its x and y value. Something like:
.offerRowView {
    frame: rect(current, current, 30, 100%);
}

That is a great suggestion - I'll certainly consider adding that.
Cheers,
Tobias


search through games list

this would be done by using ⌘ + f. when this is pressed the list will filter by whatever the user inputs.

don't even have to manually add a textfield. literally just this:
https://developer.apple.com/documentation/swiftui/adding-a-search-interface-to-your-app

done but cmd + f isn't possible to implement atm. https://developer.apple.com/forums/thread/688679


updated example around word_count to be more streamlined and use Stream

Updated the Example Solution for word_count() to use Streams and reduce overall complexity.

🤩🤩🤩


Release Kubernetes v1.22 support

Required for https://github.com/newrelic/nri-discovery-kubernetes/pull/46

Done now.


WIP - feat: try to fetch revision id to work out if event is an update

NB this is just an experiment to investigate how to process updates in the sink connector and will not be merged.
This works in the base case, but:

Performance will be terrible for large number of docs
What happens if the document is modified between fetching the etag and doing the bulk write?

Closing experimental PR - not progressing right now


"Test host process crashed" error hard to diagnose

Our CI has an intermittent failure:
The active test run was aborted. Reason: Test host process crashed
Results File: C:\a\_temp\AzDevOps_2019-6vse00024V_2021-06-24_02_47_47.trx
Test Run Aborted.

As far as I can tell, the message is printed by this code:
https://github.com/microsoft/vstest/blob/eff66c00b217b355b6ee11034ff8396a618d04e3/src/Microsoft.TestPlatform.CommunicationUtilities/TestRequestSender.cs#L667
It would be really helpful here if it printed the full path to the process executable that crashed. I took a quick look but I couldn't find where to get the executable full path from. Also it seems that the error output stream contents was empty (clientExitErrorMessage) so when the test process crashes it should print the full exception stack to the Console.Error so that the stack appears in the CI log.

FYI @aarnott who has been investigating this recently

I have found out what my problem was. It's that infamous 100ms bug striking again, I can't even fathom how much that bug has caused our ecosystem in terms of productivity loss. I personally wasted four full days tracking this down.
I had to add --diag to my dotnet test arguments to publish the diagnostic logs, and then a separate step to upload them as artifacts.
Finally I saw this:
TpTrace Error: 0 : 6860, 7, 2021/06/26, 19:34:34.416,<PHONE_NUMBER>, vstest.console.dll, LengthPrefixCommunicationChannel.Send: Error sending data: System.IO.IOException: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host..
 ---> System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host.
   at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   --- End of inner exception stack trace ---
   at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.IO.BufferedStream.Flush()
   at System.IO.BinaryWriter.Flush()
   at Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.LengthPrefixCommunicationChannel.Send(String data).
TpTrace Warning: 0 : 6860, 7, 2021/06/26, 19:34:34.417,<PHONE_NUMBER>, vstest.console.dll, ProxyOperationManager: Failed to end session: Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.Interfaces.CommunicationException: Unable to send data over channel.
 ---> System.IO.IOException: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host..
 ---> System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host.
   at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   --- End of inner exception stack trace ---
   at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.IO.BufferedStream.Flush()
   at System.IO.BinaryWriter.Flush()
   at Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.LengthPrefixCommunicationChannel.Send(String data)
   --- End of inner exception stack trace ---
   at Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.LengthPrefixCommunicationChannel.Send(String data)
   at Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.TestRequestSender.EndSession()
   at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.ProxyOperationManager.Close()
TpTrace Warning: 0 : 6860, 7, 2021/06/26, 19:34:34.417,<PHONE_NUMBER>, vstest.console.dll, ProxyOperationManager: Timed out waiting for test host to exit. Will terminate process.

 All the user sees is:
The active test run was aborted. Reason: Test host process crashed

So then the user is sent on a wild goose chase for 4 days trying to figure out various ways to deploy procdump.exe to the CI agent, find out that it doesn't work anyway because we only explicitly pass StackOverflowException and AccessViolationException as arguments to procdump and ignore other types of exceptions.
We killed the process, we know it, but we don't log it, don't publish the dump, don't have any MSBuild errors, leaving the user helpless, frustrated, blocked, not knowing how to proceed.

I agree it could be easier if you use dotnet test. But we also have vstest yaml task (and classic pipeline task) which has all those cool levers, which could have saved you those 4 days.

It enables crash dump for critical failures (it includes procdump and configures the procdump_path).
When running the pipeline, you can click Enable system diagnostics. The task will check that and add diag parameters to the call to vstest. And upload the logs afterwards. You will get them by clicking on ... on the run, and Download logs, our logs have .diag extension. Alternatively you can set syste.debug = true in your pipeline to have this enabled all the time.

The error above looks more like testhost crashed, rather than vstest.console just failing to await it. Please upload the logs if you can, or point me to the build. Or is it one of the builds you shared in chat?

Yes, it's the build I mentioned in chat.
Things should work regardless of whether I'm using dotnet test or the VSTest yaml task. Where are the docs for the VSTest task? Where are these screenshots from? What is the yaml syntax if I wanted to switch my pipeline from dotnet test to VSTest?
dotnet test experience should be just as well supported as the VSTest task.

I've switched to the LocalDumps registry key and will report how that goes.
- powershell: |
    $key = "HKLM:\\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps"
    $LogDir = "$(Build.ArtifactStagingDirectory)\build_logs"
    New-Item -Path $key -ErrorAction SilentlyContinue
    New-ItemProperty -Path $key -Name 'DumpType' -PropertyType 'DWord' -Value 2 -Force
    New-ItemProperty -Path $key -Name 'DumpCount' -PropertyType 'DWord' -Value 10 -Force
    New-ItemProperty -Path $key -Name 'DumpFolder' -PropertyType 'String' -Value $LogDir -Force
    displayName: Enable LocalDumps in registry
    continueOnError: true

- powershell: |
    $key = "HKLM:\\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps"
    New-Item -Path $key -ErrorAction SilentlyContinue
    New-ItemProperty -Path $key -Name 'DumpType' -PropertyType 'DWord' -Value 0 -Force
  displayName: Disable LocalDumps in registry
  continueOnError: true
  condition: always()

Not sure if this is the same as this issue as well.
We've also just started encountering this error as well, seemingly randomly as we're trying to add one test and it's failing in a completely different error. Log notes here:
TpTrace Verbose: 0 : 6936, 7, 2021/08/02, 22:54:58.235,<PHONE_NUMBER>7, vstest.console.exe, TestRunRequest:SendTestRunStatsChange: Starting.
TpTrace Verbose: 0 : 6936, 7, 2021/08/02, 22:54:58.236,<PHONE_NUMBER>6, vstest.console.exe, InProgress is Test_AdvancedCollectionView_Sorting_CustomComparable_With_Shaping
TpTrace Information: 0 : 6936, 7, 2021/08/02, 22:54:58.236,<PHONE_NUMBER>6, vstest.console.exe, TestRunRequest:SendTestRunStatsChange: Completed.
TpTrace Verbose: 0 : 6936, 7, 2021/08/02, 22:54:58.236,<PHONE_NUMBER>4, vstest.console.exe, TcpClientExtensions.MessageLoopAsync: Polling on remoteEndPoint: <IP_ADDRESS>:50149 localEndPoint: <IP_ADDRESS>:50148
TpTrace Verbose: 0 : 6936, 7, 2021/08/02, 22:54:59.237,<PHONE_NUMBER>4, vstest.console.exe, TcpClientExtensions.MessageLoopAsync: Polling on remoteEndPoint: <IP_ADDRESS>:50149 localEndPoint: <IP_ADDRESS>:50148
TpTrace Verbose: 0 : 6936, 7, 2021/08/02, 22:55:00.237,<PHONE_NUMBER>5, vstest.console.exe, TcpClientExtensions.MessageLoopAsync: Polling on remoteEndPoint: <IP_ADDRESS>:50149 localEndPoint: <IP_ADDRESS>:50148
TpTrace Verbose: 0 : 6936, 7, 2021/08/02, 22:55:01.240,<PHONE_NUMBER>2, vstest.console.exe, TcpClientExtensions.MessageLoopAsync: NotifyDataAvailable remoteEndPoint: <IP_ADDRESS>:50149 localEndPoint: <IP_ADDRESS>:50148
TpTrace Error: 0 : 6936, 7, 2021/08/02, 22:55:01.416,<PHONE_NUMBER>3, vstest.console.exe, Socket: Message loop: failed to receive message due to socket error System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
   at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
   at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
   --- End of inner exception stack trace ---
   at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
   at System.IO.Stream.ReadByte()
   at System.IO.BinaryReader.ReadByte()
   at System.IO.BinaryReader.Read7BitEncodedInt()
   at System.IO.BinaryReader.ReadString()
   at Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.LengthPrefixCommunicationChannel.NotifyDataAvailable()
   at Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.TcpClientExtensions.MessageLoopAsync(TcpClient client, ICommunicationChannel channel, Action`1 errorHandler, CancellationToken cancellationToken), remoteEndPoint: <IP_ADDRESS>:50149 localEndPoint: <IP_ADDRESS>:50148

@nohwnd @KirillOsenkov any updates on getting more diagnostics? We've wasted a couple of weeks pulling our hair out trying to understand what's going wrong here.
FYI @azchohfi @huynhsontung

Have you tried the LocalDumps registry key to upload dumps from your CI?

I was wondering if you had any update on this issue? I am seeing a stack trace that looks just like the one @michael-hawker mentioned.

The active test run was aborted. Reason: Test host process crashed
Test Run Aborted with error System.Exception: One or more errors occurred.
---> System.Exception: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host..
---> System.Exception: An existing connection was forcibly closed by the remote host.
at System.Net.Sockets.NetworkStream.Read(Span1 buffer)    --- End of inner exception stack trace ---    at System.Net.Sockets.NetworkStream.Read(Span1 buffer)
at System.Net.Sockets.NetworkStream.ReadByte()
at System.IO.BinaryReader.Read7BitEncodedInt()
at System.IO.BinaryReader.ReadString()
at Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.LengthPrefixCommunicationChannel.NotifyDataAvailable()
at Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.TcpClientExtensions.MessageLoopAsync(TcpClient client, ICommunicationChannel channel, Action`1 errorHandler, CancellationToken cancellationToken)
--- End of inner exception stack trace ---.

This worked fine in .NET 5 VS 2019. In .NET 6 VS 2022 I am seeing this issue.
I was wondering if I can provide something to help diagnose this issue. Until this is fixed I will have to turn off my unit test.

@Daniellled do you have diag logs that you could share? Please.

I think that I'm seeing the same thing when trying to use the blame collector in dotnet test. It is causing my CI to fail tests and not upload any of the results or the blame crashes. There is a simple repro:

Create a test project with a single test that just hangs for 10 seconds (use Thread.Sleep()) or something
Build the test
run dotnet test mytestproj.csproj --blame-hang --blame-hang-dump-type full --blame-hang-timeout 5s

See this output:
A total of 1 test files matched the specified pattern.
The active test run was aborted. Reason: Test host process crashed
Data collector 'Blame' message: The specified inactivity time of 5 seconds has elapsed. Collecting hang dumps from testhost and its child processes.
Data collector 'Blame' message: Dumping 21452 - testhost.

The active Test Run was aborted because the host process exited unexpectedly. Please inspect the call stack above, if available, to get more information about where the exception originated from.
The test running when the crash occurred:
IntegrationTest1.IntegrationTest1.Test1

This test may, or may not be the source of the crash.

Attachments:
  E:\dd\dmshiftleft\WebAppRazorPages\Tests\IntegrationTest1\TestResults\02aefd21-43ee-49db-9235-84cd19e3a678\Sequence_13b9bc7b5d554ea9bdfab637b375ce44.xml
  E:\dd\dmshiftleft\WebAppRazorPages\Tests\IntegrationTest1\TestResults\02aefd21-43ee-49db-9235-84cd19e3a678\testhost_21452_20211130T132430_hangdump.dmp
Test Run Aborted with error System.Exception: One or more errors occurred.
 ---> System.Exception: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host..
 ---> System.Exception: An existing connection was forcibly closed by the remote host.
   at System.Net.Sockets.NetworkStream.Read(Span`1 buffer)
   --- End of inner exception stack trace ---
   at System.Net.Sockets.NetworkStream.Read(Span`1 buffer)
   at System.Net.Sockets.NetworkStream.ReadByte()
   at System.IO.BinaryReader.Read7BitEncodedInt()
   at System.IO.BinaryReader.ReadString()
   at Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.LengthPrefixCommunicationChannel.NotifyDataAvailable()
   at Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.TcpClientExtensions.MessageLoopAsync(TcpClient client, ICommunicationChannel channel, Action`1 errorHandler, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---.

I think that if any collector is attempting to gather data at the end of the test run, then this timeout will be hit and none of the attachments will be uploaded.

Was this file not created at all? The error below just means that the testhost was killed (the dumper tool did that because it was hanging), but it is the data collector that is reponsible for waiting for the dump to end and passing the file as attachment to the vstest.console. It shows up on the screen so the file should be created successfully.
E:\dd\dmshiftleft\WebAppRazorPages\Tests\IntegrationTest1\TestResults\02aefd21-43ee-49db-9235-84cd19e3a678\testhost_21452_20211130T132430_hangdump.dmp

Was this file not created at all? The error below just means that the testhost was killed (the dumper tool did that because it was hanging), but it is the data collector that is reponsible for waiting for the dump to end and passing the file as attachment to the vstest.console. It shows up on the screen so the file should be created successfully.
E:\dd\dmshiftleft\WebAppRazorPages\Tests\IntegrationTest1\TestResults\02aefd21-43ee-49db-9235-84cd19e3a678\testhost_21452_20211130T132430_hangdump.dmp

The file gets created, but it doesn't get copied into the correct location to be uploaded to artifacts in my pipelines. Normally trx files and their corresponding dumps would get uploaded to artifacts. I've had to resort to scanning the temp directory for test results and dumps when the blame collector captures hangs.

Getting the same with  net6.0 but also net5.0, 3.x and 2.x by varying the global json. Thus the .NET Core version does not seem to matter. I believe that a .NET Core SDK update has resulted in this bug, quite possibly by modifying a global value/location because dotnet test ...<etc>.... used to work for us until recently.
Just guessing here, so take the above comment with a grain of salt.

In https://github.com/dotnet/runtime/issues/66515 this was because of an AV in the test itself. That's not a vs test bug. But IMO vstest should not dump the NotifyDataAvailable stack at this point. NotifyDataAvailable should catch the exception, which should be an IOException (it's been unwrapped below I believe) since that stack is purely a detail of vstest implementation when the test itself spontaneously quits.
Testlauf für "E:\external\dotnet\runtime\artifacts\bin\System.IO.FileSystem.Tests\Release\net7.0-windows\System.IO.FileSystem.Tests.dll" (.NETCoreApp,Version=v7.0)
Die Testausführung wird gestartet, bitte warten...
Insgesamt 1 Testdateien stimmten mit dem angegebenen Muster überein.
Der aktive Testlauf wurde abgebrochen. Grund: Der Testhostprozess ist abgestürzt. : Fatal error. System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at System.Threading.Thread.get_OptimalMaxSpinWaitsPerSpinIteration()
   at System.Threading.LowLevelSpinWaiter.Wait(Int32, Int32, Int32)
   at System.Threading.LowLevelLifoSemaphore.Wait(Int32, Boolean)
   at System.Threading.PortableThreadPool+WorkerThread.WorkerThreadStart()

Ergebnisdatei: E:\external\dotnet\runtime\artifacts\bin\System.IO.FileSystem.Tests\Release\net7.0-windows\TestResults\robin_ROBIN-PC_2022-03-11_19_37_56.trx
HTML-Testergebnisdatei: E:\external\dotnet\runtime\artifacts\bin\System.IO.FileSystem.Tests\Release\net7.0-windows\TestResults\TestResult_robin_ROBIN-PC_20220311_193756.html

Der Testlauf wurde mit dem Fehler System.Exception: One or more errors occurred.
 ---> System.Exception: Unable to read data from the transport connection: Eine vorhandene Verbindung wurde vom Remotehost geschlossen..
 ---> System.Exception: Eine vorhandene Verbindung wurde vom Remotehost geschlossen.
   at System.Net.Sockets.NetworkStream.Read(Span`1 buffer)
   --- End of inner exception stack trace ---
   at System.Net.Sockets.NetworkStream.Read(Span`1 buffer)
   at System.Net.Sockets.NetworkStream.ReadByte()
   at System.IO.BinaryReader.Read7BitEncodedInt()
   at System.IO.BinaryReader.ReadString()
   at Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.LengthPrefixCommunicationChannel.NotifyDataAvailable()
   at Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.TcpClientExtensions.MessageLoopAsync(TcpClient client, ICommunicationChannel channel, Action`1 errorHandler, CancellationToken cancellationToken)
   --- End of inner exception stack trace --- abgebrochen.

I agree, I've been planning to fix that message for a long time because that error is just confusing.

Same issue here with xUnit on Unix using dotnet test (net 6) in CI pipeline. No artifacts from previous builds. On windows (local machine) it is working. Also tried Microsoft.NET.Test.Sdk version 17.2.0-preview-20220401-08 and xunit version 2.4.2-pre.12 but getting the same error.

@KundM did you try enabling diag logs, and looking at it? Or collecting crash dumps? What target framework is your project targetting?

Any updates on this issue? I encountered the same error message  An existing connection was forcibly closed by the remote host when I'm trying to run a .net 472 test dll right after a .net core 3.1 test dll in the same process(in our own test tool based on VSTest and targeting .net core 3.1). But if I run the net472 test first, everything works fine. I've been struggling for several days figuring this out. I guess it might be a dependency issue or thread issue but not knowing what's happening for detail.

Any updates on this issue? I encountered the same error message An existing connection was forcibly closed by the remote host when I'm trying to run a .net 472 test dll right after a .net core 3.1 test dll in the same process(in our own test tool based on VSTest and targeting .net core 3.1). But if I run the net472 test first, everything works fine. I've been struggling for several days figuring this out. I guess it might be a dependency issue or threading issue but not knowing what's happening for detail.

Just FYI that I've resolved this issue and found out it's due to low version of Microsoft.NET.Test.Sdk. Upgrading it to 16.10.0 for test projects perfectly fixed my issue.

I'm encountering this issue randomly with the latest .NET 6 SDK. It will happen in random test projects (using XUnit) with no predictability (whether the test project itself was modified doesn't always seem to matter when running the whole of dotnet test). Has there been any progress on this? Adding --diag:logs/logs.txt doesn't give me any more information other than that the Test Host failed.

The same issue with Playwright.NET, xUnit and Microsoft.NET.Test.Sdk 17.4.0 in .netcoreapp3.1 project. Tests run on TeamCity agent.

Also just started getting this error in the last week. Has to disable our tests to get CI running which is not ideal.

We had the same error on our tests, it appeared we had a stack overflow in one of our tests. It was displayed above this error

We are experiencing the same error. Same stack . Since 2023.05.16, on two different pipelines. Only happens on C++ tests. If we split the C# and C++ the first will go through, the second will crash. Locally it runs without problems.
Der Testlauf wurde mit dem Fehler System.AggregateException: Mindestens ein Fehler ist aufgetreten. ---> System.IO.IOException: Von der Übertragungsverbindung können keine Daten gelesen werden: Eine vorhandene Verbindung wurde vom Remotehost geschlossen. ---> System.Net.Sockets.SocketException: Eine vorhandene Verbindung wurde vom Remotehost geschlossen    bei System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)    --- Ende der internen Ausnahmestapelüberwachung ---    bei System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)    bei System.IO.Stream.ReadByte()    bei System.IO.BinaryReader.ReadByte()    bei System.IO.BinaryReader.Read7BitEncodedInt()    bei System.IO.BinaryReader.ReadString()    bei Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.LengthPrefixCommunicationChannel.NotifyDataAvailable()    bei Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.TcpClientExtensions.MessageLoopAsync(TcpClient client, ICommunicationChannel channel, Action1 errorHandler, CancellationToken cancellationToken)
--- Ende der internen Ausnahmestapelüberwachung --- abgebrochen.
Gesamtzahl Tests: unbekannt
Bestanden: 1977
Nicht bestanden: 373
Gesamtzeit: 6,8843 Minuten`
Starting: VsTest - testAssemblies
Task         : Visual Studio Test (Side-by-side)
Description  : Run unit and functional tests (Selenium, Appium, Coded UI test, etc.) using the Visual Studio Test (VsTest) runner. Test frameworks that have a Visual Studio test adapter such as MsTest, xUnit, NUnit, Chutzpah (for JavaScript tests using QUnit, Mocha and Jasmine), etc. can be run. Tests can be distributed on multiple agents using this task (version 2).
Version      : 2.220.0
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/test/vstest
Microsoft (R) Testausführungs-Befehlszeilentool Version 17.4.1 (x64)
NUnit Adapter <IP_ADDRESS>: Test execution started

We are experiencing the same error. Same stack . Since 2023.05.16, on two different pipelines. Only happens on C++ tests. If we split the C# and C++ the first will go through, the second will crash. Locally it runs without problems.
Der Testlauf wurde mit dem Fehler System.AggregateException: Mindestens ein Fehler ist aufgetreten. ---> System.IO.IOException: Von der Übertragungsverbindung können keine Daten gelesen werden: Eine vorhandene Verbindung wurde vom Remotehost geschlossen. ---> System.Net.Sockets.SocketException: Eine vorhandene Verbindung wurde vom Remotehost geschlossen bei System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) --- Ende der internen Ausnahmestapelüberwachung --- bei System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) bei System.IO.Stream.ReadByte() bei System.IO.BinaryReader.ReadByte() bei System.IO.BinaryReader.Read7BitEncodedInt() bei System.IO.BinaryReader.ReadString() bei Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.LengthPrefixCommunicationChannel.NotifyDataAvailable() bei Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.TcpClientExtensions.MessageLoopAsync(TcpClient client, ICommunicationChannel channel, Action1 errorHandler, CancellationToken cancellationToken) --- Ende der internen Ausnahmestapelüberwachung --- abgebrochen. Gesamtzahl Tests: unbekannt Bestanden: 1977 Nicht bestanden: 373 Gesamtzeit: 6,8843 Minuten`
Starting: VsTest - testAssemblies
Task : Visual Studio Test (Side-by-side) Description : Run unit and functional tests (Selenium, Appium, Coded UI test, etc.) using the Visual Studio Test (VsTest) runner. Test frameworks that have a Visual Studio test adapter such as MsTest, xUnit, NUnit, Chutzpah (for JavaScript tests using QUnit, Mocha and Jasmine), etc. can be run. Tests can be distributed on multiple agents using this task (version 2). Version : 2.220.0 Author : Microsoft Corporation Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/test/vstest
Microsoft (R) Testausführungs-Befehlszeilentool Version 17.4.1 (x64) NUnit Adapter <IP_ADDRESS>: Test execution started

Update:
We have solved the problem by downgrading the Test Platform Version from 17.6.0 to 17.5.0
Cheers.

@sttobia  there are no clues in the log unfortunately, the testhost just dies, and vstest.console just says that the connection was closed. Were you able to collect dumps or inspect event viewer after the crash for some callstack?

@mlop3s were you able to collect a crash dump? e.g. by adding --blame-crash (you most likely need procdump in your PATH). It would be interesting to see what happened in 17.6, I am currently only aware of this critical issue https://github.com/microsoft/vstest/issues/4467 that affects 17.6, but it does not sound like something you are triggering.

@nohwnd We are not using dotnet but vstest and it crahses on C++ tests. I'm not aware of a blame-crash option for vstest.console.exe.
The managed tests are not crashing. Only the native C++. Not sure if it's related.

It looks like I have a similar Problem. When I start tests with the vstest.console.exe sometimes there is the "The active test run was aborted. Reason: Test host process crashed" despite all tests did run through.
So I tried to activate the timeout from "here https://github.com/microsoft/vstest/pull/3466/commits"
With setting the Variable in the .runsettings like
<RunSettings>
	<RunConfiguration>
		<EnvironmentVariables>
			<VSTEST_TESTHOST_SHUTDOWN_TIMEOUT>60000</VSTEST_TESTHOST_SHUTDOWN_TIMEOUT>
		</EnvironmentVariables>
	</RunConfiguration>
</RunSettings>

Then I tried setting it in the calling console like
SET VSTEST_TESTHOST_SHUTDOWN_TIMEOUT=60000

Then I tried to pass it directly to vstest like
vstest.console.exe dummy.dll /Settings:dummy.runsetting  /e:VSTEST_TESTHOST_SHUTDOWN_TIMEOUT=60000

Nothing had any effect despite I could verify that in the Test Environment the Environment Variable was always set. Following Unit Test was successful
[TestMethod]
public void CheckEnvironmentVariables()
{
    var timeout = int.TryParse(Environment.GetEnvironmentVariable("VSTEST_TESTHOST_SHUTDOWN_TIMEOUT"), out var time) ? time : 100;
    Assert.AreNotEqual(timeout, 100);
}

So I tried to enable logging to find out if the timeout was set correctly, but I couldn't find anywhere an EqtTrace with the timeout. Not in any logger, not in the diag log. I even tried to update the vstest.console.exe.config like this
<system.diagnostics>
    <switches>
      <add name="TpTraceLevel" value="0" />
      <add name="EqtTraceLevel" value="4" />
    </switches>
  </system.diagnostics>

So where can I find the EqtTrace Log or how do I set the Environment Variable correctly?

You would see the log when you use the /diag:logs/log.txt option. This env variable was shipped in 17.2.0, are you using vstest.console that is newer than that?
Why do you think the error is linked to the exit timeout? To me it looks like an actual crash.

When executing the tool we get "Microsoft (R) Testausfhrungs-Befehlszeilentool Version 17.6.2 (x64)". So the version should be fine.
I suspect a timeout because there is never a problem when we run the tests directly in visual studio.
I tried to log with /diag as suggest. I still couldn't find the EqtTrace Logs, but I saw something interesting in the TpTraces
Successful run:

Failed run:

The cleanup takes a bit longer in the version that failes, but it should wait longer before it reports the run as failed.

@sttobia there are no clues in the log unfortunately, the testhost just dies, and vstest.console just says that the connection was closed. Were you able to collect dumps or inspect event viewer after the crash for some callstack?

Hi @nohwnd sorry for the late reply, this somehow went by the board. Small update on this:
I tested the same code using another personal machine as another GitHub self-hosted runner, with the same VS version installed and there, everything seems to work fine. Also, there I get the same log messages:
TpTrace Verbose: 0 : 9604, 12, 2023/04/28, 18:59:21.253,<PHONE_NUMBER>31, vstest.console.dll, TestRequestSender.EndSession: Sending end session.
TpTrace Verbose: 0 : 9604, 12, 2023/04/28, 18:59:21.253,<PHONE_NUMBER>54, vstest.console.dll, ProxyOperationManager.Close: waiting for test host to exit for 100 ms
TpTrace Warning: 0 : 9604, 10, 2023/04/28, 18:59:21.281,<PHONE_NUMBER>75, vstest.console.dll, TestHostManagerCallbacks.ErrorReceivedCallback Test host standard error line:
TpTrace Verbose: 0 : 9604, 10, 2023/04/28, 18:59:21.303,<PHONE_NUMBER>37, vstest.console.dll, TestHostProvider.ExitCallBack: Host exited starting callback.
TpTrace Information: 0 : 9604, 10, 2023/04/28, 18:59:21.304,<PHONE_NUMBER>16, vstest.console.dll, TestHostManagerCallbacks.ExitCallBack: Testhost processId: 14360 exited with

So as you mentioned, there really seems to be nothing to learn from the logs. How would I go about "collecting dumps or inspecting event viewer after the crash for some callstack?". I think this is not straightforward as the tests are not being run in VS but using the console of a remote machine in our CI/CD pipeline (GitHub self-hosted runner). If run everything in VS locally, the issues don't arise, as mentioned.
Thanks for your help!

@sttobia how are you invoking vstest? Is it via yaml using VSTest task? Or in the "classical" graphical mode? Or running vstest.console directly? Or calling dotnet test directly?
Above you mention Github Action, so I assume you are doing dotnet test? in that case add --blame-crash to your run, that should generate the dump, and then you need to upload it.

@sttobia how are you invoking vstest? Is it via yaml using VSTest task? Or in the "classical" graphical mode? Or running vstest.console directly? Or calling dotnet test directly?
Above you mention Github Action, so I assume you are doing dotnet test? in that case add --blame-crash to your run, that should generate the dump, and then you need to upload it.

Exactly, I am running dotnet test "my\project" --no-build --output dotnet-my\project\bin\x64\Debug\net48 --verbosity detailed
When adding --blame-crash, it can not find procdump and I have been wasting this whole afternoon, trying to add it to the PATH  and/or setting PROCDUMP_PATH, so that GitHub can find it. Unfortunately, without success. Any experience or advice on this?

@sttobia The hosted agents have chocolatey on them, choco install --yes procdump should work just fine.

Thanks @nohwnd since the crash only happens on our self-hosted runners, this was not as straightforward. But finally I got it dumping, and you can take a look at both dumps on my drive. You should have gotten an e-mail with an invitation, since I can not upload them here.

I can see it fails in xUnit.GetAvailableRunnerReporters because it cannot load a module. I can see the name of the module. Sent you an email.

For UWP/WindowsAppSDK app tests, we see this message and it's not useful. We know it's happening at certain points due to an exception in the app platform which bubbles up to the UnhandledException handler. However, all we get in the CI log is the unable to communicate with test process message, which is less than helpful. We don't see the issue locally, so it's an arduous process to understand why it's only failing in our CI.
It'd be great if the test hosting app crashes, if the currently running test (that caused the failure) is output in the log, as well as the unhandled exception that caused the crash's stack info. Just those two changes alone would make debugging this scenario a world of difference better.
Related to #2593 #3936 #4376
Been trying to add better logging here into the logs themselves, but don't see logs working anymore for some reason, trying to upgrade, but was stopped by https://github.com/microsoft/testfx/issues/1726

It'd be great if the test hosting app crashes, if the currently running test (that caused the failure) is output in the log,

This is what --blame does, you will get sequence file which has a list of all finished and unfinished tests. And if you enable --diag you will get .datacollector. log that also has entries for tests that started and ended.
--blame-crash is then there to observe your tests (on windows you need procdump).
as well as the unhandled exception that caused the crash's stack info. Just those two changes alone would make debugging this scenario a world of difference better.
If the runtime writes it to the console of the app that is running we are able to capture that from vstest.console and write it to screen and log. That is what we do for .NET and .NET Framework applications. The experience with .NET is way better because they handle stack overflows and other exceptions "in-process" and write them to the screen before the process dies. In .NET Framework it simply writes the error without call stack and the process is killed. The info is written to event log, but we don't grab that info, because we cannot know exactly what entry to take and don't want to expose info of other processes.
We can look at how it behaves for UWP if you have a specific crash in mind.

I can see it fails in xUnit.GetAvailableRunnerReporters because it cannot load a module. I can see the name of the module. Sent you an email.

Quick update from my side: Looking at the procdump files, it looked like an issue with a specific DLL file in my build folder. After letting it rest for a while and then updating all packages at some point (including xunit IIRC), the problem was completely gone. In hindsight the process just crashing, and the dump not really helping out either, was really frustrating. Nevertheless, thank you for the support @nohwnd!

Just wanted point out something that has not been made clear in this thread so far.
If your tests interop with a native library either directly or thru a dependent managed DLL,
and a call to the native library results in a crash (e.g. exception code 0xC0000005 a.k.a EXCEPTION_ACCESS_VIOLATION)
then you're going to get the same exact "Test host process crashed" message during test runs.
A prerequisite for adding messages here should be: "have you debugged your tests under VS or windbg?"

@sanikolov Some issues might not manifest in the development environment (e.g. only in CI, or remote machines with different configurations). I think it's reasonable to want to more easily diagnose failures after the fact, espcecially in the case of a simple internal timeout from msbuild.
Personally, I think it would also be helpful here if there were an easy way to set up process level isolation with method level parallelization akin to #3424. Then we could more easily identify the failing test and get a simplified procdump to work diagnose. I note the change in isolation level might also prevent the crash from occuring, but that would probably be OK for my affected case (as it is due to third-party proprietary DLLs which the upstream provider won't/is unable to fix).

Hi all - I was just hoping if someone could either help or summarize the state of this issue.
I'll start with whats brought me here.
We've recently started to migrate to running on linux starting running our unit tests dlls using dotnet test on a linux host.
When running on windows the test past with no issue.
On Linux we'd hit this mysterious issue saying the 'Test host process crashed'.
Looking into the details logs from our test dll - there were no obvious issues... it just stops.
So we followed some of the steps here added --blame added diagnostic logging etc. We isolated it to one test (that again passed fine on windows). I combed the diagnostic log files that are produced

diag.datacollector
diag.host
*diag

and all I found was
TpTrace Verbose: 0 : 10226, 10, 2023/10/24, 07:55:32.658,<PHONE_NUMBER>27132, vstest.console.dll, TcpClientExtensions.MessageLoopAsync: NotifyDataAvailable remoteEndPoint: <IP_ADDRESS>:33932 localEndPoint: <IP_ADDRESS>:34540
TpTrace Error: 0 : 10226, 10, 2023/10/24, 07:55:32.659,<PHONE_NUMBER>46388, vstest.console.dll, Socket: Message loop: failed to receive message due to socket error System.IO.EndOfStreamException: Unable to read beyond the end of the stream.
   at System.IO.BinaryReader.ReadByte()
   at System.IO.BinaryReader.Read7BitEncodedInt()
   at System.IO.BinaryReader.ReadString()
   at Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.LengthPrefixCommunicationChannel.NotifyDataAvailable()
   at Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.TcpClientExtensions.MessageLoopAsync(TcpClient client, ICommunicationChannel channel, Action`1 errorHandler, CancellationToken cancellationToken), remoteEndPoint: <IP_ADDRESS>:33932 localEndPoint: <IP_ADDRESS>:34540

that exception is repeated a few times. From some searching this appears the the error you get when the test host unexpectedly terminates... but what I can't find is why...
I see near the start of this issue  someone mentions that the above stack trace is useless and that should be improved https://github.com/microsoft/vstest/issues/2952#issuecomment-1065479076
However I'm not seeing any real mention of a 'problem' after that. It seems it gets into weeds about adding diag logs etc... but I've done all that and it sheds no light.
Jump ahead a few wasted days... we found a null ref exception in the test. Its handled and causes no issues on windows. However if we prevent that exception being thrown... the tests run fine on linux... no crashed process.
My theory atm is that for some reason that exception is causing some kind of 'freeze' in the process and then its getting terminated because....???
Anyway I've chatted quite enough... can anyone help us with how could go about diagnosing such issues in the future.
(I can share full logs privately, but can't share them via github)

added --blame

Have you also added --blame-crash?
On which version of .NET sdk / vstest.console are you? And could you post simple repro of your problem, where was the null ref failing? My experience with crashes on .NET (not .NET Framework) is that you almost always get the full stack trace on screen in the crashing process. In the past we had problems picking this text up in the top level process, because the output streams api behavior differs on windows and linux, but that should have been fixed for a lo0ong time (since netcoreapp3.1 I think).

I see near the start of this issue someone mentions that the above stack trace is useless and that should be improved #2952 (comment)

Printing that error on crash / abort, was addressed, but it still shows up in the diag logs, because sometimes it is useful.

We had this issue pop up in last few days running our unit tests via a Github action.
   - name: Test
     run: |
       sed -i 's/"stopOnFail": false/"stopOnFail": true/g' UnitTests/xunit.runner.json
       dotnet test --no-restore --verbosity normal --collect:"XPlat Code Coverage"  --settings UnitTests/coverlet.runsettings --blame
       mv -v UnitTests/TestResults/*/*.* UnitTests/TestResults/

I just switched our runs-on from ubunti-latest to windows-latest and the tests now pass.
If I run the tests local in WSL they pass.

Hello, is there any progress? We also encountered this on CI/CD

Same issue on our side.
Even manually execution of vstest.console test is giving same error

3. --blame-hang --blame-hang-dump-type full --blame-hang-timeout 5s

Checking back on this, hoping something has been fixed in the meantime. It has not.

We had this issue pop up in last few days running our unit tests via a Github action.
   - name: Test
     run: |
       sed -i 's/"stopOnFail": false/"stopOnFail": true/g' UnitTests/xunit.runner.json
       dotnet test --no-restore --verbosity normal --collect:"XPlat Code Coverage"  --settings UnitTests/coverlet.runsettings --blame
       mv -v UnitTests/TestResults/*/*.* UnitTests/TestResults/

I just switched our runs-on from ubunti-latest to windows-latest and the tests now pass.
If I run the tests local in WSL they pass.

Checking back on this, hoping something has been fixed in the meantime. It has not.

I decided to try macos-latest and got a crash dump.
I have no idea what to do with it.
Note that I am not getting a sequence file here either. Arrrrgg!!

There is not sequence file because all tests finished running, see the last line in your screenshot.
In the logs that you uploaded you are specifying VSTEST_DUMP_PATH, this means you are responsible for uploading the created dumps (rather than vstest uploading them as attachments for you), are you doing that?
The dump you would need to inspect using dotnet dump tool,  you are probably looking for the locals in the callstack to see what data cannot be serialized. In any case this looks like an XUnit bug, there is a currently active issue that has the same error message:
https://github.com/xunit/xunit/issues/1742

In the logs that you uploaded you are specifying VSTEST_DUMP_PATH, this means you are responsible for uploading the created dumps (rather than vstest uploading them as attachments for you), are you doing that?

I never set VSTEST_DUMP_PATH explicitly. It's being set automatically somewhere.

We don't set it, it must be your or your system. I am just pointing that variable out, because it disables uploading the dumps automatically, because some systems prefer to collect all the dumps themselves from various places to have them in a single view.

For the record and others stumbling on this, the "infamous 100ms bug" mentioned under https://github.com/microsoft/vstest/issues/2952#issuecomment-871042574 is https://github.com/microsoft/vstest/issues/2379. It's here in the code.
While the default is still 100ms, you can now set the VSTEST_TESTHOST_SHUTDOWN_TIMEOUT env var (in ms) to be longer, potentially fixing your hanging tests. Perhaps something worth documenting?

Any idea how you're supposed to diagnose a test process crash that results in a hard pipeline exit?
The active test run was aborted. Reason: Test host process crashed
Data collector 'Blame' message: System.IO.FileNotFoundException: Collect dump was enabled but no dump file was generated.
   at Microsoft.TestPlatform.Extensions.BlameDataCollector.ProcessDumpUtility.GetDumpFiles(Boolean warnOnNoDumpFiles, Boolean processCrashed) in /_/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/ProcessDumpUtility.cs:line 84
   at Microsoft.TestPlatform.Extensions.BlameDataCollector.BlameCollector.SessionEndedHandler(Object sender, SessionEndEventArgs args) in /_/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/BlameCollector.cs:line 535.

Passed!  - Failed:     0, Passed:  1483, Skipped:     0, Total:  1483, Duration: 13 m 30 s - ****.Tests.dll (net9.0)
Test Run Aborted.

The active Test Run was aborted because the host process exited unexpectedly. Please inspect the call stack above, if available, to get more information about where the exception originated from.
The test running when the crash occurred:
*****

This test may, or may not be the source of the crash.

Attachments:
  /home/runner/work/****/TestResults/c17ff[93](https://github.com/******.xml
Error: The operation was canceled.

I get no dump, and seemingly no way to upload the diag log because the crash somehow results in the pipeline cancelling rather than just erroring.


Update static files of swaggerUi

The swaggerUi dependency injected in the repo looks like old. For instance, it doesn't have this commit https://github.com/swagger-api/swagger-ui/pull/2014 which solves this auth issue https://github.com/swagger-api/swagger-ui/issues/1108, useful to authenticate the calls through a Bearer token.
This pull request updates the swaggerUi folder and it also tweak the index.html in order to get the swagger doc from the header field "Swagger-API-Docs-URL".

I haven't had a chance to check the changes out to index.html to retrieve the Swagger-API-Docs-URL but did it follow the same approach we have been?  I really hate having to do this but I've no better idea.

Yes it does and I hated it too, because every time we want to update the swaggerUi dependency it is a mess! I spent a bit trying to pass the doc url in a nicer way, but the dependency serve-static doesn't help...

Agreed.  It's not pretty but without it, swagger-ui doesn't really lend itself to handling things like this itself.

I'm going to merge this after I release a new version of json-refs here in the next few days.

👍

Hi @whitlockjc, will you merge this?

Sure.  I was on vacation last week so I apologize for the slow response.

Hi @whitlockjc I was just wondering what is the status of this pull request

@whitlockjc I am sorry, but I am wondering why this PR is not merged?

Because by the time I merge it, it will be out of date.  I am holding off on updating swagger-ui until right before release time.

Ok that makes sense thank you. When do you plan to release current version to npm?

I'm not sure honestly.  I'm knee-deep in a rewrite of json-refs to fix a number of performance issues and bugs.  Once that's done, I will update sway to use it (fixing its bugs) and do the same with swagger-tools.

There's a new version of swagger-ui (v3). Wouldn't it be possible to include SwaggerUI as a dependency of swagger-tools instead of having to copy the files to this project? It would make it easier to update it to recent versions. Better yet, being able to pass a swagger-ui reference as a configuration parameter would allow the end-user to use whatever version of swagger-ui he/she wants.

Yep, already taken care of.  As for why we do it this way, we are up the details automatically so that swagger-ui can find your API and such.  It's definitely a pain having to do it this way.  I'm all ears.

Done as part of 9b5131361ec75712a6a0784b2e106d7664eb5b4f


If the client_secret is empty, don't post it at all.

Really we shouldn't be storing a client secret in an app at all, we should be using
PKCE. Some servers will reject the request if it's a "public" app and you include
the secret. Since it would be tricky to fully make it optional in the client everywhere,
I'm changing it to just ignore empty strings.
I didn't do this everywhere, as the other methods seem to assume the client/secret credentials are being used instead of pkce.

Any interest in pulling this in?

Because of conflict due to other PR I will integrate the code
thanks
But I change a little, keep the else to not change the previous behaviour

@phimage Can you publish a release that includes this? Looks like the latest release does not contain this change.


Validator Improvements Mk. II

Enhances the mapping validator with additional functionality:
Validator

Reorganizes validator classes into their own modules within the metadata_mapper package

ValidationErrors is now ValidationLog

Adds ValidationLogLevel

This enum is used to set the logging level
Options are ERROR, WARNING, INFO, DEBUG

Adds ValidationMode

An enum STRICT or LAX

STRICT is the current default behavior
LAX performs case-insensitive string comparisons and order-insensitive list comparisons

Individual validations can define their own validation_mode as either ValidationMode.STRICT or ValidationMode.LAX to override the global default.

Adds verbose option

Adds successful validation logging at the INFO level

By default, outputs a single line per record, listing the successfully-validated fields
If verbose is True, outputs a line per successfully-validated field. WARNING: This can make for very long validation files.

validate_mapping.py

Fetches isShownAt and isShownBy from CouchDB and merges it into comparison metadata
Added CLI args:

--log-level, which can be any one of ERROR, WARN, INFO, or DEBUG (case insensitive) (default: WARN)
-v --verbose to set verbose mode (default: false)
--filename to set the output file name (default: timestamp-based name)

For example:
python validate_mapping.py 12345 --log-level=INFO --verbose --filename=example.csv

will generate some console output telling you what's happening, and create a file in the env-appropriate bucket under "validation/{collection_id}/{filename}"
Lambda Shepherd

Added ability to trigger post-mapping validation by passing validate in the Lambda payload

validate can be a truthy boolean to run with default options, False to explicitly not validate, or a dict of options
The options dict can contain the same arguments as the CLI flags: log_level, verbose, and/or filename

Resolves #383
Resolves #386
Resolves #411
Resolves #412

Hey Tim! This generally looks great.
I left a few inline comments - mostly housekeeping. The biggest comment is about the usage of the word "default" - I think maybe we could find some better language for the module overall regarding the various different kinds of "defaults" there are in the module, but also some documentation write-up on module usage and module structure would likely go a long ways to address some of the confusion created by this overloading of the word "default". You've drafted some really nice PR messages for the validator work and I wonder if you could draft a Rikolti wiki update (github.com/ucldc/rikolti/wiki) with some Validator usage documentation.

Hi @amywieliczka and @barbarahui, I rebased on main and force pushed - no other changes, but it should now merge nicely.
When you're able, please re-approve and/or go ahead and merge it.
Thanks!


Bugfix for non-existing jwt keys

:tada: This PR is included in version 5.0.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Taskbar is not hidden in second monitor when using full screen app.

Describe the bug
Taskbar is not hidden in second monitor when using full screen app.
The primary monitor is not affect.
To Reproduce
Steps to reproduce the behavior:

Setup auto hide for taskbar
Run TaskbarX
Open an application with full screen mode on secondary monitor
Hover mouse to the place of taskbar

Expected behavior
Taskbar is not displayed
Screenshots

Desktop (please complete the following information):

OS: Windows 10
Version: 20H2 Build 19042.867

Additional context
N/A

I'm sorry @quyleanh but i think this is a bug in windows or the game itself.

I don't know. Because I have no issue like that before installing TaskbarX.

Can you try to turn off or uninstall TaskbarX to see if it still happens? I have been trying to reproduce it but iam unable to.

I checked. You're correct. It's seem the Windows bugs.
Could you implement feature to hide it in TaskbarX?

To be able to focus on major/current bugs I had to close all issues. The issues section has gotten very messy to a point that I couldn't follow it anymore. Most issues are duplicates, very old or are already fixed/solved. Feel free to reopen this issue if you still have this issue on the latest version of TaskbarX to get my attention. All feature requests have been put in a list here: 💡| Feature requests #870
I hope you understand ❤