-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stop sharing #4
Comments
Hi @fedeago . Yes, we have an Best, |
Hi, Suddenly this new version of SharedObject(1.3.9) gives me some problems. Running devtools::check() or R CMD check it fails to do the test of the package with this error:
It is really strange because the test do not fails when runned as a normal R script but it fails during the R check. Maybe I should open an issue on the devtools repository but I tell you this becouse it do not happen with the stable version of SharedObject(1.2.2). Thank you, best regards |
Thanks for letting me know the issue, could you please provide me more info on the issue so I can also take a look at it? Does the issue persist when running check multiple times? What is your OS? It will be better if you have a reproducible example. Best, |
this is the output of sessionInfo:
The only way I think you can reproduce the error is clone my github repository called NewWave, uncomment all the code in /tests/test_design.R and then check the package. Changing from version 1.2.2 to 1.3.9 make other test of the package fails in the same way(fails during check but not as normal R script) but I solved them adding
in the tests/testthat.R file as suggested in : r-lib/testthat#86 If you think that I should open an issue on the devtools package I will do it, I writed to you becouse it was not happening before. |
Goodmorning,
I can show you how to reproduce this error but only using the package I am delopping. Best regards |
Goodmorning,
Suddenly I am not able to reproduce that outside the package. |
Thanks for letting me know the issue, I appreciate your bug report! Last week is quite busy for me so I do not have an answer to your previous question yet, but I will try to reproduce and check the problem this week and let you know the result. Best, |
Hi @fedeago , I have tried your package on Ubuntu. I use the commit ab456d41daf413f11cad319e0eedff17038fddbb that you made on July 13 but I am not able to reproduce the check error you have seen. Both R CMD check and devtools::check works fine on my side. This error is possibly very specific to your system. I suspect it is related to your shared memory size. Would you be able to run For your second issue( Best, |
Hi, please download again the package and re-try the checks, I wrongly commented some part of the test.
The second issue is somehow related to only one specific dataset, the one i wolud use for benchmarking. It is really strange so I will investigate and try to go further giving you some reproducible example. Thank you |
Thanks @fedeago , I just want to let you know that I have located the problem. It is caused by incorrectly releasing the shared memory while it is still in-used. It affects all shared matrices so your second bug might be the same issue. I will fix it in the next couple of days and let you know. |
As you said it solved both of my issue, thank you! I am very grateful for your work! When do you think the package would be disposable on Bioconductor devel? |
Glad to hear it. I have pushed the changes to Bioconductor today and it should be available in the next two days. Please feel free to contact me if you encounter any more problems:) I will close this issue after this comment. If you see any similar bugs you can reopen it or make a new issue. Thanks again for letting me know your concern and giving me the change to make the package better! |
Goodmorning again, is possible stop an object to be shared?
In the package that I am developping the matrix that internally I shared(with the option CopyOnWrite=F) are part of the output of the model but i would like, if possible, to stop that in order to give an output with a "normal" behaviour.
Thanks for your work, it is really precious for me.
The text was updated successfully, but these errors were encountered: