firewall and firewall_rule resources always updated on windows

Cookbook version
2.5.0
Chef-client version
12.5.1
Platform Details
Windows server 2012r2
Scenario:
The firewall and firewall_rule resources are always updated (even if nothing has changed.
Steps to Reproduce:
With a recipe something like this:
firewall 'default'

firewall_rule 'http' do
  port 80
  protocol :tcp
end

Expected Result:
Subsequent chef runs should not update these resources if nothing has changed (IMO).
Actual Result:
They are always updated.
I can see the code at https://github.com/chef-cookbooks/firewall/blob/master/libraries/helpers_windows.rb#L100, but it appears as though this is never executed.

Hi @jkburges -- the firewall_rule resources simply collect data, so even when they are updated, nothing is actually changed in the system. The 'action' these resources take is simply to notify the firewall resource. I agree that the firewall resource should not show as updated. We'll have to look into why this is showing as updated, as if the same firewall_rule resources are present during each run, firewall should never show as updated.

Hi there -- I've made some changes to master so that the firewall resource itself won't report that it has been updated. I don't have a nice solution for the firewall_rule resource, as it always fires the action that causes the rules to accumulate into the firewall resource.


Custom authentication flow is not working.

I am trying to extend this app to use OTP based login But I am getting an error like initiateAuth is existed on type cognitoUser. Anyone got the same?

Duplicate #631


Make capsule configuration name configurable via helm

As this is fixed in the helm templates we need a very hacky implementation to change this value.
We have like 150 groups which we are creating in a new configuration.
So I suggest to make this configuration templated as well.

LGTM, may I ask you to amend the commits with the DCO and change the Pull Request title to feat(helm): capsuleconfiguration name configurable?
Thanks!

LGTM, may I ask you to amend the commits with the DCO and change the Pull Request title to feat(helm): capsuleconfiguration name configurable?
Thanks!

I tried to, but this DCO ... seems to make trouble? I'm lost here, sorry.

Hi @sybnex I got the problem, and I fixed.
JFI The current version of the DCO uses a version of Git that removed the dot ('.') considering it an invalid trailing crud character (commit ).
But I see you're using likely a Git version > 2.42, as the period is in your author name in your commit.
Thanks

Hi @sybnex, may I ask you to update the chart documentation?
I.e.:
+| manager.options.capsuleConfiguration | string | `"default"` | Change the default name of the capsule configuration name |

Overall LGTM


Fix test failing when load is cancelled before BDL is reached

Gonna tackle the other one in here too?


Implement GSO in the iokernel

The goal of this PR is to implement GSO (Generic Segmentation Offload) in the iokernel.

Seems to work.
Below: The client on the right sends 1460 'A' characters. Since the total packet header size (UDP + IP + Eth) is 42 bytes, the entire application data cannot fit in a single 1500 byte packet. So, we need two packets with 1458 'A' characters in the first packet, and the rest 2 'A' characters in the second packet.

udp_write_to now accepts arbitrarily sized packets
tx_burst in iokernel/tx.c can segment large packets in 1500-bytes packets


Sapling note decryption implementation

Motivation

We need an implementation of sapling note decryption for ZIP-212.
Specifications

https://zips.z.cash/protocol/protocol.pdf#saplingdecryptivk

https://zips.z.cash/protocol/protocol.pdf#saplingdecryptovk
Designs

We will use librustzcash to implement this for now.
Related Work

This is related to #271, #2041 and #2362

We're not planning to do full-node wallet work any time soon.
If we do, we'll need to decide if this ticket is in scope, and update its content, because the spec has changed since it was created.


Remove localHandler in favor of emitting an event

@jwolski @Raynos

lets add a test for the request event.

The current test does test this case. There is a listener registered at the top of allocCluster, and the fact that is is called is asserted at handle_or_proxy_test.js:87

Ok, cool, lgtm.


[v2.9] feat: bump harvester node driver to v0.6.7

Issue:
https://github.com/rancher/rancher/issues/43594
Releated Harvester issues:

https://github.com/harvester/harvester/issues/4588
https://github.com/harvester/harvester/issues/2764
https://github.com/harvester/harvester/issues/4777

This PR bump Harvester Node Driver to version v0.6.7

Merging with a single approval as it's the direct cherry-pick of already approved/merged PRs to other release lines (e.g. https://github.com/rancher/rancher/pull/43595)


Tschie/remove controlsfx

Prepares the samples to support java 9.

Update gradle/api versions (4.2+ needed for Java 9)
Update gradle wrapper
Removed controlsfx dependency (doesn't work for Java 9)

@john0005 Can you please review?


Prototype implementation of ADR24

[x] Tests added for any new code
[x] Ran make fmt-fix (or had formatting run automatically on all files edited)
[ ] Documentation added for any new functionality
[ ] Entries added to ./unreleased/ for any new functionality

This design has been discussed offline, but we should gather feedback on it on GH to keep track.
closes #2547

Codecov Report

Merging #2554 (2566dd5) into main (cfb6174) will decrease coverage by 0.02%.
The diff coverage is 44.73%.

@@            Coverage Diff             @@
##             main    #2554      +/-   ##
==========================================
- Coverage   78.51%   78.49%   -0.02%
==========================================
  Files         441      445       +4
  Lines       15546    15617      +71
  Branches     2544     2550       +6
==========================================
+ Hits        12206    12259      +53
- Misses       3340     3358      +18

Impacted Files
Coverage Δ

...he/tla/bmcmt/rules2/AssignmentStratifiedRule.scala
0.00% <0.00%> (ø)

...palache/tla/bmcmt/rules2/SubstStratifiedRule.scala
0.00% <0.00%> (ø)

...alache/tla/bmcmt/rules2/SetCupStratifiedRule.scala
82.35% <82.35%> (ø)

...yte/apalache/tla/bmcmt/rules2/StratifiedRule.scala
100.00% <100.00%> (ø)

... and 8 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

This design has been discussed offline, but we should gather feedback on it on GH to keep track.

As a record for future historians: this PR is a direct consequence of the decision in ADR24 though, right?

As a record for future historians: this PR is a direct consequence of the decision in ADR24 though, right?

https://apalache.informal.systems/docs/adr/024adr-arena-pass.html#isolated-arena-pass outlines the initial approach and the concerns that were raised there. This PR prods at the solution proposed in https://apalache.informal.systems/docs/adr/024adr-arena-pass.html#solution, to assess its viability.

The design looks great! We will revisit auxData in the future, right?

Yes, this is mostly just a 1st draft of the interface. I already have some follow-up to this PR planned, which will show different use cases for auxData, as well as an interface super-trait, which is parameter-free.

Are there meaningful tests to be added for assignment and subst?

Yes, but this PR is mostly just a sanity check on the interface, since there's not much to test atm, without meaningful constraint generation, or different arena rules.


Pop-up should be formatted to look better

I'll take a stab at this!

This is what I came up with, sending a PR in a bit!

Love it. But we might want to suggest multiple alternatives. Also, the recommendation should also explain WHY Mozilla is better than Chrome. So, the copy should be a paragraph, rather than sub-heading and a CTA.

I was thinking that the subheading can be used to explain why it is better (betterDescription).
And if we add betterHow tags in the schema, we can use those to succinctly describe why the alternative is better.
Maybe we can have one "recommended alternative", and other non recommended alternatives which can be shown with a little less emphasis?

Yes, that seems ideal. 👍 on description and tags.

This is how it looks now.


Initial implementation of nullable type

Addresses #282

Note: I had issues implementing HOC for nullable types, it was forcing loss of focus in inputs. Therefore, I used down and dirty Parent -> Child solution to implement nullable type.

I really appreciate the amount of work done here. Though, I'm still trying to figure out the benefits of json nullable types in general, and am challenging our willing to support them in this form lib. It really seems to me that they try to mimic the required jsonschema directive.
I suspect there's a bunch of tools relying on them (I've seen people mentioning .Net in issues), but I'm still wondering if we really want to support these very specific, exotic-to-us use cases; this library was never supposed to cover the entire scope of jsonschema, especially its corner cases.
The issue I have with landing code specific to certain existing tooling is that we (at Mozilla) don't use it, and we're not really prone to maintain something we don't use.
But maybe I'm missing something obvious, and there's a valid use case for nullable types in jsonschema, which can't be achieved with a required field?
On the other hand, I see value in providing a button to clear any entered value, so we would drop it from the resulting form data. Would that be an acceptable solution to you, or would you need actual support for nullable types because you critically depend on them?

We'd like to prevent the library from growing too much (if it's not too late already).
Would it be possible to add only the necessary hooks here and leave the NullableField implementation in your project?
What do you think ?

You might want to see issue https://github.com/mozilla-services/react-jsonschema-form/issues/402#issuecomment-262696104
and also https://github.com/mozilla-services/react-jsonschema-form/issues/410
The last one is mine.  I'm an advocate of turning "empty string" and "empty array" into undefined.
The string and array items are removed from the JSON data ... in the same way that they dissapear from the data for numbers and dates currently.
This allows them to pass or fail validation when setting the "required" field.  I personally plan to treat them as NULL in my backend and effectively disallow empty string (no loss for me).
Just throwing this out there in case it meets your requirements without adding a new nullable type :)
The array part of the patch has been submitted as a PR:
https://github.com/mozilla-services/react-jsonschema-form/pull/420
The string part is referenced in my issue here: https://github.com/mozilla-services/react-jsonschema-form/issues/410
but hasn't (and won't) be submitted as a PR until Issue #402 is decided upon.
Hope that helps!

I agree with @n1k0 that I don't really see the value of having null or undefined instead of a missing field. But I see in this PR the essence of a structure that could be useful for implementing oneOf (cf. #302, #417) or type: [] (as in #282). I think that if we could come up with a way to support "pick one" types on individual fields, that would be worth merging. Then, if we extend "custom fields" to let a user plug in some kind of "nullable field" like the one in the PR, I think that would cover the use case of #282 (assuming it wasn't already covered by #442).

No activity since last september, I'm closing this. Feel anyone free to reopen if you're planning to work on this.

I've been looking for a solution to this as I do have a use case for it. It may be too specific to be worth it but the short of it is that at least for our use case, there is a behavior difference between a value not being present in an API payload and a value that is being explicitly cleared or unset.
The details: I have an object with several integer properties that I want to update via an API call. For an update operation, all properties are optional; anything that is not provided as part of the API payload remains unchanged. Of course, a property set to a certain integer in the payload would change the value. In addition, though, I need to be able to 'unset' or clear any of these properties, so I need a way of expressing this via JSON. In my opinion, using undefined for this is asking for trouble because checking the difference between a property in a JS object not being present at all and being set to 'undefined' is error-prone in code. I'd much rather be able to set any given property to null instead.
So the behavior is something like this:
Payload {"iops_max":43} sets the value of iops_max to 43 and all other properties remain unchanged.
Payload {"iops_max":undefined} doesn't change anything. It would be the same as sending an empty object.
Payload {"iops_max":null} explicitly clears the value that is currently set.
So, I'd like my JSON schema to have type: ["integer", "null"] and accept both an update to a new integer value, and an intention to unset/clear. I appreciate that the difficult part here is having a UX that expresses this in an intuitive way... as others have said I would expect it could be done as a clear or 'x' control on the form field.
As far as I can tell this use case can't be addressed with the required field of JSON schema.


Fix pasting from clipboard on macOS

pbcopy does not print the content of the clipboard on macOS, it should be pbpaste.

That makes sense. Thanks for the fix!


ubuntu 22 jammy - few issues with sunshine

Hi - thanks for putting this together.
I was able to create the instance with spot/on-demand.
I'm having few issues running sunshine though. and the setup instructions do not help as few bits are missing. hoping the below will help others.
As i understand, you create a sunshine user to run sunshine vs running under ubuntu.

After the initial setup, the apt is broken as steam installs the apt repo as well. rm /etc/apt/sources.list.d/steam.list does the trick.

sunshine has no shell so cannot access dbus for most of the commands su -c "systemctl status sunshine" sunshine.
one need to exec a shell for the user sunshine once to properly setup the profile:

ubuntu$id sunshine
  uid=1000(sunshine) gid=1000(sunshine) groups=1000(sunshine),29(audio),44(video),46(plugdev),100(users),107(input),119(netdev)
ubuntu$ sudo machinectl shell --uid=1000
sunshine$ systemctl status sunshine

although sunshine is part of input group, it still cannot get permission to access input.
sunshine : sunshine audio video plugdev users input netdev

full log:
sunshine@i-xxx:~$ cat .config/sunshine/sunshine.log
[2023:08:15:20:25:11]: Info: Sunshine version: v0.20.0
[2023:08:15:20:25:11]: Warning: Failed to create system tray
[2023:08:15:20:25:11]: Error: Couldn't load cuda: -1
[2023:08:15:20:25:11]: Warning: Couldn't find /dev/dri, kmsgrab won't be enabled
[2023:08:15:20:25:11]: Error: Unable to initialize capture method
[2023:08:15:20:25:11]: Error: Platform failed to initialize
[2023:08:15:20:25:11]: Error: Could not create Sunshine Mouse: Permission denied
[2023:08:15:20:25:11]: Error: Could not create Sunshine Touchscreen: Permission denied
[2023:08:15:20:25:11]: Error: Could not create Sunshine Keyboard: Permission denied
[2023:08:15:20:25:11]: Error: Unable to create some input devices! Are you a member of the 'input' group?
[2023:08:15:20:25:11]: Info: Falling back to XTest
[2023:08:15:20:25:11]: Info: // Testing for available encoders, this may generate errors. You can safely ignore those errors. //
[2023:08:15:20:25:11]: Info: Trying encoder [nvenc]
[2023:08:15:20:25:12]: Info: Encoder [nvenc] failed
[2023:08:15:20:25:12]: Info: Trying encoder [vaapi]
[2023:08:15:20:25:14]: Info: Encoder [vaapi] failed
[2023:08:15:20:25:14]: Info: Trying encoder [software]
[2023:08:15:20:25:15]: Info: Encoder [software] failed
[2023:08:15:20:25:15]: Fatal: Couldn't find any working encoder
[2023:08:15:20:25:15]: Error: Video failed to find working encoder
[2023:08:15:20:25:15]: Info: Open the Web UI to set your new username and password and getting started
[2023:08:15:20:25:15]: Info: File /home/sunshine/.config/sunshine/sunshine_state.json doesn't exist
[2023:08:15:20:25:15]: Error: Failed to create client: Daemon not running
[2023:08:15:20:25:15]: Info: Configuration UI available at [https://localhost:47990]
[2023:08:15:20:26:11]: Info: Terminate handler called

sudo setcap -r $(readlink -f $(which sunshine)) seems to help with a reboot of the sunshine service.
I got it to work ultimately but the installation remains a bit flaky at this time.

Thanks a lot for detailed feedback and the proposed solutions, @Jonathan34!
The root cause seems to be the broken APT which I fixed now with #61. I hope this works for you.
Unfortunately, I cannot reproduce the issues with sunshine v0.18.4 (which is installed automatically) but I'll come up with a separate PR to update sunshine to the recent version (I noticed you tested with v0.20.0) and for now I'll stick to v0.18.4. ✌

Thanks! your repo saved me quite some time to setup resources. so thanks for sharing it.
I also added support for DDNS and dynamic ip update with no-ip.com (so you do not need an elastic ip) and automatically installed packages like firefox, lutrix, wine, wine-tricks for example.
sunshine 0.20 has some sysctl startup service issue as well, it now depends on xdg but it never really starts. outside of that, it works fine.


Update Rust port link

Hey @wolfgarbe,
first of all thank you very much for open-sourcing such a great library like SymSpell.
I noticed you already included link to Rust port docs few days ago while the repo was still private (I am surprised you even found it!) so I'm just updating a link to point to now public repository.

Thanks for the updated link!


improve robustness

overall, it looks like this
v5.3.1-alpha.1-g42fa1289(emqx@<IP_ADDRESS>)34> esockd:listeners().
[{{'tcp:default',{{0,0,0,0},1883}},<0.2626.0>},
 {{'ssl:default',{{0,0,0,0},8883}},<0.2606.0>}]
v5.3.1-alpha.1-g42fa1289(emqx@<IP_ADDRESS>)35> supervisor:which_children( <0.2626.0>).
[{listener,<0.2629.0>,worker,[esockd_listener]},
 {acceptor_sup,<0.2628.0>,supervisor,[esockd_acceptor_sup]},
 {connection_sup,<0.2627.0>,supervisor,
                 [esockd_connection_sup]}]

econnaborted - Software caused connection abort

econnaborted is maybe an error happens while socket is being closed.

If it's an transient error, it could be retried, e.g. https://github.com/emqx/esockd/pull/28 thought it's transient.
If it's an permeant error, maybe the best strategy is to:

close the socket, and stop with normal reason
socket close will trigger listener process to restart, which will in turn restart acceptors due to rest_for_one

If we cannot bet on retry, then close socket + stop normal is perhaps a better choice.


exclude test build files from packages

Description
Tests aren't being type checked because they are excluded tsconfig.json files. If this exclusion is removed type-checking is applied, but the resultant test build files need to be excluded from the package.
This PR

adds the !build/ts/**/*.test.* file exclusion the to all package.json files. build/* include pattern was changed to build in order for the exclusion pattern to work properly.
removes test exclusion from tsconfig.json in cases where there aren't type errors. Most packages have type errors that will be addressed in the future. To check just remove the test patterns from the exclude section of tsconfig.json.
Also, renamed test/ directories to tests/ across all packages. This improved consistency removes the need to match multiple patterns for tests.

Changes beyond the rename are in this commit.

To test what files are included in a package, use npx npm-packlist from the package directory.
Type of change

[X] in all Patch: Bug (non-breaking change which fixes an issue)

Checklist

[X] I have added a changelog entry, prefixed by the type of change noted above (Documentation fix and Test update does not need a changelog as we do not publish new version)

!build/ts/**/*.test.* is good for excluding test files. I wonder if we should exclude the whole test / tests folders, as sometimes those folders contain utility files that are only used within tests: ls -d packages/*/src/**/test{,s}/** | grep -v '\.test\.' give you a list of them. Do you think doing "!build/ts/**/tests/" instead would be worth it?
Annoyingly it seems half of our tests live in folders called test and half live folders called tests (ls -d packages/*/src/**/tests | wc -l vs ls -d packages/*/src/**/test | wc -l). the Shopify convention tends to be naming tests folders tests (3999 usages of tests in web, vs 6 for test). That's pretty annoying as ignoring both folder names in package.json feels rubbish. Renaming all instances for test folders to tests is also gonna be noisy but I'm a sucker for conventions. Reckon it might be worth it?

test folders have been renamed to tests.


Can I write date into websocketclient outputstream directly

Describe what you would like to know or do
Hello. I have a Recorder Object which need to connect to a outputStream. I need to send the data from outputStream by websocket.
Describe the solution you'd considered
Now my solution is like this:
ByteArrayOutputStream baos=new ByteArrayOutputStream();
FFmpegFrameRecorder recorder=new FFmpegFrameRecorder(baos,2);
recorder.record(xxxx);
baos.toByteArray();
webSocketClient.send(baos.toByteArray());

It works. But I must care about when the baos has data.
I am wondering if there is a solution that allows me to directly connect the stream to the websocket
I have tried this:
FFmpegFrameRecorder recorder=new FFmpegFrameRecorder(webSocketClient.getSocket().getOutputStream(),2);

But the problem runs into fails. Can anyone give me some advice?
Looking forward to your replays.
Additional context
No other context

It sounds like you could create your own OutputStream subclass which forwards to WebSocket:
public class WebSocketOutputStream extends OutputStream {
	private final WebSocket ws;

	public WebSocketOutputStream(WebSocket ws) {
		this.ws = ws;
	}

	@Override
	public void write(int b) {
		ws.send(new byte[]{(byte)b});
	}

	@Override
	public void write(byte[] b) {
		ws.send(b);
	}

	@Override
	public void write(byte[] b, int off, int len) {
		ws.send(ByteBuffer.wrap(b, off, len));
	}

	@Override
	public void close() {
		/* depending on your use case possibly close socket */
	}
}

Then you can simply pass it to FFmpeg:
FFmpegFrameRecorder recorder = new FFmpegFrameRecorder(new WebSocketOutputStream(webSocketClient), 2);

Thanks. Sounds Good! I'll have a try.
By the way. Is there any problem in my code like:
FFmpegFrameRecorder recorder=new FFmpegFrameRecorder(webSocketClient.getSocket().getOutputStream(),2);

The websocket protocol wraps all messages using its own encoding scheme. Your code writes directly to the underlying TCP socket. Since the ffmpeg output is not valid websocket data (as specified in RFC 6455), the other endpoint will get errors when trying to decode the websocket frames.

It works well. Thanks


feat(category_theory): basic definitions

This is just the start of a PR of my category theory library.
I'm very happy to add components to this PR if it is easier to see more things in context.
I am not attached at all to any of the notational choices, and am quite happy to change these. (I do really want to keep a notation like the current f ≫ g for "do f, then g", but don't mind the symbol.)

I noticed that the composition notation ≫ (or in my case, ∘) binds tighter than functor application (to morphisms) &>. This feels backwards to me, as I'd like to pretend &> is really function application and isn't there at all, and so it should have the highest binding power, like function application. I'm thinking of F &> f ∘ g as corresponding to math F f ∘ g which means (F f) ∘ g, not F (f ∘ g).

Some notation for the components of a natural transformation is necessary. I've been using
notation t ` @> `:90 X:90 := t.components X

@rwbarton, I've added @> for components of natural transformations.
How about we use ⊚ for the conventional order composition? It's easy to type as \oo, and looks similar enough to the usual operator to be unambiguous? (I've include this in the latest commit.)

@rwbarton, I did try having category extend graph at some point, and from memory it worked, but decided:

sometimes you had to refer to graph.Hom when you really were talking about the Hom for a category, and this felt weird and awkward
It's weird to talk about the Homs of a graph.

Even though logically an extension works fine here, I don't think it's giving you much, and it's conceptually unclear. Given the fairly narrow payoff (i.e. only inside a file or two where we develop that adjunction between categories and graphs) I didn't like it.

@semorrison, regarding category and graph, that makes sense. Perhaps it would be nice if one could rename the fields of a parent structure when extending...

Does anyone have more review comments? As far as I'm aware, this is ready to go.
The travis failure is just due to a timeout (which on bad days mathlib is running up against), and as far as I can see does not indicate a problem with this PR.

There is not even a travis failure on your last commit, right?

You're right --- merging in master prompted travis to rebuild, and succeed this time.

Further review:

For category: identity -> id, compose -> comp, left_identity: id_comp, right_identity: comp_id, associativity -> comp_assoc.
Why is functor in its own directory?
Identation: we don't add identation when listing the fields of a structure, i.e. for category, Functor, and NaturalTransformation the list of fields in the structure definition are not indented.
While the structures and most theorems should be just in the category_theory namespace, especially the instances should be in the namespace of the corresponding structure: Functor.has_one  and NaturalTransformation.has_one
I'm not sure about the best names for functor fields. on_objects -> obj, on_morphisms -> map, identities -> map_id, functoriality -> map_comp
should we really introduce all these infix operators for application?
"Unfortunately, while we'd like to write components of natural transformations via function application (e.g. τ X), this requires coercions to function types, which I don't like." I would prefer the coercion to functions. I don't think this comment should be in the documentation, also you should explain why you don't like it. Why do you force us to use all these strange symbols for applications ;)

