text:
Rewrite ReduceOp to support arbitrary reduce operations

Fixes #1285
This changes tt.reduce to replace redOp by a region containing arbitrary code. For example, tl.sum is now lowered as:
%res = "tt.reduce"(%arg0) ({
^bb0(%arg1: f32, %arg2: f32):
  %add = arith.addf %arg1, %arg2 : f32
  tt.reduce.return %add : f32
}) {axis = 1 : i32} : (tensor<128x128xf32>) -> tensor<128xf32>

Support for index reductions at the MLIR level are also dropped in favor of simultaneous reductions over multiple tensors. Which generalizes the code without loss of performance. So for example argmin gets lowered as:
  %7 = tt.make_range {end = 256 : i32, start = 0 : i32} : tensor<256xi32>
  %8 = tt.view %7 : (tensor<256xi32>) -> tensor<1x256xi32>
  %9:2 = "tt.reduce"(%6, %8) ({
  ^bb0(%arg4: f32, %arg5: i32, %arg6: f32, %arg7: i32):
    %14 = arith.cmpf olt, %arg4, %arg6 : f32
    %15 = arith.cmpf ogt, %arg4, %arg6 : f32
    %16 = arith.cmpi slt, %arg5, %arg7 : i32
    %17 = arith.select %16, %arg5, %arg7 : i32
    %18 = arith.select %15, %arg7, %17 : i32
    %19 = arith.select %14, %arg5, %18 : i32
    %20 = arith.cmpf olt, %arg4, %arg6 : f32
    %21 = arith.select %20, %arg4, %arg6 : f32
    tt.reduce.return %21, %19 : f32, i32
  }) {axis = 1 : i32} : (tensor<1x256xf32>, tensor<1x256xi32>) -> (tensor<1xf32>, tensor<1xi32>)

(sorry, things have been busy and haven't had time to review this yet!)

@ptillet do you have any idea when you might have time to review this?

Benchmark related stuff were merged in yesterday, so it's possible the tests got flaky. I'll investigate later today.

Thanks again for the PR @peterbell10 . And thanks @Jokeren for the review.

repo: openai/triton


text:
For using meal-assist it is essential to make sure that units is set to grams

it is possible to change the setting between "exchange" and "grams" in the bolus wizard menue of the pump under Carb. Units. Exchange is used to express how many insulin units are necessary to be given for 1 BE (10 to 12 grams of carbohydrate). In our case it was 0.6 units for 10 grams  of carbs. If the option "grams" is selected the input is how many grams of carbs are necessary for 1 unit of insulin. In this example 16. Meal-assist uses the carb_ratios.json for its calculations and expects the value entered in "grams". If the setting "exchange" is used, it calculates way to aggressive. It should be made clear in the docs how important it is to use the "grams" setting with meal-assist and to implement a verification which setting is used when the JSON-file is generated. If the setting "exchange" is used, the values should be refused and the error message should point to set the setting to "grams"

$ openaps report invoke settings/profile.json && cat settings/profile.json
get-profile://text/shell/settings/profile.json
reporting settings/profile.json
{"max_iob":3,"type":"current","dia":3,"current_basal":1.15,"max_daily_basal":1.3,"max_basal":4,"min_bg":115,"max_bg":115,"sens":40,"carb_ratio":10}

@MosiGitHub Can you please test https://github.com/openaps/oref0/commit/970a5a9d46477558b6c6516215c41109f415acd2 and make sure it prevents use of Exchange units for you?

@scottleibrand thankyou for your fast solution. We are presently on vacation. I will try to check it next week

@MosiGitHub are we good to close this?

I was thinking more of a solution like this (see below). It is not yet tested, because I had lots to do in the last couple of weeks and I just wrote it in the last 5 minutes. But you are asking to close this subject therefor I wanted to make a suggestion how to let the loop run with "exchanges" instead of "grams". I will test it tonight, when my son is in bed and the other rig is running ... I expect that there are some mistakes especially the {} stuff ;-) But the idea behind is that "exchanges" defines how much insulin is needed for 10 or 12 grams of carbohydrates - depending on how you calculate a "BE". so it could be easily transfered to "grams" by dividing the carbohydrate value (10 or 12) by the factor from the pump. I did pretty much the same in the last couple of weeks in a static carb_ratio.json. If it is workinb I will make a PR out of this....
var getTime = require('../medtronic-clock');
function carbRatioLookup (inputs) {
var now = new Date();
var carbratio_data = inputs.carbratio;
if (typeof(carbratio_data) != "undefined" && typeof(carbratio_data.schedule) != "undefined") {
var carbRatio;
if (carbratio_data.units == "grams") {
//carbratio_data.schedule.sort(function (a, b) { return a.offset > b.offset });
carbRatio = carbratio_data.schedule[carbratio_data.schedule.length - 1];
        for (var i = 0; i < carbratio_data.schedule.length - 1; i++) {
            if ((now >= getTime(carbratio_data.schedule[i].offset)) && (now < getTime(carbratio_data.schedule[i + 1].offset))) {
                carbRatio = carbratio_data.schedule[i];
                break;
            }
        }
    } else {
        if (carbratio_data.units == "exchanges") {
        //carbratio_data.schedule.sort(function (a, b) { return a.offset > b.offset });
        carbRatio = carbratio_data.schedule[carbratio_data.schedule.length - 1];

            for (var i = 0; i < carbratio_data.schedule.length - 1; i++) {
                if ((now >= getTime(carbratio_data.schedule[i].offset)) && (now < getTime(carbratio_data.schedule[i + 1].offset))) {
                    carbRatio = (10/carbratio_data.schedule[i]);
                    break;
                }
            }
        } else {
            console.error("Error: Unsupported carb_ratio units " + carbratio_data.units);
            return;
        }
    }
return carbRatio.ratio;
//profile.carbratio = carbRatio.ratio;
} else { return; }

}
carbRatioLookup.carbRatioLookup = carbRatioLookup;
exports = module.exports = carbRatioLookup;

as I made a PR that should work with the setting "exchanges" as well, we can close this issue from my point of view

source: gharchive/issue

authors: MosiGitHub scottleibrand

license: mit

license_type: permissive

license_source: bigquery


text:
Button responsiveness in different views

If you are on a small screen, some of the buttons disappear from the view:

The responsiveness of the buttons and highlighted areas should be improved.

At least the cutting view should be improved by https://github.com/opencast/opencast-editor/pull/1160

authors: Arnei snoesberger

repo: opencast/opencast-editor

license_source: github-api


text:
Ingested mediapackage name is null

Running OC 3.0, during ingestion log displays:
2017-06-28 09:56:19,394 | INFO | (IngestServiceImpl:520) - Ingesting mediapackage 8570483592947531776 is named 'null'
Although we scheduled the event with a title:

{id:'title',label:'EVENTS.SERIES.DETAILS.METADATA.TITLE',type:'text',value:'dummytext'}

As @smarquard commented on list:

We see that on our 2.3.x ingest servers, so it’s at least expected if a little misleading.
Probably the ingest code has not loaded the mediapackage Dublin Core from episode.xml so the title is null at that point.
Probably the log line should be changed to just remove the title. There isn’t much value in having it in the ingest node logs.

The decision was made to not migrate to Github but stay with Bitbucket and Jira.
If this  issue still persists, can you please open a ticket at
https://opencast.jira.com

authors: lkiesow mostolog

repo: opencast/opencast


text:
Gracefully handle missing Shibboleth User References

Shibboleth will usually check on login if a user is present in the
system, importing the user data as user reference if not or continuing
otherwise.
This behavior fails if a user exists but no user reference, causing the
login process to fail.
This might, for example, be caused if another userprovider is active to
supply the roles which a user has while Shibboleth is used for login.
Your pull request should…

[x] have a concise title
[x] close an accompanying issue if one exists
[x] be against the correct branch (features can only go into develop)
[x] include migration scripts and documentation, if appropriate
[ ] pass automated tests
[x] have a clean commit history
[x] have proper commit messages (title and body) for all commits

I did that for @ypatios. They do have this on their system already.

source: gharchive/pull-request


text:
Contacting the team

Hey, I couldn't find any information on how to contact the Open Chat team both in terms of getting support and also for more info on becoming a contributor. Is there a discord server or something?

Hey @ivfarias!
Indeed we have a discord server: https://discord.com/invite/yjEgCgvefr

authors: gharbat ivfarias

repo: openchatai/OpenChat

license: MIT


text:
No PV data in live batches

We see no (or very little PV data in the batches)
This might effect how the model is run, as when training, there are not empty fields

Occasioanly do see results in the reight place, this might be when some PV data is available

For power_perceiver, please can we turn off all interpolation? power_perceiver expects the "raw" (normalised) data, and it can handle PV data that's not at regular time intervals.
And, yeah, having some "old" PV data would be far preferable to having no PV data :slightly_smiling_face:  e.g. let's say we're creating a forecast at 10:00am. And there's no PV data for 9:30am - 10:00am (because PV data takes a while to flow through PVOutput.org). Then it'd be great to be able to give power_perceiver whatever PV data we have for 8:30am-9:30am.
(BTW, if neither PVOutput.org nor Passiv can give us timely PV data, then that feels like a strong argument to build our own data collection system as part of the SBRI project! Getting PV data within seconds of the hardware taking the reading might turn out to be quite important).

We can those options in, intperolate=True
And yea this would be solved if we took a longer history of data.
I think for this issue we should

Load 1.5 hours of pv history
interpolate up to now
only keep 30 mins of history

We should of course keep things flexible for power_perciever but I think right now, we should focus on getting resaonable outputs from CNN.

SGTM!

Another thing we could do is search for some other active sites. This might be a bigger job fro training, but I think this CNN doesnt mind too much

Another thing we could do is search for some other active sites.

Please remind me: When does the code currently update its list of "active" PV sites? (I think I remember suggesting that, for now, we should update the list manually?)

https://eu-west-1.console.aws.amazon.com/cloudwatch/home?region=eu-west-1#logsV2:log-groups/log-group/$252Faws$252Fecs$252Fforecast$252F/log-events/streaming$252Fforecast$252Fe638bb46f6b9427a897a4cda7785249c$3Fstart$3D-60000
Deployed 1.0.16, but not seeing new bug

Deployed 1.0.17, and there re plenty of pv examples now,
Need to check PV data is normalizes correectl now

authors: JackKelly peterdudfield


text:
Fix: Regra de criação de pessoa

Opa, pior que o @eudiegoborgs tinha feito assim mesmo e eu que tirei hihi
Achei que era só pra 3xx, mas serve pro 201 também: https://developer.mozilla.org/en-US/docs/web/http/headers/location
Vivendo e aprendendo.

authors: leocavalcante rafael-neris


text:
Enable email debugging in local environments

Log email text to console in dev environment
Also fixes incorrect port in .env.default

Nice! Thanks for both fixes! \o/

I think there's already DEBUG logic for when the envvar is set to "preview", so could we just add this:
diff --git a/docker/docker-compose.yml b/docker/docker-compose.yml
index b6a3227..8c9e126 100644
--- a/docker/docker-compose.yml
+++ b/docker/docker-compose.yml
@@ -6,6 +6,7 @@ services:
     environment:
       NODE_ENV: "docker"
       SEQUELIZE_ENV: "docker"
+      DEBUG: "preview"
     volumes:
       - ..:/usr/src/api
     ports:
diff --git a/server/lib/email.js b/server/lib/email.js
index 94e63f9..e382edc 100644
--- a/server/lib/email.js
+++ b/server/lib/email.js
@@ -33,6 +33,7 @@ const render = (template, data) => {

   // When in preview mode, we export an HTML version of the email in `/tmp/:template.:slug.html`
   if (process.env.DEBUG && process.env.DEBUG.match(/preview/)) {
+    console.log(text);
     filepath = `/tmp/${template}.${slug}.html`;
     const script = `<script>data=${JSON.stringify(data)};</script>`;
     fs.writeFileSync(filepath, `${html}\n\n${script}`);

fwiw the PR as merged didn't actually write anything to logs, for whatever reason (I'm working in Docker too)

authors: clarete patcon sloria

repo: opencollective/opencollective-api


text:
CI: update setup

use opencollective instead of ubuntu user

@znarf Seems this also needs to be done in the frontend.

@eloyekunle it was done and merged at the same time: https://github.com/opencollective/opencollective-frontend/pull/1808

I'm getting a CI error here: https://circleci.com/gh/opencollective/opencollective-frontend/21574

@eloyekunle It's because the matching API branch was not updated. We should deleted it instead.

Oh okay, will do that. Thanks.

authors: eloyekunle znarf


text:
New collective page initial release

This issue will track the progress for the first iteration of the new collective page.
Files

All components specific to this page will go to components/collective-page
index.js will export the main content component

Tree
└── components
⬜├── collective-page
⬜│⬜├── Hero.js
⬜│⬜├── index.js
⬜│⬜├── NavBar.js
⬜│⬜├── SectionAbout.js
⬜│⬜├── SectionBudget.js
⬜│⬜├── SectionUpdates.js
⬜│⬜├── SectionContributejs
⬜│⬜├── SectionContributors.js
Concepts

The main component (index.js) will be responsible for tracking the scroll position and update children accordingly.
For the first iteration, this page will be mounted on /collective/v2

Don't forget

[x] Migrate the old notification bar

Design

Desktop: https://www.figma.com/file/e71tBo0Sr8J7R5n6iMkqI42d/09.-Collectives?node-id=0%3A7428
Tablet: https://www.figma.com/file/e71tBo0Sr8J7R5n6iMkqI42d/09.-Collectives?node-id=2338%3A36062

The initial release is now ready, we'll use #2225 to collect feedback on it

repo: opencollective/opencollective


text:
NCP: Share buttons icons not centered

Test ID: TES100962421562679330663974
URL Tested: https://opencollective-frontend-madvukrxay.now.sh/webpack/v2
Operating System: Mac 10.12
Browser: Safari 10.1
Resolution: 1024x768

Root cause for this issue: https://github.com/philipwalton/flexbugs#9-some-html-elements-cant-be-flex-containers.

Certain HTML elements, like ,  and , do not work as flex containers. The browser's default rendering of those element's UI conflicts with the display: flex declaration.

Either we center without flex
Or we use a div instead of a button (not good for accessibility)


text:
SFLOW-1: Configure default network instance

Need to configure the default network instance before using it.

Pull Request Functional Test Report for #2641 / f793387c373da67be0f3bddf679e5446c4072f31
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

SFLOW-1: sFlow Configuration and Sampling

Cisco 8000E

SFLOW-1: sFlow Configuration and Sampling

Cisco XRd

SFLOW-1: sFlow Configuration and Sampling

Juniper cPTX

SFLOW-1: sFlow Configuration and Sampling

Juniper ncPTX

SFLOW-1: sFlow Configuration and Sampling

Nokia SR Linux

SFLOW-1: sFlow Configuration and Sampling

Openconfig Lemming

SFLOW-1: sFlow Configuration and Sampling

Hardware Devices

Device
Test
Test Documentation
Raw Log

Arista 7808

SFLOW-1: sFlow Configuration and Sampling

Cisco 8808

SFLOW-1: sFlow Configuration and Sampling

Juniper PTX10008

SFLOW-1: sFlow Configuration and Sampling

Nokia 7250 IXR-10e

SFLOW-1: sFlow Configuration and Sampling

Help

Pull Request Test Coverage Report for Build 7823146341

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

Totals

Change from base Build 7820036790:
0.0%

Covered Lines:
1668

Relevant Lines:
3199

💛  - Coveralls

/fptest all

/fptest virtual

authors: OpenConfigBot coveralls dplore sgirishj

repo: openconfig/featureprofiles


text:
Adress family not supported by protocol

getting following error from the opencost-ui container: [emerg] 1#1: socket() [::]:9096 failed (97: Address family not supported by protocol)nginx: [emerg] socket() [::]:9096 failed (97: Address family not supported by protocol) as there is no ipv6 support in the cloud or rather we only use ipv4.
support is much appreciated

Are you using ipv6? We haven't really tested with it yet, but we'd be happy to merge any patches needed for support.

Hi @mattray !
no, we're using ipv4. is there any known workaround yet?

repo: opencost/opencost-helm-chart


text:
InventoryLevelFilterGlobal

The filter org:opencrx:kernel:depot1:InventoryLevelFilterGlobal allows to define filters for InventoryLevels.

fixed with opencrx-4.2.0+

repo: opencrx/opencrx


text:
CI tool integration

Includes:

Travis CI integration (.travis.yaml)
Codacy Integration
Coveralls.io integration (without a badge)

@DanVev ,
It doesn't work. I will add WIP to title. Could youp please notify me when all problems are resolved?

authors: DanVev nmanovic

repo: opencv/cvat


text:
face_recognition_sface_2021dec_int8.onnx may be have something wrong.

face_recognition_sface_2021dec_int8.onnx may be have something wrong.
I use images of two people，but faceRecognizerSF.match result is 0.999999

`// 3.读取图片
Mat imageA = Imgcodecs.imread("C:/Users/y1793/Desktop/30e480f71265744ba45878e0b94f370.jpg");
Mat imageB = Imgcodecs.imread("C:/Users/y1793/Desktop/68c82edc82763f930777786580de935.jpg");
    Imgproc.resize(imageA, imageA, new Size(imageA.width()/3, imageA.width()/3));
    Imgproc.resize(imageB, imageB, new Size(imageB.width()/3, imageB.width()/3));

    // 4.人脸识别
    FaceDetectorYN faceDetectorYN = FaceDetectorYN.create("C:/Users/y1793/Downloads/face_detection_yunet_2022mar.onnx", "", new Size(), score_thresh, nms_thresh, top_k);
    MatOfRect faceA = new MatOfRect();
    faceDetectorYN.setInputSize(imageA.size());
    faceDetectorYN.detect(imageA, faceA);
    MatOfRect faceB = new MatOfRect();
    faceDetectorYN.setInputSize(imageB.size());
    faceDetectorYN.detect(imageB, faceB);

    for (int i = 0; i < faceA.height(); i++) {
        // 画人脸框
        Imgproc.rectangle(imageA, new Rect((int) (faceA.get(i, 0)[0]), (int) (faceA.get(i, 1)[0]), (int) (faceA.get(i, 2)[0]), (int) (faceA.get(i, 3)[0])), new Scalar(0, 255, 0), 2);
        // 画关键点
        Imgproc.circle(imageA, new Point(faceA.get(i, 4)[0], faceA.get(i, 5)[0]), 2, new Scalar(255, 0, 0), 2);
        Imgproc.circle(imageA, new Point(faceA.get(i, 6)[0], faceA.get(i, 7)[0]), 2, new Scalar(0, 0, 255), 2);
        Imgproc.circle(imageA, new Point(faceA.get(i, 8)[0], faceA.get(i, 9)[0]), 2, new Scalar(0, 255, 0), 2);
        Imgproc.circle(imageA, new Point(faceA.get(i, 10)[0], faceA.get(i, 11)[0]), 2, new Scalar(255, 0, 255), 2);
        Imgproc.circle(imageA, new Point(faceA.get(i, 12)[0], faceA.get(i, 13)[0]), 2, new Scalar(0, 255, 255), 2);
        Imgcodecs.imwrite("C:/Users/y1793/Desktop/imageA.jpg", imageA);
    }

    for (int i = 0; i < faceB.height(); i++) {
        // 画人脸框
        Imgproc.rectangle(imageB, new Rect((int) (faceB.get(i, 0)[0]), (int) (faceB.get(i, 1)[0]), (int) (faceB.get(i, 2)[0]), (int) (faceB.get(i, 3)[0])), new Scalar(0, 255, 0), 2);
        // 画关键点
        Imgproc.circle(imageB, new Point(faceB.get(i, 4)[0], faceB.get(i, 5)[0]), 2, new Scalar(255, 0, 0), 2);
        Imgproc.circle(imageB, new Point(faceB.get(i, 6)[0], faceB.get(i, 7)[0]), 2, new Scalar(0, 0, 255), 2);
        Imgproc.circle(imageB, new Point(faceB.get(i, 8)[0], faceB.get(i, 9)[0]), 2, new Scalar(0, 255, 0), 2);
        Imgproc.circle(imageB, new Point(faceB.get(i, 10)[0], faceB.get(i, 11)[0]), 2, new Scalar(255, 0, 255), 2);
        Imgproc.circle(imageB, new Point(faceB.get(i, 12)[0], faceB.get(i, 13)[0]), 2, new Scalar(0, 255, 255), 2);
        Imgcodecs.imwrite("C:/Users/y1793/Desktop/imageB.jpg", imageB);
    }

    // 5.人脸预处理
    FaceRecognizerSF faceRecognizerSF = FaceRecognizerSF.create("C:/Users/y1793/Downloads/face_recognition_sface_2021dec_int8.onnx", "");
    Mat alignFaceA = new Mat();
    faceRecognizerSF.alignCrop(imageA, faceA, alignFaceA);
    Mat alignFaceB = new Mat();
    faceRecognizerSF.alignCrop(imageB, faceB, alignFaceB);
    Imgcodecs.imwrite("C:/Users/y1793/Desktop/alignFaceA.jpg", alignFaceA);
    Imgcodecs.imwrite("C:/Users/y1793/Desktop/alignFaceB.jpg", alignFaceB);

    // 6.人脸特征提取
    MatOfRect featureA = new MatOfRect();
    faceRecognizerSF.feature(alignFaceA, featureA);
    MatOfRect featureB = new MatOfRect();
    faceRecognizerSF.feature(alignFaceB, featureB);

    // 7.人脸识别 余弦相似度
    double match1 = faceRecognizerSF.match(featureA, featureB, FaceRecognizerSF.FR_COSINE);`

Hi @12341234-yangboran , it's not a bug or something wrong. It's because the value match return is not a score. You need to compare this value with a threshold like OpenCV zoo show below.

Could i use the face_detection_yunet_2022mar.onnx and face_recognition_sface_2021dec_int8.onnx together?

Could i use the face_detection_yunet_2022mar.onnx and face_recognition_sface_2021dec_int8.onnx together?

@12341234-yangboran *_int8.onnx model is used for some specific platform and the inference time will be much less, but accuracy may loss. If your platform doesn't support speed up int8 calculation, I suggest you use the model without int8 suffix version.

can i get the file in this way

@12341234-yangboran I think you can download file in this way.

Hi. I have same issue. In my case the match also returns about 0.9999 for FR_COSINE, and about '0.000` for FR_NORM_L2...
I use OpenCV  4.8.0 running on Windows OS, and your recognition model face_recognition_sface_2021dec.onnx..
I'm sure, that I use two different aligned images... so, something somewhere is wrong.

Ahh.. sorry... seems to need to call clone(), clone() clone() everywhere ))))


text:
Adds the EXISTS CIP

Replaces #8

Comments shared during the CLG meeting:

Change EXISTS for properties to be equivalent to IS NOT NULL - i.e. valid for any expression and only returning true for null values, and not particular and special for graph elements.
All uses of has() should be capitalized
Comment on the fact that UNION subqueries will contain RETURN clauses
Weird layout around line 22
Add example of valid UNION subquery
Add example of valid EXISTS use for checking null and not property
Comment that trailing WITH is only valid together with WHERE

@systay I have made a commit with amendments according to these comments (after discussing this CIP with the CLG), but I can not push it to your fork. Please add me as a collaborator.

Replaced by #120.

authors: Mats-SX systay

repo: opencypher/openCypher


text:
Final fix for Commit Checker GH Action

Description of your changes:
Fixes the Commit Checker GitHub Action to checkout the PR branch before running the check.
Checklist:

[ ] The title for your pull request (PR) should follow our title convention. Learn more about the pull request title convention used in this repository.

Commit Checker results:
**NOTE**: These are the results of the commit checker scans.
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
ERROR: couldn't find commits from effca01ddbe891dc2f1badfb01f30bf20283f3ef..fbb2c121655f10f366449febcdf8f669c4204a88: error executing git log: fatal: Invalid revision range effca01ddbe891dc2f1badfb01f30bf20283f3ef..fbb2c121655f10f366449febcdf8f669c4204a88
: exit status 128

A set of new images have been built to help with testing out this PR:
API Server: quay.io/opendatahub/ds-pipelines-api-server:pr-50
DSP DRIVER: quay.io/opendatahub/ds-pipelines-driver:pr-50
DSP LAUNCHER: quay.io/opendatahub/ds-pipelines-launcher:pr-50
Persistence Agent: quay.io/opendatahub/ds-pipelines-persistenceagent:pr-50
Scheduled Workflow Manager: quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-50
MLMD Server: quay.io/opendatahub/mlmd-grpc-server:latest
MLMD Envoy Proxy: registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2
UI: quay.io/opendatahub/ds-pipelines-frontend:pr-50

An OCP cluster where you are logged in as cluster admin is required.
The Data Science Pipelines team recommends testing this using the Data Science Pipelines Operator.  Check here for more information on using the DSPO.
To use and deploy a DSP stack with these images (assuming the DSPO is deployed), first save the following YAML to a file named dspa.pr-50.yaml:
apiVersion: datasciencepipelinesapplications.opendatahub.io/v1alpha1
kind: DataSciencePipelinesApplication
metadata:
  name: pr-50
spec:
  dspVersion: v2
  apiServer:
    image: "quay.io/opendatahub/ds-pipelines-api-server:pr-50"
    argoDriverImage: "quay.io/opendatahub/ds-pipelines-driver:pr-50"
    argoLauncherImage: "quay.io/opendatahub/ds-pipelines-launcher:pr-50"
  persistenceAgent:
    image: "quay.io/opendatahub/ds-pipelines-persistenceagent:pr-50"
  scheduledWorkflow:
    image: "quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-50"
  mlmd:
    deploy: true  # Optional component
    grpc:
      image: "quay.io/opendatahub/mlmd-grpc-server:latest"
    envoy:
      image: "registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2"
  mlpipelineUI:
    deploy: true  # Optional component
    image: "quay.io/opendatahub/ds-pipelines-frontend:pr-50"
  objectStorage:
    minio:
      deploy: true
      image: 'quay.io/opendatahub/minio:RELEASE.2019-08-14T20-37-41Z-license-compliance'

Then run the following:
cd $(mktemp -d)
git clone git@github.com:opendatahub-io/data-science-pipelines.git
cd data-science-pipelines/
git fetch origin pull/50/head
git checkout -b pullrequest fbb2c121655f10f366449febcdf8f669c4204a88
oc apply -f dspa.pr-50.yaml

More instructions here on how to deploy and test a Data Science Pipelines Application.

Commit Checker results:
**NOTE**: These are the results of the commit checker scans.
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
ERROR: couldn't find commits from effca01ddbe891dc2f1badfb01f30bf20283f3ef..dcbeed87bc061e1737fb14cf1ea540df5e5234f5: error executing git log: fatal: Invalid revision range effca01ddbe891dc2f1badfb01f30bf20283f3ef..dcbeed87bc061e1737fb14cf1ea540df5e5234f5
: exit status 128

Change to PR detected. A new PR build was completed.
A set of new images have been built to help with testing out this PR:
API Server: quay.io/opendatahub/ds-pipelines-api-server:pr-50
DSP DRIVER: quay.io/opendatahub/ds-pipelines-driver:pr-50
DSP LAUNCHER: quay.io/opendatahub/ds-pipelines-launcher:pr-50
Persistence Agent: quay.io/opendatahub/ds-pipelines-persistenceagent:pr-50
Scheduled Workflow Manager: quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-50
MLMD Server: quay.io/opendatahub/mlmd-grpc-server:latest
MLMD Envoy Proxy: registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2
UI: quay.io/opendatahub/ds-pipelines-frontend:pr-50

Commit Checker results:
**NOTE**: These are the results of the commit checker scans.
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
Validating 0 commits between 6623b7cc19b13b371af67b209f965afdff47dfd4...dcbeed87bc061e1737fb14cf1ea540df5e5234f5

authors: dsp-developers rimolive

repo: opendatahub-io/data-science-pipelines


text:
Add projects' descriptions to projects list view

Closes RHOAIENG-10493
Description
Adds the project description to the name column in the projects list view
How Has This Been Tested?
Manually, added e2e test check
Test Impact
None
Screen shot

Request review criteria:
Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

[x] Included any necessary screenshots or gifs if it was a UI change.
[x] Included tags to the UX team if it was a UI/UX change.

/cc @tobiastal

/lgtm
/approve

repo: opendatahub-io/odh-dashboard


text:
Fix Oauth Issues when retrieving username

Description

This PR contains the following:

Add custom error code when retrieving username

It will return 401 when the token is deprecated or there is no token
It will return the default error code of the oc get request in other cases (when there's a cluster problem it will be 500)

Fixes an issue when the dashboard cannot redirect to oauth proxy and keeps a loop.

How Has This Been Tested?

In local:

Comment this line to trigger the error.
Now the frontend should not reload when displaying the error message.
Check that is returning a 401 since the token is not provided.
Get a /status call with the cookie session of the cluster.
It should return a 200 response.
Now disconnect from the VPN to emulate connection issues.
It should return a 500 response.

In the cluster:

Deploy the cluster without the oauth proxy.
It will display the error page, with a 401 error response. It won't auto-reload all the time.

Merge criteria:

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

Deploy the cluster without the oauth proxy.

Looks like impossible to happen in real clusters since oauth proxy is always deployed with the dashboard. Why the issue should happen? @lucferbux

@bdattoma this might happen when oauth proxy is down or unavailable.

@bdattoma this might happen when oauth proxy is down or unavailable.

yeah but oauth proxy should not be down, if it is down there must be something wrong happening in the cluster. So I wonder if it'd better to leave the alerts to fire. Would these change prevent the alert from firing?

@bdattoma this might happen when oauth proxy is down or unavailable.

yeah but oauth proxy should not be down, if it is down there must be something wrong happening in the cluster. So I wonder if it'd better to leave the alerts to fire. Would these change prevent the alert from firing?

Yes, i think it might help, but then again, im not able to replicate the error as it's happening in the cluster, at least i think the logic behind the code will help

@bdattoma this might happen when oauth proxy is down or unavailable.

yeah but oauth proxy should not be down, if it is down there must be something wrong happening in the cluster. So I wonder if it'd better to leave the alerts to fire. Would these change prevent the alert from firing?

@bdattoma I've not seen on production clusters oauth going down, even though it's used here as a device for reproducing the bug.  From what I saw it was just 1 user who had an bad token and the page was refreshing.  A 500  from our dashboard is because we're improperly handling the request, so a 401 makes more sense here.  If we want to detect downtime in oauth proxy, then we should put an alert on oauth proxy and read it's log.

@lucferbux @cfchase so if I understand correctly, the problem which needs Fixes an issue when the dashboard cannot redirect to oauth proxy and keeps a loop. was seen only while trying to simulate the bug by killing the oauth proxy. Is that correct?
I initially understood the oauth proxy was seen as down somewhere so you applied the fix.

@lucferbux @cfchase so if I understand correctly, the problem which needs Fixes an issue when the dashboard cannot redirect to oauth proxy and keeps a loop. was seen only while trying to simulate the bug by killing the oauth proxy. Is that correct? I initially understood the oauth proxy was seen as down somewhere so you applied the fix.

@lucferbux can correct me if he's seen otherwise, but that's correct from what I've seen.  Even if it was otherwise this fix is still the right answer for our dashboard and we should never 500.  There are better ways to check the oauth proxy.

@cfchase  Yes right, this will solve all the related 500 issues since it will return the right status code.

okay got it thanks for clarifications. Only one last question: is the bad token case caused by login session expiration? or what else?

okay got it thanks for clarifications @lucferbux @cfchase . Only one last question: is the bad token case caused by login session expiration? or what else?

I was not able to determine the root cause definitively.

authors: bdattoma cfchase lucferbux


text:
Proposal for Distributed Workloads

Proposal for Distributed Workloads and Workload Orchestration
Description
Adding written proposal for Distributed Workloads and Workload Orchestration
How Has This Been Tested?
Proposal does not affect other areas of the code, and hence, was not tested.
Merge criteria:

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

/lgtm

authors: heyselbi taneem-ibrahim

repo: opendatahub-io/opendatahub-community


text:
CI: Partially revert "CI/Bats: fix the backtrace selftest again"

This partially reverts commit efbb4e0c454125f3030e618190e3e0bd154abc62 (PR #238), restoring the requirement to test gdb if gdb is found to be working, but changing what we test of gdb. Instead of trying to start and run a process, we instead ask gdb to attach to a running process, which is what our child_debug.cpp does.

@busykai can you test that this correctly detects whether gdb will work inside child_debug.cpp?

repo: opendcdiag/opendcdiag


text:
add 1.2 announcement

new announcement with 1.2 features

@rattermeyer  / @tjaeschke  -
merged and 30 minutes still NOT at http://www.opendevstack.org/blog/index.html
whats going on there?

fixed with #116

authors: clemensutschig tjaeschke


text:
feature(pu): add NGU algorithm

Add exploration-RL algorithm NGU. Note that NGU algorithm has not been completed yet, it will being updated continuously.

Hi, is NGU now ready to use?

Hi,
Thank you very much for your question! Yes, our implemented NGU algorithm is ready to use.

We tested it on the minigrid environment. In the hard-exploration env MiniGrid-DoorKey-16x16-v0, our implemented NGU algorithm converged at about 30M  env steps, which is aligned with the results in the unpublished paper.
The learning curve for 2 seeds is as follows:

You can run this entry config https://github.com/opendilab/DI-engine/blob/main/dizoo/minigrid/config/minigrid_ngu_config.py to train NGU agent in MiniGrid env.
For the algorithm details of NGU, you can refer to our Chinese blog. For more paper information about exploration in RL, you can refer to our awesome-exploration-rl repo.

Good Luck!

@puyuan1996, Great thank you 蒲源.

Hi, is NGU now ready to use?

Hi,
Thank you very much for your question! Yes, our implemented NGU algorithm is ready to use.

We tested it on the minigrid environment. In the hard-exploration env MiniGrid-DoorKey-16x16-v0, our implemented NGU algorithm converged at about 30M  env steps, which is aligned with the results in the unpublished paper.
The learning curve for 2 seeds is as follows:

You can run this entry config https://github.com/opendilab/DI-engine/blob/main/dizoo/minigrid/config/minigrid_ngu_config.py to train NGU agent in MiniGrid env.
For the algorithm details of NGU, you can refer to our Chinese blog. For more paper information about exploration in RL, you can refer to our awesome-exploration-rl repo.

Good Luck!

@puyuan1996, Hi, did you run experiments on Atari hard exploration environments, such as Montezuma Revenge?

repo: opendilab/DI-engine


text:
fix_formatted_config_bug_eval

Description
Related Issue
TODO
Check List

[ ] merge the latest version source branch/repo, and resolve all the conflicts
[ ] pass style check
[ ] pass all the tests

Codecov Report

Merging #53 (38ec74f) into main (1318901) will decrease coverage by 0.18%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #53      +/-   ##
==========================================
- Coverage   88.96%   88.77%   -0.19%
==========================================
  Files         349      349
  Lines       25972    25678     -294
==========================================
- Hits        23105    22795     -310
- Misses       2867     2883      +16

Flag
Coverage Δ

unittests
88.77% <ø> (-0.19%)
:arrow_down:

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

Impacted Files
Coverage Δ

ding/entry/tests/test_parallel_entry.py
45.45% <0.00%> (-4.55%)
:arrow_down:

ding/envs/env_manager/subprocess_env_manager.py
80.62% <0.00%> (-3.03%)
:arrow_down:

ding/utils/tests/test_k8s_launcher.py
91.66% <0.00%> (-2.22%)
:arrow_down:

ding/entry/tests/test_serial_entry.py
77.04% <0.00%> (-2.22%)
:arrow_down:

ding/utils/tests/test_system_helper.py
80.00% <0.00%> (-1.82%)
:arrow_down:

ding/rl_utils/tests/test_ppg.py
27.50% <0.00%> (-1.77%)
:arrow_down:

ding/rl_utils/tests/test_gae.py
61.90% <0.00%> (-1.74%)
:arrow_down:

ding/utils/data/tests/test_dataloader.py
31.25% <0.00%> (-1.68%)
:arrow_down:

ding/utils/data/dataloader.py
46.11% <0.00%> (-1.04%)
:arrow_down:

ding/torch_utils/tests/test_data_helper.py
73.85% <0.00%> (-0.99%)
:arrow_down:

... and 118 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 1318901...38ec74f. Read the comment docs.


text:
Persistlabels

To work with sbercloud, you need to add labels to the VPC
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.

Hi @Vastyjoy ,
Can you please inform more on why this change is needed. I think the persistence labels can be used on the custom need of a user, based on their environment. This change is an enhancement but might not be needed by all, please provide more information.  Also please attach test results for further review.
Thanks for contribution.

Hi @Vastyjoy,
I am closing this PR as there was no response to the query. Please feel free to reopen the PR or submit new one with the requested information and test results.
Thanks for your contribution.

authors: Vastyjoy sreekarjami


text:
LDAPS connections not closing

Hi guys ,
Have configured LDAP authc and authz to query an LDAPS server and noticed that connections to the LDAPS server are not closing. Every subsequent LDAP auth query adds 2 new connections that stay open until forcibly terminated.
Not seeing the same issue on queries against the same LDAP server from an Elasticsearch cluster with the X-Pack LDAP implementation. LDAP queries are serviced and the connection is closed in a timely manner.
Have compared a traffic capture from both implementations to see if there is a difference, see attached (ldap-opendistro.png, ldap-xpack.png) .
In both examples , 10.0.42.5 is the client and 10.0.42.6 is the LDAP server.

Have noticed that in the case of the connections that do not close, the client never ACKS the servers FIN/ACK when the connection is closing. I'm wondering if this is responsible for the open connections.
What do you think about this, is this a known issue?
Package and OS details :
Distributor ID: Debian
Description:    Debian GNU/Linux 9.9 (stretch)
Release:        9.9
Codename:       stretch
elasticsearch-oss               7.2.0
opendistro-alerting             1.2.0.0-1
opendistro-job-scheduler        1.2.0.0-1
opendistro-performance-analyzer 1.2.0.0-1
opendistro-security             1.2.0.0-0
opendistro-sql                  1.2.0.0-1
opendistroforelasticsearch      1.2.0-1
LDAP Server - OpenLDAP
slapd                               2.4.40+dfsg-1+deb8u3
Cheers

I can confirm that I experience the same issue.

Experiencing the same issue. @gplechuck @Jakob3xD question for you guys: how fast does LDAP work for you? We are seeing LDAP queries take 10-15 seconds and have ensured our queries run adequately using ldapsearch
Would really appreciate help on the issue @opendistrocommunity

We have added fixed some of the leaked LDAP connection issues through this PR: https://github.com/opendistro-for-elasticsearch/security-advanced-modules/pull/57
This might solve a problem.

We are also seeing this leak in ES 6.7.2, any plans on back porting this fix?

Thanks @hardik-k-shah
Installed Elasticsearch 7.3.2 and built the security plugin v 1.3.0 and can confirm that the issue appears to be resolved.
Would you know when the official release of 1.3.0 is scheduled for?

authors: Jakob3xD avanand-git gplechuck hardik-k-shah manavkapoor

repo: opendistro-for-elasticsearch/security


text:
feat(device, scheduler, capacity): implement CSI methods for volume operations

implement Create/Delete Volume and GetCapacity calls
add DeviceNode CRD
update vendor dependencies
add VolumeWeighted and CapacityWeighted scheduler

cc: @AmitKumarDas

repo: openebs/device-localpv


text:
fix(helm): remove useless crd.enableInstall variable

What this PR does?:
remove the useless crd.enableInstall variable which has no reference in helm chart.
Does this PR require any upgrade changes?:
no

Has been cherry-picked in https://github.com/openebs/lvm-localpv/pull/284 Thanks!!

repo: openebs/lvm-localpv


text:
feat(topology): add poolTopologyAffinity/poolTopologySpread in Storage Class

Test case

No:
Details
Expected result

1
the volume replicas has topology inclusion labels matching to the labels as that of certain pools
volume creation should succeed with a returned volume object with topology

2
the volume replicas has topology inclusion labels not matching with any pools with labels
volume creation should fail with an insufficient storage error

3
the volume replicas has topology exclusion labels key matching with any pools with labels key and not value
volume creation should succeed with a returned volume object with exclusion topology key same as pool key and different value

4
the volume replicas has topology inclusion labels and exclusion labels same
replica creation should fail with an insufficient storage error

Please separate into multiple commits (core-agent scheduling, csi-driver, etc) Also tests are missing, please add them

added

Is that not the same for pools?

poolTopologyAffinity: "foo"
replica1: "foo: doo" <- A determined at creation time
replica2: "foo: bah"

Is that not the same for pools?

poolTopologyAffinity: "foo"
replica1: "foo: doo" <- A determined at creation time
replica2: "foo: bah"

As per the initial design it was not , but to make poolTopologyAffinity consistent with nodeTopologyAffinity
I have added the same

bors merge

bors merge

authors: sinhaashish tiagolobocastro

repo: openebs/mayastor-control-plane


text:
build: support podman for load/pushing container images

By default docker is tried, and then podman.
Support is simplistically verified with the exit code from --version.
First choice can be overridden with DOCKER env variable.

Making the same changes on all repos would be a pain, so instead I'm adding a common release script which all repos can make use of: https://github.com/openebs/mayastor-dependencies/pull/88

bors try

bors merge

bors merge

repo: openebs/mayastor


text:
tests(integration): print ndm logs if an integration test fails

ndm logs are necessary to debug issues with integration tests. print the
ndm pod logs if a test fails
Signed-off-by: Aditya Jain aditya.jainadityajain.jain@gmail.com
Why is this PR required? What issue does it fix?:
there have been multiple flaky integration test runs in the ndm ci pipeline. There's an open issue to fix these tests (#625). However, it is difficult to debug the test runs on github ci since the ndm logs aren't available. This PR aims to solve the problem.
Checklist:

[x] PR Title follows the convention of  <type>(<scope>): <subject>
[ ] Has the change log section been updated? (NA)
[ ] Commit has unit tests (NA)
[ ] Commit has integration tests (NA)

Codecov Report

Merging #637 (2568b22) into master (516a403) will decrease coverage by 0.95%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #637      +/-   ##
==========================================
- Coverage   47.34%   46.38%   -0.96%
==========================================
  Files          78       78
  Lines        3781     3781
==========================================
- Hits         1790     1754      -36
- Misses       1836     1871      +35
- Partials      155      156       +1

Impacted Files
Coverage Δ

cmd/ndm_daemonset/probe/eventhandler.go
30.55% <0.00%> (-8.34%)
:arrow_down:

cmd/ndm_daemonset/probe/addhandler.go
71.33% <0.00%> (-6.15%)
:arrow_down:

cmd/ndm_daemonset/probe/udevprobe.go
48.53% <0.00%> (-5.03%)
:arrow_down:

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 516a403...2568b22. Read the comment docs.

repo: openebs/node-disk-manager


text:
Add short script to move vendor folder around

What

Extract the vendor and modules cleanup into a separate shell script.
This provides more space for documenting each step cleanly.
This scripting also removes the need for the GO_REPLACE.txt hack,
it will automatically modify any local replacements in the original
go.mod file, so that they work as expected.
Update the README to describe how dependencies work in the three
supported modes: modules with vendoring, modules without vendoring,
and traditional vendoring via dep.
This new flow allows dynamic downloading of Go modules or disabling
Go modules and only using vendor. You can not use vendor and modules
at the same time due to how Go will validate that the vendor folder
and the go.mod are insync

Description
How Has This Been Tested?

You can test this branch of the template using
$ faas-cli template pull https://github.com/LucasRoesler/golang-http-template#impr
oved-module-and-vendor-support
$ faas-cli new --lang golang-http

I manually tested with this handler implementation
#  publisher/handler.go
package function

import (
	"bytes"
	"fmt"
	"log"
	"net/http"
	"os"

	nats "github.com/nats-io/nats.go"
	handler "github.com/openfaas/templates-sdk/go-http"
)

var (
	subject        = "nats-test"
	defaultMessage = "Hello World"
)

// Handle a function invocation
func Handle(r handler.Request) (handler.Response, error) {
	var err error

	msg := defaultMessage
	if r.Body != nil {
		msg = string(bytes.TrimSpace(r.Body))
	}

	natsURL := nats.DefaultURL
	val, ok := os.LookupEnv("nats_url")
	if ok {
		natsURL = val
	}

	nc, err := nats.Connect(natsURL)
	if err != nil {
		errMsg := fmt.Sprintf("can not connect to nats: %s", err)
		log.Print(errMsg)

		return handler.Response{
			Body:       []byte(errMsg),
			StatusCode: http.StatusInternalServerError,
		}, err
	}
	defer nc.Close()

	s := r.Header.Get("nats-subject")
	if s != "" {
		subject = s
	}

	log.Printf("Publishing %d bytes to: %q\n", len(msg), subject)

	err = nc.Publish(subject, []byte(msg))
	if err != nil {
		log.Println(err)

		return handler.Response{
			Body:       []byte(fmt.Sprintf("can not publish to nats: %s", err)),
			StatusCode: http.StatusInternalServerError,
		}, err

	}
	return handler.Response{
		Body:       []byte(fmt.Sprintf("Published %d bytes to: %q", len(msg), subject)),
		StatusCode: http.StatusOK,
	}, err
}

How are existing users impacted? What migration steps/scripts do we need?
Users should not notice any change.
Checklist:
I have:

[ ] updated the documentation and/or roadmap (if required)
[x] read the CONTRIBUTION guide
[x] signed-off my commits with git commit -s
[ ] added unit tests

This looks good. Do you have any concerns or areas where I can help with testing / validation?

This looks good. Do you have any concerns or areas where I can help with testing / validation?

This change is not 100% backwards compatible. For example, there is no support for vendor and modules at the same time. When modules is enabled, it will always attempt to download the modules. Which could be an issue for things like private modules. These users must use vendoring with go mod vendor but then disable modules with the build arg.
I don't know about any other configurations, e.g. existing functions using vendoring and dep, we should test that. I am not sure about any other configurations we want to support

golang-middleware template:

[x] Go modules on, public modules, no vendor folder, gets downloaded every time
[x] Go modules off, with a vendor folder (using GOPATH)
[ ] Go modules on, with a vendor folder

In Go 1.17, this will fail, because go modules are always forced on, and you cannot build from GOPATH

[x] Go modules off, with a vendor folder

golang-http template:

[x] Go modules on, public modules, no vendor folder, gets downloaded every time
[ ] Go modules off, with a vendor folder (using GOPATH)
[ ] Go modules on, with a vendor folder

Couple of suggestions for things to try:
1 - lift the handler/function code up one level and overwrite the go.mod/sum of the main entrypoint
2 - Copy the files directly into the main entrypoint and rename that to "function" so that there's no "import" needed.

@alexellis i have pushed a change that lifts the go.mod/go.sum to the main entrypoint, but only for the http template. With this, i have had successful builds with

modules ON, no vendor folder
modules ON, with vendor folder
modules OFF, with vendor folder

This also includes have sub-packages in my handler code, here is the structure of my test function with the vendor folder
├── publisher
│   ├── go.mod
│   ├── go.sum
│   ├── handler.go
│   ├── pkg
│   │   └── version
│   │       └── version.go
│   └── vendor
│       ├── github.com
│       │   ├── nats-io
│       │   │   ├── nats.go
│       │   │   │   ├── CODE-OF-CONDUCT.md
│       │   │   │   ├── context.go
│       │   │   │   ├── dependencies.md
│       │   │   │   ├── enc.go
│       │   │   │   ├── encoders
│       │   │   │   │   └── builtin
│       │   │   │   │       ├── default_enc.go
│       │   │   │   │       ├── gob_enc.go
│       │   │   │   │       └── json_enc.go
│       │   │   │   ├── go.mod
│       │   │   │   ├── go.sum
│       │   │   │   ├── GOVERNANCE.md
│       │   │   │   ├── js.go
│       │   │   │   ├── jsm.go
│       │   │   │   ├── LICENSE
│       │   │   │   ├── MAINTAINERS.md
│       │   │   │   ├── nats.go
│       │   │   │   ├── netchan.go
│       │   │   │   ├── parser.go
│       │   │   │   ├── README.md
│       │   │   │   ├── timer.go
│       │   │   │   ├── TODO.md
│       │   │   │   └── util
│       │   │   │       ├── tls.go
│       │   │   │       └── tls_go17.go
│       │   │   ├── nkeys
│       │   │   │   ├── crc16.go
│       │   │   │   ├── creds_utils.go
│       │   │   │   ├── go.mod
│       │   │   │   ├── go.sum
│       │   │   │   ├── GOVERNANCE.md
│       │   │   │   ├── keypair.go
│       │   │   │   ├── LICENSE
│       │   │   │   ├── main.go
│       │   │   │   ├── MAINTAINERS.md
│       │   │   │   ├── public.go
│       │   │   │   ├── README.md
│       │   │   │   ├── strkey.go
│       │   │   │   └── TODO.md
│       │   │   └── nuid
│       │   │       ├── GOVERNANCE.md
│       │   │       ├── LICENSE
│       │   │       ├── MAINTAINERS.md
│       │   │       ├── nuid.go
│       │   │       └── README.md
│       │   └── openfaas
│       │       └── templates-sdk
│       │           ├── go-http
│       │           │   ├── handler.go
│       │           │   └── README.md
│       │           └── LICENSE
│       ├── golang.org
│       │   └── x
│       │       └── crypto
│       │           ├── AUTHORS
│       │           ├── CONTRIBUTORS
│       │           ├── ed25519
│       │           │   ├── ed25519.go
│       │           │   ├── ed25519_go113.go
│       │           │   └── internal
│       │           │       └── edwards25519
│       │           │           ├── const.go
│       │           │           └── edwards25519.go
│       │           ├── LICENSE
│       │           └── PATENTS
│       ├── handler
│       │   └── function
│       │       └── pkg
│       │           └── version
│       │               └── version.go
│       └── modules.txt

It is important to note that this requires a small bit of schenanigens for local development, specifically, if you have sub-packages, then you need to import them relative to handler/function/...., not the "actual" function/... and then you need to add a replace of handler/function => ./
This is what the function/go.mod looks like so that local development works as expected
module function

go 1.16

require (
	github.com/nats-io/nats.go v1.10.1-0.20210228004050-ed743748acac
	github.com/openfaas/templates-sdk v0.0.0-20200723110415-a699ec277c12
	handler/function v0.0.0-00010101000000-000000000000
)

replace handler/function => ./

A side of effect of this approach is that the GO_REPLACE.txt is not needed anymore because we are just copying the go.mod to the project root, it will contain any of the original replace statements anyway.

Question for you - could this be a bash script that's copied in from the base template?

From our call - what does a sub-package look like now with these changes?

@alexellis i have moved the logic to a shell script now.  Note, from the commit message, this will automatically handle the GO_REPLACE so that we don't need the extra file anymore:

Extract the vendor and modules cleanup into a separate shell script.
This provides more space for documenting each step cleanly.
This scripting also removes the need for the GO_REPLACE.txt hack,
it will automatically modify any local replacements in the original
go.mod file, so that they work as expected.
Update the README to describe how dependencies work in the three
supported modes: modules with vendoring, modules without vendoring,
and traditional vendoring via dep.

I would like to also commit a sample function to the repo, what do you think? It would be really helpful to have a test/sample function that we can all reference as a baseline verification that the template compiles, at least for the two module use cases: with and without vendoring.

ping-ity ping ping

@alexellis can you re-review this and let me know what needs to be done for it to be merged?  I feel like it is ready to be merged

Approved. Let's see how we get on with this.
Will the script work on Alpine Linux's shell (ash) and on Ubuntu's bash shell?

@alexellis the script is written and run using sh which i believe is a subset of both ash and bash, so it should be fine

authors: LucasRoesler alexellis

repo: openfaas/golang-http-template


text:
Feature/#75: Improved unpublished node styling ensuring high-contrast visibility (Drupal 9-10)

This pull request relates to BOSA_0100-196 (JIRA issue) and contains styling updates improving the default Drupal behavior when a node is unpublished by ensuring high-contrast visibility.
This pull request will be merged with the 3.0.x (Drupal 9-10) branch.

I need to recreate a clean new branch for this issue from the latest update of the 3.0.x branch.

repo: openfed/kiso


text:
flutter_secure_storage plugin needs compileSdkVersion 33

What
While building locally for #2747 I noticed that:
Warning: The plugin flutter_secure_storage requires Android SDK version 33.
For more information about build configuration, see https://docs.flutter.dev/deployment/android#reviewing-the-build-configuration.
One or more plugins require a higher Android SDK version.
Fix this issue by adding the following to E:\111 Programming\Flutter\smooth-app\packages\smooth_app\android\app\build.gradle:
android {
  compileSdkVersion 33
  ...
}

https://pub.dev/packages/flutter_secure_storage
Since it's just the compile not the min version it's shouldn't exclude devices but we have to check what the playstore says

Since Flutter does still rely on 32, we should force staying on the previous version.
33 has some breaking changes

An open discussion on flutter_secure_storage:

On Android, when the app is uninstalled, all data stored with this plugin is removed
On iOS, the content is persisted https://medium.com/@isuru.nan/beware-of-fluttersecurestorage-on-ios-542e4c9d6a3

Shouldn't we use another plugin?

If you have a good alternative

Just add the following in the buid.gradle file:
android{
defaultConfig{
minSdkVersion 18

Your highest target API level is Android 12 (API level 31).
To ensure that you can continue to make updates to your app you must:
Update your app to target Android 13 (API level 33).
Publish a new version of your app to production. Before you do this, you can test your app using internal, closed, or open testing.

repo: openfoodfacts/smooth-app


text:
Scale MW back by Avogadro's number

Description
Fixes #568
Todos
Notable points that this PR has either accomplished or will accomplish.

This scales the MW back and adds more granular tests.
It also adds some __repr__ functions I used while debugging, which can be removed but might be nice for future debugging!

Ah, forgot about forks and OpenEye...
On the runs without OpenEye and without the fix, the tests of converting solvent mole fractions and molality fail, as well as the slightly stronger test of loading a ThermoMLDataset from an XML file with molality constraints (test_thermoml_molality_constraints) and checking multiple components are parsed.

Apologies for the failing OpenEye tests, but I think this is ready for review!

Merged #570

Thanks Matt!

authors: lilyminium mattwthompson

repo: openforcefield/openff-evaluator


text:
Make OpenEye loading failure explicitly say "Warning"

Many users are confused by the red message indicating that OETK can't be loaded. Let's make sure this starts with Warning:  to make it clear that this is non-fatal.

Same here: In AmberToolsToolkitwrapper.computer_partial_charges_am1bcc: Molecule 'DrugBank_2799' has more than one conformer, but this function will only generate charges for the first one.

Changed to
Warning: Unable to load toolkit 'OpenEye Toolkit'. Versions of the Open Force Field Toolkit past 0.2.0 (April 2019) do not require the OpenEye Toolkits and will use RDKit and AmberTools as a backend instead. However, if you have an OpenEye license available, consider installing the OpenEye toolkits for faster performance and I/O of additional file formats.
in #425

That's a dramatically better message. :)

authors: davidlmobley j-wags

repo: openforcefield/openforcefield


text:
Merge models refactor trunk

[ ] Get test coverage back up
[ ] Add plotting back to helper script
[ ] Update linters/tooling
[ ] Run type-checking
[ ] Use Pydantic V2 API
[ ] Docs?

Codecov Report
Attention: Patch coverage is 81.25000% with 21 lines in your changes missing coverage. Please review.

Project coverage is 84.68%. Comparing base (0a94095) to head (8416ea8).

Additional details and impacted files

authors: codecov-commenter mattwthompson

repo: openforcefield/yammbs


text:
Amiga is out of date

Amiga is already at version 0.1.1, but the file here still shows 0.1.0. Shouldn't it be automatic?

Amiga is already at version 0.1.1, but the file here still shows 0.1.0. Shouldn't it be automatic?

Thank you for reporting the issue.
The version is determined by the contents of the cores.json as described in the Analogue documentation.
In the case of the Amiga, the cores.json hasn't been updated to reflect the GitHub release version.
You can confirm this by checking it out here: https://github.com/Mazamars312/Analogue-Amiga/blob/main/dist/Cores/Mazamars312.Amiga/core.json

@rsn8887 After further investigation, it appears you're correct. The API still points to the previous release as it hasn't been updated.
As a result, I opened a PR for the Amiga core to address the issue (https://github.com/Mazamars312/Analogue-Amiga/pull/26). In the meantime, I'll manually update the reference to the latest release.

Closed as per the latest release of the Amiga core.


text:
Some issues with the Dynamizer model

The current version of the Dynamizer module has two issues that need to be revisited:

The SensorConnection class should be carefully examined, if it can be used to represent links to sensor services that are compliant to the OGC SensorThings API as well as to the OGC Sensor Observation Service (SOS). Also other types of platforms like ThingSpeak, OpenSensors etc. should be supported. It should also become possible to model links to MQTT based sensor services. Furthermore it should be indicated what kind of authentication mechanism has to be used for each specific sensor connection.
In the current schema the data models of the OGC standards TimeSeriesML and Observations & Measurements (O&M) are being imported to enable users to embed TimeSeriesML and O&M documents within the CityGML file. However, it turned out that for an implementation of the Dynamizer module the entire concepts from the two OGC standards would also need to be implemented, which is not practical. Instead, it should be just possible to link to an external file that is compliant to one of these standards. A very simple encoding of time value pairs that include int, double, appearances, geometries, and ImplicitGeometries should also be supported.

Please find attached a revised Dynamizer module that addresses the issues mentioned above:
2019_10_28_Dynamizer with code lists.pdf

Please find attached the presentation slides illustrating the usage of the revised Dynamizer module.
The presentation shows numerous concrete examples of how to connect city objects with sensors and IoT devices registered with the OGC SensorThings API and OGC Sensor Observation Service servers as well as with other popular platforms using HTTP and MQTT protocols.
The examples are also given on how the results of a solar potential analysis can be represented in different ways and linked with the building surfaces.
2019_10_29_Dynamizer_Examples.pdf

In the 31 October meeting some requirement of time periods to not overlap was mentioned. As I remember, this limitation would affect either multiple time series within one dynamizer (Dynamizer.dynamicData) or multiple dynamizers referring to the same particular attribute of the same particular object.
I can not find anything related to this in the documents attached to the previous posts. Thus I want to confirm whether it is possible to have multiple alternative time series for the same attribute and the same or overlapping time period. Cases for this would be, for example, measuring the same value with different technology or attaching both simulation results and measured values to one particular object.
It would also be reasonable to deny this possibility and allow for CityGML3 to just describe the state of city objects during their lifetime in one particular existence or reality. This would still very much extend CityGML2 which was limited to describe the state of city objects at one particular point in time.

Please find here the latest version of the Dynamizer UML model that is also included in the latest eap file (commit ae8c197) and encoded in the XML schema files (commit https://github.com/opengeospatial/CityGML-3.0Encodings/commit/bb0c6dcddff79208cb227a7092faa80834c76e5f): 2019_11_01_Dynamizer with code lists.pdf
The only modification to the previous version is that the attribute appearanceValue is now of the type AbstractAppearance instead of Appearance. In this way no dependency between the Dynamizer module and the Appearance module exists any more in the XML schema files.

Two more things should be improved in the most recent Dynamizer data model:

The properties firstTimestamp and lastTimestamp of the class AbstractAtomicTimeseries should be moved one level higher in the generalization hierarchy (into the class AbstractTimeseries), because these attributes are also useful for CompositeTimeseries. They would then be inherited by both classes AbstractAtomicTimeseries and CompositeTimeseries.

In the class TabulatedFileTimeseries we should give users the choice how to reference a specific column in a tabulated datafile - by column number or column name. Therefore, instead of having the properties idColumn, timeColumn, and valueColumn, we should have the following properties:
idColumnNo: Integer [0..1]
idColumnName: CharacterString [0..1]
idValue: CharacterString [0..1]
timeColumnNo: Integer [0..1]
timeColumnName: CharacterString [0..1]
valueColumnNo: Integer [0..1]
valueColumnName: CharacterString [0..1]
The property idValue would then specify that only those rows from the file are being selected, where the value in the idColumn matches the specified idValue. This allows, for example, to have a large CSV file that has e.g. the solar irradiation values for all thematic surfaces of a city model for each month in a year. In this case, a Dynamizer can be created for each RoofSurface or WallSurface feature, which all refer to the same CSV file, but using a different idValue to select the proper rows from the file for the respective RoofSurfaces and WallSurfaces.

Please find here the UML model that includes the above-mentioned things to be improved 2019_11_05_Dynamizer with code lists.pdf

Based on the discussion in the web conference on 8 November 2019 the following things were updated in the latest commit:

The data type URI was changed to CharacterString for the attributes attributeRef, linkToObservation, and linkToSensorDescription, because XPath expressions cannot be encoded as xs:anyURI, only as xs:string.
The stereotype of the class AuthenticationValue was changed from <<Enumeration>> to <<CodeList>> to allow for additional values.
The role name isComponent was renamed to component.

Please find attached the updated slides illustrating the usage of the finalised Dynamizer module:
2019_11_10_Dynamizer_Examples.pdf
Here are three CityGML 3.0 test datasets. Each dataset contains the same building, but with different kinds of Dynamizers (two are making connections to an external sensor service using the OGC SensorThings API, one includes inline timeseries data): Dynamizer_Examples.zip

authors: TatjanaKutzner hlg kanishk-chaturvedi thomashkolbe


text:
Option to make the globe visible to user after all the canvas in the whole globe(except pole?) is ready and expose a way to let the developer know when rendering is complete

currently when user rotate, there is visible experience gap before newly rotated view ready. need an option to make the globe visible to user after all the canvas in the whole globe is ready. then it will have smooth user experience when rotate. also need expose a way to let the developer know when rendering is complete so that they can do some other job.

I'm not sure that it is possible 100% especially making the globe visible to user after all the canvas in the whole globe is ready, but:

I can implement something like "rendercomplete" event, when every segment on the screen is completed, and nothing is loading.
I can add option that makes whole globe rendered when you see whole globe sphere from far space, it will helps to avoid empty tiles when user rotates the globe.

Hey @yeluoyunfei rendercomplete is enough?

Yes. I think it's ok for currently

authors: Zemledelec yeluoyunfei

repo: openglobus/openglobus


text:
finish hotfix ( 230831 )

finish hotfix ( 230831 )

rendering error는 왜 나오는거에요?

rendering error는 왜 나오는거에요?

전에 말씀드렸듯이 un-build 성 컴포넌트 전체에 대해 action 점검을 해야 합니다. istio 관련 에러가 찍히고 있는데 이번 변경이 아닌 기 발생하던 issue 로 보입니다.

authors: bluejayA ktkfree

repo: openinfradev/decapod-site


text:
ol.geom.Geometry::transform is not documented

Users are not able to know that they can use transform on any Geometry reading the API documentation.

I think this should be fixed by #3818

authors: pgiraud probins


text:
kml point features do not display the name as a label

In Google Earth, when you create a placemark that is a point that has a name, the name is displayed as a label next to the icon for the placemark.
When you import the same kml into OpenLayers, there is no name displayed.

See #4306 and #4316.

authors: marcjansen tamarmot


text:
Mark ol.format.filter.Spatial as abstract class

fixes #7217 and add missing @abstract tag

Yes, it make sense to remove the @api annotation but will it require a new major release (5.0.0) ?

Hm. Well, you cannot add a @deprecated annotation, because you will get a compiler warning. But you could mention that those are deprecated in their docs. And we can remove the @api annotation later, i.e. before we release 5.0.

@ahocevar I've added the deprecation warning in the doc

Thanks for the review

authors: ahocevar fredj

repo: openlayers/openlayers


text:
Stop listening for image decoding

See https://github.com/openlayers/openlayers/pull/9551#pullrequestreview-238330100

I've pushed some tests in this branch

authors: fredj tschaub


text:
Upload z/OSMF workflow sample files

Signed-off-by: Caihua Zhao zhaocaih@cn.ibm.com

Hi Hiren, Conner, Thanks for the comments, very helpful. It's inconvenient to track so many comments in one single request, I'd like to submit pull request separately after addressed the comments for each sample. what do you think?

@zhaocaih , I'm not sure if I'm understanding correctly. Are you asking for this pull request to be accepted as is, and then at some later point fix the comments in this review in individual pull requests per sample?
If so, I'd rather keep all the comments and their respective fixes all together if possible rather than accepting a pull request into the repo with open issues.
I'm not terribly familiar with Git processes yet; But can't this pull request be updated with as many additional commits as required in order to address the comments? Each of these commits could in address a single file if that is more convenient. For some of the simple grammatical comments it seems like you can even just accept suggestions through the webtool.

@Conner-IBM Sorry I didn't make myself clear in my previous comments. I meant close (reject) this pull request without merge. When I addressed the comments for one file, I will submit a new pull request for that single file, I think it could be more clearly and easier to track and decide if accept for that single file, and we can make progress step by step.
This pull request now include 28 files, it may take longer time to address all comments, as some may need a test or discussion before make changes (I include them in one PR because I thought only copyright need update at first).
Each of these commits could in address a single file sounds a good idea, I am just afraid that as the conversation number goes up it gets harder to read.
I am not very familiar with Git, I will try from accepting grammatical suggestions through the webtool to see how it will go.

@shreeji818 I have updated the copyright.

@shreeji818 Hiren, all the comments of this pull request were addressed, the copyright was updated, can you please review?

I have approved the changes. Li Qi should be able to merge the changes into the main branch after resolving the conflict.

We need to update the Readme.md file in this folder to describe each sample. Will you please take care of that before merging? Otherwise you will need a new pull request to update the ReadMe file.

authors: Conner-IBM shreeji818 zhaocaih

repo: openmainframeproject/zOS-Workflow


text:
Problems with filtering tasks

I can't even filter for words that are given as example (says it does not find anything)

The drop-down menu does not really show me anything interesting.

Thanks. There is a general problem with the search engine (mentioned in
several issues). I will look at it on Monday.
On Thu, Mar 9, 2017 at 10:02 AM Heidi Seibold notifications@github.com
wrote:

I can't even filter for words that are given as example (says it
does not find anything)

[image: image]
https://cloud.githubusercontent.com/assets/14146757/23743021/631b5d78-04af-11e7-8067-2928f929b52f.png

The drop-down menu does not really show me anything interesting.

[image: image]
https://cloud.githubusercontent.com/assets/14146757/23742873/e6e9c56e-04ae-11e7-9a1b-a116fe014272.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/openml/website/issues/107, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABpQV6wDRnsAsvcxWCNLlUcM4FJUS8cEks5rj8ALgaJpZM4MXzzf
.

--
Thank you,
Joaquin

All better now. Thanks for reporting the issue 👍

Thanks. The second problem is solved. The first still exists for me :/

Sorry, missed that. That happens because actual name is 'predictive_accuracy'. I have now replaced that field with a dropdown with all evaluation measures.

authors: HeidiSeibold joaquinvanschoren

repo: openml/website


text:
readme

Hey everyone,
I've added a barebones readme. Please take at least a cursory look, especially on the Contributing and Conflicts sections. I know the conflict stuff sounds silly now, but I've found that having a agreed-upon resolution mechanism in place is never a bad thing.
A simple +1  from all of you is fine with me for pulling this in.

+1
@sjpfenninger @ojdo : you might want to watch toolchest! I just caught @gidden 's pullrequest by chance.

i see the split into develop/master as one which makes sense, but only at a somewhat later stage, once the first users are in place. Since you're pulling into master i guess, you somewhat agree. Let's not forget to implement this split later!

I'm not a fan of develop branches. Why not pull into master and tag releases off of master? That's kind of the default I expect when I reach a project's repo. We can always add a release or stable branch if necessary.

Hey @sjpfenninger, the rationale for having develop branches is explained here
In short, develop is used as a back-stop in case some issue is found with a code before release. That is, develop can be considered unstable, but master is stable.
For example, after this and the License PR, I would make a develop branch and make it the default. While I've found this development model quite useful, I don't want it to hinder us at the beginning. Perhaps @ojdo can weigh in and I'll update the PR accordingly.
Finally, note that there is also a License PR!

@coroa thanks for the mention, repo is on watch now.
@gidden right now I would opt for the simpler "no develop branch model, and simply creating releases whenever we have the feeling of having reached a new milestone. I wager that the PR peer reviews will do a good enough job to keep master reasonably stable. Just my 2ct, though :smile:

ok, I believe I've addressed everyone's comments, this should be good to go

My suggestion would be to start with a simple master only work-flow,
all the while the pr's are used as gatekeepers, and use tagging to
indicate major feature set changes as @sjpfenninger had already
suggested.
When we later notice any instabilities creeping in, we can easily switch
to the more conservative separate develop/master approach.

ah, I should read ALL my mails before replying :)
i don't have write access, so can't merge!

You've been added. There's a team called "toolchest-pullers" on the
openmod-initiative group. Everyone in it has Admin access (thus should be
able to add others). You have to be a "member" of the github org to be in
the team I think. Once we get some additions to the repo, I think we should
advertise it more broadly on the list serv.
On Tue, May 3, 2016 at 2:07 PM, Jonas Hörsch notifications@github.com
wrote:

ah, I should read ALL my mails before replying :)
i don't have write access, so can't merge!
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/openmod-initiative/toolchest/pull/2#issuecomment-216508376

authors: coroa gidden ojdo sjpfenninger

repo: openmod-initiative/toolchest


text:
Add a markdown table containing the list of supported devices

The list of devices currently supported by OpenNetty can be found here: https://github.com/opennetty/opennetty-core/blob/92712cc788d1b1ecf587f8d79f015240da013885/src/OpenNetty/OpenNettyDevices.xml#L1-L599

Done: https://github.com/opennetty/opennetty-core/commit/bc1aa09a4fce63f161f688f0e6bc4ab37f744f03.

repo: opennetty/opennetty-core


text:
[#188] refactor CI to use Docker image

This decreases the distance bewteen dev and CI, whilst ensuring that updates to test stages are reflected automatically. Note that Docker images are not used for stg or prd, since they run on Heroku.

Rescinded in favour of https://github.com/openownership/register-common/pull/16 .

repo: openownership/register-common


text:
ssh一直没成功

是否是我输入的命令不对呢？
我的配置如下

ssh时输入的命令如下：
ssh username@127.0.0.1:23390
望解惑！谢谢

截图上显示connecting呢，等连上就可以了。

谢谢 已解决

authors: TenderIronh manipulative


text:
Set naming standard for meeting minute file names

Before we get too many files in the repo, we should standardize file names to be of the format <YYYY>-<MM>-<DD>-<NAME>.md (e.g. 2023-11-15-community.md or 2023-12-06-tsc.md).
This allows files to be more easily sorted/searched based on date, which will become more important the longer the project goes on.
Adding the name allows us to easily change the organization later without having to worry about name collisions (e.g. if we later decide to put all meeting minutes into a  single meetings/ directory)

Agreed. Thanks for the suggestion!

Hey @funnelfiasco , we've implemented this change for both our tsc and community meeting minutes. I'm going to close this issue out with resounding success!

authors: asamborski funnelfiasco

repo: openpubkey/community


text:
Update python package README.md: name of parser extra

Summary
I have updated the python package's README to refer to the extra parser rather than parsing, as the former is the name used in setup.cfg.
https://github.com/openqasm/openqasm/blob/main/source/openqasm/setup.cfg#L32
Details and comments

I think this is the kind of change that should not include a release note.

authors: garrison jlapeyre

repo: openqasm/openqasm


text:
Add phase descriptions to pipeline

Before

After

looks great

authors: danmitchell- gtdata

repo: openregister/register-status


text:
CZ Business is unhappy again

Traceback (most recent call last):
  File "/opensanctions/zavod/zavod/crawl.py", line 34, in crawl_dataset
    entry_point(context)
  File "/opensanctions/datasets/cz/business_register/crawler.py", line 109, in crawl
    parse_xml(context, res)
  File "/opensanctions/datasets/cz/business_register/crawler.py", line 64, in parse_xml
    tree = etree.parse(reader)
           ^^^^^^^^^^^^^^^^^^^
  File "src/lxml/etree.pyx", line 3570, in lxml.etree.parse
  File "src/lxml/parser.pxi", line 1973, in lxml.etree._parseDocument
  File "src/lxml/parser.pxi", line 1993, in lxml.etree._parseFilelikeDocument
  File "src/lxml/parser.pxi", line 1887, in lxml.etree._parseDocFromFilelike
  File "src/lxml/parser.pxi", line 1224, in lxml.etree._BaseParser._parseDocFromFilelike
  File "src/lxml/parser.pxi", line 633, in lxml.etree._ParserContext._handleParseResultDoc
  File "src/lxml/parser.pxi", line 743, in lxml.etree._handleParseResult
  File "src/lxml/parser.pxi", line 672, in lxml.etree._raiseParseError
  File "/opensanctions/VYSTUP/DATA/19063521.xml", line 95
lxml.etree.XMLSyntaxError: Input is not proper UTF-8, indicate encoding !
Bytes: 0x8D 0x20 0x20 0x20, line 95, column 18

Maybe we just catch and warn on individual XML files?

Skip over broken XML files: https://github.com/opensanctions/opensanctions/pull/884/commits/2c7a71d09a795a2421656925612d27608c36571f

repo: opensanctions/opensanctions


text:
Replace EFFRF with ERF

Pull request
Please confirm that this pull request has done the following:

[x] #281
[x] #288
[x] Tests added
[ ] Documentation added (where applicable)
[ ] Example added (either to an existing notebook or as a new notebook, where applicable)
[x] Description in CHANGELOG.rst added

@znicholls Ready

repo: openscm/pymagicc


text:
Remove bounds but keep the pan functionality

How can I remove the bounds - i mean that the user will not be able to play with the image and move the image between the white spaces, and the image will be at the middle or take the div place
I m using simple image url
In addition I'd like to keep the ability to use the pan with the mouse
thx for amazing library again

I'm not quite sure what you're asking for. Do you mean you want to allow the user to drag the image off of the viewer? Or do you mean you don't want them to drag it at all when it's zoomed out? Or do you mean you want less white space to appear around the image when it's zoomed out?

authors: iangilman johnico

repo: openseadragon/openseadragon


text:
Integ test framework should allow to create multiple clusters

Is your feature request related to a problem? Please describe
https://github.com/opensearch-project/OpenSearch/pull/15462#discussion_r1740832376
Describe the solution you'd like
https://github.com/opensearch-project/OpenSearch/pull/15462#discussion_r1740832376
Related component
Other
Describe alternatives you've considered
No response
Additional context
No response

This should already be possible from a framework perspective.
https://github.com/opensearch-project/OpenSearch/blob/9f814797d0fe57457359a1f8a1b222cea80dc003/test/framework/src/main/java/org/opensearch/test/OpenSearchIntegTestCase.java#L2012-L2081
Following is an example to create 3 clusters which I had tried in the past for some local verification:
    private InternalTestCluster[] clusters;

    @Before
    public void setupClusters() throws Exception {
        clusters = new InternalTestCluster[3];
        clusters[0] = (InternalTestCluster) buildTestCluster(Scope.TEST, randomLong());
        clusters[1] = (InternalTestCluster) buildTestCluster(Scope.TEST, randomLong());
        clusters[2] = (InternalTestCluster) buildTestCluster(Scope.TEST, randomLong());
    }

    @After
    public void teardownClusters() throws Exception {
        for (InternalTestCluster testCluster: clusters) {
            for (String nodeName : testCluster.getNodeNames()) {
                testCluster.getNode(nodeName).close();
            }
            testCluster.afterTest();
            testCluster.close();
        }
    }

[Catch All Triage - 1, 2, 3]
@sachinpkale Can you follow up if @mgodwan's example will solve your issue?

authors: andrross mgodwan sachinpkale

repo: opensearch-project/OpenSearch


text:
Use unlimited compilation rate limit for scripts template context

Is your feature request related to a problem? Please describe.
When using search templates and get stored in cluster state, they get loaded to cache via "compilation". As they evicted and hydrated back to the cache, they consume compilation rate for template context. This action eventually throw errors as  script.context.template.max_compilations_rate which is 150 per 5 minutes.
Describe the solution you'd like
for "template" context of script, the compilation rate can be unlimited as they don't really need compilation, just rendering the query with parameters.
Describe alternatives you've considered
The search templates can be used instead of storing them in cluster state, but it largely increases by REST call payload size

Thanks @arunx2 for opening this up.
I see couple of solutions to make this happen:

This is a static setting[1] today and not modifiable without restarting the cluster.
The setting could adapt to the hardware its running on. Its static and the circuit breaker limits dont scale with respect to the hardware.
Understand the implications of unlimited compilation rate for search templates.