Better support for debian/watch files and uscan

The recent change to remove index pages breaks debian/watch files used by the uscan script on Debian systems to find the upstream tarball used by package maintainers when updating and building their source packages.  After discussion with dstufft, I understand why that change was necessary.  We'll have to change lots of packages in the Debian Python repository (some of which are not team maintained).  We can communicate this to package maintainers, but it would be best to provide a good alternative.
The https://pypi.python.org/simple/package listings which take their place is not very convenient for two reasons.  While we can make it work by using debian/watch file contents such as:
version=3
opts="filenamemangle=s|.*/(.*)\#md5.*$|$1|" \
 https://pypi.python.org/simple/wheel/ .*/wheel-(.*)\.(?:zip|tgz|tbz2|txz|tar\.(?:gz|bz2|xz)).*

you can see that this is not as simple as what we used to have:
version=3
https://pypi.python.org/packages/source/w/wheel/wheel-(.*).tar.gz

The first inconvenience is the #md5=blah fragment that all hrefs in the listing contain.  uscan is not able to automatically ignore these, although it does ignore query suffixes (e.g. ?md5=blah).  This is why we have to have the filenamemangle option.
The second inconvenience is the fact that the hrefs on the simple page point to tar files at a different url, so we need the two-parameter second line.
Both of these issues means that maintainers will be cargo culting the solution, there will be several variants so folks won't know what the details mean, and it will be easy for difficult-to-debug typos to occur.  It will also be difficult to explain best practices and give readable examples.
If the urls must change (as I understand they must since you'll be moving away from a file system implementation), then it would be great if we could get simple urls with redirects back.  E.g.:
version=3
https://pypi.python.org/simple/wheel/wheel-(.*).tar.gz

This would mean 1) no #md5=blah suffixes, or that # were changed to ? and 2); the hrefs were resolvable to tarfiles on that same page, via redirects if necessary.  (Yes, I know not every upstream uses .tar.gz; that's okay don't worry about that part.)
In IRC, dstufft mentioned that the trade-off for this convenience would be the possibility of some short downtime if the backend went down, since the "debian-simple" (or "uscan-friendly") urls wouldn't be cached by the cdn.  Since those down times would be short, I can live with that.  This is primarily for the convenience of the package maintainers, and really is only needed when they build a source package locally, either for upgrading the Debian version of the package, or perhaps for building a version for which they only have the source branch (which, under svn and other conditions may not have the pristine-tar file readily available).  Unless I'm missing something, the worst effect of backend downtime would mean the unlucky package maintainer would just have to wait a little bit.

This will probably live at https://pypi.python.org/uscan/, but I have questions:
By different URL I assume you mean, what uscan really wants is something like https://pypi.python.org/uscan/wheel/ being an index page with links pointing to https://pypi.python.org/uscan/wheel/wheel-1.0.tar.gz?
I assume there's no special constraints on the markup itself?
To be clear, these URLs will likely be cached, but since they'll have different cache keys and uscan traffic is a lot less then pip/easy_install traffic it's more likely that if downtime occurs that their won't be cached items to return.

I think that would work well.  No special markup, uscan looks for standard <a href="http://pypi.python.org/uscan/wheel/wheel-1.0.tar.gz"> type HTML.

Going to close this since Debian is setting up a redirector at pypi.debian.net instead.

It would be great if Debian could move away from using a redirector. Could the "new PyPI" support our uscan tool cleanly? :)

Hi @lamby - I think we just spoke in #debian-python and I just referred to this issue in #2935 . I'd encourage you to check out our APIs/feeds issues and feel free to comment on those or file a new issue to request that PyPI's APIs support uscan better!

@brainwane Hi, thanks for the offer but as I mentioned on IRC I am really not the one to ask for this - I was just throwing ideas around! Sorry about that..


Consider removing part and part of

using part isn't considered good practice
several of the Dart team members would rather remove it from the language

Is there a better approach? I don't care for it either, but it currently beats importing a bunch of files in each part of the library. Also, my understanding of that practice is that it can have a negative impact when compiled to JS, but that won't matter here. Interested in other possibilities though

It is mostly a style that the dart team and the community are using.
I'll give you an example: dart-lang/shelf
They are no longer using library, part and part of. That's also true for all the other dart-team and google packages.
Anyway, it is just a suggestion, you can think about it and decide which approach you feel most confortable using.

Also, I dont think it has a negative impact when compiled to JS. Dart uses tree shaking and it removes unused code.


Regarding Transition Probabilities

Hello
I am using a few covariates for transition, but when I am using the sample code provided to view transition probabilities, it is throwing an error.
For Example : covariates_transition = ['a','b','c','d','e', 'f','g','h','i']
When using print(np.exp(SHMM.model_transition[0].predict_log_proba(np.array([[]])))),
I am getting an error :  X has 1 features per sample; expecting 10. How can I get the transition probabilities for the two hidden state model with transition covariates.
Also, how can I get the most likely state for each observation? In hmmlearn ,
remodel = hmm.GaussianHMM(n_components=2).fit(X, lengths)
Z3 = remodel.predict(X) provides the hidden states, how can i get that in this model.
Thank you for all the help.

Just a user, but for the first question I did:
the number of empty lists inside np.array() should be equal to the number of your inputs + 1 (constant), I have two inputs.
empty = add_constant(np.array([[], [], []])).transpose()
SHMM0.model_transition[0].fit_intercept = False
SHMM0.model_transition[1].fit_intercept = False
print(np.exp(SHMM0.model_transition[0].predict_log_proba(empty)))
print(np.exp(SHMM0.model_transition[1].predict_log_proba(empty)))


Add Ukrainian language

Hi,
I would like to work on Ukrainian translation of React.js docs. I have done a little bit of translation before (small iOS app), but I would be happy to contribute to React.
I also have an English blog on Medium.
My friend @MargarytaChepiga also wants to contribute to this translation; she has done some translations in Brave Browser.
I've also asked some people to join this project, so I might add some more maintainers later.
If anyone is interested to contribute, leave a comment 👇

@klymenkoo I would like to help!

@klymenkoo would you like to start now and add people later or would you like to wait a bit for people to respond?

Hello Volodymyr. I would like to help. Let me know what I can do.

@ithompson4 could you tell us a little more of your translation/open source experience?

I am a Seneca student. I am Ukrainian and can speak both Ukrainian and Russian. I am new to Open Source but have significant IT experience. Please feel free to look me up on linked in if you want more on my background linkedin.com/in/irynathompson. Thanks.

@klymenkoo would you like to start now and add people later or would you like to wait a bit for people to respond?

Yes, we can start now. Sounds good.


Does not work for Ruby

Unfortunately, I've found this plugin does not work properly with Ruby.
I have it set to use #region to start a new region.
I have to type //#region in order to actually get a foldable section.
I have it set up to use #region for all of the fold starts, and #endregion for all of the fold ends.

Disregard, I had to set it to use region instead of #region to get it working.
Maybe needs better documentation?


Add Mapper

Pull Request Description
Mapper is a simple Swift library to convert JSON to strongly typed objects. One
advantage to Mapper over some other libraries is you can have immutable
properties.
Acceptance Criteria
To be accepted into the Swift source compatibility test suite, a project must:

[x] be an Xcode or swift package manager project
[x] support building on either Linux or macOS
[x] target Linux, macOS, or iOS/tvOS/watchOS device
[x] be contained in a publicly accessible git repository
[x] maintain a project branch that builds against Swift 3.0 compatibility mode
and passes any unit tests
[x] have maintainers who will commit to resolve issues in a timely manner
[x] be compatible with the latest GM/Beta versions of Xcode and swiftpm
[x] add value not already included in the suite
[x] be licensed with one of the following permissive licenses:

BSD
MIT
Apache License, version 2.0
Eclipse Public License
Mozilla Public License (MPL) 1.1
MPL 2.0
CDDL

[x] pass ./check script run

Looks good. Thanks!


Internal TF

User can turn this on via Job config: packit/packit#1280
Service needs to configure secret and URL for internal TF.
Project needs to be enabled in the service config to use internal TF.

TODO:

[x] Requires packit/packit#1280
[x] Tests

recheck

The tests failed because of the missing change (packit/packit#1280) in Packit:
E           AttributeError: 'JobMetadataConfig' object has no attribute 'use_internal_tf'

recheck


Cannot destroy() table in Kendo Mvc grid

Hi,
I am  trying to use TableSaw with KendoGrid (MVC). I have code to switch between swipe and stack mode. To switch between the modes I destroy the table data before setting the new mode. It does not seem to be able to destroy(). I get the following exception.
tablesaw.js is properly loaded, so that is not the problem.
The problem is thead and tbody are in different tables and this is not handled by tablesaw. Tablesaw assumes thead and tbody are in the same table.
Uncaught TypeError: Cannot read property 'destroy' of undefined
Any help is appreciated.
Thanks
Sangeetha

This markup pattern has serious accessibility issues and thus we are unlikely to fix this in Tablesaw. Sorry!


update helm chart for release v0.8.0

Signed-off-by: Suresh Nakkeran<EMAIL_ADDRESS>fixes #2002

/retest

/lgtm
/approve


Custom parameter decorator

Hello, first of all thanks for this great lib.
I would like to ask if there is a way to create a custom decorator, something like what can be done in https://github.com/typestack/typedi#custom-decorators.
I would like to create a custom decorator, for injecting TypeORM repository based on provided entity. Something like: @InjectRepository(User) public repository: Repository<User>, where @InjectRepository is my custom decorator.
Thanks in advance.

Yep! You can do something similar to what is found here. Where you wrap the target of your custom decorator with any other decorators you wish to include


fix: /app/installations should be GET method

Why:
The example for Github APP JWT Authentication has a wrong request method POST.
According to Github API docs, it should be GET.
Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Change request method to GET.
Check off the following:

[x] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

@DenChenn Thanks so much for opening a PR! I'll get this triaged for review :zap:


Updated validations.py python script

Updated validations.py python script.
Fixed the behavior of validate_user function in validations.py.
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

@marga-google all check failed due to CLA. how do we start that again

@marga-google all check failed due to CLA. how do we start that again


Enable app developers to view and search for the list of app users authenticated to the app

Identity MVP Technical Specification
In the month of Apr, we are working on enabling app developers to view and search for the list of app users authenticated to the app in App Center.
Let us know if you have any feedback, or would like to be a part of our private preview!
Here are some designs:

The link to your spec is broken. The spec was moved up out of the month directory.

Thanks @fiannaca for letting us know, and nice catch! I've updated the link to the spec.

Closing this issue - we reduced the scope and did not implement this in our public preview. If you have any feedback, please let us know. You can learn more about Auth!


MN still uses TriTone

I read that this issue was fixed however MN still uses tri-tone whenever I get text messages.  is there any way I can change this and use a different tone???

Try pulling the latest package from http://cydia.myrepospace.com/timnovinger, just add it as a Cydia source.


sdist is missing tests

The sdist package at PyPI is missing tests.  Please add tests to sdist to make downstream testing easier.  Thank you.

@mtelka to be honest, I am not sure what is being requested here.

Please try this (sdist at PyPI):
$ wget https://files.pythonhosted.org/packages/source/p/pipenv/pipenv-2024.3.0.tar.gz
$ tar xf pipenv-2024.3.0.tar.gz
$ ls pipenv-2024.3.0/tests
ls: cannot access 'pipenv-2024.3.0/tests': No such file or directory
$

And now the same with the github tarball:
$ wget https://github.com/pypa/pipenv/archive/refs/tags/v2024.3.0.tar.gz
$ tar xf v2024.3.0.tar.gz
$ ls pipenv-2024.3.0/tests
conftest.py  fixtures  __init__.py  integration  pypi  test_artifacts  unit
$

We intentionally prune out the tests from the pypi published wheels, that would be a very large package size if we did not.

First , this issue revealed to me that we are not distributing wheels.
We should consider.  ..
Second, pipenv is quite a special case here, as we use the sdist to let people install pipenv . If we add the tests people who wanted to just install and use pipenv will unnecessarily download the tests too.
To fix it, we need to build wheels.
But even if we did that, distributing the tests only would be useless. The reason for this is that pipenv's extended integration tests required many source packages that are included in the repository as git submodules.
Hence, the audience of the sdist file - developers - would come short handed here.
The best way to get the sources with tests is included is to close the repository directly from GitHub.

To readers who want to close this issue:
The actual work here is modify the release pipeline to build and upload wheels.

Hence, the audience of the sdist file - developers - would come short handed here.

In addition to developers the sdist audience are also downstream distributions.  Which is my case too.  I use sdists to create OpenIndiana packages.

The best way to get the sources with tests is included is to close the repository directly from GitHub.

Yes, I can use github tarballs for that (I actually do so now for pipenv), but github tarballs are unstable (they could change later) and so sdists are always the preferred way for getting the sources.
Thank you.

@mtelka are you running the complete integration test as part of the build?
The gentoo ebuild is only running the unittest because the gentoo build system does not allow network calles.

@mtelka are you running the complete integration test as part of the build?

I do not know.  I just run pytest :-).  However many tests are failing and the testing takes about one hour:
===== 54 failed, 325 passed, 18 skipped, 27 warnings in 3919.83s (1:05:19) =====

Unfortunately, I had no time yet to analyze what exactly is failing there.

I recommend that you just do:
pytest -m "not cli and not needs_internet" tests/unit/

These tests do not detpend on git submodules and do not require a local pypiserver to run.
Also, they should take around no more than 20 seconds on a normal computer.


Not getting ios favorites folder as an option

Sorry, ignore this.

Any reason that this was closed? Trying to figure out how to get the favorites folder to appear in the latest version of the lib on iOS but I don't see it there.


[Q] How to aggregate metrics on the client before logging?

I currently do the following to try to reduce the amount of syncing to the server (I noticed calling wandb.log without doing this slowed down my training runs by 2x):
def commit()
    return random.randint(0, 100) == 0

# each time I call wandb.log
wandb.log({ "step": step }, commit=commit())

The idea is to commit the logs around once every hundred steps.
But I don't think that this is what is actually happening. How would I do what I'm trying to do?

Hi Vedant,
Could you explain how this is not working? I'm not sure I understand the issue you are facing here

Hi Vedant,
We wanted to follow up with you regarding your support request as we have not heard back from you. Please let us know if we can be of further assistance or if your issue has been resolved.

Hi I have the same issue. I want to avoid logging too frequently by pushing the aggregated metrics at the end of the running script. Previously I got advice from the wandb support team that I can use the following semantics:
wandb.log({ "step": step }, commit=True if step % freq == 0 else False)
But it seems this semantics overwrites the previous metrics with the current metric at the moment it commits the log as it is reported in this issue .
How can I sync the aggregated logs without overwriting the previous metrics?

I finally managed to make myself a custom aggregated metrics data sorted by steps and log to the wandb server at the end of the running script. I wish wandb would have supported delayed sync functionality at the script-level.

I finally managed to make myself a custom aggregated metrics data sorted by steps and log to the wandb server at the end of the running script. I wish wandb would have supported delayed sync functionality at the script-level.

Very nice! Would you mind sharing the code for that?

My intention was to fix the error that wandb logging kills the ray worker in a distributed learning setting. So it's not about logging too frequently actually, it's about delayed logging after running.
Please refer to the following code snippet.
import wandb
from collections import OrderedDict

aggregated_metrics = OrderedDict() # key is the time step, i.e., epoch or batch
for e in range(n_epochs):
    if e not in aggregated_metrics:
        aggregated_metrics[e] = {}
    loss = ~
    aggregated_metrics[e]['loss'] = loss
    # and so on
wandb.setup()
wandb.init(entity="your_entity", project="your_project") # and other arguments as needed
for t in aggregated_metrics:
    for k in aggregated_metrics[t]:
        wandb.log({k: aggregated_metrics[t][k]}, step=t)
wandb.finish()

Note that wandb log function ignores the metric if the step value is not ordered.


Config driven testing

Since we are trying to solve the same problem, I thought I'd post here. I've written a config driven lambda test framework here: https://github.com/simlu/lambda-tdd
We've been using something like this for several years and it works really well. Maybe an inspiration?
Anyways, would be very happy to get some insight from you and to discuss!

Looks interesting - I looked at using a config driven method but chose to use a code based approach. Might be interesting to see if we could drive lambda-tester (with some extra hooks) from your library. Also working on creating an event generator for api-gateway requests


Adding raw-loader to support including files in the documentation

Description
This PR adds the raw-loader package to support including raw files (such as scripts) in the documentation.
Motivation and Context
This is needed for the opentofu/opentofu#887 pull request.
Types of changes

[X] New feature (non-breaking change which adds functionality)

@Yantrio can you approve the workflow run please?

All looks good here 👍 Thanks for this @janosdebugs

Thanks @Yantrio !


feat(Data/Sum/Basic): sync with mathlib3

Mathlib4 version of leanprover-community/mathlib#17059.
Drop simp attributes on Sum.getLeft etc. These attrs make Lean4 simplify getLeft x to a match expression, not only getLeft (inl x) to some x.

Which lemmas should I align with isLeft_inl etc?

Which lemmas should I align with isLeft_inl etc?

I think they just don't need aligning.

bors merge


Your contacts and my questions about this library. I'm making p2p messenger on Android on top of TomP2P

Hello, I almost completely studied your library, and I have questions. Since I am doing a decentralized messenger on Android using TomP2P, I had to do a lot of crutches. I saw that you made a commit 4 days ago. Do you have other contacts besides email (to which you do not reply)?

My messenger (I actively developing it): https://github.com/ChronosX88/Influence-android

I can help you with your library.

@ChronosX88 Awesome! I just sent you the slack link


Migrate test project to XUnit?

Very minor thing, just for convenience, to make the project more portable?
Tried to quickly build in Mono, and found that unit-test project depends on MSTest.

build.cmd / build.sh in the root of the repo to build and run unit-tests from command line would be useful too 😄

I'm not familiar w XUnit, I've only used MSTest personally.  Does XUnit require an extension for VS integration?
Pull requests are welcome as long as the XUnit workflow is painless.


Bad UX for date picker selection

Suggest making both the summary display at the top/side, as well as the  MMMM yyyy display above the calendar toggle to the year selection.
Upon clicking/tapping a year (even the same one already selected), return to the month/day selection.

Also, it may be worthwhile to have a 12-month view per year as well, so that upon tapping the month, or after a year is clicked, a month selector comes up.

As much as I never liked the API or most of the look/feel for Microsoft's Ajax Toolkit, I feel the date picker is one of the things they did quite well with.
http://www.ajaxcontroltoolkit.com/Calendar/Calendar.aspx

True, the MS Calendar control has a good year/month navigation!

Started working on a standalone picker in case anyone wants to take a look, there's a couple of bugs, and want to flush out the demo page/app and get it published to gh-pages, but it's working pretty well so far... have had to use CSS, and flush out a lot of bits in order to make it work in the context it was designed for (integrating it at my day job). (npm i && npm start)
Wouldn't mind submitting something similar for here once I'm done.  I haven't looked at the codebase for this project though.  And it doesn't use the themes.


Added patterns for Solr 7/8 and audit logs

Fixes #215

@adnanrahic I'll leave it up to you to merge and release. Or will you teach me how to release?
I'm attaching a
solr.log if you'd like to test. It includes some audit logs and query logs.

Hey @radu-gheorghe, I can release it. Let me just run a quick test and approve the PR, and you go ahead and merge. I'll ping you with a DM today to explain the release procedure and what you need in order to set up the automation tooling.


add volatile mode and close background workers

Fix goroutine leak in TiDB's unit tests.
Provide a VolatileMode to reduce the disk usages when use it in TiDB's unit tests.

go test failed.

LGTM


Bump to Net and Nuget Packages

Need VS Studio preview to build
Vortice-xinput -> 3.2.0
Vortice-math... -> 1.7.2
Vortice-DXGI,Direct3d11,D3DCompiler -> 1.9.143
Please accept my polished slop :D

Closing, merged #87 instead.


Rescue from connection refused errors and return the appropriate status code

When the app that is being proxied is not running, the code currently returns an exception. This prevents the exception and returns the appropriate status code.

@andrewhavens Great work here! How do you plan to test this feature?

@waterlink hmm...I'm not sure. I can't remember exactly how it's triggered. Somewhere in Rack I think. I suppose we could mock the error. What do you think?

@andrewhavens We could try to use webmock and raise the error inside of the stub_request block. It might do the trick.
Also, I have noticed that the error connection refused handling is in the method. It would totally do the trick. What do you think, is there a more suitable place to put this error handling in?


preferred chain support

preferred chain support
This updates to to go-acme/lego v4.6.0, and adds support for passing the "preferred_chain" option through the config file.
How to use
Don't know.
Testing done
Compiled.

we've just tested this now on a new "staging" server, and while there is currently a manual step of determining the root issuer, and then regenerate the certs. Ideally we can leave this as is, and if ISRG changes their root names then worst case is the chain gets long again. :shrug:


How to indicate that time binning does / does not represent "residual time"?

Currently, ad-hoc and manual solution: I added a key t_is_residual_time (file t_is_residual_time.npy) to each table directory that stores a 1d numpy array of bool that indicates whether time is residual time. If the key is missing, Retro5DTables class defaults to False (i.e., time is absolute time since event vertex).
At the very least, we need to make this key be written to generated tables. Preferably there would be a way to store this all the way back to within the CLSim .fits table files, and it should then be propagated to any derived table formats. Regardless if we can get it back at that point, we need to either generate it anew (command line option?) or propagate it (if it already exists as a key for the table).

t_is_residual_time is a field in the fits header, also t_is_residual_time.npy is stored in directory with retro-formatted (.npy) tables.


fix up react example, add requirebin demos to docs

I wanted to try out this module with the react example provided and saw it was broken. Fixed that and added some demos so people can see it works as intended.

Thank you so much!


pkg/trace/config: move env. var registrations to shared config pkg

This change moves the loading of environment variables into the main agent config package.
Whenever a file was loaded with the pkg/config package outside the trace-agent (e.g. agent CLI, flares, etc), it would lack environment variables. The reason for this was partly lack of functionality in the Viper dependency and also support for Agent 5 (and the way the pkg/config/legacy package was working).
Support for Agent 5 is no longer needed in this repository so it is safe to do it right now.

Thanks @olivielpeau!

(haven't reviewed in details that every config option is handled exactly the same though)

That's ok, there are plenty of tests to cover for that, and I will test this well during release week too.

I have a preference for not calling config.SetKnown on config keys for which the code is setting defaults or env vars, that's the convention we use for core and logs agent

Fixed!

I think it'd make sense to allow env vars for all config options (that's what we're aiming for in other agent components). Would be a for a future PR of course.

I have added support via env. var. for all configuration options I considered that a user might want to work with. Some of them are either outdated or we want to discourage their use (such as apm_config.extra_sample_rate).

should we start at some point using DD_APM_CONFIG_ as an allowed prefix for apm env vars? Would be longer, but consistent with logs (DD_LOGS_CONFIG_)

I don't think this is a bad idea, but I'd like to bring it up with the team before making this change on my own. I hope that's ok.

@gbbr, @olivielpeau and others, it looks like this broke things for us: https://github.com/DataDog/datadog-agent/commit/b7467cc7b50bcad34b64268b25d3ba1dfeef4079#r43487574
We worked around it, but it was very concerning to see analyzed spans work one minute, then disappear the next.


Feat: up plus & minus

Add support for up:plus and up:minus operators.
Converts IntCst from i32 into i64 in order to fix overflow issues on LinearSumLeq propagation. The bounds of the sum's terms are clamped into the set_ub method.
NOTE: It was not possible to have INT_CST_MIN = i64::from(i32::MIN) - 1 (same for INT_CST_MAX) since the result is not a constant anymore. Therefore, I hard coded the value of the i32::MIN constant.

@Shi-Raida It looks for the first part but the change to use i64 should only be internal to the linear propagator.
So domains should still be represented with 32 bits (IntCst does not change) but your local copy should be 64 bits. When updating the domains, the 64bits numerals should be clamped and converted to i32.
As implemented, this would have drastic performance implications as the size of a literal would be 128bits (instead of 64), which means it cannot be manipulated as a single machine word. It would also ~double the memory footprint of the solver and negatively impact cache behavior.


Use class only for less confusion

Currently we have problem, that in some cases, we use
<Element class="some properties" other_prop_with_default_value="other-value" />
It is a bit not intuitive. React has different implementation. Where default props are just replaced in string.
Todo: Test efficiency (render speed with one or another approach?)

I got the approach. not sure if any stress-testing/profiling  is needed - alghoritm has complecity O(N), where N - number of classes.
But implemeting as a helper will be not so comfortable in usage. @margusp2heathmont , What do you think - can we make a new prop_type for Surface - moon_class, cloning & updating css_class?

https://github.com/bratsche/twix addresses this

There is also this discussion going on (that references other library and integration into LiveViews) https://github.com/phoenixframework/phoenix_live_view/pull/2366

https://github.com/coingaming/moon/tree/MDS-317-2 - branch with first try of twix (mergeClass tests are broken)
https://github.com/bratsche/twix/issues/7 - issue on a  twix itself

It also kind of looks like this is what you need. Am I understanding your setup correctly? https://github.com/bratsche/twix/issues/6

looks like current twix-free implementation is good enough for using


what is time release the code?

what is time release the code?

I would also like to know this, I would love to test out this model.


adding important note for about using ReFS for CSV

Ticket:<PHONE_NUMBER>00684,<PHONE_NUMBER>06013
further references:
https://social.technet.microsoft.com/Forums/windows/en-US/6b2dcc4f-e735-4700-81f3-df45d94e7e01/refs-for-a-hyperv-csv-volume
https://www.windowspro.de/marcel-kueppers/refs-ntfs-vor-nachteile-dateisysteme-server-2016
Support Tickets:<PHONE_NUMBER>00684,<PHONE_NUMBER>06013

Hi @eross-msft any news / suggestions regarding this PR and #4859 (they belong together contextually)

@JohnMarlin-MSFT  Would you be able to review the failover cluster portion of this? I'm not sure who would be the person for the refs piece, would you know? Thanks!

@Karl-WE : Thanks for your contribution! The author(s) have been notified to review your proposed change. @JasonGerend

Thank you Trond for your support and review @illfated it is always helpful to re-read things and refine.

You're welcome. I hope this will help to get the review process moved forward, even though I don't have the proper knowledge about this exact topic.

I would like to add that in the named support requests there was a statement from employee that is very deep into the topic but he said he cannot update his old technet > techcommunity articles at the moment to reflect the situation. This also motived my, next to trapping into this performance pitfall, to create this PR.
The fact that we have had 2 different and independent cases on the same issue both (after months of back and forth) ended with the now in this PR captured conclusion.

Sounds almost incredible, but at least you have used it for a very constructive purpose. Good to see improvements from contributors like you.

Confirmed with product team, this is ready to publish.

Thank you @eross-msft for the quick double-check


Conflict with RealBench: Crafting Pad deletes items

Vanilla Tweaks Version:
1.12.2-1.5.4
MinecraftForge Version:
<IP_ADDRESS>68
Minecraft Version:
1.12.2
(Optional) Just Enough Items (JEI) Version:
Not Installed, though it does happen with JEI installed as well.
(Optional) Baubles Version:
Not Installed, though it does happen with Baubles 1.12-1.5.2 installed as well.
Client or Server?:

[X] Client (happens in a single player world)
[X] Server (also happens on a server my friend is hosting)

Crash Report (via. Hastebin):
Does not crash. Though there is a log from RealBench injecting into a couple things, might or might not help.
What happens / happened?:
I left an item in the Crafting Pad and pressed Escape to close it. The item was deleted.
How can the issue be reproduced?:

Create a new world with the seed blue
Break 2 logs.
Make a Crafting Pad.
Put the Crafting Pad on your hotbar. Slot does not matter.
Open the Crafting Pad.
Put a stick or plank in the Crafting Pad. Slot does not matter.
Press Escape to close the Crafting Pad.
Item should be returned to your inventory, but is deleted instead.

** Mod List**:

RealBench-1.12.2-1.3.3
Vanilla Tweaks

** Comments**:
I hope there's an API call you can make, a property you can define, or a GUI / inventory you can save and reuse the next time the Crafting Pad is opened.
It sounds like other hand-held crafting tables are affected too. There's a comment on the RealBench CurseForge page about the same thing happening with the Portable Crafting Bench from the Random Things mod, though I haven't checked if that's still happening.
I wanted to file an issue about this on the RealBench issue page as well, but their issue page is down.

Looks like the RealBench mod is modifying the vanilla crafting table so it holds its contents when the gui is closed. The author seems inactive and its source code isn't available. Essentially VanillaTweaks extends Vanilla crafting table for its crafting pad. The issue can be fixed by RealBench or by a clustered way of duplicating vanilla code. I would rather not do it the second way.

I have let a message to the author of RealBench proposing a fix. Will have to see if he responds. Until that i suppose you can remove that mod?

Thank you for the quick response. We'll see when/if the RealBench author responds. In the mean time, I'll probably be careful and just cheat back in anything I end up losing; Life in the Village isn't a tough modpack, where things take many crafting steps and lots of materials to make.

There is no way to fix this issue in my side thus i am closing this.

I'm as well getting this error although, I do not currently have the RealBench mod loaded into the pack I am playing, and I do not know what is causing this problem.

Hey can you provide me the mod list of the pack. I will try reproducing the issue.

https://www.curseforge.com/minecraft/modpacks/performance-craft/relations/dependencies


Feature: Allow comment update for Kitsu Note

To be able to update a comment in a later publish, we have to split the note creation and the comment content update.
For example, publishing a note with a render sent to a farm may need a note update in a second process, for displaying that the render has complete.
Testing notes:

Move this code on last beta we have
Publish layout for e666_sh005, it should work as previously
You can monitor Kitsu and see that the note is created first and then the comment content updated.

I wasn't able to get a review sent to kitsu when using the render farm.

The test doesn't mention the render farm, there is no point using it here. This feature allows future features for farm but doesn't rely on it. As described, publish should basically work like before with regular configuration (no render farm submission).

I wasn't able to get a review sent to kitsu when using the render farm.

The test doesn't mention the render farm, there is no point using it here. This feature allows future features for farm but doesn't rely on it. As described, publish should basically work like before with regular configuration (no render farm submission).

Oh okay, I did publish once without it and it worked normally in this case.


Multiplayer support?

Will there ever be multiplayer support for this mod because I tested out multiplayer and only the host can use the gun.

What version are you using?

I am using version v1.2.0 the newest one I tried using this mod on multiplayer because I wanted to make a co op portal map but found out only the host of a plan server and or the first person to join on a actual server can use the gun everyone else it doesn't even shoot.
Dont know if this is a bug or if it was not intended for online use

It is intended for multi-player use. Can you join the Discord at https://discord.gg/m3EjDuuekg


libdvdcss 1.2.x is deprecated, remove

I added this recipe a while ago because HandBrake required it and failed with libdvdcss 1.3.x. This has been resolved with libdvdcss 1.4 (part of Homebrew proper).

@DomT4 thoughts?

👍, It looks to be technically within the +/-2 major version window but nothing uses it and there's been a wild 19 bottle downloads in the last year.

Merged in https://github.com/Homebrew/homebrew-versions/commit/a110d5d76b19c89f11c6dee186283d5c3210accb. Thank you for your contribution to Homebrew @bconway; we appreciate it! :smiley_cat:


[Fix] DeprecationWarning with dependencies and ColoredMap

Summary
When ColoredMap is called DeprecationWarning is raised. This is due to internal error of dependencies and this should be ignored in covsirphy.
Codes
import covsirphy as cs
# Dataset preparation
loader = cs.DataLoader("input")
jhu_data = loader.jhu()
jhu_data.map()

Outputs
DeprecationWarning: An exception was ignored while fetching the attribute array_interfacefrom an object of type 'MultiPolygon'.  With the exception ofAttributeError NumPy will always raise this exception in the future.  Raise this deprecation warning to see the original exception. (Warning added NumPy 1.21)
Environment

CovsirPhy version: 2.21.0-omicron
Python version: 3.9.5
Installation: poetry
System: WSL (Ubuntu)

jhu_data.map(country="Japan") also shows the DeprecationWarning due to the same cause.


[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 10:06:29 on 2023.05.02
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 2, errors out: 0
Original problem ID: 20207
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23483&eventid=20207

Problem has been resolved in 6m 0s at 10:12:29 on 2023.05.02
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 20207


Google Play cancel subscription and asking about confirmation

Version of react-native-iap
4.4.3
Version of react-native
0.62.2
Platforms you faced the error (IOS or Android or both?)
Android
Description
On Android after i bought subscription, it canceled after few days. In Google Play i can see that i need to confirm subscription or it gonna be canceled. Maybe i missed something in implementation?
I also trying update to latest version 4.5.0, but i get the same result.

You should acknowledge the purchase which I've exposed as a finishTransaction


fix: upgrade ui-shared and other peer dependency

What this PR does / why we need it:
fix: upgrade ui-shared and other peer dependency

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


fix #522

PLEASE READ THE GUIDELINES BEFORE MAKING A CONTRIBUTION

Please check if the PR fulfills these requirements

[x] The commit message are well described
[x] Docs have been added / updated (for features or maybe bugs which were noted). If not, please update the needed documentation here. This is not mandatory
[ ] All changes have fully been tested

What kind of change does this PR introduce? (Bug fix, feature, ...)

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change? (What changes might users need to make in their scripts due to this PR?)

Other information:
#522
https://github.com/SirEndii/Advanced-Peripherals-Documentation/pull/73

I'm going to sleep, so you can test by yourself or I'll do it tomorrow :)

Test done, but found other issue about the color code lol

Oh, I'm trying to merge to a wrong branch, sry


[QUESTION] response_model_exclude in docs

when using response_model_exclude=[fields] is it possible to exclude those fields from displaying in the docs as well?

I think the best way to approach it would be to create a model that doesn't have the fields that you want to exclude.
And other models could inherit from it and add the extra fields in some contexts where needed.
response_model_exclude is, more or less, a dirty, quick, trick to solve something quickly and lazily... :man_shrugging: :sweat_smile:  ...But if that is a bit more important, I would suggest making it explicit in a model.

Makes sense! )


beams and toggle gears are not affected by block volume

beams and toggle gears are not affected by block volume this is not a major issue I just  wanted to point it out

What Crossroads version are you on?

the version is
2.26.5

There is no Crossroads 2.26.5. Do you mean 2.6.5?
I've just tested this, and both toggle gear and beam sounds are adjusting with my block volume for me.

must be an issue on my side i will look into it

Closing the issue for inactivity as it's not been reproduced.


fix: Add lifecycle rules to SG definitions to allow SG deletion

This PR is included in version 1.15.5 :tada:


Can't compile with MinGW (Win8 x64)

Hi, I can't compile the Hunter's GTest package with MinGW. The package provided by google compiles without problems.
I'm using g++ (i686-posix-dwarf-rev1, Built by MinGW-W64 project) 4.9.2 that comes along with Qt 5.5.
The build step output:
$ cmake --build .
[ 25%] Building CXX object CMakeFiles/gtest.dir/src/gtest-all.cc.obj
In file included from C:/Users/wprudencio/gtest-1.7.0-hunter-11/include/gtest/internal/gtest-internal.h:40:0,
from C:/Users/wprudencio/gtest-1.7.0-hunter-11/include/gtest/gtest.h:58,
from C:\Users\wprudencio\gtest-1.7.0-hunter-11\src\gtest-all.cc:39:
C:/Users/wprudencio/gtest-1.7.0-hunter-11/include/gtest/internal/gtest-port.h:1704:3: error: 'AutoHandle' does not name a type
AutoHandle thread_;
^
In file included from C:\Users\wprudencio\gtest-1.7.0-hunter-11\src\gtest-all.cc:43:0:
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-death-test.cc:626:3: error: 'AutoHandle' does not name a type
AutoHandle write_handle_;
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-death-test.cc:628:3: error: 'AutoHandle' does not name a type
AutoHandle child_handle_;
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-death-test.cc:633:3: error: 'AutoHandle' does not name a type
AutoHandle event_handle_;
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-death-test.cc: In member function 'virtual int testing::internal::WindowsDeathTest::Wait()':
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-death-test.cc:645:36: error: 'child_handle_' was not declared in this scope
const HANDLE wait_handles[2] = { child_handle_.Get(), event_handle_.Get() };
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-death-test.cc:645:57: error: 'event_handle_' was not declared in this scope
const HANDLE wait_handles[2] = { child_handle_.Get(), event_handle_.Get() };
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-death-test.cc:659:3: error: 'write_handle_' was not declared in this scope
write_handle_.Reset();
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-death-test.cc: In member function 'virtual testing::internal::DeathTest::TestRole testing::internal::WindowsDeathTest::AssumeRole()':
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-death-test.cc:709:3: error: 'write_handle_' was not declared in this scope
write_handle_.Reset(write_handle);
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-death-test.cc:710:3: error: 'event_handle_' was not declared in this scope
event_handle_.Reset(::CreateEvent(
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-death-test.cc:766:3: error: 'child_handle_' was not declared in this scope
child_handle_.Reset(process_info.hProcess);
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-death-test.cc: In function 'int testing::internal::GetStatusFileDescriptor(unsigned int, size_t, size_t)':
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-death-test.cc:1232:3: error: 'AutoHandle' was not declared in this scope
AutoHandle parent_process_handle(::OpenProcess(PROCESS_DUP_HANDLE,
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-death-test.cc:1235:7: error: 'parent_process_handle' was not declared in this scope
if (parent_process_handle.Get() == INVALID_HANDLE_VALUE) {
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-death-test.cc:1251:26: error: 'parent_process_handle' was not declared in this scope
if (!::DuplicateHandle(parent_process_handle.Get(), write_handle,
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-death-test.cc:1266:26: error: 'parent_process_handle' was not declared in this scope
if (!::DuplicateHandle(parent_process_handle.Get(), event_handle,
^
In file included from C:\Users\wprudencio\gtest-1.7.0-hunter-11\src\gtest-all.cc:45:0:
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc: In function 'void testing::internal::SleepMilliseconds(int)':
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc:139:6: error: redefinition of 'void testing::internal::SleepMilliseconds(int)'
void SleepMilliseconds(int n) {
^
In file included from C:/Users/wprudencio/gtest-1.7.0-hunter-11/include/gtest/internal/gtest-internal.h:40:0,
from C:/Users/wprudencio/gtest-1.7.0-hunter-11/include/gtest/gtest.h:58,
from C:\Users\wprudencio\gtest-1.7.0-hunter-11\src\gtest-all.cc:39:
C:/Users/wprudencio/gtest-1.7.0-hunter-11/include/gtest/internal/gtest-port.h:1377:13: note: 'void testing::internal::SleepMilliseconds(int)' previously defined here
inline void SleepMilliseconds(int n) {
^
In file included from C:\Users\wprudencio\gtest-1.7.0-hunter-11\src\gtest-all.cc:45:0:
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc: At global scope:
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc:143:1: error: 'AutoHandle' does not name a type
AutoHandle::AutoHandle()
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc:146:1: error: 'AutoHandle' does not name a type
AutoHandle::AutoHandle(Handle handle)
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc:149:1: error: 'AutoHandle' does not name a type
AutoHandle::~AutoHandle() {
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc:153:1: error: 'AutoHandle' does not name a type
AutoHandle::Handle AutoHandle::Get() const {
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc:157:6: error: 'AutoHandle' has not been declared
void AutoHandle::Reset() {
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc: In function 'void testing::internal::Reset()':
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc:158:29: error: too many arguments to function 'void testing::internal::Reset()'
Reset(INVALID_HANDLE_VALUE);
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc:157:6: note: declared here
void AutoHandle::Reset() {
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc: At global scope:
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc:161:6: error: 'AutoHandle' has not been declared
void AutoHandle::Reset(HANDLE handle) {
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc: In function 'void testing::internal::Reset(HANDLE)':
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc:163:7: error: 'handle_' was not declared in this scope
if (handle_ != handle) {
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc:164:21: error: 'IsCloseable' was not declared in this scope
if (IsCloseable()) {
^
In file included from C:/Users/wprudencio/gtest-1.7.0-hunter-11/include/gtest/internal/gtest-internal.h:40:0,
from C:/Users/wprudencio/gtest-1.7.0-hunter-11/include/gtest/gtest.h:58,
from C:\Users\wprudencio\gtest-1.7.0-hunter-11\src\gtest-all.cc:39:
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc:169:31: error: 'IsCloseable' was not declared in this scope
GTEST_CHECK_(!IsCloseable())
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/include/gtest/internal/gtest-port.h:1250:37: note: in definition of macro 'GTEST_CHECK_'
if (::testing::internal::IsTrue(condition))
^
In file included from C:\Users\wprudencio\gtest-1.7.0-hunter-11\src\gtest-all.cc:45:0:
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc: At global scope:
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc:175:6: error: 'AutoHandle' has not been declared
bool AutoHandle::IsCloseable() const {
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc:175:32: error: non-member function 'bool testing::internal::IsCloseable()' cannot have cv-qualifier
bool AutoHandle::IsCloseable() const {
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc: In function 'bool testing::internal::IsCloseable()':
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc:178:10: error: 'handle_' was not declared in this scope
return handle_ != NULL && handle_ != INVALID_HANDLE_VALUE;
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc: At global scope:
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc:181:1: error: redefinition of 'testing::internal::Notification::Notification()'
Notification::Notification()
^
In file included from C:/Users/wprudencio/gtest-1.7.0-hunter-11/include/gtest/internal/gtest-internal.h:40:0,
from C:/Users/wprudencio/gtest-1.7.0-hunter-11/include/gtest/gtest.h:58,
from C:\Users\wprudencio\gtest-1.7.0-hunter-11\src\gtest-all.cc:39:
C:/Users/wprudencio/gtest-1.7.0-hunter-11/include/gtest/internal/gtest-port.h:1396:3: note: 'testing::internal::Notification::Notification()' previously defined here
Notification() : notified_(false) {
^
In file included from C:\Users\wprudencio\gtest-1.7.0-hunter-11\src\gtest-all.cc:45:0:
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc:189:6: error: redefinition of 'void testing::internal::Notification::Notify()'
void Notification::Notify() {
^
In file included from C:/Users/wprudencio/gtest-1.7.0-hunter-11/include/gtest/internal/gtest-internal.h:40:0,
from C:/Users/wprudencio/gtest-1.7.0-hunter-11/include/gtest/gtest.h:58,
from C:\Users\wprudencio\gtest-1.7.0-hunter-11\src\gtest-all.cc:39:
C:/Users/wprudencio/gtest-1.7.0-hunter-11/include/gtest/internal/gtest-port.h:1405:8: note: 'void testing::internal::Notification::Notify()' previously defined here
void Notify() {
^
In file included from C:\Users\wprudencio\gtest-1.7.0-hunter-11\src\gtest-all.cc:45:0:
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc:193:6: error: redefinition of 'void testing::internal::Notification::WaitForNotification()'
void Notification::WaitForNotification() {
^
In file included from C:/Users/wprudencio/gtest-1.7.0-hunter-11/include/gtest/internal/gtest-internal.h:40:0,
from C:/Users/wprudencio/gtest-1.7.0-hunter-11/include/gtest/gtest.h:58,
from C:\Users\wprudencio\gtest-1.7.0-hunter-11\src\gtest-all.cc:39:
C:/Users/wprudencio/gtest-1.7.0-hunter-11/include/gtest/internal/gtest-port.h:1413:8: note: 'void testing::internal::Notification::WaitForNotification()' previously defined here
void WaitForNotification() {
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/include/gtest/internal/gtest-port.h: In constructor 'testing::internal::Mutex::Mutex()':
C:/Users/wprudencio/gtest-1.7.0-hunter-11/include/gtest/internal/gtest-port.h:1616:13: warning: 'testing::internal::Mutex::type_' will be initialized after [-Wreorder]
MutexType type_;
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/include/gtest/internal/gtest-port.h:1612:16: warning:   'unsigned int testing::internal::Mutex::owner_thread_id_' [-Wreorder]
unsigned int owner_thread_id_;
^
In file included from C:\Users\wprudencio\gtest-1.7.0-hunter-11\src\gtest-all.cc:45:0:
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc:198:1: warning:   when initialized here [-Wreorder]
Mutex::Mutex()
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc: In constructor 'testing::internal::ThreadWithParamBase::ThreadWithParamBase(testing::internal::ThreadWithParamBase::Runnable*, testing::internal::Notification*)':
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc:337:9: error: class 'testing::internal::ThreadWithParamBase' does not have any field named 'thread_'
: thread_(ThreadWithParamSupport::CreateThread(runnable,
^
In file included from C:/Users/wprudencio/gtest-1.7.0-hunter-11/include/gtest/internal/gtest-internal.h:40:0,
from C:/Users/wprudencio/gtest-1.7.0-hunter-11/include/gtest/gtest.h:58,
from C:\Users\wprudencio\gtest-1.7.0-hunter-11\src\gtest-all.cc:39:
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc: In member function 'void testing::internal::ThreadWithParamBase::Join()':
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc:346:38: error: 'thread_' was not declared in this scope
GTEST_CHECK_(::WaitForSingleObject(thread_.Get(), INFINITE) == WAIT_OBJECT_0)
^
C:/Users/wprudencio/gtest-1.7.0-hunter-11/include/gtest/internal/gtest-port.h:1250:37: note: in definition of macro 'GTEST_CHECK_'
if (::testing::internal::IsTrue(condition))
^
In file included from C:\Users\wprudencio\gtest-1.7.0-hunter-11\src\gtest-all.cc:45:0:
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc: In function 'bool testing::internal::IsCloseable()':
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-port.cc:179:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
In file included from C:\Users\wprudencio\gtest-1.7.0-hunter-11\src\gtest-all.cc:43:0:
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-death-test.cc: At global scope:
C:/Users/wprudencio/gtest-1.7.0-hunter-11/src/gtest-death-test.cc:123:13: warning: 'testing::internal::g_in_fast_death_test_child' defined but not used [-Wunused-variable]
static bool g_in_fast_death_test_child = false;
^
CMakeFiles\gtest.dir\build.make:62: recipe for target 'CMakeFiles/gtest.dir/src/gtest-all.cc.obj' failed
mingw32-make.exe[2]: *** [CMakeFiles/gtest.dir/src/gtest-all.cc.obj] Error 1
CMakeFiles\Makefile2:66: recipe for target 'CMakeFiles/gtest.dir/all' failed
mingw32-make.exe[1]: *** [CMakeFiles/gtest.dir/all] Error 2
makefile:126: recipe for target 'all' failed
mingw32-make.exe: *** [all] Error 2

The package provided by google compiles without problems.

@WesleyCeraso Can you point to the exact version or SHA1 of commit that's working for you? I've merged last version into: https://github.com/hunter-packages/gtest/releases/tag/v1.7.x-hunter-0 and still see that error.

I can compile gtest in tag release-1.7.0, I have not realized you were following the master. Once I checked out to master I got the same error on the official repository.

I just used bisect and found the commit that broke the build:
a6340420b9cee27f77c5b91bea807121914a5831 is the first bad commit
commit a6340420b9cee27f77c5b91bea807121914a5831
Author: kosak<EMAIL_ADDRESS>Date:   Mon Mar 24 21:58:25 2014 +0000
Implement threading support for gtest on Windows.
Also, stop using localtime(). Instead, use localtime_r() on most systems, localtime_s() on Windows.

I opened an issue in googletest project (googletest#606)

Package 1.7.0-hunter-6 is the last one to build with MinGW

I have not realized you were following the master

I've just tried to apply some fixes like https://github.com/forexample/hunter-simple/issues/2
The whole state of GTest is quite unstable from my point of view :) So the last official release is 1.7.0 and it's about 2 years old. This repository was forked from https://chromium.googlesource.com/external/gtest but now looks like official GTest is: https://github.com/google/googletest which has a completely different structure and can't be merged...

I opened an issue in googletest project google/googletest#606

Great, thank you.

Package 1.7.0-hunter-6 is the last one to build with MinGW

Thanks for testing, applied: https://github.com/ruslo/hunter/commit/0a47a5eb2d5d357fc820023bcc7ae550a7709dfc
Release with this change: https://github.com/ruslo/hunter/releases/tag/v0.12.17

@WesleyCeraso Closing this since it's not a fork or Hunter issue and workaround applied. Let me know if there will be some other errors.

Thank you for the support.

I am experiencing the same issue with the downgraded package.
I found the issue in the original bug-report (https://github.com/google/googletest/issues/606), and I see the same bug in in the downgraded package's sources.

@andoks Are you experiencing the same error with 1.7.0-hunter-6?

@WesleyCeraso I tested using ruslos update HunterGate string (https://github.com/ruslo/hunter/releases/tag/v0.12.17), now I'm quite inexperienced with Hunter in general, so it is quite possible I did something wrong.
In my project I updated the HunterGate stanza, I went into my HUNTER_ROOT, and did a git clean -fxd, then ran cmake on my project from a clean build dir.

I went into my HUNTER_ROOT, and did a git clean -fxd, then ran cmake on my project from a clean build dir

@andoks git version of Hunter is only for developers, there is no need to clone repository if you're user. HunterGate will download tar.gz archive automatically. You need to remove git version of Hunter and allow HunterGate module to do his work or you can update git repository manually (check that you have commit: 0a47a5eb2d5d357fc820023bcc7ae550a7709dfc).

@ruslo indeed it seems like I have skimmed the Hunter documentation a bit too quickly. When I removed HUNTER_ROOT, it worked. Sorry for the noise.
Thank you =)

@andoks Also just for your information you can set HUNTER_STATUS_DEBUG=ON and see what version downloaded exactly:
-- downloading...
     src='https://github.com/hunter-packages/gtest/archive/v1.7.0-hunter-6.tar.gz'
     dst='C:/.../_Base/Download/GTest/1.7.0-hunter-6/64b9314/v1.7.0-hunter-6.tar.gz'
     timeout='none'

You should see this one too:
-- [hunter] GTEST_ROOT: C:/.../_Base/79f9fe4/deea0cb/2457964/Install (ver.: 1.7.0-hunter-6)

@andoks I've added a warning to README: ...it means that there is no need to clone this repository in general... and to HunterGate: ...In this case you have to update your git repo manually...

@ruslo nice tip regarding DEBUG=ON, that will definetlly come in handy =)
May I suggest expanding the HUNTER_ROOT variable explanation? e.g
Set HUNTER_ROOT environment variable (recommended but not mandatory, see other options)

Set HUNTER_ROOT environment variable (recommended but not mandatory, see other options). This is where Hunter will automatically download the version specified in your configuration (unless you have manually cloned Hunter to this directory, in that case the clone will override the configuration)
Or something similar

This is where Hunter will automatically download the version specified in your configuration (unless you have manually cloned Hunter to this directory, in that case the clone will override the configuration)

@andoks I've added a link to the README First steps section. Now it goes to the wiki page with next warning:
 Warning! If you manually cloned Hunter repository for development purpose the values of URL and SHA1 of HunterGate will be ignored, see notes

@ruslo

I've added a link to the README First steps section. Now it goes to the wiki page with next warning:
That's seems ok too.

The reason I suggested explaining it in clear-text in the bullet itself, is that intuitively (subjective, I know), I would expect that if I set a variable like that, it should actually point to something pre-existing (href SYSROOT when cross-compiling, $PATH etc), and not just some empty "caching" directory.

The reason I suggested explaining it in clear-text in the bullet itself, is that intuitively (subjective, I know), I would expect that if I set a variable like that, it should actually point to something pre-existing

@andoks How about that:
Set HUNTER_ROOT environment variable to an empty directory. This directory will
 be used by HunterGate module for storing packages and utility files. Using
 environment variable is recommended but not mandatory, see other options.

https://github.com/ruslo/hunter#first-step

@ruslo yeah, that is a very nice explanation =)
Just to make sure, does it ever make sense to set the HUNTER_ROOT variable to point to a clone of the hunter repository?

Just to make sure, does it ever make sense to set the HUNTER_ROOT variable to point to a clone of the hunter repository?

Yes, if you want to add new packages/patches and test them.

Yes, if you want to add new packages/patches and test them

@andoks Updates:

HUNTER_ROOT for use and for test: https://github.com/ruslo/hunter/wiki/dev.hunter.root
Add link for HUNTER_ROOT docs: https://github.com/ruslo/hunter/wiki/usr.variables#hunter_root
Add link for "adding new package" docs: https://github.com/ruslo/hunter/wiki/usr.adding.new.package#05-test

Great work, thanks @ruslo
In my case the most important update was the clarification regarding HUNTER_ROOT in first steps, since I was just "shopping around" for easier ways of handling dependencies in our project. And when "shopping around", I tend to skim through documentation quickly.
And the rest of the updates regarding HUNTER_ROOT will probably come in handy if we decide that we want to try to handle our dependency on Protobuf with Hunter too (hopefully including automatically execution of protoc).
Again, thanks for all the help and support!

if we decide that we want to try to handle our dependency on Protobuf with Hunter too

@andoks Just for your information: https://github.com/ruslo/hunter/issues/97


Compile on MacOS (Sierra)

Minimal changes to make it compile and work properly on MacOS with system's Clang

nope ?

Pleaaaaase :)


Update to GitHub and Export Controls policy - Winter 2019

This update to the GitHub and Export Controls policy includes clarifications of existing policies, including changes to the following sections:

GitHub.com
Enterprise Server

Thank you all for your comments and feedback! As stated in our blog post, the comment period ends today. I am closing this pull request for internal review of any remaining comments. We will commit final clarifications or edits when we merge this pull request next Friday, April 19. At that time, the updated version of this policy will be effective.


增加regex-return-regex二次匹配规则，修复了全文匹配行数的错误

增加regex-return-regex二次匹配规则
修复了全文匹配行数的错误
同时修复误用print，改为log

Coverage decreased (-0.9%) to 39.202% when pulling aec379de36dc69e307eae955106af3c59178e73a on boke1208:sissel_dev into 26fab6809126aa17867a5aa8ca65d935b5336ab3 on LoRexxar:develop.

Coverage decreased (-0.9%) to 39.202% when pulling aec379de36dc69e307eae955106af3c59178e73a on boke1208:sissel_dev into 26fab6809126aa17867a5aa8ca65d935b5336ab3 on LoRexxar:develop.

Coverage decreased (-0.9%) to 39.202% when pulling aec379de36dc69e307eae955106af3c59178e73a on boke1208:sissel_dev into 26fab6809126aa17867a5aa8ca65d935b5336ab3 on LoRexxar:develop.

Coverage decreased (-0.9%) to 39.202% when pulling aec379de36dc69e307eae955106af3c59178e73a on boke1208:sissel_dev into 26fab6809126aa17867a5aa8ca65d935b5336ab3 on LoRexxar:develop.


pipewire: 0.3.63 -> 0.3.64

Description of changes
New upstream release with some nice fixes: https://gitlab.freedesktop.org/pipewire/pipewire/-/releases/0.3.64
Supersedes #208828. Going into -next because we still don't have this stuff built.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Could we also backport these to 22.11?

I don't see why not.

:pray:, I'm having bluetooth issues there


lsp_lines integration

This issue is complementary to lsp_lines #42
Would it be possible for the plugin to implement some sort of interface so that lsp_lines.nvim and indent-blankline.nvim can communicate to correctly show indent guides on the diagnostic lines? And would someone be willing to implement it?

I am currently working on v3 for indent-blankline.
Exposing an api for other plugins to influence the indentation, and or get indentation is planned.
I still have not started looking into this, so I'm not sure yet if and how it will work.
Also no ETA, might take some time, sorry

All the building blocks are available in IBL to make this work. But the actual implementation would need to be in lsp_lines.
I'm closing the ticket here.


Color.Manipulate.lighten and darken are switched

darken adds to the lightness instead of subtracting from it.
hsla hue saturation (limit (lightness + offset)) alpha

@jtee thanks for spotting the bug


KAFKA-12691: Add case where task can be considered idling

Currently task is reporting the time it started idling as when the task is suspended where it should also take into account enforced non processing.
Committer Checklist (excluded from commit message)

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

@rodesai @ableegoldman @abbccdda @mjsax
Turns out there is another case where we should consider a task to be idling. If you can give this a review soon that would be great. I would like to get this in before Wednesday

Btw: can we add some tests?


Supporting whitelisting CVE's / Dependencies

It would be nice to be able to ignore / whitelist certain dependencies. This way we can keep working if no fix exist yet/

I thought about having some config which sits with the code (so not in .github dir) which contains a whitelist (or ignorelist) which at least contains

CVE
Possible also
End date until whitelist is valid (so required a review after x months)

And also i don't now how the CVE's on dependencies work, but i guess CVE's on a dependency can also be updated (added text, change of severity) so it would be nice to link the ignore  a certain version of the CVE.

We'll likely move our config options (licenses and allow/denylist) to an external config file in the upcoming months to make this Action easier to install in big organizations. Will take a look at this when we do the migration.

Thnx for taking a look at it!

I don't see how this can be fully utilized without whitelisting really, looks like a must for anything beyond the MVP phase.
Is there some workaround in a meantime at least?

@LiuVII what do you think about adding a new config option (a list called ignore?) that is checked against the advisory_ghsa_id field of the API response? We don't receive CVEs in the API response, hence the fallback to GHSA ids.
If you need help getting a PR started please let me know!


Gradle build failed: Could not initialize class org.codehaus.groovy.reflection.ReflectionCache

Version Information
Minecraft version: 1.16.5
Forge version: 36.2.39
Other mods (if applicable): None
Steps to reproduce:

Clone the MC_1.16 branch with "git clone -b MC_1.16"
Then "cd CubicChunks"
Now execute "./gradlew build"
It'll fail with a Could not initialize class org.codehaus.groovy.reflection.ReflectionCache error.

Expected Behavior:
The build should be successful instead of failing.
Actual Behavior:
The build has failed.
Link to crash log (if applicable - use a site such as hastebin: None

This is likely caused by using too new java version. And 1.16.x isn't and won't be supported. We switched all development to 1.17 snapshots very early.


Refactor codebase for better readability season

Rabbit season

Failed Test
Failure Summary
Logs

[chromium] should show the FAQ page correctly.
The FAQ page was not loaded correctly, and the title and heading were not found.
Logs ↗

Flaky Test
Failure Summary
Logs

---
---
---

[chromium] should display user profile information correctly.
The test timed out waiting for the element 'User ID: eli3cruz' to become visible.
Logs ↗

[chromium] should return list of users correctly.
The API call to get the list of users failed with a 404 Not Found error.
Logs ↗

[chromium] should display error message for invalid login correctly.
The expected HTTP status code 401 was not received, instead a function was returned.
Logs ↗

[chromium] should login with credentials correctly correctly.
The login request to the server failed with a 404 Not Found error.
Logs ↗

View Full Report ↗ ⋅ Docs


Not able to create cucumber.json

using below
"dependencies": {
"cypress": "^3.3.0",
"cypress-cucumber-preprocessor": "1.14.0"
},
"cypress-cucumber-preprocessor": {
"nonGlobalStepDefinitions": true,
"cucumberJson": {
"generate": true,
"outputFolder": "cypress/cucumber-json",
"filePrefix": "",
"fileSuffix": ".cucumber"
}
},

It appears the report made optional starting v1.14.0 release. Not sure if something is causing issues there (w.r.t cypress version 3.3.0). Can you try updating plugin version to something 1.16.2. or 1.17.0 and see if that works?
My working configuration is here:
{
"dependencies": {
"cypress": "3.7.0",
"cypress-cucumber-preprocessor": "1.16.2",
},
"cypress-cucumber-preprocessor": {
"nonGlobalStepDefinitions": true,
"cucumberJson": {
"generate": true,
"outputFolder": "cypress/cucumber-json",
"filePrefix": "",
"fileSuffix": ".cucumber"
}
}
}


added tool config

yes, we've been thinking about it too, need to test it first (whether you need a single step or still two steps)


yamellinting ceph-ansible

Hello :wave:
A very fancy ansible, this ceph-ansible. thanks a lot for this. :heart:
After noticing a few trailing whitespaces, I noticed that there is no yamllinting here yet. This pull request might change that.
Maybe you like it? :kissing_heart: if you have other yamllinting preferences, I'll be happy to adjust it a bit. :wink:

jenkins test centos-non_container-purge

jenkins test centos-non_container-collocation

I am not sure why the centos-container-collocation is failing. If there is anything I can help to fix it, please give me a hint :heart_decoration:

except for the extra spaces in vagrant_variables.yml files, that looks good to me.
thanks for this pr @DO1JLR

jenkins test centos-container-collocation

:grey_question: is there anything I can do to help merge this pull request? :innocent:

@guits  is there anything I can do to help merge this pull request? :innocent:


rustic-cargo.el requires the location of the cargo binary, not rustic-compile.el

I have a setup in which there is no unique cargo binary for every project, but instead each project asks for a certain cargo binary, which is provided in the PATH.
In short, this means that, in a shell, for example, you can run cargo, but there is no way to know beforehand where the binary will be. This works well when I run M-x rustic-compile, due to the fact that rustic simply execute a command (see this line), but it does not work when I run M-x rustic-cargo-test (for example) because then rustic uses a customizable path instead of letting the path being resolved dynamically (see this definition).
Concretely, the former one simply calls cargo build, and succeeds, whereas the latter one calls ~/.cargo/bin/cargo test, and fails, because there is no such file.
It's quite unclear to me why there are two different ways in the same project of calling cargo, and what is even more unclear to me is why one of them presumes the location of the binary. It seems to me that the correct one is to call cargo <...>, not ~/.cargo/bin/cargo <...>.
Because of that, I'm not sure whether to label this as a bug, or as a feature request, but anyways it would be nice if all rustic commands worked like rustic-compile, resolving the command on-the-fly instead of having to customize the binary location by hand.

I recently added remote support for rustic and this only works with absolute paths. But I can understand you(we already had this issue in the past). I guess I will just add two variables, one for local one for remote.

It's quite unclear to me why there are two different ways in the same project of calling cargo

That's because providing remote support is work in progress.

Should be working again, sorry for that. Sometimes I introduce bugs that I already fixed in the past =)
Thanks for the bug report!

Indeed, rebuilt Emacs this morning and it's working like a charm.

Thanks for the bug report!

Well, thanks for the bug fix =)


READMEに関係図を表示

This change is

Reviewed 1 of 1 files at r1.
Review status: 0 of 1 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


replace readme with readme path in dev

with this we can now run
cargo run -- build --config-path=dev/oranda.json

or with watch:
cargo watch -c -w src -x  'run -- build --config-path=dev/oranda.json'

and get a dev version

Yeah, i merged it without changing this, my bad


[i18n]Add i18n support

Add i18n support.
I can contribute Chinese translation.

Sure, contributions are always welcome.

Sure, contributions are always welcome.

@pcislo  When you put po files on weblate.org,launchpad or other online translate website, I can contribute Chinese translation on that website.


Add cache freshness option to the S3 cache plugin

Optionally use an S3_CACHE_TTL environment variable to only fetch objects modified in
the last x hours. For example, setting the variable to 24 will force the cache to bypass
and recache files more than a day old.
Makes use of the IfModifiedSince parameter available in aws-sdk.S3#getObject.
http://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/S3.html#getObject-property

+1

Good idea but not great for SEO because any request to a URL older than 1 day will be a cache miss. If your website has more than just a few pages then most requests to URLs would be older than 1 day and you'd have long response times. It's definitely much better to recache over pages to keep them up to date.
Feel free to write your own plugin with that functionality. It's easy to pull in plugins from npm and use them in the Prerender server.

@thoop I agree with your points. However, I think there's a misunderstanding about how this option works. 24 hours is an admittedly bad example. With this option, you choose the cache time yourself. My goal here was to provide an option which mimics the cache freshness slider on prerender.io.

Yeah it would be better if it's configurable but Prerender.io cache freshness works by keeping pages cached and recaching pages older than the cache freshness. We don't invalidate pages out of the cache and this change does effectively invalidate pages out of the cache. When rendering pages can take 5 or more seconds, invalidation needs to be kept to a minimum. We want to make sure we promote the best practices for SEO.

Got it. Thanks for the clarifications


Riddhikumari/anomalies grouping

PR Checklist

[ ] Explain your changes, so people looking at the PR know what and why, the code changes are the how.
[ ] Validate your changes using one or more of the testing methods.

If adding or updating templates:

[ ] post a screenshot of templates and/or gallery changes
[ ] ensure your template has a corresponding gallery entry in the gallery folder
[ ] If you are adding a new template, add your team and template/gallery file(s) to the CODEOWNERS file. CODEOWNERS entries should be teams, not individuals
[ ] ensure all steps have meaningful names
[ ] ensure all parameters and grid columns have display names set so they can be localized
[ ] ensure that parameters id values are unique or they will fail PR validation (parameter ids are used for localization)
[ ] ensure that steps names are unique or they will fail PR validation (step names are used for localization)
[ ] grep /subscription/ and ensure that your parameters don't have any hardcoded resourceIds or they will fail PR validation
[ ] remove fallbackResourceIds and fromTemplateId fields from your template workbook or they will fail PR validation

The PR supports Grouping of anomalies which came up as a Feedback from the Digital Prod System on the Private Preview experience.

The anomalies are grouped on different issue scenarios on the main screen with a filter on Scope and the Issue Type.
The anomalies with all the same columns including detected and reported time are grouped on Scope Type. The Scope column in the Anomlaies table lists all the grouped scopes and the flyout provides a dropdown to select a scope and see details respective to that.


create new checks that verify the naming conventions of TO, ETO, CTO, Entity, Dao, Repository, etc.

We should add new checks that verify the naming conventions of devonfw according to inheritance.

Classes extending AbstractEto shall end with Eto
Classes extending AbstractCto shall end with Cto
Classes extending AbstractTo but neither AbstractEto nor AbstractCto shall end with To
Classes extending AbstractSearchCriteriaTo shall end with SearchCriteriaTo
Classes implementing PersistenceEntity (extending ApplicationPersistenceEntity) shall end with Entity
(Non-Abstract) Classes extending AbstractUc shall start with Uc and end with Impl (also they should implement an interface with the same name except the suffix Impl)
Interfaces extending DefaultRepository shall end with Repository
Interfaces extending Dao shall end with Dao
(Non-Abstract) Classes extending AbstractDao shall end with DaoImpl
Also the suffixes like Eto, Cto, To, Repository, Dao, DaoImpl should be reserved for their purpose. That means if such suffix is used the above rule must apply. Otherwise an issue is generated.

Here extending or implementing means either direct or indirect (via inheritance).

Done with PR #23


Downloading Answers does not work

Downloading answers to a CSV file does not work. With no questions filled out or all questions filled out the resulting CSV is blank.

openchain-answers.xlsx

I was able to duplicate this problem so i should be able to fix it.  I'll take a look over the next couple of days.

Update: this only occurs in the production instance.  On my local development environment, it works fine.  I'll need to add some additional logging to figure this out.  It may take a few days to resolve.

Curiouser and curioser.  The production environment works for my admin login but doesn't work for my normal user login.  When I tried this on my development machine, the admin worked and the normal user did not work.  That was until I set some breakpoints to debug the problem.  Now it works for the normal user on my development environment.
I'll continue trying to debug.

The download answers only downloads answers after they are saved.
If you don't save the answers, it will not be reflected in the CSV.
The CSV also does not include any answers which are not answered.
This is actually working as designed, but the design has a couple of problems.
If you're just trying to download the survey using the download answers, you will only see survey questions.
The second problem is if there are answers when the survey is not saved, I would expect to see what I see on my screen and not what is stored on the computer.
I'm going to close this and open two enhancements:

Issue #149 to warn users when downloading with unsaved answers
Issue #150 to include unanswered questions in the download

I also found another issue when debugging.  If a user leaves the page without saving the questions, there is no warning.  i'll enter a new issue to track.

Thanks Gary! I commented in the new issues.


added tests for elastic search; changed the searchclientinterface; changed the httpClientInterface;

added tests for elastic search; changed the searchclientinterface; changed the httpClientInterface
Attention: There seems to be an error within the /Buzz/lib/Buzz/Client/FileGetContents.php when executing the Doctrine/Search/Http/Client/BuzzTest.php. Therefor I just commented out the BuzzTest::testCallNotExistingHost-Test to commit my changes.

Doctrine\Search\Http\Adapter\Client\BuzzTest::testCallNotExistingHost
Undefined variable: http_response_header

/Users/mikelohmann/Sites/doctrine-search.local/search/lib/vendor/Buzz/lib/Buzz/Client/FileGetContents.php:49
/Users/mikelohmann/Sites/doctrine-search.local/search/lib/vendor/Buzz/lib/Buzz/Browser.php:87
/Users/mikelohmann/Sites/doctrine-search.local/search/lib/vendor/Buzz/lib/Buzz/Browser.php:66
/Users/mikelohmann/Sites/doctrine-search.local/search/lib/Doctrine/Search/Http/Client/BuzzClient.php:53
/Users/mikelohmann/Sites/doctrine-search.local/search/tests/Doctrine/Search/Http/Client/BuzzTest.php:41

There seems to be an error within the /Buzz/lib/Buzz/Client/FileGetContents.php when executing the Doctrine/Search/Http/Client/BuzzTest.php. Therefor I just commented out the BuzzTest::testCallNotExistingHost-Test to commit my changes.

Doctrine\Search\Http\Adapter\Client\BuzzTest::testCallNotExistingHost
Undefined variable: http_response_header

/Users/mikelohmann/Sites/doctrine-search.local/search/lib/vendor/Buzz/lib/Buzz/Client/FileGetContents.php:49
/Users/mikelohmann/Sites/doctrine-search.local/search/lib/vendor/Buzz/lib/Buzz/Browser.php:87
/Users/mikelohmann/Sites/doctrine-search.local/search/lib/vendor/Buzz/lib/Buzz/Browser.php:66
/Users/mikelohmann/Sites/doctrine-search.local/search/lib/Doctrine/Search/Http/Client/BuzzClient.php:53
/Users/mikelohmann/Sites/doctrine-search.local/search/tests/Doctrine/Search/Http/Client/BuzzTest.php:41


Presentation: Contemporary and Established Provenance Issues in Natural History Collections

Lightening talk for ProvenanceWeek 2021, T7 Workshop.

Livermore, Laurence; Scott, Ben; Dillen, Mathias (2021): Contemporary and Established Provenance Issues in Natural History Collections. figshare. Presentation. https://doi.org/10.6084/m9.figshare.15035370.v1


Set stop=true if an error occurs while creating a socket connection

When an exception is thrown while opening a connection or subscribing, stop still remains false.
Users of WebsocketClient class will have no way to know whether a connection is live and functioning. This commit allows users to rely on ws_client.stop to figure this out.

I nd help I’m trying to get my coins


Multiple sqoop queries fix

When importing data using Sqoop using a query Sqoop creates a java class and jar with a generic name. If there are 2 sqoop imports in the same job they will have the same name and clash causing the second import to fail.
This sets a unique class name for each sqoop job.
This closes #286.

:+1:


rustic-rs: 0.4.1 -> 0.4.2

Description of changes

https://github.com/rustic-rs/rustic/releases/tag/v0.4.2
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

 Looks as if this is somehow automatically generated.

@NobbZ nixpkgs-review post-result: https://github.com/Mic92/nixpkgs-review

Nice, I wasn't aware of post-result, thanks!


feat: billing model support when creating a Kafka instance

What this PR does / why we need it:

renames CreateKafkaInstanceWithSize to be CreateKafkaInstance
splits the single state machine that was behind the dialog with three different machines:

one that, based on the results of the first API call, decides if we should be presenting the form to create standard machines or trial machines
one for trial machines
one for standard machines

adds the UI elements required for the billing
adds tests for the above while not breaking the previous tests

Which issue(s) this PR fixes
https://issues.redhat.com/browse/MGDSTRM-8965
Verification steps
All previous stories are left unchanged. New ones have been added to the FormLoad section:

User has a single active subscription in a marketplace and pre-paid quota - Standard
User has multiple active subscriptions in many marketplaces and pre-paid quota - Standard
User has multiple active subscriptions in many marketplaces and no pre-paid quota - Standard
User has multiple active subscriptions in a single marketplaces and no pre-paid quota - Standard
User has a single active subscription in a marketplace and no pre-paid quota - Standard
User has a single active subscription in Red Hat Marketplace and no pre-paid quota - Standard

Your updates look great! I only did a quick pass through the new stories. Here are a couple of things I noticed.

In User has a single active subscription in a marketplace and no pre-paid quota - Standard, there should be a couple of additional pieces of information that display to the user:

In the tile that's disabled, there should be additional text included in the tile: "Incompatible with current billing option". You can see that example here
In the Details card, there should be additional text that communicates the billing info. You can see details about that in this document.

Wherever billing displays (i.e. in the form or in the Details card) there should be a help popover that describes what this means. You can see the popover text in the same document as above, in this section.

Your latest updates look good! Here are a few things I noticed in my latest review:

Quota Available - Standard - Looking at the knobs, it looks like this example is meant to cover the use case where a user only has a RH prepaid subscription. In this case, I was expecting the text "Red Hat prepaid" to display as the "Billing" value in the Details panel, similar to the last 2 examples. Can you add this property to the Details card for this case? This allows us to provide a popover that explains there are other billing options available with a link to overview page with CTAs for purchasing on the various marketplaces.

This question applies to the other "Standard" examples that existed previously

Over Quota - Standard - The message text "contact us" should be a link, similar to how it displays in this current example.
User has prepaid quota, a single active subscription in RH marketplace - I'm not sure if it's me or the example, but I don't see the billing options in this example
User has no prepaid quota, multiple active subscriptions in many marketplaces AND User has no prepaid quota, multiple active subscriptions in a single marketplaces - In a previous design review, Duncan suggested we avoid displaying tiles in a single column layout, and if only one tile exists, it should occupy half the width. I'm not sure if this is an easy update or not, but just wanted to mention it if it's possible. I don't see this as a blocking issue.

And one other thing I noticed about the Trial examples. Not sure if this is an issue for this PR or not.

Quota Available - Trial - The Details panel shows "Size" which should only display for standard instance. Trial instances should show a "Duration" property instead. This might be a regression from our current example.

This issue appears to be present in the other Trial examples

1. [**Quota Available - Standard**](https://619e1921b3e38b003afeb2be-ddcnkanxby.chromatic.com/?path=/story/kafka-createkafkainstance-stories-formload--quota-available-on-form-load) - Looking at the knobs, it looks like this example is meant to cover the use case where a user only has a RH prepaid subscription. In this case, I was expecting the text "Red Hat prepaid" to display as the "Billing" value in the Details panel, similar to the [last 2 examples](https://619e1921b3e38b003afeb2be-ddcnkanxby.chromatic.com/?path=/story/kafka-createkafkainstance-stories-formload--single-subscription). Can you add this property to the Details card for this case? This allows us to provide a popover that explains there are other billing options available with a link to overview page with CTAs for purchasing on the various marketplaces.

   * This question applies to the other "Standard" examples that existed previously

I was under the assumption that anything about billing was to be displayed only to users that had the option. I can change this to be shown for all users; I just wanted to double-check this with you.

2. [**Over Quota - Standard**](https://619e1921b3e38b003afeb2be-ddcnkanxby.chromatic.com/?path=/story/kafka-createkafkainstance-stories-formload--over-quota-on-form-load) - The message text "contact us" should be a link, similar to how it displays in [this current example](https://redhat-developer.github.io/app-services-ui-components/?path=/story/kafka-createkafkainstancewithsizes-stories-formload--over-quota-on-form-load).

Ah, good catch, thanks!

3. [**User has prepaid quota, a single active subscription in RH marketplace**](https://619e1921b3e38b003afeb2be-ddcnkanxby.chromatic.com/?path=/story/kafka-createkafkainstance-stories-formload--prepaid-and-single-marketplace-subscription-all-rh) - I'm not sure if it's me or the example, but I don't see the billing options in this example

It does show to me. Maybe it required some scrolling, which wasn't obvious at first glance? Especially with MacOS that hides the scrollbar, this is quite a likely scenario.

4. [**User has no prepaid quota, multiple active subscriptions in many marketplaces**](https://619e1921b3e38b003afeb2be-ddcnkanxby.chromatic.com/?path=/story/kafka-createkafkainstance-stories-formload--only-marketplace-subscriptions) AND [**User has no prepaid quota, multiple active subscriptions in a single marketplaces**](https://619e1921b3e38b003afeb2be-ddcnkanxby.chromatic.com/?path=/story/kafka-createkafkainstance-stories-formload--single-marketplace) - In a previous design review, Duncan suggested we avoid displaying tiles in a single column layout, and if only one tile exists, it should occupy half the width. I'm not sure if this is an easy update or not, but just wanted to mention it if it's possible. I don't see this as a blocking issue.

Done, I think. I used a Gallery inside the FlexItem that creates the two columns. It looks like it automatically adapts the gallery items based on the available space.

And one other thing I noticed about the Trial examples. Not sure if this is an issue for this PR or not.
1. [**Quota Available - Trial**](https://619e1921b3e38b003afeb2be-ddcnkanxby.chromatic.com/?path=/story/kafka-createkafkainstance-stories-formload--trial-available-on-form-load) - The Details panel shows "Size" which should only display for standard instance. Trial instances should show a "Duration" property instead. This might be a regression from our [current example](https://redhat-developer.github.io/app-services-ui-components/?path=/story/kafka-createkafkainstancewithsizes-stories-formload--trial-available-on-form-load).

   * This issue appears to be present in the other Trial examples

Good catch again! This should be fixed now.

1. [**Quota Available - Standard**](https://619e1921b3e38b003afeb2be-ddcnkanxby.chromatic.com/?path=/story/kafka-createkafkainstance-stories-formload--quota-available-on-form-load) - Looking at the knobs, it looks like this example is meant to cover the use case where a user only has a RH prepaid subscription. In this case, I was expecting the text "Red Hat prepaid" to display as the "Billing" value in the Details panel, similar to the [last 2 examples](https://619e1921b3e38b003afeb2be-ddcnkanxby.chromatic.com/?path=/story/kafka-createkafkainstance-stories-formload--single-subscription). Can you add this property to the Details card for this case? This allows us to provide a popover that explains there are other billing options available with a link to overview page with CTAs for purchasing on the various marketplaces.

   * This question applies to the other "Standard" examples that existed previously

I was under the assumption that anything about billing was to be displayed only to users that had the option. I can change this to be shown for all users; I just wanted to double-check this with you.

This is now implemented, but the information will show only once a user has selected a billing option in case he has a choice. Hope this is the expected behavior.

I'll merge this so I can get something on stage. For any issue, we can open new PRs to fix them.

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