i/o timeout

Many thanks for putting this docker here on Gitlab. I am new to this and have followed your steps (in Ubuntu, installed all needed elements along the way) but at the last step ("sls deploy"), I am getting the following error message.
Deploying docker-selenium-lambda to stage prod (eu-central-1)
✖ Stack docker-selenium-lambda-prod failed to deploy (193s)
Environment: linux, node 16.15.0, framework 3.16.0, plugin 6.2.2, SDK 4.3.2
Credentials: Local, "default" profile
Docs:        docs.serverless.com
Support:     forum.serverless.com
Bugs:        github.com/serverless/serverless/issues
Error:
Encountered error during executing: docker push
...
dial tcp <IP_ADDRESS>:443: i/o timeout
I searched a lot on Google but could not find anything related. Do you have any idea what might be the issue for me?

@bklaus002
Building and pushing docker image may costs some memory and time. I suggest you to increase docker memory limit config but I am not sure it works. I want you to try deploying in another environment.
And could you check some ECR repositories were created and they have uploaded images inside? My guess is a repository is created but no images there.

Thanks for posting this, I have been looking for an alternative for scrapping some sites, generating an API to use the website information and now is working !!!!
As an improvement, I tried to separate the elements and construct as a LAMBDA layer the elements of Selenium and Chrome, so is easier to deploy or even change the code of the scrapping (if the website changes something), but failed miserably.
The deployment only copies the files on the directory and nothing else any support will be greatly appreciated
Here is the content of the serverless.yml
service: docker-selenium-lambda
provider:
name: aws
stage: ${opt:stage, 'prod'}
region: ${env:AWS_REGION, 'us-east-2'}
ecr:
images:
img:
path: ./
platform: linux/amd64
layers:
selenium-lambda:
path: ./
And the Dockerfile
FROM public.ecr.aws/lambda/python@sha256:2203844d7263f9c38a7f03f25bbb181772e93abc944de2b26ccca1689e1dde55 as build
RUN yum install -y unzip &&
curl -Lo "/tmp/chromedriver.zip" "https://chromedriver.storage.googleapis.com/101.0.4951.41/chromedriver_linux64.zip" &&
curl -Lo "/tmp/chrome-linux.zip" "https://www.googleapis.com/download/storage/v1/b/chromium-browser-snapshots/o/Linux_x64%2F982481%2Fchrome-linux.zip?alt=media" &&
unzip /tmp/chromedriver.zip -d /opt/ &&
unzip /tmp/chrome-linux.zip -d /opt/
FROM public.ecr.aws/lambda/python@sha256:2203844d7263f9c38a7f03f25bbb181772e93abc944de2b26ccca1689e1dde55
RUN yum install atk cups-libs gtk3 libXcomposite alsa-lib
libXcursor libXdamage libXext libXi libXrandr libXScrnSaver
libXtst pango at-spi2-atk libXt xorg-x11-server-Xvfb
xorg-x11-xauth dbus-glib dbus-glib-devel -y
RUN pip install selenium
COPY --from=build /opt/chrome-linux /opt/chrome
COPY --from=build /opt/chromedriver /opt/

increase docker memory limit config

Unfortunately, I am really new to this and would need some concrete steps to follow or links. My guess is that I have not set the needed permissions so that the image can be uploaded to the repository. I followed your suggestion and indeed the repository was created, but no image is inside. I will check the permissions.

@bklaus002
Maybe you can get more logs and details which step is hanging and why by sls deploy --verbose

@bklaus002
Maybe you can get more logs and details which step is hanging and why by sls deploy --verbose

Here is the full log from sls deploy --verbose, but I am not sure that helps to understand where the problem is.
sls deploy --verbose
To ensure safe major version upgrades ensure "frameworkVersion" setting in service configuration (recommended setup: "frameworkVersion: ^3.16.0")
Deploying docker-selenium-lambda to stage prod (eu-central-1)
Packaging
Sending build context to Docker daemon   12.8kB
Step 1/9 : FROM public.ecr.aws/lambda/python@sha256:2203844d7263f9c38a7f03f25bbb181772e93abc944de2b26ccca1689e1dde55 as build
---> ec11cea4dd41
Step 2/9 : RUN yum install -y unzip &&     curl -Lo "/tmp/chromedriver.zip" "https://chromedriver.storage.googleapis.com/101.0.4951.41/chromedriver_linux64.zip" &&     curl -Lo "/tmp/chrome-linux.zip" "https://www.googleapis.com/download/storage/v1/b/chromium-browser-snapshots/o/Linux_x64%2F982481%2Fchrome-linux.zip?alt=media" &&     unzip /tmp/chromedriver.zip -d /opt/ &&     unzip /tmp/chrome-linux.zip -d /opt/
---> Using cache
---> 187c7d849bef
Step 3/9 : FROM public.ecr.aws/lambda/python@sha256:2203844d7263f9c38a7f03f25bbb181772e93abc944de2b26ccca1689e1dde55
---> ec11cea4dd41
Step 4/9 : RUN yum install atk cups-libs gtk3 libXcomposite alsa-lib     libXcursor libXdamage libXext libXi libXrandr libXScrnSaver     libXtst pango at-spi2-atk libXt xorg-x11-server-Xvfb     xorg-x11-xauth dbus-glib dbus-glib-devel -y
---> Using cache
---> 7dfe8aea5ec1
Step 5/9 : RUN pip install selenium
---> Using cache
---> a98b23058aff
Step 6/9 : COPY --from=build /opt/chrome-linux /opt/chrome
---> Using cache
---> 42f7f809a529
Step 7/9 : COPY --from=build /opt/chromedriver /opt/
---> Using cache
---> d59b22d93d94
Step 8/9 : COPY test.py ./
---> Using cache
---> 8bd3b19e0e06
Step 9/9 : CMD [ "test.handler" ]
---> Using cache
---> 54928edad7ca
Successfully built 54928edad7ca
Successfully tagged serverless-docker-selenium-lambda-prod:img
Login to Docker succeeded!
Warning: Docker authentication token will be stored unencrypted in docker config. Configure Docker credential helper to remove this warning.
✖ Stack docker-selenium-lambda-prod failed to deploy (165s)
Environment: linux, node 16.15.0, framework 3.16.0, plugin 6.2.2, SDK 4.3.2
Credentials: Local, "default" profile
Docs:        docs.serverless.com
Support:     forum.serverless.com
Bugs:        github.com/serverless/serverless/issues
Error:
Encountered error during executing: docker push,965921893518.dkr.ecr.eu-central-1.amazonaws.com/serverless-docker-selenium-lambda-prod:img
Output of the command:
The push refers to repository [965921893518.dkr.ecr.eu-central-1.amazonaws.com/serverless-docker-selenium-lambda-prod]
ed3dd29aba64: Preparing
35d5510de2d2: Preparing
2cdd43c88afc: Preparing
0847d0e8d776: Preparing
12f97f027ec8: Preparing
a8b55e94d2b2: Preparing
deb207ae2541: Preparing
5f96311c404e: Preparing
6a0bca2873ed: Preparing
435bd6980d66: Preparing
c0bc13e98dfd: Preparing
6a0bca2873ed: Waiting
deb207ae2541: Waiting
5f96311c404e: Waiting
435bd6980d66: Waiting
c0bc13e98dfd: Waiting
a8b55e94d2b2: Waiting
ed3dd29aba64: Retrying in 5 seconds
ed3dd29aba64: Retrying in 4 seconds
ed3dd29aba64: Retrying in 3 seconds
ed3dd29aba64: Retrying in 2 seconds
ed3dd29aba64: Retrying in 1 second
ed3dd29aba64: Retrying in 10 seconds
ed3dd29aba64: Retrying in 9 seconds
ed3dd29aba64: Retrying in 8 seconds
ed3dd29aba64: Retrying in 7 seconds
ed3dd29aba64: Retrying in 6 seconds
ed3dd29aba64: Retrying in 5 seconds
ed3dd29aba64: Retrying in 4 seconds
ed3dd29aba64: Retrying in 3 seconds
ed3dd29aba64: Retrying in 2 seconds
ed3dd29aba64: Retrying in 1 second
ed3dd29aba64: Retrying in 15 seconds
ed3dd29aba64: Retrying in 14 seconds
ed3dd29aba64: Retrying in 13 seconds
ed3dd29aba64: Retrying in 12 seconds
2cdd43c88afc: Retrying in 5 seconds
ed3dd29aba64: Retrying in 11 seconds
2cdd43c88afc: Retrying in 4 seconds
ed3dd29aba64: Retrying in 10 seconds
2cdd43c88afc: Retrying in 3 seconds
ed3dd29aba64: Retrying in 9 seconds
2cdd43c88afc: Retrying in 2 seconds
ed3dd29aba64: Retrying in 8 seconds
2cdd43c88afc: Retrying in 1 second
ed3dd29aba64: Retrying in 7 seconds
ed3dd29aba64: Retrying in 6 seconds
0847d0e8d776: Retrying in 5 seconds
ed3dd29aba64: Retrying in 5 seconds
35d5510de2d2: Retrying in 5 seconds
0847d0e8d776: Retrying in 4 seconds
ed3dd29aba64: Retrying in 4 seconds
35d5510de2d2: Retrying in 4 seconds
0847d0e8d776: Retrying in 3 seconds
ed3dd29aba64: Retrying in 3 seconds
12f97f027ec8: Retrying in 5 seconds
35d5510de2d2: Retrying in 3 seconds
0847d0e8d776: Retrying in 2 seconds
ed3dd29aba64: Retrying in 2 seconds
12f97f027ec8: Retrying in 4 seconds
35d5510de2d2: Retrying in 2 seconds
0847d0e8d776: Retrying in 1 second
ed3dd29aba64: Retrying in 1 second
12f97f027ec8: Retrying in 3 seconds
35d5510de2d2: Retrying in 1 second
12f97f027ec8: Retrying in 2 seconds
12f97f027ec8: Retrying in 1 second
12f97f027ec8: Retrying in 10 seconds
ed3dd29aba64: Retrying in 20 seconds
12f97f027ec8: Retrying in 9 seconds
ed3dd29aba64: Retrying in 19 seconds
12f97f027ec8: Retrying in 8 seconds
ed3dd29aba64: Retrying in 18 seconds
12f97f027ec8: Retrying in 7 seconds
ed3dd29aba64: Retrying in 17 seconds
12f97f027ec8: Retrying in 6 seconds
ed3dd29aba64: Retrying in 16 seconds
12f97f027ec8: Retrying in 5 seconds
ed3dd29aba64: Retrying in 15 seconds
12f97f027ec8: Retrying in 4 seconds
ed3dd29aba64: Retrying in 14 seconds
12f97f027ec8: Retrying in 3 seconds
ed3dd29aba64: Retrying in 13 seconds
12f97f027ec8: Retrying in 2 seconds
ed3dd29aba64: Retrying in 12 seconds
12f97f027ec8: Retrying in 1 second
ed3dd29aba64: Retrying in 11 seconds
ed3dd29aba64: Retrying in 10 seconds
ed3dd29aba64: Retrying in 9 seconds
ed3dd29aba64: Retrying in 8 seconds
ed3dd29aba64: Retrying in 7 seconds
ed3dd29aba64: Retrying in 6 seconds
ed3dd29aba64: Retrying in 5 seconds
ed3dd29aba64: Retrying in 4 seconds
ed3dd29aba64: Retrying in 3 seconds
ed3dd29aba64: Retrying in 2 seconds
ed3dd29aba64: Retrying in 1 second
12f97f027ec8: Retrying in 15 seconds
12f97f027ec8: Retrying in 14 seconds
12f97f027ec8: Retrying in 13 seconds
12f97f027ec8: Retrying in 12 seconds
12f97f027ec8: Retrying in 11 seconds
12f97f027ec8: Retrying in 10 seconds
12f97f027ec8: Retrying in 9 seconds
12f97f027ec8: Retrying in 8 seconds
12f97f027ec8: Retrying in 7 seconds
12f97f027ec8: Retrying in 6 seconds
12f97f027ec8: Retrying in 5 seconds
dial tcp <IP_ADDRESS>:443: i/o timeout

Seems IAM permission issue? Can you use AdministratorAccess?
https://stackoverflow.com/questions/70828205/pushing-an-image-to-ecr-getting-retrying-in-seconds

Seems IAM permission issue? Can you use AdministratorAccess?
https://stackoverflow.com/questions/70828205/pushing-an-image-to-ecr-getting-retrying-in-seconds

Many thanks for the link. I tried the following:

I added the policy AmazonEC2ContainerRegistryFullAccess to the IAM user as in https://stackoverflow.com/questions/70452836/docker-push-to-aws-ecr-hangs-immediately-and-times-out/70453287#70453287
I added the policy AmazonEC2ContainerRegistryPowerUser to the IAM user as in https://stackoverflow.com/questions/70828205/pushing-an-image-to-ecr-getting-retrying-in-seconds
I added different permissions to the ECR as in https://stackoverflow.com/questions/70452836/docker-push-to-aws-ecr-hangs-immediately-and-times-out/70453287#70453287
I changed the default region to us-east-1 (as your YML-file mentions this region) as mentioned in https://www.youtube.com/watch?v=89ZeXaZEf80

None of those points solved the issue, I am still getting the same error.

Can you push any image into your ECR repository in general? If you can't, it is not this project problem.
I asked you to use AdministratorAccess. Serverless Framework requires lots of permissions..

Can you push any image into your ECR repository in general? If you can't, it is not this project problem.
I asked you to use AdministratorAccess. Serverless Framework requires lots of permissions..

Actually, I have now tried to follow the steps in this link https://www.youtube.com/watch?v=89ZeXaZEf80 and I see that when starting the push command things appear to work.
ed3dd29aba64: Retrying in 1 second
35d5510de2d2: Retrying in 1 second
2cdd43c88afc: Pushing [====>                                              ]   38.4MB/454.8MB
0847d0e8d776: Pushing [===========================================>       ]  31.38MB/35.71MB
12f97f027ec8: Pushing [====>                                              ]  40.32MB/478.8MB
a8b55e94d2b2: Waiting
deb207ae2541: Waiting
5f96311c404e: Waiting
6a0bca2873ed: Waiting
435bd6980d66: Waiting
c0bc13e98dfd: Waiting
dial tcp <IP_ADDRESS>:443: i/o timeout
To me it looks like the file sizes (the image appears to be 1.5GB) are just very large so it takes time. Can I increase the timeout limit somewhere?
And where in Serverless do I make this change to AdministratorAccess?

I followed the AWS push commands based on the steps shown in this video https://www.youtube.com/watch?v=89ZeXaZEf80 and used this small docker image https://github.com/alpinelinux/docker-alpine/tree/master as an example and it works for me. There is no timeout error there, the file sizes are a few MBs.

And where in Serverless do I make this change to AdministratorAccess?

Serverless Framework use aws credentials by default

I'll reopen this issue again if this seems relate my repository problem

And where in Serverless do I make this change to AdministratorAccess?

Serverless Framework use aws credentials by default

I checked it and I had the AdministratorAccess rights already attached to my user. Unfortunately, while I am able to deploy a smaller repository, your 1.5GB image I am not able to deploy. To me it looks like there is a timeout error.

I just wanted to provide details on what the issue was and how I solved it for me. It turned out that, probably due to my internet connection speed and the docker default setting to try and upload five layers at a time, a timeout error occurred and deployment of the docker image was not successful. This issue is described also by other users, e.g. here: https://www.kovarus.com/blog/docker-push-timeout-to-aws-elastic-container-registry/.
It is possible to lower the number of layers that docker tries to upload at a time using the dockerd command, see the options here: https://docs.docker.com/engine/reference/commandline/dockerd/
At the end, dockerd --max-concurrent-uploads 1 worked for me as it lowered the number of layers to one at a time and this prevented the timeout error from occurring.
The docker image was successfully installed and works. Many thanks to umihico!

wow I'm grad to hear that you solved. thank you for telling me about --max-concurrent-uploads option ;)


[BUG] Running cell annotation when CELL_ANNOTATION_SOURCES are NULL

Description
I ran the default configuration on the example data (pbmc1k) in the Docker environment using the Docker image: jirinovo/scdrake:1.5.0-bioc3.15.
I made the following changes to the configuration files:

02_norm_clustering.yaml

CELL_ANNOTATION_SOURCES: null

pipeline.yaml

DRAKE_TARGETS: ["report_input_qc", "report_norm_clustering", "report_norm_clustering_simple"]

The pipeline failed at the cell_annotation target while executing run_single_sample_r(), resulting in the following error:
✖ fail cell_annotation_c19514a9
Warning message:
ignoring targets not in the drake plan:
  config_integration
  config_int_clustering
Error:
! in callr subprocess.
Caused by error:
! target cell_annotation_c19514a9 failed.
diagnose(cell_annotation_c19514a9)$error$message:
  Could not evaluate cli `{}` expression: `row$name`.
...

Expected behaviour
The pipeline finishing without errors, and creating reports for quality control and normalization_clustering steps. Norm_clustering report should not contain cell annotation subchapter of the report
Current behaviour
The pipeline fails when creating cell_annotation target. It should skip the cell annotation.

Fixed in https://github.com/bioinfocz/scdrake/pull/3


Add collapsable items in OutlinePanel

https://user-images.githubusercontent.com/2925395/178054586-a28da584-38d7-40a7-a9fa-832f1004682a.mp4
Add item collapsing in outline panel

Yo, this still needs changes before to be merged ?

Additional changes in @clementroche's PR https://github.com/theatre-js/theatre/pull/367, can you merge those in? 😬

Closing in favor of #367


Refactor login page

As requested in https://github.com/go-gitea/gitea/pull/31504#issuecomment-2196196646. This PR refactor the login page:

Changes

[x] use separate box for passkey login and go to registration
[x] move forgot passoword next to password label
[x] fix password required label * and padding
[x] remove tabs from login page

Looks sexy, one issue that I see is the spacing below the Password text is not equal to the one below Username, please make it use the same spacing as below Username:

Oh and I would make the "Register Account" button also full width.

Looks sexy, one issue that I see is the spacing below the Password text is not equal to the one below Username, please make it use the same spacing as below Username:

Do you have an idea how to do this "nicely"? Problem was that the label is now nested in a div to be able to have the forgot password link at the right, however the required and padding is broken.

Did some tweaks on signup, button is full width, captchas are centered:

Not sure I like the logo on the signin page, it does take away a bit of vertical space and there is already a logo on the header.

Thanks for the adjustments.

Not sure I like the logo on the signin page, it does take away a bit of vertical space and there is already a logo on the header.

True, its not perfect yet. Without the logo it looked a bit too much like a dashboard card to me, but the header and the logo underneath isn't nice as well.
Could you check if we can somehow get the red required star for the password back.

Could you check if we can somehow get the red required star for the password back.

Hmm it looks like Fomantic UI's CSS expects the label as a direct descendant:
.ui.form .required.field > label::after

So we likely need to remove the wrapper and find other solutions.

But we also just can't add it to label as the ::after would appear after the link:

This will need a bit of hacky CSS. Luckily this indicator is not interactive and seem to be a pure CSS feature.

Found a solution with display: grid. It's the least hacky fix I could think of.

Removed the logo and did some smaller adjustments. PR should be ready from my side now.

Removed the logo and did some smaller adjustments. PR should be ready from my side now.

Could you also update the screenshots?

Sure updated them.


[ERD]  In palette view "Pin" btn does nothing

Description
For now by clicking on the header, it always collapses the section, and by clicking on the arrow, the entire palette always collapses
https://github.com/dbeaver/dbeaver/assets/84867187/c4969e21-ac73-470c-8e0c-af56edfa2f6e
DBeaver Version
23.1.0
Operating System
No response
Database and driver
No response
Steps to reproduce
No response
Additional context
No response

It prevents group from collapsing if there's not enough space. This is the default GEF behavior, and it can't be changed.
https://github.com/dbeaver/dbeaver/assets/35821147/75d27374-71d0-4ae2-a5b5-f3b3988fe5d8


HDDS-11252. Statistics of some storage space indicators

What changes were proposed in this pull request?
In SCM, there are no statistics related to storage space, such as Capacity, Scmused, remaining, NonScmused. These indicators are very useful, and the purpose of this PR is to improve them.
Below is the effect after adding this patch.
jmx:

ui:

What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-11252
How was this patch tested?
You need to ensure that JMX is displayed correctly.
You need to ensure that the UI is displayed correctly.

Can you help review this PR, @ivandika3  @devabhishekpal.
Thanks.

@jianghuazhu Btw, although the PR is not large, let's try our best to avoid force pushing a PR that's already being reviewed since the reviewer needs to review the whole patch again, instead of the latest changes.

Thanks @ivandika3 .
I'll keep an eye out for that in the future.

@jianghuazhu Thanks for the patch.


[stable/sonarqube] Fix for issue #10195

What this PR does / why we need it:  allow latest docker image for sonarqube to be used with this chart fix issue #10195
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #10195

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped

/ok-to-test

/assign

/retest

Details on the DCO here: https://github.com/helm/charts/pull/10196/checks?check_run_id=45484289
Has a couple commands that should sort it out.

Hi @rjkernick I have attempted these commands and its just making things worse as
the commits by others are now being signed off my me and its not happy. for example below

Junior<EMAIL_ADDRESS>but got "cpanato<EMAIL_ADDRESS>Commit sha: f6f2a9e, Author: Carlos Tadeu Panato Junior, Committer: Melissa Palmer; Expected "Carlos Tadeu Panato Junior<EMAIL_ADDRESS>but got "cpanato<EMAIL_ADDRESS>Commit sha: 4f796b7, Author: Carlos Tadeu Panato Junior, Committer: Melissa Palmer; Expected "Carlos Tadeu Panato Junior<EMAIL_ADDRESS>but got "cpanato<EMAIL_ADDRESS>
I started with 2 commit issues, did the commands as recommended and it then when to 44 issues
I now redid them and getting 96 issues.
I am not sure how to sort this out now.

Closing this PR will attempt to submit another as am unable to sort out the DCO from

reopening as I have the same issue when opening a new PR now anyawys

Closing this PR will attempt to submit another as am unable to sort out the DCO from


When removing sender, do not remove all receivers

Fix pls
https://github.com/nfowl/quilkin-controller/blob/master/internal/store/store.go#L97
ALso, pls add back sends in reconciliation loop

v0.2.1 should fix the main issue but won't cleanup created configmap's or internal xds snapshots due to a couple of workarounds introduced. If namespace/proxyName is not changing often the above won't cause any major issues.
Will leave this open to address the workarounds introduced

Thanks for the speedy turn around!

Reopened ticket after reading your response properly. Sorry @nfowl


Day 21 - overlapping classes

Resolves #51

Pull Request Test Coverage Report for Build 125

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 123:
0.0%

Covered Lines:
24

Relevant Lines:
24

💛  - Coveralls


nydusify: introduce chunkdict generate subcommand

Brief introduction
Add functionlity to generate chunk dictionary by database file and algorithm "exponential_smoothing"
Implement the command nydus-image chunkdict generate --database  command
Basic Usage
nydus-image chunkdict generate --database ./metadata.db
Details
Write command “nydus-image chunkdict generate” entries
Call the database interface and get the chunk information in the database
Implement the exponential smoothing algorithm and obtain chunk dictionary
To be continued, dump chunk dictionary and save, and then compact chunk

@cslinwang The broken CI needs to be fixed: https://github.com/dragonflyoss/nydus/actions/runs/9747241399/job/26899471236?pr=1572


Atomic rollback does not occur when POST request fails part way through

Could you shed any light on this? Thanks?

what is the issue? what DRF version? etc

If I am posting a large dataset and the request is interrupted before finishing then partial data remains in my database and the transactions are not rolled back. The DRF version is 2.4.3. Thanks for the fast reply!

Not sure what is an easy answer for this. DRF-bulk uses DRF serializers to save bulk data since its introduction (e.g. many=True). You can try overriding some logic in serializers save logic to preserve atomic behavior.

Okay, thanks for your help!


bower install fails to get git://github.com/nickholub/angular-ui-dashboard.git"

bower.json file has configured: "angular-ui-dashboard": "~0.8.2",
bower install fails to get git://github.com/nickholub/angular-ui-dashboard.git"
There is not such project in https://github.com/nickholub/

... sorry seems to be a bower config issue:
git config --global url."http://".insteadOf git://

If someone else stumbles across this issue:
The native git transport uses TCP port 9418, so you have to make sure your firewall accepts connections through this port.
Otherwise I would strongly recommend using https and NOT http as @rguembes suggests.


Show "expected in 2024" chip for performance rebates

Description
For now the only incentive of this kind is the federal "HER"
efficiency rebates program, which is starting to roll out
state-by-state this year, like the other IRA rebates. Show the same
timeline warning chip.
The old embed already says "2024" for that incentive, which is the
same as it does for the IRA appliance rebates.
https://app.asana.com/0/1204738794846444/1206453631604688
Test Plan
Search for weatherization projects with a low income; make sure the
"Federal Home Efficiency Rebates" result has the chip.

Confirming this looks right at https://embed-rewiringamerica-org-git-owenhomes-rewiring-america.vercel.app/state-calculator.html


[$500]  LHN-App crashes on long pressing any report in the LHN

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: 1.3.85-0
Reproducible in staging?: Y
Reproducible in production?: N
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: Applause-Internal Team
Slack conversation: @
Action Performed:

Launch app
Long press any report in the LHN

Expected Result:
App must not crash on long pressing any report in the LHN. It must show options to pin and mark as unread.
Actual Result:
App crashes on long pressing any report in the LHN instead of showing options to pin and mark as unread.
Workaround:
Unknown
Platforms:

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

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

Screenshots/Videos

Android: Native
https://github.com/Expensify/App/assets/115492554/1312bd94-d73e-4527-9861-24a2d2bd1ad4
logg.txt

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

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

Upwork Job URL: https://www.upwork.com/jobs/~01eb485ef172e2dd5f
Upwork Job ID:<PHONE_NUMBER>975524864
Last Price Increase: 2023-10-17

Not replroducible in production
https://github.com/Expensify/App/assets/115492554/83e05b08-fe68-4678-ba77-13a25ab587ae

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

this PR cause regression https://github.com/Expensify/App/pull/28846

Proposal
Please re-state the problem that we are trying to solve in this issue.
LHN-App crashes on long pressing any report in the LHN
What is the root cause of that problem?
https://github.com/Expensify/App/blob/main/src/libs/DomUtils/index.native.ts
https://github.com/Expensify/App/blob/91e2120e647aa9ee22171b6dbb772b4aebe64992/src/components/LHNOptionsList/OptionRowLHN.js#L189
here DomUtils.getActiveElement() will be null in the native devices
What changes do you think we should make in order to solve the problem?
DomUtils.getActiveElement() && DomUtils.getActiveElement().blur()

