consul

expected result:
example.com?param=abc -> will become example.com
example.com/?param=abc -> will stay example.com/

actual result:
example.com?param=abc -> become example.com
example.com/?param=abc -> stays example.com/?param=abc

overview

Today, the RequestRecorder records service RPC calls. If those take less than < 0ms, the recorder marks them as 0ms.

proposal

Make the RequestRecorder report the elapsed time for service calls that take less than < 0ms as decimal values, instead of 0.

notes

testing

If you take this on, I'd kindly advise to start in a TDD fashion. Write a test

Before you submit this issue, you has been search all existed issues and search the documentation

• [] I've been search all existed issues
• [] I've been read all documentation

Describe your question

How should I use alicloud MNS?

Both parseInt and parseFloat take strings as arguments and convert them to 64 bit numbers of their appropriate type. The json.Number type is a string sub-type that contains integers or floats, but it causes a type error with the 2 parse functions. They should be change to accept json.Number fields and handle them appropriately.

Of the learning environments that leverage Ansible, very few are using roles. This can make porting Ansible playbooks across learning environments more difficult. To fix this, Ansible-using learning environments need to be refactored (where possible) to use an Ansible role.

Expected Behavior

It should show up as it used to be.

Screenshots/Logs

Currently