[DO NOT MERGE]: consider changing math optimizations

includes ECL #601: Implemented Kahan summation algorithm for adding process noise
https://github.com/PX4/ecl/pull/601

Overall flash differences from current master on px4_fmu-v5.

@PX4/testflights could you give this one quick flight on a single platform with a comparison to current master?

Questions

Does this result in any major performance regressions?
Can we convince ourselves that this is the strictly safer thing to do?

Note this also has the Kahan summation, so I expect the flight performance to be a little different, since the bias variance estimates will actually grow now unless there is data fused that reduces them. The CPU load will be particularly interesting to track. Note the places with big code size differences will probably also be the places with big performance differences - mostly stuff with matrix oeprations that can't have common calculations factored out or cancelled now. It depends if it is in a hot loop or not.
There are also some risks, for example the optimization would save us from 0/0 situations since the variables would be cancelled. We'll have to keep an eye out for this.

SITL testing works fine for me, not noticeable changes.

I would merge Kahan summation first, then evaluate the math flags separately.

The issue is that the Kahan summation is optimized out by the math flags, so is 'implicitly disabled' unless we do workarounds in the ECL.

I'm aware, but I would do that locally first.

Tested on Pixhawk 4 v5
Modes Tested
Notes: Acro mode has a stabilization assistance feeling while flying, it does not feel like full acro mode.
Procedure: tested on acro mode only
acro Mode
https://review.px4.io/plot_app?log=5f79e673-f4f3-41e3-a1c1-da3205ca4437

@PX4/testflights please exhaustively test this across all vehicles.

Tested on PixRacer V4:
Modes Tested
Position Mode: Good.
Altitude Mode: Good.
Stabilized Mode: Good.
Mission Plan Mode (Automated): Good.
RTL: Good.
- Procedure
Arm and Take off in position mode, after flying for approximately one minute, switched to altitude then stabilized mode proceed to switch to mission plan mode then make sure that vehicle follows all waypoints as shown in QGC, once completed all waypoin activate RTL and see landing behaviour.
- Notes
No issues noted, good flight in general.
Logs
- PR 12096
https://review.px4.io/plot_app?log=aa1756f3-2994-4adc-bca0-2f0c271
Log Comparison to Master:
https://review.px4.io/plot_app?log=1c2fcafa-9b0f-41a2-8435-8c3350c8cfb8
Tested on PixRacer V4:
Modes Tested:
-Acro mode.
Procedure:
Armed and took-off in acro mode, while in the air performed flips and rolls for about a minute, then proceeded to land.
Notes: In Acro mode, while flying, it does not feel like full acro mode.
In rotation, the vehicle hesitates when passing through its level upright position in what seems like an attempt to stabilize.
Flying acro with other flight controllers would produce a smooth pass through this position.
Log:
https://review.px4.io/plot_app?log=a21269c1-081e-4379-8ce8-00c3841372bc

Tested on PixRacer V4:
Modes Tested
Position Mode: Good.
Altitude Mode: Good.
Stabilized Mode: Good.
Mission Plan Mode (Automated): Good.
RTL: Good.
- Procedure
Arm and Take off in position mode, after flying for approximately one minute, switched to altitude then stabilized mode proceed to switch to mission plan mode then make sure that vehicle follows all waypoints as shown in QGC, once completed all waypoin activate RTL and see landing behaviour.

Notes
No issues noted, good flight in general.

Logs

PR 12096
https://review.px4.io/plot_app?log=aa1756f3-2994-4adc-bca0-2f0c271

Log Comparison to Master:
https://review.px4.io/plot_app?log=1c2fcafa-9b0f-41a2-8435-8c3350c8cfb8
Tested on PixRacer V4:
Modes Tested:
-Acro mode.
Procedure:
Armed and took-off in acro mode, while in the air performed flips and rolls for about a minute, then proceeded to land.
Notes: In Acro mode, while flying, it does not feel like full acro mode.
In rotation, the vehicle hesitates when passing through its level upright position in what seems like an attempt to stabilize.
Flying acro with other flight controllers would produce a smooth pass through this position.
Log:
https://review.px4.io/plot_app?log=a21269c1-081e-4379-8ce8-00c3841372bc
Tested on Pixhawk 2 Cube V3:
Modes Tested
Position Mode: Good.
Altitude Mode: Good.
Stabilized Mode: Good.
Mission Plan Mode (Automated): Good.
RTL: Good.
- Procedure
Arm and Take off in position mode, after flying for approximately one minute, switched to altitude then stabilized mode proceed to switch to mission plan mode then make sure that vehicle follows all waypoints as shown in QGC, once completed all waypoin activate RTL and see landing behaviour.
- Notes
No issues noted, good flight in general.
Logs
https://review.px4.io/plot_app?log=c87d3e56-c34a-4562-af1e-3426e5ab4648
Log Comparison to Master:
https://review.px4.io/plot_app?log=29af6d61-61ac-49c6-a71e-df221eef0ac3
Tested on Pixhawk 2 Cube V3:
Modes Tested:
-Acro mode.
Procedure:
Armed and took-off in acro mode, while in the air performed flips and rolls for about a minute, then proceeded to land.
Notes: In Acro mode, while flying, it does not feel like full acro mode.
In rotation, the vehicle hesitates when passing through its level upright position in what seems like an attempt to stabilize.
Flying acro with other flight controllers would produce a smooth pass through this position.
Log:
https://review.px4.io/plot_app?log=18af06e1-a19c-4037-8932-fc77dc4e4330

Tested on Pixhawk 4 mini v5
Modes Tested

Position Mode: Good.
Altitude Mode: Good.
Stabilized Mode: Good.
Mission Plan Mode (Automated): Good.
RTL (Return To Land): Good.
Acro: Good.

Procedure

Arm and Take off in position mode, after flying for approximately one minute, switched to altitude then stabilized mode proceed to switch to mission plan mode then make sure that vehicle follows all waypoints as shown in QGC, once completed all waypoint trigger RTL and see landing behavior.

For Acro mode: Armed and took-off in acro mode, while in the air performed flips and rolls for about a minute, then proceeded to land.

Notes

No issues noted, good flight in general.
For Acro mode: While flying, it does not feel like full acro mode.
In rotation, the vehicle hesitates when passing through its level upright position in what seems like an attempt to stabilize.
Flying acro with other flight controllers would produce a smooth pass through this position.

Logs

Acro
https://review.px4.io/plot_app?log=6fbb0cf5-a8fa-4552-a940-f80b589faaf8

Tested on Pixhawk Pro v4
Modes Tested

Position Mode: Good.
Altitude Mode: Good.
Stabilized Mode: Good.
Mission Plan Mode (Automated): Good.
RTL (Return To Land): Good.
Acro: Good.

Procedure

Arm and Take off in position mode, after flying for approximately one minute, switched to altitude then stabilized mode proceed to switch to mission plan mode then make sure that vehicle follows all waypoints as shown in QGC, once completed all waypoint trigger RTL and see landing behavior.

For Acro mode: Armed and took-off in acro mode, while in the air performed flips and rolls for about a minute, then proceeded to land.

Notes

No issues noted, good flight in general.
For Acro mode: While flying, it does not feel like full acro mode.
In rotation, the vehicle hesitates when passing through its level upright position in what seems like an attempt to stabilize.
Flying acro with other flight controllers would produce a smooth pass through this position.

Logs

PR 12096
https://review.px4.io/plot_app?log=3f2c5b69-d586-47f1-bc53-017384d600e2
Acro
https://review.px4.io/plot_app?log=6e167ab8-4d2f-4458-8908-872df4bfae43

Tested on NXP FMUK66 v3
Modes Tested

Position Mode: Good.
Altitude Mode: Good.
Stabilized Mode: Good.
Mission Plan Mode (Automated): Good.
RTL (Return To Land): Good.

Procedure
Arm and Take off in position mode, after flying for approximately one minute, switched to altitude then stabilized mode proceed to switch to mission plan mode then make sure that vehicle follows all waypoints as shown in QGC, once completed all waypoint trigger RTL and see landing behavior.
Notes
Vehicle felt more responsive, smoother and more stable; good flight in general.
Logs

PR 12096
https://review.px4.io/plot_app?log=c6daf4c7-fd04-47d1-a074-db1f7b9d2d9a

This is looking good so far. New plan, I'll update the PR to bring in only the optimization flag changes, which will then put https://github.com/PX4/ecl/pull/601 in a position where they can bring in the change when @priseborough is ready.

