text stringlengths 0 1.8k |
|---|
**Gerhard Lazu:** I don't think that's going to work. |
**Jerod Santo:** Why not? |
**Gerhard Lazu:** I guess the versions have changed. I never even tried—I think by default PostgreSQL will be version 13, or maybe even 14 if it's out yet. I don't know whether things will work with that. |
**Jerod Santo:** Oh, it does. I’m running it. |
**Gerhard Lazu:** Are you? Okay. |
**Adam Stacoviak:** And the readme is a little off, too. |
**Gerhard Lazu:** The readme is off. Yes. |
**Adam Stacoviak:** ...in terms of what it prescribes. It just said dependencies are Elixir and Erlang; it doesn't say which Postgres, and everything else. |
**Jerod Santo:** \[48:16\] Just wait for the transcript to come out, of this episode, and then follow that. I'm telling you, brew install Elixir, brew install Postgres, clone the repo... |
**Gerhard Lazu:** Okay. So first step-- |
**Jerod Santo:** `mix deps.get` |
**Gerhard Lazu:** ...Gerhard gets a new MacBook M1 for Christmas. \[laughter\] |
**Jerod Santo:** I already got one, Gerhard. I can do this work. |
**Gerhard Lazu:** Alright. Just post it to me. \[laughter\] |
**Jerod Santo:** Well, unfortunately, with the ship dates on these new MacBooks, I also don't think that's a short-term solution either. |
**Gerhard Lazu:** I know. 4-6 weeks. I've seen that. Yes, I know what you mean. |
**Adam Stacoviak:** You had to order it like a month ago to get it on time for Christmas. |
**Gerhard Lazu:** Yes, I know. |
**Jerod Santo:** Alright, so the short-term solution is keep your old machine around, and use that till we have a medium-term solution. |
**Gerhard Lazu:** Exactly. Yes. |
**Adam Stacoviak:** Which I do. It's right next to me. It's no problem to use it. But, like anybody, I want to get set up on this new machine and never look back to the old, and just format the drive and roll on. |
**Break:** \[49:15\] |
**Jerod Santo:** Last Kaizen we talked about moving our uploads to the cloud, specifically S3 is cloud. I wanted to give a quick update on progress there. I wanted to have it done by the time we recorded this, and the fact that Gerhard, you and I met (was it last week?) to discuss a game plan to getting us from where w... |
**Gerhard Lazu:** I did a few as well, so it's okay. Your yak shave held yak shaves. It's all good. |
**Jerod Santo:** \[laughs\] So... You know, I only have so much time to work on the platform, and I have to use that time wisely, and sometimes it's GitHub issues-based development when things come in, because then you know it’s a user or a listener or a reader’s need, or something that they hit up against. So I end up... |
**Gerhard Lazu:** I think it was like 90%. |
**Jerod Santo:** 90? |
**Gerhard Lazu:** Yes, 90% is what I remember. |
**Jerod Santo:** Yeah. So probably I'm at like 94% now... And then here comes an issue, issue number 393 hit our GitHub issues, which we'll link up... Newsletter links proxy encodes special URLs with HTML instead of percent based. This is a tiny little bug that was just interesting to me. |
\[51:59\] So what happened is, in our Changelog weekly newsletter, which goes out every Sunday morning, it includes all the shows from that week, every episode we put out, as well as all the news and the links and the repos and the commentary for the week, we linked to Chris Manson's post called It's All Gravy. And his... |
But what happened with that apostrophe is the way that we encode that creates the HTML encoding instead of percent-based, which you'd expect in the URL, which caused people that clicked on that link in our newsletter to go to a web page, which was a 404, because it was incorrect. |
Now, certain browsers actually manage it okay, and the apostrophe looks fine in the address bar and everything, which I thought was kind of interesting. And so I thought, "Here's a bug I should chase down, while not working on these uploads to the cloud branch that I'm supposed to be working on..." And so I started to ... |
So I dive into our codebase and I find the line of code in question, and everything looks legit to me, and then I realize, okay, I'm calling this Phoenix... So we are an Elixir/Phoenix application, for those who haven't been following along the whole time... And at a certain point, we call into Phoenix. And Phoenix has... |
So I started digging a little deeper, and I started thinking, it's like, "Whatever is happening is outside of my domain, right? It's a dependency that's doing it." So I don't know, Gerhard... What do you do in this circumstance? You’ve got a dependency that's not doing something totally right? What's your first move? I... |
**Gerhard Lazu:** No, not really. Not really. |
**Jerod Santo:** Okay, good. |
**Gerhard Lazu:** So I would look at an issue to see if there is an issue in the repo for the DEP. I would try and find the code, see what happened around it. Like, I would call a blame, see if that is different... And if I can't find anything, I would just open an issue on that repo, explain my problem, link to my cod... |
**Jerod Santo:** Yeah, exactly. |
**Gerhard Lazu:** "What’s the problem here?" |
**Jerod Santo:** Yeah. So the interesting thing about this one is I'm not really savvy with these character encodings, and I'm not sure why it's doing the HTML encoding versus the URL encoding, but my first question is, like, is this even a bug? Or is this just like the way it would work if you pass it an apostrophe? |
And when I start to have these questions - you laid out a very clear path to potential victory, but I'm lazier than you, so my first thing is like, "Am I running the latest version?" That's just what I ask myself. Like, maybe this was fixed between my version and now. So my first step is, "Well, let's just upgrade stuf... |
**Gerhard Lazu:** \[56:11\] Update everything. Oh, my goodness me. Okay... What can possibly go wrong...? \[laughs\] |
**Jerod Santo:** Exactly. So we're on Phoenix 1.5, and 1.6 was out. Most Elixir packages do a pretty good job of following semantic versioning. So I knew this was a minor upgrade, so there are some breaking changes, but -- or no, a major upgrade breaks changes. There shouldn't have been any API changes, right? Yeah... ... |
So I did all those, ran the tests, everything was fine. Then I went to upgrade Phoenix, which was a minor version upgrade from 1.5 to 1.6. Got that done. While it was kind of doing its thing, I was like, "Well, I'm going to go read the changelog and see what's going on." And I did notice that they made a breaking chang... |
So what did they change? Well, the way Phoenix works as it passes the request data from your controllers down into your views and to be used in the template, there's this bag of data called assigns, and in the assigns, there’s a bunch of -- it’s literally a map, or a struct, or a dictionary, or a hash, depending on wha... |
So I did find those. There were two places I was using those, and I changed them. And there was a new way of doing it. Fine. And I upgrade, and all my tests pass, and so what do I do? I ship it, baby. I send it out there, and it's all good. And then I start to realize, via Twitter, that our Twitter embed’s broken. It's... |
**Gerhard Lazu:** Wow... |
**Jerod Santo:** ...which led to Twitter embeds breaking, all third-party integrations that are based on the meta elements in your HTML - busted. That led to me refactoring our entire meta module, because that data is gone, and the entire thing in that module is like, "Which view am I, and which template am I? Okay, he... |
**Gerhard Lazu:** Shaven. |
**Jerod Santo:** I shaved it. I shaved that sucker. But I did not get our cloud uploads done... So that's my excuse, and I'm sticking with it. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.