rneovim.git/test/functional/api/server_notifications_spec.lua, branch tmp Neovim fork with Rahm's personal hacks. test(api): mark "notify cancels stale events on channel close" fragile 2021-12-01T03:27:34+00:00 James McCoy jamessan@jamessan.com 2021-12-01T03:27:31+00:00 4342b81e8d0f253015e3a3fa72f5fc00f9a2f30d This is already skipped in all CI environments, so it should also be skipped in environments that don't like fragile tests. Since there's no convenient way to express these concisely, add the explicit fragile skip. 
This is already skipped in all CI environments, so it should also be
skipped in environments that don't like fragile tests.  Since there's no
convenient way to express these concisely, add the explicit fragile
skip.
docs: naming conventions 2021-09-09T13:28:11+00:00 Justin M. Keyes justinkz@gmail.com 2021-08-27T10:59:13+00:00 9f3679cbfd8633886f1ab43cd761c58da3b8a29b 






feat(api): nvim_get_chan_info: include "argv" for jobs #15537
2021-09-01T14:29:38+00:00

Justin M. Keyes
justinkz@gmail.com

2021-09-01T14:29:38+00:00

0603eba6e713b2bd25cbbb55caf2342b0ccdece9

ref #15440




ref #15440






ci(tests): skip "stale events on channel close" (#15278)
2021-08-05T13:07:26+00:00

dundargoc
33953936+dundargoc@users.noreply.github.com

2021-08-05T13:07:26+00:00

5130bc071e7720e261b7251c1716df69e33ae1dd

This test sporadically hangs CI (cf. #14083); skip until the actual code is fixed.




This test sporadically hangs CI (cf. #14083); skip until the actual code is fixed.






rpc: don't handle stale requests on already closed channel
2020-12-23T22:58:56+00:00

Björn Linse
bjorn.linse@gmail.com

2020-12-15T09:15:51+00:00

95352f490a24f5e3a1cc788d297105e4eadf1481












API: nvim_unsubscribe(): Handle unknown events #8745
2018-08-28T08:20:19+00:00

Daniel Hahler
git@thequod.de

2018-07-14T16:23:08+00:00

643ef257b3e58928071de73aaae4b5e5911802ec

close #8745





close #8745







test: rename next_message() to next_msg()
2018-03-11T11:43:42+00:00

Justin M. Keyes
justinkz@gmail.com

2018-03-08T23:24:38+00:00

fd4021387e696c7a2da4ad776789cfbb938d5332












functests: Replace execute with either command or feed_command
2017-04-09T00:24:08+00:00

ZyX
kp-pav@yandex.ru

2017-04-08T21:12:26+00:00

65fb622000af8e3dbb65480e1581758ecf4ba3e2

Hope this will make people using feed_command less likely: this hides bugs.
Already found at least two:

1. msgpackparse() will show internal error: hash_add() in case of duplicate
   keys, though it will still work correctly. Currently silenced.
2. ttimeoutlen was spelled incorrectly, resulting in option not being set when
   expected. Test was still functioning somehow though. Currently fixed.





Hope this will make people using feed_command less likely: this hides bugs.
Already found at least two:

1. msgpackparse() will show internal error: hash_add() in case of duplicate
   keys, though it will still work correctly. Currently silenced.
2. ttimeoutlen was spelled incorrectly, resulting in option not being set when
   expected. Test was still functioning somehow though. Currently fixed.







test/api: Specify handling of VimL errors, v:errmsg.
2016-10-23T23:10:23+00:00

Justin M. Keyes
justinkz@gmail.com

2016-10-22T22:02:22+00:00

43309d1993a9affc8d6b73fbd4721e6256c28712

TODO: Also spec behavior of Press-Enter prompt for these API functions.





TODO: Also spec behavior of Press-Enter prompt for these API functions.







msgpack_rpc: Fix crash in log_server_msg
2016-06-24T13:53:26+00:00

ZyX
kp-pav@yandex.ru

2016-06-11T18:59:01+00:00

0d56118d862f0a366da57c82a6e995f1a51b0fc7

It appears that used msgpack library is not able to parse back message created 
by msgpack_rpc_from_object() if nesting level is too high, so log_server_msg now 
cares about msgpack_unpack_next() return value. Also error message from 
server_notifications_spec.lua is not readable if something is wrong (though at 
least now it does not crash when parsing deeply nested structures).

log_server_msg() in the test reports

    [msgpack-rpc] nvim -> client(1) [error]        "parse error"




It appears that used msgpack library is not able to parse back message created 
by msgpack_rpc_from_object() if nesting level is too high, so log_server_msg now 
cares about msgpack_unpack_next() return value. Also error message from 
server_notifications_spec.lua is not readable if something is wrong (though at 
least now it does not crash when parsing deeply nested structures).

log_server_msg() in the test reports

    [msgpack-rpc] nvim -> client(1) [error]        "parse error"