Create compareBuildDetails object for multi-stage yaml pipelines

Is your feature request related to a problem? Please describe.
No. Discussed in #758 as it related to the checkStage and overrideStageName options that were added
Remember that there are a number of Azure DevOps (VSTS) extensions in this repo so please say which one you are using, and if an extension contains multiple tasks which task also
cross platform
Describe the solution you'd like
Just like there is a {{compareReleaseDetails}} object, create a {{compareBuildDetails}} object. It would be nice to get the run time, build run ID, etc. from the build we are comparing to.
Describe alternatives you've considered
N/a

I will try to have a look at it over the weekend

I have made the change and it has been released a 3.6.2.
There is a new object available in the Handlebars template compareBuildDetails, this is Build object, of the same type as the buildDetails object
# Build {{buildDetails.buildNumber}}
* **Branch**: {{buildDetails.sourceBranch}}
* **Tags**: {{buildDetails.tags}}
* **Completed**: {{buildDetails.finishTime}}

# Last Build {{compareBuildDetails.buildNumber}}
* **Branch**: {{compareBuildDetails.sourceBranch}}

Remember this new object is only populated if the checkStage parameter is set to true and a past pipeline has run and the stage the task is in (or the named overrideStage) has been successful.  If no pipeline has completed successfully for the stage the new object is empty.

Awesome, works as intended.
# 🚀  Notes for release

## Current Build
**Build Number**: 20200815.18
**Build Ran** : Sat Aug 15 2020 21:49:56 GMT+0000 (Coordinated Universal Time)
**Branch**: refs/heads/master
**Requested For**: Josh Johanning

## Last Build Deployed to Prod
**Build Number**: 20200815.9
**Deployment Completed**: Sat Aug 15 2020 21:24:24 GMT+0000 (Coordinated Universal Time)
**Branch**: refs/heads/master
**Requested For**: Josh Johanning

I had a bit of a struggle at first getting the {{compareBuildDetails}} object to populate, I needed two* successful runs to that stage, it seemed. It works now, but if you want any more details on that I can dig into further. Here's a screenshot:

What is it using to compare stages? I see in your code it's System.StageName, that is the stage ID, such as: - stage: dev ?

By default it gets the stage name the release notes task is in, but you can orrride this with a named one passed as a parameter. It then looks back for the last build that completed successfully that stage.
If you run with the variable system.debug=true it will log out its discovery process


Unfolding header also unfolds headers above it's parent.

If you fold a nested header and a header above that header's parent, then when you unfold the nested header the other one also unfolds.

Fixed in 1.6.0


Multi shard DELETE with LIMIT clause should not be supported

Desc
Per discussion, this was too radical. We should not support this.

LGTM

@demmer I think your comment has been addressed, if you agree I'll merge.


Add edge features in graphs (backbone/not-backbone)

also see Ingraham et all etc for geometric features


Introduce toggle method

I'd like to introduce a toggle method for any output device which can be turned on or off. If it's on, toggle will turn it off. If it's off, toggle would turn it on. Applying toggle to a group of components would invert their state.
Would it be easier to maintain state within the object or check it using GPIO.input(self.pin)?

Hmm ... depends how "correct" you want the toggle to be. For example, consider the following naive implementation:
def toggle(self):
    if self.is_active:
        self.off()
    else:
        self.on()

Now consider a multi-threaded scenario with an LED (very common in GPIO given the RPi.GPIO library uses threads for callbacks itself, not to mention all the threaded stuff we're doing in gpiozero):

Thread 1
Thread 2
Comments

LED.toggle()
LED.toggle()

if self.is_active

Returns False

if self.is_active
Returns False

self.on

Correct toggle

self.on
Incorrect toggle

So yes, we can implement toggle pretty easily using GPIO.input (this is almost certainly better than using a separately stored state) but we need to be careful about threading effects. In other words we probably want to wrap the whole thing in a threading.Lock.

Interesting. Can you determine whether or not it's blinking? I guess if you call toggle while it's blinking, it should stop blinking. (I guess turn it off?)

We could determine whether it's blinking by checking whether the blink thread is alive at that moment, but the call to on() or off() will implicitly kill the blink thread (as it should). So basically it'll read the state of the LED (let's say it's blinking and it's currently lit), then call off() (because it's currently on) which will kill the blink thread and switch off the LED (or buzzer or whatever). In other words, the locked implementation should work fine (wait did I push that last night?)

Oh I didn't ... right, well I've got a toggle implementation that seems to be working nicely. I'll pull in the latest updates from master, get it all tidied up and open another PR for it...

Cool thanks


Setup Code Cov WIP

:bulb: Description

:hammer_and_wrench: Type of change

[ ] :bug: Bug fix (non-breaking change which fixes an issue)
[ ] :gift: New feature (non-breaking change which adds functionality)
[ ] :boom: Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] :book: This change requires a documentation update

:microscope: How Has This Been Tested?

[ ] Test A
[ ] Test B

Codecov Report

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

@@          Coverage Diff           @@
##             dev       #9   +/-   ##
======================================
  Coverage       ?   70.17%
  Complexity     ?       20
======================================
  Files          ?       12
  Lines          ?       57
  Branches       ?        0
======================================
  Hits           ?       40
  Misses         ?       17
  Partials       ?        0

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add syntax highlighting to README.rst codeblocks

Added syntax highlighting so it's a bit easier to read
@nhoffman Please take a look :)

I think this makes it quite a bit easier to read, so it could help newcomers get started more easily :)

@nhoffman Hope you can merge this soon :)


Referring to variable in "required" string

Is there a way to refer to variable name in required string?
I have a template for secret like the following,
---
apiVersion: v1
kind: Secret
metadata:
    name: {{ required "a valid name is required" $secretName }}
type: {{  $secretValue.type | default "Opaque" }}
data:
    {{- range $key, $val := $secretValue.data }}
      # fix printing the key name in the required string
      {{ $key }}: {{ required "a valid key is required" $val }}
    {{- end }}
{{- end }}

As there can be multiple keys in secret data,I want to refer to the key variable in required string for better logging.
{{ $key }}: {{ required "a valid key is required" $val }}
It will be good to refer ,
{{ $key }}: {{ required "a valid {{ $key }} is required" $val }}
But its not working for me.Is there any way to do this?
HELM_VERSION=v3.2.1
HELMSMAN_VERSION=3.4.3
Output of kubectl version: 1.15
Cloud Provider/Platform (AKS, GKE, Minikube etc.): EKS

@bacongobbler  ..It worked fine :) Thankyou..


bosh-lite ops-file uses packages compiled for an old stemcell

The bosh-lite.yml ops-file is still using releases which were compiled for the 315.* stemcell (see here and here). This seems to be a problem for other ops-files as well (see https://github.com/cloudfoundry/bosh-deployment/issues/361).

Hey @gcapizzi,
Thanks for the catch. There was a bug in our autobumping pipeline that we just fixed. Everything should be up to date now.


Is there a way to choose the tagname of the component

I see that sprig injects one DIV element per sprig component with all the necessary HTMX attributes. Something like:
<div class="sprig-component" data-hx-target="..." data-hx-include="..." >
    The actual sprig component content
</div>

Is it possible to change the tagname of this HTML element?
I'm working a lot with tables, and want to update row by row. (each table row is a sprig component)
The injected DIV between my TBODY and TR makes my HTML invalid, making the browser rendering wrong.
Kind regards.
Peter

I guess this is not possible at the moment. Found this at the component service:
$event->output = Html::tag('div', $content, $attributes);

Right, it's currently hard-coded as a div. If you're creating one component per table row, then you'll likely doing something wrong, or at least not recommended, as you should have as few Sprig components on the page as possible.


config/nls folder not in cmv-wab-widgets folder

In the cmv-widgets application there is a config/nls folder.  I am assuming there will be a conflict with the cmv-wab-widgets application.  Is this true?

No conflict that I am aware of. The nls folder under the config folder is completely optional. It is only referenced by configuration files in the demo's config folder for demonstrating the use of multiple languages.
If your configs do not reference the folder, it will not be used and can be excluded completely.  The WAB demo configuration files s in this repo do not use it.


add modemenu link to admin backend

This brings a link to the admin backend to the frontend.

@jow- is this the correct way doing that? Before doing that, the modemenu link was only displayed while being logged in.

@andibraeu - hmm, can't tell without any actual runtime testing but fro mthe looks of it it would replace the Admin menu node with a Freifunk page?

yes, let's call it a workaround :)
Is it intended to see no Administration entry in the modemenu section when you're not logged in?


[PyPlanet 0.10.0] Developing a plugin/DB structure for FlagRush  to keep track of stuff

Hi,
Trying to develop a plugin for FlagRush to keep track and eventually show FlagRush related XMLRPC Callbacks i found a weird bug:
Flag.Reset is First before Scored?! Seems a bit mixed up it on the map Collided
DEBUG    [debug_][pyplanet.core.gbx.remote] GBX: Received scripted callback: FlagRush.Flag.Pickup: {'Time': 1127990, 'Flag': {'Position': [772.635, 26.0106, 766.147], 'Carrier': {'Login': 'q2-lckjXSxai11x2CgX5ew', 'Name': 'W1llaSmurf', 'TeamNum': 1, 'Position': [772.635, 26.0106, 766.147]}, 'Spawn': {'LandmarkId': 0, 'Position': [0, 0, 0]}}}

DEBUG    [debug_][pyplanet.core.gbx.remote] GBX: Received response to handler<PHONE_NUMBER>, method: None

DEBUG    [debug_][pyplanet.core.gbx.remote] GBX: Received response to handler<PHONE_NUMBER>, method: None

DEBUG    [debug_][pyplanet.utils.memleak] Checking for memory leaks...

DEBUG    [debug_][pyplanet.core.gbx.remote] GBX: Received scripted callback: FlagRush.Flag.Reset: {'Time': 1142950, 'Flag': {'Position': [768, 26, 768], 'Carrier': {'Login': '', 'Name': '', 'TeamNum': 0, 'Position': [0, 0, 0]}, 'Spawn': {'LandmarkId': 50331654, 'Position': [768, 26, 768]}}}

DEBUG    [debug_][pyplanet.core.gbx.remote] GBX: Received scripted callback: FlagRush.Flag.Scored: {'Time': 1142950, 'Scorer': {'Login': 'q2-lckjXSxai11x2CgX5ew', 'Name': 'W1llaSmurf', 'TeamNum': 1, 'Position': [637.453, 56.0127, 768.099]}, 'Assist': {'Login': '', 'Name': '', 'TeamNum': 0, 'Position': [0, 0, 0]}, 'TeamScores': [1, 0]}

Thanks for reporting. The XmlRpc stuff is not really 100% matured yet. If you find other issues, please let us know. :)
I put up a PR to fix it, as can bee seen above, Then it should be in the right order:
DEBUG    [default][pyplanet.core.gbx.remote] GBX: Received scripted callback: FlagRush.Flag.Scored: {'Time': 229860, 'Scorer': {'Login': 'W2ZNWNzVQV6z3hXuNgRMRg', 'Name': 'Ze-Rax', 'TeamNum': 1, 'Position': [637.615, 56.0214, 768.011]}, 'Assist': {'Login': '', 'Name': '', 'TeamNum': 0, 'Position': [0, 0, 0]}, 'TeamScores': [1, 0]}
DEBUG    [default][root] No callback registered for Script.FlagRush.Flag.Scored
DEBUG    [default][pyplanet.core.gbx.remote] GBX: Received scripted callback: FlagRush.Flag.Reset: {'Time': 229860, 'Flag': {'Position': [768, 34, 848], 'Carrier': {'Login': '', 'Name': '', 'TeamNum': 0, 'Position': [0, 0, 0]}, 'Spawn': {'LandmarkId': 50331660, 'Position': [768, 34, 848]}}}


B-18032: Allow an Update for an approved service item

https://www13.v1host.com/USTRANSCOM38/Default.aspx?menu=StoryBoardPage
Summary
This change allows fields sitDepartureDate, sitRequestedDelivery, sitCustomerContacted, and sitDestinationFinalAddress to be updated when the a DOASIT, DOFSIT, DOPSIT, DDDSIT serviceItem is in an APPROVED status.
Testing
To test try updating one of the fields listed above on a  DOASIT, DOFSIT, DDDSIT or DOPSIT serviceItem when in approved status.

