Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jan21 runtime deglobal 3 #6852

Draft
wants to merge 33 commits into
base: master
Choose a base branch
from

Conversation

sjmiles
Copy link
Contributor

@sjmiles sjmiles commented Jan 21, 2021

No description provided.

Scott J. Miles and others added 30 commits December 7, 2020 17:33
Unbinding from an Android service is only an indication that the client no
longer wants connected/disconnected events from the storage service, and that
from the client's point of view, it is OK for the service to shut down.

But it *doesn't* make any acquired bindings stop work. This means that we
called close, and then called idle, which succeeds, since the binding still
works.

The `idle` call coming in after `onUnbind` was causing a store to get
re-created (and then never cleaned up, since the binding in question would
never be bound/unbound again).

PiperOrigin-RevId: 346218079
… instead of accessing the StorageMeyManager.GLOBAL_INSTANCE directly.

I've only updated some really simple usages to use the DI pattern. There shouldn't be any change in behaviour; everything still points to the global singleton instance for now.

PiperOrigin-RevId: 346223334
add a comment saying it is a test for the generated entity classes
use fixture entities
test more field types

PiperOrigin-RevId: 346237958
PiperOrigin-RevId: 346255649
Coverage: 91.49% (inline protected method not covered, but tested indirectly)
PiperOrigin-RevId: 346367830
These deps will be required soon due to a change in strict deps handling related to type aliases.  Please do not remove these dependencies before b/169293220 is fixed, or risk breaking your build.

Tested:
    TAP --sample ran all affected tests and none failed
    http://test/OCL:346364948:BASE:346351027:1607454378105:b69dba0a
PiperOrigin-RevId: 346386927
…est.kt

with a comment saying it is a test for the generated references

PiperOrigin-RevId: 346404540
PolymerLabs#6734)

Closes PolymerLabs#6734

COPYBARA_INTEGRATE_REVIEW=PolymerLabs#6734 from mmandlis:schemafields-inline a00ce68
PiperOrigin-RevId: 346411248
… relationship between them.

#codehealth

PiperOrigin-RevId: 346417894
PiperOrigin-RevId: 346422565
Add error message for CollectionHandle init

Closes PolymerLabs#6690

COPYBARA_INTEGRATE_REVIEW=PolymerLabs#6690 from SHeimlich:collectionHandle dd7e309
PiperOrigin-RevId: 346455417
The latter in particular removes a decent amount of complicated, unused logic.

PiperOrigin-RevId: 346456956
PiperOrigin-RevId: 346459397
Due to the Copybara process, the correct import order is not always the
same, so this lint check is proving to be very annoying.
Scott J. Miles added 3 commits December 10, 2020 12:38
…ll-deglobal-3

# Conflicts:
#	shells/tests/arcs/ts/runtime/arc-test.ts
#	shells/tests/arcs/ts/runtime/multiplexer-integration-test.ts
#	shells/tests/arcs/ts/runtime/plan-consumer-test.ts
#	shells/tests/arcs/ts/runtime/products-test.ts
#	shells/tests/arcs/ts/runtime/slot-composer-test.ts
#	shells/tests/arcs/ts/runtime/transformation-slots-test.ts
#	src/planning/plan/tests/plan-consumer-test.ts
#	src/planning/plan/tests/plan-producer-test.ts
#	src/planning/plan/tests/planificator-test.ts
#	src/planning/plan/tests/planning-result-test.ts
#	src/planning/plan/tests/test-environment-test.ts
#	src/planning/strategies/tests/coalesce-recipes-test.ts
#	src/planning/strategies/tests/search-tokens-to-handles-test.ts
#	src/planning/tests/planner-test.ts
#	src/runtime/recipe/tests/recipe-test.ts
#	src/runtime/runtime.ts
#	src/runtime/storage/drivers/driver-factory.ts
#	src/runtime/storage/tests/active-store-test.ts
#	src/runtime/storage/tests/direct-store-muxer-test.ts
#	src/runtime/storage/tests/firebase-store-integration-test.ts
#	src/runtime/storage/tests/ramdisk-direct-store-muxer-integration-test.ts
#	src/runtime/storage/tests/ramdisk-store-integration-test.ts
#	src/runtime/storage/tests/reference-mode-store-integration-test.ts
#	src/runtime/storage/tests/reference-mode-store-test.ts
#	src/runtime/storage/tests/storage-key-test.ts
#	src/runtime/storage/tests/store-sequence-test.ts
#	src/runtime/tests/arc-test.ts
#	src/runtime/tests/capabilities-resolver-test.ts
#	src/runtime/tests/manifest-test.ts
#	src/runtime/tests/runtime-test.ts
#	src/runtime/tests/test-environment-test.ts
#	src/tests/arc-integration-test.ts
#	src/tests/particles/common-test.ts
#	src/tests/particles/dataflow-test.ts
#	src/tests/particles/particles-test.ts
#	src/tests/recipe-descriptions-test.ts
#	src/tools/tests/allocator-recipe-resolver-test.ts
#	src/tools/tests/codegen-unit-test-base.ts
#	src/tools/tests/recipe2plan-test.ts
…me-deglobal-3

# Conflicts:
#	shells/tests/arcs/ts/runtime/arc-test.ts
#	src/planning/plan/tests/planificator-test.ts
#	src/planning/recipe-index.ts
#	src/runtime/arc.ts
#	src/runtime/particle-execution-context.ts
#	src/runtime/runtime.ts
#	src/runtime/storage/direct-store-muxer.ts
#	src/runtime/storage/tests/direct-store-muxer-test.ts
#	src/runtime/storage/tests/reference-mode-store-test.ts
#	src/runtime/tests/arc-test.ts
#	src/runtime/tests/description-test.ts
#	src/runtime/tests/particle-interface-loading-test.ts
#	src/runtime/tests/runtime-test.ts
#	src/wasm/tests/wasm-api-test.ts
@sjmiles sjmiles marked this pull request as draft January 21, 2021 00:47
@google-cla google-cla bot added the cla: yes label Jan 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants