scipy.stats: Allow specifying inverse-variance matrix to multivariate_normal

Describe the solution you'd like
Currently, scipy.stats.multivariate_normal accepts a mean and covariance matrix, and computes the inverse variance matrix internally and explicitly. But I often have covariance matrices with inverses that can be computed through other linear algebra tricks, e.g., the woodbury matrix identity. It would therefore be great if scipy.stats.multivariate_normal would allow optionally passing in an inverse-variance matrix, which is sometimes useful for (a) performance, or (b) numerical precision issues with covariance matrices with large values.
I thought I would raise an issue here to discuss before actually implementing anything, but I would be happy to work on a PR.
Describe alternatives you've considered
I have either implemented my own custom_multivariate_normal distribution, or used the implementation in astroML to compute the log-pdf, but it would be nice to have this included in scipy as well.

I am not opposed to this proposal. However, that would change things in many signatures so probably want to get a broad agreement. Usually these discussions happen on the dev mailing list, I recommend sending the proposal there with an idea of how you would implement. Not the whole code just something more specific than the proposal.
To be clear, your proposal would not include SMW theorem type inversions inside the mVN methods, correct?
I understood that you would do the inversion on user side and pass the inverted matrix into the mVN method(s).
-Lucas Roberts

On Nov 11, 2019, at 2:38 PM, Adrian Price-Whelan<EMAIL_ADDRESS>wrote:

Describe the solution you'd like
Currently, scipy.stats.multivariate_normal accepts a mean and covariance matrix, and computes the inverse variance matrix internally and explicitly. But I often have covariance matrices with inverses that can be computed through other linear algebra tricks, e.g., the woodbury matrix identity. It would therefore be great if scipy.stats.multivariate_normal would allow optionally passing in an inverse-variance matrix, which is sometimes useful for (a) performance, or (b) numerical precision issues with covariance matrices with large values.
I thought I would raise an issue here to discuss before actually implementing anything, but I would be happy to work on a PR.
Describe alternatives you've considered
I have either implemented my own custom_multivariate_normal distribution, or used the implementation in astroML to compute the log-pdf, but it would be nice to have this included in scipy as well.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

That's right, I was imagining just adding a new argument to accept the inverted matrix into the mVN methods — it would be up to the user to do the inversion. I'll open a thread on the mailing list - thanks.

So this would change
pdf(x, mean=None, cov=1, allow_singular=False)

to
pdf(x, mean=None, cov=1, allow_singular=False, inverse_cov=None)

and the same for cdf, entropy, logcdf, logpdf and rvs?
Seems reasonable.

Elsewhere in statistics, I think the inverse covariance matrix is usually called the "precision" matrix. Other packages use either "precision" (stan) or "tau" (PyMC3) as a separate argument that supersedes the default cov. "Precision" might be the more generally used term?

I would prefer the inverse instead of a domain specific terminology.

So this would change
pdf(x, mean=None, cov=1, allow_singular=False)

to
pdf(x, mean=None, cov=1, allow_singular=False, inverse_cov=None)

and the same for cdf, entropy, logcdf, logpdf and rvs?
Seems reasonable.

I think entropy works with covariance matrix whereas the others work with inverse covariance matrix, so for entropy method you'd still need to invert if you passed in inverse covariance.
Another thing to consider is a flag for removing PSD checks. I've found in simulations that PSD checks can take a fair bit of overhead, even if you pass in the same covariance (or inverse covariance) matrix every time, or are (say) drawing from a wishart/inverse wishart which is PSD by construction.
It sounds like one of the goals here is speed/performance so wanted to point this out too.

@adrn thanks for this suggestion! What was the verdict of the mailing list discussion?

@rgommers expressed support, but I don't think anyone else chimed in! I forgot about this but could take another crack at it if you think it'd be useful :)

Mailing list link: https://mail.python.org/pipermail/scipy-dev/2019-November/023843.html

@rgommers expressed support, but I don't think anyone else chimed in!

That's not uncommon. Discussion typically happens here, the mailing list message gets seen by many more people though so it's a good data point that no one was opposed.

Yes, makes sense - not a criticism, just reporting :)

Thanks @adrn. Based on what I see here and from the limited response on the mailing list, sounds like a PR would be welcomed. (How long it takes to get a full review depends on how complicated it is!)

I would like to see an inverse_cov option. In my MCMC algorithms I often have to compute the log probability many times using the same cov matrix. It does not make sense for me to recompute the inverse at each iteration if i am using the same cov matrix and therefore it would be convenient to have inverse_cov as an option. Until this becomes an option I have to define my own multivariate normal log pdf function that allows inverse_cov which is annoying

Here is a similar discussion at numpy: https://github.com/numpy/numpy/issues/17158
For those interested, I wrote a cython function to do just this some time ago:
https://github.com/zoj613/OccuSpytial/blob/e599d515b5377cb8f7a16af828f39b115a04bc66/occuspytial/distributions.pyx#L42-L110

I was curious as to how this could be done and ended up making significant progress (branch: https://github.com/siddhantwahal/scipy/tree/enh/mvn-normal-inv-cov). The implementation rests on storing square roots of the covariance and the inverse covariance. This has two advantages:

It avoids repeated computation of the covariance square root in multivariate_normal.rvs (#11772)
It can be easily extended to allow the user to specify covariance square roots directly (through the CovInfo object). See #15675 for example.

Would a PR still be welcome?


Support builder history view on flutter build dashboard

The builder history is lost when moving flaky tests from prod to staging. This makes it a lot more difficult to investigate different failure modes, and look at a history (or lack thereof) of flakes.
E.g.: https://ci.chromium.org/p/flutter/builders/staging/Linux_android flutter_gallery__back_button_memory?limit=100
vs.
https://ci.chromium.org/p/flutter/builders/prod/Linux_android flutter_gallery__back_button_memory (which no 404s).
/cc @CaseyHillers @godofredoc

Is there an issue with using https://flutter-dashboard.appspot.com/#/build? The Flutter build dashboard sorts the builds by the commits and their run order, and MILO only sorts by the run order.

To be explicit, this isn't an issue in the build dashboard as it'll correctly link you to the build page (whether it's staging or prod)

In the flaky test workflow, the bot puts links to builds in issues, for example https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android flutter_gallery__back_button_memory/995/overview.
That page has a link to https://ci.chromium.org/p/flutter/builders/prod/Linux_android flutter_gallery__back_button_memory, which is now dead.
https://ci.chromium.org/p/flutter/builders/prod/Linux_android flutter_gallery__back_button_memory is a lot easier to use than https://flutter-dashboard.appspot.com/#/build since you just follow the link that's already on the build page instead of switching to a new tab. https://ci.chromium.org/p/flutter/builders/prod/Linux_android flutter_gallery__back_button_memory also has more information displayed like the commit hash, the commit time, the build number, etc. that is hidden in https://flutter-dashboard.appspot.com/#/build.
I think it would be good to revisit the decision to conflate "staging" with "flaky" since we seem to be introducing a lot of complexity to achieve that, and I don't fully understand what the advantages are. Why can't we keep tests marked flaky running on prod? /cc @godofredoc @keyonghan

I think it would be good to revisit the decision to conflate "staging" with "flaky" since we seem to be introducing a lot of complexity to achieve that, and I don't fully understand what the advantages are. Why can't we keep tests marked flaky running on prod? /cc @godofredoc @keyonghan

There's discussion in go/flutter-staging-infra. The core reasons we moved are

Flutter's LUCI metrics were getting noise from the flaky tests, which is why we moved them to staging
This approach minimizes the environments infra has to maintain, which in turn should reduce complexity (infra only needs to maintain prod, staging, try for metrics purposes instead of cloning each for a flaky tests version)
To simplify the infra configs, ci.yaml should contain the staging configs as well
A. There's still complexity here as I haven't finished migrating the devicelab_staging starlark into the framework's ci.yaml

@keyonghan what do you think about updating the flaky issue bot to point to the flutter dashboard? We can add a query parameter to filter by the target name.

Keeping noise out of LUCI metrics sounds like a goal that could be achieved a different way. For example we could do a better job of categorizing LUCI/infra vs. build/test steps.
However, I don't really understand why making the LUCI metrics look clean is a goal by itself. Why do we need to filter noise out of the LUCI metrics?

Is it possible we keep the console for both staging and prod?

Flutter build dashboard shows builds both in staging and prod pools, and it would be handy to have a direct query support in url to show historical data. Updated the title to reflect that.
Could you help with the query support @CaseyHillers?
After that, I will update the flake bot to point to new links.

This is available via https://flutter-dashboard.appspot.com/#/build?taskFilter=Mac_android microbenchmarks
The target name will need to be url encoded.


go:linkname must refer to declared function or variable is not an error in 1.17

In version 1.17, go:linkname must refer to declared function or variable is not an error
may be should change the comment to 1.18

#51706

You are targeting a 1.17 branch which hasn't been updated for some time. The right fix is being discussed in https://github.com/golang/go/issues/55889.

You are targeting a 1.17 branch which hasn't been updated for some time. The right fix is being discussed in #55889.

I don't quite understand what is the correct fix
In the comments for the 1.17 branch,go:linkname must refer to declared function or variable will become an error in version 1.17, but in fact, version 1.18 only throws it as an error
@bcmills cound you take a look when you have time

Thanks for your interest in helping, but this CL is unnecessary. We don't care about internal comments in obsolete versions of Go.


Help re-training model

Hello!
I am able to successfully train a model with the SQUAD dataset. I want to use the output model from SQUAD training for transfer learning, so my goal is to use the SQUAD output model as a baseline and do a bit of training to adjust the weights to another dataset.
I have everything to load my other data, but I don't know how to call basic.cli so that it does uses the previous model as baseline but uses my new data for training.
The test I did is,

I preprocessed my custom data and stored it in $HOME/data/marco
Configured basic to pick up the data from there.
Trained my model on the SQUAD dataset, leaving it in the default folder
Ran the following command: python -m basic.cli --mode train - -len_opt --cluster, i.e. not specifying --noload so that it would try to load the existing model

However I get the error below, saying that it could not load a checkpoint.
How can I train on SQUAD and then re-train that baseline model over a bit more data?
Basically I want to do what in vision computer folks do for imagenet, where they train their nn on ImageNet and then transfer that learning by training on a bit of data of other sources.
  File "/home/carlosscastro/miniconda3/envs/carnd-term-master2/lib/python3.5/runpy.py", line 184, in _run_module_as _main     "__main__", mod_spec)   File "/home/carlosscastro/miniconda3/envs/carnd-term-master2/lib/python3.5/runpy.py", line 85, in _run_code     exec(code, run_globals)   File "/home/carlosscastro/bi-att-flow-ccastro/bi-att-flow/marco/cli.py", line 109, in <module>     tf.app.run()   File "/home/carlosscastro/miniconda3/envs/carnd-term-master2/lib/python3.5/site-packages/tensorflow/python/platfo rm/app.py", line 30, in run     sys.exit(main(sys.argv[:1] + flags_passthrough))   File "/home/carlosscastro/bi-att-flow-ccastro/bi-att-flow/basic/cli.py", line 106, in main     m(config)   File "/home/carlosscastro/bi-att-flow-ccastro/bi-att-flow/basic/main.py", line 23, in main     _train(config)   File "/home/carlosscastro/bi-att-flow-ccastro/bi-att-flow/basic/main.py", line 90, in _train     graph_handler.initialize(sess)   File "/home/carlosscastro/bi-att-flow-ccastro/bi-att-flow/basic/graph_handler.py", line 25, in initialize     self._load(sess)   File "/home/carlosscastro/bi-att-flow-ccastro/bi-att-flow/basic/graph_handler.py", line 51, in _load     assert checkpoint is not None, "cannot load checkpoint at {}".format(save_dir) AssertionError: cannot load checkpoint at out/basic/00/save
Thanks!

@seominjoon Any hints on how to do this would be extremely helpful! Thanks :)


Ignore Laravel's core DocBlock 'errors'

Just like this error and others which Taylor has no intentions of fixing them, Larastan should automatically ignore them as false positive when analyzing the codebase.

Larastan can use a dynamic return type extension to tell the method returns
the correct type.
On Tue, 24 Jul 2018 at 07:28, Richard Keep<EMAIL_ADDRESS>wrote:

Just like this error https://github.com/laravel/laravel/pull/4210 and
others which Taylor has no intentions of fixing them, Larastan should
automatically ignore them as false positive when analyzing the codebase.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nunomaduro/larastan/issues/87, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGZuHxECg10crSRiZl3gApdXUo9zIhtks5uJrBrgaJpZM4VcGrf
.

--
Ondřej Mirtes

If it can, then it should.

You are not using the latest version. Please update and tell me if the problem persist.

Ah, I was running an older version. I have updated to ^0.2 and the issue has been solved.


Come up with a better solution for sizing the terminal margins

See https://github.com/Microsoft/vscode/issues/44154
@joaomoreno maybe we should have SplitView add first-view and last-view classes?

Let's try to keep DOM order, so you would be able to use last-of-type, would that work?

@joaomoreno that was my first solution, "type" here means element type though, and the order of the sashes and split view views is not fixed. Typically it is split view view, sash, split view view sash, but when you remove an item multiple sashes can be at the end.

How about we put the views and the sashes into two different containers?

@joaomoreno that would work too :+1:


command issue

Some commands straight up just dont work, like .cmd, .execute and few more

.critical-enable doesnt work too

Nikibowler

the command is .set-critical

Some commands straight up just dont work, like .cmd, .execute and few more

Everything has been tested extensively. I believe the issues are probably on your end. Whatever the case may be, we are rewritting a bunch of stuff to make it more stable.

Some commands straight up just dont work, like .cmd, .execute and few more

Everything has been tested extensively. I believe the issues are probably on your end. Whatever the case may be, we are rewritting a bunch of stuff to make it more stable.

about rewriting it, would you like help? i have made an issue earlier this week related to if i could help out with this project that i retracted due to hw

Some commands straight up just dont work, like .cmd, .execute and few more

Everything has been tested extensively. I believe the issues are probably on your end. Whatever the case may be, we are rewritting a bunch of stuff to make it more stable.

about rewriting it, would you like help? i had made an issue earlier this week related to if i could help out with this project that i retracted due to hw

You can do whatever you like. If you decide to help out just make a pull request.

Some commands straight up just dont work, like .cmd, .execute and few more

Everything has been tested extensively. I believe the issues are probably on your end. Whatever the case may be, we are rewritting a bunch of stuff to make it more stable.

about rewriting it, would you like help? i had made an issue earlier this week related to if i could help out with this project that i retracted due to hw

You can do whatever you like. If you decide to help out just make a pull request.

i would rather like you to tell me what files need the most corrections and issues that need to be corrected in them, it makes for a much more efficient method of improving this repo

Some commands straight up just dont work, like .cmd, .execute and few more

Everything has been tested extensively. I believe the issues are probably on your end. Whatever the case may be, we are rewritting a bunch of stuff to make it more stable.

about rewriting it, would you like help? i had made an issue earlier this week related to if i could help out with this project that i retracted due to hw

You can do whatever you like. If you decide to help out just make a pull request.

i would rather like you to tell me what files need the heaviest rewrite and issues that need to be corrected in them, it makes for a much more efficient method of improving this repo

There isn't anything that needs fixing. We are currently importing all the features to the new discord.py version so you could help with that if you want. (See branch v4-dev at resources/features)

Alternatively you could add any new feature you like if you think it would be useful. Just make sure to add it directly to v4-dev


feat: prefer desc to cmd as the fallback label

It obviously makes more sense to use the built-in description as the default label, which even eliminates a lot of repetition of require('which-key').register ...

I use this branch since almost a week and have not faced any issues so far :slightly_smiling_face:
I really like the idea of being able to register a description string for keybindings even without the which-key register function. That keeps the code more "portable" for non-which-key-users. Hope this gets merged soon

This would be very helpful for Mapx.nvim. Once this is implemented, I can remove all WhichKey specific code which would improve my plugin's performance and make the code much cleaner.

I migrated to Lua a few days ago and I've been using this branch. No problems so far.

Totally makes sense. Thank you!


Fix launchPagingStore

Closes #602
Description
The cause of #602 is we were not synchronizing updates to single items with the collection they belong to. This PR fixes that by handling the streaming and updating of single item data within a collection.
Other changes:

Introducing Pager, PagingData, Joiner, Streamer, and KeyFactory interfaces. I think this is cleaner, easier to reason about, easier to test.
Moving launchPagingStore into RealPager implementation.
Emitting a state flow of PagingData rather than StoreReadResponse. My thought is this will make it easier to support UI-level extensions, similar to collectLazyPagingItems.

Type of Change

[x] Bug fix (non-breaking change which fixes an issue)
[x] This change requires a documentation update

Test Plan

Unit tests

Checklist:
Before submitting your PR, please review and check all of the following:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my change is effective
[x] New and existing unit tests pass locally with my changes

Additional Notes:

I removed the original design doc from the source code. It is still attached to the PR that introduced paging. I am working on #595 and plan to include documentation on paging internals.
@digitalbuddha @yigit  - I'm launching a child coroutine for each single in a collection. I think this will not scale well for apps with lots of data. We should think about limiting the number of concurrent coroutines and cancellation strategies.

Closing. See #611


Couldn't close synapse

I'm wondering how I can close synapse if I dont wanna use it. Thanks

Same issue on Brackets 1.6 and Synapse 1.2.90; once synapse is opened on the left can't close it to return to Brackets file list.

sorry for delay response.
ic, please tell me the step for represent to the issue little more.
or please try relaunch bracket with only the synapse.


Set msrv as 1.58

Close #58
If the version of rustc is lower than 1.58, it will give a hint like this:
cannot be built because it requires rustc 1.58 or newer, while the currently active rustc version is 1.57.0

I would also like to see this merged, as I've run into the same problem when trying to package for myself for NixOS stable.


Have 'i' buttons next to various upload fields to describe what it does

Similar to what the Upload Wizard does, I think doing this might make it easier for new contributors to learn? For instance the 'i' button next to the Title field says "A unique descriptive title for the file, which will serve as a filename. You may use plain language with spaces. Do not include the file extension.", which could help clear up the title vs filename confusion.

I'm looking into this.

Note: the (I) on the right side of the Title field. When the (I) is clicked a message shows at the bottom part for short period and disappears.

Looks good!
On Thu, Jul 27, 2017 at 6:20 PM, The B<EMAIL_ADDRESS>wrote:

Note: the (I) on the right side of the Title field. When the (I) is
clicked a message shows at the bottom part for short period and disappears.
[image: screenshot_1501146435]
https://user-images.githubusercontent.com/26868644/28663016-d0005708-72c4-11e7-867b-bb20addb8c5c.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/commons-app/apps-android-commons/issues/701#issuecomment-318307618,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGFBoKTBgUXQArWvVhfB0AY6xayBqLeks5sSFZBgaJpZM4Np6A6
.

What message should follow the "Description" field?

How about something like this? :
Please describe the media as much as possible: Where was it taken? What
does it show? What is the context? Please describe the objects or persons.
Reveal information that can not be easily guessed, for instance the time of
day if it is a landscape. If the media shows something unusual, please
explain what makes it unusual.
On Thu, Jul 27, 2017 at 6:56 PM, The B<EMAIL_ADDRESS>wrote:

What message should follow the "Description" field?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/commons-app/apps-android-commons/issues/701#issuecomment-318316345,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGFBia18iJ5n78R_EnMXPHpsFpSKFTVks5sSF6zgaJpZM4Np6A6
.

The official doc at
https://commons.wikimedia.org/wiki/Commons:First_steps/Quality_and_description#Good_file_descriptions
does not contain much.
On Thu, Jul 27, 2017 at 7:16 PM, Nicolas Raoul<EMAIL_ADDRESS>wrote:

How about something like this? :
Please describe the media as much as possible: Where was it taken? What
does it show? What is the context? Please describe the objects or persons.
Reveal information that can not be easily guessed, for instance the time of
day if it is a landscape. If the media shows something unusual, please
explain what makes it unusual.
On Thu, Jul 27, 2017 at 6:56 PM, The B<EMAIL_ADDRESS>wrote:

What message should follow the "Description" field?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/commons-app/apps-android-commons/issues/701#issuecomment-318316345,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGFBia18iJ5n78R_EnMXPHpsFpSKFTVks5sSF6zgaJpZM4Np6A6
.

Title Information

Description Information

The text you have chosen is mostly for people who upload scientific images,
which are very unlikely to be taken with a smartphone.
On the opposite, people with smartphones are much more likely to take
pictures of live events and points of interest.
On Thu, Jul 27, 2017 at 7:49 PM, The B<EMAIL_ADDRESS>wrote:

Title Information
[image: screenshot_1501152273]
https://user-images.githubusercontent.com/26868644/28667020-584279b8-72d2-11e7-90e9-fcaeff949120.png
Description Information
[image: screenshot_1501152113]
https://user-images.githubusercontent.com/26868644/28666949-1ac67ec2-72d2-11e7-8329-c5e3d58c0829.png
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/commons-app/apps-android-commons/issues/701#issuecomment-318327997,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGFBsbIBDbQ2IVQsT_4ElOOoTMNr8Oiks5sSGtQgaJpZM4Np6A6
.

I've made the changes to the text according to text @nicolas-raoul posted above.


Dataset file formats

Core Hunter 1 and 2 only supported multi-allelic marker data in frequency format. The frequency table was given as marker-allele x individuals which is unconventional. For Core Hunter 3 we will follow the convention of individuals x markers. Additional formats are defined, including those for phenotypic datasets and precomputed distance matrices.
Multi-allelic marker data

CH1/2 format but transposed. One row per individual. One column per combination of marker and allele. Entries are allele frequencies. There is one header column (individual names) but two header rows (1 = marker names, 2 = allele names).
Simplified format for diploid datasets with two columns per marker. Entries are allele numbers/IDs/names. There is only one header row with marker names (each twice consecutively). Optionally, the two columns corresponding to the same marker may be named something like M5.1-M5.2, M17a-M17b, etc. but they should share a prefix which is unique across all markers.

Bi-allelic marker data
Single format: 0/1/2 individual x marker matrix. A number of tools exist to do conversions here if needed before running Core Hunter. One header column (individual names) and one header row (marker names).
Phenotypic data
Single format: individuals x traits. One header column (individual names) and one compulsory header row (trait names). Optionally, a second header row can be added which specifies the variable type of each trait (nominal, ordinal, ratio, interval, binary, ...). If this row is not included in the file, variable types must be set manually when running Core Hunter (through R or the GUI).
Precomputed distance matrix
Single format: symmetric distance matrix entries, row-wise, top to bottom. There is one header row (individual names). It is allowed to truncate the rows after the diagonal. The diagonal only contains zeros and should always be included. If entries of the upper diagonal part are included, it is verified whether they match the lower diagonal part. If they are truncated, the upper diagonal part is filled in by copying values from the specified lower diagonal part.

Perhaps we should make the second header row for phenotypic data compulsory as well (variable types). This would simplify reading the data from a file since we know in advance what kind of values (string, integer, double, boolean, ...) are expected in each column.
@cropinfo What do you think?

@daveneti I updated the descriptions according to my recent changes. I got the impression that you didn't fully understand the diploid (now phased) format, since it is not required that the number of possible alleles is fixed. The number of columns corresponds to the ploidy, not the number of possible alleles. Is the (updated) format clear to you now?

Thanks for the update.
What a meant to say was the maximum number of observed alleles in a one individual was fixed. Perhaps this was not clear enough. Yes, the ploidy is a factor in this, but some markers can be tricky. For example, wheat is not considered a diploid. It's a hexaploid, but the with genome specific markers the number of possible observed alleles per individual is two. So your statement below would cause confusion.
Be careful with the term 'phased' this is related to inheritance of the allele. For example, if you take phase into account then the score AC is different from CA. At the moment this difference is not possible detect using common genotyping methods.
I will review the descriptions as soon as I can.
Guy

On 22 Apr 2016, at 13:16, Herman De Beukelaer<EMAIL_ADDRESS>wrote:
@daveneti I updated the descriptions according to my recent changes. I got the impression that you didn't fully understand the diploid (now phased) format, since it is not required that the number of possible alleles is fixed. The number of columns corresponds to the ploidy, not the number of possible alleles. Is the (updated) format clear to you now?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

Ok I see what you meant. I was not aware about the subtleties like in your example from wheat.
I used the term 'phased' deliberately because in that format you can make a distinction between e.g. AC and CA. But perhaps it is confusing because you don't really need to know the phase to use the format, since you can include the columns in any order and it won't make a difference for Core Hunter.
Do you have a suggestion for a better name?

I have been thinking about it all morning. I will proposal soon.

On 23 Apr 2016, at 09:27, Herman De Beukelaer<EMAIL_ADDRESS>wrote:
Ok I see what you meant. I was not aware about the subtleties like in your example from wheat.
I used the term 'phased' deliberately because in that format you can make a distinction between e.g. AC and CA. But perhaps it is confusing because you don't really need to know the phase to use the format, since you can include the columns in any order and it won't make a difference for Core Hunter.
Do you have a suggestion for a better name?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

Great, thanks a lot!

Ok, I think is a naming issue only correct? We have three formats if I am not mistaken? Or is it four? I think the one with allele names/id can be collapsed in to one?
I propose we follow a naming approach consistent with ‘application’ of the data.
The 0,1,2 format is easy. Is only useful for bi-parental populations where you can encode 0 for one parent, 2 for another and 1 for heterozygote. BI_PARENTAL would be a better name than BI_ALLELIC in this case
The ‘frequency’ one also quite easy. If must be used for multi-parental or bulk samples, since you need to prove the allele frequency of all possible allele. This was is original use in any case, for example the original CH data was bulked SSR data. MULTI_PARENTAL is the proposed name,
The issue is the name for the third one. It is based on allele name / ids. It is difficult to come up with a good ‘application’ specific name, since it can be used for all applications. We could cheat on the name in this case. Perhaps call it STANDARD or something?
Guy

On 23 Apr 2016, at 09:27, Herman De Beukelaer<EMAIL_ADDRESS>wrote:
Ok I see what you meant. I was not aware about the subtleties like in your example from wheat.
I used the term 'phased' deliberately because in that format you can make a distinction between e.g. AC and CA. But perhaps it is confusing because you don't really need to know the phase to use the format, since you can include the columns in any order and it won't make a difference for Core Hunter.
Do you have a suggestion for a better name?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub https://github.com/corehunter/corehunter3/issues/21#issuecomment-213692726

Yes there are only three formats. The one with allele names/ids is already collapsed into a single format where the number of columns per marker is automatically inferred from the column names.
I like the suggestion to call the allele name/id format STANDARD (or maybe DEFAULT?). We can then also effectively treat it as the default format. Now frequency format is default but since it is more elaborate and only needed for bulk samples I think it makes sense to change the default. This also corresponds to the datasets that I have seen (like the one from PowerCore).
I am not so convinced about your other suggested changes though and would prefer to keep FREQUENCY and BIALLELIC since they are very clear.

I agree DEFAULT is ok
FREQUENCY I can live with,
BIALLELIC I don’t like too much, it is really BIPARENTAL. You need to know the parental line allele calls to use this format. You could still have a data with only two alleles but if it is not from a bi-parental population then it is not really correct to use format.
Guy

On 23 Apr 2016, at 11:29, Herman De Beukelaer<EMAIL_ADDRESS>wrote:
Yes there are only three formats. The one with allele names/ids is already collapsed into a single format where the number of columns per marker is automatically inferred from the column names.
I like the suggestion to call the allele name/id format STANDARD (or maybe DEFAULT?). We can then also effectively treat it as the default format. Now frequency format is default but since it is more elaborate and only needed for bulk samples I think it makes sense to change the default. This also corresponds to the datasets that I have seen (like the one from PowerCore).
I am not so convinced about your other suggested changes though and would prefer to keep FREQUENCY and BIALLELIC since they are very clear.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub https://github.com/corehunter/corehunter3/issues/21#issuecomment-213713935

What if we just call that format SNP? Or are there other marker types for which it would be used?
Else I will trust you on BIPARENTAL. I don't really get the difference but perhaps you can explain when we meet.
What do you prefer: SNP or BIPARENTAL?

SNP is more a type of marker system. You can use SNP to get 0,1,2 data, but also SNP can used to get the other two formats. Conversely, you could use other marker systems e.g. SSR to get 0,1,2 data if you have a bi-parental cross.
I prefer BIPARENTAL for the 0,1,2 format. I will run it past someone from work to double check, but it is my understanding that you can not use the 0,1,2 format with anything but bi-parental crosses.
Guy

On 23 Apr 2016, at 11:38, Herman De Beukelaer<EMAIL_ADDRESS>wrote:
What if we just call that format SNP? Or are there other marker types for which it would be used?
Else I will trust you on BIPARENTAL. I don't really get the difference but perhaps you can explain when we meet.
What do you prefer: SNP or BIPARENTAL?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub https://github.com/corehunter/corehunter3/issues/21#issuecomment-213715101

@daveneti I updated the descriptions -- can you verify?

@hdbeukel I believe this issue is now fixed?

Yes this issue is fixed. I'll close it.


Dockerfile for running nougat FastAPI server

I add Dockerfile for running nougat FASTAPI server easily.
Also write README.md for running API server via Dockerfile.

lgtm thanks


feat: esm support

closes #124
TODO

[x] docs
[x] tests

Codecov Report

Merging #127 (4502247) into main (a27fc1a) will increase coverage by 0.30%.
The diff coverage is 47.05%.

@@            Coverage Diff             @@
##             main     #127      +/-   ##
==========================================
+ Coverage   47.27%   47.57%   +0.30%
==========================================
  Files          30       30
  Lines         495      515      +20
  Branches       97      103       +6
==========================================
+ Hits          234      245      +11
- Misses        241      250       +9
  Partials       20       20

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@next-major dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


CircleCI: Create and Use Custom Docker Image

CircleCI, which we have set up in #13 supports custom Docker images so it is better to build a custom image with Intel SGX SDK and Go on Ubuntu 16.04 than to do everything in .circleci/config.yml.
A problem on using a custom image is that we need to have a Docker Registry or to manage an account of Docker Hub.

To do:

[Doing in the chat] Ask an administrator to install "Docker Hub Registry" application in hyperledger-labs organization of GitHub
[Waiting the first item] Update configuration of Docker Hub to refer hyperledger-labs/minbft for automated build (ynamiki/minbft is used now)

The above to-do items has been done. I have configure an autometed build from this repository.

CircleCI was failed because it could not get the image. I will take a look.
https://circleci.com/gh/hyperledger-labs/minbft/tree/master

@ynamiki (just off-topic comment...) sorry for letting you close this issue manually. I added the reference "solved #16" in merge commit message, but according to https://help.github.com/articles/closing-issues-using-keywords/, the word "solved" is not a magic word. I'll use right word if I'll do merge operation next.

@Naoya-Horiguchi No problem. It was my task to add the magic word in my commit comment.


MAINT: fix usage of deprecated Numpy C API in signal

are there more deprecated uses in scipy? instead of doing it by hand it seems these type of changes can be handled automatically with a coccinelle patch: http://coccinelle.lip6.fr/

urg a patch handling only three cases alreade produces a 438 insertions(+), 396 deletions(-) diff :/
@@ PyArrayObject *arr; @@
- arr->nd
+ PyArray_NDIM(arr)

@@ PyArrayObject *arr; @@
- arr->descr
+ PyArray_DESCR(arr)

@@ PyArrayObject *arr; @@
- arr->dimensions
+ PyArray_DIMS(arr)

@juliantaylor coccinelle is pretty slick!  Thanks for the pointer.  I'm experimenting with it now in scipy/integrate.

@juliantaylor looks interesting. I did this with some Vim macros but checked all the changes manually. There are some gotchas, like xxx->strides needing to be changed to PyArray_STRIDES only if xxx is an array and not if it's an iterator. Would coccinelle be able to handle that kind of thing?

yes coccinelle is type aware and knows the C invariants, it can replace only those xxx->strides where xxx is of a certain type, it is incredibly powerful (see the many examples) but for non trivial transformations it has a steep learning curve. But these simple member access -> function call replacements are easy, you run the patch I posted above with:
spatch --sp-file file.patch --in-place file
# for the full tree with gnu parallel:
find . -name "*.c*" | parallel spatch --in-place --sp-file file.spatch

@juliantaylor thanks! I'll play with it

Looks like we'll do the rest of Scipy with Coccinelle, but since this was pretty much done I just fixed the few issues pointed out by Warren.

TravisCI failure was one timeout - everything else is green. Should be good to go.

Going to merge this soon unless there are more comments.

merged. thanks all for the feedback

Thanks, Ralf.

have you made some changes to the coccinelle patch? I wanted to give it some more polish too, maybe a shared gist would be useful

@juliantaylor not yet. This PR I still did the old-fashioned way.
For the other modules, I plan to do that by a single Coccinelle patch, one module at a time. I think one commit for each Coccinelle change and then a second commit to clean up indentation, break lines to 80 chars, etc. And if needed fix build warnings - I noticed that macros like PyArray_DATA give new warnings because parameters are declared as const - needs extra casts.

@juliantaylor: I experimented a bit with this:
@@ PyArrayObject *arr; @@
- (arr)->nd
+ PyArray_NDIM(arr)

@@ PyArrayObject *arr; @@
- (arr)->dimensions
+ PyArray_DIMS(arr)

@@ PyArrayObject *arr; @@
- (arr)->data
+ PyArray_DATA(arr)

@@ PyArrayObject *arr; @@
- (arr)->strides
+ PyArray_STRIDES(arr)

@@ PyArrayObject *arr; @@
- (arr)->flags
+ PyArray_FLAGS(arr)

@@ PyArrayObject *arr; @@
- (arr)->descr->elsize
+ PyArray_ITEMSIZE(arr)

@@ PyArrayObject *arr; @@
- (arr)->descr
+ PyArray_DESCR(arr)

For this file:
int func(int k)
{
    PyArrayObject *p;
    PyArrayObject **q;
    npy_intp *strides;
    npy_intp *dims;
    npy_intp ndim;
    int flags;
    double *data;

    data = p->data;

    data = (p)->data;

    data = (*q)->data;

    data = (*(q))->data;

    k = p->descr->elsize;

    flags = p->flags | 1;

    strides = p->strides;

    ndim = p->nd;

    k = p->dimensions[0];

    p->descr;

    return k & (*q)->flags;
}

the diff looks OK:
--- tmp.c
+++ /var/folders/p9/j_v_3wvd2bx5ftq544pvvf1w0000gn/T/cocci-output-24538-a96123-tmp.c
@@ -9,25 +9,25 @@ int func(int k)
     int flags;
     double *data;

-    data = p->data;
+    data = PyArray_DATA(p);

-    data = (p)->data;
+    data = PyArray_DATA(p);

-    data = (*q)->data;
+    data = PyArray_DATA(*q);

-    data = (*(q))->data;
+    data = PyArray_DATA(*(q));

-    k = p->descr->elsize;
+    k = PyArray_ITEMSIZE(p);

-    flags = p->flags | 1;
+    flags = PyArray_FLAGS(p) | 1;

-    strides = p->strides;
+    strides = PyArray_STRIDES(p);

-    ndim = p->nd;
+    ndim = PyArray_NDIM(p);

-    k = p->dimensions[0];
+    k = PyArray_DIMS(p)[0];

-    p->descr;
+    PyArray_DESCR(p);

-    return k & (*q)->flags;
+    return k & PyArray_FLAGS(*q);
 }

Ralf, I've started making similar changes in scipy.integrate, but I don't want to duplicate any work you might have in progress.  Are you already working on a similar change for scipy.integrate?

No, I haven't done much more of this on any module recently. Please go ahead.


Spin on the y axis,but the center of the rotation is not the center point of the 3D model itself

I want to rotate on itself y axis.I render the interface via obj+mtl. I want an object3D to rotate on its own y axis, but the center of rotation is incorrect. Do I need to re-export the obj+mtl file? The center of rotation is not the center point of a 3d object. autorotation becomes revolution
  apertureRingObject.rotateY(rotate);

Hi @changning420,
Depending on your obj file your rotation of your mesh is at the center of the volume. I would import your file into blender and see what the center is there. If it is off in blender you will need to modify your files.
or you could try to find the center point and do something like this
void rotateAboutPoint(Object3D obj, Vector3 point, Vector3 axis, double theta, [bool pointIsWorld = false]){
    if(pointIsWorld){
        obj.parent.localToWorld(obj.position); // compensate for world coordinate
    }

    obj.position.sub(point); // remove the offset
    obj.position.applyAxisAngle(axis, theta); // rotate the POSITION
    obj.position.add(point); // re-add the offset

    if(pointIsWorld){
        obj.parent.worldToLocal(obj.position); // undo world coordinates compensation
    }

    obj.rotateOnAxis(axis, theta); // rotate the OBJECT
}

Hope this helps

@Knightro63 Yes! That's right. That works very well. Thank you


HTML Forms

Description 📜
I will explaining in detail about HTML forms and the different attributes related to it.

Domain of Contribution 📊

[X] Frontend Dev HTML/CSS/JS

/assign

/assign document

/assign

/assign document

/assign

/assign


Fixed typo for Electron Fiddle version 0.20.0.

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

/azp run

/azp run


[mlir] Replaced find_library with find_package to locate MLIR static library

https://github.com/ROCmSoftwarePlatform/llvm-project-private/issues/640

There is a failure potentially caused by the assembly format changes.
'func' mismatches with 'func.func'
Can we remove checking the IR output string in the test?


Convert to Kotlin

I think it will be easier to upgrade to the latest lsd dependencies if this project is converted to kotlin because the builders have been removed so having named parameters could be helpful.

I'm nearly done converting it. I have only component tests left to do. Should be finished soon... 🤞


0 ctime/mtime/atime?

Someone reported on mac files being created with a '1970-01-01' ctime/mtime — that's probably bad.
Maybe it's encoded in the 'mode' we create files with? we could binary-and it with something more strict.

we could binary-and it with something more strict.

We do that now

Someone reported on mac files being created with a '1970-01-01' ctime/mtime — that's probably bad.

Haven't seen that in a while


Example config for Source Initiated forwarding?