So... When using the API and the payload is being converted to a model in payload_to_model.go, it seems like the service code is not being passed into that so the checks that are happening on line 595 aren't happening. Specifically it's checking if the service item is a destination SIT item and then pulls the additional values needed, which we need:
sitCustomerContacted & sitRequestedDelivery
In my PR here: https://github.com/transcom/mymove/pull/11638/files#diff-54081105a3cca8353f6085cc2d26c4c98b51c1e0622cb0b48fdc26a93335a304
I added in populating those values prior to those checks because the gov wanted origin SIT items to also have those values updated.
So it seems that the service code is not being passed into the payload_to_model.go function when it is of model UpdateMTOServiceItemSIT, which is not populating those two values.
If my PR merges then this issue will go away because I added those prior to the service code check, but the problem still persists... How are we passing in the service code prior to converting the payload to a model?

So... When using the API and the payload is being converted to a model in payload_to_model.go, it seems like the service code is not being passed into that so the checks that are happening on line 595 aren't happening. Specifically it's checking if the service item is a destination SIT item and then pulls the additional values needed, which we need: sitCustomerContacted & sitRequestedDelivery
In my PR here: https://github.com/transcom/mymove/pull/11638/files#diff-54081105a3cca8353f6085cc2d26c4c98b51c1e0622cb0b48fdc26a93335a304
I added in populating those values prior to those checks because the gov wanted origin SIT items to also have those values updated.
So it seems that the service code is not being passed into the payload_to_model.go function when it is of model UpdateMTOServiceItemSIT, which is not populating those two values.
If my PR merges then this issue will go away because I added those prior to the service code check, but the problem still persists... How are we passing in the service code prior to converting the payload to a model?

And just to summarize this... This means that we aren't able to update sitCustomerContacted & sitRequestedDelivery until my PR merges.

We can probably meet about this. Im trying to understand what your talking about and working on.

I am able to update the SIT departure date, SIT requested delivery, and SIT customer contacted successfully, but haven't been able to update the SIT destination final address. I have tried using a string value and also an address id in the body and get a 500 response of:

Should have clarified that I was using the swagger prime API. The issue with updating the destination final address may not be an issue based on the latest developments?

I am able to update the SIT departure date, SIT requested delivery, and SIT customer contacted successfully, but haven't been able to update the SIT destination final address. I have tried using a string value and also an address id in the body and get a 500 response of:

Should have clarified that I was using the swagger prime API. The issue with updating the destination final address may not be an issue based on the latest developments?

Correct - it's how the updater is handling the address. Only updates that value if the address does not exist yet. Doesn't update it.

I am able to update the SIT departure date, SIT requested delivery, and SIT customer contacted successfully, but haven't been able to update the SIT destination final address. I have tried using a string value and also an address id in the body and get a 500 response of:

Should have clarified that I was using the swagger prime API. The issue with updating the destination final address may not be an issue based on the latest developments?

We will not be allowing SIT destination final address updates per conversations with DAN today.


Fix temperature gradient default value in Atmosphere DOM

The default value in the Atmosphere SDF DOM was off by a factor of 10, see default value in atmosphere.sdf spec. I believe the one in the spec is correct according to wikipedia: Temperatures in the atmosphere decrease with height at an average rate of 6.5°C/km.
This could be a behavior change so I could retarget to master if needed
Signed-off-by: Ian Chen<EMAIL_ADDRESS>

I fixed the unit test in 8aa6e13

We can note it in the migration guide

yep done.


IconButton instead of custom buttons in the SearchField

Instead of custom inner submit button and reset button we can use IconButton that has proper styles. Recently we encountered several issues with custom inner buttons and it will be much consistent for Paragon.

PR: https://github.com/openedx/paragon/pull/2719

New PR: https://github.com/openedx/paragon/pull/2842


Main module is could not found your project

[ ] Asked question in discussions
[x] Tried the troubleshooting Wiki
[x] Followed the migration Wiki

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Hi @02mk I did not see your question in discussions, but this looks like a familiar error. Are you sure you tried the troubleshooting wiki? It seems it may have been installed incorrectly. For most applications, this should be installed under dev dependencies as should babel


Adds 2024 Iroha annual report

Here the Iroha Annual Report notes in preparation for the meeting tomorrow:
Iroha Annual Review 2024 Notes
Project Health

Overall, the project appears to be in good health as indicated in the review and by looking at the LFX Insights.

Once I switched the LFX Insights to stable year-by-year comparisons (recommendation in PR).

The activity on the project seems stable, year over year, although by commits, the code contributions a bit down.

That said, the progress on Iroha v2 and in successfully transitioning the Ursa code into Iroha indicates the "important" things are being done in a timely fashion.

The examples of use are impressive -- two significant CBDC deployments and the Fraud Intelligence project (that I didn't really understand...).
The year-by-year comparison of the contributor and organizational leaderboards was interesting -- seeing that many of the the same people/organizations are still around, and that there is new and globally diverse interest.
The LFX Insights Activity Dependency metric is a little concerning (55% of activity from one person, 94% from one organization), but from my experience, I'm a little suspect of the activity charts in LFX Insights. Its not surprising to have a team lead/community organizer (especially one that is a developer) doing a lot of the activities in the various project repos.

The organizational dependency is not ideal. Deployed blockchains should be decentralized by nature, and if production networks are getting built (as they seem to be), contributions from others should come.

Recent Maintenance Activity and Progress

The stated progress on Iroha 2 looks good, and a working system is near -- impressive!
The rollout of the projects based on Iroha is likewise really impressive.

Compliance with Hyperledger Project Lifecycle Criteria

All the criteria are fulfilled with no red flags
Should remain in Graduated status

Suggestions for Improvement

While I found information about Iroha 1 and Iroha 2, the introductory documents were virtually identical -- with no indication of the difference between or the status of Iroha 2.0 for adopters. Insiders might know more, but as an outsider, I was left wondering. Suggest adding that to at least the Iroha 2 README, or perhaps to the Iroha Hyperledger Wiki Project page.
I had not realized that Iroha was being actively used for CBDC uses cases and definitely think that should be touted by the project. Perhaps it is and I'm just not aware of it.

General Recommendations
No specific recommendations about Iroha per se. Some of the comments from other Annual Reviews apply, notably:

Create an Iroha ecosystem page similar to the Fabric ecosystem page (https://wiki.hyperledger.org/display/fabric/Ecosystem). This would be helpful to the community, as currently it is hard to understand how the repos complement each other. This could be done as a pair -- one for Iroha 1 and one for Iroha 2.
Write blog articles and run workshops periodically with Hyperledger staff's help.
Signal openness towards more adding organizations to the project to reduce the organizational dependency.


Input format with faster parsing

@morganherlocker would like a simple CSV input format like the datamaps one that is faster to parse than GeoJSON. @aaronlidman, I think you said you'd like this too.

Is this just for geometry or will this also include a way of passing properties?
Before investing in this, do you have an idea of how much gain we would expect by not needing to parse JSON?

@aaronlidman I was thinking just "key"="value" at the end of the line. The more serious limitation is no good precedent for a syntax for polygons.
Datamaps input parsing is about 10x the speed of tippecanoe's, and the only real difference is GeoJSON vs just blasting through comma-separated pairs.
There's got to be something that is reasonably fast, easy to generate, and reasonably standardized, but I don't know what it is. GeoJSON is standard but slow to parse and hard to generate because of all the nested objects.

I think parallelized input mitigates this need quite a bit.
@ericfischer - Think we're good to close this?

Yeah, probably not worth worrying about this unless to support some other widely-used format like shapefile.


Make webcamjs more node-friendly

The primary change here is to not initialize with an explicit window dependency.
This allows the module to be imported on the server, since it can be exported without requiring the window. The init() call that used to happen before exporting the module now happens automatically when attaching a webcam viewer for the first time.
This solution is not as heavy-handed as https://github.com/jhuckaby/webcamjs/pull/66, in that this does not allow for separate Webcam instances (e.g., does not allow for multiple independent Webcam previews to have separate flashNotify callbacks), but does improve modularization. Ultimately, that approach is probably preferred, but these changes will allow for at least this simple implementation to work in a node environment.

Thanks man!  I'll look this over as soon as I have some time.

Traditionally, node is headless. What is the goal here? Electron support? Or more general support for modules?


feat: Support targetting Android 14 (API level 34)

Description
Targeting Android 14 requires the specification of RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED when registering a receiver. Docs: https://developer.android.com/about/versions/14/behavior-changes-14#runtime-receivers-exported

using CompatConext allow us to avoid the android version check as it handles it internally
Compatibility

OS
Implemented

iOS
❌

Android
✅

Windows
❌

Checklist

[n/a (Only android) ] I have tested this on a device/simulator for each compatible OS
[ n/a] I added the documentation in README.md
[ n/a] I updated the typings files (privateTypes.ts, types.ts)
[ n/a] I added a sample use of the API (example/App.js)

This is important and relates to the PR just merged (which added some new runtime receivers) #1623


Change Off-Canvas & Reveal Z-Index

off canvas should have z-index: 16 to be in front of sticky and reveal indez:17 to be on top of everything else by default

Fixed In Version 3.0.7


Can I turn off the inline issues index without a custom boilerplate?

The answer might be "no" which is fine. But https://domenic.github.io/streaming-mediastreams/ has an issue index which I don't like having around.

It can be omitted with Boilerplate: omit issues-index.
But that section is helpful to both readers and reviewers.  Why don't you want it?

Because it literally duplicates the open issues link at the top.

That gives
←[1;31mFATAL ERROR:←[0m Couldn't find target anchor issues-index:
Inline In Spec

Wait, my bad, it works when I merge it with my previous Boilerplate: line. Sorry for the noise.

Actually that's still an error on my part, but I'm glad your other metadata was able to mask the error. ^_^


BCC /  CC

Need to add BCC and or CC for emails

Added fields, updated readme, and re-published to NPM


Godot ignores folder with a project.godot file inside of it

Godot version
v4.0.dev.calinou [52b7d5fa3]
System information
Windows 10, Vulkan, Nvidia GTX 750 Ti
Issue description
Currently when git cloning an addon repository into your project's addons folder, Godot will ignore the folder if the folder contains a project.godot file inside of it. I assume this is because of conflict with multiple folders or might be intended to prevent conflicts with the root project godot file.
Steps to reproduce

Clone an repository into the addons folder. For example https://github.com/ywmaa/Advanced-Movement-System-Godot which is the repository that I cloned into the addons folder.
Godot will ignore the folder.

Minimal reproduction project
Currently Github's upload feature is broken for me so I will need to find another way to upload the file.
I'm constantly getting a is not included in the list error on Github which I have no clue what that means.

Just tested out more, this is not because of the .git folder but because of the project.godot file.

That's intended. A project.godot file defines a standalone Godot project, and those can't be nested (you can't have multiple res:// pointing to different locations).

As the repository's README says, "This project is a template". It isn't meant to be cloned as an add-on.
I suggest contacting the project author to ask them to create a separate add-on repository. See an example of this with https://github.com/godot-extended-libraries/godot-lod and https://github.com/godot-extended-libraries/godot-lod-demo.

Ah my bad I didn't see that part.


⚠ Minecraft has degraded performance

In f63a952, Minecraft (https://www.minecraft.net) experienced degraded performance:

HTTP code: 200
Response time: 1147 ms

Resolved: Minecraft performance has improved in 74f4714.


Handle dead workers

Incomplete jobs on dead workers should probably be rescheduled. Also, should dead/gone workers be automatically cleaned up from the database at some point (after a configurable time)?

At the very least, jobs assigned to dead workers should be marked with the "Error" state, after a grace period.


shouldPollResponse

I have a call with shouldPollResponse, with await of course, the problem is that for example I call the Deposit function and it does not continue with the following many seconds later, the call being Completed... Why?

Could you please show  some code snippet?


Not able to configure dynamic Kubernetes Accounts using Vault in Spinnaker

I had setup the config as mentioned in the doc https://docs.armory.io/docs/armory-admin/dynamic-accounts-configure/ , and configured spinnaker to access my kubernetes cloud providers accounts dynamically from vault .
I was able to successfully add kubernetes accounts as deployment targets. Deployments to those accounts were also successful.
But recently i observed, even though the accounts are getting added in the same manner, (that is, the account credentials are reflecting in the gate-endpoint/credentials url.) deployments are always happening to the cluster where Spinnaker is running( instead of the target accounts selected). Tried the same config several times but had no luck.
These are the clouddriver logs -
2021-04-29 12:36:36.772 INFO 1 --- [0.0-7002-exec-6] c.n.s.c.k.v.KubernetesValidationUtil : Validating credentials for spinpoc-GKE namespace
2021-04-29 12:36:36.786 INFO 1 --- [tionProcessor-3] c.n.s.c.data.task.jedis.JedisTask : [ORCHESTRATION] Processing op: KubernetesDeployManifestOperation
2021-04-29 12:36:36.788 INFO 1 --- [tionProcessor-3] c.n.s.c.data.task.jedis.JedisTask : [DEPLOY_KUBERNETES_MANIFEST] Beginning deployment of manifest...
2021-04-29 12:36:36.789 INFO 1 --- [tionProcessor-3] c.n.s.c.data.task.jedis.JedisTask : [DEPLOY_KUBERNETES_MANIFEST] Swapping out artifacts in namespace demons from context...
2021-04-29 12:36:36.791 INFO 1 --- [tionProcessor-3] c.n.s.c.data.task.jedis.JedisTask : [DEPLOY_KUBERNETES_MANIFEST] Finding deployer for namespace...
2021-04-29 12:36:36.793 INFO 1 --- [tionProcessor-3] c.n.s.c.data.task.jedis.JedisTask : [DEPLOY_KUBERNETES_MANIFEST] Checking if all requested artifacts were bound...
2021-04-29 12:36:36.795 INFO 1 --- [tionProcessor-3] c.n.s.c.data.task.jedis.JedisTask : [DEPLOY_KUBERNETES_MANIFEST] Sorting manifests by priority...
2021-04-29 12:36:36.798 INFO 1 --- [tionProcessor-3] c.n.s.c.data.task.jedis.JedisTask : [DEPLOY_KUBERNETES_MANIFEST] Deploy order is: namespace demons
2021-04-29 12:36:36.800 INFO 1 --- [tionProcessor-3] c.n.s.c.data.task.jedis.JedisTask : [DEPLOY_KUBERNETES_MANIFEST] Finding deployer for namespace...
2021-04-29 12:36:36.802 INFO 1 --- [tionProcessor-3] c.n.s.c.data.task.jedis.JedisTask : [DEPLOY_KUBERNETES_MANIFEST] Annotating manifest namespace demons with artifact, relationships & moniker...
2021-04-29 12:36:36.804 INFO 1 --- [tionProcessor-3] c.n.s.c.data.task.jedis.JedisTask : [DEPLOY_KUBERNETES_MANIFEST] Swapping out artifacts in namespace demons from other deployments...
2021-04-29 12:36:36.815 INFO 1 --- [tionProcessor-3] c.n.s.c.data.task.jedis.JedisTask : [DEPLOY_KUBERNETES_MANIFEST] Submitting manifest namespace demons to kubernetes master...
2021-04-29 12:36:37.418 INFO 1 --- [tionProcessor-3] c.n.s.c.data.task.jedis.JedisTask : [DEPLOY_KUBERNETES_MANIFEST] Deploy manifest task completed successfully.
Kindly help me with this. Thanks in advance! :)

Never mind it was my bad. In one of structs for sidecar code, I had
type Account struct {
	Name               string `json:"name"`
	KubeconfigFilePath string `json:"kubeconfigFile"`
}

Output file is not a JSON file so serialization tags are wrong.


[WIP] draft of docs site with versioning enabled

1. Issue, if available:
#800
2. Description of changes:
add a new dir
v1-docs/
that is a snapshot of docs/
3. Does this change impact docs?

[ X ] Yes, PR includes docs updates
[ ] Yes, issue opened: link to issue
[ ] No

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

https://karpenter-versions.gcline.us/

take a :eyes: at the dropdown
https://karpenter-versions.gcline.us/docs/
the primary remaining task: create a new hugo page type of "docs-old" that inherits from "docs" but includes a banner saying "this is old"
see, for ex, https://v1-21.docs.kubernetes.io/docs/home/

This is ready for review.
Before merging, the conf.toml must be updated to use *.karpenter.sh urls.

possible improvements:

use JS to have "releases" dropdown show the version you are currently browsing.

got 2 approvals so I'm merging 🥳


[irods/irods#6412] Bump version to 4.3.1 (main)

I just copied what I saw in some of the other repos.
Can change if necessary.

#'d


[Feature request] Do not close EmulationStation while running a game (optionally)

When launching a game, EmulationStation closes itself until the game stops running. On a desktop environment (e.g. Windows) this causes the user desktop to flash while the emulator loads the game.
It would be nice if EmulatorStation had an option to be always running, so that no desktop flashes occur. (For an example of this behavior, take a look at the AttractMode  frontend). It makes for a more seamless experience.

hide task bar and make some loading wallpaper
example wallpaper: http://i.imgur.com/vG2XFE6.png


Feature/ast13bridge

This should complete the mandatory compatibility changes.

Coverage increased (+0.04%) to 99.13% when pulling 5e57b67ffb185fec3006de5a9295083a840034f1 on feature/ast13bridge into 71622a908c9aaf3b4debce9dfaedaebbb64ce113 on feature/asterisk13.

Coverage increased (+0.01%) to 99.1% when pulling d137a6d1f7599dbdec62a22d9c69b7ec46c39b61 on feature/ast13bridge into 71622a908c9aaf3b4debce9dfaedaebbb64ce113 on feature/asterisk13.

Coverage increased (+0.01%) to 99.1% when pulling d137a6d1f7599dbdec62a22d9c69b7ec46c39b61 on feature/ast13bridge into 71622a908c9aaf3b4debce9dfaedaebbb64ce113 on feature/asterisk13.


Update MODELS.md

A new versions (d4) of the Ivrit.ai model was recently released. Updating the magic setup / direct download links to point at it.

Thanks for contribution!


[Docs] statement about fetch function

http://redux.js.org/docs/advanced/AsyncActions.html

Note on fetch
We use fetch API in the examples. It is a new API for making network requests that replaces XMLHttpRequest for most common needs. Because most browsers don't yet support it natively, we suggest that you use isomorphic-fetch library:

http://caniuse.com/#search=fetch
Well, I think only IE11 requires a polyfill. What do you think on updating this section?

Sure. Can you submit a PR? Thanks!

@timdorr If I will not provide a PR by a Monday, assume I was too lazy to make it. 😃


add unit tests for validation

Currently, I am using make validate for testing in nmdc-schema.
validate-%: test/data/%.json jsonschema/nmdc.schema.json
# util/validate_nmdc_json.py -i $< # example of validating data using the cli
	pipenv run jsonschema -i $< $(word 2, $^)

I should switch to using unit tests.
@ssarrafan can add this to the November sprint?
cc @cmungall

Currently, I am using make validate for testing in nmdc-schema.
validate-%: test/data/%.json jsonschema/nmdc.schema.json
# util/validate_nmdc_json.py -i $< # example of validating data using the cli
	pipenv run jsonschema -i $< $(word 2, $^)

I should switch to using unit tests.
@ssarrafan can add this to the November sprint?
cc @cmungall

Hi @wdduncan. Is this issue done or does it need to go to the backlog or the next sprint?

Moving to December per @wdduncan


Add MediaStream Image Capture API Sample

Hello @samdutton,
Can you review this sample?
I've tried to keep it very simple, and not showcase yet PhotoCapabilities. WDYT?
You can give it a try at https://beaufortfrancois.github.io/samples/image-capture/

LGTM.
I have a couple of suggestions, but feel free to ignore them :).

I've tried to keep it very simple, and not showcase yet PhotoCapabilities. WDYT?

It adds a bit of complexity, but it might be nice to add zoom, even if this part of the API changes (see the example at simpl.info/ic).

I was thinking if we may want another sample dedicated to zoom. WDYT?

Good point — maybe another sample focused (ha ha) on camera capabilities.
On 30 November 2016 at 11:16, François Beaufort<EMAIL_ADDRESS>wrote:

I was thinking if we may want another sample dedicated to zoom. WDYT?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleChrome/samples/pull/449#issuecomment-263848552,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMhqmKbgWShu1viaQnuWm2b9O-MLEWhks5rDVr3gaJpZM4K5Ply
.

I'll do that today then.

OK. So we have now two samples you can try at
https://beaufortfrancois.github.io/samples/image-capture/grab-frame-take-photo.html
https://beaufortfrancois.github.io/samples/image-capture/update-camera-zoom.html (This one works better with Android camera from)

Ah — excellent. Thanks! I'll take a look.
On 1 December 2016 at 11:40, François Beaufort<EMAIL_ADDRESS>wrote:

OK. So we have now two samples you can try at
https://beaufortfrancois.github.io/samples/image-
capture/grab-frame-take-photo.html
https://beaufortfrancois.github.io/samples/image-
capture/update-camera-zoom.html (This one works better with Android
camera from)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleChrome/samples/pull/449#issuecomment-264150418,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMhqgwJdqQYpSyHfZ3RmTwtg4ygsn-yks5rDrJCgaJpZM4K5Ply
.

@samdutton (gentle ping)

Zoom demo looks great — LGTM.
Did a PR (nit) for the first demo:
a ImageBitmap => an ImageBitmap
Also — I'd also be inclined to change 'photographic device such as a
webcam' to 'camera', since the difference between photo and video is
meaningful here — and 'webcam' sounds specifically like something for a
desktop machine (i.e. not a mobile device camera).
On 6 December 2016 at 10:00, François Beaufort<EMAIL_ADDRESS>wrote:

@samdutton https://github.com/samdutton (gentle ping)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleChrome/samples/pull/449#issuecomment-265108911,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMhqg4NKBfL2F3gu5CY-9VdBA6iOiewks5rFTJBgaJpZM4K5Ply
.

@samdutton Thank you! It should be addressed in https://github.com/GoogleChrome/samples/pull/449/commits/1be1c99a9c3dc05c24347f03d084618fe01b8c48

@beaufortfrancois @samdutton - can we land this asap.

This is ready to go as far as I'm concerned.
On 7 December 2016 at 14:19, Paul Kinlan<EMAIL_ADDRESS>wrote:

@beaufortfrancois https://github.com/beaufortfrancois @samdutton
https://github.com/samdutton - can we land this asap.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleChrome/samples/pull/449#issuecomment-265458477,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMhqgsTU7PPwqZ6bQIBRyBg2CCok4o3ks5rFsB0gaJpZM4K5Ply
.

Let's merge!
On Wed, Dec 7, 2016, 3:52 PM Sam Dutton<EMAIL_ADDRESS>wrote:

This is ready to go as far as I'm concerned.
On 7 December 2016 at 14:19, Paul Kinlan<EMAIL_ADDRESS>wrote:

@beaufortfrancois https://github.com/beaufortfrancois @samdutton
https://github.com/samdutton - can we land this asap.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/GoogleChrome/samples/pull/449#issuecomment-265458477
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AAMhqgsTU7PPwqZ6bQIBRyBg2CCok4o3ks5rFsB0gaJpZM4K5Ply
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleChrome/samples/pull/449#issuecomment-265466935,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAmuboYrFX5g-fG4RnZhJnXcJb267G5Oks5rFsgXgaJpZM4K5Ply
.


Focus Mode: Fullscreen

Switch to fullscreen when in focus mode.

From the docs:
setFullscreen()

setFullscreen(fullscreen): Promise<void>

Sets the window fullscreen state.
Parameters
Parameter	Type	Description
fullscreen	boolean	Whether the window should go to fullscreen or not.
Returns

Promise<void>

A promise indicating the success or failure of the operation.
Example

import { getCurrentWindow } from '@tauri-apps/api/window';
await getCurrentWindow().setFullscreen(true);

Source: https://github.com/tauri-apps/tauri/blob/dev/packages/api/src/window.ts#L1380
[isFullscreen()](https://tauri.app/reference/javascript/api/namespacewindow/#isfullscreen)

isFullscreen(): Promise<boolean>

Gets the window’s current fullscreen state.
[Returns](https://tauri.app/reference/javascript/api/namespacewindow/#returns-17)

[Promise](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Promise)<boolean>

Whether the window is in fullscreen mode or not.
[Example](https://tauri.app/reference/javascript/api/namespacewindow/#example-14)

import { getCurrentWindow } from '@tauri-apps/api/window';
const fullscreen = await getCurrentWindow().isFullscreen();

Source: https://github.com/tauri-apps/tauri/blob/dev/packages/api/src/window.ts#L604

How to implement fullscreen in Tauri v2 (not documented nicely in Tauri's docs):
Key Components and How They Work Together:

src/main.js (JavaScript/Frontend):

toggleFocusMode() Function: This function is the core of the fullscreen implementation.

It toggles a focusModeEnabled boolean variable.
It uses window.__TAURI__.window.getCurrentWindow() to get a reference to the current Tauri window.
It calls window.setFullscreen(focusModeEnabled) to switch the window to fullscreen (if focusModeEnabled is true) or back to windowed mode (if focusModeEnabled is false).
It updates the UI status to reflect the focus mode state.

handleFocusModeShortcut(event) Function: This function listens for the cmd+f (Mac) or ctrl+f (Windows) keyboard shortcut. When detected, it calls toggleFocusMode() to toggle the fullscreen state.
Event Listeners: The thoughtInputEl (the main text area) has event listeners for keydown to capture the focus mode shortcut and mousedown to prevent selection when in focus mode.
Focus Mode Restrictions: When focus mode is enabled, the code prevents editing, deletion, selection, and cut/copy/paste actions in the text area.

src-tauri/tauri.conf.json (Tauri Configuration):

app.security.capabilities: This section is crucial. It defines the permissions that the application has.

The main-capability is defined, and it includes the permission "core:window:allow-set-fullscreen". This permission is required for the setFullscreen function to work.

src-tauri/capabilities/main.json (Capability Definition):

This file defines the main-capability in more detail, specifying that it applies to the "main" window and includes the core:window:allow-set-fullscreen permission.

Implementation Steps:

Configure Tauri:

Ensure your src-tauri/tauri.conf.json file has the main-capability defined in the app.security.capabilities array, and that this capability includes the core:window:allow-set-fullscreen permission.
Make sure the src-tauri/capabilities/main.json file exists and correctly defines the main-capability with the core:window:allow-set-fullscreen permission.

Implement the Toggle Logic:

In your frontend JavaScript (like src/main.js), use window.__TAURI__.window.getCurrentWindow() to get the current window object.
Create a function (like toggleFocusMode()) that:

Toggles a boolean variable to track the fullscreen state.
Calls window.setFullscreen(true) to enter fullscreen or window.setFullscreen(false) to exit fullscreen, based on the boolean variable.

Add an event listener for a keyboard shortcut (like cmd+f or ctrl+f) to trigger the toggle function.

Handle Focus Mode Restrictions (Optional):

If you want to prevent editing while in fullscreen, add event listeners to the input element to prevent keyboard input, mouse selection, and cut/copy/paste actions.

In Summary:
The key to implementing fullscreen in Tauri v2 is:

Permission: You must include the core:window:allow-set-fullscreen permission in your Tauri configuration.
API: Use window.setFullscreen(true) and window.setFullscreen(false) from the @tauri-apps/api/window to control the fullscreen state.
Window Object: Get the current window object using window.__TAURI__.window.getCurrentWindow().


Random fix

This PR replaces the np.random to random from python standard library.
Also adds a possibility to call warp affine if the transform is affine (in MatrixTransform)

Codecov Report

Merging #19 into master will decrease coverage by 0.1%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #19      +/-   ##
==========================================
- Coverage     100%   99.89%   -0.11%
==========================================
  Files          13       12       -1
  Lines         941      944       +3
==========================================
+ Hits          941      943       +2
- Misses          0        1       +1

Impacted Files
Coverage Δ

solt/core/_core.py
100% <100%> (ø)
:arrow_up:

solt/transforms/_transforms.py
100% <100%> (ø)
:arrow_up:

solt/base_transforms/_base_transforms.py
99.52% <100%> (-0.48%)
:arrow_down:

solt/__init__.py

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 a6495f1...bfc7470. Read the comment docs.


Bad Loss Of Model

Hi author,
I'm really appreciate you for the nice source code. But when i set up enviroment for training , i can't achieve good result like your repo . I got the nice loss of training , but in validation loss increase , i think may be the model is overfitting . May be can you recommand me some way to improve the accuracy ?
Thanks !

I have the same problem. Have you solved it?


Revert state standby back to state off

Breaking Change:
State Standby is reverted back to State Off. User defined scripts, automations, etc., will need to be updated.
Description:
Fixes unforeseen front end card issue with change to state_standby from #28261. Service turn_off called when state is standby instead of turn_on when power button is clicked.
Related issue (if applicable): fixes #28891
Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

This is a workaround for a frontend bug. We should not change the backend for this.

This is a workaround for a frontend bug. We should not change the backend for this.

@ballob So what would be the best direction for this? Can we do a simple frontend change? Like home-assistant/homeassistant-polymer#4250


Remove code climate

Changes proposed in this pull request

Removes code climate in favour of codecov

I don't think its a big issue but the codecov notification seems to update a few times after cucumber tests finish etc (look at the edits). From the docs it seems as though its suppose to wait to notify until all CI has finished so not sure if we need to tweak something there.


BlockBlobClientTest.ConcurrentUpload_LIVEONLY_ fails with HTTP status code 201 won't be retried

Looking at recent CI errors post-commit (for live or nightly tests), there is an error in the runs:
From
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=2586969&view=logs&j=9778bb1b-cd71-5fb9-145c-ec3971aeda6f&t=dfc293f3-3187-52c1-9d66-0389268ad4ff
On ValidateLive Win2019_x86_with_unit_test_libcurl
https://github.com/Azure/azure-sdk-for-cpp/blob/5059347098c511b5de11c9d112eb11f7a330870c/sdk/storage/azure-storage-blobs/test/ut/block_blob_client_test.cpp#L1678
The log file is quite large, but here is some snippet of it:
2023-02-24T02:45:47.0143338Z test 97
2023-02-24T02:45:47.0144159Z         Start  97: azure-storage-blobs.BlockBlobClientTest.ConcurrentUpload_LIVEONLY_
2023-02-24T02:45:47.0144652Z
2023-02-24T02:45:47.0145707Z 97: Test command: D:\a\_work\1\s\build\sdk\storage\azure-storage-blobs\test\ut\Debug\azure-storage-blobs-test.exe "--gtest_filter=BlockBlobClientTest.ConcurrentUpload_LIVEONLY_" "--gtest_also_run_disabled_tests"
2023-02-24T02:45:47.0146966Z 97: Working Directory: D:/a/_work/1/s/build/sdk/storage/azure-storage-blobs/test/ut
2023-02-24T02:45:47.0147865Z 97: Test timeout computed to be: 10000000
2023-02-24T02:45:47.0148809Z 97: Running main() from D:\a\_work\1\s\build\_deps\googletest-src\googletest\src\gtest_main.cc
2023-02-24T02:45:47.0149933Z 97: Note: Google Test filter = BlockBlobClientTest.ConcurrentUpload_LIVEONLY_
2023-02-24T02:45:47.0150856Z 97: [==========] Running 1 test from 1 test suite.
2023-02-24T02:45:47.0151675Z 97: [----------] Global test environment set-up.
2023-02-24T02:45:47.0152512Z 97: [----------] 1 test from BlockBlobClientTest
2023-02-24T02:45:47.0153993Z 97: [ RUN      ] BlockBlobClientTest.ConcurrentUpload_LIVEONLY_
2023-02-24T02:45:47.0156017Z 97: [2023-02-24T02:45:39.9675438Z] INFO  : HTTP Request : PUT https://***.blob.core.windows.net/blockblobclienttestconcurrentupload?restype=container
2023-02-24T02:45:47.0157719Z 97: authorization : REDACTED
2023-02-24T02:45:47.0159393Z 97: user-agent : azsdk-cpp-storage-blobs/12.7.0-beta.2 (Windows Server 2019 Datacenter 6.3 17763 17763.1.x86fre.rs5_release.180914-1434)
2023-02-24T02:45:47.0161335Z 97: x-ms-client-request-id : 644f4f65-9b4b-4482-4720-8cce60919ee5
2023-02-24T02:45:47.0162825Z 97: x-ms-date : Fri, 24 Feb 2023 02:45:39 GMT
2023-02-24T02:45:47.0164258Z 97: x-ms-version : 2021-12-02
2023-02-24T02:45:47.0165799Z 97: [2023-02-24T02:45:39.9676652Z] DEBUG : [CURL Transport Adapter]: Creating a new session.
2023-02-24T02:45:47.0167582Z 97: [2023-02-24T02:45:39.9677564Z] DEBUG : [CURL Transport Adapter]: Spawn new connection.
2023-02-24T02:45:47.0169363Z 97: [2023-02-24T02:45:39.9888615Z] DEBUG : [CURL Transport Adapter]: No Host in request headers. Adding it
2023-02-24T02:45:47.0171223Z 97: [2023-02-24T02:45:39.9890258Z] DEBUG : [CURL Transport Adapter]: No content-length in headers. Adding it
2023-02-24T02:45:47.0173084Z 97: [2023-02-24T02:45:39.9891310Z] DEBUG : [CURL Transport Adapter]: Using 100-continue for PUT request
2023-02-24T02:45:47.0175126Z 97: [2023-02-24T02:45:39.9892487Z] DEBUG : [CURL Transport Adapter]: Send request without payload
2023-02-24T02:45:47.0176921Z 97: [2023-02-24T02:45:39.9895220Z] DEBUG : [CURL Transport Adapter]: Parse server response
2023-02-24T02:45:47.0178774Z 97: [2023-02-24T02:45:39.9972608Z] DEBUG : [CURL Transport Adapter]: Check server response before upload starts
2023-02-24T02:45:47.0180650Z 97: [2023-02-24T02:45:39.9973568Z] DEBUG : [CURL Transport Adapter]: Server rejected the upload request
2023-02-24T02:45:47.0182606Z 97: [2023-02-24T02:45:39.9974419Z] DEBUG : [CURL Transport Adapter]: Request completed. Moving response out of session and session to response.
2023-02-24T02:45:47.0184454Z 97: [2023-02-24T02:45:39.9975612Z] DEBUG : Moving connection to pool...
2023-02-24T02:45:47.0186088Z 97: [2023-02-24T02:45:39.9976800Z] DEBUG : Start clean thread
2023-02-24T02:45:47.0187690Z 97: [2023-02-24T02:45:39.9980941Z] INFO  : HTTP Response (30ms) : 201 Created
2023-02-24T02:45:47.0189167Z 97: content-length : 0
2023-02-24T02:45:47.0190492Z 97: date : Fri, 24 Feb 2023 02:45:39 GMT
2023-02-24T02:45:47.0191856Z 97: etag : "0x8DB1611373B03C9"
2023-02-24T02:45:47.0193229Z 97: last-modified : Fri, 24 Feb 2023 02:45:39 GMT
2023-02-24T02:45:47.0194570Z 97: server : Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
2023-02-24T02:45:47.0195542Z 97: x-ms-client-request-id : 644f4f65-9b4b-4482-4720-8cce60919ee5
2023-02-24T02:45:47.0196444Z 97: x-ms-request-id : be92679e-c01e-0058-33fa-472497000000
2023-02-24T02:45:47.0197267Z 97: x-ms-version : 2021-12-02
2023-02-24T02:45:47.0198144Z 97: [2023-02-24T02:45:39.9982459Z] INFO  : HTTP status code 201 won't be retried.
2023-02-24T02:45:47.0199354Z 97: [2023-02-24T02:45:40.0006787Z] INFO  : HTTP Request : PUT https://***.blob.core.windows.net/blockblobclienttestconcurrentupload/pC2TBj6ktI
2023-02-24T02:45:47.0200329Z 97: authorization : REDACTED
2023-02-24T02:45:47.0201088Z 97: content-length : 1024
2023-02-24T02:45:47.0202048Z 97: user-agent : azsdk-cpp-storage-blobs/12.7.0-beta.2 (Windows Server 2019 Datacenter 6.3 17763 17763.1.x86fre.rs5_release.180914-1434)
2023-02-24T02:45:47.0203039Z 97: x-ms-access-tier : Hot
2023-02-24T02:45:47.0203791Z 97: x-ms-blob-cache-control : no-cache
2023-02-24T02:45:47.0204603Z 97: x-ms-blob-content-disposition : attachment
2023-02-24T02:45:47.0205577Z 97: x-ms-blob-content-encoding : identity
2023-02-24T02:45:47.0206366Z 97: x-ms-blob-content-language : en-US
2023-02-24T02:45:47.0207192Z 97: x-ms-blob-content-type : application/x-binary
2023-02-24T02:45:47.0207957Z 97: x-ms-blob-type : BlockBlob
2023-02-24T02:45:47.0208786Z 97: x-ms-client-request-id : 00241fa0-3bc7-4c78-5303-050b3d4aaa4e
2023-02-24T02:45:47.0209660Z 97: x-ms-date : Fri, 24 Feb 2023 02:45:39 GMT
2023-02-24T02:45:47.0210533Z 97: x-ms-meta-key1 : REDACTED
2023-02-24T02:45:47.0211288Z 97: x-ms-meta-key2 : REDACTED
2023-02-24T02:45:47.0212026Z 97: x-ms-version : 2021-12-02
2023-02-24T02:45:47.0212938Z 97: [2023-02-24T02:45:40.0008134Z] DEBUG : [CURL Transport Adapter]: Creating a new session.
2023-02-24T02:45:47.0214678Z 97: [2023-02-24T02:45:40.0009344Z] DEBUG : [CURL Transport Adapter]: Re-using connection from the pool.
2023-02-24T02:45:47.0217484Z 97: [2023-02-24T02:45:40.0012135Z] DEBUG : [CURL Transport Adapter]: No Host in request headers. Adding it
2023-02-24T02:45:47.0219365Z 97: [2023-02-24T02:45:40.0013867Z] DEBUG : [CURL Transport Adapter]: Using 100-continue for PUT request
2023-02-24T02:45:47.0220559Z 97: [2023-02-24T02:45:40.0015091Z] DEBUG : [CURL Transport Adapter]: Send request without payload
2023-02-24T02:45:47.0221617Z 97: [2023-02-24T02:45:40.0018519Z] DEBUG : [CURL Transport Adapter]: Parse server response
2023-02-24T02:45:47.0222863Z 97: [2023-02-24T02:45:40.0072222Z] DEBUG : [CURL Transport Adapter]: Check server response before upload starts
2023-02-24T02:45:47.0223973Z 97: [2023-02-24T02:45:40.0073124Z] DEBUG : [CURL Transport Adapter]: Upload payload
2023-02-24T02:45:47.0225039Z 97: [2023-02-24T02:45:40.0075810Z] DEBUG : [CURL Transport Adapter]: Upload completed. Parse server response
2023-02-24T02:45:47.0226352Z 97: [2023-02-24T02:45:40.0149059Z] DEBUG : [CURL Transport Adapter]: Request completed. Moving response out of session and session to response.
2023-02-24T02:45:47.0227448Z 97: [2023-02-24T02:45:40.0150183Z] DEBUG : Moving connection to pool...
2023-02-24T02:45:47.0228429Z 97: [2023-02-24T02:45:40.0151118Z] DEBUG : Clean thread running. Won't start a new one.
2023-02-24T02:45:47.0229436Z 97: [2023-02-24T02:45:40.0154523Z] INFO  : HTTP Response (14ms) : 201 Created
2023-02-24T02:45:47.0230279Z 97: content-length : 0
2023-02-24T02:45:47.0231071Z 97: content-md5 : o0o652+ZZqkzbGDRbAdeuw==
2023-02-24T02:45:47.0231875Z 97: date : Fri, 24 Feb 2023 02:45:39 GMT
2023-02-24T02:45:47.0232641Z 97: etag : "0x8DB161137400D01"
2023-02-24T02:45:47.0233474Z 97: last-modified : Fri, 24 Feb 2023 02:45:40 GMT
2023-02-24T02:45:47.0234319Z 97: server : Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
2023-02-24T02:45:47.0235222Z 97: x-ms-client-request-id : 00241fa0-3bc7-4c78-5303-050b3d4aaa4e
2023-02-24T02:45:47.0236063Z 97: x-ms-content-crc64 : SXkg30Xi9xU=
2023-02-24T02:45:47.0236891Z 97: x-ms-request-id : be9267a5-c01e-0058-39fa-472497000000
2023-02-24T02:45:47.0237745Z 97: x-ms-request-server-encrypted : true
2023-02-24T02:45:47.0238503Z 97: x-ms-version : 2021-12-02
2023-02-24T02:45:47.0239307Z 97: x-ms-version-id : 2023-02-24T02:45:40.0256769Z
2023-02-24T02:45:47.0240367Z 97: [2023-02-24T02:45:40.0155621Z] INFO  : HTTP status code 201 won't be retried.
2023-02-24T02:45:47.0241600Z 97: [2023-02-24T02:45:40.0164065Z] INFO  : HTTP Request : HEAD https://***.blob.core.windows.net/blockblobclienttestconcurrentupload/pC2TBj6ktI
2023-02-24T02:45:47.0242585Z 97: authorization : REDACTED
2023-02-24T02:45:47.0243559Z 97: user-agent : azsdk-cpp-storage-blobs/12.7.0-beta.2 (Windows Server 2019 Datacenter 6.3 17763 17763.1.x86fre.rs5_release.180914-1434)
2023-02-24T02:45:47.0244620Z 97: x-ms-client-request-id : bbd400c5-cac1-474a-5415-d7b93f1fb462
2023-02-24T02:45:47.0245497Z 97: x-ms-date : Fri, 24 Feb 2023 02:45:40 GMT
2023-02-24T02:45:47.0246302Z 97: x-ms-version : 2021-12-02
2023-02-24T02:45:47.0247187Z 97: [2023-02-24T02:45:40.0165040Z] DEBUG : [CURL Transport Adapter]: Creating a new session.
2023-02-24T02:45:47.0249300Z 97: [2023-02-24T02:45:40.0166131Z] DEBUG : [CURL Transport Adapter]: Re-using connection from the pool.
2023-02-24T02:45:47.0250360Z 97: [2023-02-24T02:45:40.0167497Z] DEBUG : [CURL Transport Adapter]: No Host in request headers. Adding it
2023-02-24T02:45:47.0251431Z 97: [2023-02-24T02:45:40.0168786Z] DEBUG : [CURL Transport Adapter]: Send request without payload
2023-02-24T02:45:47.0252475Z 97: [2023-02-24T02:45:40.0171697Z] DEBUG : [CURL Transport Adapter]: Parse server response
2023-02-24T02:45:47.0253936Z 97: [2023-02-24T02:45:40.0222293Z] DEBUG : [CURL Transport Adapter]: Request completed. Moving response out of session and session to response.
2023-02-24T02:45:47.0255275Z 97: [2023-02-24T02:45:40.0223281Z] DEBUG : Moving connection to pool...
2023-02-24T02:45:47.0256669Z 97: [2023-02-24T02:45:40.0224207Z] DEBUG : Clean thread running. Won't start a new one.
2023-02-24T02:45:47.0258975Z 97: [2023-02-24T02:45:40.0229000Z] INFO  : HTTP Response (6ms) : 200 OK
2023-02-24T02:45:47.0260539Z 97: accept-ranges : bytes
2023-02-24T02:45:47.0261916Z 97: access-control-allow-origin : REDACTED
2023-02-24T02:45:47.0263323Z 97: access-control-expose-headers : REDACTED
2023-02-24T02:45:47.0264645Z 97: cache-control : no-cache
2023-02-24T02:45:47.0265947Z 97: content-disposition : attachment
2023-02-24T02:45:47.0267227Z 97: content-encoding : identity
2023-02-24T02:45:47.0270238Z 97: content-language : en-US
2023-02-24T02:45:47.0272121Z 97: content-length : 1024
2023-02-24T02:45:47.0273577Z 97: content-md5 : o0o652+ZZqkzbGDRbAdeuw==
2023-02-24T02:45:47.0274780Z 97: content-type : application/x-binary
2023-02-24T02:45:47.0276155Z 97: date : Fri, 24 Feb 2023 02:45:39 GMT
2023-02-24T02:45:47.0277232Z 97: etag : "0x8DB161137400D01"
2023-02-24T02:45:47.0278726Z 97: last-modified : Fri, 24 Feb 2023 02:45:40 GMT
2023-02-24T02:45:47.0280564Z 97: server : Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
2023-02-24T02:45:47.0282418Z 97: x-ms-access-tier : Hot
2023-02-24T02:45:47.0284079Z 97: x-ms-access-tier-change-time : Fri, 24 Feb 2023 02:45:40 GMT
2023-02-24T02:45:47.0285413Z 97: x-ms-blob-type : BlockBlob
2023-02-24T02:45:47.0286734Z 97: x-ms-client-request-id : bbd400c5-cac1-474a-5415-d7b93f1fb462
2023-02-24T02:45:47.0287991Z 97: x-ms-creation-time : Fri, 24 Feb 2023 02:45:40 GMT
2023-02-24T02:45:47.0288908Z 97: x-ms-is-current-version : true
2023-02-24T02:45:47.0289668Z 97: x-ms-lease-state : available
2023-02-24T02:45:47.0290436Z 97: x-ms-lease-status : unlocked
2023-02-24T02:45:47.0291203Z 97: x-ms-meta-key1 : REDACTED
2023-02-24T02:45:47.0291939Z 97: x-ms-meta-key2 : REDACTED
2023-02-24T02:45:47.0292768Z 97: x-ms-request-id : be9267ae-c01e-0058-42fa-472497000000
2023-02-24T02:45:47.0293581Z 97: x-ms-server-encrypted : true
2023-02-24T02:45:47.0294329Z 97: x-ms-version : 2021-12-02
2023-02-24T02:45:47.0295153Z 97: x-ms-version-id : 2023-02-24T02:45:40.0256769Z
2023-02-24T02:45:47.0296082Z 97: [2023-02-24T02:45:40.0230132Z] INFO  : HTTP status code 200 won't be retried.
2023-02-24T02:45:47.0297511Z 97: [2023-02-24T02:45:40.0749236Z] INFO  : HTTP Request : PUT https://***.blob.core.windows.net/blockblobclienttestconcurrentupload/8S0sn5wtmX?blockid=MDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMA%3D%3D&comp=block
2023-02-24T02:45:47.0298729Z 97: authorization : REDACTED
2023-02-24T02:45:47.0299499Z 97: content-length : 12288
2023-02-24T02:45:47.0300469Z 97: user-agent : azsdk-cpp-storage-blobs/12.7.0-beta.2 (Windows Server 2019 Datacenter 6.3 17763 17763.1.x86fre.rs5_release.180914-1434)
2023-02-24T02:45:47.0301536Z 97: x-ms-client-request-id : 5af11f61-f8ab-42a1-5251-63fbe070acf0
2023-02-24T02:45:47.0302411Z 97: x-ms-date : Fri, 24 Feb 2023 02:45:40 GMT
2023-02-24T02:45:47.0303197Z 97: x-ms-version : 2021-12-02
2023-02-24T02:45:47.0304104Z 97: [2023-02-24T02:45:40.0751255Z] DEBUG : [CURL Transport Adapter]: Creating a new session.
2023-02-24T02:45:47.0305184Z 97: [2023-02-24T02:45:40.0754119Z] DEBUG : [CURL Transport Adapter]: Re-using connection from the pool.
2023-02-24T02:45:47.0306468Z 97: [2023-02-24T02:45:40.0757422Z] DEBUG : [CURL Transport Adapter]: No Host in request headers. Adding it
2023-02-24T02:45:47.0308223Z 97: [2023-02-24T02:45:40.0759721Z] DEBUG : [CURL Transport Adapter]: Using 100-continue for PUT request
2023-02-24T02:45:47.0311324Z 97: [[2023-02-24T02:45:40.0761155Z2023-02-24T02:45:40.0761207Z] [] INFO INFO  :  : HTTP Request : PUT https://***.blob.core.windows.net/blockblobclienttestconcurrentupload/ZbDPDnUaZE?blockid=MDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMA%3D%3D&comp=block
2023-02-24T02:45:47.0313341Z 97: authorization : REDACTED
2023-02-24T02:45:47.0314128Z 97: content-length : 16384
2023-02-24T02:45:47.0315116Z 97: user-agent : azsdk-cpp-storage-blobs/12.7.0-beta.2 (Windows Server 2019 Datacenter 6.3 17763 17763.1.x86fre.rs5_release.180914-1434)
2023-02-24T02:45:47.0316575Z 97: x-ms-client-request-id : f22936e5-d456-4441-7b6b-c1d2a53cb7bb
2023-02-24T02:45:47.0317496Z 97: x-ms-date : Fri, 24 Feb 2023 02:45:40 GMT
2023-02-24T02:45:47.0318814Z 97: x-ms-version : 2021-12-02HTTP Request : PUT https://***.blob.core.windows.net/blockblobclienttestconcurrentupload/hVmwkqf5s7?blockid=MDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMA%3D%3D&comp=block
2023-02-24T02:45:47.0320024Z 97: authorization : REDACTED
2023-02-24T02:45:47.0320766Z 97: content-length : 12288
2023-02-24T02:45:47.0321735Z 97: user-agent : azsdk-cpp-storage-blobs/12.7.0-beta.2 (Windows Server 2019 Datacenter 6.3 17763 17763.1.x86fre.rs5_release.180914-1434)
2023-02-24T02:45:47.0322819Z 97: x-ms-client-request-id : 310e2903-1e1e-44ee-6445-f607ff8bbc72
2023-02-24T02:45:47.0323697Z 97: x-ms-date : Fri, 24 Feb 2023 02:45:40 GMT
2023-02-24T02:45:47.0324663Z 97: x-ms-version : 2021-12-02
2023-02-24T02:45:47.0325377Z 97:
2023-02-24T02:45:47.0326220Z 97: 2023-02-24T02:45:40.0761259Z] DEBUG : [CURL Transport Adapter]: Send request without payload
2023-02-24T02:45:47.0327646Z 97: [2023-02-24T02:45:40.0762695Z] INFO  : HTTP Request : PUT https://***.blob.core.windows.net/blockblobclienttestconcurrentupload/PwXkPuP6HN?blockid=MDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMA%3D%3D&comp=block
...
...abbreviated
...
2023-02-24T02:46:38.3696627Z 97: ] DEBUG :  : [CURL Transport Adapter]: Send request without payload[CURL Transport Adapter]: Creating a new session.
2023-02-24T02:46:38.3697580Z 97:
2023-02-24T02:46:38.3698424Z 97: [2023-02-24T02:46:06.3357940Z] DEBUG : [CURL Transport Adapter]: Send request without payload
2023-02-24T02:46:38.3699475Z 97: [2023-02-24T02:46:06.3358533Z] DEBUG : [CURL Transport Adapter]: Re-using connection from the pool.
2023-02-24T02:46:38.3700530Z 97: [2023-02-24T02:46:06.3360315Z] DEBUG : [CURL Transport Adapter]: No Host in request headers. Adding it[
2023-02-24T02:46:38.3701565Z 97: 2023-02-24T02:46:06.3360633Z] DEBUG : [CURL Transport Adapter]: Parse server response
2023-02-24T02:46:38.3702656Z 97: [2023-02-24T02:46:06.3361763Z] DEBUG : [[CURL Transport Adapter]: Parse server response2023-02-24T02:46:06.3361979Z
2023-02-24T02:46:38.3703697Z 97: ] DEBUG : [CURL Transport Adapter]: Using 100-continue for PUT request
2023-02-24T02:46:38.3704668Z 97: [2023-02-24T02:46:06.3363279Z] DEBUG : [CURL Transport Adapter]: Send request without payload
2023-02-24T02:46:38.3705716Z 97: [2023-02-24T02:46:06.3366537Z] DEBUG : [CURL Transport Adapter]: Parse server response
2023-02-24T02:46:38.3706680Z 97: [2023-02-24T02:46:06.3364549Z] DEBUG : [CURL Transport Adapter]: No Host in request headers. Adding it
2023-02-24T02:46:38.3707760Z 97: [2023-02-24T02:46:06.3370947Z] DEBUG : [CURL Transport Adapter]: Using 100-continue for PUT request
2023-02-24T02:46:38.3708784Z 97: [2023-02-24T02:46:06.3372098Z] DEBUG : [CURL Transport Adapter]: Send request without payload
2023-02-24T02:46:38.3709801Z 97: [2023-02-24T02:46:06.3375442Z] DEBUG : [CURL Transport Adapter]: Parse server response
2023-02-24T02:46:38.3710960Z 97: [2023-02-24T02:46:06.3381590Z] DEBUG : [CURL Transport Adapter]: Check server response before upload starts
2023-02-24T02:46:38.3712001Z 97: [2023-02-24T02:46:06.3382746Z] DEBUG : [CURL Transport Adapter]: Upload payload
2023-02-24T02:46:38.3713038Z 97: [2023-02-24T02:46:06.3382682Z] DEBUG : [CURL Transport Adapter]: Check server response before upload starts
2023-02-24T02:46:38.3714260Z 97: [[2023-02-24T02:46:06.3384442Z2023-02-24T02:46:06.3384438Z] ] DEBUGDEBUG :  : [CURL Transport Adapter]: Upload payload[CURL Transport Adapter]: Upload completed. Parse server response
2023-02-24T02:46:38.3715299Z 97:
2023-02-24T02:46:38.3716151Z 97: [2023-02-24T02:46:06.3384462Z] DEBUG : [CURL Transport Adapter]: Check server response before upload starts
2023-02-24T02:46:38.3717395Z 97: [[2023-02-24T02:46:06.3386840Z2023-02-24T02:46:06.3386992Z] ] DEBUGDEBUG :  : [CURL Transport Adapter]: Upload payload[CURL Transport Adapter]: Upload completed. Parse server response
2023-02-24T02:46:38.3718420Z 97:
2023-02-24T02:46:38.3719287Z 97: [2023-02-24T02:46:06.3390131Z] DEBUG : [CURL Transport Adapter]: Upload completed. Parse server response
2023-02-24T02:46:38.3720434Z 97: [2023-02-24T02:46:06.3407867Z] DEBUG : [CURL Transport Adapter]: Request completed. Moving response out of session and session to response.
2023-02-24T02:46:38.3721496Z 97: [2023-02-24T02:46:06.3416739Z] INFO  : HTTP Response (7ms) : 200 OK
2023-02-24T02:46:38.3722379Z 97: accept-ranges : bytes
2023-02-24T02:46:38.3723149Z 97: access-control-allow-origin : REDACTED
2023-02-24T02:46:38.3723989Z 97: access-control-expose-headers : REDACTED
2023-02-24T02:46:38.3724756Z 97: content-length : 817281
2023-02-24T02:46:38.3725530Z 97: content-type : application/octet-stream
2023-02-24T02:46:38.3726351Z 97: date : Fri, 24 Feb 2023 02:46:05 GMT
2023-02-24T02:46:38.3727131Z 97: etag : "0x8DB161146EE8661"
2023-02-24T02:46:38.3727940Z 97: last-modified : Fri, 24 Feb 2023 02:46:06 GMT
2023-02-24T02:46:38.3728789Z 97: server : Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
2023-02-24T02:46:38.3729569Z 97: x-ms-blob-type : BlockBlob
2023-02-24T02:46:38.3730419Z 97: x-ms-client-request-id : 651181b9-afdc-4d53-57e6-c1b21a5e604e
2023-02-24T02:46:38.3731296Z 97: x-ms-creation-time : Fri, 24 Feb 2023 02:46:06 GMT
2023-02-24T02:46:38.3732130Z 97: x-ms-is-current-version : true
2023-02-24T02:46:38.3732877Z 97: x-ms-lease-state : available
2023-02-24T02:46:38.3733721Z 97: x-ms-lease-status : unlocked
2023-02-24T02:46:38.3734569Z 97: x-ms-request-id : d2929af5-801e-0082-6cfa-47bd76000000
2023-02-24T02:46:38.3735376Z 97: x-ms-server-encrypted : true
2023-02-24T02:46:38.3736132Z 97: x-ms-version : 2021-12-02
2023-02-24T02:46:38.3736962Z 97: x-ms-version-id : 2023-02-24T02:46:06.3349345Z
2023-02-24T02:46:38.3737982Z 97: [2023-02-24T02:46:06.3419045Z] INFO  : HTTP status code 200 won't be retried.
2023-02-24T02:46:38.3739109Z 97: [2023-02-24T02:46:06.3428521Z] DEBUG : [CURL Transport Adapter]: Request completed. Moving response out of session and session to response.
2023-02-24T02:46:38.3740182Z 97: [2023-02-24T02:46:06.3429815Z] DEBUG : Moving connection to pool...
2023-02-24T02:46:38.3741174Z 97: [2023-02-24T02:46:06.3430498Z] DEBUG : Clean thread running. Won't start a new one.
2023-02-24T02:46:38.3742147Z 97: [2023-02-24T02:46:06.3433069Z] INFO  : HTTP Response (8ms) : 201 Created
2023-02-24T02:46:38.3743004Z 97: content-length : 0
2023-02-24T02:46:38.3743761Z 97: date : Fri, 24 Feb 2023 02:46:05 GMT
2023-02-24T02:46:38.3744602Z 97: server : Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
2023-02-24T02:46:38.3745497Z 97: x-ms-client-request-id : 68e9d772-ef05-473e-609b-dd9393613e92
2023-02-24T02:46:38.3746332Z 97: x-ms-content-crc64 : fUpAW5XpoRU=
2023-02-24T02:46:38.3747178Z 97: x-ms-request-id : df5faadd-401e-0069-17fa-47c584000000
2023-02-24T02:46:38.3748001Z 97: x-ms-request-server-encrypted : true
2023-02-24T02:46:38.3748749Z 97: x-ms-version : 2021-12-02
2023-02-24T02:46:38.3749733Z 97: [2023-02-24T02:46:06.3434042Z] INFO  : HTTP status code 201 won't be retried.
2023-02-24T02:46:38.3750811Z 97: [2023-02-24T02:46:06.3442478Z] DEBUG : [CURL Transport Adapter]: Request completed. Moving response out of session and session to response.
2023-02-24T02:46:38.3751894Z 97: [2023-02-24T02:46:06.3443507Z] DEBUG : Moving connection to pool...
2023-02-24T02:46:38.3752897Z 97: [2023-02-24T02:46:06.3446593Z] DEBUG : Clean thread running. Won't start a new one.
2023-02-24T02:46:38.3753863Z 97: [2023-02-24T02:46:06.3450028Z] INFO  : HTTP Response (10ms) : 201 Created
2023-02-24T02:46:38.3754722Z 97: content-length : 0
2023-02-24T02:46:38.3755477Z 97: date : Fri, 24 Feb 2023 02:46:05 GMT
2023-02-24T02:46:38.3756547Z 97: server : Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
2023-02-24T02:46:38.3758070Z 97: x-ms-client-request-id : ad4997dd-e7ae-4754-7f1c-e37a36f0b450
2023-02-24T02:46:38.3759113Z 97: x-ms-content-crc64 : E1sC1YEAjlc=
2023-02-24T02:46:38.3760176Z 97: x-ms-request-id : 2f6385ce-c01e-0005-51fa-472e13000000
2023-02-24T02:46:38.3761059Z 97: x-ms-request-server-encrypted : true
2023-02-24T02:46:38.3761848Z 97: x-ms-version : 2021-12-02
2023-02-24T02:46:38.3762710Z 97: [2023-02-24T02:46:06.3451012Z] INFO  : HTTP status code 201 won't be retried.
2023-02-24T02:46:38.3763794Z 97: [2023-02-24T02:46:06.3461093Z] DEBUG : [CURL Transport Adapter]: Request completed. Moving response out of session and session to response.
2023-02-24T02:46:38.3764878Z 97: [2023-02-24T02:46:06.3463753Z] DEBUG : Moving connection to pool...
2023-02-24T02:46:38.3765857Z 97: [2023-02-24T02:46:06.3464933Z] DEBUG : Clean thread running. Won't start a new one.
2023-02-24T02:46:38.3766847Z 97: [2023-02-24T02:46:06.3467733Z] INFO  : HTTP Response (10ms) : 201 Created
2023-02-24T02:46:38.3767672Z 97: content-length : 0
2023-02-24T02:46:38.3768454Z 97: date : Fri, 24 Feb 2023 02:46:05 GMT
2023-02-24T02:46:38.3769285Z 97: server : Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
2023-02-24T02:46:38.3770179Z 97: x-ms-client-request-id : 08c6ccaf-51ef-426a-4e8a-65b7bed2cb29
2023-02-24T02:46:38.3771032Z 97: x-ms-content-crc64 : n+R4D56skqI=
2023-02-24T02:46:38.3771852Z 97: x-ms-request-id : 26a60ff9-b01e-0052-1cfa-478020000000
2023-02-24T02:46:38.3772700Z 97: x-ms-request-server-encrypted : true
2023-02-24T02:46:38.3773450Z 97: x-ms-version : 2021-12-02
2023-02-24T02:46:38.3774307Z 97: [2023-02-24T02:46:06.3468688Z] INFO  : HTTP status code 201 won't be retried.
2023-02-24T02:46:38.3775487Z 97: [2023-02-24T02:46:06.3503060Z] DEBUG : [CURL Transport Adapter]: Check server response before upload starts
2023-02-24T02:46:38.3776504Z 97: [2023-02-24T02:46:06.3503879Z] DEBUG : [CURL Transport Adapter]: Upload payload
2023-02-24T02:46:38.3777553Z 97: [2023-02-24T02:46:06.3505824Z] DEBUG : [CURL Transport Adapter]: Upload completed. Parse server response
2023-02-24T02:46:38.3778677Z 97: [2023-02-24T02:46:06.3555919Z] DEBUG : [CURL Transport Adapter]: Request completed. Moving response out of session and session to response.
2023-02-24T02:46:38.3779756Z 97: [2023-02-24T02:46:06.3557275Z] DEBUG : Moving connection to pool...
2023-02-24T02:46:38.3780722Z 97: [2023-02-24T02:46:06.3558166Z] DEBUG : Clean thread running. Won't start a new one.
2023-02-24T02:46:38.3781714Z 97: [2023-02-24T02:46:06.3560620Z] INFO  : HTTP Response (29ms) : 201 Created
2023-02-24T02:46:38.3782546Z 97: content-length : 0
2023-02-24T02:46:38.3783301Z 97: date : Fri, 24 Feb 2023 02:46:05 GMT
2023-02-24T02:46:38.3784158Z 97: server : Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
2023-02-24T02:46:38.3785036Z 97: x-ms-client-request-id : 7f00123b-6332-4f05-6048-547558dbfa2d
2023-02-24T02:46:38.3785893Z 97: x-ms-content-crc64 : FyoYlvaAr2M=
2023-02-24T02:46:38.3786717Z 97: x-ms-request-id : b41be749-901e-006a-45fa-4724e0000000
2023-02-24T02:46:38.3787540Z 97: x-ms-request-server-encrypted : true
2023-02-24T02:46:38.3788317Z 97: x-ms-version : 2021-12-02
2023-02-24T02:46:38.3789185Z 97: [2023-02-24T02:46:06.3561592Z] INFO  : HTTP status code 201 won't be retried.
2023-02-24T02:46:38.3790493Z 97: [2023-02-24T02:46:06.3616119Z] INFO  : HTTP Request : PUT https://***.blob.core.windows.net/blockblobclienttestconcurrentupload/TkZof57Cfn?comp=blocklist
2023-02-24T02:46:38.3791504Z 97: authorization : REDACTED
2023-02-24T02:46:38.3792275Z 97: content-length : 23476
2023-02-24T02:46:38.3793062Z 97: content-type : application/xml; charset=UTF-8
2023-02-24T02:46:38.3794096Z 97: user-agent : azsdk-cpp-storage-blobs/12.7.0-beta.2 (Windows Server 2019 Datacenter 6.3 17763 17763.1.x86fre.rs5_release.180914-1434)
2023-02-24T02:46:38.3795135Z 97: x-ms-client-request-id : df0de06b-21e1-45e2-4e42-ed1119e5f743
2023-02-24T02:46:38.3796001Z 97: x-ms-date : Fri, 24 Feb 2023 02:46:06 GMT
2023-02-24T02:46:38.3796809Z 97: x-ms-version : 2021-12-02
2023-02-24T02:46:38.3797693Z 97: [2023-02-24T02:46:06.3617088Z] DEBUG : [CURL Transport Adapter]: Creating a new session.
2023-02-24T02:46:38.3798749Z 97: [2023-02-24T02:46:06.3620152Z] DEBUG : [CURL Transport Adapter]: Re-using connection from the pool.
2023-02-24T02:46:38.3799804Z 97: [2023-02-24T02:46:06.3622060Z] DEBUG : [CURL Transport Adapter]: No Host in request headers. Adding it
2023-02-24T02:46:38.3800880Z 97: [2023-02-24T02:46:06.3623323Z] DEBUG : [CURL Transport Adapter]: Using 100-continue for PUT request
2023-02-24T02:46:38.3801899Z 97: [2023-02-24T02:46:06.3624334Z] DEBUG : [CURL Transport Adapter]: Send request without payload
2023-02-24T02:46:38.3802925Z 97: [2023-02-24T02:46:06.3628236Z] DEBUG : [CURL Transport Adapter]: Parse server response
2023-02-24T02:46:38.3803989Z 97: [2023-02-24T02:46:06.3640392Z] DEBUG : [CURL Transport Adapter]: Check server response before upload starts
2023-02-24T02:46:38.3805005Z 97: [2023-02-24T02:46:06.3641556Z] DEBUG : [CURL Transport Adapter]: Upload payload
2023-02-24T02:46:38.3806030Z 97: [2023-02-24T02:46:06.3643924Z] DEBUG : [CURL Transport Adapter]: Upload completed. Parse server response
2023-02-24T02:46:38.3807017Z 97: [2023-02-24T02:46:06.3681021Z] DEBUG : Moving connection to pool...
2023-02-24T02:46:38.3807998Z 97: [2023-02-24T02:46:06.3682323Z] DEBUG : Clean thread running. Won't start a new one.
2023-02-24T02:46:38.3809090Z 97: [2023-02-24T02:46:06.3750162Z] DEBUG : [CURL Transport Adapter]: Request completed. Moving response out of session and session to response.
2023-02-24T02:46:38.3810179Z 97: [2023-02-24T02:46:06.3751275Z] DEBUG : Moving connection to pool...
2023-02-24T02:46:38.3811249Z 97: [2023-02-24T02:46:06.3751910Z] DEBUG : Clean thread running. Won't start a new one.
2023-02-24T02:46:38.3812214Z 97: [2023-02-24T02:46:06.3754657Z] INFO  : HTTP Response (13ms) : 201 Created
2023-02-24T02:46:38.3813062Z 97: content-length : 0
2023-02-24T02:46:38.3813812Z 97: date : Fri, 24 Feb 2023 02:46:05 GMT
2023-02-24T02:46:38.3814604Z 97: etag : "0x8DB161146F5D830"
2023-02-24T02:46:38.3815398Z 97: last-modified : Fri, 24 Feb 2023 02:46:06 GMT
2023-02-24T02:46:38.3816247Z 97: server : Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
2023-02-24T02:46:38.3817148Z 97: x-ms-client-request-id : df0de06b-21e1-45e2-4e42-ed1119e5f743
2023-02-24T02:46:38.3817981Z 97: x-ms-content-crc64 : 9GLksLQaEMw=
2023-02-24T02:46:38.3818821Z 97: x-ms-request-id : b41be759-901e-006a-52fa-4724e0000000
2023-02-24T02:46:38.3819644Z 97: x-ms-request-server-encrypted : true
2023-02-24T02:46:38.3820391Z 97: x-ms-version : 2021-12-02
2023-02-24T02:46:38.3821214Z 97: x-ms-version-id : 2023-02-24T02:46:06.3829040Z
2023-02-24T02:46:38.3822118Z 97: [2023-02-24T02:46:06.3755578Z] INFO  : HTTP status code 201 won't be retried.
2023-02-24T02:46:38.3823290Z 97: [2023-02-24T02:46:06.3776568Z] INFO  : HTTP Request : GET https://***.blob.core.windows.net/blockblobclienttestconcurrentupload/TkZof57Cfn
2023-02-24T02:46:38.3824273Z 97: authorization : REDACTED
2023-02-24T02:46:38.3825265Z 97: user-agent : azsdk-cpp-storage-blobs/12.7.0-beta.2 (Windows Server 2019 Datacenter 6.3 17763 17763.1.x86fre.rs5_release.180914-1434)
2023-02-24T02:46:38.3826402Z 97: x-ms-client-request-id : 1c4ce602-5743-4d12-44f0-b88ffc6e8440
2023-02-24T02:46:38.3827280Z 97: x-ms-date : Fri, 24 Feb 2023 02:46:06 GMT
2023-02-24T02:46:38.3828042Z 97: x-ms-version : 2021-12-02
2023-02-24T02:46:38.3828920Z 97: [2023-02-24T02:46:06.3777852Z] DEBUG : [CURL Transport Adapter]: Creating a new session.
2023-02-24T02:46:38.3829975Z 97: [2023-02-24T02:46:06.3778983Z] DEBUG : [CURL Transport Adapter]: Re-using connection from the pool.
2023-02-24T02:46:38.3831025Z 97: [2023-02-24T02:46:06.3780285Z] DEBUG : [CURL Transport Adapter]: No Host in request headers. Adding it
2023-02-24T02:46:38.3832071Z 97: [2023-02-24T02:46:06.3781523Z] DEBUG : [CURL Transport Adapter]: Send request without payload
2023-02-24T02:46:38.3833072Z 97: [2023-02-24T02:46:06.3783918Z] DEBUG : [CURL Transport Adapter]: Parse server response
2023-02-24T02:46:38.3834049Z 97: [2023-02-24T02:46:06.3806990Z] DEBUG : Moving connection to pool...
2023-02-24T02:46:38.3835066Z 97: [2023-02-24T02:46:06.3808282Z] DEBUG : Clean thread running. Won't start a new one.
2023-02-24T02:46:38.3836164Z 97: [2023-02-24T02:46:06.3851023Z] DEBUG : [CURL Transport Adapter]: Request completed. Moving response out of session and session to response.
2023-02-24T02:46:38.3837247Z 97: [2023-02-24T02:46:06.3855123Z] INFO  : HTTP Response (7ms) : 200 OK
2023-02-24T02:46:38.3838204Z 97: accept-ranges : bytes
2023-02-24T02:46:38.3838973Z 97: access-control-allow-origin : REDACTED
2023-02-24T02:46:38.3839773Z 97: access-control-expose-headers : REDACTED
2023-02-24T02:46:38.3840568Z 97: content-length : 910727
2023-02-24T02:46:38.3841348Z 97: content-type : application/octet-stream
2023-02-24T02:46:38.3842063Z 97: date : Fri, 24 Feb 2023 02:46:05 GMT
2023-02-24T02:46:38.3842859Z 97: etag : "0x8DB161146F5D830"
2023-02-24T02:46:38.3843657Z 97: last-modified : Fri, 24 Feb 2023 02:46:06 GMT
2023-02-24T02:46:38.3844537Z 97: server : Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
2023-02-24T02:46:38.3845326Z 97: x-ms-blob-type : BlockBlob
2023-02-24T02:46:38.3846147Z 97: x-ms-client-request-id : 1c4ce602-5743-4d12-44f0-b88ffc6e8440
2023-02-24T02:46:38.3847040Z 97: x-ms-creation-time : Fri, 24 Feb 2023 02:46:06 GMT
2023-02-24T02:46:38.3847833Z 97: x-ms-is-current-version : true
2023-02-24T02:46:38.3848606Z 97: x-ms-lease-state : available
2023-02-24T02:46:38.3849347Z 97: x-ms-lease-status : unlocked
2023-02-24T02:46:38.3850165Z 97: x-ms-request-id : b41be76a-901e-006a-61fa-4724e0000000
2023-02-24T02:46:38.3850989Z 97: x-ms-server-encrypted : true
2023-02-24T02:46:38.3851943Z 97: x-ms-version : 2021-12-02
2023-02-24T02:46:38.3852763Z 97: x-ms-version-id : 2023-02-24T02:46:06.3829040Z
2023-02-24T02:46:38.3853713Z 97: [2023-02-24T02:46:06.3856104Z] INFO  : HTTP status code 200 won't be retried.
2023-02-24T02:46:38.3854661Z 97: [2023-02-24T02:46:06.4171639Z] DEBUG : Moving connection to pool...
2023-02-24T02:46:38.3855656Z 97: [2023-02-24T02:46:06.4173003Z] DEBUG : Clean thread running. Won't start a new one.
2023-02-24T02:46:38.3856624Z 97: [2023-02-24T02:46:06.4261225Z] DEBUG : Moving connection to pool...
2023-02-24T02:46:38.3857610Z 97: [2023-02-24T02:46:06.4262436Z] DEBUG : Clean thread running. Won't start a new one.
2023-02-24T02:46:38.3858577Z 97: unknown file: error: C++ exception with description "" thrown in the test body.
2023-02-24T02:46:38.3859751Z 97: [2023-02-24T02:46:06.4343032Z] INFO  : HTTP Request : DELETE https://***.blob.core.windows.net/blockblobclienttestconcurrentupload?restype=container
2023-02-24T02:46:38.3860758Z 97: authorization : REDACTED
2023-02-24T02:46:38.3861752Z 97: user-agent : azsdk-cpp-storage-blobs/12.7.0-beta.2 (Windows Server 2019 Datacenter 6.3 17763 17763.1.x86fre.rs5_release.180914-1434)
2023-02-24T02:46:38.3869680Z 97: x-ms-client-request-id : 3d82ae3a-66ac-49a9-482d-83d97731d5b2
2023-02-24T02:46:38.3870628Z 97: x-ms-date : Fri, 24 Feb 2023 02:46:06 GMT
2023-02-24T02:46:38.3871422Z 97: x-ms-version : 2021-12-02
2023-02-24T02:46:38.3872346Z 97: [2023-02-24T02:46:06.4344367Z] DEBUG : [CURL Transport Adapter]: Creating a new session.
2023-02-24T02:46:38.3874255Z 97: [2023-02-24T02:46:06.4345491Z] DEBUG : [CURL Transport Adapter]: Re-using connection from the pool.
2023-02-24T02:46:38.3875334Z 97: [2023-02-24T02:46:06.4346949Z] DEBUG : [CURL Transport Adapter]: No Host in request headers. Adding it
2023-02-24T02:46:38.3876403Z 97: [2023-02-24T02:46:06.4348309Z] DEBUG : [CURL Transport Adapter]: Send request without payload
2023-02-24T02:46:38.3877416Z 97: [2023-02-24T02:46:06.4351686Z] DEBUG : [CURL Transport Adapter]: Parse server response
2023-02-24T02:46:38.3878541Z 97: [2023-02-24T02:46:06.4428328Z] DEBUG : [CURL Transport Adapter]: Request completed. Moving response out of session and session to response.
2023-02-24T02:46:38.3879641Z 97: [2023-02-24T02:46:06.4429730Z] DEBUG : Moving connection to pool...
2023-02-24T02:46:38.3880615Z 97: [2023-02-24T02:46:06.4430812Z] DEBUG : Clean thread running. Won't start a new one.
2023-02-24T02:46:38.3881614Z 97: [2023-02-24T02:46:06.4433291Z] INFO  : HTTP Response (8ms) : 202 Accepted
2023-02-24T02:46:38.3882451Z 97: content-length : 0
2023-02-24T02:46:38.3883217Z 97: date : Fri, 24 Feb 2023 02:46:05 GMT
2023-02-24T02:46:38.3884080Z 97: server : Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
2023-02-24T02:46:38.3884969Z 97: x-ms-client-request-id : 3d82ae3a-66ac-49a9-482d-83d97731d5b2
2023-02-24T02:46:38.3885874Z 97: x-ms-request-id : e98597f2-301e-002e-1afa-47aedf000000
2023-02-24T02:46:38.3886683Z 97: x-ms-version : 2021-12-02
2023-02-24T02:46:38.3887548Z 97: [2023-02-24T02:46:06.4434574Z] INFO  : HTTP status code 202 won't be retried.
2023-02-24T02:46:38.3888517Z 97: [  FAILED  ] BlockBlobClientTest.ConcurrentUpload_LIVEONLY_ (26485 ms)
2023-02-24T02:46:38.3889420Z 97: [----------] 1 test from BlockBlobClientTest (26485 ms total)
2023-02-24T02:46:38.3890215Z 97:
2023-02-24T02:46:38.3890942Z 97: [----------] Global test environment tear-down
2023-02-24T02:46:38.3891780Z 97: [==========] 1 test from 1 test suite ran. (26485 ms total)
2023-02-24T02:46:38.3892590Z 97: [  PASSED  ] 0 tests.
2023-02-24T02:46:38.3893318Z 97: [  FAILED  ] 1 test, listed below:
2023-02-24T02:46:38.3894170Z 97: [  FAILED  ] BlockBlobClientTest.ConcurrentUpload_LIVEONLY_
2023-02-24T02:46:38.3894930Z 97:
2023-02-24T02:46:38.3895593Z 97:  1 FAILED TEST
2023-02-24T02:46:38.3896564Z  86/243 Test  #97: azure-storage-blobs.BlockBlobClientTest.ConcurrentUpload_LIVEONLY_ .....................................***Failed   26.54 sec

cc @Jinming-Hu

Partial logs:
BlockBlobClientTest.ConcurrentUpload_LIVEONLY_ logs.txt

2023-02-24T02:46:38.3858577Z 97: unknown file: error: C++ exception with description "" thrown in the test body.

This issue has existed since this test case was added. It's really annoying. I'll find some way to fix it.


feat(peridot-cli/task-info): fetch and display task details

given a task ID, fetch its details and display them to a table or to
json with -o json. Table view also adds a calculated task duration and
can optionally include the submitter information as well as a link to
logs for the task.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#196  👈
#195
feat/build-peridot-cli-rpm

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @NeilHanlon and the rest of your teammates on  Graphite


HADOOP-18531. Fix assertion failure in ITestS3APrefetchingInputStream

Description of PR
Fix assertion failure in ITestS3APrefetchingInputStream
How was this patch tested?
Ran Changed Integration in us-west-2 region.
Results:
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running org.apache.hadoop.fs.s3a.ITestS3APrefetchingInputStream
[INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 60.2 s - in org.apache.hadoop.fs.s3a.ITestS3APrefetchingInputStream
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:19 min
[INFO] Finished at: 2022-11-18T20:04:38Z
[INFO] ------------------------------------------------------------------------

For code changes:

[X] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[X] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 48s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
41m 17s

trunk passed

+1 :green_heart:
compile
0m 50s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
0m 45s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 48s

trunk passed

+1 :green_heart:
mvnsite
0m 53s

trunk passed

+1 :green_heart:
javadoc
0m 36s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 35s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 21s

trunk passed

+1 :green_heart:
shadedclient
23m 28s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 38s

the patch passed

+1 :green_heart:
compile
0m 44s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
0m 45s

the patch passed

+1 :green_heart:
compile
0m 38s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 38s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 24s

the patch passed

+1 :green_heart:
mvnsite
0m 37s

the patch passed

+1 :green_heart:
javadoc
0m 21s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 31s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 17s

the patch passed

+1 :green_heart:
shadedclient
22m 59s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 54s

hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
0m 45s

The patch does not generate ASF License warnings.

104m 29s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5149/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5149

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 55f006e54f57 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / b5291401e70fe7a720cbd46eb46c6d12f25e07c9

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5149/1/testReport/

Max. process+thread count
556 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-aws U: hadoop-tools/hadoop-aws

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5149/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

LGTM.

Thanks @steveloughran for reviewing and merging.


[Swift/Optional] Fix the formatter to print the right value.

There's a peculiarity in the way lldb represents Int/UInt types
in Swift. They don't have summaries, but values. This historical
choice forces us to switch between GetSummary() and GetValue()
in the formatters. Maybe we should revisit this choice because it
caused several issues over the last couple of years.
rdar://problem/37835998

@swift-ci test

@jimingham can you give a thorough look? Thanks!

@jimingham I originally thought about that. Having value providing summaries also providing a summary seems a lot of work [basically, as much work as treating integers for what they really are in swift], and some amount of duplication in the logic. I'd rather go for the original plan we discussed.
That said, I wouldn't be opposed if somebody else decides to pick up the slack and implement the solution you suggest, I'm just advocating in favor of what I would implement [will?] when I have the time :)

Can one of you tell me what GetValueAsCString() actually does? What will it return for things that are not Swift integers?

For most swift struct values GetValueAsCString returns an empty string.  For classes it may return the pointer value for the class, I don't remember.  For swift Int's - because they have a "value providing summary" - GetValueAsCString will return the integer value as a string.

Can one of you tell me what GetValueAsCString() actually does? What will it return for things that are not Swift integers?

nullptr, for basically everything that's not a swift integer [and maybe float, but I haven't checked in a while]

For most swift struct values GetValueAsCString returns an empty string. For classes it may return the pointer value for the class, I don't remember. For swift Int's - because they have a "value providing summary" - GetValueAsCString will return the integer value as a string.

A few things to check then:

The patch check for a null pointer, is that what you mean by empty string?
Does this mean an optional of a class will be printed differently now?

Basically I'd like to be sure this causes no functional change except for Integers.

I checked earlier today and I'm fairly confident the return value in case 1) is a nullptr and not a string.
I also have reasons to believe that this doesn't change the optional of a class, but I have to double-check.

For structs, GetValue is null.
For classes, GetValue returns the pointer value.

So I think Fred is right, this would cause us to print the pointer value for a class that had no summary whereas before we would have printed nothing.

The test that I modified has coverage for structs and enums. lit/SwiftREPL/Optional.test
I think it's a fair point to test also other aggregates to make sure this doesn't break anything, so I'm going to add coverage for them before merging [actually, I'll check if we have it already and add in case we don't]

Note, however, since the Optional is set to print children, then we still print the address of a class.  Here's what you get for frame var today:
(tryme.Bar?) myBar = 0x0000000100303950 {
b = 10
}
But in this case I'm pretty sure the pointer value and the rest are the child printing.
Class and struct optional printing is a little inconsistent anyway.  If I have:
struct Foo {
  let a = 10
}

class Bar {
  let b = 10
}

func doIt () {
 let myFoo : Foo? = Foo()
 let myRealFoo = myFoo!
 let myBar : Bar? = Bar()
 let myRealBar = myBar!
print(myFoo!, myBar!)
}

doIt()

Then in lldb I see:
(lldb) frame var
(tryme.Foo?) myFoo = some {
  a = 10
}
(tryme.Foo) myRealFoo = {
  a = 10
}
(tryme.Bar?) myBar = 0x0000000100303950 {
  b = 10
}
(tryme.Bar) myRealBar = 0x0000000100303950 {
  b = 10
}

Note that the filled optional of a struct says "some" but the filled optional of a class doesn't.

I think this is something interesting to clean up regardless. Both structs (and classes, and enums, and ${whatever}) should print some. I personally never noticed this inconsistency, but I read the code and I realized it wouldn't be that hard to fix. It's unlikely it'll get to 5.1, though.

Added a test for class optionals.

@swift-ci test and merge


Ability to Reuse Fields from Steps in Others

As a user, I would like the ability to reuse fields from one Step in another, in order to be able to make more useful integrations.
ie new product listing -> create a banner with it or social media post
Example:
User creates a product on Shopify. News of product creation is automatically shared on Twitter and a Telegram channel with the message "Hey there, my design is now on a new product. Visit my {shop_name} to get this cool {product_name} and check out more {product_category}! {shop_link}". You can make the message even more appealing by adding a Bannerbear node that automatically creates template images for your new product announcements.

@igarashitm this is part of https://github.com/KaotoIO/kaoto-ui/issues/253 right?

Yep at least it needs Data Mapper capability, or it could be beyond that? It sounds like a complete integration story rather than a single feature.


KNOX-2664 - Let end-users revoke their own tokens

What changes were proposed in this pull request?
Users can revoke tokens created for them even they are not listed in knox.token.renewer.whitelist
How was this patch tested?
Added a new JUnit test case and ran manual test steps:

installed the new version of Knox
logged into the Knox Home page as guest (this user is not added into knox.token.renewer.whitelist in to homepage topology)
generated a token on the token generation page
revoked the previously generated token on the token management page successfully

Cc. @zeroflag


Capitalized Swiftly in README

I personally don't have strong opinions about these kinds of things as long as the text is understandable, but Swiftly as a name should be capitalized as far as I know.

That's probably a good idea 👍

So I realize this is a bit of a personal preference thing, but the all lowercase was actually done on purpose, see my comment here for a bit of my reasoning. Given that you're not the first person to bring this up, I wonder if it would be better to refer to it either as swiftly then (like swift-format: https://github.com/apple/swift-format, notably not like SwiftFormat though), since I certainly don't want to give the impression the README was written lazily or anything.

Hm, since on purpose then maybe a small note somewhere about it in the readme to point people at :-)

I like "Swiftly" more since that's more prestigious 😅, but I see where you're coming from.
I think we can use backticks (e.g. swiftly) like swift-format does, and that should be enough proof for readers that this is intentional.


Feature request: setting translation format

Hello,
right now when if I have in my app some code like
<%= t :test %>

and there is no translation available for :test I get something like this in my html:
Test

would it be possible to add a configuration parameter so that I can make something like
 <%= t :test, :format => 'html' %>

and even if the translation is present I would get in my html something like this:
Test

This would be very useful for a plugin I am developing ( https://github.com/gnagno/lost_i18n_translation ) that will allow to have on the view a link to allow developers to add translations directly from the web interface. This way every string will be in his context and the work of translators would be easier.
My idea is to use jquery to activate a popup or a baloon tip on each translated or not translated string in the application ( this is why I am requesting to add this modification) where translators can add the text for the current locale.
thank you in advance
Ignazio

Closing as this is an old feature request and it does not have an associated PR.


Hover result should wrap signatures

The hover result message does not perform line wrapping for signatures, and some clients (such as emacs-lsp) do not do wrapping themselves.
So for
2018-06-09 14:24:48.615856571 [ThreadId 5] - <--2--{"result":{"range":{"start":{"line":25,"character":8},"end":{"line":25,"character":19}},"contents":
[{"value":"sendRequest :: Proxy (RequestMessage ClientMethod DocumentSymbolParams (List SymbolInformation)) -> ClientMethod -> DocumentSymbolParams -> Session LspId"
 ,"language":"haskell"
 }
,"`sendRequest`\n\nhaskell-lsp-test Language.Haskell.LSP.Test"]},"jsonrpc":"2.0","id":209}

only the first part of the sendRequest signature is shown.

And it may well be an issue in the emacs client.


Azure Search: Adding Service Statistics API

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] The spec follows the guidelines described in the Swagger checklist document.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Thanks! maxIndexerRunTime should indeed be nullable :)

@sergey-shandar Are you taking over the review from @johanste? If so, can you please review as soon as possible, as this is blocking our next release? This release includes a fix for a bug that is affecting our customers, so time is of the essence. Thanks!