Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dangerfile cannot be compiled when using Xcode 16 #615

Closed
AndrewVebster opened this issue Aug 6, 2024 · 36 comments
Closed

Dangerfile cannot be compiled when using Xcode 16 #615

AndrewVebster opened this issue Aug 6, 2024 · 36 comments

Comments

@AndrewVebster
Copy link

Hi 👋

When running danger-swift on a device with Xcode 16 the command fails with this error:

  7 | let danger = Danger()
    |              `- error: cannot call value of non-function type 'module<Danger>'

Running locally and on Bitrise - the error is the same.
Using this command:
swift run danger-swift local --cwd ../../
or this on CI
swift run danger-swift ci --no-publish-check -f --cwd ../../

I believe my setup is pretty standard:

  • Danger installed via SPM without any additional plugins
  • Simple Dangerfile - I removed everything a left only this 👇
import Danger
import Foundation

let danger = Danger()

⚠️ The same setup works fine with Xcode 15.

Environment

  • Xcode 16.0 beta 4 (16A5211f)
  • Running locally on macOS 15.0 Beta (24A5298h)
  • or running on Bitrise CI, the error is the same

Other Info

My assumption is that import Danger doesn't work as expected. Because compiler doesn't see other types and functions. For example, fail function:

19 |         fail(message: "Message", file: $0, line: 2)
    |         `- error: cannot find 'fail' in scope

Or DangerDSL.

I tried installing danger-swift from brew instead of SMP when running on CI but the result is the same.


Full command & result
swift run danger-swift local --cwd ../../ 
Building for debugging...
[1/1] Write swift-version-39B54973F684ADAB.txt
Build of product 'danger-swift' complete! (0.34s)
(node:51429) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
/var/folders/gj/tj6dnp8d1s71sp3sj5tlkh000000gn/T/danger/B52A4EC1-CE42-45E0-955E-3E50FB477100/_tmp_dangerfile.swift:7:14: error: cannot call value of non-function type 'module<Danger>'
  5 | import Foundation
  6 | 
  7 | let danger = Danger()
    |              `- error: cannot call value of non-function type 'module<Danger>'
  8 | 
  9 | 

ERROR: Dangerfile eval failed at Dangerfile.swift
ERROR: Could not get the results JSON file at /var/folders/gj/tj6dnp8d1s71sp3sj5tlkh000000gn/T/danger/B52A4EC1-CE42-45E0-955E-3E50FB477100/danger-response.json

Danger: ⅹ Failing the build, there is 1 fail.
## Failures
`danger-swift` failed.
## Markdowns
### Log


/var/folders/gj/tj6dnp8d1s71sp3sj5tlkh000000gn/T/danger/B52A4EC1-CE42-45E0-955E-3E50FB477100/_tmp_dangerfile.swift:7:14: error: cannot call value of non-function type 'module<Danger>'
  5 | import Foundation
  6 | 
  7 | let danger = Danger()
    |              `- error: cannot call value of non-function type 'module<Danger>'
  8 | 
  9 | 
ERROR: Dangerfile eval failed at Dangerfile.swift
ERROR: Could not get the results JSON file at /var/folders/gj/tj6dnp8d1s71sp3sj5tlkh000000gn/T/danger/B52A4EC1-CE42-45E0-955E-3E50FB477100/danger-response.json

My Package.swift
// swift-tools-version: 5.9
// The swift-tools-version declares the minimum version of Swift required to build this package.

import PackageDescription

let package = Package(
    name: "DangerDependencies",
    products: [
        .library(
            name: "DangerDeps",
            type: .dynamic,
            targets: ["DangerDependencies"]),
    ],
    dependencies: [
        .package(url: "https://github.com/danger/swift.git", from: "3.18.1"),
    ],
    targets: [
        .target(
            name: "DangerDependencies",
            dependencies: [
                .product(name: "Danger", package: "swift")
            ]
        ),
    ]
)

My Dangerfile.swift
import Danger
import Foundation

let danger = Danger()
@radude89
Copy link

radude89 commented Sep 4, 2024

I could reproduce the problem with Xcode 16 beta 6 (16A5230g). Do we have any updates about this issue or a possible workaround? Thank you!

@marcomasser
Copy link

I just ran into this issue with Xcode 16.0 RC 1 (16A242). Is there any update on this?

@oronbz
Copy link

oronbz commented Sep 12, 2024

Same here with RC

@f-meloni
Copy link
Member

let danger = Danger()
    |              `- error: cannot call value of non-function type 'module<Danger>'

Is it possible that it thinks you are referring to the Danger module and not the Danger function?
Would Danger.Danger() work?

@marcomasser
Copy link

Unfortunately, this doesn’t solve the issue:

$ swift run danger-swift pr https://github.com/…
Building for debugging...
[1/1] Write swift-version--6E9C300FE98E0E3E.txt
Build of product 'danger-swift' complete! (0.34s)
Starting Danger PR on …
/var/folders/vk/v4gx2v6x4972w9v5r1xggx000000gn/T/_tmp_dangerfile.swift:13:14: error: module 'Danger' has no member named 'Danger'
 11 | import Danger
 12 | 
 13 | let danger = Danger.Danger()
    |              `- error: module 'Danger' has no member named 'Danger'
 14 | let pullRequest = danger.github.pullRequest
 15 | let git = danger.git

@CreativeSpaghetti
Copy link

CreativeSpaghetti commented Sep 17, 2024

This might help. Got it working locally.
Assuming you're workng on MacOS, have XCode 16 installed and danger-swift via brew

# Clone danger/swift repo into temp directory
mkdir mydanger
cd mydanger
git clone https://github.com/danger/swift.git
cd swift

# build with your current SDK in your current XCode (ie XCode 16)
swift build --configuration release --sdk /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX15.0.sdk

# Copy to replace files in your old brew setup
sudo cp .build/arm64-apple-macosx/release/danger-swift /opt/homebrew/opt/danger-swift/bin/danger-swift
sudo cp .build/arm64-apple-macosx/release/Modules/Danger.swiftmodule /opt/homebrew/lib/danger/Danger.swiftmodule
sudo cp .build/arm64-apple-macosx/release/Modules/DangerShellExecutor.swiftmodule /opt/homebrew/lib/danger/DangerShellExecutor.swiftmodule
sudo cp .build/arm64-apple-macosx/release/Modules/Logger.swiftmodule /opt/homebrew/lib/danger/Logger.swiftmodule
sudo cp .build/arm64-apple-macosx/release/Modules/OctoKit.swiftmodule /opt/homebrew/lib/danger/OctoKit.swiftmodule
sudo cp .build/arm64-apple-macosx/release/Modules/RequestKit.swiftmodule /opt/homebrew/lib/danger/RequestKit.swiftmodule

# cleanup
cd ../..
rm -fr mydanger

# run danger-swift
danger-swift local --text-only --verbose

@marcomasser
Copy link

That’s interesting! So if re-building Danger Swift using Xcode 16 fixes the issue, I guess a new release of Danger that was built using Xcode 16 could resolve this?

@CreativeSpaghetti
Copy link

That’s interesting! So if re-building Danger Swift using Xcode 16 fixes the issue, I guess a new release of Danger that was built using Xcode 16 could resolve this?

Nope, just tested it with 3.19.1, not working for me. So still need to stick to that workaround so far.

@marcomasser
Copy link

That’s interesting! So if re-building Danger Swift using Xcode 16 fixes the issue, I guess a new release of Danger that was built using Xcode 16 could resolve this?

Nope, just tested it with 3.19.1, not working for me. So still need to stick to that workaround so far.

3.19.1 also doesn’t work for me but I also don’t know what version of Xcode was used to build that.

@f-meloni
Copy link
Member

f-meloni commented Sep 18, 2024

Danger is built in your machine. When you install it via brew it runs the install script in your machine.
It uses the Xcode you selected with xcode-select to build.
Same for SPM, it builds Danger and runs it in your machine with the selected Xcode.

@marcomasser
Copy link

Ah right, thanks for the clarification! But that just makes it more interesting that what @CreativeSpaghetti posted works for them 🤔

@f-meloni
Copy link
Member

Indeed, it that is the fix, then Danger should work if you force a brew install and have Xcode 16 selected 🤔

@marcomasser
Copy link

Unfortunately, that does not seem to change anything 😞

> xcode-select -p
/Applications/Xcode-16.0.app/Contents/Developer
> brew reinstall danger/tap/danger-swift
==> Fetching danger/tap/danger-swift
==> Downloading https://github.com/danger/danger-swift/archive/3.19.1.tar.gz
Already downloaded: /Users/marco/Library/Caches/Homebrew/downloads/313490d738c01aae624c4dda88a017dcebd16c6123b27f341b593be2c01206e9--swift-3.19.1.tar.gz
==> Reinstalling danger/tap/danger-swift 
==> make install PREFIX=/opt/homebrew/Cellar/danger-swift/3.19.1
🍺  /opt/homebrew/Cellar/danger-swift/3.19.1: 8 files, 3.9MB, built in 31 seconds
==> Running `brew cleanup danger-swift`...
> swift run danger-swift pr https://github.com/…
[…]
Build of product 'danger-swift' complete! (5.86s)
Starting Danger PR on …
/var/folders/vk/v4gx2v6x4972w9v5r1xggx000000gn/T/_tmp_dangerfile.swift:13:14: error: cannot call value of non-function type 'module<Danger>'
 11 | import Danger
 12 | 
 13 | let danger = Danger()
    |              `- error: cannot call value of non-function type 'module<Danger>'
 14 | let pullRequest = danger.github.pullRequest
 15 | let git = danger.git
[…]

@CreativeSpaghetti
Copy link

CreativeSpaghetti commented Sep 18, 2024

Unfortunately, that does not seem to change anything 😞

> xcode-select -p
/Applications/Xcode-16.0.app/Contents/Developer
> brew reinstall danger/tap/danger-swift
==> Fetching danger/tap/danger-swift
==> Downloading https://github.com/danger/danger-swift/archive/3.19.1.tar.gz
Already downloaded: /Users/marco/Library/Caches/Homebrew/downloads/313490d738c01aae624c4dda88a017dcebd16c6123b27f341b593be2c01206e9--swift-3.19.1.tar.gz
==> Reinstalling danger/tap/danger-swift 
==> make install PREFIX=/opt/homebrew/Cellar/danger-swift/3.19.1
🍺  /opt/homebrew/Cellar/danger-swift/3.19.1: 8 files, 3.9MB, built in 31 seconds
==> Running `brew cleanup danger-swift`...
> swift run danger-swift pr https://github.com/…
[…]
Build of product 'danger-swift' complete! (5.86s)
Starting Danger PR on …
/var/folders/vk/v4gx2v6x4972w9v5r1xggx000000gn/T/_tmp_dangerfile.swift:13:14: error: cannot call value of non-function type 'module<Danger>'
 11 | import Danger
 12 | 
 13 | let danger = Danger()
    |              `- error: cannot call value of non-function type 'module<Danger>'
 14 | let pullRequest = danger.github.pullRequest
 15 | let git = danger.git
[…]

tried that brew reinstall danger-swift too, with Xcode 16 installed and selected, it did not help. Still needed to make a clean build and then replace the binaries.

@skydivedan
Copy link

Don't know if this helps, but I'm using Danger in CircleCI. I specify 3.19.1 in the Package.swift file. Xcode 16 is the only Xcode that is installed. I get a long list of errors. One of them looks like this:

/Users/distiller/project/DangerDeps/.build/debug/SwiftFormat-tool.build/module.modulemap:1:8: error: redefinition of module 'SwiftFormat'
1 | module SwiftFormat {
  |        `- error: redefinition of module 'SwiftFormat'
2 |     header "/Users/distiller/project/DangerDeps/.build/arm64-apple-macosx/debug/SwiftFormat-tool.build/SwiftFormat-Swift.h"
3 |     requires objc

Anyway, just wanted to give some more details. Hope this helps.

@Ph1Doc
Copy link

Ph1Doc commented Sep 21, 2024

The same problem with Dangerfile

/_tmp_dangerfile.swift:3:22: error: cannot call value of non-function type 'module<Danger>'
▸ 1 | import Danger
▸ 2 |
▸ 3 | private let danger = Danger()
▸ |                      `- error: cannot call value of non-function type 'module<Danger>'
▸ 4 |

@jwelton
Copy link

jwelton commented Sep 24, 2024

I'm facing the same issue. Did anyone find a solution for this? I'm using SPM.

The same problem with Dangerfile

/_tmp_dangerfile.swift:3:22: error: cannot call value of non-function type 'module<Danger>'
▸ 1 | import Danger
▸ 2 |
▸ 3 | private let danger = Danger()
▸ |                      `- error: cannot call value of non-function type 'module<Danger>'
▸ 4 |

@Arafo
Copy link

Arafo commented Sep 27, 2024

There seems to be a name conflict between the target Danger and the function Danger()

// swiftlint:disable:next identifier_name
public func Danger() -> DangerDSL {
DangerRunner.shared.dsl
}

I guess that's why the error says cannot call value of non-function type 'module'.

Not sure why this is happening now with Xcode 16 / Swift 6 but I got it working renaming the function Danger() to Danger1() 🙃
Arafo@c075cdc

Renaming the target should work as well

@marcomasser
Copy link

marcomasser commented Sep 27, 2024

Thanks for the hint! I forked Danger and renamed all occurrences of the Danger() function as you suggested, but that unfortunately leads to an error in the SwiftFormat dependency, but only when trying to run Danger in my project’s repository:

> swift run danger-swift pr https://github.com/[…]
[…]
Building for debugging...
[55/55] Applying danger-swift
Build of product 'danger-swift' complete! (5.26s)
Starting Danger PR on […]
[…]/Danger/.build/debug/SwiftFormat-tool.build/module.modulemap:1:8: error: redefinition of module 'SwiftFormat'
1 | module SwiftFormat {
  |        `- error: redefinition of module 'SwiftFormat'
2 |     header "[…]/Danger/.build/arm64-apple-macosx/debug/SwiftFormat-tool.build/SwiftFormat-Swift.h"
3 |     requires objc

[…]/Danger/.build/debug/SwiftFormat.build/module.modulemap:1:8: note: previously defined here
1 | module SwiftFormat {
  |        `- note: previously defined here
2 |     header "[…]/Danger/.build/arm64-apple-macosx/debug/SwiftFormat.build/SwiftFormat-Swift.h"
3 |     requires objc

I tried to pin this dependency to an earlier version to check if it works then, but didn’t succeed in doing that.

Regardless, the naming clash really does seem to be an issue. Good find!

@Arafo
Copy link

Arafo commented Sep 27, 2024

@marcomasser did you try building for release?

@marcomasser
Copy link

marcomasser commented Sep 27, 2024

Yes, same result:

> swift run -c release danger-swift pr https://github.com/[…]
Building for production...
[1/1] Write swift-version-7BB6C6736DFA3E78.txt
Build of product 'danger-swift' complete! (0.17s)
Starting Danger PR on […]
[…]/Danger/.build/debug/SwiftFormat-tool.build/module.modulemap:1:8: error: redefinition of module 'SwiftFormat'
1 | module SwiftFormat {
  |        `- error: redefinition of module 'SwiftFormat'
2 |     header "[…]/Danger/.build/arm64-apple-macosx/debug/SwiftFormat-tool.build/SwiftFormat-Swift.h"
3 |     requires objc

[…]/Danger/.build/debug/SwiftFormat.build/module.modulemap:1:8: note: previously defined here
1 | module SwiftFormat {
  |        `- note: previously defined here
2 |     header "[…]/Danger/.build/arm64-apple-macosx/debug/SwiftFormat.build/SwiftFormat-Swift.h"
3 |     requires objc

Update: It does not make a difference whether the isDevelop in Danger’s Package.swift is set to true or false. If it’s false, Danger doesn’t declare the dependency on SwiftFormat, but it will still depend on OctoKit, which in turn depends on SwiftFormat.

@Arafo
Copy link

Arafo commented Sep 27, 2024

Interesting, do you know from where SwiftFormat dependency is coming from?

EDIT: nvm, I was able to reproduce adding SwiftFormat to my Package.swift file

@marcomasser
Copy link

It seems OctoKit is pulling that in.

@ivanopcode
Copy link

Thanks for the hint! I forked Danger and renamed all occurrences of the Danger() function as you suggested, but that unfortunately leads to an error in the SwiftFormat dependency, but only when trying to run Danger in my project’s repository:

Have you tried renaming the product/target to 'DangerSmth'? Looks like that should help.

@marcomasser
Copy link

marcomasser commented Oct 2, 2024

Have you tried renaming the product/target to 'DangerSmth'? Looks like that should help.

Thanks for the suggestion. I tried renaming the "Danger" target in my fork and then pull that in, but it didn’t help. I just get the same error about SwiftFormat.

I think renaming either the Danger target or the global function both should work and the error about SwiftFormat is just the next issue that is probably not related to this anymore. I just don’t understand why it should be a problem that OctoKit depends on SwiftLint 🤷‍♂️

Anyway, I looked into this some more and noticed that OctoKit only declares the dependency on SwiftFormat, but doesn’t actually use it. So I forked OctoKit and commented out that line and now this error when running Danger is gone – just for the next one to appear 😩

So now I’m here:

> swift run danger-swift pr https://github.com/…
[…]
Building for debugging...
[41/41] Emitting module Runner
Build of product 'danger-swift' complete! (1.60s)
Starting Danger PR on IdeasOnCanvas/MindNode#11360
warning: 'octokit.swift': found 1 file(s) which are unhandled; explicitly declare them as resources or exclude from the target
    …/Danger/.build/checkouts/octokit.swift/OctoKit/Info.plist

/var/folders/vk/v4gx2v6x4972w9v5r1xggx000000gn/T/danger/E804D871-2424-4A8D-82DC-D1C6F8A4037C/_tmp_dangerfile.swift:13:14: error: cannot find 'makeDangerDSL' in scope
 11 | import Danger
 12 | 
 13 | let danger = makeDangerDSL() // Renamed, original was: Danger()
    |              `- error: cannot find 'makeDangerDSL' in scope
 14 | let pullRequest = danger.github.pullRequest
 15 | let git = danger.git


/var/folders/vk/v4gx2v6x4972w9v5r1xggx000000gn/T/danger/E804D871-2424-4A8D-82DC-D1C6F8A4037C/_tmp_dangerfile.swift:70:1: error: cannot find 'SwiftLint' in scope
 68 | // MARK: - Run swiftlint
 69 | 
 70 | SwiftLint.lint(inline: true, configFile: ".swiftlint.yml")
    | `- error: cannot find 'SwiftLint' in scope
 71 | 
 72 | // MARK: - Private Extensions


/var/folders/vk/v4gx2v6x4972w9v5r1xggx000000gn/T/danger/E804D871-2424-4A8D-82DC-D1C6F8A4037C/_tmp_dangerfile.swift:74:19: error: cannot find type 'Git' in scope
 72 | // MARK: - Private Extensions
 73 | 
 74 | private extension Git {
    |                   `- error: cannot find type 'Git' in scope
 75 | 
 76 |     var hasSourcesModifications: Bool {

/var/folders/vk/v4gx2v6x4972w9v5r1xggx000000gn/T/danger/E804D871-2424-4A8D-82DC-D1C6F8A4037C/_tmp_dangerfile.swift:119:19: error: cannot find type 'GitHub' in scope
117 | }
118 | 
119 | private extension GitHub.PullRequest {
    |                   `- error: cannot find type 'GitHub' in scope
120 | 
121 |     var hasMilestone: Bool { self.milestone != nil }

ERROR: Dangerfile eval failed at Dangerfile.swift
ERROR: Could not get the results JSON file at /var/folders/vk/v4gx2v6x4972w9v5r1xggx000000gn/T/danger/E804D871-2424-4A8D-82DC-D1C6F8A4037C/danger-response.json
[…]

makeDangerDSL() is my renamed version of Danger() to fix the naming clash. So now all the public symbols from the Danger module seem to be missing, see also SwiftLint and GitHub. I’m digging further…

@Arafo
Copy link

Arafo commented Oct 9, 2024

After many tries I got it working somehow

First, I forked SwiftFormat and OctoKit

In SwiftFormat fork I commented out this line
https://github.com/nicklockwood/SwiftFormat/blob/ed75a316f2f2868b9181ae8d1c7182bf8d97f269/Package%40swift-5.6.swift#L9

Then, in OctoKit fork, I just switch SwiftFormat to point to my fork in the Package.swift file.

This avoids symbols duplication, I'm not sure why this is a thing now with Swift 6 but I observed that I was getting two different build folders for SwiftFormat CommandLineTool target, the usual one and another one ending with -tool.build. I didn't found anything about this but this message in the Swift forums.

Now, with these 2 forks, I was able to override the version used in my Danger setup adding this to my Package.swift dependency list:
.package( url: "https://github.com/myfork/octokit.swift", branch: "main" )
I know this is not the ideal way to "override" dependencies but it works for now.

Now, the only way I found to properly link Danger is specifying both arm64 and x86_64 architectures, when building:
swift build -c release --arch arm64 --arch x86_64

Then the usual Danger dynamic lib renaming:
cp .build/apple/Products/Release/libDangerDeps.dylib .build/apple/Products/Release/libDanger.dylib

And last, run the danger-swift binary:
swift run -c release --arch arm64 --arch x86_64 danger-swift ci

This works for me but I have no clue why specifying both arm and Intel archs seems to do the trick.

@f-meloni
Copy link
Member

I have tested @abhi-m-simformsolutons's change from #626 and it seemed to fix all the issues.

Screenshot 2024-10-14 alle 10 24 08

I have released version 3.20.0, let me know if it works!

@marcomasser
Copy link

Yes! 🥳
This now works fine without any of the modifications discussed in this issue. Thank you 👏

@f-meloni
Copy link
Member

Good! I will close this issue then, feel free to re open it if needed

@oronbz
Copy link

oronbz commented Oct 14, 2024

@f-meloni Still experiencing this on the new version:

danger-swift 3.18.1 is already installed but outdated (so it will be upgraded).
==> Fetching danger/tap/danger-swift
==> Downloading https://github.com/danger/danger-swift/archive/3.20.0.tar.gz
==> Downloading from https://codeload.github.com/danger/swift/tar.gz/refs/tags/3.20.0
==> Upgrading danger/tap/danger-swift
  3.18.1 -> 3.20.0 
==> make install PREFIX=/opt/homebrew/Cellar/danger-swift/3.20.0
🍺  /opt/homebrew/Cellar/danger-swift/3.20.0: 8 files, 3.9MB, built in 39 seconds
Warning: HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated
dependents or dependents with broken linkage!
+ echo '⚠️ DANGER ! :)'
⚠️ DANGER ! :)
+ danger-swift ci
/var/folders/b8/9zt_tx3s1y37nzh_cs991xyc0000gn/T/danger/FFA7F08D-5ACD-4F14-9B3C-8765A95A10D2/_tmp_dangerfile.swift:1:8: error: no such module 'Danger'
 1 [REDACTED] import Danger
   [REDACTED]        `- error: no such module 'Danger'
 2 [REDACTED] import Foundation
 3 [REDACTED] 
ERROR: Dangerfile eval failed at Dangerfile.swift
ERROR: Could not get the results JSON file at /var/folders/b8/9zt_tx3s1y37nzh_cs991xyc0000gn/T/danger/FFA7F08D-5ACD-4F14-9B3C-8765A95A10D2/danger-response.json
Failing the build, there is 1 fail.
Feedback: https://github.com/gtforge/gtforge-iphone/pull/3919#issuecomment-2411101472
ERROR: Could not get the results JSON file at /var/folders/b8/9zt_tx3s1y37nzh_cs991xyc0000gn/T/danger/FFA7F08D-5ACD-4F14-9B3C-8765A95A10D2/danger-response.json

@f-meloni
Copy link
Member

@oronbz this is not using danger-swift from Package.swift, but from brew, I'm working on a fix for that as well, but is not ready yet

@oronbz
Copy link

oronbz commented Oct 14, 2024

Got it, will wait (: thanks!

@f-meloni
Copy link
Member

@oronbz this is the diff that should be able to fix the issue #627

@f-meloni
Copy link
Member

@oronbz you can try now, it should be working

@oronbz
Copy link

oronbz commented Oct 14, 2024

Same @f-meloni :(

Warning: swiftlint 0.57.0 is already installed and up-to-date.
To reinstall 0.57.0, run:
  brew reinstall swiftlint
+ brew install danger-swift
danger-swift 3.18.1 is already installed but outdated (so it will be upgraded).
==> Fetching danger/tap/danger-swift
==> Downloading https://github.com/danger/danger-swift/archive/3.20.1.tar.gz
==> Downloading from https://codeload.github.com/danger/swift/tar.gz/refs/tags/3.20.1
==> Upgrading danger/tap/danger-swift
  3.18.1 -> 3.20.1 
==> make install PREFIX=/opt/homebrew/Cellar/danger-swift/3.20.1
🍺  /opt/homebrew/Cellar/danger-swift/3.20.1: 8 files, 3.9MB, built in 47 seconds
Warning: HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated
dependents or dependents with broken linkage!
+ echo '⚠️ DANGER ! :)'
⚠️ DANGER ! :)
+ danger-swift ci
/var/folders/b8/9zt_tx3s1y37nzh_cs991xyc0000gn/T/danger/A2174C8B-B237-46B1-9154-A4BF42A901DA/_tmp_dangerfile.swift:1:8: error: no such module 'Danger'
 1 [REDACTED] import Danger
   [REDACTED]        `- error: no such module 'Danger'
 2 [REDACTED] import Foundation
 3 [REDACTED] 
ERROR: Dangerfile eval failed at Dangerfile.swift
ERROR: Could not get the results JSON file at /var/folders/b8/9zt_tx3s1y37nzh_cs991xyc0000gn/T/danger/A2174C8B-B237-46B1-9154-A4BF42A901DA/danger-response.json
Failing the build, there is 1 fail.
Feedback: https://github.com/gtforge/gtforge-iphone/pull/3919#issuecomment-2411101472
ERROR: Could not get the results JSON file at /var/folders/b8/9zt_tx3s1y37nzh_cs991xyc0000gn/T/danger/A2174C8B-B237-46B1-9154-A4BF42A901DA/danger-response.json

@oronbz
Copy link

oronbz commented Oct 14, 2024

@f-meloni Let me know if I should keep comment updates here or on the other open issue: #623

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests