-
Notifications
You must be signed in to change notification settings - Fork 50
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
Fix flutter health wf #1787
base: main
Are you sure you want to change the base?
Fix flutter health wf #1787
Conversation
PR HealthBreaking changes ✔️
Changelog Entry ✔️
Changes to files need to be accounted for in their respective changelogs.
API leaks
|
Package | Leaked API symbols |
---|---|
ffi | MallocAllocator CallocAllocator |
ffigen | Type AstNode Visitation Visitor BindingType NoLookUpBinding Binding Writer SymbolAddressWriter EnumClass EnumConstant UniqueNamer ObjCBuiltInFunctions ObjCImport Parameter ObjCMsgSendFunc ObjCMsgSendVariant ObjCMsgSendVariantFunc FunctionType ObjCInternalGlobal ObjCBlock ObjCListenerBlockTrampoline Func LookUpBinding LibraryImport BindingString BindingStringType ObjCInterface ObjCMethod ObjCProperty ObjCMethodKind ObjCMethodOwnership ObjCMethodFamily ObjCProtocol ObjCCategory Struct Compound CompoundMember CompoundType Union MacroConstant Constant UnnamedEnumConstant Global Typealias PointerType ImportedType ConfigSpec ConfigValue |
jni | _opaque_pthread_mutex_t _opaque_pthread_cond_t _Dart_FinalizableHandle _ReferenceType |
objective_c | ObjCBlockBase c._ObjCBlockImpl _ObjCBlockDesc _ObjCBlockRef _ObjCObject _Dart_FinalizableHandle _ObjCProtocol _ObjCSelector _ObjCMethodDesc _ObjCObjectRef _NSZone |
This check can be disabled by tagging the PR with skip-leaking-check
.
License Headers ⚠️
// Copyright (c) 2024, the Dart project authors. Please see the AUTHORS file
// for details. All rights reserved. Use of this source code is governed by a
// BSD-style license that can be found in the LICENSE file.
Files |
---|
pkgs/jni/lib/src/third_party/generated_bindings.dart |
pkgs/native_assets_builder/test_data/native_dynamic_linking/bin/native_dynamic_linking.dart |
pkgs/objective_c/lib/src/ns_input_stream.dart |
All source files should start with a license header.
This check can be disabled by tagging the PR with skip-license-check
.
@liamappelbe I have excluded @HosseinYousefi I have excluded |
@@ -1,4 +1,4 @@ | |||
## 16.0.1-wip | |||
## 17.0.0-wip |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's this change for? Can we make it 16.1 instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's because ffigen
has breaking changes, see the PR health comment. Happy to disable the breaking change check for ffigen
in general, address the upgrade in a later PR, or just ignore this breakage.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the issue is that the breaking change checker is checking for changes on internal classes. This is the only breaking change in the report:
"breakingChanges": {
"label": "BREAKING CHANGES",
"children": [
{
"label": "Class ImportedType",
"children": [
{
"label": "Constructor ImportedType",
"children": [
{
"changeDescription": "Kind of parameter \"defaultValue\" changed. not named -> named",
"changeCode": "CE07",
"isBreaking": true,
"type": "major"
}
]
}
]
}
]
},
ImportedType
is not part of the public API (or at least, it shouldn't be public). The fix here is to figure out why that class (and others mentioned in the non-breaking changes) are considered to be part of the public API. It's probably related to the issues in the API leaks check. But if you want to just ignore ffigen for now, that's fine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right - the leaks could have something to do with that. Those clean ups should be done in follow ups.
Update the health workflow to newest version.
Contribution guidelines:
dart format
.Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.