Skip to content

Conversation

@chancez
Copy link

@chancez chancez commented May 17, 2015

No description provided.

@philips
Copy link
Contributor

philips commented Jun 11, 2015

lgtm, could you add a MAINTAINERS file in this directory with your name?

@jonboulle
Copy link
Contributor

Copyright header please.

@chancez
Copy link
Author

chancez commented Jun 12, 2015

@jakedt @philips Done.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These don't match to the actual names

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's weird..I must have accidentally broken the tests in a rebase before I submitted the PR. Should be fixed. I also found a bug with something else, noted in a comment to this PR.

@chancez
Copy link
Author

chancez commented Jun 16, 2015

I found a small bug in my implementation with the Message field. Things were not marshalling correctly into it. I found a slightly better alternative to a getter method as well. I basically implement a custom Unmarshal function that handles the varying types of data from the journald Message field and store that data as a string on the struct's Message Field.

@chancez chancez force-pushed the gatewayd branch 2 times, most recently from b6fb0ff to 5219297 Compare June 17, 2015 00:03
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I adapted this from somewhere else to handle storing a string representation on the Entry struct.

http://www.freedesktop.org/wiki/Software/systemd/json/ has details about it. The []interface{} case should deal with non-printable non-utf8 characters. But I'm not 100% sure that's correct

@lucab
Copy link
Contributor

lucab commented Jun 14, 2017

@chancez I randomly stepped on this PR today. Do we still want to drive this toward master or should I just close this PR?

@ghost
Copy link

ghost commented Jun 14, 2017

Can one of the admins verify this patch?

@chancez
Copy link
Author

chancez commented Jun 14, 2017

@lucab It can be closed, but I also see no reason it couldn't be merged.

@lucab
Copy link
Contributor

lucab commented Jun 15, 2017

@chancez I seem to understand the original usecase is not anymore pressing. While I don't have any particular issue with this PR, I see this is mostly just an HTTP API client not strictly related to libsystemd. I'm closing this for now, but I think it can be easily resurrected or split in its own projects if there is any need for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants