Create a MeshRootCertificate on osm install

Please describe the Improvement and/or Feature Request

Part of #4502
Create a MeshRootCertificate resource when installing OSM.
Notes:

the MRC custom resource would use the existing certificate provider values defined in values.schema.json. The same default values would apply
the MRC resource must also be cleaned up on uninstall

Scope (please mark with X where applicable)

New Functionality          [x]
Install                    [x]
Certificate Management     [x]

Some thoughts and questions regarding creating MeshRootCertificate creation on install:
Creating the MeshRootCertificate on OSM install

Should the MeshRootCertificate be created in the same way the MeshConfig is created? Currently, on install a ConfigMap containing the preset mesh configurations is created. The osm-bootstrap is responsible for loading the preset mesh configuration and then creating the mesh config using those settings if it doesn't already exist. The osm-controller and osm-injector on the osm-bootrstap to start (and create the MeshConfig before starting up).

A Kubernetes secret or ConfigMap could be created on install containing the preset Mesh Root Certificate settings. The osm-bootstrap would be responsible for creating the MRC in the same way it is responsible for creating the MeshConfig.
Should the user be able to specify whether they want a Secret or Config map to contain the settings of the MRC

Could all control plane components wait on the creation of the MRC? Even though the custom resource is the last resource kind to be created by Helm, could all control plane components just wait in a pending state until the default MRC CR is created?

Upgrading OSM:

What happens if the upgrade occurs during a root certificate rotation? Is it possible to disallow this?

This shouldn't be a problem if the osm-bootstrap is able to determine if an MRC or multiple MRCs already exist and not a new one.  When information is obtained from the MRCs, OSM should be able to pick back up on rotation.

When checking for existing MRCs, the osm-bootstrap (or some other process) will look for MRCs in the control plane namespace with an active status. If there are no MRCs in an active status, a default MRC will be created.
How should certificate provider settings be preserved during an upgrade? No MRC to MRC?

Are the certificate provider settings currently preserved during an upgrade?

Some thoughts and questions regarding creating MeshRootCertificate creation on install:
Creating the MeshRootCertificate on OSM install

Should the MeshRootCertificate be created in the same way the MeshConfig is created? Currently, on install a ConfigMap containing the preset mesh configurations is created. The osm-bootstrap is responsible for loading the preset mesh configuration and then creating the mesh config using those settings if it doesn't already exist. The osm-controller and osm-injector on the osm-bootrstap to start (and create the MeshConfig before starting up).

A Kubernetes secret or ConfigMap could be created on install containing the preset Mesh Root Certificate settings. The osm-bootstrap would be responsible for creating the MRC in the same way it is responsible for creating the MeshConfig.

If you mean by creating a configmap first I see no reason to do so. I believe the reasons to do this initially for the mesh config are now obsolete.

Should the user be able to specify whether they want a Secret or Config map to contain the settings of the MRC

If there are any secret values required in an MRC, a standard approach would be to add a field secretRef which is an object that contains secret name, secret key, and maybe namespace (or just use same namespace).

Could all control plane components wait on the creation of the MRC? Even though the custom resource is the last resource kind to be created by Helm, could all control plane components just wait in a pending state until the default MRC CR is created?

Wait/error (kill the pod) seems like a reasonable approach.

Upgrading OSM:

What happens if the upgrade occurs during a root certificate rotation? Is it possible to disallow this?

This shouldn't be a problem if the osm-bootstrap is able to determine if an MRC or multiple MRCs already exist and not a new one.  When information is obtained from the MRCs, OSM should be able to pick back up on rotation.

When checking for existing MRCs, the osm-bootstrap (or some other process) will look for MRCs in the control plane namespace with an active status. If there are no MRCs in an active status, a default MRC will be created.

How should certificate provider settings be preserved during an upgrade? No MRC to MRC?

We can also provide directions for users (require multiple steps in the upgrade directions), or put more logic in the CLI to query existing settings.

Are the certificate provider settings currently preserved during an upgrade?


gaussian_blur caused panic

I'm not sure if this is a bug or just my incompetency (I'm new to both Rust and OpenCV). Calling gaussian_blur caused the following error,
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', libcore/option.rs:345:21

My code is really simple,
extern crate cv;
use cv::highgui::*;
use cv::videoio::VideoCapture;
use cv::*;

fn main() {
    let cap = VideoCapture::new(0);
    assert!(cap.is_open());

    highgui_named_window("Window", WindowFlag::Autosize).unwrap();

    while let Some(m) = cap.read() {
        let mut m = m.cvt_color(cv::imgproc::ColorConversion::BGR2HSV);
        let size = cv::core::Size2i::new(5, 5);
        m.gaussian_blur(size, 0.9, 0.9, cv::mat::BorderType::Transparent);
        m.show("Window", 30).unwrap();
    }
}

At first, I had a segfault but reading OpenCV documentation reveals that the size must be an odd number. Changing the kernel size to odd number doesn't caused segfault anymore but it panicked instead.
Running gdb, I could see that it panicked after a call to cv_gaussian_blur here,
https://github.com/nebgnahz/cv-rs/blob/46372956e02768c968507afd2507152586c414be/src/imgproc.rs#L463
I tried to step through the function to see where exactly it failed, but it just led me to something that I don't quite understand.

Could you run with full stacktrace, please?
RUST_BACKTRACE=1 cargo run

$  RUST_BACKTRACE=1 cargo run
    Finished dev [unoptimized + debuginfo] target(s) in 0.05s
     Running `target/debug/hello`
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', libcore/option.rs:345:21
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
             at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
   1: std::sys_common::backtrace::print
             at libstd/sys_common/backtrace.rs:71
             at libstd/sys_common/backtrace.rs:59
   2: std::panicking::default_hook::{{closure}}
             at libstd/panicking.rs:211
   3: std::panicking::default_hook
             at libstd/panicking.rs:227
   4: std::panicking::rust_panic_with_hook
             at libstd/panicking.rs:475
   5: std::panicking::continue_panic_fmt
             at libstd/panicking.rs:390
   6: rust_begin_unwind
             at libstd/panicking.rs:325
   7: core::panicking::panic_fmt
             at libcore/panicking.rs:77
   8: core::panicking::panic
             at libcore/panicking.rs:52
   9: __rust_maybe_catch_panic
             at /checkout/src/libcore/macros.rs:20
             at libpanic_unwind/gcc.rs:101
             at libpanic_unwind/lib.rs:108
  10: std::rt::lang_start_internal
             at libstd/panicking.rs:289
             at libstd/panic.rs:392
             at libstd/rt.rs:58
  11: std::rt::lang_start
             at /checkout/src/libstd/rt.rs:74
  12: main
  13: __libc_start_main
  14: _start
fatal runtime error: failed to initiate panic, error 5
[1]    13895 abort (core dumped)  RUST_BACKTRACE=1 cargo run

Initially I thought this might be the reason,
https://github.com/nebgnahz/cv-rs/blob/46372956e02768c968507afd2507152586c414be/src/imgproc.rs#L462
The doc mentions that dst must be the same size as the src. I changed it to something like,
let m = CMat::new_with_size(self.rows, self.cols, 1); // basically calls cv_mat_new_with_size

still the same error though.

It's clearly a rust error. CMat::new() has nothing to deal with exception. Unfortunately I have no camera so I cannot run it locally, so you have to investigate it yourself, I could only guide you.
The error says that some Option<T> that expected to be Some is None.
The only unwrap I see is highgui_named_window("Window", WindowFlag::Autosize).unwrap();. But for some reason I don't see anything in the backtrace that points to the line in user code. That's strange.

I don't think it is from highgui_named_window. You can reproduce the same issue with the following code, there is no need for camera this time. Commenting the gaussian_blur line should fix it.
extern crate cv;
use cv::highgui::*;
use cv::imgcodecs::ImageReadMode;
use cv::*;

fn main() {
    let args: Vec<_> = std::env::args().collect();
    if args.len() != 2 {
        println!("Usage: display_image ImageToLoadAndDisplay");
        std::process::exit(-1);
    }

    let mat = Mat::from_path(&args[1], ImageReadMode::Color).expect("Failed to read from path");
    let size = cv::core::Size2i::new(5, 5);

    if !mat.is_valid() {
        println!("Could not open or find the image");
        std::process::exit(-1);
    }

    mat.gaussian_blur(size, 0.9, 0.9, cv::mat::BorderType::Transparent);
    highgui_named_window("Display window", WindowFlag::Normal);
    mat.show("Display window", 0);
}

I stepped through all the codes, still no idea what's going though but it looks like it panicked after this line,
cv::_InputArray::init (this=0x7fffffffd260, _flags=16842752, _obj=0x7fffe7e42500) at /usr/local/include/opencv2/core/mat.inl.hpp:67
67	{ flags = _flags; obj = (void*)_obj; }
(gdb)
[New Thread 0x7fffe7dff700 (LWP 7036)]
[New Thread 0x7fffe75fe700 (LWP 7037)]
[New Thread 0x7fffe69ff700 (LWP 7038)]
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', libcore/option.rs:345:21
note: Run with `RUST_BACKTRACE=1` for a backtrace.
fatal runtime error: failed to initiate panic, error 5

Hmm, works for me

I only changed the border type to default because I was getting Unknown/unsupported border type for transparent.


after package update 4.11.0 php artisan optimize timeout on deploy script

✏ Describe the bug
After an update on October 22nd, my GitHub Actions deploy workflow encountered a new issue during the Docker-based deployment.
The php artisan optimize command now hangs or fails specifically at the laravel-data step of 'php artisan optimize', which appears to have been added recently.
This issue was not present in earlier deployments.
Environment:
Deployment Platform: Docker
Command: php artisan optimize
Package: spatie/laravel-data
Details:
In previous deployments, php artisan optimize completed without any issues. Here’s an example of the successful output:
php artisan optimize

config ........................................................ 63.88ms DONE
events ......................................................... 1.53ms DONE
routes ....................................................... 149.42ms DONE
views ........................................................ 160.26ms DONE

However, after the recent update to spatie/laravel-data, the php artisan optimize process now hangs during the laravel-data caching step, taking over a minute before timing out and failing:
php artisan optimize

config ........................................................ 65.99ms DONE
events ......................................................... 1.76ms DONE
routes ....................................................... 143.56ms DONE
views ........................................................ 160.37ms DONE
laravel-data ....................................................... 1m FAIL

This prolonged delay and failure at the laravel-data step are causing deployment issues and interrupting the deployment workflow.
If there are known compatibility issues, recent changes affecting this process, or recommended workarounds, please advise on resolving this behavior.
Thank you for looking into this!
↪ To Reproduce
add php artisan optimize into a dockerfile that run on deploy
✅ Expected behavior
php artisan optimize to not timeout
🖥 Versions
Laravel: 11
Laravel Data:
PHP: 8.3

@emaireZaiko Hi, in the Github Actions output, is it any other log with Exception or Error after this line?
laravel-data ....................................................... 1m FAIL

@rust17 hi sorry for the delay!
Here is the output from the github action:

To optimize performance, Laravel data caches information once during deployment. This cached data is stored in Redis, a file, or another cache driver, depending on the configuration settings:
'structure_caching' => [
        'enabled' => true, <------- whether cache is enabled
        'cache' => [
            'store' => env('CACHE_STORE', env('CACHE_DRIVER', 'file')), <------- which cache driver to use
            'prefix' => 'laravel-data',
            'duration' => null,
        ]
    ],

Based on the information provided, deployment issues might be related to the CACHE_DRIVER or CACHE_STORE configuration. It's worth checking these settings. Additionally, disabling Laravel data caching during GitHub Actions may help.


Add LoadStoreVectorizationPass to GPU pipeline as default

After splitting dispatch functions, a placeholder op could show up in
different functions. In LoadStoreVectorizationPass, we would rewrite the
shape of the placeholder op. If one is rewrote and another is not, two
spv.globalVariable are needed.
note: this depends on https://reviews.llvm.org/D87887

@MaheshRavishankar As discussed, let move forward and revisit iterating on Aliased decoration in a follow up. For now we don't hit the issue from this PR. I also filed an issue #3573 to track this.


Scheduler reoccurance pattern loses weekday

Bug found here: http://stackoverflow.com/questions/27974320/fuelux-scheduler-loose-the-information-of-day-when-we-select-weekly-recurrence
Change L510 to something like the following to include attr('checked', true): item.find( 'input[data-value="' + temp[ i ] + '"]' ).attr('checked', true).parent().addClass( 'active' );
Add additional unit tests to test multiple reoccurrence patterns.

To clarify, there are unit tests.  However, currently these check the DOM moreso to ensure that elements have the proper classes, checked attributes, etc.
We need additional tests to ensure that the value passed into schedule is what is returned.  Something like this:
var schedule = {
    startDateTime: '2014-03-31T03:23+02:00',
    timeZone: {
        offset: '+02:00'
    },
    recurrencePattern: 'FREQ=WEEKLY;BYDAY=WE;INTERVAL=6;BYSETPOS=3;UNTIL=20140919;'
};

$scheduler.scheduler('value', schedule);
equal($scheduler.scheduler('value'), schedule, 'schedule set correctly');


Fix the certificate target

Currently, the certificate still points to the VM hostname (ee-tik-nsgvm057.ethz.ch) but should be updated to use the new domain name (autopower.ethz.ch)
Also relate somewhat to #14

I'm currently waiting on the update from SWITCH to update the new url in their registry. If this works, it should be done.

Done.


Bug fix for invalid job id for many parallel cloudAI jobs

Summary
The current cloudAI slurm runner fails when many parallel jobs are submitted. The current strategy is to use squeue with the job id. However, when many CloudAI jobs are submitted in parallel, some of these jobs might complete at the same time resulting in invalid job id error by the time CloudAI queries this status.
This PR fixes this issue by using an alternative way to determine the job completion status instead of squeue. I
Test Plan
CI/CD
Run on real system (Job completion status works and moves on to the next job).
(venv) $ python ./clouda
ix.py run --system-config conf/common/system/xxxx--tests-dir conf/common/test --test-scenario conf/nccl_test_nightly.toml
[INFO] System Name: xxxx
[INFO] Scheduler: slurm
[INFO] Test Scenario Name: nccl-test
[INFO] Checking if test templates are installed.
[INFO] Test Scenario: nccl-test

Section Name: Tests.1
  Test Name: nccl_test_all_reduce
  Description: all_reduce
  No dependencies
Section Name: Tests.2
  Test Name: nccl_test_all_gather
  Description: all_gather
  Start Post Comp: Tests.1
Section Name: Tests.3
  Test Name: nccl_test_reduce_scatter
  Description: reduce_scatter
  Start Post Comp: Tests.2
Section Name: Tests.4
  Test Name: nccl_test_alltoall
  Description: alltoall
  Start Post Comp: Tests.3
[INFO] Initializing Runner [RUN] mode
[INFO] Creating SlurmRunner
[INFO] Starting test scenario execution.
[INFO] Starting test: Tests.1
[INFO] Running test: Tests.1
[INFO] Submitted slurm job: 1262768
[INFO] Job completed: Tests.1
[INFO] Delayed start for test Tests.2 by 5 seconds.
[INFO] Starting test: Tests.2
[INFO] Running test: Tests.2
[INFO] Submitted slurm job: 1262771
[INFO] Job completed: Tests.2
[INFO] Delayed start for test Tests.3 by 5 seconds.
[INFO] Starting test: Tests.3
[INFO] Running test: Tests.3
[INFO] Submitted slurm job: 1262775

Stress test on another internal cluster with simultaneous 111 job submission using CloudAI
$python utils/dgx.py --auto_hosts --partition batch --max_num_nodes=4 --test_path conf/staging/acceptance_test/test --test_scenario_dir conf/staging/acceptance_test/test_scenario/ --output_dir results --mode run
No config file provided, proceeding with command-line arguments if available.
[INFO] System Name: xxx
[INFO] Scheduler: slurm
[INFO] Test Scenario Name: xxxxx
[INFO] Checking if test templates are installed.
[INFO] Test Scenario: xxxx

Section Name: Tests.0
  Test Name: [REDACTED]
  Description: sendrecv
  No dependencies
Section Name: Tests.1
  Test Name: [REDACTED]
  Description: sendrecv
  No dependencies
Section Name: Tests.2
  Test Name: [REDACTED]
  Description: all_reduce
  No dependencies
Section Name: Tests.3
  Test Name: [REDACTED]
  Description: all_reduce
  No dependencies
Section Name: Tests.4
  Test Name: [REDACTED]
  Description: sendrecv
  No dependencies
Section Name: Tests.5
  Test Name: [REDACTED]
  Description: sendrecv
  No dependencies
Section Name: Tests.6
  Test Name: [REDACTED]
  Description: sendrecv
  No dependencies
Section Name: Tests.7
  Test Name: [REDACTED]
  Description: sendrecv
  No dependencies
Section Name: Tests.8
  Test Name: [REDACTED]
  Description: all_gather
  No dependencies
Section Name: Tests.9
  Test Name: [REDACTED]
  Description: all_gather
  No dependencies
Section Name: Tests.10
  Test Name: [REDACTED]
  Description: all_reduce
  No dependencies
Section Name: Tests.11
  Test Name: [REDACTED]
  Description: all_reduce
  No dependencies
Section Name: Tests.12
  Test Name: [REDACTED]
  Description: alltoall
  No dependencies
Section Name: Tests.13
  Test Name: [REDACTED]
  Description: alltoall
  No dependencies
Section Name: Tests.14
  Test Name: [REDACTED]
  Description: reduce_scatter
  No dependencies
Section Name: Tests.15
  Test Name: [REDACTED]
  Description: reduce_scatter
  No dependencies
Section Name: Tests.16
  Test Name: [REDACTED]
  Description: alltoall
  No dependencies
Section Name: Tests.17
  Test Name: [REDACTED]
  Description: alltoall
  No dependencies
Section Name: Tests.18
  Test Name: [REDACTED]
  Description: reduce_scatter
  No dependencies
Section Name: Tests.19
  Test Name: [REDACTED]
  Description: reduce_scatter
  No dependencies
Section Name: Tests.20
  Test Name: [REDACTED]
  Description: alltoall
  No dependencies
Section Name: Tests.21
  Test Name: [REDACTED]
  Description: alltoall
  No dependencies
Section Name: Tests.22
  Test Name: [REDACTED]
  Description: all_gather
  No dependencies
Section Name: Tests.23
  Test Name: [REDACTED]
  Description: all_gather
  No dependencies
Section Name: Tests.24
  Test Name: [REDACTED]
  Description: reduce_scatter
  No dependencies
Section Name: Tests.25
  Test Name: [REDACTED]
  Description: reduce_scatter
  No dependencies
Section Name: Tests.26
  Test Name: [REDACTED]
  Description: alltoall
  No dependencies
Section Name: Tests.27
  Test Name: [REDACTED]
  Description: alltoall
  No dependencies
Section Name: Tests.28
  Test Name: [REDACTED]
  Description: all_gather
  No dependencies
Section Name: Tests.29
  Test Name: [REDACTED]
  Description: all_gather
  No dependencies
Section Name: Tests.30
  Test Name: [REDACTED]
  Description: all_reduce
  No dependencies
Section Name: Tests.31
  Test Name: [REDACTED]
  Description: all_reduce
  No dependencies
Section Name: Tests.32
  Test Name: [REDACTED]
  Description: sendrecv
  No dependencies
Section Name: Tests.33
  Test Name: [REDACTED]
  Description: sendrecv
  No dependencies
Section Name: Tests.34
  Test Name: [REDACTED]
  Description: reduce_scatter
  No dependencies
Section Name: Tests.35
  Test Name: [REDACTED]
  Description: reduce_scatter
  No dependencies
Section Name: Tests.36
  Test Name: [REDACTED]
  Description: reduce_scatter
  No dependencies
Section Name: Tests.37
  Test Name: [REDACTED]
  Description: reduce_scatter
  No dependencies
Section Name: Tests.38
  Test Name: [REDACTED]
  Description: all_gather
  No dependencies
Section Name: Tests.39
  Test Name: [REDACTED]
  Description: all_gather
  No dependencies
Section Name: Tests.40
  Test Name: [REDACTED]
  Description: reduce_scatter
  No dependencies
Section Name: Tests.41
  Test Name: [REDACTED]
  Description: reduce_scatter
  No dependencies
Section Name: Tests.42
  Test Name: [REDACTED]
  Description: reduce_scatter
  No dependencies
Section Name: Tests.43
  Test Name: [REDACTED]
  Description: reduce_scatter
  No dependencies
Section Name: Tests.44
  Test Name: [REDACTED]
  Description: alltoall
  No dependencies
Section Name: Tests.45
  Test Name: [REDACTED]
  Description: alltoall
  No dependencies
Section Name: Tests.46
  Test Name: [REDACTED]
  Description: all_gather
  No dependencies
Section Name: Tests.47
  Test Name: [REDACTED]
  Description: all_gather
  No dependencies
Section Name: Tests.48
  Test Name: [REDACTED]
  Description: all_gather
  No dependencies
Section Name: Tests.49
  Test Name: [REDACTED]
  Description: all_gather
  No dependencies
Section Name: Tests.50
  Test Name: [REDACTED]
  Description: sendrecv
  No dependencies
Section Name: Tests.51
  Test Name: [REDACTED]
  Description: sendrecv
  No dependencies
Section Name: Tests.52
  Test Name: [REDACTED]
  Description: reduce_scatter
  No dependencies
Section Name: Tests.53
  Test Name: [REDACTED]
  Description: reduce_scatter
  No dependencies
Section Name: Tests.54
  Test Name: [REDACTED]
  Description: alltoall
  No dependencies
Section Name: Tests.55
  Test Name: [REDACTED]
  Description: alltoall
  No dependencies
Section Name: Tests.56
  Test Name: [REDACTED]
  Description: sendrecv
  No dependencies
Section Name: Tests.57
  Test Name: [REDACTED]
  Description: sendrecv
  No dependencies
Section Name: Tests.58
  Test Name: [REDACTED]
  Description: sendrecv
  No dependencies
Section Name: Tests.59
  Test Name: [REDACTED]
  Description: sendrecv
  No dependencies
Section Name: Tests.60
  Test Name: [REDACTED]
  Description: all_reduce
  No dependencies
Section Name: Tests.61
  Test Name: [REDACTED]
  Description: all_reduce
  No dependencies
Section Name: Tests.62
  Test Name: [REDACTED]
  Description: all_reduce
  No dependencies
Section Name: Tests.63
  Test Name: [REDACTED]
  Description: all_reduce
  No dependencies
Section Name: Tests.64
  Test Name: [REDACTED]
  Description: sendrecv
  No dependencies
Section Name: Tests.65
  Test Name: [REDACTED]
  Description: sendrecv
  No dependencies
Section Name: Tests.66
  Test Name: [REDACTED]
  Description: alltoall
  No dependencies
Section Name: Tests.67
  Test Name: [REDACTED]
  Description: alltoall
  No dependencies
Section Name: Tests.68
  Test Name: [REDACTED]
  Description: alltoall
  No dependencies
Section Name: Tests.69
  Test Name: [REDACTED]
  Description: alltoall
  No dependencies
Section Name: Tests.70
  Test Name: [REDACTED]
  Description: all_gather
  No dependencies
Section Name: Tests.71
  Test Name: [REDACTED]
  Description: all_gather
  No dependencies
Section Name: Tests.72
  Test Name: [REDACTED]
  Description: all_reduce
  No dependencies
Section Name: Tests.73
  Test Name: [REDACTED]
  Description: all_reduce
  No dependencies
Section Name: Tests.74
  Test Name: [REDACTED]
  Description: alltoall
  No dependencies
Section Name: Tests.75
  Test Name: [REDACTED]
  Description: alltoall
  No dependencies
Section Name: Tests.76
  Test Name: [REDACTED]
  Description: reduce_scatter
  No dependencies
Section Name: Tests.77
  Test Name: [REDACTED]
  Description: reduce_scatter
  No dependencies
Section Name: Tests.78
  Test Name: [REDACTED]
  Description: sendrecv
  No dependencies
Section Name: Tests.79
  Test Name: [REDACTED]
  Description: sendrecv
  No dependencies
Section Name: Tests.80
  Test Name: [REDACTED]
  Description: reduce_scatter
  No dependencies
Section Name: Tests.81
  Test Name: [REDACTED]
  Description: reduce_scatter
  No dependencies
Section Name: Tests.82
  Test Name: [REDACTED]
  Description: all_reduce
  No dependencies
Section Name: Tests.83
  Test Name: [REDACTED]
  Description: all_reduce
  No dependencies
Section Name: Tests.84
  Test Name: [REDACTED]
  Description: alltoall
  No dependencies
Section Name: Tests.85
  Test Name: [REDACTED]
  Description: alltoall
  No dependencies
Section Name: Tests.86
  Test Name: [REDACTED]
  Description: reduce_scatter
  No dependencies
Section Name: Tests.87
  Test Name: [REDACTED]
  Description: reduce_scatter
  No dependencies
Section Name: Tests.88
  Test Name: [REDACTED]
  Description: sendrecv
  No dependencies
Section Name: Tests.89
  Test Name: [REDACTED]
  Description: sendrecv
  No dependencies
Section Name: Tests.90
  Test Name: [REDACTED]
  Description: all_gather
  No dependencies
Section Name: Tests.91
  Test Name: [REDACTED]
  Description: all_gather
  No dependencies
Section Name: Tests.92
  Test Name: [REDACTED]
  Description: all_gather
  No dependencies
Section Name: Tests.93
  Test Name: [REDACTED]
  Description: all_gather
  No dependencies
Section Name: Tests.94
  Test Name: [REDACTED]
  Description: sendrecv
  No dependencies
Section Name: Tests.95
  Test Name: [REDACTED]
  Description: sendrecv
  No dependencies
Section Name: Tests.96
  Test Name: [REDACTED]
  Description: all_reduce
  No dependencies
Section Name: Tests.97
  Test Name: [REDACTED]
  Description: all_reduce
  No dependencies
Section Name: Tests.98
  Test Name: [REDACTED]
  Description: alltoall
  No dependencies
Section Name: Tests.99
  Test Name: [REDACTED]
  Description: alltoall
  No dependencies
Section Name: Tests.100
  Test Name: [REDACTED]
  Description: alltoall
  No dependencies
Section Name: Tests.101
  Test Name: [REDACTED]
  Description: alltoall
  No dependencies
Section Name: Tests.102
  Test Name: [REDACTED]
  Description: reduce_scatter
  No dependencies
Section Name: Tests.103
  Test Name: [REDACTED]
  Description: reduce_scatter
  No dependencies
Section Name: Tests.104
  Test Name: [REDACTED]
  Description: sendrecv
  No dependencies
Section Name: Tests.105
  Test Name: [REDACTED]
  Description: sendrecv
  No dependencies
Section Name: Tests.106
  Test Name: [REDACTED]
  Description: all_gather
  No dependencies
Section Name: Tests.107
  Test Name: [REDACTED]
  Description: all_gather
  No dependencies
Section Name: Tests.108
  Test Name: [REDACTED]
  Description: all_gather
  No dependencies
Section Name: Tests.109
  Test Name: [REDACTED]
  Description: all_gather
  No dependencies
Section Name: Tests.110
  Test Name: [REDACTED]
  Description: all_gather
  No dependencies
Section Name: Tests.111
  Test Name: [REDACTED]
  Description: all_gather
  No dependencies
[INFO] Initializing Runner [RUN] mode
[INFO] Creating SlurmRunner
[INFO] Starting test scenario execution.
 Please review the 'debug.log' file to confirm successful completion or to identify any issues.

Additional Notes
Context: Discussion thread.

SlurmInstaller has PREREQUISITES, let's add sacct there too.
Please add unit tests that reproduces the issue before this change to ensure we won't repeat this problem

Fixed 1.
Regarding 2, this is a purely system behavior and not sure how we can capture this in unit test. These commands require squeue and sacct commands which implicitly requiring slurm system.  Also the interface did not change at all.
If you have better ideas on capturing it, please follow the slack thread and please feel free to contribute to the unit test to capture this behavior in a seperate PR. I think this can be a good follow up PR and should not block customer request.
However, this PR has been tested with verification team's NCCL test on internal cluster. It has also been stress tested by simultaneously launching 111 jobs on a different production cluster. Without this PR, the original design choice used in CloudAI on checking the job completion would fail for this new customer setup. So given this has been solidly tested on production system (see the test plan), we should approve and merge this.

... feel free to contribute to the unit test to capture this behavior in a seperate PR.

We have an agreement to add unit tests for all new features and fixes. Let's stick to this agreement.
Here is how I would approach testing test_is_job_running:
@pytest.mark.parametrize("stdout,is_running", [("RUNNING", True), ("PENDING", True), ("COMPLETED", False)])
def test_is_job_running(stdout: str, is_running: bool, slurm_system: SlurmSystem):
    job = SlurmJob(Mock(), 1)
    pp = Mock()
    pp.communicate = Mock(return_value=(stdout, ""))
    slurm_system.cmd_shell.execute = Mock(return_value=pp)
    assert slurm_system.is_job_running(job) is is_running

Similar approach can be applied for testing with stderr (likely, as a separate test function).
is_job_completed is almost the same (should we move common part into a separate function?) and can be tested the same way.

... feel free to contribute to the unit test to capture this behavior in a seperate PR.

We have an agreement to add unit tests for all new features and fixes. Let's stick to this agreement.
Here is how I would approach testing test_is_job_running:
@pytest.mark.parametrize("stdout,is_running", [("RUNNING", True), ("PENDING", True), ("COMPLETED", False)])
def test_is_job_running(stdout: str, is_running: bool, slurm_system: SlurmSystem):
    job = SlurmJob(Mock(), 1)
    pp = Mock()
    pp.communicate = Mock(return_value=(stdout, ""))
    slurm_system.cmd_shell.execute = Mock(return_value=pp)
    assert slurm_system.is_job_running(job) is is_running

Similar approach can be applied for testing with stderr (likely, as a separate test function).
is_job_completed is almost the same (should we move common part into a separate function?) and can be tested the same way.

You are right. I am trying to stick to the agreement here. The authors adding a new feature should also extend the unit test for that feature. However, this is not a new feature. This was a bug fix where in certain high job submission load the CloudAI breaks due to a design choice we made ~7 months ago. Hence, this PR is basically to address and fix this bug. It does not change the interface. To cover these system related issues, I have extensively tested on two clusters (including stressing it based on the customer requirement).
The original design discussion also mentions this issue on why adding more unit test for this system class would not extend the coverage and in fact this bug further validates it.
We agreed and approved this PR (including the comments on CI test plan).
The unit test you proposing also will not provide coverage this behavior as well. I can explain the behavior and maybe you can see if unit testing can support or fake this. Merely capturing the stdout and faking the outputs will not give coverage to this or future system related bug. We need to launch 100+ fake processes and have 1 master process (cloudai executable) and capture its interactions/feedbacks. If you think unit test infra features we have today can also simulate this runtime behavior, please see this as an opportunity to solidly it. But this shouldn't block this PR and should be a separate PR imo.


No Webhook events received.

Please check attached screenshot

You won't receive webhooks till you start the season first if it's you question

I already started session then I had set the webhook but no response data recieved to webhook.site

You won't receive webhooks till you start the season first if it's you question

I already started session then I had set the webhook but no response data recieved to webhook.site

Could you try with WHATSAPP_HOOK_URL=https://httpbin.org/post and see if there's logs for that?

Where I can check the logs?

The same console or 'docker log whatsapp-http-api' command


Can't find variable: sqlite3_open_v2

Hello,
Thanks for the plugin. This is working fine with Android but having problem with IOS.

CONSOLE ERROR file:///app/services/commonServices.js:20:30: We failed to open database ReferenceError: Can't find variable: sqlite3_open_v2
CONSOLE LOG file:///app/services/commonServices.js:21:28: null
CONSOLE ERROR file:///app/tns_modules/@angular/core/./bundles/core.umd.js:1091:24: ERROR Error: Uncaught (in promise): ReferenceError: Can't find variable: sqlite3_open_v2

What I did so far:
Delete the app off the phone.
tns platform clean ios
tns run ios

My Code:
new Sqlite("mydb.db", function(err, db) {
      if (err) {
        console.error("We failed to open database", err);

      }

MacOS: 10.12.5 (16F73)
Xcode: Version 8.3.2 (8E2002)
NativeScript: 3.0.1

Anyone can help me on this issue please?

Verify the plugin exists in the node_modules folder.
Try do to another tns platform clean ios

Try it again.  The clean will normally fix the issue; but if the plugin isn't installed correctly the clean won't do anything...

@NathanaelA Thanks for reply. Yes, I am trying it but don't know not working. I think the folder exsist under "node_modules".
https://prnt.sc/fg6ow5
https://prnt.sc/fg6ozi
I tried to clean platform several time but still no luck :(
CONSOLE ERROR file:///app/services/commonServices.js:20:30: We failed to open database ReferenceError: Can't find variable: sqlite3_open_v2

@NathanaelA Any further suggestions?

@jibon57 - Off the top of my head no.   It is on my todo list to verify this works as-is on TNS 3.0; but I haven't had a chance to try it yet.

@NathanaelA, Did you get time to test it?

@jibon57 - It is on my list to do list to try out; but I only work on free stuff when my paid stuff is all done.

@jibon57 - It works fine on my demo app.   I just pulled the latest from my repo; updated to NS 3.x for everything in the demo and then ran it fine on iOS.      I am not sure what you are doing wrong...

@NathanaelA, Will you please share your MacOS's information? I tried your plugin from a fresh Nativescript angular js template. But getting same error there also.

aha.. I got the problem... It was for the long path like described here: https://github.com/NathanaelA/nativescript-sqlite/issues/2#issuecomment-289174895
I moved the project to Desktop & ran. It's working now ....

I think it has to do with spaces in the path rather than the length. See my comment here https://github.com/NathanaelA/nativescript-sqlite/issues/2#issuecomment-327161166

One more solution is to also delete the app from the phone before you do a rebuild of the app and re-run it.  A version of the APP on the phone can cause the new version to not be updated properly.

Delete App off phone
TNS platform clean ios
TNS run ios


TableOfContents without Header

Whenever the TOC starts on a new Page (by using \clearpage), the first TOC Page is generated without a Header. However, if the TOC is pushed on to the next Page (e.g. by using \vspace*{\fill}), it is generated with a Header, as expected.
As a Solution, there should be an easy-to-use Command that specifies whether the Title Page should be empty or have Text on it (maybe \cleartitlepage?). Then, when the Command is Used, the (current) 2in vspace when creating the Title could be replaced by the full Height.

Another TODO: Update the default Header vspace to 1.5in


Fix: Click on navBar crashed with null reference without search box

Re-opened PR #124 because of branch reorganization.
The NavBar plugin crashes when an item is clicked and no search box element is present.

Hi @robi26, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

This looks great! Thanks for this, @robi26 --I'll go ahead and merge this in. Cheers!


Add the major Falcon Moddels 7b  and 40b instruct

Add the major Falcon Moddels, 7b instruct and 40b instruct..
Change schema.json to reflect falcon 40B models:
In schema.json there is one quantization type missing in
definition - ModelFile-properties: There is a Q3_K_L type, i added it to the enum.
The apache-licensed Falcon Models come in the flavours of 7B and 40B.
A 40B option is  missing in the enumeration
numParameters, so i added "40B" to the enum.

I will do so if you accept these changes.

Sorry for the delay. Thanks for this! Will come back here after the next version comes out (hopefully tomorrow)


Prioritization in Http2 requests

Http2 has the concept of prioritization of requests within a stream. How do we want to think of these with respect to the proxy front end if it has an HTTP/2 or HTTP/3 connection. As we terminate the end user request, and create new requests, potentially distributed across multiple servers, any prioritization signals will be lost. As we queue requests for processing, or pack responses into the response stream, do we need to be prioritizing which responses get streamed first?
https://blog.cloudflare.com/adopting-a-new-approach-to-http-prioritization/

Prioritization is not exposed or honored in any of our http client or server stacks. It's not a thing the proxy needs to consider unless our customers come asking for it.

I tend to agree here. I'd suggest this be an Idea (since we do basically understand the actionable work, we just don't know the exact design or value) and be backlogged.

Recommend we close this due to low interest.


[3/4] Route Blinding: send MPP over multiple blinded paths

In this PR, we remove the restriction of only being able to send to a single blinded payment path.
Nodes will now be able to take advantage of the multiple blinded paths provided for a given
payment to perform MPP if needed.
Depends on: https://github.com/lightningnetwork/lnd/pull/8735
Tracking Issue: https://github.com/lightningnetwork/lnd/issues/6690

@ellemouton, remember to re-request review from reviewers when ready

@ziggie1984: review reminder
@ellemouton, remember to re-request review from reviewers when ready

@ellemouton, remember to re-request review from reviewers when ready

Finally, there is one more assumption we make here: if a recipient provides us with a set of paths of various lengths but one of those paths is an intro-node-only path, then we just go ahead and discard the rest of the paths since it doesnt make sense to try those since we know that the intro node is the dest node.

I wonder if this would be considered a wrong behaviour of the person providing us the invoice, so maybe we should consider this as an invalid invoice to spot wrong implementations ?

I went to create an invoice with a blinded path on testnet, and ran into this panic:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x143a82b]

goroutine 4084 [running]:
github.com/lightningnetwork/lnd/routing.(*ChannelRouter).FindBlindedPaths(0xc0022b6f00, {0x2, 0x70, 0x68, 0x5c, 0xa8, 0x1a, 0x8e, 0x4d, 0x4d, ...}, ...)
	github.com/lightningnetwork/lnd@v0.18.2-beta/routing/router.go:727 +0x64b
github.com/lightningnetwork/lnd.(*rpcServer).AddInvoice.func3(0x20?)
	github.com/lightningnetwork/lnd@v0.18.2-beta/rpcserver.go:5816 +0x97
github.com/lightningnetwork/lnd/lnrpc/invoicesrpc.buildBlindedPaymentPaths(0xc0070713e0)
	github.com/lightningnetwork/lnd@v0.18.2-beta/lnrpc/invoicesrpc/addinvoice.go:1054 +0x42
github.com/lightningnetwork/lnd/lnrpc/invoicesrpc.AddInvoice({0x36f9090, 0xc003fc4450}, 0xc004d95080, 0xc0070715c8)
	github.com/lightningnetwork/lnd@v0.18.2-beta/lnrpc/invoicesrpc/addinvoice.go:517 +0x108e
github.com/lightningnetwork/lnd.(*rpcServer).AddInvoice(0xc00061a600, {0x36f9090, 0xc003fc4450}, 0xc001487980)
	github.com/lightningnetwork/lnd@v0.18.2-beta/rpcserver.go:5856 +0x6a5
github.com/lightningnetwork/lnd/lnrpc._Lightning_AddInvoice_Handler.func1({0x36f9090?, 0xc003fc4450?}, {0x22965c0?, 0xc001487980?})
	github.com/lightningnetwork/lnd@v0.18.2-beta/lnrpc/lightning_grpc.pb.go:2610 +0xcb
github.com/lightningnetwork/lnd/rpcperms.(*InterceptorChain).CreateServerOpts.(*InterceptorChain).middlewareUnaryServerInterceptor.func7({0x36f9090, 0xc003fc4450}, {0x22965c0, 0xc001487980}, 0xc00391a660, 0xc002205ec0)
	github.com/lightningnetwork/lnd@v0.18.2-beta/rpcperms/interceptor.go:832 +0x111
google.golang.org/grpc.getChainUnaryHandler.func1({0x36f9090, 0xc003fc4450}, {0x22965c0, 0xc001487980})
	google.golang.org/grpc@v1.59.0/server.go:1163 +0xb2
github.com/lightningnetwork/lnd/rpcperms.(*InterceptorChain).CreateServerOpts.(*InterceptorChain).MacaroonUnaryServerInterceptor.func5({0x36f9090, 0xc003fc4450}, {0x22965c0, 0xc001487980}, 0xc00391a660?, 0xc003f8fec0)
	github.com/lightningnetwork/lnd@v0.18.2-beta/rpcperms/interceptor.go:689 +0x7d
google.golang.org/grpc.getChainUnaryHandler.func1({0x36f9090, 0xc003fc4450}, {0x22965c0, 0xc001487980})
	google.golang.org/grpc@v1.59.0/server.go:1163 +0xb2
github.com/lightningnetwork/lnd/rpcperms.(*InterceptorChain).CreateServerOpts.(*InterceptorChain).rpcStateUnaryServerInterceptor.func3({0x36f9090, 0xc003fc4450}, {0x22965c0, 0xc001487980}, 0xc00391a660, 0xc002b80900)
	github.com/lightningnetwork/lnd@v0.18.2-beta/rpcperms/interceptor.go:781 +0xfc
google.golang.org/grpc.getChainUnaryHandler.func1({0x36f9090, 0xc003fc4450}, {0x22965c0, 0xc001487980})
	google.golang.org/grpc@v1.59.0/server.go:1163 +0xb2
github.com/lightningnetwork/lnd/rpcperms.(*InterceptorChain).CreateServerOpts.errorLogUnaryServerInterceptor.func1({0x36f9090?, 0xc003fc4450?}, {0x22965c0?, 0xc001487980?}, 0xc00391a660, 0xc002205ec0?)
	github.com/lightningnetwork/lnd@v0.18.2-beta/rpcperms/interceptor.go:605 +0x52
google.golang.org/grpc.NewServer.chainUnaryServerInterceptors.chainUnaryInterceptors.func1({0x36f9090, 0xc003fc4450}, {0x22965c0, 0xc001487980}, 0xc00391a660, 0x78?)
	google.golang.org/grpc@v1.59.0/server.go:1154 +0x85
github.com/lightningnetwork/lnd/lnrpc._Lightning_AddInvoice_Handler({0x22d29c0, 0xc00061a600}, {0x36f9090, 0xc003fc4450}, 0xc004b3b280, 0xc0007747a0)
	github.com/lightningnetwork/lnd@v0.18.2-beta/lnrpc/lightning_grpc.pb.go:2612 +0x143
google.golang.org/grpc.(*Server).processUnaryRPC(0xc0002661e0, {0x36f9090, 0xc003ed0f30}, {0x3708e60, 0xc004871a00}, 0xc002440240, 0xc000769770, 0x4a551d8, 0x0)
	google.golang.org/grpc@v1.59.0/server.go:1343 +0xdd1
google.golang.org/grpc.(*Server).handleStream(0xc0002661e0, {0x3708e60, 0xc004871a00}, 0xc002440240)
	google.golang.org/grpc@v1.59.0/server.go:1737 +0xc47
google.golang.org/grpc.(*Server).serveStreams.func1.1()
	google.golang.org/grpc@v1.59.0/server.go:986 +0x86
created by google.golang.org/grpc.(*Server).serveStreams.func1 in goroutine 4083
	google.golang.org/grpc@v1.59.0/server.go:997 +0x136

Can be rebased to point to master now!

Hmm seems like we need to check that the inpolicy is not nil as we already do in other parts in the routing codebase ?
// If there is no edge policy for this candidate node, skip.
		// Note that we are searching backwards so this node would have
		// come prior to the pivot node in the route.
		if channel.InPolicy == nil {
			return nil
		}

@ziggie1984 yep was thinking the same thing, I'll add that then try again. FWIW, this is a very very very old node, which makes it great for testing!

oop - I  accidentally clicked re-request @ziggie1984 🙈  sorry about that

Tried out the latest branch, and I was able to make an initial blinded paths payment!
Ran into some other issues along the way:

When trying to pay with default settings, I got INVALID_ONION_BLINDING each time.
That was with a node that may have been added within the blinded path as I had a direct channel with it.
I then tried to reduce max-num-paths to 1, initially thinking it woudl give me only 1 hop routes, but I understand now that means only have a single path.
After that I got some errors where it was unable to make a path at all: tlncli addinvoice --amt=100 --blind
[lncli] rpc error: code = Unknown desc = could not collect blinded path relay info: no channel updates found from node
022fb1230aefbd135141997f03343f5410e6f1ab11d337af6df92cb67d5a856748 for channel<PHONE_NUMBER>846388225
 tlncli addinvoice --amt=100 --blind
[lncli] rpc error: code = Unknown desc = could not build any blinded paths

Perhaps we should have an inner retry loop here. I did the command a few more times until one of them finally worked.

I tried again with only a single blinded path ( max-num-paths=1):

The first time around, it was trying to find very long routes to the dest, and failing:  TEMPORARY_CHANNEL_FAILURE @ 2nd hop |       34.580 |       36.342 | 100          | 2.707 |  2871717 |<PHONE_NUMBER>315978752 | 030f375d8aecdddc8523->24hr Drive Thru->POSTECHCCBR->TuDuD->lnd-test.24h.to->SOMBERMASTER->039c25->025eac
I tried again, with the path succeeding with a route of similar length:

| SUCCEEDED                           |        1.229 |        6.271 | 100          | 3.106 |  2871679 | 3157069
518315978752 | 030f375d8aecdddc8523->aranguren.org->OCEAN_TESTNET_WK1->03fef5->022060 |
+-------------------------------------+--------------+--------------+--------------+-------+----------+------------
---------+------------------------------------------------------------------------+
Amount + fee:   100 + 3.106 sat
Payment hash:   ab44ac84be151fde822a7dda35a7acf908d431ad719850ddfddccdb05220d38e
Payment status: SUCCEEDED, preimage:
b6243fdf1869bae1c962c5b528b8ba563845bad51320bebd921635cbb2044ed2

I think the instances of INVALID_ONION_BLINDING might be older nodes on testnet that aren't running the latest version of blinded paths.
Some other featrure requests after trying things out:

Command to unblind blinded paths as the creator. Can be useful for debugging.
All dynamically setting values like num paths and path length via lncli addinvoice. During testing I had to restart each time I wanted to mess with a different value.
Add ability to omit a node from the blinded path. Would've been useful to pinpoint if it's just certain nodes sending INVALID_ONION_BLINDING errors.


Add immutable HTTP cookie API

Motivation:
We currently rely on Netty's HTTP cookie API, but it has the following
drawbacks:

It is mutable.
It will not have SameSite attribute until Netty 5.

https://github.com/netty/netty/issues/8161

It will not allow cookies with the same name until Netty 5.

https://github.com/netty/netty/issues/7210

Modifications:

Add Cookie, which is an immutable representation of HTTP Cookie.
Add CookieBuilder which builds a Cookie.
Fork {Client,Server}Cookie{Encoder,Decoder} from Netty so it is
possible to encode and decode our Cookie.

Modify ServerCookieDecoder to allow cookies with the same name.

Result:

Immutable HTTP cookie API
(Deprecation) Cookies.copyOf() has been deprecated in favor of Cookies.of().
(Breaking) Cookies now use Armeria's own Cookie.
(Breaking?) Cookies may contain the cookies with the same name.

RFC does not prohibit duplicate names at all, so this is a correct behavior.

(Breaking?) Annotated services now accept only the first "Cookie" header when decoding cookies in an HttpRequest. Sending multiple "Cookie" headers was a violation of RFC 6265 anyway.

(Breaking?) Annotated services now accept only the first "Cookie" header when decoding cookies in an HttpRequest. Sending multiple "Cookie" headers was a violation of RFC 6265 anyway.

reference: https://github.com/line/armeria/issues/1567


IOT Edge not sending data to IOT Hub

Hello,
I have followed the getting started guide line by line and successfully installed and deployed iot edge device and temSensor simulator module. But not sending any data to IOT Hub. Please find below the respective queries and it's response.
PS C:\WINDOWS\system32> iotedge list
NAME             STATUS           DESCRIPTION      CONFIG
tempSensor1      running          Up 29 seconds    mcr.microsoft.com/azureiotedge-simulated-temperature-sensor:1.0
edgeHub          stopped          Stopped          mcr.microsoft.com/azureiotedge-hub:1.0
edgeAgent        running          Up 9 minutes     mcr.microsoft.com/azureiotedge-agent:1.0
PS C:\WINDOWS\system32> iotedge logs tempSensor1 -f
[2018-08-16 17:14:54 : Starting Module
[08/16/2018 05:14:55.039 PM] Main()
Using transport Amqp_Tcp_Only
Creating ModuleClient failed with exception System.TimeoutException: Operation timeout expired.
at Microsoft.Azure.Devices.Client.InternalClient.<>c.<ApplyTimeout>b__62_2(Task t)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot)
--- End of stack trace from previous location where exception was thrown ---
at SimulatedTemperatureSensor.Program.InitModuleClient(TransportType transportType) in /opt/vsts/work/1/s/edge-modules/SimulatedTemperatureSensor/src/Program.cs:line 100
Retrying...
Creating ModuleClient failed with exception System.TimeoutException: Operation timeout expired.
at Microsoft.Azure.Devices.Client.InternalClient.<>c.<ApplyTimeout>b__62_2(Task t)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot)
--- End of stack trace from previous location where exception was thrown ---
at SimulatedTemperatureSensor.Program.InitModuleClient(TransportType transportType) in /opt/vsts/work/1/s/edge-modules/SimulatedTemperatureSensor/src/Program.cs:line 100
Retrying...
Iot edge device keeps repeating above error event 5min or so.
Getting following error for IOT HUB:
8/16/2018 1:07:18 PM warn: edgelet_utils::logging -- Container runtime error - ApiError(ApiError { code: InternalServerError, content: Some(Object({"message": String("driver failed programming external connectivity on endpoint edgeHub
(00ebca8eaf19ee2d975dc23744d49cc9fb77700b7ecef5069987c94f5edccb96): Error starting userland proxy: Bind for <IP_ADDRESS>:443: unexpected error Permission denied")})) })
8/16/2018 1:07:18 PM info: edgelet_http::logging -- [mgmt] - - - [2018-08-16 17:07:18.814244300 UTC] "POST /modules/edgeHub/start?api-version=2018-06-28 HTTP/1.1" 500 Internal Server Error 363 "-" "-" pid(any)
8/16/2018 1:07:19 PM info: edgelet_http::logging -- [mgmt] - - - [2018-08-16 17:07:19.813281400 UTC] "POST /modules/edgeHub/start?api-version=2018-06-28 HTTP/1.1" 500 Internal Server Error 363 "-" "-" pid(any)
8/16/2018 1:07:19 PM warn: edgelet_utils::logging -- Container runtime error - ApiError(ApiError { code: InternalServerError, content: Some(Object({"message": String("driver failed programming external connectivity on endpoint edgeHub
(d1acee0ba328d7249e853f92453e2de6571d693b08a45395c7ff81d3e77f856d): Error starting userland proxy: Bind for <IP_ADDRESS>:443: unexpected error Permission denied")})) })
8/16/2018 1:07:25 PM info: edgelet_http::logging -- [mgmt] - - - [2018-08-16 17:07:25.853612300 UTC] "POST /modules/edgeHub/start?api-version=2018-06-28 HTTP/1.1" 500 Internal Server Error 363 "-" "-" pid(any)
8/16/2018 1:07:25 PM warn: edgelet_utils::logging -- Container runtime error - ApiError(ApiError { code: InternalServerError, content: Some(Object({"message": String("driver failed programming external connectivity on endpoint edgeHub
(4aa263a06662e18d2704af0fdb22a069b3b509725c59f2cbaf8fc1574a909e2b): Error starting userland proxy: Bind for <IP_ADDRESS>:443: unexpected error Permission denied")})) })
8/16/2018 1:07:30 PM info: edgelet_http::logging -- [mgmt] - - - [2018-08-16 17:07:30.370786100 UTC] "GET /modules?api-version=2018-06-28 HTTP/1.1" 200 OK 1291 "-" "iotedge/0.1.0" pid(any)
8/16/2018 1:07:37 PM info: edgelet_http::logging -- [mgmt] - - - [2018-08-16 17:07:37.825065 UTC] "POST /modules/edgeHub/start?api-version=2018-06-28 HTTP/1.1" 500 Internal Server Error 363 "-" "-" pid(any)
8/16/2018 1:07:37 PM warn: edgelet_utils::logging -- Container runtime error - ApiError(ApiError { code: InternalServerError, content: Some(Object({"message": String("driver failed programming external connectivity on endpoint edgeHub
(5ebfcde9feaec3e7ff4006f036749d87bf8f9c98b308190f6430ba362a786c82): Error starting userland proxy: Bind for <IP_ADDRESS>:443: unexpected error Permission denied")})) })

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

ID: 64575e7c-664c-4d6b-a440-24c91e93def5
Version Independent ID: 17d9481c-a75b-bbfd-1f9a-76fc3d6b2930
Content: Quickstart Azure IoT Edge + Windows
Content Source: articles/iot-edge/quickstart.md
Service: iot-edge
GitHub Login: @kgremban
Microsoft Alias: kgremban

@johnmay1 Thanks for the feedback. We are actively investigating and will get back to you soon.

@johnmay1 Do you have any other application like a webserver etc running that using the SSL port 443?

Yes, I have IIS sever installed and I am using it on daily basis.
John
On Fri, Aug 17, 2018 at 3:58 PM Venkat Yalla<EMAIL_ADDRESS>wrote:

@johnmay1 https://github.com/johnmay1 Do you have any other application
like a webserver etc running that using the SSL port 443?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/13531#issuecomment-413973145,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVELiZv2d58PSfwUwsbi_A7YunhGerp_ks5uRyB8gaJpZM4WAR-d
.

What's going on here is that the edge hub is trying to listen for downstream connections on port 443 and failing to acquire it as it already used by IIS. To get past this, from the portal, click Set Modules,  then click Advanced Runtime Settings and edit the edge hub create options to remove the 443 port binding. Save the runtime settings and submit the updated deployment after clicking next, next.

@johnmay1 Have you had a chance to implement the change recommended by @veyalla?
We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

Hub is not connected and also able to see sensor data in log but not seeing any data on Azure IOT Hub portal. Also installed VS Code plugin and tried to send message but failed with following error:

Regards,
John

@johnmay1 I am going to keep this issue closed because the document referenced by this GitHub issue is the basic IoT Edge tutorial. It is not the tutorial that has you connect with VS Code to view messages, nor a tutorial that has you connect to you IoT Hub instance with Machine Learning or App Services, etc.
The tutorial you are working through is this one: Use Azure IoT Toolkit extension for Visual Studio Code to send and receive messages between your device and IoT Hub
By providing document feedback directly against this specific tutorial, we are able to more efficiently address any documentation issues that might arise from trying to complete this specific tutorial. If you are having technical support issues, Azure Support or the MSDN or StackOverflow forums are more appropriate.


Adding support for sparse custom board

Fixes #114
This change allows to define a sparse board object:  new Avrgirl({ board: { name: 'uno' } }).
To be valid, the board argument must be an object with only the name property defined (ie.  new Avrgirl({ board: { name: 'uno', protocol: 'stk500v1' } }) will not be considered as sparse, and wiil fail latter because of missing properties).
Also adds associated tests.

Coverage increased (+0.8%) to 45.357% when pulling c83f09f81c70ca9156b2d3dd53ff50e9dfda2abe on JordiChauzi:sparse-custom-board into 6ed8d2579c968e9bbb41f911e1d347b878be7160 on noopkat:master.

Coverage increased (+0.8%) to 45.357% when pulling c83f09f81c70ca9156b2d3dd53ff50e9dfda2abe on JordiChauzi:sparse-custom-board into 6ed8d2579c968e9bbb41f911e1d347b878be7160 on noopkat:master.

hey @JordiChauzi thanks for making this functionality more robust and flexible! Love that you also added tests - thank you so much!


Rename remaining occurences of SRML to FRAME

Rename remaining occurences of SRML to FRAME.

@apopiak can you also search for changing module to pallet where appropriate?
Got to be a little careful cause module is correct for Rust modules.

@apopiak can you also search for changing module to pallet where appropriate?
Got to be a little careful cause module is correct for Rust modules.

I'll have a look

@shawntabrizi Had a look and I have no idea how to systematically change that without combing through every location and checking so I'd like to put it in a separate PR at some other point.

[...]
frame/support/procedural/src/lib.rs
102:///   [`KeyFormat`](../srml_support/storage/generator/trait.KeyFormat.html) trait, which

oh actually that first one makes sense. Does the second one make sense?

that seems very outdated, good spot, thanks!

I made a few quick updates, but I agree, module -> pallet is a bigger issue.
So many uses of the word module ingrained in the framework, for example:
/// The metadata of a runtime.
#[derive(Eq, Encode, PartialEq, RuntimeDebug)]
#[cfg_attr(feature = "std", derive(Decode, Serialize))]
pub struct RuntimeMetadataV11 {
	/// Metadata of all the modules.
	pub modules: DecodeDifferentArray<ModuleMetadata>,
	/// Metadata of the extrinsic.
	pub extrinsic: ExtrinsicMetadata,
}

/// The latest version of the metadata.
pub type RuntimeMetadataLastVersion = RuntimeMetadataV11;

/// All metadata about an runtime module.
#[derive(Clone, PartialEq, Eq, Encode, RuntimeDebug)]
#[cfg_attr(feature = "std", derive(Decode, Serialize))]
pub struct ModuleMetadata {
	pub name: DecodeDifferentStr,
	pub storage: Option<DecodeDifferent<FnEncode<StorageMetadata>, StorageMetadata>>,
	pub calls: ODFnA<FunctionMetadata>,
	pub event: ODFnA<EventMetadata>,
	pub constants: DFnA<ModuleConstantMetadata>,
	pub errors: DFnA<ErrorMetadata>,
}

No idea what the long term plan is.

Do we already have an issue for module/pallet?

Runtime check is a false positive, suppose it can be ignored. Question, whether anything else needs addressing before it can be merged?


Next release

First, thanks for sharing your work.
I have been looking at all the commits since last deployment on Nuget and I was wondering if you are planning another release soon. There are lots of new features and fixes that I would like to give them a try.
You have one bug remaining for milestone 0.2.2 (decimal) and it is actually something I would need.
Thanks!

@karlguillotte I am actually finishing up a PR as we speak that handles decimals and nullable primitive types.
Hopefully we can get a new release out this week. @SphtKr I think we can skip 0.2.2 and just release 0.3.0 if you're okay with that?

That is good news. Thanks @csantero
Ah! I am having an issue with null int. It will probably be solved with your PR ;) I will give a try once a new release will be available.
Thanks for the hard work.

Yes I think we can wrap up a few of the in-progress changes and push a 0.3 in a few days. Be advised, there are significant changes to the API in what will be 0.3! This will probably be the case for 0.4 as well, as we're trying to hash out some significant refactors. This is to be expected this early but I know it can be irritating.
I might backport the decimal fix and push it to a 0.2.2 release as well (though this doesn't have to happen before 0.3 is released). I thought it would be nice to get that and #6 to anyone who doesn't have time to integrate the latest changes...I remember feeling burned a lot in earlier versions of Ember Data when this happened.

Also, if you'd like to try prerelease builds, I think you can get the automatically built CI Nuget packages here: https://www.myget.org/feed/Packages/jsonapi

Thanks for the link. I think I will wait for the next release. I am a real newbie with those technologies.
Thanks for the note with the breaking changes. I am starting a new web api, so not much code yet.

Hi @SphtKr ,
I tried to go on the MyGet and I do not see the package. Is it public?
Thanks!

@karlguillote Hmm... Well it's not private or if be paying for it by now. Sorry I haven't gotten the package finalized yet. What I did do for you is push a pre-release version of 0.3.0 to NuGet. You can find that here: https://www.nuget.org/packages/JSONAPI/0.3.0-pre-1 , and https://www.nuget.org/packages/JSONAPI.EntityFramework/0.3.0-pre-1 .
Since, as I said, the docs aren't where they need to be, please ask any questions you want--throw them up on StackOverflow so we'll start building a knowledge base there. I think if you @mention my username there I'll get notified. Or drop a link to the question here.

Thanks @SphtKr  and @csantero for your hard work. I installed them.
I am having an issue, I will post on StackOverflow.


Unable to fetch InRelease for Ubuntu jammy repo

Describe the bug
Trying to install azure-cli from the official repo. This works fine for noble, but when I try with jammy I get the following error:
$ apt update
…
Ign:14 https://packages.microsoft.com/repos/azure-cli jammy InRelease
Err:14 https://packages.microsoft.com/repos/azure-cli jammy InRelease
  Bad header line Bad header data [IP: 2620:1ec:bdf::54 443]
Fetched 5.654 B in 7s (755 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
W: Failed to fetch https://packages.microsoft.com/repos/azure-cli/dists/jammy/InRelease  Bad header line Bad header data [IP: 2620:1ec:bdf::54 443]

$ cat /etc/apt/sources.list.d/azure-cli.sources
Types: deb
URIs: https://packages.microsoft.com/repos/azure-cli/
Suites: jammy
Components: main
Architectures: amd64
Signed-by: /etc/apt/keyrings/microsoft.asc

Related command
apt update
Errors
Failed to fetch https://packages.microsoft.com/repos/azure-cli/dists/jammy/InRelease  Bad header line Bad header data [IP: 2620:1ec:bdf::54 443]
Issue script & Debug output
N/A
Expected behavior
N/A
Environment Summary
azure-cli    2.65.0
Additional context
No response

Thank you for opening this issue, we will look into it.

I can repro. I'm able to get that url with ipv4 and ipv6. Looks like a network issue.

Same error on Ubuntu noble just now :-/
W: Klarte ikke å skaffe https://packages.microsoft.com/repos/azure-cli/dists/noble/InRelease  Ødelagt hodelinje Ødelagte hodedata [IP: 2620:1ec:bdf::53 443]
W: Some index files failed to download. They have been ignored, or old ones used instead.

This fixed it, so must have been a temporarily wrongly downloaded file. Perhaps the repos are hosted on Microsoft technology?
$ sudo rm -rf /var/lib/apt/lists/* && sudo apt-get update


Save applicant status correctly works now

Description
User document now correctly updates on status change. Changing an application's status in admin view no longer breaks the status and submission time displays for the application and applications related to the user affected.
Related Issues
Issue #148
Data in the database affected by the issue is still ruined and needs to be cleaned/fixed.
Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change

[x] No, no existing tests failed, so this is not a breaking change.

Closes #148

resolve the conflict and you should be good to merge!


add Makefile task to setup the cdn-route to forward all headers

Context
See Trello card 338 - while investigating issues with sign-in tokens, we found that all user-agent fields in Logit were empty. Turns out the default set up for the  cdn-route  service (which is how you get custom domains to work in Gov.UK PaaS) is to only forward the Host header to your app: https://docs.cloud.service.gov.uk/deploying_services/use_a_custom_domain/#forwarding-headers
Changes proposed in this pull request
Add a Makefile task to tell the cdn-route service to forward all headers.
Guidance to review
The change is already made on prod, this is more just a record of what I did, so that it can be done again in future if needed

Looks good, as Jake said would be good to add this type of thing to the README

Sure, although TBH I should probably make that a separate task to document all the setup_ tasks in the Makefile (which were only ever run-one-time things like setup_paas_db) in the README. I'll add that to Trello


Improve diagnostics for IDestinationResolver exceptions

When an exception is thrown from IDestinationResolver.ResolveDestinationsAsync, we should catch the exception and rethrow it with context, such as which cluster failed resolution and, if possible, which destination failed to be resolved.

Thanks for the review. Will merge when CI completes


Config generator drops CDATA section

The generated standalone-camel-examples.xml looks like this
        <subsystem xmlns="urn:jboss:domain:camel:1.0">
            <camelContext id="system-context-1">

                		     <route>
                		       <from uri="direct:start"/>
                		       <transform>
                		         <simple>Hello #{body}</simple>
                		       </transform>
                		     </route>

            </camelContext>
        </subsystem>

It should however look like this
		<subsystem xmlns="urn:jboss:domain:camel:1.0">
		   <camelContext id="system-context-1">
		     <![CDATA[
		     <route>
		       <from uri="direct:start"/>
		       <transform>
		         <simple>Hello #{body}</simple>
		       </transform>
		     </route>
		     ]]>
		   </camelContext>
		</subsystem>

It makes me wonder how this is supposed to work. One possibility is that the example template already contains a camel subsystem and the tool does not touch it. Another possibility is that the tool supports system camel context input - more generally, the tool should support the subsystem's config options.

This will be resolved by #619.


Less don't work if your less file ends with /

If your server needs to add a / at the end of your served file less won't work for you raising a
href.match(/([^/]+)$/) is null at line 3094
this is because the regular expression sentence
If you go to this line and change from
var filename = href.match(/([^/]+)$/)[1];
to
var filename = href.match(/([^/]+/?)$/)[1];
it will work as expected. Note how I add /? (this change is tested on less-1.2.2.js)
Can you add this tiny change the the main branch for the next version please?
*Update: change line 3108 from this:
paths: [href.replace(/[\w.-]+$/, '')],
to this:
paths: [href.replace(/[\w.-]+/$/, '')],
for fully use of less with urls ending with /
Thanks a lot!!!

Even if we can discuss if its good or not for the comunity if less "supports" URIs ended with / I understand that perhaps this is a problem for me and not for the rest. I could solve my use case adding a hack to my code
Sorry for the inconvenience


Limiting Published Projects by Current Status in Bullhorn

Are we able to limit published jobs based on their Job Status in Bullhorn?  For example, if a job is moves from "active" to "On Hold", can it be removed from view automatically on the Career Portal?

Hello,
You could use the "additional filter" options to restrict the number of statuses used. You can also customize the portal to exclude that list of statuses.
Please let me know if you have any more questions about this.


Add support for foreign keys to the Forge

In progress. I have created two Unit Tests. I will create more
User guide in progress

Hey @davidgv88 are you going to be able to finish up the changes for these (more unit tests and docs)?

Hi @lonnieezell
In September I return and finish it!


RPA-Power Automate Desktop-Invoke WebService with SharePoint app only - client secret issue with +(plus) sign

RPA-Power Automate Desktop-Invoke WebService with SharePoint app only
Issue: If app secert contains + sign getting client secret invalid.
I am trying to invoke Webservice action to generate token to connect SharePoint Rest API using SharePoint app only. If Client secret contains +(plus) sign it is throwing invalid client secret. I tried to generate secret make sure it should not have "+" sign then it works.
Work around: generated another secret without "+" sign
Please fix this issue. Thanks.
Regards,
Jagan

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

ID: 10a843a8-7e9e-53ef-6955-bd22e62f8e8a
Version Independent ID: fd74890d-8fd9-3354-5584-3cba236902c8
Content: HTTP actions reference - Power Automate
Content Source: articles/desktop-flows/actions-reference/web.md
Service: power-automate
Sub-service: desktop-flow
GitHub Login: @georgiostrantzas
Microsoft Alias: marleon

PM unknown.


Error after upgrading from Ubuntu 20.04 to Ubuntu 22.04

Since updating my server from ubuntu 20.04 to 22.04 i'm getting an error when running the radarr sync. The sonarr sync seems to run fine.
If you need more information, please let me know.
[ERR] An exception occurred during git operations on path: /home/bas/.config/trash-updater/repo
LibGit2Sharp.LibGit2SharpException: could not load ssl libraries
at LibGit2Sharp.Core.Ensure.HandleError(Int32 result) in //LibGit2Sharp/Core/Ensure.cs:line 154
at LibGit2Sharp.Core.Ensure.ZeroResult(Int32 result) in //LibGit2Sharp/Core/Ensure.cs:line 172
at LibGit2Sharp.Core.Proxy.git_clone(String url, String workdir, GitCloneOptions& opts) in //LibGit2Sharp/Core/Proxy.cs:line 275
at LibGit2Sharp.Repository.Clone(String sourceUrl, String workdirPath, CloneOptions options) in //LibGit2Sharp/Repository.cs:line 793
at VersionControl.Wrappers.LibGit2SharpRepositoryStaticWrapper.Clone(String sourceUrl, String workdirPath, CloneOptions options) in D:\a\trash-updater\trash-updater\src\VersionControl\Wrappers\LibGit2SharpRepositoryStaticWrapper.cs:line 8
at VersionControl.GitRepositoryFactory.DeleteAndCloneRepo(String repoUrl, String repoPath, String branch) in D:\a\trash-updater\trash-updater\src\VersionControl\GitRepositoryFactory.cs:line 42
at VersionControl.GitRepositoryFactory.CreateAndCloneIfNeeded(String repoUrl, String repoPath, String branch) in D:\a\trash-updater\trash-updater\src\VersionControl\GitRepositoryFactory.cs:line 27
at TrashLib.Radarr.CustomFormat.Guide.LocalRepoCustomFormatJsonParser.CheckoutAndUpdateRepo() in D:\a\trash-updater\trash-updater\src\TrashLib\Radarr\CustomFormat\Guide\LocalRepoCustomFormatJsonParser.cs:line 68
[INF] Deleting local git repo and retrying git operation...
[1]    257872 segmentation fault (core dumped)  ./trash radarr

Are you running 32 or 64-bit Ubuntu? And which version and architecture of Trash Updater did you download and run? Also please post the debug logs (you can find instructions here).

I'm running Ubuntu 64-bit and i'm using trash-linux-x64 (version 1.8.2)
trash_2022-04-25_22-16-21.log

Did some research and as far as i can see it might be related to the move from openssl 1.1 to openssl 3 Ubuntu made with 22.04

"fixed" the problem by installing the libssl package from Ubuntu 21.10 (https://packages.ubuntu.com/impish-updates/libssl1.1)
After installing that package the updater ran as expected, removing the package broke trash-updater again.
So far no other effects observed, but i don't think this is the best solution. Hope LibGit2Sharp will get updated to support libssl3.0

Thanks a ton for researching this for me. I did about 5 minutes of Googling but I didn't come up with anything. I had a feeling it was something specific to SSL on Ubuntu 22, but I was going to set up a VirtualBox instance with it to verify. Looks like you saved me a lot of trouble, though!
I'm going to leave this issue open until some updates happen to the Troubleshooting wiki page. I'd like to document this issue for others that run into it.

This also happens to me on Fedora Server 36.


Calculate SchdeuleToCloseDeadline from current attempt instead of first attempt

What changed?
Calculate SchdeuleToCloseDeadline from current attempt instead of the first attempt

Why?
This is a bug while we are calculating the ScheduledToCloseDeadline for activity task.

How did you test it?
Unit test.

Potential risks

Pull Request Test Coverage Report for Build 54b7d223-d638-42e6-9255-3d63f61a9dc1

11 of 11 (100.0%)  changed or added relevant lines in 2 files are covered.
26 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.03%) to 74.691%

Files with Coverage Reduction
New Missed Lines
%

internal/internal_workflow_testsuite.go
26
87.16%

Totals

Change from base Build 583e27d1-93c1-4c94-9d56-1b54f1c0db29:
0.03%

Covered Lines:
9367

Relevant Lines:
12541

💛  - Coveralls


add metric plot to viz

closes: #147

What

ports over the metric correlation plot from the existing ui submodule
adds an example notebook for running the new plot

How to Test

if you haven't since the dash updates, create a new dev environment

mamba env create -f environment.yml

run through the example notebook and ensure the new experiment plot works the same as the old one

this plot should replacate the bottom half of the dashboard experience
https://github.com/capitalone/rubicon-ml/blob/147-metric-plot/notebooks/viz/plot-metric-correlation.ipynb

@shania-m

The original graph has different options in the dropdown than the new graph.

yeah those are generated based on the parameters and metrics logged to the experiments. the two examples log different things.

also will we be enabling filtering by the experiment table on the metric plot?

yeah, but that's out of scope of this PR. that'll be done in a followup.

On the same note, will we be keeping the quicklook notebook or updating it with these widgets? If we are getting rid of it, would we be able to use the wine experiment for the plot-metric-correlation notebook?

we'll update it eventually, once the dashboarding is worked out in the followup mentioned above.
things like class and function signatures are still in flux right now while I work out how it all needs to fit together for the dashboarding, which is why I haven't added docstrings or fleshed out any of the new examples yet. I just created this issue https://github.com/capitalone/rubicon-ml/issues/161 for docs and stuff once everything else is done (or at least in a state where it shouldn't majorly change). if there's anything you wanna add to that feel free!


Choose a license

We need to put a license on this. I tend to prefer MIT, BSD, or APL, but I'll defer to your choice. Some guidance on licenses: https://choosealicense.com/

Done. Chose MIT.


copy something from vsc and then paste, why with style and background color

VSCode Version: Code 1.18.1 (929bacba01ef658b873545e26034d1a8067445e9, 2017-11-16T18:23:26.125Z)
OS Version: Darwin x64 17.2.0
Extensions:

Extension
Author (truncated)
Version

gotemplate
cas
0.1.1

pgsql
dou
0.0.8

gitlens
eam
6.1.2

Go
luk
0.6.67

cpptools
ms-
0.14.2

Steps to Reproduce:
use mac book

copy something
paste

Reproduces without extensions: Yes/No

What program are you pasting the content into?

textedit， mail client or any other program of mac OS

please see https://github.com/Microsoft/vscode/issues/21820 for more info.


Enable dual shipping of logs to a secondary endpoint

What does this PR do?
This change enables dual shipping of logs. Add an additional sender with is_reliable: true and the agent will start sending logs to that org/endpoint as well. This additional endpoint wills still be sent to if the main endpoint goes down.  Messages will be retried on retryable errors, back-pressure to the input will be preserved under slow/irregular conditions, and the auditor will be updated to ensure no duplicate logs are sent, and no logs are missed.
NOTE: Right now we are only supporting 1 reliable additional sender. In the future we will support more than one.
The goal of this feature is to ensure all logs will make it to at least one of the two endpoints and none are missed.
The behavior is as follows:

if both endpoints are alive

logs will be sent to both endpoints equally.
if one slows down (due to network conditions/etc) both will slow down to ensure logs are sent to both

if ether one of the endpoints goes down

the other endpoint will continue to send logs, update the auditor, and ensure none are missed.
If the failing endpoint recovered, logs will begin to flow to that one again, but all logs between the failure and recovery will be lost to that endpoint.

if both endpoints go down

the whole logs pipeline will block until one of them becomes alive to ensure no logs are missed in the downtime.

Additional Notes
With the HTTP sender this will incur a significant CPU increase. Another change is in the works to mitigate this.
 Warning if you use DD_LOGS_CONFIG_CONTAINER_COLLECT_ALL you will create a feedback loop from the mock intake containers. I'd recommend spawning a dedicated logging container.

Watch the logs flow in both intakes.

Kill one of the intakes

make sure logs are still flowing to the other one

Kill the second intake (both are now dead)

check agent status to see that # of bytes read is not increasing (pipeline should be blocked)

Restart one of the intakes - logs should start flowing
restart the other intake - logs should start flowing.

App QA
Now instead of using mock intakes - use two real Datadog intakes. You will need 2 API keys each from different orgs.
docker run -d --name dd-agent \
    --net=host \
    -e DD_API_KEY="<API_KEY>"\
    -e DD_LOGS_ENABLED=true \
    -e DD_LOGS_CONFIG_USE_HTTP=true \
    -e DD_LOGS_CONFIG_ADDITIONAL_ENDPOINTS="[{\"api_key\": \"<ANOTHER_API_KEY>\", \"Host\": \"agent-intake.logs.datadoghq.com\", \"Port\": 10516, \"is_reliable\": true}]" \
    -v /var/run/docker.sock:/var/run/docker.sock:ro \
    -v /proc/:/host/proc/:ro \
    -v /sys/fs/cgroup/:/host/sys/fs/cgroup:ro \
    -v /var/lib/docker/containers:/var/lib/docker/containers:ro \
   <RC_IMAGE>

Stream some logs and watch the livetail in both orgs for the logs.
Checklist

[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] The need-change/operator and need-change/helm labels has been applied if applicable.
[ ] The appropriate team/.. label has been applied, if known.
[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] The config template has been updated if applicable.

Note: Adding GitHub labels is only possible for contributors with write access.

what happens if endpoint A fails very slowly, e.g. the HTTP sender for endpoint A makes the HTTP client reach its timeout for every request? It seems to me that in this case endpoint B would end up being throttled by endpoint A (because the inputChan for sender A would only be drained at the rate of the HTTP timeouts), whereas instead we'd need the data to continue to be sent to endpoint A. Am I missing something though?

If a sender starts failing we stop trying to write payloads to its input in a blocking way, and instead try to non-blocking insert them. Since all of these channels are buffered we have some room to enqueue future payloads while one is already in flight (before it fails). I suppose there is a possibility a long timeout could cause a temporary block until it falls into an error state, but this is a good thing as to prevent log loss for both destinations.
I can test this specific case though to give you a more concrete answer.

with the current defaults, how long (or for how many payloads) can the main endpoint fail before there's loss of data for the main endpoint? I'm mostly considering cases where there could be short network (or logs intake) blips on the main endpoint, which could cause loss of data (only when dual shipping is enabled). That'd be undesirable overall, although this seems unavoidable to me.

It really depends on how fast you are writing logs. Our channels buffer 100 messages by default - so we would start dropping logs to a single failing endpoint pretty quickly in most cases I would think. This is a tradeoff of our memory footprint (which is very small due to our small internal buffers).

If a sender starts failing we stop trying to write payloads to its input in a blocking way, and instead try to non-blocking enqueue them. I suppose there is a possibility a long timeout could cause a temporary block until it falls into an error state, but this is a good thing as to prevent log loss for both destinations.
I can test this specific case though to give you a more concrete answer.

Thanks for the explanation! Yes I think it's worth testing. As a follow-up, let's take some time to write down the design of this logic, the tradeoffs we're making, and under which conditions the logic ends up dropping logs for one of the endpoints. Typically, we may not want to treat the main and backup endpoints "equally" as this PR does (for example maybe slowness/errors on the backup endpoint should not affect the main endpoint at all) but it's difficult to have this conversation in this PR.

It really depends on how fast you are writing logs. Our channels buffer 100 messages by default - so we would start dropping logs to a single failing endpoint pretty quickly in most cases I would think. This is a tradeoff of our memory footprint (which is very small due to our small internal buffers).

OK! Long-term, we'll want to buffer more, since indeed 100 messages means that the agent will likely drop logs for one of the endpoints on very short network blips. Let's track this as a follow-up item as well.

Another thing we should probably follow up on later: how this affects telemetry/expvars when dual-shipping is enabled, and what visibility can be improved (typically, it'd be important to get visibility on how many logs are dropped for each of the endpoints)


Add MP and Tomislav to Tweetdeck access for ETHMagicians

Link here: https://ethereum-magicians.org/t/council-of-paris-call-for-rings-and-participants/2588

Ok, you have been added. Let me know if it works.

Hi! i only use browser for @ethberlin so if you can add that one, great

I'll close this issue, assuming @jpitts added EthBerlin as well.


Circle-CI broken on latest commit (#294)

Describe the bug
A clear and concise description of what the bug is.
The automated CircleCI build/install/test failed after #294 was merged to master.  I'm not sure what exactly failed, I think installation, even though the installation script returned 0 :
To Reproduce
Steps to reproduce the behavior:
See error https://circleci.com/gh/tesch1/OpenVnmrJ/313

Fixed by PR #299


Is there a guide for adding new sensor types?

I want to use some sensor chip that is not on the supported list, how do I add support for it and keep the code clear? What are the source code changes that must be made?

There is currently no documentation that shows what code needs to be changed / added to add a new sensor.
I think short:

Look for a lib that works with the sensor and our license. (output accel and or quat, or unfused data)
Add a #define in src/consts.h for the new IMU
Create a src/sensors/*sensor.h src/sensors/*sensor.cpp for your new sensor.
If you need to add stuff in src/configuration/CalibrationConfig.h src/configuration/CalibrationConfig.cpp and src/configuration/Configuration.cpp
Add in src/sensors/SensorManager.cpp the check for the new Sensor
Write README.md


*bool is not supported in buildEqualsClause

There is an issue with boolean conditions in buildEqualsClause: when bool fields are initialized, they default to "false" if a condition is not present, which Is not necessarily desirable behavior. I suggest to add *bool support and ignore those field if they're nil.

Thanks for filing the issue. I will schedule this to be done in next couple of weeks. Sorry for the delay in response!

Closed by https://github.com/forcedotcom/go-soql/pull/12


gtk-layer-shell: 0.1.0 -> 0.2.0

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/wmww/gtk-layer-shell/releases.
meta.description for gtk-layer-shell is: "A library to create panels and other desktop components for Wayland using the Layer Shell protocol"
meta.homepage for gtk-layer-shell is: ""
meta.changelog for gtk-layer-shell is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.2.0 with grep in /nix/store/yj5nqyfvvc765jv4r7rqq8xc5yjbz190-gtk-layer-shell-0.2.0

directory tree listing: https://gist.github.com/04a3e9e48a5bf85d7c4020f8c3a13996

du listing: https://gist.github.com/d3043174ac87a6e59684336f43d6862a

Rebuild report (if merged into master) (click to expand)

8 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
2 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
gtk-layer-shell
waybar

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/yj5nqyfvvc765jv4r7rqq8xc5yjbz190-gtk-layer-shell-0.2.0 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A gtk-layer-shell https://github.com/r-ryantm/nixpkgs/archive/2d84afa72d1e4b64601a9a9db246a4004b09ab53.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/yj5nqyfvvc765jv4r7rqq8xc5yjbz190-gtk-layer-shell-0.2.0
ls -la /nix/store/yj5nqyfvvc765jv4r7rqq8xc5yjbz190-gtk-layer-shell-0.2.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

2 packages built:

gtk-layer-shell
waybar

Maintainer pings
cc @eonpatapon for testing.

Asked about the relicensing in https://github.com/wmww/gtk-layer-shell/pull/40#issuecomment-670989893

I don't know if meta.changelog needs to be something more specific, but I noticed it's empty and I do now have a changelog here: https://github.com/wmww/gtk-layer-shell/blob/master/CHANGELOG.md

For projects that are on GitHub and include the changes in GitHub releases there is no need to set meta.changelog, we already link to the release. Though the changelog files are still useful.
I opened an issue against our updater: https://github.com/ryantm/nixpkgs-update/issues/230

Updated the license field and also cleaned up the package a bit and enabled docs.


Cleaning up student planning

Closes #332

Newest version where waste types are grouped based on putting garbage bin inside/outside


Fix off-by-one error in substring creation.

Now we can build //docs/... in rules_typescript
and rules_nodejs on Linux too, where sandboxing is
enabled by default and where the previously buggy
code path is used.
See https://github.com/bazelbuild/skydoc/issues/58

https://github.com/bazelbuild/skydoc/commit/d9b3e3b743f00bf00ba8d1306c56a477ec50fc4e is actually buggy, this PR fixes that.

/cc @laurentlb


Make Responsiveness in few places

Make Responsiveness in following places:

[ ] CustomCarousel Element on Homepage
[x] Settings Page
[x] Tags in Userprofile

@ajajaj2807 Please make carousel element responsive. Direct CSS isn't helping. Use Grid system if possible. Again I am asking you because u wrote this


Overlapping enums?

When using external libs (i.e. opengl) there are functions, that take different sets of the same constants as parameters.
Example: function f1 can take a or b as parameter, function f2 can take a and c as parameter.
Something like this using enums won't work:
(def-enum T1 extern int (a b))
(def-enum T2 extern int (a c))

(def f1 (fn extern-c void ((x T1))))
(def f2 (fn extern-c void ((x T2))))

So enums may not be a good choice in such cases. Would it be best in this case to define a general enum for all overlapping constants, and handling the type-checking in macro-versions of the functions, or may something like overlapping enums be implemented into the language?
So the chosen function won't dispatch on the value type, but the chosen value will dispatch on the function parameter type instead.

With the original version of enums this wasn't a problem.
I think defining enums in own namespaces seems a good solution.


executor: fix endianess of size of received flatbuffers root table

Flatbuffers represents each scalar in little-endian format (https://flatbuffers.dev/flatbuffers_internals.html). Therefore, the size of the received root table must be converted to the host endianness format before its first usage.
Fixes: e16e2c9a4cb6 ("executor: add runner mode")

This code needs to build for all 3 *BSD and Fuchsia.
Please check that header/function at least seems to exist on BSDs.


Attempted import error: 'ViewPropTypes' is not exported from 'react-native-web'.

I have one extra issues with react-native-web. Some interfaces are changed on RN-web and RN.  And now I have this problem with 'ViewPropTypes' is not exported from 'react-native-web'. ->
/node_modules/react-native-smooth-slider/src/Slider.js Attempted import error: 'ViewPropTypes' is not exported from 'react-native-web'.
Could you please provide instruction how to some this?
Here is the problem - https://github.com/necolas/react-native-web/issues/1537#issuecomment-619969653

Just see this issue today, don't know why github not notify me that there is a new issue.
You can ref to this https://github.com/reactrondev/react-native-web-swiper/issues/41#issuecomment-685207381

Just see this issue today, don't know why github not notify me that there is a new issue.
You can ref to this https://github.com/reactrondev/react-native-web-swiper/issues/41#issuecomment-685207381


removed redundant code in GSM8KDataset.load method.

Removed redundant code in GSM8KDataset.load method.

Thanks for your carefulness!


Test creating users for Kibana.

@Ak-sky Kibana doesn't have the concept of users. It simply uses the Elasticsearch users. So in theory, the users passed with the users input variable should be able to log in to kibana


add strip_whitespace option for ConstrainedStr and constr

@samuelcolvin updated, please check

Thanks a lot, I'll try and merge a couple of other PRs which are finished and deploy in the next couple of days.

And I will try to implement more things from #161 😃


Source code anchors are wrong sometimes

Originally opened at CodePlex by xionghuaidong
I'm trying to learn F#. I found it interesting, but the following bug is quite annoying.
Sometimes, when multiple errors happen in F# Interactive, source code anchors in error messages are wrong. They point to the source code of some previous error. See the following screenshot.
Image
My F# is part of Microsoft Visual Studio Professional 2013 English Version 12.0.30723.00 Update 3, and my operating system is Windows 8.1 Professional Simplified Chinese version.
file attachments
image001.pngI'm trying to learn F#. I found it interesting, but the following bug is quite annoying.
Sometimes, when multiple errors happen in F# Interactive, source code anchors in error messages are wrong. They point to the source code of some previous error. See the following screenshot.
Image
My F# is part of Microsoft Visual Studio Professional 2013 English Version 12.0.30723.00 Update 3, and my operating system is Windows 8.1 Professional Simplified Chinese version.

comments
brodyberg wrote Oct 10, 2014 at 11:51 AM [x]
That is indeed odd. I see that if I continue incrementing FSI will continue to report the error as with 2F:
stdin(1,1): error FS1156: This is not a valid numeric literal. Sample formats include 4, 0x4, 0b0100, 4L, 4UL, 4u, 4s, 4us, 4y, 4uy, 4.0, 4.0f, 4I.
2F;;
2F;;
^^
stdin(2,1): error FS1156: This is not a valid numeric literal. Sample formats include 4, 0x4, 0b0100, 4L, 4UL, 4u, 4s, 4us, 4y, 4uy, 4.0, 4.0f, 4I.
3F;;
2F;;
^^
stdin(2,1): error FS1156: This is not a valid numeric literal. Sample formats include 4, 0x4, 0b0100, 4L, 4UL, 4u, 4s, 4us, 4y, 4uy, 4.0, 4.0f, 4I.
4F;;
2F;;
^^
stdin(2,1): error FS1156: This is not a valid numeric literal. Sample formats include 4, 0x4, 0b0100, 4L, 4UL, 4u, 4s, 4us, 4y, 4uy, 4.0, 4.0f, 4I.
5F;;
2F;;
^^
stdin(2,1): error FS1156: This is not a valid numeric literal. Sample formats include 4, 0x4, 0b0100, 4L, 4UL, 4u, 4s, 4us, 4y, 4uy, 4.0, 4.0f, 4I.
What's even more interesting is this:
{ "foo" };;
2F;;
^^^^^^^^^

(my quick repro investigation, from earlier internal mail)
This does appear to be very annoying… for a certain batch of lexing errors, the reported range from LexBuffer simply does not increment for each new line.
Result is that error messages and “console squiggles” are now permanently (for the rest of the session) out of alignment with the culprit code that gets printed
Microsoft (R) F# Interactive version (private)
Copyright (c) Microsoft Corporation. All Rights Reserved.

For help type #help;;

> 1F ;;

  1F ;;
  ^^

stdin(1,1): error FS1156: This is not a valid numeric literal. Sample formats include 4, 0x4, 0b0100, 4L, 4UL, 4u, 4s, 4
us, 4y, 4uy, 4.0, 4.0f, 4I.
> 99999B ;;

  99999B ;;
  ^^^^^^

stdin(2,1): error FS1156: This is not a valid numeric literal. Sample formats include 4, 0x4, 0b0100, 4L, 4UL, 4u, 4s, 4
us, 4y, 4uy, 4.0, 4.0f, 4I.
> --2 ;;

  99999B ;;
  --^

stdin(2,3): error FS1208: Invalid prefix operator
> let x = 20 ;;

val x : int = 20

> x.NoSuchMember ;;

  let x = 20 ;;
  --^^^^^^^^^^^^

stdin(4,3): error FS0039: The field, constructor or member 'NoSuchMember' is not defined

i'll try to fix this one

minimal repro:

> gg;;

  gg;;
  ^^

stdin(1,1): error FS0039: The value or constructor 'gg' is not defined
> 1F;;

  1F;;
  ^^

stdin(2,1): error FS1156: This is not a valid numeric literal. Sample formats in
clude 4, 0x4, 0b0100, 4L, 4UL, 4u, 4s, 4us, 4y, 4uy, 4.0, 4.0f, 4I.
> hh;;

  1F;;
  ^^

stdin(2,1): error FS0039: The value or constructor 'hh' is not defined
>

now every other evaluation has an invalid -1 line offset.
The offset is cumulative (evaluate 2F add another -1 offset)
The error doesn't occur if the lex error is the first of the session
> 1F;;

  1F;;
  ^^

stdin(1,1): error FS1156: This is not a valid numeric literal. Sample formats in
clude 4, 0x4, 0b0100, 4L, 4UL, 4u, 4s, 4us, 4y, 4uy, 4.0, 4.0f, 4I.
> hh;;

  hh;;
  ^^

stdin(2,1): error FS0039: The value or constructor 'hh' is not defined
> gg;;

  gg;;
  ^^

stdin(3,1): error FS0039: The value or constructor 'gg' is not defined

Pity! This bug is not fixed in VS2015!

I'm closing this - it's a really minor cosmetic bug to do with numeric literal forms.


Separate Skin and chroma sections/hotkeys?

Some champions have overwhelming number of skins and chromas. It would be nice to have the skins and chromas be in two different drop-down boxes, and then allow to two different hotkeys to change each.

Closing due to Vanguard coming to League of Legends.


Update CocoaPopover to accept UIPopoverArrowDirection

Hi Vatsel,
Thanks for creating and maintaining SwiftUIX.
The previous CocoaPopover API only allows setting a single arrow direction. Which is limiting for some use cases and hence why UIPopoverArrowDirection is defined as an OptionSet.
What do you think?

@leotumwattana thanks for the PR! Could you rework this to accept an array/set of Edges? I don't want to expose UIPopoverArrowDirection in the API surface.

Updated to accept Edge.Set. See if you want me to change anything else?
My two cents: I think exposing UIPopoverArrowDirection is more efficient? Removes the need to process conversion. Especially since we are in fact bridging to UIPopoverPresentation.
However, your project, so go with what you want.
Cheers!

@leotumwattana the CocoaPopover APIs are intended to be cross-platform (proper macOS support is pending).

I see. Then going with Edge.Set makes sense. Thanks for the work once again.


pulp::simd_type! generates a missing import error

I'm guessing the macro uses MaybeUninit directly instead of a fully qualified path like std::mem::MaybeUninit or core::mem::MaybeUninit
Fix is straightforward on our end but could be nice for people who use this macro in the wild :)
error[E0412]: cannot find type `MaybeUninit` in this scope
   --> tfhe-ntt/src/lib.rs:135:1
    |
135 | / pulp::simd_type! {
136 | |     struct V4IFma {
137 | |         pub sse: "sse",
138 | |         pub sse2: "sse2",
...   |
157 | |     }
158 | | }
    | |_^ not found in this scope
    |
    = note: this error originates in the macro `pulp::simd_type` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider importing this union
    |
78  + use std::mem::MaybeUninit;
    |

thanks. gonna fix it soon, nice to see you again btw 😄

thanks. gonna fix it soon, nice to see you again btw 😄

Likewise 😄 👋

btw, if you send me a DM on discord, i have some multithreading optimizations you might be interested in chatting about

definitely ! Same handle :)

I meant, I don't think I have your handle but mine's the same

fixed