Pretty easy to reproduce this one.

<verbatim>% cd /tmp
% mkdir bug-test
% fs new fs-info-test.fossil
% mkdir co
% cd co
% fs open ../fs-info-test.fossil 
% echo bar > foo.txt
% fs add foo.txt 
ADDED  foo.txt
% fs ci -m "Add a test file" foo.txt 
New_Version: a152dde43c9bf3410205e98b7fee57555d92378a
% fs info foo.txt 
fossil: no such object: foo.txt

Exit 1</verbatim>

Getting in to feature request land that led to uncovering this bug.

I was doing a vendor import of some code and started to apply a local patch to the new branch. I was hoping to be able to snag the contents of the patch from branch=trunk, but wasn't able to do so. While poking around to find an easy way to get the artifact-id from the command line, I stumbled across this bug not working.

Ideally I'd like to be able to do something like:

<verbatim>% fs finfo -p -r master some/path/foo.txt</verbatim>

Without having looked at the code, it appears as though the arg to -r isn't performing a lookup of symbolic names.  Associating artifact-ids with filenames would be ideal.  Something like:

<code>fs artifact some/path/foo.txt</code>

And have it spit out a list of artifacts that match a given file, or "-r tip" and have it only spit out the artifact-ids of what's in tip.