I still don't like the syntax:

there are 2 morphism composition symbols. I think there should be only one, if users want another one they can add them using local infix
Functors should define a coercion for the object map, and F.map for the morphism map.
the names for NaturalTransformation are very long, I think most of them should be just in the NaturalTransformation namespace, and instead of vertical_composition and horizontal_composition we have vcomp and hcomp

Sorry, still haven't finished sorting out coercions, and verifying that replacing Functor.on_objects with a coercion doesn't break all my later proofs too much. I'll mark this [WIP] for a few days again.

I have finally prepared an example showing the difficulty that introducing coercions creates for me: the simplifier sometimes fails to rewrite underneath coercions.
At the moment the only options I see are:

Avoid using coe_to_fun instances, and have simp remain effective.
Write two versions of most simp lemmas, once with coercions (for the humans) and once without (for simp).
Give up on some of the power of simp.

I'll post the example on zulip, and perhaps discussion of this issue can go there for now.
https://leanprover.zulipchat.com/#narrow/stream/113488-general/topic/simp.20inside.20expressions.20with.20coe_to_fun.20sometimes.20fails

I would really prefer if the automation could stay!

Okay, with that latest commit I think I've dealt with the outstanding issues (thanks to @digama0 for some help today!)

There are now coercions for writing F X and α X (functors and natural transformations acting on objects.
All the names have been shortened per @johoelzl's suggestions, except for functoriality, which I just couldn't bring myself to rename to map_comp. (To a mathematician, this feels a bit like renaming "beer" to "malted barley beverage". :-)
Definitions are in better namespaces (category, Functor, NaturalTransformation are in category_theory, everything else in this PR is inside one of those).
All these changes remain compatible with the automation I want to do later! (And that automation is better as a result.)
There's just one notation for morphism composition, and an instruction advising creating another one if you prefer.

A few remaining questions:

Should I rename Functor to functor (my preference is not, as this is a 'bundled' definition; later I'll add the is_functorial typeclass)?
Should I rename NaturalTransformation to something? (my preference is not to, as with functor; I could add a is_natural typeclass as well, although in later developments I haven't seen a use for it yet)

My inclination is to actually remove entirely the has_one instances. I
think they're more cosmetic than useful. What do you think?
On Tue, Aug 7, 2018 at 2:47 PM Mario Carneiro<EMAIL_ADDRESS>wrote:

@digama0 commented on this pull request.
In category_theory/functor.lean
https://github.com/leanprover/mathlib/pull/152#discussion_r208097679:

+definition identity : C ↝ C :=
+{ obj     := λ X, X,

map     := λ _ _ f, f,
map_id  := begin /- obviously' says: -/ intros, refl end,
functoriality := begin /- obviously' says: -/ intros, refl end }

+instance has_one : has_one (C ↝ C) :=
+{ one := identity C }
+
+variable {C}
+
+@[simp] lemma identity.on_objects (X : C) : (identity C) X = X := rfl
+@[simp] lemma identity.on_morphisms {X Y : C} (f : X ⟶ Y) : (identity C).map f = f := rfl
+@[simp] lemma has_one.on_objects (X : C) : (1 : C ↝ C) X = X := rfl
+@[simp] lemma has_one.on_morphisms {X Y : C} (f : X ⟶ Y) : (1 : C ↝ C).map f = f := rfl
Do we need both of these? I would prefer to have identity simplify to 1
so that we only need the second set of lemmas. Unless you are having
similar problems as with simp under coe, but I don't think this should
happen.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/leanprover/mathlib/pull/152#pullrequestreview-143838953,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAdLBH11DTk66mfR6UlBDBAwzyvvJkV5ks5uORvjgaJpZM4UYZ19
.

I have made the renamings you suggested. (The functoriality -> map_comp
renaming only under protest! :-)
On Tue, Aug 7, 2018 at 3:00 PM Scott Morrison<EMAIL_ADDRESS>wrote:

My inclination is to actually remove entirely the has_one instances. I
think they're more cosmetic than useful. What do you think?
On Tue, Aug 7, 2018 at 2:47 PM Mario Carneiro<EMAIL_ADDRESS>wrote:

@digama0 commented on this pull request.
In category_theory/functor.lean
https://github.com/leanprover/mathlib/pull/152#discussion_r208097679:

+definition identity : C ↝ C :=
+{ obj     := λ X, X,

map     := λ _ _ f, f,
map_id  := begin /- obviously' says: -/ intros, refl end,
functoriality := begin /- obviously' says: -/ intros, refl end }

+instance has_one : has_one (C ↝ C) :=
+{ one := identity C }
+
+variable {C}
+
+@[simp] lemma identity.on_objects (X : C) : (identity C) X = X := rfl
+@[simp] lemma identity.on_morphisms {X Y : C} (f : X ⟶ Y) : (identity C).map f = f := rfl
+@[simp] lemma has_one.on_objects (X : C) : (1 : C ↝ C) X = X := rfl
+@[simp] lemma has_one.on_morphisms {X Y : C} (f : X ⟶ Y) : (1 : C ↝ C).map f = f := rfl
Do we need both of these? I would prefer to have identity simplify to 1
so that we only need the second set of lemmas. Unless you are having
similar problems as with simp under coe, but I don't think this should
happen.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/leanprover/mathlib/pull/152#pullrequestreview-143838953,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAdLBH11DTk66mfR6UlBDBAwzyvvJkV5ks5uORvjgaJpZM4UYZ19
.


Switches to positive wording for all rules besides 2.3,

simply because I could not find appropriate wording.
NOTE: No intentional semantical changes have been made. If you find issues, please, please, please let me know
Harmonises the use of "call" and "invoke" to use "call" in all places
where "invoke" was used.
@reactive-streams/contributors Could you please sanity check the changes proposed here? Thanks!
Please vote/comment before the 21st of January (as always, if you need more time let us know)

Very good initiative, avoiding negation makes the intent clearer in all those cases.

LGTM

@rkuhn Thanks for the feedback, I owe most of it to @DougLea for not only raising the issue but also suggesting how to reword it.

@reactive-streams/contributors Merging!


Remove all text from products description

What I'm trying to achieve
I added a description to a product and would like to remove the text for now, but it doesn't seem to save when deleting all the text.
Deleting text from the description works if you don't delete all of it. But once you delete all of it, it doesn't get saved correctly. When refreshing the product the text is back.
Steps to reproduce the problem

Create a product with a description and save it.
Remove all text from the description(so there is no description) and save it.

What I expected to happen
I expect all the text to get deleted.
Screenshots

System information
Operating system: Windows / Docker
Browser: Chrome

Thanks for reporting, it's a bug.

Issue resolved in new description editor.


Add readme with info about the project

It would be helpful to have some information about the purpose of the project in the readme.

Done!

Thanks! ❤


Video losing player controls

Thanks for the extension, it's working greatly for most of the cases 🎉
I noticed that after using this AdSkipper, I lost control over the video player controls. It's not focused on the controls anymore so clicking space (to play/pause) and the arrows (forward, backward, volume up/down) doesn't work.
It seems the implementation adds an iframe to the page on top of the actual video player (z-index?). Is it possible to keep the video player controls from the iframe focused rather than the actual youtube video player? That way it would keep the same behavior as youtube, meaning, if you click any part of the page, it gives control back to the video player control.

It also removes the autoplay button, and videos do not play continuously.

I am aware of the issue and it is fixed in version 3.5. It is live on Firefox and will be soon live on Chrome (when they review it) so make sure you update it as soon as possible.
I will close this for now, but feel free to open new issue if it happens again. Thanks


Doesn't have completion/docs for core Ruby modules/classes

Operating System
Ubuntu
Ruby version
3.2
Project has a bundle

[X] Has bundle

Ruby version manager being used
rbenv
Description
Since I started trying to use it, I've never seen the Ruby-LSP extension have autocomplete or docs (as portrayed in the documentation) for core Ruby modules/classes. I recorded this screencast of setting up a brand new Hello World ruby project in a vanilla VSCode Ruby devcontainer to demonstrate:
https://app.screencast.com/nxu9LQIS0YUWO?conversation=RU4ol9HhxOHuW72wMGEoFh
Steps:

Make a new directory
open the directory in VSCode
Create a new Ubuntu Ruby devcontainer for the project
Ensure deprecated Ruby extensions are disabled and uninstalled
Ensure Shopify Ruby and Ruby-LSP extensions are installed and enabled
Create new Ruby file
Attempt to use autocomplete/intellisense for core Ruby classes like IO, Kernel, File...

Indexing classes and modules from the Core library via RBS has been shipped in v0.17.3.
Indexing Core methods and constants is next. You can follow the progress in https://github.com/Shopify/ruby-lsp/issues/1335.


Fix #124 (slow prints when data is sent in chunks)

Should fix #124 but untested.
Maybe ReadLongRunningTask() should get the same treatment, not sure.

Hmm, after some googling a BlockingCollection should be the better solution as it works without arbitrary delays.
I'm not very experienced in C#, so sorry this fix isn't ideal.

I haven't reviewed yet but I hope to do so this weekend.  In the meantime, @neon-dev  would you mind adding a new test type to the console app as part of this PR that reproduces your issue? If I understand correctly, the issue is because there's a long receipt with each line being a separate printer.Write() call instead of using a ByteSplicer.Combine() to send a single write call?  Would be good to have an example in the console test suite since we typically run through those before publishing a new version and would make sure we don't have a performance regression here in the future.

I counted how many individual Write calls the shortest possible receipt takes (including commands for alignment etc.) and got 45.
So the old synchronous code can be tested with these simple lines and results in ~31 ms:
var stopwatch = new Stopwatch();
stopwatch.Start();
for (int i = 0; i < 45; i++) {
    printer.Write(E.LeftAlign());
}
stopwatch.Stop();
Console.WriteLine($"Duration: {stopwatch.ElapsedMilliseconds} ms");

But the new one will report 0 ms and can only be measured by modifying the BasePrinter class and adding a(nother) wait logic somewhere to detect when the WriteBuffer is fully drained.
I don't know about you but I dislike this idea.
We wouldn't have to worry about regressions if the async task would use said BlockingCollection backed by a simple Queue because then there are no delays involved, which would make everything even more responsive while also removing the potential for CPU load issues.
Unfortunately I won't find enough time in the near future to update my PR with this superior, alternative solution.

@lukevp have you looked into a better solution?
I'd also suggest a note about this performance issue in the README in the meantime.

Closing due to https://github.com/lukevp/ESC-POS-.NET/issues/124#issuecomment-2258120511 (includes a better solution)


Add k8s resource limit patch lib

Issue
Need to be able to limit resource usage of a charm.
Crossref: OPENG-272
Solution
Create lib to patch k8s compute resource limits and requests.
Context
NTA.
Testing Instructions

Deploy prom/318.
Compare to kubectl patch statefulset prom -n welcome -p '{"spec": {"template": {"spec": {"containers": [{"name":"prometheus", "resources": {"limits": {"cpu": "2", "memory":"2Gi"}, "requests": {"cpu": "2", "memory": "1Gi"}} }] }}}}'

Release Notes
Add k8s resource limit patch lib.

There's a complication:

When patching the StatefulSet with {"memory": "0.9Gi"}, k8s generates a PodSpec with {"memory": "966367641600m"}, i.e. millibytes (e.g. to convert it back to GiB, value = bitmath.Byte(float(memory[:-1]) / 1000).to_GiB().value).
K8s docs claim that the m suffix if part of SI, but that seems to be false, at least for binary multiples.

Is there a way to force K8s to KEEP the same unit the user provided? @simskij @rbarry82

There's a complication:

When patching the StatefulSet with {"memory": "0.9Gi"}, k8s generates a PodSpec with {"memory": "966367641600m"}, i.e. millibytes (e.g. to convert it back to GiB, value = bitmath.Byte(float(memory[:-1]) / 1000).to_GiB().value).
K8s docs claim that the m suffix if part of SI, but that seems to be false, at least for binary multiples.

The .is_ready() method compares statefulset to actual pod and currently it is buggy because of the above.
Is there a way to force K8s to KEEP the same unit the user provided? @simskij @rbarry82

Not that I know off, but I'll dig. What happens if you instead of 0.9Gi set it to<PHONE_NUMBER>00m from the get-go? Does it still bug?

There's a complication:

When patching the StatefulSet with {"memory": "0.9Gi"}, k8s generates a PodSpec with {"memory": "966367641600m"}, i.e. millibytes (e.g. to convert it back to GiB, value = bitmath.Byte(float(memory[:-1]) / 1000).to_GiB().value).
K8s docs claim that the m suffix if part of SI, but that seems to be false, at least for binary multiples.

The .is_ready() method compares statefulset to actual pod and currently it is buggy because of the above.
Is there a way to force K8s to KEEP the same unit the user provided? @simskij @rbarry82

Not that I know off, but I'll dig. What happens if you instead of 0.9Gi set it to<PHONE_NUMBER>00m from the get-go? Does it still bug?

Ok, so found it. The reason for this is that 0.9GiB (Gibibyte) in its canonical form (ie. without fractional digits, using the largest possible suffix, is m.

Before serializing, Quantity will be put in "canonical form". This means that Exponent/suffix will be adjusted up or down (with a corresponding increase or decrease in Mantissa) such that: a. No precision is lost b. No fractional digits will be emitted c. The exponent (or suffix) is as large as possible. The sign will be omitted unless the number is negative.

If we just disallow setting fractions in the first place, the problem will be solved. For instance, 900Mi will not get converted, while 0.9Gi will. Likely, 900Mi was also what the user tried to express when they put in 0.9Gi, which isn't entirely true as 0.9Gi = 6866,46Mi.

disallow setting fractions in the first place, the problem will be solved.

There's also the case of 1000000Mi we should probably support what k8s supports and do proper conversion.

Problem: when there is a single unit of prometheus and the user sets too high resource limits, then juju is stuck in
prometheus-k8s/0  unknown   lost

because the pod cannot be scheduled and there is no charm to take juju config changes to repatch the statefulset.
Any ideas @simskij @rbarry82?
For example, is there a way to ask K8s ahead of time if a given limit is going to be a problem, so I could BlockStatus instead?

Problem: when there is a single unit of prometheus and the user sets too high resource limits, then juju is stuck in
prometheus-k8s/0  unknown   lost   0/1

because the pod cannot be scheduled and there is no charm to take juju config changes to repatch the statefulset.
Any ideas @simskij @rbarry82? For example, is there a way to ask K8s ahead of time if a given limit is going to be a problem, so I could BlockStatus instead?

This is kind of a consistent mess with the kube scheduler. That is -- the kube scheduler is not aware of what else is happening on the system, and a trival process which just malloc()s up to 80% will happily let "guaranteed" pods be scheduled which are then OOM killed.
In general, kubelet itself can (and by best practice, does) reserve a certain amount of memory beyond which it will refuse to schedule because the kernel OOM killer may accidentally kill important things (like the kubelet, even, or anything else) otherwise, or swap it out.
Inside the pod, /proc is present. So from a basic level, you can check /proc/meminfo and do comparisons to see whether there is free memory. Then, you'd need to determine where the pod is running (if we hope/assume that, once a limit is set, even if the other nodes in the cluster are under MemoryPressure, that it can be rescheduled here, though that could also be racy), and describe the node to see whether there's room. Such as:
status:
  ...
  allocatable:
    cpu: "4"
    ephemeral-storage: "113180564088"
    hugepages-1Gi: "0"
    hugepages-2Mi: "0"
    hugepages-32Mi: "0"
    hugepages-64Ki: "0"
    memory: 7895304Ki
    pods: "110"
  capacity:
    cpu: "4"
    ephemeral-storage: 122808772Ki
    hugepages-1Gi: "0"
    hugepages-2Mi: "0"
    hugepages-32Mi: "0"
    hugepages-64Ki: "0"
    memory: 7997704Ki
    pods: "110"

Lastly, you'd need to check on the pod itself, which may be further limited (if there's no resource limits set in the podspec, this is probably unnecessary paperwork, but regardless) via /sys/fs/cgroup/memory/memory.limit_in_bytes inside the pod.
Trivially, checking /proc/meminfo to see the amount of free memory (which kube doesn't actually care about, but we may, lest it get OOM killed immediately) versus status["allocatable"]["memory"] on a single node under the guess that the cluster is homogenous (and/or the Juju admin deployed with some constraints applied, so we'll end up on an identical worker node) will let you check via differencing whether /proc/meminfo:MemTotal and allocatable memory differ to determine the amount of memory reserved in the kubelet (if any -- if there isn't one set, memory.limit_in_bytes will be like 9.2 exabytes).
If there isn't a reservation, then all you have to go on is whether a particular node (the one you're running on, maybe) has enough free memory, or you can check all of them, then 🤞 that some other pod which is pending or cannot be scheduled due to MemoryPressure doesn't steal it from you when you patch the StatefulSet. Or just set BlockedStatus and with a message that the requested limits won't be applied.

Ready for re-review, @simskij @rbarry82 @dstathis.


Merge license and documentation updates

Merge license files and documentation changes from upstream repository.

Downgrading this to minor effort. This is a pro forma review of non-code changes downstreamed from the parent repository.


rename

realized this should probably be cwp (current working path) and not cwf (current working file).

[x] done


[fix] probabilistic models naive; web version: https://augusthered.github.io/

web version: https://augusthered.github.io

Such web version doesn't count. Your PR has conflicts, I can't merge it


Extract CRM Bundle

Tasks:

[ ] gather feedback for my changes
[x] added changelog line

Informations:

Q
A

Tests pass?
yes

Fixed tickets
TODO

BC Breaks
none

Doc
none

Can you also link the corresponding husky PR?

Please also remove TermsOfDeliveryController, TermsOfPaymentController and the financial tab in the UI.

Still stumbling upon some iban components, shouldn't all of them be removed?

I would add the resolve target entity for the tests in the TestBundle, where it is valid for all tests, instead of adding it to every single bundle.

corresponding husky PR https://github.com/massiveart/husky/pull/466

@danrot i will create a new PR for move finacials tab

If I try to assign a main contact I'll get a 500 error.

@danrot also fixed it was a braces issue in the controller


support Czech in for nightly builds

As far as I know, Czech is available http://downloads.dbpedia-spotlight.org/2016-10/.

Hi @papousek , thank you for the PR
Also we have some space at the demo server to install more languages. Let's open an issue to install Czech there.
Best,


Package pngcrush is not available, but is referred to by another package.

I tried:
apt-get install -y advancecomp gifsicle jhead jpegoptim libjpeg-progs optipng pngcrush pngquant

and the get the following error:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package pngcrush is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Unable to locate package advancecomp
E: Unable to locate package gifsicle
E: Unable to locate package jhead
E: Unable to locate package jpegoptim
E: Unable to locate package libjpeg-progs
E: Unable to locate package optipng
E: Package 'pngcrush' has no installation candidate
E: Unable to locate package pngquant

Please tell about your environment.
First suggestion from stackexchange about «Unable to locate package» is to run sudo apt-get update. Maybe it will resolve the pngcrush error to. Also you may want to try image_optim_pack.

I use Ubuntu 12.04 LTS

I was able to reproduce the same output after removing package index files (using sudo rm -r /var/lib/apt/lists/*) in fresh ubuntu precise in vagrant. After running then sudo apt-get update and sudo apt-get install … all packages were installed successfully.

Any progress on this?

Done. Thank you.


feat: ts support

Hello there,
Thanks for making this PR. I was gonna add TypeScript support soon, but pretty cool anyways
However, there are a few problems with this PR:

Why was package-lock.json replaced with yarn.lock? I mean, as cool as yarn is, I would like to stick with npm, as it is the "standard".
Is it certain that the tsconfig.json is ESM compliant?
Shouldn't the package.json's exports field be updated as well, because the dist folder has become the outDir for compiled JS files?

gradientOptions: string | {}

Gradient options is a string or array of string. It's been specified as an object in a few places though.

Other than that, it looks fine, very cool!

will fix sir

Due to lack of recent activity, I will be closing this PR.
I have decided that, on careful consideration, that this library will continue to be JS only with a .d.ts file for TS support. I personally believe that full TypeScript support should only be give to libraries that are “big enough” and truly require it (eg: date-fns). I feel this project is comparatively tiny and doesn't need a full TS support, so yeah, I will not be merging it. Oh, and also that are a lot of things to be considered while migrating a project to TypeScript (see above comment).
Thank you so much for taking an interest in this repository and trying to contribute.


Q: How do you ensure the HEC token value is obfuscated?

This is a question, not a bug report. I was hoping you could explain the way you've (I THINK) used Kubernetes Secrets to obfuscate the HEC token, because I'm having trouble understanding how it's meant to work. Details below:
###############
I am concerned that, after the Splunk HEC token is passed to this Helm chart via the splunk.hec.token value, the HEC token will be visible (in plaintext) to anyone who runs helm get values <CHART_NAME>. Initially, I assumed that you solved this problem using a Kubernetes Secret but, now that I examine your code, I don't understand what it's accomplishing, or how it's meant to work.
As far as I can tell, these are the steps being performed in this Helm chart:

Take in HEC token via Helm value named splunk.hec.token (link)
Create a Kubernetes secret to store that token, named splunk_hec_token (link)
Create an environment variable to store that token, named SPLUNK_HEC_TOKEN (link)
Subsequently, whenever you need to use the HEC token, you reference the SPLUNK_HEC_TOKEN environment variable (link)

What's confusing me about this approach to obfuscating the HEC token is:

Isn't the original Helm value containing the HEC token (splunk.hec.token) still visible in plaintext to anyone who runs helm get values <CHART_NAME>?
If the splunk.hec.token Helm value is still visible in plaintext, then what is the point of creating the Kubernetes Secret and environment variable?
In other words, if we're not actually being more secure -- if we're not actually obfuscating the HEC token contained within the splunk.hec.token Helm value -- then why even bother creating the Kubernetes Secret and environment variable? What is it actually accomplishing here?

to anyone who runs helm get values <CHART_NAME>

The helm state is stored as Kubernetes Secret too. Only someone with rights to retrieve the Secret is able to access the the Helm values. So helm get values <chart-name> can only be run by somebody that is permissioned to access Secrets on that namespace anyway.

@vinzent Interesting, I hadn't heard of that. But then, if that's true, that leads back to my original question: Why bother creating a Kubernetes secret at all?
If a Helm value is really just as secure as a Kubernetes secret, why not just directly reference the Helm value in the Fluentd config -- why go to all the trouble of creating a Kubernetes secret based off of the Helm value, and then an env variable based off of the Kubernetes secret??

The helm value can't be read by fluentd because the fluentd config file format ist not helm values. The helm state stored in the secret is for Helm to know the state. But this is really a Helm topic, not splunk-connect.
But anyway, fluentd by default spits out its complete config on startup including the HEC token. Actually anybody with access to the logs of the pod has access to the HEC credential tool.

@vinzent Ah, I think I get it now -- the reason you create the Kubernetes secret + env variable is to get it into a form (env variable) that can be consumed by Fluentd without revealing its value (HEC token) in plaintext when Fluentd dumps its config on startup (I'm assuming here that Fluentd does not print out the actual value of env variables in its config).
In other words, although we could directly reference the Helm value in the Fluentd config (although Fluentd doesn't directly consume (or know about) Helm values, Helm will substitute the value beforehand so that, from Fluentd's perspective, it's as if you hardcoded the Helm value (HEC token) in plaintext in the config -- see example here), the HEC token would now be printed in plaintext when Fluentd dumps its config on startup.
Thanks for explaining! Assuming I understood you correctly, feel free to close this ticket.

Thank you @vinzent for your explanation! closing


Python: add XLEN command

Issue #, if available:
N/A
Description of changes:
https://redis.io/docs/latest/commands/xlen/
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

LGTM, just wondering if there should also be a test calling XLEN after XDEL.

Good question, I think the equivalent is already tested with XTRIM. We are using XTRIM to delete entries in the stream and then calling XLEN against the stream key. XDEL also deletes entries in the stream, rather than the stream itself. So both commands delete entries in the stream


🌐 Add Traditional Chinese translation for docs/zh-hant/docs/tutorial/query-param-models.md

Add Traditional Chinese translation for query-param-models.md
為 query-param-models（查詢參數模型）一章加入翻譯

Hello😉, this pull request is marked incorrectly. This is a traditional Chinese (zh-hant) translation.
Most Chinese people can understand both simplified Chinese and traditional Chinese, so I have translated both of them. But due to some differences in wording, this still needs to be checked by native speakers.

done. @mattwang44

Thanks for your work! @Vincy1230 :rocket:
And thanks for the review @mattwang44 :mag:


Can't connect to MSK Broker using kafkaJS

For IAM I followed the following steps, and not able to connect. Error is still saying "Closed Connection"

Made the IAM user named kafka-user
Created role with MSKFullAccess policy and gave that role to user
for that user created access keys
made an inbound rule in the security group for allowing All traffic

Using following code:
this.kafka = new Kafka({
      clientId: 'user_service', // Replace with your desired client ID
      brokers: ['KAFKA_BROKER_ADDRESS'],
      sasl: {
        mechanism: 'aws',
        authorizationIdentity: 'kafka-user', // UserId or RoleId
        accessKeyId: 'ACCESS_KEY',
        secretAccessKey: 'ACCESS_SECRET',
        // sessionToken: '' // Optional
      },
    });

I commented the sessionToken as it is optional and I do not know how to get it.
Error:
{"level":"ERROR","timestamp":"2023-11-23T11:43:55.513Z","logger":"kafkajs","message":"[BrokerPool] Closed connection","retryCount":5,"retryTime":6586}
node:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^

KafkaJSNonRetriableError
  Caused by: KafkaJSConnectionClosedError: Closed connection

Hello.
It is propably too late, but try this.

Hi @akospaska ,
Thank you for your reply, I used this module @jm18457/kafkajs-msk-iam-authentication-mechanism with kafkajs library. According to a blog on aws repost https://repost.aws/knowledge-center/msk-cluster-connection-issues, kafkajs iam is slightly different from what aws actually uses so previously mentioned module will work fine and its working flawlessly.


[SPARK-38867][SQL] Avoid OOM when bufferedPlan has a lot of duplicate keys in SortMergeJoin codegen

What changes were proposed in this pull request?
WholeStageCodegenExec is wrapped in BufferedRowIterator.
BufferedRowIterator uses a LinkedList to hold the output of WholeStageCodegenExec.
When the parent of SortMergeJoin cannot codegen, SortMergeJoin needs to append the output to this LinkedList.
SortMergeJoin processes a record in streamedPlan each time. If all records in bufferedPlan can match this record, all records in bufferedPlan will be saved in LinkedList, resulting in OOM.
The above situation is very common in our internal use, so it is best to add a configuration to the codegen code. If there are enough items in the LinkedList, stop SortMergeJoin and let the parent consume it first.
Why are the changes needed?
Enhanced stability to avoid OOM interfering with users
Does this PR introduce any user-facing change?
yes, added a configuration spark.sql.sortMergeJoinExec.codegen.maxRecordPerCycle to ensure that the LinkedList length does not exceed the configuration value.
How was this patch tested?
pass all current tests.

Can one of the admins verify this patch?

CI link: https://github.com/mcdull-zhang/spark/actions/runs/2171269127

cc @cloud-fan

Can we run some benchmarks to evaluate the perf impact? This adds a breakpoint to the SMJ workflow which may slow down the join processing.

cc @maryannxue

Encountered the same problem in production, but I simply added a configuration to disable codegen for SMJ.

Can we run some benchmarks to evaluate the perf impact? This adds a breakpoint to the SMJ workflow which may slow down the join processing.

The benchmark test has been updated to the description of pr. Could you please take a look at this?


[storage][hotfix] - Update storage blob to core-tracing preview 13

Now that @opentelemetry/api has gone GA, we have more users attempting to try it. The latest stable releases for storage packages still use an older version of @azure/core-tracing that depends on 1.0.0-rc version of @opentelemetry/api. This results in problems like the one seen in #16447
Moreover, our recent move to use 2.0.0 of @azure/core-http in @azure/identity results in different versions of core-http being used in cases like #16389 and failing builds even when the user does not use tracing.
We were hoping that the next storage updates would resolve this as we have already done the work to move to the latest tracing packages in the main branch, but unfortunately the storage packages in the main branch are looking at a beta release
To resolve such issues in the near term, we would like to have a stable release out for the storage packages that uses the latest @azure/core-tracing package. This PR updates storage packages to a version of core-tracing that depends on OTel ^1.0.0 and will be merged into hotfix/storage-opentelemetry-ga

PR from fork of this branch has succeeded. Overriding check-enforcer to get this PR merged to unblock storage hotfix release. https://github.com/Azure/azure-sdk-for-js/pull/16549

/check-enforcer override

To add additional context on why this was safe to override:

The name of the source branch started with the hotfix/ prefix which triggered internal pipelines. Examining the failures showed a few APIView changes against an incorrect version in unrelated packages and 404 invalid links due to this branch being stale (and also in unrelated packages). Neither of these would have triggered had the source branch not been named hotfix/
In addition, while validating that the hotfix prefix was the problem, we created another branch in a fork and pushed it up without changing the latest commit. This caused Azure DevOps to consider the two PRs equivalent and added duplicate checks here (the ones who were canceled)

These were examined by JS and the EngSys team and were deemed false positives. We will take away improvement ideas but these should not block the storage releases (as storage passed). Also, see the green build which ran successfully in our fork
We are good to release:

@azure/storage-blob
@azure/storage-file-datalake
@azure/storage-file-share
@azure/storage-queue


Implement --exclude or --skip-hidden ?

Not sure we need this.
Plus, what should we do with skipped files that may be left behind at the end of the transfer in case we are moving things ?

or maybe only pycp should accept the --exclude flag.


Can't buy masks or masks parts with goonmod shop standalone

Not sure if it's possible to make it compatible due to how the function is setup
If you want to can integrate into the mod

Sure, I'll take a look. Thanks!

Fixed.


add RSS functionality

here an additional feature request with low priority:
add an rss function to the mission list so that user get informed if there is a new mission

Could be done via rss-package, but would most likely require some sort of caching combined with re-generation every X minutes.
Will take it into consideration, thanks for the suggestion!

Unfortunately, this cannot be added for user-specific missions unless some sort of "access token" authentication has been added. Simply providing a list of publicly visible missions (like an unauthenticated user would see) would be easier to provide, but obviously not complete.
The JWTs generated for user signup are not suitable for usage in e.g. a RSS reader, so a token provided via the URL would be of need.
If functionality is added to access all missions visible to a certain user, there must also be a place to revoke those tokens in case they have been shared by accident.


Error Message v2.6.0

See https://git.io/JtMGR for more info.
[06/03/2021, 15:59:50] [homebridge-mieleathome] This plugin generated a warning from the characteristic 'Remaining Duration': characteristic was supplied illegal value: number 3840 exceeded maximum of 3600. See https://git.io/JtMGR for more info.
[06/03/2021, 16:00:50] [homebridge-mieleathome] This plugin generated a warning from the characteristic 'Remaining Duration': characteristic was supplied illegal value: number 3780 exceeded maximum of 3600. See https://git.io/JtMGR for more info.
[06/03/2021, 16:01:50] [homebridge-mieleathome] This plugin generated a warning from the characteristic 'Remaining Duration': characteristic was supplied illegal value: number 3720 exceeded maximum of 3600. See https://git.io/JtMGR for more info.
[06/03/2021, 16:02:50] [homebridge-mieleathome] This plugin generated a warning from the characteristic 'Remaining Duration': characteristic was supplied illegal value: number 3660 exceeded maximum of 3600. See https://git.io/JtMGR for more info.

Thanks, yes very unfortunately HomeKit only supports at most 3600s. I used to jus push the Miele number and let HomeKit limit the value in hopes that HomeKit will once support more than 1h, but since Homebridge itself now became more strict itself...

:tada: This issue has been resolved in version 2.7.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Start fails since yesterday because of hap-nodejs

Error is cannot find module curve25519-n.

Please make sure you updated both homebridge and hap-nodejs.
Sent from my iPhone

On Apr 9, 2017, at 2:08 AM, Markus Krüger<EMAIL_ADDRESS>wrote:
Error is cannot find module curve25519-n.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I think npm has issue with updating dependencies when you update a package.
Sent from my iPhone

On Apr 9, 2017, at 11:25 AM, Markus Krüger<EMAIL_ADDRESS>wrote:
Shouldnt this be handled via homebridges dependencies? I am not that firm with this.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Ok, works now when updating hap-nodejs before updating homebridge (using a docker image).


Issue with re-installing Larch on Mac OSX

Hello again,
Had to uninstall and re-install Anaconda Navigator as I had some issues. Now when trying to run my code in Spyder as before, I get the following error regarding the Larch package:
  File ~/anaconda3/lib/python3.11/site-packages/larch/__init__.py:1
    raise ImportError("larch cannot be installed with pip, try installing using conda-forge instead.\nSee https://larch.newman.me/getting-started.html for instructions.")

ImportError: larch cannot be installed with pip, try installing using conda-forge instead.
See https://larch.newman.me/getting-started.html for instructions.

Probably an easy fix but I can't work it out. Any assistance appreciated!

@Ayrtonb1 Not sure what you did.  Can you do (from a Terminal):
  ~/anaconda3/bin/python -m pip install xraylarch

Hi Matt,
Thanks for getting back so quickly. For some reason I am getting this error in terminal after a short while:
` Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... error
error: subprocess-exited-with-error
× Preparing metadata (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [17 lines of output]
+ meson setup /private/var/folders/98/2v6x4hv55wjcswn19y_blzlh0000gn/T/pip-install-9q3oh0a9/pyfai_2689474bc8f44615abf8be8ffddd387e /private/var/folders/98/2v6x4hv55wjcswn19y_blzlh0000gn/T/pip-install-9q3oh0a9/pyfai_2689474bc8f44615abf8be8ffddd387e/.mesonpy-6tm_wrhm -Dbuildtype=release -Db_ndebug=if-release -Db_vscrt=md --native-file=/private/var/folders/98/2v6x4hv55wjcswn19y_blzlh0000gn/T/pip-install-9q3oh0a9/pyfai_2689474bc8f44615abf8be8ffddd387e/.mesonpy-6tm_wrhm/meson-python-native-file.ini
The Meson build system
Version: 1.2.1
Source dir: /private/var/folders/98/2v6x4hv55wjcswn19y_blzlh0000gn/T/pip-install-9q3oh0a9/pyfai_2689474bc8f44615abf8be8ffddd387e
Build dir: /private/var/folders/98/2v6x4hv55wjcswn19y_blzlh0000gn/T/pip-install-9q3oh0a9/pyfai_2689474bc8f44615abf8be8ffddd387e/.mesonpy-6tm_wrhm
Build type: native build
Project name: pyFAI
Project version: 2023.9.0
  ../meson.build:1:0: ERROR: Unknown compiler(s): [['cc'], ['gcc'], ['clang'], ['nvc'], ['pgcc'], ['icc'], ['icx']]
  The following exception(s) were encountered:
  Running `nvc --version` gave "[Errno 2] No such file or directory: 'nvc'"
  Running `pgcc --version` gave "[Errno 2] No such file or directory: 'pgcc'"
  Running `icc --version` gave "[Errno 2] No such file or directory: 'icc'"
  Running `icx --version` gave "[Errno 2] No such file or directory: 'icx'"

  A full log can be found at /private/var/folders/98/2v6x4hv55wjcswn19y_blzlh0000gn/T/pip-install-9q3oh0a9/pyfai_2689474bc8f44615abf8be8ffddd387e/.mesonpy-6tm_wrhm/meson-logs/meson-log.txt
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
`
No clue what's going on. Any ideas? I did try to install larch using the Spyder built-in Kernel and pip - maybe this is where the issue is coming from somehow?

Hi Matt, Thanks for this message. I have been spending some time trying to get around this error, however I cannot seem to install pyFAI and wind up with the same error described above, I.E.
Preparing metadata (pyproject.toml) ... error   error: subprocess-exited-with-error
I've looked online and tried to find ways around it such as using a virtual environment, or by bypassing the cache, as well as some others, but cannot seem to solve this error for pyFAI and therefore for xraylarch installation. I am not very famliar with using terminal. Do you have any further suggestions that may help?

@Ayrtonb1 The error you are getting is again incomplete and deliberately truncated.  I have asked you a couple of times to explain exactly what you did and give complete error messages.  You say that the error you are getting comes from installing pyFAI (not from xraylarch)  into your own Python environment, but I actually do not have any idea what you did.
Now, installing xraylarch into your own Python environment can definitely be done.  Many people do this.  I can try to help with such situations: we want that to work well.  But in order to be able to support such cases, you absolutely must give complete information about what you are doing and give full error messages.   You have kind of consistently and repeatedly not done this.
At this point, I recommend that you install Larch with the GetLarch.sh script (https://raw.githubusercontent.com/xraypy/xraylarch/master/installers/GetLarch.sh) and then assessing why you want to run xraylarch from your other Python environment.

Hi Matt,
Apologies for my lack of clarity on the matter. Due to my inexperience with using Terminal I wanted to avoid overcomplicating the issue with too much code-related jargon if it was indeed a common problem with a simple solve. In future I will include full error messages.
To be clear, I am just trying to install xraylarch as you have suggested in the terminal on Mac OSX using
 ~/anaconda3/bin/python -m pip install xraylarch
However I get the error message as described above:
`Collecting xraylarch
Obtaining dependency information for xraylarch from https://files.pythonhosted.org/packages/8c/e0/c75296da0801d3302b5068fa68d5d9783aacfa867958a08b95c5a668c762/xraylarch-0.9.71-py3-none-any.whl.metadata
Using cached xraylarch-0.9.71-py3-none-any.whl.metadata (1.6 kB)
Requirement already satisfied: packaging in ./anaconda3/lib/python3.11/site-packages (from xraylarch) (23.0)
Requirement already satisfied: pip in ./anaconda3/lib/python3.11/site-packages (from xraylarch) (23.2.1)
Requirement already satisfied: pyyaml in ./anaconda3/lib/python3.11/site-packages (from xraylarch) (6.0)
Requirement already satisfied: toml in ./anaconda3/lib/python3.11/site-packages (from xraylarch) (0.10.2)
Requirement already satisfied: pytest in ./anaconda3/lib/python3.11/site-packages (from xraylarch) (7.4.0)
Collecting termcolor (from xraylarch)
Using cached termcolor-2.3.0-py3-none-any.whl (6.9 kB)
Requirement already satisfied: scipy>=1.7 in ./anaconda3/lib/python3.11/site-packages (from xraylarch) (1.10.1)
Requirement already satisfied: numpy>=1.20 in ./anaconda3/lib/python3.11/site-packages (from xraylarch) (1.24.3)
Requirement already satisfied: matplotlib>=3.5 in ./anaconda3/lib/python3.11/site-packages (from xraylarch) (3.7.1)
Collecting sqlalchemy>=2.0 (from xraylarch)
Obtaining dependency information for sqlalchemy>=2.0 from https://files.pythonhosted.org/packages/49/ba/dfb0ce41f7e1dc9e1d816c8f538bbd95b0e2632175c3a5702532eb1813a7/SQLAlchemy-2.0.21-cp311-cp311-macosx_10_9_x86_64.whl.metadata
Using cached SQLAlchemy-2.0.21-cp311-cp311-macosx_10_9_x86_64.whl.metadata (9.4 kB)
Collecting sqlalchemy-utils (from xraylarch)
Using cached SQLAlchemy_Utils-0.41.1-py3-none-any.whl (92 kB)
Requirement already satisfied: h5py>=3.2 in ./anaconda3/lib/python3.11/site-packages (from xraylarch) (3.7.0)
Requirement already satisfied: pillow>=8.3.2 in ./anaconda3/lib/python3.11/site-packages (from xraylarch) (9.4.0)
Collecting psycopg2-binary (from xraylarch)
Obtaining dependency information for psycopg2-binary from https://files.pythonhosted.org/packages/37/e6/7dd26ba148a02b7e78471ed7ce177e9890167994c5a1d4182361b9bee4cc/psycopg2_binary-2.9.7-cp311-cp311-macosx_10_9_x86_64.whl.metadata
Using cached psycopg2_binary-2.9.7-cp311-cp311-macosx_10_9_x86_64.whl.metadata (4.4 kB)
Requirement already satisfied: dill in ./anaconda3/lib/python3.11/site-packages (from xraylarch) (0.3.6)
Requirement already satisfied: imageio in ./anaconda3/lib/python3.11/site-packages (from xraylarch) (2.31.1)
Requirement already satisfied: charset-normalizer in ./anaconda3/lib/python3.11/site-packages (from xraylarch) (2.0.4)
Collecting peakutils (from xraylarch)
Using cached PeakUtils-1.3.4-py3-none-any.whl (7.7 kB)
Requirement already satisfied: requests in ./anaconda3/lib/python3.11/site-packages (from xraylarch) (2.31.0)
Requirement already satisfied: scikit-image in ./anaconda3/lib/python3.11/site-packages (from xraylarch) (0.20.0)
Requirement already satisfied: scikit-learn in ./anaconda3/lib/python3.11/site-packages (from xraylarch) (1.3.0)
Collecting asteval>=0.9.28 (from xraylarch)
Obtaining dependency information for asteval>=0.9.28 from https://files.pythonhosted.org/packages/05/34/bdb51767967cb29302ee7dfe95662b057af7f23c62dd1967fc4b373656aa/asteval-0.9.31-py3-none-any.whl.metadata
Using cached asteval-0.9.31-py3-none-any.whl.metadata (2.0 kB)
Collecting lmfit>=1.2.0 (from xraylarch)
Obtaining dependency information for lmfit>=1.2.0 from https://files.pythonhosted.org/packages/16/87/d1b01fa4e4b69e0dea803592af88608c1c22eb4f92bfccf83ac66fa0792f/lmfit-1.2.2-py3-none-any.whl.metadata
Using cached lmfit-1.2.2-py3-none-any.whl.metadata (9.9 kB)
Collecting uncertainties>=3.1 (from xraylarch)
Using cached uncertainties-3.1.7-py2.py3-none-any.whl (98 kB)
Collecting pyshortcuts>=1.9.0 (from xraylarch)
Using cached pyshortcuts-1.9.0-py3-none-any.whl (158 kB)
Collecting xraydb>=4.5 (from xraylarch)
Obtaining dependency information for xraydb>=4.5 from https://files.pythonhosted.org/packages/70/f5/1bfd9dee2f4465c7ae4da968ef4afbf0793619e7fe833dd7a951fe0d8a51/xraydb-4.5.1-py3-none-any.whl.metadata
Using cached xraydb-4.5.1-py3-none-any.whl.metadata (1.6 kB)
Collecting silx>=0.15.2 (from xraylarch)
Using cached silx-1.1.2-cp311-cp311-macosx_10_9_universal2.whl (6.6 MB)
Collecting hdf5plugin (from xraylarch)
Obtaining dependency information for hdf5plugin from https://files.pythonhosted.org/packages/2d/76/d25e6aa8b74bc9545a9a1d3b981e7089dc2eee927cc0272b2e0f891e9a91/hdf5plugin-4.2.0-py3-none-macosx_10_9_universal2.whl.metadata
Using cached hdf5plugin-4.2.0-py3-none-macosx_10_9_universal2.whl.metadata (2.8 kB)
Collecting numdifftools (from xraylarch)
Using cached numdifftools-0.9.41-py2.py3-none-any.whl (100 kB)
Requirement already satisfied: psutil in ./anaconda3/lib/python3.11/site-packages (from xraylarch) (5.9.0)
Collecting pymatgen (from xraylarch)
Obtaining dependency information for pymatgen from https://files.pythonhosted.org/packages/94/25/54a0da147ead5d0f75a8695ad7c94d693344226464ae49113ce9c828381d/pymatgen-2023.9.25-cp311-cp311-macosx_10_9_x86_64.whl.metadata
Downloading pymatgen-2023.9.25-cp311-cp311-macosx_10_9_x86_64.whl.metadata (12 kB)
Collecting fabio (from xraylarch)
Obtaining dependency information for fabio from https://files.pythonhosted.org/packages/e3/c9/a7288b7eb8e4fb4076d470ac9936e23946b250de9342806403af4a62bdca/fabio-2023.6.0-cp311-cp311-macosx_10_15_x86_64.whl.metadata
Using cached fabio-2023.6.0-cp311-cp311-macosx_10_15_x86_64.whl.metadata (15 kB)
Collecting pyfai (from xraylarch)
Using cached pyfai-2023.9.0.tar.gz (54.8 MB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... error
error: subprocess-exited-with-error
× Preparing metadata (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [17 lines of output]
+ meson setup /private/var/folders/98/2v6x4hv55wjcswn19y_blzlh0000gn/T/pip-install-1cu81rhl/pyfai_483e8a60313748c7be4d26874ea2a2fb /private/var/folders/98/2v6x4hv55wjcswn19y_blzlh0000gn/T/pip-install-1cu81rhl/pyfai_483e8a60313748c7be4d26874ea2a2fb/.mesonpy-gz3i__8v -Dbuildtype=release -Db_ndebug=if-release -Db_vscrt=md --native-file=/private/var/folders/98/2v6x4hv55wjcswn19y_blzlh0000gn/T/pip-install-1cu81rhl/pyfai_483e8a60313748c7be4d26874ea2a2fb/.mesonpy-gz3i__8v/meson-python-native-file.ini
The Meson build system
Version: 1.2.1
Source dir: /private/var/folders/98/2v6x4hv55wjcswn19y_blzlh0000gn/T/pip-install-1cu81rhl/pyfai_483e8a60313748c7be4d26874ea2a2fb
Build dir: /private/var/folders/98/2v6x4hv55wjcswn19y_blzlh0000gn/T/pip-install-1cu81rhl/pyfai_483e8a60313748c7be4d26874ea2a2fb/.mesonpy-gz3i__8v
Build type: native build
Project name: pyFAI
Project version: 2023.9.0
  ../meson.build:1:0: ERROR: Unknown compiler(s): [['cc'], ['gcc'], ['clang'], ['nvc'], ['pgcc'], ['icc'], ['icx']]
  The following exception(s) were encountered:
  Running `nvc --version` gave "[Errno 2] No such file or directory: 'nvc'"
  Running `pgcc --version` gave "[Errno 2] No such file or directory: 'pgcc'"
  Running `icc --version` gave "[Errno 2] No such file or directory: 'icc'"
  Running `icx --version` gave "[Errno 2] No such file or directory: 'icx'"

  A full log can be found at /private/var/folders/98/2v6x4hv55wjcswn19y_blzlh0000gn/T/pip-install-1cu81rhl/pyfai_483e8a60313748c7be4d26874ea2a2fb/.mesonpy-gz3i__8v/meson-logs/meson-log.txt
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.`
Then, I have tried to install pyFAI separately as it seems xraylarch is experiencing an installation issue as a result of pyFAI as you said. However, I can't install this either. I am using the command
pip install pyFAI
I have also tried solving the problem by ignoring the cache, using:
pip install --no-cache-dir pyFAI
or by alternatively using:
pip install pyFAI --use-deprecated=legacy-resolver
I have also tried using conda:
conda install pyfai -c conda-forge
I have also tried using a virtual environment before attempting installation, as in:
python -m venv venv source venv/bin/activate
and have tried updating the pip package by:
pip install wheel setuptools pip --upgrade
These are most of the things I have tried, and have. tried replacing pyFAI with xraylarch in the above commands. However, in these above cases I still get the same error message for both pyFAI and for xraylarch, I.E.:
`Collecting pyFAI
Downloading pyfai-2023.9.0.tar.gz (54.8 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 54.8/54.8 MB 23.4 MB/s eta 0:00:00
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... error
error: subprocess-exited-with-error
× Preparing metadata (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [17 lines of output]
+ meson setup /private/var/folders/98/2v6x4hv55wjcswn19y_blzlh0000gn/T/pip-install-8r63qrl1/pyfai_72a71cc4b54a4e62a024db586ef8f83e /private/var/folders/98/2v6x4hv55wjcswn19y_blzlh0000gn/T/pip-install-8r63qrl1/pyfai_72a71cc4b54a4e62a024db586ef8f83e/.mesonpy-3qw2muqo -Dbuildtype=release -Db_ndebug=if-release -Db_vscrt=md --native-file=/private/var/folders/98/2v6x4hv55wjcswn19y_blzlh0000gn/T/pip-install-8r63qrl1/pyfai_72a71cc4b54a4e62a024db586ef8f83e/.mesonpy-3qw2muqo/meson-python-native-file.ini
The Meson build system
Version: 1.2.2
Source dir: /private/var/folders/98/2v6x4hv55wjcswn19y_blzlh0000gn/T/pip-install-8r63qrl1/pyfai_72a71cc4b54a4e62a024db586ef8f83e
Build dir: /private/var/folders/98/2v6x4hv55wjcswn19y_blzlh0000gn/T/pip-install-8r63qrl1/pyfai_72a71cc4b54a4e62a024db586ef8f83e/.mesonpy-3qw2muqo
Build type: native build
Project name: pyFAI
Project version: 2023.9.0
  ../meson.build:1:0: ERROR: Unknown compiler(s): [['cc'], ['gcc'], ['clang'], ['nvc'], ['pgcc'], ['icc'], ['icx']]
  The following exception(s) were encountered:
  Running `nvc --version` gave "[Errno 2] No such file or directory: 'nvc'"
  Running `pgcc --version` gave "[Errno 2] No such file or directory: 'pgcc'"
  Running `icc --version` gave "[Errno 2] No such file or directory: 'icc'"
  Running `icx --version` gave "[Errno 2] No such file or directory: 'icx'"

  A full log can be found at /private/var/folders/98/2v6x4hv55wjcswn19y_blzlh0000gn/T/pip-install-8r63qrl1/pyfai_72a71cc4b54a4e62a024db586ef8f83e/.mesonpy-3qw2muqo/meson-logs/meson-log.txt
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
`
Apologies, I am not sure how to use the .sh github link you sent as an alternative, either, and I can't find any further resources online about how to resolve this error. Are you able to help? Apologies if this is the wrong place for this issue. Hopefully I have included enough information about what I have been trying. Any help is appreciated! Thank you again

Hi Matt, Thanks for your reply. The reason I'm describing my troubles installing pyFAI is because that is where my issues with installing xraylarch arise from. I can't seem to find a forum to discuss issues about pyFAI directly but seeing as I am actually just trying to reinstall xraylarch (as far as I know I am trying this in the normal, documented, supported way, that being the method you suggested earlier - please correct me if I am wrong) I figured here would be a good place to start. I am using conda 23.7.4  and Python 3.11.5  which I believe to be the most up-to-date versions.
I am using terminal to try and download this, as opposed to a custom python environment, and that is where the issue with installing xraylarch arises. Is there any other further information I can provide that may help get to the bottom of this?

Hi Matt,
I think I managed to install after having a call with a friend more knowledgeable about these things than myself. However, I am still getting this error when I try to run my script in Python using Spyder:
`Traceback (most recent call last):
File ~/anaconda3/lib/python3.11/site-packages/spyder_kernels/py3compat.py:356 in compat_exec
exec(code, globals, locals)
File ~/PycharmProjects/beamtime_10_9_22/DAFS_GUI.py:24
from larch.xafs import diffkk
ModuleNotFoundError: No module named 'larch'`
Am I calling this correctly? Or should I be calling larch a different way? Thanks again

@Ayrtonb1   Again you said you did a bunch of stuff and want my help and deliberately decided to not tell me exactly what you did.  Like, did you run pip install xraylarch?
Why are you not running Larch from the supported installer?
I am working today on a new release of Larch (0.9.72) and new installer scripts for Windows and MacOS.   These will be the supported environments. I strongly encourage you to install use Larch using these installers.
Larch is open source and you can choose to run Larch in a different Python environment.  In fact, several people do this.  I try to help those who want to do this, but that assumes that they have some familiarity with Python, know how to install packages, and can communicate effectively about issues they are having.


Homepage: unable to create content list based on a tags

Hi @rdunk -- we discussed this a while ago. A content list based on a specific tag will be really helpful in homepage listings.
Missing add by 'tag':

This one is ready to go, just need to confirm whether you want an AND or OR implementation for multiple tags.
AND: Content returned must have all of the selected tags.
OR: Content returned will have one or more of the selected tags.

@rdunk -- is it possible to have both options?
If not, the second option, "Content returned will have one or more of the selected tags" would be preferable.

Implemented both with a toggle to choose the preferred option.
Also added an example (currently hidden) as the last element for you to check out, feel free to delete it.


error ssL certificate

After update monolog to version: 1.14.0

Error in exception handler: Curl error (code 60): SSL certificate problem: self signed certificate in certificate chain in C:\xampp\htdocs\imob-io\vendor\monolog\monolog\src\Monolog\Handler\LogglyHandler.php:96

Since 56dcd1a668a60b2c25df2dd078e1745d890ca60d, the handler throws an exception when the curl_exec() call fails. It looks like the handler didn't work for you before, but you didn't notice as it fell silently.

Indeed, you might need to fix your curl.cafile setting in php.ini, make sure you have an up to date ca file


Knife cookbook upload ignores chef-server port number specified in knife.rb

Description
As a result of various 'security' requirements on my current chef deployment I have to tunnel knife traffic from my knife client machine to chef server. I have this value set in my knife.rb:
server: "https://localhost:8890/organizations/my-org"
This works fine, up until using knife cookbook upload
$ knife cookbook upload --verbose <cookbook>
INFO: Using configuration from /Users/matalo33/.chef/knife.rb
Uploading <cookbook> [<version>]
INFO: Validating ruby files
INFO: Validating templates
INFO: Syntax OK
INFO: Saving <cookbook>
INFO: Uploading files
ERROR: Connection refused connecting to https://localhost/bookshelf/organization-<hash>/checksum-<hash>?AWSAccessKeyId=<aws-key>&Expires=1485434250&Signature=<sig>, retry 1/5

knife cookbook upload drops the port 8890 specified in my config and tried to use port 443. If I set up a new tunnel forwarding port 443, without changing any knife config, the upload is successful.
Chef Version
12.12.15
Platform Version
macOS Sierra 10.12.2
Replication Case

Specify a custom port number in server: in knife.rb
For testing this can be a locally forwarded port through SSH
ssh -L 8890:<chef-server>:443 user@host
Observe that knife functions as expected
Try knife cookbook upload and notice it disregards the port in knife.rb and connects directly via port 443

Unfortunately this isn't something Chef really supports. This isn't an issue in Chef itself, but with the protocol from Chef Server. The URL file uploads is sent from the server not read from the confit file. As such there can be only a single canonical name use there. You can change it by setting the bookshelf URL and VIP setting in your Chef Server config.

Interesting to know. But doesn't explain why the error that I get back from knife is not in the attempt to get to the actual chef server URL but to the localhost URL (that I configured in the knife.rb) only missing the port:
ERROR: Connection refused connecting to https://<IP_ADDRESS>/organizations/orgname/env/c054828f422965664e2b30df1b866aaf, retry 1/5
ERROR: Connection refused connecting to https://<IP_ADDRESS>/organizations/orgname/env/c054828f422965664e2b30df1b866aaf, retry 2/5
...
...
If what you say is correct I should see something like this instead:
ERROR: Connection refused connecting to https://server_url/organizations/orgname/...

I've had the same issue with "knife cookbook upload" - all other knife commands follow the chef server url specified in the knife.rb config file but "knife cookbook upload" doesn't follow this configuration.
I agree with @andreazorzetto in that it doesn't make sense for the chef server to give you the URL to upload the cookbook. This is a local command pushing cookbooks to the server rather than the server pulling from your remote machine.


[MINOR][PYTHON][DOCS] Fix docstring for pyspark.sql.DataFrameWriter.json lineSep param

What changes were proposed in this pull request?
Add a new line to the lineSep parameter so that the doc renders correctly.
Why are the changes needed?

The first line of the description is part of the signature and is bolded.
Does this PR introduce any user-facing change?
Yes, it changes how the docs for pyspark.sql.DataFrameWriter.json are rendered.
How was this patch tested?
I didn't test it; I don't have the doc rendering tool chain on my machine, but the change is obvious.

Can one of the admins verify this patch?

Thanks @AlexMooney.
Jenkins, ok to test

Test build #137320 has started for PR 32153 at commit 5969741.

Test build #137320 has finished for PR 32153 at commit 5969741.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged to master and branch-3.1

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41900/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/137320/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/41900/

Can one of the admins verify this patch?


Clickhouse fails to import CSV from postgres pipe

Description
CH fails to import CSV data. Maybe a parser error or something similar.
Reproduction

CH version: <IP_ADDRESS>
CH:
create table crash_test (x String, y String, z String) engine = Log();
PostgreSQL:
create table crash_test (x text, y text, z text);
insert into crash_test values ('1st', '''2nd', '3rd');
COPY (select * from crash_test) TO PROGRAM 'clickhouse-client --query="INSERT INTO crash_test FORMAT CSV"' delimiter ',' CSV;

Expected behavior
Correct import of string with apostrophe to clickhouse and if not, message in the clickhouse-server.err.log (now it's completely silent on the clickhouse side).
Message in postgresql console after command
[2019-04-29 15:26:30] [38000] ERROR: program failed "clickhouse-client --query="INSERT INTO crash_test FORMAT CSV"" [2019-04-29 15:26:30] Description: child process fail with return code 27

try force quote
COPY (select * from crash_test) TO PROGRAM 'clickhouse-client --query="INSERT INTO crash_test FORMAT CSV"' with csv force quote *;

no force quote
| => cat aaa
1st,'2nd,3rd

| => cat aaa|clickhouse-client -q 'INSERT INTO crash_test FORMAT CSV'
Code: 27. DB::Exception: Cannot parse input: expected , at end of stream.: (at row 1)

force quote

| => cat aab
"1st","'2nd","3rd"
| => cat aab|clickhouse-client -q 'INSERT INTO crash_test FORMAT CSV'

ah, another option by CH --format_csv_allow_single_quotes
cat aaa|clickhouse-client --format_csv_allow_single_quotes 0 -q 'INSERT INTO crash_test FORMAT CSV'

ah, another option by CH --format_csv_allow_single_quotes
cat aaa|clickhouse-client --format_csv_allow_single_quotes 0 -q 'INSERT INTO crash_test FORMAT CSV'

thank you, both answers fix the issue. So it's not a bug. But im not sure if other symbols can also crash parser if we escape apostrophe.

CSV parser works as expected
https://clickhouse.yandex/docs/en/interfaces/formats/#csv

Both double and single quotes are supported.

Check TSV https://clickhouse.yandex/docs/en/interfaces/formats/#tabseparated


Bitcoin private keys

Hello sir can you do this
https://github.com/miguelmota/ethereum-private-key-to-address
for Bitcoin private keys and also make it possible for users to convert a large .txt file of private keys to addresses. Thanks

Unfortunately I can't help with this request.
Closing as out of scope.


Prepare for v0.7.5

Currently with cortex-m 0.7.4 it's not possible for stable Rust users to enable the inline-asm feature, even though their compiler might support it, because of the ![cfg_attr(feature = "inline-asm", feature(asm))] line. I propose a new 0.7.5 release that removes this line, which means users on stable Rust >=1.59 could enable the previously nightly-only feature to get stable inline asm.
I wouldn't enable the feature by default, because that would be a significant MSRV bump, but at least this way more users could enable it before we release 0.8 with the revamped and inline-only asm.
I've also backported the bugfix from #380 which I don't believe is a breaking change.
I haven't had a chance to test this yet so it would be great if someone could try it out and just make sure the inline-asm feature does work before merging.
Any thoughts on anything else worth backporting from 0.8?

I've tested this and confirmed that code using one of the asm functions, when inline-asm feature is on and using release mode, gets the asm inlined directly into the call site, with a stable Rust compiler. Should be good to go!

So the only thing to be aware of is https://github.com/rust-embedded/cortex-m/issues/442 because if we get a PR for that, we'll almost certainly get a request to push it out in a new release.

Since it looks like #442 relates to cortex-m-semihosting instead, I don't think it's a blocker for this.


[lve-tools] Support for Back-and-forth-Chat

Support prompts where the LLM need to fill in multiple values, e.g.:
Q: What is 1+3?
A: [answer1]
Q: What is 3+1?
A: [answer2]

This needs an adjustment to how prompts are stored (also see compatibility with #9)  and parsed as well as support for verifiers to access to the values assigned to the individual variables (answer1 and answer2 here) as well as the full answer.

See example implementation in 9c65fc4.


Nightscout dev to master

Some images and improvements to Nightscout page instructions.
Note: don't merge until get the missing image from @Kdisimone

I also added a scratch/starting page for the "explain the board" page we've talked about needing, based on notes from Gitter. @scottleibrand please clarify specific wording on light locations, and @Kdisimone amazing pictures with arrows would be super welcome to improve this further :) https://github.com/openaps/docs/commit/540d397213b8ba8fbb472351a391c959678f1bfe


Not working on Android 4.1.2

Menu does not work that well on Android 4.1.2, I have to tap it constantly for it to open and when it does it crashes.
Any ideas.

This is going to be fixed in new version https://github.com/artberri/sidr/blob/master/CHANGELOG.md


[AVM Module Issue]: res/web/serverfarm - can we default reserved = true when customer specify kind as Linux?

Check for previous/existing GitHub issues

[X] I have checked for previous/existing GitHub issues

Issue Type?
Feature Request
Module Name
avm/res/web/serverfarm
(Optional) Module Name if not listed above
No response
(Optional) Module Version
No response
Description
Based on https://azure.github.io/AppService/2021/08/31/Kind-property-overview.html - you can set kind to “Linux” for the ASP, but that won’t make your ASP a Linux ASP; only if reserved = true, then it’s a Linux ASP. Let's help customer make the right default in the AVM module.
(Optional) Correlation Id
No response

Hi @puicchan - Thanks for logging this. We shall triage it WC 15 April when we are next scheduled for AVM Work.

@puicchan this one is all done for you. Thanks for submitting it. I will look to submit a PR for the others later this week potentially.


Support Ghost 4.0

to be honest I'm still not try ghost 4 with lebling template
maybe we can test it, so to make sure, is all feature of liebling theme works or not in ghost 4

nvm just check README, now it's working in ghost 4


Fix displaying of Codecov badge

Codecov Report

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

@@           Coverage Diff           @@
##           master       #2   +/-   ##
=======================================
  Coverage   95.34%   95.34%
=======================================
  Files           3        3
  Lines          43       43
  Branches        9        9
=======================================
  Hits           41       41
  Misses          2        2

Continue to review full report at Codecov.

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


[FEAT] add vscode eslint req.

add es lint module to required / recommended extension in the .vscode dir so that new user get this automatically as suggestion
add eslint config into vs code proj settings

this comment comes from teams just to test this will work


Added config specify url restriction pattern

This change adds request restriction based on a regex pattern. This pattern is specified in the config.
The following config would block the image requests.
{
  "restrictedUrlPattern": ".*(\\.png|\\.jpg|\\.gif|\\.webp)($|\\?)"
}

Example usage for this feature would be to block image requests since in some use cases they do not provide additional value and use up the bandwidth.
Besides that. I might be general enough to cover domain blacklisting: #489

@googlebot I signed it!

Thanks a lot for this, @EgorDm 👏


Improve User-search page

Describe the bug
Make the User-search page in sync with Project-search page. This requires the following changes:
--Add border around individual search result
--Remove the horizontal rule between results
--Center and add padding to the pagination element (to be done on both Project and User search page)

--Fix names moving on to the side of profile image

Are you working on this issue? (Yes/No)
Maybe

Hey! Can i try working on this? It's my first contribution to open source!

Hii @aayush-05 If anyone is working ? if not then  I want to take it

@manasivaraiya alloted another PR to you. @pavanjoshi914 you can work on this

ohk

I would like to work on this issue. Is anyone working on this issue??