setParameterValue from UI has no effect

This is an issue I noticed while starting to implement an UI to my plugin
here, the UI events properly get called, and the UI gets updates from the plugin, like when the value changes in the plugin through automation for instance, the UI will get updated to reflect the change however the reverse doesn't seem to be the case, updates to the value sent from the UI don't seem to trigger the setParameterValue method from the plugin, the breakpoint on the video is never reached
I'm using vst3, i dunno if it's a general dpf issues or a vst3 only issue
https://user-images.githubusercontent.com/16335601/147703296-97ee2680-a04d-4050-9243-cc41c2a1f984.mp4

I wonder if it is related to this issue https://github.com/DISTRHO/DPF/issues/343

this was broken on the experimental vst3 side until a 1-2 days ago.
so retry with latest and see if it works now or not.

this was broken on the experimental vst3 side until a 1-2 days ago. so retry with latest and see if it works now or not.

I retried on the latest commit and it still doesn't seem to be working, i'm going to test on another daw to see if it's reaper specific

Never mind, seems like it's now fixed, it didn't trigger the breakpoint in my new test because i added the breakpoint at runtime, seems like it doesn't like it when i add them later


High priority notification even if "do not disturb" enabled

Checklist

[X] I have used the search function to see if someone else has already submitted the same feature request.
[X] I will describe the problem with as much detail as possible.
[X] This issue only contains a request for one single feature, not multiple (related) features.

App version
6.603
Problem you are trying to solve
Ability to provide a high priority notification if an important email is received.  This could be based on subject or based on sender.  High priority should be able to override "do not disturb" setting if needed and be an option by user for each topic/sender.
Suggested solution
Example scenarios where immediate attention is required and "do not disturb" should be ignored (by user selection)

Sensor in home detects water leak and sends email notification which is critical
Utility notifies of potential water leak
Important contact (spouse, business associate, etc) sends message that you are waiting for
Important topic (home purchase details, etc)

There are lots of reasons why an email might be critical to know about as soon as received.  If it comes in at night, it might be important enough to be woken up for.  Push notifications work if both parties are on them but sometimes email is the only mechanism to send such a message.
Screenshots / Drawings / Technical details
I have been using K9 for years and have never seen this feature though looked in app many times.  I searched the github but found nothing.  The K9 community forum seems to be offline so I don't see any other vehicle to make such a request.

Duplicate of #5118


Add notebook for multilingual-CLIP

Now that multilingual clip has been added to the client, a notebook explaining how is it used should be added to the client.

https://github.com/jina-ai/finetuner/pull/611


Automate core gafferpy maintenance with fishbowl

Fishbowl was integrated as a sub-module to gafferpy in #981. It is now used to generate the core api of gafferpy, but this must be done manually after every Gaffer release and before every gaffer-tools release.
To use fishbowl to generate every supported Gaffer Operation, the spring-rest api must be used. This is because it contains every store on its classpath and has an extra endpoint to get details of those Operations, even if they aren't supported by the current running store.
However, there is no simple way to get Gaffer's spring-rest running within the gaffer-tools repository.
The gaffer-rest docker image could be used, but right now this is built in the gaffer-docker release stage. This happens after a gaffer-tools release, as it relies on the new release of the ui, so there is a dependency order issue.
If we decided to build an image as part of a Gaffer release, then perhaps this could be used. This has been proposed in https://github.com/gchq/Gaffer/issues/2694.

Wouldn't it be possible to start the spring-rest in a similar way to how the existing Python and Selenium tests start the road-traffic example at the moment?
https://github.com/gchq/gaffer-tools/blob/45f5fd1920bf5b93459f16df097224c1c2d0ed50/.github/workflows/continuous-integration.yaml#L63-L66
The spring-rest can be started in a similar way by using the -exec jar. As we don't need any data for this, it wouldn't need any config files or scripts and could simply be run as a java command directly from the workflow step.
Do you envisage this happening as part of the update-gaffer-version workflow? So long as the new Gaffer has been released and the jars are on central, it will be possible to pull down the latest spring, run it, then run fishbowl, and take the resulting generated code and add that into the PR which is generated for updating the Gaffer version.

I was indeed thinking it would be best placed in the update-gaffer-version workflow.
The mvn script cannot be used in the same way though.
You're right that it could find the correct jar from maven central and pull that down before running it with java.
Alternatively we could release the spring-rest jar as a release artifact in Gaffer.

Closed by https://github.com/gchq/gaffer-tools/pull/1033


spike: move test to installCheck phase

Motivation for this change
The test doesn't need to run in an actual VM, so there is no harm in moving it to the installCheck phase.
Relates to #143681.
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 via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

This bit:
let
  riscvPkgs = import ../../../.. { crossSystem = lib.systems.examples.riscv64-embedded; };
in
  # ...

Breaks completely in pure evaluation mode, because it doesn't pass localSystem and builtins.currentSystem is unavailable, rendering the spike package unusable for, e.g., flakes users unless --impure is turned on.
Any idea on how we should be fixing this? Depending on pkgsCross.riscv64-embedded.{riscv-pk,hello} is an idea, but this is the first time I've ever encountered something like this.


Scheduler does not execute job when provided with UTC Date information.

I have the need of executing a job at certain times, and I use UTC Dates to keep track of them. I push jobs on the scheduler using the following code:
setScheduledChange(timestamp + (timelimit * 1000));	 function setScheduledChange(date{ 	schedule.scheduleJob(date,function(){ 		//something happens here 	}); }
This means I'm executing the job at timestamp + timelimit seconds. Because in your wiki you schedule Date using the Date constructor, I assumed the scheduler alots time according to the UTC Date. This does not happen. Am I doing something wrong?

I'm not sure UTC dates (milliseconds I assume) are supported. @tejasmanohar ?
Adding support for them shoudn't be that hard.

Very easy. I'll take care of this :)

@tejasmanohar don't worry. See https://github.com/tejasmanohar/node-schedule/pull/181

Functionality added in commit https://github.com/tejasmanohar/node-schedule/commit/14a1d915faf04917cced3108e490c030210c8d85


feat: errutil.Merge and errutil.Reduce

I started thinking just on Merge and an easy way to deal with slices of errors, where we accumulate a bunch of errors and want to merge all them together or return nil if no error happened, as easily as possible. But one thing that annoys me is how we usually hardcode the formatting (we also do it on chain), but it is hard to come up with something that is flexible on formatting that is not more verbose, like having error list handlers, chain handlers, objects, etc. Wanted to keep everything as simple functions operating on the core error type. The less terrible way I could imagine is the errutil.Reduce idea, because it seems to be what we are doing with the errors on merge (reducing a set to a single value, accumulating..in a way). So we have a basic Merge that is opinionated on how to concatenate the errors but Reduce could be used to do it in a different way (and Reduce is the building block of Merge).
Not sure the idea is good, just the first one I had to keep things reasonably simple and non-intrusive (no need to use special types, just Go's error). The reduce implementation is quite trivial but maybe inneficient on its use of recursion, but that can be changed later, I wanted to focus on the published API itself, if it makes sense or not.

@i4ki Im on the fence if errutil.Reduce should automatically filter nil errors inside slice before calling the reduce function...it does seem that we will always want that, like any reduction function will need to filter for nil anyway....but I was not sure..so I was more conservative for now. WDYT ? (or maybe the idea itself is dumb, in that case disregard =P).

Im on the fence if errutil.Reduce should automatically filter nil errors inside slice before calling the reduce function...it does seem that we will always want that

yeah good question. I agree that this should be the most common use case.
The other option would be for cases like this?
execution report: ok, timeout, ok, ok, file not found, network unreachable, ok, ok, ok

if so... well I think optimizing for the most common use cases makes more sense right now.

Im on the fence if errutil.Reduce should automatically filter nil errors inside slice before calling the reduce function...it does seem that we will always want that

yeah good question. I agree that this should be the most common use case.
The other option would be for cases like this?
execution report: ok, timeout, ok, ok, file not found, network unreachable, ok, ok, ok

if so... well I think optimizing for the most common use cases makes more sense right now. I bet no one would ever ask for this kind of behavior (now the universe will kick my ass haha).

hmm yeah, I was being very generic/flexible but I think we will end in a position where we always need to filter nils again and again... on the other hand you did provide a good example...on your example a hacky way would be to replace the nils with an error.New("ok") before reduction/merging 😆 .
I will cook this up a little on my head...but I'm prone to filtering...for a VERY generic reduction function we can just use go >= 1.18 and use type parameters (would not be surprised if this is added on Go stdlib at some point), so this one would be less flexible but more useful for default use cases.


[Modern] - User not able to edit own details unless admin

Describe the bug
Users aren't able to access their own account information
To Reproduce
Create a user with any permissions apart from admin
Sign in as user and try to access account using button at bottom right of LH menu.
Error - 'User access denied - SecurityException'
Expected behavior
Users should be able to access own information as per old traccar ui
Screenshots

This is actually not an issue with the web app. It's a change on the backend. Here's the fix https://github.com/traccar/traccar/commit/69d45b4429be70ce079b51200f6baefeb3873220.


Reject crates.io uploads which declare a feature named no_std

Since Cargo features are additive, it is always better to expose a default-enabled std feature instead.
Thanks to @cmr for the original idea, and @steveklabnik for suggesting that I write an RFC!
 But sorry, this strikes me as a very ad-hoc counter-measure.
Also, as the creator of spin_no_std, I do regret using a name with bad implications, but since it only affects implementation not interface, there is no additivity issue either way.

We could perhaps disallow negating feature=... in cfgs on crate-public items. This would solve the problem in its entirety.

Noooooooooo! That's the only way to conditionally change your API based on the feature set available. You need to know if you are "std" or "not std".

@Ericson2314 I was going to say that would rule out patterns like
#[cfg(not(feature = "fast_foo"))]
pub fn foo() { ... }

#[cfg(feature = "fast_foo")]
pub fn foo() { ... }

but we can work around that:
pub fn foo() {
    foo_impl()
}

#[cfg(not(feature = "fast_foo"))] fn foo_impl() { ... }
#[cfg(feature = "fast_foo")] fn foo_impl() { ... }

Not sure how we can preserve backwards compatibility though. Maybe have it as a warn-by-default lint?

@cmr Is there a case where going from "not std" to "std" in fact changes or removes an API? I think that's what @Ericson2314 is trying to get at: that enabling a feature should always add something.
And if it's implemented as a lint, then it can always be overridden.

@lfairy for example, serde. Serde will change things to not use String/Vec if those aren't available, and will sometimes instead use &'static str.

(Full disclosure: I implemented that)

In general, my initial thought here is that this is

a big thing to the ecosystem
kind of a footgun

So that said, in general, I am in favor of this kind of thing. I wouldn't want to suggest this for everything, but no-std as a feature is really, really important, and so might merit as special treatment as we did for *.

@cmr I find this idea very interesting; I didn't know that crates did this

@ifairy Ah good catch. I think your impl work around is better style anyways---helps catch those two signatures accidentally falling out of sync.

I am confused as to why it is worth going through the effort of making a change that will affect four thousandths of one percent of crates. It also seems pretty dubious to do this by blacklisting exactly one feature name.

I few things from talking on IRC:

The "additivity" rule is really a contravariance rule that
∀ fa, fb: Set<feature>. fa ⊂ fb ⇒ interface(crate-with(fa)) >: interface(crate-with(fb))

or, imperatively in English, adding a feature always makes the crate's interface a subtype of what it was before.

My proposal to disallow negation is sound, and I think complete for width subtyping of the crate's interface, i.e. subtyping from new items. So if you want to use features to extend an API with new items, my rule will certainly stop you from messing up, but also I think never block you by mistake provided you jump through hoops of @ifairy's impl trick.

Depth subtyping ,i.e., a preexisting item is given a more-refined type with additional features, is harder to verify, however. This is both because multiple variants of a crate need to be compiled through type checking, not just name resolution, and worse, because some subtyping relationships are quite hard to prove.

For example, @cmr's examct example of https://github.com/serde-rs/serde/blob/master/serde/src/ser/mod.rs#L29 might be OK if we can show that Into<String> is super-bound of Into<&'static str> via an impl like impl<T, U: Into<T>, V: Into<U>> into<T> for V. But  I don't think that impl can be written anyways right now.

A broader thing than blacklisting one common feature name would be a crater-like service that compiles new crates with all possible feature combinations, to find out whether they really are additive.

@durka that's basically what I'm proposing, except it needs to be a smart tool deeply leveraging incremental compilation to not be the most crazily exponential, crazily big constant factors, expensive thing.

Some crates are not designed to be used with all possible feature combinations. Every optional dependency is implicitly a "feature" name. I document which features are intended to be enabled, can't support a random pick. (However additivity is of course obeyed.)

@bluss that's valid, but actually doesn't get one out of a positivity requirement. I've long wanted Cargo packages giving a boolean expression of their features that must always be true---this is the best way to declare up front what feature combinations make sense.

Every optional dependency is implicitly a "feature" name.

Are you saying Cargo automatically turns optional dependencies into features, or that users in practice will make sure every optional dependency is covered by at least one feature?

Every optional dependency (xyz) is something you can use as --feature = "xyz", so for cargo they are the same thing.

@Ericson2314

it needs to be a smart tool deeply leveraging incremental compilation

Well, maybe it doesn't have to be a crater service. It could be part of cargo publish.
@bluss

Some crates are not designed to be used with all possible feature combinations.

This is the reality, but is it at odds with the intended purpose of features? Do your crates where a random pick wouldn't work fall into categories of missing functionality that could be addressed by a more flexible feature system (e.g. rust-lang/cargo#2980, etc)?

Btw for intuition on positivity and restricted feature sets, Take a look at this . When following edges upword, the set of features (1s, not 0s) becomes large, and the interface also becomes richer (subtype). Deleting combinations removes nodes and edges from the diagram, but the same positivity restriction still applies to traversing the remaining edges.

Sounds good. I was mainly thinking of something like for example feature "accel" depends on crates "simd", "blas-sys", and "foo"; The intended usage is to enable the feature "accel" or not, not to pick either of the optional deps manually. In the regular case, all the internal code will simply cfg on the main feature variable, but since the other feature combinations are not supported, they may not ever have been compile-tested.
Aha! But.. it is a goal for me to ensure a crate compiles with all supported features enabled or disabled. It's not a goal to ensure a crate compiles with nonsensical feature picks. (For example if I pick just features = ["blas-sys", "foo"], what do I get? The documented additions to the crate go off of "accel", so most likely you get nothing.)

So, the fact that you have to specify the supported feature combinations in English in the readme means that Cargo.toml isn't as expressive as we need. So that's why I said we likely need some more declarative possibilities before my broader check-everything idea could work. But we've strayed a bit from the title of this issue now.

While we're derailing, I'd like to point out the checking feature additivity and checking semver compliance are all but identical processes ;).

Does one really have to forbid uploads of crates? Wouldn't it be less drastic to make cargo emit a warning at build time?

@est31 As far as I know, there are no valid reasons to have a no_std feature flag. And we have banned wildcard dependencies already, so we have precedent for enforcing rules this way.

@lfairy

Forbidding crate uploads is quite a big caliber. Its like if rust errored if you declared a variable but not used it, its not appropriate.

The check won't help users who don't upload to crates.io. If they upload their crates to github and use them as git dependencies, they won't even notice. You want to prevent all cargo users from using no_std, no?

Banning wildcard deps is a different thing. Wildcard deps make sense in the local setup, and don't make sense on crates.io, while no_std doesn't make sense in both setups.

Its like if rust errored if you declared a variable but not used it, its not appropriate.

No, it isn't. Downstream programs will break because of mistakes like this.

Forbidding crate uploads is quite a big caliber.

Can you elaborate on how this change can be considered "big"? As it stands, this change would affect exactly 21 crates, out of over 7000.

Its like if rust errored if you declared a variable but not used it, its not appropriate.

Can you please explain how that example relates to the original proposal? I don't see what a check on publish has to do with a check that stops code from building at all.

The check won't help users who don't upload to crates.io. If they upload their crates to github and use them as git dependencies, they won't even notice. You want to prevent all cargo users from using no_std, no?

That would justify adding an additional warning to cargo build, not scrapping the proposal altogether.

Can you elaborate on how this change can be considered "big"?

Its "big" because if you want to publish an affected crate, you will never ever be allowed to do so. That hopefully also answers your other question.

That would justify adding an additional warning to cargo build, not scrapping the proposal altogether.

Sorry, I might have expressed myself wrongly. I never proposed to scrape this proposal. In fact, I would quite like a check! However, I think the proper place should be such a lint on cargo build, and not on the crates.io server. That is my entire criticism of this RFC.

I hope we can all agree that there should be a check on cargo build. It is better if you have a warning/error on cargo build instead of having it later in the release process.
With such a preliminary check, you can even ask the question of what the additional advantage of an additional check for uploads to crates.io is.
I just have the general feeling that adding checks to crates.io uploads is a thing to avoid, because the crates should be owned by their uploaders, and not by whoever controls crates.io. I mean github also allows you to check binaries into git, and do all your commit messages in past tense if you want to, even if both are probably things you shouldn't do.

@est31 the point of this is to make sure that build plans are resolved correctly, which means we need any crates.io crate Cargo might download to be well-behaved.
The lest draconian way to prevent people from getting bit by poorly-packaged software is to blacklist (by default) any crate+version in violation and warn the author. We'll probably need this anyways for crates that are already up there.

There's a general problem with regards to lints and #[cfg(..)]: The former don't see the latter – all conditional compilation is done before even an EarlyLintPass visits the AST. This is quite suboptimal for other reasons, too, but it would also preclude building this as a lint unless we change the order of operations (and possibly pessimize compilation) at least as a special case.
Apart from that, I very much support the idea of requiring additivity at the public interface level. However, allowing to #[cfg(not(X))] fn item(..) if there is a #[cfg(X)] fn item(..) seems to me a more agreeable solution. I would also allow type declarations to conditionally result in different types (e.g. core::foo::Foo instead of std::foo::Foo) as long as both variants declare the type at all.

@llogiq I can think of a possible solution to that problem:

Have the expander wrap every non-matching #[cfg] in a special "removed" node, instead of deleting the item outright

Don't strip #[cfg] attributes from the expanded code, so that further passes can inspect them

True to their name, every part of the compiler will ignore the "removed" nodes, except for the #[cfg]-checker lint

Adding a whole new node type to the AST just for a single lint seems a bit overkill, though.

@Ericson2314

the point of this is to make sure that build plans are resolved correctly, which means we need any crates.io crate Cargo might download to be well-behaved.

I agree with the first part (as I've said above), but think the measure is too drastic, as I've said above as well. Auto-yanking crates would not make sense to the crate owners themselves, as they won't be able to use their crates. Yanking existing crates is (correct me if I'm wrong) without example. I mean, all the broken pre-1.0 crates are still up there, no?

Mhh, I think I want to do different things than arguing about this (quite small) change. Please, don't expect replies from me on this thread!

@retep998 do you use negation? Checking for no negation is linear in the number of cfgs. If you do use negation, only need to check for pairings as @ifairy describes. There's a bunch of wonderful tricks to make this tractable!

@Ericson2314 #[cfg] syntax allows any CNF/DNF expression, so you have a nice SAT problem.

@Ericson2314 What if I use a build script that examines the specified features to emit new cfg flags and have code conditional on those cfgs? For winapi I'll be doing that because sometimes headers depend on each other recursively and cargo features can't have any dependency cycles, so I have to implement header dependencies in the build script.

What if I use a build script that examines the specified features to emit new cfg flags and have code conditional on those cfgs?

Oh my! 😁

For winapi I'll be doing that because sometimes headers depend on each other recursively and cargo features can't have any dependency cycles

This too would be solved with my proposal for a boolean expression on features that must be true.

From the RFC:

In particular, a crate may provide a no_std feature, which restricts its API so that it works with just the core library. But because features can only be enabled, not disabled, any consumer which enables no_std here will also enable it for every other user of this crate. Most of the time, this is not what the user wants to do.

I assume the first occurrence of the word user in this description is intended to be consumer, i.e. another create/dependency which depends on the same crate, as opposed to a different human?
Secondly, if I'm trying to turn off a reliance on std (or remove a dependency on openssl, say) from one crate, wouldn't I want it to stay off regardless of what other crates depend on it? That is, what evidence do we have that "most of the time, this is not what the user wants to do" is true? (perhaps I'm misunderstanding the problem here?)

We could perhaps disallow negating feature=... in cfgs on crate-public items. This would solve the problem in its entirety.

@Ericson2314 , doesn't disallowing negation in cfgs break using alternate signatures/syntax for an API? For example, I recently raised a PR which used specialization only if a particular feature was enabled (so the code could run fast on nightly and but still work on stable), which used cfg(not(..)) to work around default not being a valid keyword in stable Rust.

This RFC has stalled out, without feedback from those involved in Cargo/crates.io work directly. @alexcrichton, @carols10cents, @wycats: do any of you have thoughts?

I feel like @sfackler has articulated my feelings on this RFC as well.
With just a simple grep around the index I found a total of 373 candidates for "maybe this RFC would help", many of which are "no_std" but not all.
Overall I personally feel that we need more aggressive documentation about features in Cargo. Strictly mentioning that features must be additive so unioning them together works. Furthermore we can call out antipatterns, such as "no_std".
I feel that taking the identifier "no_std" and warning about it, while perhaps useful in the short term, is better done through specific author outreach. These patterns came from somewhere, and 99% of the time it's just copied from someone else's pattern. If we "fix" the sources it will likely propagate over time.

I don't fully understand all the implications of features or Hasse diagrams, but from what I do understand of this RFC, I think I agree with @alexcrichton that it would be more appropriate to improve documentation in this area, with examples of problematic features, and outreach to particular crate authors.

@carols10cents BTW, have you used RFC bot yet? There's some basic docs here, and anyone on the tagged team can propose a "motion to FCP" at any point. (If you have questions about when that's appropriate, feel free to ping me on IRC to discuss.)

@rfcbot fcp close

@rfcbot reviewed

@rfcbot reviewed

@rfcbot reviewed

Looks like serde has a completely broken no_std feature... https://github.com/serde-rs/serde/issues/918#issue-227331308

@whitequark  it's not? It's working as intended; it's a defaulted "std" feature, which is how no_std support should be done.

We have a std feature (not a no_std feature) that is working as intended.

OK, I misunderstood, sorry about that.

Sheesh right at the heart of the ecosystem.
The evidence is stark. Semver compatability, feature additivity, and portability all are simple too subtle, tedious, yet exceedingly important to ask the user to police themselves. The same infrastructure can be used to enforce all three.

Sheesh right at the heart of the ecosystem.

It's not, serde did the right thing here, there was a misunderstanding 😄

Oops there goes my soapbox 😂

Not quite. Serde has a positive std feature, but it's still non-additive, so incurs the same problems as a negative no-std feature would.

Again, this is working as intended. If anyone would like to keep discussing Serde's error handling please keep that on Serde's issue tracker or #serde IRC.

I don't see what this has to do with Serde in particular. Non-additive features exist and they work counterintuitively. Whether or not you intended your particular feature to work that way is beside the point.

Ok looks like not much new discussion happned during FCP, so I'm going to close.

Ah and of course thanks regardless for the RFC @lfairy!


how to get the feature of one image?

Hi,
I tried to use your model to extract feature of any image, it works and I get the feature;
however, the feature value is related to camera id and view, but I don't know the camera id and view, can we directly get the feature?
can I get the feature of any image?
thanks.

no question any more. why I can't delete  it????

Hi,
can you share the code of extract feature of any image?


Don't fail the runner through PropertyHelper fail

I mistakenly failed the TestHelper's runner through the PropertyHelper, which is inconsistent with the other methods.

And which would fail the property without starting the shrinking process and such.

you need to make fail a ref method.

sorry, fixed


Please verify that the package.json has a valid "main" entry

has anyone found a way to resolve this? I ran into this after installing dukpt

@xyxdaily @Alexximn Are you both using this package on Windows. I haven't tested this package on windows. Unfortunately I won't be able to look into this at the moment, but I'd always welcome a PR if you could fix it :)


Get All Chat Emoticons API Endpoint

Feature Request

Currently, there is no way to get all chat emoticons from the Kraken/Chat/ChatAPI helpers. However, it is a supported endpoint from Twitch itself:
https://dev.twitch.tv/docs/v5/reference/chat#get-all-chat-emoticons
I have already made code changes related to this feature request and can open a PR if this feature is approved - I'm simply trying to follow the direction of the PR/Issue template and open an issue first

I misunderstood this API, and realized that it's a now-removed V5 API. My bad, closing


JWT_SECRET_KEY exception

Raises an exception when JWT_SECRET_KEY is not defined in Flask app.config
If this key is not defined, functions like create_access_token give unexpected errors, for example. TypeError: String is expected.

LGTM, but how about extract secret key from flask?

LGTM, but how about extract secret key from flask?

What purpose would the extraction serve though? The PR changes would ensure that the app will not get initialized if the secret key is not in app.config

LGTM, but how about extract secret key from flask?

What purpose would the extraction serve though? The PR changes would ensure that the app will not get initialized if the secret key is not in app.config

I means find JWT_SECRET_KEY -> find SECRET_KEY -> raise exception if both are not exist.
flask describes app.config.secret_key as "A secret key that will be used for securely signing the session cookie and can be used for any other security related needs by extensions or your application."

Ok, I misunderstood earlier.
Added with the changes:
IF "JWT_SECRET_KEY" does not exist THEN app.config["SECRET_KEY"] will be picked as the default value.
Else
exception

Also, this has yet to be merged. :)

LGTM, but how about extract secret key from flask?

What purpose would the extraction serve though? The PR changes would ensure that the app will not get initialized if the secret key is not in app.config

This is just recommendation :)
I means find JWT_SECRET_KEY -> find SECRET_KEY -> raise exception if both are not exist.
flask describes app.config.secret_key as "A secret key that will be used for securely signing the session cookie and can be used for any other security related needs by extensions or your application."
p.s. flask-jwt-extended also use SECRET_KEY if JWT_SECRET_KEY not exists.

I made the changes. This is approved but not merged.


aider-chat: 0.59.0 -> 0.60.0

Things done
just a simple update
I'm in the process of using this more. If all goes well in a couple of months, I'll be happy to add myself as a maintainer.

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 350691

x86_64-linux

:x: 3 packages failed to build:

aider-chat
aider-chat.dist
vimPlugins.aider-nvim

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 350691

x86_64-linux

:white_check_mark: 3 packages built:

aider-chat
aider-chat.dist
vimPlugins.aider-nvim


feat: store cache-state data in database

Closes #115
Will require everybody to delete database and run precache command.

@AuHau is this always going to be the case to initial setup to run Precache and then Start?

Well, not exactly sure what you mean. If you are asking about the comment I put to the description it is meant as a reminder to tell everybody to make this (eq. delete DB and precache) after they pull these changes, otherwise they might get weird behavior from Cache...

Well, not exactly sure what you mean. If you are asking about the comment I put to the description it is meant as a reminder to tell everybody to make this (eq. delete DB and precache) after they pull these changes, otherwise they might get weird behavior from Cache...

Adam what I meant is that started everything from scratch and couldnt run Start as before. It forced me to execute Precache and then Start as two separate steps to run the Cache.


fix awkward wording

There is awkward wording in the docs for SQL database managed instance VNet configuration.

@derekmorr : Thanks for your contribution! The author, @srdan-bozovic-msft, has been notified to review your proposed change.

agree with the proposed change


roc-toolkit: bump scons

Motivation for this change
Scons 3 uses python2 by default on nix, bumping scons removes the python2 dependency.
#148779
Things done
Updated the scons version and added two patches from upstream.

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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.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.

Result of nixpkgs-review pr 156474 run on aarch64-darwin 1

1 package built:

roc-toolkit


Some changes to the resultdb

We are planning to do some changes and to send a pull request afterwards but we would like to hear your opinion first.

We would like to let the user specify the primary key used for saving to the resultdb because taskid might not be a good choice (we are having some duplicates because the same item comes from different tasks). The idea is to subclass BaseHandler and add a method which computes a primary key for every item using the fields specified by the spider (I guess we would need to override on_result). An user would use it like this:

class MySpider(BaseHandlerWithPrimaryKey):
      PRIMARY_KEY = [ 'name', 'age' ]

The ResultWorker will then use the primary key which was calculated (if present) instead of the taskid to save the item to the resultdb.
2. We would like to add two more fields to the resultdb; created will store the datetime when a result was first scraped (this is one of the reasons we need a custom primary key) and modified will store the datetime when a result was last updated (i.e. one of its fields changed value or there is a new field). Since we are adding these two fields it would make sense to add another column which stores the lastcrawltime of the corresponding task so that all the information are stored in the same table. We would also change the result page so that it exposes this new information.
What do you think? Hints/suggestions?

def get_taskid(self, task) is what you can override to calculate a taskid by your needs. https://github.com/binux/pyspider/blob/master/pyspider/libs/base_handler.py#L319. Or you can just specify a taskid via self.crawl(url, taskid="any_taskid")

Resultdb is designed for data preview, it's not recommended to use resultdb directly in product environment. To connect with other components outside pyspider system, it's better to design a new database for product and override the result worker storing data to the database for product not resultdb.

Currently, there is a field updatetime can be used as modified.

Unfortunately this is not enough: we are scraping many websites where the information from a single item is contained in different places (we already have overridden get_taskid to include form data as well by the way). The key point is that the taskid and the primary key for an item are two different things (semantically), and sometimes it's even possible that the item PK is not known until we fetch and parse a webpage, and therefore should be handled on task completion, and not on task startup

We are only using it as a preview, indeed we transfer the data to another temporary database prior to our computations. We just need pyspider to keep track of these datetimes

In my understanding, PK is a customized logic to deduplicate results? It might better calculated and stored in result dict?
def detail_page(self, response):
    result = {
        "name": response.doc(selector),
        "age": response.doc(selecto2),
    }

   result["PK"] = calculate_pk(result["name"], result["age"])

pyspider use taskid to relate same task in taskdb and resultdb. If PK is added, how do it affect pyspider?

ok, I agree createtime is useful in some case. As for modified, is updatetime enough? But adding a new column might need database migration. Any idea?

We don't really know, that's why we ask. But we think it is needed, consider the case when many items can be scraped from a single page, they will all come from the same task and therefore have the same taskid no matter how it is build; thus they will be grouped together despite being actually different. It would definitely make sense to decouple taskids to item ids.

This could be a problem. Our idea is to update ResultDB._create_project to include the new columns with a default value so that BaseDB._replace does not complain about missing values. Then a new class extending ResultWorker will be created which will take care of handling created, modified and the primary key issue of (1). This new result worker will also take care of creating these columns in case they do not exists in the table; this ensures portability for both old users and new users as they will have to specify the new result worker class at startup.

For the multiple results from one single task case, my solution is using a "fake" task by adding "#item-id" to it's url. send_message has a parameter url to disguise a task. Here is a sample: http://demo.pyspider.org/debug/yongle .
Another solution is just yield the items one by one, the item will be sended via message queue and received by result worker. Although they will be overwritten in resultdb, but by writing a customized result worker, how to handle the item is up to the user.
I'm not so clear about how PK in resultdb works. e.g. task_a produce item_a, item_b the first time, and item_b, item_c the second time. Will item_a be deleted? If not, how to expand the result item_a in /task/project:task_a page, especially when script had changed?

Regardless of issue(1). There are 3 ways to do this.

Auto detect and alter the table when connection.
Using default value and keep the fields un-touched.
Adding a migration tool, asking user to migrate while upgrade to new version.


Update chaos-studio-fault-providers.md

TargetType for Cosmos DB has a space that should be removed.

@prasha-microsoft
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


make docker-push "succeeds" if it fails to talk to the registry

Describe the bug
make docker-push exits with a 0 exit-code even if docker push fails to push the images.
To Reproduce
Steps to reproduce the behavior:

DOCKER_REGISTRY=bogus.com:1234 make docker-push
Observe a single line on stderr, then Make exiting successfully:

$ DOCKER_REGISTRY=localhost:31000 make docker-push
Successfully tagged localhost:31000/ambassador:lukeshu-backtrace-04cc91fa-dirty
PUSH localhost:31000/ambassador:lukeshu-backtrace-04cc91fa-dirty
.Get http://localhost:31000/v2/: dial tcp [::1]:31000: connect: connection refused

$ echo $?
0

Expected behavior
I expected make to exit with a non-zero exit code, and for any targets that depend on docker-push to not be built.
Versions (please complete the following information):

Ambassador: 0.76.0<PHONE_NUMBER>de6dfff223812e7a77ad9dbb7cf5fd)

To be fair, there is little error handling in the Makefile today. Simple workaround is to just run docker push manually. In any case, will put up a quick PR for this specific issue.

Wow, I didn't expect anyone other than me to work on this issue :)
I suspect all that's needed is to say SHELL = bash -o pipefail, but it's possible that this causes other issues.


Make AuthHandler call Teardown on unhandled exceptions.

#82 - AuthHandler needs to clean up after itself even for unhandled exceptions. This is especially true if the ErrorHandler starts re-executing requests.
@badriL

@Praburaj @muratg

Looks good to me :shipit:


pipeline一段时间不使用，再用的时候就会响应很多的None

pipeline一段时间不使用，再用的时候就会响应很多的None

https://translate.google.com/#auto/en/段时间不使用，再用的时候就会响应很多的

Translates into English:

The segment time is not used, and it will respond a lot when used again.

@hmyixiu would you care to explain a little more what is the problem? :)

Hello holmboe，I am a beginner，thank you very much
when I use StrictRedisCluster to get a pipeline.
eg:
conn = StrictRedisCluster
conn.pipeline()
pipeline.hmget()
pipeline.hmget()
pipeline.hmget()
....(more commands)
result_list = conn.execute()
usually it is no problem.
but when I don't use it，about after 5 minute，
then I use it again，result_list will have some elements are None

@hmyixiu Are you saying that you are creating a pipeline object, runs execute on that object, then waits for a few minutes, then try to run execute on that object a second time??


Permute points dimensions

Analogous to image permutation
Closes #302

I decided to push https://github.com/imagej/napari-imagej/commit/1cd0bf9701da262b0d815b26f0a6de5f19615329 to a separate branch point-permutations-gui, which will allow us to merge this behavior and benefit in SciJava scripts


Netlify build after hydrogen remix upgrade not rendering site

What is the location of your example repository?
private
What version of Hydrogen are you using?
2023.1.4
What version of Remix are you using?
1.13.0
Steps to Reproduce
Upgrade to new version of Hydrogen using Remix per the upgrade document steps.
Expected Behavior
Pages should load locally and on netlify preview after build.
Using latest
"@netlify/hydrogen-platform": "1.1.4",
Actual Behavior
Site works locally after upgrade but on netlify all pages are not found.

Moving to https://github.com/netlify/hydrogen-platform


MB-11600 Block incomplete PPMs on frontend

Jira ticket for this change
Summary

This PR blocks submission on the move/home page if any ppm shipment is incomplete.
I removed legacy current_ppm logic on this page and in the unit tests

ENGINEERING NOTES

I noticed that mto_shipment.ppmShipment.advancedRequested isn't being automatically set to null on the front and instead that field is missing completely. Our existing isPPMComplete utility function was checking for a null value and since the field wasn't present (and not set to null) that check was failing. I've added an additional check in isPPMComplete to check for undefined as a temp fix and will look into why advanceRequested isn't being set to null

DESIGN NOTES

I realize when the PPM is incomplete the step number should show instead of a check mark. I will add this in when I'm back
reference:

Other Todos

fix unit test for the home page
add test for incomplete ppms for the home page
update the step (3) to display instead of checkmark when there's ppm shipment that's incomplete
look into why the frontend isn't setting advanceRequested to null initially

Setup to Run Your Code

💻 You will need to use three separate terminals to test this locally.
Terminal 1
Start the Storybook locally.
make storybook

Terminal 2
Start the UI locally.
make client_run

Terminal 3
Start the Go server locally.
make server_run

Additional steps

Access the
Login as a

Frontend

[ ] User facing changes have been reviewed by design.
[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] There are no new console errors in the browser devtools
[ ] There are no new console errors in the test output
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.

Screenshots

Messages

:book:
:link: MB-11600

  Generated by :no_entry_sign: dangerJS against e24b332827774fbe82e51d28b5b5d12999d5b796

* I noticed that `mto_shipment.ppmShipment.advancedRequested` isn't being automatically set to `null` on the front and instead that field is missing completely. Our existing `isPPMComplete` utility function was checking for a null value and since the field wasn't present (and not set to null) that check was failing. I've added an additional check in `isPPMComplete` to check for `undefined` as a temp fix and will look into why `advanceRequested` isn't being set to null

thought: I think it's because we didn't set x-omitempty to false for advance and advanceRequested: https://github.com/transcom/mymove/blob/e24b332827774fbe82e51d28b5b5d12999d5b796/swagger-def/internal.yaml#L2540-L2550
suggestion (non-blocking): Since we do set it for other fields on the PPMShipment and it's affecting this PR, can you update it as part of this PR?

This needs tweaking on the mobile view — the incomplete label should not move the delete and edit links off the screen. Label can move left, closer to PPM.

@ronaktruss is this fixed in your PR? otherwise I can address it here


CD Release notes 1.49.5

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66a3baf2e6387a21db9952a4--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66a748ac975f4c07f3977ad1--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66b2fd232f38c45feaf5ba22--harness-developer.netlify.app


the toggle option in video settings doesnt seem to work.

its probably an incompatibility with reese's sodium options or sodium extra

i'll check it later

tested, i think the problem is caused by Sodium Extra as it modify the options, I'll fix it later

Fixed in 1.1.2


Is it possible to start with a specified slide?

Is it possible to start with a specified slide? For example, I have a gallery of thumb images, clicking on one of them loads a page with the same images, but using different layout, in this case 'Superslides'.
I want to start Superslides with a image user clicked.
Thanks.

@keeprock - did you ever figure this out? Thanks!


0.15

Work in progress! 🙈🙈
Preview: https://deploy-preview-90--colyseus-docs.netlify.app/colyseus/migrating/0.15/

Missing documentation updates:

https://github.com/colyseus/colyseus/pull/459
https://github.com/colyseus/colyseus/pull/453
https://github.com/colyseus/colyseus/issues/354
https://github.com/colyseus/colyseus/pull/454

wen?

cn version will be pulled later today.

cn version will be pulled later today.

maybe tommorrow...

hi @CocosGames, we've made a few changes to the sidebar, e.g. added a "Dev Mode" page, and a "More" section, when you have some time could you please review if changes are necessary for the translated pages?

You got it.👌

@CocosGames this pull-request shouldn't have been merged yet. I've just reverted the PR to avoid docs for 0.15 going live. We'll need to figure out how to re-open the PR as we had before now.

Sorry about that, I'll resubmit a pr we need.


Describe issues with memory

@maxaalexeeva, the documentation has been updated based on your experience and feedback.  If you can think of anything to add, you are welcome to do so.
I still have to address the null ScienceParser.


[5.5] Pipeline: Function name should be a string (AuthManager)

Laravel Version: 5.5.4
PHP Version: 7.1.1
Database Driver & Version: MySQL

Description:
Currently trying to upgrade from Laravel 5.4 to 5.5. We are using the Cloudcreativity Laravel JSON package to run a json api with laravel. Also we have our own auth provider to validate JWT tokens.
As soon as we upgrade we get the error "Function name should be a string". After searching through the code and vendor dir, i've a found a solution:
Adding following code to the Laravel AuthManager solved the problem:
public function handle($request, Closure $next) {
     return $next($request);
}

The question is: What tries to call AuthManager::handle? I've found nothing.

This sounds like you're attempting to use the middleware alias "auth", but havn't registered it or it just resolves to the Auth facade, which is backed by AuthManager.

Thanks, this actually solved it. The auth middleware wasn't registered properly.

Thank you for writing this issue @saiik , it prevented me from another hour of debugging ;)

How to register auth Middleware properly?

How to register auth Middleware properly?

@razigohar If you're using Lumen, you'll need to uncomment the auth middleware being registered at https://github.com/laravel/lumen/blob/master/bootstrap/app.php#L66


🐛 Bug: Setup script isn't updating .all-contributorsrc contents

Bug Report Checklist

[X] I have tried restarting my IDE and the issue persists.
[X] I have pulled the latest main branch of the repository.
[X] I have searched for related issues and found none that matched my issue.

Expected
From https://github.com/JoshuaKGoldberg/template-typescript-node-package/issues/147#issuecomment-1364485885: after running pnpm run setup, .all-contributorsrc should have its contents updated to the new projectName, projectOwner, etc.
Actual
The contributors list is reduced to just one (me!), but the projectName and projectOwner are still the same as before. Those properties should be updated to the repository and owner values already used in the setup script.
Additional Info
No response

Merging with #161: there are a lot of files that aren't updated to the new name. 😢


Terminal Processes Terminated Exit Code 5

We have written the needed daAll folders I have, if I open any of them and click Terminal and then new, it starts a new terminal for me but then as soon as it appears it disappears stating "The terminal process terminated with exit code: 5". I have been working in it fine for weeks.ta into your clipboard because it was too large to send. Please paste.

This means that your shell exited with a code of 5. You have likely configured something wrong in your system or VS Code.

Thank you all, I did discover my company blocked my access to Powershell...issue resolved.


Multilayer map - Feature to toggle between different layers

Description
Is there a feature to toggle between different layers in a deck.gl multiple layer map once it is published in a dashboard?
For example, if a map has 3 layers (scatterplot, line map, arc map) , I want to enable only scatterplot. A toggle button to change the layers.

@Geethanjali11 thanks for suggesting.
from product standpoint this is almost a  must have, however, I don't think we can get to it anytime soon.
community contribution is always welcome!


Change property dimiss to dismiss

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: CONTRIBUTING.md#commit
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[x] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

I think dimiss is likely a typo and it is more natural to call this property dismiss.
Issue Number: N/A
What is the new behavior?
Property name is renamed to dismiss.
Does this PR introduce a breaking change?
[ x] Yes
[ ] No

Other information
BREAKING CHANGE: property dimiss is renamed to dismiss on help component and may cause compilation or runtime errors in clients that depend on the old name.

Thanks. The breaking change should be in the commit message based on https://github.com/ngneat/hotkeys/blob/master/CONTRIBUTING.md#-commit-message-guidelines

Thanks. The breaking change should be in the commit message based on https://github.com/ngneat/hotkeys/blob/master/CONTRIBUTING.md#-commit-message-guidelines

Updated the commit message and the link to the sample commits in CONTRIBUTING.md.

@NetanelBasal is there anything else that's needed for this?

@rars ci failed

@rars ci failed

Ok, think I've pushed a fix for that. Please try again.


[Bug report] yarn install __dirname the path is wrong

Description
npm correct

yarn wrong

Reproduction
https://github.com/qqlcx5/vuepress-next/tree/master/.github/workflows
Used Package Manager
yarn
System Info
Environment Info:

  System:
    OS: macOS 13.0
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  Binaries:
    Node: 14.20.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 8.18.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 105.0.5195.52
    Edge: Not Found
    Firefox: Not Found
    Safari: 16.1
  npmPackages:
    @vuepress/core:  2.0.0-beta.51
    @vuepress/theme-default:  2.0.0-beta.51
    vuepress: ^2.0.0-beta.51 => 2.0.0-beta.51
  npmGlobalPackages:
    vuepress: Not Found

Related file https://github.com/qqlcx5/vuepress-next/blob/master/docs/.vuepress/config/sidebar.js
CC @meteorlxy

Is the issue still exisit?
And does the issue exisits in npm@8, pnpm @7 and yarn@2 and yarn@3?
I guess this is because we are using esbuild to handle your config file, and the import.meta object is somehow wrong under env you reported. However, I do think that it's probably not a VuePress issue, The issue probably comes from upstream.

I just tried the repo locally with yarn v1.22.19 and upgrade all deps to latest version. Everything looks good.


Update to specs 0.15.0!

I wrote a PR to do just that for https://github.com/amethyst/specs-physics, only to discover that you guys weren't updated either! I'm getting to work on a PR for this crate as well :D

#14  for reference.

It was merged! :D


Fix link rendering

Before
Reading

Source

Live Preview

After

Closes #5 with an empty commit -- this is just an inherent rendering difference between the three modes. Also #8 might have closed this already


Trim hazard data in parallel

Should be able to call gdap warp {workflow.cores} times concurrently

Reworked rules to make each output tiff a job, a.k.a. parallelism via snakemake


Update showcase.md

Hey! Thanks for the contribution. I'm generally looking for sites that showcase different aspects of Quartz. I feel like there are enough similar sites on the showcase so I'm going to close this PR for the sake of maintaining a high signal-to-noise ratio


#740 #1580 Support multiple authentication schemes in one route

Closes #1580 #740

#1580
#740

Proposed Changes

opportunity to have the several authentication provider keys in Routes what allows to authenticate requests via different providers

@raman-m,
That is a new PR. Is it OK for you?

@MayorSheFF commented on Dec 28

Thank you very much!

@ggnaegi @RaynaldM @MayorSheFF
I have the concern regarding new AuthenticationProviderKeys property.
We can reuse old AuthenticationProviderKey property and as a developer I haven't update a lot of code lines.
Seems adding the new AuthenticationProviderKeys property is overhead design...
Please share your opinion!

@raman-m I'm not a fan of the language approach with delimiters. You will need a parser for that, with some risks. I would recommend keeping the variant proposed by @MayorSheFF and mark the property AuthenticationProviderKey as deprecated.

@raman-m I don't think I'm qualified to give an opinion (we don't use auth through the gateway).

@ggnaegi Good, make sense... Everybody loves its own design... Seems it is to late to change design.
But the property is not deprecated. We still consider it as primary auth key, because of backward compatibility.
But what did you mean actually?
Marking the property with [Obsolete] attribute?

@ggnaegi Good, make sense... Everybody loves its own design... Seems it is to late to change design.
But the property is not deprecated. We still consider it as primary auth key, because of backward compatibility.
But what did you mean actually?
Marking the property with [Obsolete] attribute?

Yes mark it obsolete, so we promote the new approach...

@MayorSheFF could you give me the permissions on your PR so I can finish the last steps? Thanks ggnaegi

@ggnaegi  I have done feature design. And added major required acceptance tests 👉https://github.com/ThreeMammals/Ocelot/pull/1870/commits/0f0a856b44770d6d0dbfcc5c8c31445a0d40b5b8 related to Identity Server 4.
Could you review please? And if no objections then I'm going to merge.

The build is 🟢
Ready for delivery! ✔


feat: squash Prisma migrations

I'd ignore this one and focus on
https://github.com/hypercerts-org/oso/pull/243
I'm keeping this temporarily as reference code for creating the continuous aggregates later

Deprecated. bye bye prisma


add memory-leak-test

Feature-request
Description
Add memory-leak-tests based on the memory-counter class

added new memory-leak-test-helper and memory-leak-tests for the current code-base
updated gitlab-ci-runner for multi-stage


Use fs.realpath to get actual project directory

In server/build/webpack.js: pass the cwd through fs.realpathSync in order that babel-loader can find the "pages" components when the user is in a directory junction. Without this I would receive the "you may need an appropriate loader" error on compilation (Windows 10).

That travis error is kind of strange. Can you check it @sdgluck

Not sure what's going on with this. Will close and open another, maybe the CI pipeline won't fail then.


In Prerequisites section link to Microsoft Dataverse returns a 404

In Prerequisites section link to Microsoft Dataverse returns a 404
Audience insights profiles must be stored in an Azure Data Lake Storage account that you own, or in a Microsoft Dataverse–managed data lake.
Not sure if correct link should be:
https://docs.microsoft.com/en-us/powerapps/maker/data-platform/data-platform-intro

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

ID: b2ab19a0-907c-272b-36dc-15db4e943f36
Version Independent ID: 0a875890-492d-51a6-4565-24ae6e68a383
Content: Create a link between audience insights and engagement insights - Dynamics 365 Customer Insights
Content Source: ci-docs/engagement-insights/integrate-audience-insights-engagement-insights.md
Service: customer-insights
GitHub Login: @mkisel
Microsoft Alias: mkisel

Thanks for letting me know @saviegas ! The fix is pushed and will publish shortly. Thanks!


The Expected network bandwidth (Mbps) should not be MBps in zh-cn pages

In Simplified Chinese pages, the 期望的网络带宽 (MBps) should be Mbps!
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: fe301d91-d416-fd08-af13-f84b12cee7cd
Version Independent ID: b668960b-4524-6d97-9ddf-af8beb5ef8ad
Content: Azure Linux VM sizes - General purpose
Content Source: articles/virtual-machines/linux/sizes-general.md
Service: virtual-machines-linux
GitHub Login: @jonbeck7
Microsoft Alias: jonbeck

Thanks for the feedback! We are currently investigating and will update you shortly.

@wbpluto the docs are correct.
Mbps means megabits per second. Mb is used in reference to download and upload speeds.
It takes 8 bits of data to equal 1 byte.
MBps stands for megabytes per second. MB is used in reference to file size, or the amount of data transferred.


I tried three branches (master, 2.3.1, version-2.1.3)  but all failed to resolve dependencies. Which version/branch to use?

[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building SoapUI Swagger plugin 2.1
[INFO] ------------------------------------------------------------------------
[WARNING] The POM for com.smartbear:ready-api-soapui-pro:jar:1.2.0 is missing, no dependency information available
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.352 s
[INFO] Finished at: 2016-05-29T10:24:04+03:00
[INFO] Final Memory: 8M/145M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project soapui-swagger-plugin: Could not resolve dependencies for project com.smartbear:soapui-swagger-plugin:jar:2.1: Failure to find com.smartbear:ready-api-soapui-pro:jar:1.2.0 in http://www.soapui.org/repository/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of soapUI Repository has elapsed or updates are forced -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
get this under master branch. please help :)

[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Ready! API Swagger plugin 2.3.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[WARNING] The POM for com.smartbear:swagger4j:jar:1.0-beta6 is missing, no dependency information available
[WARNING] The POM for io.swagger:swagger-inflector:jar:1.0.6-SNAPSHOT is missing, no dependency information available
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.777 s
[INFO] Finished at: 2016-05-29T10:45:58+03:00
[INFO] Final Memory: 9M/145M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project soapui-swagger-plugin: Could not resolve dependencies for project com.smartbear:soapui-swagger-plugin:jar:2.3.1-SNAPSHOT: The following artifacts could not be resolved: com.smartbear:swagger4j:jar:1.0-beta6, io.swagger:swagger-inflector:jar:1.0.6-SNAPSHOT: Failure to find com.smartbear:swagger4j:jar:1.0-beta6 in http://www.soapui.org/repository/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of soapUI Repository has elapsed or updates are forced -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
get this under 2.3.1 branch.

[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building SoapUI Swagger plugin 2.1.3
[INFO] ------------------------------------------------------------------------
[WARNING] The POM for io.swagger:swagger-parser:jar:1.0.8-SNAPSHOT is missing, no dependency information available
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.690 s
[INFO] Finished at: 2016-05-29T10:55:42+03:00
[INFO] Final Memory: 10M/205M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project soapui-swagger-plugin: Could not resolve dependencies for project com.smartbear:soapui-swagger-plugin:jar:2.1.3: Failure to find io.swagger:swagger-parser:jar:1.0.8-SNAPSHOT in http://www.soapui.org/repository/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of soapUI Repository has elapsed or updates are forced -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
on version-2.1.3

Hi - I'm sorry about this - I've just finalized 2.3.1 and merged it back to master - you should use master going forward - could you please try building that?
thanks!

[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Ready! API Swagger plugin 2.4.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[WARNING] The POM for com.smartbear:swagger4j:jar:1.0-beta6 is missing, no dependency information available
[WARNING] The POM for io.swagger:swagger-parser:jar:1.0.20-SNAPSHOT is missing, no dependency information available
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.979 s
[INFO] Finished at: 2016-06-07T21:14:00+03:00
[INFO] Final Memory: 12M/205M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project soapui-swagger-plugin: Could not resolve dependencies for project com.smartbear:soapui-swagger-plugin:jar:2.4.0-SNAPSHOT: Failure to find com.smartbear:swagger4j:jar:1.0-beta6 in http://www.soapui.org/repository/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of soapUI Repository has elapsed or updates are forced -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException

oops - you'll have to build that locally from https://github.com/SmartBear/swagger4j until I can get it pushed to our repository - I'm sorry for the hassle...

ok - i've pushed swagger4j-1.0.0-SNAPSHOT to sonatype and update the dependency herein - and also added a new SwaggerComplianceAssertion...

Can someone fix also the build for version 2.1.3? Because I'm facing a bug in 2.3 and 2.4 master and need to downgrade to an older version until the bug is fixed.


Api change

Hey @kkamalov,
I see you've already closed this PR - but I'd love to hear how you're using tota11y and why you chose to make these changes on your fork. Let me know if there's anything I can do!
Thanks,
Jordan


ReplicaSet connection not working when turning on Auth

Hello,
I set up a fresh servers and tested a 3 node replica set (2 + 1arb) according to the tutorial. Everything works fine.
However, connecting to the ReplicaSet via Mongoose doesn't seem to work, especially with auth.   I know that the replica set is working because rs.status() says health/state is all fine.
First, I turned off auth (did not have keyFile flag).  I try to connect to the replica set, but the following does not work. Nothing happens.
mongoose.connect('mongodb://host1,host2,host3/mydb');

According to the docs, this should work (http://www.mongodb.org/display/DOCS/Connections).
Oddly enough, this works:
mongoose.connect('mongodb://host1/mydb,mongodb://host2/mydb,mongodb://host3/mydb');

This weird format works, for some reason.  But, it shows an error in the primary mongo's logs:
[conn8] assertion 13530 bad or malformed command request?

Finally, after I turned on auth, I would always get "unauthorized".  I've tried multiple combinations.  This format should work, but I still get unauthorized:
mongoose.connect('mongodb://myuser:mypass@host1,host2,host3/mydb');

This also results in "unauthorized":
mongoose.connect('mongodb://myuser:mypass@host1/mydb,mongodb://myuser:mypass@host2/mydb,mongodb://myuser:mypass@host3/mydb');

How can I connect to my replica set correctly without getting unauthorized?
Thanks!

If I have Replica Set with servers:
<IP_ADDRESS>:27017
<IP_ADDRESS>:27018
<IP_ADDRESS>:27017
<IP_ADDRESS>:270178
When i specify the host in connectSet, do I need to include all 4 or just the host Ip?
ie.
a) mongoose.connectSet('mongodb://<IP_ADDRESS>:271017/mydb,mongodb://<IP_ADDRESS>:27018/mydb,mongodb://<IP_ADDRESS>:27107/mydb, mognodb://<IP_ADDRESS>108/mydb);
Or
b) mongoose.connectSet('mongodb://<IP_ADDRESS>/mydb, mongodb://<IP_ADDRESS>/mydb');


upgrade turbo

Upgrade to turbo v2

Seems build does not to work on Vercel. Works locally

Still getting issue with Vercel deployments unable to read from Vercel ENV vars after upgrading turbo


[4.1][CSSolver/TypeJoin] Look through optional types before trying to join

• Explanation: Bring back old code which deals with optionality of the types
before trying to compute their join, this is temporary before all of the
type visitor cases are implemented and we can switch to a better
implementation.
• Scope of Issue: Affects logic related to picking bindings for type variables in constraint solver.
• Origination: Caused by changes to type join implementation.
• Risk: Low risk; Fixes a bug in constraint solver.
• Reviewed By: @rudkx
• Testing: Compiler regression tests
• Radar / SR: rdar://problem/37241221
Resolves: rdar://problem/37241221
(cherry picked from commit 1f81667e85415e738a83208c2e4992a6f4f3901c)
(cherry picked from commit e74e3999b659cbb1feefb3f233afb30778282b84)

@swift-ci please test

@swift-ci please test source compatibility

@swift-ci please nominate


Base for new UI & base for Minimap & Hotbar.

Adding base placeholder for new Minimap.
Adding base placeholder for new Hotbar menu.
Structure clean up.

This PR looks ok, but it's not actually doing anything. It's creating a separate app.
Can we get this but part of the main app?

Also, missing description.

UI PR's should at minimum have screenshots or a note as to what changed, or else it is impossible to test.

Updated description.

I have tested the major functionalities
-No new errors or warnings
-Scenes loading fine
-Voice packs fine
-Both Logins working fine
-Character tab works fine
-Equipping items works fine
The stats panel appears beneath the minimap placeholder.
Everything Else seems fine.


interest in react-intl integration?

today I looked into react-intl. It offers a babel plugin for automatically extracting message ids from source code:
https://github.com/yahoo/babel-plugin-react-intl
I managed to use react-app-rewired to integrate it. Here's the code:
const babelLoader = function(conf) {
  return conf.loader === "babel";
};

//webpack2
function rewireIntl(config, env) {
  const babelrc = config.module.loaders.find(babelLoader).query;
  babelrc.plugins = [
    [
      "react-intl",
      {
        messagesDir: "./messages/"
      }
    ]
  ].concat(babelrc.plugins || []);
  return config;
}

module.exports = rewireIntl;

If you're interested I could create a pull request so you can maintain it as part of this project. One question is how to configure it. I've hardcoded "messagesDir" into it for now, and the configuration options aren't that broad, but perhaps people want something more.

@faassen very nice.
I'm slightly mixed feelings on including in this repo.
Personally I would like to see people adding 'rewires' to npm and I can link / point people to them from this repo.  The reason for that being if I don't personally use all the rewires i.e. which is currently the case with the relay rewire in this repo. I can't really at least not without tests for each in place if they will continue working. For instance when Webpack 2 hits CRA (soon) I won't know if the Relay one still works unless @pasviegas tells me it does.
I like the path of the rewires vs everyone needing to roll a config for MobX etc... but need some community around that idea to make it go further.
Note: I started down the testing path here but I'm really not sure what the best strategy is for the tests https://github.com/timarney/react-app-rewired/issues/9

My view is that right now would be better to have as many rewires as possible in the same repo so it can get some traction and release more people from the strict rules in create-react-app. 😄

Alright - let's add it to this repo.  @faassen if you want to create a PR at some point please do.  Might want to wait until 0.10.0 of CRA (that will be the Webpack2 release ... expecting to rejig some of the configs for that - I already prepped the MobX one).
@pasviegas thoughts on the note about:

I've hardcoded "messagesDir" into it for now, and the configuration options aren't that broad, but perhaps people want something more.

Probably not the best place but maybe could be added to the .env file.

@faassen going to close this issue.  Feel free to create a PR.  Thinking just hardcode the ./messages/ path for now and see if anyone has an issue with that ;)

@faassen just so your aware - https://github.com/timarney/react-app-rewired/issues/26 if you have any interest in adding a PR for the upcoming version.


Remove HDD reporting in the stats views

Which package/s are you suggesting this feature for?
No response
Is your feature request related to a problem? Please describe
Remove HDD reporting in the stats views
Describe the solution you'd like
Remove HDD reporting in the stats views

Verified on QA,
Version: 2.6.2
HDD reporting has been removed in the stats view

Related Link:
https://app.testlodge.com/a/26076/projects/40893/suites/234374?expand_section=426660#case_4150456

Verified on Mainnet.
Currently SSD capacity format is changed to be like "7,376,570 GB"

Related Link:
https://app.testlodge.com/a/26076/projects/40893/suites/234374?expand_section=426660#case_4150456


Cannot import name 'ModelMetaclass' from 'pydantic.main'

Describe the bug
When I run the python3 devika.py command, I am faced with ImportError: cannot import name 'ModelMetaclass' from 'pydantic.main'error, who know how I can fix this?
Below is the full traceback
File "/home/donztobs/Workspace/Projects/devika/devika.py", line 10, in <module>
    init_devika()
  File "/home/donztobs/Workspace/Projects/devika/src/init.py", line 24, in init_devika
    from src.bert.sentence import SentenceBert
  File "/home/donztobs/Workspace/Projects/devika/src/bert/sentence.py", line 1, in <module>
    from keybert import KeyBERT
  File "/home/donztobs/.local/lib/python3.10/site-packages/keybert/__init__.py", line 2, in <module>
    from keybert._model import KeyBERT
  File "/home/donztobs/.local/lib/python3.10/site-packages/keybert/_model.py", line 17, in <module>
    from keybert.llm._base import BaseLLM
  File "/home/donztobs/.local/lib/python3.10/site-packages/keybert/llm/__init__.py", line 28, in <module>
    from keybert.llm._langchain import LangChain
  File "/home/donztobs/.local/lib/python3.10/site-packages/keybert/llm/_langchain.py", line 3, in <module>
    from langchain.docstore.document import Document
  File "/home/donztobs/.local/lib/python3.10/site-packages/langchain/__init__.py", line 6, in <module>
    from langchain.agents import MRKLChain, ReActChain, SelfAskWithSearchChain
  File "/home/donztobs/.local/lib/python3.10/site-packages/langchain/agents/__init__.py", line 2, in <module>
    from langchain.agents.agent import (
  File "/home/donztobs/.local/lib/python3.10/site-packages/langchain/agents/agent.py", line 15, in <module>
    from langchain.agents.tools import InvalidTool
  File "/home/donztobs/.local/lib/python3.10/site-packages/langchain/agents/tools.py", line 8, in <module>
    from langchain.tools.base import (
  File "/home/donztobs/.local/lib/python3.10/site-packages/langchain/tools/__init__.py", line 3, in <module>
    from langchain.tools.base import BaseTool
  File "/home/donztobs/.local/lib/python3.10/site-packages/langchain/tools/base.py", line 16, in <module>
    from pydantic.main import ModelMetaclass
ImportError: cannot import name 'ModelMetaclass' from 'pydantic.main' (/home/donztobs/.local/lib/python3.10/site-packages/pydantic/main.py)

I solved the issue by upgrading my python3 from 3.10 to 3.11 and pip from 22 to 24.
This article guided me through https://medium.com/python-mvp/upgrade-python-3-10-to-3-11-on-ubuntu-22-04-2f63e4d326f9

I solved the issue by upgrading my python3 from 3.10 to 3.11 and pip from 22 to 24.
This article guided me through https://medium.com/python-mvp/upgrade-python-3-10-to-3-11-on-ubuntu-22-04-2f63e4d326f9


go lint failures on macos

What happened:
The make verify-go-lint fails on macos.
ERRO Running error: buildir: failed to load package : could not load export data: no export data for "github.com/seccomp/libseccomp-golang"
What you expected to happen:
Should not fail on macos.
How to reproduce it (as minimally and precisely as possible):
make verify-go-lint
https://github.com/naveensrinivasan/security-profiles-operator/runs/1765263186?check_suite_focus=true
Anything else we need to know?:
Environment:

Cloud provider or hardware configuration:
OS (e.g: cat /etc/os-release):
Kernel (e.g. uname -a):
Others:

I think it tries to include the seccomp build tag which fails on macOS:
https://github.com/kubernetes-sigs/security-profiles-operator/blob/master/.golangci.yml#L7

I think it tries to include the seccomp build tag which fails on macOS:
https://github.com/kubernetes-sigs/security-profiles-operator/blob/master/.golangci.yml#L7


Update OAuth2PasswordGrant Authenticator to use Fetch

This is a replacement for @bakerac4's PR #1060 that I messed up when trying to rebase his branch 😊
This PR implements the updates to the oauth2 password grant authenticator that allow it to work in Fastboot per #1049
Notable Changes
I created 'rejectWithResponse' to replace 'rejectWithXhr'
I added a deprecatingAlias pointing to rejectWithResponse for rejectWithXhr
I had to include ember-cli-import-polyfill as a dependency, otherwise ember-network fails to be included

@marcoow I was just taking a look at it! Thanks for taking care of the rebase!


Meaningless judgment

In MathParser/MathParser.cs Line 339
if (i != 0 && (char.IsDigit(expr[i - 1]) || char.IsDigit(expr[i - 1]) || expr[i - 1] == ')'))
I don't know why "(char.IsDigit(expr[i - 1])" write twice.
I think it's a slip of the pen.

I might have missed it when I wrote the first version of the parser (which was several years ago). Thank you for pointing that out!
I think that me and @napen123 will rewrite the entire parsing module using a parser generator, eg: http://goldparser.org/.


Add link to DOS agreements page

The page already exists and can be viewed for any framework so the simplest possible solution is to just add a link to the admin home page.
Before

After

At some point the admin interface needs a bit of love, but in terms of what we have right now I think this just grand and does everything needed :+1:

This has had the :+1: from @cathrooney too


random data inconsistency when thread using dynamodb-titan-storage-backend library is interrupted in commit phase

Hello,
We have encountered an issue with how this dynamodb-titan-storage-backend library handles interrupts to the parrallelMutate method in the "DynamoDBDelegate.java" code.
As can be seen in the method (https://github.com/awslabs/dynamodb-titan-storage-backend/blob/1.0.0/src/main/java/com/amazon/titan/diskstorage/dynamodb/DynamoDBDelegate.java#L285), interrupts to this method by titan are not handled gracefully. As per line 300, "// fail out because titan does not poll this thread for interrupted anywhere".
We are using the Hystrix library (https://github.com/Netflix/Hystrix) to protect our service from overloading. Every Titan transaction runs in a separate Hystrix command in our app. These commands are interrupted on timeout, so if any latency problem occurs, we are failing fast. This interruption may occur in various different moments of a TitanDB transaction. However, when the interrupt occurs, we are getting the following error on the parrallelMutate method (error trace shortened here for brevity, as indicated by "...", full stacktrace can be found at http://pastebin.com/LLzZXkiY):

13:19:13 [ERROR] [c.t.t.g.database.StandardTitanGraph] [] Could not commit transaction [9] due to exception
com.thinkaurelius.titan.core.TitanException: Could not execute operation due to backend exception
    at com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:44) ~[titan-core-1.0.0.jar:na]
    at com.thinkaurelius.titan.diskstorage.keycolumnvalue.cache.CacheTransaction.persist(CacheTransaction.java:87) ~[titan-core-1.0.0.jar:na]
...
Caused by: com.amazon.titan.diskstorage.dynamodb.BackendRuntimeException: was interrupted during parallelMutate
    at com.amazon.titan.diskstorage.dynamodb.DynamoDBDelegate.parallelMutate(DynamoDBDelegate.java:301) ~[dynamodb-titan100-storage-backend-1.0.0.jar:na]
...
13:19:13 [INFO ] [c.h.c.c.t.TitanTransactionManager] [] TRANSACTION - doRollback()
13:19:13 [ERROR] [c.h.c.c.t.TitanTransactionManager] [] Commit exception overridden by rollback exception
com.thinkaurelius.titan.core.TitanException: Could not commit transaction due to exception during persistence
    at com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1363) ~[titan-core-1.0.0.jar:na]
    at com.hybris.caas.category.titan.TitanTransactionManager.doCommit(TitanTransactionManager.java:126) ~[classes/:na]
...
Caused by: com.thinkaurelius.titan.core.TitanException: Could not execute operation due to backend exception
    at com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:44) ~[titan-core-1.0.0.jar:na]
    at com.thinkaurelius.titan.diskstorage.keycolumnvalue.cache.CacheTransaction.persist(CacheTransaction.java:87) ~[titan-core-1.0.0.jar:na]
...
Caused by: com.thinkaurelius.titan.diskstorage.PermanentBackendException: Permanent exception while executing backend operation CacheMutation
    at com.thinkaurelius.titan.diskstorage.util.BackendOperation.executeDirect(BackendOperation.java:69) ~[titan-core-1.0.0.jar:na]
    at com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:42) ~[titan-core-1.0.0.jar:na]
    ... 40 common frames omitted
Caused by: com.amazon.titan.diskstorage.dynamodb.BackendRuntimeException: was interrupted during parallelMutate
    at com.amazon.titan.diskstorage.dynamodb.DynamoDBDelegate.parallelMutate(DynamoDBDelegate.java:301) ~[dynamodb-titan100-storage-backend-1.0.0.jar:na]
...

We did some further investigations and we found out that if that interruption occurs during a commit phase, it may lead to data inconsistency.
That data inconsistency may show up as an inconsistency between Titan's composite index and real data (vertex is returned by index, but is not present in database anymore) or by incomplete vertex without all provided properties. In essence, it seems that while out thread is interrupted, the data is still inserted in the DynamoDB table during the operation. However, the rollback fails due to the backend exception caused by the parrallelMutate issue mentioned above.
We created a sample project to reproduce that problem, but to be fair it can be quite hard to reproduce it consistently.
With this sample project (https://github.com/marcinczernecki/titan-dynamodb-hystrix-issue), we were able to reproduce it once or twice, but we were running it over and over all day to achieve that. It's a Spring Boot application that creates an index (if it's not present) and runs Hystrix commands that wrap a Titan transaction with single vertex creation. The command has a configurable timeout (persistenceTimeout), so if you choose a proper value for this timeout, it should be interrupted during the commit phase (but it depends on your network latency to DynamoDB).
When all commands finish we are checking our data consistency within the DynamoDB table. Most of the time it seems to work OK but sometimes it leaves some inconsistency within the DynamoDB table. It might be that this inconsistency is more likely to occur when it's the first run and tables in DynamoDB doesn't exists yet (but that's not always the case).
When we use Cassandra DB as our TitanDB's backend we do not have such a problem, and we are using same application and Titan's settings there.
While we could potentially increase the persistenceTimeout value to a large value, this is not a suitable option for us. Extending the timeout to a a larger value would be contrary to our main goal which is to help our service stay responsive with Hystrix. Besides, it would likely negatively impact our applications performance which may make it not practical for our use-case.

Can this method ("parrallelMutate" and wherever else applicable) be altered please to handle any interrupts gracefully?
As it stands, this issue is even failing the resulting rollback process and is thus causing our DynamoDB table data to be inconsistent/out-of-sync with our application. This can often result in unexpected data within our table, "ghost vertices" in our graphs, etc.
Many thanks,

Krzysztof

What is your definition of handling interrupts gracefully? What behavior do you expect?

@kgenge Please submit a PR with repro/test case that elicits this behavior.

@kgenge Ghost vertices are part of the design of Titan, as it was built with distributed and eventually consistent storage backends in mind. Consistency is at the column (vertex property or edge) level in the multiple item model and at the out-vertex level in the single item model. The recommendations in Titan apply, and we recommend you use Faunus/Titan Hadoop to periodically clean up your graph.
Having said all that, I will abstract the specific inquiry about being gracefully interruptible in parallelMutate into a different issue.

@kgenge Locking fixes I will implement in the very near future might enable you to implement better semantics with a lock store.

@kgenge Depending on the size of your vertices and the average degree of your graph, using the single item model may help a lot, as all the vertex properties get put into the same DynamoDB item.


Allow for creating documentation that can link to external dependencies

This isn't the prettiest of code, nor approachs, but the goal of this
action so far is to get everything working "end-to-end" and then go
back and see what additional support we need in tooling to make the
process less brittle.
The code in this commit makes a lot of assumptions about the layout
of dependencies pulled by corral. It shouldn't be doing that. That
knowledge should be in corral and then we could either:

use parts of corral as a library from a pony version of this
have a corral command to get said information dumped in some fashion

or something similar. In the meantime, this works.
As usual, I apologize for my Python. It is what it is.
Closes #13

Hi @SeanTAllen,
The changelog - added label was added to this pull request; all PRs with a changelog label need to have release notes included as part of the PR. If you haven't added release notes already, please do.
Release notes are added by creating a uniquely named file in the .release-notes directory. We suggest you call the file 8.md to match the number of this pull request.
The basic format of the release notes (using markdown) should be:
## Title

End user description of changes, why it's important,
problems it solves etc.

If a breaking change, make sure to include 1 or more
examples what code would look like prior to this change
and how to update it to work after this change.

Thanks.


feat(components): rename builtin component content fields [LUMOS-459]

Purpose
Rename specific built-in component fields. This is only changing the displayName field so no breaking changes.
Ticket: https://contentful.atlassian.net/browse/LUMOS-459
https://github.com/user-attachments/assets/96457342-089c-4403-8a0e-c1c8c85334f2

Looks good to me overall.
Did you meant to include the package-lock.json file changes? Maybe this shouldn't be included in this PR?

Yeah the build failed without those changes so figured I had to include them.


Generate shasums and upload them as part of the release

It was mentioned by @darkk here: https://github.com/TheTorProject/ooni-sysadmin/pull/112/files/f47ab38baa78f1169baf15622d9a2516366038ea#r133564756

We are going to be discontinuing orchestra in the future. We can close this issue as no longer relevant.


Use Spark archive site to download for a broader range of versions that can be used.

The main download site does not include "archived" versions.

@creechy  Sorry it took so long for me to take a look.
Does the archive site contain the newest versions as well?

@creechy Sorry it took so long for me to take a look. Does the archive site contain the newest versions as well?

@mrn-aglic yes I believe it does. it might be a little slower than the main site but I believe all versions are there.


(release)[version] change branch-2.0 version to 2.0.11

Proposed changes
prepare to release 2.0.11

run buildall

run buildall


Build for Python 3.10

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender.


ISPN-13608 fix for NPE after stream.filterKeys(null) was used

https://issues.redhat.com/browse/ISPN-13608

Integrated into main, thanks @heli80 !


LE Audio: Cleanup handling of objects and included OTS

Expected things to do

ensure local controller using media_proxy can access media player objects directly, not via MCS
=> probable solution: Add direct object interface to MPL
update handling of included services to follow pattern from VCS (can possibly be factored out as separate story)
handling of objects in media_proxy

API, functions and callbacks - ~8 or so APIs

update media_controller shell commands

~8 commands, some are very similar, these relate to APIs

2022-03-23: Also: Guard object-related callbacks in media_proxy.h so that they are excluded from the struct if objects are not used.

Issue becomes obsolete after refactoring is done


Error: Unable to find a paired notebook for /src/bar.sync.py in registered notebooks: {}.

Im facing this error and am wondering if there is any version that jupyter needs to be pinned into to work?
My startup script:
#!/bin/bash
set -e
python3 -m jupyter_ascending.scripts.make_pair --base /src/$1
sleep 2
jupyter notebook --debug  --allow-root --ip='*' --NotebookApp.token='' --NotebookApp.password='' --no-browser $1.sync.ipynb & disown
sleep 3
python3 -m jupyter_ascending.requests.sync --filename /src/$1.sync.py
```
Cheers

Got around the problem by pinning jupyter client and tornado versions as the following:
jupyter-client==7.3.2 tornado==6.1

Hi @jeanCarloMachado , I am getting the same issue, could you please explain how you installed the versions for your work around?


any interest in a version of this for the game exe itself?

Hi! I found this while looking up Oregon Trail II stuff. During the pandemic I started reverse engineering the game as a side project because I guess this is what I do now.
So, I was wondering if there was any interest in a version of this that would randomize the game itself. Theoretically speaking, anything with tweakable numbers could be fairly straightforwardly randomized, which encompasses more than you might think, both the obvious (success chances for events, health, prices) and the less obvious (a lot of stuff about landmarks, for instance).

Hey there,
This project was made for MonotoneTim, but I don't think Tim has streamed OT II in years... you can try reaching out to see if they're interested, though.