Can I get an example of how source initiated forwarding would be configured via DSC?
I set up a basic configuration but it fails with error "threw one or more non-terminating errors while running the Set-TargetResource functionality."
configuration SetupCollector
{
Import-DscResource -ModuleName xWindowsEventForwarding
xWEFCollector Enabled
{
Ensure = "Present"
Name = "Enabled"
}
xWEFSubscription SecurityEvents
{
SubscriptionID = "Security events"
SubscriptionType = "SourceInitiated"
DependsOn = "[xWEFCollector]Enabled"
LogFile = "ForwardedEvents"
Query = @('Security:*')
AllowedSourceDomainComputers = 'O:NSG:NSD:(A;;GA;;;DC)(A;;GA;;;NS)'
}
}
SetupCollector
From what I saw in the MSFT_xWEFSubscription.psm1, the permission for AllowedSourceDomainComputers is set by default. But omitting the value also causes the configuration to fail.

Could you please provide the verbose output and the error message that is thrown?
Is this the same issue as #9?


New arch 'RNPaymentsSpec.h' file not found

Looks like not working with the new arch:
"react-native": "0.75.2"

Today I updated to the last ver. 0.75.3 and do RCT_NEW_ARCH_ENABLED=1 bundle exec pod install, then I see that RNPaymentsSpec is generated ok
However, the previous version does not generate the RNPaymentsSpec. I tried several times but had to do RCT_NEW_ARCH_ENABLED=0


Trying to update purview contacts (expert and owner) but not able to do it

Describe the bug
Behavior is weird as it appears as it succeed, but when I go to purview entity contacts are not there, but when I go to filters I can filtered by those contacts. not sur if purview bug or sdk.
To Reproduce
Steps to reproduce the behavior:
I'm using this code
actual_entity = AtlasEntity(
name=name,
qualified_name=qualified_name,
typeName=typeName,
attributes={
"userDescription": description
},
guid=guid,
contacts ={"Expert":[{"id":"aad-id-of-some-user", "info":""}], "Owner":[]}
)

do you know if there is a near release date?

nope ive been waiting for one since august

@Sgidwani61 @vjcuadros Thank you both for your extreme patience.  I just published a new release and it is now available on PyPi with the fix.    Thank you both for your continued use of PyApacheAtlas!


feat(VIST-CPC-913): sorting visits into status tables

JIRA: link to jira ticket
https://champlainsaintlambert.atlassian.net/browse/CPC-913
Context:
This ticket is regarding making updates to the Visit-List UI. Our team thought it would be an interesting idea to separate visits into more than just a single table and, to compliment our recent implementations of status-button functionalities, we thought it would be best for these tables to be based on visit status. We now have a total of four tables: Upcoming Visits, Confirmed Visits, Cancelled Visits and Completed Visits.
Changes

Tweaks to the controller.js file were made to push visitData to the appropriate status table
Three new status tables were added to the html template (aside from our original upcoming visits table that was previously implemented)
Styling modifications were made to make the UI maintain consistency and be more visually appealing

Before and After UI (Required for UI-impacting PRs)
Before changes:

After Changes:

After all visits are removed from a particular table:

Dev notes (Optional)

A table that has no visits in it will be hidden until a new one is eventually added to it. This is possible through the use of ' ng-show="$ctrl.table.length > 0 '

Could the filters be added to all the tables?

To avoid duplicating the tables multiple times, would it be better to have 1 visits table and add a dropdown to select the status instead of a filter to sort for only 1 type of visit?

Could the filters be added to all the tables?

I believe we discussed this in the previous scrum but I could be mistaken. For the filters, if one is in use then it automatically filters all the visits we are searching for in all tables it is present in (if for example we would search by a date, then all visits with that date will be highlighted in all tables in the UI). I thought it would maybe be unnecessary to have the same search filters on each table but we'll discuss it and could add it again in a future pr if.


Update Uglifier, pin to a newer version

I rule and have completed some work on Case Manager that's ready for review!
Just a tiny PR that updates one of our out of date dependencies. Uglifier was on 3.1.0, this moves to 3.2.0 which is just tiny changes in what version of Uglifier is used. It also pins Uglifier to above 3.2.0 for the time being
Report of dependencies can be seen here: https://gemnasium.com/github.com/DCAFEngineering/dcaf_case_management
This pull request makes the following changes:

Updates Gemfile and Gemfile.lock

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1027   +/-   ##
=======================================
  Coverage   95.54%   95.54%
=======================================
  Files          48       48
  Lines         898      898
=======================================
  Hits          858      858
  Misses         40       40

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 188a23b...72a0673. Read the comment docs.


RFC: Redesign how progress bars are added to MultiProgress

I believe the current MultiProgress API is error-prone and too easy to "hold wrong", and would like to suggest a small-ish redesign.
MultiProgress exists primarily to coordinate draws of multiple ProgressBars.
With the current API, you create a ProgressBar and add it to the MultiProgress. These are two discrete steps:
let mp = MultiProgress::new();

// possibly other pbs added here too...

let pb = ProgressBar::new(100);
// <--- (1)  danger!
mp.add(pb);

The problem is that it is very easy to accidentally cause the ProgressBar to be drawn before it is added to the MultiProgress, i.e. at the spot marked (1). The most common offender is enable_steady_tick (for spinners). But lots of other methods (e.g. set_message) can cause a draw too.
If the MultiProgress has been drawn by the time we get to (1), then it is already game over: pb has likely corrupted the screen.
Off the top of my head, the most recent occurrences I've seen are listed below (I could have sworn there are more, but I can't find them):

https://github.com/console-rs/indicatif/issues/502
https://github.com/console-rs/indicatif/issues/645

The safe "fix" is to ensure ProgressBars are only mutated/customized after being added to MultiProgress. For example:
let mp = MultiProgress::new();

// possibly other pbs added here too...

let pb = mp.add(ProgressBar::new(100));
// no problem touching `pb` here

However, I think we can do better by ensuring the ProgressBars destined for a MultiProgress are never prematurely touched in the first place. We could replace MultiProgress::add with add_pb/add_progress and add_spinner methods to MultiProgress. (Similarly, insert_spinner_before, insert_pb_after, etc.)
let mp = MultiProgress::new();

// possibly other pbs added here too...

let pb: ProgressBar = mp.add_pb(100);

// no possibility of touching pb before we should

Obviously, this breaks backwards compatibility. But I think it will save users from a lot of troubleshooting and annoyance in the long term.
Another option would be to create some kind of proxy with a ProgressBar-like API, but which defers customizations/draws until added to a MultiProgress. Then change MultiProgress to only take those instead of ProgressBar. Example:
// other name options: DeferredProgressBar, ProgressBarBuilder, ???
let pbp: ProgressBarProxy = ProgressBarProxy::new_spinner();
pbp.enable_steady_tick(Duration::from_secs(5));   // <--- this call doesn't start the tick yet, just notes it down for later

let pb: ProgressBar = mp.add(pbp);  // <--- all customizations applied after internalizing `ProgressBar`

This might be a little nicer for users, at the cost of more implementation effort.

@djc  Interested in any thoughts you have on this, when you have time :).

BTW in the past I have tried to explain my concerns about MultiProgress with a hand-wavy "MultiProgress can't know if the ProgressBar has already been drawn", ala https://github.com/console-rs/indicatif/issues/502#issuecomment-1366016287. This RFC is my attempt to give more concrete reasons.

Would be great to make this harder to break, thanks for writing this up!
I think we'd want to avoid combinatorial API explosion which add_progress() / add_spinner() / insert_spinner_before() / .. might trigger? If we're building a bar we should keep the API similar to bar creation.
I also think making things nicer for users at the cost of a little more code to maintain is probably worth it. I don't like the ProgressBarProxy name much, MultiBar seems like a decent concise way of expressing what it's for? The challenge will be avoiding duplicate stuff as much as possible.
I also think we should try to first expose this in a semver-compatible update, guiding users to the new API by way of #[deprecated] so we can see how things shake out, and then kill old/duplicate API in a future 0.18 release.

Would be great to make this harder to break, thanks for writing this up!
I think we'd want to avoid combinatorial API explosion which add_progress() / add_spinner() / insert_spinner_before() / .. might trigger? If we're building a bar we should keep the API similar to bar creation.
I also think making things nicer for users at the cost of a little more code to maintain is probably worth it. I don't like the ProgressBarProxy name much, MultiBar seems like a decent concise way of expressing what it's for? The challenge will be avoiding duplicate stuff as much as possible.
I also think we should try to first expose this in a semver-compatible update, guiding users to the new API by way of #[deprecated] so we can see how things shake out, and then kill old/duplicate API in a future 0.18 release.

Sounds like a plan, and I like the name MultiBar.
Definitely agreed regarding the combinatorial explosion. As a first attempt, I think I can write some kind of macro to slap on ProgressBar to generate MultiBar automatically. I'll try to take a stab at it over the next few weeks during US holiday break.

I don't love macros for this kind of thing but I guess it might be the best way to deduplicate.

I don't love macros for this kind of thing but I guess it might be the best way to deduplicate.

I'll try with and without. I also don't love macros since they tend to break code completion in my IDE (RustRover).


Added support for Linux Mint 19.3

I wanted to install pivpn onto my Linux Mint installation. Here are the changes I've made to get it to install. I have only tried with the OpenVPN option and haven't tried to uninstall so I cannot confirm that those areas work. I would think so since Linux Mint is based on Ubuntu.

Unfortunately not. I hope that they will add support for Pi someday. I know pivpn wasn't ment to be for desktop but it seems to work fine. My Pi died a couple of days ago and I wanted to get my VPN back up and pivpn makes it way easier to setup. I see someone else is also requesting Mint support on issue #1038

Sorry ... not accepting this one, for multiple reasons ...
1 - lack of testing ...
2 - Mint is based on debian so it should give you a warning but it should work anyway.
3 - We cannot keep up with the releases of every distribution ... so we are sticking with 2 main ones .. ubuntu and debian for now.
4 - Mint doesn't run on a Pi, support for ubuntu, reason why ubuntu is supported is because it runs also in most inexpensive VPS thus allowing those who want a VPN offshore to have it using pivpn.
5 - Mint is a desktop distribution therefore not the right place to run a VPN server and would be against our posture of encouraging security and privacy best practices to allow such a thing.
Once again sorry for refusing but hope you understand.
Kind regards.

