-
Notifications
You must be signed in to change notification settings - Fork 63
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
getting Layout Error! Scheme found before folio entry. when i try to clone and run the code #20
Comments
Hi Sandeep Somasekharan,
Please find the attach screenshot
Regards
Bharath B
…On Wed, Jan 13, 2021 at 4:20 PM Sandeep Somasekharan < ***@***.***> wrote:
If you don't mind, can you please send me a cropped screenshot of just the
first scheme entry from the CAS (with all personal data removed) ?
something like
[image: cas_screenshot]
<https://user-images.githubusercontent.com/8553055/104442504-2997ed80-55bb-11eb-832c-be807f19a53f.jpg>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABIZ2QN74ZPLMTYJXP7N57DSZV3GZANCNFSM4WAR5MHA>
.
|
looks like you missed to attach the file |
I have attached the file, still, I have attached once again.
[image: Screen Shot 2021-01-13 at 4.24.07 PM.png]
…On Wed, Jan 13, 2021 at 4:32 PM Sandeep Somasekharan < ***@***.***> wrote:
looks like you missed to attach the file
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABIZ2QIQDMBW4G7Q727GMV3SZV4TTANCNFSM4WAR5MHA>
.
|
do let me know once the issue is resolved
Regards
Bharath B
…On Wed, Jan 13, 2021 at 4:58 PM Bharath B ***@***.***> wrote:
I have attached the file, still, I have attached once again.
[image: Screen Shot 2021-01-13 at 4.24.07 PM.png]
On Wed, Jan 13, 2021 at 4:32 PM Sandeep Somasekharan <
***@***.***> wrote:
> looks like you missed to attach the file
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#20 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABIZ2QIQDMBW4G7Q727GMV3SZV4TTANCNFSM4WAR5MHA>
> .
>
|
The image is still not visible here. Looks like github doesn't support attaching images in "Reply via email" . Can you please email me the file if you are having issues uploading it here? My email is available in my profile. [codereverser .at. gmail .dot. com] |
Many thanks! |
any idea on how to reimport the changes you have done because when I uninstall the requirements and reinstall it using pip, I think it's reinstalling from the cache. |
the previous error seems to be resolved, but getting below error
casparser.exceptions.CASParseError: Unable to parse investor data |
I've pushed a new version to sort the issues . Try installing it by
If the error still persists, please give via API, data = read_cas_pdf(filename, password, force_pdfminer=True) or via CLI,
|
even after adding the above parameter the error still persists
with Cli getting below error |
fixed in 76cf582 |
I installed the latest package still getting same issue "Unable to parse investor data" |
In that case, it would be difficult to fix this without looking at the actual CAS file (or at least the layout of investor info). It is working for all the sample files I have. May be the contact details are in a different format than the ones I've seen. Can you please send me the casparser version?
|
Version : 0.7.4 |
CAS file would be super helpful. many thanks! may be it is some regression bug in one of the new releases. my email id is there in the profile https://github.com/codereverser |
Hi
when I try to run the example shown in README.md, getting the below error
raise CASParseError("Layout Error! Scheme found before folio entry.")
casparser.exceptions.CASParseError: Layout Error! Scheme found before folio entry.
not sure if I have missed anything, the statement was downloaded from CAMS on 13/01/2021
The text was updated successfully, but these errors were encountered: