Olm issueshttps://gitlab.matrix.org/matrix-org/olm/-/issues2020-07-06T15:38:48Zhttps://gitlab.matrix.org/matrix-org/olm/-/issues/1merge GitLib CI config from famedly2020-07-06T15:38:48ZHubert Chathimerge GitLib CI config from famedlyhttps://gitlab.com/famedly/libraries/olm/-/blob/master/.gitlab-ci.yml
- make sure license is changed to Apache2https://gitlab.com/famedly/libraries/olm/-/blob/master/.gitlab-ci.yml
- make sure license is changed to Apache2https://gitlab.matrix.org/matrix-org/olm/-/issues/2Is it libolm.dylib.3 or libolm.3.dylib?2020-07-22T09:49:05ZTomIs it libolm.dylib.3 or libolm.3.dylib?Trying to build a bot using https://github.com/anoadragon453/nio-template I followed the instructions on https://gitlab.matrix.org/matrix-org/olm.git to build olm and the python bindings.
It built successfully, but building olm generate...Trying to build a bot using https://github.com/anoadragon453/nio-template I followed the instructions on https://gitlab.matrix.org/matrix-org/olm.git to build olm and the python bindings.
It built successfully, but building olm generated a file called `libolm.dylib.3` and the python bindings seemed to expect a file called `libolm.3.dylib`.
Renaming `libolm.dylib.3` to `libolm.3.dylib` in `/usr/local/lib` made the python bindings work.https://gitlab.matrix.org/matrix-org/olm/-/issues/6CI pipeline broken?2021-06-07T19:16:42ZHubert ChathiCI pipeline broken?https://gitlab.matrix.org/matrix-org/olm/-/pipelines/5731 failed, even though it is for the same commit as https://gitlab.matrix.org/matrix-org/olm/-/pipelines/5723 which succeeded, and the only change between that commit and https://git...https://gitlab.matrix.org/matrix-org/olm/-/pipelines/5731 failed, even though it is for the same commit as https://gitlab.matrix.org/matrix-org/olm/-/pipelines/5723 which succeeded, and the only change between that commit and https://gitlab.matrix.org/matrix-org/olm/-/pipelines/5722 is documentation changes. Re-trying the failed pipeline still fails.
When I check out that commit and test locally, it succeeds. I even tried using the same docker image, building, and testing, and it succeeds.
@arunn can you take a look and see if you can figure out what's going on?https://gitlab.matrix.org/matrix-org/olm/-/issues/9Add java bindings for new fallback keys api2021-12-02T08:46:53ZValereAdd java bindings for new fallback keys apihttps://gitlab.matrix.org/matrix-org/olm/-/issues/10Add OLM_OPTIONS definition to olm.js prefix2022-04-27T20:49:30ZRobert LongAdd OLM_OPTIONS definition to olm.js prefixCurrently if you import `@matrix-org/olm` in your Javascript project it gives you an error saying that `OLM_OPTIONS` is undefined. I think we're missing a definition of `OLM_OPTIONS` in the olm.js prefix file [here](https://gitlab.matrix...Currently if you import `@matrix-org/olm` in your Javascript project it gives you an error saying that `OLM_OPTIONS` is undefined. I think we're missing a definition of `OLM_OPTIONS` in the olm.js prefix file [here](https://gitlab.matrix.org/matrix-org/olm/-/blob/master/javascript/olm_prefix.js.in#L5).
It should be as simple as adding `var OLM_OPTIONS;`https://gitlab.matrix.org/matrix-org/olm/-/issues/11Better logging in C layers2022-06-14T05:22:21ZTravis RalstonBetter logging in C layersref https://github.com/vector-im/element-web/issues/10955ref https://github.com/vector-im/element-web/issues/10955https://gitlab.matrix.org/matrix-org/olm/-/issues/14Simplify the documentation around message payload encoding2024-02-13T17:27:45ZValereSimplify the documentation around message payload encodingCurrently the doc is explaining a sort of [encoding with key values pairs](https://gitlab.matrix.org/matrix-org/olm/-/blob/master/docs/olm.md?ref_type=heads)
> The keys are encoded as a variable length integer tag where the 3 lowest bit...Currently the doc is explaining a sort of [encoding with key values pairs](https://gitlab.matrix.org/matrix-org/olm/-/blob/master/docs/olm.md?ref_type=heads)
> The keys are encoded as a variable length integer tag where the 3 lowest bits indicates the type of the value: 0 for integers, 2 for strings....
And talking about tags `0x0A`, `0x10`, `0x22`
Given that it is just plain protobuf, like `0xA` is `0| 0001 | 010` that is tag `1` and type `2` (bytes).
Probably we could just simplify and put the proto definitions:
```
package messages;
syntax = "proto3";
message PreKey {
bytes one_time_key = 1;
bytes base_key = 2;
bytes identity_key = 3;
bytes message = 4;
}
message Normal {
bytes ratchet_key = 1;
uint64 chain_index = 2;
bytes cipher_text = 4;
}
```