python310Packages.localstack-ext: 2.3.2 -> 3.0.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.localstack-ext is: Extensions for LocalStack
meta.homepage for python310Packages.localstack-ext is: https://github.com/localstack/localstack
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.0.2 with grep in /nix/store/ny598irxnddf6gf1ya7iyvm23qbi11lm-python3.10-localstack-ext-3.0.2
found 3.0.2 in filename of file in /nix/store/ny598irxnddf6gf1ya7iyvm23qbi11lm-python3.10-localstack-ext-3.0.2

Rebuild report (if merged into master) (click to expand)

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath
localstack
python310Packages.localstack
python310Packages.localstack-ext
python311Packages.localstack
python311Packages.localstack-ext

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ny598irxnddf6gf1ya7iyvm23qbi11lm-python3.10-localstack-ext-3.0.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.localstack-ext https://github.com/r-ryantm/nixpkgs/archive/cb694b16669b258bb1129673906a720a5e2773b3.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/cb694b16669b258bb1129673906a720a5e2773b3#python310Packages.localstack-ext

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ny598irxnddf6gf1ya7iyvm23qbi11lm-python3.10-localstack-ext-3.0.2
ls -la /nix/store/ny598irxnddf6gf1ya7iyvm23qbi11lm-python3.10-localstack-ext-3.0.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

4 packages built:

localstack (python311Packages.localstack)
python310Packages.localstack
python310Packages.localstack-ext
python311Packages.localstack-ext

Maintainer pings
cc @jonringer for testing.

Merge conflict, please open a new PR.


Use pp-sketchlib for lineage assignment code

This updates the lineage assignment mode as follows:

Makes the Lineage fit into a model object, the same as BGMM, DBSCAN and Refine
Combine some of the main() control given that the code is now more similar between modes. The main difference is that lineage assign loops over ranks, and also outputs a combined lineage CSV (as before)
Adds save, load, plot, fit and assign methods to this
Fit gets nearest neighbours by passing the distance matrix to pp_sketchlib.sparsifyDists() with the appropriate rank, getting a sparse COO matrix in return
Assign simply gets the i, j elements of the COO matrix, which can be used to directly construct the network
Save and load store the rank in the pickle, and the sparse matrix in the npz
Plot creates a histogram of the distances for the included links

Still to do is assign query in this mode, which will:

[x] Load the sparse matrix
[x] Calculate the q v q and q v r dists as usual
[x] Add these into the sparse matrix, forming a dense section, but still as a sparse representation
[x] Reapply the rank cutoff
[x] Construct the network, but use the previous clusters to ensure names match correctly

Closes #79

In theory this is all done, but needs testing (properly)


Alignment issue resolved

Resolved alignment issue
https://github.com/user-attachments/assets/d8fa62f8-f902-49e2-900b-5cdd9fb93bf2

I have added Random text to it to make the name long it is working fine ,I have attached the screenShot

same PR code can handle long names also , if still i'm missing something please let me know.

@meisabhishekpatel sir, can you please look into it

@Ayush5071 sorry for late response I was not recieving any email until now,

can you see that 1st team's priyanshu's avatar is not perfectly aligned
like the 2nd team, same problem with 3rd team kshatriya's avatar they should be perfectly aligned like the 2nd team where the names are not too big

@Ayush5071 you are working on this or not ??

@meisabhishekpatel Can i still work ? i thought time is up for the issue. Sir, curently im travelling can't do right now i'll be free tomorrow. Sorry for inconvenience caused sir .

@Ayush5071 you can still work, also the timer is only for you to raise a PR.

@Ayush5071 you still working on it or not


Update headers so it downloads the pkpass file correctly

On my server using PHP 7 the download was getting corrupted, I've changed the headers and it works now correctly

LGTM. Thanks for helping to keep the library up to date and for the refactor!


Discord

Hey what's your discord ?

Why would you need it

Because burgerking has updated its API and your project no longer works


Adds nonprofit card

Closes part of #369

Not sure why the CI/CD check is failing. The lint runs without issue locally.


New release

I guess v2 since we removed a public extension on String?

If we haven't hit 1.x yet then all bets are off. If we've released 1 then yes this sadly has to be 2. Don't know where to check on the mobile site, sorry!

Yep, it would be v2. I can make all the changes to the code and then I'll ping you and you make the pod release?

Sounds good to me

Code and tag pushed to origin 👍

Hah, only just got round to this (sorry!) and it turns out I’m not an owner of the pod :) You need to poke<EMAIL_ADDRESS><EMAIL_ADDRESS>- and we should probably both get added as owners while he’s in there.
S

On 21 Apr 2020, at 11:06, Kerr Marin Miller<EMAIL_ADDRESS>wrote:
Code and tag pushed to origin 👍
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/design-ops/stylable-swiftui/issues/15#issuecomment-617083977, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB4FSD3BUTFG4KQEVGAXNBTRNVVZZANCNFSM4MMGXLDQ.

cool, will add it to my todo list and get onto it soon

2.0 is pushed to trunk. Overjoyed to add you both as owners, please dm me your pod trunk username and I'll see to it (pod trunk me will show you your current sessions) or see https://guides.cocoapods.org/making/getting-setup-with-trunk.html with instructions for creating one.

It’s, predictably, deanWombourne (or<EMAIL_ADDRESS><EMAIL_ADDRESS>if it insists on an email).
S

On 4 May 2020, at 16:10, Adam Hoyle<EMAIL_ADDRESS>wrote:
2.0 is pushed to trunk. Overjoyed to add you both as owners, please dm me your pod trunk username and I'll see to it (pod trunk me will show you your current sessions) or see https://guides.cocoapods.org/making/getting-setup-with-trunk.html https://guides.cocoapods.org/making/getting-setup-with-trunk.html with instructions for creating one.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/design-ops/stylable-swiftui/issues/15#issuecomment-623522143, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB4FSDY7LZYM6HCHEGK6HW3RP3LIDANCNFSM4MMGXLDQ.


Does it support messages to/from pages?

Yep! Sending messages to pages should be the same as sending them to people.
If you want to send a message as a page, that'll take a little bit more effort. You'll have to change this line:
https://github.com/AstroCB/Messenger-CLI/blob/ae614c6ecccdd035e9eb97432f2a9120ed12e91d/index.js#L113
to include the ID of the page. It'd look like this:
api.setOptions({ "logLevel": "warn", "listenEvents": true, "pageID": "YOUR_PAGE_ID" });

Perfect! Thanks 😃


Fixes for some bugs with Instagram Stories on Android

Overview
There were a couple of shortcomings when trying to share Instagram Stories on Android. base64 would not work on a file of any decent size. The flags on the intents were not set correctly, so Instagram was not able to open the image after it was sent. Stickers could only be sent if you were using forceDialog.
I've just upstreamed the changes I made at work to get Instagram Stories to work in our app.
Fixes #852
Fixes #853
Fixes #854
Fixes #855
Test Plan
There are no tests for Android currently. I have patched these changes into the app at work, and they all work as expected (for us), so I'm upstreaming them

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update config section in README.md

I recently started using fm on Linux, macOS, and Windows. The documentation in the Configuration section was not accurate for macOS and Windows but matches the documentation for os.UserConfigDir which is used by fm:

On Darwin, it returns $HOME/Library/Application Support. On Windows, it returns %AppData%.

This is great, thank you for this!


Zero-cycle transitions from dynamic to static control

To slightly expand on this:

Some of the grouping we were initially trying to have, a blocking group, a servicing group, an assert and deassert group, had to be combined together due to the time it takes to transfer between groups.

I actually think this is a super interesting problem that has implications for static/dynamic Calyx assignments. Artistically, we would like to be able to manage an AXI transaction with a control program like this:
while <more transactions to do> {
  seq {
    assert_ready;  // tell the remote side we are ready for their data
    wait_for_valid;  // wait for them to send us stuff
    par {
      do_transfer;  // actually do things the data on the bus
      deassert_ready;  // tell them to wait while we process the data
    }
  }
}

The problem is that AXI, of course, is super cycle-timing-sensitive. Remember that one of the core invariants is:

On any cycle when both ready=1 and valid=1, a transaction occurs.

So the remote side can schedule these transaction cycles back-to-back, i.e., 3 transactions can happen in exactly 3 cycles. Most saliently for us, say the remote side just keeps its valid signal high all the time and relies on us to assert/deassert ready to do transfers. Then, if we need to take some time to process a transfer, we have to be absolutely sure we only assert ready for one cycle at a time.
The problem with dynamic Calyx is that it offers no guarantees about how long it takes to go from wait_for_valid above to deassert_ready. And in practice, it actually does waste at least one cycle, meaning that the remote side sees us do two transfers when we only wanted one.
The big upshot of static Calyx is that it does offer these guarantees, so we would like to be able to just sprinkle the static everywhere get the timing we want. There is a critical problem, however: the wait_for_valid group is fundamentally dynamic. Our "dynamic islands" approach does not support sequencing a dynamic group with a static one with a zero-cycle transition latency.
So the big design question that I think this opens up is: is there some rule we can make up that would allow this kind of sequencing? That is, to allow some version of seq { a ; b } where a is dynamic and b is static where we can guarantee that b runs in the same cycle where a says it is done. It seems hard to do in general but maybe there is something we can do for restricted cases?
Originally posted by @sampsyo in https://github.com/calyxir/calyx/issues/1820#issuecomment-1866308023

That is, to allow some version of seq { a ; b } where a is dynamic and b is static where we can guarantee that b runs in the same cycle where a says it is done.

The two relevant issues here both have to do with the early-transitions flag for the dynamic compilation pass (tdcc): #662 and #621.
The high-level problem is that, in general, we cannot transition from a to b in the same cycle when generating dynamic FSMs because the done condition of b could be the same as a. However, note that this problem cannot occur if b is static because it does not have a done condition. This means that it might be possible to always guarantee that transitions from a dynamic group into a static island takes zero cycles. @calebmkim & @paili0628 anything I'm missing here?
Another question worth asking is that can transitions out of static islands be zero cycle as well? My guess is that the current answer is no because we generate a dynamic wrapper for static islands which means we adopt the 1-cycle delay in dynamic-to-dynamic transitions.

The high-level problem is that, in general, we cannot transition from a to b in the same cycle when generating dynamic FSMs because the done condition of b could be the same as a. However, note that this problem cannot occur if b is static because it does not have a done condition. This means that it might be possible to always guarantee that transitions from a dynamic group into a static island takes zero cycles. @calebmkim & @paili0628 anything I'm missing here?

Yeah, I think this is right. Although to rephrase slightly, we are technically giving b a done condition "under the hood" by adding a wrapper. We just know b's done signal won't be the same as the done signal of a, since we are the ones creating the register for the done signal.

Another question worth asking is that can transitions out of static islands be zero cycle as well? My guess is that the current answer is no because we generate a dynamic wrapper for static islands which means we adopt the 1-cycle delay in dynamic-to-dynamic transitions.

I think this goes back to the previous comment. Suppose we have seq {a; b;} but this time a is static and b is dynamic. We already know b's done condition, and we know what a's done condition will be when we compile it: so if we can guarantee they'll be different, then is it possible to do an early transition?
One thing I'm realizing is that, if we do this, maybe we should move the wrapping logic from compile-static to tdcc.

so if we can guarantee they'll be different, then is it possible to do an early transition?

This was thinking too but this is a fact about dynamic -> dynamic transitions too. It seems that maybe we can unconditionally guarantee that transitions from dynamic to static will be zero cycle which might be enough for what the YXI team needs.

One thing I'm realizing is that, if we do this, maybe we should move the wrapping logic

Yeah, this makes sense. There is a lot of optimizations here with optimizing wrapper generation and transitions that we haven't explored. I think these could be high-impact because FSMs are likely the worst offenders in terms of resource blow up.

Really good points here. To summarize, we believe it is possible for the compiler to provide zero-cycle transitions in seq { a ; b } when it can be certain that a[done] & b[done] is UNSAT. There are two things we can do with this information:

Write a freaky pass that tries to prove this theorem and, when it can, somehow gets TDCC to provide such zero-cycle transitions in the FSM logic. This is purely opportunistic and provides no language-level guarantees, so it is not helpful for #1820, but it is still a cool optimization.
Exploit the observation that a[done] & b[done] is guaranteed to be UNSAT when b is a static group to provide some kind of language-level guarantee.

I think one question we'd have to answer for option 2 would be: what does the surface-level, syntactic rule look like that implies this guarantee? It could just be this:

In any dynamic seq, consider every adjacent pair of child statements. (They need not be group activations.) If the first statement in the pair is dynamic and the second is static, it is guaranteed to start executing during the cycle that the first statement becomes done.

I don't like this very much because it means that even a dynamic seq can tie the compiler's hands w/r/t scheduling. We can't do schedule compaction on any seq that contains this adjacent pairing, for example.
An alternative (which would be pretty heavyweight) would be to introduce a new, special control operator just for this purpose.

The opportunistic stuff is an optimization so I won't say much about it. You're right about the trade-offs: no semantic guarantees and therefore not particularly useful timing-precise reasoning.
I was thinking of a rule of the form that "entering a static control program is guaranteed to be zero-cycle". However, I agree with you that this is putting constraints on the way dynamic scheduling works. Unfortunately, I don't see a way out of it: if we want to provide guarantees between the timing interactions between dynamic and static control, we'll have to make statements about the scheduling policies for dynamic operators. We can try adding attributes but that doesn't really address the problem.

I suppose my high-level point about the dilemma here is that we probably want to support both modes. That is, seq { a ; b } should keep its current guarantees and remain schedule-able, for the general case where the code is not timing-sensitive and you just want the computation done as quickly as possible. But perhaps we want to invent something else that is more in the vein of static seq, in the sense that it is useful for carefully orchestrating time, but that does not require all its children to be static.

How do you feel about making the "slow transition" behavior opt-in in the same we've been discussing adding a new attribute to make static control programs compactable? That is, in the normal case, we will generate fast transitions from dynamic to static sub-programs but if you give us an attribute to say "I don't care", then we are allowed to generate slow transitions?
I'm hesitant of introducing a new control operator with these semantics because then we have three different kinds of sequencing and I don't know what the guideline for which is a "good default" will be. If we already know that the good default is "fast transition", then let's make seq default to that?

It could work! Yeah, I think what's confusing here is that I also don't know what the right default is: schedulable vs. save-a-cycle. There is a reasonable argument to be made that "schedulable" is the right default because it reflects "normal" computations that don't need to interface with the outside world. Especially if paired with a best-effort optimization that saves a cycle in most cases anyway?

I think defining which computations potentially interact with the outside world will become increasingly difficult, especially in presence of ref cells. If that is the case, then we should make the precise behavior ("save a cycle") the default and allow programs to opt out of it.
I would also reframe the "save a cycle" to something like "dynamic to static transition guarantee" to imply that this isn't just an optimization; it's a guarantee of the compiler that user-level programs can rely on.

During a synchronous discussion, we were trying to generalize the problem expressed in the original post: in other words, come up with other situations in which we need cycle-precise behavior for control between the static/dynamic boundary.
For example, one scenario we were thinking of was the following If we had something like:
while port {
  seq {
    // static child
    // dynamic child
  }
}

What if we need the backwards edge from dynamic child -> static child to be a 0 cycle transition?
@nathanielnrn can you think of any other scenarios in the yxi project where you would need 0 cycle transition behavior, besides the scenario you already gave?

It seems to me like the dynamic -> static description covers the cases we are encountering in AXI.

@nathanielnrn I think Caleb is asking if there are specific, concrete examples you can think of. For example, one possible example is a burst transfer where, once the valid signal is asserted, the component needs to start reading values starting the next cycle for n cycles where n is the burst size:
seq {
  wait_for_valid;
  repeat N {
    par { incr_idx; write_inp }
  }
}

@calebmkim and I spoke synchronously about this. The scenarios we came up with are dynamic -> static transitions like those discussed above as well as a likely-useful optimization for transitions between the end of while loops and the start of them.
A reduced example would be something like
while perform_writes.out {
  block_transfer;
  perform_write_transfer; //having a group like this would require 0 transition dynamic -> static
}

If we had some guarantee on the transition between the end of perform_write_transfer to the start of block_transfer in between while cycles, we could likely save on some boiler plate assignment/groups that exist in the current implementation to guarantee write_transfer handshakes happen for a single cycle. This would almost definitely increase the throughput of our interface down the road.

This is great; thanks for the synopsis. And interesting that this example contains both static->dynamic and dynamic->static transitions!

Another bump on this issue because I'd like to make progress on this. @calebmkim thoughts on taking the next open slot in the Calyx meeting to discuss this issue and maybe propose concrete implementation strategy?

Just took the next slot

Based on the synchronous discussion today, it seems like we probably do not want to introduce a zero-cycle transition as a guarantee of the language, as it would infect the scheduling of seqs and would prevent things like compaction.
The option that we had in mind was to add a minimally expressive extension as an attribute: we can call it @qt for quick-transition. It can be attached to a dynamic seq and it will guarantee zero-cycle transitions between each child of the seq. To support this guarantee, we require that any @qt seqs alternate between static and dynamic children. In other words, if we have
@qt seq {
  A;
  B;
  C;
  D;
}

A->B->C->D must either be Static->Dynamic->Static->Dynamic or Dynamic->Static->Dynamic->Static.
From the synchronous discussion, it seems like the specificity is the point. We normally don't want to use this, but in case you have some specific timing constraints that you need to be met, then we will offer this special attribute to you.
@rachitnigam do you have thoughts?

We are limiting this to the alternating style because any non-alternating case can just be crafted using the alternating style (above) plus calls to appropriate control operators.
Say you need:
@qt seq {
  s1;
  s2;
  d1;
  d2;
  s3
}

where s*s are static and d*s are dynamic.
Too bad, you must write:
@qt seq {
  static seq { s1; s2; };
  seq { d1; d2; };
  s3
}

This is neat because it crisps up what the promise of @qt is: my immediate children will enjoy quick transitions, I don't know what will happen below them.

Zero-cycle groups or static groups are not allowed. If a program provides a zero-cycle group, it leads to undefined behavior (miscompilation, specifically)

In this case, compaction would not be allowed to parallelize the execution of A and the static par.

So this is what I don't understand. If A does not have any dependency on par { ... }, the zero-cycle transition semantics should allow for compaction. IMO the rule is: seq guarantees that the static child will observe the dynamic child within zero-cycles. If compaction can occur, then that means that the static child cannot observe the dynamic predecessor anyways because there is no dependence.
Does that make sense? The rule is only meaningful when there is a dependency between children. If there is no dependency, the rule does not matter.

Ah, I see what you're saying.
I still think there are some tricky cases here, though. For example, suppose we have:
@promotable(20) seq {
  @promotable(10) A;
  @promotable(5) B;
  static<5> par {..}; // par depends on *both* A and B
}

In this case, compaction would schedule them like this:
@static<15> par {
  static<10> par {A; B;}
  static<5> par {..}; // par depends on *both* A and B
}

Which would break the 0-cycle transition. B would execute from [0,5) and the par would start on cycle 10.
One "solution" would be to treat the static-dynamic pair as a "package" which must be thought of as a single entity when performing compaction, but a) this still limits compaction a bit and b) we still need to think about what the language-level guarantee would be.
Another "solution" could be that the 0-cycle transition only occurs if the length of the seq is 2, but this seems like a weird rule to have.

Ah, this is a good example! Note that as-late-as-possible (ALAP) schedule will still be able to satisfy the requirement of zero-cycle transition from B -> par { ... } but we cannot pick any other start time for B anymore. Now we need to decide if that's an okay restriction or not.
The relevant question is: are all schedules (ASAP, ALAP, etc.) about the same hardware cost when performing compacting? If yes, then maybe the freedom of scheduling choices is irrelevant; if not, let's see why?

Truly awesome; thanks for making this concrete, @calebmkim. That issue where the compiler would like to add latency between B and the static par is exactly the situation I was thinking of, but I never succeeded in writing it down this explicitly.
@rachitnigam, in this example, you're right that an ALAP schedule could still respect 0-cycle transitions from dynamic to static. I think, however, that there is a complementary counter-example for ALAP if we want to support the opposite direction to (0-cycle transitions from static to dynamic). Slightly modifying @calebmkim's example:
@promotable(20) seq {
  static<5> par {..}; // both A and B depend on this `par`
  @promotable(10) A;
  @promotable(5) B;
}

Now ALAP violates the 0-cycle guarantee and you want ASAP in order to respect it. To make things worse, consider a static/dynamic/static "sandwich":
@promotable(25) seq {
  static<5> par {..}; // both A and B depend on this `par`
  @promotable(10) A;
  @promotable(5) B;
  static<5> par {..}; // this other `par` depends on both A and B
}

Now, I think, there is no choice of when to run B that suffices to respect both directions of 0-cycle transition.
To return from specifics to generalities: it seems like it is very valuable for a rescheduling optimizer to have lots of freedom to insert delays between group activations, not just to delete them. Inserting them can sometimes (paradoxically?) let you reduce delays elsewhere, and it can certainly allow area/latency trade-offs by reducing parallelism. So it would be a shame to have seq restrict this ability by default.

@sampsyo okay, these examples are a nail in the coffin of the whole "language-level guarantee" pitch I was trying to go for. I think the attribute approach is fine for now and we can eventually consider a fast seq (fast as the new keyword) that attempts to give the guarantees.

Cool. That's a good plan… I share your aesthetic discomfort with semantics-bearing attributes, so I dig the idea of starting with one just because it's simpler to implement and then probably turning that into a proper qualifier. (I like the spelling fast!)

Okay, I'm going to mark this as "available" then! The plan is to implement the @fast attribute for now and eventually promote it to the fast keyword!

Who should I discuss the syntax/semantics of fast with before I start working on it?

The issue describes the high-level stuff. Are there specific questions you have?

Hi Ethan-- thanks for picking this up.
The most relevant comments regarding implementation are my comment on Feb 5 and Anshuman's comment on Feb 6.
You will probably have to edit tdcc (top_down_compile_control.rs) pass to implement this.
It's quite a big file-- I've found it useful to individually run passes on files to help get a high level understanding of what's going on in the pass. So for you, it might be helpful to run cargo run <filename> -p tdcc on some random Calyx design to get a better idea of what's going on in the pass (tdcc might expect you to ahve run some other passes before it like compile-invoke, so it might be something like cargo run <filename> -p compile-invoke -p any-other-passes -p tdcc).

Thanks, Caleb! Are you free today to discuss this?

Sure-- I'm pretty free this afternoon, we can DM to find a time


[XRT] Add command buffer

With this commit we can start testing to see if we can launch kernels. Some changes are made to the pipeline layout to better suit the needs of XRT API.

after testing I have uncovered issues such as block_pool not being optional but necessary for internal resources and that I didnt actual create the command bvuffer from device, I will fix these issues and come back with something that works


Request:  Ability to customize colors

It would be useful for those who are color blind or using a dark mode sheet to be able to customize colors with this mod.
As seen here, half the colors are difficult to read while either equipped or not on the dark mode sheet:

My color blind friend also wanted to include:  "please don't use red and green, or blue and purple"

As a heavily colour blind user I also massively appreciate anything that allows me to customise the colours. Would love this.

I also support this suggestion, as this module is very promising, but for a slightly different reason. The inability to change colours brings some difficulties. In my games, I use predefined background colours and a template from Lineage II, depending on the rarity of the item for the icons. If the item names could also be coloured in a specified colour for when I was using the standard Foundry VTT icon, or match the background, it would be great.

Fixed in latest release


Typo: finshed

merged https://github.com/kaazing/node-http2/commit/5a9fca9640b3cd8b3a57f932a5e956709e8fda5e


PKCS7/CMS: fix doc on signer/chain certs; prevent double free on up_ref() failures

This is a spin-off from a correction and extension of #18916,
containing those fixes that should also be backported:

PKCS7 and SMIME: improve documentation w.r.t. untrusted and signer certificates
X509_add_cert(): prevent double free on X509_up_ref() failure
CMS_get1_crls(): prevent double free on X509_CRL_up_ref() failure

Overall, this PR is too big. Submitting separate PRs for easier to review parts would be helpful in the future.

Would it be possible to have at least some tests for some of the fixes?

Not really - besides the doc, comment, and app help/diagnostics changes,
the fixes are only for exceptional error situations (out of memory).

This PR is in a state where it requires action by @openssl/committers but the last update was 30 days ago

@vdukhovni can you please check my changes and approve as well?

This PR is in a state where it requires action by @openssl/committers but the last update was 30 days ago

This PR is in a state where it requires action by @openssl/committers but the last update was 61 days ago

This PR is in a state where it requires action by @openssl/committers but the last update was 92 days ago

This PR is in a state where it requires action by @openssl/committers but the last update was 123 days ago

This PR is in a state where it requires action by @openssl/committers but the last update was 154 days ago

This PR is in a state where it requires action by @openssl/committers but the last update was 185 days ago

This PR is in a state where it requires action by @openssl/committers but the last update was 216 days ago

Could you please rebase the PR to resolve conflicts?
Marking as inactive to be closed at the end of 3.4 dev barring further input.

This PR is in a state where it requires action by @openssl/committers but the last update was 30 days ago

This PR is in a state where it requires action by @openssl/committers but the last update was 60 days ago


tracing id

in SFU server, has mary peerconnection object.  now how to discriminate each pc by log is very difficulty。 so I a tracing id to identifying each pc，ice agent , ice address(relay,host) , dtls....

Hey @newzai
The W3C decided against this, so we aren't planning to do it either. You can see the thread here. We try to keep in sync so that our WASM bindings make sense as well.
I would embed the PeerConnection in another struct and keep the ID there.
Thanks for using Pion!

any progress?


ecds: add support for access log extensions

This is a tracking issue to implement ECDS for access log extensions. This can be used to dynamically update access log format without reloading HCM/listener, for example.

@kyessenov Are there any more details about ECDS?

https://www.envoyproxy.io/docs/envoy/latest/configuration/overview/extension#discovery-service. Right now, it's just HCM that supports it.

@kyessenov are you still working on this? I think we need this for #21718

@zirain No, I'm not. I agree this is useful for fine-grained access log configuration.


Adding readme's to each folder

Hi @stephenhuang, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

there are conflicts...

what happened to gpiotesttool? removed from samples?


Fixed UF-230: Adding/Removing docks can cause incorrect workbench layout

Adding/Removing docks needs to trigger resizing of the workbench layout so that other components can adjust their size accordingly.

master:<PHONE_NUMBER>30c75b98d731ed4101811e011850a3
0.7.x: 74f6bb8efad314531012a76d9354773b28888f7d
Thanks for the tests and your help!

@csadilek :)


code

I want to know which code stand for the funtion of invShiftRow in the file  cryto\aes\aes_x86core.c
I find substitute bytes  and Mix Columns,maybe some codes I am not understand, hope you can help me,thanks.

This question seems stale with no recent activity. Marked as "unresolved" and scheduling for later closure.


[PERF] Cache results of State.get

Speed up of about ~30 op/s consistently overall. 5000 op/s improvement around recognize. Tried using an object that was placed into dictionary mode for the cache as the shape changes overtime but seemed slower.
  Add ................... 505.78 op/s
  End-to-end ............ 270.97 op/s
  Generate ........ 4,874,011.82 op/s
  Handlers For ... 37,588,869.18 op/s
  Recognize ......... 360,278.12 op/s

Adding link to baseline numbers https://github.com/tildeio/route-recognizer/pull/76


Cndit 669 keycloak

Implementation for auth service using Keycloak as Idp.
For the development, used the keycloak server that is installed in the FTS2 AWS environment, and unit testing has been completed.
This PR is mainly to see if the code coverage is sufficient for the SonarCould scan.

The user registration module has been removed as it's not required.

Can you also check to remove the public.pem file from the /resources/certs/ directory? I remember it was also a part of old auth mechanism.

Removed the public.pem


Generate Sphinx docs in nitpicky mode

Add -n to SPHINXOPTS in docs/Makefile, and update the documentation to fix any issues uncovered by these extra checks.

I'll do this one


Add withSwipe higher-order component

Will support:

[x] onSwipeUp, onSwipeDown, onSwipeLeft, onSwipeRight
[ ] Move the container with the swipe moving, or let it static
[ ] Velocity threshold and distance threshold

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: Fernando Via Canel:x: xavierviaFernando Via Canel seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: Fernando Via Canel:x: xavierviaFernando Via Canel seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Support of converting YUV_240_888 to Bitmap

Hello, first of all thanks for your great library!
I am now trying to do something to each frame returned by Android Camera 2 API (Which I guess most user of this library do).
Note that I have already specified YUV_240_888 for the ImageReader:
        mFrameImageReader = ImageReader.newInstance(largest.getWidth() / 4, largest.getHeight() / 4,
                ImageFormat.YUV_420_888, 2);

