Skip to content
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

unused argument (std.nox = std.nox) #359

Closed
cjvanlissa opened this issue Jun 10, 2024 · 2 comments
Closed

unused argument (std.nox = std.nox) #359

cjvanlissa opened this issue Jun 10, 2024 · 2 comments

Comments

@cjvanlissa
Copy link

Dear Yves,

since the recent lavaan update, people are experiencing the following error when calling summary() on a lavaan object with syntax generated by tidySEM:

Error in lav_object_summary(object = object, header = header, fit.measures = fit.measures,  : 
  unused argument (std.nox = std.nox)

Since I am not modifying the call to summary, I'm wondering if you have an idea where this comes from?

@TDJorgensen
Copy link
Contributor

Hi Caspar,

This inconsistently occurred (or didn't) after making this change, and not just with your package. Without it being reproducible, we hoped it would not become an actual problem---sorry for the inconvenience. There seemed to be some mysterious behavior where R remembered the old summary() method even after the newer lavaan was installed. This occurred until updating the blavaan package after this PR, where you can see some discussion about the weirdness that occurred.

So if you(r users) have blavaan installed (maybe it was loaded when the error occurred?), a solution could be to uninstall blavaan, then installing the new version that just went to CRAN. It is possible that some other package besides blavaan could cause the same mysterious problem, but we could not locate any of lavaan's reverse-dependencies that explicitly use the std.nox= argument, so hopefully updating blavaan is the solution. Please keep us updated, and link to this issue when anyone posts about this.

Thanks,
Terrence

@yrosseel
Copy link
Owner

yrosseel commented Jul 2, 2024

I think we can close this issue now. But feel free to reopen if this issue persists.

@yrosseel yrosseel closed this as completed Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants