Dgraph: Health endpoint doesn't show a version when built from master

Created on 24 Jun 2020  路  8Comments  路  Source: dgraph-io/dgraph

Health endpoint doesn't show a version (at 8080/health) when built from master - This causes a block on Ratel UI. Also, any Dgraph version will get blocked by this. Not sure if this needs to be fixed on Dgraph itself or Ratel. Pinging @paulftw.

2 potential bugs (both true, not sure if both can be solved at Dgraph side)
1 - When using master, ratel thinks I'm using an old version.
2 - Got "Unsupported Content-Type".

What version of Dgraph are you using?

Master

Have you tried reproducing the issue with the latest release?

yes

What is the hardware spec (RAM, OS)?

Darwin 32GB

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

  1. Build Dgraph from master or any PR.
  2. Start Dgraph's cluster built from master and run Ratel.
  3. Connect Ratel to http://localhost:8080

Captura de Tela 2020-06-24 a虁s 11 55 45

Captura de Tela 2020-06-24 a虁s 11 58 24

  1. Now open the console (F12)

You might see in some moment an error like:

Login Failed http://localhost:8080 Error: Pre v1.1 clients do not support Login methods

Also several errors like:

serverAclState error t: Unsupported Content-Type. Supported content types are application/json, application/graphql+-

This is a normal health endpoint

Captura de Tela 2020-06-24 a虁s 11 45 27

And this is the one from master/PR builds.

Captura de Tela 2020-06-24 a虁s 11 45 17

Expected behaviour and actual result.

That it should work with master builds.

areusability exbeginner statuaccepted

All 8 comments

Also the dgraph version that is being passed as argument while building go is incorrect. If you execute git describe of master branch, we get v2.0.0-beta1-508-g931b8a81b instead of v20.07.0-beta.Jun22.

I can work on this.

I'm on master and also getting the error Pre v1.1 clients do not support Login methods

Any updates on this? Thanks

Raised a PR for this.

@rahulgurnani This fixes the issue with the wrong tag. But the issue with empty values continues. Anyway, I have found that this happens only with go build. And I think the issue is that, we have to discourage users from building it with golang build. They must use make dgraph.

Yes they should be using make install. This also happens when running dgraph in debug mode.

Sure, in VScode debug mode this is a blocker. We can't use Ratel there. Se we need a "default" value set for cases like that.

Github issues have been deprecated.
This issue has been moved to discuss. You can follow the conversation there and also subscribe to updates by changing your notification preferences.

drawing

Was this page helpful?
0 / 5 - 0 ratings

Related issues

xhochipe picture xhochipe  路  3Comments

allen-munsch picture allen-munsch  路  4Comments

fritzblue picture fritzblue  路  5Comments

MichelDiz picture MichelDiz  路  3Comments

pjebs picture pjebs  路  4Comments