id
stringlengths 4
10
| text
stringlengths 4
2.14M
| source
stringclasses 2
values | created
timestamp[s]date 2001-05-16 21:05:09
2025-01-01 03:38:30
| added
stringdate 2025-04-01 04:05:38
2025-04-01 07:14:06
| metadata
dict |
|---|---|---|---|---|---|
992512198
|
[tool_crash] ProcessException: Process timed out: Command: xcrun, OS error code: -1
Command
flutter build ipa
Steps to Reproduce
...
...
...
Logs
ProcessException: Process timed out:
Command: xcrun, OS error code: -1
#0 RunResult.throwException (package:flutter_tools/src/base/process.dart:124:5)
#1 _DefaultProcessUtils.run (package:flutter_tools/src/base/process.dart:347:19)
<asynchronous suspension>
#2 buildXcodeProject (package:flutter_tools/src/ios/mac.dart:374:47)
<asynchronous suspension>
#3 _BuildIOSSubCommand.runCommand (package:flutter_tools/src/commands/build_ios.dart:257:37)
<asynchronous suspension>
#4 BuildIOSArchiveCommand.runCommand (package:flutter_tools/src/commands/build_ios.dart:122:50)
<asynchronous suspension>
#5 FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1043:27)
<asynchronous suspension>
#6 AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#7 CommandRunner.runCommand (package:args/command_runner.dart:196:13)
<asynchronous suspension>
#8 FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:284:9)
<asynchronous suspension>
#9 AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#10 FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:232:5)
<asynchronous suspension>
#11 run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:62:9)
<asynchronous suspension>
#12 AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
[✓] Flutter (Channel stable, 2.2.3, on Mac OS X 10.15.7 19H2 darwin-x64, locale en-IN)
• Flutter version 2.2.3 at /Users/clorida/flutter_projects/flutterSDK/flutter
• Framework revision f4abaa0735 (2 months ago), 2021-07-01 12:46:11 -0700
• Engine revision 241c87ad80
• Dart version 2.13.4
[!] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
• Android SDK at /Users/clorida/Library/Android/sdk
• Platform android-30, build-tools 29.0.2
• Java binary at: /Applications/Android Studio 2.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
✗ Android license status unknown.
Run `flutter doctor --android-licenses` to accept the SDK licenses.
See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.
[✓] Xcode - develop for iOS and macOS
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 12.4, Build version 12D4e
• CocoaPods version 1.10.2
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 4.2)
• Android Studio at /Applications/Android Studio 2.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
[✓] Connected device (2 available)
• iPod touch (7th generation) (mobile) • 139844B3-7257-4943-B1DD-A1EBF221BBA7 • ios • com.apple.CoreSimulator.SimRuntime.iOS-14-4 (simulator)
• Chrome (web) • chrome • web-javascript • Google Chrome 93.0.4577.63
! Error: Admin’s iPhone is not connected. Xcode will continue when Admin’s iPhone is connected. (code -13)
! Doctor found issues in 1 category.
Flutter Application Metadata
Type: app
Version: 1.0.0+1
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: f4abaa0735eba4dfd8f33f73363911d63931fe03
Plugins
agora_rtc_engine-3.4.6
android_intent-0.3.7+7
firebase_auth-0.16.1
firebase_auth_web-0.1.3+1
firebase_core-0.4.5
firebase_core_web-0.1.1+2
firebase_crashlytics-0.1.4+1
firebase_database-3.1.6
firebase_messaging-6.0.16
flutter_local_notifications-4.0.1+2
flutter_plugin_android_lifecycle-1.0.11
flutter_webview_plugin-0.3.11
fluttertoast-8.0.8
geocoder-0.2.1
geolocator-5.3.2+2
google_api_availability-2.0.4
google_maps_flutter-0.5.33
google_sign_in-4.5.9
google_sign_in_web-0.9.2
location-3.2.4
location_permissions-3.0.0+1
location_web-1.0.1
path_provider-1.6.28
path_provider_linux-0.0.1+2
path_provider_macos-0.0.4+8
path_provider_windows-0.0.5
permission_handler-5.1.0+2
shared_preferences-0.5.12+4
shared_preferences_linux-0.0.2+4
shared_preferences_macos-0.0.1+11
shared_preferences_web-0.1.2+7
shared_preferences_windows-0.0.2+3
sqflite-2.0.0+4
url_launcher-5.7.10
url_launcher_linux-0.0.1+4
url_launcher_macos-0.0.1+9
url_launcher_web-0.1.5+3
url_launcher_windows-0.0.1+3
webview_flutter-2.0.12
Closing this as duplicate of https://github.com/flutter/flutter/issues/47633
|
gharchive/issue
| 2021-09-09T18:28:31 |
2025-04-01T04:34:17.119737
|
{
"authors": [
"darshankawar",
"prabuscs"
],
"repo": "flutter/flutter",
"url": "https://github.com/flutter/flutter/issues/89771",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
1091104334
|
Multiline Textfield List don’t add newline when pressing Enter on Samsung device
I have a problem with multiline Textfield ListView. When i press enter, it dont makes new line, only if typing more characters. How to get newline with pressing enter? The textfield newline by pressing enter works well when widget is alone, not in a listview. Also it works with google's GBoard even in listview.
Steps to Reproduce
I have attached the code below
Runing it on Samsung phone , with default Samsung keyboard
Expected results: the textfield breaks the line when pressing enter
Actual results: when pressing enter , the textfield dont makes new line
Code sample
import 'package:flutter/material.dart';
void main() => runApp(const MyApp());
class MyApp extends StatelessWidget {
const MyApp({Key? key}) : super(key: key);
@override
Widget build(BuildContext context) {
return MaterialApp(
title: 'Flutter Hello World',
theme: ThemeData(
primarySwatch: Colors.blue,
),
home: MyHomePage(),
);
}
}
class MyHomePage extends StatelessWidget {
final List<MultiLineTextField> items;
MyHomePage({Key? key}) :
items = List<MultiLineTextField>.generate(200, (i) =>
MultiLineTextField(hint:'Text1 $i')),
super(key: key);
@override
Widget build(BuildContext context) {
return Scaffold(
appBar: AppBar(
title: const Text('title'),
),
body: Column(
children: [
const MultiLineTextField(hint: 'text'),
Expanded(
child: ListView.builder(
itemCount: 100,
itemBuilder: (context, index) {
final item = items[index];
return ListTile(
title: item.build(context),
);
},
),
),
],
),
);
}
}
class MultiLineTextField extends StatelessWidget {
const MultiLineTextField({Key? key,required this.hint}):super(key: key);
final String hint;
@override
Widget build(BuildContext context) {
return const TextField(
keyboardType: TextInputType.multiline,
maxLines: null,
textInputAction: TextInputAction.newline,
decoration: InputDecoration(
hintText: 'text',
fillColor: Colors.red,
),
);
}
}
Logs
flutter run --verbose
[ +65 ms] executing: [C:\Flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[ +436 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[ +1 ms] 18116933e77adc82f80866c928266a5b4f1ed645
[ ] executing: [C:\Flutter/] git tag --points-at 18116933e77adc82f80866c928266a5b4f1ed645
[ +44 ms] Exit code 0 from: git tag --points-at 18116933e77adc82f80866c928266a5b4f1ed645
[ ] 2.5.3
[ +8 ms] executing: [C:\Flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[ +35 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[ ] origin/stable
[ ] executing: [C:\Flutter/] git ls-remote --get-url origin
[ +29 ms] Exit code 0 from: git ls-remote --get-url origin
[ ] https://github.com/flutter/flutter.git
[ +96 ms] executing: [C:\Flutter/] git rev-parse --abbrev-ref HEAD
[ +32 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[ ] stable
[ +64 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[ ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[ ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[ ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[ +3 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[ ] Artifact Instance of 'WindowsUwpEngineArtifacts' is not required, skipping update.
[ ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[ ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[ ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[ ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[ ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[ ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[ +50 ms] executing: C:\Users\vikto\AppData\Local\Android\sdk\platform-tools\adb.exe devices -l
[ +40 ms] List of devices attached
R5CR8012KLY device product:p3sxeea model:SM_G998B device:p3s transport_id:1
[ +5 ms] C:\Users\vikto\AppData\Local\Android\sdk\platform-tools\adb.exe -s R5CR8012KLY shell getprop
[ +59 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[ ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[ +3 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[ +1 ms] Artifact Instance of 'WindowsUwpEngineArtifacts' is not required, skipping update.
[ ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[ ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[ ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[ ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[ ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[ ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[ +73 ms] Skipping pub get: version match.
[ +95 ms] Generating C:\Users\vikto\Desktop\flutter_app\android\app\src\main\java\io\flutter\plugins\GeneratedPluginRegistrant.java
[ +48 ms] ro.hardware = exynos2100
[ ] ro.build.characteristics = phone
[ +30 ms] Initializing file store
[ +9 ms] Skipping target: gen_localizations
[ +6 ms] Skipping target: gen_dart_plugin_registrant
[ +1 ms] Skipping target: _composite
[ +2 ms] complete
[ +6 ms] Launching lib\main.dart on SM G998B in debug mode...
[ +5 ms] C:\Flutter\bin\cache\dart-sdk\bin\dart.exe --disable-dart-dev C:\Flutter\bin\cache\artifacts\engine\windows-x64\frontend_server.dart.snapshot --sdk-root
C:\Flutter\bin\cache\artifacts\engine\common\flutter_patched_sdk/ --incremental --target=flutter --debugger-module-names --experimental-emit-debug-metadata -DFLUTTER_WEB_AUTO_DETECT=true
--output-dill C:\Users\vikto\AppData\Local\Temp\flutter_tools.b6424904\flutter_tool.efe933c3\app.dill --packages C:\Users\vikto\Desktop\flutter_app.dart_tool\package_config.json
-Ddart.vm.profile=false -Ddart.vm.product=false --enable-asserts --track-widget-creation --filesystem-scheme org-dartlang-root --initialize-from-dill
build\c075001b96339384a97db4862b8ab8db.cache.dill.track.dill --enable-experiment=alternative-invalidation-strategy
[ +10 ms] executing: C:\Users\vikto\AppData\Local\Android\sdk\build-tools\30.0.3\aapt dump xmltree C:\Users\vikto\Desktop\flutter_app\build\app\outputs\flutter-apk\app.apk AndroidManifest.xml
[ +11 ms] Exit code 0 from: C:\Users\vikto\AppData\Local\Android\sdk\build-tools\30.0.3\aapt dump xmltree C:\Users\vikto\Desktop\flutter_app\build\app\outputs\flutter-apk\app.apk
AndroidManifest.xml
[ ] N: android=http://schemas.android.com/apk/res/android
E: manifest (line=2)
A: android:versionCode(0x0101021b)=(type 0x10)0x1
A: android:versionName(0x0101021c)="1.0.0" (Raw: "1.0.0")
A: android:compileSdkVersion(0x01010572)=(type 0x10)0x1e
A: android:compileSdkVersionCodename(0x01010573)="11" (Raw: "11")
A: package="com.example.flutter_app" (Raw: "com.example.flutter_app")
A: platformBuildVersionCode=(type 0x10)0x1e
A: platformBuildVersionName=(type 0x10)0xb
E: uses-sdk (line=7)
A: android:minSdkVersion(0x0101020c)=(type 0x10)0x10
A: android:targetSdkVersion(0x01010270)=(type 0x10)0x1e
E: uses-permission (line=14)
A: android:name(0x01010003)="android.permission.INTERNET" (Raw: "android.permission.INTERNET")
E: application (line=16)
A: android:label(0x01010001)="flutter_app" (Raw: "flutter_app")
A: android:icon(0x01010002)=@0x7f080000
A: android:debuggable(0x0101000f)=(type 0x12)0xffffffff
A: android:appComponentFactory(0x0101057a)="androidx.core.app.CoreComponentFactory" (Raw: "androidx.core.app.CoreComponentFactory")
E: activity (line=21)
A: android:theme(0x01010000)=@0x7f0a0000
A: android:name(0x01010003)="com.example.flutter_app.MainActivity" (Raw: "com.example.flutter_app.MainActivity")
A: android:launchMode(0x0101001d)=(type 0x10)0x1
A: android:configChanges(0x0101001f)=(type 0x11)0x40003fb4
A: android:windowSoftInputMode(0x0101022b)=(type 0x11)0x10
A: android:hardwareAccelerated(0x010102d3)=(type 0x12)0xffffffff
E: meta-data (line=35)
A: android:name(0x01010003)="io.flutter.embedding.android.NormalTheme" (Raw: "io.flutter.embedding.android.NormalTheme")
A: android:resource(0x01010025)=@0x7f0a0001
E: meta-data (line=45)
A: android:name(0x01010003)="io.flutter.embedding.android.SplashScreenDrawable" (Raw: "io.flutter.embedding.android.SplashScreenDrawable")
A: android:resource(0x01010025)=@0x7f040000
E: intent-filter (line=49)
E: action (line=50)
A: android:name(0x01010003)="android.intent.action.MAIN" (Raw: "android.intent.action.MAIN")
E: category (line=52)
A: android:name(0x01010003)="android.intent.category.LAUNCHER" (Raw: "android.intent.category.LAUNCHER")
E: meta-data (line=59)
A: android:name(0x01010003)="flutterEmbedding" (Raw: "flutterEmbedding")
A: android:value(0x01010024)=(type 0x10)0x2
[ +6 ms] executing: C:\Users\vikto\AppData\Local\Android\sdk\platform-tools\adb.exe -s R5CR8012KLY shell -x logcat -v time -t 1
[ +11 ms] <- compile package:flutter_app/main.dart
[ +420 ms] --------- beginning of main
12-30 14:02:48.942 I/heimdall( 1006): update_proc_tgid:436, put logcat(10365) in root memcg
[ +8 ms] executing: C:\Users\vikto\AppData\Local\Android\sdk\platform-tools\adb.exe version
[ +18 ms] Android Debug Bridge version 1.0.41
Version 31.0.3-7562133
Installed as C:\Users\vikto\AppData\Local\Android\sdk\platform-tools\adb.exe
[ +2 ms] executing: C:\Users\vikto\AppData\Local\Android\sdk\platform-tools\adb.exe start-server
[ +21 ms] Building APK
[ +16 ms] Running Gradle task 'assembleDebug'...
[ +4 ms] Using gradle from C:\Users\vikto\Desktop\flutter_app\android\gradlew.bat.
[ +13 ms] executing: C:\Program Files\Android\Android Studio\jre\bin\java -version
[ +142 ms] Exit code 0 from: C:\Program Files\Android\Android Studio\jre\bin\java -version
[ ] openjdk version "11.0.10" 2021-01-19
OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
OpenJDK 64-Bit Server VM (build 11.0.10+0-b96-7249189, mixed mode)
[ +1 ms] executing: C:\Program Files\Android\Android Studio\jre\bin\java -version
[ +138 ms] Exit code 0 from: C:\Program Files\Android\Android Studio\jre\bin\java -version
[ +1 ms] openjdk version "11.0.10" 2021-01-19
OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
OpenJDK 64-Bit Server VM (build 11.0.10+0-b96-7249189, mixed mode)
[ +2 ms] executing: [C:\Users\vikto\Desktop\flutter_app\android/] C:\Users\vikto\Desktop\flutter_app\android\gradlew.bat -Pverbose=true -Ptarget-platform=android-arm64
-Ptarget=C:\Users\vikto\Desktop\flutter_app\lib\main.dart -Pdart-defines=RkxVVFRFUl9XRUJfQVVUT19ERVRFQ1Q9dHJ1ZQ== -Pdart-obfuscation=false -Ptrack-widget-creation=true -Ptree-shake-icons=false
-Pfilesystem-scheme=org-dartlang-root assembleDebug
[+1525 ms] > Task :app:compileFlutterBuildDebug UP-TO-DATE
[ +1 ms] > Task :app:packLibsflutterBuildDebug UP-TO-DATE
[ ] > Task :app:preBuild UP-TO-DATE
[ ] > Task :app:preDebugBuild UP-TO-DATE
[ ] > Task :app:compileDebugAidl NO-SOURCE
[ ] > Task :app:compileDebugRenderscript NO-SOURCE
[ ] > Task :app:generateDebugBuildConfig UP-TO-DATE
[ ] > Task :app:checkDebugAarMetadata UP-TO-DATE
[ ] > Task :app:cleanMergeDebugAssets
[ ] > Task :app:mergeDebugShaders UP-TO-DATE
[ ] > Task :app:compileDebugShaders NO-SOURCE
[ ] > Task :app:generateDebugAssets UP-TO-DATE
[ ] > Task :app:mergeDebugAssets
[ +287 ms] > Task :app:copyFlutterAssetsDebug
[ +1 ms] > Task :app:generateDebugResValues UP-TO-DATE
[ ] > Task :app:generateDebugResources UP-TO-DATE
[ ] > Task :app:mergeDebugResources UP-TO-DATE
[ ] > Task :app:createDebugCompatibleScreenManifests UP-TO-DATE
[ ] > Task :app:extractDeepLinksDebug UP-TO-DATE
[ ] > Task :app:processDebugMainManifest UP-TO-DATE
[ ] > Task :app:processDebugManifest UP-TO-DATE
[ ] > Task :app:processDebugManifestForPackage UP-TO-DATE
[ ] > Task :app:processDebugResources UP-TO-DATE
[ +87 ms] > Task :app:compileDebugKotlin UP-TO-DATE
[ +1 ms] > Task :app:javaPreCompileDebug UP-TO-DATE
[ ] > Task :app:compileDebugJavaWithJavac UP-TO-DATE
[ ] > Task :app:compileDebugSources UP-TO-DATE
[ ] > Task :app:mergeDebugNativeDebugMetadata NO-SOURCE
[ ] > Task :app:compressDebugAssets UP-TO-DATE
[ ] > Task :app:processDebugJavaRes NO-SOURCE
[ ] > Task :app:mergeDebugJavaResource UP-TO-DATE
[ ] > Task :app:checkDebugDuplicateClasses UP-TO-DATE
[ ] > Task :app:dexBuilderDebug UP-TO-DATE
[ ] > Task :app:desugarDebugFileDependencies UP-TO-DATE
[ ] > Task :app:mergeExtDexDebug UP-TO-DATE
[ ] > Task :app:mergeDexDebug UP-TO-DATE
[ ] > Task :app:mergeDebugJniLibFolders UP-TO-DATE
[ ] > Task :app:mergeDebugNativeLibs UP-TO-DATE
[ ] > Task :app:stripDebugDebugSymbols UP-TO-DATE
[ ] > Task :app:validateSigningDebug UP-TO-DATE
[ +100 ms] > Task :app:packageDebug UP-TO-DATE
[ +181 ms] > Task :app:assembleDebug
[ +1 ms] Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
[ ] Use '--warning-mode all' to show the individual deprecation warnings.
[ ] See https://docs.gradle.org/6.7/userguide/command_line_interface.html#sec:command_line_warnings
[ ] BUILD SUCCESSFUL in 2s
[ ] 32 actionable tasks: 4 executed, 28 up-to-date
[ +535 ms] Running Gradle task 'assembleDebug'... (completed in 3,0s)
[ +38 ms] calculateSha: LocalDirectory: 'C:\Users\vikto\Desktop\flutter_app\build\app\outputs\flutter-apk'/app.apk
[ +697 ms] √ Built build\app\outputs\flutter-apk\app-debug.apk.
[ +3 ms] executing: C:\Users\vikto\AppData\Local\Android\sdk\build-tools\30.0.3\aapt dump xmltree C:\Users\vikto\Desktop\flutter_app\build\app\outputs\flutter-apk\app.apk AndroidManifest.xml
[ +15 ms] Exit code 0 from: C:\Users\vikto\AppData\Local\Android\sdk\build-tools\30.0.3\aapt dump xmltree C:\Users\vikto\Desktop\flutter_app\build\app\outputs\flutter-apk\app.apk
AndroidManifest.xml
[ +1 ms] N: android=http://schemas.android.com/apk/res/android
E: manifest (line=2)
A: android:versionCode(0x0101021b)=(type 0x10)0x1
A: android:versionName(0x0101021c)="1.0.0" (Raw: "1.0.0")
A: android:compileSdkVersion(0x01010572)=(type 0x10)0x1e
A: android:compileSdkVersionCodename(0x01010573)="11" (Raw: "11")
A: package="com.example.flutter_app" (Raw: "com.example.flutter_app")
A: platformBuildVersionCode=(type 0x10)0x1e
A: platformBuildVersionName=(type 0x10)0xb
E: uses-sdk (line=7)
A: android:minSdkVersion(0x0101020c)=(type 0x10)0x10
A: android:targetSdkVersion(0x01010270)=(type 0x10)0x1e
E: uses-permission (line=14)
A: android:name(0x01010003)="android.permission.INTERNET" (Raw: "android.permission.INTERNET")
E: application (line=16)
A: android:label(0x01010001)="flutter_app" (Raw: "flutter_app")
A: android:icon(0x01010002)=@0x7f080000
A: android:debuggable(0x0101000f)=(type 0x12)0xffffffff
A: android:appComponentFactory(0x0101057a)="androidx.core.app.CoreComponentFactory" (Raw: "androidx.core.app.CoreComponentFactory")
E: activity (line=21)
A: android:theme(0x01010000)=@0x7f0a0000
A: android:name(0x01010003)="com.example.flutter_app.MainActivity" (Raw: "com.example.flutter_app.MainActivity")
A: android:launchMode(0x0101001d)=(type 0x10)0x1
A: android:configChanges(0x0101001f)=(type 0x11)0x40003fb4
A: android:windowSoftInputMode(0x0101022b)=(type 0x11)0x10
A: android:hardwareAccelerated(0x010102d3)=(type 0x12)0xffffffff
E: meta-data (line=35)
A: android:name(0x01010003)="io.flutter.embedding.android.NormalTheme" (Raw: "io.flutter.embedding.android.NormalTheme")
A: android:resource(0x01010025)=@0x7f0a0001
E: meta-data (line=45)
A: android:name(0x01010003)="io.flutter.embedding.android.SplashScreenDrawable" (Raw: "io.flutter.embedding.android.SplashScreenDrawable")
A: android:resource(0x01010025)=@0x7f040000
E: intent-filter (line=49)
E: action (line=50)
A: android:name(0x01010003)="android.intent.action.MAIN" (Raw: "android.intent.action.MAIN")
E: category (line=52)
A: android:name(0x01010003)="android.intent.category.LAUNCHER" (Raw: "android.intent.category.LAUNCHER")
E: meta-data (line=59)
A: android:name(0x01010003)="flutterEmbedding" (Raw: "flutterEmbedding")
A: android:value(0x01010024)=(type 0x10)0x2
[ +3 ms] Stopping app 'app.apk' on SM G998B.
[ ] executing: C:\Users\vikto\AppData\Local\Android\sdk\platform-tools\adb.exe -s R5CR8012KLY shell am force-stop com.example.flutter_app
[ +121 ms] executing: C:\Users\vikto\AppData\Local\Android\sdk\platform-tools\adb.exe -s R5CR8012KLY shell pm list packages com.example.flutter_app
[ +79 ms] package:com.example.flutter_app
[ +1 ms] executing: C:\Users\vikto\AppData\Local\Android\sdk\platform-tools\adb.exe -s R5CR8012KLY shell cat /data/local/tmp/sky.com.example.flutter_app.sha1
[ +29 ms] b249d0772ae879c6f55aa353a15e409fa1b7c573
[ +1 ms] Latest build already installed.
[ ] executing: C:\Users\vikto\AppData\Local\Android\sdk\platform-tools\adb.exe -s R5CR8012KLY shell -x logcat -v time -t 1
[ +296 ms] --------- beginning of main
12-30 14:02:53.466 I/heimdall( 1006): update_proc_tgid:436, put logcat(10393) in root memcg
[ +6 ms] executing: C:\Users\vikto\AppData\Local\Android\sdk\platform-tools\adb.exe -s R5CR8012KLY shell am start -a android.intent.action.RUN -f 0x20000000 --ez enable-background-compilation
true --ez enable-dart-profiling true --ez enable-checked-mode true --ez verify-entry-points true com.example.flutter_app/com.example.flutter_app.MainActivity
[ +68 ms] Starting: Intent { act=android.intent.action.RUN flg=0x20000000 cmp=com.example.flutter_app/.MainActivity (has extras) }
[ +1 ms] Waiting for observatory port to be available...
[ +160 ms] W/FlutterActivityAndFragmentDelegate(10415): A splash screen was provided to Flutter, but this is deprecated. See flutter.dev/go/android-splash-migration for migration steps.
[ +44 ms] Observatory URL on device: http://127.0.0.1:37693/-fAUnjMJQS4=/
[ +1 ms] executing: C:\Users\vikto\AppData\Local\Android\sdk\platform-tools\adb.exe -s R5CR8012KLY forward tcp:0 tcp:37693
[ +19 ms] 59123
[ ] Forwarded host port 59123 to device port 37693 for Observatory
[ +4 ms] Caching compiled dill
[ +21 ms] Connecting to service protocol: http://127.0.0.1:59123/-fAUnjMJQS4=/
[ +107 ms] Launching a Dart Developer Service (DDS) instance at http://127.0.0.1:0, connecting to VM service at http://127.0.0.1:59123/-fAUnjMJQS4=/.
[ +101 ms] DDS is listening at http://127.0.0.1:59126/C2eObEWCO3s=/.
[ +45 ms] Successfully connected to service protocol: http://127.0.0.1:59123/-fAUnjMJQS4=/
[ +44 ms] DevFS: Creating new filesystem on the device (null)
[ +17 ms] DevFS: Created new filesystem on the device (file:///data/user/0/com.example.flutter_app/code_cache/flutter_appMXLOIU/flutter_app/)
[ +2 ms] Updating assets
[ +64 ms] Syncing files to device SM G998B...
[ +1 ms] <- reset
[ ] Compiling dart to kernel with 0 updated files
[ +2 ms] <- recompile package:flutter_app/main.dart f930b4dd-aaa4-4aa7-a269-d9bedaea0190
[ ] <- f930b4dd-aaa4-4aa7-a269-d9bedaea0190
[ +50 ms] Updating files.
[ ] DevFS: Sync finished
[ +1 ms] Syncing files to device SM G998B... (completed in 56ms)
[ ] Synced 0.0MB.
[ +1 ms] <- accept
[ +4 ms] Connected to _flutterView/0xb400007b613d6f80.
[ +2 ms] Flutter run key commands.
[ +1 ms] r Hot reload.
[ ] R Hot restart.
[ ] h List all available interactive commands.
[ ] d Detach (terminate "flutter run" but leave application running).
[ ] c Clear the screen
[ ] q Quit (terminate the application on the device).
[ ] Running with sound null safety
[ +1 ms] An Observatory debugger and profiler on SM G998B is available at: http://127.0.0.1:59126/C2eObEWCO3s=/
[ +266 ms] DevTools activation throttled until 2021-12-31 01:20:39.702036.
[ +453 ms] The Flutter DevTools debugger and profiler on SM G998B is available at: http://127.0.0.1:9101?uri=http://127.0.0.1:59126/C2eObEWCO3s=/
------tapping on standalone textfield
[+36903 ms] I/ViewRootImpl@8003e81MainActivity: ViewPostIme pointer 0
[ +48 ms] I/ViewRootImpl@8003e81MainActivity: ViewPostIme pointer 1
[ +29 ms] I/IMM_LC (10415): ssi() - flag : 0 view : com.example.flutter_app reason = SHOW_SOFT_INPUT
[ +1 ms] I/IMM_LC (10415): ssi() view is not EditText
[ +1 ms] D/InputMethodManager(10415): startInputInner - Id : 0
[ ] I/InputMethodManager(10415): startInputInner - mService.startInputOrWindowGainedFocus
[ +6 ms] D/InputMethodManager(10415): startInputInner - Id : 0
[ +1 ms] I/InputMethodManager(10415): startInputInner - mService.startInputOrWindowGainedFocus
[ +7 ms] W/IInputConnectionWrapper(10415): getCursorCapsMode on inactive InputConnection
[ +3 ms] W/IInputConnectionWrapper(10415): getExtractedText on inactive InputConnection
[ +1 ms] W/IInputConnectionWrapper(10415): requestCursorAnchorInfo on inactive InputConnection
[ +16 ms] W/IInputConnectionWrapper(10415): getExtractedText on inactive InputConnection
[ +18 ms] D/InputConnectionAdaptor(10415): The input method toggled cursor monitoring on
[ +29 ms] D/InsetsController(10415): show(ime(), fromIme=true)
[ +4 ms] D/InsetsSourceConsumer(10415): setRequestedVisible: visible=true, type=19, host=com.example.flutter_app/com.example.flutter_app.MainActivity,
from=android.view.InsetsSourceConsumer.show:235 android.view.InsetsController.showDirectly:1488 android.view.InsetsController.controlAnimationUnchecked:1136
android.view.InsetsController.applyAnimation:1455 android.view.InsetsController.applyAnimation:1436 android.view.InsetsController.show:975
android.view.ViewRootImpl$ViewRootHandler.handleMessageImpl:6329 android.view.ViewRootImpl$ViewRootHandler.handleMessage:6254 android.os.Handler.dispatchMessage:106 android.os.Looper.loopOnce:226
------enter key creates newline on standalone textfield
[+45931 ms] I/IMM_LC (10415): ssi() - flag : 0 view : com.example.flutter_app reason = SHOW_SOFT_INPUT
[ +1 ms] I/IMM_LC (10415): ssi() view is not EditText
[ +1 ms] D/InsetsController(10415): show(ime(), fromIme=true)
[+35962 ms] I/ViewRootImpl@8003e81MainActivity: ViewPostIme pointer 0
[ +40 ms] I/ViewRootImpl@8003e81MainActivity: ViewPostIme pointer 1
[ +8 ms] I/IMM_LC (10415): ssi() - flag : 0 view : com.example.flutter_app reason = SHOW_SOFT_INPUT
[ +1 ms] I/IMM_LC (10415): ssi() view is not EditText
[ +1 ms] D/InputMethodManager(10415): startInputInner - Id : 0
[ +1 ms] I/InputMethodManager(10415): startInputInner - mService.startInputOrWindowGainedFocus
[ +1 ms] D/InsetsController(10415): show(ime(), fromIme=true)
------pointing on texfield in listview
[ +30 ms] D/InputConnectionAdaptor(10415): The input method toggled cursor monitoring on
[ +8 ms] D/InsetsController(10415): show(ime(), fromIme=true)
[+46539 ms] I/DecorView(10415): [INFO] isPopOver=false, config=true
[ +1 ms] I/DecorView(10415): updateCaptionType >> DecorView@f4e3705[MainActivity], isFloating=false, isApplication=true, hasWindowControllerCallback=true, hasWindowDecorCaption=false
[ ] D/DecorView(10415): setCaptionType = 0, this = DecorView@f4e3705[MainActivity]
[ ] I/MSHandlerLifeCycle(10415): isMultiSplitHandlerRequested: windowingMode=1 isFullscreen=true isPopOver=false isHidden=false skipActivityType=false isHandlerType=true this:
DecorView@f4e3705[MainActivity]
[ ] I/MSHandlerLifeCycle(10415): removeMultiSplitHandler: no exist. decor=DecorView@f4e3705[MainActivity]
[ ] V/ViewRootImpl@8003e81MainActivity: updateAppliedLetterboxDirection, direction=2, Caller=android.view.ViewRootImpl.handleDispatchLetterboxDirectionChanged:12558
[ +43 ms] I/ViewRootImpl@8003e81MainActivity: Relayout returned: old=(0,0,1080,2400) new=(0,0,2325,1080) req=(1080,2400)0 dur=4 res=0x3 s={true -5476376615359329712} ch=false fn=94
[ +1 ms] I/ViewRootImpl@8003e81MainActivity: updateBoundsLayer: t = android.view.SurfaceControl$Transaction@756629d sc = Surface(name=Bounds for -
com.example.flutter_app/com.example.flutter_app.MainActivity@0)/@0x4420312 frame = 94
[ ] I/SurfaceView(10415): updateSurface: mVisible = true mSurface.isValid() = true
[ ] I/SurfaceView(10415): updateSurface: mSurfaceCreated = true surfaceChanged = false visibleChanged = false
[ ] I/SurfaceView(10415): surfaceChanged (2325,1080) 1 #5 io.flutter.embedding.android.FlutterSurfaceView{1315367 V.E...... ......ID 0,0-2325,1080}
[ ] I/ViewRootImpl@8003e81MainActivity: [DP] dp(1) 1 android.view.SurfaceView.updateSurface:1369 android.view.SurfaceView.setFrame:683 android.view.View.layout:24453
[ +1 ms] I/ViewRootImpl@8003e81MainActivity: [DP] pdf(0) 1 android.view.SurfaceView.notifyDrawFinished:607 android.view.SurfaceView.performDrawFinished:594
android.view.SurfaceView.$r8$lambda$st27mCkd9jfJkTrN_P3qIGKX6NY:0
[ ] I/ViewRootImpl@8003e81MainActivity: [DP] rdf()
[ ] I/ViewRootImpl@8003e81MainActivity: [DP] dp(1) 1 android.view.ViewRootImpl.reportNextDraw:11233 android.view.ViewRootImpl.performTraversals:4075
android.view.ViewRootImpl.doTraversal:2819
[ ] D/ViewRootImpl@8003e81MainActivity: Creating frameCompleteCallback mNextDrawUseBlastSync=false mReportNextDraw=true commitCallbacks size=0
[ ] I/View (10415): draw TR bounds[ Rect(2249, 0 - 2325, 76) ] color[ ff000000 ] this - DecorView@f4e3705[MainActivity]
[ ] I/View (10415): draw BR bounds[ Rect(2249, 1004 - 2325, 1080) ] color[ ff000000 ] this - DecorView@f4e3705[MainActivity]
[ ] D/ViewRootImpl@8003e81MainActivity: Received frameCompleteCallback frameNum=94
[ ] I/ViewRootImpl@8003e81MainActivity: [DP] pdf(0) 1 android.view.ViewRootImpl.lambda$createFrameCompleteCallback$3$ViewRootImpl:4833
android.view.ViewRootImpl$$ExternalSyntheticLambda15.run:6 android.os.Handler.handleCallback:938
[ ] I/ViewRootImpl@8003e81MainActivity: [DP] rdf()
[ ] I/ViewRootImpl@8003e81MainActivity: handleResized, msg = 5 frames=ClientWindowFrames{frame=[0,0][2325,1080] display=[0,0][2325,1080] backdrop=[0,0][2325,1080]}
forceNextWindowRelayout=true displayId=0 frameChanged=false backdropFrameChanged=false configChanged=false displayChanged=false mNextDrawUseBlastSync=false mergedConfiguration={mGlobalConfig={1.1
216mcc30mnc [en_US] ldltr sw411dp w885dp h383dp 420dpi nrml long land finger -keyb/v/h -nav/h winConfig={ mBounds=Rect(0, 0 - 2400, 1080) mAppBounds=Rect(0, 0 - 2325, 1080) mMaxBounds=Rect(0, 0 -
2400, 1080) mWindowingMode=fullscreen mDisplayWindowingMode=fullscreen mActivityType=undefined mAlwaysOnTop=undefined mRotation=ROTATION_270 mFreeformTaskPinningState=unpinned} s.567
fontWeightAdjustment=0 ff=0 bf=0 bts=0 desktop/d dm/n dc/d ?dcui ?dcaf enb/d themeSeq=0} mOverrideConfig={1.1 216mcc30mnc [en_US] ldltr sw411dp w885dp h383dp 420dpi nrml long land finger -keyb/v/h
-nav/h winConfig={ mBounds=Rect(0, 0 - 2400, 1080) mAppBounds=Rect(0, 0 - 2325, 1080) mMaxBounds=Rect(0, 0 - 2400, 1080) mWindowingMode=fullscreen mDisplayWindowingMode=fullscreen
mActivityType=standard mAlwaysOnTop=undefined mRotation=ROTATION_270 mFreeformTaskPinningState=unpinned} s.2 fontWeightAdjustment=0 ff=0 bf=0 bts=0 desktop/d dm/n dc/d ?dcui ?dcaf enb/d
themeSeq=0}}
[ +1 ms] I/ViewRootImpl@8003e81MainActivity: [DP] dp(1) 1 android.view.ViewRootImpl.reportNextDraw:11233 android.view.ViewRootImpl.handleResized:2145
android.view.ViewRootImpl.access$1000:290
[ ] I/ViewRootImpl@8003e81MainActivity: Relayout returned: old=(0,0,2325,1080) new=(0,0,2325,1080) req=(2325,1080)0 dur=3 res=0x1 s={true -5476376615359329712} ch=false fn=95
[ ] D/ViewRootImpl@8003e81MainActivity: Creating frameCompleteCallback mNextDrawUseBlastSync=false mReportNextDraw=true commitCallbacks size=0
[ ] D/ViewRootImpl@8003e81MainActivity: Received frameCompleteCallback frameNum=95
[ ] I/ViewRootImpl@8003e81MainActivity: [DP] pdf(0) 1 android.view.ViewRootImpl.lambda$createFrameCompleteCallback$3$ViewRootImpl:4833
android.view.ViewRootImpl$$ExternalSyntheticLambda15.run:6 android.os.Handler.handleCallback:938
[ ] I/ViewRootImpl@8003e81MainActivity: [DP] rdf()
----when pressing enter on textfield no new loggs appear
flutter doctor -v
[√] Flutter (Channel stable, 2.5.3, on Microsoft Windows [Version 10.0.19043.1415], locale hu-HU)
• Flutter version 2.5.3 at C:\Flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 18116933e7 (3 months ago), 2021-10-15 10:46:35 -0700
• Engine revision d3ea636dc5
• Dart version 2.14.4
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
• Android SDK at C:\Users\vikto\AppData\Local\Android\sdk
• Platform android-30, build-tools 30.0.3
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
• All Android licenses accepted.
[√] Chrome - develop for the web
• Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
[√] Android Studio (version 2020.3)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin can be installed from:
https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
[√] VS Code (version 1.62.0)
• VS Code at C:\Users\vikto\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.27.0
[√] VS Code, 32-bit edition (version 1.32.3)
• VS Code at C:\Program Files (x86)\Microsoft VS Code
• Flutter extension version 3.27.0
[√] Connected device (3 available)
• SM G998B (mobile) • R5CR8012KLY • android-arm64 • Android 12 (API 31)
• Chrome (web) • chrome • web-javascript • Google Chrome 96.0.4664.110
• Edge (web) • edge • web-javascript • Microsoft Edge 96.0.1054.62
• No issues found!
<!--
Consider also attaching screenshots and/or videos to better
illustrate the issue.
You can upload them directly on GitHub.
Beware that video file size is limited to 10MB.
--
https://user-images.githubusercontent.com/25665922/147755920-1d742c4d-cb29-4c51-b245-9c42f39e8d2b.mp4
>
https://user-images.githubusercontent.com/25665922/147756035-d4aad833-d402-4190-ab3d-5a2ed7092290.mp4
I have same issue on Samsung phone too.
@visign3d
Can you upgrade to latest stable (2.8.1) and try again to see if you still get same behavior ?
@visign3d Can you upgrade to latest stable (2.8.1) and try again to see if you still get same behavior ?
updated the Flutter SDK with $flutter upgrade. The issue is still there. Still no new line by enter in list of TextFields
@visign3d Can you upgrade to latest stable (2.8.1) and try again to see if you still get same behavior ?
updated the Flutter SDK with $flutter upgrade. The issue is still there. Still no new line by enter in list of TextFields
I tried to add some basic '\n' newline actions with RawKeyboardListener() and it worked.
New line was added . It seems that the enter key is ignored in Flutter TextField() when inside a ListView.
Ok , the problem was , that the TextField was inside a ListTile. When i moved it outside ListTile the new line is working.
|
gharchive/issue
| 2021-12-30T13:25:11 |
2025-04-01T04:34:17.210765
|
{
"authors": [
"darshankawar",
"puetsua",
"visign3d"
],
"repo": "flutter/flutter",
"url": "https://github.com/flutter/flutter/issues/95965",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
1102022371
|
GitLab CI/cd pipeline failed : Cannot invoke method toInteger() on null object in build.gradle
I am trying to run build android build stage on GitLab CI pipeline, and am getting this error :
Build file '/builds/wecraft.tn/projects/xenon/front/mobile/android/app/build.gradle' line: 47
40* What went wrong:
41A problem occurred evaluating project ':app'.
42> Cannot invoke method toInteger() on null object
The error occurred because he couldn't get the mindk version in this line :
minSdkVersion localProperties.getProperty('flutter.minSdkVersion').toInteger()
targetSdkVersion localProperties.getProperty('flutter.targetSdkVersion').toInteger()
The minsdk and targetSdkversion are both declared in localProperties file in new flutter sdk version , the file is declared by default in android's gitignore file . My question
is how do I fix this error without having to push the file , can I declare the mindsdkversion in the ci/cd script ?
here's my current gitlabci file:
image: "cirrusci/flutter:2.8.1"
before_script:
- flutter pub get
stages:
- test # All jobs related for testing such as Unit Test
- build
flutter_test: # Name of the lane
stage: test # type of stage
script:
- flutter test # Run Flutter test
flutter_build_android: #Job name
stage: build # kind of job
before_script:
- flutter packages get
- flutter clean
script:
- flutter build apk
artifacts:
paths:
- build/app/outputs/apk/release/app-release.apk
If anyone knows the solution please do not hesitate to respond thank you so much.
Hi @talbiislam96, Thanks for filing the issue.
It seems like the constants from local.properties are not working. Does it work if you hardcode the minsdkversion?
Closing as a duplicate of https://github.com/flutter/flutter/issues/95533, if you disagree feel free to write in the comments and I will reopen it.
Thank you.
@talbiislam96, Thanks for the info what version of flutter are you using locally? Could you please share the complete error logs of your CI script?
The minsdk and targetSdkversion are both declared in localProperties file in new flutter sdk version , the file is declared by default in android's gitignore file .
If you are using constants from this file I believe this shouldn't be in gitignore and should be pushed to version control.
it doesn't work when I hardcode the minskVersion
From your error It looks like the localProperties are not being read, Did you try hardcoding both minimum and target SDK version?
|
gharchive/issue
| 2022-01-13T16:41:41 |
2025-04-01T04:34:17.217480
|
{
"authors": [
"maheshmnj",
"talbiislam96"
],
"repo": "flutter/flutter",
"url": "https://github.com/flutter/flutter/issues/96605",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
1130763092
|
[Android] Kotlin support library dependency no longer required
At the moment, all Flutter Android Kotlin templates contain a dependency on the Kotlin support library. E.g.:
https://github.com/flutter/flutter/blob/0e2f51dfd04eca2935318389a75e8bc112809342/packages/flutter_tools/templates/app_shared/android-kotlin.tmpl/app/build.gradle.tmpl#L67-L69
Starting from Kotlin 1.4, the Kotlin Gradle plugin adds the dependency on the standard library automatically by default: (ref)
You no longer need to declare a dependency on the stdlib library in any Kotlin Gradle project, including a multiplatform one. The dependency is added by default.
The automatically added standard library will be the same version of the Kotlin Gradle plugin, since they have the same versioning.
For platform-specific source sets, the corresponding platform-specific variant of the library is used, while a common standard library is added to the rest. The Kotlin Gradle plugin will select the appropriate JVM standard library depending on the kotlinOptions.jvmTarget compiler option of your Gradle build script.
The current Kotlin version in the templates is 1.6.10:
https://github.com/flutter/flutter/blob/1bfb7400c8ce546fd19ffd93b458ded583d9ada5/packages/flutter_tools/lib/src/android/gradle_utils.dart#L32
So the explicit dependency to the Kotlin support library dependency is no longer required.
Hi @davidmigloz I get crashes with or without the Kotlin references https://github.com/flutter/flutter/issues/98223#issuecomment-1040338050
|
gharchive/issue
| 2022-02-10T19:31:00 |
2025-04-01T04:34:17.221666
|
{
"authors": [
"andesappal",
"davidmigloz"
],
"repo": "flutter/flutter",
"url": "https://github.com/flutter/flutter/issues/98212",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
1375234946
|
Tnd.master
Replace this paragraph with a description of what this PR is changing or adding, and why. Consider including before/after screenshots.
List which issues are fixed by this PR. You must list at least one issue.
If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.
Pre-launch Checklist
[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.
If you need help, consider asking for advice on the #hackers-new channel on Discord.
Hello! It looks like this PR was opened by mistake. If that's not the case, please update the PR description to give more context and reopen it. In the meantime I am going to close this PR. Thanks!
|
gharchive/pull-request
| 2022-09-16T00:19:02 |
2025-04-01T04:34:17.228256
|
{
"authors": [
"goderbauer",
"tankistko"
],
"repo": "flutter/flutter",
"url": "https://github.com/flutter/flutter/pull/111710",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
1466798412
|
Roll Flutter Engine from 7665ae51846f to 8f3cd0f5f7a3 (19 revisions)
https://github.com/flutter/engine/compare/7665ae51846f...8f3cd0f5f7a3
2022-11-28 skia-flutter-autoroll@skia.org Roll Skia from 556e08aa5354 to 3ab92e777da1 (1 revision) (flutter/engine#37936)
2022-11-28 zanderso@users.noreply.github.com Revert Dart to 2.19.0-431.0.dev (flutter/engine#37934)
2022-11-28 skia-flutter-autoroll@skia.org Roll Skia from 9d3726a26123 to 556e08aa5354 (1 revision) (flutter/engine#37933)
2022-11-28 skia-flutter-autoroll@skia.org Roll Fuchsia Mac SDK from 7hM0w3gBLnY1eZM2G... to CUPWWG1rEmonxuLpv... (flutter/engine#37932)
2022-11-28 skia-flutter-autoroll@skia.org Roll Skia from f0a2e2a08ee7 to 9d3726a26123 (2 revisions) (flutter/engine#37929)
2022-11-28 skia-flutter-autoroll@skia.org Roll Skia from 79f890c4ba92 to f0a2e2a08ee7 (1 revision) (flutter/engine#37928)
2022-11-27 skia-flutter-autoroll@skia.org Roll Fuchsia Mac SDK from vt3S3a_dnaqNTkO0x... to 7hM0w3gBLnY1eZM2G... (flutter/engine#37922)
2022-11-27 skia-flutter-autoroll@skia.org Roll Skia from 2618d380def4 to 79f890c4ba92 (1 revision) (flutter/engine#37921)
2022-11-27 skia-flutter-autoroll@skia.org Roll Dart SDK from 4851720b30d2 to 3ed1fc1c344d (1 revision) (flutter/engine#37920)
2022-11-27 skia-flutter-autoroll@skia.org Roll Fuchsia Mac SDK from E3Fd0hvwiXVfn7egS... to vt3S3a_dnaqNTkO0x... (flutter/engine#37917)
2022-11-26 skia-flutter-autoroll@skia.org Roll Fuchsia Mac SDK from lYAPXiPJ9RcPGLUqb... to E3Fd0hvwiXVfn7egS... (flutter/engine#37915)
2022-11-26 skia-flutter-autoroll@skia.org Roll Dart SDK from ae4b643d2a4b to 4851720b30d2 (1 revision) (flutter/engine#37914)
2022-11-25 skia-flutter-autoroll@skia.org Roll Fuchsia Mac SDK from ejjE2o60iiA3_agab... to lYAPXiPJ9RcPGLUqb... (flutter/engine#37911)
2022-11-25 skia-flutter-autoroll@skia.org Roll Dart SDK from eb65e5cd48e9 to ae4b643d2a4b (1 revision) (flutter/engine#37910)
2022-11-25 skia-flutter-autoroll@skia.org Roll Dart SDK from ae7042bf53ff to eb65e5cd48e9 (1 revision) (flutter/engine#37909)
2022-11-25 skia-flutter-autoroll@skia.org Roll Skia from a01af64f5cec to 2618d380def4 (4 revisions) (flutter/engine#37907)
2022-11-25 skia-flutter-autoroll@skia.org Roll Fuchsia Mac SDK from NvafPMjJLQ0fBSSAc... to ejjE2o60iiA3_agab... (flutter/engine#37906)
2022-11-25 skia-flutter-autoroll@skia.org Roll Dart SDK from 962cd6e0d20a to ae7042bf53ff (1 revision) (flutter/engine#37904)
2022-11-25 skia-flutter-autoroll@skia.org Roll Dart SDK from eddf73d66119 to 962cd6e0d20a (1 revision) (flutter/engine#37900)
Also rolling transitive DEPS:
fuchsia/sdk/core/mac-amd64 from NvafPMjJLQ0f to CUPWWG1rEmon
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC kaushikiska@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Commit queue failed; closing this roll.
|
gharchive/pull-request
| 2022-11-28T17:21:29 |
2025-04-01T04:34:17.242919
|
{
"authors": [
"engine-flutter-autoroll"
],
"repo": "flutter/flutter",
"url": "https://github.com/flutter/flutter/pull/116119",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
1601391732
|
Roll Flutter Engine from 4bba1b958e11 to 0591c9f4813b (1 revision)
https://github.com/flutter/engine/compare/4bba1b958e11...0591c9f4813b
2023-02-27 skia-flutter-autoroll@skia.org Roll Dart SDK from 046c78d307d7 to 6095d12c274b (1 revision) (flutter/engine#39911)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC chinmaygarde@google.com,rmistry@google.com,zra@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Commit queue failed; closing this roll.
|
gharchive/pull-request
| 2023-02-27T15:16:37 |
2025-04-01T04:34:17.247869
|
{
"authors": [
"engine-flutter-autoroll"
],
"repo": "flutter/flutter",
"url": "https://github.com/flutter/flutter/pull/121526",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
1724386541
|
Change useMaterial3 default to true
Not for review. This is just a smoke test. Many test failures are expected.
Currently all of the tests in packages/flutter/test are expected to pass except for the tests in packages/flutter/test/material.
Golden file changes have been found for this pull request. Click here to view and triage (e.g. because this is an intentional change).
If you are still iterating on this change and are not ready to resolve the images on the Flutter Gold dashboard, consider marking this PR as a draft pull request above. You will still be able to view image results on the dashboard, commenting will be silenced, and the check will not try to resolve itself until marked ready for review.
For more guidance, visit Writing a golden file test for package:flutter.
Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.
Changes reported for pull request #127501 at sha af56960
I think I forgot to update golden tests🥲. Creating another PR to test that. Will also take a look at the failed tests in web_canvas_tests_2 and web_canvas_tests_3.
|
gharchive/pull-request
| 2023-05-24T16:39:59 |
2025-04-01T04:34:17.251963
|
{
"authors": [
"HansMuller",
"QuncCccccc"
],
"repo": "flutter/flutter",
"url": "https://github.com/flutter/flutter/pull/127501",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
1770427482
|
Updated TextMagnifierExampleApp to M3
This change is part of "step 3" in https://github.com/flutter/flutter/issues/127064.
Updated the TextMagnifierExampleApp to use Material3.
There's a golden image that should be updated as part of this PR. I'm assuming that eventually the presubmit will ask me to approve the new golden image.
So I would have expected the API docs tests to have run and there would be an image at https://flutter-gold.skia.org/changelists in spite of the bot, but there is none. It looks like the API docs tests just did not run for this PR (filed https://github.com/flutter/flutter/issues/129390), in addition to the bot not noticing this was a PR that should be checked for golden file images (filed https://github.com/flutter/flutter/issues/129389).
So much discovery for one tiny PR! 🕵️
Issues in last comment should be resolved by https://github.com/flutter/flutter/pull/129433 and https://github.com/flutter/cocoon/pull/2860
Once those land and deploy, a rebase here should have this all fixed up. :)
Once those land and deploy, a rebase here should have this all fixed up. :)
All is well. The golden image change was offered up and triaged by yours truly. Thanks for the quick fix!
|
gharchive/pull-request
| 2023-06-22T21:36:46 |
2025-04-01T04:34:17.256276
|
{
"authors": [
"HansMuller",
"Piinks"
],
"repo": "flutter/flutter",
"url": "https://github.com/flutter/flutter/pull/129381",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
1977478180
|
[benchmarks] disable partial repaint in iOS macrobenchmarks.
Partial repaint is too effective, and we'd like to be able to measure performance without carefully structuring the benchmarks. For example, right now partial repaint is culling any blurs in the multibackdrop case, which we should be using to track https://github.com/flutter/flutter/issues/132735
This will allow https://github.com/flutter/engine/pull/47688 to improve a benchmark
Presumably, partial repaint has performance benefits in the rest of the benchmarks
🤔 Let me double check that
I've updated this PR so that partial repaint is only disabled for the backdrop blur case I want to measure.
|
gharchive/pull-request
| 2023-11-04T19:30:13 |
2025-04-01T04:34:17.258755
|
{
"authors": [
"jonahwilliams"
],
"repo": "flutter/flutter",
"url": "https://github.com/flutter/flutter/pull/137902",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
351452344
|
Roll engine 4ee648914f91..6381bea25a5e (5 commits)
https://github.com/flutter/engine/compare/4ee648914f91...6381bea25a5e
git log 4ee648914f91..6381bea25a5e --date=short --no-merges --format='%%ad %%ae %%s'
2018-08-16 37626415+skia-flutter-autoroll@users.noreply.github.com Roll src/third_party/skia e21f0ec04e98..bc414ed5dec5 (2 commits) (flutter/engine#6037)
2018-08-16 jamesderlin@users.noreply.github.com Fix potential null pointer dereference in FlutterDartProject (flutter/engine#6035)
2018-08-16 37626415+skia-flutter-autoroll@users.noreply.github.com Roll src/third_party/skia 8d77d1d85e2f..e21f0ec04e98 (5 commits) (flutter/engine#6036)
2018-08-16 37626415+skia-flutter-autoroll@users.noreply.github.com Roll src/third_party/skia cbb7d572aaa1..8d77d1d85e2f (12 commits) (flutter/engine#6034)
2018-08-16 37626415+skia-flutter-autoroll@users.noreply.github.com Roll src/third_party/skia cbd83bbd77d1..cbb7d572aaa1 (5 commits) (flutter/engine#6033)
The AutoRoll server is located here: https://flutter-engine-flutter-roll.skia.org
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.
Trybots failed. These were the failed builds: https://flutter-dashboard.appspot.com/build.html
Commit queue failed; closing this roll.
|
gharchive/pull-request
| 2018-08-17T04:24:09 |
2025-04-01T04:34:17.264311
|
{
"authors": [
"engine-flutter-autoroll"
],
"repo": "flutter/flutter",
"url": "https://github.com/flutter/flutter/pull/20729",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
406463644
|
Make kReleaseMode, kDebugMode, and kProfileMode constants that are public.
Before this, we had several places where an isReleaseMode was defined, all with the same definition. This just makes it more broadly visible to allow our users to use it, as well as creating debug and profile versions.
Since this is a const value, this makes it possible for a developer to easily mark blocks that should be tree-shaken out at AOT compile time.
Yeah, I agree. Kinda daunting though.
Actually, it wasn't too bad. I have a devicelab test that will run in all three modes. Now I just need to fix the fact that debug and both dynamic modes don't seem to pick up the -D definitions on the frontend compiler's command line.
Maybe something in here does it? https://github.com/flutter/flutter/blob/master/packages/flutter_tools/gradle/flutter.gradle
Pass or not pass the flag, that is
Good idea @jonahwilliams, but no, that doesn't make any difference, unfortunately.
|
gharchive/pull-request
| 2019-02-04T18:39:11 |
2025-04-01T04:34:17.267386
|
{
"authors": [
"gspencergoog",
"jonahwilliams"
],
"repo": "flutter/flutter",
"url": "https://github.com/flutter/flutter/pull/27502",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
503714373
|
Roll engine 1d62160fdb2f..b785ab902a5e (13 commits)
git@github.com:flutter/engine.git/compare/1d62160fdb2f...b785ab902a5e
git log 1d62160fdb2f..b785ab902a5e --no-merges --oneline
2019-10-06 chinmaygarde@google.com Update buildroot to pull in ubsan updates. (flutter/engine#12821)
2019-10-05 skia-flutter-autoroll@skia.org Roll src/third_party/skia 95edac1c9a4a..4c82a9fc83a5 (13 commits) (flutter/engine#12818)
2019-10-05 chinmaygarde@google.com Enable sanitizer build variants. (flutter/engine#12816)
2019-10-05 katelovett@google.com Revert "Adding Link SemanticsFlag (#12453)" (flutter/engine#12815)
2019-10-04 jason-simmons@users.noreply.github.com Use the x64 host toolchain for x86 target gen_snapshot only on Linux (flutter/engine#12809)
2019-10-04 yjbanov@google.com add option for bulk-updating screenshots; update screenshots (flutter/engine#12797)
2019-10-04 dnfield@google.com unbreak unopt fuchsia (flutter/engine#12805)
2019-10-04 jason-simmons@users.noreply.github.com Build gen_snapshot with a 64-bit host toolchain even if the target platform is 32-bit (flutter/engine#12802)
2019-10-04 dnfield@google.com [flutter_runner] a11y updates, tests! (flutter/engine#12380)
2019-10-04 WATER1350@gmail.com Fix crash in copypixelbuffer (flutter/engine#10326)
2019-10-04 bkonyi@google.com Roll src/third_party/dart d6c6d12ebf..8413a0db0d (2 commits)
2019-10-04 skia-flutter-autoroll@skia.org Roll fuchsia/sdk/core/mac-amd64 from JyZWz... to kwa2O... (flutter/engine#12803)
2019-10-04 katelovett@google.com Adding Link SemanticsFlag (flutter/engine#12453)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC liyuqian@google.com on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
Trybots failed. These were the failed builds: https://cirrus-ci.com/task/4950086999605248 , https://cirrus-ci.com/task/6638936859869184 , https://cirrus-ci.com/task/5513036953026560 , https://cirrus-ci.com/task/4598243278716928
Commit queue failed; closing this roll.
|
gharchive/pull-request
| 2019-10-07T22:01:21 |
2025-04-01T04:34:17.278558
|
{
"authors": [
"engine-flutter-autoroll"
],
"repo": "flutter/flutter",
"url": "https://github.com/flutter/flutter/pull/42161",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
511175270
|
Roll engine f0a2850b356d..88734cc9ef53 (1 commits)
git@github.com:flutter/engine.git/compare/f0a2850b356d...88734cc9ef53
git log f0a2850b356d..88734cc9ef53 --no-merges --oneline
2019-10-23 bkonyi@google.com Roll src/third_party/dart 17ed3cb5b3..cccb9ffb2a (2 commits)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC aaclarke@google.com on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
Auto-roller completed checks. About to merge.
|
gharchive/pull-request
| 2019-10-23T08:53:16 |
2025-04-01T04:34:17.282505
|
{
"authors": [
"engine-flutter-autoroll"
],
"repo": "flutter/flutter",
"url": "https://github.com/flutter/flutter/pull/43330",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
581867693
|
Roll engine b23138c3598e..7880cc75a53e (2 commits)
https://github.com/flutter/engine/compare/b23138c3598e...7880cc75a53e
git log b23138c3598e..7880cc75a53e --first-parent --oneline
2020-03-15 skia-flutter-autoroll@skia.org Roll src/third_party/skia 7e0a7dbd22e0..9a4ac6e86586 (1 commits) (flutter/engine#17163)
2020-03-15 chinmaygarde@google.com Update the Metal backend selection to use iOS 10.0 and A7 as the version floor. (flutter/engine#17162)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC garyq@google.com on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
Commit queue failed; closing this roll.
|
gharchive/pull-request
| 2020-03-15T23:20:29 |
2025-04-01T04:34:17.287777
|
{
"authors": [
"engine-flutter-autoroll"
],
"repo": "flutter/flutter",
"url": "https://github.com/flutter/flutter/pull/52642",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
639762332
|
Revert "Modernize selection menu appearance"
Reverts flutter/flutter#59115
It looks like this change broke android_semantics_integration_test in the device lab.
Maybe relevant: https://github.com/flutter/flutter/blob/master/dev/integration_tests/android_semantics_testing/test_driver/main_test.dart#L89
Landing on red to green the tree.
Thanks, looks like I'll need to update those selectors and reland.
|
gharchive/pull-request
| 2020-06-16T15:23:45 |
2025-04-01T04:34:17.289944
|
{
"authors": [
"justinmc",
"zanderso"
],
"repo": "flutter/flutter",
"url": "https://github.com/flutter/flutter/pull/59561",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
1056871224
|
[flutter_releases] Flutter beta 2.8.0-3.2.pre Framework Cherrypicks
https://github.com/flutter/flutter/pull/93841
Patch was applied to https://github.com/flutter/flutter/pull/93841, closing.
|
gharchive/pull-request
| 2021-11-18T02:43:39 |
2025-04-01T04:34:17.291401
|
{
"authors": [
"jmagman"
],
"repo": "flutter/flutter",
"url": "https://github.com/flutter/flutter/pull/93844",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
534292020
|
Temporarily disable CI on stable Flutter
To enable using new Flutter features closely before a new release we're temporarily disabling CI on stable.
https://github.com/flutter/flutter/issues/46258 for re-enabling.
cc @jmagman this conflicts with https://github.com/flutter/plugins/pull/2357, we need to disable stable ASAP to unblock endorsing web plugins, not sure how close is the other PR to landing I'm ok with waiting for the other PR first (or @jmagman if you can land i#2357 with stable disabled already 😄 ).
cc @collinjackson
LGTM, defer to @jmagman on whether we want to land #2357 first.
Feel free to land this one first, I'm happy to rebase https://github.com/flutter/plugins/pull/2357 once this lands.
|
gharchive/pull-request
| 2019-12-06T22:42:21 |
2025-04-01T04:34:17.305908
|
{
"authors": [
"amirh",
"jmagman"
],
"repo": "flutter/plugins",
"url": "https://github.com/flutter/plugins/pull/2367",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
1216825989
|
Roll Flutter from 1b58a593deac to 0b80f08cf058 (106 revisions)
Roll Flutter from 1b58a593deac to 0b80f08cf058 (106 revisions)
https://github.com/flutter/flutter/compare/1b58a593deac...0b80f08cf058
2022-04-27 engine-flutter-autoroll@skia.org Roll Engine from 5d844aa30fc6 to fcc15947754b (1 revision) (flutter/flutter#102622)
2022-04-27 engine-flutter-autoroll@skia.org Roll Engine from 24471f3cbb33 to 5d844aa30fc6 (1 revision) (flutter/flutter#102619)
2022-04-27 engine-flutter-autoroll@skia.org Roll Engine from 6ac401970df1 to 24471f3cbb33 (3 revisions) (flutter/flutter#102618)
2022-04-27 54558023+keyonghan@users.noreply.github.com Update open sdk version to be version version:11 (flutter/flutter#102610)
2022-04-27 engine-flutter-autoroll@skia.org Roll Engine from 46b0889d13ce to 6ac401970df1 (3 revisions) (flutter/flutter#102612)
2022-04-27 jonahwilliams@google.com Revert "[framework] Reland: use ImageFilter for zoom page transition " (flutter/flutter#102611)
2022-04-26 engine-flutter-autoroll@skia.org Roll Engine from 07584c64bb7b to 46b0889d13ce (1 revision) (flutter/flutter#102606)
2022-04-26 jonahwilliams@google.com [framework] remove usage and deprecate physical model layer (flutter/flutter#102274)
2022-04-26 engine-flutter-autoroll@skia.org Roll Engine from 545a0b4ad107 to 07584c64bb7b (3 revisions) (flutter/flutter#102603)
2022-04-26 engine-flutter-autoroll@skia.org Roll Engine from b30b65a74554 to 545a0b4ad107 (4 revisions) (flutter/flutter#102599)
2022-04-26 goderbauer@google.com Fix docs re: return value of Navigator's restorable methods (flutter/flutter#102595)
2022-04-26 54558023+keyonghan@users.noreply.github.com Enable Mac/android arm64 tests as bringup: true (flutter/flutter#102589)
2022-04-26 zanderso@users.noreply.github.com [flutter_tools] Add entries to HostArtifacts for impellerc, libtessellator (flutter/flutter#102593)
2022-04-26 jason-simmons@users.noreply.github.com Improve efficiency of copying the animation ObserverList in notifyListeners (flutter/flutter#102536)
2022-04-26 engine-flutter-autoroll@skia.org Roll Engine from 3f27923c7e6c to b30b65a74554 (1 revision) (flutter/flutter#102594)
2022-04-26 jonahwilliams@google.com [framework] Reland: use ImageFilter for zoom page transition (flutter/flutter#102552)
2022-04-26 engine-flutter-autoroll@skia.org Roll Engine from d5b381c2e56d to 3f27923c7e6c (2 revisions) (flutter/flutter#102588)
2022-04-26 jonahwilliams@google.com [flutter_tools] remove UWP tooling (flutter/flutter#102174)
2022-04-26 katelovett@google.com Revert "Re-land reverse case for AppBar scrolled under" (flutter/flutter#102580)
2022-04-26 engine-flutter-autoroll@skia.org Roll Engine from 6d60b810d747 to d5b381c2e56d (1 revision) (flutter/flutter#102581)
2022-04-26 jonahwilliams@google.com [framework] allow other RenderObjects to behave like repaint boundaries (flutter/flutter#101952)
2022-04-26 engine-flutter-autoroll@skia.org Roll Plugins from 4ff0157340ea to e55659835427 (1 revision) (flutter/flutter#102576)
2022-04-26 engine-flutter-autoroll@skia.org Roll Engine from cd78221a88ae to 6d60b810d747 (1 revision) (flutter/flutter#102575)
2022-04-26 dnfield@google.com Avoid scheduling a forced frame when there is no child to the renderView (flutter/flutter#102556)
2022-04-26 leroux_bruno@yahoo.fr Fix DraggableScrollableController.animateTo leaks Ticker (flutter/flutter#102504)
2022-04-26 engine-flutter-autoroll@skia.org Roll Engine from 8aace64d19fc to cd78221a88ae (1 revision) (flutter/flutter#102562)
2022-04-26 engine-flutter-autoroll@skia.org Roll Engine from df21738974e3 to 8aace64d19fc (1 revision) (flutter/flutter#102555)
2022-04-26 engine-flutter-autoroll@skia.org Roll Engine from 79152137a94c to df21738974e3 (1 revision) (flutter/flutter#102553)
2022-04-26 engine-flutter-autoroll@skia.org Roll Engine from 4df9cf27052b to 79152137a94c (8 revisions) (flutter/flutter#102551)
2022-04-26 jonahwilliams@google.com add missing benchmark test file fromhttps://github.com/flutter/flutter/pull/102532 (flutter/flutter#102544)
2022-04-26 xubaolin@oppo.com Fix a Slider widget accessibility bug (flutter/flutter#102129)
2022-04-26 jonahwilliams@google.com add benchmark for animated complex opacity (flutter/flutter#102532)
2022-04-26 jonahwilliams@google.com [framework] allow disabling image filter layer (flutter/flutter#102085)
2022-04-25 54558023+keyonghan@users.noreply.github.com Enable M1 mac/ios tests in prod as bringup: false (flutter/flutter#102530)
2022-04-25 engine-flutter-autoroll@skia.org Roll Engine from 5fdfbe3010bb to 4df9cf27052b (1 revision) (flutter/flutter#102529)
2022-04-25 30870216+gaaclarke@users.noreply.github.com Made Directionality forego dependency tracking for better performance. (flutter/flutter#102336)
2022-04-25 49699333+dependabot[bot]@users.noreply.github.com Bump debian from bullseye-20220328-slim to bullseye-20220418-slim in /dev/ci/docker_linux (flutter/flutter#102528)
2022-04-25 engine-flutter-autoroll@skia.org Roll Engine from 0f47c7a68811 to 5fdfbe3010bb (1 revision) (flutter/flutter#102526)
2022-04-25 katelovett@google.com Re-land reverse case for AppBar scrolled under (flutter/flutter#102343)
2022-04-25 engine-flutter-autoroll@skia.org Roll Engine from f1bb8f421135 to 0f47c7a68811 (1 revision) (flutter/flutter#102523)
2022-04-25 engine-flutter-autoroll@skia.org Roll Engine from c4184728a9ad to f1bb8f421135 (1 revision) (flutter/flutter#102519)
2022-04-25 engine-flutter-autoroll@skia.org Roll Engine from 966812846313 to c4184728a9ad (1 revision) (flutter/flutter#102515)
2022-04-25 rageofepicfury@gmail.com Enable TestDefaultBinaryMessenger to intercept all platform channels. (flutter/flutter#100049)
2022-04-25 egarciad@google.com Reduce Gradle log level in verbose output (flutter/flutter#102422)
2022-04-25 wangying3426@gmail.com Assign debugCreator for more layers (flutter/flutter#101899)
2022-04-25 engine-flutter-autoroll@skia.org Roll Engine from 5451e88a09c0 to 966812846313 (2 revisions) (flutter/flutter#102513)
...
Commit queue failed; closing this roll.
|
gharchive/pull-request
| 2022-04-27T05:42:34 |
2025-04-01T04:34:17.332727
|
{
"authors": [
"engine-flutter-autoroll"
],
"repo": "flutter/plugins",
"url": "https://github.com/flutter/plugins/pull/5412",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
615366149
|
Reset zoom to initial state?
Is it possible to reset a zoomed image to the initial state when changing its content? I don't see any controller to do this with.
do you mean when image is changed ,zoom status is not initialize？
|
gharchive/issue
| 2020-05-10T10:55:47 |
2025-04-01T04:34:17.345832
|
{
"authors": [
"henriklagergren",
"zmtzawqlp"
],
"repo": "fluttercandies/extended_image",
"url": "https://github.com/fluttercandies/extended_image/issues/185",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1773657884
|
连续调用loading，可控频闪现象
版本信息
Flutter版本：[3.7.9]
flutter_smart_dialog版本：[4.9.2]
描述bug/需求
iOS上 mask Color不起作用
问题demo
FlutterSmartDialog.init(
loadingBuilder: (String msg) => CustomSmartLoadingWidget(msg),
toastBuilder: (msg) => CustomSmartToastWidget(msg),
)
class _CustomSmartLoadingWidgetState extends State<CustomSmartLoadingWidget> {
@override
Widget build(BuildContext context) {
return Center(
child: Column(
mainAxisSize: MainAxisSize.min,
children: [
Lottie.asset(AppLottie.loading, width: 50, fit: BoxFit.fitWidth, animate: true, repeat: true),
if (widget.msg.isNotEmpty == true)
const SizedBox(
height: 30,
),
if (widget.msg.isNotEmpty == true)
Text(
widget.msg,
style: TextStyles.tsPrimary14,
),
if (widget.btnText?.isNotEmpty == true)
Container(
width: double.infinity,
margin: const EdgeInsets.only(left: 90, right: 90, top: 30),
child: MaterialButton(
elevation: 0,
height: 48,
shape: RoundedRectangleBorder(borderRadius: BorderRadius.circular(24)),
color: AppColor.primary,
onPressed: widget.btnOnTap,
child: Text(
widget.btnText ?? '',
style: const TextStyle(fontSize: 16, fontWeight: FontWeight.bold),
),
))
],
),
);
}
}
这demo写的是个啥？重新弄下吧，能直接运行的全部简化代码
看错了 不是这个引起的 是因为在有loading的时候 又弹了一个新的loading 导致前面设置的不起效果了
但是好像这种弹起多个loading情况也没有办法避免,有办法让他永远只弹同一个吗?比如单例?
loading本来就是单个overlayEntry，后一个会顶掉前一个，这个只是你对loading设置不一样导致的
就是后面的顶掉前面的 会导致loading的效果看上去会有闪动 有办法让它始终保持这一个loading吗?
我周末想想怎么弄
感谢! 辛苦了!
解决了，试下新版本吧
dependencies:
flutter_smart_dialog: ^4.9.3
测试代码
void _showLoading() async {
SmartDialog.showLoading(msg: "test one");
await Future.delayed(const Duration(seconds: 1));
SmartDialog.showLoading(msg: "test two");
await Future.delayed(const Duration(seconds: 1));
SmartDialog.showLoading(msg: "test three");
await Future.delayed(const Duration(seconds: 1));
SmartDialog.dismiss();
}
解决了，试下新版本吧
dependencies:
flutter_smart_dialog: ^4.9.3+1
测试代码
void _showLoading() async {
SmartDialog.showLoading(msg: "test one");
await Future.delayed(const Duration(seconds: 1));
SmartDialog.showLoading(msg: "test two");
await Future.delayed(const Duration(seconds: 1));
SmartDialog.showLoading(msg: "test three");
await Future.delayed(const Duration(seconds: 1));
SmartDialog.dismiss();
}
太棒了！非常感谢！
|
gharchive/issue
| 2023-06-26T01:54:33 |
2025-04-01T04:34:17.351873
|
{
"authors": [
"SeeYouWilsen",
"xdd666t"
],
"repo": "fluttercandies/flutter_smart_dialog",
"url": "https://github.com/fluttercandies/flutter_smart_dialog/issues/137",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1011625784
|
CancelToken 取消请求后异常
CancelToken 取消请求后异常
使用 CancelToken 取消请求，请求已被取消，但还会抛出 Receiving data timeout 异常
Info
Value
Platform Name
ios 、android
Platform Version
2.2.3
Dio Version
4.0.0
try with 4.0.5-betal1
|
gharchive/issue
| 2021-09-30T02:25:50 |
2025-04-01T04:34:17.354649
|
{
"authors": [
"wendux",
"xiejibiao"
],
"repo": "flutterchina/dio",
"url": "https://github.com/flutterchina/dio/issues/1287",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
522754064
|
demo 错误
首页 get请求方式 示例错误
response = await dio.get(data2['url'], queryParameters: data2['data']);
queryParameters你写成了data
在哪里？
我看已经改了
|
gharchive/issue
| 2019-11-14T10:08:14 |
2025-04-01T04:34:17.355906
|
{
"authors": [
"MrQiu920702",
"wendux"
],
"repo": "flutterchina/dio",
"url": "https://github.com/flutterchina/dio/issues/554",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
445575639
|
Make DioError catchable by implementing Exception instead of Error
dart.core.Error is intended to be used for program failures and shouldn't be caught. DioError extends Error which is odd because errors like timeouts are intended to be caught. Therefore DioError should implement Exception.
From the dart.core.Error documentation:
* Error objects thrown in the case of a program failure.
*
* An `Error` object represents a program failure that the programmer
* should have avoided.
*
* Examples include calling a function with invalid arguments,
* or even with the wrong number of arguments,
* or calling it at a time when it is not allowed.
*
* These are not errors that a caller should expect or catch -
* if they occur, the program is erroneous,
* and terminating the program may be the safest response.
*
* Since errors are not created to be caught,
* there is no need for subclasses to distinguish the errors.
The favourite retry package follows this rule and doesn't allow catching non-Exception classes like DioError.
// form retry source
try {
return await fn();
} on Exception catch (e) { // doesn't catch DioError
FWIW I just started using Dio (which looks great btw) and immediately ran into an error I couldn't catch (server returned 401 Unauthorized because I was missing a header, but the debugger halts and there's nothing I can do about it).
This PR looks like it would sove this issue easily and painlessly.
Ive been caught into this using version 3.0.7, just today
|
gharchive/pull-request
| 2019-05-17T18:59:20 |
2025-04-01T04:34:17.359141
|
{
"authors": [
"SvenSchoene",
"diego-lipinski-de-castro",
"passsy"
],
"repo": "flutterchina/dio",
"url": "https://github.com/flutterchina/dio/pull/304",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
158261619
|
Cell Update Bug
When running the game in extended mode, all cells are converted to standard cells upon updating the game to the second round (the first round after initialization).
Fixed in 3.0.1
|
gharchive/issue
| 2016-06-02T23:25:05 |
2025-04-01T04:34:17.366968
|
{
"authors": [
"flutterflies"
],
"repo": "flutterflies/GameOfLife",
"url": "https://github.com/flutterflies/GameOfLife/issues/1",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
1053366221
|
Kustomization reconciliation failed: too many fields within:
I've installed Flux v0.23.0 and some kustomizations that should be working cannot be updated giving me this error:
2021-11-15T08:40:40.715Z error Kustomization/rights.flux-system - Reconciliation failed after 23.465925ms, next try in 5m0s too many fields within: exploitation_clusterRole_rbac.authorization.k8s.io
As far I can search, the error message is ent by apply mechanism when the object metadata doesn't have the correct format (in this case, the "_" between clusterRole and rbac whould e replaced by ".".
An poor-man bissect give me that the faulty release is the 0.15.0 of kustomize-controller (and I may put another penny on https://github.com/fluxcd/kustomize-controller/commit/3a03d235c241e097e0b6c5d293eca1e55e7c3917 without any validation).
A clean install of 0.23.0 of flux cd, followed by a downgrade of kustomize-controller to version 0.14.1 fixes the issue.
Can you post an RBAC example of how to replicate this error?
here's the tar.gz of both repositories used in my test (flux-system and the link admin repository).
Here's the command to add administration repo :
flux create source git administration
--interval 5m0s
--branch "${CLUSTER_NAME}"
--secret-ref flux-system
--url "${GIT_BASE_URL}${ADMIN_REPOSITORY}"
flux create kustomization rights
--source=GitRepository/administration
--path="./rights"
--prune=true
--interval=5m
flux create kustomization delegations
--source=GitRepository/administration
--path="./delegations"
--prune=true
--interval=5m
administration.tar.gz
flux-system.tar.gz
Can you please confirm that your RBAC can be applied on the cluster with kubectl apply --server-side -f.
yes it's working :
kubectl apply --server-side -f ../rights/exploitation_clusterrole.yaml
clusterrole.rbac.authorization.k8s.io/ops_clusterRole2 serverside-applied
Note the problem seems to be only on update.
Having a similar issue with the Thanos monitoring mixin. The initial error message wasn't very helpful:
{"level":"error","ts":"2021-11-19T10:41:41.825Z","logger":"controller.kustomization","msg":"Reconciliation failed after 7.335991041s, next try in 1m0s","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"kube-prometheus-components","namespace":"monitoring","revision":"master/958670aabba07f97fdebbd0287076fd34877ae83","error":"too many fields within: grafana-dashboard-bucket_replicate_","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.10.2/pkg/internal/controller/controller.go:311\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.10.2/pkg/internal/controller/controller.go:266\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.10.2/pkg/internal/controller/controller.go:227"}
{"level":"debug","ts":"2021-11-19T10:41:41.826Z","logger":"events","msg":"Warning","object":{"kind":"Kustomization","namespace":"monitoring","name":"kube-prometheus-components","uid":"e8ee9cd5-4701-4519-bc41-93ef37b7f760","apiVersion":"kustomize.toolkit.fluxcd.io/v1beta2","resourceVersion":"52741687"},"reason":"error","message":"too many fields within: grafana-dashboard-bucket_replicate_"}
# $ kubectl -n monitoring get kustomization kube-prometheus-components -o yaml
apiVersion: kustomize.toolkit.fluxcd.io/v1beta2
kind: Kustomization
metadata:
creationTimestamp: "2021-11-10T14:59:40Z"
finalizers:
- finalizers.fluxcd.io
generation: 5
labels:
kustomize.toolkit.fluxcd.io/name: infra
kustomize.toolkit.fluxcd.io/namespace: flux-system
managedFields:
- apiVersion: kustomize.toolkit.fluxcd.io/v1beta2
fieldsType: FieldsV1
fieldsV1:
f:metadata:
f:labels:
f:kustomize.toolkit.fluxcd.io/name: {}
f:kustomize.toolkit.fluxcd.io/namespace: {}
f:spec:
f:dependsOn: {}
f:interval: {}
f:path: {}
f:prune: {}
f:sourceRef:
f:kind: {}
f:name: {}
f:namespace: {}
f:targetNamespace: {}
manager: kustomize-controller
operation: Apply
time: "2021-11-16T11:29:39Z"
- apiVersion: kustomize.toolkit.fluxcd.io/v1beta2
fieldsType: FieldsV1
fieldsV1:
f:metadata:
f:finalizers:
.: {}
v:"finalizers.fluxcd.io": {}
f:status:
f:conditions: {}
f:inventory:
.: {}
f:entries: {}
f:lastAppliedRevision: {}
f:lastAttemptedRevision: {}
f:observedGeneration: {}
manager: kustomize-controller
operation: Update
time: "2021-11-10T15:05:56Z"
name: kube-prometheus-components
namespace: monitoring
resourceVersion: "52722166"
uid: e8ee9cd5-4701-4519-bc41-93ef37b7f760
spec:
dependsOn:
- name: kube-prometheus-setup
namespace: monitoring
- name: kube-prometheus-install
namespace: kube-system
force: false
interval: 1m
path: kubernetes/clusters/management/kube-prometheus/components
prune: true
sourceRef:
kind: GitRepository
name: infra
namespace: flux-system
targetNamespace: monitoring
status:
conditions:
- lastTransitionTime: "2021-11-19T10:16:21Z"
message: 'too many fields within: grafana-dashboard-bucket_replicate_'
reason: ReconciliationFailed
status: "False"
type: Ready
inventory:
entries:
- id: monitoring_alertmanager-main__ServiceAccount
v: v1
- id: monitoring_grafana__ServiceAccount
v: v1
- id: monitoring_prometheus-k8s__ServiceAccount
v: v1
- id: monitoring_prometheus-k8s-config_rbac.authorization.k8s.io_Role
v: v1
- id: monitoring_prometheus-k8s_rbac.authorization.k8s.io_ClusterRole
v: v1
- id: monitoring_prometheus-k8s-config_rbac.authorization.k8s.io_RoleBinding
v: v1
- id: monitoring_prometheus-k8s_rbac.authorization.k8s.io_ClusterRoleBinding
v: v1
- id: monitoring_grafana-dashboard-alertmanager-overview__ConfigMap
v: v1
- id: monitoring_grafana-dashboard-apiserver__ConfigMap
v: v1
- id: monitoring_grafana-dashboard-cert-manager__ConfigMap
v: v1
- id: monitoring_grafana-dashboard-cluster-total__ConfigMap
v: v1
- id: monitoring_grafana-dashboard-controller-manager__ConfigMap
v: v1
- id: monitoring_grafana-dashboard-k8s-resources-cluster__ConfigMap
v: v1
- id: monitoring_grafana-dashboard-k8s-resources-namespace__ConfigMap
v: v1
- id: monitoring_grafana-dashboard-k8s-resources-node__ConfigMap
v: v1
- id: monitoring_grafana-dashboard-k8s-resources-pod__ConfigMap
v: v1
- id: monitoring_grafana-dashboard-k8s-resources-workload__ConfigMap
v: v1
- id: monitoring_grafana-dashboard-k8s-resources-workloads-namespace__ConfigMap
v: v1
- id: monitoring_grafana-dashboard-kubelet__ConfigMap
v: v1
- id: monitoring_grafana-dashboard-namespace-by-pod__ConfigMap
v: v1
- id: monitoring_grafana-dashboard-namespace-by-workload__ConfigMap
v: v1
- id: monitoring_grafana-dashboard-node-cluster-rsrc-use__ConfigMap
v: v1
- id: monitoring_grafana-dashboard-node-rsrc-use__ConfigMap
v: v1
- id: monitoring_grafana-dashboard-nodes__ConfigMap
v: v1
- id: monitoring_grafana-dashboard-persistentvolumesusage__ConfigMap
v: v1
- id: monitoring_grafana-dashboard-pod-total__ConfigMap
v: v1
- id: monitoring_grafana-dashboard-prometheus__ConfigMap
v: v1
- id: monitoring_grafana-dashboard-prometheus-remote-write__ConfigMap
v: v1
- id: monitoring_grafana-dashboard-proxy__ConfigMap
v: v1
- id: monitoring_grafana-dashboard-scheduler__ConfigMap
v: v1
- id: monitoring_grafana-dashboard-workload-total__ConfigMap
v: v1
- id: monitoring_grafana-dashboards__ConfigMap
v: v1
- id: monitoring_alertmanager-main__Secret
v: v1
- id: monitoring_grafana-config__Secret
v: v1
- id: monitoring_grafana-datasources__Secret
v: v1
- id: monitoring_monitoring-http-basic-auth__Secret
v: v1
- id: monitoring_alertmanager-main__Service
v: v1
- id: monitoring_grafana__Service
v: v1
- id: monitoring_prometheus-k8s__Service
v: v1
- id: monitoring_prometheus-k8s-thanos-sidecar__Service
v: v1
- id: monitoring_grafana_apps_Deployment
v: v1
- id: monitoring_alertmanager-main_policy_PodDisruptionBudget
v: v1
- id: monitoring_main_monitoring.coreos.com_Alertmanager
v: v1
- id: monitoring_k8s_monitoring.coreos.com_Prometheus
v: v1
- id: monitoring_alertmanager-main-rules_monitoring.coreos.com_PrometheusRule
v: v1
- id: monitoring_cert-manager_monitoring.coreos.com_PrometheusRule
v: v1
- id: monitoring_kube-prometheus-rules_monitoring.coreos.com_PrometheusRule
v: v1
- id: monitoring_prometheus-k8s-prometheus-rules_monitoring.coreos.com_PrometheusRule
v: v1
- id: monitoring_prometheus-k8s-thanos-sidecar-rules_monitoring.coreos.com_PrometheusRule
v: v1
- id: monitoring_prometheus-operator-rules_monitoring.coreos.com_PrometheusRule
v: v1
- id: monitoring_alertmanager-main_monitoring.coreos.com_ServiceMonitor
v: v1
- id: monitoring_grafana_monitoring.coreos.com_ServiceMonitor
v: v1
- id: monitoring_prometheus-k8s_monitoring.coreos.com_ServiceMonitor
v: v1
- id: monitoring_prometheus-operator_monitoring.coreos.com_ServiceMonitor
v: v1
- id: monitoring_thanos-sidecar_monitoring.coreos.com_ServiceMonitor
v: v1
- id: monitoring_alertmanager-main_networking.k8s.io_Ingress
v: v1
- id: monitoring_grafana_networking.k8s.io_Ingress
v: v1
- id: monitoring_prometheus-k8s_networking.k8s.io_Ingress
v: v1
lastAppliedRevision: master/77627c84f65fd8ee95204f2b3e5760f2fdb7cd46
lastAttemptedRevision: master/2e58eb07bd4136babce9969f823f6a6ac643f21e
observedGeneration: 5
After deleting the above Kustomization, I got a "proper" error:
{"level":"error","ts":"2021-11-19T10:53:28.010Z","logger":"controller.kustomization","msg":"Reconciliation failed after 1.025864206s, next try in 1m0s","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"kube-prometheus-components","namespace":"monitoring","revision":"master/958670aabba07f97fdebbd0287076fd34877ae83","error":"ConfigMap/monitoring/grafana-dashboard-bucket_replicate dry-run failed, reason: Invalid, error: ConfigMap \"grafana-dashboard-bucket_replicate\" is invalid: metadata.name: Invalid value: \"grafana-dashboard-bucket_replicate\": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')\n","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.10.2/pkg/internal/controller/controller.go:311\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.10.2/pkg/internal/controller/controller.go:266\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.10.2/pkg/internal/controller/controller.go:227"}
{"level":"debug","ts":"2021-11-19T10:53:28.011Z","logger":"events","msg":"Warning","object":{"kind":"Kustomization","namespace":"monitoring","name":"kube-prometheus-components","uid":"63f8f759-d6d8-43d3-ac61-0c38d8253286","apiVersion":"kustomize.toolkit.fluxcd.io/v1beta2","resourceVersion":"52752092"},"reason":"error","message":"ConfigMap/monitoring/grafana-dashboard-bucket_replicate dry-run failed, reason: Invalid, error: ConfigMap \"grafana-dashboard-bucket_replicate\" is invalid: metadata.name: Invalid value: \"grafana-dashboard-bucket_replicate\": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')\n"}
# $ kubectl -n monitoring get kustomization kube-prometheus-components -o yaml
apiVersion: kustomize.toolkit.fluxcd.io/v1beta2
kind: Kustomization
metadata:
creationTimestamp: "2021-11-19T10:53:26Z"
finalizers:
- finalizers.fluxcd.io
generation: 2
labels:
kustomize.toolkit.fluxcd.io/name: infra
kustomize.toolkit.fluxcd.io/namespace: flux-system
managedFields:
- apiVersion: kustomize.toolkit.fluxcd.io/v1beta2
fieldsType: FieldsV1
fieldsV1:
f:metadata:
f:labels:
f:kustomize.toolkit.fluxcd.io/name: {}
f:kustomize.toolkit.fluxcd.io/namespace: {}
f:spec:
f:dependsOn: {}
f:path: {}
f:prune: {}
f:sourceRef:
f:kind: {}
f:name: {}
f:namespace: {}
f:targetNamespace: {}
manager: kustomize-controller
operation: Apply
time: "2021-11-19T10:53:26Z"
- apiVersion: kustomize.toolkit.fluxcd.io/v1beta2
fieldsType: FieldsV1
fieldsV1:
f:metadata:
f:finalizers:
.: {}
v:"finalizers.fluxcd.io": {}
f:spec:
f:interval: {}
f:status:
f:conditions: {}
f:lastAttemptedRevision: {}
f:observedGeneration: {}
manager: kustomize-controller
operation: Update
time: "2021-11-19T10:53:28Z"
name: kube-prometheus-components
namespace: monitoring
resourceVersion: "52752917"
uid: 63f8f759-d6d8-43d3-ac61-0c38d8253286
spec:
dependsOn:
- name: kube-prometheus-setup
namespace: monitoring
- name: kube-prometheus-install
namespace: kube-system
force: false
interval: 1m0s
path: kubernetes/clusters/management/kube-prometheus/components
prune: true
sourceRef:
kind: GitRepository
name: infra
namespace: flux-system
targetNamespace: monitoring
status:
conditions:
- lastTransitionTime: "2021-11-19T10:54:29Z"
message: |
ConfigMap/monitoring/grafana-dashboard-bucket_replicate dry-run failed, reason: Invalid, error: ConfigMap "grafana-dashboard-bucket_replicate" is invalid: metadata.name: Invalid value: "grafana-dashboard-bucket_replicate": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
reason: ReconciliationFailed
status: "False"
type: Ready
lastAttemptedRevision: master/958670aabba07f97fdebbd0287076fd34877ae83
observedGeneration: 2
kubeval gives the file a pass, as does client side kubectl apply dry-run:
kubeval kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains an empty YAML document
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-alertmanager-overview)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-apiserver)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-bucket_replicate)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-cluster-total)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-compact)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-controller-manager)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-k8s-resources-cluster)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-k8s-resources-namespace)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-k8s-resources-node)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-k8s-resources-pod)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-k8s-resources-workload)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-k8s-resources-workloads-namespace)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-kubelet)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-namespace-by-pod)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-namespace-by-workload)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-node-cluster-rsrc-use)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-node-rsrc-use)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-nodes)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-overview)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-persistentvolumesusage)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-pod-total)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-prometheus-remote-write)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-prometheus)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-proxy)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-query)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-query_frontend)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-receive)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-rule)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-scheduler)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-sidecar)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-store)
PASS - kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml contains a valid ConfigMap (monitoring.grafana-dashboard-workload-total)
$ kubectl -n monitoring apply -f kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml --dry-run=client
configmap/grafana-dashboard-alertmanager-overview created (dry run)
configmap/grafana-dashboard-apiserver created (dry run)
configmap/grafana-dashboard-bucket_replicate created (dry run)
configmap/grafana-dashboard-cluster-total created (dry run)
configmap/grafana-dashboard-compact created (dry run)
configmap/grafana-dashboard-controller-manager created (dry run)
configmap/grafana-dashboard-k8s-resources-cluster created (dry run)
configmap/grafana-dashboard-k8s-resources-namespace created (dry run)
configmap/grafana-dashboard-k8s-resources-node created (dry run)
configmap/grafana-dashboard-k8s-resources-pod created (dry run)
configmap/grafana-dashboard-k8s-resources-workload created (dry run)
configmap/grafana-dashboard-k8s-resources-workloads-namespace created (dry run)
configmap/grafana-dashboard-kubelet created (dry run)
configmap/grafana-dashboard-namespace-by-pod created (dry run)
configmap/grafana-dashboard-namespace-by-workload created (dry run)
configmap/grafana-dashboard-node-cluster-rsrc-use created (dry run)
configmap/grafana-dashboard-node-rsrc-use created (dry run)
configmap/grafana-dashboard-nodes created (dry run)
configmap/grafana-dashboard-overview created (dry run)
configmap/grafana-dashboard-persistentvolumesusage created (dry run)
configmap/grafana-dashboard-pod-total created (dry run)
configmap/grafana-dashboard-prometheus-remote-write created (dry run)
configmap/grafana-dashboard-prometheus created (dry run)
configmap/grafana-dashboard-proxy created (dry run)
configmap/grafana-dashboard-query created (dry run)
configmap/grafana-dashboard-query_frontend created (dry run)
configmap/grafana-dashboard-receive created (dry run)
configmap/grafana-dashboard-rule created (dry run)
configmap/grafana-dashboard-scheduler created (dry run)
configmap/grafana-dashboard-sidecar created (dry run)
configmap/grafana-dashboard-store created (dry run)
configmap/grafana-dashboard-workload-total created (dry run)
However, server side kubectl apply dry run fails with the exact error the Kustomize controller is throwing:
kubectl -n monitoring apply -f kubernetes/clusters/management/kube-prometheus/components/grafana-dashboardDefinitions.yaml --dry-run=server
configmap/grafana-dashboard-alertmanager-overview created (server dry run)
configmap/grafana-dashboard-apiserver created (server dry run)
configmap/grafana-dashboard-cluster-total created (server dry run)
configmap/grafana-dashboard-compact created (server dry run)
configmap/grafana-dashboard-controller-manager created (server dry run)
configmap/grafana-dashboard-k8s-resources-cluster created (server dry run)
configmap/grafana-dashboard-k8s-resources-namespace created (server dry run)
configmap/grafana-dashboard-k8s-resources-node created (server dry run)
configmap/grafana-dashboard-k8s-resources-pod created (server dry run)
configmap/grafana-dashboard-k8s-resources-workload created (server dry run)
configmap/grafana-dashboard-k8s-resources-workloads-namespace created (server dry run)
configmap/grafana-dashboard-kubelet created (server dry run)
configmap/grafana-dashboard-namespace-by-pod created (server dry run)
configmap/grafana-dashboard-namespace-by-workload created (server dry run)
configmap/grafana-dashboard-node-cluster-rsrc-use created (server dry run)
configmap/grafana-dashboard-node-rsrc-use created (server dry run)
configmap/grafana-dashboard-nodes created (server dry run)
configmap/grafana-dashboard-overview created (server dry run)
configmap/grafana-dashboard-persistentvolumesusage created (server dry run)
configmap/grafana-dashboard-pod-total created (server dry run)
configmap/grafana-dashboard-prometheus-remote-write created (server dry run)
configmap/grafana-dashboard-prometheus created (server dry run)
configmap/grafana-dashboard-proxy created (server dry run)
configmap/grafana-dashboard-query created (server dry run)
configmap/grafana-dashboard-receive created (server dry run)
configmap/grafana-dashboard-rule created (server dry run)
configmap/grafana-dashboard-scheduler created (server dry run)
configmap/grafana-dashboard-sidecar created (server dry run)
configmap/grafana-dashboard-store created (server dry run)
configmap/grafana-dashboard-workload-total created (server dry run)
Error from server (Invalid): ConfigMap "grafana-dashboard-bucket_replicate" is invalid: metadata.name: Invalid value: "grafana-dashboard-bucket_replicate": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
Error from server (Invalid): ConfigMap "grafana-dashboard-query_frontend" is invalid: metadata.name: Invalid value: "grafana-dashboard-query_frontend": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
Server side apply (non dry run) also fails with the same error.
Flux version info:
$ flux version
flux: v0.23.0
helm-controller: v0.12.0
image-automation-controller: v0.15.0
image-reflector-controller: v0.12.0
kustomize-controller: v0.15.5
notification-controller: v0.17.1
source-controller: v0.16.0
$ flux check
► checking prerequisites
✔ Kubernetes 1.21.5-gke.1802 >=1.19.0-0
► checking controllers
✔ helm-controller: deployment ready
► ghcr.io/fluxcd/helm-controller:v0.12.0
✔ image-automation-controller: deployment ready
► ghcr.io/fluxcd/image-automation-controller:v0.15.0
✔ image-reflector-controller: deployment ready
► ghcr.io/fluxcd/image-reflector-controller:v0.12.0
✔ kustomize-controller: deployment ready
► ghcr.io/fluxcd/kustomize-controller:v0.15.5
✔ notification-controller: deployment ready
► ghcr.io/fluxcd/notification-controller:v0.17.1
✔ source-controller: deployment ready
► ghcr.io/fluxcd/source-controller:v0.16.0
✔ all checks passed
Kubernetes version info:
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.6", GitCommit:"d921bc6d1810da51177fbd0ed61dc811c5228097", GitTreeState:"clean", BuildDate:"2021-10-27T17:50:34Z", GoVersion:"go1.16.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.5-gke.1802", GitCommit:"d464a255a4acb8dca1e0914586f4f5085681fb51", GitTreeState:"clean", BuildDate:"2021-10-21T21:43:23Z", GoVersion:"go1.16.7b7", Compiler:"gc", Platform:"linux/amd64"}
I'd rather not post the grafana-dashboardDefinitions.yaml file as it's like a bajillion lines and I'm not sure if it contains anything sensitive. Am I correct in assessing the situation (in my case) as an issue with the Thanos mixin rather than flux or k8s?
Am I correct in assessing the situation (in my case) as an issue with the Thanos mixin rather than flux or k8s?
Yes, if Kubernetes API server-side apply validation finds the manifest invalid, it's nothing we can do in Flux.
Hi,
we're facing the same issue with flux 0.23.0.
The error message says: "too many fields within: xyz-admin-teamabc_admin_rbac.authorization.k8s.io"
Appliying on the rolebinding-manifest:
kubeval --> says o.k.
kubectl apply --dry-run=client --> says o.k.
kubectl apply --dry-run=server --> says o.k.
kubectl apply --> Resources are applied to cluster
Exactly the same gitops-repo was applied earlier (flux 0.17.1) to another cluster without any problems.
I also downgraded kustomize-controller to v0.14.1 as suggested by @castorls and it works immediately.
Nevertheless flux2 is a great tool!
@doc-olliday Flux does kubectl apply --server-side -f can please try this with your RBAC. If applying with --server-side works, please post here the RBAC so we can replicate the issue. Thanks.
kubectl apply --server-side -f worked without any problem.
Here is the content of the manifest. Some sensitive data is anonymised:
---
kind: RoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: xxx-admin-abcabcabc_admin
namespace: foo
subjects:
- kind: Group
name: abcabcabc_admin
roleRef:
kind: ClusterRole
name: crc-namespace-admin
apiGroup: rbac.authorization.k8s.io
---
kind: RoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: xxx-edit-abcabcabc_edit
namespace: foo
subjects:
- kind: Group
name: abcabcabc
- kind: Group
name: abcabcabc_edit
roleRef:
kind: ClusterRole
name: crc-namespace-edit
apiGroup: rbac.authorization.k8s.io
---
kind: RoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: xxx-view-abcabcabc_view
namespace: foo
subjects:
- kind: Group
name: abcabcabc_view
roleRef:
kind: ClusterRole
name: crc-namespace-view
apiGroup: rbac.authorization.k8s.io
A workaround for this error is to remove an underscore from the names of your resources .
For ability to rename (remove underscores) without deleting any resources, older flux v2 is needed, one without this bug.
But if flux v2 has been upgraded to a version with this bug, and one is fine with deleting+recreating resource with underscores in name, notice that you will have to delete them manually (kubectl or helm CLI) but one will also have to delete the Kustomization resource was managed under since flux v2 maintains inventory in status subresource of Kustomization and kustomize-controller will not successfully reconcile the Kustomization resource until inventory has been cleaned up too.
For status inventory subresource, workaround that for me didn't delete any other resource/HelmRelease (other than one with underscores) in same Kustomization, but recovered Kustomization to be able to reconcile again:
scale down kustomize-controller to 0
delete the Kustomization which has inventory item with underscore in resource name (if it's bootstrap/root Kustomization, save yaml of it before deleting, and edit the yaml, remove all of the status, annotations, finalizers, generation, resourceVersion, uid i.e. keep apiVersion, kind, metadata.name, metadata.namespace, and all of spec.*)
scale back up kustomize-controller
recreate the deleted "bootstrap" Kustomization (or watch kustomize-controller recreate it, if it's a "leaf" Kustomization that had issues)
This error comes from an upstream library sigs.k8s.io/cli-utils because it incorrectly assumes a resource cannot have an underscore in its name.
A workaround for this error is to remove an underscore from the names of your resources .
Pretty sure RFC1123-style naming is still a thing.
Name must be unique within a namespace. Is required when creating resources, although some resources may allow a client to request the generation of an appropriate name automatically. Name is primarily intended for creation idempotence and configuration definition. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/identifiers#names
The documentation for roleBinding says that their names must be valid path segment names. That restricts them to not contain things like ., .., /, etc. but doesn't seem to require RFC 1123 names.
Even though I fixed _-s in the descriptor names, and made sure the tree of Flux resources (sources, kustomizations) referred to the proper revision, I wasn't able to reconcile the actual revision, the kustomization controller still threw an error. (Just to be sure, manually deleted the relevant RBAC resources as well.)
What solved the problem is the manual deletion of the parent kustomization, and its manual reconciliation.
This still appears to be an issue with v2.1.1.. Happy to be told that underscore or colon is not a valid character in the resource name, but we are able to server-side apply a resource with those characters in name.
|
gharchive/issue
| 2021-11-15T08:45:15 |
2025-04-01T04:34:17.413397
|
{
"authors": [
"SomtochiAma",
"castorls",
"doc-olliday",
"gladiatr72",
"itspngu",
"marcsaegesser",
"ntjn",
"scpandit",
"stefanprodan",
"stevo-f3"
],
"repo": "fluxcd/kustomize-controller",
"url": "https://github.com/fluxcd/kustomize-controller/issues/491",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
652196081
|
Support for git repository update notifications based on selective file patterns
The custom resource status (transition timestamp and url) should only change when a change occurred to a file that is included by the ignorePatterns specification, see issue #74
Should this just be notifications or should it be the entire resource isn't reconciled based on selective file patterns?
|
gharchive/issue
| 2020-07-07T10:12:56 |
2025-04-01T04:34:17.416417
|
{
"authors": [
"arbourd",
"paulcarlton-ww"
],
"repo": "fluxcd/source-controller",
"url": "https://github.com/fluxcd/source-controller/issues/75",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1231987116
|
🛑 Cartilla is down
In 1b096d9, Cartilla (https://extranet.osam.org.ar/Consulta/cartilla) was down:
HTTP code: 0
Response time: 0 ms
Resolved: Cartilla is back up in 4c598f4.
|
gharchive/issue
| 2022-05-11T04:21:44 |
2025-04-01T04:34:17.418756
|
{
"authors": [
"flvanney"
],
"repo": "flvanney/OSAMuptime",
"url": "https://github.com/flvanney/OSAMuptime/issues/135",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
120373500
|
Cluster in an undefined state
Hi,
I'm playing arround with letsencrypt. To get my certs, I needed port 80 on my first machine of the cluster. So I temporarly stopped flynn-host. After restarting it, I needed multiple tries to modify my routes: Like 4 in 5 times, flynn route answered with
Post https://controller.........com/apps/myApp/routes: dial tcp 213.73........:443: connection refused
This is what flynn-host ps on the first machine gave me:
ID STATE STARTED CONTROLLER APP CONTROLLER TYPE
flynn1-aff1eb28-b419-4b70-9f0b-1396452989c1 running 17 minutes ago blobstore web
flynn2-80a2ed31-d7df-400c-95b0-58b2b44c8f89 running 27 minutes ago discoverd app
flynn2-106fefa1-c73f-432d-acb0-994380634fc7 running 27 minutes ago status web
flynn2-15c1f7fb-05cf-4256-a9f9-4631fd39847a running 27 minutes ago controller worker
flynn1-8e930eb2-9cf5-45fb-9d0c-7f86e6b9eb26 running 16 hours ago myApp web
flynn1-d50b9817-a6f6-462a-8eed-ce9fc4832216 running 16 hours ago status web
flynn2-0949316c-3fdf-4f39-a31f-4ace4eff176d running 16 hours ago dashboard web
flynn1-aff44ae1-158f-472c-88ac-124fdd63e672 running 16 hours ago dashboard web
flynn2-964fd054-2260-4f46-b037-6e85f1a4b06d running 16 hours ago logaggregator app
flynn1-875b4ab5-156b-4c54-9243-729e6c4fa891 running 16 hours ago logaggregator app
flynn2-3e1132c2-0110-41dd-91b1-0c567b3ded87 running 16 hours ago gitreceive app
flynn1-b86f171b-dd67-45c4-a3de-2dc130b8cd51 running 16 hours ago gitreceive app
flynn2-63cd63f8-7f5a-48aa-8db5-a54a9cef9756 running 16 hours ago router app
flynn1-a6d9c865-01f8-47dd-8961-766f677f72fa running 16 hours ago router app
flynn2-5f2c646e-1039-487f-9038-d0603e800232 running 16 hours ago blobstore web
flynn2-f8b72616-19be-4052-97b4-f8d9216c7986 running 16 hours ago controller web
flynn1-bfdb7f3e-05c3-43ec-8859-c506ce1cd9d1 running 16 hours ago controller worker
flynn1-10079698-29b0-4638-96b0-659b238f0fe2 running 16 hours ago controller scheduler
flynn2-316b622a-e939-43eb-9522-edcea84b683e running 16 hours ago controller scheduler
flynn0-f2c9039e-434b-4da4-b5f7-7a79b4963922 running 16 hours ago controller web
flynn2-98fc5ba5-302d-4e3b-8541-4cece78dc96d running 16 hours ago postgres web
flynn1-65990563-2963-4a86-870f-233a037a5854 running 16 hours ago postgres web
flynn1-b61848c7-90b4-4046-83f4-bd227d5bd65c running 16 hours ago postgres postgres
flynn2-0c6f786e-db3f-4599-ab5b-4f17848cf694 running 16 hours ago postgres postgres
flynn2-681d66a2-be60-4395-b91c-32f5e409375c running 16 hours ago flannel app
flynn1-cf1b7ce0-d58a-4e6e-8742-51a650248ce7 running 16 hours ago flannel app
flynn1-44154587-83cb-4e40-962c-f53ce0c8d147 running 16 hours ago discoverd app
flynn0-2c1e9972-aa46-4622-bcca-fe6b1dfaf586 running 16 hours ago discoverd app
So I restarted flynn-host on the first machine again. Now flynn-host ps gives me just that:
11:14:47.072828 host.go:135: could not list hosts: Get http://127.0.0.1:1111/services/flynn-host/instances: dial tcp 127.0.0.1:1111: connection refused
Here is a gist from the first machine:
https://gist.github.com/70c23d5e27c9507d4a68
Collecting the infos on the first machine resulted in:
EROR[12-04|11:18:03] error getting job logs, falling back to on-disk logs err="could not list hosts: Get http://127.0.0.1:1111/services/flynn-host/instances: dial tcp 127.0.0.1:1111: connection refused"
So I collected them on the second machine as well:
https://gist.github.com/ca4273e7a0e285a5479e
Is this relevant? Or might I close this?
We have other issues about fixing up TLS cert handling (#2442) so we can close this one.
Alright, thx.
|
gharchive/issue
| 2015-12-04T10:26:31 |
2025-04-01T04:34:17.471968
|
{
"authors": [
"philiplb",
"titanous"
],
"repo": "flynn/flynn",
"url": "https://github.com/flynn/flynn/issues/2241",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
198802744
|
Cluster setup from web installer may fail related to netfilter-persistent
Attempting to set up a 3x 2 GB / 40 GB cluster on DigitalOcean via the web installer failed multiple times before successfully completing on the third of fourth try. I don't have complete logs from the failed startup, so I'll do the best I can to describe what I remember seeing last night.
First off, I know that the logs included the lines:
'netfilter-persistent: command not found' and
'run-parts: executing /usr/share/netfilter-persistent/plugins.d/15-ip4tables save'
The failures appeared to hang in different places, and I don't believe any of them stopped immediately upon hitting the initial issue with netfilter-persistent. There would be a message about a missing dependency or service setup failure around netfilter-persistent, and then the installer would print some lines related to setting it up (looked like a delayed or retry attempt), and finally the install would get stuck. I waited about 5-10 minutes each time before killing the install and starting over.
There may have been some interplay between previously failed (but not fully cleaned up clusters) and the new deployment attempts, but it seems pretty unlikely. The only reason I'm mentioning it is because I made sure to fully clean up the previous failed clusters before the last attempt finally completed successfully.
@ncantelmo I have bootstrapped multiple DigitalOcean clusters and cannot reproduce what you describe.
If you see this again please post the full output from the installer.
I was able to reproduce the issue with the following steps:
Running flynn install
Install a 3-node cluster on DO (successfully)
Killing the flynn install process via Ctrl-C
Running flynn cluster remove <cluster-name>
Running flynn install (removed cluster still listed in installer)
Without cleaning up the removed cluster, installing a new 3-node cluster on DO
As requested, a log from the installer is attached.
flynn-install-failure-20160113.txt
|
gharchive/issue
| 2017-01-04T20:26:46 |
2025-04-01T04:34:17.476911
|
{
"authors": [
"lmars",
"ncantelmo"
],
"repo": "flynn/flynn",
"url": "https://github.com/flynn/flynn/issues/3802",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
187239173
|
all: Switch to SquashFS + OverlayFS images
This merges all the Flynn image changes into master:
#3381 - all: Add Flynn image manifests and imagebuilder
#3471 - host: Use SquashFS + OverlayFS via Mountspecs
#3481 - all: Add Flynn image artifacts
#3496 - Migrate slugs and docker-receive releases to Flynn images
#3605 - bootstrap: Convert slugs and Docker images on cluster restore
#3609 - all: Release Flynn images
Although there a lot of changes, they have already been reviewed so I have squashed into two commits to make this easier to revert if we need to.
Replaces #3100.
:smile:
|
gharchive/pull-request
| 2016-11-04T02:23:11 |
2025-04-01T04:34:17.479319
|
{
"authors": [
"lmars"
],
"repo": "flynn/flynn",
"url": "https://github.com/flynn/flynn/pull/3619",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
824237695
|
Google OAuth
Google OAuth is ready to go.
@Meechlouch
google oauth is sending back data
28285fa
@Meechlouch
login and logout components added
2329ec6
@Meechlouch
login and logout buttons
7ac4ad8
@Meechlouch
function added for refresh tokens
43a6356
@Meechlouch
dependancies
04a7bdb
@Meechlouch
Merge branch 'main' of github.com:flynn0087/Suds_Scheduler into Googl… …
f4b6fe6
…e-OAuth
|
gharchive/pull-request
| 2021-03-08T06:49:52 |
2025-04-01T04:34:17.482065
|
{
"authors": [
"Kay0s",
"Meechlouch"
],
"repo": "flynn0087/Suds_Scheduler",
"url": "https://github.com/flynn0087/Suds_Scheduler/pull/44",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
602597173
|
Parser issue for Sybase ASE for keyword GOTO
Which version and edition of Flyway are you using?
6.3.3 (community and pro edition)
If this is not the latest version, can you reproduce the issue with the latest one as well?
(Many bugs are fixed in newer releases and upgrading will often resolve the issue)
Yes the issue can be reproduced in the latest. (v6.3.3)
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Command Line
Which database are you using (type & version)?
Sybase ASE 16.2
Which operating system are you using?
Linux
What did you do?
(Please include the content causing the issue, any relevant configuration settings, the SQL statement that failed (if relevant) and the command you ran.)
SQL with GOTO keywords results in a 'column not found' error when running migrate command. The parser is splitting the GOTO into two keywords (GO, TO)
declare @count smallint
select @count = 1
restart:
print 'yes'
select @count = @count + 1
while @count <= 4
goto restart
What did you expect to see?
No errors when running migrate command. In the code snippet above 'yes' should be printed 3x
What did you see instead?
Migration R__wes.sql failed
---------------------------
SQL State : 37000
Error Code : 102
Message : Incorrect syntax near '4'.
Line : 1
Statement : declare @count smallint
select @count = 1
restart:
print 'yes'
select @count = @count + 1
while @count <= 4
This will be in flyway 6.4.1
|
gharchive/issue
| 2020-04-19T01:55:32 |
2025-04-01T04:34:17.498693
|
{
"authors": [
"Lyeeedar",
"ltwesley"
],
"repo": "flyway/flyway",
"url": "https://github.com/flyway/flyway/issues/2774",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1780807493
|
Replace Jackson usage in ClassicConfiguration with Gson
Jackson is optional and therefore compilation fails while building a native image. Because Flyway already depends on Gson, it's better to use that instead
See https://github.com/quarkusio/quarkus/pull/34262#issuecomment-1612559070 for the error that's thrown in 9.20.0
@gastaldi We are looking to move away form GSON to Jackson as we use Jackson for other mapping as well as Json. As a result this PR is not compatible with that roadmap. Please bare with us.
|
gharchive/pull-request
| 2023-06-29T13:19:54 |
2025-04-01T04:34:17.500532
|
{
"authors": [
"Barry-RG",
"gastaldi"
],
"repo": "flyway/flyway",
"url": "https://github.com/flyway/flyway/pull/3697",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
2136175561
|
Initialize pixi project
We now specify dependencies in a pixi.toml file.
FAIM-Robocopy can be started with:
pixi run faim-robocopy
(Also bump the project version to 1.5.0)
NB: the environment activation script sets the path to TCL_LIBRARY and is currently implemented and tested for Windows only.
I updated the instructions in README.md and successfully tested on a multi-user system, so I am going to merge now.
|
gharchive/pull-request
| 2024-02-15T10:37:27 |
2025-04-01T04:34:17.512285
|
{
"authors": [
"imagejan"
],
"repo": "fmi-basel/faim-robocopy",
"url": "https://github.com/fmi-basel/faim-robocopy/pull/15",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1568609259
|
🛑 Site suite is down
In b380909, Site suite ($SECRET_SITE_1) was down:
HTTP code: 0
Response time: 0 ms
Resolved: Site suite is back up in dc323e8.
|
gharchive/issue
| 2023-02-02T18:54:31 |
2025-04-01T04:34:17.515855
|
{
"authors": [
"fmmaia"
],
"repo": "fmmaia/fmAtAllUptime",
"url": "https://github.com/fmmaia/fmAtAllUptime/issues/747",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
232986160
|
Access UIWindow
Where do i setup AppDelegate window and use it in the app where needed ?
Duplicate of issue 8
|
gharchive/issue
| 2017-06-01T19:32:39 |
2025-04-01T04:34:17.516820
|
{
"authors": [
"stami",
"tpatelattek"
],
"repo": "fmo91/PluggableApplicationDelegate",
"url": "https://github.com/fmo91/PluggableApplicationDelegate/issues/22",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
1935869383
|
🛑 Contaboo is down
In e244392, Contaboo (https://contabo.com) was down:
HTTP code: 403
Response time: 404 ms
Resolved: Contaboo is back up in a374e70 after 53 minutes.
|
gharchive/issue
| 2023-10-10T17:25:41 |
2025-04-01T04:34:17.540268
|
{
"authors": [
"fnzv"
],
"repo": "fnzv/status",
"url": "https://github.com/fnzv/status/issues/1058",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2152261680
|
🛑 Contaboo is down
In 1416808, Contaboo (https://contabo.com) was down:
HTTP code: 403
Response time: 560 ms
Resolved: Contaboo is back up in b3ddace after 18 hours, 44 minutes.
|
gharchive/issue
| 2024-02-24T11:07:24 |
2025-04-01T04:34:17.542515
|
{
"authors": [
"fnzv"
],
"repo": "fnzv/status",
"url": "https://github.com/fnzv/status/issues/2146",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2599323094
|
🛑 Contaboo is down
In 35bac7d, Contaboo (https://contabo.com) was down:
HTTP code: 403
Response time: 97 ms
Resolved: Contaboo is back up in 939d127 after 4 hours, 35 minutes.
|
gharchive/issue
| 2024-10-19T15:52:04 |
2025-04-01T04:34:17.544963
|
{
"authors": [
"fnzv"
],
"repo": "fnzv/status",
"url": "https://github.com/fnzv/status/issues/2986",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1867993720
|
🛑 Contaboo is down
In 0adf919, Contaboo (https://contabo.com) was down:
HTTP code: 403
Response time: 506 ms
Resolved: Contaboo is back up in bb87a42 after 968 days, 19 hours, 53 minutes.
|
gharchive/issue
| 2023-08-26T09:13:44 |
2025-04-01T04:34:17.547201
|
{
"authors": [
"fnzv"
],
"repo": "fnzv/status",
"url": "https://github.com/fnzv/status/issues/432",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1925397307
|
🛑 Contaboo is down
In 5b840d5, Contaboo (https://contabo.com) was down:
HTTP code: 403
Response time: 415 ms
Resolved: Contaboo is back up in da044cf after 1 hour, 52 minutes.
|
gharchive/issue
| 2023-10-04T04:46:12 |
2025-04-01T04:34:17.549433
|
{
"authors": [
"fnzv"
],
"repo": "fnzv/status",
"url": "https://github.com/fnzv/status/issues/951",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
132322872
|
Can not run main.py
As i followed the steps, i got stuck when running the main.py
[root@ip-10-0-7-118 Minecraft]# python main.py
Traceback (most recent call last):
File "main.py", line 7, in
from pyglet.gl import *
File "/usr/lib/python2.7/site-packages/pyglet/gl/init.py", line 97, in
from pyglet.gl.lib import GLException
File "/usr/lib/python2.7/site-packages/pyglet/gl/lib.py", line 142, in
from pyglet.gl.lib_glx import link_GL, link_GLU, link_GLX
File "/usr/lib/python2.7/site-packages/pyglet/gl/lib_glx.py", line 50, in
gl_lib = pyglet.lib.load_library('GL')
File "/usr/lib/python2.7/site-packages/pyglet/lib.py", line 160, in load_library
raise ImportError('Library "%s" not found.' % names[0])
ImportError: Library "GL" not found.
Can you tell me how to fix it please?
I'm running python 2.7.5 on Centos 7.2
Try this: http://stackoverflow.com/a/7941950/539465
Ah sorry i think i just forgot.
I don't have OS graphic version, now i'm running CentOS7 on Instance EC2 on AWS. That's totally command-line interface.
You need an X server to run this.
|
gharchive/issue
| 2016-02-09T03:33:32 |
2025-04-01T04:34:17.571159
|
{
"authors": [
"ProgVal",
"thinhduckhoi"
],
"repo": "fogleman/Minecraft",
"url": "https://github.com/fogleman/Minecraft/issues/69",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
226472672
|
Please add LICENSE file to repo
@fogleman - this looks fantastic.
Can you please add a "LICENSE" file to the top-level directory of the repo?
Ideally, you would choose Apache-2.0, MIT, or BSD, but choosing one is important to enable others to use your open source repo.
Thank you!
+1
|
gharchive/issue
| 2017-05-05T04:42:07 |
2025-04-01T04:34:17.573190
|
{
"authors": [
"adamluzsi",
"gmlewis"
],
"repo": "fogleman/fauxgl",
"url": "https://github.com/fogleman/fauxgl/issues/1",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
2152330200
|
Text in PDF recognized as gibberish in any PDFium viewer due to invalid bfrange definitions in ToUnicodeMap
Bug Report
Description of the problem
https://github.com/foliojs/pdfkit/blob/485b7e6bee6f3fa0ab9aa19647da838c482e3803/lib/font/embedded.js#L269-L271
Currently, our code generates all ToUnicodeMap entries on a single line. This yields invalid text mapping on any PDFium base viewers (and maybe others).
https://source.chromium.org/chromium/_/pdfium/pdfium.git/+/master:core/fpdfapi/font/cpdf_tounicodemap.cpp;l=171-172;drc=61bda438f9071586c92f8f626c29021524a8d0b0
uint32_t lowcode = lowcode_opt.value();
uint32_t highcode = (lowcode & 0xffffff00) | (highcode_opt.value() & 0xff);
Related Chromium bug: https://bugs.chromium.org/p/pdfium/issues/detail?id=1339#c1
The PDF spec doesn't give too much detail about beginbfrange. I looked around and found the doc below. Based on section 1.4.1 in that doc, the <19ff><1a00><63cf> beginbfrange entry is illegal. The first byte values should be the same for the two source range values in the entry.
https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/5411.ToUnicode.pdf
The link is moved or removed at this moment. I found another copy at http://www.audentia-gestion.fr/ADOBE/5411.ToUnicode.pdf
Screenshots
Google Chrome 122.0.6261.69 Linux x86_64
Chromium 122.0.6261.69 (Official Build) Arch Linux (64-bit)
WPS Office for Linux 11.1.0.11698
Firefox (pdf.js) - CORRECT
Adobe Acrobat Reader 2023.008.20533 64-bit on Windows 11 - CORRECT
Code sample
https://replit.com/@orzFly/pdfkit-tounicode?v=1
I used 258 glyphs in the document, so only the first two (258 % 256 = 2) glyphs is correct - yields "AB" correctly. All the rest are incorrect.
Your environment
pdfkit version: 0.12.3, or master
Node version: 12.22.9
Browser version:
Google Chrome 122.0.6261.69 Linux x86_64
WPS Office for Linux 11.1.0.11698
Chromium 122.0.6261.69 (Official Build) Arch Linux (64-bit)
Operating System: Linux x86_64
I have a possible fix - will send a pull request later. However, I am not sure how to add unit test about this particular behavior.
|
gharchive/issue
| 2024-02-24T14:03:12 |
2025-04-01T04:34:17.626326
|
{
"authors": [
"orzFly"
],
"repo": "foliojs/pdfkit",
"url": "https://github.com/foliojs/pdfkit/issues/1498",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
891318370
|
Incompatible with phaazon/hop.nvim
Hey, nice plugin!
romgrk/nvim-treesitter-context: seems like floating window showing content gets hidden when cursor is on the line matched by todo-comments.nvim
phaazon/hop.nvim: when hop displays its extmarks all other highlighting is disabled, but background of todo-comments.nvim strings prevails
Looks super great though!
Bonus question - how does it side with comment parser from treesitter? Should it be uninstalled? Can they be used together?
I want to say that the problem with treesitter-context happens regardless of this plugin; whenever your cursor is over a comment that plugin doesn't work at all in my experience.
@levouh thanks. I updated the title
|
gharchive/issue
| 2021-05-13T19:42:27 |
2025-04-01T04:34:17.628793
|
{
"authors": [
"cloggier",
"folke",
"levouh"
],
"repo": "folke/todo-comments.nvim",
"url": "https://github.com/folke/todo-comments.nvim/issues/5",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1213705822
|
bpf-sys, handle when /proc/version_signature is empty
Hello, I tried to compile my BPF program on a system that's running proxmox, but strangely the /proc/version_signature is empty - it seems like it's due to /boot/config-5.13.19-4-pve having an empty CONFIG_VERSION_SIGNATURE="".
Here's the exact error when running my loader:
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', /root/.cargo/registry/src/github.com-1ecc6299db9ec823/redbpf-2.3.0/src/lib.rs:2765:54
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
which refers to here. As I can see, the parse_version_signature doesn't handle the fact that /proc/version_signature can be empty, and so return a None.
Would you like me to create a PR to fix this issue, or do you need any more information? Thanks.
That's a good catch. I think it would make sense to get rid of this unwrap in fn get_version in addition to handling the case of an empty string in parse_version_signature.
get_version is used only in ModuleBuilder::parse, so this line can be easily replaced with something like get_version(&content).ok_or(Error::InvalidVersion).
Would I still be able to run the loader with your proposition? Looks like the version is used at other spots.
I'm thinking about checking in get_kernel_internal_version if the file is empty or not before calling parse_version_signature, to fallback to uname(). I think it's doesn't make a lot of sense to parse the version from a file that is empty 🤔 .
checking in get_kernel_internal_version if the file is empty or not before calling parse_version_signature
Sure, but fs::read_to_string should take care of that for you because there's no data associated with inode - so checking if a file is empty would be superfluous. So I would just do something like
let mut version = None;
if let Ok(version) = fs::read_to_string("/proc/version_signature") {
version = parse_version_signature(&version.trim())?
}
if version.is_none() {
version = to_str(&uname().ok()?.release).into()
}
parse_version(&version).map(|(major, minor, patch)| major << 16 | minor << 8 | patch)
Would I still be able to run the loader with your proposition?
I think so - in this case the get_kernel_internal_version call should fall back to uname() and if that fails then it's a legit error which is better conveyed through returning an Error variant instead of panicking through unwrap().
Looks great, should I create a PR for this fix?
should I create a PR for this fix?
Sure, it would be very appreciated! :)
Closing since merged with #322, thanks!
|
gharchive/issue
| 2022-04-24T16:51:04 |
2025-04-01T04:34:17.647523
|
{
"authors": [
"QuiiBz",
"nbaksalyar"
],
"repo": "foniod/redbpf",
"url": "https://github.com/foniod/redbpf/issues/320",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
2523611335
|
Remove references to "proposal=legacy:check-number"
I'm preparing a list of ancient numerical check-IDs and their current IDs.
I'll post them here later. I've opened this issue so that I can have an issue URL to place on the source in place of the old "proposal=legacy" entries.
As of today, at https://github.com/fonttools/fontbakery/commit/2ebcbe13cc153c0cae4cb788958eb229062ea930, this is the list of check-IDs that were originally (many years ago) referred to by numerical IDs. I'm keeping this list here just in case it may be useful for someone in the future.
Nowadays all checks must have detailed rationale description. But many of these older checks originally lacked such detailed documentation. As we continue developing the collection of checks, I recommend that the links to this issue can be gradually removed, as we feel that the other discussions about the checks (also linked via URLs in their proposal field) can serve as better / more solid justification for their QA routine implementations.
001: googlefonts/canonical_filename
002: family/single_directory
003: googlefonts/description/broken_links
004: googlefonts/description/valid_html
005: googlefonts/description/min_length
008: opentype/family/underline_thickness
010: opentype/family/panose_familytype
014: opentype/family/equal_font_versions
015: opentype/post_table_version
016: googlefonts/fstype
018: googlefonts/vendor_id
019: googlefonts/name/unwanted_chars
020: googlefonts/usweightclass
028: googlefonts/family/has_license
029: googlefonts/name/license
030: googlefonts/name/license_url
031: opentype/name/no_copyright_on_description
032: googlefonts/name/description_max_length
033: opentype/monospace
034: opentype/xavgcharwidth
036: ots
037: fontvalidator
040: family/win_ascent_and_descent
042: os2_metrics_match_hhea
043: opentype/unitsperem
044: opentype/font_version
045: opentype/dsig
046: mandatory_glyphs
047: whitespace_glyphs
048: whitespace_glyphnames
049: whitespace_ink
050: whitespace_widths
052: required_tables
053: unwanted_tables
054: hinting_impact
055: googlefonts/name/version_format
056: googlefonts/old_ttfautohint
057: googlefonts/name/line_breaks
058: valid_glyphnames
059: unique_glyphnames
062: googlefonts/gasp
063: opentype/gpos_kerning_info
066: opentype/kern_table
067: googlefonts/name/familyname_first_char
068: opentype/name/match_familyname_fullfont
069: opentype/glyf_unused_data
071: opentype/family_naming_recommendations
072: smart_dropout
073: opentype/maxadvancewidth
074: name/ascii_only_entries
083: googlefonts/metadata/unique_full_name_values
084: googlefonts/metadata/unique_weight_style_pairs
085: googlefonts/metadata/license
086: googlefonts/metadata/menu_and_latin
087: googlefonts/metadata/subsets_order
088: googlefonts/metadata/copyright
089: googlefonts/metadata/familyname
090: googlefonts/metadata/has_regular
091: googlefonts/metadata/regular_is_400
093: googlefonts/metadata/nameid/post_script_name
095: googlefonts/metadata/nameid/font_name
096: googlefonts/metadata/match_fullname_postscript
097: googlefonts/metadata/match_filename_postscript
099: googlefonts/metadata/valid_full_name_values
100: googlefonts/metadata/valid_filename_values
101: googlefonts/metadata/valid_post_script_name_values
103: googlefonts/metadata/reserved_font_name
108: googlefonts/metadata/nameid/family_and_full_names
110: googlefonts/metadata/match_name_familyname
111: googlefonts/metadata/canonical_weight_value
112: googlefonts/metadata/os2_weightclass
113: googlefonts/metadata/match_weight_postscript
115: googlefonts/metadata/canonical_style_names
116: googlefonts/unitsperem
117: googlefonts/version_bump
118: googlefonts/production_glyphs_similarity
129: opentype/fsselection
130: opentype/italic_angle
131: opentype/mac_style
153: contour_count
154: googlefonts/production_encoded_glyphs
155: googlefonts/font_copyright
156: googlefonts/name/mandatory_entries
180: opentype/loca/maxp_num_glyphs
|
gharchive/issue
| 2024-09-13T00:46:10 |
2025-04-01T04:34:17.679970
|
{
"authors": [
"felipesanches"
],
"repo": "fonttools/fontbakery",
"url": "https://github.com/fonttools/fontbakery/issues/4829",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
391683251
|
pyftmerge: getting OverflowError
When I tried to merge fonts covering the range of U + 100000 to U + 10EA5F and fonts covering U + 10EA60 to U + 10FFF5, I got the following error.
Traceback (most recent call last):
File "c:\python2715\lib\runpy.py", line 174, in _run_module_as_main
"main", fname, loader, pkg_name)
File "c:\python2715\lib\runpy.py", line 72, in run_code
exec code in run_globals
File "C:\Python2715\Scripts\pyftmerge.exe_main.py", line 9, in
File "c:\python2715\lib\site-packages\fontTools\misc\loggingTools.py", line 375, in wrapper
return func(*args, **kwds)
File "c:\python2715\lib\site-packages\fontTools\merge.py", line 1125, in main
font.save(outfile)
File "c:\python2715\lib\site-packages\fontTools\ttLib\ttFont.py", line 173, in save
writer_reordersTables = self._save(tmp)
File "c:\python2715\lib\site-packages\fontTools\ttLib\ttFont.py", line 212, in _save
self._writeTable(tag, writer, done, tableCache)
File "c:\python2715\lib\site-packages\fontTools\ttLib\ttFont.py", line 633, in _writeTable
tabledata = self.getTableData(tag)
File "c:\python2715\lib\site-packages\fontTools\ttLib\ttFont.py", line 651, in getTableData
return self.tables[tag].compile(self)
File "c:\python2715\lib\site-packages\fontTools\ttLib\tables_p_o_s_t.py", line 51, in compile
data = data + self.encode_format_2_0(ttFont)
File "c:\python2715\lib\site-packages\fontTools\ttLib\tables_p_o_s_t.py", line 173, in encode_format_2_0
indices.append(index)
OverflowError: unsigned short is greater than maximum
you're trying to pack too many glyphs into a single opentype font. you can't fit more than 65535 glyphs.
Fonts that support the range U+100000 to U+10EA5F have 60003 glyphs(include 3 other glyphs). The font that supports U + 10EA 60 to U + 10 FFF 5 has 5527 (include 1 other glyph)glyphs. Since the total number of glyphs expected after merging is 65530, I think that there are five margins.
right ok, then your fonts probably aren't including glyph names from the "standard macintosh set" so all glyph names in post table format 2.0 end up in the extra names, but post format 2.0 only has room between 258 and 65535 for these:
If the name index is between 0 and 257, treat the name index as a glyph index in the Macintosh standard order. If the name index is between 258 and 65535, then subtract 258 and use that to index into the list of Pascal strings at the end of the table.
https://docs.microsoft.com/en-us/typography/opentype/spec/post
I'd recommend you switch to post table format 3.0, which basically means dropping all the glyph names.
try something like this
from fontTools.ttLib import TTFont
font = TTFont("myfont.ttf")
font["post"].formatType = 3.0
font.save("myfont2.ttf")
Thank you! It went well!
|
gharchive/issue
| 2018-12-17T12:08:01 |
2025-04-01T04:34:17.689063
|
{
"authors": [
"anthrotype",
"dadasutasudadas"
],
"repo": "fonttools/fonttools",
"url": "https://github.com/fonttools/fonttools/issues/1412",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
673596744
|
When running ./quickstart-setup-store.sh test I recieve the following error
ERROR running force:data:tree:import: {"hasErrors":true,"results":[{"referenceId":"PricebookEntryRef2","errors":[{"statusCode":"REQUIRED_FIELD_MISSING","message":"Required fields are missing: [Pricebook2Id]","fields":["Pricebook2Id"]}]},{"referenceId":"PricebookEntryRef4","errors":[{"statusCode":"REQUIRED_FIELD_MISSING","message":"Required fields are missing: [Pricebook2Id]","fields":["Pricebook2Id"]}]},{"referenceId":"PricebookEntryRef6","errors":[{"statusCode":"REQUIRED_FIELD_MISSING","message":"Required fields are missing: [Pricebook2Id]","fields":["Pricebook2Id"]}]},{"referenceId":"PricebookEntryRef8","errors":[{"statusCode":"REQUIRED_FIELD_MISSING","message":"Required fields are missing: [Pricebook2Id]","fields":["Pricebook2Id"]}]},{"referenceId":"PricebookEntryRef10","errors":[{"statusCode":"REQUIRED_FIELD_MISSING","message":"Required fields are missing: [Pricebook2Id]","fields":["Pricebook2Id"]}]},{"referenceId":"PricebookEntryRef12","errors":[{"statusCode":"REQUIRED_FIELD_MISSING","message":"Required fields are missing: [Pricebook2Id]","fields":["Pricebook2Id"]}]},{"referenceId":"PricebookEntryRef14","errors":[{"statusCode":"REQUIRED_FIELD_MISSING","message":"Required fields are missing: [Pricebook2Id]","fields":["Pricebook2Id"]}]},{"referenceId":"PricebookEntryRef16","errors":[{"statusCode":"REQUIRED_FIELD_MISSING","message":"Required fields are missing: [Pricebook2Id]","fields":["Pricebook2Id"]}]},{"referenceId":"PricebookEntryRef18","errors":[{"statusCode":"REQUIRED_FIELD_MISSING","message":"Required fields are missing: [Pricebook2Id]","fields":["Pricebook2Id"]}]},{"referenceId":"PricebookEntryRef20","errors":[{"statusCode":"REQUIRED_FIELD_MISSING","message":"Required fields are missing: [Pricebook2Id]","fields":["Pricebook2Id"]}]},{"referenceId":"PricebookEntryRef22","errors":[{"statusCode":"REQUIRED_FIELD_MISSING","message":"Required fields are missing: [Pricebook2Id]","fields":["Pricebook2Id"]}]},{"referenceId":"PricebookEntryRef24","errors":[{"statusCode":"REQUIRED_FIELD_MISSING","message":"Required fields are missing: [Pricebook2Id]","fields":["Pricebook2Id"]}]},{"referenceId":"PricebookEntryRef26","errors":[{"statusCode":"REQUIRED_FIELD_MISSING","message":"Required fields are missing: [Pricebook2Id]","fields":["Pricebook2Id"]}]},{"referenceId":"PricebookEntryRef28","errors":[{"statusCode":"REQUIRED_FIELD_MISSING","message":"Required fields are missing: [Pricebook2Id]","fields":["Pricebook2Id"]}]},{"referenceId":"PricebookEntryRef30","errors":[{"statusCode":"REQUIRED_FIELD_MISSING","message":"Required fields are missing: [Pricebook2Id]","fields":["Pricebook2Id"]}]},{"referenceId":"PricebookEntryRef32","errors":[{"statusCode":"REQUIRED_FIELD_MISSING","message":"Required fields are missing: [Pricebook2Id]","fields":["Pricebook2Id"]}]},{"referenceId":"PricebookEntryRef34","errors":[{"statusCode":"REQUIRED_FIELD_MISSING","message":"Required fields are missing: [Pricebook2Id]","fields":["Pricebook2Id"]}]}]} 5. Mapping Admin User to Role. ERROR running force:data:record:update: An unexpected error occurred. Please include this ErrorId if you contact support: 1677524363-167767 (2074184818) 6. Creating Buyer User with associated Contact and Account. ERROR running force:user:create: Insert failed. First exception on row 0; first error: UNKNOWN_EXCEPTION, portal account owner must have a role: [] Making Account a Buyer Account. ERROR running force:data:record:create: Required fields are missing: [BuyerId] Assigning Buyer Account to Buyer Group. ERROR running force:data:record:create: Required fields are missing: [BuyerId]
@itsallrelative thank you for letting us know about this! The errors you mention should now be fixed or worked around. Please try again with a new scratch org.
|
gharchive/issue
| 2020-08-05T14:45:20 |
2025-04-01T04:34:17.745981
|
{
"authors": [
"cnastasa",
"itsallrelative"
],
"repo": "forcedotcom/b2b-commerce-on-lightning-quickstart",
"url": "https://github.com/forcedotcom/b2b-commerce-on-lightning-quickstart/issues/1",
"license": "CC0-1.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1340838434
|
(7.163.0) sfdx force:source:deploy throwing UNKNOWN_EXCEPTION
Summary
When trying to deploy our source metadata using sfdx force:source:deploy it throws UNKNOWN_EXCEPTION: An unexpected error occurred. Please include this ErrorId if you contact support: 1556838228-417394 (-1488516052).
Full command is sfdx force:source:deploy -p "/builds/services/dcms/financialforce/thunder/force-app/" -w 0 -u TARGET_ORG -l NoTestRun --json | ConvertFrom-Json
It is erroring in v7.164.1 as well.
No error on v7.162.0
Steps To Reproduce:
Run sfdx force:source:deploy -p "/builds/services/dcms/financialforce/thunder/force-app/" -w 0 -u TARGET_ORG -l NoTestRun --json | ConvertFrom-Json
Expected result
Create a deploy on TARGET_ORG
Actual result
No deploy created and sfdx command returns UNKNOWN_EXCEPTION: An unexpected error occurred. Please include this ErrorId if you contact support: 1556838228-417394 (-1488516052)
System Information
Tested on cmd and powershell on docker
CMD:
{
"cliVersion": "sfdx-cli/7.162.0",
"architecture": "win32-x64",
"nodeVersion": "node-v16.17.0",
"pluginVersions": [
"@oclif/plugin-autocomplete 0.3.0 (core)",
"@oclif/plugin-commands 1.3.0 (core)",
"@oclif/plugin-help 3.3.1 (core)",
"@oclif/plugin-not-found 1.2.6 (core)",
"@oclif/plugin-plugins 1.10.11 (core)",
"@oclif/plugin-update 1.5.0 (core)",
"@oclif/plugin-warn-if-update-available 1.7.3 (core)",
"@oclif/plugin-which 1.0.4 (core)",
"@salesforce/sfdx-plugin-lwc-test 1.0.0 (core)",
"alias 2.1.0 (core)",
"apex 1.1.0 (core)",
"auth 2.2.3 (core)",
"community 2.0.0 (core)",
"config 1.4.14 (core)",
"custom-metadata 2.0.0 (core)",
"data 2.1.1 (core)",
"generator 2.0.2 (core)",
"info 2.0.1 (core)",
"limits 2.0.1 (core)",
"org 2.0.7 (core)",
"salesforce-alm 54.6.4 (core)",
"schema 2.1.1 (core)",
"sfdx-cli 7.162.0 (core)",
"signups 1.2.0 (core)",
"source 2.0.11 (core)",
"telemetry 2.0.0 (core)",
"templates 55.0.0 (core)",
"trust 2.0.3 (core)",
"user 2.1.0 (core)"
],
"osVersion": "Windows_NT 10.0.19042"
}
Docker:
{
"cliVersion": "sfdx-cli/7.160.0",
"architecture": "linux-x64",
"nodeVersion": "node-v14.20.0",
"pluginVersions": [
"@oclif/plugin-autocomplete 0.3.0 (core)",
"@oclif/plugin-commands 1.3.0 (core)",
"@oclif/plugin-help 3.3.1 (core)",
"@oclif/plugin-not-found 1.2.6 (core)",
"@oclif/plugin-plugins 1.10.11 (core)",
"@oclif/plugin-update 1.5.0 (core)",
"@oclif/plugin-warn-if-update-available 1.7.3 (core)",
"@oclif/plugin-which 1.0.4 (core)",
"@salesforce/sfdx-plugin-lwc-test 1.0.0 (core)",
"alias 2.1.0 (core)",
"apex 1.1.0 (core)",
"auth 2.2.2 (core)",
"community 2.0.0 (core)",
"config 1.4.14 (core)",
"custom-metadata 2.0.0 (core)",
"data 2.0.4 (core)",
"generator 2.0.2 (core)",
"info 2.0.1 (core)",
"limits 2.0.1 (core)",
"org 2.0.3 (core)",
"salesforce-alm 54.6.2 (core)",
"schema 2.1.1 (core)",
"sfdx-cli 7.160.0 (core)",
"signups 1.2.0 (core)",
"source 2.0.7 (core)",
"telemetry 2.0.0 (core)",
"templates 55.0.0 (core)",
"trust 2.0.1 (core)",
"user 2.1.0 (core)"
],
"osVersion": "Linux 5.4.0-1085-azure"
}
Additional information
Feel free to attach a screenshot.
@Renan-Mastropaolo are you able to provide a project that replicates the issue? Thanks!
Hello @mdonnalley ,
Sorry but I can not provide you the project our company uses, it is private.
But I can perform tests myself and report you the results.
I will start by cleaning up the project and adding one metadata type at a time to see if I found anything, if you have any other test in mind please let me know so I try it as well.
Thanks.
I have just found one thing, both my test were done using sfdx installed using npm install -g sfdx-cli@latest command. On my Windows machine, I uninstalled sfdx using npm uninstall -g sfdx-cli and installed using the EXE file on official website and it is now deploying with the same command, maybe it is something related to that?
I do not think that's the case, during my tests I've been uninstalling and reinstalling the same version and other versions multiple times with the same behavior all the time.
And on the docker side, every time we run a deploy a new docker instance is created, uninstalling and installing v7.163.0 version all the time.
Anyway, I will uninstall the standalone version and reinstall the npm one right now, just give me a sec.
Thanks
@mdonnalley Same issue after uninstalling EXE version and installing npm again
@Renan-Mastropaolo thanks for testing that out for me. At this point I'll need to investigate that error id you provided in the original description to see if there are any clues there. I'll let you know if I learn anything
Thank you.
I will keep testing some more scenarios in the meantime.
Obter o Outlook para Androidhttps://aka.ms/AAb9ysg
From: Mike Donnalley @.>
Sent: Wednesday, August 17, 2022 5:27:26 PM
To: forcedotcom/cli @.>
Cc: Mastropaolo, Renan @.>; Mention @.>
Subject: Re: [forcedotcom/cli] (7.163.0) sfdx force:source:deploy throwing UNKNOWN_EXCEPTION (Issue #1673)
[EXTERNAL EMAIL]
@Renan-Mastropaolo [github.com]https://urldefense.com/v3/__https://github.com/Renan-Mastropaolo__;!!LpKI!gPuRhpfGGOSgJ281U3oJs6f31GrQgvD_Bix0P0O8NjUVHxripUUq_ePNugMf0ZNDiuuv8klm76pTpJdWMbpOdfbqiPaPCQ$ thanks for testing that out for me. At this point I'll need to investigate that error id you provided in the original description to see if there are any clues there. I'll let you know if I learn anything
—
Reply to this email directly, view it on GitHub [github.com]https://urldefense.com/v3/__https://github.com/forcedotcom/cli/issues/1673*issuecomment-1218458939__;Iw!!LpKI!gPuRhpfGGOSgJ281U3oJs6f31GrQgvD_Bix0P0O8NjUVHxripUUq_ePNugMf0ZNDiuuv8klm76pTpJdWMbpOdfYsnXYpeA$, or unsubscribe [github.com]https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/A2R2TJ3367GBAEN3QW2Y7Z3VZVDK5ANCNFSM56XD7RDA__;!!LpKI!gPuRhpfGGOSgJ281U3oJs6f31GrQgvD_Bix0P0O8NjUVHxripUUq_ePNugMf0ZNDiuuv8klm76pTpJdWMbpOdfaiMgWJgg$.
You are receiving this because you were mentioned.Message ID: @.***>
Internal Use - Confidential
Hey @mdonnalley, On our docker image, I've uninstalled the npm version and used the one on this tutorial (https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_setup_install_cli.htm#sfdx_setup_install_cli_linux) using the .tar.xz file and it worked as well.
Looks like it is something related to the npm installation.
Hello,
Had a similar issue one week ago and the same as @Renan-Mastropaolo after changing the CLI installation file from npm to tar file error has been solved.
But today, I am getting a similar UNKNOWN_ERROR issue with the npm and tar file both with the 7.164.2 version.
After downgrading to the 7.163.0 version everything work well.
I opened the case to Salesforce Support, they provided me the server log as below:
Thrown: java.util.zip.ZipException: only DEFLATED entries can have EXT descriptor
Date: Fri, 19 Aug 2022 01:39:19 +0000 (GMT)
And log message does not give me any insight or tips on how to solve the issue.
Maybe it's related to how CLI converts sources to metadata zip archive at force:source:deploy command.
Hello everyone, confirmed on my side that 7.164.2 indeed cause the same error (UNKNOWN_EXCEPTION: An unexpected error occurred. Please include this ErrorId if you contact support: 1801400831-592134 (-1488516052)), with both npm and tar.xz/.exe versions.
Hello, there is definitely something odd with 7.164.2, for a bit more input: we are using exclusively Github Actions, and our workflow didn't work with 7.164.2 either from npm or tar files. For now, we are stickling with 7.163.0 tar and it works fine.
*** Deploying with SOAP API v55.0 ***
ERROR running force:source:deploy: UNKNOWN_EXCEPTION: An unexpected error occurred. Please include this ErrorId if you contact support: 1671461828-106631 (-1488516052)
@isaiassilva-osf @Renan-Mastropaolo @LeoCordiuS A couple of follow up questions:
Can you try deploying with v7.164.1?
Can you share the output of sfdx plugins:inspect @salesforce/plugin-source?
Thanks!
@mdonnalley
Tested on 7.164.1 and 7.164.0, both npm and .tar.xz failed to deploy with the same error message.
7.164.2 --> npm version
└─ @salesforce/plugin-source
├─ version 2.0.12
├─ homepage https://github.com/salesforcecli/plugin-source
├─ location C:\Users\Renan_Mastropaolo\AppData\Roaming\npm\node_modules\sfdx-cli\node_modules\@salesforce\plugin-source
├─ commands
│ ├─ force
│ ├─ force:mdapi:convert
│ ├─ force:mdapi:deploy
│ ├─ force:mdapi:deploy:cancel
│ ├─ force:mdapi:deploy:report
│ ├─ force:mdapi:describemetadata
│ ├─ force:mdapi:listmetadata
│ ├─ force:mdapi:retrieve
│ ├─ force:mdapi:retrieve:report
│ ├─ force:source:convert
│ ├─ force:source:delete
│ ├─ force:source:deploy
│ ├─ force:source:deploy:cancel
│ ├─ force:source:deploy:report
│ ├─ force:source:ignored:list
│ ├─ force:source:manifest:create
│ ├─ force:source:open
│ ├─ force:source:pull
│ ├─ force:source:push
│ ├─ force:source:retrieve
│ ├─ force:source:status
│ ├─ force:source:tracking:clear
│ └─ force:source:tracking:reset
└─ dependencies
├─ @oclif/core ^1.9.5 => 1.13.10
├─ @oclif/plugin-help ^3.3.1 => 3.3.1
├─ @salesforce/apex-node ^1.0.0 => 1.1.0
├─ @salesforce/command ^5.2.1 => 5.2.4
├─ @salesforce/core ^3.21.5 => 3.26.2
├─ @salesforce/kit ^1.5.41 => 1.5.45
├─ @salesforce/source-deploy-retrieve ^6.2.6 => 6.3.0
├─ @salesforce/source-tracking ^2.1.2 => 2.2.2
├─ chalk ^4.1.2 => 4.1.2
├─ got ^11.8.3 => 11.8.5
├─ jsforce ^2.0.0-beta.16 => 2.0.0-beta.18
├─ open ^8.4.0 => 8.4.0
├─ proxy-agent ^5.0.0 => 5.0.0
├─ proxy-from-env ^1.1.0 => 1.1.0
└─ tslib ^2 => 2.4.0
7.164.2 --> .tar.xz version
└─ @salesforce/plugin-source
├─ version 2.0.12
├─ homepage https://github.com/salesforcecli/plugin-source
├─ location /root/sfdx/node_modules/@salesforce/plugin-source
├─ commands
│ ├─ force
│ ├─ force:mdapi:convert
│ ├─ force:mdapi:deploy
│ ├─ force:mdapi:deploy:cancel
│ ├─ force:mdapi:deploy:report
│ ├─ force:mdapi:describemetadata
│ ├─ force:mdapi:listmetadata
│ ├─ force:mdapi:retrieve
│ ├─ force:mdapi:retrieve:report
│ ├─ force:source:convert
│ ├─ force:source:delete
│ ├─ force:source:deploy
│ ├─ force:source:deploy:cancel
│ ├─ force:source:deploy:report
│ ├─ force:source:ignored:list
│ ├─ force:source:manifest:create
│ ├─ force:source:open
│ ├─ force:source:pull
│ ├─ force:source:push
│ ├─ force:source:retrieve
│ ├─ force:source:status
│ ├─ force:source:tracking:clear
│ └─ force:source:tracking:reset
└─ dependencies
├─ @oclif/core ^1.9.5 => 1.13.10
├─ @oclif/plugin-help ^3.3.1 => 3.3.1
├─ @salesforce/apex-node ^1.0.0 => 1.1.0
├─ @salesforce/command ^5.2.1 => 5.2.4
├─ @salesforce/core ^3.21.5 => 3.26.2
├─ @salesforce/kit ^1.5.41 => 1.5.45
├─ @salesforce/source-deploy-retrieve ^6.2.6 => 6.3.0
├─ @salesforce/source-tracking ^2.1.2 => 2.2.2
├─ chalk ^4.1.2 => 4.1.2
├─ got ^11.8.3 => 11.8.5
├─ jsforce ^2.0.0-beta.16 => 2.0.0-beta.18
├─ open ^8.4.0 => 8.4.0
├─ proxy-agent ^5.0.0 => 5.0.0
├─ proxy-from-env ^1.1.0 => 1.1.0
└─ tslib ^2 => 2.4.0
I am witnessing the same issue on multiple versions of the CLI:
Versions with error codes:
7.163.0 - 1256550982-117127 (-1488516052)
7.162.0 - 2063887122-299599 (-1488516052)
7.159.0 - 1334184225-265985 (-1488516052)
7.158.0 - 125231351-244937 (-1488516052)
7.157.0 - 219879244-5650 (-1488516052)
@rob-baillie-ortoo maybe if you install 7.163.0 with .tar.xz or .exe file this issue will not happen again.
Same error with v7.165.0 installed thru .exe file
UNKNOWN_EXCEPTION: An unexpected error occurred. Please include this ErrorId if you contact support: 256389163-55367 (-1488516052)
@mdonnalley I just saw that I've never posted the full json response I got, with stack. Here you go (v7.165.0)
{
"status": 1,
"name": "sf:UNKNOWN_EXCEPTION",
"message": "UNKNOWN_EXCEPTION: An unexpected error occurred. Please include this ErrorId if you contact support: 256389163-55367 (-1488516052)",
"exitCode": 1,
"context": "Deploy",
"stack": "sf:UNKNOWN_EXCEPTION: UNKNOWN_EXCEPTION: An unexpected error occurred. Please include this ErrorId if you contact support: 256389163-55367 (-1488516052)\n at Function.wrap (C:\Users\Renan_Mastropaolo\AppData\Local\sfdx\client\7.165.0-65b4bb0\node_modules\@salesforce\core\lib\sfError.js:61:25)\n at Deploy.catch (C:\Users\Renan_Mastropaolo\AppData\Local\sfdx\client\7.165.0-65b4bb0\node_modules\@salesforce\command\lib\sfdxCommand.js:267:38)\n at processTicksAndRejections (node:internal/process/task_queues:96:5)\n at async Deploy._run (C:\Users\Renan_Mastropaolo\AppData\Local\sfdx\client\7.165.0-65b4bb0\node_modules\@salesforce\command\lib\sfdxCommand.js:93:13)\n at async Config.runCommand (C:\Users\Renan_Mastropaolo\AppData\Local\sfdx\client\7.165.0-65b4bb0\node_modules\@oclif\core\lib\config\config.js:272:25)\n at async run (C:\Users\Renan_Mastropaolo\AppData\Local\sfdx\client\7.165.0-65b4bb0\node_modules\@oclif\core\lib\main.js:76:5)",
"warnings": [],
"commandName": "Deploy"
}
a.) Issue seen in sfdx-cli/7.165.0 linux-x64 node-v16.13.2
ERROR running force:source:deploy: UNKNOWN_EXCEPTION: An unexpected error occurred. Please include this ErrorId if you contact support: 363786184-312086 (-1488516052)
b.) Works fine with sfdx-cli/7.159.0 linux-x64 node-v16.13.2
Hello all, just wanted to follow up to let you know that we've got a ticket created and will be looking into this soon. Feel free to post any additional details you come across. Thanks!
@Renan-Mastropaolo - Have witnessed it when downloading 7.165.0 as a tar.xz
Have also seen it on:
Windows Server 2022
Ubuntu 22.04
Ubuntu 20.04
macOS Monterey 12
Have also seen it when performing both a push and a deploy.
@iowillhoit - thanks for taking a look
It looks like this GACK is reproducable with a .bin extension static resource of zero size and the following meta file:
<?xml version="1.0" encoding="UTF-8"?> <StaticResource xmlns="http://soap.sforce.com/2006/04/metadata"> <cacheControl>Public</cacheControl> <contentType>application/octet-stream</contentType> </StaticResource>
Issue can be replicated with the attached project. See the README for details
gack-replication.zip
Hey @rob-baillie-ortoo, thanks for that .zip, I was able to replicate the issue with it!
As you mentioned the crux of the issue seems to revolve around the pleasewait.bin in that .zip which is just an empty file. But if you add any content to it at all, like just the letter a or a random string, then the deploy proceeds without throwing a GACK.
Is anybody in this thread that's encountering this issue purposefully trying to deploy an empty file with their metadata?
If not, could you please try the following?
Set the SFDX_MDAPI_TEMP_DIR env var to a valid directory
Run the deploy again
Compare the metadata files in your project to the ones in the SFDX_MDAPI_TEMP_DIR dir
Post here with your results
I'm particularly interested to see if any files show up as size 0 in the SFDX_MDAPI_TEMP_DIR that weren't size 0 in your project dir.
I'm wondering if for some reason the CLI is accidentally deleting file contents when zipping them up for some metadata types. I haven't been able to find any instances of that happening in my testing so far though.
We were purposefully deploying an empty file since we're in ISV using 1st generation packaging and cannot delete a defunct static resource - the ideal is that any deprecated binary files are empty. We have had to work around by putting contents into the file, which we would prefer not to have to do.
I have also now witnessed the problem with an empty css file in an LWC bundle
I had one empty file on staticResources, after I deleted that file the error is fixed. Thank you for the workaround.
Thanks for the extra context @rob-baillie-ortoo, I don't want you to have to put meaningless content in your files either but I'm not sure why these deploys work with versions 7.163.0 or less of the CLI but not with newer versions.
I'll dig into that a little more but if I were to hazard a guess I'd say maybe earlier versions of the CLI didn't bundle empty files into the .zip sent to the org. Would that be acceptable for your use case?
From my side we expect to be able to deploy staticResources, or other metadata types, with empty content. We do it currently on our Production ORG.
The fix is out now in the stable-rc channel for the installers or latest-rc tag for npm installs.
• Update with npm: npm install -g sfdx-cli@latest-rc
• Update with Installer: sfdx update stable-rc (run sfdx update stable to rollback)
Hi everyone, just a quick update.
My apologies but there was an issue with our release last Thursday and the fix didn't actually go out with version 7.169.0 like we had thought.
We just released a new release candidate, version 7.169.1, that I have confirmed has the fix. As usual, you can update your CLI like so:
• Update with npm: npm install -g sfdx-cli@latest-rc
• Update with Installer: sfdx update stable-rc (run sfdx update stable to rollback)
Appears fixed for me.
|
gharchive/issue
| 2022-08-16T20:22:13 |
2025-04-01T04:34:17.796767
|
{
"authors": [
"LeoCordiuS",
"Renan-Mastropaolo",
"RodEsp",
"iowillhoit",
"isaiassilva-osf",
"mdonnalley",
"rob-baillie-ortoo",
"vaibhavdangar-woolies"
],
"repo": "forcedotcom/cli",
"url": "https://github.com/forcedotcom/cli/issues/1673",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
1460327846
|
sfdx:force:data:record:create and sfdx:force:data:record:update are trimming single quotes from values
Summary
sfdx:force:data:record:create and sfdx:force:data:record:update are trimming single quotes from values
Steps To Reproduce:
sfdx force:data:record:update -u sfUserName -s SObjectName -i SObjectID -v "field__c='Won't fix'" --json
sfdx force:data:record:update -u sfUserName -s SObjectName -i SObjectID -v "field__c='Won\\'t fix'" --json
sfdx force:data:record:update -u sfUserName -s SObjectName -i SObjectID -v "field__c='Won''t fix'" --json
sfdx force:data:record:update -u sfUserName -s SObjectName -i SObjectID -v "field__c='Won\\''t fix'" --json
Expected result
The value should be uploaded with single quotes present as the value is a contraction.
Actual result
The value has single quotes removed even when escaped.
System Information
Which shell/terminal are you using? (e.g. bash, zsh, powershell 5, powershell 7, cmd.exe, etc.)
git bash windows 10
see below for sfdx version --verbose --json
{
"cliVersion": "sfdx-cli/7.173.0",
"architecture": "win32-x64",
"nodeVersion": "node-v16.14.0",
"pluginVersions": [
"@oclif/plugin-autocomplete 1.3.1 (core)",
"@oclif/plugin-commands 2.2.0 (core)",
"@oclif/plugin-help 5.1.14 (core)",
"@oclif/plugin-not-found 2.3.3 (core)",
"@oclif/plugin-plugins 2.1.1 (core)",
"@oclif/plugin-update 3.0.2 (core)",
"@oclif/plugin-version 1.1.2 (core)",
"@oclif/plugin-warn-if-update-available 2.0.6 (core)",
"@oclif/plugin-which 2.1.0 (core)",
"alias 2.1.5 (core)",
"apex 1.3.0 (core)",
"auth 2.2.14 (core)",
"community 2.0.7 (core)",
"config 1.4.21 (core)",
"custom-metadata 2.0.1 (core)",
"data 2.1.4 (core)",
"generator 2.0.6 (core)",
"info 2.1.10 (core)",
"limits 2.0.5 (core)",
"org 2.2.9 (core)",
"packaging 1.9.4 (core)",
"schema 2.1.10 (core)",
"signups 1.2.7 (core)",
"source 2.0.19 (core)",
"telemetry 2.0.2 (core)",
"templates 55.1.0 (core)",
"trust 2.0.4 (core)",
"user 2.1.12 (core)",
"@salesforce/sfdx-plugin-lwc-test 1.0.1 (core)",
"salesforce-alm 54.8.1 (core)"
],
"osVersion": "Windows_NT 10.0.19044",
"shell": "C:\Users\USERNAME\AppData\Local\Programs\Git\usr\bin\bash.exe",
"rootPath": "C:\Users\USERNAME\AppData\Roaming\npm\node_modules\sfdx-cli"
}
Hey @jamesedwardsvtgov, I think I have a fix for this but wanted your opinion.
If you ran the following would you be ok with the value of field__c being 'Won't Fix'?
sfdx force:data:record:create -s SObjectName -v "field__c='Won't fix'"
In order to get the value to just be Won't Fix you'd have to run it without the ' surrounding it, like so:
sfdx force:data:record:create -s SObjectName -v "field__c=Won't fix"
Hi @RodEsp thank you for this comment.
The field is used in a roll-up calculation and the value that is used to calculate is managed - so the value in this case would need to be Won't Fix with the apostrophe included.
Unfortunately as shown in the original issue summary, both examples are not working as expected and the single quote is removed.
I do see there is a PR open for this and we'll look forward to a resolution.
Thank you and this is greatly appreciated!
Hi @RodEsp
Thank you for these updates! I have installed the latest-rc with the command you provided npm install sfdx-cli@latest-rc -g
With the latest release candidate apostrophes are no long removed from the value, which is solving the original issue!
Unfortunately, there is a new issue with uploading a value that contains a space.
For example:
sfdx force:data:record:update -u sfUserName -s SObjectName -i SObjectID -v "field__c=this contains a space"
is showing the error message:
Updating Record... Failed
ERROR running force:data:record:update: Malformed key=value pair for value: contains
The value that our use case requires is Won't fix, which besides containing an apostrophe contains a space.
I've included the output for sfdx version --verbose --json. Please let me know if any other information would be helpful at this time or steps needed on my part to move towards resolution.
Here is the sfdx version output for latest install
{
"cliVersion": "sfdx-cli/7.181.0",
"architecture": "win32-x64",
"nodeVersion": "node-v16.14.0",
"pluginVersions": [
"@oclif/plugin-autocomplete 1.3.6 (core)",
"@oclif/plugin-commands 2.2.1 (core)",
"@oclif/plugin-help 5.1.19 (core)",
"@oclif/plugin-not-found 2.3.9 (core)",
"@oclif/plugin-plugins 2.1.7 (core)",
"@oclif/plugin-search 0.0.4 (core)",
"@oclif/plugin-update 3.0.7 (core)",
"@oclif/plugin-version 1.1.3 (core)",
"@oclif/plugin-warn-if-update-available 2.0.14 (core)",
"@oclif/plugin-which 2.2.2 (core)",
"alias 2.1.11 (core)",
"apex 1.3.0 (core)",
"auth 2.3.1 (core)",
"community 2.0.18 (core)",
"config 1.4.22 (core)",
"custom-metadata 2.0.5 (core)",
"data 2.1.15 (core)",
"generator 2.0.12 (core)",
"info 2.2.11 (core)",
"limits 2.1.3 (core)",
"org 2.2.17 (core)",
"packaging 1.10.10 (core)",
"schema 2.1.18 (core)",
"signups 1.2.12 (core)",
"source 2.3.7 (core)",
"telemetry 2.0.5 (core)",
"templates 55.1.0 (core)",
"trust 2.2.1 (core)",
"user 2.1.22 (core)",
"@salesforce/sfdx-plugin-lwc-test 1.0.1 (core)",
"salesforce-alm 54.8.4 (core)"
],
"osVersion": "Windows_NT 10.0.19044",
"shell": "C:\Users\user.name\AppData\Local\Programs\Git\usr\bin\bash.exe",
"rootPath": "C:\Users\user.name\AppData\Roaming\npm\node_modules\sfdx-cli"
}
Hey @jamesedwardsvtgov, if you want to include values that contain a space you can surround them by single quotes, like so:
sfdx force:data:record:update -u sfUserName -s SObjectName -i SObjectID -v "field__c='this contains a space'"
You're right that there's still an issue with values that contain both a ' and a space though 🤔
We've been struggling to remedy that use case while maintaining backward compatibility with others, such as including Unicode characters.
I'll give this another try in the next few days. I've already re-opened our internal bug record.
Thank you I will look forward to the resolution of this issue to use the CLI.
I edited my previous comment and want to clarify that both:
sfdx force:data:record:update -u sfUserName -s SObjectName -i SObjectID -v "field__c=this contains a space"
and
sfdx force:data:record:update -u sfUserName -s SObjectName -i SObjectID -v "field__c='this contains a space'"
result in the same error which is:
Updating Record... Failed
ERROR running force:data:record:update: Malformed key=value pair for value: contains
Thanks again for your assistance with this, and I might suggest to include in the documentation that a value containing an apostrophe does not currently work on the stable branch.
Hey @jamesedwardsvtgov, that's very strange 🤔
The spaces work for us no problem.
This is the command running with the same version of the CLI as you
And the value pulled up in the developer console using a SOQL query
We will continue to look into this though.
I'm not sure about a workaround for now using the CLI but also looking into it.
For a workaround you could use the sfdx force:data:bulk:upsert command, it's definitely overkill for just updating one value but it could let you move forward for now.
Checkout sfdx force:data:bulk:upsert --help for more info but you'll want to create a CSV file that contains the field names and values you want to update for the record type. You can learn more about the format for that CSV file in our Bulk API 2.0 docs: Prepare CSV Files.
@RodEsp I am sorry yes that is working to save values with spaces!
You are correct it is the combination of apostrophe and space that is causing the issue. I see that you have included this info in 1837 and I will monitor that issue for updates.
Thank you also for the suggestion to use the sfdx force:data:bulk:upsert. We will try this approach.
Hi @jamesedwardsvtgov, I've been doing some testing and the fix implemented in https://github.com/salesforcecli/plugin-data/pull/427 does allow for quotes inside values with spaces but there's some weird interplay in how different shells parse strings and how the sfdx force:data:record:update|create commands parse strings that create some weird behavior.
I'm going to keep testing and see if we can at least update our docs and --help output to make that interplay easier to understand.
For now here's an example of how you can add your Won't Fix value using both Powershell and GitBash:
GitBash
Enclose the value of your key=value pair in " and use \ to escape them.
Powershell
Enclose the value of your key=value pair in " and use \` to escape them.
(I'm not entirely sure why \` is needed in that order but ` is the escape character for Powershell and I'm assuming \ does something in the command parsing logic to escape the `).
@RodEsp thank you for this update! Your suggested work around to use the bulk upsert command has worked great for our use case and we are able to proceed.
👋 This has been released in today's latest build 7.181.1
|
gharchive/issue
| 2022-11-22T18:05:23 |
2025-04-01T04:34:17.830289
|
{
"authors": [
"RodEsp",
"iowillhoit",
"jamesedwardsvtgov"
],
"repo": "forcedotcom/cli",
"url": "https://github.com/forcedotcom/cli/issues/1820",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
1937339091
|
@W-13893187 feat : added shipping entries in store setup.
What does this PR do?
Adds initialise shipping method to the setup script that populates the inital shipping entities for Native Shipping.
What issues does this PR fix or reference?
W-13893187
How to Test/Testing Effort
Create and setup the store using commerce:store:create
Check for values under developer console
Entities added :
ShippingConfigurationSet
ShippingRateArea
ShippingRateGroup
StandardShippingRate
@KalyanBoya @wei-liu-salesforce review please.
Thanks.
@tarcang @joeluong-sfcc please merge.
|
gharchive/pull-request
| 2023-10-11T09:48:04 |
2025-04-01T04:34:17.834109
|
{
"authors": [
"imAdityaSrivastav"
],
"repo": "forcedotcom/commerce-on-lightning",
"url": "https://github.com/forcedotcom/commerce-on-lightning/pull/269",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
168125794
|
iHaveAnExistingWithWhere now throws errors when no rows are affected.
Workaround is to wrap your feature context in a try/catch, however throwing an error when something is not affected seems a bit overzealous...?
Have an existing infers that one is looking for something that already exists, if it doesnt it throws an exception. This behavior has been like this from day 1.
What are you trying to achieve?
What you could do is catch the specific type of exception which is https://github.com/forceedge01/behat-sql-extension/blob/behat/2.5.x/src/Context/Exceptions/NoRowsAffectedException.php
I think this was fixed, I just hadn't done a pull. Hence closed.
|
gharchive/issue
| 2016-07-28T15:31:10 |
2025-04-01T04:34:17.847603
|
{
"authors": [
"forceedge01",
"jpswade"
],
"repo": "forceedge01/behat-sql-extension",
"url": "https://github.com/forceedge01/behat-sql-extension/issues/39",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
2010832758
|
🛑 UNAL Discord bot is down
In 5abd5b0, UNAL Discord bot (https://unal.forero.xyz) was down:
HTTP code: 502
Response time: 162 ms
Resolved: UNAL Discord bot is back up in f34f795 after 2 hours, 34 minutes.
|
gharchive/issue
| 2023-11-25T23:56:32 |
2025-04-01T04:34:17.870369
|
{
"authors": [
"forerosantiago"
],
"repo": "forerosantiago/upptime",
"url": "https://github.com/forerosantiago/upptime/issues/154",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1570738524
|
Only run unit tests for code coverage
Integration tests are disabled, because they rely on Rust toolchains which do not support the -C instrument-coverage, needed by llvm-cov. E.g. in some integration tests we use Rust 1.38, which does not support this flag yet.
bors r+
|
gharchive/pull-request
| 2023-02-04T03:41:27 |
2025-04-01T04:34:17.871391
|
{
"authors": [
"foresterre"
],
"repo": "foresterre/cargo-msrv",
"url": "https://github.com/foresterre/cargo-msrv/pull/606",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
45688210
|
idea: remove yAxis.nicing ( ? )
solves #183 and #184, plus it's not really needed since axes are "nicer" by default than they used to be.
Fixed by 00e7b23665f38122f66de77f0c87ac2f33f631a1
verified in 0.9.108
|
gharchive/issue
| 2014-10-13T21:31:04 |
2025-04-01T04:34:17.879502
|
{
"authors": [
"jaimedp",
"mmrj"
],
"repo": "forio/contour",
"url": "https://github.com/forio/contour/issues/185",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
793584785
|
handleChange type doesn't work
Bug report
Current Behavior
no type error with
onChange(v: number)
Expected behavior
with this commented
we finally get type error
Reproducible example
Suggested solution(s)
https://github.com/formium/formik/blob/80f9a831797429ae3c4457a47b6d8391e9d8bd2c/packages/formik/src/types.tsx#L140-L145
modify preact-like typing
Additional context
Your environment
Software
Version(s)
Formik
2.2.6
React
17.0.1
TypeScript
4.0.5
Browser
Any
npm/Yarn
1.22.4
Operating System
Big Sur
You would have to pass onChange={handleChange("lengthMeterTo")} so it would automatically pass your value back to the field itself.
If that callback is typed with a string, that would be an issue. It should be any. You can accomplish this right now with
const [{ onChange }] = useField<number>("lengthMeterTo");
// this onChange knows it will be a number.
<YourInput onChange={onChange} />
What you're requesting for handleChange is actually impossible to completely type. Even though you suggest "kind of" typing it, it doesn't type it based off of Values and name, so it is an incomplete type. We're trying to figure out how to give full typing to values and all related callbacks based on name, and have had some success with #1334 #2655 but nothing to merge just yet. Our successful tries require bleeding edge TypeScript, which we're not going to depend on just yet. Probably targeted for v3.
You would have to pass onChange={handleChange("lengthMeterTo")} so it would automatically pass your value back to the field itself.
If that callback is typed with a string, that would be an issue. It should be any. You can accomplish this right now with
const [{ onChange }] = useField<number>("lengthMeterTo");
// this onChange knows it will be a number.
<YourInput onChange={onChange} />
What you're requesting for handleChange is actually impossible to completely type. Even though you suggest "kind of" typing it, it doesn't type it based off of Values and name, so it is an incomplete type. We're trying to figure out how to give full typing to values and all related callbacks based on name, and have had some success with #1334 #2655 but nothing to merge just yet. Our successful tries require bleeding edge TypeScript, which we're not going to depend on just yet. Probably targeted for v3.
Duplicate of #2084 at al
Duplicate of #2084 at al
Thanks for getting back to me, that solution work for me!
Thanks for getting back to me, that solution work for me!
|
gharchive/issue
| 2021-01-25T17:38:02 |
2025-04-01T04:34:17.949339
|
{
"authors": [
"johnrom",
"olso"
],
"repo": "formium/formik",
"url": "https://github.com/formium/formik/issues/3013",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1250375661
|
When will there be a stable version of this package?
Hi! So far from what I have seen, this project is insanely good, but still in beta. Any idea when we will have a stable version of it so we can safely use it in a production environment? Thank you.
Likely in the 1-2 month time range for the first RC version. However, its pretty stable today and we publish breaking changes on every release so quite a few users are already using it in production. Feel free to join us on discord to ask about any specifics too: https://discord.gg/bF7JQKrp3X
|
gharchive/issue
| 2022-05-27T06:00:46 |
2025-04-01T04:34:17.955693
|
{
"authors": [
"StefanGhiban",
"justin-schroeder"
],
"repo": "formkit/formkit",
"url": "https://github.com/formkit/formkit/issues/257",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1682618987
|
🛑 K-samsök (Riksantikvarieämbetet) is down
In cfd436b, K-samsök (Riksantikvarieämbetet) (http://www.kulturarvsdata.se/ksamsok/api?method=search&query=thumbnailExists=j&x-api=test&hitsPerPage=500&recordSchema=xml&fields=itemId,thumbnail&startRecord=1) was down:
HTTP code: 404
Response time: 1481 ms
Resolved: K-samsök (Riksantikvarieämbetet) is back up in 0511a69.
|
gharchive/issue
| 2023-04-25T07:45:03 |
2025-04-01T04:34:17.974638
|
{
"authors": [
"Abbe98"
],
"repo": "fornpunkt/dependency-monitor",
"url": "https://github.com/fornpunkt/dependency-monitor/issues/73",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
478167180
|
Merge v2.19.0 into dev
Merge Forseti v2.19.0 into dev.
This is the cleanest change from a release to dev!
|
gharchive/pull-request
| 2019-08-07T22:29:12 |
2025-04-01T04:34:17.975630
|
{
"authors": [
"blueandgold",
"hshin-g"
],
"repo": "forseti-security/forseti-security",
"url": "https://github.com/forseti-security/forseti-security/pull/3047",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
}
|
620458655
|
Move the Discourse link at the top
Currently one must scroll down to find the Discourse link. Let's put it at the top horizontal menu? I think we want this as the primary discussion forum, so that would be a great place for it.
I agree it should be easier to find. I'm not crazy about the Discourse badge being in the navbar, design-wise. But maybe it could work, all the way to the right of "News". The problem here is that on mobile, Discourse link would be hidden until the user opens the sandwich bar. A workaround for this would be to keep the Discourse link both where it is now, and to add it to the navbar.
An alternative would be to move the whole "Join us" section up, and bring the "News" section down. I think this would be my favorite solution.
Yeah I agree, just move the section up. It definitely shouldn't be in the navbar.
I was thinking putting either "Forum" or "Discourse" into the navigation bar at the top, not the logo. Is there a problem design-wise with that?
We could do something like this where we group our external links (discourse, twitter, github) as mini icons in the navbar far right, separate from internal nav links?
@LKedward this looks even better! I just want to go to fortran-lang.org and then get to Discourse from there. I just don't remember the address and ultimately we want more people to do what I do --- to go through the main webpage. So that as we add more things, or announcements, they can see them.
I just want to go to fortran-lang.org and then get to Discourse from there. I just don't remember the address ..
I've been doing the exact same thing! Scrolling down each time.
and ultimately we want more people to do what I do --- to go through the main webpage. So that as we add more things, or announcements, they can see them.
Absolutely I agree, we want this to be more accessible and visible.
I can have a go at putting this together this week 👍
|
gharchive/issue
| 2020-05-18T19:40:56 |
2025-04-01T04:34:18.011161
|
{
"authors": [
"LKedward",
"certik",
"milancurcic"
],
"repo": "fortran-lang/fortran-lang.org",
"url": "https://github.com/fortran-lang/fortran-lang.org/issues/85",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
459992186
|
feat: Ask for login/sign up at start
Fixes #2001
build fails
successful
|
gharchive/pull-request
| 2019-06-24T16:44:48 |
2025-04-01T04:34:18.047759
|
{
"authors": [
"liveHarshit"
],
"repo": "fossasia/open-event-android",
"url": "https://github.com/fossasia/open-event-android/pull/2004",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
}
|
89259049
|
Database test
@creativepsyco Please check
The names of the test function are not according to Java style. Also the spaces, parenthesis etc are not formatted properly. Please fix then we merge.
@creativepsyco Fixed.
|
gharchive/pull-request
| 2015-06-18T10:47:11 |
2025-04-01T04:34:18.048785
|
{
"authors": [
"creativepsyco",
"mananwason"
],
"repo": "fossasia/open-event-android",
"url": "https://github.com/fossasia/open-event-android/pull/41",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
}
|
172480908
|
Rooms page errors of time and rooms
Please move times back to left side of the table and ensure room only shows up once.
@aayusharora will you take a look at this ? your earlier PR moved the times into the boxes.
@championswimmer Working for this
thanks, done via https://github.com/fossasia/open-event-webapp/pull/685
Rooms still repeating
@championswimmer Figured that out Please check the spaces in front off Dalton hall in data https://github.com/fossasia/open-event/blob/master/sample/FOSSASIA16/sessions#L48 This is the reason for creating two objects. Can you remove this?
done https://github.com/fossasia/open-event/pull/92
|
gharchive/issue
| 2016-08-22T15:22:49 |
2025-04-01T04:34:18.082966
|
{
"authors": [
"aayusharora",
"championswimmer",
"mariobehling"
],
"repo": "fossasia/open-event-webapp",
"url": "https://github.com/fossasia/open-event-webapp/issues/677",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
269425472
|
Added Parsijoo support
Fixes #293
Checklist
[x] I have read the Contribution & Best practices Guide and my PR follows them.
[x] My branch is up-to-date with the Upstream master branch.
[x] I have added necessary documentation (if appropriate)
Changes proposed in this pull request:
Added Parsijoo support
@gabru-md @vaibhavsingh97 Please review. Providing the heroku deployment at https://shielded-castle-17515.herokuapp.com/
Thanks !!
@mariobehling @niranjan94 please review !!
|
gharchive/pull-request
| 2017-10-29T19:06:59 |
2025-04-01T04:34:18.104124
|
{
"authors": [
"bhaveshAn"
],
"repo": "fossasia/query-server",
"url": "https://github.com/fossasia/query-server/pull/294",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
343239343
|
Adding support for audio_play action
Fixes #383
Changes: Play video from youtube for audio_play action, same as the SUSI Android and Web client.
Screenshots for the change:
@batbrain7 I implemented the same way as SUSI Android. Please review
|
gharchive/pull-request
| 2018-07-20T20:34:30 |
2025-04-01T04:34:18.107094
|
{
"authors": [
"imjog"
],
"repo": "fossasia/susi_iOS",
"url": "https://github.com/fossasia/susi_iOS/pull/384",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
293489355
|
Components reflow and lifecycle
It seems that for a lot of Foundation components, reflow and reInit are not properly supported. I'm making here a list of the issues related to this problem.
https://github.com/zurb/foundation-sites/issues/8016 [Magellan] active class not being applied when content is loaded dynamically (@npapazian)
https://github.com/zurb/foundation-sites/issues/8333 Orbit not reinitializing (@olefredrik)
https://github.com/zurb/foundation-sites/issues/8395 Abide reflow in F6 not working? (@Boduje)
https://github.com/zurb/foundation-sites/issues/8684 [Equalizer] wrong height (@pavelblazek)
https://github.com/zurb/foundation-sites/issues/9193 Abide form in a Reveal modal isn't initialised when added after page load (@u35tniyh)
https://github.com/zurb/foundation-sites/issues/9829 Reinit magellan plugin after DOM update (@fchengpc)
https://github.com/zurb/foundation-sites/issues/9858 How to reset Magellan barOffset after initialization? (@klihelp)
https://github.com/zurb/foundation-sites/issues/10340 Resize events for dynamically added elements using data-interchange not working (@JarvisH)
https://github.com/zurb/foundation-sites/issues/10501 Equalizer reInit not reliably working w/ data-equalize-on option (@zitrusblau)
https://github.com/zurb/foundation-sites/issues/10768 Range slider-fill doesn't update correctly for sliders with two handles (@pulekies)
https://github.com/zurb/foundation-sites/issues/10898 Changing the 'title' property of a tooltip element does not change the tooltip (@tedivm)
https://github.com/zurb/foundation-sites/issues/10923 [Sticky] Cannot change data option after init (@fleps)
I identified some commons problems in these issues:
_reflow is not implemented in all components
_init and _reflow does not update the options list
reInit/reflow are not well documented
What do you think ? @colin-marshall @brettsmason @IamManchanda @JeremyEnglert @Owlbertz
I think you can add #10898 to that list. Probably something we should make a goal for 6.5?
Can we solve most of the easily?
I think there's nothing difficult here, but it will take a long time to resolve. We need to go over all components, re-enable a full "reflow" support for all options and everything relying on them. This include templates, events...
Is there an update on this or a workaround until it's fixed?
Is there an update on this or a workaround until it's fixed?
So far no updates and I'm not aware of better workarounds then reinitializing, destroying and refreshing Foundation components.
So far no updates and I'm not aware of better workarounds then reinitializing, destroying and refreshing Foundation components.
|
gharchive/issue
| 2018-02-01T11:06:51 |
2025-04-01T04:34:18.128881
|
{
"authors": [
"DanielRuf",
"colin-marshall",
"kjgenevieve",
"ncoden"
],
"repo": "foundation/foundation-sites",
"url": "https://github.com/foundation/foundation-sites/issues/10900",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
369952869
|
names
event: request_process -> request_received
https://www.drupal.org/project/drupal/issues/1677052#comment-6679754
this is pertinent to lighttouch, and the event is already named incoming_request_received
|
gharchive/issue
| 2018-10-14T22:52:27 |
2025-04-01T04:34:18.134993
|
{
"authors": [
"Arnaz87",
"mitchtbaum"
],
"repo": "foundpatterns/torchbear",
"url": "https://github.com/foundpatterns/torchbear/issues/34",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1227310038
|
cast sig does not behave as expected on some inputs
Component
Cast
Have you ensured that all of these are up to date?
[X] Foundry
[X] Foundryup
What version of Foundry are you on?
nightly-8478c0841b00789c735df68ad111105fa9204f55
What command(s) is the bug in?
cast sig
Operating System
No response
Describe the bug
This should fail but does not
cast sig "foo(uint999)"
0x54511ad7
This should succeed
cast sig "foo(function() external)"
# panic with 'Illegal abi' message
The root of the problem is really over in ethers-rs. The parser does not handle function types in human readable ABI and does not make sure the bytes/int/uint sizes are correct, among other things. ref https://github.com/gakonst/ethers-rs/issues/474
Some more examples
Arrays with unit sizes are techincally valid solidity
In solidity this expands out to uint[60].
foo(uint[1 minutes] memory)
Arrays have a maximum size in solidity
This gets parsed as correct but is not.
cast sig "foo(uint[99999999999999999])"
0xfece5cb9
Should I have opened this issue in https://github.com/gakonst/ethers-rs/ ? It's really more of a problem there than it is a foundry bug.
cast sig "foo(function() external)"
I don't think it should? You cannot make these functions external, so they will never have a 4byte signature.
The others make sense to me.
There is another issue: Some Cast commands (cast call for example), we cannot use structs. AbiParser supports it, but it really just expands them into tuples. We should probably allow people to pass tuples (even though it is technically invalid) to support people calling functions with structs (and functions that return structs)
@mattsse Assigning you to this since it's the same underlying issue as #2025 and you assigned yourself to that one
function types are currently not supported by ethabi, there's simply not a type variant for them
tracked here https://github.com/rust-ethereum/ethabi/issues/273
If ethabi doesn't add function types then you could just treat them as bytes24 https://docs.soliditylang.org/en/latest/abi-spec.html#types
there are essentially two issues:
encoding/decoding
signature
which is handled here
https://github.com/rust-ethereum/ethabi/blob/451d029c69a1fce7c4d57cc117e985a31dc53627/ethabi/src/param_type/writer.rs#L25-L52
and would require another variant
Should be fixed in #2151, please let me know if it's not!
|
gharchive/issue
| 2022-05-06T00:51:40 |
2025-04-01T04:34:18.148245
|
{
"authors": [
"mattsse",
"onbjerg",
"zk-tarts"
],
"repo": "foundry-rs/foundry",
"url": "https://github.com/foundry-rs/foundry/issues/1521",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1794523618
|
Bracketed "diceNumber" resolving problem.
Last update it was working just fine but a rule element like this no longer works on the current update (5.1.1)
"brackets": [
{
"start": 11,
"value": {
"diceNumber": "@item.badge.value * 2"
"dieSize": "d8"
},
"end": 16
}
Is this found on a compendium item?
|
gharchive/issue
| 2023-07-07T23:15:46 |
2025-04-01T04:34:18.165039
|
{
"authors": [
"HibaniPaws",
"stwlam"
],
"repo": "foundryvtt/pf2e",
"url": "https://github.com/foundryvtt/pf2e/issues/8597",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1691692665
|
🛑 Wishing Out Loud is down
In d03a176, Wishing Out Loud (https://www.wishingoutloud.com) was down:
HTTP code: 500
Response time: 521 ms
Resolved: Wishing Out Loud is back up in 8adbc10.
|
gharchive/issue
| 2023-05-02T02:46:30 |
2025-04-01T04:34:18.169263
|
{
"authors": [
"fourthfloor"
],
"repo": "fourthfloor/uptime",
"url": "https://github.com/fourthfloor/uptime/issues/686",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1979209600
|
🛑 Gahanna Area Chamber is down
In 815ec25, Gahanna Area Chamber (https://www.gahannaareachamber.com) was down:
HTTP code: 0
Response time: 0 ms
Resolved: Gahanna Area Chamber is back up in 304cfae after 16 minutes.
|
gharchive/issue
| 2023-11-06T13:50:51 |
2025-04-01T04:34:18.171786
|
{
"authors": [
"fourthfloor"
],
"repo": "fourthfloor/uptime",
"url": "https://github.com/fourthfloor/uptime/issues/826",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
566749839
|
Add dockerfile, update README.md
Install impacket from github and bloodhound via setup.py.
thanks, merged!
|
gharchive/pull-request
| 2020-02-18T09:14:37 |
2025-04-01T04:34:18.173087
|
{
"authors": [
"dirkjanm",
"h4rm0ny"
],
"repo": "fox-it/BloodHound.py",
"url": "https://github.com/fox-it/BloodHound.py/pull/38",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
387683874
|
Feature Request: Improve Dijkstra performance
Hi @dirkjanm,
The current implementation of the Dijkstra algorithm is not optimal, which is noticeable when dealing with larger graphs. As you mentioned in the wiki, the ShortestPath algorithm is faster than Dijkstra but the performance differences can be greatly reduced with few optimizations.
Neo4j stores relationship's properties values on disk which mean a lot of unnecessary IO overhead which dramatically slowing the process of graph traversal. Because the weight is constant for each ACL, it's better to calculate the cost based on the relationship type (name) which is in-memory (assuming the entire graph can be loaded to RAM and cache is warmed up). You can achieve this by tweaking the neo4j-graph-algorithms plugin to use constant weight values for each ACL instead of looking at the relationship's property. This will also spare the creation of additional properties.
Thanks for thinking along with this :) Do you have an example of how and where this can be configured? Note that the weight is not constant for each ACL, it depends on the start and end node as well, see the code here: https://github.com/fox-it/aclpwn.py/blob/master/aclpwn/database.py#L78
I haven't come along something like this in the exposed cypher procedures. Also the default uses the REST API Dijkstra algorithm, which doesn't use the neo4j-graph-algorithms plugin.
Because Neo4j builtin Dijsktra capabilities are disappointing, you would probably have to write a user procedure that implements Dijkstra with relationship name as cost. This issue made others create custom plugins who modified the implementation to their liking.
This link is a good place to start: https://grokbase.com/t/gg/neo4j/156knxv03a/performance-difference-between-dijkstra-and-allshortestpath
With user procedures, you could also evaluate the weight based on the start/end node and make it REST compatible.
|
gharchive/issue
| 2018-12-05T10:13:20 |
2025-04-01T04:34:18.176964
|
{
"authors": [
"dirkjanm",
"machosec"
],
"repo": "fox-it/aclpwn.py",
"url": "https://github.com/fox-it/aclpwn.py/issues/1",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1661201654
|
Make handler functions return status value
Public-Facing Changes
None
Description
Refactors the way handler functions are run in a separate thread. It's better to do that in a unified way in the server rather than doing that for ROS 1 & 2 differently as it was implemented in #165
Change handler function signature to return a success status and an additional error message which will be sent to the client if the handler did not succeed.
Fixes #148
This seems like a good change overall. I have seen C++ codebases benefit greatly from a Status type, e.g. https://abseil.io/docs/cpp/guides/status, so that would be a nice improvement/cleanup to consider. I'm not sure if there is one already in the ROS package ecosystem?
I wonder if we should not simply throw exceptions if something went wrong. We already use exceptions in other places, so there is no good reason to not use them. This seems to be also what the C++ core guidelines recommend: https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#e25-if-you-cant-throw-exceptions-simulate-raii-for-resource-management
|
gharchive/pull-request
| 2023-04-10T18:57:48 |
2025-04-01T04:34:18.181337
|
{
"authors": [
"achim-k"
],
"repo": "foxglove/ros-foxglove-bridge",
"url": "https://github.com/foxglove/ros-foxglove-bridge/pull/210",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1789108303
|
Feat: add esm module export
Public-Facing Changes
None
Description
Add support for ESM generated library, so some esm friendly build tools such as Vite can benefit from it since browser also use this library.
Although, vite can use pre-optimize, commonjs plugin, but provide esm module also provide treeshaking when esm import this library.
For some of our other packages we produce both dist/cjs/... and dist/esm/..., we could do that here too. Is the world ready for us to publish ESM only packages? Somehow I doubt it?
@aresyy Does @jtbandes comment make sense to you on the changes we'd like to see in this PR? We'd like to keep using the .js extension and put the esm output into an esm folder (and move the cjs output into a cjs folder).
@jtbandes did I get that right?
I guess I didn't realize that this library is manually constructing the output scripts rather than producing them via tsc like our other packages do. Then I guess I don't have a strong opinion and .mjs seems alright – should we rename index.js to index.cjs as well?
should we rename index.js to index.cjs as well?
I would not - I'd probably use the separate folders approach and stick with .js syntax. mjs is some nodejs-ism from what I can tell.
.mjs is nodejs-ism for me as well.
If this package is not used by any nodejs platform upstream project, I think we can name this index.esm.js which webpack community prefers :smile:
since it only generates one file, my personal opinion is not create esm, cjs folder until it generates multiple outputs.
@aresyy sounds good to me - if you want to make those updates we can re-review.
force pushed to keep commit history clean
|
gharchive/pull-request
| 2023-07-05T09:02:50 |
2025-04-01T04:34:18.186769
|
{
"authors": [
"aresyy",
"defunctzombie",
"jtbandes"
],
"repo": "foxglove/rosmsg-msgs-common",
"url": "https://github.com/foxglove/rosmsg-msgs-common/pull/13",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
75567619
|
wai-app-static 3.1.0
wai-app-static-3.1.0 depended on by:
keter-1.3.10.1 (==3.0.*). Michael Snoyman michael@snoyman.com @snoyberg. @snoyberg
servant-server-0.4.0 (==3.0.*). Haskell Servant jkarni@gmail.com @jkarni. @haskell-servant
servant-server fixed in 0.4.1
|
gharchive/issue
| 2015-05-12T11:22:12 |
2025-04-01T04:34:18.222489
|
{
"authors": [
"jkarni",
"snoyberg"
],
"repo": "fpco/stackage",
"url": "https://github.com/fpco/stackage/issues/579",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
452611049
|
renamed xboxapp xkm not detecting
hey got a problem since couple of days when microsoft decided to uppgrade the xboxapps name, now it dosnt know it is running. and just stays blue. ive looked abit on my own but i cannot find where to change or so please fix this if u can please
yeah, this new xbox app update, the mouse and keyboard app doesnt lock the mouse into the app, need fix asap
It is really easy to fix on our end until someone from the projects fixes it. Just go in the XboxStream class and change line 32 for the right name. I did it last night and it works.
Wish i knew how to do that
Could you give a quick tour on how to do that, you change on github? or on the computer itself?
You cannot do it on github unless you are a contributor. Do it locally on your computer. Git clone the project (or download the zip) on your computer, open the code (you will need to download Microsoft Visual Studio 2019 if you don't have it). Change the code and run it from Visual Studio.
hmm nice, thanks a lot man will do
But what sucks now is the name of the app is not longer language neutral. The name before was "Xbox" which is the same in all the languages. Now, for me in French I had to write "Compagnon de la console Xbox". So now the project will only work with English computers, unless the project contributors can find something to handle it.
Thats bad, the guys will figure it out im sure, and i managed to get it working, thanks for the help
@secretspy911 how should it say im in a english version it says Xbox Console Companion but it still wont trigger :( should spaces in the name be just spaces or no spaces or ? love if u sent me the bit of text edited here in commment that i need to change
Whatever the language, the text in the code must be the exact same the the text you see at the top of the xbox app when it's open.
nvm Just got it to work i hope xD mouse locked in window app turned green XD thanks alot
solved issue and i got a build that works if ur OS is english and can mabey? be sent? dunt know-.- thankks @secretspy911 (had solved the issue long ago haha but missspelled the name :D thanks for correcting me) ^^
Yeah we should get some code in that detects the app better. Its the same exact string match that blocked an Xbox app beta version user a while ago. Then we can push a new click-once update to auto deploy the fix to everyone.
Im pretty busy but will try to squeeze out some time to start looking into this late tonight.
reopening until we deploy a fix to everyone
I can could send u the change I made for English OS if you want I have it in a .rar .zip file just don't know alot of how GitHub, works just started trying to "code" and yea
Den 6 juni 2019 19:37 skrev David Rieman notifications@github.com:
reopening until we deploy a fix to everyone
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/fqlx/XboxKeyboardMouse/issues/158?email_source=notifications&email_token=AMIBX3VFLZNO55F7UVF74JLPZFDOBA5CNFSM4HT7MEO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXDTLQY#issuecomment-499594691, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMIBX3VQQWGY4M7WEJCJDYLPZFDOBANCNFSM4HT7MEOQ.
@shrek88 don't worry, we got this.
seems like title already there, but it still does not trigger mouse =((
@kostkol87 you can try opening the .sln file in Visual Studio and building it that way. (setdd isn't recognized on my Win10 machine either, and there are other oddities in build.bat like the configuration being out of date. I know I haven't ever touched that build.bat and we should probably delete it or fix it.)
Or wait for the fixed binaries, which I'm working on soon.
Great news: I've deployed the new version. If you've used the installation instructions to install with that click-once installer, then the next launch should auto-update to the fixed version. Please try it out and report back here so we can confirm and close the issue.
Great news: I've deployed the new version. If you've used the installation instructions to install with that click-once installer, then the next launch should auto-update to the fixed version. Please try it out and report back here so we can confirm and close the issue.
Still not working, how can I resolve?
|
gharchive/issue
| 2019-06-05T16:54:51 |
2025-04-01T04:34:18.236149
|
{
"authors": [
"CrsDany",
"DavidRieman",
"RenanBan",
"kostkol87",
"secretspy911",
"shrek88"
],
"repo": "fqlx/XboxKeyboardMouse",
"url": "https://github.com/fqlx/XboxKeyboardMouse/issues/158",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
}
|
2122017980
|
Can't install locally
OS: Macos Sonoma 14.2.1
Node: 18.17.0
When I clone the repo, main branch and run yarn install I'm getting this error
[1/5] 🔍 Validating package.json...
[2/5] 🔍 Resolving packages...
error An unexpected error occurred: "Invalid URL".
info If you think this is a bug, please open a bug report with the information provided in "/Users/user/projects/frames.js/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
If I upgrade to yarn >2.x the install works but I get a bunch of other building errors. Do I need a specific node 18.x version? yarn automatically gets set to 1.22.19 which is declared in the package.json.
Update: I just had to update to the latest 18.19.0 we should probably update the version requirement to match.
|
gharchive/issue
| 2024-02-07T02:08:47 |
2025-04-01T04:34:18.266961
|
{
"authors": [
"madroneropaulo"
],
"repo": "framesjs/frames.js",
"url": "https://github.com/framesjs/frames.js/issues/34",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1421377956
|
Prior is specific to astrophysics
this can easily be fixed :)
that -0.478 is much to close to -1/2.
I was looking into this stuff from a theoretical standpoint, infact given a Poisson distribution with mean "N" the Jeffreys prior for such distribution is N^{-1/2}.
Maybe very unsurprisingly their MC study has empirically found that the best prior is a non-informative one.
|
gharchive/issue
| 2022-10-24T20:12:07 |
2025-04-01T04:34:18.270373
|
{
"authors": [
"Moelf",
"francescoalemanno"
],
"repo": "francescoalemanno/BayesHistogram.jl",
"url": "https://github.com/francescoalemanno/BayesHistogram.jl/issues/7",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
276223397
|
we can not add an event directly to the calendar from days
morning
I am wilfried kouadio student at the institute Atlantic telecom of brest and this project attracted me to the proposal of a rather interesting idea. Indeed after analysis of this agenda I noticed that it was impossible to add events directly from the days.
So it would be interesting to do it by clicking on the desired day which opens a window pop-up giving the possibility to the user to add directly his event through a text area taking obviously of course the fact that we can not add d event on the days preceding the current day.
I propose to achieve this task.
cordially.
Hi berba1995!
Thank you for paying attention to my project. I agree with you on this point. But I do not have time yet to do this feature.
key i noticed that you have merged my recently pull request about this.
thank you for accepting my contribution.
you are welcome! there are still many features that remain
|
gharchive/issue
| 2017-11-22T22:39:05 |
2025-04-01T04:34:18.274821
|
{
"authors": [
"berba1995",
"franck123"
],
"repo": "franck123/ui-agenda",
"url": "https://github.com/franck123/ui-agenda/issues/2",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1552038873
|
🛑 PEDCO is down
In 50b9394, PEDCO (https://pedco.uncoma.edu.ar/) was down:
HTTP code: 0
Response time: 0 ms
Resolved: PEDCO is back up in 95f3436.
|
gharchive/issue
| 2023-01-22T08:12:46 |
2025-04-01T04:34:18.277305
|
{
"authors": [
"francoZuniga32"
],
"repo": "francoZuniga32/pedco-status",
"url": "https://github.com/francoZuniga32/pedco-status/issues/523",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
675132925
|
Compile without debug options
Compiling without debug flags by default might be a good idea :)
Closing #6 because that changed a lot of things. This should be good for you.
It might be interesting to check if O3 actually makes sense here. I've seen enough software break with it to be very weary of using it.
O2 is safer and sometimes even faster.
I took this from the master branch, which is why it uses O3
|
gharchive/pull-request
| 2020-08-07T16:29:59 |
2025-04-01T04:34:18.301452
|
{
"authors": [
"andrebrait"
],
"repo": "frangarcj/vita2dlib",
"url": "https://github.com/frangarcj/vita2dlib/pull/7",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
1069282465
|
Test fetch GitHub id for issue body
I want add some repos and orgs into the project.
Label: Alibaba
Repos:
apache/dubbo
apache/rocketmq
Orgs/Users:
alibaba
aliyun
invalid-org
frank-zsy
/parse-github-id
Test
Test
Test
Test
Test
|
gharchive/issue
| 2021-12-02T08:48:28 |
2025-04-01T04:34:18.306073
|
{
"authors": [
"frank-zsy"
],
"repo": "frank-zsy/open-digger",
"url": "https://github.com/frank-zsy/open-digger/issues/4",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
2112052402
|
Ghost in the lights
I have 16 WiZ bulbs set up in one lightener device. All of which have 4 mapping lines, allowing me to gradually turn them on one by one, and then gradually increase brightness slowly.
When it works it's great, but after setting this up, the lights change brightness on their own every few minutes, always down, until they eventually turn off. The mapping config also slowly drifts "off", so that 100% on the lightener device seems to only go to about 30% on the config.
The automation that connects the wireless rotary dimmer to the light is not being triggered when the dimming happens, and there is nothing in the logs. I've turned on debug logging for the integration, but nothing their either.
Any ideas?
User reports same issue in a reddit thread, so probably not particular to my setup.
I think I have faced something similar myself. It was tricky to debug the problem though and I figured a workaround that worked for me.
In my case, it felt like the Lightner configuration got messed up during HA (re)load. The following automation stabilized everything:
alias: Reload Lightener configurations on Home Assistant start
description: ""
trigger:
- platform: homeassistant
event: start
condition: []
action:
- service: homeassistant.reload_config_entry
data: {}
target:
entity_id:
- light.living_room
- light.dining_room
- light.kitchen
- light.club
- light.hall
- light.stairs
- light.office
- light.eduardo
- light.ewa
- light.riki
- light.kids_bathroom
- light.master_bedroom
- light.master_bathroom
- light.closet
- light.cinema
mode: single
If I remember well, I believe I was seeing this problem in rooms with many lights. Maybe you're seeing the same with your 16 bulbs.
I hope someone else can confirm tha this automation helps. It could give hints on what's the cause of this issue bucause, in any case, we need a reliable way to reproduce the problem before we even try to fix it.
Thanks, I'll see if this makes a difference in my case.
No change with the proposed workaround, here is my 16 bulb config in case it helps...
{ "entry_id": "7579a8ab4410a2532461a2cd5ad2a1fb", "version": 2, "minor_version": 1, "domain": "lightener", "title": "Svefnherbergi_Loftljós", "data": { "friendly_name": "Svefnherbergi_Loftljós", "entities": { "light.wiz_dandelion_1": { "brightness": { "1": "1", "60": "1", "100": "50" } }, "light.wiz_dandelion_2": { "brightness": { "1": "0", "5": "0", "60": "1", "100": "50" } }, "light.wiz_dandelion_3": { "brightness": { "1": "0", "10": "0", "60": "1", "100": "50" } }, "light.wiz_dandelion_4": { "brightness": { "1": "0", "15": "0", "65": "1", "100": "50" } }, "light.wiz_dandelion_5": { "brightness": { "1": "0", "20": "0", "65": "1", "100": "50" } }, "light.wiz_dandelion_6": { "brightness": { "1": "0", "22": "0", "65": "1", "100": "50" } }, "light.wiz_dandelion_7": { "brightness": { "1": "0", "25": "0", "70": "1", "100": "50" } }, "light.wiz_dandelion_8": { "brightness": { "1": "0", "28": "0", "70": "1", "100": "50" } }, "light.wiz_dandelion_9": { "brightness": { "1": "0", "30": "0", "70": "1", "100": "50" } }, "light.wiz_dandelion_10": { "brightness": { "1": "0", "35": "0", "70": "1", "100": "50" } }, "light.wiz_dandelion_11": { "brightness": { "1": "0", "40": "0", "70": "1", "100": "50" } }, "light.wiz_dandelion_12": { "brightness": { "1": "0", "42": "0", "70": "1", "100": "50" } }, "light.wiz_dandelion_13": { "brightness": { "1": "0", "45": "0", "75": "1", "100": "50" } }, "light.wiz_dandelion_14": { "brightness": { "1": "0", "50": "0", "75": "1", "100": "50" } }, "light.wiz_dandelion_15": { "brightness": { "1": "0", "52": "0", "75": "1", "100": "50" } }, "light.wiz_dandelion_16": { "brightness": { "1": "0", "55": "0", "75": "1", "100": "50" } } } },
Having given it some time, I believe the automation workaround is making it somewhat more stable. It is definitely usable now with the occasional quirk. Thank you @fredck
If that's the case, you may try using the "Reload" option of the specific Lightener configuration in your system at https://my.home-assistant.io/redirect/integration/?domain=lightener when this situation happens.
If this really helps, it can give us some hints that could help figure this thing out. Thanks!
@fcassata Are you able to give a try to Lightener v2.3.0-beta.3 and see if there is any improvement. This is a pre-release so HACS doesn't install it by default but it gives you the option to install it ("redownload").
This release has lots of small improvements and I have hope that they may help. Also, it comes now with a lot of debug logging. If your problem persists, please enable debug logging in your ha configuration:
logger:
default: info
logs:
custom_components.lightener: debug
Then, play with the lights and see what your logs says (check the log file directly, not the log page). You may find something helpful there. You can even attach some logs here.
As you can imagine it is very difficult to reproduce your specific use case. It may be related to the lights themselves. I really hope this release can help us figuring this out.
Thanks!
Thanks @fredck, installed and will monitor. Will also disable the workaround-automation that was proposed earlier so it's not getting in the way while I test this release out.
Thanks @fredck, will update. Btw, seeing the same issue as before with Beta 3 that I'm currently on. Lights dimming on their own, and in rare cases it seems the brightness is reported back incorrectly since the lovelace slider creeps upward on its own without a brightness change.
@fcassata, just to clarify, I didn't make any fixes specific to your use case. What we have in the betas are overall improvements in the internals of Lightener, with the hope that they may have a positive impact on your use case.
Also, there is a good chance that the issue has little to do with Lightener. What it does is, in theory, very simple: it sends individual calls to the "turn_on" service for each of the controlled lights, with the calculated brightness level configured for each of them, and that's it. Then it's the job of HA, the WiZ integration, and the bulbs themselves to do what they have to do.
You're talking about 16 wireless bulbs being controlled at once. By nature, all this happens in an asynchronous way where some bulbs may respond earlier than others. All those actions also enter a queue which, depending on the delay of the bulbs in answering, could cause the ghost behavior.
To that, add a rotary dimmer, which may be sending many changes to the brightness level in a very short amount of time. This means you multiply 16 "turn_on" calls for each change received, which may be piling up and overloading the system.
In a few words, it may be that your setup and your goals are too much for Lightener, the WiZ Integration, Home Assistant, and the WiZ bulbs to handle, and you'll have to settle with what is possible.
But that's not a definitive answer, for sure. We can only accept that after further investigation. That's the reason the betas included extensive debug logging. So, please enable the debug logging for the integration as I described before, and let's see if the logs can tell us anything that could help us form a final opinion on this matter.
I really hope we'll find that there is an issue with Lightener, so we'll be able to get it fixed. But I've started to doubt it has anything to do with that. Please prove me wrong.
Thanks!
Haha I'll try proving you wrong @fredck. I do appreciate your time on this hard to reproduce vaguely described issue though!
The gradual dimming I've described happens long after any change is made to brightness (5 minutes at the earliest), and usually after "brightness up" is sent either through lovelace slider or a wireless dimmer knob/remote. I would agree strongly with a possible queue congestion if it was the same command as was last sent manually.
I've also had these WiZ bulbs set up "normally" for a long time before, controlling them all at once through a group, but no unexpected behaviour.
I'll do an experiment now and create a new lightener device with only 4 of the bulbs and see if there's a difference.
One noob question, I've enabled the debug logging, where is the log located?
There is no evidence that this issue is caused by Lightener. In fact, the source code doesn't give any indication that Lightener is capable of randomly changing the state of its controlled lights without receiving direct turn_on requests, which are handled immediately.
There's a good chance that this issue is related to the limitations of the installation and the smart home technology, especially regarding wireless devices. It's very likely that the wireless network is being flooded with light change requests that are being asynchronously handled in a non-linear way. That's, for sure, a difficult situation to fix or optimize.
I'm closing this issue for now, but I'll be happy to revisit it if it becomes clear that Lightener is the cause of this issue. Actually, I would be relieved if that were the case, as it would at least give us a chance to fix it.
@fcassata, please stay in touch if you have more news. Thanks!
|
gharchive/issue
| 2024-02-01T09:52:04 |
2025-04-01T04:34:18.370759
|
{
"authors": [
"fcassata",
"fredck"
],
"repo": "fredck/lightener",
"url": "https://github.com/fredck/lightener/issues/120",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
207397972
|
Raw dialogue
ideally right below raw images
done
|
gharchive/issue
| 2017-02-14T02:16:56 |
2025-04-01T04:34:18.387895
|
{
"authors": [
"fredhohman",
"ianbstewart"
],
"repo": "fredhohman/a-viz-of-ice-and-fire",
"url": "https://github.com/fredhohman/a-viz-of-ice-and-fire/issues/50",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
755388182
|
Query timeout
Hello everyone,
I'm having an issue with a query that is almost constantly timing out.
The query itself last max 15 sec and I have set up my config like this:
sql_exporter
global:
scrape_timeout_offset: 30s
prometheus:
scrape_interval: 60s
scrape_timeout: 55s
I have gone through the documentation and issues but I'm sure I'm missing something.
Please let me know if I should change something or config it differently.
Thanks and Best Regards
It is kind of hard to tell what's going on without any logs. All I can tell from looking at your configuration is that based on the configuration, the query has at most 25 seconds to complete (scrape_timeout - scrape_timeout_offset = 55s - 30s = 25s).
It could be that there are multiple Prometheus instances running the same query and the queries all get serialized. If so, I would set min_interval to 15s - 50s, so you serve cached metrics on some of those scrapes. May be worth doing regardless, a query that runs for 15 seconds is not something you want to run every couple of seconds. And regardless, I would drop the scrape_timeout_offset quite a bit. It's only there to cover network latency.
Did you look at your DB logs and saw that the query actually completes in 15 seconds when run by SQL Exporter?
|
gharchive/issue
| 2020-12-02T15:45:15 |
2025-04-01T04:34:18.401156
|
{
"authors": [
"aleksandarilic96",
"free"
],
"repo": "free/sql_exporter",
"url": "https://github.com/free/sql_exporter/issues/84",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2359517732
|
feat(5glan): add ue policy container
Add the ue policy container data type and related encode/decode way. Details can be found at 3GPP TS24.501 v17, chapter Annex D (normative): UE policy delivery service
I will fix the errors of linter
|
gharchive/pull-request
| 2024-06-18T10:29:52 |
2025-04-01T04:34:18.402185
|
{
"authors": [
"BENHSU0723"
],
"repo": "free5gc/nas",
"url": "https://github.com/free5gc/nas/pull/26",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1108399999
|
Stat increases / decreases not showing properly
What bug did you encounter?
Every time I answer a CS question correctly, my stat increases don't show properly. Instead the message states:
"[stats_name!t] knowledge increased by [val_str]"
When my sanity decreases after studying, it's the same thing.
Steps to Reproduce
Every time I study and answer quiz questions, it happens. Happens every time stats go up or down. Consistent from beginning to now.
Screenshots
Additional Information
I installed the game on my desktop. That wouldn't have any effect, right?
Hi @DuxVictorum. 6cd34d7a169b6135687cef971d15e861b78b6e47 should fixed it and the build on itch has been updated.
|
gharchive/issue
| 2022-01-19T18:02:08 |
2025-04-01T04:34:18.404798
|
{
"authors": [
"DuxVictorum",
"RuolinZheng08"
],
"repo": "freeCodeCamp/LearnToCodeRPG",
"url": "https://github.com/freeCodeCamp/LearnToCodeRPG/issues/61",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
1866028157
|
Replace DataTable with useTable inside adminTable.js
Describe the bug
The DataTable library is being used inside the adminTable component. This library has caused issues in the past. It needs to be removed and replaced with useTable from react.
To Reproduce
Steps to reproduce the behavior:
Go to '../components/adminTable.js'
Remove line 2, and replace it with import { useTable } from 'react-table'
Scroll down to line 5. Update the rest of the code to work with useTable, and render.
Additional context
The library useTable has been used in the past inside '../components/dashtable_v2.js'. Refer to this file for example.
I will be working on this.
Is this issue still open??
hey @Ranjan-bej, the issue is open but I am working on it. There should be a PR up soon.
is this PR still under review?
|
gharchive/issue
| 2023-08-24T23:41:30 |
2025-04-01T04:34:18.407906
|
{
"authors": [
"Komal914",
"Ranjan-bej",
"shootermv"
],
"repo": "freeCodeCamp/classroom",
"url": "https://github.com/freeCodeCamp/classroom/issues/467",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
294544247
|
BETA: separated margin & padding attributes taught, but clockwise notation accepted; minor formatting error too
Challenge Name
Basic CSS: Add Different Padding to Each Side of an Element
https://beta.freecodecamp.org/en/challenges/basic-css/add-different-padding-to-each-side-of-an-element
Basic CSS: Add Different Margins to Each Side of an Element
https://beta.freecodecamp.org/en/challenges/basic-css/add-different-margins-to-each-side-of-an-element
Basic CSS: Use Clockwise Notation to Specify the Padding of an Element
https://beta.freecodecamp.org/en/challenges/basic-css/use-clockwise-notation-to-specify-the-padding-of-an-element
Basic CSS: Use Clockwise Notation to Specify the Margin of an Element
https://beta.freecodecamp.org/en/challenges/basic-css/use-clockwise-notation-to-specify-the-margin-of-an-element
Issue Description
The first two challenges teach individual property usage for borders and margins, while the last 2 teach clockwise notation. I completed the first two using clockwise notation and my solutions were accepted, despite the goal of learning the long form. If the goal is to have them use the long form, why accept the short form on the first two challenges?
Also, in the 4th challenge, for some reason the phrase "Clockwise Notation" is formatted as if it were part of a property, whereas it is correctly without formatting in the 3rd.
Screenshot
3rd challenge:
4th challenge (note the incorrect formatting):
Instead of focussing on the solutions, we can remove the first two Challenges and mention the margin-left,margin-right, etc properties. The content might be a 'little' long, but if written properly, it could be made more concise.
As for the minor formatting error, I would be happy to modify it and submit a PR within an hour once I have your permission for it.
@utkarshsingh99
I think there is worth in teaching these progressively and keeping the challenges. To an expert/advanced eye this may look a little too easy, or redundant, but trust me new comers usually feel this is good to be a exercise.
But, we would love a pull request for the formatting issue on the fourth challenge in the OP.
Thanks for your interest in tackling that.
@ReveurGAM
Thanks for the issue and the feedback.
If the goal is to have them use the long form, why accept the short form on the first two challenges?
While there is no harm in accepting short form, because its not explicitly being said to NOT do that in the description. But, I agree we can check for this in the tests.
Happy contributing!
@raisedadead I did some analysis and the tests for this challenge checks for paddings from the output pane. We need to add the test to assert user-written code.
I'm closing this issue as stale since it hasn't been active lately. If you think this is still relevant to the newly updated platform, please explain why, then reopen it.
|
gharchive/issue
| 2018-02-05T21:14:07 |
2025-04-01T04:34:18.415453
|
{
"authors": [
"QuincyLarson",
"ReveurGAM",
"ninadingole",
"raisedadead",
"utkarshsingh99"
],
"repo": "freeCodeCamp/freeCodeCamp",
"url": "https://github.com/freeCodeCamp/freeCodeCamp/issues/16651",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
718099577
|
I feel Linked Lists should be taught BEFORE having us do Circular Queue in the Advanced section
I just took a step back to fully learn data structures and I am watching one of FCC's videos: https://www.youtube.com/watch?v=RBSGKlAvoiM
An amazing video. I just learned about linked lists and noticed something.
In FCC Interview Section: https://www.freecodecamp.org/learn/coding-interview-prep/data-structures/create-a-circular-queue
We are challenged to do circular queue, honestly in my opinion that thing was hard to understand and still kinda is, but after learning Linked Lists, I see that Circular Queue uses an implementation of Linked Lists in it, which is why I think Linked Lists should probably be taught first to give people more of an understanding on how to solve that challenge. Maybe that or edit it a bit to make a bit more sense, idk
Just a small thing I figured I should point out.
Also I think its broken
is there any way I can help? like I have learned linked list, doubly linked list, circular, stack, queue.
I'm not 100% sure I agree, here.
A queue is still first-in-first-out, even when it's circular. I can see how some of the syntax might be similar, because it's still class-based, but I would argue that the circular queue is more relevant to the other queue lessons than the linked list lessons.
Since this issue has had no activity, I think it is safe to close for now. If anyone would like to discuss this restructure further, let us know and we can reopen this. 🙂
|
gharchive/issue
| 2020-10-09T12:18:19 |
2025-04-01T04:34:18.419586
|
{
"authors": [
"Dilip-Jain",
"Symbolistic",
"nhcarrigan"
],
"repo": "freeCodeCamp/freeCodeCamp",
"url": "https://github.com/freeCodeCamp/freeCodeCamp/issues/39834",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
1943993255
|
Jidu search
Describe the Issue
In there there's a problem in broken searching
Affected Page
colonile.blogspot.com
Your code
Expected behavior
Hg
Screenshots
No response
System
Device: [e.g. iPhone 6, Laptop]
OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04]
Browser: [e.g. Chrome, Safari]
Version: [e.g. 22]
Additional context
No response
Usvxv
I don't think that website is associated with freeCodeCamp?
|
gharchive/issue
| 2023-10-15T18:05:49 |
2025-04-01T04:34:18.423495
|
{
"authors": [
"jeremylt",
"sayandutta635"
],
"repo": "freeCodeCamp/freeCodeCamp",
"url": "https://github.com/freeCodeCamp/freeCodeCamp/issues/51989",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
2017060036
|
[python]: bad script fails wrong test
I do not really know how to word the problem other than:
Follow instructions of challenge to best of ability
Run tests
See hint given does not correspond to issue
Expected Behaviour
When tests do not rely on Camper code "compiling", the tests should still be allowed to pass/run.
OR
When Camper code does not "compile", a different error should appear other than defaulting to the first hint
I'm going to need some more context. Which challenge is this and where is the code?
Duplicate of https://github.com/freeCodeCamp/freeCodeCamp/issues/52411
Thanks @ieahleen 🚀
@ojeytonwilliams As also shown in #52411 , if I have a test assert.match(code, /a = 1/), but a Camper has a syntax/logic error in their Python:
a = 1
b =
The tests will fail, and the first hint text will be given to the Camper. That hint text could be You should have "a = 1" in your code (which it clearly does). So, the hint does not make sense.
Thanks for clarifying, @ieahleen and @ShaunSHamilton. Is the desired behaviour: if the python script raises an exception, show a hint like "something went wrong in your python script, please see the console for more information"?
Is the desired behaviour:
I would say we should have the option to:
a) Allow an invalid script to pass all tests (what if we want to show what happens with errors) - just test the code string
b) Manually check the code exceptions or not
Closed by #53040
|
gharchive/issue
| 2023-11-29T17:13:19 |
2025-04-01T04:34:18.429250
|
{
"authors": [
"ShaunSHamilton",
"ieahleen",
"ojeytonwilliams"
],
"repo": "freeCodeCamp/freeCodeCamp",
"url": "https://github.com/freeCodeCamp/freeCodeCamp/issues/52448",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
143119571
|
Change Text Inside an Element Using jQuery NOT WORKING
FreeCodeCamp Issue template
To Use this Template:
Fill out what you can
Delete what you do not fill out
NOTE: ISSUES ARE NOT FOR CODE HELP - Ask for Help at https://gitter.im/FreeCodeCamp/Help
Issue Description
When Issue Happens: Every time
Steps To Reproduce: Go to the challenge and try it
Browser Information
current version of Firefox
Operating System
Windows 7
jQuery Playground
#left-well
#target1
#target2
#target3
#right-well
#target4
#target5
#target6
Where is your code?
jQuery Playground
#left-well
#target1
#target2
#target3
#right-well
#target4
#target5
#target6
Sorry. Pasting it wasn't working properly. Here is a pertinent screenshot.
You should use .html() instead of .text() for this challenge.
This part of the instructions may be the cause of confusion:
jQuery also has a similar function called .text() that only alters text without adding tags.
It could be rewritten so it's clear to students that .text() will not evaluate the tags in the string input as HTML and instead treat them as part of the text.
Thank you for the reply, sir. However, I tried it with .html as well as with .text and it still did not work. Please go to this challenge amd see for yourself. If I am makimg a mistake I do not knlw what it is. I have tried it any number of ways and it does not work.
In your original code, you were missing the # in front of target4.
@alistermada Thanks for the for the clarification, we could add a test to check campers are not reading through the lines, and getting confused?
Make sure you are using .html() and not .text()
or something on similar lines.
@raisedadead Sounds like a good idea to me.
Thank you. I can't believe I missed that.
I and others are using .html (and trying instead of ) to no avail. Clicking "Run Test" does not return an error or a success message, nothing happens. Others reports her of same issue with what I assume is exactly correct code:
$(document).ready(function() { $("#target1").css("color", "red"); $("#target4").html("<em>$target4</em>"); });
I'm guessing it's correct because it does change the text of target 4 to italics within the codecamp editor or in a separate environment like cloud9 or codeanywhere.com etc.
@texxs It should be #target4 instead of $target4 between the tags.
Ya got me on that one! Thanks. :)
Is this still and issue? and if so what is the exact issue? It seems like the test in staging was updated to look for em tags and the text about .text seems clear enough to me. Though seems like an aside that may not be needed since the .text method isn't relevant to what is being looked for.
If I were to draw issues with this one it would be the following.
The title is "Change Text Inside an Element Using jQuery", yet that is not what you are asked to do. You are asked to add tags, without changing the text.
There is another jQuery method to add tags without changing text that may be better suited, .wrapInner, since it will do what is looked for adding tags without changing the text, inside of #target4$('#target4').wrapInner('<em></em>')
where as using .html you have to add the text again.
Using .wrapInner will pass the test by the way, so should a test be added to check that .html is being used?
Just looking for some clarification?
this worked for me
@cinquemason
Please don't put your solution on here. You could help people at FreeCodeCamp Chat Room or Forum. GitHub Issues are for reporting bugs on the website only.
Happy Coding!
@amin8666 please reach out to the Help Chat Room.
You could try code as below:
$("#target4").html("#target4");
change , to
then run tests
@cainesim I am also getting the same error. Can't see any issue. Did you find any solution ?
here is a solution !!!
In the exercise it says
Make sure to select button id="target4" with jQuery.
What is it exactly implying upon?
Not working... here is the screenshot...
|
gharchive/issue
| 2016-03-24T01:18:09 |
2025-04-01T04:34:18.449147
|
{
"authors": [
"Arash1982",
"Getachew-Mulat",
"Mikaiyl",
"Preeetrockz",
"alistermada",
"amin8666",
"cainesim",
"cinquemason",
"ebrees",
"gracexu222",
"jnmorse",
"piyushkathayat",
"raisedadead",
"texas2010",
"texxs"
],
"repo": "freeCodeCamp/freeCodeCamp",
"url": "https://github.com/freeCodeCamp/freeCodeCamp/issues/7713",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
311459805
|
fix(challenges): Tests are not shown on visiting challenges for the first time
Closes #16948
Pre-Submission Checklist
[x] Your pull request targets the staging branch of freeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.
Type of Change
[x] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)
Checklist:
[x] Tested changes locally.
[x] Addressed currently open issue (replace XXXXX with an issue no in next line)
Closes #16948
Description
When you visit a challenge, the test sometimes are not showing. This pr solves that issue.
To reproduce the issue:
Open a block(here a request is being made to the server for the block's data) then quickly select a challenge inside that block before the response from the server for that block request arrives.
how to store looks that is related for reference:
store: { entities: { challenge: { challengename: { challengeinformation } } }, challenge: { tests: { here are the tests } } }
The cause:
The lesson pane is where the tests and other information of the challenge is shown. This pane has selectors for the information of the challenge. Every selector points for the information of the challenge in the store to "entities: challenge: challengename: challengeinformation" except the tests selector. The tests are stored in "challenges: tests". When the block data arrives from the server it updates the "entities" where the information of the challenge is being stored, but the "challenges" where the tests are being selected from is not getting updated. Because of this when you reproduce the issue successfully, you are going to see the skeleton loading of the challenge in the lesson pane, but tests are going to be already displayed incorrectly(meaning they have been selected already but since there were no data yet the tests array is going to be empty), and when the block data arrives, the skeleton loading is being replaced, but the tests are not.
ds
This solution:
The "app.fetchNewBlock.complete" action is now going to have the challenge information that is currently selected if there is a challenge currently selected. This action is going to also arrive now in the challenges reducer with the currently selected challenge. In this reducer if there is a challenge in the payload, its going to update the "challenge" part of the store which contains the tests that are being selected in the lesson pane.
Related files:
Lesson pane to check the selectors.
fetchNewBlockCompleted this updates the "entities" but not the "challenge" where the tests are.
Reducer of challenge this is where the tests are being updated.
There may be better solutions but atleast you can indentify the problem from this. Hopefully my explanation is not gibberish.
@absolitudo Thank you for your work on this, sorry for the delay in getting round to it.
Are the tests available under store.entities the way the rest of the challenge data is? If so, can you update the testsSelector to access them there.
The fetchChallenge reducer deals only with the fetching of the current challenge after a direct navigation, i.e. navigation the the challenge URL rather than clicking on the map or completing a challenge.
Are the tests available under store.entities the way the rest of the challenge data is? If so, can you update the testsSelector to access them there.
Yes they are available there, but there are a couple of problems that need to be considered. One is that the tests are not in the format that the component is able to display them. The tests go through a function called "createTests". This function is here: https://github.com/freeCodeCamp/freeCodeCamp/blob/30b26e1476eb2e40695256c5e060c2d804138789/common/app/routes/Challenges/utils/index.js
The selector could use this function to format the tests.
The other problem is related to executing the challenge. I don't completely understand what is happening when you execute the challenge but at least in the challenge reducer the tests are being used from store.challenge.tests so in order for that to still work the tests would need to be present there. The current bug is produced because in store.challenge.tests no tests are present.
The reducer: https://github.com/freeCodeCamp/freeCodeCamp/blob/167b60985353ccce69181cbe7d365d3cafb69c49/common/app/routes/Challenges/redux/index.js
ctrl + f: types.executeChallenge
Hi @absolitudo once again!
I have replied on https://github.com/freeCodeCamp/freeCodeCamp/pull/16986
Once again thanks a lot for taking the time to make this pull-request.
Happy contributing!
|
gharchive/pull-request
| 2018-04-05T03:20:28 |
2025-04-01T04:34:18.463036
|
{
"authors": [
"Bouncey",
"absolitudo",
"raisedadead"
],
"repo": "freeCodeCamp/freeCodeCamp",
"url": "https://github.com/freeCodeCamp/freeCodeCamp/pull/17029",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
370067029
|
Added sample code for D3Js library.
I've appended the code for a simple html file which renders text using D3JS library.
[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.
If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX
@devanshhu Awesome! Thanks! Congrats on your first open source contribution to this repository!
|
gharchive/pull-request
| 2018-10-15T09:08:45 |
2025-04-01T04:34:18.466549
|
{
"authors": [
"QuincyLarson",
"devanshhu"
],
"repo": "freeCodeCamp/freeCodeCamp",
"url": "https://github.com/freeCodeCamp/freeCodeCamp/pull/19227",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
372182264
|
Remove the redundant "[" before "this" word
[x ] I have read freeCodeCamp's contribution guidelines.
[ x] My pull request has a descriptive title (not a vague title like Update index.md)
[x ] My pull request targets the master branch of freeCodeCamp.
[x ] None of my changes are plagiarized from another source without proper attribution.
[x ] My article does not contain shortened URLs or affiliate links.
If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX
Thank you @Qbuiba for your contribution.
|
gharchive/pull-request
| 2018-10-20T07:09:48 |
2025-04-01T04:34:18.469203
|
{
"authors": [
"Qbuiba",
"ezioda004"
],
"repo": "freeCodeCamp/freeCodeCamp",
"url": "https://github.com/freeCodeCamp/freeCodeCamp/pull/24015",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
372873769
|
Update index.md
[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.
If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX
Thank you for opening this pull request.
Book recommendations are beyond the scope of the freeCodeCamp Guide, so we've decided to go ahead and remove these book recommendation articles.
I encourage you to review this book in the ratings category of the freeCodeCamp forum. Your recommendation will reach way more people there.
Thanks again recommending this book, and for contributing to the freeCodeCamp Guide.
|
gharchive/pull-request
| 2018-10-23T08:33:50 |
2025-04-01T04:34:18.472830
|
{
"authors": [
"QuincyLarson",
"mejraf"
],
"repo": "freeCodeCamp/freeCodeCamp",
"url": "https://github.com/freeCodeCamp/freeCodeCamp/pull/26774",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.