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

AriocE/baseEncode.cpp 1263: buffer capacity exceeded #35

Closed
jarrettrios opened this issue Jun 17, 2024 · 3 comments
Closed

AriocE/baseEncode.cpp 1263: buffer capacity exceeded #35

jarrettrios opened this issue Jun 17, 2024 · 3 comments

Comments

@jarrettrios
Copy link

Hello again!

I've been running into the title as an error and can't see why exactly its happening. Other references run fine!

AriocE v1.52.3142.24159 (release) +2024-06-07T20:55:42
Copyright (c) 2015-2024 Johns Hopkins University.  All rights reserved.
 compiled             : 2024-06-13T15:49:58 (GNU g++ v11.4.0)
 data type sizes      : int=4 long=8 *=8 Jvalue5=5 Jvalue8=8 JtableHeader=5 (little-endian)
 computer name        : 94e17f383007
 operating system     : Ubuntu 22.04.4 LTS
 executable file      : /Arioc.x.152/src/AriocE
 configuration file   : /mnt/ramdisk/kraken/experiments/Kraken_Test_V3/encode_gapped_reference.cfg
AriocE::encodeR: encoding 1 file (48 CPU threads available)...
ApplicationException ([0x00000019] AriocE/baseEncode.cpp 1263): buffer capacity exceeded (136/112 bytes)
Command exited with return code 1

Here is the cfg and the reference.fa file. I had to add a .txt to the end of the file name to be able to upload them to github

encode_gapped_reference.cfg.txt
reference_templates.fa.txt

@RWilton
Copy link
Owner

RWilton commented Jun 24, 2024

Yikes! AriocE isn't properly digesting that simple FASTA file.

I will dig into this, try to produce a more informative failure message, and fix any bug that I find.

[Update: I am able to reproduce the error message, but I have not yet identified the problem. I will post a solution as soon as possible.]

[Update: The error message is accurate. It's one of those "this should never happen" sanity checks that does indeed trap an internal buffer allocation error. I will fix this bug and post an updated "pre-release" build tomorrow.]

@RWilton
Copy link
Owner

RWilton commented Jun 24, 2024

This bug is fixed in the current Arioc release (v1.52.3143).

@RWilton RWilton closed this as completed Jun 24, 2024
@jarrettrios
Copy link
Author

Exciting, thank you!

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

No branches or pull requests

2 participants