You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have traced the issue down to the piece of code that tries to construct mcols for outer matches, but fails if there are no mcols to start with and instead of generating a DataFrame of the appropriate number of rows (and zero cols), it always seems to generate a 0,0 DataFrame, which then fails to merge with (another empty) mcols frame on the right. If there are some metadata in the right ranges, then all works without a glitch.
Thanks for the report - will get around to this in the next week or so. In the meantime you are more then welcome to contribute a PR that fixes this issue :)
Hi, here is a quick example to demonstrate:
I have traced the issue down to the piece of code that tries to construct mcols for outer matches, but fails if there are no mcols to start with and instead of generating a DataFrame of the appropriate number of rows (and zero cols), it always seems to generate a 0,0 DataFrame, which then fails to merge with (another empty) mcols frame on the right. If there are some metadata in the right ranges, then all works without a glitch.
https://github.com/sa-lee/plyranges/blob/da3c4f40292ac3a4cd0ad9c4b383ca9ab0a3db91/R/ranges-overlap-joins-outer.R#L44
The text was updated successfully, but these errors were encountered: