ScrollArea doesnt work under IE 11

Cheers.
when rendering page in Internet Explorer 11 invariant.js throws error:

e.render(): A valid React element (or null) must be returned. You may have returned undefined, an array or some other invalid object.

chrome, firefox, safari, opera work just fine;
main.js as basic as it gets:
import React from 'react';
import {render} from 'react-dom';
import ScrollArea from 'react-scrollbar';

render(<ScrollArea>
hello
</ScrollArea>, document.getElementById('app'));

When i was looking for solution i managed to make a scenario (in real app, with router.js) when i saw in ReactReconciler:

Unable to get property 'getNativeNode' of undefined or null reference.

But i forgot how exactly and cant provide info how to reproduce it anymore.
On above i've found
https://github.com/facebook/react/issues/6271,
https://github.com/facebook/react/issues/6246
may those be connected to this issue?
installed packages:
"dependencies": {
    "autoprefixer": "6.3.6",
    "babel-loader": "6.2.4",
    "babel-plugin-transform-decorators-legacy": "1.3.4",
    "babel-polyfill": "6.9.1",
    "babel-preset-es2015": "6.9.0",
    "babel-preset-react": "6.11.0",
    "babel-preset-stage-0": "6.5.0",
    "bundle-loader": "0.5.4",
    "classnames": "2.2.5",
    "css-loader": "0.23.1",
    "debug-levels": "0.2.0",
    "extract-text-webpack-plugin": "1.0.1",
    "file-loader": "0.9.0",
    "gen-uid": "0.0.2",
    "immutable": "3.8.1",
    "less": "2.7.1",
    "less-loader": "2.2.3",
    "lodash": "4.13.1",
    "moment": "2.13.0",
    "nuka-carousel": "2.0.2",
    "postcss-loader": "0.9.1",
    "pure-render-decorator": "1.1.1",
    "react": "15.1.0",
    "react-dom": "15.1.0",
    "react-dropzone": "3.5.1",
    "react-highcharts": "8.4.0",
    "react-intl-tel-input": "3.1.0",
    "react-lazyload": "2.1.3",
    "react-mixin": "3.0.5",
    "react-modal": "1.3.0",
    "react-notification-system": "0.2.7",
    "react-redux": "4.4.5",
    "react-router": "2.5.1",
    "react-scrollbar": "0.4.1",
    "react-select": "1.0.0-beta13",
    "react-tooltip": "3.0.7",
    "redux": "3.5.2",
    "redux-create-reducer": "1.1.1",
    "redux-logger": "2.6.1",
    "redux-thunk": "2.1.0",
    "sortablejs": "1.4.2",
    "style-loader": "0.13.1",
    "superagent": "2.0.0",
    "svg-inline-loader": "0.6.0",
    "svg-inline-react": "1.0.1",
    "url-loader": "0.5.7",
    "webpack": "2.1.0-beta.14",
    "why-did-you-update": "0.0.8"
  },
  "devDependencies": {
    "MD5": "1.3.0",
    "babel-cli": "6.10.1",
    "babel-eslint": "6.1.0",
    "babel-preset-react-hmre": "1.1.1",
    "babel-register": "6.9.0",
    "eslint": "2.13.1",
    "eslint-plugin-react": "5.2.2",
    "expect": "1.20.1",
    "glob": "7.0.5",
    "gulp": "3.9.1",
    "gulp-batch": "1.0.5",
    "gulp-clean": "0.3.2",
    "gulp-clean-css": "2.0.10",
    "gulp-concat": "2.6.0",
    "gulp-filter": "4.0.0",
    "gulp-if": "2.0.1",
    "gulp-less": "3.1.0",
    "gulp-mustache": "2.2.0",
    "gulp-plumber": "1.1.0",
    "gulp-rename": "1.2.2",
    "gulp-requirejs": "0.1.3",
    "gulp-rev": "7.1.0",
    "gulp-sourcemaps": "1.6.0",
    "gulp-svg-sprite": "1.3.1",
    "gulp-uglify": "1.5.4",
    "gulp-watch": "4.3.8",
    "isparta": "4.0.0",
    "istanbul": "0.4.4",
    "less-plugin-autoprefix": "1.5.1",
    "mocha": "2.5.3",
    "mock-local-storage": "1.0.2",
    "nock": "8.0.0",
    "react-addons-test-utils": "15.1.0",
    "react-styleguidist": "2.3.1",
    "redux-devtools": "3.3.1",
    "redux-devtools-dock-monitor": "1.1.1",
    "redux-devtools-filterable-log-monitor": "0.6.6",
    "redux-devtools-log-monitor": "1.0.11",
    "redux-mock-store": "1.1.1",
    "redux-slider-monitor": "1.0.6",
    "run-sequence": "1.2.1",
    "superagent-nock": "0.1.1",
    "through2": "2.0.1"
  },

webpack config:
module.exports = {

        entry: {
            app: APP_ENTRY,
            vendor: VENDOR_ENTRY
        },
        output: {
            path: BUILD_PATH,
            publicPath: PUBLIC_PATH,
            filename: '[name]-' + revision + '.js'
        },
        devtool: 'inline-source-map',
        module: {
            loaders: [{
                test: /bootstrap\.less$/,
                loader: ExtractTextPlugin.extract('style-loader', 'css?sourceMap!postcss!less?sourceMap'),
                exclude: /node_modules/
            }, {
                test: /\.less$/,
                loaders: ['style', 'css?sourceMap', 'postcss', 'less?sourceMap'],
                exclude: [/node_modules/, /bootstrap\.less$/]
            }, {
                test: /\.css$/,
                loaders: ['style', 'css?sourceMap', 'postcss'],
                exclude: /node_modules/
            }, {
                test: /\.jsx?$/,
                loaders: ['babel-loader'],
                plugins: ['transform-decorators-legacy'],
                exclude: /node_modules/
            }, {
                test: /\.svg$/,
                loaders: ['svg-inline'],
                exclude: /node_modules/
            }, {
                test: /\.(png|jpg|gif)$/,
                loaders: [
                    'url?limit=1000000'
                ]
            }, {
                test: /\.(woff|eot|ttf])$/,
                loader: 'url-loader',
                exclude: /node_modules/
            }]
        },
        postcss: function () {
            return [autoprefixer];
        },
        plugins: [
            new webpack.optimize.CommonsChunkPlugin({
                name: 'vendor'
            }),
            new ExtractTextPlugin('bootstrap-' + revision + '.css'),
            new webpack.EnvironmentPlugin([
                'NODE_ENV'
            ])
        ]
    };

Dont know what more useful info i could provide.

same here, @bulaj have you found any workaround for this issue?

nope, we moved to react-custom-scrollbars

Hi, thanks for notice that defect. I'll look at it :)

@souhe any progress on this issue? I think I'm being bitten by it too.

:(


Improve overall unit test performance

Our unit tests take way too long to run.  The top 25 longest running tests:
NewRelic::Agent::TransactionTest#test_generates_guid_when_running_out_of_file_descriptors = 21.27 s = .
NewRelic::Agent::PipeChannelManagerTest#test_listener_merges_sql_traces = 5.26 s = .
NewRelic::Agent::PipeChannelManagerTest#test_listener_merges_error_traces = 4.28 s = .
NewRelic::Agent::Transaction::SegmentTest#test_generates_guid_when_running_out_of_file_descriptors = 3.85 s = .
NewRelic::Agent::PipeChannelManagerTest#test_listener_merges_timeslice_metrics = 3.26 s = .
NewRelic::Agent::PipeChannelManagerTest#test_listener_merges_error_events = 3.26 s = .
NewRelic::Agent::PipeChannelManagerTest#test_listener_merges_transaction_traces = 3.25 s = .
LicenseTest#test_for_scary_license_terms = 3.07 s = .
NewRelic::Agent::AgentTest#test_exit_connecting_worker_thread = 3.06 s = .
NewRelic::MainAgentTest#test_shutdown_removes_server_config = 2.84 s = .
NewRelic::MainAgentTest#test_manual_start_kicks_dependency_check_again = 2.81 s = .
NewRelic::Agent::Agent::RequestBuilderTest#test_connect_settings_includes_labels_from_semicolon_separated_config = 2.11 s = .
NewRelic::Agent::Agent::RequestBuilderTest#test_connect_settings = 2.09 s = .
OrphanedConfigTest#test_all_default_source_config_keys_are_used_in_the_agent = 1.98 s = .
NewRelicServiceTest#test_json_marshaller_should_handle_crazy_strings = 1.95 s = .
NewRelic::Agent::UtilizationDataTest#test_full_hostname_omitted_if_empty_or_nil = 1.45 s = .
NewRelic::Agent::AgentTest#test_after_fork_should_not_start_agent_multiple_times = 1.30 s = .
NewRelic::Agent::Agent::RequestBuilderTest#test_enviroment_metadata = 1.11 s = .
NewRelic::Agent::UtilizationDataTest#test_aws_information_is_included_when_available = 0.91 s = .
NewRelic::Agent::UtilizationDataTest#test_pcf_information_is_omitted_when_available_but_disabled_by_config = 0.90 s = .
NewRelic::Agent::UtilizationDataTest#test_aws_and_docker_information_is_included_when_both_available = 0.88 s = .
NewRelic::Agent::UtilizationDataTest#test_configured_hostname_added_to_config_hash = 0.86 s = .
NewRelic::Agent::StatsEngineTest#test_record_scoped_and_unscoped_metrics_is_thread_safe = 0.85 s = .
NewRelic::Agent::UtilizationDataTest#test_boot_id_is_present_in_collector_hash = 0.85 s = .
NewRelic::Agent::UtilizationDataTest#test_docker_information_is_included_when_available = 0.85 s = .

These take 74.3 seconds to run.
The entire unit test suite takes 103.2 seconds to run.
Finished tests in 103.222255s, 31.6502 tests/s, 1470.2934 assertions/s

That means those 25 unit tests are responsible for 72% of total time spent in unit tests.
Let's fix this by targeting and improving the slowest tests and reducing total test runs by at least 30 seconds with a reduction of 45 and 60 seconds overall as a stretch goal.

The unit tests itself is quite efficient when compared to other tests in our collection.  We will create a new story to quantify the different types of test time and go from there.


add scc that forces ray pods to run as user 1000

Description
fixes: https://github.com/project-codeflare/codeflare-sdk/issues/129
How Has This Been Tested?
I tested this on my local cluster by explicitly creating the SCC, I will retest after completely removing kuberay
Merge criteria:

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

I ran this on our teams cluster with ODH and Codeflare and it successfully overcomes the issue pointed out in https://github.com/project-codeflare/codeflare-sdk/issues/129

Heh, I wanted to confirm the scc isn't a "bad" idea. @astefanutti can you also take a look at this tomorrow?

I can't think of any cons for using SCC.
It's not clear to me how that issue has something to do with the kuberay operator SA, rather than the SA that's used to run the Ray pods. From the referenced issues, it seems more related to the later than the former, which is the one added to the SCC.  That's probably my lack of the Kuberay internals, but I'd be curious to find out what I'm actually missing here.
Anyhow, it fixes the issue, and ideally, it'll be tackled in Ray eventually, so the images can run with any users.


Add Multipart

Pull Request Test Coverage Report for Build<PHONE_NUMBER>2
Details

11 of 20 (55.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.8%) to 90.779%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

config.go
11
20
55.0%

Totals

Change from base Build<PHONE_NUMBER>8:
-0.8%

Covered Lines:
827

Relevant Lines:
911

💛  - Coveralls

Nice! 🎉
Would it be possible to make it available as well as a method directly on *Builder if that makes sense? I imagined something like this, similar to the Body* methods:
requests.URL("https://example.com").
    BodyMultipart("", func(multi *multipart.Writer) error {
        // do something with multi
        return nil
    }).
    Fetch(ctx)

Do you think there's that much demand for it? OTOH, nesting the Config calls looks pretty ugly. Also unlike some of the other stuff I'm trying to move out to separate packages, this imports mime/multipart, which net/http also imports, so it's not introducing any import dependencies. 🤔

There's some weirdness around the random boundary. I think if you created a Builder and reused it, you would get the same "random" boundary every time until you make a new Builder. That's probably an okay limitation for a Config, but for a method I would expect it to work every time…

Do you think there's that much demand for it?

Probably not, seeing the activity about the topic in the discussion 😛.
My concern is mostly about discoverability, I wasn't aware of Config before your PR.
For this kind of "simple" HTTP usage, I'd be in favor of consistency in the API.

I think if you created a Builder and reused it, you would get the same "random" boundary every time until you make a new Builder.

Is it an issue? If the generated boundary is sufficiently random and is already OK for a single usage, I'm guessing that it can be safely reused. There's no requirement for it to change on every request as far as I'm aware of.

Hello! Any blocker here? Can I help releasing this? :)

This looks pretty good. I think it can be released as just a config for now and we can decide if it should be promoted to a method later. I want to change the example test to use a content type for en.txt, but other than that it looks good to go.


Generate coverage reports externally，no cargo binary

One scenario I have is a program written in rust that exposes the http interface and does not generate Python-related dependency packages via pyo3.
Invoke http interface directly by executing request through pytest;
Is it possible for me to get a coverage report for this integration test?
Trying the following method so far does not generate the relevant *.profraw
In simple terms, for example, rust program is a back-end, it has a front-end page, can I get the coverage of the relevant operations through the front-end operations
Set the environment variables needed to get coverage.
source < (cargo llvm-cov show-env --export-prefix)
Remove artifacts that may affect the coverage results.
This command should be called after show-env.
cargo llvm-cov clean --workspace
Above two commands should be called before build binaries.
cargo build # Build rust binaries.
Commands using binaries in target/debug/*, including cargo test and other cargo subcommands.
#...
cargo llvm-cov report --lcov # Generate report without tests.

Trying the following method so far does not generate the relevant *.profraw

cargo build # Build rust binaries.
# Commands using binaries in target/debug/*, including `cargo test` and other cargo subcommand.
#...

After you built the binaries, did you run them? If you have not run any, no profiles will be generated. If you run the binary, how exactly did you do it? (When using tools that do not propagate environment variables or parent directory structures, such as docker for example, environment variables must be propagated/mapped properly. See also https://github.com/taiki-e/cargo-llvm-cov/issues/319#issuecomment-1750813090)

Trying the following method so far does not generate the relevant *.profraw

cargo build # Build rust binaries.
# Commands using binaries in target/debug/*, including `cargo test` and other cargo subcommand.
#...

After you built the binaries, did you run them? If you have not run any, no profiles will be generated. If you run the binary, how exactly did you do it? (When using tools that do not propagate environment variables or parent directory structures, such as docker for example, environment variables must be propagated/mapped properly. See also #319 (comment))

My steps are as follows:

source through the environment variable generated in cargo llvm-cov show-env --export-prefix
The cargo llvm-cov clean --workspace is executed
cargo build --release --features tls Compile my side of the rust project
Run./target/release/xxx
Run pytest to execute the http request call
kill -9 Indicates related service processes
Run the cargo llvm-cov report --lcov

But there is no *.profraw file

kill -9 Indicates related service processes

AFAIK, SIGKILL is currently not supported. See https://github.com/taiki-e/cargo-llvm-cov/issues/235 for more.

Trying the following method so far does not generate the relevant *.profraw

cargo build # Build rust binaries.
# Commands using binaries in target/debug/*, including `cargo test` and other cargo subcommand.
#...

After you built the binaries, did you run them? If you have not run any, no profiles will be generated. If you run the binary, how exactly did you do it? (When using tools that do not propagate environment variables or parent directory structures, such as docker for example, environment variables must be propagated/mapped properly. See also #319 (comment))

I found a problem,
rust services run on physical machines
But I mount the working directory through docker and do the steps 1,2,3 above, and there is no cargo command on the physical machine.
Then I perform Step 4 on the physical machine.
Do environment variables need to be set on the physical machine to run the program? Whether the environment variable set here is the same as the docker internal, using a relative path, or the external physical machine absolute path address

kill -9 Indicates related service processes

AFAIK, SIGKILL is currently not supported. See #235 for more.

*.profraw file

Is the *.profraw file generated when I run pytest (while the rust program is still working), and how do I trigger the *.profraw file

Do environment variables need to be set on the physical machine to run the program? Whether the environment variable set here is the same as the docker internal, using a relative path, or the external physical machine absolute path address

set-env currently sets the following environment variables:
export RUSTFLAGS='-C instrument-coverage --cfg=coverage --cfg=trybuild_no_target'
export LLVM_PROFILE_FILE='/path/to/target/name-%p-%10m.profraw'
export CARGO_LLVM_COV=1
export CARGO_LLVM_COV_SHOW_ENV=1
export CARGO_LLVM_COV_TARGET_DIR=/path/to/target

The environment variables actually used in each step are different.

cargo build requires RUSTFLAGS.
Binaries require LLVM_PROFILE_FILE.
cargo llvm-cov report and cargo llvm-cov clean require CARGO_LLVM_COV_TARGET_DIR.

When using docker or other, absolute paths may need to be mapped to point to the same directory. (LLVM_PROFILE_FILE or/and CARGO_LLVM_COV_TARGET_DIR, depending on the situation)

Is the *.profraw file generated when I run pytest (while the rust program is still working), and how do I trigger the *.profraw file

IIRC, rust binary (or cdylib) will generate *.profraw file on exit.
The LLVM documentation says there is a way to generate file on a regular basis, but it didn't work when I tried it before. (https://github.com/taiki-e/cargo-llvm-cov/pull/280)

Do environment variables need to be set on the physical machine to run the program? Whether the environment variable set here is the same as the docker internal, using a relative path, or the external physical machine absolute path address

set-env currently sets the following environment variables:
export RUSTFLAGS='-C instrument-coverage --cfg=coverage --cfg=trybuild_no_target'
export LLVM_PROFILE_FILE='/path/to/target/name-%p-%10m.profraw'
export CARGO_LLVM_COV=1
export CARGO_LLVM_COV_SHOW_ENV=1
export CARGO_LLVM_COV_TARGET_DIR=/path/to/target

The environment variables actually used in each step are different.

cargo build requires RUSTFLAGS.
Binaries require LLVM_PROFILE_FILE.
cargo llvm-cov report and cargo llvm-cov clean require CARGO_LLVM_COV_TARGET_DIR.

When using docker or other, absolute paths may need to be mapped to point to the same directory. (LLVM_PROFILE_FILE or/and CARGO_LLVM_COV_TARGET_DIR, depending on the situation)

Is the *.profraw file generated when I run pytest (while the rust program is still working), and how do I trigger the *.profraw file

IIRC, rust binary (or cdylib) will generate *.profraw file on exit. The LLVM documentation says there is a way to generate file on a regular basis, but it didn't work when I tried it before. (#280)

I tried using LLVM_PROFILE_FILE, but it didn't work.
If I inject so file at compile time, this so file is mainly used to listen to semaphore, can I generate *.profraw file, which method can I trigger internally to generate?

I have hit a similar issue, in this CI run.
As can be seen there, cargo llvm-cov show-env sets LLVM_PROFILE_FILE to '/home/runner/work/nearcore/nearcore/target/nearcore-%p-%16m.profraw'. Yet cargo llvm-cov report is searching in another folder:
warning: not found *.profraw files in /home/runner/work/nearcore/nearcore/target/llvm-cov-target

I think this might be a bug in show-env, and I tried solving it by adding this line to CI, after the show-env:
      - run: echo "LLVM_PROFILE_FILE=$(pwd)/target/llvm-cov-target/nearcore-%p-%16m.profraw" >> "$GITHUB_ENV"

However, this resulted in this other failing CI job, where the profraw was still not detected.
I then tried to add back the clean step, that I was trying to avoid in order to avoid spending tens of minutes of CI time rebuilding dependencies all the time. It still failed, and find found no *.profraw files.
The workflow I’m currently trying to get to work is the following:
https://github.com/near/nearcore/pull/10180/files#diff-b803fcb7f17ed9235f1e5cb1fcd2f5d3b2838429d4368ae4c57ce4436577f03fR79-R102
Do you have any idea what I’m doing wrong? AFAICT with the last iteration, I’m basically only trying to get the cargo llvm-cov show-env-based example to work, without anything too specific to our setup.

@Ekleog-NEAR One of the problems is that you are passing the output of --export-prefix to GITHUB_ENV; -export-prefix adds a prefix for the UNIX shell, which is not the format GITHUB_ENV expects.
One of the ways is to save the output of --export-prefix to a file and source it, as in https://github.com/nextest-rs/nextest/issues/1036.

 Thank you for the solution! I ended up with this code for setting the environment in a github action. Would you be interested in a PR that showcases the more "advanced" (multiple codecov labels, using with python tests that call into rust, etc.) use cases of cargo-llvm-cov in the readme?
Also I’m curious, does llvm-cov actually need the whole target folder, or would it be possible to trim it somehow, to be able to share build artifacts across jobs without having to share the whole target folder? And if it’s possible (and significantly reduces the size of the target folder), would you be interested in a subcommand that cleans target to just leave the necessary stuff?
Also, just to say, I had parsed --export-prefix as "also export the prefix, like the target/ directory", resulting in this mistake. Maybe on the next major upgrade of cargo-llvm-cov, you could consider renaming it into --with-export-prefix, that does not have this potential for mis-parsing? (I’d totally understand if the churn would be too big, it’s just an idea)

Would you be interested in a PR that showcases the more "advanced" (multiple codecov labels, using with python tests that call into rust, etc.) use cases of cargo-llvm-cov in the readme?

A PR to add an example is welcome!

Also I’m curious, does llvm-cov actually need the whole target folder, or would it be possible to trim it somehow, to be able to share build artifacts across jobs without having to share the whole target folder? And if it’s possible (and significantly reduces the size of the target folder), would you be interested in a subcommand that cleans target to just leave the necessary stuff?

Only the binaries and profraw are actually needed to generate the report.
I think it would be okay to add a subcommand that copies some of the files that clean_partial deletes instead of deleting and outputs to a specified directory and an option to get the needed files from the directory containing the output of that command instead of the target directory.

Also, just to say, I had parsed --export-prefix as "also export the prefix, like the target/ directory", resulting in this mistake. Maybe on the next major upgrade of cargo-llvm-cov, you could consider renaming it into --with-export-prefix, that does not have this potential for mis-parsing? (I’d totally understand if the churn would be too big, it’s just an idea)

I have no strong opinion on the naming. That said, it may indeed be clearer to clarify that "export" is a noun, not a verb.


Create Procfile

Pull Request Test Coverage Report for Build 949658971

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.0%

Totals

Change from base Build 949598678:
0.0%

Covered Lines:
49

Relevant Lines:
50

💛  - Coveralls


Request: AL class for Newtonsoft.Json.JsonTextWriter

We use the JsonTextWriter to build web requests as opposed to building and adding json objects and would like to request an AL class equivelant
Example of use:
System.Text.StringBuilder
System.IO.StringWriter
Newtonsoft.Json.JsonTextWriter

StringBuilder := StringBuilder.StringBuilder();
StringWriter := StringWriter.StringWriter(StringBuilder);
JsonTextWriter := JsonTextWriter.JsonTextWriter(StringWriter);
JsonTextWriter.WriteStartObject();
JsonTextWriter.WritePropertyName('name',false);
JsonTextWriter.WriteValue(0);
JsonTextWriter.WriteStartObject();
JsonTextWriter.WritePropertyName('name2',false);
JsonTextWriter.WriteValue(0);
JsonTextWriter.WriteEndObject();
JsonTextWriter.WriteEndObject();
RequestBody = StringBuilder.ToString();

to something like
JsonTextWriter

JsonTextWriter := JsonTextWriter.Create();
JsonTextWriter.WriteStartObject();
JsonTextWriter.WritePropertyName('name',false);
JsonTextWriter.WriteValue(0);
JsonTextWriter.WriteStartObject();
JsonTextWriter.WritePropertyName('name2',false);
JsonTextWriter.WriteValue(0);
JsonTextWriter.WriteEndObject();
JsonTextWriter.WriteEndObject();
RequestBody =JsonTextWriter.ContentsAsText();

Can we have this issue get more attention?   The lack of this ability (that was available in C/AL via .net ) means that JSON generation will be limited to Dom-style creation, which provides no predictability or guarantee on ordering of DOM elements.     This is a problem.
On the performance side the lack of this ability also means that JSON generation will be slower, as we cannot use the much speedier approach of just using a JSON writer.
Not having basic writers and readers for streams for JSON and XML seems to go counter to the apparent goals of pushing vendor integrations towards cloud based micro services.
We are converting from a v1 to v2 extension that used JSON and XML heavily to communicate with a cloud based micro-service, and the lack of these basic tools is making our conversion process much more cumbersome than it needs to be.
We have other apps in our backlog that also depend on JSON and XML communication with other services.   At minimum we need visibility into whether this has been categorized as a "won't do" so that we can identify if we need to make workarounds.

Would this address your needs?
https://github.com/Microsoft/cal-open-library/pull/35
Feel free to comment directly on that pull request if there is anything more that the author could add to meet your scenario.

That would assist, thanks! I will comment there with more detail.

Hi! This issue is beyond the scope of the AL language and development tools. Please go ahead and post this to our Ideas forum at https://aka.ms/BusinessCentralideas, or vote up the idea if its already there. We're constantly monitoring top Ideas and will consider them for a future release.


Remove old server KB

@brandysmith Please fix broken links

@jim-phillips I fixed links, all checks have passed. Please merge.


Is this project still alive?

It would be good to know if this project is still alive, if it may see bug fixes or if pull requests would get accepted.

@alxgb since there was no activity or response, I plan to create a copy of this repository (with the original license and commit history intact) to simplify future updates and community contributions. Let me know if you are not OK with this.

I have now created https://github.com/OFAI/sip-parser2 for this purpose

Hi, that's totally fine - I don't have much time to dedicate to this (or aligns with any current projects either), more than OK with a fork!

Thank you!

Hi, that's totally fine - I don't have much time to dedicate to this (or aligns with any current projects either), more than OK with a fork!

Hi! Can you please add notification in README for new users?


Changing the input streamer or file path to ros2 node publisher

Hey all, and thank you for this incredible project!
I would like to know what are the changes that need to be done in order to convert the input of the node from camera/mp4 file path to a topic of a node that publisher bag file of frames.
which class should be changed or what kind of topic should I use? or other modifications I should take in consider.
best regrades,
AK

Abbreviation of the question above, what should i change in the deepstream pipeline flow, in order to replace the input stream with a ros topic subscriber which receives frame by frame images (using Image msg converted by cv2 in python
cv_image = self.bridge.imgmsg_to_cv2(msg)

Hi! This project currently supports video input through webcam/file.
Converting ROS to OpenCV images will not give you the latency optimizations that the underlying DeepStream pipeline provides. Could you please tell us what you want to achieve using CvBridge?
If interested in accessing image data, you could try using deepstream-imagedata-multistream.
You could also try using RTSP input with your DeepStream application; refer to deepstream-rtsp-in-rtsp-out.

Thanks @AsawareeBhide for your response!

Short overview, the system image analysis process, is inside ros2 node and receives frames by DDS messages, that sent from a mDVR component, than using self.bridge.imgmsg_to_cv2(msg) the image topic is converted to cv2 and continue to YOLO NN for inference.
I wish to replace the analytic process with the deepstream pipeline.
In order to support the existing flow (using messages), I wrapped the Deepstream with ROS2 subscriber (with this project).
But didnt find a plugin that supports the receives or transformation from ROS\DDS topics to some thing that supported by deepstream input.

So what should be a good practice to convert DDS/ROS messages to a deepstream input?

Hey there,
Still intrigued to find a solution to this problem, so I really appreciate any feedback/ help.

Any approach? Very interesting to move some ai to models to ROS using real-time cameras on board robot


Update README.md

update docker compose

Docker compose isn't docker, and we can't take on the whole ecosystem here :-/


Docker compose files for CI

@swift-server-bot test this please

@swift-server-bot test this please

Is there anything that can be done to move this forward?


Client: Have polkadot-api handle changes in runtime code more smoothly

This seems to be mostly handled by recent API-calls-into-runtime changes. Reopen (and properly describe) if otherwise.


HDDS-2923 Add fall-back protection for rack awareness in pipeline creation.

What changes were proposed in this pull request?
#HDDS-2923 Add fall-back protection for rack awareness in pipeline creation.
(Please fill in changes proposed in this fix)
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-2923
(Please create an issue in ASF JIRA before opening a pull request,
and you need to set the title of the pull request which starts with
the corresponding JIRA issue number. (e.g. HDDS-XXXX. Fix a typo in YYY.)
Please replace this section with the link to the Apache JIRA)
How was this patch tested?
UT. Test in actual env.
(Please explain how this patch was tested. Ex: unit tests, manual tests)
(If this patch involves UI changes, please attach a screen-shot; otherwise, remove this)

Acceptance test failed due to:
ERROR: Test execution of /home/runner/work/hadoop-ozone/hadoop-ozone/hadoop-ozone/dist/target/ozone-0.5.0-SNAPSHtOT/compose/ozonesecure is FAILED!!!!
Doesn't seem to be related to this change. @xiaoyuyao Do you have any ideas on the ozonesecure test failure? Thanks.

+1


Update of LumenX logo

Already have another PR ready, https://github.com/osmosis-labs/osmosis-frontend/pull/1449; pending further discussion on image selection.


add 'spark_session' as alias for 'hive_context' (Spark 2.0.0)

With Spark 2.0.0, the Spark session / SQL context / hive context have all been amalgamated into a single object. Right now, hive_context() returns that:
> hive_context(sc)
<jobj[8]>
  class org.apache.spark.sql.SparkSession
  org.apache.spark.sql.SparkSession@65b602ec

But we should be able to access this with a plain spark_session(sc) call.

Definitely! If we do this then we should also check for spark_version >= 2.0 and throw a nice error if it isn't a version that supports SparkSession


Reduce load time for Pinot UI Home Page

In the Pinot UI home page currently the following is the behaviour:
Redundant calls
Multiple /instances calls, 2 for each component type (total 4*2=8) although one call should provide information for all
Multiple /zk/ls?path=%2Fpinot%2FLIVEINSTANCES calls, 1 each component type (total 4) although one call should provide information for all.
We can try to reduce these redundant calls:
Reuse the response from /instances to display instance counts and instance info tabs
Reuse the response from /zk/ls?path=%2Fpinot%2FLIVEINSTANCES to display instance status in instance info tabs.
Left over task from : https://github.com/apache/pinot/issues/13278

@deepthi912 is it just on the homepage or do we have to address redundant api calls from other pages in the UI as well

Not necessarily with Home page, if there are redundant calls from these apis made in other pages, we can change that as well. Does that answer the question?

okay, will try to check each page and raise pr one page at a time. Starting with home page.

@jayeshchoudhary Does #14295 resolve this issue completely? Or are you going to make more improvements?

I think this issue can be closed now.


Bump submariner version

For example, I see the actual Submariner version is unchanged.

github.com/submariner-io/submariner v0.13.0-m2

yeah that's weird - not sure what happened there. I updated it.


Add support for local functions

is there any support like switch status for local functions ?

Grab the new release! 🚀


@ashfurrow => [Analytics] Add back page view event for Search and add Bell.

Fixes #674.
Is the event name ‘Bell’ good or should it be ‘Notifications’ or ‘Works For You’?
/cc @alexanderfabry

Looks good!


Rename 'LDTSI' da observation in LIS configuration to 'USAFSI'

For this, please change the below lines in 'lis.config' for USAF-SI DA
Data assimilation set:                               "LDTSI"   ->
Data assimilation set:                               "USAFSI"
LDTSI data directory:       ->
USAFSI data directory:
If the USAFSI file output will be needed to change from "ldtsi_yyyymmddhh.nc" to "usafsi_yyyymmddhh.nc", further changes are required in LIS, as well as LVT.

Can you update the lis/configs/lis.config.adoc file to reflect these changes?

Hi Yeosang:
Friendly reminder:  Please update the lis.config.adoc file.  Thanks.

I add an option to the lis.config to specify the USAFSI DA observation name, similar to #430.
Also, update the lis.config.adoc file.

@yyoon4 I pushed code updates to your branch.  These changes replace 'LDTSI' with 'USAFSI', and also changes the lis.config setting for the USAFSI prefix to:
USAFSI netcdf filename prefix:
This also updates the documentation.

NOTE:  A separate pull request exists for the restricted-lisf-jules repository to handle analogous changes to the JULES DA system.


X pixel group master

merged

merged from XPixelGroup-master

sorry, ignore this.. wanted to add to my repository, accidentally added it here


404 page

@AbdoKousara I'm going to remove this PR. Could you make it again but use a clone of this project instead of a fork in your personal account?


add data-cy for mesh adapter url element

Notes for Reviewers
This PR fixes #7623
Signed commits

[x] Yes, I signed my commits.

Close, but no cigar?

@MarioArriaga92 👀 https://github.com/meshery/meshery/actions/runs/4888341259/jobs/8725962396?pr=7657#step:5:158

Oh sorry @Chadha93 I thought it was evident that failing tests are unrelated to the one I fixed as part of this PR

I'll take a look at the failing tests

I'll take a look at the failing tests

Thank you

Merged these changes along with #7658, which is WIP and we're aiming it to include fixes for all tests. So far we've identified several intermittent problems which we're hoping are not an issue any more after adding some cypress configs to give a bit more time to request responses and UI elements to render, when needed.


Error Code 2201

While Registering for a Microsoft Partner Center Account I filled out all information required. When I click "next" I receive Error code 2201. Correlation ID [90cd6f76-aeba-424f-9703-4ca05a9821c5,C6jNu8ZEWkeFbrmv.0.0.]

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

ID: fc9d4d96-2865-5f2d-8737-66fe44db7cce
Version Independent ID: 239560a3-7506-bb73-b436-6eec162e5196
Content: Account types, locations, and fees - UWP applications
Content Source: windows-apps-src/publish/account-types-locations-and-fees.md
Product: uwp
Technology: publish
GitHub Login: @hickeys
Microsoft Alias: hickeys

This feels not so much like feedback specifically about the documentation, but rather like a support request. Here are all of the developer support resources, for completeness.

Microsoft Q&A offers relevant and timely answers to your technical problems from a community of experts and Microsoft engineers.
For community assistance with development questions, there are our forums, and StackOverflow.
The Windows developer support site explains other support options.
The Visual Studio developer community is available, and responsive. The former User Voice feature is now there on the Suggest a feature tab, if you want to lobby for a change, a feature, or to make a suggestion.
For developer issues, or suspected product bugs, there's Microsoft Support; a support engineer will look at the repro and see whether the issue is a Microsoft product bug, or something else. If it's a bug with a Microsoft product then the ticket will be free of charge.

If you receive assistance via any of these support resources, and you believe that information would help us improve the docs, then please come back and let us know.


.interactive dataframe repr: table columns overlap

ALL software version info
hvplot                : 0.8.0
pandas                : 1.4.3
holoviews             : 1.14.9
bokeh                 : 2.4.3

Python version        : 3.9.13
IPython version       : 8.4.0
jupyter notebook      : 6.4.12
jupyterlab            : 3.4.3

OS                    : Darwin ( = MacOS 11.5.2)
Release               : 20.6.0
Browser               : Safari

Description of expected behavior and the observed behavior
The columns of the dataframe representation in both jupyter notebook and jupyter lab are too narrow, so numbers overlap for a particular example dataframe.
Complete, minimal, self-contained example code that reproduces the issue
import hvplot.pandas
from bokeh.sampledata import airports

df = airports.data
df1 = df.interactive()
df1    # show dataframe

Performing a dynamic calculation on the dataframe doesn't change that behavior
p = pnw.IntSlider(start=0, end=100)
df1[df1.index<p]   # dataframe still squished

Stack traceback and/or browser JavaScript console output
No error message in jupyter notebook / lab.
Ne error / warning in javascript console.
Screenshots or screencasts of the bug in action

Expected behavior

I see there is a height parameter also. Would be nice if that would go in the docstring of .interactive().

@maximlt Seems to be solved now. So close it? An informative docstring was also added to .interactive, though height is not mentioned as a parameter, but width at least.


Add authorize method

@pgom could you please provide a description?

What is left for this to be merged?

+1 for this.

+1 as well, what is left to be changed here for this to get merged?

@pgom Let's rebase this?


Update paragraph about Google sunsetting Google Enhanced Conversion L…

Proposed changes
-- Updated paragraph to let customers know the Google Enhanced Conversion Legacy API is sunsetting June 30th, 2024

Communication that was sent out to customers:
We are contacting you about an update that will affect your Google Ads Conversion destination. Please continue reading to learn what action will be required in your Segment workspace.
Google's Enhanced Conversion Legacy API is scheduled to EOL June 30th 2024. Google will no longer let data flow and will no longer maintain the API.


Import bundled ujson

Theorically ujson is a bundled library like ammonite-ops.
From the REPL I can do this:
import ujson.Js

but from a script I can't.
ammonite-ops, can be used both from a script and from the REPL, withouth doing import $ivy.
The same can be said with:
import scalaj.http._

Why ujson doesn't work?
I'd like to run the same source file from Ammonite and SBT, so I'd like to avoid import $ivy constructs.

No idea, seems to work for me
$ amm
Loading...
Welcome to the Ammonite Repl 1.1.2
(Scala 2.12.6 Java 10.0.1)
If you like Ammonite, please support our development at www.patreon.com/lihaoyi
@ Bye!

$ amm foo.sc
ujson.Js$@72eed547

$ cat foo.sc
import ujson.Js
println(Js)


Subnets: Update docusaurus config to point to master

Change the lines of code related to Subnets to point to master instead of develop.
Example: This link  https://raw.githubusercontent.com/hirosystems/stacks-subnets/develop/docs/feature-guides/ will change to https://raw.githubusercontent.com/hirosystems/stacks-subnets/master/docs/feature-guides/

This is invalid; not required.


llm中data中数据名称错误，对应的ee抽取数据处理部分代码报错

Describe the bug

A clear and concise description of what the bug is.

Environment (please complete the following information):

OS: [e.g. mac / window]
Python Version [e.g. 3.6]

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.

您好请问您的错误解决了吗


Add vertical progress bar

Add vertical progress bar according to https://lightningdesignsystem.com/components/progress-bar/#Vertical

I will take this up

What do you think about this for the prop:
variant: base | vertical

I can add an initial PR for the same.

Looks like there is already progress-indicator with orientation: 'horizontal' | 'vertical'.  Let's just use that to be consistent.


"nslookup -type=" fails or times out

wsl-vpnkit is working great for me for everything except kerberos right now.
Seems like kerberos relies on the SRV record rather than the normal A record, and kerberos within WSL isn't able to find the kerberos admin servers when connected to the VPN.
I tried using nslookup to investigate this behavior, and here's what I saw:
[16:04:37] $ nslookup www.google.com
Server:         <IP_ADDRESS>
Address:        <IP_ADDRESS>#53

Non-authoritative answer:
Name:   www.google.com
Address: <IP_ADDRESS>
Name:   www.google.com
Address: <IP_ADDRESS>
Name:   www.google.com
Address: <IP_ADDRESS>
Name:   www.google.com
Address: <IP_ADDRESS>
Name:   www.google.com
Address: <IP_ADDRESS>
Name:   www.google.com
Address: <IP_ADDRESS>

[16:04:48] $ nslookup -type=AAAA www.google.com
Server:         <IP_ADDRESS>
Address:        <IP_ADDRESS>#53

Non-authoritative answer:
*** Can't find www.google.com: No answer

[16:04:56] $ nslookup -type=any www.google.com
;; Connection to <IP_ADDRESS>#53(<IP_ADDRESS>) for www.google.com failed: timed out.
;; Connection to <IP_ADDRESS>#53(<IP_ADDRESS>) for www.google.com failed: timed out.
;; connection timed out; no servers could be reached

;; Connection to <IP_ADDRESS>#53(<IP_ADDRESS>) for www.google.com failed: timed out.

[16:05:35] $ nslookup -type=TXT www.google.com
Server:         <IP_ADDRESS>
Address:        <IP_ADDRESS>#53

Non-authoritative answer:
*** Can't find www.google.com: No answer

Authoritative answers can be found from:

I've followed the instructions to install wsl-vpnkit as a systemd service, and just about everything else is working.
Let me know if there's more information I can provide.

@kevelairn The DNS proxy server in gvisor-tap-vsock only supports limited query types (namely, A). You can setup your own DNS configuration in /etc/resolv.conf and point that to your internal DNS servers directly.


Improve the ReflectionProbe class documentation

master version of https://github.com/godotengine/godot/pull/55832.
This also documents Viewport's lod_threshold property as it's also present in ReflectionProbe.
This closes https://github.com/godotengine/godot/issues/55800.

Thank you!


Uncertainty merge

Merged climate_uncertainty repo which had CRPS, MC dropout, and parametric prediction implementations. Requires download of constants. For example,
download(root = "/content/drive/MyDrive/Climate/.climate_tutorial", source = "weatherbench", variable = "constants", dataset = "era5", resolution = "5.625")

Colab proof that this branch works: https://colab.research.google.com/drive/1Eb0pnpyhMxmNmtf7p_eXyG5Fl37wmtvU?usp=sharing.
Also, the call to visualize in the last code cell failed, but I suspect that it would have also failed in the original notebook since it is neither imported from the package nor defined in the notebook.

Do we really need mcdropout as an argument to the forward function? If not, then can we make it a member of the class instead? Something like self.mcdropout
OK. That sounds good to me. I'll make that change.

In resnet.py, do we need the commented part at the end of the script?
No, I can delete this.


feat(ux/#2496): Configurable statusbar

Adds a fully configurable status bar from the configuration file

<breaking>Fully configurable status bar</breaking>

Based on the ideas from @z0al #3402 there is some work that needs to be done on this branch:
:ballot_box_with_check: Change from start/end right/left
:ballot_box_with_check: Make ... move all to one side
:ballot_box_with_check: Make ... move all the extensions to their side based if ... is on both sides or not
:ballot_box_with_check: Make Hidden
:ballot_box_with_check: Add a notificationMode or make showInNotificaion work as notificationMode if it's a string
:ballot_box_with_check: Make notificaionPopup with fixed size for compact
There are some changes differences from @z0al proposed, I left the rightItems and leftItems If you want to move the all the left or right extensions items to a different position, but all the other "rules" still apply.
I also made, so you could use the command and the id for selection extensions items.
The compact mode for notifications is now 2 possible options compact and compact+ where compact lets notifications "stack up" on the bar and compact+ does not (we could probably find better names for this).

What do you think? @z0al @bryphe
Sorry for the long GIF

I left the rightItems and leftItems If you want to move the all the left or right extensions items to a different position

I'm confused. I don't understand why leftItems and rightItems would be relevant anymore given the introduction of the ... notation. Maybe you can share an example for the use case you have in mind?
Previously (or currently, in the main branch), leftItems and rightItems are based on the extension alignment config. We will still respect that if the user provided an expansion slot (a.k.a ... notation) in both items.left/right configuration.
However, with the ... syntax, the user can overwrite the default alignment (set by the extension) to something else. e.g.
{
  "workbench.statusBar.items": {
    "left": ["modeIndicator"],
    "right": ["...", "notificationCount"],
  }
}

In the above configuration, I'm basically overwriting all items that there previously known as leftItems to be right-aligned.
Now if we keep the leftItem/rightItems what would that mean for the logic of ...? Taking this configuration as an example.
{
  "workbench.statusBar.items": {
    "left": ["modeIndicator", "rightItems"],
    "right": ["...", "leftItems", "notificationCount"],
  }
}

That doesn't seem to be predictable or deterministic anymore to me. The ... and leftItems/rightItems will be conflicting with each other and making the configuration a bit vague.

The compact mode for notifications is now 2 possible options compact and compact+ where compact lets notifications "stack up" on the bar and compact+ does not (we could probably find better names for this).

It's not about the naming for me. I don't see the benefit of the compact+ mode. There is a very limited space on the status bar and showing multiple messages next to each other horizontally doesn't seem like a good idea to me.
The purpose of the notification popup is to give visual feedback that there is something that may need my attention. Having the last message in the status bar is more than enough to achieve that. That being said you might have noticed that the notification pop contains duplicated information by design. If I want to see any message in details there is a notification panel for that. In fact, the messages are most likely to be duplicated in the editor too as errors/warnings or hints in a specific line if possible.
But in any case, we can always add it in future if see a need. The current configurations set is flexible enough to support different modes in future.

I also made, so you could use the command and the id for selection extensions items.

I've no clue if this is a good idea or not tbh 🤷🏻♂

On a different note, I think it's a good idea to start explicitly assigning priority and alignment attributes to the built-in/hardcoded items e.g.
let modeIndicator = {
  id: "mode",
  alignment: RIGHT,
  priority: 1 // I don't know
}

let notificationCount = {
  id: "notificationCount",
  alignment: LEFT,
  priority: 1 // I don't know
}

This should avoid accidentally changing the priority or alignment of these items between releases.

I might have confused the difference between compact and compact+ . What I wrote above is about the one that adds multiple notification message to the status bar. The compact mode I have mind doesn't.

Thanks for the impressive work on this, @andr3h3nriqu3s11 !
I had a lot of fun playing with it - like, putting mode indicators on both sides of my status bar 😎
I noticed a bug with the notifications - it seems like the background color isn't being transitioned for the status bar items that are 'pinned' to the notification - like:

More noticeable with more items pinned:

The sort of 'gap' in the pinned items where the color isn't transitioning seems a bit jarring / confusing - it does make more sense in the 'compact' mode where it just the smaller notification is animating. In 'default' mode - I wonder if we could preserve the existing color transition behavior?

💯


Use Async API to upload segment

Change uploading segment API to be async because it's might take long time and block other calls
Fix the issue where we fetch ideal state twice before adding new segment
Fix the thread-safety issure for segmentAssignmentStrategyMap
Explicitly handle ZkBadVersionException

Codecov Report

Merging #2490 into master will increase coverage by 0.03%.
The diff coverage is 57.5%.

@@            Coverage Diff             @@
##           master    #2490      +/-   ##
==========================================
+ Coverage    69.4%   69.43%   +0.03%
==========================================
  Files         848      848
  Lines       39550    39545       -5
  Branches     5329     5328       -1
==========================================
+ Hits        27448    27460      +12
+ Misses      10310    10296      -14
+ Partials     1792     1789       -3

Impacted Files
Coverage Δ

...ntroller/helix/core/PinotHelixResourceManager.java
63.12% <100%> (-0.1%)
:arrow_down:

...i/resources/PinotSegmentUploadRestletResource.java
55.7% <25%> (-1.12%)
:arrow_down:

...linkedin/pinot/common/utils/helix/HelixHelper.java
49.31% <52.17%> (-3.67%)
:arrow_down:

...a/manager/realtime/RealtimeSegmentDataManager.java
50% <0%> (-50%)
:arrow_down:

...in/pinot/core/query/pruner/ValidSegmentPruner.java
57.14% <0%> (-28.58%)
:arrow_down:

.../impl/dictionary/FloatOnHeapMutableDictionary.java
80% <0%> (-13.34%)
:arrow_down:

.../impl/dictionary/LongOffHeapMutableDictionary.java
81.81% <0%> (-5.46%)
:arrow_down:

...not/core/query/pruner/DataSchemaSegmentPruner.java
53.65% <0%> (-4.88%)
:arrow_down:

...impl/dictionary/DoubleOnHeapMutableDictionary.java
68.88% <0%> (-4.45%)
:arrow_down:

...e/operator/dociditerators/SortedDocIdIterator.java
61.11% <0%> (-2.78%)
:arrow_down:

... and 14 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fe6e083...54f9de5. Read the comment docs.


Does dalex does not support for regression, Using fairness mitigation but not working. Also while fairness check biased data also showing not biased detected.

Comment:
No response

fairness supports only classification


Build of Hello World Failed on Darwin (MacOS)

$ bazel build -c opt mediapipe/examples/desktop/hello_world:hello_world
Starting local Bazel server and connecting to it...
DEBUG: Rule 'build_bazel_rules_apple' indicated that a canonical reproducible form can be obtained by modifying arguments commit = "6c9fcae7a3597aabd43f28be89466afe0eab18de", shallow_since = "1565379803 -0700" and dropping ["tag"]
DEBUG: Call stack for the definition of repository 'build_bazel_rules_apple' which is a git_repository (rule definition at /private/var/tmp/_bazel_faucherd/3a6923036fc899f82029b0fb9d70b802/external/bazel_tools/tools/build_defs/repo/git.bzl:181:18):

/Users/faucherd/Documents/Personal/Machine_Learning/Google/mediapipe/WORKSPACE:251:1
ERROR: /private/var/tmp/_bazel_faucherd/3a6923036fc899f82029b0fb9d70b802/external/local_config_cc/BUILD:46:1: in cc_toolchain_suite rule @local_config_cc//:toolchain: cc_toolchain_suite '@local_config_cc//:toolchain' does not contain a toolchain for cpu 'darwin_x86_64'
ERROR: Analysis of target '//mediapipe/examples/desktop/hello_world:hello_world' failed; build aborted: Analysis of target '@local_config_cc//:toolchain' failed; build aborted
INFO: Elapsed time: 58.077s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (53 packages loaded, 1164 targets configured)

The error could mean that Bazel can't find an appropriate c++ compiler on your mac.
Did you install Xcode in your /Applications folder (that's where Bazel will look for it), and are the the Xcode command line tools also installed?
Please see the "Installing on macOS" section in install.md for more details.
If you still have the issue, let me know the version number of the OS, Bazel, XCode you have.

Thank you @jiuqiant. I did not have Xcode installed. I installed Xcode and got closer but still received a (different) error.
$ bazel run --verbose_failures --define MEDIAPIPE_DISABLE_GPU=1     mediapipe/examples/desktop/hello_world:hello_world
DEBUG: Rule 'build_bazel_rules_apple' indicated that a canonical reproducible form can be obtained by modifying arguments commit = "6c9fcae7a3597aabd43f28be89466afe0eab18de", shallow_since = "1565379803 -0700" and dropping ["tag"]
DEBUG: Call stack for the definition of repository 'build_bazel_rules_apple' which is a git_repository (rule definition at /private/var/tmp/_bazel_faucherd/3a6923036fc899f82029b0fb9d70b802/external/bazel_tools/tools/build_defs/repo/git.bzl:181:18):

/Users/faucherd/Documents/Personal/Machine_Learning/Google/mediapipe/WORKSPACE:251:1
INFO: Analyzed target //mediapipe/examples/desktop/hello_world:hello_world (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
ERROR: /private/var/tmp/_bazel_faucherd/3a6923036fc899f82029b0fb9d70b802/external/zlib_archive/BUILD.bazel:5:1: undeclared inclusion(s) in rule '@zlib_archive//:zlib':
this rule is missing dependency declarations for the following files included by 'external/zlib_archive/uncompr.c':

I am wondering if you need to uninstall and install bazel again after your get Xcode and its command line tools. Also, please do bazel clean --expunge to make sure you have a clean start.
It seems like the error message is truncated, I would like to see more error message if possible.  Moreover, can you report the version number of your OS, Bazel, clang, and XCode?
Here are some links that may help:

https://stackoverflow.com/questions/43230143/tensorflow-build-issue-with-bazel#comment73708719_43230143
https://github.com/bazelbuild/bazel/issues/9213

Thank you again @jiuqiant. --expunge did the trick
Target //mediapipe/examples/desktop/hello_world:hello_world up-to-date:
bazel-bin/mediapipe/examples/desktop/hello_world/hello_world
INFO: Elapsed time: 212.890s, Critical Path: 149.52s
INFO: 539 processes: 539 darwin-sandbox.
INFO: Build completed successfully, 548 total actions
INFO: Build completed successfully, 548 total actions
I0820 16:49:42.129235 210040256 hello_world.cc:56] Hello World!
I0820 16:49:42.129977 210040256 hello_world.cc:56] Hello World!
I0820 16:49:42.130002 210040256 hello_world.cc:56] Hello World!
I0820 16:49:42.130019 210040256 hello_world.cc:56] Hello World!
I0820 16:49:42.130035 210040256 hello_world.cc:56] Hello World!
I0820 16:49:42.130053 210040256 hello_world.cc:56] Hello World!
I0820 16:49:42.130074 210040256 hello_world.cc:56] Hello World!
I0820 16:49:42.130100 210040256 hello_world.cc:56] Hello World!
I0820 16:49:42.130112 210040256 hello_world.cc:56] Hello World!
I0820 16:49:42.130125 210040256 hello_world.cc:56] Hello World!


Unexpected behavior for drag between line

Describe the bug
The drag line doesn't disappear if the user's cursor leaves the dragline area.
To Reproduce
https://rct.lukasbach.com/docs/guides/drag-and-drop#only-reordering-of-items-allowed
Can be reproduced here.

Drag an item
Move your cursor between items to display the drag between line
Move your cursor horizontally outside of the tree and see that the drag between line is still shown, even though dropping won't result in the item actually going there

You can also reproduce this (more significantly) when moving the cursor to the top or bottom of the tree, and then outside.
Expected behavior
The drag between line should only appear if the user's cursor is in a valid position to drop between items.

It looks like the same behavior can occur with dragging over items, not just the drag between line.

+1, I feel removing the drag line is a better indicator to the user that a drop will fail, rather than adjusting the dataTransfer.dropEffect cursor icon. However I don't see an easy way to accomplish this, I think the InteractionManager would need to communicate with the tree.

Adding to this, if I drag an element over another element and then decide I don't want to actually drop it there, the element I was dragging over remains selected as the place to drop.
https://github.com/user-attachments/assets/f1b63824-3d08-4b0f-a51b-7d5c39255ab1
This is particularly undesirable.

Hi, thanks for the report! I pushed a new release 2.4.6 which hopefully solves the issues you described. Let me know if that worked for you.

Hi @lukasbach looks great - I've been testing for several days now and can confirm all of the issues seem to be resolved. Thank you!


molotov: init at 4.2.2

Motivation for this change
Implementation of  #76849. Currently can't work with "master" because gst-plugins-base-0.10.36 has been marked broken with d034a00 . You can test with https://github.com/apeyroux/molotov.nix
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Oops dup with #92884


If inlined source has sourceMaps, then following lines will be broken

e.g.

If I want to inline A script which has source maps, then above scripts will become
**
Note B and C scripts are  ignored because of the leading //# for source maps

I can confirm make sure to set
devtool: false in your webpack config


[Epic] OpenXLA PJRT multiple client (single-node, multi-GPU) support

### Tasks
- [ ] https://github.com/openxla/iree/issues/13245
- [ ] https://github.com/openxla/iree/issues/12948

@julianwa Please review the Confidence status here - this was taken from Tables.

@julianwa Is this Epic still relevant? Duplicate of #13245 ?


Move ZFS options to correct place in man page

ZFS options in man page was put in wrong place, correct it.
Signed-off-by: Zhu Guihua<EMAIL_ADDRESS>

LGTM 🐯
/cc @thaJeztah

LGTM, thanks!


Expose etcd.Response for romana-2.0

Existing implementation doesn't expose recursive nature of etcd.Node which makes it impossible to watch trees recursively.

Approved for 2.0, lets revist this after 2.0 is out.


Particular libraries are getting downgraded

Describe the issue
Particular libraries are getting downgraded, even if on the TOML it says there's a new update available.
Attached you can see the libraries that are being downgraded.
com.google.android.play:core always downgraded to 1.8.0 from 1.10.3
ok.squareup.okhttp3:okhttp downgraded to 4.9.2 from 4.11.0
Stacktrace
Please run Gradle with the --stacktrace option and share the output in case of a Gradle error.

This has been mentioned a couple of times, for example here: https://github.com/littlerobots/version-catalog-update-plugin/issues/116
Can you try if running the task with --refresh-dependencies helps? I suspect this is some kind of sorting issue in the dependency versions plugin, but I'm not sure. If you have a project that you can provide that reproduces this consistently, that would be great.

The 0.8.2 release has a new way of resolving dependencies, which might fix this problem too (see #125 for more details).  Would be great if you could try it on your project!

@beshoy-samy did you enable the new resolver? Like mentioned in #125? If you want me to take a look, please provide a minimal project as an example that reproduces the problem.


tower-abci: support CometBFT 0.38.x

This PR adds support for 0.38.x and adds a key-value store over ABCI example for that version.

We want to get this into a tagged release ahead of deciding whether/when we will move to cometbft-rs.

thank you for doing this, @erwanor!


K8SPXC-264 Improve scaling tests

* try to wait for data synchronization between pxc nodes
* add smart check of 'CrashLoopBackOff' status

Test name
Status

big-data
passed

scaling
passed

init-deploy
failed

recreate
passed

storage
passed

limits
passed

self-healing
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

upgrade
passed

monitoring
passed

self-healing-advanced
passed

monitoring-2-0
passed

upgrade-consistency
passed

security-context
passed

demand-backup
passed

affinity
passed

operator-self-healing
passed

one-pod
passed

auto-tuning
passed

scheduled-backup
passed

proxysql-sidecar-res-limits
passed

demand-backup-encrypted-with-tls
passed


resize unamed.gif

Ref:
https://logosbynick.com/edit-an-animated-gif-with-gimp/#:~:text=To resize your GIF%2C simply,not just the active layer.

or
grantwinney.com/cool-markdown-tricks-for-github/

Using Kramdown so this worked
https://gist.github.com/uupaa/f77d2bcf4dc7a294d109#gistcomment-2096178
If you are using kramdown, try this:

![test image size](/img/post-bg-2015.jpg){:class="img-responsive"}
![test image size](/img/post-bg-2015.jpg){:height="50%" width="50%"}
![test image size](/img/post-bg-2015.jpg){:height="700px" width="400px"}


Return information from the optimization routine

Such as number of function evaluations, number of interchanges of information between processes, etc.
This should probably be returned in a struct that you define.

Ok, a nice thing to implement.

What is "number of function evaluations" ?

The number of times the function is called.
On Sat, 22 Jun 2019, 00:30 Yashvardhan Sharma<EMAIL_ADDRESS>wrote:

What is "number of function evaluations" ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/yashcodes/CharibdeOptim.jl/issues/17?email_source=notifications&email_token=AABO2TVBUOG27PS42DIPJVLP3W2IFA5CNFSM4H2G66F2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYKBH3Q#issuecomment-504632302,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABO2TTHMC75P5QOOMOZKIDP3W2IFANCNFSM4H2G66FQ
.


Add original version of Digital Twin Blueprint for review purposes

Going to use this PR as a placeholder to review the Digital Twin Blueprint

Closing this since nobody cares


can you set colours globally?

Hi,
Really like this and am using it quite a bit throughout an app I'm developing.
But since I want the same style to be consistent throughout, I was wondering if it's possible to set the colours globally rather than having to pass them each time.
Something like:
Vue.use(VueRadioToggleButtons, {     color:'#ff5500',     textColor:'#000',     selectedTextColor:'#fff' });
Not a big deal, but would just be neater.
Thanks
Simon.

Plugin options has been release with v0.1.0. 🎉
Happy New Year 2020. 🎆

Many thanks!
Happy New Year to you too!
Simon

On 5 Jan 2020, at 13:19, Saran Tanpituckpong ✅<EMAIL_ADDRESS>wrote:
Plugin options has been release with v0.1.0. 🎉
Happy New Year 2020. 🎆
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/gluons/vue-radio-toggle-buttons/issues/3?email_source=notifications&email_token=ABISTIRPFYKW4AYRONX6T6DQ4HM5FA5CNFSM4JRV5FSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIDWZAA#issuecomment-570911872, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABISTIR6X7MLMESXS72BK4DQ4HM5FANCNFSM4JRV5FSA.


Compile error due to libusb in Ubuntu 19.10

I am having trouble building librealsense on Ubuntu 19.10 . All builds fine till I get to these errors shown below.
/usr/bin/ld: ../../librealsense2.so.2.34.0: undefined reference tlibusb_get_port_numbers
/usr/bin/ld: ../../librealsense2.so.2.34.0: undefined reference to libusb_handle_events_completed
My cmake command is
cmake ../ -DFORCE_RSUSB_BACKEND=true -DCMAKE_BUILD_TYPE=release -DBUILD_EXAMPLES=true -DBUILD_GRAPHICAL_EXAMPLES=true -DBUILD_PYTHON_BINDINGS=true
Any idea what I need to fix the libusb errors. The tail end of the build is shown below.
[ 59%] Building CXX object examples/hello-realsense/CMakeFiles/rs-hello-realsense.dir/rs-hello-realsense.cpp.o cd /home/jim/Downloads/librealsense/build/examples/hello-realsense && ccache /usr/bin/c++  -DBUILD_EASYLOGGINGPP -DBUILD_SHARED_LIBS -DELPP_NO_DEFAULT_LOG_FILE -DELPP_THREAD_SAFE -DGLFW_DLL -DHWM_OVER_XU -DRS2_USE_LIBUVC_BACKEND -DUNICODE -I/home/jim/Downloads/librealsense/realsense2 -I/home/jim/Downloads/librealsense/src -I/home/jim/Downloads/librealsense/examples/hello-realsense/rs-hello-realsense -I/home/jim/Downloads/librealsense/build -I/home/jim/Downloads/librealsense/include  -pedantic -g -Wno-missing-field-initializers -Wno-switch -Wno-multichar -Wsequence-point -Wformat -Wformat-security -mssse3 -pthread -O3 -DNDEBUG -fPIE   -std=gnu++11 -o CMakeFiles/rs-hello-realsense.dir/rs-hello-realsense.cpp.o -c /home/jim/Downloads/librealsense/examples/hello-realsense/rs-hello-realsense.cpp [ 59%] Linking CXX executable rs-hello-realsense cd /home/jim/Downloads/librealsense/build/examples/hello-realsense && /usr/bin/cmake -E cmake_link_script CMakeFiles/rs-hello-realsense.dir/link.txt --verbose=1 ccache /usr/bin/c++   -pedantic -g -Wno-missing-field-initializers -Wno-switch -Wno-multichar -Wsequence-point -Wformat -Wformat-security -mssse3 -pthread -O3 -DNDEBUG  -rdynamic CMakeFiles/rs-hello-realsense.dir/rs-hello-realsense.cpp.o  -o rs-hello-realsense -Wl,-rpath,/home/jim/Downloads/librealsense/build: ../../librealsense2.so.2.34.0 /usr/lib/x86_64-linux-gnu/libglfw.so.3.3 -lGL -lGLU  /usr/bin/ld: ../../librealsense2.so.2.34.0: undefined reference tolibusb_get_port_numbers'
/usr/bin/ld: ../../librealsense2.so.2.34.0: undefined reference to `libusb_handle_events_completed'
collect2: error: ld returned 1 exit status
make[2]: *** [examples/hello-realsense/CMakeFiles/rs-hello-realsense.dir/build.make:88: examples/hello-realsense/rs-hello-realsense] Error 1
make[2]: Leaving directory '/home/jim/Downloads/librealsense/build'
make[1]: *** [CMakeFiles/Makefile2:496: examples/hello-realsense/CMakeFiles/rs-hello-realsense.dir/all] Error 2
make[1]: Leaving directory '/home/jim/Downloads/librealsense/build'
make: *** [Makefile:130: all] Error 2
`

I have had a case where Librealsense has been successfully built in Ubuntu 19.10 using the FORCE RSUSB method, so it should be possible.  Assuming that you have an internet connection (which is a requirement of this installation method), does the build succeed please if you do not include the -DBUILD_PYTHON_BINDINGS=true statement please?

Thanks @MartyG-RealSense .  I tried without  -DBUILD_PYTHON_BINDINGS=true and got the same result unfortunatelel.

Are you launching the CMake instruction whilst in the Build folder of Librealsense please?   (Librealsense > Build)
If you do not have a Build directory in your Librealsense root folder, it can be created and then navigated to with the instruction ** mkdir build && cd build.**

Thanks @MartyG-RealSense
Yes I am executing the cmake from within the build folder.
~/Downloads/librealsense/build$ cmake ../ -DFORCE_RSUSB_BACKEND=true -DCMAKE_BUILD_TYPE=release -DBUILD_EXAMPLES=true -DBUILD_GRAPHICAL_EXAMPLES=true
Any other thoughts on this.

I have never seen these libusb error messages before.  It looks as though it is tripping up on building the hello-realsense example program though.  Try leaving out -DBUILD_EXAMPLES=true this time please.

It seems that the problem program hello-realsense is still being built despite removing examples from the cmake command. New cmake command is below followed by the tail of the build output. Same errors as before.
cmake ../ -DFORCE_RSUSB_BACKEND=true -DCMAKE_BUILD_TYPE=release
[ 59%] Building CXX object examples/hello-realsense/CMakeFiles/rs-hello-realsense.dir/rs-hello-realsense.cpp.o cd /home/jim/Downloads/librealsense/build/examples/hello-realsense && ccache /usr/bin/c++  -DBUILD_EASYLOGGINGPP -DBUILD_SHARED_LIBS -DELPP_NO_DEFAULT_LOG_FILE -DELPP_THREAD_SAFE -DGLFW_DLL -DHWM_OVER_XU -DRS2_USE_LIBUVC_BACKEND -DUNICODE -I/home/jim/Downloads/librealsense/realsense2 -I/home/jim/Downloads/librealsense/src -I/home/jim/Downloads/librealsense/examples/hello-realsense/rs-hello-realsense -I/home/jim/Downloads/librealsense/build -I/home/jim/Downloads/librealsense/include  -pedantic -g -Wno-missing-field-initializers -Wno-switch -Wno-multichar -Wsequence-point -Wformat -Wformat-security -mssse3 -pthread -O3 -DNDEBUG -fPIE   -std=gnu++11 -o CMakeFiles/rs-hello-realsense.dir/rs-hello-realsense.cpp.o -c /home/jim/Downloads/librealsense/examples/hello-realsense/rs-hello-realsense.cpp [ 59%] Linking CXX executable rs-hello-realsense cd /home/jim/Downloads/librealsense/build/examples/hello-realsense && /usr/bin/cmake -E cmake_link_script CMakeFiles/rs-hello-realsense.dir/link.txt --verbose=1 ccache /usr/bin/c++   -pedantic -g -Wno-missing-field-initializers -Wno-switch -Wno-multichar -Wsequence-point -Wformat -Wformat-security -mssse3 -pthread -O3 -DNDEBUG  -rdynamic CMakeFiles/rs-hello-realsense.dir/rs-hello-realsense.cpp.o  -o rs-hello-realsense -Wl,-rpath,/home/jim/Downloads/librealsense/build: ../../librealsense2.so.2.34.0 /usr/lib/x86_64-linux-gnu/libglfw.so.3.3 -lGL -lGLU  /usr/bin/ld: ../../librealsense2.so.2.34.0: undefined reference to libusb_get_port_numbers'
/usr/bin/ld: ../../librealsense2.so.2.34.0: undefined reference to libusb_handle_events_completed' collect2: error: ld returned 1 exit status make[2]: *** [examples/hello-realsense/CMakeFiles/rs-hello-realsense.dir/build.make:88: examples/hello-realsense/rs-hello-realsense] Error 1 make[2]: Leaving directory '/home/jim/Downloads/librealsense/build' make[1]: *** [CMakeFiles/Makefile2:496: examples/hello-realsense/CMakeFiles/rs-hello-realsense.dir/all] Error 2 make[1]: Leaving directory '/home/jim/Downloads/librealsense/build' make: *** [Makefile:130: all] Error 2

It looks as though you have stripped the CMake build instruction about as far as you can go.
Did you do any other Librealsense installations on this computer before doing the RSUSB method?  If there are multiple conflicting installations then it may be better to start with a fresh install of Linux.

I did try using a Linux package to install it though it didn't work out so I went this route. I thought I uninstalled all remnants of the package however. Could my error be related to this issue with libusb which I found here #555

Though that case relates to the current SDK's predecessor Librealsense1, there is a potential for conflicts in any situation where you have files with the same filename and different ages.

I noticed I have a libusb-0.1-4 on my system as well. Maybe that is causing an issue?
`~$ dpkg -L libusb-0.1-4
/lib/x86_64-linux-gnu/libusb-0.1.so.4.4.4
/usr/share/doc/libusb-0.1-4
/usr/share/doc/libusb-0.1-4/README.Debian
/usr/share/doc/libusb-0.1-4/changelog.Debian.gz
/usr/share/doc/libusb-0.1-4/copyright
/lib/x86_64-linux-gnu/libusb-0.1.so.4
`
Though I tried using this flag with no difference
-D USE_SYSTEM_LIBUSB=false

I found an older Librealsense1 case where an old libusb file was also causing the libusb_get_port_numbers error:
https://github.com/IntelRealSense/librealsense/issues/180

Thanks @MartyG-RealSense . I uninstalled libusb-0.1-4 but still no change. such a mystery..

I'm not sure why it would be having such difficulty over building a simply constructed program such as rs-hello-realsense.cpp
If you have another PC available, you could try installing it on that and see if it makes a difference.  Otherwise, I will pick up the case again when I am back on-shift in the morning in 7 hours from the time of writing this.  Good luck!

I did further research and found other cases where the build fails at 59%.  One user with this problem solved it by explicitly stating -DBUILD_EXAMPLES=false in their CMake instruction.

Thank you I will try this later today and get back to you. It would be nice however to be able to build the examples but one step at a time I guess.

Ok @MartyG-RealSense that worked! Thanks! Strangely it also built pyrealsense2 even though it wasn't asked to build the python bindings? It seems as if there is something wrong with the cmake flags. The command I used is
cmake ../ -DFORCE_RSUSB_BACKEND=true -DCMAKE_BUILD_TYPE=release -DBUILD_EXAMPLES=false
Now any thoughts on how I can build the examples?

Great news - congratulations!
Advice on only building the samples is offered here:
https://github.com/IntelRealSense/librealsense/issues/2946#issuecomment-449290237

Yes I tried that . When building only the examples I get the same errors as previously.

Any luck if you do make after CMake?
cmake .. -DBUILD_EXAMPLES=true && make -J && sudo make install

No that is what I tried but I get the same errors as before.

Please try to build it "headless" (no examples that use a graphics interface such as OpenGL) in case the build is breaking due to a graphics related issue:
cmake ../ -DBUILD_EXAMPLES=true -DBUILD_GRAPHICAL_EXAMPLES=false

Ok I tried that and get the same result which I would expect since it seems to be a libusb issue, not really graphics related from what I can see.

Would it be possible to use Ubuntu 18.04 instead, since that is more of a known quantity in regard to Librealsense installation.

Sorry no I can't go back to 18.04. I was actually hoping to migrate up to 20.04 soon.  I ran make with the -d option and here is the tail of that in case that is of use..
  Prerequisite '../include/librealsense2/hpp/rs_device.hpp' is older than target 'examples/hello-realsense/CMakeFiles/rs-hello-realsense.dir/rs-hello-realsense.cpp.o'.      Prerequisite '../include/librealsense2/hpp/rs_frame.hpp' is older than target 'examples/hello-realsense/CMakeFiles/rs-hello-realsense.dir/rs-hello-realsense.cpp.o'.      Prerequisite '../include/librealsense2/hpp/rs_options.hpp' is older than target 'examples/hello-realsense/CMakeFiles/rs-hello-realsense.dir/rs-hello-realsense.cpp.o'.      Prerequisite '../include/librealsense2/hpp/rs_pipeline.hpp' is older than target 'examples/hello-realsense/CMakeFiles/rs-hello-realsense.dir/rs-hello-realsense.cpp.o'.      Prerequisite '../include/librealsense2/hpp/rs_processing.hpp' is older than target 'examples/hello-realsense/CMakeFiles/rs-hello-realsense.dir/rs-hello-realsense.cpp.o'.      Prerequisite '../include/librealsense2/hpp/rs_record_playback.hpp' is older than target 'examples/hello-realsense/CMakeFiles/rs-hello-realsense.dir/rs-hello-realsense.cpp.o'.      Prerequisite '../include/librealsense2/hpp/rs_sensor.hpp' is older than target 'examples/hello-realsense/CMakeFiles/rs-hello-realsense.dir/rs-hello-realsense.cpp.o'.      Prerequisite '../include/librealsense2/hpp/rs_types.hpp' is older than target 'examples/hello-realsense/CMakeFiles/rs-hello-realsense.dir/rs-hello-realsense.cpp.o'.      Prerequisite '../include/librealsense2/rs.h' is older than target 'examples/hello-realsense/CMakeFiles/rs-hello-realsense.dir/rs-hello-realsense.cpp.o'.      Prerequisite '../include/librealsense2/rs.hpp' is older than target 'examples/hello-realsense/CMakeFiles/rs-hello-realsense.dir/rs-hello-realsense.cpp.o'.      Prerequisite '../examples/hello-realsense/rs-hello-realsense.cpp' is older than target 'examples/hello-realsense/CMakeFiles/rs-hello-realsense.dir/rs-hello-realsense.cpp.o'.      Prerequisite 'examples/hello-realsense/CMakeFiles/rs-hello-realsense.dir/flags.make' is older than target 'examples/hello-realsense/CMakeFiles/rs-hello-realsense.dir/rs-hello-realsense.cpp.o'.     No need to remake target 'examples/hello-realsense/CMakeFiles/rs-hello-realsense.dir/rs-hello-realsense.cpp.o'.     Considering target file 'examples/hello-realsense/CMakeFiles/rs-hello-realsense.dir/build.make'.     File 'examples/hello-realsense/CMakeFiles/rs-hello-realsense.dir/build.make' was considered already.     Considering target file 'librealsense2.so.2.34.0'.      Looking for an implicit rule for 'librealsense2.so.2.34.0'.      Trying pattern rule with stem 'librealsense2.so.2.34.0'.      Trying implicit prerequisite 'librealsense2.so.2.34.0,v'.      Trying pattern rule with stem 'librealsense2.so.2.34.0'.      Trying implicit prerequisite 'RCS/librealsense2.so.2.34.0,v'.      Trying pattern rule with stem 'librealsense2.so.2.34.0'.      Trying implicit prerequisite 'RCS/librealsense2.so.2.34.0'.      Trying pattern rule with stem 'librealsense2.so.2.34.0'.      Trying implicit prerequisite 's.librealsense2.so.2.34.0'.      Trying pattern rule with stem 'librealsense2.so.2.34.0'.      Trying implicit prerequisite 'SCCS/s.librealsense2.so.2.34.0'.      No implicit rule found for 'librealsense2.so.2.34.0'.      Finished prerequisites of target file 'librealsense2.so.2.34.0'.     No need to remake target 'librealsense2.so.2.34.0'.    Finished prerequisites of target file 'examples/hello-realsense/rs-hello-realsense'.   Must remake target 'examples/hello-realsense/rs-hello-realsense'. Putting child 0x55ee9a3355a0 (examples/hello-realsense/rs-hello-realsense) PID 32098 on the chain.
Reaping losing child 0x55cd9a995160 PID 32097
make[1]: *** [CMakeFiles/Makefile2:496: examples/hello-realsense/CMakeFiles/rs-hello-realsense.dir/all] Error 2
Removing child 0x55cd9a995160 PID 32097 from chain.
Reaping losing child 0x55983fa64290 PID 32056
make: *** [Makefile:130: all] Error 2
Removing child 0x55983fa64290 PID 32056 from chain.
`

I'm not sure that there is anything else that can be done to rescue this build.  It has ended up with the same errors that were present at the start of the case (libusb_handle_events_completed and libusb_get_port_numbers).  It may be better to try again with the upcoming SDK version (probably 2.35.0) or wait until you upgrade to 20.04 and see if the clean Ubuntu install that it will provide removes whatever was preventing the examples from building.

Thanks @MartyG-RealSense I guess I am a bit surprised that none of the developers have a sense from the error messages what is going wrong with the build. I don't really see downloading a new distribution as a great solution. I would prefer to know what is throwing the error message and why.

I have never seen the 'Trying pattern rule with stem' error before.  It seems to result from CMake rather than Librealsense.
It is recommended to use CMake version 3.8 or newer for Librealsense building.  Could you check which version you have and update to a newer one from the CMake website if it is old please?
https://cmake.org/download/

My cmake version is much newer that 3.8 ie.
cmake version 3.13.4

I will refer your case to a support manager for further guidance.  I apologise for the delay in resolving your problem in the meantime.

Thank you. I really appreciate the support.

Ok I figured this out. I rebuilt and installed the latest libusb.  This may not be necessary however what was important was to get rid of an older version of libusb-1.0.so  that was in /usr/local/lib  which is where librealsense2.so.2.34 lives. Installing the new libusb put it in /usr/lib . I suppose I could have linked the old libusb to this one as well but the build process was able to find the new libusb anyway.

Thanks for the update!  Is it all working okay now?

Everything built so that's good. I am still waiting for my sensor to arrive but I think all is good. I believe we can close this issue.

Awesome news - thanks a lot for your patience during this process.  I will close the case now.  Good luck!


/editor support

Hello! How to use /editor command for aider? It works but I can't save buffer with editor mode.
Error: E382: Cannot write, 'buftype' option is set

How to fix this problem or how to use it correctly in this plugin?
Thanks.

Hi, sorry for the late response. Maybe I dont get your question but using /editor command defeats the purpose of nvim-aider plugin. The plugin integrates aider directly into Neovim, so you don't need to open another Neovim instance.

I've enabled this the flatten plugin https://github.com/aweis89/aider.nvim if you wanna check it out

Thanks for pointing that out. So I will close that issue bc I am not currently thinking about implementing this.


A thought about exposing rendering pipeline to public.

Is your feature request related to a problem? Please describe.
I really like how F3D is set up in its minimal and bloat-free way. The only downside I experienced so far is that libf3d does not expose its rendering pipeline to the client. Sometimes I just have a vtkObject (e.g., vtkUnstructuredGrid or vtkPolyData) which I want to visualize. But if I use F3D as a dependency in my project without changing the source, I can only read a file from disk.
Something as easy as this will satisfy all my needs.
vtkNew<vtkUnstructuredGrid> ug;
// build my ug and then add it to f3d engine
f3d::engine eng;
eng->getRenderer()->addDataSet(ug);

Or maybe there is already a way to achieve this using the plugin? Please advise.
Describe the solution you'd like
Expose vktRenderer in the engine so we can use it to add vtkObject from memory.
Describe alternatives you've considered
None.
Additional context
None.
Contribution
Yes, I can contribute.

It was a design choice to make VTK dependency private and it is not planned to change.
That being said, I think this may be possible through a "dummy" plugin as long as you can make it communicate with your application and provide the unstructured grid there. You may want to give it a go just so we know if and how to do it.
Another way to implement this would be trough a void* API, or some kind of vtkDataSet marshalling operation, but adding such an API needs some reflexion to do it right.

I also think it could be done through a plugin. It definitely makes sense if your VTK pipeline is fixed.
For example, if you have a simulation code, you can set the inputs in a file, and run the simulation and the post-processing pipeline in the importer.

Once read/write to buffer is supported by VTK, implementing that should be trivial.

Is there a WIP MR we can follow in VTK?

First layer has been implemented:
https://gitlab.kitware.com/vtk/vtk/-/merge_requests/9663
Second layer is ongoing:
https://gitlab.kitware.com/vtk/vtk/-/merge_requests/9764
Then we need to implement it in the reader we want though.

@YangShen398 : please note a new API has been added to the loader. You can now load geometry from a dedicated mesh struct. You probably can convert from a VTK dataset without mush issue. Closing this.
#978 #980 #983


Consider streaming some progress indication to stderr

Currently there's no output until the trace is done. We could print some progress indicator to stderr, or we could try to rework the guts of transformation from the tracer to output so that we'd be able to at least stream output, instead of waiting for the whole trace.

JSON and markdown aren't very stream-friendly, so at best we're getting a progress bar.

Not necessary at all for lint, and quite complex to do well for tracing. I don't think this is valuable enough right now.


Line graph aggregate data

I have a data set that has values based on a month time interval. I would like to toggle between the month view and a year (or quarter) view. I noticed I could use the 'round' option to round where the data points appear on the graph, but then I get 12 data points per 'x' value. Is there an easy way to sum the values for each 'x' into a single displayed point?
I can pretty easily just change the data set, but I thought it might be worth asking.

@Warlord099 the best way to do this is to change the dataset and call update() on the chart instance.

I figured as much. Thanks.


Add support for threshold dates in filter query expressions

This PR consists of two commits.

The first simply removes the generated file src/js/filterlang.mjs from the git repo and adds it to the .gitignore to help keep it from being added to the repo again in future.
The second commit adds support for threshold dates (with tag t:) to the filter query expressions.  This means also adding a jsTodoTxt extension to recognize the threshold date tag during parsing of the todos.

This PR provides a large part of the functionality requested in issue #193, namely the filtering of the todo list based on threshold dates.  Still to do in a future PR is the support for updating threshold dates on completion of recurring todos.

@zerodat I'm out for the weekend and cannot build before Monday. Sorry, I didn't expect you to be so fast ;)

No problem, @ransome1.  Who knows ... maybe I'll have some more for you to merge by Monday.  ;)

@ransome1, adding commits to this pull request to do the following:

make the filter query expressions a little more forgiving in supporting ISO dates with single-digit month or day, and supporting intervals without a number like today+d rather than requiring today+1d.
add the code to main.js to support command-line arg for todo file name

@ransome1, :smile: these are my last commits for this PR, which should merge painlessly with the head of your develop branch.
The last two commits are:

incorporating @weisserd s fix for the ambiguous sunday problem in sugar.  I added this to my PR because his fix is in todotxtExtensions.mjs and that is also a file that I have modified to add the ThresholdExtension.  Including it in this PR will make it easier for you to merge I think.
the bigger commit is to add recurrence support for threshold dates, so that the t: gets updated according to the logic that @amariusz outlined in #193 .  Note that I have decided to stick with the past behavior of sleek by adding due dates to todos that have only a rec: tag and neither due: nor t:.  But if there is a rec: and a t:, no due: will be added.


[Meta] Allow public edits for wiki

The wiki page currently doesn't allow other users to make edits or fixes.

I would gladly accept PR:s for the wiki, but I'm not sure if that is possible..

Wikis should be editable without prs if the repo owner sets it up.
See https://github.com/inorichi/tachiyomi/wiki
On that wiki there's an edit button that anyone can use to edit the wiki.
I'll try to look for some instructions on how to set that up and link them here.

Link for setting up public editing of wiki : https://help.github.com/en/github/building-a-strong-community/changing-access-permissions-for-wikis


 U: .

 U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2382/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 27s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m 52s
master passed

+0 :ok:
refguide
4m 52s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 24s
the patch passed

+1 :green_heart:
whitespace
0m  1s
The patch has no whitespace issues.

+0 :ok:
refguide
5m  1s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

_ Other Tests _

+1 :green_heart:
asflicense
0m 17s
The patch does not generate ASF License warnings.

19m 24s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2382/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2382

Optional Tests
dupname asflicense refguide

uname
Linux 34b10941d160 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 9c5dbb29c0

refguide
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2382/1/artifact/yetus-general-check/output/branch-site/book.html

refguide
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2382/1/artifact/yetus-general-check/output/patch-site/book.html

Max. process+thread count
78 (vs. ulimit of 12500)

modules
C: . U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2382/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.


The kluster wil have all cloudprovider references removed from the helm deployment
launchctl, flightctl and routegc are skipped for "noCloud" klusters.
At the moment it still create a service user in the openstack project and sets up etcd to backup to swift. We disentail that at a later stage

rebase on master


⚠ Bofrost.lu has degraded performance

In 38541ca, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1398 ms

Resolved: Bofrost.lu performance has improved in f242f03 after 19 minutes.


Revisit user/permission docs

/enterprise/v1.0/features/web-console-features/
The current docs are out of date.

Fixed by https://github.com/influxdata/docs.influxdata.com/pull/560


Rahul docs basic concepts

WIP - draft of a "FHIR Basics Concepts" page for our docs.
After finishing this, next step will be to create a "Medplum Basic Concepts" page

Coverage remained the same at 95.068% when pulling 6274ec0e2c3702494a267256091da1e41873cbd1 on rahul-docs-basic-concepts into f3c01f2cb4cbb420fd207e643a7961f405367be9 on main.


Is PA only now available for 5.1 now. Or am I Missing Somthing?

So on my laptop everything works fine
I had fresh install of UE5.03 on to a new PC
Installed visual studio 2019 with everything needed, and got a fresh install of PA from the market place for UE5.03.
However for some reason the UE5 project with project acoustics it now doesnt work, saying the Ace file isnt loading.

I have double checked and it works on my laptop fine. (installed and completed summer 2022)
the set up is also the same

Again it works fine with Laptop,  On the PC i deleted and re-imported the ace file with a different name to stop any referencing issues, and still nothing loads.
Im was unable to find the 'project acoustics sample project' for 5.03, so i moved it over from my previous laptop, and I am having the same issue.
Is PA only now available for 5.1 now, and i need migrate everything? Or am I Missing Somthing?
Thanks Tommy

When you installed the latest version from the marketplace, you installed a new version of Project Acoustics (we call it 2022.1). This version of PA works with both UE 5.0 and UE 5.1, but will not work with older ACE files. I suspect you are trying to use an ACE file you generated with the previous version of PA, and that is not supported. Look in the Output Log to see if you see an error message about your ACE file. To fix this, you will need to regenerate your ACE files with the latest version of PA.

Thank you kyle for the quick reply, this makes total sense now thank you x