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

ydb_subscript_next_s(nonexistentVariable) gives back "0" #347

Closed
pkoper opened this issue Dec 7, 2018 · 1 comment
Closed

ydb_subscript_next_s(nonexistentVariable) gives back "0" #347

pkoper opened this issue Dec 7, 2018 · 1 comment

Comments

@pkoper
Copy link

pkoper commented Dec 7, 2018

ydb_subscript_next_s() for nonexistent local returns next subscript "0"

Running https://gist.github.com/pkoper/53ee72ab35bbfcbfdabec2710e3085e1 prints:

next(x)
rc = 0, next.len_used = 1, next.buf_addr = |0|
set(x, val)
next(x)
rc = 0, next.len_used = 0, next.buf_addr = ||

Expected result:

next(x)
rc = 0, next.len_used = 0, next.buf_addr = ||
set(x, val)
next(x)
rc = 0, next.len_used = 0, next.buf_addr = ||
@nars1
Copy link
Collaborator

nars1 commented Dec 7, 2018

@pkoper : Thanks for the report. This is tracked at https://gitlab.com/YottaDB/DB/YDB/issues/394 (we migrated to gitlab a while back) and will be fixed in the upcoming r1.24 release.

@nars1 nars1 closed this as completed Jan 7, 2019
ChristopherEdwards pushed a commit to ChristopherEdwards/YottaDB that referenced this issue Jun 3, 2019
@nars1
[YottaDB#347] Issue error at start of ydbinstall if any one of needed…
b75bf6c 
… utilities is not installed on the system (!351)

We had a failure with ydbinstall.sh on a CentOS 7.5 docker image while trying to install the utf8 directory.
This turned out to be due to the absence of the "file" utility which ydbinstall.sh/configure.gtc assumed.

This is now fixed by checking for the existence of "file" and various other utilities assumed by the
ydbinstall.sh/configure.gtc scripts at the start of ydbinstall.sh. And issuing an error and exiting
if at least one of the needed utilities is not found.

The check is done using the "command -v" command of the POSIX sh. This is the recommended approach for
checking the existence of a utility instead of the 'which' command. So existing 'which' usages have been
replaced too.
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
No milestone
Development

No branches or pull requests
2 participants
@pkoper @nars1