or we can add if condiiton
if(DomUtils.getActiveElement()) {
DomUtils.getActiveElement().blur()

The author of the PR that caused this regression will be fixing this.

@narefyev91
Can you review this PR?

@narefyev91 Can you review this PR?

On it

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
https://github.com/Expensify/App/assets/28352309/ccce8010-c1e2-444d-ac7e-5e3396f53e5d
https://github.com/Expensify/App/assets/28352309/efa36df7-d4b2-42a4-85d4-fc5987f2732c

Mobile Web - Chrome
https://github.com/Expensify/App/assets/28352309/e4d0911d-b7be-49ed-a83e-f58cefad84ed

Mobile Web - Safari
https://github.com/Expensify/App/assets/28352309/747423cb-237e-4724-bfe6-607b9adcec7f

Desktop
https://github.com/Expensify/App/assets/28352309/9d58eac4-03bf-4214-9414-92b12787acca

iOS
https://github.com/Expensify/App/assets/28352309/10487bdc-6b14-4891-aa68-7339bc393caf

Android

@narefyev91 to complete checklist then we can close!

The PR that introduced the bug has been identified. Link to the PR - https://github.com/Expensify/App/pull/28846
The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment https://github.com/Expensify/App/issues/29746#issuecomment-1766106884
A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion - N/A - it was quickly fixed in staging
Determine if we should create a regression test for this bug - N/A


[BUG]captchas.io Not working in 1.2.2

Says An error has occurred on balance check.
Working fine in 1.2.1

Could you kindly provide an api key we can use for testing this? Send it to Ruri on forum.openbullet.dev

Please register an account, i dont have a key i asked for a refund from them.

@openbullet I know this issue is a bit old, but I would be happy to provide you a working api key to investigate if you are still willing to look into it

Let's work


Add documentation, Makefile, and linting

Documentation and linting
More linting and documentation
usb_exceptions.py and the sign_*.py files pass linting checks
More linting and documentation
More linting and documentation
pylint: ignore too-few-public-methods
Spacing
Linting
Linting
Documentation
Linting
Create .readthedocs.yml
Create requirements.txt
Add documentation link to README
Update README.rst
Update README.rst
Update README.rst
Update .gitignore
Add call graphs
pylint and flake8 pass
Documentation
Documentation fixes
Add my Travis CI and Coveralls badges (#2)
Add some tables of contents to the documentation
Add linting to CI (#3)

Add linting to CI

Install flake8 and pylint

Hide the original repo's badges (for now) (#4)
Finish documentation skeletons for the sign_* files and usb_exceptions.py (#5)
Finish documentation skeletons for fastboot.py and fastboot_debug.py (#6)
Almost done with documentation skeletons
Finish documentation skeletons
Add contents to module docstrings
Working on documentation contents
Finish adding contents to module docstrings
Replace sections with rubrics
Document the sign_* modules and usb_exceptions.py
Remove whitespace
Fix typo
Add tests for the signers
Change 'ValueError' to more general 'Exception'
Added tests for the 'GetPublicKey()' methods
Add ADB keygen functionality (from @joeleong)
Fix sign_* tests
Add debugging code, work on documentation of filesync_protocol.py
Working on documentation
Remove debugging code
Fill in some documentation
Documentation and code formatting
Add some documentation
More documentation
Put command onto one line
Linting
Linting
Update documentation index.rst
Remove CHECKLIST.md

Coverage increased (+6.02%) to 49.735% when pulling ab99e77ef3c1a58f19597b0c34c93bd6dc56a1f3 on JeffLIrion:documentation into f4e597fe55900651a8a91fccc1e09061fd96b5e9 on google:master.

I know that this pull request is pretty extensive and difficult to review.  To help with this, I created two branches on my fork:

The master branch from this repo with comments removed and black code formatting
My documentation branch with comments removed and black code formatting

Here is a pull request from the latter to the former: https://github.com/JeffLIrion/python-adb/pull/7/files
If you look through the changes, you'll see that there are no breaking changes.


JVM 13.0.1+ crash: void OopOopIterateDispatch::Table::oop_oop_iterate<InstanceKlass, unsigned int>(ShenandoahMarkRefsClosure*, oopDesc*, Klass*)+0xf3

Platform:
Linux ip-172-31-18-15 4.9.0-11-amd64 AdoptOpenJDK/openjdk-build#1 SMP Debian 4.9.189-3+deb9u1 (2019-09-20) x86_64 GNU/Linux
kops Version 1.15.0 (git-9992b4055)
Architecture:
AWS EC2 t3.small
Please describe the issue that you are having with our binaries and if possible how to recreate it.
JVM crashed with message:
[1930537.203s][info][gc] Trigger: Time since last GC (300003 ms) is larger than guaranteed interval (300000 ms)
[1930537.205s][info][gc] GC(6433) Concurrent reset 388M->388M(512M) 1.542ms
[1930537.207s][info][gc] GC(6433) Pause Init Mark 1.920ms
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fba7aee5ee3, pid=24, tid=26
#
# JRE version: OpenJDK Runtime Environment (13.0.1+9) (build 13.0.1+9-201911081227)
# Java VM: OpenJDK 64-Bit Server VM (13.0.1+9-201911081227, mixed mode, sharing, tiered, compressed oops, shenandoah gc, linux-amd64)
# Problematic frame:
# V  [libjvm.so+0xd97ee3]  void OopOopIterateDispatch<ShenandoahMarkRefsClosure>::Table::oop_oop_iterate<InstanceKlass, unsigned int>(ShenandoahMarkRefsClosure*, oopDesc*, Klass*)+0xf3
#
# Core dump will be written. Default location: /lightstreamer/core
#
# An error report file with more information is saved as:
# /lightstreamer/hs_err_pid24.log
Compiled method (c1)<PHONE_NUMBER> 42447       3       com.github.benmanes.caffeine.cache.PSWMS::newNode (17 bytes)
 total in heap  [0x00007fba62071710,0x00007fba62071ee8] = 2008
 relocation     [0x00007fba62071870,0x00007fba620718d0] = 96
 main code      [0x00007fba620718e0,0x00007fba62071c60] = 896
 stub code      [0x00007fba62071c60,0x00007fba62071d08] = 168
 oops           [0x00007fba62071d08,0x00007fba62071d10] = 8
 metadata       [0x00007fba62071d10,0x00007fba62071d38] = 40
 scopes data    [0x00007fba62071d38,0x00007fba62071e40] = 264
 scopes pcs     [0x00007fba62071e40,0x00007fba62071ee0] = 160
 dependencies   [0x00007fba62071ee0,0x00007fba62071ee8] = 8
#
# If you would like to submit a bug report, please visit:
#   https://github.com/AdoptOpenJDK/openjdk-build/issues
#
Aborted (core dumped)
+ result=134

Full log attached
server.log.gz

Please share a project that reproduces the problem. While you are at it, test with http://jdk.java.net/14/.
If we do not hear back within a week, we are going to close the issue.

Hi @aahlenst,
thank you for reply.
Unfortunately the bug is not reproducible.
We switched on JDK 14.0.1, we will update you for further issues.

running into this again, on pycharm-community version 2020.2:
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fe2cb4a3518, pid=16599, tid=16603
#
# JRE version: OpenJDK Runtime Environment (11.0.7+10) (build 11.0.7+10-b944.20)
# Java VM: OpenJDK 64-Bit Server VM (11.0.7+10-b944.20, mixed mode, tiered, compressed oops, concurrent mark sweep gc, linux-amd64)
# Problematic frame:
# V  [libjvm.so+0xabe518]  void OopOopIterateDispatch<MarkAndPushClosure>::Table::oop_oop_iterate<InstanceKlass, unsigned int>(MarkAndPushClosure*, oopDesc*, Klass*)+0x178
#
# No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/user/java_error_in_PYCHARM_16599.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#
Aborted

@hivemall Do you have steps to reproduce?

not available, yet reoccuring crashes, sths off, here the log
---------------  S U M M A R Y ------------

Command Line: -Xms128m -Xmx977m -XX:ReservedCodeCacheSize=240m -XX:+UseConcMarkSweepGC -XX:SoftRefLRUPolicyMSPerMB=50 -ea -XX:CICompilerCount=2 -Dsun.io.useCanonPrefixCache=false -Djava.net.preferIPv4Stack=true -Djdk.http.auth.tunneling.disabledSchemes="" -XX:+HeapDumpOnOutOfMemoryError -XX:-OmitStackTraceInFastThrow -Djdk.attach.allowAttachSelf=true -Dkotlinx.coroutines.debug=off -Djdk.module.illegalAccess.silent=true -Dawt.useSystemAAFontSettings=lcd -Dsun.java2d.renderer=sun.java2d.marlin.MarlinRenderingEngine -Dsun.tools.attach.tmp.only=true -XX:ErrorFile=/home/user/java_error_in_PYCHARM_%p.log -XX:HeapDumpPath=/home/user/java_error_in_PYCHARM.hprof -Didea.vendor.name=JetBrains -Didea.paths.selector=PyCharmCE2020.2 -Djb.vmOptionsFile=/home/user/.config/JetBrains/PyCharmCE2020.2/pycharm64.vmoptions -Didea.platform.prefix=PyCharmCore com.intellij.idea.Main

---------------  T H R E A D  ---------------

Current thread (0x00007fe2c40de000):  VMThread "VM Thread" [stack: 0x00007fe2c8264000,0x00007fe2c8364000] [id=16603]

Stack: [0x00007fe2c8264000,0x00007fe2c8364000],  sp=0x00007fe2c8360880,  free space=1010k
Native frames: (J=compiled Java code, A=aot compiled Java code, j=interpreted, Vv=VM code, C=native code)
V  [libjvm.so+0xabe518]  void OopOopIterateDispatch<MarkAndPushClosure>::Table::oop_oop_iterate<InstanceKlass, unsigned int>(MarkAndPushClosure*, oopDesc*, Klass*)+0x178
V  [libjvm.so+0xabbe49]  MarkSweep::follow_stack()+0x89
V  [libjvm.so+0xcf96bb]  JavaThread::oops_do(OopClosure*, CodeBlobClosure*)+0x3b
V  [libjvm.so+0xcfef5b]  Threads::possibly_parallel_oops_do(bool, OopClosure*, CodeBlobClosure*)+0x7b
V  [libjvm.so+0x7a4616]  GenCollectedHeap::process_roots(StrongRootsScope*, GenCollectedHeap::ScanningOption, OopClosure*, CLDClosure*, CLDClosure*, CodeBlobToOopClosure*)+0x66
V  [libjvm.so+0x7a4945]  GenCollectedHeap::full_process_roots(StrongRootsScope*, bool, GenCollectedHeap::ScanningOption, bool, OopsInGenClosure*, CLDClosure*, OopStorage::ParState<false, false>*)+0x55
V  [libjvm.so+0x7a797b]  GenMarkSweep::mark_sweep_phase1(bool)+0x1fb
V  [libjvm.so+0x7a9911]  GenMarkSweep::invoke_at_safepoint(ReferenceProcessor*, bool)+0xd1
V  [libjvm.so+0x6270e8]  CMSCollector::do_compaction_work(bool)+0x248
V  [libjvm.so+0x62a161]  CMSCollector::acquire_control_and_collect(bool, bool)+0x141
V  [libjvm.so+0x7a579a]  GenCollectedHeap::collect_generation(Generation*, bool, unsigned long, bool, bool, bool, bool)+0x27a
V  [libjvm.so+0x7a6a38]  GenCollectedHeap::do_collection(bool, bool, unsigned long, bool, GenCollectedHeap::GenerationType)+0xc58
V  [libjvm.so+0x7a6f35]  GenCollectedHeap::satisfy_failed_allocation(unsigned long, bool)+0x115
V  [libjvm.so+0xd67a43]  VM_GenCollectForAllocation::doit()+0x53
V  [libjvm.so+0xd68f77]  VM_Operation::evaluate()+0xe7
V  [libjvm.so+0xd6ecd7]  VMThread::evaluate_operation(VM_Operation*) [clone .constprop.71]+0xc7
V  [libjvm.so+0xd6f398]  VMThread::loop()+0x5b8
V  [libjvm.so+0xd6f6b3]  VMThread::run()+0x73
V  [libjvm.so+0xd00d39]  Thread::call_run()+0x149
V  [libjvm.so+0xb741de]  thread_native_entry(Thread*)+0xee

siginfo: si_signo: 11 (SIGSEGV), si_code: 2 (SEGV_ACCERR), si_addr: 0x00000000d24ac058

If you haven't reconfigured PyCharm to use another JVM, it is using the one built and bundled by JetBrains which is different than OpenJDK. You could try and report it to JetBrains. If you have reconfigured PyCharm, it is at least not using AdoptOpenJDK (but that's not really important). Without reproduction steps, it's very unlikely that anyone can work on it, as annoying as the crash is.


Add toggle to change timezone to UTC for Nakama Console graphs

Should fix https://github.com/heroiclabs/nakama/issues/703 /cc @mofirouz
I only see charts in the Status page.
Please do tell me if there charts in some other page and I'll updated them too!
Demo:
https://github.com/user-attachments/assets/65da2d71-b291-4113-8384-d562389c7505

Rebased with latest master

This LGTM but I'd kindly ask @jpntex to give it a second pass.


Added greaterThan and lessThan validations

Description
Added greaterThan and lessThan validations.

Does min/max not work for you?
http://jqueryvalidation.org/min-method/
http://jqueryvalidation.org/max-method/

will close for now, feel free to discuss it furhter. we can re-open when required.

it is something like that, but in the min / max methods it is using greaterThanOrEqual, I'm using the greaterThan not Equal


CassandraTask reconcile fails with json unmarshal error

What happened?
I have created a task
apiVersion: control.k8ssandra.io/v1alpha1
kind: CassandraTask
metadata:
  name: rebuild-dc2
spec:
  datacenter:
    name: dc2
    namespace: cassandra
  jobs:
    - name: rebuild-dc2
      command: rebuild
      args:
        source_datacenter: dc1

But I found it only triggered rebuild on a single pod.
What did you expect to happen?
I expected task to be triggered on all 3 pods of my datacenter.
How can we reproduce it (as minimally and precisely as possible)?
Create a task to rebuild datacenter, check operator's logs.
cass-operator version
v1.17.2
Kubernetes version
v1.27.4
Method of installation
Helm
Anything else we need to know?
Here is my findings:
When I create a task, it's being created on the pod-0:
kubectl -n hsm-db get pod cluster1-dc2-default-sts-0 -o yaml | yq .metadata | grep job
  control.k8ssandra.io/job-ffedaf36-a81a-413f-9635-f4796e7e611c: '{"id":"b4d23d4f-8d9a-40d8-b0c8-d3b5595593ea","handler":"management-api"}'

Since .spec.concurrencyPolicy is Forbid, task is being executed on the first pod and is waiting to completion status sent back before proceeding with the next pod.
On cass-operator pod I can see following logs (I have omitted pod json output):
2023-10-18T13:21:23.451Z	INFO	calling Management API features - GET /api/v0/metadata/versions/features	{"controller": "cassandratask", "controllerGroup": "control.k8ssandra.io", "controllerKind": "CassandraTask", "CassandraTask": {"name":"rebuild-dc2","namespace":"cassandra"}, "namespace": "cassandra", "name": "rebuild-dc2", "reconcileID": "9bf92e19-1fe9-4eaa-b828-60847e63dba6", "pod": "cluster1-dc2-default-sts-0"}
2023-10-18T13:21:23.451Z	INFO	client::callNodeMgmtEndpoint	{"controller": "cassandratask", "controllerGroup": "control.k8ssandra.io", "controllerKind": "CassandraTask", "CassandraTask": {"name":"rebuild-dc2","namespace":"cassandra"}, "namespace": "cassandra", "name": "rebuild-dc2", "reconcileID": "9bf92e19-1fe9-4eaa-b828-60847e63dba6"}
2023-10-18T13:21:23.469Z	INFO	calling Management API keyspace rebuild - POST /api/v1/ops/node/rebuild	{"controller": "cassandratask", "controllerGroup": "control.k8ssandra.io", "controllerKind": "CassandraTask", "CassandraTask": {"name":"rebuild-dc2","namespace":"cassandra"}, "namespace": "cassandra", "name": "rebuild-dc2", "reconcileID": "9bf92e19-1fe9-4eaa-b828-60847e63dba6", "pod": "cluster1-dc2-default-sts-0"}
2023-10-18T13:21:23.469Z	INFO	client::callNodeMgmtEndpoint	{"controller": "cassandratask", "controllerGroup": "control.k8ssandra.io", "controllerKind": "CassandraTask", "CassandraTask": {"name":"rebuild-dc2","namespace":"cassandra"}, "namespace": "cassandra", "name": "rebuild-dc2", "reconcileID": "9bf92e19-1fe9-4eaa-b828-60847e63dba6"}
2023-10-18T13:21:23.512Z	INFO	calling Management API features - GET /api/v0/metadata/versions/features	{"controller": "cassandratask", "controllerGroup": "control.k8ssandra.io", "controllerKind": "CassandraTask", "CassandraTask": {"name":"rebuild-dc2","namespace":"cassandra"}, "namespace": "cassandra", "name": "rebuild-dc2", "reconcileID": "742e0ae3-3511-4eb2-bf96-9257b12659da", "pod": "cluster1-dc2-default-sts-0"}
2023-10-18T13:21:23.512Z	INFO	client::callNodeMgmtEndpoint	{"controller": "cassandratask", "controllerGroup": "control.k8ssandra.io", "controllerKind": "CassandraTask", "CassandraTask": {"name":"rebuild-dc2","namespace":"cassandra"}, "namespace": "cassandra", "name": "rebuild-dc2", "reconcileID": "742e0ae3-3511-4eb2-bf96-9257b12659da"}
2023-10-18T13:21:23.546Z	INFO	calling Management API features - GET /api/v0/ops/executor/job	{"controller": "cassandratask", "controllerGroup": "control.k8ssandra.io", "controllerKind": "CassandraTask", "CassandraTask": {"name":"rebuild-dc2","namespace":"cassandra"}, "namespace": "cassandra", "name": "rebuild-dc2", "reconcileID": "742e0ae3-3511-4eb2-bf96-9257b12659da", "pod": "cluster1-dc2-default-sts-0"}
2023-10-18T13:21:23.546Z	INFO	client::callNodeMgmtEndpoint	{"controller": "cassandratask", "controllerGroup": "control.k8ssandra.io", "controllerKind": "CassandraTask", "CassandraTask": {"name":"rebuild-dc2","namespace":"cassandra"}, "namespace": "cassandra", "name": "rebuild-dc2", "reconcileID": "742e0ae3-3511-4eb2-bf96-9257b12659da"}
2023-10-18T13:21:23.849Z	ERROR	Could not get JobDetails for pod	{"controller": "cassandratask", "controllerGroup": "control.k8ssandra.io", "controllerKind": "CassandraTask", "CassandraTask": {"name":"rebuild-dc2","namespace":"cassandra"}, "namespace": "cassandra", "name": "rebuild-dc2", "reconcileID": "742e0ae3-3511-4eb2-bf96-9257b12659da", "Pod": {<omitted>}, "error": "json: cannot unmarshal number into Go struct field JobDetails.submit_time of type string"}
github.com/k8ssandra/cass-operator/internal/controllers/control.(*CassandraTaskReconciler).reconcileEveryPodTask
	/workspace/internal/controllers/control/cassandratask_controller.go:619
github.com/k8ssandra/cass-operator/internal/controllers/control.(*CassandraTaskReconciler).Reconcile
	/workspace/internal/controllers/control/cassandratask_controller.go:326
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:122
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:323
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:274
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.14.6/pkg/internal/controller/controller.go:235

So the reason seems to be here:
Struct: https://github.com/k8ssandra/cass-operator/blob/34e2ae63e5cb38acbba32f2c62cfd34f62d9cb24/pkg/httphelper/client.go#L115-L122
And it's being unmarshalled here:
https://github.com/k8ssandra/cass-operator/blob/34e2ae63e5cb38acbba32f2c62cfd34f62d9cb24/pkg/httphelper/client.go#L1088
it gets data from /api/v0/ops/executor/job?job_id=%s
If I curl API I get a number, not a string:
curl <IP_ADDRESS>:8080/api/v0/ops/executor/job?job_id=b4d23d4f-8d9a-40d8-b0c8-d3b5595593ea
{"id":"b4d23d4f-8d9a-40d8-b0c8-d3b5595593ea","type":"rebuild","status":"COMPLETED","submit_time":1697635283476,"end_time":1697635285454,"error":null,"status_changes":[]}

And API doc says submit_time is an integer, not string: https://github.com/k8ssandra/management-api-for-apache-cassandra/blob/master/management-api-server/doc/openapi.json#L2153-L2160
       {
          "submit_time" : {
            "type" : "integer",
            "format" : "int64"
          },
          "type" : {
            "type" : "string"
          }
        }

Am I missing something obvious or this is a bug? I'm doubt as this code was not changed for a quite a long time.
Thank you!

Just found a test is being added here https://github.com/k8ssandra/cass-operator/pull/584/files#diff-8975636a650e4f693ea9fc9c9870311666765068357bdaabc06bc7573c41457b
If what I described is correct then this test might be failing exactly because of type mismatch @burmanm

That's right, thank you @burmanm!
Now I can see it was updated to string here https://github.com/k8ssandra/management-api-for-apache-cassandra/commit/c46d8f9eca884b9f3f8a0a128dca61e586288f71
I wonder if it should be updated in the api doc as well https://github.com/k8ssandra/management-api-for-apache-cassandra/blob/master/management-api-server/doc/openapi.json#L2153-L2156?
I'll close the issue, thanks again.

No, the "int64" is correct there, that's the type of data that's in the field. But JSON can't serialize int64, instead it serializes all the numbers as float64, so that would cause certain numbers to be incorrectly serialized/deserialized. Thus, they need to be serialized as strings to retain all the information.