Anisotropy distribution

I did not fully read the previous “anisotropy” issues (#60 and #176), but from a more recent discussion with @stggh, it seems that the means to calculate the anisotropy distribution (radially dependent anisotropy parameters) are still demanded and not really available.
So I have a proof of concept implementing several approaches that seem reasonable for fast calculations. They all seem to work, with somewhat different properties:
For the simple image with separate peaks (1 quadrant):

For the Dribinski sample image:

The implemented methods are:

nearest bins image pixels to the nearest radial bin.
linear bins image pixels, distributing them over the 2 closest radial bins with linear weights.
remap converts the image to a uniform polar grid (like reproject_image_into_polar).

Except these differences, they all do linear least-squares fitting to cosl θ terms, then convert them to Legendre polynomial and finally to the intensity and anisotropy parameters.
Some of this stuff does not depend on the image data and can be cached, some needs to be done with the image.

nearest has the fastest non-cacheable part (~50 ms on my system for 1 quadrant of a megapixel image), seems to be the least biased, but the noisiest.
linear is about twice slower, less noisier, but produces somehow biased β in very-low-intensity parts.
remap has the best total time, but a slightly worse throughput (non-cacheable) than nearest, has the lowest noise on the peaks, but behaves crazily in very-low-intensity parts.

So it all seems to work in principle, but needs some improvements before adding to PyAbel:

Now it works with 1 quadrant only. This should be extended to full and half (?) images. Maybe by automatic folding (fast, but limited), maybe by actually going through all the supplied data. What do other polar/vmi tools expect in this regard?
It probably should be integrated deeply with the available tools. On the one hand, remap relies on the same thing as reproject_image_into_polar, but cannot reuse it directly. On the other hand, angular_integration and anisotropy_parameter can be reimplemented as particular simplified cases of these anisotropy-distribution calculations.
The sin θ weighting should be added (optional, used by default?).
Specifying the radial range (possibly beyond clipping) would be useful.
Specifying the radial step could be useful? Or not really? (This has potential problems of having less pixels than parameters.)
It can be relatively easily extend to arbitrary orders. Maybe, including odd orders (unlike the even-orders decomposition, they are not strict, but still useful for alignment studies).
(Optionally) clip the β values to their meaningful ranges?
Consider the caching API. It can be made like in the transform methods, but here we do not have a separate module.

Any comments, suggestions, concerns, considerations?

Ah, I think, there must be currently missing sothething-π factor (4π or 4/3 π or something else) for the intensity. And maybe a different r scaling.

@MikhailRyazanov this is very neat and very clever. Thanks!

abel.tools.vmi operates on an individual quadrant (vertically flipped from your implementation), or the whole image, depending on the image origin parameter.
The intensity variation for photoelectron images is σ/4π [ 1 + βP2(cosθ)]. There is no sinθ term.
and 7.  The common technique is to plot/present  I * beta to hide the low signal issues = bad β values.

Still playing ...

@stggh,
2. |sin θ| should be the weight in the fitting procedure (weighted least squares), since there is proportionally less signal near the axis. The fitting function is, of course, the same as you wrote.
7. I * beta is the 2nd spherical harmonic, which by itself does not tell much about the anisotropy. It can be meaningful if plotted together with I (the 0th harmonic) for comparison, but then plotting the cos² and sin² parts probably makes more sense (they both are at least positive and directly correspond to the “parallel” and “perpendicular” components).

The main thing about computations that I actually wanted to ask:
Let's say, I have the 2D image array IM with pixel values and an array bin of the same dimensions, which contains integers indicating to which radial bin (1D) each pixel corresponds. So I need to bin the images pixels like this:
res = np.array(...)
for i in range(height):
  for j in range(width):
    b = bin[i, j]
    res[b] += IM[i, j]

(notice the += operator — there are many pixels that must be summed into a bin).
This code is very slow, since it runs in the Python interpreter. Is there a fast way to perform this kind of operation in numpy/scipy/whatever?
(Currently I'm doing this backwards by precomputing lists of image pixel indices corresponding to each bin and then iterating over the bins and using IM[indices[b]].sum(). It is faster than the loops above, but looks like a wrong way.)

Isn't the/your remap method the answer?

The idea is that nearest and linear use each image pixel exactly once. remap distorts and interpolates the data. And scipy.ndimage.map_coordinates cannot add pixel values.
However, I've found the solutions myself:

scipy.ndimage.sum is designed do this kind of binning.
But also numpy.bincount can be used as numpy.bincount(bin.reshape(-1), IM.reshape(-1)), with the image pixels as weights... Might appear unusual, but this is actually the fastest method.

The updated version works much faster and is much simpler, as expected. nearest now can process megapixel images in just 4 ms!
And the intensity indeed should be 4π r2 P0.
The Dribinski example again:

Looks pretty much as in the article.

@DanHickstein, there is a mistake in abel.tools.analytical.SampleImage._dribinski():
t9 = 20*_gauss(r, 45, 3600)  # background under t3 to t5

must be
t9 = 20*_gauss(r, 45, 60)  # background under t3 to t5

(the last parameter is squared inside _gauss()).
Can you please correct it directly in the master branch? I don't think that we need a PR for this...

This looks good. Here is the `O2-ANU1024.txt.bz2' test case:

code gist  (lacks comments)
You are right, there is a case for filtering the β values.

When β varies across the peak, it might be an indication of some image distortions or imperfect centering (I had some experience ;–) with this), unless there is a good physical reason. And if it is not expected to vary, then getting it from intensity components radially integrated over the peak is the most proper way.
However, the strange thing in your plot is that linbasex and image fitting yield opposite trends.

strange thing in your plot is that linbasex and image fitting yield opposite trends.

This represents the noise, and perhaps, a displacement between the transform methods.  Extending the radial-range around each peak (± 2Γ) is more illustrative.  Some β smoothing required.

linbasex has a smoothing parameter (> 1 pixel). For smoothing=2:

I should add that any smoothing (> 1 pixel) degrades the structure in the (my) radial intensity spectrum, so for linbasex the two cannot be used/compared together.

Wow! This looks super awesome! Thanks Mikhail!

Now it works with 1 quadrant only. This should be extended to full and half (?) images. Maybe by automatic folding (fast, but limited), maybe by actually going through all the supplied data. What do other polar/vmi tools expect in this regard?

As @stggh mentions, the other tools can set the origin arbitrarily, so can work with either the whole image or a quadrant. But, the sort of assume the full image. I don't think that we have good precedent either way, and would welcome a good suggestion on how to handle this.

It probably should be integrated deeply with the available tools. On the one hand, remap relies on the same thing as reproject_image_into_polar, but cannot reuse it directly. On the other hand, angular_integration and anisotropy_parameter can be reimplemented as particular simplified cases of these anisotropy-distribution calculations.

Yes, we should integrate it as well as possible. But, the angular integration function is currently reasonably fast, so if this method is significant slower (it's probably not, but we should check), we may want to retain both methods.

Specifying the radial range (possibly beyond clipping) would be useful.

Agreed.

Specifying the radial step could be useful? Or not really? (This has potential problems of having less pixels than parameters.)

I would probably allow the radial step to be specified, with a good description in the docstring that it's probably not a good idea to set it too much below it's default value of 1 pixel.

It can be relatively easily extend to arbitrary orders. Maybe, including odd orders (unlike the even-orders decomposition, they are not strict, but still useful for alignment studies).

Interesting! That sounds useful for some people.

(Optionally) clip the β values to their meaningful ranges?

Yeah, we can either add a functionality to do this, or (easier) include an example in the docstring showing people how to set the beta values to np.nan for ranges where the intensity is low.

Consider the caching API. It can be made like in the transform methods, but here we do not have a separate module.

I don't understand this comment - what are you trying to cache?

Can you please correct it directly in the master branch? I don't think that we need a PR for this...

I think that all changes to the code should be accompanied by a PR. Then, we can always look back and see when a change occurred and (if we are doing our job right) why it occurred. Also, you found the bug, so you should get credit for fixing it.

@DanHickstein, thanks!
1. Now I have the folding working, need to test whether it is faster than just going over the whole image. But yes, specifying an arbitrary origin works and is the universal way.
8. The calculations involve some parts that do not depend on the actual image (if you look at the printout from the example, these are the lines that do not have “IMG”), so they can be stored and reused for repetitive analysis of multiple images (just like the transform methods now cache the transform matrices).  In some cases this increases the throughput significantly.
I am currently thinking about making this an object, which will store the parameters (and all precalculations), then you can feed it with images and get any desired distributions. But maybe several separate functions will be enough.
6. Even orders are in progress.
When I'm done with this, I plan to make a PR. And leave 5., 7., and odd orders from 6. for the next iteration(s).

Can you please correct it directly in the master branch? I don't think that we need a PR for this...

I think that all changes to the code should be accompanied by a PR. Then, we can always look back and see when a change occurred and (if we are doing our job right) why it occurred. Also, you found the bug, so you should get credit for fixing it.

OK, then I'll prepare it soon...

Well, since most of the ideas here are implemented in #257 and #266, I'm closing this issue.
The remaining possible improvements are the adjustable radial step and clipping the β values. If somebody really needs them, it would be better to open separate issues.


recommended config should configure plugin

Hi,
Some very nice rules! I'm hoping to introduce this plugin in our corporate projects soon.
One suggestion though:
Currently, we have to configure "plugins": ["proper-tests"] manually in order to use the recommended config as "extends": ["plugin:proper-tests/recommended"] (as documented in the README) .
However, if the config would include that line itself, this wouldn't be necessary making the consumption easier.
Including it seems to be common practice and is done by most other plugins we use.
Examples:

https://github.com/jest-community/eslint-plugin-jest/blob/3888beea7b0db48e017d3e696fca8b8aef988dea/src/index.ts#L90
https://github.com/typescript-eslint/typescript-eslint/blob/3f02687d964c1e7888e5db62256d56cd72c4f281/packages/eslint-plugin/src/configs/base.ts#L6

Cheers,
Steffen

Thank you for your interest and kind words!
Looking forward to see how it works for your projects. If you have other ideas, feel free to file an issue with suggestions or even make a PR.
Regarding this recommendation - cool, implemented. I will create a new release soon.

Released as 1.0.10


Differentiate sync and async calls in OpenSearchVectorClient

Description
Separate sync and async clients in OpenSearchVectorClient to improve method flexibility, and adapted tests to reflect these changes. I took inspiration from the LangChain's OpenSearchVectorSearch implementation.
I also added a parameter to customize the index creation. This is given through the settings parameter. The default value (if it is left None) is the same as before.
Solves #15922
Fixes https://github.com/run-llama/llama_index/issues/15955
New Package?
Did I fill in the tool.llamahub section in the pyproject.toml and provide a detailed README.md for my new integration or package?

[ ] Yes
[x] No

Version Bump?
Did I bump the version in the pyproject.toml file of the package I am updating? (Except for the llama-index-core package)

[x] Yes
[ ] No

Type of Change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Added new unit/integration tests
[ ] Added new notebook (that tests end-to-end)
[ ] I stared at the code and made sure it makes sense

Suggested Checklist:

[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added Google Colab support for the newly added notebooks.
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] I ran make format; make lint to appease the lint gods

Works! Amazing work @kobiche thanks a ton!


VNC support

Tart supports launching a VM with no GUI but a working VNC server (--vnc and --vnc-experimental). While disabling GUI is supported in this plugin, it misses the VNC options.
Adding support for these params seems pretty straightforward, so I'd be happy to do it, if you accept PRs and publish a new version when they are merged.

I have merge the support for VNC option. The new Gem has been published.

Awesome, thank you for your hard work!


Register version 0.4.8

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/79768
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.4.8 -m "<description of version>" b4aa775315ee82244238c5c4b858004c0c6f97b6
git push origin v0.4.8


fix(Relationship): do not set static_record_type for polymorphic relationships

What is the current behavior?
Specifying :polymorphic on a belongs_to relationship gives a static record_type.
What is the new behavior?
Polymorphic relationships do not set a static record_type.  This allows a lookup of each record type.
Checklist
Please make sure the following requirements are complete:

[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been reviewed and added / updated if needed (for bug fixes /
features)
[x] All automated checks pass (CI/CD)

@kpheasey could you provide a test case please?

@kpheasey please start adding tests to the PRs, this is just not nice!!!

@stas I was moving too quickly this morning and thought I included them.
https://github.com/fast-jsonapi/fast_jsonapi/pull/85
I'll even let you merge that one.


Updated & fixed documentation a bit

I made the install instructions a bit more clear, and fixed a dead link.
Also the titles in some of the component docs were mildly annoying, so I standardised those too. (e.g. "BottomNavigationAction" -> "Bottom Navigation Action")
I hope this is helpful to the project, it would have certainly saved me a few minutes of navigating around.

Codecov Report

Merging #244 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #244   +/-   ##
=======================================
  Coverage   76.61%   76.61%
=======================================
  Files          19       19
  Lines         774      774
  Branches      113      113
=======================================
  Hits          593      593
  Misses        150      150
  Partials       31       31


Ecurrencyhodler patch 1

Pull Request checklist
Please review the below PR requirements:

Build was run locally and any changes were pushed
Ensure that the title clearly describes the changes
Issue to be referenced in the PR description rather than in the commits or PR title
Clean commit history

Sorry I was just experimenting. Please ignore.


Redo of Index/Filter/Data blocks sizes in Block (LRU) Block Cache per CF after rebase on RocksDB 8.1 (#516)

The original issue is: https://github.com/speedb-io/speedb/issues/338

plz also update the HISTORY.md file

plz also update the HISTORY.md file

OK.

@Yuval-Ariel - Are you done with the review?

Member

Done

Rebased on latest origin/main and squashed to prepare for the merge

checking licence and history


nodejs: attach-maps: Build on older Ubuntu version

We use ubuntu:20.04, see
https://github.com/Granulate/gprofiler/blob/914e05081bf90f96059f1a3b5995dec71b334b7c/Dockerfile#L26
This means the lib is compiled against new libstdc++ and glibc and will not necessary load on older systems (e.g on a system/container based on Ubuntu 16.04).
Logically, this is the same problem as we have with async-profiler - we build it on CentOS 7 and do many "shenanigans" to have it load on systems as old as CentOS 6. NodeJS is more modern so I don't think we need to support that old system. I suppose getting the build to work on 14.04 is good enough.
We can also add a test that verifies it, or at the very least, test manually on an Ubuntu 14.04 container where NodeJS was installed. If we try to attach-maps such container now, it will fail with an error like Error: /lib64/libstdc++.so.6: version CXXABI_1.3.9 not found (required by /tmp/gprofiler_tmp/node_module/20eb88a/glibc/10/build/Release/linux-perf.node).

Let's also make sure it supports CentOS 7 (glibc 2.17 libstdc++ 3.4.19)


docs($http): expand caching section to cover FAQ

add note that only GET & JSONP requests are cached
add note that cache keys are the url and search params (headers not considered)
add note that cache-control header on response does not affect angular caching
add note that $httpProvider.defaults.cache can be used to set cache default (in addition to $http.defaults.cache)
expand note on how default cache property affects requests with cache set to true

Fixes #11101

@gkalpak, I fixed the spelling error and also uppercased 'URL' to be consistent with the rest of the comments. I also added Fixes #11101 to the commit comment.

@gkalpak, you are correct: a default cache value of false can be overridden by a cache config value of true as well as a custom cache object, so I will update.
This means that rows 260-263 of the file (describing the defaults object) are also incorrect, so I will include a revision of these in my commit as well.
There is also no mention of the effect of setting the default cache to true (it results in the $http cache being used when the config cache is undefined), so I will expand my comments to include this.
I set up this [plunker] (http://plnkr.co/edit/QuHeEzUYLmyKNxuIjMUh?p=preview) to test the various combinations.

@ryanhart2 Did you ever update this PR?

@Narretz Apologies, I didn't and had forgotten about it. I will have a look this weekend and try to get it done.

Am 21.01.2016 um 15:04 schrieb Ryan Hart:

@Narretz https://github.com/Narretz Apologies, I didn't and had
forgotten about it. I will have a look this weekend and try to get it
done.
—
Reply to this email directly or view it on GitHub
https://github.com/angular/angular.js/pull/13003#issuecomment-173577789.

No problem. I just wouldn't want to see good work go to waste!

@ryanhart2 why did you close it?

@Narretz Just struggling to do the rebase... I think I am getting there!

@Narretz , @gkalpak I have updated this pull request to more accurately describe how http caching works. Appreciate if you have time to review and provide feedback. Thanks.

I left a couple of comments (actually it's the same comment twice :stuck_out_tongue: ).
BTW, @ryanhart2, you don't need to rebase. (In fact it's preferrable to just push a new commit with the changes :smiley:)

Thanks @gkalpak. I agree, the revised version now reads better. Thanks for the hint on the rebase. I have pushed a new commit addressing your suggestions. Note that, on the same lines, I also updated the words "enable caching" to "enable or disable caching", given that the values could be false.

Backported to v1.5.x (2a7d4c1) and v1.4.x (b9d3625).
Thx @ryanhart2 for working on this !


Add application submission id everywhere, with an optional prefix

This PR allow adding an option prefix to the submission ID's that are auto generated.
The prefix can be added by going to round or lab settings page.
This PR also ensure the prefix or application ID displayed along with title almost everywhere for each reference. Since the title of application is not unique, this helps add uniqueness to it.
The autolinking of submission ids in communication has be updated to account for application id prefix
Fixes https://github.com/HyphaApp/hypha/issues/3830

Test Steps

[ ] general checks across the site
[ ] check notification generate - slack, email, etc.

@theskumar I think this needs rebuild migrations and a rebase. Merged in a number of PRs today.

Super small issue from my testing with the slack comment notif but otherwise works great!


Cannot run any zeta command

Currently, the doc says we can run the command zeta on the command line after having installed zetapush. However, since the CLI module is not installed as a global module, the command fails.
$ zeta run --serve-front
zeta: command not found

Hi!
According to the documentation, 6.1. From your terminal
npm run start is a script alias defined in the package.json file. The executed command under the hood is:

Solution 1
Use aliases command npm run start  and npm run deploy.
Solution 2
Update your PATH
export PATH=./node_modules/.bin:$PATH

Solution 3
Use npx tool (shipped with npm standard install)
npx zeta <command>


Add a file header comment

@piotr-oles As suggested in this comment, together with @Seb-figment we're splitting the code from #10 into 3 separate pull requests:

file header comment (this PR)
helper methods for encoding and decoding (coming soon)
proto dependencies (the rest of #10)

Please let us know if this works for you.

@piotr-oles I'm working on another PR which will add helper methods for encoding and decoding. Do we want that as a default behavior too or should I add a compiler option for it?

For this one please add an option :)


Bug: ng eject --prod fails for project with static assets

The StaticAssetPlugin is not imported properly in the webpack config when ejecting from a CLI project that uses it.
ng eject in angular/angular's aio/ for example fails to produce a webpack config that will build.

Closing this as obsolete.


Allow using MacroDeck variables in WriteScript Actions

This provides the ability to use variables in WriteScript Actions (implementing https://github.com/jbcarreon123/MacroDeck2-AHKPlugin/issues/9)
It uses an obsolete method, however I hope this gets sorted out in the future: https://github.com/Macro-Deck-org/Macro-Deck/issues/299.

I did test the WriteScriptAction but not the WriteScriptv2Action.

I updated it to use MacroDeck's Cottle Rendering.
This way it's possible to use the full power of Cottle as well ;)

It works also in v2. Will modify some of it and will update the plugin!


[Regression] drogon::getVersion() compilation failed

Notice
If you need support or clarification regarding the usage of Drogon in your project, visit the official Drogon support channel at gitter
Please create a new issue only if you think you have found a bug or if have a feature request/enhancement.
Describe the bug
error LNK2001: unresolved external symbol class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > __cdecl drogon::getVersion(void)" (?getVersion@drogon@@YA?AV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@XZ)
To Reproduce
Steps to reproduce the behavior:

Install drogon 1.7.5 with vcpkg.json
compile the following code:

#include <drogon/drogon.h>

int main() {
    LOG_INFO << drogon::getVersion();
    return 0;
}

Expected behavior
Program will compile
Desktop (please complete the following information):

OS: Windows 11 21H2 22000.556
Browser N/A

Additional context
Compiler: MSVC 19.31.31104

I just started using the library and am experiencing a similar issue.
I've downloaded drogon 1.7.5 via vcpkg. I've followed the windows installation instructions. I setup a project using dragon_ctl. I'm using VS2019 with C++ 20
I'm getting a linker error when calling into certain functions like drogon::getVersion() or HttpResponse::getBody()
Error	LNK2019	unresolved external symbol "class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > __cdecl drogon::getVersion(void)" (?getVersion@drogon@@YA?AV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@XZ) referenced in function main

I've also tried using C++14 and boost and got the same linker error.
I have added the following to the path environment variables: vcpkg\installed\x64-windows\bin, lib and include
OS: Windows 10 10.0.19043
Visual Studio 2019 v16.11.7
MSVC 14.29.30133

the DROGON_EXPORT macro is missed with the getVersion function, I'll fix this issue by adding the macro.

Thank you for the prompt response and fix.
Any idea about the linker error with HttpResponse::getBody()?
Error	LNK2019	unresolved external symbol "__declspec(dllimport) public: class boost::basic_string_view<char,struct std::char_traits<char> > __cdecl drogon::HttpResponse::getBody(void)const " (__imp_?getBody@HttpResponse@drogon@@QEBA?AV?$basic_string_view@DU?$char_traits@D@std@@@boost@@XZ) referenced in function main

This seems to be a problem only when compiling with C++ 14 and boost. I don't see this error when using C++20. However my main project is stuck on C++14 for now.

Thank you for the prompt response and fix. Any idea about the linker error with HttpResponse::getBody()?
Error	LNK2019	unresolved external symbol "__declspec(dllimport) public: class boost::basic_string_view<char,struct std::char_traits<char> > __cdecl drogon::HttpResponse::getBody(void)const " (__imp_?getBody@HttpResponse@drogon@@QEBA?AV?$basic_string_view@DU?$char_traits@D@std@@@boost@@XZ) referenced in function main

This seems to be a problem only when compiling with C++ 14 and boost. I don't see this error when using C++20. However my main project is stuck on C++14 for now.

C++ 14 was checked in github CI actions. Try to clean your build folder and re-cmake, rebuild every thing.


[BUG] eks-operator | Clusters with the same display name can't be imported

Rancher Server Setup

Rancher version: v2.7.1
Installation option (Docker install/Helm Chart):
Helm Chart on existing EKS cluster

Information about the Cluster

Kubernetes version: v1.21.14-eks-48e63af
Cluster Type: Imported EKS cluster

User Information

Admin

Describe the bug

Can't import more then 1 EKS cluster with the display name, although those cluster exists in different accounts/regions
To Reproduce

Import an EKS cluster nemed <my_eks_cluster>
Import another EKS cluster from different region  / account named my_eks_cluster

Result
The first cluster is successfully imported, but the second cluster fails with the following error:
Cannot create cluster [my_eks_cluster] because an eksclusterconfig exists with the same name

Expected Result

The second cluster will be imported successfully
Additional context
I don't see why this should be failing as the EKS can repeat itself in different accounts/regions.
I think that it'll be more reasonable to check the Name field as it represents the cluster name inside Rancher and it should be unique.
Thie validation occurs here:
https://github.com/rancher/eks-operator/blob/cfda1338ab33752feb903838e087e4c94f81e316/controller/eks-cluster-config-handler.go#L464
What is the logic behind this validation?

Ran into this as well but managed to find a workaround: change spec.eksConfig.displayName to something that doesn't exist (you'll get a new error about the cluster not existing), then change it back.

Nice @hall.. I've ran a local eks-operator and i removed this check from the code, added the cluster,  then ran the cluster eks-operator again.. Still, i think that this should be solved

Guys, where exactly did you solve it, on the rancher? I'm having the same error but I don't know where to fix it

Guys, where exactly did you solve it, on the rancher? I'm having the same error but I don't know where to fix it

I'm having the same error. i use this way to avoid this error
## edit the ekscc change the displayName to something that doesn't exist  then change it back.
kubectl edit  ekscc c-dffcn -n cattle-global-data

well, for me it worked as follows:
I tried to add a cluster, but I received this error, I noticed that it gave a command that should be executed within the cluster, I executed it and it worked.
Of course, your entire infrastructure connection (if you have one, it has to be ok too, probably if you already have other clusters added you can ignore this addendum)


wow, very easter

Easter bunni!
Added python-dateutil as a dependency to perform Easter calculations.

Seems that the Arch Linux's package doesn't properly include the python-dateutil package as a dependency. Had to manually install it to get things to work.

Created an issue here:
https://github.com/Olivia5k/doge/issues/76


Add a workflow to automatically add issues and PRs to my maintenance GH project

I have created a GitHub project board here to track all issues and PRs across all of the repositories I maintain:
https://github.com/orgs/RMI-PACTA/projects/12
This PR adds a workflow that automatically adds issues and PRs to that project.
Adapted from @cjyetman's action.
FYI @RMI-PACTA/developers in case you find this useful or interesting. Ping me if you would like an explanation of this.

I will likely do exactly the same for the repos I maintain, as well as (maybe) maintain the board I have used in the past for all TM related repos.

I will likely do exactly the same for the repos I maintain, as well as (maybe) maintain the board I have used in the past for all TM related repos.

Then we can trade PR review spamming 😂

@cjyetman last one :-)

Looks interesting. I want it too.

I can show you how to do it, but you're gonna have to set it up yourself ;-) hahaha


Microsoft Teams in WSL2 installed successfully but not opened.

Windows Build Number
Microsoft Windows [Version 10.0.21390.2025]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
5.10.16
Distro Version
Ubuntu 20.04
Other Software
No response
Repro Steps
I have all default configuration.
Expected Behavior
Opening teams startup window.
Actual Behavior
Not showing any kinds behavior or error messages.
Diagnostic Logs
No response

Are you using WSLg?

Are you using WSLg?

no.

WSLg is required to use GUI apps.
Please see https://github.com/microsoft/wslg.

WSLg is required to use GUI apps.
Please see https://github.com/microsoft/wslg.

after installation WSLg gedit is working but not teams .


feat: add Ukrainian language support

Thanks again for adding these translations, and for making this library better :) Feel free to contribute again anytime
I'll try and add a release tomorrow


No clusters or pins displayed when zoomed out

Issue: when viewing clusters over the international dateline clusters and pins disappear. This issue can be recreated with the following steps:

Add annotations which cluster across the world.
Move the mapview over the international date line (see images below). If the user moves over the dateline and reloads new annotations, no clusters are displayed.

To recreate the issue I have attached a test project:
Three buttons have been created to show the problem:
Button:
"Data Loads Correctly": Positions the map to an area which will load the data correctly. After tapping this button tap "Load Data" to show the clusters appearing.
"All Data Does Not Load": positions the map to show the data not loading correctly. After tapping this button tap "Load Data" to show all clusters not appearing.
Tapping Load Data will load the data once the map is positioned (regardless of where you position).
kingpin-test.zip

@smahmoodpbm
thanks for reporting this!
I was able to reproduce this issue using your test project. The problem was in annotation tree that was not recognizing MKMapRect spanned over international dateline. Quick fix I have made just checks for this case and splits spanning map rect into two parts.
Before fixing it in actual kingpin I want to know if my fix solves your original issue.
https://github.com/stanislaw/Examples/tree/20160210-kingpin-international-dateline

Thanks Stainislaw,  great work! The changes do help it looks like the pins now appear however I noticed the clustering count value seems to be off (this may be related to state of the fix). For example taking a look at north america counts vs. counts you get when positioning over the date line.
Thanks for helping!

Maybe I am missing something on your screenshots but looks like it is expected behavior of kingpin -- when you press "Load Data" multiple times on the same screen (without moving/zooming it) you will always have the same clusters (positions and counts).
But when you start doing small adjustments for kingpin clustering algorithm it means change of base point from which cluster grid is calculated (it is specific drawback of grid clustering algorithm).
Real kingpin partially solves this visual inconsistency of changes in clusters positions by using normalization - every time you do panning (left-right-top-down without zooming) kingpin always uses base point from invisible grid of cluster size (one which is set using algorithm.annotationSize = CGSizeMake(50, 50)) that's why it doesn't look like recalculation from scratch every time.
In this application with "Load Data" you recreate annotation from scratch every time that's why you see those fluctuations as it is base point for algorithm computation that changes.
I believe this sounds obscure, let me know if it somehow clarifies your confusion :)

I may have caused the confusion by putting together the image and not adding enough detail.
In total for the test project there are 115 annotations, which appear correctly if you load data from North America (not over the dateline).  However if you load data from the dateline the counts for the clusters are about 390 annotations.
The counts for the number of annotations look to double or triple up when you are over the international date line and are correct when you are not over the date line.
Im looking into this more but annotationsInMapRect may be returning the same annotations for both the left and right annotation.
[annotationsLeft arrayByAddingObjectsFromArray:annotationsRight]

@smahmoodpbm thanks for reviewing this thoroughly. Indeed it was my quick fix based on what Kent Beck calls Obvious Implementation :)
Now I have made it correct to handle remaining edge cases.
Try the latest branch: 20160210-kingpin-international-dateline.

If everything is fine, I'll add this proper implementation with tests to kingpin here.

@stanislaw Thanks!! Everything looks good to add to the proper implementation.

@smahmoodpbm, I have just released 0.3.2 having this fix.


preg_match_all fails with concatenated string

Bug Report

[ x] Yes, I reviewed the contribution guidelines.
[ x] Yes, more specifically, I reviewed the guidelines on how to write clear bug reports.

A string in wp-config.php like this:
define( 'WP_HOME', 'https://'.$_SERVER['HTTP_HOST'] );

Is not properly match in parse_wp_config() and ends up swallowing additional line(s).
The quick fix (for me) was to change to:
define( 'WP_HOME', "https://{$_SERVER['HTTP_HOST']}" );

But that doesn't change things in the wild.
You can see this by pasting the line in the regex101 before the /* That's all, stop editing! Happy blogging. */ line.

Thanks for the report, @KBurkholder !
Feel free to submit a pull request, if you'd like. Here is some guidance on our pull request best practices.

@danielbachhuber I've been playing around with updating the RegEx rules over here at https://regex101.com/r/ArEndA/1. It seems like I've managed to get it working in this scenario, but I've been unsuccessful trying to implement it in the source code. I'm unfamiliar with how the tests work here, especially since it seems like they're dynamically generating the file fixtures. 🤔
Speaking of which, have we considered to parse it into AST with something like nikic/PHP-Parser? It may be more reliable than using RegEx to cover more scenarios.


fix: Clarify setup guide

Is there an existing issue for this?

[X] I have searched the existing issues.

Version
alchemist: ^0.3.3
Description
Hi, great package, solves an important problem! However, I am not sure two aspects are clear.

The setup guide suggests checking for environment variables in a different fashion the what is used in the example. For me, only the example way works, perhaps it's worth it update it?

I am not sure I understand how you are handling the platform tests across developers. Since platform goldens are not tracked in CI, what happens when someone adds a new test? Wouldn't I have to first always run flutter test --update-goldens on my local machine?

Steps to reproduce

Expected behavior
The setup guide, especially in terms of handling the platform tests, should be clear.
Screenshots
No response
Additional context and comments
No response

Hi there,
Thanks for opening up an issue! You raise some great points.
1)
The recommended setup guide is used to illustrate how we used Alchemist in our workflow. The example could use a similar configuration to determine whether it's being executed on CI or otherwise. This part has been left out of the example for both simplicity's sake and since the example (currently) isn't being tested.
If you think it'd be valuable to add this environment mechanic to the example, I'm open to revising this :)
2)
Correct, I've recently noticed the same things. Since platform goldens are generally not tracked in source control, Flutter will throw an error when trying to run goldens on any fresh copy of a repo on a local machine.
We have a couple options to accommodate for this. One is to add better documentation around this mechanic to make sure new users are aware of this discrepancy.
Another interesting proposal would be to add a generateMissingPlatformGoldens flag to AlchemistConfig (or generateMissingGoldens on PlatformGoldensConfig) that, when enabled, makes sure missing platform golden files are generated and their checks passed automatically.
Pinging @Kirpal and @definitelyokay for their opinion on this, especially the second point.

I like that idea! I lean towards having generateMissingGoldens as a parameter on the abstract GoldensConfig class, so it could be applied to the CiGoldensConfig as well, just in case someone wanted that.


Closes #527 | Add Dataloader MDIA

Closes #527
I implemented one config per language/subset. Thus, configs will look like this: mdia_ind_dialogue_source, mdia_tgl_eng_seacrowd_t2t, etc. When testing, pass mdia_<subset> to the --subset_id parameter.
Note: this dataset can be used for two tasks and both use the same t2t schema with different implementation.
Checkbox

[x] Confirm that this PR is linked to the dataset issue.
[x] Create the dataloader script seacrowd/sea_datasets/my_dataset/my_dataset.py (please use only lowercase and underscore for dataset naming).
[x] Provide values for the _CITATION, _DATASETNAME, _DESCRIPTION, _HOMEPAGE, _LICENSE, _URLs, _SUPPORTED_TASKS, _SOURCE_VERSION, and _SEACROWD_VERSION variables.
[x] Implement _info(), _split_generators() and _generate_examples() in dataloader script.
[x] Make sure that the BUILDER_CONFIGS class attribute is a list with at least one SEACrowdConfig for the source schema and one for a seacrowd schema.
[x] Confirm dataloader script works with datasets.load_dataset function.
[x] Confirm that your dataloader script passes the test suite run with python -m tests.test_seacrowd seacrowd/sea_datasets/<my_dataset>/<my_dataset>.py.
[ ] If my dataset is local, I have provided an output of the unit-tests in the PR (please copy paste). This is OPTIONAL for public datasets, as we can test these without access to the data files.

@MJonibek @danjohnvelasco Done reformatting!

I'm merging this since both @MJonibek and @danjohnvelasco's reviews have been addressed. Thank you so much for your work, @akhdanfadh!! 👍


add Pod Manager References

Just to clarify where the name came from. We also now manage
volumes so add that to the description.
Signed-off-by: Daniel J Walsh<EMAIL_ADDRESS>

Could someone give this a /lgtm

/lgtm


Protocol documentation?

I don't use Hubitat but am interested in creating an integration with ioBroker for HikVision events and stumbled across your code.
Am curious if you have any doco for this protocol that would be useful is all?
Thanks :)

Hi.. It's a bit of trial-and-error and reading through Hikvision's ISAPI document, which you should be able to find by just Googling.
The camera is set-up to send events to the Hubitat, which is passively receiving a stream of data from the camera. What I get is just a bunch of data in XML that I parse through.
There is a way to interact with the camera API with a PUT, but due to limitations of Hubitat (or maybe my abilities -- I'm not very experienced in SW dev), I'm stuck with the above integration.
There's some discussion here: https://ipcamtalk.com/threads/figuring-out-hikvision-api-isapi.43619/
I hope that's somewhat useful. Sorry if not.

Now I'm confused - not hard to do :wink:
I know about ISAPI and have the doco. But I thought ISAPI is for incoming connections to the camera only. Is that not the case?
I mean, you say the server is, "...passively receiving a stream of data from the camera." which implies one needs a server listening for connections, handling requests and sending an appropriate response so the camera thinks the alarm server is working.
I actually tried starting a dummy HTTP server on a host here and configured that host/port in the alarm server screen but looked like my camera (DS-2CD2143G2) was just making a connection but then never sent a request. Or any data at all after the socket connection which is very odd. Guess it's possible I messed something up in the logging :thinking:
Don't suppose you have a packet capture of your camera sending events and the responses necessary or anything like that?

Sorry... maybe some context is missing here. The intended usage for this driver code is described on the Hubitat forums:

Basically, the cameras are configured to simply send data to a "HTTP Listening" server by specifying a destination IP and port. Then events (motion, line crossing, etc.) are linked to the "Notify Surveillance Center" under "linkage method" which will trigger the camera to send data to the specified IP/port. No response from the listening server is expected.

Ah, OK, thanks for that. It's a bit odd how there is no kind of handshake or whatever with this server, but guess for me it's easier to implement an integration into our system.
FWIW, because the camera is so 'dumb' you can just fire up netcat and look at the data it's sending. With this I get:
Content-Type: application/xml; charset="UTF-8"
Host: <IP_ADDRESS>
Connection: Keep-Alive
Content-Length: 744

<?xml version="1.0" encoding="UTF-8"?>
<EventNotificationAlert version="1.0" xmlns="urn:psialliance-org">
<ipAddress>x.x.x.x</ipAddress>
<protocol>HTTP</protocol>
<macAddress>44:a6:42:xx:xx:xx</macAddress>
<channelID>1</channelID>
<dateTime>2022-01-19T09:31:00+01:00</dateTime>
<activePostCount>1</activePostCount>
<eventType>VMD</eventType>
<eventState>active</eventState>
<eventDescription>Motion alarm</eventDescription>
<channelName>Camera 01</channelName>
<Extensions version="1.0" xmlns="urn:psialliance-org">
<serialNumber>DS-2CD2143G2-xxxxxxxxxxxxxxxxxxxxxx</serialNumber>
<eventPush>VMD&&DS-2CD2143G2-xxxxxxxxxxxxxxxxxxxxxx,2022-01-19T09:31:00+01:00,1,1.0</eventPush>
</Extensions>
</EventNotificationAlert>

So yeah. Just parse the post request without issuing a response and job done. Cheers :smile:


WIP Generate schema from config

ddev validate config --schema
TODO:

required fields
better list/dict support
way to validate automatically?

Closing for now, not matching exactly what we need to do.


Development environment

Hi, I guess this is still in early development and is not supposed to be tried by others.
Anyway, I need to ask: to try this what environment is needed? Would Julia nightly (through juliaup) work? In Linux? And what about the dependencies, are they from main/master branches?
I'm really looking forward for this package to be officially released!
Thanks!

Yes. This package is still in a proof-of-concept stage.
I'm targeting Julia 1.12/LLVM 18, but at the moment the package can only work with Julia 1.12/LLVM 17 on aarch64 macOS.
As I'm only working on this package a couple of hours per week, so you might need to wait a bit longer until October.


Prepared vertex_ai_managed_notebooks_runtime for inclusion in C.G.C documentation

Intending to use this snippet on the following page:
https://cloud.google.com/vertex-ai/docs/workbench/user-managed/create-new

Test failure seems unrelated


SUMMARIZATION: WHY DOES THIS WORK

bike %>% select(length) %>% mean()
I thought it could only work on vectors 😾

I could not reproduce this. My guess is that select was being superseded by something else?


Virtual Layers

Support higher layers than are defined in a map file, so that we can overlay entities or other graphics above everything on the map.

Should be working as of f047bbd747b29ee8667dfef2bdf5c6d9e5c47d7b using the new_layer function in tilemap.


Add agreement-related audit events

We need audit events to track creating, updating, signing, and countersigning an agreement.

👍


Some formula entry impractical in ui2

Right now when entering a formula, if you want to change from permutations(n,3) to combinations(n,3) (say), and you do this by deleting permut character-by-character and then typing combin, you get an error dialog that e.g. permations is an undefined function for every single keystroke that you have to respond to by clicking on an 'OK' button. It is frustrating and makes formulas essentially unusable. We need to make the validation of formulas "softer" in some way for the instant update to be usable.
Originally posted by @gwhitney in https://github.com/numberscope/admin/discussions/6#discussioncomment-9899148

This behaves as described and fixes that problem.  But I got a popup that permutations requires second argument to be less than first argument.  There are still going to be tons of popups as we use this.  Is it possible to route all popups that derive from mathjs to a red error message like this PR does for unknown function?

Formula entry much smoother in ui2 thanks to #498, closing.


Fix 404s on homepage at first load

When first loading an app in dev mode there was a request to /_react-static_/routeinfo/undefined. This fixes the issue.
fixes #523

@tannerlinsley, I saw you fixed something similar in 89d899dbc3b11d7ee600130a02c11ba298d5e7d2 so not sure if this PR is still mandated.

Technically, this should be needed 🤔 . But why is it working right now then? Or is it not...

WTF...

Apparently, window.location.toString() returns a string similar to the window.location.href, So it works, but we should probably use href to make sure we're backwards compatible.


Services: first build: abs added

{package} {version} {:snowflake:}
Destination channel: {Snowflake | defaults}
Links

{ticket_number}
Upstream repository
Upstream changelog/diff
Relevant dependency PRs:

...

Explanation of changes:

...

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_b5arhj0gbm/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:15: avoid_noarch: noarch: python packages should be avoided
clone/recipe/meta.yaml:44: missing_description: The recipe is missing a description

===== ERRORS =====

clone/recipe/meta.yaml:44: missing_license_family: The recipe is missing the about/license_family key.
===== Final Report: =====
1 Error and 2 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_d2p6e6j1bq/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:15: avoid_noarch: noarch: python packages should be avoided
clone/recipe/meta.yaml:44: missing_description: The recipe is missing a description

===== ERRORS =====

clone/recipe/meta.yaml:44: missing_license_family: The recipe is missing the about/license_family key.
===== Final Report: =====
1 Error and 2 Warnings were found


Extract base pipeline code for reuse in other projects

I would like to reuse the pipeline approach in VulnerableCode and possibly PurlDB as a common way to structure code that imports, improves, collects, visits and maps package and vulnerability data in these tools.
Reusing the pipeline approach will help structure similar code the same way and enable more reuse and easier switch coding between each projects.
See these issues:

[ ] https://github.com/nexB/vulnerablecode/issues/1509
[ ] https://github.com/nexB/purldb/issues/521

@pombredanne @keshav-space @TG1999
aboutcode.pipeline 0.1 published to PyPI at https://pypi.org/project/aboutcode.pipeline/


detect-secrets --scan outside/of/repository/ does not work

Perhaps in baseline.py we can do something similar to
+        if os.path.isdir(
+            os.path.join(rootdir, '.git')
+        ):
+            # This only works when you run it on the root directory of another repository
+            git_ls_files_args = [
+                'git',
+                '--git-dir', os.path.join(rootdir, '.git'),
+                'ls-files',
+            ]
+        else:
+            # This only works when you run it on a folder or file in the current repository
+            git_ls_files_args = [
+                'git',
+                'ls-files',
+                rootdir,
+            ]
         with open(os.devnull, 'w') as fnull:
             git_files = subprocess.check_output(
-                [
-                    'git',
-                    'ls-files',
-                    rootdir,
-                ],
+                git_ls_files_args,
                 stderr=fnull,
             )

However I tested this and although the output from the command was good and all, the outputted baseline was not.
Also note, that the above only works if the directory outside the current repository is the root directory for that repository, not if it's some/other/repo/folder_inside_that_repo I can imagine we could loop through all parents and see if one of them has a .git directory, but that feels real dirty. We could maybe try something similar to
    subprocess.check_output(
        ('git', 'remote', 'get-url', 'origin'),
        cwd=os.path.dirname(filename)
    ).decode('utf8').strip()

Not sure I want this feature that much, so gonna close.


Support for non-importable values

Hello!

Vote on this issue by adding a 👍 reaction
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details
I'd like to be able to have a key in the value section which when imported to other environments doesn't propagate.
Example:
Imagine you have one env whose job is to read a secret from a secrets manager, so that multiple downstream envs can reuse that logic. .e.g
# env-creds
values:
  _login:
    fn::open::aws-login:
      oidc:
        roleArn: arn:aws:iam::<>:role/Role
        sessionName: pulumi-environments-session
        duration: 1h
  _secrets:
    fn::open::aws-secrets:
      region: us-east-1
      login: ${_login}
      get:
        creds:
          secretId: myCredId
  _parsedCreds:
    fn::fromJSON: ${_secrets.creds}
  clientId: ${_parsedCreds.client_id}
  secret: ${_parsedCreds.client_secret}

When you import this into a downstream env, you're really doing it just to get the clientId and secret values, but the downstream env gets _login, secrets, _parsedCreds, etc which all get hard to read.
It's be nice if there was a way to prevent that from happening, either by denylisting them (e.g. an underscore prefix prevents propagation on import), or allowlisting the intended "exports"

My first impression is that I like the use of _ to indicate visibility: it's simple and though its meaning may not be immediately obvious, it's easy to learn and remember.
I worry, though, about values from external systems containing properties that accidentally become private due to these semantics (e.g. importing a secret from AWS secrets manager that is then deserialized into a value and exported).
Curious for opinions from @lukehoban @komalali @cleverguy25 in that regard.

I think you could potentially reserve the _ behavior for top level keys which should preclude that from ever happening

I think you could potentially reserve the _ behavior for top level keys which should preclude that from ever happening

That kind of specialization makes me slightly uncomfortable, but I think it is probably okay? Like, values + its top-level properties are already somewhat special, and I don't think that this makes that worse.


Nothing work on email and you keep closing issue...

Hello it's me!!! again and again!!
Like i previously said the advanced background in the previous version run forever and now with the change dont run at all, Skiptracer cant acces HaveIBeenPwn, LinkedIn when we say yes to enter credentials it keep going without asking for enter them, and WhoIsMind just ask for Enter and stop...
So nothing work lol except maybe MySpace but i dont look the packet send because of others issue and MySpace i dont care..

working on some updates this week, have to remove whoismind because they changed to a paid service called whoisamped, will fix the linkedin credential storage issue.

new code out, released for bsidesCT talk on saturday but advancedbackgroundchecks added some more crap to detect us, other than that everything else works


Can you add module httpclient ?

Hi
Webserver of you is very stable.
Can you add httpclient for get or post url ?

HttpClient works with TCP2UART: http -> TCP-UART Settings -> Client/Server IP: ext. ip
HttpClient a URL to GET / POST requires specialization by each task...


Prig test run crashing (when a nested static, unstubbed method is called)

I have a problem with couple of my tests. I generally observed that prig has issues with static methods with optional arguments. Not always though - I tried to reproduce this on a side project but I could not. However in my tests (fairly large solution) there are a few which had optional arguments, and they crashed the whole test run. Refactoring to methods without optional arguments solved it... for some of the. There are few tests which crash even after optional args have been removed. When I am running the test in the console:
prig run -process "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow \vstest.console.exe" -arguments "PrigTests.dll"
the process crashes, I get popup "program stopped working" then I click the "debug" button and I can get this stack trace in VS:
https://www.screencast.com/t/jvesh3Yrx
This doesn't tell me much though. Anyone has a clue what might be wrong? I am willing to make further investigation and provide more details on this tomorrow.

Thank you for the reporting! But it seems a difficult problem...
Possibly, Prig was outputting some error log. By default, it is in the directory %ALLUSERSPROFILE%\chocolatey\lib\Prig\tools\log. If possible, could you share it to me?

Here it is, but I suspect these are not the errors I was referring to:
2017/01/26 10:39:12.283066,ERROR,0x00002648,11,0x00002ef8,"    Weaver.cpp(175): Throw in function long __stdcall CWeaverDetail::CWeaverImpl::InitializeCore(struct IUnknown *)
Dynamic exception type: class boost::exception_detail::clone_impl
std::exception::what: The package which has the source """"C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\IntelliTrace\14.0.0"""" is not found.
[struct Urasandesu::CppAnonym::tag_stack_trace *] = at ?save_object_data@?$oserializer@Vxml_woarchive@archive@boost@@Vpath@filesystem@3@@detail@archive@boost@@UBEXAAVbasic_oarchive@234@PBX@Z in C:\ProgramData\chocolatey\lib\Prig\tools\x86\Urasandesu.Prig.dll
at ?save_object_data@?$oserializer@Vxml_woarchive@archive@boost@@Vpath@filesystem@3@@detail@archive@boost@@UBEXAAVbasic_oarchive@234@PBX@Z in C:\ProgramData\chocolatey\lib\Prig\tools\x86\Urasandesu.Prig.dll
at GetHistoryFileDirectory in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
at GetHistoryFileDirectory in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
at GetHistoryFileDirectory in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
at IEE in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
at IEE in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
at SetRuntimeInfo in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
at DllRegisterServerInternal in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
at SetRuntimeInfo in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
at _CorExeMain in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
at _CorExeMain in C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
at _CorExeMain in C:\Windows\SYSTEM32\MSCOREE.DLL
at BaseThreadInitThunk in C:\Windows\SYSTEM32\KERNEL32.dll
at RtlSetCurrentTransaction in C:\Windows\SYSTEM32\ntdll.dll
at RtlSetCurrentTransaction in C:\Windows\SYSTEM32\ntdll.dll
","C:\Users\urasa\Prig\Swathe\Urasandesu.Swathe\Urasandesu/Swathe/Profiling/ICorProfilerCallbackImpl.h",262,"long __stdcall CWeaverDetail::CWeaverImpl::InitializeCore(struct IUnknown *)=>Weaver.cpp,115","if (regex_search(procPath, wregex(targetProcName)))=>Weaver.cpp,139"
2017/01/26 12:00:47.667896,ERROR,0x0000264c,11,0x00002724,"    Weaver.cpp(175): Throw in function long __stdcall CWeaverDetail::CWeaverImpl::InitializeCore(struct IUnknown *)
Dynamic exception type: class boost::exception_detail::clone_impl
std::exception::what: The package which has the source """"C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\IntelliTrace\14.0.0"""" is not found.
[struct Urasandesu::CppAnonym::tag_stack_trace *] = at ?save_object_data@?$oserializer@Vxml_woarchive@archive@boost@@Vpath@filesystem@3@@detail@archive@boost@@UBEXAAVbasic_oarchive@234@PBX@Z in C:\ProgramData\chocolatey\lib\Prig\tools\x86\Urasandesu.Prig.dll
at ?save_object_data@?$oserializer@Vxml_woarchive@archive@boost@@Vpath@filesystem@3@@detail@archive@boost@@UBEXAAVbasic_oarchive@234@PBX@Z in C:\ProgramData\chocolatey\lib\Prig\tools\x86\Urasandesu.Prig.dll
at GetHistoryFileDirectory in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
at GetHistoryFileDirectory in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
at GetHistoryFileDirectory in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
at IEE in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
at IEE in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
at SetRuntimeInfo in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
at DllRegisterServerInternal in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
at SetRuntimeInfo in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
at _CorExeMain in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
at _CorExeMain in C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
at _CorExeMain in C:\Windows\SYSTEM32\MSCOREE.DLL
at BaseThreadInitThunk in C:\Windows\SYSTEM32\KERNEL32.dll
at RtlSetCurrentTransaction in C:\Windows\SYSTEM32\ntdll.dll
at RtlSetCurrentTransaction in C:\Windows\SYSTEM32\ntdll.dll
","C:\Users\urasa\Prig\Swathe\Urasandesu.Swathe\Urasandesu/Swathe/Profiling/ICorProfilerCallbackImpl.h",262,"long __stdcall CWeaverDetail::CWeaverImpl::InitializeCore(struct IUnknown *)=>Weaver.cpp,115","if (regex_search(procPath, wregex(targetProcName)))=>Weaver.cpp,139"
2017/01/26 12:58:18.243092,ERROR,0x00002d2c,11,0x00001318,"    Weaver.cpp(175): Throw in function long __stdcall CWeaverDetail::CWeaverImpl::InitializeCore(struct IUnknown *)
Dynamic exception type: class boost::exception_detail::clone_impl
std::exception::what: The package which has the source """"C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\IntelliTrace\14.0.0"""" is not found.
[struct Urasandesu::CppAnonym::tag_stack_trace *] = at ?save_object_data@?$oserializer@Vxml_woarchive@archive@boost@@Vpath@filesystem@3@@detail@archive@boost@@UBEXAAVbasic_oarchive@234@PBX@Z in C:\ProgramData\chocolatey\lib\Prig\tools\x86\Urasandesu.Prig.dll
at ?save_object_data@?$oserializer@Vxml_woarchive@archive@boost@@Vpath@filesystem@3@@detail@archive@boost@@UBEXAAVbasic_oarchive@234@PBX@Z in C:\ProgramData\chocolatey\lib\Prig\tools\x86\Urasandesu.Prig.dll
at GetHistoryFileDirectory in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
at GetHistoryFileDirectory in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
at GetHistoryFileDirectory in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
at IEE in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
at IEE in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
at SetRuntimeInfo in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
at DllRegisterServerInternal in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
at SetRuntimeInfo in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
at _CorExeMain in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
at _CorExeMain in C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
at _CorExeMain in C:\Windows\SYSTEM32\MSCOREE.DLL
at BaseThreadInitThunk in C:\Windows\SYSTEM32\KERNEL32.dll
at RtlSetCurrentTransaction in C:\Windows\SYSTEM32\ntdll.dll
at RtlSetCurrentTransaction in C:\Windows\SYSTEM32\ntdll.dll
","C:\Users\urasa\Prig\Swathe\Urasandesu.Swathe\Urasandesu/Swathe/Profiling/ICorProfilerCallbackImpl.h",262,"long __stdcall CWeaverDetail::CWeaverImpl::InitializeCore(struct IUnknown *)=>Weaver.cpp,115","if (regex_search(procPath, wregex(targetProcName)))=>Weaver.cpp,139"

I also managed to get a brief error message in visual studio when the test process crashes: it says that the heap is damaged.

I have made some further investigation and the error is not caused by optional arguments. My code is set up as follows:
public void DoSomething(.....) {
    ....
    StaticClass.StaticMethod(.....);
}
public static void StaticMethod(....) {
    ....
    string result = AnotherStaticClass.AnotherStaticMethod("some string input");
}
The test calls DoSomething and stubs the StaticMethod with a simple delegate. As soon as I comment out the line var result = AnotherStaticClass.AnotherStaticMethod(...); and recompile prig assemblies the test starts to work. I cannot share my exact code and I am unable to reproduce this behavior on a side project unfortunately. Might there be some problem with how the classes/methods are named, or how many args they have or with naming of those args? I should also mention that AnotherStaticMethod is also added in prig settings file (so I can stub them and I do that in some other tests, which work just fine).

Here it is, but I suspect these are not the errors I was referring to:

The latest error log that is recorded at 2017/01/26 12:58:18.243092 is probably caused by that prig install command was not executed correctly, but umm... What is "IntelliTrace"? I little investigated about that, it seems the feature Visual Studio 2015 Enterprise Edition or more only has. Could you disable it?

I have made some further investigation and the error is not caused by optional arguments. My code is set up as follows:

Thank you for your deep investigation!
In the past, the complex issue around a parameter that is caused by the order of referenced assembly existed. You might be able to reproduce on a side project if you make it having plurality class libraries.

There is one more thing I noticed: when I run the test from VS Test Explorer it works. When it is executed from ReSharper test runner, or from command line ("prig run ...") - then it crashes.

I don't have ReSharper license, so I'm investigating command line side. However, vstest.console.exe works correctly in my environment against some simple samples :disappointed_relieved:
Now, I have requested ReSharper Ultimate Free Open Source License to JetBrains to investigate this issue. I will contact you if there is progress.

Thanks for your support. Today I did even more investigation and it seems that the cause of the error is even different than I thought. I even can't isolate the problematic line of code now. What I'm doing is commenting/changing code withing the method that is being stubbed in the test, recompiling prig assemblies and re-runing the test. There is some randomness around it, and in the end it seems that the optional parameters have something to do with the issue - when removing/changing calls to such methods I am able to make the test run or make it fail, but it doesn't seem to be consistent (or I can't see the clue).
I also tried on a side project as well, by copying quite a lot of code from my original project but without success. in the new project the test passes.

I tried to run one of @andy250 's tests (we're co-workers) - and it also failed on my local PC.
When analyzing the .dmp file in DebugDiag2 - it seems it is also related to Serialization in Boost.
Exception Information
NTDLL!RTLREPORTCRITICALFAILURE+89In vstest.executionengine.x86.exe.21552.dmp the assembly instruction at ntdll!RtlReportCriticalFailure+89 in C:\Windows\System32\ntdll.dll from Microsoft Corporation has caused a corrupted heap exception (0xC0000374) when trying to perform an unknown operation on memory location 0x09b1b500 on thread 21

Thread 21 - System ID 6168

This thread is not fully resolved and may or may not be a problem. Further analysis of these threads may be required.

.NET Call Stack

[[PrestubMethodFrame] (.{error})] www.dll!Unknown

Full Call Stack

ntdll!NtWaitForMultipleObjects+c
ntdll!WerpWaitForCrashReporting+63
ntdll!RtlReportExceptionHelper+2c7
ntdll!RtlReportException+6a
ntdll!RtlReportCriticalFailure+ad
ntdll!RtlpReportHeapFailure+32
ntdll!RtlpLogHeapFailure+9f
ntdll!RtlFreeHeap+ac
msvcr120!free+1a
Urasandesu_Prig!boost::archive::detail::oserializer<boost::archive::xml_woarchive,boost::filesystem::path>::save_object_data+a7024
Urasandesu_Prig!boost::archive::detail::oserializer<boost::archive::xml_woarchive,boost::filesystem::path>::save_object_data+a72ee
Urasandesu_Prig!boost::archive::detail::oserializer<boost::archive::xml_woarchive,boost::filesystem::path>::save_object_data+13038b
Urasandesu_Prig!boost::archive::detail::oserializer<boost::archive::xml_woarchive,boost::filesystem::path>::save_object_data+12fd67
Urasandesu_Prig!boost::archive::detail::oserializer<boost::archive::xml_woarchive,boost::filesystem::path>::save_object_data+130266
Urasandesu_Prig!boost::archive::detail::oserializer<boost::archive::xml_woarchive,boost::filesystem::path>::save_object_data+12fa41
Urasandesu_Prig!boost::archive::detail::oserializer<boost::archive::xml_woarchive,boost::filesystem::path>::save_object_data+12f4e5
Urasandesu_Prig!boost::archive::detail::oserializer<boost::archive::xml_woarchive,boost::filesystem::path>::save_object_data+129826
Urasandesu_Prig!boost::archive::detail::oserializer<boost::archive::xml_woarchive,boost::filesystem::path>::save_object_data+f8c0d
Urasandesu_Prig!boost::archive::detail::oserializer<boost::archive::xml_woarchive,boost::filesystem::path>::save_object_data+aa0b6
Urasandesu_Prig!InstanceGettersTryRemove+1d1b
Urasandesu_Prig!boost::archive::detail::oserializer<boost::archive::xml_woarchive,boost::filesystem::path>::save_object_data+51765
Urasandesu_Prig!boost::archive::detail::oserializer<boost::archive::xml_woarchive,boost::filesystem::path>::save_object_data+4f0fb
clr!EEToProfInterfaceImpl::JITCompilationStarted+5d
clr!MethodDesc::MakeJitWorker+2fe

@ngjermundshaug, it is strange... In the stack trace, boost::archive::xml_woarchive is appeared. This class is only used when executing prig install, prig update and prig uninstall command in Prig. Normally, these command is executed only once at the first time in each environment.
Are you wrapping prig run by any scripts? If it is true, would you share it to me?

Basically when running from within VS "prig run" is wrapped by either ReSharper test runner or VSTest runner (which we donb't have access to). When running from command line there is no additional wrapping.
Today I can observe a bit different behavior (which is weird, to say the least):

pring run -process "vstest.console.exe" -arguments "PrigTests.sll /Tests:CrashingTestName" --> test runs but the stubs are not working (original implementation is called) - which is different than it was yesterday/last week. How is this even possible?
ReSharper test runner from within VS --> test crashes. ReSharper uses vstest.executionengine.x86.exe internally. The error originates in C:\Windows\SYSTEM32\ntdll.dll.

OK, I have understood that there are no any wrapper scripts. Ummmmm...

Restarted PC, Opened VS, Recompiled, Ran test with VS Test Runner ==> It crashed.
So it's definitely not related to installing/uninstalling PRIG in the VS Menu.

@ngjermundshaug, thank you for the retrying.
After that, what kind of situation is Prig log of your machine?(it is in the directory %ALLUSERSPROFILE%\chocolatey\lib\Prig\tools\log)
Is it same as andy250's?

MEMO
The log message The package which has the source "..." is not found. is Prig's. However, boost::archive::xml_woarchive isn't appeared in the stack trace usually. For example,  the following log will output after deleting all packages by prig uninstall all:
2017/02/02 06:59:53.993709,ERROR,0x00001d74,11,0x00003ec0,"    Weaver.cpp(175): Throw in function long __cdecl CWeaverDetail::CWeaverImpl::InitializeCore(struct IUnknown *)
Dynamic exception type: class boost::exception_detail::clone_impl<struct Urasandesu::CppAnonym::CppAnonymInvalidOperationException>
std::exception::what: The package which has the source """"C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO 12.0\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\TESTWINDOW"""" is not found.
[struct Urasandesu::CppAnonym::tag_stack_trace * __ptr64] = at Urasandesu::CppAnonym::CppAnonymInvalidOperationException::CppAnonymInvalidOperationException in C:\ProgramData\chocolatey\lib\Prig\tools\x64\Urasandesu.Prig.dll(c:\users\urasa\prig\cppanonym\urasandesu.cppanonym\urasandesu\cppanonym\cppanonyminvalidoperationexception.cpp:50)
at CWeaverDetail::CWeaverImpl::InitializeCore in C:\ProgramData\chocolatey\lib\Prig\tools\x64\Urasandesu.Prig.dll(c:\users\urasa\prig\urasandesu.prig\weaver.cpp:175)
at Urasandesu::Swathe::Profiling::ICorProfilerCallbackImpl<ICorProfilerCallback5>::Initialize in C:\ProgramData\chocolatey\lib\Prig\tools\x64\Urasandesu.Prig.dll(c:\users\urasa\prig\swathe\urasandesu.swathe\urasandesu\swathe\profiling\icorprofilercallbackimpl.h:262)
at TranslateSecurityAttributes in C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
at TranslateSecurityAttributes in C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
at NGenCreateNGenWorker in C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
at InitializeFusion in C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
at InitializeFusion in C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
at InitializeFusion in C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
at InitializeFusion in C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
at GetCLRFunction in C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
at _CorExeMain in C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
at _CorExeMain in C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
at _CorExeMain in C:\WINDOWS\SYSTEM32\MSCOREE.DLL
at BaseThreadInitThunk in C:\WINDOWS\System32\KERNEL32.dll
at RtlUserThreadStart in C:\WINDOWS\SYSTEM32\ntdll.dll

","C:\Users\urasa\Prig\Swathe\Urasandesu.Swathe\Urasandesu/Swathe/Profiling/ICorProfilerCallbackImpl.h",262,"long __cdecl CWeaverDetail::CWeaverImpl::InitializeCore(struct IUnknown *)=>Weaver.cpp,115","if (regex_search(procPath, wregex(targetProcName)))=>Weaver.cpp,139"

I guess that there is some environmental problem. Now, I have gotten ReSharper Ultimate Free Open Source License. After this, I'm going to change the investigation environment to it and continue.

@urasandesu %ALLUSERSPROFILE%\chocolatey\lib\Prig\tools\log is empty on mu machine.

@ngjermundshaug, thank you for the reply!
These problems are same superficially but they possibly are different basically, aren't they?
I have installed ReSharper and started the investigation.  I will contact you if there is progress.

I am not running tests using Resharper, so I doubt that Resharper is causing this.. but then again you never know..

@ngjermundshaug, vstest.console.exe works fine in my environment, so I think this side has no key to progress, sorry...

@andy250, I tried to execute Quick Tour with ReSharper test runner, but I couldn't do it(it wasn't stubbed anything):

Probably, you have changed some options of ReSharper to be able to execute your test project. Would you give me those information? For example,

Testing framework and its version(NUnit? xUnit.net? MsTest?)
Project platform architecture(Any CPU? x86? x64?)
.NET Framework version(CLR2.0? CLR4.0? CLR4.5?)
Is enabled shadow-copy assemblies?
Is enabled separated AppDomain testing?
Where is the test work directory?($(TargetDir)? or another?)
Is used Test Settings File?

I really haven't changed anything to run from R#. Here are the information:

MsTest (assembly referenced: Microsoft.VisualStudio.QualityTools.UnitTestFramework)
AnyCPU
4.6
I guess not - where can I find this setting/information?
I guess not - where can I find this setting/information?
Not sure about the work directory: I just compile tests in VS and then run from VS, so I guess bin/Debug
Nothing that I know of

Be sure to enable Prig Adapter for TestProject - I failed to do so in the beginning (or I enabled the adapter for some other project accidentally) - in that case nothing was stubbed for me.
Also as @ngjermundshaug  mentioned this is not a R# specific issue. I am getting the same when executing prig run ... from command line.

@andy250, thank you for the information!
Now I have investigated from these information, and I have found out that there are some issues when executing tests in MsTest. As far as I have grasped, #90 and #91 have been found.
As you and @ngjermundshaug pointed out, this isn't R# specific issue.

@urasandesu Do you think fixing #90 and #91 will fix the current problem too?

@andy250, yes, I think so. Specially, if I fix #91, other issues will also be fixed at same time.

@andy250, now I have created VSIX that contains the commit to fix #90 and #91. Would you try this?: Prig.zip

@urasandesu thanks for the new package. I got 2 issues:

When instaling new vsix I got error about duplicate package when calling nuget sources add -name "Prig Source". To fix this I had to run nuget sources remove -name "Prig Source".
When running the test I am getting an exception:

Initialization method PrigTests.SomeTest.Initialize threw exception. System.EntryPointNotFoundException: System.EntryPointNotFoundException: DLL 'Urasandesu.Prig.dll' cannot find entry point named 'InstanceGettersTryGet'..
w Urasandesu.Prig.Framework.InstanceGetters.TryGet(String key, IntPtr& ppFuncPtr)
w Urasandesu.Prig.Framework.LooseCrossDomainAccessor1.GetOrRegisterHolder()    w Urasandesu.Prig.Framework.LooseCrossDomainAccessor1.get_HolderOrRegistered()
w Urasandesu.Prig.Framework.LooseCrossDomainAccessor.GetOrRegisterT
w Urasandesu.Prig.Framework.TypedBehaviorPreparableImpl.set_BodyCore(Delegate value)
w Urasandesu.Prig.Framework.TypedBehaviorPreparableImpl.set_Body(Delegate value)
w Urasandesu.Prig.Framework.TypedBehaviorPreparable`1.set_Body(TDelegate value)
It seems that this happens as soon as I call any PMyClass.GetInfo().Body = ....

@andy250, the exception is caused by the uninstallation failure against previous. Please check the following point:

From empty Visual Studio, select PRIG - Unregister Prig (Needs Restarting) and Register Prig (Needs Restarting) again.
In your sln directory, remove packages directory and all obj, bin directories.
In your test project, open packages.config and replace Prig entry version 2.3.1 to 2.3.2.
Rebuild your sln.

@urasandesu I can confirm the new version fixed the crash. This is awesome! Thanks for your support.
When can we expect new prig version in chocolatey gallery?

@andy250, I'm glad :relieved:
Now I'm adding some tests for the extent of the impact. I'll finish new Prig version this month if there is no problem. Please wait for a little longer.

Sure no problem. I actually have one more minor issue - when I run from the console (prig run -process "vstest.console.exe" "MyTests.dll") it seems that stubs are not used - original implementation gets called. When I run it from Visual Studio it is OK (TestExplorer + MSTest). Any ideas?
I have prig.exe in C:\ProgramData\chocolatey\lib\Prig\tools. It looks like it has been updated today.

Did you set environment variables?
When Prig is executed from Visual Studio, some special environment variables are set automatically like the bellow:

URASANDESU_PRIG_CURRENT_DIRECTORY
Working directory for Prig. Default value is set to $(TargetDir) (output directory for build results).
URASANDESU_PRIG_TARGET_PROCESS_NAME
The target process name that Prig should attach. Default value is set to '(vstest\.executionengine)|(te\.processhost\.managed[^/]+/role=testexecution).

Our Wiki also explains to collect coverage by prig and OpenCover with these variables. It might be helpful to you.

Tried setting the variables (process name set to "vstest.console.exe") but with no effect. I remember it worked at the very beginning just after I installed 2.3.1 few weeks ago. I think it stopped working even before I installed your new vsix. What else could have been modified in my environment?

Where is vstest.console.exe installed on your local machine?
In v2.3.2, Prig searches VSxxxCOMNTOOLS environment variables and installs necessary DLLs to all location of Visual Studio Test Tools that also contains vstest.console.exe normally (e.g. %VS140COMNTOOLS%..\IDE\CommonExtensions\Microsoft\TestWindow).
You can check the install information for Prig by the following commands in PowerShell:
PS C:\> prig list | ConvertFrom-Json | fc

For example, this is my local machine Prig install information:

Source property is the directory of the process that Prig can attach. Is there difference compared to the location of vstest.console.exe?

The configuration looks OK. It points to C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow where vstest.console.exe resides. In that folder there are also symlinks to dlls, which point to C:\ProgramData\chocolatey\lib\Prig\lib. Only the x64 subfolder does not contain vstest.console.exe at all (but contains symlinks). I looked at TeamCity server - configuration also looks correct there.

What is going on... :dizzy_face:
Well, Prig has debug trace mode. We might be able to find the problem if enabling that. Set environment variable URASANDESU_CPPANONYM_LOGGING_SEVERITY to 0 when executing vstest.console.exe. For example,
CMD C:\> SET URASANDESU_CPPANONYM_LOGGING_SEVERITY=0

CMD C:\> prig run -process "%VS120COMNTOOLS%..\IDE\CommonExtensions\Microsoft\TestWindow\vstest.console.exe" -arguments UnitTestProject1.dll
Microsoft (R) Test Execution Command Line Tool Version 12.0.30723.0
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...
Passed   TestMethod1

Total tests: 1. Passed: 1. Failed: 0. Skipped: 0.
Test Run Successful.
Test execution time: 0.9470 Seconds

CMD C:\>

After this, debug level log will be outputted to the directory %ALLUSERSPROFILE%\chocolatey\lib\Prig\tools\log. For example, this is the log of my environment: app_20170215.zip
Note the following and check the log:

Find the Current Process Path: record. Is it intended path of vstest.console.exe?
Find the Indirection DLL: record. Is it intended Prig Assembly?
Find the Current Path: record. Is it the path that is same as the location that unit test DLL and Prig Assembly are located?
Find the This method is marked by IndirectableAttribute. record. Does it exist?

Thx for the tips. You pointed me in the right direction with the Current Path - I didn't know I need to cd to the folder with test dll and prig assembly! My log file was missing Indirection DLL. After I changed working directory the Indirection DLL appeared in the log and the stubbing seems to take place now... but I get a crash, the same way as it did before upgrade to 2.3.2. So it seems my local machine has same problem as TeamCity server. Only place where it works is VisualSTudio test runner. So we are one step ahead, but I need to make this work from the command line now. Would the trace-mode log file be of any help?

Umm... I can't think of a solution right away. Sorry to cause you trouble.
In addition, today it turned out that there are some problems if applying current correction way (FileLoadException: Loading this assembly would produce a different grant set from other instances. (Exception from HRESULT: 0x80131401) will occur in some situation). I'm going to investigate it this weekend, so you might have better try again after that.

Sorry to say, but we have decided to revert back to fakes. Apart from couple of tests crashing we had trouble running tests stable under TeamCity (especially recently stubbing stopped working at all). If you can improve TeamCity support and fix the crashes we are more than happy to try it out again in near future. Thanks again for your efforts and great support.

I'm the one who should apologize. Thanks to you, I was able to also find other new issues. I will continue to improve this framework. If there is an opportunity, please try Prig again.


docs: make it clear in the tutorial where the docs folder is

I'm afraid it was not clear, to the beginner user—who this tutorial is for—where the docs folder was .
The only reason I know this is because I'm a beginner user and I tried for too many minutes to find the docs folder inside the website folder. :sweat_smile:
I had this assumption because the previous example is offered under the assumption that you're in the website folder.
Feel free to change the wording, I just want to make it clear where you should be looking, if you're new.

Motivation
I'm new to Docusaurus and I want to make the tutorial clear for new users.
Have you read the Contributing Guidelines on pull requests?
I haven't... and now I have. Sorry about my commit not matching the style. I'm not sure how to fix that now.
Test Plan
N/A, I'm pretty sure. :sweat_smile:
Related PRs
Also, N/A.

Oh, and maybe it would fit better to use that yellow note style, rather than parenthesis.

I'll let you decide.

Oh, look, another! I found it eventually, but it's not super clear where sidebars.json is either.

Maybe specifying website/sidebars.json would be better?

Should I start another pull request?

Should I start another pull request?

Yes please. You can also include the updates to sidebars.json you mentioned above.


Pivnet-resource should optionally trigger on version changes only

Symptom:
We use pivnet-resource in the PCF Redis team to trigger our pipelines when new stemcell patches are released.
We use tag: latest-final of pivnet-resource from docker hub.
Current Behaviour:
Multiple changes to source metadata causes our pipelines to run multiple times with the same stemcell. The last stemcell (3445.28) triggered 5 times across several hours.
We suspect that in most cases the pivnet resource should not trigger on changes to metadata. We want the resource to trigger only on changes to the minor version.
Suggestion:

Add an 'ignore_metadata_changes' flag to the source configuration.
This would allow teams that wish to check metadata to continue to do so, while improving the experience for teams interested in actual releases.

cc: @mrosecrance

Yes, with ignore_metadata_changes: true, I think any changes that are not file changes should be ignored.

@jacknewberry If you log in without an admin or special access account, does that help resolve the issue as well?

Hi Tiffany,
I think using a user with reduced permissions has fixed this for us. We
won't know for certain until a new stemcell is released.
It is a little less than ideal. We now need to maintain separate users to
check pivnet, and to upload to pivnet. I'm sure we will manage.
Jack
On Tue, May 15, 2018 at 8:13 PM Tiffany Jordan<EMAIL_ADDRESS>wrote:

@jacknewberry https://github.com/jacknewberry If you log in without an
admin or special access account, does that help resolve the issue as well?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pivotal-cf/pivnet-resource/issues/90#issuecomment-389280960,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAfjQA1f_YUHnr3y1D_66ooJCg5p9H7zks5tyyjPgaJpZM4STq4W
.

Hi @tiffjordan,
We definitely see this when our PMs make changes to our releases once they are public. We've gotten around it by checking the version of the triggering resource against an external file to see if we have already performed the desired action, but it would be nice if we didn't have to do this.
Regards,
Dave

I will bring this to our PM's attention.
Closing issue.
Marking as wont' fix.
This is not permanent but a reflection of the current status. Please feel free to comment or reopen.


Introduce Spinnaker pipelines

Create "Deploy to staging" and "Deploy to production" pipelines.
Deploy to staging should:

Depend on a Jenkins build job for a trigger
Leverage a Jenkins smoke test job
Deploy using highlander strategy, presuming staging resources should be kept to a minimum.

Deploy to production should:

Depend on deploy to staging pipeline as a trigger
Use Find Image for artifact discovery, finding the newest server group
Deploy using a red/black strategy with 2 server groups.

These jobs should presume user configures Spinnaker for a single CF space.

Tracking this effort on https://github.com/gregturn/spring-cloud-pipelines/tree/gh-25

On hold. We'll come back to this if the community is interested in this.


Can nvim-bqf shorten file paths similar to vim-qf?

Feature description
vim-qf can shorten filepaths for better legibility.
Can nvim-bqf do something similar, e.g. relative to the current pwd?
Describe the solution you'd like
Shorten the filepaths for better legibility.
Additional context
No response

Apparently, it can already. Is it documented?

Have you sovled?

I might have fixed it by changing pwd. Does nvim-bqf have actually a path shortening feature?
vim-qf describes its shorten path feature as following:
------------------------------------------------------------------------------
                                                          *'g:qf_shorten_path'*
Value: numeric                                                               ~
Default: 1                                                                   ~

Enables or disables shortening of the file paths in the location/quickfix
window.

With the option set to `0` (vanilla Vim):
>
    very/long/path/with/lots/of/subdirectories/filename.ext|87 col 22| …
With the option set to `1` (vim-qf default):
>
    v/l/p/w/l/o/s/filename.ext|87 col 22| …
With the option set to `3` (Vim v8.2.1741 or above):
>
    ver/lon/pat/wit/lot/of/sub/filename.ext|87 col 22| …
Add the line below to your vimrc to change the default value:
>
    let g:qf_shorten_path = 0
<

I am not sure whether I want it exactly as vim-qf. I think only for long paths it should be abbreviated. So there should be a threshold setting and then maybe  a number for the number of characters used to display a shortened path.

https://github.com/kevinhwang91/nvim-bqf#customize-quickfix-window-easter-egg
Program by yourself.

Thanks for the pointer. I will have a look into this.


understanding tolerance

Hi there,
I'm having an issue with tolerances: From the following test sample, do you have an idea what I might do wrong? The test passes against values 21100 (system under test) and 15892 (assert). I'm expecting it to fail.
I'm testing the runtime of jobs taking data from MSDB.
 <test name="Check if last run of Job '(does not work due to bug)' is within '1%' deviation to average.">
    <category>ETL Performance</category>
    <system-under-test>
      <execution>
        <query connectionString="@MSDB">
SELECT
	jobs.name AS Job
	, Avg(hist.run_duration) AS RunDuration
FROM dbo.sysjobs jobs
INNER JOIN (
	SELECT
	ROW_NUMBER() OVER (PARTITION BY [job_id] ORDER BY [run_date] desc, [run_time] desc) AS LastRunNumber
	,job_id
	,[run_duration]
	,run_date
  FROM [dbo].[sysjobhistory]
  WHERE step_id = 0 -- just job outcome
  AND [run_status] = 1 -- just successful runs
  ) hist ON
  hist.job_id = jobs.job_id
  AND
  hist.LastRunNumber = 1 -- take last run
  WHERE
	jobs.name = '<myJobName>'
GROUP BY jobs.name</query>
      </execution>
    </system-under-test>
    <assert>
      <equalTo tolerance="1%">
        <query connectionString="@MSDB">
SELECT
	jobs.name AS Job
	, Avg(hist.run_duration) AS RunDuration
FROM dbo.sysjobs jobs
INNER JOIN (
	SELECT
	ROW_NUMBER() OVER (PARTITION BY [job_id] ORDER BY [run_date] desc, [run_time] desc) AS LastRunNumber
	,job_id
	,[run_duration]
	,run_date
  FROM [dbo].[sysjobhistory]
  WHERE step_id = 0 -- just job outcome
  AND [run_status] = 1 -- just successful runs
  ) hist ON
  hist.job_id = jobs.job_id
  AND
  hist.LastRunNumber BETWEEN 2 AND 20 -- take last runs
  WHERE
	jobs.name = 'myJobName'
GROUP BY jobs.name</query>
      </equalTo>
    </assert>
  </test>

What's your version of the framework?
Could you reproduce with
 <test name="Check if last run of Job '(does not work due to bug)' is within '1%' deviation to average.">
    <category>ETL Performance</category>
    <system-under-test>
      <execution>
        <query connectionString="@MSDB">
SELECT 21100 </query>
      </execution>
    </system-under-test>
    <assert>
      <equalTo tolerance="1%">
        <query connectionString="@MSDB">
SELECT 15892 </query>
      </equalTo>
    </assert>
  </test>

If yes I'll investigate further because it's clearly not expected.

It's no bug. Your hint pointed me in the right direction, thank you @Seddryck !
I connected to the wrong server (got a connection to a MSDB there, therefore no error, which made it difficult to debug). *palmface


Push to version 0.7.9 of denonavr

Description:
Push to version 0.7.9 of denonavr includes several fixes

Fix empty sources list in Zone 2 and 3 at non AVR-X devices
Add sound mode 'DOLBY HD'
Add 'Dolby TrueHD' sound mode
Add sound mode 'DOLBY ATMOS'

Checklist:

[X] The code change is tested and works locally.
[X] Local tests pass with tox. Your PR cannot be merged unless tests pass
[X] There is no commented out code in this PR.
[X] I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[X] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[X] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[ ] Untested files have been added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

Failure is unrelated to PR.  Merging.


Update README.md

Codecov Report

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

@@          Coverage Diff           @@
##             main      #7   +/-   ##
======================================
  Coverage        ?   0.00%
======================================
  Files           ?       2
  Lines           ?      87
  Branches        ?       0
======================================
  Hits            ?       0
  Misses          ?      87
  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 a5c053b...d2d552d. Read the comment docs.

thanks!


Find widget in small editor makes red background overflow

Open find widget and have no results (so there is red background)
Shrink the editor to be very narrow, notice the find widget gets broken, red background overflows

Seems fixed now.

Yeah, I killed the red background


take version from protoc instead of scalapb config

fixes #367
@azymnis any objections?

@johnynek any objections?

It would be nice to have test that exercised what you are trying to get at here, but I guess this won't break us.
We can merge and if this unblocks you. If it does break us, we can follow up with a test or change.

What I'm trying to get here is to have one source of truth where today we have two (as detailed in #367). This isn't actually for our needs (internally we use a different entry point) but for the good of the community.


Missing ',' on struct declarations absorbs next item silently

Expected Behaviour:
A error would be raised when there's a missing ',' after a struct declaration
MWE :
(using structstruck = "0.3")
#![allow(unused)]
structstruck::strike!{
    #[strikethrough[derive(Debug, Default)]]
    struct Correct {
        not_eater: struct {
            stomach: (),
        },
        not_eaten: struct {
            apple: bool,
        }
    }
}

structstruck::strike!{
    #[strikethrough[derive(Debug, Default)]]
    struct Incorrect {
        eater: struct {
            stomach: (),
        } // notice the missing comma
        eaten: struct {
            apple: bool,
        }
    }
}

fn main() {
    println!("correct: {:?}", Correct::default());
    println!("incorrect: {:?}", Incorrect::default());
}

and the output is:
correct: Correct { not_eater: NotEater { stomach: () }, not_eaten: NotEaten { apple: false } }
incorrect: Incorrect { eater: Eater { stomach: () } }

Observations
@jcaesar, if you have a vague idea of how to fix this, you can try to guide me, as I would like to fix this (to learn more about derive macros).

My usual entrypoint to this kind of debugging is to

Add a (hopefully failing) test with the broken struct. (Then you can ignore the proc macro part and debug the test like its normal rust code.)
Add a println!("{parsed:#?}") here to see how venial transformed the tokens into rust structs. (Or well, if you've got a debugger that doesn't consist of println and thinking meat, use that.)

Spoiler
I think what's happening here is that venial doesn't parse types, so the entire … } /* missing comma */ eaten: struct … is interpreted as the type of eater. I haven't looked at it deeply yet, but probably structstruck should error on finding two is_decl_kw here.

Thinking about it: similar bugs might also exist for struct Foo { foo: Result<struct O {} struct E {}> }. I'll check that.

Thanks a lot, I'll look into it when I can.
So far I've opened the issue to document it, but I'm not sure when I will be able to try my hand at fixing it. It's just a little annoying to have (and to spot) when you don't know about it, and rust usually is great at warning you about this kind of 'obvious' stumbling blocks.
Maybe add a note on the main docs.rs page about this so other people using the library are aware of it?

I don't think a fix would be too complicated. I hope I'll have time to have a look this weekend.

I don't think a fix would be too complicated. I hope I'll have time to have a look this weekend.

3 months go by 😹

Its fixed in this repo. Its fixed in venial, too, and I was kind of hoping they'd do a release. Oh well, I guess I'll do one.