@4s3ti Probably Mint gives a fatal error since it's not "Debian", "Ubuntu", "Raspbian" in the release file. Agree with the rest. At best there could be an argument like --skip-unsupported to force proceeding.

@orazioedoardo There were no errors while installing; at least not for the OpenVPN option. I haven't tried the WireGuard option but that would probably work as well. Mint is based on Ubuntu and uses many of it package repos. All of the pivpn commands have been working without issue.
That being said, I understand the reasoning for not merging this pr. Supporting many distros would be a pain. I do like to idea of a --skip-unsupported though or maybe a --allow-unsupported.

Get the based of Linux Mint version you use and add it into the installation file if they are supported, for example for LM 19.3 as following:
OSCN="bionic"
PLAT="Ubuntu"
The file here contains this:
install.sh.zip
Please be aware not to use his file in other environment!
A better way is to modify the installer by adding "LinuxMint" and "tricia" version all over the file side by side with "Ubuntu" and "bionic".

As a user : making a VPN install script in order to simplify the VPN installing process is a neat progress...and definitely "fitted" for desktop distro users that dont want to spend hours.
My experience is that I have it installed on a dedicated machine at home with a Ubuntu LTS installed on it. I dont plan to install a Debian since I dont find it "Out of the box" enough. What I want is to install a distro and use it to do what I have to do with it, not spend hours installing it.
Mint has my preference over Ubuntu and has a significant share in terms of users now, and it would seem relevant for me to make piVPN run on it.
Power users dont need a script to run a VPN. People who are definitely happy to use PiVPN are noobs like I am, who are likely to use a distro like Mint.


made get_cooldown_with_key async for consistency, added reset_with_ke…

…y and get_cooldown_time_with_key
Pull Request Type

[x] Feature addition
[ ] Bugfix
[ ] Documentation update
[ ] Code refactor
[ ] Tests improvement
[ ] CI/CD pipeline enhancement
[x] Other: For consistency, get_cooldown_with_key is async

Description

Cooldown resets with keys was a problem I had earlier; this solution is useful.
I made get_cooldown_with_key async for consistency as I said, so one doesn't have to remember which one is which.
await command.cooldown.reset_with_key(other_user)
await command.cooldown.get_cooldown_time_with_key(other_user)
vsc pylance did NOT complain.
Changes

made get_cooldown_with_key async
added reset_with_key
added get_cooldown_time_with_key

Related Issues

none
Test Scenarios

none
Python Compatibility

[ ] I've ensured my code works on Python 3.10.x (I don't have an installation of this.)
[x] I've ensured my code works on Python 3.11.x

Checklist

[x] I've run the pre-commit code linter over all edited files (couldn't install idk why but vsc pylance gave no problems) (Github pre-commit workflow)
[ ] I've tested my changes on supported Python versions (3.11)
[ ] I've added tests for my code, if applicable
[ ] I've updated / added  documentation, where applicable

These don't need to be async - all doing that does is limit what situations you can use these methods

Yes that's true, I will remove async. When I was going through the other files though I'm pretty sure I saw a "this doesn't really need to be async, but it is for consistency." or something to that extent. I will remove async, if you already haven't made it non-async I can fix that too.

Yeah, that method was a contentious point for ux. Rule of thumb is if it doesn't need to be async, it shouldn't be - however yes reset_all is an outlier and as changing it would be a breaking change, it remains

Alright then I will return it to the way it was (reset_all only).

Could you check it on 3.10 for me?

How do I update documentation?

haha, index.md still said bot.load! I fixed it to bot.load_extension.

Your last change was out-of-scope. please revert it and create a new pr for that

Alright.


Included documentation for crossfilter.js

Added a brief introduction and set up instructions.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.

Duplicate of # 32677


SocketException is not being retried

Might be related: https://github.com/reportportal/commons-net/issues/18

It seems nunit engine successfully executed ReportPortalListener.FinishRun(), and is waiting until it finishes. May be nunit has some timeouts for listeners, need investigate this part.


Modularize mux and demux

mux and demux are some awesome util functions. It would make a lot of sense to take it out of this project as a standalone dependency.

Hmmm. That's very interesting proposal. I don't see it impossible to extract core transforms into separate module, e.g @tsers/prelude. It might even clear the codebase.

@milankinen Does it have to be a part of tsers? I mean, it could be a completely different module which is stream agnostic too.

