text:
Details Layout has a small bit of blank space on the right causing scrollbar to appear

Explain the bug
E.g. after "Size" column, there's a tiny mini bit of an empty column that when you resize other columns (e.g. Name) to move the last column (in my case Size) to the very edge of the window, as indicated by its border-right of the Size column header, it causes a Horizontal scrollbar to appear, as if there's some text I've overflowed.
To reproduce

Open any folder, and assume you only have 3 columns. Name, Date modified, and Size.
Enlarge the Name columns width to move size to the far right of the window's edge.
You will notice a horizontal scrollbar appears as if you overflowed some text or content, but you haven't.

Expected behavior
It shouldn't show the scrollbar as there was no content in what was hidden.
Logfile
N/A. It's unnecessary.
Screenshots
As you can see below, I've moved the size column to the very edge, and it still thinks there's content there so it shows a scrollbar.

System Information

OS Version: Windows 11 21H2 22000.100
App version: v1.9.15.0

Additional comment
N/A

Thanks for opening this feedback item. That's done on purpose to always let you resize the last column easily. If there's no space you'd risk resizing the window instead.

I see now that its the same happening on the left-most column, a bit of space for resizing the column.
May I ask for an option in settings to remove or condense this then?

It could just make more sense to have it padded so that there will always be space whether the scrollbar is at the end or not.

This behavior it's the same when you resize a window with this view activated... it can become annoying.

As @gave92 mentioned, this is the intended behavior, and it lines up with other apps such as File Explorer.


text:
Fix release build issues with SQLite binaries

This is a fix for an issue reported in https://github.com/files-community/Files/pull/2655

@jakoss Could you verify that this does not add an extra SqLite binary to the package? An SQLBinary is already included due to AppCenter

@gave92 It seems like it does, but i'm not sure what to do about that. SQLitePCLRaw clearly does not work in current setup.
I can see binaries: e_sqlite3.dll and sqlite3.dll

@jakoss what happens if you update Microsoft.Data.Sqlite from 1.1.1 to 5.0.1?

@jakoss try updating Microsoft.Data.Sqlite from 1.1.1 to 5.0.1, seems to get rid of the extra dll

It compiles without extra dll, but it does not work with the exact exception from PR #2655

It compiles without extra dll, but it does not work with the exact exception from PR #2655

@jakoss dammit :) I'd really like to avoid adding a second sqlite binary. I'm going to a try few experiments too

I wonder if AppCenter can use this library or is it crashing silently in background. Because there's not much one can do if native library won't match..

@jakoss maybe you're right. Do you think the Default.Rd.xml could have somthing to do with this?

@jakoss maybe you're right. Do you think the Default.Rd.xml could have something to do with this?
I'm gonna try adding <Assembly Name="*Application*" Dynamic="Required All" /> to it. Is it something you tried already?

That's a possibility. Adding sqlite to rd.xml shouldn't be too difficult.

@gave92 Even though i worked with .NET for 10 years now - i don't have any prior experience with .NET Native or UWP. So i'm lost here more then you do :)

@jakoss @yaichenbaum I can confirm that changing the Default.Rd.xml fixes this 🚀🚀🚀

@gave92 The namespace is probably Microsoft.Data.Sqlite.

@yaichenbaum I hope so, that's what I'm trying right now. Release build is just sooo slow 😃

@gave92 I just took a look and it looks like it might actually be Microsoft.Data.Sqlite.Core.

@yaichenbaum I'll try that next. How did you guess?

@yaichenbaum I'll try that next. How did you guess?

That's what it comes up as under the references section in solution explorer.

Of course it was neither xD It was SQLitePCL
Going to open a PR with this

@jakoss I hope you don't mind if I close this PR. Thank you for your amazing work on #2655

No worries

source: gharchive/pull-request

authors: gave92 jakoss yaichenbaum

repo: files-community/Files

license: MIT

license_type: permissive

license_source: github-api


text:
Considerar remover a dependência do $http do repositório do Firebase

A idéia é substituir por um módulo genérico qualquer que faça o mesmo request. Com isto, dá para fazer o repositório ser inicializado em injetar o $http do Angular.

Resolvi remover e substituir pelo https://www.npmjs.com/package/browser-request

source: gharchive/issue

repo: filipedeschamps/insiderNews

license: mit

license_source: bigquery


text:
ARM64

Please, add arm64 image. Buildx can help.

Good idea. Do you feel like taking a stab at it?

Afaik, there's not yet a ARM64 compatible GraalVM, right?

Maybe I can try to help with it, but don't know how to use "if" in RUN. Need to compare TARGETPLATFORM (like that name) with linux/amd64 and linux/arm64, then download GraalVM. ARM64 builds named "aarch64"

authors: averyanalex findepi nightscape

repo: findepi/graalvm-docker


text:
Document code changes in releases

Add a tag comparison to the GitHub Releases so it's easier to see what's changed between versions.
Ideally this is automated by using the hooks from npm-version.

I've converted all tags to releases and added a changes trailer to their release notes.
The trailer has the following format:

Changes: https://github.com/findmypast-oss/git-mob/compare/<old-tag>...<new-tag>

repo: findmypast-oss/git-mob


text:
2023-11-13 - KDB Project Call Meeting Agenda

Date
Monday, November 13, 2023 - 9:30am ET / 2:30pm UK
// Second Monday of every month
Attendees

Fullname
Affiliation
GitHub Username

Meeting notices

FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact legal@finos.org with any questions.

FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

(5 min) Convene, roll call, welcome new people.
[ ] Display FINOS Antitrust Policy summary slide
[ ] Review Meeting Notices (see above)
(5 min) Approve previous meeting minutes.
(10 min) Takeaways from OSFF New York?

Data Lakehouse

Ideas to incorporate into kdb+ / KX Insights?

(10 min) Takeaways from Vectorize NY?

Retrieval-Augmented Generation might not necessarily be decided by speed.
Someone mentioned BuaBook to me.

(5 min) Walkthrough of https://github.com/finos/kdb/pull/98 .
(10 min) technical-documentation/ ideas continued

"Awesome XYZ" seems to be a popular name for GitHub repos hosting curated lists of resources:

https://github.com/EthicalML/awesome-production-machine-learning

Found "Awesome K" but not much momentum:

https://github.com/mkmik/awesome-k

Revisit HDB querying gotchas?

(5 min) kdb.ai / Document scraping

Downloads from RSS feeds of regulatory agencies:

https://github.com/synechron-finlabs/horizon-scanning-core

Downloads a variety of SEC filings from EDGAR:

https://github.com/sec-edgar/sec-edgar

(5 min) AOB, Q&A, Adjourn.

Decisions Made

Decision 1
Decision 2
...

Action Items

Action 1
Action 2
...

WebEx info
Webex

https://finos.webex.com/finos/j.php?MTID=me61719ca3c3295a7cc76762d78392bc3

Dial-in and Project Materials

US: +1-415-655-0003 US Toll
UK: +44-20319-88141 UK Toll
Access code: 2704 417 0390
GitHub Repos:

https://github.com/finos/kdb
https://github.com/finos/kdb-studio

Wiki Page:

https://finosfoundation.atlassian.net/wiki/spaces/DT/pages/329383945/kdb+Project

KDB Metrics on FINOS

https://metrics.finos.org/goto/033b15c80f0d08cab70f40f4358932f6

James McLeod / FINOS

Peter Gyorok/KX

Aaron Davies/Morgan Stanley

Jo :fox_face:

Gary Davies/Data Intellect

Rian Ó Cuinneagáin / KX

morning = (
    taxi.filter(pl.col("pickup_time") >= time(7), pl.col("pickup_time") < time(9))
    .select(["weekday", "trip_distance"])
    .group_by(pl.col("weekday"))
    .sum()
    .rename({"trip_distance": "morning_rush_taxi"})
)

Alvin Shih / Morgan Stanley

authors: adavies42 alvin-c-shih drgdavies gyorokpeter jshinonome mcleo-d rianoc

repo: finos/kdb


text:
Apply fix for false realizeInMemory calls during plan execution (edited)

What type of PR is this?
Bug Fix/ Feature Improvement

What does this PR do / why is it needed ?
 Modifies the way plan is generated by separating authDependency on the plan and transformAllocation, which helps resolve logical fallacy occurring with setting TA inside execution nodes, that later is used to determine if plan is realized in Memory.
Which issue(s) this PR fixes:
 PR responds to a keystone raised by user where plan fails to execute because it is unexpectedly realizing in Memory for their TDS Join operation.

@cla-bot[bot] check

repo: finos/legend-engine


text:
integration: Pins juju to 3.1 for integration tests

Currently, the Juju client version installed for the integration tests is 2.9, while the Python Juju library is unpinned (currently installed version: 3.2). Because of this, the integration tests are failing with the following error [1]:
juju.errors.JujuConnectionError: juju server-version 2.9.44 not supported

Pins the installed version of juju to 3.1, which is the same as the version mentioned in the Juju Legend deployment guide.
Additionally, switches microk8s version to 1.27-strict/stable, as juju 3.0 and newer requires microk8s to be strictly confined.
Constrains the Python juju to lower than 3.2.
[1] https://github.com/finos/legend-juju-bundle/actions/runs/5809373229/job/15748021952?pr=46
xref: https://github.com/finos/legend-juju-bundle/pull/45
(cherry picked from commit 672e0fa235d38a72d5637edd0760ae0515a3c8db)

Integration tests now pass on this branch. Merging.

repo: finos/legend-juju-bundle


text:
Add support for Android Architecture Components

#718

@samtstern see https://github.com/firebase/FirebaseUI-Android/issues/718#issuecomment-317928588.

@SUPERCILEX thanks for experimenting with this.  I am not as familiar with these components as you are, so I'm going to ask all the dumb questions that come to mind.

It's a shame LiveData wasn't a fit for FirebaseUI Database, but I'm not complaining. This LGTM.

@TheCraftKid not really. Dunno if you've used AC much, but the point of LiveData as I understand it is to be able to add a listener that's lifecycle aware and won't leak contexts. This PR basically retrofits the Firebase listeners to be lifecycle aware which is what LiveData is for.
As I see it, LiveData's main use for retrofitting libraries that don't yet support AC and for internal app listeners.
Feel free to correct me if I'm wrong! 😄

Kind of a late response here, but LiveData is about more than just having a lifecycle-aware listener (although that's its main benefit). MediatorLiveData (esp. via Transformations) can create a whole system of chained LiveDatas where updates in one can trigger updates in others, leading to a much more functional style of programming.
I'm curious what would preclude a small shim class to translate between a ValueEventListener and a LiveData? I've written an example at https://gist.github.com/keyboardr/8259533ec74f703f9e999f103a6b1135

@keyboardr you are right and I think simple Live Data classes like that could be useful!  Do you mind filing a separate issue for that in particular?
Also I had this same discussion with someone at the Firebase summit in Amsterdam, was that you?

Not me, but glad to see I'm not the only one with this idea. FWIW the shim linked above has been working decently well for me, but hasn't yet been rigorously validated. I'll file an issue to get something canonical made.

@keyboardr Oh no, you found my old comments! 😆 Yeah, I've learned way more over the past few months.
Anyway, that sounds like a really good idea. I've written some classes to manage a FirestoreArray's lifecycle, but not a specific document. I think it would be really nice to add a whole bunch of lifecycle aware classes like that. For example, I'd like to have the adapter save its FirestoreArray across screen rotations, and lifecyclize the other database classes. Would you like to open an issue or should I?

You're probably more familiar with FirebaseUI in particular (I've used Firebase in a few projects, but haven't used it for directly driving UI), so you'd probably have more context about what kinds of wins can be had here.

SGTM, will do! 😄

authors: SUPERCILEX TheCraftKid keyboardr samtstern

repo: firebase/FirebaseUI-Android


text:
FUITableViewDataSource raising  'attempt to perform an insert and a move to the same index path'

Step 2: Describe your environment

Objective C or Swift: ____Swift
iOS version: _____9.3
Firebase SDK version: _____3.6
FirebaseUI version: ____2.0.2
CocoaPods Version: ____1.1

Step 3: Describe the problem:
I have MasterVC table view controller and DetailVC view controller. MasterVC uses a FUITableViewDataSource with a query using queryOrderedByValue.
When an update is made in DetailVC that causes the the .child_changed event to trigger in the MasterVC an NSInternalInconsistencyException is raised with reason: 'attempt to perform an insert and a move to the same index path'
Steps to reproduce:

_____Select a row in the MasterVC to navigate to the DetailVC
_____Update the record in the DetailVC which triggers the observer in the MasterVC

Observed Results:

What happened?  The app crashes with the error described above. However, when the queryOrderedByValue is removed from the query it functions as expected

Expected Results:

What did you expect to happen? I would expect that when the .child_changed event is triggered in the MasterVC the location of the record in the UITableView would be ordered to the top.

It is the attempt to re-order the cells in the UITableView that is causing the exception

Can you post the code here? This is most likely a bug on our end.

Sure. The below example updates the display order of a Color to 0 in the DetailVC. This will trigger the .child_changed event in the MasterVC, which changes the order of rows in the tableView.
The following example assumes a reference colors with firebase data model as follows:
{   "blue" : {     "displayOrder" : 0   },   "green" : {     "displayOrder" : 2   },   "red" : {     "displayOrder" : 1   } }
Master TableViewController:
`
import UIKit
import Firebase
import FirebaseDatabaseUI
class MasterTableViewController: UITableViewController {
var ref: FIRDatabaseReference!
var dataSource: FUITableViewDataSource!

override func viewDidLoad() {
    super.viewDidLoad()

    ref = FIRDatabase.database().reference().child("colors")

    let query = ref.queryOrdered(byChild: "displayOrder")

    dataSource = FUITableViewDataSource(query: query, view: tableView, populateCell: { (tableView, indexPath, snapshot) -> UITableViewCell in
        let cell = tableView.dequeueReusableCell(withIdentifier: "reuseIdentifier", for: indexPath)

        cell.textLabel?.text = snapshot.key

        return cell
    })

    tableView.dataSource = dataSource

}

override func prepare(for segue: UIStoryboardSegue, sender: Any?) {
    let destVC = segue.destination as! DetailViewController

    destVC.colour = tableView.cellForRow(at: tableView.indexPathForSelectedRow!)?.textLabel?.text
}

}`
Detail View Controller:
`import UIKit
import Firebase
class DetailViewController: UIViewController {
var colour: String!

@IBOutlet weak var colourLabel: UILabel!

override func viewDidLoad() {
    super.viewDidLoad()

    // Do any additional setup after loading the view.

}

@IBAction func changeDisplayOrder(_ sender: Any) {

    let ref = FIRDatabase.database().reference().child("colors").child(colour)

    ref.updateChildValues(["displayOrder" : 0])

}

}`

This affects us too. It seems to be triggered any time an existing record is updated, and one of the updated fields is the one that is used to do sorting in the query.
I actually tried to go around this using FUISortedArray, but got bitten by https://github.com/firebase/FirebaseUI-iOS/issues/234#issuecomment-277953684

I think this was introduced when we started batching updates.

This is fixed in the latest release (by dropping batch updates in table views).

authors: codemodouk morganchen12 swftvsn

repo: firebase/FirebaseUI-iOS


text:
High Severity Vulnerability on  node-forge-0.10.0.tgz (Vulnerable Library)

JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.
Library home page: https://registry.npmjs.org/node-forge/-/node-forge-0.10.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/google-p12-pem/node_modules/node-forge/package.json
Dependency Hierarchy:
firebase-admin-10.0.2.tgz (Root Library)
storage-5.3.0.tgz
gcs-resumable-upload-3.1.1.tgz
google-auth-library-6.1.2.tgz
gtoken-5.0.4.tgz
google-p12-pem-3.0.3.tgz
❌ node-forge-0.10.0.tgz (Vulnerable Library)

Admin SDK v10.0.2 is on "node-forge": "^1.0.0" https://github.com/firebase/firebase-admin-node/blob/5b0a49ba0dbc22dc7ef8a5646d028f1b55b3e9bc/package.json#L168
What you see could have been a cached version in your development environment or pulled by a different package. You should also be able to just update node-forge manually in you environment. Thanks!

node-forge has a transient dependency on firebase-admin-10.0.2.tgz (Root Library) as shown in the description. I can't manually update it. For me, even after updating to 10.0.2 the node-forge version stays at 0.10.0. How do I make this work?

Please see my answer on https://github.com/firebase/firebase-admin-node/issues/1634

authors: biswajit-ibm lahirumaramba

repo: firebase/firebase-admin-node


text:
Not clear how to set channel for messaging

There's value mentions of android_channel_id in some stackoverflow posts, but nothing in the docs or in this repo. How do you set the channel? The console has a field for it even though the API makes no mention of it.

NotificationMessagePayload type is defined as follows:
type NotificationMessagePayload = {
    tag?: string;
    body?: string;
    icon?: string;
    badge?: string;
    color?: string;
    sound?: string;
    title?: string;
    bodyLocKey?: string;
    bodyLocArgs?: string;
    clickAction?: string;
    titleLocKey?: string;
    titleLocArgs?: string;
    [key: string]: string | undefined;
  };

Since it allows arbitrary keys, I would expect that if you just add android_channel_id under notification, it will just work.

Can something be added to the docs? It's strange the web console has a field for this and nothing is mentioned in the docs for how to do it programmatically.

You can still use the legacy APIs for this. The new REST API doesn't support it as far as I can tell: https://firebase.google.com/docs/reference/fcm/rest/v1/projects.messages#AndroidConfig
SDK's admin.messaging.send() API cannot support it until it's exposed in the REST interface.

hey guys, bringing this old thread back to live. it took me a few days to find out how to use firebase admin sdk with node.js and assign a channel ID to a notification. thanks for the post above I just added "android_channel_id" to my notification payload object, see below.
It works, but is it the correct way?
                        //prepare firebase cloud messaging push notification
                        var notification_message =  {                                                                                notification: {
                                        title: topic.toString(),                                                                                body: message.toString(),
                                        android_channel_id: config.mqtt_subscriptions[index].channelID
                                }
                        };

That looks correct for the legacy API.
Channel ID is also supported by the new (v1) API now: https://firebase.google.com/docs/reference/admin/node/admin.messaging.AndroidNotification#optional-channelid


text:
[firebase_auth] token issued by createCustomToken are not valid with emulated in <> project

As per the documentation:
<< For security reasons, the Authentication emulator issues unsigned ID tokens, which are only accepted by other Firebase emulators, or the Firebase Admin SDK when configured. >>
So when there is an env variable FIREBASE_AUTH_EMULATOR_HOST="127.0.0.1:9099"  firebase admin is supposed to give unsigned tokens via the emulator, which it does not:
The following:
    const user = await admin.auth().createUser({ uid: randomUUID() });
    const jwt = await admin.auth().createCustomToken(user.uid);

Results in:
Firebase ID token has incorrect "aud" (audience) claim. Expected "demo-test" but got "https://identitytoolkit.googleapis.com/google.identity.identitytoolkit.v1.IdentityToolkit"

Were you able to solve? I'm experiencing the same issue.

Dealing with the same problem. The verifyIdToken function expects the project id in the aud except the token created by the same instance of the auth emulator uses https://identitytoolkit.googleapis.com/google.identity.identitytoolkit.v1.IdentityToolkit

I get this error only if i try to verify the token generated by createCustomToken.
If you pass the token to signInWithCustomToken in the client app then get the user token with auth.currentUser.getIdToken your will notice the token is slightly different and claims are the expected ones.
You can then verify this token in your backend and no errors show up.

I am facing the same issue.
At the moment I am doing what @luisjoserivera said but on the backend. I initialise a client instance of FB with the same credentials and then simulate a login, getId, logout to get the ID token.

I'm having the same problem. createCustomToken doesn't respect the emulator.

authors: cedvdb karthikrao5 luisjoserivera mp3por shelbycotton wieringen


text:
FR: Search users by name or email address

I'd love to be able to search users by their display name or part of a display name, but I also can't see any reason not to allow the search to be done by email address (eg. finding all users with a gmail.com email).
Right now my only option is to list all users and do the work manually. It's wasteful and won't scale. Ultimately it would also be worth to be able to perform simple queries such as count, so I could display how many users I have. But I'd settle for being able to search display name and email addresses.

I don't think search functionality is really in the roadmap for Firebase Auth. Full text search is always a complicated use case, and even the Firebase database solutions don't support it natively. I guess the only solution I can think of is indexing the user information in a separate system like Algolia or ElasticSearch, and then facilitating search through that. You can use a Cloud Function to automatically index all new user data into the search engine, and keep them up to date.
Checkout this solution proposed for Firestore: https://firebase.google.com/docs/firestore/solutions/search
You can do that same with Firebase Auth.
@bojeil-google wdyt?

As @hiranya911 mentioned, we don't have any plan to allow rich query searching in Firebase Auth. We will allow searching by providing list of emails, uids, phone numbers or federated IDs, nothing beyond that. I recommend the alternatives already suggested by @hiranya911.

There's still no plans to support this feature. Please file via Firebase Support is further follow up is needed.

authors: bojeil-google diegofrata hiranya911


text:
Login v2 for Ionic-Auth

@sararob Can you verify this builds?

@mcdonamp Can you verify this builds?

@davideast looks like it does to me

authors: davideast mcdonamp

repo: firebase/firebase-angular-starter-pack


text:
gRPC abort in grpc::Channel::PerformOpsOnCall

[REQUIRED] Step 2: Describe your environment

Xcode version: 10.1
Firebase SDK version: 5.13.0
Firebase Component: Firestore
Component version: Latest one included in 5.13.0 pod

[REQUIRED] Step 3: Describe the problem
We never saw this crash before. We thought it might be related to the recent switch from gRPC in #1968 and related ones.
The app is currently running in a small internal beta test with about 20 Users so far. The crash occurred on 3 different devices for 3 users from those 20. (iPhone 6, iPhone 6s, iPhone X. All are running iOS 12.0.1 or newer)
Steps to reproduce:
As far as we can see from our analytics screen views and the code we can just believe that the following state was in the app:

We had one snapshot listener open which was about to being disposed (the user left the screen where this snapshot listener was running)
It might have been that the document the snapshot listener was attached to was deleted or modified while the listener has been disposed

Stacktrace:
Crashed: com.google.firebase.firestore
SIGABRT ABORT 0x00000001d429b104

Crashed: com.google.firebase.firestore
0  libsystem_kernel.dylib         0x1d429b104 __pthread_kill + 8
1  libsystem_pthread.dylib        0x1d4316070 pthread_kill$VARIANT$mp + 380
2  libsystem_c.dylib              0x1d41f2d78 abort + 140
3  grpcpp                         0x10203d414 non-virtual thunk to grpc::Channel::PerformOpsOnCall(grpc::internal::CallOpSetInterface*, grpc::internal::Call*) (channel_cc.cc)
4  APP_NAME                        0x10139345c grpc::ClientAsyncReaderWriter<grpc::ByteBuffer, grpc::ByteBuffer>::Finish(grpc::Status*, void*) (call.h:680)
5  APP_NAME                        0x101393238 firebase::firestore::remote::GrpcStream::Shutdown() (functional:1862)
6  APP_NAME                        0x1013931c8 firebase::firestore::remote::GrpcStream::FinishImmediately() (grpc_stream.h:186)
7  APP_NAME                        0x1013935c0 firebase::firestore::remote::GrpcStream::WriteAndFinish(grpc::ByteBuffer&&) (optional.h:184)
8  APP_NAME                        0x1013a9704 firebase::firestore::remote::WriteStream::TearDown(firebase::firestore::remote::GrpcStream*) (byte_buffer.h:88)
9  APP_NAME                        0x1013a4a04 firebase::firestore::remote::Stream::Close(firebase::firestore::util::Status const&) (memory:2595)
10 APP_NAME                        0x1013a4868 firebase::firestore::remote::Stream::Stop() (memory:2595)
11 APP_NAME                        0x1012fb454 firebase::firestore::util::AsyncQueue::ExecuteBlocking(std::__1::function<void ()> const&) (atomic:921)
12 APP_NAME                        0x1013032a8 firebase::firestore::util::internal::TimeSlot::InvokedByLibdispatch(void*) (executor_libdispatch.mm:173)
13 libdispatch.dylib              0x1d413e484 _dispatch_client_callout + 16
14 libdispatch.dylib              0x1d40e183c _dispatch_continuation_pop$VARIANT$mp + 412
15 libdispatch.dylib              0x1d40f1bac _dispatch_source_invoke$VARIANT$mp + 1704
16 libdispatch.dylib              0x1d40e5aac _dispatch_lane_serial_drain$VARIANT$mp + 284
17 libdispatch.dylib              0x1d40e6728 _dispatch_lane_invoke$VARIANT$mp + 432
18 libdispatch.dylib              0x1d40eeec8 _dispatch_workloop_worker_thread + 600
19 libsystem_pthread.dylib        0x1d43200dc _pthread_wqthread + 312
20 libsystem_pthread.dylib        0x1d4322cec start_wqthread + 4

com.google.firebase.firestore.rpc

com.google.firebase.firestore.rpc
0  libsystem_kernel.dylib         0x1d429d000 poll + 8
1  grpc                           0x101f39a3c pollset_work(grpc_pollset*, grpc_pollset_worker**, long long) (ev_poll_posix.cc:986)
2  grpc                           0x101f3c308 pollset_work(grpc_pollset*, grpc_pollset_worker**, long long) (ev_posix.cc:264)
3  grpc                           0x101f31270 cq_next(grpc_completion_queue*, gpr_timespec, void*) (completion_queue.cc:927)
4  grpcpp                         0x10203e968 grpc::CompletionQueue::AsyncNextInternal(void**, bool*, gpr_timespec) (completion_queue_cc.cc:57)
5  APP_NAME                        0x1012fdb50 firebase::firestore::remote::Datastore::PollGrpcQueue() (datastore.mm:128)
6  APP_NAME                        0x101303e6c firebase::firestore::util::internal::DispatchAsync(NSObject<OS_dispatch_queue>*, std::__1::function<void ()>&&)::$_0::__invoke(void*) (executor_libdispatch.mm:57)
7  libdispatch.dylib              0x1d413e484 _dispatch_client_callout + 16
8  libdispatch.dylib              0x1d40e5be0 _dispatch_lane_serial_drain$VARIANT$mp + 592
9  libdispatch.dylib              0x1d40e6728 _dispatch_lane_invoke$VARIANT$mp + 432
10 libdispatch.dylib              0x1d40eeec8 _dispatch_workloop_worker_thread + 600
11 libsystem_pthread.dylib        0x1d43200dc _pthread_wqthread + 312
12 libsystem_pthread.dylib        0x1d4322cec start_wqthread + 4

Thread #1

Thread
0  libsystem_kernel.dylib         0x1d429b374 __select_nocancel + 8
1  libsystem_dnssd.dylib          0x1d4232b78 deliver_request + 1000
2  libsystem_dnssd.dylib          0x1d4233ea0 DNSServiceCreateConnection + 116
3  libsystem_info.dylib           0x1d424c244 _mdns_search_ex + 940
4  libsystem_info.dylib           0x1d424bdac _mdns_search + 128
5  libsystem_info.dylib           0x1d424b2a8 mdns_addrinfo + 940
6  libsystem_info.dylib           0x1d4251118 search_addrinfo + 264
7  libsystem_info.dylib           0x1d42551c4 si_addrinfo + 1672
8  libsystem_info.dylib           0x1d4248964 _getaddrinfo_internal + 196
9  libsystem_info.dylib           0x1d4248894 getaddrinfo + 56
10 grpc                           0x101f6dba0 posix_blocking_resolve_address(char const*, char const*, grpc_resolved_addresses**) (resolve_address_posix.cc:87)
11 grpc                           0x101f6de98 do_request_thread(void*, grpc_error*) (resolve_address_posix.cc:157)
12 grpc                           0x101f3d2b0 GrpcExecutor::RunClosures(grpc_closure_list) (executor.cc:70)
13 grpc                           0x101f3d440 GrpcExecutor::ThreadMain(void*) (executor.cc:175)
14 grpc                           0x101f93338 grpc_core::(anonymous namespace)::ThreadInternalsPosix::ThreadInternalsPosix(char const*, void (*)(void*), void*, bool*)::'lambda'(void*)::__invoke(void*) (thd_posix.cc:101)
15 libsystem_pthread.dylib        0x1d431f2ac _pthread_body + 128
16 libsystem_pthread.dylib        0x1d431f20c _pthread_start + 48
17 libsystem_pthread.dylib        0x1d4322cf4 thread_start + 4

Thread #2

Thread
0  libsystem_kernel.dylib         0x1d429af0c __psynch_cvwait + 8
1  libsystem_pthread.dylib        0x1d4317cd8 _pthread_cond_wait$VARIANT$mp + 636
2  grpc                           0x101f8c950 gpr_cv_wait (sync_posix.cc:91)
3  grpc                           0x101f95e64 timer_thread(void*) (trace.h:72)
4  grpc                           0x101f93338 grpc_core::(anonymous namespace)::ThreadInternalsPosix::ThreadInternalsPosix(char const*, void (*)(void*), void*, bool*)::'lambda'(void*)::__invoke(void*) (thd_posix.cc:101)
5  libsystem_pthread.dylib        0x1d431f2ac _pthread_body + 128
6  libsystem_pthread.dylib        0x1d431f20c _pthread_start + 48
7  libsystem_pthread.dylib        0x1d4322cf4 thread_start + 4

Thread #3

Thread
0  libsystem_kernel.dylib         0x1d429af0c __psynch_cvwait + 8
1  libsystem_pthread.dylib        0x1d4317cd8 _pthread_cond_wait$VARIANT$mp + 636
2  grpc                           0x101f8c940 gpr_cv_wait (sync_posix.cc:89)
3  grpc                           0x101f95e64 timer_thread(void*) (trace.h:72)
4  grpc                           0x101f93338 grpc_core::(anonymous namespace)::ThreadInternalsPosix::ThreadInternalsPosix(char const*, void (*)(void*), void*, bool*)::'lambda'(void*)::__invoke(void*) (thd_posix.cc:101)
5  libsystem_pthread.dylib        0x1d431f2ac _pthread_body + 128
6  libsystem_pthread.dylib        0x1d431f20c _pthread_start + 48
7  libsystem_pthread.dylib        0x1d4322cf4 thread_start + 4

In the "Keys" entry of the crash log there's the following entry:
crash_info_entry_0
abort() called

These are all stack traces related to firestore / grpc i believe. There is no other information in the crash log.
I hope i could provide some information to maybe find the cause of this crash.
Kind regards

Thank you for the report. This certainly looks related to the recent gRPC transition. I will try to reproduce this and will follow up here.

We have exactly the same issue.

@ntnmrndn Does your stack trace also look identical?

@var-const I have the same stack trace, and a second one in addition (almost identical).
See:

Crashed: com.google.firebase.firestore
0  libsystem_kernel.dylib                0x19ac5f104 __pthread_kill + 8
1  libsystem_pthread.dylib               0x19acde998 pthread_kill$VARIANT$armv81 + 296
2  libsystem_c.dylib                     0x19abb6d78 abort + 140
3  grpcpp                                0x1054d5020 grpc::Channel::PerformOpsOnCall(grpc::internal::CallOpSetInterface*, grpc::internal::Call*) + 622
4  Alpaca                                0x1031c272c grpc::ClientAsyncReaderWriter<grpc::ByteBuffer, grpc::ByteBuffer>::Finish(grpc::Status*, void*) (async_stream.h:570)
5  Alpaca                                0x1031c203c firebase::firestore::remote::GrpcStream::Shutdown() (functional:1862)
6  Alpaca                                0x1031c1eb8 firebase::firestore::remote::GrpcStream::FinishImmediately() (grpc_stream.h:186)
7  Alpaca                                0x1031c2bd8 firebase::firestore::remote::GrpcStream::WriteAndFinish(grpc::ByteBuffer&&) (optional.h:184)
8  Alpaca                                0x10321fd04 firebase::firestore::remote::WriteStream::TearDown(firebase::firestore::remote::GrpcStream*) (byte_buffer.h:88)
9  Alpaca                                0x10320a9d8 firebase::firestore::remote::Stream::Close(firebase::firestore::util::Status const&) (memory:2595)
10 Alpaca                                0x10320a3ec firebase::firestore::remote::Stream::Stop() (memory:2595)
11 Alpaca                                0x1030090f0 firebase::firestore::util::AsyncQueue::ExecuteBlocking(std::__1::function<void ()> const&) (atomic:921)
12 Alpaca                                0x10302b97c firebase::firestore::util::internal::TimeSlot::Execute() (executor_libdispatch.mm:187)
13 Alpaca                                0x10302b7a8 firebase::firestore::util::internal::TimeSlot::InvokedByLibdispatch(void*) (executor_libdispatch.mm:173)
14 libclang_rt.asan_ios_dynamic.dylib    0x105af7030 asan_dispatch_call_block_and_release + 312
15 libdispatch.dylib                     0x19ab02484 _dispatch_client_callout + 16
16 libdispatch.dylib                     0x19aad8e14 _dispatch_continuation_pop$VARIANT$armv81 + 404
17 libdispatch.dylib                     0x19aae8ab4 _dispatch_source_invoke$VARIANT$armv81 + 1704
18 libdispatch.dylib                     0x19aadce84 _dispatch_lane_serial_drain$VARIANT$armv81 + 248
19 libdispatch.dylib                     0x19aaddaf4 _dispatch_lane_invoke$VARIANT$armv81 + 412
20 libdispatch.dylib                     0x19aae5f14 _dispatch_workloop_worker_thread + 584
21 libsystem_pthread.dylib               0x19ace40dc _pthread_wqthread + 312
22 libsystem_pthread.dylib               0x19ace6cec start_wqthread + 4

We sadly could not reproduce this crash in our development environment yet but as soon as I have more information I'll provide it here.

I'm also getting this as well

I'm downgrading to FirebaseFirestore 0.14.0 to see if it fixes the issue since #1968 was merged 23 days ago and 0.14.0 is the last build before

One thing that I found a little weird is that there is one function I would expect to see in the call stack that isn't there. To clarify, in all the call stacks I see, execution goes directly from GrpcStream::Shutdown to grpc::ClientAsyncReaderWriter::Finish. I would expect to see GrpcStream::FinishCall in-between. Perhaps it's just optimized away, but just to double-check, it would be helpful for me to see how GrpcStream::Shutdown() function looks on your end -- can I ask for anyone to find grpc_stream.cc file from FirebaseFirestore pod and post the contents of that function (Shutdown) here? (or just attach the whole file, whichever is easier)

Ignore my previous post; looks like that function can indeed be optimized away.

@zackshapiro can you please share how to deal with the downgrade. We used
`  pod 'FirebaseCore', '~> 5.1.7' #, :git => 'https://github.com/firebase/firebase-ios-sdk.git', :branch => 'master
pod 'FirebaseFirestore', '~> 0.14.0' #, :git => 'https://github.com/firebase/firebase-ios-sdk.git', :branch => 'master'
pod 'Firebase/Database'
pod 'Firebase/Storage'
pod 'Firebase/Messaging'
pod 'Firebase/Performance'
pod 'Firebase/RemoteConfig'
pod 'Firebase/InAppMessagingDisplay'
#All FirebaseUI
Only pull in FirebaseUI Firestore features
pod 'FirebaseUI/Firestore'`
However, we faced this error:
`[!] CocoaPods could not find compatible versions for pod "Firebase/Firestore":
In Podfile:
FirebaseUI/Firestore was resolved to 5.2.2, which depends on
Firebase/Firestore
Specs satisfying the Firebase/Firestore dependency were found, but they required a higher minimum deployment target.
CocoaPods could not find compatible versions for pod "FirebaseFirestore":
In Podfile:
FirebaseFirestore (~> 0.14.0)
FirebaseUI/Firestore was resolved to 5.2.2, which depends on
  Firebase/Firestore was resolved to 5.13.0, which depends on
    FirebaseFirestore (= 0.15.0)

`
Any ideas?

We found a bug which might be the cause of the issue (hard to say with full confidence, because the issue is so hard to reproduce, but the symptoms look similar). We're actively working on a fix, and I will post an update here as soon as I have it.

@businessengine I just bumped the version of FirebaseFirestore down from 0.15.0 to 0.14.0 and did a pod install. That's it :)

@var-const Thank you very much for your work on this! Very appreciated!

+1

Update: I merged a PR to master which I believe might fix the issue. However, because the issue is so difficult to reproduce, it's hard to know whether this fix covers all possible cases.
It would be super helpful if anyone could temporarily modify their podfiles to get Firestore from the current master branch and give it a try. The instructions are here, let us know if you run into any difficulties with this process. Once we're confident that the issue is fully resolved, we'll try to release the fix ASAP.
Additionally, it would also be very helpful if you could enable logging in Firestore (if you're using Swift, it can be done via FirebaseConfiguration.shared.setLoggerLevel(.debug)) and attach the device/emulator logs here in case you experience crashes (hopefully not).

@pschneider @zackshapiro @businessengine
Any chance you could try out our fix?
Add this to your Podfile for testing:
pod 'FirebaseCore', :git => 'https://github.com/firebase/firebase-ios-sdk.git', :branch => 'master'
pod 'FirebaseFirestore', :git => 'https://github.com/firebase/firebase-ios-sdk.git', :branch => 'master'

Thanks @var-const for the quick fix on this. We have made a build with this fix and will monitor to see if the crash is gone.

@wilhuff We've pointed to the fix in our app as well. Unfortunately the crash also didn't happen for us anymore since I've created the issue (I guess the internal test usage of the app is probably to low right now) and therefor it will be hard to really verify this. But I'll report back if we can see the crash again.

We confirm that no crash for the last 12hours since the fix was deployed!

Just a heads up that I am also seeing the exact same crash on the latest Firestore version. Will deploy the latest fix on my test environment and see if it still reproduces.
Thanks for the quick work on trying to fix this!

(I've updated the title here to avoid the "non-virtual thunk" because that description was misleading.)
At this point we haven't been able to reproduce this on device, but given the stack were able to recreate this in unit tests added in #2146. We believe that fixes this issue and it will go out with the next release.

Thanks for all of your work on this. Really appreciate it and so quickly.
What does this functionality improve or enable that wasn't there before? Thanks

I'm not sure I understand the question. Do you mean what did our fix change? The PR notes describe the underlying problem and the changes to address it so we didn't repeat that here. However, maybe you meant something else though--could you clarify which functionality you're inquiring about?

A colleague has pointed out that you may have been inquiring why we're migrating our usage C++ internally. This doesn't really benefit existing users at all but the point of the project is to make Firestore compatible with the Firebase Games SDKs, which are available in C++ and Unity and also run on Windows and Linux. Our eventual goal here is to share the core of this Firestore codebase among all those efforts, so we're moving away from Objective-C as the primary implementation language.

@wilhuff Yeah I was more inquiring what benefits to my company, if any, these changes had aside from what's in 0.14.0 and if there was any urgency for me to upgrade our pod. I understand that your goal is to make Firestore compatible with the games SDK. Thanks for explaining

Our release notes list changes of note across Firebase products. If you're just interested in Firestore, the release notes come from our CHANGELOG.
Note that while we're putting a release together the CHANGELOG may have notes about changes that haven't yet made it out to CocoaPods. For example, as of this writing the 0.16.1 release of Firestore is in the CHANGELOG (and includes the fix for this issue) but is not yet available.

Just checking whether a new release will be pushed out soon?
I am a bit in a bind as I don't want to push my app with this version given the random fatal errors this issue create (I've experienced it 4-5 times a week on my test build) and when rolling back to previous versions 5.11.0 or 5.12.0 either give me the GoogleAppMeasurement issue #2151 (wrong version) or the #2102 issue at build (multiple commands produce).
If someone could point me to the last stable version that would be great! I tried rolling back to 5.10.0 but then get the #2151 error again (and I don't seem to be able to find the GoogleAppMeasurement version that would work with 5.10.0), so if you could point me to the right dependencies on GoogleAppMeasurement that would be great.
Thanks!

@fschaus 5.15.0 is planned to be pushed out in the next few work days.  For some older versions, the GoogleAppMeasurement needs to be explicitly forced to match the FirebaseAnalytics version in the Podfile.

@fschaus You need to specify a correct version in your podfile. Maybe you can checkout an older version of your podfile.lock and use that ?
It's definitely an issue in the pod spec tho...

Thanks for your work on this one guys. Intending to hold out for 5.15.0 (unless it's arriving after the holidays 😄).

Same issue here as well

This comment isn’t actionable.
This issue was filed against Firebase 5.13.0 and was fixed in 5.15.0. If you’re using a version prior to that point, please upgrade. If you’re using Firebase 5.15.0 or later please open a new issue with all the details.

some issue like this .
how can I fix it？

@EvenDu This comment isn’t actionable.
This issue was filed against Firebase 5.13.0 and was fixed in 5.15.0. If you’re using a version prior to that point, please upgrade. If you’re using Firebase 5.15.0 or later please open a new issue with all the details

authors: EvenDu StackHelp businessengine edwardbeecroft fschaus mikelehen ntnmrndn paulb777 pschneider var-const wilhuff zackshapiro

repo: firebase/firebase-ios-sdk


text:
Zip: Stop including Swift specific frameworks

Now that Swift specific APIs are now distributed in the standard xcframeworks, there's no reason to include separate Swift xcframeworks in the zip distro.

Should this be treated as a breaking change? I'm wondering since it would likely break clients that have tooling to process the zip distribution.

We have not treated changing dependencies in the zip as a breaking change.
We consider the contract to be the README instructions - primarily,  copying everything from the product directory.

Confirmed manually the README changes and that the zip artifacts no longer include the five Swift.xcframeworks.
Ready for review but will wait until 10.18.0 settles to merge.


text:
[Question] androidx.fragment Version 1.0.0 is out of date.

[REQUIRED] Please fill in the following fields:

Unity editor version: 2020.3.38f1
Firebase Unity SDK version: 11.3.0
Source you installed the SDK: FirebaseMessaging.unitypackage
Problematic Firebase Component:
Other Firebase Components in use:
Additional SDKs you are using:
Platform you are using the Unity editor on: Mac
Platform you are targeting: Android
Scripting Runtime: IL2CPP
Pre-built SDK from the website or open-source from this repo: website

[REQUIRED] Please describe the question here:
When uploading the AppBundle that uses FCM to Google Play Console, the following warning was displayed:
'The developer of androidx.fragment:fragment (androidx.fragment:fragment) has reported version 1.0.0 as outdated. Consider upgrading to one of the following versions before publishing a new release: 1.1.0+.'

After contacting Firebase Support, they responded that the latest varsion (currently 1.6.0) is available, so we are considering taking action to add this to the mainTemplate.gradle of the Unity project.
Regarding the warning about the androidx.fragment version, do you have any plans to address this in Firebase SDK, and if so, when can it be expected to be provided?

Hi @YonahaShota,
Thanks for bringing this to our attention. The cause of this version may lie within the External Dependency Manager for Unity (EDM4U) rather than the Firebase SDK. That said, I've relayed this to the team. I'm unable to provide a timeline as of writing, but you may refer to this thread for updates.
In the meantine, you made add the following lines of code in your Dependencies.xml file to override the older version:
<dependencies>
<androidPackages>
<androidPackage spec="androidx.fragment:fragment:1.1.0" />
</androidPackages>
</dependencies>

Hi all,
Investigating this further, the problem is that a handful of our dependencies, like Play Services (and the Firebase Android SDK) are currently set to use that version.  They are working on updating them, but not sure when that will be available.
In the meantime, the suggestion above, adding that to the dependencies files (or if you are using a custom gradle file, you can likely do a similar change in that) is the best course of action if you want to get rid of the warning.

authors: YonahaShota a-maurice paulinon

repo: firebase/firebase-unity-sdk


text:
Exif function example, fix "metadata.downloadURLs" deprecated

Fix error message: "Cannot read property '0' of undefined"
Root cause: Storage API FullMetadata.downloadURLs is deprecated, ref:https://firebase.google.com/docs/reference/js/firebase.storage.FullMetadata.html#downloadurls
Replace with Reference.getDownloadURL, https://firebase.google.com/docs/reference/js/firebase.storage.Reference.html#getdownloadurl

@googlebot I signed it!

@googlebot I signed it!

Adding a note that I couldn't get this to work (node 12).  I kept getting an error that downloads[0] wasn't an object. I switched back to the "deprecated" version and now it works.  Might have trouble later, if so I'll come back and update.

authors: mxlius ramblescout

repo: firebase/functions-samples


text:
[Bug] Crashlytics is not being enabled (Did not register exception handlers: Crashlytics SDK was not initialized)

[REQUIRED] Please fill in the following fields:

Unity editor version: 2019.4.14f1 and 2020.1.17f1
Firebase Unity SDK version: 7.1.0 and 6.16.1
Source you installed the SDK: both (.unitypackage or Unity Package Manager)
Problematic Firebase Component: Crashlytics
Other Firebase Components in use: Messaging, remote config, analytics in 2019.4.14f1 and just Crashlytics in  2020.1.17f1
Additional SDKs you are using: Facebook, AppMetrica, Mycom.Tracker.Unity in 2019.4.14f1 and none in 2020.1.17f1
Platform you are using the Unity editor on: Windows
Platform you are targeting: Android
Scripting Runtime: Mono

[REQUIRED] Please describe the issue here:
(Please list the full steps to reproduce the issue. Include device logs, Unity logs, and stack traces if available.)
Im making my project in 2019.4.14f1. I tried 7.1.0 and 6.16.1 SDK. Then i tried in clean 2020.1.17f1 with just Crashlytics

Did not register exception handlers: Crashlytics SDK was not initialized UnityEngine.Debug:Log(Object) Firebase.Platform.FirebaseLogger:LogMessage(PlatformLogLevel, String) (at Z:/tmp/tmp.tpC7OdQUHa/firebase/app/client/unity/src/Unity/FirebaseLogger.cs:89) Firebase.LogUtil:LogMessage(LogLevel, String) (at Z:/tmp/tmp.JYnsY9apCV/firebase/app/client/unity/proxy/LogUtil.cs:68) Firebase.Crashlytics.PlatformAccessor:.cctor() (at Z:/tmp/tmp.t4KIuy72sN/firebase/crashlytics/client/unity/proxy/Crashlytics.cs:123) Firebase.Crashlytics.Crashlytics:Initialize() (at Z:/tmp/tmp.t4KIuy72sN/firebase/crashlytics/client/unity/proxy/Crashlytics.cs:59) System.Reflection.MethodBase:Invoke(Object, Object[]) Firebase.FirebaseApp:InitializeCrashlyticsIfPresent() (at Z:/tmp/tmp.JYnsY9apCV/firebase/app/client/unity/proxy/FirebaseApp.cs:507) Firebase.FirebaseApp:<CreateAndTrack>m__1() (at Z:/tmp/tmp.JYnsY9apCV/firebase/app/client/unity/proxy/FirebaseApp.cs:635) Firebase.Dispatcher:Run(Func1) (at Z:/tmp/tmp.tpC7OdQUHa/firebase/app/client/unity/src/Platform/Dispatcher.cs:40)
Firebase.Platform.FirebaseHandler:RunOnMainThread(Func`1) (at Z:/tmp/tmp.tpC7OdQUHa/firebase/app/client/unity/src/Unity/FirebaseHandler.cs:115)
Firebase.FirebaseApp:CreateAndTrack(CreateDelegate, FirebaseApp) (at Z:/tmp/tmp.JYnsY9apCV/firebase/app/client/unity/proxy/FirebaseApp.cs:633)
Firebase.FirebaseApp:Create() (at Z:/tmp/tmp.JYnsY9apCV/firebase/app/client/unity/proxy/FirebaseApp.cs:119)
Firebase.FirebaseApp:get_DefaultInstance() (at Z:/tmp/tmp.JYnsY9apCV/firebase/app/client/unity/proxy/FirebaseApp.cs:94)
Firebase.Sample.Crashlytics.UIHandler:InitializeFirebase() (at Assets/TestCrash/UIHandler.cs:63)
Firebase.Sample.Crashlytics.d__9:MoveNext() (at Assets/TestCrash/UIHandler.cs:50)
UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr)
Steps to reproduce:
Have you been able to reproduce this issue with just the Firebase Unity quickstarts (this GitHub project)?
Yes.
What's the issue repro rate? (eg 100%, 1/5 etc)
100%
What happened? How can we make the problem occur?
Just fallow guide.
If you have a downloadable sample project that reproduces the bug you're reporting, you will
likely receive a faster response on your issue.
Link to 2020.1.17f1 project.
https://drive.google.com/file/d/1vPe5NqXjDS7XgL6672uvnEOtwMQckYLY/view?usp=sharing
Related issue #963

Hi @Dimidrol112,
Take note that crashes reported from the SDK are non-fatal unless you're using some native code to force crashes. Could you verify if you're receiving any crashes by removing the filters from your Crashlytics dashboard?

Yes. I removed filter and can see now. But is it ok to have this errors?

Thanks for confirming, @Dimidrol112. Having these reports means that Crashlytics has been successfully enabled for your app. Also, take note that Crashlytics reports will be sent after your app is relaunched.
I'll be closing this for now. Feel free to reopen if you have any other questions or if an issue arises.
Thanks!

repo: firebase/quickstart-unity


text:
can't find idb2pat.py in your repository

Hi, I read your blog post and can't find the script.
Where it is ?
Thanks

Hi @dummys, good point. PR containing the script is in #8, and should be accepted into the repo this morning.

closed in 5bff8acf0f5b83fa74e662349ca3b814ec815c1c

authors: dummys williballenthin

repo: fireeye/flare-ida


text:
Smooth scrolling navbar

Closes #4

add smooth scrolling to navbar links
add padding to anchor links

Coverage remained the same at 81.176% when pulling 44e97696bacf34c7791f82e0b0d0ff1d892c8ec0 on smooth-scrolling-navbar into a396c07b04426d9f21dc773dc2fc1067f95fba18 on master.

authors: coveralls firefelix

repo: firefelix/dsouvage-homepage


text:
Trouble installing FirePHPCore on ubuntu 14.04 LTS

I am working off a clean install of Ubuntu 14.04 LTS and cannot install firephp due to error:
#pear install firephp/FirePHPCore

downloading FirePHPCore-0.3.2.tgz ...
Starting to download FirePHPCore-0.3.2.tgz (25,019 bytes)
.........done: 25,019 bytes
could not extract the package.xml file from "/build/buildd/php5-5.5.9+dfsg/pear-build-download/FirePHPCore-0.3.2.tgz"
Download of "firephp/FirePHPCore" succeeded, but it is not a valid package archive
Error: cannot download "firephp/FirePHPCore"
Download failed
install failed

I've installed this on several other servers in the same fashion with no problems but they were all running Ubuntu 12 or earlier.

The pear release channel is no longer supported. Please use ** composer**.

authors: billynoah cadorn

repo: firephp/firephp-core


text:
🛑 FirstQuadrant web app is down

In 91a2d70, FirstQuadrant web app (https://firstquadrant.ai) was down:

HTTP code: 0
Response time: 0 ms

Resolved: FirstQuadrant web app is back up in 518e96f after 6 minutes.

repo: firstquadrant-ai/status


text:
New URL for Jinja Template Docs

New version of jinja, new URL
Description & motivation
Updated link to documentation

Thanks!

authors: armaciej clrcrl


text:
Fix: coalesce typeless colnames

Updates macro that coalesces datatype-named column variants, which is a common behavior in Stitch-loaded tables.
Base case (previous functionality): coalesce field__type1 and field__type2 to string column field
Additional case (this PR): coalesce field and field__type to string column field
This was causing errors in a project, whereby the previous macro behavior included two columns named field (one "clean" and one coalesced) in its output.

@drewbanin I added integration tests + some comments to the macro code, which is admittedly dense. Do you have recommendations around possible areas to refactor?

repo: fishtown-analytics/stitch-utils


text:
Update filter in filtered reply times CTE in int_zendesk__reply_time_combined

PR Overview
This PR will address the following Issue/Feature:
https://github.com/fivetran/dbt_zendesk/issues/131
It was discovered that some tickets were not persisting through the final sla policies model, and mistakenly filtered out at the int_zendesk__reply_time_combined model.
This PR will result in the following new package version:

v0.13.2
Please provide the finalized CHANGELOG entry which details the relevant changes included in this PR:

Bug Fixes

Updated the int_zendesk__reply_time_combined model to account for when a ticket is first replied to outside SLA schedules or not yet replied to.

Under the Hood

Adjusted the filter used in the filtered_reply_times CTE for business hours to account for the aforementioned cases, as these records were mistakenly being filtered out previously.

PR Checklist
Basic Validation
Please acknowledge that you have successfully performed the following commands locally:

[x] dbt run –full-refresh && dbt test
[ ] dbt run (if incremental models are present) && dbt test

Before marking this PR as "ready for review" the following have been applied:

[x] The appropriate issue has been linked, tagged, and properly assigned

[x] All necessary documentation and version upgrades have been applied

[x] docs were regenerated (unless this PR does not include any code or yml updates)

[x] BuildKite integration tests are passing

[ ] Detailed validation steps have been provided below

tested with internal data, validations linked in height ticket

Detailed Validation
Please share any and all of your validation steps:

Confirmed the missing tickets were showing up prior to the int_zendesk__reply_time_combined model, and confirmed they are in fact expected to exist in the end models and not be filtered out. Then adjusted the filters in the filtered reply times CTE, ran the package, and confirmed that the tickets persisted in the end sla policies model.

If you had to summarize this PR in an emoji, which would it be?

:calendar:

Consolidating this into PR #136

authors: fivetran-joemarkiewicz fivetran-reneeli


text:
Database reached a seemingly irrecoverable state

Hey,
Since today I am experiencing an issue with my application that uses fjall 1.1.3, in that it can no longer resume operation when starting the application and it fails on decoding one of the UTF-8 strings in the journal as shown by the backtrace below:
thread 'main' panicked at /home/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/fjall-1.1.3/src/journal/marker.rs:126:65:
should be utf-8: Utf8Error { valid_up_to: 26, error_len: Some(1) }
stack backtrace:
   0: rust_begin_unwind
             at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/std/src/panicking.rs:645:5
   1: core::panicking::panic_fmt
             at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/core/src/panicking.rs:72:14
   2: core::result::unwrap_failed
             at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/core/src/result.rs:1653:5
   3: core::result::Result<T,E>::expect
             at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/core/src/result.rs:1034:23
   4: <fjall::journal::marker::Marker as lsm_tree::serde::Deserializable>::deserialize
             at /home/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/fjall-1.1.3/src/journal/marker.rs:126:33
   5: <fjall::journal::reader::JournalShardReader as core::iter::traits::iterator::Iterator>::next
             at /home/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/fjall-1.1.3/src/journal/reader.rs:46:15
   6: fjall::journal::shard::JournalShard::recover_and_repair
             at /home/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/fjall-1.1.3/src/journal/shard.rs:101:25
   7: fjall::journal::Journal::recover_memtables
             at /home/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/fjall-1.1.3/src/journal/mod.rs:44:17
   8: fjall::journal::Journal::recover
             at /home/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/fjall-1.1.3/src/journal/mod.rs:66:25
   9: fjall::keyspace::Keyspace::find_active_journal
             at /home/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/fjall-1.1.3/src/keyspace.rs:508:32
  10: fjall::keyspace::Keyspace::recover
             at /home/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/fjall-1.1.3/src/keyspace.rs:528:13
  11: fjall::keyspace::Keyspace::create_or_recover
             at /home/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/fjall-1.1.3/src/keyspace.rs:279:13
  12: fjall::keyspace::Keyspace::open
             at /home/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/fjall-1.1.3/src/keyspace.rs:264:24
  13: fjall::config::Config::open
             at /home/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/fjall-1.1.3/src/config.rs:199:9
  14: my_project::db::Database::open
             at ./src/db.rs:39:24
  15: my_project::main::{{closure}}
             at ./src/main.rs:380:14
  16: tokio::runtime::park::CachedParkThread::block_on::{{closure}}
             at /home/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.35.0/src/runtime/park.rs:282:63
  17: tokio::runtime::coop::with_budget
             at /home/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.35.0/src/runtime/coop.rs:107:5
  18: tokio::runtime::coop::budget
             at /home/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.35.0/src/runtime/coop.rs:73:5
  19: tokio::runtime::park::CachedParkThread::block_on
             at /home/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.35.0/src/runtime/park.rs:282:31
  20: tokio::runtime::context::blocking::BlockingRegionGuard::block_on
             at /home/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.35.0/src/runtime/context/blocking.rs:66:9
  21: tokio::runtime::scheduler::multi_thread::MultiThread::block_on::{{closure}}
             at /home/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.35.0/src/runtime/scheduler/multi_thread/mod.rs:87:13
  22: tokio::runtime::context::runtime::enter_runtime
             at /home/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.35.0/src/runtime/context/runtime.rs:65:16
  23: tokio::runtime::scheduler::multi_thread::MultiThread::block_on
             at /home/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.35.0/src/runtime/scheduler/multi_thread/mod.rs:86:9
  24: tokio::runtime::runtime::Runtime::block_on
             at /home/stephan/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.35.0/src/runtime/runtime.rs:350:45
  25: my_project::main
             at ./src/main.rs:522:5
  26: core::ops::function::FnOnce::call_once
             at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Unfortunately, due to a license agreement I have for some of the data used in this database, I cannot share the files, but I would like to debug this myself and I am looking for some pointers on how to approach this since I am not familiar with the underlying disk format used by lsm-tree/fjall. Any tips would be appreciated.

I changed the code at src/journal/marker.rs:126 to show me what bytes it actually failed to parse as UTF-8, so I could then grep what journal files have the same byte occurrence and removing them at least causes the database to reach some state where it does not panic anymore, but I think it would be useful to figure out how it got into this state in the first place so we can prevent this from happening.

Oh wow, thanks for looking into this. I ran workloads with >64K values before, but I think I never recovered them, so I had a false sense of security.

are the values allowed to be longer than 64K? According to the README, the values can be up to 2^32 in length

Yes. I don't recommend large values before 2.0, but yes.

but the code here seems to write out the value length as u16

Yeah that should be 32. lsm-tree supports values up to 2^32. I will add a regression test case, however changing it to u32 would be a format breaking change, so I need to look into how to handle this.

I also think that another issue is that the recovery should always reach some operational state, i.e. it should be panic-free and shouldn't use Result<T, E>, but it should have a way of indicating that something could be amiss with the database in these cases, such that the user can decide to turn that into a panic or simply log it somewhere. Currently, an irrecoverable journal would lead to a denial-of-service, which is not great.

Yeah that should be 32. lsm-tree supports values up to 2^32. I will add a regression test case, however changing it to u32 would be a format breaking change, so I need to look into how to handle this.

Thanks for confirming this! I understand that it would break the format, thus that it would be incompatible with fjall 1.x. Fortunately, I can work around this for now and restructure my database again once fjall 2.x is ready.

I also think that another issue is that the recovery should always reach some operational state, i.e. it should be panic-free and shouldn't use Result<T, E>

I think it should be panic-free yes, however it needs to return a Result, because depending on your consistency requirements, replaying the journal may fail (kind of like https://github.com/facebook/rocksdb/wiki/WAL-Recovery-Modes). In that case, the error variant would be variant that says something like "ConsistencyFailed", and the user could decide to recover with a more lax replay mode. That's WIP however, right now everything gets recovered up until the journal is invalid (which is kTolerateCorruptedTailRecords).

However, for fjall 1.x, it might be an idea to check that the value isn't larger than 64K when inserting data to avoid people from running into this situation. It would probably be better to have insertion fail prematurely, rather than to end up with irrecoverable journal files.

Yeah, my plan was to assert the values are not larger than 64K (they are asserted in lsm-tree to fit in a u32), and update the docs, and then v2 will support values larger than 64K, which plays well with the key-value separation feature that will come with it anyway.

Fortunately, I can work around this for now and restructure my database again once fjall 2.x is ready.

I have pushed a pre-release of v2 now. I don't expect any further breaking changes at this point and will probably release it on Friday (with announcement).
Here's an example for large values:
use fjall::{Config, PartitionCreateOptions};
use nanoid::nanoid;

fn main() -> fjall::Result<()> {
    let keyspace = Config::default().open()?;
    let partition = keyspace.open_partition(
        "default",
        PartitionCreateOptions::default().use_kv_separation(true),
    )?;

    let large_value = "a".repeat(128_000);
    partition.insert(nanoid!(), &large_value)?;

    for kv in partition.iter() {
        let (k, v) = kv?;
        let k = String::from_utf8_lossy(&k);
        println!("{k:?} => <{} bytes>", v.len());
    }
    println!("len: {}", partition.approximate_len());

    Ok(())
}

Thanks for the update! I am slowly working on migrating towards Fjall 2 and I will let you know if I run into any issues again.

repo: fjall-rs/fjall


text:
Decouple opengl/rendering from widgets/core

I don't know how deep the current connection goes, but I would be glad to reuse the application framework with different (vulkan, glfw, etc.) renderer.

Hi @dpwiz!
The library has a Renderer abstraction that is used by widgets for all rendering related operations. Currently, there is only one implementation based on NanoVG, although other implementations could be added. I recently added this section to Design decisions that could be of interest, especially for the alternative renderer ideas.
Regarding GLFW, I think that one is going to be much harder. Originally I wanted to abstract SDL to be able to replace it with a different library (GLFW in particular), but it turned out to be complex, and I didn't feel it provided much value for what I needed at that point (plus I'd like to support mobile someday, which GLFW does not handle). At this point, Monomer is pretty much tied to SDL2.
Note regarding mixing lower-level rendering code
While still using the current NanoVG implementation, in your widget's render function, you can call createRawTask; the action provided to this function will be run outside the context of NanoVG. Since NanoVG uses OpenGL, this means you will be able to run any OpenGL command you want (and also means you have to take care of setting everything up, including shaders). Raw tasks are executed after rendering regular widgets (it's a separate rendering pass).
I don't currently have an example at hand, and it's been a while since I last tested this, so weird issues may happen that I'm unaware of.

Hmm. Building on DearImGui is an interesting venue - opens up many different backends.

The polymorphic event story is a mess, I agree. I, too, decided to ditch it for now, in my engine and stuck with glfw instead.

Just to clarify, the widgets are agnostic to SDL2. They handle events and requests using Monomer's types and functions.
What I mean when I say that it is tied to SDL2 is that the internals, which are not visible to library users, are programmed directly using SDL2 functions instead of using some abstraction. This is contrary to what happens with Renderer, which can be swapped for a different one.

@dpwiz I'll close this issue for the time being. If you have any other questions or issues, don't hesitate to re-open it or create a new one. Thanks!

BTW, I've added most of the DrawList methods to dear-imgui bindings.
There are some event/input related functions I need to investigate, they might provide that cross-framework platform.

@dpwiz nice! I'll take a look. My main concern is I'm relying on quite a few NanoVG features:

Painting with a texture inside an arbitrary path (can be seen when setting rounded corners on an image widget)
General curves (bezier, quadratic, etc), which are rendered pretty nicely.

I have to check how hard it is to get the same out of ImGUI's DrawList.

DrawLists have both textures with rounded corners and straight/smooth paths.

authors: dpwiz fjvallarino

repo: fjvallarino/monomer


text:
The provided request must include a 'client_id' input parameter.

I wrote the following Dockerfile, but got an error that a client_id parameter is required:
FROM debian:stretch-slim
RUN apt-get update \
    && apt-get upgrade -y \
    && apt-get install -y git curl

RUN git clone --recursive https://github.com/fkalis/bash-onedrive-upload.git
WORKDIR /bash-onedrive-upload

RUN ./onedrive-authorize

Output
Step 5/5 : RUN ./onedrive-authorize
 ---> Running in d19bb61d17ee
Please open the following URL in your browser and follow the steps until you see a blank page:
https://login.live.com/xxxxx

When ready, please enter the value of the code parameter (from the URL of the blank page) and press return
Something went wrong, here is the API response:
{"error":"invalid_client","error_description":"The provided request must include a 'client_id' input parameter."}
 ---> 1d51c684d675

Seems like Microsoft made some changes in their API?

You skipped one step, from README:

Afterwards your overview should show your freshly created credentials in the form
Application ID: 00000000A2B3C495
Applications secrets: qOFCYaZKjm6e13aq3fdGiNz

Please insert these values in the matching variables in onedrive.cfg:
export api_client_id="00000000A2B3C495"
export api_client_secret="88qC3kX2Cbd0tXV2sBnqYbS321abcDEF"

After the initial configuration you must authorize the app to use your OneDrive account. Run
$ ./onedrive-authorize

repo: fkalis/bash-onedrive-upload


text:
do not show and fetch logos on mobile

it is not too difficult to disable showing logos on mobile, but also not downloading them is a bit more tricky as we use the <img> tag for showing the logo.
It would be better to switch to CSS backgrounds for the logos. Possible solution:

add "encoded" entity ID to the class of the button
write a CSS file that points to the logo as a background
add this CSS from the "data" directory also to the template, but only when loaded on non-mobile, e.g. with a large viewport.

Something similar is done for the logos where they are written to the "data" directory and exposed through Apache...

This actually works!
form.entity button {
    padding-left: 100px;
    background-repeat: no-repeat;
    background-position: 1em 50%;
    height: 75px;
}

form.entity button.https_www\.onegini\.me {
    background-image: url("https_www.onegini.me.png");

}

form.entity button.https_idp\.surfnet\.nl {
    background-image: url("https_idp.surfnet.nl.png");
}

form.entity button.https_idp\.surf\.nl {
    background-image: url("https_idp.surf.nl.png");
}

https://github.com/fkooman/php-saml-ds/commit/844db9b8abfe98101eed5177274c7efb7d507ef6

repo: fkooman/php-saml-ds


text:
[Proposal]: use case for SG AI

Problem statement
A lot of manual work and tuning goes into every single publisher that's currently maintained, and still requires constant monitoring if anything changes in the supported news outlets or web sources.
Solution
replace manual and labour-intensive scraping code with SG AI, whose you-only-scrape-once (YOSO) concept serves that purpose specifically: you write the scraping pipeline once, and leverage powerful LLMs (open-source or closed-source) to extract the articles in the desired format regardless of the web source or its HTML code changing over time.
write a single smart scraper graph tailored for news and articles crawling in the desired relational format, common to all available publishers and outlets.
Draft

Open Questions
No response

Hey @DiTo97 thanks for the proposal :)
Fundus uses manual-written heuristics to optimize for accuracy and recall. Our library aims to yield artifact-free extractions for every supported publisher. I will give SG AI a shot and see the results it scores on our benchmark

repo: flairNLP/fundus


text:
Make relative baseline file paths relative to the current pyproject.toml

Currently flakehell searches for baseline files in the current working directory. It doesn't play nice together with pyproject.toml search logic.
Consider the following example:
project/
    pyproject.toml # baseline = flakehell.baseline
    flakehell.baseline
    subdir1/
        ...
    subdir2/
        ...

If flakehell executed in subdir1 or subdir2 it finds project-level pyproject.toml but fails to find flakehell.baseline as it tries to find it in the current directory.
The proposal is to make it search files referenced in pyproject.toml relative to pyproject.toml location. If referenced files have relative paths, of course.
The same should be done for the base files, I guess (didn't check the behavior with them).
If you think this is okay, I can prepare a PR with these changes.

@sgaynetdinov, is the project alive? I understand that maintaining the project requires efforts and it is not always possible to respond timely, but looks like there is no activity for almost a half year. Except for a couple of PRs, but they are not accepted and not commented…
Maybe you can consider adding some additional people with write access to the repository?

repo: flakehell/flakehell


text:
Interactive docs: OpacityEffect

Interactive doc for the OpacityEffect
The OpacityEffect should have a small example that show how the effect is applied and how it works. This could for example be just clicking somewhere in the game and changing the opacity of a geometrical shape or SpriteComponent.
https://docs.flame-engine.org/1.3.0/flame/effects.html#opacityeffect
What are interactive docs?
On our documentation site has the possibility to run inline interactive examples and we would like every visual feature to have a small, pretty and easily understandable example attached to it. Some current examples are the router and the decorators.
Some inspiration can also be found on our examples page where we have examples for most features.
Good to know
Make sure that you comment on the issue that you will be working on this before starting to program.
To set up the Flame environment you need to follow the instructions in our contributing.md doc, if you have any problems setting up your environment (or other issues of course) feel free to ask for help in the Flame channel on our Discord server.
Since this is a documentation change, you need to be able to build the docs. Instructions for building the documentation site locally can be found here: https://docs.flame-engine.org/main/development/documentation.html#building-documentation-locally
Make sure to include a video of the example when you upload the PR so that it will be easier for us to review it. (You can attach videos directly in the PR, so no need to upload them somewhere else)
Happy hacking!

Hey 👋,
I would like to work on this issue😄

Hey 👋,
I would like to work on this issue😄

Awesome! I assigned you to the issue. Join our discord if you have any doubts

I will gladly help out if needed.

authors: 2002Bishwajeet erickzanardo munsterlander spydon

repo: flame-engine/flame


text:
Auto-complete filter (as with create form)

Suppose I have a model with a many-to-one relationship with another.
In the create form I have a choice input field in which I can select the model I want to connect.
How about adding this feature to filter? Currently I can only use filter with the relationship's columns, or id which is less helpful than having a nice choice input with indicative names like in the create form.
Since the code already exists, I wonder how difficult would it be to integrate it into the filters?

+1

I'm sure it would be useful. A PR would be welcome. Closing this in the meantime.

authors: ElvisTheKing petrus-jvrensburg vToMy

repo: flask-admin/flask-admin


text:
Add systemd-sysext docs for custom extensions

With Alpha 3185.0.0 we have the basics for users to start extending the
base OS with systemd-sysext. The replacement of custom Torcx images is
already possible and we also provide a helper to create sysext images
from the Docker release binaries.
How to use
Testing done
the resulting images work

These are just scripts?

I thought these helper scripts would get downloaded with wget instead of cloning a repo. Maybe they get integrated into some custom automation for further adaptation.
For the sysext building story a new repo could make sense to extend them and make users contribute their own use cases. Should I create one like sysext-builders?

Huh, this got lost in the GitHub outage, I bet I saw it here

Or maybe I didn't push because I knew it's not working well…?^^

Anyway, for the long term perspective I propose we set up a special repo for sysext recipes, will discuss the name in Matrix.

Ok, updated it to use the new repo. PR for moving the helper scripts there https://github.com/flatcar-linux/sysext-bakery/pull/1

authors: jepio pothos

repo: flatcar-linux/flatcar-docs


text:
added flavor keys

addressed #73 by making icecream flavor assignment a separate field in the json file.

I cleaned up a little bit, and removed an unused variable. Now I just have to remove the seed assignment flavor key from the preprocessing config file


text:
Not working with  element

I have tried to use flatpckr latest version 4.5.2 using a dialog element (with polyfill where no supported). Unfortunately the date picker and the time picker are not displayed - it seems that they are being displayed behind the dialog so I assume there is a z-index issue. Is there a work around for this?

a related thread that can maybe help you
https://github.com/flatpickr/flatpickr/issues/551
to set z-index:
div.flatpickr-calendar {
    z-index: 9;
}

Thanks I have taken a look at that and have got the calendar to work but using this:
.flatpickr-calendar.open {   z-index: 999999; }
But this doesn't seem to work for when just using time only 🤔

...  actually that fix only seems to work when using the dialog polyfill - when using dialog in Chrome browser the calendar is behind the dialog.
Time only picker don't work with or without polyfill

@niko5 try the { static: true } option

@chmin thanks that has got the time pickers showing 😀unfortunately there is a but - the time picker doesn't dismiss so when there is more than they all start to show and crowd the UI ..

@niko5 you mean pickers don't close after clicking outside?
If so, I would suggest using https://flatpickr.js.org/plugins/#confirmdate

@chmin yes for time pickers (no calendar) when in calendar mode it works.
I will take a look at your suggestion  and see if that helps .
Thanks

@chmln unfortunately confirm date plugin make no difference - and in fact for just time picker doesn't seem to show anyway.
What seems to happen is that if you click outside the dialog the TimePickers are dismissed but if you click any control within the dialog and form time pickers stay visible.

Ok now seemed to have sorted and got it working.
The reason that the flatpickr time was not being dismissed is because I was using
{ appendTo: document.getElementById('rs-dialog')}
Once I removed that and just used
{      static: true }
as suggested by @chmin it all works !
A big thank you

@niko5 you're welcome. Glad you got it sorted

authors: adrienpoly chmln niko5

repo: flatpickr/flatpickr


text:
Revert default export typings

Hello! After https://github.com/flatpickr/flatpickr/commit/10b33ca3a08cc597bce858245620a10250cd18d1 the typings now no longer match up to the shape of the imported typescript object. i.e. to use this module typescript users now have to do
import * as flatpickr from 'flatpickr';

Instead of
import flatpickr from 'flatpickr';

This changes the declaration to match this change.
Alternatively, to go back to the old behaviour output.exports in the rollup config needs to be set to named instead of default as it is now.

@chmln any chance you could merge this when you've got the chance? Thanks! 😄

@mattlewis92 unfortunately I don't think I can change the typings now without causing more breaking changes for users.
From my understanding, this issue only happens with older TypeScript versions, and therefore affects older @angular/cli versions as well. I have just tested the typings on a fresh ng project and confirmed that they work without errors (both compile-time and runtime).
Since TypeScript doesn't follow semver, they have changed the way modules work multiple times in 2.x versions from 2.6 and onward. Needless to say, this has caused breakage for my relatively small library, and I imagine the dreadful magnitude of this on older, larger angular-based projects.
The only workaround I am aware of right now is using the esModuleInterop flag and possibly allowSyntheticDefaultImports, where ng cli upgrades are not possible.

Ah, the angular CLI works because it compiles to es2015 modules and webpack automatically adds the default export. esModuleInterop wasn't available to me last time I tried this, it works as a workaround to the problem I was having, thanks! 👍


text:
Parallax section reduce to "kolibri intro" and "no internet" slide

@jtamiace @66eli77

Comment out old parallax section code
Comment out "media query" CSS code
Added kolibri intro with logo and text
Added "No internet" section with picture and text

the image has a thumb cut off.

repo: fle-internal/fle-home


text:
fix: skip running flutter doctor on windows if no_rich_output=True

Description
Error message

  File "C:\hostedtoolcache\windows\Python\3.12.2\x64\Scripts\flet.exe\__main__.py", line 7, in <module>
  File "C:\hostedtoolcache\windows\Python\3.12.2\x64\Lib\site-packages\flet\cli\cli.py", line 88, in main
    args.handler(args)
  File "C:\hostedtoolcache\windows\Python\3.12.2\x64\Lib\site-packages\flet\cli\commands\build.py", line 360, in handle
    with console.status(
  File "C:\hostedtoolcache\windows\Python\3.12.2\x64\Lib\site-packages\rich\status.py", line 106, in __exit__
    self.stop()
  File "C:\hostedtoolcache\windows\Python\3.12.2\x64\Lib\site-packages\rich\status.py", line 91, in stop
    self._live.stop()
  File "C:\hostedtoolcache\windows\Python\3.12.2\x64\Lib\site-packages\rich\live.py", line 147, in stop
    with self.console:
  File "C:\hostedtoolcache\windows\Python\3.12.2\x64\Lib\site-packages\rich\console.py", line 864, in __exit__
    self._exit_buffer()
  File "C:\hostedtoolcache\windows\Python\3.12.2\x64\Lib\site-packages\rich\console.py", line 822, in _exit_buffer
    self._check_buffer()
  File "C:\hostedtoolcache\windows\Python\3.12.2\x64\Lib\site-packages\rich\console.py", line 2024, in _check_buffer
    self._write_buffer()
  File "C:\hostedtoolcache\windows\Python\3.12.2\x64\Lib\site-packages\rich\console.py", line 2060, in _write_buffer
    legacy_windows_render(buffer, LegacyWindowsTerm(self.file))
  File "C:\hostedtoolcache\windows\Python\3.12.2\x64\Lib\site-packages\rich\_windows_renderer.py", line 17, in legacy_windows_render
    term.write_styled(text, style)
  File "C:\hostedtoolcache\windows\Python\3.12.2\x64\Lib\site-packages\rich\_win32_console.py", line 442, in write_styled
    self.write_text(text)
  File "C:\hostedtoolcache\windows\Python\3.12.2\x64\Lib\site-packages\rich\_win32_console.py", line 403, in write_text
    self.write(text)
  File "C:\hostedtoolcache\windows\Python\3.12.2\x64\Lib\encodings\cp1252.py", line 19, in encode
    return codecs.charmap_encode(input,self.errors,encoding_table)[0]
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
UnicodeEncodeError: 'charmap' codec can't encode character '\u221a' in position 0: character maps to <undefined>

\u221a' represents the square root character, which comes from flutter doctor.
Summary by Sourcery
Fix a bug by skipping the execution of flutter doctor on Windows when no_rich_output=True to avoid Unicode encoding errors. Improve code readability by refactoring the handling of platform and output settings.
Bug Fixes:

Skip running flutter doctor on Windows if no_rich_output=True to prevent Unicode encoding errors.

Enhancements:

Refactor code to use self.no_rich_output and self.current_platform for better readability and maintainability.

Fix a conflict here please.

authors: FeodorFitsner ndonkoHenri

repo: flet-dev/flet


text:
Websocket proxy nginx conf fix.

https://github.com/flet-dev/flet/pull/748#event-8119098225

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Mehmet Fatih Güman seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

What issue does this PR fix (looks like you posted a link to unrelated discussion)?

What issue does this PR fix (looks like you posted a link to unrelated discussion)?

My websocket problem in nginx was solved when I replaced keep-alive with "upgrade". Other changes were accidental, I guess. If you think that the "upgrade" solution is correct, I can throw another PR and eliminate what I changed wrong.

I've checked the number of sources and looks like proxy_set_header Connection "upgrade" is the correct solution which worked for you.

authors: CLAassistant FeodorFitsner qraxiss

repo: flet-dev/website


text:
make make work with macos

small fix to accommodate macos

LGTM

Thank you for your contribution!

authors: hanikesn kai-keliikuli

repo: flix-tech/vagrant-kubernetes


text:
Hundreds of Android Vitals crash reports

Hi,
I got hundreds of crash reports linked to cordova-admob-pro from Android vitals.
I am using:
cordova 7.0.1
cordova-android 6.2.3
cordova-admob-pro 2.29.21
I am not using crosswalk webview.
Here are the reports (all are the same, but happen on different devices and android version 4.4 to 7+):

java.lang.NullPointerException:
at com.rjfun.cordova.admob.AdMobPlugin.getAdViewSize (AdMobPlugin.java:185)
at com.rjfun.cordova.admob.AdMobPlugin.__getAdViewWidth (AdMobPlugin.java:191)
at com.rjfun.cordova.ad.GenericAdPlugin$5.run (GenericAdPlugin.java:582)
at android.os.Handler.handleCallback (Handler.java:739)
at android.os.Handler.dispatchMessage (Handler.java:95)
at android.os.Looper.loop (Looper.java:158)
at android.app.ActivityThread.main (ActivityThread.java:7225)
at java.lang.reflect.Method.invoke (Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:1230)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1120)

Thank you in advance.

Here is the source code:
https://github.com/floatinghotpot/cordova-admob-pro/blob/master/src/android/AdMobPlugin.java#L185
  protected AdSize getAdViewSize(View view) {
    if(view instanceof PublisherAdView) {
      PublisherAdView dfpView = (PublisherAdView) view;
      return dfpView.getAdSize();
    } else {
      AdView admobView = (AdView) view;
      return admobView.getAdSize();
    }
  }

NullPointerException means adview is NULL, it seems the adview is not created for some unknown reasons.
In normal cases, it won't happen. Unless, system error, like out of memory, etc.

Thank you for your answer.
Then isn't it possible to check if adview is NULL or not to avoid the crashes?

Nothing can be done if out of memory.

I am not sure that is the issue.
It occurs on many phones with 4gb ram or more. Users report that it happens a few seconds after launching the app.
What would happen if i call AdMob.removeBanner, AdMob.showBanner or AdMob.hideBanner before the banner is created? Could it be the source of the crashes?

calling removeBanner() too soon after createBanner() might cause the issue. As it will take some time to load the ad resource from ad server, need give the app a little time to process. hideBanner() won't cause the issue, as the ad view is not deleted, it's just make invisible.

authors: floatinghotpot tominou

repo: floatinghotpot/cordova-admob-pro


text:
Suggestion: group name with underscore

Thanks for this library, that's exactly what I was looking for.
Could it be possible to have group name containing underscore?
That's will make syntax clearer on big expression.
ex: (?'group_name') instead of (?'groupName')

The latest commit makes underscores in group names possible.
When version 1.1.6 is ready for download on maven (hopefully tomorrow), you will be able to use that feature.

authors: florianingerl hexosse


text:
Make cache lifetime for static files configurable

The cache lifetime sent in an HTTP response as the "expires" header should be configurable via an environment variable.

The cache lifetime I set (30d) is too short – Google Lighthouse wants at least half a year.
And we will need changes in the Google Cloud Storage plugin in order to achieve proper cache lifetimes for persistent resources (see flownative/flow-google-cloudstorage#32).

repo: flownative/docker-nginx


text:
Error in definitions file crashes install / search commands

There is a CONTRIBUTING.md file in the react-apollo type definitions. This won't allow me to install or search any type definitions. This is the first time I am installing flow-typed and I have nothing in my local cache.
The output of, for example, flow-typed search queue-fifo@x.x.x is:
(node:8056) DeprecationWarning: Using Buffer without `new` will soon stop working. Use `new Buffer()`, or preferably `Buffer.from()`, `Buffer.allocUnsafe()` or `Buffer.alloc()` instead.
• rebasing flow-typed cache...done.
UNCAUGHT ERROR: Error: ../../../pmrcunha/.flow-typed/repo/definitions/npm/react-apollo_v2.x.x/CONTRIBUTING.md: Malformed test file name! Test files must be formatted as test_(.*).js: CONTRIBUTING.md
    at validationError (/Users/pmrcunha/Documents/reps/oss/prepack/node_modules/flow-typed/dist/lib/validationErrors.js:14:11)
...

FWIW I am also hitting this same exact issue

same issue here

yarn global remove flow-typed
yarn global add flow-typed
solved the problem for me
(duplicated issue https://github.com/flowtype/flow-typed/issues/2226)

authors: bent0b0x pmrcunha rdbmax

repo: flowtype/flow-typed


text:
CLI favors more generic version ranges when installing libdefs

When running flow-typed install enzyme@2.3.2 -f 0.30, flow-typed installs libdefs for enzyme 2.x.x as there are two different libdef versions, 2.x.x and 2.3.x. The generic 2.x.x version is more outdated and is probably intended as a fallback unless there are more specific versions available.
Since there seems to be no way for defining upper bounds for version ranges currently, would it make most sense to just track major versions separately instead of making new libdefs for minor versions as well?

This was fixed over in https://github.com/flowtype/flow-typed/pull/326

authors: jeffmo strax


text:
Swap order of lodash flowRight definitions

This works around this issue: https://github.com/facebook/flow/issues/2360.

Scratch that, it doesn't actually fix the issue.


text:
Concat plugin not concatenating multiple lines

Problem
Concat not working for multi line on kubernetes environment. I am using fluentd kinesis and concat plugin
I have two scenarios for which its not working

Multiline seperated by \n and starting with a time stamp - Only the first line of multiline reaches the destination. Other logs are lost.
Example: Testing line 1 \n Testing line 2\n Testing line3
The log is lost and does not reach the destination
Java exception stack trace which is multiple lines - The stack traces are reaching the destination as multiple records and in jumbled. They are not sent as single record after concatenation.

This is my fluentd configuration
# concat multiline logs if the first line starts with a date in a specific format
    <filter kubernetes.**>
      @type concat
      key message
      multiline_start_regexp /^\d{4}-\d{1,2}-\d{1,2}/
      stream_identity_key stream
      flush_interval 2
      use_first_timestamp true
      timeout_label @NORMAL
    </filter>

I am using concat plugin version 2.3.0
Also, I am not clear with the usage of stream_identity_key. What is it used for?

Hello, Anyone please suggest something.

Could you show me your logs about both scenarios?

dude what happened , how do you solve the second scenario

I am experiencing the same issue. I think is related to the timeout label.

authors: MyOldSkyGrandfather cristianpetrula lp060 okkez


text:
deb rpm: group logging

To investigate build log effectively, grouping log is better to do.

Verbose logs are grouped like this.

repo: fluent/fluent-package-builder