'StartWorkTimer' must be called on the foreground thread.

Is this a Bug or Feature request?:
Bug
Steps to reproduce
Have razor file open, possibly also be in debugging mode.
Description of the problem:
Razor language server stops unexpectedly and without any real indication of what triggers the stop.
Expected behavior:
Razor language server to not stop unexpectedly.
Actual behavior:
Razor language server stops unexpectedly.
razor file/log
https://gist.github.com/eevahr/c25c22612563740b9570a9f8871567fb

Thanks for the report @eevahr! I wonder what could be going wrong here hmmm. I'll have to take a deeper look.

I would like to second the report. Happens for me on VS Code 1.34.0, C# extension 1.20.0 ,.NET Core SDK 2.2.300. Unfortunately, I can't share stack traces because my company does not allow file uploads.
All I remember is that this exception happens and causes the Razor Language Server to be restarted a lot, crashing immediately with an RpcException every time until VS Code stops restarting it.

Same issue. Within the past month or so, VS Code on Mac has repeatedly begun crashing while editing Razor .cshml pages. The stack trace is typically StartWorkTimer must be called on the foreground thread

Issue remains in C# Extension 1.21.0.
Happened last time when creating a Razor comment (@* *@).

Issue remains in C# Extension 1.21.0.
Happened last time when creating a Razor comment (@* *@).

Yup, we haven't had the bandwidth to push out an official fix for this quite yet. Sorry! 😢

Sorry if my previous comment came across as a complaint.
I just meant to inform you that commits in 1.21.0 have not inadvertently fixed the issue, given that you had said you were still looking into the cause of this issue, and that other people in the thread mentioned this might be a regression ("Within the past month or so...")
That being said, would you be able to share with us if a cause has been identified? (if/when you have time to do so, of course)

Definitely!

@NTaylorMullen If it helps, this exact JsonRpc.Server crash occurs reproducably, every time on my Macbook (VS Code and with dotnet Core 2.1) right after I press the "dot" in Orchard. as shown in this example:
https://www.youtube.com/watch?v=4o9zG17cfa0&feature=youtu.be&t=1391

@nkev thank you for the exact info. That'll definitely help in reproducing on my end 😄


Remove redundant test logs in ballerina transaction manager.

Description:
$subject for the following logs.
Checked with @afkham who was the author of the code and those are INFO logs added to validate the behaviour. We can safely remvoe them as it is not meaningful for the end user.
2020-03-18 12:36:26,983 INFO  [ballerina/transactions] - Created transaction: 17130bbc-28e0-414d-b0a0-e20efccdacec
Inserted count: 1
2020-03-18 12:36:26,999 INFO  [ballerina/transactions] - Running 2-phase commit for transaction: 17130bbc-28e0-414d-b0a0-e20efccdacec:$anon$.$0

Steps to reproduce:
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

Fixed with #26419, #26542 for 1.2.x.


Remove external ITHC testers for Xhibit-Portal

User Story
Remove external ITHC testers for Xhibit-Portal ITHC to Xhibit-Portal accounts -
Thomas Marshall
Matthew Smith
Daniel Zielinski
Value
Keep the platform secure

Questions / Assumptions

Definition of done

[ ] readme has been updated
[ ] user docs have been updated
[ ] another team member has reviewed
[ ] tests are green

Reference
How to write good user stories

All users with access to xhibit portal removed from collaborators in modernisation-platform

Error: error removing IAM User (thomas.boyle) Virtual MFA devices: Error deleting Virtual MFA device arn:aws:iam::946070829339:mfa/thomas.boyle: AccessDenied: User: arn:aws:iam::946070829339:user/ci is not authorized to perform: iam:DeleteVirtualMFADevice on resource: arn:aws:iam::946070829339:mfa/thomas.boyle with an explicit deny
status code: 403, request id: 80bc30e5-ce21-41b9-ae40-7ea27ae49ad8

the same for other users

It was a deny on access required for the user ci. This was ported to the main on github and then run manually to delete the accounts
module.collaborators["thomas.marshall"].module.iam_user.aws_iam_user.this[0]: Destruction complete after 1s
module.collaborators["thomas.boyle"].module.iam_user.aws_iam_user.this[0]: Destruction complete after 1s
module.collaborators["matthew.smith"].module.iam_user.aws_iam_user.this[0]: Destruction complete after 1s
module.collaborators["lewis.smith"].module.iam_user.aws_iam_user.this[0]: Destruction complete after 1s


pin_memory and num_workers > 1 produces completely different results?

Try disabling xformers?

Seems like this depends on when intermediate sampling happens. Possibly changing rng state despite attempt to set it back to state before inference?


The good stuff

🤓🤓🤓🤓🤓🤓
Code is really clean!
🤓🤓🤓🤓🤓🤓
🤓🤓🤓🤓🤓🤓
You divide your JavaScript into modules
🤓🤓🤓🤓🤓🤓

Thanks for the nice feedback 😄


Wrong comment in real mvrx state store

https://github.com/airbnb/MvRx/blob/8375363d29cdab3561b5259118c2c2e4190cc562/mvrx/src/main/kotlin/com/airbnb/mvrx/RealMvRxStateStore.kt#L24 the comment refers to an observer while the next line is a disposable

Thanks for catching this. will update it as some point (or anyone else is welcome to put up a PR!)

This will be deprecated by #347

Fixed bt #347


CAS Server Ticket Validation From Client  To Server

Hi,
If we logged through cas "we got one ticket from cas server, i need to validate this ticket from client whether its available or not in the server. Kindly check and let us know your feedbacks.
Also, kindly explain the below function For this we need to configure anything in the CAS Server or Client, kindly explain ...
phpCAS::handleLogoutRequests();
Regards,
Senthilkumar

Please check our documentation on the wiki. https://wiki.jasig.org/display/casc/phpcas or use one of the cas mailing lists.
This issue tracker is for any issues/errors with the lib.


Multiple duplicate review events captured by scraper

