Airat Arifullin aarifullin
  • Joined on 2023-03-16
aarifullin pushed to fix/ape_root_parsing at aarifullin/frostfs-node 2025-01-15 11:23:29 +00:00
4cb509e0e1 [#1601] util: Correctly parse 'root' name for container resources
aarifullin created pull request TrueCloudLab/frostfs-node#1601 2025-01-15 11:22:59 +00:00
Correctly parse 'root' name for container resources
aarifullin pushed to fix/ape_root_parsing at aarifullin/frostfs-node 2025-01-15 11:22:38 +00:00
71c2655376 [#XX] util: Correctly parse 'root' name for container resources
aarifullin created branch fix/ape_root_parsing in aarifullin/frostfs-node 2025-01-15 11:21:45 +00:00
aarifullin pushed to fix/ape_root_parsing at aarifullin/frostfs-node 2025-01-15 11:21:45 +00:00
97cf307947 [#XX] util: Correctly parse 'root' name for container resources
eff95bd632 [#1598] engine: Drop unnecessary result structs
fb928616cc [#1598] golangci: Enable unparam linter
4d5ae59a52 [#1598] golangci: Enable unconvert linters
a9f27e074b [#1243] object: Look for X-Headers within origin before APE check
Compare 10 commits »
aarifullin commented on pull request TrueCloudLab/frostfs-node#1481 2025-01-15 09:58:46 +00:00
local_object_storage: Guarantee graves removal when handling expired tombstones

SetTombstoneAddress have been, obviously, responsible for setting tombstone address :) And I think we shouldn't change its prototype as you don't set tombstone's address relying on expiration epoch.

aarifullin commented on pull request TrueCloudLab/frostfs-node#1481 2025-01-15 07:52:11 +00:00
local_object_storage: Guarantee graves removal when handling expired tombstones

Not a big deal, but the prototype with return values (epoch uint64, found bool, err error) (has -> found) looks more natural for Go. WDYT?

aarifullin opened issue TrueCloudLab/frostfs-node#1599 2025-01-14 10:20:19 +00:00
Object won't be deleted if shards are out of free space
aarifullin commented on pull request TrueCloudLab/frostfs-node#1597 2025-01-13 09:47:28 +00:00
Look for X-Headers within metaheader origin before APE check

The nesting can be more than 2 (theoretically).

Getting meta from origin (if it's present) should be enough for ape

aarifullin commented on pull request TrueCloudLab/frostfs-node#1597 2025-01-13 09:46:50 +00:00
Look for X-Headers within metaheader origin before APE check

The method is no longer actual as I used the approach suggested by @dstepanov-yadro

aarifullin commented on pull request TrueCloudLab/frostfs-node#1597 2025-01-13 09:45:26 +00:00
Look for X-Headers within metaheader origin before APE check

It's very-very good point. Fixed!

aarifullin pushed to fix/1243_xheaders at aarifullin/frostfs-node 2025-01-13 09:45:03 +00:00
4091fb64fa [#1243] object: Look for X-Headers within origin before APE check
aarifullin created pull request TrueCloudLab/frostfs-node#1597 2025-01-10 13:34:50 +00:00
Look for X-Headers within metaheader origin before APE check
aarifullin created branch fix/1243_xheaders in aarifullin/frostfs-node 2025-01-10 13:30:17 +00:00
aarifullin pushed to fix/1243_xheaders at aarifullin/frostfs-node 2025-01-10 13:30:17 +00:00
50a4df4324 [#1243] object: Look for X-Headers within origin before APE check
dc410fca90 [#1590] adm: Accept many accounts in proxy-* commands
cddcd73f04 [#1590] adm: Make --account flag required in proxy-* commands
d7fcc5ce30 [#1586] objsvc: Allow to send search response in multiple messages
c0221d76e6 [#1577] node/container: Fix typo
Compare 10 commits »
aarifullin commented on pull request TrueCloudLab/xk6-frostfs#190 2025-01-10 11:41:55 +00:00
Allow to log date in k6 scenarios

You have removed only the last line and it affected first line although there is no changes in JS. It seems it didn't have linefeed after the comment? And we should add it after js?