Hi James,

Am Mon, Dec 30, 2024 at 10:25:38AM -0500, schrieb James McCoy:

I'm working on bisecting the Vim change which broke the test to see if anything needs to be changed on the Vim side, but I'm filing this in
case YCM can be fixed.

Thanks for looking into this and reporting it to vim-ycm upstream!


That said, I am not quite sure how to proceed now… this seems not like
an issue that deserves to block testing migration for vim, so do you
think vim upstream is going to deal with this some way or another soon
or is that going to take a while if ever?

vim-ycm upstream isn't usually supporting varying versions and doubly
so in its tests, so I presume they will more or less wait until an
affected vim reaches their CI which might or might not be a long while.


I am happy to look into getting 'my' tests to pass with old/new vim if
that helps/unblocks us in the meantime.


Best regards

David Kalnischkies

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEE5sn+Q4uCja/tn0GrMRvlz3HQeIMFAmd2cr0ACgkQMRvlz3HQ eIPqnA//QDPuMSmj076R0VUbiDZ6emUVkKs/wOayXKRRj26iky0bthI26+byJqR5 ukl/i6Q4V3x0nuc9SXf1C6IhYT7nE3OsvhLdWcPnzcos1LYVt+zFVI5FDFoVyKlD 7OSCClPCA0a/90poDfPi5y6zDep/Eoes0IS4aszDbGGUeLZBH24ge0aF9Fvwtjeh 6PQkh9uoz5BWujPmaZIOnEeh8kN35Lj1AuFT0Pyb9V+AaDAYdZbMJx4+M17Rj2xg u4f05fuA81FXQKJ3/SmRlWAE4Vy1E0qLes+JIvcfS2YVFECaQbYbdJsS6/69RQ9x fUVqkmu1/5IO68zcWCCJVyAh6lNGyMPPzGDeyNKT5fAYG1a04Y3K7lpBmtVZkO9w g7rhR5XP2qRrnMGL3cvvO6BPcn1LiGLfYuJl5Dcc1O+qylTFrifBaOayw4T4qJGC 3+PzyhunYLITgcTwrWBjWWrvn74YmsDtHQVa6lU2Kfb38vyDd1E25VSlXzhUTaYo 7j76dUKbEZBWfot1rTk9VCRkp80cBZ4zbseo5RFDJJR/IROF1oAik6e1MgBbXikf WjyBhsPdR41Nkj6jNIHrSt2zo8mas+/WkjUJRmVcPeBLEtsC4vzmgmFUZ7M0+3FW VxQMrb6TvWkF5foES6gKj9AgYJu/ZWqkDduXhkuuatRCpFuF0tI=
=wFGW
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Thu, Jan 02, 2025 at 12:04:34PM +0100, David Kalnischkies wrote:

Hi James,

Am Mon, Dec 30, 2024 at 10:25:38AM -0500, schrieb James McCoy:

I'm working on bisecting the Vim change which broke the test to see if anything needs to be changed on the Vim side, but I'm filing this in
case YCM can be fixed.

Thanks for looking into this and reporting it to vim-ycm upstream!

That said, I am not quite sure how to proceed now… this seems not like
an issue that deserves to block testing migration for vim, so do you
think vim upstream is going to deal with this some way or another soon
or is that going to take a while if ever?

I have a couple other things to work on first, but if there's still not
any progress in either upstream when I come back to Vim I'll close this
by reverting that particular Vim patch.

Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)