-
-
Notifications
You must be signed in to change notification settings - Fork 507
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
segmentation fault while try to create a local backup in a dolthub/dolt-sql-server:1.7.5 docker image #6365
Comments
Hey @chicco785, thank you for taking the time to report this. I was able to repro the segfault. On first look, I believe this is happening either because In the meantime, to get you unblocked, try running
I then ran
Let us know if that helps! I'm happy to take a look at our |
Hi @chicco785 , Thanks for using Dolt and filing this. We'd love to learn more about your Dolt use case too. If you'd like to share, feel free to email me or swing by our Discord. |
thx @fulghum,
I assumed it was the destination directory to create the backup. |
hi @bpf120 , if you think it's an interesting usecase, happy to have a meeting or drop you an email. |
@chicco785 super interesting! :) Want to send me an email and we can try to talk next week? |
You are correct, Jason misspoke. The cause of the error is that this command must be run inside a dolt database directory. % dolt init
Successfully initialized dolt data repository.
zachmu@zachmu-thinkpad:zachmu/dolt-scratch/b6365% mkdir backup
zachmu@zachmu-thinkpad:zachmu/dolt-scratch/b6365% dolt backup add local-backup file://./backup
zachmu@zachmu-thinkpad:zachmu/dolt-scratch/b6365% cd backup
zachmu@zachmu-thinkpad:dolt-scratch/b6365/backup% dolt backup add local-backup file://./
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x18b1b95]
goroutine 1 [running]:
github.com/dolthub/dolt/go/libraries/doltcore/env.(*DoltEnv).AddBackup(0xc0006202d0, {{0x7fffc26f31ef, 0xc}, {0x7fffc26f31fc, 0x9}, {0xc00057b7c0, 0x1, 0x1}, 0xc00067e780})
/c/Users/zachmu/liquidata/go-workspace/src/github.com/dolthub/dolt/go/libraries/doltcore/env/environment.go:882 +0x75
github.com/dolthub/dolt/go/cmd/dolt/commands.addBackup(0xc0006202d0, 0xc00067e750)
/c/Users/zachmu/liquidata/go-workspace/src/github.com/dolthub/dolt/go/cmd/dolt/commands/backup.go:180 +0x485
github.com/dolthub/dolt/go/cmd/dolt/commands.BackupCmd.Exec({}, {0x2d087d8, 0xc00072b780}, {0xc000642e80, 0xb}, {0xc0000520c0, 0x3, 0x3}, 0x55bdd00?, {0x0, ...})
/c/Users/zachmu/liquidata/go-workspace/src/github.com/dolthub/dolt/go/cmd/dolt/commands/backup.go:119 +0x1e5
github.com/dolthub/dolt/go/cmd/dolt/cli.SubCommandHandler.handleCommand({{0x2451cf6, 0x4}, {0x2470ff6, 0x11}, {0x0, 0x0}, {0x553ed20, 0x32, 0x32}, 0x0}, ...)
/c/Users/zachmu/liquidata/go-workspace/src/github.com/dolthub/dolt/go/cmd/dolt/cli/command.go:244 +0x4ec
github.com/dolthub/dolt/go/cmd/dolt/cli.SubCommandHandler.Exec({{0x2451cf6, 0x4}, {0x2470ff6, 0x11}, {0x0, 0x0}, {0x553ed20, 0x32, 0x32}, 0x0}, ...)
/c/Users/zachmu/liquidata/go-workspace/src/github.com/dolthub/dolt/go/cmd/dolt/cli/command.go:193 +0x4b8
main.runMain()
/c/Users/zachmu/liquidata/go-workspace/src/github.com/dolthub/dolt/go/cmd/dolt/dolt.go:545 +0x2a1e
main.main()
/c/Users/zachmu/liquidata/go-workspace/src/github.com/dolthub/dolt/go/cmd/dolt/dolt.go:204 +0x19
zachmu@zachmu-thinkpad:dolt-scratch/b6365/backup% I'm fixing the panic and updating the docs, and I'll close this when I have. |
I am try to add a local backup from a
dolthub/dolt-sql-server:1.7.5
docker image and I get a segmentation fault as result:i am running the test on mac book pro with m2
The text was updated successfully, but these errors were encountered: