Semantic versioning and stricter API versioning constraints

We've had feedback from folks (in particular gRPC-LB) that the current Breaking Change Policy is insufficient for handling long-term compatibility at the wire and generated proto level.
Specifically:

Coupling API field validity and deprecation to Envoy release cycles is an implicit API state that mostly makes sense for Envoy but not for independent clients. Even https://github.com/envoyproxy/envoy/issues/5405 introduces too much pain for non-Envoy clients.
Upgrading to oneof and other wire compatible changes breaks Go code generation for protobuf. There are no safe mutations to existing proto fields.

The proposal here is that we switch to semantic versioning by making use of package namespaces. Any API that is not marked as alpha, e.g. v2alpha, becomes immutable modulo field addition. Deprecation would happen by moving to v3, v4, etc.
What do folks think? CC @envoyproxy/maintainers @alyssawilk

One concern that springs to mind is the issues we've had with moving service between packages, since that breaks gRPC wire compatibility due to the :path header. Would this make changes to any protobufs that's referenced by a service very painful?

@snowp package namespace changes would imply service endpoint changes. The management server would need to support both during a transition period.

Not sure if this is relevant for this particular issue but CockroachDB recently switched away from SemVer - Why we're switching to calendar versioning. Along the same lines the SemVer specification is getting an upgrade - What’s next for SemVer.

What do folks think?

I'm not thrilled about this since I do think it will increase deprecation overhead/velocity quite a bit. I think I'm not fully understanding the problem that gRPC is facing. Can you potentially describe in more detail?

@markdroth can you provide a summary for your team?

API stability is an extremely important factor for anyone outside Envoy looking to adopt the xDS protocol.  gRPC needs the ability to easily express to its users what version(s) of the protocol it works with.  At this point, we cannot say "gRPC works with xDS v2", because features present in the initial release of v2 may have been removed and replaced -- or may be in the future -- in accordance with the breaking change policy.  This means if gRPC uses the old fields, it won't work with new servers and vice-versa.
In addition to those concerns, gRPC-Go has twice in the past two months (https://github.com/envoyproxy/envoy/pull/6118, https://github.com/envoyproxy/envoy/pull/5432) been broken by wire-compatible changes to the proto format that break the go generated API.  This is not only disruptive to our development, but it also affects our users: they will need to vendor these protos at the right version.  The problem with this is, if they are developing a project that has other dependencies on the xDS API, they may not be able to find a single version that satisfies all of their dependencies (some may require newer versions and some may require older versions).  Multiple copies of the same proto definitions are not permitted, and will result in init-time panics.

re: the Go issues, I think that is more straightforward. We can just not do the things that break Go such as add a oneof after the fact (and anything else).
The other concern is much trickier. I understand it, but adhering to it will greatly reduce our velocity. Can we discuss this on the next community call and brainstorm possible outcomes?

@mattklein123 In order to maintain backward compatibility for the Go generated API, the other condition also needs to be met.  Removing a field will break the generated code API (in addition to breaking wire compatibility).
I have no desire to reduce your velocity.  New features can be added with a clear "experimental" tag to be exempted from these requirements.  gRPC and other users requiring a stable API would not use those features until they are finalized.
Discussing this further at the next community meeting sounds fine.

I agree that discussing this in the community meeting would be the most
efficient way to move forward. Doug, can you and interested gRPC folks join
https://calendar.google.com/event?action=TEMPLATE&tmeid=NzI4c2E5YWJjbDRnMmp1amdsOW5uNTJsMjZfMjAxOTAzMjZUMTYwMDAwWiA4YnNmYzhtMmRmOG1hZDJqdGdmNmY4b25qNEBn&tmsrc=8bsfc8m2df8mad2jtgf6f8onj4%40group.calendar.google.com&scp=ALL
on
3/26?
On Wed, Mar 13, 2019 at 5:17 PM Doug Fawley<EMAIL_ADDRESS>wrote:

@mattklein123 https://github.com/mattklein123 In order to maintain
backward compatibility for the Go generated API, the other condition also
needs to be met. Removing a field will break the generated code API (in
addition to breaking wire compatibility).
I have no desire to reduce your velocity. New features can be added with a
clear "experimental" tag to be exempted from these requirements. gRPC and
other users requiring a stable API would not use those features until they
are finalized.
Discussing this further at the next community meeting sounds fine.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/envoyproxy/envoy/issues/6271#issuecomment-472609155,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKaLvxhDKFmbTIcMkTUR0nSoXuZJsUQ1ks5vWWrngaJpZM4brnnv
.

@htuch, yes, I plan to attend, and I have invited a few others.  Thanks for sharing the link.

Resharing Doug's doc which presented at the community call via my chromium account (so folks can read and comment)
https://docs.google.com/document/d/1nAomWSjvSSFCNZ1wQJ7D01f5VGDGLn5zcNxcDozYqYI/edit?ts=5c9a516b#heading=h.hv6zo3sm8vz7

We now have a design document to share:

Full design document
TL;DR summary

It looks like we have general buy-in on the proposal, so the following calendar is what I think I can commit to:
Before end of Q2:

[ ] TDS (https://github.com/envoyproxy/envoy/issues/6708)
[ ] Unknown field support for dynamic config, stats tracking, etc. (https://github.com/envoyproxy/envoy/issues/6818 and https://github.com/envoyproxy/envoy/issues/6651).
[ ] Add presubmit check forcing sign-off from @envoyproxy/api-shepherds for any changes to api/.
[ ] Manual inspection of all API changes to avoid any breaking changes at either wire or language stub level.
[ ] Minor/patch version proto annotations added to v2 API.
[ ] Semantic version reporting in xDS for core APIs.
[ ] Introduce v3alpha for some relatively isolated example package. Write a translation module in Envoy implementation, providing the pattern for the "translate old versions of API to new on API ingest".
[ ] Node enhancements for user agent and client feature reporting.

Before end of Q3:

[ ] Node enhancements for extension version reporting, corresponding filter interface changes to support this.
[ ] TBD tool enforcement of minor/patch version updates when material proto changes occur.
[ ] TBD tool to enforce ODR and ensure transitive upgrades work as expected.
[ ] TBD tool to enforce package dependency constraints, e.g. verify the property that stable APIs do not depend on experimental APIs, that the latest stable version of any API only depends on the latest stable versions (including transitively) of other APIs. Also, to ensure we have well formed package namespace.
[ ] TBD tooling to support reducing the manual stub/code toil when moving from vN to v(N+1) where most fields are the same.
[ ] protolock presubmit (https://github.com/envoyproxy/envoy/issues/3368, https://github.com/envoyproxy/envoy/issues/3368)
[ ] Extend protolock to handle PGV annotations.

At the end of Q3, we will start the annual release calendar for new API major versions, and the APIs that were in v3alpha will be frozen as v3, v4alpha will begin, etc.
Field will continue to be deprecated via annotation according to https://github.com/envoyproxy/envoy/blob/master//CONTRIBUTING.md#breaking-change-policy. However, we will not remove any further fields from the v2 fields from now on. Deprecated fields will become disabled by default following the existing schedule, this may be overriden by TDS. The goal of deprecation across major versions will be to allow advanced notion of significant structural changes to the API when moving from vN to v(N+1), but no fields will be removed in vN.
@mattklein123 @alyssawilk @dfawley @envoyproxy/api-shepherds @envoyproxy/maintainers (and anyone else who cares about API stability!) does this sound like a reasonable plan-of-record?

@htuch +1 looks great to me. Thanks for driving.

See https://github.com/envoyproxy/envoy/issues/8085 for the v3alpha and v3 release plans. The burndown is at https://github.com/envoyproxy/envoy/issues?q=is%3Aopen+is%3Aissue+label%3A"v3+API"+milestone%3A1.12.0


rows_affected in adapter response is 0 for incremental models

I seem to be having issues since upgrading to 1.8.4+ of the sql server adapter where the rows_affected is coming back as 0 for incremental models. It used to work in 1.4.3. Is anyone else having this issue or able to reproduce it?

If you pin sql server to 1.8.4 and fabric to 1.8.7 does it work?

No, that’s what I had originally and then upgraded to 1.8.5 and 1.8.8 of fabric to see if that fixed anything. The issue seems to be happening on the first run when inserting new records into incremental table but when I run again with the same condition it will report correctly.

@cody-scott Also, for table materialization, the rows_affected is always -1 for me.

So I was playing around the fabric__get_delete_insert_merge_sql macro and it seems that if I removed the delete statement that comes before the insert, the cursor properly reports the rowcount. It seems the rowcount being reported is from the delete statement and the insert doesn't change the rowcount.  Was this maybe a change in pyodbc functionality?
{% macro fabric__get_delete_insert_merge_sql(target, source, unique_key, dest_columns, incremental_predicates=none) %}
{% set query_label = apply_label() %}
{%- set dest_cols_csv = get_quoted_csv(dest_columns | map(attribute="name")) -%}

{% if unique_key %}
    {% if unique_key is sequence and unique_key is not string %}
        delete from {{ target }}
        where exists (
            select null
            from {{ source }}
            where
            {% for key in unique_key %}
                {{ source }}.{{ key }} = {{ target }}.{{ key }}
                {{ "and " if not loop.last }}
            {% endfor %}
        )
        {% if incremental_predicates %}
            {% for predicate in incremental_predicates %}
                and {{ predicate }}
            {% endfor %}
        {% endif %}
        {{ query_label }}
    {% else %}
        delete from {{ target }}
        where (
            {{ unique_key }}) in (
            select ({{ unique_key }})
            from {{ source }}
        )
        {%- if incremental_predicates %}
            {% for predicate in incremental_predicates %}
                and {{ predicate }}
            {% endfor %}
        {%- endif -%}
        {{ query_label }}
    {% endif %}
{% endif %}

insert into {{ target }} ({{ dest_cols_csv }})
(
    select {{ dest_cols_csv }}
    from {{ source }}
){{ query_label }}

{% endmacro %}

So wrapping SET NOCOUNT ON; and SET NOCOUNT OFF; around the DELETE statements resolved the issue for me.

I was also able to fix the rowcount for table materialization as well by calling the create view in a separate batch.
`{% macro sqlserver__create_table_as(temporary, relation, sql) -%}
{%- set query_label = apply_label() -%}
{%- set tmp_relation = relation.incorporate(path={"identifier": relation.identifier ~ '__dbt_tmp_vw'}, type='view') -%}
{%- do adapter.drop_relation(tmp_relation) -%}

{% call statement('create_temp_view', fetch_result=False) %}
    USE [{{ relation.database }}];
    {{ get_create_view_as_sql(tmp_relation, sql) }}
{% endcall %}

{%- set table_name -%}
    {{ relation }}
{%- endset -%}

{%- set contract_config = config.get('contract') -%}
{%- set query -%}
    {% if contract_config.enforced and (not temporary) %}
        CREATE TABLE {{table_name}}
        {{ get_assert_columns_equivalent(sql)  }}
        {{ build_columns_constraints(relation) }}
        {% set listColumns %}
            {% for column in model['columns'] %}
                {{ "["~column~"]" }}{{ ", " if not loop.last }}
            {% endfor %}
        {%endset%}
        INSERT INTO {{relation}} ({{listColumns}})
        SELECT {{listColumns}} FROM {{tmp_relation}} {{ query_label }}

    {% else %}
        SELECT * INTO {{ table_name }} FROM {{ tmp_relation }} {{ query_label }}
    {% endif %}
{%- endset -%}

EXEC('{{- escape_single_quotes(query) -}}')

{# For some reason drop_relation is not firing. This solves the issue for now. #}
EXEC('DROP VIEW IF EXISTS {{tmp_relation.schema}}.{{tmp_relation.identifier}}')

{% set as_columnstore = config.get('as_columnstore', default=true) %}
{% if not temporary and as_columnstore -%}
    {#-
    add columnstore index
    this creates with dbt_temp as its coming from a temporary relation before renaming
    could alter relation to drop the dbt_temp portion if needed
    -#}
    {{ sqlserver__create_clustered_columnstore_index(relation) }}

{% endif %}
{% endmacro %}`


Add asynchronous client

Fixes https://github.com/inspired-co/eaas_client/issues/11

Looks good,
Is it a kinda shallow-asynchronous strategy that follows ExplainaBoard? For example,  if multiple metrics are submitted simultaneously, then they will be calculated sequentially?

Yes, it seems that the current client makes consecutive requests per evaluation metric:
https://github.com/inspired-co/eaas_client/blob/main/eaas/client.py#L405
This should be fixed so that all requests are sent to the server simultaneously, and the server can do whatever multithreading it wants behind the scenes.


Display issue with theme with a background

There seems to be a blank bar at the bottom of pages as can be seen in the image below (the blank bar is just a lack of background image)

This issue only shows if your theme has a background image and only shows on secondary+ Lovelace dashboards with custom-header installed.
Disabling custom-header doesnt solve the problem.
Uninstall custom-header and problem goes away.
Problem is found on all browsers I have tried
Versions:
Home assistant: 0.108.4 (also did it in 0.107.x)
custom-header: 1.3.8
Chrome: 80
Firefox: 75
Android client: 1.8.0-144
The theme I am using can be found here https://github.com/lispwarez/hass/blob/master/themes/midnight2.yaml

+1
Issue again:

The issue arise from setting ch-header and ch-footer to visibility: hidden instead of display: none, see below.

Much has changed recently and I cannot reproduce this in the latest version. The current version is 1.4.5. Is this still an issue?

I just completed my upgrade to 0.110.1 along with custom-header and all seems to be fine now
Thank you


support for federated graphs?

Not sure if this is really an issue as you might define it, but I can't figure out how to use this great package with a federated graph and Apollo server/gateway. Is it possible? Feel free to close if my problem is irrelevant.

Do I understand correctly that the individual services Schemas should be annotated and the gateway then enforces those rules?

I think that's how I'd planned to do it, yes. Is there a better/different way?

I have not investigated on that yet (and never used federation), but here my thoughts on how it might work.
Directive/field/object/argument extensions information is not exposed via introspection, thus you need another way of exposing that information. One possible option might be via the extensions field on the execution result.
So of your gateway sends a introspection Query to your service you could expose that information via extensions on that introspection result.
The gatway could them use that information with a custom isPublic function 🤔

Sorry - family event took me away from the computer. Thanks for the prompt reply.
So create a plugin on the gateway side to add a custom isPublic function? Is that the route you would suggest?

@scottmccaskill Yes, I would do that!

Gonna close this as it is answered.


[CI] Make params.env check happy again

No need for a workaround for the habana image anymore :)

/lgtm

Just realized that we have an upstream -> downstream branch regular updates. So maybe this is irrelevant and I should just check that the appropriate changes are done in a relevant branch in upstream, right? I'm moving this to draft until it's clear.

I'm undrafting this, since the change for this in main is for some time already 248047b5b0a984811c6e332f2149cc1cb4a61edb and the latest main -> 2024a PR #307 doesn't seem to grab it...

Hey Jan this will sync on release-2024a automatically through this https://github.com/red-hat-data-services/notebooks/pull/307 (If the changes are merged on 2024a upstream branch)

@atheo89 The PR you linked says it needs rebase. How to fix this? https://github.com/red-hat-data-services/notebooks/pull/307#issuecomment-2209199695

@jiridanek It can be through GitHub UI, (I did that once) or checkout this PR and fix conflicts and push back.

As was discussed above, the changes from upstream weren't brought in by the sync PRs, probably due to the manual changes due to the conflicts resolving or that Habana isn't in upstream. Anyway, since I forgot about this PR of mine in the meantime, this got fixed in this one instead #351. As such, this one can be closed as obsolete now :upside_down_face: :sunglasses:


Repeating and missing Number Java

Issue #317 (Repeating and missing) is solved here.

@raksha009 , I have made all the requested changes. Kindly review it.

@raksha009 , I have done all the requested changes kindly review it.

Hey @raksha009 , I have made all the required changes , Kindly Review it.

@raksha009 , I have made all the suggested chances. Kindly review it.


[SPARK-34048][SQL][TESTS] Check the amount of calls to Hive external catalog

What changes were proposed in this pull request?
Add new tests to unified test suites to check the total amount of calls via the Hive client.
Why are the changes needed?

To improve test coverage
To make foundation for future optimizations

Does this PR introduce any user-facing change?
No
How was this patch tested?
By running the affected test suites like:
$ build/sbt -Phive-2.3 -Phive-thriftserver "test:testOnly *AlterTableDropPartitionSuite"

Test build #133838 has started for PR 31092 at commit e0bd817.

Test build #133838 has started for PR 31092 at commit e0bd817.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38427/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38427/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38427/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38427/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/38427/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/38427/

Test build #133838 has finished for PR 31092 at commit e0bd817.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class ShowTablesSuite extends v1.ShowTablesSuiteBase with CommandSuiteBase

Test build #133838 has finished for PR 31092 at commit e0bd817.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class ShowTablesSuite extends v1.ShowTablesSuiteBase with CommandSuiteBase

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/133838/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/133838/

@dongjoon-hyun @cloud-fan @HyukjinKwon Could you have a look at this PR, please.

@dongjoon-hyun @cloud-fan @HyukjinKwon Could you have a look at this PR, please.

I thought you are going to make  another PR to reduce the Hive API call. Is the PR merged?

I thought you are going to make  another PR to reduce the Hive API call. Is the PR merged?

I thought you are going to make another PR to reduce the Hive API call. Is the PR merged?

@dongjoon-hyun I have some ideas how to reduce the number of calls to Hive external catalog. And I am going to try to implement those ideas after this PR is merged.
But I think the tests from this PR are useful independently from future optimizations. They can prevent regressions in the future.

I thought you are going to make another PR to reduce the Hive API call. Is the PR merged?

@dongjoon-hyun I have some ideas how to reduce the number of calls to Hive external catalog. And I am going to try to implement those ideas after this PR is merged.
But I think the tests from this PR are useful independently from future optimizations. They can prevent regressions in the future.

Got it. Thank you for sharing your dev direction, @MaxGekk .

Got it. Thank you for sharing your dev direction, @MaxGekk .

Yeah, I think its okay. LGTM2

Yeah, I think its okay. LGTM2

late LGTM

late LGTM

I have some ideas how to reduce the number of calls to Hive external catalog.

Thank you for sharing your dev direction

@dongjoon-hyun I implemented one of my ideas in this PR https://github.com/apache/spark/pull/31206 , could you, please, review it.

I have some ideas how to reduce the number of calls to Hive external catalog.

Thank you for sharing your dev direction

@dongjoon-hyun I implemented one of my ideas in this PR https://github.com/apache/spark/pull/31206 , could you, please, review it.

Oh, got it. Sorry for missing ping on that PR. I'll try to visit there when I become available, @MaxGekk .

Oh, got it. Sorry for missing ping on that PR. I'll try to visit there when I become available, @MaxGekk .


Update set-a-database-to-single-user-mode.md

Grammatical correction.

Looks good; thanks, @himanshu-ram-punjabi


'package:flutter/src/widgets/framework.dart': Failed assertion: line 5191 pos 16: 'owner!._debugCurrentBuildTarget == this': is not true.

Steps to reproduce
when I run the flutter app on IOS after initializing the bloc providers it returns the error on the MaterialApp
Expected results
It should continue the app and open it normally
Actual results
it return an error more than 100 times on
The relevant error-causing widget was:
'package:flutter/src/widgets/framework.dart': Failed assertion: line 5191 pos 16: 'owner!._debugCurrentBuildTarget == this': is not true.
Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
The relevant error-causing widget was:
    MaterialApp MaterialApp:file:///Users/qamacbook/Desktop/abwaab-mobile-v3/lib/app.dart:41:20

When the exception was thrown, this was the stack:
#2      Element.rebuild.<anonymous closure> (package:flutter/src/widgets/framework.dart:5191:16)
framework.dart:5191
#3      Element.rebuild (package:flutter/src/widgets/framework.dart:5194:8)
framework.dart:5194
#4      ComponentElement._firstBuild (package:flutter/src/widgets/framework.dart:5453:5)
framework.dart:5453
#5      ComponentElement.mount (package:flutter/src/widgets/framework.dart:5447:5)
framework.dart:5447
...     Normal element mounting (366 frames)
#371    SingleChildWidgetElementMixin.mount (package:nested/nested.dart:222:11)
nested.dart:222
...     Normal element mounting (15 frames)
#386    _InheritedProviderScopeElement.mount (package:provider/src/inherited_provider.dart:411:11)
inherited_provider.dart:411
...     Normal element mounting (7 frames)
#393    SingleChildWidgetElementMixin.mount (package:nested/nested.dart:222:11)
nested.dart:222
...     Normal element mounting (7 frames)
#400    SingleChildWidgetElementMixin.mount (package:nested/nested.dart:222:11)
nested.dart:222
...     Normal element mounting (7 frames)
#407    _InheritedProviderScopeElement.mount (package:provider/src/inherited_provider.dart:411:11)
inherited_provider.dart:411
...     Normal element mounting (7 frames)
#414    SingleChildWidgetElementMixin.mount (package:nested/nested.dart:222:11)
nested.dart:222
...     Normal element mounting (7 frames)
#421    SingleChildWidgetElementMixin.mount (package:nested/nested.dart:222:11)
nested.dart:222
...     Normal element mounting (7 frames)
#428    _NestedHookElement.mount (package:nested/nested.dart:187:11)
nested.dart:187
...     Normal element mounting (7 frames)
#435    _InheritedProviderScopeElement.mount (package:provider/src/inherited_provider.dart:411:11)
inherited_provider.dart:411
...     Normal element mounting (7 frames)
#442    SingleChildWidgetElementMixin.mount (package:nested/nested.dart:222:11)
nested.dart:222
...     Normal element mounting (7 frames)
#449    SingleChildWidgetElementMixin.mount (package:nested/nested.dart:222:11)
nested.dart:222
...     Normal element mounting (7 frames)
#456    _NestedHookElement.mount (package:nested/nested.dart:187:11)
nested.dart:187
...     Normal element mounting (7 frames)
#463    _InheritedProviderScopeElement.mount (package:provider/src/inherited_provider.dart:411:11)
inherited_provider.dart:411
...     Normal element mounting (7 frames)
#470    SingleChildWidgetElementMixin.mount (package:nested/nested.dart:222:11)
nested.dart:222
...     Normal element mounting (7 frames)
#477    SingleChildWidgetElementMixin.mount (package:nested/nested.dart:222:11)
nested.dart:222
...     Normal element mounting (7 frames)
#484    _NestedHookElement.mount (package:nested/nested.dart:187:11)
nested.dart:187
...     Normal element mounting (7 frames)
#491    _InheritedProviderScopeElement.mount (package:provider/src/inherited_provider.dart:411:11)
inherited_provider.dart:411
...     Normal element mounting (7 frames)
#498    SingleChildWidgetElementMixin.mount (package:nested/nested.dart:222:11)
nested.dart:222
...     Normal element mounting (7 frames)
#505    SingleChildWidgetElementMixin.mount (package:nested/nested.dart:222:11)
nested.dart:222
...     Normal element mounting (7 frames)
#512    _NestedHookElement.mount (package:nested/nested.dart:187:11)
nested.dart:187
...     Normal element mounting (7 frames)
#519    _InheritedProviderScopeElement.mount (package:provider/src/inherited_provider.dart:411:11)
inherited_provider.dart:411
════════ Exception caught by widgets library ═══════════════════════════════════
'package:flutter/src/widgets/framework.dart': Failed assertion: line 5191 pos 16: 'owner!._debugCurrentBuildTarget == this': is not true.
The relevant error-causing widget was:
════════════════════════════════════════════════════════════════════════════════

════════ Exception caught by widgets library ═══════════════════════════════════
'package:flutter/src/widgets/framework.dart': Failed assertion: line 5191 pos 16: 'owner!._debugCurrentBuildTarget == this': is not true.
The relevant error-causing widget was:
════════════════════════════════════════════════════════════════════════════════

════════ Exception caught by widgets library ═══════════════════════════════════
'package:flutter/src/widgets/framework.dart': Failed assertion: line 5191 pos 16: 'owner!._debugCurrentBuildTarget == this': is not true.
The relevant error-causing widget was:
════════════════════════════════════════════════════════════════════════════════

════════ Exception caught by widgets library ═══════════════════════════════════
'package:flutter/src/widgets/framework.dart': Failed assertion: line 5191 pos 16: 'owner!._debugCurrentBuildTarget == this': is not true.
The relevant error-causing widget was:
════════════════════════════════════════════════════════════════════════════════

════════ Exception caught by widgets library ═══════════════════════════════════
'package:flutter/src/widgets/framework.dart': Failed assertion: line 5191 pos 16: 'owner!._debugCurrentBuildTarget == this': is not true.
The relevant error-causing widget was:
════════════════════════════════════════════════════════════════════════════════

════════ Exception caught by widgets library ═══════════════════════════════════
'package:flutter/src/widgets/framework.dart': Failed assertion: line 5191 pos 16: 'owner!._debugCurrentBuildTarget == this': is not true.
The relevant error-causing widget was:
════════════════════════════════════════════════════════════════════════════════

════════ Exception caught by widgets library ═══════════════════════════════════
'package:flutter/src/widgets/framework.dart': Failed assertion: line 5191 pos 16: 'owner!._debugCurrentBuildTarget == this': is not true.
The relevant error-causing widget was:
════════════════════════════════════════════════════════════════════════════════

════════ Exception caught by widgets library ═══════════════════════════════════
'package:flutter/src/widgets/framework.dart': Failed assertion: line 5191 pos 16: 'owner!._debugCurrentBuildTarget == this': is not true.
The relevant error-causing widget was:
════════════════════════════════════════════════════════════════════════════════

════════ Exception caught by widgets library ═══════════════════════════════════
'package:flutter/src/widgets/framework.dart': Failed assertion: line 5191 pos 16: 'owner!._debugCurrentBuildTarget == this': is not true.
The relevant error-causing widget was:
════════════════════════════════════════════════════════════════════════════════

════════ Exception caught by widgets library ═══════════════════════════════════
'package:flutter/src/widgets/framework.dart': Failed assertion: line 5191 pos 16: 'owner!._debugCurrentBuildTarget == this': is not true.
The relevant error-causing widget was:
════════════════════════════════════════════════════════════════════════════════

════════ Exception caught by widgets library ═══════════════════════════════════
'package:flutter/src/widgets/framework.dart': Failed assertion: line 5191 pos 16: 'owner!._debugCurrentBuildTarget == this': is not true.
The relevant error-causing widget was:
════════════════════════════════════════════════════════════════════════════════
...     Normal element mounting (7 frames)```

</details>

### Flutter Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.16.7, on macOS 14.1.2 23B92 darwin-x64, locale en-JO)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.2)
[✓] VS Code (version 1.85.1)
[✓] Connected device (5 available)
[✓] Network resources

• No issues found!
<details open><summary>Doctor output</summary>

```console
[Paste your output here]

@MhmdAlkashif
In order to properly address the issue, please provide us complete runnable but reproducible code sample without any third party package implementation and check if without third party implementation, you get same error or not.

following this issue

Dear @darshankawar
This issue just only happens when I run debug for ios platform
The cause is MaterialApp.router in my case (.../main_application.dart:503:44)

@longphgcs17521 how did you fix the issue

@darshankawar its a big structure, can't provide you a runnable code cause it is company based code

@MhmdAlkashif
I have not fixed yet, I got the issue as your case. Iam following this post to find the solution

@MhmdAlkashif
That's why we need a runnable but reproducible code sample without third party implementation so as to know which area of the framework could be causing the error. Most likely it occurs due to conflict between various packages you are using and looking at the logs, there are entries pointing to provider third party package. Without reproducible code, we can't make the issue actionable. You can search for similar issues o stackoverflow to see if they help to solve the issue.


[firestore-bigquery-export] Support cross-project Bigquery export

Extension name
This feature request is for extension: firestore-bigquery-export
What feature would you like to see?
Ability to specify a different GCP project for BigQuery.
This could be implemented by passing BigQueryOptions when creating the BigQuery client
It's not clear to me to what extent the extension relies on the built-in Firebase/BigQuery link feature and whether that would support a cross-project BQ connection.
How would you use it?
Our backend consists of microservices using Firestore. Because there can only be one Firebase/Firestore instance per GCP project and there doesn't seem to be a native namespacing/isolation mechanism either, in order to isolate our microservices databases we've had to create a separate GCP project to host each service's Firestore.
Our BigQuery instance however lives in the main project, so without cross-project support we can't use this helpful extension.
It looks like custom extensions are not yet supported so we can't make the change ourselves and run it, although I suppose we could simply take the code, make the change, and run it as a Firebase Cloud Function ? Any caveats with this ?
I'm happy to hear about any alternative solutions. If we can't use this extension we're considering a dedicated microservice listening to Firestore changes and writing them to a PubSub -> Cloud DataFlow -> BQ pipeline, or even directly to BQ.

@renaudguerin @i14h I'd definitely support a Cloud Pub/Sub solution, with the data sent unchanged and the metadata (eventId, document_name, action, etc.) passed as attributes.

Closed via https://github.com/firebase/extensions/pull/891


metadata

Include a metadata file with stations and locations

[x] include a stationary file with coordinates and LC
[ ] Think of how to incorporate moving stations, maybe by using a separate file?

stationary metadata added in 537eb47


odrive version bump.

This version bump includes support for copy app. And was a much needed bump. Please merge.

Can you please squash your commits.

I have squashed the commits.


[Bug] weblog.lol: Multiple advanced variables on one line only render one

Bug Description
The example blog post uses an advanced variable called spanmod. It is defined as below:
Spanmod: $content

Using the following code in the post body...
{spanmod:class=1&content=1} {spanmod:class=2&content=2} {spanmod:class=3&content=3}

...produces the output below:
1} {spanmod:class

when I would expect it to output...
1 2 3

Steps to Reproduce
Example blog post: https://maxic.weblog.lol/2022/12/webloglol-bug-report
Raw blog post content: https://maxic.paste.lol/weblog.lol-bug-report.md/raw

This has been resolved. Sorry for the trouble! Turns out it was due to a missing ? in the regex. Regex, amirite?

Regex, amirite?

something something hard problems in computer science :)

Thank you for such a quick reply! It looks like it renders properly now, but only the first advanced variable of a given type given on a line will be rendered each time (e.g. in the example, it should output 1 2 3 but in this post, for example it outputs 1 1 1).
Sorry to be a pain, I imagine this is a super tricky bit of functionality to add but just wanted to flag so you're aware!

Ah, sorry — found and fixed! It was due to a sloppy string replacement process that I got away with only because I hadn’t attempted to do more than one replacement of the same variable on a page. Should be good now, but I won’t tempt fate by closing this like I did I last time. Let me know how it looks on your end!

Thank you! That issue seems to be fixed! 🎉
Slightly different one - an advanced variable that had previously been working no longer replaces some of the $parameters when including it. I can create a new issue if you'd prefer.

My configuration contains...
Footnote: $emoji<input type="checkbox" id="fn-$fnid">$content

...which I've included in the blog post from before as...
{footnote:fnid=1&theme=danger&emoji=x&content=content1}
{footnote:fnid=2&theme=danger&emoji=x&content=content2}
{footnote:fnid=3&theme=danger&emoji=x&content=content3}

...which renders as...
$emoji<input type="checkbox" id="fn-$fnid">content1
$emoji<input type="checkbox" id="fn-$fnid">content2
$emoji<input type="checkbox" id="fn-$fnid">content3

Weird that $content seems to work properly, but none of the other variables do?

Sorry to keep adding to this 😭 none of the fixes are urgent if that helps!

As someone who simply crushed the whack-a-mole game at Chuck-E-Cheese in the 80s, I’m ready to keep at this until everything works flawlessly. Pretty sure I’ve got this where it needs to be now, but let me know if you encounter any other glitches.


[Share Items] share multiple images at once

If your issue is for a particular feature (e.g. Camera, Connectivity, Biometric etc), please prefix the issue title with the feature in square brackets, e.g. "[Camera] Crash when image is captured"
Description
Share multiple images at once. Unfortunately, that doesn't work.
Error messages
no error. message: Share completed. Under debugging: DW.ShareItems.Android.pas not found, but under Project - Delphi Compiler -Serach path I have insert ..\Kastri-master\Features\ShareItems
Please indicate
Delphi Version: Delphi 11.3 Patch 1
Platform(s) that the issue occurs on (i.e. iOS, Android etc): Android 10
If mobile, device model and OS version (e.g. Pixel 3a, Android 11):
Steps To Reproduce
procedure TForm1.Share;
var
LSharedFileName: string;
begin
//LSharedFileName := TPath.Combine('Files', 'Lorem.txt');
// FShareItems.AddText('Share Test');
// Uncomment the following line and comment out the next one, to test sharing of a file
//   FShareItems.AddFile(TPath.Combine(TPath.GetDocumentsPath, LSharedFileName));
FShareItems.AddImage(Image1.Bitmap); // On Android, don't attempt to share an image as well as text
FShareItems.AddImage(Image2.Bitmap); // I have insert a new TImage
FShareItems.Share(Button1, FExcluded);
end;

Looks like it's an exception for later versions of Android. I think the original code was probably tested around Android 8 or 9!
I've pushed a fix for it (in DW.ShareItems.Android.pas, so please try out the changes.

Great job. Works perfect. thx


_convert_convolution in NNVM from_keras has a fatal error of calculation of dilation rate and not inserting ZEROS in the weight list after editing the kernel_h kernel_w

PLEASE look at this function again and fix the dilation rate calculation and don't forget to insert zeros in the Weightlist.

Operator conv2d(channels=64, kernel_size=[3, 5], padding=[0, 0], dilation=[1, 2], strides=[1, 1], use_bias=True, name=conv2d2) expects weight's shape to be [64,32,3,5], but got [64,32,3,3]

Thanks for reporting this. It should be fixed by #1715
The weight shape of dilated conv passed from frontend to nnvm compiler should be the original h and w, not including inserted zeros. NNVM supports dilated conv by inserting a dilate op: https://github.com/dmlc/tvm/blob/master/nnvm/python/nnvm/top/nn.py#L94-L102


Added route for saving paintings to database

Added route for saving paintings to database and used painting scheme
Added frontend save capabilities
Added loop to frontend on account page
Styled the svgs on account page.
Also updated the cross origin policy for live site to work.

Last push was a styling change, pulling


tune rocksdb option for lock cf

After we introduce lock cf, we should tune it with better configuration.
/cc @disksing

https://github.com/pingcap/tikv/pull/906 use different configuration for lock cf.

Using different configuration improves performance?


feature: Handle "Warning: The file has been changed since reading it" natively

Did you check the docs?

[X] I have read all the noice.nvim docs

Is your feature request related to a problem? Please describe.
Currently, this message goes to my regular messages (which I personally use the mini view for):

Describe the solution you'd like
It would be best if this was a user input prompt (i.e. in the middle of the screen), like what happens when you try to open a file that has a swapfile.
Describe alternatives you've considered
I suppose I could set up a filter, but I'm not sure if that would handle getting user input since the message type seems to be msg_show
Additional context
No response

    routes = {
      {
        filter = { event = "msg_show", find = "Do you really want to" },
        view = "popup",
      },
    },

I tried stuff like this but it doesn't seem to work very well, it looks like this message isn't implemented like other input prompts in neovim

I've also been trying to figure out an elegant solution for this. I've been using the notify view for messages and I can't seem to get the lines for the prompt to merge into one notification. The best I've got so far is a route like this:
{
  view = "notify",
  filter = {
    event = "msg_show",
    ["not"] = { kind = { "confirm", "confirm_sub", "search_count" } },
  },
  opts = { replace = false, merge = true, title = "Merge Attempt" },
},

it at least prevents the notifications that pop up from replacing each other, but it still doesn't merge them together. This is what it spits out for me:

ignore that return StatusCol(...)item in there, I'm debugging that separately. Ideally the behavior I'm looking for from noice is just for those three notify bubbles to be combined into one, or to be turned into a confirm popup like the issue author suggests. Appreciate any help I can get.

If anyone knows who would be a good person to reach out to in neovim core, I would appreciate some help getting my first PR merged!


kt-legacy v1.0.5

Destination channel: defaults
Links

PKG-6044
Upstream repository
Relevant dependency PRs:

dependency for keras-tuner

Explanation of changes:

initialize package (forked from conda forge)
linter fixes

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_f8o1un5_3w/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:33: missing_imports_or_run_test_py: Python packages require imports or a python test file in tests.
===== Final Report: =====
1 Error and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_45f3kp4e0a/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:33: missing_imports_or_run_test_py: Python packages require imports or a python test file in tests.
===== Final Report: =====
1 Error and 0 Warnings were found


How to Save Model with TF2.x Keras Multiworker Distributed Training?

Description:
I've created a  Keras model, and trained it with multiworker distributed strategy.
Every worker uses the same python scripts for training. I uses model.save function for model saving with the same hdfs path.
After training, every worker would try to save model to the path, and it will cause race condition, because all of them want to handle the same variables files.
Code snippets
tf_config = {
    "task": {
        "index": 0,
        "type": "worker"
    },
    "cluster": {
        "worker": ["localhost:21834", "localhost:27271"],
    }
}
os.environ["TF_CONFIG"] = json.dumps(tf_config)
print(json.loads(os.environ["TF_CONFIG"]))

def main(argv):
    del argv  # Unused
    BATCH_SIZE = 100
    SAMPLE_SIZE = 50000
    strategy = tf.distribute.experimental.MultiWorkerMirroredStrategy()
    with strategy.scope():
        model = tf.keras.Sequential([
            layers.Dense(64, activation='relu'),
            layers.Dense(32, activation='relu'),
            layers.Dense(1, activation='sigmoid')
        ])
        model.compile(optimizer=tf.keras.optimizers.Adam(),
                      loss=tf.keras.losses.BinaryCrossentropy(),
                      metrics=[tf.keras.metrics.AUC()])
    log_dir = FLAGS.logs
    tensorboard_callback = tf.keras.callbacks.TensorBoard(log_dir=log_dir,
                                                          histogram_freq=1,
                                                          update_freq='epoch')
    train_dataset = tf.data.Dataset.from_tensor_slices(
        (np.random.randint(1000, size=(SAMPLE_SIZE, 31)),
         np.random.randint(2, size=(SAMPLE_SIZE, 1))))
    train_dataset = train_dataset.batch(BATCH_SIZE)
    validation_dataset = tf.data.Dataset.from_tensor_slices(
        (np.random.randint(1000, size=(SAMPLE_SIZE, 31)),
         np.random.randint(2, size=(SAMPLE_SIZE, 1))))
    validation_dataset = validation_dataset.batch(BATCH_SIZE)
    options = tf.data.Options()
    options.experimental_distribute.auto_shard_policy = tf.data.experimental.AutoShardPolicy.DATA
    train_dataset = train_dataset.with_options(options)
    validation_dataset = validation_dataset.with_options(options)
    model.fit(train_dataset,
              epochs=5,
              steps_per_epoch=10,
              validation_data=validation_dataset,
              validation_steps=5)
    model_dir = FLAGS.logs + '/models'
    model.save(model_dir)

if __name__ == '__main__':
    app.run(main)

Question:
In my opinion, the save should only be done by the chief worker not all of them. So

Is there some problem with my save code?
Should I change the path for different workers? If so, which model is the final model for serving?
Is there a way that chief worker saves model only?

Thanks ~

Did you get a chance to see Multi-worker training with Keras example? That should help answer some of your questions. Thanks!

Ideally the save should only be done by the chief worker, but it is a bit unfortunate that currently all workers in MultiworkerMirroredStrategy will try to save the model, and because they run the same piece of code, they will save to the same location. AFAIK the main reason behind this is model.save is not and in principle should not be made to be aware of which worker is running it.
I heard there are plans to make it better. For now you can use different saving paths for different workers , and at the end delete the paths if the code is running on non-chief workers. The model saved by chief worker can be used for serving (in fact models saved by different workers are identical).

@ymodak Yes, I've read that before. But I don't  think it will help with my doubts about  Model  Save

@ckkuang Thanks very much~.  Really helpful to me.


Technical Details on PowerApps visual for Power BI

Probably not the best place to reach out with a question like this, but I am giving a presentation at the Power BI World Tour Chicago on April 9-10th where I will be talking about the PowerApps visual for Power BI.
I was hoping I could sync up with someone that could provide some under the hood details about the visual? I think it would be great to provide some content about how the integration works between PowerApps and Power BI is accomplished.
Thank you!

Hi, @jdobrzen. I've forwarded your request to the owner of this feature and asked him to respond. Closing this issue.


What do i need to make it work with 4.27

Hi how do you compile the binary to make it work with UE 2.27

+ClassRedirects=(OldName="/Script/SpeechRecognition.SpeechRecognitionActor",NewName="/Script/SpeechRecognition.SpeechRecognitionSubsystem")
I got like Script/SpeechRecognition.SpeechRecognitionActor
Severity	Code	Description	Project	File	Line	Suppression State
Error		Unrecognized type 'ASpeechRecognitionActor' - type must be a UCLASS, USTRUCT or UENUM	Sphinx_UE4_Demo	D:\Unreal Projects\Sphinx_UE4_Demo\Source\Sphinx_UE4_Demo\SpeechRecogTestActor.h	25

Works in UE4.27


Reporting - Tool Evaluation

Title of ticket: Tool Evaluation
Description
This ticket is to analyze and document the features and advantages of available reporting tools.
Dependencies
No
DOD

[x] Setup a test data warehouse to be used to build the analytics
[x] Setup the tool on local machine
[x] Check the connectivity to PostgreSQL DB
[x] Check the latency while running direct reports
[x] Check if the tool allow caching of data
[ ] Check if there is an option to triggers emails based on threshold
[ ] Check if there are custom styling options available
[x] Check the available visualizations
[ ] Check the options to apply row level security

@VineetBala-AOT Is this likely to be complete within this sprint? Do you want my help creating a new task with any remaining tasks for next sprint?

Hi @mpilchar , there are two points still need to be tested. We can close this ticket and create a new task with those two for next sprint.


Don't override default browser font

The default font is often set for accessibility reasons, we shouldn't override it. Asking Tailwind to stop doing this would be very helpful.

I had some looking in to this and found that this is defined in the normalization/preflight CSS: https://tailwindcss.com/docs/preflight
One thing that kind of rubs me the wrong way is this:

Unstyled lists are not announced as lists by VoiceOver. If your content is truly a list but you would like to keep it unstyled, add a “list” role to the element

I created a PR to fix both these issues.


Upgrade to work with latest dimod (0.7.7)

In dimod>=0.7.7, SampleSet replaced Response as a more general sample container.

Closed in #11.


Tab sequence when suggestions are shown; need to tab twice to tab to the next field

Although my PR https://github.com/LeaVerou/awesomplete/pull/17254 fixes the issue that in the Talkback screen reader you couldn't select anything from the suggestions, it also introduced a minor annoyance in the tab sequence:

if suggestions are shown and you hit the tab key in the input field to leave the field, it doesn't go immediately to the next field in the tab sequence. It tries to go to the suggestion first. You have to enter the tab key another time to get in the next field.

Luckily there is an easy fix.
Instead of having tabindex 0 on the list items, it is enough to set tabindex -1 to make the list items focusable elements.
I tested this in the Talkback screen reader, and this works just as good and this doesn't disturb the tab sequence.
I will submit a PR for this.
I was thinking about adding a test, but as far as I know, it is not possible to test the tab sequence with Jasmine tests.
In the PR I will also make aria-activedescendant empty when no suggestion is selected. Currently aria-activedescendant keeps pointing to a list item even though the popup with items are hidden. This doesn't seem to cause any issues, but it is cleaner to make aria-activedescendant empty.

PR with the fix is merged. Closes this ticket.


Unable to reuest.

I have tested this and I am unable to get it to connect to a docker-registry service.
I am running docker-registry on centos 6.6
[root@docker ~]# rpm -qa|grep docker-registry
python-docker-registry-core-2.0.1-2.el6.noarch
docker-registry-0.9.0-1.el6.noarch
There is no firewall running and port 5000 is WIDE open.
I have used your github version and it still doesn't work.
Suggestions?

Can you request to your registry at your browser ?
like http://YOUR_IP:5000/v1/search
If your can not, your registry do not allow CORS.
Relaunch your docker-registry with configuration of CORS.
https://github.com/docker/docker-registry/blob/master/config/config_sample.yml#L58
You can enable CORS like following settings at your config.yml
origins: _env:CORS_ORIGINS:[*]


build: bump cosmos-sdk version to v0.44.3

Summary
Bump cosmos-sdk version to v0.44.3
it contains tendermint v0.34.14.

For Admin Use

[x] Not duplicate issue
[x] Appropriate labels applied
[ ] Appropriate contributors tagged
[x] Contributor assigned/self-assigned

We will hold the merge for a while until we are sure of Gaia v6 Vega's cosmos-sdk version.


code insiders: outline view no longer highlights heading matching current cursor position

related to #154645
the current cursor position  in the document, e.g. within #### this heading use to be highlighted in the outline view

Have you set the Follow Cursor option from the ... menu on the Outline view's header?

I owe you a beer @gjsjohnmurray


[RFE] Tag should be an array?

#Feature Request
Request description:
Customer requests that tag field should be an array? (Not 100% on this one but would make sense, need to check the spec of vmwarevsphereconfig to be sure)

The tag field is an array. The helm chart does not enforce this but the Rancher CRD does.
>kubectl explain VmwarevsphereConfig.tag
GROUP:      rke-machine-config.cattle.io
KIND:       VmwarevsphereConfig
VERSION:    v1

FIELD: tag <[]string>

DESCRIPTION:
    vSphere tag id e.g. urn:xxx

@bcdurden Did you check the helmchart before closing this.
Yes the API is an array, the helmchart only allows a single value. The helmchart needs to be updated to allow an array in the values.yaml and be received in the following file
https://github.com/rancherfederal/rancher-cluster-templates/blob/main/charts/cluster-templates/templates/nodeconfig-vsphere.yaml#L40

@zackbradys can you reopen this.


[Swipe to refresh] Swipe gesture won't work if the child composable is not scrollable.

Description
Swipe to refresh doesn't work if the child composable is not scrollable.
Steps to reproduce
SwipeRefresh(state = swipeRefreshState, onRefresh = { viewmodel.refresh() }) {
    ErrorMessage(text = "Error message", modifier = Modifier.fillMaxSize())
}

Expected behavior
Additional context

This is working as intended and documented at https://google.github.io/accompanist/swiperefresh/

Quoting the link

The content needs to be 'vertically scrollable' for SwipeRefresh() to be able to react to swipe gestures. Layouts such as LazyColumn are automatically vertically scrollable, but others such as Column or LazyRow are not. In those instances, you can provide a Modifier.verticalScroll


Canvas resolutions

Describe the Bug
Shouldnt the canvas only be in the middle of the whole page? I would like to take screenshots of exactly the canvas size and compare them in tests, might need to resize the canvas for that so that I can get the exact sizes of the canvas for that and not have other stuff in my screenshots.
Ah I guess this is because you can shrink the other tool areas?
Edit:
I see, I could use the divs above the canvas.
We can close this issue if its no real issue for you.
Steps to Reproduce the Problem
Open the webapp, go to a map, open the dev window.
Expected Result
Be exactly in the middle
Actual Result
Going a bit too far right and down
PermaplanT version
permaplant.net
Operating System
Windows 10
Browser
Opera
Versions of other relevant software/extensions
Additional info/logs

If this is about taking the screenshot, maybe screenshot is not necessary for now, see https://github.com/ElektraInitiative/PermaplanT/pull/760#issuecomment-1663291583
We still should nevertheless look into the canvas, maybe we render something which is never shown because of this overlap. @Bushuo @absurd-turtle do you know something about this issue described here? Is it something worth fixing besides the need for tests?


fixed the-data-model not been updated to Lume 2

The change was copied from docs/core/processors.md.
Supposedly this change is mistakenly missing from edabb6e6.

good catch. Thanks!


[ZEPPELIN-1212] User impersonation support in JDBC

What is this PR for?
Add impersonation support to JDBC interpreters, in addition to Kerberos Authentication to improve auditability in all JDBC interpreters.
What type of PR is it?
[Bug Fix | Improvement]
What is the Jira issue?

ZEPPELIN-1212

How should this be tested?
In JDBC interpreter setting add following properties

zeppelin.jdbc.auth.type = KERBEROS
zeppelin.jdbc.principal = principal value
zeppelin.jdbc.keytab.location = keytab location
enable shiro authentication via shiro.ini

Now try and run any of hive's query (say show tables) it should return with valid results/errors depending on user permission.
Questions:

Does the licenses files need update? n/a
Is there breaking changes for older versions? n/a
Does this needs documentation? n/a

LGTM, at some stage we should start thinking about connection pooling. But that can be a different PR.

Merging this if no more discussion.


Draft Proposal: File Naming Convention

Purpose
As the collection of recipes grows we need to get consistent about naming conventions for the recipe (and other) files.
Proposed Solution
This solution is still in draft form. Feedback actively needed.
The naming convention is intended to encourage clarity and consistency. Getting good recipes into the collection is more important that adhering perfectly to a set of rules. However it is helpful to have a set of guidelines to give everyone a clear path to follow.
Directory Structure
The main project should have a directories named docs, orgs, and samples.

All recipes should be in sub-directories of that directory
All documentation (other than the main ReadMe file) should be in the docs directory
All Org definitions for CCI should be in the orgs directory

The subdirectories of samples should use the common acronym for a project (e.g. npsp, eda) or the full name of the project in snake_case when there is no clearly community understood acronym (e.g. outbound_funds).
Recipe File Names
Recipe file names should be in snake_case, and clearly define the purpose of the recipe, and should end with recipe.yml.

A simple recipe that just generates one or two objects can simply list the object names: Accounts_Contacts.recipe.yml
A recipe that is supporting a specific scenario with those objects should include a purpose: Account_Contacts_Internationalization.recipe.yml
A recipe that is supporting a more complex scenario including several objects should be focused on the purpose of the scenario: Recurring_Donations.recipe.yml

Because recipes should be located in a subdirectory clearly named for the product they are meant to support the file name should not contain a reference to the product.
Documentation File Names
There should be one project ReadMe.md in the project root. All other documentation should be included in markdown format the docs directory.  Files should be named in snake_case. For recipe instructions they should indicated the product name and finish with the word "instructions" (e.g. EDA_Setup_Instructions.md). Any images, or other assets needing for the documentation should be placed in the assets directory in the docs directory.

This helps resolve #17

Updates:
I encountered the limit using Github Actions to validate the recipe.

It requires custom codes to dynamically assigning a recipe file based on the status if we cannot find existing action libraries.
Installing NPSP or EDA takes about 15-20 minutes. We will be well below 2000 free minutes per month but we cannot avoid creating a custom task for each recipe file.

Let me create a ticket for creating a set of custom flows per the recipe folder.

I updated the text to include the .recipe.yml suggestion.

This looks good to me @acrosman :)  it will take a bit of effort to implement with our growing cookbook of recipes.  please feel free to convert to documentation!


feat: add children for radio input form component

Description of the issue
Miss children for radio input component
Person(s) for reviewing proposed changes
@guillaumechervet

Super :D


'Ooops, an unexpected error occurred'

\node_modules\tidalapi\lib\client.js:106
        throw new Error(data)
        ^
Error: {"status":500,"subStatus":999,"userMessage":"Ooops, an unexpected error occurred. We'll try to fix this asap!"}

What causes this issue, and is there anything I can do about it? Thanks.

Having this problem too...

Updated the TIDAL token.

Hi Lucaslg26, I'm getting the same error using the kgsOOmYk3zShYrNP from https://github.com/lucaslg26/TidalAPI/issues/23. Alas I don't have an Android device and the Windows machine doesn't have any obvious token files in the thousands of files in .\AppData\Roaming\TIDAL\Service Worker\CacheStorage\. Would love to contribute to the docs once this is fixed so we can stop bothering you! 🙂

me too

Download an android emulator and get the token with that
On Sep 3, 2017 9:47 AM, "Jan Okoński"<EMAIL_ADDRESS>wrote:

me too
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lucaslg26/TidalAPI/issues/22#issuecomment-326806040,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEHGPDl8AewlB-2OhJ2z0lUdAuL4uE9Eks5seq3bgaJpZM4J75VC
.

How to get token with emulator?

Enable external access in fiddler then use Drony to force all traffic on
the emulator through fiddler
On Sep 3, 2017 2:35 PM, "Jan Okoński"<EMAIL_ADDRESS>wrote:

How to get token with emulator?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/lucaslg26/TidalAPI/issues/22#issuecomment-326822762,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEHGPL8L6Dki7qkLj0c2HUW6NrhSig1Yks5sevFYgaJpZM4J75VC
.

Ok I actually copied it from Pythons tidal api and it works.

@bayrock @jonaaa20 @lucaslg26 @okonek @jbschooley
I found a solution, I assume you guys are using the Android token "kgsOOmYk3zShYrNP", I had the same problem, but I tried to change some stuff.
Apparently, for the android token, you need to set "clientUniqueKey" in the form, when you log in. The funny thing is, it just needs to exist, so you could add a random string to it and it will work :D

The README now has instructions on getting a token
https://github.com/lucaslg26/TidalAPI#obtain-the-tidal-token-needed-to-use-this-api

@mikemaccana the problem is not that, the problem is that the package does not work out of box with the android token "kgsOOmYk3zShYrNP", that is extracted from the APK. :)


Feature: activeLabelStyle and activeTabStyle

Version
Tell us which versions you are using:

react-native-router-flux v4.0.0-beta.21
react-native v0.48.4

Expected behaviour
Since we have a labelStyleand tabStyle along with activeBackgroundColor and activeTintColor, it would be handy to have activeLabelStyle and activeTabStyle which would be styles that could be passed in and applied when that tab is currently selected

I've ditches these all together and am using the icon prop to get all of the styling for inactive and active states on the icon and text. See my example here


Bosses of the Elementals, lots of tryhard Boss fight designs and "Soul Stones" mechanics

So, inspired by the last Vlog about Boss examples and some unique ways to defeat them, I came up with an idea of not only making the fighting style of Boss unique, but also helping players to possess something one and only in each game What if we take the mechanics of some boss and create some item(or more like an orb effect) that actually contains some significant part of their powers.
Exemplary boss concept(not mine) with few topic related changes
For example, lets "steal" the idea from one of other suggestions about sunlike Phoenix Boss  (it might be any other, but I really liked its concept and also this one should illustrate the idea in most obvious way) and modify it a little. Lets make this boss some kind of spellproof guy, with not that much of physical resistance, stick to idea of him blinding enemies (causing disarm effect in 600 AOE for about 3 sec) when they stare at him while he casts any of his spells (the casting itself does not cause the blinding effect, but when spell is done it creates the "Blinding flash"). Also I would like to suggest some changes for the Boss arena, because in the given state I see no funny interaction helping to defeat the Boss and not only to annoy players, slipping into lava of his skills all the time. So lets make his habitat all bloomy and green, having some high rocks near the edge of the map. And there in the middle on some sort of pedestal is going to be an egg, which turns into the Phoenix at the start of the boss fight. He is going to glide around casting spells and hitting enemies in his reach (in my head, it seems like he should be more passive kind of a boss that doesn't really want to fight and has to be provoked by spell of regular attack). Both his attacks and skills cause "Sunburn" debuff, dealing damage for 4 sec and reducing rightclick damage for 5% for a minute (it stacks and refreshes, but also gets purged) .There are also 4 crystal pillars around the pedestal. They are capable of protecting from Phoenix's skills in a small area behind them and restoring health and mana for all heroes around for every spell blocked, to help players in late stages of the fight. What is going to be unique about this Boss?  But in exchange, just as regular Dota 2 Phoenix, his skills will require not only mana but also his HP, providing him heals for each hero it hits (restoring about 25% of spent HP for a hero hit).  But if somebody finds this way too slow, there gonna be 2 waterfalls on 2 different edges of the arena, causing aghanim "Gush" effect on activation (has 1 min cooldown) in a small range around it.  This gives at least 2 possible ways of fighting the boss (exhausting or active one; the choise depends on your fighing capabitilies and what damage type prevails in your team).
Now in short about the stages:
1st - I like the original idea about Lina's stun ability adding him capability of making some usual hits between times.
2nd (75 % HP)- As we decided to make the blinding effect some kind of passive, I think that those "sun grenades" are actually really neat idea for the second stage. They should have the same mechanic as regular Phoenix's fire spirits, with their effects slightly changed.
3rd (35% HP) - Our Phoenix is almoust out of HP and goes to berserk mode. At this stage the number of his "sun grenades" is x3 and the cooldown is twice lower. He furiously bombards the arena in circles, targeting ground ( not players). Here is also another use for waterfalls, which now can't be used to stun the boss (because he is not in range), but are capable to make your rightclickers fight in full power, without worrying about debuffs caused by the boss.
4th (0% HP) - Finally, Phoenix is basically dead and he Icarus Dives into the pedestal, he was on at the very beginning of the fight, turning himself into an egg, trying to reborn. He causes magic explosions every five second (these explosions have his passive effects, so u still have to avoid looking straight on the egg, while it explodes. In the worst case scenario, on the 6th flash (in 30 seconds) he will rise again (OMFG). U and your team have to hit the egg with 30 instances of phys damage before that happens and u won. Congrats!
The "Soul Stone"
And here comes the new hero mechanics! (finally!!!) On death he drops all kinds of items around the pedestal (just casual boss loot, like in usual AA). But on the pedestal itself is going to be some another thing. Not just a regular Item, but more like a blessing(or a curse) - "The soul of fire" (or some other nameless disaster xD). It gets consumed by one of the heroes and turns into a passive effect (much like a consumed Moon shard). For this specific one the effect will be something like this:

Spell Damage resistance (+15% - +60%) (to the base of 25%). Increases for 1% for every instance of enemy hero spell damage "tanked"
Spell Damage amplification (+15% - + 60%). Increases for 1% every time your spell hits enemy hero.
Passive effects:
Adds "Sunburn" effect to your attacks.
Every time you cast a spell, enemies within the range (200-800), looking in your direction, get a "Sunburn" effect and "Blinding flash" effect on them (the continuety is twice lower than Phoenix's ones). The range increases for 15 for every enemy hero hit with this passive.
10% lifesteal from spells
Every spell cast takes 5 % of your current HP and converts it into additional damage
Negative effects

Physical damage resistanse (-5% - - 35%). Decreases for 3% for each death.

Conclusion
So, as you can see, this effect has two sides, both positive and negative, but provides an absolutely different gameplay style for a player, who has obtained it.
So, that's my suggestion, Though all these numbers barely matter, they show the basic idea. Create an impression that player, who actually consumed one of these souls, kind of obtained the essense of the boss himself. And yes, with only one of such things in game there won't be any balance at all. However, if you add, lets say, at least 3 more of these unique artefacts into the game, getting them and fighting to make them even more powerful (that is also + one more activity motivating factor in game) is going to be another one exciting part of the game mode.
Afterwords
I already have some ideas about other boss arenas and their "Soul stone" effects.  And with my english skills below average, reading all of it must be a real torture, so I don't think that even half of the readers have reached the main point. However, I still would be happy to see your responds for my ideas and hope that at least some of these thoughts will make it through into the final game mode, in one way or another.

The original boss idea belongs to JackGrayling. https://github.com/AngelArenaAllstars/suggestions/issues/56
I'm sorry for merciless distortion of your concept and thanks for giving me some base to start with!

Thanks for the post! Boss items which contain parts of the boss mechanics have been suggested, and are in the game. So I can say with confidence that most of the team thinks it's a great idea.
About the boss: if you have ideas to alter a boss, please post them on the original issue. Also, please format it more clearly, as it is currently it is hard to read.
The item idea looks interesting, although I dislike how its stats change with deaths and tanking spells. Also, I don't believe it should be a consumable. Effects like this should take item slots, and it also robs us of an item upgrade path.

Thanks for your respond! Yey, that's already something!
Okay, next time I will. Though I thought that these changes were kind of too much to keep sticking to the original post.
Well, that was just an example. I just thought about all kinds of possible spell interactions and that's what came to my mind.
And although upgrading boss items (as usual one) is a fine idea in general, that would kind of kill the mechanics of upgrading an effect buy the actual game activity (because the idea was to bring into the game some other upgrade mechanics, except buying (or collecting) stuff. In somelike a "bloodstone" way of upgrading - the more you kill, the more powerful you are). Well, if only you keep the collected effect on the item after upgrading it.
Will keep working on those and try to give some interesting suggestions next!

Any update on this? #37 has a useful template for formatting which would help with clarity.

This ticket is very confused, but I took some of the ideas and posted in #331. Closed.


Four lessons render no output

Perhaps I'm missing something, but I find that lessons 20-23 (lighting 4&5, cel shading, gooch shading) don't render any model (neither the "expected" nor the user-defined versions).
The two lighting lessons (4&5) render squares flying around (which I take to be the point lights), but the Stanford dragon doesn't render at all. (Sometimes it shows up for a moment when refreshing the browser.)
For the two shading lessons (npr 1&2), no GLSL output renders at all. Just the lesson UI.
Lessons 24 (game of life) and onwards appear to work normally.
This is all for a fresh install of shader-school, without any edits to the user versions of the scripts.

I am experiencing the same thing, "Point Lights" and "Multiple Lights" render the colored squares only, and the "Cel Shading" and "Gooch Shading" render nothing in Chrome Version 40.0.2214.115 (64-bit) on a MacBook Pro with NVIDIA GeForce GT 650M.
However, the same lessons work correctly in Safari v8.0.3.
Output missing completely in FireFox 34-36.
--
Thanks for all of the hard work on this awesome project, it is very appreciated!

Thanks for the report, will look into this next week.

Fixed


Perf: register a file provider in the ext host to avoid certain roundtrips

This builds on top the work of https://github.com/microsoft/vscode/pull/136657 and enables a shortcut of file system operations that target the file scheme.
We instantiate the DiskFileSystemProvider that is the provider used in the workbench and everywhere for file scheme in the extension host and delegate to it. Since this required node.js layer, we need to register a version of ExtHostConsumerFileSystem for node and for web differently.
The existing src/singlefolder-tests/workspace.fs.test.ts test suite is actually covering the changes nicely.
//cc @dbaeumer for originally asking for this

Love it. Tho, I am not a fan of extending ExtHostConsumerFileSystem just so that we can invoke a public method on it. We don't have a proper contribution mechanism but you be able to run node-specific code here which then takes a dependency on the new IExtHostFileSystem service.

@jrieken that is the entry point I was looking for 👍 , addressed in https://github.com/microsoft/vscode/pull/181107/commits/24ef435fee9a30b658f954a5cbbe7068421989e1

Very cool. @bpasero thanks for providing it.


[BUG] Date format does not change

For whatever reason, when using the settings to change date. No matter what I do there: the app will always display the date as mm/dd regardless of the date settings.
I wanted it to show it in dd/mm is that implemented and I am missing something? I tried the built-in settings but couldn't get them to work.

The date on the homepage can only be displayed as mm/dd at the moment. And the settings for the date display format are applied to the detail page.
However, I am considering adding settings to change the date display on the homepage in future versions. Thank you very much for your suggestion.

 Change date display on homepage


Single digit fraction parsing

Currently, adding these two lines to money_parse_test.dart would fail:
      expect(euro.parse('€EUR10,2', pattern: 'SCCC0,0'),
          equals(Money.fromInt(1020, euro)));

This results money2 parsing 10.02 EUR, instead of 10.20 EUR.
Should/Could this plugin perform differently here or would this be considered a client task to transform the input beforehand?

I would view this as a bug.

Fixed in 2.0


Regenerate YAMLs for GCST90268462 to GCST90268500

Corrected sumstats have been provided by the author for GCST90268462 to GCST90268500.
I have deleted the old sumstats and moved the corrected sumstats into the staging folders.
YAMLs now need to be re-generated for these GCSTs.

Testing the following for the new metadata yaml update feature:

[ ] https://ftp.ebi.ac.uk/pub/databases/gwas/summary_statistics/GCST90268001-GCST90269000/GCST90268462/
[ ] https://ftp.ebi.ac.uk/pub/databases/gwas/summary_statistics/GCST90268001-GCST90269000/GCST90268463/
[ ] https://ftp.ebi.ac.uk/pub/databases/gwas/summary_statistics/GCST90268001-GCST90269000/GCST90268464/
[ ] [ ] https://ftp.ebi.ac.uk/pub/databases/gwas/summary_statistics/GCST90268001-GCST90269000/GCST90268465/

All tests passed. Regenerated all other metadata YAML files; expect them on the public FTP tomorrow.

New metadata YAML files and md5sum.txt files are now available on the public FTP. Please verify: https://ftp.ebi.ac.uk/pub/databases/gwas/summary_statistics/GCST90268001-GCST90269000/


Group chats hi-fi styling

The first in many messaging pull requests

This is already getting big so I'll stop it here for review.
Questions: Some things I'm not sure if I should be styling individual components where they are used or styling for everything.  I'll go through and add some comments.

This is already getting big so I'll stop it here for review.
Questions: Some things I'm not sure if I should be styling individual components where they are used or styling for everything.  I'll go through and add some comments.

Noticed: Buttons next to message title should have outline, send button is stretched on desktop

Noticed: Buttons next to message title should have outline, send button is stretched on desktop


node-gyp problem gyp ERR! This is a bug in node-gyp.

> node-gyp rebuild

gyp ERR! Completion callback never invoked!
gyp ERR! System Linux 2.6.32-431.23.3.el6.x86_64
gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /space/node/cherry/node_modules/oracle
gyp ERR! node -v v0.10.29
gyp ERR! node-gyp -v v0.13.1
gyp ERR! This is a bug in `node-gyp`.
 Try to update node-gyp and file an Issue if it does not help:
gyp ERR!     <https://github.com/TooTallNate/node-gyp/issues>
npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 6
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is most likely a problem with the oracle package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls oracle
npm ERR! There is likely additional logging output above.

npm ERR! System Linux 2.6.32-431.23.3.el6.x86_64
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! cwd /space/node/cherry
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.14
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /space/node/cherry/npm-debug.log
npm ERR! not ok code 0

 Try to update node-gyp and file an Issue if it does not help:

npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is most likely a problem with the oracle package,
npm ERR! not with npm itself.
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls oracle
npm ERR! There is likely additional logging output above.

https://github.com/joeferner/node-oracle

I've done everything as I could but the problem isn't resolved yet!

@naeem1098 please update npm:
npm install --global npm

@naeem1098 please update npm:
npm install --global npm

Thank you @joaocgreis,  I've already solved this with node-pre-gyp.

@naeem1098  How did you fix this,  still cannot resolve.

Why comment on an issue that is over 5 years old?  Clearly much has changed since then.
gyp ERR! node-gyp -v v3.8.0 is a problem.  Click the label above to see other issues about using out of date releases of node-gyp.

@naeem1098 How did you fix this, still cannot resolve.

I did explicitly installed the node-gyp at that time. It was needed to me for brain.js I think.

Sad this is still happening. I've nuked Node.js and Visual Studios and reinstalled. Not sure what to do might have to completely wipe computer.

If you are running node-gyp v3 when the current version is v7 perhaps you need to upgrade node-gyp.

It would be nice to be able to do that, but it is a transitive dependency, and there doesn't seem to be a good way to force a given version of a transitive dependency, at least nothing I've tried works.  I tried updating the top level dependency to a newer version, but that breaks other things that don't have newer versions to apply.  This is in a yarn project, and it just isn't obvious how one forces an update.

It would be nice to be able to do that, but it is a transitive dependency, and there doesn't seem to be a good way to force a given version of a transitive dependency, at least nothing I've tried works. I tried updating the top level dependency to a newer version, but that breaks other things that don't have newer versions to apply. This is in a yarn project, and it just isn't obvious how one forces an update.

Found a solution to allow upgrading node-gyp.  The problem is if you are using a multi package.json setup, then only the resolutions in the TOP package.json count (even if your dependency comes from a child package.json), so if you add to the top level package.json the lines:
"resolutions": {
    "**/node-gyp": "8.4.1",

then it will over-ride the child dependency version.


Refs #23919 -- Replaced smart/force_text by smart/force_str.

Keeping smart/force_str and smart/force_bytes in Python 3 is more
sensible because that mirrors the str and bytes types.
smart/force_str and smart/force_text were identical on Python 3.
However smart/force_text was much more commonly used given Django's
strong support for unicode.

Just thinking: smart/force_text should be deprecated and removed (in django 3.0)?

Yes I'll add them to https://code.djangoproject.com/ticket/27753 for later deprecation.

I didn't think about backporting.
Let's stick to force_text in Django itself but recommend force_str in the documentation, then.

Updated with a new version that doesn't include significant code changes, only docs changes.

My latest thinking is to let Claude complete his audit that removes as many force_text() usages as possible, then make the originally proposed change of changing all force_text() to force_str() along with sufficient documentation notes about the changed semantics for older code that still supports Python 2. Although it will require some thinking when doing backports, I think this leaves master in a less confusing state.

Closing per Tim's feedback.


Add World::State

This PR addresses #261 . Based on discussion on #263, this PR creates WorldState struct and provides equals method to compare with other WorldStates.

Before creating a pull request

[x] Document new methods and classes
[x] Format code with make format

Before merging a pull request

[ ] Set version target by selecting a milestone on the right side
[ ] Summarize this change in CHANGELOG.md
[ ] Add unit test(s) for this change

Just to clarify some things about the semantics in DART:
Skeleton::Configuration follows the classical concept of a robot configuration, which is basically a glorified vector that describes only the relevant components of the robot state using as few parameters as possible. This is usually all that's needed for kinematic planning.
Skeleton::State contains a perfect and complete description of the state that the robot is in, making it suitable for perfect recreations of fully dynamic simulations. The Skeleton::State class is extensible, so if users add their own "Aspects" to the Skeleton or any of its BodyNodes or Joints, then the state information of those Aspects will also be captured by the Skeleton::State. The most concrete example of this can be seen in SoftBodyNode: The deformation of the soft body is captured in a Skeleton::State, but it is not captured in a Skeleton::Configuration.
Since the World::State implementation here is building off of Skeleton::Configuration, you might want to consider naming it World::Configuration. That would leave you with an opportunity to create a World::State later on which could build off of Skeleton::State and capture more than what this current implementation is able to.

Thanks for the comments @mxgrey .
Indeed, what you described is precisely why I chose to use Skeleton::Configuration instead of Skeleton::State. Skeleton::Configuration has everything we need from Skeleton for kinematic planning. I initially thought of calling ours as World::Configuration, but the reason why I decided to go with World::State is because, although the current version only contains skeleton configurations, World::State should contain everything we need for kinematic planning in aikido, which might include a set of collision groups(dart::collision::CollisionGroup) or collision constraints(aikido::constraint::CollisionFree), or joint limits, etc.
In fact, now might be a good time to discuss whether to put in collision groups or anything else, to make World::State contain everything we need for making planning calls. Any thoughts @mkoval @jslee02 @brianhou @mxgrey ?
Additionally, I think I'll add WorldStateSaver, just like aikido::statespace::dart::MetaSkeletonStateSpaceSaver, but it seems like once we have the former we might not need the latter too much. In general, shouldn't planners take World to restore after planning as well as MetaSkeletonStateSpace to plan with? Restoring World should include restoring MetaSksletonState .

You may want to consider putting information like collision groups and constraints into a World::Properties data structure, assuming those are parameters that describe the scenario and don't change over time. That way, if you're recording or comparing states for a scenario, you can be a little leaner in terms of memory usage and the reduce the number of operations that are performed in a comparison.
Note that the Skeleton::Properties class records time-independent information like joint limits.

@brianhou @mkoval Could you review this?

@brianhou could you give it a (hopefully) final pass? :)

@mkoval Thanks for the feedback! I agree that saving/restoring a smaller subset of the world which gets modified during planning is a better idea, which we're not currently doing in magi. I think it'd still be useful to be able to take a snapshot of the world's current state, for example, in serializing/deserializing, etc. We might want to support selective state saving/restoring in the near future, so I'll leave it to #276.

There also seems to be a bit of detailed comparison that needs to be done in order to say whether two skeletons have the same "state space", which is necessary when we are doing == operation or setState operation. I am leaving that for later and just comparing skeleton names for now.

I think comparing Skeleton names is fine for now. I agree that comparing StateSpaces is a giant can of worms - and I don't have a good solution in mind. Let's revisit that issue once we have some solid demos running in Aikido on HERB. Then we'll have some more context for the discussion.


#584 Fix IRC line splitting

Rewrite of the line-splitting functionality... including unit-tests. 🎉

I think it would be useful to make getSubLines a helper.go function.
So it can be reused for other bridges that also have line length limits.
WDYT ?

Sure. Will do.

Great job, thanks! 👍


docs: update find_class documentation

Description: Update the documentation of find_class method as it seems to accept / and . and using / should be less confusing as this is what env->findClass expects.
Risk Level: None
Testing: Manual confirmed that the current implementing of tagging works and it does uses / as opposed to ..
Docs Changes: N/A
Release Notes: N/A
Signed-off-by: Rafał Augustyniak<EMAIL_ADDRESS>

/retest

/retest


Fix cargo files that were broken after the last commit

Description

Performance / NEAR gas cost considerations

Testing

How should this be reviewed

Additional information

@karim-en keep in mind, that aurora-is-near/aurora-eth-connector/pull/68 do the same.


I can not get the futures options chain

I have a problem to get options chain for British Pounds Futures. I tried to use "/6BH9", "^6BH9".  Is it any bug?

Problem resolved. I re-programmed that to PHP and add new endpoint for futures.  /futures-option-chains/{$ticker}/nested


Speedup tests on Windows platform - Part 1 (more to come)

In many cases specifying tools=[] in some or all of the Environment() statements in the tests and/or  adding
DefaultEnvironment(tools=[])
Will speed up the tests. This shortcuts looking for MSVC and/or MSVS installs which can be several seconds depending how many versions of MSVC are installed on the system.
These changes should not change the functionality of the test.

[X] I have created a new test or updated the unit tests to cover the new/changed functionality.
[X] I have updated master/src/CHANGES.txt directory (and read the README.txt in that directory)
[X] I have updated the appropriate documentation

Do we know why the msvs steps are so expensive? I'm assuming they actually do some work, because just looking in a few places for a tool should be quite cheap.

@mwichmann  - Yes. It shells out a few times. Creating processes on Windows is expensive. (compared to linux, mac,unix,etc)


freefolating_gazebo problem

I am a student in Portugal and I am developing an autopilot for a tele-commanded sailboat and I found your simulator.
When I installed the simulator, it is not possible to use freefloating_gazebo, the folder is empty and I can not manually put files.
When I access the folder in github, a "NOT FOUND" window appears.
Thanks any help
best regards

Hello
Last week, we missed a commit error on our submodule. Can you pull again the repository?
I think you should execute again the following commands:
git pull
git submodule update
Regards,
Marcelo

Bom dia,
O que recomendou fazer: git pull e submodule update funcionou.
No entanto, existe outra situação.
Coloquei um novo issue no github.
Cumprimentos,
Bruno Pinto.

De: marceloparavisi<EMAIL_ADDRESS>Enviado: terça-feira, 26 de março de 2019 18:19
Para: disaster-robotics-proalertas/usv_sim_lsa
Cc: brunopinto900; Author
Assunto: Re: [disaster-robotics-proalertas/usv_sim_lsa] freefolating_gazebo problem (#15)
Hello
Last week, we missed a commit error on our submodule. Can you pull again the repository?
I think you should execute again the following commands:
git pull
git submodule update
Regards,
Marcelo
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/disaster-robotics-proalertas/usv_sim_lsa/issues/15#issuecomment-476783744, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aui5ezrl4YmMAG6hpFMZ53H0OM_1wXhrks5vamTLgaJpZM4cDdlE.

Olá Bruno
Vou fechar esse issue e passamos a conversar por lá.
Atenciosamente,
Marcelo

Boa tarde,
Está funcionar correctamente.
Muito obrigado.

De: marceloparavisi<EMAIL_ADDRESS>Enviado: quarta-feira, 27 de março de 2019 19:06
Para: disaster-robotics-proalertas/usv_sim_lsa
Cc: brunopinto900; Author
Assunto: Re: [disaster-robotics-proalertas/usv_sim_lsa] freefolating_gazebo problem (#15)
Closed #15https://github.com/disaster-robotics-proalertas/usv_sim_lsa/issues/15.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/disaster-robotics-proalertas/usv_sim_lsa/issues/15#event-2234206340, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aui5e51-s1zlyQPyrXiOAOvz1m9y2YGBks5va8EtgaJpZM4cDdlE.


Compressed Bitmap Caching for Facet Data

At least the implementation I proposed does not really use space efficiently when storing facet data, and memory consumption is not efficient. A compressed caching could reduce the storage space required for facet data, as per thispaper on Dynamic Faceted Search.
We could explore libraries or algs that support compressed indexing like Roaring bitmaps.

Yes you are right. The time and space complexity should be put into consideration as well. I will find time to go through the paper prior to the meeting. Thank you.


Add jsDelivr hits badge

Hey, I noticed that Swiper gets 8M hits per month on jsDelivr, so I thought you might like this badge.

Thanks


feat: introduce vector property popup

Thank you for submitting a pull request!
Description
Introduced properties editor popup (like raster one) to vector legend.
moved some minor properties to the popup

heatmap

symbol

line

fill

no changes
Type of Pull Request

[x] Adding a feature
[ ] Fixing a bug
[ ] Maintaining documents
[ ] Adding tests
[ ] Others ()

Verify the followings

[x] Code is up-to-date with the develop branch
[x] No build errors after pnpm build
[x] No lint errors after pnpm lint
[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check
[x] Make sure all the existing features working well

Changesets

[x] If your PR makes a change under packages folder that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Refer to CONTRIBUTING.MD for more information.
┆Issue is synchronized with this Wrike task by Unito

I fixed close icon position and popup size.

I moved opacity tab to popup for both raster and vector


Filter out the CoPyright property for WGo.js

It breaks IGS uploads and @git-oca's been having to do it manually.

The simplest way of dealing this turned out to be adjusting the regular expression WGo.js used to parse property IDs to accept lowercase letters. On a relatively casual inspection, it looks like WGo still parses everything correctly, but it no longer chokes on CoPyright.
41241cf83b20e03519a8bad9fd51c46356e29ab9
Let me know if you spot any funny side-effects!

Cool ! I just upload that game http://gokibitz.com/kifu/4k7nqNXm without doing any modification and that worked just fine !
Thanks a lot for making things easier for us even when the problem is not in your application !

No problem! And thanks, as always, for helping make GoKibitz better. :) I
really appreciate it!
On Wed, May 6, 2015 at 1:14 PM, git-oca<EMAIL_ADDRESS>wrote:

Cool ! I just upload that game http://gokibitz.com/kifu/4k7nqNXm without
doing any modification and that worked just fine !
Thanks a lot for making things easier for us even when the problem is not
in your application !
—
Reply to this email directly or view it on GitHub
https://github.com/neagle/gokibitz/issues/72#issuecomment-99541460.


Second Contribution by Sajid Khallow

Name: Sajid Khallow
Projects Analyzed: GNU Radio | OpenJS Foundation
Project Link: GNU Governance Model

Hello Sajid, you need to write a written comparative analysis in your issue.
It has to include their similarities, differences and your opinion on which of them has the best governance model.
The word limit is 400 words.
I hope this helps.

Hey @Chimnwendum Thanks and I know. I mistakenly clicked ctrl + enter. I am just editing things right now.

@arliss-NF Second task completed.


[doc incomplete] Error through quick_start doc

Ⅰ. Issue Description
Cannot success through quick_start doc.
Ⅱ. Describe what happened
Cannot reproduce through quick_start and I found an error in the logs by docker exec dfclient cat /root/.small-dragonfly/logs/dfclient.log.
2019-07-01 08:48:00.159 ERRO sign:24-1561970880.159 : Connect to node:<IP_ADDRESS>:8002 error: dial tcp <IP_ADDRESS>:8002: connect: connection refused

Dfget cannot access localhost:8082 because dfget and supernode are in different containers so they have their own localhost.
IMO one of the solutions is to specify the supernode ip via --node when starting dfclient container.
Ⅲ. Describe what you expected to happen
Can see the downloading logs just as the quick_start shows.
downloading piece:{"taskID":"00a0503ea12457638ebbef5d0bfae51f9e8e0a0a349312c211f26f53beb93cdc","superNode":"<IP_ADDRESS>","dstCid":"<IP_ADDRESS>-95953-1553845720.488","range":"67108864-71303167","result":503,"status":701,"pieceSize":4194304,"pieceNum":16}

Ⅳ. How to reproduce it (as minimally and precisely as possible)

Ⅴ. Anything else we need to know?
Ⅵ. Environment:

dragonfly version:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

/assign

I have test it works and the previous guide is wrong


"API USAGE OVER TIME" show empty data

"API USAGE OVER TIME" Widget show 0 API invocation when non subscribed application is selected. ideally it should not show any data.
Dashboard: Manager Analytics
Page: API Usage

Since the data plotted is accurate, we will not be changing this behavior.


Automatically adjust plotly figure width

Is your feature request related to a problem? Please describe.
When I change the browser width the plot for the current tab is adjusted, but when I change tabs the plots for the other tabs will not be automatically adjusted and I have to manually do that in the figure 'reset axes':
Describe the solution you'd like
Plot width is automatically adjusted when I change tabs.
Describe alternatives you've considered

Additional context
GIF showing the current behavior:

Hi @raphaeltimbo, thanks for putting the demo book up.
In both sphinx-tabs and sphinx-panel we hide the content on tabs which aren't selected. According to plotly/plotly.js#2769, plotly can't know what the size of it's parent element is when the element is hidden. Therefore, it can't resize until the element is no longer hidden. Even then, the chart doesn't refresh until you interact with it.
It seems like a rare issue and the plot does resize correctly if a user interacts with it in any way. But if this is likely to occur often in your use case, you could write some JavaScript that uses Plotly.Plots.resize() to trigger the plots to resize every time the tabs are changed.
I don't know if plotly could be adjusted to detect when a chart stops being hidden, but I'm afraid this probably wouldn't be fixed in either tabs package. Shall leave this open, in case someone suggests a workaround or others are interested!

Thank you for the explanation @foster999 .
I went through some related issues to the one that you linked here and found the following js code to trigger the resize when the user clicks the document:
document.addEventListener("click", function(){
    window.dispatchEvent(new Event('resize'));
  });

Feel free to close the issue and thank you again for looking into this.

Thanks very much for following up with the workaround, that's great to know 😊


Changed avatar OSC config export to nest into an 'Avatars' subfolder.

This will make the OSC config subfolder structure in-line with VRChat's own OSC config subfolder structure.

Whoops accidentally included my .csproj file, let me correct that

Looks like you've done it yourself just now! No need for PR now


reactions: Add Reaction popover.

This PR fixes #8679 and adds reaction popover to be used instead of html 'title' attribute.
See this for more discussion - https://chat.zulip.org/#narrow/stream/101-design/subject/reaction.20popover

@HarshitOnGitHub Thanks for this detailed review. I will surely address all the problems as soon as I get some time from college stuff! :)

@HarshitOnGitHub I've updated the PR, can you please review it and let me know if more work is required! :)

@HarshitOnGitHub I've updated the PR, you may check! :)

@Kumar-Tarun Thanks for quick reply! Just noticed one more thing which is that on sliding the mouse over a reaction, the popover also slides which looks really bad:

On inspecting a little bit I found that you need to use mouseenter and mouseleave events instead of mouseover and mouseout events. Search for mouseenter vs mouseleave and mouseover vs mouseout for more info.
Otherwise this is looking great and seems to be ready for a final review from @timabbott mod the event related changes. :)

@timabbott This is ready for a final review from you! :)

@Kumar-Tarun Did you close this PR accidentally?

@HarshitOnGitHub Oh sorry, I was closing some other PR and by mistake closed this one, sorry again for the trouble! :)

Closing in favor of #10266.