Blitz | An eBook Framework | Media library

As already pointed out in the comments, Firestore cannot store functions (or constructors for that matter). From my perspective, you have two options:

Option 1

Serialize your functions as a string, store them in Firestore, then eval them on the client. But that's pretty terrible.

Option 2

Adjust your data model in Firestore. From the looks of it the collection "users" should either have two sub-collections "inbox" and "friends" or you could make "inbox" and "friends" root-level collections and reference the user they belong to (so you can query them like collection('friends').where('uid', '==', userId) or something like this).

In general, I always take all the pieces of data apart and try to structure them in the most independent manner possible. Don't shoehorn your client logic into your data model. This is a recipe for tedious refactors later on when your client logic will eventually change.

Okay found your issue:

1. formControlName="i" in inspect element formcontrolname was i, and not a number. use angular string interpolation [formControlName]="i" or formControlName="{{i}}
2. here you are checking whole array, not individual controle. it still works though if any of inputs has error. but will show error for both inputs.

It is actually doing the hover - just not using the color you tried to apply due to the .table-hover and specificity due to https://getbootstrap.com/docs/5.1/content/tables/#how-do-the-variants-and-accented-tables-work

To use your own hover on all rows you can remove the table-hover class and force it on the td.

I fixed this by wrapping rows and columns in useRefs and used their .current property for both of them. Fixed it immediately.

Typescript is showing errors because, You had not explain any type. You can create your type with

The issue is that your DbProvider context isn't the source of truth as to the status, it's not the component maintaining the requestStartDbObj state. Each Button is duplicating the state locally and using its own start function. Each Button is also replacing the requestStartDbObj state of the context, so when switching back to the home path all the buttons get the same initial state value. Upon navigating away from the home path the Button component is unmounted, so the state updates on timeout are lost.

You should move the start logic to the sharedContext so DbProvider maintains control over the state updates. start should consume an id argument so it can correctly update the status for that specific object.

DbProvider

To solve your specific issue, you can generate dummy variables to run your desired clustering.

One way to do it is using the dummy_columns() function from the fastDummies package.

TLDR; Tensor and Tensor.data are not the same! Please refer to this answer.

While Tensor and Tensor.data do share the same memory they are not the same interface to accessing it. Also, notice how Tensor.data is a Tensor, which means the data attribute is recursive... However, there is a difference between the two: operations performed on the data attribute will bypass Autograd's check. This means any computation performed from Tensor.data won't be tracked for backpropagation. In practice, this means that using data for computing is identical to detaching the tensor from its computational graph if any.

Try this: