The event_api example is not working

Steps to Reproduce Issue
cargo run --example event_api

Expected Result
This example will continuously listen for incoming events and print them out.
Actual Result
WS version "1.36.2"
Error: Subscription error : Subscription only supported by WebSocket client.

System Information

OS: ubuntu 24.04
Compiler: rustc 1.82.0 (f6e511eec 2024-10-15)

@jacob-chia thanks for reporting this issue. Unfortunately, Subscriptions are not supported on public full nodes (operated by us), so this example does not work. You might still find a full node that has subscriptions enabled.
As an alternative, we recommend to use polling for whatever events you need.
I will make a note on the example that this is no longer supported.
Thanks for your understanding.

@stefan-mysten
Thank you for your response.
My fullnode.yaml is as follows, but I'm still encountering the same error. If I want to enable ws, what additional configuration should I add?
# this address is also used for web socket connections
json-rpc-address: "<IP_ADDRESS>:9000"
enable-event-processing: true

In general, we advocate for not using websockets, but if you're running your own node you can set
jsonrpc-server-type: both
which should enable the websocket service.


Make global search case insenstive for MACs with colons

When searching for a MAC address in global search, and it is formatted with colons, it is case sensitive - and should not be.  Without colons it works just fine...

Very strange.


Proposal: Tracer Components

Proposal: Instead of a global tracer singleton, every library needs to create it's own tracer, which also has a proper name that identifies the library/component that uses the tracer.
Motivation: "Configurability of library/component instrumentation"

Identify the library/component that created a span
Be able to turn the instrumentation of a certain library/component on/off. This might be necessary if the instrumentation

causes too much overhead
is buggy (e.g. does not call span.end in every case)
avoid "double-tracing". E.g. a tracing vendor (e.g. Dynatrace) might already have built-in auto-instrumentation for a certain library. In this case the vendor might want to decide (automatically or config-based) which of the implementations should be enabled/disabled.

Technically, this could be achieved similar to how logging frameworks deal with Loggers and LoggerFactories (log4j).
Tracer tracer = OpenConsensus.Tracing.getTracer("io.opensomething.contrib.mongo");

Every span would contain the information about the Tracer that it was created with. Based on that a span can be discarded or not.
Not sure how a naming convention could look like. Not sure if "component" is the right word, as it has already been used in the past as attribute name. At Dynatrace we call that a "Sensor". Not sure about granularity of "Tracers". Should every class have one? Should Tracing act as a registry (cache already created instances) or as a factory (just create new ones at every call)?
This is kind of related to the GlobalTracer discussion (#107).

Some more thoughts, should every tracer in the registry support full configuration? For instance different sampling, reporting mechanism. Perf-wise I would prefer a cached registry and also a single instrumentation might use multiple instrumentation points - e.g. servlet filer and jaxrs interceptors.
This could be an iteration after #107 - if we allow a globally scoped tracer.

Something I'd be quite interested to know, is how common an application needs such specific scenario. I remembering seeing this pattern in HTrace, but haven't seen it much in other places. Depending on that, I'd be up to putting this in out contrib/ artifact (as opposed to put it in the main API side).

Love the use case. However, I'm not sure tracer-per-component is necessary to address that. For example, if instrumentation follows the OpenTracing conventions and sets the "component" tag on span builder, then the tracer can compare it with configuration and decide to return a noop span with span context equal to the parent.

We currently name components in OpenTracing via a tag:

Span tag name
Type
Notes and examples

component
string
The software package, framework, library, or module that generated the associated Span. E.g., "grpc", "django", "JDBI".

I agree there should be a component scope, and it should be handled more directly – the tag approach was due to backwards compatibility, etc, and is not the best.
This concept is more related to scope management and span creation; I don't feel it is related to the global tracer, or tracer instantiation. Tracers are a mechanism for recording data and exporting it - ideally, there should be only one. We should not conflate instantiating the export mechanism with name-spacing and scoping the current operations.
Likewise, I would prefer not to conflate this kind of namespacing to a particular language feature, such as classes or functions – it should be a cross-language concept.
This still leaves the question open as to where to put this information. I suggest that this information is part of the Span or SpanContext, and should be constructed there. Spans inherit their parents component unless it is overridden during construction.

Am I understanding correctly that we want to have a notion of component at the SpanBuilder time is ok, I think this achieves the end result of having Spans grouped by the component.
@tedsuo I don't think we should propagate this between spans, maybe require instrumentation to set this when they create new Spans.

I can see pros and cons in inheriting component from parent span, but I think the con is bigger: if another layer doesn't set component then inheriting it is unexpected behavior. So I'd rather have it set on every span, which isn't too onerous for middleware for a given library/framework.

Also a contrib TracerWithComponent implements Tracer that simply set the component when a SpanBuilder is return is easy to offer.

@yurishkuro I'm not actually sure what the current inheritance behavior is with the component tag in OT.
@bogdandrutu that might be a good way to model the behavior @discostu105 was asking for. We could move it into core if it looks like a good pattern. Ideally, I would like "best practices" to not require contrib projects.

I agree with @yurishkuro on not inheriting component from the parent Span. Doing so could get tricky eventually, and I'd stick with simplicity for now.

This is a bit broader, but relevant. Please bear with me:
In general, each trace event can be modeled as if it is occurring in a nested namespace. So far, I have seen a lot of interest in the following namespaces:
Trace::Service::Component::Operation
Currently state of affairs (correct me if I am wrong):

The trace is modeled as a SpanContext, with an ID but no name or attributes.
The service is modeled as a Tracer, with attributes but no name or ID.
The component is proposed to be modeled as a Span property, with a name but no ID or attributes.
The operation is modeled as a Span, with a name, ID, and attributes.

In the long run, I suspect we want something like Name, ID, and Attributes for each namespace.
In the short run, I am hearing a lot of interest in attributes for components. Only having them on the span and the service is proving cumbersome for real world usage.
So perhaps we should think deeper about this subject.

Would some sort of ComponentScope that can be passed into the span builder help here?

I am not sure Name/ID/Attributes applies to all 4 entities:

Name for a trace is quite vague
ID for service/component is counterproductive (high cardinality)
Attributes make sense across all four entities (realizing that operation == span), however semantically different: static for service/component, dynamic for trace/span.

service and component sound like two different levels of resource

Thanks, I agree @yurishkuro, it's not clear that this needs to be fully normalized. But we have some holes, especially around attributes and the component scope.

Instead of
Tracer tracer = OpenConsensus.Tracing.getTracer("io.opensomething.contrib.mongo"); we could simply have one global instance
Tracer tracer = OpenConsensus.Tracing.getTracer(); hen tracer could be converted something like a builder which would modify some of the configurations - tags, exporter, sampling.

I think developers want an API that lets them write concise instrumentation code, so that the weight of instrumentation doesn't overwhelm the code itself. The question is how individual modules of code will (concisely) declare their component in the source, at that point where spans are built.
This suggests making it possible to build spans and supply very few "component" arguments, potentially just one argument at the call site. In my own code, I've accomplished this by bundling a set of attributes, including the component concept, into a single object that's passed to the span builder. Importantly, this includes more than one attribute potentially.
The pattern generally involves some heavy-weight resource that is loaded into memory. It's part of a component, sure, but it also includes a number of other attributes that specifically describe an instance of the component being invoked at the point where a span is created. The code could read like:
class MyClass {
  TraceComponent traceComponent;

  MyClass() {
    traceComponent = OpenTelemetry.Tracing.getTracer().componentBuilder("this_is_my_class").
                                                withAttribute("key1", "value1").
                                                withAttribute("key2", "value2");
    // ...
  }

  void someMethod(String arg) {
     Span span = this.traceComponent.spanBuilder("someMethod").withAttribute("arg", arg).startSpan()
     // ...
  }
};

The component builder would be a subset of the span builder API, merely allowing attribute names and setting the standard component attribute, for use in building spans elsewhere in the same module of code.

Thanks @jmacd. I discussed this with @pavolloffay, @bogdandrutu, and @carlosalberto.
An updated proposal is as follows:
class MyLibrary {
  Tracer tracer;

  MyLibrary() {
    tracer = OpenTelemetry.getTracer().toBuilder("this_is_my_class").
                                                                setResource(resource).
                                                                build();
    // ...
  }

  void someMethod(String arg) {
     Span span = this.tracer.spanBuilder("someMethod").setAttribute("arg", arg).startSpan()
     // ...
  }
};

Main Notes:

OpenTelemetry.getTracer() returns a Tracer. This Tracer is the base "Service Tracer" which was instantiated via a service loader, and contains the name and resources for the entire service.
OpenTelemetry.getTracer().toBuilder() returns a TracerBuilder which allows a component (framework, mysql client, RPC library) to add a component name, and add additional resources which are associated only with that component, and not the rest of the service. This is considered a "Component Tracer."

Additional Notes:

We don't think we need an intermediary OpenTelemetry.Tracing class. The OpenTelemetry class can directly contain tracing, metrics, and tag methods.
We'd like to remove the setResource method currently available on Tracer. Resources should only be set on tracer creation.

I don't know how the hell Github mis-ordered mine and @pavolloffay's comments, but it did.

@tedsuo see the attachment :))), @pavolloffay came from the future :)))

I like it, @tedsuo. I always focus on concision, so I wonder if a ResourceBuilder might help with readability. For example, to construct a resource in the same line of code, you might like to write:
tracer = OpenTelemetry.getTracer().toBuilder("this_is_my_class").
                                                                setResource(Resource.ofEntries(
                                                                       entry("key1", "value1"),
                                                                       entry("key2", "value2")
                                                               )).build();


NRT DbSet default seems incorrect in example.

Possible related PR: https://github.com/dotnet/EntityFramework.Docs/commit/db7df54678a225da9ebb85371be59263b46068c0#diff-c98f9d4ab6f3584846cc2f188a8ecea77bbfe34fe592d217b907f765763a5b46
In this PR, the example code was changed to:
        public DbSet<Customer> Customers => Set<Customer>();
        public DbSet<Order> Orders => Set<Order>();

What are Sets in above snippet? The most commonly possible classes are DbSet or HashSet but neigher works when replaced Set in above.
 Neigher new DbSet<Customer>() works because DbSet is abstract class.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 93c3721a-da23-d9ea-a054-9d786d2ff4d2
Version Independent ID: 6d3b0f96-6642-75e5-93c8-02c23f142ac4
Content: Working with nullable reference types - EF Core
Content Source: entity-framework/core/miscellaneous/nullable-reference-types.md
Product: entity-framework
Technology: entity-framework-core
GitHub Login: @roji
Microsoft Alias: avickers

@Gateswong Set is a call to the Set method on  DbContext.

Oh. That's it. I typed wrong = instead of =>. Thank you for helping.


[SEO][Rollout Monikered Canonical]Add URL moniker

Enable build config to generate canonical URL with moniker

Docs Build status updates of commit c3d4bed:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

officedocs-dev-exchange-ews-api/docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


tests: fetching failures

Environment
semaphore
What did you do?
pushed new PR
What did you expect to see?
tests should PASS
What did you see instead?
https://semaphoreci.com/coreos/rkt/branches/pull-request-2715/builds/1
=== RUN   TestFetch
--- FAIL: TestFetch (39.19s)

IMO our tests should be independent from external (from build machine) resources. To achieve this - there should be an option to mock downloading them - possibly by using mocked reading files from local fs. This should also shorten time of tests execution.
Other option (a bit ugly and harder to achieve on local dev machines) would be to add entries like:
<IP_ADDRESS> mocked_host

to /etc/hosts before running tests, and then starting helper server in manner close to api-server tests.
What do you think about this?

Yeah, totally, the thing is we need to implement a docker registry process
and some mock images. I think there's a ticket for this somewhere.
In the meantime this failure you're seeing is tracked in another ticket
that's blocking 1.7.0 (check out the milestone)
Piotr Skamruk<EMAIL_ADDRESS>schrieb am Sa., 28. Mai 2016,
14:28:

IMO our tests should be independent from external (from build machine)
resources. To achieve this - there should be an option to mock downloading
them - possibly by using mocked reading files from local fs. This should
also shorten time of tests execution.
Other option (a bit ugly and harder to achieve on local dev machines)
would be to add entries like:
<IP_ADDRESS> mocked_host
to /etc/hosts before running tests, and then starting helper server in
manner close to api-server tests.
What do you think about this?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/coreos/rkt/issues/2718#issuecomment-222306057, or mute
the thread
https://github.com/notifications/unsubscribe/ACewN5-09JO_ehPkt7gdhPyCKYmzHlYfks5qGDTbgaJpZM4IpEHe
.

Imo we don't need whole functionality of docker registry for this. Simple predefined answers should be enough.
Also we are running 12 combinations of tests for each of https://github.com/coreos/rkt/blob/master/tests/rkt_fetch_test.go#L116 configuration, what seems to be too precise - in fact this test do not do what one could read from func name, it's not only testing fetching, but also starting and preparing.
This single test have many false-positives in history and AFAIR is the longest one...

@s-urbaniak can you please add details of what you're experiencing - semaphore does not keep enough history and I actually think jell's failure here was pre-docker2aci fixes

I don't have the logs anymore, semaphore already wiped them out :-/ I am trying to reproduce now.

Failure was probably connected with pre-docker2aci fixes, but still IMO this test should be rewritten ASAP, because this single test runs for ~5min and is a bit unpredictible.
E.x. https://semaphoreci.com/coreos/rkt/branches/pull-request-2745/builds/1 - 360sec for kvm flavor, 260sec for coreos flavor - and still, idk why there is 100sec difference, there is no single line of difference in this area between these flavors.
Maybe we should also tag some functionalities as flavor independent and then test them once, without testing them for each flavor again?
I think that after rktnetess release we should discuss a bit out testsuite.

k, I have TestFetch failures, again, this time I saved both Semaphore thread outputs: https://gist.github.com/s-urbaniak/cd0fc6aa8eb1d5b8abf7715b84849729

Another TestFetch failure, same error output, seen on jenkins https://jenkins-rkt.prod.coreos.systems/job/rkt-matrix/170/dummy=dummy1,label=debian-8-flavor-coreos/consoleFull
15:57:56 --- FAIL: TestFetch (36.38s)
15:57:56 	rkt_tests.go:115: Running command: /home/admin/workspace/rkt-matrix/dummy/dummy1/label/debian-8-flavor-coreos/builds/build-rkt-coreos/build-rkt-1.7.0+git/tmp/functional/rkt --dir=/tmp/datadir-144491511 --local-config=/tmp/localdir-002110698 --system-config=/tmp/systemdir-248779073 --user-config=/tmp/userdir-102579628 --insecure-options=image fetch coreos.com/etcd:v2.1.2
15:57:56 	rkt_tests.go:115: Running command: /home/admin/workspace/rkt-matrix/dummy/dummy1/label/debian-8-flavor-coreos/builds/build-rkt-coreos/build-rkt-1.7.0+git/tmp/functional/rkt --dir=/tmp/datadir-144491511 --local-config=/tmp/localdir-002110698 --system-config=/tmp/systemdir-248779073 --user-config=/tmp/userdir-102579628 --insecure-options=image fetch coreos.com/etcd:v2.1.2
15:57:56 	rkt_tests.go:115: Running command: /home/admin/workspace/rkt-matrix/dummy/dummy1/label/debian-8-flavor-coreos/builds/build-rkt-coreos/build-rkt-1.7.0+git/tmp/functional/rkt --dir=/tmp/datadir-944348443 --local-config=/tmp/localdir-295129534 --system-config=/tmp/systemdir-940638213 --user-config=/tmp/userdir-061544352 --store-only --insecure-options=image fetch coreos.com/etcd:v2.1.2
15:57:56 	rkt_tests.go:115: Running command: /home/admin/workspace/rkt-matrix/dummy/dummy1/label/debian-8-flavor-coreos/builds/build-rkt-coreos/build-rkt-1.7.0+git/tmp/functional/rkt --dir=/tmp/datadir-944348443 --local-config=/tmp/localdir-295129534 --system-config=/tmp/systemdir-940638213 --user-config=/tmp/userdir-061544352 --store-only --insecure-options=image fetch coreos.com/etcd:v2.1.2
15:57:56 	rkt_tests.go:115: Running command: /home/admin/workspace/rkt-matrix/dummy/dummy1/label/debian-8-flavor-coreos/builds/build-rkt-coreos/build-rkt-1.7.0+git/tmp/functional/rkt --dir=/tmp/datadir-775007359 --local-config=/tmp/localdir-940986322 --system-config=/tmp/systemdir-303058697 --user-config=/tmp/userdir-796180180 --no-store --insecure-options=image fetch coreos.com/etcd:v2.1.2
15:57:56 	rkt_tests.go:115: Running command: /home/admin/workspace/rkt-matrix/dummy/dummy1/label/debian-8-flavor-coreos/builds/build-rkt-coreos/build-rkt-1.7.0+git/tmp/functional/rkt --dir=/tmp/datadir-798231587 --local-config=/tmp/localdir-917467942 --system-config=/tmp/systemdir-077558861 --user-config=/tmp/userdir-550027080 --insecure-options=image fetch https://github.com/coreos/etcd/releases/download/v2.1.2/etcd-v2.1.2-linux-amd64.aci
15:57:56 	rkt_tests.go:115: Running command: /home/admin/workspace/rkt-matrix/dummy/dummy1/label/debian-8-flavor-coreos/builds/build-rkt-coreos/build-rkt-1.7.0+git/tmp/functional/rkt --dir=/tmp/datadir-798231587 --local-config=/tmp/localdir-917467942 --system-config=/tmp/systemdir-077558861 --user-config=/tmp/userdir-550027080 --insecure-options=image fetch https://github.com/coreos/etcd/releases/download/v2.1.2/etcd-v2.1.2-linux-amd64.aci
15:57:56 	rkt_tests.go:115: Running command: /home/admin/workspace/rkt-matrix/dummy/dummy1/label/debian-8-flavor-coreos/builds/build-rkt-coreos/build-rkt-1.7.0+git/tmp/functional/rkt --dir=/tmp/datadir-265057287 --local-config=/tmp/localdir-317068730 --system-config=/tmp/systemdir-634408913 --user-config=/tmp/userdir-994184444 --store-only --insecure-options=image fetch https://github.com/coreos/etcd/releases/download/v2.1.2/etcd-v2.1.2-linux-amd64.aci
15:57:56 	rkt_tests.go:115: Running command: /home/admin/workspace/rkt-matrix/dummy/dummy1/label/debian-8-flavor-coreos/builds/build-rkt-coreos/build-rkt-1.7.0+git/tmp/functional/rkt --dir=/tmp/datadir-265057287 --local-config=/tmp/localdir-317068730 --system-config=/tmp/systemdir-634408913 --user-config=/tmp/userdir-994184444 --store-only --insecure-options=image fetch https://github.com/coreos/etcd/releases/download/v2.1.2/etcd-v2.1.2-linux-amd64.aci
15:57:56 	rkt_tests.go:115: Running command: /home/admin/workspace/rkt-matrix/dummy/dummy1/label/debian-8-flavor-coreos/builds/build-rkt-coreos/build-rkt-1.7.0+git/tmp/functional/rkt --dir=/tmp/datadir-566339115 --local-config=/tmp/localdir-645904270 --system-config=/tmp/systemdir-684457877 --user-config=/tmp/userdir-560313328 --no-store --insecure-options=image fetch https://github.com/coreos/etcd/releases/download/v2.1.2/etcd-v2.1.2-linux-amd64.aci
15:57:56 	rkt_tests.go:115: Running command: /home/admin/workspace/rkt-matrix/dummy/dummy1/label/debian-8-flavor-coreos/builds/build-rkt-coreos/build-rkt-1.7.0+git/tmp/functional/rkt --dir=/tmp/datadir-321434255 --local-config=/tmp/localdir-240744098 --system-config=/tmp/systemdir-674444185 --user-config=/tmp/userdir-453212196 --insecure-options=image fetch docker://busybox
15:57:56 	rkt_tests.go:115: Running command: /home/admin/workspace/rkt-matrix/dummy/dummy1/label/debian-8-flavor-coreos/builds/build-rkt-coreos/build-rkt-1.7.0+git/tmp/functional/rkt --dir=/tmp/datadir-321434255 --local-config=/tmp/localdir-240744098 --system-config=/tmp/systemdir-674444185 --user-config=/tmp/userdir-453212196 --insecure-options=image fetch docker://busybox
15:57:56 	rkt_tests.go:115: Running command: /home/admin/workspace/rkt-matrix/dummy/dummy1/label/debian-8-flavor-coreos/builds/build-rkt-coreos/build-rkt-1.7.0+git/tmp/functional/rkt --dir=/tmp/datadir-477713715 --local-config=/tmp/localdir-859184374 --system-config=/tmp/systemdir-968781789 --user-config=/tmp/userdir-165054360 --store-only --insecure-options=image fetch docker://busybox
15:57:56 	rkt_tests.go:216: Error: ExpectRegex didn't find regex 'sha512-[0-9a-f]{32,64}'.
15:57:56 		Output: image: remote fetching from URL "docker://busybox"
15:57:56 		Downloading sha256:a3ed95caeb0 [===================================] 32 B / 32 B
15:57:56 		fetch: error generating ACI: error writing ACI: flate: corrupt input before offset 40070

A similar error also occurring when running tests locally using make check.  I'm unsure how to proceed with generating pull requests, if the tests won't run.
kiai$ sudo rkt run --net=host --dns=<IP_ADDRESS> --volume src-dir,kind=host,source="$(pwd)" --volume build-dir,kind=host,source="$(pwd)/release-build" --interactive coreos.com/rkt/builder:1.2.0 --exec /bin/sh
# make check
make check
  ACTOOL       /opt/build-rkt/target/bin/stage1-coreos.aci
  COPY FILES   kvm-qemu
  ACTOOL       /opt/build-rkt/target/bin/stage1-kvm.aci
can't load package: package ./release-build/tmp/usr_from_kvm/kernel/linux-4.9.2/arch/mips/generic: read /opt/rkt/release-build/tmp/usr_from_kvm/kernel/linux-4.9.2/arch/mips/generic/vmlinux.its.S: syntax error
can't load package: package ./release-build/tmp/usr_from_kvm/kernel/linux-4.9.2/arch/mips/generic: read /opt/rkt/release-build/tmp/usr_from_kvm/kernel/linux-4.9.2/arch/mips/generic/vmlinux.its.S: syntax error
  GOFMT        ./api/v1 ./api/v1alpha ./common ./common/apps ./common/cgroup ./common/cgroup/v1 ./common/cgroup/v2 ./common/labelsort ./common/networking ./common/overlay ./lib ./networking ./networking/netinfo ./networking/tuntap ./pkg/aci ./pkg/aci/acitest ./pkg/backup ./pkg/distribution ./pkg/fileutil ./pkg/flag ./pkg/fs ./pkg/group ./pkg/keystore ./pkg/keystore/keystoretest ./pkg/label ./pkg/lock ./pkg/log ./pkg/mountinfo ./pkg/multicall ./pkg/passwd ./pkg/pod ./pkg/selinux ./pkg/set ./pkg/sys ./pkg/tar ./pkg/tpm ./pkg/user ./rkt ./rkt/config ./rkt/flag ./rkt/image ./rkt/pubkey ./stage0 ./stage1/app_add ./stage1/app_rm ./stage1/app_start ./stage1/app_stop ./stage1/attach ./stage1/common ./stage1/common/ssh ./stage1/common/types ./stage1/enter_kvm ./stage1/gc ./stage1/init ./stage1/init/common ./stage1/init/kvm ./stage1/init/kvm/hypervisor ./stage1/init/kvm/hypervisor/hvlkvm ./stage1/init/kvm/hypervisor/hvqemu ./stage1/iottymux ./stage1/stop ./stage1/stop_kvm ./stage1_fly/enter ./stage1_fly/gc ./stage1_fly/run ./stage1_fly/stop ./store/db ./store/imagestore ./store/treestore ./tests ./tests/cniproxy ./tests/echo-socket-activated ./tests/inspect ./tests/rkt-monitor ./tests/rkt-monitor/cpu-stresser ./tests/rkt-monitor/log-stresser ./tests/rkt-monitor/mem-stresser ./tests/rkt-monitor/sleeper ./tests/stub-stage1/enter ./tests/stub-stage1/gc ./tests/stub-stage1/run ./tests/testutils ./tests/testutils/aci-server ./tests/testutils/logger ./tools/cleangen ./tools/common ./tools/common/filelist ./tools/depsgen ./tools/filelistgen ./tools/quickrm ./version
  GO VET       github.com/rkt/rkt/api/v1 github.com/rkt/rkt/api/v1alpha github.com/rkt/rkt/common github.com/rkt/rkt/common/apps github.com/rkt/rkt/common/cgroup github.com/rkt/rkt/common/cgroup/v1 github.com/rkt/rkt/common/cgroup/v2 github.com/rkt/rkt/common/labelsort github.com/rkt/rkt/common/networking github.com/rkt/rkt/common/overlay github.com/rkt/rkt/lib github.com/rkt/rkt/networking github.com/rkt/rkt/networking/netinfo github.com/rkt/rkt/networking/tuntap github.com/rkt/rkt/pkg/aci github.com/rkt/rkt/pkg/aci/acitest github.com/rkt/rkt/pkg/backup github.com/rkt/rkt/pkg/distribution github.com/rkt/rkt/pkg/fileutil github.com/rkt/rkt/pkg/flag github.com/rkt/rkt/pkg/fs github.com/rkt/rkt/pkg/group github.com/rkt/rkt/pkg/keystore github.com/rkt/rkt/pkg/keystore/keystoretest github.com/rkt/rkt/pkg/label github.com/rkt/rkt/pkg/lock github.com/rkt/rkt/pkg/log github.com/rkt/rkt/pkg/mountinfo github.com/rkt/rkt/pkg/multicall github.com/rkt/rkt/pkg/passwd github.com/rkt/rkt/pkg/pod github.com/rkt/rkt/pkg/selinux github.com/rkt/rkt/pkg/set github.com/rkt/rkt/pkg/sys github.com/rkt/rkt/pkg/tar github.com/rkt/rkt/pkg/tpm github.com/rkt/rkt/pkg/user github.com/rkt/rkt/rkt github.com/rkt/rkt/rkt/config github.com/rkt/rkt/rkt/flag github.com/rkt/rkt/rkt/image github.com/rkt/rkt/rkt/pubkey github.com/rkt/rkt/stage0 github.com/rkt/rkt/stage1/app_add github.com/rkt/rkt/stage1/app_rm github.com/rkt/rkt/stage1/app_start github.com/rkt/rkt/stage1/app_stop github.com/rkt/rkt/stage1/attach github.com/rkt/rkt/stage1/common github.com/rkt/rkt/stage1/common/ssh github.com/rkt/rkt/stage1/common/types github.com/rkt/rkt/stage1/enter_kvm github.com/rkt/rkt/stage1/gc github.com/rkt/rkt/stage1/init github.com/rkt/rkt/stage1/init/common github.com/rkt/rkt/stage1/init/kvm github.com/rkt/rkt/stage1/init/kvm/hypervisor github.com/rkt/rkt/stage1/init/kvm/hypervisor/hvlkvm github.com/rkt/rkt/stage1/init/kvm/hypervisor/hvqemu github.com/rkt/rkt/stage1/iottymux github.com/rkt/rkt/stage1/stop github.com/rkt/rkt/stage1/stop_kvm github.com/rkt/rkt/stage1_fly/enter github.com/rkt/rkt/stage1_fly/gc github.com/rkt/rkt/stage1_fly/run github.com/rkt/rkt/stage1_fly/stop github.com/rkt/rkt/store/db github.com/rkt/rkt/store/imagestore github.com/rkt/rkt/store/treestore github.com/rkt/rkt/tests github.com/rkt/rkt/tests/cniproxy github.com/rkt/rkt/tests/echo-socket-activated github.com/rkt/rkt/tests/inspect github.com/rkt/rkt/tests/rkt-monitor github.com/rkt/rkt/tests/rkt-monitor/cpu-stresser github.com/rkt/rkt/tests/rkt-monitor/log-stresser github.com/rkt/rkt/tests/rkt-monitor/mem-stresser github.com/rkt/rkt/tests/rkt-monitor/sleeper github.com/rkt/rkt/tests/stub-stage1/enter github.com/rkt/rkt/tests/stub-stage1/gc github.com/rkt/rkt/tests/stub-stage1/run github.com/rkt/rkt/tests/testutils github.com/rkt/rkt/tests/testutils/aci-server github.com/rkt/rkt/tests/testutils/logger github.com/rkt/rkt/tools/cleangen github.com/rkt/rkt/tools/common github.com/rkt/rkt/tools/common/filelist github.com/rkt/rkt/tools/depsgen github.com/rkt/rkt/tools/filelistgen github.com/rkt/rkt/tools/quickrm github.com/rkt/rkt/version
  (C) CHECK
  GO TEST      github.com/rkt/rkt/common github.com/rkt/rkt/common/cgroup/v1 github.com/rkt/rkt/common/labelsort github.com/rkt/rkt/common/overlay github.com/rkt/rkt/pkg/backup github.com/rkt/rkt/pkg/distribution github.com/rkt/rkt/pkg/fileutil github.com/rkt/rkt/pkg/flag github.com/rkt/rkt/pkg/group github.com/rkt/rkt/pkg/keystore github.com/rkt/rkt/pkg/lock github.com/rkt/rkt/pkg/log github.com/rkt/rkt/pkg/mountinfo github.com/rkt/rkt/pkg/passwd github.com/rkt/rkt/pkg/pod github.com/rkt/rkt/pkg/selinux github.com/rkt/rkt/pkg/set github.com/rkt/rkt/pkg/tar github.com/rkt/rkt/pkg/user github.com/rkt/rkt/rkt github.com/rkt/rkt/rkt/config github.com/rkt/rkt/rkt/flag github.com/rkt/rkt/rkt/image github.com/rkt/rkt/stage1/init/common github.com/rkt/rkt/stage1/init/kvm github.com/rkt/rkt/store/db github.com/rkt/rkt/store/imagestore github.com/rkt/rkt/store/treestore
ok  	github.com/rkt/rkt/common	1.020s	coverage: 23.6% of statements
ok  	github.com/rkt/rkt/common/cgroup/v1	1.008s	coverage: 10.2% of statements
ok  	github.com/rkt/rkt/common/labelsort	1.007s	coverage: 61.5% of statements
ok  	github.com/rkt/rkt/common/overlay	1.006s	coverage: 37.5% of statements
ok  	github.com/rkt/rkt/pkg/backup	1.014s	coverage: 71.9% of statements
ok  	github.com/rkt/rkt/pkg/distribution	1.037s	coverage: 70.1% of statements
ok  	github.com/rkt/rkt/pkg/fileutil	1.012s	coverage: 31.9% of statements
ok  	github.com/rkt/rkt/pkg/flag	1.006s	coverage: 86.5% of statements
ok  	github.com/rkt/rkt/pkg/group	1.007s	coverage: 35.7% of statements
ok  	github.com/rkt/rkt/pkg/keystore	1.280s	coverage: 52.6% of statements
ok  	github.com/rkt/rkt/pkg/lock	1.008s	coverage: 77.2% of statements
ok  	github.com/rkt/rkt/pkg/log	1.005s	coverage: 62.9% of statements
ok  	github.com/rkt/rkt/pkg/mountinfo	1.201s	coverage: 78.4% of statements
ok  	github.com/rkt/rkt/pkg/passwd	1.005s	coverage: 31.7% of statements
ok  	github.com/rkt/rkt/pkg/pod	1.169s	coverage: 23.4% of statements
ok  	github.com/rkt/rkt/pkg/selinux	1.006s	coverage: 3.4% of statements
ok  	github.com/rkt/rkt/pkg/set	1.006s	coverage: 100.0% of statements
ok  	github.com/rkt/rkt/pkg/tar	8.081s	coverage: 51.5% of statements
ok  	github.com/rkt/rkt/pkg/user	1.009s	coverage: 53.4% of statements
TestOpenSocket: Listening on 1 systemd-provided socket(s)
TestOpenSocket: Listening on localhost:0
Downloading ACI: 0 B of an unknown total size
Downloading ACI: 3.07 KB of an unknown total size

--- FAIL: TestDownloading (0.54s)
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
	panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0x752b2a]

goroutine 23 [running]:
panic(0xf98fe0, 0xc42000e120)
	/usr/lib/go-1.7/src/runtime/panic.go:500 +0x1ae
testing.tRunner.func1(0xc42044d500)
	/usr/lib/go-1.7/src/testing/testing.go:579 +0x474
panic(0xf98fe0, 0xc42000e120)
	/usr/lib/go-1.7/src/runtime/panic.go:458 +0x271
github.com/rkt/rkt/store/treestore.(*Store).GetID(0x0, 0xc4200a43f0, 0x47, 0xc4203f58e0, 0xc4203f58a0, 0x170ca00, 0xc420029840)
	/opt/build-rkt/gopath/src/github.com/rkt/rkt/store/treestore/tree.go:93 +0xea
