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

Excel database importer #858

Closed
Zoophobus opened this issue Oct 7, 2022 · 3 comments
Closed

Excel database importer #858

Zoophobus opened this issue Oct 7, 2022 · 3 comments
Assignees
Labels
prio:high Issues that are high priority

Comments

@Zoophobus
Copy link
Contributor

The excel database importer appears to be featuring a range of bugs related to memory based issues. These issues are related to the brightway2 importer and need to be dealt with either in brightway, or in the generation of the software environment.

An example of an unsuccessful importation process in GNU/Linux is as follows:
Applying strategy: strip_biosphere_exc_locations Applying strategy: set_code_by_activity_hash Applying strategy: link_iterable_by_fields Applying strategy: assign_only_product_as_production Applying strategy: link_technosphere_by_activity_hash Applying strategy: drop_falsey_uncertainty_fields_but_keep_zeros Applying strategy: convert_uncertainty_types_to_integers Applying strategy: hash_parameter_group Applying strategy: convert_activity_parameters_to_list Applied 19 strategies in 16.90 seconds Could not link exchanges, here are 10 examples.: [{'amount': 0.00262, 'database': 'super_ei38_REMIND_el_20220923', free(): invalid pointer

Another encountered error is segmentation faults both typical of faulty memory handling.
In contrast errors in Windows occur as errors with Peewee, any inclusion of these errors here would be appreciated

@Zoophobus
Copy link
Contributor Author

Zoophobus commented Oct 11, 2022

In Peewee update logs 3.15.1 there is a fix for an issue introduced by sqlite 3.39.0. Versions that were present in my environment with the above errors. My apologies this is not a fix, these errors still occur on importing databases!

@Zoophobus Zoophobus added the prio:high Issues that are high priority label Oct 12, 2022
@simb-sdu
Copy link

@Zoophobus I have a problem that might be related to this. did you find any workaround?
#1021

@marc-vdm
Copy link
Member

Closing as resolved in #1011

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
prio:high Issues that are high priority
Projects
None yet
Development

No branches or pull requests

4 participants