583 commits

Author	SHA1	Message	Date
cschen	02d7e71180	properly export the event object to the python glue	2025-03-17 13:09:01 +01:00
cschen	480f210a60	changed the worker recognizing the closure of the controller from error to debug message.	2025-02-17 23:24:05 +01:00
cschen	1f388b2eb4	some rewording in the log messages	2025-02-15 22:09:17 +01:00
frelodev	c41fd40696	bumped to pyo3 0.23 (#81) ... Co-authored-by: cschen <cschen@codemp.dev>	2025-02-15 17:47:00 +00:00
alemi	a4c2583b6f	feat: introduce tracing::instrument and more debug	2025-02-15 13:38:50 +01:00
zaaarf	194a49c970	feat: handle unknown cursor ... ...by discarding and logging a warning, instead of displaying an empty one.	2025-02-01 16:55:55 +01:00
alemi	32255bec55	fix: send only delta patches via DiamondTypes	2025-01-13 12:37:58 +01:00
zaaarf	34fd4bdf82	feat: workspace worker ... Co-authored-by: alemi <me@alemi.dev>	2024-11-19 23:57:39 +01:00
cschen	28e04ab446	Merge branch 'dev' into fix/python/getter-for-nested-elements	2024-11-20 09:40:29 +01:00
zaaarf	e4c81c0d0d	test: wait more	2024-11-20 00:13:20 +01:00
cschen	1b97ef0b90	adds getters for complex nested elements.	2024-11-19 19:42:17 +01:00
alemi	0c8c4a61ea	fix(lua): dont serialize hash when None ... because it becomes an `userdata: NULL` and not `nil`, what??	2024-11-17 18:58:22 +01:00
alemi	456a78d7c9	feat(lua): back to using official mlua ... since we can't have `send` and `module` we store `LuaFunctions` inside the registry and pass around keys to them. ehh, basically what i was doing with the callback channel but now twice i guess, idk i hope this can get better eventually ™️	2024-11-16 16:43:46 +01:00
alemi	03a158e678	feat: cursor+buffer controllers know their ws id	2024-11-16 16:42:58 +01:00
alemi.dev	4fcab00d34	chore: cargo features (#66) ... * chore: changed features layout now using `dep:` and `crate?/feat` syntaxes (introduced in rust 1.60). this may mess with lua rockspec	2024-11-16 16:28:46 +01:00
zaaarf	6f2dda463e	docs: missing ` on code	2024-11-15 11:43:40 +01:00
zaaarf	e25b82aefb	chore: cargo fmt	2024-11-05 19:17:22 +01:00
zaaarf	fb6e1cdeea	feat: use single tuple in buffer fixture too	2024-11-05 19:17:01 +01:00
alemi	97ee48629d	test: wait 1s so it can catch up in case its slow	2024-11-05 01:48:45 +01:00
alemi	bf9ea18d67	test: dont use ws fixture coz leave wont work	2024-11-05 01:42:21 +01:00
alemi	ed0e05ffe2	test: drop workspace so that it disconnects	2024-11-05 01:30:49 +01:00
alemi	b549f82ce5	test: even more time to disconnect?	2024-11-05 01:29:19 +01:00
alemi	2e05c3d757	test: split down invite_to_workspace_and_lookup	2024-11-05 01:24:46 +01:00
alemi	f350bc0ea8	test: dont use is_ok(), propagate err	2024-11-05 01:09:39 +01:00
alemi	59f9096fb6	test: split lookup and create/delete tests	2024-11-05 01:04:45 +01:00
alemi	2155f0d36c	test: improved tests cleanup and logic ... Co-authored-by: cschen <cschen@codemp.dev>	2024-11-05 00:19:42 +01:00
alemi	3f0b04af6e	feat(test): added fixture macro	2024-11-05 00:19:29 +01:00
alemi	300f6620c0	fix: cleanup for buffer fixture ... idk who made this?? it was already fixed in dev env, uncommitted Co-authored-by: cschen <cschen@codemp.dev> Co-authored-by: zaaarf <me@zaaarf.foo>	2024-11-05 00:18:06 +01:00
alemi	c42b091b63	test: better assert_or_err messages ... Co-authored-by: cschen <cschen@codemp.dev>	2024-11-05 00:16:27 +01:00
alemi	ee2ced51ca	chore: removed need of adding type hints ... Co-authored-by: cschen <cschen@codemp.dev>	2024-11-05 00:15:17 +01:00
zaaarf	888f7fd80c	docs: better wording in detach_buffer docs	2024-11-03 20:11:36 +01:00
zaaarf	c1c9dea033	tests: actually delete the buffer in the buffer fixture	2024-11-03 20:11:21 +01:00
zaaarf	c08e209e06	tests: cleanup redundant code	2024-11-03 19:58:09 +01:00
cschen	c0bff45989	fix(test): add more clear explainations of what went wrong.	2024-11-03 17:53:27 +01:00
cschen	3773ebfd7d	test: moved around previously existing tests. and other formatter shenanigans	2024-11-03 17:26:14 +01:00
cschen	7f17d1fd6e	test: inviting users to one's workspace	2024-11-03 17:24:47 +01:00
cschen	84bfc45fc8	test(WIP): added skeleton for testing of behaviour when deleting workspace with people attached. ... Need to know what is the expected behaviour that we want.	2024-11-03 17:24:08 +01:00
cschen	35b9b12aaf	test: deleting twice or non existing is an error	2024-11-03 17:23:00 +01:00
cschen	9d0c961ac2	test: delete empty workspace	2024-11-03 17:22:41 +01:00
cschen	781fd9ba42	test: leaving workspaces, attaching after leaving	2024-11-03 17:22:13 +01:00
cschen	fdd272646d	test: attaching to a non existing workspace is an error	2024-11-03 17:21:06 +01:00
cschen	ccb5406ccf	test: attaching to workspaces and making them active	2024-11-03 17:20:30 +01:00
cschen	9ff9a47d86	test: can't create workspace more than once	2024-11-03 17:20:09 +01:00
cschen	44e5e390eb	chore: implement from ConnectionError and from RemoteError for AssertionError	2024-11-03 17:19:38 +01:00
cschen	dc627dc6af	fmt: formatter shenanigans	2024-11-03 17:18:47 +01:00
cschen	7a535d4492	test: workspace creation and lookup	2024-11-03 17:18:24 +01:00
zaaarf	111020afd8	test: buffer fixture	2024-11-02 23:26:42 +01:00
alemi	cd4e09c1cd	test: show for which test workspace was ... basically fixtures leak workspaces when errors occur, so to better debug what is happening every test now names its workspace. this is tedious and should probably be removed eventually but for now it helps a ton	2024-10-30 17:33:51 +01:00
alemi	e0b919bae8	fix: more time in tryRecv to compensate longer RTT	2024-10-30 14:22:51 +01:00
alemi	90568bba8d	test: ignored a test, fixed another ... leftover assert!(false) for debugging, test_cant_delete_other_buffers will not work since server doesn't track buffer ownership yet	2024-10-30 13:50:08 +01:00