Microsoft stop supporting Firebase.iOS

Microsoft stop supporting Firebase.iOS (https://github.com/dotnet/maui/discussions/20359) and now best option is to use (https://github.com/AdamEssenmacher/GoogleApisForiOSComponents).
MauiMTAdmob uses Xamarin.Firebase.iOS.Core <IP_ADDRESS>, so would you consider to update it to AdamE.Firebase.iOS.Core <IP_ADDRESS> in the future?
I got this error and only fix for now is to install original Xamarin.Firebase.iOS libraries.
##[error]/Users/runner/hostedtoolcache/dotnet/packs/Microsoft.iOS.Sdk.net8.0_17.5/17.5.8018/targets/Xamarin.Shared.Sdk.targets(1641,3): Error : clang++ exited with code 1:
Undefined symbols for architecture x86_64:
"_APMAnalyticsConfiguration", referenced from:
+[FIRAnalytics startWithConfiguration:options:] in FirebaseAnalytics(FIRAnalytics.o)
"_APMAppMeasurementOriginFirebase", referenced from:
+[FIRAnalytics startWithConfiguration:options:] in FirebaseAnalytics(FIRAnalytics.o)
"_APMConsentSettings3P", referenced from:
+[FIRAnalytics setConsent:] in FirebaseAnalytics(FIRAnalytics.o)
"_APMFormattedEventName", referenced from:
+[FIRAnalytics logEventWithOrigin:name:parameters:] in FirebaseAnalytics(FIRAnalytics.o)
"_APMFormattedUserPropertyName", referenced from:
+[FIRAnalytics setUserPropertyString:forName:] in FirebaseAnalytics(FIRAnalytics.o)
"_APMIsAnalyticsCollectionDeactivated", referenced from:
+[FIRAnalytics startWithConfiguration:options:] in FirebaseAnalytics(FIRAnalytics.o)
"_APMIsAnalyticsCollectionEnabled", referenced from:
+[FIRAnalytics startWithConfiguration:options:] in FirebaseAnalytics(FIRAnalytics.o)
"_APMMonitorLogTagOptionKey", referenced from:
+[FIRAnalytics startWithConfiguration:options:] in FirebaseAnalytics(FIRAnalytics.o)
"_APMSafelistedEventsOptionKey", referenced from:
+[FIRAnalytics startWithConfiguration:options:] in FirebaseAnalytics(FIRAnalytics.o)
"OBJC_CLASS$_APMAdExposureReporter", referenced from:
OBJC_CLASS$_FIRAAdExposureReporter in FirebaseAnalytics(FIRAAdExposureReporter.o)
"OBJC_CLASS$_APMAnalytics", referenced from:
objc-class-ref in FirebaseAnalytics(FIRAnalytics.o)
"OBJC_CLASS$_APMConditionalUserProperty", referenced from:
OBJC_CLASS$_FIRAConditionalUserProperty in FirebaseAnalytics(FIRAConditionalUserProperty.o)

Yes, as this seems the most promising package to replace the deprecated
libraries, I'll test everything and then if everything works fine I'll
switch to it.
On Wed, 7 Aug 2024, 14:11 Mateusz Kapusta, @.***> wrote:

Microsoft stop supporting Firebase.iOS (dotnet/maui#20359
https://github.com/dotnet/maui/discussions/20359) and now best option
is to use (https://github.com/AdamEssenmacher/GoogleApisForiOSComponents).
MauiMTAdmob uses Xamarin.Firebase.iOS.Core <IP_ADDRESS>, so would you consider
to update it to AdamE.Firebase.iOS.Core <IP_ADDRESS> in the future?
I got this error and only fix for now is to install original
Xamarin.Firebase.iOS libraries.
##[error]/Users/runner/hostedtoolcache/dotnet/packs/Microsoft.iOS.Sdk.net8.0_17.5/17.5.8018/targets/Xamarin.Shared.Sdk.targets(1641,3):
Error : clang++ exited with code 1:
Undefined symbols for architecture x86_64:
"_APMAnalyticsConfiguration", referenced from:
+[FIRAnalytics startWithConfiguration:options:] in
FirebaseAnalytics(FIRAnalytics.o)
"_APMAppMeasurementOriginFirebase", referenced from:
+[FIRAnalytics startWithConfiguration:options:] in
FirebaseAnalytics(FIRAnalytics.o)
"_APMConsentSettings3P", referenced from:
+[FIRAnalytics setConsent:] in FirebaseAnalytics(FIRAnalytics.o)
"_APMFormattedEventName", referenced from:
+[FIRAnalytics logEventWithOrigin:name:parameters:] in
FirebaseAnalytics(FIRAnalytics.o)
"_APMFormattedUserPropertyName", referenced from:
+[FIRAnalytics setUserPropertyString:forName:] in
FirebaseAnalytics(FIRAnalytics.o)
"_APMIsAnalyticsCollectionDeactivated", referenced from:
+[FIRAnalytics startWithConfiguration:options:] in
FirebaseAnalytics(FIRAnalytics.o)
"_APMIsAnalyticsCollectionEnabled", referenced from:
+[FIRAnalytics startWithConfiguration:options:] in
FirebaseAnalytics(FIRAnalytics.o)
"_APMMonitorLogTagOptionKey", referenced from:
+[FIRAnalytics startWithConfiguration:options:] in
FirebaseAnalytics(FIRAnalytics.o)
"_APMSafelistedEventsOptionKey", referenced from:
+[FIRAnalytics startWithConfiguration:options:] in
FirebaseAnalytics(FIRAnalytics.o)
"OBJC_CLASS$_APMAdExposureReporter", referenced from:
OBJC_CLASS$_FIRAAdExposureReporter in
FirebaseAnalytics(FIRAAdExposureReporter.o)
"OBJC_CLASS$_APMAnalytics", referenced from:
objc-class-ref in FirebaseAnalytics(FIRAnalytics.o)
"OBJC_CLASS$_APMConditionalUserProperty", referenced from:
OBJC_CLASS$_FIRAConditionalUserProperty in
FirebaseAnalytics(FIRAConditionalUserProperty.o)
—
Reply to this email directly, view it on GitHub
https://github.com/marcojak/MauiMTAdmob/issues/89, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAUIPIQ5266PHI4WVYOBZBDZQIMGNAVCNFSM6AAAAABMEMN242VHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ2TGNBVGEZTENA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Can you tell me how long this might take?


Relational Training: CUDA OOM Out of Memory Error

Hi,
Thanks for developing and releasing this codebase. I'm using it to train on a tabular data. I tried both in Tabular format and Relational format. But in the Relational format I'm getting CUDA OOM (Out of Memory Error).
Original Table (Raw data):
The original table has only 8 cols x 10,000 rows (which I have subsampled for testing).
The model in Tabular mode trains perfectly fine and I am able to generate synthetic samples.
Relational Table Format (Parent / Child):
In the relational format the tables have the following statistics:

Parent: 4 cols x 5359 rows
Child: 6 cols x 10,000 rows, where one parent row has ~150 corresponding child rows (at most).

However, in this case:

Parent model in Tabular format trains well, but
Child model in Relational format, with the parent model, fails with error CUDA OOM (Out of Memory Error).

I have tried this on GCP with

NVIDIA T4 x2 (16GB)
NVIDIA L4 x2 (24GB)
NVIDIA A100 (40GB)

I suspect the Relational format Child model fails because it requires both the Parent & Child tables to be loaded into GPU memory. But the dataset is tiny. How can I overcome the OOM error?
Do you have any suggestions?

Hi @solitaryangler , you are correct; I think the issue is with the Relational model. In particular, it may be due to the large number of child rows a single parent row has. You can try setting the output_max_length to some number like 1024 or 2048 to see if it prevents the OOM.  What this does, however, is it will limit the number of children that will be used in training the model.
Also, you can try experimenting with not using the trained parent model and instead training the full relational model from scratch. Just set parent_realtabformer_path=None. We got better results training the full relational model from scratch in one of our experiments. :)
So you can have something like:
child_model = REaLTabFormer(
    model_type="relational",
    parent_realtabformer_path=None,
    output_max_length=2048,
    train_size=0.8)

Hope this helps!

Hi @avsolatorio
Thanks for your comments. You were absolutely right. Once I limited the child entries per parent row, then the model trained fine. I am closing this issue as resolved.
My apologies on the late reply, I was traveling.

Closed

Hello @solitaryangler, no worries! I am so glad that it's working now. 😀


ENH: sparse: add count_nonzero method

Here's a count_nonzero method for sparse matrices, as well as some better docs for getnnz, as discussed at #3343. It doesn't entirely fix that issue, and I'm not actually going to try to do that in a single PR.
Ping @argriffing, @chebee7i, @jnothman.

Closed this PR as I'm not going to finish it. If someone else wants to have a try, please submit a new PR.


Fix BaseEvent inheritance

This PR fixes the following errors:
(237,36): error TS2339: Property 'layerX' does not exist on type 'Event | BaseEvent'.
(236,56): error TS2339: Property 'layerY' does not exist on type 'Event | BaseEvent'.
(8,14): error TS2339: Property 'stopPropagation' does not exist on type 'Event | BaseEvent'.

For people who looks for a workaround, this is the solution:
var e = <any>d3.event;

I'm not sure BaseEvent is meant to extend Event. Do you have docs for this change?
The Event is the browser default event, while I believed d3 created it's own events with a sourceEvent pointing to the original event. If you know the event is an Event at that point in time, you should be using TypeScript for coercion - not changing the definition.

d3.event is a DOM Event. the following definition is from the d3 document:
 The d3.event object is a DOM event and implements the standard event fields like timeStamp and keyCode as well as methods like preventDefault() and stopPropagation().

Cool, thanks. Did you have a link to that? Should d3.event be updated to be event: BaseEvent instead of a union of types?

@blakeembrey https://github.com/d3/d3/wiki/Selections


Loading Models with Keras/Tensorflow into Android App with Chaquopy API

System information.

OS Platform and Distribution: Android 13
TensorFlow installed from: Chaquopy
TensorFlow version: tensorflow==2.1
Python version: 3.8

Describe the problem.
I trained models then have saved and uploaded them as zip files into the cloud. In the Android App, I'm using a 3rd party API called chaquopy which interfaces python code in a Java app, facilitating the transition between prototyping and deployment.
In the app, I download the models from the cloud, unzip them, then when I try to load these models, an error is thrown.
Describe the current behavior.
The app crashes when I try to load the models. There were similar challenges with .h5 files as compiling them threw errors, but they were different errors.
Describe the expected behavior.
The model should be loaded, then be able to predict values based on outputs like in the standard documentation.
Contributing.

Do you want to contribute a PR? (yes/no): no

Standalone code to reproduce the issue.
build.grade file
buildscript {
    repositories {
        jcenter()
        maven { url "https://chaquo.com/maven" }
        google()

    }
    dependencies {
        classpath 'com.android.tools.build:gradle:8.0.2'

        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}
plugins {
    id 'com.chaquo.python' version '14.0.2' apply false
    id 'com.android.application' version '7.3.0' apply false
    id 'com.android.library' version '7.3.0' apply false
    id 'org.jetbrains.kotlin.android' version '1.7.21' apply false

}

Source code / logs.
def download_models():
    global optimal_NNs

    path = file_management.get_file_path()

    file_name = functions.get_model_folder_name()

    i = 0
    for filename in os.listdir(os.environ['HOME']):
        if "Model " in filename:
            optimal_NNs = load_model(os.path.join(os.environ['HOME'], f'{filename}'))
            return optimal_NNs.optimizer

Process: ca.mcmaster.waterqualitymonitor, PID: 28707
com.chaquo.python.PyException: NotFoundError: Op type not registered 'DisableCopyOnRead' in binary running on localhost. Make sure the Op and Kernel are registered in the binary running in this process. Note that if you are loading a saved graph which used ops from tf.contrib, accessing (e.g.) tf.contrib.resampler should be done before importing the graph, as contrib ops are lazily registered when the module is first accessed.
at .tensorflow.python.framework.ops._get_op_def(ops.py:3712)
at .tensorflow.python.framework.function_def_to_graph.function_def_to_graph_def(function_def_to_graph.py:218)
at .tensorflow.python.framework.function_def_to_graph.function_def_to_graph(function_def_to_graph.py:58)
at .tensorflow.python.saved_model.function_deserialization.load_function_def_library(function_deserialization.py:312)
at .tensorflow.python.saved_model.load.init(load.py:113)
at .tensorflow.python.keras.saving.saved_model.load.init(load.py:118)
at .tensorflow.python.saved_model.load.load_internal(load.py:550)
at .tensorflow.python.keras.saving.saved_model.load.load(load.py:89)
at .tensorflow.python.keras.saving.save.load_model(save.py:150)
at .backend.download_models(backend.py:54)
at .chaquopy_java.call(chaquopy_java.pyx:354)
at .chaquopy_java.Java_com_chaquo_python_PyObject_callAttrThrowsNative(chaquopy_java.pyx:326)
at com.chaquo.python.PyObject.callAttrThrowsNative(Native Method)
at com.chaquo.python.PyObject.callAttrThrows(PyObject.java:232)
at com.chaquo.python.PyObject.callAttr(PyObject.java:221)
at ca.mcmaster.testsuitecommon.SplashActivity$1.onClick(SplashActivity.java:99)
at android.view.View.performClick(View.java:7892)
at android.widget.TextView.performClick(TextView.java:16219)
at android.view.View.performClickInternal(View.java:7869)
at android.view.View.-$$Nest$mperformClickInternal(Unknown Source:0)
at android.view.View$PerformClick.run(View.java:30880)
at android.os.Handler.handleCallback(Handler.java:942)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:226)
at android.os.Looper.loop(Looper.java:313)
at android.app.ActivityThread.main(ActivityThread.java:8757)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:571)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1067)

The latest stable keras doesn't provide any issues. It's a platform issue.

@siddij3,
Glad the issue was resolved with the latest stable tensorflow version. Are you still looking for any further assistance from the Keras team? If not, Could you please feel free to move this issue to closed status. Thank you!


PR: Improve UI/UX of the Run plugin configuration widgets

Description of Changes

The new architecture for the Run plugin (added in #17467) is quite powerful and flexible. However, it's not easy to understand how to make use of it.
This PR aims to improve that by

Adding default execution parameters to our config system. That will show them in the Preferences page for Run, which will allow users to easily modify them. In addition, that page won't appear empty, which is a bit odd.
Simplifying significantly the UI of the dialog that appears when you go to Run > Open run settings. In addition, that dialog was modified so that it allows to only set run settings per file (just as in Spyder 5). That makes it simpler to understand and leaves creating global execution configs to the Run entry in Preferences.

Add a new CollapsibleWidget widget, which is based on QCollpasible from SuperQt. That required increasing our minimal constraint on SuperQt to >=0.6.2.

Visual changes
Configuration per file

Before

After

Preferences page

Before

After

Dialog to create global run configurations

Before

After

Issue(s) Resolved

Fixes #21878
Fixes #20700
Fixes #20569
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: @ccordoba12

Hello @ccordoba12! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file spyder/plugins/run/models.py:

Line 454:14: E231 missing whitespace after ','

In the file spyder/plugins/run/tests/test_run.py:

Line 644:46: E712 comparison to False should be 'if cond is False:' or 'if not cond:'
Line 816:9: E124 closing bracket does not match visual indentation

In the file spyder/plugins/run/widgets.py:

Line 819:14: E231 missing whitespace after ':'

In the file spyder/utils/icon_manager.py:

Line 381:80: E501 line too long (116 > 79 characters)
Line 382:80: E501 line too long (115 > 79 characters)

@dalthviz, this is ready for review. Please let me know issues/shortcomings you find with the new implementation.

Gave this an initial local check on Windows and saw some behaviors/interactions that felt kind of strange (the last couple of things are more likely bugs):

Information tooltip refering to the Ok button at first glance make me think that it was refering to the Save globally button instead of the OK button at the bottom of the dialog itself. Not sure if it was discussed before, but now that I'm trying the dialog is kind of strange to have buttons in different places of the dialog:  Also, the Delete button refers to a global delete of the config right?

Being able to trigger a file run config delete when I haven't save anything yet (even a confirmation dialog appears and then the run dialog gets closed):

Triggering a Save globally without entering a name/leaving the default one triggers a confirmation dialog before showing and red circle x over the config name lineedit:

Trying to save a new global config without a name changes the lineedit placeholder to a message indicating a name is needed. Maybe to make things more clear putting the red circle x over the lineedit:

Seems like trying to modify a global config from the run config dialog ends up deleting the global config?:

A traceback when using Reset changes and Edit selected buttons on the Run preference page:

Traceback (most recent call last):
  File "E:\Acer\Documentos\Spyder\Spyder otros\carlos\spyder\spyder\plugins\run\confpage.py", line 251, in <lambda>
    lambda checked: self.params_table.show_editor()
  File "E:\Acer\Documentos\Spyder\Spyder otros\carlos\spyder\spyder\plugins\run\confpage.py", line 111, in show_editor
    (extension, context, params) = model[index]
  File "E:\Acer\Documentos\Spyder\Spyder otros\carlos\spyder\spyder\plugins\run\models.py", line 540, in __getitem__
    tuple_index = self.params_index[index]
KeyError: -1

Other than that seems like things are working as expected but probably having more people testing this could be worthy (seems like there could be some interactions that I haven't checked yet :thinking:)

Just looking at the pictures, I would remove the heading "Runner settings" in the dialog windows. As a user, it is not clear why the working directory settings are separate from the runner settings. This will also simplify the dialog by removing one level of nesting.

To @dalthviz:

Information tooltip refering to the Ok button at first glance make me think that it was refering to the Save globally button instead of the OK button at the bottom of the dialog itself. Not sure if it was discussed before, but now that I'm trying the dialog is kind of strange to have buttons in different places of the dialog

We discussed this with @conradolandia and agree with you. That's why I decided to remove "Save globally" and move the Delete button to the dialog button box at the bottom.
To help understand users where to set global configurations, I added a new entry called like that to the Run menu:

Also, the Delete button refers to a global delete of the config right?

No, it refers to deleting file configurations only. To clarify that, I changed the behavior of that button so that it's disabled for default or global configurations.

Being able to trigger a file run config delete when I haven't save anything yet (even a confirmation dialog appears and then the run dialog gets closed)

It should be fixed now by the change I mentioned above.

Triggering a Save globally without entering a name/leaving the default one triggers a confirmation dialog before showing and red circle x over the config name lineedit

It's no longer a problem.

Trying to save a new global config without a name changes the lineedit placeholder to a message indicating a name is needed. Maybe to make things more clear putting the red circle x over the lineedit

That's a great suggestion to make things consistent. I implemented it in one of my last commits.

Seems like trying to modify a global config from the run config dialog ends up deleting the global config?

It shouldn't be a problem anymore.

A traceback when using Reset changes and Edit selected buttons on the Run preference page

Thanks for noticing it. It should be fixed now.

To @jitseniesen:

Just looking at the pictures, I would remove the heading "Runner settings" in the dialog windows

Great suggestion! I did that in one of my last commits (see updated screenshots in the OP).

In addition to fixing the problems found in review, I took the opportunity to improve the design of the Run page in Preferences (see the updated OP).

Gave another check and I think the difference between the local vs global configs is clearer now :+1: However, there are a couple of things that seem like bugs/I'm still not sure about:

Cloning/duplicationg a global config and then removing the selected config removes all the created global configs:

Create a new local config, open the dialog again, try to modify the config without changing the name lineedit. The circular red x appears. Following that, try to set as preset configuration the default from the combobox (or use the reset button), still unable to close the dialog via the Ok button

Open the run dialog and choose a different preset or even just open and try to close it via the Ok button the dialog will be kept open due to the name:

So my guess is that it is not possible to override an existing local config? In fact, as things are right now, is not possible to select one of the already created configs/presets without creating a new config, right? If that is the case, probably more feedback about the error needs to be provided. Some ideas:

Add some sort of message somewhere indicating that a new name is needed
When showing the collapsible section, remove the text along side showing the circle red x and move focus to the line edit to point people not only that something is invalid but that they need to take action to overcome it

From the checks I have been doing, I would say that from the run dialog it would be nice to support the following operations:

Select a config from the presets and use it without having to do any modification (without having to deal with the Custom configuration section)
Be able to select a preset and change a specific config without having to create a new one
Be able to select a preset and use it as a base for a new config with a different name

Not sure how much of the these things are feasible/fall under the scope you had for this PR/the general functionality of the run dialog @ccordoba12 but sharing the ideas that came to mind while checking this

Thanks @dalthviz for the additional review! About your comments:

Cloning/duplicationg a global config and then removing the selected config removes all the created global configs

Good catch! It should be fixed now.

Create a new local config, open the dialog again, try to modify the config without changing the name lineedit. The circular red x appears.
Open the run dialog and choose a different preset or even just open and try to close it via the Ok button the dialog will be kept open due to the name
So my guess is that it is not possible to override an existing local config?

These problems were an oversight on my side. The thing is I added a validation so that users can't introduce repeated config names in the run dialog. But I forgot to skip it when the config name and the one shown in the preset combobox are the same. So, please test again.

Select a config from the presets and use it without having to do any modification (without having to deal with the Custom configuration section)

This should be fixed now.

Be able to select a preset and change a specific config without having to create a new one

This is not possible anymore, i.e. with the changes done here. I think it was before, but then it gave users the odd impression that settings were not saved (see issue #20700, which was reported several times).
However, to not force users to provide a name the first time they change global parameters, I decided to set Custom for this file as the config name in that case. But for any other change to those parameters, they'll need to set a name of their own.

Be able to select a preset and use it as a base for a new config with a different name

This should be possible now. Please check again.

Gave this another check and seems like things are now working as expected. Will give the code another check but for the most part I would say that this looks good to me :+1:

Also, on a last manual check, I noticed that seems like you can create a global config with the same name of an already create per file config

Yep, that's correct. Since global configs take precedence over file ones, I think that validation is not appropriate and so I didn't implement it. Furthermore, it could be too restrictive to users given that they can create as many file configs as they want for as many files as possible.
The good thing is that there a subtle clue in RunDialog about which configs are global and which ones belong to the file: the Delete button. If it's enabled, it means we're dealing with a file config; if not, it means the config is global.
If users let us know that's not enough, we can think about how to disambiguate them. But for now, I think that's ok.

One last note: this PR also contains a couple of small fixes to our tests to deal with the Numpy 2.0 release (which is causing the failures in master).

After modifying the default behaviour and restarting spyder the original default configuration reappears along side my changed version. As a result my changes are not used.
Is this expected behaviour? If so how do i change the default behaviour?

Is this expected behaviour? If so how do i change the default behaviour?

No, it's not. Please open a new issue about it and add to it a small video showing what you did to better understand your problem.

Configuration per file
| Before | After |
| - | - |
| ![imagen](https://github.com/spyder-ide/spyder/assets/365293/26515b4e-1b7d-4b11-8ddd-20b9ea515d90) | ![imagen](https://github.com/spyder-ide/spyder/assets/365293/4e294cbe-d697-49bd-919b-dca43a04f307)

Preferences page
| Before | After |
| - | - |
| ![imagen](https://github.com/spyder-ide/spyder/assets/365293/f898e6e0-3bd0-4005-975f-40c7b024eb92) | ![imagen](https://github.com/spyder-ide/spyder/assets/365293/822dd54e-3ad0-49a1-876a-a9faccad57ff)

Global run configuration
| Before | After |
| - | - |
| ![imagen](https://github.com/spyder-ide/spyder/assets/365293/83cf96d5-f303-425e-a39f-812274652045) | ![imagen](https://github.com/spyder-ide/spyder/assets/365293/ec83d2c5-026b-4d20-a2bf-af5001659082)


Jamf-Pro-External-Application-Custom-Schema-com.macjutsu.super-v5.0.0-beta2

Updated the JSON to include the new keys introduced with super v5.0.0-beta2.
Jamf-Pro-External-Application-Custom-Schema-com.macjutsu.super-v5.0.0-beta2.json

Thank you!


Spending a Predicate should not require a Wallet, just a provider

Motivation
After reviewing specs and implementation, its clear that spending the locked coins in an existing Predicate should not require using a Wallet, just the Provider.
Usage example
Update this function to use a Provider instance instead of a Wallet.
Possible implementations
Update the spend predicate function and tests to use the Provider directly.
For the tests, can probably just change it like this:
    const initialPredicateBalance = await setupPredicate(wallet, amountToPredicate, predicate);
    const initialReceiverBalance = await wallet.provider.getBalance(receiverAddress, NativeAssetId);

-    await predicate.submitSpendPredicate(wallet, initialPredicateBalance, receiverAddress);
+    await predicate.submitSpendPredicate(wallet.provider, initialPredicateBalance, receiverAddress);

And then update implementation of submitSpendPredicate to use this parameter type.
The spending step of a Predicate requires:

provider
amount of coin
asset id
receiver address

and optionally:

predicate data

@camsjams, I think the predicate should be treated as a new Signer Module... enabling the Wallet to be instantiated with a predicate. Does it make sense?
Or it could be a Wallet Vault on the Wallet Manager.

I think the predicate should be treated as a new Signer Module... enabling the Wallet to be instantiated with a predicate. Does it make sense?
Or it could be a Wallet Vault on the Wallet Manager.

@luizstacio Can you drop a link or example?

I don't have a very good example because it would be something new.
But, the idea is to make predicate work for SDK users like a Wallet and also integrate with all parts that already use Wallet.
The main changes would be;

Abstract common methods like transfer, fund, sendTransaction to a BaseWallet class.
Remove/Implement a signer class here.
Update the populateTransactionWitnessesSignature to populate the predicate data on the transaction.


Unify ForAllIndex/Snapshot/Lock functions

What does this PR change? What problem does it solve?
The ForAllIndex/Snapshot/Lock functions use the same code pattern, thus introduce an new ParallelList function to deduplicate the implementation. This also allows to easily parallelize a few more List usages.

Was the change previously discussed in an issue or on the forum?
No.

Checklist

[x] I have read the contribution guidelines.
[x] I have enabled maintainer edits.
[ ] I have added tests for all code changes.
[ ] I have added documentation for relevant changes (in the manual).
[ ] There's a new file in changelog/unreleased/ that describes the changes for our users (see template).
[x] I have run gofmt on the code in all commits.
[x] All commit messages are formatted in the same style as the other commits in the repo.
[x] I'm done! This pull request is ready for review.

LGTM.

I've restored the code handling excludeIDs in ForAllSnapshots, which got lost while refactoring it.


Create issue templates

In our other repos, we make it easier for users to create the right kind of issue with templates.  Basically, prepopulates labels based on bug, question, enhancement, etc.  Also provides some general structure to the issue to help us make it actionable.

Added Bug and Feature request templates. Thanks!


month-picker can not use range

here is the sample code:
const month = ref([] as any)

<VueDatePicker v-model="month" month-picker range />

and get error
It was work when I use v5.0.1, but when you update version to v5.1.0, my code get error

fix
new version shoud be declared
const monthDateData = ref([
  {
    month: new Date().getMonth(),
    year: new Date().getFullYear()
  }, {
    month: new Date().getMonth(),
    year: new Date().getFullYear()
  }
])


Cannot install pyrosm

I've been trying to install this pyrosm on Windows10 and Python 3.6 because it looks potentially useful (although inadequately documented... like, which elements are included in the "walking" network?) for isolating parts of OSM data within a polygon before converting the remaining "highways" into a NetworkX graph.
However, I tried to use pip installl pyrosm, but I cannot install the package because I get the infamous "A GDAL API version must be specified" error.
`  Collecting fiona
Using cached Fiona-1.8.17.tar.gz (1.3 MB)
ERROR: Command errored out with exit status 1:
command: 'c:\winpython\python-3.6.5.amd64\python.exe' -c 'import sys, setuptools, tokenize; sys.argv[0] = ...
Complete output (1 lines):
A GDAL API version must be specified. Provide a path to gdal-config using a GDAL_CONFIG environment variable or use a GDAL_VERSION environment variable.
ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.`
The thing is, I already have the newest version of GDAL and Fiona 1.8.17 installed, and I already added GDAL to my path variables, and I can already use geopandas, fiona, shapely, rtree, etc. normally.
I couldn't find a list of requirements and/or dependencies in the documentation aside from Py3.6, so maybe the real problem is something else.
I hope to be able to use this package, and so I appreciate any assistance in properly installing it.

Hi @bramson,
the recommended way to install pyrosm is by using conda as mentioned in the docs:
https://pyrosm.readthedocs.io/en/latest/installation.html
If you have not use conda before, I very much recommend start using it. There is more information about this e.g. in here:
https://autogis-site.readthedocs.io/en/latest/course-info/installing-miniconda.html
The issue you face is not actually related to Pyrosm as such, but installing the dependencies (geopandas) which rely on external C-libraries (which do not install well on Windows unfortunately).

My python installation is WinPython, rather than Anaconda, and is not a(as far as I know) compatible with conda installation.
So, In order to install GeoPandas I had to do things manually with whl files, but it's not that bad once you know the sequence.
I believe I have already installed all the packages of the same versions that pyrosm depends on, but for some reason the installation of pyrosm with pip on Windows doesn't recognize my previous installations, and tries to collect and reinstall them, which it cannot do.  But it shouldn't be trying to do that (GeoPandas installation doesn't try to reinstall GDAL after my manual installation of GDAL).
I don't really know much about dependencies, installation, or pip, but what I though would work (installing all the dependencies, then installing the package) is not working in this case.
Do you have any ideas for a work around?

@bramson Is there a specific reason why you need to stick with WinPython instead of using conda which is nowadays more or less the "industry standard" dealing with package installations for Python ecosystem?
What comes to your installation issue under Windows, I cannot say much with this information, as I would need to understand what versions of Geopandas, Fiona, etc. packages you have installed. Most likely there is a dependency for newer version of specific package why pyrosm attempts to install fiona etc. again with pip instead of using your already installed versions. But to make your life easier also in the long run, I still highly recommend to start using conda and do all your Python installations with that, because conda was developed exactly to handle tricky installation situations like this. Hence, it will help make your life MUCH easier also with many other packages as well. With conda you do not need to worry about any environment settings or installing packages separately from wheels etc. but everything (just) works with a single command i.e. conda install -c conda-forge pyrosm.
There is a good Twitter thread about these things, and how to solve them in here:
https://twitter.com/ocefpaf/status/1321814088662568965

Hi all! Thanks for the library, very awesome! To (hopefully) shed some light on this issue (because I was struggling with it too - somehow didn't see the conda-forge installation process and tried with pip):
It seems that setup_requires=requirements is set in setup.py. As far as I understood, this tries to install geopandas (with its dependencies fiona etc.) for the setup process, and not just for running it later. I managed to resolve the issue by cloning the repository, replacing the line with setup_requires=['setuptools>=18.0'] and installing with pip install -e ..
In case the setup_requires is not required I'll gladly make a pull request.
I had some other issues due to pygeos geometries not being compatible with geopandas but I think they're not related to the problem at hand but to my geopandas installation.
Cheers

@HTenkanen The only reason I'm sticking with WinPython is that up to now I've only faced minor inconveniences with it...much smaller inconveniences than installing a new python distribution from scratch and making sure all my code still works on it.  Obviously I like the idea of installing packages with no effort, but that's what pip is already supposed to do, and usually does.  I looked at the twitter thread you pointed to in order to convince myself to make the sideways leap to anaconda, but it immediately descended to technical jargon that I could not follow, so unfortunately I could not understand what the proposed benefits or solutions to problems actually are.  So far the only thing I've had to install "manually" is geopandas.  And the only thing that's ever failed to install is this package.
@dominikbucher This sounds reasonable to me.  Like I said, based on the docs, I already have the appropriate versions of all the required packages installed.  But the installation of this package seems to be trying to reinstall them, and it can't via pip.  I'm not currently proficient in cloning and altering repositories, so it would be great (at least for me and other non-conda users) to make this change part of a pip-able package.

Hi guys! And thanks @dominikbucher for sharing how you tackled this issue! 👍 Your solution indeed seems like it could resolve this issue with pip, and definitely the goal is to support installation using pip only also in Windows (assuming all the requirements have been installed). So I will test if this trick works, and update the package for the next release. This should then hopefully resolve @bramson's installation issue.
@bramson About conda vs pip/WinPython: it is definitely up to you what package manager you want to use. Just from experience I can say that pip installations in Windows can sometimes be tricky especially with GIS packages that often rely on non-Python libraries (such as GDAL), hence recommended conda.

@HTenkanen Thank you for incorporating this fix in the next version.
If I could go back, then I'd go the Anaconda route, as I've advised new people in the lab to do.  But from where I am, it's probably a few days of package version compatibility frustration just to get back to exactly where I am.  Actually, if there is a function in conda to read a requirements file and get all those versions of all those packages, then it may not be so bad.  I'll look into it.  But anyway, as you said, being to install via pip in Windows will only strengthen the package and broaden/accelerate its use.

FYI: @bramson With conda, there is this fileformat called environment.yaml (or .yml which is the same thing) which does same things as requirements.txt (it is formatted a bit differently but should be quite easy). Typically the safest way to do the installations is to use these things called environments that isolate the installations e.g. for different projects that you might have.
To get a quick overview about this, you can take a look some docs that we have written about it here:  https://autogis-site.readthedocs.io/en/latest/course-info/create-python-gis-env.html#create-an-environment-from-an-yaml-file
Also to understand how the environment.yml files typically look like, you can take a look e.g. how the environment files for different versions of Python have been written for this pyrosm package, such as this for Python 3.8: 38-conda.yaml

@bramson : I now merged the installation fix to the master, and hopefully it should work now. Could you please test and verify if you can now successfully install pyroms with pip by running the following command (which installs the dev version directly from Github):
pip install git+https://github.com/HTenkanen/pyrosm.git@master

@HTenkanen : Thank you for your message.  I was able to successfully install the dev version with your command.
When I run the command from pyrosm import get_data (in order to work through some examples in the docs), I get:
C:\WinPython\python-3.6.5.amd64\lib\site-packages\geopandas\_compat.py:88: UserWarning: The Shapely GEOS version (3.8.0-CAPI-1.13.1 ) is incompatible with the GEOS version PyGEOS was compiled with (3.8.1-CAPI-1.13.3). Conversions between both will be slow.
  shapely_geos_version, geos_capi_version_string

I don't know if this is the same problem @dominikbucher mentioned, but my geopandas and shapely versions seem to match the pyrosm requirements.  I don't know if ignoring this will cause problems (I mean, how slow, and will I ever do that?), or what exactly the fix would be.  But it seems to be installed and working, so I'll try it on my real problem on Tuesday and let you know if anything explodes.

@bramson Excellent, now everything seems to work. 👍 The warning that you get actually comes from geopandas (used under the hood in pyrosm). It is nothing dangerous and you can ignore it. Will add a note about this to the documentation as well.
Technical details but: It just warns that in couple of different libraries that are used under the hood of geopandas are using different version of GEOS library. This is something that will eventually be automatically fixed once Shapely library is updated to version 2.0 (should happen sometime next year hopefully).


Rename new branch name in the Orchestrator

I have created a new branch in Mauro (CR8000) based on November 2021 but is not displaying as a branch in the Orchestrator as below. Instead there are three versions of NHS Data Dictionary (November 2021).
I raised this with James and he said:
It should be showing the branch name too - I'll fix that. But yes, I think the process of creating a new branch should probably include a step to rename the model so that it's easier to identify in the UI too.
It might be a manual step for the time being, until we build it into Mauro.

Workaround is to edit the title in Mauro, e.g. change it to NHS Data Dictionary (CR8000).
James will add the branch names to the drop-down for the next release.

15/2/22 - branches renamed.


Update README.md

Update README file per developer's feedback from validation

@hermanwenhe This change also needs to be merged after you merge #85 , then we apply the pattern to all samples and add Alex as reviewer for a final review. Thanks!


Detect .well/knowns that do not have a version number

The New York Times has a .well-known, however, without the version number. Currently, OptMeowt does not detect the .well-known. So, I think we should change the detection on our end. It works if am on https://www.nytimes.com/.well-known/gpc.json but not if I am just on https://www.nytimes.com/.

Maybe, this is a timing issue. The formatting seems to be OK.

As discussed in our meeting earlier today, I found that this issue was not caused by OptMeowt being unable to find the GPC.json file, but rather a reset happening when sub-frames are loaded on the NYT site.
This involves the Chrome APIs, since I have a local variable reset to false when a page is detected to refresh. I did not know that a listener connected to the Chrome onBeforeNavigate API was triggered even when sub-frames were loaded. Checking to see if a parent frame is being loaded resolved this issue.
Since I have pushed the resulting bug fixes, I will go ahead and close this issue.


update particle-cli on README.md

In addition to installing and uninstalling, I'd thought it made sense to also show users how to update particle-cli.  There is a section on Particle Docs on how to do this, but I thought it might be convenient to see it on the Github repo which is where I was looking for it and couldn't find it.

Thanks. This dropped out of the radar for some reason.


Add functionality to select what events we want to log

Title says it all.
Adds the --events flag.

Im going to merge this as the repo is about to get moved to cloudfoundry-contrib org.


Remove deprecated attributes and methods

Must be done in a major release (3.0.0).

Must be well documented in release notes

Since the methods are deprecated before, do we need to specify that in the doc?

Since the methods are deprecated before, do we need to specify that in the doc?

The methods should not be documented anymore, but in the release notes we should have an entry listing them.


Add support for serialization of suppressed exceptions

This change serializes the Java 7+ suppressed exceptions similarly
to exception causes. This means that we would try to deserialize
known exceptions and if it's not possible, for example because the
suppressed exception is a custom exception type, then we fallback
on the placeholder exception type.
Fixes #9487

@bot-gradle test RFM

OK, I've already triggered ReadyForMerge build for you.


Linux CLI Fails to Create NodeJS Webapp

Following the guide for deploying a nodejs webapp using CLI (https://docs.microsoft.com/en-ca/azure/app-service/containers/quickstart-nodejs), the following is outputted:
az webapp up -n app-name
Resource group 'appsvc_rg_Linux_CentralUS' already exists.
Creating App service plan 'appsvc_asp_Linux_CentralUS' ...
__init__() takes 1 positional argument but 2 positional arguments (and 2 keyword-only arguments) were given
Traceback (most recent call last):
  File "/opt/az/lib/python3.6/site-packages/knack/cli.py", line 197, in invoke
    cmd_result = self.invocation.execute(args)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 366, in execute
    cmd.exception_handler(ex)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/appservice/commands.py", line 54, in _polish_bad_errors
    raise ex
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 343, in execute
    result = cmd(params)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 182, in __call__
    return self.handler(*args, **kwargs)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/__init__.py", line 436, in default_command_handler
    result = op(**command_args)
  File "/home/daniel/.azure/cliextensions/webapp/azext_webapp/custom.py", line 131, in create_deploy_webapp
    sku=sku_def, reserved=(is_linux or None))
TypeError: __init__() takes 1 positional argument but 2 positional arguments (and 2 keyword-only arguments) were given

This occurred both when attempting to deploy my own app, and deploying the quickstart provided in the guide.
The expected behaviour was successful creation of the service plan, then zipping and deploying the app, as defined in the guide.
I am on Ubuntu 18.04.01, using the most updated version of the az tool.

This is a dupe of https://github.com/Azure/azure-cli-extensions/issues/325, will be using #325 to track the issue.
A fix is in PR https://github.com/Azure/azure-cli-extensions/pull/326


UDTs in expanded panel - 0.5天

If you don't mind, could you please explain a bit about the meaning of the links on the left?
I am wondering if they are the type script hashes. If so, when clicked one of the links, would it be better to pre-fill the UDT form in the UDT management view? I am bit confused when it shows me the empty UDT form after clicking one of the links.

We will add the explanation and pre-fill feature, thanks!

Add a link to explorer:
EXPLORER_URL/sudt/:typeHash
For example:
https://explorer.nervos.org/aggron/sudt/0xe3be4fb98ec914886c6525abac97e1f8769c59492636a1d35955e9163ef46efa

Pre-fill is added:


Building turicreate is broken with GCC 5.4.0

$ g++ --version
g++ (Ubuntu 5.4.0-6ubuntu1~16.04.12) 5.4.0 20160609

Running make -j8 on turicreate/debug breaks with following errors -
In file included from /home/shreya/turicreate/test/unity/toolkits/neural_net/test_combine_queue.cxx:10:0:
/home/shreya/turicreate/src/ml/neural_net/combine_queue.hpp: In instantiation of ‘void turi::neural_net::SubscribeOnQueuePublisher<T>::Proxy::Receive(std::shared_ptr<turi::neural_net::Subscription>) [with T = int]’:
/home/shreya/turicreate/test/unity/toolkits/neural_net/test_combine_queue.cxx:294:1:   required from here
/home/shreya/turicreate/src/ml/neural_net/combine_queue.hpp:72:13: error: ‘assert’ was not declared in this scope
       assert((downstream_));  // We cannot have been canceled yet.
             ^
/home/shreya/turicreate/src/ml/neural_net/combine_queue.hpp:72:13: note: suggested alternatives:
In file included from /home/shreya/turicreate/src/external/boost/boost_1_68_0/boost/test/tools/assertion.hpp:23:0,
                 from /home/shreya/turicreate/src/external/boost/boost_1_68_0/boost/test/test_tools.hpp:53,
                 from /home/shreya/turicreate/src/external/boost/boost_1_68_0/boost/test/unit_test.hpp:18,
                 from /home/shreya/turicreate/test/unity/toolkits/neural_net/test_combine_queue.cxx:12:
/home/shreya/turicreate/src/external/boost/boost_1_68_0/boost/mpl/assert.hpp:79:27: note:   ‘mpl_::assert’
 template< bool C >  struct assert        { typedef void* type; };
                           ^
/home/shreya/turicreate/src/external/boost/boost_1_68_0/boost/mpl/assert.hpp:79:27: note:   ‘mpl_::assert’
cc1plus: error: unrecognized command line option ‘-Wno-unknown-warning-option’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-tautological-compare’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-parentheses-equality’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-constant-logical-operand’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-mismatched-tags’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-deprecated-register’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-unused-command-line-argument’ [-Werror]
cc1plus: all warnings being treated as errors
test/unity/toolkits/neural_net/CMakeFiles/test_combine_queue.cxxtest.dir/build.make:62: recipe for target 'test/unity/toolkits/neural_net/CMakeFiles/test_combine_queue.cxxtest.dir/test_combine_queue.cxx.o' failed
make[2]: *** [test/unity/toolkits/neural_net/CMakeFiles/test_combine_queue.cxxtest.dir/test_combine_queue.cxx.o] Error 1
CMakeFiles/Makefile2:17962: recipe for target 'test/unity/toolkits/neural_net/CMakeFiles/test_combine_queue.cxxtest.dir/all' failed
make[1]: *** [test/unity/toolkits/neural_net/CMakeFiles/test_combine_queue.cxxtest.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
In file included from /usr/include/c++/5/bits/random.h:35:0,
                 from /usr/include/c++/5/random:49,
                 from /home/shreya/turicreate/src/toolkits/drawing_classifier/dc_data_iterator.hpp:11,
                 from /home/shreya/turicreate/test/unity/toolkits/drawing_classifier/test_dc_prediction.cxx:9:
/usr/include/c++/5/bits/uniform_int_dist.h: In instantiation of ‘class std::uniform_int_distribution<float>’:
/home/shreya/turicreate/test/unity/toolkits/drawing_classifier/test_dc_prediction.cxx:112:54:   required from here
/usr/include/c++/5/bits/uniform_int_dist.h:63:7: error: static assertion failed: template argument not an integral type
       static_assert(std::is_integral<_IntType>::value,
       ^
In file included from /usr/include/c++/5/bits/move.h:57:0,
                 from /usr/include/c++/5/bits/stl_pair.h:59,
                 from /usr/include/c++/5/bits/stl_algobase.h:64,
                 from /usr/include/c++/5/bits/char_traits.h:39,
                 from /usr/include/c++/5/string:40,
                 from /usr/include/c++/5/random:40,
                 from /home/shreya/turicreate/src/toolkits/drawing_classifier/dc_data_iterator.hpp:11,
                 from /home/shreya/turicreate/test/unity/toolkits/drawing_classifier/test_dc_prediction.cxx:9:
/usr/include/c++/5/type_traits: In instantiation of ‘struct std::make_unsigned<float>’:
/usr/include/c++/5/bits/uniform_int_dist.h:223:57:   required from ‘std::uniform_int_distribution<_IntType>::result_type std::uniform_int_distribution<_IntType>::operator()(_UniformRandomNumberGenerator&, const std::uniform_int_distribution<_IntType>::param_type&) [with _UniformRandomNumberGenerator = std::linear_congruential_engine<long unsigned int, 16807ul, 0ul,<PHONE_NUMBER>ul>; _IntType = float; std::uniform_int_distribution<_IntType>::result_type = float]’
/usr/include/c++/5/bits/uniform_int_dist.h:165:51:   required from ‘std::uniform_int_distribution<_IntType>::result_type std::uniform_int_distribution<_IntType>::operator()(_UniformRandomNumberGenerator&) [with _UniformRandomNumberGenerator = std::linear_congruential_engine<long unsigned int, 16807ul, 0ul,<PHONE_NUMBER>ul>; _IntType = float; std::uniform_int_distribution<_IntType>::result_type = float]’
/home/shreya/turicreate/test/unity/toolkits/drawing_classifier/test_dc_prediction.cxx:129:66:   required from here
/usr/include/c++/5/type_traits:1757:62: error: invalid use of incomplete type ‘class std::__make_unsigned_selector<float, false, false>’
     { typedef typename __make_unsigned_selector<_Tp>::__type type; };
                                                              ^
/usr/include/c++/5/type_traits:1721:11: note: declaration of ‘class std::__make_unsigned_selector<float, false, false>’
     class __make_unsigned_selector;
           ^
cc1plus: error: unrecognized command line option ‘-Wno-unknown-warning-option’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-tautological-compare’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-parentheses-equality’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-constant-logical-operand’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-mismatched-tags’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-deprecated-register’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-unused-command-line-argument’ [-Werror]
cc1plus: all warnings being treated as errors
test/unity/toolkits/drawing_classifier/CMakeFiles/test_dc_prediction.cxxtest.dir/build.make:62: recipe for target 'test/unity/toolkits/drawing_classifier/CMakeFiles/test_dc_prediction.cxxtest.dir/test_dc_prediction.cxx.o' failed
make[2]: *** [test/unity/toolkits/drawing_classifier/CMakeFiles/test_dc_prediction.cxxtest.dir/test_dc_prediction.cxx.o] Error 1
CMakeFiles/Makefile2:18671: recipe for target 'test/unity/toolkits/drawing_classifier/CMakeFiles/test_dc_prediction.cxxtest.dir/all' failed
make[1]: *** [test/unity/toolkits/drawing_classifier/CMakeFiles/test_dc_prediction.cxxtest.dir/all] Error 2
In file included from /usr/include/c++/5/bits/random.h:35:0,
                 from /usr/include/c++/5/random:49,
                 from /usr/include/c++/5/bits/stl_algo.h:66,
                 from /usr/include/c++/5/algorithm:62,
                 from /home/shreya/turicreate/src/external/boost/boost_1_68_0/boost/smart_ptr/shared_ptr.hpp:39,
                 from /home/shreya/turicreate/src/external/boost/boost_1_68_0/boost/shared_ptr.hpp:17,
                 from /home/shreya/turicreate/src/external/boost/boost_1_68_0/boost/test/tools/assertion_result.hpp:21,
                 from /home/shreya/turicreate/src/external/boost/boost_1_68_0/boost/test/tools/old/impl.hpp:20,
                 from /home/shreya/turicreate/src/external/boost/boost_1_68_0/boost/test/test_tools.hpp:46,
                 from /home/shreya/turicreate/src/external/boost/boost_1_68_0/boost/test/unit_test.hpp:18,
                 from /home/shreya/turicreate/test/unity/toolkits/drawing_classifier/test_dc_evaluation.cxx:10:
/usr/include/c++/5/bits/uniform_int_dist.h: In instantiation of ‘class std::uniform_int_distribution<float>’:
/home/shreya/turicreate/test/unity/toolkits/drawing_classifier/test_dc_evaluation.cxx:66:51:   required from here
/usr/include/c++/5/bits/uniform_int_dist.h:63:7: error: static assertion failed: template argument not an integral type
       static_assert(std::is_integral<_IntType>::value,
       ^
In file included from /usr/include/c++/5/bits/move.h:57:0,
                 from /usr/include/c++/5/bits/stl_pair.h:59,
                 from /usr/include/c++/5/bits/stl_algobase.h:64,
                 from /usr/include/c++/5/bits/char_traits.h:39,
                 from /usr/include/c++/5/string:40,
                 from /home/shreya/turicreate/src/external/boost/boost_1_68_0/boost/test/utils/basic_cstring/bcs_char_traits.hpp:25,
                 from /home/shreya/turicreate/src/external/boost/boost_1_68_0/boost/test/utils/basic_cstring/basic_cstring.hpp:21,
                 from /home/shreya/turicreate/src/external/boost/boost_1_68_0/boost/test/detail/global_typedef.hpp:15,
                 from /home/shreya/turicreate/src/external/boost/boost_1_68_0/boost/test/tree/observer.hpp:17,
                 from /home/shreya/turicreate/src/external/boost/boost_1_68_0/boost/test/unit_test_log.hpp:18,
                 from /home/shreya/turicreate/src/external/boost/boost_1_68_0/boost/test/tools/old/impl.hpp:19,
                 from /home/shreya/turicreate/src/external/boost/boost_1_68_0/boost/test/test_tools.hpp:46,
                 from /home/shreya/turicreate/src/external/boost/boost_1_68_0/boost/test/unit_test.hpp:18,
                 from /home/shreya/turicreate/test/unity/toolkits/drawing_classifier/test_dc_evaluation.cxx:10:
/usr/include/c++/5/type_traits: In instantiation of ‘struct std::make_unsigned<float>’:
/usr/include/c++/5/bits/uniform_int_dist.h:223:57:   required from ‘std::uniform_int_distribution<_IntType>::result_type std::uniform_int_distribution<_IntType>::operator()(_UniformRandomNumberGenerator&, const std::uniform_int_distribution<_IntType>::param_type&) [with _UniformRandomNumberGenerator = std::linear_congruential_engine<long unsigned int, 16807ul, 0ul,<PHONE_NUMBER>ul>; _IntType = float; std::uniform_int_distribution<_IntType>::result_type = float]’
/usr/include/c++/5/bits/uniform_int_dist.h:165:51:   required from ‘std::uniform_int_distribution<_IntType>::result_type std::uniform_int_distribution<_IntType>::operator()(_UniformRandomNumberGenerator&) [with _UniformRandomNumberGenerator = std::linear_congruential_engine<long unsigned int, 16807ul, 0ul,<PHONE_NUMBER>ul>; _IntType = float; std::uniform_int_distribution<_IntType>::result_type = float]’
/home/shreya/turicreate/test/unity/toolkits/drawing_classifier/test_dc_evaluation.cxx:58:44:   required from here
/usr/include/c++/5/type_traits:1757:62: error: invalid use of incomplete type ‘class std::__make_unsigned_selector<float, false, false>’
     { typedef typename __make_unsigned_selector<_Tp>::__type type; };
                                                              ^
/usr/include/c++/5/type_traits:1721:11: note: declaration of ‘class std::__make_unsigned_selector<float, false, false>’
     class __make_unsigned_selector;
           ^
cc1plus: error: unrecognized command line option ‘-Wno-unknown-warning-option’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-tautological-compare’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-parentheses-equality’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-constant-logical-operand’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-mismatched-tags’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-deprecated-register’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-unused-command-line-argument’ [-Werror]

However, you can build turicreate/debug/src

I am experiencing a similar problem while building the debug version on Ubuntu 20.04. My gcc version is 9.3.0. Here is the log
[ 62%] Building CXX object src/model_server/CMakeFiles/unity.dir/server/registration.cpp.o
In file included from /home/pradeep/repos/turicreate/src/core/storage/serialization/serialize.hpp:8,
                 from /home/pradeep/repos/turicreate/src/core/storage/serialization/serialization_includes.hpp:6,
                 from /home/pradeep/repos/turicreate/src/core/parallel/atomic.hpp:12,
                 from /home/pradeep/repos/turicreate/src/core/data/flexible_type/flexible_type.hpp:15,
                 from /home/pradeep/repos/turicreate/src/model_server/lib/toolkit_class_specification.hpp:10,
                 from /home/pradeep/repos/turicreate/src/model_server/lib/toolkit_class_registry.hpp:8,
                 from /home/pradeep/repos/turicreate/src/model_server/server/registration.hpp:9,
                 from /home/pradeep/repos/turicreate/src/model_server/server/registration.cpp:6:
/home/pradeep/repos/turicreate/src/core/storage/serialization/iarchive.hpp: In instantiation of ‘void turi::iarchive::read_into(T&) [with T = boost::multiprecision::number<boost::multiprecision::backends::cpp_int_backend<128, 128, boost::multiprecision::unsigned_magnitude, boost::multiprecision::unchecked, void> >]’:
/home/pradeep/repos/turicreate/src/core/storage/serialization/iarchive.hpp:242:9:   required from ‘static void turi::archive_detail::deserialize_impl<InArcType, T, true>::exec(InArcType&, T&) [with InArcType = turi::iarchive; T = boost::multiprecision::number<boost::multiprecision::backends::cpp_int_backend<128, 128, boost::multiprecision::unsigned_magnitude, boost::multiprecision::unchecked, void> >]’
/home/pradeep/repos/turicreate/src/core/storage/serialization/iarchive.hpp:257:65:   required from ‘turi::iarchive& turi::operator>>(turi::iarchive&, T&) [with T = boost::multiprecision::number<boost::multiprecision::backends::cpp_int_backend<128, 128, boost::multiprecision::unsigned_magnitude, boost::multiprecision::unchecked, void> >]’
/home/pradeep/repos/turicreate/src/core/util/hash_value.hpp:65:39:   required from here
/home/pradeep/repos/turicreate/src/core/storage/serialization/iarchive.hpp:120:15: error: ‘void* memcpy(void*, const void*, size_t)’ writing to an object of type ‘class boost::multiprecision::number<boost::multiprecision::backends::cpp_int_backend<128, 128, boost::multiprecision::unsigned_magnitude, boost::multiprecision::unchecked, void> >’ with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Werror=class-memaccess]
  120 |         memcpy(&c, buf + off, sizeof(T));
      |         ~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/pradeep/repos/turicreate/src/external/boost/boost_1_68_0/boost/multiprecision/cpp_int.hpp:12,
                 from /home/pradeep/repos/turicreate/src/core/util/int128_types.hpp:44,
                 from /home/pradeep/repos/turicreate/src/core/data/flexible_type/flexible_type.hpp:16,
                 from /home/pradeep/repos/turicreate/src/model_server/lib/toolkit_class_specification.hpp:10,
                 from /home/pradeep/repos/turicreate/src/model_server/lib/toolkit_class_registry.hpp:8,
                 from /home/pradeep/repos/turicreate/src/model_server/server/registration.hpp:9,
                 from /home/pradeep/repos/turicreate/src/model_server/server/registration.cpp:6:
/home/pradeep/repos/turicreate/src/external/boost/boost_1_68_0/boost/multiprecision/number.hpp:41:7: note: ‘class boost::multiprecision::number<boost::multiprecision::backends::cpp_int_backend<128, 128, boost::multiprecision::unsigned_magnitude, boost::multiprecision::unchecked, void> >’ declared here
   41 | class number
      |       ^~~~~~
cc1plus: error: unrecognized command line option ‘-Wno-unknown-warning-option’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-parentheses-equality’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-constant-logical-operand’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-mismatched-tags’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-deprecated-register’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-unused-command-line-argument’ [-Werror]
cc1plus: all warnings being treated as errors
make[2]: *** [src/model_server/CMakeFiles/unity.dir/build.make:63: src/model_server/CMakeFiles/unity.dir/server/registration.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:3952: src/model_server/CMakeFiles/unity.dir/all] Error 2
make: *** [Makefile:152: all] Error 2

Is there a temporary workaround?

I just noticed there is a PR to fix this here. I will be very happy to have that one resolved. :pray:

I just noticed there is a PR to fix this here. I will be very happy to have that one resolved. 🙏 Also, is there a temporary workaround in the meanwhile (apart from disabling -Werror)?

@pradkrish - I think the temporary workaround would be to apply the changes (or at least the first commit) from the pull request you reference.
@hoytak - It's not clear to me what still needs to be done in that pull request. Can you take over the pull request?

Thanks, I rebased the branch on master locally and I was able to build the debug version. Then while running make to build C++ unit tests, it failed with the following error.
[ 79%] Building CXX object test/util/CMakeFiles/SpanTests.cxxtest.dir/SpanTests.cxx.o
In file included from /usr/include/c++/9/vector:67,
                 from /home/pradeep/repos/turicreate/src/core/util/Span.hpp:12,
                 from /home/pradeep/repos/turicreate/test/util/SpanTests.cxx:9:
/usr/include/c++/9/bits/stl_vector.h: In instantiation of ‘class std::vector<const int, std::allocator<const int> >’:
/home/pradeep/repos/turicreate/test/util/SpanTests.cxx:66:41:   required from here
/usr/include/c++/9/bits/stl_vector.h:398:66: error: static assertion failed: std::vector must have a non-const, non-volatile value_type
  398 |       static_assert(is_same<typename remove_cv<_Tp>::type, _Tp>::value,
      |                                                                  ^~~~~
cc1plus: error: unrecognized command line option ‘-Wno-unknown-warning-option’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-parentheses-equality’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-constant-logical-operand’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-mismatched-tags’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-deprecated-register’ [-Werror]
cc1plus: error: unrecognized command line option ‘-Wno-unused-command-line-argument’ [-Werror]
cc1plus: all warnings being treated as errors
make[2]: *** [test/util/CMakeFiles/SpanTests.cxxtest.dir/build.make:63: test/util/CMakeFiles/SpanTests.cxxtest.dir/SpanTests.cxx.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:8206: test/util/CMakeFiles/SpanTests.cxxtest.dir/all] Error 2
make: *** [Makefile:152: all] Error 2


Layout Components

Are we planning to have basic layout components like Rows and Columns in the component library? I was building basic components for personal use, i can try to create a pr for those, if its still in the scope of the project

I haven't thought much about layout stuff just yet. Having flexbox-based rows and columns would be nice. You are welcome to create PR but currently, the SCSS building only works on Windows - I'm planning on fixing this next.

I was able to use sass building on mac, and fix the css output by using include_str instead of magnis as of now.    std::process::Command::new("sass.cmd") to    std::process::Command::new("sass") made it work with Mac. I will try to push Column and Row for layout soon just for the review.


Proved part of the braiding coherence lB=r

Proved the -⊗1 version of the coherence theorem.
I might get around to proving the final identity later but for now I thought it would be useful to have this as a PR and other people can do it in the meantime if they want.
Also, I wasn't sure where exactly to write it so I created a new module inside Braided.agda. Feel free to move stuff around if that is not appropriate.

TODO: Open the module publicly exposing the final identity once it's proved


question

https://github.com/poudel/bikram/blob/5a669c66e5a447c2e5c67576ed1adf3eb34969a3/bikram/constants.py#L66-L157
was curious how did you get those values?

I pulled that from here here but changed the data structure to my liking


Better alert UI than native alert

Hi @thevahidal !
I would love to create an alert window :)

Maybe I can make a design in figma and send you a picture what I would love to implement ?

Hi @thevahidal !
I've designed the modal window.
Let me know if that's okay :)


interpolation of Alpha values on Transformations

I added interpolation of Alpha values on transformation. This does not make much sense but I got some Spriter-Animations where the Alpha-value of "bones" where animated. This did not get applied otherwise.
Discard the PR if you think, it is not useful

Hey, thanks for submitting the PR. Before merging, I'll have to investigate if this can have any adverse effects for other scenations.


How to set CMake version?

Sorry, I'm new at this. I understand I need version 3.19.1 specifically. How to configure that?

Hello.
You should install cmake version 3.19.1. Also you can sets the minimum required version of cmake for a project in CMakeLists.txt.
https://cmake.org/cmake/help/latest/command/cmake_minimum_required.html
example:
cmake_minimum_required(VERSION 3.19.1) <--------- This is setting  minimum required version of cmake for a project

project(RemoteBinaryMapper)

set(CMAKE_CXX_STANDARD 17)

include(cmake/make.cmake)

set(CMAKE_INCLUDE_CURRENT_DIR ON)
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -g -Wall")

include_directories(${CMAKE_SOURCE_DIR}/modules/common/include)

find_package(cpprestsdk REQUIRED)

executable(${PROJECT_NAME}
            SOURCES "./src"
            THREADS
            MODULES BinaryMapper)

Hello.
GitHub-hosted runners have a cmake version 3.21.4 on all OS and you shouldn't have any problems with action.
If your project don't build on github then send it to me, I check it.
If you cannot build project locally then you need install cmake version 3.19.1 and more on your computer.
Also I recommend to set the minimum required version of cmake for a project in CMakeLists.txt.
https://cmake.org/cmake/help/latest/command/cmake_minimum_required.html
example:
cmake_minimum_required(VERSION 3.19.1)    #<--------- This is setting minimum required version of cmake for a project

project(RemoteBinaryMapper)

set(CMAKE_CXX_STANDARD 17)

include(cmake/make.cmake)

set(CMAKE_INCLUDE_CURRENT_DIR ON)
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -g -Wall")

include_directories(${CMAKE_SOURCE_DIR}/modules/common/include)

find_package(cpprestsdk REQUIRED)

executable(${PROJECT_NAME}
            SOURCES "./src"
            THREADS
            MODULES BinaryMapper)

Hi @chadananda
Do you have some problems with Action?
If you don't have problem I will close this issue.


loki, prometheus: Add Loki metrics to Consul and scrape it with Prometheus

Adds Loki metrics endpoint as a service in Consul and configures Prometheus to scrape it.
Nginx configs already have a proxy set up for port 3100.

@grembo prometheus.ini needs version increment

@grembo prometheus.ini needs version increment

Good catch


Should support multi-topics certificate?

Firstly, thanks for the great library. It helped me a lot.
Last week, I had struggled with the push for 3 days. The iOS guys gave me new iOS certificates and ask me to update current certificates on server. Everything worked fine except that iOS app didn't receive the push. The notification.error was empty.
I investigated and figured out that the iOS certificate was a multi-topics one which contains 2 bundle ids for both staging and production environments. Unfortunately, houston doesn't support specifying apns-topic header, so I asked iOS guy to give a single-topic certificate and it worked like a charm.
I wonder if we should allow specifying bundle id so that library can work with multi-topics certificates.
Thanks.

Currently on the second day of struggling with this. I've tried everything. Scoured every stackoverflow / forum related topic to this issue of the notification not being received from APN houston, but yet working flawlessly from the command line. Are there any alternatives to sending notifications via Rails?

@joshuachestang try Rpush.


escrow timeout notifications should be returned with the order filter in GETNotifications

have the following notification types in your db:

buyerDisputeTimeout
vendorDisputeTimeout
moderatorDisputeExpiry
buyerDisputeExpiry

call GETNotifications with ?filter=order

Observed:
The notifications from step 1 are not returned.
Expected:
Escrow timeout related notifications are picked up by the order filter and returned.

This is actually a client issue. The client needs to send additional types in the filter param (& separated)


New extensions PR naming convention

I recently submitted an extension and wondered how I should name the PR. I took exemple on the other opened PRs for new extensions but I think there should be a template for naming them, that we can find in the docs or when creating the PR.
What do you think?

Any thoughts on that?

We have a bot that will properly tag the PR if it's a new extension or a improvement to one (with its name) - that's what we use to quickly check them. I'm not sure we have to enforce a specific pattern, just write whatever is the most descriptive!


fix typo in GetStartedJavaAndroid.md

iOS -> Android

@KenAlin : Thanks for your contribution to the Azure documentation! The author, @zhouwangzw, has been notified to review your proposed change.

#sign-off

#sign-off


File params-sim-run.json

How to generate file params-sim-run.json?

params-sim-run.json should be generated in the following steps.

Execute python -m circa.experiment generate to generate the simulation data.
Execute python -m circa.experiment tune to explore parameter combinations.

You can insert --max-workers 16 before tune to enable multi-processing. 16 can be replaced with other positive integers, e.g., the number of CPU cores.
--model-params params-sim-tune.json stated in README.md is also optional, which is used to filtered out some parameter combinations.

Execute Rscript img/draw.sim.R to produce summaries under img/output.

This command may end with a file-not-found error, as other simulation experiments have not been conducted.
Only the content in img/output/best-sim-tuning.tex is in need now.

Execute python -m circa.experiment params > params-sim-run.json to create a parameter template.
Edit params-sim-run.json (generated in the Step 4) according to img/output/best-sim-tuning.tex (generated in the Step 3).

For each Method in img/output/best-sim-tuning.tex, choose the row with the highest AC.5. The related parameters can be found in the name column.
For example, in my previous run, name of the SPOT instance with the highest AC.5 is Empty-SPOT\_p0.01. Hence, in params-sim-run.json, only 0.01 in the spot.risk list is reserved and other options (0.001 and 0.0001) are removed.
All the graph parameters are neglected in the simulation study. As for a real-world dataset, the leading component in name before the first dash (-) is for the graph. For example, PC\_gauss\_a0.5 means,

only pc_gauss is used,
choose 0.5 for alpha, and
max_conds_dim is unlimited with null in the json file.

Our experiment results can be found in figshare.
In circa.zip, you can find all four param-*.json we used.


Improve Data Import deletion

Currently, if there are over 10k rows, the delete function throws an unhandled exception. We should either implement a bulk method for deletion, or limit the deletion to 10k rows and inform the user that they will have to perform the operation several times.
Per this hub thread.

Duplicate of #1740


I get metrics for all of the topics but I don't see all of the consumer groups

I get metrics for all of the topics (i see all of the topic names in the metrics list), but for some reason not for all of the consumer groups.

+1
I'm using:
Burrow v1.2.2
Kafka 2.3.1
Zookeeper 3.5.6
When I hit the v3 API I can see my kafka cluster
curl localhost:8000/v3/kafka/local {    "error":false,    "message":"cluster module detail returned",    "module":{       "class-name":"kafka",       "client-profile":{          "client-id":"burrow-lagchecker",          "kafka-version":"0.8",          "name":"",          "sasl":null,          "tls":null       },       "offset-refresh":10,       "servers":[          "kafka-kfk-0.dxlstreaming-kafka-headless.neweksdatabus.svc.cluster.local:9092",          "kafka-kfk-1.dxlstreaming-kafka-headless.neweksdatabus.svc.cluster.local:9092"       ],       "topic-refresh":60    },    "request":{       "host":"kafka--0-0-8--monitoring-b47f6bbcb-kvb5v",       "url":"/v3/kafka/local"    } }
But, when i try to list the consumers it prints out an empty list and i do have some consumers running.
curl localhost:8000/v3/kafka/local/consumer {     "consumers": [],     "error": false,     "message": "consumer list returned",     "request": {         "host": "kafka--0-0-8--monitoring-b47f6bbcb-kvb5v",         "url": "/v3/kafka/local/consumer"     } }
I'm assuming @avnerbarr only sees info about topics in his metric exporter because burrow can see the brokers, but cannot see any consumers.

Just saw there is no support for 2.3.0 or above yet #568.


KIM should be able to deprovision clusters

Description
Deletion of RuntimeCR should trigger the removal of a Kyma cluster. The RuntimeCR should be marked to be in "deleting" state until the cluster was completely removed. Only when the cluster was completely deprovisioned, the CR should also be deleted.
Force deletion feature in Gardener is per default enabled (see #103 ) and should avoid longer deletion cycles in Gardener.
AC:

[ ] Deleting a RuntimeCR triggeres the deprovisioning of an SKR cluster
[ ] While deleting, the RuntimeCR is indicating that it's deleting (e.g. by setting the status field accordingly)
[ ] RuntimeCR is only deleted when the deprovisioning succeeded/is completed.

*Relates to
#103

In current implementation, we decided to not process status of Gardener cluster during deleting state.
Because of that when deletion process fails the CR will remain in Pending deletion state forever.


Don't run tests when building a Windows release

This slows down the release builds and in the worst case scenario
causes a single job failing meaning we need to rerun the entire build.
Problems with tests will have been caught we'll before we start
building release binaries.
Thoughts @saper?

Not sure it's a good idea. master is the only place where all PRs really meet together. Apart from the (very rare) direct commits to master there is always a possibility of a bad merge.  The intent here is to skip tests on the release branch.


Bump for 2.4.6

This release includes about 20 bug fixes after the previous release, and also includes several security fixes
https://www.ruby-lang.org/en/news/2019/04/01/ruby-2-4-6-released/
Also, I am adding information related to EOL status of each version : https://endoflife.software/programming-languages/server-side-scripting/ruby

Just noticed this hasn't been merged in yet.  Is there a holdup?

Just noticed this hasn't been merged in yet. Is there a holdup?

No hold up other than competing priorities. Do note that we no longer recommend to our customer to use this image, so if our release schedule doesn't meet your needs, you might look to https://hub.docker.com/_/ruby
https://www.aptible.com/documentation/enclave/tutorials/faq/aptible-base-images.html


bad wifi  set db version  can not enter app

let config = Realm.Configuration(
// Set the new schema version. This must be greater than the previously used
// version (if you've never set a schema version before, the version is 0).
schemaVersion: UInt64(version),
        // Set the block which will be called automatically when opening a Realm with
        // a schema version lower than the one set above
        migrationBlock: { migration, oldSchemaVersion in
            // We haven’t migrated anything yet, so oldSchemaVersion == 0
            if (oldSchemaVersion < 1) {
                // Nothing to do!
                // Realm will automatically detect new properties and removed properties
                // And will update the schema on disk automatically
            }
    })

    // Tell Realm to use this new configuration object for the default Realm
    Realm.Configuration.defaultConfiguration = config

the code in didFinishLaunchingWithOptions
the wifi have not network

@luckycherry From this description it's not clear what your issue is - can you please use the issue template and provide more details?
Thanks!

Closing this issue due to no response. Feel free to reopen if additional information can be provided.


Auto ping/pong logs should be debug instead of info

https://github.com/crossbario/autobahn-python/blob/2466c2b4a666c49bb3ccd50502a3c49e07b378ec/autobahn/websocket/protocol.py#L852-L855
With the latest version of autobahn, my logs are being filled by auto ping/pong messages :)

uups. this should be a debug, not info level log message. well, we don't have CI tests for not logging;) anyways, I fix it.

ok, here:
https://pypi.org/project/autobahn/22.2.2/
https://github.com/crossbario/autobahn-python/tree/v22.2.2

Thanks!


Documentation/op-guide: remove grafana demo link

The dashboard was removed during Tectonic migration in AWS, while the Grafana still runs in GCP.
Screenshot should be good enough for now.
We can add it back when Grafana is fully migrated to Tectonic cluster,
which won't happen in the near future.

lgtm


Issues with data collection - supported?

Describe the issue
I'm experiencing several issues while running the SWE-bench data collection. I'm able to run get_tasks_pipeline.sh, however have the following issues, even when running on a supported repo (e.g., pallets/flask):

Versioning: Running get_versions.py often results in the error reference is not a tree <commit hash>.
Harnessing: The suggested validation.ipynb notebook does not exist, making it difficult to evaluate which scraped PRs have working tests. I can't seem to find which scripts sets the FAIL_TO_PASS and PASS_TO_PASS fields in each instance in my created dataset.
Missing Constants: There are missing values in constants.py for supported environments like pallets/flask (e.g. SPECS_FLASK has no config for version "1.0", "1.1", "3.0" etc)

Is there another branch or location that fully reproduces your dataset generation?
Suggest an improvement to documentation
No response

Seeems like a major change removeing the validation.ipynb and engine_validation.py was done here - https://github.com/princeton-nlp/SWE-bench/pull/142/files#diff-896819df1387fcab75ada7f5df54f4af5cc2d58bae1c2e287e3e1ac5f656fa3b
Not sure what script replaced it yet for producing the SWE-bench dataset (not running evaluation)

@john-b-yang Thanks for the response! Emailing you now.

@john-b-yang is there any update on re-adding the validation feature? I'm interesting in generating a new dataset, similar to the lite version of SWE-bench, but with a cutoff_date of 20240101, to get more recent PRs.


Multi-arch build: amd64, arm

Build for amd64, arm
ARM build: dapper make ARCH=arm rootfs produces ./dist/artifacts/rootfs.tgz which should be extracted into the root partition (formatted as ext4) of a Raspberry Pi SD card (just be sure to remove everything from that root partition before).
Make sure you add init=/init rwto the kernel boot params in cmdline.txt on Raspberry Pi SD card boot partition (formatted as FAT).

I'm on this train. Will help you with what I can.
BTW I'm porting kubernetes to ARM, ARM64 and ppc64le: kubernetes/kubernetes#17981

@luxas Thanks for your feedback! Can you please take another look at the code: I've added building a rootfs.tgz archive (see above for usage).

Okay, so two major-ish changes.

Don't pull docker from rancher/docker, but instead have build.conf reference a docker to download, just like before.
We shouldn't reference the HypriotOS kernel.  For ARM all I want to release right now is the rootfs.tar that does not have any kernel/firmware.  This will be a completely generic ARM userspace.  We later need to build a post step that combines rootfs.tar + board specific image + board specific kernel/firmware to produce an SD card image.  Honestly I'd like to see if we can join forces with @DieterReuter on this one and hopefully share some work.

rootfs without modules/firmware is unbootable:
ERRO[0002] Failed to create bridge docker-sys: operation not supported

And then it's
INFO[xxxx] Waiting for Docker at unix:///var/run/system-docker.sock

every second, forever.

Okay, not forever: it panics in ~5 minutes, probably because of the timeout waiting for system-docker to become available.

@imikushin of course it's not bootable without the modules/firmware.  They have to be added to the SD image

@ibuildthecloud I've separated rootfs.tgz and usrlib.tgz (which contains modules and firmware) in the last commit. So now you can run dapper make ARCH=arm rootfs usrlib and get whatever you want :smile:

@imikushin I'd rather not produce the usrlib.  Even with the usrlib the user still needs to take a series of steps to produce a bootable sd image.  So I do see much point to it and the usrlib is tied to a rpi.  I'd much rather for this release not refer to the hypriot kernel at all and just produce the rootfs.  As a convince for this release we can manually assemble a full sd image.  But the next release we need to automate that as a separate step but I want that to be more generic so we can target more boards.

Just got this working on an XU4 by using the rootfs alongside an existing bootloader, /boot and /lib/modules directories. Thanks for the work so far! :+1:

Awesome @djmaze! I'll try this too ASAP on a RPi 1 and 2.
I agree with @ibuildthecloud that the first RancherOS on ARM release should feature only a rootfs.tar.gz and alpha testers have to add e.g. the Hypriot kernel, /boot and /lib/modules directories.
Then we could discuss support for other types of boards and maybe arm64 :smile:

@imikushin I'll merge on one condition.  You absolutely promise that we will not maintain a os-config.yml and os-config_arm.yml going forward.  So next PR will consolidate these?

@ibuildthecloud Sure! I'll consolidate these in a next PR.

@imikushin ok

OK, got it partially working on a Pi 2.
It has some rough edges though: ~1GB size and boots in ~60s
However, it's very annoying to have it working but not be able to log in.
None of rancher/rancher, root/root, pi/raspberry, root/hypriot work.
@djmaze How did you log in?
@imikushin @ibuildthecloud ??

@luxas users and passwords should be defined in the rootfs and not in the kernel package, so there must be the Rancher defaults apply - nothing from Hypriot.

@DieterReuter Yeah, I know. But I had to test it anyway :)
And yeah, I used /boot/ and /lib/modules from latest Hypriot image

@luxas You need to add a cloud-config.yml to /var/lib/rancher/conf/ in the rootfs before booting the first time. That file should include the ssh_authorized_keys as described in the manual.

Btw, the image builders by hypriot help a lot in that. I used one adjusted for my XU4, replaced the rootfs tgz, adjusted the boot.ini and added the cloud config before building the final image.

Thanks @djmaze! Was only thinking about using my keyboard to the Pi, so didn't think about ssh at all. But now when I've added my computer to ssh, it works!! :smile:
Will try to run kubernetes on it now


Switching to opengl3_angle rendering backend fails to open projects in compatibility mode

Godot version
v4.2.beta.custom_build [b662d232a]
System information
Windows 10.0.19045 - GLES3 (Compatibility) - dedicated NVIDIA GeForce GTX 1650 (NVIDIA; <IP_ADDRESS>92) - Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (8 Threads)
Issue description
This has been happening on the latest artifact builds, but not on 4.2-beta3

The drivers are updated and the PC rebooted.
The build console seems to recognize OpenGL API on 3.3.0 and my GPU can run up to 4.6

I was planning to wait for beta4, as this could be due to different build settings, but decided to open the issue anyway, in case it's important. 👀
Steps to reproduce
The MRP's contents are of little importance. Instead, it's a project in compatibility rendering using opengl3_angle for Windows.
Minimal reproduction project
GPUParticles Compatibility Angle.zip

This has been happening on the latest artifact builds, but not on 4.2-beta3

Official builds use statically linked ANGLE, CI build does not, so a compatible libEGL.dll and libGLESv2.dll should be placed in the executable folder for it to work. You can build ANGLE from source or extract required dlls from the minimal CEF distribution - https://cef-builds.spotifycdn.com/index.html

Oh. . . I was right on thinking it was about the build, I just didn't know how.
Now it's working normally, thank you. 😄
I did not find any mention to Angle in the latest docs for building godot. Should I open an issue in godot-docs about that?

I did not find any mention to Angle in the latest docs for building godot. Should I open an issue in godot-docs about that?

Yes, docs weren't updated.
The relevant build flag is angle_libs=/PATH/TO/STATIC/LIBS, and pre-built static libs are available at https://github.com/godotengine/godot-angle-static/releases

Since the issue is pretty much solved, should I close this, or should it stay open for another reason?

Official builds use statically linked ANGLE, CI build does not, so a compatible libEGL.dll and libGLESv2.dll should be placed in the executable folder for it to work. You can build ANGLE from source or extract required dlls from the minimal CEF distribution - cef-builds.spotifycdn.com/index.html

Could we include those DLLs in the CI artifacts?


Unity Editor crash

Overview
After I've saved the code in Visual Studio, crashing back into the updated code in Unity, with some sporadic.Detailed error information please see the figure

Expected Behavior
don't crash
Actual Behavior
Editor crash
Unity Editor Version
Unity 2017.4.3.f1
Mixed Reality Toolkit Release Version
2<IP_ADDRESS>

Looks like an error from Unity's base XR Namespace for the interaction manager.
Do you have repro steps?

This happens sporadically with our project as well. If you have a project over a certain size, try clicking play 30-40 times in a row. As mentioned in the error, some kind of buffer gets filled up and forces Unity to restart. I think the issue is Unity-related and there is already a ticket submitted for it (has 2 votes last I checked).

Closed in favor of 2268, it has a bug report to unity attached.


[CRITICAL] No support to Grafana 8

HI, i'm reopening the issue because the other one was closed and there is no release solving the problem.
The original issue #91

@MaikiGirardi my PR is still under review. And honestly I don't have any idea how long it will take to merge it. In the mean time with every changes I am updating the build under release directory. You can directly download it and replace  plugins/oci-metrics-datasource/dist with the new dist from zip.

@chillaxd can you please share your Datasource configs right now and if i have to change CLI installation? After apply this new version i'm facing 404 when testing.

Hi @MaikiGirardi  sorry for late response. I have added the screenshot of the datasource configuration here.
For multi tenancies, currently plugin will require tenancies file path, which you can get in datasource configuration.
Format of the tenancies file will be
<tenancy_name>,<tenancy_ocid>
and please remember create the oci profile with <tenancy_name>
Please let me know if you need any further help

.

Sorry for the delay, i found my problem, my Grafana and OCI-CLI version was too old for those changes. After i upgraded for the last version on both it start working properly.
Right now, on my tests, i found some critical issues  that makes me wait. I don't know, do you want me to report those issues? If yes, where i can open those issues?
Thanks @chillaxd

@MaikiGirardi Sorry for late response. Please put the issues here as I am currently in enhancement mode for this plugin so I can so if I have already covered those or not.

@chillaxd, i put the issues i've found on the PR #106 . If it helps, please let me know. When did you will release this? There is any planned date?

@MaikiGirardi the latest 3.0.0 on Grafana marketplace(same as latest on a main branch here) supports Grafana 8, it has few additional minor updates too. Please use that.

I've tested the version 3.0.0 and the plugin starts working again on Grafana 8! Thx

@MaikiGirardi we regret to be late to update the docs...we will soon post it to Github and to the Grafana Marketplace too...BTW the new version has a few additional improvements .... fully qualified cmpt names and you will also see dimensions for each metric stream in UI

@mayurOciSA The time frame to release this bug fix was really bad. Please, in the future don't merge new features with bug fix as i could see that's the problem. I hope this plugin keep improving as i can see on PR #106 that are covering a lot of needs like support for alerts and multi tenant. And, maybe one day, remove the need OCI-CLI like other vendors.
Anyway, thanks right now i could update my grafana server properly.


Uncaught exception for C++ module

Although the documentation of inspect.getsource says

An OSError is raised if the source code cannot be retrieved.

When I do
import inspect, sys
inspect.getsource(sys)

I get a TypeError and not a OSError, thus generating the documentation with a C++ module fails (it did not for earlier versions).
Catching both TypeError and OSError here fixes the issue:
https://github.com/tox-dev/sphinx-autodoc-typehints/blob/01b3a1abeac063a5530b96b78252aa17a93f040c/src/sphinx_autodoc_typehints/__init__.py#L286

Can you provide a reproducible that generates a TypeError?

I can't provide the code I have an error with. I tried to replicate the error by adding a file foo.rst with
.. automodule:: sys
  :members:

I don't understand why it never calls inspect.getsource with argument sys. Any hints ?

I just ran into the same issue (I think). Our project is using pybind11 to build an extension module.
The error I got is:
Traceback (most recent call last):
  File "/home/simon/miniconda3/envs/scipp-developer/lib/python3.8/site-packages/sphinx/events.py", line 101, in emit
    results.append(listener.handler(self.app, *args))
  File "/home/simon/miniconda3/envs/scipp-developer/lib/python3.8/site-packages/sphinx_autodoc_typehints/__init__.py", line 498, in process_docstring
    type_hints = get_all_type_hints(obj, name)
  File "/home/simon/miniconda3/envs/scipp-developer/lib/python3.8/site-packages/sphinx_autodoc_typehints/__init__.py", line 307, in get_all_type_hints
    result = _get_type_hint(name, obj)
  File "/home/simon/miniconda3/envs/scipp-developer/lib/python3.8/site-packages/sphinx_autodoc_typehints/__init__.py", line 343, in _get_type_hint
    _resolve_type_guarded_imports(obj)
  File "/home/simon/miniconda3/envs/scipp-developer/lib/python3.8/site-packages/sphinx_autodoc_typehints/__init__.py", line 330, in _resolve_type_guarded_imports
    module_code = inspect.getsource(module)
  File "/home/simon/miniconda3/envs/scipp-developer/lib/python3.8/inspect.py", line 997, in getsource
    lines, lnum = getsourcelines(object)
  File "/home/simon/miniconda3/envs/scipp-developer/lib/python3.8/inspect.py", line 979, in getsourcelines
    lines, lnum = findsource(object)
  File "/home/simon/miniconda3/envs/scipp-developer/lib/python3.8/inspect.py", line 780, in findsource
    file = getsourcefile(object)
  File "/home/simon/miniconda3/envs/scipp-developer/lib/python3.8/inspect.py", line 696, in getsourcefile
    filename = getfile(object)
  File "/home/simon/miniconda3/envs/scipp-developer/lib/python3.8/inspect.py", line 659, in getfile
    raise TypeError('{!r} is a built-in module'.format(object))
TypeError: <module 'scipp._scipp.core'> is a built-in module

I locally tried the fix in #210 and it does solve the issue.
If it is useful, I can link to a code branch highlighting the problem, but it is far from a simple reproducer.

Our current solution is to stick to an earlier version (I don't recall which one exactly right now).

Thanks, I installed 1.14.1 and it works. 1.15.3 does not.


ready for 3.4.0 release

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 94.404%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1704

Relevant Lines:
1805

💛  - Coveralls

@stlehmann Hi, I believe I have made all the changes required here to make a release to PyPi to fix a few issues. In order toi upload the PyPi, do I just run the Github Action "Release Python Package"?

@stlehmann Hi, I believe I have made all the changes required here to make a release to PyPi to fix a few issues. In order toi upload the PyPi, do I just run the Github Action "Release Python Package"?

Great work. @chrisbeardy thank you very much for helping me maintaining this repository. Hopefully I'll find some more time to spare in the future to get more involved in the process again. In the meantime I'm more then happy to see the package being so well maintained by you :)
Yes actually the Github Action should start the release process. It could be that you get issues because github secrets are used to upload to PyPi with my credentials. But I propose you give it a try and see if it does what it should do.

@stlehmann thanks. I'll do my best with the time I have. I seem to have an issue making the release (PyPI saying its not accepting new users or projects I think). Can you try manually running the release action please and see if it's just because I'm running it with my account?

I had to create a PyPi API-Token for pyads before the upload worked. I stored it in the project secrets so it should work out-of-the-box for the next CI-triggered release, hopefully :)


hover effect for the icons in the contributors page

hover effect for the icons in the contributors page will make it look more good and cool , please assign this under jwoc 2024

Which icons? the circle within which the contributor's profile picture is present?

Which icons? the circle within which the contributor's profile picture is present?

Yes

Okay go for it!


How to configure pierrot to use the enterprise github instead of github

Is there a way to use the enterprise github url for fetching files from github. I ask this as GitHub API for Java supports enterprise github as well. If not there i would like to see if i can contribute to this.

Hi, the support is not there yet. If you would like to contribute then

Add new required properties to GithubConfiguration (enterpriseUrl, enterpriseOauthToken)
Use the properties when creating GitHub instance

Ok will take a look and try to raise the PR for this.

Great, thank you too


Can't select "Backup file" option in Restore dialog

SQL Operations Studio Version: master

Steps to Reproduce:

Open Restore dialog
Click on Restore from drop-down list
Click on Backup file

Expected: Backup file is selected
Actual: Nothing
Note: Backup file can be selected using keyboard DOWN arrow
Note that Backup file is not highlighted even though it's being hovered

*Note here's what Backup file should look like

@MattIrv could you please take a look at this issue?  thanks!