Change JavaScript MIME type

A minor fix for successful testing.
text/javascript is a recommended standard (both by IETF and by MDN). application/javascript is obsolete.

This change will break this test as it's testing the return from the HTTP request.
If you want to change the MIME type of the actual request you'll have to update Hio, I believe

Yeah, you are right. At a glance, falcon still uses application/javascript for the JS MIME type in the simulation of HTTP request. However, surprisingly, on Ubuntu machine the test was failed on the stale MIME type while there was no problem on a Mac machine.

If you want, I'll close this PR. Of course, you can directly close it.

https://github.com/falconry/falcon/issues/2110

So we can close this issue here I assume?

Yes.

Hello @euj1n0ng & @pfeairheller!
While we are looking to enforce Falcon's standard media types for some common file types, you can absolutely override this in your application if you wish.
Just add the desired types to your application's app.resp_options, for instance,
app.resp_options.static_media_types['.js'] = 'text/javascript'

Update: you should now get @euj1n0ng's improvement automatically via Falcon 4.0.0+.


removes unused code related to root tablet location

These changes were motivated by this thread https://github.com/apache/accumulo/pull/4668#discussion_r1637202535

While working on this, happened to discover three thrift methods that nothing was calling.  Wonder if there are other thrift methods like this, but not sure how they could be found.


[feature]add workerId and starlet_port in showBackends

What type of PR is this：

[ ] bug
[x] feature
[ ] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

[FE PR Coverage check]
:disappointed: fail : 22 / 28 (78.57%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/server/GlobalStateMgr.java
1
2
50.00%

:large_blue_circle:
com/starrocks/common/proc/BackendsProcDir.java
11
15
73.33%

:large_blue_circle:
com/starrocks/catalog/StarOSAgent.java
7
8
87.50%

:large_blue_circle:
com/starrocks/common/Config.java
1
1
100.00%

:large_blue_circle:
com/starrocks/system/Backend.java
1
1
100.00%

:large_blue_circle:
com/starrocks/system/HeartbeatMgr.java
1
1
100.00%

[FE PR Coverage check]
:heart_eyes: pass : 26 / 28 (92.86%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/server/GlobalStateMgr.java
1
2
50.00%

:large_blue_circle:
com/starrocks/catalog/StarOSAgent.java
7
8
87.50%

:large_blue_circle:
com/starrocks/common/proc/BackendsProcDir.java
15
15
100.00%

:large_blue_circle:
com/starrocks/common/Config.java
1
1
100.00%

:large_blue_circle:
com/starrocks/system/Backend.java
1
1
100.00%

:large_blue_circle:
com/starrocks/system/HeartbeatMgr.java
1
1
100.00%


[Cherry-pick] Blueprints v4.31.0 (#731) and auto setup describe ALB name fix (#732)

Cherry-pick #731 #732
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

let me cut new release branch and we can pick this PR to that to keep the code and docs in sync

done, release-v1.7.0-aws-b1.0.1


Browser is shown instead of Operating System

On web platform, information about the browser is placed in the field intended for the operating system:
https://github.com/amplitude/Amplitude-JavaScript/blob/d6982f7d86ea240e85037eefb4c4c1bf50cd96b4/src/amplitude-client.js#L1143
Actual result:

Expected result:
Field OS should contain info about operating system, like Windows or Mac.

Related: https://github.com/amplitude/Amplitude-JavaScript/issues/220#issuecomment-777106995


fix typo

Merged via https://github.com/nikku/wuffle/commit/5ec83f59dc88a64dc9e87acce9fa4ae8774fe0ff.
Thank you for the contribution.


Impact Analysis - Follow-up investigation of Microsoft change to Sharepoint custom scripting

🐛 Summary
Microsoft is making updates to the custom scripting configuration options for Sharepoint and OneDrive. The purpose of this issue is to determine if we need to remove or revise policies MS.SHAREPOINT.4.1v1 and 4.2 based on the changes.
https://techcommunity.microsoft.com/t5/sharepoint/removing-custom-scripting-on-sharepoint-sites/m-p/4055563
Original issue #977 was closed and this issue is opened to further investigate once the change is made.
Microsoft's suggestion is to remove the policies once change has been made but will further investigate once update is available in the test tenants.
Implementation notes

[ ] Examine the Microsoft documentation which states that the scripting configuration is going to change.
[ ] Perform a hands-on analysis of the Sharepoint admin center for the two affected settings and document the impacts.
[ ] Document a recommendation on whether the baseline and ScubaGear need to change.
[ ] If changes are needed, create new issues.

Via hands-on testing, I verified that the MS.SHAREPOINT.4.1v1 (custom scripts for personal OneDrive sites) has been removed from the MS Sharepoint admin portal so @ahuynhMITRE we should remove it from the baseline. Create a new issue for that.
There are no code impacts because ScubaGear didn't have this field in the available cmdlets - it is currently not checked.

Via hands-on testing, I verified that Microsoft changed the way that MS.SHAREPOINT.4.2v1 (custom scripts for self-service (aka Sharepoint sites) is implemented in the admin portal. This impacts our baseline and I am currently still testing this for the next few days. My interim notes are saved below.

I changed the custom scripts for self-service sites setting in the Sharepoint classic settings admin page (per our baseline) but it had no effect on the configuration setting checked by ScubaGear. I am guessing that changing the respective value from that classic page is OBE so we might need to change the baseline instructions.
I was able to change the custom scripts for self-service setting in Powershell using the commands below and I verified that the setting was changed by running ScubaGear so it is still possible to modify this settings via API call.

To set it to a non-compliant value use $false. For compliant use $true
set-sposite -identity https://tedstoplevelsite.sharepoint.com/  -DenyAddAndCustomizePages:$false

Apparently there is a new place in the GUI to set the value for the custom scripts for self-service sites and that is on the Sharepoint Admin > Sites > Active Sites page. Open the top level site and click the Settings tab. There is a new option there named Custom scripts which changes the value of the setting and therefore impacts the ScubaGear policy check. I tested this.

When you change the configuration setting to a non-compliant value in the admin portal (i.e. to allow custom scripts), the portal warns you that the setting will automatically be reverted back to Blocked within 24 hours. I set a few of the sites (including the top level site) to Allowed and I will check back on Friday to see if they get reverted back.

I set the Custom Scripts setting to Allowed at the site level for the following three sites on 7/17. According to Microsoft they were supposed be automatically reverted back to Blocked within 24 hours. As of today 7/19 only one of the sites was automatically reverted back to Blocked so I will check again on Monday 7/22 to see if the other two sites change.

Sharepoint site name
Custom Scripts status 7/17
Custom Scripts status 7/19

Communication site
Allowed
Reverted back to Blocked

Digital Initiative Public Relations
Allowed
still Allowed

Mark 8 Project Team
Allowed
still Allowed

Update the status of #622 once we determine if we are keeping or removing Sharepoint policy 4.2. We are currently in back and forth discussions and hands-on testing with Microsoft.

After speaking with Ted to get updated on the status of this investigation following meeting with Microsoft, current suggestion by me is the following with Jellyfish not expecting to have any SCB changes due to the BOD:

Update ScbaGear report to remove check for 4.2 and have the setting be N/A
add notes in the details section of 4.2 report noting that the policy is expected to be decommissioned in the future.

sample language can be "The Custom Script setting in SharePoint is planned to be removed. The NoScriptSite setting will be configured to True for all existing sites except for specific site templates. If you change this setting for a classic team site, it will be overridden by the Custom Script setting in the admin center within 24 hours." this text was lifted from Microsoft's documentation on the change (links listed below).
https://learn.microsoft.com/en-us/sharepoint/allow-or-prevent-custom-script
https://mc.merill.net/message/MC714186
-Future issue to be added to remove the policy from the SCB and ScubaGear set for Kraken.

Tagging in @mitchelbaker-cisa and @tkol2022 on review on the recommend next steps prior to creating a new issues.

Thank you!

I am good with the action plan to change the Rego to produce an N/A for 4.2 as a short-term implementation.

I am good with updating the language in the baseline. I would not put too much detail because I find the message from the website confusing and can likely confuse users. Instead I recommend just putting something like "The configuration setting that this policy was based on has been deprecated in its original form and we expect to decommission it from the baseline in the near future."

analysis complete. Follow actions are captured in #1324 and #1325


Fix missing intellisense #2962

This fixes the missing intellisense regression https://github.com/Microsoft/visualfsharp/issues/2962 using the technique mentioned at the end of that discussion
https://github.com/Microsoft/visualfsharp/issues/2970 also seems fixed - perhaps not by this though

Thanks @dsyme!

@dsyme #2970 is not fixed:

@vasily-kirichenko Thanks, looking into it. It seemed ok when I checked last night

@dsyme It works OK on release VSIX, but never - on debug on.

@vasily-kirichenko Strange - Intellisense works for me in Project.fs.  Are you doing anything special, e.g. reloading the solution, or cleaning the directories, or ...?

Ah, I see, debug is the problem.  Will take a look


Bumped down styled-jsx version

Signed-off-by: Aditya Agarwal<EMAIL_ADDRESS>Description
The styled-jsx v5.0.0 deprecates styled-jsx/server as well as the flush API which we use in the project. The package.json files in ui as well as provider-ui folders use both "styled-jsx": "latest" and "styled-jsx": "*" which makes our project depend on the latest version of the package and hence vulnerable to the breaking API. I have changed the * and latest to ^4.0.1 which will use releases from 4.0.1 to <5.0.0
This PR fixes #5118
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Codecov Report

Merging #5122 (00f134c) into master (41c0b0a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #5122   +/-   ##
=======================================
  Coverage   32.04%   32.04%
=======================================
  Files          62       62
  Lines        5267     5267
=======================================
  Hits         1688     1688
  Misses       3154     3154
  Partials      425      425

Flag
Coverage Δ

gointegrationtests
10.74% <ø> (ø)

integrationtests
∅ <ø> (?)

unittests
24.01% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out 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 41c0b0a...00f134c. Read the comment docs.

@Nikhil-Ladha before moving forward with this could you please try to recreate this issue once, I'm not being able to reproduce it at all. Checked with both v4.x.x and v5.x

@Nikhil-Ladha before moving forward with this could you please try to recreate this issue once, I'm not being able to reproduce it at all. Checked with both v4.x.x and v5.x

As o

Yes, the issue is reproducible by manually changing the package version to 5.0.0.
Now there are 2 things:

We should never use latest in the versioning of the package, it is always prone to such risks.
We can update to ^5.0.0 and use the newer function provided by styled-jsx. Though, this can be tracked in a separate issue/PR.

We are good to move ahead with this PR for now. Thanks @adi611 for finding this out :)


As a user I need to to see important links and info on the Resources page in the storefront

Should have links to GitHub repos, Figma

This is covered on an issue for zeroheight


Checkboxgroup is not working as expected in the SmartForm

I tried with the "example-forum" in the latest "Vulcan-Starter" repo, I could add the new category, but could not remove the checked category from the "Edit Post" after submitting the form.

OK, I see the issue now. It's a bit tricky to fix, I need to think about it…

Yes it was because of the rewrite. You can see how I fixed it in the linked commit.

The label of the checkboxgroup is disappeared, and the 'null' value causes the validation error if the data type is 'String'.

Yes, I can confirm that it's broken on the current devel. It works on the master branch though (v1.11.2). I don't know what could have broken this, I did not read the latest commits
And the label is missing too.

Add {inputProperties.label} to the beginning of the  could add the label back.
The default value for the 'checkboxgroup' is [""], and it will update to [undefined, "value"] if you toggle the second checkbox. The "undefined" value breaks the graphQL validation when submitting the smart form.

I fixed the missing label. The null value thing is trickier, let me think about it…

So the root issue is deciding whether the array containing the checkbox values can be "sparse" or not, i.e. ['foo', null, 'bar'] vs ['foo', 'bar'].
With nested forms (like in the address example) it's important to preserve empty array items because we rely on paths to update other items – so if we delete the first item, we don't want the foo.0 path to start pointing to the previously second –and now first– item.
For checkboxes though it makes less sense, so maybe we shouldn't be using that same system at all and just handle the entire checkbox array's state inside the checkbox group component instead.

That should hopefully fix it. It was actually a lot simpler than I thought (assuming it actually works now!).

Actually this is still not fixed because when going from ['a', 'b', 'c'] to ['a', 'c'] the old a new values get merged meaning you still end up with ['a', 'b', 'c']…


Improve code coverage of submodule parsing

This is a PR to improve coverage for submodule parsing that's already in the system. Specifically func getSubmodules in pkg/osvscanner/osvscanner.go.
This is already covered by a fixture based test in pkg/osvscanner/osvscanner_internal_test.go but while have execution inside getSubmodules, it doesn't actually cover the working parts of getSubmodules.
You can see coverage info by running  ./scripts/generate_coverage_report.sh and looking in ./coverage.html#file133.
There are a number of states a submodule can be in:

a submodule is setup and checked out
a submodule is setup and but dir is empty
a submodule is setup and and checked out but dir has local changes
a submodule is setup and but dir is set to a different commit

I'm planning to test 1 and 2. I think 3 and 4 are nice to haves, and I plan to only tackle them if they're easy once 1 and 2 are done. Possibly submodules have more possible states, but these seem reasonable for coverage.
I see two implementation options:

re-use and modify the func Test_scanGit in pkg/osvscanner/osvscanner_internal_test.go
but with the fixture including a submodule
re-use and modify the functions that create git repositories from scratch in
https://github.com/google/osv-scanner/pull/797

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 60.89%. Comparing base (b28c1c8) to head (711236e).
Report is 37 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #873      +/-   ##
==========================================
+ Coverage   59.78%   60.89%   +1.11%
==========================================
  Files         136      144       +8
  Lines       11268    11808     +540
==========================================
+ Hits         6737     7191     +454
- Misses       4102     4140      +38
- Partials      429      477      +48

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

I've done a bit more poking and managed to create git-repo with submodules that doesn't have a backing github repo, so re-utilising the existing fixture based testing —func Test_scanGit— looks like the best option at this stage.


Dynamic batching - don't discard built models

Is your feature request related to a problem? Please describe.
preferred_batch_size: [ 1, 2 ]
If there is only a single request trtis rebuilds the model for batchsize 1 and discards the model for batchsize 2.
This makes dynamic batching inefficient for me as I don't have steady load.
Describe the solution you'd like
I would like to have an option to keep models that have been build in memory so I can switch without rebuilding.

TRTIS does not build and discard models in the dynamic batcher. The dynamic batcher simply groups together independent requests that are then sent to the backend framework as a single batched inference request. What framework backend are you using? What makes you think that it is rebuilding models?

the problem occurs fortensorflow savedmodelswith input size [None, None, None, 3].
Everytime the number of clients changes it says something along the lines rebuilding model for input size, which takes around 40 seconds during which no request can be performed.

Is it a pure TF model or is optimized with TensorRT?

I create it using the save_model_cli tool - so I assume it at least gets some optimization
./saved_model_cli convert --dir /saved_model/ --output_dir /saved-model --tag_set serve tensorrt --precision_mode FP16 --max_batch_size 16 --is_dynamic_op True

TF+TRT has an option for how many compiled versions to cache.  Default is 1.

I just got some feedback from TF-TRT engrs. They proposed 2 solutions:

Make all the input shapes static before optimizing  with TF-TRT
Pass the argument maximum_cached_engines with some larger value. The default is 1.

Thanks @nieksand @deadeyegoodwin.


@conda-forge-admin please rerender

Additional comment:
No response

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I rerendered the recipe in conda-forge/celerite-feedstock#24.


Override entity unit of measurement

Hi!
Thanks for da card, it's awesome! :+1:
I have a suggestion, how 'bout adding the ability to overwrite the value of entities?
I mean, so that u can set a localization value, for example if W --> but I want to set to Вт and etc...
Something similar has already been implemented, for example, in lovelace-multiple-entity-row, u can find it here: https://github.com/benct/lovelace-multiple-entity-row#secondary-info
Thanks in advance!

I'll think about this because it has some implications.
You can do this with template entities. The calculations will still work if the prefix is in latin, like kВт. And handling non latin prefixes is too much work to bother.

ok, I thought that it would only concern the display, produce entities specifically for the specific card, well, such a solution :) Okay, let's see. Thank u.

There is a problem with intermediate "remaining_child_state" and my guess is that having two level "remaining_child_state" cause an issue, because the top node does not know the units of measurement, since the the middle node is also a virtual node.
Consider a scenario like
energy
  \/
Lights
\/    \/
1F    2F
   \/
(then actual entities)

Lights, 1F, 2F are all of type remaining_child_state. That would throw an error and it seems so that it is related to that it does not know the "units of measurement". So, being able to specify "unit_of_measurement" would be a good workaround for this problem as well.


Update robocopy.md

By reading the document I miss understood it and did the opposite. By searching the web I found many complaints about the clarity of this document and many answers.
I also did a test robocopy to confirm.

@sanzic-wes : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Export or save the generated barcodes as an image.

Hi,
About the Barcode Generator View.
Is it possible to share, export or save the generated barcodes as an image?
If so, how?
Thanks in advance.

Solved.
Works with the .CaptureAsync() method.

Hi,
This is how I do it:
MainPage.xaml
<zxing:BarcodeGeneratorView
x:Name="bgvBarcode"
Grid.Row="4"
Grid.Column="0"
Grid.ColumnSpan="2"
HeightRequest="250" />

MainPage.xaml.cs
// Button share event - make screenshot of the barcode.
private async void OnShareClicked(object sender, EventArgs e)
{
    if (Screenshot.Default.IsCaptureSupported)
    {
        IScreenshotResult screen = await bgvBarcode.CaptureAsync();
        Stream stream = await screen.OpenReadAsync();

        SaveStreamAsFile(stream);
    }
}

// Save the barcode as an image file.
private static async void SaveStreamAsFile(Stream inputStream)
{
    // Save the image file.
    string cFileName = Path.Combine(FileSystem.CacheDirectory, "BarcodeGenerator.png");

    using (FileStream outputFileStream = new FileStream(cFileName, FileMode.Create))
    {
        inputStream.CopyTo(outputFileStream);
    }

    inputStream.Dispose();

    // Open the share interface to share the file.
    await OpenShareInterface(cFileName);
}

// Open the share interface.
public static async Task OpenShareInterface(string cFile)
{
    await Share.Default.RequestAsync(new ShareFileRequest
    {
        Title = "Barcode Generator",
        File = new ShareFile(cFile)
    });
}

Best regards,
Geert Geerits
From: hukjin @.>
Sent: Wednesday, 23 November 2022 10:04
To: Redth/ZXing.Net.Maui @.>
Cc: Geert Geerits @.>; Author @.>
Subject: Re: [Redth/ZXing.Net.Maui] Export or save the generated barcodes as an image. (Issue #53)
how to use .CaptureAsync()??
—
Reply to this email directly, view it on GitHubhttps://github.com/Redth/ZXing.Net.Maui/issues/53#issuecomment-1324735909, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYKB3DOSEIX2Q55SLZ6RHPLWJXMWRANCNFSM6AAAAAAQURYEYA.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>


Remove unused ActivityLogAttachments (bug 1198817)

Less code, yay !

Tests pass, :shipit:?
BTW, do we rename our migration files or keep the auto generated name?

@ngokevin Mind taking a quick look?

r+ we're not showing activitylogattachments in the reviewer logs so this seems okay.


Implement Feign ErrorDecoder that is aware of spring HttpClientErrorException and HttpServerErrorException

In our consumption of feign we ran into an issue where we need access to the response status code and response body associated to a client error.  We have implemented the following ErrorDecoder implementation in our code base and wanted to share it with the community. It seems like others that are familiar with spring RestOperations are accustom to HttpClientErrorException and HttpServerErrorException exception trees versus the stripped down FeignException.  The only concern with the implementation below is how to handle the response body if an exception where to happen during the copying process from feign response to a given instance of spring HttpStatusCodeException:
public class SpringWebClientErrorDecoder implements ErrorDecoder {

    private ErrorDecoder delegate = new ErrorDecoder.Default();

    @Override
    public Exception decode(String methodKey, Response response) {
        HttpHeaders responseHeaders = new HttpHeaders();
        response.headers().entrySet().stream()
                .forEach(entry -> responseHeaders.put(entry.getKey(), new ArrayList<>(entry.getValue())));

        HttpStatus statusCode = HttpStatus.valueOf(response.status());
        String statusText = response.reason();

        byte[] responseBody;
        try {
            responseBody = IOUtils.toByteArray(response.body().asInputStream());
        } catch (IOException e) {
            throw new RuntimeException("Failed to process response body.", e);
        }

        if (response.status() >= 400 && response.status() <= 499) {
            return new HttpClientErrorException(statusCode, statusText, responseHeaders, responseBody, null);
        }

        if (response.status() >= 500 && response.status() <= 599) {
            return new HttpServerErrorException(statusCode, statusText, responseHeaders, responseBody, null);
        }
        return delegate.decode(methodKey, response);
    }
}

The feign support includes support for returning a ResponseEntity<MyObject> which gives you access to the status code, headers and body.
@FeignClient
interface TestClient {
	@RequestMapping(method = RequestMethod.GET, value = "/helloresponse")
	public ResponseEntity<Hello> getHelloResponse();
}

Updated our code to use the ResponsEntity.  Works great.  It would be useful if there was something adding to the spring cloud documentation around this topic.  If there is something I apologize for missing it.

Nope, opened #319

We started to do more integration testing and this appears to be working slightly different than I expected based upon your comment of using the ResponseEntity.  Our use case is to handle a rest API that would return a 409 in the case of a conflict and a 201 in the case of a resource that is created.  In these two scenarios the 409 results in a FeignException and the 201 results in a null object being returned instead of a resource entity.  The 201 null object response we can account for.  However, I was hoping that the 409 would result in a populated ResponseEntity.  We also experience this in the case of a 400.

Pull requests are welcome.

When I use
@FeignClient("usermanagement")
public interface UserClient {
	@RequestMapping(method = RequestMethod.GET, value = "/um/v1/user/{secLoginId}", produces = "application/json")
	ResponseEntity<List<SecUserDTO>> getUsersWithHeader(@PathVariable("secLoginId") String secLoginId);
}

and then getUsersWithHeader returns 404, in exception (FeignException) e .g. like this:
feign.FeignException: status 404 reading UserClient#getUsersWithHeader(String); content:
{
  "httpStatus" : "NOT_FOUND",
  "code" : "U001",
  "message" : "User [ blah ] not found",
 }

How do I determine that I got 404 ? I thought if I wrap it into ResponseEntity, I wont get Exception, but I'm still getting FeignException. Here is my call:
try
		{
		ResponseEntity<List<SecUserDTO>> response = userClient.getUsersWithHeader(loginId);
		if (response.getStatusCode().equals(HttpStatus.OK))
		{
			List<SecUserDTO> userList = response.getBody();
			log.info("userList :{}", userList );
			if (userList != null && userList.size()>0)
			{
				returnUser=userList.get(0);
			}
		}
		else
		{
			log.error("Got error code:{} headers:{}", response.getStatusCode(), response.getHeaders());
		}

		}
		catch(Exception e)
		{
			log.error("Exception:",e);
		}

How do I call getUsersWithHeader and determine if I get 404 ?

@bogdatov you need to use a create a feign.ErrorDecoder.

How I can registermy feign.ErrorDecoder with FeignClient?
Why Error 404 is not catch by ResponseEntity with FeignClient?

How I can registermy feign.ErrorDecoder with FeignClient?

See the docs Overriding Feign Defaults for how to register your ErrorDecoder.

Why Error 404 is not catch by ResponseEntity with FeignClient?

Because feign throws an error, though feign 8.12 will change that.

Thanks.

@spencergibb I implemented ErrorDecoder, but still not able to get the exact error response message. I am only receiving status (as 400 or 500 etc) and reason (as BAD REQUEST or SERVER ERROR) but no exact response message like why 400 or 500. e.g. I am calling spring oauth2 through feign client to check if token is valid. in case of invalid token, oauth2 throwing exception as Bad request along with response body:
{"error":"invalid_token","error_description":"Token was not recognised"}

but in ErrorDecoder on caller side, I am only getting reason and status from response and not the exact message. any idea ?

Hi, I think automatically decode exception objects depend on the declared thrown types maybe a good idea. Just like:
@FeignClient
interface TestClient {
    @RequestMapping(method = RequestMethod.GET, value = "/hello/{name}")
    public Hello getHelloResponse(@Param("name") String name) thrown InvalidNameException;
}

@ResponseStatus(HttpStatus.BAD_REQUEST)
class InvalidNameException extends IllegalArgumentException {
    // ...
}

If the response status is BAD_REQUEST, it will decode and throw InvalidNameException automatically.  If the method has more than one declared exception types, the decoder will choose one by some kind of conditions, like the ResponseStatus annotation on the InvalidNameException.

I used
@AuthorizedFeignClient
Instead of the default Feign Client and the issue is solved

Hey guys what status of this?
I use @FeignClient(value = "test-service", decode404 = true) and it's handle 404 error, so I got ResponseEntity filled by code without exception.
Is this da way?

Basically I use FeignClient to communicate with HATEOAS like service, full example code:
@FeignClient(value = "test-service", decode404 = true)
public interface TestServiceClient {
    @GetMapping(value = "/testItems", consumes = MediaTypes.HAL_JSON_VALUE)
    ResponseEntity<Resources<TestItem>> findAll();

    @GetMapping(value = "/testItems/{id}", consumes = MediaTypes.HAL_JSON_VALUE)
    ResponseEntity<Resource<TestItem>> findOne(@PathVariable("id") String id);
}

@Hronom the issue is still open so the issue still exists

Not sure why FeignException has to convert the actual exception into a String and stuff it inside the Body. Most rest services throw custom exception and it would be nice to let them propagate as such. Now with @ResponseStatus we can define various Http Codes on exceptions all over an application. Having a centralized error decoder and trying to untangle them from the String seems like a waste of time. I have spent enough time just to untangle the actual business exception I want buried deep inside FeignException as a string!

feign.FeignException: status 404 reading FeignInterface#test(String); content:
{"timestamp":1519611212015,"status":404,"error":"Not Found","message":"No message available","path":"/**/test"}

Guys I think me and other people a little bit confused about that we use ResponseEntity<> and still get exceptions instead of "filled" ResponseEntity<> with error code 4xx, 5xx etc.
It would be nice if you put flag in annotation org.springframework.cloud.netflix.feign.FeignClient like enable processing of ResponseEntity<>.
Or do it automatically if you see ResponseEntity<> as return type.

I think the problem here is that ResponseEntity is parameterized class, and the only way to deserialize json response is to read it's type parameter.
Imageine a feign method that returns something like ResponseEntity<MyDTO>
When API returns response with status 500, then usually it's body is not deserializable into MyDTO. It should be deserialized into MyApiError or something. Or just Map<String, Object>. But anyway not into MyDTO.
This is the reason why RestTemplate can't just return ResponseEntity when response status is not 2xx and throw exception instead.
And this is the reason, I think, why this library can't do this.
Instead an ErrorDecoder should decode error response into ApiError model and throw specific appliation exception or some general exception, that includes ApiError as field.

how do we define errorDecoder if we use @FeignClient annotation on an interface to act as feign client or remote service interface?

@coolprashi06 your question seems unrelated, please open a separate issue in https://github.com/spring-cloud/spring-cloud-openfeign


system_tests_tcp_adaptor_tls failing with router crash on assert

 Thread 1 (Thread 0x7f4e3c04a700 (LWP 3269)):
#0  0x00007f4e45582aff in raise () from /lib64/libc.so.6
#1  0x00007f4e45555ea5 in abort () from /lib64/libc.so.6
#2  0x00007f4e45555d79 in __assert_fail_base.cold.0 () from /lib64/libc.so.6
#3  0x00007f4e4557b456 in __assert_fail () from /lib64/libc.so.6
#4  0x000000000044340f in qd_raw_connection_drain_read_buffers (pn_raw_conn=0x3bbc120) at /home/runner/work/skupper-router/skupper-router/skupper-router/src/adaptors/adaptor_common.c:167
#5  qd_raw_connection_drain_read_buffers (pn_raw_conn=0x3bbc120) at /home/runner/work/skupper-router/skupper-router/skupper-router/src/adaptors/adaptor_common.c:160
#6  0x0000000000443448 in qd_raw_connection_drain_read_write_buffers (pn_raw_conn=0x3bbc120) at /home/runner/work/skupper-router/skupper-router/skupper-router/src/adaptors/adaptor_common.c:179
#7  0x0000000000447a28 in handle_connection_event (e=<optimized out>, qd_server=<optimized out>, context=0x394e350) at /home/runner/work/skupper-router/skupper-router/skupper-router/src/adaptors/tcp/tcp_adaptor.c:1088
#8  0x000000000049ee71 in handle_event_with_context (context=<optimized out>, qd_server=<optimized out>, e=<optimized out>) at /home/runner/work/skupper-router/skupper-router/skupper-router/src/server.c:793
#9  do_handle_raw_connection_event (qd_server=<optimized out>, e=<optimized out>) at /home/runner/work/skupper-router/skupper-router/skupper-router/src/server.c:799
Undefined command: "py-bt".  Try "help".
#10 handle (qd_server=qd_server@entry=0x244e3a0, e=e@entry=0x3739720, pn_conn=pn_conn@entry=0x0, ctx=ctx@entry=0x0) at /home/runner/work/skupper-router/skupper-router/skupper-router/src/server.c:1076
#11 0x00000000004a0dec in thread_run (arg=0x244e3a0) at /home/runner/work/skupper-router/skupper-router/skupper-router/src/server.c:1108
#12 0x00007f4e467951ca in start_thread () from /lib64/libpthread.so.0
#13 0x00007f4e4556de73 in clone () from /lib64/libc.so.6

https://github.com/skupperproject/skupper-router/actions/runs/3577663632/jobs/6016923702#step:31:115

Upon analyzing the router logs, it looks like the client in some cases pipelines a valid http request followed right after the TLS handshake. In the failure case, the client is expected to send a client cert to the router and it does not, so the TLS handshake fails. But there is pipelined request is still in the input buffer and that is ok and we need to discard this buffer since the TLS handshake fails.
It is ok to remove the assert in qd_raw_connection_drain_read_buffers() in adaptor_common.c


Locales are inheritance

Why the locale change for all not for current browser # user.
When i get 2 instace of my site and switch language, language is switched in both. Why its isn;t switched for browser window?

Hi @Perfect7M I can't reproduce this. Could you please point me to a stripped-down sample app / code which shows this behavior? Thanks!


Fixed: selector-no-redundant-nesting-selector now handle multiple nested selectors.

Fix: https://github.com/kristerkari/stylelint-scss/issues/112

Awesome work! Thanks a lot


Support custom STS endpoint

Is your feature request related to a problem? Please describe.
MinIO now supports STS client authentication, https://min.io/docs/minio/linux/developers/security-token-service.html
This does not seem to be supported currently by Quickwit due to a lack of support for custom STS endpoints.
Describe the solution you'd like
In order to support this, the rust AWS sdk needs to be configured to use a custom STS endpoint. I could imagine a QW_STS_ENDPOINT env var.
Describe alternatives you've considered
Creating and distributing secret keys and access keys in my cluster is operationally challenging and often requires security tradeoffs.
Additional context
If this is pretty low lift I'm happy to take a crack at it, but I'm new to Rust and this project.

@rmvangun We welcome contributions :)

I did do a little investigation on the matter, and would be happy to help out though I'm pretty constrained on bandwidth right now--I'll add my research for the time being and if the implementation looks straightforward I'll try to hop in sooner than later.
Some AWS SDKs supports the ability to specify any AWS service endpoint using something like AWS_ENDPOINT_URL_<SERVICE> doc. Unfortunately, the rust AWS SDK isn't one of them (yet).
In lieu of this, would need to do it directly via the SDK, expand the client implementation in https://github.com/quickwit-oss/quickwit/blob/6fa3c295fa9518712a8dd3cb04476850d45ef24c/quickwit/quickwit-storage/src/object_storage/s3_compatible_storage.rs


Extensions for alternative code editors

Sorry for putting this into issues but I wasn't sure how else to ask.
Are there extensions for alternative code editors than Brackets? I use Atom Editor and a lot of my team use Sublime Text.
It would be great to have an extension for these editors too so we're not having to use a different code editor.
Thanks

+1

You can use VLT and there is a plugin for Sublime2 (https://github.com/tomalec/Sublime-Text-2-Vlt-Plugin). Personally the thing that made it difficult for me to continue using Something like Sublime was the fact that .vlt files were created on each directory.
Lastly (and if you don't mind the extra step) Once the connection has been made between Brackets and AEM you can fire up your favorite editor and use it. Brackets will keep files in sync in the background.
So far I have not found any issues with that approach, however I have learned to live with brackets and actually it is not "that" bad. Enjoy!

@helmutgranda this is currently the workflow I have to endure to work on any AEM project. My point is I shouldn't have to be forced to use another Adobe product in order to work in AEM. There should be the option to choose.

@glennflanagan Agreed! And I believe that is why the code is open source so that you can fork and integrate with your favorite IDE. I would imagine that developing their own free IDE with free tools may keep the Adobe team busy enough to not be able to release plugins for other IDEs but that is mho.

I have ported the sync feature to Visual Studio Code.
Please try it!
https://marketplace.visualstudio.com/items?itemName=yamato-ltd.vscode-aem-sync


Add build cache client library

Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

@bot-gradle test BD

I've triggered the following builds for you. Click here to see all build failures.

BuildDistributions build

The merge queue build has failed. Click here to see all failures.

The merge queue build has failed. Click here to see all failures.

@bot-gradle test this please.

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test this please.

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

Why not Guice 6? see https://github.com/google/guice/wiki/Guice600
Or even Guice 7 which switches to jakarta.inject? See https://github.com/google/guice/wiki/Guice700


{AKS} Vendor new SDK and bump API version to 2023-11-02-preview

This checklist is used to make sure that common guidelines for a pull request are followed.
{AKS} Vendor new SDK and bump API version to 2023-11-02-preview.
Related command

General Guidelines

[] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[x] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
[x] My extension version conforms to the Extension version schema

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

AKS


how can I build cmake with arm64 architecture?

I saw the tutorial and I can make libsioclient_tls.a file .
and it works when I use iphone simulator in my mac.
but there is some problem when I compile project with my iphone.
After I searching I found it because of build architecture.
when I use file
cmake -DBOOST_INCLUDEDIR=/Users/David/Desktop/Developement/projects/asio/boost_1_63_0 -DBOOST_LIBRARYDIR=/Users/David/Desktop/Developement/projects/asio/boost_1_63_0/stage/lib -DBOOST_VER:STRING=1.63.0 -DTARGET=sioclient_tls -DOPENSSL_INCLUDE_DIR=/usr/local/opt/openssl/include
there is only x86_64 architecture available.
I need arm64 or armv7 architecture. How can I make libsioclient_tls.a and libboost.a file with arm64 architecture..?

Hi, we removed the boost dependency and changed a bit the build system. Could you try again?


Compilation error with sc_fifo< std::vector<...> >

I want to store std::vector in sc_fifo. But by definining a variable of type
sc_fifo< std::vector<uint16_t> > fifo;
I get the following error:
In file included from /home/gav/SystemC-2.3.4/include/systemc:84,
                 from /home/gav/systemc-test/src/main.cpp:1:
/home/gav/SystemC-2.3.4/include/sysc/communication/sc_fifo.h: In instantiation of ‘void sc_core::sc_fifo<IF>::print(std::ostream&) const [with T = std::vector<short unsigned int>; std::ostream = std::basic_ostream<char>]’:
/home/gav/SystemC-2.3.4/include/sysc/communication/sc_fifo.h:431:12:   required from ‘std::ostream& sc_core::operator<<(std::ostream&, const sc_core::sc_fifo<T>&) [with T = std::vector<short unsigned int>; std::ostream = std::basic_ostream<char>]’
/home/gav/systemc-test/src/main.cpp:28:18:   required from here
/home/gav/SystemC-2.3.4/include/sysc/communication/sc_fifo.h:317:16: error: no match for ‘operator<<’ (operand types are ‘std::ostream’ {aka ‘std::basic_ostream<char>’} and ‘std::vector<short unsigned int>’)
  317 |             os << m_buf[i] << ::std::endl;
      |             ~~~^~~~~~~~~

But actually I have defined operator<< for std::vector<uint16_t>.
Here is the full code of my test program:
#include <systemc>
using namespace sc_core;

#include <vector>
#include <stdint.h>

std::ostream& operator<<(std::ostream& out, const std::vector<uint16_t>& data )
{
    return out;
}

int sc_main(int argc, char* argv[])
{
    sc_fifo< std::vector<uint16_t> > tmp;
    std::cout << tmp;

    std::vector<uint16_t> ddd;          // just for checking operator<< for std::vector<uint16_t> is really defined
    std::cout << ddd << std::endl;

    sc_start(4, SC_SEC);

    return 0;

};

If I comment lines
    sc_fifo< std::vector<uint16_t> > tmp;
    std::cout << tmp;

the compilation finished successfully, but when I uncommnent them then I get the error as provided above.
My OS is Ubuntu 22.04.
Tested on SystemC v2.3.3 and v2.3.4

Your issue seems not SystemC-related, but most likely a C++ issue (operator visibility when instantiating the template). Please post on a C++ forum for further discussion.

It is not a problem with SystemC, but rather understanding that sc_signal and sc_fifo have requirements on T that are not part of standard C++ containers. A simple wrapper can solve this.
See https://github.com/dcblack/sc_fifo-of-vector for how to do this.
It is likely you need proper formal training in Modern C++ and SystemC.
Note: I teach C++ and SystemC for Doulos. Our graduates know this stuff. Go to https://www.doulos.com for more information.


go-camo: 2.4.13 -> 2.5.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/cactus/go-camo/releases.
meta.description for go-camo is: Camo server is a special type of image proxy that proxies non-secure images over SSL/TLS
meta.homepage for go-camo is: https://github.com/cactus/go-camo
meta.changelog for go-camo is: https://github.com/cactus/go-camo/releases/tag/v2.5.0
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.5.0 with grep in /nix/store/pppa8rh4l2gzxhmcfqgjqsqqkvr3b334-go-camo-2.5.0
found 2.5.0 in filename of file in /nix/store/pppa8rh4l2gzxhmcfqgjqsqqkvr3b334-go-camo-2.5.0

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

go-camo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/pppa8rh4l2gzxhmcfqgjqsqqkvr3b334-go-camo-2.5.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/20442b4e0bec861d0c36e84260ae650b83cfa5fe#go-camo

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

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

1 package built:

go-camo

Maintainer pings
cc @viraptor for testing.

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

1 package built:

go-camo


[Feature Request] [Telemetry] Make available the instance of tracer and metrics registry to all the plugins

Is your feature request related to a problem? Please describe
We want to extend the support of telemetry in the plugins so that plugin code can also be instrumented. We are working on an issue  to migrate the metrics from Performance analyzer to the telemetry framework. In order to achieve that we need to inject the telemetry objects to the plugins.
Describe the solution you'd like
We should add a method in the plugin interface which helps in injecting the telemetry instances to all the plugins and plugin can overrirde that method and use. Instead of injecting the multiple instances we should have a one single Telemetry object which should be able to give access to specific objects like tracer and metricsRegistry.
Related component
Other
Describe alternatives you've considered
No response
Additional context
No response

[Triage - attendees 1 2 3 4 5 6 7 8]
@Gaganjuneja Thanks for creating this issue and pull request for this functionality


Request: 12/24h Time Format

Would be awesome so switch the time format from 12 to 24.

I did a PR for this request https://github.com/bpxl-labs/StatusBarLayer/pull/14


Reset of N250SP on P9 leads to lost PCIe link

On the N250S+ in a Zaius P9 system, the card reset via sudo sh -c "echo 1 > /sys/class/cxl/card0/reset"doesn't work most times. This means the card can't be updated reliably without power cycling the system, and automated Jenkins testing is not possible.
This may also affect other CAPI 2.0 cards on P9, so the fix must be done for all supported cards.
The issue was found and fixed in another N250SP design:
Changes required for CAPI2-BSP/N250SP/src/capi_bsp.vhdl: It is missing some fixes related to reset that might be causing lab issues.

The MCM that generates the psl_clk and icap_clk should have its reset input tied off:
-- MMCM to generate PSL clock (100...250MHz)
pll0:         flashgtp_clk_wiz
PORT MAP  (
clk_in1  => pcihip0_psl_clk, -- Driven by PCIHIP
clk_out1  => psl_clk,   -- Goes to PSL logic
clk_out2    => psl_clk_div2, -- Goes to PSL logic
clk_out3  => icap_clk,     -- Goes to SEM, multiboot
clk_out3_ce => icap_clk_ce,     -- gate off while unstable to prevent SEM errors
-- reset   => pcihip0_psl_rst, -- Driven by PCIHIP
-- reset was pcihip0_psl_rst.  this killed the clock to icap before a reconfig could complete
reset   => '0',
locked   => clk_wiz_2_locked
);

The reset inputs to PSL9_WRAP_0 need to change as well:
-- PSL_RST and PCIHIP_PSL_RST must both be asserted if one is asserted
-- If only 1 is asserted, async fifo gets into invalid state
PSL_RST         => pcihip0_psl_rst,  -- was psl_reset_sig,
PSL_CLK         => psl_clk,
PCIHIP_PSL_RST  => pcihip0_psl_rst,
PCIHIP_PSL_CLK  => pcihip0_psl_clk

=> take over latest PSL changes into capi2-bsp, in addition to the two changes listed above

These changes should be applied to all of the cards, not just N250S+.   These changes are also committed to the FlashGTPlus repo.


Rename 'authorization' header to 'x-access-token'

The readme refers to x-access-token as the header that'll be used to pass the token around in, but the code didn't. Now is do.

Ah...! Ciao @olizilla!
Sadly, its the readme that needs to be updated ... My Bad ... :disappointed:
Our Hapi.js Plugin uses request.headers.authorization
see: https://github.com/dwyl/hapi-auth-jwt2/blob/f62bf57795e22b97f5c31a2375b68d6e7e6b80e1/lib/extract.js#L21-L22
Its worth keeping it consistent because the plugin advises people to visit the this repo to learn more about JWTs ... thanks so much for drawing our attention to this!

For my knowledge is authorization the generally preferred header name for this kind of thing? What was the backstory on the change?

Ah, we was using x-access-token but switched to using the (standard) authorization header because it was mentioned in the spec:
http://self-issued.info/docs/draft-ietf-oauth-json-web-token.html#rfc.section.1
(or RFC: http://www.rfc-editor.org/rfc/rfc7519.txt if you prefer ... you'll need to grep for it)
and it keeps it consistent with Hapi Auth Basic:
https://github.com/hapijs/hapi-auth-basic/blob/ea5b694adeaf15b3df46243a5501394d6f3c9268/lib/index.js#L35
Also, there's industry trend (best-practice?) for it:

https://developer.atlassian.com/static/connect/docs/latest/concepts/authentication.html
http://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-auth-using-authorization-header.html
https://dev.twitter.com/oauth/overview/authorizing-requests

@nelsonic ok so. Do you think the auth scheme should be prefixed into the header value, as it is with other schemes, Basic is prefixed with Basic, Digest has Digest...
https://en.wikipedia.org/wiki/Digest_access_authentication
The Atlassian seems to do it with JWT:
Authorization" header value: "JWT <insert jwt-token here>"

https://developer.atlassian.com/static/connect/docs/latest/concepts/authentication.html
Perhaps a win for consistency at the expense of simplicity. I've no strong opinion. I guess as it's joining the masses in a commonly used header it'd be polite to follow suit.

Yeah, its easier to use the authorization key because hapi automatically toLowerCase()es the header keys (so you don't have to remember if its upper/lower case) oh, and did I mention its one fewer character to type. :wink:

Does #39 superseded this PR?

This PR is irrelevant now, but the question above is about the value for the Authorisation header. Should it be prefixes with JWT to denote the Authorisation method bei g used as per other styles like Basic et al?

We could probably have some sort of word to denote that the token is a JWT ...
But we are assuming that there will only be one token passed by the client.
A multiple token use-case has not yet surfaced ...

If we want to use basic auth, we simply register the https://github.com/hapijs/hapi-auth-basic plugin first and it will attempt to authenticate the user first in the request lifecycle.
But again, this use-case has not presented its' self.
If you are happy that the readme/demo app is consistent, please close the PR.
(Sorry to have created work for you ... will buy you a :beer: next time we :bowling: )


[NPM] Periodic Reconciliation of NPM Chain ordering in FORWARD table

Today, NPM is in a configure and forget state for adding AZURE-NPM chain in FORWARD iptable chain. This change will include running a go routine to periodically (every 5 mins) check the order of AZURE-NPM chain in FORWARD. We can later extend this go routine to check other chains too.

/azp run

/azp run


Wanted to get my changes in before we start changing things around too much.

Also, I know the GetDthickness() function is ugly, but I don't know of a cleaner way to do per-pixel variables.  TChannel only handles per-strip.

but you may want to look in https://github.com/steffencruz/SharcCalibration
where we do things like this a bit more elegantly for ideas.  just a
reference for future work.
I am trusting that these things do what you want, if you ever find your
self stuck trying to get a job done, let me know.  I might have some code
stashed away somewhere that does a very similar job.
On Mon, Jul 20, 2015 at 6:43 PM, Ryan Braid<EMAIL_ADDRESS>wrote:

Also, I know the GetDthickness() function is ugly, but I don't know of a
cleaner way to do per-pixel variables. TChannel only handles per-strip.
You can view, comment on, or merge this pull request online at:
https://github.com/GRIFFINCollaboration/GRSISort/pull/402
Commit Summary

Doubled almost equal window
Added loop to correlate single punchthrough events
Added thickness information to TCSM
Removed debug output
Merge branch 'master' of
https://github.com/GRIFFINCollaboration/GRSISort
Merge branch 'master' of
https://github.com/GRIFFINCollaboration/GRSISort
Forgot to comment out a diagnostic message
Merge branch 'master' of
https://github.com/GRIFFINCollaboration/GRSISort
Merge branch 'master' of
https://github.com/GRIFFINCollaboration/GRSISort
Switched to rudimentary minimizer when evaluating two possible hits
Added break statements to loops. Also have diagnostic printing
New build de e
added 2 in d
added others
Moved away from summing for now
Merge branch 'master' of
https://github.com/GRIFFINCollaboration/GRSISort

File Changes

M include/TCSM.h
https://github.com/GRIFFINCollaboration/GRSISort/pull/402/files#diff-0
(2)
M include/TCSMHit.h
https://github.com/GRIFFINCollaboration/GRSISort/pull/402/files#diff-1
(6)
M libraries/TGRSIAnalysis/TCSM/TCSM.cxx
https://github.com/GRIFFINCollaboration/GRSISort/pull/402/files#diff-2
(318)
M libraries/TGRSIAnalysis/TCSM/TCSMHit.cxx
https://github.com/GRIFFINCollaboration/GRSISort/pull/402/files#diff-3
(41)

Patch Links:

https://github.com/GRIFFINCollaboration/GRSISort/pull/402.patch
https://github.com/GRIFFINCollaboration/GRSISort/pull/402.diff

—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/pull/402.


How to share the intent observable?

Hi, In My app User clicks a button to increment the counter by one. But the user can click the button rapidly to increase the count. As the user clicks a network request would get fired. But i don't want to fire network request every time the button get clicked. But I also want the UI get updated as soon as the event happens. I tried to use share operator but then it doesn't work. So how should I approach this problem.

You can use Multicasting in RxJava. Like:
val buttonStream = view.buttonClickedTream().share()
buttonStream.subscribe { // update UI }
buttonStream.flatMap(doNetworkStuff()). subscribe { //update UI}

You can take a look at this blog: http://blog.danlew.net/2016/06/13/multicasting-in-rxjava/

The intent method in the presenter takes the observable returned by the view. I added a share operator on the button click observable so that I could have two subscribers one for updating ui immediately and other for network operation. But with that setup the UI updation code never executes.

There are may ways to do this. share() could be used like this in Presenter.bindIntents():
public void bindIntents(){
  Observable<?> buttonClickIntent = intent(View::butonClickIntent).share();
  Observable<Foo> directUpdate = buttonClickIntent.map( /* transform to state to update UI immediately */ );
  Observable<Foo> networkRequest = buttonClickIntent.map( /* execute network request */):

  Observable<Foo> allObservables = Observable.merge(directUpdate, networkRequest);
  subscribeViewState( allObservable,  View::render);
}

Alternatively, you could also do something like this:
public void bindIntents(){
  Observable<Foo> observable = intent(View::clickIntent)
        .flatMap(click -> {
               if (shouldRunNetworkRequest())
                   return networkApi.getFoo()
                                    .startWith(Foo.initialValue());  // directly Update UI before starting Http request
               else
                   return Observable.just(new Foo() ); // Directly update UI, no networkRequest
         });
  subscribeViewState( observable,  View::render);
}

I hope this gives you an idea on how this could be achieved.
There are also other ways, it really depends on what exactly you want to implement.

Thanks. Your Suggestion works.

Great. Please consider asking future queations like this on stackoverflow because stackoverflow is much better indexed compared to github issue tracker by search engines like google and therefore easier to find for other Mosby users with same / similar question. There is a mosby tag on stackoverflow I regularly keep looking at for new questions. Also this question is not really Mosby related, its more aboit RxJava chain construction.
I would also appreciate if you could copy over this question & answer to stackoverflow.
I'm sure you are not the first nor the last developer facing such a problem. Thanks.

I would definitely going to do that.  I will post this question tommorow.


Add localhost masquerade for Thunder plugin

Description
Add localhost masquerade for the Thunder plugin
Test Procedure
Add thunder plugin and check if there is a localhost connection on port 9998
Type of Change

[ 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)
[ ] Other (doesn't fit into the above categories - e.g. documentation updates)

Requires Bitbake Recipe changes?
No

Closed due to inactivity, please restore if still needed.


"New Item" menu should contain "Razor Component" element

See https://github.com/aspnet/AspNetCore/issues/10945 for details.

Duping out in favor of https://github.com/dotnet/aspnetcore-tooling/issues/4560.


Where is the documentation now?

Hi all,
Is there a link that I can look up all the functions? It used to have one but now I can't find it anywhere, seems like that the links is not very stable and always disappear!

You can generate it by make doc

The documentation for python lives under http://mxnet.io/packages/python/index.html

Thank you!


fix: add secret scanning

Long-lived branch for FE projects

We will carefully merge this

Assumption
I assume changing the sbom names won't impact anything.
Next steps
Gonna look over all uses of these workflows, and chose an indicative set to test once merged.

@TelicentPaul resolved merge conflicts here https://github.com/telicent-oss/shared-workflows/pull/45/commits/6e74d0fc6ac2b99b883c78e3b015237f1e931f78 -


Add BLOC into the project

#7
I've crated blocs for News, Articles and ChannelIcon.
I also have created Api classes to handle the HTTP requests.
Please notice that I've changed some Stateful Widgets where the arguments are passed down to State classes. It's unnecessary and you can access theses fields using 'widget.' prefix.
I've also changed some fat arrow functions to regular methods when I had some readability difficult.
If there are anything wrong, please let me know. :)

Are there some problem with my changes? I've tested and it's working normally in Android.


SSL certificate for root domain is showing invalid.

App Id: d1adxv4fcyjebh
Region: Mumbai
Step: SSL certificate for custom third party domain
Issue/question
The SSL certificate configured by amplify for the root domain i.e domain.com is showing invalid, while the SSL certificate for the www.domain.com url is working fine. I am using godaddy for my domain management. I have configured a redirect from root domain to the www subdomain in my godaddy as well as amplify aws account.
Whenever I browse to domain.com it shows privacy error with the error message
NET::ERR_CERT_COMMON_NAME_INVALID and my page does not redirect to the www domain.
I have configured the CNAME record for the ssl certificate and the www domain at godaddy properly.

@teslaLDead. The reason is that the certificate we issued for you is for www.domain.com and is mismatched with domain.com.  You should set redirect rule for your root domain.

I solved the issue by using aws name servers instead of godaddy NS. Configured aws route 53 to set my CNAME and other records. It is working fine now.

@teslaLDead I am having the exact same issue and followed what you described to resolve- however I am now getting a https://shortener.secureserver.net/error_404 response when trying to navigate to the root domain. Any thoughts?

After the long research, the AWS amplify is not supporting the https://example.com, it only redirect URL to www by using the domain forward option with our domain provider, The solution was we need to replace our AWS Route 53 NS Records with our domain provider NS record, then it will work with https://example.com
Anyone have better solution please share here
Thanks in Advance

In case anyone comes across this problem in the future, we've added a FAQ section to our docs: https://docs.aws.amazon.com/amplify/latest/userguide/custom-domain-troubleshoot-guide.html#ssl-HTTPS-errors-on-domain


BC: drop support for python<3.8

currently supporting python >- 3.7
3.7 is end of life -- see https://devguide.python.org/versions/
lets drop PY3.7 support

checklist:

[ ] update py-requirement in project manifest
[ ] update trove classifiers in project manifest
[ ] update CI
[ ] update test envs (tox)
[ ] update in code switches: based on sys.version_info

@madpah FYI.
i am planning to release https://github.com/madpah/serializable/pull/47 early next tear.
and after that, around end of January, the v1 will be finalized.


Setting com.sun.xml.internal.bind.ObjectFactory property raises an exception on JRE server

This code u.setProperty("com.sun.xml.internal.bind.ObjectFactory", new ObjectFactoryEx() raises an exception when the engine is run in JRE server environment. The issue is related to 			https://bugs.eclipse.org/bugs/show_bug.cgi?id=406032
and https://javaee.github.io/jaxb-v2/doc/user-guide/ch03.html#compiling-xml-schema-adding-behaviors.

Yes, I checked in a fix for it. Interesting how I didn't catch it. Thanks

Please verify that the applied fix in the referenced commit resolves this issue and close. Thanks


Remove gql.d.ts or make gql.d.ts optional

Is your feature request related to a problem? Please describe.
I'm using GraphQL TypeScript Code Generator. It can output .d.ts files like:
declare module '*/xxxxx.gql' {
  import { DocumentNode } from 'graphql';
  const defaultDocument: DocumentNode;
  export const SomeQuery: DocumentNode;

  export default defaultDocument;
}

but if I install vue-apollo it is overwritten by gql.d.ts and the compiler says:
 ERROR  ERROR in xxxx.vue(20,10):                                                                nuxt:typescript 23:12:39
20:10 Module '"*.gql"' has no exported member 'SomeQuery'. Did you mean to use 'import SomeQuery from "*.gql"' instead?
  > 20 | import { SomeQuery } from<EMAIL_ADDRESS>
Describe the solution you'd like
Remove gql.d.ts file or make it optional.

PR related #881

Thanks, actually I'm doing the same.
I hope it will be solved sooner or later.


Nextjs 14 compatibility

Are there plans to make it compatible with nextjs 14?

Looking forward to it regardless 👍

Do you guys have any ETAs on this or is this a "when it's done" situation? Looking forward to it regardless 👍

This week, for sure 🤗

TailAdmin is now compatible with Next.js 14


wrong X509v3 Authority Key Identifier

Hello! Help me please sign my certificates correct.
I have this code:
func signCertificate(cert, caCert *openssl.Certificate, caKey openssl.PrivateKey) (err error) {
	if err = cert.AddExtensions(map[openssl.NID]string{
		openssl.NID_basic_constraints:        "CA:FALSE",
		openssl.NID_netscape_cert_type:       "client, email",
		openssl.NID_netscape_comment:         "OpenSSL Generated Client Certificate",
		openssl.NID_subject_key_identifier:   "hash",
		openssl.NID_authority_key_identifier: "keyid,issuer",
		openssl.NID_key_usage:                "critical, nonRepudiation, digitalSignature, keyEncipherment",
		openssl.NID_ext_key_usage:            "clientAuth, emailProtection",
	}); err != nil {
		return err
	}

	if err = cert.SetIssuer(caCert); err != nil {
		return err
	}

	return cert.Sign(caKey, openssl.EVP_SHA256)
}

My generated certificate has 'X509v3 Authority Key Identifier' and 'X509v3 Subject Key Identifier' fields the same. This is a problem, because it means that generated certificate is not valid. Could you  help me with this problem ?

Sorry, this doesn't appear to be a problem in the bindings. NID_subject_key_identifier and NID_authority_key_identifier have distinct values that match the definitions in https://github.com/openssl/openssl/blob/f52292be10cb42c25ae83be969d3ad469ea7cb4e/include/openssl/obj_mac.h.


[FEATURE] Support for creating CrewAI projects using uv instead of poetry

Feature Area
Other (please specify in additional context)
Is your feature request related to a an existing bug? Please link it here.
NA
Describe the solution you'd like
Description
Currently, Crewai uses Poetry for project creation and dependency management. While Poetry is a robust tool, I propose adding support for uv as an alternative option for creating Crewai projects.
Proposed Change
Introduce the ability to create Crewai projects using uv in addition to the existing Poetry setup. This would allow users to choose their preferred tool based on their specific needs. That could be done, for example, with a command such as:
crewai create crew <my_project> --package-manager uv

Benefits

Faster Dependency Resolution: uv resolves dependencies approximately 10 times faster than Poetry, significantly reducing setup time.
Flexibility: Offering uv as an option provides users with more flexibility and choice in their development workflow.
Performance: Improved performance in dependency management can lead to a more efficient development process.

Use Cases

Projects with large and complex dependency trees that require faster resolution times.
Development environments where speed and efficiency are critical.
Teams that prefer uv for its performance benefits but still want to use Crewai.

Impact

Minimal Disruption: This change would not deprecate the current Poetry solution, ensuring that existing workflows remain unaffected.
Optional Adoption: Users can opt to use uv based on their preference, making the transition smooth and voluntary.

Describe alternatives you've considered
I've manually migrated some of my Crewai projects to uv, but crewai run runs poetry run run_crew, which is a small nuisance.
I can run them with uv run <my_script>, or simply importing the crew class in a notebook.
Additional context
No response
Willingness to Contribute
Yes, I'd be happy to submit a pull request

Thank you for the suggestion. We are actually merging this tomorrow. We've been working on this migration the past few weeks!


Use seo_description instead of page.description

seo_description is used in the meta tags but not in the ld+json
If page.description is not set, the the description at ld+json will be null.
Meta tags and ld+json should use the same logic.
Same PR (#40) was send to main branch.

Thanks @CGarces! Believe the failing tests are due to https://github.com/benbalter/jekyll-seo-tag/pull/43.


Adding tests for sourceWDTInstallHome and sourceModelHome

Jenkins results -
https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/8714/
https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/8711/

Can u add a test case for the JIRA [OWLS-94649 ( Domain Status should report error when there is problem pulling auxiliary image )

Is this specific to AI 4.0? If not, it can go in different IT class in separate PR.

Can u add a test case for the JIRA [OWLS-94649 ( Domain Status should report error when there is problem pulling auxiliary image )

Is this specific to AI 4.0? If not, it can go in different IT class in separate PR.

This is not specific to 4.0 but since the test case deals with  AuxImages I want to add a Even usecase specific to AuxImage.  I do not see any AuxImage specific tests in ItKubernetesEvents.java

Can u add a test case for the JIRA [OWLS-94649 ( Domain Status should report error when there is problem pulling auxiliary image )

Is this specific to AI 4.0? If not, it can go in different IT class in separate PR.

This is not specific to 4.0 but since the test case deals with AuxImages I want to add a Even usecase specific to AuxImage. I do not see any AuxImage specific tests in ItKubernetesEvents.java

Thanks for clarifying, as it is specific to 4.0, will add in the same IT class in next PR.

Added a separate JIRA to track the effort.


Add "read" example from API documentation

This PR adds the usage example from https://github.com/mitsuhiko/rust-sourcemap/blob/fa7065ab3529c646979ab0c39d3d655dd943cd8c/src/lib.rs#L26-L39 as a runnable example binary (cargo run --example read <path> [line=0] [column=0])

@mitsuhiko any comments?

Looks good!


Wrong overlap between lfw and webface

In FaceDatasets/CASIA/webface_lfw_overlap_detail.txt Michael B. Jordan (actor, from webface) and Michael Jordan (basketball player, from lfw) marked as the same person while they are not.

Richard A. Cohen from webface also not Richard Cohen from lfw


Update .openpublishing.publish.config.json

@jdanyow,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@jdanyow  merged

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


fix: pass usedSimps argument

It's slightly awkward to write a test for this: simp? is in Std, which is how this should really be tested. I can add a test that uses the plumbing functions if desired.

There is an alternate syntax for simp? which is to set set_option tactic.simp.trace true. I think there is a test file for this?

tactic.simp.trace

I've added a test to tests/lean/simp_trace.lean.

CI is not green.


[ts-4023] cachekey plugin

This plugin allows some common cache key manipulations based on various HTTP request elements. It can

sort query parameters so reordering can be a cache hit
ignore specific query parameters from the cache key by name or regular expression
ignore all query parameters from the cache key
only use specific query parameters in the cache key by name or regular expression
include headers or cookies by name
capture values from the User-Agent header.
classify request using User-Agent and a list of regular expressions

I'm going to land this, unless there are other review concerns. (Gancho fixed a few number of issues that was reported outside of this PR already).


Demo-Server need to be more robust and reliable

The two demo instances of the koalixcrm do not really work reliable.

User gets bad impression about the quality of the software
Guest password reset.
Time-consuming installation is very often not properly done

The improved demo instance should work in a a docker container and should be set up with initial data so that guest user are not annoyed by set-up issues like: Missing tempaltesets, missing currency, wrong setting of the accounting period and so on.

seams like the demo is offline.


Flipping doesnt work

When I flip animation (changing AtlasExample/0.scml x-direction), pieces goes wrong places.
Test:
Added
if (IsPressed(Keys.Tab)) currentAnimator.Scale = new Vector2(-1f, 1f);
to SpriterGameState.cs.

That's in the feature/texture-atlas branch, right? It's still work in progress. The develop branch should be working fine (without texture atlases though). Thanks for reporting - I wasn't aware of this.

Yes, feature/texture-atlas branch.

Fixed with the latest commit on feature/texture-atlas


Release v6.0.2 lacework-agent Helm Charts

Signed-off-by: nschmeller<EMAIL_ADDRESS>

should be no changes to daemonset or schema


Clarify architecture

The components were given a clear area of responsibility.
Now you don't have to think about what to put in what component.
Less likely to make a mistake.

Project Dependency Diagram:

Projects hierarchy in Solution Explorer:

@iammukeshm ready for review.

Hi, I am not actually thrilled with this extend of project separation. It May not be preferred by most of the developers. The idea was to keep the project clean, yet very simple. However, I will take some time and look into it.

Hi @iammukeshm
In fact, the project remains as simple and clean. Only visually it seems that it has become more complicated, as the number of projects in the solution has increased.
However, this approach has several advantages:

First, we have a clear atomic separation of contexts and components, and there is no need to think about where to put them when adding new functionality or new components.
Secondly, the area of responsibility of each component is more clearly defined due to the fact that, for example, any service implementation refers only to its own interface (there are no references to a common project with all interfaces). That is, it is more difficult to make an error in the code (call the wrong method, etc.).
Thirdly, when developing different teams of different services, there is no need to change the code in one project - all services are separated at the project level. Accordingly, it is easier to merge changes into a common branch for several teams.
Fourthly, on the contrary, it is easier for developers to familiarize themselves with such a solution structure, since it is more atomic and the classes are located in those components where they are guaranteed to be used.

I agree with your points. My main concern is that following this structure, adding new features would be an issue visually, as devs would have to ideally follow the same structure for adding new features and services. This would become a nightmare in complete applications. RoleService / ExcelService and so on... But that's my first thought only. will check

The only difference is that instead of adding a new service class within one project, a new project will be added for a new service.
In addition, I don’t think that in most real projects the number of such services is more than a ten :)
For me, for example, it is easier to visually abstract from other services in a separate project, without fear of influencing other services with my changes, as if they were in the same project.
You can additionally group services in your layers by different directories. Visually, this will be almost no different from how it is done now.

Well, in conclusion, we can use the ability to unload individual projects from the solution, which we do not need for the current development (when developing for different hosts - web or mobile or another, - that use different components). Visual Studio allows us to do this. When placing all services in one project, this will not work :)

Hi, @iammukeshm
What do you think ultimately about such a pure architecture implementation?

I would tend to agree with @iammukeshm in that this would not be preferred by most developers.  I would expect many developers looking for a clean architecture approach to Blazor would have some experience with the eShopOnWeb solution and the Jason Taylor Clean Architecture solution.  This repo is currently very similar to those, allowing a lot of knowledge and comfort transition.

This is an interesting comment.  When I first saw this repo I was looking at adding Blazor to the Jason Taylor solution which I have used before.  What was the inspiration for starting fresh and not just building on top of Jason work?
From: Scott Kuhl @.>
Sent: Sunday, 16 May 2021 9:05 AM
To: blazorhero/CleanArchitecture @.>
Cc: Subscribed @.***>
Subject: Re: [blazorhero/CleanArchitecture] Clarify architecture (#76)
I would tend to agree with @iammukeshmhttps://github.com/iammukeshm in that this would not be preferred by most developers. I would expect many developers looking for a clean architecture approach to Blazor would have some experience with the eShopOnWebhttps://github.com/dotnet-architecture/eShopOnWeb solution and the Jason Taylor Clean Architecturehttps://github.com/jasontaylordev/CleanArchitecture solution. This repo is currently very similar to those, allowing a lot of knowledge and comfort transition.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/blazorhero/CleanArchitecture/pull/76#issuecomment-841737115, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACCK53WQSDK3NEB472353XLTN34ZBANCNFSM43LHX7RA.

I would tend to agree with @iammukeshm in that this would not be preferred by most developers. I would expect many developers looking for a clean architecture approach to Blazor would have some experience with the eShopOnWeb solution and the Jason Taylor Clean Architecture solution. This repo is currently very similar to those, allowing a lot of knowledge and comfort transition.

I understand your position, and I partially agree with it.
However, there are many arguments in favor of the approach I propose, which I mentioned above.
In the Russian-speaking community, there are specialists Andrei Tsvettsikh and Denis Tsvettsikh who speak at the largest .net conference - dotnext (and more other conferences) and show (video 1, video 2) the flaws of Jason Taylor's architecture.
Unfortunately, videos with their reports exist only in Russian, but I fully support their point of view.
And not always following the already existing project structure (as in the repositories from Jason Taylor or eShopOnWeb) is right.
Sometimes it is useful to break existing approaches in order to grow)

@unchase  Could you elaborate or show the practical solution being used for this kind of separation. There is no right or wrong for the pattern the code structure. It's just who uses it for which purpose.
I personally separate only for 4 projects - API, Application, Persistence and Client.  This is good enough for most purposes. The atomic separation of your seems nightmare at first, but it may be very useful for enterprise application like - Facebook , Google.
Might be there is should be option.

@chhinsras You can use this separation in any enterprise project. I gave its advantages earlier, they are valid for any solution.
Since such an architecture is universal for an application of any complexity, when switching to another project with such an architecture, it is easier for a programmer to adapt.

Since such an architecture is universal for an application of any complexity

This is the one part I would disagree with.  The proposed changes would be overkill for small to medium complexity applications.  However, this entire solution could be argued to be too complex for small applications anyway.
I guess my final thought on this can be summed up like this, if these changes would be made:
1 - I would probably not use this template.
2 - I would not recommend this template to students at our code school for their final projects because it is too different than what they are likely to run into on the job.
3 - Other developers first seeing the repo may be instantly turned off by the number of projects without even giving it a chance.
Perhaps it's better to create a fork of this repo with your proposed changes and see how the adoption rate grows?
Either way, it's an interesting change, and I appreciate the effort to make things better.  It may actually make things more usable in very large projects with multiple bounded contexts split into separate assemblies.  I think that may be the most viable target audience.  But at that point you also start to slip into micro-services and serverless as a better option.
🤷♂

Since such an architecture is universal for an application of any complexity

This is the one part I would disagree with.  The proposed changes would be overkill for small to medium complexity applications.  However, this entire solution could be argued to be too complex for small applications anyway.
I guess my final thought on this can be summed up like this:
1 - If these changes would be made, I would probably not use this template.
2 - If these changes would be made, I would definitely not recommend this template to students at our code school for their final projects because it is too different than what they are likely to run into on the job.
Perhaps it's better to create a fork of this repo with your proposed changes and see how the adoption rate grows?
Either way, it's an interesting change, and I appreciate the effort to make things better.

I do not mean to offend any one. I personally build few projects without any separation. Using only MVC pattern. This is kinda obsolete but, yes, it is depend on the project itself.
Somehow, having 3 separated projects should be okay for most case (API, Application, Client).


Should ** be a synonym for //?

This seems to be a popular syntax for some other tools, I think, and removes the UNC path issues with construction. I could support both, but document and example with ** if we do decide to support both.

Yes, please!

@kaoskorobase - can you point at an existing system that does this? Ideally many systems implementing it? I'm keen to follow something standard rather than reinventing my own syntax, if possible (within compatibility constraints). I could Google, but don't really know who is the standard and who are imitators which might get it a bit wrong :)

Hmm, here are the ones I know from the top of my head:

rsync
ant
gradle
Jenkins (most if not all plugins use that syntax)

And found by Google:

FishEye (same as ant)

Great, so rsync treats it as a regular expression, but everything else treats it as a special directory, so I'll follow that.

This is now supported. I'm going to wait from feedback from someone using it in anger before I convert the documentation over to make it the default and recommended way.

I'm going to wait from feedback from someone using it in anger

??

I've implemented it. I've tested it. However, no one has used it in a real project for real purposes yet. I'll wait until someone says they have, and that it worked, before I convert all the docs and recommendations over. I think it should be fine, but various weaknesses of // as a wildcard only became apparent after using it for real.

Thanks, we'll port our build systems over to the new syntax and report back.

As soon as the feature is released and in stackage LTS, that is :)

An unhealthy incentive for me to avoid bumping the middle version digit :) - thanks for offering to test though, I hope to release in a week or so, perhaps two.

I ran into a bug: #376

Things to do after please have had experience with it:

Update the manual and docs to always use **
Update the docs to discourage //


Sync of GitHub repositories within 2024.09.16-22

The aim is to synchronize GitHub repositories in the given period.

Two sync were done during given period


(Bug Bash) Android Issues

Not sure how much (if any) we want to fix, but documented for posterity:
Android 4.1.1 on a Huawei Prism II smart phone.
With the default web browser
The min-width: 400px design doesn't fit on the screen

In additions, the .woff format icon font is not supported

And the site is basically not navigable

With Firefox 34.0
The min-width: 400px design doesn't fit on the screen

However, all other functionality seems to work okay.
With Chrome 39.0.2171.93
Everything works as expected

Moving to the technical backlog as this won't be an immediate priority


Support Data Wrangler

Adding Fortescue Future Industries to the support list. Keep up the great work team!

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: ebbf365e8c367ad1871c28fbf0097a3cc19a6a47
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Feature Request: Chocobo Stable

It would be nice if you could add the a timmer for trainnig Chocobo.
If possible for your own and from your Free Company.

I would love this as well. There seems to be a timer for the chocobo owner and one for others to feed.


Add WaterfallDialog StartEvent for VA

Add support for WaterfallStart event.
Also:

Support multiple Application Insights configs within BotConfig
Include BotTelemetryClient tests

Pull Request Test Coverage Report for Build 44562

0 of 0   changed or added relevant lines in 0 files are covered.
22 unchanged lines in 3 files lost coverage.
Overall coverage increased (+0.1%) to 55.543%

Files with Coverage Reduction
New Missed Lines
%

/libraries/integration/Microsoft.Bot.Builder.ApplicationInsights.WebApi/TelemetryBotIdInitializer.cs
6
64.91%

/libraries/integration/Microsoft.Bot.Builder.ApplicationInsights.Core/ServiceCollectionExtensions.cs
7
85.11%

/libraries/Microsoft.Bot.Builder.Dialogs/WaterfallDialog.cs
9
89.91%

Totals

Change from base Build 44481:
0.1%

Covered Lines:
5411

Relevant Lines:
9742

💛  - Coveralls


[FEA] commonize the version checking in the integration tests

Is your feature request related to a problem? Please describe.
currently we have a couple ways to checks versions.

--runtime-env option
is_spark_300 and is_before_spark_310  in spark_session.py

I think we could get rid of both of those and use the shim layer versioning checks like we do in the unit tests.  We should investigate and try to make things common.

this is a nice to have, in some ways the runtime-env is easier so just closing this for now and we can reopen if it becomes an issue


White Stripe Basculin won't evolve after I made it take 450 recoil in one life.

IGN: StepSisTsunade
Server: Orion
Ive been trying to train this basculin's recoil for 45 mins, through trial and error and it fainting. and I finally made it stay alive long enough to go well over the evolve conditions. Was wondering if It could get force evo'd into basculegion.

If you can't replicate this in Singleplayer, we will look into the issue and fix it for you. If this happens in SP, please report it to Pixelmon and await a fix from them.
Reopen if you can't replicate in SP please.


Upgrade ReScript to v11

See the post for more details about the upcoming ReScript 11.

Closing this PR in favor of #22


Origin Custom Headers Support

I'm using this component for hosting a CF distribution that includes Appsync as an /graphql origin. Adding this feature will help me not having to have the x-api-key on the client itself.

Just a heads-up that you ended up committing the yarn.lock file by mistake.

Thanks for the heads up, I removed the file :)


[OAP-2041][oap-native-sql] skip null checking if allowed

What changes were proposed in this pull request?
when joining, we could skip the if_is_null checking if the whole batch didn't contain null
How was this patch tested?
locally verified on TPC-H/TPC-DS

notes: the CI failures are not related


Fix training mode outputs for roberta and distilbert mlm models

What does this PR do?

In training mode for MLM models we don't want to return the logits for performance.
Distilbert and Roberta were only checking for if labels is None, but this meant that in evaluation the training path was being taken. Fix this by checking instead for if self.training.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Cannot connect to server using SSL via PHP Client

I created key<==>crt pair usiing openssl
 openssl req -newkey rsa:2048 -nodes -keyout keys/app.key -x509 -days 365 -out keys/app.crt

On gRPC Server, I'm using go.
The server is running fine with the key files. And I can connect gRPC server using GRPCUI using insecure mode..
To test thhe client, I copied the crt file to php client and tried to send request to server as follow:
<?php

use App\Calculator\CalculatorClient;

require 'vendor/autoload.php';

$client = new CalculatorClient(
    'localhost:50051',
    [
        'credentials' => \Grpc\ChannelCredentials::createSsl(file_get_contents('app.crt')),
    ]
);
$i = 2;
$sum = new \App\Calculator\Sum([
    'a' => $i,
    'b' => $i + 1
]);
[$result, $mt] = $client->Sum($sum)->wait();
var_dump($mt);

But I'm getting following error:
failed to connect to all addresses
Here i'm using gRPC 1.27 as PHP Extension on Ubuntu 18.04.
What am I missing with PHP Client? Or it's some kind of bug

Not clear what the problem is from the error message, but I was thinking: does your certificate match your actual hostname? In addition to the credentials key, which you supplied correctly, you may have to supply the grpc.ssl_target_name_override key and provide the hostname that you are trying to connect to.

How would I put above keys: grpc.ssl_target_name_override and the grpc.default_authority in PHP as the PHP Client has following parameters
new Client($host, $options, $channel = null)

Those would be part of the $options parameter:
$client = new CalculatorClient(
    'localhost:50051',
    [
        'credentials' => \Grpc\ChannelCredentials::createSsl(file_get_contents('app.crt')),
        'grpc.ssl_target_name_override' => '<your value>',
        'grpc.default_authority' => '<your value>'
    ]
);


Feature: Casbin Deny Support Scripts

🔖 Feature description
Casbin Deny Support Scripts
🎤 Pitch / Usecases
Casbin Deny Support Scripts
🔄 Alternative
Casbin Deny Support Scripts
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Fixed with attached PR


feat(demo): aggregations and filters for search

Description

Changes how the filters work on the Search page
Add new Aggregations for the count to the Search page
Adds the count from the aggregations to properties or manufacturers in Template
Use filter instead of "global" properties and manufacturer (aggregations are now updated)
If you have properties or manufacturers in the URL the filters are opened automatically

Type of change
New feature (non-breaking change which adds functionality)
ToDo's

[ ] Clean up and remove the functions from the search
[ ] Integrate the same logic into category
[ ] Create new e2e tests for all the new features

Additional context
Sometimes the count does not match the products the customer sees.
Currently, we have a problem getting the aggregations into CMSPage listing elements. :warning:

Re-build and use also:
reduce-aggregations Parameter (so we can stick to the old filter logic).
Example criteria to fix counting childs problem:
{
    "search": "sal",
    "filter": [
        {
            "type": "equalsAny",
            "field": "optionIds",
            "value": "05e49d0296ea49d99ad6a031e3a5581a"
        }
    ],
    "aggregations": [
        {
            "name": "option_ids_counter",
            "type": "terms",
            "field": "optionIds"
        },
        {
            "name": "filter-aggregation-for-option",
            "type": "filter",
            "filter": [
                {
                    "type": "equalsAny",
                    "field": "optionIds",
                    "value": "05e49d0296ea49d99ad6a031e3a5581a"
                }
            ],
            "aggregation": {
                "name": "product-found-counter",
                "type": "count",
                "field": "product.id"
            }
        },
        {
            "name": "filter-aggregation-manufacturer",
            "type": "filter",
            "filter": [
                {
                    "type": "equals",
                    "field": "manufacturerId",
                    "value": null
                }
            ],
            "aggregation": {
                "name": "product-found-counter-for-manufacturer",
                "type": "count",
                "field": "product.id"
            }
        }
    ]
}

Closed. See https://github.com/shopware/frontends/pull/642


Fix logger factory logger

Fixes #78
Changes
This changes the API used to configure loggers for Akka.Hosting, we will need to deprecate the previous nuget release.
With the new API, you use the ConfigureLoggers(Action<LoggerSetup>) extension method to configure the Akka.NET logging system. The new API is a lot more flexible compared to the previous one and should be compatible with our other logger plug-ins.
builder.Services.AddAkka("MyActorSystem", configurationBuilder =>
{
    configurationBuilder
        .ConfigureLoggers(setup =>
        {
            // Example: This sets the minimum log level
            setup.LogLevel = LogLevel.DebugLevel;

            // Example: Clear all loggers
            setup.ClearLoggers();

            // Example: Add the default logger
            // NOTE: You can also use setup.AddLogger<DefaultLogger>();
            setup.AddDefaultLogger();

            // Example: Add the ILoggerFactory logger
            // NOTE:
            //   - You can also use setup.AddLogger<LoggerFactoryLogger>();
            //   - To use a specific ILoggerFactory instance, you can use setup.AddLoggerFactory(myILoggerFactory);
            setup.AddLoggerFactory();
        })
        .WithActors((system, registry) =>
        {
            var echo = system.ActorOf(act =>
            {
                act.ReceiveAny((o, context) =>
                {
                    Logging.GetLogger(context.System, "echo").Info($"Actor received {o}");
                    context.Sender.Tell($"{context.Self} rcv {o}");
                });
            }, "echo");
            registry.TryRegister<Echo>(echo); // register for DI
        });
});

The reflection magic is needed for the LoggerFactoryLogger to support the .AddLogger<LoggerFactoryLogger>() feature, are we sure we want to remove that?

The reflection magic is needed for the LoggerFactoryLogger to support the .AddLogger<LoggerFactoryLogger>() syntax, are we sure we want to remove that?

Added test coverage to see if this was a problem and then added a check into the AkkaConfigurationBuilder to automatically include any dependencies it needs.

Simplified the internals of the LoggingFactoryLogger so it only creates a single ILogger<ActorSystem> instance. The output logs look like this:
[Information] [22/07/21-15:15:26.9254][ActorSystem(MySys)][akka://test/system/testActor1][0023]: foo

LGTM, merging


database update not working

On some machines "dnx ef databae update" does not working, if database does not exists.
Should it be a security problem?
No error message occurs.

@marcels2204 there isn't much we can do with this issue without some more details to help us reproduce the problem. It could be a permissions issue, the credentials used to connect would need permissions on master database to create databases.


The right to get shares of the company I buy from.

I have some thoughts around this that I did not formalize yet and maybe it doesnt make sense at all.
The core of it means basically, that every customer should have the right to buy a small micro-amount of shares from the company that was being paid during a sale. Companies can offer an immediate buy-back option if they want to, but the customer has the right, even the duty if that buy-back-option is not taken, to receive shares from the company.
The benefit I'm hoping for is, that if it should ever happen, that a single company gets some kind of monopoly that locks a certain resource and starts abusing its power, customers can slowly buy up all the shares and then use their gained voting power to restructure the company.

For now, this is not an interesting idea, because the infrastructure to handle that kind of micro-shares and a market to trade those does not exist yet - it has to be created first, so this idea probably has to rest for a very long time.

If somebody reads this and knows some links or projects or whatever, that has similar ideas, please feel free to share the links, so the process of developing this idea can be speeded up :-)

related: https://wiki.p2pfoundation.net/Capped_Returns

"Taxemes"
var people = {
  P: { myRate: 40, taxemes: {
    Q:[{r:20,v:100}],R:[{}],S:[{}],T:[{}],U:[{}],V:[{}],W:[{}]
  }, antitaxemes: {
    Q:[{r:20,v:100}],R:[{}],S:[{}],T:[{}],U:[{}],V:[{}],W:[{}]
  } },
  Q: { myRate: 40, taxemes: {
    Q:[{r:20,v:100}],R:[{}],S:[{}],T:[{}],U:[{}],V:[{}],W:[{}]
  }, antitaxemes: {
    Q:[{r:20,v:100}],R:[{}],S:[{}],T:[{}],U:[{}],V:[{}],W:[{}]
  } },
  R: { myRate: 40, taxemes: {
    Q:[{r:20,v:100}],R:[{}],S:[{}],T:[{}],U:[{}],V:[{}],W:[{}]
  }, antitaxemes: {
    Q:[{r:20,v:100}],R:[{}],S:[{}],T:[{}],U:[{}],V:[{}],W:[{}]
  } },
  S: { myRate: 40, taxemes: {
    Q:[{r:20,v:100}],R:[{}],S:[{}],T:[{}],U:[{}],V:[{}],W:[{}]
  }, antitaxemes: {
    Q:[{r:20,v:100}],R:[{}],S:[{}],T:[{}],U:[{}],V:[{}],W:[{}]
  } },
  T: { myRate: 40, taxemes: {
    Q:[{r:20,v:100}],R:[{}],S:[{}],T:[{}],U:[{}],V:[{}],W:[{}]
  }, antitaxemes: {
    Q:[{r:20,v:100}],R:[{}],S:[{}],T:[{}],U:[{}],V:[{}],W:[{}]
  } },
  V: { myRate: 40, taxemes: {
    Q:[{r:20,v:100}],R:[{}],S:[{}],T:[{}],U:[{}],V:[{}],W:[{}]
  }, antitaxemes: {
    Q:[{r:20,v:100}],R:[{}],S:[{}],T:[{}],U:[{}],V:[{}],W:[{}]
  } },
  W: { myRate: 40, taxemes: {
    Q:[{r:20,v:100}],R:[{}],S:[{}],T:[{}],U:[{}],V:[{}],W:[{}]
  }, antitaxemes: {
    Q:[{r:20,v:100}],R:[{}],S:[{}],T:[{}],U:[{}],V:[{}],W:[{}]
  } }
}


Develop a tutorial about how to develop networks based on MONAI APIs

Is your feature request related to a problem? Please describe.
We have very rich network layers, blocks, etc. and support both 2D and 3D, we also have layer factory to generate common layers. But currently, we don't have a step by step tutorial to show how to use the APIs to develop networks.

addressed by https://github.com/Project-MONAI/MONAIBootcamp2020/blob/master/day1notebooks/lab3_networks.ipynb

addressed by https://github.com/Project-MONAI/MONAIBootcamp2020/blob/master/day1notebooks/lab3_networks.ipynb