github.com/rkt/rkt/store/treestore.(*Store).Render(0x0, 0xc4200a43f0, 0x47, 0xc4200a4300, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
	/opt/build-rkt/gopath/src/github.com/rkt/rkt/store/treestore/tree.go:115 +0xd7
github.com/rkt/rkt/rkt/image.(*Fetcher).FetchImage(0xc4203f5cc8, 0x1713400, 0xc420409f80, 0xc4201b27e0, 0x17, 0x0, 0x0, 0xc42007c020, 0x0, 0x0)
	/opt/build-rkt/gopath/src/github.com/rkt/rkt/rkt/image/fetcher.go:89 +0x3d8
github.com/rkt/rkt/rkt.TestDownloading(0xc42044d500)
	/opt/build-rkt/gopath/src/github.com/rkt/rkt/rkt/fetch_test.go:295 +0x158a
testing.tRunner(0xc42044d500, 0x1147870)
	/usr/lib/go-1.7/src/testing/testing.go:610 +0xca
created by testing.(*T).Run
	/usr/lib/go-1.7/src/testing/testing.go:646 +0x530
FAIL	github.com/rkt/rkt/rkt	0.586s
ok  	github.com/rkt/rkt/rkt/config	1.023s	coverage: 74.1% of statements
ok  	github.com/rkt/rkt/rkt/flag	1.006s	coverage: 40.7% of statements
ok  	github.com/rkt/rkt/rkt/image	1.029s	coverage: 7.1% of statements
ok  	github.com/rkt/rkt/stage1/init/common	1.013s	coverage: 7.6% of statements
ok  	github.com/rkt/rkt/stage1/init/kvm	1.009s	coverage: 19.4% of statements
ok  	github.com/rkt/rkt/store/db	7.527s	coverage: 68.4% of statements
ok  	github.com/rkt/rkt/store/imagestore	7.887s	coverage: 55.6% of statements
panic: test timed out after 1m0s

goroutine 50 [running]:
panic(0xa6b920, 0xc4203c1a20)
	/usr/lib/go-1.7/src/runtime/panic.go:500 +0x1ae
testing.startAlarm.func1()
	/usr/lib/go-1.7/src/testing/testing.go:918 +0x14e
created by time.goFunc
	/usr/lib/go-1.7/src/time/sleep.go:154 +0x78

goroutine 1 [chan receive]:
testing.(*T).Run(0xc420093380, 0xb08e67, 0x13, 0xb73568, 0x4ccba3)
	/usr/lib/go-1.7/src/testing/testing.go:647 +0x56e
testing.RunTests.func1(0xc420093380)
	/usr/lib/go-1.7/src/testing/testing.go:793 +0xba
testing.tRunner(0xc420093380, 0xc42004bd20)
	/usr/lib/go-1.7/src/testing/testing.go:610 +0xca
testing.RunTests(0xb739b8, 0xf63b20, 0x3, 0x3, 0x0)
	/usr/lib/go-1.7/src/testing/testing.go:799 +0x4bb
testing.(*M).Run(0xc42004bef0, 0x30)
	/usr/lib/go-1.7/src/testing/testing.go:743 +0x130
main.main()
	github.com/rkt/rkt/store/treestore/_test/_testmain.go:104 +0x2f9

goroutine 17 [syscall, locked to thread]:
runtime.goexit()
	/usr/lib/go-1.7/src/runtime/asm_amd64.s:2086 +0x1

goroutine 21 [syscall]:
syscall.Syscall6(0xf7, 0x1, 0x1e9f, 0xc4203db400, 0x1000004, 0x0, 0x0, 0xc4200e9668, 0x46a320, 0xc4200e9660)
	/usr/lib/go-1.7/src/syscall/asm_linux_amd64.s:44 +0x5
os.(*Process).blockUntilWaitable(0xc420105380, 0x0, 0x0, 0x5)
	/usr/lib/go-1.7/src/os/wait_waitid.go:28 +0x104
os.(*Process).wait(0xc420105380, 0xc420096960, 0xc420105380, 0xc420302680)
	/usr/lib/go-1.7/src/os/exec_unix.go:22 +0xf9
os.(*Process).Wait(0xc420105380, 0xc420096918, 0xc4200e97d0, 0xc4200968f0)
	/usr/lib/go-1.7/src/os/doc.go:49 +0x39
os/exec.(*Cmd).Wait(0xc420096840, 0x0, 0x0)
	/usr/lib/go-1.7/src/os/exec/exec.go:434 +0xf6
os/exec.(*Cmd).Run(0xc420096840, 0x70, 0xc4200e98e0)
	/usr/lib/go-1.7/src/os/exec/exec.go:279 +0x87
os/exec.(*Cmd).CombinedOutput(0xc420096840, 0xb73500, 0xc4201a29c0, 0xc42006d770, 0xc4203ee420, 0xc420096840)
	/usr/lib/go-1.7/src/os/exec/exec.go:494 +0x2b8
github.com/rkt/rkt/pkg/tar.ExtractTar(0x7fcd05425de0, 0xc42033a1c0, 0xc4202a5f20, 0x2f, 0xc42033a100, 0xc4200e9c10, 0xc4203ee420, 0x0, 0x0)
	/opt/build-rkt/gopath/src/github.com/rkt/rkt/pkg/tar/chroot.go:123 +0x500
github.com/rkt/rkt/pkg/aci.renderImage(0xc420354000, 0x1, 0x1, 0xc4202a5f20, 0x2f, 0x7fcd053d9028, 0xc42006ce10, 0xc4200e9c10, 0x1, 0x0)
	/opt/build-rkt/gopath/src/github.com/rkt/rkt/pkg/aci/render.go:72 +0x17c
github.com/rkt/rkt/pkg/aci.RenderACIWithImageID(0xc4200a7830, 0x6, 0xc4200a7837, 0x40, 0xc4202a5f20, 0x2f, 0xf743c0, 0xc42006ce10, 0xc4200e9c10, 0xc42001550c, ...)
	/opt/build-rkt/gopath/src/github.com/rkt/rkt/pkg/aci/render.go:36 +0x17f
github.com/rkt/rkt/store/treestore.(*Store).render(0xc420254fc0, 0xb0655c, 0xd, 0xc4200a7830, 0x47, 0x0, 0x0, 0x0, 0x0)
	github.com/rkt/rkt/store/treestore/_test/_obj_test/tree.go:258 +0x7dd
github.com/rkt/rkt/store/treestore.TestTreeStoreRender(0xc420093440)
	/opt/build-rkt/gopath/src/github.com/rkt/rkt/store/treestore/tree_test.go:123 +0x1cd
testing.tRunner(0xc420093440, 0xb73568)
	/usr/lib/go-1.7/src/testing/testing.go:610 +0xca
created by testing.(*T).Run
	/usr/lib/go-1.7/src/testing/testing.go:646 +0x530

goroutine 7 [chan send]:
github.com/rkt/rkt/pkg/tar.ExtractTar.func1(0xc4201a29c0, 0xc42006d770, 0xc4203ee420)
	/opt/build-rkt/gopath/src/github.com/rkt/rkt/pkg/tar/chroot.go:120 +0x8b
created by github.com/rkt/rkt/pkg/tar.ExtractTar
	/opt/build-rkt/gopath/src/github.com/rkt/rkt/pkg/tar/chroot.go:121 +0x4ef

goroutine 33 [syscall]:
syscall.Syscall(0x0, 0x9, 0xc4200ec200, 0x200, 0xa262d2, 0x44bcc7, 0xa23b40)
	/usr/lib/go-1.7/src/syscall/asm_linux_amd64.s:18 +0x5
syscall.read(0x9, 0xc4200ec200, 0x200, 0x200, 0xc420462d30, 0x10019000041d180, 0x0)
	/usr/lib/go-1.7/src/syscall/zsyscall_linux_amd64.go:783 +0x63
syscall.Read(0x9, 0xc4200ec200, 0x200, 0x200, 0x30, 0xc4203ee120, 0xc420462d08)
	/usr/lib/go-1.7/src/syscall/syscall_unix.go:161 +0x5b
os.(*File).read(0xc42007abd0, 0xc4200ec200, 0x200, 0x200, 0x0, 0xc4203ee0f0, 0xc420462d48)
	/usr/lib/go-1.7/src/os/file_unix.go:228 +0x83
os.(*File).Read(0xc42007abd0, 0xc4200ec200, 0x200, 0x200, 0x0, 0x0, 0x1)
	/usr/lib/go-1.7/src/os/file.go:101 +0x70
bytes.(*Buffer).ReadFrom(0xc42010f110, 0xf6e560, 0xc42007abd0, 0xc420462e68, 0x1, 0x0)
	/usr/lib/go-1.7/src/bytes/buffer.go:176 +0x1b6
io.copyBuffer(0xf6d560, 0xc42010f110, 0xf6e560, 0xc42007abd0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
	/usr/lib/go-1.7/src/io/io.go:384 +0x3c2
io.Copy(0xf6d560, 0xc42010f110, 0xf6e560, 0xc42007abd0, 0x0, 0x0, 0x0)
	/usr/lib/go-1.7/src/io/io.go:360 +0x7f
os/exec.(*Cmd).writerDescriptor.func1(0x472d31, 0x0)
	/usr/lib/go-1.7/src/os/exec/exec.go:253 +0x69
os/exec.(*Cmd).Start.func1(0xc420096840, 0xc42000cca0)
	/usr/lib/go-1.7/src/os/exec/exec.go:370 +0x39
created by os/exec.(*Cmd).Start
	/usr/lib/go-1.7/src/os/exec/exec.go:371 +0x87f
FAIL	github.com/rkt/rkt/store/treestore	60.034s
tests/tests.mk:10: recipe for target '/opt/build-rkt/stamps/__tests_tests_mk_short_tests.stamp' failed
make: *** [/opt/build-rkt/stamps/__tests_tests_mk_short_tests.stamp] Error 1
#

Environment as follows:
rkt Version: 1.26.0
appc Version: 0.8.10
Go Version: go1.7.4
Go OS/Arch: linux/amd64
Features: -TPM +SDJOURNAL
--
Linux 4.8.6-300.fc25.x86_64 x86_64
--
NAME=Fedora
VERSION="25 (Workstation Edition)"
ID=fedora
VERSION_ID=25
PRETTY_NAME="Fedora 25 (Workstation Edition)"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:fedoraproject:fedora:25"
HOME_URL="https://fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=25
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=25
PRIVACY_POLICY_URL=https://fedoraproject.org/wiki/Legal:PrivacyPolicy
VARIANT="Workstation Edition"
VARIANT_ID=workstation
--
systemd 231
+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN

@tesujimath that looks like a completely different story, as that test is mocking a local web server to avoid network fetches. I'm not sure why it takes so long and hit the timeout on your machine, but if so you may just try increasing the threshold.

I tried with a 600s timeout in tests/tests.mk, and it made no difference.
Following the developer quickstart, I tried the instructions for running just one test.
# make functional-check GO_TEST_FUNC_ARGS='-run TestEnv'
Functional tests are disabled, pass --enable-functional-tests to configure script to enable them.
tests/tests.mk:47: recipe for target '/opt/build-rkt/stamps/__tests_tests_mk_func_test_disabled.stamp' failed
make: *** [/opt/build-rkt/stamps/__tests_tests_mk_func_test_disabled.stamp] Error 1

So I tried again:
kiai$ sudo rkt run --net=host --dns=<IP_ADDRESS> --volume src-dir,kind=host,source="$(pwd)" --volume build-dir,kind=host,source="$(pwd)/release-build" --interactive coreos.com/rkt/builder:1.2.0 --exec /bin/sh
# make clean
  GO           github.com/rkt/rkt/tools/quickrm
  GO           github.com/rkt/rkt/tools/depsgen
writing files
writing symlinks
writing dirs
set -e; \
echo "Removing everything"; \
"/opt/build-rkt/tools/quickrm" --files="/opt/build-rkt/file_ops/files" --symlinks="/opt/build-rkt/file_ops/symlinks" --dirs="/opt/build-rkt/file_ops/dirs"
Removing everything
Failed to remove directory "/opt/build-rkt": remove /opt/build-rkt: device or resource busy
  Contents of the directory:
makelib/file-ops-epilog.mk:190: recipe for target '_file_ops_mk_clean_' failed
make: *** [_file_ops_mk_clean_] Error 1
# ./autogen.sh

----------------------------------------------------------------
Initialized build system. For a common configuration please run:
----------------------------------------------------------------

./configure

# ./configure --enable-functional-tests
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl.exe... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking whether we are using the GNU C++ compiler... no
checking whether g++ accepts -g... no
checking for bash... /bin/bash
checking for git... git
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for cat... cat
checking for comm... comm
checking for cpio... cpio
checking for gzip... gzip
checking for md5sum... md5sum
checking for mktemp... mktemp
checking for sort... sort
checking for touch... touch
checking for unsquashfs... unsquashfs
checking for wget... wget
configure: will build linux kernel and kvm hypervisors (qemu) from source, make sure that all their build requirements are fulfilled
checking for patch... patch
checking for tar... tar
checking for xz... xz
checking for openssl/bio.h... yes
configure: WARNING: * fly is an experimental stage1 implementation with almost no isolation and less features
checking for acl/libacl.h... yes
checking for dlfcn.h... yes
checking for printf in -lc... yes
checking whether C library provides setns function... yes
configure: including qemu...
checking for gpg... gpg
checking whether functional tests can be run... yes
checking for fork in -lc... yes
checking for trousers/tss.h... no
configure: error: *** TPM is enabled, but could not find required development files

So the builder image I'm using doesn't support functional tests?
I think in fact I just want to run some unit tests, i.e. not use the stuff in rkt/tests at all.  How do I run some unit tests?  It seems that make unit-check runs all these tests, including the broken (for me) TestDownloading.

A few things in order:

to enabled functional tests, pass --enable-functional-tests to configure
your configure is failing on TPM devlib, you can either install it or disable with --enable-tpm=no
TestEnv is a functional-test, TestDownloading is a unit-test. You can run ftests with make functional-check and utest with make unit-check.

That said, I thing I overlooked your initial comment and it doesn't pertain here. You are hitting a panic in GetID() which I don't see locally, but it should be investigated in its own ticket and fixed.


openssl 1.1.0h gives error with update-ca-certificates

When I install openssl 1.1.0h on Ubuntu 16.04 and run "update-ca-certificates", I get the following error:
Updating certificates in /etc/ssl/certs...
syntax error at /usr/bin/c_rehash line 15, near "= ;"
Unknown regexp modifier "/W" at /usr/bin/c_rehash line 28, at end of line
Unknown regexp modifier "/3" at /usr/bin/c_rehash line 28, at end of line
Unknown regexp modifier "/2" at /usr/bin/c_rehash line 28, at end of line
No such class installdir at /usr/bin/c_rehash line 63, near "Prefix our installdir"
  (Might be a runaway multi-line // string starting on line 28)
syntax error at /usr/bin/c_rehash line 63, near "Prefix our installdir"
Execution of /usr/bin/c_rehash aborted due to compilation errors.

This seems to be caused by missing quotes in
my $dir = ;
my $prefix = /usr;

I install openssl via downloading the package and running:
config --prefix=/usr
make clean
make
make install

I've tried different config options, but none works:
config --prefix=/usr --openssldir=/usr

The quotes are not there in /usr/bin/c_rehash which gives the following error upon installing extra certificates (note you have to have new certificates in the /usr/local/share/ca-certificates folder):
# update-ca-certificates
Updating certificates in /etc/ssl/certs...
Unknown regexp modifier "/r" at /usr/bin/c_rehash line 15, at end of line
Execution of /usr/bin/c_rehash aborted due to compilation errors.

If I add quotes, the quotes are escaped.
It seems caused by this change: https://github.com/openssl/openssl/commit/77ba00bc3b7a1348f310ea7ce44890eb2c11899f#diff-4a4711c36bc44fe6f6cfa046eb6144fb. If the string does not contain quotes, it does not add the required quotes.

This has been fixed after the release of 1.1.0h, in 7ee2a43069913fb7c444c656048996ea92cc465e
Incidently, we're releasing 1.1.0i tomorrow, so you'll have that code changed back when upgrading.


Bumped kotlin to 1.9.20

Description
Bumped kotlin to 1.9.20
Changelog

Describe added features
Bumped kotlin to 1.9.20
Describe deleted features

A suggestion for improvement, could have a GitHub workflow that runs on PR, that just runs rest and build?

that is a good idea. Will add a simple build workflow that builds and run unit tests. :+1:


Wallet history

[x] Fetch history from Deposit Backend (API TBD: https://github.com/empowerchain/deposit-backend/issues/3)
[x] Show history

Moved infinite scroll to #59


wiztree update to 4.16

Change version to 4.16
change hash to:
336c6ff43c0b4722de45517192ded99a6cff1a86b9132c25e4c00a3031c7e0e *wiztree_4_16_portable.zip

seems updated in extras

@NSP-0123456 Thank you for reporting.
I have deleted the WizTree manifest from my buckets, because it already exists in extras.


Group Policy

Is it possible to configure a GP within the script?
I'm thinking about disabling the Windows Automatic Update and OneDrive use on win 10 pro/enterprise.

@Radder124 - Many Group Poiicy settings are nothing else but registry values. As long as you know which ones they are, you can change them.
In a domain environment it still makes more sense to use domain based group policies.
I like to have only privacy settings in this script.
Just make a copy of the script, remove the privacy settings and add your own stuff to it.


Update TFLite_detection_image.py

That is the correct variable

Thanks! Silly mistake on my part. I think I corrected it on my local file but forgot to change it on the file I uploaded to GitHub.


Bug in MudAutocomlete - @bind-Text doesn't work as intended (fix included)

Bug type
Component
Component name
MudAutocomplete
What happened?
On MudAutocomplete there is missing argument on text changed event.
This causes the @bind-Text option to not work.
Line 768:
private async Task OnTextChanged(string text)
{
    await base.TextChanged.InvokeAsync();
    // Should be await base.TextChanged.InvokeAsync(text);

    if (text == null)
        return;
    await SetTextAsync(text, true);
}

Expected behavior
To update the source with the correct value
Reproduction link
xxxxx
Reproduction steps

Use autocomplete box with @bind-Text

Relevant log output
No response
Version (bug)
6.1.7
Version (working)
No response
What browsers are you seeing the problem on?
Chrome
On what operating system are you experiencing the issue?
Windows
Pull Request

[X] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

If this is still an issue in the latest version, please add a reproduction and ping a team member so we can reopen the issue.

I see it was fixed, thanks!


feat: expose config as public package

What kind of change does this PR introduce?
feature
What is the new behavior?
Allows 3rd party to load, eject, and validate config.toml.
Additional context
Add any other context or screenshots.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
7 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.03%) to 61.304%

Files with Coverage Reduction
New Missed Lines
%

internal/storage/rm/rm.go
2
89.53%

internal/gen/keys/keys.go
5
11.76%

Totals

Change from base Build<PHONE_NUMBER>:
-0.03%

Covered Lines:
7126

Relevant Lines:
11624

💛  - Coveralls


Wayland: Create the surface before the context

This fixes a regression introduced in 496f559c where a context would be created for a NULL egl_surface, which subsequently fails.

LGTM :+1:


Document Console and Output Reports

This should be documented on the following web page and in the source code.
https://detekt.github.io/detekt/configurations.html#console-and-output-reports
Successor of #2833

using detekt 1.10 ( id("io.gitlab.arturbosch.detekt").version("1.10.0")), and including the config stanza:
output-reports:
  active: true
  exclude:
  #  - 'HtmlOutputReport'
  #  - 'TxtOutputReport'
  #  - 'XmlOutputReport'

I get the following error:
$ ./gradlew detekt

> Task :jobs:detekt FAILED
Property 'output-reports' is misspelled or does not exist.

FAILURE: Build failed with an exception.

Also, the documentation shows this configuration is available, but the default config file linked from the documentation does not have it.
Finally, running without this stanza commented yields empty xml reports:
$ cat lib/build/reports/detekt/detekt.html
...

Complexity Report

224 lines of code (loc)

169 source lines of code (sloc)

130 logical lines of code (lloc)

23 comment lines of code (cloc)

32 cyclomatic complexity (mcc)

9 cognitive complexity

0 number of total code smells

13% comment source ratio

246 mcc per 1,000 lloc

0 code smells per 1,000 lloc

$ cat lib/build/reports/detekt/detekt.xml
<?xml version="1.0" encoding="utf-8"?>
<checkstyle version="4.3">
</checkstyle

@sean-abbott I moved your comment to a new issue.

Thank you, sorry for misfiling...I'm new to detekt so I wasn't sure if this was user error or not.

No worries..
This is issue here is rather a reminder to update the docs accordingly. May I ask you to submit your complete config in the other issue.


Data preperation script only imports 1 chunk of large pdfs

Describe the bug
The data preparation script is only importing 1 chunk of large PDFs. I am attempting to prep and import a 99 page pdf document, running the data preparation script on only that one document using the layout model using the config and command below.
[
    {
        "data_path": "C:\\Users\\PATHTODATA",
        "location": "eastus",
        "subscription_id": "SUBID",
        "resource_group": "RG NAME",
        "search_service_name": "SEARCH NAME",
        "index_name": "chunkingtesting",
        "chunk_size": 1024,
        "token_overlap": 128,
        "semantic_config_name": "default",
        "language": "en"
    }
]

python data_preparation.py --config config.json --njobs=4 --form-rec-resource FORMRECOGNAME --form-rec-key KEYGOESHERE --form-rec-use-layout

Output from script
Data preparation script started
Using Form Recognizer resource REDACTED for PDF cracking, with the Layout model.
Preparing data for index: chunkingtesting
Using existing search service REDACTED
Created search index chunkingtesting
Chunking path C:\Users\REDACTED ...
Total files to process=1 out of total directory size=1
Multiprocessing with njobs=4
  0%|                                                                                | 0/1 [00:00<?, ?it/s]SingletonFormRecognizerClient: Creating instance of Form recognizer per process
100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 1/1 [00:11<00:00, 11.02s/it]
Processed 1 files
Unsupported formats: 0 files
Files with errors: 0 files
Found 1 chunks
Uploading documents to index...
Indexing Chunks...: 100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 1/1 [00:00<00:00,  1.60it/s]
Validating index...
Index is empty. Waiting 60 seconds to check again...
Index is empty. Waiting 60 seconds to check again...
Index is empty. Waiting 60 seconds to check again...
The index contains 1 chunks.
The average chunk size of the index is 9712.0 bytes.
Index validation completed
Data preparation for index chunkingtesting completed
Data preparation script completed. 1 indexes updated.`

After this is complete looking at the index that is created I see the following

When looking at the content in that one chunk it is only the first two pages of the PDF. The last 98 pages of data is missing.
Expected behavior
Expect to see many many chunks containing all the information from the 99 page PDF file.

This issue was because I was on the free SKU of the Document Intelligence resource. Was I changed to S0, it is working properly now.


UI update

Checklist:

[x] I followed the guidelines in Contributing document
[x] I checked to ensure there aren't other open Pull Requests for the same update/change
[x] I successfully ran tests with my changes locally?
[x] I updated the UI for solution file upload

Issues Solved
Fixes #{75}

i updated the UI

i resolved the conflicts

I made the changes you requested please merge it now

changed the action attribute and I will  contribute more  to this project, open the issues which u require I will try to fix them and don't forget to add the gssoc label


How to configure a RDS in a static listener?

If you are reporting any crash or any potential security issue, do not
open an issue in this repo. Please report the issue via emailing
<EMAIL_ADDRESS>where the issue will be triaged appropriately.
Description:
We are new to XDS and have a couple questions on RDS.  We have a running version of static configuration that envoy runs on, and we are trying to upgrade one of the service using dynamic route. So far, have a working version of configuring dynamic routes in a new dynamic listener as all of the examples we have found. However, we are wondering if we could have the dynamic routes configured in a static listener? Does dynamic route (RDS) needs to associate with a dynamic listener (LDS)?
Thanks and Regards,
[optional Relevant Links:]

Any extra documentation required to understand the issue.

you can use the 'rds' field in http connection manager filter https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/network/http_connection_manager/v3/http_connection_manager.proto#extensions-filters-network-http-connection-manager-v3-httpconnectionmanager, I found there is an example config clip (although it isn't fully example for RDS), you may reference how to use the rds field: https://www.envoyproxy.io/docs/envoy/latest/configuration/overview/extension#id1


Text binding not working as expected

import SwiftUI
import SwiftDown

struct DownTest: View {
    @State private var text: String = "Reply"

    var body: some View {
        VStack {
            SwiftDownEditor(text: $text).frame(height: 50)
            TextField("", text: $text).frame(height: 50)
            Button {
               self.text = ""
            } label: {
                Text("Clear")
            }
        }
    }
}

struct DownTest_Previews: PreviewProvider {
    static var previews: some View {
        DownTest()
    }
}

The text should clear as the TextField does when you run this code.

Looks like you're missing the implementation in:
public func updateUIView(_ uiView: UITextView, context: Context) {}

👋🏼 Thanks for the report, I'll work on this ASAP. Your example is also showing that default text isn't parsed in a proper way.


score_thr

why the score_thr is 0.05 not 0.5?

i also have the same question.
i would appreciate an answer when someone get a chance please.

May be experimental experience