Next Generation Shell Weekly Meetings, 20 Feb 2022

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: NGS weekly meeting #19 - 2022-02-20

Description

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

Discord - https://discord.gg/6VqgcpM

Arch Linux build is broken - https://github.com/ngs-lang/ngs/issues/556

Separate GitHub action (install NGS) into own repository - https://github.com/ngs-lang/ngs/issues/534

A

Hello welcome to weekly ngs meetings. Ngs stands for next generation shell. um Here we have ricardo contributor, I'm ilya, author of the project. uh Weekly meetings are about progress made and uh future plans. um Let's go ricardo. Would you like to discuss anything or you would like me to start.

B

Yeah, you can start this time.

A

Okay, so uh I'll start I'll, try to start uh in an organized manner, so I'll share my screen and I'll go over uh recently opened and closed issues. How about that.

B

A

Okay, share screen, firefox issues. Okay, I think I'll. Do it smaller, okay, yeah, okay, so uh our linux build is now broken. uh I commented this out in the build, but I pinned the issue here at the top. uh We need to check that. I don't know it sounds like probably they upgraded something or downgraded or whatever just broken um yeah. So we still have the auto verification discussion going on.

A

uh It is interesting and I need to understand more and more what should and can be done or can and should okay, so we have that uh other than that. I noticed that replace uh doesn't work properly.

A

So for now I committed something to dev branch, which would at least prevent this from happening and throw exception instead, but actually uh that's a functionality which is not implemented when you replace a prefix of the string or a suffix of a string. It's just not implemented. So that's why um it was happening because it was catching like kind of the default implementation and it is not right for prefixes and suffixes uh okay. So that's from the ongoing.

A

uh Yeah support it would be a 32-bit arcs, that's yeah. We commented on that and read me actually I'm trying to organize readme just a bit more, so it will all be in the table.

A

No, I would like to show that uh the problem is that I actually don't know which architectures we are building hold a sec I'll share the screen. It will be cleaner, clearer, um where's, this thing here. Okay, so I had this string. I was trying to normalize this comment that.

B

A

Debian on different architectures so, which architectures are this- I don't know.

B

A

Kind of what github gives you yeah, but we need to actually write this down because it's not just any 63 64-bit. It's.

B

Like it's, I 6 8.

A

It's amd 64, probably right.

B

Or or that yeah yeah now it's called like that yeah yeah, but we can check.

A

Yeah we should check, because I want to normalize this and not to be like comments. I want it to be a table from which everything is uh is clear.

A

By the way nice move from jetbrains that they support the editing of the stables. You see.

B

A

Nice uh yeah hold yes, okay, so that's this topic, so these are the the um the things which are open, I'm still working on working on the release script uh and since I switched from.

A

Github command line to curl. I today discovered that the uh api limit is 60. Api calls per hour for anonymous users, it's apparently per ap, and since I was testing, I just hit that limit, and now I um corrected the script, but it didn't have the chance uh to test it. So now it just slips more between calls and uh doesn't do more than one per minute. So we should be good uh well, since I would assume that I'm the only one using github api on the particular ip that I have and you are.

B

The only one using it either way.

A

Yeah, all the others are using github command line for which they have a token and which has, I don't know like one per second limit, or something like that. If you have, uh if you are authenticated, so that was probably the reason that the examples were for um gh command.

A

uh So what I have now I and was not able to test. I actually have this thing, which commits the update to change log with the current version instead of unreleased at the top, and then it actually follows the start of the build it. It waits until the build starts. It calls a github api to see that the build starts and it also waits for the build to finish properly, but I was not able to test that yet by the way, I think I did not commit.

A

uh Let's maybe take a quick look uh into how the script looks by now.

A

Build release, okay, so more slips.

A

What I like is the retry function, the built-in, which is very helpful here, I'm using interesting thing, which is called dot tap. The tab takes uh an argument and the function. It runs the function on the argument, but the result of the whole thing is still the first argument.

A

So if I just remove this, it's exactly the same like it behaves exactly the same just without debugging yeah, that's what it enables.

A

Otherwise debug will need to return x in here, and I debugged, because I had a problem here. It was another letter and it was giving the tree id and not the commit id, and I wanted to go to uh capture this uh into files and that's what this debug does. It stores um the response which we get from the api. It stores us into a file which is named after the current timestamp dot json.

A

So that's for now, so we have one retry which waits for the build to start and we are waiting for exactly one build which is having this commit id and after we have this workflow run.

A

uh We then queries that url of that workflow run and we wait for the conclusion and conclusion must be either null or success now means it's. It did not finish yet, and success means it was okay.

A

So what do we have here? So let's say we have null here, then this expression returns false and that tells retry to continue to try and if it was success it means it tells retry to uh to stop trying because it was successful so and if it is not null and not success, it will crash just here and this assert.

A

So if the build failed, it will not continue.

A

That's pretty much it for uh the script and I guess from my side in general,.

B

Yeah, so I guess my site, so not much news, so I just assigned myself to this arch linux. Build is broken.

A

Okay, good start.

B

Looking into that, um outside from that, I do require more information from you on.

A

B

Other issues that are open that are assigned to me.

B

Because I don't know what to do there.

A

Which issues and which information do you need.

B

So five, three four and five three three.

A

Five: three three.

B

And five, three four yeah.

A

Yeah hold a second declutter.

B

Yeah, you need to know exactly what you mean by that.

A

Yeah, I can't, can you maybe like comment here that you want more information.

B

A

533, that's the first time. I think I hear that how about four three four also I I open this issues yeah and uh yeah. If something's not clear, you write it in the issue, yeah sure well separate github action. I think it's pretty clear right.

B

No, I don't know what you mean by that.

A

Like everybody else where the github action is not in the same repository as uh the uh language or whatever it installs.

B

Why shouldn't the github action be the same repository.

A

uh The the most uh important reason is that the readme looks uh bad if you uh go to the github action and you're trying to interact with the action right. If you look like any other action for any other language or like any other project,.

B

Yeah, you don't mean the actions actions, but you mean.

A

They installed whatever yeah.

B

This other thing, yeah.

A

Installing json, that's why it's installed in json yeah, the one that is on yeah. The readme looks like uh in their repositories. It looks like okay, this is a github action for installing blah blah and then our github action. It looks like that's the language and it's like, I think, it's pretty confusing for everybody. Yeah.

B

But you know the problem of having another repository is that we have so. We cannot uh use use these with the same name which sucks okay, because currently we could just ngs slang, slash engine.

A

I understand that and still we need to do it because it's confusing.

B

A

uh And I mean everybody else: does it this way? So it's probably a kind of um acceptable by everybody. By now I guess.

B

I didn't so yeah, I didn't show any best standards on that. So, let's.

A

Say github, I don't know, install node.js action. Let's see how that actions setup dash, node setup dash yeah. We can call setup dash and gs. I guess.

B

A

And let's see the readme usage yeah that the usage is very specific: yeah yeah, I'll, uh okay, I'll post, you the link to node.js roughly, like I'm, adding this to the issue. You know what I'll edit the issue.

A

Yeah and it's like it's not like.

B

Yeah, that's fine.

A

Just like everybody else, okay, anything else from your side.

B

ah But then we have to deal with the versions there. Well also, I also have it on the repository yeah.

A

But you have like 10 different uh setup actions in into which you can look and see it's.

B

A

Probably with uh at v1 at v2 stuff, like that.

B

A

They actually have parameters for that.

B

Now, currently, here right, you see yeah.

A

Every time yes yeah and automatically.

B

This is automatically, uh but we can have.

A

Yeah, but we can have our action, our workflow, which updates the action and to say which sets. You know the default to the whatever version, or we can say that if the version is not specified, I think the action actually can take parameters right.

B

It's not about the action is about you know. If you have this in a separate repository, it means you have.

A

B

In both places.

A

No, no, they actually.

B

Can't the action.

A

Can go to your repository and take the latest.

B

Yes, but we don't want to have the latest, we want to have the special version.

A

B

Somebody wants to.

A

Install specific version of ngs, which they showed what they need to do. They need to specify the version when they call the action.

B

Yes, yes, if you click there, that's what they tell you.

A

B

And what I'm saying right is that if you have this on another repository, when you release ngs, you don't release the action. You have to go and release the action manually so that it builds the new version.

A

No, I don't understand why uh the separate repository, which has the action why it can't, by default installs the latest, released ngs, why? Why not hold a sec? Let's, let's, let's take a look at uh how.

B

Setup works. Okay. The question: the question is not that earlier the question.

A

B

uh Do you know it's like if you release something on ngs, the action has no idea that you released something.

A

B

So you have to go there and trigger it so that it builds a new version based on the latest thing.

A

B

Little reaction, I don't understand.

A

B

Like docker images, you have to build it.

A

B

A

No, it completely isn't.

B

A

Using node 12 main.

B

Here bam there you go, you have a special if you.

A

Want to keep this occasionality? Okay, uh sorry! This is becoming not very productive. uh We can rediscuss this after. You take a long look at the node.js action: okay, because they they don't look like they dealing with versions at all.

A

B

Well, they have version.

A

B

A

You just pass it as a parameter and that's it.

B

ah I I understand what you mean: okay, they pass it as a parameter on the thing itself. Okay, I understand.

A

Yeah, that's what I tried to talk about the time. So I don't understand.

B

What you mean yeah, okay, yeah, that's that we can do it yeah sure.

A

Okay, doc so yeah, you commented on the other one in which I still need to look. Yes,.

B

A

Three: three: it's there: okay.

A

Take a look, that's clear, more information, okay, okay, doc, so anything else before we, ah I learned a new shortcut aob, you ask aob, and that means any other business.

A

uh I I participated in a few other meetings. Although I'll tell you later doesn't matter, then they they use. This shortcut aob.

A

B

A

Anyhow, so um well how to say like and subscribe see you next week then see.

B

A