Skip to content

Not able to use blosc2 directly in AWS lambda #501

@piyushrpt

Description

@piyushrpt

Describe the bug

  • The call to lscpu in core.get_cache_info results in Permission denied: 'lscpu' in AWS lambda environment
  • This should probably raise a ValueError as suggested in this commit - 2623fe8
  • Is there a workaround by setting any env variables?

To Reproduce
Steps to reproduce the behavior:

  1. Can be reproduced in AWS lambda by importing the module

Expected behavior
Not to fail and work with defaults, as is the case when no information is found resulting in a ValueError being raised by get_cache_info.

Desktop (please complete the following information):

  • OS: Ubuntu24.04

Additional context
This happens on AWS lambda as the functions don't run with root privileges. We can workaround this by building containers and setting permissions within them but it would be useful to be able to use blosc2 directly as a python package for lambda functions.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions