Get Key Failed From Google

Running Node-red on two PC's. "home notify" Node worked well for a few hours then stopped and showed the "get key failed from google" message under the "google home notify" icon. All other functions of Google Home appear to be working - cast - broadcast etc.

I'm also experiencing the "get key failed from google" error. It's been working well for weeks.

Is it now working ?

Hi Scott,
        Did it just start working again or did you do something ?

Cheers
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
From: Scott<EMAIL_ADDRESS>Sent: Wednesday, September 19, 2018 12:48 PM
To: nabbl/node-red-contrib-google-home-notify
Cc: juulg; Author
Subject: Re: [nabbl/node-red-contrib-google-home-notify] Get Key Failed From Google (#25)
I'm also experiencing the "get key failed from google" error. It's been working well for weeks.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/nabbl/node-red-contrib-google-home-notify/issues/25#issuecomment-422875578 , or mute the thread https://github.com/notifications/unsubscribe-auth/ApZkfZZ5-uhn8i7CAXUU8D-CIM-7OEMLks5ucnVHgaJpZM4WwQKr .  https://github.com/notifications/beacon/ApZkfS98-DxrAe6MCijcWNN-s7ar_KqSks5ucnVHgaJpZM4WwQKr.gif
http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient
Virus-free.  http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient www.avg.com

What did you do if anything to get it going again ?

Unfortunately last I checked it was still not working. My initial guess is there's an API key that needs to be renewed or something.

Getting this as well.

I am going to try and fix this today. Might be the API key being too old.
On Thu, Sep 20, 2018, 03:58 heytcass<EMAIL_ADDRESS>wrote:

Getting this as well.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nabbl/node-red-contrib-google-home-notify/issues/25#issuecomment-423014550,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEdmg4EbKw3DlFCygAAYWtOWRT1pMGP5ks5ucvZbgaJpZM4WwQKr
.

After analyzing the problem a bit... this is definitely a problem from one of the underlying libs I use:
https://github.com/zlargon/google-tts/blob/master/lib/key.js
This can also happen when you are using the API too much...

I'm also getting this error message. I found if I restart node-red that the error goes away, if I can connect to Google and the home device (I have 2 home devices).

If I restart Node Red the error does go away, but as soon as a flow calls it the error comes back.

I'm also getting this error message :-(

I have to amend my observation, seems mine worked for a few hours but the message has returned.

This issue is triggered when you want to send a message though the Google Home Notify.
In case you restart or redeploy your project, the error will reset and wait until it's being triggered again.
Due to this error, the Google Home won't trigger.
(This Error also occurs on the Home-Assistant tts)
@nabbl Do you have (status) updates for us or a workaround for this problem?
(Love this function to have my google home wake me up in the morning 😅 thanks)

Any solution in sight to this problem? Really good function, miss it a lot! ;o)
using it from Node-Red for reminders for my wife to take her medicine!

Yeh, I was here to report this, now I see that is a common problem, any news on this?
Thank You

Guess you're right, having the same problem from Hassio and media_player.googlehome

Same problem here

Must be hassio related because together with node-red issue my media_player tts stopped working too. I see tts/google_say service launched but no sound comes from the speaker.

I guess it's Google TTS related  since nor Hassio or  Node-red is working, but I can be wrong.
peter@mobilen

From: eventhorizonbreaker<EMAIL_ADDRESS>Sent: Saturday, September 22, 2018 12:29:06 PM
To: nabbl/node-red-contrib-google-home-notify
Cc: PeAnSwe; Comment
Subject: Re: [nabbl/node-red-contrib-google-home-notify] Get Key Failed From Google (#25)
Must be hassio related because together with node-red issue my media_player tts stopped working too. I see tts/google_say service launched but no sound comes from the speaker.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnabbl%2Fnode-red-contrib-google-home-notify%2Fissues%2F25%23issuecomment-423733655&data=02|01||f29cf69348514c72d28208d620763a25|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636732089480336816&sdata=aLn3oHnl0A4zfAMp2iEuipuMHPTkOmnRpk7z0AWbihk%3D&reserved=0, or mute the threadhttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAV27b6gPbvDXbu_8_g4AZjQ9CRpSxVo0ks5udhDygaJpZM4WwQKr&data=02|01||f29cf69348514c72d28208d620763a25|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636732089480336816&sdata=MmcnjbgyTWAB7F2elj3sjT3XTcGXWsM5tHnCPIBPHIQ%3D&reserved=0.

Confirms the same problem for me as well.

Thanks Achronite.
It works for me again :-)

Works perfect again! Thank you!

That works perfect for me also. Thanks

Hassio 0.78.3 resolved tts problem in itself and tts works. This did not help node-red though. Too bad I can't adjust the files as Archonite on hassio (the files are not visible).

