search

Open-EO / openeo-backend-validator

Service to validate back-end compliance with the API specification.
Apache License 2.0
1 stars 3 forks source link

received 'panic' #45

Open kempenep opened 4 years ago

kempenep commented 4 years ago

When I tried to run the openeoct, I get a 

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x38 pc=0x7da0f0]

goroutine 1 [running]:
main.build_url(0xc00012eac0, 0x15, 0x8a3a5d, 0x1, 0x0, 0xb83d40)
    /home/kempepi/openeo_service/openeo-backend-validator/openeoct/openeoct.go:130 +0x50
main.(*ComplianceTest).loadCapabilities(0xc0001d8000)
    /home/kempepi/openeo_service/openeo-backend-validator/openeoct/openeoct.go:735 +0x6c
main.(*ComplianceTest).appendConfig(0xc0001d8000, 0xc00012eac0, 0x15, 0xc00012eb00, 0x12, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
    /home/kempepi/openeo_service/openeo-backend-validator/openeoct/openeoct.go:868 +0x78c
main.main.func1(0xc00013ac40, 0x1, 0x1)
    /home/kempepi/openeo_service/openeo-backend-validator/openeoct/openeoct.go:902 +0xd8
github.com/urfave/cli.(*Command).Run(0xc000130360, 0xc00013ab80, 0x0, 0x0)
    /home/kempepi/go/src/github.com/urfave/cli/command.go:163 +0x4ed
github.com/urfave/cli.(*App).RunContext(0xc000124300, 0x932b80, 0xc000116000, 0xc000102150, 0x3, 0x3, 0x0, 0x0)
    /home/kempepi/go/src/github.com/urfave/cli/app.go:306 +0x81f
github.com/urfave/cli.(*App).Run(...)
    /home/kempepi/go/src/github.com/urfave/cli/app.go:217
main.main()

I was using this configuration:

openapi = "openapi_1_0_0.json"
username = ""
password = ""
authurl = ""
output = "jrc_v1"

[endpoints]
  [endpoints.collections]
  id = "endpoint1"
  url = "/collections/"
  request_type = "GET"
bgoesswe commented 4 years ago

You need to at least provide the URL of the backend you want to test to, so the url config needs to be set in the config file. Please have a look at the example configurations especially this one. If you want to test for deliverable 28 I would recommend to look at the config files at this repository

bgoesswe commented 4 years ago

But of course, there should be a better response from the tool, so I'll add some useful error messages for incomplete/wrong config files.

kempenep commented 4 years ago

Thanks for the links. I omitted the private IP address of my personal computer. I think the issue was I only provided the IP without the "http://". by adding the "http://" there was not the error message