[Bug]: Sampling strategies not working as expected

What happened?
Configured the Sampling strategies as per the Jaeger documentation:  https://www.jaegertracing.io/docs/1.34/sampling/
Sampling strategy does not seem to affect even after configuring the strategy using .json file. I can also see in the collector logs that the input json file is read but the output is not obtained as expected.
Following is the configuration .json file used by us by default:
{
"service_strategies": [],
"default_strategy": {
"type": "probabilistic",
"param": 0.1
}
}
Even after providing the sampling configuration as above keeping the type as probabilistic and parameter as 0.1.
When 100 spans are generated all of those spans are seen on UI and no filtration of spans is done.
Tested with the parameter as 0, even then I could see all the spans are stored and seen on UI.
Steps to reproduce

Select a Sampling strategy and Parameter[As above case Probablistic and 0.1]
Configure the sampling_strategies.json file using the method selected.
Check if the spans are sampled as per the strategy provided.

Expected behavior
Sampling has to be performed as per the input configuration file.
Relevant log output
Log that Samplingstrategies file is being read:
{"level":"info","ts":1663994011.7913685,"caller":"static/strategy_store.go:138","msg":"Loading sampling strategies","filename":"/etc/sampling/samplingstrategies.json"}
Jaeger backend version
v1.34.0
Storage backend
Issue is seen with both Cassandra and Elastic search as backends.
Operating system
Ubuntu 18.04.6

Expected behavior
Sampling has to be performed as per the input configuration file.

How are you verifying that?

Hi @yurishkuro ,
We have checked it in the Query UI. When 1000 traces are generated all of them can be queried out from the Query and 1000 traces were seen on Query UI.

Jaeger backend does not perform sampling, sampling happens in the SDK. Which SDK are you using? Which sampler is the SDK configured to use?

Hi @yurishkuro ,
Thanks for your reply.
We are using Go-SDK and we are configuring the sampling in SDK as per the below link: https://pkg.go.dev/go.opentelemetry.io/otel/sdk/trace
The sampler we are using from the SDK is AlwaysSample() in our client side configuration[https://github.com/open-telemetry/opentelemetry-go/blob/main/example/otel-collector/main.go]
In the collector we are configuring file sampling as decribed in the below link :https://www.jaegertracing.io/docs/1.36/sampling/#file-sampling
However, Sampling is not considered by the collector provided using strategies.json file.
Can you please let us know what else need to be configured, for the collector to consider the .json file sampling.
Also, As you mentioned that Sampling happens on sdk then what can be the exact use of sampling_strategies.json file which is provided as input in Collector configuration.Could you please let us know the complete flow of work for sampling from Client side to the Collector.

Hi @yurishkuro,
Can you please help us with this issue that is mentioned in above comment.

Hi @yurishkuro ,
We have configured our trace generator using GO SDK remote sampling configuration similar to way mentioned in https://github.com/open-telemetry/opentelemetry-go-contrib/tree/main/samplers/jaegerremote.
jaegerRemoteSampler := jaegerremote.New(
"your-service-name",
jaegerremote.WithSamplingServerURL("http://{sampling_service_host_name}:5778"),
jaegerremote.WithSamplingRefreshInterval(10*time.Second),
jaegerremote.WithInitialSampler(trace.TraceIDRatioBased(0.5)),
)
tp := trace.NewTracerProvider(
	trace.WithSampler(jaegerRemoteSampler),
	...
)
otel.SetTracerProvider(tp)
    ticker := time.Tick(time.Second)
for {
	<-ticker
	fmt.Printf("\n* Jaeger Remote Sampler %v\n\n", time.Now())
	spewCfg := spew.ConfigState{
		Indent:                  "    ",
		DisablePointerAddresses: true,
	}
	spewCfg.Dump(jaegerRemoteSampler)
}

}
After configuring the SDK using the above configuration,samplingstrategies.json file configuration is successfully fetched.
But when we tried generating the traces, the sampling_strategies.json file of collector is still not applied and did not show any effect on the sampling of traces.
What is the reason for not applying the fetched sampling configuration, are we missing anything ? could you please help us?

What is printed when you do spewCfg.Dump(jaegerRemoteSampler)?

Hi @yurishkuro,
logs.txt
Please find the output log of spewCfg.Dump(jaegerRemoteSampler) in above file.
Apart from this I have one another query regarding sampling,
Using 5778 we are performing the sampling, is there any way of configuring the sampling without using 5778 port and directly configuring the sampling configuration using Jaeger collector.

Hi @yurishkuro ,
We have tried to check for the tags in the Query UI but could not find anything of such in the UI.
Also,Can you please let us know is there any port of sampling for Collector other than applying sampling using Agent 5778 port as we are trying to remove agent and directly connect to Collector we want to know is there any way to perform Sampling using Jaeger collector.

We have an open ticket for it, but nobody stepped up to implement it. https://github.com/jaegertracing/jaeger/issues/1420

My bad, it's been already implemented: https://github.com/jaegertracing/jaeger/issues/1971

Hi @yurishkuro ,
Thanks for the support, we have gone through the implementation in #1990, as per this sampling endpoint in collector was previously implemented using the Configmanager in pkg/clientcfg/clientcfghttp/cfgmgr.go and same is added in the cmd/collector/main.go, but currently the implementation is changed in cmd/collector/main.go and is not implemented using pkg/clientcfg/clientcfghttp. so is the latest code( cmd/collector/main.go) still can be used for adding sampling endpoint in collector?, May I know how it can be implemented.
In #1971 we have seen a discussion regarding JAEGER_SAMPLING_ENDPOINT environment variable but it was no where mentioned in the Jaeger documentation about the environment variable and it's usage.Can you please let us know how we can include and use the JAEGER_SAMPLING_ENDPOINT variable.

Hi @yurishkuro ,
Thanks, from the implementation of #1990, understand that collector supports remote sampling.
Do we have any sample code like below(its for agent) in OTLP SDK for apply sampling and connect to collector with any collector sampling port.
jaegerRemoteSampler := jaegerremote.New(
"your-service-name",
jaegerremote.WithSamplingServerURL("http://{sampling_service_host_name}:5778"),
jaegerremote.WithSamplingRefreshInterval(10*time.Second),
jaegerremote.WithInitialSampler(trace.TraceIDRatioBased(0.5)),
)
tp := trace.NewTracerProvider(
trace.WithSampler(jaegerRemoteSampler),
...
)
otel.SetTracerProvider(tp)

Sorry, I don't follow your question. The code you showed is already for OTEL SDK

Hi @yurishkuro ,
Can we use the same code for sampling at collector. If yes, what are all the ports supports for sampling? as we have different interfaces with different ports(4317,4318, 14268, 14250, 9411).

Sampling via SDK and collector are not interchangeable

Hi Yuri,
Sorry we did not understand, can you please explain little bit more on that, do you mean we cannot use any other port of collector but we need to use agent sampling port 5778 only?
what are all the configuration we need to do at OTLP SDK side and Jaeger side, in order to make remote sampling work.
The Configuration/changes we have done at OTLP SDK side is as below:
jaegerRemoteSampler := jaegerremote.New(
"your-service-name",
jaegerremote.WithSamplingServerURL("http://{sampling_service_host_name}:5778"),
jaegerremote.WithSamplingRefreshInterval(10*time.Second),
jaegerremote.WithInitialSampler(trace.TraceIDRatioBased(0.5)),
)
tp := trace.NewTracerProvider(
trace.WithSampler(jaegerRemoteSampler),
...
)
otel.SetTracerProvider(tp)
From Jaeger collector side,we have sampling_strategies.json file with similar configuration available in https://www.jaegertracing.io/docs/1.36/sampling/#file-sampling
After making above changes, We are generating spans.
With the above changes we are able to fetch the Jaeger collector sampling configuration but it is not applied if we checked it with the spans in the UI.Do we need to do any more changes for the remote sampling to work other than this?

With the above changes we are able to fetch the Jaeger collector sampling configuration

How did you confirm that?

but it is not applied if we checked it with the spans in the UI

How did you verify that?

Hi Yuri,
How did you confirm that?
We have attached the file which is the output of code from below link:
https://github.com/open-telemetry/opentelemetry-go-contrib/blob/samplers/jaegerremote/v0.5.2/samplers/jaegerremote/example/main.go
The output contains the sampling configuration information which was given using jaeger_collector sampling_strategies.json file.
File of log which has sampling information in output: /home/zpinsuc/logs1.txt
Full log: /home/zpinsuc/Desktop/logs.txt
How did you verify that?
Once the spans are generated, we are checking the spans count in the Jaeger UI but the spans count is not obtained as per the sampling rate that is mentioned in the configuration file(sampling_strategies.json file).

Once the spans are generated, we are checking the spans count in the Jaeger UI but the spans count is not obtained as per the sampling rate

The samplers are supposed to record the description & parameters of the sampler in the attributes of the root span. What do they say?

Hi @yurishkuro,
Could you please tell us where we can check the root span and attributes of root span.

you can view the span in Jaeger

Hi @yurishkuro ,
Please find the requested screenshot. We did not find the sampler.param and sampler.type in the tags section of span in Jaeger UI.

Could you please let us know how we can set these parameters in OTLP SDK.Please share sample code if there is any.
Is this the reason for the sampling not working as expected?

Well, it is possible that OTEL SDK that you're using does not record the type of sampler in the attributes, although they should, precisely for this reason, it allows debugging issues like this. The old Jaeger SDKs always recorded the sampler type/param on the root span so that you would know the kind of sampling that was used. I recommend raising an issue in the corresponding OTEL SDK repository, there is not much we can investigate from Jaeger side.

Hi @yurishkuro ,
Thanks for the information. We have raised a ticket for OTEL SDK.
Also, We have tested using open tracing. In our trace generator if we specify sampler.type as "const" we can see the spans in Jaeger UI and also sampler.param and sampler.type can be seen in the UI, but if we keep the sampler.type as "Remote" in the trace generator, we are not able to see any spans in the UI(even after setting samplingrate as 0.1,0.6 or 0.7).
When we tried to fetch the sampling configuration using curl command, we are able to fetch the configuration that was given in sampling strategies.json file in collector but spans are not visible in the Jaeger UI.
Below is command and fetch information we obtained:
curl http://<jaeger_agent_service_name>..svc.cluster.local:5778/sampling?service
{"strategyType":"PROBABILISTIC","probabilisticSampling":{"samplingRate":0.7},"operationSampling":{"defaultSamplingProbability":0.7,"defaultLowerBoundTracesPerSecond":0,"perOperationStrategies":[{"operation":"/health","probabilisticSampling":{"samplingRate":0.6}},{"operation":"/metrics","probabilisticSampling":{"samplingRate":0.4}}],"defaultUpperBoundTracesPerSecond":0}}

Hi @yurishkuro,
Can you please check my previous comment and help us by answering the question and also by letting us know what else needs to be done.

Hi @yurishkuro ,
Using opentracing if sampling.Type is selected as "remote", can you we see same in Jaeger UI tags section, like "const" we are seeing in above commented screenshot?

I did not see any concrete issue with Jaeger in this ticket, more like OTEL implementation / configuration, so closing


The video compression will flash a flash

Mobile phone is meizu note3

@haegyeong please be more explicit. I don't get what you are trying to do.

the same problem ,the video compressed ,play with twinkle

I also get the same problem


Manager API - Save menu to file

Done when a file exists containing all of the data in the menu

4/10
2hrs: wrote tests and implementation

1 hr: pair programming with peter


use only WebVRAdapter for device detection

lgtm. maybe next we can make a more intelligent  VizorWebVRAdapter.isNativeWebVRAvailable that doesn't rely on a hacked polyfill


WebSocket does not support headers

because of native WebSockets, headers can't be in the request like the WS library in node.js, this could effect authentication

Fixed in v0.3 with the addition of a new dependency, custom socket.


Kpg/scrollview cinterop

There's probably some renaming or moving to do here, but this PR includes a UIScrollView in Objc with a delegate, to avoid copy/pasting code.

I was having an issue running the sample locally anyway, so was flying blind a bit. The app ran, but wasn't getting local data properly. Will try to fix that and adjust.

Took a bit to get back to this @colinrtwhite. I don't think you need app.cash.redwood.layout.uiview.cinterop.CGSize. I got your branch, and replaced it with just platform.CoreGraphics.CGSize and it compiles for me.
I updated my branch with your changes to EmojiSearch.kt. Here's a screenshot with the output (and some vertical padding on the Column, because the search box was up by the notch).

I just tried import app.cash.redwood.layout.uiview.cinterop.CGSize in my branch and it fails to compile.
Will need to dig into more tomorrow I guess.

Pushed a fix for the compilation issue here, but when I run the emoji sample app it doesn't render correctly. It seems like RedwoodScrollViewDelegateProtocol produces intrinsicContentSize and sizeThatFits methods with a different signature that use a custom app.cash.redwood.layout.uiview.cinterop.CGSize.

@colinrtwhite I tried your branch again and its the same result as mine. IDE and CLI build don't resolve import app.cash.redwood.layout.uiview.cinterop.CGSize. Not sure why you're seeing that, but I can't repro that in either branch.

I don't want to just dismiss what you're seeing, though, so if you could, please try a clean build or whatever to see if we can figure that out.


Problem with jni modules

Modules introduced in 6b4b3abbf29a8aaa021cc03be79a1e9cecc815a8 have problem:
java.lang.UnsatisfiedLinkError: dlopen failed: could not load library "libavformat-56.so" needed by "libFFmpegWrapper.so"; caused by could not load library "libavcodec-56.so" needed by "libavformat-56.so"; caused by could not load library "libswresample-1.so" needed by "libavcodec-56.so"; caused by could not load library "libavutil-54.so" needed by "libswresample-1.so"; caused by could not load library "librtmp-1.so" needed by "libavutil-54.so"; caused by cannot locate symbol "rand" referenced by "librtmp-1.so"...
Tested on Xiaomi Mi3 (Android 4.4.4).
At stackoverflow were hints, that this can be becourse this modules were compiled with NDK API 21.
Could you please provide C code for net.openwatch.ffmpegwrapper.FFmpegWrapper as OpenWatch/FFmpegWrapper-Android is outdated?

This issue should now be addressed in the kickflip-android-sdk master branch.
I've also just updated OpenWatch/FFmpegWrapper-Android. That repository now reflects the exact configuration used to build libFFMpegWrapper.so for Kickflip.


🐛 Use APIExport cluster names within webhooks

Summary
Look up APIExports by name, not path, within the generic webhook.
Adds a new required field that the APIBinding reconciler sets: APIBinding.Status.LogicalCluster.
Related issue(s)
Fixes #2622

At least one valid failure, not flakes.

Possible flakes on TestGarbageCollectorTypesFromBinding from e2e-shared.
/retest


Attempting to install some docker images causes the app to break

When working with some images, the app UI breaks and the docker container is never started.

This was attempted after searching for a Discourse docker image in the search bar.
@jeffdm has deduced the following:

Ends up this image (the Discourse image with the most stars) doesn’t have a CMD directive in the docker image, so Kitematic doesn’t know how to run it.

Thanks for filing an issue! We'll need to check for these in the image before running it and let the user know.


Make it cool again ;)

from gi.repository import Modulemd
mmd = Modulemd.ModuleMetadata()
print(mmd.props.buildrequires)
mmd.props.buildrequires = {'foo': 'bar'}
print(mmd.props.buildrequires)

works now quite well. Although mmd.props.buildrequires['foo'] = 'bar' doesn't have any effect (will debug tomorrow)...
@sgallagher @contyk I think we really need to stop using this ModuleMetadata thing.... Module should be enough. We can create compatibility wrapper for this if really want to. typing all this stuff made me cry this night.

I accepted several of the patches into my branch (fixing conflicts). The majority of this patch needs to be reworked.


WIP Allow cloud-init with networkData alone

What this PR does / why we need it:
In the current code, we always require userData section in the
cloudInitNoCloud attribute. This however does not make sense when we
want to configure networking using a networkData section while we have
no reason to use userData. Due to that, we have to define at least an
empty userData section to silence the validation.
This patch drops this requirement and makes sure that at least one
source for cloud-init is provided, no matter which.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #4033
Special notes for your reviewer:
Release note:

Drop the requirerement for userData section in cloudInitNoCloud when networkData are provided.

[Fail] [rfe_id:151][crit:high][vendor:cnv-qe@redhat.com][level:component]CloudInit UserData [rfe_id:151][crit:medium][vendor:cnv-qe@redhat.com][level:component]A new VirtualMachineInstance with cloudInitNoCloud networkData [It] [test_id:3183]should have cloud-init network-config from k8s secret

job failing

Thanks a lot for reviews. Alas, I won't be able to finish this one. Quique took over it via his #4626


Pact consumer core crash prevents interactions being completed when using V4 spec

Software versions
Please provide at least OS and version of pact-js

OS: Mac OSX 13.6
Pact Node version<EMAIL_ADDRESS>Node Version: 18.13.0
Other Versions: Any other versions you think might be relevant (optional)

Issue Checklist
Please confirm the following:

[x] I have upgraded to the latest
[x] I have the read the FAQs in the Readme
[x] I have triple checked, that there are no unhandled promises in my code
[x] I have set my log level to debug and attached a log file showing the complete request/response cycle
[x] For bonus points and virtual high fives, I have created a reproduceable ~git repository~ code snippet (see below) to illustrate the problem

Expected behaviour
When more than one interaction is tested with pact.addInteraction()...executeTest(), both tests pass without error.
Actual behaviour
The first test passes, but the next one fails with the error:
Test failed for the following reasons:

  Mock server failed with the following mismatches:

        0) The following request was expected but not received:
            Method: GET
            Path: /pet/one
            Headers:
              Accept: application/json

Pact appears to be re-driving the first interaction, so in subsequent executeTest() calls the mock server is receiving the wrong request.
This feels like user error, but for the life of me I'm not seeing where I've gone wrong! The docs all appear to be geared around V3 at the moment whilst V4 support is in beta, so I've been using examples such as this one to pull things together.
Steps to reproduce
Minimal-ish script to replicate (replicate.js):
import { PactV4, SpecificationVersion, MatchersV3 } from "@pact-foundation/pact";

const { string, number, regex } = MatchersV3;

const provider = new PactV4({
  consumer: "consumer",
  provider: "provider",
  spec: SpecificationVersion.SPECIFICATION_VERSION_V4,
  logLevel: "fatal",
});

const test1 = async () => {
  const petId = "one";
  await provider
    .addInteraction()
    .uponReceiving("a request for a pet with an invalid ID")
    .withRequest('get', regex("/pet/[a-z]+", `/pet/${petId}`), (builder) => builder
      .headers({ Accept: "application/json" })
    )
    .willRespondWith(400, (builder) => builder
      .headers({ "content-type": "application/json" })
      .jsonBody({
        code: number(1),
        type: string("error"),
        message: string("Invalid ID supplied"),
      })
    )
    .executeTest(async (mockserver) => {
      await fetch(`${mockserver.url}/pet/${petId}`, {
        headers: {
          Accept: "application/json",
        },
      });
    });
};

const test2 = async () => {
  const petId = 100;
  await provider
    .addInteraction()
    .given("no pets exist")
    .uponReceiving("a request for a pet with an ID")
    .withRequest('get', regex("/pet/[0-9]+", `/pet/${petId}`), (builder) => builder
      .headers({ Accept: "application/json" })
    )
    .willRespondWith(404, (builder) => builder
      .headers({ "content-type": "text/plain" })
    )
    .executeTest(async (mockserver) => {
      await fetch(`${mockserver.url}/pet/${petId}`, {
        headers: {
          Accept: "application/json",
        },
      });
    });
  };

const delay = (t) => new Promise((r) => setTimeout(r, t));

try {
  await test1();
  await delay(1000); // not needed
  await test2();
} catch(e) {
  console.log(e.message);
}

Run with:
ENABLE_FEATURE_V4=1 PACT_DO_NOT_TRACK=1 node replicate.js

To confirm behaviour with a single test running, comment out await test1() and re-run - it should pass with no error.
Relevant log files
Minimal logs:
2023-10-26T11:43:45.687066Z  INFO tokio-runtime-worker pact_mock_server::hyper_server: Received request GET /pet/one
2023-10-26T11:43:45.688576Z  INFO tokio-runtime-worker pact_matching: comparing to expected HTTP Request ( method: get, path: /pet/one, query: None, headers: Some({"Accept": ["application/json"]}), body: Missing )
2023-10-26T11:43:45.694120Z  INFO tokio-runtime-worker pact_mock_server::hyper_server: Request matched, sending response
2023-10-26T11:43:46.710220Z  INFO tokio-runtime-worker pact_mock_server::hyper_server: Received request GET /pet/100
2023-10-26T11:43:46.710271Z  INFO tokio-runtime-worker pact_matching: comparing to expected HTTP Request ( method: get, path: /pet/one, query: None, headers: Some({"Accept": ["application/json"]}), body: Missing )
2023-10-26T11:43:46.710371Z  INFO tokio-runtime-worker pact_matching: comparing to expected HTTP Request ( method: get, path: /pet/100, query: None, headers: Some({"Accept": ["application/json"]}), body: Missing )
2023-10-26T11:43:46.710428Z  INFO tokio-runtime-worker pact_mock_server::hyper_server: Request matched, sending response

