tensorflow2.1 can not initialize colab TPU

if '2.1' in tf.__version__:
    if 'COLAB_TPU_ADDR' in os.environ:
        resolver = tf.distribute.cluster_resolver.TPUClusterResolver(tpu='grpc://' + os.environ['COLAB_TPU_ADDR'])
        tf.config.experimental_connect_to_cluster(resolver)
        tf.tpu.experimental.initialize_tpu_system(resolver)
        strategy = tf.distribute.experimental.TPUStrategy(resolver)
        print('Running on TPU ', resolver.cluster_spec().as_dict())

NotFoundError                             Traceback (most recent call last)
 in ()
160             resolver = tf.distribute.cluster_resolver.TPUClusterResolver(tpu='grpc://' + os.environ['COLAB_TPU_ADDR'])
161             tf.config.experimental_connect_to_cluster(resolver)
--> 162             tf.tpu.experimental.initialize_tpu_system(resolver)
163             strategy = tf.distribute.experimental.TPUStrategy(resolver)
164             print('Running on TPU ', resolver.cluster_spec().as_dict())
3 frames
/usr/local/lib/python3.6/dist-packages/six.py in raise_from(value, from_value)
NotFoundError: '__inference__tpu_init_fn_4' is neither a type of a primitive operation nor a name of a function registered in binary running on n-3ea5ef93-w-0. Make sure the operation or function is registered in the binary running in this process.

tensorflow-gpu-2.1 has this problem ,and tensorflow-2.1 is fine.

I tried installing using pip install tensorflow==2.1, but I still get nearly the same error:
NotFoundError                             Traceback (most recent call last)
<ipython-input-5-0a40fe7e3383> in <module>
      8     resolver = tf.distribute.cluster_resolver.TPUClusterResolver(TPU_ADDRESS)
      9     tf.config.experimental_connect_to_cluster(resolver)
---> 10     tf.tpu.experimental.initialize_tpu_system(resolver)
     11     strategy = tf.distribute.experimental.TPUStrategy(resolver)

~/.local/lib/python3.5/site-packages/tensorflow_core/python/tpu/tpu_strategy_util.py in initialize_tpu_system(cluster_resolver)
    101     context.context()._clear_caches()  # pylint: disable=protected-access
    102
--> 103     serialized_topology = output.numpy()
    104
    105     # TODO(b/134094971): Remove this when lazy tensor copy in multi-device

~/.local/lib/python3.5/site-packages/tensorflow_core/python/framework/ops.py in numpy(self)
    940     """
    941     # TODO(slebedev): Consider avoiding a copy for non-CPU or remote tensors.
--> 942     maybe_arr = self._numpy()  # pylint: disable=protected-access
    943     return maybe_arr.copy() if isinstance(maybe_arr, np.ndarray) else maybe_arr
    944

~/.local/lib/python3.5/site-packages/tensorflow_core/python/framework/ops.py in _numpy(self)
    908       return self._numpy_internal()
    909     except core._NotOkStatusException as e:
--> 910       six.raise_from(core._status_to_exception(e.code, e.message), None)
    911
    912   @property

/usr/local/lib/python3.5/dist-packages/six.py in raise_from(value, from_value)

NotFoundError: '__inference__tpu_init_fn_4' is neither a type of a primitive operation nor a name of a function registered in binary running on n-9a4d14b8-w-0. Make sure the operation or function is registered in the binary running in this process.

Strangely though, when I test for GPU support using tf.test.is_built_with_gpu_support() it returns True, so perhaps that's the issue. When I check tf.__version__ and tf.version.GIT_VERSION I get 2.1.0 and v2.1.0-rc2-17-ge5bf8de respectively.

@ofpppppppdbfjs ,
Can you share code to reproduce the issue?Thanks!

@ofpppppppdbfjs ,
Can you share code to reproduce the issue?Thanks!

i do not know how to share .ipynb file,   so put the code here i reproduced
%tensorflow_version 2.x
import tensorflow as tf
resolver = tf.distribute.cluster_resolver.TPUClusterResolver(tpu='grpc://' + os.environ['COLAB_TPU_ADDR'])
tf.config.experimental_connect_to_cluster(resolver)
strategy = tf.distribute.experimental.TPUStrategy(resolver)

Update:
Even when using tensorflow==2.1 and tf.test.is_built_with_gpu_support() returning False I still get the same error.
I tried installing using pip install tensorflow==2.1, but I still get nearly the same error:
NotFoundError                             Traceback (most recent call last)
<ipython-input-5-0a40fe7e3383> in <module>
      8     resolver = tf.distribute.cluster_resolver.TPUClusterResolver(TPU_ADDRESS)
      9     tf.config.experimental_connect_to_cluster(resolver)
---> 10     tf.tpu.experimental.initialize_tpu_system(resolver)
     11     strategy = tf.distribute.experimental.TPUStrategy(resolver)

~/.local/lib/python3.5/site-packages/tensorflow_core/python/tpu/tpu_strategy_util.py in initialize_tpu_system(cluster_resolver)
    101     context.context()._clear_caches()  # pylint: disable=protected-access
    102
--> 103     serialized_topology = output.numpy()
    104
    105     # TODO(b/134094971): Remove this when lazy tensor copy in multi-device

~/.local/lib/python3.5/site-packages/tensorflow_core/python/framework/ops.py in numpy(self)
    940     """
    941     # TODO(slebedev): Consider avoiding a copy for non-CPU or remote tensors.
--> 942     maybe_arr = self._numpy()  # pylint: disable=protected-access
    943     return maybe_arr.copy() if isinstance(maybe_arr, np.ndarray) else maybe_arr
    944

~/.local/lib/python3.5/site-packages/tensorflow_core/python/framework/ops.py in _numpy(self)
    908       return self._numpy_internal()
    909     except core._NotOkStatusException as e:
--> 910       six.raise_from(core._status_to_exception(e.code, e.message), None)
    911
    912   @property

/usr/local/lib/python3.5/dist-packages/six.py in raise_from(value, from_value)

NotFoundError: '__inference__tpu_init_fn_4' is neither a type of a primitive operation nor a name of a function registered in binary running on n-9a4d14b8-w-0. Make sure the operation or function is registered in the binary running in this process.

Strangely though, when I test for GPU support using tf.test.is_built_with_gpu_support() it returns True, so perhaps that's the issue. When I check tf.__version__ and tf.version.GIT_VERSION I get 2.1.0 and v2.1.0-rc2-17-ge5bf8de respectively.

use
%tensorflow_version 2.x

@ofpppppppdbfjs thanks, I had figured out how to specify the correct TensorFlow version, but I still get the same error.
@oanush
I'm using Colab connected to Google Cloud CPU &B TPU instances running:
Python:
3.5.3 (default, Sep 27 2018, 17:25:39)
[GCC 6.3.0 20170516]
TensorFlow:
2.1.0
v2.1.0-rc2-17-ge5bf8de
GPU Support: False
I still get the same error:
NotFoundError                             Traceback (most recent call last)
<ipython-input-6-c84946626dc0> in <module>
     11     except tf.errors.UnimplementedError as uie:
     12         print(uie, "This appears to be caused by the TPU already being connected. Ignoring.", sep='\n')
---> 13     tf.tpu.experimental.initialize_tpu_system(resolver)
     14     tpu_strategy = tf.distribute.experimental.TPUStrategy(resolver)

3 frames
/usr/local/lib/python3.5/dist-packages/six.py in raise_from(value, from_value)

NotFoundError: '__inference__tpu_init_fn_4' is neither a type of a primitive operation nor a name of a function registered in binary running on n-80f5d4ef-w-0. Make sure the operation or function is registered in the binary running in this process.

Here is the code I can use to reproduce:
import tensorflow as tf

TPU_ADDRESS = "grpc://" + "<IP_ADDRESS>:8470"
resolver = tf.distribute.cluster_resolver.TPUClusterResolver(TPU_ADDRESS)
tf.config.experimental_connect_to_cluster(resolver)
tf.tpu.experimental.initialize_tpu_system(resolver)
tpu_strategy = tf.distribute.experimental.TPUStrategy(resolver)

Which is exactly what the documentation says to do here: https://www.tensorflow.org/api_docs/python/tf/distribute/experimental/TPUStrategy?version=stable


Couldn't recognize device - com.fibaro.multilevelSwitch - com.fibaro.dimmer

I noticed the dimmers do not get recognized anymore.
"Couldn't recognize device #968 - com.fibaro.multilevelSwitch - com.fibaro.dimmer"
No idea since when, but i'm pretty sure it was working 2 days ago.
For safety i copied again all the original files, still the same.

Are you sure it worked before? It would be great to learn using what QuickApp version.
There is a chance it is not a QuickApp defect, but Fibaro HC3 changed the way device type is named.

Hmm i'm sure it worked.  And yes, maybe Fibaro changed something in the last FW.
This is one the dimmers in swagger:
{   "id": 968,   "name": "LightsHolGaraj",   "roomID": 226,   "view": [     {       "assetsPath": "dynamic-plugins/com.fibaro.multilevelSwitch",       "name": "com.fibaro.multilevelSwitch",       "translatesPath": "/assets/i18n/com.fibaro.multilevelSwitch",       "type": "ts"     },     {       "assetsPath": "dynamic-plugins/energy",       "name": "energy",       "translatesPath": "/assets/i18n/energy",       "type": "ts"     },     {       "assetsPath": "",       "name": "level-change",       "translatesPath": "/assets/i18n/level-change",       "type": "ts"     },     {       "assetsPath": "dynamic-plugins/power",       "name": "power",       "translatesPath": "/assets/i18n/power",       "type": "ts"     }   ],   "type": "com.fibaro.FGD212",   "baseType": "com.fibaro.multilevelSwitch",   "enabled": true,   "visible": true,   "isPlugin": false,   "parentId": 965,   "viewXml": false,   "hasUIView": true,   "configXml": false,   "interfaces": [     "energy",     "levelChange",     "light",     "power",     "zwave",     "zwaveAlarm",     "zwaveMultiChannelAssociation",     "zwaveProtection",     "zwaveSceneActivation"   ],   "properties": {     "parameters": [       {         "id": 1,         "lastReportedValue": 1,         "lastSetValue": 1,         "size": 1,         "value": 1       },       {         "id": 2,         "lastReportedValue": 30,         "lastSetValue": 30,         "size": 1,         "value": 30       },       {         "id": 3,         "lastReportedValue": 99,         "lastSetValue": 99,         "size": 1,         "value": 99       },       {         "id": 4,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 2,         "value": 0       },       {         "id": 5,         "lastReportedValue": 99,         "lastSetValue": 99,         "size": 1,         "value": 99       },       {         "id": 6,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 2,         "value": 0       },       {         "id": 7,         "lastReportedValue": 99,         "lastSetValue": 99,         "size": 1,         "value": 99       },       {         "id": 8,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 2,         "value": 0       },       {         "id": 9,         "lastReportedValue": 1,         "lastSetValue": 1,         "size": 1,         "value": 1       },       {         "id": 10,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 2,         "value": 0       },       {         "id": 11,         "lastReportedValue": 255,         "lastSetValue": 255,         "size": 2,         "value": 255       },       {         "id": 13,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 1,         "value": 0       },       {         "id": 14,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 1,         "value": 0       },       {         "id": 15,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 1,         "value": 0       },       {         "id": 16,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 2,         "value": 0       },       {         "id": 19,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 1,         "value": 0       },       {         "id": 20,         "lastReportedValue": 1,         "lastSetValue": 1,         "size": 1,         "value": 1       },       {         "id": 21,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 1,         "value": 0       },       {         "id": 22,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 1,         "value": 0       },       {         "id": 23,         "lastReportedValue": 1,         "lastSetValue": 1,         "size": 1,         "value": 1       },       {         "id": 24,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 1,         "value": 0       },       {         "id": 25,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 1,         "value": 0       },       {         "id": 26,         "lastReportedValue": 1,         "lastSetValue": 1,         "size": 1,         "value": 1       },       {         "id": 27,         "lastReportedValue": 15,         "lastSetValue": 15,         "size": 1,         "value": 15       },       {         "id": 28,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 1,         "value": 0       },       {         "id": 29,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 1,         "value": 0       },       {         "id": 30,         "lastReportedValue": 2,         "lastSetValue": 2,         "size": 1,         "value": 2       },       {         "id": 31,         "lastReportedValue": 1,         "lastSetValue": 1,         "size": 1,         "value": 1       },       {         "id": 32,         "lastReportedValue": 1,         "lastSetValue": 1,         "size": 1,         "value": 1       },       {         "id": 33,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 1,         "value": 0       },       {         "id": 34,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 1,         "value": 0       },       {         "id": 35,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 1,         "value": 0       },       {         "id": 37,         "lastReportedValue": 1,         "lastSetValue": 1,         "size": 1,         "value": 1       },       {         "id": 39,         "lastReportedValue": 250,         "lastSetValue": 250,         "size": 2,         "value": 250       },       {         "id": 40,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 1,         "value": 0       },       {         "id": 41,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 1,         "value": 0       },       {         "id": 42,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 1,         "value": 0       },       {         "id": 43,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 1,         "value": 0       },       {         "id": 44,         "lastReportedValue": 600,         "lastSetValue": 600,         "size": 2,         "value": 600       },       {         "id": 45,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 1,         "value": 0       },       {         "id": 46,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 1,         "value": 0       },       {         "id": 47,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 1,         "value": 0       },       {         "id": 48,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 1,         "value": 0       },       {         "id": 49,         "lastReportedValue": 1,         "lastSetValue": 1,         "size": 1,         "value": 1       },       {         "id": 50,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 1,         "value": 0       },       {         "id": 52,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 2,         "value": 0       },       {         "id": 53,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 2,         "value": 0       },       {         "id": 54,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 1,         "value": 0       },       {         "id": 58,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 1,         "value": 0       },       {         "id": 59,         "lastReportedValue": 0,         "lastSetValue": 0,         "size": 2,         "value": 0       }     ],     "pollingTimeSec": 0,     "zwaveCompany": "Fibargroup",     "zwaveInfo": "3,4,5",     "zwaveVersion": "3.5",     "RFProtectionState": 0,     "RFProtectionSupport": 3,     "alarmLevel": 0,     "alarmType": 0,     "categories": [       "lights"     ],     "configured": true,     "dead": false,     "deadReason": "",     "deviceControlType": 2,     "deviceIcon": 15,     "deviceRole": "Light",     "emailNotificationID": 0,     "emailNotificationType": 0,     "endPointId": 1,     "energy": 31.16,     "icon": {       "path": "/assets/icon/fibaro/light/light0.png",       "source": "HC"     },     "isLight": true,     "localProtectionState": 0,     "localProtectionSupport": 5,     "log": "",     "logTemp": "",     "manufacturer": "",     "markAsDead": true,     "model": "",     "nodeId": 207,     "parametersTemplate": "740",     "power": 0,     "productInfo": "1,15,1,2,16,0,3,5",     "protectionExclusiveControl": 0,     "protectionExclusiveControlSupport": false,     "protectionState": 0,     "protectionTimeout": 0,     "protectionTimeoutSupport": false,     "pushNotificationID": 0,     "pushNotificationType": 0,     "saveLogs": true,     "saveToEnergyPanel": true,     "sceneActivation": 0,     "serialNumber": "h'0000000000006c3a",     "showEnergy": true,     "smsNotificationID": 0,     "smsNotificationType": 0,     "state": false,     "storeEnergyData": true,     "supportedDeviceRoles": [       "Light"     ],     "useTemplate": true,     "userDescription": "",     "value": 0   },   "actions": {     "reconfigure": 0,     "reset": 0,     "sceneActivationSet": 0,     "setValue": 1,     "startLevelDecrease": 0,     "startLevelIncrease": 0,     "stopLevelChange": 0,     "toggle": 0,     "turnOff": 0,     "turnOn": 0   },   "created":<PHONE_NUMBER>,   "modified":<PHONE_NUMBER>,   "sortOrder": 17 }

Most likely Fibaro firmware, and it looks like I need to add more sophisticated device detection rules with wildcards, but it takes time and I wish there was more time during weekends (((

By the way - do you need all the feature requests for yourself?
I guess it would be simpler if it was for commercial use $, the we could get it sponsored byyour clients (if any) - and thus we all invest to add more capabilities to QuickApp

I could try and help if you can tell me where i have to modify.  It would be good to have the typem basetype and overrites somewhere they could be easily modified so we do not bother you all the time.  Just log in swagger , look at the json and input the new type / basetype in the respective fields in the QA code.
Or am i over simplifying things ?!

unfortunatelly i need for myself only.  But maybe if at some point it becomes very reliable, $ can be made.
I'm using HA for mobile/tablet interface between FIbaro and various other systems i have,

One idea about making some $ would be to make it v. v. . good:) then encrypt it - as it is possible to do now. But first it needs rock solid and fast/ packed with features.

@alexander-vitishchenko
So any idea how to fix the dimmers please ?

Same problem here, after last update of the QA the dimmers are not there anymore. So I think something has changed in the QA itself in the last versions.
Couldn't recognize device #116 - 8 Spots - com.fibaro.multilevelSwitch - com.fibaro.dimmer

cheers :)

Hi @MomosX , @rwijbenga,

I've tested the device from above "id": 968, "name": "LightsHolGaraj" => it appears to be fully functional dimmer:

I used the exactly device JSON that I got from you
You can check it by yourself by adding "developmentMode" variable and setting its value to "true"

I've redeployed the latest version of the QuickApp, can you please recheck if the issue persist?

I'm using GitHub release/tag feature to do version control for the QuickApp, see at https://github.com/alexander-vitishchenko/hc3-to-mqtt/releases. It is currently used for major releases, e.g. once per quarter.

Thank you,
Alexander

I copied again all the files. After that i deleted and reinstalled the QA.
Result:

By the way : as an addition, the code posted by someone here works for Fibaro FGT001 and for Danfoss Room thermostats.
function Thermostat.isSupported(fibaroDevice)     if (fibaroDevice.type == "com.fibaro.hvacSystem" or fibaroDevice.type == "com.fibaro.FGT001" or fibaroDevice.type == "com.fibaro.thermostatDanfoss") then           return true      else          return false     end end
But it is not included in the QA yet.  This solves the thermostats part.
For dimmers no idea why it still doesn't work.

Same here with the lastest version, dimmers are not recognized anymore...

So i found out what the problem is: thee is no "light" interface in those dimmers json.
Adjusted the code like this:
function Dimmer.isSupported(fibaroDevice)   --  if fibaroDeviceHasType(fibaroDevice, "com.fibaro.multilevelSwitch") and fibaroDeviceHasInterface(fibaroDevice, "light") then     if fibaroDeviceHasType(fibaroDevice, "com.fibaro.dimmer") then         return true     else          return false     end end
And it works !!!

In fact i think there is a deeper issue here:  all the devices that have the interface "light" should be imported in HA as lights.  But they are not, they are imported as switches.
Taking out the "light" interface check from those dimmers for example made them show in HA as lights .
Which way should be correct ?

Also i think this goes even deeper as i see in main.lua lines 244 to 258 that the QA is supposed to create HA devices for battery level, but it does not.   table_contains_value(fibaroDevice.interfaces, "battery")
This points back to the table reading as it seems none of the interfaces gets read properly.
@alexander-vitishchenko   am i reading the code right or ?!

Sooo, in device_api.lua line 499 where the QA defines what device attributes is looking for:
            attributes = {
                -- define the list of Fibaro device attributes we are interested in
                main = {
-- changed from "interface" to "interfaces"                    "id", "name", "roomID", "view", "type", "baseType", "enabled", "visible", "isPlugin", "parentId", "viewXml", "hasUIView", "configXml", "interface", "properties", "actions", "created", "modified", "sortOrder"
                    "id", "name", "roomID", "view", "type", "baseType", "enabled", "visible", "isPlugin", "parentId", "viewXml", "hasUIView", "configXml", "interfaces", "properties", "actions", "created", "modified", "sortOrder"

interface was missing an "s" .   Modified it and it seems all interfaces are working now, HA even has power/batery sensors.
@alexander-vitishchenko  can you please check all this if i'm correct or not ?
Thank you !

@MomosX, @rwijbenga

That's right - fixed.

The wrong attribute name was caused by the inconsistency with my development environments at the home lab, resulting me into looking at the functional code, while publishing the wrong one to GitHub, i.e. human factor.

The human factor clearly need to be addresses. QuickApp is growing and new features may break the existing functionality, where dimmer's issue is just one of such examples:

I've reduced the development environments to a single instance at the home lab, so there is a less chance for me to make a mistake because of unnecessary complexity (by the cost of removing branching flexibility for my dev env, but I guess stability is more important)
I've automated the majority of the Fibaro HC3 -> GitHub deployment with Microsoft Power Automate. Now it take me 10 seconds to get ready for commit, and there smaller chance to make a mistake while executing executing repeatative steps over several minutes manually

Plus, what need to do - invest into setting up an Automated Regression Test framework for the QuickApp, at least on the "Smoke Testing" level. Not an easy thing to do with lua and Fibaro ecosystem, but something what I think should avoid breaking core functionality in a future.

Once development environment is enabled with a higher quality code for the QuickApp - I should be able to add new features without a significant risk of breaking an existing functionality. Hope to get it done within a week.

@alexander-vitishchenko you are doing a great job and i'm sure all who use this QA appreciate it.
Human factor is something i know very well ... happens.
So now you included the "interfaces" fix and the thermostats in the QA ?  the thermostat i posted above also.  And we can close the Danfoss RS, Fibaro FGT and Danfoss TRV issues as solved

The fix applies to all devices that rely on "interfaces" for their type identification. So the fix applies to dimmers and other devices that work before.
Worth mentioning - the QuickApp had and still has limited support for thermostats overall. I plan to add better support for thermostats once stability improvements are implemented with the Regression/Smoke Testing framework.


[feature]: Adding Pagination

Is there an existing feature request for this?

[X] I have searched the existing issues

Summary
Add Pagination to the following for performance optimisation :

[ ]  To /testlist app names list
[ ]  To /testlist testcases list represented in the table
[ ]  To /testruns cards list rendered
[ ]  To /testrun/testid table of test cases listed
[ ]  To /testrun/testid unique URI list on the left tab pannel

Why should this be worked on?
This will enhance the performance of the page due data fetched and rendered.

 To /testlist app names list
@nehagup Currently app names are returned in entirety, so incase pagination is required here. Change of  UI component might be required.

@anirudhjain75 For now we're planning to bring in all the app names list and then for each app details there's a seperate query done.


Feature/utf8 path

Now all filepath that tinygltf API use will be utf8 encoded std::string
On Windows, those string will be convertd to wstring before used on file operation
On Linux, it is utf8 by default and nothing changed
Based on gltf 2.0 spec, all path of resources described in gltf will also be utf8 string
This merge also make any internal resource finding support utf8 path
On user side, make sure to convert any local filepath to utf8 encoded string(highly recommanded with filesystem::path::u8string() )

Awesome! Merged!


Respect Sender Recovery prune part in the pipeline

Describe the feature
We need to start writing tables related to the Sender Recovery prune part during the initial sync only when the pruning target is reached:

SenderRecoveryStage writes to the TxSenders table
ExecutionStage uses senders recovered in SenderRecoveryStage. The fetching of BlockWithSenders will fail if we try to sync a full node with pruned senders, so we need to dynamically recalculate the sender if it's missing.

Additional context
No response

We don't want to prune senders during the initial pipeline, as it will slow down the Execution stage significantly. Instead, we will prune senders in the pruner during the blockchain tree sync https://github.com/paradigmxyz/reth/issues/3695, which will prune all senders on its first run.


Cannot find module 'availability-monitor' or its corresponding type declarations.ts(2307)

I tried installing this with yarn (v1.22.18) in my TypeScript project, but when I try importing the module I get an error saying the module can't be found.

Hi, Sorry for the long wait. Should be fixed with 'v1.1.4' now.


flipped version

@sjolicoeur do you know how to run the tests? want to make sure they still work.

All working for me. :+1:


fix: Provide virtctl binary for kubevirtci

What this PR does / why we need it:
kubevirtci does not ship its own virtctl binary which is needed for the functional tests. Fix it by downloading the latest virtctl release binary during setup of the kubevirtci cluster.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

None

Thanks for the fix!
/lgtm

/approve


Update Safe Client Gateway repo url

Updates the Safe Client Gateway repo url from the Rust implementation to the NodeJS implementation

Thank you @fmrsabino 🙌


Add parallelize kwargs as an IPU config entry

What does this PR do?

Fixes # (issue)
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Pipelined models require an ipu config in order to parallelize. If kwargs is not populated on the parallelize call, can we defer to the parallelize kwargs in the ipu config?
def parallelize(for_generation=False, **kwargs):
    kwargs = PipelineMixin.parallelize(kwargs)

The above avoids having to reference the already provided ipu_config on parallelize:
model = to_pipelined(model, ipu_config)
model.parallelize(**ipu_config._parallelize_kwargs)


Fix incorrect example code

In the case of sortable.options.group, [object Object] is returned.
Correctly is seems to sortable.options.group.name.
Sorry my bad English. Thanks!

thx


add ElementDecls to an internal subset

The use case is transforming this XML:
<?xml version="1.0"?>
<!DOCTYPE arbitrary SYSTEM "https://<IP_ADDRESS>/some.dtd" [

    <!ENTITY test "Dereferenced!">

]>
<arbitrary>
  <child>&test;</child>
</arbitrary>

into this XML (note the additional element definition within the DTD):
<?xml version="1.0"?>
<!DOCTYPE arbitrary SYSTEM "https://<IP_ADDRESS>/some.dtd" [

    <!ENTITY test "Dereferenced!">
    <!ELEMENT new_element ANY>

]>
<arbitrary>
  <child>&test;</child>
</arbitrary>

Nokogiri doesn't have any functionality to create or manipulate element declarations. The ElementDecl class is pretty much read-only, meaning that if your XML has one, you can parse and inspect it.
See original nokogiri-talk thread for more details.

Pardon me, if this makes no sense, but this would also allow something like this?
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE mydoc SYSTEM "mydoc.dtd" [
  <!ENTITY foo SYSTEM "./foo.xml">
]>
<root>&foo;</root>
]>

I'm having a hard time to understand how to get this using Nokogiri::XML::Builder 😢

Similarly for AttributeDecl ... Nokogiri offers no way to dynamically modify the document DTD to add these declarations.
Side note: libxml2 does not support adding EntityDecl to the DTD at runtime.
As a workaround for anyone who comes across this limitation: a way to work around this, suggested in this SO  post is to create a new doc by parsing the desired DTD, and then build the desired DOM tree within that document.

libxml2 API links:

https://gnome.pages.gitlab.gnome.org/libxml2/devhelp/libxml2-valid.html#xmlAddElementDecl
https://gnome.pages.gitlab.gnome.org/libxml2/devhelp/libxml2-valid.html#xmlAddAttributeDecl

Interesting side note: the JRuby implementation's parser, Xerces, does not support modifying the doctype!
https://xerces.apache.org/xerces-j/apiDocs/org/w3c/dom/Document.html#getDoctype()
So this is a feature that can only be implemented in CRuby, as far as I know.


Presentation Submission is missing top-level context

The JSON-LD document at:
https://identity.foundation/presentation-exchange/submission/v1
is missing the top-level @context object that should contain the rest of the document.

https://github.com/decentralized-identity/presentation-exchange/blob/master/submission/v1/index.json ?

@troyronda  can you include an example of the error you are experiencing with https://www.jsonld-checker.com/

@OR13 Yes - this document is missing the @context property that should wrap the rest of the properties.

I see... https://w3id.org/security/bbs/v1

Does this fix work.... https://github.com/decentralized-identity/presentation-exchange/pull/196

Yes, thanks @OR13


404 is "Not Found"

When I start a http-server.Browser will queried  "Failed to load resource: the server responded with a status of 404 (Not Found)". What's it? How can I solve?

Which files are in the directory you ran http-server in? What URL did you type in your browser?

Bumping this because I am suddenly having the same issue. I can't load any of my includes from a relative path. I'm getting 404 errors in the console, but only when running in http-server, not off the file system.
e.g. ../bower_components/angular/angular.min.js
All my production dependencies are up one dir from my index.html (I don't want 3rd party code in my app directory).
The Chrome console is showing all include requests as being located in a child directory, but only when running in http-server: localhost:8080/bower_components/etc.

http-server doesn't allow and, by the HTTP specs, cannot deliver files outside the web root. You should either let http-server serve the directory above or symlink it into the web root using ln -s.

@derhuerst Thanks much, makes perfect sense.

Would you mind closing the issue to reduce cognitive load for the maintainer? Thanks!

closes #315

Didn't see that @weirdoCHAO opened the issue. @weirdoCHAO please close this.

House cleaning.

I use https://www.npmjs.com/package/live-server


Add color picker

Please include color picker as well as an enhancement for this plugin.
Thanks,
Rohan

Duplicate of #11.


Hive Gateway debug logging now working

Issue workflow progress

Progress of the issue based on the
Contributor Workflow

[ ] 1. The issue provides a reproduction available on
Github,
Stackblitz
or
CodeSandbox

Make sure to fork this template and run yarn generate in the terminal.
Please make sure Mesh package versions under package.json matches yours.

[ ] 2. A failing test has been provided
[ ] 3. A local solution has been provided
[ ] 4. A pull request is pending review

Describe the bug
Even if i configure the logging to DEBUG, only INFO and WARN logs appear
To Reproduce Steps to reproduce the behavior:
Configure logger to DEBUG
  gateway.config.ts: |
    import {defineConfig, type WSTransportOptions, createStdoutExporter} from '@graphql-hive/gateway'

    export const gatewayConfig = defineConfig({
      pollingInterval: 60_000,
      healthCheckEndpoint: '/health',
      readinessCheckEndpoint: '/readiness',
      logger: 'debug',
    });

Expected behavior
DEBUG logs appear
Environment:

OS:
Hive gateway docker image

The name of the option is "logging" not logger;
https://github.com/ardatan/graphql-mesh/blob/02b234453f661996ce7a0a719e7753c78c78249f/packages/serve-runtime/src/types.ts#L335

Then the docs are incorrect
https://the-guild.dev/graphql/hive/docs/api-reference/gateway-config#logger

Hi, i do not think it works. If i set logging: debug, i get:
 [2024-09-24T07:38:13.971Z] INFO Configuring Hive registry reporting [2024-09-24T07:38:13.997Z] ERROR TypeError: Cannot read properties of undefined (reading 'child') at getReportingPlugin (file:///node_modules/.chunk/createGatewayRuntime-CUzu5O_p.mjs:56526:38) at createGatewayRuntime (file:///node_modules/.chunk/createGatewayRuntime-CUzu5O_p.mjs:57198:61) at runSupergraph (file:///node_modules/.chunk/cli-D8ZQiHnw.mjs:6301:19) at Command.supergraph (file:///node_modules/.chunk/cli-D8ZQiHnw.mjs:6225:14) at async Command.parseAsync (file:///node_modules/.chunk/cli-D8ZQiHnw.mjs:3661:6)


fix(ci): Show logs after each Google Cloud test job

Motivation
PR #5330 stopped showing any test logs in Google Cloud test runs that use the ssh-compute action.
But we need those logs to diagnose test failures.
Solution
Add a step that shows the logs after each time we run ssh-compute
Review
This PR is urgent because we need to be able to diagnose google cloud failures.
Reviewer Checklist

[x] Will the PR name make sense to users?

[ ] Does it need extra CHANGELOG info? (new features, breaking changes, large changes)

[x] Are the PR labels correct?
[x] Does the code do what the ticket and PR says?
[ ] How do you know it works? Does it have tests?

I think we're running into the 1 MB step output limit here:
https://github.com/ZcashFoundation/zebra/actions/runs/3200985566/jobs/5228636615
Longer-term, we could use log artifacts:
https://docs.github.com/en/actions/using-workflows/storing-workflow-data-as-artifacts
Or modify the ssh-compute GitHub action so it shows the SSH output.

https://github.com/google-github-actions/ssh-compute/issues/29

Superseded by https://github.com/ZcashFoundation/zebra/pull/5367


Cannot see tedee integration while trying to add from HA

I cannot see this integration when I'm trying to do steps from the instruction: Go to the integrations page (Configuration - Devices & Services). Click the "+ Add Integration" button in the lower left corner and look for the "tedee" integration
Steps to reproduce:

install tedee_hass_integration in HACS
restart
try to add integration

There is nothing in logs, except that HA reads the integration and gives the warning on non-standard integration.
https://github.com/joerg65/tedee_lock works perfectly.
HA version: 2022.3.3
tedee_hass_integration version: 2022.2.0

https://github.com/joerg65/tedee_lock works perfectly.

I assume this is the problem - please uninstall it before using this integrations and check if it works.

@cayco Did that help solving your issue?


feat: text decoration styling

Added feature from #215
Tag highlighting was missing the ability to do custom text decoration like line-through, underline, etc.
This PR exposes text decoration (the same way border styling is exposed)

Looks good to me!


Fix the EventTarget.addEventListener and EventTarget.removeEventListener useCapture argument - related to issue #14188

According to https://dom.spec.whatwg.org/#interface-eventtarget

The EventTarget.addEventListener useCapture argument must be (AddEventListenerOptions or boolean)
The EventTarget.removeEventListener useCapture argument must be (EventListenerOptions or boolean)

Fix issue https://github.com/Microsoft/TypeScript/issues/14188

@Diullei,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
It will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot

@Diullei, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, Microsoft Pull Request Bot

This appvayor error is not clear to me. Can someone help me to understand what I'm doing wrong?

The appveyor error means when replacing the default lib.d.ts with your changed version in TypeScript repo, some TypeScript tests failed (in this case the verifyDefaultLib_webworker test.
The test is a simple check: https://github.com/Microsoft/TypeScript/blob/master/tests/cases/compiler/verifyDefaultLib_webworker.ts
to see if the webworker library file contains error.
On a glance it looks like you defined the two new types only in the dom.generated.d.ts but not in the worker file, so when you use them in the worker file they could not be found.

Ok, thanks for your help! I'll fix this.

Hi @zhengbli the appveyor build has been fixed.

@zhengbli done!

Thanks @Diullei !


ERC20 extension

With a ERC20 contract, and a page showing the token balance and a form to send the tokens.

Talked with Damu about this yesterday. ERC721 might be a good idea too.
We should make sure that this works for hardhat & foundry!


Faulty availability shown when filter active

When I use an active filter for example filtering only chargers with min. 100 kw, there is always a green "0/0" shown in the bottom bar when I click on a charger (Ionity Weißkirchen for example). When I enter the details, I see the real availability (3/4).
Does not happen without filter, there it is working fine.

I think this has nothing to do with the filter by power, but rather a filter by plug type (e.g. CCS). Correct?

Could also be the cause. I am filtering for power and CCS / Type 2 plugs, yes.

Okay, in that case 6ec44bb should fix it. The availability shown at the bottom bar takes into account the filters (e.g. when you filter by CCS it only shows CCS plugs) - and with the changes introduced in the beta version for compatibility with OpenChargeMap, each plug type now has an API-internal ID and a common name, which need to be converted correctly for filtering the availability.


Error on edit preview

Getting unknown property: bizley\podium\models\Post::post
<?php if (!empty($preview)): ?>

        <?= Alert::widget([
            'body' => ''
                        . Yii::t('podium/view', 'Post Preview')
                        . ':
'
                        . $model->post,
            'options' => ['class' => 'alert-info']
        ]); ?>

<?php endif; ?>

Which version of Podium is this and where does this error occur? Is it post edit?

Podium 0.6 on Yii 2.0.10
Edit post, then Preview (New post/Preview works, both editors)
This line marked in error log (above)
. $model->post,
(BTW Reply with quote: nothing happens)

Confirm.
There should be $model->content instead of $model->post

Actually it's $model->parsedContent.
@triboe
It's fixed now in dev-master (0.7). d94989969011c2a2611cf4ee15959ec8bdce0c8b
Trigger on "Reply with quote" has been corrected as well. 80a062ca0f3ccebe584ed915bf9d30b823e9b7d8


[BEAM-12474] Write PubsubIO parsing errors to dead-letter topic

Current behavior of PubsubIO is to ignore parsing errors, relying on Pub/Sub dead-letter configuration to eventually send the message to a dead-letter topic. However, the message sent to the dead-letter topic loses all info on the error (though error logs should exist). Since parsing errors are also unlikely transient, it wastes a lot of resources with retries, and it can lead to infinite retry loops if no dead-letter is set up. This PR attempts to mitigate these issues by allow PubsubIO.Read to be configured with a dead-letter topic.
To avoid some messiness with the ExceptionAsMapHandler, I added a handler to WithFailures that just returns the exception. This also requires a new wrapper around Throwable to override the default equals implementation. Otherwise, we'd get a ton of log spam about the coder mutating the exception.
PubsubTestClient also needed to be updated to support testing this feature.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] Update CHANGES.md with noteworthy changes.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run Java PreCommit

Run Whitespace PreCommit

Run Java PreCommit

Run RAT PreCommit

Run Java PreCommit

Run Java PreCommit

Something seems wrong with pre-commit. It won't run. The only failure on the last run was a flake in the FlinkRunner test.

R: @TheNeuralBit

I think I'm going to be swamped until I go on leave for a while on July 1. Maybe @kennknowles could review?

Sure. Enjoy your leave!

R: @kennknowles

Run Java PreCommit

Added a comment to BEAM-10955 related to the Flink runner failures.

Run Java PreCommit

Run Java PreCommit

Run Java_Examples_Dataflow PreCommit

Run Java PreCommit

Failure is related to BEAM-10955. PR15119 needs to be merged to disable the test.

Moved EncodableThrowable to values/ and squashed the commits.

Run Java_Examples_Dataflow PreCommit

Run Java PreCommit

Run Java PreCommit

The only failure is related to BEAM-10955. It seems to be coming in and out of sickbay, so I don't think it should block this PR.

Run Java_Examples_Dataflow PreCommit

Run Java_Examples_Dataflow PreCommit

Run Java PreCommit

Failing tests seem related to BEAM-5172 and BEAM-10955

Thanks! Sorry for the slow review here.


Feature request: Sort Artist by Role

Not sure if this is a skin issue, or a core server issue.
I'd love to see an ability to sort an artists albums by their role.   For instance, in the attached screenshot, we can see that Miles Davis has performed or composed on a large number of albums, some of them his, some of them other artists.   On the first album, Sonny Rollins' "A Night at the Village Vanguard", Davis is the composer of track 5.  The second album, "Bag's Groove" is a Miles Davis album.   On "Blue Note Perfect Takes", he is the principal artist on one track of a compilation.
It would be great if we could get some sort of Role sort, such as:

Albums:

Bags Groove
Blue Haze
etc

Composer:

A Night at the Village Vanguard
Bass on Top

Performer:

Some other album
Yet another Album

This should be somewhat possible via LMS 8.4's release type support.


IWR6843 firmware package

Dear @sxontheway ,
Would you pls specify the firmware that you used for IWR6843 mmWave Radar in this project?
I would like to reproduce your output but cannot find the information of radar firmware.
Thank you,
hphnngcquan

Hi, do you solve the problem?


enable keyboard commands for Interactive Window history

Partially inspired by microsoft/vscode-jupyter#9914 and https://github.com/microsoft/vscode/issues/130724, the IW history view would be more useful if there were more actions that could be taken from that view. You can already re-run the cell in place with shift+enter, but actions like remove cell and go to code could also be given keyboard shortcuts (or just commands)

should also do https://github.com/microsoft/vscode-jupyter/issues/7756 as part of this

interactive.input.focus and interactive.history.focus commands already exist and the former has been expanded to focus on the most recent IW input from anywhere. Core delete cell commands are also now enabled for IW to allow keyboard commands

after some feedback, I'll try to enable these commands in the palette to increase discoverability, and add shift+tab as the default keybinding to focus on history


Sliver Decoration

This is a second attempt to merge #107269. Currently I've fixed two of the issues:

Fixed horizontal scrollview by using a switch statement to consider vertical/horizontal case.
Fixed issue of paintExtent not being the right extent for painting. Rather using a scrollExtent for the main axis length of the decoration box and painting it offsetted by the scrollOffset.
If the sliver child has inifinite scrollExtent, then we only draw the decoration down to the bottom of the cacheExtent. The developer is expected to ensure that the border does not creep up above the cache area.

This PR includes a test that checks that the correct rectangle is drawn at a certain scrollOffset for both the horizontal and vertical case which should be sufficient for checking that SliverDecoration works properly now.
Fixes https://github.com/flutter/flutter/issues/107498.

Also, looks like the analyzer is unhappy here.


Wrong text detection in "no sense" text

Hi,
I'm having a "de" response with > 0.99 score for a text like the following:
6LSHOJDV 5LYR 8LERXSLQ 8UPDV 5DXGVHSS 0DULQH 6\VWHPV ,QVWLWXWH DW 7DOOLQQ 8QLYHUVLW\ RI 7HFKQRORJ\ $%675$&7 7KH RWKHU LPSRUWDQW HQYLURQPHQWDO DVSHFW WKDW QHHGV (QYLURQPHQWDO FRQGLWLRQV ZHUH PRQLWRUHG XVLQJ LQ VLWX FRQWLQXRXV PRQLWRULQJ DUH RLO VSLOOV ,Q WKH *XOI RI )LQODQG PHDVXUHG LQKHUHQW RSWLFDO SURSHUWLHV DQG ZDWHU VDPSOLQJ WKH SUREDELOLW\ RI RLO VSLOOV LV KLJK GXH WR WKH LQFUHDVLQJ RLO WRJHWKHU ZLWK UHPRWH VHQVLQJ LPDJHU\ 0(5,6 DQG $6$5 WUDQVSRUWDWLRQ 6HYHUDO RLO SROOXWLRQ LQFLGHQWV KDSSHQHG LQ LQ 0XXJD %D\ %DOWLF 6HD 6LPXOWDQHRXV PRQLWRULQJ XVLQJ WKH JXOI RYHU WKH ODVW GHFDGH 'LUHFW HQYLURQPHQWDO LPSDFWV GLIIHUHQW PHWKRGRORJLHV JDYH GHWDLOHG RYHUYLHZ RI RI RLO VSLOOV DIIHFW VHDELUGV DQG FRDVWDO HFRORJ\ HVSHFLDOO\ VXVSHQGHG PDWWHU 630 ORDG LQWR WKH ZDWHU FROXPQ GXULQJ ZKHQ WKH VSLOO KLWV WKH VKRUH 7R PLQLPL]H WKH QHJDWLYH HIIHFW WKH GUHGJLQJ RSHUDWLRQV 0(5,6 )56 GDWD HQDEOHG WR RI RLO SROOXWLRQ DQG WR IDFLOLWDWH IDVW DSSOLFDWLRQ RI RLO UHFHLYH WKH GLVWULEXWLRQ RI 630 RQ ZDWHU VXUIDFH 7KH FRPEDWLQJ PHWKRGV DQ HDUO\ GHWHFWLRQ RI RLO VSLOOV DW VHD LV PHDVXUHPHQWV RI LQKHUHQW RSWLFDO SURSHUWLHV UHYLOHG WKH RI D JUHDW LPSRUWDQFH 0DQ\ VWXGLHV KDYH SURYHG WKDW UDGDU SDUWLFOH FRQFHQWUDWLRQ RQ YHUWLFDO VFDOH %DFNVFDWWHULQJ IURP LPDJHV FDQ SURYLGH LQIRUPDWLRQ RQ SRVVLEOH ORFDWLRQ DQG WKH $6$5 GDWD ZDV LQ FRUUHODWLRQ ZLWK RLO SURGXFWV H[WHQW RI RLO VSLOOV > @ GHWHUPLQHG IURP ZDWHU VDPSOHV ZKHQ EDOODVW ZDWHU GLVFKDUJH &RQWLQXRXV DQG ILQH VFDOH UHPRWH VHQVLQJ LV RQH RI WKH NH\ ZDV GHWHFWHG GXULQJ ILHOG VDPSOLQJ DVSHFWV LQ PRQLWRULQJ RI 630 DQG SRVVLEOH RLO VSLOOV QHDU WKH KDUERUV (QYLVDW 0(5,6 IXOO UHVROXWLRQ GDWD 0(5,6 )56 ,QGH[ 7HUPV  0(5,6 VXVSHQGHG PDWWHU LQKHUHQW DQG (QYLVDW $6$5 LPDJHU\ LV SURYLGHG E\ (6$ GDLO\ EDVHV RSWLFDO SURSHUWLHV DQG JLYHV JRRG EDVHV IRU FRQWLQXRXV PRQLWRULQJ 7KH VFRSH RI WKH FXUUHQW VWXG\ ZDV WR HYDOXDWH WKH XVH RI ,1752'8&7,21 0(5,6 )56 GDWD IRU PRQLWRULQJ RI VXVSHQGHG PDWWHU ORDG WR WKH FRDVWDO VHD GXULQJ WKH KDUERU GUHGJLQJ (QYLVDW $6$5 2QH RI WKH PDLQ FKDOOHQJHV LGHQWLILHG E\ WKH (XURSHDQ 6HD GDWD ZDV XVHG WR HYDOXDWH WKH SRVVLELOLW\ WR GHWHFW WKH RLO 3RUWV 2UJDQLVDWLRQ (632 LQ LWV HQYLURQPHQWDO FRGH VSLOOV (632 ZDV WKH VXVWDLQDEOH GHYHORSPHQW RI VHD SRUWV 0(7+2'6 $FFRUGLQJ WR WKH GRFXPHQW WKH HQYLURQPHQWDO LPSDFWV FDXVHG E\ SRUW UHODWHG DFWLYLWLHV VKRXOG EH UHGXFHG > @ 7KH 7KH ILHOG PHDVXUHPHQWV RI LQKHUHQW RSWLFDO SURSHUWLHV ILUVW VWHS LV WR SURSHUO\ PDQDJH HQYLURQPHQWDO LVVXHV ZKLFK WRJHWKHU ZLWK WDNLQJ ZDWHU VDPSOHV ZHUH SHUIRUPHG LQ UHTXLUHV FRQWLQXRXV HQYLURQPHQWDO PRQLWRULQJ 5HPRWH DQG 0XXJD %D\ RQ DQG

Citing from the front page:

This software cannot handle it well when the input text is in none of the expected (and supported) languages. For example if you only load the language profiles from English and German, but the text is written in French, the program may pick the more likely one, or say it doesn't know. (An improvement would be to clearly detect that it's unlikely one of the supported languages.)

Thanks anyway for the submission. It's a good example to demonstrate a limit of the library.
I believe that it should be detectable in the n-grams that the above is not a good match. And another idea is to cross-check with real words... it doesn't contain any.

My doubt is about the high percentage found, which is over 99%. My expectation would be to have a low percentage.
Thanks

+1. Today the probabilities of all detectable languages always add up to 100%, and the library doesn't even attempt to check if the text makes sense.

Would be interesting to see what's detected for a lower-case version of this text. German nouns are all capitalised, so it's plausible that German is the best match as there's decent scores for capital letter unigrams (moreso than for any other language, at least!). all-caps bigrams and trigrams are probably quite rare in the models.
@andrea-bologna ,  @djelinski  may I ask where you got texts like this from? It seems like strange input (though dictionary validation would be a nice feature)


Fail to download the RhoFold checkpoint

Hi,
Thanks for your brilliant work! I tried to download the RhoFold checkpoint for evaluation: wget https://proj.cse.cuhk.edu.hk/aihlab/RhoFold/api/download?filename=RhoFold_pretrained.pt -O RhoFold_pretrained.pt
However, it fails to download the checkpoint. Could you provide some suggestions? Thanks!

Hello,
Thank you for checking out our project! Sorry for the delay in getting back to you – GitHub doesn't send notifications properly 😅
We've pushed our checkpoints and miscellaneous files into a Google Drive for easier access. You can download them here:

https://drive.google.com/drive/folders/1umg0hgkBl7zsF_2GdCIKkfsRWbJNEOvp?usp=sharing

Hope this helps, happy to clarify anything else!
Cheers,
R


Remove kiyui as maintainer for AUR package

Kiyui has made it evident that they're no longer on Arch and outright removed themselves as a maintainer for the AUR package.
See: https://aur.archlinux.org/packages/lbry-app-bin#comment-813900
Best wishes to em' in their journies!

Best of luck Kiyui!


MSID: 96755 Version: 1 DOI: 10.1101/2<IP_ADDRESS>0977

MSID: 96755
Version: 1
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>0977
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=96755
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>0977

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/96755v1
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>0977
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/96755/v1/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

error: This journal reference (id c42) has no article-title element.


fix: wrong service account name

CLA is signed

/easycla

Hi @Vampouille,
please sign EasyCLA, which is mandatory check to review your PR and accept the contribution.
You can find about EasyCLA here - https://docs.linuxfoundation.org/lfx/easycla
and the steps to sign EasyCLA are here - https://docs.linuxfoundation.org/v2/easycla/contributors/individual-contributor
You can start your signing EasyCLA from here - https://api.easycla.lfx.linuxfoundation.org/v2/repository-provider/github/sign/18706487/51478266/38056/#/?version=2

This issue has been resolved in the latest documentation and you can now close the PR.
https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#manually-create-an-api-token-for-a-serviceaccount

/close
Feel free to reopen if the issue is not resolved yet.


CLI checks minimum supported Node.js version

Uses semver to check the Node.js version and throws an error if an unsupported version is used.
Closes #152

@JotinhaBR FYI, as this should help developers understand what's happening on #151


Settings screen: UI issue

Check the alignment of text.It should be same as design.

Verified this issue on keeper app v 1.1.9(289)


Implement: home page - 06

implement the home page from the 06 section up to the 07 section.
MacBook Pro 16_ - Home.zip

Hello I'm interested in contributing to this task.. I am implementing 6th and 7th section of homepage


chore(xp-treatment): Add k8s service account to XP Treatment chart

Motivation
This PR introduces a Kubernetes service account for the XP Treatment Service that will allow it to use Google service account credentials via workload identity instead of them being mounted as a volume.
Modification

charts/xp-treatment/templates/_helpers.tpl - Addition of the XP Treatment Service service account block in the default XP Treatment Service configs
charts/xp-treatment/templates/service-account.yaml - Addition of the new XP Treatment Service Kubernetes service account manifest
charts/xp-treatment/values.yaml - Addition of default XP Treatment Service service account values

Checklist

[x] Chart version bumped
[x] README.md updated

Thanks for the quick review @krithika369! I might need your help on this other PR first https://github.com/caraml-dev/helm-charts/pull/337 for XP Management; I'll be merging the changes there first before updating the XP Treatment chart in this PR to consume the updated XP Management chart.


[bugfix][DM] dm database, schema is database,so table no need schema

Purpose of this pull request

Check list

[ ] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

[ ] Update the release-note.

https://github.com/apache/seatunnel/pull/5208/   is update so close


Toggle is not work after modal view presented.

This UI hierarchy is before present modal view.

And this UI hierarchy is after present and dismiss modal view.

A position of frontview is now move properly I think.
(iOS8, Xcode 6)
Anybody has same issue?

Yeah, my issue is not exactly the same, but when I segue to a TabBarViewController using the modal segue, I am not able to toggle the side menu. The viewDidLoad method gets called in the side menu view controller, but the view never shows.


[test] Fix a DebugInfo test

A test fix missing from https://github.com/apple/swift/pull/11598

@swift-ci Please test macOS

@swift-ci Please smoke test Linux

Thanks! LGTM. I thought I had a similar PR yesterday, but perhaps I forgot to merge it!?

@adrian-prantl ahh, found it! https://github.com/apple/swift/pull/11611 tests passed, I'll merge yours. Thanks!