-
Notifications
You must be signed in to change notification settings - Fork 29
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
UNIX - SystemError: (9, 'Bad File Descriptor') on writing to file by line #54
Comments
What do you read for |
The os.path.join translates to: os.path.join('./8ball', '806944440488296508.txt') |
The issue still exists, but I've transitioned to just using an async SQLite call so I don't need to worry about async file access. |
short code which reproduces same issue
Ubutnu 16.04/ Python 3.7 aiofile 3.4.0
|
@pymen Please provide linux kernel version and the file system. |
@mosquito there is a warning, but it is not quite clear that everything will be broken
and exception
|
@pymen could you please upgrade kernel? Just for experiment? I think maybe restrict use linux_aio for kernels before 4.18. |
@mosquito, unfortunately, the Nvidia driver have made my system not working after upgrade to 4.18, and the next upgrade to 18.04 finished it off, so I had to install new ubuntu 20.4, where the script works perfectly |
Probably fixed in 3.5.0 |
I have a script that is working on my Windows 10 Pro machine, that is not working on my AWS Environment. Am I missing something simple?
MS Windows Version 2004 (OS Build 19041.685)
Python 3.8.0
UNIX Version:
uname -r: 4.14.214-160.339.amzn2.x86_64
NAME="Amazon Linux"
VERSION="2"
ID="amzn"
ID_LIKE="centos rhel fedora"
VERSION_ID="2"
PRETTY_NAME="Amazon Linux 2"
CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2"
Python 3.8.0 (Manually compiled, same issue on the stock python 3.7.9 that I could install with yum)
Requirements file:
The following code throws the error:
I am using a relative path for the os.path.join, as the config file is currently pointing to "./8ball"
Error Listing:
When substituting the aiofile.async_open for a regular open this succeeds without issue on the Linux machine.
Reading online this error usually means that the file was closed and then attempted to be referenced, but I'm writing into the file, and then closing the file.
I've also tried to write into this using AIOFile with a writer instead of async_open, but I'm receiving the same result.
The text was updated successfully, but these errors were encountered: