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

Inconsistent error messages on empty pools #151

Closed
ydahhrk opened this Issue Apr 20, 2015 · 1 comment

Comments

Projects
None yet
1 participant
@ydahhrk
Member

ydahhrk commented Apr 20, 2015

NAT64 Jool:

$ jool --pool4 --display
  (empty)

$ jool --pool6 --display
Object not found (System error -12)

SIIT Jool:

$ jool_siit --pool6 --display
Object not found (System error -12)

$ jool_siit --pool6791 --display
Object not found (System error -12)

$ jool_siit --blacklist --display
Object not found (System error -12)

$ jool_siit --eamt --display
  (empty)

(Assuming --pool4 and --eamt don't segfault - see #150.)

This doesn't cause any crying kids - all it is is visually inconsistent. While "(empty)" is the expected output, "Object not found (System error -12)" is not really misleading.

Thanks to Edgar Rodriguez for pointing this out.

@ydahhrk

This comment has been minimized.

Show comment
Hide comment
@ydahhrk

ydahhrk Aug 17, 2015

Member

Merged; closing.

Member

ydahhrk commented Aug 17, 2015

Merged; closing.

@ydahhrk ydahhrk closed this Aug 17, 2015

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