Skip to content

fix: orphan object client detector #672

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

fenos
Copy link
Contributor

@fenos fenos commented Apr 21, 2025

What kind of change does this PR introduce?

Bug fix

What is the new behavior?

Client-side tool to interact with the object scanner to list and/or detect orphan objects.

Additional context

This tool has 2 commands: list and delete
In both operations, detected orphans' references are saved to disk.

Is recommended to run the list command before delete

@coveralls
Copy link

coveralls commented Apr 21, 2025

Pull Request Test Coverage Report for Build 14575349690

Details

  • 50 of 56 (89.29%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.03%) to 77.579%

Changes Missing Coverage Covered Lines Changed/Added Lines %
src/internal/streams/ndjson.ts 50 56 89.29%
Totals Coverage Status
Change from base Build 14422171405: 0.03%
Covered Lines: 16454
Relevant Lines: 21043

💛 - Coveralls

import path from 'path'

const ADMIN_URL = ''
const ADMIN_API_KEY = ''
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we pull these values from process.env instead? I'd just like to eliminate the chance of accidentally pushing a commit with secrets. Using node 20+ we can just use the --env-file flag so we don't need any 3rd party libraries to support this.

@fenos fenos force-pushed the fix/orphan-client branch from b29a7ae to e58e9a6 Compare April 21, 2025 14:36
@fenos fenos force-pushed the fix/orphan-client branch from e58e9a6 to c0e4d8f Compare April 21, 2025 14:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants