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

GDE @ command reports success after executing good command files #193

Closed
nars1 opened this issue Apr 4, 2018 · 0 comments
Closed

GDE @ command reports success after executing good command files #193

nars1 opened this issue Apr 4, 2018 · 0 comments
Assignees
Labels
Milestone

Comments

@nars1
Copy link
Collaborator

nars1 commented Apr 4, 2018

Final Release Note

The GDE @ command reports success after executing good command files. In r1.20, it would issue a YDB-E-IOEOF error even after sucessfully executing the commands in the file specfied. A workaround was to set the environment variable ydb_msgprefix to "GTM" for the GDE process. (#193)

Description

This is an issue I noticed in r1.20 GDE when using the @ syntax.

> gde @tmp.com
%GDE-I-GDUSEDEFS, Using defaults for Global Directory 
        /extra1/testarea1/nars/test/temp/tmp/tmp/mumps.gld
%GDE-I-EXECOM, Executing command file /extra1/testarea1/nars/test/temp/tmp/tmp/tmp.com

**%YDB-E-IOEOF, Attempt to read past an end-of-file**
%GDE-I-VERIFY, Verification OK

%GDE-I-GDCREATE, Creating Global Directory file 
        /extra1/testarea1/nars/test/temp/tmp/tmp/mumps.gld

Draft Release Note

GDE @ syntax works correctly. In r1.20, it used to issue a YDB-E-IOEOF error even though it executed the file pointed to by the @. A workaround for this was to set the environment variable ydb_msgprefix to "GTM" for the duration of the GDE @ usage. (#193)

@nars1 nars1 added the bug label Apr 4, 2018
@nars1 nars1 self-assigned this Apr 4, 2018
@nars1 nars1 added this to the r130 milestone Apr 4, 2018
nars1 added a commit to nars1/YottaDB that referenced this issue Apr 6, 2018
This is an issue in r1.20 after the ydb_msgprefix changes which caused the default
message prefix to be "YDB" instead of "GTM". This means the actual error GDE gets
when the end of <filename> is reached is YDB-E-IOEOF whereas GDE was still looking
for GTM-E-IOEOF. This is now fixed to search for -E-IOEOF since the message prefix
can be variable (depending on the ydb_msgprefix env var contents).
nars1 added a commit to nars1/YottaDB that referenced this issue Apr 6, 2018
nars1 added a commit to nars1/YottaDB that referenced this issue Apr 6, 2018
nars1 added a commit to nars1/YottaDB that referenced this issue Apr 6, 2018
nars1 added a commit to nars1/YottaDB that referenced this issue Apr 6, 2018
nars1 added a commit to nars1/YottaDB that referenced this issue Apr 6, 2018
nars1 added a commit that referenced this issue Apr 6, 2018
This is an issue in r1.20 after the ydb_msgprefix changes which caused the default
message prefix to be "YDB" instead of "GTM". This means the actual error GDE gets
when the end of <filename> is reached is YDB-E-IOEOF whereas GDE was still looking
for GTM-E-IOEOF. This is now fixed to search for -E-IOEOF since the message prefix
can be variable (depending on the ydb_msgprefix env var contents).
nars1 added a commit that referenced this issue Apr 6, 2018
nars1 added a commit that referenced this issue Apr 6, 2018
nars1 added a commit that referenced this issue Apr 6, 2018
nars1 added a commit that referenced this issue Apr 6, 2018
nars1 added a commit that referenced this issue Apr 6, 2018
@nars1 nars1 closed this as completed Apr 6, 2018
@ksbhaskar ksbhaskar changed the title GDE @ syntax results in YDB-E-IOEOF error GDE @ command reports success after executing good command files May 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant