Datasets:
willtheorangeguy
/
2022-Go-Time-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
2.35k
[2708.48 --> 2709.78] It probably is doing something.
[2710.28 --> 2713.56] And if it isn't, maybe it should be like in your case, Chris.
[2713.80 --> 2714.08] Yeah.
[2714.72 --> 2715.36] Spoopy.
[2715.78 --> 2716.92] The zombie apocalypse.
[2717.30 --> 2717.56] Yeah.
[2718.94 --> 2720.62] Will be caused by Istio.
[2722.84 --> 2725.82] Zombie code just haunting us.
[2726.18 --> 2728.04] I'm never sure what's worse than those things.
[2728.04 --> 2733.52] Like the insecure environment where we're just like nothing applies or the extremely secure environment.
[2733.74 --> 2736.72] I've seen some where they've been really locked down and like everything.
[2736.88 --> 2741.02] You've got an IP firewall for everything and you're like, I have total confidence.
[2741.62 --> 2744.54] And then mysteriously API calls between machines just didn't work.
[2744.80 --> 2746.54] We're just like, why not?
[2746.98 --> 2750.30] And what we realized, the debugging for this went wild.
[2750.38 --> 2751.16] It went really low.
[2751.60 --> 2755.40] And we were down at Wireshark and we're watching what's going on and we're watching what's going on inside the kernel.
[2755.40 --> 2759.66] But we were turning on contract connection tracking.
[2760.00 --> 2760.96] And this is in TCP.
[2761.28 --> 2766.80] It's got little tables, state tables and network there to keep track of the sort of TCP connections.
[2766.94 --> 2768.14] But you can overflow these tables.
[2768.28 --> 2769.32] We were turning them on and off.
[2769.76 --> 2775.78] And every time we turned them on and off, we were toggling which IP firewall rules were actually matching or not.
[2776.12 --> 2781.10] So we were taking existing connections and then just randomly dropping them every time we flipped these things.
[2781.42 --> 2782.66] But we could never observe it.
[2782.66 --> 2785.74] And we were just there the whole time just going, we lost it again.
[2786.04 --> 2786.92] There goes the connection.
[2787.44 --> 2791.24] And it took us weeks of just poking around going, what's going on?
[2791.74 --> 2792.44] Can't see it.
[2792.62 --> 2793.40] Ghost in the machine.
[2794.84 --> 2795.24] Wow.
[2796.00 --> 2797.20] Yeah, too secure is a problem.
[2798.26 --> 2798.66] Honestly.
[2799.12 --> 2801.42] Well, in that spirit, D, what's your pin number?
[2802.80 --> 2804.28] Just give us three of the numbers.
[2805.32 --> 2806.38] Let's play Mastermind.
[2806.96 --> 2808.76] Is this like, what's it, Spaceballs?
[2808.98 --> 2809.88] One, two, three, four?
[2810.34 --> 2810.58] Yeah.
[2811.44 --> 2813.06] No one's going to suspect that, I think.
[2813.54 --> 2814.78] No one's going to try that, are they?
[2815.20 --> 2816.54] Zero, zero, zero, zero.
[2816.92 --> 2817.80] Does it allow you?
[2817.88 --> 2819.58] I don't think systems allow you to do that.
[2819.80 --> 2820.08] Why?
[2820.72 --> 2821.00] I don't know.
[2821.06 --> 2822.28] I'm going to try and change my pin now.
[2822.34 --> 2822.46] Yeah.
[2823.04 --> 2823.38] You might.
[2823.38 --> 2825.52] Oh, yeah.
[2825.62 --> 2826.10] I don't know.
[2826.46 --> 2826.70] Maybe.
[2826.90 --> 2827.60] Because it's too easy.
[2828.24 --> 2828.74] I don't know.
[2829.92 --> 2834.96] Any other horror stories before we throw a, what do you put on fire?
[2835.06 --> 2835.42] Water?
[2835.78 --> 2836.60] Don't do that, do you?
[2836.66 --> 2838.10] Just let it die out on its own?
[2838.26 --> 2839.24] No, we've got to be responsible.
[2839.76 --> 2841.46] How are we going to sort this fire out?
[2841.92 --> 2843.78] By throwing water and the electrical equipment?
[2845.72 --> 2846.48] Use foam.
[2846.72 --> 2847.28] We'll use foam.
[2847.36 --> 2847.70] Turn it off.
[2847.72 --> 2848.60] We'll close slack.
[2848.60 --> 2849.32] What's on fire?
[2849.50 --> 2849.64] Yeah.
[2849.80 --> 2851.96] Close slack, and then the fire will die down.
[2851.96 --> 2856.06] So before we put the fire out, has anyone got any other final horror stories?
[2856.70 --> 2859.18] Well, you know, if you're mine, anyone you want to hear?
[2859.60 --> 2861.14] Well, what do you mean in real life?
[2863.06 --> 2867.18] I wrote one down, which actually I wrote in advance about doing a sequel statement and
[2867.18 --> 2874.08] accidentally double putting in the semicolon after the from table, so an update.
[2874.58 --> 2878.50] So the where statement didn't apply, and that was to a production system.
[2878.92 --> 2881.86] Oh, so what's the effect of that then?
[2881.86 --> 2886.38] So normally you would be updating something and specifying the where, which will limit
[2886.38 --> 2887.92] what gets changed, right?
[2888.32 --> 2889.06] Yeah, exactly.
[2889.38 --> 2892.48] I tweeted this when you actually asked about it, and I think no one really appreciated
[2892.48 --> 2896.00] what it does and how it happened.
[2896.16 --> 2897.46] But I executed a query.
[2897.60 --> 2902.22] I was just tidying up some debt that was left over, and it should have been really trivial.
[2902.22 --> 2905.68] And I practiced it, and then I copy and pasted it into the console.
[2905.84 --> 2910.78] But after I copied and pasted the first one, for whatever reason, I fingered a semicolon
[2910.78 --> 2912.78] and then put in the where line.
[2912.92 --> 2914.20] But that makes it two commands.
[2914.50 --> 2918.58] So it successfully did the update column set value equals on table.
[2919.06 --> 2920.46] And it didn't apply the where.
[2920.62 --> 2923.62] So it updated, I think it was like 90 million rows or something.
[2923.90 --> 2924.68] Oh, God.
[2924.68 --> 2927.08] And the machine was very fast.
[2927.84 --> 2929.70] Faster than I was at finding Control Z.
[2929.96 --> 2930.90] Oh, no.
[2931.48 --> 2934.94] And that's why you work inside of transaction blocks, kids.
[2936.22 --> 2940.36] That's why that's advisable, but was not what I was doing that day.
[2940.36 --> 2946.20] The real mess there is actually sort of going, how can we restore this when our database backup
[2946.20 --> 2950.84] was like 12 hours ago, and there's 12 hours of changes in other tables since then?
[2951.16 --> 2951.26] Ouch.
[2951.68 --> 2953.34] So you're not going to sort of do anything there.
[2953.44 --> 2959.06] So it's a pull the old sort of thing and extract that table and then go and update all the necessary