Skip to content

Read OASIS files with large property strings#2319

Closed
abdelq wants to merge 5 commits intoKLayout:masterfrom
abdelq:abdelq/usrwnotzsnnk
Closed

Read OASIS files with large property strings#2319
abdelq wants to merge 5 commits intoKLayout:masterfrom
abdelq:abdelq/usrwnotzsnnk

Conversation

@abdelq
Copy link
Copy Markdown
Contributor

@abdelq abdelq commented Apr 5, 2026

I have some OAS files written by KLayout (through Kfactory) that can't be opened with it because of large metadata strings (e.g. JSON blobs).

I've also had to make some changes to RPATH in order to be able to run KLayout and the test.

I've avoided changing the InflateFilter logic, since I'm making the assumption that there is are performance concerns regarding the fixed buffer size.

@stefanottili
Copy link
Copy Markdown

Could you comment on what kind of metadata takes up 42k characters ?

@klayoutmatthias
Copy link
Copy Markdown
Collaborator

Thanks for the PR, but:

could you please first file an issue and give me a chance to look at that? The buffer length should not have anything to do with the maximum number of bytes you can read into a string. If that is limited, the problem is somewhere else and the solution should not be OASIS specific.

Matthias

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

Successfully merging this pull request may close these issues.

3 participants