[DISCUSSION GUIDE] Week 4: Artificial Intelligence

Agenda:

[ ] Share one or two of the flood frequency or temperature change analyses [20 min].

[ ] Did you find anything unexpected, like a regime change? Can you find any evidence of anthropogenic changes, climatic oscillations, or other influences that might have contributed?
[ ] Who is the audience for your portfolio? Can you think of ways your rhetoric could be improved to better convey a message to that audience?

[ ] Reading and Discussion on AI [30 min]
[ ] Student screen share [optional, 10 min]: Review any questions or outstanding bugs from previous assignments, if applicable
[ ] Take a look at the Camp Fire using the time slider on Google Earth [20 min]
[ ] Start the new raster data assignment on vegetation recovery after the Camp Fire [10 min]

/adminteamassign @earthlab-education/ea-instructors


Go version upgrade

chore: go module upgrade
chore: upgrade go version

Since apparently the just-module rev didn't build.

Happened to see this one, so I can put my stamp on it :stuck_out_tongue:
I noticed that deploys started failing after the (not technically necessary?) golang.org/x/crypto update in #105, but I haven't had a chance to look into it.

Yeah - I just wanted to get through the dependabot noise.
The builder was failing with:
/workspace/go.mod:3: invalid go version '1.22.7': must match format 1.23

Which...I dunno, did that change? I don't think we manually edited it.
But, whatever let's see if this works...


[Bug]: The rows gets scrambled on RUN with dynamic binding

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When the user adds a row from the from with field it is observed that the fields get scrambled and inserted on the GSheet

Steps To Reproduce
Steps to reproduce:

Add a form
Add fields to the Forms
On submit ensure "Insert Query" gets added
GSheet Query :
Add an "Insert Query" into the field
Ensure to do dynamic binding

Public Sample App
No response
Version
Release

Order of the keys in Query is not preserved in the spreadsheets. Seems like a backend issue as string value of the object is parsed on BE.

GSheets 6m usage: 2300
assume 80% of these use INSERT and/or UPDATE: 1840
Stats

Stat
Values

Reach
1840

Effort (months)
<>

@prapullac tested these steps in release, it worked ok for me:
https://images.zenhubusercontent.com/275993885/c12eb88e-2169-4039-bbf7-cec033b16922/screen_recording_2022_06_05_at_11_23_37.mov

GSheets 6m usage: 2300
assume 80% of these use INSERT: 1840
Stats

Stat
Values

Reach
1840

Effort (months)
0.25

@prapullac is this still happening? This seems like a critical issue but I can't reproduce it


Fix the null exception when starting the proxy service

Fixes #7960
Motivation
When enable the broker tls and enable broker client authentication with oauth2 plugin,
the proxy service will exit with an unexpected null exception.
Because there are some methods call the authentication before initializing the flow
which will cause the token client isn't initialized before using.

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

@zymap I just noticed this fix, and do you recall why you fixed it in this way.  The true issue looks to me that the Authentication interface has a start method and a getAuthData method but that the PulsarProxy calls getAuthData before calling start.  The OAuth2 implementation assumes that start will be called first.  This PR avoids taking that assumption, but is it not a correct assumption to make?
Thanks


Does it support long content input?

hello @winktool ! what do you mean for long input?
The function takes an array of N messages of M bytes and processes them in parallel. For example you can pass an array of 4 messages of 1 byte each. Or an array of 1000 messages of 1MB each.

I tried it and if the data I enter is a long piece of hex, then I get the wrong result.
Also, is there a version for single data?

@winktool can you paste the code here? thanks

Also, is there a version for single data?

you can pass one message but in this case the performance could be worse than the CPU version due to the GPU binding memory overhead

0100000001ffe8208acf0f69b5333ff5701a41c83ca688c16536b48a488921a20b3b1761932400000000ffffffff02c01f0200000000002251208db78f8cb3622355cae7d5021d1b9cb38d9afd2a96d6b6386970b7a4638e133300000000000000000a6a082f40d38515337cc900000000

plz input this hex

Please teach me how to deal with this situation

that is a bitcoin block header in hexadecimal format. You cannot input hexadecimal string.  The sha256_gpu function takes array of bytes so you have to convert the block header to an array of bytes. You can find examples online, I cannot support you in this.

Thanks


Test stays "not run" if TestContext property is readonly, no error

Describe the bug
It was hard to locate the issue here because the error was hidden deep in the logs and additionally marked [Warning].
If test class has readonly TestContext the tests in that class will not get run. Setting this property in constructor does not affect the issue.
Additionally just changing the property from get to get;set doesn't change situation immediately, elaborate "clean;rebuild" dance is further required.
Steps To Reproduce
namespace TestProject1;

[TestClass]
public class UnitTest1 {
    // bork
    public TestContext TestContext { get; }

    // works
    //public TestContext TestContext { get; set; }

    public UnitTest1(TestContext context) => TestContext = context;

    [TestMethod]
    public void TestMethod1()
        => Assert.Fail();
}

Expected behavior
Either the test should be allowed to run even if injection of TestContext failed (it's trusted to be set in constructor) or the test should get failed with clear error message.
Actual behavior
Test stays "not run". No errors are shown:

Additional context
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <TargetFramework>net6.0</TargetFramework>
    <ImplicitUsings>enable</ImplicitUsings>
    <Nullable>enable</Nullable>

    <IsPackable>false</IsPackable>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="17.1.0" />
    <PackageReference Include="MSTest.TestAdapter" Version="2.2.8" />
    <PackageReference Include="MSTest.TestFramework" Version="2.2.8" />
    <PackageReference Include="coverlet.collector" Version="3.1.2" />
  </ItemGroup>

</Project>

Hi @pasisavolainen,
Thanks for the feedback. This is something that needs to be improved.
I think we can add an analyzer for this and also add a safety by emiting a warning in the logs when we detect that there is no setter.

Analyzer is brought by #2019

I did a few more tests and there is actually an error printed:

In Visual Studio, you have to go to Output > Tests:

With dotnet test:

Another problem that exists with your solution is that (for now), MSTest doesn't support injecting the TestContext object through the ctor (and more widely doesnt' support non-parameterized ctors.
The analyzer was added as described on my previous comment so I will move ahead and close this issue.


Transcript with Default trait and anotation removed

Transcript with Default trait and anotation removed
A little refactor to improve the transcript module
Description
Description of the pull request changes and motivation.
Type of change
Please delete options that are not relevant.

[ ] New feature
[ ] Bug fix
[ ] Optimization

Checklist

[ ] Linked to Github Issue
[ ] Unit tests added
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

[ ] This change is an Optimization

[ ] Benchmarks added/run

Codecov Report

Merging #204 (1b4a343) into main (6ee9655) will decrease coverage by 0.05%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #204      +/-   ##
==========================================
- Coverage   95.58%   95.54%   -0.05%
==========================================
  Files          62       62
  Lines        6837     6840       +3
==========================================
  Hits         6535     6535
- Misses        302      305       +3

Impacted Files
Coverage Δ

crypto/src/fiat_shamir/transcript.rs
94.33% <0.00%> (-5.67%)
:arrow_down:

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


[Feat]: Frontend Needed

What feature?
So there is design... Just wanted it in react js and tailwind
No other extras

[ ] Design to Development

Add screenshots

Code of Conduct

[ ] I agree to follow this project's Code of Conduct

I would like to work. Will you provide figma for the design?

Thats what i added as screenshot, try creating it

The upper vertical slider are for VOLUME for each set
The bottom ones are SPEED
the horizontal was CROSSFADER
Use this for ref: youdj website

Thats what i added as screenshot, try creating it
The upper vertical slider are for VOLUME for each set The bottom ones are SPEED the horizontal was CROSSFADER
Use this for ref: youdj website

I can give a try. Can you assign me?

Make sure the CD's moveable....
Clean and smooth overall✨

hii @LokeshKumar-Dev , this one seems like a complicated task. i want to collaborate on it too. Maybe it needs more than one collaborator

Hey @LokeshKumar-Dev , I don't think think the assignee @dhrumishah  is active on this one. If thats the case, Please assign it me I'll do it  with in 4 days.

This is the progress so far. https://rdj-exe.vercel.app/ . Making the Disc Responsive is a little tricky but according to the tests it should not break in Desktop Screen. @LokeshKumar-Dev

Okay, your are moving in right direction....
Make space around the whole accessing screen and center it

Finish whole screen and send....
Good job!!!

I have completed the frontend task.  https://rdj-exe.vercel.app

I have also updated the order of UI components to better suite responsive design. For instance, Song List is in the last in my UI version because track controller is more important and should be on top. Change these as per requirements.
Tasks Completed:
:heavy_check_mark: Desktop responsive Design. Can easily support Tablet as well with few breakpoints.
:heavy_check_mark: Sliders and other Components as per UI with required props.
:heavy_check_mark: Track State is managed.
:heavy_check_mark:  Songs loading from dummy data.
:heavy_check_mark: Tracks are searchable.
Things that can be Improved and remaining features:

Knob Buttons are not as per UI. The only knob react library requires a svg skin to make a knob button. So first we need to create a svg of the UI button and then create a skin and load in knob button. Check Docs here (Knob Skin Example: https://github.com/hugozap/react-rotary-knob-skin-pack/blob/master/skins/s14.js)
Functionality to actually load tracks or songs in the player, extract metadata like duration, title, singer, etc. and play the track.
Control State of all the sliders , knob buttons.
Update Disc Animation. Use Framer Motion instead of css to get a seamless animation effect. (Use track time as animation delta)

Let me know if there are any other improvements for this particular task.
@LokeshKumar-Dev, I am a third-year student participating in GSSOC. Please consider marking this task for GSSOC as well. Is there a Slack or online community available for communication? I would like to work on other tasks as well.

@LokeshKumar-Dev Please review the PR i opened. If something is missing or wrong please provide a feedback.


updated package.json

updated package babel-register from 6.23.0 to 6.24.1
Npm link :  https://www.npmjs.com/package/babel-register
Repository link : https://github.com/babel/babel/tree/master/packages/babel-register/releases

Codecov Report

Merging #16 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #16   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines          60     60
=====================================
  Hits           60     60

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 0922027...ef3e14a. Read the comment docs.


Move curvature EncodedValue out of MotorcycleTagParser

I kept the meaning of the curvature value but instead of (beeline/edge_distance)² it is now only beeline/edge_distance as it did not make a big difference (sure, the small deviations from 1 will be "earlier snap to 0.95", but in practise this didn't matter in my simple tests and having a simpler formula was preferable).
If you want to use curvature to prefer curves then do not overdo it and something like this is sufficient:
{ "priority": [{
   "if": "curvature > 0.9",
   "multiply_by": "0.3"
}]}

Otherwise, without proper turn costs, you'll see things like:

I tried to calculate some kind of a max_curve value instead as the curvature was sometimes a bit too similar to 1 and used the maximum orientation change of the PointList like:
for (int i = 1; i < pointList.size(); i++) {
    double orientation = ANGLE_CALC.calcOrientation(pointList.getLat(i - 1), pointList.getLon(i - 1),
            pointList.getLat(i), pointList.getLon(i), false);
    if (i > 1) {
        orientation = ANGLE_CALC.alignOrientation(prevOrientation, orientation);
        maxCurve = Math.max(maxCurve, Math.abs(orientation - prevOrientation));
    }
    prevOrientation = orientation;
}
maxCurveEnc.setDecimal(false, edgeFlags, Math.max(maxCurveEnc.getMinStorableDecimal(), Math.min(maxCurveEnc.getMaxStorableDecimal(),
       Math.toDegrees(maxCurve))));

But at the end it did not properly show when a road was curvy (even sometimes not for serpentines). Probably because a curvy road in OSM is often mapped smooth leading to relative small orientation changes. Of course this could happen with the curvature too if multiple ways are created but often this is not the case and of course we would need another feature like "turning angle" to complement this. A good test route for this was here.

Nice! I did not look at the exact modeling of the curvature EV, but the code changes LGTM.


[fusion-plugin-react-router#249] Add support for React Router v5

This issue was migrated from fusionjs/fusion-plugin-react-router#249 and was originally reported by @NameFILIP.

It should be fully compatible with v4: https://reacttraining.com/blog/react-router-v5/

Closed by https://github.com/fusionjs/fusionjs/commit/4bec790253489bb9dae09270c3f8e95579d8848d


#22: Implement ReaderAssert in a similar way as InputStreamAssert

Copied and renamed the InputStreamAssert to ReaderAssert together with supporting classes. Kept the same structure for Reader* as for the InputStream*.

what is the status of implementing ReaderAssert feature?

it is in limbo status but I can resurrect it by actually revieing at the PR

Closing due to lack of interest but happy to reopen it if someones wants to finish it.


.close stalls when replicating

When you call dat.close(cb) while it's still replicating data, it will never call the close callback

Hmm I saw this too but thought I fixed it closing the network/importer before the archive.
We can probably call archive.unreplicate as the first thing in close.

I'm not 100% at this point if this is a dat-* bug or was caused by some UI issue in dat-desktop not triggering some action. So take this "bug report" with a grain of salt. I'll report back here if I can reproduce after the UI issue has been addressed.

published in 1.3.2


feat(theme): Add package structure

task: https://emurgo.atlassian.net/browse/YOMO-972

it's looking solid, bringing in

[ ] update types to use ColorValue
[ ] start updating Text to correlate to its design typography


Add limit for app name

Codecov Report
Base: 62.32% // Head: 62.30% // Decreases project coverage by -0.02% :warning:

Coverage data is based on head (9d732ff) compared to base (c228349).
Patch coverage: 0.00% of modified lines in pull request are covered.

:exclamation: Current head 9d732ff differs from pull request most recent head 22e3e2e. Consider uploading reports for the commit 22e3e2e to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #551      +/-   ##
==========================================
- Coverage   62.32%   62.30%   -0.02%
==========================================
  Files          94       94
  Lines        7803     7805       +2
==========================================
  Hits         4863     4863
- Misses       2157     2158       +1
- Partials      783      784       +1

Impacted Files
Coverage Δ

api/application.go
71.78% <0.00%> (-0.26%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


improvement(filteraudiorender): update nb_samples in renderFrame

the nb_samples would not correct before decode, update it with frame info
Signed-off-by: pingkai<EMAIL_ADDRESS>

Codecov Report

Merging #231 into develop will decrease coverage by 4.31%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop     #231      +/-   ##
===========================================
- Coverage    69.71%   65.39%   -4.32%
===========================================
  Files          203      203
  Lines        10984    10986       +2
===========================================
- Hits          7657     7184     -473
- Misses        3327     3802     +475

Impacted Files
Coverage Δ

framework/render/audio/filterAudioRender.cpp
87.26% <100.00%> (+0.80%)
:arrow_up:

framework/tests/dataSource/ipList.h
0.00% <0.00%> (-100.00%)
:arrow_down:

framework/tests/demuxer/demuxerUnitTest.cpp
0.00% <0.00%> (-100.00%)
:arrow_down:

mediaPlayer/SuperMediaPlayerDataSourceListener.h
0.00% <0.00%> (-100.00%)
:arrow_down:

framework/tests/decoder/decoderUnitTest.cpp
0.00% <0.00%> (-93.62%)
:arrow_down:

framework/tests/dataSource/dataSourceUnitTest.cpp
0.00% <0.00%> (-93.39%)
:arrow_down:

framework/tests/demuxer/demuxerUtils.cpp
0.00% <0.00%> (-76.00%)
:arrow_down:

framework/data_source/ffmpeg_data_source.cpp
7.50% <0.00%> (-57.50%)
:arrow_down:

framework/demuxer/AVBSF.cpp
25.27% <0.00%> (-42.86%)
:arrow_down:

framework/data_source/curl/CURLShareInstance.cpp
69.44% <0.00%> (-27.78%)
:arrow_down:

... and 18 more

Continue to review full report at Codecov.

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


DTO Application Interface

DTO Application Interface
DTO Functions
The interface has the following methods:
Decoding
Decoding and converting connection data into an application data type.

from_connection() class method - create an instance of the dto given a connection. This is intended for parsing raw bytes into the type of the "data" kwarg annotation.
to_data_type() - intended to return the data that is represented by the dto to inject into the handler.

Encoding
Encoding data types back into bytes for responses.

from_data() class method - create an instance of the dto given the return value of the handler function.
to_encodable_type() - receives the request and returns anything that starlite can convert to bytes, or bytes.

On Registration

on_registration() class method - this is called by the route handler when it is registered on an application. It receives the ParsedTyped of the annotation it is being asked to manage, and the route handler.

App Layers Interface
DTOs can be defined through all layers of the application structure, closest definition to the handler wins.
Each layer has the following parameters:

dto: type[AbstractDTOInterface] | None | Empty - the DTO used to decode request data to be injected for the "data" kwarg. If return_dto not specified, this is also used as return_dto.
return_dto: type[AbstractDTOInterface] | None | Empty - the DTO used to encode handler response data, if not resolved for the handler, the resolved dto type is used.

If a handler resolves no dto or return_dto type for a handler there is no change to current behavior.
For either parameter, to disable a DTO that has been declared higher up the branch, set it to None on the node below which you don't want it to apply.

Going to start splitting out the work from the other dto branch by function.

So how hard to we want to be with type checking the outputs of the DTO from the application side? Anywhere between blind trust and stringently instance check every value.
How about this? The dto gets the annotation given to it in the on registration hook. It can raise an "unsupported" type exception if it doesn't support the type - and the expectation is that DTO types do validate this at this point. The user has the option to revert to default serialisation behaviour, or raise if the DTO cannot handle the type.
What do you guys think about having a sample rate for runtime type checking? So you could configure a runtime type neck every 1000/10000 or whatever requests?

It can raise an "unsupported" type exception if it doesn't support the type - and the expectation is that DTO types do validate this at this point. The user has the option to revert to default serialisation behaviour, or raise if the DTO cannot handle the type.

That sounds like a very good approach. I'm all for that.

So you could configure a runtime type neck every 1000/10000 or whatever requests?

I'm all for a good type necking, but I'm not so sure if we should do this. Sounds like a lot of overhead. Also, couldn't users simply employ beartype for this?

Maybe (in the somewhat distant future) we could somehow bridge this gap by employing some kind of static analysis - perhaps a mypy plugin or a standalone tool - that would help find those issues we can't easily detect at run-time.

Maybe (in the somewhat distant future) we could somehow bridge this gap by employing some kind of static analysis - perhaps a mypy plugin or a standalone tool - that would help find those issues we can't easily detect at run-time.

OK cheers, I'll leave it out. Not familiar with beartype - looks interesting!

It can raise an "unsupported" type exception if it doesn't support the type - and the expectation is that DTO types do validate this at this point. The user has the option to revert to default serialisation behaviour, or raise if the DTO cannot handle the type.

That sounds like a very good approach. I'm all for that.

Sweet, to get this through, I'll provide the UnsupportedType exception, and I won't add any handling, so it will be effectively an ImproperlyConfiguredException. The fall-back stuff I'll circle back on.

What do you guys think about having a sample rate for runtime type checking? So you could configure a runtime type neck every 1000/10000 or whatever requests?

This sounds unpredictable to me. Also, to me we simply guarantee the static type checks, but dynamic type checking at runtime (except validation of our own constructors) is left in user land.

So how hard to we want to be with type checking the outputs of the DTO from the application side? Anywhere between blind trust and stringently instance check every value.

I agree we should expect users to implement the same validation we do.

Yes, I will ensure docs are in order.


zipkin-web end time set

I find i can not select end time (zipkin version is 1.17.2)
url send end time is not my select time ，but the OS current time

url send end time is not my select time ，but the OS current time

maybe related to #783

We also encounter this in 1.25.1.
Another problem, when I select span name, and send the request, the page returns, with span name reset to all, which is unexpected. I expect the span name remains to be what I select.

thanks for reporting! sounds like a valid problem. personally, I'm offline
for a week or so. If anyone else can help with this, please do!

Any update? another problem, why the graph initially collapsed ?  It makes me click the expand all all the time.

@liyichao If you'd like to have a stab at resolving your issue, this is open source: we'd welcome the hand.

@liyichao wrt "why the graph initially collapsed" the collapsed-ness has to do with the serviceName query. For example, if the serviceName parameter corresponds to the root span, it will show up collapsed. If it doesn't it will expand to the child that contains it. Feel free to spin off another issue on this if you feel that behavior isn't ideal cc @yurishkuro

wrt your original concern (about end time resetting) I see that this is certainly the case.
For example, if you start from scratch, ex. where there's no query params in the URL, you can select any time, and the page will return with the correct endTs query parameter.
If you already have an endTs query parameter, changing the endtime date or time fields has no effect.
The work around is to clear the URL when you want to change. I agree this is a bug.

@adriancole i checked even with no query params in the URL and i select a previous date from the dropdown, the timestamp added in the query is still the current one (ignoring the selected endTs).


Upgrade Spring Boot to 2.4.10

@gytis Do you agree to bump the version of the SB ?

@cmoulliard , @gytis: I will bump this PR to the newest version 2.4.10

Could we keep an intermediary release with Spring Boot 2.4.9 before bumping to 2.4.10?

Could we keep an intermediary release with Spring Boot 2.4.9 before bumping to 2.4.10?

Fine with me, if someone can update and release, since @gytis seems to be absent at the moment.


chore: Release v1.0

Release script from: https://github.com/cap-js/change-tracking/blob/main/.github/workflows/release.yml

CI added via #60 ; merging this PR; then running dry run; if it works, enable the release-job in additional PR; then release


linux/node: reallocate nodeID upon conflict

NodeIDs and IPsec state suffer from a lack of reconciliation. If the agent misses a node deletion event, stale state is never cleaned up. This is somewhat known (#29822, #26298), but was generally considered not of huge consequence. Stale XFRM states/policies can accumulate, but will not match traffic - the effect is mostly slowing down processing in agent and kernel. nodeIDs can eventually run out if too many node deletions are missed, but the rate at which these are missed is expected to be low.
Unfortunately, there are large clusters with high node churn in which rare events become common, and hence the following sequence of events is probable enough to actually observe:

a node is deleted while the agent is down (e.g. due to being upgraded)
a new node joins the cluster and is allocated IPs which overlap with previously used IPs.

If this occurs, the agent can have a partioned view of what nodeID this node should have - in the BPF map, the k8s internal IP will map to a different nodeID than the cilium internal ip. This breaks IPsec traffic towards this node, as BPF applies a mark based on the BPF map nodeID of the tunnnel endpoint, but the xfrm states expect to match the mark based on the cilium internal IP. The result is traffic which doesn't match any xfrm state/policy, falling back to the catch all block policy.
To work around this, we enforce that all IPs of a node get the same nodeID - even if an IP was already pointing to an existing nodeID. Since this node update is more current than whatever state we had held, it seems more correct to ensure all IPs point to the same nodeID than avoiding a BPF map write. We do so by forcing the allocation of a new nodeID.
It is possible that unmapping the IPs but not deallocating the nodeID can leak the nodeID. Deallocating unconditionally would be wrong, as the stale mapping might point to a nodeID which represents a different, alive node.
The cilium agent will now recover from stale nodeID mappings which could occur in clusters with high node churn, possibly manifesting itself in dropped IPsec traffic.

cc @mhofstetter as a person with mutual auth knowledge - can you gauge the impact of this on that subsystem? Specifically - if we detect a stale nodeID mapping, and reallocate, does mutual auth break in fun and exiting ways?

/test

CI triage:

ci-integration: filed https://github.com/cilium/cilium/issues/33673
ingress: seems to have hit https://github.com/cilium/cilium/issues/25040
ipsec e2e: https://github.com/cilium/cilium/issues/26351
ipsec upgrade failed to upload artifacts

cc @mhofstetter as a person with mutual auth knowledge - can you gauge the impact of this on that subsystem? Specifically - if we detect a stale nodeID mapping, and reallocate, does mutual auth break in fun and exiting ways?

If datapath is triggering a new auth request based on the new node id of a remote-node we should be fine - as this would only lead to a new auth request - and corresponding auth handshake.
Apart from this, one might see some errors due to failures during re-authentication of existing auth entries in the auth map (e.g. on certificate rotation). This is because the node ids of remote nodes are stored in the auth map as well.

I think this matches the backport criteria for v1.14 and v1.15 given that it can cause connectivity to break between pairs of nodes and it is hard to recover from. IMO that qualifies as a "major bugfix".


The scale was not being reset when resetting tiles.

This could cause some weird texture glitches.

Example:
You can see that the left box is flipped: http://prntscr.com/aq6w11
Now once it goes out the camera view and it gets reused: http://prntscr.com/aq6wdi
It gets reused for the chair as seen here: http://prntscr.com/aq6wx9
The image flips and moves one tile to the right, since the scale is still flipped.
You can see it in action here: http://jimvliet.github.io/HTML5-Game/

So I just noticed this was already fixed in this pull request. https://github.com/englercj/phaser-tiled/pull/59 So now it's double fixed. So I recommend reverting my change and keeping the old one.


[docs] update seatunnel.md

correct some wrongly written words and update document format
Proposed changes
Issue Number: close #xxx
Problem Summary:
Describe the overview of changes.
Checklist(Requried)

Does it affect the original behavior: (Yes/No/I Don't know)
Has unit tests been added: (Yes/No/No Need)
Has document been added or modified: (Yes/No/No Need)
Does it need to update dependencies: (Yes/No)
Are there any changes that cannot be rolled back: (Yes/No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

EN doc also need to correct.

EN doc also need to correct.

LGTM


: Cannot read properties of undefined (reading 'invalidate')

打包报错：npm run build
 Cannot read properties of undefined (reading 'invalidate')

vue cli 项目配置如下：

  configureWebpack: {
    devtool: "source-map",
    plugins: [
      ComponentsPlugin({
        resolvers: [VantResolver()],
      }),
    ],
  },

包版本：  "unplugin-vue-components": "^0.19.6"

compiler.watching.invalidate();
Cannot read properties of undefined (reading 'invalidate')

you can upgrade your version above v0.20.1

https://antfu.me/posts/why-reproductions-are-required-zh


MOTR-41 Create Routing/Navigation

Integrated react-router, history, and mock authentication. Unit tests for authentication reducer and integrated tests of user flow through the application created. README updated with notes on recent integration.
The styling of footer changed to remain at bottom of the page and most instances of <br /> tags are removed in place of proper CSS styles.

@akre96 Looks good to me.


how to run OpenDevin with Claude 2 or Claude 3?

how to setup OpenDevin with Claude 2 or Claude 3?

@code2graph we don't have model-specific instructions, but I'm modifying things here to make it easier to set up: https://github.com/OpenDevin/OpenDevin/pull/614

set LLM_MODEL to claude-2 or claude-3, then export ANTHROPIC_API_KEY = "your_key" and run.
OpenDevin uses LiteLLM, you basically have to follow the instruction there for each model
https://docs.litellm.ai/docs/providers/anthropic

Should be fixed. https://github.com/OpenDevin/OpenDevin/pull/614


Private packages

Is there any way to publish private packages, and doing it with Github Actions linked to private Github repositories?

No, JSR does not support private packages. We are planning to handle private package usecases by letting organizations self host JSR. This is however not yet available.

I found JSR to be attractive but not being able to self-host a private registry would be a blocker for us. Or a cheap to have private package could be considered. We currently use Artifactory for example.
Side note, not being able to set upstream registries would also be a blocker, some companies give us access to their codebase via access to their own NPM registries. Upstreams are great for providing other sources without the need to migrate and disturb the current workflow.

Also looking forward to try this as a private proxy-registry in place of verdaccio because of verdaccio's bad performance. Hosting of defined @scopes would be a requirement, along with being able to proxy all other requests to another registry.

We are also using Verdaccio for testing and enabling some pre-merge CI
runs. Being able to run a local version of JSR maybe even with Verdaccio
behind the scene would be great.
On Thu, 21 Mar 2024 at 17:26, silverwind @.***> wrote:

Also looking forward to try this as a private proxy-registry in place of
verdaccio https://github.com/verdaccio/verdaccio because of verdaccio's
bad performance. Hosting of defined @scopes would be a requirement, along
with being able to proxy all other requests to another registry.
—
Reply to this email directly, view it on GitHub
https://github.com/jsr-io/jsr/issues/203#issuecomment-2013125779, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AABARLMFZ5AMPVK3CS3ZSG3YZMJ53AVCNFSM6AAAAABEH7R632VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJTGEZDKNZXHE
.
You are receiving this because you commented.Message ID:
@.***>

--
www.soundstep.com

If JSR can somehow support git url as a dependency, that would solve private registry for a lot of folks. With SSH authentication to the git repository, it becomes dead simple to use.

If JSR can somehow support git url as a dependency, that would solve private registry for a lot of folks. With SSH authentication to the git repository, it becomes dead simple to use. However npm doesn't support installing packages from sub directory of the git repository. But yarn does!

Git dependencies are wrong on many levels imho:

Git repos or their content can easily be deleted which breaks dependants
SSH connectivity is often not available in security-restricted environments

The prime benefit of a registry is that the content can be seen as immutable and it can be traced back to the source via provenance. So I would recommend to not support volatile and insecure git dependencies at all.

Deno literally downloads from a URL / git repository.

Also the request you have is not relevant to JSR a registry at all

https://www.npmjs.com/package/jsr is a CLI (client) that interacts with a website called https://jsr.io/, it just happens to be embedded in a npm package.

We are planning to handle private package usecases by letting organizations self host JSR.

Nice, some ask for self hosting documentation and more simplicity #150

Is there any progress with this subject @lucacasonato? Thanks in advance.

Is there a feature that can be tracked for a self-hosted registry @lucacasonato ?

+1

@lucacasonato
do you have any update on this?
else i'd start looking into building my own and i'd much rather take the easy route

I'm willing to work on this but after taking a quick look through the code I have some questions about how auth would be handled. Will it stay github only or are there plans for other OAuth methods.
Overall it feels like there are a lot of developer experience questions that I have which depend on the roadmap the jsr team has in mind

I would love to see private repository support for JSR. I have a use case for some internal libraries which cannot be open sourced, and to use JSR as an opportunity to advocate for multiple runtimes, provenance, and... well, you know folks already know the reasons why what you've built is so compelling.

It would be nice to have this if not just to have a non-hacky workaround deno limtations:

https://github.com/denoland/deno/issues/18478
https://github.com/denoland/deno/issues/18474

You could solve these by instead having a self-hosted local jsr registry to pull packages from


ManagedMqttClient is probably leaking memory through CancellationTokenSource

Describe the bug
ManagedMqttClient is probably leaking memory.
According to docs - cancellation-in-managed-threads CancellationTokenSource used in class that implements IDisposable should be disposed.
E.g., ManagedMqttClient.cs do not disposes cts it holds.
Which project is your bug related to?
ManagedClient

Hi it gets disposes in the StopMaintainingConnection method. In the dispose method the client is stopped. So to me now memory leak. Do you have a memory leak?

Ah, missed that. Thanks for the clarification!
No, memory leaks so far :)


⚠ Bofrost.at has degraded performance

In 955f3f3, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2176 ms

Resolved: Bofrost.at performance has improved in 130f788 after 21 minutes.


Example request

Hi @zubricky, Thanks for this awesome library. It would be more helpful if you add some working example or GIF to show the result
Thanks in Advance

Hey @karthickvkumar, added some examples here: https://github.com/zubricky/react-native-android-keyboard-adjust/blob/master/Examples/KeyboardAdjustExample.android.js
Also added some screenshots showing adjust nothing vs adjust resize to the readme.
If you or anyone else wants to add some examples for other methods, feel free! Hopefully what's there now covers the basic use cases.


sumneko_lua is deprecated, use lua_ls instead.

Version confirmation

[X] Confirm

Following prerequisites

[X] Confirm

Neovim version
NVIM  v0.8.3
Operating system/version
Arch linux 6.1.11
Terminal name/version
kitty 0.27.1
$TERM environment variable
No response
Branch info
main (Default/Latest)
Fetch Preferences
SSH (use_ssh = true)
Affected language servers
sumneko
How to reproduce the issue
Just use nvim to open any files, and the warning will display.
Actual behavior
Each time I open some files, the warning message bounces first.

Expected behavior
Migrate to lua_ls.
Support info
:Lspinfo
 Language client log: /home/liu/.local/state/nvim/lsp.log
 Detected filetype:   lua

 2 client(s) attached to this buffer:

 Client: lua_ls (id: 1, bufnr: [1])
 	filetypes:       lua
 	autostart:       true
 	root directory:  /home/liu/.config/nvim
 	cmd:             lua-language-server

 Client: efm (id: 2, bufnr: [1])
 	filetypes:       markdown, javascript, typescriptreact, lua, vim, css, scss, sh, html, yaml, javascriptreact, c, cpp, python, vue, typescript
 	autostart:       true
 	root directory:  /home/liu/.config/nvim
 	cmd:             efm-langserver

 Configured servers list: lua_ls, html, bashls, clangd, efm, gopls, pyright

:Mason
  Installed
      bash-language-server
      black
      clangd
      efm
      gopls
      lua-language-server
      prettier
      pyright
      shellcheck
      shfmt
      stylua

Logs
[START][2023-02-12 15:24:41] LSP logging initiated
[ERROR][2023-02-12 15:24:41] .../vim/lsp/rpc.lua:733	"rpc"	"efm-langserver"	"stderr"	"2023/02/12 15:24:41 efm-langserver: no configuration file\n2023/02/12 15:24:41 efm-langserver: reading on stdin, writing on stdout\n"
[ERROR][2023-02-12 15:24:48] .../vim/lsp/rpc.lua:733	"rpc"	"efm-langserver"	"stderr"	"2023/02/12 15:24:48 jsonrpc2 handler: sending response 2: jsonrpc2: connection is closed\n2023/02/12 15:24:48 efm-langserver: connections closed\n"
[START][2023-02-12 15:29:45] LSP logging initiated
[ERROR][2023-02-12 15:29:45] .../vim/lsp/rpc.lua:733	"rpc"	"efm-langserver"	"stderr"	"2023/02/12 15:29:45 efm-langserver: no configuration file\n2023/02/12 15:29:45 efm-langserver: reading on stdin, writing on stdout\n"
[ERROR][2023-02-12 15:30:14] .../vim/lsp/rpc.lua:733	"rpc"	"efm-langserver"	"stderr"	"2023/02/12 15:30:14 jsonrpc2 handler: sending response 2: jsonrpc2: connection is closed\n2023/02/12 15:30:14 efm-langserver: connections closed\n"
[START][2023-02-12 15:32:44] LSP logging initiated
[ERROR][2023-02-12 15:32:44] .../vim/lsp/rpc.lua:733	"rpc"	"efm-langserver"	"stderr"	"2023/02/12 15:32:44 efm-langserver: no configuration file\n2023/02/12 15:32:44 efm-langserver: reading on stdin, writing on stdout\n"
[ERROR][2023-02-12 15:36:20] .../vim/lsp/rpc.lua:733	"rpc"	"efm-langserver"	"stderr"	"2023/02/12 15:36:20 jsonrpc2 handler: sending response 2: jsonrpc2: connection is closed\n2023/02/12 15:36:20 efm-langserver: connections closed\n"

Additional information
No response

Thanks for the report, will fix soon.

We're waiting for the following issue to be merged before pushing any changes:

[ ] https://github.com/williamboman/mason-lspconfig.nvim/pull/148

We're waiting for the following PR to be merged before pushing any changes:

[ ] https://github.com/williamboman/mason-lspconfig.nvim/pull/148

side note: other upstream plugins that had already change sumneko_lua to lua_ls
https://github.com/williamboman/mason.nvim/blob/main/lua/mason-registry/lua-language-server/init.lua
https://github.com/neovim/nvim-lspconfig/blob/master/lua/lspconfig/server_configurations/lua_ls.lua

cc @Jint-lzxy
I'm planning to include this change in the upcoming PR for efm->null-ls migration, since I'm changing a lot of related stuffs.

@CharlesChiuGit It's ok, but I will still push this change as those options will be invalid very soon.

@CharlesChiuGit It's ok, but I will still push this change as those options will be invalid very soon.

Sure, but it seems there's still some place not recognize lua_ls. I'm trying to track the source.


Document which Glyphs features are supported by fontmake

@davelab6 asked over e-mail:

Are the 'bracket' and 'brace' glyphs interpolation features compatible with the toolchain?
Are smart corners and smart components?

Since Dave might not the only person wondering, should we document in the README whether fontmake supports all Glyphs features? If not, what specifically is missing?

Right now fontmake does not generate GX variation fonts, so the answer is no and no.  But both are possible and planned.

Cool. How to make GX fonts as @twardoch did in
https://github.com/twardoch/test-fonts/tree/master/gx ?

You could try this https://github.com/behdad/fonttools/blob/master/Snippets/interpolate.py

Are the 'bracket' and 'brace' glyphs interpolation features compatible with the toolchain?

They currently are not. Well, sparse masters are supported by mutatorMath but not tested.  But both are planned.  Let's keep this open.


Fix/update terraform 2023

Merging this after applying merge conflicts against #16 and #20
This may not be release ready but these changes are necessary to get us to the next release.


[Hackadoc] Update operational-insights-security.md

[Hackadoc] Adding a link to the full article

Hi @leylakazemi, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

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

TTYL, AZPRBOT;

Please recode the link in markdown format - see the survival kit: Markdown Cheatsheet.


Translate Docs to Polish - work in progress

Hi!
I would like to start translation into polish and I have seen Your recommendation for a translator from Czech Republic saying that the best way is to create a new organization (vuejs-pl) and fork the main repo there, which I did. Is it ok that I did it?
There is another person already willing to help me with that, but I would like to invite more people for this team. Is there a chance the organization can be added on the translations list on README to confirm we are the part of the project so others can be sure and more willing to join us?

Hi @anushhka - sorry for the delay in getting back to you. What you did is perfect and we look forward to your translation! We usually like to wait a little while for progress before adding a note to the README, but you can feel free to link back to this issue for now, to confirm that you've been officially invited to translate. 🙂

Hi @anushhka - with pleasure, I will contribute to the community of Vue.js and make a translation for Polish users. Let me know how you're doing with the stuff so I can join the efforts.

Hi @chrisvfritz - it seems that nothing was done in this issue and there is no contact with @anushhka
Is there a chance to take control over vuejs-pl organization or should I set up a new one, like pl-vuejs. Is it ok for you?

I'd recommend giving @anushhka a little more time to respond to your comment, then trying to contact her via email/Twitter. If you still can't get in touch, you could technically contact GitHub to try to get control, but I think it would be easier to just create a new one and that'd be fine with me. 🙂

Is there some progress going on? Where is this "vuejs-pl" organization?
This one? : https://github.com/vuejs-pl/vuejs.org
No sync with main repository ;(

Hi @Triloworld. I had tried to contact @anushhka but with no response. Even GitHub stuff tried to do it. There is a group "Translation Gang" that you can contact.

Ok. Can you (@wbankowski) create new organization as you described?
And add me so we can work together. Or I can do that if you need?

Due to lack of contact possibilities with @anushhka we have set a new organization for Polish translation, i.e. pl-vuejs
We kindly inform about it @chrisvfritz and @sdras

Can you add me to it? You don't have any contact information on your profile

@Triloworld I sent an invitation for you already. My email<EMAIL_ADDRESS>and mobile +48 533 95 25 95

@wbankowski How do you progress? I would like to join and help in the creation of Polish translation

Hello all
We communicate on https://discord.gg/gggQsTD
Join us and help translate.
As we write, there was some change ongoing to the link: https://github.com/pl-vuejs
(we get acceptance from github staff to claim the right name: vuejs-pl so there is little delay on work to be started)
I'am working daily as frontend developer and getting better hands-on with original documentation.
Our goal is to bring not only "Polish" version but detailed so more people enjoy using it.
I will try hard to do everyday progress but project is big for only one person

Closing in favor of #2015. Feel free to post a link there.


Added Dockerfile for running main.py from docker

Hi, i have added a basic Dockerfile for running the cli from docker. it uses python:3.10-slim as base image

Thank you for your contribution and the effort you've put into this PR. While Docker is useful for managing complex dependencies, for the current phase of our project, we're focusing on managing dependencies through Python packages to maintain simplicity, and we expect that the people who are running Docker also have python3 installed and can make a virtual environment if they wish to do so.
We hope you understand our perspective -- your enthusiasm and initiative are genuinely appreciated!


Enabling custom extension in view layer

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes and the overall coverage did not decrease.
[ ] All unit tests pass on CircleCi.
[ ] I ran all tests locally and they pass.

-1 for exposing individual view layer classes to global names pace. They have been deliberately kept as internal to reduce maintenance and chances of breaking brekaward compatibility.
The layer is already thin and the developer can just copy paste the code in the cuts componem if required.
What's the exact issue you're facing to customize the component?
Also: pls avoid merging PRs without even a single review.

-1 for exposing individual view layer classes to global names pace. They have been deliberately kept as internal to reduce maintenance and chances of breaking backward compatibility. The layer is already thin and the developer can just copy paste the code in the custom component if required.

Customers have a use case to extend individual components, hence their exposure. While developers can resort to copying and pasting, any alterations in the existing view layer, such as fixing minor bugs, would necessitate the repetition of the copy-and-paste process after each upgrade. This is not a seamless developer experience.

Also: pls avoid merging PRs without even a single review.

Given the magnitude of this alteration, it's worth noting that the changes have already undergone offline review by @vdua .why a significant change like this would be merged without review.

What's the exact issue you're facing to customize the component?

Have you had a chance to review the list of changes to see if the customer's use case is included in the test collateral?

-1 for exposing individual view layer classes to global names pace.

@nit23uec Conversations held offline with @vdua and @sakshi-arora1 have led to the decision not to expose the namespace at this time. Instead, we will allow customers to copy and paste the code. In the event of any changes during upgrades, developers will need to manually copy and paste the new code.
@barshat7 Please remove the code which exposes the individual component view to global namespace.


RFC: Named arguments in explicit mode should not be able to make parameters become implicit

Summary
Modify argument processing in the app elaborator so that the anyNamedArgDependsOnCurrent feature is disabled in explicit mode.
Motivation
The app elaborator has a feature where every explicit parameter that is depended upon by a named argument becomes an implicit parameter. We will call this feature argument suppression via named arguments. A motivation for it is to make projection notation more convenient. When S is a structure with field S.f, then the elaborator makes use of the fact that the main parameter for the field is named self, elaborating the projection notation x.f as S.f (self := x).
For structures such as classes, the self parameter is not explicit, and in that case structure parameters might be explicit due to the fact that they cannot be inferred from other parameters or the result type. Without special support, elaboration can lead to counterintuitive behavior. For example, in the following code block the projection C.val has n as an explicit parameter. This means that a straightforward implementation of projection notation would require the user to write inst.val n (or inst.val _) even though n can be inferred immediately from inst. However, due to argument suppression via named arguments, users can simply write inst.val:
class C (n : Nat) (α : Type) where
  val : α

variable (n : Nat) (α : Type) [inst : C n α]

set_option pp.explicit true
#check (C.val n : α)  -- @C.val n α inst : α
#check inst.val       -- @C.val n α inst : α

Side note: Named arguments in general suppress all explicit parameters depending on them, not just in the structure projection case. It should also be noted that generalized field notation might or might not be affected by this feature, since "lval resolution" for generalized field notation tries to use positional arguments if possible, falling back to named arguments when it is not. This inconsistency is not the subject of this RFC.
The argument suppression via named arguments feature has a counterintuitive interaction with explicit mode ("@ mode"). The assumption of explicit mode is that each argument should be provided explicitly. Argument suppression via named arguments is however still enabled in explicit mode since the implementation of explicit mode is, essentially, that each parameter becomes explicit (with a special case for _ arguments to instance implicit parameters). Since they are explicit, argument suppression via named arguments applies.
For example, in the following the n parameter becomes implicit since the self parameter depends on it.
#check @C.val (self := inst) -- @C.val n α inst : α

We believe users would expect to need to write @C.val (self := inst) n in explicit mode.
Guide-level explanation
(Rough draft with key information) Sometimes we want to be able to pass values to implicit parameters in function applications. Named arguments can be used for arguments of all binder types, even implicit parameters. For example (... example ...)
Another way is to enter explicit mode with the @ prefix. In this mode, every parameter is treated as if it were an explicit parameter. (... example ...)
Named arguments can be paired with explicit mode, which can be a convenient way to ensure an argument is being given to the correct parameter amidst a sea of arguments. (... example ...) This can also be used with a trailing .. to automatically insert the correct number of _'s at the end of an application.
For normal applications, named arguments have a feature where each explicit argument that a named argument depends on will become implicit automatically. These arguments can be inferred from the type of the named argument, so they are not strictly needed, which saves needing to write _s for such arguments. For explicit mode this feature is disabled.
Migration: In Lean pre-v4.XX.0, explicit mode had this feature enabled. You may need to insert some number of positional _ or (_) arguments to adapt to the change. Using _ should usually work, but (_) may be necessary for instance implicit arguments that are non-canonical.
Reference-level explanation
(... explanation of elaboration of normal applications, including the argument suppression via named arguments feature ...)
In explicit mode, parameters are processed one at a time according to the following:

If the next parameter is instance implicit and the next positional argument is _, then the parameter is elaborated as an instance implicit argument and the _ is consumed.
Otherwise, the next parameter is elaborated as if it were explicit while disabling the argument suppression via named arguments feature.

Drawbacks
Users may be making use of this feature in explicit mode. Kevin Buzzard for example was using it to avoid needing to supply "obvious" _s. It should be said that Kevin was making use of this feature with guess-and-check, not intentionally.
Rationale

The argument suppression via named arguments feature is motivated by projection notation. There is no such thing as explicit mode for projection notation, so it makes sense that it should not be enabled in explicit mode.
This makes explicit mode more predictable. It keeps the invariant that each argument (be it positional or named) corresponds to one parameter. It is hard to predict which arguments are suppressed, especially ones that are originally implicit arguments as they do not generally appear in the syntax.
Users can specify the exact expression they want for every argument. Argument suppression via named arguments leads to terms that might not definitionally be in the correct form — there are some mathlib examples where this causes typeclass inference failure.
The pretty printer is not aware of argument suppression via named arguments. If explicit mode delaboration were to have a feature to use named arguments in certain circumstances, then it would need to be made aware of it. (This does need to be fixed for normal mode delaboration. This is out of scope of this RFC.)

Unresolved questions and future possibilities

Should the argument suppression via named arguments feature be generally enabled? Or should it instead be enabled only for projection notation?
Should it also be enabled for generalized field notation in all cases?

Community Feedback
This RFC comes from discussion on the Lean Zulip. There is a bug in the interaction between how _ is handled in explicit mode for instance implicit arguments and argument suppression via named arguments. The PR #5283 fixes it with the assumption that we want the feature to be enabled in explicit mode. However, there is support in the Zulip thread to disable it in explicit mode.
Impact
Add :+1: to issues you consider important. If others benefit from the changes in this proposal being added, please ask them to add :+1: to it.

Superseded by #5397.


plugin: cross compiling fails

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
(1.8beta1)
go version devel +41908a5 Thu Dec 1 02:54:21 2016 +0000 darwin/amd64
What operating system and processor architecture are you using (go env)?
Darwin:
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/urso/.gvm/pkgsets/go1.8beta1/global"
GORACE=""
GOROOT="/Users/urso/.gvm/gos/go1.8beta1"
GOTOOLDIR="/Users/urso/.gvm/gos/go1.8beta1/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/2s/38f_b6sj0mn6_14km12vyq0r0000gn/T/go-build255645567=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"
PKG_CONFIG="pkg-config"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"

Linux:
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/urso/.gvm/pkgsets/go1.8beta1/global"
GORACE=""
GOROOT="/home/urso/.gvm/gos/go1.8beta1"
GOTOOLDIR="/home/urso/.gvm/gos/go1.8beta1/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build240993252=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
PKG_CONFIG="pkg-config"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"

What did you do?
Try to cross compile the plugin by setting GOOS=linux (darwin)
package main

import "fmt"

func F() { fmt.Println("Hello World!") }

func main() {}

What did you expect to see?
plugin being build
What did you see instead?
Darwin:
$ GOOS=linux go build -buildmode=plugin plugin.go
# command-line-arguments
warning: unable to find runtime/cgo.a
/Users/urso/.gvm/gos/go1.8beta1/pkg/tool/darwin_amd64/link: running clang failed: exit status 1
ld: unknown option: -z
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Linux:
$ GOOS=darwin go build -buildmode=plugin plugin.go
# command-line-arguments
warning: unable to find runtime/cgo.a
/home/urso/.gvm/gos/go1.8beta1/pkg/tool/linux_amd64/link: running gcc failed: exit status 1
/usr/bin/ld: -f may not be used without -shared
collect2: error: ld returned 1 exit status

Cross compiling plugins needs to use external linking, and therefore
you need to have cross compiling toolchain for the target platform
installed.
i.e. for the first case, you need linux toolchain installed on Darwin
and for the 2nd case, you need darwin toolchain install on Linux.

Should the go tool emit a more helpful error message after the existing failure messages?
Or is there missing documentation?
/cc @ianlancetaylor @crawshaw

Related issues:
#17620: cmd/go: docs need section on cross-compiling
#16395: cmd/go: provide better error message when cross-compiling toolchain
is required
maybe we can merge this one into #16395?

Better error handling is covered by #16395, any solution to that will work here.
There are two potential feature requests here, the first is internal linking of plugins which don't use cgo when GOOS=linux, the second is the same for GOOS=darwin.
Let's turn this issue into a feature request for GOOS=linux, -buildmode=plugin internal linking. It's not a priority for me, but it's an entirely reasonable feature request.
@urso if you want, you can file a separate bug for GOOS=darwin, -buildmode=plugin internal linking.


chore: clean up left over comments from the migration to jiff

These comments were disabled original upstream lines of code used for reference during the migration (or so I assume).

Looks good to me.
Also worth pointing out that I did a very basic port and there's probably opportunity to e.g. make these tests nicer by leaning into jiff's API.

Sounds good!


First implementation of recording data message being saved to filename + lots of dependency updates

This is an updated version of #37
This is the first implementation of the recording data being sent as a metadata struct, so it could be applied to the output filename of the recording.
I have also updated a lot of go and javascript (yarn/npm) dependencies.
I made Dockerfile to use node16 - since it's the latest LTS supported version aswell as some other improvements.
Each commits has quite well described commit message
With this commit I'm also updating develop branch to the current code state in master, so there will be no issues later on when merging this.
There are no changes in the code I've made since #37 I just resolved the conflicts caused by adding another commit to the original develop branch and recreated the PR

This PR is pretty dirty, I will clean it up a bit and send another


[DX] Shorten the way to try out Nuxt

Hey!
I noticed something in Nuxt docs about trying it out / quickstart / getting started. It is relatevely a long way for the user that just types nuxt.com and opens a website to actually go through the docs and see the actual nuxi command to try it out.

Access nuxt.com website
Click Get Started
Read whole page about Introduction
Navigate manually to Installation
Scroll to https://nuxt.com/docs/getting-started/installation#new-project
Actually type the nuxi command to generate a new project

From my DX experience this path is a bit too long and hard to follow. It could be easily fixed by following a pattern we leverage in major modules where a command to install the module is actually on the homepage:

My proposition:
I would recommend to have a simple bash terminal in the Nuxt.com website just below the H1 and the diamond, with a simple nuxi new command that would allow users first seeing the nuxt.com page to easily generate a new project without searching for the actual command further in the docs.
This should decrease the number of steps and the time new users need to spend in order to try out Nuxt which should eventually help improving DX :)
Let me know what you think about it

Also, if you agree, I could work on adding this to the docs :)

Agreed, good idea!

This is even better idea @harlan-zw !
If the nuxt.com is not OS yet, they you are right, I cannot add it. So I am leaving this up to you  and @Atinux to work with :)

Made a small update to start that the Get started button now goes to the installation page.

@Atinux What about including the terminal on the homepage as Harlan suggested? I think it can drastically help users to faster try Nuxt out 🙂

I know I tried but right now I am not happy about the result (also have a small bug):
https://nuxt.com/?preview=422205636c782eac46bd5691e584662bc48064027b82e252fc97c493756e03fb

It’s live ❤


[SPARK-9843] allow pluggable optimizers

This is to allow adding optimization passes that might be valid for specific application.

Can one of the admins verify this patch?


Hover and active color for monospaced text in sidenav

When you hover over something monospaced in the sidenav (e.g., a SQL statement), the hover color is blue. Is that right?

Also, when you're on such a page, the item in the sidenav isn't purple to indicate it's active:

Hover/ selected monospace in sidenav should be purple

Hover/ selected monospace in sidenav should be purple


chore(lib): release<EMAIL_ADDRESS>

What?
This PR updates the lib version for release.
The changes included in this release preparation are:

adding translatable to the message payload

Blocked by https://github.com/storyblok/storyfront/pull/5221


Extensions: Download counter font seems serif

Refs: https://github.com/Microsoft/vscode/issues/5767

Electron update 👎


More flexible way to trigger completion

I haven't been able to find a more flexible way to trigger the completer. I currently complete eg. sqrt to √, but would like it to happen automatically as you finish typing sqrt. You can set keymaps, but I need to attempt a completion every time a letter is written. This does not seem to be possible?

Nop and currently input Validator does not support validate_while_typing and can fix input:

For auto-correction like a missing closing quote or to reject invalid char while typing, the input will be mutable (TODO).

Ah yeah, I see.


fix protected column check in update analyzer

for assignments that involve two references or an unresolved
function on the right side.

ack


Sync test with main

:tada: This PR is included in version 1.3.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Free trial] HOLD on #43668 & #43672 - Restrict actions throughout the App of "past due" billing owner

This covers this section of the design doc:

Restrict actions throughout the App of "past due" billing owner

cc @fabioh8010 @pac-guerreiro as you'll be picking this up

Hi, I'm Fábio - expert agency contributor - and I would like to work on this issue.

@MitchExpensify right now we have @rojiphil and @hoangzinh - is one of them the Contributor, or are they both C+ and we can assign @fabioh8010?

Me and @hoangzinh are both C+ assigned to this project. But one of us has to take this up.
Callstack is implementing this project as mentioned here. So we can assign @fabioh8010

@fabioh8010 Don't we have to wait until #43672 is done to work on this? Or are we taking this up for implementation now?

Actually this one would be HOLD on https://github.com/Expensify/App/issues/43668 and https://github.com/Expensify/App/issues/43673, since the first one is merged and Restricted Action is close to be merged I will start my work on top of it, so I think this GH issue title was wrong.

Actually this one would be HOLD on https://github.com/Expensify/App/issues/43668 and https://github.com/Expensify/App/issues/43673, since the first one is merged and https://github.com/Expensify/App/pull/43855 I will start my work on top of it

Cool. That make sense.
@MitchExpensify I can take this up as C+ here.

Updating the title to reflect the hold on https://github.com/Expensify/App/issues/43673

The PR for https://github.com/Expensify/App/issues/43673 has been deployed, removed the hold.

@twisterdotcom I think the work in this issue deserves an increase in compensation:
Reasonings:

The PR took more time than the usual one or two rounds of testing as the scope involved too many tests (as described here)
Though not directly related to this issue, we addressed a related navigation issue on navigating back/away from the restricted actions view as mentioned here
Identified and supported an additional case here which was not identified yet in the design document

$750 is reasonable here. What do you think?

I'm happy with that, sure.

Payment Summary:

@fabioh8010 does not require payment (Contractor)

Payment Summary:

@rojiphil paid $750 here (C+)
@fabioh8010 does not require payment (Contractor)


OpenAL currently causing Windows builds to fail.

Title.
Relevant vcpkg issue links:
https://github.com/microsoft/vcpkg/issues/10825
https://github.com/microsoft/vcpkg/issues/9628
We can't do anything about this directly. We'll need to figure out some kind of hack. Marking as wontfix until resolved in Vcpkg itself.

Hey @RubyNova, based on https://github.com/microsoft/vcpkg/issues/12935 I think this can be closed.
It appears that the issue stems from CMake not choosing proper versioning of the Windows SDK if your OS does not match it, which:

is no longer an issue if you use Win 10 + latest SDK that matches your installed version, and
We're moving off of vcpkg in the near future anyways 😄


tenant services don't Deploy on minishift 1.4.1 / openshift 3.6.0

not sure if there's something wrong with the YAML or if its something we need to do to https://github.com/fabric8-services/fabric8-tenant to force a Deployment to happen.
in the console it just shows that the 2 deployments for jenkins and the content-repo failed; no Events - just failed. Clicking Deploy on each DC worked fine though

seems fine again now


[Usage] Installation on Windows - async_io dependency

Describe the issue
Issue: When installing requirements on windows, installation fails due to not being able to pre-compile async_io
Command:
pip install -e .

Log:
Obtaining file:///D:/AI/LLaVA
  Installing build dependencies ... done
  Checking if build backend supports build_editable ... done
  Getting requirements to build editable ... done
  Installing backend dependencies ... done
  Preparing editable metadata (pyproject.toml) ... done
Collecting einops (from llava==1.1.0)
  Obtaining dependency information for einops from https://files.pythonhosted.org/packages/29/0b/2d1c0ebfd092e25935b86509a9a817159212d82aa43d7fb07eca4eeff2c2/einops-0.7.0-py3-none-any.whl.metadata
  Using cached einops-0.7.0-py3-none-any.whl.metadata (13 kB)
Collecting fastapi (from llava==1.1.0)
  Obtaining dependency information for fastapi from https://files.pythonhosted.org/packages/4d/d2/3ad038a2365fefbac19d9a046cab7ce45f4c7bfa81d877cbece9707de9ce/fastapi-0.103.2-py3-none-any.whl.metadata
  Using cached fastapi-0.103.2-py3-none-any.whl.metadata (24 kB)
Collecting gradio==3.35.2 (from llava==1.1.0)
  Obtaining dependency information for gradio==3.35.2 from https://files.pythonhosted.org/packages/50/70/ed0ba0fb5c3b1cb2e481717ad190056a4c9a0ef2f296b871e10375b2ab83/gradio-3.35.2-py3-none-any.whl.metadata
  Using cached gradio-3.35.2-py3-none-any.whl.metadata (15 kB)
Collecting markdown2[all] (from llava==1.1.0)
  Obtaining dependency information for markdown2[all] from https://files.pythonhosted.org/packages/f1/98/61276a753f078dd2f3171c9a69fd3f451d220e806b2b1cdca41b8e368b0f/markdown2-2.4.10-py2.py3-none-any.whl.metadata
  Using cached markdown2-2.4.10-py2.py3-none-any.whl.metadata (2.0 kB)
Requirement already satisfied: numpy in d:\anaconda3\envs\llava\lib\site-packages (from llava==1.1.0) (1.26.0)
Requirement already satisfied: requests in d:\anaconda3\envs\llava\lib\site-packages (from llava==1.1.0) (2.31.0)
Collecting sentencepiece (from llava==1.1.0)
  Using cached sentencepiece-0.1.99-cp310-cp310-win_amd64.whl (977 kB)
Collecting tokenizers>=0.12.1 (from llava==1.1.0)
  Obtaining dependency information for tokenizers>=0.12.1 from https://files.pythonhosted.org/packages/92/02/15556b80450301d2ef014bc598df4352bfb39631c5fcff758d8e0ac9f065/tokenizers-0.14.1-cp310-none-win_amd64.whl.metadata
  Using cached tokenizers-0.14.1-cp310-none-win_amd64.whl.metadata (6.8 kB)
Collecting torch==2.0.1 (from llava==1.1.0)
  Using cached torch-2.0.1-cp310-cp310-win_amd64.whl (172.3 MB)
Collecting torchvision==0.15.2 (from llava==1.1.0)
  Using cached torchvision-0.15.2-cp310-cp310-win_amd64.whl (1.2 MB)
Collecting uvicorn (from llava==1.1.0)
  Obtaining dependency information for uvicorn from https://files.pythonhosted.org/packages/79/96/b0882a1c3f7ef3dd86879e041212ae5b62b4bd352320889231cc735a8e8f/uvicorn-0.23.2-py3-none-any.whl.metadata
  Using cached uvicorn-0.23.2-py3-none-any.whl.metadata (6.2 kB)
Collecting wandb (from llava==1.1.0)
  Obtaining dependency information for wandb from https://files.pythonhosted.org/packages/1c/5e/0362fa88679852c7fd3ac85ee5bd949426c4a51a61379010d4089be6d7ac/wandb-0.15.12-py3-none-any.whl.metadata
  Using cached wandb-0.15.12-py3-none-any.whl.metadata (9.8 kB)
Collecting shortuuid (from llava==1.1.0)
  Using cached shortuuid-1.0.11-py3-none-any.whl (10 kB)
Collecting httpx==0.24.0 (from llava==1.1.0)
  Using cached httpx-0.24.0-py3-none-any.whl (75 kB)
Collecting deepspeed==0.9.5 (from llava==1.1.0)
  Using cached deepspeed-0.9.5.tar.gz (809 kB)
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [15 lines of output]
      test.c
      LINK : fatal error LNK1181: cannot open input file 'aio.lib'
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "C:\Users\valkozin\AppData\Local\Temp\pip-install-s9q4kp7v\deepspeed_1f2978aea66844a2af764a83fd024764\setup.py", line 163, in <module>
          abort(f"Unable to pre-compile {op_name}")
        File "C:\Users\valkozin\AppData\Local\Temp\pip-install-s9q4kp7v\deepspeed_1f2978aea66844a2af764a83fd024764\setup.py", line 51, in abort
          assert False, msg
      AssertionError: Unable to pre-compile async_io
      DS_BUILD_OPS=1
       [WARNING]  async_io requires the dev libaio .so object and headers but these were not found.
       [WARNING]  If libaio is already installed (perhaps from source), try setting the CFLAGS and LDFLAGS environment variables to where it can be found.
       [WARNING]  One can disable async_io with DS_BUILD_AIO=0
       [ERROR]  Unable to pre-compile async_io
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

As async_io/libaio are dependent on Linux, these dependencies seem to make it impossible to run LLaVA natively on Windows.

Please check the latest doc for Windows. I tested on my Windows 11 PC and it seems to be working for 16-bit inference.
https://github.com/haotian-liu/LLaVA/blob/main/docs/Windows.md


Misc lint, perfs and docs

cf. #242

Codecov Report

Merging #251 into master will decrease coverage by 0.12%.
The diff coverage is 83.33%.

@@            Coverage Diff             @@
##           master     #251      +/-   ##
==========================================
- Coverage     100%   99.87%   -0.13%
==========================================
  Files          12       12
  Lines        1654     1660       +6
==========================================
+ Hits         1654     1658       +4
- Misses          0        2       +2

Impacted Files
Coverage Δ

ldap2pg/defaults.py
100% <ø> (ø)
:arrow_up:

ldap2pg/ldap.py
100% <ø> (ø)
:arrow_up:

ldap2pg/psql.py
100% <100%> (ø)
:arrow_up:

ldap2pg/inspector.py
100% <100%> (ø)
:arrow_up:

ldap2pg/manager.py
100% <100%> (ø)
:arrow_up:

ldap2pg/privilege.py
98.83% <66.66%> (-1.17%)
:arrow_down:

Continue to review full report at Codecov.

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


Request for .net core version

I am impressed by the performance and not having to request online service. but we couldnt work on production because we use .net core. is there any chance you port the library to .net core or .net standard?
Thankyou

I have no plans to work on this myself. If you need it you have to provide a PR.

I have a working branch for net472, mostly solved by using the Polyfill NuGet. Had to add a couple pragmas and turn IType into an abstract class, since default implementations in interfaces is not supported.
It's certainly significantly slower, but not necessarily prohibitively so (about 2x). Also, I haven't really dug into optimizing things. Just wanted to make it compile and get green tests.

Closed due to inactivity


Incremental reports with syslog output not picking up changes

I have a feeling that I am missing something  obvious, but I can't get incremental reports to work correctly in my configuration. New records are not picked up.
Installed pgBadger version 10.2 from the postgres apt repository:

apt show pgbadger
Package: pgbadger
Version: 10.2-1.pgdg16.04+1
Priority: optional
Section: database
Maintainer: Debian PostgreSQL Maintainers<EMAIL_ADDRESS>Installed-Size: 1,408 kB
Depends: libjson-xs-perl, libtext-csv-xs-perl, perl
Homepage: https://dalibo.github.io/pgbadger/
Download-Size: 307 kB
APT-Manual-Installed: yes
APT-Sources: http://apt.postgresql.org/pub/repos/apt xenial-pgdg/main amd64 Packages

Postgres is configured to log using syslog. Logrotate is configured to rotate daily. Command used is:
/usr/bin/pgbadger -v \
  --exclude-appname pg_dump --start-monday \
  --incremental --extra-files --format syslog \
  /var/log/postgresql.log.1 \
  --outdir "/root/pg_reports"

For the initial run it creates the report just fine:
DEBUG: Output 'html' reports will be written to out.html
DEBUG: Can not autodetected log format from /var/log/postgresql.log.1, using default
DEBUG: Starting progressbar writer process
DEBUG: Autodetected log format 'syslog' from /var/log/postgresql.log.1
DEBUG: pgBadger will use log format syslog to parse /var/log/postgresql.log.1.
DEBUG: Processing log file: /var/log/postgresql.log.1
DEBUG: Starting reading file /var/log/postgresql.log.1...
DEBUG: Start parsing postgresql log at offset 0 of file /var/log/postgresql.log.1 to 174882
DEBUG: Saving last parsed line into /tmp/tmp_LAST_PARSED (2019-02-11 06:25:06 0,174882): 0

DEBUG: the log statistics gathering took: 2 wallclock secs ( 0.01 usr  0.00 sys +  0.04 cusr  0.00 csys =  0.05 CPU)
LOG: Ok, generating HTML daily report into /root/pg_reports/2019/02/10/...
LOG: Ok, generating HTML daily report into /root/pg_reports/2019/02/11/...
LOG: Ok, generating HTML weekly report into /root/pg_reports/2019/week-06/...
LOG: Ok, generating HTML weekly report into /root/pg_reports/2019/week-07/...
LOG: Ok, generating global index to access incremental reports...
DEBUG: building reports took:  0 wallclock secs ( 0.12 usr +  0.01 sys =  0.13 CPU)
DEBUG: the total execution time took:  2 wallclock secs ( 0.13 usr  0.01 sys +  0.04 cusr  0.00 csys =  0.18 CPU)

cat /root/pg_reports/LAST_PARSED

2019-02-11 06:25:06	174882	Feb 11 06:25:06 redacted-hostname postgres[9603]: [488-1] db=,user=,app=,client= LOG:  checkpoint starting: time

When I manually rotate the log:
cp /var/log/postgresql.log /var/log/postgresql.log.1

and re-run
DEBUG: Output 'html' reports will be written to out.html
DEBUG: Removing obsolete binary file: /root/pg_reports/2019/02/10/2019-02-10-22923.bin
DEBUG: Can not autodetected log format from /var/log/postgresql.log.1, using default
DEBUG: this file has already been parsed: /var/log/postgresql.log.1, there no new lines in this file
DEBUG: the log statistics gathering took: 0 wallclock secs ( 0.00 usr +  0.00 sys =  0.00 CPU)
DEBUG: no new entries in your log(s) since last run.
LOG: Ok, generating global index to access incremental reports...
DEBUG: building reports took:  0 wallclock secs ( 0.00 usr +  0.00 sys =  0.00 CPU)
DEBUG: the total execution time took:  0 wallclock secs ( 0.00 usr +  0.00 sys =  0.00 CPU)

LAST_PARSED is not updated. Last actual log entry in this case is:
tail -n1 /var/log/postgresql.log.1

Feb 11 09:45:10 redacted-hostname postgres[9603]: [529-1] db=,user=,app=,client= LOG:  checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.203 s, sync=0.001 s, total=0.212 s; sync files=1, longest=0.001 s, average=0.001 s; distance=7 kB, estimate=3735 k

If I remove the old output directory and re-run, it creates a report including the last entries. If I use something like  /var/log/postgresql.log /var/log/postgresql.log.* for input, it's still also not picking up changes after initial run.

I am not able to reproduce the issue. Can you try with latest development code and let me know if the problem persist?
wget https://raw.githubusercontent.com/darold/pgbadger/master/pgbadger

As suggested, I've removed the repo version, cloned master and installed. Works as expected!
DEBUG: Output 'html' reports will be written to out.html
DEBUG: Autodetected log format 'syslog' from /var/log/postgresql.log.1
DEBUG: Starting progressbar writer process
DEBUG: Autodetected log format 'syslog' from /var/log/postgresql.log.1
DEBUG: pgBadger will use log format syslog to parse /var/log/postgresql.log.1.
DEBUG: Processing log file: /var/log/postgresql.log.1
DEBUG: This log might not be parsed: /var/log/postgresql.log.1, timestamp 2019-02-11 06:25:21 read at offset 0 is lower than saved timestamp: 2019-02-11 09:45:10
DEBUG: Starting reading file /var/log/postgresql.log.1...
DEBUG: Start parsing postgresql log at offset 70796 of file /var/log/postgresql.log.1 to 243846
DEBUG: Saving last parsed line into /tmp/tmp_LAST_PARSED (2019-02-11 13:47:16 4,243846): 2

DEBUG: the log statistics gathering took: 2 wallclock secs ( 0.00 usr  0.00 sys +  0.04 cusr  0.00 csys =  0.04 CPU)
LOG: Ok, generating HTML daily report into /root/pg_reports/2019/02/11/...
LOG: Ok, generating HTML weekly report into /root/pg_reports/2019/week-07/...
LOG: Ok, generating global index to access incremental reports...
DEBUG: building reports took:  6 wallclock secs ( 5.42 usr +  0.01 sys =  5.43 CPU)
DEBUG: the total execution time took:  8 wallclock secs ( 5.42 usr  0.01 sys +  0.04 cusr  0.00 csys =  5.47 CPU)

Thanks for the feedback, I will publish a new release asap.


third-party Appstore

我维护了一个 第三方 应用商店，主要都是一些渗透相关的工具，可以加入到第三方应用商店推荐么？
以下是链接：https://github.com/arch3rPro/Pentest-Docker

CasaOS Pentest-Docker AppStore
Pentest-Docker is a CasaOS third-party Appstore with Pentest-Tools apps.
Source link:
https://github.com/arch3rPro/Pentest-Docker/archive/refs/heads/master.zip

This probably should be added via PR in the third party repo


tsconfig.js ignore and module resolution problems in Visual Studio.NET 2017 RC4

TypeScript Version:  2.1 (the one which comes with the VS.NET 2017 RC4. Also 1.7 and 1.8 is installed)
TS files generate lots of errors with decorators and module resolution in VS.NET 2017 RC4. I'd appreciate if I can get any insight if this is a bug or something wrong with my setup.
Here's an example screenshot:

Example file is located in this location:
<root>\wwwroot\Application\Components\Task\Search\Search.ts
Here's my tsconfig.json in the root folder of the project:
{
  "compilerOptions": {
    "target": "es5",
    "module": "commonjs",
    "moduleResolution": "node",
    "sourceMap": true,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "lib": [ "es2015", "dom" ],
    "suppressImplicitAnyIndexErrors": true
  },
  "exclude": [
    "node_modules",
    "wwwroot/Application"
  ]
}

I have Typings globally installed.

The errors suggest that your tsconfig.json is not picked up for your file Search.ts. can you verify that:

tsconfig.json is added to your project, and that its content type is content
tsconfig.json is in a parent folder of Search.ts

If yes for both, can you share a sample project to look at?

@mhegazy : I can confirm both.
I don't know what happened but I'm not getting errors now so I'm closing this issue. Thank you for your help.


[Backend] fix model name

Fixed chat model name as "moxin-chat"
Fixed embedding model name as "moxin-embedding"

The frontend doesn't need to change because I've already replaced the model name in the request on the backend

Thanks. Would love to see this merged.
This is needed for agent apps that use the moxin API server. We cannot ask the agent to re-configure its model name whenever the moxin UI user switch to another model to chat.


nixos/postfix: add systemd hardening directives

Description of changes
Inspired (copied!) by Gentoo's postfix hardening:
https://github.com/gentoo/gentoo/blob/a9ccc48242da316f37b8e6ddf99bae660fadef48/mail-mta/postfix/files/postfix.service
This decreases the systemd-analyze exposure level from UNSAFE to MEDIUM:
$ systemd-analyze security --offline=true postfix-hardened.service | grep Overall
→ Overall exposure level for postfix-hardened.service: 6.2 MEDIUM 😐

$ systemd-analyze security --offline=true postfix-original.service | grep Overall
→ Overall exposure level for postfix-original.service: 9.6 UNSAFE 😨

A previous postfix hardening PR appears to have stalled: https://github.com/NixOS/nixpkgs/pull/93305/files

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

Why not use the postfix file in the official Gentoo repo: https://github.com/gentoo/gentoo/blob/17d3ba5e9c2b0d3b2acbf74db127d64b579edd93/mail-mta/postfix/files/postfix.service

I deployed it on my server and everything still seems to be working. :+1:

The gentoo unit file also specifies ReadWritePaths, don't we need them?

On NixOS postfix does not use these files - /etc/mail/aliases.db, /etc/mail/aliases.cdb and /etc/mail/aliases.lmdb.
@tomfitzhenry have you checked these parameters in work?
  ProtectHome = true;
  ProtectHostname = true;
  LockPersonality = true;
  PrivateMounts = true;

Was able to send the email out with the patch. Thank you!

And don't forget the receiving part! Works for me with dovecot over domain socket.

Result with systemd-analyze security postfix:
→ Overall exposure level for postfix.service: 6.1 MEDIUM 😐


fix: the misleading log message

Maintainers will complete the following section

[ ] Commit messages are descriptive enough (hints)
[ ] Code coverage from testing does not decrease and new code is covered (check the PR coverage on codecov)
[ ] Controllers diagrams are updated when PR changes controllers code  (if applicable)

Looks like we'll need to update the unit test here to get it passing.


How to perform a measurement in acqdp?

There are two classes (Measurement and PureMeas) in circuit.py. Since this simulator is based on tensor-network and density matrix, the effect of a measurement can be represented as a density-matrix update.  To my understanding, this is the method acqdp adopts.
In some cases, we are only interested in the state vector update, where a measurement collapses the state vector and returns a single bit representing the measurement result. How could we do this in acqdp?
Thanks!

Hello gtaifu,
We have added two methods measure and collapse in acqdp.circuit.Circuit.
The method measure of a circuit takes an argument specifying the index of the qubit to be measured, and returns a random measurement result and the corresponding conditional quantum state. Two optional arguments include remove_qubit, indicating whether the qubit being measured is to be removed from the system, and collapse, indicating whether the returned conditional state still preserves the tensor network structure.
The method collapse evaluates a quantum circuit as a tensor network, and replace the tensor network structure with the value of it. Doing this simplifies the quantum circuit and makes state vector update more efficient. collapse now only supports quantum circuits that are states, i.e. quantum operators with no input wires.
Please let us know if those functionalities meet your need.

@cupjinhuang thank you! I think it should work for us. I will integrate it into our open-source simulation platform (pyqcisim). If there is any question, I will return to you!


ESM Resolution failing

Error:
$ yarn build

><EMAIL_ADDRESS>build
> react-scripts build

Creating an optimized production build...
Failed to compile.

Module not found: Error: Can't resolve './builders/html_builders' in '/private/tmp/myapp/node_modules/safevalues/dist/mjs'
Did you mean 'html_builders.js'?
BREAKING CHANGE: The request './builders/html_builders' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.

Reproduction Steps:

npx create-react-app repro-app --template typescript
cd repro-app
yarn add safevalues
Modify src/App.tsx to be the following:

import React from 'react';
import logo from './logo.svg';
import './App.css';
import { sanitizeHtml } from 'safevalues';

function App() {
  const html = sanitizeHtml('
my post
');
  return (

          Edit src/App.tsx and save to reload.

          Learn React

  );
}

export default App;

yarn build

It works when I modify the imports to have the .js file extensions.

Would it be possible to provide a bundled version of this library, so that there are no issues with module resolution in some environments?

Thanks for reporting. I'll add the .js extensions to the path-based imports.

I've released safevalues 0.6.0 on NPM. It includes https://github.com/google/safevalues/commit/fa5bbf0fda5605d26ba1daf5c6a7f809f817c0af which adds the .js extension to all the path-based imports.


fixed no status bug

Description
Fixes #250
Type of change
Just put an x in the [] which are valid.

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

How Has This Been Tested?
Please describe the tests that you ran to verify your changes.

[x] ./gradlew assembleDebug assembleRelease
[x] ./gradlew checkstyle

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

@aayushinigam There are merge conflicts

@aayushinigam It's failing

I'll squash commits and update the PR

No need to squash. I'll squash & merge

Oh okay!


Back port changes for XWALK-3575 to Crosswalk 13

Back port changes for BUG=https://crosswalk-project.org/jira/browse/XWALK-3575

Please use a better title for the pull request and mention the original commits that are being cherry-picked in each commit message (git cherry-pick -x).

@rakuco Thanks for advices, changed.


Adds Animated.FlatList

Adds CreateComponent functor to FlatList so that it can be used with both FlatList and Animated.FlatList
Adds FlatList to AnimatedComponents module and to Animated module

FlatList has not yet been added to the Animated library in React-Native but I guess it will be added in the next release since this commit is already merged.
If you don't like having it in the AnimatedComponents module until it's released in React-Native I can remove it from there and only add the CreateComponent functor for FlatList

I think we’re good to merge. We don’t have tools to sync with JS lib releases so whatever we do is potentially wrong. For that reason I prefer to merge things early.

I agree, should we merge this then @wokalski ?


Change font of website to match logo

https://helpx.adobe.com/fonts/user-guide.html/fonts/using/add-fonts-website.ug.html

Which font?

Pragmatica and pragmatica slab serif

the header isn't picking it up... it's all going pragmatica. Will check with Sunny if this is worth more time.


Solaris support

On Solaris the type of ifaddrs.ifa_flags is uint64_t, so should change the type of Interface::flags to u64.

Thanks for the PR, published as v1.0.3.


Add libgmodule-2.0 to exclude list

This will fix an error when an AppImage was created with glib < 2.70 and executed with glib >= 2.70:
symbol lookup error: /lib/x86_64-linux-gnu/libgio-2.0.so.0: undefined symbol: g_module_open_full

Full analysis: https://github.com/project-slippi/Ishiiruka/issues/323
Also fixes https://github.com/knarfS/smuview/issues/40
@probonopd I guess updating this file will fix the download in the generate-excludelist.sh scripts of linuxdeploy and liunxdeployqt?

The interesting question is whether this will in turn cause other breakages.
In some cases, libraries are so closely related that either all or none of a certain set need to be bundled.
I would not be surprised if all of gio should be treated as such a set.

The interesting question is whether this will in turn cause other breakages.

Fingers crossed :D

In some cases, libraries are so closely related that either all or none of a certain set need to be bundled. I would not be surprised if all of gio should be treated as such a set.
My gut feeling is that we need to bundle all libraries in https://packages.debian.org/bullseye/amd64/libglib2.0-0/filelist or none.

Yes you are absolutely right. All libs that come with libglib2.0 should be handled the same, either remove all of them or bundle all into the AppImage.
That's exactly what's causing the issue right now: Some of the libglib2.0 libraries are excluded (libgio-2.0.so.0, libglib-2.0.so.0, libgobject-2.0.so.0) and others not (libgmodule-2.0.so.0and libgthread-2.0.so.0). This leads to problems, when the system glib2.0 >= 2.70 and AppImages' glib2.0 < 2.70 are mixed.
I'm not sure what the better solution would be. Maybe bundle all of the glib2.0 libraries?
But on the other hand, not sure what dangerous means in this context, but it somewhat suggests to exclude the libs:
https://github.com/AppImage/pkg2appimage/blob/dd87a9ee27908f5527d1b03c42d4a55c421ebd7e/excludelist#L161-L162

Addressed with https://github.com/AppImage/pkg2appimage/commit/1e3ecde6b92ef198405463415b8090a4435d0cb0

I'm the developer of an application that links to GStreamer and I want to target Debian Bullseye. To make the AppImage I'm using linuxdeploy and the GStreamer plugin, to bundle all the needed files. I'm building the AppImage on a Debian Bullseye container, because it's the lowest denominator I want to support, and I find that Ubuntu makes things harder with cross-compilation and has more bloat for my taste.
However, when I test the generated AppImage on a Debian Bullseye chroot, I get this error, due to the gobject library not being part of the base, non-GUI distro:
/tmp/.mount_PackSqYahSyB/AppRun.wrapped: error while loading shared libraries: libgobject-2.0.so.0: cannot open shared object file: No such file or directory

Searching the Internet for that error directed me to the exclude list mentioned in this issue and this issue itself, so that's why I think that it might be relevant to comment here.
For my use case, I find that the "so far, we have been considering glib as something that is provided by the distribution" statement is quite unsatisfactory, as I wouldn't call a base Debian Bullseye installation without GLib components a strange system at all (in fact, some users of my application are reporting that they use Debian Bullseye).
Is it feasible to consider bundling all the GLib components in AppImages that need them, not treating GLib as "distribution-provided", even if there are fairly sensible distribution configurations that do not include GLib? The current behavior basically means that users of my AppImage still need to make sure that the GLib package is installed, which partially defeats one of the objectives of AppImages: not having to install packages at all.

The current behavior basically means that users of my AppImage still need to make sure that the GLib package is installed, which partially defeats one of the objectives of AppImages: not having to install packages at all.

Well.
The objective of AppImage is that you can run applications on most mainstream desktop Linux distributions without having to manually install additional packages besides what they come with out of the box by default on their Live ISOs.
If you really want to make an AppImage that has no dependencies on any distribution-provided packages, why draw the line at GLib? One could argue that a system without glibc is a perfectly fine system as well, and just bundle all libraries. This is what e.g., go-appimage appimagetool -s deploy and https://github.com/AppImageCrafters/appimage-builder do. The result is that you can even run AppImages made on newer build systems on older user systems.

I get this error, due to the gobject library not being part of the base, non-GUI distro

Then you need to ship Xorg as well I guess... which is out of the scope for AppImage, even though technically you might even be able to put it into an AppImage as well.

I'm using GStreamer to process audio files in a CLI app, which does not not need a full-blown desktop environment at all. I understand that drawing the line on GLib is somewhat arbitrary, and that if the goal for AppImage is to target desktop environments, then it makes sense to assume it's there. I just wish I had found that out earlier. I'll look into the alternatives you've suggested. Thank you!

I understand. Yes, for your use case it may be sensible to draw the line there.


Add message for anon users that view Pending Approvals

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella: