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

Strange response when applying enterprise license #4965

Closed
Aelbannan opened this issue Mar 18, 2020 · 2 comments · Fixed by #5230
Closed

Strange response when applying enterprise license #4965

Aelbannan opened this issue Mar 18, 2020 · 2 comments · Fixed by #5230
Labels
area/enterprise Related to proprietary features kind/bug Something is broken. status/accepted We accept to investigate/work on it.

Comments

@Aelbannan
Copy link
Contributor

Aelbannan commented Mar 18, 2020

What version of Dgraph are you using?

v2.0.0-beta

Have you tried reproducing the issue with the latest release?

Yes

What is the hardware spec (RAM, OS)?

16 GB, Windows (Docker)

Steps to reproduce the issue (command/config used to run Dgraph).

Send a valid enterprise license to /enterpriseLicense

Expected behaviour and actual result.

Expected: Success message and license applied

Actual: License applied, but error message. See below:

{
    "errors": [
        {
            "message": "Done",
            "extensions": {
                "code": "Success"
            }
        }
    ]
}
@Aelbannan Aelbannan added area/enterprise Related to proprietary features kind/bug Something is broken. labels Mar 18, 2020
@sleto-it sleto-it added the status/accepted We accept to investigate/work on it. label Mar 18, 2020
@all-seeing-code
Copy link
Contributor

@Aelbannan Unable to repro this, if I apply a key on my end I get

{ "code": "Success", "message": "License applied." }

@all-seeing-code
Copy link
Contributor

@Aelbannan Unable to repro this, if I apply a key on my end I get

{ "code": "Success", "message": "License applied." }

I stand corrected. It was actually an issue. I have proposed a small PR as a fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/enterprise Related to proprietary features kind/bug Something is broken. status/accepted We accept to investigate/work on it.
Development

Successfully merging a pull request may close this issue.

3 participants