Skip to content
#

instrumentation

Here are 393 public repositories matching this topic...

objection
Techbrunch
Techbrunch commented Apr 19, 2020

According to the documentation in the wiki:

Frida scripts loaded with the import command are also run as jobs automatically

Describe the bug

When loading a script with the import command, the script is successfully loaded but no jobs is created.

To Reproduce

  1. import test.js
  2. jobs list

Expected behavior

The job should be listed when running jobs list

**E

IGx89
IGx89 commented Mar 7, 2020

Hello! The documentation appears to indicate that Format can be specified on the command line for the VSTest integration (see https://github.com/tonerdo/coverlet/blob/master/Documentation/VSTestIntegration.md#coverlet-options-supported-by-vstest-integration), but it provides no examples on how to do so and I've had zero luck figuring it out myself. Assuming that is indeed possible, would someone b

aki-0919
aki-0919 commented Apr 21, 2020

I guess the last condition of this line should be typeof options2.port !== "number", not options.port.

If OPCUA server is created without port, it throws error of expecting a valid port (number)

Works: server = new opcua.OPCUAServer({ port: 26543 });
Error: `server = new o

bug
bryanhuntesl
bryanhuntesl commented Jul 9, 2019

Is this expected behavior ?

I declare a metric with a microseconds suffix :

@histogram [
    name: :http_check_duration_microseconds,
    labels: [:target],
    buckets: :default,
    help: "Http check execution time"
  ]

And I then feed it a microseconds value (20481):

Histogram.observe(
      [name: :http_check_duration_microseconds, labels: [target]],
      t
JustAPerson
JustAPerson commented Mar 5, 2017

I was first curious if it was possible to easily modify things to use the full paths of items (module::fn_name instead of fn_name), but asking on #rust-internals, that may be impossible. So I guess perhaps an alternate scheme would be to allow an argument to the attribute, specifying a name.

#[flame("module::fn_name")]
fn fn_name() {}

I think that would be a really usefu

Improve this page

Add a description, image, and links to the instrumentation topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the instrumentation topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.