DFFML Rolling Alice: Engineering Logs: Volume 0: Architecting Alice, 13 May 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Architecting Alice: Volume 0: Context: Part 32: Implementing hack and slash style

Description

https://github.com/intel/dffml/discussions/1369#discussioncomment-2739704

A

A

A

No more chrome.

A

Too, distracting.

A

From reading too many specs, not writing enough code, let's write some code.

A

A

A

So, let's do scan results. So let's call this.

A

All right so run scan.

A

A

Pdid and scan service input- okay, hopefully it's last.

A

A

A

All right so changing last to result.

A

Okay, what do we got? So it's not running for us anymore great. I wish I could get mermaid to render the terminal. ah That would be great, don't get distracted.

A

A

Let's trigger this thing,.

A

A

All right, so background default. This thing is going to sit here and.

A

It is going to.

B

Background default is a subflow we're going to so we launch background default as a subflow. So what we can do.

A

Is we can um actually just have an auto start operation? So let's just have an auto start operation god. Why didn't? I just write the code. Jesus.

A

I'm not very good at planning trying to get better should have just written a code fairly.

A

Fairly well versed in that part. Okay, so, let's see background default. Oh splendid, okay,.

A

Oh just splendid: okay, okay,.

A

This caps are gone: okay,.

A

A

Run system context holy- this is so easy.

A

Wow who knew all you have to do is write the code shocking background default. Oh my god, look at this look at this look at this look at this look at.

B

A

All right, this is fantastic.

A

Oh man, I was so stressed out for nothing. uh I was reading all these specs all right now, then, I'm just kidding. We had to read all those specs and they were good. They were good specs.

A

um So let's get into this our background default. What do we want you to do? uh Well, we want you to, um let's see so: let's go check out, run data flow.

A

So, on default run okay on default subflow, so we kick off the subflow. Look at the results. We return the results as a um custom data flow context: okay, aha, okay, yeah, so move string, privilege, validation to another location. So you know quite honestly, I think we should just call run command.

A

We should really have the.

A

More configurability on dfp process, or maybe we're just using it wrong. I think we're just using it wrong. I think it is configurable enough all right so what time time check? Okay, 15 minutes!

A

Okay, so, basically.

A

Let's figure out.

A

B

Background default, so we want this to basically.

A

Start a sub flow.

A

Please start subflow.

A

Background default. Okay, so, let's see.

A

A

System context, hey huzzah here it is our first system context, delightful, all right, so system context. Well, what is a system context? Well, we know that a system context.

A

Contains the data flow right or the architecture.

A

A

The inputs all right, let's see static values, the static values, so static, values, architecture and orchestrator right, and so you can have nested orchestrators, but you need a top-level orchestrator.

A

Okay, so what is this.

A

So this is input. Data, okay and they'll- have their origins and that'll map to the input data of these. So basically this is so seed, I think. Are we pulling out seed then.

A

Yeah so we'll do a validity check so to do a validity check.

A

So to do a validity check, uh ensure all inputs in architecture allow lists.

A

Okay, so we have the architecture with the extruder and we'll introduce a plug-in, basically we'll introduce.

A

We'll introduce a plug-in system over data flows to uh we'll introduce a plug-in system over dataflows and we'll basically call dataflow architecture so do to do uh data flow. So dataflow is one type of architecture.

A

um Base class for architecture is open arc. Texture.

A

Data flow is n.

A

Should register itself under open architecture plugins.

A

Okay, so we'll go ahead and we'll create this open architecture class and then we'll um we'll make dataflow a plug-in of that. But for now all we have is dataflow. So the other thing is so architecture, orchestrator right and then parent.

A

Architect, architecture, orchestrator and parent.

A

A

A

Architecture orchestrated.

A

And then we have the inputs.

A

No, we have to context system context and then the context within that right, so list input set context.

A

So some context apparent equals none all right so just like our input objects. um So let's see.

A

Okay, so just like our input objects, we must always. I think the parent parameter on the input object is a required parameter, because uh if you don't set it and then all of a sudden, you start losing where these input objects come from and we never want to lose that lineage. Okay. So where are we at time check? Eight minutes? Okay, so context?

A

A

All right: here's a memory input set context.

A

Wow, it's so much easier when you have code in front of you.

A

Every input set- oh remember, it puts that.

A

Isn't there an input, set context concept.

A

All right puts it.

A

What is this, why does this not use the double context? Entry pattern, there's a issue for this. ah This is old.

A

I know it was me, but I want to know when it was.

A

Yeah october 2019.

A

yeah, I think I wrote this in a hurry.

A

This is that giant, commit.

A

Yeah, what does stat stay out? Yeah? That's what I thought yeah! This is the most unhelpful commit look at that three pdfs added.

A

Oh, that was a yes yeah. That was quite that was interesting. um Okay, so.

A

So memory input set does not follow the double context and true pattern. This is concerning um everything else follows the double context in jupiter, okay memory, so there's wait, no parameter set memory, parameter, set, parameter, sets and input sets, do not follow the double context, entry pattern and I never really liked how they have these async parameters that don't have a handle on their input network.

A

I think that we shouldn't be passing around input sets without an input network attached. I don't think that's a good idea.

A

I think that's there's just something wrong about it.

A

There's just something that ain't right about it.

A

And we're input set. Okay, let's make a note.

A

So they really should have handles the input network for things like removal, etc.

A

All right- and they must so they must be there for our critics etc. uh Must.

A

Is the double context? Entry pattern? Okay,.

A

A

Memory input set base and puts it over here puts a config. Oh base inputs are context. That's what I'm looking for all right inputs, a config.

A

Face input set context.

A

Our space inputs are context based inputs are context, handle base context, handle.

A

Face inputs are context, so base input set. Context doesn't necessarily take anything on init, so we can just say so. In here's string, input set context.

A

Okay, I gotta go.

A