flickrfs-users Mailing List for Flickr Filesystem (Page 6)
Brought to you by:
manishrjain
You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(28) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
(5) |
Feb
(22) |
Mar
|
Apr
(7) |
May
(11) |
Jun
(2) |
Jul
(3) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(3) |
2007 |
Jan
(5) |
Feb
(8) |
Mar
(1) |
Apr
(2) |
May
(1) |
Jun
(5) |
Jul
|
Aug
|
Sep
|
Oct
(5) |
Nov
(4) |
Dec
|
2008 |
Jan
(21) |
Feb
(3) |
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(5) |
2014 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Manish R. J. <man...@gm...> - 2005-11-18 06:28:48
|
Hi Fabio This seems a problem with your set name. I will fix this bug in flickrfs meta beta. Just wait for some time before I get time to release that. Manish On 11/16/05, Fabio Spelta <sp...@gm...> wrote: > > > Version 1.1.9 is out! > > Hello and thank you for your work. > Too bad I still get the "Unhandled exception in thread started by > <bound method Flickrfs.sets_thread of <__main__.Flickrfs instance at > 0xb7af89cc>>" error. > > I still can see only the first four sets, too. > > I attach the /home/fabio/.flickrfs/log file, I hope it will be helpful! > > Ciao, and thank you > -- > Fabio > > > -- http://tuxmann.blogspot.com "If I have seen further it is by standing on the shoulders of Giants" "Software is like sex: it's better when it's free." "An infinite number of monkeys typing into GNU emacs would never make a goo= d program." |
From: Fabio S. <sp...@gm...> - 2005-11-16 07:44:36
|
> Version 1.1.9 is out! Hello and thank you for your work. Too bad I still get the "Unhandled exception in thread started by <bound method Flickrfs.sets_thread of <__main__.Flickrfs instance at 0xb7af89cc>>" error. I still can see only the first four sets, too. I attach the /home/fabio/.flickrfs/log file, I hope it will be helpful! Ciao, and thank you -- Fabio |
From: Manish R. J. <man...@gm...> - 2005-11-16 04:33:38
|
Actually, the statfs (shown by 'df'), is the one which determines if a new file can go into the filesystem. Here, because statfs shows 100% filled, therefore, no new file is allowed. Check your log, it shd confirm a call to statfs. Manish On 11/16/05, Alex Vollmer <ale...@gm...> wrote: > > I only included the 'df' output for extra information. My real problem is > that when I try to put files into a new directory in > /mnt/flickrfs/tags/personal/my:tag the OS says "no space left on device". > The numbers 'df' returned looked non-sensical but I think that is just a > symptom. > > Let me know if I can provide any more information. > > Thanks! > > On 11/15/05, Manish Rai Jain <man...@gm...> wrote: > > > > Currently 'df' is not working properly. Okay! I will temporary patch it > > up, so as to return fictitous values. > > > > Manish > > > > > > On 11/16/05, Alex Vollmer <ale...@gm... > wrote: > > > > > > I tried uploading some pictures through flickrfs and the filesystem i= s > > > telling me there is no space left on the device. Any idea what may be > > > causing this? > > > > > > Here is what 'df' says: > > > island ~ # df > > > Filesystem 1K-blocks Used Available Use% Mounted on > > > /dev/hda3 76081512 41382484 34699028 55% / > > > udev 513168 204 512964 1% /dev > > > /dev/hda1 104376 43652 60724 42% /boot > > > none 513168 0 513168 0% /dev/shm > > > /dev/fuse 1024 -18446744073707455488 0 100% /mnt/flickrfs > > > > > > Thanks! > > > > > > --Alex V > > > > > > -- > > > "I think there are only three things America will be known for 2,000 > > > years from now when they study this civilization: the Constitution, j= azz > > > music, and baseball." > > > --Gerald Early > > > > > > > > > > -- > > http://tuxmann.blogspot.com > > > > "If I have seen further it is by standing on the shoulders of Giants" > > "Software is like sex: it's better when it's free." > > "An infinite number of monkeys typing into GNU emacs would never make a > > good program." > > > > > -- > "I think there are only three things America will be known for 2,000 year= s > from now when they study this civilization: the Constitution, jazz music, > and baseball." > --Gerald Early > -- http://tuxmann.blogspot.com "If I have seen further it is by standing on the shoulders of Giants" "Software is like sex: it's better when it's free." "An infinite number of monkeys typing into GNU emacs would never make a goo= d program." |
From: Manish R. J. <man...@gm...> - 2005-11-16 04:26:12
|
Currently 'df' is not working properly. Okay! I will temporary patch it up, so as to return fictitous values. Manish On 11/16/05, Alex Vollmer <ale...@gm...> wrote: > > I tried uploading some pictures through flickrfs and the filesystem is > telling me there is no space left on the device. Any idea what may be > causing this? > > Here is what 'df' says: > island ~ # df > Filesystem 1K-blocks Used Available Use% Mounted on > /dev/hda3 76081512 41382484 34699028 55% / > udev 513168 204 512964 1% /dev > /dev/hda1 104376 43652 60724 42% /boot > none 513168 0 513168 0% /dev/shm > /dev/fuse 1024 -18446744073707455488 0 100% /mnt/flickrfs > > Thanks! > > --Alex V > > -- > "I think there are only three things America will be known for 2,000 year= s > from now when they study this civilization: the Constitution, jazz music, > and baseball." > --Gerald Early -- http://tuxmann.blogspot.com "If I have seen further it is by standing on the shoulders of Giants" "Software is like sex: it's better when it's free." "An infinite number of monkeys typing into GNU emacs would never make a goo= d program." |
From: Manish R. J. <man...@gm...> - 2005-11-16 01:15:58
|
On 11/16/05, nagaraja sosale ramaswamy <nag...@gm...> wrote: > > hi manish, > i'm having a few problems using flickrfs-1.1.9: > firstly, when i run flickrfs.py as normal user, i'm able to see my > photos, but i can't see any metadata (ls -al shows no .meta files) The metadata files wont exist in '/tags/public'. Also, you'll have to wait for some time after mounting the fs, so that, the information is downloaded= . The time taken will depend upon your internet connection. So best is to kee= p a tail -f ~/.flickrfs/log running. This will tell you what exactly the fs i= s doing. secondly, when i try to list the contents as root user, i get a > 'permission denied' error. this is not so much of a problem but still > i'm curious why root user is denied access to flickrfs if mounted by > normal user This is the apparently the way FUSE mounts the fs. If you do a 'mount', you will realize that flickrfs is automatically mounted with 'nosuid', user=3D'username'. Hence, no root access! thirdly, not all of my sets are showing up in flickrfs. only the ones > i created thru flickrfs are shown, but if i manually login to flickr > and change the name of the set or add new sets, they are not reflected > in flickrfs. Currently flickrfs is not updating itself dynamically. After you have already mounted flickrfs, and the information has been received, Any change= s done to your flickrfs account externally (not from flickrfs), won't show up in flickrfs. Though this will change, and a dynamic update will be added in later versions. last of all, even with this version, i get an unhandled exception when > flickrfs starts up. i'm running on ubuntru breezy amd64 > the error is as below: > ------------ > Unhandled exception in thread started by <bound method > Flickrfs.sets_thread of <__main__.Flickrfs instance at > 0x2aaaaadc6998>> > ------------ I tried checking your account using this link: http://flickr.com/photos/28359235@N00 . Is this right? But, this shows no photos at all? So, in case you have no sets at all, for the time being ignore the msg, and create some new sets from the fs itself. See how it goes. there is no further information in ~/.flickrfs/log, but i am attaching > just in case. > > let me know if you need anything else. sorry to bombard you with so > many problems, but would be really happy if the first problem is > addressed. i have a *huge* collection of photos to upload and using > the browser is becoming a drag. > > regards, > nagu. > > -- > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > get firefox ! browse happy ! > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > -- http://tuxmann.blogspot.com "If I have seen further it is by standing on the shoulders of Giants" "Software is like sex: it's better when it's free." "An infinite number of monkeys typing into GNU emacs would never make a goo= d program." |
From: Manish R. J. <man...@gm...> - 2005-11-15 16:53:24
|
Version 1.1.9 is out! Check out http://flickrfs.sf.net and http://tuxmann.blogspot.com Do try it out! Manish -- http://tuxmann.blogspot.com "If I have seen further it is by standing on the shoulders of Giants" "Software is like sex: it's better when it's free." "An infinite number of monkeys typing into GNU emacs would never make a goo= d program." |
From: Fabio S. <sp...@gm...> - 2005-11-15 15:06:09
|
> If the problem persists, attach the log file, will help me debug. Thank you very much. Here's two feature requests now: :-) The first is to have the chance to mount the filesystem read-only (I mean, flickr side - to allow flickrfs to read and not to write any data), to avoid any kind of problems if the only intent is to use it to view pictures (perhaps over a share, as I intend to do) The chance to append a .jpg extension to the filenames which does not have of their own, so that external apps which uses the file extension to recognize the file type would do it easily. Thank you very much, -- Fabio |
From: Manish R. J. <man...@gm...> - 2005-11-15 11:17:26
|
Hi Fabio This bug exists in v1.1. The newer upcoming version shd be able to tackle this. I will be releasing it by tonight SGT. Do try it out. If the problem persists, attach the log file, will help me debug. Regards Manish On 11/15/05, Fabio Spelta <sp...@gm...> wrote: > > Hello people. Dunno if this is a bug or if I'm missing something. > When I start flickrfs.py /mnt/mountpoint I get this error: > > Unhandled exception in thread started by <bound method > Flickrfs.sets_thread of <__main__.Flickrfs instance at 0xb79325ec>> > > And it only shows four of my many sets in the /mnt/mountpoint/sets folder= . > > Please ask for any detail that can be helpful in spotting the problem. > > Ciao and thanks, > -- > Fabio > > > ------------------------------------------------------- > This SF.Net email is sponsored by the JBoss Inc. Get Certified Today > Register for a JBoss Training Course. Free Certification Exam > for All Training Attendees Through End of 2005. For more info visit: > http://ads.osdn.com/?ad_idv28&alloc_id=16845&opclick > _______________________________________________ > Flickrfs-users mailing list > Fli...@li... > https://lists.sourceforge.net/lists/listinfo/flickrfs-users > -- http://tuxmann.blogspot.com "If I have seen further it is by standing on the shoulders of Giants" "Software is like sex: it's better when it's free." "An infinite number of monkeys typing into GNU emacs would never make a goo= d program." |
From: Fabio S. <sp...@gm...> - 2005-11-15 11:09:47
|
Hello people. Dunno if this is a bug or if I'm missing something. When I start flickrfs.py /mnt/mountpoint I get this error: Unhandled exception in thread started by <bound method Flickrfs.sets_thread of <__main__.Flickrfs instance at 0xb79325ec>> And it only shows four of my many sets in the /mnt/mountpoint/sets folder. Please ask for any detail that can be helpful in spotting the problem. Ciao and thanks, -- Fabio |
From: Manish R. J. <man...@gm...> - 2005-11-14 03:56:20
|
flickrfs in tags of the week: http://flickr.com/photos/tags/ 650 photos and growing: http://flickr.com/photos/tags/flickrfs If those who are wondering why I wrote this mail, here comes: Next version of flickrfs will soon be out, and here are some of the new features: 1. Direct read/write access to metainfo, like description, title, tags. And more? so, let it be, here comes 'license' as well. You need still more? Do let me know and I will add them before making the release. But, please be quick! 2. Access to your whole stream, only if you wish to. Just create a director= y named 'stream' in root, and will automatically retrieve the whole stream. 3. Oh! I think my 'bikini' photo I uploaded as public is not suitable. Only friends shd be allowed. Use your fav command: # chmod 754 my_bikini_photo.jpg And, here it is! Already changed your permissions. 4. Allows normal user access. I will be really glad to add any new features, before I release this versio= n and go underground for some time (my assignments are piling up). Regards Manish -- http://tuxmann.blogspot.com "If I have seen further it is by standing on the shoulders of Giants" "Software is like sex: it's better when it's free." "An infinite number of monkeys typing into GNU emacs would never make a goo= d program." |
From: Manish R. J. <man...@gm...> - 2005-11-13 10:55:09
|
On 11/13/05, nagu <nor...@bl...> wrote: > > i'm getting this error when starting flickrfs.py: > Unhandled exception in thread started by <bound method > Flickrfs.sets_thread of <__main__.Flickrfs instance at 0x5598c24c>> > btw, i'm on ubuntu breezy (amd64, kernel version 2.6.12-9) and using > flickrfs-1.1. i've tried it on 32 bit chroot and get the same error. > other package versions i'm using: > > libfuse2/unknown uptodate 2.3.0-1ubuntu1 > python2.4-fuse/unknown uptodate 2.2-2ubuntu2 > python-fuse/unknown uptodate 2.2-2ubuntu2 > fuse-utils/unknown uptodate 2.3.0-1ubuntu1 Can u please attach the log file at /var/log/flickrfs. This will help me identify the problem. also, how do i stop flickrfs ? i can't hit Ctrl-C to stop it.. it just says > 'Keyboard Interrupt'. i have to login in another terminal and kill this > process. is there a cleaner way ? Currently, the python script doesn't stop when you unmount the fs. So, it has to be killed. I am working upon this, and will come up with a cleaner way soon. -- > Posted by nagu to mann<http://tuxmann.blogspot.com/2005/11/announcing-fli= ckrfs_03.html>at 11/13/2005 06:37:52 PM -- http://tuxmann.blogspot.com "If I have seen further it is by standing on the shoulders of Giants" "Software is like sex: it's better when it's free." "An infinite number of monkeys typing into GNU emacs would never make a goo= d program." |
From: Paul P. <pe...@ee...> - 2005-11-11 07:32:28
|
On Fri, Nov 11, 2005 at 01:51:38PM +0800, Manish Rai Jain wrote: > > FlickrFS is really cool, but after playing around with it a bit I feel > > like it's also missing some pieces. It would be nice if there were a > > direct interface into the photostream, as well as a way to edit the > > metadata directly. I'd like to suggest one possible filesystem layout, > > just for the sake of discussion: <snip> > It will be desirable that, the metadata information can be edited easily, > for a whole lot of photos. For e.g. adding a new tag 'tag1', can be easily > updated for all the photos in the set. So, I think in that case, it will be > more useful if the files containing metadata be 1 file per image. For image > named 'img1', the metadata file will be named '.img1' (<dot>img1), and exist > in the same directory as the image itself. So, this will also remain hidden > from the user, so as to avoid any cluttering, while on the other hand, > allows using grep, sed scripts to do a mass change on all the .*.meta > (metadata) files. Using a dotfile for the metadata makes a lot of sense. I'm not sure that I agree about putting all the metadata in a single file, however. The file would need to be organized somehow (XML or whatever) and then you risk having the user accidentally break the file structure and screw up the metadata in a bad way. I think I would be happier with having one .imgN/ (or .imgN.meta/) directory for each photo, and using separate files inside that directory for each piece of metadata. > > Also, it feels a bit inelegant to have to set the permissions of a photo > > *before* copying it into the flickr FS. It would be nice to be able to > > change the permissions on pre-existing photos in-place. > > Next version will allow that. Great! > Nice ideas Paul :). It's an interesting problem, how to map flickr functionality on to a FS. I wish I had more time to actually help work on it, instead of just feeding you ideas. :-) Paul |
From: Manish R. J. <man...@gm...> - 2005-11-11 05:51:41
|
On 11/11/05, Paul Pelzl <pe...@ee...> wrote: > > > FlickrFS is really cool, but after playing around with it a bit I feel > like it's also missing some pieces. It would be nice if there were a > direct interface into the photostream, as well as a way to edit the > metadata directly. I'd like to suggest one possible filesystem layout, > just for the sake of discussion: > > ------------------------------------------------------------------------ > /flickrfs_mount > stream/ > metadata/ > photo\ title\ 1/ > tags # ASCII file containing list of tags > sets # ASCII file containing sets for this photo > description # ASCII file containing photo description > photo\ title\ 2/ > tags > sets > description > photo\ title\ 3/ > tags > sets > description > ... > photo\ title\ 1 # jpeg files > photo\ title\ 2 > photo\ title\ 3 > ... > tags/ > ... # as implemented currently > sets/ > ... # as implemented currently > ------------------------------------------------------------------------ > > So the idea here is that the stream/ directory is sort of a primary > interface, with a metadata/ subdir that lets the user change the > metadata for any of the photos. (It would be even nicer to have a > ReiserFS 4-style system for handling metadata...) Dropping a new photo > into stream/ should (1) upload the file and (2) add blank entries to the > proper location in stream/metadata/ . It will be desirable that, the metadata information can be edited easily, for a whole lot of photos. For e.g. adding a new tag 'tag1', can be easily updated for all the photos in the set. So, I think in that case, it will be more useful if the files containing metadata be 1 file per image. For image named 'img1', the metadata file will be named '.img1' (<dot>img1), and exis= t in the same directory as the image itself. So, this will also remain hidden from the user, so as to avoid any cluttering, while on the other hand, allows using grep, sed scripts to do a mass change on all the .*.meta (metadata) files. Note that I'm no filesystem expert, so I'm pretty clueless when it comes > to the technical limitations of something like this. > > Also, it feels a bit inelegant to have to set the permissions of a photo > *before* copying it into the flickr FS. It would be nice to be able to > change the permissions on pre-existing photos in-place. Next version will allow that. Paul Nice ideas Paul :). Regards Manish ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. > Download > it for free - -and be entered to win a 42" plasma tv or your very own > Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > Flickrfs-users mailing list > Fli...@li... > https://lists.sourceforge.net/lists/listinfo/flickrfs-users > |
From: Paul P. <pe...@ee...> - 2005-11-10 23:25:05
|
FlickrFS is really cool, but after playing around with it a bit I feel like it's also missing some pieces. It would be nice if there were a direct interface into the photostream, as well as a way to edit the metadata directly. I'd like to suggest one possible filesystem layout, just for the sake of discussion: ------------------------------------------------------------------------ /flickrfs_mount stream/ metadata/ photo\ title\ 1/ tags # ASCII file containing list of tags sets # ASCII file containing sets for this photo description # ASCII file containing photo description photo\ title\ 2/ tags sets description photo\ title\ 3/ tags sets description ... photo\ title\ 1 # jpeg files photo\ title\ 2 photo\ title\ 3 ... tags/ ... # as implemented currently sets/ ... # as implemented currently ------------------------------------------------------------------------ So the idea here is that the stream/ directory is sort of a primary interface, with a metadata/ subdir that lets the user change the metadata for any of the photos. (It would be even nicer to have a ReiserFS 4-style system for handling metadata...) Dropping a new photo into stream/ should (1) upload the file and (2) add blank entries to the proper location in stream/metadata/ . Note that I'm no filesystem expert, so I'm pretty clueless when it comes to the technical limitations of something like this. Also, it feels a bit inelegant to have to set the permissions of a photo *before* copying it into the flickr FS. It would be nice to be able to change the permissions on pre-existing photos in-place. Paul |
From: Manish R. J. <man...@gm...> - 2005-11-10 08:38:35
|
Great Paul ! That's really good news. Do check out features-request list on sourceforge main page. Manish On 11/10/05, Paul Pelzl <pe...@ee...> wrote: > > > Problem solved. Turns out I had a year-old copy of fuse-python > installed, and flickrfs was loading that version instead of the current > one. Sorry for the confusion. > > Thanks for a great little program. This looks like the perfect unixy > interface to flickr. I look forward to seeing what other features you > have in mind. > > Paul > > > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. > Download > it for free - -and be entered to win a 42" plasma tv or your very own > Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > Flickrfs-users mailing list > Fli...@li... > https://lists.sourceforge.net/lists/listinfo/flickrfs-users > |
From: Paul P. <pe...@ee...> - 2005-11-10 08:36:48
|
Problem solved. Turns out I had a year-old copy of fuse-python installed, and flickrfs was loading that version instead of the current one. Sorry for the confusion. Thanks for a great little program. This looks like the perfect unixy interface to flickr. I look forward to seeing what other features you have in mind. Paul |
From: Manish R. J. <man...@gm...> - 2005-11-10 07:04:43
|
On 11/10/05, Paul Pelzl <pe...@ee...> wrote: > > On Thu, Nov 10, 2005 at 01:45:28PM +0800, Manish Rai Jain wrote: > > > which corresponds to the last photo in the last set. Not having much > > > luck with debugging so far, but then again I don't know much about > FUSE. > > > Any debugging suggestions you have would be very helpful. > > > > > > Some checks: > > 1. ls -al /dev/fuse -> does it show a character device? (Though, this > shd be > > fine, otherwise flickrfs won't mount) > > crw-rw-rw- 1 root root 10, 229 Nov 8 00:43 /dev/fuse > > > 2. Try out flickr account of your friend, on the same installation, and > see > > if the prob remains. You'll need to remove ~/.flickr directory > containing > > the authentication information, so that flickrfs will show the login > prompt > > again. > > I registered a new account and uploaded a couple of photos. Same > problem. However, I did uncover another bug: if the user has no sets, > then the main for loop in sets_thread fails because rsp.photosets[0] has > no 'photoset' attr. I guess you can fix it with something like > > if hasattr(rsp.photosets[0], "photoset"): > for a in rsp.photosets[0].photoset: > ... Someone else reported this as well. Will fix it asap. > 3. Add some debugging statements to sets_thread, and see if the thread > > returns before the error shows up. > > sets_thread does return. However, I'm not sure whether the "short read" > error occurs before or after sets_thread returns. The error message > doesn't show up until I hit enter. If I don't touch the keyboard then > the flickrfs process just sits there doing nothing after iterating > through all the tags and sets (and the mount point remains empty), so I > assume the error has already occurred even though the message is not > printed until I hit enter. Must be some weird multithreading thing. While mounting flickrfs, don't do it as a background process. # ./flickrfs /mnt/flickrfs (no &) You shd be able to see the error msg. Also, you may use the 'print' statement inside the code, instead of the log.info <http://log.info> so as to print it on the same terminal (on which you mounted). Paul > > > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. > Download > it for free - -and be entered to win a 42" plasma tv or your very own > Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > Flickrfs-users mailing list > Fli...@li... > https://lists.sourceforge.net/lists/listinfo/flickrfs-users > |
From: Paul P. <pe...@ee...> - 2005-11-10 06:53:00
|
On Thu, Nov 10, 2005 at 01:45:28PM +0800, Manish Rai Jain wrote: > > which corresponds to the last photo in the last set. Not having much > > luck with debugging so far, but then again I don't know much about FUSE. > > Any debugging suggestions you have would be very helpful. > > > Some checks: > 1. ls -al /dev/fuse -> does it show a character device? (Though, this shd be > fine, otherwise flickrfs won't mount) crw-rw-rw- 1 root root 10, 229 Nov 8 00:43 /dev/fuse > 2. Try out flickr account of your friend, on the same installation, and see > if the prob remains. You'll need to remove ~/.flickr directory containing > the authentication information, so that flickrfs will show the login prompt > again. I registered a new account and uploaded a couple of photos. Same problem. However, I did uncover another bug: if the user has no sets, then the main for loop in sets_thread fails because rsp.photosets[0] has no 'photoset' attr. I guess you can fix it with something like if hasattr(rsp.photosets[0], "photoset"): for a in rsp.photosets[0].photoset: ... > 3. Add some debugging statements to sets_thread, and see if the thread > returns before the error shows up. sets_thread does return. However, I'm not sure whether the "short read" error occurs before or after sets_thread returns. The error message doesn't show up until I hit enter. If I don't touch the keyboard then the flickrfs process just sits there doing nothing after iterating through all the tags and sets (and the mount point remains empty), so I assume the error has already occurred even though the message is not printed until I hit enter. Must be some weird multithreading thing. Paul |
From: Manish R. J. <man...@gm...> - 2005-11-10 05:45:30
|
On 11/10/05, Paul Pelzl <pe...@ee...> wrote: > > On Wed, Nov 09, 2005 at 05:15:52AM +0800, Manish Rai Jain wrote: > > Hi all > > Version 1.1 is out. > > I am still seeing the "short read on fuse device" error that I reported > the other day. The log file does not show any errors; the last line > reads > > Creating file:/sets/Michigan football game/naptime:with id:1156242 > > which corresponds to the last photo in the last set. Not having much > luck with debugging so far, but then again I don't know much about FUSE. > Any debugging suggestions you have would be very helpful. Some checks: 1. ls -al /dev/fuse -> does it show a character device? (Though, this shd b= e fine, otherwise flickrfs won't mount) 2. Try out flickr account of your friend, on the same installation, and see if the prob remains. You'll need to remove ~/.flickr directory containing the authentication information, so that flickrfs will show the login prompt again. 3. Add some debugging statements to sets_thread, and see if the thread returns before the error shows up. Also, I couldn't help but notice that flickrfs.py has a whole lot of > indentation that mixes tabs and spaces. That's a dangerous thing to do > in Python; there's a note about it here: > http://www.python.org/peps/pep-0008.html > I'd be happy to submit a patch that uses spaces for all indentation. It > takes about 2 seconds to fix in Vim. Thanks for the suggestion. I will identate it properly in the next version according to python style. Paul > > > > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. > Download > it for free - -and be entered to win a 42" plasma tv or your very own > Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > Flickrfs-users mailing list > Fli...@li... > https://lists.sourceforge.net/lists/listinfo/flickrfs-users > |
From: Paul P. <pe...@ee...> - 2005-11-10 05:35:15
|
On Wed, Nov 09, 2005 at 05:15:52AM +0800, Manish Rai Jain wrote: > Hi all > Version 1.1 is out. I am still seeing the "short read on fuse device" error that I reported the other day. The log file does not show any errors; the last line reads Creating file:/sets/Michigan football game/naptime:with id:1156242 which corresponds to the last photo in the last set. Not having much luck with debugging so far, but then again I don't know much about FUSE. Any debugging suggestions you have would be very helpful. Also, I couldn't help but notice that flickrfs.py has a whole lot of indentation that mixes tabs and spaces. That's a dangerous thing to do in Python; there's a note about it here: http://www.python.org/peps/pep-0008.html I'd be happy to submit a patch that uses spaces for all indentation. It takes about 2 seconds to fix in Vim. Paul |
From: Manish R. J. <man...@gm...> - 2005-11-10 02:40:11
|
Just caught this one: http://flickr.com/photos/51035632655@N01/61566983/ |
From: Manish R. J. <man...@gm...> - 2005-11-10 02:38:56
|
SGVyZSBpcyB0aGUgbGluazoKaHR0cDovL2Jsb2cuYmlnZmF0Z2Vlay5vcmcvP3A9OQoKQW5kIGV4 Y2VycHQ6CiogRGlyZWN0b3JpZXMgYXJlIG9ubHkgYWNjZXNzaWJsZSAob3IgZXZlbiB2aXNpYmxl KSB0byByb290LCBzbyBJIGhhZCB0bwpjaGFuZ2UgdGhlIHNhbWJhIGFjY291bnQgdG8gcm9vdC4g Tm90IHZlcnkgaGVhbHRoeYUKIEkgYW0gd29ya2luZyB1cG9uIHRoaXMsIHdpbGwgYWxsb3cgYWNj ZXNzIHRvIG5vcm1hbCB1c2VyIHNvb24uCgoqIFRhZyBzdXBwb3J0IGlzIGJhc2VkIG9uIGNyZWF0 aW5nIGRpcmVjdG9yaWVzIHdpdGggbmFtZXMgbWF0Y2hpbmcgdGhlIHRhZ3MuClJlbmFtaW5nIGRv ZXNuJ3Qgc2VlbSB0byBiZSBzdXBwb3J0ZWQuIEhvd2V2ZXIsIFdpbmRvd3Mgd2lsbCBjcmVhdGUg YWxsCmRpcmVjdG9yaWVzIGFzICJOZXcgRm9sZGVyIiwgYW5kIG9ubHkgbGV0IHlvdSByZW5hbWUg dGhlbSBhZnRlcndhcmRzLgogVGhpcyBpcyB0cmlja3khIFdpbGwgYmUgcG9zdGluZyBvbiBmbGlj a3JmcyBtYWlsaW5nIGxpc3QgYWJ0IGhvdyBpdCBnb2VzLgoKKiBGaWxlbmFtZXMgYXJlIHRha2Vu IGZyb20gdGhlIGZsaWNrciB0aXRsZXMsIHdpdGhvdXQgYWRkaW5nIGV4dGVuc2lvbnMsIGFuZApX aW5kb3dzIGlzIHZlcnkgcGlja3kgYWJvdXQgZXh0ZW5zaW9ucwpXaWxsIGZpeCB0aGlzIG9uZSBz b29uLgo= |
From: Manish R. J. <man...@gm...> - 2005-11-08 21:16:02
|
Hi all Version 1.1 is out. Changes are as follows: v1.1 - - fixed bug if photo title=3D=3D'', then flickrfs crashes. - Including API Key - Support for spaces in tags while uploading - Permissions support while Uploading (mode=3Dabc -a=3D7(always), b=3D(friends=3D5 | family=3D6 | none=3D4), c=3D(5=3Dpublic | 4=3Dprivate) More abt it online at: http://flickrfs.sf.net Regards Manish |
From: Manish R. J. <man...@gm...> - 2005-11-08 07:05:17
|
On 11/8/05, Manish Rai Jain <man...@gm...> wrote: > > Hi Jacob > The /usr/bin/firefox is the location of the executable for your browser. > So, in case you are not using firefox, you need to change this to the > location of your browser (may be '/usr/bin/mozilla', you may use 'which > your_browser_name_here' to find it. THen, replace it in the source code n= ear > the authentication information. > The first time you execute the code, it will direct you to flickr web > page, where you need to authenticate with flickr to provide read/write > permissions to the tool. > The frob error most probably will be due to this only. > > Regards > Manish > > > On 11/8/05, Jacob Stoner <re...@ja...> wrote: > > > > Thanks for the speedy reply its not often that I get some real help fro= m > > a developer. Your advice did fix those messages, but then It was giving= a > > message about the firefox file so i rantouch /usr/bin/firefox > > then > > chmod 777 /usr/bin/firefox > > the firefox message went away but I'm still getting this: > > RAID:/data/flickrfsv1.0# ./flickrfs.py /data/flickr & > > [2] 8270 > > RAID:/data/flickrfsv1.0# rsp: error 108: Invalid frob > > > > I have no clue about this. > > Well thanks for your help. > > -Jacob > > > > On Nov 8, 2005, at 12:22 AM, Manish Rai Jain wrote: > > > > Hi Jacob > > Just to check, you installed 'fuse', followed by 'fuse-python'. > > > > The problem is because of the libfuse.so.2 library being in > > /usr/local/lib. If you copy this over to /usr/lib, then the problem shd= go > > away. > > > > If you can't find the library over there, just do an 'slocate > > libfuse.so.2', and then copy it over. > > > > Let me know if you have any more problems. > > > > Regards > > Manish > > > > > > On 11/8/05, Jacob Stoner <re...@ja...> wrote: > > > > > > I'm very excited about this flickrfs, I have some great uses in > > > mind. Please help me. I'm getting this error > > > > > > RAID:/data/flickrfsv1.0# ./flickrfs.py /data/flickr & > > > [1] 8254 > > > RAID:/data/flickrfsv1.0# Traceback (most recent call last): > > > File "./flickrfs.py", line 15, in ? > > > from fuse import Fuse > > > File "/usr/lib/python2.3/site-packages/fuse.py", line 24, in ? > > > from _fuse import main, FuseGetContext, FuseInvalidate > > > ImportError: libfuse.so.2: cannot open shared object file: No such > > > file or directory > > > > > > I followed the instructions very well. I'm using debain and I also > > > installed python using > > > apt-get install python > > > and > > > apt-get install python2.3-dev > > > > > > Do I need to add fuse files to the path somehow? > > > > > > Thanks. This looks like a very fine piece of code. > > > -Jacob > > > > > > > > > > |