disable_remnant=True,disable_prior_sampling=True ignored (for bilby)?

With current master (ed582027), if I load a pBilby (d9725af) file it seems to ignore both the disable_prior_sampling=True and disable_remnant=True options:

>>> from pesummary.io import read
>>> d=read("merged_result.json",disable_remnant=True,disable_prior_sampling=True)                    
DEBUG: pycondor - PESummary : Drawing prior samples from bilby result file
DEBUG: pycondor - PESummary : PESummary does not have a 'standard name' for the following parameters:
[...]
DEBUG: pycondor - PESummary : Starting to generate all derived posteriors
2021-01-18  11:58:13 PESummary WARNING : The redshift is being approximated using interpolation. Bear in mind that this does introduce a small error.
WARNING: pycondor - PESummary : The redshift is being approximated using interpolation. Bear in mind that this does introduce a small error.
2021-01-18  11:58:20 PESummary WARNING : Could not find reference_frequency in input file. Using 20Hz as default
WARNING: pycondor - PESummary : Could not find reference_frequency in input file. Using 20Hz as default
bbh_final_spin_precessing_HBR2016(): The argument of the square root is -0.000408; truncating it to zero.
2021-01-18  12:04:00 PESummary INFO    : Averaging the final spin from the following fits: function bbh_final_spin_precessing_projected_UIB2016 at 0x7fdb7fe1a8b0, function bbh_final_spin_precessing_projected_Healyetal at 0x7fdb7fe1a820, function bbh_final_spin_precessing_HBR2016 at 0x7fdb7fe1a940
INFO: pycondor - PESummary : Averaging the final spin from the following fits: function bbh_final_spin_precessing_projected_UIB2016 at 0x7fdb7fe1a8b0, function bbh_final_spin_precessing_projected_Healyetal at 0x7fdb7fe1a820, function bbh_final_spin_precessing_HBR2016 at 0x7fdb7fe1a940
2021-01-18  12:04:01 PESummary INFO    : Averaging the peak luminosity from the following fits: function bbh_peak_luminosity_non_precessing_UIB2016 at 0x7fdb7fe1aa60, function bbh_peak_luminosity_non_precessing_Healyetal at 0x7fdb7fe1aaf0
INFO: pycondor - PESummary : Averaging the peak luminosity from the following fits: function bbh_peak_luminosity_non_precessing_UIB2016 at 0x7fdb7fe1aa60, function bbh_peak_luminosity_non_precessing_Healyetal at 0x7fdb7fe1aaf0
2021-01-18  12:08:07 PESummary INFO    : Averaging the final mass from the following fits: function bbh_final_mass_non_precessing_UIB2016 at 0x7fdb7fe1a3a0, function bbh_final_mass_non_precessing_Healyetal at 0x7fdb7fe1a1f0
INFO: pycondor - PESummary : Averaging the final mass from the following fits: function bbh_final_mass_non_precessing_UIB2016 at 0x7fdb7fe1a3a0, function bbh_final_mass_non_precessing_Healyetal at 0x7fdb7fe1a1f0

In this case the prior step seemed pretty fast, so I'm not sure if it's actually drawing anything or just erroneously printing that message. Then, the final spin and mass seem instantaneous but the peak luminosity takes a few minutes. (The file has 234k samples.)

Note: Running on two different installations (but same versions), I got the "DEBUG" messages only on one for some reason...

Also, not sure if this is bilby-specific, but that's the only results I've tested.