Please see my previous comment, I cannot be more helpful without a reproducible example.

hi, I want to speed up code execution by using this package.But this error occurs frequently, and it resumes normal operation after a while. I don't know why. thank you~

------------------ 原始邮件 ------------------ 发件人: "Bioconductor/BiocParallel" ***@***.***>; 发送时间: 2021年6月17日(星期四) 晚上10:03 ***@***.***>; ***@***.******@***.***>; 主题: Re: [Bioconductor/BiocParallel] Error in serialize(data, node$con) : error writing to connection (#143)

This could be because the data (input or return) is too large. Pass less data, e.g., a path to a file on your system instead of the contents of the file in memory.

It could also be that an error occurs in your code. Try running with register(SerialParam()) instead of in parallel.

Please report back here if this helps.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

This could be because the data (input or return) is too large. Pass less data, e.g., a path to a file on your system instead of the contents of the file in memory.

It could also be that an error occurs in your code. Try running with register(SerialParam()) instead of in parallel.

Please report back here if this helps.

hello，I have a problem when use the BiocParallel package.When I use the bplappy() function，it reports an error and terminates the code operation： Error in serialize(data, node$con) : 链结书写发生了错误 Calls: local ... .send -> <Anonymous> -> sendData.SOCKnode -> serialize how can I solve this problem? Thank you ~

Without this commit, installation of emms fails with:

make: *** No rule to make target 'autoloads'.  Stop.

Since Emacs 27 the package cl is deprecated, the replacement is cl-lib, which is available since Emacs 24.3.

This patch replaces cl by cl-lib and drops support for Emacs versions less than 24.3. Dropping older Emacsen is required, because cl-lib is a builtin starting from version 24.3 and doesn't need an extra package from ELPA.

Testcases for past issues (in test/issues) still contain cl. Most of them seem to be broken and need further investigation.

This patch is tested with test/run-ert.sh, which outputs:

Ran 10 tests, 10 results as expected, 0 unexpected (2021-01-30 13:24:54+0100, 0.672122 sec)
1 expected failures

and manually by daily usage for a month now.

This PR addresses issue #2792.

Build el-get for Emacs 27.1 as well.

Closed, because el-get moved to Github Actions.

@tarao Fixed all compilation errors. The PR doesn't look nice, because it fixes several unrelated errors, due to unreliable CI. I created a follow-up issue to fix the remaining compilation errors.

$ byte-compile -Werror *.el

... nothing.

$ for i in *.el ; do byte-compile -Werror $i ; done

In toplevel form:
el-get-byte-compile.el:64:9:Error: reference to free variable ‘el-get-byte-compile’

In toplevel form:
el-get-core.el:42:9:Error: reference to free variable ‘el-get-verbose’

In toplevel form:
el-get-dependencies.el:186:1:Error: the function ‘el-get-read-package-with-status’ is not known to be defined.

In toplevel form:
el-get.el:199:28:Error: The compiler ignores ‘autoload’ except at top level.  You should
     probably put the autoload of the macro ‘el-get-bundle’ at top-level.

In toplevel form:
el-get-list-packages.el:452:1:Error: the following functions are not known to be defined: el-get-recipe-filename, el-get-package-type, el-get-package-def, el-get-package-method, el-get-version-to-list, el-get-recipe-pprint, el-get-read-all-recipes

In toplevel form:
el-get-methods.el:46:11:Error: reference to free variable ‘el-get-allow-insecure’

In toplevel form:
el-get-recipes.el:331:1:Error: the function ‘el-get-github-parse-user-and-repo’ is not known to be defined.

In toplevel form:
el-get-status.el:81:21:Error: reference to free variable ‘el-get-status-file’

This issue causes spurious CI failures.

@tarao For some strange reason https://github.com/dimitri/el-get/pull/2838/checks?check_run_id=2813750015 gives:

In toplevel form:
methods/el-get-go.el:42:43:Error: reference to free variable ‘el-get-dir’

I cannot reproduce it locally, but I fix that nevertheless.

@stephan-cr I think I could fix it now. It seems that byte-compilation tests should run if there is change outside recipe/.

Here are results from a test pull request; I think these are what you have expected: https://github.com/dimitri/el-get/pull/2838/checks?check_run_id=2813750015

Strangely, running

$ byte-compile -Werror *.el methods/*.el

gives me

Source file ‘/home/stephan/.emacs.d/el-get/el-get/el-get-notify.el’ newer than byte-compiled file; using older file

In toplevel form:
el-get-notify.el:24:1:Error: Alias for ‘el-get-growl-notify-path’ should be declared before its referent

Neither Travis-CI nor GH do fail for this.

It looks good now.

@tarao It must be something different, the message fatal: origin/master...HEAD: no merge base appears for the successful ones as well.

Aha, I guess it is about a workaround replacing TRAVIS_COMMIT_RANGE. I will fix it but it may take some time.

Rebased to current master. Some check for Emacs 24.5 fails with fatal: origin/master...HEAD: no merge base.

@stephan-cr

I had the same question and looked into the test code. It seems that byte-compilation is skipped for recipe-only changes (non-code changes) except on Emacs 24.5. So, it should do byte-compilation test on your replace-cl branch after rebasing master branch.

@tarao I saw your changes. Great move! But I wonder why byte-compile -Werror *.el methods/*.el doesn't fail for Emacs 27.2.

@stephan-cr I've added Emacs 27.2 to CI during switching from Travis CI to GitHub Actions in #2836. Could you continue #2802 with this?