-
Notifications
You must be signed in to change notification settings - Fork 236
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
Ensure ckb run
Automatically Creates default.db-options
if Missing in data_dir
#4671
Labels
t:enhancement
Type: Feature, refactoring.
Comments
default.db-options
file after ckb run
?default.db-options
if Missing in data_dir
default.db-options
if Missing in data_dirckb run
Automatically Creates default.db-options
if Missing in data_dir
eval-exec
added a commit
to eval-exec/ckb
that referenced
this issue
Oct 28, 2024
eval-exec
added a commit
to eval-exec/ckb
that referenced
this issue
Oct 28, 2024
Signed-off-by: Eval EXEC <[email protected]>
eval-exec
added a commit
to eval-exec/ckb
that referenced
this issue
Oct 28, 2024
Signed-off-by: Eval EXEC <[email protected]>
eval-exec
added a commit
to eval-exec/ckb
that referenced
this issue
Oct 28, 2024
Signed-off-by: Eval EXEC <[email protected]>
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
eval-exec
added a commit
to eval-exec/ckb
that referenced
this issue
Nov 13, 2024
Signed-off-by: Eval EXEC <[email protected]>
eval-exec
added a commit
to eval-exec/ckb
that referenced
this issue
Nov 13, 2024
Signed-off-by: Eval EXEC <[email protected]>
eval-exec
added a commit
to eval-exec/ckb
that referenced
this issue
Nov 14, 2024
Signed-off-by: Eval EXEC <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Request
Is your feature request related to a problem? Please describe.
When running
ckb run
, it would be ideal if the absence of thedefault.db-options
file in thedata_dir
doesn't prevent the launch. It might be best forckb run
to check if thedefault.db-options
file exists indata_dir
during the initialization process, and if not, create it automatically.Describe the solution you'd like
create
default.db-options
file automatically if it doesn't exists.The text was updated successfully, but these errors were encountered: