Skip to main content

GitHub: view commits that include images

One of the cool features in GitHub is the way it allows you to compare images. Image your designer created a first version of your new company logo and later he does some small changes. How can you easily detect what’s changed? 

GitHub gives you four easy ways to view changes between image versions: 2-up, Swipe, Onion Skin, and Difference.

Let’s have a look at how this works:

  • Open your GitHub repository
  • Go to Commits

image

  • Click on the Commit that contains the image change.

image

  • Now you see the different images next to each other. This is the default 2-up view which lets you get a quick glimpse of both images. In addition, if the image has changed size between versions, the actual dimension change will be displayed. (Hmm, I’m wondering what the designer has changed… Knipogende emoticon)

image

  • Let’s click on Swipe to switch to another view. This lets you view portions of your image side by side. By dragging the swipe slider you can see the old version transform to the new version.

image

  • Next one is Onion Skin. It allows you to drag an opacity slider back to see how things have changed.

image

  • The last option is Difference. You have no clue what’s changed? Difference will highlight only pixels that are different between the two images, making it the go-to view mode for finding those single pixel changes in a file.

image

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

The role of ActivitySource in OpenTelemetry for .NET

While doing some pair programming to integrate OpenTelemetry tracing to a .NET application, we had a discussion on how to use the ActivitySource . It looks simple. You new one up, give it a name, start an activity, done. The discussion started when we added a second ActivitySource with the exact same name in a different class. This made us wonder: "Are we duplicating traces now? Is this a memory leak? Do we need a singleton?" So we decided to dig deeper. This post is what we learned… What ActivitySource actually is ActivitySource is part of System.Diagnostics , not part of the OpenTelemetry NuGet packages. Microsoft built tracing primitives directly into the BCL, and OpenTelemetry's .NET SDK simply listens to them. This is why you can add distributed tracing to a library without taking a dependency on OpenTelemetry at all. An ActivitySource is a factory for Activity objects, and an Activity is .NET's name for what OpenTelemetry calls a span.(don’t ask m...
Read more