test-to-harness: use new API endpoint to extract test code

This makes it possible to extract a subset of test, for example when a test file is too long.

/gcbrun exp -n dk-ft-100 -m vertex_ai_gemini-1-5 -b minor-for-ci -i


Add NuGet support

This pull request adds a NuGet manifest (.nuspec file) to the repository. It allows you to easily create a NuGet package and ship the project through NuGet.
You can do this automatically upon commit using MyGet.org build services (free for OSS! contact us at info@myget.org). If you want I can set this up for you, just reply to this pull request for further details.
Main idea: continuously package the UniformJS sources in a NuGet package and have it on MyGet.org on your own feed so people can test it. With a click of a button you can then push the package from MyGet to NuGet (upstream package source) and release it to the masses. This very simple workflow is also explained on our blog.
FYI: I currently already have a package jQuery.Uniform on NuGet, I'd happily transfer ownership to you.

We already have enough package managers in JS world, adding another (which we won't be able to maintain in long run) and cluttering codebase is something we should avoid. Especially considering this very package might need a revamp in light of the latest developments in front-end arena, I don't think it's a good idea to bother with DevOps related issues at this point. Closing this one for the moment.


typo on documentation

http://mbostock.github.com/d3/tutorial/bar-1.html
The first css example  .chart div should be div.chart
There's any way to make a patch? I would love to help!

Yes, you can send pull requests to the gh-pages branch. Until next time, I've fixed the typo. Thanks for the report!

Dude! I was wrong!  LOLOLOL
You were talking about the div inside
Sorry about that, man! /o
By the way, I am loving d3.js ,<3 <3 <3

I got trolled!


Updated Teachers Digital Platform URL for release

The current release of the Teachers Digital Platform needs the base url to be:
https://www.consumerfinance.gov/practitioner-resources/youth-financial-education/curriculum-review/
[Short description explaining the high-level reason for the pull request]
Additions

None

Removals

None

Changes

Changed 'tdp' to 'practitioner-resources/youth-financial-education/curriculum-review/' in the urls.py

Testing

Verify the new url redirects to the current tdp develop-apps/teachers-digital-platform app

Checklist

[x] PR has an informative and human-readable title
[x] Changes are limited to a single goal (no scope creep)
[x] Code can be automatically merged (no conflicts)
[x] Code follows the standards laid out in the development playbook
[x] Passes all existing automated tests
[x] Any change in functionality is tested
[x] New functions are documented (with a description, list of inputs, and expected output)
[x] Placeholder code is flagged / future todos are captured in comments
[x] Visually tested in supported browsers and devices (see checklist below :point_down:)
[x] Project documentation has been updated
[x] Reviewers requested with the Reviewers tool :arrow_right:

Testing checklist
Browsers

[ ] Chrome
[ ] Firefox
[ ] Safari
[ ] Internet Explorer 8, 9, 10, and 11
[ ] Edge
[ ] iOS Safari
[ ] Chrome for Android

Accessibility

[ ] Keyboard friendly
[ ] Screen reader friendly

Other

[ ] Is useable without CSS
[ ] Is useable without JS
[ ] Flexible from small to large screens
[ ] No linting errors or warnings
[ ] JavaScript tests are passing

@atuggle The Travis failure is for the line length being too long now. Can you either break that onto two lines, or add   # noqa: E501 at the end of the line? (I am not sure if we have a preference; both are done in this file.)

@atuggle Can you update the requirements/optional-public.txt file to bump the version of the TDP app to 0.5.11?
That release isn’t ready yet, but it will be shortly after I merge in your work.

@atuggle The 0.5.11 release is now ready.

@Scotchester I would like to move forward with this for now, because in another PR request I will have additional feature flags for them. Though I will keep that in mind if it makes sense going forward


Add support for a create_many_and_return method

https://www.prisma.io/docs/orm/reference/prisma-client-reference#createmanyandreturn

+1 to this feature! A create_many_and_return() method would streamline batch operations by avoiding the need for separate fetches, saving time and reducing complexity


Not dismiss Kakao popup after linking

Hi,
First of all, thank for your module. I have some issues:

This response is logged before the popup appears, and I don't know the event when the link is success.

const response = await RNKakaoLink.link(options);
console.log(response)

After linking, the popup is not dismissed.
https://imgur.com/dY8Hd8O

Well,
I made this Example Using 'async' function.
but Kakao linking doesn't work asynchronous.
So the response doesn't have any infomation about result of kakao linking.
Don't care about the response of linking. 😥
And you can dismiss with touching 'Cancel' on the top-left.
It's common Usage because IPhone doesn't have Back button.

This is strange behavior 😥
Like Facebook share, after sharing the popup is dismissed automatically.
I don't know the reason is from the native SDK or not.
Anyway, thank you so much 👍

Hi,
Sorry. Could you mind looking at this issue:
When I compile Android:
A problem occurred evaluating project ':react-native-kakao-links'.
> Could not get unknown property 'KAKAO_SDK_GROUP' for project ':react-native-kakao-links' of type org.gradle.api.Project.

I don't know about Android, but looking into your build.gradle:
implementation group: project.KAKAO_SDK_GROUP, name: 'kakaolink', version: project.KAKAO_SDK_VERSION

Sorry i'm late.
First, you have to install Kakao SDK following Official guide.
check 'KAKAO_SDK_GROUP' property in your /android gradle settings.


DNSSEC validation

How can I import the root keys and what do I have to do to validate DNS results?

sigok.verteiltesysteme.net should be valid
sigfail.verteiltesysteme.net should be bogus

A piece of example code - or even better a client test would be great.

You need to write a full blown dnssec resolver, which is by no means easy. See miekg/unbound for a Go wrapper for unbound.
I'm no aware of a Go only DNSSEC resolver.

Ok, thanks. I will try your unbound wrapper.

I tried your libunbound wrapper. Unfortunately libunbound creates a thread for every lookup. Your Go library works well with 4 threads and 4000 go routines. It resolves around 240k domains per minute.
https://github.com/corny/dnsresolver/tree/master
libunbound does not scale well because having more than 50 threads does not result in more lookups per second on my machine. It makes around 6500 domains per minute with DNSSEC.
https://github.com/corny/dnsresolver/tree/libunbound
I reopen this issue because a validating recursive resolver in Go would be nice to heave.

True...
except writing such a beast is a multi-year effort.


PSM should set Content-Type: application/javascript on optimized JS

On rewritten JS resources PSM sets
Content-Type: application/x-javascript;
It should set application/javascript according to http://stackoverflow.com/questions/9664282/difference-between-application-x-javascript-and-text-javascript-content-types .

My memory from the last time this came up was that not all browsers accepted application/javascript and we needed to send the x- for compatibility. But I'm not remembering which, and they're probably four more years out of date now than when we last looked at it.

Looking at the source code, we preserve known Javascript mimetypes of
the input (and use application/javascript when the original mimetype
is weird); it seems like
application/x-javascript is what nginx and Apache both appears to default to.
FWIW, the table in content_type.cc has a warning that text/javascript
has problems with some firewall gziping.
On Mon, Jan 26, 2015 at 9:17 AM, Jeff Kaufman<EMAIL_ADDRESS>wrote:

My memory from the last time this came up was that not all browsers accepted
application/javascript and we needed to send the x- for compatibility. But
I'm not remembering which, and they're probably four more years out of date
now than when we last looked at it.
—
Reply to this email directly or view it on GitHub.


Return optionals as part of a Cucumber Expression match

🤔 What's the problem you're trying to solve?
I want to provide syntax highlighting (LSP semantic tokens) for the parts of a Gherkin step that is optional in the corresponding Cucumber Expression.
✨ What's your proposed solution?
Use named capture groups for optionals, as explained in https://github.com/cucumber/language-service/issues/57
The return type of match would change from Argument[] | null to Match | null:
export type Match = {
  arguments: readonly Argument[]
  optionals: readonly Optional[]
}

export type Optional = {
  group: Group
}

⛏ Have you considered any alternatives or workarounds?
If we want to support this, I can't think of any other option.

Currently you can not assign special meaning to groups because every possible regex generated by a Cucumber expression is also a regular valid regular regex that may be provided by a user.
For example the regex:
A(?<Special-String> non-optional) pattern

Would be capturing when used with Cucumber, but non capturing in the Language Server. And while it is unlikely a user may have guessed Special-String, it is an indication that this abstraction is leaking.
Now I'm not opposed to adding named group support to the tree regex. These names could be used when generating step definitions based of regular regexes for example.
However the proposed Special-String should not be used in production code. So consider generating a different regex patterns when transforming the AST to a Cucumber expression while using the langue server.
This may require some refactoring.

I wrote in https://github.com/cucumber/language-service/issues/57 that we could change TreeRegexp. After thinking about it a bit more, I think the correct place to do this is in rewriteOptional: https://github.com/cucumber/cucumber-expressions/blob/2841a19bc90d6c02b571a3670f9b89583bda5f79/javascript/src/CucumberExpression.ts#L72
We could pass a makeOptionalGroup: (regex: string) => string constructor argument to CucumberExpression (defaulting to this:
(regex, count) => `(?:${regex})?`

That way, the language server could pass its own:
(regex, count) => `(?<optional-${count}>${regex})`

That interface is very language server specific.
For example:

count is not a concept that occurs in cucumber expressions. It exists only for the language server.
This only and specifically replaces optionals.

Ideally we define the Cucumber expression API in its own domain terms.
So I think some refactoring is in order.

It does come to mind that currently we also assume that all capture groups are parameters. If you write optionals as capturing then match won't work anymore.
Maybe you can extract the code that rewrites the AST, add support for named groups to tree-regex and then use those in a class that is not CucumberExpression.


Do id_tokens contain email or not?

The limitation document says id_tokens from the v2 endpoint do not contain the email claim, even if they request it.
However, it's explicitly listed as a returned claim in this document. Which document is right?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c18ae119-a9b9-44eb-ead0-f8dee59718b2
Version Independent ID: 92634a9a-ac00-6aa4-1c3b-67f8940a9ad5
Content: Azure Active Directory v2.0 tokens reference
Content Source: articles/active-directory/develop/active-directory-v2-tokens.md
Service: active-directory
GitHub Login: @CelesteDG
Microsoft Alias: celested

@colemickens Thanks for your feedback! We will investigate and update as appropriate.

@colemickens  I have assigned this issue to content author to investigate and update the document as appropriate.

Hello @colemickens - Current behavior today for id_tokens is to release email only if an optional claim is configured and scope=email was specified in the request. For access_tokens, behavior is to release email only if an optional claim is configured and scope=email was specified in the request. Please let us know if this info helps with your question.

I'm not sure. I'm still confused.
I still don't understand the documentation situation. One page clearly says ID tokens that are issued by the v2.0 endpoint do not contain an email claim for the user, even if you acquire permission from the user to view their email..
The docs for the token says: The primary email address associated with the user account, if one exists. Its value is mutable and might change over time. The email scope is required in order to receive this claim.
Is this true:

OIDC id_tokens usually contain email even w/o requesting it in a scope
AADv2 doesn't do this
but, AADv2 does return it in the id_token and access_token if the email scope was specifically requested

If so, I feel like there's a much clearer, easier way to say this and document it than what exists right now. The limitation document reads as a conclusive statement that the email claim does not propagate, or maybe I just read it wrong and it's stuck with me. Either way an extra sentence of clarification would go along way. Other resources on the Internet point to that as well...

@colemickens - Can you please add links to the pages that you're referencing? There is some ongoing work that will update the email claim behavior so I'm waiting on guidance from our feature team before making further doc changes. I've only recently taken ownership of the docs and I appreciate your feedback on where it can improve.

Of course, my apologies, I thought they were in the initial description!
Here's the AAD V2 Limitations document I'm referring to: https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-v2-limitations
And then the AADv2 Token Reference: https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-v2-tokens

Thank you, @colemickens - This is super helpful. I'm following up on this now and will update this thread once I've got more info or have a PR ready to address your question.

@colemickens - I updated the "Restrictions on protocols" section to call out that:

Currently, the email claim is returned only if an optional claim is configured and scope is scope=email was specified in the request. However, this behavior will change as the v2.0 endpoint is updated to further comply with the Open ID Connect and OAuth2.0 standards.

Fix waiting to go to master and go live. #please-close

Great to hear. Thank you for the followup and resolution!

@colemickens Thank you very much for your feedback and your help in ensuring we've got accurate and useful docs. Please don't hesitate to provide us with further feedback.


missing script: build

If I try to run the minified script I get the error message:
npm ERR! missing script: build
The scripts section of the package.json looks like this:
"scripts": {
    "env": "env",
    "test": "gulp test",
    "watch": "gulp watch",
    "minified": "gulp release && npm run build && NODE_ENV=production browserify -t [ reactify --es6 ] --standalone rd3 ./build/cjs/index.js | uglifyjs -c > dist/public/js/react-d3.min.js"
  },

So there is no build script and there never was AFAICS (I was looking at the history of package.json and apparently https://github.com/esbullington/react-d3/commit/f9f7244458aa0452f0bf0b1dab3ba8ad810c75bf#diff-b9cfc7f2cdf78a7f4b91a753d10865a2 introduced the minified script but there was no build script).
Removing the npm run build &&  and running npm run minified will work and it seems that everything necessary is created but I don't know if I'm missing something.

Removing the npm run build && and running npm run minified will work and it seems that everything necessary is created but I don't know if I'm missing something.

You are correct. Mind to send us a pr ?

I don't know if just removing the npm run build is alright, but I'll commit the version without it.
@esbullington should know if there's missing something from the npm run build script.


Multiple views feature

Hi Team,
Possible to configure multiple viewer in Storybook? If yes, is there any reference?
Example, in single template have "Statement of Results" and "Explanatory Notes".

Hey,
what do you mean by single template have "Statement of Results" and "Explanatory Notes".?
are you just trying to render multiple data in a single template?
if so, you can always customise the template to your needs.

possible to configure storybook have multiple views as below?

what do you intend to achieve if you configure storybook to display a tabbed view?
storybook is only meant for devs to visualise the template and how it looks, I dont see a need for a dev to want a tabbed view.
if you want this kind of behavior in your project, then you'll have to code it up, you can reference opencerts website on how we are currently doing tabbed views.


Refactor AtomMapper to use OpenFF toolkit only

#884 was a valiant attempt to refactor AtomMapper to make the OpenEye toolkit, but unfortunately created a great deal of additional complexity without providing much advantage.
Instead, we should tackle this using a simpler approach, where we convert everything to use openff.toolkit.topology.Molecule and, should we need to use a toolkit operation (OpenEye or RDKit), simply retrieve the appropriate toolkit representation using molecule.to_openeye() or molecule.to_rdkit() in a just-in-time manner.
This may require we add a few things to the OpenFF toolkit to ensure we don't lose information, so this may take a little time and coordination.
We can also likely replace some of the MCSS functionality with NetworkX or equivalent (e.g. igraph) as needed without too much complexity.

To avoid needing to have this PR take an extended amount of time, we could first subclass Molecule with the additional methods we needed within perses and then work to migrate these methods into the OpenFF toolkit. That would allow for a quick refactor to use Molecule for everything, followed by a timely migration of new features into the OpenFF toolkit in a robust manner.
cc: @richardjgowers


⚠ Bofrost.fr has degraded performance

In 6c63779, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1105 ms

Resolved: Bofrost.fr performance has improved in 2c87061 after 9 minutes.


use schema package to encode and decode query paramters

currently, http query parameters are encoded and decoded using local converters, which may be error prone if some type changes happen. luckily there is a package that does this already schema.
i think it would be better to use it and not bother with the conversion again.

It's definitely a step in the right direction.

rebased the pr branch on latest development

track updates on the pr discussion


'Start Chapter-1' button should take to current challenge

Describe the enhancement
"The "Start Chapter 1" button on the chapter overview page should always take you to the current challenge you are working on instead of restarting Chapter 1." - Christoph

One possible solution I researched is to get the user progress information and use the data to direct the user to the latest challenge they are on in a particular chapter.
This approach requires using the user's data stored in local storage. But with #158, we aim to change data storage from local to the backend. It's best to keep this issue on hold until we have transformed the storage logic.

Here's a design for this, the button simply reads "Continue".

Here's a design for this, the button simply reads "Continue".

Thanks for tagging that, @GBKS! However, the functionality change of directing users to the current challenges requires reading their progress, which is dependent on backend implementation.
IMO it's best to implement design and functionality change simultaneously in this case!


Logistic Regression

Added a code file and a .csv file
for Logistic Regression on the Great TItanic

Do give a Star to this repo.. happy hacking.


Build readme as part of docs

Look into inserting the readme into the crate docs, so that it shows up at docs.rs/just

Inserted some of the readme into the docs.


Address issues reported by CTAO DPPS sonarqube

PR #957 integrated simtools into CTAO DPPS sonarqube. Issues reported here should be addressed (or discussed, if it is something we are fine with).

PR #969 reduces nicely the number of issues - see https://sonar-cta-dpps.zeuthen.desy.de/dashboard?id=gammasim_simtools_AY_ssha9WiFxsX-2oy_w
I've noticed that we do not run the unit tests after merging to main and therefore the sonarqu statistics on the project is not updated. Should we add running unit tests after merging?
Coverage dropped below the required 80% and we should check if this is mostly due to the missing unit tests in applications (see issue #972). Maybe we really should look into this add test for some of the functions in the applications.

Zero issues - this can be closed. Nice work, @tobiaskleiner


Uncaught Error: connect ECONNREFUSED

From @JostCrow on January 23, 2015 9:46
[Enter steps to reproduce below:]

killed ungit via ctrl+p.
pressed ctrl+p again afterwards.
Nothing happened so I pressed it again.

Atom Version: 0.175.0
System: linux 3.13.0-44-generic
Thrown From: Atom Core
Stack Trace
Uncaught Error: connect ECONNREFUSED
At events.js:85

Error: connect ECONNREFUSED
  at exports._errnoException (util.js:746:11)
  at Object.afterConnect [as oncomplete] (net.js:990:19)

Commands
     -0:24.2 window:run-package-specs (atom-text-editor.editor)
  3x -0:21.2 project-manager:toggle (atom-text-editor.editor)
     -0:19.5 core:move-up (atom-text-editor.editor.mini)
     -0:19.3 core:confirm (atom-text-editor.editor.mini)
     -0:16.1 command-palette:toggle (atom-workspace.workspace.scrollbars-visible-always.theme-monokai.theme-atom-dark-ui)
     -0:14.3 core:confirm (atom-text-editor.editor.mini)
     -0:14.3 ungit:toggle (atom-workspace.workspace.scrollbars-visible-always.theme-monokai.theme-atom-dark-ui)
     -0:01.9 command-palette:toggle (atom-text-editor.editor.is-focused)
     -0:00.0 core:confirm (atom-text-editor.editor.mini)
     -0:00.0 ungit:kill (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "disabledPackages": [
      "tabs",
      "tree-view",
      "linter-python-pep8",
      "toolbar",
      "toolbar-main",
      "pane-layout-plus",
      "indent-guide-improved"
    ],
    "themes": [
      "atom-dark-ui",
      "monokai"
    ]
  },
  "editor": {
    "fontSize": 12,
    "showIndentGuide": true,
    "tabLength": 4,
    "scrollSensitivity": 80,
    "scrollPastEnd": true,
    "invisibles": {}
  }
}

Installed Packages
# User
atom-python-debugger, v0.1.1
atom-ungit, v0.4.0
autoclose-html, v0.13.0
autocomplete-plus, v1.1.0
autocomplete-plus-async, v0.22.0
highlight-selected, v0.7.0
language-django, v0.1.1
linter, v0.10.1
linter-pep8, v0.1.0
minimap, v3.5.6
minimap-color-highlight, v3.1.0
minimap-find-and-replace, v3.1.0
minimap-git-diff, v3.1.0
minimap-highlight-selected, v3.1.0
minimap-selection, v3.1.1
monokai, v0.11.0
project-manager, v1.15.0
python-isort, v0.0.5
set-syntax, v0.1.0
sublime-tabs, v0.4.8
tab-history, v0.4.0

# Dev
No dev packages

Copied from original issue: atom/atom#5230

From @mnquintana on January 23, 2015 12:37
I can't reproduce this in OS X 10.10.1, Atom 0.175.0. Can you try seeing if you can reproduce this with all of your installed packages disabled except atom-ungit?

@benogle Thanks and will be looking at it.
@JostCrow First thing I would suspect is that wether or not ungit is able to use provided port, by default ungit uses 8448.  Best thing to do is install ungit within npm and see if you can run that independently from atom-ungit.
Admittedly I do not own any windows machine so atom-ungit's window durability is spotty at best but I will see what I can do help you with this problem.

@codingtwinky I used ungit before outside of atom. I can still run ungit and use it independently.

I'm not able to reproduce this issue and I'm not sure how to approach this.


[Chrome] Storage empty after some days without using the extension

The input for the name was prompted as the storage was emptied during the weekend. Last use was on friday and on monday it was empty.

We couldn't reproduce the bug, so we close it


[Bug]: Missing focus ring

What happened?
Currently, the user is unable to identify what they are focused on within the delete modal as no focus ring is provided on the "cancel" or "delete" buttons.
Steps to Reproduce

Create a chat
Begin focus in nav bar
Click tab and navigate to the trashcan (delete) icon
Select Enter
Observe modal and look for focus ring, where is it?
Tab around the modal and note that your focused is trapped (yay) but you are unable to see when your focus is on the cancel/delete button... only the exit icon in the top right corner

What browsers are you seeing the problem on?
No response
Relevant log output
No response
Screenshots

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Thanks! I plan on resolving this soon with a quick fix, but a detailed accessibility review is also planned

awesome! Please let me know if I can help support this! 🥳 @danny-avila

Of course, PRs always welcome. Here are my notes from looking into it this morning.
We use a lot of primitives found in client/src/components/ui so changes here can affect styling app-wide. In some, very few if not null cases, after my PR, a component may still be passing className that removes focus rings (but I can't find any that do).
In some other cases, tabIndex is set to -1, mainly dropdown/select components, preventing use of tabbing--these could use some investigation.
Lastly, I did notice a minor issue where continuing to tab within the conversation list keeps scrolling the list. There should be some way of tabbing to the <HeaderOptions /> component.
I am aware that when many conversations are fetched, from infinite scrolling, the application slows down from memory usage increase. This can be mitigated (with virtualization) and/or by trimming the data used to populate the list, which can then be fetched in full when clicked. The solution for this is pretty involved but will need to assess the priority for this.


Show emulator gutters/margins, tweak layout

This started out with an effort to provide contrast between the gutters/margins and the LED. Without the gutters being visible, it was very difficult to that the right LEDs were being lit up. I found, though, the math to locate LEDs, gutters, etc to be a bit challenging. In the end, I rewrote some portions in order to consolidate the mathematics, simplifying (in my opinion) things a little bit. I should note that the math became easier when I started expressing things in terms of the gutter width (ex: PixelPitch = 2*Gutter).

Gutters and margins are now drawn in a contrasting color (gray), so that it is easy to distinguish the LED pixels from the background.
The initial emulator window dimensions are calculated based on the initial pixel pitch.
LED matrix resizing is a bit more precise as the window is resized.

I've tested this code quite extensively on Linux and am quite happy with the results.

Nice addition!


HADOOP-18930. Make fs.s3a.create.performance a bucket-wide setting

Description of PR
HADOOP-18930. Make fs.s3a.create.performance a bucket-wide settings.
Adds the switch;
How was this patch tested?
doesn't change the tests which will fail when enabled, or provide and explicit way to set in a maven profile.
likely outcome

all tests about overwrite fail
cost of creation tests fail.

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?

creation tests fail. propose: parameterize
[ERROR] Tests run: 16, Failures: 3, Errors: 0, Skipped: 4, Time elapsed: 25.039 s <<< FAILURE! - in org.apache.hadoop.fs.contract.s3a.ITestS3AContractCreate
[ERROR] testOverwriteNonEmptyDirectory(org.apache.hadoop.fs.contract.s3a.ITestS3AContractCreate)  Time elapsed: 5.549 s  <<< FAILURE!
java.lang.AssertionError: write of file over dir succeeded
        at org.junit.Assert.fail(Assert.java:89)
        at org.apache.hadoop.fs.contract.AbstractContractCreateTest.testOverwriteNonEmptyDirectory(AbstractContractCreateTest.java:194)
        at org.apache.hadoop.fs.contract.AbstractContractCreateTest.testOverwriteNonEmptyDirectory(AbstractContractCreateTest.java:210)

[ERROR] testOverwriteEmptyDirectory(org.apache.hadoop.fs.contract.s3a.ITestS3AContractCreate)  Time elapsed: 1.51 s  <<< FAILURE!
java.lang.AssertionError: Should be a directory -but isn't: S3AFileStatus{path=s3a://stevel-london/fork-0001/test/testOverwriteEmptyDirectory; isDirectory=false; length=256; replication=1; blocksize=33554432; modification_time=1696965045000; access_time=0; owner=stevel; group=stevel; permission=rw-rw-rw-; isSymlink=false; hasAcl=false; isEncrypted=true; isErasureCoded=false} isEmptyDirectory=FALSE eTag="fba66d3273eac117107832558bc9a363" versionId=0u_U.3vOkC7.7F0kQHv9fHuNAIRxAo3f
        at org.junit.Assert.fail(Assert.java:89)
        at org.junit.Assert.assertTrue(Assert.java:42)
        at org.apache.hadoop.fs.contract.ContractTestUtils.assertIsDirectory(ContractTestUtils.java:585)
        at org.apache.hadoop.fs.contract.ContractTestUtils.assertIsDirectory(ContractTestUtils.java:577)
        at org.apache.hadoop.fs.contract.AbstractFSContractTestBase.assertIsDirectory(AbstractFSContractTestBase.java:352)
        at org.apache.hadoop.fs.contract.AbstractContractCreateTest.testOverwriteEmptyDirectory(AbstractContractCreateTest.java:145)
        at org.apache.hadoop.fs.contract.AbstractContractCreateTest.testOverwriteEmptyDirectory(AbstractContractCreateTest.java:161)

[ERROR] testCreateFileOverExistingFileNoOverwrite(org.apache.hadoop.fs.contract.s3a.ITestS3AContractCreate)  Time elapsed: 1.467 s  <<< FAILURE!
java.lang.AssertionError: writing without overwrite unexpectedly succeeded
        at org.junit.Assert.fail(Assert.java:89)
        at org.apache.hadoop.fs.contract.AbstractContractCreateTest.testCreateFileOverExistingFileNoOverwrite(AbstractContractCreateTest.java:92)
        at org.apache.hadoop.fs.contract.AbstractContractCreateTest.testCreateFileOverExistingFileNoOverwrite(AbstractContractCreateTest.java:106)
)

+ most of ITestCreateFileCost.

+ITestDirectoryMarkerListing

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 33s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
45m  2s

trunk passed

+1 :green_heart:
compile
0m 47s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
compile
0m 39s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
0m 36s

trunk passed

+1 :green_heart:
mvnsite
0m 46s

trunk passed

+1 :green_heart:
javadoc
0m 32s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
0m 37s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
1m 12s

trunk passed

+1 :green_heart:
shadedclient
34m 10s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 32s

the patch passed

+1 :green_heart:
compile
0m 36s

the patch passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javac
0m 36s

the patch passed

+1 :green_heart:
compile
0m 28s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
javac
0m 28s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 22s
/results-checkstyle-hadoop-tools_hadoop-aws.txt
hadoop-tools/hadoop-aws: The patch generated 1 new + 3 unchanged - 0 fixed = 4 total (was 3)

+1 :green_heart:
mvnsite
0m 32s

the patch passed

+1 :green_heart:
javadoc
0m 18s

the patch passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
0m 26s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
1m  6s

the patch passed

+1 :green_heart:
shadedclient
32m 53s

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 40s

The patch does not generate ASF License warnings.

130m  4s

Subsystem
Report/Notes

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

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

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

uname
Linux 1d8cc5622913 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 99f879abce39bf8cc5f75eedeb26fd9239b81069

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

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

Max. process+thread count
578 (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-6168/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.

testing: updated test against s3 london from ide and maven.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 38s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
46m 11s

trunk passed

+1 :green_heart:
compile
0m 43s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
0m 34s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
0m 33s

trunk passed

+1 :green_heart:
mvnsite
0m 42s

trunk passed

+1 :green_heart:
javadoc
0m 28s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 36s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
1m 12s

trunk passed

+1 :green_heart:
shadedclient
34m 42s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 31s

the patch passed

+1 :green_heart:
compile
0m 36s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
0m 36s

the patch passed

+1 :green_heart:
compile
0m 26s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
javac
0m 26s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 20s
/results-checkstyle-hadoop-tools_hadoop-aws.txt
hadoop-tools/hadoop-aws: The patch generated 1 new + 3 unchanged - 0 fixed = 4 total (was 3)

+1 :green_heart:
mvnsite
0m 31s

the patch passed

+1 :green_heart:
javadoc
0m 16s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 26s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
1m  6s

the patch passed

+1 :green_heart:
shadedclient
35m 48s

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

_ Other Tests _

-1 :x:
unit
2m 51s
/patch-unit-hadoop-tools_hadoop-aws.txt
hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
0m 37s

The patch does not generate ASF License warnings.

134m  6s

Reason
Tests

Failed junit tests
hadoop.fs.s3a.impl.TestErrorTranslation

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6168/2/artifact/out/Dockerfile

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

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

uname
Linux 387fc5cf7fb2 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / f234e28951e43e8bf6cdfbaae898e20b4611d4ce

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6168/2/testReport/

Max. process+thread count
555 (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-6168/2/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.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 37s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

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 2 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
44m 28s

trunk passed

+1 :green_heart:
compile
0m 46s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
0m 37s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
0m 34s

trunk passed

+1 :green_heart:
mvnsite
0m 44s

trunk passed

+1 :green_heart:
javadoc
0m 30s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 36s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
1m 12s

trunk passed

+1 :green_heart:
shadedclient
33m 37s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 31s

the patch passed

+1 :green_heart:
compile
0m 36s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
0m 36s

the patch passed

+1 :green_heart:
compile
0m 28s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
javac
0m 28s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 22s
/results-checkstyle-hadoop-tools_hadoop-aws.txt
hadoop-tools/hadoop-aws: The patch generated 4 new + 3 unchanged - 0 fixed = 7 total (was 3)

+1 :green_heart:
mvnsite
0m 34s

the patch passed

+1 :green_heart:
javadoc
0m 16s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 26s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
1m  7s

the patch passed

+1 :green_heart:
shadedclient
33m 28s

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

_ Other Tests _

-1 :x:
unit
3m  0s
/patch-unit-hadoop-tools_hadoop-aws.txt
hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
0m 40s

The patch does not generate ASF License warnings.

129m 30s

Reason
Tests

Failed junit tests
hadoop.fs.s3a.impl.TestErrorTranslation

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6168/3/artifact/out/Dockerfile

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

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

uname
Linux 1c98e744b912 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 18b4628eab1c6cccdc53b5c59448cd47908bddd5

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6168/3/testReport/

Max. process+thread count
699 (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-6168/3/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.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 37s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

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 2 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
45m 49s

trunk passed

+1 :green_heart:
compile
0m 45s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
0m 40s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
0m 36s

trunk passed

+1 :green_heart:
mvnsite
0m 46s

trunk passed

+1 :green_heart:
javadoc
0m 32s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 39s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
1m 13s

trunk passed

+1 :green_heart:
shadedclient
35m  5s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 29s

the patch passed

+1 :green_heart:
compile
0m 37s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
0m 37s

the patch passed

+1 :green_heart:
compile
0m 26s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
javac
0m 26s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 21s
/results-checkstyle-hadoop-tools_hadoop-aws.txt
hadoop-tools/hadoop-aws: The patch generated 3 new + 3 unchanged - 0 fixed = 6 total (was 3)

+1 :green_heart:
mvnsite
0m 34s

the patch passed

+1 :green_heart:
javadoc
0m 18s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 28s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
1m  7s

the patch passed

+1 :green_heart:
shadedclient
34m 50s

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

_ Other Tests _

-1 :x:
unit
2m 49s
/patch-unit-hadoop-tools_hadoop-aws.txt
hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
0m 37s

The patch does not generate ASF License warnings.

133m 34s

Reason
Tests

Failed junit tests
hadoop.fs.s3a.impl.TestErrorTranslation

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6168/4/artifact/out/Dockerfile

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

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

uname
Linux 2e8335d06225 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / fe03f94e4a35d2172be9380335a2e72aead8c047

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6168/4/testReport/

Max. process+thread count
699 (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-6168/4/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.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 36s

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 8 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
44m 20s

trunk passed

+1 :green_heart:
compile
0m 44s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
0m 37s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
0m 35s

trunk passed

+1 :green_heart:
mvnsite
0m 44s

trunk passed

+1 :green_heart:
javadoc
0m 30s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 36s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
1m 15s

trunk passed

+1 :green_heart:
shadedclient
33m 46s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 31s

the patch passed

+1 :green_heart:
compile
0m 36s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
0m 36s

the patch passed

+1 :green_heart:
compile
0m 28s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
javac
0m 28s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 22s
/results-checkstyle-hadoop-tools_hadoop-aws.txt
hadoop-tools/hadoop-aws: The patch generated 7 new + 4 unchanged - 0 fixed = 11 total (was 4)

+1 :green_heart:
mvnsite
0m 34s

the patch passed

+1 :green_heart:
javadoc
0m 18s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 28s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
1m  7s

the patch passed

+1 :green_heart:
shadedclient
34m 12s

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

_ Other Tests _

-1 :x:
unit
2m 56s
/patch-unit-hadoop-tools_hadoop-aws.txt
hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
0m 41s

The patch does not generate ASF License warnings.

130m 14s

Reason
Tests

Failed junit tests
hadoop.fs.s3a.impl.TestErrorTranslation

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6168/5/artifact/out/Dockerfile

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

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

uname
Linux 297a121467f6 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 43bed651e666b00d55f1d6c79f58f7c2dc843778

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6168/5/testReport/

Max. process+thread count
554 (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-6168/5/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.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 36s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+0 :ok:
markdownlint
0m  1s

markdownlint 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 10 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 45s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
32m 48s

trunk passed

+1 :green_heart:
compile
17m  5s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
15m 56s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
4m 22s

trunk passed

+1 :green_heart:
mvnsite
2m 51s

trunk passed

+1 :green_heart:
javadoc
2m  8s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 50s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
3m 54s

trunk passed

+1 :green_heart:
shadedclient
34m  1s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 33s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 28s

the patch passed

+1 :green_heart:
compile
15m 43s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
15m 43s

the patch passed

+1 :green_heart:
compile
15m 24s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
javac
15m 24s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
4m 21s

the patch passed

+1 :green_heart:
mvnsite
2m 46s

the patch passed

+1 :green_heart:
javadoc
2m  3s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 55s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
4m 21s

the patch passed

+1 :green_heart:
shadedclient
34m 49s

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

_ Other Tests _

+1 :green_heart:
unit
19m 11s

hadoop-common in the patch passed.

+1 :green_heart:
unit
3m  7s

hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
1m 13s

The patch does not generate ASF License warnings.

246m 23s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6168/6/artifact/out/Dockerfile

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

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

uname
Linux 55d05975eafc 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / f67058241478473369baa0057e5db91f0ba5cd09

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6168/6/testReport/

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

modules
C: hadoop-common-project/hadoop-common hadoop-tools/hadoop-aws U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6168/6/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.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 36s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+0 :ok:
markdownlint
0m  1s

markdownlint 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 10 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
16m 25s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
30m  3s

trunk passed

+1 :green_heart:
compile
18m  1s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
16m 33s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
4m 41s

trunk passed

+1 :green_heart:
mvnsite
2m 31s

trunk passed

+1 :green_heart:
javadoc
2m  2s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 56s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
4m  3s

trunk passed

+1 :green_heart:
shadedclient
33m 45s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 31s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 27s

the patch passed

+1 :green_heart:
compile
16m  3s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
16m  3s

the patch passed

+1 :green_heart:
compile
15m 52s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
javac
15m 52s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
4m 15s

the patch passed

+1 :green_heart:
mvnsite
2m 36s

the patch passed

+1 :green_heart:
javadoc
1m 47s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 44s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
4m 10s

the patch passed

+1 :green_heart:
shadedclient
35m 16s

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

_ Other Tests _

+1 :green_heart:
unit
19m 13s

hadoop-common in the patch passed.

+1 :green_heart:
unit
3m  0s

hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
1m  5s

The patch does not generate ASF License warnings.

245m  3s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch-windows-10/job/PR-6168/1/artifact/out/Dockerfile

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

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

uname
Linux aad2ad01bc2b 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / f67058241478473369baa0057e5db91f0ba5cd09

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

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

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

modules
C: hadoop-common-project/hadoop-common hadoop-tools/hadoop-aws U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch-windows-10/job/PR-6168/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.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 36s

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.

+0 :ok:
markdownlint
0m  0s

markdownlint 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 10 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
16m  4s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
35m 25s

trunk passed

+1 :green_heart:
compile
18m 13s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
17m  9s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
4m 23s

trunk passed

+1 :green_heart:
mvnsite
2m 34s

trunk passed

+1 :green_heart:
javadoc
1m 53s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 40s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
3m 49s

trunk passed

+1 :green_heart:
shadedclient
37m 54s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 33s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 25s

the patch passed

+1 :green_heart:
compile
15m 47s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
15m 47s

the patch passed

+1 :green_heart:
compile
16m  7s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
javac
16m  7s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
4m 19s

the patch passed

+1 :green_heart:
mvnsite
2m 46s

the patch passed

+1 :green_heart:
javadoc
2m  1s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 55s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
4m 16s

the patch passed

+1 :green_heart:
shadedclient
35m 14s

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

_ Other Tests _

+1 :green_heart:
unit
19m 12s

hadoop-common in the patch passed.

+1 :green_heart:
unit
3m  9s

hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
1m 12s

The patch does not generate ASF License warnings.

255m 57s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6168/7/artifact/out/Dockerfile

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

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

uname
Linux 1df3f3eea80b 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 7bdf9725b7f278a0c59df01cfb1bb314203f6378

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6168/7/testReport/

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

modules
C: hadoop-common-project/hadoop-common hadoop-tools/hadoop-aws U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6168/7/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.


Cannot build wolfi-dev/os datadog-agent on a chainguard workstation

On a workstation I currently cannot build datadog-agent with --runner=docker or --runner=bubblewrap.
Full logs of my failed attemt here here:

bubblewrap
docker

$ git log --oneline HEAD^..
87d8a659c (HEAD, upstream/main, upstream/HEAD) gitaly setup_cgroups (#24320)

$ git remote -v | grep upst
upstream        git@github.com:wolfi-dev/os (fetch)
upstream        git@github.com:wolfi-dev/os (push)

$ melange version | grep ^[A-Z]
GitVersion:    v0.11.1
GitCommit:     a52edcc075ebf1dc89aea87893e3821944171ee3
GitTreeState:  clean
BuildDate:     '2024-07-19T02:44:39Z'
GoVersion:     go1.22.5
Compiler:      gc
Platform:      linux/amd64

Failures:

--runner=bubblewrap
$ make MELANGE_EXTRA_OPTS=--runner=bwrap package/datadog-agent
2024/07/19 20:14:30 WARN   8700K .......... .......... .......... .......... .......... 97%  673M 0s
2024/07/19 20:14:30 WARN   8750K .......... .......... .......... .......... .......... 97%  114M 0s
2024/07/19 20:14:30 WARN   8800K .......... .......... .......... .......... .......... 98% 68.7M 0s
2024/07/19 20:14:30 WARN   8850K .......... .......... .......... .......... .......... 98%  131M 0s
2024/07/19 20:14:30 WARN   8900K .......... .......... .......... .......... .......... 99%  184M 0s
2024/07/19 20:14:30 WARN   8950K .......... .......... .......... .......... .......... 99%  402M 0s
2024/07/19 20:14:30 WARN   9000K ....                                                  100% 7.79T=0.3s
2024/07/19 20:14:30 WARN
2024/07/19 20:14:30 WARN 2024-07-19 20:14:30 (27.3 MB/s) - 'common.deb' saved [9220280/9220280]
2024/07/19 20:14:30 WARN
2024/07/19 20:14:55 INFO clang --version
2024/07/19 20:14:55 INFO clang version 12.0.1
2024/07/19 20:14:55 INFO Target: x86_64-unknown-linux-gnu
2024/07/19 20:14:55 INFO Thread model: posix
2024/07/19 20:14:55 INFO InstalledDir: /opt/clang/bin
2024/07/19 20:14:55 WARN /bin/bash: line 1: sudo: command not found
2024/07/19 20:14:55 WARN /bin/bash: line 1: sudo: command not found
2024/07/19 20:14:55 WARN /bin/bash: line 1: sudo: command not found
2024/07/19 20:14:55 INFO sudo /opt/datadog-agent/embedded/bin/clang-bpf --version
2024/07/19 20:14:55 INFO sudo /opt/datadog-agent/embedded/bin/llc-bpf --version
2024/07/19 20:14:55 INFO sudo mkdir -p /opt/datadog-agent/embedded/bin
2024/07/19 20:14:55 ERRO ERROR: failed to build package. the build environment has been preserved:
2024/07/19 20:14:55 INFO   workspace dir: /home/user/tmp/melange-workspace-403892385
2024/07/19 20:14:55 INFO   guest dir: /home/user/tmp/melange-guest-3929106491
2024/07/19 20:14:55 ERRO failed to build package: unable to run package datadog-agent pipeline: unable to run pipeline: exit status 127
make[1]: *** [Makefile:111: packages/x86_64/datadog-agent-7.55.1-r0.apk] Error 1
make[1]: Leaving directory '/home/user/src/wolfi-os'
make: *** [Makefile:101: package/datadog-agent] Error 2

--runner=docker:
$ echo $TMPDIR
/home/usr/tmp
$ ls -altrd /home/user/tmp
drwxr-sr-x  226 user     docker       40960 Jul 19 20:27 /home/user/tmp

2024/07/19 20:25:13 WARN + cp Dockerfiles/agent/init-stage3-host-pid /home/build/melange-out/datadog-agent/etc/s6/init/init-stage3-host-pid
2024/07/19 20:25:13 WARN + exit 0
2024/07/19 20:25:13 INFO running step "Strip binaries"
2024/07/19 20:25:13 WARN + '[' -d /home/build ]
2024/07/19 20:25:13 WARN + cd /home/build
2024/07/19 20:25:13 WARN + exit 0
2024/07/19 20:25:13 WARN + '[' -d /home/build/melange-out/datadog-agent ]
2024/07/19 20:25:13 WARN + cd /home/build/melange-out/datadog-agent
2024/07/19 20:25:13 WARN + scanelf --recursive --nobanner --osabi --etype ET_DYN,ET_EXEC .
2024/07/19 20:25:13 WARN + read type osabi filename
2024/07/19 20:25:13 WARN + '[' NONE '!=' STANDALONE ]
2024/07/19 20:25:13 WARN + strip -g ./usr/bin/agent
2024/07/19 20:25:16 WARN + read type osabi filename
2024/07/19 20:25:16 WARN + '[' NONE '!=' STANDALONE ]
2024/07/19 20:25:16 WARN + strip -g ./usr/lib/libdatadog-agent-rtloader.so.0.1.0
2024/07/19 20:25:16 WARN + read type osabi filename
2024/07/19 20:25:16 WARN + '[' NONE '!=' STANDALONE ]
2024/07/19 20:25:16 WARN + strip -g ./usr/lib/libdatadog-agent-three.so
2024/07/19 20:25:16 WARN + read type osabi filename
2024/07/19 20:25:16 WARN + exit 0
2024/07/19 20:25:16 INFO running pipeline for subpackage datadog-agent-jmx
2024/07/19 20:25:26 INFO pod 6d99476d0e0ba3e4507c2c22e201b1442f07bb419b7babc3598b8c3dfe055198 terminated
2024/07/19 20:25:26 ERRO ERROR: failed to build package. the build environment has been preserved:
2024/07/19 20:25:26 INFO   workspace dir: /home/user/tmp/melange-workspace-150168302
2024/07/19 20:25:26 INFO   guest dir: /home/user/tmp/melange-guest-2009475398
2024/07/19 20:25:26 ERRO failed to build package: mkdir /home/user/tmp/melange-workspace-150168302/melange-out: permission denied
make[1]: *** [Makefile:111: packages/x86_64/datadog-agent-7.55.1-r0.apk] Error 1
make[1]: Leaving directory '/home/user/src/wolfi-os'
make: *** [Makefile:101: package/datadog-agent] Error 2

Note that on a workstation you get TMPDIR set to /home/user/tmp/ and
$ ls -ld /home/user/tmp/
drwxr-sr-x  226 user     docker       40960 Jul 19 20:33 /home/user/tmp/

I've also tried unsetting TMPDIR (thus using /tmp) (dies the same way).
$ make ....
2024/07/19 20:36:19 INFO running pipeline for subpackage datadog-agent-jmx
2024/07/19 20:36:30 INFO pod e526f79266b40c1dba9eeb27775b82217a088ac964d4c134afd51144ecd4e9aa terminated
2024/07/19 20:36:30 ERRO ERROR: failed to build package. the build environment has been preserved:
2024/07/19 20:36:30 INFO   workspace dir: /tmp/melange-workspace-2565688441
2024/07/19 20:36:30 INFO   guest dir: /tmp/melange-guest-4221147986
2024/07/19 20:36:30 ERRO failed to build package: mkdir /tmp/melange-workspace-2565688441/melange-out: permission denied
make[1]: *** [Makefile:111: packages/x86_64/datadog-agent-7.55.1-r0.apk] Error 1

$ ls -ld /tmp/
drwxrwxrwt   11 root     root           300 Jul 19 20:32 /tmp/

I'm having the same sort of issue I think. Looks like the melange workspace folder is getting created as root and then can't be accessed again. This only happens sometimes.

Also of note, if I run with --runner=bubblewrap, it'll succeed. Although it takes 10x longer...

wiki page documenting what is required to workaround these issues @ https://eng.inky.wtf/docs/squads/sustaining/playbooks/package-updates/datadog_agent/

https://github.com/chainguard-dev/wiki/pull/914 PR to remove playbook now that building datadog-agent without build patches is possible

@smoser Can we close this now with your changes @ https://github.com/wolfi-dev/os/pull/33387 ?

yes. closing. thanks.


fix(ring_outlier_filter): change a parameter to be less misleading

Description
The name of a ring_outlier_filter parameter (max_rings_num) has been changed to be less misleading (max_ring_index), and the source code has been modified accordingly.
In a project using Autoware, max_rings_num was set to 128 (i.e. the range of ring index was set to be 0~127), but actually the maximum value of ring index was 128.
To prevent this kind of thing, the parameter name should be changed to be less misleading.
TIER IV internal link
Tests performed
Even in projects with a maximum ring index of 128, it worked without error messages.
Effects on system behavior
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[x] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

We are closing this PR as there are no response for months. Please re-open if the issue still persists.


Crash Report 956529866

Link:
http://localhost:3333/cata/death_knight/unholy/#eJzjkuBgdGBMYGxgZJzByPiBkbGDiXEDE+MFJkYnTgGgTAHjBEZGIQapVrZZzGwBOYmVqUUcjAJcUg8YuYQEtl5nlninoMR2bAZz+wxmjXmMXGwCi/8wa9Rw8Quc6GGReKagBJZoZOTiFFj/nFniB5dGLVDfsj/MEvflldj+TofpExDoO8Is0SqnxAIUYNBYzsjFKzDnL7MSyyQQdykjF5/Avj/MSmxAWaAI0AIhgXl/mSXmK4CFQIYAtQgKHL3GLNGhADYYooxd4OQxZpB+NoF1YIexCNz7wwwS3sGsMZ2Ri0vgJ9AtK6Q0JjJyMXDxCCx+xqzE/G46s0YXoxI3B6OBRABjBCgEtB4wSTBz3WBkGKZAqGHAvWbF4MQQxS/Fy8UpCBH4YC/EsIvJzsjA2AAd6BpiCIEEjYEqjY0MjYwNjI0NDUEMw0NMKhzzrzAJzL3CJPHmKZNC7xUmjU3XmAzmXGGy6L/C5DD5CpPHjKtMJ0BJnuUWE8MjJiYJxhdMKY3MEEeIOCyEsiIdupgZlI4zeTBzgvkNaQ6CMDWSs2aCwEl7S4jIBXvFNDC4Zu949gwIvLE36mEqWPWZsYo7KDEzRSEksSg9tUQhQoJVi06pSqPTgZrGNaQcRzbPx2LuHEd0NeDQaFjE6TiTERJAN+2halgcANaun38=
RNG Seed:<PHONE_NUMBER>
runtime error: invalid memory address or nil pointer dereference
Stack Trace:
goroutine 191 [running]:
runtime/debug.Stack()
/opt/hostedtoolcache/go/1.21.13/x64/src/runtime/debug/stack.go:24 +0x5e
github.com/wowsims/cata/sim/core.runSim.func1()
/home/runner/work/cata/cata/sim/core/sim.go:125 +0x98
panic({0x1ab4be0?, 0x3ff1d30?})
/opt/hostedtoolcache/go/1.21.13/x64/src/runtime/panic.go:914 +0x21f
github.com/wowsims/cata/sim/core.(*Simulation).advanceTasks(0xc0069830e0)
/home/runner/work/cata/cata/sim/core/sim.go:546 +0x69
github.com/wowsims/cata/sim/core.(*Simulation).Step(0xc0069830e0?)
/home/runner/work/cata/cata/sim/core/sim.go:503 +0xd2
github.com/wowsims/cata/sim/core.(*Simulation).runPendingActions(...)
/home/runner/work/cata/cata/sim/core/sim.go:481
github.com/wowsims/cata/sim/core.(*Simulation).runOnce(0xc0069830e0?)
/home/runner/work/cata/cata/sim/core/sim.go:368 +0x30
github.com/wowsims/cata/sim/core.(Simulation).run(0xc0069830e0)
/home/runner/work/cata/cata/sim/core/sim.go:335 +0x2db
github.com/wowsims/cata/sim/core.runSim(0xc005ff3e00, 0xc0000b6a80, 0x0, {{0xc001e4e8f8?}})
/home/runner/work/cata/cata/sim/core/sim.go:180 +0x2c7
github.com/wowsims/cata/sim/core.(...

Cheers!
We've recently updated how stats are handled internaly. Is it possibel that you opened your browser with a saved instance? This might lead to inconsistencies. Usually this should be removed by simply refreshing the page.
Make sure you're running the latest version of the local sim.
Does the error persist?

Closed due to no reaction for 4 weeks


chore: make gateway-common crate domain agnostic

Code relocation changes to put all domain-specific code under gateway-framework. In other words, "putting together things that should change together".

Part of https://github.com/edgeandnode/gateway/issues/791


Report State and changing light colors

Hi,
is there a definition how to handle lights which change their light color very quickly?
For example, there might be a Hue light which uses a 'party' scene. It changes the color, brightness, etc. all the time, even within a second. How should such lights be handled with report state? I don't think that it makes sense to report about 10 states within a second.
Thanks!

Any updates on this? Same applies to measured temperature for thermostats. How often should it be updated? In some cases it might happen that the temperature jumps between 21.24 and 21.25 degrees and I have to report it every minute about 20 times. Humidity is the same.

The goal of proactively reporting the state is to show the user useful information on their phone or smart display. If a color is changing frequently, then they shouldn't expect to see the same color right immediately. If they're looking at the temperature, the accuracy of the thermostat display is to the whole degree.
Report state should be used during meaningful changes in the device state, such if it settles on one color or changes by a whole number degree.


19.3 fb 39753 pg jdbc caching

Parent branch has been merged to develop; this branch was used to fix the name for TeamCity purposes.


2024-11-08_01-35-00_master-next_python3-boto3

Automatically created.

Backport failed for kirkstone-next, because it was unable to cherry-pick the commit(s).
Please cherry-pick the changes locally and resolve any conflicts.
git fetch origin kirkstone-next
git worktree add -d .worktree/backport-10290-to-kirkstone-next origin/kirkstone-next
cd .worktree/backport-10290-to-kirkstone-next
git switch --create backport-10290-to-kirkstone-next
git cherry-pick -x 88f6c443ab9ad91399b9c3b68ed57debc041accb

Backport failed for scarthgap-next, because it was unable to cherry-pick the commit(s).
Please cherry-pick the changes locally and resolve any conflicts.
git fetch origin scarthgap-next
git worktree add -d .worktree/backport-10290-to-scarthgap-next origin/scarthgap-next
cd .worktree/backport-10290-to-scarthgap-next
git switch --create backport-10290-to-scarthgap-next
git cherry-pick -x 88f6c443ab9ad91399b9c3b68ed57debc041accb

Backport failed for styhead-next, because it was unable to cherry-pick the commit(s).
Please cherry-pick the changes locally and resolve any conflicts.
git fetch origin styhead-next
git worktree add -d .worktree/backport-10290-to-styhead-next origin/styhead-next
cd .worktree/backport-10290-to-styhead-next
git switch --create backport-10290-to-styhead-next
git cherry-pick -x 88f6c443ab9ad91399b9c3b68ed57debc041accb


fix: auto-format file on save + format all files

I noticed several files had indentation / format issues.
I've added a auto-format on save config for VSCode, and formatted all files.
This will make collaboration easier / more consistent

Good idea. Thanks!


5-fold validation

Thank you so much for collecting and open-sourcing this dataset!
However, I noticed that you used 5-fold validation in your work. Could you provide the metrics for each fold? Or provide the relevant code and model.
Looking forward to your reply.

Can anyone provide this dataset?


Support language specific folders

It would be nice to support language specific folder, i.e if I name a folder folder.en, that folder should be considered just if the language is set to en.
That, IMHO, would help keep the folder structure more settled (Imagine 10 files in a folder for 3 languages, that's 30 files)

Sorry I didn't know that was already possible


Fix typo in template_v2.py

seperator -> separator

Thanks! We need to fix this in all files though. I see it in template v3 also and maybe elsewhere?

@okhat
Thank you for reaching out! I've used grep to search and fixed everything.

Merged. Thank you!


Which version to use? v3 or v4?

Hey guys, based on the changelog you wanted to stop supporting v3 on 29. Mar 2018 when v4 was released. Unfortunately, I see only v3 changes in the changelog to continue since then.
Does it mean we should still use the v3 instead?

Hello @rokerkony,
Sorry for the late reply. You should use v3 for now


Add SWR fallback to index page

SWR on index page should use SSR data for first page
https://swr.vercel.app/docs/with-nextjs#complex-keys

I think it's not actual. We will use same hack to live updates.


AHHH HELP MAJOR CRASH

Issue Description:
What happens:
Client side crash
What you expected to happen:
Get a bucket from Applied Energetic System
Steps to reproduce:

Make a Magma Crucible
2.Make a Fluild Transponder
3.power up using energy conduits
...

Affected Versions (Do not use "latest"):

EnderIO: 5.0.31
EnderCore:1.12.2-0.5.37
Minecraft: 1.12.2
Forge: <IP_ADDRESS>
SpongeForge? No
Optifine? No
Single Player and/or Server? Server

https://paste.dimdev.org/jacubonodo.mccrash

what do mean invalid. That is the minecraft version I am using 1.12.2....and besides that what about the bug.....????

"Invalid", presumably, because of line seven of your posted crash report:

java.lang.RuntimeException: Fluid tinker_io.fluids.PureMetal@342c1534 (puremetal, class tinker_io.fluids.PureMetal) from item 1xic2.fluid_cell@0 returned an unregistered block from getBlock(). This is a major bug in the mod that fluid belongs to.

Which, if I'm reading it correctly, indicates that a fluid from Tinker's IO, stored in an item from IC2, is not registering a block for the fluid.

Not exactly... tinkerio says Yes my fluid has a block form. Then when enderio aakes for that form it returns undefined and crashes... this is not a enderio issue


Renew TEST Certificate (mid April)

Describe the task
Our TEST certificate will expire on June 1st, 2024. Ticket for renew we done last year for PROD https://github.com/bcgov/nr-fom/issues/421. Since the Certbot is not working anymore, we might not get notification, created this ticket to remind us. We need to send service desk a ticket to renew the certificate, and write Derek a ticket to help us install the new one.
Acceptance Criteria

[x] create a service desk ticket
[x] pass the certificate to Derek
[ ] third

Additional context

Add any other context about the task here.
Or here

service desk ticket created https://apps.nrs.gov.bc.ca/int/jira/servicedesk/customer/portal/1/SD-110002

Process:

Create a service desk ticket: https://apps.nrs.gov.bc.ca/int/jira/servicedesk/customer/portal/1
Create a certificate request file (CSR)
Derek has a script to auto generate that: https://github.com/bcgov/quickstart-openshift-helpers/blob/main/cert-setup/csr_generator.sh
To run the script:
- clone the repo git clone https://github.com/bcgov/quickstart-openshift-helpers.git
- go to the script cd cert-setup/csr_generator.sh
- run the script sh csr_generator.sh and provide our domain fom-test.nrs.gov.bc.ca in the popup questions
The script will generate two files: fom-test.nrs.gov.bc.ca.csr and fom-test.nrs.gov.bc.ca.key
Send the CSR file to the service desk request, and keep the key file safe

Timeline for this time:

Created the service desk ticket on Apr 29, 2024
Submitted the certificate request file (CSR) on May 7, 2024 (this one should be done when created the ticket, but because this is the first time we went through the new process, missed it at the beginning)
Service desk created new certificate request on their side REQ0512972 on May 8, 2024

Got email from CITZ Identity Management Solutions CITZ:EX<EMAIL_ADDRESS>send them the CSR file again.

FOM TEST certificate is renewed for our Api, Public and Admin site:

Removed the certbot cronjob from Openshift FOM TEST namespace as it's not working anymore.


How to better manage release doc

The GitHub Issues allow only two categories: Label and Milestone. Naturally we use a release label for Milestone and assign issue for each. But some issues are fixed across multiple releases, and we can't do that with Milestone in GitHub :(
We can either use Label for a release or we can track them with a RELEASE.adoc file. Which one is better?
If we use Label, then creating Milestone per release label seems redundant. I suppose Milestone is just a categories of ONE timeline bucket rather than tight to multiple release schedules.

This is addressed by #301


How to get [Backup Directory Path]

How can I get the Backup Directory Path. This is the field in System->[Application Paths]->[Backup Directory Path].
I'm trying to implement logic to limit the number of backups.
Side-Note: I'm not sure yet when to post a question in CommunityScripts or when to post it in stg-annon->stashapi. It would help if when posting a question, the issue template would state what type of issues should be posted.
There doesn't seem to be as much eyes in stg-annon->stashapi compared to CommunityScripts, which makes me think my question would get answered faster in CommunityScripts.

it would be part of a configuration query so for stashapi that would be
stashapp.get_configuration("general { backupDirectoryPath }")

It probably would be answered quicker in the community repo or in Discord stashapi is just a python wrapper around the GraphQL API that stash provides it is intended to mirror most of the functions of the API to make it easier to develop python integrations, this specific question as more to do with Stash's API
More generally if your looking to replicate something from the UI take a look in the network section of the browser dev tools and you will see what call the UI is making to the API

stashapp.get_configuration("general { backupDirectoryPath }")

Thank you very much.
Can it safely be called like this stashapp.get_configuration()['general']['backupDirectoryPath'] instead? Or could that cause issues?

More generally if your looking to replicate something from the UI take a look in the network section of the browser dev tools and you will see what call the UI is making to the API

I'm not sure what you mean by browser dev tools. Are you referring to the GO files in the following path:
stash\stash-0.26.2\internal\api
I've been looking for documentation on stashapi, but I can't seem to find any.
I was expecting to see something in docs.stashapp.cc, but I found nothing that came close to covering it.
Is there some place else I should look for documentation?
Thank you for all your help.

Can it safely be called like this stashapp.get_configuration()['general']['backupDirectoryPath'] instead? Or could that cause issues?

I believe it is safe to do this unless there is an error encountered somewhere in the request to stash, if that happens you'll get a KeyError
By browser dev tools I mean the F12/"Inspect Element" portion of your browser, when interacting with the Stash application you can see the requests the UI is making to the Go backend
Stash the application is self documenting see http://localhost:9999/playground
stashapp-tools generally trys to follow the same structure just in a more pythonic syntax, all of the available documentation for stashapp-tools are in the form of docstrings which will show up when using an IDE like VS Code

By browser dev tools I mean the F12/"Inspect Element" portion of your browser, when interacting with the Stash application you can see the requests the UI is making to the Go backend

I just tried this on both Firefox and Chrome.  I wanted to see if I can find what's sent to the backend  when clicking [Clean generated files...] in the Task->Maintenance option. But I didn't see any indication of that. I did try inspecting the sub sections, but there's so many sub parts, that it's like finding a needle in a hey stack.
Here's snapshots before and after clicking the button with F12/Inspect displayed using Chrome.

After clicking the button.

I guess this might be more obvious to someone more familiar with GraphiQL and/or using the F12-Inspect.
Can you please direct me as to specifically what section I should be looking for?
Thank you

at the top of the window you will see a tab called Network select that tab and you will see the request being made

at the top of the window you will see a tab called Network select that tab and you will see the request being made

Thank you so much. That does clarify things for me now.
And thank you for being so patient with me. ☺ I appreciate it.
With the tools you've shown me I was able to figure out how to implement the metadata_clean_generated.
def metadata_clean_generated(self, blobFiles=True, dryRun=False, imageThumbnails=True, markers=True, screenshots=True, sprites=True, transcodes=True):
    query = """
    mutation MetadataCleanGenerated($input: CleanGeneratedInput!) {
      metadataCleanGenerated(input: $input)
    }
    """
    clean_metadata_input = {
        "blobFiles": blobFiles,
        "dryRun": dryRun,
        "imageThumbnails": imageThumbnails,
        "markers": markers,
        "screenshots": screenshots,
        "sprites": sprites,
        "transcodes": transcodes,
    }
    result = self.call_GQL(query, {"input": clean_metadata_input})
    return result

The above variables are in the following network graphql listing:

However, when I look at the network graphql listing for MetadataClean, I only see the dryRun variable:

The metadata_clean function has a paths variable in addition to the dryRun variable. At first I was wondering how would you know to include the paths variable, but when I removed the paths variable from the input, the function still worked.
	def metadata_clean(self, paths:list=[], dry_run=False):
		query = """
		mutation MetadataClean($input:CleanMetadataInput!) {
			metadataClean(input: $input)
		}
		"""
		clean_metadata_input = {
			"dryRun": dry_run
		}
		result = self.call_GQL(query, {"input": clean_metadata_input})
		return result

I don't think the paths variable is supposed to be in metadata_clean.
Should I include that as a fix in the update?
If so, I was thinking of leaving the paths in the function argument so-as to not to break existing code for anyone using the API.

The network tab is a good place to see a working example of something you might want to do but further documentation of a function can be found in the playground

So my conclusion is that the paths variable seems to be an undocumented supported variable for MetadataClean.

not undocumented but unused in that call from the UI, see CleanMetadataInput in the playground for what the metadataClean function is expecting as the input

Thank you again for all your help.


Search page autocomplete

Implement autocomplete for genes + drugs

look at Civic repo

Things to fix/implement with this issue:

No suggestions are shown when a user starts typing
Clicking on a "suggestion" does nothing
We probably shouldn't show the suggestions until a user begins typing


[CALCITE-2489] Order of fields in JavaTypeFactoryImpl#createStructType is unstable

2488

 Quality gate: Failed
10 Issues

 5 Code issues
 5 Anti-patterns

Details


MOL company job listings discrepancies and non-functional links on peviitor.ro

Environment:
URL: _https://peviitor.ro/_
Browser: Microsoft Edge
Device: Desktop
OS: Windows 7
Steps to Reproduce:

Access the link: _https://peviitor.ro/_
Search for the given company: MOL
Right-click and select "Inspect"
Copy the Request URL: _https://api.peviitor.ro/v3/search/?q=mol&country=România&page=1_
Check the Request Method, which is GET
Open Postman and create a new entry with a GET request
Send the request

Expected Results:
The GET request should return a response with a status of 200 OK. The number of job openings retrieved from the API response should ideally match the number of job openings listed on the official website of MOL. The links directing to MOL job openings should be functional, and the location information should accurately reflect the job locations.
Actual Results:
The GET request returns a response with a status of 200 OK, indicating that the request was successful. However, the number of job openings retrieved from the API response does not match the number of job openings listed on the official website of MOL, likely due to the scraper running only once a day.

Furthermore, the links directing to MOL job openings are not functional, indicating a potential issue with the website's linking mechanism. Additionally, the location information for the job listings is inaccurately marked as "Romania" instead of specifying the actual city, which may lead to confusion for users.

Cred ca gata. Poti retesta?


Fix build

Codecov Report

Merging #45 (c4fc670) into develop (9473a38) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop      #45      +/-   ##
===========================================
- Coverage    98.26%   98.26%   -0.01%
===========================================
  Files           32       32
  Lines         6736     6735       -1
===========================================
- Hits          6619     6618       -1
  Misses         117      117

Impacted Files
Coverage Δ

tests/test_translator.py
91.57% <0.00%> (-0.09%)
:arrow_down:

tests/test_mongo.py
30.00% <0.00%> (ø)

splunk_connect_for_snmp_mib_server/mib_server.py
22.50% <0.00%> (ø)

splunk_connect_for_snmp_mib_server/translator.py
82.12% <0.00%> (ø)

...unk_connect_for_snmp_mib_server/snmp_mib_server.py
44.11% <0.00%> (ø)

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 9473a38...c4fc670. Read the comment docs.

I have read the Code of Conduct and I hereby accept the Terms

recheck

:tada: This PR is included in version 1.8.0-develop.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Second Order FC Performance Enhancements

Looks great, thanks for Christmas PR-esent! Waiting for CI to finish and I'll approve.


Fix app data dir not opening on macOS when "Open AppData" button pressed

Pull request checklist:

[x] CHANGELOG.md was updated, if applicable

Description
This PR aims to fix chatterino's app data directory not opening on macOS when pressing the "Open AppData..." button. When pressing the button on Windows/Linux the relevant directory is opened in the file explorer. When attempting to do this on macOS Finder does not open up the expected directory of $HOME/Library/Application Support/chatterino.
This is caused by macOS requiring file:// prior to the path in order for it to be opened in finder.
Fixes #2531

Current behaviour:
https://user-images.githubusercontent.com/4962764/111604626-6ce62680-87cd-11eb-819a-69b2b9511524.mp4
Expected behaviour:
https://user-images.githubusercontent.com/4962764/111604620-6bb4f980-87cd-11eb-86ea-cf18d954bf0b.mp4


Added survey to workshop!

There are multiple copies of the image. only the png image in media is used.

Thnx @karthik2804 - removed the image that wasn't being used.


Fast lossless incorrectly encodes grayscale+alpha image

Describe the bug
When encoding losless images with the fast lossless encoder, the encoder creates images the decoder cannot parse
To Reproduce
The below image

was used as the test sample
Expected behavior
An image encoded to .jxl which could be decoded back to the expected input using the fast encoder

OS: Manjaro Linux
Compiler version:  GCC 12.2.1
CPU type: x86_64

Additional context

Removing the alpha channel makes the encoder produce a working image.

The cjxl encoder generates a decodable image.

the first generated bytes are

cjxl
fast_lossless

ff 0a fa 15 e0 3f 58 09  08 08 10 00 84 02 00 00
ff 0a fa 15 e0 3f 58 14  37 02 08 08 10 00 30 0b

The only weird behaviour I could note was that jxlinfo interpreted the output as RGB+A
Command
jxlinfo -v ./a.jxl

output was
JPEG XL image, 512x704, (possibly) lossless, 8-bit RGB+Alpha
num_color_channels: 3
num_extra_channels: 1
extra channel 0:
  type: Alpha
  bits_per_sample: 8
  alpha_premultiplied: 0 (Non-premultiplied)
have_preview: 0
have_animation: 0
Intrinsic dimensions: 512x704
Orientation: 1 (Normal)
Color space: RGB, D65, sRGB primaries, sRGB transfer function, rendering intent: Relative

There is also a huge difference in size, when using cjxl and fast encoder, (53k vs 33k), is there something I'm missing?
sample outputs

wrong-image: Output of what I got after encoding with fast lossless encoder
correct-working-jxl-image: Working image
input.ppm.txt: Input image, P7 ppm format in grayscale+alpha

input.ppm.txt

Does the issue still happen on github-main? I cannot seem to reproduce it...
Can you give more details on how you compiled and ran fast-lossless?

Can you give more details on how you compiled and ran fast-lossless?

I copied enc_fast_lossless.cpp from the repo into a project, and added the main repo which simply calls the PPM reader and writes to a jxl file.
The file was simplified to meet my needs, i.e  a little less template code and removed the intrinsics support for easier debugging.
The enc fast lossless code comes to about 2k LOC , https://gist.github.com/etemesi254/09f66aeab2d38b6b3ef358c3ec9a8a96

Does the issue still happen on github-main? I cannot seem to reproduce it...

Yes it does,  attached simple setup I'm using. Use input.ppm as it contains the necessary headers for luma+alpha support,
simple_jxl.zip


Fix highlight-article priority (Issue #227)

Highlight-article now takes priority over listnormal_unread and
listfocus_unread.
Fixes issue #227

I slightly amended your fix, but it's now merged. Thank you!


[BUG] When running a Tail, user gets prompted for password for sudo

Describe the bug
When running a Tail in the Field Mapping Builder, no data is coming in, and when I check the Shipper's logs, I can see it's waiting for user to enter its password:
[sudo] password for logrhythm:
Log sample:
webhookbeat service started.
🔎 Checking if the new instance is running...
webhookbeat_T_34263d4a_1 // running // Up Less than a second
📑 Tailing the Beat's own internal logs to EZ Client...
📑 Tailing the realtime data...
2023-04-25T12:44:37.207Z INFO instance/beat.go:616 Home path: [/app/cmd/beats/webhookbeat] Config path: [/app/cmd/beats/webhookbeat] Data path: [/app/cmd/beats/webhookbeat/data] Logs path: [/app/cmd/beats/webhookbeat/logs]

[... LOGS REMOVED ...]

2023-04-25T12:44:37.266Z INFO beater/webhook.go:62 webhookbeat is running! Hit CTRL-C to stop it.
2023-04-25T12:44:37.268Z INFO heartbeat/status_beater.go:111 heartbeat sent
[sudo] password for logrhythm:
🟥 Tailing Terminated.
EXIT | Tailjob exited. | 1
END | Closing this Tail. | 🏁

To Reproduce
Steps to reproduce the behavior:

Go to Field Mapping Builder
Click on Start Tail
View Shipper's logs
See error

Expected behavior
The tail should work fine.
Screenshots

Desktop (please complete the following information):

OS: Windows and MacOS
Browser: Chrome
Version: 112.0.5615.138 (Official Build) (64-bit)

Additional context
Error reported by Brandon Pace. Thanks.

###Root cause:
The command that causes this actually runs two commands:

docker logs ...
sudo -S tail -F ....

docker logs --follow --since 10s "webhookbeat_ABCDEF" >&2 & cat | sudo -S tail -F /var/lib/docker/volumes/webhookbeat_spool_volume_ABCDEF/_data/realtime.tail
The password is provided in the STDIN, as expected by the sudo -S, but as the docker command is first, then it grabs the STDIN instead of sudo -S.
Solution:
Switch the commands order.


Add eleventy-plugin-footnotes to the list of plugins

I hope I did everything well!

LGTM thanks!


Install not returning error message if cluster not bootstrapped

When running glasskube install argo-cd on not bootstrapped cluster, CLI asking if I want to bootstrap instead of error message and non-zero exit code.
If you're making glasskube in idea of Linux package managers, it should not ask anything by default, too "GUIsh".

I think there is definitely a case for this, but I'm not sure if this should be the default.
One solution I could imagine would be a --no-bootstrap flag, that if used prevents the bootstrap dialog and the application just exits with a non-zero code. Do you think this would work for your use-case?

Can I work on this issue and add --no-bootsrap flag?

Hi @aminsaedi, thank you for your interest in contributing!
I just realized, that the desired behavior is already possible using the --non-interactive flag. Therefore, I don't think an additional --no-bootstrap flag would add any value.
What's your opinions @pmig @christophenne?

@kosmoz that's a good point. @aleksey-hariton would this solve your issue you encountered in the first place?

@kosmoz good idea, I also think this should be fine.


[New game]: Fruit Catching

🎮 Game Request
Game logic and basic description
This is a single-player game made of HTML CSS and javascript. The basic idea is the player uses A and D or <- and -> keys to move the bucket to catch the fruit. If they miss the game is over and the point is displayed.
Point down the features
Game points
The player catches as many fruits as they are rewarded with the same amount of points.
 Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


Binary Serach Program using C++

Binary Serach Program (Iterative method) using C++

Star this repo

Star this repo

Ofcourse 🙂


add support for using the fixture tests from other libraries

[x] I've added tests to cover the proposed changes

overview
In budgetkey-data-pipelines project we have the need to write unit tests for custom datapackage processors
The framework used to test the datapackage pipelines stdlib is perfectly suited for that.
Changes proposed in this pull request:

refactor the test_stdlib code into an externally accessible base class under datapackage_pipelines.utilities.lib_test_helpers.ProcessorFixtureTestsBase
test_stdlib was modified to use this class

@OriHoch Would you mind giving a brief guide to using this text fixture set up in an external plugin? I'm trying to get a simple example working, but I'm not sure how to structure the fixtures or ProcessorFixtureTestsBase subclass.

@brew - it's used here: https://github.com/frictionlessdata/datapackage-pipelines/tree/master/tests/stdlib
and here: https://github.com/OriHoch/budgetkey-data-pipelines/tree/7526219c0bc8420a9e595e3899df01e7f6c59d85/tests/tenders

Thanks - I found those. I was more interested what each item (delimited by '--') in the fixtures file refers to. They're order dependent, but not documented, so a bit opaque (to me).

this is the relevant function:
https://github.com/frictionlessdata/datapackage-pipelines/blob/master/datapackage_pipelines/utilities/lib_test_helpers.py#L47
the order is:
processor - the name of the processor to run
--
params - json object with parameters for the processor
--
dp_in - input datapackage descriptor
--
data_in - input data stream
--
dp_out - expected output datapackage descriptor
--
data_out - expected output data stream

Thanks - that's a useful summary. Especially for people coming back to this pull request later.