And in onImageAvailable:
        @Override
        public void onImageAvailable(ImageReader reader) {
            Image image = reader.acquireNextImage();
            try {
                if (onFrameCallback != null) {
                    ByteBuffer buffer = image.getPlanes()[0].getBuffer();
                    byte[] bytes = new byte[buffer.capacity()];
                    buffer.get(bytes);
                    Bitmap frameBitmap = YuvToRgb.yuvToRgb(rs, bytes, width, height);
                    Log.i("onFrame", frameBitmap.getWidth() + ", " + frameBitmap.getHeight());
                }
            } finally {
                image.close();
            }
        }

When I attach a debugger, I can see the conversion line is executed but before the logging line, the app crashes without any stacktrace, instead giving this error message:
Fatal signal 7 (SIGBUS), code 2, fault addr 0xbe68f040 in tid 1699
Do you have any idea / any working example with Camera 2 API?
By the way, Camera 1 returns NV21 format and I have tried with Camera 1 API and NV21 works perfectly. But Camera 2 does not support NV21...

Hi @siralam !
First, without further look at the actual running code, I would like to point out that errors like these most often comes from unexpected-sized input. The input for the NV21 byte array input should be (width * height) * 1.5 bytes (check this diagram, please note UV byte order is mistakingly reversed though). Looking at your code it looks like you are only taking the Y-plane of your YUV_420_888 image, which is only a (width * height)log byte array, thus causing the crash. You would need to also pass the right UV data in order for any conversion to work.
Then, there is the bigger issue of actual conversion support of the format you are trying to do on this library. As far as I know, Camera 2 API provides these YUV_420_888 images in a separate plane presentation. Note in the referred documentation that each plane has pixel and row stride, meaning several formats could be encoded in that Image object you are reading from, NV21 being just one possibility. So, in general, the library doesn't support conversion from these objects provided from Camera 2 API, unless you somehow convert those possible formats to a NV21 compliant one, or make sure the one you are receiving from the API is NV21 (and then you still need to do some byte array stitching).
In short, it looks like the big issue is actually lack of conversion support for Camera 2 API provided images. I think this is a legitimate request and a valuable one, and while I may not have the time to do it shortly, I'd be glad to mark it as "Help wanted" and welcome community contributions to it. So please if you'd like that support to be implemented please open that issue so that people could eventually contribute to it :)

Hi @silvaren ! Thanks for your response, actually I have managed to do it, but did not use any RenderScript.
What I did is convert the byte[] from Camera 2 API to NV21 format, and then use your library as usual to convert NV21 to Bitmap.
And below is how I convert that byte[] to NV21:
    public static byte[] YUV420toNV21(Image image) {
        Rect crop = image.getCropRect();
        int format = image.getFormat();
        int width = crop.width();
        int height = crop.height();
        Image.Plane[] planes = image.getPlanes();
        byte[] data = new byte[width * height * ImageFormat.getBitsPerPixel(format) / 8];
        byte[] rowData = new byte[planes[0].getRowStride()];

        int channelOffset = 0;
        int outputStride = 1;
        for (int i = 0; i < planes.length; i++) {
            switch (i) {
                case 0:
                    channelOffset = 0;
                    outputStride = 1;
                    break;
                case 1:
                    channelOffset = width * height + 1;
                    outputStride = 2;
                    break;
                case 2:
                    channelOffset = width * height;
                    outputStride = 2;
                    break;
            }

            ByteBuffer buffer = planes[i].getBuffer();
            int rowStride = planes[i].getRowStride();
            int pixelStride = planes[i].getPixelStride();

            int shift = (i == 0) ? 0 : 1;
            int w = width >> shift;
            int h = height >> shift;
            buffer.position(rowStride * (crop.top >> shift) + pixelStride * (crop.left >> shift));
            for (int row = 0; row < h; row++) {
                int length;
                if (pixelStride == 1 && outputStride == 1) {
                    length = w;
                    buffer.get(data, channelOffset, length);
                    channelOffset += length;
                } else {
                    length = (w - 1) * pixelStride + 1;
                    buffer.get(rowData, 0, length);
                    for (int col = 0; col < w; col++) {
                        data[channelOffset] = rowData[col * pixelStride];
                        channelOffset += outputStride;
                    }
                }
                if (row < h - 1) {
                    buffer.position(buffer.position() + rowStride - length);
                }
            }
        }
        return data;
    }

I believe the above method is a bit slower compared to using RenderScript. But since I don't know how to implement a RenderScript by myself, I have to use this method.
But I also found someone posted how to use RenderScript to convert YUV_240_888 to RGB, you may have a try to see if it works.
Since it directly converts YUV_240_888 to RGB, and use RenderScript instead of Java code, I think it should be much faster than the current method I am using.
Thanks!

This looks great @siralam ! I might give it a try at some point to include it in the library :) Thanks!

Thanks @silvaren , looking forward to your good news :D

I am not able to create instance of RenderScript . below is the code
byte[] bytes = YUV420toNV21(image);
RenderScript rs = new RenderScript.create(getApplicationContext());
Bitmap outputBitmap = Nv21Image.nv21ToBitmap(rs, bytes, image.getWidth(), image.getHeight());
Error : Cannot resolve symbol 'create'


Implement Retry Logic for Cluster Selection

This is the second PR opened for retries. Closed #828

I’m just on my phone but I’m guessing that having do_worker_build raise
OsbsException would make the most sense.
On Thu, Oct 12, 2017 at 7:56 AM Luiz Carvalho<EMAIL_ADDRESS>wrote:

@lcarva commented on this pull request.
In atomic_reactor/plugins/build_orchestrate_build.py
https://github.com/projectatomic/atomic-reactor/pull/841#discussion_r144266851
:

       raise UnknownPlatformException('No clusters found for platform {}!'

                                      .format(platform))

   retry_contexts = {

       cluster.name: ClusterRetryContext(self.max_cluster_fails)

       for cluster in clusters

   }

   while True:

       possible_cluster_info = self.get_clusters(platform, retry_contexts, clusters)

       for cluster_info in possible_cluster_info:

           ctx = retry_contexts[cluster_info.cluster.name]

           try:

               self.do_worker_build(cluster_info)

               return

Ha! Good catch. Let's change do_worker_build to not catch exceptions when
cluster_info.osbs.create_worker_build(**kwargs) is called. This should
cause the exception to propagate as needed.
What do you think?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/projectatomic/atomic-reactor/pull/841#discussion_r144266851,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ab7hEVrRq8cb2rhsGUBnJ80cbHkOW1I2ks5srf5mgaJpZM4PgsxK
.

Updated release notes draft:

Retry approach has been applied to interaction with worker clusters


Ci for azps-5.7.0

Docs Build status updates of commit 4dbaa3e:
:warning: Validation status: warnings

File
Status
Preview URL
Details

:warning:Warning

Details

docs-conceptual/azps-5.7.0/release-notes-azureps.md
:warning:Warning
View (azps-5.7.0)
Details

azps-.5.7.0/Az.ADDomainServices/Az.ADDomainServices.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.ADDomainServices/Get-AzADDomainService.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.ADDomainServices/New-AzADDomainService.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.ADDomainServices/New-AzADDomainServiceForestTrust.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.ADDomainServices/New-AzADDomainServiceReplicaSet.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.ADDomainServices/Remove-AzADDomainService.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.ADDomainServices/Update-AzADDomainService.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Add-AzEnvironment.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Az.Accounts.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Clear-AzContext.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Clear-AzDefault.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Connect-AzAccount.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Disable-AzContextAutosave.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Disable-AzDataCollection.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Disable-AzureRmAlias.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Disconnect-AzAccount.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Enable-AzContextAutosave.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Enable-AzDataCollection.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Enable-AzureRmAlias.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Get-AzAccessToken.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Get-AzContext.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Get-AzContextAutosaveSetting.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Get-AzDefault.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Get-AzEnvironment.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Get-AzSubscription.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Get-AzTenant.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Import-AzContext.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Invoke-AzRestMethod.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Register-AzModule.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Remove-AzContext.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Remove-AzEnvironment.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Rename-AzContext.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Resolve-AzError.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Save-AzContext.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Select-AzContext.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Send-Feedback.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Set-AzContext.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Set-AzDefault.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Set-AzEnvironment.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Accounts/Uninstall-AzureRm.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Advisor/Az.Advisor.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Advisor/Disable-AzAdvisorRecommendation.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Advisor/Enable-AzAdvisorRecommendation.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Advisor/Get-AzAdvisorConfiguration.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Advisor/Get-AzAdvisorRecommendation.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Advisor/Set-AzAdvisorConfiguration.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Aks/Az.Aks.md
:white_check_mark:Succeeded

azps-.5.7.0/Az.Aks/Disable-AzAksAddOn.md
:white_check_mark:Succeeded

This comment lists only the first 50 files in the pull request.

[Warning-RepositoryOwnerPermissionInsufficient] Owner rloutlaw of repository https://github.com/MicrosoftDocs/azure-docs-powershell has lost Admin permission. Please use Transfer Owner via Docs portal https://ops.microsoft.com to assign a new owner.
Line 0, Column 0: [Warning-MAML2Yaml_Directory_NotFound] Directory can't be found: azps-5.7.0

docs-conceptual/azps-5.7.0/release-notes-azureps.md

Line 3161, Column 1: [Warning-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
Line 4401, Column 1: [Suggestion-sensitive-language-wl] Term 'whitelist' is sensitive and should not be used in content or code. Usage: '* Added new sizes to the whitelist of VM sizes for which accelerated networking will be turned on when using the simple param set for '

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit a2264d5:
:warning: Validation status: warnings

File
Status
Preview URL
Details

azps-5.7.0/Az.DataFactory/Get-AzDataFactoryV2DataFlow.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.DataFactory/Remove-AzDataFactoryV2DataFlow.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.DataFactory/Set-AzDataFactoryV2DataFlow.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.KeyVault/Add-AzKeyVaultKey.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.KeyVault/Get-AzKeyVaultCertificate.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.KeyVault/Get-AzKeyVaultKey.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.KeyVault/Remove-AzKeyVaultKey.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.KeyVault/Undo-AzKeyVaultSecretRemoval.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Monitor/Get-AzActivityLogAlert.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Monitor/Get-AzAlertHistory.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Monitor/Get-AzAlertRule.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Monitor/New-AzAlertRuleEmail.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Monitor/New-AzAlertRuleWebhook.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Monitor/New-AzDataCollectionRuleAssociation.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Get-AzApplicationGatewayClientAuthConfiguration.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Get-AzApplicationGatewaySslProfilePolicy.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Get-AzExpressRouteCircuitConnectionConfig.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Get-AzNetworkWatcher.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Get-AzNetworkWatcherFlowLog.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Get-AzNetworkWatcherFlowLogStatus.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Get-AzNetworkWatcherNextHop.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Get-AzNetworkWatcherPacketCapture.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Get-AzNetworkWatcherReachabilityProvidersList.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Get-AzNetworkWatcherReachabilityReport.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Get-AzNetworkWatcherSecurityGroupView.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Get-AzNetworkWatcherTopology.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Get-AzNetworkWatcherTroubleshootingResult.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Get-AzVpnClientPackage.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Invoke-AzNetworkWatcherNetworkConfigurationDiagnostic.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/New-AzApplicationGatewayClientAuthConfiguration.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/New-AzNetworkWatcher.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/New-AzNetworkWatcherFlowLog.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/New-AzNetworkWatcherNetworkConfigurationDiagnosticProfile.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/New-AzNetworkWatcherPacketCapture.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/New-AzNetworkWatcherProtocolConfiguration.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/New-AzPacketCaptureFilterConfig.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Remove-AzApplicationGatewayClientAuthConfiguration.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Remove-AzApplicationGatewaySslProfilePolicy.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Remove-AzExpressRouteCircuitConnectionConfig.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Remove-AzNetworkWatcher.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Remove-AzNetworkWatcherFlowLog.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Remove-AzNetworkWatcherPacketCapture.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Resize-AzVirtualNetworkGateway.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Set-AzApplicationGatewayClientAuthConfiguration.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Set-AzApplicationGatewaySslProfilePolicy.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Set-AzNetworkWatcherConfigFlowLog.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Set-AzNetworkWatcherFlowLog.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Start-AzNetworkWatcherResourceTroubleshooting.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Stop-AzNetworkWatcherPacketCapture.md
:warning:Warning
View (azps-5.7.0)
Details

azps-5.7.0/Az.Network/Test-AzNetworkWatcherConnectivity.md
:warning:Warning
View (azps-5.7.0)
Details

This comment lists only the first 50 files in the pull request.

azps-5.7.0/Az.DataFactory/Get-AzDataFactoryV2DataFlow.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Set-AzDataFactoryDataFlow.md'.
Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Remove-AzDataFactoryDataFlow.md'.

azps-5.7.0/Az.DataFactory/Remove-AzDataFactoryV2DataFlow.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Get-AzDataFactoryDataFlow.md'.
Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Set-AzDataFactoryDataFlow.md'.

azps-5.7.0/Az.DataFactory/Set-AzDataFactoryV2DataFlow.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Get-AzDataFactoryDataFlow.md'.

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Add-AzApplicationGatewaySslProfilePolicy.md'.

azps-5.7.0/Az.Network/Remove-AzExpressRouteCircuitConnectionConfig.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: 'New-AzExpressRouteCircuitConnectionConfig.md'.

azps-5.7.0/Az.Network/Remove-AzNetworkWatcher.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Get-AzNetworkWatcherConnectionMonitor'.

azps-5.7.0/Az.Network/Remove-AzNetworkWatcherFlowLog.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Get-AzNetworkWatcherConnectionMonitor'.
Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Get-AzNetworkWatcherFlowLog'.

azps-5.7.0/Az.Network/Remove-AzNetworkWatcherPacketCapture.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Get-AzNetworkWatcherConnectionMonitor'.

azps-5.7.0/Az.Network/Resize-AzVirtualNetworkGateway.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Set-AzVirtualNetworkGatewayVpnClientConfig.md'.

azps-5.7.0/Az.Network/Set-AzApplicationGatewayClientAuthConfiguration.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Add-AzApplicationGatewayClientAuthConfiguration.md'.

azps-5.7.0/Az.Network/Set-AzApplicationGatewaySslProfilePolicy.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Add-AzApplicationGatewaySslProfilePolicy.md'.
Line 0, Column 0: [Warning-file-not-found] Invalid file link: './New-AzApplicationGatewaySslProfilePolicy.md'.

azps-5.7.0/Az.Network/Set-AzNetworkWatcherConfigFlowLog.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Get-AzNetworkWatcherConnectionMonitor'.

azps-5.7.0/Az.Network/Set-AzNetworkWatcherFlowLog.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Get-AzNetworkWatcherConnectionMonitor'.
Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Get-AzNetworkWatcherFlowLog'.

azps-5.7.0/Az.Network/Start-AzNetworkWatcherResourceTroubleshooting.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Get-AzNetworkWatcherConnectionMonitor'.

azps-5.7.0/Az.Network/Stop-AzNetworkWatcherPacketCapture.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Get-AzNetworkWatcherConnectionMonitor'.

azps-5.7.0/Az.Network/Test-AzNetworkWatcherConnectivity.md

Line 0, Column 0: [Warning-file-not-found] Invalid file link: './Get-AzNetworkWatcherConnectionMonitor'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


RTC: Rewritten

Removed rtcc in favor of time
Removed get functions in favor of a single get_datetime function
Takes into account registers synchronization flag
Always returns a valid time (or panics)
Removed disgusting 12-hour format support (Which wasn't implemented consistent anyway)

See https://github.com/stm32-rs/stm32f7xx-hal/pull/160#issuecomment-988792463 from @adamgreig.

Instead of returning an error, maybe it would be nicer to perform a second read and so always return consistent data?
The RM says (in RM0385 29.3.8 Reading the calendar) that if the APB clock is >= 7x the RTC clock (which is very likely since RTC clock is usually 32kHz) then it's OK to just read TR and then DR: the hardware locks DR after you read TR to ensure you get consistent data. In fact, it's important to always read TR and then DR, otherwise the later read of TR will lock an old value of DR. But, even if the APB clock is extremely slow, you can always read TR, then DR, then TR, then DR, and use the first values if the two TRs match, or the second values if the TRs don't match (as also described in the RM). Seems friendlier than returning an error to the user who has no choice but to now re-read in a loop until it doesn't error.
It looks like the driver should also wait for RSF to be set before taking values in case the user re-reads very soon afterwards too, and clear it after each read. Maybe it would be best to have a single get_datetime() method that does the correct wait-for-RSF, read TR, read DR, clear RSF sequence, and parses the fields, and then convenience methods for reading just seconds/minutes/etc could call that and return the relevant bit. Or just always give the user a full consistent datetime to make sure they don't try and read each part separately and end up with inconsistent data that way anyway...

Thanks also, true, should be quite easy to re-add, if someone cares or rtcc changes the trait definition.

@systec-ms Are you interested in porting improvements to related hals like f4, f3, l0?

@burrbull, this is on my to do list, but I don't know when I'll have the time.
(This is @systec-ms private account).


refactoring test case

This pull request refactors the E2E tests for the JP Learn Microsoft.com Update Checker to make them more maintainable and comprehensive. The changes primarily involve consolidating multiple individual test cases into a single parameterized test suite, improving the readability and reusability of the tests.
Refactoring of E2E Tests:

Consolidated multiple individual test cases into a single parameterized test suite using a testCases array. (tests/e2e/content.e2e.test.js)
Added support for testing different color schemes and themes by including prefersColorScheme and themeColor parameters in the testCases array. (tests/e2e/content.e2e.test.js)
Modified the test logic to dynamically set the theme and color scheme based on the parameters from the testCases array. (tests/e2e/content.e2e.test.js)
Ensured that the tests check for the presence or absence of specific text elements based on the expected theme and color scheme. (tests/e2e/content.e2e.test.js)

These changes improve the maintainability of the tests by reducing code duplication and making it easier to add new test cases for different scenarios.

$ npm run test:e2e

><EMAIL_ADDRESS>test:e2e
> jest tests/e2e

 PASS  tests/e2e/content.e2e.test.js (14.352 s)
  JP Learn Microsoft.com Update Checker E2E Test
    ✓ should display English update date on https://learn.microsoft.com/ja-jp/azure/virtual-machines/overview with dark theme in dark mode (1726 ms)
    ✓ should not run script on en-us pages  with dark theme in dark mode (418 ms)
    ✓ should display English update date on https://learn.microsoft.com/ja-jp/azure/virtual-machines/overview with dark theme in light mode (1231 ms)
    ✓ should not run script on en-us pages  with dark theme in light mode (172 ms)
    ✓ should display English update date on https://learn.microsoft.com/ja-jp/azure/virtual-machines/overview with light theme in dark mode (1220 ms)
    ✓ should not run script on en-us pages  with light theme in dark mode (158 ms)
    ✓ should display English update date on https://learn.microsoft.com/ja-jp/azure/virtual-machines/overview with light theme in light mode (1211 ms)
    ✓ should not run script on en-us pages  with light theme in light mode (153 ms)
    ✓ should display English update date on https://learn.microsoft.com/ja-jp/azure/virtual-machines/overview with high-contrast theme in dark mode (1224 ms)
    ✓ should not run script on en-us pages  with high-contrast theme in dark mode (158 ms)
    ✓ should display English update date on https://learn.microsoft.com/ja-jp/azure/virtual-machines/overview with high-contrast theme in light mode (1216 ms)
    ✓ should not run script on en-us pages  with high-contrast theme in light mode (155 ms)
    ✓ should display English update date on https://learn.microsoft.com/zh-cn/azure/virtual-machines/overview with light theme in light mode (1496 ms)
    ✓ should not run script on en-us pages  with light theme in light mode (153 ms)
    ✓ should run script with jp-learn-microsoft-com-update-checker-debug flag (193 ms)

Test Suites: 1 passed, 1 total
Tests:       15 passed, 15 total
Snapshots:   0 total
Time:        14.411 s, estimated 21 s
Ran all test suites matching /tests\/e2e/i.

👌


Fix DevTools tab switching.

What does the pull request do?
As described in #11120, DevTools got broken shortly before the preview7 release by #11084. Correctly handle the DataContext changing in TreeViewPage, and make sure we unsubscribe from the ClipboardCopyRequested event as well as subscribe.
Fixed issues
Fixes #11120.

You can test this PR using the following package version. 11.0.999-cibuild0033792-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-all/nuget/v3/index.json) [PRBUILDID]


Android unsets app as wallpaper

No clue why, but on my Android 7 device, sometimes PhotoPhase randomly disappears as wallpaper and I suddenly have the default factory wallpaper again. This happens once or twice a day so is rather annoying. Any way I could help debug this?
I'm running the F-Droid build.

I just noticed F-Droid's version is still very outdated. May be related. I'll reopen this issue if F-Droid gets a newer build so I can check if it's still relevant 4 years later.

In the meantime, if you need a recent version, all the published versions of the play store are in the release section of the repo https://github.com/jruesga/PhotoPhase/releases. All the contains the gms services and are signed with the release keys.


Add ISC to license whitelist

I asked about the license's inclusion in a line note, but it's probably more relevant to bring it up in the form of a pull request.
The ISC license is a permissive, OSI-approved free software license that's functionally identical to the MIT/Expat license. The only "difference" is the ISC license excludes legal clauses that're already covered by the Berne Convention.
The ISC license is recommended by OpenBSD, and is also the default license type of newly-created NPM modules. The terseness and straightforwardness of the clauses make it (in my opinion, anyway) a preferable alternative to the decidedly long-winded MIT license.

Basically, I was surprised when Linguist's tests rejected the addition of a grammar addition, stating that ISC wasn't on the license whitelist.

Just to clarify, I'm definitely not an authority on this subject.


AudioSwitch, DFX Audio Enchancher problem

AudioSwitch is not compatitable with DFX Audio Enchancher. It Crash Instantly

Problem exists with AudioSwitch 2.1.3, DFX 12.014, Win 10.
ErrorLog.txt


ci: disable CI status checks that we are letting fail during CDP development

During CDP development, we have been OK with letting some of the CI status checks fail before we merge a PR. Instead of merging with some status checks be red (fail), this change disables CI running the checks that we currently let fail. This way, we can get back in the habit of not merging a PR until all CI status checks are green. Making it less likely we will break the main-cdp branch by accident.

Since multiple team members prefer to have failed status checks, I'll close this PR.


AMBARI-24270. Agent Status Command Are Randomly Failing With Empty stderr (debug patch)

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3045/
Test PASSed.


refactor: Tidy design-system dockerfiles [NP-1037]

Tidying of dockerfiles and general improvements
Since this is going to be a chunky PR, I'm going to drop checkpoint commits in that gather up related changes in a (hopefully) more organised fashion than trying to dump the inevitable iterative commits that come from playing with a Jenkinsfile. It'll stay in draft until that last step is complete.

@simonwgill I'm seeing the following error locally when I run docker-compose build
Step 1/6 : FROM backstopjs/backstopjs
 ---> cb1076c73da7
Step 2/6 : USER root
 ---> Running in eee89a83acd8
Removing intermediate container eee89a83acd8
 ---> 47cafb564aed
Step 3/6 : RUN echo 'debconf debconf/frontend select Noninteractive' | sudo debconf-set-selections
 ---> Running in a8e20c26b7b9
Removing intermediate container a8e20c26b7b9
 ---> 314739088db8
Step 4/6 : RUN apt-get update
 ---> Running in 07c25e09b9f8
Get:1 http://security.debian.org/debian-security stretch/updates InRelease [53.0 kB]
Ign:1 http://security.debian.org/debian-security stretch/updates InRelease
Get:2 http://security.debian.org/debian-security stretch/updates/main amd64 Packages [604 kB]
Get:3 http://dl.google.com/linux/chrome/deb stable InRelease [1811 B]
Ign:3 http://dl.google.com/linux/chrome/deb stable InRelease
Get:4 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages [1089 B]
Ign:5 http://deb.debian.org/debian stretch InRelease
Get:6 http://deb.debian.org/debian stretch-updates InRelease [93.6 kB]
Ign:6 http://deb.debian.org/debian stretch-updates InRelease
Get:7 http://deb.debian.org/debian stretch Release [118 kB]
Get:8 http://deb.debian.org/debian stretch-updates/main amd64 Packages [2596 B]
Get:9 http://deb.debian.org/debian stretch Release.gpg [2410 B]
Ign:9 http://deb.debian.org/debian stretch Release.gpg
Get:10 http://deb.debian.org/debian stretch/main amd64 Packages [7080 kB]
Fetched 7956 kB in 2s (2766 kB/s)
Reading package lists...
W: GPG error: http://security.debian.org/debian-security stretch/updates InRelease: At least one invalid signature was encountered.
W: The repository 'http://security.debian.org/debian-security stretch/updates InRelease' is not signed.
W: GPG error: http://dl.google.com/linux/chrome/deb stable InRelease: At least one invalid signature was encountered.
W: The repository 'http://dl.google.com/linux/chrome/deb stable InRelease' is not signed.
W: GPG error: http://deb.debian.org/debian stretch-updates InRelease: At least one invalid signature was encountered.
W: The repository 'http://deb.debian.org/debian stretch-updates InRelease' is not signed.
W: GPG error: http://deb.debian.org/debian stretch Release: At least one invalid signature was encountered.
W: The repository 'http://deb.debian.org/debian stretch Release' is not signed.
Removing intermediate container 07c25e09b9f8
 ---> 8e0849d3fd2f
Step 5/6 : RUN sudo apt-get install wait-for-it
 ---> Running in 08e6eca305aa
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  wait-for-it
0 upgraded, 1 newly installed, 0 to remove and 115 not upgraded.
Need to get 4000 B of archives.
After this operation, 17.4 kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
  wait-for-it
Install these packages without verification? [y/N] E: Some packages could not be authenticated
ERROR: Service 'visual-tests' failed to build : The command '/bin/sh -c sudo apt-get install wait-for-it' returned a non-zero code: 100

@simonwgill I'm seeing the following error locally when I run docker-compose build

Are you getting that on the master branch as well? A GPG error in apt is definitely not something I'd expect to see right now!

Are you getting that on the master branch as well? A GPG error in apt is definitely not something I'd expect to see right now!

I was also surprised, as it didn't seem related to your changes (looking great btw). Figured it was worth flagging anyway.
it's slightly more terse but I'm still getting an error on master:
Step 1/6 : FROM backstopjs/backstopjs
 ---> cb1076c73da7
Step 2/6 : USER root
 ---> Using cache
 ---> 47cafb564aed
Step 3/6 : RUN echo 'debconf debconf/frontend select Noninteractive' | sudo debconf-set-selections
 ---> Using cache
 ---> 314739088db8
Step 4/6 : RUN apt-get update
 ---> Using cache
 ---> 8e0849d3fd2f
Step 5/6 : RUN sudo apt-get install wait-for-it
 ---> Running in cb74b9cc52ed
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  wait-for-it
0 upgraded, 1 newly installed, 0 to remove and 115 not upgraded.
Need to get 4000 B of archives.
After this operation, 17.4 kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
  wait-for-it
Install these packages without verification? [y/N] E: Some packages could not be authenticated
ERROR: Service 'visual-tests' failed to build : The command '/bin/sh -c sudo apt-get install wait-for-it' returned a non-zero code: 100


Feature: Leaderboard

https://app.clickup.com/t/86bzgxbqd
https://app.clickup.com/t/86bzh4xev
https://github.com/gator-labs/chomp/assets/104349866/c85ff5dc-10f9-4c3e-b778-b4fb6e728b80
SUMMARY

add daily leaderboard
add weekly leaderboard
add campaign leaderboard
usernames on leaderboard are not showing because users are mocked and they do not have wallet address, it won't happen on prod

** BUILD WILL FAIL ON PREVIEW BECAUSE PR CONTAINS MIGRATIONS **

Approving now so I can start testing. But I have doubts about the leaderboard refresh logic. In all cases, I expect the leaderboard to update in realtime.

Campaign leaderboards are all-time. Scores never reset to 0.

Chomp leaderboard is daily or weekly. Scores reset to 0 at the same frequency.

Will weekly/daily leaderboard update in realtime as-is currently?

Campaign leaderboard never resets to 0 because it is ALL TIME.
Weekly and daily also never resets to 0 because let say today you achived 1000 points and you ranked first on leaderboard. Tommorow you won't be on leaderboard unless you get some points. We are not showing 0 values on leaderboard.

Weekly and daily also never resets to 0 because let say today you achived 1000 points and you ranked first on leaderboard. Tommorow you won't be on leaderboard unless you get some points. We are not showing 0 values on leaderboard.

Yes, good point, 0 doesn't show. But the reset does happen. And points do show up in realtime as you accumulate, right?


SSL defaults to false, but ssl.pp is included in various manifest fil…

…es.  Leave only the include in common.pp and remove the others.

Just to be clear, are you looking to deploy bacula using this module without SSL?  I ask because, while I recognize the bug, I'm also thinking that there is a case for requiring SSL in this module and not make it tune-able.  That would reduce the noise that dancing around the SSL would bring.  Thoughts?

In my case, as a second step I am using SSL - but my initial work with the module I was just trying to get it working as simply as possible (and that was without SSL).

@ianssoftcom Were you able to get this module deployed?  Apologies for the silence.  Just looking over it again, I am still unclear that this is the correct change.  In either case, the current conditionals check for $ssl, but that doesn't exist as a param on any of the classes attempting to use that variable for logic switching.  I would recommend trying the module with SSL and see what issues you have.  It has been working quite well for me, but I'd like to know if there are troubles getting it going elsewhere.

$ssl is defined based on hiera in params.pp
$ssl = hiera('bacula::params::ssl', false)
and is inherited by other classes.  It was only during the early days of testing where I was testing without the added complexity of SSL.  I was able to configure with SSL without issue.

@ianssoftcom Glad to hear you got SSL working.  With that in mind, do you think this PR is still valuable?  I'm inclined to think we should turn that default false into a true and cut a release reflecting that change.

Yes that will be fine.  If you really want to configure without ssl, you probably know what you're doing.  :-)

Great, thank you for the feedback @ianssoftcom.  I hope my slowness here didn't cause you trouble.  I'm going to close this one out and I'll put a card on my board to follow up on ssl tuning.


Cleanup

Hopefully the last round of conext refactoring :-)
r? @alexcrichton

:pushpin: Commit 7bfddee has been approved by alexcrichton

@bors: r+
Nice!

:hourglass: Testing commit 7bfddeeb4e8c7eefde640069dea14da8b1672309 with merge e06b964865c87e91c1710e76143bfdf9723044db...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing e06b964865c87e91c1710e76143bfdf9723044db to master...


Add support for user customized local options.

Related to #2. See my comment there about allowing the user to specify which local options should be transfered to the temporary diff-window.

I don't want to have too many options in the config of this plugin. Just keep it simple


Setting appropriate job status in hadoop2

@sandeepSamudrala kindly merge this

this pull req needs a rebase..
@avi-ram : please rebase and update the pull


[BP-1.14][FLINK-22821][core] Stabilize NetUtils#getAvailablePort in order to a…

Unchanged backport of #22821 on release-1.14

This is such a weird change. It only protects against concurrent uses of NetUtils#getAvailablePort, but any other port allocation can still break it.
It also seems like we could solve this properly for at least a few cases; the NettyClientServerSslTest could be changed to use port 0 for the server, and then query the server for the actually used port and pass that to the client...

Hi @zentol ,
Thank you very much for your reply. I have tested Netty ServerBootstrap and it turns out that if we bind 0 as the port number, the server will finally choose a random unallocated port. I agree with you that for Netty related test the file lock could be simplified to assign a port 0 to the NettyServer, as the file lock implementation is more cumbersome.
I think we may need to discuss whether it makes sense if we keep using the uniform logic by calling NetUtils#.getAvailablePort.


Bullet points fixed

Fixed issue where "Electron and Vue", "Electron and React" and "Electron and Angular" where invisible due to incorrect formatting of links.

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

:star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2:
Congrats on your first PR!
:star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2:


Export the individual Bar component

It is nicer to be able to use the already implemented Bar component inside the Bars slot.
See more at https://discord.com/channels/920755200552226868/1168230758276677762/1228256447834492988

Care to add a changeset (pnpm changeset)?

Done :+1:.

Thanks!


Moving header search filter above table header columns

Hi,
I just want to place the search filter above the header column.Would be more helpful if it is solved.
Thanks in advance..

https://github.com/6pac/SlickGrid is the current repo. use that.
i think there is a section above the columns, but you'd need to code that yourself.

Do you have any sample regarding placing search header above header titles.?

Bcuz,i cannot use some properties like dragging and etc by placing search header above the header titles..


Fix Examples

This PR contains Rosco's work in fixing the bitbox-sdk examples. This PR does not need a version bump as it does not effect the npm library.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


tbv2: re-add indirection to list

tbv2: re-add indirection to list
std::list was intended to have an extra layer to represent the overhead of
each list element similar to map implementations. This wasn't currently being
output which meant the size of each list element was being undercounted.
Add the extra layer of indirection to list elements and include this in the
tests.
Test Plan:

CI
Updated test cases

Stack created with Sapling. Best reviewed with ReviewStack.

#452
-> #455

Is that consistent with our implementations for other types? For instance, for std::set in types/set_type.toml, we have no indirection and directly go on to process the child. The exclusive size then aggregates the overhead of each element, see types/set_type.toml:114, and ensure correct reporting of the overhead.

Thanks for pointing that out! Thinking about it I agree. While specifically std::list suits this approach because each element has very specific overhead, no other lists do. std::deque can't split the overhead neatly between elements, and std::vector has no concept of per element overhead. I'll change this to attribute the overhead of the elements to the container as you say.


Update the dev application

Update the development environment application with more friendly example.
Could be a simple example of a space delivery company that has 3 APIs:

One for the sender that use the service to create and track deliveries
One for the receiver to track and validade reception of deliveries
One for the back-office to manage the company

Close in favor of https://github.com/AlexisNo/lager-dev-env/issues/1


Question- can't get the value from object

Hello, I would like to ask why I can't get the property of the object in JS script, it is undefined.The parameter passed in is a JSONObject and is also an Object at typeof

Hi @skymike11
can you please provide a minified executable example?
If with JSONObject you mean a javax.json.JsonObject or similar, one reason could be that you don't start the engine with sufficient permissions to access the Java properties. For instance, Context.newBuilder().allowHostAccess(HostAccess.EXPLICIT) might solve your problem.
-- Christian

Hello, this problem still exists,How do you modify it?
graalvm version 20.3.4。
code：
public static void main(String[] args) {
Context.Builder builder = Context.newBuilder("js")
.allowHostAccess(HostAccess.EXPLICIT);
    Context context = builder.build();
    context.getBindings("js").putMember("test",new TestA());
    String script = "" +
            "let a = test.test();" +
            "console.log(a.id)";
    context.eval("js",script);
}
public static class TestA {
    public TestA() {
    }

    @Export
    public Object test() throws InterruptedException {
        HashMap<String, Object> map = new HashMap<>();
        map.put("id","123");
        return map;
    }
}

outputs: undefined


How to build / deploy / configure with Mac and Platform.io

I cloned the repo and got the code to build and deploy to ESP32-C2 from my Mac.  However I don't know how to set the wifi parameters or mqtt parameters.
flasher.exe is a windows thing and i am trying to do this all on Mac OSX
Any hints to get this going?  I am using Platform.io and Visual Studio Code.
Thanks!
P.S. had to change board to:
board = esp32-c3-devkitm-1
and Serial2 to Serial1 in the code...

If the blue led is flashing on the esp32, then it’s in AP mode. Using a mobile device, connect to the TS45ToMQTT hotspotThe admin password is TS45ToMQTT, then enter your WiFi said and passwordSent from my iPadOn May 25, 2024, at 6:59 PM, kevinlieb @.***> wrote:
I cloned the repo and got the code to build and deploy to ESP32-C2 from my Mac.  However I don't know how to set the wifi parameters or mqtt parameters.
flasher.exe is a windows thing and i am trying to do this all on Mac OSX
Any hints to get this going?  I am using Platform.io and Visual Studio Code.
Thanks!
P.S. had to change board to:
board = esp32-c3-devkitm-1
and Serial2 to Serial1 in the code...
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>


Promote thoughtbot's Elixir experience

We love working with Elixir and Phoenix and want to call attention
specifically to our experience with those technologies. Our
elixir-phoenix landing page has open source projects, blog posts, and
information on why we love Elixir.

LGTM!


Optional parameters in UpdateActions

The RemoveLineItemAction has an optional parameter quantity. The implementation uses a default value of 0. But this value should not be transported on the API when not set else the line item will not be removed.
I didn't checked for other update actions and optional parameters but most likely this can happen also at other update action models

The quantity parameter has been removed from the RemoveLineItemAction constructor.  I am working on removing the others.


hugo: 0.77.0 -> 0.78.0

Motivation for this change
https://github.com/gohugoio/hugo/releases/tag/v0.78.0
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.


Adding Savings Tracker and Setting Savings Goal components

Feature

Basic UI Layout for SavingsTracker and SetGoal component
SetGoal component as popup modal window when attempting to set a new savings goal
Uses global tailwind config colors for red and blue.
Added global css style to remove the up and down arrows for default style of input element, type = number
Rectangular Progress Bar dynamically updates and filled when balance/goal are altered.
Max savings goal is currently 1 million.

Bug:

Unable to configure Axios fetch and requests to set balance and goal variables dynamically.
Unable to add rounding to progress bar as a 1% completion to the goal couldn't apply proper rounding to the div fill bar.

resolves #41

actually looks like you have a conflict now, would you be able to resolve this?
Yep. I just added what was on the main branch.

Almost complete, just gonna refactor fetching balance via Context Provider. Once #84 is squash merged.


[Critical Bug] Script unable to like any posts

Seems like IG made a change on the elements that the script can't like any posts now, making it unfunctional.

perfect! thank you!

@imakou do you know of any version that uses Appium? this script is very solid but deskop version gets soft bans so fast, mobile appium has 5x higher limit of actions

Hi @ap0l0 , Change line: 268 to the following in file instFunc.py like_button = self.wait.until(EC.presence_of_element_located((By.XPATH, '//span[@class="_aamw"]/div')))

perfect thank you! this worked as a work around


Started expanding docs

In terms of old examples, the 02_HDF5_examples directory is fully out of date so we'll remove it, as the basic IO example already covers it.
The 03_PIC_examples need documenting and cleaning up to remove the non-PIR implementation.
The 04_sourcesink_boundaries probably needs some examples of implementing source and sink boundary conditions and documentaiton.
The 05_electron_scattering will just stay undocumented/incomplete for now.


chore(deps): bump @backstage/plugin-techdocs-backend to 1.10.13

https://issues.redhat.com/browse/RHIDP-4114
https://issues.redhat.com/browse/RHIDP-4115
https://issues.redhat.com/browse/RHIDP-4116
https://issues.redhat.com/browse/RHIDP-4117

/assign @nickboldt
for approval
/assign @JessicaJHee @04kash
for lgtm

/lgtm

we can't update without updating backstage versions


Add more details for reproducing training runs

In the readme you have a note

TODO: forthcoming: more information on how to replicate + relaunch the Pythia training runs, once the data is actually downloaded.

We are trying to reproduce your results and it would be awesome to get some more details here. One particular thing that would be helpful would be to point us to a version/commit of gpt-neox that is similar to the one you used for these training runs, unless you're confident that the newest version of that library will still closely reproduce these results.

Hi, sorry for being slow to respond on this, was on vacation for the past week!
v1.0 of GPT-NeoX is what you want! I believe the exact commit I used for the most recent runs is here, but v1.0 should only differ in some features not enabled in the training runs. The major breaking change done in v2.0 would be the switch of Deepspeed versions from DeeperSpeed (forked around 0.3.15 from DeepSpeed) to DeepSpeed's most recent version as of v2.0.
Note that in ~the next few days we'll be sharing a very slightly updated version of all models. The old models will remain available under the name pythia-v0-* on Huggingface, and the new models will have NeoX configs uploaded to the repo, with the following being the changes:

- All model sizes are now trained with uniform batch size of 2M tokens. Prior, the models of size 160M, 410M, and 1.4B parameters were trained with batch sizes of 4M tokens, but in the course of training the initial suite we discovered that it was feasible to train all models with uniform batch size, though based on prior literature we had not been certain of this fact before performing our own experiments on batch size.
- We additionally save checkpoints at initialization (step 0), and checkpoints at steps 1,2,4,8,16,32,64,128,256.
- Flash attention is enabled.
- in the original suite: all models of size 2.8B parameters or smaller had a learning rate (LR) schedule which decayed to a minimum LR of 10% the starting LR rate, but the 6.9B and 12B models all used an LR schedule which decayed to a minimum LR of 0. In the redone training runs: all models now were trained with LR decaying to a minimum of $0.1 \times$ their maximum LR.

Hope this helps!
Are there any other particular details you'd want to have for replicating our runs? Happy to share, e.g. more on the hardware setup and library versions used for these runs!

Thank, you, the new models sound great! Are those still trained with v1.0 or are they now using v2.0? We had been regenerating 0-step checkpoints ourselves so that's really helpful too.
We (Generally Intelligent) are trying to replicate your results in a different LLM library (a modified version of MosaicML) since pythia seems to be the best-documented and decent-performing medium-sized LLM around, so it's a really useful baseline to verify our implementation. Honestly impressed with the quality of all y'alls stuff. We aren't trying to get identical checkpoints, but just want to get matching loss/eval curves over a training run. Currently things look great when we use your tokenized dataset+dataloader with our model/training setup, so seems like the model/training stuff is replicating well, but we're still having trouble getting our version of the dataset+dataloader to match. Most likely the problem is on our side but that's why I was asking the exact details on how you generated the deduped tokenized dataset in the other thread - hoping to deterministically match them so we can compare the tokenized datasets token-for-token.

We trained with v1.0 still for these!
Got it, I see. Is your fork of Composer / MosaicML/examples public? As I'm parsing it it sounds like you've added the Megatron dataset/dataloader code to a Composer training script and are working on using perhaps Mosaic's streaming library to get the same exact inputs / ordering in that codebase(?)
If this is the case, then getting all the concat+shuffling to play out precisely as Megatron does it will be a huge headache. Megatron does a lot of stuff with shuffling + sampling ratios under the hood--some of that like the BlendableDataset code can be ignored in the 1-datasource case as is the case here with just the deduped Pile, but plenty of the rest would more or less require reimplementing the Megatron data code in your codebase verbatim.
Maybe I've misunderstood the scenario you're describing though!

I think #81 was the bulk of my confusion, I had accidentally unsharded the un-deduped tokenized dataset and was thinking it was the deduped one. I also discovered that the way Mosaic's StreamingDataset shuffling works isn't ideal - they pick a random shard, shuffle the sequences in the shard, and then yield all the sequences from that shard before continuing. But that seems to introduce some autocorrelations between batches that causes worse performance than a full global shuffle of tokenized sequences. This is most problematic when only using one GPU/dataloader worker, as you're yielding every batch from the same shard.

@zplizzi is any follow-up required, or can we close this issue?


[bug] Navbar visibility issue

The navbar is not visible. A glassy finish can be added. Can I be assigned the same under the hacktoberfest tag?

This is a website issue so I can't assign a contributor to it @Unnati2603. But I appreciate the report!
I'd be happy to add the tag to any other issues you'd like to work on

This is a website issue so I can't assign a contributor to it @Unnati2603. But I appreciate the report!
I'd be happy to add the tag to any other issues you'd like to work on

Ok 👍


DNS Capacity Testing

What
There is a business wide push to enable PDNS across the estate in order to improve security. Our MoJ DNS service provides this but it is not in use across the entire estate. Currently (exact number tbd) some devices are using Infloblox DNS service. The current tactical solution is to point to the MoJ DNS service in order to provide the PDNS service.
For testing purposes we are looking to double the current amount of traffic for DNS
This ticket is to complete DNS capacity testing from ticket 376
Findings From Spike:
During this spike, It has been established that dnsperf can be executed from "Corsham Test Bastion" server in AWS.
Here is an output of a test that was conducted
`ubuntu@ip-10-180-82-176:~$ time dnsperf -s staff-device-production-dns-754e69ecf996b619.elb.eu-west-2.amazonaws.com -d test_queryfile -c 1 -Q 10 -t 2 -l 300
DNS Performance Testing Tool
Nominum Version <IP_ADDRESS>.d
[Status] Command line: dnsperf -s staff-device-production-dns-754e69ecf996b619.elb.eu-west-2.amazonaws.com -d test_queryfile -c 1 -Q 10 -t 2 -l 300
[Status] Sending queries (to <IP_ADDRESS>)
[Status] Started at: Tue Jun 27 13:15:17 2023
[Status] Stopping after 300.000000 seconds
[Status] Testing complete (time limit)
Statistics:
Queries sent: 3000
Queries completed: 3000 (100.00%)
Queries lost: 0 (0.00%)
Response codes: NOERROR 2333 (77.77%), NXDOMAIN 667 (22.23%)
Average packet size: request 33, response 117
Run time (s): 300.000323
Queries per second: 9.999989
Average Latency (s): 0.003219 (min 0.000523, max 0.462044)
Latency StdDev (s): 0.021142
real 5m0.140s
user 0m0.057s
sys 0m0.388s`
Lessons learned
Codepipeline did not pick up changes from the code when trying to update the variable to provision a bastion server. This happened because the actual value is supposed to be updated in Parameter store "/staff-device/dns-dhcp/$ENV/enable_bastion" and not in the code.
The generate_tfvars.sh script in the code base is useful only for development environment. It is not optimized for preprod and prod because all the values override are pulled from parameter store at run time.
The Onprem VM is not reachable from the Bastion, hence test was conducted on bastion in AWS. We need to understand more, why it may be necessary to run the tests from the onprem VM
Considerations for Implementation
The bastion server in AWS is configured as a t2.nano instance type. If the testing will be done here, we will need to configure a larger instance
The scope of testing needs to be established. The previous testing that was conducted had 9 tests conducted covering different scenarios. Given the current requirement and load expectations, we will need to be more specific on the desired performance benchmark as this will help us scope the test a lot more better.
Query Load: Desired query load that the DNS server needs to handle. Can we define or articulate what is considered a "heavy load"?
Concurrency: Desired performance under multiple connections
Test Duration: What is the DNS server's stability and performance over an extended period.
Response Time: How quickly do we expect the DNS server to respond. In other words, what is our expectations in terms of DNS server's performance as it relates to latency and responsiveness.
Resource Utilization: What is the maximum resource utilization expected under heavy load.
Scalability and Load Balancing: Do we care about this? Is this part of what we want to see during the tests?
Reporting and Analysis: Do we care about visualizing the test reports for further analysis
With this, we can then proceed with testing.

Conclusions:

Add a scaling metric for “Max CPU utilization” (leaving the average in place)
Increase CPU capacity from 0.5 to 1 on the ECS clusters (Introduce this change separately to memory)
Once it is proven the service can scale correctly, we will then be in a position to set the scaling down config to be able to lower the “desired count”, based on usage.
Reduce memory from 1GB to 512MB  on the ECS cluster. Subject to more testing / validation (Introduce this change separately to CPU)
Currently the method of testing cannot generate a high amount of load. Therefore we need to review the method of load testing to increase the amount of queries per second. We can do this by either increasing the amount of hosts running  dnsperf or look into the AWS load testing solution using Jmeter scripts.

detailed of the testing documented below
https://docs.google.com/document/d/1hEUFC5h4u0K9MQElRQ7AZwx4Iuy3gyIgFQzT7tx7Ez4/edit