mux and demux use only map and filter so that is indeed possible! Do you want to create a new npm module and copy those functions into it (it's fine for me)? Or do you want that I'll do that?

@milankinen I would be glad to create a separate module. What would you want to call it?

That is a hard question. Something related to signal processing perhaps? I'm counting on your judgement in this matter. 😄

Here it is — https://github.com/tusharmath/muxer

Nice 👍

@milankinen What is the purpose of demuxCombined in this module? I have not seen it being used in anywhere and quite a lot of test cases have been written for it.

@tusharmath check tsers-js/examples

demuxCombined must be used if you have an observable containing an array of muxed observables (usually when you're dealing a list).
Like @pmros pointed out, an example usage can be found here: https://github.com/tsers-js/examples/blob/86810a6cbe76e63cf35493a7005fe9547ec62b48/examples/counter-list/index.js#L32-L43

@milankinen This should too be out of the package isn't it?

It's up to you to decide that. 😄  I'm fine with both options (in/out).
There is not much code, though: https://github.com/tsers-js/core/blob/master/src/index.js#L72-L78


[BUG] Unable to craft or see Jetpacks in Fabric 1.20.1

Mod is shown in Mod Menu, but content isn't available in-game. It cannot be seen using JEI or REI nor in creative inventory.

I've the same bug


Construct databases for all profilers from the same input refseq data

Construct databases using the same refseq data as the kraken2 database which includes

complete genome, chromosome, scaffold and contigs
Archaea, Bacteria, viral, protozoa, fungi, plasmid, human (GRCh38 &T2T),  UniVec_Core

kraken2 database can be downloaded from https://benlangmead.github.io/aws-indexes/k2
The list of refseq sequences is stored in the tsv file: https://genome-idx.s3.amazonaws.com/kraken/pluspf_20231009/library_report.tsv
Update databases whenever the kraken2 database is updated.
This issue can be closed after construction these databases:

[x] diamond
[ ] kaiju
[ ] centrifuge
[ ] krakenuniq
[ ] kmcp
[ ] ganon
[ ] sourmash

kaiju The db construction failed due the memory limit, 450GB on hasta. I am trying to build it on UPPMAX Bianca which you can book memory up to 512GB.


S3 connection timeout with IAM

Everything works perfectly when using file storage, am trying to upload to an S3 bucket but getting the following error:
[fog][WARNING] Unable to fetch credentials: connect timeout reached
[fog][WARNING] Unable to fetch credentials: connect timeout reached
[fog][WARNING] Unable to fetch credentials: connect timeout reached
   (0.2ms)  ROLLBACK
Completed 500 Internal Server Error in 181906ms

Excon::Errors::Forbidden (Expected(200) <=> Actual(403 Forbidden)
excon.error.response
  :body          => "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<Error>AccessDenied<Message>Access Denied</Message><RequestId>CCEECDDC7942972B</RequestId><HostId>IIZYUhoTtGeD1HFN50/IB3cgo9O29c5zw/UcA3WbpkNbO9bU2Wk1NrQWaa8lZnS/J+zUlLbb8WQ=</HostId></Error>"
  :headers       => {
    "Content-Type"     => "application/xml"
    "Date"             => "Wed, 30 Dec 2015 14:49:09 GMT"
    "Server"           => "AmazonS3"
    "x-amz-id-2"       => "IIZYUhoTtGeD1HFN50/IB3cgo9O29c5zw/UcA3WbpkNbO9bU2Wk1NrQWaa8lZnS/J+zUlLbb8WQ="
    "x-amz-request-id" => "CCEECDDC7942972B"
  }
  :local_address => "XX.XX.XX.XX"
  :local_port    => 60431
  :reason_phrase => "Forbidden"
  :remote_ip     => "XX.XX.XX.XX"
  :status        => 403
  :status_line   => "HTTP/1.1 403 Forbidden\r\n"
):

dragonfly.rb configured as follows:
require 'dragonfly'
require 'dragonfly/s3_data_store'

# Configure
Dragonfly.app.configure do
  plugin :imagemagick

  secret "-- desensitised --"

  url_format "/media/:job/:name"

#  datastore :file,
#    root_path: Rails.root.join('public/system/dragonfly', Rails.env),
#    server_root: Rails.root.join('public')
  datastore :s3,
    bucket_name: AWS_S3_BUCKET,
    access_key_id: AWS_ACCESS_KEY_ID,
    secret_access_key: AWS_SECRET_ACCESS_KEY,
    region: 'eu-west-1',
    use_iam_profile: true,
    url_scheme: 'https',
    fog_storage_options: {
    	:provider => "AWS",
    	:aws_access_key_id => AWS_ACCESS_KEY_ID,
    	:aws_secret_access_key => AWS_SECRET_ACCESS_KEY
    }

end

This might be more concerned with Fog than dragonfly but any chance you can help with a little diagnosis.
The AWS_ACCESS_KEY_ID and SECRET work fine with the aws-sdk gem and I can manually put files no problem.
I was thinking about doing a fork for aws-sdk but it seems pointless to duplicate what Fog is supposed to do if its fog's issue.
Thanks.

Changing your policy as this gist did will help.

I was experiencing the same issue with IAM. Removing use_iam_profile and setting the correct region (I was using eu-central) solved the problem.


New Product: Spot

In order to be ready for Q2 2022 development we need to agree upon the scope for the engineering team to deliver in this time period.
Create a new spec with for new product spot markets.
How do we know when we are done:

[ ] The spec for spot has been written
[ ] The specification contains acceptance criteria with IDs that reflect the scope of the work required
[ ] The engineering team has reviewed the specifications and understand the scope
[ ] The spec is merged into the specs repo before engineering start development/test work

closing as PR has been merged.


Several instances of styled-components on the same application (microfrontends)

https://www.styled-components.com/docs/faqs#why-am-i-getting-a-warning-about-several-instances-of-module-on-the-page
I have already read this page. Basically the suggestion here is to use one styled-components for multiple applications. This is against what we want to achieve. We want to have the flexibility of using different libraries/versions for different applications (microfrontends). At the moment the only library causing an issue is styled-components. Is there by any chance a workaround to prevent misbehaviour of loading multiple styled-components in the same application?

Not in the near term future, though it's something I want to spend time on after the v5 release. At the moment the easiest way to support your use case is to either do a "DLL bundle" including styled-components or to load it from CDN and configure your microfrontends to reference window.styled instead during bundling.


Switch away from deprecated JUnit import

Your pull request should…

[ ] have a concise title
[ ] close an accompanying issue if one exists
[ ] be against the correct branch
[ ] include migration scripts and documentation, if appropriate
[ ] pass automated tests
[ ] have a clean commit history
[ ] have proper commit messages (title and body) for all commits

https://github.com/opencast/opencast/issues/4325

Hi @swatichauhan814,
thanks for the patch. Unfortunately, the patch breaks several of Opencast's checkstyle rule:
modules/common/src/test/java/org/opencastproject/util/JsonsTest.java:26:1: 'org.junit.Assert' should be separated from previous imports. [ImportOrder]
modules/common/src/test/java/org/opencastproject/util/JsonsTest.java:26:8: Unused import - org.junit.Assert. [UnusedImports]
modules/common/src/test/java/org/opencastproject/util/JsonsTest.java:28:1: Wrong order for 'org.junit.Assert.*' import. [ImportOrder]
modules/common/src/test/java/org/opencastproject/util/JsonsTest.java:28:31: Using the '.*' form of import should be avoided - org.junit.Assert.*. [AvoidStarImport]

Take a look at the failing GitHub Actions test for more details.
The tests should automatically run if you build Opencast with mvn clean install if you want to test locally.
If you happen to use IntelliJ, you can also import the checkstyle rules which should automatically take care of most checkstyle related stuff (e.g. import order).

To hopefully make sure life a bit easier, here is a short video to show you how to reproduce the errors locally. May be easier than to always wait for GitHub Actions to fail:
https://user-images.githubusercontent.com/1008395/196129094-80e1e7cf-d853-46be-86a5-e856ede351e1.mp4

@swatichauhan814 Your tests are failing checkstyles, which can be run locally with mvn checkstyle:check.  I'm going to guess you missed importing the checkstyle rules Lars mentioned, or they didn't get applied automatically by your development environment.


Expose dataset for result entities in query result

I'd like the query results to show the dataset the result entities are stored in. Both for the matching entity and for the inverse matches. This could then be used to filter the results i.e. when looking for inverse matches in or more particular datasets.

Proposal for this is to introduce a new query parameter which is merge default value is true. This can be set to false to get back more than one entity per URI. The dataset can also be included as part of the entity using a well known property class.

Having looked at the code this is a bit of change given the way its written at the moment.

Plan is to add a queryflag NoPartialMerge which is false by default. Setting to true changes the existing behaviour to return an Entity that has a property called partials, whose value is an array of entities. Each entity has had an additional property added that is the name of the dataset it originates from.


upgrad node to v20

Codecov Report

Merging #578 (3a3223e) into main (0e0b5fd) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #578   +/-   ##
=======================================
  Coverage   81.98%   81.98%
=======================================
  Files          31       31
  Lines         744      744
  Branches      134      134
=======================================
  Hits          610      610
  Partials      134      134

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 0bcfc36...3a3223e. Read the comment docs.

closes #572


OSX tar: Option --xattrs is not supported

Hi
It seems it's not playing so nice with tar on OSX:
$ docker save 091eebea9efd | sudo docker-squash -t squash -verbose | docker load
Loading export from STDIN using /tmp/docker-squash978633966 for tempdir
Loaded image w/ 17 layers
Extracting layers...
  -  /tmp/docker-squash978633966/e566a8a9474f62235548281ed5e276a559dca94a9ebd8f1acb5e8cd287bc7b08/layer.tar
tar: Option --xattrs is not supported
Usage:
  List:    tar -tf <archive-filename>
  Extract: tar -xf <archive-filename>
  Create:  tar -cf <archive-filename> [filenames...]
  Help:    tar --help

ERROR: exit status 1
Removing tempdir /tmp/docker-squash978633966
open /var/lib/docker/tmp/docker-import-172480019/repositories: no such file or directory

Any suggestions would be greatly recevied.
Thanks
Nathan

I used a different version of tar.
brew install gnu-tar
PATH="/usr/local/opt/gnu-tar/libexec/gnubin:$PATH"

Having the same issue, while I could install gnu tar just wondering if this can be made to work on os x without that workaround?

gnutar is required for OS X.  docker-squash looks for gtar in your path.  https://github.com/jwilder/docker-squash/blob/master/utils_darwin.go#L5

In fact
docker-squash doesn't look for gtar, it just uses tar directly
➜  /tmp docker-squash -v
v0.2.0

➜  /tmp gtar --version
tar (GNU tar) 1.29

➜  /tmp which gtar
/usr/local/bin/gtar

➜  /tmp sudo docker-squash -i image.tar -o squashed.tar
Password:
tar: Option --xattrs is not supported
Usage:
  List:    tar -tf <archive-filename>
  Extract: tar -xf <archive-filename>
  Create:  tar -cf <archive-filename> [filenames...]
  Help:    tar --help

ERROR: exit status 1


Improve uninstall for glimmerblocker

Closes #8219.

But that could interfere with other proxies the user may have configured.

Lets play it safe and not do it, then.

Merged in 98cb264.


[BUG] NullReferenceException when creating an empty blob

Describe the bug
When attempting to create an empty blob by invoking the UploadAsync method with content set to null we get a NullReferenceException exception. I tested with BlockBlobClient but I suspect the same is true with other types of blobs.
If null is not a valid value, I would expect a guard to throw a ArgumentNullException which would be more informative.
If null is a valid value, I would expect an empty blob to be created. This would mean replacing code such as contentLength: content.Length, here with something like contentLength: content?.Length ?? 0,.
The workaround is to use new MemoryStream() instead of a null value.
Exception or Stack Trace
Unhandled exception. System.NullReferenceException: Object reference not set to an instance of an object.
   at Azure.Storage.NonDisposingStream.get_Length()
   at Azure.Storage.Blobs.Specialized.BlockBlobClient.UploadInternal(Stream content, BlobHttpHeaders blobHttpHeaders, IDictionary`2 metadata, BlobRequestConditions conditions, Nullable`1 accessTier, IProgress`1 progressHandler, Boolean async, CancellationToken cancellationToken)
   at Azure.Storage.Blobs.Specialized.BlockBlobClient.UploadAsync(Stream content, BlobHttpHeaders httpHeaders, IDictionary`2 metadata, BlobRequestConditions conditions, Nullable`1 accessTier, IProgress`1 progressHandler, CancellationToken cancellationToken)

Code Snippet
var content = (Stream)null;
await blob.UploadAsync(content, headers, metadata, requestConditions, null, null, cancellationToken).ConfigureAwait(false);

Expected behavior
I expect an empty blob to be created.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x] Bug Description Added
[x] Repro Steps Added

@tg-msft: Would you be so kind as to help route this?

/cc @JoshLove-msft

Hi @Jericho,
Thanks for bringing this issue to our attention. The plan for now is to make sure that it throws the correct exception ("ArgumentNullException") for not just block blob, but for the regular blob client, page blob and append blob as well.
I made a new issue to investigate whether or not we should make a new API for block blob to create an empty blob, like how page and append blob has it.
#9390


Option to disable update notifications

please add an option to disable notifications about new versions.
Although I appreciate active development, I don't want to be bothered every few days.
"Don't call me, I will call you"

Duplicate of https://github.com/microsoft/PowerToys/issues/2701


🛀🏾  Clear core/built/assets content in dev mode

refs TryGhost/Ghost#8162
When in development mode, we're clearing the core/built/assets directory, so they don't build up over time as we're now delivering client
assets with cache-busting hash in the filename.

I wasn't able to run a production build, due to this error:

If anyone has a suggestion how to solve this?

@kevinansfield @AileenCGN
I'm also getting the build error for production.
It's either caused by https://github.com/TryGhost/Ghost-Admin/commit/16438f8c68804ed4101956ea92334fde101cf073 or https://github.com/TryGhost/Ghost-Admin/commit/df354c15d341a0614f0b75c6a42e1a29c63e353d, because https://github.com/TryGhost/Ghost-Admin/commit/bed6089aaa3f295683e849fb02b1e826dc2db061 works.

Coverage remained the same at 71.686% when pulling 3682eee0412f99614636a970bebb1db0d79f8eae on AileenCGN:clean-asset-directory-in-dev-mode into 88f13b6857a00fb82623abed82c099e98d0fa27b on TryGhost:master.

Coverage remained the same at 71.686% when pulling 3682eee0412f99614636a970bebb1db0d79f8eae on AileenCGN:clean-asset-directory-in-dev-mode into 88f13b6857a00fb82623abed82c099e98d0fa27b on TryGhost:master.

Coverage remained the same at 71.686% when pulling 3682eee0412f99614636a970bebb1db0d79f8eae on AileenCGN:clean-asset-directory-in-dev-mode into 88f13b6857a00fb82623abed82c099e98d0fa27b on TryGhost:master.

Closing this as I think there needs to be a rather different approach due to the "delta" nature of rebuilds.


refactor: move emoji formatting into concrete fns

doing this for some more flexibility in new message function formats. merging into master but this is relevant to KV commands work #392

This is great! Do you eventually want to deprecate external usage of message altogether? Perhaps we should open an issue for updating instances of message elsewhere in the codebase to use these new functions.

@EverlastingBugstopper there shouldn't be any external use of the message fn, as it is not public. everywhere you see message outside of this file it is used as a namespace. The purpose of this module is to centralize and standardize how we present information to the user in the terminal. the purpose of the refactor is to just move more of the formatting concerns into the module functions themselves rather than assume that every type of message is surrounded by a specific emoji.


clickhouse: fix compilation on aarch64-linux

Workaround for: #353775
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Hydra builds also affected on 24.05 now: https://hydra.nixos.org/build/277504634


Make time field in Metadata struct optional

Fixes #3.
This is a potentially breaking change.

Thanks for the PR. Yes, this is a breaking change. I will release it as 0.6.0. We might want to do some other changes too. If you are in a hurry, let me know and I will release it sooner rather than later.

I currently use a fork, so if these other changes will be done in the coming 2-3 weeks, that would be no problem for me. Otherwise I'd be happy about a release, makes maintenance of my codebase a bit easier 🙂


Added Default Protocol as "https"

[Opinion wanted]Should we wait for better scrubber logic , or merge it ?

#35 Links here.


Does config file support multiple targets ?

Hello,
i'm currently writing an ansible role to deploy and configure your exporter (https://github.com/lrk/ansible-role-prometheus-sql-exporter if you want to check).
I'm not sure if the config file support multiple entries of "target", right now i have a Hash model with multiple targets/datasources configurable, and i generate multiple configuration files (with one target inside).
I have to create multiple systemd services as i want the exporter to run and restart automatically after failure or reboot. each one corresponding to one config file (and one target).
i'm not sure if it was somewere in the documentation, but i haven't found any clues, config.go seems to support multiple (undocumented) jobs, but only one target.
If multiple target per config are not supported, i would like to request that feature
thank you in advance.
best regards

SQL Exporter does in fact support multiple targets, but that feature has been removed from the documentation at the request of the Prometheus team. There are a number of reasons for that, such as SQL Exporter becoming a single point of failure, it not being in the same failure domain (i.e. on the same server) as the target it monitors and replicating Prometheus' job/instance/up/labels model. So I'd recommend you deploy one SQL Exporter instance alongside each database you intend to monitor.
That being said, if you go back a couple of versions (for README.md and examples/sql_exporter.yml), you'll find the feature documented.

Oh, and you might find that using the same SQL Exporter instance for multiple targets will cause collection to time out on multiple DB servers when only one DB server is slow.

Thank you for those explanations.

You still might want to hint this somewhere.
This feature is quite useful if you have multiple databases in one RDMS instance.
So you only need to start one instance of sql_exporter per, for example, every PostgreSQL-Cluster and not one for every database in every cluster.

Fair enough. It was a requirement for having SQL Exporter listed in the Prometheus docs, but that configuration was aimed squarely at running a single exporter with multiple independent targets.
I guess one could make an argument that this is aimed at multiple instances running on the same host (and document it as such). Or just be vewy-vewy quiet about it. :)

@free I totally understand why it is not a good idea to run your SQL Exporter centralized for independent targets. This should never be recommended!
Maybe it is possible to have a disclaimer or so, that this option is available if you run legacy (not containerized) setups on bare metal or big VMs where you want to host multiple databases per host.


[Tree] Not correct setter for root node

For  this  example setter of root element works not correctly. Now in the current implementation, Nested set root to self but need to set root to Shop entity.
I think need replace this string to
if ($root = $meta->getFieldValue($node, $config['root'])) {                 $newRoot = $root;             } else {                 if ($meta->isSingleValuedAssociation($config['root'])) {                     $newRoot = $node;                 } else {                     $newRoot = $wrapped->getIdentifier();                 }             }

hm, seems like an issue, can you submit a pull request?


Custom compiler time conditionals for macos and ios

Use #if macOS for macos compiler conditionals and #if iOS for iOS/mac catalyst compiler conditionals.

This is aMAzing! 🙌


graphql create my-app --boilerplate react-fullstack-advanced

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Versions (please complete the following information):

OS: [e.g. Windows 10, OS X High Sierra, Ubuntu 16.04]
graphql-cli: [e.g. 2.16.5]
other packages if applicable

Additional context
Add any other context about the problem here.

Same issue here.
"Choose GraphQL boilerplate project:" doesn't list "react-fullstack-advanced.
Versions

OS: Max OS 10.14.2
graphql-cli: 3.0.9

boilerplates template can not find react-fullstack-advanced

It was deleted in this commit. The question is why though. I don't see an explanation. @nikolasburk would you mind commenting on why this was removed?

Is there any update regarding this? as @wdoug mentioned it's removed, is it removed by mistake, or it doesn't work anymore?
Thanks for creating this

Any update or solution found?

Currently we have new structure for GraphQL CLI and in the new alpha version 4.0.0-alpha.0 we suggest to use init command of GraphQL CLI with Graphback. Checkout new instructions and we will be happy to hear your feedback. Feel free to contact us using our Discord channel;
https://discord.gg/xud7bH

We have just released a new structure for GraphQL CLI in a new alpha versions track -  4.0.0-alpha.XXX!!
We suggest to use the init command of GraphQL CLI which was completely rewritten!
Checkout the new instructions and the migration guide on the docs and let us know your feedback.
Feel free to contact us by opening an issue or using our Discord channel;
https://discord.gg/xud7bH

I've posted the wrong Discord link, this is the correct one: https://discord.gg/xud7bH9


Retry "file status" request with exponential backoff if it failed

but CI is failing

yeah, either travis env needs to be downgraded or the project's pom needs to be upgraded


add stimulus trajectory

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Details

10 of 12 (83.33%)  changed or added relevant lines in 3 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-1.7%) to 92.292%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/harissa/simulation/approx_ode/base.py
5
6
83.33%

src/harissa/simulation/bursty_pdmp/base.py
4
5
80.0%

Files with Coverage Reduction
New Missed Lines
%

src/harissa/core/simulation.py
1
99.03%

Totals

Change from base Build<PHONE_NUMBER>:
-1.7%

Covered Lines:
1428

Relevant Lines:
1497

💛  - Coveralls


Escape hex and octal codes

The tokenizer is only considering \n, \r, \t, \\
https://github.com/risor-io/risor/blob/e940fd00a2c110ff44d9e0713d025edc7f358959/lexer/lexer.go#L495-L510
Want to be able to do the following:

Same sequences as Go: https://go.dev/ref/spec#String_literals

\u65e5
\U00008a9e
\xff

Also the \033 octal one, commonly used in ANSI color codes (e.g printf '\033[31mred text\033[0m\n')
Additional hardcoded sequences:

\e alias for \033/\x1B, sometimes used in ANSI color codes (e.g in Bash echo -e '\e[31mred text\e[0m')

I'm mostly listing different escape sequences just to make it more consistent, but the ANSI color codes is the most important one to me so that I can do the following in Risor:
# my-risor-file.risor
c_reset := "\033[0m"
c_red := "\033[31m"

func log_error(err) {
  print('{c_red}error:{c_reset} {err}')
}

Thanks @applejag, I agree with all this. By any chance would you want to take a stab at the implementation?
I'm sure I can get to it, but it might not be as soon as either of us would like. So I'd be grateful to enlist your help with this :-)

Yea sure, I'll give it a go


Unable to click continue when specifying a new cloud credential as part of creating a new cluster.

Setup

Rancher version:  v2.7.1
Browser type & version: Firefox 109.0.1

Describe the bug
When creating a new cluster on a infrastructure provider without an existing cloud credential , the Rancher UI will prompt to create a new one, however, continue cannot be selected.
To Reproduce

Remove any existing cloud credentials for a infrastructure provide (ie Harvester, DO, etc)
Rancher -> Cluster Management -> Create
Select a cluster type under Provision new nodes and create a cluster using RKE2/K3s
Attempt to continue with the credential creation flow

Result

Continue is greyed out, unable to proceed

Expected Result

Rancher UI should guide the user into creating a cloud credential

Screenshots

Additional context

I couldn't recreate this in 2.9-head (around 2.9.0).

There should be more input fields when creating an azure cred. There might have been a page error causing them not to render. I think there were some updates to this area since 2.7.1 which may have fixed them

I wasn't able to recreate the issue on 2.7.1  either.


[hotfix][k8s] fix checkstyle problem

File should be end with a new line. This PR append the missing line.

There is no rule that files should end with a new-line.

@zentol There is trully a rule constrains that file should be end with a new line.
<module name="Checker">
....
  <module name="NewlineAtEndOfFile">
    <!-- windows can use \r\n vs \n, so enforce the most used one ie UNIx style -->
    <property name="lineSeparator" value="lf" />
  </module>
...

Doesn't seem to be working though, since all builds should then be failing.


package.branch-rate="0" even though class.branch-rate!="0"

dotnet-coverage: v17.6.6
Microsoft.CodeCoverage: 17.6.0-preview-20230221-02
After switching to dotnet code-coverage "command" I'm getting our code coverage validation failing which worked when I collected the coverage via dotnet test --collect:... --test-adapter-path:....
For example:

This looks wrong to me, should package.branch-rate="1" in this case? Stats collected the old way (i.e., dotnet test --collect...) and then merged together resulted in the following (for the same package, I stripped the package name and file names):

You can grab the new coverage.cobertura.xml here (under "drop").
The old merged covertura.xml can be downloaded from here.
I also tried dotnet-coverage 17.4.2 and 17.5.2 and few different version of Microsoft.CodeCoverage, and results seem to be the same.

@fhnaseer please check overall statistics calculation.

@RussKie please check 17.6.7. I hope issue is fixed.