8000 train_continuous error with R 4.5.0 · Issue #60 · giocomai/ganttrify · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

train_continuous error with R 4.5.0 #60

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.

Sign up for GitHub

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

Jump to bottom
Closed
mdcodedoctor opened this issue Apr 29, 2025 · 5 comments
Closed

train_continuous error with R 4.5.0 #60

mdcodedoctor opened this issue Apr 29, 2025 · 5 comments

Comments

@mdcodedoctor
Copy link

Hi there.

Amazing package and fully agree with the need for nice looking Gantt charts. Hope to see it reach CRAN someday.

The package seems to be broken in R 4.5.0 (via RStudio). Tried to run just a basic plot using your test data in the packag.
Tried doing this while only loading this package after launch.

library(ganttrify) 

ganttrify(
  project = ganttrify::test_project,
  spots = ganttrify::test_spots,
  project_start_date = "2021-03",
)

I get the following error:

Error in train_continuous(x, self$range, call = call) : 
  unused argument (call = call)

If I revert back to 4.2.0 which was also installed, the plot is outputted as expected with no issue.
@giocomai
Copy link
Owner

Thanks for reporting, I'm not yet on 4.5, will check as soon as I get a chance

@mdcodedoctor
Copy link
Author

Thanks for reporting, I'm not yet on 4.5, will check as soon as I get a chance

No worries! It's not time critical for me at least.

@giocomai
Copy link
Owner

I've just tested this on a fresh 4.5 install, and everything seems to work as expected. Do you have this issue on a fresh install? Unless there is some more specific info, I'll probably close this issue. The error you're pointing at seemingly stems from the scales package, so I wonder if you have either a very old or very new (development) version of that package which may be causing this issue.

@mdcodedoctor
Copy link
Author

I am actually not sure if I updated that package between my first post here, but I just tried to rerun it with 4.5.0 (With scales 1.4.0) and had no issue. So at least it's resolved and I am sorry that you had to spent time on what might have been an issue on my end!

Thanks for looking into it, it's a great package you've made

@giocomai
Copy link
Owner

No worries! thanks for the kind words!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@giocomai @mdcodedoctor
0