'data parameter is nil' when parsing FIRUser IDToken on 4.13.0 while signing into facebook

[REQUIRED] Step 1: Describe your environment

Xcode version: 9.3_
Firebase SDK version: 4.13.0___
Firebase Component: _Auth (Auth, Core, Database, Firestore, Messaging, Storage, etc)
Component version: 4.6.1_

[REQUIRED] Step 2: Describe the problem
My current IOS project has two targets ("production" and "development").
In the production version of the project, I can sign in using facebook without a crash.
Yet when signing into Facebook on the development target the app crashes with a "Thread 82: EXC_BREAKPOINT" break point inside - (void)invokeFetchCallbacksOnCallbackQueueWithData:  function. Also all other sign methods work (email/password and google) on both targets.

podfile.lock

If you like to see the pod file itself i can also add that too. Yet i did not change that file before updating pods, i just ran pod update in terminal. Before the update everything worked as intended on both targets.

Same exact stacktrace here
- Firebase/Auth (4.13.0):
    - Firebase/Core
    - FirebaseAuth (= 4.6.1)
  - Firebase/Core (4.13.0):
    - FirebaseAnalytics (= 4.2.0)
    - FirebaseCore (= 4.0.20)
  - Firebase/DynamicLinks (4.13.0):
    - Firebase/Core
    - FirebaseDynamicLinks (= 2.3.2)
  - Firebase/Messaging (4.13.0):
    - Firebase/Core
    - FirebaseMessaging (= 2.2.0)
  - Firebase/Performance (4.13.0):
    - Firebase/Core
    - FirebasePerformance (= 1.1.3)
  - FirebaseAnalytics (4.2.0):
    - FirebaseCore (~> 4.0)
    - FirebaseInstanceID (~> 2.0)
    - "GoogleToolboxForMac/NSData+zlib (~> 2.1)"
    - nanopb (~> 0.3)
  - FirebaseAuth (4.6.1):
    - FirebaseAnalytics (~> 4.2)
    - "GoogleToolboxForMac/NSDictionary+URLArguments (~> 2.1)"
    - GTMSessionFetcher/Core (~> 1.1)
  - FirebaseCore (4.0.20):
    - "GoogleToolboxForMac/NSData+zlib (~> 2.1)"

Implementation, redacted unrelated.
let credential = PhoneAuthProvider.provider().credential(withVerificationID: verificationId, verificationCode: verificationCode)
Auth.auth().signIn(with: credential) { [weak self] (user, error) in
    user.getIDTokenForcingRefresh(true, completion: { (idToken, error) in

        guard let user = user else {
          SVProgressHUD.showError(withStatus: C.ErrorMessages.generic)
          return
        }
    })
}

I am able to quickly reproduce this error with the following in AppDelegate
func applicationDidBecomeActive(_ application: UIApplication) {
  if let currentUser = Auth.auth().currentUser {
      currentUser.getIDToken { (token, error) in

      }
  }
}

Thanks @stshelton and @rromanchuk. I was just coming here to add this and y'all beat me to it. I'm having the exact same issue.

Im trying to switch to source pods or master branch but I keep getting the error [!] Unable to find a specification for 'Firebase'. when running pod install. Ive deleted and reinstalled cocoa pods but still receiveing error.

@stshelton yeah, it's a little picky, here is what i'm using
pod 'FirebaseCore', :git => 'https://github.com/firebase/firebase-ios-sdk.git', :branch => 'master'
  pod 'FirebaseAuth', :git => 'https://github.com/firebase/firebase-ios-sdk.git', :branch => 'master'
  pod 'FirebaseMessaging', :git => 'https://github.com/firebase/firebase-ios-sdk.git', :branch => 'master'
  pod 'Firebase/DynamicLinks'
  pod 'Firebase/Performance'

@stshelton: @rromanchuk's Podfile looks good. Change to the branch specifier to :branch => 'release-4.13.0' to get the last official release.
If you're still having trouble, please post what you have.

I'm not sure if this is related to facebook login, these few days the photoURL returned is either:

https://lookaside.facebook.com/platform/profilepic/?asid={Facebook_user_ID}&height=100&width=100&ext=1524206352&hash=AeRU6R6kKZ1WJbz5
https://graph.facebook.com/{Facebook_user_ID}/picture

The crash will happen if the URL is of pattern 1.

Even before this problem, I'd been having a lot of trouble with Facebook's lookaside CDN subdomain. I would use the graph URL to fetch the profile picture, but whenever it routed to the lookaside CDN it always failed to get the image. I've never had this problem with any of Facebook's other CDN subdomains.

As #1072 was closed, I'll post here which seems to be the new Issue related to the -[FIRUser parseIDToken:error:] crash.
There is still a regression with -[FIRUser parseIDToken:error:] .
We upgraded from 4.11 to 4.12 in our previous release and went from 94.38% crash free users to 51.19% - #1072
Then we released a hotfix version including 4.13 and still get some -[FIRUser parseIDToken:error:] crashes. We have 85.15% crash-free users, number going down.
#0 Crashed: com.google.firebase.auth.serialTaskQueue
EXC_BREAKPOINT 0x00000001002b3418

Still looking into this error. Was anyone able to obtain the affected token via source pods. There is an easier method to obtain the affect ID token. If you are able to sign in with the problematic Facebook user, you can obtain the refreshToken from the user object [FIRAuth auth].currentUser.refreshToken.
You can then use the refresh token to obtain the IDToken by following the instructions here. If you are able to please share your affected IDToken.
Please be advised that any IDToken you share publicly can be easily parsed to obtain the contents, please make sure you are sharing the IDToken for a test account if you decide to do so.

I noticed i keep getting this error. I noticed in the FIRAuthErrorUserInfoDeserializedResponseKey it's my JWT token. This may be developer error, as i have been recently refactoring for better firebase session management.
13:39:41.216 ❤ ERROR SparApp.refreshFirebaseIfNeeded():137 - Error Domain=FIRAuthErrorDomain Code=17999 "An internal error has occurred, print and inspect the error details for more information." UserInfo={error_name=ERROR_INTERNAL_ERROR, NSLocalizedDescription=An internal error has occurred, print and inspect the error details for more information., NSUnderlyingError=0x1d4249600 {Error Domain=FIRAuthInternalErrorDomain Code=4 "(null)" UserInfo={FIRAuthErrorUserInfoDeserializedResponseKey= [MY JWT TOKEN]}}}

@rromanchuk

I noticed i keep getting this error. I noticed in the FIRAuthErrorUserInfoDeserializedResponseKey it's my JWT token

This isn't your error, this is by design. The reason that the  error contains your JWT is so that whether or not the token parsing fails we can still provide you the JWT which we couldn't parse ourselves (you can at least use to to trouble shoot or contact support and it won't crash the app).
For everyone building from the source pods; please use this the following branch to avoid building from head which is not as stable:
https://github.com/firebase/firebase-ios-sdk/tree/staging-4.13.1
Any updates to this parsing error will be added to this branch.
-Z

Thanks for the quick response to fix the issue.
Last week (19 April 2018) I was using the master branch with this commit:
https://github.com/firebase/firebase-ios-sdk/commits/81ac1761e2195aa2f16c0377471e084910ccdb35
And Firebase will return the following error for invalid token after signing in with Facebook:
Error Domain=FIRAuthErrorDomain Code=17999 "An internal error has occurred, print and inspect the error details for more information." UserInfo={error_name=ERROR_INTERNAL_ERROR, NSLocalizedDescription=An internal error has occurred, print and inspect the error details for more information., NSUnderlyingError=0x1d4249600 {Error Domain=FIRAuthInternalErrorDomain Code=4 "(null)" UserInfo={FIRAuthErrorUserInfoDeserializedResponseKey= [MY JWT TOKEN]}}}
And today (23 April 2018) after switching to the 'staging-4.13.1' branch, Firebase no longer return the error above even with the same sign-in, is this the expected behaviour?
Thank you.

@klwoon This is expected behavior. The parser is able to handle the "invalid URL" now (I can provide a detailed explanation as to why the token parsing failed if needed).
I think you should still handle the above mentioned error case since there may be some exceptional edge case where token parsing fails; in which case you can obtain your JWT regardless.
-Z

@protocol86 Hi, thanks for the reply, I would be appreciated if you could explain the token parsing, I'm new and still learning every bit, thanks.

Trying to switch over to the staging branch here's pod file.
pod 'FirebaseCore', :git => 'https://github.com/firebase/firebase-ios-sdk.git', :branch => 'staging-4.13.1'
  pod 'FirebaseAuth', :git => 'https://github.com/firebase/firebase-ios-sdk.git', :branch => 'staging-4.13.1'
pod 'FirebaseMessaging', :git => 'https://github.com/firebase/firebase-ios-sdk.git', :branch => 'staging-4.13.1'
  pod 'Firebase/Performance'
 pod 'Firebase/DynamicLinks'
 pod 'Firebase/RemoteConfig'
  pod 'Firebase/Database'
 pod 'Firebase/Storage'
Yet after runnging pod install,  I get these build  errors "Could not build Objective-C module 'Firebase", "Could not build module 'FirebaseAnalytics'" and "'FirebaseCore/FIRAnalyticsConfiguration.h' file not found"
Should I be inclunding the branch for all pods? I also noticed the podfile.lock still says firebase version is 4.13.0 after running pod install with above pod file too.

@stshelton I'm able to build a sample app with your Podfile.
Do you have use_frameworks! in your Podfile?  If not, see the static library usage section.
The versions are a bit confusing. Sorry about that. Here are the details: Since we didn't do a full Firebase update for this bug fix and the Firebase CocoaPod locks to particular patch versions of its subspec dependencies, none of the version specification are changed in 'staging-4.13.1', so that the fixed FirebaseAuth pod which you're accessing via GitHub will override the default version for Firebase 4.13.0. If we roll out the fixes in a published release before 5.0.0, it will be 4.13.1, but that's not set yet.

Having the same error as well currently while calling user.getIDTokenForcingRefresh

Hello all, I am having the same [FIRUser parseIdToken:error] crash as @Francescu.  Mine occurs on any call to FirebaseAuth getIDToken***  This seems to be the currently active thread, so I will post here.
 Unable to find a specification for 'Firebase'. (though I am sure this is user error...)
Podfile.lock
PODS:
  - AFNetworking (3.2.0):
    - AFNetworking/NSURLSession (= 3.2.0)
    - AFNetworking/Reachability (= 3.2.0)
    - AFNetworking/Security (= 3.2.0)
    - AFNetworking/Serialization (= 3.2.0)
    - AFNetworking/UIKit (= 3.2.0)
  - AFNetworking/NSURLSession (3.2.0):
    - AFNetworking/Reachability
    - AFNetworking/Security
    - AFNetworking/Serialization
  - AFNetworking/Reachability (3.2.0)
  - AFNetworking/Security (3.2.0)
  - AFNetworking/Serialization (3.2.0)
  - AFNetworking/UIKit (3.2.0):
    - AFNetworking/NSURLSession
  - Bolts (1.9.0):
    - Bolts/AppLinks (= 1.9.0)
    - Bolts/Tasks (= 1.9.0)
  - Bolts/AppLinks (1.9.0):
    - Bolts/Tasks
  - Bolts/Tasks (1.9.0)
  - Branch (0.24.1):
    - Branch/Core (= 0.24.1)
  - Branch/Core (0.24.1)
  - Crashlytics (3.10.1):
    - Fabric (~> 1.7.5)
  - Fabric (1.7.6)
  - FBSDKCoreKit (4.32.0):
    - Bolts (~> 1.7)
  - FBSDKLoginKit (4.32.0):
    - FBSDKCoreKit
  - Firebase/Analytics (4.13.0):
    - Firebase/Core
  - Firebase/Auth (4.13.0):
    - Firebase/Core
    - FirebaseAuth (= 4.6.1)
  - Firebase/Core (4.13.0):
    - FirebaseAnalytics (= 4.2.0)
    - FirebaseCore (= 4.0.20)
  - Firebase/Database (4.13.0):
    - Firebase/Core
    - FirebaseDatabase (= 4.1.5)
  - Firebase/DynamicLinks (4.13.0):
    - Firebase/Core
    - FirebaseDynamicLinks (= 2.3.2)
  - Firebase/Messaging (4.13.0):
    - Firebase/Core
    - FirebaseMessaging (= 2.2.0)
  - Firebase/Performance (4.13.0):
    - Firebase/Core
    - FirebasePerformance (= 1.1.3)
  - Firebase/Storage (4.13.0):
    - Firebase/Core
    - FirebaseStorage (= 2.2.0)
  - FirebaseAnalytics (4.2.0):
    - FirebaseCore (~> 4.0)
    - FirebaseInstanceID (~> 2.0)
    - GoogleToolboxForMac/NSData+zlib (~> 2.1)
    - nanopb (~> 0.3)
  - FirebaseAuth (4.6.1):
    - FirebaseAnalytics (~> 4.2)
    - GoogleToolboxForMac/NSDictionary+URLArguments (~> 2.1)
    - GTMSessionFetcher/Core (~> 1.1)
  - FirebaseCore (4.0.20):
    - GoogleToolboxForMac/NSData+zlib (~> 2.1)
  - FirebaseDatabase (4.1.5):
    - FirebaseAnalytics (~> 4.1)
    - FirebaseCore (~> 4.0)
    - leveldb-library (~> 1.18)
  - FirebaseDynamicLinks (2.3.2):
    - FirebaseAnalytics (~> 4.0)
  - FirebaseInstanceID (2.0.10):
    - FirebaseCore (~> 4.0)
  - FirebaseMessaging (2.2.0):
    - FirebaseAnalytics (~> 4.1)
    - FirebaseCore (~> 4.0)
    - FirebaseInstanceID (~> 2.0)
    - GoogleToolboxForMac/Logger (~> 2.1)
    - Protobuf (~> 3.5)
  - FirebasePerformance (1.1.3):
    - FirebaseAnalytics (~> 4.1)
    - FirebaseInstanceID (~> 2.0)
    - FirebaseSwizzlingUtilities/ISASwizzling (~> 1.0)
    - FirebaseSwizzlingUtilities/MethodSwizzling (~> 1.0)
    - GoogleToolboxForMac/Logger (~> 2.1)
    - GoogleToolboxForMac/NSData+zlib (~> 2.1)
    - GTMSessionFetcher/Core (~> 1.1)
    - Protobuf (~> 3.5)
  - FirebaseStorage (2.2.0):
    - FirebaseAnalytics (~> 4.1)
    - FirebaseCore (~> 4.0)
    - GTMSessionFetcher/Core (~> 1.1)
  - FirebaseSwizzlingUtilities/ISASwizzling (1.0.1)
  - FirebaseSwizzlingUtilities/MethodSwizzling (1.0.1):
    - FirebaseCore (~> 4.0)
  - FontAwesomeKit (2.2.1):
    - FontAwesomeKit/Core (= 2.2.1)
    - FontAwesomeKit/FontAwesome (= 2.2.1)
    - FontAwesomeKit/FoundationIcons (= 2.2.1)
    - FontAwesomeKit/IonIcons (= 2.2.1)
    - FontAwesomeKit/Material (= 2.2.1)
    - FontAwesomeKit/Octicons (= 2.2.1)
    - FontAwesomeKit/Zocial (= 2.2.1)
  - FontAwesomeKit/Core (2.2.1)
  - FontAwesomeKit/FontAwesome (2.2.1):
    - FontAwesomeKit/Core
  - FontAwesomeKit/FoundationIcons (2.2.1):
    - FontAwesomeKit/Core
  - FontAwesomeKit/IonIcons (2.2.1):
    - FontAwesomeKit/Core
  - FontAwesomeKit/Material (2.2.1):
    - FontAwesomeKit/Core
  - FontAwesomeKit/Octicons (2.2.1):
    - FontAwesomeKit/Core
  - FontAwesomeKit/Zocial (2.2.1):
    - FontAwesomeKit/Core
  - GoogleSignIn (4.1.2):
    - GoogleToolboxForMac/NSDictionary+URLArguments (~> 2.1)
    - GoogleToolboxForMac/NSString+URLArguments (~> 2.1)
    - GTMOAuth2 (~> 1.0)
    - GTMSessionFetcher/Core (~> 1.1)
  - GoogleToolboxForMac/DebugUtils (2.1.3):
    - GoogleToolboxForMac/Defines (= 2.1.3)
  - GoogleToolboxForMac/Defines (2.1.3)
  - GoogleToolboxForMac/Logger (2.1.3):
    - GoogleToolboxForMac/Defines (= 2.1.3)
  - GoogleToolboxForMac/NSData+zlib (2.1.3):
    - GoogleToolboxForMac/Defines (= 2.1.3)
  - GoogleToolboxForMac/NSDictionary+URLArguments (2.1.3):
    - GoogleToolboxForMac/DebugUtils (= 2.1.3)
    - GoogleToolboxForMac/Defines (= 2.1.3)
    - GoogleToolboxForMac/NSString+URLArguments (= 2.1.3)
  - GoogleToolboxForMac/NSString+URLArguments (2.1.3)
  - GTMOAuth2 (1.1.6):
    - GTMSessionFetcher (~> 1.1)
  - GTMSessionFetcher (1.1.15):
    - GTMSessionFetcher/Full (= 1.1.15)
  - GTMSessionFetcher/Core (1.1.15)
  - GTMSessionFetcher/Full (1.1.15):
    - GTMSessionFetcher/Core (= 1.1.15)
  - IQKeyboardManager (6.0.1)
  - ISO8601DateFormatter (0.8)
  - KZPropertyMapper (2.9)
  - leveldb-library (1.20)
  - Masonry (1.1.0)
  - MGSwipeTableCell (1.6.6)
  - nanopb (0.3.8):
    - nanopb/decode (= 0.3.8)
    - nanopb/encode (= 0.3.8)
  - nanopb/decode (0.3.8)
  - nanopb/encode (0.3.8)
  - Plaid (1.1.8)
  - Protobuf (3.5.0)
  - SDWebImage (4.1.2):
    - SDWebImage/Core (= 4.1.2)
  - SDWebImage/Core (4.1.2)
  - SMTWiFiStatus (1.0.4)
  - Stripe (12.1.2)
  - SVProgressHUD (2.2.5)
  - UIImage-Resize (1.0.1)

DEPENDENCIES:
  - AFNetworking
  - Branch
  - Crashlytics (~> 3.10.1)
  - Fabric (~> 1.7.6)
  - FBSDKLoginKit
  - Firebase/Analytics
  - Firebase/Auth
  - Firebase/Core
  - Firebase/Database
  - Firebase/DynamicLinks
  - Firebase/Messaging
  - Firebase/Performance
  - Firebase/Storage
  - FontAwesomeKit (from `https://github.com/PrideChung/FontAwesomeKit.git`, commit `ed5eb02`)
  - GoogleSignIn
  - IQKeyboardManager
  - ISO8601DateFormatter (~> 0.8)
  - KZPropertyMapper (~> 2.9)
  - Masonry
  - MGSwipeTableCell
  - Plaid
  - SDWebImage (~> 4.1.2)
  - SMTWiFiStatus
  - Stripe
  - SVProgressHUD (~> 2.2.2)
  - UIImage-Resize (~> 1.0.1)

EXTERNAL SOURCES:
  FontAwesomeKit:
    :commit: ed5eb02
    :git: https://github.com/PrideChung/FontAwesomeKit.git

CHECKOUT OPTIONS:
  FontAwesomeKit:
    :commit: ed5eb02
    :git: https://github.com/PrideChung/FontAwesomeKit.git

SPEC CHECKSUMS:
  AFNetworking: 8ac6017b94ea105479f7776e5288e48ae9c59bb4
  Bolts: ac6567323eac61e203f6a9763667d0f711be34c8
  Branch: 8b59411a12867bde4fe8c9d3c0f107c5811e303e
  Crashlytics: aee1a064cbbf99b32efa3f056a5f458d846bc8ff
  Fabric: f8d42c893bb187326a7968b62abe55c36a987a46
  FBSDKCoreKit: 55d7f2ac45d9c4b9b6119f4e43900fe84b9b7b1b
  FBSDKLoginKit: 32ac05c2a59952c363c2e85aafa8f73ba93bcbad
  Firebase: 5ec5e863d269d82d66b4bf56856726f8fb8f0fb3
  FirebaseAnalytics: 7ef69e76a5142f643aeb47c780e1cdce4e23632e
  FirebaseAuth: bf22cacf22c60ab454bf2636f556d8892b10b53f
  FirebaseCore: 90cb1c53d69b556f112a1bf72b5fcfaad7650790
  FirebaseDatabase: 5f0bc6134c5c237cf55f9e1249d406770a75eafd
  FirebaseDynamicLinks: 38b68641d24e78d0277a9205d988ce22875d5a25
  FirebaseInstanceID: 8d20d890d65c917f9f7d9950b6e10a760ad34321
  FirebaseMessaging: 75cdb862e86c30e0913a2ff307e48d49357c5b73
  FirebasePerformance: 85bdc3f3d630deb629e85695fcab23364d68f5db
  FirebaseStorage: 0c223481c8f89ed300cf1239ddd2d9833622c65f
  FirebaseSwizzlingUtilities: 6006111d30248d2321ffac0231e246663e704ea3
  FontAwesomeKit: 3614979b3dbb0ec3f7fac1bd760b91f66c31db67
  GoogleSignIn: d9ef55b10f0aa401a5de2747f59b725e4b9732ac
  GoogleToolboxForMac: 2501e2ad72a52eb3dfe7bd9aee7dad11b858bd20
  GTMOAuth2: c77fe325e4acd453837e72d91e3b5f13116857b2
  GTMSessionFetcher: 5fa5b80fd20e439ef5f545fb2cb3ca6c6714caa2
  IQKeyboardManager: 118602feb2d0b8852cc7387c21db988f2ebdec6d
  ISO8601DateFormatter: 4551b6ce4f83185425f583b0b3feb3c7b59b942c
  KZPropertyMapper: 26e5a63c47cf4c7b1a1c2bdc853a9406200f8868
  leveldb-library: 08cba283675b7ed2d99629a4bc5fd052cd2bb6a5
  Masonry: 678fab65091a9290e40e2832a55e7ab731aad201
  MGSwipeTableCell: c3bc6e261e7bc06c112909fe3fb8205de286082c
  nanopb: 5601e6bca2dbf1ed831b519092ec110f66982ca3
  Plaid: a9935ff28449b2ccbdbe89fac56ec58bee432fd4
  Protobuf: 8a9838fba8dae3389230e1b7f8c104aa32389c03
  SDWebImage: cb6f9f266a9977741efcbc21e618e8be3734c774
  SMTWiFiStatus: 2ceb47a51cfe166d2c3a0301071c8e88b2a879c2
  Stripe: 3230cdf8a8b0c04902e45e86f222fb82a926239c
  SVProgressHUD: 1428aafac632c1f86f62aa4243ec12008d7a51d6
  UIImage-Resize: fa776860f10e6900bbaf53a73e494bdceaaccc77

PODFILE CHECKSUM: 16f36c45d9e045ca6ef2d9ec2dce5d5b5b9b8880

COCOAPODS: 1.4.0

The fix will deploy in our upcoming 5.0.0 release.
In the meantime to access the workaround, make sure you run pod update with a Podfile including:
pod 'FirebaseCore', :git => 'https://github.com/firebase/firebase-ios-sdk.git', :branch => 'staging-4.13.1'
pod 'FirebaseAuth', :git => 'https://github.com/firebase/firebase-ios-sdk.git', :branch => 'staging-4.13.1'

If you're having trouble setting up the workaround, please share the Podfile you're using.

Hi Paul!  Attempts to use the staging branch now build, but don't compile.
Podfile
# Uncomment this line to define a global platform for your project
platform :ios, '9.0'

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

  # Pods for Events
  pod 'AFNetworking'
  pod "SMTWiFiStatus"

  pod 'FontAwesomeKit', :git => 'https://github.com/PrideChung/FontAwesomeKit.git', :commit => 'ed5eb02'
  pod 'Masonry'

  pod 'MGSwipeTableCell'

  pod 'Firebase'
  pod 'FirebaseCore', :git => 'https://github.com/firebase/firebase-ios-sdk.git', :branch => 'staging-4.13.1'
  pod 'FirebaseAuth', :git => 'https://github.com/firebase/firebase-ios-sdk.git', :branch => 'staging-4.13.1'
  pod 'Firebase/Messaging'
  pod 'Firebase/Analytics'
  pod 'Firebase/Database'
  pod 'Firebase/DynamicLinks'
  pod 'Firebase/Storage'
  pod 'Firebase/Performance'

  pod 'Fabric', '~> 1.7.6'
  pod 'Crashlytics', '~> 3.10.1'

  pod 'GoogleSignIn'
  pod 'FBSDKLoginKit'

  pod 'Branch'

  pod 'Stripe'
  pod 'Plaid'

  pod 'SDWebImage', '~> 4.1.2'
  pod 'UIImage-Resize', '~> 1.0.1'
  pod 'SVProgressHUD', '~> 2.2.2'
  pod 'KZPropertyMapper', '~> 2.9'

  pod 'ISO8601DateFormatter', '~> 0.8'
  pod 'IQKeyboardManager'
end

post_install do |installer|
  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
      config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '9.0'
    end
  end
end

I am sure this is an error on my end, but thought I would share nonetheless.  Do you have an ETA for v5.0.0 ?  Thank you and your team!

@iiAtlas  You're running into the static library (no use_frameworks!) issue documented with workaround here. The static library source pods issue is also fixed in 5.0.0.
Sorry, we can't give out dates - but you could investigate when the last two major Firebase releases came out to make a guess ...

@paulb777 THANK YOU for the assistance with that.  I can confirm the post_installer script/FirebaseAnalytics script fixed my build issues, and that 4.13.1 has fixed my [FIRUser parseIDToken:error:] crash.
Looking forward to 5.0.0 !

I'm running pod update after modifying my Podfile and am getting this:
Pre-downloading: `FirebaseAuth` from `https://github.com/firebase/firebase-ios-sdk.git`, branch `staging-4.13.1`
[!] Failed to download 'FirebaseAuth'.

These are my Pods
  pod 'RNFirebase', :path => '../node_modules/react-native-firebase/ios/RNFirebase.podspec'
  pod 'FirebaseCore', :git => 'https://github.com/firebase/firebase-ios-sdk.git', :branch => 'staging-4.13.1'
  pod 'Firebase/AdMob'
  pod 'Firebase/Analytics'
  pod 'FirebaseAuth', :git => 'https://github.com/firebase/firebase-ios-sdk.git', :branch => 'staging-4.13.1'
  pod 'Firebase/Database'
  #pod 'Firebase/DynamicLinks'
  #pod 'Firebase/Firestore'
  #pod 'Firebase/Messaging'
  pod 'Firebase/Performance'
  pod 'Firebase/RemoteConfig'
  pod 'Firebase/Storage'
  pod 'Fabric', '~> 1.7.2'
  pod 'Crashlytics', '~> 3.9.3'

Note that we use React Native but I don't think that should have any influence in this error we're getting unless it needs the Firebase pod that we replaced with RNFirebase.

@wbattel4607 can you run pod update with the --verbose flag and post the reason the download failed?

It wasn't giving any reason, so I updated my version of Cocoapods and now it seems to be working. Sorry for the inconvenience.

@wbattel4607 Might need to add pod Firebase. Share your Podfile if you're still having trouble.

Unfortunately it seems that adding the Firebase pod made no difference.
This is my Podfile. To avoid a massive blob of code I've uploaded it to PasteBin here: https://pastebin.com/7saHaezn

I tried to revert to 4.11.0, which is the version we used before without problem. I'm getting the same error, so I think I have to ask the RNFirebase guys. I don't think that particular build error is from the native iOS sdk.
  pod 'RNFirebase', :path => '../node_modules/react-native-firebase/ios/RNFirebase.podspec'
  pod 'FirebaseCore', :git => 'https://github.com/firebase/firebase-ios-sdk.git', :tag => '4.11.0'
  pod 'Firebase/AdMob'
  pod 'Firebase/Analytics'
  pod 'FirebaseAuth', :git => 'https://github.com/firebase/firebase-ios-sdk.git', :tag => '4.11.0'
  pod 'Firebase/Database'
  #pod 'Firebase/DynamicLinks'
  #pod 'Firebase/Firestore'
  #pod 'Firebase/Messaging'
  pod 'Firebase/Performance'
  pod 'Firebase/RemoteConfig'
  pod 'Firebase/Storage'
  pod 'Fabric', '~> 1.7.2'
  pod 'Crashlytics', '~> 3.9.3'

We still can't get our project to build when we use 4.11.0 or 4.13.1 via git. 4.13.0 builds fine but then we have the problem that this issue is about, so we can't use it.
When we use 4.11.0 we get this problem, and when we use 4.13.1 we get this problem.
@paulb777 @protocol86 how come 4.13.1 isn't being released beyond staging? I know 5.0.0 is coming very soon but we haven't been able to get our project to build for the past 2 weeks and it's really becoming a problem.

@wbattel4607 Sorry about the slow response.
It looks like you solved the 4.11.0 issue in #1197. More comments coming there.
Were you able to find out anything from RNFirebase folks about the other problem. It looks like the search path to the Firebase module.map is not set up correctly. If minimal repro instructions (for someone who does not have RNFirebase installed) are published, I'll take a deeper look.

@paulb777 it does seem to be a podspec issue with RNFirebase. I was able to fix that problem using a suggested fix in an open PR on their repo, see here: https://github.com/invertase/react-native-firebase/pull/1017
tl;dr, this repo is not the cause of that issue.


An error occured while loading a crd resource list

Describe the bug
A parse error occurred while loading my own customize resource definition,
Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

Lens Version: 3.4.0
OS: [e.g. OSX] MacOS Catalina 10.15.4
Installation method (e.g. snap or AppImage in Linux):

Logs:
When you run the application executable from command line you will see some logging output. Please paste them here:
Error: Lexical error on line 1. Unrecognized text.
...ta.labels.kubesphere\.io/workspace
-----------------------^
    at Parser.parseError (webpack-internal:///105:3928:15)
    at Parser.parser.yy.parseError (webpack-internal:///105:5128:17)
    at Object.parseError (webpack-internal:///105:4103:28)
    at Object.next (webpack-internal:///105:4357:25)
    at Object.lex (webpack-internal:///105:4367:22)
    at lex (webpack-internal:///105:3956:28)
    at Parser.parse (webpack-internal:///105:3969:26)
    at JSONPath.nodes (webpack-internal:///105:4982:26)
    at JSONPath.query (webpack-internal:///105:4958:22)
    at eval (webpack-internal:///990:13303:39)

crd.yaml
kind: CustomResourceDefinition
apiVersion: apiextensions.k8s.io/v1
metadata:
  name: workspaceroles.iam.kubesphere.io
  annotations:
    controller-gen.kubebuilder.io/version: (devel)
spec:
  group: iam.kubesphere.io
  names:
    plural: workspaceroles
    singular: workspacerole
    kind: WorkspaceRole
    listKind: WorkspaceRoleList
    categories:
      - iam
  scope: Cluster
  versions:
    - name: v1alpha2
      served: true
      storage: true
      schema:
        openAPIV3Schema:
          type: object
          properties:
            apiVersion:
              description: >-
                APIVersion defines the versioned schema of this representation
                of an object. Servers should convert recognized schemas to the
                latest internal value, and may reject unrecognized values.  Servers may infer this from the endpoint the
                client submits requests to. Cannot be updated. In CamelCase.
                More info:
                https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
              type: string
            metadata:
              description: Standard object's metadata.
              type: object
            rules:
              description: Rules holds all the PolicyRules for this ClusterRole
              type: array
              items:
                description: >-
                  PolicyRule holds information that describes a policy rule, but
                  does not contain information about who the rule applies to or
                  which namespace the rule applies to.
                type: object
                required:
                  - verbs
                properties:
                  apiGroups:
                    description: >-
                      APIGroups is the name of the APIGroup that contains the
                      resources.  If multiple API groups are specified, any
                      action requested against one of the enumerated resources
                      in any API group will be allowed.
                    type: array
                    items:
                      type: string
                  nonResourceURLs:
                    description: >-
                      NonResourceURLs is a set of partial urls that a user
                      should have access to.  *s are allowed, but only as the
                      full, final step in the path Since non-resource URLs are
                      not namespaced, this field is only applicable for
                      ClusterRoles referenced from a ClusterRoleBinding. Rules
                      can either apply to API resources (such as "pods" or
                      "secrets") or non-resource URL paths (such as "/api"),
                      but not both.
                    type: array
                    items:
                      type: string
                  resourceNames:
                    description: >-
                      ResourceNames is an optional white list of names that the
                      rule applies to.  An empty set means that everything is
                      allowed.
                    type: array
                    items:
                      type: string
                  resources:
                    description: >-
                      Resources is a list of resources this rule applies to.
                      ResourceAll represents all resources.
                    type: array
                    items:
                      type: string
                  verbs:
                    description: >-
                      Verbs is a list of Verbs that apply to ALL the
                      ResourceKinds and AttributeRestrictions contained in this
                      rule.  VerbAll represents all kinds.
                    type: array
                    items:
                      type: string
      subresources: {}
      additionalPrinterColumns:
        - name: Workspace
          type: string
          jsonPath: .metadata.labels.kubesphere\.io/workspace
        - name: Alias
          type: string
          jsonPath: .metadata.annotations.kubesphere\.io/alias-name
  conversion:
    strategy: None
  preserveUnknownFields: true

I am having trouble reproducing this issue. Running both on the latest release (3.5.0) and on the latest master I don't see a crash. I do get a different error:
The CustomResourceDefinition "workspaceroles.iam.kubesphere.io" is invalid:
* spec.validation.openAPIV3Schema.properties[metadata]: Forbidden: must not specify anything other than name and generateName, but metadata is implicitly specified
* spec.preserveUnknownFields: Invalid value: true: cannot set to true, set x-preserve-unknown-fields to true in spec.versions[*].schema instead

I can see that the current error footer makes this very difficult to read. So I will probably do some work on that.

@leoendless are you still seeing this error on the latest version?

@Nokel81 please see also #611

Hi @Nokel81,
I'm still seeing this issue. I thought it may have been a regression in 4.0.0, but I was able to reproduce the same issue in versions 3.6.9 and 3.6.0, so I'm not sure it was ever resolved.

@arzarif Would you mind opening a new issue then please? (It helps in tracking to have a new issue). Thanks.

Of course! Opened #1773, as per requested. Thanks!


Unity editor rounds down floats to integers when retrieved from realtime database

Please fill in the following fields:
Unity editor version: 2019.2.6f1, 2019.2.10f1, 2019.3.0b10, 2020.1.0a12
Firebase Unity SDK version: 6.6.0
Firebase plugins in use: Only Database
Additional SDKs you are using: None
Platform you are using the Unity editor on: Linux, ubuntu 19.10 on two different machines
Platform you are targeting (iOS, Android, and/or desktop): Android
Scripting Runtime (Mono, and/or IL2CPP): Mono (I believe)
Please describe the issue here:
(Please list the full steps to reproduce the issue. Include device logs, Unity logs, and stack traces if available.)

Create a new firebase realtime database.
Create a new floating point value
Try to retrieve that value - it will be rounded down.

Here is an example script that you can just attach to any object that gets loaded and test the issue:
using System.Collections;
using System.Collections.Generic;
using UnityEngine;

using Firebase;
using Firebase.Unity.Editor;
using Firebase.Database;

public class test: MonoBehaviour {
  void Start() {
    // Set this before calling into the realtime database.
    FirebaseApp.DefaultInstance.SetEditorDatabaseUrl("https://unity-test-9f7cc.firebaseio.com/");

    DatabaseReference reference = FirebaseDatabase.DefaultInstance.RootReference;
    Debug.Log("Aigt imma head in");
        FirebaseDatabase.DefaultInstance
      .GetReference("test")
      .GetValueAsync().ContinueWith(task => {
        if (task.IsFaulted) {
          // Handle the error...
          Debug.Log("Error");
        }
        else if (task.IsCompleted) {
          DataSnapshot snapshot = task.Result;
          // Do something with snapshot...
          Debug.Log(snapshot);
        }
      });
  }
}

Expected output: "Aight imma head in" and "key:"test",value:2.69"
Tested output: "Aight imma head in" and "key:"test",value:2"
Could this be linked to the fact that i have (quite disgustingly) downloaded the libssl.1.0.2 and install it in order to circumvent this issue:
https://forum.unity.com/threads/empty-log-errors-in-2019-1-0f2.669961/
https://issuetracker.unity3d.com/issues/linux-roslyn-fails-if-there-is-a-newer-libssl-than-1-dot-0
Because ubuntu 19.04 and newer come with libssl-1.1.0, and there is no libssl-1.0.0 in the repositories.
Please answer the following, if applicable:
Have you been able to reproduce this issue with just the Firebase Unity quickstarts (this GitHub project)?
Sorry, I have not tried.
What's the issue repro rate? (eg 100%, 1/5 etc)
100%

Hi @Havard-SL,
I tested this using C++ library on desktop, Unity library on desktop and Unity library on Android and got the same output each time for my test: DataSnapshot { key = test, value = 3.14156 }.

Are you able to provide a screen shot of your firebase database console showing the data you have?
Are you able to use GetRawJsonValue and dump the correct value in json?

Thank you for your quick response, and sorry for my slow response!
First of all, I updated my firebase SDK to version 6.7.0, but the issue still persisted.
I am not sure if I implemented it correctly but GetRawJsonValue just gave me "2" in the debug log,
And lastly, weirdly enough, the log line I got was reading:
[pc_4] handleServerMessage d {"d":2,"p":"test"}

Thank you for trying to help me, I really appreciate it!

That message you replied with is the raw response Firebase gets over the wire. Thus it looks like the data stored in Firebase real time database is an integer not a double and thus not a problem with the SDK.  Please check the logic you use to save the values and ensure types are correct for storing floating point numbers (should be using double).

I have attached a picture of my firebase realtime database and unity side by side:

Here you can see that I have stored the variable as a float, and my only database rules are:
{
  "rules": {
    ".read": true,
    ".write": false
  }
}

I have no clue why this happens, any help would be appreciated!

Can you show us the code that you're using to set the value?
On Tue, Nov 19, 2019, 6:44 AM Havard-SL<EMAIL_ADDRESS>wrote:

I have attached a picture of my firebase realtime database and unity side
by side:
[image: bilde]
https://user-images.githubusercontent.com/55786766/69156080-2d2d0300-0ae3-11ea-8000-3a9ea9da4828.png
Here you can see that I have stored the variable as a float, and my only
database rules are:
{
"rules": {
".read": true,
".write": false
}
}
I have no clue why this happens, any help would be appreciated!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/firebase/quickstart-unity/issues/513?email_source=notifications&email_token=AAEBYXJX7KYR72BIX5JZSWDQUP3U7A5CNFSM4JNKFKF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEONWUY#issuecomment-555539283,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEBYXLDNDA3MBEHWUZ6K33QUP3U7ANCNFSM4JNKFKFQ
.

Hi @Havard-SL
Could you provide more logs?  Yo can find your Editor log here
https://docs.unity3d.com/Manual/LogFiles.html
Also, the snippet of code about how you call into database API would be very helpful.
Here is what I read from your screenshot.
There is a mysterious request 1 sent before the listen request.
Then there is a listen request 2
And the response for mysterious request 1 is received with value 2 at "test". This seems to trigger the listener with value 2 and removed the listen id.
When response for request 2 is received, it cannot do anything.  And I cannot see what the actual response message is from your screenshot.
I suspect you might did something like
ref.SetValueAsync(2);
ref.GetValueAsync().ContinueWith(task => {
  Debug.Log(task.Result);
});

So, please provide more information.

I am extremely sorry for the late response, but thank you all for trying to help!
I've been busy studying for a final, so I had to focus on some other things, but I would be happy to answer any questions now!!
@chkuang-g Ive made a gist of my Editor.log placed in my ~/.config/unity3d/ folder:
https://gist.github.com/Havard-SL/c7fa8d760ec403c4373c6315af63815f
The current code I'm using to access the realtime database right now is almost the same as the one in my original issue description:
using System.Collections;
using System.Collections.Generic;
using UnityEngine;

using Firebase;
using Firebase.Unity.Editor;
using Firebase.Database;

public class test: MonoBehaviour {
  void Start() {
    FirebaseApp.LogLevel = LogLevel.Verbose;
    FirebaseDatabase.DefaultInstance.LogLevel = LogLevel.Verbose;

    // Set thistask before calling into the realtime database.
    FirebaseApp.DefaultInstance.SetEditorDatabaseUrl("https://unity-test-9f7cc.firebaseio.com/");

    DatabaseReference reference = FirebaseDatabase.DefaultInstance.RootReference;
    Debug.Log("Aigt imma head in");
      FirebaseDatabase.DefaultInstance
      .GetReference("test")
      .GetValueAsync().ContinueWith(task => {
        if (task.IsFaulted) {
          // Handle the error...
          Debug.Log("Error");
        }
        else if (task.IsCompleted) {
          DataSnapshot snapshot = task.Result;
          // Do something with snapshot...
          Debug.Log(snapshot.GetRawJsonValue());
        }
      });
  }
}

This is almost directly copied from the Unity firebase starter guide, but including all changes people have suggested here.
If you want more screenshots I would be happy to share, but I dont know what part of the console output contains the relevant information!
I am very grateful for your help!
-Håvard

@Havard-SL
This is definitely odd.
For what it worth, we actually fixed whole load of database editor issues in 6.7.0.  Also 6.8.0 is out too.
https://firebase.google.com/support/release-notes/unity#version_670_-_november_13_2019
Could you try to download the latest version and see if that fixed your issue?
Also, I'll try to run your code with 6.6.0 next week and see what I can find.
Shawn

@chkuang-g
Thank you for informing me of the new update. However, it did not work. On the contrary I get two new errors:
Error: Could not load signature of Firebase.Editor.XcodeProjectModifier:get_Project due to: Could not load file or assembly 'UnityEditor.iOS.Extensions.Xcode, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' or one of its dependencies. assembly:UnityEditor.iOS.Extensions.Xcode, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null type:<unknown type> member:(null) signature:<none>

But as I'm not testing or planning to build this on iPhone, this is most likely irrelevant.
The other one:
Unloading broken assembly Assets/Firebase/Editor/Firebase.Editor.dll, this assembly can cause crashes in the runtime

I have no clue what this means. I did not see these in any of the previous firebase sdk versions.
I just thought I should mention them in case they were relevant to this problem.
Something I haven't mentioned previously, but could be useful is that i didn't have this issue previously, but it appeared after a while. The only thing I can think of that could have made a difference is a rouge config (however, I have this issue on two different machines, so it would be unlikely, but still possible), or the messing around with libssl.1.0.2 to sercumvent the above mentioned issues.
I work with a fellow student who runs arch linux, but he does not have this problem, on the other hand, since I run ubuntu, there should be more bug reports similar to mine, as it is a more popular distrobution.
Thank you for trying to help me!
-Håvard

@Havard-SL
Oh boy, that looks like a regression in 6.8.0.
Could you try 6.7.0 and see if that is fixed?
I'm trying to reproduce this on Linux machine.

Alright, tried to modify the quick-start  and change UIHandler.cs to call GetValue() like you did, and imported 6.6.0.  Got a solid 2.69.
    // Initialize the Firebase database:
    protected virtual void InitializeFirebase() {
      FirebaseApp app = FirebaseApp.DefaultInstance;
      StartListener();
      isFirebaseInitialized = true;

      FirebaseApp.LogLevel = LogLevel.Verbose;
      FirebaseDatabase.DefaultInstance.LogLevel = LogLevel.Verbose;

      FirebaseDatabase.DefaultInstance
      .GetReference("test")
      .GetValueAsync().ContinueWith(task => {
        if (task.IsFaulted) {
          // Handle the error...
          Debug.Log("Error");
        }
        else if (task.IsCompleted) {
          DataSnapshot snapshot = task.Result;
          // Do something with snapshot...
          Debug.Log(snapshot.GetRawJsonValue());
        }
      });
    }

I really wonder if were connected to the right database...
Could you try to do the same with quickstart and add your google-services.json to the project as well?

Thank you for your response, @chkuang-g !
I have reinstalled my entire operating system (Still ubuntu 19.10) and launched unity hub using a flatpak, so that I don't have installed libssl 1.0.2 manually as mentioned before, and it just worked fine (except for the lowermost error you can see on the picture below).
I tried changing the value in the database to 7.77 as you said, and got 7 as my output!

I used the same code as I wrote in my original post, but I can try to change the example code, like you did if you want!
If I put quotation marks around the values, I get the correct response:

Thank you!
-Håvard

I'll dig more about this issue with our RT DB backend.
At the meantime, in order to fix those error message you saw about "Unload broken assembly", we just release a patch 6.8.1 which should resolve that.  Not really related to your original issue though.

@Havard-SL
Happy new year and sorry for the late reply.
We had a hard time to reproduce the same issue on our Linux/Window/Mac machines.  This seems to be an unique issue to your machine since no other people has reported the same issue yet.  However, based on your log and our tests, we narrow down the potential place which was causing the issue.
Long story short, it does not seems to be a server issue but the problem when the client is parsing the data here.
https://github.com/firebase/firebase-cpp-sdk/blob/master/database/src/desktop/connection/connection.cc#L310
Since we cannot reproduce the issue, we would need your help to root the cause.  And the first step is to confirm our assumption.
Could you download this custom build FirebaseDatabase plugin, import it, run your game and paste the log here?
You should see some logs start with "JsonToVariant:" and "FlexbufferToVariant:".  Basically this custom build is just trying to log the message your editor received from the database server and print out the parsing process.
Thank you!
Shawn

Happy new year, @chkuang-g ! And thank you for sticking to this issue!
I made a new gist of the Editor.log after trying the new DLL in a new clean project, as just copying the logs from inside the unity editor proved extremely cumbersome:
https://gist.github.com/Havard-SL/211f5e913c5061d0c047de911155f972
I have also noticed that at the top of the log it still says "No usable version of libssl found", which is kind of weird considering I am using unityhub from a flatpak and the project runs fine (except for the bug, of course)
On the positive side there are a ton of those JsonToVariant and FlexbufferToVariant, so at least I imported the DLL correctly!
Thank you so much for helping, and if there is anything else I can do to help please inform me! :)

Hi @Havard-SL
Thanks for the log.  This confirms that something is wrong during the parsing.
https://gist.github.com/Havard-SL/211f5e913c5061d0c047de911155f972#file-editor-log-L4562
https://gist.github.com/Havard-SL/211f5e913c5061d0c047de911155f972#file-editor-log-L4674
We uses Flexbuffer, from Flatbuffer, to do the parsing.  Let me see what I can find.

Thank you so much, @chkuang-g and everyone else who helped!
Using export LANG=en_US.utf8 fixed the issue, since my current LANG was nn_NO.UTF8
I would never have expeced that to be the issue, thank you so much for helping!
Should I leave this issue open until a permanent fix is pushed?
Again, thank you so much for all your help, you're doing an amazing job!
-Håvard

Glad that it works for you.
Please leave this issue open.  We will close it once we release a patch for this.


Not working

me，too

This issue has been fixed on a fork by clauzewitz.
Use the version found here:
https://github.com/clauzewitz/scriptable-instagram-widgets
I believe this is the commit that fixed the issue:
https://github.com/clauzewitz/scriptable-instagram-widgets/commit/39215e0fc68fca3bd7a77544240406f2842c9bcb


Include a glossary with all jargon terms

To help users, it would be good to have a glossary.

Use the Quarto glossary extension https://debruine.github.io/quarto-glossary/


Revert "disable DebugInfo/async-args.swift"

Reverts apple/swift#36067
This isn't supposed to fail so let's see how it's failing.

@swift-ci test

We had a massive automerger delay of >5days that was resolved around the same time this was merged. I'm hoping that that's why it was broken.

Build failed
Swift Test Linux Platform
Git Sha - 8905b2ab50e52be72812ca7163e750cfc2557f9a

Build failed
Swift Test OS X Platform
Git Sha - 8905b2ab50e52be72812ca7163e750cfc2557f9a

Completely unrelated test failure.

@swift-ci test

Build failed
Swift Test Linux Platform
Git Sha - 8905b2ab50e52be72812ca7163e750cfc2557f9a

@swift-ci test and merge


Change immutable and stable section for Function Volatility

Here http://postgrest.org/en/v5.2/api.html#immutable-and-stable-functions. We get a lot of questions regarding errors when executing in read-only transactions https://github.com/PostgREST/postgrest/issues/1379, https://gitter.im/begriffs/postgrest?at=5d51e160029a51607f82142b.
Make clear POST allows VOLATILE functions.

I believe this is much clearer now https://postgrest.org/en/stable/references/transactions.html


⚠ Bofrost.de has degraded performance

In bc2726b, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 2365 ms

Resolved: Bofrost.de performance has improved in d90602b after 10 minutes.


getPeople.set doesn't work sometimes

We are using the 1.3.5 library in our client app, and we have discovered an issue recently where some of the users are missing properties, after calling mixpanel.identify and then mixpanel.getPeople.set to set the properties. The issue only happens sometimes, on IOS and Android. We suspect that there might be an issue with race condition between the calls, or something of that sort.

Hi @MariaTolstov , this might be caused by a race condition. We released v2.3.0 which adds support for returning Promise for the identify(). Now you can do something like this
     mixpanel.identify('Unique User ID').then(() => {
       // mixpanel.getPeople.set...
    });

Please try and feel free to reopen if the problem still exists.


RetryError When I ask a question to pentestgpt

pentestgpt
Your CHATGPT_COOKIE is not set. Please set it in the environment variable.
Your GOOGLE_API_KEY is not set. Please set it in the environment variable.
Your GOOGLE_API_KEY is not set. Please set it in the environment variable.
Welcome to pentestGPT, an automated penetration testing parser empowered by GPT.
The settings are:

parsing model: gpt-4o-2024-05-13
reasoning model: gpt-4o-2024-05-13
use API: True
log directory: logs
Do you want to continue from previous session? (y/n) n
ChatGPT Sessions Initialized.
Please describe the penetration testing task in one line, including the target IP, task type, etc.

API Testing
Traceback (most recent call last):
File "/Users/rahulbhor/Documents/pentestgpt/lib/python3.10/site-packages/tenacity/init.py", line 478, in call
result = fn(*args, **kwargs)
File "/Users/rahulbhor/Documents/pentestgpt/lib/python3.10/site-packages/pentestgpt/utils/llm_api.py", line 268, in send_message
conversation = self.conversation_dict[conversation_id]
KeyError: None

The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/Users/rahulbhor/Documents/pentestgpt/bin/pentestgpt", line 8, in
sys.exit(main())
File "/Users/rahulbhor/Documents/pentestgpt/lib/python3.10/site-packages/pentestgpt/main.py", line 62, in main
pentestGPTHandler.main()
File "/Users/rahulbhor/Documents/pentestgpt/lib/python3.10/site-packages/pentestgpt/utils/pentest_gpt.py", line 737, in main
self.initialize(previous_session_ids=loaded_ids)
File "/Users/rahulbhor/Documents/pentestgpt/lib/python3.10/site-packages/pentestgpt/utils/pentest_gpt.py", line 266, in initialize
self._feed_init_prompts()
File "/Users/rahulbhor/Documents/pentestgpt/lib/python3.10/site-packages/pentestgpt/utils/pentest_gpt.py", line 193, in _feed_init_prompts
_reasoning_response = self.reasoningAgent.send_message(
File "/Users/rahulbhor/Documents/pentestgpt/lib/python3.10/site-packages/tenacity/init.py", line 336, in wrapped_f
return copy(f, *args, **kw)
File "/Users/rahulbhor/Documents/pentestgpt/lib/python3.10/site-packages/tenacity/init.py", line 475, in call
do = self.iter(retry_state=retry_state)
File "/Users/rahulbhor/Documents/pentestgpt/lib/python3.10/site-packages/tenacity/init.py", line 376, in iter
result = action(retry_state)
File "/Users/rahulbhor/Documents/pentestgpt/lib/python3.10/site-packages/tenacity/init.py", line 419, in exc_check
raise retry_exc from fut.exception()
tenacity.RetryError: RetryError[<Future at 0x1083795a0 state=finished raised KeyError>]

Looking into this now.

@violinist2149 Did you link a payment method to your OpenAI account? Can you validate if you can successfully request the OpenAI API?

┌──(root㉿xxxx)-[~]
└─# pentestgpt-connection
You're testing the connection for PentestGPT v"0.14.0"
Test connection for OpenAI api (GPT-3.5)
New conversation.xxxxxxxxxx-00155d2c852f is created.

You're connected with OpenAI API. You have GPT-3.5 access. To start PentestGPT, please use <pentestgpt --reasoning_model=gpt-3.5-turbo-16k>

Test connection for OpenAI api (GPT-4)
New conversation.xxxxxxxx-xxxx-00155d2c852f is created.

You're connected with OpenAI API. You have GPT-4(o) access. To start PentestGPT, please use <pentestgpt --reasoning_model=gpt-4o>

┌──(root㉿xxxx)-[~]
└─# pentestgpt --reasoning_model=gpt-4o
Your GOOGLE_API_KEY is not set. Please set it in the environment variable.
Your GOOGLE_API_KEY is not set. Please set it in the environment variable.
usage: pentestgpt [-h] [--log_dir LOG_DIR] [--reasoning_model {gpt-4,gpt-4-turbo}] [--parsing_model {gpt-4-turbo,gpt-3.5-turbo-16k}] [--logging] [--useAPI]
pentestgpt: error: argument --reasoning_model: invalid choice: 'gpt-4o' (choose from 'gpt-4', 'gpt-4-turbo')

@violinist2149 Did you link a payment method to your OpenAI account? Can you validate if you can successfully request the OpenAI API? A simple debug is to use pentestgpt-connection.

@GreyDGL It's working now after linking a payment method . Thanks for your help !


BYE is not sent for calls over websocket

This may be related to #143.
We are trying to implement a websocket server, so browsers connect to libre via websocket.
Responses to an INVITE get sent just fine, but a BYE after 200 OK does not.
When I step through the code, what happens is that in sip_request_send(), because the "somethingsomething.invalid" host that I see used with websockets is neither an IP address nor a real host that can be looked up,  the first if that performs the request immediately is not entered, and dnsc_query() ends up being called but returns an error. So no BYE gets sent at all.
I haven't tried yet, but I suspect making calls to a websocket client will fail as well because the INVITE won't find its way to the already connected client.
At the moment I'm reading the code and the RFCs trying to undertand how it all should work, but this is quite complex and I haven't been able to come up with a quick fix for this. It seems websocket support is missing in this corner of the library, especially the websocket server side?
Anyway, what I think needs to happen in general is that the code must notice that it's a websocket address, and then consult the table of connected websocket clients to find the client and its connected socket.

please note that SIP over Websock should be considered "Work in progress".
It is not production quality.
Can you please provide some logs for your setup ?


terms-and-conditions page on Enbed

add terms-and-conditions page for google cloud  wromo-com-153559 [Action Needed] by Google Cloud Platform.
google cloud cannot confirm two privacy-policy and my-account pages and we also add  terms-and-conditions/ to remain stable pages / for google clouds OAuth API

page/my-account in php script or it is also possible in .node js with mongoDB backend


Update JobsManager to watch App_Data folder

If we set up FileSystemWatcher to watch App_Data\jobs\continuous, it will hold the handler to App_Data\jobs\continuous. When we try to delete App_Data\jobs, it may block the deletion. It usually happens when WebDeploy tries to clean up App_Data folder.
The change sets up FileSystemWatcher to watch App_Data folder, it hold the handler to App_Data folder and still includes the sub directory changes.
@davidebbo @pharring @iusafaro

@northtyphoon,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

One mitigation is that we don't do the FileSystemWatcher at all if there are no WebJobs. So any high notification situation is limited to sites that have both WebJobs and App_Data that they actively write to.

@davidebbo  We don't do FileSystemWatcher if there is no jobs folders initially.  Instead, we have a timer to check if jobs folders (wwwroot/app_data/jobs/triggered or wwwroot/app_data/jobs/continuous) exists before starting FileWatcher.   Vice versa, when the folder (or any of its parent folders) is deleted, we get an OnError event and stop watcher accordingly.
@northtyphoon The issue is the race between deleting parent folder and an OnError event stopping the watcher.  If one were to retry deleting the parent folder again, it would succeed.
The concern for the fix is (as @davidebbo pointed out) duplicated watchers on app_data folder.  Both job managers will get noises from the others; though, the code should filter them properly.   In addition, any unknown regression that I can't yet think of.
Given the scenario is limited to clean up (anything else?), I wonder patching the web deploy to retry on deleting failure would be a proportional solution for the issue (less invasive than changing how Kudu listens to file changes).

@suwatch For your comment, "The issue is the race between deleting parent folder and an OnError event stopping the watcher." It made me think OnError event handler code should immediately dispose FileSystemWatcher to release the file handler instead of queuing a task.
BTW: Since the change watches App_Data, OnError event is only raised when deleting App_Data folder.
@EricSten-MSFT, what do you think of "patching web deploy to retry on deleting failure"?

It made me think OnError event handler code should immediately dispose FileSystemWatcher to release the file handler instead of queuing a task.

@northtyphoon Looking at the hostory, the queued task was done intentionally.   Besides, the event is likely async and we will still have a race.

We decided to hold the change and ask users to exclude the profiler web jobs from web deploy clean up task.


Multiple modules throwing Multiple files found error.

Please provide us with the following information:

OS && Version
Mac OSX El Capitan
angular-cli: 1.0.0-beta.15
node: 6.6.0
os: darwin x64
Repro steps. Was this an app that wasn't created using the CLI? What change did you
do on your code? etc.
I have a module that is exporting all of my component modules (vdl.module.ts) and another module(app.module.ts) that is actually my bootstrapped demo app.  index.ts is only pointing to the app.module. The demo of the component library uses the app.module.  Trying to run ng serve throws the below error.
The log given by the failure.

Error locating module for declaration
        SilentError: Multiple module files found:

I think most component libraries will follow this pattern is there a way to get around the error?

Looking at the code, it looks like you need to put vdl.module.ts in a separate folder. app.module.ts should be the only module in the root src directory, other modules should be in a separate folder named after the module.

Update to beta.16 and you should be good to go.
I was having the same issue when trying to generate  a new component from root folder.
In my case, the modules were:

app.module.ts
app-routing.module.ts
both generated by the cli, and located in src/app ...

After updating (see how here ), it now works as expected without having to move the additionnal module file in separate folder.

@tinesoft I'm on beta-21 and I want to do exactly what you said: in the src directory I want to have:

app.module.ts
app-router.module.ts

I can't. When I'm trying to generate a new component, I get an error
Error locating module for declaration
	SilentError: Multiple module files found:

Hi @Olgagr ,
Did you upgrade to beta-21 from a previous version of the cli?
if yes, make sure you followed steps provided in the Updating Angular-CLI Guide .
A quick look  your  in  file: <YOUR_PROJECT_FOLDER>/node_modules /angular-cli/package.json  can confirm that you are indeed using the right version of the cli (and not still referencing an old one with the bug).

@tinesoft Thanks for answer. I think I'm using correct version:
In my project folder:
ng version
angular-cli: 1.0.0-beta.21
node: 6.8.1
os: darwin x64

In my project folder/node_modules/angular-cli/package.json:
"version": "1.0.0-beta.21"

That's weird,
Can you post your app.module.ts and app-router.module.ts files?
Also, beta-22-1 is out since a few hours, maybe you can give it a try.

@tinesoft Sure. These are my modules:
app.module.ts
import
{ BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';
import { FormsModule, ReactiveFormsModule } from '@angular/forms';
import { HttpModule } from '@angular/http';
import { StoreModule } from "@ngrx/store";

import { AppComponent } from './app.component';
import { LoginComponent } from './public-pages/login/login.component';
import { AuthService } from "./common/services/auth.service";
import { rootReducer } from "./common/reducers/root.reducer";
import { StoreDevtoolsModule } from "@ngrx/store-devtools";
import { ApiHttpService } from "./common/services/api-http.service";
import { CompaniesComponent } from './companies/companies.component';
import { AppRouterModule } from "./app-router.module";

@NgModule({
  declarations: [
    AppComponent,
    LoginComponent,
    CompaniesComponent
  ],
  imports: [
    BrowserModule,
    FormsModule,
    ReactiveFormsModule,
    HttpModule,
    StoreModule.provideStore(rootReducer),
    StoreDevtoolsModule.instrumentOnlyWithExtension(),
    AppRouterModule
  ],
  providers: [AuthService, ApiHttpService],
  bootstrap: [AppComponent]
})
export class AppModule { }

app-router.module.ts
import {NgModule} from "@angular/core";
import {Routes, RouterModule} from "@angular/router";
import {LoginComponent} from "../public-pages/login/login.component";
import {CompaniesComponent} from "../companies/companies.component";

const routes: Routes = [
  {path: '', pathMatch: 'full', component: LoginComponent},
  {path: 'companies', component: CompaniesComponent}
];

@NgModule({
  imports: [RouterModule.forRoot(routes)],
  exports: [RouterModule],
  providers: []
})
export class AppRouterModule {}

They are pretty basic, to my mind.
I'll also try beta-22-1 as you recommend.

@tinesoft Ok, I know what is going on. I've checked @bonnici referenced to and it looks like my router module has to be in file called routing.module.ts. When I changed the file name, I didn't have problems with generating component any more. I think this is not obvious. Do we have any docs about it ? Maybe we should add it ?

I did notice you called your routing file app-router.module.ts instead of app-routing.module.ts as illustrated in most Angular Routing-related docs & examples on angular.io, but i never thought that could be the issue...
Good to know!
Maybe this will no longer matter when generating Routing from the CLI is re-activated again, as the tool with take care of naming the file appropriately.

This issue is happening to me all of a sudden in my project https://github.com/MohamadAtieh/angular2-dash
I am not sure why, but I can't generate anything although I was able to before. I have two modules in the app directory, but they are named differently (app.module.ts and nav.module.ts)
I think this happened to me after adding the nav.module.ts as this was the last thing generated by the cli.

That's what I was about to recommend you!


Two different versions of a dependency (direct + transitive) breaks dev build

It appears that if you have two different versions of a package in your dependency tree and a file that uses both versions (one directly, one indirectly), then the dev build will resolve all references using a single version during prebundling, instead of using the locally correct version for each bundle.
I didn't see any config options that would address this, let me know if I'm missing something obvious!
Steps to reproduce

Scaffold a Vanilla project with npm init @vitejs/app
npm install && npm install<EMAIL_ADDRESS><EMAIL_ADDRESS>Replace main.js with:

import { min } from "d3-array";
import { tidy, groupBy } from "@tidyjs/tidy";

console.log(min([1, 2, 3]));
console.log(
  tidy(
    [1, 2, 3],
    groupBy(d => d % 2, [], groupBy.entries())
  )
);

Run npm run dev

More info
In this case your package.json has:
"dependencies": {
  "@tidyjs/tidy": "2.3.0",
  "d3-array": "1.2.1"
}

So you end up with the installed dependencies:
├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>
When your main.js contains something like:
import { min } from "d3-array";
import { tidy, groupBy } from "@tidyjs/tidy";

then npm run dev will produce errors when trying to prebundle tidy:
> node_modules/@tidyjs/tidy/dist/es/groupBy.js:1:9: error: No matching export in "node_modules/d3-array/src/index.js" for import "group"
    1 │ import { group } from 'd3-array';

This is seemingly because it's using the direct dependency version of d3-array<EMAIL_ADDRESS>instead of the version that tidy depends on (d3-array^2.9.1), even though both are installed.
In this case the failure is obvious because the exported API of d3-array changes in v2, but this could also fail more insidiously since two different versions could have the same named exports but different internal behavior, so then the difference would only show up at runtime.
Note: I couldn't reproduce this same issue using esbuild directly, so the issue seems specific to the way in which vite is using it.

Also present in 2.3.8

@patak-js can you clarify why this was closed? From my read of the two PRs (#3753 and #4019) it seems like a fix was tried but then reverted.

Thanks @veltman, looks like GitHub interpreted from the description that this should be closed. As you said, a fix had to be reverted because of regressions. Another solution is required here.


Debug on mobile

Nowadays, most web is mobile-first and I didn't make much effort to check if my blog looks good on the phones yet.

Moving to theme.


Follow-up of #190 - Memory efficient request

The following pattern would keep weakref of  SubmissionOnCVFold which will load into memory the prediction arrays.
submissions = [get_submission_by_id(session, sub[o])
               for sub in get_submissions(session, 'iris_test', state='scored')]
for sub in submissions:
    for cv_fold in sub.on_cv_folds:
        ... # for instance get_scores, get_time, etc.

If submissions contains submissions then, the predictions arrays will be kept. We allievate the issue with #221 by avoiding to have submissions in memory and the arrays for all submissions.
However, there is a better job to be done. Getting the score, time, or memory info should not require to load the array. In facts, these info are stored in SubmissionScoreOnCVFold. Therefore, we could make a memory/speed efficient query avoiding to load the arrays:
    submission = get_submission_by_id(session, submission_id)
    results = defaultdict(list)
    for fold_id, cv_fold in enumerate(submission.on_cv_fold):
        results['fold'].append(fold_id)
        for step in ('train', 'valid', 'test'):
            results[step].append(getattr(cv_fold, '{}_time'.format(step)))
    return pd.DataFrame(results).set_index('fold')

for step in ('train', 'valid', 'test'):
    times_per_fold = session.query(getattr(SubmissionOnCVFold, '{}_time')).filter(SubmissionOnCVFold.submission_id == submission_id).all()
    for fold_id, times in enumerate(times_per_fold):
        results['fold'].append(fold_id)
        results[step].append(times)
    return pd.DataFrame(results).set_index('fold')

I tried this:
    results = defaultdict(list)
    for step in ('train', 'valid', 'test'):
        times_per_fold = session.query(
            getattr(SubmissionOnCVFold, '{}_time'.format(step))).filter(
            SubmissionOnCVFold.submission_id == submission_id).all()
        for fold_id, times in enumerate(times_per_fold):
            results['fold'].append(fold_id)
            results[step].append(times)
    return pd.DataFrame(results).set_index('fold')

The return statement throws a ValueError("arrays must all be same length")

OK, done. The get_time was easy, get_scores not so much. Both work lightning fast now. https://github.com/paris-saclay-cds/ramp-board/pull/276/commits/c42d7ebc3f7dc59d18918f27a5a5be526e7e509c

The following pattern would keep weakref of SubmissionOnCVFold which will load into memory the prediction arrays.

I'm not sure I understood the underlying issue correctly, but isn't this related to the fact that we want to specify (or exclude) columns when querying, including for foreign keys? If so wouldn't using sqlachemy deferred option help?
We could also add delayed in the model definition for all large sized fields. I don't think it affects the DB, it must be a sqlalchemy thing.

Actually it looks like defer is what we want. Let me check if it would work. I am not sure it will be good enough because we are dealing with backref which give a list on which we will iterate. But let see.

It works perfectly:
    all_cv_folds = (session.query(SubmissionOnCVFold)
                           .filter_by(submission_id=submission_id)
                           .options(defer("full_train_y_pred"),
                                    defer("test_y_pred"))
                           .all())
    for fold_id, cv_fold in enumerate(all_cv_folds):

I spent to much time doing useless stuff, a pity that I don't know anything about ORM :)

@rth thanks

Gread that it works. No  -- it's that sqlalchemy adds a lot of complex instructions on top of "SELECT columns from table"..


fix: use links for sept-ember censer, hulk is once-per-day

Most of these switches have no tests. Some in UseItemRequest have tests, but normally those that have slightly more involved logic than just setting a pref on use (i.e. there is a test for the presence of a string)
There isn't really any logic here, so the tests would be something like "did I write what I wrote", so I didn't write any -- I just checked in the browser manually.


libinput: 1.2.1 -> 1.2.2, propagate udev dependency

Things done:

[x] Tested using sandboxing (nix-build --option build-use-chroot true or nix.useChroot on NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

What exactly does it mean to move it from a build input to a propagatedbuild input? Just for my own learning/understanding? Thanks. (Looks good to me otherwise.)

Propagating it makes udev available to packages that depend on libinput. Otherwise a package that depends on libinput will also need an explicit dependency to udev.


feat: add vscode frontend feature for new amalthea

@rokroskar this is how we can use features to inject frontends into our sessions.
I am pretty sure this will work. I am not sure how to test this without fully publishing the feature though.

Ah the problem is that the entrypoint field in the devcontainer feature spec does not get used in the image. I thought it will just override the entrypoint of the image that was built but it does not. It only gets executed when you start things with the devcontainer cli.


getRecentlyPlayed does not brings the game if it's part of a collection

In case you played some game that it's part of a bundle like Devil May Cry HD Collection or NARUTO SHIPPUDEN™: Ultimate Ninja® STORM TRILOGY, the game specific game that you played from the bundle does not apears in the return, this function just brings the collection info.

@leandroSalesCotrim there's no way to do this because the API doesn't report the Collection as individual games. Correct me if I'm wrong but neither the console, nor the PS App show this as separate games, do they?

i understand, but in PS4 (probably ps5 and ps app too) i can see exactly the same list retrieved in my profile, but when i click in a game that is a bundle/collection, it bring me the trophy list of all games from the bundle, it seems that only don't bring me the games that i didn't started from collection, so it doesn't show in the bundle list.
I thought this information was in API too, but if doesn't, it should be something internal data from sony that's not in the api or part from their algorithm

In that case you're probably looking for titles, rather than games. The API has 2 endpoints, trophyTitles and games.
https://m.np.playstation.com/api/trophy/v1/users/6462910331343535058/trophyTitles this should spit individual trophy lists while this https://m.np.playstation.net/api/gamelist/v2/users/6462910331343535058/titles?limit=300&offset=0 will give you the bundle, most likely.
The mapping will have to be handled by you though, as I'm not aware of the API providing this. It should be fairly trivial though.
I've done this on games.directory ( apologies for the plug ) . You need to use npCommunicationId and title_id to map them.

Thanks!! i didn't knew about the gamelist endpoint, this will help me a lot to map in my project!


Show date on the chatApp UI

Currently chatApp only shows the time at which a message was sent. We need a feature which also shows date at which message was sent.
Preferably not just appended to the time string, but categorised messages by a pseudo horizontal ruler, somewhat like WhatsApp/Telegram/Instagram

hi @osBins , can I work on this issue?

Hi @PrakritiRaw , thank you for taking interest in this issue, I have assigned it to you! Do let us know if you face any issue.

Hi @PrakritiRaw, do we have an update on this?

Unassigning @PrakritiRaw because of lack of response/updates.

hi @osBins , Id like to work on this issue.

@DragoVeizen assigned

@DragoVeizen any updates?

not yet
busy with exams

@PrimalPimmy Hey I want to work on this issue

@PrimalPimmy you can unassign me and assign this issue to @Rithvik-padma


Wrong OAuth2 Form target when running on modified root URL

Gitea version (or commit ref): v1.9.4
Git version: 2.22.0
Operating system: gitea/gitea on Docker on Ubuntu 18.04.3 LTS
Database (use [x]):

[x] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[x] No (because its root matches the server root)
[ ] Not relevant

Log gist: https://gist.github.com/PeterNerlich/275d199733c38d2aee8a607b5d7bf84a

Description
I have set gitea up in docker behind a reverse proxy (Traefik). We are not given subdomains so we have to work with prefixes like /git/. When trying to integrate drone into our setup, granting authorization to it fails. I think I traced it down to the "grant or cancel" form action url leading to /login/oauth/grant instead of /git/login/oauth/grant. Manipulating the HTML and clicking the button then worked.
Screenshots

Looking at code I don't see anything wrong, have you set ROOT_URL in app.ini right?

I have the same problem (reported in #8466 which I closed now again). My config is
ROOT_URL = https://example.com/repo/

but the POST also goes to the base (https://example.com/login/oauth/grant)
I also noted this on the configuration page (e.g. https://example.com/repo/user/settings/applications/oauth2/1)

I'm also experiencing this on Drone. The URL redirect forgets the /git prefix

The problem is here:
https://github.com/go-gitea/gitea/blob/dbd9d8dd54fd3b0ff7b02ae7b7da8369654e3725/templates/user/auth/grant.tmpl#L19
If you change that line to:
https://github.com/go-gitea/gitea/blob/e9ac23ceb562e1badaed7dd476096fa3594b7636/templates/user/auth/grant.tmpl#L19
The problem should be fixed.
You can either wait for #8647 to be merged, or if you can't use 1.11 you should be able to make a custom version of the user/auth/grant.tmpl with this fix.


kata_agent: Support CRI-O with overlay

This pull request enables CRI-O to work with Kata Containers in case the storage driver used is overlay, meaning we rely on 9pfs to pass the rootfs inside the VM.

@chavafg could you check if you get CRI-O working for Kata with this PR ? Only with overlay.

LGTM

lgtm


When will the training code be available?

Hi there!
Thank you for your work and congrats on the great results!
I know everyone hates this question, but we would like to evaluate your work to cite it in our paper, so could you give a hint how long the publication of the training code will still take? :D
Thank you!

Hi there! Thank you for your work and congrats on the great results! I know everyone hates this question, but we would like to evaluate your work to cite it in our paper, so could you give a hint how long the publication of the training code will still take? :D Thank you!

Now I have submitted the revision, and I will release the train code as soon as possible after the review.

Hi there!
Any news or updates about the revision?

+1

+1

Hi @flyinghu123, thanks for the great paper!
Btw, could we know, will there be a released training code in the near future? thank you~

Hi there!
Thank you for your work and congrats on the great results!
I know everyone hates this question, but we would like to evaluate your work to cite it in our paper, so could you give a hint how long the publication of the training code will still take?
Thank you!


Route [admin.servergateway.index] is not defined` error by creating CRUD with Tomato/PHP

Hello.
Unable to generate CRUD. When I try to generate my first CRUD by following this link: https://docs.tomatophp.com/get-started/start-your-first-crud.
But After create and make servergateway migration, I add in app\Providers\AppServiceProvier, this following in its boot method:
use TomatoPHP\TomatoAdmin\Facade\TomatoMenu;
use TomatoPHP\TomatoAdmin\Services\Contracts\Menu;

...

public function boot()
{
    TomatoMenu::register(
        Menu::make()
            ->group('Resources')
            ->label('Users')
            ->route('admin.servergateway.index')
            ->icon('bx bx-user')
    );
}

I get Route [admin.servergateway.index] is not defined error.
Does Documentation about How to create a first CRUD is really complete ???
Otherwise, please help me to fix that error and succeed my CRUD's creation.
Awaiting your reply.
Thanks.

TomatoMenu add a menu to side menu with the route name and before generate this route not exists and it's a laravel route error not Tomato, so please make a generate first and then add your menu to the provider

I don't understand clearly.

Or do I just need to follow this link: https://docs.tomatophp.com/tomato-admin/generate-crud and forget adding to provider ???

you need to generate the CRUD first than add to the provider.


Lagged hyperparameters check and correct

The function of changing the lagged transformation hyperparameter depending on the length of the time series was implemented.

Hello @Dreamlone! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file examples/ts_forecasting_problem_small_ts.py:

Line 152:1: W391 blank line at end of file


[W5][W10-2] Shune Lei Yee Tun

Enhanced Find Command to be able to find persons by tags

should include a system test, i.e. change the input and expected output files to reflect your new functionality


c2patool fails to extract all x509 certs

"c2patool --certs" is supposed to extract the x509 certificates.
While this does extract everything in the primary x5chain, it doesn't extract the certs from sigTst tstTokens (used for validating the ta_url signature).

As designed


Free thread-local OpenSSL state on thread exit

OpenSSL 1.0.x automatically allocates a per-thread error queue as needed, but requires that the application call ERR_remove_thread_state() when terminating a thread to prevent the memory from leaking. As the Go runtime may create and terminate threads arbitrarily, the amount of memory leaked has the potential to grow unbounded.
Clean up the OpenSSL error queue for a thread upon thread exit. Use the native threading APIs to arrange a callback on thread exit as the Go runtime does not provide any similar facilities itself.
No explicit thread-exit handling is needed for OpenSSL 1.1.0 and above as it automatically deallocates thread-local resources without application assistance. See the OPENSSL_thread_stop(3) man page for more information.

cc @ueno


Clean test translator

Proposed changes
Most of the translator tests can be used for both crate and timescale. This PR put it common part of the
mentioned translator tests.
Following bugs have been detected thanks to that:

timescale/postgis add additional properties to geo:json (fixed)
Relationship was not handled correctly in timescale

Types of changes
What types of changes does your code introduce to the project: Put
an x in the boxes that apply

[x] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)

Checklist
Put an x in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to
ask. We're here to help! This is simply a reminder of what we are going
to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA
[x] I have added tests that prove my fix is effective or that my
feature works
[x] I have added necessary documentation (if appropriate)
[x] Any dependent changes have been merged and published in
downstream modules

excellent work, ready to merge...


SimulationTrialResult usability

I'm always baffled by the members of this class. If you do a wavefunction simulation you need result.final_state but if you do a density matrix simulation you need result.final_density_matrix.
The state vector / wavefunction terminology rears its head when you're trying to use PauliString.expectation_from_xxx
term.expectation_from_wavefunction(result.final_state)
term.expectation_from_density_matrix(result.final_density_matrix)

Is your main issue with the naming?  i.e. is #2143 your beef?

Yes, closing as duplicate


fix anchor [object Object] tag in args

these can be unfurled further

Gonna push this, definitely kind of annoying, but schema browsing isn't of as much interest as some other items we have, and we need to do some chewing on how we integrate the Anchor schema page with the rest of what we've been adding or want to add


Virtual environment not recognized

Environment data

VS Code version: 1.27.2
Extension version (available under the Extensions sidebar): 2018.8.0
OS and version: Debian 0.5
Python version (& distribution if applicable, e.g. Anaconda): Anaconda Python 3.7
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
Relevant/affected Python packages and their versions: vscode-python

Actual behavior
In my workspace I have created an environment with python -m venv .venv/, then reloaded VSCode. I open the command palette and click Python: Select Interpreter and new environment is not present.
Expected  behavior
Acording to https://code.visualstudio.com/docs/python/environments#_where-the-extension-looks-for-environments the extension looks for environments inside the workspace, but this beaviour is not working.
I know I can manually set the python path in python.pythonPath.

It's possible the extension is still in the process of discovering the interpreters. Please could you reload vscode and wait for around 20 seconds before trying.
If that falls, please wait 5 minutes and try once again.

Solved, I was being impatient. Also noticed that if venv folder is two levels down it is not recognized. For example:
This won't work
.
├── backend
│   ├── .venv
│   ├── app.py
│   └── Dockerfile
└── docker-compose.yml

Working dir must be backend
.
├── .venv
├── app.py
└── Dockerfile

I guess this is the expected behavior, but it would be nice to work in both cases. So this would

Changing status accordingly

Scanning for a virtual environment an extra level below your workspace is costly and not our recommended practice. So our recommendation is to either set python.pythonPath (as you know), or use multi-root workspaces.


Adds sendPasswordResetEmail to firebase-auth.

Better solution is to rebase

@bennypowers Hi I can't really rebase this as this branch only edits the storage functionality. You can go to the original polymerfire to ask for a pull request. Closing this


[ENH] Calendar Feature Extractor

Is your feature request related to a problem? Please describe.
I would like to use sktime in the context of tree based models for time series. In general, these models need some data preparation to make them useful for time series. One data prepation step involves creating calendar dummy features representing the current day of the year, day of the month, week of the quarter etc. Another data preparation step would involve generating features representing fourier terms of different order and periodicity.
Describe the solution you'd like
I have been thinking about the best way to implement this, and @aiwalter  suggested to use an SeriesToSeries Transformer to generate new exogeneous features based on the index in ForecastingPipeline. Would that approach work from an architecture point of view, or do we need a separate not yet defined class "FeatureExtractor" and / or a specific IndexToSeries Generator?
We could either try to adapt solutions from GluonTS (dummies) / Prophet (fourier features) or build our own approach. Attached is some example code (not yet adapted to sktime) to outline the general goal.
import pandas as pd
import numpy as np

base_seasons = [
    ["parent","child","period","dummy"],
    ["year","year",None,"year"],
    ["year","quarter",365.25/4,"quarter"],
    ["year","month",12,"month"],
    ["year","week",365.25/7,"week_of_year"],
    ["year","day",365.25,"day_of_year"],
    ["quarter","month",12/4,"month_of_quarter"],
    ["quarter","week",365.25/(4*7),"week_of_quarter"],
    ["quarter","day",365.25/4,"day_of_quarter"],
    ["month","week",365.25/(12*7),"week_of_month"],
    ["month","day",30,"day"],
    ["week","day",7,"day_of_week"],
    ["day","hour",24,"hour"],
    ["hour","minute",60,"minute"],
    ["minute","second",60,"second"],
    ["second","millisecond",1000,"millisecond"]
]

base_seasons = pd.DataFrame(base_seasons[1:],columns=base_seasons[0])

base_seasons["fourier"] = base_seasons["child"] + '_in_' + base_seasons["parent"]
base_seasons["child"] = base_seasons["child"].astype("category").cat.reorder_categories(['year','quarter','month', 'week','day',"hour","minute","second","millisecond"])
base_seasons["rank"] = base_seasons["child"].cat.codes

def get_supported_seasons(base_frequency,base_seasons=base_seasons):
    rank = base_seasons.loc[base_seasons["child"]==base_frequency,"rank"].max()
    matches = base_seasons.loc[base_seasons["rank"]<=rank]
    if matches.shape[0] == 0:
        raise ValueError("Seasonality or Frequency not supported")
    return matches

def calendar_fourier(dti_actual,fourier_period,fourier_order,base_frequency):
    dti = pd.date_range(dti_actual.min(),dti_actual.max(),freq=base_frequency.upper()[0])

    if dti.min().to_numpy() != dti_actual.min().to_numpy():
        raise ValueError("Actual time Series does not correspond to frequencies provided by pandas Datetimeindex. This can happen when e.g. monthly data does not correspond to month end.")

    funcs = [np.sin,np.cos]

    outlist = list()
    for index,item in enumerate(fourier_order):
        outlist.append((np.arange(item)+1)*1/fourier_period[index])

    inlist = np.zeros(shape=(len(dti),np.concatenate(outlist).shape[0]*len(funcs)))
    colnames = list()
    k = 0
    for item in outlist:
        for index,p in enumerate(item):
            for func in funcs:
                inlist[:,k] =func(2*np.pi*p*np.arange(len(dti)))
#                colnames.append("per"+ str(int(1/p)*int(index+1)) + "_or" + str(int(index+1))+func.__name__)
                colnames.append("per"+ str(int(1/p)) + func.__name__)
                k = k +1

    inlist = pd.DataFrame(inlist)
    inlist.columns = colnames
    inlist.set_index(dti,inplace=True)

    inlist = inlist[inlist.index.isin(dti_actual)]
    inlist = inlist.reset_index(drop=True)
    return inlist

def calendar_dummies(x,funcs):
    if funcs == "week_of_year":
        return pd.DataFrame({funcs:getattr(x,"isocalendar")()["week"].reset_index(drop="date")})
    elif funcs == "week_of_month":
        return  pd.DataFrame({funcs:(x.day - 1) // 7 + 1})
    elif funcs == "month_of_quarter":
        return pd.DataFrame({funcs:(np.floor(x.month/4)+1).astype(np.int64)})
    elif funcs == "week_of_quarter":
        year_week = getattr(x,"isocalendar")()["week"]
        def week_of_quarter(x):
            if x <= 13:
                return 1
            elif x <=26:
                return x-13
            elif x <=39:
                return x-26
            elif x <=53:
                return x-39
        year_week.apply(lambda x: week_of_quarter(x))
    elif funcs == "millisecond":
        return  pd.DataFrame({funcs:x.microsecond*1000})
    elif funcs == "day_of_quarter":
        quarter = x.quarter
        quarter_start = pd.DatetimeIndex(
        x.year.map(str) + "-" + (3 * quarter - 2).map(int).map(str) + "-01")
        values  = ((x - quarter_start) / pd.to_timedelta("1D") + 1).astype(int)
        return pd.DataFrame({funcs:values},dtype=np.float64)
    else:
        return pd.DataFrame({funcs:getattr(x,funcs)})

def calendar_other(x,funcs):
    if funcs == "proportion_total":
        values = 1+(x.view(np.int64)-x.view(np.int64).max())/(x.view(np.int64).max()-x.view(np.int64).min())
        return pd.DataFrame({funcs:values},dtype=np.float64)
    elif funcs == "proportion_total_squared":
        values = (1+(x.view(np.int64)-x.view(np.int64).max())/(x.view(np.int64).max()-x.view(np.int64).min()))^2
        return pd.DataFrame({funcs:values},dtype=np.float64)
    elif funcs == "proportion_total_cubic":
        values = (1+(x.view(np.int64)-x.view(np.int64).max())/(x.view(np.int64).max()-x.view(np.int64).min()))^3
        return pd.DataFrame({funcs:values},dtype=np.float64)
    elif funcs == "proportion_total_squared_root":
        values = (1+(x.view(np.int64)-x.view(np.int64).max())/(x.view(np.int64).max()-x.view(np.int64).min()))^(1/2)
        return pd.DataFrame({funcs:values},dtype=np.float64)
    elif funcs == "proportion_total_cubic_root":
        values = (1+(x.view(np.int64)-x.view(np.int64).max())/(x.view(np.int64).max()-x.view(np.int64).min()))^(1/3)
        return pd.DataFrame({funcs:values},dtype=np.float64)
    elif funcs == "proportion_month":
        values = x.day/x.days_in_month
        return pd.DataFrame({funcs:values},dtype=np.float64)
    elif funcs == "proportion_quarter":
        quarter = x.dt.quarter
        quarter_start = pd.DatetimeIndex(
        x.dt.year.map(str) + "-" + (3 * quarter - 2).map(int).map(str) + "-01")
        next_quarter_start = x + pd.tseries.offsets.QuarterBegin(startingMonth=1)
        quarter_length = (next_quarter_start - quarter_start).dt.days
        doq  = ((x - quarter_start) / pd.to_timedelta("1D") + 1).astype(int)
        values = doq / quarter_length
        return pd.DataFrame({funcs:values},dtype=np.float64)

Yes that would be a great addition!
In terms of design, the main issue is how to integrate this into the pipeline. The workflow for featurizers is slightly different compared to standard series-to-series transformers. During prediction, you first need to generate features before calling the predict method of the forecaster.
We've had some previous discussions on this (see e.g. these notes).
My preference would be to define a new class for featurizers which closely follows the forecaster API with fit and predict and extend the pipeline class to handle that.

but why can it not be a transformer? As the calendar information has to be passed as X, the ForecastingPipeline would anyway transform X, so it would just add the columns?

My thinking was that you may also want to generate these features if you only have a target series and no exogenous data. That wouldn't be covered by the transformer.

Yes, the X=None is an unfortunate edge case here.
I would actually treat it as follows:

change to base class: if X is None in fit, the input to X in _fit is an empty pd.DataFrame with the same index as y.
may require some dependent changes that checks for X is None in _fit.
CalendarTransformer only looks at the index and adds the features there.
pipeline applied to this X should then work out of the box, no edge case treatment necessary

Still seems like a tricky problem.
Passing an empty pd.DataFrame seems unintuitive to me. In a way, empty data is also an indicator of an error so we may want to check for that at some point in the future.
Allowing None in the transformer interface would be a major interface change.

change to base class: if X is None in fit, the input to X in _fit is an empty pd.DataFrame with the same index as y.

When we do this change, would we not have to update all forecasters that use X to now ignore an empty X? Making all forecaster having to deal with an empty X internally doesn't seem right to me. None is the expected value here for an optional input argument (for users and developers).
To me, this seems like a perfect use case for making some progress on the more advanced pipelining, but that would involve some extra design work I think.

or, we could simply decide that it's not worth letting this edge case stall development and lead to major design discussions, and simply add the caveat that calendar feature adder only works if you have a non-empty X and be done with it'?

Yes, that's also what I would prefer if no-one has the capacity to work on the pipeline, so happy to add the holiday featurizer now and think about the pipeline later.

I think also its a good idea to just ignore this edge case for now. And there is still a workaround for advanced users with the solution I mentioned:

forecaster.fit(y, X=CalendarTransformer().fit_transform(pd.DataFrame(index=y.index)))


CK: fixed correct parsing of the ABI and compiler target string.

Hi Martin - I have fixed now the configure scripts to use the correct ABI strings. Now zlib works like a charm, and I get actual compilations errors our of the run. Please test this out.
For a reference which ABI-strings are valid, look at https://developer.android.com/studio/projects/gradle-external-native-builds.

To answer the questions from inside the compileThirdPartyLibs.sh file:

"where are the VTK libs ?" => VTK is not used or required in any way in the main branch, so there is no reason to compile it.
"doesn't this need to change to target for all being 'app/src/main/jniLibs/$ABI' ?" => Yes, it does. Thank you!


⚠ Bofrost.be has degraded performance

In d6445ef, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 3711 ms

Resolved: Bofrost.be performance has improved in b7f9eae.


Add the policies for opensdhift version 4.13

@vkareh this is a module that uses AWS provider only, that means that it cannot call OCM,
If we would like to call OCM for each creation, we need to add a new data source (as part of terraform-provider-ocm) that  calls to OCM in order to get the policies and it will looks like:
data "ocm_policies" "account_role_policies" {
    rosa_openshift_version = var.rosa_openshift_version
}

module account_role{
  source = "terraform-redhat/rosa-sts/aws"
  version = "0.0.3"

  create_operator_roles = false
  create_oidc_provider = false
  create_account_roles = true

  account_role_prefix = var.account_role_prefix
  policies = data.ocm_policies.account_role_policies.policies
  ocm_environment = var.ocm_env
  rosa_openshift_version=var.rosa_openshift_version
}

Also, it means several changes in the account roles creation which are not in the scope of the first release

@vkareh let's talk about it today in our sync meeting.

I opened a new PRs:
https://github.com/terraform-redhat/terraform-aws-rosa-sts/pull/6
https://github.com/terraform-redhat/terraform-provider-ocm/pull/36
So closing that PR


fix: update image versions

Sanity-checked locally on Slack Clone & Todo List examples

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 22.648%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1163

Relevant Lines:
5135

💛  - Coveralls


coq_8_13: 8.13.1 → 8.13.2

Motivation for this change
Bug fixes: https://coq.github.io/doc/V8.13.2/refman/changes.html#changes-in-8-13-2
cc maintainers @Zimmi48 @roconnor @thoughtpolice
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Thanks!


fix(datepicker): allow using min/max mode/date with datepickerOptions

So I changed datepickerOptions to be processed on the scope directly, that way we can achieve two-way databinding for free.
Now, all the options that are not watchable are put directly and the watchables are put in a way that if they change, the change will be propagated.
As today, attrs overrides options, but that if another PR and another issue.
Fixes #5315

LGTM


checklist:  Implement eth_ namespace API

Description
To ensure compatibility with Ethereum tooling and integrations, we need to implement the eth_ namespace API endpoints as part of our JSON-RPC interface. This will allow clients to interact with our node using the same methods they would with a standard Ethereum client. The below tasks are to be implemented to successfully close this checklist.
Task Checklist

[x] https://github.com/matter-labs/era-test-node/issues/36
[x] https://github.com/matter-labs/era-test-node/issues/37
[x] https://github.com/matter-labs/era-test-node/issues/38
[x] https://github.com/matter-labs/era-test-node/issues/39
[x] https://github.com/matter-labs/era-test-node/issues/40
[x] https://github.com/matter-labs/era-test-node/issues/41
[x] https://github.com/matter-labs/era-test-node/issues/42
[x] https://github.com/matter-labs/era-test-node/issues/43
[x] https://github.com/matter-labs/era-test-node/issues/44
[x] https://github.com/matter-labs/era-test-node/issues/45
[x] https://github.com/matter-labs/era-test-node/issues/46
[x] https://github.com/matter-labs/era-test-node/issues/47
[x] https://github.com/matter-labs/era-test-node/issues/48
[x] https://github.com/matter-labs/era-test-node/issues/49
[x] https://github.com/matter-labs/era-test-node/issues/50

Think this can be closed.