- 18 Dec, 2024 2 commits
-
-
Przemyslaw Kaminski authored
-
Przemyslaw Kaminski authored
-
- 09 Dec, 2024 1 commit
-
-
Przemyslaw Kaminski authored
Also, add -Werror to tests so that no warnings in tests are reported anymore.
-
- 29 Nov, 2024 1 commit
-
-
Przemyslaw Kaminski authored
-
- 06 Nov, 2024 1 commit
-
-
Przemyslaw Kaminski authored
-
- 30 Oct, 2024 2 commits
-
-
Przemyslaw Kaminski authored
-
Przemyslaw Kaminski authored
-
- 29 Oct, 2024 1 commit
-
-
Przemyslaw Kaminski authored
-
- 23 Oct, 2024 2 commits
-
-
Przemyslaw Kaminski authored
-
Przemyslaw Kaminski authored
-
- 10 Oct, 2024 1 commit
-
-
Przemyslaw Kaminski authored
-
- 04 Oct, 2024 1 commit
-
-
Przemyslaw Kaminski authored
-
- 18 Sep, 2024 1 commit
-
-
Grégoire Locqueville authored
-
- 12 Sep, 2024 3 commits
-
-
Przemyslaw Kaminski authored
-
Przemyslaw Kaminski authored
-
Przemyslaw Kaminski authored
Remove allow-newer:*, allow-older:* in cabal.project file and instead list these explicitly. This is a big step for managing dependencies.
-
- 05 Sep, 2024 2 commits
-
-
Przemyslaw Kaminski authored
-
mzheng authored
-
- 04 Sep, 2024 1 commit
-
-
Fabien Maniere authored
-
- 02 Sep, 2024 1 commit
-
-
Alfredo Di Napoli authored
Remove the calls to `recvMalloc` in favour of using the (patched) `recv` from the original nanomsg library, which shouldn't segfault anymore. The reason for using `recv` are a few, but mostly the fact that `recv` can allocated arbitrary-long payloads data (up to the 1MB limit) without an hardcoded limit like `recvMalloc` was imposing. Furthermore, `recv` does resource cleanup for us via `c_nn_freemsg`, whereas `recvMalloc` is not thread/exception safe. Consider the implementation: ``` recvMalloc :: Receiver a => Socket a -> Int -> IO ByteString recvMalloc (Socket t sid) numBytes = do ptr <- mallocBytes numBytes -- receive by blocking the thread len <- c_nn_recv sid ptr (#const NN_MSG) 0 -- (#const NN_DONTWAIT) str <- C.packCStringLen (castPtr ptr, fromIntegral len) free ptr return str ``` If any exception (synchronous or asynchronous) strikes _before_ the call to `free`, we would be leaking C memory.
-
- 29 Aug, 2024 1 commit
-
-
mzheng authored
-
- 28 Aug, 2024 1 commit
-
-
Przemyslaw Kaminski authored
-
- 22 Aug, 2024 1 commit
-
-
Grégoire Locqueville authored
-
- 21 Aug, 2024 1 commit
-
-
Przemyslaw Kaminski authored
-
- 19 Aug, 2024 1 commit
-
-
Alfredo Di Napoli authored
-
- 31 Jul, 2024 1 commit
-
-
Yoelis Acourt authored
-
- 29 Jul, 2024 1 commit
-
-
Przemyslaw Kaminski authored
Also, throttle messages to avoid flooding the client
-
- 19 Jul, 2024 1 commit
-
-
mzheng authored
-
- 12 Jul, 2024 1 commit
-
-
mzheng authored
-
- 09 Jul, 2024 1 commit
-
-
Alfredo Di Napoli authored
It integrates servant-routes which allows to list and export the server backend routes.
-
- 04 Jul, 2024 1 commit
-
-
Alfredo Di Napoli authored
This commit moves `GargConfig` and the other config-related data structures back into gargantext, so that they can be edited and expanded without needing to worry about the prelude project.
-
- 26 Jun, 2024 4 commits
-
-
Alfredo Di Napoli authored
This commit extends the reverse proxy for the microservices so that it would serve a custom `/config` file which would contain the correct baseUrl to initialise the websocket connection correctly.
-
Alfredo Di Napoli authored
Still needs to fix some hardcoded URLs. The problem with websockets is that they use the first URL fragment to determine the documentId, therefore we cannot proxy to `http://localhost:8009/notes/<frameId>` because the underlying WS connection will use `noteId=notes`, which is wrong.
-
Alfredo Di Napoli authored
-
Alfredo Di Napoli authored
-
- 18 Jun, 2024 1 commit
-
-
mzheng authored
-
- 17 Jun, 2024 2 commits
-
-
Przemyslaw Kaminski authored
-
Przemyslaw Kaminski authored
-
- 03 Jun, 2024 1 commit
-
-
Alfredo Di Napoli authored
-
- 22 May, 2024 1 commit
-
-
Przemyslaw Kaminski authored
-