[flexcoders] Flex Builder 3: *major* bug in deleting linked folders
I am trying my best to not go to my blog and rant about Flex Builder 3... but its getting harder by the hour. I had an earlier post about having to dig around and delete some hidden caches to get my code to compile correctly... and now, Flex Builder just hosed by entire website (well -- my localhost copy that I debug against). I'm pretty annoyed by the whole Export release build... change in Flex Builder 3 because I'm building a performance-intensive (i.e. game) Flash app and there's a noticeable difference between release and debug builds. As a result, I like to regularly check out the release build. Annoyingly, the release build doesn't get exported to the same spot as the debug build (which is into my web server's document root) so I was exporting it, then copying it by hand. Annoying... So, I had the bright idea of setting the export... target folder to be by document root. I was warned that the export may get trampled by the debug build because they're in the same location. Fine with me, I'll rebuild the debug version after I check out the release build. Well, I did it, and sure enough, with automatic building it got confused and so I decided to undo it. I went into export release build... and changed the path back. Annoyingly, the linked directory for bin-release didn't update, so now I was stuck with a linked bin-release folder pointing at my document root. Okay, I'll just delete that linked folder... it won't delete the contents of the directory will it? Sure enough, my fears were allayed when FB warned, Deleting the linked folder will not remove the target folder just the link... OK? Hey, that's exactly what I want, so yeah, okay! F*CK! Even though the folder was definitely a linked folder (little icon and all), even though FB just told me it wasn't going to touch my file system, it deleted the contents of my document root. Zap. Instantly. And it didn't move it the trash like a decent human being, it just nuked it from the file system. Which leaves me to say, F* you Flex Builder... I shoulda just stayed in bed this morning, I'd be further along in my work than I am right now. I know there's not any answers to a post like this... just a heads up, a warning, to be *very* careful when deleting linked folders because there's definitely something buggy happening there. It may be user error on my part, but I feel pretty safe yelling bug with the confirmation dialog that I got. At the very least, folks, let have all our apps that delete files from the file system go the extra mile and send them to the trash, m'kay? Troy.
Re: [flexcoders] Flex Builder 3: *major* bug in deleting linked folders
F*CK! Even though the folder was definitely a linked folder (little icon and all), even though FB just told me it wasn't going to touch my file system, it deleted the contents of my document root. Zap. Instantly. And it didn't move it the trash like a decent human being, it just nuked it from the file system. Wow, it really nuked the file system... I'm running on OSX, and my htdocs folder (document root that got nuked) had all its permissions reset to No Access (even though my user account is still the owner/group). Wow, just wow. Troy.
Re: [flexcoders] Flex Builder 3: *major* bug in deleting linked folders
Wow, it really nuked the file system... I'm running on OSX, and my htdocs folder (document root that got nuked) had all its permissions reset to No Access (even though my user account is still the owner/group). Wow, just wow. Okay, FB... forgive me for getting upset. I've had a bad day. Very stressful. Sorry if I got a little unhinged. We can get back together, right? Apparently, the only thing that FB did was to clear the permissions on the file (which makes me think it's *definitely* a bug, because I wouldn't expect FB to ever need to mess with permissions on files). When I reset the permissions all of my files re-appeared (you know, since I didn't have read-access on the directory I couldn't see its contents!). Apologies for the flaming nature of my previous e-mails... happy that it worked out okay in the end, though there's still a bug in there! ;-) Troy.
RE: [flexcoders] Flex Builder 3: *major* bug in deleting linked folders
Well... now we know not to keep our development and production versions in the same place. And moving stuff to the trash is a feature of whatever operating system you're using, Linux or Windows or Mac. Any decent programming language will actually *delete* stuff you tell it to. I personally have nothing but good experiences with Flex Builder, so there ya go. - Clinton From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Troy Gilbert Sent: Wednesday, March 05, 2008 3:47 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Flex Builder 3: *major* bug in deleting linked folders F*CK! Even though the folder was definitely a linked folder (little icon and all), even though FB just told me it wasn't going to touch my file system, it deleted the contents of my document root. Zap. Instantly. And it didn't move it the trash like a decent human being, it just nuked it from the file system. Wow, it really nuked the file system... I'm running on OSX, and my htdocs folder (document root that got nuked) had all its permissions reset to No Access (even though my user account is still the owner/group). Wow, just wow. Troy.
Re: [flexcoders] Flex Builder 3: *major* bug in deleting linked folders
Well… now we know not to keep our development and production versions in the same place. And moving stuff to the trash is a feature of whatever operating system you're using, Linux or Windows or Mac. Any decent programming language will actually *delete* stuff you tell it to. I personally have nothing but good experiences with Flex Builder, so there ya go. Well, thanks for the warm remarks, but you'll notice that I quite clearly stated that it was my *localhost* copy of my site, i.e. it was my development version. It's a pain because restoring the development version from a backup or the production version is time consuming... And not deleting files when an app tells me hey, I'm not going to delete these files is a feature that should work. It's a bug, plain and simple. And a decent app that is *mirroring* the file system to the user (which FB is doing which it links folders or shows the directory tree) should *mirror* the file system's (i.e. OS's) feature of moving items to the trash. Oh, and I take back my previous apology. After looking at all my documents I discovered that all of the php files (and only the php files) were empty. Me thinks FB was trying to do something clever related to it's db wizards, etc. and clean up files it *thought* it had created. So, now the restore from the production server is finished. Now I'll (hopefully) get back to work. And for the record, I'm a *big* fan of Flex Builder (mostly Flex/Flash, not so much Builder) and have praised it on many occasions on my blog. Troy. -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links * To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ * Your email settings: Individual Email | Traditional * To change settings online go to: http://groups.yahoo.com/group/flexcoders/join (Yahoo! ID required) * To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] * To unsubscribe from this group, send an email to: [EMAIL PROTECTED] * Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
RE: [flexcoders] Flex Builder 3: *major* bug in deleting linked folders
It's ok, we recognize frustration when we we see it. However, I think there is a reason for FB to change file permissions. I keep the output-bin folder in source control so it is easier to deploy to our internal servers. Usually I keep the compiled files checked out but sometimes forget. If FB did not clear the read-only attribute on the compiled files, the compile would fail. And I verified that it does definitely remove the read-only attribute from the compiled swfs, I just tested it explicitly. Tracy From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Troy Gilbert Sent: Wednesday, March 05, 2008 3:50 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Flex Builder 3: *major* bug in deleting linked folders Wow, it really nuked the file system... I'm running on OSX, and my htdocs folder (document root that got nuked) had all its permissions reset to No Access (even though my user account is still the owner/group). Wow, just wow. Okay, FB... forgive me for getting upset. I've had a bad day. Very stressful. Sorry if I got a little unhinged. We can get back together, right? Apparently, the only thing that FB did was to clear the permissions on the file (which makes me think it's *definitely* a bug, because I wouldn't expect FB to ever need to mess with permissions on files). When I reset the permissions all of my files re-appeared (you know, since I didn't have read-access on the directory I couldn't see its contents!). Apologies for the flaming nature of my previous e-mails... happy that it worked out okay in the end, though there's still a bug in there! ;-) Troy.
Re: [flexcoders] Flex Builder 3: *major* bug in deleting linked folders
However, I think there is a reason for FB to change file permissions. I keep the output-bin folder in source control so it is easier to deploy to our internal servers. Usually I keep the compiled files checked out but sometimes forget. If FB did not clear the read-only attribute on the compiled files, the compile would fail. Yeah, but in this case, FB changed file *permissions*... not just a Windows read-only flag, but access permissions for user/group/other. Oh, and it smashed the contents of my php files... something is fishy. Troy.
Re: [flexcoders] Flex Builder 3: *major* bug in deleting linked folders
- Original Message - From: Troy Gilbert [EMAIL PROTECTED] To: flexcoders@yahoogroups.com Sent: Wednesday, March 05, 2008 9:38 PM Subject: Re: [flexcoders] Flex Builder 3: *major* bug in deleting linked folders However, I think there is a reason for FB to change file permissions. I keep the output-bin folder in source control so it is easier to deploy to our internal servers. Usually I keep the compiled files checked out but sometimes forget. If FB did not clear the read-only attribute on the compiled files, the compile would fail. Yeah, but in this case, FB changed file *permissions*... not just a Windows read-only flag, but access permissions for user/group/other. Oh, and it smashed the contents of my php files... something is fishy. Why not sit tight until someone at Adobe picks this up, or go ahead and raise a bug. Paul Troy.
RE: [flexcoders] Flex Builder 3: *major* bug in deleting linked folders
Well, thanks for the warm remarks, but you'll notice that I quite clearly stated that it was my *localhost* copy of my site, i.e. it was my development version. It's a pain because restoring the development version from a backup or the production version is time consuming... Ah, my bad then. However, I assume you're not using version control software of any kind then. Mistakes happen, we learn from them, but in your case Subversion can keep multiple versions of your files backed up. And Subclipse is a plugin that will work in Flex Builder 3 that makes it much easier to commit your development copy before you try something new. So, now the restore from the production server is finished. Now I'll (hopefully) get back to work. And for the record, I'm a *big* fan of Flex Builder (mostly Flex/Flash, not so much Builder) and have praised it on many occasions on my blog. Then I misunderstood your Which leaves me to say, F* you Flex Builder comment from earlier. I know we have plenty of Flex developers on this list and I was just trying to even things out a bit, that's all.
Re: [flexcoders] Flex Builder 3: *major* bug in deleting linked folders
Hi all, If you can please file a bug with a test project and detailed steps as to how to reproduce we can certainly take a look. Write back here with the bug number and maybe other folks who are seeing similar issues can vote on it to make sure we're aware of how much impact this is having on folks. Matt On 3/5/08 1:47 PM, Clinton D. Judy [EMAIL PROTECTED] wrote: Well, thanks for the warm remarks, but you'll notice that I quite clearly stated that it was my *localhost* copy of my site, i.e. it was my development version. It's a pain because restoring the development version from a backup or the production version is time consuming... Ah, my bad then. However, I assume you're not using version control software of any kind then. Mistakes happen, we learn from them, but in your case Subversion can keep multiple versions of your files backed up. And Subclipse is a plugin that will work in Flex Builder 3 that makes it much easier to commit your development copy before you try something new. So, now the restore from the production server is finished. Now I'll (hopefully) get back to work. And for the record, I'm a *big* fan of Flex Builder (mostly Flex/Flash, not so much Builder) and have praised it on many occasions on my blog. Then I misunderstood your Which leaves me to say, F* you Flex Builder comment from earlier. I know we have plenty of Flex developers on this list and I was just trying to even things out a bit, that's all.
Re: [flexcoders] Flex Builder 3: *major* bug in deleting linked folders
If you can please file a bug with a test project and detailed steps as to how to reproduce we can certainly take a look. Write back here with the bug number and maybe other folks who are seeing similar issues can vote on it to make sure we're aware of how much impact this is having on folks. I went through the steps in a fresh project and the issue didn't occur again. I'll try it again (later) with the project where it occurred for me the first time. If I can reproduce it, I'll file a bug. Apologies to everyone for the crudeness of my posts today... lots of stressing going on, most of it not related to Flex Builder... sorry it was the target! ;-) Troy.
Re: [flexcoders] Flex Builder 3: *major* bug in deleting linked folders
Ah, my bad then. However, I assume you're not using version control software of any kind then. I most certainly am using version control with my source code. The web stuff is developed by an external group and I don't (routinely) access their source control, so it wasn't a quick, easy option in my case. Troy.
