fdbozzo Posted December 11, 2013 Report Share Posted December 11, 2013 Hi cidico, I will check the capitalization of files, may be this is the problen. I'm using Visual FoxPro, and it have the bad habit of changing the capitalization of files, so this could make trouble. I just don't know if there is a way to change the capitalization of all files to normalze them (may be accesing the database directly?) Thanks! Link to comment Share on other sites More sharing options...
calbzam Posted December 11, 2013 Report Share Posted December 11, 2013 Hi, Are you trying to sync your local Plastic repository with a clean GitHub one, right? Could you send us the repository or the fast-export package? cm fast-export repo@server:8084 --no-data I will try to reproduce the issue and debug the problem. Regards, Carlos Link to comment Share on other sites More sharing options...
fdbozzo Posted December 12, 2013 Report Share Posted December 12, 2013 I've tried, but: 1st try with --no-data switch: C:\Users\windows>cm fast-export foxbin2prg@win7u:8087 --no-datafast-export: Unexpected option --no-dataExports Plastic SCM repository data to a fast-export format. 2nd try without --no-data switch: C:\Users\windows>cm fast-export foxbin2prg@win7u:8087Getting branch list...Getting changeset list...Building changeset list...1 changesets retrieved1 changesets will be exported0 labels will be exported0 merges found0 csets are out of orderSkipping changeset 0@/main.C:\Users\windows>dir Directorio de C:\Users\windows12/12/2013 18:01 0 fast-export.dat Export file es empty! :-( Link to comment Share on other sites More sharing options...
calbzam Posted December 12, 2013 Report Share Posted December 12, 2013 Ups sorry, the option is "--nodata" (without the middle "-") C:\Users\windows>cm fast-export foxbin2prg@win7u:8087 --nodata But checking the second try, it seems that you are exporting an empty repository, only 1 changeset is retrieved (the default one that is created when the repository is created). That´s the reason why the export file is empty. Could you review if "foxbin2prg" contains more changesets?? In case the repository is not empty I would like to get connected and review why it´s failing. Regards, Carlos Link to comment Share on other sites More sharing options...
fdbozzo Posted December 12, 2013 Report Share Posted December 12, 2013 Here is a screenshot of my repo, with 80 changesets. May be I am missing some parameter, or I should use this command from the workspace? Link to comment Share on other sites More sharing options...
calbzam Posted December 12, 2013 Report Share Posted December 12, 2013 But, as far as I can see, the repository name is: "desarrollo", so the command should be: C:\Users\windows>cm fast-export desarollo@win7u:8087 --nodata Regards, Carlos Link to comment Share on other sites More sharing options...
fdbozzo Posted December 12, 2013 Report Share Posted December 12, 2013 Ok... my fault, up to now I've convinced that my repo was on "foxbin2prg", but now I see that it is on "desarrollo". Sorry Attached file (14.5 Mb) fast-export.7z.txt Link to comment Share on other sites More sharing options...
fdbozzo Posted December 12, 2013 Report Share Posted December 12, 2013 It is a 7zip file, decompressed uses 14.5 MB. Link to comment Share on other sites More sharing options...
calbzam Posted December 13, 2013 Report Share Posted December 13, 2013 Hi, I´m able to reproduce the issue. We will review why this error is happening. Regards, Carlos Link to comment Share on other sites More sharing options...
cidico Posted December 15, 2013 Author Report Share Posted December 15, 2013 WoW! Are you able to reproduce the problem? YEAAAAAAAAAAAH!! If you want (and you're able to) we can connect and you can see the problem in my machine too! Just to know, were you able to see the error message as we are? Link to comment Share on other sites More sharing options...
cidico Posted December 15, 2013 Author Report Share Posted December 15, 2013 I mean, the same message Link to comment Share on other sites More sharing options...
calbzam Posted December 16, 2013 Report Share Posted December 16, 2013 Hi @cidico, Using @fdbozzo´s repository, I could reproduce the issue with the first push. I ´ve attached your repository and information to the task. We will try to debug the issue and check why this error is happening. Regards, Carlos Link to comment Share on other sites More sharing options...
fdbozzo Posted January 13, 2014 Report Share Posted January 13, 2014 Any news about this? Link to comment Share on other sites More sharing options...
calbzam Posted January 16, 2014 Report Share Posted January 16, 2014 Hi, The task is going to be planned for the next sprint. We will try to fix it ASAP. Regards, Carlos Link to comment Share on other sites More sharing options...
cidico Posted February 26, 2014 Author Report Share Posted February 26, 2014 Hi Carlos! I tried the 5.0.44.533 version and you guys have made an nice progress! I was finally able to do the "initial sync" with a git repository @ BitBucket! The problem now is that after a few checkins, the git repository seems to be getting "corrupted". Plastic appears to sync nicely and no error messages are displayed now, BUT, in the fact, no sync was made at all. After that, I can't access my git repo. I know I'm been very annoying about this feature, and, for what I can see, only we (me and @fdbozzo) are having this issue. Last night I tried to sync some dumb repos, and everything was working fine UNTIL I branched and performed a merge. It was already late and I was not able to perform more specific tests to try to isolate the problem. As I said, no error messages are displayed by Plastic but no sync was made at all and Plastic was not "aware" of it. Thanks for your time and patience! Link to comment Share on other sites More sharing options...
calbzam Posted February 26, 2014 Report Share Posted February 26, 2014 Hi @cidico, We are fixing this week two GitSync bugs. One was related to using Spanish accents (eg: "cámara" ) or other symbols in labels and branches, the other one is related to using blanks in tag names. We figured out that @fdbozzo issues was related to this circumstance. Could you confirm if your issues relate to the same scenarios? Best regards, Carlos Link to comment Share on other sites More sharing options...
cidico Posted February 26, 2014 Author Report Share Posted February 26, 2014 Hi Carlos! Yes, I do confirm the usage of such chars! As my natural language is Brazilian Portuguese I tend to use a lot of "á, ó, é, ç, ã, õ" and several others chars! I my first repo (the one that started this thread), I don't remember if I have spaces at tags, but, I have a lot of spaces on labels and comments. I don't remember right now, but I once told you that the sync was being made but there was a problem in comments and branch's names. Their names were being cropped. If you want, after doing the fix, I volunteer myself to run a "special build" or something like that, with the fix to help you confirm the fix! Thanks! Link to comment Share on other sites More sharing options...
cidico Posted February 26, 2014 Author Report Share Posted February 26, 2014 Maybe, just maybe, but I think the problem you're describing is related to this: http://www.plasticscm.net/index.php?/topic/618-fast-export-failing-to-deal-with-non-english-chars-in-branch-names/ http://www.plasticscm.net/index.php?/topic/930-importing-tfs-project-into-plastic/ Link to comment Share on other sites More sharing options...
calbzam Posted February 26, 2014 Report Share Posted February 26, 2014 Hi, Yes, as soon as we can release the fix, I will let you know to test it. Thank you!! Regards, Carlos Link to comment Share on other sites More sharing options...
cidico Posted March 7, 2014 Author Report Share Posted March 7, 2014 Hi Carlos! As always, I try to keep the latest version of Plastic SCM running on all my machines... In the release notes of 5.0.44.537 I found these two bug corrections: Bug GitSync: Push branches or tags with non ASCII characters was failing.Fixed.BugGitSync: Plastic labels with spaces and other illegal git characterswere not being pushed to Git. Fixed. Now they are pushed, the nameexported to git will be the same in plastic but replacing theseillegal characters with a dash ('-').E.g.: "Label 1" will be pushed as "Label-1". Are these fixes THE fix for the issue described in this thread? If yes, I'll try this build tomorrow! Thanks in advance! Link to comment Share on other sites More sharing options...
calbzam Posted March 14, 2014 Report Share Posted March 14, 2014 Hi, Yes, please test the new fixes, and let us know if your issue is also fixed. I think you issue was related to some illegal characters. Regards, Carlos Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.