Tested on PixRacer V4:
Flight Card 1
Modes Tested:
Position Mode: Good.
Altitude Mode: Good.
Stabilized Mode: Good.
Procedure:
Arm in position mode, check take off behavior (Vehicle should stay on the ground as long as the throttle stick is at the middle or below, and start to ascend smoothly as long as throttle stick as above the middle.), the land and disarm.
Same procedure was repeated with Altitude and Stabilized mode.
Notes:
No issues were noted, good flight in general.
Flight Card 2
Modes Tested
Mission Plan Mode (Automated): Good.
RTL (Return To Land): Good.
Procedure
Arm and Take off in mission plan mode then make sure that vehicle follows all waypoints as shown in QGC, once completed all waypoint see landing behavior.
Note:
No issues were noted, good flight in general.
Flight Card 3
Modes Tested
Position Mode: Good.
Mission Plan Mode (Automated): Good.
RTL (Return To Land): Good.
Procedure
Arm and Take off in position mode, after flying for approximately one minute, switched to mission plan mode then make sure that vehicle follows all waypoints as shown in QGC, once completed all waypoint see landing behavior.
Note:
No issues were noted, good flight in general.
Logs:
Flight card 1:  https://review.px4.io/plot_app?log=63ea5b4e-d8df-49cf-a25b-ad5495395a76
Flight card 2:  https://review.px4.io/plot_app?log=7c6f8293-2489-4784-8823-df034c5d17a2
Flight card 3:  https://review.px4.io/plot_app?log=e195ddd3-b27b-4d66-a010-1759d23809cf

Tested on Pixhawk Pro v4
Flight Card 1
Modes Tested:

Position Mode: Good.
Altitude Mode: Good.
Stabilized Mode: Good.

Procedure:
Arm in position mode, check take off behavior (Vehicle should stay on the ground as long as the throttle stick is at the middle or below, and start to ascend smoothly as long as throttle stick as above the middle.), the land and disarm.
Same procedure was repeated with Altitude and Stabilized mode.
Notes:
No issues were noted, good flight in general.
Flight Card 2
Modes Tested

Mission Plan Mode (Automated): Good.
RTL (Return To Land): Good.

Procedure
Arm and Take off in mission plan mode then make sure that vehicle follows all waypoints as shown in QGC, once completed all waypoint see landing behavior.
Note:
No issues were noted, good flight in general.
Flight Card 3
Modes Tested

Position Mode: Good.
Mission Plan Mode (Automated): Good.
RTL (Return To Land): Good.

Procedure
Arm and Take off in position mode, after flying for approximately one minute, switched to mission plan mode then make sure that vehicle follows all waypoints as shown in QGC, once completed all waypoint see landing behavior.
Note:
No issues were noted, good flight in general.
Flight Card 4
Modes Tested

Position Mode: Good.
Failsafe RTL (Return To Land): Not returning after RC shutdown.

Note:
No issues were noted, good flight in general.
Logs:

Flight Card 1: https://review.px4.io/plot_app?log=913c24c2-fcfa-48f6-aeb2-b21f2c159c29
Flight Card 2: https://review.px4.io/plot_app?log=d50c17e6-4419-4846-a028-dd06a2f064e4
Flight Card 3: https://review.px4.io/plot_app?log=a312d9d1-ac90-4218-bd21-13b9c46ab6b6
Flight Card 4: https://review.px4.io/plot_app?log=a3cd52f5-3ee1-4882-9078-6a28b7d46472

Tested on Pixhawk 4 mini v5
Flight Card 1
Modes Tested:

Position Mode: Good.
Altitude Mode: Good.
Stabilized Mode: Good.

Procedure:
Arm in position mode, check take off behavior (Vehicle should stay on the ground as long as the throttle stick is at the middle or below, and start to ascend smoothly as long as throttle stick as above the middle.), the land and disarm.
Same procedure was repeated with Altitude and Stabilized mode.
Notes:
No issues were noted, good flight in general.
Flight Card 2
Modes Tested

Mission Plan Mode (Automated): Good.
RTL (Return To Land): Good.

Procedure
Arm and Take off in mission plan mode then make sure that vehicle follows all waypoints as shown in QGC, once completed all waypoint see landing behavior.
Note:
No issues were noted, good flight in general.
Flight Card 3
Modes Tested

Position Mode: Good.
Mission Plan Mode (Automated): Good.
RTL (Return To Land): Good.

Procedure
Arm and Take off in position mode, after flying for approximately one minute, switched to mission plan mode then make sure that vehicle follows all waypoints as shown in QGC, once completed all waypoint see landing behavior.
Note:
No issues were noted, good flight in general.
Flight Card 4
Modes Tested

Position Mode: Good.
Failsafe RTL (Return To Land): Not returning after RC shutdown.

Note:
No issues were noted, good flight in general.
Logs:

Flight Card 1: https://review.px4.io/plot_app?log=2832fce5-062f-4cf0-b9de-fc22e55f4e95
Flight Card 2: https://review.px4.io/plot_app?log=22f07599-5e3f-4328-89b2-77801de30399
Flight Card 3: https://review.px4.io/plot_app?log=def44909-756a-42b3-93ea-7b1cc19648a3
Flight Card 4: https://review.px4.io/plot_app?log=6fa32b26-6bc8-46c4-9cd2-ca00cb054aa8

Tested on Pixhawk 4 mini v5 v-tol convergence
Modes Tested:
Position Mode: perfect
Stabilized Mode: perfect
transition: perfect
log:
https://review.px4.io/plot_app?log=a5c65240-61c9-40dd-872f-96a761cf7cdf
mission mode: perfect
transition: perfect
land: perfect
log:
https://review.px4.io/plot_app?log=22a506bb-1eec-401e-9764-e945440bc36d

@PX4/testflights can you do another acro test with the latest build? The Kahan stuff has been removed, I want to see if that fixes the feeling of stabilization when exactly horizontal in acro. It needs to be compared to master to see if it feels different.

Tested on Pixhawk pro:
Modes tested: Acro mode
Notes: In Acro mode, while flying, it does not feel like full acro mode. In rotation, the vehicle hesitates when passing through its level upright position in what seems like an attempt to stabilize. Same behavior as before noted. No improvements noted.
On master and Acro mode is better but still feels like it has assistance.
Flying acro with other flight controllers would produce a smooth pass through this position.
Acro mode test log:
https://review.px4.io/plot_app?log=ba7bce05-4718-4ff8-bec9-8404683d823e
https://review.px4.io/plot_app?log=21ec7361-08e6-4684-8835-b0fbc13bdcbb
Master:
https://review.px4.io/plot_app?log=1fdeec0d-604f-473f-8e63-e40ff6e5d316
Tested on Pixhawk4 mini v5
Modes Tested: Acro mode
Notes: In Acro mode, while flying, it feels much better than before,  but still it does not feel like full acro mode. You can still note slight assistance to attempt to stabilize. It definitely improved, noted lock-in when rotating.
On master, Acro mode is better but you can still note slight assistance.
PR Acro mode test log:
https://review.px4.io/plot_app?log=ce154708-36a4-4917-b5ba-efdcd25b40f2
https://review.px4.io/plot_app?log=daee9d62-2a99-45ea-8421-91a7d706359d
Master test log:
https://review.px4.io/plot_app?log=c11dda1a-4632-4656-be76-7a75a2faf964

Notes: In Acro mode, while flying, it still does not feel like full acro mode. In rotation, the vehicle hesitates when passing through its level upright position in what seems like an attempt to stabilize. Same behavior as before noted, no improvements noted.

@dannyfpv please enable Airmode and let me know if it still feels off. The rate tracking is also not great on the log I see. Can you tune it? Make sure to increase the I gains.


What am I doing wrong ?

<?php
require  __DIR__ . '/vendor/autoload.php';

  $camo = new WillWashburn\Phpamo\Client();
  $camo->setDomain('https://mydomain.com/camoproxy/');
  $camo->setCamoKey('mycamokey');

  $test = $camo->proxy('someurl'); // returns the proxy url

 print $test;
?>

When I run hhvm test.php it outputs : Fatal error: Class undefined: WillWashburn\Phpamo\Client in /usr/local/src/camotest/test.php on line 4

I just pushed up another version, I had the namespace wrong. Sorry if that wasted your time and thanks for the heads up!


Oct 03 2023 - Regulation Innovation SIG Meeting

Regulation Innovation SIG
Date
Oct 03 2023 - 12pm EST / 5pm GMT
Untracked attendees

Fullname, Affiliation, (optional) GitHub username
...

Meeting notices

FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact<EMAIL_ADDRESS>with any questions.

FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

[ ] Convene & roll call (5mins)
[ ] Display FINOS Antitrust Policy summary slide
[ ] Review Meeting Notices (see above)
[ ] Approve past meeting minutes
[ ] ESG Data Industrialization project & hackathon proposal (PJ Di Giammarino)
[ ] ...
[ ] AOB, Q&A & Adjourn (5mins)

Decisions Made

[ ] Decision 1
[ ] Decision 2
[ ] ...

Action Items

[ ] Action 1
[ ] Action 2
[ ] ...

WebEx info

Meeting link: https://finos.webex.com/finos/j.php?MTID=m6be3cd5cdc56622e15e74fbd30e7253c
Meeting number:<PHONE_NUMBER>
Password: d9kKJPdX5C9
More ways to join:

Join by video system: Dial<EMAIL_ADDRESS>You can also dial <IP_ADDRESS> and enter your meeting number.
Join by phone: +1-415-655-0003 US Toll | +44-20319-88141 UK Toll | Access code:<PHONE_NUMBER>

PJ Di Giammarino, JWG

Jane / FINOS

Anantha SHARMA / Synechron

Eteri / FINOS


Request - Open Graph support.

Hello,
Any idea if Open Graph support is possible or on it's way ?
http://ogp.me/
Will see if I can add it myself when I have some time free.
Reason:
https://discourse.gohugo.io/t/adding-hyperlink-image/7235/2
Many thanks

https://github.com/comfusion/after-dark/blob/master/layouts/_default/baseof.html#L17

If theme author doesn't have it you can extend the head or base layout (whichever is appropriate for the theme) and add the internal layout to achieve basic open graph support.

@Kaicastledine does that help?


boinc: 7.22.0 -> 7.22.1

Description of changes
https://github.com/BOINC/boinc/releases/tag/client_release/7.22/7.22.1
Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 231063 run on x86_64-linux 1

1 package built:

boinc

Thank you!


terraform use required?

So, I was going to set this up on three bare-metal nodes, and I don't see a way to specify to the scripts that I'm not using a cloud provider. I set provider=metal in my hosts: all / vars section in my playbook just so it wouldn't complain about provider being undefined (which it first encounters in the LVM task.)
However, it bombs out a few steps later with the following error, and I'm not sure how to work around it:
TASK: [docker | configure docker consul dns] **********************************
fatal: [10.x.x.x] => One or more undefined variables: 'private_ipv4' is undefined
Am I missing something?

Terraform is not required, but the script in plugins/inventory/terraform.py does populate ansible vars.
You can create a manual ansible inventory file and include the extra vars.  For example:
[role=control]
control-01 private_ipv4=<IP_ADDRESS>

Here's the output of terraform.py for a standard openstack cluster, build recently, in case that's helpful! Some fields have been deleted.

@tonybecker let's track this in #847.


ERROR in Cannot determine the module for class XComponent in '/var/XComponent'. Add XComponent to the NgModule to fix it

I am having trouble deploying, for custom components created for formly and not yet declared in any module, not yet in use.
The others that were created and are in use gave no problem, it seems that to solve must associate the component with a module.
how to solve ?

That's an angular issue, the solution is to include them in an NgModule or use tsconfig to exclude those files:
{
  "exclude": [
    "..."
  ]
}


Fix line truncation on printing null character via *printf() functions

Using strlen() in these two places is bad idea because it stops at the first '\0' and only prefix of formatted string is printed.
I tried to update tests, but couldn't embed null character in cmake string and those in captured output of printf seem to be completely ignored by it either on input or in regular expression engine...

Thanks @xaizek


Can't bind to 'uploader' since it isn't a known native property

I had this working before the release candidate upgrade.  Now it compiles but I get this runtime error:
EXCEPTION: Template parse errors:
Can't bind to 'uploader' since it isn't a known native property ("-over': hasBaseDropZoneOver}"
                 (fileOver)="fileOverBase($event)"
                 [ERROR ->][uploader]="uploader"
                 class="well my-drop-zone">

                <input type="file" ng2-file-select [ERROR ->][uploader]="uploader" multiple />

Here is a snippet from my component.ts:
@Component({
    selector: 'file-upload',
    templateUrl: 'app/components/fileUpload/fileUpload.component.html',
    directives: [FILE_UPLOAD_DIRECTIVES, NgClass, NgStyle, CORE_DIRECTIVES, FORM_DIRECTIVES]
})

export class FileUploadComponent {
    public uploader: FileUploader = null;
    public hasBaseDropZoneOver: boolean = false;
    public hasAnotherDropZoneOver: boolean = false;

    constructor(private _config: ConfigService, private _sessionService: SessionService) {
        this.uploader = new FileUploader({ url: this._config.getUrl('/api/fileupload/upload') });
        this.uploader.authToken = 'Bearer ' + this._sessionService.Session.id_token;
    }

And here is the relevant markup in the template where the error occurs.

                <input type="file" ng2-file-select [uploader]="uploader" multiple />

Any ideas?

Solved.  The directive is now ng2FileDrop, not ng2-file-drop.

@chambersDon getting this error.. Please how to resolve this.
Can't bind to 'uploader' since it isn't a known native property ("rimary">
Browse
<input type="file" class="upload" ng2FileSelect [ERROR ->][uploader]="uploader" (change)="browse($event.target.value)" >

"):

I am kind of stuck with this error too, can someone post a code sample on how to solve this please?

For those encountering this problem, I finally solved it.
First you have to import {FileDropDirective} from ng2-file-upload :
import {FileSelectDirective,
        FileDropDirective,
        FileUploader} from 'ng2-file-upload/ng2-file-upload';

Then pass 'FileDropDirective' in your component's directives

@escarabin
I am getting this error when using jspm to bundle the js files for serving purpose, but not getting it when running separately with systemjs. May I know what tool you to bundle them to avoid this error in production? Thanks!

@yeelan0319 I suppose your tool for bundle is eliminating the code that is actually in use. If you are using webpack see the configuration examples for production at https://github.com/angular/angular-cli or https://github.com/AngularClass/angular2-webpack-starter and compare it to yours. I had similar problems before and it was an issue with the production config.


The Agrippa Defense rvalue

This is the error I get in this Python mission. The help button doesn't speak to this cryptic error.

AND, the error is actually on the previous line.
Assigning to rvalue means you are assigning to something that should be on the right side of an assignment not the left side . . . huh!?  Yup, I agree...
For example: "x+1 = y+2", the "x+1" belongs on the right side of an '='. . it's an r(ight)value. "z= x+1"
In your code, on the line before (which is where the error is a lot of times.) you have '=' when you should have '=='. It thinks you are trying to assign "True" to "self.isReady(cleave)" instead of checking to see if they are equal.


improvementAdd nereids p0 pipeline trigger not required

Proposed changes
Problem summary
Describe your changes.
Checklist(Required)

[ no ] Does it affect the original behavior
[ no] Has unit tests been added
[ no] Has document been added or modified
[ no] Does it need to update dependencies
[ yes ] Is this PR support rollback (If NO, please explain WHY)

Further comments
you can add comment like “run nereids_p0”  to trigger teamcity  nereids  p0 pipeline.

run buildall


Do heterozygous variants remain in long reads after correction?

Dear fmlrc developers,
Thank you very much for developing such a beautiful tool for us. I am trying to use fmlrc to correct my ONT long reads (42x) with Illumina short reads (80x) from the same biological sample. Our target genome is a diploid heterozygous genome and from the short-read k-mer distribution, I can see two clear peaks, which means we have reads from both haplotypes (I also believe my long reads are from both haplotypes)
My question is does fmlrc distinguish heterozygous variants from real sequencing errors, will the heterozygous variants remain in long reads after correction? I would like to try read-based phasing later, so I would expect to have correct long reads from both haplotypes.  Could you please give me any insights? Thanks very much.
Best,
Yutang

Yutang,
There is no explicit differentiation between sequencing errors and heterozygosity built into fmlrc.  However, there is implicit differentiations assuming your errors are "random" or at least significantly lower representation than your real variant signal.
Assuming your variants are sufficiently represented in the data, then you basically want to find the sweet spot where the count for error k-mers is below the filtering threshold and the counts for heterozygous variant k-mers are above that threshold.  The main parameters to tinker with will be:

the k-mer sizes, as these influence your counts,
-m - the minimum number of k-mers to be considered "real", and
-f - the dynamic threshold for if you have higher than expected counts

It's entirely possible that the default values of -m 5 -f 0.1 will work here, but I haven't explicitly tested it.  For more details, similar concepts have been brought up in this topic and this older topic.
Happy to answer follow up questions if those explanations need more description.
Matt

As a follow up, since you have k-mer distributions to look at, that will be a good way to inform your choice of -m for that k-mer size.

Hi Matt,
Interesting! Thank you very much for your explanation and dcopetti who posted the older topic was my colleague.
In my k-mer distribution, the heterozygous peak is at ~40x and the homozygous peak is at ~80x, so I think -m 5 is fine for my analysis but I could increase it a bit to 10 or something. Anyway, I would like to try the default setting first. What do you think?
Yutang

Yea, that sounds like a good initial approach to me.  If you have a way to benchmark/evaluate afterwards (depends on your organism and what you know about it already), that would definitely help inform which one is "better".

To be honest, I have no idea for benchmarking right now, but thank you very much for all your input. I will close this issue now and I may reopen it in the future when I have other questions.
Cheers,
Yutang

Hi Matt,
My FMLRC2 program finished within 4 days, I think this is really quick considering that I was correcting 108 gb long reads. My colleague tried Canu correction method with the same data, he said it took like forever and he could not get the corrected reads. So I think the benchmark paper is correct, FMLRC2 does perform very well. Thank you very much for developing this masterpiece.
Since I have the corrected long reads, I thought why not I compare kmers between my short reads and the corrected long reads. From the kmer comparison plot, I think I should be able to tell whether the heterozygous variants were preserved. So, I did KAT and I got the plot.

As you can see from the plot, in the heterozygous peak (the first peak), heterozygous kmers from both haplotypes that are present in the short reads are also present in my long reads and the kmer frequency is greater than 6. I think this is true since I have 40x long reads, and I expect kmers from each haplotype to have 20x coverage. If most of the true heterozygous kmers were corrected and only one haplotype left after correction, I should see a large black area in the first peak, but this is not the case. So, I think FMLRC2 did preserve true heterozygous variants in my long reads. What do you think?
As for the read accuracy after correction, since we don't have a high-quality reference genome at this moment, I don't know how to evaluate the accuracy, but I believe the error rate is dramatically decreased, otherwise I should not obtain such a nice kmer plot.
Thanks again for developing this nice tool for us.
Best wishes,
Yutang

Yutang,
If I understand the plot correctly, you're creating one of these figures against your read dataset instead of a reference genome, right?
If that's true, then I agree with what you're saying.  It looks like you have a high heterozygous peak and another visible homozygous peak at about double, and the vast majority falling on k-mers that are present in your short-read set.  Glad to hear it worked out for you!
Matt

Hi Matt,
Yes, you are correct. The kat plot I made is comparing kmers between two read files. The heterozygosity is really high in our target genome, I like that but I also hate that, very complicated feeling.
Anyway, thank you very much for all your help and support. I will recommend your program to my colleagues.
Best wishes,
Yutang


Preview icon is old Blockstack icon

When you post a link to our documentation in Discord, the site preview displays an icon which is the outdated Blockstack logo.  Update this icon to the Stacks logo.

Fixed by #1160


Observation list yaml file limited to 1 filter per observation

Need to modify observation list yaml file to be able to supply more than one filter per observation. Code development was done using an example APT file that had only a single filter per observation, and was never expanded to accept multiple filters.

Updated observation list yaml file format and all supporting code changes merged in #46. Simulator now supports having multiple filter pairs per observation in the APT file.


chore(icons): move out of the monorepo

Codecov Report

Merging #253 (06b8993) into dev (efb7469) will decrease coverage by 2.70%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##              dev     #253      +/-   ##
==========================================
- Coverage   95.66%   92.95%   -2.71%
==========================================
  Files        1487      113    -1374
  Lines        6544     3081    -3463
  Branches     1073     1029      -44
==========================================
- Hits         6260     2864    -3396
+ Misses        137      103      -34
+ Partials      147      114      -33

Impacted Files
Coverage Δ

...act-magma-dom/src/components/Dropdown/Dropdown.tsx
82.60% <0.00%> (-2.90%)
:arrow_down:

...ma-icons/src/icons/Image/ImageNotSupportedIcon.tsx

...react-magma-icons/src/icons/Image/ColorizeIcon.tsx

...ct-magma-icons/src/icons/Content/AddCircleIcon.tsx

...magma-icons/src/icons/Image/NavigateBeforeIcon.tsx

...react-magma-icons/src/icons/Social/MoodBadIcon.tsx

...gma-icons/src/icons/Communication/LiveHelpIcon.tsx

...a-icons/src/icons/Maps/LocalFireDepartmentIcon.tsx

...agma-icons/src/icons/Communication/RssFeedIcon.tsx

...ma-icons/src/icons/Communication/SwapCallsIcon.tsx

... and 1079 more

Continue to review full report at Codecov.

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

Just a note: there's no actions for the new icons repo. We'll need those before adding more icons :D


build make scann build on macos

The goal of this PR is to enable scann to be built on MacOS as well. (My system: Big Sur 11.5 intel chip). It includes several existing know fixes to common issues and some addtional fixes to the issues during my local build.
With this PR and following recommended steps, you should be able to get a scann macos wheel built from source successfully.

Create a virtual env within scann WORKSPACE folder.
python configure.py
export BAZEL_USE_CPP_ONLY_TOOLCHAIN=1
CC=/usr/local/Cellar/llvm/14.0.6_1/bin/clang bazelisk build  --incompatible_blacklisted_protos_requires_proto_info=false -c opt --macos_sdk_version=11.3 --features=thin_lto --copt=-mavx2 --copt=-mfma --cxxopt="-D_GLIBCXX_USE_CXX11_ABI=0" --cxxopt=-std=c++17 --copt=-fsized-deallocation --copt=-w :build_pip_pkg
./bazel-bin/build_pip_pkg

@sammymax Apologies for pining you directly, but I kind wanna hear your thoughts on this one, have seen a bunch of folks complaining about missing whls for macosx. Lemme know if this one makes sens to you, thanks in advance!

It's unfortunately a fairly big commitment for us to test and release binaries on MacOS, so we're hesitant to accept this change. Based off this PR though, I removed the hash_set includes from the ScaNN codebase in https://github.com/google-research/google-research/commit/06604970e69f9f79a2ff32e07742890bcfc6c268 -- hope this at least helps a bit.

@sammymax Make sense, I completely understand the efforts maintaining whls cross platform. Do you feel comfortable that we made more explicit steps in the README regarding how to built Scann locally? I think with your house keeping change (removing hash_set), the minimum change for folks to build on macos, the tensorflow dylib also needs to be updated, and pruned bazel build command.  Thanks!


Issue #6 child: revise CDP neighbour code

https://github.com/ctomkow/verify/blob/b733eab0d168f7b06c882e67eca9224c0a872a90/Verify.py#L156

revised code, aligned with stack member code using the compare_list method.
https://github.com/ctomkow/verify/commit/b1a5219120e27febd891a33e542f4ec29133f747


Pypi/0.1.1 release

Coverage remained the same at 100.0% when pulling 23565cdb55db41be88f057051a837cbdb00fd0ae on pypi/0.1.1-release into 2ca3f2771ae573c7445a3dadcff24b13962e0cc4 on master.


Add license badge to readme (first-timers-only)

first-timers-only
This issue is tagged :octocat: first-timers-only. It is only for people who have never contributed to open source before and are looking for an easy way take their first steps.
Consider this as your chance to dip your toe into the world of open-source and get some bragging rights for writing code that makes drones fly, cars find charging stations, helps people and goods move from place to place and more...
Find more first-timers-only issues from DAV Foundation here.
Thank you for your help :heart:
What is this project?
DAV (Decentralized Autonomous Vehicles) is a new non-profit foundation working to build an open-source infrastructure for autonomous vehicles (cars, drones, trucks, robots, and all the service providers around them) to communicate and transact with each other over blockchain.
As an organization that believes in building a large community of open-source contributors, we often create issues like this one to help people take their first few steps into the world of open source.
DAV CLI
The DAV project you are looking at is DAV CLI. This CLI (command-line interface) tool makes developing applications and solutions that interact with DAV a much more pleasant experience.
How you can help
The Issue
Your task for this issue is to add the license badge in the README.md file.
Just add the below lines in the README.md and have a look at other DAV projects for the location.
[![license](https://img.shields.io/github/license/DAVFoundation/dav-cli.svg?style=flat-square)](https://github.com/DAVFoundation/dav-cli/blob/master/LICENSE)

Contributing to DAV CLI

[ ] Make sure this issue is labeled up-for-grabs and not labeled claimed, to verify no one else is working on it.
[ ] Comment in this issue that you would like to do it.
[ ] Open the DAV CLI GitHub page and click the ★ Star and then ⑂ Fork buttons.
[ ] Clone a copy to your local machine with $ git clone git@github.com:YOUR-GITHUB-USER-NAME/dav-cli.git
[ ] Edit the README.md file
[ ] Once you've made sure all your changes work correctly and committed all your changes, push your local changes back to github with $ git push -u origin master
[ ] Visit your fork on GitHub.com (https://github.com/YOUR-USER-NAME/dav-cli) and create a pull request for your changes.
[ ] Make sure your pull request describes exactly what you changed and references this issue (include the issue number in the title like this: #5)
[ ] Please do not fix more than one issue at a time. Your pull request should only fix what is described in this issue.

Asking for help
We appreciate your effort in taking the time to work on this issue and help out the open source community and the foundation.
If you need any help, feel free to ask below or in our gitter channel. We are always happy to help 😄

@cg-cnu Hi, I would love to work on this.

Go ahead @204070. Just a small note. Make sure you are adding it below the project title. Look at other projects for reference. 👍

Congratulations @204070 on your first contribution to opensource 🎆 💯 Wish you a happy new year and keep doing amazing work in the year ahead 🙂 Feel free to join our gitter channel for find out more opportunities and get updates from dav foundation 😄

@cg-cnu Thanks a lot.


Add no-shallow-imports rule

Prevent shallow (barrel) imports.
Why?
Obviates the need for tree shaking.
Todo:

[ ] Add more test cases
[ ] Fix commented-out test case (for full coverage)
[x] Update examples within docs
[x] Add line to README.md

@ljharb Hey Jordan, just wondering if there's any feedback on this pull request. Cheers :)

I don't think this should work by looking at the consuming side - i think it should work by looking at the exporting side.

Hmmm, sorry, I don't understand what you mean by this. How would the exporting side preemptively know what's consuming it?

It wouldn't. The problem is caused by a file re-exporting something.
If you don't re-export anything, it's impossible to have a "barrel" approach unless you put everything in the same file.

Why is file re-exporting a bad thing? Should we be discouraging nested barrel exports?

It's a bad thing because it creates an otherwise nonexistent need for tree-shaking - which due to the nature of JS, can only ever do a half-assed job at deleting unused code.
Yes, nobody should ever be using barrel exports, nested or otherwise, and everything should always be deep-imported from the most granular place it can be.


Iteration4

Apply APScheduler.
PR Type

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Others. (Please describe)

PR Info.
Changes

Add scheduler.
All jobs can be view at Django admin page.

Shows logging when job is added.
reminderTime for Tag and Assignment can accept only 3 values.
When Assignment doesn't have reminderTime, it will use reminderTime from Tag instead.

Codecov Report

Merging #45 (0f263f1) into master (dd51b23) will increase coverage by 1.43%.
The diff coverage is 96.90%.

@@            Coverage Diff             @@
##           master      #45      +/-   ##
==========================================
+ Coverage   84.15%   85.58%   +1.43%
==========================================
  Files          56       59       +3
  Lines         934     1034     +100
  Branches       43       53      +10
==========================================
+ Hits          786      885      +99
  Misses        134      134
- Partials       14       15       +1

Impacted Files
Coverage Δ

garnbarn_api/serializer.py
72.22% <ø> (+1.57%)
:arrow_up:

garnbarn_api/services/pubsub.py
50.00% <50.00%> (ø)

garnbarn_api/models.py
95.94% <96.42%> (+0.39%)
:arrow_up:

garnbarn_api/tests/test_scheduler.py
98.21% <98.21%> (ø)

config/settings.py
100.00% <100.00%> (ø)

garnbarn_api/apps.py
100.00% <100.00%> (ø)

garnbarn_api/services/scheduler.py
100.00% <100.00%> (ø)

garnbarn_api/views.py
61.74% <0.00%> (+0.85%)
:arrow_up:

Continue to review full report at Codecov.

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


Fix the build of docs on docs.rs

The build on docs.rs is failing because libbsd isn't found by pkgconf. But pkgconf isn't needed to build this crate on FreeBSD.  So switch the docs.rs build to target that OS.
(depends on #6)

Thanks, merging.


feat: add cli flag to disable light client server

Motivation
Disable the lightclient server in situations where needed.
Description

Disable lightclient server
Don't enable the reqresp protocols for lightclient
Don't server lightclient REST endpoints.

Closes #6800
Steps to test or reproduce
Run all tests

We should also disable light client gossip topics

:tada: This PR is included in v1.21.0 :tada:


Suppress missing key warning when loading partial model weights in BLIP2

ViT (if not finetuned) and LLM weights are not stored in the current BLIP2 checkpoints.
The default load_checkpoint() in BaseModel raises warning on missing keys, which causes confusion.
Proposed solution is to overwrite load_checkpoint() in BLIP2. This solution is not meant to be universal and it shouldn't in general to avoid neglecting missing key by accident.

Done in https://github.com/salesforce/LAVIS/commit/baad2d7c8df599d8d9b081ba2e946626eaa2dc34.


filter out non mTLS cross network endpoints  (#30705)

cherry-pick of #30705

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio_release-1.9
b94cd954ee892c13a992a6fe199b7a3725626e08
link
/test lint_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio_release-1.9
b94cd954ee892c13a992a6fe199b7a3725626e08
link
/test lint_istio_release-1.9

unit-tests_istio_release-1.9
b94cd954ee892c13a992a6fe199b7a3725626e08
link
/test unit-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio_release-1.9
b94cd954ee892c13a992a6fe199b7a3725626e08
link
/test lint_istio_release-1.9

unit-tests_istio_release-1.9
b94cd954ee892c13a992a6fe199b7a3725626e08
link
/test unit-tests_istio_release-1.9

integ-ipv6-k8s-tests_istio_release-1.9
b94cd954ee892c13a992a6fe199b7a3725626e08
link
/test integ-ipv6-k8s-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio_release-1.9
b94cd954ee892c13a992a6fe199b7a3725626e08
link
/test lint_istio_release-1.9

unit-tests_istio_release-1.9
b94cd954ee892c13a992a6fe199b7a3725626e08
link
/test unit-tests_istio_release-1.9

integ-ipv6-k8s-tests_istio_release-1.9
b94cd954ee892c13a992a6fe199b7a3725626e08
link
/test integ-ipv6-k8s-tests_istio_release-1.9

analyze-tests_istio_release-1.9
b94cd954ee892c13a992a6fe199b7a3725626e08
link
/test analyze-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio_release-1.9
b94cd954ee892c13a992a6fe199b7a3725626e08
link
/test lint_istio_release-1.9

unit-tests_istio_release-1.9
b94cd954ee892c13a992a6fe199b7a3725626e08
link
/test unit-tests_istio_release-1.9

integ-ipv6-k8s-tests_istio_release-1.9
b94cd954ee892c13a992a6fe199b7a3725626e08
link
/test integ-ipv6-k8s-tests_istio_release-1.9

analyze-tests_istio_release-1.9
b94cd954ee892c13a992a6fe199b7a3725626e08
link
/test analyze-tests_istio_release-1.9

integ-distroless-k8s-tests_istio_release-1.9
b94cd954ee892c13a992a6fe199b7a3725626e08
link
/test integ-distroless-k8s-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.9
b94cd954ee892c13a992a6fe199b7a3725626e08
link
/test unit-tests_istio_release-1.9

integ-ipv6-k8s-tests_istio_release-1.9
b94cd954ee892c13a992a6fe199b7a3725626e08
link
/test integ-ipv6-k8s-tests_istio_release-1.9

analyze-tests_istio_release-1.9
b94cd954ee892c13a992a6fe199b7a3725626e08
link
/test analyze-tests_istio_release-1.9

integ-distroless-k8s-tests_istio_release-1.9
b94cd954ee892c13a992a6fe199b7a3725626e08
link
/test integ-distroless-k8s-tests_istio_release-1.9

lint_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test lint_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio_release-1.9
b94cd954ee892c13a992a6fe199b7a3725626e08
link
/test integ-ipv6-k8s-tests_istio_release-1.9

analyze-tests_istio_release-1.9
b94cd954ee892c13a992a6fe199b7a3725626e08
link
/test analyze-tests_istio_release-1.9

integ-distroless-k8s-tests_istio_release-1.9
b94cd954ee892c13a992a6fe199b7a3725626e08
link
/test integ-distroless-k8s-tests_istio_release-1.9

lint_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test lint_istio_release-1.9

unit-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test unit-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio_release-1.9
b94cd954ee892c13a992a6fe199b7a3725626e08
link
/test integ-ipv6-k8s-tests_istio_release-1.9

analyze-tests_istio_release-1.9
b94cd954ee892c13a992a6fe199b7a3725626e08
link
/test analyze-tests_istio_release-1.9

lint_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test lint_istio_release-1.9

unit-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test unit-tests_istio_release-1.9

integ-distroless-k8s-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test integ-distroless-k8s-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio_release-1.9
b94cd954ee892c13a992a6fe199b7a3725626e08
link
/test analyze-tests_istio_release-1.9

lint_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test lint_istio_release-1.9

unit-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test unit-tests_istio_release-1.9

integ-distroless-k8s-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test integ-distroless-k8s-tests_istio_release-1.9

integ-ipv6-k8s-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test integ-ipv6-k8s-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test lint_istio_release-1.9

unit-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test unit-tests_istio_release-1.9

integ-distroless-k8s-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test integ-distroless-k8s-tests_istio_release-1.9

integ-ipv6-k8s-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test integ-ipv6-k8s-tests_istio_release-1.9

integ-security-k8s-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test integ-security-k8s-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test lint_istio_release-1.9

unit-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test unit-tests_istio_release-1.9

integ-distroless-k8s-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test integ-distroless-k8s-tests_istio_release-1.9

integ-ipv6-k8s-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test integ-ipv6-k8s-tests_istio_release-1.9

integ-security-k8s-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test integ-security-k8s-tests_istio_release-1.9

integ-security-multicluster-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test integ-security-multicluster-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test lint_istio_release-1.9

integ-distroless-k8s-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test integ-distroless-k8s-tests_istio_release-1.9

integ-ipv6-k8s-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test integ-ipv6-k8s-tests_istio_release-1.9

integ-security-k8s-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test integ-security-k8s-tests_istio_release-1.9

integ-security-multicluster-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test integ-security-multicluster-tests_istio_release-1.9

unit-tests_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test unit-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test integ-distroless-k8s-tests_istio_release-1.9

integ-ipv6-k8s-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test integ-ipv6-k8s-tests_istio_release-1.9

integ-security-k8s-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test integ-security-k8s-tests_istio_release-1.9

integ-security-multicluster-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test integ-security-multicluster-tests_istio_release-1.9

unit-tests_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test unit-tests_istio_release-1.9

lint_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test lint_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test integ-ipv6-k8s-tests_istio_release-1.9

integ-security-k8s-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test integ-security-k8s-tests_istio_release-1.9

integ-security-multicluster-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test integ-security-multicluster-tests_istio_release-1.9

unit-tests_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test unit-tests_istio_release-1.9

lint_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test lint_istio_release-1.9

integ-distroless-k8s-tests_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test integ-distroless-k8s-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test integ-security-k8s-tests_istio_release-1.9

integ-security-multicluster-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test integ-security-multicluster-tests_istio_release-1.9

unit-tests_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test unit-tests_istio_release-1.9

lint_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test lint_istio_release-1.9

integ-distroless-k8s-tests_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test integ-distroless-k8s-tests_istio_release-1.9

integ-ipv6-k8s-tests_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test integ-ipv6-k8s-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio_release-1.9
3b4bbfa01b3d220ffc2585f824cde62781856428
link
/test integ-security-k8s-tests_istio_release-1.9

unit-tests_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test unit-tests_istio_release-1.9

lint_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test lint_istio_release-1.9

integ-distroless-k8s-tests_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test integ-distroless-k8s-tests_istio_release-1.9

integ-ipv6-k8s-tests_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test integ-ipv6-k8s-tests_istio_release-1.9

integ-security-multicluster-tests_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test integ-security-multicluster-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test unit-tests_istio_release-1.9

lint_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test lint_istio_release-1.9

integ-distroless-k8s-tests_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test integ-distroless-k8s-tests_istio_release-1.9

integ-ipv6-k8s-tests_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test integ-ipv6-k8s-tests_istio_release-1.9

integ-security-multicluster-tests_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test integ-security-multicluster-tests_istio_release-1.9

integ-security-k8s-tests_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test integ-security-k8s-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test unit-tests_istio_release-1.9

integ-distroless-k8s-tests_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test integ-distroless-k8s-tests_istio_release-1.9

integ-ipv6-k8s-tests_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test integ-ipv6-k8s-tests_istio_release-1.9

integ-security-multicluster-tests_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test integ-security-multicluster-tests_istio_release-1.9

integ-security-k8s-tests_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test integ-security-k8s-tests_istio_release-1.9

lint_istio_release-1.9
a8393f2a5894acca53ed3faf163b6907f7b7ea7d
link
/test lint_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test integ-ipv6-k8s-tests_istio_release-1.9

integ-security-k8s-tests_istio_release-1.9
afd33e4b117b02ed2bca8c593e57dc39fc0aab94
link
/test integ-security-k8s-tests_istio_release-1.9

unit-tests_istio_release-1.9
8619b2b4f9fcbc77532c490a8db11670ab123f11
link
/test unit-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.9
8619b2b4f9fcbc77532c490a8db11670ab123f11
link
/test unit-tests_istio_release-1.9

integ-security-multicluster-tests_istio_release-1.9
8619b2b4f9fcbc77532c490a8db11670ab123f11
link
/test integ-security-multicluster-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio_release-1.9
8619b2b4f9fcbc77532c490a8db11670ab123f11
link
/test integ-security-multicluster-tests_istio_release-1.9

unit-tests_istio_release-1.9
86c944e3c3946f29c389a1dcfc8658ff9b040b19
link
/test unit-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.9
edf57a1d171b4c6f871769e45e569d5076d84fef
link
/test unit-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.9
edf57a1d171b4c6f871769e45e569d5076d84fef
link
/test unit-tests_istio_release-1.9

integ-security-multicluster-tests_istio_release-1.9
edf57a1d171b4c6f871769e45e569d5076d84fef
link
/test integ-security-multicluster-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio_release-1.9
edf57a1d171b4c6f871769e45e569d5076d84fef
link
/test integ-security-multicluster-tests_istio_release-1.9

unit-tests_istio_release-1.9
76185ec8a8eee0c698cf0a1420ec271ede75c1d1
link
/test unit-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.9
76185ec8a8eee0c698cf0a1420ec271ede75c1d1
link
/test unit-tests_istio_release-1.9

integ-security-multicluster-tests_istio_release-1.9
76185ec8a8eee0c698cf0a1420ec271ede75c1d1
link
/test integ-security-multicluster-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio_release-1.9
dd85e6e1ea09cc45ed6ef7a95dcd22d0b54f1809
link
/test integ-security-multicluster-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio_release-1.9
dd85e6e1ea09cc45ed6ef7a95dcd22d0b54f1809
link
/test integ-security-multicluster-tests_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

TestPassthroughFilterChain is super flaky in 1.9...
https://prow.istio.io/?repo=istio%2Fistio&job=integ-security-multicluster-tests_istio_release-1.9

/retest


[BUG] System.OutOfMemoryException - LiteDatabase in memory

Bug not resolved. When I use LiteDatabase in memory and use bulkinsert and insert in 1k to 1k rows (using transaction our not) and shows memory erros always. Please verify thanks.
at System.IO.MemoryStream.set_Capacity(Int32 value)
at System.IO.MemoryStream.EnsureCapacity(Int32 value)
at System.IO.MemoryStream.Write(Byte[] buffer, Int32 offset, Int32 count)
at LiteDB.Engine.ConcurrentStream.Write(Byte[] buffer, Int32 offset, Int32 count)
at LiteDB.Engine.DiskService.WriteLogDisk(IEnumerable`1 pages)
at LiteDB.Engine.TransactionService.PersistDirtyPages(Boolean commit)
at LiteDB.Engine.TransactionService.Commit()
at LiteDB.Engine.LiteEngine.CommitAndReleaseTransaction(TransactionService transaction)
at LiteDB.Engine.LiteEngine.Commit()

Can you provide a repro?

This error occurs here
LiteDB\Engine\Engine\Transaction.cs -> AutoTransaction line 93

More details:
at System.IO.MemoryStream.set_Capacity(Int32 value)
at System.IO.MemoryStream.EnsureCapacity(Int32 value)
at System.IO.MemoryStream.Write(Byte[] buffer, Int32 offset, Int32 count)
at LiteDB.Engine.ConcurrentStream.Write(Byte[] buffer, Int32 offset, Int32 count) in C:\LiteDB\Engine\Disk\Streams\ConcurrentStream.cs:line 75
at LiteDB.Engine.DiskService.WriteDataDisk(IEnumerable1 pages) in C:\LiteDB\Engine\Disk\DiskService.cs:line 304    at LiteDB.Engine.WalIndexService.CheckpointInternal() in C:\LiteDB\Engine\Services\WalIndexService.cs:line 349    at LiteDB.Engine.WalIndexService.TryCheckpoint() in C:\LiteDB\Engine\Services\WalIndexService.cs:line 293    at LiteDB.Engine.LiteEngine.CommitAndReleaseTransaction(TransactionService transaction) in C:\Users\e_dns\Downloads\LiteDB\LiteDB\Engine\Engine\Transaction.cs:line 118    at LiteDB.Engine.LiteEngine.AutoTransaction[T](Func2 fn) in C:\LiteDB\Engine\Engine\Transaction.cs:line 91

Sugested solution to fix Memory Alocation error and inprove performance:
File: LiteDB\Engine\Disk\StreamFactory\StreamFactory.cs - line 33
public Stream GetStream(bool canWrite, bool sequencial)
 {
     const int bufferSize = 81920; // 80 KB

     if (_password == null)
     {
         using (var bs = new BufferedStream(_stream, bufferSize))
         {
             return new ConcurrentStream(bs, canWrite);
         }
     }
     else
     {
         using (var bs = new BufferedStream(_stream, bufferSize))
         {
             return new AesStream(_password, new ConcurrentStream(bs, canWrite));
         }
     }
 }


Modify default values for sam bringup script

Update bringup script with the world config and robot config for kristineberg.

Do we still need this? @luxiya01

Hmm... No I don't think so, let me close this.


Implemented Pagination and Sorting functionality; Added unit test cas…

Service (Implementation of pagination and Sorting
`   @Override
public Page pagination(int offset, int pageSize, String field) {
    if ("defaultValue".equals(field)){
        return robotPositionRepository.findAll(
                PageRequest.of(offset, pageSize)
        );
    }
    return robotPositionRepository.findAll(
            PageRequest.of(offset, pageSize).withSort(Sort.by(field))
    );
}`

The purpose of this code is to facilitate paginated retrieval of RobotPosition entities from a repository. The method takes three parameters: offset and pageSize control the range of results to be retrieved, while field specifies the sorting criteria. If the provided field is equal to the string "defaultValue," the method returns a paginated result without applying any specific sorting. Otherwise, it returns the paginated result sorted by the specified field using the provided robotPositionRepository for data retrieval. The implementation allows for flexible and efficient retrieval of paginated data with optional sorting based on the specified field.

Ta, I will review at my earliest convenience.


Multiple "line" type graphs with different Y and X?

Looking at the latest 2.0dev branch. Is it possible to combine together multiple graphs with not only Y different, but X too (where X is date)?
Great work on 2.0 btw, even alpha works great :+1:

@iroller it is possible to have charts with multiple x and y axes. The sample config below will create 2 x axes, 2 y axes and then bind each dataset to one pair of axes.
config = {
    data: {
        datasets: [{
            label: "My First dataset",
            xAxisID: "x-axis-1", // bottom axis
            yAxisID: "y-axis-1", // left axis
	    data: []
        }, {
            label: "My Second dataset",
            xAxisID: "x-axis-2", // top axis
            yAxisID: "y-axis-2", // right axis
            data: []
        }]
    },
    options: {
        scales: {
            xAxes: [{
                position: "bottom",
                type: "time", // gives us a date axis
                id: "x-axis-1"
            }, {
                position: "top",
                type: "time",
                id: "x-axis-2"
            }],
            yAxes: [{
                type: "linear",
                position: "left",
                id: "y-axis-1",
            }, {
                type: "linear",
                position: "right",
                id: "y-axis-2",
            }],
        }
    }
}

Hey thanks @etimberg , but what I'm asking is not how to have multiple axes, but multiple "labels: [newDate(0), newDate(1)]" per dataset on the same axis.
For example if you look at
https://github.com/nnnick/Chart.js/blob/v2.0-dev/samples/line-time-scale.html
I'd looking for a way do modify it in a following way:
        var config = {
            type: 'line',
            data: {
                //labels: [newTimestamp(0), newTimestamp(1), newTimestamp(2), newTimestamp(3), newTimestamp(4), newTimestamp(5), newTimestamp(6)], // unix timestamps
                // labels: [newDate(0), newDate(1), newDate(2), newDate(3), newDate(4), newDate(5), newDate(6)], // Date Objects
-                labels: ["01/01/2015 20:00", "01/02/2015 21:00", "01/03/2015 22:00", "01/05/2015 23:00", "01/07/2015 03:00", "01/08/2015 10:00", "01/10/2015"], // Hours
                // labels: ["01/01/2015", "01/02/2015", "01/03/2015", "01/06/2015", "01/15/2015", "01/17/2015", "01/30/2015"], // Days
                // labels: ["12/25/2014", "01/08/2015", "01/15/2015", "01/22/2015", "01/29/2015", "02/05/2015", "02/12/2015"], // Weeks
                datasets: [{
                    label: "My First dataset",
                    data: [randomScalingFactor(), randomScalingFactor(), randomScalingFactor(), randomScalingFactor(), randomScalingFactor(), randomScalingFactor(), randomScalingFactor()],
+                   labels: ["01/01/2015 20:00", "01/02/2015 21:00", "01/03/2015 22:00", "01/05/2015 23:00", "01/07/2015 03:00", "01/08/2015 10:00", "01/10/2015"], // Hours
                    fill: false,
                    borderDash: [5, 5],
                }, {
                    label: "My Second dataset",
+                   labels: ["01/01/2015 20:30", "01/02/2015 21:30", "01/03/2015 22:30", "01/05/2015 23:30", "01/07/2015 03:30", "01/08/2015 10:30", "01/10/2015"], // Hours
                    data: [randomScalingFactor(), randomScalingFactor(), randomScalingFactor(), randomScalingFactor(), randomScalingFactor(), randomScalingFactor(), randomScalingFactor()],
                }]

@etimberg I think I get what he is asking. Similar functionality to the scatter api. X and Y properties within an object as opposed to the equally mapped category style.

One of the use cases for this is to compare some of your health levels (that you measure every day in different time) from today and yesterday, from this week and previous week, etc.  You'll need those values on one graph, but both X and Y are different.

ah, ok, I get it. Similar to how the scatter data looks. @tannerlinsley we can easily move the getRightValue function up into the base

Nice.

@iroller I got this implemented in the tooltip refactor branch. It will be into v2 as soon as that's merged (hopefully in the next few days)

Thanks @etimberg . In the sample you modified (samples/line-time-scale.html) there's a first x data point should be located at "12/31/2014 06:00" however it's located between January 1st and 2nd on the graph:

All the other points in "Dataset with point data" do not actually match the X axis. Is it supposed to be so?

odd, this is the view on my browser. The "Dataset with point data" data should match the axis. Did you sync down that branch completely and build or just used 7603b3cc?

Oh it looks like I forgot to re-build with gulp, not used to it, sorry about that!
Thanks for this, works great.

I am trying to draw the y axis on the right hand side with the code below:
var data = {
    labels: ["January", "February", "March", "April", "May", "June", ""],
    datasets: [
		{
			label: "My first dataset",
			xAxisID: "x-axis-1",
			yAxisID: "y-axis-1",
			fillColor : "rgba(151,220,220,0.2)",
			strokeColor : "rgba(151,220,220,1)",
			pointColor : "rgba(151,220,220,1)",
			pointStrokeColor : "#fff",
			pointHighlightFill : "#fff",
			pointHighlightStroke : "rgba(151,187,205,1)",
			data: [40, 59, 80, 34, 57, 92, 60]
		}
    ]
};
var options = {
	scales: {
		xAxes: [{
			scaleType: "linear",
			display: true,
			position: "bottom",
			id: "x-axis-1",

			labels: {
				show: true,
				template: "<%=value%>",
				fonrSize: 12,
				fontStyle: "normal",
				fontcolor: "rgba(220,200,220,1)",
				fontFamily: "Helvetica Neue",
			},
		}],
		yAxes: [{
			scaleType: "linear",
			display: true,
			position: "right",
			id: "y-axis-1",

			labels: {
				show: true,
				template: "<%=value%>",
				fontSize: 12,
				fontStyle: "normal",
				fontColor: "#666",
				fontFamily: "Helvetica Neue",
			},
		}]
	}

and then draw the chart:
var ctx = document.getElementById("myChart").getContext('2d');
var myLineChart = new Chart(ctx).Line(data, options);

But it doesnt change anything. Am I doing anything wrong here?

@iroller : how did you solve it
, @etimberg :As it is the issue of synchronization, I may have the same problem because at the time of filtering in January it appears to me that it uses all the labels
https://github.com/chartjs/Chart.js/issues/5443#issuecomment-384286238

How can I raise the y-axis or superimpose an example axis?

@Memo211985 @adtm this is not the place to ask for advice, better head over to stackoverflow.
For me it worked using type: 'scatter' and in the datasets showLines: true.

@wtho I disagree. If I use the library by its documentation and it's not the expected output, it's normal to question.


plugin: runtime.main_main·f: undefined: "main.main"(buildmode=plugin)

I want to build a plugin for my program, and the main content is ...
package main

import (
        "mylib"
        ......
)

The package "mylib" is a package of my defined, when I import it and then build it, the error will occur ...
command-line-arguments
runtime.main_main·f: relocation target main.main not defined
runtime.main_main·f: undefined: "main.main"

why? Thanks a lot!

@kenkao, please provide a complete repro (code & commands you ran), and include the output of go bug.
@crawshaw, maybe you recognize this as a dup of something else?

@bradfitz
Thanks for your replying!
I have found the answer, because I import the package "plugin" in "mylib" . (Σ( ° △ °|||)︴)
I want to use the "go build" to build the main app, and use "go build plugin" to build the "main.so", then I can let  the main to load the "main.so" for itself's hotloading
Can't I ?

No clue.

@bradfitz
The source code is here:
https://github.com/kenkao/plugintest
go version go1.8 linux/amd64
cd main/
go build -ldflags "-pluginpath=plugin/hot-$(date +%s)" -buildmode=plugin -o gplugin.so gplugin.go

You have 2 main functions defined in your main package.  I was getting a similar error when I had none defined in a package main.

 I was getting a similar error when I had none defined in a package main.
That was my issue too

In my case I had not defined a function called main i.e.  func main(){}

[root@localhost main]#  go build -ldflags "-pluginpath=plugin/hot-$(date +%s)" -buildmode=plugin -o gplugin.so gplugin.go
command-line-arguments
runtime.main_main·f: relocation target main.main not defined
runtime.main_main·f: undefined: "main.main"
[root@localhost main]#

@jimmiebtlr
the 'main' func in gplugin.go is an redundant code block for my debuging, i have deleted it. but when you want to build the gplugin.go to a plugin.so, the same error will occur..
i guess that you cannot import any package that imported the 'plugin' package (╮(￣▽￣")╭), when you want to build it to a plugin.so (the 'gplugin' import the 'mylib', and the 'mylib' import the 'plugin')
i think it may be beneficial to the security of golang..

my hot-update based on plugin for go has succeeded! ^ ^

It sounds like this was resolved when you added func main() {} to your plugin. For now, the main function is required and documented, so I'm going to close this.
(If I misunderstood this issue, please comment and I'll reopen it.)

@crawshaw
When i use plugin in plugin:
runtime.main_main·f: relocation target main.main not defined
runtime.main_main·f: undefined: "main.main"

demo

You need to add func main() {} to your plugin.

Sorry, I have added func main () {} to plugin/plugin.go and models/models.go, but still hold the wrong.
runtime.main_main·f: relocation target main.main not defined
runtime.main_main·f: undefined: "main.main"

@crawshaw Need me to open a new issue?

Hello I've a same this problem.
but... I've 3 folders for 3 applications (app-test, app-update, app-deploy)
1st app-test it will be ok and running as server
but when I create second app-update for check heartbeat of first app that i cant use "package main" but when I need run it that I can't
What/How I can fix it... Thank you

@KubisGroup Please ask questions on a forum; see https://golang.org/wiki/Questions.  You will get a better and faster response.  When asking your question please explain exactly what you are doing and exactly what happens.  Thanks.

I came across the same issue when I executed go run main.go.
Demo Repo

I hit this error when I accidentally defined func Main() instead of func main().


az resource move ResourceID case issue

Describe the bug
When trying to move a collection of resources ids with az resource move --ids $IDs --destination-group $DestinationGroup, the command fails with the error All resources should be under the same group even though all resources /are/ under the same group.
It seems that this occurs when the resource ID collection contains resources where the group is in a different case, eg. ResourceGroup, RESOURCEGROUP.  All of these IDs are gleaned from the az resource show command.
Using the Az Powershell module and the portal succeed without issue.  Manually changing the ResourceGroup in the ResourceID to match across the entire collection succeeds.
The difference seems to be localized to disk IDs in this case.
To Reproduce
$VM = az vm show --resource-group $SourceResourceGroup --name $VMName --resource-type "Microsoft.Compute/virtualMachines" | convertfrom-json
Add VMid and OS Disk
$IDsToMove += ($VM.id , $VM.properties.storageProfile.osDisk.managedDisk.id )
Add NIC(s)
($VM.properties.networkProfile.networkInterfaces | ForEach-Object { if ($.id -match {$IDsToMove += $.id} )
Add Data disk(s)
($VM.properties.storageProfile.dataDisks.managedDisk | ForEach-Object {$IdsToMove += $_.id})
az resource move --destination-group $DestinationGroup --ids $Ids
Expected behavior
The resources are all in the same source resource group, so they should move without error with case not being a consideration in the validation.
Environment summary
MSI / 2.0.77 / Windows 10 17763 / Powershell Core 6.23 / VS Code 1.40.1
Additional context
This may be related to GH Issue #8283
My workaround is to manually create the resource ID to be the same case, which works.

@Juliehzl Please take a look

@Tiano2017 any update for this issue?

@Tiano2017 any update for this issue?

@ifeoluwaokunoren to take a look and triage.

@ifeoluwaokunoren any update for this issue?

We're still seeing this, any reason it's closed?

In particular, when we create a vm under some rg abc, the osDisk is labeled as rg ABC, and trying to move all entries of show -g abc fails with the mismatch error.

@ifeoluwaokunoren Hi, could you please take a look and triage it. There are some customers need to solve relevant problems~

@lmeyerov Hi, this problem does not belong to our team. I have communicated with relevant teams to solve this problem

FYI, using the latest api-version (2021-04-01) with the same payload works, if the CLI command gets updated to that then this should just work as intended. For now, I'm using the az rest command.

@timio73 Apologies for the late reply. I hope you had a chance to look at the above comment. Could you please let me know if you are still facing this issue ? Awaiting your reply.


Authentication Spike

Spike Story to investigate options available for App authentication. Time boxed activity terminating on 24 July 2023

Research Report: Google Calendar Spike Findings

Introduction
This research report presents the comprehensive findings from an in-depth analysis of the official Google Calendar API documentation, exploration of sample code, and rigorous experimentation with various implementations. The primary focus was to assess the viability of leveraging Google's appointment scheduling management services.
Leveraging Google Authentication and APIs
The investigation extensively covered the process of establishing a secure connection between our React app and Google Cloud using Google authentication. Additionally, meticulous attention was given to setting up the API with Google, facilitating access to crucial data such as email addresses, calendar events, and contact information.
Test Users and Rigorous App Testing
As part of the research, a series of test users were successfully incorporated to ensure thorough testing of the application upon deployment. This iterative testing process played a crucial role in refining the app's functionality and user experience.
Authentication and Authorization Protocols
Ensuring the integrity of the system, both providers and users underwent stringent authentication and authorization processes, in accordance with Google's guidelines. This entailed robust login procedures to ensure secure access. Moreover, providers were required to make their calendars public, and acquiring their Google Calendar ID was essential for seamless event listing.
Streamlined Appointment Creation and Dynamic Calendar Updates
A noteworthy achievement in this research was the development of a streamlined form that seamlessly utilized Google API to create appointments and dynamically update Google calendars. These advancements align seamlessly with the integration objectives envisioned for our project.
Cost-Effectiveness Analysis
An essential aspect of the research entailed a comprehensive cost-effectiveness analysis, which indicated significant potential cost savings by opting for Google's appointment scheduling management services.
Conclusion
In conclusion, the research outcomes strongly advocate for the adoption of Google Calendar API as an efficient and cost-effective solution for managing appointment scheduling. By adhering to the necessary authentication and authorization measures, we can confidently proceed with the integration process to achieve our project goals.


User rights to database are reseted after upgrade from 3.2.* to next version

I downloaded and install new version of ArangoDB 3.2.2. And after installing I run it from Terminal
/Applications/ArangoDB3-CLI.app/Contents/MacOS/usr/sbin/arangod --server.storage-engine=rocksdb /mypath/rocksdb_3_2 --server.endpoint tcp://<IP_ADDRESS>:8585

And rights of my user were reseted to database: I can't create new collections and write to collections (only read). The same situation was after upgrade from 3.2 to 3.2.1.
After logging in by root user and setting new rights for my user all became good.

This should have been fixed in one of the recent releases. Could you try with 3.2.6 and re-check if the problem is actually solved?
Thanks!

@jsteemann I have no problems with rights now. Thank you! :)


[FEATURE REQUEST] HDR Gain map support

Is your feature request related to a problem? Please describe.

Providing compatible HDR content for an increasing number of HDR capable devices.

Describe the solution you'd like
Proposing to add support for gain maps in OIIO to read/write backwards compatible jpg images with gain maps.

Add reader and writer plugins for libultrahdr. Existing support in Chrome to view these seems beneficial.

Describe alternatives you've considered

ImageMagick appears to have support for UltraHDR.

Additional context

https://www.iso.org/standard/86775.html
https://github.com/google/libultrahdr/
https://github.com/libjpeg-turbo/libjpeg-turbo/issues/746

This is apparently an extension to JPEG that stashes an extra part to the file that includes the HDR information (readers that don't know about this just see the part that's the ordinary SDR JPEG image.
This would be great for somebody to tackle as a modification to our JPEG reader.
🎣 Mackerel!

I can take a stab at it if that's alright with everyone!

Yes, please, @mugulmd !

Implemented by #4484


dataset

Hello, I would like to ask some questions about the dataset. I noticed that rebuilding one's own dataset from the example folder requires three files, namely "JAX_214_CLS.tif", JAX_214_DSM.tif，JAX_214_DSM.txt”， I would like to ask what JAX_214_CLS.tif is and how to obtain it. Also, is it possible for my DSM resolution to be 30m? Thank you!

Hi, sorry for the late response. The JAX_214_CLS.tif is provided in the open source DFC dataset, it is not necessary for your own dataset.
For the DSM resolution, my suggestion is that it should not be worse than 8*(resolution of the image).


Logging

Guys, what do you think if we add logging system to this library? Sometimes it's worth to now what's going on at low level interaction with Mandrill API. Unfortunately, the api-mandrill gem itself doesn't have ability to log it's work. I know that's not very appropriate abstraction level to do such things in mandrill_dm, but maybe we could at least log api call parameters and concise result.
If you find this idea reasonable, let's proceed the discussion.
Also I'm happy to contribute, but I'd like to be referred to good example of logging in other libraries.

Why would you need that? There's a full API Logs in Mandrill - https://mandrillapp.com/settings/api

Because I can see there only failed API calls, but it's rather useful to know, what's going on under the hood from your side even in non-failed circumstances, as far as mandrill_dm gives you some abstraction layer. I believe that every system should provide information about it's state in some way. Of course I could enable Excon DEBUG mode, for example, but it's to low level.
I'm curious, why api-mandrill gem doesn't have logging capabilities?

 That's quite enough to be informed. Feel free to close this issue.

@Tensho you can close issues that you open, but since I'm commenting here, I'll close it.

After some time of working with Mandrill API Log I'm confident to say that provided search capabilities are far from perfect. It's hard to find needed in the tons of calls (they don't distinguish them as in Outbound Activity panel with filters help). So could my request of logging be considered again ^_^

@kshnurov, @spovich, any thoughts?

Ping

@Tensho I don't have an issue with logs and hasn't been a problem for me.  I'm open to considering a PR, but by default, it should preserve current behavior (extra logging would need to explicitly set in the settings)