Updates:
Summary: Plugins Primitives no longer work after a while Labels: -Type-FirstImpressionsCount Type-Bug Comment #5 on issue 7600 by [hidden email]: Plugins Primitives no longer work after a while http://code.google.com/p/pharo/issues/detail?id=7600 (No comment was entered for this change.) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Updates:
Cc: [hidden email] [hidden email] Comment #6 on issue 7600 by [hidden email]: Plugins Primitives no longer work after a while http://code.google.com/p/pharo/issues/detail?id=7600 It's not the IO primitives per se, it is ALL plugin primitives. Since we could still open fileStreams and read write to them. For instance the NB is plugin installed check primitive didn't work anymore either. So it invalidated all the plugin primitives after a while. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #7 on issue 7600 by [hidden email]: Plugins Primitives no longer work after a while http://code.google.com/p/pharo/issues/detail?id=7600 this should not be in cog tracker? -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #8 on issue 7600 by [hidden email]: Plugins Primitives no longer work after a while http://code.google.com/p/pharo/issues/detail?id=7600 I use a "very" old VM from last june and I experienced the same issues. So I assume it is more image related, no? -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #9 on issue 7600 by [hidden email]: Plugins Primitives no longer work after a while http://code.google.com/p/pharo/issues/detail?id=7600 so, you have a way how to reproduce it? because the behavior is really weird. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #10 on issue 7600 by [hidden email]: Plugins Primitives no longer work after a while http://code.google.com/p/pharo/issues/detail?id=7600 so... since nobody knows how to reproduce it, and it happens not really common... is this a show stopper? -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #11 on issue 7600 by [hidden email]: Plugins Primitives no longer work after a while http://code.google.com/p/pharo/issues/detail?id=7600 It was happening to me pretty often, and the consequences are severe, since the image can not be saved, and MC packages can't be committed, but I don't know how to reproduce it. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #12 on issue 7600 by [hidden email]: Plugins Primitives no longer work after a while http://code.google.com/p/pharo/issues/detail?id=7600 I think we should make an image where all the delays are killed (from Issue 7553 ) *and* which is saved from a normally running VM (not using the headless setup from Jenkins). -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #13 on issue 7600 by [hidden email]: Plugins Primitives no longer work after a while http://code.google.com/p/pharo/issues/detail?id=7600 Yes Marcus. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Free forum by Nabble | Edit this page |