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.

Sign up for GitHub

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

Jump to bottom

Backport EOS patch about GELF 1.1 unstringified numbers #997

Open
abitmore opened this issue May 30, 2018 · 3 comments
Open

Backport EOS patch about GELF 1.1 unstringified numbers #997

abitmore opened this issue May 30, 2018 · 3 comments
Milestone
7.1.0 - Feature R...

Comments

@abitmore
Copy link
Member

EOSIO/eos@2d980b4

Note: I believe GELF logging is not used by default in BitShares, although node admins can try it.

Easy task but low priority.
@jmjatlanta
Copy link
Contributor

jmjatlanta commented May 30, 2018 •
edited
Loading

EOSIO/eos#2458

It seems that if GELF is set up to use udp, a network "would_block" error could needlessly cause problems. The PR above should have fixed it in EOS. We should look at doing something similar.

This may deserve its own ticket, but placing it here until more research is completed.

Update: Created issue #1005 to track the GELF/udp issues.

@pmconrad
Copy link
Contributor

Related: EOSIO/eos@b2be860

@pmconrad
Copy link
Contributor

Related to udp would_block: EOSIO/eos@9224efe

@jmjatlanta jmjatlanta mentioned this issue May 30, 2018
Open
@pmconrad pmconrad mentioned this issue Sep 24, 2019
Open
@abitmore abitmore added this to the 4.1.0 - Feature Release milestone Sep 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
7.1.0 - Feature Release
Development

No branches or pull requests
3 participants
@jmjatlanta @pmconrad @abitmore