5 Jun 2024 |
| Vic H changed their display name from Waffle Lee to Vic H. | 15:23:54 |
Vic H | Hi guys :) This is my first time to join this kind of open source project community. I am not so good at coding but I can contribute some of my knowledge in cybersecurity domain. | 15:46:39 |
7 Jun 2024 |
Red | In coding you become a coder π Welccome Vic H
I guess joining is a way to give purpose to coding have you navigated the Librecube projects already ? What do you prefer doing for now - python, javascript, erlang, rust, visual basic*, cobol* ?
| 12:29:09 |
Red | * In coding you become a coder π Welccome Vic H
I guess joining is a way to give purpose to coding have you navigated the Librecube projects already ? What do you prefer doing for now - python, javascript, erlang, rust, visual basic*, cobol* ?
* nope.
| 12:29:15 |
shayanmajumder | Maybe we can add *Fortran in the list too π
https://primalnebula.com/updating-voyager-from-15-billion-miles-away/ | 12:35:09 |
| Vaishak Vidhyadharan joined the room. | 13:52:10 |
Rajkumar | yes why not, good idea | 18:50:28 |
Rajkumar | ok | 18:51:08 |
8 Jun 2024 |
Hasan | Hi raj, The PLUTO syntax highlighter has already been published on the open-vsx marketplace | 18:15:34 |
Hasan | Feel free to look into the extension repo's develop branch for more information and to make any improvements βοΈ | 18:17:05 |
Hasan | Extension's open-vsx link: https://open-vsx.org/extension/LibreCube/pluto-syntax/ | 18:17:55 |
Hasan | Repo link: https://gitlab.com/librecube/templates_and_tools/vscodium-pluto-syntax | 18:18:26 |
Hasan | Download 045b227d-2d3c-4c3b-987c-ba669e417a7d.png | 18:19:37 |
Hasan | I have tested the extension on both vscode and vscodium and it works well π | 18:20:32 |
9 Jun 2024 |
Hasan | * Hi raj, The PLUTO syntax highlighter has already been published on the open-vsx marketplace and VSC marketplace | 13:40:55 |
10 Jun 2024 |
Artur Scholz | @room Be reminded to add yourself to the map! You do not need to have contributed yet, your interest counts already! π | 13:02:29 |
Artur Scholz | * @room Be reminded to add yourself to the map (https://librecube.org/community/)! You do not need to have contributed yet, your interest counts already! π | 13:02:50 |
Rajkumar | Oh great Hasan, Nice Workπ | 19:32:31 |
Rajkumar | Take care, Arthur, and get well soonβ. | 19:37:53 |
11 Jun 2024 |
| Maulana joined the room. | 07:40:07 |
14 Jun 2024 |
Artur Scholz | Download Screenshot_2024-06-14_17-54-56.png | 16:00:27 |
Artur Scholz | cajt: Thanks for you suggestions on Raspi proto board. I implemented most of them. | 16:01:05 |
Artur Scholz | * cajt: Thanks for you suggestions on Raspi proto board. I implemented most of them. Will send for production now. | 16:01:17 |
Artur Scholz | If someone is inclined to work on test cases for spacecan that would be great. The problem is that one needs to bring up a virtual CAN network for the tests. That can be done locally, but I do not know how to do it for the gitlab pipelines. You can see my attempts in the test branch... https://gitlab.com/librecube/lib/python-spacecan/-/network/tests?ref_type=heads | 17:59:03 |
15 Jun 2024 |
cajt | creating, modifying and deleting network interfaces might be limited for a good reasons. I would also assume that HiL Testing is the prefered approach in the long run, so why not skip it. Maybe add a commit hook to remind the commiter to have passing tests for the has being commited, to have some process in place. Otherwise one might have to setup a self-hosted runner, and set it up accordingly (would be similar for a HiL too). | 07:12:53 |