[Fatal Error] annotation-1.2.0.pom:2:1: Content is not allowed in prolog and [Fatal Error] firebase-firestore-24.0.0.pom:2:1: Content is not allowed in prolog.

 crash log
First time coming across such error. Some help out please
`[Fatal Error] annotation-1.2.0.pom:2:1: Content is not allowed in prolog.
[Fatal Error] annotation-1.2.0.pom:2:1: Content is not allowed in prolog.
[Fatal Error] annotation-1.2.0.pom:2:1: Content is not allowed in prolog.
[Fatal Error] firebase-firestore-24.0.0.pom:2:1: Content is not allowed in prolog.
[Fatal Error] firebase-firestore-24.0.0.pom:2:1: Content is not allowed in prolog.
[Fatal Error] firebase-firestore-24.0.0.pom:2:1: Content is not allowed in prolog.
[Fatal Error] firebase-firestore-24.0.0.pom:2:1: Content is not allowed in prolog.
[Fatal Error] firebase-firestore-24.0.0.pom:2:1: Content is not allowed in prolog.
[Fatal Error] firebase-firestore-24.0.0.pom:2:1: Content is not allowed in prolog.
[Fatal Error] firebase-firestore-24.0.0.pom:2:1: Content is not allowed in prolog.
[Fatal Error] firebase-firestore-24.0.0.pom:2:1: Content is not allowed in prolog.
[Fatal Error] firebase-firestore-24.0.0.pom:2:1: Content is not allowed in prolog.
[Fatal Error] firebase-firestore-24.0.0.pom:2:1: Content is not allowed in prolog.
[Fatal Error] firebase-firestore-24.0.0.pom:2:1: Content is not allowed in prolog.
[Fatal Error] firebase-firestore-24.0.0.pom:2:1: Content is not allowed in prolog.
[Fatal Error] firebase-firestore-24.0.0.pom:2:1: Content is not allowed in prolog.
[Fatal Error] firebase-firestore-24.0.0.pom:2:1: Content is not allowed in prolog.
[Fatal Error] firebase-firestore-24.0.0.pom:2:1: Content is not allowed in prolog.
[Fatal Error] firebase-firestore-24.0.0.pom:2:1: Content is not allowed in prolog.
[Fatal Error] firebase-firestore-24.0.0.pom:2:1: Content is not allowed in prolog.
[Fatal Error] firebase-firestore-24.0.0.pom:2:1: Content is not allowed in prolog.
[Fatal Error] firebase-firestore-24.0.0.pom:2:1: Content is not allowed in prolog.
[Fatal Error] firebase-firestore-24.0.0.pom:2:1: Content is not allowed in prolog.
[Fatal Error] firebase-firestore-24.0.0.pom:2:1: Content is not allowed in prolog.
[Fatal Error] firebase-firestore-24.0.0.pom:2:1: Content is not allowed in prolog.
[Fatal Error] firebase-firestore-24.0.0.pom:2:1: Content is not allowed in prolog.
[Fatal Error] firebase-firestore-24.0.0.pom:2:1: Content is not allowed in prolog.
[Fatal Error] firebase-firestore-24.0.0.pom:2:1: Content is not allowed in prolog.

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:checkDebugAarMetadata'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
   > Could not resolve androidx.annotation:annotation:1.2.0.
     Required by:
         project :app
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
   > Could not resolve androidx.annotation:annotation:1.2.0.
     Required by:
         project :app > project :firebase_core
         project :app > project :path_provider_android
         project :app > project :facebook_audience_network
         project :app > project :share
         project :app > project :firebase_messaging
         project :app > project :flutter_plugin_android_lifecycle
         project :app > project :firebase_analytics
         project :app > project :firebase_auth
         project :app > project :firebase_storage
         project :app > androidx.browser:browser:1.3.0
         project :app > project :firebase_core > io.flutter:flutter_embedding_debug:1.0.0-d3ea636dc5d16b56819f3266241e1f708979c233
         project :app > project :image_picker > androidx.exifinterface:exifinterface:1.3.0
         project :app > project :flutter_inappwebview > androidx.webkit:webkit:1.4.0
         project :app > project :flutter_inappwebview > androidx.appcompat:appcompat:1.2.0
         project :app > project :flutter_inappwebview > androidx.swiperefreshlayout:swiperefreshlayout:1.1.0
         project :app > androidx.browser:browser:1.3.0 > androidx.collection:collection:1.1.0
         project :app > androidx.browser:browser:1.3.0 > androidx.concurrent:concurrent-futures:1.0.0
         project :app > com.google.firebase:firebase-auth:21.0.1 > com.google.firebase:firebase-components:17.0.0
         project :app > project :firebase_core > io.flutter:flutter_embedding_debug:1.0.0-d3ea636dc5d16b56819f3266241e1f708979c233 > androidx.lifecycle:lifecycle-common-java8:2.2.0
         project :app > project :flutter_facebook_auth > com.facebook.android:facebook-login:12.1.0 > com.facebook.android:facebook-core:12.1.0
         project :app > project :facebook_audience_network > androidx.lifecycle:lifecycle-runtime:2.3.0 > androidx.arch.core:core-common:2.1.0
         project :app > project :flutter_inappwebview > androidx.appcompat:appcompat:1.2.0 > androidx.appcompat:appcompat-resources:1.2.0
         project :app > project :firebase_messaging > com.google.firebase:firebase-messaging:23.0.0 > com.google.android.datatransport:transport-api:3.0.0
         project :app > project :firebase_messaging > com.google.firebase:firebase-messaging:23.0.0 > com.google.android.datatransport:transport-backend-cct:3.0.0
         project :app > project :firebase_messaging > com.google.firebase:firebase-messaging:23.0.0 > com.google.android.datatransport:transport-runtime:3.0.0
         project :app > project :firebase_messaging > com.google.firebase:firebase-messaging:23.0.0 > com.google.firebase:firebase-datatransport:18.0.0
         project :app > project :firebase_storage > com.google.firebase:firebase-storage:20.0.0
         project :app > project :flutter_facebook_auth > com.facebook.android:facebook-login:12.1.0 > com.facebook.android:facebook-core:12.1.0 > androidx.core:core-ktx:1.3.2
         project :app > com.google.firebase:firebase-auth:21.0.1 > androidx.fragment:fragment:1.3.0 > androidx.activity:activity:1.2.0
         project :app > com.google.firebase:firebase-auth:21.0.1 > androidx.fragment:fragment:1.3.0
         project :app > project :flutter_inappwebview > androidx.appcompat:appcompat:1.2.0 > androidx.appcompat:appcompat-resources:1.2.0 > androidx.vectordrawable:vectordrawable:1.1.0
         project :app > project :firebase_messaging > com.google.firebase:firebase-messaging:23.0.0 > com.google.android.datatransport:transport-backend-cct:3.0.0 > com.google.firebase:firebase-encoders-json:18.0.0
         project :app > com.google.firebase:firebase-bom:29.0.0 > com.google.firebase:firebase-encoders:17.0.0
         project :app > project :image_picker > androidx.core:core:1.3.2 > androidx.versionedparcelable:versionedparcelable:1.1.1
         project :app > project :image_picker > androidx.core:core:1.3.2
         project :app > project :facebook_audience_network > androidx.lifecycle:lifecycle-runtime:2.3.0
         project :app > com.google.firebase:firebase-auth:21.0.1 > androidx.fragment:fragment:1.3.0 > androidx.lifecycle:lifecycle-viewmodel:2.3.0
         project :app > com.google.firebase:firebase-auth:21.0.1 > androidx.fragment:fragment:1.3.0 > androidx.savedstate:savedstate:1.1.0
         project :app > com.google.firebase:firebase-auth:21.0.1 > androidx.fragment:fragment:1.3.0 > androidx.activity:activity:1.2.0 > androidx.tracing:tracing:1.0.0
         project :app > project :facebook_audience_network > androidx.lifecycle:lifecycle-runtime:2.3.0 > androidx.arch.core:core-runtime:2.1.0
         project :app > project :firebase_core > io.flutter:flutter_embedding_debug:1.0.0-d3ea636dc5d16b56819f3266241e1f708979c233 > androidx.lifecycle:lifecycle-common:2.3.0
         project :app > project :google_mobile_ads > com.google.android.gms:play-services-ads:20.1.0 > com.google.android.gms:play-services-ads-lite:20.1.0 > androidx.work:work-runtime:2.1.0 > androidx.room:room-runtime:2.1.0 > androidx.room:room-common:2.1.0
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
   > Could not resolve androidx.annotation:annotation:1.2.0.
     Required by:
         project :app > project :image_picker
         project :app > project :webview_flutter_android
         project :app > project :firebase_messaging > androidx.localbroadcastmanager:localbroadcastmanager:1.0.0
         project :app > androidx.browser:browser:1.3.0 > androidx.interpolator:interpolator:1.0.0
         project :app > project :flutter_inappwebview > androidx.appcompat:appcompat:1.2.0 > androidx.cursoradapter:cursoradapter:1.0.0
         project :app > project :flutter_inappwebview > androidx.appcompat:appcompat:1.2.0 > androidx.drawerlayout:drawerlayout:1.0.0
         project :app > com.google.firebase:firebase-analytics:20.0.0 > com.google.android.gms:play-services-measurement:20.0.0 > androidx.legacy:legacy-support-core-utils:1.0.0
         project :app > com.google.firebase:firebase-auth:21.0.1 > androidx.fragment:fragment:1.3.0 > androidx.viewpager:viewpager:1.0.0
         project :app > com.google.firebase:firebase-auth:21.0.1 > androidx.fragment:fragment:1.3.0 > androidx.loader:loader:1.0.0
         project :app > project :flutter_facebook_auth > com.facebook.android:facebook-login:12.1.0 > com.facebook.android:facebook-common:12.1.0 > androidx.cardview:cardview:1.0.0
         project :app > project :flutter_inappwebview > androidx.appcompat:appcompat:1.2.0 > androidx.drawerlayout:drawerlayout:1.0.0 > androidx.customview:customview:1.0.0
         project :app > project :google_mobile_ads > com.google.android.gms:play-services-ads:20.1.0 > com.google.android.gms:play-services-ads-lite:20.1.0 > com.google.android.ump:user-messaging-platform:1.0.0
         project :app > com.google.firebase:firebase-analytics:20.0.0 > com.google.android.gms:play-services-measurement:20.0.0 > androidx.legacy:legacy-support-core-utils:1.0.0 > androidx.documentfile:documentfile:1.0.0
         project :app > com.google.firebase:firebase-analytics:20.0.0 > com.google.android.gms:play-services-measurement:20.0.0 > androidx.legacy:legacy-support-core-utils:1.0.0 > androidx.print:print:1.0.0
         project :app > com.google.firebase:firebase-auth:21.0.1 > androidx.fragment:fragment:1.3.0 > androidx.lifecycle:lifecycle-viewmodel-savedstate:2.3.0
         project :app > project :flutter_facebook_auth > com.facebook.android:facebook-login:12.1.0 > com.facebook.android:facebook-common:12.1.0 > androidx.legacy:legacy-support-v4:1.0.0 > androidx.legacy:legacy-support-core-ui:1.0.0
         project :app > project :flutter_facebook_auth > com.facebook.android:facebook-login:12.1.0 > com.facebook.android:facebook-common:12.1.0 > androidx.legacy:legacy-support-v4:1.0.0 > androidx.legacy:legacy-support-core-ui:1.0.0 > androidx.coordinatorlayout:coordinatorlayout:1.0.0
         project :app > project :flutter_facebook_auth > com.facebook.android:facebook-login:12.1.0 > com.facebook.android:facebook-common:12.1.0 > androidx.legacy:legacy-support-v4:1.0.0 > androidx.legacy:legacy-support-core-ui:1.0.0 > androidx.slidingpanelayout:slidingpanelayout:1.0.0
         project :app > project :flutter_facebook_auth > com.facebook.android:facebook-login:12.1.0 > com.facebook.android:facebook-common:12.1.0 > androidx.legacy:legacy-support-v4:1.0.0 > androidx.legacy:legacy-support-core-ui:1.0.0 > androidx.asynclayoutinflater:asynclayoutinflater:1.0.0
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
   > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
     Required by:
         project :app > project :cloud_firestore
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
   > Could not resolve androidx.annotation:annotation:1.2.0.
     Required by:
         project :app > project :cloud_firestore
         project :app > project :just_audio > com.google.android.exoplayer:exoplayer-core:2.15.0
         project :app > project :just_audio > com.google.android.exoplayer:exoplayer-dash:2.15.0
         project :app > project :just_audio > com.google.android.exoplayer:exoplayer-hls:2.15.0
         project :app > project :just_audio > com.google.android.exoplayer:exoplayer-smoothstreaming:2.15.0
         project :app > project :just_audio > com.google.android.exoplayer:exoplayer-core:2.15.0 > com.google.android.exoplayer:exoplayer-common:2.15.0
         project :app > project :just_audio > com.google.android.exoplayer:exoplayer-core:2.15.0 > com.google.android.exoplayer:exoplayer-extractor:2.15.0
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
   > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
     Required by:
         project :app > com.google.firebase:firebase-bom:29.0.0
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
      > Could not resolve com.google.firebase:firebase-firestore:24.0.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/24.0.0/firebase-firestore-24.0.0.pom
            > Content is not allowed in prolog.
   > Could not resolve androidx.annotation:annotation:1.2.0.
     Required by:
         project :app > project :google_mobile_ads > com.google.android.gms:play-services-ads:20.1.0 > com.google.android.gms:play-services-ads-lite:20.1.0 > androidx.work:work-runtime:2.1.0 > androidx.room:room-runtime:2.1.0 > androidx.sqlite:sqlite-framework:2.0.1
         project :app > project :google_mobile_ads > com.google.android.gms:play-services-ads:20.1.0 > com.google.android.gms:play-services-ads-lite:20.1.0 > androidx.work:work-runtime:2.1.0 > androidx.room:room-runtime:2.1.0 > androidx.sqlite:sqlite:2.0.1
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.
      > Could not resolve androidx.annotation:annotation:1.2.0.
         > Could not parse POM https://dl.google.com/dl/android/maven2/androidx/annotation/annotation/1.2.0/annotation-1.2.0.pom
            > Content is not allowed in prolog.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 1m 1s
Exception: Gradle task assembleDebug failed with exit code 1

@Prime-Ext
When do you get this log ? Can you provide flutter doctor -v and steps to replicate ?

Here is my flutter doctor -v
I get the error each time i try running my app.
`[√] Flutter (Channel stable, 2.5.3, on Microsoft Windows [Version 10.0.18362.30], locale en-US)
• Flutter version 2.5.3 at C:\flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 18116933e7 (9 weeks ago), 2021-10-15 10:46:35 -0700
• Engine revision d3ea636dc5
• Dart version 2.14.4
[√] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
• Android SDK at C:\Users\PRIME\AppData\Local\Android\sdk
• Platform android-31, build-tools 31.0.0
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
• All Android licenses accepted.
[√] Chrome - develop for the web
• Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe
[√] Android Studio (version 2020.3)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin can be installed from:
https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
[√] IntelliJ IDEA Community Edition (version 2020.2)
• IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2020.2.3
• Flutter plugin can be installed from:
https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
https://plugins.jetbrains.com/plugin/6351-dart
[√] VS Code (version 1.63.1)
• VS Code at C:\Users\PRIME\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.29.0
[√] Connected device (3 available)
• itel P651W (mobile) • 062983715I011447 • android-arm    • Android 10 (API 29)
• Chrome (web)        • chrome           • web-javascript • Google Chrome 96.0.4664.93
• Edge (web)          • edge             • web-javascript • Microsoft Edge 94.0.992.38
• No issues found!`

@Prime-Ext
Can you upgrade to latest stable and try again ?
If issue still persists, please provide pubspec.yaml, android and app level build.gradle in properly formatted text.

I'm on the stable flutter version that is version 2.8.1
My pubspec.yaml
`name: bwamnews
description: News App.
publish_to: 'none' # Remove this line if you wish to publish to pub.dev
version: 1.0.0+1
environment:
sdk: ">=2.12.0 <3.0.0"
dependencies:
flutter:
sdk: flutter
cupertino_icons: ^1.0.2
badges: ^2.0.1
cached_network_image: ^3.0.0
cloud_firestore: ^3.1.5
dots_indicator: ^2.0.0
easy_localization: ^3.0.0
firebase_auth: ^3.3.4
firebase_core: ^1.3.0
firebase_messaging: ^11.2.4
firebase_storage: ^10.2.4
flutter_web_browser: ^0.16.0
flutter_html: ^2.1.0
flutter_widget_from_html: ^0.8.4
google_fonts: ^2.1.0
google_sign_in: ^5.0.4
html: ^0.15.0
html_unescape: ^2.0.0
image_picker: ^0.8.1+3
intl: ^0.17.0
introduction_screen: ^2.1.0
launch_review: ^3.0.1
line_icons: ^2.0.1
lottie: ^1.1.0
package_info: ^2.0.2
path_provider: ^2.0.2
provider: ^6.0.1
share: ^2.0.4
shared_preferences: ^2.0.6
skeleton_text: ^3.0.0
fluttertoast: ^8.0.7
url_launcher: ^6.0.9
youtube_player_flutter: ^8.0.0
youtube_plyr_iframe: ^2.0.7
rounded_loading_button: ^2.0.5
firebase_analytics: ^9.0.4
flutter_facebook_auth: ^3.5.0
the_apple_sign_in: ^1.1.1
video_player: ^2.1.10
flick_video_player: ^0.4.0-dev.4
flutter_icons:
git:
url: https://github.com/adarsh-technocrat/flutter-icons
md2_tab_indicator:
git:
url: https://github.com/westdabestdb/md2_tab_indicator
google_mobile_ads: ^1.0.1
facebook_audience_network: ^1.0.0-nullsafety.0
dev_dependencies:
flutter_test:
sdk: flutter
flutter_launcher_icons: "^0.9.0"
flutter_lints: ^1.0.0
flutter_icons:
android: "launcher_icon"
ios: true
image_path: "assets/images/icon.png"
flutter:
uses-material-design: true
To add assets to your application, add an assets section, like this:
assets:
- assets/images/
- assets/animation_files/
- assets/translations/
fonts:
- family: Poppins
  fonts:
    - asset: assets/fonts/Poppins-Light.ttf
      weight: 400
    - asset: assets/fonts/Poppins-Regular.ttf
      weight: 500
    - asset: assets/fonts/Poppins-Medium.ttf
      weight: 600
    - asset: assets/fonts/Poppins-SemiBold.ttf
      weight: 700
    - asset: assets/fonts/Poppins-Bold.ttf
      weight: 800

- family: Open Sans
  fonts:
    - asset: assets/fonts/OpenSans-Light.ttf
      weight: 400
    - asset: assets/fonts/OpenSans-Regular.ttf
      weight: 500

- family: Manrope
  fonts:
    # - asset: assets/fonts/Manrope-Light.ttf
    #   weight: 300
    - asset: assets/fonts/Manrope-Regular.ttf
      weight: 400
    - asset: assets/fonts/Manrope-SemiBold.ttf
      weight: 500
    - asset: assets/fonts/Manrope-Medium.ttf
      weight: 600
    - asset: assets/fonts/Manrope-Bold.ttf
      weight: 700
    - asset: assets/fonts/Manrope-ExtraBold.ttf
      weight: 900

`
Android/app/build.gradle
`def localProperties = new Properties()
def localPropertiesFile = rootProject.file('local.properties')
if (localPropertiesFile.exists()) {
localPropertiesFile.withReader('UTF-8') { reader ->
localProperties.load(reader)
}
}
def flutterRoot = localProperties.getProperty('flutter.sdk')
if (flutterRoot == null) {
throw new GradleException("Flutter SDK not found. Define location with flutter.sdk in the local.properties file.")
}
def flutterVersionCode = localProperties.getProperty('flutter.versionCode')
if (flutterVersionCode == null) {
flutterVersionCode = '1'
}
def flutterVersionName = localProperties.getProperty('flutter.versionName')
if (flutterVersionName == null) {
flutterVersionName = '1.0'
}
apply plugin: 'com.android.application'
apply plugin: 'com.google.gms.google-services'
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"
android {
compileSdkVersion 31
compileOptions {
    sourceCompatibility JavaVersion.VERSION_1_8
    targetCompatibility JavaVersion.VERSION_1_8
}

defaultConfig {
    // TODO: Specify your own unique Application ID (https://developer.android.com/studio/build/application-id.html).
    applicationId "com.bwamnews.bwamnews"
    minSdkVersion 23
    targetSdkVersion 31
    versionCode flutterVersionCode.toInteger()
    versionName flutterVersionName
    multiDexEnabled true
}

buildTypes {
    release {
        // TODO: Add your own signing config for the release build.
        // Signing with the debug keys for now, so `flutter run --release` works.
        signingConfig signingConfigs.debug
    }
}

}
flutter {
source '../..'
}
dependencies {
implementation platform('com.google.firebase:firebase-bom:28.4.2')
implementation 'com.google.firebase:firebase-analytics'
implementation "androidx.browser:browser:1.3.0"
implementation 'com.google.firebase:firebase-auth'
implementation 'com.android.support:multidex:2.0.1'
}
`
Android/build.gradle
`buildscript {
repositories {
google()
mavenCentral()
}
dependencies {
    classpath 'com.android.tools.build:gradle:4.1.0'
    classpath 'com.google.gms:google-services:4.3.10'
}

}
allprojects {
repositories {
google()
mavenCentral()
}
}
rootProject.buildDir = '../build'
subprojects {
project.buildDir = "${rootProject.buildDir}/${project.name}"
project.evaluationDependsOn(':app')
}
task clean(type: Delete) {
delete rootProject.buildDir
}
`

@Prime-Ext
It may seem to be related to the firebase implementations. Can you try removing or commenting those and see what do you get ?


Re-Editing the levels

certain levels feel shallow or completely cut in half. Not intentional during the inception of the creation for this game, however, levels require complete re-works where...
The top half is difficult based on timing jumps while the bottom half takes more effort to get to the solution (both are solvable). The Sonic The Hedgehog solution to the problem of needing to use multiple stages of the levels and managing to both challenge and allow new players to solve the level eventually.
Using whole levels is rather difficult unless the route is not planned for ahead of time.
 We made it to level 13 and here are the current results:

Put more easier levels at the start (even if it's a repeat idea, like the hit space or level 3). This will give players more time to get used to the physics/jumping. We should put a simple level before hallways and introduce elements that way (self.platforms and self.win_zones in one, self.death_zone in another, self.respawn, and then introduce self.draw with it's rules where it's any color except for the ones described before). The levels after will be a good review since they'll be more detailed).
Candles is a bit too difficult (for it's position/level number in the main set). Also this level needs a redesign, as the play tester thought the dripping wax were walls (maybe we do dynamic stuff?) or keep it simple. Another issue with this level is that the last candle has no collision for some reason.
Letters is way too hard. I think we should avoid the use of the elevator step ups (we could do the teleporter idea). It could also use some color, like this:
.

Overall, we should focus on more visually appealing levels and put less focus on the level mechanics (and how we can make it different)

I agree with a lot of what is being said here, however, there are a lot of levels later that need to be introduced beforehand like avoid_red and split_path and signals. I made a lot of these levels with ease in mind and just made letters way too soon. I'll put a patch for that soon, however, I think what we should do is lock some of the levels so that players are not allowed to access it unless they have beaten the main branch.

@shoc71 Should we close this issue since it's no longer relevant and open up another one more relevant to our direction?

yes, agreed. Close this whenever you'd like


Semantic versioning should be followed with new releases that include breaking changes

https://dart.dev/tools/pub/versioning#semantic-versions
Flutter recommends using the caret syntax for developers when including libraries/dependencies in their apps.
According to the documentation on version constraints, non-major updates should be backwards compatible and not break existing implementations.
There have been a few updates that have broken apps (or created regression issues) using flutter_inappwebview without the developers explicitly bumping the version numbers in the pubspec.

You are completely right! I apologize for any issue that I created.
However, I have documented every BREAKING CHANGES every time, if there were any of them, on each release: https://github.com/pichillilorenzo/flutter_inappwebview/blob/master/CHANGELOG.md
In the next releases, if there are any breaking changes, I will update the plugin with a major release.
The next one will have for sure some breaking changes, so I will publish it as 4.0.0.
Thanks!


Refactor that would check order of called private methods and reorder them if needed

private function getThis()
{
}

// this one should be above, because reading code from top to bottom makes is easier to understand
private function getThat()
{
    return $this->getThis();
}

Too imba


[full-ci] bump core commit id to run new versions tests

Description
run tests of https://github.com/owncloud/core/pull/38921
after https://github.com/owncloud/core/pull/38921 is merged this need to be changed to have master branch and the correct commit id in the .env file
How Has This Been Tested?
:robot:
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Technical debt
[x] Tests only (no source changes)

Checklist:

[ ] Code changes
[ ] Unit tests added
[ ] Acceptance tests added
[ ] Documentation ticket raised:

:boom: Acceptance tests localApiTests-apiBugDemonstration-ocis failed. The build is cancelled...

@individual-it there days you can put full-ci in the PR title, and all the test pipelines will run to completion. That is handy when you need to see all the things that fail.

:boom: Acceptance tests localApiTests-apiBugDemonstration-ocis failed. The build is cancelled...

IMO you need to push a change or rebase. Just restarting the drone build does not make it fetch the updated PR title.

that failing test does not make any sense in the first place, it does not use Shares/ to access the received share and also the original test https://github.com/owncloud/core/blob/b8e8d740b24e18da4e951b99302d2034f2e7215d/tests/acceptance/features/apiVersions/fileVersionsSharingToShares.feature#L43 is not listed in expected to fail, so should pass

Those "local API" "bug demo" scenarios don't seem to try to use the Shares folder at all. It's a long time since anyone looked at them. They need to be reviewed and sorted out.

But I think the cause of the fail is https://github.com/owncloud/core/pull/38921#pullrequestreview-699133898

:boom: Acceptance tests localApiTests-apiBugDemonstration-ocis failed. The build is cancelled...

Note: @kiranparajuli589 has #2264 almost ready - that will adjust a lot of stuff.

#2264 bumps the we commit id, here we bump the core id

https://drone.owncloud.com/owncloud/ocis/5841/37/7
runsh: There were no unexpected failures.
runsh: Total unexpected passed scenarios throughout the test run:
apiVersions/fileVersions.feature:420
apiVersions/fileVersions.feature:438
apiVersions/fileVersionsSharingToShares.feature:301

https://drone.owncloud.com/owncloud/ocis/5841/38/6
runsh: There were no unexpected failures.
runsh: Total unexpected passed scenarios throughout the test run:
apiVersions/fileVersions.feature:420
apiVersions/fileVersions.feature:438
apiVersions/fileVersionsSharingToShares.feature:301

the only reason why they pass is because they did not run :-( but why?

I've copied the wrong commit id from master, lets see now


Updating to latest nuxt-bridge version breaks Webpack HMR

Environment

Operating System: Darwin
Node Version:     v16.18.0
Nuxt Version:     2.16.0-27720022.54e852f
Nitro Version:    0.6.0
Package Manager<EMAIL_ADDRESS>Builder:          webpack
User Config:      bridge, head, css, plugins, components, buildModules, build, serverHandlers, devServerHandlers, typescript
Runtime Modules:  -
Build Modules<EMAIL_ADDRESS><EMAIL_ADDRESS>
Reproduction
https://github.com/linhmtran168/test-nuxt-bridge
Just a clean create-nuxt-app updated to use latest nuxt-bridge version
Describe the bug
Nuxt Bridge latest version<EMAIL_ADDRESS>breaks webpack HMR with the following error in browser console:
GET http://localhost:3001/__webpack_hmr/client 404 (Not Found)

Downgrading to 3.0.0-27747000.69db93e fixes the problem
Additional context
No response
Logs
No response

Me downgrading to bridge 3.0.0-27747000.69db93e did not help. Why is the bridge so useless. Many bugs, not stable.

@Draccano Did you actually downgrade to bridge 3.0.0-27747000.69db93e?
It seems that there are problems with Nuxi 3.0.0-rc.12, and bridge 3.0.0-27747000.69db93e uses Nuxi 3.0.0-rc.11 which doesn't have the problems.
Please check when running npm run dev, the version of Nuxi displayed is 3.0.0-rc.11

@linhmtran168 I use nuxt bridge together with the nuxt-edge. The Nuxi 3.0.0-rc.11 is related to nuxt 3, no?

@Draccano Yes.nuxt-bridge use nuxi for all command line operations.
For me, I fixed the nuxt-bridge version in package.json as follows and ran npm install again, then Webpack HRM worked normally
@nuxt/bridge": "npm<EMAIL_ADDRESS>

I ran your version, together with `"nuxt-edge": "latest", and it showed 404 error :/

Same here 👍 I do confirm that<EMAIL_ADDRESS>seems not to have the issue, but<EMAIL_ADDRESS>does.
I could reproduce it from starter template:
npx nuxi init nuxt-bridge-app -t v2-bridge

Any progress on that?
@danielroe

I've downgraded to 3.0.0-27747000.69db93e and now other bridge methods stopped working for me...

The issue still exists on<EMAIL_ADDRESS>

Confirmed that it's still happening on 3.0.0-27846691.4aaf4eb. Here it's a repo I created to reproduce the error.

same in 3.0.0-27851925.695ddd7

This issue still persists. Using an old version works, as described earlier:
// works
@nuxt/bridge": "npm<EMAIL_ADDRESS>// doesn't work
@nuxt/bridge": "npm:@nuxt/bridge-edge@latest"

To use Webpack HMR with latest nuxt-bridge, you can patch @nuxt/webpack-edge package by using npm's patch-package package or pnpm. New versions of Nitro require node middleware to be converted to h3 handler and the hook for running middleware also changed. The following patch works for me:
diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index ebe49a8..290907d 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -41,6 +41,7 @@ const createResolver = require('postcss-import-resolver');
 const Watchpack = require('watchpack');
 const objectToMap = require('webpack/lib/util/objectToMap');
 const nodeExternals = require('webpack-node-externals');
+const h3 = require('h3')

 function _interopDefaultLegacy (e) { return e && typeof e === 'object' && 'default' in e ? e : { 'default': e }; }

@@ -1929,6 +1930,7 @@ class WebpackBundler {
       });
       await nuxt.callHook("build:resources", this.mfs);
     });
+
     if (options.dev) {
       if (["client", "modern"].includes(name)) {
         return new Promise((resolve, reject) => {
@@ -1992,7 +1994,7 @@ class WebpackBundler {
         }
       )
     );
-    await this.buildContext.nuxt.callHook("server:devMiddleware", this.middleware);
+    await this.buildContext.nuxt.callHook("server:devHandler", h3.fromNodeMiddleware(this.middleware));
   }
   async middleware(req, res, next) {
     const name = utilsEdge.isModernRequest(req, this.buildContext.options.modern) ? "modern" : "client";

This also fixed HMR for me. I am using yarn and this worked for me:
yarn patch @nuxt/webpack-edge

Then just do what the command line prompts. Open the file, change it and then commit the patch. It should look something like this:
yarn patch-commit -s /private/var/folders/jg/5g_62ljn0dz2y1x3bnd9q31r0000gn/T/xfs-5730634f/user

Instead of patching node_modules you can also do the conversion within the ready hook in your nuxt.config.ts:
import { fromNodeMiddleware, type NodeMiddleware } from 'h3';

export default defineNuxtConfig({
  hooks: {
    ready(nuxt) {
      // https://github.com/nuxt/bridge/issues/607
      // translate nuxt 2 hook from @nuxt/webpack-edge to nuxt bridge hook
      nuxt.hook('server:devMiddleware' as any, async (devMiddleware: NodeMiddleware) => {
        await nuxt.callHook('server:devHandler', fromNodeMiddleware(devMiddleware));
      });
    },
  },
});

@sreuss
Great Job!

@sreuss you fixed this problem

And the hot reload in my nuxt bridge project <3
These problems was with the packages versions bellow (pnpm)

@sreuss Thanks a lot! Finally, it works
For those who are not using typescript:
`import { fromNodeMiddleware } from 'h3';
export default defineNuxtConfig({
hooks: {
ready (nuxt) {
// https://github.com/nuxt/bridge/issues/607
// translate nuxt 2 hook from @nuxt/webpack-edge to nuxt bridge hook
nuxt.hook('server:devMiddleware', async (devMiddleware) => {
await nuxt.callHook('server:devHandler', fromNodeMiddleware(devMiddleware));
});
},
},
});`

But after coding few hours with this workaround, i constated that my web app crash sometimes.

I haven't any error

NodeMiddleware

It works!
Can you fix this issue at the next version?
@danielroe

Absolutely! A PR would be very welcome 🙏

I have this issue currently with the latest version of bridge.
webpackHotUpdate("app", {

    /***/
    "./assets/scss/tailwind.css": /*!**********************************!*\
  !*** ./assets/scss/tailwind.css ***!
  \**********************************/
    /*! no static exports found */
    /***/


Revert "Reland "[web] Move JS content to its own .js files""

Reverts flutter/flutter#120363
Breaking the Google roll as the patch isn't working.

FYI I believe this is no longer necessary. I'm going to leave open until the roll has submitted.


DRILL-5902: Regression: Queries encounter random failure due to RPC connection timed out

@arina-ielchiieva Please review

@ilooner DRILL-6143 is not related to DRILL-5902. DRILL-6143 requires a separate RCA. See DRILL-5902 for details.

K thx @vrozov

+1, LGTM.


fix: update config to policy file conversion and associated tests

config --> policy file conversion and test files needed updates to match changes to per-plugin config/version expectations

Resolves #572 .


Identify and prioritize open perf benchmarks

We want to select various (open-source) performance benchmark suites/harnesses to run at AdoptOpenJDK (for validating JDK binaries and to make available for easy use by JDK developers).
We can first list any that could be useful for JDK measurement/verification, identify why they are interesting, and then prioritize accordingly.  This list can include both full suites and microbenchmarks with links to git repos (and pre-compiled jar/zip files when available).
Once we start adding test targets from different benches, we will also have to ensure that they are suitable for all implementations (not based on implementation specific classes, etc).  But we can leave that as a separate exercise.
Larger suites
HiBench:
https://github.com/Intel-bigdata/HiBench
AcmeAir:
https://github.com/blueperf/acmeair-monolithic-java
https://acmeair.github.io/acmeair/
DayTrader3:
https://github.com/WASdev/sample.daytrader3
DayTrader7:
https://github.com/WASdev/sample.daytrader7
Dacapo:
https://github.com/dacapobench/dacapobench
http://dacapobench.org/
Micro/Macro Bench Harnesses
Bumblebench:
https://github.com/AdoptOpenJDK/bumblebench
jmh:
https://openjdk.java.net/projects/code-tools/jmh/
Also look at https://github.com/Hyperfoil/

Thanks Shelley for creating this list! Besides the ones that you've already mentioned, here are some more open benchmarks:
Startup time, Footprint and Throughput of OpenLiberty with different apps:
https://github.com/OpenLiberty/open-liberty + DT3, DT7, AcmeAir & More
Linkerd:
https://github.com/linkerd/linkerd-examples/tree/master/perf-baseline/linkerd1-perf
Databricks:
https://github.com/databricks/spark-perf
ES Rally:
https://github.com/elastic/rally
Spring Boot Startup Benchmark:
https://github.com/dsyer/spring-boot-startup-bench
FrameworkBenchmarks:
https://github.com/TechEmpower/FrameworkBenchmarks
Perf Team's Microbenchmarks
We've also written a few micro-benchmarks such as for crypto and GPU over the few years so we could think of adding those if you think they might be interesting and useful.
SPEC
I guess we're just talking about open benchmarks here but we can also think of running some benchmarks from Standard Performance Evaluation Corporation (SPEC) such as SPECjbb2015 if it's possible to get licenses for them. It would be good to have them as part of AdoptOpenJDK quality assurance and possibly publish official results (https://www.spec.org/jbb2015/results/jbb2015.html) for our releases.
Priority
I've already got started on adding Open Liberty with different apps (DT3, DT7 & AcmeAir) since that's the highest priority for us. I'm planning to schedule a meeting soon to discuss about perf testing. FYI @vijaysun-omr

Thanks @piyush286 !  I have also added a note to the AdoptOpenJDK testing channel to solicit feedback from others (on what open benchmarks they choose, and why)...  and looks like we have a nice selection already.

I also agree that we should consider SPEC benchmarks.  We will have to look at the licenses, to understand all of the details.
As I mentioned in our meeting, it could be that we start with the scenario that we add the metadata for running them (as special level), and treat it like JCKs, where folks with licenses could choose to run those targets, moving towards a scenario where we may license & publish results.  Ultimately, we will want to look closely at the details, and decide if those benchmarks meet the criteria (open/transparent) and therefore fit into the AQA story or not.

https://renaissance.dev/
To quote their website:

Renaissance is a modern, open, and diversified benchmark suite for the JVM, aimed at testing JIT compilers, garbage collectors, profilers, analyzers and other tools.

https://github.com/Hyperfoil/ also interesting

Adding https://github.com/spring-projects/spring-petclinic to the list here, so that I can close related: https://github.com/AdoptOpenJDK/openjdk-tests/issues/1501 as we do not need to keep both issues open.

Instead of tracking it via a separate issue, will close https://github.com/adoptium/aqa-tests/issues/1255 and track databricks and hibench via this issue.


chore: use rayon in pq transform and remove async calls

one nit + would you happen to have benchmark numbers?
did not find a handy benchmark for PQ::transform yet, could be next time.

Codecov Report
Attention: Patch coverage is 94.33962% with 6 lines in your changes are missing coverage. Please review.

Project coverage is 80.79%. Comparing base (4cb0a2b) to head (0e374af).

Files
Patch %
Lines

rust/lance-linalg/src/kmeans.rs
81.81%
4 Missing :warning:

rust/lance-index/src/vector/pq.rs
98.76%
0 Missing and 1 partial :warning:

rust/lance-index/src/vector/pq/transform.rs
0.00%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2343      +/-   ##
==========================================
+ Coverage   80.78%   80.79%   +0.01%
==========================================
  Files         192      192
  Lines       56189    56213      +24
  Branches    56189    56213      +24
==========================================
+ Hits        45392    45420      +28
- Misses       8128     8129       +1
+ Partials     2669     2664       -5

Flag
Coverage Δ

unittests
80.79% <94.33%> (+0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[Blog Feature Request] Is it Possible adding some scripts to generate markdown files?

Greeting!✋🏼
I was wondering if we could add some simple scripts that could generating title, author, date even h1 tag...
Create file manually each time is troubling.

Hey! I think you can manually create a script file and execute it before building the Next.js project. Here's a similar example (how I generate these RSS feeds): https://github.com/shuding/site/blob/master/package.json#L9


Docker not needed after server launched ?

We just need some precisions about the general functioning of the Offline Matcher server.
After having executed the import bash from inside the docker, a ".bfmap" file was created outside of the docker.
This file is then used by the java file ("target/barefoot-0.1.1-matcher-jar-with-dependencies.jar"). This starts a server reachable on port 1234. And it works fine.
But it seems that if we kill and remove the docker, the java server still works fine, and can be restarted anytime since it just uses the ".bfmap" file to work.
Is that expected ? Can we safely destroy any Docker after having created the ".bfmap" file ?

Yes, this is correct. However, if you modify/update Barefoot source code it will be incompatible with the *.bfmap file. In this case, it is necessary to reread data from the Docker map server. That means you could just stop the container (not delete) it if you want to stick with a certain map version. If you don't need a certain map version you could just recreate the map server with a new version of map data. Further, it is more easy to modify map data in the database of the Docker map server as in the program.


CVEs Related Advisories missing props for v1 parity

In v1 CVE detail page you have the following properties visible for its related advisories, which are not available now:

Revision
Vulnerabilities
No aggregate severity showing up in column value despite severity existing? This might just be a "not enough data" issue on my part

See also this spreadsheet for a complete list of properties missing in the current version of the UI.

I think that "Aggregated severity" is already available:

It's just the wrong column header. Because that's a severity, not a score.

Taking a look at the "revision", I think it's just the advisory's date. So you should be able to use modified.


Fixed typo in classname

Renamed w-header__glpyh to w-header__glyph.
Based on https://github.com/wagtail/wagtail/pull/8799#pullrequestreview-1029707808.
Introduced in #8799.

That LGTM now - I see that the test-postgres test is failing on other MRs as well as this one, so I assume that is unrelated to these changes. @thibaudcolas are you able to approve / merge this one?


Confusing interface when both "Allow run Sync" and "Allow run Async" checked for datasource

Make sure these boxes are checked before submitting your issue - thank you!

[X] I have checked the superset logs for python stacktraces and included it here as text if any
[X] I have reproduced the issue with at least the latest released version of superset
[X] I have checked the issue tracker for the same issue and I haven't found one similar

Superset version
0.28.0rc5
Expected results
The button displayed in the SQL Lab view's hover text corresponds with the actual type of execution that will happen. SqlEditor.runQuery() passes the proper argument into SqlEditor.startQuery()
Actual results
When you have a database that has both "Allow Run Sync" and "Allow Run Async" enabled, src/SqlLab/components/RunQueryActionButton.jsx:L67 will render the asyncBtn. The asyncBtn has the onClick action of SqlEditor.runQuery(true). This method, if I understand SqlEditor:L136 correctly, doesn't actually accept that parameter to do anything. Instead, it calls startQuery(!(this.props.database || {}).allow_run_sync). If you have allow_run_sync enabled, it runs startQuery(runAsync = false). Meaning that even though you have enabled async running on the database configuration, it still runs as sync. Basically, if I'm understanding the code correctly, this means that the "Allow Run Async" option is essentially useless, as it will always just execute !database.allow_run_sync.
However, if you toggle sync to effect the method of execution, the button rendered won't update to the correct version, meaning you can very easily end up with situations where the hover on the button says "Run Query Asynchronously" and it runs synchronously, or "Run Query Synchronously" and it runs async. This is confusing behavior.
I'll caveat all of this with a giant "I'm not great at JS" sticker however, so I very well could have misunderstood what's happening, even though I'm confident that the behavior is wrong.
Steps to reproduce
Set up an async backend. Create a datasource. Mark both "async" and "sync" in the database config. Run a SQL Lab query. Even though the button's hover text says "async", the arg passed in the form in POST for runAsync will be set to "false"

https://github.com/apache/incubator-superset/pull/4961


"Duration" Playout Mode errors out

This occurs when using a single collection of Movies in the Schedule. I'm trying to get it to schedule between 08:00 and 17:00, and then going offline, but I keep running into this error when generating the Playout:
[17:46:42 ERR] Unhandled exception in circuit 'n_u1VmAMZHa1VvOKqEFyujgq76ihmTuWssojSGWDulg'.
System.ArgumentOutOfRangeException: The UTC time represented when the offset is applied must be between year 0 and 10,000. (Parameter 'offset')
   at System.DateTimeOffset.ValidateDate(DateTime dateTime, TimeSpan offset)
   at System.DateTimeOffset..ctor(DateTime dateTime)
   at System.DateTimeOffset.op_Implicit(DateTime dateTime)
   at ErsatzTV.Core.Scheduling.PlayoutBuilder.<>c__DisplayClass8_4.<BuildPlayoutItems>b__19(MediaItem peekMediaItem) in /source/ErsatzTV.Core/Scheduling/PlayoutBuilder.cs:line 371
   at ErsatzTV.Core.Scheduling.PlayoutBuilder.<>c__DisplayClass8_3.<BuildPlayoutItems>b__16(MediaItem mediaItem) in /source/ErsatzTV.Core/Scheduling/PlayoutBuilder.cs:line 353
   at LanguageExt.ClassInstances.MOptionAsync`1.Match(OptionAsync`1 opt, Action`1 Some, Action None)
   at ErsatzTV.Core.Scheduling.PlayoutBuilder.BuildPlayoutItems(Playout playout, DateTimeOffset playoutStart, DateTimeOffset playoutFinish, Boolean rebuild) in /source/ErsatzTV.Core/Scheduling/PlayoutBuilder.cs:line 235
   at ErsatzTV.Core.Scheduling.PlayoutBuilder.BuildPlayoutItems(Playout playout, Boolean rebuild) in /source/ErsatzTV.Core/Scheduling/PlayoutBuilder.cs:line 45
   at ErsatzTV.Application.Playouts.Commands.BuildPlayoutHandler.ApplyUpdateRequest(TvContext dbContext, BuildPlayout request, Playout playout) in /source/ErsatzTV.Application/Playouts/Commands/BuildPlayoutHandler.cs:line 33
   at ErsatzTV.Core.LanguageExtensions.<>c__DisplayClass2_0`2.<<Apply>b__0>d.MoveNext() in /source/ErsatzTV.Core/LanguageExtensions.cs:line 25
--- End of stack trace from previous location ---
   at ErsatzTV.Application.Playouts.Commands.BuildPlayoutHandler.Handle(BuildPlayout request, CancellationToken cancellationToken) in /source/ErsatzTV.Application/Playouts/Commands/BuildPlayoutHandler.cs:line 28
   at ErsatzTV.Application.Playouts.Commands.BuildPlayoutHandler.Handle(BuildPlayout request, CancellationToken cancellationToken) in /source/ErsatzTV.Application/Playouts/Commands/BuildPlayoutHandler.cs:line 28
   at MediatR.Pipeline.RequestExceptionProcessorBehavior`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
   at MediatR.Pipeline.RequestExceptionProcessorBehavior`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
   at MediatR.Pipeline.RequestExceptionActionProcessorBehavior`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
   at MediatR.Pipeline.RequestExceptionActionProcessorBehavior`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
   at MediatR.Pipeline.RequestPostProcessorBehavior`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
   at MediatR.Pipeline.RequestPreProcessorBehavior`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
   at ErsatzTV.Pages.Playouts.RebuildPlayout(PlayoutNameViewModel playout) in /source/ErsatzTV/Pages/Playouts.razor:line 135
   at Microsoft.AspNetCore.Components.ComponentBase.CallStateHasChangedOnAsyncCompletion(Task task)
   at MudBlazor.MudBaseButton.OnClickHandler(MouseEventArgs ev)
   at Microsoft.AspNetCore.Components.ComponentBase.CallStateHasChangedOnAsyncCompletion(Task task)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle)

The settings:

I think duration here should be 09:00 because that is the length of time that the schedule item will be used in the playout, which will make it from 08:00 to 17:00. The error is probably because scheduling doesn't like wrapping around midnight (08:00 + 17:00 = 25:00), which may be considered a bug but I think it's unrelated to what you're trying to do.

 I assumed that I was supposed to input the stop time here, since the controls were the same as when using Start Time.
I haven't tested it yet, but I'm fairly sure it's just pebkac on my part. Thanks.

I just tested this, and unfortunately the error persist. I tried setting a start time of 08:00 and a Duration of 05:00,10:00 and a few other combinations without success

If you're able to join the discord I might be able to identify this bug more quickly by looking at your ersatztv.sqlite3 database (via DM).

Unfortunately I'm not a discord user, but I can share it via something else (like reddit?)
It's pretty easy to reproduce though:
Use jellyfin as backend,
Sync movie library,
Create normal collection from a bunch of movies,
Create schedule with said collection, using start time and duration (offline tail doesn't matter),
Try to generate playout, get error,
Profit?

I've definitely tried to reproduce and unfortunately those steps do not work consistently. I believe there's an edge case unaccounted for in your specific data, which is why your database would help. I'm jasondove on reddit if you want to dm me a link to your db that way.


bugfix: errors when an empty pipeline finishes with no data written

This is a corner case. It happens when an empty pipeline finishes before any data has been written.
var pipeline = require('stream-splicer');
pipeline([]).end();

/Users/zoubin/usr/src/zoubin/stream-splicer/index.js:45
        self._streams[0].end();
                        ^
TypeError: Cannot read property 'end' of undefined

Thanks for the patch and the reproduction case, which I've added to the test suite. All fixed in 1.3.2.


Change "More options" button text to "Try another option"

On the verify screens. Needs confirmation if this applies to registrations as well.
cc @silverstripeux

What did you mean by "registrations"? did you mean like when setting up account and registering the methods? There are no points in MFA setup flow where the user would need a "try another option" button. This only applies in the login flows.

@newleeland all good. They're exactly the same thing in principle, but we can keep different text between them if you'd like.

cc @sachajudd, still relevant?

Yeah happy to close.


Selection Sort in PHP

💥 Proposal
To implement Selection Sort in PHP
Have you read the Contributing Guidelines on Pull Requests?
YES

/assign


Reporting a vulnerability

Hello!
I hope you are doing well!
We are a security research team. Our tool automatically detected a vulnerability in this repository. We want to disclose it responsibly.  GitHub has a feature called Private vulnerability reporting, which enables security research to privately disclose a vulnerability. Unfortunately, it is not enabled for this repository.
Can you enable it, so that we can report it?
Thanks in advance!
PS: you can read about how to enable private vulnerability reporting here: https://docs.github.com/en/code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository

@igibek see also https://docs.gitops.weave.works/security/
thanks for reporting it!


[Docs] Create documentation for storeValue function

Describe the problem
We do not have documentation for our storeValue action today. The action can be triggered by the action selector of a widget such as the onClick of a button

Hey I am Hetu, one of the maintainers at Appsmith. This is a great issue for anyone looking to start contributing to the repo. Make sure you read our docs contributions guidelines before starting.
The signature of the function is mentioned here
I'm here if you need any help fixing this so feel free to tag me on this thread 😄

I want to take uo this issue

@kichloo go for it!

@Nikhil-Nandagopal , I see the issue is still open. Can you assign it to me ?

@pooja1198 Assigning this to you. Please make sure you read our docs contributions guidelines before starting and raise a PR in 2 days 🙂

@Nikhil-Nandagopal, @hetunandu Can I take this up as well as we need this page for sharing data across pages PR?

Go for it @deepakchethan


Handle Swagger slash basepath within Swagger UI Middleware

Fixes #1834 .
Changes proposed in this pull request:

Add slash before basePath

coverage: 94.211%. remained the same
when pulling 53e95a53011ee54b43cfe008e84da25f9026d8df on bugfix/swagger-slash-base-path
into 6dc943661dee4f979d4608a6dd8ec4c4aaaed2ee on main.


[WIP] Update content on Tanzu TAP page

Changed ordering and content for New and Featured content.

@BrianMMcClain, here is the PR we discussed where the New Content items are a bit jumbled. Or at least, not the Newest items.