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

Error loading custom configuration #43

Closed
nseba opened this issue Aug 16, 2020 · 7 comments
Closed

Error loading custom configuration #43

nseba opened this issue Aug 16, 2020 · 7 comments
Labels
bug Something isn't working

Comments

@nseba
Copy link

nseba commented Aug 16, 2020

Hello,

The jog tool is really awesome, but I've tried to provide it a custom configuration for better parsing pino logs using the -t option to generate a template. Unfortunately this fails with the following golang error:

home/seba/.jog.yaml: yaml: unmarshal errors:
  line 1: cannot unmarshal !!str `/home/s...` into map[string]interface {}

I'm not an experienced golang programmer, but I could track the following issue which seems to be related to this:
go-yaml/yaml#139

@qiangyt
Copy link
Owner

qiangyt commented Aug 19, 2020

Which version of jog you're using?
And could you paste your home/seba/.jog.yaml ?

@qiangyt
Copy link
Owner

qiangyt commented Sep 21, 2020

Close because unable to reproduce and no further response from original reporter

@qiangyt qiangyt closed this as completed Sep 21, 2020
@frudolph77
Copy link
Contributor

frudolph77 commented Oct 9, 2020

I just got the same error.

I'm using version 0.9.14
I've redirected the output of jog -t to .jog.yaml

I would use this as a base to customize it, leaving it unchanged and starting jog leads to this error.

I've check the file with a yaml validators and it is valid.

SMALL Update:
using the very same file with the -c parameter works fine

@qiangyt
Copy link
Owner

qiangyt commented Oct 9, 2020

I just got the same error.

I'm using version 0.9.14
I've redirected the output of jog -t to .jog.yaml

I would use this as a base to customize it, leaving it unchanged and starting jog leads to this error.

I've check the file with a yaml validators and it is valid.

SMALL Update:
using the very same file with the -c parameter works fine

I see your point and now can reproduce it, Thanks! Will fix it

@qiangyt qiangyt reopened this Oct 9, 2020
@qiangyt
Copy link
Owner

qiangyt commented Oct 9, 2020

Fixed by commit: cea3edb.
Release v0.9.15 for this fix as well.

@qiangyt qiangyt closed this as completed Oct 9, 2020
@frudolph77
Copy link
Contributor

WOW, this was fast. Thanks, works like a charm.

@qiangyt qiangyt added the bug Something isn't working label Oct 10, 2020
@qiangyt
Copy link
Owner

qiangyt commented Oct 10, 2020

@frudolph77 , prev commit has a critical regression, please use new v0.9.15.1, instead

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants