Support directly deliver packet to UDPProxy

It allows user to simulate the REPLAY ATTACK,
by delivering duplicated packet to server,
or simulate the network delay and ARQ packet.

@Sean-Der @at-wat Could you please help to review this PR? Thanks~

Sorry for the delay :(

Sorry for the delay :(

Thanks 😃


Use the proper namespace for exception classes

Exceptions go to the App\Exception namespace.
You have some in other places (e.g. InvalidCSVHeaderException).

Solved https://github.com/marceldobrica/training/pull/65


Warming up model

Hello,
After the new 0.9 update, it seems to be that there is a new "Warmup Model" feature added at the start. This is causing an issue  where the model is taking double the vram. I first thought that it uses the input and output token length to determine the max vram usage but it doesnt seem to be case as when the questions are asked, the vram goes up causing it to oom eventually which did not happen before.
I am on 4 A10G's 96gb vram and using a 13b model at fp16. It works fine when I use the older build. I also tried to build the image again locally by removing the warmup code, it does get rid of the double vram but it errors out as I believe its needed for the new factorization of the code.
Old build =  32gb vram
New build = ~64gb vram

Have you read the stack trace?

This was fixed! Not sure what happened but working good now


style prop applied to SvgIcon generating warning

I want to adjust the position of icon with style
<Icons style={styles.place} name="Place" width="12" height="12"/>

const styles = StyleSheet.create({
  place: {
    marginTop: 4,
    marginLeft: 2,
  },
})

the position is changed, but it generates some annoying warning:
Warning: Failed prop type: Invalid prop `style` supplied to `SvgIcon`.

the work around is use in this way
<Icons style={[styles.place]} name="Place" width="12" height="12"/>

or
<Icons style={{marginTop: 4, marginLeft: 2,}} name="Place" width="12" height="12"/>

Sorry, I apparently missed this for 6 months :-. Will fix!

I just published 0.8.1 which fixes this issue


Add transaction for input-scan/output-scan package

scan package will be deprecated, so we can ignore it.

Abandoned


Feat/update user extensions

Pull Request Test Coverage Report for Build 142

27 of 29 (93.1%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.05%) to 91.024%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

user_extensions.go
13
15
86.67%

Totals

Change from base Build 139:
-0.05%

Covered Lines:
720

Relevant Lines:
791

💛  - Coveralls


Updating UI for CardUI costs not working correctly

For context, my CardUI scene has a label with the cost of the card and the font color should change to red if the player doesn't have enough energy to play the card and should be white if player can play the card.
In order to achieve this I added a method to the hand.gd script called update_playable_cards
func update_playable_cards(char_stats: CharacterStats) -> void:
	for card: CardUI in get_children():
		card.playable = char_stats.can_play_card(card.card)

This method is called, by the PlayerHandler, at the start of every turn, after the hand is drawn, and on the method that handles the card_played signal.
At the start of the turn, this seems to work fine, but if I play a card and then have no mana to play some of the remaining cards, those cards cost UI isn't updated. However, if I don't have enough mana to play any of the remaining cards, then it updates. It basically only seems to work if I can't play any of my remaining cards. This is only a visual bug though, because even if it shows I can play the card, if I don't have enough mana, the game doesn't let me play it.
Also, I only did everything until season 1, haven't started season 2 yet.
If you need any more info please let me know.
Any help would be really appreciated

@dsemiao I have the same issue, any updates on fixes?

Hey people,
I'll look into it today and get back to you asap!

I looked into this, with the season 1 ending code: https://github.com/guladam/deck_builder_tutorial/tree/season-1-code
And I didn't encounter this issue at all:

I think this might be a problem on your end. The relevant code is in the CardUI class.
Check the _set_char_stats() and _on_char_stats_changed() methods, these are responsible for updating the UI when the mana changes, it's not done in the PlayerHandler class.
Hope that helps. I will close this for now and let me know if I can do anything to help.

Thanks  for taking the time Adam! I actually just changed the card's modulate to make the whole thing transparent when it's disabled. Still not sure what the actual issue was, but I'm not code savvy enough to pinpoint it exactly.


Calling Update on an empty model creates malformed query

Given:
type Book struct {
    ID int64

    name *string
}

book := Book{
    ID: 1,
}

trying to update the model without any values generates an invalid query
db.NewUpdate().Model(&book).Where("id = ?", book.ID).Exec(ctx)

=> 'UPDATE "books" AS "book" SET  WHERE (id = 1)'

The same issue exists in go-pg as well.

What do you expect instead?

this is the expected result!

Perhaps you meant to write Name *string so the field is exported
type Book struct {
    ID int64

    Name *string
}

We could check number of fields but it is not clear what that improves. Closing for now.


Game takes 3 minutes to load and performances drops to 10 fps when combat text is showing

It worked perfectly before but now it's a disaster i'm so sad i LOVE this mod... What can I do without losing all my settings?

FIXED! For some reason, the addon had Num_Scroll_Areas = 65536 in its .ini file


Render pass device

Resolves #11, but I am not sure this is the correct approach

hm, I think BaseLayerType.__init__() should be called whenever a VolumetricLayer is created. If it doesn't, it's some sort of bug.
Here's why I think it should be called:
VolumetricLayer inherits from BaseLayerType, then calls super here.
Could you explain a bit why do you think it's not getting called?

Could you explain a bit why do you think it's not getting called?
I added a corgie_logger.debug and a pdb call to the init function for some tasks queued in SQS. The workers completely ignored it...

Ah, found it: https://docs.python.org/3.6/library/pickle.html#pickling-class-instances

When a class instance is unpickled, its __init__() method is usually not invoked.

Got it. Another reason to do away with pickle.
Let's adapt your approach for now, and I'll try to remove the pickle from the code base by the end of next week. This would make the tasks smaller, task serialization faster, and the workflow more intuitive.


Delete output directory

Clean the output directory before running.
Changing the parameters of the simulation and re-running will leave old plots, old folders, etc. that don't correspond to the simulation you are running presently.
Cleaning the output directory ensures that whatever is in that folder corresponds to the latest simulation.
Thanks to Coleman for highlighting this!

Great idea @tbarchyn


[RTL] Change direction of content in forms at runtime

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes and the overall coverage did not decrease.
[ ] All unit tests pass on CircleCi.
[ ] I ran all tests locally and they pass.

Build has failed, please check if SDK is released

Build has failed, please check if SDK is released
SDK is released locally : https://artifactory.corp.adobe.com/ui/native/maven-aemforms-release-local/com/adobe/aemfd/aem-forms-sdk-api/2<IP_ADDRESS>/
From where does it pick?
This one is public : https://mvnrepository.com/artifact/com.adobe.aem/aem-forms-sdk-api


fix: false positives on structs

Ignore structs which are not being used as test tables.
For example, here "1" and "2" are reported as test examples:
func TestStruct(t *testing.T) {
	type item struct {
		id   string
		name string
	}
	items := []item{
		{"1", "one"},
		{"2", "two"},
	}

	for _, i := range items {
		if i.id == "" {
			t.Fail()
		}
	}
}

Before

After

Hey @letmein and many thanks for this fix! ⭐


ISO C99 Standards Support

I am working on identifying where boost::format and sprintf differ in behavior.  I wrote a matrix test comparing standard sprintf to boost::format for purposes of ensuring that boost::format handles all of the format strings that sprintf does, and we're currently at about 41% pass rate.  This matrix doesn't test every possible combination of format modifiers yet - just one of each was enough.  Results are very early, and I will be working on improving this.
Here's some sample output from the test:
       Format String | RSLT | "printf"                              | "boost::format"                       | error info
---------------------+------+---------------------------------------+---------------------------------------+--------------------------------------------------
              % 1.5c | FAIL | "X"                                   | " "                                   | mismatch
             % 1.20c | FAIL | "X"                                   | " "                                   | mismatch
                % 2c | FAIL | " X"                                  | "  "                                  | mismatch
               % 2.c | FAIL | " X"                                  | "  "                                  | mismatch
...
                 %5u |      | "4294954950"                          | "4294954950"                          |
                %5.u |      | "4294954950"                          | "4294954950"                          |
               %5.2u |      | "4294954950"                          | "4294954950"                          |
               %5.5u |      | "4294954950"                          | "4294954950"                          |
              %5.20u | FAIL | "00000000004294954950"                | "4294954950"                          | mismatch
...
              %020Lf |      | "6543211234567.891602"                | "6543211234567.891602"                |
             %020.Lf |      | "00000006543211234568"                | "00000006543211234568"                |
            %020.2Lf |      | "00006543211234567.89"                | "00006543211234567.89"                |
            %020.5Lf |      | "06543211234567.89160"                | "06543211234567.89160"                |
           %020.20Lf |      | "6543211234567.89160156250000000000"  | "6543211234567.89160156250000000000"  |
                  %F | EXCP | "1234567.875000"                      | ""                                    | boost::bad_format_string: format-string is ill-formed
...
              %020LG |      | "0000000006.54321E+12"                | "0000000006.54321E+12"                |
             %020.LG | FAIL | "0000000000000007E+12"                | "0000000006.54321E+12"                | mismatch
            %020.2LG |      | "00000000000006.5E+12"                | "00000000000006.5E+12"                |
            %020.5LG |      | "00000000006.5432E+12"                | "00000000006.5432E+12"                |
           %020.20LG |      | "6543211234567.8916016"               | "6543211234567.8916016"               |

Failed Tests: 6707
Total Tests: 11401
Pass Rate: 41.2%

Read through the docs; sounds like the intention of the library is not to be a sprintf replacement (sad).   Closing this out.


add description env var RESTIC_PASSWORD_COMMAND

The environment variable RESTIC_PASSWORD_COMMAND works but has
not been documented yet. e.g. it could contain a command that
would fetch the password from a local user keyring
enhances: https://github.com/restic/restic/pull/2094

What is the purpose of this change? What does it change?

Was the change discussed in an issue or in the forum before?

Checklist

[x] I have read the Contribution Guidelines
[ ] I have added tests for all changes in this PR: n/a
[ ] I have added documentation for the changes (in the manual)
Answer: I suggest a little change to the manual
[ ] There's a new file in changelog/unreleased/ that describes the changes for our users (template here)
I think this one-line doc addition is not worht another changelog line
[ ] I have run gofmt on the code in all commits
[x] All commit messages are formatted in the same style as the other commits in the repo
[x] I'm done, this Pull Request is ready for review

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@604b18a). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #2394   +/-   ##
=========================================
  Coverage          ?   46.89%
=========================================
  Files             ?      174
  Lines             ?    14480
  Branches          ?        0
=========================================
  Hits              ?     6790
  Misses            ?     6678
  Partials          ?     1012

Continue to review full report at Codecov.

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

Eager to merge this as soon as the things I mentioned in my comment to the code are done 👍


How can I modify the tree using plot_phylo?

Hi Katy,
I am glad to see a project to merge the matplotlib and ete3, I have a question here. How can I reroot the tree with some groups using plot_phylo? plot_phylo could not parse a Tree() object into it. That means I could not modify the tree before plot it.
Thanks for your reply.

there is a parameter outgroup in ploy_phylo, but it can just specifies one leaf instead of muiltiple leaves.

Hi @klcym, sorry for my very slow response. Currently, you can't edit the tree directly with plot_phylo - I'd recommend opening the tree with ete3, making the edit and saving in newick format, then loading into plot_phylo for visualisation.
I'm working on a method to use multiple sequences as an outgroup, but I've not figured it out yet.


Add API to handle persistent Database

Signed-off-by: Subba Reddy Veeramreddy<EMAIL_ADDRESS>Description:  Add Issue/Feature description
Changes Proposed in PR:
Fixes: #Github issue id
General Checklist

[ ] Updated Added functionality/ bug fix in release notes
[ ] Added examples for new feature
[ ] Updated the documentation

CRD Checklist

[ ] Updated required CR schema

/azp run

/azp run


Check if 3D to 2D transformation correct

it is possible, that pixels that overlap after projection to 2D get assigned larger depth value. This would result in noise surfaces with potentially big outliers.

Transformation assigned at 3D to 2D projection arbitrary depth values for duplicate pixel coordinates after transformation. Cleaning function implemented, that choses the smallest depth values among duplicates for the projected 2D image.


[release-1.10] Use random names in Channel tests (#6972)

Backport from upstream

/assign @matzew


CASMHMS-6282: Update alpine base image to resolve CVE

IGNORE THIS PR - JUST USING FOR TESTING
Summary and Scope
Update alpine base image to resolve CVE
Issues and Related PRs

Resolves CASMHMS-6282

Testing
Tested on:

<development system>
Local development environment
Virtual Shasta

Test description:
TBD

Were the install/upgrade-based validation checks/tests run (goss tests/install-validation doc)?
Were continuous integration tests run? If not, why?
Was upgrade tested? If not, why?
Was downgrade tested? If not, why?

Pull Request Checklist

[x] Version number(s) incremented, if applicable
[x] Copyrights updated
[x] License file intact
[x] Target branch correct
[x] CHANGELOG.md updated
[x] Testing is appropriate and complete, if applicable

Closing this PR as it was replaced by https://github.com/Cray-HPE/hms-firmware-action-charts/pull/39


Compliance with fsspec's API

Closing, a lot of tests for file obj were added recently and should be enough for compliance.


[server] Implement AuthenticationService

Server:

activate the AuthenticationService and the AuthorizerService
implement Router -> Server authentication

when authentication in configured on the Venice Server the Router needs to be configured with this property
authentication.token=xxxxx
This is because it needs to authenticate.
It is expected that the token has super powers for router > server communications


EKFGSF ahrsAlignYaw() does not affect filter state

In EKFGSF_yaw.cpp, we have the following function:
void EKFGSF_yaw::ahrsAlignYaw()
{
	// Align yaw angle for each model
	for (uint8_t model_index = 0; model_index < N_MODELS_EKFGSF; model_index++) {
		Dcmf& R = _ahrs_ekf_gsf[model_index].R;
		const float yaw = wrap_pi(_ekf_gsf[model_index].X(2));
		R = updateYawInRotMat(yaw, R);

		_ahrs_ekf_gsf[model_index].aligned = true;
	}
}

Is it just me, or does all this math do nothing to alter the state of the filter? A rotation matrix is updated but never pushed back to the filter.
I presume R of each model is intended to be updated to the newly-calculated R?

Dcmf& R = _ahrs_ekf_gsf[model_index].R;

Means that R is a reference (note the &) to _ahrs_ekf_gsf[model_index].R, a rotation matrix of _ahrs_ekf_gsf, which is a member variable. Then, R =  is actually updating _ahrs_ekf_gsf[model_index].R.

Thanks, I read through that too quickly!


libredirect: Add support for Darwin

The library can be used also on Darwin using it like this:
NIX_REDIRECTS='foo=bar' \
DYLD_INSERT_LIBRARIES=${libredirect}/lib/libredirect.so \
DYLD_FORCE_FLAT_NAMESPACE=1 \
some_program

So let's actually not hardcade gcc and add Darwin to meta.platforms.
No other changes seem to be required.
Cc: @zimbatm, @edolstra, @dezgeg, @copumpkin

Success on aarch64-linux (full log)
Attempted: libredirect
Partial log (click to expand)
building
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/ani97cssh4p7dniflksk889f4rvxdgis-libredirect-0
shrinking /nix/store/ani97cssh4p7dniflksk889f4rvxdgis-libredirect-0/lib/libredirect.so
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/ani97cssh4p7dniflksk889f4rvxdgis-libredirect-0/lib
patching script interpreter paths in /nix/store/ani97cssh4p7dniflksk889f4rvxdgis-libredirect-0
checking for references to /build in /nix/store/ani97cssh4p7dniflksk889f4rvxdgis-libredirect-0...
/nix/store/ani97cssh4p7dniflksk889f4rvxdgis-libredirect-0

Success on x86_64-darwin (full log)
Attempted: libredirect
Partial log (click to expand)
/nix/store/l928iaj0m48lfb7dib6h7p22d50l566x-clang-wrapper-5.0.2/resource-root/include/stdarg.h:35:50: note: expanded from macro 'va_arg'
#define va_arg(ap, type)    __builtin_va_arg(ap, type)
                                                 ^~~~
2 warnings generated.
installing
post-installation fixup
strip is /nix/store/g5r4apl0za012ffs6ladinwa5w0m1l3k-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/g2af9n36xcdrasdchqd5pd76bziiyl9r-libredirect-0/lib
patching script interpreter paths in /nix/store/g2af9n36xcdrasdchqd5pd76bziiyl9r-libredirect-0
/nix/store/g2af9n36xcdrasdchqd5pd76bziiyl9r-libredirect-0

Success on x86_64-linux (full log)
Attempted: libredirect
Partial log (click to expand)
building
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/h1z3mhdvxa44xb6nb7wygpxrgz6ci9hi-libredirect-0
shrinking /nix/store/h1z3mhdvxa44xb6nb7wygpxrgz6ci9hi-libredirect-0/lib/libredirect.so
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/h1z3mhdvxa44xb6nb7wygpxrgz6ci9hi-libredirect-0/lib
patching script interpreter paths in /nix/store/h1z3mhdvxa44xb6nb7wygpxrgz6ci9hi-libredirect-0
checking for references to /build in /nix/store/h1z3mhdvxa44xb6nb7wygpxrgz6ci9hi-libredirect-0...
/nix/store/h1z3mhdvxa44xb6nb7wygpxrgz6ci9hi-libredirect-0

Success on x86_64-linux (full log)
Attempted: libredirect
Partial log (click to expand)
building
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/i0qwzfwxmbvn85i63yj5ml8bcv72lcll-libredirect-0
shrinking /nix/store/i0qwzfwxmbvn85i63yj5ml8bcv72lcll-libredirect-0/lib/libredirect.so
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/i0qwzfwxmbvn85i63yj5ml8bcv72lcll-libredirect-0/lib
patching script interpreter paths in /nix/store/i0qwzfwxmbvn85i63yj5ml8bcv72lcll-libredirect-0
checking for references to /build in /nix/store/i0qwzfwxmbvn85i63yj5ml8bcv72lcll-libredirect-0...
/nix/store/i0qwzfwxmbvn85i63yj5ml8bcv72lcll-libredirect-0

Success on x86_64-darwin (full log)
Attempted: libredirect
Partial log (click to expand)
/nix/store/l928iaj0m48lfb7dib6h7p22d50l566x-clang-wrapper-5.0.2/resource-root/include/stdarg.h:35:50: note: expanded from macro 'va_arg'
#define va_arg(ap, type)    __builtin_va_arg(ap, type)
                                                 ^~~~
2 warnings generated.
installing
post-installation fixup
strip is /nix/store/g5r4apl0za012ffs6ladinwa5w0m1l3k-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/zjv2hq60zi44r0f2bjlh6nm1216yfrmy-libredirect-0/lib
patching script interpreter paths in /nix/store/zjv2hq60zi44r0f2bjlh6nm1216yfrmy-libredirect-0
/nix/store/zjv2hq60zi44r0f2bjlh6nm1216yfrmy-libredirect-0

Success on x86_64-linux (full log)
Attempted: libredirect
Partial log (click to expand)
building
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/i0qwzfwxmbvn85i63yj5ml8bcv72lcll-libredirect-0
shrinking /nix/store/i0qwzfwxmbvn85i63yj5ml8bcv72lcll-libredirect-0/lib/libredirect.so
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/i0qwzfwxmbvn85i63yj5ml8bcv72lcll-libredirect-0/lib
patching script interpreter paths in /nix/store/i0qwzfwxmbvn85i63yj5ml8bcv72lcll-libredirect-0
checking for references to /build in /nix/store/i0qwzfwxmbvn85i63yj5ml8bcv72lcll-libredirect-0...
/nix/store/i0qwzfwxmbvn85i63yj5ml8bcv72lcll-libredirect-0

Success on aarch64-linux (full log)
Attempted: libredirect
Partial log (click to expand)
/nix/store/kqwp4p56pnrnpwq16rjcfsb4dfxc97g4-libredirect-0

Success on x86_64-linux (full log)
Attempted: libredirect
Partial log (click to expand)
'libredirect.so' -> '/nix/store/y0qqg5bv77lwzjz6cn14x0wpiv6lh8pm-libredirect-0/lib/libredirect.so'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/y0qqg5bv77lwzjz6cn14x0wpiv6lh8pm-libredirect-0
shrinking /nix/store/y0qqg5bv77lwzjz6cn14x0wpiv6lh8pm-libredirect-0/lib/libredirect.so
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/y0qqg5bv77lwzjz6cn14x0wpiv6lh8pm-libredirect-0/lib
patching script interpreter paths in /nix/store/y0qqg5bv77lwzjz6cn14x0wpiv6lh8pm-libredirect-0
checking for references to /build in /nix/store/y0qqg5bv77lwzjz6cn14x0wpiv6lh8pm-libredirect-0...
running install tests
/nix/store/y0qqg5bv77lwzjz6cn14x0wpiv6lh8pm-libredirect-0

Success on aarch64-linux (full log)
Attempted: libredirect
Partial log (click to expand)
'libredirect.so' -> '/nix/store/mx43z123cf2pa3g0pnpnjh8axi1lmq94-libredirect-0/lib/libredirect.so'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/mx43z123cf2pa3g0pnpnjh8axi1lmq94-libredirect-0
shrinking /nix/store/mx43z123cf2pa3g0pnpnjh8axi1lmq94-libredirect-0/lib/libredirect.so
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/mx43z123cf2pa3g0pnpnjh8axi1lmq94-libredirect-0/lib
patching script interpreter paths in /nix/store/mx43z123cf2pa3g0pnpnjh8axi1lmq94-libredirect-0
checking for references to /build in /nix/store/mx43z123cf2pa3g0pnpnjh8axi1lmq94-libredirect-0...
running install tests
/nix/store/mx43z123cf2pa3g0pnpnjh8axi1lmq94-libredirect-0

Failure on x86_64-darwin (full log)
Attempted: libredirect
Partial log (click to expand)
'libredirect.dylib' -> '/nix/store/qcbmwjzbdgghjnrl0z3ah38n5hiva176-libredirect-0/lib/libredirect.dylib'
post-installation fixup
strip is /nix/store/g5r4apl0za012ffs6ladinwa5w0m1l3k-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/qcbmwjzbdgghjnrl0z3ah38n5hiva176-libredirect-0/lib
patching script interpreter paths in /nix/store/qcbmwjzbdgghjnrl0z3ah38n5hiva176-libredirect-0
running install tests
Assertion failed: (stat(TESTPATH, &testsb) != -1), function main, file test.c, line 50.
/nix/store/8qai18dv0nqyw6s61g9p91n8684rnlg8-stdenv-darwin/setup: line 1305: 17906 Abort trap: 6           NIX_REDIRECTS="/foo/bar/test=/nix/store/acnfbicd84bnya2l2dq868b5l482qihw-coreutils-8.30/bin/true" DYLD_INSERT_LIBRARIES="$out/lib/libredirect$shlibext" DYLD_FORCE_FLAT_NAMESPACE=1 ./test
builder for '/nix/store/abn55bz07azlgx7i2bvbs4j1dgspnsi0-libredirect-0.drv' failed with exit code 134
error: build of '/nix/store/abn55bz07azlgx7i2bvbs4j1dgspnsi0-libredirect-0.drv' failed

I am going to back-port this to 18.09 unless there are objections

The install_name is wrong so the library won't be usable without patching stuff afterwards, on darwin something like this is needed to set it properly.
$CC ... -Wl,-install_name,$out/lib/libredirect$shlibext


Default port to 8888.

The dev server seems to expect the port to be 8888 so I guess it would make sense to make it the default.

Really? Dev server must run on different port then web app. If you have problem with clean checkout, please open a new issue.


Simplify Synchronizer Status

Simplify states to

Up to date -> app has finished catching up with the latest blockchain events and it's considered to be synced and waiting for new blocks to arrive
Syncing -> app is syncing a significant range of blocks
Refreshing. -> this is sync that is 1 or 2 blocks
Error -> some error has happened and can't be auto-resumed and needs user attention.

android counterpart https://github.com/zcash/zcash-android-wallet-sdk/issues/967

@pacu I guess you mean synchronizer status (aka SyncStatus) not state (aka SynchronizerState) right?

I was thinking about this. I am not sure if we can simplify it that much.
We either need to keep unprepared or say that prepare() must be called before each start. Without unprepared status the client doesn't know if it need to call prepare. We can say it must be called before each start.
Our current policy is that client apps shouldn't think much and simply render UI for the status that the SDK provides. To decide if Syncing or Refreshing should be used the SDK first must make to call to GRPC to fetch latest height. And that may take some time. So the client app calls start and nothing happens before GRPC call is finished and before the SDK switches to Syncing or Refreshing status. And for this time user see same UI, not any progress, nothing. We should have some kind of working or whatever status for which the client app should render some "in progress" UI.
I have no idea how to compute progress when we merge syncing, enhancing and fetching status to one. I agree that it would be easier for the client app.
I think we need to keep synced state. If we keep only "in progress" states then the client app doesn't know when the process finishes and when to render "process done" UI.

Our current policy is that client apps shouldn't think much and simply render UI for the status that the SDK provides. To decide if Syncing or Refreshing should be used the SDK first must make to call to GRPC to fetch latest height. And that may take some time. So the client app calls start and nothing happens before GRPC call is finished and before the SDK switches to Syncing or Refreshing status. And for this time user see same UI, not any progress, nothing. We should have some kind of working or whatever status for which the client app should render some "in progress" UI.

I think we can simplify this down.  When the SDK is first launched, it could report syncing as a heuristic.  It is highly likely the SDK is more than 1 block behind when a new synchronizer instance is constructed.
Refreshing is for the case that the user has been in the app for a while and it does periodic fetches of new blocks every ~30 seconds.  The goal is to prevent flickering during this periodic refresh, as the UI transitions from idle -> syncing -> idle currently.
The risk of flicker for app launch -> syncing -> idle is low because as you note the first fetch for largest block height is slower.  Also there's only 1 state transition here rather than two as in the case we're trying to handle.

If our goal is for clients to debounce Refreshing or show non intrusive UI cues, maybe the Status change could be Refreshing -> Syncing if there's work to do or Refreshing -> Up-To-Date if it's only refreshing.
we could treat every sync attempt as a refresh preemptively and then when the length of the block range to sync is determined we can send an update to the state and switch to syncing with the complete progress information.

We could argue that refreshing could be a helper function of a information-rich progress state.
struct SyncProgress {
   var currentProgress: Height
   var targetheight: Height
   var nowSyncing: Date
   var targetDate: Date
   var syncID: UUID
}

extension  SyncProgress {
   var isRefreshing: Bool {
        // return a bool by checking if this block range is negligible under some criteria
   }
}

then a client could actually update their UI by debouncing or filtering refreshing states
void setUpUI() {
    synchronizer.statePublisher
        .filter { !$0.progress.isRefreshing }
        .map { $0.asPercentage }
        .receive(on: DispatchQueue.main)
        .sink { [weak self] in
             self?.progressGauge.setProgress($0)
        }
        .store(in: &disposeBag)
}


Check format to all rs files under src

fixed-format of all missing files.
i don't have permissions but can someone with permissions can add this to the ci.yml file?
under line 35:
      - name: temporary workaround - fmt all files under src
        run: find src -type f -name "*.rs" | tr '\n' ' ' | xargs cargo fmt -- --check -l

Fixes seanmonstar/reqwest#1186

You could include a change to the workflows file in this PR. This line might be clearer (copied from tokio):
rustfmt --check --edition 2018 $(find . -name '*.rs' -print)

@seanmonstar updated the ci.yml i was working from gitpod, and got premessions.

@seanmonstar
it doesn't work.


unicode decode error - v09e

I updated to the newest release and I'm getting:
2024-06-04 21:34:32  ERROR     [__main__] A JuicePass Proxy task failed: UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 33: invalid start byte

With debug logging on, I see this as the last logged line: https://github.com/snicker/juicepassproxy/blob/master/juicebox_mqtthandler.py#L500, and the first non-ascii byte is \x8b

I suspect that my device may have updated and now it's using a new protocol, possibly encrypted. the format appears to be <device id>:v09e<binary>
I haven't been logging all the packets previously, but it was working previously and I saw others with a format like <device id>:v07:<plaintext>

Yes.  My older device started doing the same thing yesterday but the newer one is still ok.  I won't be able to give debug or anything until tomorrow evening but at least your report helped with my sanity.

By blocking traffic out to Enel X and rebooting, I was able to have it stay at v07 instead of getting updated to v08 (which is what it looks like my older unit changed to yesterday).  I have both EXPERIMENTAL and IGNORE_ENELX enabled but unsure how they play into it.  Will try to get more info later.

Can you provide a few example strings you are now getting?

It's not doing it anymore - but here's one of the packets I captured:
        0x0000:  4500 00dc 1a9e 0000 8011 99fc ac11 16b6  E...............
        0x0010:  ac11 169e 1656 1f6a 00c8 0000 3039 3130  .....V.j....0910
        0x0020:  3034 3230 3031 3238 3036 3630 3432 3733<PHONE_NUMBER>604273
        0x0030:  3233 3632 3035 3335 3a76 3039 6512 b10a  23620535:v09e...
        0x0040:  0000 0071 6b14 9327 0404 a809 cbcb b799  ...qk..'........
        0x0050:  5fd8 6b39 1e4b 5e60 6fd5 153a 81ec d625  _.k9.K^`o..:...%
        0x0060:  1eb2 bf87 da82 db9c eaef b268 caa8 f0c0  ...........h....
        0x0070:  1b53 8af4 8e45 d1ef 3ad2 8ca7 2a4f df05  .S...E..:...*O..
        0x0080:  2617 80fd 753b 3619 0636 8634 821b f6ca  &...u;6..6.4....
        0x0090:  da56 24ba e11f eb7d c975 cfe1 4e2c 305e  .V$....}.u..N,0^
        0x00a0:  b01a dcc7 b396 87dd c130 d66c c39b c2cc  .........0.l....
        0x00b0:  ac7f 903c b9b5 0adb 9a77 b95b 77bd 364b  ...<.....w.[w.6K
        0x00c0:  82dc be85 99dc 9a8a 880c c44e b0f0 4e8a  ...........N..N.
        0x00d0:  1d9f 4a63 0597 8a7f 3e3c 58d5            ..Jc....><X.

I was hesitant to share, since this leaks my unique id - but I guess there isn't any harm in it
I also have hex values from two separate packets after the v09e part:
12b10a000000716b1493270404a809cbcbb7995fd86b391e4b5e606fd5153a81ecd6251eb2bf87da82db9ceaefb268caa8f0c01b538af48e45d1ef3ad28ca72a4fdf05261780fd753b361906368634821bf6cada5624bae11feb7dc975cfe14e2c305eb01adcc7b39687ddc130d66cc39bc2ccac7f903cb9b50adb9a77b95b77bd364b82dcbe8599dc9a8a880cc44eb0f04e8a1d9f4a6305978a7f3e3c58d5

12b10a00000073480d38833df8ebed8add322332c5c9f0501b32e9b35b71d1d8d3e389f5b9002b42ee953b5d9f712ddd36ebcb9f0a8973eba739f388583429d3fcd4cd135f9e4d437ad6ad21c11ad8e89369252ada194b52436beeb67a15b4a24f85eae07ebeeb6270588c94e390fa6da00c831e290a8552bd49ce014db1aa70843ebb5db2b0dea0fa20d0ed00714ae3001c895bf54779d5d1449ee15bf486

They both start with a common prefix, and there are some common bytes throughout.

I was able to get my system back into the mode where it's sending v09u messages - I rebooted several times, but not sure what may have finally triggered it back to that mode.

As it returned just with reboots I suppose the firmware can send in both formats and depending of server response it will change the format.

That does seem likely, however if that's the case, it would be good to know more about which message does that so it could be blocked.
One thing I did change is that originally I was using juicenet-udp-prod5-usa.enelx.com as the target host and intercepting DNS for that. During my testing though, I also noticed juicenet-udp-prod3-usa.enelx.com being used, so I added that to my domain intercept list, and then rebooted and I think that's when it came back to the v09u messages.
I'm assuming the v09u means v9 unencrypted and v09e means v9 encrypted. Which would imply the version didn't actually change.

Removed the firewall blocks and rebooted again and I'm staying on v07 but ... I noticed something new.  My older unit (haven't checked the newer one) is now reaching out and getting what look like normal certs and what might be two new URLs:
https://juicenet-prod3-usa.enelx.com/v2/unit/[   MY ID   ]/data
https://juicenet-prod3-usa.enelx.com/v1/unit/[   MY ID   ]/keys
the key one returned a 64 hex character key and an expiration date of 2025-06-04T12:43:10.079Z which looks to be pretty close to one year from when things changed yesterday.  Maybe they turned on some testing a bit early?

to keep for reference, this URL on directory service that have an encrypted  element that changes the juicebox to encrypted protocol mode
https://directory-api.emotorwerks.com/v1/profiles/juicebox/DEVICE_ID/


Throws error when there is both an enterprise application and a managed identity present

Describe the bug
Command Name
az ad app credential reset
Errors:
more than one entry matches the name, please provide unique names like app id guid, or app id uri

To Reproduce:

Create an app registration
Create a secret for that app registration via the portal
Create a user assigned managed identity for that application
Try and modify the secret

The OData query executed under the hood is:
$filter=servicePrincipalNames/any(x:x eq '[APP_ID]') or displayName eq '[APP_ID]'

To ensure only service principals of type 'Application' are having their credentials targeted by this command the query should be modified to the following:
$filter=(servicePrincipalNames/any(x:x eq '[APP_ID]') or displayName eq '[APP_ID]') and servicePrincipalType eq 'Application'

Expected Behavior
The credential of the application should be reset
Environment Summary
Windows-10-10.0.19041-SP0
Python 3.6.8
Installer: MSI

azure-cli 2.20.0 *

Extensions:
azure-devops 0.18.0
interactive 0.4.4

Additional Context

@jiasli for awareness

I just hit this issue! Ouch. It's not a feature request. It's a bug.

Create a user assigned managed identity for that application

May I know how this is done? Based on my understanding, user-assigned identity is not bound to an application: https://docs.microsoft.com/en-us/azure/automation/add-user-assigned-identity
Are you creating a user-assigned identity with the same display name as the application?
The query $filter=servicePrincipalNames/any(x:x eq '[APP_ID]') or displayName eq '[APP_ID]' and error "more than one entry matches the name, please provide unique names like app id guid, or app id uri" are from the AD Graph implementation:
https://github.com/Azure/azure-cli/blob/74ea23bc805d57e3cf68cc9a4396141975acb580/src/azure-cli/azure/cli/command_modules/role/custom.py#L1697-L1703
The Microsoft Graph implementation doesn't accept display name anymore:
https://github.com/Azure/azure-cli/blob/98f7865402569ec9a6ae05ccdd0d27d5ea20927c/src/azure-cli/azure/cli/command_modules/role/custom.py#L1283
Using appId as the filtering keyword should work.

In my case the name of the user assigned identity was completely different than the name of the enterprise application and application registration. The user assigned identity was created at the resource group level.
Enterprise App Name: user-principal-name
App Reg Name: user-principal-name
App Reg Application ID URI: https://user-principal-name
Managed Identity Name: completely-unrelated-name
I'm not sure what the relationship was, but deleting the managed identity allowed the credential on the app reg to be reset with az ad app credential reset. Then the managed identity was created again.

How do you relate the user assigned identity with the application? Based on my understanding, user assigned identity is created by ARM while application is created AAD.

A user assigned identity is created within a resource group but you can interact with it like any other service principal in AAD.
We have downgraded our az cli builds to use 2.36 due to many issues in our scripts related to az ad and sub-commands. We have not had time to review the changes.
The specific command is
az ad app credential reset --id "${appId}" --append --years 1  --credential-description "blah"


2 invalid keys in stanza

crossServerChecksum and precompressBundles aren't recognised as valid keys in serverclass.conf

I'm not able to reproduce this.  Which .spec version are you using?

Terribly sorry for such a slow response. I am using spec version 9.0,extension version 0.3.2.
crossServerChecksum and precompressBundles in server class.conf in a stanza
[serverclass:foo:app:bar] are being highlighted in red while other configs are accepted OK.


HBASE-27099 The log printing pread/read cost time unit should be ms

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 25s
Docker mode activated.


chore: reduce number of CVEs in docker image

Description

How to test

Screenshots

Notes for developers and reviewers:

Think to update CHANGELOG.md before merge if needed !

/e2e --tests mnist,frontend

End to end tests: :hourglass_flowing_sand: STARTING


Building faild on cygwin

In file included from providers/implementations/storemgmt/winstore_store.c:27:
/usr/include/w32api/wincrypt.h:20:11: error: unknown type name ‘LONG’
   20 |   typedef LONG HRESULT;
      |           ^~~~
In file included from providers/implementations/storemgmt/winstore_store.c:27:
/usr/include/w32api/wincrypt.h:283:11: error: unknown type name ‘ULONG_PTR’
  283 |   typedef ULONG_PTR HCRYPTHASH;
      |           ^~~~~~~~~
/usr/include/w32api/wincrypt.h:284:11: error: unknown type name ‘ULONG_PTR’
  284 |   typedef ULONG_PTR HCRYPTKEY;
      |           ^~~~~~~~~
/usr/include/w32api/wincrypt.h:285:11: error: unknown type name ‘ULONG_PTR’
  285 |   typedef ULONG_PTR HCRYPTPROV;
      |           ^~~~~~~~~
/usr/include/w32api/wincrypt.h:628:5: error: unknown type name ‘DWORD’
  628 |     DWORD dwVersion;
      |     ^~~~~
/usr/include/w32api/wincrypt.h:630:5: error: unknown type name ‘BYTE’
  630 |     BYTE *pbOID;
      |     ^~~~
/usr/include/w32api/wincrypt.h:631:5: error: unknown type name ‘DWORD’
  631 |     DWORD cbOID;
      |     ^~~~~
/usr/include/w32api/wincrypt.h:636:5: error: unknown type name ‘BYTE’
  636 |     BYTE *pbInnerString;
      |     ^~~~
/usr/include/w32api/wincrypt.h:637:5: error: unknown type name ‘DWORD’
  637 |     DWORD cbInnerString;
      |     ^~~~~
/usr/include/w32api/wincrypt.h:638:5: error: unknown type name ‘BYTE’
  638 |     BYTE *pbOuterString;
      |     ^~~~
/usr/include/w32api/wincrypt.h:639:5: error: unknown type name ‘DWORD’
  639 |     DWORD cbOuterString;
      |     ^~~~~
/usr/include/w32api/wincrypt.h:643:5: error: unknown type name ‘DWORD’
  643 |     DWORD dwUse;
      |     ^~~~~
/usr/include/w32api/wincrypt.h:645:5: error: unknown type name ‘DWORD’
  645 |     DWORD cBits;
      |     ^~~~~
/usr/include/w32api/wincrypt.h:646:5: error: unknown type name ‘DWORD’
  646 |     DWORD dwFlags;
      |     ^~~~~
/usr/include/w32api/wincrypt.h:647:5: error: unknown type name ‘DWORD’
  647 |     DWORD dwReserved;
      |     ^~~~~
/usr/include/w32api/wincrypt.h:656:5: error: unknown type name ‘DWORD’
  656 |     DWORD dwBitLen;
      |     ^~~~~
/usr/include/w32api/wincrypt.h:657:5: error: unknown type name ‘DWORD’
  657 |     DWORD dwNameLen;
      |     ^~~~~
/usr/include/w32api/wincrypt.h:658:5: error: unknown type name ‘CHAR’
  658 |     CHAR szName[20];
      |     ^~~~
/usr/include/w32api/wincrypt.h:663:5: error: unknown type name ‘DWORD’
  663 |     DWORD dwDefaultLen;
      |     ^~~~~
/usr/include/w32api/wincrypt.h:664:5: error: unknown type name ‘DWORD’
  664 |     DWORD dwMinLen;
      |     ^~~~~
/usr/include/w32api/wincrypt.h:665:5: error: unknown type name ‘DWORD’
  665 |     DWORD dwMaxLen;
      |     ^~~~~
/usr/include/w32api/wincrypt.h:666:5: error: unknown type name ‘DWORD’
  666 |     DWORD dwProtocols;
      |     ^~~~~
/usr/include/w32api/wincrypt.h:667:5: error: unknown type name ‘DWORD’
  667 |     DWORD dwNameLen;
      |     ^~~~~
/usr/include/w32api/wincrypt.h:668:5: error: unknown type name ‘CHAR’
......

Command build below
cd openssl
./config
make -j8

I just add
#ifdef __CYGWIN__
#include <Windows.h>
#endif

at  providers/implementations/storemgmt/winstroe_stroe.c at line 26
after, I faced link error
Add Configurations10-main.conf
1563|         ex_libs          => add("-lcrypt32"),

then I Succeed build openssl.exe at cygwin terminal

Hope you can fix. Thanks !

@affggh
where did you add this line,
1563|         ex_libs          => add("-lcrypt32"),

@affggh
where did you add this line, I am still facing problem in CYGWIN
1563| ex_libs => add("-lcrypt32"),

Its in Configurations/Configurations10-main.conf
at line 1563

@affggh  Thanks for Reply.
But I already see that at Line number 1573,

After doing above changes to config file..
I am still receiving errors as attached.

@affggh Thanks for Reply.
But I already see that at Line number 1573,

this mingw target is not working on cygwin

After doing above changes to config file..
I am still receiving errors as attached.

did you add -lctypt32 on cygwin target

Yes,
I did add that line.. see below screenshot.

Yes,
I did add that line.. see below screenshot. Line Number : 1563

you should insert it at cygwin target，not mingw

Thanks Buddy!!
It working now..


fsautocomplete: fix build

Description of changes
fixes https://github.com/NixOS/nixpkgs/issues/271704
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

@marsam thank you for quick response !

Thanks for the fix @kirillrdy !


[OLS-871]  datacollection is off when there is no pull-secret

Description
Make data collection is off when there is no pull-secret.
Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library

Related Tickets & Documents

Related Issue #
Closes #

Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] PR has passed all pre-merge test jobs.
[ ] If it is a core feature, I have added thorough tests.

Testing

Please provide detailed steps to perform tests related to this code change.
How were the fix/results from this change verified? Please provide relevant screenshots or results.

/lgtm
/retest

/approve

/retest "Red Hat Konflux"

/retest

/lgtm

/approve
/override "Red Hat Konflux / ols-enterprise-contract / lightspeed-operator"


V6 xmatch6

Bringing Configs up to spec

Ok so I gave it a bit of creative 'rewiring' to get a piece of it back to originality. But really it's 6 or 1/2 dozen of the other. But it works.  The frequency is also back to the original state since 2 words match.  I tuned assert suggestions since more came back in the last count.


[BUG] AttributeError: 'TrackingConfig' object has no attribute 'speed'

Describe the bug
When trying to run the SDK object tracking example, I get the following error as soon as an object is detected:
Traceback (most recent call last):
  File "/home/pi/object_tracking.py", line 22, in <module>
    oak.start(blocking=True)
  File "/home/pi/sdkvenv/lib/python3.9/site-packages/depthai_sdk/oak_camera.py", line 353, in start
    self.poll()
  File "/home/pi/sdkvenv/lib/python3.9/site-packages/depthai_sdk/oak_camera.py", line 381, in poll
    self._oak.check_sync()
  File "/home/pi/sdkvenv/lib/python3.9/site-packages/depthai_sdk/oak_device.py", line 44, in check_sync
    sync.check_queue(block=False)  # Don't block!
  File "/home/pi/sdkvenv/lib/python3.9/site-packages/depthai_sdk/oak_outputs/xout/xout_base.py", line 91, in check_queue
    self.on_callback(packet)
  File "/home/pi/sdkvenv/lib/python3.9/site-packages/depthai_sdk/oak_outputs/xout/xout_tracker.py", line 78, in on_callback
    self._add_tracklet_visualization(packet, spatial_points, tracklet2speed)
  File "/home/pi/sdkvenv/lib/python3.9/site-packages/depthai_sdk/oak_outputs/xout/xout_tracker.py", line 119, in _add_tracklet_visualization
    if self._visualizer.config.tracking.speed and tracklet.id in tracklet2speed:
AttributeError: 'TrackingConfig' object has no attribute 'speed'

Minimal Reproducible Example
https://github.com/luxonis/depthai/blob/main/depthai_sdk/examples/NNComponent/object_tracking.py
Expected behavior
Show object tracker output on frame.
Attach system log
{
"architecture": "64bit ELF",
"machine": "aarch64",
"platform": "Linux-6.1.21-v8+-aarch64-with-glibc2.31",
"processor": "",
"python_build": "default Feb 28 2021 17:03:44",
"python_compiler": "GCC 10.2.1 20210110",
"python_implementation": "CPython",
"python_version": "3.9.2",
"release": "6.1.21-v8+",
"system": "Linux",
"version": "#1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023",
"win32_ver": "",
"packages": [
"blobconverter==1.4.1",
"boto3==1.26.137",
"botocore==1.29.137",
"certifi==2023.5.7",
"charset-normalizer==3.1.0",
"depthai==<IP_ADDRESS>",
"depthai-pipeline-graph==0.0.5",
"depthai-sdk==1.10.1",
"idna==3.4",
"jmespath==1.0.1",
"marshmallow==3.17.0",
"numpy==1.24.3",
"opencv-contrib-python==<IP_ADDRESS>",
"packaging==23.1",
"pip==20.3.4",
"pkg-resources==0.0.0",
"python-dateutil==2.8.2",
"pytube==15.0.0",
"PyTurboJPEG==1.6.4",
"PyYAML==6.0",
"Qt.py==1.3.8",
"requests==2.30.0",
"s3transfer==0.6.1",
"sentry-sdk==1.21.0",
"setuptools==44.1.1",
"six==1.16.0",
"types-PySide2==<IP_ADDRESS>.5",
"urllib3==1.26.15",
"xmltodict==0.13.0"
],
"usb": [
"NoLib"
],
"uname": [
"Linux rpi4 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023 aarch64"
]
}
Thanks for looking into it!

CC: @daniilpastukhov  - please check this out

Broken in commit: e8da50524d1ec7ae2e17c9e8df0987b8b4d5ff21


[TDX] [Kernel] Define the device tree kernel interface for the AP mailbox protocol

[Migrated from https://github.com/microsoft/HvLite/issues/315]
Need to define where we want to put the device tree discovery for the gpa of the mailbox protocol. The kernel will define the interface that underhill_boot will use to tell the kernel where the interface is for.

@jyiang5 initially posted on LKML (https://lore.kernel.org/lkml/20240806221237.1634126-1-yunhong.jiang@linux.intel.com/). The discussion digressed into using the proposed new enable-method for virtual devices. The proposed enable-method is not required to be used only on virtual devices. I can be used on any machine, physical or virtual.
Other architectures use the enable-method as a per-CPU property when describing the system on a device tree.
I will write an updated prototype of the new enable-method and try to get feedback from the maintainers.


Error during finetuning base model

Hi I encountered an error when I try to further finetune the base model. During validation check, there is a warning  Token indices sequence length is longer than the specified maximum sequence length for this model (599 > 512). Running this sequence through the model will result in indexing errors
How do I fix this ?
Log:
2022-04-15T21:01:58 INFO: m4c_textvqa:, 41100/41100, train/total_loss: 0.6898 (0.6971), train/m4c_textvqa/m4c_decoding_bce_with_mask: 0.6898 (0.6971), train/m4c_textvqa/textvqa_accuracy: 0.8406 (0.8330), val/total_loss: 6.9965, val/m4c_textvqa/m4c_decoding_bce_with_mask: 6.9965, val/m4c_textvqa/textvqa_accuracy: 0.4969, max mem: 6524.0, lr: 0., time: 01m 07s 802ms, eta:
2022-04-15T21:01:58 INFO: Stepping into final validation check
2022-04-15T21:01:58 INFO: Evaluation time. Running on full validation set...
Token indices sequence length is longer than the specified maximum sequence length for this model (599 > 512). Running this sequence through the model will result in indexing errors
intemediate model saving skipped. utiles/checkpoint, 41101
2022-04-15T21:05:21 INFO: m4c_textvqa: full val:, 41101/41100, val/total_loss: 6.5700, val/m4c_textvqa/m4c_decoding_bce_with_mask: 6.5700, val/m4c_textvqa/textvqa_accuracy: 0.4969, validation time: 04m 31s 394ms, best iteration: 41000, best val/m4c_textvqa/textvqa_accuracy: 0.499082
2022-04-15T21:05:21 INFO: Restoring checkpoint
2022-04-15T21:05:23 INFO: Starting inference on test set
  0%|                                                                                | 0/180 [00:00<?, ?it/s]2022-04-15T21:05:25 WARNING: /home/cybertron/TAP/pythia/modules/losses.py:93: UserWarning: Sample list has not field 'targets', are you sure that your ImDB has labels? you may have wanted to run with --evalai_inference 1
  "Sample list has not field 'targets', are you "

2022-04-15T21:05:25 WARNING: /home/cybertron/TAP/pythia/modules/losses.py:93: UserWarning: Sample list has not field 'targets', are you sure that your ImDB has labels? you may have wanted to run with --evalai_inference 1
  "Sample list has not field 'targets', are you "

Hi @soonchangAI ,
"Token indices sequence length..." is a warning related to the tokenizer. You could safely ignore that.
The validation process looks good to me. "Sample list has not field 'targets'" is also expected as there is no GT on the test set.

Thanks


Amazon add move remove

Combined the following branches into one:

sc-3312/amazon-s3-remove-file-s
sc-3314/amazon-s3-move-file-s

Remove functionality seems to be good.
Unable to test "move_file.py" in full due to issues with regex_match. Left what notes I could.
Biggest thing is testing for all cases of regex/exact match when moving the file(s).

When using the regex_match functionality and when supplying the destination-file-name, the script needs to rename the matches with the supplied destination-file-name and the _1, _2, _3, _n suffixes. It is currently using the original name and appending the suffix

https://github.com/shipyardapp/databricks-blueprints/blob/main/databricks_blueprints/upload_file_to_dbfs.py Example of the most recent Blueprint using the shipyard_utils functionality for this.

@wrp801 Good to merge, increment the tag, publish the Blueprints on Shipyard, and update the requirements to use the new tag.

Will do!

@ericelsken - Can you approve this so I can merge?

Done.


cargo fix: Pass --all-targets by default

After hearing from a few people that they expected cargo fix to fix their tests by default and discussing this on discord, we now want to pass --all-targets by default.
The main disadvantage of this is that it hides some of the actual complexity -- while you get a lot more fixed code, optional features and #[cfg(…)] parts are still not covered.

Another disadvantage (from my perspective, unless I'm mistaken) is that it makes it irregular with, say, build.


Better qubit and measurement lo interface

What is the expected enhancement?
I find the current lo interface confusing to use. I think it is a combination of naming and functionality. My main complaint is that:

qubit_lo_freq and meas_lo_freq seem to serve the same purpose as schedule_los

This can be confusing for users. I think it may be better to replace
qubit_lo_freq and meas_lo_freq by qubit_freq_est and meas_freq_est and then have the default behaviour to be too use these to create and pad schedule_los if not supplied. This way there is only one explicit behaviour to set the los for assembly (schedule_los).
Thoughts @nkanazawa1989  and @itoko?

I remember why we didn't take the approach of

to replace qubit_lo_freq and meas_lo_freq by qubit_freq_est and meas_freq_est

is separation of schedule_los from backend and immutability of schedule_los , i.e. schedule_los should receive backend in its constructor to know qubit_freq_est and meas_freq_est .
Currently everything about los is done in the assembler (because the assembler gets backend), but we don't need to output los in qobj when user los are default because default values will be automatically assigned in the backend.
My another concern is naming issue (pulse.configuration.LoConfig), because #2650 will add another configuration for scheduler. We will have many schedule configuration s defined in different places and in different context. This is also confusing to use. I think these configurations should be combined.

The issue is naming. Right now it appears there are three ways to set the schedule lo qubit_lo_freq, meas_lo_freq and schedule_lo_freq. I understand the reason for having all three, but we should make it clearer that the qubit_lo_freq is really the frequencies of the qubits that the LO will default too.

My another concern is naming issue (pulse.configuration.LoConfig), because #2650 will add another configuration for scheduler. We will have many schedule configuration s defined in different places and in different context. This is also confusing to use. I think these configurations should be combined.

I don't really see the need for the users to ever use this class. They should be able to just provided a dictionary of channel:frequencies. Perhaps we could hide it?

qubit_lo_freq and meas_lo_freq are appeared only in qobj, so I think they are hidden from users unless the user directly assemble qobj. But I agree

the qubit_lo_freq is really the frequencies of the qubits that the LO will default

The only reason to have LoConfig class is self validation of frequency range. If we create pulse job validator, we don't need the class.

I don't think the above addresses my concerns. qubit_lo_freq and meas_lo_freq are arguments to assemble in conjunction with schedule_los this is confusing as these are really the qubit and measurement frequencies that as a matter of protocol we default to if schedule_los are not provided. Perhaps these should be default_qubit/meas_lo_freq?

I understand your point. I agree. We need to simplify the configuration of los. qubit_lo_freq and meas_lo_freq can be used to set los which is common in all experiments, while schedule_los is used to set los depending of experiment.
As far as I understand,

(1) nothing
this will set backend default qubit_lo_freq and meas_lo_freq as common configuration.

(2) qubit_lo_freq and meas_lo_freq, without schedule_los
this will set custom qubit_lo_freq and meas_lo_freq as common configuration.

(3) single schedule_los, without qubit_lo_freq and meas_lo_freq
this will set custom schedule_los as common configuration - just same as (2).

(4) n schedule_los of the same frequencies, without qubit_lo_freq and meas_lo_freq
this will set qubit_lo_freq and meas_lo_freq for each experiment configuration, but this will give the same configuration as above (just increasing the size of qobj).

(5) qubit_lo_freq and meas_lo_freq, with n schedule_los
this will overwrite backend default qubit_lo_freq and meas_lo_freq, and overwrite them by schedule_los in each experiment configuration.

now we have too many options to set lo configuration, and we should simplify this. As (3) can cover (2), we might be able to deprecate qubit_lo_freq and meas_lo_freq from arguments.
And I don't like the name qubit_frequency because this can be intentionally detuned from it. This should be drive_frequency and meas_frequency.

Yes, I agree. The other subtlety is that if we only allow schedule_los the user must provide an lo for each qubit/measure channel. This is what I was thinking of when I was suggesting keeping qubit_freq_est and meas_freq_est as these are what the backend is going to use create the default lo. Do you think this is an issue?

I agree that drive_freq and meas_freq are the most accurate, we should support this at least in the user API. I also find schedule_lo confusing, and have been thinking about this problem

What does schedule_los do that cannot be done with the others?

Schedule_lo right now is essentially a dictionary that is a mapping of {channel: frequency}. schedule_los can be a list of these. Right now if you do not specify all Drive and Measure channels, it will default qubit_lo_freq or meas_lo_freq which are typically set to qubit_freq_est and meas_freq_est (this is what is done if just a backend is provided).

We are also able to complement schedule_los using the backend defaults inside assembler. In this case we don't need qubit_lo_freq and meas_lo_freq in arguments. We can specify a single schedule_los to overwrite backend default. On the other hand, I also feel it is reasonable to rename them to have schedule_los and default_los in the arguments.
I think we have three approaches (examples are how to overwrite default qubit drive[1] and apply frequency sweep of qubit drive[0]).
1. Rename qubit_lo_freq and meas_lo_freq to default_*
default_los = backend.defaults().qubit_freq_est
custom_los = default_los.copy()
custom_los[1] = 5.1

schedule_los = []
for drive_lo in drive_los:
    schedule_los.append({system.drives[0]: drive_lo})

qobj = assemble(schedule, backend, default_meas_lo_freq=custom_los, schedule_los=schedule_los)

Pros:

Default lo frequencies are clear to users.
Minimum workload.

Cons:

Different formats for lo configuration - default los are List[float], while schedule_los is List[Dict[PulseChannels, float]].
Need to specify default frequencies for all channels.

2. Remove qubit_lo_freq and meas_lo_freq from arguments and replace by qubit_freq_est and meas_freq_est.
schedule_los = []
for drive_lo in drive_los:
    schedule_los.append({system.drives[0]: drive_lo, system.drives[1]: 5.1})

qobj = assemble(schedule, backend, schedule_los=schedule_los)

Pros:

Interface for lo configuration is unified.

Cons:

Default lo frequencies are not clear to users.
No implicit way to set default los (giving a single schedule_los will implicitly set default).

3. User LoConfig class for both default and schedule dependent
default_los = {system.drives[1]: 5.1}

schedule_los = []
for drive_lo in drive_los:
    schedule_los.append({system.drives[0]: drive_lo})

qobj = assemble(schedule, backend, default_los=default_los, schedule_los=schedule_los)

Pros:

Default frequencies are clear to users.
Same data format for default and schedule_los (interface becomes clean).

Cons:

Large workload.

@lcapelluto I agree that schedule_los is bit confusing, but this is sometime very useful. e.g. when we do frequency sweep of qubit drive, only schedule_los enables us to combine all frequency sweeps in a single job. This is extremely useful to minimize a drift. Currently schedule_los consists of a list of LoConfig (when we provide los with python dictionary, LoConfig instance is generated internally). The reason we have this class is (1) to validate frequency range, and (2) to guarantee immutability. I think these are not mandatory.

In general, this problem would be overcome if for each pulse channel we could specify the frame and sideband with which it should be applied. Then we could track these frames and sidebands separately (as we do already internally).

Related to #3467. I'm not sure if the PR #3468 addresses the problem of frame. @eggerdj, this conversation may be interesting to you.

PR #3468 does not address the problem of frame.
After reading this conversion here is what I think would make sense from a physics point of view. Let's assume that the aim of PulseChannel is to generate Re[exp(i 2pi f j dt + phase) * d_j]. Then,

Drive channel should default to the estimate of the qubit frequency called qubit_freq_est.
Measure channel should default to the estimate of the readout resonator's frequency meas_freq_est.
At assemble time, the user can override the default frequencies. This should be done with a dict data structure to avoid having to specify the frequency of the channels we do not wish to change. I would almost be tempted to call this dictionary initial_channel_frequencies.

Consequences:

For 1. and 2. I don't believe that we need to give assemble an input variable with the default frequencies. It seems that defaulting to qubit and resonator frequencies is the natural thing to do.
Point 3. implies that all schedules in a job have the same initial frequency.
Point 3. has some interesting consequences for validation, especially when the user can change f through SetChannelFrequency. From a validation perspective, and in the context of IQ mixing, the valid range for initial_channel_frequencies would be determined by the output range of the RF source (plus/minus sideband if one really wants to be nitpicky). Then any change to the frequency f (made through SetChannelFrequency) would have to be limited to the initial channel frequency, say f0, plus/minus the bandwidth of the AWG. This methodology of setting and initializing frequencies and changing them using SetChannelFrequency has the advantage of reflecting what is happening in the hardware. It allows you to accomodate setups with IQ mixing as well as setups with direct signal generation (a la Tek70k).

The one aspect I am still unclear on is how do we properly handle frames when changing frequencies. Consider the situation below for a cross-resonance gate with control i and target j.

For coupled qubits i, j we currently expose a drive channel for each and then a control channel coupling the two
In our physical hardware the control channel is actual the drive channel for i
Instead if we expose just the drivechannels to properly implement the CR gate we must be able to change the frequency and phase of drivechannel i to that of drivechannel j.

I don't think this is captured within the current SetFrequency instruction. It may make more sense to define a frame object, which has a frequency and a frame that evolves. Channels could then be assigned a frame.


Revert "Revert "Revert "Revert "Use common tranport for TlsClient""""

Reverts vespa-engine/vespa#21326

@geirst Retrying this one now that Supervisor shutdown has been fixed

👍


gzip with --best the operator.tar docker file

Closes: https://github.com/istio/istio/issues/18143

@sdake: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e_operator
65a93fc0aa94f2fa82082b5c2294ce7dd11508b9
link
/test e2e_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

In response to a cherrypick label: new pull request created: #435


cmd/compile: data race at ssagen.deferstruct

#!watchflakes
post <- builder ==  "linux-amd64-racecompile" && `WARNING: DATA RACE` && `deferstruct`

Split from #60235.

Probably related to CL https://golang.org/cl/510539 . cc @rsc @mdempsky

Note that this is a recent regression, not a longstanding bug: the watchflakes timestamps are misleading because they take only the subrepo commit time into account. (Filed as #62116.)


docs(readme): adding python requirements to the docs

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


fix: identification of Genius X and 10000

Genius x: https://community.home-assistant.io/t/oral-b-integration-entities/485017/27?u=lash-l
10,000: https://github.com/home-assistant/core/issues/86242
Side thought: maybe it is worth changing the default identification to "Unknown toothbrush" rather than the 7000 series.

Side thought: maybe it is worth changing the default identification to "Unknown toothbrush" rather than the 7000 series.

I'm fine with that change, but lets do it after we don't have any more patch releases bumps since this change can go into a patch release and that probably shouldn't

@bdraco Release failed. Perhaps because I had amended a commit? Could that have broken anything?


Training on TGIF-QA / FrameQA

Hi,
Thanks for your great work. I have no problem using the code for MSVD-QA / MSRVTT-QA / the 3 other tasks of TGIF-QA, but as I train on TGIF-QA for FrameQA subtask, the loss quickly becomes nan (after about 80% of the first epoch), and the accuracy is 0. Do you have an idea why it happens?

Hi,
Thank you for your interest in my work and sorry for the issue you got.
My guess is that it is due to the gradients exploding. I could not reproduce the issue on my PC so I'm not sure if the following solution helps. Can you please try to set the max_norm in gradient clipping (nn.utils.clip_grad_norm_ in train.py) to a lower value, say 8 or even lower? Also, did you use my extracted features or you did it yourself?

I tried to reduce the gradient clipping (up to 3) but it keeps on happening. I do use your extracted visual features and processed the linguistic features as indicated.

Hi,
Thank you for reporting the issue.
It looks like I uploaded the wrong files that cause the problem. I've just re-uploaded new files. Can you please download new files and try again.
Thank you!

Hi,
Thank you for reporting the issue.
It looks like I uploaded the wrong files that cause the problem. I've just re-uploaded new files. Can you please download the new files and try again?
Thank you!

Thanks for the quick fix, it is now indeed working :)

Hi,
I have another question. And what is the accuracy of the TGIF-QA dataset you have trained on your machine? The accuracy of the training on my machine is very different from the paper.

Hi,
The accuracy is pretty much the same as those reported in the paper. There are some small differences (some better, some worse) between my public code and local code but they should not be too large.
I would recommend you to extract visual features yourself using commands in the README to reproduce performance reported in the paper. If you find any issue, please feel free to open an issue on github.
Thanks.

Okay, Thanks.

Hi,
I downloaded the code as well as provided extracted features and run all experiments on TGIF-QA again. Here are the results that I got:
Action: 75.8 ; Transition:  82.1; Count: 3.83; FrameQA: 55.8
Cheers.

Hi,
Thank you for your answer, because I tested three times and the results are  different. This should be my mistake, I will re-download all files and re-train them.


ROS2 support

@grammers Any plans for ROS2 support !
Had any chance to test in ROS2 ?

Yes branch ros2_msgs. The name is misleading but it is the full pkg.
It is working in the same way as for ros1. However, the support scrip (path to point) is not ported.


Set coral-tflite-delegate version to 0.0.1

Also depend on version ^0.0.1 of tfjs-tflite-node instead of a link: dependency.
We don't have any release automation set up for the sig repo yet, so I manually created a pair of branches similar to how we release in the monorepo. This PR will fail presubmits until the tfjs-tflite-node package is released at 0.0.1.

This change is

This PR was supposed to be created against the coral release branch instead of main.


Adding content on proxy-based auth

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

I last used this in pre-1.0 days, but I also needed
opendistro_security.auth.type: proxy

in kibana.yml


Is it possible to write middleware to instrument decoding errors?

Question
I'd like to add telemetry to my app to report issues where an API response is missing a required key or otherwise has decoding errors. Ideally I could write middleware to achieve this, but from what I've been able to tell, middleware can't intercept decoding errors.
In a perfect world, the server handling the API requests would always return 100% spec-compliant responses, never introducing breaking changes, but mistakes happen.
How would you suggest I add this telemetry to my client application using swift-openapi-*?

Hi @jpsim,
you're right that a middleware won't be the solution here, as transports and middlewares still work with generic HTTP requests and responses, and only the type-safe layer closest to your code turns that into values of your generated types.
If you want to e.g. emit metrics for specifically decoding errors, you can catch ClientError, which, as its underlyingError will have the original DecodingError thrown by JSONDecoder. I'd suggest logging it together with the causeDescription.
So, in code, you could do something like:
@main struct HelloWorldURLSessionClient {
    static func main() async throws {
        let client = Client(serverURL: URL(string: "http://localhost:8080/api")!, transport: URLSessionTransport())
        do {
            let response = try await client.getGreeting()
            print(try response.ok.body.json.message)
        } catch let error as ClientError where error.underlyingError is DecodingError {
            print("The reason for this request failing was the following decoding error: \(error)")
            // Increment your metric here.
            // Rethrow the original error.
            throw error
        }
    }
}

Yes, I can catch decoding errors at the call site like this, but that will lead to a lot of duplication.
This seems like a perfect fit for middleware conceptually, where other metrics and instrumentation can easily be added for all endpoints without needing the call sites to explicitly handle those cases.
Consider this a feature request to consider having centralized handling of decoding errors 🙏
And thanks for all your efforts in making this library ❤

Thanks for the kind words 🙂
If we were to add a middleware at the suggested layer, do you have ideas of what the signature could be?
Thinking out-loud here, but if we made it generic, somehow matching the raw HTTP one:
protocol Middleware: Sendable {
    func intercept(_ input: Sendable, operationId: String, next: (Sendable) async throws -> Sendable) async throws -> Sendable
}

Would that be useful? I wonder if the as? casting you'd need to do in the body of it would actually be useful/acceptable.
Opinions/ideas welcome here, also cc @simonjbeaumont.

Could we keep the type information by using generic parameters?
func intercept<Input: Sendable, Output: Sendable>(
  input: Input,
  operationId: String,
  next: (Input) async throws -> Output
) async throws -> Output {
    // Middleware could transform or log input, output or errors here
    return try await next(input)
}

The Client type needs to have an array of these middlewares that all run on every request to every operation. But these Input/Output types are per-operation.
Today, we have a property var middlewares: [any ClientMiddleware] on the underlying client. In my less-than-ideal scenario, that would be var middlewares: [any Middleware], for example.
What would that array signature be in your example? How would the Client code iterate through them?

I think with my suggestion, you could keep var middlewares: [any ClientMiddleware] since the generic parameters are defined on the function, not the protocol, so it doesn't add any generic constraints to the protocol itself.

Sorry, I'm still not sure I understand how it'd actually work. Could you try to open a draft PR to the runtime library with your experimental change, and maybe that'll help me get it? 😇

Proof of concept here: https://github.com/apple/swift-openapi-runtime/pull/99
I basically just took the shortest path I could find that would allow me to hook into decoding errors in a centralized place. I suspect you may want to go a different direction that may be a better fit conceptually for the project, but I'll leave that to you to decide.

Oh right, if you don't need the Input/Output when handling these errors, then yes we could totally do that.
A few thoughts:

should this cover encoding errors as well, and errors such as a missing header when it was required?
should the method itself throw, to allow you to handle the error and rethrow a different one (or the same one)? Maybe the method should return an error to ensure we always have something to rethrow after the handler returns.
should the error be ClientError, which has more useful context, or just the underlying error?

Yeah let's discuss, this is definitely an interesting direction.

These are no doubt important questions for you to answer as a library author. From my perspective, any answer to those questions would satisfy my need to add instrumentation and alerting to api response decoding errors.

Oh right, if you don't need the Input/Output when handling these errors, then yes we could totally do that.
A few thoughts:

should this cover encoding errors as well, and errors such as a missing header when it was required?
should the method itself throw, to allow you to handle the error and rethrow a different one (or the same one)? Maybe the method should return an error to ensure we always have something to rethrow after the handler returns.
should the error be ClientError, which has more useful context, or just the underlying error?

Yeah let's discuss, this is definitely an interesting direction.

Users can already catch and unpack the error today; the complaint wasn't that it wasn't possible, but that it was tedious to wrap every call like this. For this reason, I think that allowing the user to convert to a different error doesn't add much value. Same argument goes for whether this error is wrapped or unwrapped.
IIUC, the request is to instrument this particular error flow to log or collect metrics? In that case, any hook we provide should probably be purely an optional side-effect, so a void function.
I have a couple of questions of my own:

If we're providing this as an optional function hook that users can provide, why make it specific to this error? Are there more places where such a handler could be beneficial.
From an API perspective, could we position this as a middleware still (cf. a function hook), even if it means we need to do some things behind the scenes? E.g. ErrorMiddleware(_ handler: (any Error) -> Void).
If it's just instrumentation that users are after, should we consider adding "actual" instrumentation to the runtime library, i.e. by depending on Swift Metrics and emitting metrics for these sorts of things with dimensions for the operationID and the kind of error?

All great points. If we say that this is purely a read-only action (no transforming of errors), then maybe something like this? (Naming to be bikeshed separately)
protocol ClientErrorDelegate: Sendable {
  func requestSerializationDidThrow(_ error: ClientError) async throws
  func transportOrMiddlewareDidThrow(_ error: ClientError) async throws
  func responseDeserializationDidThrow(_ error: ClientError) async throws
}

And then you could optionally provide one of these on the Configuration struct. WDYT?

We'd probably also provide a server variant:
protocol ServerErrorDelegate: Sendable {
  func requestDeserializationDidThrow(_ error: ClientError) async throws
  func transportOrMiddlewareDidThrow(_ error: ClientError) async throws // Not entirely sure how this one would work, TBD
  func responseSerializationDidThrow(_ error: ClientError) async throws
}

If it's just instrumentation that users are after, should we consider adding "actual" instrumentation to the runtime library, i.e. by depending on Swift Metrics and emitting metrics for these sorts of things with dimensions for the operationID and the kind of error?

Comprehensive metrics would be great, but much broader scope compared to my near-term needs
Ideally comprehensive metrics would be pluggable like ClientTransport currently is to:
a. avoid the cost of the swift-metrics dependency for users who don't need it
b. allow for alternative metrics implementations

Also I consider fine-grained metrics (number of requests, failure #s, timing data histograms, etc) to be fairly distinct from and very differently actionable compared to decoding errors where a server is returning non-conformant responses. So I can see some benefit in having a unified metrics solution but that's not necessary for this level of instrumentation.

Discussion happening on the runtime PR: https://github.com/apple/swift-openapi-runtime/pull/99


Keyboard hides input after autofill on Android

Describe the bug
When using autofill on Android with Google password manager inside KeyboardAwareScrollView, keyboard behaves like this:

pops up, input scrolls above keyboard (correct)
autofill prompt: keyboard hides, text input does not loose the focus, saved credentials selection appears as a bottom sheet
click on any saved cred, it gets filled into the text field (no onFocus or onBlur fires)
password manager bottom sheet hides, keyboard appears again
this time keyboard covers input field as scrollview does not react to keayboard second appearance
[optional]: on any input keyboard avoidance restores

Code snippet
export const App = sentryWrap(() => {
  return (
    <Providers>
      <LoginOTPEmailScreen />
    </Providers>
  );
});

function LoginOTPEmailScreen() {
  const [value, setValue] = useState("");

  return (
    <KeyboardAwareScrollView keyboardShouldPersistTaps="handled">
      <View style={{ height: 600 }} />
      <TextInput
        accessibilityLabel="Text input field"
        style={{ borderWidth: 1 }}
        value={value}
        autoComplete="username"
        keyboardType="email-address"
        autoCorrect={false}
        autoCapitalize="none"
        onChangeText={setValue}
      />
    </KeyboardAwareScrollView>
  );
}

export const Providers = ({ children }) => {
  return (
    <GestureHandlerRootView style={{ flex: 1 }}>
      <SafeAreaProvider initialMetrics={initialWindowMetrics}>
        <KeyboardProvider statusBarTranslucent>{children}</KeyboardProvider>
      </SafeAreaProvider>
    </GestureHandlerRootView>
  );
};

Repo for reproducing
N/A, full code provided in the snippet.
To Reproduce
See the video and follow steps in description
Expected behavior
On the second keyboard appearance keyboard avoidance works
Screenshots
https://github.com/user-attachments/assets/ccbf2599-4f4e-4800-aad9-0d3f320398bd
Smartphone (please complete the following information):

Desktop OS: Windows 11
Device: Samsung A41 and any other android
OS: Android 13
RN version: 0.75
RN architecture: old
JS engine: Hermes
Library version: 1.14.2

Additional context
"react-native-gesture-handler": "^2.20.2",
"react-native-reanimated": "~3.15.5",
"react-native-safe-area-context": "^4.12.0",

@antonandreyev thank you for the issue! I'm able to reproduce it 🎉
I opened a PR with a potential fix - https://github.com/kirillzyusko/react-native-keyboard-controller/pull/667
May I ask you to test it and let me know how it works for you?

Yes, I can confirm it helped! But also I can note little regression in the actual app:
Status bar loses (or gains) color when password manager is visible (it returns back once manager is hidden). Context:

react-navigation 6
react-native-screens 3.35.0
statusBarColor: "transparent" in screen options of native stack navigator

I will try to find time tomorrow to create a reproduction repo

I will try to find time tomorrow to create a reproduction repo

Thank you, because StatusBar doesn't change a color in my example app 🙂
Feel free to open a new issue then 🙌 (I'll merge a PR and this issue will be automatically closed)


3D viewer for schedule based commits

This might be an actual limitation of the viewer, but we should definitely support the viewer when using the parameter updater.
See: https://speckle.community/t/parameter-updater-sync-revit-schedules-with-excel/5978/3

Closing this ticket as we are moving to Jira to reduce noise. You can access it there.


Unable to use ingress using metallb - it gets <IP_ADDRESS>

Hi there
I have enabled ingress & metallb
microk8s enable metallb:<IP_ADDRESS>-<IP_ADDRESS>
microk8s enable ingress

Now when creating ingress, it uses <IP_ADDRESS>. Is there a way to make ingress use MetalLb to expose an external ip?
Used this description: https://microk8s.io/docs/addon-ingress
I have looked at:
microk8s kubectl -n ingress edit configmaps nginx-load-balancer-microk8s-conf
But with out any luck.
Thanks in advance
What Should Happen Instead?
Ingress will expose a Loadbalancer incl. external ip

Hello,
Have you checked the doc[0] with the metallb/ingress examples?
Using the doc, my lab below:
kubectl  get svc -n ingress
NAME      TYPE           CLUSTER-IP      EXTERNAL-IP     PORT(S)                      AGE
ingress   LoadBalancer   <IP_ADDRESS>   <IP_ADDRESS>   80:30440/TCP,443:32443/TCP   42s
[0] https://microk8s.io/docs/addon-metallb

Hi @JCzz
Note that the IP address of the ingress is purely informative. You can access the ingress using any of the node IPs.

Thanks both @neoaggelos and @pedrofragola
I do in fact have:
kubectl get svc -n ingress
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
ingress LoadBalancer <IP_ADDRESS> <IP_ADDRESS> 80:30440/TCP,443:32443/TCP 42s

Sorry, I did not mention this as I disregarded it as I can't see how it is a "normal" ingress.
The yaml configuration is as a service as described here:
https://microk8s.io/docs/addon-metallb
But I dont see any way to define the path?
Also why pointing at 80:30440?
So I looked at this:
https://microk8s.io/docs/addon-ingress
hoping that it would pickup from the metallb and create an external ip(I have seen this for cloud providers).
But this one, is the one creating an ingress for <IP_ADDRESS> and not using metallb.

Hi @JCzz sorry for taking long to reply here.
So, microk8s enable ingress deploys nginx-ingress with the daemonset mode, which means that you can use ports 80 and 443 on any cluster node to access the services, no need to get a separate loadbalancer service.
If you create more than one ingress (and there is no conflicts between them), then they will work as expected.
80:30440 is just a port mapping that Kubernetes creates for the services, you can consider this an implementation detail.

Thanks @neoaggelos


Manage 2.0 OAS versions in Postman

To be executed after issue #140:

[ ] Postman: create new version with name "2.0.0_spec" for documenting the published state
[ ] Postman: create new version with name "2.0.1" for future work

Completed.


Add license

I'm adding a license as you suggested on Twitter.

Thanks. Kept forgetting about this!!


Typekit doesn't load

I think diverselevant.herokuapp.com and www.diverselevent.org need to be added as allowed domains.

Yep, added those and think it works now. (Though it's only used for a backup font in the title.)


Allow a number to be pressed to select an account [Enchancement]

When the following dialog is displayed allow the user to press 1-9 on the keyboard to select one of the first nine entries

Originally that was actually the purpose of having them numerated int he first place... I'm not sure why in the end I ended up not adding the feature but I'll be doing it in the next release.
Thanks for the suggestion.


User Should Be Notified When Transactions Are Orphaned

Currently when a transaction is orphaned, the existing transaction is just left in the list until the client restarts. zcoind needs to be modified so that it emits events in this situation, and then zcoin-client should remove the transaction from the list or mark it somehow as orphaned and untrustworthy.

Thinking about solutions to this: I could add the stateWallet call as a publisher method, and under any circumstance that it occurs, the client will clear it's tx list and repopulate with it's contents. Then in the daemon when reorg is detected, it's triggers this event. How does that sound

Somewhere along the line the behaviour has changed to correctly marking orphaned transactions as unconfirmed. Closing.


invalid location, status 400 returned from WPT when HA sends "IE8" for location parameter

My httparchive instance is sending the default "IE8" as the location parameter but my WPT private instance was returning status 400 and complaining that location parameter is invalid.  To unblock I've deleted the location parameter from the submitTest function so now WPT just uses its default, but I'm sure there is a proper fix.

For private instances, you need to customize the settings in bulktest/bootstrap.inc.


Optimize cleanup_range of TiKV.

Development Task
When PD acquires one peer in TiKV removes itself from its raft-group, TiKV needs to delete all data of this peer after the conf-change has finished. TiKV would delete all SST files overlap with the range of region, and then deletes rest keys key by key, which will degrade the performance of apply-thread. So we need to check that whether the number of keys that need to be deleted is too large, and if there are too many keys need to be deleted, we shall write all of them into SstFileWriter and ingest it into RocksDB rather than write them into memtable directly.

/found customer


Add custom Button and Box component variants

https://github.com/chakra-ui/chakra-ui/issues/2456#issuecomment-725407887

Looks like I can't add variants to Box hmm
https://github.com/chakra-ui/chakra-ui/issues/2456

Superseded by #93


Some benches have images which are more than one media type.

While going through the list of benches with no media type (#307), I discovered some benches which have only one image and most of it appears to be "view from the bench" but also part of it is "close-up of the inscription". I set them to "view from bench" as that's what they mostly are. But perhaps someone can think of reasons why it would be better for them to be classed as "close-up of the inscription".
https://openbenches.org/bench/288
https://openbenches.org/bench/286
https://openbenches.org/bench/285
https://openbenches.org/bench/284
https://openbenches.org/bench/283
https://openbenches.org/bench/282
https://openbenches.org/bench/281

Thanks for going through all of those - very impressive!
I think for the ones where it is uncertain either leave them blank or use your best judgement. It's always going to be a little fuzzy.


ENH: New modes for extract_label_time_course

I'm proposing to added some new modes to the SourceEstimate.extract_label_time_course method and appreciate any feedback. Specifically, I would like to add weighted-mean and weighted-mean-flip modes that would compute a (flipped) weighted-mean for each label with weights given by the values of the label. This functionality would be useful for instance to weight the signals in each label proportional to their distance from the center of the label.

Sounds reasonable to me

I see conceptually the reason but do you have some evidence that it's
actually useful / helpful on data?

@wronk has some evidence coming out any day now. But even without a
publication it seems useful for aiding simulation studies, no?
On Jun 22, 2016 4:07 AM, "Alexandre Gramfort"<EMAIL_ADDRESS>wrote:

I see conceptually the reason but do you have some evidence that it's
actually useful / helpful on data?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/issues/3326#issuecomment-227672494,
or mute the thread
https://github.com/notifications/unsubscribe/ACQZXjtd1JHZUoIGz81ZB6J8WHTPOokAks5qOO1KgaJpZM4I7KRk
.

well I am bit reluctant to add methods / options for our users unless it's really what we recommend to use. Let's try to limit confusion.
my 2c
so I did not say no but I'd like to be able to explain why we offer this option.

I'm find tabling this issue for now. It just seemed like an easy way to add in a lot of flexibility that has come up recently for generating synthetic data.

Fine by me


Always update (allow for controlled components)

Proposed fix for https://github.com/airbnb/rheostat/issues/76.

Yup - adding that now.  Thanks.

Updated original test to reflect new behavior.  Code coverage is complaining because the removed lines were covered which shifts the % down slightly.  That can be addressed if folks agree this change actually makes sense.

Any word on when this can be incorporated? It would help me out!

This will need a rebase on the command line - the "update branch" button adds a merge commit, unfortunately.

It looks like you rebased your merged branch on top of your fork's master, instead of on top of this repo's master - I'll rebase it for you now.

thanks - sorry realized that and then got pulled away.


Fixed Typo in README

Changed depandencies to dependencies in readme.md

@all-contributors please add @HOSENUR for docs


Revert "ArrayWrapper Constructor, add, get, and set methods + Unit Te…

…sting" this is a great class and I'm learning loads

git merge main

Is there a reason this pull request is reverting a change?


A bunch of syntaxes not working

command /proxytest:
        permission: *
        trigger:
                send "%bungee servers%"                 #works
                send bungee "%player%" to "lobby" #works
                send "%bungee players%"                 #works
                if bungee "%player%" is online:         #doesnt work
                        send "hi12" to bungee "%player%"
                send "hi" to all bungee players          #doesnt work
                send "test" to bungee "%player%"    #works

pretty much using the default config, paperspigot 1.13 and 1.12 (tried both), skript 2.3-alpha4 and skungee 1.0.7d

the if statement returns false btw, not none

Skript 2.3 is still experimental and I believe that Skungee is only tested and made for 1.12, so you shouldn't be using Skript 2.3 if you're using Skungee. Use dev37c or dev36 since they probably will work. But @TheLimeGlass should know if I'm completely wrong.
Proof is that the first 1.13 Skript update was a month ago, and the last Skungee update was also a month ago ¯_(ツ)_/¯

Skungee handles the majority of it's processing on the Bungeecord, not Spigot. If the syntax are not working, there will most likely be a console error, that is what I need. Skungee hasn't been tested on the alpha versions either, but doesn't use Skript that much, just to relay the information.

Fixed in 1.0.7e


Preview freezes while recording video on Samsung tablet (SM-T580)

I am testing the app on SM-T580 and while recording video the preview freezes and the video does not get recorded.
It gets frozen when record button is pressed. I believe this happening while the camera is autofocusing. If I wait for the camera to finish focusing and then press record button, it works as expected.
The app works perfectly fine on my other device where the camera has no autofocus function.
Is there a way to turn the autofocus off.

The demo project is updated. Please check it.


Cloud Backup.

-It needs a text here always. When I am touching cloud backup, nothing is happening.

-Verified this in dev app v1.5.0(254)


msgpack-cxx: 6.0.0 -> 6.1.0

Diff: https://github.com/msgpack/msgpack-c/compare/refs/tags/cpp-6.0.0...cpp-6.1.0
Changelog: https://github.com/msgpack/msgpack-c/blob/refs/tags/cpp-6.1.0/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 242753 run on x86_64-linux 1

1 package built:

msgpack-cxx


Take Action revisions (to dev)

nb @cgettings and @etorem - based on our conversations this week, merging TA changes to dev. When it rebuilds, can you please take a look at it and lmk if any final thoughts/comments before we merge to production? Thanks.

The tags are above the Take Action stuff, but we were going to put them below.
The social share buttons don't have any content. The URL fields are all empty, and the email shows this in the body:

<nil>, by <nil>
<nil>

%!s(<nil>)

Ah! I need to pass the dot in to the partial call with {{- partial "socialshare" . -}}
Thanks for catching that. I'll also flip the keywords.

I think this is looking good!


[Suggestion] Desktop app will be helpful  more

Desktop app will be helpful  more
Thanks for this

It should not be very difficult to make this into a desktop app, of course ui refactor and improvement to fit desktop size is needed. As of now this is not a proirity

Desktop app will be helpful more
Thanks for this

In this case you can make Medusa a PWA...