lablup / lablup/backend.ai

Error when permanently deleting VFolder with specific naming pattern in WebUI

Open
#3,152 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
670
Forks
183
Avg merge
17h 7m
Merged PRs (30d)
358

Description

When attempting to permanently delete a VFolder that has been moved to the trash, an error occurs if the folder name follows a specific pattern like "e2e-test-folder-sharing1732683913062". This issue can be reproduced in the Web UI. However, if the folder is shorter folder nam, such as `test`, it can be permanently deleted without any issues.

## Steps to Reproduce

1. Create a VFolder with a name following the pattern "e2e-test-folder-sharing1732683913062".
1. Move the VFolder to the trash.
1. Attempt to permanently delete the VFolder from the trash.
1. Observe the error.
## Expected Behavior

The VFolder should be permanently deleted without any errors, regardless of its name.

## Actual Behavior

An error occurs when trying to permanently delete the VFolder with a specific naming pattern.

## Error Logs

```Java
(Background on this error at: https://sqlalche.me/e/14/dbapi)" from manager
2024-11-27 13:51:59.795 ERROR ai.backend.manager.server [44034] Uncaught exception in HTTP request handlers DBAPIError("(sqlalchemy.dialects.postgresql.asyncpg.Error) : value too long for type character varying(64)")
Traceback (most recent call last):
File "/Users/codejong/Workspace/lablup/bai-dev2403/dist/export/python/virtualenvs/python-default/3.12.6/lib/python3.12/site-packages/sqlalchemy/dialects/postgresql/asyncpg.py", line 442, in _prepare_and_execute
self._rows = await prepared_stmt.fetch(*parameters)
```

## Environment

- Branch: 24.09.1
- Reproducible on: dogbow
## Additional Information

After renaming it to a shorter name, such as `e2e-test-folder-shar`, it worked properly again.

JIRA Issue: BA-39

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.