Whole new way of computing a polyline arrow interior.

How did I get roped into this?  It has nothing to do with anything I'm working on.
Fixes #3491
Possible continued crazy ideas:

[x] Outlines (color + width) would be a good idea to add to this, and would make the arrow head and line pop a little better.  Also given this new method, the outline should be able to hold a constant width even around the arrow head and interface with the rest of the line, the same way that fuzz does now.  Previously there was a sharply aliased boundary between the head and the line, which is fixed here.
Would be nice someday to add a uniform to control headLength
Would be nice someday to add a uniform to control centerAmount which I guess should be renamed to centerWidth or some such.

Don't try to read this as a line-by-line diff.  The whole body has been replaced by new math.

Thanks for the pull request @emackey!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

How did I get roped into this? It has nothing to do with anything I'm working on.

:laughing: I guess I'm just that charismatic.

outlineColor and outlineWidth have been added to the uniforms at the primitive level.
There's a default 1-pixel width black outline.  The previous arrow had an unintentional dark blur around it, on account of blending against transparent black.  So, the new default looks somewhat similar to the previous effect, except it's crisp and controllable by uniforms.

Since outlines work, you can now do hollow arrows.
var viewer = new Cesium.Viewer("cesiumContainer");
var scene = viewer.scene;
var polylines = scene.primitives.add(new Cesium.PolylineCollection());

polylines.add({
  positions: Cesium.Cartesian3.fromDegreesArrayHeights([
    -120.0,
    35.0,
    500000,
    -80.0,
    35.0,
    500000,
  ]),
  width: 80.0,
  material: Cesium.Material.fromType(
    Cesium.Material.PolylineArrowType,{
      color: Cesium.Color.fromAlpha(Cesium.Color.GOLD, 0.3),
      outlineColor: Cesium.Color.GOLD,
      outlineWidth: 4,
    }
  ),
});

Looks awesome @emackey the lines are definitely much nicer and crisper.
There are some issues with horizon views and ending up with an arrow head on each side, from your Sandcastle:

Yep, I believe those are known issues with the way polylines generate their texture coordinates.

Or maybe it's an artifact of the line being too short for its own head...

Well it's... less terrible?  CI still running.

I’m not seeing the arrow at all on my iPad. I can try desktop Safari tomorrow.

The arrow worked on my kids' iPad (Pro or something?  2016-era iPad, I can't keep track of their generations).  More testing always welcome.

Weird.  I tried both my iPhone Xs running 13.4.1 (model MTAL2LL/A) and iPad Pro (10.5 inch) running 13.4.1 (model MQDT2LL/A)
Can anyone else with an iPad/iPhone give a try and confirm if they see the arrow?

@shunter Any chance you can test this demo on your iPhone or other iOS gear?
It should look like this:

For comparison, here's a similar demo in master with the blurry solid-color arrow.

No polyline at all.  iPad Air 2 and iPhone 7.  I checked the console and there were no related errors (some 404s about missing JS source map files)

Thanks again for your contribution @emackey!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @emackey!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

I'm at a stalemate on this.  I presume it's some issue between GLSL and older iOS, but it could be the branch, and I have no hardware that can reproduce it (we have 3 iPads here circa 2017, all show the arrow).
If it's not salvageable, feel free to close this.

I believe the next version of Safari is getting a new angle-based WebGL backend.  So I'm okay with just leaving this open and revisiting as soon as that update is out.  I appreciate the effort either way @emackey!

Thanks again for your contribution @emackey!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Merged master in, just in case #9064 fixed anything here.

Thanks @emackey!  Unfortunately not.  But I still hold out hope the next version of Safari will (since there's a big WebGL overhaul).
I also wonder if there is some undiscovered bug in Cesium that is causing this, (vs the WebGL implementation)

Thanks again for your contribution @emackey!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @emackey!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @emackey!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @emackey!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @emackey!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @emackey!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @emackey!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @emackey!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @emackey!
No one has commented on this pull request in 90 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 90 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @emackey!
No one has commented on this pull request in 90 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 90 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @emackey!
No one has commented on this pull request in 90 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 90 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @emackey!
No one has commented on this pull request in 90 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 90 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @emackey!
No one has commented on this pull request in 90 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 90 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

I was curious about this PR since Safari is now using ANGLE and has much better WebGL support. I merged in main and the arrow now shows up on iOS. So aspects of this PR is a huge improvement over what's in main. There are still some weird behavior at certain angles that someone might look into, but I feel like this PR is something we can revisit sometimes soon.

Thanks again for your contribution @emackey!
No one has commented on this pull request in 90 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 90 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @emackey!
No one has commented on this pull request in 90 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 90 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @emackey!
No one has commented on this pull request in 90 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 90 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

I'm closing this for now as it's quite out of date with main. If we wish to revisit this in the future, let's open a fresh PR. Thanks all.


Error when training yolov8-seg in validators.py

Hi!
Describe the bug
I used sparseml-nightly version <IP_ADDRESS>30404 , but I got an error after passing the first epoch of yolov8 segmentation training, which is in the file sparseml/yolov8/validators.py .
Environment

OS: Ubuntu 20.04.1
Python version: 3.8.10
SparseML version or commit hash: sparseml-nightly <IP_ADDRESS>30404
ML framework version(s): torch 1.9.1

Errors

@Landaunn yes, this has come to our attention lately. We know the root cause and will be patching it asap.

Hey, @Landaunn the fix is in #1522 . We will probably land it today, but if you wish, you can already introduce those changes locally to your repo.


[FEAT] Multiline flashcards with table inbetween

Is your feature request related to a problem? Please describe.
When using tables in multi line flashcards the empty lines enforced by obsidian cuts off the top of the card.
This is how it has to be made
- Question opening
                   <-- Empty line needed to make the table render in obsidian
| a   | b   |
| --- | --- |
| c   | d   |
Question continued
??
Answer

As a result the flash card starts from the table cutting off the 'question opening'
Describe the solution you'd like

A way for multi line flashcards to incorporate/recognize the empty line before tables
A way to manually include an empty line in a multi line card
2.1. A character/string used before the empty line
2.2. A character/string to define beginning and ending of the flash card

Additional context

A related issue : https://github.com/st3v3nmw/obsidian-spaced-repetition/issues/122

I am dealing with this issue as well. Currently there is essentially no way to include tables into flash card answers as far as I can tell.

+1 .. I have a table in the answer section and currently not able to render it

Although it hasn't been finalised, there is progress at https://github.com/st3v3nmw/obsidian-spaced-repetition/pull/1012

I think the issue was fixed.
Though, based on issues and documentation it's still open, however I managed to achieve required behavior in flash cards.
@ronzulu  to confirm.
Header
??
Question 1
Table
?
Answer
table
+++

Not sure what is a callout, I've recently started using obsidian and spaced repetition.
Here is the full syntax of my example:
`
Q6 - Returns over 3 Years
??
A fund receives investments at the beginning of each year and generates returns for three years as follows:

Year of Investment
Assets under Management at the Beginning of each year
Return during Year of Investment

1
USD 1,000
15%

2
USD 4,000
14%

3
USD 45,000
-4%

Which return measure over the three-year period is negative?
A. [[Geometric Mean|Geometric Mean Return]]
B. [[TWR|Time-weighted rate of return]]
C. [[IRR - MWR(r)|Money-Weighted Rate of Return]]
?
C. [[IRR - MWR(r)|Money-Weighted Rate of Return]]
Solution

[[Geometric Mean|Geometric Mean Return (GMR)]]: This measures average compounded growth. Here, GMR ≈ 7.9% (positive), as it averages the returns over the three years without factoring in the size of each year's investment.

[[TWR|Time-Weighted Return (TWR)]]: Similar to the GMR, TWR ≈ 7.9% (positive), as it eliminates the impact of cash flows, focusing only on performance.

[[IRR - MWR(r)|Money-Weighted Rate of Return (MWR)]]: MWR considers cash flow timing and amount. Since a large investment was made in Year 3, which had a negative return, MWR reflects the negative impact on the investor's experience, yielding an MWR ≈ -2.12%.
+++
`

Wow, it looks like having a manually defined 'end' tag for the flashcards (+++ for you)  turns the reverse multi line tag into a manual 'start' tag.
@ronzulu I haven't seen this mentioned in the settings, but even if it's a bug it works. I'll hold off on closing this until your verdict.
@IDZorin a callout is a native obsidian feature; Heres's the link to the official website detailing it.
Wraping a table in a callout 'fills in' the empty spaces, so I was using it as a workaround.


Error when login to a management cluster with server endpoint .

Bug Report
I'm trying to remotely log in to a management cluster using the Server endpoint and it failed (see below error message ) However, I can successfully login into the same management cluster with the kubeconfig .  (I haven't integrated AD authentication (LDAP) for this management cluster)
Also, I have tested remotely logging in to a different management cluster which has enabled LDAP and it worked (It prompted a web-based authentication for AD ). Does that mean I can only use server endpoint if we have integrated LDAP?
Expected Behavior
Should be able to access management cluster remotely via Server Endpoint.
Steps to Reproduce the Bug
Create a management cluster without Authentication (LDAP) integration.
Try to login to it with Server Endpoint (tanzu login)
Screenshots or additional information and context
1st : Unsuccessful with server endpoint.
2nd : Successful with kubeconfig to the same management cluster ,
PS C:\Users\lpmha> tanzu login
? Select a server + new server
? Select login type Server endpoint
? Enter server endpoint https://<IP_ADDRESS>:6443
? Give the server a name tanzuwin6
✖  Error creating kubeconfig with tanzu pinniped-auth login plugin: failed to get pinniped-info: failed to get pinniped-info from the cluster
Error: exit status 1
✖  exit status 1

PS C:\Users\lpmha> tanzu login
? Select a server + new server
? Select login type Local kubeconfig
? Enter path to kubeconfig (if any) C:\Users\lpmha\Downloads\config
? Enter kube context to use tanzuwin6-admin@tanzuwin6
? Give the server a name tanzuwin6
✔  successfully logged in to management cluster using the kubeconfig tanzuwin6

Environment Details

Build version (tanzu version): v0.9.1
Deployment (Managed/Standalone cluster):  Managed
Infrastructure Provider (Docker/AWS/Azure/vSphere):   vSphere
Operating System (client): Tried with both Ubuntu /  Windows

Diagnostics and log bundle
✖  Error creating kubeconfig with tanzu pinniped-auth login plugin: failed to get pinniped-info: failed to get pinniped-info from the cluster

@ankeesler - is this something you can help with? Or @vuil, can you help route it to the right person? Thanks!

@prkalle can you PTAL as well?

ah i think i remember what the issue is here. that failed to get pinniped-info from the cluster happens when the pinniped package has not been installed on the cluster, i.e., when using tanzu login --server https://<mgmt-cluster-addr> we expect that the pinniped package has already been installed.
this is probably not a fair assumption on our part, and we should also give better error messages. perhaps we should open an issue in tanzu-framework to improve this 1) ux and 2) error message?

Does that mean I can only use server endpoint if we have integrated LDAP?

so the answer is yes, as of right now, you need to have setup the pinniped package on your cluster in order to use tanzu login --server https://<mgmt-cluster-addr> flow

I agree with @ankeesler on giving a better error message and currently tanzu login only works when cluster is configured with pinniped.

Thanks everyone! I'll get a new issue opened up in tanzu-framework and keep this one here so we can track and make sure it gets into a TCE release.

Thank you all for your feedback.

We'll use this issue to track https://github.com/vmware-tanzu/tanzu-framework/issues/1444
Thanks again for bringing this to our attention!

I know we are tracking in the other bug so is it ok for this to get stale.


ZERO mAP issue of object detection model with kitti dataset (Nvidia Digits 4 on AMI)

Hi everyone,
I'm trying to train car detection model with example tutorial below.
https://github.com/NVIDIA/DIGITS/tree/digits-4.0/examples/object-detection
But mAP always shows ZERO while 30 epoch with about 6373 training data.
If anyone answer my questoins below, I will do appreciate.

Is this common issure or only happen to my model? And how to improve mAP score?
Is there any steps to change check carefully in this tutorial?

I also attached my caffe outputlog and picture of my mAP graph.
Thank you for your help.

caffe_output (1).log

Hi kzya32.
I was in for trouble like you asked.
I have been not able to understand this problem since then, but I could solve this problem.
1.You need to make a networkmodel in the same way that you talked.
2.You need to do again this but,
when you choice network, please choice the networkmodel that you made(the networkmodel that learned 30epoch)

Hi aa14074,
I had tried your method, but it does not work. I still get 0 mAP value.
Did you solve this problem @kzya32 ?
Thanks.

Any update on this? I am having the same issue


fix(staking): page inconsistencies

https://sovryn.monday.com/boards/2218344956/pulses/2273556093

Looks pretty good, but there is still a state where the vests table is displayed as empty, it should either show a loading text or the you have not vests text.

Re-reviewed this and noticed that withdraw buttons are missing for some assets in the Fee Claiming block (tested this on mainnet)

Amount to withdraw is 0, do you prefer on still being able to see the button?


Fix multi-selection doesn't correctly show in the inspector

Fix #47555
Fix selection not correctly  showing in the inspector when using shift key select first node or deselecting node until last selection.
The problem also appears in master.
They caused by #32908.

The problem also appears in master.

The PR should be made for the master branch then, as the PR template describes. Fixes should always be made in master in priority, that's the main development branch.


Closing an issue which has open dependencies does not show any error

Gitea Version
1.16.0+dev-819-g3a0dee01e
Git Version
No response
Operating System
No response
How are you running Gitea?
try.gitea.io + 1.15.9 on https://Codeberg.org
Database
MySQL
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Description
https://try.gitea.io/fnetx/dependencytesting/issues/2
If an issue depends on another one which is not closed, trying to close the issue with dependencies fails but does not show any helpful error in the UI. This might be confusing to users, they might either miss the issue wasn't closed, or wonder why it cannot be closed when they don't notice the dependencies.
Screenshots
No response

This is a regression due to #17643 - we should be handling the dependency error in the callers.


[Accessibility] [Reset Password] The form field constraints/errors are not associated with their fields programmatically.

Steps to Reproduce

Enable NVDA screen reader.
Open page in Google Chrome.
Activate the "Reset Password" button without inputting any information in form fields.
Navigate through form fields using TAB or TAB + SHIFT.
Notice that no error is announced when focusing fields.

Current Behavior
The field input elements make no reference to the constraints and error messages associated with them. Screen reader users are not informed that the inputs have errors when they navigate through the form.
Expected behavior/code
Authors should use an aria-describedby attribute on the input elements with an ID reference to the associated constraints/errors. Follow the best practices for accessible form error identification.
Environment
Chrome 92, Windows 10, NVDA 2020.4
AEM Core Components v. 2.17
Affected Users
Screen reader users
WCAG SC
1.3.1 Info and Relationships

Tracked via CIF-2351


Notes on reading data in Testbench

readmemh reads .mem which is same as text with newline delim
file needs to be in xsim folder
need to use  blocking statement when reading

Read data incorrect

Code:
https://github.com/dayalannair/FMCW_FFT_Radar/blob/5672fe550288c4748f2c9ae143796b73d0a87feb/FMCW_FFT_Radar.srcs/sim_1/new/UART_AXIS_TB.sv#L50-L81

Solved
mem in wave shows the last sample at the top

ERROR with shift

The above was generated with code:

This indicates that the shift is shifting the hexadecimal number and not its binary form. This must have something to do with the memory read. Seems like memory read stores the value as a set of hexadecimals instead of as a single hexadecimal value.

the shift is shifting the hexadecimal number and not its binary form

The statement makes no sense.  It's one and the same thing.  If you shift by 8 bits, that is 2 hex places.

True...when I set data hold as shown for data_hold1, it comes out to 00000800 and when I set it as shown above, it comes out the same but now data_hold1 is somehow correct. Will be an interesting fix

maybe needs a clk edge wait inside loops

Fixed for the shifting case and also got it working for the split into bytes case


Avatar changes by users are not applied when posting through webhook

Applies to:
Using webhook URLs to spoof avatars and usernames from IRC when matched to Discord usernames in the server.
What was expected:
User changes avatar on a whim, bot spoof should use the new avatar.
What happened instead:
The bot doesn't pick up the new picture, it uses the generic discord profile picture instead, until it is restarted.
Is this something that can be fixed? It's been amazing so far, but my server staff got pretty irritated just recently because someone changed their avatar and the bot started posting their messages with no profile pic. This ended up looking like spam/issues with the bot, when it seems it's just "caching" the old URL for the profile picture and isn't updating when it's changed.

Here is an example where a user tested by changing their avatar, then sending a message shortly after; the avatar change broke the avatar spoofing and made it default back to the default discord avatar.

The issue was with too big avatars not displaying, regex replacing the size to be always 128x128 fixes the issue, PR: https://github.com/reactiflux/discord-irc/pull/511

I looked around and couldn't find any Discord documentation on the max size for webhook images. It seems particularly strange that it would be different from the limit for user avatars. Can you confirm that this is still an issue, it's consistently replicable by using a large avatar, and that it's fixed by reducing the size of the avatar?

Updated and confirmed this is still an issue  in #511

Fixed in 88fecf3aa18fed509d6a70bc335b3b6bf11a3e2b, hopefully! Please get back to me if this is still an issue. I'll look into cutting a patch release with this change if I have time, but otherwise please try the master branch.


Providing values for additional fields

I'd like to use #[convert(into(...))] to convert into a struct that has one additional field, which I'd set to its default value.  Something akin to serde's #[convert(default)] could help here, though I'm not set as to what the best solution could be, since precisely when deriving Into the field is missing from the struct.  Maybe something like #[convert(into(...), default="field1 field2")]?
More context might give ideas: this is for a custom serde deserialization, in which the struct representation has an additional field computed from deserialized ones.  The idea is for the deserializer to return PublicStruct{computed=|| (), ..raw_struct.into()} - it is slighly wasteful indeed having to specify a default value for the computed field just to get it ignored, and hopefully the compiler will just optimize the useless away, but that's Into.

Thinking about it... that forced-handling of additional fields in my use-case does point to a different approach to the problem: a macro that would expand to a "set of initializers" (surely not the right terminology), could at the same time serve as basis for an implementation of #[convert(...)] and as a replacement for my usage of the struct update syntax - something like:
PublicStruct{computed=|| (), copy_fields!(raw_struct)}

I'd like to use #[convert(into(...))] to convert into a struct that has one additional field, which I'd set to its default value. Something akin to serde's #[convert(default)] could help here, though I'm not set as to what the best solution could be, since precisely when deriving Into the field is missing from the struct. Maybe something like #[convert(into(...), default="field1 field2")]?

I believe i cover this already - https://github.com/voidpumpkin/structural-convert/blob/05f0a23ba5b9e39db8577a9965272a500f0c7aa0/tests/into_struct_default.rs#L6

But overall my goal with this macro/crate is to optimize the "dumb" manual conversions.
When something more complex or custom is needed, I by design expect the user to opt out of the macro and write the conversion themselves.


Language dropdown

Still a WIP
Tasks

[x] Have the dropdown show up on click rather than on hover
[x] Fix bug where dropdown triangle will show up before click on mobile only
Fixed, sort of - the JS sets the display attribute on page load to hide the triangle. Proper fix would be to fix it in CSS.
[x] Move the language navbar item to the right of the navbar, instead of next to the navigational links on desktop. The language navbar item should be located on the left of the theme switcher button.
[ ] Proper styling on mobile

[ ] Language switcher text is too big
[ ] The dropdown overlaps the language switcher button

[ ] On clicking anywhere outside of the dropdown, the dropdown should be dismissed. There is some commented out code in the JS file that attempts to do this but it's broken and will cancel out with the code that toggles the dropdown in the first place, which results in no dropdown at all.
[ ] Fix dropdown text color in dark mode (text is too grey)

Will close #169

@ericswpark Thanks for the draft. I just gave it a try. Unfortunately, neither in mobile or desktop view the dropdown opens.
Did I miss something?

@lxndrblz that is weird! Did you pull from the languagedropdown branch from my repository?
Desktop:
https://user-images.githubusercontent.com/13326074/134336938-9023b90f-c180-4887-8a09-86175f9d0306.mov
Mobile:
https://user-images.githubusercontent.com/13326074/134337648-90aff0df-0433-4bb9-b049-c143e4649f69.mp4

@ericswpark Yes, I had pulled the latest version from your branch, because I saw that you had commits there.
In the meantime I had also worked on a purely CSS based version which works fairly way. By not relying on CSS it has the benefit that the menu would work, even if someone has JavaScript disabled in their browser:
https://user-images.githubusercontent.com/12200062/134369394-efa08cb2-d655-4a82-9524-bb529d65cd32.mp4
The only thing that is still missing is a proper mobile view.

@ericswpark Yes, I had pulled the latest version from your branch, because I saw that you had commits there.

That is weird! Are there any errors in the console? I did have problems with the dropdown not opening, but only because of the buggy code that dismisses the dropdown on window click outside of the dropdown. That should be commented out though.

