Should

migrate-call-by-name

work on standalone plugins? I'm trying to migrate my plugins now but it fails out immediately:

$ pants --source-root-patterns='["pants-plugins"]' migrate-call-by-name pants-plugins/::
13:00:06.23 [ERROR] '/home/ts/.cache/nce/68f5608a60df9b97aab453d453817a4ded400d1d8ec7ede7ec14bcac83421a7b/bindings/venvs/2.24.0/lib/python3.9/site-packages/pants/option/subsystem.py' is not in the subpath of '/home/ts/Repositories/pants-backends' OR one path is relative and the other is absolute.

Eventually, yes, but not yet - it doesnt handle out of repo plugins at last check

Ah, drats.

yeah i havent even looked into it - I was going to wait until Pants was ported before worrying about external plugins

Gotcha. I just bumped mine to 2.24 so figured I'd migrate before releasing the next version.

Yeah, that's what I do a lot in the repo, because rule_helpers aren't handled well by the migration. I'm pretty sure the migration code looks for it, but the scheduler might not extract them properly