Cannot get FlutterFire to work with iOS

I've tried so many things that its going to be hard to pin this one down, so apologies in advance.
I followed the instructions on Firebase Console (cannot link) and https://codelabs.developers.google.com/codelabs/flutter-firebase/#5
using cocoapods 1.5.3

installed credentials into ios/Runner/GoogleService-Info.plist
did flutter run
got error fatal error: 'firebase_core/FirebaseCorePlugin.h' file not found

using cocoapods 1.4.0

did flutter clean; flutter run

got error fatal error: 'firebase_core/FirebaseCorePlugin.h' file not found
using cocoapods 1.5.3

found this https://stackoverflow.com/questions/50125534/firestore-is-failed-to-build-with-flutter-for-ios
pasted this into my Podfile https://github.com/flutter/flutter/blob/master/packages/flutter_tools/templates/cocoapods/Podfile-objc
flutter clean; flutter run

got error
5.4.0 - [Firebase/Core][I-COR000003] The default Firebase app has not yet been configured. Add `[FIRApp configure];` (`FirebaseApp.configure()` in Swift) to your application initialization. Read more: https://goo.gl/ctyzm8.
5.4.0 - [Firebase/Core][I-COR000012] Could not locate configuration file: 'GoogleService-Info.plist'.

using cocoapods 1.5.3

pasted this into my Podfile because I have no idea if Flutter uses obj-c or swift out of the box https://github.com/flutter/flutter/blob/master/packages/flutter_tools/templates/cocoapods/Podfile-swift
flutter clean; flutter run

got error
5.4.0 - [Firebase/Core][I-COR000003] The default Firebase app has not yet been configured. Add `[FIRApp configure];` (`FirebaseApp.configure()` in Swift) to your application initialization. Read more: https://goo.gl/ctyzm8.
5.4.0 - [Firebase/Core][I-COR000012] Could not locate configuration file: 'GoogleService-Info.plist'.

user story
Guy knows barely enough es6 javascript to be dangerous and likes react. Decides to learn React-Native. starts to realize that third party libraries are horrible and looks into Flutter. Is excited, perhaps mistakenly so, that he doesn't have to learn anything about iOS/Android specific builds. Uses npm install firebase nearly daily for all kinds of projects. Goes to install Firebase into his shiny new Flutter project and the whole process falls flat on its face with very little guidance from Flutter team. Finds some whisperings about this being fixed but can't find any resolution.
Any help?

using flutter branch dev

flutter clean; flutter run

Failed to build iOS app
Error output from Xcode build:
↳
    ** BUILD FAILED **

Xcode's output:
↳
    === BUILD TARGET Runner OF PROJECT Runner WITH CONFIGURATION Debug ===
    /Users/lukepighetti/code/when-coin/when_coin/ios/Runner/GeneratedPluginRegistrant.m:6:9: fatal error: 'firebase_core/FirebaseCorePlugin.h' file not found
    #import <firebase_core/FirebaseCorePlugin.h>
            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1 error generated.

OK. I'm going to try again from stage 1.

flutter channel dev
create flutter project in VSC
make first commit with a basic layout
open Runner.xcodeproj
set team to ME!
put bundle identifier com.example.myproject into firebase console
give it a name in Firebase console
do not give it an App Store id
download GoogleService-Info.plist
move it to ios/Runner/
cd ios
pod --version >> 1.5.3
pod init >> no response

Podfile looks like this
# Uncomment the next line to define a global platform for your project
# platform :ios, '9.0'

target 'Runner' do
  # Uncomment the next line if you're using Swift or would like to use dynamic frameworks
  # use_frameworks!

  # Pods for Runner

end

Add pod 'Firebase/Core' to Podfile
# Uncomment the next line to define a global platform for your project
# platform :ios, '9.0'

target 'Runner' do
  # Uncomment the next line if you're using Swift or would like to use dynamic frameworks
  # use_frameworks!

  # Pods for Runner
  pod 'Firebase/Core'

end

pod install

Lukes-iMac:ios lukepighetti$ pod install
Analyzing dependencies
Downloading dependencies
Installing Firebase (5.4.0)
Installing FirebaseAnalytics (5.0.1)
Installing FirebaseCore (5.0.5)
Installing FirebaseInstanceID (3.1.1)
Installing GoogleToolboxForMac (2.1.4)
Installing nanopb (0.3.8)
Generating Pods project
Integrating client project
Sending stats
Pod installation complete! There is 1 dependency from the Podfile and 6 total pods installed.

[!] Automatically assigning platform `ios` with version `8.0` on target `Runner` because no platform was specified. Please specify a platform for this target in your Podfile. See `https://guides.cocoapods.org/syntax/podfile.html#platform`.

[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `Runner` to `Pods/Target Support Files/Pods-Runner/Pods-Runner.debug.xcconfig` or include the `Pods/Target Support Files/Pods-Runner/Pods-Runner.debug.xcconfig` in your build configuration (`Flutter/Debug.xcconfig`).

[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `Runner` to `Pods/Target Support Files/Pods-Runner/Pods-Runner.release.xcconfig` or include the `Pods/Target Support Files/Pods-Runner/Pods-Runner.release.xcconfig` in your build configuration (`Flutter/Release.xcconfig`).

added initialization code

#include "AppDelegate.h"
@import Firebase;
#include "GeneratedPluginRegistrant.h"

@implementation AppDelegate

- (BOOL)application:(UIApplication *)application
    didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
      [FIRApp configure];
  [GeneratedPluginRegistrant registerWithRegistry:self];
  // Override point for customization after application launch.
  return [super application:application didFinishLaunchingWithOptions:launchOptions];
}

@end

cd ..; flutter run

Failed to build iOS app
Error output from Xcode build:
↳
    ** BUILD FAILED **

Xcode's output:
↳
    === BUILD TARGET Runner OF PROJECT Runner WITH CONFIGURATION Debug ===
    diff: /Podfile.lock: No such file or directory
    diff: /Manifest.lock: No such file or directory
    error: The sandbox is not in sync with the Podfile.lock. Run 'pod install' or update your CocoaPods installation.
Could not build the application for the simulator.
Error launching application on iPhone X.

pod install >> No podfile found

cd ios; pod install

Analyzing dependencies
Downloading dependencies
Using Firebase (5.4.0)
Using FirebaseAnalytics (5.0.1)
Using FirebaseCore (5.0.5)
Using FirebaseInstanceID (3.1.1)
Using GoogleToolboxForMac (2.1.4)
Using nanopb (0.3.8)
Generating Pods project
Integrating client project
Sending stats
Pod installation complete! There is 1 dependency from the Podfile and 6 total pods installed.

[!] Automatically assigning platform `ios` with version `8.0` on target `Runner` because no platform was specified. Please specify a platform for this target in your Podfile. See `https://guides.cocoapods.org/syntax/podfile.html#platform`.

[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `Runner` to `Pods/Target Support Files/Pods-Runner/Pods-Runner.debug.xcconfig` or include the `Pods/Target Support Files/Pods-Runner/Pods-Runner.debug.xcconfig` in your build configuration (`Flutter/Debug.xcconfig`).

[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `Runner` to `Pods/Target Support Files/Pods-Runner/Pods-Runner.release.xcconfig` or include the `Pods/Target Support Files/Pods-Runner/Pods-Runner.release.xcconfig` in your build configuration (`Flutter/Release.xcconfig`).

OK. looks like this isn't working, will try another way

Does anyone have a boilerplate project for FlutterFire that works with iOS and Android? I keep trying different ways and I solve some issues and get others such as
5.4.0 - [Firebase/Core][I-COR000012] Could not locate configuration file: 'GoogleService-Info.plist'.
5.4.0 - [Firebase/Core][I-COR000005] No app has been configured yet.

I'm totally at a loss here.

OK this appears to be WAY easier than the documentation would have you believe.

new flutter project
new iOS app in Firebase Console
put GoogleService-Info.plist into Runner directory in XCode!!!!!!!!!!!!!!
make pubspec.yaml look like this

dependencies:
  flutter:
    sdk: flutter
  firebase_core: "^0.2.4"
  firebase_database: "^1.0.1"

flutter packages get
flutter run

and it appears to work just fine
Also, there appears to be an error that most people ignore and continue to develop.
5.4.0 - [Firebase/Core][I-COR000003] The default Firebase app has not yet been configured. Add `[FIRApp configure];` (`FirebaseApp.configure()` in Swift) to your application initialization. Read more: https://goo.gl/ctyzm8.
5.4.0 - [Firebase/Analytics][I-ACS023007] Firebase Analytics v.50001000 started
5.4.0 - [Firebase/Analytics][I-ACS023008] To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see http://goo.gl/RfcP7r)

This will get rid of that error message on Objective-C project
ios/Runner/AppDelegate.m
#include "AppDelegate.h"
#include "GeneratedPluginRegistrant.h"
@import Firebase; // ADD THIS

@implementation AppDelegate

- (BOOL)application:(UIApplication *)application
    didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
  [FIRApp configure]; // ADD THIS
  [GeneratedPluginRegistrant registerWithRegistry:self];
  // Override point for customization after application launch.
  return [super application:application didFinishLaunchingWithOptions:launchOptions];
}

@end

I am updating my recommendation to not use Xcode to place GoogleService-Info.plist into ios/Runner because it appears to create a link instead of actually copying the file. If you delete the file (like move it from Downloads to Trash) it will break things.

Hi, I did follow all the troubleshoots above but I still get this error. Tested on iOS Simulator.
    /Users/yousoffeffendy/Documents/personal/workspace/flutter-workspace/flutter-firebase-crud-app/ios/Runner/GeneratedPluginRegistrant.m:6:9: fatal error: 'firebase_core/FirebaseCorePlugin.h' file not found
    #import <firebase_core/FirebaseCorePlugin.h>

Can assist ?
[✓] Flutter (Channel dev, v0.8.2, on Mac OS X 10.13.6 17G65, locale en-MY)
    • Flutter version 0.8.2 at /Users/yousoffeffendy/Documents/software/flutter
    • Framework revision 5ab9e70727 (6 days ago), 2018-09-07 12:33:05 -0700
    • Engine revision 58a1894a1c
    • Dart version 2.1.0-dev.3.1.flutter-760a9690c2

[!] Android toolchain - develop for Android devices (Android SDK 28.0.2)
    • Android SDK at /Users/yousoffeffendy/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses

[✓] iOS toolchain - develop for iOS devices (Xcode 9.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 9.4.1, Build version 9F2000
    • ios-deploy 1.9.2
    • CocoaPods version 1.5.3

[✓] Android Studio (version 3.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)

[✓] Connected devices (1 available)
    • iPhone X • 569D3D1B-E828-4A98-AE81-3B5950B6AAE7 • ios • iOS 11.4 (simulator)

oh ok.. I follow this url above, replace podfile and everything works fine https://github.com/flutter/flutter/blob/master/packages/flutter_tools/templates/cocoapods/Podfile-swift

Hi, I did follow all the troubleshoots above but I still get this error. Tested on iOS Simulator.
    /Users/yousoffeffendy/Documents/personal/workspace/flutter-workspace/flutter-firebase-crud-app/ios/Runner/GeneratedPluginRegistrant.m:6:9: fatal error: 'firebase_core/FirebaseCorePlugin.h' file not found
    #import <firebase_core/FirebaseCorePlugin.h>

Can assist ?
[✓] Flutter (Channel dev, v0.8.2, on Mac OS X 10.13.6 17G65, locale en-MY)
    • Flutter version 0.8.2 at /Users/yousoffeffendy/Documents/software/flutter
    • Framework revision 5ab9e70727 (6 days ago), 2018-09-07 12:33:05 -0700
    • Engine revision 58a1894a1c
    • Dart version 2.1.0-dev.3.1.flutter-760a9690c2

[!] Android toolchain - develop for Android devices (Android SDK 28.0.2)
    • Android SDK at /Users/yousoffeffendy/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses

[✓] iOS toolchain - develop for iOS devices (Xcode 9.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 9.4.1, Build version 9F2000
    • ios-deploy 1.9.2
    • CocoaPods version 1.5.3

[✓] Android Studio (version 3.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)

[✓] Connected devices (1 available)
    • iPhone X • 569D3D1B-E828-4A98-AE81-3B5950B6AAE7 • ios • iOS 11.4 (simulator)

Did you get it fixed? if so please share, I'm also stuck

@sudharsanprasadh your Flutter version is quite outdated (from September)

OK. I'm going to try again from stage 1.

flutter channel dev
create flutter project in VSC
make first commit with a basic layout
open Runner.xcodeproj
set team to ME!
put bundle identifier com.example.myproject into firebase console
give it a name in Firebase console
do not give it an App Store id
download GoogleService-Info.plist
move it to ios/Runner/
cd ios
pod --version >> 1.5.3
pod init >> no response

Podfile looks like this
# Uncomment the next line to define a global platform for your project
# platform :ios, '9.0'

target 'Runner' do
  # Uncomment the next line if you're using Swift or would like to use dynamic frameworks
  # use_frameworks!

  # Pods for Runner

end

Add pod 'Firebase/Core' to Podfile
# Uncomment the next line to define a global platform for your project
# platform :ios, '9.0'

target 'Runner' do
  # Uncomment the next line if you're using Swift or would like to use dynamic frameworks
  # use_frameworks!

  # Pods for Runner
  pod 'Firebase/Core'

end

pod install

Lukes-iMac:ios lukepighetti$ pod install
Analyzing dependencies
Downloading dependencies
Installing Firebase (5.4.0)
Installing FirebaseAnalytics (5.0.1)
Installing FirebaseCore (5.0.5)
Installing FirebaseInstanceID (3.1.1)
Installing GoogleToolboxForMac (2.1.4)
Installing nanopb (0.3.8)
Generating Pods project
Integrating client project
Sending stats
Pod installation complete! There is 1 dependency from the Podfile and 6 total pods installed.

[!] Automatically assigning platform `ios` with version `8.0` on target `Runner` because no platform was specified. Please specify a platform for this target in your Podfile. See `https://guides.cocoapods.org/syntax/podfile.html#platform`.

[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `Runner` to `Pods/Target Support Files/Pods-Runner/Pods-Runner.debug.xcconfig` or include the `Pods/Target Support Files/Pods-Runner/Pods-Runner.debug.xcconfig` in your build configuration (`Flutter/Debug.xcconfig`).

[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `Runner` to `Pods/Target Support Files/Pods-Runner/Pods-Runner.release.xcconfig` or include the `Pods/Target Support Files/Pods-Runner/Pods-Runner.release.xcconfig` in your build configuration (`Flutter/Release.xcconfig`).

added initialization code

#include "AppDelegate.h"
@import Firebase;
#include "GeneratedPluginRegistrant.h"

@implementation AppDelegate

- (BOOL)application:(UIApplication *)application
    didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
      [FIRApp configure];
  [GeneratedPluginRegistrant registerWithRegistry:self];
  // Override point for customization after application launch.
  return [super application:application didFinishLaunchingWithOptions:launchOptions];
}

@end

cd ..; flutter run

Failed to build iOS app
Error output from Xcode build:
↳
    ** BUILD FAILED **

Xcode's output:
↳
    === BUILD TARGET Runner OF PROJECT Runner WITH CONFIGURATION Debug ===
    diff: /Podfile.lock: No such file or directory
    diff: /Manifest.lock: No such file or directory
    error: The sandbox is not in sync with the Podfile.lock. Run 'pod install' or update your CocoaPods installation.
Could not build the application for the simulator.
Error launching application on iPhone X.

pod install >> No podfile found
cd ios; pod install

Analyzing dependencies
Downloading dependencies
Using Firebase (5.4.0)
Using FirebaseAnalytics (5.0.1)
Using FirebaseCore (5.0.5)
Using FirebaseInstanceID (3.1.1)
Using GoogleToolboxForMac (2.1.4)
Using nanopb (0.3.8)
Generating Pods project
Integrating client project
Sending stats
Pod installation complete! There is 1 dependency from the Podfile and 6 total pods installed.

[!] Automatically assigning platform `ios` with version `8.0` on target `Runner` because no platform was specified. Please specify a platform for this target in your Podfile. See `https://guides.cocoapods.org/syntax/podfile.html#platform`.

[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `Runner` to `Pods/Target Support Files/Pods-Runner/Pods-Runner.debug.xcconfig` or include the `Pods/Target Support Files/Pods-Runner/Pods-Runner.debug.xcconfig` in your build configuration (`Flutter/Debug.xcconfig`).

[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `Runner` to `Pods/Target Support Files/Pods-Runner/Pods-Runner.release.xcconfig` or include the `Pods/Target Support Files/Pods-Runner/Pods-Runner.release.xcconfig` in your build configuration (`Flutter/Release.xcconfig`).

OK. looks like this isn't working, will try another way

thanks to you. i seem easier than expect.

I still got the Could not locate configuration file: 'GoogleService-Info.plist'. error.
Eventually I found the way to fix it:

Download the GoogleService-Info.plist file from Firebase
Place it in the ios/Runner directory of your flutter project
open XCode with open ios/Runner.xcworkspace
In XCode, drag the file GoogleService-Info.plist from your finder, to the yellow Runner folder underneath the blue RunnerProject`, (in the project navigator on the left side of the screen). This the main step that was missing (at least, for me).

@dotdotcommadot

I still got the Could not locate configuration file: 'GoogleService-Info.plist'. error.
Eventually I found the way to fix it:
* Download the `GoogleService-Info.plist` file from Firebase

* Place it in the `ios/Runner` directory of your flutter project

* open XCode with `open ios/Runner.xcworkspace`

* In XCode, drag the file `GoogleService-Info.plist` from your finder, to the yellow `Runner` folder underneath the blue `Runner`Project`, (in the project navigator on the left side of the screen). This the main step that was missing (at least, for me).

This helped me.

In XCode, drag the file GoogleService-Info.plist from your finder, to the yellow Runner folder underneath the blue RunnerProject`, (in the project navigator on the left side of the screen). This the main step that was missing (at least, for me).

After a lot of trial and error, this is what finally made it work for me. No idea why this was never mentioned in the documentation.

This worked for me as well -- and should be in the instructions.

I am developing for Android and IOS. After many trial and error, I discovered my setting in the pubspec.yaml file for android would have to be different for that of ios
For Android:
firebase_core:^0.2.0
firebase_auth: ^0.7.0

while for ios:
firebase_core:^0.4.0
firebase_auth: ^0.11.1+8

oh ok.. I follow this url above, replace podfile and everything works fine https://github.com/flutter/flutter/blob/master/packages/flutter_tools/templates/cocoapods/Podfile-swift

Broken link. Anyone else got this to work with a Swift AppDeligate ?

Opening new issue, this is not fixed.

In My flutter app
Im getting 'Could not locate configuration file: 'GoogleService-Info.plist'.' error
Running Xcode build...
Xcode build done.                                           21.9s
path: satisfied (Path is satisfied), interface: en0, expensive
6.18.0 - [Firebase/Core][I-COR000012] Could not locate configuration file: 'GoogleService-Info.plist'.
*** First throw call stack:
(
0   CoreFoundation                      0x00007fff23c7127e __exceptionPreprocess + 350
1   libobjc.A.dylib                     0x00007fff513fbb20 objc_exception_throw + 48
2   CoreFoundation                      0x00007fff23c710bc +[NSException raise:format:] + 188
3   Runner                              0x00000001017897aa +[FIRApp configure] + 138
4   Runner                              0x00000001015c8f3d -[AppDelegate application:didFinishLaunchingWithOptions:] + 93
5   UIKitCore                           0x00007fff48089ad8 -[UIApplication _handleDelegateCallbacksWithOptions:isSuspended:restoreState:] + 232
6   UIKitCore                           0x00007fff4808b460 -[UIApplication _callInitializationDel<…>
This is taking longer than expected...


Better display of toots

The Mastodon API returns toots as HTML strings. The current view simply strips off all the markup and interprets the result as Markdown. This is not pretty, messes up hashtags, and prevents links from being clickable.

Also: media attachments are ignored for now. At least images should be displayed.

Attachment handling is now reasonable (image previews shown in-line, links to attachments shown for all types). Text display has also improved, but requires more work, in particular for hashtags.


TreeView not working with showTags

Hi,
if you set showTags to true the following exception occurs.
I made a fiddle
jQuery.Deferred exception: Cannot read property '0' of undefined TypeError: Cannot read property '0' of undefined
at Tree.addTag (https://rawgit.com/patternfly/patternfly-bootstrap-treeview/master/dist/bootstrap-treeview.js:975:29)
Problem is in line 977 tagsClass is undefinded.
typeof node.tagsClass[id] === 'string' ?
hope this helps.

You probably linked a wrong fiddle, could you please update it? Thanks!

Thank you. Issue updated.
working fiddle

Release pushed, should work


Write-Output -NoEnumerate outputs PSObject[] rather than Object[] and generally doesn't respect the input collection type

Related: #5122

Write-Output -NoEnumerate, when given a collection, always returns a PSObject[] rather than a regular object[]] array, which is unexpected.

Additionally, this means that if a different collection type such as [System.Collections.ArrayList] was passed, it is not preserved.

Write-Output's documentation, which currently only states, "prevents Write-Output from enumerating output", which sounds like the input collection - whatever its type - is simply passed through - a sensible expectation that Windows PowerShell versions up to v5.1  indeed honor.

I suspect this regression is a consequence of the ill-fated #2038 PR that arose out of issue #2035.
Steps to reproduce
(Write-Output -NoEnumerate 1, 2).GetType().Name
(Write-Output -NoEnumerate ([System.Collections.ArrayList] (1, 2))).GetType().Name

Expected behavior
Object[]
ArrayList

This is how it still works in Windows PowerShell v5.1
Actual behavior
PSObject[]
PSObject[]

As stated, this affects PS Core only.
Environment data
PowerShell Core v6.0.0 on macOS 10.13.2
PowerShell Core v6.0.0 on Ubuntu 16.04.3 LTS
PowerShell Core v6.0.0 on Microsoft Windows 10 Pro (64-bit; v10.0.15063)

How has this been allowed to continue for this long?

@Jaykul Fixing this now. After a longer-than-necessary foray into the pipeline files, it turns out that typing your parameters as PSObject[] forces PS to enumerate whatever collection you throw at it during the parameter binding stage. Typing the param as PSObject works for both singletons and collections just fine, though.


Typed throws

Start implementing typed throw specifiers with the syntax throws(X).

[x] Parsing throws(X) as an effect specifier everywhere it is needed (functions, initializers, accessors, closures, function types, expressions that can become function types)
[x] AST representation for having a specified thrown type on functions, initializers, accessors, closures, and function types
[x] Function type substitution and canonicalization
[x] AST serialization and printing support
[x] Type checking of throws statements against the specified thrown type of functions/initializers/accessors
[x] Type checking of closures with specified thrown type
[x] Effects checking
[x] Access control checking for thrown type
[x] SIL type lowering and SIL generation
[x] Subtyping relationships involving typed throws
[ ] Override relationships involving typed throws
[x] Witness checking involving typed throws
[x] Associated type inference from typed throws
[x] IR generation
[x] SIL generation for generic thrown errors
[x] SIL generation for thunks that convert generic thrown error types
[x] Name mangling for typed throws
[x] Runtime type metadata and dynamic casting support for functions with typed throws
[ ] async let with typed throws
[ ] Opaque thrown error types
[ ] Closure thrown error type inference

https://github.com/apple/swift-syntax/pull/2219
@swift-ci please smoke test

https://github.com/apple/swift-syntax/pull/2219
@swift-ci please smoke test

https://github.com/apple/swift-syntax/pull/2219
@swift-ci please smoke test

@swift-ci please build toolchain

Note: I'm looking to get this building cleanly and then merging it, since everything is behind an experimental flag and the next part is a major refactoring of the effects checker.

(Note: toolchain builds aren't useful, and were kicked off with the wrong settings. Those failures are meaningless)

Effects checking mostly implemented in https://github.com/apple/swift/pull/68898 and https://github.com/apple/swift/pull/68976

Witness checking and associated type inference was implemented in https://github.com/apple/swift/pull/69087

Subtyping implemented via https://github.com/apple/swift/pull/68995

Basic IR generation is in https://github.com/apple/swift/pull/68833

Improving effects checking in https://github.com/apple/swift/pull/69198

Infer Error conformance when needed in https://github.com/apple/swift/pull/69181

Introduce upcoming feature FullTypedThrows for inferring thrown type from a throw statement in https://github.com/apple/swift/pull/69225

Name mangling is coming in via https://github.com/apple/swift/pull/69471

SIL generation for generic thrown errors is coming in via https://github.com/apple/swift/pull/69430

Name mangling and runtime type metadata are in https://github.com/apple/swift/pull/69493

SIL generation for generic typed throws is working now, with https://github.com/apple/swift/pull/69767 being the last of the series of PRs.

Fun in the standard library: https://github.com/apple/swift/pull/69771

Yet more SILGen thunking fun: https://github.com/apple/swift/pull/69791

Overrides: https://github.com/apple/swift/pull/69839

Silly me, overrides are going to land as https://github.com/apple/swift/pull/69922, but the code is done


Indentation is off inside a macro

-        Annotatable::Item(it) => vec![
+        Annotatable::Item(it) => {
+            vec![
             Annotatable::Item(P(Item {
                 attrs: it.attrs.clone(),
                 ..(*quote_item!(cx, enum Foo2 { Bar2, Baz2 }).unwrap()).clone()
             })),
             Annotatable::Item(quote_item!(cx, enum Foo3 { Bar }).unwrap()),
             Annotatable::Item(quote_item!(cx, #[cfg(any())] fn foo2() {}).unwrap()),
-        ],
+        ]
+        }

https://github.com/rust-lang/rust/pull/35850/files#r75626143

Note that the closing ] is also indented wrong, so this could be a symptom of a more general problem.

It seems like it would be a bug in the macro code, where we are not indenting when we start the list of arguments and then continue with that 'off by 1' indent when we finish off the macro (the ] line). The } of the match arm is indented correctly and so is the start of the macro, so I expect that the match arm formatting is OK here.

With RFC style and the latest master, we now get
        Annotatable::Item(it) => {
            vec![
                Annotatable::Item(P(Item {
                    attrs: it.attrs.clone(),
                    ..(*quote_item!(cx, enum Foo2 { Bar2, Baz2 }).unwrap())
                          .clone()
                })),
                Annotatable::Item(quote_item!(cx, enum Foo3 { Bar }).unwrap()),
                Annotatable::Item(quote_item!(cx, #[cfg(any())] fn foo2() {}).unwrap()),
            ]
        }


Multiple hightlight

If I type in search input two words, nothing happens. What I need to do for hightlight two words?!

text-highlight component accepts Array<string> for queries prop. You can try splitting your search input.

Work great! Thnk!


Aim of Statement.clone() method and DB.clone

Your Question
I look into chainable_api.go to learn about chainable method like what happened when I call db.Where(some-arugments..).
Source code here:
func (db *DB) Where(query interface{}, args ...interface{}) (tx *DB) {
	tx = db.getInstance()
	if conds := tx.Statement.BuildCondition(query, args...); len(conds) > 0 {
		tx.Statement.AddClause(clause.Where{Exprs: conds})
	}
	return
}

I know tx = db.getInstance() makes sure thread safe, but I'm confused to the clone() method in implement of db.getInstance()
func (db *DB) getInstance() *DB {
	if db.clone > 0 {
		tx := &DB{Config: db.Config}
		if db.clone == 1 {
			// clone with new statement
			tx.Statement = &Statement{
				DB:       tx,
				ConnPool: db.Statement.ConnPool,
				Context:  db.Statement.Context,
				Clauses:  map[string]clause.Clause{},
				Vars:     make([]interface{}, 0, 8),
			}
		} else {
			// with clone statement
			tx.Statement = db.Statement.clone()
			tx.Statement.DB = tx
		}
		return tx
	}

	return db
}

I'm confused to why there is a clone in a DB,  and what a clone method do in short?
The document you expected this should be explained

something about DB.clone,method clone() and the Statement.

Expected answer

the aim of clone in DB struct
In getInstance() method code, I find clone is used as a condition.  So I guess clone constrict the db cloned by a transaction.

type DB struct {
	*Config
	Error        error
	RowsAffected int64
	Statement    *Statement
	clone        int
}

Why there is a clone() method

refer https://gorm.io/docs/method_chaining.html https://gorm.io/docs/hooks.html#Modify-current-operation
also checkout *gorm.DB's Session, getInstance methods


New PR to test SignCLA at 2017-10-04 14:45:55.925839585 -0700 PDT m=+6.036086796

Body of PR

Thanks for your pull request.  It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
:memo: Please visit https://cla.developers.google.com/ to sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll verify.  Thanks.

If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address.  Check your existing CLA data and verify that your email is set on your git commits.
If your company signed a CLA, they designated a Point of Contact who decides which employees are authorized to participate. You may need to contact the Point of Contact for your company and ask to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the project maintainer to go/cla#troubleshoot.
In order to pass this check, please resolve this problem and have the pull request author add another comment and the bot will run again.


Add HelloWorld example

Can you provide a simple HelloWorld type example for someone to use/follow?  A simple MySQL or webserver would suffice.

Thanks for your ticket, that's a great idea. We'll add marathon example files to the repo in a future release.
For now, you can use some of the examples from the marathon project: https://github.com/mesosphere/marathon/tree/master/examples

Perhaps we create a single shell script that queries consul for the marathon endpoints in each datacenter and post a marathon config!

Something like this ...
$ cat hello-world.json
{
"container": {
"type": "DOCKER",
"docker": {
"network": "BRIDGE",
"image": "keithchambers/docker-hello-world",
"portMappings": [ { "containerPort": 80,"protocol": "tcp"} ]
}
},
"id": "hello-world",
"instances": 2,
"cpus": 0.1,
"mem": 128
}
curl -X POST -H "Content-Type: application/json" http://<IP_ADDRESS>:8080/v2/apps<EMAIL_ADDRESS>

Add some comments to the beginning and it looks good.

Close? We have a hello world example now


pr build test

Can one of the admins verify this patch?

retest this please

retest this please

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Aries-JPA-pr/1/


Update styling docs and add example on theme switch detection

Building on #1267 and iterating on the docs, re-organizing them into Layout and Theme sections.
Also adding sample code on how to detect theme changes in JavaScript.
Related is #1338 which would further improve this documentation by generating color-reference.md from source, somehow.

@aleksfront WDYT?

Thanks for great changes and additions! I will look now on how to provide an easy theme switch indicator for emotion case.

My pleasure! Thanks for the pull. 😄


Add support for generating noise images with an offset

Problem
OpenSimplexNoise.get_image() and NoiseTexture can only generate noise from coordinates in the range (0,0) to (image_width, image_height). The result is that these classes can't be used to generate texture data across a larger space. My use case is that I want to generate noise data at arbitrary coordinates so that I can use the data for creating a procedural world, and passing to shaders.
Workaround
It is possible to achieve the desired outcome in gdscript. I can generate an image by calling OpenSimplexNoise.get_noise_2d() for each coordinate, and generate a texture from that image. However, doing this in gdscript is very slow.
Solution
In this PR, I've updated OpenSimplexNoise.get_image() and NoiseTexture to accept a coordinate offset, so that they can generate noise images from anywhere in the noise space. In my tests, using the updated method is about an order of magnitude faster than using the gdscript method mentioned above.
Rationale

This enhancement enables the generation of large amounts of noise data.
This enhancement is about 10x faster than doing the same thing in gdscript.
This enhancement does not break compatibility.
This enhancement is small and easily understood.

Demo
Create a Node2D and attach the following script.
The default behavior is to generate a grid of sprites containing noise data using gdscript. This is the slow method which is compatible Godot 3.3.
Running generate_noise_texture_grid() or generate_image_texture_grid() demonstrate the new, faster functionality provided by this PR.
`extends Node2D
var grid_size = 4
var texture_size = 512
var noise = OpenSimplexNoise.new()
func _ready():
generate_manually_offset_grid()
#generate_noise_texture_grid()
#generate_image_texture_grid()
func generate_manually_offset_grid():
"""Generate noise textures by manually calculating offset in gdscript."""
for grid_y in range(grid_size):
for grid_x in range(grid_size):
var pos = Vector2(grid_x, grid_y) * texture_size
var data := PoolByteArray()
data.resize(texture_size * texture_size)
for y in range(texture_size):
for x in range(texture_size):
var n = noise.get_noise_2d(x + pos.x, y + pos.y) * 0.5 + 0.5
data[y * texture_size + x] = n * 256
var image := Image.new()
image.create_from_data(texture_size, texture_size, false, Image.FORMAT_L8, data)
var texture := ImageTexture.new()
texture.create_from_image(image, 0)
var sprite := Sprite.new()
sprite.texture = texture
sprite.position = pos
add_child(sprite)
func generate_noise_texture_grid():
"""Generate NoiseTextures using new offset feature."""
for y in range(grid_size):
for x in range(grid_size):
var noise_texture := NoiseTexture.new()
noise_texture.noise = noise
noise_texture.width = texture_size
noise_texture.height = texture_size
var pos = Vector2(texture_size * x, texture_size * y)
noise_texture.noise_offset = pos
var sprite = Sprite.new()
sprite.position = pos
sprite.texture = noise_texture
add_child(sprite)
func generate_image_texture_grid():
"""Generate noise images using new offset feature and create texture manually."""
for y in range(grid_size):
for x in range(grid_size):
var sprite = Sprite.new()
var pos = Vector2(texture_size * x, texture_size * y)
sprite.position = pos
var image
image = noise.get_image(texture_size, texture_size, pos.x, pos.y)
var tex = ImageTexture.new()
tex.create_from_image(image, 0)
sprite.texture = tex
add_child(sprite)`

I will see about adding documentation for the new parameter today.

This change would also have the side effect of fixing https://github.com/godotengine/godot/issues/47040

This has been tagged "breaks compat" but I don't believe it does break compatibility. The default behavior remains the same as before.

This change would also have the side effect of fixing #47040

It wouldn't fix #47040 per se, as the (0, 0) noise space pixel would be generated as before, and because the default behavior is still to generate a noise image which spans (0, 0) - (width, height). But this enhancement would give users more flexibility in working around #47040.

This change would also have the side effect of fixing #47040

It wouldn't fix #47040 per se, as the (0, 0) noise space pixel would be generated as before, and because the default behavior is still to generate a noise image which spans (0, 0) - (width, height). But this enhancement would give users more flexibility in working around #47040.

At the suggestion of @Xrayez I updated this PR to use Vector2 all the way through. This gives an effective way to work around #47040: pass non-integer offsets, for example (0.5, 0.5), and the noise map will not generate a value for (0, 0).

Looks great! Can you please squash your commits into one. We like to keep our git history very clean. After that, it should be ready to merge!

Looks great! Can you please squash your commits into one. We like to keep our git history very clean. After that, it should be ready to merge!

Done. Thank you for the link!

FYI, your local Git author details (see header of https://github.com/godotengine/godot/commit/f33800a9c8023843de271280a7482a5b7911e8e6.patch) don't seem to match the email registered in your GitHub account, which is why the commit doesn't appear as authored by "@radishes", so your GitHub account would not be properly credited as contributor once merged. It's not a problem technically for Git or GitHub, but if you want to claim this commit to your account, you can add this email as secondary email in your GitHub settings.

Thank you! I've added that email address as a secondary email to my Github account.

Thanks! And congrats for your first merged Godot contribution :tada:

This was label as a candidate to cherry-pick for 3.x, but there's an issue due to #30424 which was not cherry-picked as it breaks compatibility. So I'm not sure if adding this feature as is would make sense or if the x and y coordinates should also be swapped, but that potentially makes things even more confusing.

I implemented the noise offset changes in the 3.x branch for myself and noticed the swapped axes bug too. I left the bug alone and added the offsets as shown below.
The method I pasted below produces a good outcome because, despite the coordinate bug, it produces noise images which can be tiled together for a seamless view of the larger noise space. This satisfies my use cases, and probably most use cases; I'm not concerned about the unexpected orientation of the generated noise.
However, if a user is generating noise images this way, and comparing specific areas with the equivalent noise generated using OpenSimplexNoise.get_noise_2d(), they will notice the discrepancy between the two. But, since get_image() already causes this discrepancy, I don't see any harm in leaving the bug alone to maintain compatibility.
tl;dr: I recommend implementing it in 3.x as below, for the "principal of least surprise" reasons. This is compatible with expected outcomes considering #30424. If #30424 gets fixed, it will still work with the new noise offset feature. The noise images produced are continuous and tile-able in either case.
Ref<Image> OpenSimplexNoise::get_image(int p_width, int p_height, const Vector2 &p_noise_offset) const {
	PoolVector<uint8_t> data;
	data.resize(p_width * p_height);

	PoolVector<uint8_t>::Write wd8 = data.write();

	for (int i = 0; i < p_height; i++) {
		for (int j = 0; j < p_width; j++) {
			float v = get_noise_2d(float(j) + p_noise_offset.x, float(i) + p_noise_offset.y);
			v = v * 0.5 + 0.5; // Normalize [0..1]
			wd8[(i * p_width + j)] = uint8_t(CLAMP(v * 255.0, 0, 255));
		}
	}

	Ref<Image> image = memnew(Image(p_width, p_height, false, Image::FORMAT_L8, data));
	return image;
}

I think swapping the offset coordinates to match the bug is the least surprising outcome for users. The example below produces tile-able continuous noise. Maybe an explanatory comment would help?
float v = get_noise_2d(float(i) + p_noise_offset.y, float(j) + p_noise_offset.x);  // Axes swapped to maintain compatibility, per #30424.

In any case, #30424 is a clear bug to me which could've been cherry-picked as well, but I guess too many people might already rely on the wrongly swapped coordinates...

If there's going to be a 3.4, maybe that's a good time to break compatibility and fix the bug? Is that option on the table?

If there's going to be a 3.4, maybe that's a good time to break compatibility and fix the bug? Is that option on the table?

I personally think it would be worth it, as long as the change is documented of course. But it's up to Akien to decide.

I agree, I cherry-picked #30424 for 3.4.

We've had regressions in NoiseTexture due to major thread modernization backports in the past: #46907 (and many other regressions because of #45618), so I don't see a reason why such a minor bug fix cannot be cherry-picked...

That's not a very good argument. Those regressions have been fixed before the stable release, so there's no compat breakage in that specific instance. On the other hand, the now cherry-picked #30424 will break compat in a stable release. That's apples and oranges.

Cherry-picked for 3.4.


Refactor the Multipart parsing into a Sans-IO layer

This allows it to be used in async (ASGI) frameworks. It also
hopefully makes the code a little clearer to follow.
This removes the Content-Transfer-Encoding support as RFC7578
states it is deprecated and
Currently, no deployed implementations that send such bodies have
been discovered.

This requires the dataclasses backport, which I think is ok as
dataclasses are in the stdlib, and 3.6 has less than a year till EoL.

closes #1788
closes #875

Checklist:

[x] Add tests that demonstrate the correct behavior of the change. Tests should fail without the change.
[x] Add or update relevant docs, in the docs folder and in code.
[x] Add an entry in CHANGES.rst summarizing the change and linking to the issue.
[x] Add .. versionchanged:: entries in any relevant code docs.
[x] Run pre-commit hooks and fix any issues.
[x] Run pytest and tox, no tests failed.

Nice work, the code is easy for me to follow and well commented. Had a bunch of questions and ideas as I was reviewing.

Nice work, the code is easy for me to follow and well commented. Had a bunch of questions and ideas as I was reviewing.

Thanks!

Thanks!


Default listing for sonalyze jobs must show host

Now that I have multi-node data I can execute a bughunt:
SONAR_ROOT=~/sonar/data target/release/sonalyze jobs --zombie

This prints
job#      user              time       start?             end?                 cpu        mem gb     gpu        gpu mem   command
3025762> _zombie_3025762    0d18h25m   2023-08-03 11:35   2023-08-04 06:00      0/   0     0/   0     0/   0     1/   1   _unknown_
3843643  _zombie_3843643    0d18h25m   2023-08-03 11:35   2023-08-04 06:00      0/   0     0/   0     0/   0     1/   1   _unknown_

But where are those jobs?  Having looked at the logs, I know that they are on two different hosts, and neither one is the host I'm currently on.  It would be helpful for that data to be printed.
(Also observed: The start and end times are not that useful in practice.  The running time, along with the ">" and "<" markers, is usually enough information.  Also see #16.)

This and #16 are basically ready to land after major cleanup of the printing code, see branch print_revamp.
Main task remaining is one of syntax: is it cpu-avg (as in the printing code) or avg-cpu (as in the command line switches)?  Let's pick one.
Minor task: more testing, but everything looks good.
Bonus: Allow the printer to print to a random output stream, not just stdout.  That way we can implement good tests, for one thing.

Testing found a bug.  Never write tests.


Action can get stuck if rustdoc changes behavior from one Rust version to another

We've been struggling with [cargo-semver-checks-action erroring out] and blocking PR validations and release builds.
I think we've found a temporary workaround, but wanted you to be aware of the issue.
Please read the log at https://github.com/contentauth/c2pa-rs/actions/runs/3734139307/jobs/6335827121.
In this log, version 0.16.0 is the prior release for comparison and you'll notice that the cargo rustdoc task for that release fails with:
error: unclosed HTML tag `u8`
   --> sdk/src/assertion.rs:175:58
175 | /// for Json assertions the data is a Json string and Vec<u8> for
                                                             ^^^^

… which is a valid error in Rust 1.66. However, at the time we released our crate 0.16.0, we were still on Rust 1.65 where the above doc comment went unnoticed.
The problem is that (short of disabling the cargo-semver-checks-action, which is how we're now working around it), the previous build check can't pass and so the step fails.
Not sure how to work around this, but thought you should be aware of the issue.

Thanks for the detailed report! Especially appreciate you digging into the cause — it really makes it easier to come up with a fix.
It seems that it's possible to override the deny(warnings) from the command line by setting RUSTFLAGS=-Awarnings: https://users.rust-lang.org/t/suppress-warnings-from-the-cargo-command/10536/2
However, I'm hesitant to enable that by default since my understanding is that any change to RUSTFLAGS causes a full rebuild, which could be quite expensive. And making the RUSTFLAGS=-Awarnings command opt-in as a config option seems suboptimal too, since it should remain off almost all of the time — except when a new lint comes up like this.
I could perhaps make the action attempt to build the baseline normally first, and then retry with -Awarnings if the first attempt failed.
How does that sound? Is there a better option? Any downsides I might be missing?
Two other, minor things:

Re: disabling cargo-semver-checks, I think you'd only need to do that until your next version is released, right? After that, that version becomes the baseline, and the problem should go away. Please let me know if that doesn't end up being the case for any reason.
Based on user feedback, we're planning some significant upgrades to the GitHub Action in the near future, aiming to significantly improve performance by using a prebuilt binary and caching baseline files. Is that something you also see as important, or is there something else you'd rather have first? Would you be interested in being an early adopter of the new faster Action and giving us feedback on it?

Resolved by https://github.com/obi1kenobi/cargo-semver-checks/pull/357 and will be available with the next release.


somatic variant calling

Hi, I want to know if this tool can be used (or need some tweaking) to call somatic variants on pacbio-ccs data?
Thanks.

Hi - the tool is designed for germline variant calling. I am not knowledgeable regarding what issues may be presented by SMRT-based somatic variant calling.


Count characters rather than bytes

The limit suggested by Slack is referring to the number of characters, not the number of bytes which is returned from len() on a string. Converting to a rune slice is a quick way to get the correct number of characters in the message text.

LGTM, mind just rebasing against master? I made a mistake this morning when moving some personal branches around and had to fix master.


add autoscale, server version to mongodb

Description
added autoscale throughput scripts
updated mongodb to include server version property in account create
Checklist

[X] This pull request was tested on both of:

[ ] PowerShell 5.1 (Windows)
[X] PowerShell 6.x
[X] PowerShell 7.x (Latest PowerShell)

[X] Scripts do not contain static passwords or other secret tokens.
[X] All Azure resource identifiers which must be universally unique are guaranteed to be so.

#sign-off
@dbradish-microsoft this is ready to merge. Thanks!

@markjbrown , I am not an admin in this repo.  CCing @mikefrobbins who should be, I believe.


Fix typo: expire_at -> expires_at

Finished in 3 minutes 58.2 seconds (files took 8.93 seconds to load)
573 examples, 1 failure, 10 pending

@mod ping

@mod rebased


Breakpoint does not bind on Electron's main process with webpack

VSCode Version:

버전: 1.25.1
커밋: 1dfc5e557209371715f655691b1235b6b26a06be
날짜: 2018-07-11T15:43:53.668Z
Electron: 1.7.12
크롬: 58.0.3029.110
Node.js: 7.9.0
V8: 5.8.283.38
아키텍처: x64

OS Version:
Windows 10

Steps to Reproduce:

git clone https://github.com/kwonoj/vscode-node-async-import-webpack-repro
cd vscode-node-async-import-webpack-repro
npm install

Set breakpoint at https://github.com/kwonoj/vscode-node-async-import-webpack-repro/blob/57c4fb5e16adde9c4c05235d09cd6ee085ae9df9/src/main.ts#L4 , F5 to trigger debugger
: Breakpoint will not bind

uncomment line https://github.com/kwonoj/vscode-node-async-import-webpack-repro/blob/57c4fb5e16adde9c4c05235d09cd6ee085ae9df9/src/main.ts#L3 , F5 to trigger debugger
: debugger statement will hit breakpoint

Change webpack target https://github.com/kwonoj/vscode-node-async-import-webpack-repro/blob/master/webpack.config.js#L20 to target: 'node',, F5 to trigger debugger with breakpoint https://github.com/kwonoj/vscode-node-async-import-webpack-repro/blob/57c4fb5e16adde9c4c05235d09cd6ee085ae9df9/src/main.ts#L4
: Breakpoint will bind

I was not able to fully understand behavior around above, while sourcemap is generated for both target (node, electron-main) it is only bound on node target, but while debugger statement still bound regardless of target configuration with proper mapping. Created under bug, couldn't find duplicated issues by myself.

This works for me. If it's still an issue for you in the latest version, please set "trace": true, try again with the breakpoint, and upload the log here.

@roblourens I just tried with latest vs code, still observe issue:

Breakpoint is not binded. Attached trace log below.
debugadapter.txt

Debugged and filed an upstream issue https://github.com/webpack/webpack/issues/8032

Thanks for verifying!


Upgrade Viv to 0.8.3

This PR mainly upgrades Viv to allow for the transparentColor prop and some small fixes.
In addition, I noticed that the debug functionality wasn't working for non-api.js datasets (i.e from view configs) so I added that as well.
Also, I re-aligned our controller layout - before:

after:

Finally, I noticed that modelMatrix is actually not in our layer schema even though it has been a part of it for a while.  @keller-mark I don't think it's an issue to store this information in two different places since in the future (Nils has mentioned) allowing users to rotate images, but if it's multimodal, we probably want some sort of initialization value which can still come from the options part of raster.json, especially if all of the layers are not all initially shown (i.e you need to use the Add Image button).  I also like the simplicity of having it as part of the raster.json.  Open to other thoughts.
To test this out, you can try this url

The interface feels like borderline https://twitter.com/stelian/status/720913927639560194 but I also can't think of any better alternative at the moment (a color picker feels wrong because this value needs to be exact, right?). What do the empty options do (the ones before 0)?
And I am guessing the interface is necessary due to HuBMAP datasets which may have unpredictable transparency values?
And I agree that it should be fine to put an initial model matrix in raster.json options - in my mind this is analogous to specifying the initial image layers in the options or in the file itself.

The interface feels like borderline https://twitter.com/stelian/status/720913927639560194 but I also can't think of any better alternative at the moment (a color picker feels wrong because this value needs to be exact, right?). What do the empty options do (the ones before 0)?
And I am guessing the interface is necessary due to HuBMAP datasets which may have unpredictable transparency values?
And I agree that it should be fine to put an initial model matrix in raster.json options - in my mind this is analogous to specifying the initial image layers in the options or in the file itself.

@keller-mark I thought about a color picker as well and yes, that was basically the reason I avoided it.  I think you only ever really want [0,0,0] (at the moment) and it does need to be exact.
The interface is necessary less because of different values and more because of the need to turn it on and off, at which point allowing the customizability seemed natural.
@ngehlenborg I think you asked specifically to be able to set these values, but do you have an idea for a better UI?

@keller-mark I thought about a color picker as well and yes, that was basically the reason I avoided it.  I think you only ever really want [0,0,0] (at the moment) and it does need to be exact.
The interface is necessary less because of different values and more because of the need to turn it on and off, at which point allowing the customizability seemed natural.
@ngehlenborg I think you asked specifically to be able to set these values, but do you have an idea for a better UI?

Updated UI to float left with no padding on bottom. as per conversation.

Updated UI to float left with no padding on bottom. as per conversation.


Convert Google Prettify.js Links to CDN Links

Convert Google code-prettify links to use CDN and the new preferred
method of loading: run_prettify.js which no longer requires separate
includes of prettify.css
Addresses issue #115

Yes. Here a link to a jsfiddle which simply includes run_prettify.js without the CSS.

Looks like I messed up my PR. The only intended commit for this PR is the first commit on March 14 relating to the addition of the CDN links in the examples.

@kaptainkommie did you want to cancel and re-open this PR with the cherry picked changes? Or go ahead with it as it is?

According to repo info rawgit.com was turned off October 2019.
It's possible to use this CDN now<EMAIL_ADDRESS>


Example to Display Previous/Next Items

Hello,
Could you please provide documentation on how to properly set up the CoverFlowFiew to display a partial view of the previous/next item and make it seems to transition directly into that item?
When setting this up based on your example, currently, only 1 item is presented each swipe; not like visually represented in this photo...

@zwilkin hm.
How it's possible?
Did you run my sample project?

It would be great to see small reproduction sample here :)

As for your question:
here is small doc https://github.com/AndreiMisiukevich/CardView/blob/master/docs/CoverFlowView.md
it must be your center view occupy all space.. try to add margins/paddings maybe.
Or just send me your sample :)

I figured out my issue. I was attempting to adjust the size of the internal frame which visually was working, however I forgot to set a padding on the internal ContentView to allow the previous/next items to "bleed" onto the page.
Amazing library, amazing support, great work man keep it up!
Please feel free to close this thread.
Zach Wilkin
<EMAIL_ADDRESS>| www.goeis.net
(352) 236-4500 Office
(610) 709-4292 Cell
(866) 861-3294 Fax
Executive Information Services, Inc.
1396 NE 20th Avenue, Suite 100
Ocala, FL 34470

From: Andrei<EMAIL_ADDRESS>Sent: Tuesday, February 26, 2019 6:56 PM
To: AndreiMisiukevich/CardView
Cc: Zach; Mention
Subject: Re: [AndreiMisiukevich/CardView] Example to Display Previous/Next Items (#171)
As for your question:
here is small doc https://github.com/AndreiMisiukevich/CardView/blob/master/docs/CoverFlowView.md
it must be your center view occupy all space.. try to add margins/paddings maybe.
Or just send me your sample :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/AndreiMisiukevich/CardView/issues/171#issuecomment-467664963, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AJAE2bsn_J3tZx0fL6K-0o-djwVSx6I1ks5vRcm5gaJpZM4bTX6H.

@zwilkin i'm glad to hear it :)
Thx


Undefined is not an object evaluating 'styles[selector]')

This error happens in my home file that is located under screens folder and it has been added to the tailwind.config.js, also it was working before I've added tab navigation to my app.tsx.
Anyone can help me? I like a lot this package but I think that for some reason the provider cannot pass the props to my component

Hi @Pnlvfx, are you able to push your code to a public repo so I can reproduce the error?

Hi thanks for creating this issue, unfortunately this issue does not have enough information for me to troubleshoot.
I'm going to close this issue for now, but if you reply with more information I'll happily reopen it.

Hi,
I had the same issue and I fixed it just with running npm run start --reset-cache
Best regards,
Jeremie


Question about resource attribute

Since the help documentation is a bit light I thought I'd ask here. In New-xDSCResourceProperty the Attribute property is required. I understand the Key and Required values. But am not sure what Read or Write is referring to. The resources I've test built seem to work just fine when using Write. I assumed this meant "writing" to the something on the computer. But that's just an assumption on my part. I'd appreciate any clarification on the Read and Write parameter values for Attribute.

I found this when wanting the same clarification myself:
The [write] qualifier indicates that this property is optional when using the custom resource in a configuration script. The [read] qualifier indicates that a property cannot be set by a configuration, and is for reporting purposes only.`
Source: https://docs.microsoft.com/en-us/powershell/dsc/authoringresourcemof

Thanks. I guess I wasn't that far off in my assumption.

No worries Jeff. Glad to repay a simple link, after the many years I've spent learning from your content! :)


Adding left and right transition effects in the "ABOUT" section

Adding transition effects to give the website a more dynamic user experience

elaborate on what changes you are proposing

elaborate on what changes you are proposing

The about section contains three divs. Adding translation in each div such that first div comes from left with  slight delay in the picture ,second div will come from right. All this will happen on scrolling,Also the coloured heading of each div will be displayed  with a slight typing and glowing effect.

assigned


Are there any breaking changes log

Version
4.1.0-release
Steps to reproduce
We are going to upgrade echarts from 4.1 to 4.5 or higher, are there any breaking changes log that can guide us to evaluate the risk of the upgrading operation? Thanks for help.
What is expected?
a breaking change log
What is actually happening?
breaking change log not found

Upgrading from 4.1.0 to 4.5 or other higher versions with 4.x should be compatible and you can upgrade without too much consideration.

Ok thanks, I will try to upgrade to 4.6 the newest version.


Standardize Airflow Variable names

Description

Presently we have a discrepancy with Airflow Variable names, as most Variables are referenced using upper-case but some are referenced with lower-case. This can make it confusing for users and operators to know which case to use for a given Variable. I believe this discrepancy arises because the Variable management via environment variables allows you to reference AIRFLOW_VAR_FOO as either Variable.get("FOO") or Varuable.get("foo"). Here's an example:
$ j shell
docker-compose --file=docker-compose.yml --file=docker-compose.override.yml up -d
Creating network "openverse-catalog_default" with the default driver
Creating openverse-catalog_s3_1       ... done
Creating openverse-catalog_postgres_1   ... done
Creating openverse-catalog_load_to_s3_1 ... done
Creating openverse-catalog_webserver_1  ... done
docker-compose --file=docker-compose.yml --file=docker-compose.override.yml exec webserver /bin/bash
airflow@79395672cbfd:~$ airflow variables get API_KEY_FREESOUND
XXXyyyZZZ
airflow@79395672cbfd:~$ airflow variables get api_key_freesound
XXXyyyZZZ

This will create trouble for us down the line, since variables added in the UI must match the casing with which they're referenced in the code. I tested this by adding the Variable foo_bar in the UI:
airflow@79395672cbfd:~$ airflow variables get foo_bar
this is a sample value
airflow@79395672cbfd:~$ airflow variables get FOO_BAR
Variable FOO_BAR does not exist

We have only a few variables that are referenced using the lower-case versions:
$ rg -Ue "Variable.get\(\s*\"[a-z_]+\""
openverse_catalog/dags/common/slack.py
228:    environment = Variable.get("environment", default_var="dev")
249:    environment = Variable.get("environment", default_var="dev")
250:    force_message = Variable.get(
251:        "slack_message_override", default_var=False, deserialize_json=True

openverse_catalog/dags/providers/provider_api_scripts/provider_data_ingester.py
63:        self.limit = Variable.get(
64:            "ingestion_limit", deserialize_json=True, default_var=0

I think it would be best to standardize around all upper case Variable values, since that's the bulk of our existing references:
$ rg -U --count -e "Variable.get\(\s*\"[A-Z_]+\""
openverse_catalog/dags/providers/provider_api_scripts/jamendo.py:1
openverse_catalog/dags/providers/provider_api_scripts/freesound.py:1
openverse_catalog/dags/providers/provider_api_scripts/walters.py:1
openverse_catalog/dags/providers/provider_api_scripts/flickr.py:1
openverse_catalog/dags/providers/provider_api_scripts/brooklyn_museum.py:1
openverse_catalog/dags/providers/provider_api_scripts/nypl.py:1
openverse_catalog/dags/providers/provider_api_scripts/thingiverse.py:1
openverse_catalog/dags/providers/provider_api_scripts/smithsonian.py:1
openverse_catalog/dags/providers/provider_api_scripts/europeana.py:1
openverse_catalog/dags/maintenance/pr_review_reminders/pr_review_reminders_dag.py:3

We'll also need to be sure to update any references to the lower case Variables that appear within documentation.
Resolution

[ ] 🙋 I would be interested in resolving this bug.

Hi, is it still open? I would be interested in resolving this bug.

Hi @davcortez! Thanks for submitting a PR for this 😄 I'll assign this to you nonetheless so it's clear, and take a look at the PR later today 🙂


definition of relational column and relation causes duplicate params when updating

Issue type:
[ ] question
[x] bug report
[ ] feature request
[ ] documentation issue
Database system/driver:
[ ] cordova
[ ] mongodb
[ ] mssql
[x] mysql / mariadb
[ ] oracle
[ ] postgres
[ ] sqlite
[ ] sqljs
[ ] react-native
[ ] expo
TypeORM version:
[ ] latest
[x] @next
[ ] 0.x.x (or put your version here)
Steps to reproduce or a small repository showing the problem:
@Entity()
class Parent {
  @PrimaryGeneratedColumn()
  id: number;

  @OneToMan(type => Child, Child => Child.parent)
  children: Child[]
}

@Entity()
class Child {

  @PrimaryGeneratedColumn()
  id: number;

  @Column({
    name: "parent_id"
    type: "int"
  })
  parentId: number;

  @ManyToOne(type => Parent, Parent => Parent.children)
  @JoinColumn({name: "parent_id"})
  parent: Parent;
}

const entityManager = typeorm.getConnection().getEntityManager();

const aParent = new Parent();
entityManager.save(aParent);

const aChild = new Child();
aChild.parentId = aParent.id;
aChild.parent = aParent;
entityManager.save(aChild);

couldn't reproduce

Issue was probably caused by mismatched definitions of relational key and related object primary key

Also note: properties don't have to be mismatched, but merely defined in relational key and nested related object primary key


python311Packages.aiosql: 9.2 -> 9.3

Diff: https://github.com/nackjicholson/aiosql/compare/refs/tags/9.2...9.3
Changelog: https://github.com/nackjicholson/aiosql/releases/tag/9.3
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 283840 run on x86_64-linux 1

2 packages failed to build:

oterm
oterm.dist

6 packages built:

python311Packages.aiosql
python311Packages.aiosql.dist
python311Packages.aiosql.doc
python312Packages.aiosql
python312Packages.aiosql.dist
python312Packages.aiosql.doc

oterm is already broken.


Windows 10 c++, bazel build successfully， where is the .lib file？

I have build both TensorFlow1.11 and 1.10 's libtensorflow_cc.so file successfully, but where is the .lib file for Visual Studio ?

Hi Did you get the answer?
I have built tensorflow for c++ with bazel on windows and need .lib and .dll. Can you share what you did to include tensorflow in visual studio project?


Codacy tech debt

This PR fixes some issues that Codacy found that relate to coding practices that could cause confusion. Many of the changes are to address using default package protected scoping instead of explicit scoping rules. The README file was also updated to include information on working screen modes.

Codecov Report

Merging #24 into master will decrease coverage by 0.08%.
The diff coverage is 58.33%.

@@             Coverage Diff              @@
##             master      #24      +/-   ##
============================================
- Coverage     67.75%   67.66%   -0.09%
  Complexity     1025     1025
============================================
  Files            43       43
  Lines          4853     4856       +3
  Branches        487      487
============================================
- Hits           3288     3286       -2
- Misses         1474     1479       +5
  Partials         91       91

Impacted Files
Coverage Δ
Complexity Δ

...a/craigthomas/yacoco3e/datatypes/MemoryResult.java
100% <ø> (ø)
5 <0> (ø)
:arrow_down:

...ava/ca/craigthomas/yacoco3e/components/Memory.java
71.29% <ø> (ø)
33 <0> (ø)
:arrow_down:

...n/java/ca/craigthomas/yacoco3e/components/CPU.java
95.61% <ø> (-0.01%)
514 <0> (ø)

...a/ca/craigthomas/yacoco3e/components/Keyboard.java
55.03% <ø> (-0.04%)
65 <0> (ø)

...ca/craigthomas/yacoco3e/datatypes/RegisterSet.java
100% <ø> (ø)
22 <0> (ø)
:arrow_down:

...listeners/FlushCassetteMenuItemActionListener.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...a/ca/craigthomas/yacoco3e/components/Emulator.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...ava/ca/craigthomas/yacoco3e/components/Screen.java
38.98% <100%> (+0.38%)
5 <0> (ø)
:arrow_down:

...ca/craigthomas/yacoco3e/components/DiskSector.java
50.32% <100%> (-1.97%)
23 <0> (ø)

.../craigthomas/yacoco3e/datatypes/SG4ScreenMode.java
17.85% <100%> (ø)
1 <1> (ø)
:arrow_down:

... and 1 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 719648a...7d35872. Read the comment docs.


Drop the Slack inviter app and just use an invite link

At some point since the website launched Slack has added the ability to create invite links that don't expire.
Given that Heroku is going to charge soon, and that we can now create a permanent invite link, I propose that we:

Delete the Heroku inviter app
Update the "Join our Slack" link to use a permanent invite link instead.

You can read about how to create a permanent link in the Slack docs, but I created one that's ready to go if anyone wants to take this on. I can do a PR after work if there's interest:
https://join.slack.com/t/devedmonton/shared_invite/zt-1g5tyn7c1-JaTgK4Mf7HvO9LAgaXvt7g

I have no real skin in the game, but as an infrastructure guy I'm always happy to see "decommission the thing we don't need" proposed!
Technical nit: probably should do 2 before 1, or some new member may get unlucky in their attempt to join.

Good point @jon-at-rithmik. I've tested the invite link myself, but a few others might want to do the same before we switch over to it...
https://join.slack.com/t/devedmonton/shared_invite/zt-1g5tyn7c1-JaTgK4Mf7HvO9LAgaXvt7g

I tried signing up using an alternate email in an incognito window

Hmm... annoying it doesn't tell you anymore than that! I assume that appears after you've entered your email and submitted the form?

Another issue I see with this is that is says that link is only valid for 100 invites? What happens after the 100?

Yes signed in using oauth @MarkBennett

Yes signed in using oauth @MarkBennett

Hmm, I'm at work but will look into this when I have a moment.

Finally had some time to circle back on this... I deactivated the old link completely and made a new one that's set to never expire.
https://join.slack.com/t/devedmonton/shared_invite/zt-1h0s5j0g4-ntARRvWGapJcnckM34jdZw
I was then able to use it to join using my Google account.
@acenasir, can you try and see if this one works for you?

Worked Smoothly this time around. Thanks @MarkBennett


WIP types

Closes #10
Support 4 types for reading:

INT
DOUBLE
BOOL
VARCHAR

Support as many types as is practical for writing:

INT
DOUBLE
BOOL
VARCHAR

Closed in favour of https://github.com/evidence-dev/duckdb_gsheets/pull/41


Improve the content for Java and JavaScript SDK

Improve the content for Java and JavaScript SDK to cover the user guide for both Metrics And Traces

Hi Min, could you address the following changes for your PR:

./docs/getting-started/js-sdk/metric-manual-instr.mdx - has the wrong path in the front-matter

./docs/getting-started/js-sdk/trace-manual-instr.mdx - has the wrong path in the front-matter

./docs/getting-started/java-auto-instrumentation-agent.mdx - you imported a Link component but it was never used in the rest of the document

./docs/getting-started/js-sdk - Incorrect title for "Sample Code with Java SDK"

Thanks Wil, I updated your comments #1, #2 and #4. I plan to rewrite the content for "java-auto-instrumentation-agent.mdx" and rename it to aws-xray.mdx. It is still WIP. Thanks.


Ensure Backend has issues with recently destroyed infrastructure

Hello!
ISSUE: Ensure backend sometimes fails to create the storage account
YML setup:
trigger: none
pr: none

pool:
  vmImage: 'ubuntu-latest'

Replication:
I am using your Auzre terraform pipeline module similiar to the below.
While development of this code is ongoing, i see myself manually taking down the Resource group via the Azure UI, and immediately redeploying the pipeline that contains the below snippet.. I think this is the cause of my issue...usually if i let the Resource group stay dead for awhile, i do not have this issue.  Obviously low priority as i have a workaround (ie patience)
    - task: TerraformCLI@0
      inputs:
        command: 'init'
        workingDirectory: '$(System.DefaultWorkingDirectory)/infra/dev'
        backendType: 'azurerm'
        backendServiceArm: '$(DisbursementsSubscriptionId)'
        ensureBackend: true
        backendAzureRmResourceGroupName: 'tfrepubsim'
        backendAzureRmResourceGroupLocation: '$(Location)'
        backendAzureRmStorageAccountName: 'tfrepubsim'
        backendAzureRmContainerName: 'tfrepubsim'
        backendAzureRmKey: 'dev.terraform.tfstate'
        allowTelemetryCollection: true
      displayName: "Terraform Init"

Occasionally (for reasons unknown) i get this during the above tf init. It will succesfully build the Resource group for me, but fails to build the Storage Account.  Usually, letting the Resource Group stay dead for 10 minutes before i redeploy a pipeline solves the issue.
Starting: Terraform Init
==============================================================================
Task         : Terraform CLI
Description  : Execute terraform cli commands
Version      : 0.6.13
Author       : Charles Zipp
Help         :
==============================================================================
/opt/hostedtoolcache/terraform/0.14.7/x64/terraform version
Terraform v0.14.7

/usr/bin/az login --service-principal -t *** -u *** -p ***
[
  {
    "cloudName": "AzureCloud",
    "homeTenantId": "***",
    "id": [redacted],
    "isDefault": true,
    "managedByTenants": [],
    "name": "[redacted]",
    "state": "Enabled",
    "tenantId": "***",
    "user": {
      "name": "***",
      "type": "servicePrincipal"
    }
  }
]

/usr/bin/az account set -s [redacted]

/usr/bin/az group create --name dev-ids-repub-sim-rg --location eastus2
{
  "id": "/subscriptions/[redacted]/resourceGroups/dev-ids-repub-sim-rg",
  "location": "eastus2",
  "managedBy": null,
  "name": "dev-ids-repub-sim-rg",
  "properties": {
    "provisioningState": "Succeeded"
  },
  "tags": null,
  "type": "Microsoft.Resources/resourceGroups"
}

/usr/bin/az storage account show --name devidsrepubsimsa --resource-group dev-ids-repub-sim-rg
ERROR: (StorageAccountNotFound) The storage account devidsrepubsimsa was not found.

##[error]Error: ERROR: (StorageAccountNotFound) The storage account devidsrepubsimsa was not found.

##[error]Error: ERROR: (StorageAccountNotFound) The storage account devidsrepubsimsa was not found.

##[error]Error: ERROR: (StorageAccountNotFound) The storage account devidsrepubsimsa was not found.

Finishing: Terraform Init

@amoore-incomm I believe the reason you are seeing unexpected behavior has to do with what the azure cli reports when the resource group and its resources are being removed. As you are aware, behavior is async so therefore, those resources probably go into a "deleting" state until the operation has finished. It would appear that while they are in this state, az storage account show returns a different error message than we typically expect. The TerraformCLI task expects a very specific error message to be returned in order to determine it needs to create the storage account. This error doesnt match up to what it expects.
We would first need to verify if the storage account with the same name could even be created while the existing one is being deleted. My suspicion is that this would fail if performed normally for the az cli but, would need to be tested to be sure. If it does fail, then I dont believe there is much we could do here outside of reporting this failed because one with the same name is being deleted.
However, if this is allowed, then what we would need to do is to add this error to the condition that determines if the task should create the storage account. This should be simple change to only a few lines. A new test case would also need to be added to verify the behavior under this condition. Existing test case is here and could be used as reference. The new scenario would probably name something like "init with backend azurerm ensured and storage account is being deleted".
Let me know your thoughts @amoore-incomm

Deprioritizing for the time being as this appears to be isolated and have simple work around of delaying time to account for async nature of ARM. If there additional interest or more information added, prioritization can be revisited in the future.


CPP/taskcpp/1_towerofhanoi.cpp

write a recursive function of tower of hanoi.
NOTE:- Screen shot of the code and output is required

Can you assign this to me , i can solve this by showing the steps also


asiana21 DOCSUP-194

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
Changelog category (leave one):

New Feature
Bug Fix
Improvement
Performance Improvement
Backward Incompatible Change
Build/Testing/Packaging Improvement
Documentation (changelog entry is not required)
Other
Non-significant (changelog entry is not required)

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
...
Detailed description / Documentation draft:
...
By adding documentation, you'll allow users to try your new feature immediately, not when someone else will have time to document it later. Documentation is necessary for all features that affect user experience in any way. You can add brief documentation draft above, or add documentation right into your patch as Markdown files in docs folder.
If you are doing this for the first time, it's recommended to read the lightweight Contributing to ClickHouse Documentation guide first.

Did you see https://github.com/ClickHouse/ClickHouse/blob/41e3bf55180dc735dd1b7ad202501ae109bcad45/dbms/src/IO/parseDateTimeBestEffort.h ? Does your description correspond to the description in the header or you just tried to guess formats from test?

It looks that we need just say that function parses ISO 8601 and list non-standard formats.
For example it supports 9 or 10 digit unixtimestamp but only as a string
clickhouse.ru-central1.internal :) SELECT parseDateTimeBestEffort(1284101485)

SELECT parseDateTimeBestEffort(1284101485)

Received exception from server (version 20.2.1):
Code: 43. DB::Exception: Received from localhost:9000. DB::Exception: Illegal type UInt32 of first argument of function parseDateTimeBestEffort.

0 rows in set. Elapsed: 0.001 sec.

clickhouse.ru-central1.internal :) SELECT parseDateTimeBestEffort(toString(1284101485))

SELECT parseDateTimeBestEffort(toString(1284101485))

┌─parseDateTimeBestEffort(toString(1284101485))─┐
│                           2013-08-20 10:13:29 │
└───────────────────────────────────────────────┘

1 rows in set. Elapsed: 0.001 sec.

It parses 14 digit string with no delimiters as a DateTime
SELECT parseDateTimeBestEffort('20200227095300')

┌─parseDateTimeBestEffort('20200227095300')─┐
│                       2020-02-27 09:53:00 │
└───────────────────────────────────────────┘

Other formats we should describe only if they are not the part of 8601. Should we separatedly mension RFC 1123 (https://tools.ietf.org/html/rfc822#section-5) ?
Does the functions parses the native ClickHouse time format YYYY-MM-DD HH:MM:SS ?


[SPARK-25299] Driver lifecycle api

Introduce driver shuffle lifecycle APIs

tagging @mccheah and @ifilonenko for initial review.
FYI - I searched through core spark code, but I couldn't figure out when and how the application shuffle files get removed in the case that uses YARN External Shuffle Service in cluster mode (since deleteFilesOnStop in the DiskBlockManager is false in the case of YARN ESS). The applicationRemoved() and executorRemoved() methods in ExternalShuffleBlockHandler seem only to be used in non-cluster modes. Ideally whatever codepath that is would go under the DefaultShuffleDriverComponents.cleanupApplicaiton() method

The applicationRemoved() and executorRemoved() methods in ExternalShuffleBlockHandler seem only to be used in non-cluster modes.

Well regardless we need to make sure whatever we make is viable in client mode. Just a note.

I'm digging through the code and I think this is how spark standalone seems to work:
Each Worker launches 1 or more Executors, which contain the spark conf and spark env (it actually launches an ExecutorRunner, which I believe seems to construct a command to launch the Executor although it wasn't automatically clear from the code). If a plugin is configured, then the external shuffle service should ideally be configured to be off, so the Executors and Driver should behave with the same code that it would in cluster mode in terms of interacting with the shuffle plugin interfaces, and the applicationRemoved() and executorRemoved() methods should do nothing. If the shuffle service is turned on, then the Worker is just launching an unused external shuffle service, which is also fine.
So I don't think we need to do anything extra to support shuffle plugins in standalone mode, but let me know if I'm missing something.

I couldn't figure out when and how the application shuffle files get removed in the case that uses YARN External Shuffle Service

YarnShuffleService is runs within yarn's Nodemanager, and its stopApplication() method gets called by yarn when yarn stops the application -- you won't see it getting called directly from spark code.  that in turn calls blockHandler.applicationRemoved().

Probably out of scope for this change, but I have a feeling that for non-default configs it would be useful to have a way for the driver component to provide data to the executor components.

Does accepting SparkConf in the constructor of ShuffleDataIO suffice? Or did we need something more sophisticated, for example the driver discovers some set of available remote servers and communicates those over to the executor components?

Or did we need something more sophisticated, for example the driver discovers some set of available remote servers and communicates those over to the executor components?

That's pretty much the use case I'm thinking of. It could be done through SparkConf but then it puts a burden on the configuration object being propagated properly so that the changes made by the driver plugin are visible to the executors when they start up. It may be the case already, haven't really tracked all the code.

That kind of protocol might belong in the implementation of the plugin and doesn't necessarily belong in core Spark as an RPC API. But perhaps if enough implementations end up wanting to do similar things down the line then we can support it in a first class way.

That kind of protocol might belong in the implementation of the plugin

Maybe, but even then, how would executors know how to connect back to the driver endpoint of the plugin? For example, for socket communication, they may be able to get the driver address from Spark's conf, but which port?
There must be some kind of communication between driver and executor to bootstrap that process. Not all plugins will be able to deal with static configuration (i.e. stuff you can pass to spark-submit with --conf).

What would be the API and the hooks we'd have to add to set up that communication? I'm very reluctant to add the complexity of having the driver serialize a bundle up to the executors via custom RPC endpoints set up on both sides.

I think making sure that the driver plugin can modify SparkConf, and that those modifications are available on the executor side when the executor plugin is started is enough to bootstrap this. No need to get too fancy.

How does the driver pass specific Spark configuration up to the executors? I thought once you started a Spark Context with a given Spark configuration, the executors are tied down to only using said configuration. Would we have to hook into the cluster manager specific scheduler backends? E.g. the Kubernetes executor pod launcher knows to pass along certain Spark configurations when launching executors.

Any config modification that is made on the driver side before the scheduler backend is started ends up propagated to executors. So if this plugin is being initialized before the scheduler backend is started, then the configuration should make it to executors. On the executor side, as long as the executor plugin is being initialized after the executor sends the RetrieveSparkAppConfig message to the driver, the plugin should see them.
Otherwise, you'd probably have to create another RPC to get the shuffle plugin-specific configs and make them available to the executor.

btw this topic of exchanging communication info also came up in a discussion on the executor plugin: https://issues.apache.org/jira/browse/SPARK-24918?focusedCommentId=16572850&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16572850

I don't think every plugin will need to setup communication between the driver and executor (in the case of kubernetes, the executors can dynamically discover the list of shuffle servers themselves), but I see how the current APIs would make setting sparkConf seem a bit more like a hack. Since the driver initialization happens in setting up the SparkContext, we could make initializeApplication() return a map of additional SparkConf configs that could be set in the SparkContext initialization code? And then move the plugin initialization to before the task scheduler starts. Would that address the driver to executor communication?

we could make initializeApplication() return a map of additional SparkConf configs that could be set in the SparkContext initialization code?

That sounds good enough for me.

Let's see how much work that would take - but if it looks to be too involved I'd like to make that a separate patch. We'd also have to test it against at least some of the cluster managers specifically.

Namely because I think writing an integration test that validates the behavior will not be easy to write.

Should be pretty simple e.g. in YarnClusterSuite. (Could also try using local-cluster[...] as the master.)

@vanzin i searched for a while, but I couldn't find the location in the code that limits the spark configs passed from the driver to the executor to start with the spark. prefix. The test breaks if I remove the spark. prefix on the key. I'm trying to figure out if it's a result of local-cluster deploy mode or something else, and whether we should just prefix all the driver configs returned with spark. automatically for the plugin implementer.

Actually, another suggestion would be to require a prefix and check for that prefix upon return from the initializeApplication() method (i.e. spark.shuffle.plugin)

I'm pretty sure the check is in CoarseGrainedSchedulerBackend.scala, check where sparkProperties is initialized.
What you could do, also to make the API more symmetric, is to add the prefix yourself when stashing the driver config in the SparkConf, and remove it on the executor side before passing a Map[String, String] to its initialization method (instead of relying on the code reading it from SparkConf directly).

This is looking close. @vanzin can you sanity check our implementation of properties propagation and confirm that it's in line with what you suggested? I'm +1 on my end.

Think all the comments are addressed so far. I'm going to merge this to unblock Ignite shuffle, otherwise the caches are going to be bloated indefinitely =) thanks everyone for reviewing!


master or <IP_ADDRESS> version doesn't load correctly in docker.

It displays briefly a blue background and then redirects to
"Not Found
The requested URL /app/overview.py was not found on this server."

Try using the latest tag, it works fine

I think the issue I encountered is with docker.
I always thought when I declare a bind-mount in docker or docker-compose, I would be able to persist that mount.  So I did this:

./haproxy-wi:

Strangely, what happens is that somehow it just shadows the app folder with an empty dir.

Probably your folder "./haproxy-wi" is empty


Install as Puma plugin if available

This PR implements a first approach to resolve #327. The README remains to be updated if this solution is finally accepted.

Thank you for writing this up! It seems reasonable, but I do have a concern that we're doing a lot to try to guess (and then not break) the user's development workflow.
I have a slight preference for #347 which is more general, if we can figure out how to land it. Let's leave this open for now, but I'll circle back once we made a decision on the other PR.


Refactored SelectMetadataField from class based component to functional Component

Refactored SelectMetadataField.jsx from class-based component to functional-based component.
Please let me know, if there is any changes required, as I am a new contributor to volto.

@codic-yeeshu you need to sign the Plone Contributor Agreement to merge this pull request.
Learn about the Plone Contributor Agreement: https://plone.org/foundation/contributors-agreement

Now, I have accepted the Plone contribution agreement. What should I do now? @mister-roboto

@codic-yeeshu from https://plone.org/foundation/contributors-agreement#8c8d380c-9337-4aa1-875e-b7292f64ac86

I signed the Agreement, but haven't been given access yet?
Please allow a week for a response. Volunteers process the Contributor Agreements. If you have issues, such as making a spelling error in your email or GitHub username, please contact<EMAIL_ADDRESS>
Also make sure that your email address on the agreement matches one for your GitHub account.

This was a duplicate of #5570


Fix: docs

updated docs for

new format for strategy
new parameter key names for backtesting and papertrading
quantstats mode for statistics report generation
new flowchart

Yes, for certain exchanges.
On Mon, 29 May 2023 at 18:41, akhil-jain-algobulls @.***>
wrote:

@.**** commented on this pull request.
In docs/pyalgotrad/index.md
https://github.com/algobulls/pyalgotrading/pull/20#discussion_r1209304030
:

   - [Test your Strategy](testing.md)

+### Features
+- Powered by the AlgoBulls Platform
+- Everything related to Algorithmic Trading Strategies!

Create & upload strategies on the AlgoBulls Platform

Free pool of Strategies are available separately at pyalgostrategypool!

Support for all 150+ Technical Indicators provided by TA-Lib

Support for multiple candlesticks patterns - Japanese OHLC, Renko, Heikin-Ashi, Linebreak

Support for multiple candle intervals - 1 minute, 3 minutes, 5 minutes, 10 minutes, 15 minutes, 30 minutes, 1 hour, 1 day.

Support for MARKET, LIMIT, STOPLOSS-MARKET, STOPLOSS-LIMIT orders

Support for INTRADAY and DELIVERY orders
+- Support for Backtesting and Paper Trading

Currently supported brokers
+- Real-time Logs for Backtesting and Paper Trading

@pushpakdagade https://github.com/pushpakdagade I told
@prithviraj-gotepatil-algobulls
https://github.com/prithviraj-gotepatil-algobulls to remove RT from
everywhere
we are planning to support RT through pyalgotrading?
—
Reply to this email directly, view it on GitHub
https://github.com/algobulls/pyalgotrading/pull/20#pullrequestreview-1449474879,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWO2Q3OGPAYTJ5KAQQQSVKTXISOA5ANCNFSM6AAAAAAX4GOCZY
.
You are receiving this because you were mentioned.Message ID:
@.***>


Camera Vision realtime still not support ?

I tested found vision parts just show front camera view, but vision frame not realtime comunicated with LLM, So, Any plan to support this?

Thanks for the question @skyxiaobai. Vision is only supported with some models, such as Claude Sonnet. Also please make sure you have "Voice and Vision" selected in the settings.

Thank you for your reminder. This is what I am doing. I am using GPT-4o by default and the RTVI Android SDK. After generating the APK and running it on the phone, I can see that the camera opens, but I found out that during the conversation, the content from the camera cannot be recognized. For example, in a scenario where you ask, "Can you see what I am doing?" the camera content is not detected. Actually, my goal is to utilize the camera's real-time video stream for conversation, similar to a video chat function. However, after testing, I found that only voice is real-time. Thanks again for your support.


hls buffering too much data

I am having problems trying to implement fluid player.  The problem is that it is buffering 2 1/2 minutes instead of about 30 seconds.    I tried to set the maxBufferLength but it didn't seem to work.  I looked at the example on https://docs.fluidplayer.com/docs/streaming/hls/ and it buffers half of the 9 minute video almost immediately.
Thanks for any help.

Hi @ashmodai1972, currently this can be done by using the module hook configureHls, here is a sample on how to this:
var instance = fluidPlayer('fluid-player', {
    modules: {
        configureHls: (options) => ({
            maxMaxBufferLength: 30, // Max length of buffered video
            startLevel: 4, // Starting quality level - 4 is usually Full HD (1080p)
            ...options,
        })
    }
});

Let me know if this helps you with your problem.