Next Generation Shell Weekly Meetings, 16 Jan 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: NGS weekly meeting #14 - 2022-01-16

Description

Project website - https://ngs-lang.org/

Builds for Red Hat based distros - https://github.com/ngs-lang/ngs/pull/524

Milestone 0.2.15 - UI infrastructure - I/O -- https://github.com/ngs-lang/ngs/milestone/10

IO Design issue - https://github.com/ngs-lang/ngs/issues/526

IO Design wiki page - https://github.com/ngs-lang/ngs/wiki/IO-Design

JSON RPC - https://www.jsonrpc.org/specification

Netty - https://netty.io/

A

Hello, welcome to weekly ngs meeting ngs stands for next generation. Shell weekly meetings are about recent progress and future plans. uh We have ricardo today contributor, I'm ilya the author of the project. Let's go okay, ricardo. Do you want to start or you want me to start.

B

Yeah, I can start so not much so there are some pull requests going forward. um Good thing is that we manage also to to do the red hat builds, that's also another pull request, that is there and yeah. We are trying to move forward with it.

A

Yeah, nice, okay um yeah. So let me uh then share the screen and share the milestones and all that and we'll try to be orderly here. Okay, share screen milestones yeah. Here we go okay. So what do we have so as to 0 to 14? It was finished over a week ago. uh We just need to release the version um zero to 15. I'm kind of thinking about this so and the first thing that I think that we need to do is uh to design the I o.

B

A

To be able to make a server which will be used by the ui, um so I I was looking into several uh let's say: patterns or designs, and okay, it's all here. uh So I was looking into this guys so uh at this point in time, I'm mostly impressed by neti channels um as they uh implement the intercepting filter pattern, uh as we see it in many other places too. I think that native that did a great job in the implementation.

A

So I think I'll take uh many ideas from there uh with um cutting some corners. Let's say to make it uh smaller, easier to implement and maybe simpler, but I think I'll be basing the io after 90 like in most in most of the things.

A

um Okay go back, okay, so pull requests. So, okay, let's go back one. So that's all for zero to 15.. I maybe I'll be adding some issues here, but probably io design and implementation is big enough to have its own release.

A

uh Actually, it is unknown amount of work, but it's pretty big that I already know for now. um Okay, so let's go back to the pull request. So first.

B

Shall we add these pull requests to 0 to 14 milestone because it would be nice? You know that zero to 14 would come. You know at least we did the build jobs and whatever all of them.

A

I want to merge it before everything. Yes,.

B

uh That will probably make sense, because you know I don't want to bring these changes into the this io. This io milestone. Why.

A

Because, in that.

B

One we should just focus on that one on the thing right.

A

Maybe, but also there is nothing that stops us from like shifting the release making a new one in the middle. You know up to you, so this one.

B

Okay, here's what I mean.

A

Instead, 0 to 15 will be 0 to 16 and 0 to 15 will have like different miscellaneous things.

B

A

Example, but you know if something uh will be uh completely ready from my point of view, we can there's no like issue merging this, like releasing this with this release. Okay, so what do we have improved github actions that was the reddit build.

B

Yeah so that brings all the red hat builds.

A

Yeah, it also fixes yeah. I still have some doubts because you know there's like still um things that you didn't answer here, for example like here stuff, which is not answered. I know.

B

It's not possible, not joking, I did so. I didn't saw that one yet, but do you know why, before I dive into this, we need to handle the man, because both the man and that one changes the actions yeah build actions, yeah.

A

So I looked at man today. I had some comments. You say you handled them. Yes, yeah! It's fixed, uh okay, try to consolidate, conciliate, install and test new change; okay, as well I'll need to go over this. I will not do this online. uh Well, I assume it's sold website.

B

When we merge that one, we probably should merge with the with the dislike, you know ah how do they call it? I know I got a blank with uh give me a hint. ah Let me look, they have a word for that. They have a special word for that too much.

B

Weed squash question much: why? Because you know there is no need, you know to have these nine commits, because most of them were like so on on both mac man os and on the improved gh actions. There were a lot of commits that was just to test. If you know the github actions worked, yeah.

A

I uh never did that, so I don't know how to do that, but.

B

Yeah you have squash from this verse will be combined into one committee: okay, yeah.

A

It makes more sense.

A

How do you do this in the common line.

B

On the command line, it's kind of the same, there is like a thing to do it yeah.

A

Okay, interesting, okay, good that you mentioned the asset that we can make some order.

B

Yeah, especially on these, you know, improved ph actions. If you look there, there are already.

A

Yeah, I think there.

B

A

uh Okay, so and website yeah we need to get there. I don't actually remember where it is stuck. Is it on my side on your side on.

B

Your side, you need to look into the website too branch, because it has.

A

B

Changes that you wanted, this is getting out of hand. Okay, look there yeah.

A

That's why we need to.

B

Close them yeah, we need to.

A

Start closing them: okay, yeah. I need to look ah yeah requested your review. Yes, okay, that's pretty clear! Okay! So uh we have this and.

B

A

B

Rid of these middle clean up improvement tasks so that we can start. You know with the big things.

A

A

Well, I guess uh that would be it right: yeah, yeah, okay, so our biggest ah yeah, okay, yeah almost forgot. So I in this um io infrastructure I was thinking. How would something talk to ngs and um uh I was thinking something like some simple protocol like json, based something very simple, and I found something actually which is pretty close to what I imagined not exactly but pretty close, uh and this is called json rpc and it is actually pretty simple.

A

Okay, you have json with request and json with response uh request. Object has json rpc, which has version, which is must be two: zero have methods. That's a function name, parameters to a function; it's either array or object. So it's like either positional named and id of the request. That's what you have and your response is json rpc, with version result error. If there was an error and the id of the request, that's pretty much it so by the way. I I didn't remember that this exists, and I was thinking hold a moment.

A

There is like language server right for the visual studio code and stuff, like that. How does it work? And I went there and I seen that they they're using this json. I think they are actually using this over http, but it doesn't have to be over http, so it can be just simple things. The only uh downside that I see here.

A

So these are all like lines: okay, request response, but if you have a batch that could be multi-line and uh well, then you need to parse it. You know, get the multiple lines and you need to understand where the json ends- and I don't know, I'm wondering whether it will be like valid implementation without supporting batch, something.

B

Is off under example, what it just ends there? You know it's like.

A

It's not available yeah yeah.

A

Maybe something didn't pass. The request correctly in this batch.

B

Yeah it's for the echo, oh! No, they are okay.

A

ah Okay, parser, okay, okay, uh okay, I did now parser ah and you can't have ids.

B

A

Yeah, that's pretty shitty situation. How about this jason erpis wait.

B

What about the answer of the first one, uh this I don't know.

A

B

The above one right, he filled two parts, the second, the second line, but he probably could pass the first line.

A

uh Rp sequel is empty, uh it doesn't say so. Maybe all with the world batch is not valid. In this case I don't know a rpc called batch.

A

ah Okay, they just have one source, one, two, one with the.

B

That makes more sense yeah exactly that's why I was saying that the other one was a bit weird, because I was expecting something like this right. Yeah.

A

B

One is okay, but the second one failed right.

A

Yes, ah invalid request: yeah, when you can parse your json, that's fine, but here you couldn't. You could.

B

A

Yeah, okay, that's the whole protocol. That's that's why I like it by the way when I was thinking I was thinking about something like which has like uh content playing encoded like in let's say four bytes uh wisconsin and then json something it would be like. I think it would be simpler to parse because you don't need to find the end of line, and you know to cut this.

A

So I don't know anyhow just.

B

You see if, if, if.

A

We wouldn't implement the batch, it's pretty simple. uh Oh just.

B

To write may send.

A

To send several request options, client may send so we'll search the responses, apparently yeah supposed to implement that um yeah.

B

But on this patch it's easy right: you go one by one and you go by order and you rip it.

A

Yeah but but the parsing is not simple, you cannot like take one line and parse json from it. It's multi-line right here, wait hold on yeah, so.

B

Okay, it's it's lining that reason. Yeah, it's good.

A

Yeah, so how how you need to like understand where your json ends right? You need to pass json and you need in this json to understand that you passed an array and I don't think I have low label json parsing methods exposed like that. My json methods can get a string and pass adjacent. But if you don't know when the string ends well, you can't parse it, but.

B

Like right now, you can do like a get of an array. Then you go with the four over the array right and just send to your method, one by one.

A

You want me to pass this manually yeah. You just do a four right.

B

A

Gonna know, that's gonna be pretty bad because it may be on separate string or separate line on not separate line with one of them. It can be like finished here right and then how do I know that the closing bracket is uh is actually for this one? Maybe it's this one right so, like you can't like take it.

B

Pretty much the world.

A

Jason parser to understand that this bracket actually belongs to the closing bracket, belongs to the opening brackets. You can't just guess it right.

B

Yes, you can parse it json. That is an array.

A

You can pass a json, but if you know where it ends here you don't know where it ends. You have a request. It's streaming, bytes right.

B

ah This is based by streaming: okay,.

A

Well, you get it somehow over the network right so or anything. So you don't know where it ends. There is no like packets or anything.

B

A

uh There was something about transport transport. I think it's transport agnostic. So you don't? You don't know about transport, so you can yeah over http uh over sockets, yeah, sockets and then socket. You don't know where.

A

Where is the yeah the fragment yeah? But I hope by implementing this uh we will be able to find many tools on the other side which could work with that or maybe maybe I can find c implementation for this thing, unfortunately, and be done with this also good for.

B

Sure you will find something yeah.

A

But I I would like that uh c implementation to use the same json libraries that I'm using just not to duplicate json libraries right yeah anyhow, if it, if I don't, find anything appropriate in c. That's not it's not supposed to be a big problem to parse it.

A

Of course, I will not do it in c I'll expose lower level implementation, implementations of json, parser or parts, and then everything else will be in ngs, of course, and that could be already be in this um io design layout, where you have like a channel, and you have these filters in the channel. So you have the channel. You have filter which can cut chunks up out of the stream, and then you have like next filter already gets json and that's pretty much. It.

B

Yeah, by the way you have you have already on github something on that.

A

Yeah, probably.

B

A

Yeah, I guess that uh that would be it for now.

A

uh So, let's finish uh how to say uh like and subscribe: do that: okay see you guys, you.