The scraper seems to be capturing multiple review events (duplicate) in some cases. (Review events are unique by their PR Review ID (the last number in the link).
Tasks

[ ] Update the scraper to register duplicate review events. (Skip appending if the URL is already present in the list of activities).
[ ] Create a script to clean existing data by removing duplicate events.

can you please assign me !

Can you please assign me this issue


dashboard_app.DashboardWidgetLastUpdate.last_update: (fields.E160) The options auto_now, auto_now_add, and default are mutually exclusive. Only one of these options may be present.

This is the issue I am facing while upgrading to Django 1.8.

@shubham2892 by the way, I never really used this app in production. I discovered influxdb and grafana when I was halfway through this and gave up on this app. I'm not sure, but you might be wasting your time on this one.

@mbrochh : Yeah, they are really cool. Moving on to grafana.


Clear statement regarding Mac support of M365 Apps Device licenses

Could you please add a note to this page to advise on whether or not the Mac version of M365 Apps supports device licenses? It is not addressed at all.
I have assigned M365 Apps device licenses to our Macs but it looks like they don't support it.
Is support coming for this? It's a real problem for us because we work with multiple tenants and I can't separate my Mac users from the Windows users and do not want to see Windows clients preference user licensing over the device licensing I have provided.

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

ID: c517dca4-9d87-72b1-9789-68fbcd1e56af
Version Independent ID: 0535d6c1-d5eb-7b30-73f9-c12a45f7049f
Content: Overview of activation for Office for Mac - Deploy Office
Content Source: DeployOffice/mac/overview-of-activation-for-office-for-mac.md
Service: o365-proplus-itpro
Sub-service: office-mac
GitHub Login: @DHB-MSFT
Microsoft Alias: danbrown

@pbowden-msft   Can you answer this question?  Thanks.

@mcnaugha Unfortunately, Office for Mac doesn't support device-based licenses. It is something that we've looked at, but there are some large technical challenges. While I understand it's not ideal, the current recommendation would be to use the Office 2021 VL Serializer to activate shared Macs.


Bug: going from a folder to one before

Description
when I go from 194.xxx.xx.xx.../test folder to 194.xxx.xx.xx...
It crashes and I have to wait
Steps To Reproduce
Have a folder on the local network like 192.xxx..../folder1
click on 192.xxx.... to see other folders on this address
and it should crash
Files Version
<IP_ADDRESS>
Windows Version
10.0.22631.4460
User ID
2f8501ed-5821-4f9b-b1fd-1de9e66fe103
Log File
debug.log

Thanks for the report, the log doesn't show any error message, Can you type Event Viewer into the Windows start menu search > Click Windows logs > Click Application > Screenshot any errors that have Files.exe shown on the first line

I don't see anything


warning: 'codec' is deprecated and a lots of deprecated module when install

Warning displayed when I install.
libavcodec/smvjpegdec.c: In function 'smvjpeg_decode_init':
libavcodec/smvjpegdec.c:131:5: warning: 'refcounted_frames' is deprecated [-Wdeprecated-declarations]
     s->avctx->refcounted_frames = 1;
     ^
In file included from libavcodec/smvjpegdec.c:28:0:
libavcodec/avcodec.h:2396:9: note: declared here
     int refcounted_frames;
         ^~~~~~~~~~~~~~~~~
libavcodec/smvjpegdec.c: In function 'smvjpeg_decode_frame':
libavcodec/smvjpegdec.c:162:9: warning: 'avcodec_decode_video2' is deprecated [-Wdeprecated-declarations]
         ret = avcodec_decode_video2(s->avctx, mjpeg_data, &s->mjpeg_data_size, avpkt);
         ^~~
In file included from libavcodec/smvjpegdec.c:28:0:
libavcodec/avcodec.h:4828:5: note: declared here
 int avcodec_decode_video2(AVCodecContext *avctx, AVFrame *picture,

BRs!

Hi @abinhho,
These warnings are part of the ffmpeg build. There's usually a lot of warnings, but shouldn't affect the code. Is this causing you issues building the docker image?

@alfg
Yes, I am building in docker.

@abinhho Is it failing to build?

@alfg
It's built OK. Just saw a lots of warning. My customer will be ask why.
Any way, thanks you!

Ah, okay thanks!


Better Documentation on Resuming

I was wondering if there were any strong examples of resuming a training run that failed for whatever reason. I'm also curious if stool could be expanded to support that functionality.
Thanks for such a great repo, been super fun to hack around with it!

The process works as follows: when a run is relaunched, the checkpoint manager scans all checkpoints in the checkpoint folder and reloads the most recent one based on the step number. This means that if the job is preempted or requeued by SLURM, it will automatically reload from the last checkpoint.
If the job crashes for some reason and you are using stool to launch it, simply run sbatch /your_dump_dir/submit.slurm to restart the job; the checkpoint manager will handle reloading automatically. The same approach applies to evaluation jobs. To relaunch an evaluation, use sbatch /your_dump_dir/evals/your_eval_step/submit.slurm. This works if the eval_on_gpus parameter is set to a non-null value (e.g., eval_on_gpus: 8), which indicates that the evaluation job should be run on a separate job using 8 GPUs.

Thank you, really helps. Would say that putting this in the readme would be super helpful for others. Thanks again!


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/84974

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/85240

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/87077

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/87081

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/116533

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.


Fortran ai_util module should be renamed to aero_util.

In the Great Reorganization, we renamed src/ai_util.F90 to src/aero_util.F90, but we didn't rename the Fortran module. Not a big deal at the moment, but we should fix this when it makes sense.

Fixed by #12


Fix failing quality check from PR #25

npm ci is failing on Ubuntu. It's possible a sync problem between package.json and package-lock.json. Needs further investigation.

Actually, it looks like the merge was bad and that npm test  is still calling jest. Pointing this back to the native runner should solve the problem.


License for dependency

Hello,
I'm doing an audit of the packages we use to ensure we're compliant with licenses and noticed that the dependency of @icons/material (https://github.com/at-icons/material) does not have a license file. Can the version used here be bumped to one that contains the license file?
Thanks,
Sean

This is fixed in my fork, @hello-pangea/color-picker


STC # and BritDrama # need to search multiple numbers independently

In each of these fields, there are 4 items that have multiple numbers in the field, separate by semicolons.
When a user searches for one of these numbers, it should return the record. Right now they have to enter both, with the semicolon, for the record to be hit. It should treat each number as a discrete number and either one of them will suffice to hit the record.

When there is more than one number in these fields, they should appear in Display as follows, if possible:

lowest number first
alphabetically for those with a letter at the start
numbers before any with a letter at the start.

DEEP, Greg, BritDrama, STC/Wing should all search for numerals, so that "25" does not also hit 251, 252, 525 etc

Some problems resolved, but others created:
I think the problem with string searching has been solved, BUT: now we can no longer hit a record that has 2 STC/Wing or BritDrama #s.
If you search for STC/Wing = 14959 or BritDrama = 1488 or BritDrama = 1489, you get no hits. Because these numbers are all in records with more than one value for those fields.
Is this impossible to do unless we re-implement string searching here (which causes other problems)? If so, maybe the best way to handle this to add a second STC/Wing and a second BritDrama field and have these filters run on both those fields? (In most cases the second field will be empty)

changed to regex with split on space, working for brit drama but not stc/wing.
also make changes to OR after AND is working


Angular update to supported version

Angular version 8 is out of date, 13 is probably what we should aim for, or whatever CL wants everyone to be on.
Angular major versions come out twice per year, we should have at least a yearly standing order to keep current with latest LTS. Upgrading from major versions isn't terrible but it's a chore, as we will need to do full upgrade to each version and clean up any breaking changes before moving onto next (8 --> 9 --> 10.....)
https://endoflife.date/angular
https://update.angular.io/?v=8.0-13.0

I will take a look at this while upgrading the node v16 and npm v8.


SpotEllipsoidAspectRatiosFeature

UserStory
From a biological perspective, the aspect ratios of the semi-axes of the ellipsoid that approximates the cell shape may be a good descriptor for the cell type. Thus, it would be useful to have this information as a feature.
Acceptance criteria

Available as Feature within the Feature Computer
Computes the aspect ratios between the three semi-axes

$aspect\ ratio\ a\ to\ b\ = \frac{a}{b}$
$aspect\ ratio\ a\ to\ c\ = \frac{a}{c}$
$aspect\ ratio\ b\ to\ c\ = \frac{b}{c}$

Computes all 3 aspect ratios of the Spot/Ellipsoid
Re-uses SpotEllipsoidFeature

Tasks

[x] Implement Feature
[x] Implement FeatureComputer
[x] Write Unit test

Additional information
Ellipsoid parameters (semi-axes) do not need to be computed again, as they are already computed in the SpotEllipsoidFeature, cf.: #13

https://github.com/mastodon-sc/mastodon-deep-lineage/pull/22


Parsing error with single-line comments

Looks like // comments are causing a parsing error:
* no Run | --watch | Debug *
test("404", async (t) => {
    t.is(statusCode, 404);
});
// test("405", async (t) => {
//     t.is(statusCode, 405);
// });

Hi @AaronPorts - thanks for the report.
I'll take a look at this 🤞

Seems like the issue occurs only if you comment the test line. Thanks again - I'll fix it.


Add Secret Manager - please add this one liner to make it easier

Now: you are pointing the user to a Secret Management intro article away from the tutorial. All they really need to know is dotnet user-secrets init andUserSecretsId  is populated. Please make this change.. It's easier if everything is in one article rather than having to go to another article and then come back

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

ID: 2984100d-7d78-2115-40f4-4b9478a5a5bc
Version Independent ID: 24ac6adc-6779-b847-ce81-c9d36e4b067b
Content: Quickstart for Azure App Configuration with ASP.NET Core
Content Source: articles/azure-app-configuration/quickstart-aspnet-core-app.md
Service: azure-app-configuration
GitHub Login: @lisaguthrie
Microsoft Alias: lcozzens

@softchris Thank you for the feedback!  We are going to assign this to the document author so they can review the documentation.

@softchris - the tutorial itself actually contains everything you need to know about Secret Manager in order to complete the tutorial itself. I've updated it to make clear that the link out to the Secret Manager article is purely informational, for anyone wanting to know more about it.

#please-close


Implementation of JWTAuthorizationProvider

What changed?
Implementation of JWTAuthorizationProvider in both worker and client

Why?
Part of this proposal

How did you test it?
Running the server with oauth file
./cadence-server --env development_oauth start

and modifying cadence-samples
Adding Authorization value in NewClient here
Adding Authorization value in NewDomainClient here
Adding Authorization value in worker.Options here

Potential risks
None

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@longquanzheng test added, check internal/common/auth/service_wrapper_test.go and internal/jwt_authorization_test.go

Pull Request Test Coverage Report for Build ebefd216-b2af-484f-8ba4-55a8796259d8

346 of 391 (88.49%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.4%) to 71.084%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/internal_worker.go
1
3
33.33%

worker/worker.go
0
3
0.0%

internal/client.go
6
10
60.0%

internal/jwt_authorization.go
21
25
84.0%

internal/common/util/rsa.go
0
32
0.0%

Totals

Change from base Build b792b9b0-c0a6-4a59-9363-e60d3948b178:
0.4%

Covered Lines:
12068

Relevant Lines:
16977

💛  - Coveralls


Remove connections (functions data source included)

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
Like in pro-code, connections will be with environment variables so it will be removed from the UI.
Functions data source is also going to get irrelevant as the same purpose could be achieved from scratch.
Examples 🌈
No response
Motivation 🔦
No response

If I can understand correctly, this has already been removed from Direction 13:
It might also be about removing the code related to connections that we don't use anymore?


[V12] - Oracle Cleanup Needs

Needs

[ ] #486
[x] #487
[ ] Link source for query contract
[x] price-feeder/config.toml
[x] #490
[x] #491 ?

Notes
upgrade handler

Timings, 30 second submits? we can do more often since fees are 0

config.toml

A ton of "provider timed out" spam in between broadcasting votes.
Does it need to query so often (once a second)? We only submit 1 time per 30. Wouldn't every 5 be enough? don't want Vals to get blacklisted

Fantastic

@vuong177 wdyt?
I like the idea of querying less often

I like the idea of querying less often
@faddat Just did about an hour of testing.Not worth the risk of querying less often.

Also it queries sequentially which I did not expect. We can optimize by 100% (2 second queries) at the max, and this begins to miss some submits. Would need an overhaul to the feeder to run all queries at 1 time in parallel

Scrapped, not confident in it


"_id" in Object fields is being renamed to "objectId"

Check out this issue for an ideal bug report. The closer your issue report is to that one, the more likely we are to be able to help, and the more likely we will be to fix the issue quickly!
For implementation related questions or technical support, please refer to the Stack Overflow and Server Fault communities.
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!

[x] You've met the prerequisites.

[x] You're running the latest version of Parse Server.

[x] You've searched through existing issues. Chances are that your issue has been reported or resolved before.

Environment Setup
Test Schema
{
    "_id" : "Test",
    "objectId" : "string",
    "updatedAt" : "string",
    "createdAt" : "string",
    "data" : "object"
}

Test Data
{
    "_id" : "tqwysmYbjP",
    "data" : {
        "_id": "testObjectKey",
        "arr" : [ {
                "_id" : "testArrayKey",
                "_testKey" : "otherKey"
            }],
        "obj": {
            "_id": "testNestedObjectKey"
        }
    },
    "_updated_at" : ISODate("2016-04-07T04:22:47.653Z"),
    "_created_at" : ISODate("2016-04-07T04:22:47.653Z")
}

When querying this Class the output I receive is:
{
    "results": [{
        "objectId": "tqwysmYbjP",
        "data": {
            "objectId": "testObjectKey",
            "arr": [{
                "objectId": "testArrayKey",
                "_testKey": "otherKey"
            }],
            "obj": {
                "objectId": "testNestedObjectKey"
            }
        },
        "updatedAt": "2016-04-07T04:22:47.653Z",
        "createdAt": "2016-04-07T04:22:47.653Z"
    }]
}

Steps to reproduce
Fetch the Test Class in parse dashboard/curl and look at the results.
Logs/Trace
N/A

With the same data on parse.com this is the output for the same query.
{
    "results": [
        {
            "createdAt": "2016-04-07T21:30:07.528Z",
            "data": {
                "_id": "testObjectKey",
                "arr": [
                    {
                        "_id": "testArrayKey",
                        "_testKey": "otherKey"
                    }
                ],
                "obj": {
                    "_id": "testNestedObjectKey"
                }
            },
            "objectId": "VvFMrOwBhF",
            "updatedAt": "2016-04-07T21:30:11.447Z"
        }
    ]
}

in transform.js keys are being renamed even when they are inside fields of type Object and Array.
What would happen if you stopped traversing into these fields?

Verified. Working on a fix.


Fix material batch entities from disappearing

Fixes #4096
createPrimitive was always being incorrectly set to false whenever an entity not in the batch tried to be removed from the batch, causing the entity actually in the batch to never be created. The code in StaticGeometryColorBatch was correct, so I just copied it from there to StaticGeometryPerMaterialBatch.

Wow, this might fix a bunch of other random issues we've seen in the past as well.  Thanks for tracking this down.  I'll look at it closely tonight.

Might be worth a moment's consideration of #3807.  I don't understand the code well enough to say for sure, but I think #3807 is caused by incorrect batch updating logic in StaticGeometryColorBatch.

@lilleyse can you update CHANGES.md?  Is it also possible to add a reasonable unit test?
@mramato do you want to review before we merge this?

Yes, I'll look at it today.

Might be worth a moment's consideration of #3807. I don't understand the code well enough to say for sure, but I think #3807 is caused by incorrect batch updating logic in StaticGeometryColorBatch.

I actually think @tfili fixed that as part of his entity clamping work and we just forgot to close the issue.

Looks good, thanks again @lilleyse!

I actually think @tfili fixed that as part of his entity clamping work and we just forgot to close the issue.

Yep, confirmed.  Thanks guys!

@lilleyse can you update CHANGES.md? Is it also possible to add a reasonable unit test?

I'll update CHANGES.md in master. I wrote a unit test but I can't seem to replicate (or am just not properly testing) the failing behavior, so it may not be worth adding.

Just putting it here for reference.
it('StaticGeometryPerMaterialBatch and StaticGeometryColorBatch update simultaneously', function() {
    var entityCollection = new EntityCollection();
    var visualizer = new GeometryVisualizer(EllipseGeometryUpdater, scene, entityCollection);

    var ellipse = new EllipseGraphics();
    ellipse.semiMajorAxis = new ConstantProperty(2);
    ellipse.semiMinorAxis = new ConstantProperty(1);
    ellipse.material = Color.RED;
    ellipse.height = 100;

    var entity = new Entity();
    entity.position = new Cartesian3(1234, 5678, 9101112);
    entity.ellipse = ellipse;
    entityCollection.add(entity);

    var ellipse2 = new EllipseGraphics();
    ellipse2.semiMajorAxis = new ConstantProperty(3);
    ellipse2.semiMinorAxis = new ConstantProperty(2);
    ellipse2.material = new GridMaterialProperty();
    ellipse.height = 100;

    var entity2 = new Entity();
    entity2.position = new Cartesian3(1234, 5679, 9101112);
    entity2.ellipse = ellipse2;
    entityCollection.add(entity2);

    return pollToPromise(function() {
        scene.initializeFrame();
        scene.render(time);
        return visualizer.update(time);
    }).then(function() {
        entity.material = Color.BLUE;
        entity2.material = new CheckerboardMaterialProperty();
        expect(scene.primitives.length).toBe(2);
        return pollToPromise(function() {
            scene.initializeFrame();
            scene.render(time);
            return visualizer.update(time);
        }).then(function() {
            expect(scene.primitives.length).toBe(2);
            visualizer.destroy();
        });
    });
});


Publish later (aka scheduled publishing)

Authors should be able to set a date and time when their content gets published.

One of my customers depends on this functionality for their business. Having this functionality as part of the sidekick to easily publish later would be amazing.

We have also had discussions with Maidenform on this topic. They typically do all their content changes using scheduling. We built a client-side version of this, but it leaves the content publicly visible (if discovered) before it is live. Having built-in scheduling would fix this.

I think usually what they want is some kind of reviews using the snapshot feature, where they can prepare a set of changes and then publish together on a set date. @rofe @davidnuescheler how difficult is it to re-use the review features we built for other customers?

@tripodsan rather difficult. I think we should build this independently from the review aspect to start. But I would recommend creating a snapshot of the current page behind the scenes, and publishing the snapshot at the given time. I think that would be more intuitive than publishing the main version of the page with potential other changes made in between.
cc @davidnuescheler

I think we should just drop the feature of publish later....

I would definitely NOT drop this feature because it is extremely important to a lot of our media/news customers.
Rather than complicating the requirement, the simplest form of what my customers would want is to see is a simple Publish Later Button on the sidekick that

allows them to select a date/time in the future (from their timezone) to publish a page that has already been previewed.

Having the above would solve the most common publish later use-case.


MissingMethodException in WebSocket4Net

Stumbled upon the WebSocket4Net issue on Win7, and from what I've been able to google, the solution should be to set the WebSocketProvider for the DiscordSocketClient like so:
private DiscordSocketClient client = new DiscordSocketClient(new DiscordSocketConfig {
	WebSocketProvider = Discord.Net.Providers.WS4Net.WS4NetProvider.Instance
});

But this seems to throw an error with a missing static constructor(?) for the WebSocket4Net library:
15:12:17 Gateway     Connecting
15:12:17 Gateway     System.MissingMethodException: Method not found: 'Void WebSocket4Net.WebSocket..ctor(System.String, System.String, System.Collections.Generic.List`1<System.Collections.Generic.KeyValuePair`2<System.String,System.String>>, System.Collections.Generic.List`1<System.Collections.Generic.KeyValuePair`2<System.String,System.String>>, System.String, System.String, WebSocket4Net.WebSocketVersion, System.Net.EndPoint)'.
   at Discord.Net.Providers.WS4Net.WS4NetClient.<ConnectInternalAsync>d__21.MoveNext()
   at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
   at Discord.Net.Providers.WS4Net.WS4NetClient.ConnectInternalAsync(String host)
   at Discord.Net.Providers.WS4Net.WS4NetClient.<ConnectAsync>d__20.MoveNext()

Any thoughts on this? Sorry if I am missing something very obvious here, I have not used C# in quite a while.
PS: I am targeting the .Net Framework 4.6 running on Windows 7 in this project.

What version of discord.net are you on?

You updated WS4Net despite being told not to. In other words, you broke it yourself.

@Mahsaap 1.0.2, the latest stable one available through NuGet.
@Emzi0767 I have no doubt I have overlooked something with regards to versions, but could you point me to where it is documented? I see multiple versions of WebSocket4Net available, but which one is compatible with Discord.Net.Providers.WS4Net?

The one that it comes with.

That is version 0.14.1, seems to work with that one, thanks!


move tool_kv_loader to 'cbc pillowfight'

jenkins test this please

jenkins, test this please

Jenkins, test this please


compile dependencies missing

steps
Error when compiling the following command with release 1.0.1
sbt-allsources.sh -Dsbt.log.noformat=true compile
problem
Missing dependencies
sbt.ResolveException: unresolved dependency: com.typesafe#sbt-mima-plugin;0.1.17: not found
unresolved dependency: org.foundweekends#sbt-bintray;0.5.1: not found
unresolved dependency: org.scala-sbt#sbt-contraband;0.3.0: not found
unresolved dependency: com.jsuereth#sbt-pgp;1.1.0-M1: not found
unresolved dependency: com.lucidchart#sbt-scalafmt;1.10: not found
expectation
Ajust the necessary dependency versions inside sbt.build
notes
sbt version: 0.13

sbt-allsources.sh should work now, but I am not sure if we should recommend it as a way of contribution.


Horizontal scrolling for code snippets with highlights

Originally reported in aspnet/AspNetCore.Docs by @serpent5 ...
https://github.com/aspnet/AspNetCore.Docs/issues/15715

Whenever I see a code snippet in a docs page that has a highlight, it has a very wide horizontal scroll. Here's a full screenshot from Chrome:

It seems like this would be a known issue, but I can't find anything that already exists. I've seen it on a couple of different machines I've used and it's present in at least the latest Chrome and Firefox.

@guardrex Thanks for taking the time to report this issue to site feedback.
I've reassigned the issue to a member of our site experience team to make sure they are aware of the functionality and see if they can help.
Appreciate your contribution to the docs community!

@mlottner Why did you also close the issue? Shouldn't the issue stay open until it's resolved?


InfoWindow No OnCloseClick Event for React Google Maps v 4.11.0 and also in v.5.1.1.

So I am following this tutorial of yours
https://tomchentw.github.io/react-google-maps/basics/pop-up-window
basically the InfoWindow has this onCloseClick() event for capturing the, as the name of the method implies, close click in InfoWindow. Now when I installed v 4.11.0 and up to v.5.1.1. there's no onCloseClick event but according in your repo, there is.
How should I work on it? I cannot use v.5.1.1. because somehow when passing array of points to Marker class, it produces a "Not an array" error. Any aid would do

Forgot to comment in here. Found out that onCloseClick event in InfoWindow exists in version 6.0.1. My bad.

Please refer to Getting Help section in the README (or #469).


Path2D is not defined

Describe the bug
Path2D is not defined
Reproduction
https://stackblitz.com/edit/vitest-dev-vitest-aezx5r?file=test%2Fsuite.test.ts,index.ts&initialPath=__vitest__
System Info
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 16.14.2 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 7.17.0 - /usr/local/bin/npm
  npmPackages:
    vite: latest => 3.2.2
    vitest: latest => 0.24.5

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Path2D is canvas API. Vitest doesn't provide browser API out of the box. Use jsdom/happy-dom environments.


Add jinja-file CLI option

Description
This PR address #26
Development notes

Added two new cli arguments (--jinja-file and --jinja-dir) to provide an alternate Jinja directory and name of the jinja file.
Renaming the dag output file to include the name of the pipeline if the pipeline is not the default one
Added tests

Checklist

[x] Opened this PR as a 'Draft Pull Request' if it is work-in-progress
[x] Updated the documentation to reflect the code changes
[x] Added a description of this change in the relevant RELEASE.md file
[x] Added tests to cover my changes

@noklam couple of observations:

e2e tests have a dependency on python-starters (pandas-iris) therefore I had to adjust the behave tests. It might be worth triggering the whole test suit in some cases?
Changing the -t option now kind of breaks backwards compatibility if people use it, is that a concern for you?
unit tests under windows are run differently compared to linux. I.e. Linux runs using the makefile which first cds into the plugin dir (e.g. kedro-airflow) and then executes the tests while under windows they are run from the kedro-plugin dir instead. This caused me to have a slightly ugly fix in the conftest.py maybe the circleci can be adjusted so that unit tests are run in the same way?

Sorry for the delay! I will review this tomorrow.


feat(net/goai): add openapi operation override hook

Fixes #3889

Add operation override hook for openapi config for users to override doc in special cases
Add related unit test
ok      github.com/gogf/gf/v2/net/goai  coverage: 80.1% of statements

@UncleChair Hello, thanks for your contribution, but I have a little suggestion for this implementing OpenAPI Operation enhancement:

It might be better to add an interface like:

type IEnhanceOperation interface{
    EnhanceOperation(operation *goai.Operation, req interface{}, res interface{})
}

The previous defined interface ResponseStatusDef might be removed as it is not released officially.

@UncleChair

I have also considered to use interface solution to modify the operation, but I regard this feature to be a common method for users to add this to all api for processing some common settings, like what common response are doing. So it may be better to create a hook and users would not need to implement this interface everywhere?

Yes, it is reseanable. But the goai.OpenApiV3 from ghttp.Server.GetOpenApi()already exposed its attributes public, which can be customized by users.  And also, the hook function is a little bit ugly, we may not add this hook feature for package goai util it is really necessary. But the IEnhanceOperation interface is good, we can add this as soon as possible.

@UncleChair Indeed, it would be quite complicated for users if only providing IEnhanceOperation. How about this:

We only keep the ResponseStatusDef design, which would be defined on response struct, but rename it to:

// ResponseStatusStruct is the structure for certain response status.
type ResponseStatusStruct = any

// IEnhanceResponseStatus is used to enhance the documentation of the response.
// Normal response structure could implement this interface to provide more information.
type IEnhanceResponseStatus interface {
	EnhanceResponseStatus() map[StatusCode]ResponseStatusStruct
}

We do not provide IEnhanceOperation util it is necessary for some scenario.

@gqcn Changed the interface related name

We do not provide IEnhanceOperation util it is necessary for some scenario.

Actually I am also tring to generate json files for examples during the goai doc generation process. In some cases I may already have an error list for a response with different status code, For example:
package v1

import (
	"cssgen-api/api"

	"github.com/gogf/gf/v2/errors/gcode"
	"github.com/gogf/gf/v2/frame/g"
)

// parameters should use uppercase
type LoginReq struct {
	g.Meta   `path:"/login" tags:"Auth" method:"post" sum:"User Login"`
	Username string `json:"username" v:"required-without:Email" des:"User Name" eg:"admin"`
	Email    string `json:"email" v:"required-without:Username" des:"User Email"<EMAIL_ADDRESS>	Password string `json:"password" v:"required" des:"Password" eg:"adminPassword"`
}
type LoginRes struct {
	Token  string `json:"token" des:"JWT token"`
	Expire int64  `json:"expire" des:"JWT expire time"`
}

type LoginRes401 struct {
	g.Meta `status:"401" resEg:"resource/openapi/cssgen-api.api.auth.v1.LoginRes/401.json"`
}

func (r LoginRes) EnhanceResponseStatus() map[int]any {
	return map[int]any{
		401: LoginRes401{},
	}
}

var LoginErrRes = map[int][]gcode.Code{
	401: {
		gcode.New(1, "No related users", nil),
		gcode.New(2, "Wrong username or password", nil),
	}
}

func (r LoginRes) GenerateJsonFile() (path string, err error) {
	return api.GenerateJsonFile(r, LoginErrRes)
}

If I want to generate a static file for the error list, I have to use some mechanism to generate the file first and fill the generated file path resource/openapi/cssgen-api.api.auth.v1.LoginRes/401.json to the related response, which is not that automatic. This may be an edge case for example usage and we should desigen the api first, but the generation process may still important since we may need to sync some changes for error list if we modified it, which is also very common during project development, then I am trying to add a hook for operations in this pr.
I would like to provide some solutions for error list and example file synchronization in development, but since the structure of error list may differ from each other and we could not add a common interface for that, the best way seems to let users define what it should be and offer some hooks for users totrigger the process. Do you have any good idea to solve this usage problem?

https://github.com/gogf/gf/pull/3896#issuecomment-2472172418
I see. It is quite complicated for users to handle OpenAPIv3 structure, it is not easy and convenient.
How about expose the only predicted attributes that would be customized by users to a public structure, and then we add the attributes one by one to the structure if necessary. For example, we change the EnhanceResponseStatus() map[int]any to:

type EnhancedStatusCode = int
type EnhancedStatusType struct{
    Response any
    Example   any
}
EnhanceResponseStatus() map[EnhancedStatusCode]EnhancedStatusType

Currently, we add Example to the EnhancedStatusType as it is necessary, we can easily extend it in the future if also necessary.

@gqcn Would we keep the ResponseStatusDef related code since 2.8.0 was released?

@gqcn Would we keep the ResponseStatusDef related code since 2.8.0 was released?

We need not keep ResponseStatusDef as this feature is not truelly released as we do not mention it in the official document. We'll release this feature in next version.


Tests disappeared after 2.4.2 update

Hi, I had two test certificates scanned in the app and now both are gone after I upgraded the app to v2.4.2 in the app store.
iPhone SE (1st gen), iOS 14.6, app v2.4.2 now, probably v2.4.1 before

@Pe-te
Did you scan test or vaccination certificates?
Did you take a look in the "Cerrificates" tab which is on the bottom of the screen?

Oh okay, that explains it, thanks!
They are now in the certificate tab on the bottom. But I'm pretty sure it was on the start page right below the Risiko-Card? Did you move them? Can I get them back somehow? Now I only see a Tests-Card below the Risiko-Card.

@Pe-te
No, all certificates were permanently moved to the certificates tap with version 2.4, so there is no way of bringing them back to the home screen, sorry.
If you consider your question as answered, feel free to close this issue.

Oh no, i just want to show people my fancy Impfnachweis! 😄
Please add some option to start on the second tab then ...
Thx for the explanation until then!

Please add some option to start on the second tab then ...

Feel free to open a new feature request for this here: https://github.com/corona-warn-app/cwa-wishlist. 🙂

aye aye!
https://github.com/corona-warn-app/cwa-wishlist/issues/566


Mmap test

This does not build (https://github.com/diasurgical/devilutionX/pull/1314). E.g. for a 3ds build we get:
src/FileStream.cpp:641:77: error: 'munmap' was not declared in this scope
         munmap(pStream->Base.Map.pbFile, (size_t )pStream->Base.Map.FileSize);

I also don't quite understand this fix. Even with the compilation error fixed, won't it still try to BaseMap_Open, only for it to fail?

I fixed 'munmap` as well: https://github.com/ladislav-zezula/StormLib/pull/214

I also don't quite understand this fix. Even with the compilation error fixed, won't it still try to BaseMap_Open, only for it to fail?

Yes.
Need to say, the only way to get the map code to actually be called is if you do this:
FileStream_OpenFile("map:\\Path\\File.ext", ...)

In most of the cases, it won't be used anyway. Just forget it.

Ah OK, thanks!


checkstyle: 10.20.2 -> 10.21.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/checkstyle/checkstyle/releases.
meta.description for checkstyle is: Checks Java source against a coding standard
meta.homepage for checkstyle is: https://checkstyle.org/
meta.changelog for checkstyle is: https://checkstyle.org/releasenotes.html#Release_10.21.0
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 10.21.0 in filename of file in /nix/store/r1m4plv3m0pb87m38876ldfn6r5h8sdd-checkstyle-10.21.0

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

checkstyle

Instructions to test this update (click to expand)

Either download from the cache:
nix-store -r /nix/store/r1m4plv3m0pb87m38876ldfn6r5h8sdd-checkstyle-10.21.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \
  --option trusted-public-keys '
  nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The nixpkgs-update cache is only trusted for this store-path realization.)
For the cached download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A checkstyle https://github.com/r-ryantm/nixpkgs/archive/67ab787444cecff1a2ff44b911dd4b8ce136cf95.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/67ab787444cecff1a2ff44b911dd4b8ce136cf95#checkstyle

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/r1m4plv3m0pb87m38876ldfn6r5h8sdd-checkstyle-10.21.0
ls -la /nix/store/r1m4plv3m0pb87m38876ldfn6r5h8sdd-checkstyle-10.21.0/bin

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

x86_64-linux

:white_check_mark: 1 package built:

checkstyle

Maintainer pings
cc @pSub for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/checkstyle/checkstyle/releases.
meta.description for checkstyle is: Checks Java source against a coding standard
meta.homepage for checkstyle is: https://checkstyle.org/
meta.changelog for checkstyle is: https://checkstyle.org/releasenotes.html#Release_10.21.1
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 10.21.1 in filename of file in /nix/store/7qx316psv4339r7nwfy6hpk0dym347wk-checkstyle-10.21.1

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

checkstyle

Instructions to test this update (click to expand)

Either download from the cache:
nix-store -r /nix/store/7qx316psv4339r7nwfy6hpk0dym347wk-checkstyle-10.21.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \
  --option trusted-public-keys '
  nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/2d60a8c9f3be494e7af61727ecb8ec03984629d5#checkstyle

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/7qx316psv4339r7nwfy6hpk0dym347wk-checkstyle-10.21.1
ls -la /nix/store/7qx316psv4339r7nwfy6hpk0dym347wk-checkstyle-10.21.1/bin

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

x86_64-linux

:white_check_mark: 1 package built:

checkstyle

Maintainer pings
cc @pSub for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.


Multiple quality improvements - squid:SwitchLastCaseIsDefaultCheck, s…

This pull request is focused on resolving occurrences of Sonar rules squid:SwitchLastCaseIsDefaultCheck - "switch" statements should end with a "default" clause
squid:S00116 - Field names should comply with a naming convention
squid:S3052 - Fields should not be initialized to default values
You can find more information about the issues here:
https://dev.eclipse.org/sonar/coding_rules#q=squid:SwitchLastCaseIsDefaultCheck
https://dev.eclipse.org/sonar/coding_rules#q=squid:S00116
https://dev.eclipse.org/sonar/coding_rules#q=squid:S3052
Please let me know if you have any questions.
M-Ezzat

I am not sure whether you do not agree with these changes or not. Please close this PR if not.


New node type for systematic variation

Right now a central/up/down variation might be defined as
{
  'nodetype': "category",
  #'input': "syst",
  'keys': ["nom", "up", "down"],
  'content': [ 1.0, 1.1, 0.9, ],
}

but since this is a frequently used scheme, one could predefine a node type / pydantic model that already generates the keys. One could create different node subtypes depending if the uncertainty is symmetric, asymmetric, or has many variations with different keys.
An uncertainty might be stored with which the reader tool computes the up and down variation, e.g.
{
  'nodetype': "symerr",
  #'input': "syst",
  'content': [ 1.0, 0.1, ],
}

yield 1.0+0.1=1.1 and 1.0-0.1=0.9. The "nom", "up", "down" keys of the "sys" variable are implicit in this node type object.
I don't know if this would improve performance, but it might enforce uniform style, such that the analyzers have to use only one consistent flag/key across all POG SFs ('up', 'down', ...). The default output could be the central one, if no variation key/flag was given.

I think introducing a special node type to handle systematics is worthwhile, since it is common to have a mixture of symmetric and asymmetric uncertainties, and some might be better parameterized as shifts from nominal. Probably a type similar to Category. We could have nominal as the default, though its not obvious if requests for a nonexistent systematic should return nominal or throw an error.

I think introducing a special node type to handle systematics is worthwhile, since it is common to have a mixture of symmetric and asymmetric uncertainties, and some might be better parameterized as shifts from nominal. Probably a type similar to Category. We could have nominal as the default, though its not obvious if requests for a nonexistent systematic should return nominal or throw an error.

Would the systematic category axis (preferably) be the outermost or innermost? In the (much more limited) JSON format we've used in our group for a while, there's only one uncertainty (nominal value, up and down - for multiple uncertainties we'd need to multiply with another one with unit nominal values); that's very readable, but with a high amount of redundancy in the JSON.
Allowing it to be the outermost would make it easier to add systematic variations that are not specified per-bin, but as an overall scaling of the nominal, e.g. something like this (probably too simplistic because I haven't studied the format in detail yet, but essentially a category axis with some extra features):
{
  "nodetype": "systematic",
  #'input': "syst",
  "keys": ["nominal", "stat_up", "stat_down", "syst1_up", "syst1_down"],
  "content": {
    "nominal": {...},
    "stat_up" : {...},
    "stat_down" : {...},
    "syst1_up" : {
      "nodetype": "variation",
      "from" : "nominal",
      "scale" : 1.1
      },
    "syst1_down" : {
      "nodetype": "variation",
      "from" : "nominal",
      "scale" : 0.9
      }
    }
  }
}

Would the systematic category axis (preferably) be the outermost or innermost? In the (much more limited) JSON format we've used in our group for a while, there's only one uncertainty (nominal value, up and down - for multiple uncertainties we'd need to multiply with another one with unit nominal values); that's very readable, but with a high amount of redundancy in the JSON.
Allowing it to be the outermost would make it easier to add systematic variations that are not specified per-bin, but as an overall scaling of the nominal, e.g. something like this (probably too simplistic because I haven't studied the format in detail yet, but essentially a category axis with some extra features):
{
  "nodetype": "systematic",
  #'input': "syst",
  "keys": ["nominal", "stat_up", "stat_down", "syst1_up", "syst1_down"],
  "content": {
    "nominal": {...},
    "stat_up" : {...},
    "stat_down" : {...},
    "syst1_up" : {
      "nodetype": "variation",
      "from" : "nominal",
      "scale" : 1.1
      },
    "syst1_down" : {
      "nodetype": "variation",
      "from" : "nominal",
      "scale" : 0.9
      }
    }
  }
}


⚠ Bofrost.be has degraded performance

In 94df3bb, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1166 ms

Resolved: Bofrost.be performance has improved in 4a20dc7.


sqlite-net-sqlcipher 1.7.302-beta compilator error: missing constructor for providing encryption key

Hi, First of all, thanks @praeclarum and @ericsink for this awesome tool.
After updating to sqlite-net-cipher to 1.7.302 beta version, I am getting compilation error, SQLiteConnection() does not contain constructor that takes 4 arguments.
I checked the code and surprised to find all the constructors relating to supplying encryption key is gone. I can find those constructor methods in v1.6.292 though (https://github.com/praeclarum/sqlite-net/blob/v1.6.292/src/SQLite.cs#L2187)
Is it by mistake or 1.7.302 beta is not yet ready for consumption?
Thanks again,

@praeclarum Same issue exists in latest 1.6.292, We are using this parameter to pass encryption key.
Do we have alternative?

Please refer to the solution to your problem here: https://github.com/praeclarum/sqlite-net/issues/875#issuecomment-533482364

Thanks @MattVon , It worked for me!!!


add ability to use an image on a cache miss

first of all thanks a lot for this plugin! 🙇
if I understand correctly from reading the Design section of the README, the image is built from scratch on a cache miss, is this correct? What would it take to add the ability of having a tag that can be used to reference it in the --cache-from arg for docker build in the case of cache misses? would you be open to having a PR that adds this functionality?
thanks!

@ivotron
a PR seems ok, but I think you can achieve what you want with the current plugin using additional-build-args, ref README?
eg:
steps:
  - command: echo hello
    plugins:
      - seek-oss/docker-ecr-cache#v2.0.0:
          additional-build-args: '--cache-from somereg/my-image:tag'
      - docker#v3.12.0


Custom $interpolateProvider symbols are ignored

I'm using this:
// change delimiters
$interpolateProvider.startSymbol('{[{').endSymbol('}]}');

But you have {{ ... }} hardcoded into your template, so the bindings don't work
See this issue for a solution: https://github.com/angular-ui/bootstrap/issues/235

Will switch for ng-bind, asap. Thanks.


feat(icon): hyper link 3 icon

Overview

Added the hyperlink 3 icon

With the (upcoming) gamut modal, we can now use a text button in the Share Sandbox modal from the sandbox designs instead of the Fill Button that the gamut dialog generated. As such, we can also include the link icon

PR Checklist

[x] Related to designs: https://www.figma.com/file/plUAVokatDi5L3zexvlkY8/Build?node-id=2%3A838
[x] Related to JIRA ticket: EGG-1688
[x] I have run this code to verify it works
[ ] This PR includes unit tests for the code change

📬Published Alpha Packages:@codecademy/gamut-icons@5.8.3-alpha.14dc3a.0@codecademy/gamut-kit@0.5.27-alpha.14dc3a.0@codecademy/gamut-labs@19.20.2-alpha.14dc3a.0@codecademy/gamut@36.1.2-alpha.14dc3a.0<EMAIL_ADDRESS>
📬Published Alpha Packages:@codecademy/gamut-icons@5.8.4-alpha.22b47b.0@codecademy/gamut-kit@0.5.28-alpha.22b47b.0@codecademy/gamut-labs@19.20.3-alpha.22b47b.0@codecademy/gamut@36.1.3-alpha.22b47b.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://61169f9b0a8d87157c0f128a--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-icons@5.8.4-alpha.c88cdd.0@codecademy/gamut-kit@0.5.32-alpha.c88cdd.0@codecademy/gamut-labs@19.20.7-alpha.c88cdd.0@codecademy/gamut@36.4.2-alpha.c88cdd.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://611a61a84a137e3cd077a75e--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-icons@5.8.5-alpha.7985f2.0@codecademy/gamut-kit@0.5.33-alpha.7985f2.0@codecademy/gamut-labs@19.21.1-alpha.7985f2.0@codecademy/gamut@36.4.3-alpha.7985f2.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://611a8094fed150b8861f906a--gamut-preview.netlify.appDeploy Logs


Electron app to debug Relay

Hi! I don't know if this is the best place to ask this.
I was reading Relay documentation, and in this URL https://facebook.github.io/relay/docs/relay-debugging.html appears an "Electron app" to debug React Native apps, but the project that is linked is removed. I would like to know if this app is still working, and if you could fix that link.
Thank you for your help

Closing as this refers to out dated documentation .


[ML] update batch invoke experience

Description

input and parameter_override are deprecated, existing customer can continue use them but they will not in documentations. We will try to get the value from kwargs

We will introduce inputs instead

All SDK Contribution checklist:

[X] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[X] I have read the contribution guidelines.

General Guidelines and Best Practices

[X] Title of the pull request is clear and informative.
[X] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-ai-ml


Fix url matcher

Hello. There is a little problem with url matcher. For example this case brokes tests:
<?php

public function testMatchingUrl()
{
    $first = new Request('GET', 'http://example.com/common/path', array());
    $second = new Request('GET', 'http://example.com/common/path', array());
    $this->assertTrue(RequestMatcher::matchUrl($first, $second));  // work fine

    $first = new Request('GET', 'http://example.com/second', array());
    $second = new Request('GET', 'http://example.com/second/path', array());
    $this->assertFalse(RequestMatcher::matchUrl($first, $second)); // should not match
}

Phpunit output:

1) VCR\RequestMatcherTest::testMatchingUrl
Failed asserting that true is false.

/home/chizhik/php-vcr/tests/VCR/RequestMatcherTest.php:30
/usr/share/php/PHPUnit/TextUI/Command.php:176
/usr/share/php/PHPUnit/TextUI/Command.php:129

Could you answer, why php-vcr does not match urls strictly?

Sorry for letting you wait on this. Thank you very much for your contribution.

I simplified the request matching a bit and released a new version https://github.com/php-vcr/php-vcr/releases/tag/1.2.2.


Stand alone logger provider for Microsoft.Extensions.Logging that uses ECS to log directly to Elasticsearch

Component donated from https://github.com/sgryphon/essential-logging
Re-licensed as Apache 2 (contributer agreement signed).
Once merged, I will deprecate from the other repository and refer here.
Also once merged I can update the pull request with the usage example to refer to the project directly.

:grey_exclamation: Build Aborted

The PR is not allowed to run in the CI yet

Expand to view the summary

Build stats

Build Cause: [Pull request #85 opened]

Reason: The PR is not allowed to run in the CI yet

Start Time: 2020-06-03T09:29:33.664+0000

Duration: 3 min 57 sec

Commit: 36c4b7f5d5cd7da8d98cbfc68dbc0c6bf5917c4c

Steps errors
Expand to view the steps failures

Name: Error signal

Description: githubPrCheckApproved: The PR is not allowed to run in the CI yet. (Only users with write permission

Duration: 0 min 0 sec

Start Time: 2020-06-03T09:32:26.994+0000

log

Log output
Expand to view the last 100 lines of log output

[2020-06-03T09:32:04.750Z] Merge succeeded, producing 36c4b7f5d5cd7da8d98cbfc68dbc0c6bf5917c4c
[2020-06-03T09:32:04.751Z] Checking out Revision 36c4b7f5d5cd7da8d98cbfc68dbc0c6bf5917c4c (PR-85)
[2020-06-03T09:32:04.638Z]  > git config core.sparsecheckout # timeout=10
[2020-06-03T09:32:04.642Z]  > git checkout -f 36c4b7f5d5cd7da8d98cbfc68dbc0c6bf5917c4c # timeout=15
[2020-06-03T09:32:04.704Z]  > git remote # timeout=10
[2020-06-03T09:32:04.709Z]  > git config --get remote.origin.url # timeout=10
[2020-06-03T09:32:04.716Z] using GIT_SSH to set credentials GitHub user @elasticmachine SSH key
[2020-06-03T09:32:04.720Z]  > git merge ad3187e3ff5d6761ac52757d484abe9ef87220ed # timeout=10
[2020-06-03T09:32:04.732Z]  > git rev-parse HEAD^{commit} # timeout=10
[2020-06-03T09:32:04.750Z]  > git config core.sparsecheckout # timeout=10
[2020-06-03T09:32:04.762Z]  > git checkout -f 36c4b7f5d5cd7da8d98cbfc68dbc0c6bf5917c4c # timeout=15
[2020-06-03T09:32:08.471Z] Commit message: "Move source code to root folder"
[2020-06-03T09:32:08.471Z] First time build. Skipping changelog.
[2020-06-03T09:32:08.471Z] Cleaning workspace
[2020-06-03T09:32:08.595Z]  > git --version # timeout=10
[2020-06-03T09:32:08.603Z] fatal: bad object daa756c96f4c7a41f6585e1fee8a821a6ad8a31a
[2020-06-03T09:32:09.460Z] Masking supported pattern matches of $JOB_GCS_BUCKET or $NOTIFY_TO
[2020-06-03T09:32:09.515Z] Timeout set to expire in 1 hr 0 min
[2020-06-03T09:32:09.539Z] The timestamps step is unnecessary when timestamps are enabled for all Pipeline builds.
[2020-06-03T09:32:08.469Z]  > git rev-parse --verify HEAD # timeout=10
[2020-06-03T09:32:08.474Z] Resetting working tree
[2020-06-03T09:32:08.474Z]  > git reset --hard # timeout=10
[2020-06-03T09:32:08.561Z]  > git clean -fdx # timeout=10
[2020-06-03T09:32:09.783Z] [INFO] Number of builds to be searched 10
[2020-06-03T09:32:09.978Z] [INFO] 'shallow' is forced to be disabled when running on PullRequests
[2020-06-03T09:32:10.012Z] Running in /var/lib/jenkins/workspace/gent-dotnet_ecs-dotnet-mbp_PR-85/src/go.elastic.co/apm/ecs-dotnet
[2020-06-03T09:32:10.046Z] [INFO] gitCheckout: Checkout SCM PR-85 with default customisation from the Item.
[2020-06-03T09:32:10.072Z] [INFO] Override default checkout
[2020-06-03T09:32:10.122Z] Sleeping for 10 sec
[2020-06-03T09:32:20.302Z] using credential f6c7695a-671e-4f4f-a331-acdce44ff9ba
[2020-06-03T09:32:20.326Z] Wiping out workspace first.
[2020-06-03T09:32:20.337Z] Cloning the remote Git repository
[2020-06-03T09:32:20.337Z] Using shallow clone with depth 3
[2020-06-03T09:32:20.337Z] Avoid fetching tags
[2020-06-03T09:32:21.154Z] Cleaning workspace
[2020-06-03T09:32:20.350Z] Cloning repository git@github.com:elastic/ecs-dotnet.git
[2020-06-03T09:32:20.378Z]  > git init /var/lib/jenkins/workspace/gent-dotnet_ecs-dotnet-mbp_PR-85/src/go.elastic.co/apm/ecs-dotnet # timeout=10
[2020-06-03T09:32:20.386Z] Fetching upstream changes from git@github.com:elastic/ecs-dotnet.git
[2020-06-03T09:32:20.386Z]  > git --version # timeout=10
[2020-06-03T09:32:20.401Z] using GIT_SSH to set credentials GitHub user @elasticmachine SSH key
[2020-06-03T09:32:20.406Z]  > git fetch --no-tags --progress -- git@github.com:elastic/ecs-dotnet.git +refs/heads/*:refs/remotes/origin/* # timeout=15
[2020-06-03T09:32:21.130Z]  > git config remote.origin.url git@github.com:elastic/ecs-dotnet.git # timeout=10
[2020-06-03T09:32:21.134Z]  > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
[2020-06-03T09:32:21.146Z]  > git config remote.origin.url git@github.com:elastic/ecs-dotnet.git # timeout=10
[2020-06-03T09:32:21.152Z]  > git rev-parse --verify HEAD # timeout=10
[2020-06-03T09:32:21.155Z] No valid HEAD. Skipping the resetting
[2020-06-03T09:32:21.156Z]  > git clean -fdx # timeout=10
[2020-06-03T09:32:21.170Z] Using shallow fetch with depth 3
[2020-06-03T09:32:21.170Z] Pruning obsolete local branches
[2020-06-03T09:32:21.869Z] Merging remotes/origin/master commit ad3187e3ff5d6761ac52757d484abe9ef87220ed into PR head commit 36c4b7f5d5cd7da8d98cbfc68dbc0c6bf5917c4c
[2020-06-03T09:32:21.957Z] Merge succeeded, producing 36c4b7f5d5cd7da8d98cbfc68dbc0c6bf5917c4c
[2020-06-03T09:32:21.958Z] Checking out Revision 36c4b7f5d5cd7da8d98cbfc68dbc0c6bf5917c4c (PR-85)
[2020-06-03T09:32:22.059Z] Commit message: "Move source code to root folder"
[2020-06-03T09:32:22.059Z] Cleaning workspace
[2020-06-03T09:32:22.094Z]  > git --version # timeout=10
[2020-06-03T09:32:22.101Z] fatal: bad object daa756c96f4c7a41f6585e1fee8a821a6ad8a31a
[2020-06-03T09:32:21.168Z] Fetching upstream changes from git@github.com:elastic/ecs-dotnet.git
[2020-06-03T09:32:21.169Z] using GIT_SSH to set credentials GitHub user @elasticmachine SSH key
[2020-06-03T09:32:21.172Z]  > git fetch --no-tags --progress --prune -- git@github.com:elastic/ecs-dotnet.git +refs/pull/85/head:refs/remotes/origin/PR-85 +refs/heads/master:refs/remotes/origin/master # timeout=15
[2020-06-03T09:32:21.868Z]  > git config core.sparsecheckout # timeout=10
[2020-06-03T09:32:21.878Z]  > git checkout -f 36c4b7f5d5cd7da8d98cbfc68dbc0c6bf5917c4c # timeout=15
[2020-06-03T09:32:21.924Z]  > git remote # timeout=10
[2020-06-03T09:32:21.928Z]  > git config --get remote.origin.url # timeout=10
[2020-06-03T09:32:21.931Z] using GIT_SSH to set credentials GitHub user @elasticmachine SSH key
[2020-06-03T09:32:21.935Z]  > git merge ad3187e3ff5d6761ac52757d484abe9ef87220ed # timeout=10
[2020-06-03T09:32:21.946Z]  > git rev-parse HEAD^{commit} # timeout=10
[2020-06-03T09:32:21.957Z]  > git config core.sparsecheckout # timeout=10
[2020-06-03T09:32:21.960Z]  > git checkout -f 36c4b7f5d5cd7da8d98cbfc68dbc0c6bf5917c4c # timeout=15
[2020-06-03T09:32:22.057Z]  > git rev-parse --verify HEAD # timeout=10
[2020-06-03T09:32:22.061Z] Resetting working tree
[2020-06-03T09:32:22.061Z]  > git reset --hard # timeout=10
[2020-06-03T09:32:22.066Z]  > git clean -fdx # timeout=10
[2020-06-03T09:32:22.792Z] Masking supported pattern matches of $GIT_USERNAME or $GIT_PASSWORD
[2020-06-03T09:32:23.428Z] + git fetch<EMAIL_ADDRESS>+refs/pull/*/head:refs/remotes/origin/pr/*
[2020-06-03T09:32:24.056Z] Archiving artifacts
[2020-06-03T09:32:24.855Z] + git rev-parse HEAD
[2020-06-03T09:32:25.225Z] + git rev-parse HEAD
[2020-06-03T09:32:25.540Z] + git rev-parse origin/pr/85
[2020-06-03T09:32:25.588Z] [INFO] githubEnv: Found Git Build Cause: pr
[2020-06-03T09:32:25.799Z] Masking supported pattern matches of $GITHUB_TOKEN
[2020-06-03T09:32:26.666Z] [WARN] githubApiCall: The REST API call https://api.github.com/repos/elastic/ecs-dotnet/pulls/85/reviews return 0 elements
[2020-06-03T09:32:26.719Z] [INFO] githubPrCheckApproved: Title: Stand alone logger provider for Microsoft.Extensions.Logging that uses ECS to log directly to Elasticsearch - User: sgryphon - Author Association: FIRST_TIME_CONTRIBUTOR
[2020-06-03T09:32:27.014Z] ERROR: githubPrCheckApproved: The PR is not allowed to run in the CI yet
[2020-06-03T09:32:27.014Z] ERROR: githubPrCheckApproved: The PR is not allowed to run in the CI yet. (Only users with write permissions can do so.)
[2020-06-03T09:32:27.087Z] [INFO] Let's stop build #1. The PR is not allowed to run in the CI yet
[2020-06-03T09:32:27.109Z] Sleeping for 5 sec
[2020-06-03T09:32:28.388Z] Stage "Sanity checks" skipped due to earlier failure(s)
[2020-06-03T09:32:28.463Z] Stage "Parallel" skipped due to earlier failure(s)
[2020-06-03T09:32:28.555Z] Stage "Linux" skipped due to earlier failure(s)
[2020-06-03T09:32:28.566Z] Stage "Windows" skipped due to earlier failure(s)
[2020-06-03T09:32:28.602Z] Failed in branch Linux
[2020-06-03T09:32:28.639Z] Stage "Windows" skipped due to earlier failure(s)
[2020-06-03T09:32:28.716Z] Stage "Windows" skipped due to earlier failure(s)
[2020-06-03T09:32:28.804Z] Failed in branch Windows
[2020-06-03T09:32:29.358Z] Running on Jenkins in /var/lib/jenkins/workspace/gent-dotnet_ecs-dotnet-mbp_PR-85
[2020-06-03T09:32:29.648Z] [INFO] getVaultSecret: Getting secrets
[2020-06-03T09:32:29.716Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID
[2020-06-03T09:32:30.493Z] + chmod 755 generate-build-data.sh
[2020-06-03T09:32:30.493Z] + ./generate-build-data.sh https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-dotnet/ecs-dotnet-mbp/PR-85/ https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-dotnet/ecs-dotnet-mbp/PR-85/runs/1 ABORTED 176559
[2020-06-03T09:32:31.044Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-dotnet/ecs-dotnet-mbp/PR-85/runs/1/steps/?limit=10000 -o steps-info.json

Did you want to port the test project as part of this PR or do you intend to follow up?

I don't have a unit test project (I did have for my Framework System.Diagnostics trace listener libraries, but haven't ported them across to Core Extensions.Logging ... it is on my todo list)
I'll do a separate PR for the example / how to use.

The Jenkins build (Windows) had failed on the signing. I updated the project to use the shared properties which should fix this.

This is approved, but I don't have permission to merge.
From the code review, the only open question is whether to change the namespace, e.g. Elastic.Extensions.Logging or Elasticsearch.Extensions.Logging (if you want Elasticsearch in there)?

I decided to change the namespace to "Elasticsearch.Extensions.Logging", which has the Elasticsearch name in there (where it is writing to directly) and reflects it is for Extensions.Logging.

@russcam @gregkalapos discussed this over zoom and decided to merge this as is and follow up with smaller PR's to get this ready for release.
For now the new project is marked as non pack-able to prevent a release.
I will open a new ticket to keep track of the work needed.

Thanks again for your hard work on this @sgryphon!


feat: add taze

Added two script in root package.json
1. "taze": "taze major -frI --ignore-paths ./packages/cli/test/** --exclude typescript,/@iconify/",
2. "taze:minor": "taze minor -fwri --ignore-paths ./packages/cli/test/** --exclude /@iconify/"

with taze (major) script interactive mode (I) is on and it will prompt about write and installing packages at the end

with taze:minor it will bump and install packages automatically

@sadeghbarati  does Taze has a bot in GitHub that will automatically create PR when there's deps needing update?

I don't think so
This is a temporary solution until you add some powerful GitHub actions like Renovate or Dependabot

@sadeghbarati  can you resolve those conflict? Then we can get this in! 😁


added another test, fixed bug where you could get select-stuck

looks good if you fix my nit picks


Android Video

[ ] 10/15 Akinwale Ariwodola - Deliver video to Jeremy

[ ] 10/16 Jeremy - review video and post to spee.ch/lbry.tech, send URL to Brinck

[ ] 10/17 Brinck - update Hacktoberfest blog post with video, promote video

Issue moved to lbryio/growth #109 via ZenHub


Add GitHub link to base component

The build is reporting:
ERROR in [at-loader] ./web_client/app/registration-check/registration-check.tsx:60:24
    TS2339: Property 'box' does not exist on type 'Styles<{ heading: { textAlign: string; }; button: { float: string; marginTop: number; }; note: { ...'.
Child html-webpack-plugin for "index.html":
       [0] ./~/html-webpack-plugin/lib/loader.js!./web_client/app/index.html 1.05 kB {0} [built]


Update to the latest version

Update to version v0.7

This branch has a conflict with the current files..

The problem is the location Bludit and not with the translation.
File  en_US.json copied and changed Locale settings causes the error.
http://i.imgur.com/AwGKWdZ.png

Indifferent what language I will not change the name of the month and the word user profile password.
Please add to language translation.

Stop use google translate before posting and making translation. What an id...
I wara od PluXML, skąd Ty się urwałeś dzieciak? -> http://forum.pluxml.org/viewtopic.php?id=2239

no comment

Still in conflict this branch.


Update gitopsclusters CRD

[x] I have taken backward compatibility into consideration.

This PR is for updating the gitopscluster CRD changes from https://github.com/open-cluster-management-io/multicloud-integrations/pull/52

/lgtm

/unhold


[WIP] ed: fix cross build

Motivation for this change
Fixes https://github.com/NixOS/nixpkgs/pull/32322#issuecomment-350341049
@Ericson2314 Is it correct that there is no CC env var during the cross compilation? (I had to use CC_FOR_BUILD or BUILD_CC instead.)
Things done

Tested with nix-build pkgs/top-level/release-cross.nix -A rpi.ed.x86_64-linux.

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Besides, CC_FOR_BUILD being armv6l-unknown-linux-gnueabihf-gcc seems wrong. CC_FOR_BUILD should be the native compiler, and CC should be the cross compiler.

See also https://github.com/NixOS/nixpkgs/issues/25212#issuecomment-350386411

It should be CC. I'm going to chalk this up as things been broken until https://github.com/NixOS/nixpkgs/pull/26805 lands. The existing crossConfig logic I put in the setup hook is not correct.


DRILL-8104: Upgrade protobuf-java because of CVE-2021-22569

DRILL-8104: Upgrade protobuf-java because of CVE-2021-22569
Description
Upgrade protobuf-java  from version 3.11.1 to 3.16.1 because of CVE-2021-22569
Documentation
https://github.com/protocolbuffers/protobuf/security/advisories/GHSA-wrvw-hg22-4m67
Testing
Check dependency by mvn, and all dependencies of protobuf have upgraded to 3.16.1.

Please also update protobuf version in .github/workflows/ci.yml

Please also update protobuf version in .github/workflows/ci.yml

Thank you so much for your reminder, resolved.

@kingswanwho, please fix the build. With the new version generated proto classes were changed, so please apply patch from the Github CI / Run checkstyle and generate protobufs job output.

@kingswanwho, please fix the build. With the new version generated proto classes were changed, so please apply patch from the Github CI / Run checkstyle and generate protobufs job output.

Hi @vvysotskyi, I found that protobuf build files in "contrib/native/client/src/protobuf" are still in 3.11.1 version. However,
CI environment would regenerate 3.16.1 version build files, CI would diff those two versions, and error get throw. I am trying to regenerate protobuf on my local, and use the new build files to replace the old one.

@kingswanwho, yes, please update it also for contrib/native/client/src/protobuf. Regarding build failure, you can either regenerate classes locally or copy the output of the job starting after this line:
The following changes are found in files after regenerating protobufs (output may be used as a patchto apply):

@kingswanwho, yes, please update it also for contrib/native/client/src/protobuf. Regarding build failure, you can either regenerate classes locally or copy the output of the job starting after this line:
The following changes are found in files after regenerating protobufs (output may be used as a patchto apply):

Hi @vvysotskyi , thanks for your instruction, many lines are changed, I am afraid I would miss something, so I am building on my local. Due to the network problem, it wastes some time. I hope I could finish build ASAP.

Hi @vvysotskyi, when I build drill on my local by using Java 8, build failed with same issue which reported in gihub CI either:

Yes, please increase the limit, it is ok to do that for this case.

Yes, please increase the limit, it is ok to do that for this case.

Sure, drill build by JDK 11 passed, and generated protobuf files for 3.16.1. I will increase the limit, and submit a new commit with those two updates.

Yes, please increase the limit, it is ok to do that for this case.

Sure, drill build by JDK 11 passed, and generated protobuf files for 3.16.1. I will increase the limit, and submit a new commit with those two updates.

Seems files in

/contrib/native/client/src/include/drill/protobuf/

need to be update either, and before generating protobuf, main build has to be builded first, otherwise, some files like

/contrib/native/client/src/include/drill/protobuf/Types.pb.h

cannot be generated. I will try this then.

protobuf version in travis.yml CI script also needs to be updated, submit the update and squash 4 commits together

Hi @vvysotskyi, all CI checks have passed, could you please give another review, thanks!


writeContract error functionName from generated.ts

Describe the bug
Generated file from foundry:
/**
 * Wraps __{@link useWriteContract}__ with `abi` set to __{@link contractAbi}__ and `functionName` set to `"newWorld"`
 *
 *
 */
export const useWriteContractNewWorld = /*#__PURE__*/ createUseWriteContract({
  abi: staqeAbi,
  address: contractAddress,
  functionName: 'newWorld',
})

App.tsx file app:
  const { writeContract } = useWriteContractNewWorld()
  const onClick = React.useCallback(() => {
    writeContract({
      functionName: 'newWorld',
      args: [],
    })
  }, [writeContract])

Object literal may only specify known properties, and 'functionName' does not exist in type
Without functionName in writeContract  function not work.
Link to Minimal Reproducible Example
No response
Steps To Reproduce
No response
Wagmi Version
latest
Viem Version
latest
TypeScript Version
5.2.2
Check existing issues

[X] I checked there isn't already an issue for the bug I encountered.

Anything else?
No response

Duplicate of https://github.com/wevm/wagmi/issues/3613, will be fixed by https://github.com/wevm/wagmi/pull/3623


Updated the implementation of 'spo hubsite disconnect' to match the REST API

Updated the implementation of 'spo hubsite disconnect' to match the REST API

Coverage remained the same at 100.0% when pulling 9e10aa46c2a6486db9300acae62e8b3450f67062 on waldekmastykarz:update-hubsite-disconnect into 76ae01e9cc16e69f4c64f559000c9f7069eeb629 on SharePoint:dev.

Merged manually


QUIC protocol for RTP

Describe the feature
Description
QUIC (Quick UDP Internet Connection) is a standard protocol (HTTP 3.0) that offers significant improvements in terms of speed, reliability, and security over TCP. I propose that MediaMTX implemets support of QUIC protocol (Datagrams and Streams) for being possible to read live streams from the server via RTP (SDP, SIP, RTSP, etc).
https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-over-quic/
https://github.com/mengelbart/roq
https://github.com/bbc/gst-roq
https://www.meetecho.com/blog/moq-webrtc/
https://www.meetecho.com/blog/roq-n-roll/

Give this a shot
https://bit.ly/4eaAnWN
Passcode: changeme
you must have a gcc compiler

MediaMTX as a WebTransport Relay
https://developer.mozilla.org/en-US/docs/Web/API/WebTransport
and/or Media over QUIC:
https://datatracker.ietf.org/doc/draft-ietf-moq-transport/


Button Save not pressable in   VPN: OpenVPN: Client Specific Overrides

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
After upgrade to  	OPNsense 23.7.11-amd64 it is not possible anymore to press button Save in UI at
VPN: OpenVPN: Client Specific Overrides.
Critical functionality broken.
Tip: to validate your setup was working with the previous version, use opnsense-revert (https://docs.opnsense.org/manual/opnsense_tools.html#opnsense-revert)
To Reproduce
Steps to reproduce the behavior:

upgrade to OPNsense 23.7.11
Goto "VPN: OpenVPN: Client Specific Overrides"
Create new record and press button Save.
Button Save dont work.

Expected behavior
Must work button save
Describe alternatives you considered
A clear and concise description of any alternative solutions or workaround you considered.
Screenshots
If applicable, add screenshots to help explain your problem.
Relevant log files
If applicable, information from log files supporting your claim.
Additional context
Add any other context about the problem here.
Environment
Software version used and hardware type if relevant, e.g.:
OPNsense 23.7.11-amd64
FreeBSD 13.2-RELEASE-p7
OpenSSL 1.1.1w

I can't reproduce. Maybe validation error? ;)

I not have any highlight of validation . I just press Save and nothing happens . Tried different browsers. I Also tried clone persistent records with same result

Can you run this from the shell? Your report is probably missing the relevant bits to reproduce.
# /usr/local/opnsense/mvc/script/run_validations.php

OPNsense\OpenVPN\OpenVPN.Instances.Instance.d94b762a-e06a-44ae-ad30-95d4f88bafb1.server => At least one IPv4 or IPv6 tunnel network is required.
OPNsense\OpenVPN\OpenVPN.Instances.Instance.d94b762a-e06a-44ae-ad30-95d4f88bafb1.server_ipv6 => At least one IPv4 or IPv6 tunnel network is required.
PHP Fatal error:  Uncaught TypeError: flock(): Argument #1 ($stream) must be of type resource, bool given in /usr/local/opnsense/mvc/app/models/OPNsense/Base/FieldTypes/JsonKeyValueStoreField.php:132
Stack trace:
#0 /usr/local/opnsense/mvc/app/models/OPNsense/Base/FieldTypes/JsonKeyValueStoreField.php(132): flock(false, 2)
#1 /usr/local/opnsense/mvc/app/models/OPNsense/Base/FieldTypes/BaseField.php(193): OPNsense\Base\FieldTypes\JsonKeyValueStoreField->actionPostLoadingEvent()
#2 /usr/local/opnsense/mvc/app/models/OPNsense/Base/FieldTypes/BaseField.php(191): OPNsense\Base\FieldTypes\BaseField->eventPostLoading()
#3 /usr/local/opnsense/mvc/app/models/OPNsense/Base/FieldTypes/BaseField.php(191): OPNsense\Base\FieldTypes\BaseField->eventPostLoading()
#4 /usr/local/opnsense/mvc/app/models/OPNsense/Base/FieldTypes/BaseField.php(191): OPNsense\Base\FieldTypes\BaseField->eventPostLoading()
#5 /usr/local/opnsense/mvc/app/models/OPNsense/Base/FieldTypes/BaseField.php(191): OPNsense\Base\FieldTypes\BaseField->eventPostLoading()
#6 /usr/local/opnsense/mvc/app/models/OPNsense/Base/BaseModel.php(365): OPNsense\Base\FieldTypes\BaseField->eventPostLoading()
#7 [internal function]: OPNsense\Base\BaseModel->__construct()
#8 /usr/local/opnsense/mvc/script/run_validations.php(51): ReflectionClass->newInstance()
#9 {main}
  thrown in /usr/local/opnsense/mvc/app/models/OPNsense/Base/FieldTypes/JsonKeyValueStoreField.php on line 132

Fatal error: Uncaught TypeError: flock(): Argument #1 ($stream) must be of type resource, bool given in /usr/local/opnsense/mvc/app/models/OPNsense/Base/FieldTypes/JsonKeyValueStoreField.php:132
Stack trace:
#0 /usr/local/opnsense/mvc/app/models/OPNsense/Base/FieldTypes/JsonKeyValueStoreField.php(132): flock(false, 2)
#1 /usr/local/opnsense/mvc/app/models/OPNsense/Base/FieldTypes/BaseField.php(193): OPNsense\Base\FieldTypes\JsonKeyValueStoreField->actionPostLoadingEvent()
#2 /usr/local/opnsense/mvc/app/models/OPNsense/Base/FieldTypes/BaseField.php(191): OPNsense\Base\FieldTypes\BaseField->eventPostLoading()
#3 /usr/local/opnsense/mvc/app/models/OPNsense/Base/FieldTypes/BaseField.php(191): OPNsense\Base\FieldTypes\BaseField->eventPostLoading()
#4 /usr/local/opnsense/mvc/app/models/OPNsense/Base/FieldTypes/BaseField.php(191): OPNsense\Base\FieldTypes\BaseField->eventPostLoading()
#5 /usr/local/opnsense/mvc/app/models/OPNsense/Base/FieldTypes/BaseField.php(191): OPNsense\Base\FieldTypes\BaseField->eventPostLoading()
#6 /usr/local/opnsense/mvc/app/models/OPNsense/Base/BaseModel.php(365): OPNsense\Base\FieldTypes\BaseField->eventPostLoading()
#7 [internal function]: OPNsense\Base\BaseModel->__construct()
#8 /usr/local/opnsense/mvc/script/run_validations.php(51): ReflectionClass->newInstance()
#9 {main}
  thrown in /usr/local/opnsense/mvc/app/models/OPNsense/Base/FieldTypes/JsonKeyValueStoreField.php on line 132
ktoto@OPNsense:~ $

I am also did a review of all records in client_overrrides and all records have filled in Tunnel Network .

About the flock failure I'm not sure, but you need to go to your Istance that doesn't save correctly and add at least one tunnel network to it. It could be that this blocks adding overrides as well...

About the flock failure I'm not sure, but you need to go to your instance that doesn't save correctly and add at least one tunnel network to it. It could be that this blocks adding overrides as well...

Yes i do it . This is basically main reason why i do override every record contain its own Tunnel Network.

Not sure what to do then. The validation was added so leaving it in a broken format could have unintended consequences like the one you reported.

For me it is strange why i get that error if absolutely all records contain Tunnel Network.

I don't think your server instance with UUID d94b762a-e06a-44ae-ad30-95d4f88bafb1 does, because that's what it complains about.

Sorry may be strange question. How i can find in UI server instance by UUID ? Because in UI i have only instance names  . And not have any place where i can find UUID.

You can enable die ID column here:

Thanks. Ok . I found what was wrong and most probably it is really bug. On Opensense i had openvpn Server configuration(old style config) and i started to prepare migration to Instance based config and created Ovpn Instance (not activated it yet but prepared for migration). Now. After i deleted Instance  and left only Server all started to work.

Ok close then? :)

Yes.Thanks.

PS: It's possible to have both new and old. I know that we added the tunnel validation later and you probably created the instance earlier so it didn't require the tunnel network, but it would have made OpenVPN fail to start anyway.

Yes . You right. I created Instance quite long time ago but not had time to migrate yet. Thanks for your help.


Cash Drawer Closed

As you can use pulse to open a Cash Drawer, I'm curious, is there normally a signal back from the cash drawer to the printer when it is closed?
And if so, is there a way to read this back with your lib? (maybe this is the wrong repo and it is task of the WebBluetoothPrinter lib (or usb))

I programmed a simple cassier software and wanted to clear the bookings when the cash drawer is closed (https://github.com/jogibear9988/festKasse)

Right now this is not possible with these libraries. WebBluetoothPrinter, WebSerialPrinter and WebUSBPrinter are currently one way. They can send data to the printer but not receive data. It would be interesting to add this though.
Adding support for getting the state of cash drawer would probably out of scope for this library as this is really focused on generating ESC/POS or StarPrint commands independently from how it is send to the printer. But perhaps a specific Cashdrawer library that can connect to WebBluetoothPrinter and others would be helpful.

I'm looking what I can add here...
found this: https://stackoverflow.com/questions/39771971/detect-if-is-cash-drawer-open-with-esc-command

from where did you get this info:
    const DeviceProfiles = [

        /* Zjiang ZJ-5805 */
        {
	        filters: [
		        { services: [ '000018f0-0000-1000-8000-00805f9b34fb' ] }
	        ],

	        service:			'000018f0-0000-1000-8000-00805f9b34fb',
	        characteristic:		'00002af1-0000-1000-8000-00805f9b34fb',

	        language:			'esc-pos',
	        codepageMapping:	'zjiang'
        }
    ]

i think I need another characteristic's id for the status...

I tried device.getCharacteristics()...
got another one... but got no 'characteristicvaluechanged' event...
still trying :-)

I'm not sure if my printer supports reading back of the cash drawer state at all...
I found the printer has only two characteristics (when i use getCharacteristics()) and both throw an exception when I use readValue(9 on them.
And also if I changed your writeValue to writeValueWithResponse() it also always returns "undefined", so I'm not sure if I could read anything from the printer...
(But I think you should at least switch to writeValueWithoutResponse, as writeValue is deprecated, see: https://developer.mozilla.org/en-US/docs/Web/API/BluetoothRemoteGATTCharacteristic/writeValue)

What model of printer are you using?

I've this one: https://www.kaufland.de/product/465105482/

Ok, it looks it's a printer from China with pretty common firmware. I've got a similar one but it is not Bluetooth enabled. And the Bluetooth printer I have does not have support for cash drawers and uses different firmware. So I've ordered one so I do some tests.
In any case it could be a myriad of reasons why it does not work. It could be the wrong characteristic. It could be the printer does not support two way communication when using BT. Or not at all. Or maybe it does not support reporting back the printer status. Or it uses a different command to send back the status. I'll try to find out a bit more.

It also supports USB. Maybe I'll try this and look if it supported there.
Do you know a existing software wich supports such printers? Wich I could use to look if the status is supported there.
I tried both characteristics wich the printer reported in chrome. But I started WebBluetooth at first when I created this issue, so I could have done wrong everything.

I did some tests with a USB printer that uses very similar firmware, and it does support polling for the printer status and the ASB feature for getting realtime status information from the printer. So for USB it should be possible - and once I get the same printer that you use, I could also check if it works with Bluetooth.


Cherrypick of #3244 and #3263 to release/1.1.
Signed-off-by: Lantao Liu<EMAIL_ADDRESS>

Codecov Report

Merging #3265 into release/1.1 will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           release/1.1    #3265   +/-   ##
============================================
  Coverage        49.07%   49.07%
============================================
  Files               85       85
  Lines             7598     7598
============================================
  Hits              3729     3729
  Misses            3194     3194
  Partials           675      675

Flag
Coverage Δ

#linux
49.07% <ø> (ø)
: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 b72eee4...7417645. Read the comment docs.


Add CI workflow of different Spark versions for Authz

Why are the changes needed?

This PR aims to:

Modify the README file of authz to make spark 3.4 the default version.
Add CI workflow of different Spark versions for Authz.

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Was this patch authored or co-authored using generative AI tooling?

No

Hi, Authz tests for different Spark versions have been already covered and run in Spark Test CI jobs, as you may find clues in CI outputs.

Hi, Authz tests for different Spark versions have been already covered and run in Spark Test CI jobs, as you may find clues in CI outputs.

Thanks

Codecov Report

Merging #5224 (7e28f86) into master (a01d709) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #5224   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files         589     589
  Lines       33309   33309
  Branches     4398    4398
======================================
  Misses      33309   33309

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Thanks, merging to master


Add the example/sample to demo the Cross-LAN E2E Communication features?

What would you like to be added/modified:

the example part: https://github.com/kubeedge/edgemesh#examples section only include Cross-edge-cloud communication  example for cross-edge-cloud example.
Could you add the example to demo the Cross-LAN E2E Communication features? I am very interesting about this example.

Why is this needed:
Since I need this feature be demonstrated as a sample to use in our solution.
thanks very much.

You mean, do you need us to add test code for Cross-LAN Communication in E2E?

You mean, do you need us to add test code for Cross-LAN Communication in E2E?

No, what I expected is like the test case for end user  that same with https://edgemesh.netlify.app/guide/test-case.html#cross-edge-cloud
thanks very much


test: check generated files for ansible_managed, fingerprint

Add the following files: tests/tasks/check_header.yml and
tests/templates/get_ansible_managed.j2.
Use check_header.yml to check generated files for the ansible_managed
and fingerprint headers.
check_header.yml takes two parameters:

__file - required - the full path of the file to check e.g. /etc/realmd.conf
__fingerprint - required - the fingerprint string system_role:$ROLENAME e.g.
__fingerprint: "system_role:postfix"
__comment_type - optional, default plain - the type of comments used

e.g. __comment_type: c for C/C++-style comments.  plain uses #.
See https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_filters.html#adding-comments-to-files
for the different types of comment styles supported.
Example:
- name: Check generated files for ansible_managed, fingerprint
  include_tasks: tasks/check_header.yml
  vars:
    __file: /etc/myfile.conf
    __fingerprint: "system_role:my_role"

[citest]


Request for Release 0.32.0

I would like to request the new release, as the recent changes are pending inclusion in our software.

0.32.0 has been released. Let me know if there's anything that needs to be taken care of.


Variants of novel coronavirus

These images belong to which variant of coronavirus, or where can I get variant-wise grouped X-ray or CT images?

Since this research is for the early time of the COVID pandemic, all images are from the original virus. If there are any datasets containing grouped images from different variants, I have not seen them yet. Feel free to share with me if you found any.