Struggled a bit with making the changes on Windows but followed Achronite’s description using Powershell and all is now well again !
Great job !
Thank you.
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
From: Achronite<EMAIL_ADDRESS>Sent: Sunday, September 23, 2018 10:21 AM
To: nabbl/node-red-contrib-google-home-notify
Cc: juulg; Author
Subject: Re: [nabbl/node-red-contrib-google-home-notify] Get Key Failed From Google (#25)
The issue is called by google changing their tts libraries.
I'm not a github expert, but you can fix this by the following commands for a node-red install:
cd ~/.node-red/node_modules/google-home-notify
edit package.json and change the dependency on 'google-tts-api' from '0.0.2-alpha1' to '0.0.3', so it reads:
"dependencies": {
"bluebird": "3.5.1",
"castv2-client": "^1.2.0",
"google-tts-api": "0.0.3"
}
Update the dependency
npm update
Restart node-red
node-red-stop
node-red-start
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/nabbl/node-red-contrib-google-home-notify/issues/25#issuecomment-423820062 , or mute the thread https://github.com/notifications/unsubscribe-auth/ApZkfeB1yb8__d1ptlEHTtTBsFsA6EdPks5ud5i7gaJpZM4WwQKr .  https://github.com/notifications/beacon/ApZkfUj8hEfd0xeWzqjzyxB5vOetck6Pks5ud5i7gaJpZM4WwQKr.gif
http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient
Virus-free.  http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient www.avg.com

Struggled a bit with making the changes on Windows but followed Achronite’s description using Powershell and all is now well again !
Great job !
Thank you.

Hmm,  it's not quite working correctly. I have 2 Google home devices.

Oops, the mini changed it's dhcp address (I messed up the mac in the dhcp file). My bad. Both work now.

Thanks for suggestion @blackshoals. I have created a subflow based on HA tts service which emulates google-home-notify node. Now it works for me and in addition I have an influence on volume of the speaker.

After analyzing the problem a bit... this is definitely a problem from one of the underlying libs I use:
https://github.com/zlargon/google-tts/blob/master/lib/key.js
This can also happen when you are using the API too much...

Hi
I did what Achronite suggested and that worked for most of the guys here, but I still get the "get key failed from Google" err message. I just love your node contribution and really miss it. What else can I try?
/John

Hi John,  Long shot – But I had a similar problem with it working  on some PC’s and not others after I installed the fix. I found that the “update” was the problem. I had to ensure that that “NPM update” was executed in the absolute directory where the Loader.json file that was modified was installed.

Hi Achronite all working and a special thanks to juulg ......drove me mental too, but thanks to you now working.......now how to fix in hassio?
Thanks Phil

@phil040462 et al. other Hass.io users: I sent a message to Frenck on the Hass.io Community Add-on Discord server and he says he is not repairing this issue downstream, it needs to be fixed in the node-red add-on itself. So @nabbl can you accept @tjorim's PR and get us Home Assistant users back and operational?

Hi all
Something wrong with Get Key Failed?
I've applied the fix from @Achronite and it worked until today (or yesterday), but now it's not working.
Any suggestion?
Thanks

node is broken here also ... hope there is an update soon

@nabbl Could you take a look at the pull request above (https://github.com/nabbl/google-home-notifier/pull/1).

Hi,
The workaround with google tts v0.0.3 worked for me but not anymore since the middle of this week. Same error is back (get key failed from google). I have tried to restart node-red and update the packages but no more luck. Any idea?
Thanks in advance

Have it running on two Win7 PC's.  No problems since the update !

I had same "issue".
Was not an issue....
Try to modify the Google home config of this node with same info.
Restart node red or reboot the he on which it is installed.
Now it's working for me again.

Well, I restarted node-red and even rebooted my pi but I still have the same issue. I'll check a bit more in detail. This is strange because similarly to you @Achronite I have also checked the dependent library and it's 0.0.3. Not sure exactly when it has stopped to work but for sure everything worked fine mid this week because I have IFTTT scenario that trigger tts on my google home and I have not installed anything else since.

Just tried it, still working with 0.0.3.

I have rerun npm update then stopped and restarted node-red and now it's working. Very strange...
Anyway thanks all for your help :)

Hi @gijsje
Same problem for me yesterday. What I did to fix the issue has been to rerun an npm update under directory cd ~/.node-red/node_modules/google-home-notify and then stop and restard node-red by making sure first that 0.0.3 was still the version available in package.json.
Did you tried that?

I will try when I get back on Friday.

Yes, now I remember, I did the same, npm update solved the problem for me.

Hi @gijsje
Same problem for me yesterday. What I did to fix the issue has been to rerun an npm update under directory cd ~/.node-red/node_modules/google-home-notify and then stop and restard node-red by making sure first that 0.0.3 was still the version available in package.json.
Did you tried that?

It worked thanks a lot

Hi,
I realized that I have to run an npm update under cd ~/.node-red/node_modules/google-home-notify then stop/start node-red, each time I reboot my pi otherwise, I got the same error again. Not sure if this is the same for all.

Nope, this in not my case @JBX028
If I reboot my Pi I don't need npm update again.

im having no luck getting this to work on 0.0.6, "get key failed from google" error.

Getting "get key failed error from Google " despite having 0.0.3 in package.json. Any other fixes?

My NodeRed-flows have been running smoothly since the "google-tts-api": "0.0.2-alpha.1" ---> "google-tts-api": "0.0.3" fix was introduced back in September, but as of this morning the "get key failed from google" error message is back :-(

Everyone, as this no longer seems to be maintained, I've checked to see if there were any other projects out there.  See: [https://flows.nodered.org/node/node-red-contrib-cast].  You can install this using the package explorer in the GUI and then just swap out your old node for the 'cast' node, and config your IP of your device.  The good thing about those of us upgrading is that by default the message.payload gets output as speech; so you wont need any other code changes.
The nodes also offer other casting capabilities (Chromecast!) too, but that's to explore another day...
Hope this helps someone, it worked for me anyway!

node-red-contrib-cast is giving me the same error as the Google Home Notify node.
Is anyone else having the same problem?

Yeap. I'm also having this problem now.

There was a new release of node-red-contrib-cast (0.2.2). But please, stop commenting here, it has nothing to do with this node.
For further comments and issues, go to the related repo: https://github.com/Hypnos3/node-red-contrib-cast.

The issue is called by google changing their tts libraries.
I'm not a github expert, but you can fix this by the following commands for a node-red install:
cd ~/.node-red/node_modules/google-home-notify
edit package.json and change the dependency on 'google-tts-api' from '0.0.2-alpha1' to '0.0.3', so it reads:
"dependencies": {
"bluebird": "3.5.1",
"castv2-client": "^1.2.0",
"google-tts-api": "0.0.3"
}
Update the dependency
npm update
Restart node-red
node-red-stop
node-red-start

I used 0.0.4 now it works Thanks Everybody

As of 2019 it needs to be changed to 0.0.4


Does not work fully  with MongoDB

Writes are working fine with Mongo.   Reads fail to find the token.  Any interest in adding mongo support?

Hi!
I can't wait recover of this problem. So, I changed local deps as follows.
I'll waiting for cleared master release.
@moduledoc """
A very simple model for storing tokens generated by guardian.
"""
use Ecto.Schema
# @primary_key {:jti, :string, autogenerate: false }
# primary key setting was changed as follow.
@primary_key {:id, :binary_id, autogenerate: true}
@schema_name Keyword.get(Application.get_env(:guardian_db, GuardianDb), :schema_name) || "guardian_tokens"
@schema_prefix Keyword.get(Application.get_env(:guardian_db, GuardianDb), :prefix) || nil

import Ecto.Changeset
import Ecto.Query

schema @schema_name do
  # jti field added for query in mongodb
  field :jti, :string
  field :typ, :string
  field :aud, :string
  field :iss, :string
  field :sub, :string
  field :exp, :integer
  field :jwt, :string
  field :claims, :map

  timestamps
end

@dhonig a pull request that adds support is welcomed 😀

Since mongodb_ecto doesn't support timestamps in schema definition properly.
So, inserted_at, updated_at fields are not created in mongodb collection.
This issue is resolved with changing "use Ecto.Schema" to "use Ecto.Model"
You can reference this issue in here.

@kevinblade Thats really cool to know.  We ended up chucking ecto on our project in favor of custom Mongo repositories.  In our case we were not getting enough from Ecto to stay with it due to different factors.  We wrote our own mongo guardian token store, which we will see if it can be opensourced for those not using ecto....


[2.1.0]  pointer ‘peaks0’ may be used after ‘realloc’ [-Wuse-after-free]

Hello, while preparing the Debina package of 2.1.0, I got this warning about realloc
src/silx/math/fit/peaks/src/peaks.c: In function ‘seek’:
src/silx/math/fit/peaks/src/peaks.c:210:36: warning: pointer ‘peaks0’ may be used after ‘realloc’ [-Wuse-after-free]
  210 |                             *peaks = peaks0;
      |                             ~~~~~~~^~~~~~~~
src/silx/math/fit/peaks/src/peaks.c:206:41: note: call to ‘realloc’ here
  206 |                         realloc_peaks = realloc(peaks0, max_npeaks * sizeof(double));
      |                                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/silx/math/fit/peaks/src/peaks.c:211:41: warning: pointer ‘relevances0’ may be used after ‘realloc’ [-Wuse-after-free]
  211 |                             *relevances = relevances0;
      |                             ~~~~~~~~~~~~^~~~~~~~~~~~~
src/silx/math/fit/peaks/src/peaks.c:207:46: note: call to ‘realloc’ here
  207 |                         realloc_relevances = realloc(relevances0, max_npeaks * sizeof(double));
      |                                              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Cheers
Fred

Thanks for the report!
Which version of gcc was used? 14?
PR #4147 might fix this. Is there an easy to set-up environment where I could test this?


fix: don't warn on user defined vscode variables (#324)

Added a whitelist for the VSCode task's variables which are unsupported by us.
Now it warns only if variable is in whitelist.
I also moved the TODO comments closer to the whitelist.

LGTM thanks!


Improve caching by running bundle install for all tools in the dependencies phase of CI

Previously, only the dependencies from fastlane (and the root) were cached because bundle install was only run for each tool during the test phase (not the dependencies phase). This should save some time because now they'll be cached.

👍 👍 👍

This is great! Did I see correctly that this cuts about 2 minutes of the build time? If so, that's huge 🚀, no more 🐌

Also +1 for the great branch name

I think it saves about 30 seconds. Recent successful build are just under 5 min 👍

Oh yeah, great work! 🚀


use createToken without CardField

We're doing migration from tipsi-stripe to stripe-react-native
Our backend is toughly coupled with tokens and also we prefer not to change the current UI of card payment.
Is it possible somehow to use createToken without CardField?
Maybe by passing them somehow to the function?
Another some crazy thought: if we do need CardField, I thought to create some sort binding between our custom fields and CardField. I mean, to create invisible CardField and to send needed data from custom fields to it. Is it possible?

Are you collecting the card data yourself in your own custom UI? Please be aware this requires additional PCI compliance steps, which is why we recommend integrating with CardField


Working

Is this working?

@StDensity  No, it doesn't work anymore, it's very old. and they ban you


DatabaseObjectNotClosedException thrown on 9.8.0

Android device: Moto G (2nd Gen)
Android OS version: Android 6.0
Google Play Services version: 3.0.0
Firebase/Play Services SDK version: 9.8.0

Hi guys! I'm trying to use the latest version of the messaging library but I'm getting an DatabaseObjectNotClosedException exception and it says that the  google_app_measurement_local.db file is closed. The funny thing is that if I change the version of the library to, lets say 9.6.1, this doesn't happen and the notifications arrived successfully.
My gradle file is:
dependencies {
    compile fileTree(include: ['*.jar'], dir: 'libs')
    compile 'com.android.support:appcompat-v7:25.0.0'
    compile 'com.android.support:design:25.0.0'
    compile 'com.android.support:cardview-v7:25.0.0'
    compile 'com.google.android.gms:play-services-gcm:9.8.0'
    compile 'com.google.android.gms:play-services-maps:9.8.0'

    compile 'com.google.firebase:firebase-database:9.8.0'
    compile 'com.google.firebase:firebase-storage:9.8.0'
    compile 'com.google.firebase:firebase-auth:9.8.0'
    compile 'com.google.firebase:firebase-messaging:9.8.0'

    ... (other libraries)
}

(I'm trying to have support for both, GCM and FCM for now, just in case our FCM server breaks down we need a backup)
I've been looking on SO or similar and haven't found a solution to this.
Some links:

http://stackoverflow.com/questions/40364204/firebase-the-database-google-app-measurement-local-db-is-not-open
http://stackoverflow.com/questions/40307855/firebase-is-firing-a-database-leak

So basically, my questions are:

Why does this happen using the latest version and not the previous one?
Is it feasible to have both, GCM and FCM in my app?

Thanks in advance

@betomaluje sorry for the slow response here but we're looking into this!  Thank you for the report.

Hi! have you looked at this? I still can't upgrade the play services of my project

I am getting the same error and app crash, when it goes to background.
Got any solution?

Hi all.  We have looked at this and there will be a fix in a future release.  Right now there are no known workarounds for the broken versions, but I will update here if there are.

Seeing this exception on 10.0.1, when enabling StrictMode.  No crash. Is there an issue opened on Firebase?

Seeing similar exception with 10.0.1
12-30 13:07:42.527 513-522/com.sense.androidclient E/StrictMode: Finalizing a Cursor that has not been deactivated or closed. database = /data/user/0/com.sense.androidclient/databases/google_app_measurement_local.db, table = null, query = select count(1) from messages                                                                  android.database.sqlite.DatabaseObjectNotClosedException: Application did not close the cursor or database object that was opened here                                                                      at android.database.sqlite.SQLiteCursor.<init>(SQLiteCursor.java:98)                                                                      at android.database.sqlite.SQLiteDirectCursorDriver.query(SQLiteDirectCursorDriver.java:50)                                                                      at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1318)                                                                      at android.database.sqlite.SQLiteDatabase.rawQuery(SQLiteDatabase.java:1257)                                                                      at com.google.android.gms.internal.zzatg.zza(Unknown Source)                                                                      at com.google.android.gms.internal.zzatg.zza(Unknown Source)                                                                      at com.google.android.gms.internal.zzatw.zzc(Unknown Source)                                                                      at com.google.android.gms.internal.zzatu.zzb(Unknown Source)                                                                      at com.google.android.gms.internal.zzatu.zza(Unknown Source)                                                                      at com.google.android.gms.internal.zzatu$4.run(Unknown Source)                                                                      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:428)                                                                      at java.util.concurrent.FutureTask.run(FutureTask.java:237)                                                                      at com.google.android.gms.internal.zzato$zzd.run(Unknown Source)

Same problem here:
compile 'com.google.firebase:firebase-core:9.8.0'
compile 'com.google.firebase:firebase-crash:9.8.0'
compile 'com.google.firebase:firebase-messaging:9.8.0'
compile 'com.google.firebase:firebase-ads:9.8.0'

+1

This issue is still known to be present in 10.0.1.
When a release goes out that contains the fix I will update this issue.

Thanks @samtstern. Any ETA on it? Unfortunately I have shipped a release with this and this only showed up in logs afterwards. It seems that this issue is causing the biggest problems on Android 6.0.1 phones for some reason?

Seeing this on 6.0.1 with StrictMode -- for what it's worth: only occurs on first clean install.

Still seeing this in 10.2.0 whenever an activity or fragment is destroyed.
3-01 19:58:49.070 24205-24216/com.theclinician.oneclinic E/StrictMode: Finalizing a Cursor that has not been deactivated or closed. database = /data/user/0/com.theclinician.oneclinic/databases/google_app_measurement_local.db, table = null, query = select count(1) from messages                                                                         android.database.sqlite.DatabaseObjectNotClosedException: Application did not close the cursor or database object that was opened here                                                                             at android.database.sqlite.SQLiteCursor.<init>(SQLiteCursor.java:98)                                                                             at android.database.sqlite.SQLiteDirectCursorDriver.query(SQLiteDirectCursorDriver.java:50)                                                                             at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1318)                                                                             at android.database.sqlite.SQLiteDatabase.rawQuery(SQLiteDatabase.java:1257)                                                                             at com.google.android.gms.internal.zzatv.zza(Unknown Source)                                                                             at com.google.android.gms.internal.zzatv.zza(Unknown Source)                                                                             at com.google.android.gms.internal.zzaul.zzc(Unknown Source)                                                                             at com.google.android.gms.internal.zzauj.zzb(Unknown Source)                                                                             at com.google.android.gms.internal.zzauj.zza(Unknown Source)                                                                             at com.google.android.gms.internal.zzauj$8.run(Unknown Source)                                                                             at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:428)                                                                             at java.util.concurrent.FutureTask.run(FutureTask.java:237)                                                                             at com.google.android.gms.internal.zzaud$zzd.run(Unknown Source) 03-01 19:59:16.932 24205-24216/com.theclinician.oneclinic E/StrictMode: A resource was acquired at attached stack trace but never released. See java.io.Closeable for information on avoiding resource leaks.                                                                         java.lang.Throwable: Explicit termination method 'close' not called                                                                             at dalvik.system.CloseGuard.open(CloseGuard.java:180)                                                                             at android.database.CursorWindow.<init>(CursorWindow.java:111)                                                                             at android.database.AbstractWindowedCursor.clearOrCreateWindow(AbstractWindowedCursor.java:198)                                                                             at android.database.sqlite.SQLiteCursor.fillWindow(SQLiteCursor.java:138)                                                                             at android.database.sqlite.SQLiteCursor.getCount(SQLiteCursor.java:132)                                                                             at android.database.AbstractCursor.moveToPosition(AbstractCursor.java:219)                                                                             at android.database.AbstractCursor.moveToFirst(AbstractCursor.java:258)                                                                             at com.google.android.gms.internal.zzatv.zza(Unknown Source)                                                                             at com.google.android.gms.internal.zzatv.zza(Unknown Source)                                                                             at com.google.android.gms.internal.zzaul.zzc(Unknown Source)                                                                             at com.google.android.gms.internal.zzauj.zzb(Unknown Source)                                                                             at com.google.android.gms.internal.zzauj.zza(Unknown Source)                                                                             at com.google.android.gms.internal.zzauj$8.run(Unknown Source)                                                                             at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:428)                                                                             at java.util.concurrent.FutureTask.run(FutureTask.java:237)                                                                             at com.google.android.gms.internal.zzaud$zzd.run(Unknown Source) 03-01 19:59:16.933 24205-24216/com.theclinician.oneclinic E/StrictMode: Finalizing a Cursor that has not been deactivated or closed. database = /data/user/0/com.theclinician.oneclinic/databases/google_app_measurement_local.db, table = null, query = select count(1) from messages                                                                         android.database.sqlite.DatabaseObjectNotClosedException: Application did not close the cursor or database object that was opened here                                                                             at android.database.sqlite.SQLiteCursor.<init>(SQLiteCursor.java:98)                                                                             at android.database.sqlite.SQLiteDirectCursorDriver.query(SQLiteDirectCursorDriver.java:50)                                                                             at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1318)                                                                             at android.database.sqlite.SQLiteDatabase.rawQuery(SQLiteDatabase.java:1257)                                                                             at com.google.android.gms.internal.zzatv.zza(Unknown Source)                                                                             at com.google.android.gms.internal.zzatv.zza(Unknown Source)                                                                             at com.google.android.gms.internal.zzaul.zzc(Unknown Source)                                                                             at com.google.android.gms.internal.zzauj.zzb(Unknown Source)                                                                             at com.google.android.gms.internal.zzauj.zza(Unknown Source)                                                                             at com.google.android.gms.internal.zzauj$8.run(Unknown Source)                                                                             at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:428)                                                                             at java.util.concurrent.FutureTask.run(FutureTask.java:237)                                                                             at com.google.android.gms.internal.zzaud$zzd.run(Unknown Source) 03-01 19:59:23.901 24205-24216/com.theclinician.oneclinic E/StrictMode: A resource was acquired at attached stack trace but never released. See java.io.Closeable for information on avoiding resource leaks.                                                                         java.lang.Throwable: Explicit termination method 'close' not called                                                                             at dalvik.system.CloseGuard.open(CloseGuard.java:180)                                                                             at android.database.CursorWindow.<init>(CursorWindow.java:111)                                                                             at android.database.AbstractWindowedCursor.clearOrCreateWindow(AbstractWindowedCursor.java:198)                                                                             at android.database.sqlite.SQLiteCursor.fillWindow(SQLiteCursor.java:138)                                                                             at android.database.sqlite.SQLiteCursor.getCount(SQLiteCursor.java:132)                                                                             at android.database.AbstractCursor.moveToPosition(AbstractCursor.java:219)                                                                             at android.database.AbstractCursor.moveToFirst(AbstractCursor.java:258)                                                                             at com.google.android.gms.internal.zzatv.zza(Unknown Source)                                                                             at com.google.android.gms.internal.zzatv.zza(Unknown Source)                                                                             at com.google.android.gms.internal.zzaul.zzc(Unknown Source)                                                                             at com.google.android.gms.internal.zzauj.zzb(Unknown Source)                                                                             at com.google.android.gms.internal.zzauj.zza(Unknown Source)                                                                             at com.google.android.gms.internal.zzauj$8.run(Unknown Source)                                                                             at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:428)                                                                             at java.util.concurrent.FutureTask.run(FutureTask.java:237)                                                                             at com.google.android.gms.internal.zzaud$zzd.run(Unknown Source) 03-01 19:59:23.902 24205-24216/com.theclinician.oneclinic E/StrictMode: Finalizing a Cursor that has not been deactivated or closed. database = /data/user/0/com.theclinician.oneclinic/databases/google_app_measurement_local.db, table = null, query = select count(1) from messages                                                                         android.database.sqlite.DatabaseObjectNotClosedException: Application did not close the cursor or database object that was opened here                                                                             at android.database.sqlite.SQLiteCursor.<init>(SQLiteCursor.java:98)                                                                             at android.database.sqlite.SQLiteDirectCursorDriver.query(SQLiteDirectCursorDriver.java:50)                                                                             at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1318)                                                                             at android.database.sqlite.SQLiteDatabase.rawQuery(SQLiteDatabase.java:1257)                                                                             at com.google.android.gms.internal.zzatv.zza(Unknown Source)                                                                             at com.google.android.gms.internal.zzatv.zza(Unknown Source)                                                                             at com.google.android.gms.internal.zzaul.zzc(Unknown Source)                                                                             at com.google.android.gms.internal.zzauj.zzb(Unknown Source)                                                                             at com.google.android.gms.internal.zzauj.zza(Unknown Source)                                                                             at com.google.android.gms.internal.zzauj$8.run(Unknown Source)                                                                             at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:428)                                                                             at java.util.concurrent.FutureTask.run(FutureTask.java:237)                                                                             at com.google.android.gms.internal.zzaud$zzd.run(Unknown Source) 03-01 19:59:33.570 24205-24216/com.theclinician.oneclinic E/StrictMode: A resource was acquired at attached stack trace but never released. See java.io.Closeable for information on avoiding resource leaks.                                                                         java.lang.Throwable: Explicit termination method 'close' not called                                                                             at dalvik.system.CloseGuard.open(CloseGuard.java:180)                                                                             at android.database.CursorWindow.<init>(CursorWindow.java:111)                                                                             at android.database.AbstractWindowedCursor.clearOrCreateWindow(AbstractWindowedCursor.java:198)                                                                             at android.database.sqlite.SQLiteCursor.fillWindow(SQLiteCursor.java:138)                                                                             at android.database.sqlite.SQLiteCursor.getCount(SQLiteCursor.java:132)                                                                             at android.database.AbstractCursor.moveToPosition(AbstractCursor.java:219)                                                                             at android.database.AbstractCursor.moveToFirst(AbstractCursor.java:258)                                                                             at com.google.android.gms.internal.zzatv.zza(Unknown Source)                                                                             at com.google.android.gms.internal.zzatv.zza(Unknown Source)                                                                             at com.google.android.gms.internal.zzaul.zzc(Unknown Source)                                                                             at com.google.android.gms.internal.zzauj.zzb(Unknown Source)                                                                             at com.google.android.gms.internal.zzauj.zza(Unknown Source)                                                                             at com.google.android.gms.internal.zzauj$8.run(Unknown Source)                                                                             at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:428)                                                                             at java.util.concurrent.FutureTask.run(FutureTask.java:237)                                                                             at com.google.android.gms.internal.zzaud$zzd.run(Unknown Source) 03-01 19:59:33.570 24205-24216/com.theclinician.oneclinic E/StrictMode: Finalizing a Cursor that has not been deactivated or closed. database = /data/user/0/com.theclinician.oneclinic/databases/google_app_measurement_local.db, table = null, query = select count(1) from messages                                                                         android.database.sqlite.DatabaseObjectNotClosedException: Application did not close the cursor or database object that was opened here                                                                             at android.database.sqlite.SQLiteCursor.<init>(SQLiteCursor.java:98)                                                                             at android.database.sqlite.SQLiteDirectCursorDriver.query(SQLiteDirectCursorDriver.java:50)                                                                             at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1318)                                                                             at android.database.sqlite.SQLiteDatabase.rawQuery(SQLiteDatabase.java:1257)                                                                             at com.google.android.gms.internal.zzatv.zza(Unknown Source)                                                                             at com.google.android.gms.internal.zzatv.zza(Unknown Source)                                                                             at com.google.android.gms.internal.zzaul.zzc(Unknown Source)                                                                             at com.google.android.gms.internal.zzauj.zzb(Unknown Source)                                                                             at com.google.android.gms.internal.zzauj.zza(Unknown Source)                                                                             at com.google.android.gms.internal.zzauj$8.run(Unknown Source)                                                                             at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:428)                                                                             at java.util.concurrent.FutureTask.run(FutureTask.java:237)                                                                             at com.google.android.gms.internal.zzaud$zzd.run(Unknown Source)

Same here :(

It would be awesome if this gets fixed.

+1

Just close the poor cursor

How frequently is this crashing? Did anyone by chance get a
'java.lang.RuntimeException: Could not read input channel file descriptors from parcel' crash?
because I got it once after adding firebase analytics.
Along with 'Finalizing a Cursor that has not been deactivated or closed' every time but no crash in StrictMode

Same here:
Finalizing a Cursor that has not been deactivated or closed. database = /data/user/0/com.mail.mobile.android.mail/databases/google_app_measurement_local.db, table = null, query = select count(1) from messages  android.database.sqlite.DatabaseObjectNotClosedException: Application did not close the cursor or database object that was opened here      at android.database.sqlite.SQLiteCursor.<init>(SQLiteCursor.java:98)      at android.database.sqlite.SQLiteDirectCursorDriver.query(SQLiteDirectCursorDriver.java:50)      at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1318)      at android.database.sqlite.SQLiteDatabase.rawQuery(SQLiteDatabase.java:1257)      at com.google.android.gms.internal.zzatg.zza(Unknown Source)      at com.google.android.gms.internal.zzatg.zza(Unknown Source)      at com.google.android.gms.internal.zzatw.zzc(Unknown Source)      at com.google.android.gms.internal.zzatu.zzb(Unknown Source)      at com.google.android.gms.internal.zzatu.zza(Unknown Source)      at com.google.android.gms.internal.zzatu$4.run(Unknown Source)      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:428)      at java.util.concurrent.FutureTask.run(FutureTask.java:237)      at com.google.android.gms.internal.zzato$zzd.run(Unknown Source)

