I am getting the error here in this Travis build, and I cannot reproduce it locally. Yes, I realize that I do not have a minimal reproducible example, but I do know that it happens within tidyselect::vars_select(). Has anyone else encountered this before? I cannot find any mention of lang_unnamespace() in a Google search.
See if modifying your travis yaml to include the dev versions of the tidyverse packages help.
It looks like you're not calling rlang::lang_unnamespace() directly, correct? That function appears to have been removed, but tidyselect::vars_select() is still trying to call it.
I arbitrarily went back to the beginning of the year to see this old version.
The file doesn't even exist in today's version.
Related
I have the following module:
module TestModule
export foo
function foo()
return 1
end
end
and a calling script:
using .TestModule
println(foo())
I get the following error:
ERROR: UndefVarError: TestModule not defined
According to the documentation this should work. I know this can be accomplished via include() but I read that this can cause inconsistencies when trying to include the module multiple times. Another way of achieving this seems to be editing the LOAD_PATH but that seems rather inconvenient and also causes the project to not be portable.
I'm wondering if those are the only current solutions to the problem or if there is something better (The two other post regarding this question are 6+ years old and the docs currently state that this is the way to do it, so I wonder if the problem has been fixed by now). Any help is greatly appreciated.
Cheers
I'm closing this thread as it has been tagged a duplicate multiple times now. I conclude from this that there currently is no way of splitting code into multiple local modules while maintaining portability. The canonical way of splitting code into modules is by adding the module paths to the LOAD_PATH (julia push!(LOAD_PATH, "\path\to\module")). Thanks to everyone for the feedback nonetheless!
Edit:
After executing the TestModule file it works for this example (I missed that this was necessary, at least in VSCode). My actual program still produces module-not-found errors but since I'm unable to reproduce them in a simple example I'll try figuring it out myself first.
Another Edit:
Renaming the modules solved the problem. I suppose the names were already taken by public packages. For any reader wondering how to solve this problem without renaming the custom module, please have a look at this documentation
Cheers
Whenever I try to deploy my firebase cloud functions, it considers poor formatting as a real error and doesn't let me proceed. For example:
error Expected linebreaks to be 'LF' but found 'CRLF' linebreak-style
Could someone tell me how to prevent this and let me deploy my code regardless of its formatting? Thanks
As I saw you mention in the comments, there is a previous iteration of this issue.
You can see there that you have to configure your linebreak-style in your .eslintrc or in your source code. You can also follow the approach of the second answer and ignore the linebreak-rules to avoid this warnings/errors from happening.
For further information, refer to the documentation.
I'm currenty cleaning up my first big R project and at a point, where I have a lot of functions implemented but I am not sure, which function got called and used by me in an other script and which function got never used. So now I want to get all calls of this function in my project. Is this possible?
I'm using RStudio and a lot of other IDEs I've used got a feature like this, so I was wondering if this is also implemented in RStudio.
I searched the web and stack overflow, but got no answer, so I assume that this is not possible but I wanted to ask, just in case it IS possible but I didn't found the right answer.
Thank you!
I have a -lelf option in my makefile, I want to know: how does it choose the version of libelf.so to link (e.g. libelf.so.0 or libelf.so.1)? I do have a libelf.so.1 in my system, as well as a libelf.so which links to libelf.so.1. When I compile the code, everything is fine, however, when I try to run the binary, it reports: "can not find libelf.so.0". Any guide on solving this problem? Thanks in advance.
Ok, finally I understand something. I can specify which version of the .so at compile-time (I can force it to link to libelf.so.1, while it will cause some problem at run-time). It seems the best way is to find the required libelf.so.0 anyhow.
When using the program slicer of Frama-C version Oxygen, I have the problem that the resulting slice uses undeclared variables.
I searched for existing postings to this topic before and found this:
http://bts.frama-c.com/print_bug_page.php?bug_id=806
There it is mentioned that the bug was fixed in the Nitrogen version of Frama-C. Maybe this change was not carried over to Oxygen? Like in the description of the existing posting it only happens for blocks with just one statement.
I cannot attach the example source code since it is from a customer project.
I have checked the exact steps described in the bug report you mention with Frama-C Oxygen (and csmith 2.0.0 for Csmith's runtime library), and everything works fine: it's very likely that you're experiencing another issue, but without the code, it's impossible to say more.