Replies: 2 comments 2 replies
-
Hi, thanks for reporting. Before anything else, You just won the prize for the longest subject line here on GitHub 😛 Please use a more informative subject line next time. The underlying problem is that the main R session can no longer communicate with the parallel R worker running in the background. The post-mortem diagnostic provided by the error message suggests that something has badly messed up the R connections, which should not happen. This was not done by the future framework, but something else. I haven't seen this reported regarding Seurat, so I doubt it is Seurat, but you can check with them. As the error message suggests, this can happen if someone/something calls For future reports, here or for other R packages, please always gives as much details as possible, e.g. calls made to reproduce this and what your |
Beta Was this translation helpful? Give feedback.
-
Hello Henrik, Thanks but this issue is very annoying. Apologize not attached the sessionInfo() There was no error or warning in my main program, and a few days ago I've posted another issue in the Seurat repository but the author cannot find the issue satijalab/seurat#5613. This issue was similar to satijalab/seurat#1436. I even uninstalled the R studio and re-installed the newest R the problem is still there. I follow up on suggestions on #311 but I am still unable to fix it. I really need someone help to fix this issue The commands I used :
|
Beta Was this translation helpful? Give feedback.
-
I am trying to integrate my seurat object but keep getting this error. is anyone know how to fix this issue
Beta Was this translation helpful? Give feedback.
All reactions