In the meantime I had also worked on a purely CSS based version which works fairly way. By not relying on CSS it has the benefit that the menu would work, even if someone has JavaScript disabled in their browser:
2021-09-22.17-01-50.mp4
The only thing that is still missing is a proper mobile view.

This looks great, however I think the language controls should be next to the theme switcher to avoid confusion with navigational links. Not sure about the long language name but I guess that's easier to parse in one go instead of remembering language shortcodes. Maybe we can make it a configurable option?
If you push the changes to a separate branch I'll test it out here. Thank you for spending so much time on this!

@ericswpark  No, unfortunately I could not find any errors in the script console.
You can find the version from the video in the branch under:
https://github.com/lxndrblz/anatole/tree/languagedropdown
The name of the languages that are displayed in the dropdown is actually configured by the user. This allows a user to set a full name, a short code or even an emoji if they want.
I am still a bit torn about the placement of the language dropdown. I can see the merit of placing it separately from the menu items as this can aid as a visual distinction. For now, I want to finish the mobile view first.

Sounds good. I'll close this PR in favor of the CSS-only solution in the languagedropdown branch. We can continue tracking this issue in #169.


colspan por multiple actions on the same column

Is it possible to apply a colspan="3" (for example), so that I can put my edit, show and delete actions on the same column?
As of today, I can set those actions on different  or pass a block as
[
  record.item,
  ...
   [
     link_to('edit', edit_path(record),
     link_to('delete', record, method: :delete)
   ]
]

Using this second approach, I almost get the result I want but my links are separated with a comma (,).
A fiddle to illustrate: fiddle

@thalesmiguel You can add these action links on client side:
$ ->
  $('#dataTable').dataTable
    ajax: Routes.cities_path()
    columns: [
        data: "id"
      ,
        data: "name"
      ,
        data: "iata"
      ,
        data: "custom_column"
      ,
        data: null
        render: (record)->
          "edit remove"
    ]

Thank you very much for your reply.
As I was struggling with this question, I've came up with another solution:

_datatable.rb

[
  record.item,
  ...
   [

,
       link_to('edit', edit_path(record),
       link_to('delete', record, method: :delete),

   ]
]

.js

  $('#table').dataTable({
    "initComplete": function(settings, json) {
      $(".actions").html($(".actions").html().replace(/,/g, ' '));
    }
  });

I'm giving a Class for all my Actions and then, after rendering the Datatables, I'm using Javascrip to remove the commas.
Hope this issue helps someone else eventualy.

well, It will work but its not recomended way for ajax-datatable gem and datatables.net lib.
for datatables.net render event is convertion event to render custom content.

You are right.
Turn out, you can use strings to define Data inside de "_datatable.rb" file.
This is working fine for me (although it's kind of ugly code):
[
  record.item,
  ...
  "#{ link_to('edit', edit_path(record) }" "#{ link_to('delete', record, method: :delete) }"
]

This way, I don't neet to make any other changes and I can keep more ruby code.


Correction of cuDNN library files name

http://docs.chainer.org/en/stable/install.html#install-chainer-with-cuda-and-cudnn
$ cp /path/to/cudnn.h $CUDA_PATH/include
$ cp /path/to/cudnn.so $CUDA_PATH/lib64

cuDNN library fine names are libcudnn.so*
I think it would be better to change the file name from cudnn.so to libcudnn.so*

Oh, that's right. libcudnn.so* is correct.


Multiple directories and path glob pattern support for pipeline caching

This extends the pipeline caching tasks so that multiple paths can be cached with a single task. The following are supported scenarios:

Single path segment with absolute path outside of Pipeline.Workspace.
Single path segment with path relative to System.DefaultWorkingDirectory.
Multiple path segments, all paths are within Pipeline.Workspace.
Glob patterns with all matches within Pipeline.Workspace

The following are unsupported scenarios:

Glob patterns that match anything outside of Pipeline.Workspace
Multiple path segments with absolute path outside of Pipeline.Workspace

The limitation of having multiple paths being rooted in Pipeline.Workspace is because the tarball needs to be created somewhere, and Pipeline.Workspace seemed like the most build agent agnostic location to anchor on.
There will need to be a PR to the azure-pipelines-tasks repository to update the docs for the task inputs when/if these changes make it in.
Finally, here a some examples:
# cache 'out' and 'dist' directory (iff 'out' and 'dist' exists at root of repository)
- task: Cache@2
  displayName: Cache
  inputs:
    key: 'foo.key'
    path: 'out | dist'
    cacheHitVar: 'OUTPUT_RESTORED'

# cache all node_modules
- task: Cache@2
  displayName: Cache
  inputs:
    key: '$(Agent.OS) | npm | package-lock.json'
    path: '**/node_modules,!**/node_modules/**/node_modules'
    cacheHitVar: 'PACKAGES_RESTORED'

# cache binaries directory and 'out' directory (iff 'out' exists at root of repository)
- task: Cache@2
  displayName: Cache
  inputs:
    key: 'foo.key'
    path: '$(Pipeline.Workspace)/b | out'
    cacheHitVar: 'OUTPUT_RESTORED'

# cache node from tools directory
- task: Cache@2
  displayName: Cache
  inputs:
    key: 'foo.key'
    path: '$(Agent.ToolsDirectory)/node'
    cacheHitVar: 'NODE_RESTORED'

The following will fail because 1 path segment is outside Pipeline.Workspace and 1 is within
# cache node from tools directory
- task: Cache@2
  displayName: Cache
  inputs:
    key: 'foo.key'
    path: '$(Agent.ToolsDirectory)/node | out'

@fadnavistanmay should the path input be included in the cache version now? If someone adds a new item to cache, but doesn't change the key the cache entry won't be updated to include the new path. This would also allow for easy salt-ing of cache entries making backwards compat easier.
For reference, GitHub Actions includes the path in a cache's version via this PR

This PR addresses https://github.com/microsoft/azure-pipelines-tasks/issues/11219

Thanks for the contribution Ethan. LGTM - @b-barthel - do you mind being the second pair of eyes for this. Thanks

@fadnavistanmay / @b-barthel what are the next steps for this PR? My main concern is still with backwards compatibility with existing caches..

@ethanis the following doesn't seem to work on Mac agent:
# cache all node_modules
- task: Cache@2
  displayName: Cache
  inputs:
    key: '$(Agent.OS) | npm | package-lock.json'
    path: '**/node_modules,!**/node_modules/**/node_modules'
    cacheHitVar: 'PACKAGES_RESTORED'

Because I am trying the following task in my mono repo (using yarn workspace):
variables:
  - name: YARN_CACHED_PATH
    value: '**/node_modules | !**/node_modules/**/node_modules'

 - task: Cache@2
    displayName: Cache Yarn packages
    inputs:
      key: 'yarn | "$(Agent.OS)" | yarn.lock'
      restoreKeys: |
        yarn | "$(Agent.OS)"
        yarn
      path: $(YARN_CACHED_PATH)

result in the following error:
Starting: Cache Yarn packages
==============================================================================
Task         : Cache
Description  : Cache files between runs
Version      : 2.0.0
Author       : Microsoft Corporation
Help         : https://aka.ms/pipeline-caching-docs
==============================================================================
Resolving key:
 - yarn      [string]
 - "Darwin"  [string]
 - yarn.lock [file] --> 8F7DDEB929E5F8FE04BAC62DC69D57AC641BCDCB2E6518905F114FC86D237861
Resolved to: yarn|"Darwin"|qocY/6XZs7snurcY99+jFkYGbc+KutavQiN7/4Owleo=
Information, ApplicationInsightsTelemetrySender will correlate events with X-TFS-Session a0973c5a-71c8-4c16-9ca0-a7bdfeb1a2ac
Information, Getting a pipeline cache artifact with one of the following fingerprints:
Information, Fingerprint: `yarn|"Darwin"|qocY/6XZs7snurcY99+jFkYGbc+KutavQiN7/4Owleo=`
Information, There is a cache miss.
tar: could not chdir to '/Users/runner/runners/2.166.4/work/1/s/**/node_modules,!**/node_modules/**/node_modules'

Information, ApplicationInsightsTelemetrySender correlated 1 events with X-TFS-Session a0973c5a-71c8-4c16-9ca0-a7bdfeb1a2ac
##[error]Process returned non-zero exit code: 1
Finishing: Cache Yarn packages

I have also tried using the env variable AZP_CACHING_CONTENT_FORMAT=Files like:
variables:
  - name: YARN_CACHED_PATH
    value: '**/node_modules | !**/node_modules/**/node_modules'
  - name: AZP_CACHING_CONTENT_FORMAT
    value: Files

but in this case it result in the following error:
Starting: Cache Yarn packages
==============================================================================
Task         : Cache
Description  : Cache files between runs
Version      : 2.0.0
Author       : Microsoft Corporation
Help         : https://aka.ms/pipeline-caching-docs
==============================================================================
Resolving key:
 - yarn      [string]
 - "Darwin"  [string]
 - yarn.lock [file] --> 8F7DDEB929E5F8FE04BAC62DC69D57AC641BCDCB2E6518905F114FC86D237861
Resolved to: yarn|"Darwin"|qocY/6XZs7snurcY99+jFkYGbc+KutavQiN7/4Owleo=
Information, ApplicationInsightsTelemetrySender will correlate events with X-TFS-Session 66febed0-4ed9-47b2-942d-b7a8ffe02d37
Information, Getting a pipeline cache artifact with one of the following fingerprints:
Information, Fingerprint: `yarn|"Darwin"|qocY/6XZs7snurcY99+jFkYGbc+KutavQiN7/4Owleo=`
Information, There is a cache miss.
Information, DedupManifestArtifactClient will correlate http requests with X-TFS-Session 66febed0-4ed9-47b2-942d-b7a8ffe02d37
Information, ApplicationInsightsTelemetrySender correlated 3 events with X-TFS-Session 66febed0-4ed9-47b2-942d-b7a8ffe02d37
##[error]The path provided is invalid.
Finishing: Cache Yarn packages

Do you have any idea how to make it work?

@fadnavistanmay: do you have any rough estimates on timeline for getting this PR completed for @GoMino?

Any further updates on this PR?

Hi again, folks. Any update on this? Thanks.

@fadnavistanmay sorry, I missed your earlier approval of this.
@ethanis If you rebase this on master and remove the TODO comments with questions that were addressed in @fadnavistanmay's earlier review I will merge it.

@mjroghelia @fadnavistanmay so excited to get this shipped!

Not sure what's going on with this failing Functional Test - it's coming from a project not touched by this PR..


Bungeecord support

Nothing happens when I put jar in bungee/plugins :<
Can You add bungeecord support? (I'm using MultiChat as chat bridge, so all chat go only thru my bungee server)

I definitely want to add support for MultiChat, but I'm pretty busy at the moment, so I can't give you any guarantee or time frame.

How I can help you?


Trap representations

Hi,
am I safe to assume that there are no trap representations of FixedPoint<I, U>? To paraphrase, can FixedPoint always be safely transmuted to and from I? I have the feeling this is so, but I'd like a confirmation

Yep. It seems that repr(transparent) is enough as a guarantee.

Well, the reason I'm asking this question is because repr(transparent) isn't always enough. For instance, you cannot always transmute *mut T into NoNull<T>, you need to make sure the pointer isn't null before doing the transmute. Not all bit patterns are valid for the newtype wrapper

How does the representation of FixedPoint relate to *mut FixedPoint? Are you trying to cast FIxedPoint to *mut FixedPoint?

How does the representation of FixedPoint relate to *mut FixedPoint? Are you trying to cast FixedPoint to *mut FixedPoint?

Haha, ofc not. I was just concerned whether there was a value in the underlying integer that is not allowed by the as a FixNum value

And here transparent should be enough.

Ok then

I was just concerned whether there was a value in the underlying integer that is not allowed by the as a FixNum value

Ok. No, all values are acceptable.


KAFKA-7656: Disallow negative max bytes in fetch request

Implement a new Validator that

Returns an INVALID_REQUEST for all of the fetch partitions if the
fetch request has a negative max bytes.
Returns an INVALID_REQUEST for any fetch partion that has a negative
max bytes.

Extended the unittest FetchRequestTest to cover this scenario.
Committer Checklist (excluded from commit message)

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

cc @cmccabe @hachikuji @omkreddy

@jsancio just curious what's the status of this JIRA / PR? Did we confirm it is a real issue or not?

@jsancio just curious what's the status of this JIRA / PR? Did we confirm it is a real issue or not?

@guozhangwang,
We modify the broker logging to include more information. In particular, we now log the type of client, consumer vs replica.
All of the new reports against the brokers with this change indicate that the max byte value is coming from a consumer client.


WIP: Use OIDC

Description
Refactor to use OIDC for infrastructure deployment.
References
https://app.zenhub.com/workspaces/mighty-ducks---the-outlaws-6193fe815d79fc0011e741b1/issues/energinet-datahub/the-outlaws/364

We decided to drop OIDC for Timeseries and Wholesale for now, as it requires more work with regards to the Databricks TF provider.


incorrect info in battery_charge when below 10% remains

The current code causes the battery charge to display incorrectly there is less than 10% because battery percentage outputs x instead of 0x.  Also, please feel free to provide your fix as a pull request.

I am using the modern theme, so you can see the battery charge on the prompt.
This is the expected behavior:

But this is the observed behavior:

Yes, that looks odd. So the expected behavior is that for "8", it should show only one filled triangle (8%), and for e.g. "85", it should show an almost complete green bar (85%), right?
If that is the case, please provide a pull request and we'll make that change.

This issue is very stale, so I close it. Thanks for contributing and posting!


Fix ajv and ajv-cli versions to yesterday's version

New versions of ajv (https://github.com/epoberezkin/ajv/releases) and ajv-cli (https://github.com/jessedc/ajv-cli/releases) released hours ago broke the master.
To go with latest versions we might need to upgrade the schemas, as suggested in https://github.com/epoberezkin/ajv/releases/tag/5.0.0.
Let's do that more carefully in a different branch to keep master running fine.

hi tomas, please make changes to the travis-ci branch not to the master for the time being.

approved


Add ability to run under AWS Lambda

Add --region optional cli param to override credentials file (missing on Lambda)
Fall back to EnvironmentVariableCredentialsProvider if credentials file missing
Output API ID to log so that bash can parse it out

related: #38

It looks like this is a subset of PR #38. Can you confirm that #38 works for your use-case?

It is a strict subset - I'll test with #38 and suggest any changes but the code looks good. In Lambda there is no credentials file - it's all in ENV. #38 looks good for that.

I'll add a new PR for "Output API ID to log so that bash can parse it out"


revert: Revert table thead inline-flex

Please make sure these boxes are checked before submitting your PR, thank you!

[x] Make sure you follow Element's contributing guide (中文 | English | Español).
[x] Make sure you are merging your commits to dev branch.
[x] Add some descriptions and refer relative issues for you PR.

Revert #9030
We should obey original design


Enums that named with the word T started will be unexpectedly imported from a wrong path

Describe the bug
Prerequisites: unplugin-vue-components && unplugin-auto-import && tdesign-vue-next
When we have any enum that its name starts with the word T:
export enum THEME {
    LIGHT
}

And use it:
import { THEME } from `~`
console.log(THEME.LIGHT)

This would result in an error that  something unexpectedly re-writes the import path towards tdesign-vue-next libary.
How to reproduce it:

Hit the reproduction link below
Run the project
Check your console and keep cleanning it untill you see an Uncaught SyntaxError:

Uncaught SyntaxError: The requested module '/node_modules/.vite/deps/tdesign-vue-next.js?v=e1b92d83' does not provide an export named 'HEME2' (at enum.ts:1:10)

Reproduction
https://stackblitz.com/edit/vitejs-vite-rbldp3?file=src%2Fenum.ts,src%2FApp.vue,package.json,src%2Fmain.ts&terminal=dev
System Info
System:
    OS: Windows 10 10.0.19045
    CPU: (12) x64 AMD Ryzen 5 3600X 6-Core Processor
    Memory: 4.46 GB / 15.95 GB
Binaries:
    Node: 20.9.0 - C:\DevTool\node\node.EXE
    Yarn: 1.22.21 - C:\DevTool\node\yarn.CMD
    npm: 10.1.0 - C:\DevTool\node\npm.CMD
    pnpm: 8.10.5 - C:\DevTool\node\pnpm.CMD
Browsers:
    Edge: Chromium (121.0.2277.83)
    Internet Explorer: 11.0.19041.3636

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

Duplicate of #552 #505


Create a flag that can switch mode for BestBuy Canada

I will start working on this if there is enough interest

Please do !

Yes, please do this!

Yes, please do this! Have a couple of people I know who would want this done as well.

Please implement this feature, would be the first if not the only working one available !

It looks like this will have to wait until after Halloween !

It looks like this will have to wait until after Halloween !

Did you ever got a chance to look at this?  It feels with so low quantities of items in Canada the bots are getting mostly everything.

I would make use of this feature as well!

We are 80 in my field of study (computer science) and most are trying to create a bot to buy gpu, but we are only at the beginning of our career and we are lacking in knowledge.  You would be of great help to us!

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @


Add ability to add and update postal addresses

Adds postal addresses to the addContact and updateContact methods.
Note: I did not know if you also wanted to include other properties
like ISOCountryCode or if those are provided by iOS

This looks great, @paintedbicycle. Were you able to test it out quite thoroughly?
(At some point we'll need to add a solid test suite to this library.)

We should test a little more. I tested an update on iOS 11 but with simple data. If you can’t test it out today I’ll do a bit more testing tomorrow and ping you.

Sounds good. I'm tied up with a couple other things today so I'll wait to hear from you tomorrow. Thanks!

OK I did some testing and things should be good to go.
Note that I still need an answer to my question at the start of this PR. Do you need any of the following fields added into this?

isoCountryCode
mailingAddress
or any others?

I'm trying to keep things consistent with what you're outputting here:
  "postalAddresses": [     {       "label": "Home",       "city": "City",       "state": "CA",       "localizedLabel": "home",       "postalCode": "98765",       "country": "United States",       "isoCountryCode": "",       "stringValue": "123 St\nCity CA 98765\nUnited States",       "street": "123 St",       "identifier": "7A472311-AB4F-46F4-B046-B60143DBC858"     }   ],
But I haven't dug into how isoCountryCode,  stringValue and identifier are being generated. Are they automatic or do they need to be passed?

This looks good. We don't need isoCountryCode or mailingAddress now. I think the basics are all we need to start and we can add those later as required/requested.
The only one that might be necessary when updating is the identifier because that's the primary key for iOS.
Were you able to update a contact's postal address in your tests? If so, we should be good to go.
Let me know and I'll get this merged in.

I believe it worked fine with postal, yes, but you have me second guessing. I'll check out a clean copy and try again and let you know.
As for identifier, is this generated by iOS on each update? I don't want to overwrite some system setting. Or, should it be passed in again on update?

Identifier is like the UID of the record. It's generated by the OS and I believe can be used to lookup an existing record.
For a postalAddress, it will have it's own identifier. I'm just not sure if you need to pass it in to update the contact's postalAddresses. For example, if the contact has multiple postalAddress's, my thinking is that you would have to pass in the identifier in order to update them, otherwise the OS wouldn't know which one(s) to update. It might create new ones and essentially duplicate the postalAddress's already there.
If you can just test that, that would be great. Again, what this library really needs is a solid test suite.

Agreed, it does need tests. I've never written any, so not sure I can help much there.
As for identifier I can have a look, but your library erases all of the pre-existing array values and then re-saves them. It doesn't actually update them.
It would be great if it did, but with the removal of old addresses and the requirement to re-pass both old and new, I don't think it would matter if iOS needs the identifier or not

Okay, if it clears the existing array of postalAddresses and overwrites it with new ones then you shouldn't need to worry about the identifier for now. Perhaps later we can handle that more eloquently if a user is trying to update a single postalAddress as opposed to an entire contact record, but it's fine for now.
Are we good to merge then?

I agree, there should be a more elegant way - however I just followed your lead as this is what you do with both email addresses and telephone addresses.
I'm just installing this again now. I'll let you know in a few minutes

👍

@joshuapinter Confirmed. Both new addresses and updated addresses both save postalCode if provided in the proper format. Go ahead and merge.
      updatedRecord.postalAddresses = [{
        label: 'home',
        city: 'CityName',
        state: 'CA',
        postalCode: '98765',
        country: 'United States',
        street: '123 St',
      }];


Type error on run in getFullyQualifiedClassNameFromFile

Type error: Return value of Spatie\ModelCleanup\CleanUpModelsCommand::getFullyQualifiedClassNameFromFile() must be of the type string, null returned
This seems to happen if when using a glob for the models config, there are some files that don't contain classes (such as traits for example). It should probably filter those out.
The config I'm using is app_path('Models/*'),

We'll handle this in #15


unexpected EOF on docker push

Pretttty bizarre - never seen this one before. Kind of game-breaking for me right now.

Not that I know of. You're welcome to look for the place in the docker source code that emits the error message and update the detection of missing .dockercfg files and to improve the error message. We're always happy to get pull requests, especially from new contributors.

ping @jlhawn @dmcgowan @dmp42

Also having this problem, and not sure from this transcript what I need to do to work around it. Is there a work-around?

Not sure, if this issue is still valid, as I was trying to reproduce it on 1.8.2 with non-root user and .dockercfg file in the user home dirictory and get an error which is quite reasonable "Image push failed ... unauthorized: access to the requested resource is not authorized".

@vincentwoo is this still an issue for you?

I no longer use this flow, I moved to a private registry. I think the repro case was very reproducible though, so if those steps no longer cause an error I'd assume the problem was resolved.

I had similar problem unexpected EOF when I was pushing to docker repo
this was due to fact I've been building docker images from 2 machines (one had docker -v 1.6, the other one was docker -v 1.9). When I've upgraded the 1.6 machine to 1.9 suddenly this problem started when I done docker push .... from it.
I've ended up doing docker build --no-cache -t=myapp:latest .  and after that push worked

Well, now it seems the 1.10 release also causes this problem to appear then pushing. Rolling back to 1.9 works.

This is my first attempt to push, as far as I remember (I did some tests 2 years ago).
I forked vegasbrianc/docker-hello-world (itself forked from tutumcloud/hello-world), pulled the git to a Digital Ocean droplet, built without any change to the source and pushed with EOF error.
This can be reproduced ad infinitum. It looks like it is always the last layer 8698b31c92d5 causing the problem. Adding --no-cache or building again did not help. Pulling vegasbrianc/docker-hello-world went fine.
To change my setup, I replaced the maintainer in Dockerfile and built again, to no avail. The following pattern can be observed:
All 4 Layers 5f70bf18a086 ff. switch to Waiting first, then retrying immediately; only the last one, 8698b31c92d5, picks up pushing. The others keep retrying and pushing in sync, 4 seconds, 10, 15, 19 seconds, whereas 8698b31c92d5 pushes all the way through (as far as I can tell - I was able to spot 187.3/187.7, then even beyond to 191.1 MB -- I could record this via screenshot), then this also switches to retry, while the others keep retrying and begin pushing after waiting at last 19 seconds. At second try, however, 8698b31c92d5 fails sooner or later.
Interestingly, depending on the appearance of the EOF error, the other layers seem to be uploaded totally, but are not marked as Pushed, instead keep retrying. All this looks very mystifying.
Here are some records, from the first try (changing Dockerfile in between did not result in any different behavior):
wp@ubuntu-512mb-fra1-01:~/docker-hello-world$ sudo docker push kklepper/docker-hello-world:latest
The push refers to a repository [docker.io/kklepper/docker-hello-world]
c7e5bab43295: Pushed
3ed9b499d3d6: Pushed
9d2e7f239390: Pushed
b5c4d12d5aad: Pushed
7cd0a716db26: Pushed
2798dde3b07a: Pushed
5f70bf18a086: Pushing
0d81735d8272: Pushing [==================================================>] 1.895 kB/1.895 kB
982549bd6b32: Pushing [==================================================>] 194.5 kB/194.5 kB
8698b31c92d5: Pushing [==========>                                        ] 39.73 MB/187.7 MB
unexpected EOF

sudo docker push kklepper/docker-hello-world:latest
The push refers to a repository [docker.io/kklepper/docker-hello-world]
c7e5bab43295: Layer already exists
3ed9b499d3d6: Layer already exists
9d2e7f239390: Layer already exists
b5c4d12d5aad: Layer already exists
7cd0a716db26: Layer already exists
2798dde3b07a: Layer already exists
5f70bf18a086: Pushing
0d81735d8272: Pushing [==================================================>] 1.895 kB/1.895 kB
982549bd6b32: Pushing [==================================================>] 194.5 kB/194.5 kB
8698b31c92d5: Pushing [========================>                          ] 90.73 MB/187.7 MB
unexpected EOF

5f70bf18a086: Pushing
0d81735d8272: Pushing [==================================================>] 1.895 kB/1.895 kB
982549bd6b32: Pushing [>                                                  ]      0 B/194.5 kB
8698b31c92d5: Pushing [========================>                          ] 91.79 MB/187.7 MB
unexpected EOF

5f70bf18a086: Pushing
0d81735d8272: Pushing [==================================================>] 1.895 kB/1.895 kB
982549bd6b32: Pushing [==================================================>] 194.5 kB/194.5 kB
8698b31c92d5: Pushing [=========================>                         ] 97.12 MB/187.7 MB
unexpected EOF

5f70bf18a086: Pushing
0d81735d8272: Pushing [>                                                  ]      0 B/1.895 kB
982549bd6b32: Pushing [>                                                  ]      0 B/194.5 kB
8698b31c92d5: Pushing [=================>                                 ] 64.12 MB/187.7 MB
unexpected EOF

5f70bf18a086: Pushing
0d81735d8272: Pushing [==================================================>] 1.895 kB/1.895 kB
982549bd6b32: Pushing [>                                                  ]      0 B/194.5 kB
8698b31c92d5: Pushing [====================>                              ]  78.4 MB/187.7 MB
unexpected EOF

5f70bf18a086: Pushing
0d81735d8272: Pushing [==================================================>] 1.895 kB/1.895 kB
982549bd6b32: Pushing [==================================================>] 194.5 kB/194.5 kB
8698b31c92d5: Pushing [========================>                          ] 92.85 MB/187.7 MB
unexpected EOF

5f70bf18a086: Pushing
0d81735d8272: Pushing [==================================================>] 1.895 kB/1.895 kB
982549bd6b32: Pushing [>                                                  ]      0 B/194.5 kB
8698b31c92d5: Pushing [=====================>                             ] 80.55 MB/187.7 MB
unexpected EOF

5f70bf18a086: Pushing
0d81735d8272: Pushing [==================================================>] 1.895 kB/1.895 kB
982549bd6b32: Pushing [==================================================>] 194.5 kB/194.5 kB
8698b31c92d5: Pushing [======================>                            ] 85.35 MB/187.7 MB
unexpected EOF

5f70bf18a086: Pushing
0d81735d8272: Pushing [==================================================>] 1.895 kB/1.895 kB
982549bd6b32: Pushing [>                                                  ]      0 B/194.5 kB
8698b31c92d5: Pushing [=======================>                           ] 86.41 MB/187.7 MB
unexpected EOF

5f70bf18a086: Pushing
0d81735d8272: Pushing [>                                                  ]      0 B/1.895 kB
982549bd6b32: Pushing [==================================================>] 194.5 kB/194.5 kB
8698b31c92d5: Pushing [====================>                              ] 77.88 MB/187.7 MB
unexpected EOF

5f70bf18a086: Pushing
0d81735d8272: Pushing [>                                                  ]      0 B/1.895 kB
982549bd6b32: Pushing [==================================================>] 194.5 kB/194.5 kB
8698b31c92d5: Pushing [========================>                          ] 93.39 MB/187.7 MB
unexpected EOF

5f70bf18a086: Pushing
0d81735d8272: Pushing [==================================================>] 1.895 kB/1.895 kB
982549bd6b32: Pushing [>                                                  ]      0 B/194.5 kB
8698b31c92d5: Pushing [=============================>                     ]   110 MB/187.7 MB
unexpected EOF

5f70bf18a086: Pushing
0d81735d8272: Pushing [>                                                  ]      0 B/1.895 kB
982549bd6b32: Pushing [>                                                  ]      0 B/194.5 kB
8698b31c92d5: Pushing [=============================>                     ]   110 MB/187.7 MB
unexpected EOF

5f70bf18a086: Pushing
0d81735d8272: Pushing [==================================================>] 1.895 kB/1.895 kB
982549bd6b32: Pushing [==================================================>] 194.5 kB/194.5 kB
8698b31c92d5: Pushing [===============================>                   ] 117.4 MB/187.7 MB
unexpected EOF

@vpalos @kklepper if you're having this issue on docker 1.10, that may be https://github.com/docker/docker/issues/20104. A fix has been merged already and will be included in a patch update soon

@thaJeztah Thanks a lot!

I occasionally get this while pushing to AWS ECR:
d7e2065b375e: Pushed
5f70bf18a086: Layer already exists
4b46b70c720f: Layer already exists
a49c7743279a: Pushed
ddef881aeaff: Pushed
unexpected EOF
```

I am not sure what would help to understand why this happens.

@tugberkugurlu can you try updating to docker 1.10.2? That release carries the patch I referred to (https://github.com/docker/docker/issues/20104)

@thaJeztah for me 1.10.2 did not solve the problem (see https://github.com/docker/docker/issues/20104#issuecomment-187705710 )

@jbruggem thanks for testing; I left a comment there

I am seeing this problem too with v1 registry.

@thaJeztah @stevvooe this is a pretty big problem IMO. We've migrated to v2, but some tooling we use unfortunately only knows how to communicate with v1, so we are left supporting v1 for a little bit right now and having our build server crash every time it tries to push to v1 is not good.

Pushing to registry v1, unexpected EOF and on logs panic: runtime error: index out of range; full log:
time="2016-03-10T14:07:47.594494710Z" level=debug msg="Applied tar sha256:391fb2eed92cfaf70b6bcdd03797b33aefc741813f0a2dbe853e99b523d6d523 to af410abeeb85ff7d0471917b60c0cc343639cf73f81d96f9fc23ebcc2fd65f13, size: 11870527"
time="2016-03-10T14:07:47.946534109Z" level=debug msg="Calling POST /v1.22/images/index.private.io/name/tag/push"
time="2016-03-10T14:07:47.946574962Z" level=debug msg="POST /v1.22/images/index.private.io/name/tag/push?tag="
time="2016-03-10T14:07:47.946596442Z" level=debug msg="Warning: client and server don't have the same version (client: 1.10.0, server: 1.10.2)"
time="2016-03-10T14:07:48.231443336Z" level=debug msg="hostDir: /etc/docker/certs.d/index.private.io"
time="2016-03-10T14:07:48.372738272Z" level=debug msg="hostDir: /etc/docker/certs.d/index.private.io"
time="2016-03-10T14:07:48.372894424Z" level=debug msg="Trying to push index.private.io/name/tag to https://index.private.io v2"
time="2016-03-10T14:07:49.261532828Z" level=debug msg="Pushing repository: index.private.io/name/tag:latest"
time="2016-03-10T14:07:49.264287984Z" level=debug msg="Pushing layer: sha256:391fb2eed92cfaf70b6bcdd03797b33aefc741813f0a2dbe853e99b523d6d523"
time="2016-03-10T14:07:49.265548079Z" level=debug msg="Pushing layer: sha256:f58047ace956ade48f64644352de00174ee32329faa7cd4b23ed5c855a980af0"
time="2016-03-10T14:07:49.265891814Z" level=debug msg="Pushing layer: sha256:a1458647a86323670ad3bacc3a83d4a896a31952a862b54f538670f8d1a5ebc9"
time="2016-03-10T14:07:49.266233680Z" level=debug msg="Pushing layer: sha256:690d9849888450d080a5cff82ffe526f18b15d56a04bd0e68bb2e2bf0579b43c"
time="2016-03-10T14:07:49.266682746Z" level=debug msg="Pushing layer: sha256:3275442d02e61cd78d2cd622a9563421d175b0ea5fe8c427903b82f46246adc2"
panic: runtime error: index out of range
goroutine 355 [running]:
github.com/docker/docker/distribution.retryOnError(0x7fce80f2bba8, 0xc821013d00, 0x0, 0x0)
        /go/src/github.com/docker/docker/distribution/registry.go:143 +0x138
github.com/docker/docker/distribution.(*v2PushDescriptor).Upload(0xc8212b3980, 0x7fce82764f78, 0xc8212b3c40, 0x7fce82764fb8, 0xc8201fba40, 0x0, 0x0)
        /go/src/github.com/docker/docker/distribution/push_v2.go:335 +0x12fb
github.com/docker/docker/distribution/xfer.(*LayerUploadManager).makeUploadFunc.func1.1(0xc8201fba40, 0xc8201fb980, 0x7fce80f2b9e0, 0xc8212b3980, 0xc821bdb5f0)
        /go/src/github.com/docker/docker/distribution/xfer/upload.go:108 +0x1a6
created by github.com/docker/docker/distribution/xfer.(*LayerUploadManager).makeUploadFunc.func1
        /go/src/github.com/docker/docker/distribution/xfer/upload.go:150 +0x13e
goroutine 1 [chan receive, 2 minutes]:
main.(*DaemonCli).CmdDaemon(0xc820309840, 0xc82000a140, 0xf, 0x10, 0x0, 0x0)
        /go/src/github.com/docker/docker/docker/daemon.go:305 +0x20a7
reflect.callMethod(0xc82063ce40, 0xc820785c78)
        /usr/local/go/src/reflect/value.go:628 +0x1fc
reflect.methodValueCall(0xc82000a140, 0xf, 0x10, 0x1, 0xc82063ce40, 0x0, 0x0, 0xc82063ce40, 0x0, 0x4745b4, ...)
        /usr/local/go/src/reflect/asm_amd64.s:29 +0x36
github.com/docker/docker/cli.(*Cli).Run(0xc82063cdb0, 0xc82000a130, 0x10, 0x11, 0x0, 0x0)
        /go/src/github.com/docker/docker/cli/cli.go:89 +0x383
main.main()
        /go/src/github.com/docker/docker/docker/docker.go:63 +0x43c
goroutine 17 [syscall, 2 minutes, locked to thread]:
runtime.goexit()
        /usr/local/go/src/runtime/asm_amd64.s:1721 +0x1
goroutine 12 [chan receive, 2 minutes]:
github.com/docker/docker/daemon.setupDumpStackTrap.func1(0xc8206580c0)
        /go/src/github.com/docker/docker/daemon/debugtrap_unix.go:17 +0x4d
created by github.com/docker/docker/daemon.setupDumpStackTrap
        /go/src/github.com/docker/docker/daemon/debugtrap_unix.go:20 +0x12a
goroutine 6 [syscall, 2 minutes]:
os/signal.loop()
        /usr/local/go/src/os/signal/signal_unix.go:22 +0x18
created by os/signal.init.1
        /usr/local/go/src/os/signal/signal_unix.go:28 +0x37
goroutine 11 [select, 2 minutes, locked to thread]:
runtime.gopark(0x1a01bd0, 0xc82001f728, 0x16ffa58, 0x6, 0x18, 0x2)
        /usr/local/go/src/runtime/proc.go:185 +0x163
runtime.selectgoImpl(0xc82001f728, 0x0, 0x18)
        /usr/local/go/src/runtime/select.go:392 +0xa64
runtime.selectgo(0xc82001f728)
        /usr/local/go/src/runtime/select.go:212 +0x12
runtime.ensureSigM.func1()
        /usr/local/go/src/runtime/signal1_unix.go:227 +0x353
runtime.goexit()
        /usr/local/go/src/runtime/asm_amd64.s:1721 +0x1
goroutine 13 [select]:
github.com/docker/libnetwork.(*controller).watchLoop(0xc820104630)
        /go/src/github.com/docker/docker/vendor/src/github.com/docker/libnetwork/store.go:409 +0x140
created by github.com/docker/libnetwork.(*controller).startWatch
        /go/src/github.com/docker/docker/vendor/src/github.com/docker/libnetwork/store.go:423 +0x100
goroutine 34 [IO wait, 2 minutes]:
net.runtime_pollWait(0x7fce8379fdd0, 0x72, 0xc82000e1a0)
        /usr/local/go/src/runtime/netpoll.go:157 +0x60
net.(*pollDesc).Wait(0xc8202a5800, 0x72, 0x0, 0x0)
        /usr/local/go/src/net/fd_poll_runtime.go:73 +0x3a
net.(*pollDesc).WaitRead(0xc8202a5800, 0x0, 0x0)
        /usr/local/go/src/net/fd_poll_runtime.go:78 +0x36
net.(*netFD).accept(0xc8202a57a0, 0x0, 0x7fce8379e928, 0xc8206a0120)
        /usr/local/go/src/net/fd_unix.go:408 +0x27c
net.(*UnixListener).AcceptUnix(0xc82068dec0, 0x0, 0x0, 0x0)
        /usr/local/go/src/net/unixsock_posix.go:304 +0x53
net.(*UnixListener).Accept(0xc82068dec0, 0x0, 0x0, 0x0, 0x0)
        /usr/local/go/src/net/unixsock_posix.go:314 +0x41
github.com/docker/libnetwork.(*controller).acceptClientConnections(0xc820104630, 0xc8202a5730, 0x63, 0x7fce8379f018, 0xc82068dec0)
        /go/src/github.com/docker/docker/vendor/src/github.com/docker/libnetwork/sandbox_externalkey_unix.go:130 +0x45
created by github.com/docker/libnetwork.(*controller).startExternalKeyListener
        /go/src/github.com/docker/docker/vendor/src/github.com/docker/libnetwork/sandbox_externalkey_unix.go:124 +0x28a
goroutine 54 [chan receive]:
github.com/docker/docker/daemon.(*statsCollector).run(0xc820711480)
        /go/src/github.com/docker/docker/daemon/stats_collector_unix.go:99 +0xcd
created by github.com/docker/docker/daemon.(*Daemon).newStatsCollector
        /go/src/github.com/docker/docker/daemon/stats_collector_unix.go:38 +0x1af
goroutine 55 [chan receive, 2 minutes]:
github.com/docker/docker/daemon.(*Daemon).execCommandGC(0xc820001c80)
        /go/src/github.com/docker/docker/daemon/exec.go:237 +0x8e
created by github.com/docker/docker/daemon.NewDaemon
        /go/src/github.com/docker/docker/daemon/daemon.go:807 +0x30f1
goroutine 56 [chan receive, 2 minutes]:
main.setupConfigReloadTrap.func1(0xc82072b140, 0x17dfbc0, 0x17, 0xc820072700, 0xc820733620)
        /go/src/github.com/docker/docker/docker/daemon_unix.go:62 +0x68
created by main.setupConfigReloadTrap
        /go/src/github.com/docker/docker/docker/daemon_unix.go:67 +0x162
goroutine 57 [chan receive, 2 minutes]:
github.com/docker/docker/api/server.(*Server).serveAPI(0xc82064dec0, 0x0, 0x0)
        /go/src/github.com/docker/docker/api/server/server.go:102 +0x1af
github.com/docker/docker/api/server.(*Server).Wait(0xc82064dec0, 0xc82072b1a0)
        /go/src/github.com/docker/docker/api/server/server.go:217 +0x2b
created by main.(*DaemonCli).CmdDaemon
        /go/src/github.com/docker/docker/docker/daemon.go:287 +0x1f7a
goroutine 58 [chan receive, 2 minutes]:
github.com/docker/docker/pkg/signal.Trap.func1(0xc82072b200, 0xc82074f890)
        /go/src/github.com/docker/docker/pkg/signal/trap.go:29 +0x71
created by github.com/docker/docker/pkg/signal.Trap
        /go/src/github.com/docker/docker/pkg/signal/trap.go:55 +0x21a
goroutine 61 [IO wait, 2 minutes]:
net.runtime_pollWait(0x7fce8379ff50, 0x72, 0xc82000e1a0)
        /usr/local/go/src/runtime/netpoll.go:157 +0x60
net.(*pollDesc).Wait(0xc820317250, 0x72, 0x0, 0x0)
        /usr/local/go/src/net/fd_poll_runtime.go:73 +0x3a
net.(*pollDesc).WaitRead(0xc820317250, 0x0, 0x0)
        /usr/local/go/src/net/fd_poll_runtime.go:78 +0x36
net.(*netFD).accept(0xc8203171f0, 0x0, 0x7fce8379e928, 0xc82092bac0)
        /usr/local/go/src/net/fd_unix.go:408 +0x27c
net.(*UnixListener).AcceptUnix(0xc8201cdf40, 0xc820787dc8, 0x0, 0x0)
        /usr/local/go/src/net/unixsock_posix.go:304 +0x53
net.(*UnixListener).Accept(0xc8201cdf40, 0x0, 0x0, 0x0, 0x0)
        /usr/local/go/src/net/unixsock_posix.go:314 +0x41
net/http.(*Server).Serve(0xc82064df20, 0x7fce8379f018, 0xc8201cdf40, 0x0, 0x0)
        /usr/local/go/src/net/http/server.go:1887 +0xb3
github.com/docker/docker/api/server.(*HTTPServer).Serve(0xc82013c100, 0x0, 0x0)
        /go/src/github.com/docker/docker/api/server/server.go:121 +0x47
github.com/docker/docker/api/server.(*Server).serveAPI.func1(0xc8208ef620, 0xc82013c100)
        /go/src/github.com/docker/docker/api/server/server.go:94 +0x13d
created by github.com/docker/docker/api/server.(*Server).serveAPI
        /go/src/github.com/docker/docker/api/server/server.go:98 +0x148
goroutine 62 [IO wait]:
net.runtime_pollWait(0x7fce8379fe90, 0x72, 0xc82000e1a0)
        /usr/local/go/src/runtime/netpoll.go:157 +0x60
net.(*pollDesc).Wait(0xc820317480, 0x72, 0x0, 0x0)
        /usr/local/go/src/net/fd_poll_runtime.go:73 +0x3a
net.(*pollDesc).WaitRead(0xc820317480, 0x0, 0x0)
        /usr/local/go/src/net/fd_poll_runtime.go:78 +0x36
net.(*netFD).accept(0xc820317420, 0x0, 0x7fce8379e928, 0xc820f32b80)
        /usr/local/go/src/net/fd_unix.go:408 +0x27c
net.(*TCPListener).AcceptTCP(0xc820026128, 0xc8208ef680, 0x0, 0x0)
        /usr/local/go/src/net/tcpsock_posix.go:254 +0x4d
net.(*TCPListener).Accept(0xc820026128, 0x0, 0x0, 0x0, 0x0)
        /usr/local/go/src/net/tcpsock_posix.go:264 +0x3d
crypto/tls.(*listener).Accept(0xc82013c180, 0x0, 0x0, 0x0, 0x0)
        /usr/local/go/src/crypto/tls/tls.go:46 +0x60
net/http.(*Server).Serve(0xc820658060, 0x7fce837a00c0, 0xc82013c180, 0x0, 0x0)
        /usr/local/go/src/net/http/server.go:1887 +0xb3
github.com/docker/docker/api/server.(*HTTPServer).Serve(0xc82013c260, 0x0, 0x0)
        /go/src/github.com/docker/docker/api/server/server.go:121 +0x47
github.com/docker/docker/api/server.(*Server).serveAPI.func1(0xc8208ef620, 0xc82013c260)
        /go/src/github.com/docker/docker/api/server/server.go:94 +0x13d
created by github.com/docker/docker/api/server.(*Server).serveAPI
        /go/src/github.com/docker/docker/api/server/server.go:98 +0x148
goroutine 324 [select]:
github.com/docker/docker/distribution/xfer.(*LayerUploadManager).Upload(0xc820665410, 0x7fce82764f78, 0xc821b0a500, 0xc821547d00, 0xb, 0x10, 0x7fce82764fb8, 0xc820659a40, 0x0, 0x0)
        /go/src/github.com/docker/docker/distribution/xfer/upload.go:72 +0x48b
github.com/docker/docker/distribution.(*v2Pusher).pushV2Tag(0xc821835500, 0x7fce82764f78, 0xc821b0a500, 0x7fce82757688, 0xc820ddcaa0, 0xc820661e00, 0x47, 0x0, 0x0)
        /go/src/github.com/docker/docker/distribution/push_v2.go:149 +0x847
github.com/docker/docker/distribution.(*v2Pusher).pushV2Repository(0xc821835500, 0x7fce82764f78, 0xc821b0a500, 0x0, 0x0)
        /go/src/github.com/docker/docker/distribution/push_v2.go:97 +0x659
github.com/docker/docker/distribution.(*v2Pusher).Push(0xc821835500, 0x7fce82764f78, 0xc821b0a500, 0x0, 0x0)
        /go/src/github.com/docker/docker/distribution/push_v2.go:70 +0x37e
github.com/docker/docker/distribution.Push(0x7fce82764f78, 0xc821b0a500, 0x7fce82757498, 0xc820c17da0, 0xc8217214d0, 0x0, 0x0)
        /go/src/github.com/docker/docker/distribution/push.go:138 +0xc0e
github.com/docker/docker/daemon.(*Daemon).PushImage(0xc820001c80, 0x7fce82757498, 0xc820c17da0, 0xc8206925d0, 0xc8206599e0, 0x7fce82764928, 0xc821b0a4c0, 0x0, 0x0)
        /go/src/github.com/docker/docker/daemon/daemon.go:1070 +0x440
github.com/docker/docker/api/server/router/local.(*router).postImagesPush(0xc8207335c0, 0x7fce82752ff8, 0xc820692540, 0x7fce82752f48, 0xc8218526e0, 0xc821efa9a0, 0xc8206b31d0, 0x0, 0x0)
        /go/src/github.com/docker/docker/api/server/router/local/image.go:238 +0xa77
github.com/docker/docker/api/server/router/local.(*router).(github.com/docker/docker/api/server/router/local.postImagesPush)-fm(0x7fce82752ff8, 0xc820692540, 0x7fce82752f48, 0xc8218526e0, 0xc821efa9a0, 0xc8206b31d0, 0x0, 0x0)
        /go/src/github.com/docker/docker/api/server/router/local/local.go:102 +0x74
github.com/docker/docker/api/server.versionMiddleware.func1(0x7fce82752ff8, 0...

@ghostbar: Based on the trace, this is an issue that was just fixed in #21030 for the 1.10.3 release.

It seems to work but has very very odd behavior
c2cf220e05d: Retrying in 8 seconds
37beb931a0ec: Retrying in 8 seconds
3b8236726630: Retrying in 8 seconds
45c65a8e2f8f: Retrying in 8 seconds
138b8807a375: Retrying in 8 seconds
13945f14cb88: Waiting
2f09382363fe: Waiting
828922308e61: Waiting
1c2206890b5c: Waiting
0d4e22451772: Waiting
9c0553043bb7: Waiting
745737c319fa: Waiting```

But eventually all layers go to Waiting, and then it starts pushing from the bottom up..

```dc2cf220e05d: Waiting
37beb931a0ec: Waiting
3b8236726630: Waiting
45c65a8e2f8f: Waiting
138b8807a375: Waiting
13945f14cb88: Waiting
2f09382363fe: Waiting
828922308e61: Pushing [==================================================>] 294.2 kB
1c2206890b5c: Image successfully pushed
0d4e22451772: Image successfully pushed
9c0553043bb7: Image successfully pushed
745737c319fa: Image successfully pushed```

Just ran across the same issue consistently with Docker version 1.10.1, build 9e83765 when pushing images built on base images that were downloaded with an older version of Docker (as described in #20104) to a private Docker Hub repository. Deleting all base images and then rebuilding solved the push issues for us.

@advancingu try updating to 1.10.3; see https://github.com/docker/docker/issues/8793#issuecomment-194976405

I can confirm that 1.10.3 fixes the push issue, but the v1 registry support is horrible now. It goes into a forget long retry that lasts over a minute before it actually pushes the layers.

@ekristen have you opened a separate issue for that?

I'm not sure what this is issue is about now, can we close it? 1.10.3 and current master code solve the panic and the unexpected EOF, @ekristen sounds like yours is a different issue.
@vincentwoo shall we close this issue?

+1 to close, I opened https://github.com/docker/docker/issues/21147 for the other issue

Uh, I have no idea what these other people are talking about. I imagine they just googled an error and piled into this ticket. The root cause of my original problem turned out to be a very specific edge case involving the presence or absence of a .dockercfg. The original issue submission was from like 18 months ago so I'm just gonna go ahead and close this since I figure there should be like a statute of limitations on this shit or something.

still having this issue

@danday74 please open a new issue; this is a very old issue now, and as stated above, this issue has been collecting issues that are not related to the original issue (but can have a similar effect). When reporting, please provide as much information as possible.
I'm going to lock this issue for the above reason, for others arriving here; please open a new issue (but search for existing, non-resolved issues first to prevent duplicates)


chore: update assumevalid for v18.2.0

Issue being fixed or feature implemented

What was done?

How Has This Been Tested?

Hasn't been
Breaking Changes

Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added or updated relevant unit/integration/functional/e2e tests
[x] I have made corresponding changes to the documentation

For repository code-owners and collaborators only

[x] I have assigned this pull request to a milestone

These changes should either:
A) go into v18.2.x branch first and should be brought into develop via "merge master into develop" PR after v18.2 release
or
B) be dropped from #5127 and re-added to 18.2.x as a backport of this PR (after merge)
which way do you prefer?

B. They'll be dropped / backported once merged to develop


Ensure _munge_to_bytestring always returns bytes

@anderspitman ready for merge once the test is fixed to use the correct input


x-rate patch conflicts on v2.20.1

Hi @free 👋
Once again it is not possible to apply your patch on the latest prometheus release.
Would it be possible to you to take a look ?
Thank you.

It seems that the same code has also been modified between v2.20.1 and v2.21.0-rc.1 so if you make a new patch based on v2.20.1 it will conflict again on the future v2.21.0.


Storing data in excel as date format when downloading excel file

Hi,
I want to store value for a particular column in date format.
Below is the column in my workbook:
<Workbook.Column label="lastUpdatedDate" value="lastUpdatedDate" />
How can I store this 'LastUpdatedDate' as date value when we download the excel file?
The values are getting stored as text.The column values should come as 'date' instead of 'general' so that we can sort according to dates for that column.
Thanks

Hi,
I want to store value for a particular column in date format.
Below is the column in my workbook:
<Workbook.Column label="lastUpdatedDate" value="lastUpdatedDate" />
How can I store this 'LastUpdatedDate' as date value when we download the excel file?
The values are getting stored as text.The column values should come as 'date' instead of 'general' so that we can sort according to dates for that column.
Thanks.

I used this to build dynamic Excel exports that had arbitrary columns.
{Data != null && (     <Workbook filename={Data.Name + " Export.xlsx"} element={         <Button color="primary" className={classes.subHeaderButton}>             <i className="far fa-file-excel"></i> Excel Data Export         </Button>     }>         <Workbook.Sheet data={formatExcelData(Data)} name={Data.Name}>             {getExcelColumnMap().map(d => <Workbook.Column key={d.index} value={d.key} label={d.value} />)}         </Workbook.Sheet>     </Workbook> )}
getExcelColumnMap generated the list of columns and formatExcelData took care of Boolean/Date/Number/Currency/etc formatting.


400 from bad record get corrupts client with used concurrently

We are continuously addressing and improving the SDK, if possible, make sure the problem persist in the latest SDK version.

Describe the bug
When using ReadItemAsync on the container and getting a 400 due to a bad id (this was created by adding a record with an id containing a "/").
If the same cosmos client is used to make another request on the same container but with a valid row id, this get request also throws a  400.
If the two calls are made sequentially the second one succeeds as expected.
If we create two separate clients and call them both async concurrently the second call also succeeds as expected.
To Reproduce
Create a row with a invalid id field contain a "/".
When using ReadItemAsync on the container and getting a 400 due to a bad id (this was created by adding a record with an id containing a "/").
If the same cosmos client is used to make another request on the same container but with a valid row id, this get request also throws a  400.
If the two calls are made sequentially the second one succeeds as expected.
If we create two separate clients and call them both async concurrently the second call also succeeds as expected.
Expected behavior
Concurrent call for a valid row should not return 400 (not impacted by previous bad call).
Actual behavior
Second call throws 400.
Environment summary
SDK Version: 3.32.1
OS Version Windows 11
Additional context
Add any other context about the problem here (for example, complete stack traces or logs).

Please attach the complete exceptions (ToString()) for both failures and a way for us to reproduce.


Automated cherry pick of #5439: fix(esxi): Fix bugs when using network with vlanID

Cherry pick of #5439 on release/3.1.
#5439: fix(esxi): Fix bugs when using network with vlanID

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/3.1@4a04405). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff              @@
##             release/3.1   #5441   +/-   ##
=============================================
  Coverage               ?   7.26%
=============================================
  Files                  ?     575
  Lines                  ?   97540
  Branches               ?       0
=============================================
  Hits                   ?    7084
  Misses                 ?   89886
  Partials               ?     570

Flag
Coverage Δ

#aFlag
7.26% <0%> (?)

Impacted Files
Coverage Δ

pkg/multicloud/esxi/network.go
0% <0%> (ø)

pkg/multicloud/esxi/devtools.go
0% <0%> (ø)

pkg/multicloud/esxi/host.go
0.95% <0%> (ø)

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 4a04405...bdb9929. Read the comment docs.

/lgtm

/approve


Mouse picking

Enables you to click on entities in the editor to bring up their 'edit' menus. Beware that objects for which ABB you're inside all the time (such as 'cave') needs to be furthest down on the entity list.
fixes #170

SonarQube analysis reported 3 issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 AncientFungus:LGEPR: Cppcheck cannot find all the include files (use --check-config for details)
 main.cpp#L27: Return value of function freopen() is not used.
 main.cpp#L41: Variable 'vrSystem' is assigned a value that is never used.

SonarQube analysis reported 4 issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 AncientFungus:LGEPR: Cppcheck cannot find all the include files (use --check-config for details)
 main.cpp#L27: Return value of function freopen() is not used.
 main.cpp#L41: Variable 'vrSystem' is assigned a value that is never used.
 SoundManager.cpp#L148: The function 'GetListeners' is never used.

SonarQube analysis reported 7 issues

 7 minor

Watch the comments in this conversation to review them.
4 extra issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 AncientFungus:LGEPR: Cppcheck cannot find all the include files (use --check-config for details)
 main.cpp#L27: Return value of function freopen() is not used.
 main.cpp#L42: Variable 'vrSystem' is assigned a value that is never used.
 SoundManager.cpp#L149: The function 'GetListeners' is never used.

SonarQube analysis reported 7 issues

 7 minor

Watch the comments in this conversation to review them.
4 extra issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 AncientFungus:LGEPR: Cppcheck cannot find all the include files (use --check-config for details)
 main.cpp#L27: Return value of function freopen() is not used.
 main.cpp#L42: Variable 'vrSystem' is assigned a value that is never used.
 SoundManager.cpp#L149: The function 'GetListeners' is never used.

SonarQube analysis reported 7 issues

 7 minor

Watch the comments in this conversation to review them.
4 extra issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 AncientFungus:LGEPR: Cppcheck cannot find all the include files (use --check-config for details)
 main.cpp#L27: Return value of function freopen() is not used.
 main.cpp#L42: Variable 'vrSystem' is assigned a value that is never used.
 SoundManager.cpp#L149: The function 'GetListeners' is never used.

SonarQube analysis reported 7 issues

 7 minor

Watch the comments in this conversation to review them.
4 extra issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 AncientFungus:LGEPR: Cppcheck cannot find all the include files (use --check-config for details)
 main.cpp#L27: Return value of function freopen() is not used.
 main.cpp#L42: Variable 'vrSystem' is assigned a value that is never used.
 SoundManager.cpp#L149: The function 'GetListeners' is never used.


New deployments not possible due as AWS ACLs are disabled by default

Attempting a brand new deployment fails because AWS requires buckets to have their ACLs enabled explicitly. This causes a failure of the statics_deploy.aws_s3_bucket_acl.static_upload and statics_deploy.aws_s3_bucket_acl.static_deploy resources.

Any fix for those of us trying to deploy the first time?


EKAttributes#entryBackground doesn't get updated when switching to dark mode

Describe the bug
When switching from dark mode to light mode the entryBackground color doesn't get updated.
attributes.entryBackground = .color(color: .tertiarySystemBackground)
attributes.positionConstraints.safeArea = .empty(fillSafeArea: true)

To Reproduce
Steps to reproduce the behavior in the simulator:

SwiftEntryKite.display a view with the configuration provided.
Open the settings app and click on developer
Click on UISwitch to enable dark mode
Open the app again
See error

Expected behavior
When switching from dark mode to light mode the entryBackground color should change
Screenshots

iPhone (please complete the following information):

Device: iPhone XR Beta Simulator
iOS Version: iOS13 Beta
Xcode Version: 11.0 beta
Dependency Manager Version: CocoaPods 1.5.2
SwiftEntryKit Release # 1.0.1

Additional context
I think it has something to do with the CALayer in EKBackgroundView. If you skip the provided video (bottom of the issue) to minute 24 you can see what I mean. I played around with it, but I couldn't find a view that has the correct traitCollection.
rest of the configuration
attributes = .bottomFloat
attributes.displayDuration = .infinity
attributes.screenBackground = .clear
attributes.entryBackground = .color(color: .tertiarySystemBackground)
attributes.screenInteraction = .forward
attributes.entryInteraction = .forward
attributes.scroll = .edgeCrossingDisabled(swipeable: true)
attributes.entranceAnimation = .init(translate: .init(duration: 0.5, spring: .init(damping: 1, initialVelocity: 0)))
attributes.exitAnimation = .init(translate: .init(duration: 0.35))
attributes.popBehavior = .animated(animation: .init(translate: .init(duration: 0.35)))
attributes.positionConstraints.size = .init(width: .fill, height: .intrinsic)
attributes.positionConstraints.verticalOffset = 0
attributes.positionConstraints.safeArea = .empty(fillSafeArea: true)
attributes.shadow = .active(with: .init(color: .systemGray, opacity: 0.3, radius: 6))

Screenshots / Video Links
Implementing Dark Mode on iOS: https://developer.apple.com/videos/play/wwdc2019/214

Thanks, @doodzik. I'll look into it.

@doodzik, not sure it's EKBackgroundView since it's colored according to what specified in the given EKAttributes.
I suspect that maybe your UIPickerView is constrained to the bottom safe-area of its superview, thus exposing its white background. I couldn't know for sure. Could you send over a reproducible example project perhaps?

btw, thank for pinging on the dark mode subject. soon it's going to be quite important for users.
It seems that for custom entries there is full support on dark-mode because anything can be customized to the extreme, but I'm now preparing built-in support in SwiftEntryKit presets.

SwiftEntryKit now supports dark mode (1.1.0).  please read the changelog to catch up with what should be done to achieve that.
Let me know if you have any questions.

🎉


rename LaxOrStrictBuilder ser variable

noticed while reviewing #5564

Codecov Report

Merging #561 (c34b74f) into main (414745c) will not change coverage.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #561   +/-   ##
=======================================
  Coverage   94.17%   94.17%
=======================================
  Files          95       95
  Lines       12844    12844
  Branches       24       24
=======================================
  Hits        12096    12096
  Misses        742      742
  Partials        6        6

Impacted Files
Coverage Δ

src/serializers/type_serializers/other.rs
84.90% <100.00%> (ø)

Continue to review full report in Codecov by Sentry.

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


ApiTest.testConflict() test failure

Conflict Revisions order is opposite.
expected:<[{9d7d8ff5-1ca2-43f8-9429-1b803b74806d #2-b5952ca45a833601e40f7c5141168035}, {9d7d8ff5-1ca2-43f8-9429-1b803b74806d #2-8c5a4d9eb7790a9146f8e333684eb3ac}]> but was:<[{9d7d8ff5-1ca2-43f8-9429-1b803b74806d #2-8c5a4d9eb7790a9146f8e333684eb3ac}, {9d7d8ff5-1ca2-43f8-9429-1b803b74806d #2-b5952ca45a833601e40f7c5141168035}]>
Expected :[{9d7d8ff5-1ca2-43f8-9429-1b803b74806d #2-b5952ca45a833601e40f7c5141168035}, {9d7d8ff5-1ca2-43f8-9429-1b803b74806d #2-8c5a4d9eb7790a9146f8e333684eb3ac}]
Actual   :[{9d7d8ff5-1ca2-43f8-9429-1b803b74806d #2-8c5a4d9eb7790a9146f8e333684eb3ac}, {9d7d8ff5-1ca2-43f8-9429-1b803b74806d #2-b5952ca45a833601e40f7c5141168035}]

I have encountered this today as well. The expected order is by sequence DESC so [rev2b, rev2a].

@pasin, It seems original unit test is correct, and there is bug in Document.getLeafRevisions() of forestdb. Thanks!

PR: https://github.com/couchbase/couchbase-lite-android/pull/662


Libgdx 1.6.2 + robovm 1.3.0 makes iOS app crash

Hello
My iOS launch used to work fine, but since I upgraded libgdx to 1.6.2 and robovm to 1.3.0 I started to have problems.
First i had this error:
ld: file not found: /ios/build/libs/ios/libgdx-box2d.a
clang: error: linker command failed with exit code 1 (use -v to see invocation)
So I changed robovm.xml libs to only a "z" as mentioned by one user in libgdx forums.
(http://www.badlogicgames.com/forum/viewtopic.php?t=19642&p=82236)
After this I can build, but the app is crashing on launch with this exception:
java.lang.UnsatisfiedLinkError: com/badlogic/gdx/backends/iosrobovm/IOSGLES20.init()V
at com.badlogic.gdx.backends.iosrobovm.IOSGLES20.init(Native Method)
at com.badlogic.gdx.backends.iosrobovm.IOSGLES20.<init>(IOSGLES20.java)
at com.badlogic.gdx.backends.iosrobovm.IOSApplication.didFinishLaunching(IOSApplication.java)
at com.badlogic.gdx.backends.iosrobovm.IOSApplication$Delegate.didFinishLaunching(IOSApplication.java)
at com.badlogic.gdx.backends.iosrobovm.IOSApplication$Delegate.$cb$application$didFinishLaunchingWithOptions$(IOSApplication.java)
at org.robovm.apple.uikit.UIApplication.main(Native Method)
at org.robovm.apple.uikit.UIApplication.main(UIApplication.java)
at ggj2015.game.IOSLauncher.main(IOSLauncher.java)

Note that I followed everything said here http://www.badlogicgames.com/wordpress/?p=3694 to update my project correctly.
Thank you

I am closing this, looks like its bad configuration on my side, so I will need to dig a bit more.
Thanks anyway.


Leaf

Expand the logic for what counts as a leaf, since the current code only accepts bytes, str, int, float, bool, type(None)
For instance, when parsing a YAML or JSON, datetimes are serialized and would not be counted as a leaf.

Blocked by #136

Will be fixed by #126