CLDSRV-838: Change startTime type to milliseconds since epoch by dvasilas · Pull Request #6056 · scality/cloudserver

dvasilas · 2026-01-22T09:55:55Z

Change the startTime field in server access logs from a formatted "seconds.milliseconds" string to milliseconds since Unix epoch.

bert-e · 2026-01-22T09:56:00Z

Hello dvasilas,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
`/after_pull_request`	Wait for the given pull request id to be merged before continuing with the current one.
`/bypass_author_approval`	Bypass the pull request author's approval	⭐
`/bypass_build_status`	Bypass the build and test status	⭐
`/bypass_commit_size`	Bypass the check on the size of the changeset `TBA`	⭐
`/bypass_incompatible_branch`	Bypass the check on the source branch prefix	⭐
`/bypass_jira_check`	Bypass the Jira issue check	⭐
`/bypass_peer_approval`	Bypass the pull request peers' approval	⭐
`/bypass_leader_approval`	Bypass the pull request leaders' approval	⭐
`/approve`	Instruct Bert-E that the author has approved the pull request.		✍️
`/create_pull_requests`	Allow the creation of integration pull requests.
`/create_integration_branches`	Allow the creation of integration branches.
`/no_octopus`	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
`/unanimity`	Change review acceptance criteria from `one reviewer at least` to `all reviewers`
`/wait`	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
`/help`	Print Bert-E's manual in the pull request.
`/status`	Print Bert-E's current status in the pull request `TBA`
`/clear`	Remove all comments from Bert-E from the history `TBA`
`/retry`	Re-start a fresh build `TBA`
`/build`	Re-start a fresh build `TBA`
`/force_reset`	Delete integration branches & pull requests, and restart merge process from the beginning.
`/reset`	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

bert-e · 2026-01-22T09:56:06Z

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.

dvasilas · 2026-01-22T14:20:06Z

/approve

bert-e · 2026-01-22T14:20:19Z

Conflict

A conflict has been raised during the creation of
integration branch w/9.3/improvement/CLDSRV-838 with contents from improvement/CLDSRV-838
and development/9.3.

I have not created the integration branch.

Here are the steps to resolve this conflict:

 git fetch
 git checkout -B w/9.3/improvement/CLDSRV-838 origin/development/9.3
 git merge origin/improvement/CLDSRV-838
 # <intense conflict resolution>
 git commit
 git push -u origin w/9.3/improvement/CLDSRV-838

The following options are set: approve

dvasilas · 2026-01-22T14:23:23Z

🤖

bert-e · 2026-01-22T14:28:54Z

Build failed

The build for commit did not succeed in branch w/9.3/improvement/CLDSRV-838

The following options are set: approve

bert-e · 2026-01-22T15:50:46Z

Incorrect fix version

The Fix Version/s in issue CLDSRV-838 contains:

9.2.18
9.3.0

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

9.2.19
9.3.0

Please check the Fix Version/s of CLDSRV-838, or the target
branch of this pull request.

The following options are set: approve

dvasilas · 2026-01-22T15:51:25Z

🤖

bert-e · 2026-01-22T15:51:40Z

History mismatch

Merge commit #44084e6f838e5dae971ffda8082ce0dedb0333a8 on the integration branch
w/9.3/improvement/CLDSRV-838 is merging a branch which is neither the current
branch improvement/CLDSRV-838 nor the development branch
development/9.3.

It is likely due to a rebase of the branch improvement/CLDSRV-838 and the
merge is not possible until all related w/* branches are deleted or updated.

Please use the reset command to have me reinitialize these branches.

The following options are set: approve

dvasilas · 2026-01-22T15:51:48Z

/reset

codecov · 2026-01-22T15:52:07Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.40%. Comparing base (f204ad4) to head (0f24499).
⚠️ Report is 6 commits behind head on development/9.2.
✅ All tests successful. No failed tests found.

Additional details and impacted files

Files with missing lines	Coverage Δ
lib/utilities/serverAccessLogger.js	`76.33% <ø> (-0.42%)`	⬇️

... and 1 file with indirect coverage changes

@@                 Coverage Diff                 @@
##           development/9.2    #6056      +/-   ##
===================================================
- Coverage            84.43%   84.40%   -0.04%     
===================================================
  Files                  206      206              
  Lines                13036    13033       -3     
===================================================
- Hits                 11007    11000       -7     
- Misses                2029     2033       +4

Flag	Coverage Δ
file-ft-tests	`67.48% <ø> (+<0.01%)`	⬆️
kmip-ft-tests	`28.08% <ø> (-0.04%)`	⬇️
mongo-v0-ft-tests	`68.73% <ø> (+<0.01%)`	⬆️
mongo-v1-ft-tests	`68.72% <ø> (+<0.01%)`	⬆️
multiple-backend	`35.38% <ø> (-0.01%)`	⬇️
sur-tests	`35.54% <ø> (-0.04%)`	⬇️
sur-tests-inflights	`37.38% <ø> (-0.01%)`	⬇️
unit	`69.92% <ø> (-0.01%)`	⬇️
utapi-v2-tests	`34.24% <ø> (-0.01%)`	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

bert-e · 2026-01-22T15:52:09Z

Reset complete

I have successfully deleted this pull request's integration branches.

The following options are set: approve

bert-e · 2026-01-22T15:52:31Z

Conflict

A conflict has been raised during the creation of
integration branch w/9.3/improvement/CLDSRV-838 with contents from improvement/CLDSRV-838
and development/9.3.

I have not created the integration branch.

Here are the steps to resolve this conflict:

 git fetch
 git checkout -B w/9.3/improvement/CLDSRV-838 origin/development/9.3
 git merge origin/improvement/CLDSRV-838
 # <intense conflict resolution>
 git commit
 git push -u origin w/9.3/improvement/CLDSRV-838

The following options are set: approve

dvasilas · 2026-01-22T15:54:42Z

🤖

BourgoisMickael · 2026-01-22T16:04:19Z

I'm trying to merge #6055 to go in the bump 9.2.19

bert-e · 2026-01-22T18:30:02Z

Build failed

The build for commit did not succeed in branch w/9.3/improvement/CLDSRV-838

The following options are set: approve

bert-e · 2026-01-22T18:33:46Z

In the queue

The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.

The changeset will be merged in:

✔️ development/9.2
✔️ development/9.3

The following branches will NOT be impacted:

development/7.10
development/7.4
development/7.70
development/8.8
development/9.0
development/9.1

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

Any commit you add on the source branch will trigger a new cycle after the
current queue is merged.
Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.

The following options are set: approve

bert-e · 2026-01-22T18:55:33Z

I have successfully merged the changeset of this pull request
into targetted development branches:

✔️ development/9.2
✔️ development/9.3

The following branches have NOT changed:

development/7.10
development/7.4
development/7.70
development/8.8
development/9.0
development/9.1

Please check the status of the associated issue CLDSRV-838.

Goodbye dvasilas.

anurag4DSB approved these changes Jan 22, 2026

View reviewed changes

fredmnl approved these changes Jan 22, 2026

View reviewed changes

nicolas2bert approved these changes Jan 22, 2026

View reviewed changes

dvasilas mentioned this pull request Jan 22, 2026

WKBCH-18: Fix version detection and update ClickHouse schema scality/workbench#61

Merged

dvasilas added 2 commits January 22, 2026 17:49

CLDSRV-838: Change startTime type to ms since epoch

294f26c

CLDSRV-838: Bump version to 9.2.19

0f24499

dvasilas force-pushed the improvement/CLDSRV-838 branch from 7aae6b6 to 0f24499 Compare January 22, 2026 15:50

BourgoisMickael approved these changes Jan 22, 2026

View reviewed changes

bert-e merged commit a4f17bb into development/9.2 Jan 22, 2026
29 checks passed

bert-e deleted the improvement/CLDSRV-838 branch January 22, 2026 18:55

Conversation

dvasilas commented Jan 22, 2026

Uh oh!

bert-e commented Jan 22, 2026

Hello dvasilas,

Uh oh!

bert-e commented Jan 22, 2026

Request integration branches

Uh oh!

dvasilas commented Jan 22, 2026

Uh oh!

bert-e commented Jan 22, 2026

Conflict

Uh oh!

dvasilas commented Jan 22, 2026

Uh oh!

bert-e commented Jan 22, 2026

Build failed

Uh oh!

bert-e commented Jan 22, 2026

Incorrect fix version

Uh oh!

dvasilas commented Jan 22, 2026

Uh oh!

bert-e commented Jan 22, 2026

History mismatch

Uh oh!

dvasilas commented Jan 22, 2026

Uh oh!

codecov bot commented Jan 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

bert-e commented Jan 22, 2026

Reset complete

Uh oh!

bert-e commented Jan 22, 2026

Conflict

Uh oh!

dvasilas commented Jan 22, 2026

Uh oh!

BourgoisMickael commented Jan 22, 2026

Uh oh!

bert-e commented Jan 22, 2026

Build failed

Uh oh!

bert-e commented Jan 22, 2026

In the queue

Uh oh!

bert-e commented Jan 22, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

codecov bot commented Jan 22, 2026 •

edited

Loading