Not getting 'pipelineStatuses' from Airflow Pipelines API

Affected module
Does it impact the UI, backend or Ingestion Framework?
Backend
Describe the bug

Not getting pipelineStatuses field from Airflow Pipelines API
if we pass fields=status it throws error with status code 400
if we pass fields=pipelineStatuses, API does't throw any error but also not getting pipelineStatuses field in response

To Reproduce
Screenshots or steps to reproduce
http://localhost:8585/api/operations/v1/airflowPipeline?fields=owner&service=bigquery_test
Response:
{
  "data": [
    {
      "id": "227c95b0-9b3b-4902-8c2d-256de9276254",
      "name": "bigquery_test_metadata",
      "displayName": "bigquery_test_metadata",
      "pipelineType": "metadata",
      "owner": {
        "id": "bcf6da47-0689-4fde-8302-b4cdfb5f309b",
        "type": "user",
        "name": "aaron_johnson0",
        "displayName": "Aaron Johnson",
        "deleted": false,
        "href": "http://localhost:8585/api/v1/users/bcf6da47-0689-4fde-8302-b4cdfb5f309b"
      },
      "fullyQualifiedName": "bigquery_test.bigquery_test_metadata",
      "pipelineConfig": {
        "config": {
          "includeViews": true,
          "enableDataProfiler": false,
          "generateSampleData": false
        },
        "schema": "databaseServiceMetadataPipeline"
      },
      "forceDeploy": true,
      "pausePipeline": false,
      "concurrency": 1,
      "startDate": "2022-03-22",
      "endDate": "",
      "pipelineTimezone": "UTC",
      "retries": 1,
      "retryDelay": 300,
      "pipelineCatchup": false,
      "scheduleInterval": "5 * * * *",
      "pipelineTimeout": 60,
      "service": {
        "id": "5359f1cd-ed44-466c-9b9b-622fd1d31ed5",
        "type": "databaseService",
        "name": "bigquery_test",
        "description": "",
        "deleted": false,
        "href": "http://localhost:8585/api/v1/services/databaseServices/5359f1cd-ed44-466c-9b9b-622fd1d31ed5"
      },
      "href": "http://localhost:8585/api/operations/v1/airflowPipeline/227c95b0-9b3b-4902-8c2d-256de9276254",
      "version": 0.1,
      "updatedAt":<PHONE_NUMBER>369,
      "updatedBy": "anonymous",
      "deleted": false
    }
  ],
  "paging": {
    "total": 1
  }
}

Expected behavior
API should send pipelineStatuses in response.
Version:

OS: [e.g. iOS]
Python version:
OpenMetadata version: [e.g. 0.8]
OpenMetadata Ingestion package version: [e.g. openmetadata-ingestion[docker]==XYZ]

Additional context
Add any other context about the problem here.
cc @ayush-shah

@ShaileshParmar11 you need to pass "status" in fields to get this. Can you try this call http://localhost:8585/api/operations/v1/airflowPipeline?fields=owner,status&service=bigquery_test

@ShaileshParmar11 do you have the airflow container running?


Fix insta-timeout bug

This PR has a bunch of changes related to fixing the "status: Recreate bug" (which turned out to a progress deadline problem) and making stuff like that easier to debug in the future (or now, if the workaround doesn't work 😄 ). I believe this may be the same bug we've seen when doing a rollback on core. I've added test cases for type: Recreate and rollbacks, though unfortunately I wasn't able to figure out how to make them true regression tests (the buggy k8s behaviour seems to be inconsistent, and these tests do not fail on master).
Highlights:

Work around this k8s bug in versions < 1.7.7 by refusing to declare a failure to progress within 10 seconds of the resource being deployed.
Make sure Deployment failures and timeouts always log something about why they happened, and include the name of the replicaset we looked at (if applicable)
Make the resets used when a particular poll cycle fails more robust.
Make deploy_timed_out? more explicit (it was sometimes a fallback else after the other two checks)
Make it possible to use debug-level logging in production by disabling kubectl output logs for the EjsonSecretProvisioner (previously, the debug-level logging would have logged everything we got back from the server, including base64-encoded secret data).

It also does two renames to fix frequent sources of confusion: Runner (often confused with RunnerTask) -> DeployTask, and @deploy_started -> @deploy_started_at/deploy_started? (it's a timestamp). These admittedly aren't necessary for this PR, so I can extract them (they're separate commits) if they're making it hard to review. Same goes for the apps/v1beta change in the fixtures.
@Shopify/cloudplatform

LGTM I'd probably split them out but I'm not very concerned.

Here's an example of the timeout logging after the commit I just pushed:

🎩  using the executable was successful. Will merge on green.


Clean blanks before format when write option is demanded

Reason:
usually when an import is added by the IDE it adds it at the top of the dependency block. Like this:
import (
    "github.com/guyincogninto/costumes"
    "bytes"
    "flag"
    "fmt"

    "github.com/elbarto/graffiti"
)

Current go imports -w option formats and leave it like this:
import (
    "bytes"
    "flag"
    "fmt"

    "github.com/guyincogninto/costumes"

    "github.com/elbarto/graffiti"
)

Solution:
Maybe I'm a bit fussy, but it's not desirable for me. This fork will leave the thing like this:
import (
    "bytes"
    "flag"
    "fmt"

    "github.com/elbarto/graffiti"
    "github.com/guyincogninto/costumes"
)

Wow such a mistake, I thought I was working on my fork. Sorry for any botherings 🙇


[DNM][stdlib] Add reduce(_:) method for Sequence to standard library

Introduces a folding operator that seeds itself from the elements
passed to reduce, removing the need for an explicit value seed.
Implements SE-nnnnnnnn

Swift Evolution thread

Can one of the admins verify this patch?

Please update the base branch to main by Oct 5th otherwise the pull request will be closed automatically.

How to change the base branch: (Link)
More detail about the branch update: (Link)


Restructure codebase

Documentation still needs to be worked on.

When using with rpc_auth: False, I had to delete the dependency of the tezos chart on the rpc-auth chart otherwise I get such message (both with devspace and without):
[fatal]  error deploying: Error deploying chain: Unable to deploy helm chart: error during 'helm upgrade chain ./charts/tezos --namespace default --values /tmp/921905247 --install --kube-context minikube': Release "chain" does not exist. Installing it now.
Error: found in Chart.yaml, but missing in charts/ directory: authenticated-rpc-tezos-chain
 => exit status 1
Run `devspace purge -d chain` and `devspace deploy` to recreate the chart

Same with rpc-auth true in values.yaml and with -v rpc-auth passed.

@nicolasochem I believe you need to run helm dependency update charts/tezos. This packages rpc-auth into the tezos chart. Then you can run devspace dev --var=CHAIN_NAME="$CHAIN_NAME" -p rpc-auth to have devspace also spin up rpc-auth.
(i wouldn't run mkchain --rpc-auth if you are using devspace. Right now it will try applying the same manifest twice bec rpc_auth: true in values yaml. It's a kink I have an idea of how to solve. Still working on cleaning up docs and adding new info about restructured codebase to explain everything)

After speaking with @nicolasochem , we decided to open the PR although some documentation is still being worked on. That should be finished obviously before the release

After speaking with @nicolasochem , we decided to open the PR although some documentation is still being worked on. That should be finished obviously before the release

I have some reservations about moving all the init containers to top-level directories. I understand that every one of them should be in a ready state to be separated into its own repo, but in some cases it feels that the containers are doing something trivial. However, this should be addressed prior to release and should not prevent us from merging this PR.

I agree we should discuss

We have identified a bug where nodes sometimes don't connect to the p2p service, but I do not think anything in this PR caused this behavior to change. I have another work in progress where I completely remove the p2p service which I think will make things wlookork better.

Roland and I both ran into this. I believe a recent minikube version broke something as I ran the exact same code on a separate machine with an older version of minikube and it worked.

I have some reservations about moving all the init containers to top-level directories. I understand that every one of them should be in a ready state to be separated into its own repo, but in some cases it feels that the containers are doing something trivial. However, this should be addressed prior to release and should not prevent us from merging this PR.

I agree we should discuss

We have identified a bug where nodes sometimes don't connect to the p2p service, but I do not think anything in this PR caused this behavior to change. I have another work in progress where I completely remove the p2p service which I think will make things wlookork better.

Roland and I both ran into this. I believe a recent minikube version broke something as I ran the exact same code on a separate machine with an older version of minikube and it worked.


Spec v3.0

This is pretty stable now, and the spec is backward compatible with the earlier version.

Nice!
I didn't realise version 3 was backwards compatible with version 2. Does this mean that using VSCode with a version 2 language client, or neovim or emacs with plugins that support version 2 only, will still work with this version?


membrane raft inferences

'protein localization to membrane raft ; GO:1903044' is not being inferred to be is_a 'protein localization to membrane ; GO:0072657' because membrane raft is_a membrane part, not a membrane.
Change membrane raft to be is_a membrane region and recheck inferences.
Reported by: jl242
Original Ticket: geneontology/ontology-requests/10970

Fixed by improved axiomatisation of membrane regions - now inferred.


ARM Extension error

Does this occur consistently?
Repro steps:

Action: startArmLanguageServer
Error type: Error
Error Message: This extension requires .NET Core for full functionality, but we were unable to download and install a local copy for the extension. If this error persists, please see https://aka.ms/vscode-armtools-dotnet for troubleshooting tips.
Details: dotnet.acquire returned undefined
Version: 0.12.0
OS: win32
OS Release: 10.0.18363
Product: Visual Studio Code
Product Version: 1.50.0
Language: en

Call Stack
Object.wrapError extension.bundle.js:395:93998
Object.<anonymous> extension.bundle.js:486:771149
fulfilled extension.bundle.js:486:770045

@chiragce17 Did the troubleshooting tips help?  Thanks!

FYI I've improved the troubleshooting instructions at https://github.com/microsoft/vscode-azurearmtools/wiki/Troubleshooting-DotNet-Acquisition.


Colored terminal output

The filename, line numbers and function are hard to read in the command line output, e.g.
lib/matplotlib/patches.py:3887 in public method `__init__`:
        D301: Use r""" if any backslashes in a docstring
lib/matplotlib/offsetbox.py:238 in public method `set_offset`:
        D301: Use r""" if any backslashes in a docstring
lib/matplotlib/image.py:741 in private method `set_interpolation`:
        D301: Use r""" if any backslashes in a docstring

It would be great to color them differently. I would be willing to provide a PR if there is interest.
If so:

Should color be on or off by default?
I'd use https://pypi.org/project/colorama/ for the output. Can I make it a dependency (hard or optional)?

Flake8 has a plugin that will color these for you and is configurable. FWIW

Thanks https://pypi.org/project/flake8-colors/ will do.
If somebody else want's to do this, you also need https://pypi.org/project/flake8-docstrings/ to make pydocstyle error codes available in flake8.


config.json is missing uuid for exercise

Hello,
As a result of #290 a new exercise was added to the config.json file. This broke the file due to a missing comma, which then broke the nexercism importer. I've just hot-fixed this missing comma as it's blocking us shipping nextercism, but I also noticed that the new exercise is also missing a uuid, core and unlocked_by fields.

Could one of the @exercism/swift maintainers add these fields in for this exercise please :)
@kytrinyx - I'm guessing configlet isn't configured on this track? Or did it miss the comma? Could we rectify that either way please?
@ccare - Can we defend against this in the importer please? If broke during a full db seed, but I imagine it would be the same issue on an update too.

Thanks everyone 💙

https://travis-ci.org/exercism/swift/jobs/265299577
@iHiD  The configlet did not fail even though it did report the config.json was not valid.  This should have failed.
Is there a way to check all the required fields are there in the JSON?
$ bin/fetch-configlet
The command "bin/fetch-configlet" exited with 0.
$ bin/configlet lint .
-> invalid config config.json -- invalid character '{' after array element
The command "bin/configlet lint ." exited with 0.

How do I check if the UUID is unique across all exercises? https://github.com/exercism/docs/blob/39109e34d3590b4b9399600a57798601353e96d2/language-tracks/configuration/README.md

My understanding is that configlet should do that for you. I'll let @kytrinyx fill in the details when she's online. As @iHiD says, we'll also defend against it at our end (I thought we had, but obviously not).

I'm Masa, who issued #290.
I am so sorry for this commit and the inconvenience this has been causing you.
To be honest, I was overlooking the process of configlet. I promise I never forget to do so anymore.
I can't apologize enough.

@creaaa Hi Masa, This is not your fault. Please do not feel bad about it. This was a bug in the config checker that did not catch the new keys that were needed. The config checker should have failed the check when it saw that the config file was not valid. Thank you for your pull request and helping us find this bug. 👍

@creaaa Don't worry at all :) When stuff like this breaks it's never any one person's fault and it's always the fault of systems not being good enough, not people making mistakes. This is why tests and CI and things like configlet exist. You can just take this as good learning about why those things are important, but don't feel bad about it! As @masters3d said, thank you for your contribution!

How do I check if the UUID is unique across all exercises?
Is there a way to check all the required fields are there in the JSON?

@masters3d Both of these will be configlet. Everything's under real active development atm so I imagine @kytrinyx is just playing catchup on things. I'm not sure what's written or not yet, but they will both eventually be the responsibility of it. In terms of uuid, if you generate a new one, it will be unique - the key is just not to copy and paste, which as you highlight, we need to check for.
Thanks for replying everyone - none of this is anything to worry about! :)

Thanks so much for the contribution, and for finding all of these gaps in our CI process! No time like the present to get this all sorted out.
I'll make sure that configlet fails the build if necessary. It does some checking of UUIDs, I think (can't remember if we've implemented it or just opened the issue about it). I built a UUID checker service, but haven't had time to get Configlet to call it yet.


[Bug] Datetime data inconsistency (off by 8 hours) in snapshot phase

Search before asking

[X] I searched in the issues and found nothing similar.

Flink version
1.13.6/1.14
Flink CDC version
2.2/2.3
Database and its version
MySQL 5.7+ & 8.0+
Minimal reproduce step
#1739
The issue still persists in snapshot phase and when MySQL is of CST timezone, and the reason is Debezium's Timestamp::toEpochMillis does not respect time zone:

PRECONDITION：Server/local time zone are Asia/Shanghai (UTC+8)，MySQL time zone is CST
To reproduce the issue:

create a time with pk and datetime field and insert some random data:

CREATE TABLE `batchdatetime` (
  `id` bigint NOT NULL AUTO_INCREMENT,
  `dt` datetime DEFAULT NULL,
  PRIMARY KEY (`id`)
)

# insert data here

mysql> select * from batchdatetime;
+----+---------------------+
| id | dt                  |
+----+---------------------+
|  1 | 2016-10-15 02:15:15 |
|  2 | 2016-10-15 02:15:15 |
+----+---------------------+

create cdc job using stream api

  public static void main(String[] args) throws Exception {
    final StreamExecutionEnvironment env = StreamExecutionEnvironment.createLocalEnvironment();
    env.setParallelism(1);
    MySqlSource<String> mysqlSource = new MySqlSourceBuilder<String>()
	.databaseList("aps_test")
	.tableList("aps_test.batchdatetime")
	.hostname("localhost")
	.username("root")
	.password("")
	.serverTimeZone("Asia/Shanghai")
	.includeSchemaChanges(true)
	.deserializer(new JsonDebeziumDeserializationSchema())
	.scanNewlyAddedTableEnabled(true)
	.build();

    DataStreamSource<String> source = env.fromSource(mysqlSource, WatermarkStrategy.noWatermarks(), "mysql-source");
    source.print();
    env.execute();
  }

Start the job and witness how debezium brings inconsistency to datetime columns:

dateTime.toInstant(ZoneOffset.UTC).toEpochMilli() =<PHONE_NUMBER>000
BUT 2016-10-15T02:15:15 corresponds to<PHONE_NUMBER>000 in milliseconds in BOTH server and local time zone:
AND we can verify this using the following SQL:
mysql> select UNIX_TIMESTAMP(dt) * 1000 as aha from batchdatetime;
+---------------+
| aha           |
+---------------+
|<PHONE_NUMBER>000 |
|<PHONE_NUMBER>000 |
+---------------+

The correct way to convert datetime to timestamp is dateTime.toInstant(ZoneOffset.of("+8")).toEpochMilli()

and the +8 should've come from user specific dbz properties OR a default time zone of the system.
What did you expect to see?
{"before":null,"after":{"id":1,"dt":1476468915000},"source":{"version":"1.6.4.Final","connector":"mysql","name":"mysql_binlog_source","ts_ms":0,"snapshot":"false","db":"aps_test","sequence":null,"table":"batchdatetime","server_id":0,"gtid":null,"file":"","pos":0,"row":0,"thread":null,"query":null},"op":"r","ts_ms":1680861868595,"transaction":null}
What did you see instead?
{"before":null,"after":{"id":1,"dt":1476497715000},"source":{"version":"1.6.4.Final","connector":"mysql","name":"mysql_binlog_source","ts_ms":0,"snapshot":"false","db":"aps_test","sequence":null,"table":"batchdatetime","server_id":0,"gtid":null,"file":"","pos":0,"row":0,"thread":null,"query":null},"op":"r","ts_ms":1680861868595,"transaction":null}
Anything else?
Critical data inconsistency issue.
Are you willing to submit a PR?

[X] I'm willing to submit a PR!

Hello, until now this problem still exists, is it dependent on upstream updates?
#1739 This doesn't solve the problem
Flink version
1.18
Flink CDC version
3.0.1
Database and its version
MySQL 5.7+ & 8.0+

So far I have implemented it this way and the snapshot and incremental timestamp values are normal
I can submit pr if necessary

Closing this issue as it has been migrated to Apache Jira.


test: fix && update flaky snapshots

Notable changes:

removed the webpack manifest from snapshots to remove noise
wrapped the loader with a hack to force the resourcePath to be consistent across builds so the instrumented output is always the same

@michael-ciniawsky done!

Ship it @michael-ciniawsky


the first commit 2023.04.18

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


[BUG] Storage Class can be created with 3 replicas when disk has 0 replicas

Describe the bug
"Number Of Replicas" for Storage Class creation doesn't audit replicas available on extra-disk that has been force-formatted with ext4 from Host Storage Config, with disk selector label added.
To Reproduce
Steps to reproduce the behavior:

Add an extra disk to the node, Hosts -> Edit Config -> Storage -> Add Disk -> Force Format Ext4
Add tags to the disk you just added
Go-to Advanced ->  Storage Classes -> Create
Fill out, keep "Number Of Replicas: 3", select node, select disk selector with the same tag that you used for the extra disk, "Provisioner: Longhorn", keep everything in Customize as default
Go-to Image -> Create, fill out, go-to "Storage" select Storage Class to the one you just created

Expected behavior
That the storage class would check the disk with the Longhorn provisioner to validate that if the user specified "Number Of Replicas: 3" that the Longhorn extra-disk has 3 replicas - validating that # of replicas are accurate.
Support bundle
supportbundle_22241fc2-4f6e-4105-9483-178b97ed77b8_2022-09-24T00-40-56Z.zip
Environment

Harvester ISO version: v1.0.1-rc1
Underlying Infrastructure: bare-metal Dell PowerEdge R720

Additional context
When image is uploaded you can see that it persists to the disk on the host /dev/sda at 546MB the same size as the ubuntu-20.04-server-cloudimg-amd64-disk-kvm.img that was uploaded.  It is persisting the image to that disk but the disk itself doesn't have any replicas in Longhorn.
It can be noticed that we do have tests that cover both "1" and "3" replicas:
https://github.com/futuretea/harvester/blob/218dfd23449a2b393e20ac80a40a0072f970cad6/pkg/webhook/resources/virtualmachineimage/mutator_test.go#L49-L80
Supporting Screenshots

@irishgordo
The number of replicas on a disk is the sum of the volume replicas that are currently scheduled to the disk

@futuretea thanks for looking at this :smile: !
So all that happens when replicas are set for the StorageClass is that it just makes sure that any Volumes created using that StorageClass have "N" number of replicas in Longhorn?

@futuretea thanks for looking at this 😄 ! So all that happens when replicas are set for the StorageClass is that it just makes sure that any Volumes created using that StorageClass have "N" number of replicas in Longhorn?

Yes


Deleting plugin never completes

django-cms==3.2.5;  Django==1.8.13
If I have a page with plugins and I attempt to delete one from the page (either through the "Structure" UI or double-clicking on the plugin on the "Content" view of the page,  it never completes (just spins forever).
It appears to happen to any plugin (custom-built ones but also the "native" text, etc. plugins).
Any ideas?   The site is using MySQL==5.6.17, but it doesn't appear to be a hang there (I've checked "SHOW FULL PROCESSLIST" and there's nothing "stuck").     It's not a server issue (I can reproduce it on different machines).
Any suggestions of where to look next would be appreciated.

Any chance it is a duplicate of https://github.com/divio/django-cms/issues/4376 ?
tl;dr the can happen if you use firefox with 1password/lastpass extensions enabled
If it's not the case then I'd love to hear more details. OS / Browser / any javascript errors in the browser console?

Does it and with 500 error?
It is ajax request. Use developer tools in Your browser and check request result .

vxsx ---- OMG - I think you've hit it.   I AM using Firefox and just recently installed that extension.  Lemme check to see if that is the culprit.

YES - that's the problem.


How exactly do I "adjust location of leptonica and tesseract in qt-box-editor.pro"?

How exactly do I "adjust location of leptonica and tesseract in qt-box-editor.pro"?
Do I need to do that too if I build it in Ubuntu?

What error you get when you tried to build this program?

I get no errors (I used the instructions to build on Ubuntu)
The problem is that when I open a png image I can't generate the boxes from the editor, the option "Generate boxes for page" does nothing (that's why I asked the question because I had imagined it might be related to this problem)
It is no longer a problem for me because I am now generating the boxes directly using tesseract.
By the way the editor is very good and very helpful, thanks for it (It crashes sometimes, but if I save often it is not a problem)

What version of tesseract are you using?

tesseract --version
tesseract 3.04.00
leptonica-1.72
libjpeg 8d (libjpeg-turbo 1.3.0) : libpng 1.2.50 : libtiff 4.0.3 : zlib 1.2.8

"Generate boxes for page" does not work is with tesseract 3.04 - there was change of tesseract API, that caused that this function stop to work. I will try to find solution, but it will not be soon...

Thank you, and again thank you for making the editor, it is very useful.

              [tesseract --version
               tesseract 3.04.00
               leptonica-1.72]
 -->  Following the "building on ubuntu"  instructions -->after make comand , these showed-->

src/ChildWidget.cpp:28:34: fatal error: leptonica/allheaders.h: No such file or directory
compilation terminated.
Makefile:628: recipe for target 'temp/ChildWidget.o' failed
make: *** [temp/ChildWidget.o] Error 1


Cart Error on 1.1.1

get this command error after entering "carthage update --platform iOS --use-xcframeworks"
Build Failed
Task failed with exit code 65:
/usr/bin/xcrun xcodebuild -workspace /Users/marcus/Downloads/appdb/Carthage/Checkouts/SwiftMessages/iMessageDemo/iMessageDemo.xcworkspace -scheme SwiftMessages -configuration Release -derivedDataPath /Users/marcus/Library/Caches/org.carthage.CarthageKit/DerivedData/13.0_13A5154h/SwiftMessages/9.0.2 -sdk iphoneos ONLY_ACTIVE_ARCH=NO CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES archive VALIDATE_WORKSPACE=NO -archivePath /var/folders/v9/spyf71qn3vvg_lg6_xkb46_r0000gn/T/SwiftMessages SKIP_INSTALL=YES GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=NO CLANG_ENABLE_CODE_COVERAGE=NO STRIP_INSTALLED_PRODUCT=NO (launched in /Users/marcus/Downloads/appdb/Carthage/Checkouts/SwiftMessages)
This usually indicates that project itself failed to compile. Please check the xcodebuild log for more details: /var/folders/v9/spyf71qn3vvg_lg6_xkb46_r0000gn/T/carthage-xcodebuild.37su4c.log
The last few lines in the log file says this
The following build commands failed:
CompileSwift normal arm64 (in target 'SwiftMessages' from project 'Pods')
CompileSwiftSources normal arm64 com.apple.xcode.tools.swift.compiler (in target 'SwiftMessages' from project 'Pods')
CompileSwiftSources normal armv7 com.apple.xcode.tools.swift.compiler (in target 'SwiftMessages' from project 'Pods')
CompileSwift normal armv7 (in target 'SwiftMessages' from project 'Pods')
(4 failures)

Hi, I can't reproduce this. Just tested with a fresh carthage build and it worked fine.
Make sure you have latest Xcode installed (v12.5), latest Carthage (v0.38.0) and also try cleaning Carthage folder before running the command

How do I clean my Carthage folder.

How do I clean my Carthage folder.

You can just delete it, it rebuilds automatically

Sorry, you know where is located 😅