bolkedebruin
bolkedebruin
Currently only one fragment can be handled, it should be made more robust to check the length of the packet and wait for all data to arrive.
I just noticed that the glyphs cache is always disabled https://github.com/neutrinolabs/xorgxrdp/blob/12cc88cfa16b9bbe4ec4553bab0e597310e14e43/module/rdpClientCon.c#L845 But this code is also more than 3 years old. Is it still required to be disabled?
Guava is not backward compatible and if an including project also uses Guava this results in conflicts. By shading Guava this is not an issue anymore.
The requirements for dev contain severely outdated linters and formatters: flake8 is at version 6 black is at version 22.X This make it tougher to develop against FAB as IDEs...
The new structure introduces eager loading, which we don't want. This re-instates lazy loading at the expense of that storage_options might not be fully parsed. @potiuk @ap-- @Taragolis --- **^...
### Body ``` from airflow.io.path import ObjectStoragePath a = 'file:///tmp/xcom/dag/scheduled__2021-12-03T04:56:00+00:00/task_1/a5e36734-11f2-4487-8aa7-46c70cc9718b' b = 'file:///tmp/xcom' y = ObjectStoragePath('file:///tmp/xcom/dag/scheduled__2021-12-03T04:56:00+00:00/task_1/d301899e-64bf-4a4d-8599-83c6cf097183') x = ObjectStoragePath('file:///tmp/xcom') y.is_relative_to(x) False ``` ``` from upath import UPath x = UPath("file:///tmp/xcom/dag/scheduled__2021-12-03T04:56:00+00:00/task_1/d301899e-64bf-4a4d-8599-83c6cf097183")...
As there is no way to associate a client with its NetBIOS name treat the address slice as empty if it only contains a NetBIOS address. This makes the behavior...
Microsoft clients can request tickets with their Netbios names which are typically net resolvable in a non AD context. In the case that the address list only contains NetBIOS addresses...
## Checklist - [X] I've read the [publishing documentation](https://hacs.xyz/docs/publish/start). - [X] I've added the [HACS action](https://hacs.xyz/docs/publish/action) to my repository. - [X] The actions are passing without any disabled checks in...
While experimenting with SSO tokensin the username field I noticed that with long usernames (dont know exactly the number) the MS clients will report error 0xD06 and disconnect. This seems...