❌ build issues: github.com/nicklockwood/SwiftFormat=0.53.0

[github-actions]

Running log of build failure for github.com/nicklockwood/SwiftFormat=0.53.0

[github-actions]

Build failure

github.com/nicklockwood/SwiftFormat=0.53.0

logs: https://github.com/pkgxdev/pantry/actions/runs/7452299004

[github-actions]

Build failure

github.com/nicklockwood/SwiftFormat=0.53.0

logs: https://github.com/pkgxdev/pantry/actions/runs/7452299004

[jhheider]

@mxcl both xcbeautify and SwiftFormat have developed the same fault:

+ swift build --configuration release
TSCUtility/Triple.swift:215: Fatal error: Failed to parse target info (malformed).
Raw compiler output: 
/Users/builder/actions-runner/_work/pantry/pantry/builds/github.com∕nicklockwood∕SwiftFormat-0.53.0.sh: line 29: 11964 Trace/BPT trap: 5       swift build --configuration release

looks like that error is thrown from https://github.com/apple/swift-tools-support-core/blob/990afca47e75cce136d2f59e464577e68a164035/Sources/TSCUtility/Triple.swift#L196-L231

that's a deep dep. weirdly, jq thinks the JSON is just fine:

$ swift -print-target-info | jq .
{
  "compilerVersion": "Apple Swift version 5.8 (swiftlang-5.8.0.124.2 clang-1403.0.22.11.100)",
  "target": {
    "triple": "arm64-apple-macosx14.0",
    "unversionedTriple": "arm64-apple-macosx",
    "moduleTriple": "arm64-apple-macos",
    "compatibilityLibraries": [],
    "librariesRequireRPath": false
  },
  "paths": {
    "runtimeLibraryPaths": [
      "/Applications/Xcode-14.3.0.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/macosx",
      "/usr/lib/swift"
    ],
    "runtimeLibraryImportPaths": [
      "/Applications/Xcode-14.3.0.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/macosx"
    ],
    "runtimeResourcePath": "/Applications/Xcode-14.3.0.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift"
  }
}

soooooooo... we could try injecting a specific version in Package.resolved, but that feels super wrong, especially since it's not a direct dependency. even de-patching xcbeautify to its last used Package.resolved doesn't fix it.

this might be an instance where SPM prevents everything from building until some middle dependency gets updated. thoughts on jumping through extreme hoops for this?

[jhheider]

Interestingly, that doesn't seem to be coming in from the package (somehow), and seems to be deprecated code, and if you run the commands by hand you don't get those issues. So, something about running it in our env is messing it up. Unsetting MACOSX_DEPLOYMENT_TARGET doesn't seem to fix it, but this is extremely weird. Digging in deeper.

[jhheider]

ok, this fixes it:

    - export TMPDIR=$(mktemp -d)

so, it's not liking, apparently, the extended unicode characters in the TMPDIR envvar. slightly gross. but an easy fix.