Same here

Can anyone provide a reproduction method for this?  Also does this crash the entire app or just appear in the logs?

it happens when changing activities, or resuming one. Yes, the app crashes. It does not crash on run with StrictMode.setVmPolicy with penaltyDeath disabled though, it just keeps showing up in logcat
E/StrictMode: Finalizing a Cursor that has not been deactivated or closed. database = /data/user/0/< package name >/databases/google_app_measurement_local.db, table = null, query = select count(1) from messages
                                                                       android.database.sqlite.DatabaseObjectNotClosedException: Application did not close the cursor or database object that was opened here
                                                                           at android.database.sqlite.SQLiteCursor.<init>(SQLiteCursor.java:98)
                                                                           at android.database.sqlite.SQLiteDirectCursorDriver.query(SQLiteDirectCursorDriver.java:50)
                                                                           at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1318)
                                                                           at android.database.sqlite.SQLiteDatabase.rawQuery(SQLiteDatabase.java:1257)
                                                                           at com.google.android.gms.internal.zzatv.zza(Unknown Source)
                                                                           at com.google.android.gms.internal.zzatv.zza(Unknown Source)
                                                                           at com.google.android.gms.internal.zzaul.zzc(Unknown Source)
                                                                           at com.google.android.gms.internal.zzauj.zzb(Unknown Source)
                                                                           at com.google.android.gms.internal.zzauj.zza(Unknown Source)
                                                                           at com.google.android.gms.internal.zzauj$8.run(Unknown Source)
                                                                           at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:428)
                                                                           at java.util.concurrent.FutureTask.run(FutureTask.java:237)
                                                                           at com.google.android.gms.internal.zzaud$zzd.run(Unknown Source)

@fuzzyBatman can you provide the code from your Activity onCreate or onStart that may be relevant?

@samtstern this is the shortest onCreate() method in the project. onResume() and onStart() are empty

switching to this activity back and forth 3 times displayed the relevant log
D/Settings Activity: onCreate - entry
D/Settings Activity: onCreate - exit
D/Settings Activity: onStart
D/Settings Activity: onResume
D/OpenGLRenderer: endAllActiveAnimators on 0x8333d880 (RippleDrawable) with handle 0x7a7973d0
E/StrictMode: Finalizing a Cursor that has not been deactivated or closed. database = /data/user/0/<my-package-name>/databases/google_app_measurement_local.db, table = null, query = select count(1) from messages
              android.database.sqlite.DatabaseObjectNotClosedException: Application did not close the cursor or database object that was opened here
                  at android.database.sqlite.SQLiteCursor.<init>(SQLiteCursor.java:98)
                  at android.database.sqlite.SQLiteDirectCursorDriver.query(SQLiteDirectCursorDriver.java:50)
                  at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1318)
                  at android.database.sqlite.SQLiteDatabase.rawQuery(SQLiteDatabase.java:1257)
                  at com.google.android.gms.internal.zzatv.zza(Unknown Source)
                  at com.google.android.gms.internal.zzatv.zza(Unknown Source)
                  at com.google.android.gms.internal.zzaul.zzc(Unknown Source)
                  at com.google.android.gms.internal.zzauj.zzb(Unknown Source)
                  at com.google.android.gms.internal.zzauj.zza(Unknown Source)
                  at com.google.android.gms.internal.zzauj$8.run(Unknown Source)
                  at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:428)
                  at java.util.concurrent.FutureTask.run(FutureTask.java:237)
                  at com.google.android.gms.internal.zzaud$zzd.run(Unknown Source)
E/StrictMode: A resource was acquired at attached stack trace but never released. See java.io.Closeable for information on avoiding resource leaks.
              java.lang.Throwable: Explicit termination method 'close' not called
                  at dalvik.system.CloseGuard.open(CloseGuard.java:180)
                  at android.database.CursorWindow.<init>(CursorWindow.java:111)
                  at android.database.AbstractWindowedCursor.clearOrCreateWindow(AbstractWindowedCursor.java:198)
                  at android.database.sqlite.SQLiteCursor.fillWindow(SQLiteCursor.java:138)
                  at android.database.sqlite.SQLiteCursor.getCount(SQLiteCursor.java:132)
                  at android.database.AbstractCursor.moveToPosition(AbstractCursor.java:219)
                  at android.database.AbstractCursor.moveToFirst(AbstractCursor.java:258)
                  at com.google.android.gms.internal.zzatv.zza(Unknown Source)
                  at com.google.android.gms.internal.zzatv.zza(Unknown Source)
                  at com.google.android.gms.internal.zzaul.zzc(Unknown Source)
                  at com.google.android.gms.internal.zzauj.zzb(Unknown Source)
                  at com.google.android.gms.internal.zzauj.zza(Unknown Source)
                  at com.google.android.gms.internal.zzauj$8.run(Unknown Source)
                  at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:428)
                  at java.util.concurrent.FutureTask.run(FutureTask.java:237)
                  at com.google.android.gms.internal.zzaud$zzd.run(Unknown Source)

@fuzzyBatman thank you!  That is super helpful.

Hey all.  I just heard back from the team and apparently the fix for this got delayed but will be included in the next SDK release, which should be in a matter of weeks.  I will keep this issue closed until it comes out, thank you all for your patience.

E/StrictMode: A resource was acquired at attached stack trace but never released. See java.io.Closeable for information on avoiding resource leaks.                                                                       java.lang.Throwable: Explicit termination method 'close' not called                                                                           at dalvik.system.CloseGuard.open(CloseGuard.java:180)                                                                           at android.database.CursorWindow.<init>(CursorWindow.java:111)                                                                           at android.database.AbstractWindowedCursor.clearOrCreateWindow(AbstractWindowedCursor.java:198)                                                                           at android.database.sqlite.SQLiteCursor.fillWindow(SQLiteCursor.java:138)                                                                           at android.database.sqlite.SQLiteCursor.getCount(SQLiteCursor.java:132)                                                                           at android.database.AbstractCursor.moveToPosition(AbstractCursor.java:219)                                                                           at android.database.AbstractCursor.moveToFirst(AbstractCursor.java:258)                                                                           at com.google.android.gms.internal.zzatv.zza(Unknown Source)                                                                           at com.google.android.gms.internal.zzatv.zza(Unknown Source)                                                                           at com.google.android.gms.internal.zzaul.zzc(Unknown Source)                                                                           at com.google.android.gms.internal.zzauj.zzb(Unknown Source)                                                                           at com.google.android.gms.internal.zzauj.zza(Unknown Source)                                                                           at com.google.android.gms.internal.zzauj$8.run(Unknown Source)                                                                           at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:428)                                                                           at java.util.concurrent.FutureTask.run(FutureTask.java:237)                                                                           at com.google.android.gms.internal.zzaud$zzd.run(Unknown Source) 05-04 10:04:58.039 16651-16663/com.bookmark.money.debug E/StrictMode: Finalizing a Cursor that has not been deactivated or closed. database = /data/user/0/com.bookmark.money.debug/databases/google_app_measurement_local.db, table = null, query = select count(1) from messages                                                                       android.database.sqlite.DatabaseObjectNotClosedException: Application did not close the cursor or database object that was opened here                                                                           at android.database.sqlite.SQLiteCursor.<init>(SQLiteCursor.java:98)                                                                           at android.database.sqlite.SQLiteDirectCursorDriver.query(SQLiteDirectCursorDriver.java:50)                                                                           at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1318)                                                                           at android.database.sqlite.SQLiteDatabase.rawQuery(SQLiteDatabase.java:1257)                                                                           at com.google.android.gms.internal.zzatv.zza(Unknown Source)                                                                           at com.google.android.gms.internal.zzatv.zza(Unknown Source)                                                                           at com.google.android.gms.internal.zzaul.zzc(Unknown Source)                                                                           at com.google.android.gms.internal.zzauj.zzb(Unknown Source)                                                                           at com.google.android.gms.internal.zzauj.zza(Unknown Source)                                                                           at com.google.android.gms.internal.zzauj$8.run(Unknown Source)                                                                           at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:428)                                                                           at java.util.concurrent.FutureTask.run(FutureTask.java:237)                                                                           at com.google.android.gms.internal.zzaud$zzd.run(Unknown Source)
new update 10.2.4

same issue on 10.2.4 . Is there an estimate, when it will be fixed?

Same issue on 10.2.6. When this issue will be fixed?

+1 I got many crashes on Samsung GT-S5303B

@petrovichtim you should never use strict mode in release builds

@joshfriend  I don't use it. My stack trace is  Exception android.database.CursorWindowAllocationException: Cursor window allocation of 2048 kb failed. android.database.CursorWindow.<init> (CursorWindow.java:112) android.database.CursorWindow.<init> (CursorWindow.java:100) android.database.AbstractWindowedCursor.clearOrCreateWindow (AbstractWindowedCursor.java:198) android.database.sqlite.SQLiteCursor.clearOrCreateWindow (SQLiteCursor.java:364) android.database.sqlite.SQLiteCursor.fillWindow (SQLiteCursor.java:162) android.database.sqlite.SQLiteCursor.getCount (SQLiteCursor.java:156) android.database.AbstractCursor.moveToPosition (AbstractCursor.java:161) android.database.AbstractCursor.move (AbstractCursor.java:197) bre.b (bre.java:152) bru.run (bru.java:3124) java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1076) java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:569) java.lang.Thread.run (Thread.java:856)
While I don't use SQLite in the project at all

It appears to be fixed in version 11.0.1.

This should definitely be fixed in version 11.0.1.  If anyone can reproduce on that version, please let me know.

compile 'com.google.firebase:firebase-messaging:11.2.0'

Failed to open database '/data/user/0/xxx/databases/google_app_measurement_local.db'.
android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14): Could not open database
at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:209)
at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:193)
at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:463)
at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:185)
at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:177)
at android.database.sqlite.SQLiteDatabase.openInner(SQLiteDatabase.java:808)
at android.database.sqlite.SQLiteDatabase.open(SQLiteDatabase.java:793)
at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:696)
at android.app.ContextImpl.openOrCreateDatabase(ContextImpl.java:690)
at android.content.ContextWrapper.openOrCreateDatabase(ContextWrapper.java:299)
at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:223)
at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:163)
at com.google.android.gms.internal.zzcbl.getWritableDatabase(Unknown Source)
at com.google.android.gms.internal.zzcbk.getWritableDatabase(Unknown Source)
at com.google.android.gms.internal.zzcbk.zzb(Unknown Source)
at com.google.android.gms.internal.zzcbk.zza(Unknown Source)
at com.google.android.gms.internal.zzceg.zzc(Unknown Source)
at com.google.android.gms.internal.zzcdo.zzb(Unknown Source)
at com.google.android.gms.internal.zzcdo.zza(Unknown Source)
at com.google.android.gms.internal.zzcdw.run(Unknown Source)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:428)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at com.google.android.gms.internal.zzccn.run(Unknown Source)


Guide on imposter syndrome

I would write this guide, but I am not smart enough to  ☹

not smart enough to write this guide so not doing it (also, there are better youtube videos than what we could reasonable write imo)


Plugin not available in version 2022.2.2

I get this error message:
Not compatible with the version of your running IDE (IntelliJ IDEA 2022.2.2)

Hello @rcastagno,
Thanks for reporting. Plugin update will be available soon

v0.4.0 is released


Use the right bind flag name for minio

Otherwise cd deployments/compose; docker-compose up never brings up minio.

Bad one, sorry.

Was due to an old installed version.  Need to figure out how to force a new-enough version.


Added generateEnumMap back to flow output.

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

@ajbogh Thanks for taking the time to post this PR. a few minor comments:
Can you remove the package-lock.json file?
Also, how about adding a test for this case?

As discussed, let's hold off on this for now unless it's a pain others report in which case we can add an optional flag for this ability. Either way, long term, we can't really rely on safely generating utility constants like this as they may conflict with other type definition names. We've seen conflicts with ValueMap in particular in our internal IDL registry.
Secondly, thriftrw appears to decode these enums as strings on the JS side. Golang seems to decode these as integer enums. thrift2flow is only compatible with generated code from thriftrw specifically. Generating code compatible with go thrift runtime might be possible in some cases but likely not all. Instead, interlanguage communication should happen over one of the thrift protocols.


Communication with background script

This isn't an issue with the library itself, but just hoping to get you feedback. If the content script was just a normal script and didn't embed js links in the dom, you could communicate with a background script using:
    chrome.runtime.sendMessage data, (response) ->

However, if you embed the main.js in to the and I define some behavior on the read_email event, I need to send some messages to a background script. Because I'm now in the actual tab, not in the content script, I haven't been able to use chrome.runtime.sendMessage because it seems like it's out of context of the extension at that point.
Do you have suggestions on getting back in to the extension?

This link demonstrates what I think you are trying to achieve. This is devtools specific, but the concept is the same for injected scripts. You can add window.postMessage to main.js, and listen for the message in the content.js
injected agent
|
| window.postMessage()
V
content script
|
| chrome.runtime.sendMessage()
V
background script

More info here as well: http://stackoverflow.com/questions/25838804/gmail-extension-sendmessage-to-background-from-page-context


Ast update

Updates the AST per https://gist.github.com/kpdecker/cb3592114071c3f80604
Breaking changes: Many

AST structure and API completely refactored
invokePartial now uses a call pattern that is closer to helpers

Related to #889

Released in 3.0.0

:+1: wanted to say thanks for this for a while, much appreciated


add HiveCatalog support Decimal type.

fix exception: org.apache.flink.table.data.DecimalData cannot be cast to java.math.BigDecimal

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

add partition settings have no effect

add partition settings have no effect


Abandoned

Has the repo been abandoned?

@CThomas87 Sorry I do not have time to maintain this library.


Should prompts work when the input file is stdin?

I'm trying to use the confirmation_option decorator. When I add an argument of type click.File('r') and give it '-' on the command line - the confirmation prompt is reading stdin instead of /dev/tty
I expect the confirmation prompt to be read from /dev/tty when the input file is stdin.
Is there a way to do this?
Apologies if I missed it in the documentation.
I understand there's getchar to read characters from the terminal.

relates to #300


feat: blocks can consume elements during hydration

Is your feature request related to a problem? Please describe.
This is how our packages/react-server setup works:
Take some arbitrary component:
function Component() {
	return
foo

}

During SSR, allow react to render the HTML (ref)
Internally, this is passed into React.renderToString, which is sent to the client

During hydration, the element from SSR is replaced with a block (ref)
This is a full DOM element replacement.

This is obviously inefficient, we are basically replacing a lot of the DOM for no reason here.
Describe the solution you'd like
We need something that will set this.l of a block instance for hydration. Essentially we need to set a hydration id to the loader component with useId during SSR. Then, during client render, we can grab the element via document.querySelector and set the this.l of a block instance.
You may hit some issues. We may need to make a "hydration" mount to get the cache correctly.
This allows for efficient hydration without the need to replace the element.

Curious to see what happens with this. I'll see if I can try this after the current issue I'm working on.


replace DockerHub user from "kozo2" to "cytoscape"

@keiono created an automated build for this repository. See https://hub.docker.com/r/cytoscape/jupyter-cytoscape/

Thanks @kozo2!


Is it possible to get notified when a user scrolls left or right?

I tried using this
-(void) scrollViewWillBeginDragging:(UIScrollView *)scrollView

But it looks like scrollView is being managed by scrollManager. I was wondering if there's an option to get notified. It doesn't have to be NSNotification. Just something that will let me know that the user has swiped.

Does setting my view as a delegate to JTHorizontalCalendarView safe?

Yes you can use the scrollview delegate for JTHorizontalCalendarView and JTVerticalCalendarView.
But not for JTCalendarMenuView.

Did you get the sorted? I need to implement this and I see no other way unless altering the internal API which I shouldn't do.
Could you provide a bit more steps?


Review GO terms referencing myotube

Myotube in CL has recently been broadened to cover both arthropod somatic muscle and skeletal muscle fibers (formerly restricted to latter) - with new subclasses added for skeletal muscle fiber and somatic muscle myotube.  See this ticket and this commit.
In the light of these changes, terms in GO referencing myotubes (and the few referencing skeletal muscle fibers) need to be reviewed for whether they have skeletal muscle specific aspects to their definitions and relations.  If so, need to decide whether to add new specific or new general terms.  Probably the former but should review annotations first.
Reported by: dosumis
Original Ticket: geneontology/ontology-requests/10400

@ukemi
I think you did a related issue recently; did your changes take care of this issue here ?

Checked all terms with 'myotube', and they are all either general (ie, do not mention specifically somatic muscle and skeletal muscle fibers), or they are specific to somatic muscles.
So it may be that we need more specific terms for skeletal muscle fibers but right now extsting terms and definitions are correct.


Handle tags returned in an unexpected order

Closes #3404
Code Changes

[x] Add a failing test for tags that are returned in an unexpected order
[x] Sort matched tags in descending order to ensure the increment is as expected

Steps to Confirm

[ ] Inspecting the matched tags (2.14.1a*) will show the two in tests as out of sequence. Reverting the last commit will show the test failing in that scenario

Pre-Merge Checklist

[x] All CI Pipelines Succeeded
Documentation:

[ ] documentation complete, PR opened in fidesdocs
[ ] documentation issue created in fidesdocs

[x] Issue Requirements are Met
[x] Relevant Follow-Up Issues Created
[x] Update CHANGELOG.md
[x] For API changes, the Postman collection has been updated

Description Of Changes
I did this manually last night to force 2.14.1a2 to push, then created an issue and PR to see if this was the right path forward.

oh also, i forgot to mention - we should make the same changes over on the fidesplus side! we've got the same nox commands over there, unfortunately we don't have a good way of sharing nox code between the two repos so we've gotta just c+p for now. hopefully the tagging code stabilizes after this change! 🤞

oh also, i forgot to mention - we should make the same changes over on the fidesplus side! we've got the same nox commands over there, unfortunately we don't have a good way of sharing nox code between the two repos so we've gotta just c+p for now. hopefully the tagging code stabilizes after this change! 🤞

Once we are good here I can pop a PR open over there as well, thanks for calling that out!


Update submissions-admin.md

Added link to CELA privacy and compliance notice.

@chrisda could you please merge this request?


Fix template instantiation for MSVC

Scope & Purpose
Fix a compile error on windows when google tests are disabled.

[X] Bug-Fix for devel-branch

Testing & Verification
This change is a trivial rework / code cleanup without any test coverage.

http://jenkins01.arangodb.biz:8080/job/arangodb-ANY-windows-packages/545

Tests blue except unrelated failures (in Enterprise branch).


fix(command): Restore environment variables before calling exec

Previously, the command would overwrite the HOST and PORT variables based on the hostname and port of the service which we would check for being available. This change prevents these variables from being overwritten, which allows you to set them outside the command.
BREAKING CHANGE: HOST, PORT and other internally used environment variables are not overwritten anymore. If you use these, then you need to manually supply them.

This pull request contains the content of 9964904 that was previously in https://github.com/eficode/wait-for/pull/27.
@Addono I have added 2 test cases to the commit additionally. Please take a look.


[SUGGESTION] Make the back button in preferences more contrastable

I was trying to leave this page for at least 5 seconds before I found the back button
also, please make it so pressing esc goes back

I'm unsure how to add contrast to the button. Making it green will make the window more cluttered. The best solution would be to move the back button, but I don't know where

In the next release the button is moved to the bottom which fixes the issue


Add IDEA IntelliJ to .gitignore

This pull request add ".idea" folder into .gitignore file

Current coverage is 3.13% (diff: 100%)

Merging #131 into master will not change coverage

@@            master      #131   diff @@
========================================
  Files           33        33
  Lines         7841      7841
  Methods          0         0
  Messages         0         0
  Branches         0         0
========================================
  Hits           246       246
  Misses        7575      7575
  Partials        20        20

Powered by Codecov. Last update b5bfab9...7ea943d

LGTM

I have this in my global .gitignore in my home directory, because it's my choice that I use that editor, but nevertheless having this in ours as well won't do bad.
LGTM

Just WHY??? This is nothing that should be handled by projects, we would end up with so many useless ignores. That is something everybody got to have in his personal global gitignore.

In fact, I dont' like global config.

But than you have to add so much editor/user specific stuff. Just add a simple gitignore to your local gitconfig which ignores files/folders specific to YOUR editor and don't put this general stuff in there :(

echo ".DS_Store" >| ~/.gitignore
echo ".idea" >> ~/.gitignore

echo "[core]" >> ~/.gitconfig
echo "  excludesfile = ~/.gitignore" >> ~/.gitconfig

And nobody cares about the editor configs anymore.

IDE-specific files should be in a user's own global .gitignore, not in the project-specific ones.

So where should it be?

@lunny
http://stackoverflow.com/a/7335487/749521

That way, it will ignore IDEA files for all Git repo's you have.


PSUControl with sirishortcut ?

Hi i'm wondring if the On/Off button has a link? so i can add it on sirishortcut and toggle it on and off from siri with my voice

Good idea. I have not created a Siri shortcut for this plugin. Adding it to next release


[frugually-deep] update to  v0.15.10 p0

Describe the pull request

What does your PR fix?

update to  v0.15.10 p0

Which triplets are supported/not supported? Have you updated the CI baseline?

yes

Does your PR follow the maintainer guide?

yes

If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?

yes

Feature 'double' tested successfully in the following triplet:

x86-windows
x64-windows
x64-windows-static


classIdPrefix interpolations broken

It looks like using a classIdPrefix string with interpolations like [name] through a webpack config is broken. I think it is due to a typo here, classIdPref instead of classIdPrefix.
The example from the readme using classIdPrefix: '[name]-[hash:8]__' uses the literal string as a prefix instead of interpolating it. Using classIdPrefix: true to use the name as a prefix does work.

I'm having this issue with the gatsby plugin.... can't even get classIdPrefix: true to work. What is this a duplicate of?


Adding as it is new to ES and needed by Doximity.

@DanielNill doesn't show removal of your custom_json method because you never merged it into the fork's master (bad nill)
https://github.com/doximity/doximity/pull/10877

:+1:


PORTALS-2701: Refactor download confirmation in synapse-react-client

Depends on #346

DownloadConfirmation component was split into three components:

TableQueryDownloadConfirmation - business logic for adding a TableQuery to the download list
FolderDownloadConfirmation - business logic for adding a folder to the download list
DownloadConfirmationUI - view logic for the component used by the above

See diagram (aside: ERD semantics does not work very well for UI components)
erDiagram
    TableQueryDownloadConfirmation ||--|| DownloadConfirmationUI : contains
    FolderDownloadConfirmation ||--|| DownloadConfirmationUI : contains
    DownloadConfirmationUI ||--|| DownloadDetails : contains

This separation of concerns should make it easier to add table-specific row selection logic for adding to the DL list as needed in PORTALS-2701

nice mermaid diagram


Usdf rebase on lsst main

Here are changes to PR 1915 that don't break the installer. They were significant enough they were done in a separate branch rebased on lsst main. There are a few changes from the previous PR that I'm not confident how to perform. I'll point them out in comments.

Thanks for feedback, I added another commit making these changes.

Thanks! The semantics of the changes look good now, and I've enabled tests.  Follow the instructions here to set that up: https://phalanx.lsst.io/about/precommit-and-helm-docs.html
That will fix the whitespace directly but you'll need to investigate and fix the yamllint errors before we can merge.
Once that's done, rebase against the main branch and push again and we should be pretty much ready to merge.


[T4A6][W15-B2]Marcus Ng Wen Jian

Ready for review
References:

http://junit.sourceforge.net/doc/cookbook/cookbook.htm
http://junit.sourceforge.net/javadoc/org/junit/Assert.html

Don't forget method comments even though this is a test class!

Noted. With thanks.


Fix process loading stuck

This fixes http://b/182996343 by starting state_machine_ before registering the OnProcessListUpdate callback with process_manager_ (Only the "Fix ProfilingTargetDialog being stuck" is relevant. The other commits are just refactoring/renaming).
I am pretty sure this solved the problem, but it would be appreciated if someone could test this PR (@karupayun, the problem seems to occur often on your machine, maybe you can test it?)
This is a PR for main and I dont think it needs to be on release, since I dont think this is a regression, but I am happy to be convinced otherwise

Haven't looked at it yet. But I wanted to say I agree. This doesn't need to be in the release.

Trying this now.

Trying this now.

Seems to work. I can't reproduce the problem anymore! Thanks!

Okay, this sounds good!
There is another issue with switching between local and stadia that @reichlfl found (see http://b/182996343). I will address this in different PR.


fix anthropogenic total ERF

Accidently set the wrong index for reporting anthropogenic total ERF from FaIR.

[x] Description in CHANGELOG.rst added (single line such as: (`#XX <https://github.com/openscm/openscm-runner/pull/XX>`_) Added feature which does something)

possible nan in the anthropogenic. To check.

possible nan in the anthropogenic. To check.

 Problem summary is that Effective Radiative Forcing|Anthropogenic from FaIR was not reporting the right numbers.

OK ready. I can squash my last 7 commits where I'm arguing with a computer if you want.


[1.12.2-1.6.8] Server crash when right clicking 256k fluid blocks

Issue description:
Server crash when right clicking 256k fluid blocks
What happens:
Dedicated server crashes
What you expected to happen:
to not crash
Steps to reproduce:

place 256k fluid block
right click while holding any item
enjoy the dedicated server crash

Version (make sure you are on the latest version before reporting):

Minecraft: 1.12.2
Forge: <IP_ADDRESS>70
Refined Storage: 1.6.8

Does this issue occur on a server? [yes/no]
yes
If a (crash)log is relevant for this issue, link it here:
http://paste.ubuntu.com/p/45bnVDrg28/
http://paste.ubuntu.com/p/YZt6ZVjHvK/

That shouldn't be possible. Did you mess with your refinedstorage_nodes.dat file?

How are you placing the fluid storage block?

Can you reproduce this 100% of the time?

you would have to ask the FTB: Sky Adventures team if they modified that, because I did not touch it one bit.

and yes I was doing it 100% of the time, if you want to see it for yourself open up FTB: sky adventures latest version and enjoy crashing a dedicated server.

Can not confirm. Installed FTB Skyadventures and placed down a 256k Fluidstorage Block. Rightclicking it does not crash. Neither does powering it, inserting a fluid and then rightclicking.

Did you try running it as a server @Darkere  ?

This has been fixed in 5bc750812e210a3ad0faae893ab66cf3191e8bda


training

Code version (Git Hash) and PyTorch version
Dataset used
Expected behavior
Actual behavior
Steps to reproduce the behavior
Other comments

I trained with my own data (1920x1080), and how to set the resolution parameters of the json file generated by openpose. Frame_width, frame_height values is？
Def json_pack(snippets_dir, video_name, frame_width, frame_height, label='unknown', label_index=-1)
Looking forward to your help, thank you very much

Hi, just set frame_width=1920, frame_height=1080.

Hello, how to set the resolution of the json file generated by openpose。Does it affect the parameters of openpose. py. frame_width=1920，frame_height=1080
Thank you very much @yysijie

About 10 people in my test video, ran the original program, and the human skeleton （skeleton_result）and the human body（rgb_result） don't overlap.（attention+rgb video）
Do you know why? I tried to adjust the parameters but couldn't solve it. Like change def video_info_parsing(video_info, num_person_in=15, num_person_out=2):           Thanks

@liuk3615, hi you should keep the parameters of openpose.py the same as the resolution of your rgb videos.

"Attention + RGB" on video. The skeleton produces a great deal of fluidity and does not cover the human  in the image. Do you know why? Thanks very much. @yysijie

@liuk3615, hi, What is the format of the json you generated? What is the starting point for frame_index?

I used openpose for the default format. my video format 1920x1080. Shake hands for about three seconds.Don't understand the problem" the starting point for frame_index" @wwwpbai
Do you know how to solve this problem？ Thanks

if the resolution of all videos is not same, how should i set the parameters of height and width?  Thanks!

@Tylerjoe ,  that the resolution of all videos are not same is doesn't matter, you can see get_video_frame function[here] (https://github.com/yysijie/st-gcn/blob/master/tools/utils/video.py)

@wwwpbai Thanks for your reply and help, I will see the source code and check it

you can get your resolution (weight,height) by using
cap = cv2.VideoCapture('video.mp4')
ret, frame = cap.read()
imgSize = list(frame.shape)
outSize = imgSize[1::-1]
After that, you can use that outSize as a parameter in your json_pack.


Tranquillity

@MonkeyKiing25 First stage of verification passed, official domain is tranquillity.ee as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

Hi,
Thank you for your email.
Please let me know if you need more information.
Look forward to hearing from you!
On Thu, 20 Apr 2023 at 10:33 Philip Torchinsky @.***>
wrote:

@MonkeyKiing25 https://github.com/MonkeyKiing25 First stage of
verification passed, official domain is tranquillity.ee as far as I
verified. This is just an informational note. Pull request is still in the
review. I appreciate your patience while waiting for the final decision.
—
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/swot/pull/17306#issuecomment-1515664355,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQDAWSN3HZ4SJ36ZQD2GOFLXCCVABANCNFSM6AAAAAAXE3OQHM
.
You are receiving this because you were mentioned.Message ID:
@.***>

@MonkeyKiing25 Regrettably, this request has signs of fraud. I have to close it without merging.

Hi,
Why you told this is fraud without telling me any information?
On Wed, 26 Apr 2023 at 18:42 Philip Torchinsky @.***>
wrote:

Closed #17306 https://github.com/JetBrains/swot/pull/17306.
—
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/swot/pull/17306#event-9102570215, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AQDAWSISJ4LGP3FVPLLANATXDEC2XANCNFSM6AAAAAAXE3OQHM
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi,I am sorry, I cannot disclose what was specifically suspicious in your request due to security reasons.I did not say that your request was a fraud. I said the request had signs of fraud. It means, the request might be a fraud.Also, I recommend to apply for a license with documents that confirm your student or teacher status. It is to grant you the free license without adding the email domain to the trusted list.Thank you for your understanding!On 30. Apr 2023, at 6.11, Monkey King @.***> wrote:
Hi,
Why you told this is fraud without telling me any information?
On Wed, 26 Apr 2023 at 18:42 Philip Torchinsky @.***>
wrote:

Closed #17306 https://github.com/JetBrains/swot/pull/17306.
—
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/swot/pull/17306#event-9102570215, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AQDAWSISJ4LGP3FVPLLANATXDEC2XANCNFSM6AAAAAAXE3OQHM
.
You are receiving this because you were mentioned.Message ID:
@.***>

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: @.***>

Hi,
I dont know why this request was marked as a fraud. Do I need to use admin
account with domain name to request again?
Looking forward to hearing from you.
On Sun, 30 Apr 2023 at 14:30 Philip Torchinsky @.***>
wrote:

Hi,I am sorry, I cannot disclose what was specifically suspicious in your
request due to security reasons.I did not say that your request was a
fraud. I said the request had signs of fraud. It means, the request might
be a fraud.Also, I recommend to apply for a license with documents that
confirm your student or teacher status. It is to grant you the free license
without adding the email domain to the trusted list.Thank you for your
understanding!On 30. Apr 2023, at 6.11, Monkey King @.***> wrote:
Hi,
Why you told this is fraud without telling me any information?
On Wed, 26 Apr 2023 at 18:42 Philip Torchinsky @.***>
wrote:

Closed #17306 https://github.com/JetBrains/swot/pull/17306.
—
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/swot/pull/17306#event-9102570215, or
unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AQDAWSISJ4LGP3FVPLLANATXDEC2XANCNFSM6AAAAAAXE3OQHM
.
You are receiving this because you were mentioned.Message ID:
@.***>

—Reply to this email directly, view it on GitHub, or unsubscribe.You are
receiving this because you modified the open/close state.Message ID:
@.***>
—
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/swot/pull/17306#issuecomment-1528959523,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQDAWSI5KH2RQIALUITXKX3XDYIJVANCNFSM6AAAAAAXE3OQHM
.
You are receiving this because you were mentioned.Message ID:
@.***>


i wrote a hound search plugin for hain

check out this project:https://github.com/appetizermonster/hain
it's kind of like a spotlight search with tons of plugins.
i wrote a hound plugin to allow us to quickly search for code
https://github.com/talarari/hain-plugin-hound
you're welcome to install it from hain's package manager to check it out.
looks kind of like this:
.

This is awesome! Closing this issues since it's not actually an issue :)


Add back convertion to float for Matrix Indices

We believe this change was made by accident. Babylon Native currently needs matrix index buffers to be converted to float in the JS side.

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/14758/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14758/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14758/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/14758/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/14758/merge
https://gui.babylonjs.com/?snapshot=refs/pull/14758/merge
https://nme.babylonjs.com/?snapshot=refs/pull/14758/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/14758/merge#BCU1XR#0

Possibly yes, but our conclusion was that this line was changed by mistake in a previews PR.

Are you sure it was not for perf ? cc @Popov72 just in case ?

I made this change accidentally.

Matrix indices buffers don't have a type in the glTF file (as other types of vertex buffers have a type)? In that case, I guess we should create the vertex buffer according to this type?

Matrix indices buffers don't have a type in the glTF file (as other types of vertex buffers have a type)? In that case, I guess we should create the vertex buffer according to this type?

I'm not sure what you mean by this. What do you mean by type? Maybe the following statement will help? Babylon matrix indices is equivalent to glTF joints.

By type, I mean int16, int32, float, etc. Positions, normals, etc don't have to be float in a glTF file, they can have another type. So I guess it's the same thing for the joint indices? Or does the spec mandate a specific type (but float would be a bit strange, I would think that int16/int32 would be more appropriate for joint indices)?

By type, I mean int16, int32, float, etc. Positions, normals, etc don't have to be float in a glTF file, they can have another type. So I guess it's the same thing for the joint indices? Or does the spec mandate a specific type (but float would be a bit strange, I would think that int16/int32 would be more appropriate for joint indices)?

@Popov72 , I think the glTF 2.0 specification states that position, normals, and tangents must be float:
https://registry.khronos.org/glTF/specs/2.0/glTF-2.0.html
And joint indexes must be unsigned short:

By type, I mean int16, int32, float, etc. Positions, normals, etc don't have to be float in a glTF file, they can have another type. So I guess it's the same thing for the joint indices? Or does the spec mandate a specific type (but float would be a bit strange, I would think that int16/int32 would be more appropriate for joint indices)?

The type conversion to float is just for the shader since webgl does not support integer attributes.

WebGL2 supports integer attributes:
https://developer.mozilla.org/en-US/docs/Web/API/WebGL2RenderingContext/vertexAttribIPointer
But I understand it's required because our shaders take a vec4 for the indices.


Create zh_tw

@eric122805 hey, do you use google translate to do this work?
I see there has some word that is not really traditional chinese use.

Reverted in #553 due to additional proof of being machine-translated.


Fix query subscriptions not emitting data

Fix query subscriptions not emitting data in various cases.
There are some issues with OperationExecutor that cause query subscriptions to not return any data.

After performing the network request, the observer is always completed. This is correct for subscriptions, but should not be done for queries, as it will prevent them from receiving updates from the entity store.
Subsequent executions of a query with the NetworkOnly strategy will not emit any results if the data does not change between requests. This is due to the entity store internally skipping the update notification for duplicate results.

This PR modifies the executor's logic to instead send results directly to the observer, while still avoiding duplicate messages in the case of CacheAndNetwork and Subscription requests. The entity store subscription is always subscribed to in all query strategies, and the observable is never completed for queries.
The completion logic was moved from the finally into the end of the try, since the observable contract states that only one of OnError and OnCompleted should be called, not both. Previously an exception would have caused both to be called.
Closes #5704

 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.Kevin Boyles 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.

Thank you for contributing ... give us a ping once you want a review.

@michaelstaib I couldn't find tests for this file, so I added a bunch of cases that should cover everything related to queries. Ready for review now

@Sibusten I will have a look at it. Thank you for contributing!

/azp run


Auto-Update LiveSplit Components

Maybe need a new component (LiveSplit.LCGoLSplitter.Manager) that will download, then load the dlls for injection as I believe LiveSplit only auto-updates 1 dll. It's possible that the LCGoLSplitterFactory may be able to do this without a new component. Should look into that.

This may also fix or relate to #3


VoIP Test call with IMS

Please suggest the procedure to make voice call through kamailio - IMS | SIPP | SoftPhone. Need to check the vIMS (PCSCF | SCSCF | ICSCF | smsc | physs)

Refer to below step in this tutorial https://open5gs.org/open5gs/docs/tutorial/02-VoLTE-setup/

A quick check for the basic working of SIP server can be done as follows:

Want to go with Simulator VoIP call test(i.e.  SiPp & softphone tool). If you could suggest. The procedures any reference link.

Sorry, I cant be of help there since I haven't used either of them.


BF/ENH: Make _read_elp_besa() respect fiducial points

What does this implement/fix?
I had trouble reading a BESA spherical elp file using channels.read_custom_montage(), as the fiducials were treated as sensor channels. This PR adds special handling for the fiducials.

Can you please add a test ? Thx @hoechenberger

@agramfort Done

Yes the column is currently ignored. I was thinking about making use of it too, but then wondered if it would even make sense since we‘d still have to identify the fiducials via their respective names anyway. I do have an elp file here but don’t remember where I got it from... probably EEGLAB? Can share later today
--
Sent from my phone, please excuse brevity and erroneous auto-correct.

On 21. Dec 2019, at 13:00, Alexandre Gramfort<EMAIL_ADDRESS>wrote:

@agramfort commented on this pull request.
In mne/channels/tests/test_montage.py:

@@ -240,18 +240,23 @@ def test_documented():
pytest.param(
partial(read_custom_montage, head_size=None, unit='n/a'),
('346\n'  # XXX: this should actually race an error 346 != 4

    'EEG\t      F3\t -62.027\t -50.053\t      85\n'

    'EEG\t      Fz\t  45.608\t      90\t      85\n'

    'EEG\t      F4\t   62.01\t  50.103\t      85\n'

    'EEG\t      FCz\t   68.01\t  58.103\t      85\n'),

    'FID\t      LPA\t -120.03\t      0\t      85\n'

    'FID\t      RPA\t  120.03\t      0\t      85\n'

    'FID\t      Nz\t   114.03\t     90\t      85\n'

I see that you have this first column that tells you the channel type. Do we ignore it so far because we only had EEG? do you have a public file that contains this FID?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

ok let's move on. Thx @hoechenberger


✨Introduce ReconcileError with Transient and Terminal Error type

This PR:

Introduces ReconcileError with Transient and Terminal Error type
Removes RequeueAfterError (as it was depricated in CAPI)
Removes repetitive error setting on m3Machine status Fixes #705

ReconcileError represents an generic error of Reconcile loop.  errorType indicates what type of action is required to recover. It can take two values:
a. Transient - Can be recovered , will be requeued after.
b. Terminal - Cannot be recovered, will not be requeued.
When error is not ReconcileError it will be returned to Reconciler.

/test-ubuntu-integration-main

/test-centos-e2e-integration-main
/test-ubuntu-integration-main

/test-centos-e2e-integration-main
/test-ubuntu-integration-main

/test-ubuntu-integration-main
/test-centos-e2e-integration-main

/test-ubuntu-integration-main
/test-centos-e2e-integration-main

/keep-test-centos-e2e-integration-main

/test-ubuntu-integration-main

/assign @kashifest

/test-ubuntu-integration-main/

/test-ubuntu-integration-main

test-centos-e2e-integration-main

/test-centos-e2e-integration-main

/test-centos-e2e-integration-main

/test-ubuntu-e2e-integration-main
/test-centos-e2e-integration-main
/test-e2e-upgrade-main

/test-ubuntu-e2e-feature-main
/test-centos-e2e-feature-main

/test-centos-integration-main

/test-centos-e2e-feature-main

/retest

/approve

/test-e2e-upgrade-main-from-release-1-1
/test-centos-e2e-integration-main

/cherry-pick release-1.4


Clear button does not trigger (onRemove) event

When "Clear" button is pressed (onRemove) event does not get triggered. So, uploaded images does not get deleted.
Current code seen in my project:

Should be like:

Important: I have installed ng2-image-upload through the following command:

npm install angular2-image-upload --save

However, the codes of ng2-image-upload which is in my project now seems slightly different from the original code in github.
e.g. The event (removed) in github corresponds as (onRemove) event in my project.

We currently have an issue with the wrong readme being displayed on github.
Our default branch is development, whereas the latest release is on master, by default the repo will show you the development readme, which is unreleased - #104
This issue was fixed in 0.6.5, but it would appear we've had an issue publishing it.
@aberezkin I think it's probably worth grabbing the 0.6.5 tag, manually bumping the version to 0.6.6 and releasing again.

Done


Add realtime-core

Summary
This PR adds realtime-core. This is the first PR in attempt to separate the core functionality into a separate package.
Changes
realtime-core contains the following classes and functions:

RealtimeConnection: A class that establishes and maintains realtime connection.
RealtimeConnectionNegotiator: A class that negotiates connection.
RealtimeConnecitonMediaManager: A class that manages all realtime connection media (local as well as remote).
SDP: A class to process/modify sdp.
ConsoleLogger: A class that can be used as logger. It will log everthing in the console.
Logger: Base logger class.
Some utils functions like retry fetch on fail, and function to validate the type of an unknown object.
Refactor the components that are using realtime connection. Haven't updated them much.

Testing
Tested the app locally and successfully ran both the cooking assistant and the voice bot. However, the connection was somewhat unstable, due to:

The browser says CORS issues but, in the response, it says Internal server error.
the chatbot disconnecting from the server after a few minutes due to some unknown reason. When connected to the cooking assistant backend, I didn't encounter any disconnecting issue, but experience CORS/Internal Server issue.

Note
In the next PR, I'll separate the React-related components and hooks into realtime-react. I'm certain we'll encounter a few bugs and some missing functionalities during that process, but we can address those as they arise.

Please add comments and more detailed explanations in RealtimeConnection/MediaManager/Negotiator.
I can handle the comments for SDP.ts.


[Feature] Cloud Zone destroy and deleted Citrix Cloud Connector

Thanks for taking the time to fill out this feature request! Before submitting this issue please check the open feature requests to ensure the feature has not already been reported. If it has been reported give it a 👍
Describe the feature request
Fill out the following questions and add any additional information.
Summary:
Hello,
We are creating a new Citrix environment in Azure via a GitLab pipeline with all components (Cloud Connector, VDA using Terraform). As part of the CI/CD process, we need to repeatedly redeploy the entire Terraform setup and then completely delete it.
We have noticed that when performing a Terraform destroy on the Citrix zone, we encounter an error.
Error: Error deleting resource location with id: ffa7e978-b72a-4897-8d42-57e3647a296b
/-/jobs/3373164#L205)│ TransactionId: f01cf1bd-139c-4bb5-8e37-195577229039
/-/jobs/3373164#L206)│ Error message: 400 Bad Request
The reason is that the deleted Citrix Cloud Connector still remains in the zone. This causes additional effort, as we have to manually uninstall and maintain the Citrix Cloud Connector.
Could you please check internally whether it is possible to call an API during the Terraform destroy of the zone that ensures the Cloud Connector is automatically deleted as well? When someone destroys the zone, they understand the implications, and I see no risk in also removing the Cloud Connector. If I manually remove the deleted Cloud Connector from the Citrix plan, the destroy process works without any issues.
If you have any further questions or need more details, please let me know.
Is this an enhancement to an existing resource or data source, if so which one?
Exmaple for Cloud Zone
resource "citrix_cloud_resource_location" "example-resource-location" {
name = "example-resource-location"
}
resource "citrix_zone" "example-cloud-zone" {
resource_location_id = citrix_cloud_resource_location.example-resource-location.id
}
If this is a new resource or data source describe what it should do.
Link to any docs that cover this feature:
https://docs.citrix.com/
Link to any APIs that cover this feature:
https://developer-docs.citrix.com/

@AlanCitrix Thank you for the very interesting idea 👍 with the variable "CITRIX_CLOUD_RESOURCE_LOCATION_FORCE_DELETE," and we will definitely adopt it. 💯

Great. The delete Connectors API is not public so we will put this on our roadmap and try to get it prioritized.
In the meantime if you are able to automate the Connector uninstallation, or just leave the resource location unmanaged by Terraform and reuse it between runs, that could be a workaround.