[$500] unable to submit report, "unexpected error" appears

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number:
Reproducible in staging?: needs reproduction
Reproducible in production?: needs reproduction
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @luacmartins
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1706246633750589
Action Performed:

Create an expense report as employee
Submit the report

Expected Result:
Able to submit with no errors
Actual Result:
Requested approver not on workspace RequestID 84b6517d4fb061e2-YVR. Unexpected error, please try again error message
NOTE: After sometime the message shows as concierge submitted the report and submit button disappears
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0153368e03926bacdf
Upwork Job ID:<PHONE_NUMBER>786544128
Last Price Increase: 2024-02-21

This might be a backend issue, but I'm not positive. @mollfpr, would you mind taking a look?

Yeah, that seems to be a backend issue but I'll have a look.

Sorry for the delay, I'll get the test in the morning!

Issue not reproducible during KI retests. (First week)

I'll apply the re-test label for one more week. If the behavior is not reproducible after that, let's close the issue.

Issue not reproducible during KI retests. (First week)

I think we can close this. Please reopen if it happens again.


Brginning skip.

Describe your bug here. Mind you, if you are modding, please try testing your bug in a clean version of the engine instead, this ensures the bug is actually caused by the engine itself. Also, if you're using an older version of JSE, please try the latest action build in the Actions tab or the latest release build. The issue has probably been fixed since that version. Oh yeah, and also be sure to check the pinned 'JS Engine: Known Issues' issue, to double check if your issue hasn't already been found!
Every time I press enter during the intro screen before the starting screen where I press enter to begin, it shows this error messsage:
"Invalid fiield:timestamp" #332

Maybe retry checking the timestamps & matching them with the configured field or something to broadcast the flash & skip to the "PRESS ENTER TO BEGIN" screen...
Command Prompt/Terminal/Crash logs (if existing)
No response
Have you identified any steps to reproduce the bug? If so, please describe them below in as much detail as possible. Use images if possible.
No response
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
No, I just reported the issue.
If you use 1.12.0 or earlier, did you have Optimized Chart Loading turned on?
None
Did you check for any similar issues to what you're reporting? Check, then come back here. If there is a similar issue, then do not report the issue, otherwise it will be marked as a duplicate.
Yes

but.. when you press ENTER, it does FlxG.switchState(TitleState.new);

now i cant even go to the main menu

the only thing i can do now is click, any key i press and it says i cant go to main menu
https://github.com/JordanSantiagoYT/FNF-PsychEngine-NoBotplayLag/assets/163363593/ebda75f0-507d-48a5-a2fc-532e80d796e6

maybe it has something to do with the timming of the intro screens?

there could be a slight possibility that your installation is corrupted. try reinstalling jse

i already did, that video was my 2nd attempt for my 1-2 comment, the photo is from my 3rd trying to see what happens if i wait for the last intro text state

im gonna try one more time without using win rar

didnt work

Yeah idk. i don't get the error so i can't help you.

ill just wait for next version then (ill have my pc updated by then)

congratulations, you fixed the error i was having, it now works and i can use your engine 100% again


Update matrix.json

fix (documentation): updated text to use CI/CD consistently

This file is generated by a Github action that uses the yaml files as source. I see the bug - i'll fix the source itself.
Thanks!


Blackfire integration seems incomplete?

ISSUE TYPE

Question

SUMMARY
Support for Blackfire seems to be incomplete. After adding Blackfire through the instructions, the profiling returns an error "Probe not found, invalid signature".
It seems like Blackfire PHP is not being installed? If I install it - along with the agent - manually, nothing works either.
Are there any of these steps which are missing in the configuration, so Blackfire starts correctly when issuing "docker-compose up"?

https://blackfire.io/docs/integrations/docker
https://blackfire.io/docs/up-and-running/installation
https://blackfire.io/docs/book/06-installation

Goal
To be able to run Blackfire profiling on my local Devilbox Docker environment.
Thank you in advance.

It seems like Blackfire PHP is not being installed? If I install it - along with the agent - manually, nothing works either.

Can you provide the exact steps you have done to install it manually.

Thanks for replying.
The steps are as follows:

Copied compose/docker-compose.override.yml-blackfire to docker-compose.override.yml in the Devilbox root.
Added the following to the .env file for my Devilbox root:

BLACKFIRE_SERVER_ID=myid
BLACKFIRE_SERVER_TOKEN=mytoken
#BLACKFIRE_SERVER=1.12.0
#BLACKFIRE_SERVER=1.13.0
#BLACKFIRE_SERVER=1.14.0
#BLACKFIRE_SERVER=1.14.1
#BLACKFIRE_SERVER=1.15.0
#BLACKFIRE_SERVER=1.16.0
#BLACKFIRE_SERVER=1.17.0
#BLACKFIRE_SERVER=1.17.1
#BLACKFIRE_SERVER=1.18.0
BLACKFIRE_SERVER=latest

Restarted Docker and fired up Devilbox with the following command: docker-compose up -d bind httpd php mysql memcd blackfire
Installed the Blackfire Chrome extension
Navigated to my localhost Devilbox project, and clicked the red "Profile" button in the Blackfire extension.
Received the following Blackfire error: "Probe not found, invalid signature."

Please let me know if there's anything else you need in order to debug it. Thank you.

@runedalton can you check out the blackfire branch and see if it now works: https://github.com/cytopia/devilbox/pull/457


Serial port does not seem to be created when using VMWare Fusion 6.0.4 and Vagrant 1.6.3

This is an odd issue. If I move the serial port vmx properties to where memory and cpus are being set, it works as expected.

Moved to https://github.com/coreos/bugs/issues/1370


Added ElasticCloud logging

This introduces two new extension methods:

UseElasticCloud(string cloudId, string apiKey)
UseElasticCloud(string cloudId, string username, string password)

Breaking change:

Removed NodeUris from the ElasticsearchLoggerOptions
Added new ShipTo class which encloses the previous NodeUris

I am not 100% sure if this is what you want/need, but it works fine for me.
Tested on a local ElasticSearch instance using .AddElasticsearch().
Tested on elastic cloud using .AddElasticCloud(cloudId, username, password)
Tested on elastic cloud using .AddElasticCloud(cloudId, apiKey)
The ApiKey has to come in correctly. So the base64'd "ApiKey.Id + colon + ApiKey.Key".
Please let me know if you need anything to be changed.

:grey_exclamation: Build Aborted

The PR is not allowed to run in the CI yet

Expand to view the summary

Build stats

Build Cause: [Pull request #98 opened]

Reason: The PR is not allowed to run in the CI yet

Start Time: 2020-07-16T14:01:51.555+0000

Duration: 3 min 9 sec

Commit: ae0fd82fe402a2257737b0279deb10b94f712ba9

Steps errors
Expand to view the steps failures

Name: Load a resource file from a shared library

Description:

Duration: 0 min 0 sec

Start Time: 2020-07-16T14:04:56.912+0000

log

Name: Error signal

Description: githubPrCheckApproved: The PR is not allowed to run in the CI yet. (Only users with write permission

Duration: 0 min 0 sec

Start Time: 2020-07-16T14:04:56.957+0000

log

Log output
Expand to view the last 100 lines of log output

[2020-07-16T14:04:32.906Z]  > git init /var/lib/jenkins/workspace/gent-dotnet_ecs-dotnet-mbp_PR-98 # timeout=10
[2020-07-16T14:04:32.971Z] Fetching upstream changes from git@github.com:elastic/ecs-dotnet.git
[2020-07-16T14:04:32.972Z]  > git --version # timeout=10
[2020-07-16T14:04:32.980Z] using GIT_SSH to set credentials GitHub user @elasticmachine SSH key
[2020-07-16T14:04:33.009Z]  > git fetch --no-tags --progress -- git@github.com:elastic/ecs-dotnet.git +refs/heads/*:refs/remotes/origin/* # timeout=15
[2020-07-16T14:04:33.855Z] Cleaning workspace
[2020-07-16T14:04:33.876Z] Pruning obsolete local branches
[2020-07-16T14:04:34.577Z] Merging remotes/origin/master commit 370a68e26b8b57892f251ae425604e8a19b65903 into PR head commit ae0fd82fe402a2257737b0279deb10b94f712ba9
[2020-07-16T14:04:34.845Z] Merge succeeded, producing 9c23b9a60cd637e0687c5923b71186c1b6c748f7
[2020-07-16T14:04:34.845Z] Checking out Revision 9c23b9a60cd637e0687c5923b71186c1b6c748f7 (PR-98)
[2020-07-16T14:04:33.821Z]  > git config remote.origin.url git@github.com:elastic/ecs-dotnet.git # timeout=10
[2020-07-16T14:04:33.832Z]  > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
[2020-07-16T14:04:33.844Z]  > git config remote.origin.url git@github.com:elastic/ecs-dotnet.git # timeout=10
[2020-07-16T14:04:33.855Z]  > git rev-parse --verify HEAD # timeout=10
[2020-07-16T14:04:33.862Z] No valid HEAD. Skipping the resetting
[2020-07-16T14:04:33.863Z]  > git clean -fdx # timeout=10
[2020-07-16T14:04:33.879Z] Fetching upstream changes from git@github.com:elastic/ecs-dotnet.git
[2020-07-16T14:04:33.880Z] using GIT_SSH to set credentials GitHub user @elasticmachine SSH key
[2020-07-16T14:04:33.885Z]  > git fetch --no-tags --progress --prune -- git@github.com:elastic/ecs-dotnet.git +refs/pull/98/head:refs/remotes/origin/PR-98 +refs/heads/master:refs/remotes/origin/master # timeout=15
[2020-07-16T14:04:34.584Z]  > git config core.sparsecheckout # timeout=10
[2020-07-16T14:04:34.599Z]  > git checkout -f ae0fd82fe402a2257737b0279deb10b94f712ba9 # timeout=15
[2020-07-16T14:04:34.667Z]  > git remote # timeout=10
[2020-07-16T14:04:34.680Z]  > git config --get remote.origin.url # timeout=10
[2020-07-16T14:04:34.685Z] using GIT_SSH to set credentials GitHub user @elasticmachine SSH key
[2020-07-16T14:04:34.689Z]  > git merge 370a68e26b8b57892f251ae425604e8a19b65903 # timeout=10
[2020-07-16T14:04:34.835Z]  > git rev-parse HEAD^{commit} # timeout=10
[2020-07-16T14:04:34.845Z]  > git config core.sparsecheckout # timeout=10
[2020-07-16T14:04:34.856Z]  > git checkout -f 9c23b9a60cd637e0687c5923b71186c1b6c748f7 # timeout=15
[2020-07-16T14:04:38.595Z] Commit message: "Merge commit '370a68e26b8b57892f251ae425604e8a19b65903' into HEAD"
[2020-07-16T14:04:38.595Z] First time build. Skipping changelog.
[2020-07-16T14:04:38.595Z] Cleaning workspace
[2020-07-16T14:04:38.595Z]  > git rev-parse --verify HEAD # timeout=10
[2020-07-16T14:04:38.601Z] Resetting working tree
[2020-07-16T14:04:38.602Z]  > git reset --hard # timeout=10
[2020-07-16T14:04:38.698Z]  > git clean -fdx # timeout=10
[2020-07-16T14:04:38.736Z]  > git --version # timeout=10
[2020-07-16T14:04:38.745Z] fatal: bad object b31ef20c542e25648b10129d07861c870a134b3f
[2020-07-16T14:04:39.423Z] Masking supported pattern matches of $JOB_GCS_BUCKET or $NOTIFY_TO
[2020-07-16T14:04:39.482Z] Timeout set to expire in 1 hr 0 min
[2020-07-16T14:04:39.506Z] The timestamps step is unnecessary when timestamps are enabled for all Pipeline builds.
[2020-07-16T14:04:39.730Z] [INFO] Number of builds to be searched 10
[2020-07-16T14:04:39.857Z] [INFO] 'shallow' is forced to be disabled when running on PullRequests
[2020-07-16T14:04:39.878Z] Running in /var/lib/jenkins/workspace/gent-dotnet_ecs-dotnet-mbp_PR-98/src/go.elastic.co/apm/ecs-dotnet
[2020-07-16T14:04:39.913Z] [INFO] gitCheckout: Checkout SCM PR-98 with some customisation.
[2020-07-16T14:04:39.943Z] [INFO] Override default checkout
[2020-07-16T14:04:40.001Z] Sleeping for 10 sec
[2020-07-16T14:04:50.158Z] using credential f6c7695a-671e-4f4f-a331-acdce44ff9ba
[2020-07-16T14:04:50.219Z] Cloning the remote Git repository
[2020-07-16T14:04:50.233Z] Cloning repository git@github.com:elastic/ecs-dotnet.git
[2020-07-16T14:04:50.262Z]  > git init /var/lib/jenkins/workspace/gent-dotnet_ecs-dotnet-mbp_PR-98/src/go.elastic.co/apm/ecs-dotnet # timeout=10
[2020-07-16T14:04:50.273Z] Fetching upstream changes from git@github.com:elastic/ecs-dotnet.git
[2020-07-16T14:04:50.274Z]  > git --version # timeout=10
[2020-07-16T14:04:50.281Z] using GIT_SSH to set credentials GitHub user @elasticmachine SSH key
[2020-07-16T14:04:50.287Z]  > git fetch --tags --progress -- git@github.com:elastic/ecs-dotnet.git +refs/heads/*:refs/remotes/origin/* # timeout=10
[2020-07-16T14:04:51.022Z]  > git config remote.origin.url git@github.com:elastic/ecs-dotnet.git # timeout=10
[2020-07-16T14:04:51.715Z] Checking out Revision ae0fd82fe402a2257737b0279deb10b94f712ba9 (origin/PR-98)
[2020-07-16T14:04:51.773Z] Commit message: "Elasticsearch.Extensions.Logging: Added ElasticCloud logging"
[2020-07-16T14:04:51.773Z] First time build. Skipping changelog.
[2020-07-16T14:04:51.787Z]  > git --version # timeout=10
[2020-07-16T14:04:51.795Z] fatal: bad object b31ef20c542e25648b10129d07861c870a134b3f
[2020-07-16T14:04:51.027Z]  > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
[2020-07-16T14:04:51.037Z]  > git config remote.origin.url git@github.com:elastic/ecs-dotnet.git # timeout=10
[2020-07-16T14:04:51.048Z] Fetching upstream changes from git@github.com:elastic/ecs-dotnet.git
[2020-07-16T14:04:51.049Z] using GIT_SSH to set credentials GitHub user @elasticmachine SSH key
[2020-07-16T14:04:51.053Z]  > git fetch --tags --progress -- git@github.com:elastic/ecs-dotnet.git +refs/pull/98/head:refs/remotes/origin/PR-98 +refs/heads/master:refs/remotes/origin/master # timeout=10
[2020-07-16T14:04:51.705Z]  > git rev-parse origin/PR-98^{commit} # timeout=10
[2020-07-16T14:04:51.715Z]  > git config core.sparsecheckout # timeout=10
[2020-07-16T14:04:51.719Z]  > git checkout -f ae0fd82fe402a2257737b0279deb10b94f712ba9 # timeout=10
[2020-07-16T14:04:52.761Z] Masking supported pattern matches of $GIT_USERNAME or $GIT_PASSWORD
[2020-07-16T14:04:53.373Z] + git fetch<EMAIL_ADDRESS>+refs/pull/*/head:refs/remotes/origin/pr/*
[2020-07-16T14:04:54.017Z] Archiving artifacts
[2020-07-16T14:04:54.734Z] + git rev-parse HEAD
[2020-07-16T14:04:55.114Z] + git rev-parse HEAD
[2020-07-16T14:04:55.442Z] + git rev-parse origin/pr/98
[2020-07-16T14:04:55.493Z] [INFO] githubEnv: Found Git Build Cause: pr
[2020-07-16T14:04:55.730Z] Masking supported pattern matches of $GITHUB_TOKEN
[2020-07-16T14:04:56.591Z] [WARN] githubApiCall: The REST API call https://api.github.com/repos/elastic/ecs-dotnet/pulls/98/reviews return 0 elements
[2020-07-16T14:04:56.650Z] [INFO] githubPrCheckApproved: Title: Added ElasticCloud logging - User: btastic - Author Association: FIRST_TIME_CONTRIBUTOR
[2020-07-16T14:04:56.974Z] ERROR: githubPrCheckApproved: The PR is not allowed to run in the CI yet
[2020-07-16T14:04:56.975Z] ERROR: githubPrCheckApproved: The PR is not allowed to run in the CI yet. (Only users with write permissions can do so.)
[2020-07-16T14:04:57.049Z] [INFO] Let's stop build #1. The PR is not allowed to run in the CI yet
[2020-07-16T14:04:57.071Z] Sleeping for 5 sec
[2020-07-16T14:04:58.152Z] Stage "Sanity checks" skipped due to earlier failure(s)
[2020-07-16T14:04:58.233Z] Stage "Parallel" skipped due to earlier failure(s)
[2020-07-16T14:04:58.331Z] Stage "Linux" skipped due to earlier failure(s)
[2020-07-16T14:04:58.343Z] Stage "Windows" skipped due to earlier failure(s)
[2020-07-16T14:04:58.379Z] Failed in branch Linux
[2020-07-16T14:04:58.421Z] Stage "Windows" skipped due to earlier failure(s)
[2020-07-16T14:04:58.515Z] Failed in branch Windows
[2020-07-16T14:04:58.639Z] Stage "Release" skipped due to earlier failure(s)
[2020-07-16T14:04:58.675Z] Stage "Release" skipped due to earlier failure(s)
[2020-07-16T14:04:58.752Z] Stage "Release" skipped due to earlier failure(s)
[2020-07-16T14:04:58.828Z] Stage "Release" skipped due to earlier failure(s)
[2020-07-16T14:04:58.904Z] Stage "Release" skipped due to earlier failure(s)
[2020-07-16T14:04:59.263Z] Running on Jenkins in /var/lib/jenkins/workspace/gent-dotnet_ecs-dotnet-mbp_PR-98
[2020-07-16T14:04:59.560Z] [INFO] getVaultSecret: Getting secrets
[2020-07-16T14:04:59.641Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID
[2020-07-16T14:05:00.432Z] + chmod 755 generate-build-data.sh
[2020-07-16T14:05:00.432Z] + ./generate-build-data.sh https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-dotnet/ecs-dotnet-mbp/PR-98/ https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-dotnet/ecs-dotnet-mbp/PR-98/runs/1 ABORTED 188606
[2020-07-16T14:05:00.983Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-dotnet/ecs-dotnet-mbp/PR-98/runs/1/steps/?limit=10000 -o steps-info.json


updated access modifiers rule to be more specific

This came up yesterday during work with @MichaelCampbell and @htinlinn, and I think we agreed that this is preferable, so I decided to update our access modifier rule to qualify for this.
@paulmiard @ThibaultKlein

:+1:

:+1:


Allow customFiles to be used without custom template

Currentlycontroller.customFiles cannot be used unless at least one of Values.controller.haproxy.enabled .Values.controller.template .Values.controller.templateFile .Values.controller.extraVolumeMounts is set, which i think is a bug since this option should be usable even without any of the other settings listed above, this PR will fix that.

Good catch thanks. Merging now.


http2 and ssl for the api

just requires the cli-deploy to be adjusted to add self signed certs... or should the user just provide certs?

Since the CLI deploy is a quick installer I think self signed certs might be easier. Lets encrypt would be nice but can be added in a future ticket.

this is good to go now. merging this.


[Event Request] Codeunit 40 LogInManagement - local procedure LogInEnd()

Describe the request
local procedure LogInEnd()
var
    UserSetup: Record "User Setup";
    UserTimeRegister: Record "User Time Register";
    LogOutDate: Date;
    LogOutTime: Time;
    Minutes: Integer;
    UserSetupFound: Boolean;
    RegisterTime: Boolean;
begin
    OnBeforeLogInEnd(LogInDate, LogInTime); //CustPub
    if LogInDate = 0D then
        exit;

    if LogInWorkDate <> 0D then
        if LogInWorkDate = LogInDate then

[IntegrationEvent(false, false)]
local procedure OnBeforeLogInEnd(var LogInDate: Date; var LogInTime: Time) //CustPub
begin
end;

Additional context
Publisher request marked with //CustPub tag.Internal work item: AB#494011

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 14693.


Feature/circle ci setup

Describe your PR
Sets up a basic Circle CI workflow to run Cypress integration tests to work with forked PR's. It's not required for merging yet since the tests aren't passing. (a11y and navigation tests to fix)
Steps to test

Check https://app.circleci.com/pipelines/github/Rebuild-Black-Business/RBB-Website

Additional notes
Will be changing it over to only do builds on PR's instead of any commit ever after this.

@llexical I agree that having failing tests is bad, but these tests are already in the repo and failing. I was wanting to get this done in multiple parts that way it's not so dependent on one person.
Someone else could easily work on improving the tests.
With that said though, the main reason for test failures is a11y color contrast reasons, and that's going to require feedback from design (already let them know about it).  I have found a few fixes for some of the other errors but wanted to do it as it's own PR so it's easier to review. Unless we .skip the a11y tests we wouldn't be able to fix it now, and I think that's worse than having failing tests because they are less likely to ever be fixed. Thoughts?

We could set the tests to disable the color contrast rule, but theres not a great way to enforce that we un-disable it in the future. We could make a GitHub issue for it but that's the best idea I can think of.
{
    rules: { 'color-contrast': { enabled: false } },
}

@llexical I agree that having failing tests is bad, but these tests are already in the repo and failing. I was wanting to get this done in multiple parts that way it's not so dependent on one person.
Someone else could easily work on improving the tests.
With that said though, the main reason for test failures is a11y color contrast reasons, and that's going to require feedback from design (already let them know about it). I have found a few fixes for some of the other errors but wanted to do it as it's own PR so it's easier to review. Unless we .skip the a11y tests we wouldn't be able to fix it now, and I think that's worse than having failing tests because they are less likely to ever be fixed. Thoughts?

I would rather skip than have failing tests that we ignore and merge anyway. If you have failing tests then people will ignore them and they may as well not be there, often they mean people will not check the tests to see if the ones normally passing do and so they assume and it gives false confidence. Also normalising a failing test does not make them more likely to get fixed, I've seen teams ignore them for years xD.
If we never make the tests work then thats a different issue. Either we don't care about the tests and they are not useful so we don't need them or we do and so we should prioritise fixing them. Theres no point having tests we are not committing to maintaining or we may as well not have any at all.


refactor: update settings-module template

module update introduces local branch rules for main and development

closing, modules will be updated again if required.


Failed to request message, please check your network from docker

Describe the bug
Failed to request message, please check your network.、
公网可以使用sqlchat，但是用docker起就会出现这样的问题
To reproduce
这是什么情况
Additional context
No response

Docker image updated. Please try again


Can you post the automatic data conversion file?

As the title said. And what is label "X O T" mean in the JSON files. Please post your data conversion file.

please refer to the previous issue #3 for the data conversion. And for the labels, you can check the official website of DBDC3.


typo in _strip_string?

Description
There appears to be a typo in the _strip_string function of the math_equivalence.py file, where an unnecessary escape character is used with the percent sign. The code uses string.replace("\%", "") when it seems to me that string.replace("%", "") was intended. I'm not 100% certain whether this behavior is unintentional but currently is_equiv("50%", "50") == False. The current code also throws a warning for python 3.11.
https://github.com/hendrycks/math/blob/357963a7f5501a6c1708cf3f3fb0cdf525642761/modeling/math_equivalence.py#L104
Suggestion
string = string.replace("\%", "")
->
string = string.replace("%", "")

Just did some research for 5 mins
Everything in the data should correctly normalized since they all seem to be formatted like 50\\%.
The only difference due to this is when the model predicts 50% instead of 50 or 50\\% because is_equiv("50\\%", "50%") == False. There are 51 % signs in the test set(~1%), and the results are only impacted if the model acts in a certain way.


Blockchain Service Down

We keep getting below error when trying to login/register for cpweb application. [deployed locally and connecting via localhost - connected to bluemix by updating mycred.json.
]
For most of time today, we got this error. Is there any maintenance going on right now?
"Waiting on the node server to open up so we can talk to the blockchain. This app is likely still starting up. Check the server logs if this message does not go away in 1 minute.
This application cannot run without the blockchain network"

@pauljoyhere  - can you post (or send to me directly) the ID for your network (or even one of your hostnames)?

eaa9c17d-b756-4dec-a8e0-6ebe12f07228

It added few blocks, then stopped working for about 3 + hours.

has anything improved? its always a good idea to delete and recreate the service if you feel you have unexpected results.
are you using a unmodified cp-web?

I'm closing this issue due to inactivity.  @pauljoyhere If you are still having issues, just let us know.  We have made improvements to the service to increase stability and performance, but we have noticed some connectivity issues when using the fabric SDK on Bluemix since pushing out this update.  I'll update #50 when we have a fix.


Numbers being appended to the TypeScript interface names when using the same $ref multiple times

Hey there,
I’m trying to resolve some $refs in a YML model that looks like this:
type: object
required:
  - title
properties:
  identifier:
    type: string
  title:
    $ref: "TranslatableField.yml"
    example:
      de: Konzert
      en: concert
  displayName:
    $ref: "TranslatableField.yml"
  description:
    $ref: "TranslatableField.yml"
    example:
      de: Eine Beschreibung
      en: Some description

TranslatableField.yml looks like this:
type: object
additionalProperties:
  type: string
description: |-
  A string that can be translated into multiple languages, e.g. { "de": "Konzert", "en": "concert" }
example:
  de: Konzert
  en: concert

As you can see, I’m referencing TranslatableField multiple times. I would expect my TypeScript interface to look like this after calling compile():
export interface Model {
    title: TranslatableField
    displayName?: TranslatableField
    description?: TranslatableField
}

… but what I get is this:
export interface Model {
    title: TranslatableField
    displayName?: TranslatableField1
    description?: TranslatableField2
}

Note the extra numbers at the end of TranslatableField. With declareExternallyReferenced: false this breaks the generated TypeScript file, because that’s an invalid model name that cannot be found/imported from anywhere. I’d like to reuse the same name (TranslatableField without the number) for all fields.
Here’s a full example: https://codesandbox.io/p/sandbox/json-schema-to-typescript-test-8n5d9s
Is there any way to prevent these extra number suffixes, e.g. with some configuration? 🤔
I appreciate any hints or ideas!
References

https://github.com/bcherny/json-schema-to-typescript/issues/193

This does not seem to be an issue with json-schema-ref-parser - the json schema returned by the ref parser is valid, and does not append the names. This looks like an issue in the library you are using.


BUG - FORMULA SQL IS LOWERCASeD

Are you a current Fivetran customer?
Yes

David , Artica
Describe the bug
The formula SQL is lower cased so for example:
CASE WHEN field = 'Bob' THEN 1 ELSE 0 END as isBob
would become
case when field = 'bob' then 1 else 0 end as isbob
And therefore fail to match Bob correctly.
Steps to reproduce
Try a case statement Salesforce formula that is case-sensitive
See line causing this here: https://github.com/fivetran/dbt_salesforce_formula_utils/blob/main/macros/sfdc_get_formula_column_values.sql#L26
Expected behavior
I would expect it not to change CASE statements inside sql formulas.
Package Version

copy packages.yml here

Warehouse

[ ] BigQuery
[ ] Redshift
[ X] Snowflake
[ ] Postgres
[ ] Databricks
[ ] Other (provide details below)

Are you interested in contributing to this package?

[ ] Yes, I can do this and open a PR for your review.
[X ] Possibly, but I'm not quite sure how to do this. I'd be happy to do a live coding session with someone to get this fixed.
[ ] No, I'd prefer if someone else fixed this.  I don't have the time and/or don't know what the root cause of the problem is.

Unrelated - is there a Fivetran opinion on how to use this with your other packages? https://github.com/fivetran/dbt_salesforce_source
They seem somewhat incompatible / conflicting in that the other packages don't know about "fivetran_formula"

Hey @dfagnan, thanks so much for creating this issue!
I actually just encountered a similar issue where a convert_timezone function was not working because I lower case the fields and the timezone is not able to find a match. I believe the snippet of code you pointed out is right on track with where I am thinking we should make some adjustments to ensure we do not change the casing.
Since you helped point this out, it would be great if you wanted to open a PR for this quick fix. If you wanted to make the small adjustment you highlighted and open the PR on this branch, then I can help debug and test this further to ensure there are no other changes need. Let me know if you have any question.

Unrelated - is there a Fivetran opinion on how to use this with your other packages? https://github.com/fivetran/dbt_salesforce_source
They seem somewhat incompatible / conflicting in that the other packages don't know about "fivetran_formula"

^ That is a great question! While the two seem unrelated, you actually can use the two package together. The salesforce_source package by default looks at the raw tables synced by Fivetran to generate the staging and then final models. However, if you wanted the source package to look at the output of the models generated via this macro you could simply override the variables in your dbt_project.yml to point to the new models generated from this macro. An example of the override would look like the below config:
vars:
  salesforce_source:
    account: "{{ ref('account_formula_view') }}"
    opportunity: "{{ ref('opportunity_formula_view') }}"
    user: "{{ ref('user_formula_view') }}"
    user_role: "{{ ref('user_role_formula_view') }}"

The salesforce_source package would then reference these models when running the downstream package models.
You make a great point though that this is not entirely clear. I will make a note for myself and the team to put together some supporting docs to show how this may be possible. Thanks for the helpful question! 😄

Hi @dfagnan this issue should be resolved in the latest release of the dbt package! Let me know if you continue experiencing the casing issue.
Thanks!

Thanks @fivetran-joemarkiewicz - I don't think I had any issues related to this after updating. I regret I wasn't more helpful on this one but appreciate your support.


Add Provisioning ability for IBM Cloud Self-managed

extending the provisionin/deprovisioning tasks to work with IBM Cloud

IBM Cloud provisioning/deprovisioning tested from local multiple times: PASSED. Cannot test on CI yet because of missing pkgs
Other cloud provider regression testing provisioning/deprovisionin: coming soon


Feature appchain erc20 transfer

Before merge, We have to verify that AppChain ERC20 can be traded successfully.


Standardise docstring content and formatting

I noticed today that our docstrings are a bit inconsistent. There are guidelines here, which we should try and follow:
https://docs.julialang.org/en/v1/manual/documentation/
One of the easier things to fix will be formatting, using backticks like this instead of quote marks is visually helpful. Restructuring, adding examples etc will take a bit more time.

As part of this, and with reference to point 6 in the above link, we may want to use self-contained docstring examples as tests, so we can be sure they are always up-to-date.

I had a look through the API section (which, if I remember corrrectly, was where some of the formatting was inconsistent) and it seems to have been fixed at some point.


default environment variables - where can they be used?

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/actions/learn-github-actions/variables#default-environment-variables
What part(s) of the article would you like to see updated?
the section on default environment variables. it says

The default environment variables that GitHub sets are available to every step in a workflow.

but when I try for instance to use such a variable as input to a step using a composite action, as in
      - name: Fetch job html
        uses: ./.github/actions/job_html_url
        with:
          job_name: ${{ env.GITHUB_JOB }}

the passed input is the empty string.
I would like to see more specifically where in a step these env vars can be used, as i would expect that they can be accessed using the env context in expressions, but apparently this is not the case. not even a step with
        run: echo ${{ env.GITHUB_JOB }}

works! it seems they are not accessible through the env context at all :thinking:
Additional information
No response

@valentin-krasontovitsch Thank you for opening an issue and linking it to your PR! ✨

we have a PR, which is waiting for review

we still have a PR, which is waiting for review


Improve documentation

Reference Issues/PRs
Some of #240
What does this implement/fix? Explain your changes.

Document attributes in Models
Explain what pairplot is doing better
fix MASE.fit_transform docs

Any other comments?

Some ambiguity with model selection based on whether or not y is passed, if it is, should the attribute vertex_assignments_ just be equal to y? (a la mug2vec embedding dimensions)

Codecov Report

Merging #242 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #242   +/-   ##
=======================================
  Coverage   86.14%   86.14%
=======================================
  Files          33       33
  Lines        1935     1935
=======================================
  Hits         1667     1667
  Misses        268      268

Impacted Files
Coverage Δ

graspy/models/sbm.py
99.37% <ø> (ø)
:arrow_up:

graspy/embed/mase.py
100% <ø> (ø)
:arrow_up:

graspy/models/er.py
100% <ø> (ø)
:arrow_up:

graspy/models/rdpg.py
100% <ø> (ø)
:arrow_up:

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 4308b95...df6df4c. Read the comment docs.

looks good barring the merge conflict


boundary effects in template_matching

fix shift within template matchin function

The returned values are correct. The threshold values seem shifted, but they are not. In fact, the event is symmetrically centered around peaks in the threshold curve, i.e. to get the event start, one needs to shift by half the kernel size in negative direction!


How to use other UserStores?

I have identityserver4 setup and was able to get your library to support authenticating against ActiveDirectory. This works when using InMemory UserStore but what I am looking to do is authenticate against ActiveDirectory and then store the user in a database specific to my application. My ultimate objective is to get this working with AspNet.Identity.MongoDbCore but I'm not sure how to even get this working with AspNetCore's built-in EF provider. I am looking for guidance on how to use your library for authentication only but not as the userstore?

Hi, sorry for the delay.
Regarding the IdentityServer4, you have a setup for the official storage. This plugin/extension is IS configuration in order to validate the credentials towards a LDAP server. The current userstore is configurable regarding the caching (Redis/InMemory). It can then be used in conjunction with the IS database configuration.
If you want to implement the user caching within mongo (which is maybe not the best decision due to performance), you can base yourself on the Redis implementation.
For the IS4 with MongoDb instead of Postgres or MS SQL, please refer to the official IS4 site or stackoverflow questions.
Thank you.

Sorry @Nordes , just in case i did not understand what you're talkin about, what if i want to use is4 with a sql server (EF) and with ldap plugin, can that be done ?


fips: allow to customize provider vendor name

FIPS providers need to specify identifiable names and versions. Allow to customize the fips provider name prefix, via VERSION.dat which already allows to customize version & buildinfo. With this patch in-place it removes the need of patching code to set customized provider name.
E.g. echo FIPSVENDOR=ACME >> VERSION.dat, results in
$ OPENSSL_CONF=fips-and-base.cnf ../util/wrap.pl ../apps/openssl list -providers --verbose
Providers:
  base
    name: OpenSSL Base Provider
    version: 3.4.0
    status: active
    build info: 3.4.0-dev
    gettable provider parameters:
      name: pointer to a UTF8 encoded string (arbitrary size)
      version: pointer to a UTF8 encoded string (arbitrary size)
      buildinfo: pointer to a UTF8 encoded string (arbitrary size)
      status: integer (arbitrary size)
  fips
    name: ACME OpenSSL FIPS Provider
    version: 3.4.0
    status: active
    build info: 3.4.0-dev
    gettable provider parameters:
      name: pointer to a UTF8 encoded string (arbitrary size)
      version: pointer to a UTF8 encoded string (arbitrary size)
      buildinfo: pointer to a UTF8 encoded string (arbitrary size)
      status: integer (arbitrary size)
      security-checks: integer (arbitrary size)
      tls1-prf-ems-check: integer (arbitrary size)
      drbg-no-trunc-md: integer (arbitrary size)

It was a note for the @openssl/omc ...

Placing a hold on this until internal discussions are held.

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

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

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

yes.

@xnox apologies for the delay on this. As @paulidale notes there are some trademark issues here. We are able to allow renaming, but believe it should be of the form:
<Vendor Name> Provider for OpenSSL

That is to say can be optionally inserted, but with the fixed text "Provider for OpenSSL" trailing it. Are you able to update your PR to reflect that?

Here is updated version
Default build:
$ ./Configure enable-fips && make -j10
$ ./util/wrap.pl -fips ./apps/openssl list -providers
Providers:
  base
    name: OpenSSL Base Provider
    version: 3.4.0
    status: active
  fips
    name: OpenSSL FIPS Provider
    version: 3.4.0
    status: active

Vendor build:
$ echo FIPSVENDOR=ACME >> VERSION.dat
$ ./Configure enable-fips && make -j10
$ ./util/wrap.pl -fips ./apps/openssl list -providers
Providers:
  base
    name: OpenSSL Base Provider
    version: 3.4.0
    status: active
  fips
    name: ACME FIPS Provider for OpenSSL
    version: 3.4.0
    status: active

@levitte any thoughts on this?

Rebasing to resolve merge conflict with #25166

Reconfirm @nhorman please?

Ack, approval holds

Ack, approval holds

Merged, thanks for following through on this.


RequestAnimationFrame webkit polyfill ios_saf 6

Allow webkit polyfill for requestAnimationFrame on all iOS6 safari browsers, as opposed to just versions greater than 6.1

Hmm, according to caniuse iOS added support for raf in 6.1, so this should be <= 6.0.  What tests have you done?

@triblondon this is the polyfill for the prefixed one — which is only needed in iOS 6.1

I believe this only applies to the webkit prefixed polyfill — which for Safari applies to 6.0 and 6.1 only

OK, understood.
What testing have you done?

@laurieboyes has been coordinating this and i believe he's off today.  i suspect this can wait until he's back.

Cheers for looking at this. I couldn't spot anywhere within the current testing that I could slot in an automated test for this but please let me know if I'm missing anything.
Manual testing so far has involved looking at the polyfill.js file on an iOS6 device and noting that raf was indeed being alias polyfilled. I was putting faith in the fact that the change was so minor but this degree of testing seems fairly pitiful now that I see it written down so will do more thorough testing and report back.

Test results
/test/director?feature=requestAnimationFrame&mode=targeted
Carried on on iPad2 with Safari iOS 6.0
Before:

After

:+1:


Added "trim object names" rule

Add a rule that checks if any objects have leading or trailing spaces in their names, as this is most likely unintentional (i.e. when copying an object, Tabular Editor appends " 1" to the name, and deleting just the "1" leaves a trailing space in the name).
CC @m-kovalsky

This is great, thanks Daniel. I will merge this into the next version of BPA!

This rule is in 1.2.5. Thanks!


What are these commands for?

Extension version:
VSCode Version: 1.95.2
OS: windows 11
Repository Clone Configuration (single repository/fork of an upstream repository): signle repository
Github Product (Github.com/Github Enterprise version x.x.x): Github.com

Steps to Reproduce:

Any of these commands, even if I hover over the issue in the window of this extension, it doesn't care

They're used for the menu items in the issues view. It's not possible to create keyboard shortcuts for tree items like this.


[FEATURE] Moved initialization of field-descriptors before init of list-builder

… in accounts cget action

ack


shcr refactor code

Adjustments to work around data quality issues, plus commenting code to aid comprehension.

Heroic efforts @christodd-nhsx


nodeclaims deleted but not getting reason for delete

Description
Nodeclaims deleted without and pdbs are not considered . need to know reason why nodeclaims deleted
here is the logs i got for nodeclaim deletion:
{"level":"INFO","time":"2024-09-26T13:34:44.210Z","logger":"controller","message":"annotated nodeclaim","commit":"62a726c","controller":"nodeclaim.termination","controllerGroup":"karpenter.sh","controllerKind":"NodeClaim","NodeClaim":{"name":"marketplace-hgbqt"},"namespace":"","name":"marketplace-hgbqt","reconcileID":"0da1aeb2-a5cf-4557-afa9-b39d7225d9d0","Node":{"name":"ip-10-0-97-41.ap-south-1.compute.internal"},"provider-id":"aws:///ap-south-1c/i-0bcf1f7224f0e82e4","karpenter.sh/nodeclaim-termination-timestamp":"2024-09-26T13:36:44Z"}
{"level":"INFO","time":"2024-09-26T13:34:44.441Z","logger":"controller","message":"tainted node","commit":"62a726c","controller":"node.termination","controllerGroup":"","controllerKind":"Node","Node":{"name":"ip-10-0-97-41.ap-south-1.compute.internal"},"namespace":"","name":"ip-10-0-97-41.ap-south-1.compute.internal","reconcileID":"e653dc3c-0f4f-43d8-a04b-77314ba38c88","taint.Key":"karpenter.sh/disrupted","taint.Value":"","taint.Effect":"NoSchedule"}
then deleted nodeclaim

What version of Karpenter are you using? What's the k8s version?

karpenter version : 1.0.1
k8s version: 1.30
Why don't we receive any logs indicating the reason when a NodeClaim is deleted due to node expiration or when a spot instance becomes unavailable?
How can we determine the reason for a NodeClaim deletion reasons in this case ??

Can you share nodePool, nodeClass, nodeClaim and a more complete set of logs?

We get the same issue; some of the nodeclaims have annotation karpenter.sh/nodeclaim-termination-timestamp, and when reach the termination timestamp, nodes are deleted. node didn't reach the expire time. and it is on-demand instance
here is one of nodeclaim's manifest

apiVersion: karpenter.sh/v1
kind: NodeClaim
metadata:
  annotations:
    compatibility.karpenter.k8s.aws/cluster-name-tagged: "true"
    compatibility.karpenter.k8s.aws/kubelet-drift-hash: "9225586735335466555"
    compatibility.karpenter.sh/v1beta1-kubelet-conversion: '{"maxPods":110}'
    karpenter.k8s.aws/ec2nodeclass-hash: "17044720421536988815"
    karpenter.k8s.aws/ec2nodeclass-hash-version: v3
    karpenter.k8s.aws/tagged: "true"
    karpenter.sh/nodeclaim-termination-timestamp: "2024-10-30T05:29:18Z"
    karpenter.sh/nodepool-hash: "2620790099938737011"
    karpenter.sh/nodepool-hash-version: v3
    karpenter.sh/stored-version-migrated: "true"
  creationTimestamp: "2024-10-30T02:18:26Z"
  deletionGracePeriodSeconds: 0
  deletionTimestamp: "2024-10-30T05:14:18Z"
  finalizers:
  - karpenter.sh/termination
  generateName: airflow-
  generation: 2
  labels:
    k8s.tubi.io/RancherRole: worker
    k8s.tubi.io/airflow: "true"
    k8s.tubi.io/worker_type: airflow
    karpenter.k8s.aws/instance-category: c
    karpenter.k8s.aws/instance-cpu: "16"
    karpenter.k8s.aws/instance-cpu-manufacturer: amd
    karpenter.k8s.aws/instance-ebs-bandwidth: "10000"
    karpenter.k8s.aws/instance-encryption-in-transit-supported: "true"
    karpenter.k8s.aws/instance-family: c6a
    karpenter.k8s.aws/instance-generation: "6"
    karpenter.k8s.aws/instance-hypervisor: nitro
    karpenter.k8s.aws/instance-memory: "32768"
    karpenter.k8s.aws/instance-network-bandwidth: "6250"
    karpenter.k8s.aws/instance-size: 4xlarge
    karpenter.sh/capacity-type: on-demand
    karpenter.sh/nodepool: airflow
    kubernetes.io/arch: amd64
    kubernetes.io/os: linux
    node.kubernetes.io/instance-type: c6a.4xlarge
    topology.k8s.aws/zone-id: usw2-az2
    topology.kubernetes.io/region: us-west-2
    topology.kubernetes.io/zone: us-west-2b
  name: airflow-p2kj5
  ownerReferences:
  - apiVersion: karpenter.sh/v1
    blockOwnerDeletion: true
    kind: NodePool
    name: airflow
    uid: 71a8322d-58d2-46fe-a55b-93c156224548
  resourceVersion: "5289051911"
  uid: 240351a5-af56-49be-9194-4bfaba57a7de
spec:
  expireAfter: 168h
  nodeClassRef:
    group: karpenter.k8s.aws
    kind: EC2NodeClass
    name: default
  requirements:
  - key: karpenter.k8s.aws/instance-family
    operator: In
    values:
    - c5
    - c6a
    - c6i
  - key: karpenter.k8s.aws/instance-size
    operator: In
    values:
    - 4xlarge
  - key: karpenter.sh/capacity-type
    operator: In
    values:
    - on-demand
  - key: karpenter.sh/nodepool
    operator: In
    values:
    - airflow
  - key: k8s.tubi.io/airflow
    operator: In
    values:
    - "true"
  - key: k8s.tubi.io/worker_type
    operator: In
    values:
    - airflow
  - key: k8s.tubi.io/RancherRole
    operator: In
    values:
    - worker
  - key: node.kubernetes.io/instance-type
    operator: In
    values:
    - c5.4xlarge
    - c6a.4xlarge
    - c6i.4xlarge
  resources:
    requests:
      cpu: 4230m
      memory: 7146Mi
      pods: "9"
  taints:
  - effect: NoSchedule
    key: k8s.tubi.io/airflow
    value: "true"
  terminationGracePeriod: 15m0s
status:
  allocatable:
    cpu: 15890m
    ephemeral-storage: 179Gi
    memory: 27381Mi
    pods: "110"
    vpc.amazonaws.com/pod-eni: "54"
  capacity:
    cpu: "16"
    ephemeral-storage: 200Gi
    memory: 30310Mi
    pods: "110"
    vpc.amazonaws.com/pod-eni: "54"
  conditions:
  - lastTransitionTime: "2024-10-30T02:28:29Z"
    message: ""
    reason: ConsistentStateFound
    status: "True"
    type: ConsistentStateFound
  - lastTransitionTime: "2024-10-30T04:23:31Z"
    message: NodePoolDrifted
    reason: NodePoolDrifted
    status: "True"
    type: Drifted
  - lastTransitionTime: "2024-10-30T02:23:12Z"
    message: ""
    reason: Initialized
    status: "True"
    type: Initialized
  - lastTransitionTime: "2024-10-30T02:18:28Z"
    message: ""
    reason: Launched
    status: "True"
    type: Launched
  - lastTransitionTime: "2024-10-30T02:23:12Z"
    message: ""
    reason: Ready
    status: "True"
    type: Ready
  - lastTransitionTime: "2024-10-30T02:21:58Z"
    message: ""
    reason: Registered
    status: "True"
    type: Registered
  imageID: ami-07897e5d530875b75
  lastPodEventTime: "2024-10-30T05:15:31Z"

karpenter version: 1.0.6
controller logs
{"level":"INFO","time":"2024-10-30T02:18:28.992Z","logger":"controller","message":"launched nodeclaim","commit":"6174c75","controller":"nodeclaim.lifecycle","controllerGroup":"karpenter.sh","controllerKind":"NodeClaim","NodeClaim":{"name":"airflow-p2kj5"},"namespace":"","name":"airflow-p2kj5","reconcileID":"4151ad84-3afe-491a-bc6a-45d09fe1aff4","provider-id":"aws:///us-west-2b/i-xxxxxxx","instance-type":"c6a.4xlarge","zone":"us-west-2b","capacity-type":"on-demand","allocatable":{"cpu":"15890m","ephemeral-storage":"179Gi","memory":"27381Mi","pods":"110","vpc.amazonaws.com/pod-eni":"54"}}
{"level":"INFO","time":"2024-10-30T02:21:58.316Z","logger":"controller","message":"registered nodeclaim","commit":"6174c75","controller":"nodeclaim.lifecycle","controllerGroup":"karpenter.sh","controllerKind":"NodeClaim","NodeClaim":{"name":"airflow-p2kj5"},"namespace":"","name":"airflow-p2kj5","reconcileID":"fe0a1cbb-d2db-41b9-8fd5-afeff7c38c4d","provider-id":"aws:///us-west-2b/i-xxxxxxx","Node":{"name":"ip-172-18-31-105.us-west-2.compute.internal"}}
{"level":"INFO","time":"2024-10-30T02:23:12.728Z","logger":"controller","message":"initialized nodeclaim","commit":"6174c75","controller":"nodeclaim.lifecycle","controllerGroup":"karpenter.sh","controllerKind":"NodeClaim","NodeClaim":{"name":"airflow-p2kj5"},"namespace":"","name":"airflow-p2kj5","reconcileID":"2984becf-6605-4f02-88cb-1589cfc0acef","provider-id":"aws:///us-west-2b/i-xxxxxxx","Node":{"name":"ip-172-18-31-105.us-west-2.compute.internal"},"allocatable":{"cpu":"15500m","ephemeral-storage":"174592944937","hugepages-1Gi":"0","hugepages-2Mi":"0","memory":"27959808Ki","pods":"110"}}
{"level":"INFO","time":"2024-10-30T05:14:18.369Z","logger":"controller","message":"annotated nodeclaim","commit":"6174c75","controller":"nodeclaim.termination","controllerGroup":"karpenter.sh","controllerKind":"NodeClaim","NodeClaim":{"name":"airflow-p2kj5"},"namespace":"","name":"airflow-p2kj5","reconcileID":"c90b4154-a252-4e3a-b88f-4458f0067350","Node":{"name":"ip-172-18-31-105.us-west-2.compute.internal"},"provider-id":"aws:///us-west-2b/i-xxxxxxx","karpenter.sh/nodeclaim-termination-timestamp":"2024-10-30T05:29:18Z"}
{"level":"INFO","time":"2024-10-30T05:30:22.043Z","logger":"controller","message":"deleted nodeclaim","commit":"6174c75","controller":"nodeclaim.termination","controllerGroup":"karpenter.sh","controllerKind":"NodeClaim","NodeClaim":{"name":"airflow-p2kj5"},"namespace":"","name":"airflow-p2kj5","reconcileID":"3243e713-0e24-4b50-9ffc-91c77a550006","Node":{"name":"ip-172-18-31-105.us-west-2.compute.internal"},"provider-id":"aws:///us-west-2b/i-xxxxxxx"}

Is it caused by the new feature terminationGracePeriod?

Just noticed this happening during the first karpenter startup after the v1 upgrade. I followed the v1 upgrade procedure, and it looks like all went smoothly. However, during the first startup karpenter taints nodes that are supposed to be disrupted only on 1st day of the month:
  spec:
    disruption:
      budgets:
      - duration: 164h
        nodes: "0"
        schedule: 0 4 * * 0
      - duration: 4h
        nodes: "10"
        schedule: 0 0 * * 0
      consolidateAfter: 0s
      consolidationPolicy: WhenEmptyOrUnderutilized

Karpenter logs show the normal startup without any errors, then it suddenly decides to taint the nodes:
{"level":"INFO","time":"2024-10-30T16:12:54.598Z","logger":"controller","message":"Starting workers","commit":"6174c75","controller":"nodeclaim.tagging","controllerGroup":"karpenter.sh","controllerKind":"NodeClaim","worker count":1}
{"level":"INFO","time":"2024-10-30T16:12:54.704Z","logger":"controller","message":"tainted node","commit":"6174c75","controller":"node.termination","controllerGroup":"","controllerKind":"Node","Node":{"name":"ip-10-16-15-204.eu-west-1.compute.internal"},"namespace":"","name":"ip-10-16-15-204.us-west-1.compute.internal","reconcileID":"7e76855c-9d0a-48ab-b0a1-2b163ec67e20","taint.Key":"karpenter.sh/disrupted","taint.Value":"","taint.Effect":"NoSchedule"}

I'm going to try increase the auto-generated value for the consolidateAfter: 0s to several minutes...

Would anyone be able to point to the line in the code that generates these messages?
"message":"tainted node"
"controller":"node.termination"
"taint.Key":"karpenter.sh/disrupted","taint.Value":"","taint.Effect":"NoSchedule"

I'm having difficulties finding these strings in the karpenter source code...

(Karpenter v1.0.6):
Similarly, I'm not happy with the Karpenter logs ... I think... "reason": "drifted" is pretty much the only information you get from that controller, WHAT out of the several drift sources caused the drift? Or am I missing something?
I guess... if the NodeClaims are the resources that contain the "coherent" status and events summarized in a useful way... the NodeClaims need to remain AFTER the node deletion has happened, or be archived somehow. When they're gone, the easily accessible information is also gone!
Right now, Karpenter seem to have too many blind spots for production confidence compared to the calmness and "it just works" nature of Cluster-Autoscaler.


Update wheel building workflow to include Python 3.11

This was initially successful for all but win32/Python 3.10:
https://github.com/grlee77/pywt/actions/runs/3028888975
Updating the pyproject.toml numpy pinnings for windows as in SciPy fixed the issue (non-windows cases were commented out in that commit):
https://github.com/grlee77/pywt/runs/8287429816?check_suite_focus=true
Aside from adding Python 3.11 this MR

removes all linux i686 builds
splits the Windows and MacOS build matrix into parallel actions
changed to using ubuntu-latest
some updates to NumPy pinnings in pyproject.toml

Not sure if we should also drop the universal2 wheels on MacOS?

Not sure if we should also drop the universal2 wheels on MacOS?

Yes please!

CI here didn't run the wheel builds, but assuming they were tested on your fork I think this is good to go modulo my one comment.

It had passed here. I cancelled some long running aarch64 cases that had passed in a previous test run.


java.lang.NullPointerException while scanning a dependency with org.owasp.dependencycheck 6.1.3

Describe the bug
Started getting Null pointer exception after bumping the org.owasp.dependencycheck from 6.1.1 to 6.1.3.
The exception is specifically occurring while analysing the latest stable version of pitest dependency 0.14.
Please find the below table to illustrate the issue:

S.NO
Dependencheck version
Pitest version
Result

1
6.1.1
0.12
works fine

2
6.1.1
0.14
works fine

3
6.1.3
0.12
works fine

4
6.1.3
0.14
Null Pointer Exception

Version of dependency-check used
org.owasp.dependencycheck: 6.1.3
gradlew: 6.8.3
java: 8
Log file
> Task :dependencyCheckAnalyze
Verifying dependencies for project companieshouse
Checking for updates and analyzing dependencies for vulnerabilities

An unexpected error occurred during analysis of '/Users/abhishekrajput/.gradle/caches/modules-2/files-2.1/org.pitest/pitest-junit5-plugin/0.14/d44159efa6807898d0a881bb6d0fb0f63a6f0ec2/pitest-junit5-plugin-0.14.jar' (CPE Analyzer): null

java.lang.NullPointerException
        at java.lang.String.endsWith(String.java:1449)
        at org.owasp.dependencycheck.analyzer.CPEAnalyzer.lambda$null$3(CPEAnalyzer.java:380)
        at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:174)
        at java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1556)
        at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
        at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
        at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
        at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
        at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
        at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
        at org.owasp.dependencycheck.analyzer.CPEAnalyzer.lambda$addMajorVersionToTerms$5(CPEAnalyzer.java:383)
        at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
        at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
        at java.util.HashMap$EntrySpliterator.forEachRemaining(HashMap.java:1699)
        at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
        at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
        at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
        at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
        at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
        at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
        at org.owasp.dependencycheck.analyzer.CPEAnalyzer.addMajorVersionToTerms(CPEAnalyzer.java:378)
        at org.owasp.dependencycheck.analyzer.CPEAnalyzer.determineCPE(CPEAnalyzer.java:279)
        at org.owasp.dependencycheck.analyzer.CPEAnalyzer.analyzeDependency(CPEAnalyzer.java:764)
        at org.owasp.dependencycheck.analyzer.AbstractAnalyzer.analyze(AbstractAnalyzer.java:131)
        at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:88)
        at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:37)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)

> Task :dependencyCheckAnalyze FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':dependencyCheckAnalyze'.
> Analysis failed.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.8.3/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 11s
2 actionable tasks: 1 executed, 1 up-to-date

Publishing a build scan to scans.gradle.com requires accepting the Gradle Terms of Service defined at https://gradle.com/terms-of-service. Do you accept these terms? [yes, no]

To Reproduce
Steps to reproduce the behaviour:

Clone the GitHub repo:
git clone https://github.com/abhisheksr01/spring-boot-microservice-best-practices.git

Checkout branch dependencychecknpe
created a separate branch specifically for this issue.
git checkout -t origin/dependencychecknpe

Execute dependency scan
./gradlew clean dependencyCheckAnalyze --scan

Expected behaviour
Should have executed successfully.
Additional context
In meantime, I was thinking if I can ignore this dependency maybe by adding it into suppression.xml.
But obviously, that's not the right place. Is there another way how can I ignore this dependency (something like the way .gitignore works).
Thanks,

This will be with the 6.1.4 release.

Thanks @jeremylong for quick response.
Just for my understanding the exception occurred because the latest 6.1.3 release doesn't have pitest 0.14 in the known list & when it looks for that it returns null.
Do we have a way of saying ignore a specific dependency for scanning (apart from standard suprressing)?


Gradle Java Plugin: Gradle Test Executor ignores proxy settings in gradle.properties

In a Java project we use (JUnit) integration tests which test how one of our components deals with a Certificate Revocation List (CRL) retrieved from a server. We noticed that these integration tests fail, whenever we run them on a machine behind a proxy.
After we defined ~/.gradle/gradle.properties
systemProp.https.proxyHost=##.##.##.##
systemProp.https.proxyPort=####
systemProp.http.proxyHost=##.##.##.##
systemProp.http.proxyPort=####

gradle was able to download its plugins, but still our integration tests did fail. Apparently those proxy settings have no impact on the Gradle Test Executor.
Expected Behavior

If a proxy is defined, it should be consistently used. The Gradle Test Executor should not ignore the proxy settings.
Current Behavior

As work-around we configured the test task in our root build.gradle to pass-further the proxy-settings:
subprojects {
    test {
        // pass the proxy configuration to the gradle test executor
        systemProperty "http.proxyHost", System.getProperty('http.proxyHost')
        systemProperty "http.proxyPort", System.getProperty('http.proxyPort')
        systemProperty "https.proxyHost", System.getProperty('https.proxyHost')
        systemProperty "https.proxyPort", System.getProperty('https.proxyPort')
    }
}

Sorry for the late reply.
This issue needs a decision from the team responsible for that area. They have been informed. Response time may vary.

By default, we run tests in isolation. Even if we talk about proxy, there can be scenarios when no proxy is preferred.
It's unlikely that Gradle should behave the way you described by default because overriding this might be cumbersome, and the list of "exceptions" for isolation might lengthen.
Note that the solution you provided can be applied globally via init scripts.
This nuance of worker isolation (not only for tests) should be documented more, e.g. here or in tests related docs.


openai-whisper: 2022.09-23 -> 2022.09-30

Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

The version in nixpkgs doesn't have this issue, but I can't run this new version.
[nix-shell:~/.cache/nixpkgs-review/pr-193707]$ whisper
Traceback (most recent call last):
  File "/nix/store/p7rkmymg8k1agznnsx7j84pmcgrjqf1c-python3.10-whisper-unstable-2022-09-30/bin/.whisper-wrapped", line 6, in <module>
    from whisper.transcribe import cli
  File "/nix/store/9mlwjdipzdwqafd2m0qj7m84i84x59q1-python3.9-whisper-unstable-2022-09-30/lib/python3.9/site-packages/whisper/__init__.py", line 8, in <module>
    import torch
  File "/nix/store/mh8gs1vp7rhi4fd31r2mil8dzfhljlgy-python3.9-torch-1.12.1/lib/python3.9/site-packages/torch/__init__.py", line 219, in <module>
    raise ImportError(textwrap.dedent('''
ImportError: Failed to load PyTorch C extensions:
    It appears that PyTorch has loaded the `torch/_C` folder
    of the PyTorch repository rather than the C extensions which
    are expected in the `torch._C` namespace. This can occur when
    using the `install` workflow. e.g.
        $ python setup.py install && python -c "import torch"

    This error can generally be solved using the `develop` workflow
        $ python setup.py develop && python -c "import torch"  # This should succeed
    or by running Python from a different directory.

This is a problem when executing whisper from the nixpkgs-review shell.
cc @Mic92 @SuperSandro2000

PYTHONPATH is a known issue when mixing different python versions. I don't know how to solve this in nixpkgs-review.


Add create_game_event template

Desired Outcome

users will have a template to create game events
the template will have routing like "/game-events/create"

Implemented Changes

I added a template for the form to create game events.
added a view that will render the template + will accept the post reqeust from the user and create the game event
added basic validation  for the view
applied group routing for game-events

Most of the PR is the game_events.views.create_game_event function
and the template itself game_event\templates\game_event\create_game_event.html
Connected Issue/Story
Resolves #68
Dependencies
There are no dependencies for now.

[ ] This PR depends on other PR's
changes
[x] This PR does not depend on other PR's

Definition of Done

Form for creation of GameEvents for the Players will be displayed at routing "game-events/create"
A view will be created which handles the display of the form and the creation GameEvent from the filled form by the Player.
Form Data will be validated inside the GameEvent.create() function, and if valid will create the GameEvent.
Otherwise error messeages will be displayed and the player will be redirected back to the form page.

Test coverage

[x] This PR includes new unit and integration tests to go with the code
changes
[ ] The changes in this PR do not require tests

Documentation

[ ] Docs (e.g. READMEs) were updated in this PR
[ ] A follow-up issue to update official docs has been filed here: insert issue ID
[x] This PR does not require updating any documentation

Hi Daniel,
You did a good job here!
I left you some reviews, would like to hear what you think about it.

here are some screenshots of the form and the possible validation erros.

And here is just noraml form

Dear Reviewers.
It's Important that you let me know, if the current implementation of the value of the court is sufficient (for future perposes maybe), since it's only the concatenation of the city and the neighborhood, and I thought it would be more user friendly fot the creator of an event to understand what court he is choosing .

In my opinion, we should keep the court value like that.

here are some screenshots of the form and the possible validation erros.

And here is just noraml form

The validation tests look very good with that red warning. Well done.
What happens when a user wants to enter a court? Does he have a list of all the existing ones, and he picks from there?
Or does he write his own text, and a court would be created?

The validation tests look very good with that red warning. Well done. What happens when a user wants to enter a court? Does he have a list of all the existing ones, and he picks from there? Or does he write his own text, and a court would be created?

For now, i render select option for each instance of a scourt, so user chooses from the existing courts in db.
maybe in the future we could manage a field for the user to input some address e.g "Kriat Ono Shlomo hameleh" and with the help of th "pin" library we can extract longitude and latitude from it, to create fresh instance of court in db. just a thought

Dear Reviewers. It's Important that you let me know, if the current implementation of the value of the court is sufficient (for future perposes maybe), since it's only the concatenation of the city and the neighborhood, and I thought it would be more user friendly fot the creator of an event to understand what court he is choosing .

For me it sounds good, I agree it will be more user friendly.

Do you still need your routing at game_event.urls ?
i dont know which PR will be merged first, so in a case this one get's merged, i will have to do quick rebase to include the game_event.urls in the meat_balls_urls
so i wonder maybe you can just fix it now  ? you can look at my PR #69
and instead of the 'game-event' routing you got there you could replace that line with
path('', views.game_events, name='game events')
the empty string in the path is because it has the prefix of "game-events/" from the meat_balls.urls

@Yuval-Vino I hope I have addressed all your comments, you can update me if something remains unaddressed and I would be happy if you resolve the conversations.


consider setting lookup-hostnames: false in default.yaml?

Pro: speeds up handshakes. Con: real hostname information won't be available to operators by default (they can dig -x manually, of course).

Probably going to do this after all.


Set log level to debug for kill switch activation message

As discussed, setting log level to debug for kill switch activation message.

Fixes #1004.


replace all IBitmap to Bitmap

https://github.com/AvaloniaUtils/AsyncImageLoader.Avalonia/issues/11#issue-1720011211

@SKProCH  hello , is this PR useless

Hello, @afunc233
No, it useful, i think, but i plan merge it when new version of Avalonia with IBitmap changes released.

it is compatible with avalonia11 , and the avalonia version has no change

Hmm, okay, i'll merge it in the weekends. Thanks!


Using vmhgfs with drvfs on 16179

Your Windows build number:  (Type ver at a Windows Command Prompt)
16179

What you're doing and what's happening:  (Copy&paste specific commands and their output, or include screen shots)

I'm trying to access files on a VMware (vmhgfs) drive using drvfs:
$ ls /mnt/z
$ mount -t drvfs z: /mnt/z
$ ls /mnt/z
ls: cannot open directory 'z': Invalid argument
$ ls /mnt/z/shared
[..]
test.txt
$ cat /mnt/z/shared/test.txt
cat: z/shared/test.txt: No such file or directory

What's wrong / what should be happening instead:

ls /mnt/z should show the contents of z:
cat /mnt/z/shared/test.txt should show the contents of the file.

Strace of the failing command, if applicable:  (If <cmd> is failing, then run strace -o strace.txt -ff <cmd>, and post the strace.txt output here)

ls strace:
execve("/bin/ls", ["ls", "/mnt/z"], [/* 27 vars */]) = 0
brk(NULL)                               = 0x1a3c000
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f00e2570000
access("/etc/ld.so.preload", R_OK)      = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=26140, ...}) = 0
mmap(NULL, 26140, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f00e2569000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libselinux.so.1", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260Z\0\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=130224, ...}) = 0
mmap(NULL, 2234080, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f00e1fd0000
mprotect(0x7f00e1fef000, 2093056, PROT_NONE) = 0
mmap(0x7f00e21ee000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e000) = 0x7f00e21ee000
mmap(0x7f00e21f0000, 5856, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f00e21f0000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1864888, ...}) = 0
mmap(NULL, 3967392, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f00e1c00000
mprotect(0x7f00e1dbf000, 2097152, PROT_NONE) = 0
mmap(0x7f00e1fbf000, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1bf000) = 0x7f00e1fbf000
mmap(0x7f00e1fc5000, 14752, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f00e1fc5000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libpcre.so.3", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0000\25\0\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=456632, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f00e2560000
mmap(NULL, 2552072, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f00e1990000
mprotect(0x7f00e19fe000, 2097152, PROT_NONE) = 0
mmap(0x7f00e1bfe000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x6e000) = 0x7f00e1bfe000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libdl.so.2", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\240\r\0\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=14608, ...}) = 0
mmap(NULL, 2109680, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f00e1780000
mprotect(0x7f00e1783000, 2093056, PROT_NONE) = 0
mmap(0x7f00e1982000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2000) = 0x7f00e1982000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libpthread.so.0", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260`\0\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=138696, ...}) = 0
mmap(NULL, 2212904, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f00e1560000
mprotect(0x7f00e1578000, 2093056, PROT_NONE) = 0
mmap(0x7f00e1777000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x17000) = 0x7f00e1777000
mmap(0x7f00e1779000, 13352, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f00e1779000
close(3)                                = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f00e2550000
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f00e2540000
arch_prctl(ARCH_SET_FS, 0x7f00e2540800) = 0
mprotect(0x7f00e1fbf000, 16384, PROT_READ) = 0
mprotect(0x7f00e1777000, 4096, PROT_READ) = 0
mprotect(0x7f00e1982000, 4096, PROT_READ) = 0
mprotect(0x7f00e1bfe000, 4096, PROT_READ) = 0
mprotect(0x7f00e21ee000, 4096, PROT_READ) = 0
mprotect(0x61d000, 4096, PROT_READ)     = 0
mprotect(0x7f00e2425000, 4096, PROT_READ) = 0
munmap(0x7f00e2569000, 26140)           = 0
set_tid_address(0x7f00e2540ad0)         = 192
set_robust_list(0x7f00e2540ae0, 24)     = 0
rt_sigaction(SIGRTMIN, {0x7f00e1565b50, [], SA_RESTORER|SA_SIGINFO, 0x7f00e1571390}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {0x7f00e1565be0, [], SA_RESTORER|SA_RESTART|SA_SIGINFO, 0x7f00e1571390}, NULL, 8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=8192*1024}) = 0
statfs("/sys/fs/selinux", 0x7fffe57a2f80) = -1 ENOENT (No such file or directory)
statfs("/selinux", 0x7fffe57a2f80)      = -1 ENOENT (No such file or directory)
brk(NULL)                               = 0x1a3c000
brk(0x1a5d000)                          = 0x1a5d000
open("/proc/filesystems", O_RDONLY)     = 3
fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(3, "nodev      sysfs\nnodev      root"..., 4096) = 367
read(3, "", 4096)                       = 0
close(3)                                = 0
open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=2981280, ...}) = 0
mmap(NULL, 2981280, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f00e1288000
close(3)                                = 0
ioctl(1, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(1, TIOCGWINSZ, {ws_row=41, ws_col=151, ws_xpixel=0, ws_ypixel=0}) = 0
stat("/mnt/z", {st_mode=S_IFDIR|0555, st_size=512, ...}) = 0
open("/mnt/z", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 EINVAL (Invalid argument)
open("/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=2995, ...}) = 0
read(3, "# Locale name alias data base.\n#"..., 512) = 512
read(3, "See the\n# GNU General Public Lic"..., 512) = 512
read(3, "nd for the time being for\n# back"..., 512) = 512
read(3, "hese lines were removed\n# becaus"..., 512) = 512
read(3, "8859-1\ngalego\t\tgl_ES.ISO-8859-1\n"..., 512) = 512
read(3, "O.ISO-8859-1 nb_NO.ISO-8859-1\nno"..., 512) = 435
read(3, "", 512)                        = 0
close(3)                                = 0
open("/usr/share/locale/en_US.UTF-8/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en_US.utf8/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en_US/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en.UTF-8/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en.utf8/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en_US.UTF-8/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en_US.utf8/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en_US/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en.UTF-8/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en.utf8/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en/LC_MESSAGES/coreutils.mo", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=619, ...}) = 0
mmap(NULL, 619, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f00e2576000
close(3)                                = 0
write(2, "ls: ", 4)                     = 4
write(2, "cannot open directory '/mnt/z'", 30) = 30
open("/usr/share/locale/en_US.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en_US.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en_US/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en_US.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en_US.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en_US/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
write(2, ": Invalid argument", 18)      = 18
write(2, "\n", 1)                       = 1
close(1)                                = 0
close(2)                                = 0
exit_group(2)                           = ?
+++ exited with 2 +++

cat strace:
execve("/bin/cat", ["cat", "/mnt/z/shared/test.txt"], [/* 27 vars */]) = 0
brk(NULL)                               = 0x1e93000
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fc500640000
access("/etc/ld.so.preload", R_OK)      = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=26140, ...}) = 0
mmap(NULL, 26140, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fc500642000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1864888, ...}) = 0
mmap(NULL, 3967392, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fc500030000
mprotect(0x7fc5001ef000, 2097152, PROT_NONE) = 0
mmap(0x7fc5003ef000, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1bf000) = 0x7fc5003ef000
mmap(0x7fc5003f5000, 14752, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fc5003f5000
close(3)                                = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fc500630000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fc500620000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fc500610000
arch_prctl(ARCH_SET_FS, 0x7fc500620700) = 0
mprotect(0x7fc5003ef000, 16384, PROT_READ) = 0
mprotect(0x60b000, 4096, PROT_READ)     = 0
mprotect(0x7fc500625000, 4096, PROT_READ) = 0
munmap(0x7fc500642000, 26140)           = 0
brk(NULL)                               = 0x1e93000
brk(0x1eb4000)                          = 0x1eb4000
open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=2981280, ...}) = 0
mmap(NULL, 2981280, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fc4ffd58000
close(3)                                = 0
fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 1), ...}) = 0
open("/mnt/z/shared/test.txt", O_RDONLY) = -1 ENOENT (No such file or directory)
write(2, "cat: ", 5)                    = 5
write(2, "/mnt/z/shared/test.txt", 22)  = 22
open("/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=2995, ...}) = 0
read(3, "# Locale name alias data base.\n#"..., 512) = 512
read(3, "See the\n# GNU General Public Lic"..., 512) = 512
read(3, "nd for the time being for\n# back"..., 512) = 512
read(3, "hese lines were removed\n# becaus"..., 512) = 512
read(3, "8859-1\ngalego\t\tgl_ES.ISO-8859-1\n"..., 512) = 512
read(3, "O.ISO-8859-1 nb_NO.ISO-8859-1\nno"..., 512) = 435
read(3, "", 512)                        = 0
close(3)                                = 0
open("/usr/share/locale/en_US.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en_US.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en_US/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en_US.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en_US.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en_US/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
write(2, ": No such file or directory", 27) = 27
write(2, "\n", 1)                       = 1
close(1)                                = 0
close(2)                                = 0
exit_group(1)                           = ?
+++ exited with 1 +++

This looks similar to #1954.

I am having the exact same problem.

@lucidbee please vote on uservoice as suggested by @sunilmut


TemplateEngine: render fails on multiple tags on the same line

working case:
{{ tag1 }}
{{ tag2 }}
{{ tag3 }}
issue with:
{{ tag1 }} {{ tag2 }}
{{ tag3 }}
-> render takes "tag1 }} {{ tag2" as tag instead of "tag1" and "tag2" separately

Hello, Thanks Yanis for the feedback. Can you add an entry in the changelog folder like the following:
echo "Fix template rendering when multiple tags are passed on the same line" > changelog/48.bugfix.rst
You can can commit that file with your pull request

Hello, Thanks Yanis for the feedback. Can you add an entry in the changelog folder like the following: echo "Fix template rendering when multiple tags are passed on the same line" > changelog/48.bugfix.rst
You can can commit that file with your pull request

Hello,
Sorry I missed the message, maybe for the next time ;-)


Empty nofification with function sendMulticast of CloudMessaging

I'm using 4.44.0 version for my php 7.0 server
But I catch a problem with function sendMulticast of CloudMessaging feature
When I using this method, create a new message object and bind notification and data, then call sendMulticast function, i got notification on device but it had no title and body, just empty notification
$deviceTokens = [
    'xxx',
    'yyy'
];
$message = CloudMessage::new(); // Any instance of Kreait\Messaging\Message
$message->withNotification(Notification::create('Title', 'Body'));
$message->withData(['key' => 'value']);
$send = $messaging->sendMulticast($message, $deviceTokens);

After that, I change the method to build message from object to from array
$message = CloudMessage::fromArray([
    'notification' => [
        'title' => 'Test',
        'body' => 'This is a test'
    ],
    'data' => [
        'key' => 'value'
    ],
]);
$send = $messaging->sendMulticast($message, $deviceTokens);

Then I receive a notification has title and body properly
Environment

OS:  Windows 10
PHP version: 7.0.13
Firebase SDK Version: 4.44.0

Could you please check what cause problem with the 1st method to build CloudMessage object?

The message object is immutable, this means that method calls will return a new object and leave the original object untouched.
If you use
$message = $message->with*(...);

you will have the expected result 🤞

I have a related question, fcm support send messages to multiple devices (1000) on a request to their server https://fcm.googleapis.com/fcm/send
How is it going with our sdk? Do you applied this feature to send message to multiple devices or send it one by one (1 request per device in loop)?

The SDK uses the same API - you can send up to 1000 messages in one request 🥳

The SDK uses the same API - you can send up to 1000 messages in one request 🥳

Glad to hear that, but when I read the docs, it said that max number of tokens is 500, is it okay if I use array of 1000 tokens to send?

Oh, my bad, you're right, the limit here is currently 500 - Firebase must have upped the limits in the meantime.
I'll change the limit after I confirm this in the official SDKs and create new releases.

thank you for your reply, I will close the issue

The official Node Admin SDK (still( has the 500 messages per batch limit (https://github.com/firebase/firebase-admin-node/blob/master/src/messaging/messaging.ts#L45 - I'll change it here when they change it, too 😅


Dial’s Algorithm

Again, the PR is for the C branch. Make a PR for the master branch. Closing this issue for now


Prevent overfitting the model

Hello,
I am currently playing the the unsloth library and its performing amazingly, even on my local machine. Unfortunately, I have an issue with the model kind of "forgetting" its generic purpose as I've been training it on "custom task" dataset e.g.
### Instruction:
I have an issue with order 3124
### Response:
Apologies for the issue with order 3124, the reason for the issue is {"id": 3124}"""

Currently my dataset is around 30k entries and I've been using r=8 and lora_alpha=16 to try to prevent overfitting.
However, now when I ask "What is the capital of France", I get hallucinations of the sort of "Apologies for the issue with order 3124, the reason for the issue is {"id": 3124}".
Correct me if I am wrong but running if False: model.push_to_hub_gguf("hf/model", tokenizer, quantization_method = "f16", token = "") merges the lora adapters with the pre-trained weights so in a sense we should keep the "old" knowledge of the model.
Maybe reducing the amount of target modules can help ?

I have the same problem and I can't get the model inference process.

Hello,
I am currently playing the the unsloth library and its performing amazingly, even on my local machine. Unfortunately, I have an issue with the model kind of "forgetting" its generic purpose as I've been training it on "custom task" dataset e.g.
### Instruction:
I have an issue with order 3124
### Response:
Apologies for the issue with order 3124, the reason for the issue is {"id": 3124}"""

Currently my dataset is around 30k entries and I've been using r=8 and lora_alpha=16 to try to prevent overfitting.
However, now when I ask "What is the capital of France", I get hallucinations of the sort of "Apologies for the issue with order 3124, the reason for the issue is {"id": 3124}".
Correct me if I am wrong but running if False: model.push_to_hub_gguf("hf/model", tokenizer, quantization_method = "f16", token = "") merges the lora adapters with the pre-trained weights so in a sense we should keep the "old" knowledge of the model.
Maybe reducing the amount of target modules can help ?

I think you need to modify your input format, I have tested it on my fine-tuned model, and it worked.

But I don't get the reasoning process on my task, I don't know why.

So to maintain the model's "old" knowledge, I would try adding some generic datasets to the finetune (concat), or reduce the number of steps. Another "trick" is before you merge the lora adapters, simply scale all of them by some fraction (say 0.1) to reduce the effect of the adapters. It might not work very well, but it should function (hopefully)

So to maintain the model's "old" knowledge, I would try adding some generic datasets to the finetune (concat), or reduce the number of steps. Another "trick" is before you merge the lora adapters, simply scale all of them by some fraction (say 0.1) to reduce the effect of the adapters. It might not work very well, but it should function (hopefully)

Thank you, in your second suggestion how to exactly scale them in terms of code ?

Oh in the adapter_config.json file, change lora_alpha literally


Timeout exceeded while awaiting headers

I'm using cachet-monitor v2.0
Got this message in the incident.
Get http://someurl/health: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
The health check URL is fine, but somehow its response is slightly slow (the slowest take up to 3000ms). But I think it is still acceptable. Is there a way to control the timeout value?
Thanks

Should be possible via the config file.

@matejkramny Here a PR to enhance the timeout.

Thanks

Hi @matejkramny when do you plan to release that fix?
Thanks a lot you two!

Hi @tk-s, I meant to improve the package slightly after merging however life got in the way. Will be soon


'CondaVerificationError' and 'ClobberError'

Hi, all,
I was using conda to install MiGA on a local MasOS laptop. When I used conda to activate MiGA and following install the requirements, it always reported 'CondaVerificationError' and 'ClobberError'.
The description attached,
The errors.txt
I was trying to reinstall conda with different versions, or use a command 'conda clean -a'
to reset conda, but the errors were still reporting.

Hello @chencan-cc
I strongly recommend using Homebrew whenever possible, since conda has incompatibilities between packages that are very system-specific.  However, I have now updated the instructions to resolve some incompatibilities between conda packages.
It seems the conda package for FastANI still downgrades several other packages, so I would recommend excluding FastANI from the conda installation and installing it directly from source or through Homebrew. Nevertheless, If you're ok with the risk of using (very) outdated packages, I believe the new instructions should work properly.
I'm closing this issue, but please feel free to reopen if you continue to experience problems.


Feature: DenseMap utility implementation

Nice work, thanks for adding the documentation.
I am getting a compile error on this line:
			mCount = size() > 32 ? 1 << (std::log(size()) + 1) : 64;

Cannot apply binary << to 'int' and 'double'.

Also I noticed the code is mixing bs_allocN and bs_delete, allocN will allocate the memory without calling the constructor, while bs_delete will call the destructor and then free the memory.
bs_alloc/bs_allocN should be freed through bs_free, while bs_construct should be freed with bs_delete.
Not sure whether the intent was to call the constructor/destruction or not...

Thanks for making the changes. Awesome work on this one. Merged.


Traefik bungles the PDNS_API_URL string for accessing the PowerDNS API

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?
I'm trying to do a Let's Encrypt DNS challenge using PowerDNS.  My PowerDNS server is ns1.example.org and I confirmed that I can successfully query the API like this:
curl  -H 'X-API-Key: $PDNS_API_KEY' https://ns1.example.org/api/v1/servers/localhost/zones/example.net
When I set the environment variable PDNS_API_URL=https://ns1.example.org/api/v1 then I get this error message:
time="2023-02-15T23:13:32Z" level=error msg="Unable to obtain ACME certificate for domains \"cluster.example.net\": unable to generate a certificate for the domains [cluster.example.net]: error: one or more domains had a problem:\n[cluster.example.net] [cluster.example.net] acme: error presenting token: pdns: unexpected HTTP status code 404 when GETing 'https://ns1.example.org/api/v1/api/v1/servers/localhost/zones/example.net.'\n" providerName=letsencrypt.acme ACME CA="https://acme-v02.api.letsencrypt.org/directory" routerName=grafana-grafana-cluster-example-net-grafana@kubernetes rule="Host(`cluster.example.net`) && PathPrefix(`/grafana`)"

When I set the environment variable PDNS_API_URL=https://ns1.example.org/ then I get this error message:
time="2023-02-15T23:14:45Z" level=error msg="Unable to obtain ACME certificate for domains \"cluster.example.net\": unable to generate a certificate for the domains [cluster.example.net]: error: one or more domains had a problem:\n[cluster.example.net] [cluster.example.net] acme: error presenting token: pdns: unexpected HTTP status code 404 when GETing 'https://ns1.example.org/servers/localhost/zones/example.net.'\n" routerName=grafana-grafana-cluster-example-net-grafana@kubernetes rule="Host(`cluster.example.net`) && PathPrefix(`/grafana`)" providerName=letsencrypt.acme ACME CA="https://acme-v02.api.letsencrypt.org/directory"

What did you see instead?
Traefik is changing the $PDNS_API_URL string that I provide. It either adds or removes the "api/v1" part but it has inverted the logic, changing it so that "api/v1" is present either 0 or 2 times instead of exactly once. So no matter what string I provide I can not get it to query the correct API path.

Helm chart v21.0.0
Pod is running with
spec:
  containers:
  - args:
    - --entrypoints.metrics.address=:9100/tcp
    - --entrypoints.traefik.address=:9000/tcp
    - --entrypoints.web.address=:8000/tcp
    - --entrypoints.websecure.address=:8443/tcp
    - --api.dashboard=true
    - --ping=true
    - --metrics.prometheus=true
    - --metrics.prometheus.entrypoint=metrics
    - --providers.kubernetescrd
    - --providers.kubernetesingress
    - --entrypoints.websecure.http.tls=true
    - --log.level=DEBUG
    - --certificatesresolvers.letsencrypt.acme.dnsChallenge.provider=pdns
    - --certificatesresolvers.letsencrypt.acme.storage=/data/acme.json

If applicable, please paste the log output in DEBUG level
No response

Hello,
can you try to use Traefik v2.9.8?

There isn't a helm chart for that yet but I manually updated to image: traefik:v2.9.8
/ $ traefik version
Version:      2.9.8
Codename:     banon
Go version:   go1.19.6
Built:        2023-02-15T15:23:25Z
OS/Arch:      linux/amd64

But it's still the same problem. @ldez

I also downgraded the traefik image to 2.9.5 and the problem still remained the same.
I am using powerdns-admin to access the API.

If the problem persists when you downgrade traefik maybe it's related to PowerDNS.

The behavior around the URL depends on the API version of PowerDNS.
example 1:

baseURL: https://ns1.example.org/api/v1
API version: 1
=> https://ns1.example.org/api/v1/api/v1

example 2:

baseURL: https://ns1.example.org/api/v1
API version: 0
=> https://ns1.example.org/api/v1

example 3:

baseURL: https://ns1.example.org
API version: 1
=> https://ns1.example.org/api/v1

example 4:

baseURL: https://ns1.example.org
API version: 0
=> https://ns1.example.org

The API version is obtained by calling baseURL+"/api" of PowerDNS.

@ldez thanks for looking into this. We're using PDA as a proxy in front of the "real" API so that tokens can be used to authn.
Hmm but it looks like    /api and /api/v1 display a 404 page.
time="2023-02-16T01:41:27Z" level=debug msg="legolog: [WARN] pdns: failed to get API version unexpected HTTP status code 404 when GETing 'https://ns1.example.org/api'"

However based on your examples above, even if the API version detection falls back to 0, I should be able to set PDNS_API_URL: https://ns1.example.org/api/v1 and end up with https://ns1.example.org/api/v1 which would work.
In fact when I go back to setting https://ns1.example.org/api/v1 , I get
time="2023-02-16T01:48:12Z" level=debug msg="legolog: [WARN] pdns: failed to get API version unexpected HTTP status code 404 when GETing 'https://ns1.example.org/api/v1/api'"

which implies that the URL gets messed up before the API version detection can happen.

API version detection happens when Traefik starts so it cannot be done after something else.
I have unit tests on the build of the URL and I'm not able to have this behavior with API version 0.
So I don't understand.

What I meant is that the "failed to get API version" error message tries to query https://ns1.example.org/api/v1/api which is already wrong, so if the message is to be believed, the wrong URL was already used before the API detection was attempted.
Anyway it seems like it is related to using powerdns-admin. If I instead use the HTTP API directly then /api returns version 1 and it works. But I would argue there is still a bug because if LEGO would just use the URL I provide instead of getting confused by whatever is happening with the version detection, it would work.