Repository navigation
Refactor/fixes - #710
Merged
Merged
Refactor/fixes#710
Conversation
timcadman
marked this pull request as ready for review
October 13, 2026 14:48
⏳ 4 of 5 checks reported so far
Tested against Logs: Devtools checks · Code quality · Armadillo unit tests · Opal unit tests · Codecov |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## v7.0-dev #710 +/- ##
============================================
+ Coverage 68.64% 68.93% +0.29%
============================================
Files 142 142
Lines 5785 5788 +3
============================================
+ Hits 3971 3990 +19
+ Misses 1814 1798 -16
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
StuartWheater
approved these changes
Oct 15, 2026
StuartWheater
left a comment
Member
There was a problem hiding this comment.
- Changes appear consistent
- The CRAN were very particular about error/warning production and required changes around suppressing error messages. I don't think there changes will be a problem.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Background
Fixes found in a full review of the v7.0 refactor (batches 1–10): a data leak, behaviour that changed relative to 6.3.5, and small doc and code errors.
What's changed
ds.asListdata leak:asListDSreturned the converted object to the client. It is now an assign function. It was an aggregate only to work around an old repository quirk with lists; tests confirm lists now assign correctly on Opal and Armadillo..loadServersideObjectnow errors on a NULL object ("is NULL") for every function, includingds.class, which used to return"NULL". Deliberate breaking change: NULL objects only arise from mistakes such as a typo inds.make.meanDS/varDSaccept logical, so an all-NA column no longer breaks the call.corDS/covDSaccept factors again (correlated on level codes).lengthDS/dimDSaccept any class.meanSdGpDSaccepts a numeric grouping variable.ds.cor/ds.covignorey(with a warning) whenxis a matrix or data.frame.ds.changeRefGrouptreats a numericrefas a level name again.BooleDSaccepts"TRUE"/"FALSE"/"NA"asV2.levelsDSchecks the privacy level first.ds.mdPatterncombine: pools columns by variable name, not position.md.patternorders columns by missingness, which differs between studies, so variables could be mixed.seqDS: from/to/by/length.out are converted withas.numericinstead of being looked up as object names.glmChecks,ds.table: restore the user'swarnoption on exit. This fix was on 6.3.x but never ported to v7.