I'm using an aws postgres database and get this error when I try running the syncdb command.  root@c89f2222f95d:/app# dap syncdb --table accounts 2023-12-06 20:06:03,485 - ERROR - missing cont...

The problem was on line 37 inside the timestamp.py in the dap package. It was creating a datetime object with a value of 1/1/0001, which Python didn't like. So we wrote an exception handler at lin...

It does seem to be an issue with bad data. There are 49 submissions with a submitted date of 1/1/0001, which we expect to be causing the problem. What do we do with bad dates in the download files?

How do I look at the instructure_dap_temp directory? I looked through my directory and couldn't find it. Doesn't dap delete it right after it's created? 

When I run initdb on the submissions table I get a "year 0 is out of range" error. It seems like I'm dealing with a bad row of data. What are the best options for resolving this? I assume ...

The problem was on line 37 inside the timestamp.py in the dap package. It was creating a datetime object with a value of 1/1/0001, which Python didn't like. So we wrote an exception handler at lin...

It does seem to be an issue with bad data. There are 49 submissions with a submitted date of 1/1/0001, which we expect to be causing the problem. What do we do with bad dates in the download files?

How do I look at the instructure_dap_temp directory? I looked through my directory and couldn't find it. Doesn't dap delete it right after it's created? 

When I run initdb on the submissions table I get a "year 0 is out of range" error. It seems like I'm dealing with a bad row of data. What are the best options for resolving this? I assume ...

This worked for me. Thank you!