Sync'd images not displaying and IOError after symlinking - Syncing & AnkiWeb

link管理

链接快照平台

输入网页链接，自动生成快照
标签化管理网页链接

相关文章推荐

笑点低的猴子 · �廪��ѧУ��· 6 月前 ·

文质彬彬的咖啡豆 · MapKit中的地理编码和路线规划技术 | ...· 6 月前 ·

愤怒的李子 · 夏　鹏 -西安交通大学第一附属医院· 7 月前 ·

想旅行的香烟 · What's new in Kotlin ...· 8 月前 ·

冷静的酱牛肉 · 正则表达式 – 简介 | W3C教程· 8 月前 ·

Several days ago, I symlinked collection.media and collection.anki2 to Dropbox (I wasn’t aware that this is a bad idea at the time). Since then, there have been two issues:

On startup, close and sync, I get the error:


    IOError { info: "unable to read collection.media: No such file or directory (os error 2)" }

. The error doesn’t occur with shift startup (which leads me to believe the sync event triggers the error).

media doesn’t display through ankiweb sync (but media displays fine via local anki desktop):

I’ve tried the following yet 1. and 2. persist:
3. disabling all plugins
4. replacing the symlinks with the original files
5. importing a backup of date prior to creating symlinks
6. checking that the collections.media filename matches ankiweb

collection.media/paste-feaa17546c4336679924918e6639df1284173368.jpg
<img src="paste-feaa17546c4336679924918e6639df1284173368.jpg">
I’m not sure what could be causing the IOError at this point since collection.media is in the original location (and is not a symlink) and media displays fine locally. I don’t know what other data sources might be be relevant. As far as I can tell, collection.anki2 is not corrupt (Check Database report seems fine and Anki Desktop works normally aside from the IOError messages).
Any advice on how to proceed? Since I have backups, my next thought would be to reinstall Anki Desktop fresh and import.
Tracing this “unable to read” message in Anki’s source, I found these two occurences:

      github.com
    ankitects/anki/blob/f45d51c92d706d80c56d173eb2bc6db3674eafd7/rslib/src/media/changetracker.rs#L155
    .as_secs() as i64;
if let Some(previous_mtime) = previous_mtime {
    if previous_mtime == mtime {
        debug!(self.log, "mtime unchanged"; "fname"=>fname.as_ref());
        continue;
    }
}
// add entry to the list
let data = sha1_of_file(&dentry.path()).map_err(|e| AnkiError::IOError {
    info: format!("unable to read {}: {}", fname, e),
})?;
let sha1 = Some(data);
added_or_changed.push(FilesystemEntry {
    fname: fname.to_string(),
    sha1,
    mtime,
    is_new: previous_mtime.is_none(),
});
debug!(self.log, "added or changed";
    "fname"=>fname.as_ref(),
    ankitects/anki/blob/f45d51c92d706d80c56d173eb2bc6db3674eafd7/rslib/src/media/files.rs#L416
}
pub(super) fn data_for_file(media_folder: &Path, fname: &str) -> Result<Option<Vec<u8>>> {
    let mut file = match fs::File::open(&media_folder.join(fname)) {
        Ok(file) => file,
        Err(e) => {
            if e.kind() == io::ErrorKind::NotFound {
                return Ok(None);
            } else {
                return Err(AnkiError::IOError {
                    info: format!("unable to read {}: {}", fname, e),
                });
            }
        }
    };
    let mut buf = vec![];
    file.read_to_end(&mut buf)?;
    Ok(Some(buf))
}
#[cfg(test)]
But AFAIK, in both places, Anki should be trying to open a media file rather than the collection.media directory.

It seems some file in your media directory is somehow ending up appearing with an empty name in these places.
              If you can run from source, maybe try inserting some print statements before that error message in both places to find which one exactly is getting triggered. Maybe this will help pinpoint the source of the issue.
Like:
println!("sha1_of_file: {}", fname);
println!("data_for_file: {}", fname);
              I realized the IOError was caused by a symlink named collection.media inside collection.media. Symlink misadventures . And the image display issue no longer occurs after forcing a one way sync.
Thanks for your help and sorry for the confusion.