BigQuery: Pandas import errors

Hi, I am getting import errors for pandas which I am not even trying to use. Would probably make sense to throw a warning in these cases instead of crashing.

Specify the API at the beginning of the title: Bigquery

OS type and version:
OSX 10.13.2

Python version and virtual environment information:
2.7.12

google-cloud-python versions:

Name: google-cloud
Version: 0.22.0
Name: google-cloud-bigquery
Version: 0.29.0

Stacktrace if available

   from google.cloud.bigquery import Client as BigQueryClient
 File "/usr/local/lib/python2.7/site-packages/google/cloud/bigquery/__init__.py", line 35, in <module>
   from google.cloud.bigquery.client import Client
 File "/usr/local/lib/python2.7/site-packages/google/cloud/bigquery/client.py", line 39, in <module>
   from google.cloud.bigquery.dataset import Dataset
 File "/usr/local/lib/python2.7/site-packages/google/cloud/bigquery/dataset.py", line 22, in <module>
   from google.cloud.bigquery.table import TableReference
 File "/usr/local/lib/python2.7/site-packages/google/cloud/bigquery/table.py", line 25, in <module>
   import pandas
 File "/usr/local/lib/python2.7/site-packages/pandas/__init__.py", line 42, in <module>
   from pandas.core.api import *
 File "/usr/local/lib/python2.7/site-packages/pandas/core/api.py", line 10, in <module>
   from pandas.core.groupby import Grouper
 File "/usr/local/lib/python2.7/site-packages/pandas/core/groupby.py", line 50, in <module>
   from pandas.core.frame import DataFrame
 File "/usr/local/lib/python2.7/site-packages/pandas/core/frame.py", line 77, in <module>
   from pandas.core.series import Series
 File "/usr/local/lib/python2.7/site-packages/pandas/core/series.py", line 81, in <module>
   import pandas.plotting._core as gfx
 File "/usr/local/lib/python2.7/site-packages/pandas/plotting/__init__.py", line 11, in <module>
   from pandas.plotting._core import boxplot
 File "/usr/local/lib/python2.7/site-packages/pandas/plotting/_core.py", line 45, in <module>
   from pandas.plotting import _converter
 File "/usr/local/lib/python2.7/site-packages/pandas/plotting/_converter.py", line 8, in <module>
   import matplotlib.units as units
 File "/usr/local/lib/python2.7/site-packages/matplotlib/__init__.py", line 1100, in <module>
 File "/usr/local/lib/python2.7/site-packages/matplotlib/__init__.py", line 947, in rc_params
 File "/usr/local/lib/python2.7/site-packages/matplotlib/__init__.py", line 789, in matplotlib_fname
 File "/usr/local/lib/python2.7/site-packages/matplotlib/__init__.py", line 325, in wrapper
 File "/usr/local/lib/python2.7/site-packages/matplotlib/__init__.py", line 693, in _get_data_path_cached
 File "/usr/local/lib/python2.7/site-packages/matplotlib/__init__.py", line 689, in _get_data_path
RuntimeError: Could not find the matplotlib data files

Steps to reproduce
Hard to say, installed a package that depends on google-cloud-bigquery==0.29.0 but when I try to run it I get this import error

Code example
N/A

Using GitHub flavored markdown can help make your request clearer.
See: https://guides.github.com/features/mastering-markdown/

@thejens I'm going to go ahead and close this issue.  If you come across any more issues, please let us know.
I believe that the problem will be fixed for newer versions and possibly a pip install --upgrade would fix the problem.
@tswast if you think otherwise, please let me know Tuesday.  I wrote a except RuntimeError with warning, but I think it just unnecessarily complicates things.

I think it just unnecessarily complicates things.

My initial response would have been to move the imports into the to_dataframe() questions, but after discussing with @alixhami and @jonparrott, I also believe catching these errors is unnecessary.
The solution for this problem is for the user to either fix or remove their Pandas installation.

We could have a new file for pandas only functions, but it wouldn't solve this problem.  Just a suggestion if there might be other uses for it.


Need react version update

I was tried to use this package and got following error.
Element ref was specified as a string (RICC_main_container) but no owner was set. This could happen for one of the following reasons:

You may be adding a ref to a functional component
You may be adding a ref to a component that was not created inside a component's render method
You have multiple copies of React loaded
See https://fb.me/react-refs-must-have-owner for more information.
▶ 29 stack frames were collapsed.
./src/index.js
F:/GIT/PBIC/Designer_Tool_Sprint_2/designer_web/src/index.js:15
12 |
13 |
14 | const store = configureStore();

15 | ReactDOM.render(
16 |
17 |
18 |   ,
View compiled
▶ 6 stack frames were collapsed.
This screen is visible only in development. It will not appear if the app crashes in production.
Open your browser’s developer console to further inspect this error.

Then I went through the your code and identified you use react 15.6.2 and my version is 16.3.2. So it seems your package load react 15.6.2 and due to that this issue will happened.
So is it possible to update react version of this package. Thank you ..

Thanks.
I will update library next week.


Configurable LR schedulers

Updates the mlx_lm LoRA module's YAML configuration to include sections like the following:
schedule:
  join:
    boundaries: [101]
    schedules:
      - { name: linear_schedule,
          arguments: [0.0, 1e-5, 100] }
      - { name: cosine_decay,
          arguments: [ 1e-5, 100 ] }

and creates joined schedules using parameters specified in the configuration or single schedules if specified like so
schedule:
  cosine_decay:
    arguments: [ 0.1, 10 ]

The schedule names refer to those in mlx.optimizers.schedulers and their arguments are the same as those in the functions defined there.
Currently, mlx_lm hardcodes to using optim.Adam, but this configuration framework can be extended to also allow the optimizer to be specified to use others, such as SGD, for example.

Great one! @chimezie

@chimezie I think we can allow a scheduler config but let's keep it simpler for now. What you've built is very flexible but I think for most cases people don't need that much flexibility and would actually benefit from some useful constraints. I would provide the option to do a warmup and maybe the choice of schedule (e.g. cosine vs exponential) with arguments. So something like:
schedule:
  name: cosine_decay
  warmup: 100 # 0 for no warmup
  arguments: .... # get passed to scheduler

@chimezie I think we can allow a scheduler config but let's keep it simpler for now. What you've built is very flexible but I think for most cases people don't need that much flexibility and would actually benefit from some useful constraints. I would provide the option to do a warmup and maybe the choice of schedule (e.g. cosine vs exponential) with arguments. So something like:
schedule:
  name: cosine_decay
  warmup: 100 # 0 for no warmup
  arguments: .... # get passed to scheduler

It would be useful to also be able to specify the warmup minimum and have it default to 0 like so:
schedule:
    name: cosine_decay
    warmup: 100 # 0 for no warmup
    minimum: 1e-6 # 0 if not specified
    arguments: ...

Thoughts?

It would be useful to also be able to specify the warmup minimum and have it default to 0 like so:
What about;

warmup: 100 1e-1

If the second value is not set, it defaults to 0? If warmup is not set then no warmup is used.

It would be useful to also be able to specify the warmup minimum and have it default to 0 like so:
What about;

warmup: 100 1e-1

If the second value is not set, it defaults to 0? If warmup is not set then no warmup is used.

That causes the Yaml parser to interpret the argument to warmup as a string  instead of a float:
import yaml
from mlx_lm.lora import yaml_loader

In [1]: CONFIG_YAML6 = """
   schedule:
      name: cosine_decay
      warmup: 100 1e-1
      minimum: 1e-6
      arguments: [ 1e-5, 20 ] """

In [2]: config = yaml.load(CONFIG_YAML6, yaml_loader)
In [3]: config
Out[3]:
{'schedule': {'name': 'cosine_decay',
  'warmup': '100 1e-1',
  'minimum': 1e-06,
  'arguments': [1e-05, 20]}}

A separate key/value field would allow the Yaml parser to handle all the casting, etc.


add user configurable config to kaocha test runner

I would like to be able to pass a custom config map to the kaocha runner.
In my case, the projects I'm working on have standardized to using tests.edn for the CI configuration, and tests.local.edn for developer specific config that is not committed to git.
To add a slight monkey wrench, there is not always a tests.local.edn file in every project, so I'd like to be able to set something like this: (if (.exists (new java.io.File \"tests.local.edn\")) {:config-file \"tests.local.edn\"} {})

I've added a way to do this to develop you can try something like this!
let g:conjure#client#clojure#nrepl#test#call_suffix = "{:kaocha/color? false, :config-file (when (.exists (new java.io.File \"tests.local.edn\")) \"tests.local.edn\")"

Let me know what you think, not sure if I'm fully happy with it, maybe I should merge these maps and make it slightly more opinionated so you don't need to add that :kaocha/color? false 🤔

Oops, misclick. But I think this will be closed when I release, probably tomorrow morning?


Fix the tests creating indexes multiple times: [ECR-3347]

Overview
As the code iterated over a MultiSet from MultiMap#keys
with a key for each key-value pair, it created multiple
instances of some collections.

See: https://jira.bf.local/browse/ECR-3347
Definition of Done

[x] There are no TODOs left in the code
[ ] Change is covered by automated tests
[x] The coding guidelines are followed
[x] Public API has Javadoc
[x] Method preconditions are checked and documented in the Javadoc of the method
[x] Changelog is updated if needed (in case of notable or breaking changes)
[x] The continuous integration build passes

Coverage remained the same at 85.672% when pulling fde86bf32308dcbea5da3d5696d14a8f5f5a0e27 on dmitry-timofeev:fix-tests into 4aa9ae10035937a3c22010a76e2a80b423e21eed on exonum:master.

@skletsun I merged into master, merkledb can be created off it if it is not already.


Allow postMessage for :before, :after, :hover selectors

Currently we can not use postMessage for selectors which contain :before, :after, :hover, for example a:hover. This problem causes the customizer is hard to see change immediately.
I have did some changes to fix it. Please take a look at this PR.

It looks like there's something wrong and your code doesn't pass the phpunit tests.
To be more specific, this is the test that fails: https://github.com/aristath/kirki/blob/master/tests/test-kirki-scripts-customizer-postmessage.php#L26-L29
It should be returning the string containing the script and instead it's getting an array as seen on https://travis-ci.org/aristath/kirki/jobs/74279212#L352
I see you changed the names of some functions etc...
Could you please include a fix for the unit tests in your PR as well?

Hi @aristath,
Thanks for your reply!
Because I have to insert JavaScript and CSS in the footer, so I returned a array. Maybe we should rewrite the unit test to work with new change :)
Please take a look at it here: https://github.com/luanvuvt/kirki/commit/427e1850ce52926e6227d83f53793f9049fd0381#diff-0fc4d00a4dd8a0ad9a9a9cb4e32119caR76

@luanvu I've been going through all the PRs and issues and I saw this one again...
I'm sorry, I completely forgot about this!
Could you please update the PR so it doesn't conflict with the latest changes we made to the repo so that we may merge it?
Thanks!

Hi @aristath, I have just updated the PR to fix conflict. Please recheck it.

Hi @aristath,
Could you please check this PR?
Thanks!

The reason I haven't merged this yet is because I'm trying to understand what you're doing, and something just doesn't seem right.
Example:
on this line: https://github.com/aristath/kirki/pull/289/files#diff-8abb598b6325e38c3fb671fb128b0c2bR256 and line 264 just below that, it's clear that the new generate_css_by_fields method acceps ALL fields as the 1st argument.
However, when you call that function on https://github.com/aristath/kirki/pull/289/files#diff-0fc4d00a4dd8a0ad9a9a9cb4e32119caR47 and on line 67 on the class-kirki-scripts-customizer-postmessage.php file, you're sending a single field instead.
I mean... if all we want to do is allow using pseudo-elements, wouldn't we be able to do it by tweaking these lines https://github.com/aristath/kirki/blob/67b81801028e9b423bd5f4b46d5808be810e6f21/includes/class-kirki-scripts-customizer-postmessage.php#L49-L51 ?
We should be able to just check if we have a : character in the $js_vars['element'], and if we do then use jquery's .attr. Or am I missing something obvious?
I'm not that good when it comes to JS so I don't have the whole picture, it just seems like overkill.
If I'm mistaken then please do correct me, it's how we learn.

Hi @aristath,
In this PR, I don't use jquery's .attr to style of element. Intead of this I use a style element. Please take a look at simple example here for more details http://jsbin.com/wumaramumi/1/edit?html,output
About the new method generate_css_by_fields, because there are some places I have to generate CSS by a field, so I make a small change in this method to allow generate CSS of array of fields or a field only.
Hope this useful!

There were lots of issues, in fact the output stopped working altogether when in the customizer so I had to revert this merge.

Yes. We have tested this change in our themes but we don't see any problem. Maybe it does not fit to general case.


CGBitmapContext const updates and unit tests

Adds const keywords in implementation per review notes. Also, adds basic unit tests that will help for regression testing later. Interoperability of APIs with iOS is NOT tested for since underlying implementations are not Interoperable.

Hi @jparmentervf, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

@jaredhms is added to the review. #Closed

In CI build.

:clock1:


Filtermovie

Filtering with the options retrieved from the Quiz component

Filtering with the options retrieved from the Quiz component


Minor updates for new names, adds phones postprocess

[x] Updated Unreleased in CHANGELOG.md to reflect the changes in code or data.

This just contains some small changes now that we are using 'broad' and 'narrow'. I don't think we really need to change anything else. Apparently our phones table was broken, so I changed the links.
I added a postprocess script to the phones side just for the sake of consistency.
Closes #360.

I had one minor suggestion, but otherwise LGTM. Thanks for catching the issue with the links in the HOWTO.

FWIW that doesn't bother me.
On Thu, Apr 22, 2021 at 1:36 PM Lucas Ashby @.***>
wrote:

@.**** commented on this pull request.
In data/scrape/lib/generate_tsv_summary.py
https://github.com/kylebgorman/wikipron/pull/405#discussion_r618608995:

@@ -15,8 +15,8 @@
)

-def _wiki_name_and_transcription_level(ele: List[str]) -> str:

return ele[3] + ele[7]
+def wiki_name_filtered_and_path(ele: List[str]) -> str:

Perhaps, but then we'd be sorting by ISO code and get things like Irish
ending up next to German.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/kylebgorman/wikipron/pull/405#discussion_r618608995,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABG4OIS2P4NECNVE6AXNSLTKBNAHANCNFSM43LGZ7LQ
.

I think we can close it. The original goal of the issue (i.e.,wikipron/data/src reorganization) has been met, IMO — data/src has been thoroughly reorganized (and removed).
There is still one small outstanding issue related to the project of reorganization, namely the suggested renaming/reorganization of data/covering_grammar (@Othergreengrasses), but I don't think it directly relates to the discussion in #360

Okay. Add it to the PR description then, Lucas, if you could.
K
On Thu, Apr 22, 2021 at 11:53 PM Aidan Malanoski @.***>
wrote:

I think we can close it. The original goal of the issue (i.e.,
wikipron/data/src reorganization) has been met, IMO — data/src has been
thoroughly reorganized (and removed).
There is still one small outstanding issue related to the project of
reorganization, namely the suggested renaming/reorganization of
data/covering_grammar (@Othergreengrasses
https://github.com/Othergreengrasses), but I don't think it directly
relates to the discussion in #360
https://github.com/kylebgorman/wikipron/issues/360
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/kylebgorman/wikipron/pull/405#issuecomment-825367123,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABG4OKSVSDV3Y4RVJCVVN3TKDVNNANCNFSM43LGZ7LQ
.

I've hopefully sorted out our sorting problem. I can go through tomorrow and add some content to our temporary READMEs. I'll add the relevant closing statement then.

I didn't update the README in the covering grammar section as that directory is subject to change shortly.

Did you intend for this to be to a non-master branch? I just noticed that it is. Can I move it to master?

Yeah you can move it to master, it was just building on top of Aidan's changes but I think we're done renaming stuff now.


cleanup: move filter wrappers into Network namespace.

No functional changes.

Extracted from https://github.com/envoyproxy/envoy/pull/3217.
cc @mattklein123

I had to temporarily point example filter at my fork in order to unblock CI.
Please make sure this PR is not merged before https://github.com/envoyproxy/envoy-filter-example/pull/48.

Oh, one thing I should have mentioned, this change moves NetworkFilterFactoryCb and ListenerFilterFactoryCb to Network:: namespace, but I left HttpFilterFactoryCb in Server::Configuration::, since I didn't need it for https://github.com/envoyproxy/envoy/pull/3217.
Let me know if I should move HttpFilterFactoryCb into Http:: namespace as part of this PR.
@ggreenway @mattklein123


Building extension breaks history RDLC

1. Describe the bug
When developing a RDLC report layout with Visual Studio it is recommended to leave the modified file open while testing your changes. This way it was possible to easily revert any breaking changes with Visual Studio by using the Undo action. Currently this is no longer possible, building your extension after modifying a RDLC file seems to wipe your history. Using the Undo action does not lead to reversion anymore.
2. To Reproduce

Use any report with RDLC layout, for this scenarion created a simple example

 report 50100 MyReport
{
    UsageCategory = ReportsAndAnalysis;
    ApplicationArea = All;
    DefaultRenderingLayout = LayoutName;

    dataset
    {
        dataitem(Customer; Customer)
        {
            column(No_; "No.")
            {
            }
            column(Name; Name)
            {
            }
        }
    }

    rendering
    {
        layout(LayoutName)
        {
            Type = RDLC;
            LayoutFile = 'mylayout.rdlc';
        }
    }
}

Open RDLC file externally with Visual Studio.

Change RDLC layout and save

Use Undo (Ctrl+Z) and change is reverted

Now do the same but build (or publish) your extension after making the change in the RDLC layout (without closing the file!). Using Undo does not lead to any reversion.

3. Expected behavior
Retention of change history in Visual Studio when developing RDLC layouts. This was the case in C/AL development. Finding a breaking change in a complicated document report layout is very difficult, easy reversion to working version is critical for smooth RDLC development.
4. Actual behavior
See reproduction.
5. Versions:

AL Language: v10.2.719883
Visual Studio Code: 1.74.0
Visual Studio: Professional 2022 (64-bit) - Version 17.4.3
Business Central: NL Business Central 21.2 (platform 21.0.49939.50846 + application 21.2.49946.50869)
List of Visual Studio Code extensions that you have installed: None during reproduction.

Final Checklist
Please remember to do the following:

[x] Search the issue repository to ensure you are reporting a new issue

[x] Reproduce the issue after disabling all extensions except the AL Language extension

[x] Simplify your code around the issue to better isolate the problem

Just answer the question of reloading the rdlc file in Visual Studio with "No", then you can still undo. The modifications in the rdlc file when building the application aren't of any relevance.

Take you for your reply. I already suspected it had something to do with reloading, but in my case it does not seem to be optional. As in I do not get any question or other dialog which asks me to reload or not. Where does this difference in behaviour come from?

Maybe this helps: https://stackoverflow.com/questions/45741034/visual-studio-auto-reload-solution

Maybe this helps: https://stackoverflow.com/questions/45741034/visual-studio-auto-reload-solution

Thanks, this works. I do still think this behaviour is a bug, but at least there is a workaround.

This behavior is not a bug. In order to publish an RDLC layout or just to build the app, the AL compiler needs to modify the layout to insert some parameters and also the schema of the report dataset. This re-writes the entire RDLC layout.
When you open the RDLC layout in Visual Studio and we re-write the entire file, Visual Studio loses the history because it considers it to be a different file (reloading).  We can't avoid re-writing the file as that would mean that we would not be inserting the dataset in it and it would render incorrectly.
Thus this behavior is by design and the workaround to not reload from VS is the correct solution.


reusing an existing ID field in a connection leads to error: All fields provided to an @connection must be non-null scalar or enum fields.

Which Category is your question related to?
AppSync / GraphQL
Amplify CLI Version
4.12.0
What AWS Services are you utilizing?
AppSync, DynamoDB, Cognito, S3
Provide additional details e.g. code snippets
Given an existing model:
type Order
  @model
  @key(
    name: "ByUser"
    fields: ["userId", "createdAt"]
    queryField: "ordersByUser"
  )
  id: ID!
  …
  userId: ID
}

Why would the addition of a new connection like this
  user: User @connection(fields: ["userId"])

Lead to the error: All fields provided to an @connection must be non-null scalar or enum fields.
When adding the connection without the fields parameter, the generated orderUserId would have the same properties as the already existing userId, but it would work with the connection.

@AndreasEK  I ask myself the same question: why adding a connection require a non nullable field?

I read the replies so far as a temporary inconsistency, which hopefully will be resolved at some point.

+1 this is a major oversight and prevents a model from having optional connections

CodySwannGT  Yes really it's really painfull to deal with these kind of oversight.
Having optional connections is often necessary. Imagine I have an application to manage teachers, and each teachers can belongs to a classroom. Actually, how could i create a teacher not linked to a classroom yet? Should I specify a dummy classroomId in the connection field to bypass validation?

@hirochachacha The #1657 issue is related in the sense that it would resolve our problem but this is a separate issue and not a duplicate. This is simply two undocumented issues that result in a catch-22 and prevent basic usage of this framework.

You can't make a model's primary ID non-nullable because then you would need to set it on the client side during object creation, as opposed to leveraging AppSync's autogeneration. (#1657)

You can't use a connection for a primary ID if the ID is nullable (this issue).

Thus, you can't use a model's primary ID if you want to leverage AppSync's autogeneration.

Thus, you can't use appsync autogeneration for ID if your API uses the connection directive.

Yet another undocumented issue (notably, every single example from Amplify uses mandatory ID's without ever mentioning that that is, in fact, necessary) that prevents basic functionality and makes the amplify cli experience brutal. If you're running into this issue when creating your first schema, I highly recommend finding an alternative product

@ajhool I already stand corrected at https://github.com/aws-amplify/amplify-cli/issues/3275#issuecomment-579203618.

Hey, do we have any update on this issue or any valid workaround? It's an important requirement for my app to have optional connections, and simply using @connection without fields create some other problems for me.

Bump

I guess a workaround could be having a dummy instance of the type you need to connect to and create that connection when in theory it should be null.
Nonetheless this is a major feature that needs to be implemented ASAP.

I was creating a nested tree and need to have optional connections.

bump please, just running into this issue here

Same issue here, the API seems inconsistent on that point

To get around this issue, explicitly declare the amplify internally generated FK property as optional (make sure to use their naming convention so it maps the data correctly):
orderUserId: ID user: User @connection
The naming convention is: {camel-cased model name - order}{property name user}Id

@tomhirschfeld
To get around this issue, explicitly declare the amplify internally generated FK property as optional (make sure to use their naming convention so it maps the data correctly):
orderUserId: ID
user: User @connection

The naming convention is: {camel-cased model name - order}{property name with capital - User}Id
When this property has been explicitly declared, it now becomes available in queries, mutations and filters and can be used in @key directives.

Can you please link to the documentation where this is explained (provided it exists)? I tried what you proposed and it didn't work.

@raffibag I didn't find this in any documentation, but figured it out through trial and error. Can you share some code and what you're trying to achieve so I can help?

Thanks, @blydewright - I may have misunderstood the implications of your solution... I was assuming that if implemented correctly, you'd be able to access the association when calling the parent object. In my case (though I was able to figure out another solution that ended up working better for our project), I had two associations under a Plan model: app and bundle. In my code (under the Plan model) I originally represented these associations as:
appId: ID! app: App @connection(fields: ["appId"]) bundleId: ID! bundle: Bundle @connection(fields: ["bundleId"])
This, of course, caused the error that's the subject of this thread... So I adopted your strategy and tried:
orderAppId: ID app: App orderBundleId: ID bundle: Bundle @connection
The problem was when I tried creating the associations (using a GraphQL mutation), the parent object (Plan) returns null for the app and bundle objects.
Again, I may have totally misunderstood the expected outcome of your solution, but that's why I was asking for a link to the docs.

Hi @raffibag no problem :) We're all trying to figure this out with limited documentation and examples since it's so new!
Glad to here you sorted out a solution. Perhaps it may help to point out a few things in your example code above:

Your orderSparkId and orderWidgetId fields would only work if the model they reside in is called Order. But based on what you described, they should be planSparkId and planWidgetId. The rest of your implementation looks good.
Creating/updating by passing the planSparkId or planWidgetId is the only way I know of that will allow the underlying model to persist the change. The internal resolvers (created due to the @connection directive), will take care of building the appropriate widget and spark data for the graphql payload.
Setting things up in this way (using planWidgetId and planSparkId) is only necessary when needing OPTIONAL relations. Had spark and widget been mandatory at the time of creating the model, you could have stuck to your original sparkId: ID! implementation

Does this help and make sense?

Absolutely, makes sense @blydewright. Thanks for the explanation! I went back and tried it out and it worked perfectly - was able to get the optional associations to show up simply by writing the respective ID to the parent model. I didn't read the previous posts closely enough and assumed "order" was an Amplify directive (or something like that).
Hopefully this gets documented, as my concern now is that any breaking changes will likely not get relayed to those who used this as a workaround / solution.

Glad it works :) I don't believe that this "workaround" will result in future errors, unless the amplify team change the way they internally name relational IDs. We're simply plugging into their way of doing things to accommodate optional relations which in my opinion should be catered for when defining your own foreign key fields: i.e. using widgetId: ID (without !) and widget: Widget @connection (fields: ["widgetId"]).
Good luck with your development!

Oh boy, this is a scary situation as any changes down the road will invalidate my current data.
Sometimes I really regret using Amplify, other times I think "oh this is seriously cool" But I certainly shouldn't have used it in a production environment
!

Yep just hit this, too. +1.

A dirty way around this is to just provide non-existing IDs for the required ID fields that are null.
createPlan {
  widgetID: "thisWidgetIDneverExists"
  sparkID: "thisSparkIDneverExists"
}

This (surprisingly) does not cause an error. And when you query Plan, the connections will return null.

The naming convention is: {camel-cased model name - order}{property name with capital - User}Id

Hi @blydewright , I'm trying to implement your solution, I'm halfway there. I am discovering the internals of Amplify right now, created a schema from the Amplify admin UI, and when doing this way, the ids are camel-cased then caps ID, eg: doctorID, as opposed to doctorId.
Am I missing something? You can see my attempt at implementing your idea in Appointment with an optional patientID field, and patient: Patient @connection.
type Appointment
    @model
    @aws_iam
    @auth(rules: [{ allow: owner }])
    @key(name: "byPatient", fields: ["patientID"])
    @key(name: "byDoctor", fields: ["doctorID"]) {
    id: ID!
    start: AWSDateTime!
    end: AWSDateTime!
    doctorID: ID!
    patientID: ID #This is where I'm trying to implement your idea
    doctor: Doctor @connection(fields: ["doctorID"])
    patient: Patient @connection
}

type Patient
    @model
    @aws_iam
    @auth(rules: [{ allow: owner }])
    @key(name: "byOrganization", fields: ["organizationID"]) {
    id: ID!
    legacyPatientId: String
    legacySystem: String
    firstName: String
    Appointments: [Appointment]
        @connection(keyName: "byPatient", fields: ["id"])
    organizationID: ID!
}

It lets me create Appointments without specifying patientID, however, querying the list of appointments returns an empty patient even when I provided the patientID during the creation of the appointment:
{
  "data": {
    "listAppointments": {
      "items": [
        {
          "id": "a778269e-f504-4828-9881-03312d311fef",
          "start": "2021-01-06T09:00:00Z",
          "end": "2021-01-06T11:00:00Z",
          "doctorID": "5d7a1734-a317-471e-a470-62dc6479f184",
          "patientID": "95e97098-dbc8-41b8-ba73-b8c66c479b99",
          "owner": "8bb20a0e-6063-43e1-b344-bc55c7cbdfe7",
          "report": null,
          "note": "1er rdv",
          "patient": null
        }
      ]
    }
  }
}

Not sure what I'm doing wrong, thanks in advance!

The naming convention is: {camel-cased model name - order}{property name with capital - User}Id

Hi @blydewright , I'm trying to implement your solution, I'm halfway there. I am discovering the internals of Amplify right now, created a schema from the Amplify admin UI, and when doing this way, the ids are camel-cased then caps ID, eg: doctorID, as opposed to doctorId.
Am I missing something? You can see my attempt at implementing your idea in Appointment with an optional patientID field, and patient: Patient @connection.
type Appointment
    @model
    @aws_iam
    @auth(rules: [{ allow: owner }])
    @key(name: "byPatient", fields: ["patientID"])
    @key(name: "byDoctor", fields: ["doctorID"]) {
    id: ID!
    start: AWSDateTime!
    end: AWSDateTime!
    doctorID: ID!
    patientID: ID #This is where I'm trying to implement your idea
    doctor: Doctor @connection(fields: ["doctorID"])
    patient: Patient @connection
}

type Patient
    @model
    @aws_iam
    @auth(rules: [{ allow: owner }])
    @key(name: "byOrganization", fields: ["organizationID"]) {
    id: ID!
    legacyPatientId: String
    legacySystem: String
    firstName: String
    Appointments: [Appointment]
        @connection(keyName: "byPatient", fields: ["id"])
    organizationID: ID!
}

It lets me create Appointments without specifying patientID, however, querying the list of appointments returns an empty patient even when I provided the patientID during the creation of the appointment:
{
  "data": {
    "listAppointments": {
      "items": [
        {
          "id": "a778269e-f504-4828-9881-03312d311fef",
          "start": "2021-01-06T09:00:00Z",
          "end": "2021-01-06T11:00:00Z",
          "doctorID": "5d7a1734-a317-471e-a470-62dc6479f184",
          "patientID": "95e97098-dbc8-41b8-ba73-b8c66c479b99",
          "owner": "8bb20a0e-6063-43e1-b344-bc55c7cbdfe7",
          "report": null,
          "note": "1er rdv",
          "patient": null
        }
      ]
    }
  }
}

Not sure what I'm doing wrong, thanks in advance!

Thanks @blydewright
Your solution works for me.
me too was wondering what happens if only use @connection without any arguments (https://github.com/aws-amplify/amplify-js/discussions/7593)
The doc given an example like this:
type Project @model {
  id: ID!
  name: String
  team: Team @connection
}

type Team @model {
  id: ID!
  name: String!
}

But after I saw your solution, I think the doc's example code should be this???
type Project @model {
  id: ID!
  name: String
  team: Team @connection
  projectTeamId: ID
}

type Team @model {
  id: ID!
  name: String!
}

I'm not should if the doc's example will work(not tried yet),
There is no description in the doc..
Hope the Amplify team put this in the docs..

Thanks @blydewright
Your solution works for me.
me too was wondering what happens if only use @connection without any arguments (https://github.com/aws-amplify/amplify-js/discussions/7593)
The doc given an example like this:
type Project @model {
  id: ID!
  name: String
  team: Team @connection
}

type Team @model {
  id: ID!
  name: String!
}

But after I saw your solution, I think the doc's example code should be this???
type Project @model {
  id: ID!
  name: String
  team: Team @connection
  projectTeamId: ID
}

type Team @model {
  id: ID!
  name: String!
}

I'm not should if the doc's example will work(not tried yet),
There is no description in the doc..
Hope the Amplify team put this in the docs..

@yaquawa no problem :)
You can use the structure as the docs describe without issue. Internally, a field called projectTeamId will automatically be created for the mapping to exist. The only real purpose for manually declaring that field (in an optional @connection relationship), was if you, like me, want the field to have a specific name so that you can refer to it in some way. I would refer to the field explicitly for defining @keys and/or query filtering or other use cases in my app. From my experience, you can only do this if the field is explicitly declared.
If you don't need to refer to the @connection field in any way, you can just define your @model in the way the docs describe.

@yaquawa no problem :)
You can use the structure as the docs describe without issue. Internally, a field called projectTeamId will automatically be created for the mapping to exist. The only real purpose for manually declaring that field (in an optional @connection relationship), was if you, like me, want the field to have a specific name so that you can refer to it in some way. I would refer to the field explicitly for defining @keys and/or query filtering or other use cases in my app. From my experience, you can only do this if the field is explicitly declared.
If you don't need to refer to the @connection field in any way, you can just define your @model in the way the docs describe.

@blydewright Thanks for your kindly explanation! Hop the team can fix this issue too..!

@blydewright Thanks for your kindly explanation! Hop the team can fix this issue too..!

Nullable connection fields are now supported in the latest version of the CLI. Please upgrade to try it out!

@edwardfoyle yee haw! thanks!

Nullable connection fields are now supported in the latest version of the CLI. Please upgrade to try it out!

@edwardfoyle I just submitted #558 because in Flutter I'm still having issues with nullable connection fields.


feat: Add configurable frame id prefix

In order to be able to properly handle (e.g. visualize) a multi robot scenario (where multiple voraus.core instances and bridges are running), one need the ability to distinguish between the coordinate systems of the different robots.
This change introduces an environment variable (FRAME_ID_PREFIX) to solve that problem.
The default value defined in the compose file is robot1, meaning that for example for the base_link coordinate system, the resulting frame_id is now: robot1_base_link.

I have not had time to look into this, just wanted to leave this here for now:
Whether someone is proficient in a specific field does IMO not influence the usefulness of PRs greatly. Either the code author or the reviewer learns something, ideally both.
Asking questions in PRs is a great way to have the answers to them near the relevant context and can be of great use to others a few weeks/months/years down the road.
Do never hesitate to ask.


Improve PageSpeed

Improve the PageSpeed of the Animate-A-Name website: https://animate-a-name.tk/.

Check the current situation: https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fanimate-a-name.tk%2F

To do list:

[ ] Fix "above the fold" issue
[ ] Fix render blocking for JavaScript files
[ ] Fix render blocking for CSS files

Hi, I would like to check this out. Any ideas on how I would test this?
I'm thinking that I would have to host the page somewhere else (most likely github page) and run the tool with that host.

@tyricec Ok. The source code is available here: https://github.com/SuriyaaKudoIsc/animate-a-name.

Helpful resources

To fix the "above the fold" issue use this tool: https://jonassebastianohlsson.com/criticalpathcssgenerator/
To fix render blocking for JS files read: https://varvy.com/pagespeed/render-blocking.html
To fix render blocking for CSS files read: https://varvy.com/pagespeed/render-blocking-css.html

Found out that the way to test is to use a tunnel app such as ngrok. Pretty cool.


Undocumented change in 4.0: append element with class name

Hello,
while porting my code from v3 to v4, nothing was working without error until I found out that you cannot set the class name in the append/insert function anymore.
Example:
v3:
this.xAxisElement = this.axesArea.append('g.axis.x')
    .attrs({
        transform: `translate(${0}, ${this.internalHeight})`
    })
    .call(this.xAxis);

v4:
this.xAxisElement = this.axesArea.append('g')
    .attrs({
        'class': "axis x",
        transform: `translate(${0}, ${this.internalHeight})`
    })
    .call(this.xAxis);

And this fails totally silently, which is not good !

This is documented in the release notes, but I will check and try to make
it more explicit.
The multi-value map methods have been removed from the default bundle. If
you want them, you can use the d3-selection-multi module.
https://github.com/d3/d3-selection-multi
As for calling selection.append with shorthand syntax for setting classes
on the created elements: that has never been supported in D3, so you must
be using a convenience module such as d3-jetpack. I am not the maintainer
of that module, so I am not sure whether it is compatible with 4.0 or
whether it needs an update. There’s a chance it still works but it could
probably also use an update (at least to adopt the new module pattern).
On Thu, Jun 30, 2016 at 8:21 AM Olivier Combe<EMAIL_ADDRESS>wrote:

Hello,
while porting my code from v3 to v4, nothing was working without error
until I found out that you cannot set the class name in the append/insert
function anymore.
Example:
v3:
this.xAxisElement = this.axesArea.append('g.axis.x')
.attrs({
transform: translate(${0}, ${this.internalHeight})
})
.call(this.xAxis);
v4:
this.xAxisElement = this.axesArea.append('g')
.attrs({
'class': "axis x",
transform: translate(${0}, ${this.internalHeight})
})
.call(this.xAxis);
And this fails totally silently, which is not good !
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/d3/d3/issues/2877, or mute the thread
https://github.com/notifications/unsubscribe/AAOEjXKyNde1hBs5dxQpUcozJyhNx5wzks5qQ97ogaJpZM4JCRox
.

Ahah my bad sorry, I used to have d3-jetpack for so long that I didn't even know that this wasn't some part of D3, and I removed jetpack when I updated to v4.0 ! (Man, I miss the .translate method so much!!)
Thanks then !
As for the multi value map, I'm aware of that, no worries !


Filter data from promise instead of array

is there a way to get the items array from a promise function?
What i'm trying to do is get the search term from ionFilterBar and call my backend server to get the the array that i need to pass to items array.
Thanks

$scope.showFilterBar = function(){
filterBarInstance = $ionicFilterBar.show({
items: $scope.items,
update: function (filteredItems, filterText) {
filterText is what you are looking for may be.

Update function Called after the items are filtered I don't think it would work.
Thanks anyway.

I think the items will have to contain all the items to be filtered prior to, yes and then the update function will be have the filteredItems.


Allow passing of parameters/data to command

Thanks!

Great change, will pull it now.

Thanks, by the way I tested it with sunroof controls:
def trigger_sunroof(c, car, state):
logT.debug("Setting sunroof to %s for %s", state, car)
for v in c.vehicles:
if v["display_name"] == car:
cmd = {"state": state}
res = v.command("sun_roof_control", data=cmd)
logT.debug("Garage door trigger: %s", res)
return

The change made sense, and your code was clean.  Appreciated!

No problem. I mentioned the library in a post here:
http://www.teslarati.com/tesla-api-controlling-model-s-model-x/
Thanks again.


Create sqitch tag for policyfile API tables

What it says on the tin. Creates a 'policyfile-api-tables' tag in sqitch so we can tell partybus to upgrade the schema.

@chef/lob

:+1:

:+1:


Hosted Fields are not working on IE 11 browser

I am using Braintree 3.19 for hosted fields.
Below file is throwing a javascript error Object.keys: argument is not an Object, hence hosted fields are not loading in IE 11 browser.
https://assets.braintreegateway.com/web/3.19.0/html/hosted-fields-frame.min.html

Is it still not loading when using the latest version, 3.32.1?

@crookedneighbor
It was happening because of the customs styles were having CSS3 properties.
It worked after removing it.


Kotest plugin does not detect custom or inherited test specs

The kotest plugin does not detect tests that use from custom or inherited specs. Minimal example:
class ScenarioSpec : BehaviorSpec()

MyUnitTest : ScenarioSpec() // Not detected by kotest
I cannot run MyUnitTest as an individual test (no right click context menu) and no icons are shown in the gutter. This issue also affects users creating their own custom specs when using this plugin.
I would expect kotest to detect and work with any test that inherits from the Spec abstract class.

There is a new plugin release pending approval by Jetbrains (they have to approve each upload) that will fix this.
Should be approved by Tuesday.

The new plugin has been released and this is working now


HealthCheck returns 500 on unhealthy result

The current version of dropwizard that I am using 0.7.1.
If you write a HealthCheck that is healthy then the servlet returns a 200 code, which is fine.
If there is an unhealthy result then the servlet returns with a 500.
The problem is that a 500 indicates an "Internal Server Error" whereas I have a requirement that it should return a 503 meaning "Service Unavailable".
I think the 503 is a more appropriate response code than a 500, because at the moment I cannot tell the difference between a severe server issue (which is returning a 500) and a unhealthy service which maybe operational with restrictions (which are made clear in the HealthCheck response text).

Internally we use HealthCheckServlet from the Dropwizard Metrics project.
I would advice to open a feature request there to add an attribute to the HealthCheckServlet to customize a response code of a failed health check.
If it's done, we will be happy to support it in the server YAML configuration.

Any updates on this?

Perhaps refer to https://github.com/dropwizard/metrics/issues/766, seems stalled there as well.


consumer: backoff strategies

refactoring of the work in #123
RFR @jehiah

code looks good (Aside from integration test failures)

updated

LGTM

:hammer:

It nice be beneficial to document that the code calls setConfig so that implementors can also use the function, the same way flag does IsBoolFlag.

@twmb I made those explicitly private, I don't want others relying on that method/interface/etc.  My expectation is that user-implemented BackoffStrategy would use their own parameters/config.


remove trusted types on empty string

Removed trustedTypes because this created issues in HN-Skjema when rendering empty translations in sidebar

Bra jobba Ruben 😊


Timesheet - 02/04/2021 - Mr. K

Task 1
Worked on Download Wallet Page Hifi design.
Proof of Work

https://www.figma.com/file/dniKTujBGiZmRha4OrtCOT/Download-Wallet?node-id=1%3A10

Time Spent
2.0 hours

Task 2
Worked on FAQ Handoff, Core, User Flows, Specs, states.
Proof of Work

https://www.figma.com/file/C22D4Et2I0AIE0n8QwBDMm/FAQ?node-id=152%3A3508

Time Spent
2.0 hours

Total Time Spent
4.0 hours
Account Number
c93ee24b89991a1438b45444cf06e5bb167ed1796d54a800174def4480f98ed0

Approved

Approved


feat: add @ts-nocheck option

Description
Add a new config option to enable adding // @ts-nocheck on top of generated type file.
Related #5073
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
I have added tests for this.
Checklist:

[X] I have followed the CONTRIBUTING doc and the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[X] Any dependent changes have been merged and published in downstream modules

Further comments
I didn't enable this by default since this can potentially be breaking for projects which enable ESlint ban-ts-comment. For future breaking release we can consider making this as default but personally think this should be kept opt-in.

closing this see: https://github.com/dotansimha/graphql-code-generator/issues/5073#issuecomment-1174027572


Kodi fails to build because of missing "EGL/eglextchromium.h"

Steps To Reproduce
Steps to reproduce the behavior:

add kodi to environment.systemPackages list in configuration.nix
run nixos-rebuild switch

Build log
...
[  4%] Built target pack-skins
[  4%] Built target crossguid
[  4%] Building CXX object build/network/httprequesthandler/python/CMakeFiles/network_httprequesthandlers_python.dir/HTTPPythonInvoker.cpp.o
[  4%] Building CXX object build/network/httprequesthandler/python/CMakeFiles/network_httprequesthandlers_python.dir/HTTPPythonWsgiInvoker.cpp.o
[  4%] Linking CXX static library network_httprequesthandlers_python.a
[  4%] Built target network_httprequesthandlers_python
[  5%] Building CXX object build/cores/RetroPlayer/process/X11/CMakeFiles/rp-process-x11.dir/RPProcessInfoX11.cpp.o
[  5%] Linking CXX static library rp-process-x11.a
[  5%] Built target rp-process-x11
[  5%] Building CXX object build/cores/VideoPlayer/Process/X11/CMakeFiles/processX11.dir/ProcessInfoX11.cpp.o
[  5%] Linking CXX static library processX11.a
[  5%] Built target processX11
[  5%] Building CXX object build/windowing/X11/CMakeFiles/windowing_X11.dir/GLContextEGL.cpp.o
In file included from /build/source/xbmc/windowing/X11/GLContextEGL.cpp:16:
/build/source/xbmc/windowing/X11/GLContextEGL.h:16:10: fatal error: EGL/eglextchromium.h: No such file or directory
   16 | #include <EGL/eglextchromium.h>
      |          ^~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [build/windowing/X11/CMakeFiles/windowing_X11.dir/build.make:76: build/windowing/X11/CMakeFiles/windowing_X11.dir/GLContextEGL.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:5054: build/windowing/X11/CMakeFiles/windowing_X11.dir/all] Error 2
make: *** [Makefile:146: all] Error 2
error: builder for '/nix/store/6g0ljp50j9y7mfs8i4lmli2lspiv6mx1-kodi-19.5.drv' failed with exit code 2
error: 1 dependencies of derivation '/nix/store/q7ngwycy36cm2zjyp9hr6x21gqisvg3s-system-path.drv' failed to build
error: 1 dependencies of derivation '/nix/store/h0q80zrc3gbgbs2a4yj7kkd2yw4818mz-nixos-system-nixTest-23.05pre443927.6dccdc45851.drv' failed to build

Additional context
Tried on two nixos machines, both on unstable channel.
Notify maintainers
@aanderse
@cpages
@edwtjo
@minijackson
@peterhoeg
@sephalon
Metadata
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.86, NixOS, 23.05 (Stoat), 23.05pre443927.6dccdc45851`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.12.0`
 - channels(root): `"nixos"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

https://github.com/NixOS/nixpkgs/pull/210941


WIP: migrate to nox, parallel tests, revamp test infra

Description
[To be added]
Closes #631 and related to #630

I now see why the PyPy tests were taking a long time – SciPy is being built from the source distribution because it doesn't publish wheels for PyPy, while NumPy does, of course (hence I'm myself answering the question I had). To keep CI time low, I can add another nox session for PyPy.

It looks like some of the tests have not been entirely deterministic, and failures with differences in precision between macOS Intel vs M-series devices were being reported (only in CI, though, I didn't face any of them locally). Setting a fixed random seed seems to have resolved the problem. This PR enables testing against both Intel and ARM macOS platforms, which we can keep until Intel devices surpass their EoL.

I have also added tests against NumPy and SciPy nightlies. Both of them support Python 3.10–3.13, which explains the failure across platforms for Python 3.8 and 3.9. We will be dropping 3.8 sometime soon in October anyway, but in the meantime, we could explore ways to make them fail more gracefully somehow or perhaps limit our nightly testing against the Python versions that are supported or the latest Python version. Please let me know your thoughts here.

Thanks for going through the changes, @fjosw! After all, nox is essentially the same as tox, but the Pythonic API might have made it at least slightly easier to read and maintain your own sessions, I hope!
I'm not sure if I have a robust answer for how robust the nightly tests will be – I think it depends a lot on our availability to ensure that we can land fixes at the right time since breakages will be critical to our users. At the same time, if we implement an upper pin on NumPy, it could, in rare circumstances, conflict with our ability to run the nightly tests, too. Say, if we have a pin on NumPy, say, <2.4, and NumPy 2.4.0-dev wheels get published in the nightly indices, we won't be able to install those wheels because the dependency resolution will fail with an unsatisfied requirement. If we bump the pin to NumPy <2.5, we run into the risk of having a new version of NumPy release on PyPI sometime later and breaking our code (if we aren't able to notice and fix it in time). It is a very low-risk situation overall, though, since we are both actively making changes to the repository, plus, NumPy makes it easier for us by deprecating things with warnings at least two releases before they get removed, and we as downstream maintainers are urged by them to try out the (one, and in some cases, two) release candidates once and when they are available.
However, without a robust refactoring of the original code, we can expect that there will be problems in the coming months and years. For example, if we see that something breaks, say, in NumPy 2.3.0 in their nightly wheels when we are in the NumPy 2.2.0 stable stage, we'll need to add some code patterns similar to this:
if _np.lib.NumpyVersion(_np.__version__) >= "2.3.0":
    # some logic
elif _np.lib.NumpyVersion(_np.__version__) >= "2.2.0" and _np.lib.NumpyVersion(_np.__version__) < "2.3.0":
    # some other logic
else:
    # yet some more logic

which are more code smells than code patterns, and will surely not be maintainable for us. At the same time, we don't want a lot of reds to appear in our CI either (and not too many if they do). Moreover, it is too early to support NumPy>2, as we discussed in https://github.com/HIPS/autograd/pull/628#pullrequestreview-2255629293.
With that extra context, I'm open to more suggestions on how we can improve our testing, since I'm out of ideas :) We still need to add some testing against the minimum supported NumPy version (1.X) and decide on a lower bound, which I feel can be solved using uv pip install --resolution lowest (see https://docs.astral.sh/uv/concepts/resolution/#lower-bounds). I will be doing it in another PR, of course.
I just triggered CI again with the updated config, and while I can disable the current nightly tests for Python 3.8 and 3.9 since they don't have wheels (we'll drop 3.8 soon in October, anyway), I wonder if you would have suggestions on actual test failures? It could be a NumPy bug or a bug in our own codebase, but I'm not confident about it. I thought it was flaky and re-triggered that test in CI, but that did not seem to help, it fails with the same values.

In d54683477e790a0943abdedefa88245ebdb5eec0, I've disabled the nightly NumPy tests for now, since you've already approved the PR and nothing else is blocking it. I'll merge this for now, and open a new PR to track re-enabling the nightly tests to look at the PyPy Windows failure there. An answer to the above comment on a proposition for our policies would be appreciated, and thank you for the review here, @fjosw!


Assertion failure in MIR

Hi,
I am hitting an assertion failure in MIR:
wrong destroy for uint8_travi: /home/dylan/github/mir/mir-varr.h:22: mir_var_assert_fail: Assertion `0' failed.

Program received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51      ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) where
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x00007ffffe840801 in __GI_abort () at abort.c:79
#2  0x00007ffffe83039a in __assert_fail_base (fmt=0x7ffffe9b77d8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n",
    assertion=assertion@entry=0x81527f7 "0", file=file@entry=0x8153188 "/home/dylan/github/mir/mir-varr.h",
    line=line@entry=22, function=function@entry=0x8154f80 <__PRETTY_FUNCTION__.2808> "mir_var_assert_fail")
    at assert.c:92
#3  0x00007ffffe830412 in __GI___assert_fail (assertion=0x81527f7 "0",
    file=0x8153188 "/home/dylan/github/mir/mir-varr.h", line=22,
    function=0x8154f80 <__PRETTY_FUNCTION__.2808> "mir_var_assert_fail") at assert.c:101
#4  0x00000000080a83a7 in mir_var_assert_fail ()
#5  0x00000000080ab27c in VARR_uint8_tdestroy ()
#6  0x00000000080c838d in machine_finish ()
#7  0x00000000080bd288 in code_finish ()
#8  0x00000000080afcf0 in MIR_finish ()
#9  0x0000000008087fe6 in raviV_close (L=0x858a280) at /home/dylan/github/ravi/src/ravi_mirjit.c:194
#10 0x0000000008042d64 in close_state (L=0x858a280) at /home/dylan/github/ravi/src/lstate.c:280
#11 0x000000000804360c in lua_close (L=0x858a280) at /home/dylan/github/ravi/src/lstate.c:426
#12 0x00000000080195b3 in main (argc=3, argv=0x7ffffffee098) at /home/dylan/github/ravi/src/lua.c:637

I will add any more information I can obtain.

Thank you for reporting this, Dibyendu.  The assert raises when we destroy variable array repeatedly.
I looked at the code and it seems that the global state was not removed completely (there is still one global varr outside the context).  So if you are using more one context, it might happen.
I'll fix this on this week.

I think I am only using 1 context but I will check if somehow multiple are being created.

I've removed the found global variable.  Here is the patch
https://github.com/vnmakarov/mir/commit/bbc8fc4b8a4163e906e5a1959eddb55174c526c3

@vnmakarov Thank you I will apply and retest and report back.

@vnmakarov Confirm this issue appears to be fixed by your patch.


Fix broken cherry-pick of rsaz_exp_x2.c bug fix [3.0]

Unfortunately the rsaz_exp_x2.c is slightly different in 3.0 in that it still needs the ALIGN64 macro.
This fixes CI failure on 3.0 so it is urgent.

@mattcaswell @paulidale do you agree with urgent?

Yes

Yes.

Merged.


Block library

Start with static blocks - variations of Columns block

Columns block added https://main--phoenix--aemsites.hlx.page/tools/sidekick/library.html?plugin=blocks


Fix for updates with multiple users

I know you just made a release, but I found a bug in the change I made that only happens when multiple users are present, so I didn't catch it. Sincerest apologies, I should've done more testing before committing.
This fix makes it such that only the owner of the message will update the dorako-ux flags on it. Without this, every user except the one who made the message will see a "[user] does not have permission to update ChatMessage" error banner if a message is updated.

No worries, thanks for the fix.


Update tooling versions

Some of the tools installed in here a few years out of date. kube-score for example installs a version from Jan 23, 2021 which only supports Kubernetes <1.21.

@FalconerTC  thanks for the issue! I've updated default tool vesrions https://github.com/yokawasa/action-setup-kube-tools/pull/44
Please check release versions too https://github.com/yokawasa/action-setup-kube-tools/releases


Origin address sometimes does not show the input address in the input transaction json

The Input address shows in the testnet explorer but sometimes it doesn't in the cardano-wallet transaction json.
The first image shows the input address for transaction id: 0e9fb584d12bf70964d54a7ab26ddbe3e6a301b929767662a2b8619345a8595b

The second image don't show the input address for transation id: 02643009ef0c5e42a9e30aaa2949aae5164aff723fd0b66ac5e84d38835b5612

The wallet can only show inputs details for transactions it knows of. That is the case of all outgoing transactions (because all inputs belong to the wallet), and generally not the case for incoming transactions (although, a transaction from the wallet to itself consuming rewards may be marked as incoming, and inputs fully known).
This is mentioned in the relevant section of the API documentation:

We had the same issue. Sometimes the addresses are present; other times, they are not. We had this even with two equal transactions on testnet. Both with the same amount. Both from the same source wallet to the same destination wallet. They were about 20 minutes apart. In the first transaction, the input address was missing. But in the second transaction, it wasn't.
On testnet, it's there in most of the cases. I mean, we had about 130 test payments where it was, and just one not. On mainnet, it's a different story. There we had about 80% without and 20% with an address.
It feels like an odd inconsistency for an API. Why would the input address be sometimes present and sometimes not? Why is it even there if you can't rely on the data? Then it's just taking up space and bandwidth. Was that a conscious choice? Or is it a transitional situation?


Add simple usage example

Maybe even something as simple as
using ManifoldDiff
using ADTypes
using Manifolds, FiniteDifferences, ForwardDiff

rb_onb_fd51 = ManifoldDiff.TangentDiffBackend(AutoFiniteDifferences(central_fdm(5, 1)))
rb_onb_fwdd = ManifoldDiff.TangentDiffBackend(AutoForwardDiff())

s2 = Sphere(2)

A = [1.0 2.0 5.0; 2.0 -1.0 4.0; 5.0 4.0 0.0]

f(p) = p' * A * p
q = [0.0, 1.0, 0.0]

ManifoldDiff.gradient(s2, f, q, rb_onb_fd51)
ManifoldDiff.gradient(s2, f, q, rb_onb_fwdd)

@kellertuer Where would you prefer to put it? Just in the readme or somewhere else?

I would maybe do a menu entry below Home called “Get started”?
In the long run this could replace the corresponding tutorial in Manopt.


DriverFramework/cmake_hexagon: use defines with DF (Don't merge yet)

This changes the following defines:
__QURT -> __DF_QURT
__RPI -> __DF_RPI
__EDISON -> __DF_EDISON
__BEBOP -> __DF_BEBOP
__LINUX -> __DF_LINUX
This addresses https://github.com/PX4/DriverFramework/issues/144.
Before it can be merged, these need to be merged:
https://github.com/ATLFlight/dspal/pull/7
https://github.com/ATLFlight/cmake_hexagon/pull/9

@julianoes The above PRs you referenced have been merged. I was away at a conference last week. Apologies for not seeing this sooner.
-Mark

Thanks @mcharleb for merging them!

Rebased, and pointing to correct submodule, let's check CI.

Rebased - let's hope it passes finally.

@LorenzMeier Let me know if there remaining issues

@mcharleb Semaphore failed with: ```-- Check for working CXX compiler using: Ninja -- broken
CMake Error at /usr/share/cmake-3.5/Modules/CMakeTestCXXCompiler.cmake:54 (message):
The C++ compiler
"/home/docker1000/Qualcomm/HEXAGON_Tools/7.2.12/Tools/bin/hexagon-clang++"
is not able to compile a simple test program.
It fails with the following output:
Change Dir: /home/runner/Firmware/build_qurt_eagle_default/CMakeFiles/CMakeTmp
Run Build Command:"/usr/bin/ninja" "cmTC_ab51c"
[1/2] Building CXX object CMakeFiles/cmTC_ab51c.dir/testCXXCompiler.cxx.o
[2/2] Linking CXX executable cmTC_ab51c
FAILED: : &&
/home/docker1000/Qualcomm/HEXAGON_Tools/7.2.12/Tools/bin/hexagon-clang++
CMakeFiles/cmTC_ab51c.dir/testCXXCompiler.cxx.o -o cmTC_ab51c -rdynamic &&
:
clang-3.5: warning: argument unused during compilation: '-rdynamic'
WARNING: can not open search directory
`-L/home/docker1000/Qualcomm/HEXAGON_Tools/7.2.12/Tools/bin/../target/hexagon/lib/v60'.
Fatal: cannot read file
/home/docker1000/Qualcomm/HEXAGON_Tools/7.2.12/Tools/bin/../target/hexagon/lib/v60/crt0_standalone.o
clang-3.5: error: hexagon-link command failed with exit code 1 (use -v to
see invocation)
ninja: build stopped: subcommand failed.
CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
CMakeLists.txt:216 (project)
-- Configuring incomplete, errors occurred!```

@julianoes @dagar FYI

Probably unrelated, but I updated semaphoreci to use the newer snappy image after this build.

@dagar It does most likely have an effect because the compiler toolchain needed an update. Let's see if this does it.

@julianoes Needs work.

Hmm, looks like the semaphoreci change wasn't saved earlier. The build forced with julianoes/px4-snappy-2016-10-16 is passing.
https://semaphoreci.com/px4/firmware/branches/fix_qurt_define/builds/9
Semaphoreci is definitely updated now.

Thanks everybody!

The error pasted above is exactly what the newer docker images was supposed to resolve. Sorry, I missed out on the conversation here but it seems resolved now.


Update French translations

This PR finish work started here #22646
I have:

Improves and add new French translations
Fix the name of this translations file

Hello @Jean-BaptisteC
Thank you for your contribution!
We will look at it.

Adjusted some translations
Fixed wrong encoding and question mark

For the QA Team - you can look at PostgreSQL metadata object fields at least (columns, procedures, indexes).

verified


fixed HTTP/500 when generating a SVG graph without any data

without this patch, generating a SVG graph leads to HTTP/500 instead of an red "no data" image like with PNG

Hi, is someone interested in reviewing and/or merging these changes ?

@g76r I don't know the SVG code very well; it was written by @tmm1 but he's not really active anymore. Regardless, it seems like you seem to know what you're doing so... :boom::wink:

thanks.


Add VB-Audio/VoiceMeeterPotato versions "latest"

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

Microsoft Reviewers: Open in CodeFlow

/azp run

/AzurePipelines run

/azp run

/azp run

Looks like the issues is that the PRs are not in the manifests folder.


Updated Natron homepage.

Changes to a cask
Editing an existing cask

[x] Commit message includes cask’s name (and new version, if applicable).
[x] brew cask audit --download natron is error-free.
[x] brew cask style --fix natron left no offenses.

You did not run the commands. There’s a failure.

Thank you for the contribution. It needed some fixes, so they were made in 26a8eb93e33ecce087ea04b33e4bbb06569203cd. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.

I updated the original PR with extra fixes, is this desirable?

It has already been fixed and merged.


Not working with Angular 12

Hi,
I have upgraded my project to angular 12 and when I run the below command
ng add @angular-architects/module-federation --project shell --port 4200
I am getting "Mf" schema is using the keyword "id" which its support is deprecated. Use "$id" for schema ID.
@manfredsteyer

@rkanthaliya Upgrade to @next.
See the discussion here: https://github.com/angular-architects/module-federation-plugin/issues/34#issuecomment-831489612


Animation glitch

While taking a look at #8293, noticed some glitches when moving the mouse around quite fast. I did a recording and here is a frame from that:

One very pointy point there.
https://jsfiddle.net/uo2j6cwf/
It has something to do with the radius going to 0, and I guess its the point border what is seen.

What browser were you using? I just tried in Firefox 84 and didn't see it. Almost seems like it'd be a problem in the canvas API itself.

What browser were you using? I just tried in Firefox 84 and didn't see it. Almost seems like it'd be a problem in the canvas API itself.

Chromium based browsers (87.0.x) seem to reproduce, but not FF
I was initially using Brave.

Chromium based browsers (87.0.x) seem to reproduce, but not FF
I was initially using Brave.

Reproduces with pointRadius: 0.000005, but not with pointRadius: 0.00005
Easy workaround could be to set to zero when small enough.

Reproduces with pointRadius: 0.000005, but not with pointRadius: 0.00005
Easy workaround could be to set to zero when small enough.

yeah, that makes sense. Below 0.5 it's probably not worth drawing

yeah, that makes sense. Below 0.5 it's probably not worth drawing


Create docker-compose-simple.yml

Why do we need this?

Closing, as I don't believe we need to add back an additional compose file.


Fixes for nightly

Closes #41

Codecov Report
Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (c370d5c) 1.90% compared to head (d20023a) 1.89%.

Files
Patch %
Lines

src/IR/IR.jl
0.00%
2 Missing :warning:

src/IR/Pass.jl
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff            @@
##            main     #42      +/-   ##
========================================
- Coverage   1.90%   1.89%   -0.01%
========================================
  Files        107     107
  Lines      26054   26056       +2
========================================
- Hits         496     495       -1
- Misses     25558   25561       +3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


AttributeError: 'Delegate' object has no attribute '_library' - RPi4 + Coral USB

Hi, flagging this error when trying to run the bodypix.py script.
Believe it's linked to 'OSError: posenet_lib/armv7l/posenet_decoder.so: cannot open shared object file: No such file or directory'7
Any help appreciated.

Actually I just noticed it's looking in armv7l and the repo saves armv7a - renaming folder seemed to let it run. Whether that was the correct fix or not I don't know...

@airqualityanthony that is the fix :)

Saved my day, thanks!


[9.x] Collection->random() add preserve keys option

This PR adds preserveKeys parameter to Collection->random()
before:
Arr::random($collection->all(), 2, true);

after:
$collection->random(2, true);

Changing the method signature here is a breaking change unfortunately. Please send this in to master.


Update back link and panel components

We need to display custom text on the back link component and this
changes that to allow text to be injected.
The panel component should not render a div for the description if there
isn't one, this fixes that.
Remember to update the CHANGELOG if your change needs to be listed in the next version of the gem.

Component guide for this PR:
https://govuk-publishing-compon-pr-628.herokuapp.com/component-guide/

@kevindew I've added examples and tidied up the commits a little bit


remove in-place operator '+=' in resnet

in-place operator in the residual path could potentially cause issues with autograd

I believe this is fine in the current implementation, and uses slightly less memory than the non-inplace version that this PR proposes.
But indeed, other model configurations might not work if modified without taking this in-place operation into account.
As this is not a bug with the current version of ResNet, I'm tempted not to modify it.
cc. @soumith

I don't think we should make this change


[Feature Request] button to prune all stopped containers

Hi,
do you think you could add a prune button in containers page to prune all the stopped container in a single click  (docker container prune command)
thanks in advance

We already had some similar feature requests for the equivalent in the images and volumes section but these were judged too dangerous for the end user.
Maybe only available to an administrator with a confirmation modal as detailed in #714 ?
cc @ncresswell

Now that we have RBAC, i am willing to accept that "prune" functions can be introduced, but only for administrators, and only after at least two warning prompts. If portainer is started with --noauth then i dont want the prune functions displayed.
Do you know if the prune functions are able to return a list of "to be deleted" so the admin can review the list before confirming?
Rgds,
Neil Cresswell
On 31/05/2017, at 2:43 AM, Anthony Lapenna <notifications<EMAIL_ADDRESS>wrote:
We already had some similar feature requests for the equivalent in the images and volumes section but these were judged too dangerous for the end user.
Maybe only available to an administrator with a confirmation modal as detailed in #714https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_portainer_portainer_issues_714&d=DQMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=KWXQP7t8gfrTQKuAxC-RYcIX--bmYS5-KId6VynB80I&s=qgl1Pisz7vNRzEs9shShB10MEx20aembz36i7qksbWo&e= ?
cc @ncresswellhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ncresswell&d=DQMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=KWXQP7t8gfrTQKuAxC-RYcIX--bmYS5-KId6VynB80I&s=-0skmUtnRGjWQt4BVKC_PZBM-pLlDxusE0dj7kmJeY4&e=
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_portainer_portainer_issues_904-23issuecomment-2D304900697&d=DQMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=KWXQP7t8gfrTQKuAxC-RYcIX--bmYS5-KId6VynB80I&s=RaRrlETaf-7Mui7Fk9jtILR4guN2nzA5fmrcMXGf5K4&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AWGrlZykaeMxAlON1jo6Bi9yG5lfTOjXks5r-5FCsggaJpZM4Np9XK&d=DQMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=KWXQP7t8gfrTQKuAxC-RYcIX--bmYS5-KId6VynB80I&s=v6pJwdiBiLFGD6uinwSB5B8iXeCzPMyAhJTYsqt-ON4&e=.

From what I can see in the Docker API, there is no 'dry run' method.

Ok. So then accept, but only for admins and only behind double confirm.
Rgds,
Neil Cresswell
On 31/05/2017, at 8:06 AM, Anthony Lapenna <notifications<EMAIL_ADDRESS>wrote:
From what I can see in the Docker API, there is no 'dry run' method.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_portainer_portainer_issues_904-23issuecomment-2D304992440&d=DQMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=7uunrI2cVysgB0YmsJeJCnISyvIG0sBw-iDyLRISSec&s=bYhqeBHvb4w-8KLUBcHPAWHMuit6Jlwcjm0dKFoX084&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AWGrld9rL1hFIjk7Nd1ayx3cK2ole5xMks5r-5FHaygaJpZM4Np9XK&d=DQMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=7uunrI2cVysgB0YmsJeJCnISyvIG0sBw-iDyLRISSec&s=swJQ455VL3PW6Kn5Uduea05RC30whvqJQfcOzkjAgEw&e=.

sounds good solution on my side :)

We can use system/df call to get info on what is reclaimable I think, but it's maybe complicated
docker system df display a summary of that
It's coded here for example :
https://github.com/docker/cli/blob/6686ada6a4cf4e872af4d9bf3f61c387be934d87/cli/command/formatter/disk_usage.go#L216
https://github.com/docker/cli/blob/6686ada6a4cf4e872af4d9bf3f61c387be934d87/cli/command/system/df.go

admin user within RBAC + double confirm is the way to go.


New script

Use a standalone shell script to replace makefile and install script and provide more functionnalities.

[ ] #6
[ ] #7
[ ] #8
[ ] #9
[ ] #10
[ ] #11

Forsaken


[bug report] UpdateAsync don't fire any callback at sometimes.

using firebase_unity_sdk_5.4.0
if UpdateAsync function called many times at small term, it doesn't fire any callback.
if Unity API function called at this time, the app is crashing.
I think it is the cause of UpdateAsync's tread is not the main thread.

Hi @green4you, thanks for reporting an issue!
For the first bug, can I have you verify two things?

sometimes tasks may fail silently if an exception occurs off the main thread. Try wrapping the body of your ContinueWith with try{}catch(Exception e){} to see if you get anything in there.
if you're still failing and there's no exception being logged, can you update to the latest Firebase SDK (right now 5.7.0) and verify that you're still experiencing the issue?
If the problem persists, it would help me a ton to know:
which Firebase products you're using (I assume Realtime Database)
what version of Unity you're building for
your target platforms (iOS/Android/both)
which scripting backend you're using (IL2CPP or mono)
instructions on reproducing your issue on one of our quickstart projects

For the main thread issue: Unity 4.6's implementation of Task doesn't give us much control over which worker thread your logic executes on. You can work around this in a number of ways:

switching to .NET 3.5 will cause you to use a Task implementation that always dispatches on the main thread.
If you want compatibility between .NET 3.5 and 4.6, you can queue up actions to occur on the main thread via a MonoBehaviour's update loop. I would recommend looking at this implementation.
ContinueWith can take a TaskScheduler. If you're wholly on board with .NET 4.6, you can call TaskScheduler.FromCurrentSynchronizationContext to pass in your current context.

Please let me know if these help at all, and thanks again for taking the time to help us out!
--Patrick

Hi @green4you, thanks for reporting an issue!
For the first bug, can I have you verify two things?

sometimes tasks may fail silently if an exception occurs off the main thread. Try wrapping the body of your ContinueWith with try{}catch(Exception e){} to see if you get anything in there.
if you're still failing and there's no exception being logged, can you update to the latest Firebase SDK (right now 5.7.0) and verify that you're still experiencing the issue?
If the problem persists, it would help me a ton to know:
which Firebase products you're using (I assume Realtime Database)
what version of Unity you're building for
your target platforms (iOS/Android/both)
which scripting backend you're using (IL2CPP or mono)
instructions on reproducing your issue on one of our quickstart projects

For the main thread issue: Unity 4.6's implementation of Task doesn't give us much control over which worker thread your logic executes on. You can work around this in a number of ways:

switching to .NET 3.5 will cause you to use a Task implementation that always dispatches on the main thread.
If you want compatibility between .NET 3.5 and 4.6, you can queue up actions to occur on the main thread via a MonoBehaviour's update loop. I would recommend looking at this implementation.
ContinueWith can take a TaskScheduler. If you're wholly on board with .NET 4.6, you can call TaskScheduler.FromCurrentSynchronizationContext to pass in your current context.

Please let me know if these help at all, and thanks again for taking the time to help us out!
--Patrick

Thank you!
I'm checking this link in ur answer.
https://github.com/firebase/quickstart-unity/issues/261#issuecomment-443896396
I'm using .NET 3.5 plugin, and my unity setting is also using .NET 3.5
Can I use that implementation on my .NET 3.5 setting?

Absolutely!
The trick is that you're just throwing Actions into a queue that's serviced in some MonoBehaviour's Update loop, so it's just like any other function you'd call there.

@green4you did @patm1987 solve your problem(s)?

I'm testing now, but all trying has failed(nothing changed before update firebase SDK).

@patm1987

@patm1987
I can't solve this issue, so sharing my state.
-Unity Version
Unity 2018.2.10f1 (64-bit)

Resolver
play-services-resolver-<IP_ADDRESS>
Firebase SDK
firebase_unity_sdk_5.4.0
or
firebase_unity_sdk_5.7.0

code sample
``RunOnMainThread(() =>
{
            Dictionary<string, object> dicDataToUpload = new Dictionary<string, object>();
            for (int i = 0; i < _pathAndValueListToUpload.Count; ++i)
            {

                string path = _pathAndValueListToUpload[i].path_;
                object value = _pathAndValueListToUpload[i].value_;
                dicDataToUpload[path] = value;
                Debug.LogWarningFormat("UpdateChildrenAsync() - index : {0}, path : {1}, value : {2}", i, path, value.ToString());
            }

            Debug.LogWarningFormat("UpdateChildrenAsync() - call Firebase rootReference.UpdateChildrenAsync()");
            GoOnline();

            DatabaseReference rootReference = FirebaseDatabase.DefaultInstance.RootReference;
            rootReference.UpdateChildrenAsync(dicDataToUpload).ContinueWith(task =>
            {

                RunOnMainThread(() =>
                {
                    GoOffline();
                    if (task.Exception != null)
                    {
                        Debug.Log("task.Exception");
                    }
                    else
                    {

                        FirebaseDBResult result = FirebaseDBResult.None;
                        try
                        {
                            if (task.IsFaulted)
                            {
                                Debug.LogWarningFormat("<color=red>UpdateChildrenAsync - IsFaulted : {0}</color>", task.Exception.ToString());
                                result = FirebaseDBResult.Faulted;
                            }
                            else if (task.IsCanceled)
                            {
                                Debug.LogWarningFormat("<color=red>UpdateChildrenAsync - IsCanceled : {0}</color>", task.Exception.ToString());
                                result = FirebaseDBResult.Canceld;
                            }
                            else if (task.IsCompleted)
                            {
                                Debug.LogWarningFormat("<color=red>UpdateChildrenAsync - IsCompleted</color>");
                                result = FirebaseDBResult.Completed;
                            }
                        }
                        catch
                        {
                        }
                        _onEnd(result);
                    }
                });
            });
        });``

I found another issue on testing with firebase_unity_sdk_5.7.0
firebase_unity_sdk_5.4.0 didn't heat device.
but firebase_unity_sdk_5.7.0 did even if i didn't use firebase database.

@green4you
It's been awhile.  I wonder if later version of Firebase SDK resolve your issue.  If not, I wonder if you see any exception thrown in the log.
I also saw you were using RunOnMainThread() to forward continuation function to main thread.  I would recommend you to try-catch your myDispatcher_.PollJobs(); as well since the exception can be thrown over there.
Also, we just introduce an extension method Task.ContinueWithOnMainThread().  This can handler the exception thrown during continuation function a bit better.
https://firebase.google.com/docs/reference/unity/class/firebase/extensions/task-extension
(Tip: you should add using Firebase.Extensions; to enable these extension methods)
It is a bit hard to reproduce this from our end.  If possible, could you try to reproduce this using Unity quickstart?
Thank you

Hi @green4you I just spent some time reassembling your code snippet http://colorscripter.com/s/YWQcrcp into our database sample and tried it out on macOS, iOS & Android in all cases I'm able to hammer the problematic method with no problems at all.
Since we haven't heard from you with a minimal reproducible case that uses our database sample I'm going to assume that this is something broken in your application.  Let us know if you can come up with a reproducible case and we'll take a look.

Thank you for the "ContinueWithOnMainThread" with using Firebase.Extensions; !!!
It saved me !!


Add memcached container

Adding Memcached container.
You have implemented a new container and would like to contribute it? Great! Here are the necessary steps.

[x] Create a new feature directory and populate it with the package structure described in the documentation. Copying one of the existing features is likely the best way to get started.
[x] Implement the new feature (typically in __init__.py) and corresponding tests.
[x] Add a line -e file:[feature name] to requirements.in and run make requirements. This command will find any new requirements and generate lock files to ensure reproducible builds (see the pip-tools documentation for details). Then run pip install -r requirements/[your python version].txt to install the new requirements.
[x] Update the feature README.rst and add it to the table of contents (toctree directive) in the top-level README.rst.
[x] Add a line [feature name] to the list of components in the  GitHub Action workflow in .github/workflows/main.yml to run tests, build, and publish your package when pushed to the master branch.
[x] Rebase your development branch on master (or merge master into your development branch).

@romulojales Can you get this merged and released?

@romulojales @pffijt Can you get this merged and released?

Hello @damjankuznar ,
I just rebased the PR with the latest main version.
Since I don't manage the project, I'm also waiting for the maintainers to review, and hopefully, approve my pr, so I could work with it without using my own fork.

original commits are here - https://github.com/testcontainers/testcontainers-python/commits/romulojales/add-memcached


How to ignore case when sorting in data mode

As far as I can tell, there is no way to ignore case when sorting. Please correct me if I'm wrong.

This actually has nothing to do with Vuetable because Vuetable never sorts the data by itself. It eighter relies on server side API or data-manager function (which you have to define by yourself) to do this job.
In the data mode example, I used lodash library to perform sorting and filtering functions. You can try to research more on that. My guess is that you should be able to use _sortBy and define the "iteratee` function to perform sort the way you want as well.

Ah, the data manager, that's it! I completely forgot that you define it there. I did it in the past and then, after a long break, it seemed like vuetable-2 was doing the sorting.
Thanks for that.


[Testing] Guides on user provisioning

Guides on user provisioning [1] should be tested.
[1] https://is.docs.wso2.com/en/latest/guides/identity-lifecycles/provisioning-overview/

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Ensure redirects are handled correctly

A few cases that may not be handled correctly right now:

user visits a group detail page they are not a member of
user visits a page that does not exist at all (no route)
item does not exist (e.g. group id that does not exist)
other things like this (but for the store)

In general some of this stuff should/is be handled, but is maybe not completely correct right now. Should also have some tests unit and/or e2e.

As e2e tests seem to be a bit too complicated to add in the next week, I would try to go through obvious cases and test it manually.

Currently handled quite ok

invalid group info id

https://dev.foodsaving.world/#/groupInfo/99999
redirects to /notfound

user visits a page that does not exist at all (no route)

Shows 404
handled, but might be confusing

user visits a group detail page they are not a member of

https://dev.foodsaving.world/#/group/9999/wall
Redirects to  currentGroup. I was confused to see the wall of a different group, although there was a very short toast. Does not change the URL in the browser.
Currently not handled at all (shows empty or half-empty page)

[ ] invalid user id: https://dev.foodsaving.world/#/user/999
[ ] invalid store id: https://dev.foodsaving.world/#/group/6/store/9999/pickups

I think the method of redirecting to /notfound is a ugly workaround. It should rather keep the URL in the browser, but show the most detailed error message possible ('not a member of the group', 'route invalid', 'store id invalid')

Now that we have the routeError vuex module, we should use it for all kinds of "id not found/accessible" errors


Validation of 2 fields against each other

@felangel
This is related to issue #5
I am curious to how it would work out if there are 2 inputs that have to be validated against each other.
This method won't work anymore since 2 objects cannot co-create each other.
@felangel what would be a direction in this case?
The example of would be 2 time entries that need to be verified against each other.
Like start time and end time.
If I add the code example from above the the end_time field then it is only verified against start_time. But start_time is not verified against the initial field and I am struggling to find an elegant solution to solve this.

Hm, what about treating these 2 fields as one complex field (as it seems it is in such case).
class ComplexObject {
  // ...
  final SomeObject one;
  final SomeObject two;
  // ...
}

class ComplexObjectFormzInput extends FormzInput<ComplexObject, FieldValidationError> {
  const ComplexObjectFormzInput() : super.pure(ComplexObject());
  const ComplexObjectFormzInput([ComplexObject value = ComplexObject()]) : super.dirty(value);

  @override
  FieldValidationError validator(ComplexObject value) {
    // ...
  }
}

@ycherniavskyi Thank you for the advice. I will try to implement and provide feedback here in the comment.
Thanks for your input

Closing for now but feel free to comment with additional questions and I'm happy to continue the conversation 👍


Attempt to fix the exp popup crash

I couldn't reproduce this, so maybe someone who can should test this first?

Heya, I will test this solution.

Theorethically, this should work. Pulling and praying.


Fix typo in README.md

extensibilty -> extensibility
Changes proposed ✍
What

🤖 Generated by Copilot at aba7a93
This pull request corrects a spelling error in the README.md file of the crowd.dev repository. The change enhances the quality and clarity of the project's documentation.

🤖 Generated by Copilot at aba7a93

README.md typo
Corrected with care and skill
Spring of extensibility

Why
How

🤖 Generated by Copilot at aba7a93

Corrected a typo in the word "extensibility" in the README.md file (link)

Checklist ✅

[ ] Label appropriately with Feature, Improvement, or Bug.
[ ] Add screehshots to the PR description for relevant FE changes
[ ] New backend functionality has been unit-tested.
[ ] API documentation has been updated (if necessary) (see docs on API documentation).
[ ] Quality standards are met.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hey @eltociear, thanks for noticing this!
Could you solve the conflicts so that I can merge this? 😄


hugo: 0.125.5 -> 0.125.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/gohugoio/hugo/releases.
meta.description for hugo is: A fast and modern static website engine
meta.homepage for hugo is: https://gohugo.io
meta.changelog for hugo is: https://github.com/gohugoio/hugo/releases/tag/v0.125.6
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.125.6 in filename of file in /nix/store/41g1v7mbx9iz7bv7sdy8h547rwgyr5fr-hugo-0.125.6

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

hugo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/41g1v7mbx9iz7bv7sdy8h547rwgyr5fr-hugo-0.125.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A hugo https://github.com/r-ryantm/nixpkgs/archive/3a2c6c746aec49df4042782167ae509bf5d00d35.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/3a2c6c746aec49df4042782167ae509bf5d00d35#hugo

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/41g1v7mbx9iz7bv7sdy8h547rwgyr5fr-hugo-0.125.6
ls -la /nix/store/41g1v7mbx9iz7bv7sdy8h547rwgyr5fr-hugo-0.125.6/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

hugo

Maintainer pings
cc @schneefux @Br1ght0ne @Frostman for testing.

That's fine, you can just bump to the next version.


Image replace

When i try run the example, the image isn't replaced. No error generated. It's works with images?

It does work with images and is in production usage with it. Not sure what the issue is, but it’s likely on your side. You might want to do some debugging to see what’s actually going on. Eg are the images resized, placed into the docx file etc. This library technically works well, but is not well documented nor has it sufficient error reporting. Therefore more digging on the implementation side is necessary.
Sent from my iPhone

On Aug 15, 2019, at 02:30, medeirosrafael<EMAIL_ADDRESS>wrote:

When i try run the example, the image isn't replaced. No error generated. It's works with images?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I got it. In Libreoffice i need put the {{img_url}} tag in a ghost field (LOL!).

@tobiasvielmetter i was having a problem.. when my condition is not satisfied, a blank space still in document.
Example:
"
BLA BLA BLA BLA BLA
{{#myCondition}}
xxxxxxxxxxxxxxxx
{{/myCondition}}
ZZZZZZZZZZZZZZZZZZZZz
"
If myCondition is false the result is:
"
BLA BLA BLA BLA BLA
ZZZZZZZZZZZZZZZZZZZZz
"
instead of
"
BLA BLA BLA BLA BLA
ZZZZZZZZZZZZZZZZZZZZz
"
I solved locally adding
        foreach ($matches[0] as $match) {
            if (strpos($match, '<w:t xml:space="preserve"></w:t>') !== false) {
                $this->word_doc = str_replace($match, '', $this->word_doc);
            }
        }

in DocxMustache.php line 156..
Can i make a merge request?

Not sure this makes sense. If a \n /  is outside of the condition, it will be shown, no matter if the condition is met. The way to do your condition would be the following instead, so you dont have any unnecessary new lines, even if the condition is not met:
"
BLA BLA BLA BLA BLA{{#myCondition}}
xxxxxxxxxxxxxxxx
{{/myCondition}}
ZZZZZZZZZZZZZZZZZZZZz
"


[Bug] run docker-compose up error

What happened:
report error message: service "arana" depends on undefined service arana-admin: invalid compose project that when docker-compose up
What you expected to happen:
start arana service success
How to reproduce it (as minimally and precisely as possible):
run docker-compose up
Anything else we need to know?:
nothing

Use the latest master version, it should include arana-admin already.


Stateless Proxy Support

Would like to use multiple drachtio-servers to ship requests around. For example:
UE1         UE2       drachtioA       drachtioB
 |           |          |              |
 | INVITE (1)---------->|              |
 |           |          |(2)---------->|
 |           |          |              |
 |           |          |<----------(3)|
 |           |<------(4)|              |
 |           |          |              |

drachtioA handles most requests as a proxy and if coming from users from the internal network will forward the messages to another server, in this case, drachtioB. drachtioB acts as a Registrar/Proxy. In this case, UE1 and UE2 are registered with it. I want UE1 to send an INVITE to UE2 via drachtioA, then drachtioB, which will route the INVITE back through drachtioA to get to UE2. drachtioA would see the message coming from the external network and route to the internal client (UE2 address state would be in the application).
However, upon testing, I see the drachtio-server message "Discarding retransmitted request since we are a stateful proxy INVITE ...". Can drachtio-server be configured to be a stateless proxy? On a per message type request? Or is there a better way?
For drachtioA I am using drachtio Node.js app and for drachtioB I am using drachtio-srf.

Currently there is no support for acting as a stateless proxy, only as a stateful proxy.
However, the scenario you outline should work fine as a stateful proxy.  The fact that drachtioA is seeing retransmitted requests from UE1 seems strange to me, because drachtioA would have sent a 100 Trying back to the INVITE from UE1, therefore UE1 should not need to retransmit INVITEs.
Unless, it is a different message that is being retransmitted?  A REGISTER or something?
If an INVITE, then I would like to look into why this is happening (logs etc).  If this is a non-INVITE then the question would be why is it taking so long for drachtioB to process and respond to the request

any thoughts on this?  I'd like to help make it work as a stateful proxy, not sure why you are experiencing retransmits

I was mulling over creating a simple (specific to my needs) stateless proxy... Didn't mean to delay. When I tested and described the original post, it certainly seemed like it was an INVITE retransmit. I will capture logs and upload, in case you are able to see something that can be fixed in this case. But I might not be able to get to this until later next week. Thanks for all you help as usual!

I would like to close this issue, we are not planning to go in this direction at this time. Thanks!


cPickle.load takes no keyword arguments

seems that cPickle.load got a new argument in 3.0?

Can you explain in more detail, perhaps with a code snippet, what the bug you're reporting is? cPickle doesn't exist in Python 3, so I'm not sure exactly what you're referring to.


Russian translation

Added russian language to langs

Thank you

@Vrex123 would you mind please translating the following as well? These are new with the addition of Readarr support (currently in the beta branch).
readarr_disabled: Sorry, but book support is disabled.
include_book_title_in_cmd: Please include the book title in the command, e.g. {commands}
no_matching_books: Sorry, but I didn't find any matching books.
help_readarr: Use {book_commands} to add a book to Readarr.
no_metadata_profiles: "Error adding {kind}: no metadata profiles enabled for {app}! Please check your Searcharr configuration and try again."
add_metadata_button: "Add Metadata: {metadata}"