roderik

2024-04-15T19:25:31.088735Z ERROR create_virtual_branch: crates/gitbutler-tauri/src/virtual_branches.rs:87: error=Error(failed to set ownership

Caused by:
    inconsistent ownership claims) project_id=b62e0f66-0449-453b-8316-8a2d260176ca branch=BranchCreateRequest { name: None, ownership: Some(BranchOwnershipClaims { claims: [OwnershipClaim { file_path: "charts/settlemint/charts/observability/dashboards/besu.json", hunks: [Hunk { hash: Some("943c9ab701f6afa1dfceed3b021bdc82"), timestamp_ms: None, start: 20, end: 27 }, Hunk { hash: Some("aab8edce6a4e64c51cdd6b1488b0d9d6"), timestamp_ms: None, start: 437, end: 444 }, Hunk { hash: Some("87579ecb9fe745dfa9fb37351c81041f"), timestamp_ms: None, start: 451, end: 458 }, Hunk { hash: Some("41e2e1d0ba00c845155db7fb183fa429"), timestamp_ms: None, start: 463, end: 470 }, Hunk { hash: Some("e1d304af1f73d58077a0424a54a0a17b"), timestamp_ms: None, start: 475, end: 482 }, Hunk { hash: Some("0b98836117d5615ead47d9ea11e456cd"), timestamp_ms: No

roderik

#!/bin/bash

## Configure all the nx, jest and tx config files for the libraries.
## The only thing you need to make sure of is to set the name correct in the package.json file

jq '.compilerOptions.paths = {}' tsconfig.base.json > temp.json && mv temp.json tsconfig.base.json

find ./libs -name "package.json" | while read pkg; do
    pkg_name=$(jq -r '.name' "$pkg")
    pkg_dir=$(dirname "$pkg")

roderik

        "@typescript-eslint/consistent-type-imports": [
          "warn",
          {
            "prefer": "type-imports",
            "fixStyle": "separate-type-imports"
          }
        ]

roderik

---
apiVersion: troubleshoot.sh/v1beta2
kind: Preflight
metadata:
  name: settlemint
spec:
  analyzers:
    - clusterVersion:
        outcomes:
          - fail:

roderik

Keybase proof

I hereby claim:

• I am roderik on github.
• I am roderik (https://keybase.io/roderik) on keybase.
• I have a public key ASC9nkZpcMl7mcpWU0m2T3_9ymHi0ySEJRkzExeqdZmjuQo

To claim this, I am signing this object:

roderik

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: faster
provisioner: kubernetes.io/gce-pd
parameters:
  type: pd-ssd

roderik

pragma solidity ^0.4.25;
// File: @settlemint/solidity-mint/contracts/authentication/interfaces/IRoleRegistry.sol
/**
 * Copyright (C) SettleMint NV - All Rights Reserved
 *
 * Use of this file is strictly prohibited without an active license agreement.
 * Distribution of this file, via any medium, is strictly prohibited.
 *
 * For license inquiries, contact hello@settlemint.com
 */

roderik

pragma solidity ^0.4.15;


contract Migrations {
  address public owner;
  uint public last_completed_migration;

  modifier restricted() {
    require(msg.sender == owner);
    _;

roderik

module Fastlane
  module Actions
    class AppNameAction < Action
      def self.run(params)
        require 'plist'
        identifier_key = 'CFBundleDisplayName'
        folder = Dir['*.xcodeproj'].first
        info_plist_path = params[:plist_path]
        raise "Couldn't find info plist file at path '#{params[:plist_path]}'".red unless File.exist?(info_plist_path)
        plist = Plist.parse_xml(info_plist_path)

roderik

Hey Dan,

glad you like the Kunstmaan Bundles CMS! We put a lot of hard work in it and are always glad if people discover and use it. If your website goes online, please submit it for the showcase gallery.

Now in regards to the translations on page level you mentioned, this was actually an explicit design decision. We've been building loads of sites in a multilingual environment (NL/FR/DE/EN are the most common but recently we also launced a chinese translation for a site) and more often than not does the content of a page (apart from the literal translation) differs between languages. The message is often targetted differently to different languages.

It's a lot easier to do this with page level translations than pagepart level translations. It also makes it possible to do user-understandable versioning, what page with what content was online at that point in time.

As you mentioned you can indeed solve a lot by just creating custom pageparts. Apart from this we al