Skip to content
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

"panic: runtime error: invalid memory address or nil pointer dereference" when running "jfrog rt npmp" #1306

Open
SomaSharath opened this issue Nov 23, 2021 · 3 comments
Labels
bug Something isn't working

Comments

@SomaSharath
Copy link

SomaSharath commented Nov 23, 2021

Describe the bug
When running jfrog rt npmp --build-name={} --build-number={} , I get the following (similar to #1297 )

[Info] Running npm Publish
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0xb9f71e]

goroutine 1 [running]:
github.com/jfrog/jfrog-cli-core/v2/artifactory/commands/npm.(*NpmPublishCommand).preparePrerequisites(0xc00023d600)
	/root/go/pkg/mod/github.com/jfrog/jfrog-cli-core/[email protected]/artifactory/commands/npm/publish.go:192 +0xfe
github.com/jfrog/jfrog-cli-core/v2/artifactory/commands/npm.(*NpmPublishCommand).Run(0xc00023d600)
	/root/go/pkg/mod/github.com/jfrog/jfrog-cli-core/[email protected]/artifactory/commands/npm/publish.go:138 +0x77
github.com/jfrog/jfrog-cli-core/v2/common/commands.Exec({0xf192e0, 0xc00023d600})
	/root/go/pkg/mod/github.com/jfrog/jfrog-cli-core/[email protected]/common/commands/command.go:26 +0xad
github.com/jfrog/jfrog-cli/artifactory.npmPublishCmd(0xc0000d2f20)
	/var/jenkins_home/workspace/eco-system/release/jfrog-cli-release/temp/jfrog-cli/artifactory/cli.go:1197 +0x1cf
github.com/jfrog/jfrog-cli/artifactory.GetCommands.func33(0x1)
	/var/jenkins_home/workspace/eco-system/release/jfrog-cli-release/temp/jfrog-cli/artifactory/cli.go:537 +0x19
github.com/codegangsta/cli.HandleAction({0xc8cdc0, 0xe06e28}, 0xb)
	/root/go/pkg/mod/github.com/codegangsta/[email protected]/app.go:490 +0x5a
github.com/codegangsta/cli.Command.Run({{0xdbcd6a, 0xb}, {0x0, 0x0}, {0xc00023a770, 0x1, 0x1}, {0x0, 0x0}, {0x0, ...}, ...}, ...)
	/root/go/pkg/mod/github.com/codegangsta/[email protected]/command.go:210 +0x8f8
github.com/codegangsta/cli.(*App).RunAsSubcommand(0xc000222680, 0xc0000d2c60)
	/root/go/pkg/mod/github.com/codegangsta/[email protected]/app.go:379 +0x985
github.com/codegangsta/cli.Command.startApp({{0xdb6baa, 0x2}, {0x0, 0x0}, {0x0, 0x0, 0x0}, {0x0, 0x0}, {0x0, ...}, ...}, ...)
	/root/go/pkg/mod/github.com/codegangsta/[email protected]/command.go:298 +0x6bb
github.com/codegangsta/cli.Command.Run({{0xdb6baa, 0x2}, {0x0, 0x0}, {0x0, 0x0, 0x0}, {0x0, 0x0}, {0x0, ...}, ...}, ...)
	/root/go/pkg/mod/github.com/codegangsta/[email protected]/command.go:98 +0x418
github.com/codegangsta/cli.(*App).Run(0xc0002224e0, {0xc0000300a0, 0x5, 0x5})
	/root/go/pkg/mod/github.com/codegangsta/[email protected]/app.go:255 +0x6ac
main.execMain()

To Reproduce
After I've upgraded the jFrog cli version to 2.6.1 the command fails with the above error, works fine with v2.5.1 version of cli.

Expected behavior
Publishing npm package should not throw an error.

Screenshots
If applicable, add screenshots to help explain your problem.

Versions

  • JFrog CLI version: 2.6.1
  • JFrog CLI operating system: Alpine Linux v3.11
  • Artifactory Version: 7.24.4

Additional context
As a temporary fix, I have rolled back the cli version to 2.5.1 and it works as expected.

@SomaSharath SomaSharath added the bug Something isn't working label Nov 23, 2021
@RobiNino RobiNino mentioned this issue Nov 24, 2021
3 tasks
@RobiNino
Copy link
Contributor

Hi @SomaSharath ,
Thank you for reporting this issue.
We just released version 2.6.2 that includes a fix.
We'd appreciate your feedback for it.

@sstephant
Copy link

Hi. The related issue #1297 mentionned is not fixed by version 2.6.2

@rsi-mrobinson
Copy link

Seeing this issue in 2.71.5 looks like it's been open for 3 years, so I'm assuming theres no hope of a fix from jfrog

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants