Datasets:
willtheorangeguy
/
2021-Ship-It-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
1.8k
[2658.56 --> 2658.74] Cool.
[2658.74 --> 2664.16] So this is great to be able to see the difference.
[2664.62 --> 2668.48] And I suppose, I'm just wondering if we were to take this memory address
[2668.48 --> 2674.24] and if we were to look into that file, into that perf map file,
[2674.56 --> 2677.30] would we be able to figure out what this is?
[2678.26 --> 2679.64] It's possible.
[2679.64 --> 2684.64] The problem is in this case, so we can look at the process
[2684.64 --> 2689.20] and we can kind of go through the steps of what the Parker agent would do manually.
[2689.76 --> 2695.80] And then we can try to see if we can figure out why this is not able to symbolize this.
[2695.92 --> 2698.06] My theory is because of what we can see here,
[2698.82 --> 2702.86] the way that this binary code was memory map,
[2703.16 --> 2707.34] we weren't actually able to understand where it's mapped.
[2707.34 --> 2713.38] So the way that this works is let's go back to our terminal, I would say,
[2713.88 --> 2716.20] and we can inspect this actually,
[2716.56 --> 2722.28] the way that binary code is memory mapped for the process.
[2722.74 --> 2725.58] So we can again look into our procfs.
[2725.94 --> 2728.16] This is where all the magic happens in Linux.
[2728.36 --> 2728.54] Okay.
[2728.64 --> 2730.36] So do we want to go like on the host?
[2730.76 --> 2733.34] We can do the host or the container.
[2733.64 --> 2734.38] Yeah, it shouldn't matter.
[2734.56 --> 2735.12] Both should work.
[2735.22 --> 2735.44] Okay.
[2735.44 --> 2736.84] So yeah, let's go on the host.
[2736.84 --> 2739.62] So we want to go on that.
[2739.80 --> 2740.18] Let's see.
[2740.24 --> 2742.12] We shall have the CD.
[2742.78 --> 2743.30] There you go.
[2743.50 --> 2744.10] That's the proc.
[2744.40 --> 2744.62] Yes.
[2745.02 --> 2745.28] Right.
[2745.80 --> 2748.10] And here there's a file called maps.
[2751.02 --> 2751.54] Yes.
[2752.68 --> 2753.00] Yeah.
[2753.10 --> 2755.30] So let's have a look at what it says in there.
[2755.30 --> 2763.84] And the way that symbolization effectively works is that we take that memory address that we saw.
[2763.98 --> 2764.28] Yes.
[2764.66 --> 2770.98] And we try to find in which range within this file that memory address is from.
[2771.08 --> 2771.90] So this one right here.
[2771.94 --> 2772.18] Okay.
[2772.72 --> 2773.92] So that's the memory address.
[2774.58 --> 2776.76] So do we need to do 7FF?
[2776.76 --> 2779.34] I mean, I can see something here, 7FF.
[2780.10 --> 2792.54] Well, if you're able to search within your terminal, maybe we can, you know, it's a bit of a hack, but we can search for the address that you have copied.
[2792.54 --> 2800.24] And we can just try to remove certain digits until we maybe get a match.
[2800.58 --> 2800.66] Okay.
[2801.26 --> 2802.40] So let's remove those two.
[2802.44 --> 2807.18] And as we can see, the ranges don't have the 0x prefix here.
[2807.24 --> 2808.90] So we're going to need to remove that.
[2809.38 --> 2809.54] Okay.
[2809.54 --> 2812.02] So yeah, this is an interesting one.
[2812.10 --> 2814.82] And this is exactly why this is not working.
[2815.02 --> 2818.36] So the way that this table works is that we have these ranges.
[2818.62 --> 2827.32] And then it tells us on the very right, this is the binary that this executable code came from.
[2827.32 --> 2841.98] And so actually the stack, I want to say this could be a, I don't know if it's necessarily a bug, but what can happen in some languages and in Go, this can happen as well.
[2841.98 --> 2857.32] So sometimes when we do the stack, like the stack trace snapshots, when we retrieve them from eBPF, sometimes the kernel does them a bit too tall and we don't fully understand why.
[2857.74 --> 2864.42] Like basically it, what it does is it goes back and walks the stack and sometimes it walks too far.
[2864.42 --> 2870.96] And in this case, it doesn't actually make sense that the stack contains executable code.
[2871.12 --> 2873.90] That shouldn't be how things work.
[2874.58 --> 2877.46] So it could be that this is just an artifact of that.
[2878.48 --> 2888.82] But because it's also a virtual machine, maybe there's something happening that we don't understand and we are actually executing code that is on the stack.
[2888.82 --> 2897.78] It seems unlikely, but you know, it's one of those things where I'm not an expert on the Erlang VM, so I don't know for sure.
[2898.42 --> 2898.48] Yeah.
[2898.64 --> 2905.52] But like my intuition says that this shouldn't be possible just from like the way that processes work.
[2905.74 --> 2906.28] Right, right.
[2906.72 --> 2907.02] Okay.
[2907.50 --> 2910.90] So this is like the Erlang runtime itself, right?
[2910.90 --> 2913.34] How it executes code on the kernel.
[2913.78 --> 2915.20] That's what we would need to know.
[2915.20 --> 2920.48] So I think that we have a person that we can ask, which is Lucas Larson.
[2921.36 --> 2934.54] So that is, even though he's very busy, I know, and he's focused like deep down on like some very gnarly problems in the world of Erlang, we can, you know, ask him.
[2934.74 --> 2940.32] And if you're interested to follow what happens, I mean, this is like pull request 396 is what started this.
[2940.32 --> 2946.22] I intend to keep, right, as many details as I can here and all the follow-ups.
[2946.74 --> 2953.10] So yeah, this is a place to go, I suppose, to see what else has happened since this was recorded.
[2953.88 --> 2957.24] So what I'd like to say is thank you very much, Frederick.
[2957.38 --> 2957.66] My pleasure.
[2957.78 --> 2959.34] For running us through Parca.
[2959.34 --> 2988.20] What we want to do is, first of all, fix this R.
[2988.20 --> 2994.76] Damn it, someone can't type infrastructure as if my life depended on it.
[2995.66 --> 2996.26] Right.
[2996.66 --> 3009.98] So we want in 2022 for the changelog.com setup to use cross-plane to provision our Linode Kubernetes cluster.
[3009.98 --> 3010.82] That's the goal.
[3011.32 --> 3024.18] And the way we're thinking of achieving it is to follow this guide to generate a Linode cross-plane provider using the TerraJet tool, which is part of the cross-plane ecosystem.
[3024.58 --> 3028.10] And we can generate any cross-plane provider from any Terraform provider.
[3028.34 --> 3028.54] Cool.
[3028.84 --> 3030.02] So how are we going to do that?
[3030.44 --> 3034.20] Yeah, I think, well, you know, there's a couple different parts here.
[3034.20 --> 3043.08] In order to be able to test out anything that we generate, we're going to need a cross-plane control plane running somewhere.
[3043.08 --> 3054.10] That being said, right, we need to generate and package up this provider to be able to install it in cross-plane and go through our package manager there.
[3054.74 --> 3059.48] But it could be as simple as even just having a local kind cluster to start out.
[3060.04 --> 3066.02] And, you know, after generating, using Go Run to just apply some CRDs and see if it picks them up correctly.
[3066.02 --> 3067.58] That is a good idea.
[3067.98 --> 3068.58] I like it.
[3068.92 --> 3073.04] But I have found issues when I went from kind to something else.
[3073.88 --> 3083.42] GKE, LKE, any like real cluster, because they have, there's different things like RBAC, for example, or different security policies or who knows what.
[3083.66 --> 3089.34] So I like starting with like production, which is a bit weird because you would think like you start from development.
[3089.48 --> 3090.84] But I like starting with production.
[3090.84 --> 3097.68] What I'm thinking is I want to start with cross-plane installed in the production setup.
[3098.12 --> 3106.90] And I can't remember this was episode 16 or 17, where I was saying that if there was a cross-plane 15, there you go.
[3107.22 --> 3110.14] Gerhard has an idea for the changelog 22 setup.