Full debug logs:
[12:45:18.045] INFO (73031): 0.4.6: pact native library successfully found, and the correct version
2023-10-26T11:45:18.052784Z DEBUG ThreadId(01) pact_ffi::mock_server::handles: detected pact:matcher:type, will configure a matcher
2023-10-26T11:45:18.053474Z DEBUG ThreadId(01) pact_ffi::mock_server::handles: parsed header value: Left("application/json")
2023-10-26T11:45:18.053881Z DEBUG ThreadId(01) pact_ffi::mock_server::handles: parsed header value: Left("application/json")
2023-10-26T11:45:18.055043Z DEBUG ThreadId(01) pact_plugin_driver::catalogue_manager: Updated catalogue entries:
core/transport/http
core/transport/https
2023-10-26T11:45:18.055137Z DEBUG ThreadId(01) pact_plugin_driver::catalogue_manager: Updated catalogue entries:
core/content-generator/binary
core/content-generator/json
core/content-matcher/json
core/content-matcher/multipart-form-data
core/content-matcher/text
core/content-matcher/xml
2023-10-26T11:45:18.055191Z DEBUG ThreadId(01) pact_plugin_driver::catalogue_manager: Updated catalogue entries:
core/matcher/v1-equality
core/matcher/v2-max-type
core/matcher/v2-min-type
core/matcher/v2-minmax-type
core/matcher/v2-regex
core/matcher/v2-type
core/matcher/v3-content-type
core/matcher/v3-date
core/matcher/v3-datetime
core/matcher/v3-decimal-type
core/matcher/v3-includes
core/matcher/v3-integer-type
core/matcher/v3-null
core/matcher/v3-number-type
core/matcher/v3-time
core/matcher/v4-array-contains
core/matcher/v4-equals-ignore-order
core/matcher/v4-max-equals-ignore-order
core/matcher/v4-min-equals-ignore-order
core/matcher/v4-minmax-equals-ignore-order
core/matcher/v4-not-empty
core/matcher/v4-semver
2023-10-26T11:45:18.055681Z DEBUG ThreadId(01) pact_mock_server::mock_server: Started mock server on <IP_ADDRESS>:52832
2023-10-26T11:45:18.082974Z DEBUG tokio-runtime-worker hyper::proto::h1::io: parsed 7 headers
2023-10-26T11:45:18.083030Z DEBUG tokio-runtime-worker hyper::proto::h1::conn: incoming body is empty
2023-10-26T11:45:18.083086Z DEBUG tokio-runtime-worker pact_mock_server::hyper_server: Creating pact request from hyper request
2023-10-26T11:45:18.083118Z DEBUG tokio-runtime-worker pact_mock_server::hyper_server: Extracting query from uri /pet/one
2023-10-26T11:45:18.083188Z  INFO tokio-runtime-worker pact_mock_server::hyper_server: Received request GET /pet/one
2023-10-26T11:45:18.083204Z DEBUG tokio-runtime-worker pact_mock_server::hyper_server:
      ----------------------------------------------------------------------------------------
       method: GET
       path: /pet/one
       query: None
       headers: Some({"sec-fetch-mode": ["cors"], "accept-encoding": ["gzip", "deflate"], "accept": ["application/json"], "host": ["<IP_ADDRESS>:52832"], "accept-language": ["*"], "user-agent": ["undici"], "connection": ["keep-alive"]})
       body: Empty
      ----------------------------------------------------------------------------------------

2023-10-26T11:45:18.083301Z  INFO tokio-runtime-worker pact_matching: comparing to expected HTTP Request ( method: get, path: /pet/one, query: None, headers: Some({"Accept": ["application/json"]}), body: Missing )
2023-10-26T11:45:18.083329Z DEBUG tokio-runtime-worker pact_matching:      body: ''
2023-10-26T11:45:18.083340Z DEBUG tokio-runtime-worker pact_matching:      matching_rules: MatchingRules { rules: {HEADER: MatchingRuleCategory { name: HEADER, rules: {} }, PATH: MatchingRuleCategory { name: PATH, rules: {DocPath { path_tokens: [Root], expr: "$" }: RuleList { rules: [Regex("/pet/[a-z]+")], rule_logic: And, cascaded: false }} }} }
2023-10-26T11:45:18.083361Z DEBUG tokio-runtime-worker pact_matching:      generators: Generators { categories: {} }
2023-10-26T11:45:18.083507Z DEBUG tokio-runtime-worker pact_matching::matchers: String -> String: comparing '/pet/one' to '/pet/one' ==> true cascaded=false matcher=Regex("/pet/[a-z]+")
2023-10-26T11:45:18.083541Z DEBUG tokio-runtime-worker pact_matching: expected content type = '*/*', actual content type = '*/*'
2023-10-26T11:45:18.083598Z DEBUG tokio-runtime-worker pact_matching: content type header matcher = 'RuleList { rules: [], rule_logic: And, cascaded: false }'
2023-10-26T11:45:18.083707Z DEBUG tokio-runtime-worker pact_matching: --> Mismatches: []
2023-10-26T11:45:18.083792Z DEBUG tokio-runtime-worker pact_mock_server::hyper_server: Test context = {"mockServer": Object {"port": Number(52832), "url": String("http://<IP_ADDRESS>:52832")}}
2023-10-26T11:45:18.083829Z  INFO tokio-runtime-worker pact_mock_server::hyper_server: Request matched, sending response
2023-10-26T11:45:18.083840Z DEBUG tokio-runtime-worker pact_mock_server::hyper_server:
          ----------------------------------------------------------------------------------------
           status: 400
           headers: Some({"content-type": ["application/json"]})
           body: Present(57 bytes, application/json) '{"code":1,"message":"Invalid ID supplied","type":"error"}'
          ----------------------------------------------------------------------------------------

2023-10-26T11:45:18.083954Z DEBUG tokio-runtime-worker hyper::proto::h1::io: flushed 418 bytes
2023-10-26T11:45:18.092830Z DEBUG ThreadId(01) pact_ffi::mock_server::handles: pact_ffi::mock_server::handles::pactffi_pact_handle_write_file FFI function invoked
2023-10-26T11:45:18.093014Z DEBUG ThreadId(01) pact_models::pact: Merging pact with file "./pacts/consumer-provider.json"
2023-10-26T11:45:18.094448Z DEBUG ThreadId(01) pact_matching::metrics: Could not get the tokio runtime, will not send metrics - there is no reactor running, must be called from the context of a Tokio 1.x runtime
2023-10-26T11:45:18.094488Z DEBUG ThreadId(01) pact_mock_server::server_manager: Shutting down mock server with ID 530ec6d6-7f87-495c-b47c-f20a32846ee8 - MockServerMetrics { requests: 1, requests_by_path: {"/pet/one": 1} }
2023-10-26T11:45:18.094517Z DEBUG ThreadId(01) pact_mock_server::mock_server: Mock server 530ec6d6-7f87-495c-b47c-f20a32846ee8 shutdown - MockServerMetrics { requests: 1, requests_by_path: {"/pet/one": 1} }
2023-10-26T11:45:18.094542Z DEBUG tokio-runtime-worker hyper::server::shutdown: signal received, starting graceful shutdown
2023-10-26T11:45:18.094826Z DEBUG ThreadId(01) pact_ffi::plugins: pact_ffi::plugins::pactffi_cleanup_plugins FFI function invoked
[12:45:19.096] ERROR (73031<EMAIL_ADDRESS>!!!!!!!!! PACT CRASHED !!!!!!!!!

The pact consumer core returned false at 'given'. This
should only happen if the core methods were invoked out of order

...[snip]...

[12:45:19.097] ERROR (73031<EMAIL_ADDRESS>!!!!!!!!! PACT CRASHED !!!!!!!!!

The pact consumer core returned false at 'uponReceiving'. This
should only happen if the core methods were invoked out of order

...[snip]...

2023-10-26T11:45:19.097852Z DEBUG ThreadId(01) pact_ffi::mock_server::handles: detected pact:matcher:type, will configure a matcher
[12:45:19.097] ERROR (73031<EMAIL_ADDRESS>!!!!!!!!! PACT CRASHED !!!!!!!!!

The pact consumer core returned false at 'withRequest'. This
should only happen if the core methods were invoked out of order

...[snip]...

2023-10-26T11:45:19.098453Z DEBUG ThreadId(01) pact_ffi::mock_server::handles: parsed header value: Left("application/json")
[12:45:19.098] ERROR (73031<EMAIL_ADDRESS>!!!!!!!!! PACT CRASHED !!!!!!!!!

The pact consumer core returned false at 'withRequestHeader'. This
should only happen if the core methods were invoked out of order

...[snip]...

[12:45:19.098] ERROR (73031<EMAIL_ADDRESS>!!!!!!!!! PACT CRASHED !!!!!!!!!

The pact consumer core returned false at 'withStatus'. This
should only happen if the core methods were invoked out of order

...[snip]...

2023-10-26T11:45:19.099126Z DEBUG ThreadId(01) pact_ffi::mock_server::handles: parsed header value: Left("text/plain")
[12:45:19.099] ERROR (73031<EMAIL_ADDRESS>!!!!!!!!! PACT CRASHED !!!!!!!!!

The pact consumer core returned false at 'withResponseHeader'. This
should only happen if the core methods were invoked out of order

...[snip]...

2023-10-26T11:45:19.099795Z DEBUG ThreadId(01) pact_mock_server::mock_server: Started mock server on <IP_ADDRESS>:52835
2023-10-26T11:45:19.101570Z DEBUG tokio-runtime-worker hyper::proto::h1::io: parsed 7 headers
2023-10-26T11:45:19.101593Z DEBUG tokio-runtime-worker hyper::proto::h1::conn: incoming body is empty
2023-10-26T11:45:19.101607Z DEBUG tokio-runtime-worker pact_mock_server::hyper_server: Creating pact request from hyper request
2023-10-26T11:45:19.101617Z DEBUG tokio-runtime-worker pact_mock_server::hyper_server: Extracting query from uri /pet/100
2023-10-26T11:45:19.101656Z  INFO tokio-runtime-worker pact_mock_server::hyper_server: Received request GET /pet/100
2023-10-26T11:45:19.101667Z DEBUG tokio-runtime-worker pact_mock_server::hyper_server:
      ----------------------------------------------------------------------------------------
       method: GET
       path: /pet/100
       query: None
       headers: Some({"connection": ["keep-alive"], "sec-fetch-mode": ["cors"], "host": ["<IP_ADDRESS>:52835"], "user-agent": ["undici"], "accept-language": ["*"], "accept-encoding": ["gzip", "deflate"], "accept": ["application/json"]})
       body: Empty
      ----------------------------------------------------------------------------------------

2023-10-26T11:45:19.101738Z  INFO tokio-runtime-worker pact_matching: comparing to expected HTTP Request ( method: get, path: /pet/one, query: None, headers: Some({"Accept": ["application/json"]}), body: Missing )
2023-10-26T11:45:19.101750Z DEBUG tokio-runtime-worker pact_matching:      body: ''
2023-10-26T11:45:19.101757Z DEBUG tokio-runtime-worker pact_matching:      matching_rules: MatchingRules { rules: {HEADER: MatchingRuleCategory { name: HEADER, rules: {} }, PATH: MatchingRuleCategory { name: PATH, rules: {DocPath { path_tokens: [Root], expr: "$" }: RuleList { rules: [Regex("/pet/[a-z]+")], rule_logic: And, cascaded: false }} }} }
2023-10-26T11:45:19.101767Z DEBUG tokio-runtime-worker pact_matching:      generators: Generators { categories: {} }
2023-10-26T11:45:19.101805Z DEBUG tokio-runtime-worker pact_matching::matchers: String -> String: comparing '/pet/one' to '/pet/100' ==> false cascaded=false matcher=Regex("/pet/[a-z]+")
2023-10-26T11:45:19.101838Z DEBUG tokio-runtime-worker pact_matching: expected content type = '*/*', actual content type = '*/*'
2023-10-26T11:45:19.101853Z DEBUG tokio-runtime-worker pact_matching: content type header matcher = 'RuleList { rules: [], rule_logic: And, cascaded: false }'
2023-10-26T11:45:19.101882Z DEBUG tokio-runtime-worker pact_matching: --> Mismatches: [PathMismatch { expected: "/pet/one", actual: "/pet/100", mismatch: "Expected '/pet/100' to match '/pet/[a-z]+'" }]
2023-10-26T11:45:19.101922Z  INFO tokio-runtime-worker pact_matching: comparing to expected HTTP Request ( method: get, path: /pet/100, query: None, headers: Some({"Accept": ["application/json"]}), body: Missing )
2023-10-26T11:45:19.101932Z DEBUG tokio-runtime-worker pact_matching:      body: ''
2023-10-26T11:45:19.101938Z DEBUG tokio-runtime-worker pact_matching:      matching_rules: MatchingRules { rules: {PATH: MatchingRuleCategory { name: PATH, rules: {DocPath { path_tokens: [Root], expr: "$" }: RuleList { rules: [Regex("/pet/[0-9]+")], rule_logic: And, cascaded: false }} }, HEADER: MatchingRuleCategory { name: HEADER, rules: {} }} }
2023-10-26T11:45:19.101946Z DEBUG tokio-runtime-worker pact_matching:      generators: Generators { categories: {} }
2023-10-26T11:45:19.101966Z DEBUG tokio-runtime-worker pact_matching::matchers: String -> String: comparing '/pet/100' to '/pet/100' ==> true cascaded=false matcher=Regex("/pet/[0-9]+")
2023-10-26T11:45:19.101979Z DEBUG tokio-runtime-worker pact_matching: expected content type = '*/*', actual content type = '*/*'
2023-10-26T11:45:19.101990Z DEBUG tokio-runtime-worker pact_matching: content type header matcher = 'RuleList { rules: [], rule_logic: And, cascaded: false }'
2023-10-26T11:45:19.102008Z DEBUG tokio-runtime-worker pact_matching: --> Mismatches: []
2023-10-26T11:45:19.102047Z DEBUG tokio-runtime-worker pact_mock_server::hyper_server: Test context = {"mockServer": Object {"port": Number(52835), "url": String("http://<IP_ADDRESS>:52835")}}
2023-10-26T11:45:19.102062Z  INFO tokio-runtime-worker pact_mock_server::hyper_server: Request matched, sending response
2023-10-26T11:45:19.102070Z DEBUG tokio-runtime-worker pact_mock_server::hyper_server:
          ----------------------------------------------------------------------------------------
           status: 404
           headers: Some({"content-type": ["text/plain"]})
           body: Missing
          ----------------------------------------------------------------------------------------

2023-10-26T11:45:19.102122Z DEBUG tokio-runtime-worker hyper::proto::h1::io: flushed 352 bytes
2023-10-26T11:45:19.103908Z DEBUG ThreadId(01) pact_matching::metrics: Could not get the tokio runtime, will not send metrics - there is no reactor running, must be called from the context of a Tokio 1.x runtime
2023-10-26T11:45:19.103948Z DEBUG ThreadId(01) pact_mock_server::server_manager: Shutting down mock server with ID 9ef4391d-30e7-4844-84c8-c4b20a64aacb - MockServerMetrics { requests: 1, requests_by_path: {"/pet/100": 1} }
2023-10-26T11:45:19.103965Z DEBUG ThreadId(01) pact_mock_server::mock_server: Mock server 9ef4391d-30e7-4844-84c8-c4b20a64aacb shutdown - MockServerMetrics { requests: 1, requests_by_path: {"/pet/100": 1} }
2023-10-26T11:45:19.103985Z DEBUG tokio-runtime-worker hyper::server::shutdown: signal received, starting graceful shutdown
2023-10-26T11:45:19.104104Z DEBUG ThreadId(01) pact_ffi::plugins: pact_ffi::plugins::pactffi_cleanup_plugins FFI function invoked
Test failed for the following reasons:

  Mock server failed with the following mismatches:

	0) The following request was expected but not received:
	    Method: GET
	    Path: /pet/one
	    Headers:
	      Accept: application/json

Tweaking this a little to turn provider into a factory function, so generating a new PactV4 instance for every interaction, seems to resolve the issue:
import { PactV4, SpecificationVersion, MatchersV3 } from "@pact-foundation/pact";

const { string, number, regex } = MatchersV3;

const provider = () => new PactV4({
  consumer: "consumer",
  provider: "provider",
  spec: SpecificationVersion.SPECIFICATION_VERSION_V4,
  logLevel: "fatal",
});

const test1 = async () => {
  const petId = "one";
  await provider()
    .addInteraction()
    .uponReceiving("a request for a pet with an invalid ID")
    .withRequest('get', regex("/pet/[a-z]+", `/pet/${petId}`), (builder) => builder
      .headers({ Accept: "application/json" })
    )
    .willRespondWith(400, (builder) => builder
      .headers({ "content-type": "application/json" })
      .jsonBody({
        code: number(1),
        type: string("error"),
        message: string("Invalid ID supplied"),
      })
    )
    .executeTest(async (mockserver) => {
      await fetch(`${mockserver.url}/pet/${petId}`, {
        headers: {
          Accept: "application/json",
        },
      });
    });
};

const test2 = async () => {
  const petId = 100;
  await provider()
    .addInteraction()
    .given("no pets exist")
    .uponReceiving("a request for a pet with an ID")
    .withRequest('get', regex("/pet/[0-9]+", `/pet/${petId}`), (builder) => builder
      .headers({ Accept: "application/json" })
    )
    .willRespondWith(404, (builder) => builder
      .headers({ "content-type": "text/plain" })
    )
    .executeTest(async (mockserver) => {
      await fetch(`${mockserver.url}/pet/${petId}`, {
        headers: {
          Accept: "application/json",
        },
      });
    });
  };

const delay = (t) => new Promise((r) => setTimeout(r, t));

try {
  await test1();
  // await delay(1000); // not needed
  await test2();
} catch(e) {
  console.log(e.message);
}

And both interactions are written to the same pact json without conflict. So problem solved ... but is the correct approach? The example I was following is 3 months old at the time of writing, so perhaps things have moved on?


[Release] Verify 7.0.0 RC9 [WIP]

@github-actions crossbow submit --group verify-rc-source --param release=7.0.0 --param rc=9

Closing in favor of https://github.com/apache/arrow/pull/12293


Consider renaming default branch to main

Just a socially conscious recommendation.
https://github.com/github/renaming

Thanks. We considered that and renamed other repositories. But with this one we need to do quite a few fixes:
https://github.com/fortran-lang/fortran-lang.org/search?q=master
However if you send us PRs, it can happen faster. :)

Duplicate of https://github.com/fortran-lang/fortran-lang.org/issues/325

This repository will be migrated to https://github.com/fortran-lang/webpage soon (see #415), where we use main as name for the default branch.


PhoneMask Module updated for international phone number

This PR handles Issue#1
The PhoneMask component now supports international phone formats for the following countries: United States (US), United Kingdom (UK), France (FR), and South Korea (KR).
Key Features:
Dynamic Formatting: Automatically formats phone numbers based on the selected country code.
Future Scalability: The existing code structure is designed for easy expansion, allowing for the addition of more countries as needed.
Future Enhancements:
To support more countries, simply add their respective formatting patterns and rules to the formats object in the code. This modular approach ensures that maintaining and extending the component is straightforward.
Points to Note
Since I am not fully aware of use cases, I assumed that the user selects the coutrny code with dropdown box,
and only enters their own phone number.

Could you add 'Hacktoberfest label for my PR when merging?

@gitdevjin Sorry for the delay.  Would you like to merge this PR?  You can open it, and I will merge.  Thanks


Resolved duplicate code

Why are these changes needed?
I eliminated redundant code where "SKILLS_TABLE_SQL" previously held the same value as "SESSIONS_TABLE_SQL." Additionally, I revised "SKILLS_TABLE_SQL" to ensure it functions as intended.
Related issue 927

Checks

[ ] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
[ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[ ] I've made sure all auto checks have passed.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (8ea6377) 26.60% compared to head (79ebb44) 26.41%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #928      +/-   ##
==========================================
- Coverage   26.60%   26.41%   -0.19%
==========================================
  Files          28       28
  Lines        3733     3733
  Branches      847      847
==========================================
- Hits          993      986       -7
- Misses       2667     2673       +6
- Partials       73       74       +1

Flag
Coverage Δ

unittests
26.41% <ø> (-0.14%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

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

@sonichi @elecnix @halr9000 @joshuavial please review these changes

@victordibia @elecnix @halr9000 @joshuavial any feedback on this PR?

Hi, @ShobhitVishnoi30 ,
Sorry for the delay here.
The issue you mention was an artifact from an earlier attempt to migrate some of the sample UI application capabilities to use a db. The duplicate code (while still being an issue) you reference was never called, so there were no side effects.
The autogen assistant (now called studio) code is being updated in this PR,  branch.
Can you confirm if these issues still apply? This is the current version of dbutils.py


Unable to delegate libedgetpu.so.1 after installing FogLamp then trying to run ‘edgetpu_classify’

Hi I suspect this issue is due to the incompatibility of tflite-runtime

@NooLL Are there any errors or logs that you can share ?

Marking this as closed due to lack of activity. Feel free to reopen if the issue still persists.


undefined reference to `spoof_call2'

target\release\deps\apc-772f286d6c12883d.apc.bad2967599c135d4-cgu.0.rcgu.o:apc.bad2967599c135:(.text+0x38b79): undefined reference to `spoof_call2'
Using replace and syscall will cause errors during compilation;
nightly-x86_64-pc-windows-gnu
rustup 1.26.0 (5af9b9484 2023-04-05)
rustc 1.78.0-nightly (ef324565d 2024-02-27)
cargo 1.78.0-nightly (194a60b29 2024-02-21)

Use the toolchain set in .cargo\config file: x86_64-pc-windows-msvc. Let me know if that solves the issue.

yes issue was solved.thanks
不成大佬不改名！
@.***

------------------ 原始邮件 ------------------
发件人:                                                                                "Kudaes/Unwinder"                                                                                @.>;
发送时间: 2024年6月11日(星期二) 晚上7:03
@.>;
<EMAIL_ADDRESS>主题: Re: [Kudaes/Unwinder] undefined reference to `spoof_call2' (Issue #3)
Use the toolchain set in .cargo\config file: x86_64-pc-windows-msvc. Let me know if that solves the issue.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Great

Great


Improve live_logs websocket endpoint

The current websocket endpoint for log messages are basic strings with no structure.  A more structured format would be easier to work with; I would expect it to look something like this:
{
  "message": "...",
  "hostname": "some.domain",
  "level": "info"
}

It may also be useful to have the possibility of toggling loglevel or hostname filters on this endpoint

... turns out this is already the case! This PR  also solves all known issues with this endpoint so closing this issue


Distributed Tracing - Option to propagate trace context when dispatching celery tasks

Is your feature request related to a problem? Please describe.
To illustrate, consider a process from a client calling a process in a server via a HTTP API, which then dispatches a task to do some background work (e.g. sending email, etc.).
sequenceDiagram
    Note over client: (A) Do stuff and log what happened
    client->>API:  POST /api (now: includes trace context)
    Note over API: (B) Do stuff and log what happened
    API->>queue: dispatch task (now: DOES NOT include trace context)
    API->>client: 200 Ok
    queue->>celery-worker: push
    Note over celery-worker: (C) Do stuff and log what happened

Right now, the client sends the trace context to the server and we are able to correlate what happened in A with B.
This is possible via the distributed tracing feature.
The celery-worker is instrumented by the agent, but the API process doesn't send the trace context to the queue and we can't correlate C with A/B.
Indeed, we might not want to correlate those when thinking about performance of the API (the API doesn't wait the worker to reply to the client. they are decoupled).
But, in the context that we are using the distributed tracing to correlate application logs of different process, it would be VERY useful to have the link between what's happening in the worker (C) with A and B.
Feature Description
Given that there are scenarios where we don't benefit from propagating the trace to the worker and other scenarios where we want this, I believe the agent could include the option to execute the context propagation to celery tasks.
To be sure, the very same diagram with the propagation in caps :point_down:
sequenceDiagram
    Note over client: (A) Do stuff and log what happened
    client->>API:  POST /api (now: includes trace context)
    Note over API: (B) Do stuff and log what happened
    API->>queue: dispatch task (after: CONTEXT PROPAGATION)
    API->>client: 200 Ok
    queue->>celery-worker: push
    Note over celery-worker: (C) Do stuff and log what happened

Describe Alternatives
Open telemetry client does that
https://github.com/open-telemetry/opentelemetry-python-contrib/blob/main/instrumentation/opentelemetry-instrumentation-celery/src/opentelemetry/instrumentation/celery/__init__.py#L143-L154
https://github.com/open-telemetry/opentelemetry-python-contrib/blob/main/instrumentation/opentelemetry-instrumentation-celery/src/opentelemetry/instrumentation/celery/utils.py#L135-L140
And datadog agent as well
https://ddtrace.readthedocs.io/en/stable/advanced_usage.html#examples
Additional context
If the idea is welcome, I'm willing to contribute :hand: , since the python agent is open source.
Thank you !!
Priority
[Really Want]

Hey @msscaroso; we already have a Feature Request for this; however since this is open-source you are more than welcome to make a contribution for our team to review.
cc: @ak-war


Extension issue

Issue Type: Bug
Extension Name: html-css-class-completion
Extension Version: 1.19.0
OS Version: Darwin x64 19.6.0
VSCode version: 1.48.2

:warning: We have written the needed data into your clipboard. Please paste! :warning:

By Mistake create Bug report


Add Get-ShimCache Module

Add a Get-ShimCache Module that returns the output of ShimCacheParser as a powershell object.
This route was chosen because Mandiant keeps the tool updated for newer OS versions. It should be easier to maintain this way.
Requires ShimCacheParser to be created via pyinstaller.

Download ShimCacheParser from https://github.com/mandiant/ShimCacheParser
Install pyinstaller 'pip install pyinstaller'
Run 'pyinstaller -F ShimCacheParser.py'
Copy ./dist/ShimCacheParser.exe to \Modules\bin\

Closing this request while evaluating an alternative method suggested by EricZimmerman.


Daskversionfix 1v2

WIP do not merge

It works ... So I wonder why #3431 doesn't pick up dask 1.2 ? :confused:

I wonder why #3431 doesn't pick up dask 1.2 ?

😕 indeed.  N.B. the commit is exactly the same as the first one here.
However, it does seem to be an adequate fix ...

why #3431 doesn't pick up dask 1.2 ?

Comparing the conda list output, the only differences are ...

package
"OLD" pin dask>=1.1

//
"NEW" pin dask>=1.2

dask (AND dask-core)
1.1.4
py27_1
defaults
//
1.2.2
py_3
conda-forge

pyproj
1.9.6
py27h14380d9_0
defaults
//
1.9.6
py27h516909a_1002
conda-forge

In fact that's so odd I don't believe it.
Maybe the underlying channels have  just shifted ??
I will re-spin the original checks ...

I will re-spin the original checks ...

Nope, still does the same.
:sigh:


Add-on to current "time tracking" plugin

I like to stay in other tabs but am forced to watch when my next run is coming up.
Can we get something like what is in the "XP Tracker" and a "Add to canvas" feature.
I know some would love this for the more afk skills its easier to follow.
The notification currently doesn't work for me because I have desktop notifications off due to it interfering with my interface when I am bossing and what not.

Duplicate of #8500


SMTP Relay Script - Read Recipient from Console

Inform User about repeated Prompt for Recipient List

closed with Pull Request #95


Huntlion discussion

Do we need ~huntlion?
Also, bot will have to need changes to always change ownership to TA account when making sheets.
Also, how hardcoded do we want it

Same goes for anything that clones any spreadsheet, because we also have ~clonelion and ~clonetemplatelion which will have the same issues

Temporarily diabled these commands from user-facing side in 7137327. Will re-enable or delete as necessary post discussing
~template will also fall in same category


two types of error messages from mythril

Description
when running  mythril to analyze solidity files, there are two type of error messages:
command format: myth -v 4 analyze name.sol: contractName
error message 1:

error message 2:

Could you explain what error messages mean?
What factors cause these problems?
is there anyway to solve them?
Thanks

Thanks for the report. Are you running mythril in parallel? that may be the problem with the second error and also probably with the first error. If you are running it in parallel then run it using the docker container so there will be a separate signature.db file for each run.

Thanks!

Hi Norhh,
The second type of error still here!
I just use the command: myth analyze solidity_file_name. There is no parallel running.  this  second type of error still shows up.

Also, I run it in a docker container, it still has issue with 0 coverage.
I guess, there maybe some other factors like compiler version?
Thanks!

Seems like this is resolved, closing it 🙌


Question about "nongt_dim"

hi! do you know how 'nongt_dim' works?
https://github.com/msracver/Relation-Networks-for-Object-Detection/blob/e83e911d828e3c86624ce0aeb8d742d5ee67d5ba/relation_rcnn/symbols/resnet_v1_101_rcnn_attention_1024_pairwise_position_multi_head_16_learn_nms.py#L85
for example, nongt_dim = 2000(rois per image), when train, there is 2 images per batch, so 2000*2 rois. it will get the relation between every rois and first 2000 rois. but the rois of 2th image also get the relation about rois of 1th image. it is unreasonable.
thanks!

@lilichu Have you solved it? I also want to know the meaning of this parameter.

@jmuyjl Have you solved it? I

hi! do you know how 'nongt_dim' works?
https://github.com/msracver/Relation-Networks-for-Object-Detection/blob/e83e911d828e3c86624ce0aeb8d742d5ee67d5ba/relation_rcnn/symbols/resnet_v1_101_rcnn_attention_1024_pairwise_position_multi_head_16_learn_nms.py#L85
for example, nongt_dim = 2000(rois per image), when train, there is 2 images per batch, so 2000*2 rois. it will get the relation between every rois and first 2000 rois. but the rois of 2th image also get the relation about rois of 1th image. it is unreasonable.
thanks!

Can you tell me more about it? I'm also confused about this parameter

Have you saved this question? I am so confused!


Column size property for questiontype Matrix Dynamic

Are you requesting a feature, reporting a bug or ask a question?
Question
I noticed there is no Size property (or similar, it seems) for the columns when questiontype = matrix dynamic. Is there another way to specify column size in the editor/in the JSON code? Especially when celltype = comment a columnsize property would help when programming the back-end validation.
Specify your

browser:
browser version:
surveyjs platform (angular or react or jquery or knockout or vue):
surveyjs version:

@Lynn42 There is column.winWidth property.
Thank you,
Andrew


Sort a simple integer column

Could anyone give me a hint how I do a sorting on a simple integer column? I would like to have a select dropdown where I can choose between ascending or descending order.
Thank you

@ymc-sise why select??
You can do that by clicking on the header of your column (one click sorting ASC, one more click sorting DESC)

Oh I completely missed that :) Thank you!


double-click G bug

Crouch down and double-click G to drop all items. They will disappear and can be scanned, but cannot be seen or picked up.

Happened to us in MP too. Other mods affecting inventory were GeneralImprovements and HotbarPlus, nothing drop related though. Never happened to me as a host but happened to others. Not all of them though, just some. Also, double G drop didn't work for me at all. But for them it was insanely sensitive. They dropped all on one click.

I think this has something to do with an incompatibility with TLTwoHand or something else, I have had the same issue and tried disabling all other things that mess with the inventory/hotbar except for that.
There's also an issue with selling all, it only works once with 4 items, then you have to place more on the bench one by one until the hook swipes all the items. Once there's no items you can do it a single time again.
Don't have many issues while hosting except for that 2nd one.

您好，感谢您报告此问题。 我已尝试复制您的问题，但没有遇到任何问题，您是否使用过任何其他可能改变掉落或库存系统的模组？这种情况是每次都会发生还是仅在某些条件下发生，例如在地图上的特定部分或仅在多人游戏中？

Sorry for replying to you so late.
Yes, every time I join the game as a client, it causes this issue.
This is my mod list：
1、https://thunderstore.io/c/lethal-company/p/qingmi/buladeng_chunjing_mod_pack/
2、https://thunderstore.io/c/lethal-company/p/qingmi/buladeng_chunjing_funny_mod_pack/
3、The Chinese mod should have nothing to do with this.
https://thunderstore.io/c/lethal-company/p/qingmi/buladeng_chinese_mod_pack/

您好，感谢您报告此问题。我已尝试复制您的问题，但仍没有遇到任何问题，您是否使用过任何其他可能改变故障或库存系统的模组？这种情况每次都会发生仅在某些条件下发生，例如在地图上的特定部分或仅在多人游戏中？

抱歉这么晚才回复你。 是的，每次我作为客户端加入游戏时，都会导致此问题。 这是我的模组列表： 1、https://thunderstore.io/c/lethal-company/p/qingmi/buladeng_chunjing_mod_pack/ 2、https://thunderstore.io/c/lethal-company/p/qingmi/buladeng_chunjing_funny_mod_pack/
3、中文mod应该与此无关。 https://thunderstore.io/c/lethal-company/p/qingmi/buladeng_chinese_mod_pack/

In my mod list, there are mods that interact with the inventory：
vasanex-ItemQuickSwitch
FlipMods-HotbarPlus
ShaosilGaming-FlashlightFix
Renegades-WalkieUse
Renegades-FlashlightToggle


Can share the log in the process of training video_renderer or give some guidance in the loss change?

Hi,
Thanks for sharing code and your contribution in the field of talking head generation.
I am confused about the training loss of the video_renderer. I have trained the video_renderer in  LRS2 dataset which passed 24 epoches, 33220 steps, but the running_gen_loss seemed change randomly. The logs are as follow:

Is that normal or I did something wrong with that?  Looking for your reply! Thanks a lot!

When the traning came the 26 epoch,  step: 34560, the running_gen_loss dropped quickly. Just as following:


Examples won't compile (version number needs to be bumped?)

Hi, I'm very excited to start building Homie devices using my ESP8266 boards! I've just installed Homie using PlatformIO's library manager, which works, but the LED strip controller example won't compile.
error: 'HomieRange' was not declared in this scope

My local copy of Homie 1.5.0 doesn't have Homierange.cpp. I think this is because when you added HomieRange, and updated the examples to use it, you didn't change the version number. As a result the version in PlatformIO's repository hasn't been synced with the new additions.

Pinging @ivankravets as I just noticed you're a contributor here too.

You use stable 1.5.0 version where this HomieRange has not been implemented yet. If you want to try development version of this library, you should use GitHub URL or path to archive with latest sources. For example,
platformio lib install https://github.com/marvinroger/homie-esp8266.git
platformio lib install https://github.com/marvinroger/homie-esp8266/archive/master.zip

In any case, you should deinstall previous stable version via platformio lib uninstall Homie.
I recommend to use first option with GIT VCS. In this case, platformio lib update Homie will automatically sync library with thisrepository.

Great, thanks a lot! It compiles now using the latest source from the repository.

Thanks @ivankravets for the explanation
@zouden the code in the master branch is the 2.0.0 one, which is not yet released. As a result, PlatformIO does not know HomieRange. It's not a mistake, it's just the v2 is not ready.
Examples are bundled within each release. For PlatformIO, I don't know if there's a built-in way to show examples from the CLI, but the examples on the Homie PlatformIO page are the right ones, the 1.5.0 examples.

Examples are located in the same directory where library is installed. @zouden check it via pio lib list, where you will Library Storage path, follow to Homie and check examples folder.


Add Light-Dark mode

I can Add Light Dark Mode to all of the pages which adds another feature to this website and which just gives two choices to the user as whats its preferable UI is either light or dark.

it's already there, but you can improve if wants to

In the sidenav,
the last 2nd option i.e. Change mode


[FREEMARKER-7] convert to Maven build

fixes FREEMARKER-7
This is a PoC for a proposal:
Make a new 3.0.0-branch with only the following features:

Maven Build (this PR) fixes FREEMARKER-7
Bump to Java 8 (this PR)
Remove old Jython, JSP and servlet implementations (this PR)
Add module-info.java (later PR)
relocate base package to org.apache.freemarker (currently: freemarker).

This would be a very slight change for users which would be a good stepping stone towards a 4.0 release (current 3.x branch).

[ERROR] Tests run: 899, Failures: 12, Errors: 0, Skipped: 2

I'd say not too bad for the first try :)

Down to three test errors:
Error:  Failures:
Error:    RealServletContainertTest.basicELFunctions:116->WebAppTestCase.assertJSPAndFTLOutputEquals:150->WebAppTestCase.assertOutputsEqual:155->WebAppTestCase.getResponseContent:92 Expected HTTP status 200, but got 500 (message: Server Error) for URI http://localhost:36263/basic/tester?view=customELFunctions1.jsp
Error:    RealServletContainertTest.basicELFunctionsTagNameClash:124->WebAppTestCase.assertJSPAndFTLOutputEquals:150->WebAppTestCase.assertOutputsEqual:155->WebAppTestCase.getResponseContent:92 Expected HTTP status 200, but got 500 (message: Server Error) for URI http://localhost:36263/basic/tester?view=elFunctionsTagNameClash.jsp
Error:    RealServletContainertTest.basicTrivial:77->WebAppTestCase.assertJSPAndFTLOutputEquals:150->WebAppTestCase.assertOutputsEqual:155->WebAppTestCase.getResponseContent:92 Expected HTTP status 200, but got 500 (message: Server Error) for URI http://localhost:36263/basic/tester?view=trivial.jsp

Sadly there is not description for the exception:
Error:  Tests run: 17, Failures: 3, Errors: 0, Skipped: 1, Time elapsed: 3.509 s <<< FAILURE! -- in freemarker.ext.jsp.RealServletContainertTest
Error:  freemarker.ext.jsp.RealServletContainertTest.basicELFunctions -- Time elapsed: 0.040 s <<< FAILURE!
java.lang.AssertionError: Expected HTTP status 200, but got 500 (message: Server Error) for URI http://localhost:36263/basic/tester?view=customELFunctions1.jsp
	at org.junit.Assert.fail(Assert.java:89)
	at freemarker.test.servlet.WebAppTestCase.getResponseContent(WebAppTestCase.java:92)
	at freemarker.test.servlet.WebAppTestCase.assertOutputsEqual(WebAppTestCase.java:155)
	at freemarker.test.servlet.WebAppTestCase.assertJSPAndFTLOutputEquals(WebAppTestCase.java:150)
	at freemarker.ext.jsp.RealServletContainertTest.basicELFunctions(RealServletContainertTest.java:116)
	at java.lang.reflect.Method.invoke(Method.java:498)

Error:  freemarker.ext.jsp.RealServletContainertTest.basicTrivial -- Time elapsed: 0.020 s <<< FAILURE!
java.lang.AssertionError: Expected HTTP status 200, but got 500 (message: Server Error) for URI http://localhost:36263/basic/tester?view=trivial.jsp
	at org.junit.Assert.fail(Assert.java:89)
	at freemarker.test.servlet.WebAppTestCase.getResponseContent(WebAppTestCase.java:92)
	at freemarker.test.servlet.WebAppTestCase.assertOutputsEqual(WebAppTestCase.java:155)
	at freemarker.test.servlet.WebAppTestCase.assertJSPAndFTLOutputEquals(WebAppTestCase.java:150)
	at freemarker.ext.jsp.RealServletContainertTest.basicTrivial(RealServletContainertTest.java:77)
	at java.lang.reflect.Method.invoke(Method.java:498)

Error:  freemarker.ext.jsp.RealServletContainertTest.basicELFunctionsTagNameClash -- Time elapsed: 0.015 s <<< FAILURE!
java.lang.AssertionError: Expected HTTP status 200, but got 500 (message: Server Error) for URI http://localhost:36263/basic/tester?view=elFunctionsTagNameClash.jsp
	at org.junit.Assert.fail(Assert.java:89)
	at freemarker.test.servlet.WebAppTestCase.getResponseContent(WebAppTestCase.java:92)
	at freemarker.test.servlet.WebAppTestCase.assertOutputsEqual(WebAppTestCase.java:155)
	at freemarker.test.servlet.WebAppTestCase.assertJSPAndFTLOutputEquals(WebAppTestCase.java:150)
	at freemarker.ext.jsp.RealServletContainertTest.basicELFunctionsTagNameClash(RealServletContainertTest.java:124)
	at java.lang.reflect.Method.invoke(Method.java:498)

As of migrating away from Ant, there's already a PR for a Gradle-based solution, that keeps binary backward compatibility, while still modularizes the source code (as it's in the current 3.x). That also can handle the cases where we depend on multiple versions of the same artifact (like even of Java), which we sometimes need (in 2.x, as we have a monolithic artifact, for backward compatibility).
As of the Maven package name change, I'm against thing that are annoyances for the users without bring significant new functionality in exchange. At least last time I checked, renaming a Maven group is a pain for its consumers, because then Maven won't do version conflict resolution between the old and new artifacts, and you end up having multiple version of the same classes in your application. (So you then should also rename the Java packages, but that's an even more drastic change, and should have really good reasons, like if you want to break backward compatibility in template language rules etc., as in te current 3.x.)

As of migrating away from Ant, there's already a PR for a Gradle-based solution, that keeps binary backward compatibility, while still modularizes the source code (as it's in the current 3.x). That also can handle the cases where we depend on multiple versions of the same artifact (like even of Java), which we sometimes need (in 2.x, as we have a monolithic artifact, for backward compatibility).

I know. But since we are Apache, you'd get plenty of help from other foundation members, committers etc. We already have an Apache-based project setup which adds the benefit of streamlined releases, reproducible releases etc.
If you want to do the same work again, I won't stop you. But that means I cannot contribute, as my knowledge of Gradle is very limited. And that might be true for a lot of other Apache committers.
As for the backward compatibility:
Breaking changes is what major releases are for. It it was not breaking anything, don't update the major version.

As of the Maven package name change, I'm against changes that are annoyances for the users without bringing significant new benefits in exchange.

No need to do that right now, BUT it would be worth it to streamline Apache projects.
Again, if you need help -- the maven team can help you.

At least last time I checked, renaming a Maven group is a pain for its consumers, because then Maven won't do version conflict resolution between the old and new artifacts, and you end up having multiple versions of the same classes in your application.

That is not entirely true. First of all, dependabot, renovate etc. can read the relocation from the pom.xml:
https://maven.apache.org/guides/mini/guide-relocation.html

(So then you should also rename the Java packages, so the two artifacts can co-exist, but that's an even more drastic change, and should have really good reasons. Like when you want to break backward compatibility in template language rules anyway, as in the current 3.x, then you should do that. But not just for aesthetic reasons for sure.)

Other projects did this as well, see Junit 4 to JUnit Jupiter. I never saw anyone being trapped with this. On the contrary, it was helpful that two major versions could co-exist: Migration does not need to be done at the same time for all files. This could be true for Freemarker.

To summarize:
With only the changes mentioned in the first post of the PR, users would have a migration release which does not expect a lot of work:

stay at single-jar dependency
relocation is pretty easy
renaming packages is pretty easy
module identifier is consistent, not split packages
Path to Java 8 opened
Abandon old JavaEE 5 APIs.

Again, I am only saying "move your 3 branch to 4 and keep Gradle".
I did not say "abandon it".
The idea is that I want to use freemarker with JPMS right now and don't want to wait for the current-3-branch for two more years with so many breaking changes etc. which is way more pain.

As for backwards compatible binary: We can still do that in a multi-module setup with maven. And I disagree with your opinion that this is less feasible with Maven. We could do that right now.

The idea is that this is merged into a new branch, a new 3 branch. Yes, the idea here is to change a few things, see on the mailing list.
Intermediate release with just
Java 8
Remove some old APIs (jsp, servlet),
...
But yes, changing the location is not needed here.

To clarify, for anyone else looking at this, FREEMARKER-7 was closed like 5 years ago. That's when the "3" branch switched to Gradle. Then even that was modernized, and there's a similar Gradle PR for 2.3.x: https://github.com/apache/freemarker/pull/79 (FREEMARKER-204). I'm not aware of any issue with that.

there's a similar Gradle PR for 2.3.x: https://github.com/apache/freemarker/pull/79 (FREEMARKER-204). I'm not aware of any issue with that.

oh, I did not know: the only issue is that it's not merged

Thanks for the clarification. Closed in favour of new PRs.

there's a similar Gradle PR for 2.3.x: #79 (FREEMARKER-204). I'm not aware of any issue with that.

oh, I did not know: the only issue is that it's not merged

Yeah... The reason it's not merged that it makes the source code modular, just like in "3" (but here it still generates a single monolithic jar), so if I merge it, I will break all pending PR-s (or I think so). So I have to review and merge those first... And I couldn't catch up so far. And then merge the Gradle one. And then have time to check if it can go into the release.


Instagram changed something in the main feed again

@y252328  Instagram changed something, on the main feed the download buttons don't appear anymore.

just got that today too, download button is gone everywhere except for stories and profile for avatar
Happens on firefox desktop and android and edge, script version 1.17.5


Assertion failed in websocket/impl/write.ipp line 468

Version of Beast 79
Sometimes I get Assertion failed in websocket/impl/write.ipp line 468
Can you explain some cases make assert failed in this code ?
Thanks.

Yes, there was a bug that got fixed in a later version. Please use version 124:
https://github.com/boostorg/beast/tree/v124

Has this issue been resolved?

It seems this is resolved in the newer version of Beast, so I'll go ahead and close this. If the problem persists feel free to open a new issue, thanks!


Unable to hardcode the OMP_NUM_THREADS into program

Hi, I want to run mxnet in single thread mode, and for some reason I can't set environment variables.
First I recompile the library without MKL-DNN and OpenMP support using the latest code and hardcode "MXNET_ENGINE_TYPE=NaiveEngine"
Then I want to set OMP_NUM_THREADS=1 in a similar way.
Here's what I done, I modify some code in openmp.cc
OpenMP::OpenMP()
  : omp_num_threads_set_in_environment_(true) {
    enabled_ = true;
    omp_thread_max_ = 1;
}

void OpenMP::on_start_worker_thread(bool use_omp) {
  omp_set_num_threads(1);
}

void OpenMP::set_reserve_cores(int cores) {

  CHECK_GE(cores, 0);
  reserve_cores_ = cores;
  omp_set_num_threads(1);
}

int OpenMP::GetRecommendedOMPThreadCount(bool exclude_reserved) const {
  return 1;
}

But the program will create 56 workers as usual.
When I set environment variable OMP_NUM_THREADS=1, there would be only one worker.
I don't see how the program would handle this environment variable.
And if I really want to hardcode this, what should I do?
Thanks a lot!

Can you list the mxnet build cmd? If you're using openblas, I doubt the openmp threads are introduced by it. Maybe you can try to rebuild openblas without openmp.

Yes, the threads are created by openblas, and I rebuild the openblas setting the number of threads to one, then problem solved.
Thanks @ZhennanQin

@MediosZ how did you rebuild openblas setting the number of threads to one??. And by your responses I understood that OpenMP wasn't the issue, it was OpenBlas. Please correct me if I am wrong.

Setting OPENBLAS_NUM_THREADS=1 also limits the number of threads to 1.


Request: Allow deletion of individual cached models.

Would it be possible to allow deletion of individual cached models using the GUI?

Hi! Please check this example: https://github.com/mlc-ai/web-llm/tree/main/examples/cache-usage
With these APIs, you can: delete a model's weights, a model's config, a model's WASM, or all of these for a model.
A developer can build GUI with these APIs.

Whoa, I built this manually. But of course there's an API for this. Awesome.

Closing this issue for now, feel free to open new ones.


feat: clone marquee slides for infinite effect

The feature previously snapped to the start when reaching the end, but now the last selected slides are duplicated to create an infinite and seamless effect.
This could be a breaking change for some like me, who have patched this by duplicating the slides manually prior to passing them to the SliderTrack. Due to this, you may want to change this to a toggled feature in the SliderProvider.

Also noticed a bug (potential unexpected feature)
If you only provide 1 slide but set slidesToShow to 10. It will duplicate the single slide and marquee rather than the previous result which would show 1 and not move.

Hey @kalon-robson!!! This is amazing. I have noticed the same effect before and always wished to the find time fix it, so THANK YOU. I'll be sure to dive deeper into this as soon as I can.

but now the last selected slides are duplicated to create an infinite and seamless effect.

Can you explain this a little but further? What do you mean by "last selected slides" and also can you describe you're method of "duplicating"?

I can't even remember why I wrote that. What I'm doing is running a useEffect in SliderTrack that checks to see if marquee is enabled. If so, it will then clone a selection of slides from the start, depending on the number of slidesToShow. Once cloned, it appends them to the track.
If I have 5 slides and slidesToShow is 2 it will take the first two slides and duplicate them onto the end (making the number of slides 7). Then, when it scrolls to the end the view looks identical ready to snap back to the start.


[FEATURE] OpenSearch-Project workflow manager

Is your feature request related to a problem?
As an organization, there are policies that should be enabled on all repositories, such as enforcing the use of the DCO [1], supporting consistent platforms in continuous integration tests [2], and ensuring repositories are using consistent labeling for untriaged issues [3].
There are easy ways to roll out these changes, such as the GitHub App that has been used for DCO checks.  Or the more often-used creation of a campaign with issues created in all repositories, actively driving those issues to resolution in all repositories.
GitHub Apps need to be a special purpose and take effort to create, publish, and maintain.  Whereas manual issues can support any kind of flexibility.
Maybe there is space for a middle ground that could be easier to centrally manage and support customization.
What solution would you like?
Let's build a system to can inspect and update GitHub Action workflows in the organization.  Built out as a GitHub Application it would read from a repository to discover workflows and then deploy to those repositories.  Add some filtering metadata on those workflows and different policies would be applied where needed.
This would allow authoring a workflow update/create, review, and then deployment to be managed via a single pull request in the configuration repository.  Adding individual workflow is simpler than a GitHub App and easier to customize based on the target repository.
Do you have any additional context?

[1] https://github.com/opensearch-project/.github/blob/main/CONTRIBUTING.md#developer-certificate-of-origin
[2] https://github.com/opensearch-project/opensearch-build/issues/33
[3] https://github.com/opensearch-project/.github/pull/111#issuecomment-1334328082
[4] https://github.com/opensearch-project/.github/pull/112

I feel like this would be a step backwards, as the apps significantly simplify deployment and maintenance, and are automatically enabled for new repos.

For me, the overhead for an individual app is prohibitive for handling the untriaged label.  Here is a diagram that might help clarify this proposal for a GitHub App that can be configured/managed via an open centralized config repository - does this still seem like a backwards step?
graph LR
   app(Workflow Management
GitHub App) -- Install App for all repos --> osp(OpenSearch Project)
   app -- Read Workflows / Config --> cr[GitHub Org Workflow Configure Repo]
   app -- Sync managed
 .github/workflows/* --> sec[Security Repo]
   sec --> gha(Github Actions)
   app -- Sync managed
 .github/workflows/* --> os[OpenSearch Repo]
   os --> gha
   app -- Sync managed
 .github/workflows/* --> etc[[... Repo]]
   etc --> gha

style gha fill:#9f6,stroke:#333,stroke-width:4px;
style app fill:#f96,stroke:#333,stroke-width:4px;

Would you prefer we made a GitHub app for each kind of workflow we'd like to enforce, such as the untriaged flow?

For me, the overhead for an individual app is prohibitive for handling the untriaged label. Here is a diagram that might help clarify this proposal for a GitHub App that can be configured/managed via an open centralized config repository - does this still seem like a backwards step?

I think so, but it's just my 0.02c because of below ...

Would you prefer we made a GitHub app for each kind of workflow we'd like to enforce, such as the untriaged flow?

Yes. Conceptually org-wide processes should be enforced at org-wide level. I actually have more feature requests for the label app. For example, I'd like to enforce a minimum set of labels across all projects, such as performance.

I think we need something like https://organizer.gitconsensus.com/#/

Nice find!  I'd much rather adopt an existing tool and we can always contribute back if we'd need more functionality.  Want to create an issue with a proposal for it / your use cases?

Coming from https://github.com/opensearch-project/opensearch-plugins/issues/201#issuecomment-1429020772
This is nice!

github-org-sync(-action) is a tool to sync files from a skeleton/template repository to other repositories in your organization.

Found github-organization-sync-er while that tool doesn't look like it is in active development, maybe it could be resurrected or forked?

https://github.com/marketplace/actions/github-organization-sync-er
https://github.com/hostwithquantum/github-org-sync-action


SenseHat LED matrix not responding

Hello all,
I have the problem that on both of my Raspberry Pi (2 &4) the Sense Hat LED matrix is no longer responsive. After powering on the Pi, the LED matrix lights up in rainbow colors. But then the LED matrix does not respond to any commands - that is, it does not display anything when you want to display text on the LED matrix. No error message is displayed.
At first I thought it was a hardware defect. For testing I connected the Sense Hat to my old Raspberry Pi 2 - it worked as usual. Then I updated the Raspberry Pi 2 (sudo apt update && suso apt upgrade). After that, the error also occurred on the Raspberry Pi 2 - as described above. It must be a software / driver problem. The error occurs with a Sense Hat V1 like Sense Hat V2.
Have any of you experienced the same phenomenon or have an idea how I can narrow down or fix the error?
(Temperature, humidity and pressure sensor are working normally).
Greetings DMHas
Translated with www.DeepL.com/Translator (free version)
Update: With a fresh image (without updates - created with Raspberry Pi Imager) works the LED-Matrix fine. (I guess the new firmware update for the Raspberry Pi is the problem.)

I have experienced the same problem on a Raspberry Pi 4 with a Sense Hat V2. I can also trace back my initial problems to updates I have made in the last few days.
I have not tried to re-flash my SD card with a fresh image yet, though I suspect that would solve my problem as well.
Currently I am attempting to determine which updates break the LED matrix API so that I can roll them back. Please let me know if you determine which updates affect the Sense Hat, and which versions are stable to use currently.

That would've been the kernel update. Something broke in the move to 6.1.

Same here, seems only to affect the LED matrix.
Confirmed not working with 6.1.19-v8+ #1637 SMP PREEMPT Tue Mar 14 11:11:47 GMT 2023 aarch64 GNU/Linux.

Thanks all for confirming. I open a new issue here: https://github.com/raspberrypi/firmware/issues/1798

This has been fixed today. You can install a beta kernel with sudo rpi-update.

This has been fixed today. You can install a beta kernel with sudo rpi-update.

I just installed the beta kernel. It fixed the LED matrix but seems to have broken the temperature and humidity measurements. The pressure sensor is still reading something, while the other two are "0". Can anyone reproduce my experience?

It has also been pointed out that the mmap support got broken back in 5.18, but https://github.com/raspberrypi/linux/pull/5404 should fix that.

@pelwell , @DMHas : I just installed the beta kernel. It fixed the LED matrix but seems to have broken the temperature and humidity measurements. The pressure sensor is still reading something, while the other two are "0". Can anyone reproduce my experience?

I can't confirm the zero values after firmware update.
But my both RasPi's (2B & 4 with 8GB) and both SenseHat's (V1 & V2) shows this behavior sometimes. Turn off and turn on fix it (restart change nothing). The RasPi 2 shows the zero values often as the RasPi 4. It happens more, when 2 program's have access to temperature, air pressure and humidity at the same time. (May be it is depending from the CPU load or GPIO load.)

The only issues that have been addressed are the cancelling of deferred I/O on close and the mmap() breakage. Please open a new issue if you are seeing other problems.

I will observe the behavior. If it happens again, I will open a new thread


[Feature Request] flutter and dart command without proxy

I think using fvm together with flutter and dart proxy commands is unnecessary.
Also, proxy command responses are not colored. #202
The autocomplete function of the ohmyzsh plugin cannot be used together.
Like nvm or pyenv, it would be better to separate the proxy command or use the command prompt display.
For example,
$ fvm use 3.0.4
$ (fvm) flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 2.10.4, on macOS 11.6.4 20G417 darwin-x64, locale ko-KR)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.1)
[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
...

Thanks for your attention. I’m looking forward to your reply or feedback.

@jeesang7 you are able to use FVM cached versions without the proxy. https://fvm.app/docs/guides/running_flutter#call-sdk-directly, however keep in mind that proxying might be needed when running scripts and tooling that are dependent on the Flutter configured version, as FVM injects the select cached version in the env vars of the process


Content isn't loaded in the editor

We have reports by some users that sometimes content isn't loaded in the editor. It happens less than 0,1% of the times, our users have used the editor around 200.000 times without problems but we have around 40 reports of content not being loaded. It's more likely to happen with users with slow connections or that use many photos in their content.
We use the Redactor 9 version and we are not updating to Redactor 10 for this reason.
We have tryed to solve this by gaining more control over the load process so we switched to RequireJS but it didn't solve it.
Analyzing the code we have detected a theorical point in failure in line 29 but we are unable to verify it in the practice.
We modified line 29 this way:
if (scope.redactorLoaded)
ngModel.$setViewValue(value);

Hi brainsqueezer,
Did you find any solution for this issue? We're also getting this issue some time. We've Redactor version 10.1.1
To solve this issue, we're updating redactor model manually under $timeout. Since it's hard to re-produce, we're still waiting for another report for this issue.
Another issue we found: Sometime Redactor source doesn't update any text but it appears on Redactor front-end. In this case, callback like onkeyup, onchange, onblur etc. doesn't fire on writing any text on Redactor. We're not able to find any solution for this and for now just showing an alert to user by checking "redactor is properly loaded or not (scope.redactorLoaded)" in 5 seconds.
Kindly let us know if you've any idea or solutions for above mentioned issues.


Is it possible to use OLS UI components in other websites?

Hi SPOT Team 👋,
I have a simple question. Is it possible to include someway the Tree view UI component on a website (maybe using an iframe?). We are evaluating options to show the ChEBI Ontology on the new ChEBI website and we are studying a few options.
Thank you!

cc @rombaum

Hi @CarMoreno! the component you mentioned is not being maintained by us anymore so unfortunately we won't be able to help here 😢 This is the treeview component we currently use in ols but it won't work out of the box as a widget atm.

(Reopening because it would be nice if the docs I wrote above didn't get lost, but up to @henrietteharmse what to do with them)

Hi @jamesamcl It would be wonderful if those components, or at least Tree view for now, could be published on npm. If you guys ask me, OLS widgets are clean and very usables. Have you guys thought about publishing UI components as npm packages?. For ChEBI team would be very useful at least having Tree view for our ChEBI website.
cc @eloyfelix

@jamesamcl  Yes, indeed the "docs" added now is useful. It would have been helpful if it was added when the component was added. When we looked through the code base we could not find it.
I will assign Haider to have it published on npm with your help.

Thanks, @haideriqbal lets look at this next Thursday when I’m in the office

Hey everyone! Just wanted to check in and see if there's any update on when the package might be published? It would be really helpful for us to know so we can start planning some topics on our end. Thanks a bunch! :)

Hi @CarMoreno! we still need to coordinate this within our team and once we have a timeline we'll let you know soon :)

@CarMoreno I don't want to hijack this discussion here.  But maybe our widgets are also interesting for you. We developed one of the widgets together with @jamesamcl and @serjoshua in the past. This is also the part @jamesamcl was talking in his earlier comment. Nevertheless we are provided a whole suite of different React-based widgets which should be compatible with OLS3 and OLS4. There will be a bigger update of the widgets in the next week. In this update we will also provide the tree widget from OLS4 directly. If you are interested just contact me. @matentzn thanks for pointing me to this post.
https://github.com/nfdi4health/semlookp-widgets
Nevertheless were are also interested in the npm publication. Since it is easier for us to reuse this widget in our suite.

Hi @rombaum, thank you for your reply. We are using VueJS in the frontend, so I do not know if seemlookp-widgets package will be compatible with our code, what do you think?. I was checking all the components and it is a great job. If the new tree view will be released next week and, if it is compatible with VueJS, I think we could use it.

Hey @CarMoreno there is already a proof-of-concept branch with a JavaScript version of the widgets. This will be released on a regular basis in the future. We will focus on this after the bigger update mentioned before. So at least this should work for you.

@CarMoreno we have published the treeview component on npm (https://www.npmjs.com/package/@ebi-ols/ols4-widgets?activeTab=readme) and you can use it in your webapp now :) The readme has an example of how to use it with React framework which you can use as a reference for your VueJS application.

@haideriqbal and the entire team, thank you immensely for not only delivering a quick solution but also for the exemplary code example and comprehensive documentation 🙌 . We are going to put effort into integrating the solution provided in our VueJS application this week. If we have any feedback or additional comments, we'll communicate them to you!

Hi @CarMoreno , thank you for your kind words... let us know if you need any further help :)

@CarMoreno I will look into it and get back to you :)

New widget is published here: https://www.npmjs.com/package/@ebi-ols/ols4-widgets Closing this issue now :)

Hi @haideriqbal, I hope you're doing well. I wanted to apologize for my delayed response; priorities have shifted a bit since we last discussed this feature, and I also took a few days off for the holidays. I reviewed the component today, and it looks fantastic, we are just thinking of customizing it even more.
PD: I was talking with @theArsalanM and he told me that we could use the OLS API to get customized results and show our graph using data from there. So we will be exploring that option.
Thank you very much again for your excellent work!


Added tarampampam/webhook-tester in the DockerCompose stack to test subcriptions locally

Testing subscriptions using external websites can lead to confusion because of rate limiting.
Using a self-hosted webhook tester can prevent unwated rate limiting when testing/developing.
Obviously, this is not meant for production and shouldn't be shipped by default when deploying Cloud Streams.

@JBBianchi Are you sure that service does not define rate limiting? All webhook.site like apps I saw come bundle with it out of the box.


Autocomplete for #cite does not work

Description
Support for autocompletion for #cite mentioned in  this issue does not seem to work in the current version of the app, as can be seen in the included screenshots. Typing a < also does not trigger a suggestion list.

Reproduction URL
https://typst.app/project/rD0GBvitfTqHqNn7ZHx-ff
Browsers
Firefox, Chrome
OS
Linux

Interestingly, I can reproduce this with 0.11.1+, but not 0.11.0. So it seems like a 0.11.1 regression.


Use a single instance of PagePermissionPolicy in wagtail.permissions module

Instead of instantiating PagePermissionPolicy everywhere we need it, create a single instance of it in wagtail.permissions, following the pattern for other permission policies. (I probably should've done this from the start...)
I imagine we could maybe spin wagtail.permissions into an actual app later, and you can replace it with your own app that subclasses the app config, with your own permission policies. Or maybe not an app, but something that lives in wagtail.permissions for the default instances of permission policies, with wagtail.permission_policies (or later rename it to wagtail.permissions.policies?) providing the default implementations of the policies.
Later on, we can maybe create a registry that maps model classes to the permission policy instances. This is where you'll register permission policies for your own models, including snippets.
I think instead of having permission policies be defined through the viewsets/views, it makes more sense to have a separate place dedicated for permissions. The reason being, permissions are a central piece that does not have to be tied to views. Views can do permission checks, but if you need to do permission checks elsewhere (e.g. a programmatic action, a background job), you shouldn't need to know the viewset the model is registered with. In most cases, you want the permission checks to have consistent results, regardless where/in what context you're doing it from.
Finally, if we could figure out how PagePermissionTester fits in all this, it would be great to have a similar approach for snippets/models managed via ModelViewSet.
Please check the following:

[x] Do the tests still pass?[^1]
[x] Does the code comply with the style guide?

[x] Run make lint from the Wagtail root.

[ ] For Python changes: Have you added tests to cover the new/fixed behaviour?

[^1]: Development Testing
[^2]: Browser and device support
[^3]: Accessibility Target

Thanks @gasman, I thought about that but I think it's better to wait until we have a better idea how to proceed from this. I explored the idea of having a registry for the permission policies in #11268. That would replace most changes in this PR in favour of something like policies_registry.get_by_type(Page), to allow the policies to be defined at runtime instead of at import time. If that's the way we're going to proceed, then we shouldn't recommend importing the default policy object directly from wagtail.permissions.
However, with the discussions we had this morning about potentially using a registry for PermissionTesters and exposing that instead of permission policies, that might change the end result. That is, if the permission policies are not something we want to allow to be customisable, then defining it at import time is fine (and we could call out the changes in this PR in the release notes).
Let's revisit that decision closer to the release. Hopefully we'll have a better picture of what we want to expose to developers. In the meantime, I think this PR is still worthwhile to merge so at least the way we use PagePermissionPolicy internally is consistent with the other permission policies.


System colors not updating when changing the Neutral key colors

Currently the neutral / neutral variant roles inherit default settings from the primary color. When you tryin to override that color, and update, the reference colors change but not the system.
E.G We would like green hue to be primary and purple to be neutral.
Here are the steps we took

Change primary color to green
Change neutral color from green-ish hue to purple hue
Hit update
Change neutral variant to same key color as neutral
Hit update

Screenshot 2024-03-21 at 3 17 20 PM

+1 to this issue

Looks like this is related or similar to this issue: #318
I reported my issue there, which is the same issue here.

I have a similar issue with the Color Styles in Figma.
Even after changing them, the generated neutral and neutral-variant color styles remain the default colors.


Add negation to search domain

["!", ["tag", "includes", "foo"]]
Maximum of one field!

Fixed since 5cb48324259fc0a8d7498b82e14b620f1e03edd4


New version: FLANN v1.0.1

Registering package: FLANN
Repository: https://github.com/wildart/FLANN.jl
Created by: @wildart
Version: v1.0.1
Commit: 892f48f6cc1167374563fb93fcf0b0be7548cda5
Reviewed by: @wildart
Reference: https://github.com/wildart/FLANN.jl/issues/19#issuecomment-497534818
Release notes:

fixed the index correction for matrix

TagBot tag


How do I ensure my .bot file settings aren't user-readable after deployment?

While the deployment section doesn't outline putting the 'production' endpoint in the .bot file, I'm not comfortable doing so as the appid and password would be human-readable. There is no documentation on how to prevent people from reading these settings in the .bot file to separate roles in a DevOps environment (like we used to do with Application Settings on web apps).

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

ID: cf112c0a-0400-ede4-ab7c-ce10f86d6f30
Version Independent ID: 5fa92c50-b8d1-460c-aa3c-f3f851c15da9
Content: Deploy your C# bot using Visual Studio - Bot Service
Content Source: articles/bot-builder-howto-deploy-azure.md
Service: bot-service
Product: bot-framework
GitHub Login: @ivorb
Microsoft Alias: v-ivorb

If you encrypt the bot file using msbot tool before deploying back to azure, does that not work?

Closing as a duplicate of #902.


governance: update migration logic in GovernanceDelegation

Description & Context
For interop, the governor will have to be updated use the L1 block number instead of the OP L2 block number as networks in their superchain will have their own cadence of blocks.
Proposed by @smartcontracts, the interop update introduces breaking changes so it's better to have the delegation state separated: the legacy state in the GovernanceToken (with L2 block number), and the new state in the GovernanceDelegation contract. This means that the GovernanceToken doens't call the GovernanceDelegation in its getter functions, and vice versa.

I'd like a review from @smartcontracts given he has the most context here


low latency V3 snapshot recovery

This patchset is intended to fix network errors such as:
rafthttp: dropped internal raft message to fd422379fda50e48 since pipeline's sending buffer is full (bad/overloaded network)
when recovering a large v3 snapshot.

LGTM. Assume you have tested it. After separate out the applier thing, we probably can also add unit test for the behaviors. We do not have unit test covering this since the server loop was huge.


⚠ RbxVeri has degraded performance

In e32f17a, RbxVeri (https://verify.triza.dev) experienced degraded performance:

HTTP code: 200
Response time: 3010 ms

Resolved: RbxVeri performance has improved in 6f77665.


GitHub actions ci

I'm very familiar with this branch so it all looks fine to me hahah, so maybe someone else that hasn't worked that much on the branch should approve it


R.6. - Set up tests

There don't appear to be any tests that came with the code base. We should set up the testing framework so that as we contribute to the codebase we can write unit tests to verify our contributions.
There should be a testing framework that comes with ASP.NET. We should set it up and add any tests we can think of for the existing code base.

@ramseyharrison we merged your PR for this, is there anything else you need to do? If not, you're good to close this issue 👍

Closed by #18