Add unit tests

Resolve #19

thanks heaps for this PR, hopefully I'll have some time soon to check out what is going on in appVeyor

MSBuild auto-detection: using msbuild version '<IP_ADDRESS>4' from 'C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\bin'.
nuget : C:\Program Files\dotnet\sdk\2.2.109\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.TargetFrameworkInference.targets(137,5): error NETSDK1045: The current .NET SDK does not support targeting .NET Core 3.0.  Either target
.NET Core 2.2 or lower, or use a version of the .NET SDK that supports .NET Core 3.0. [C:\projects\fastexcel-43v9o\FastExcel.Tests\FastExcel.Tests.csproj]

Need to change image on Visual Studio 2019

@rstm-sf I have fixed the build, it also released to nuget... i better do some work to stop that on open PRs

@mrjono1 thanks for watching!
Regarding PR, I'm sorry, I had little time for finish. I think that in the near future I will be able to add new tests if I figure out what can be added. Or I just open PR if I can’t figure out what can be added

I could not figure out how to reproduce the remaining cases

Thankyou again ill review this soon


⚠ ClamAV has degraded performance

In 3226614, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 89 ms

Resolved: ClamAV performance has improved in 6206748.


calling contextsRequest

What is passed into the contexts parameter when calling contextsRequest?
https://github.com/api-ai/api-ai-node-js/blob/823c79cff1efcfec4edf620019f636b44e91826d/module/apiai.js#L121
I want to get back all the current contexts for a session

disregard, I see that this is to add (POST) contexts, not to get.

please publish it on npm :D


Update PHE importers

PHE do not support their API anymore and the files have changed format and content. Need to update the importers for both adult and childhood obesity.

Closing as solved in #477 and #484.


Core updates to Instagram4j

This PR updates some core features of Instagram4j.
Updated:

Photo Upload to use Resumable Photo upload endpoint
Video Upload to use Resumable Video upload endpoint
Album Upload to upload both photo and video
Instagram constants
Timeline request (with pagination)

Some notable remarks:

Default Headers are now applied to all request (by InstagramRequest.applyHeaders())
Pre and Post login are requests are now in separate methods (can be called before and after login request)

Closes #393 #354

Would be awesome if you could review and merge this @brunocvcunha 😃
Just wanted to remind you in case you missed it because I know you're very busy!
Much appreciated!

Thanks @jvogit


A-Z material list

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


HFSS plugin

We already have a couple of Ansys plugins. How could we add RF design specific plugin using HFSS?
some examples:

https://github.com/PhilReinhold/pyHFSS
https://github.com/qiskit-community/qiskit-metal/tree/main/qiskit_metal/renderers/renderer_ansys

@nikosavola
@zlatko-minev
@jagandecapri

I think Ansys recommends this library nowadays https://github.com/ansys/pyaedt. Qiskit Metal uses pyEPR as a backend, which is very focused on superconducting qubits, maybe pyaedt could be mroe general?

we should move it to the gdsfactory plugins repo


Cannot derive StateMachine for public struct

error[E0446]: private type `CharacterTransform` in public interface
 --> state/src/character.rs:4:10
  |
4 | #[derive(StateMachine, Clone, Debug, Serialize, Deserialize, PartialEq)]
  |          ^^^^^^^^^^^^
  |          |
  |          can't leak private type
  |          `CharacterTransform` declared as private
  |
  = note: this error originates in the derive macro `StateMachine` (in Nightly builds, run with -Z macro-backtrace for more info)

Solved by #24

Excellent, thanks for confirming! I will merge now.


Polaroid effect

Hi!! I added polaroid effect when hovering over pics. :D I hope you like it!!

Hi!! Sorry!! First time on Git. Thank you for your suggest :D


Dropdown menu doesn't hide after selecting an option.

Describe the bug
The dropdown menu does not hide after selecting an option.
To Reproduce
Make a dropdown with options. Minimal example script:
import pygame
import pygame_gui
pygame.init()
screens = {}
guiManager = pygame_gui.UIManager((630, 656))
screens[0] = pygame.display.set_mode((630, 656))
screens[0].fill("gray")

screens[1] = pygame.Surface((256, 256))
screens[1].fill("black")

fileDropdown = pygame_gui.elements.UIDropDownMenu(relative_rect=pygame.Rect((0, 0), (100, 50)),
                                        options_list=["Open", "Save", "Save As", "Export", "Import"],
                                        starting_option="Open",
                                         manager=guiManager)

clock = pygame.time.Clock()
running = True

while running:
    time_delta = clock.tick(60)/1000.0
    # Handling events
    for event in pygame.event.get():
        if event.type == pygame.QUIT:
            running = False

        if event.type == pygame_gui.UI_DROP_DOWN_MENU_CHANGED:
            if event.ui_element == fileDropdown:
                print(f"Selected: {event.ui_element.selected_option}")

        guiManager.process_events(event)

    guiManager.draw_ui(screens[0])
    screens[0].blit(screens[1], (128, 128) )
    guiManager.update(time_delta)
    pygame.display.flip()

Expected behaviour
It should hide the dropdown after an option is selected?
Screenshots

OS: [Windows]
Pygame GUI version [0.6.9]
Pygame version [2.4.1]

Additional context
I am trying to make a level editor GUI in pygame, and I need to use pygame_gui for the buttons.

Hi there!
You aren't clearing your main screen surface back to gray each loop, so it will still have whatever you drew on it the previous frame. Luckily this is an easy fix:
import pygame
import pygame_gui

pygame.init()
screens = {}
guiManager = pygame_gui.UIManager((630, 656))
screens[0] = pygame.display.set_mode((630, 656))
screens[0].fill("gray")

screens[1] = pygame.Surface((256, 256))
screens[1].fill("black")

fileDropdown = pygame_gui.elements.UIDropDownMenu(
    relative_rect=pygame.Rect((0, 0), (100, 50)),
    options_list=["Open", "Save", "Save As", "Export", "Import"],
    starting_option="Open",
    manager=guiManager,
)

clock = pygame.time.Clock()
running = True

while running:
    time_delta = clock.tick(60) / 1000.0
    # Handling events
    for event in pygame.event.get():
        if event.type == pygame.QUIT:
            running = False

        if event.type == pygame_gui.UI_DROP_DOWN_MENU_CHANGED:
            if event.ui_element == fileDropdown:
                print(f"Selected: {event.ui_element.selected_option}")

        guiManager.process_events(event)

    screens[0].fill("gray")
    guiManager.draw_ui(screens[0])
    screens[0].blit(screens[1], (128, 128))
    guiManager.update(time_delta)
    pygame.display.flip()


Count added waypoints as "nearest"

When adding a new waypoint, it's not included in the list of waypoints used for checking the nearest botzone, should probably include them

This would actually be a pain to fix, I'd have to either call protected method in BotSpawnerClass (method_1), or re-build a protected dictionary in the same class. I'm not sure if either is really worth it now that you can pick the botzone


Surveys have legacy references

Looks like we forgot to update some of these :P
[17/Feb/2019 05:04] ERROR [django.request:228] Internal Server Error: /engagement/surveys/view/all/
Traceback (most recent call last):
  File "/home/auth/production/kryptedauth/myvenv/lib/python3.5/site-packages/django/core/handlers/exception.py", line 34, in inner
    response = get_response(request)
  File "/home/auth/production/kryptedauth/myvenv/lib/python3.5/site-packages/django/core/handlers/base.py", line 126, in _get_response
    response = self.process_exception_by_middleware(e, request)
  File "/home/auth/production/kryptedauth/myvenv/lib/python3.5/site-packages/django/core/handlers/base.py", line 124, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/home/auth/production/kryptedauth/myvenv/lib/python3.5/site-packages/django/contrib/auth/decorators.py", line 21, in _wrapped_view
    return view_func(request, *args, **kwargs)
  File "/home/auth/production/kryptedauth/myvenv/lib/python3.5/site-packages/django/contrib/auth/decorators.py", line 21, in _wrapped_view
    return view_func(request, *args, **kwargs)
  File "/home/auth/production/kryptedauth/app/modules/engagement/views/surveys.py", line 16, in dashboard
    guilds = set([survey.guild for survey in surveys if survey is not None])
  File "/home/auth/production/kryptedauth/app/modules/engagement/views/surveys.py", line 16, in <listcomp>
    guilds = set([survey.guild for survey in surveys if survey is not None])
AttributeError: 'Survey' object has no attribute 'guild'

This goes a little deeper, surveys need to be attached to a group on the model instead of a guild since we are no longer doing dependencies on external modules, e.g
group = models.ForeignKey(Group, on_delete=models.CASCADE, blank=True, null=True)

Whoops I already did that in migration :P


Extension is not working, displaying some warning

The settings of extension<EMAIL_ADDRESS>had an error:
SyntaxError: import declarations may only appear at top level of a module

Stack trace:
@file:///home/kali/.local/share/gnome-shell/extensions/network-stats@gnome.noroadsleft.xyz/prefs.js:8:12
_init/GLib.MainLoop.prototype.runAsync/</<@resource:///org/gnome/gjs/modules/core/overrides/GLib.js:266:34

Looks like you are on new version of gnome probably gnome >= 45.
It should be fixed with https://github.com/noroadsleft000/gnome-network-stats/issues/59


Add stack information when stack_info is set in logging integration.

Problem Statement
The stack information should be added to events send with the logging integration when stack_info=True is set.
Code like this should have a stack attached in the resulting event in Sentry:
logger.error(
    "Option %s set to %s. previous update channel: %s",
    key,
    value,
    channel,
    stack_info=True,
)

Solution Brainstorm
Check for the parameter in logging integration and add the stack information if parameter is True.

Some info from @untitaker :
exc_info=True should send the stack
specifically, it sends the current stack if sys.exc_info is None, otherwise it sends the current exc info
stack_info appears to be new in 3.2, we made the api design decisions with py2 in mind at the time

Hello @antonpirker,
Sentry's support just informed me that the stack trace is critical during the auto assignment of one event to the correct team as the path type rule is matched against all file paths of the stack.
Therefore I do have a lot of interest in resolving this issue. I did some research and I believe this is the method in need of modification. Any other places or any recommendation you find useful ?


Add snapshot callback on Journal exaustion

Add hook for taking snapshot of service data when journal has reached its maximum size and restart a clean journal

Added callback handler when journal has reached its maximum size, still missing handler taking snapshot of service data on callback activation

Added snapshot saving on journal depletion callback activation


Do not allow surrounding spaces to be counted as part of ${number} templates in template index strings

Suggestion

🔍 Search Terms

Template String Pattern Index Signatures
Template Index Strings
✅ Viability Checklist

My suggestion meets these guidelines:

[ ] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

Actually it would change the typescript behavior as it was released - maybe better now than later?
The current behavior might be more bug than feature.
⭐ Suggestion
Not allowing spaces would reduce typing mistakes.

📃 Motivating Example
Modification of the example feature explanation in  the handbook:
interface Options {
    width?: number;
    height?: number;
}

let a: Options = {
    width: 100,
    height: 100,
    "data-1": true, // Error! 'data-blah' wasn't declared in 'Options'.
};

interface OptionsWithDataProps extends Options {
    // Permit any property matching 'data-${number}'.
    [optName: `data-${number}`]: unknown;
}

let b: OptionsWithDataProps = {
    width: 100,
    height: 100,
    "data-1": true,       // Works!
    "data- 1": true,       // Passes but might be better off failing
    "data-1 ": true,       // Passes but might be better off failing
    "data- 1 ": true,       // Passes but might be better off failing
    "data- ": true,       // Passes but might be better off failing  (no number at all)

    "unknown-property": true,  // Error! 'unknown-property' wasn't declared in 'OptionsWithDataProps'.
};

playground
💻 Use Cases
Using it to catch unintended key entries.

Can be simplified to
const a: `data-${number}` = "data-1"; // OK

// No errors
const a1: `data-${number}` = "data- 1";
const a2: `data-${number}` = "data-1 ";
const a3: `data-${number}` = "data- 1 ";
const a4: `data-${number}` = "data- ";

Oh wow this an even better example for my list of surprising behaviors of `${number}`!  I'm still not quite able to internalize the interpretation of `${number}` meaning "some string that converts to a finite number",  but apparently that's what it means (as opposed to "the type of `${n}` when n is a finite number).

@jcalz - Thanks for link to <IP_ADDRESS>.2 Runtime Semantics: StringNumericValue, that is very informative.  So the behavior is intended to match some formal standard - as I suspected but wasn't sure.  (I also enjoyed you list of examples!)
For a user on the consuming end of the data, if they want to correctly decode the pattern suffix to disambiguate the many-to-one mapping of strings to numbers, they must use of algorithm listed in [<IP_ADDRESS>.2 Runtime Semantics: StringNumericValue].  I see that a possible source of confusion and errors.  That risk would be mitigated by employing a simple one-to-one mapping.
Having a many-to-one mapping of keys strings to semantic keys, before using the keys to lookup the value in the object map seems anti intuitive and error prone.  But the original problem lies in JS, not TS.
On the other hand, if TS is going to impose some strict typing on the keys for arbitrary integers, why not go the whole way and allow specification of a one-to-one map?   For an explicit limited range of integers it is already possible:
type CountingIntegers = "1"|"2";
type FooN = Record<`foo${CountingIntegers}`,any>

Maybe the feature request should be for a temple-key-string use specific intrinsic utility type "CountingIntegers" allowing all nonnegative integers up to Number.MAX_SAFE_INTEGER.  That is narrow enough to be safe and easy to implement, is extremely simple for a user to understand completely at a glance, and has practical value in eliminating misunderstandings.

Thanks to @jcalz pointing out  <IP_ADDRESS>.2 Runtime Semantics: StringNumericValue, it is now clear within a shadow of a doubt that the "surrounding space" behavior is "working as intended".  So I will close this issue.

I’m not sure… I’d really like to hear someone officially say that this is intentional.  I’m just an interested bystander.

Same here regarding whitespace.
While 100.1 or even 1e3 are really looking as number literals including whitespace doesn't look expected from usage perspective, but that's IMHO.

This is very surprising to me and seems undesirable, but I’ll let @ahejlsberg have the definitive word.

Yeah, we're basically just relying on JavaScript's intrinsic string-to-number conversion to validate `${number}` placeholder values--and it permits leading and trailing whitespace. Also, strangely, it permits empty strings and strings with only whitespace and returns 0 for those.
I agree it makes more sense to not permit any whitespace and in particular to not permit empty strings. It's technically a breaking change, but can't imagine many types depend on it.


should we feature flag counting subjects for users

@zwolf should we feature flag to avoid counting the subjects for users on login? We cache that value but a lot of people logging in may cause some heavy reads on the subject table. Thoughts?

My concern would be how PFE would handle that value being missing. If it would just drop the whole thing, that'd be fine, but I'm afraid it would choke on the nulls.

That value is only used in messaging to the user when they are uploading data in the lab and it's also used on the admin page. It's mostly used api side to allow subject creates to proceed.

closing this for now.


Use openssl-src from crates.io to link to OpenSSL

This commit updates the CI builds for rustup to always build
openssl-src from crates.io instead of having a baked-in build of
OpenSSL. This matches what Cargo has switched to as well, and is
intended to centralize OpenSSL updates to one crates.io crate.
This also modernizes the docker containers and builds a bit to remove
the need for some scripts here and there.

@bors: r+

:pushpin: Commit 4a4370afe3835a71e9a1927ed111b58150a6f982 has been approved by alexcrichton

:broken_heart: Test failed - status-travis

@bors: r+

:pushpin: Commit 0f95956af504a0390a6804063acef9824d57be0b has been approved by alexcrichton

:hourglass: Testing commit 0f95956af504a0390a6804063acef9824d57be0b with merge 3569540ff1a10812ef62b5869509e9e0ba26327c...

:broken_heart: Test failed - status-travis

@bors: r+

:pushpin: Commit a699b6d3e6e3901ed7e82f9b091eefaa5620280e has been approved by alexcrichton

:hourglass: Testing commit a699b6d3e6e3901ed7e82f9b091eefaa5620280e with merge 6ed41535562a3bce3fd4a47e294259ffa57aaa8f...

:boom: Test timed out

@bors: retry

:hourglass: Testing commit a699b6d3e6e3901ed7e82f9b091eefaa5620280e with merge a9f6ace1bee561610bf1d1586c27ff7779177311...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing a9f6ace1bee561610bf1d1586c27ff7779177311 to master...


How to toggle between 2 padding presets?

Ideally, i want to switch between 2 padding options. The first one is
yabai -m config top_padding    5
yabai -m config bottom_padding 5
yabai -m config left_padding   5
yabai -m config right_padding  5
yabai -m config window_gap     5

The second one is
yabai -m config top_padding    20
yabai -m config bottom_padding 20
yabai -m config left_padding   20
yabai -m config right_padding  20
yabai -m config window_gap     20

Normally, i leave all values at 20 for better looking. But when i need maximum amount of spaces, i leave them at 5. Right now i assign the second preset for space 1 only. I'd like a way to toggle between these two, rather than switch between spaces to experience different padding options.
i also could use these commands
yabai -m space --toggle padding
yabai -m space --toggle gap

but i would rather want to have 5px padding between windows than 0px.

Write a script that queries the current padding and just reassigns the values you want, then bind that script to execute when you press a key.
yabai -m config --space 1 top_padding will return the current top padding of space 1.
then something like the following logic to make a toggle..
if 20 then _padding 5 else _padding 20 where  in [ top, bottom, left, right ]

@koekeishiya Thanks for the idea! I haven't figured out the code yet but I really appreciate your answer. Might work this out soon.


Run 'docker exec mc-server mc-send-to-console' prompts 'Permission denied' on arm64

Describe the problem
It is normal to run docker exec mc-server mc-send-to-console tp @e 1 1 1 on windows wsl docker, but arm64 (Raspberry Pi 4B with ubuntu) prompts /usr/local/bin/mc-send-to-console: line 15: /tmp/minecraft-console-in: Permission denied.

This is most likely a permission problem. But it is a little weird:
root@c01c0cbb8b61:/tmp# ls -alsh minecraft-console-in
0 prw-rw-rw- 1 minecraft minecraft 0 Dec 17 09:56 minecraft-console-in

root@c01c0cbb8b61:/tmp# echo "say test" > minecraft-console-in
bash: minecraft-console-in: Permission denied

root@c01c0cbb8b61:/tmp# chown root:root minecraft-console-in
root@c01c0cbb8b61:/tmp# echo "say test" > minecraft-console-in
# The above works fine.

Oh, I see, the problem is that fs.protected_fifos=1 prevents any user (including root) from writing to a pipe not owned by said user.
commit
documentation

==============================================================
protected_fifos:
The intent of this protection is to avoid unintentional writes to
an attacker-controlled FIFO, where a program expected to create a regular
file.
When set to "0", writing to FIFOs is unrestricted.
When set to "1" don't allow O_CREAT open on FIFOs that we don't own
in world writable sticky directories, unless they are owned by the
owner of the directory.
When set to "2" it also applies to group writable sticky directories.
This protection is based on the restrictions in Openwall.

If we weren't in a docker container this would be as easy as doing sysctl fs.protected_fifos=0. However, that is disabled inside the container. I don't know what the best practice is in this case tbh. I'll leave this to someone else.

Can someone test out the image  itzg/minecraft-server:fix-1208? I haven't been able to recreate the issue myself.


Removed Hotkey tooltip info from backend config module

Description
Please describe your pull request:

Why is it necessary?
Hotkeys doesn't work
What does it improve?
Removes the hotkey info
Does it have side effects?
Nope

Questions
Answers

BC breaks?
no

Tests pass?
yes

Related tickets?

How to test?
Goto Grundeinstellungen => Shopeinstellungen => Kundengruppen and hover at "Hinzufügen" button

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-17955.
Please use this issue to track the state of your pull request.

thanks @shyim :+1:


Are there known issues with cloning pipelines?

I've tested cloning across a few different databases, all running the same pipeline activities, but with minor changes to the data sources and data sinks of a copy activity.  I've found intermittent and inconsistent errors when running these cloned pipelines, and the only way I was able to fix this was to create entirely new (not cloned) data sinks and/or entirely recreate pipelines.

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

ID: cf0ffffe-83ba-2c9e-bbc1-1f73d128ff0c
Version Independent ID: ede76f69-0388-5dbe-ac41-8aff949c84e1
Content: Copy or clone a data factory in Azure Data Factory
Content Source: articles/data-factory/copy-clone-data-factory.md
Service: data-factory
GitHub Login: @sharonlo101
Microsoft Alias: shlo

@AlexFiala Thanks for the feedback. We are investigating into the issue and will update you shortly.

@AlexFiala There are no known issues with cloning pipelines. Can you please share more details of what errors you get when you run the cloned pipelines? That would help us narrow down to the exact issue.

@AlexFiala There are no known issues with cloning pipelines. Can you please share more details of what errors you get when you run the cloned pipelines? That would help us narrow down to the exact issue.

Hey @ChiragMishra-MSFT, the behavior is as follows:
I created a working pipeline with an iterative copy activity that iterates through tables in a database and outputs those tables as CSV files within ADLS.  This pipeline includes two datasets, a source database and an ADLS sink.  This pipeline worked.
I had to replicate this exact same behavior for 4 other databases, so I cloned the database datasets and the ADLS sink datasets I used for the original pipeline.  I also cloned the pipelines themselves.  I then went through all relevant settings and parameters of the cloned pipelines and datasets, and updated them to reflect whatever the new database was.  When I did this, across 5 databases, the clone activity worked only sometimes, and the success of running the pipelines was inconsistent.  The below error was one of the errors I kept seeing when running a cloned pipeline:
ErrorCode=InvalidTemplate, ErrorMessage=The expression 'body('Copy DataComposeRuntimeVariables')?.3gTMS_StagingSinkae9c783bbc2f42b6ba7c712e329256e6.ADLSFile' is not valid: the string character 'g' at position '43' is not expected."
Eventually, I had to completely recreate all additional pipelines from scratch, including the datasets.
Is there a known issue with copy and pasting text into fields in the datasets and/or pipelines?  I suspect there is maybe an encoding issue or somehow copy/pasting text removes or adds escape characters somewhere...  I'm flying blind on my theories here.

@djpmsft Can you please have a look at this one ?

Hi there,
The engineering team is investigating this issue. I will update once I have the root cause or if we require more information.
Thanks,
Daniel

@AlexFiala The issue is your dataset name starts with numeric characters which is not allowed for parameterized datasets. Apologies for the cryptic error message (we are working on improving these).

#please-close

@AlexFiala The issue is your dataset name starts with numeric characters which is not allowed for parameterized datasets. Apologies for the cryptic error message (we are working on improving these).

Ah, thank you!  I did end up changing the dataset names to start with letters, and that resolved the issue.  Thanks dude!


Generate Signatures

Hi there! Not sure if I've missed something, but is there a plan to support generating/verifying JWT signatures with @oslojs/jwt? It appears that you can only parse the JWT, but not validate that the signature itself is correct.

I'm interested in the same question. It seems the old "general" repo (which is about to be deprecated) has a lot more: https://github.com/pilcrowOnPaper/oslo/blob/main/src/jwt/index.ts
Can we somehow help? 😺

Personally, I want to separate cryptographic operations (especially signatures) and the "rest" since the best cryptographic modules depend on the runtime you're using.

It would be helpful if there was a lib that provided getAlgorithm() with the @oslojs/crypto classes for those of us that are fine with that implementation. Maybe similar convenience methods that use the best crypto module for a given runtime could be created too? i.e. @oslojs/crypto/bun, @oslojs/crypto/nodejs, etc


Location Monitor Pool?

Is there a way to get the pool of locations that are being monitored when using Location.monitor? In our previous setup using just CoreLocation there are times where we needed to cycle through all the monitored regions in LocationManager.monitoredRegions so we can remove any duplicates or regions that are no longer within a certain radius of the users. Can't seem to find anything in the documentation that shows whether you can/can't access the Location pool. This is the one thing missing that would SwiftLocation a complete replacement for our current structure. Thanks.

Thank you for your contribution.
A new rewritten version is available both on master and CocoaPods (marked as 3.0.0-beta). It requires iOS9 and Swift 4.
If you encounter any other problem feel free to open an issue; I'll close because with the new version its now invalid.
Current version does not support region monitoring yet. It's planned for incoming 3.1 release. If you have questions or suggestions feel free to reopen a new issue.
Thanks

Thanks @malcommac for the response and updated library. Not to rush or sound ungrateful, but do you know when you may have 3.1 with the replacement for the 'Location.monitor(region:' in place? I had just got the whole background updates and location monitoring finished on Friday and now the monitor method is gone :( .
Really great library, I've been using this and SwiftDate on a couple projects now and both have made life so much easier.

I'll try to work on it this week but I can't make any promise about that because I'm pretty busy with another project.
You can follow it here: https://github.com/malcommac/SwiftLocation/issues/162

No problem, I'll roll back for now just because the monitor part is important for the testing we are doing but will bookmark this to update when ready. Thanks again for everything.


Apache HttpClient failed to download yarn package from s3.amazonaws.com (redirection from github)

Hi,
Description
What I am trying to do: ./gradlew installYarn
Expected results: yarn is installed
Actual results:
Execution failed for task ':ui:installYarn'.
> javax.net.ssl.SSLPeerUnverifiedException: Certificate for <github-production-release-asset-2e65be.s3.amazonaws.com> doesn't match any of the subject alternative names: [*.s3.amazonaws.com, s3.amazonaws.com]

org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':ui:installYarn'.
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.lambda$executeIfValid$1(ExecuteActionsTaskExecuter.java:200)
	at org.gradle.internal.Try$Failure.ifSuccessfulOrElse(Try.java:263)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:198)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:179)
	at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:109)
	at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)
	at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:62)
	at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)
	at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:56)
	at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:200)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:195)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:62)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$call$2(DefaultBuildOperationExecutor.java:76)
	at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.callWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:54)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:76)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)
	at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:41)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:372)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:359)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:352)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:338)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.lambda$run$0(DefaultPlanExecutor.java:127)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:191)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.executeNextNode(DefaultPlanExecutor.java:182)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:124)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
	at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56)
Caused by: org.gradle.api.UncheckedIOException: javax.net.ssl.SSLPeerUnverifiedException: Certificate for <github-production-release-asset-2e65be.s3.amazonaws.com> doesn't match any of the subject alternative names: [*.s3.amazonaws.com, s3.amazonaws.com]
	at org.gradle.internal.UncheckedException.throwAsUncheckedException(UncheckedException.java:61)
	at org.gradle.internal.UncheckedException.throwAsUncheckedException(UncheckedException.java:41)
	at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:107)
	at org.gradle.api.internal.project.taskfactory.StandardTaskAction.doExecute(StandardTaskAction.java:58)
	at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:51)
	at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:29)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$3.run(ExecuteActionsTaskExecuter.java:555)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:56)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$run$1(DefaultBuildOperationExecutor.java:71)
	at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.runWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:45)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:71)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:540)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:523)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.access$300(ExecuteActionsTaskExecuter.java:108)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$TaskExecution.executeWithPreviousOutputFiles(ExecuteActionsTaskExecuter.java:271)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$TaskExecution.execute(ExecuteActionsTaskExecuter.java:260)
	at org.gradle.internal.execution.steps.ExecuteStep.lambda$execute$1(ExecuteStep.java:34)
	at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:34)
	at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:26)
	at org.gradle.internal.execution.steps.CleanupOutputsStep.execute(CleanupOutputsStep.java:67)
	at org.gradle.internal.execution.steps.CleanupOutputsStep.execute(CleanupOutputsStep.java:36)
	at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:49)
	at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:34)
	at org.gradle.internal.execution.steps.CancelExecutionStep.execute(CancelExecutionStep.java:43)
	at org.gradle.internal.execution.steps.TimeoutStep.executeWithoutTimeout(TimeoutStep.java:73)
	at org.gradle.internal.execution.steps.TimeoutStep.execute(TimeoutStep.java:54)
	at org.gradle.internal.execution.steps.CreateOutputsStep.execute(CreateOutputsStep.java:44)
	at org.gradle.internal.execution.steps.SnapshotOutputsStep.execute(SnapshotOutputsStep.java:54)
	at org.gradle.internal.execution.steps.SnapshotOutputsStep.execute(SnapshotOutputsStep.java:38)
	at org.gradle.internal.execution.steps.BroadcastChangingOutputsStep.execute(BroadcastChangingOutputsStep.java:42)
	at org.gradle.internal.execution.steps.CacheStep.executeWithoutCache(CacheStep.java:159)
	at org.gradle.internal.execution.steps.CacheStep.execute(CacheStep.java:72)
	at org.gradle.internal.execution.steps.CacheStep.execute(CacheStep.java:43)
	at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:44)
	at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:33)
	at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:38)
	at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:24)
	at org.gradle.internal.execution.steps.SkipUpToDateStep.executeBecause(SkipUpToDateStep.java:92)
	at org.gradle.internal.execution.steps.SkipUpToDateStep.lambda$execute$0(SkipUpToDateStep.java:85)
	at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:55)
	at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:39)
	at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:76)
	at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:37)
	at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:36)
	at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:26)
	at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:94)
	at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:49)
	at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:79)
	at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:53)
	at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:74)
	at org.gradle.internal.execution.steps.SkipEmptyWorkStep.lambda$execute$2(SkipEmptyWorkStep.java:78)
	at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:78)
	at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:34)
	at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsStartedStep.execute(MarkSnapshottingInputsStartedStep.java:39)
	at org.gradle.internal.execution.steps.LoadExecutionStateStep.execute(LoadExecutionStateStep.java:40)
	at org.gradle.internal.execution.steps.LoadExecutionStateStep.execute(LoadExecutionStateStep.java:28)
	at org.gradle.internal.execution.impl.DefaultWorkExecutor.execute(DefaultWorkExecutor.java:33)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:187)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:179)
	at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:109)
	at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)
	at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:62)
	at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)
	at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:56)
	at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:200)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:195)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:62)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$call$2(DefaultBuildOperationExecutor.java:76)
	at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.callWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:54)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:76)
	at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)
	at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:41)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:372)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:359)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:352)
	at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:338)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.lambda$run$0(DefaultPlanExecutor.java:127)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:191)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.executeNextNode(DefaultPlanExecutor.java:182)
	at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:124)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
	at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56)
Caused by: javax.net.ssl.SSLPeerUnverifiedException: Certificate for <github-production-release-asset-2e65be.s3.amazonaws.com> doesn't match any of the subject alternative names: [*.s3.amazonaws.com, s3.amazonaws.com]
	at org.apache.http.conn.ssl.SSLConnectionSocketFactory.verifyHostname(SSLConnectionSocketFactory.java:507)
	at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:437)
	at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:384)
	at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)
	at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:376)
	at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393)
	at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
	at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186)
	at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
	at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
	at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
	at org.siouan.frontendgradleplugin.infrastructure.httpclient.ApacheHttpClient.getRemoteResource(ApacheHttpClient.java:89)
	at org.siouan.frontendgradleplugin.domain.usecase.AbstractHttpClient.sendGetRequest(AbstractHttpClient.java:33)

Environment

OS: [Mac OS X]
JDK: [e.g. Oracle JDK 11 64 bits]
Gradle: [e.g. Gradle 6.7]
Frontend Gradle plugin: [4.0.1]

Settings in build.gradle.kts file:
frontend {
    nodeVersion.set("14.15.0")
    nodeInstallDirectory.set(file("${buildDir}/node"))
    assembleScript.set("run build")
    yarnEnabled.set(true)
    yarnVersion.set("1.22.5")
}

Investigation
Seems like Apache HttpClient failed to do SSL hostname validation for the file. I don't have Windows or Linux to test so not sure whether it works in those environments or not.

Hi @huynguyentuong,
At the moment, I didn't succeed in reproducing the issue. Either locally with my Windows workstation, or with automated tests under Travis (Windows Server, Mac OS and Linux), everything works fine.
However:

I can see GitHub redirects download requests to an AWS S3 bucket.
And it seems the issue itself was reported multiple times last years. I could find some bug reports about equivalent problems with private/public domain names and/or wildcards. More recently, in Apache HTTP client 4.5.12, the problem was also reported in other products like here. The plugin uses release 4.5.13.

I have no idea how to fix the issue now, and I don't want to disable any SSL verification when the plugin uses the Apache HTTP client, for security reasons of course.
I will try to report the issue in Apache's bugtracker, and watch for any update on the HTTP client in the next weeks. Right now, I see 2 workarounds:

Download and explode the distribution somewhere on the target workstation, and use the yarnDistributionProvided / yarnInstallDirectory properties.
Use a distribution server mirroring Yarn's official distribution server, and set the yarnDistributionServerUrlRoot / yarnDistributionServerUrlPathPattern properties accordingly.

Finally:

Is the issue systematic?
Could you try cloning the master branch, run automated test TaskTypesWithDownloadedDistributionsFuncTest.shouldRunCustomTasks on your workstation, and provide the results here?

Thank you very much for your help!
Best regards

Hi @huynguyentuong,
After some research, I don't see any reason the plugin and its internal Apache HTTP client would fail with the s3.amazonaws.com domain name. This domain name is registered as a private domain name suffix in the public suffix list, and the HTTP client has an internal copy of this list which seems up-to-date. This means wildcards shall be supported in certificates by the client, as long as hostname verification with that list of public suffixes is not disabled when an instance is configured to send a request. I didn't find any misconfiguration in the plugin, when the HTTP client is used.
However, I may have made a mistake in the plugin, by using version 4.5.13 of the Apache HTTP client. The client latest version is 5.0.3, and works also perfectly. There's no reason the plugin does not use the latest version. It will be upgraded in the next release.
My question is still pending: do you still face this issue, or was it temporary?
Thank you in advance for your help.
BR

Hi @v1nc3n4,
Thank you very much for looking into this.
I tried to run the test and it is green. The result is as following
Using 12 worker leases.
Starting Build
Settings evaluated using settings file '/private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/settings.gradle'.
Projects loaded. Root project using build file '/private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/build.gradle'.
Included projects: [root project 'junit5042318668945607359']

> Configure project :
Evaluating root project 'junit5042318668945607359' using build file '/private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/build.gradle'.
Compiling build file '/private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/build.gradle' using SubsetScriptTransformer.
Compiling build file '/private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/build.gradle' using BuildScriptTransformer.
All projects evaluated.
Selected primary task 'myRunNodeTask' from project :
Tasks to be executed: [task ':installNode', task ':myRunNodeTask']
:installNode (Thread[Execution worker for ':' Thread 4,5,main]) started.

> Task :installNode
Task ':installNode' is not up-to-date because:
  No history is available.
[installNode] Removing install directory '/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/node-dist'
[installNode] Downloading distribution at 'https://nodejs.org/dist/v12.18.3/node-v12.18.3-darwin-x64.tar.gz'
[installNode] Downloading resource at 'https://nodejs.org/dist/v12.18.3/node-v12.18.3-darwin-x64.tar.gz' (proxy: DIRECT)
[installNode] Downloading resource at 'https://nodejs.org/dist/v12.18.3/SHASUMS256.txt' (proxy: DIRECT)
[installNode] Verifying distribution integrity
[installNode] Exploding distribution into '/private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/build/tmp/installNode/extract'
[installNode] Moving distribution into '/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/node-dist'
[installNode] Removing explode directory '/private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/build/tmp/installNode/extract'
[installNode] Removing distribution file '/private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/build/tmp/installNode/node-v12.18.3-darwin-x64.tar.gz'
[installNode] Distribution installed in '/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/node-dist'
:installNode (Thread[Execution worker for ':' Thread 4,5,main]) completed. Took 9.024 secs.
:myRunNodeTask (Thread[Execution worker for ':' Thread 4,5,main]) started.

> Task :myRunNodeTask
Task ':myRunNodeTask' is not up-to-date because:
  Task has not declared any outputs despite executing actions.
[myRunNodeTask] Install directory resolved from extension: /var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/node-dist
[myRunNodeTask] Executable '/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/node-dist/bin/node' resolved from install directory
[myRunNodeTask] Running '/bin/sh' with arguments: [-c], [/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/node-dist/bin/node /var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/script.js]
Starting process 'command '/bin/sh''. Working directory: /var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/frontend Command: /bin/sh -c /var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/node-dist/bin/node /var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/script.js
Successfully started process 'command '/bin/sh''
Hello!
:myRunNodeTask (Thread[Execution worker for ':' Thread 4,5,main]) completed. Took 0.78 secs.

BUILD SUCCESSFUL in 13s
2 actionable tasks: 2 executed
Using 12 worker leases.
Starting Build
Settings evaluated using settings file '/private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/settings.gradle'.
Projects loaded. Root project using build file '/private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/build.gradle'.
Included projects: [root project 'junit5042318668945607359']

> Configure project :
Evaluating root project 'junit5042318668945607359' using build file '/private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/build.gradle'.
All projects evaluated.
Selected primary task 'myRunNodeTask' from project :
Tasks to be executed: [task ':installNode', task ':myRunNodeTask']
:installNode (Thread[Execution worker for ':',5,main]) started.

> Task :installNode UP-TO-DATE
Skipping task ':installNode' as it is up-to-date.
:installNode (Thread[Execution worker for ':',5,main]) completed. Took 0.171 secs.
:myRunNodeTask (Thread[Execution worker for ':',5,main]) started.

> Task :myRunNodeTask
Task ':myRunNodeTask' is not up-to-date because:
  Task has not declared any outputs despite executing actions.
[myRunNodeTask] Install directory resolved from extension: /var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/node-dist
[myRunNodeTask] Executable '/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/node-dist/bin/node' resolved from install directory
[myRunNodeTask] Running '/bin/sh' with arguments: [-c], [/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/node-dist/bin/node /var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/script.js]
Starting process 'command '/bin/sh''. Working directory: /var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/frontend Command: /bin/sh -c /var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/node-dist/bin/node /var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/script.js
Successfully started process 'command '/bin/sh''
Hello!
:myRunNodeTask (Thread[Execution worker for ':',5,main]) completed. Took 0.048 secs.

BUILD SUCCESSFUL in 0s
2 actionable tasks: 1 executed, 1 up-to-date
> Task :installNode UP-TO-DATE

> Task :myRunNpxTask
6.14.6

BUILD SUCCESSFUL in 0s
2 actionable tasks: 1 executed, 1 up-to-date
> Task :installNode UP-TO-DATE

> Task :myRunNpxTask
6.14.6

BUILD SUCCESSFUL in 0s
2 actionable tasks: 1 executed, 1 up-to-date
> Task :installNode UP-TO-DATE
> Task :installYarn SKIPPED

> Task :installFrontend
npm notice created a lockfile as package-lock.json. You should commit this file.
up to date in 0.392s
found 0 vulnerabilities

> Task :myRunNpmYarnTask

><EMAIL_ADDRESS>another-script /private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/frontend
> node -v && npm -v && echo 'Another frontend script executed' && npm run check

v12.18.3
6.14.6
Another frontend script executed

><EMAIL_ADDRESS>check /private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/frontend
> npm run lint && npm run test

><EMAIL_ADDRESS>lint /private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/frontend
> echo 'Frontend linted'

Frontend linted

><EMAIL_ADDRESS>test /private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/frontend
> echo 'Frontend tested'

Frontend tested

BUILD SUCCESSFUL in 2s
3 actionable tasks: 2 executed, 1 up-to-date
> Task :installNode UP-TO-DATE
> Task :installYarn SKIPPED

> Task :installFrontend
up to date in 0.315s
found 0 vulnerabilities

> Task :myRunNpmYarnTask

><EMAIL_ADDRESS>another-script /private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/frontend
> node -v && npm -v && echo 'Another frontend script executed' && npm run check

v12.18.3
6.14.6
Another frontend script executed

><EMAIL_ADDRESS>check /private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/frontend
> npm run lint && npm run test

><EMAIL_ADDRESS>lint /private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/frontend
> echo 'Frontend linted'

Frontend linted

><EMAIL_ADDRESS>test /private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/frontend
> echo 'Frontend tested'

Frontend tested

BUILD SUCCESSFUL in 1s
3 actionable tasks: 2 executed, 1 up-to-date
> Task :installNode UP-TO-DATE

> Task :installYarn
Invalid cookie header: "Set-Cookie: _octo=GH1.1.1627453147.1606516210; Path=/; Domain=github.com; Expires=Sat, 27 Nov 2021 22:30:10 GMT; Secure; SameSite=Lax". Invalid 'expires' attribute: Sat, 27 Nov 2021 22:30:10 GMT
Invalid cookie header: "Set-Cookie: logged_in=no; Path=/; Domain=github.com; Expires=Sat, 27 Nov 2021 22:30:10 GMT; HttpOnly; Secure; SameSite=Lax". Invalid 'expires' attribute: Sat, 27 Nov 2021 22:30:10 GMT

> Task :installFrontend
yarn install v1.22.4
info No lockfile found.
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
Done in 0.04s.

> Task :myRunNpmYarnTask
yarn run v1.22.4
$ node -v && npm -v && echo 'Another frontend script executed' && npm run check
v12.18.3
6.14.6
Another frontend script executed
npm WARN lifecycle The node binary used for scripts is /var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/yarn--1606516213882-0.026593492711227684/node but npm is using /private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/node-dist/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.

><EMAIL_ADDRESS>check /private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/frontend
> npm run lint && npm run test

npm WARN lifecycle The node binary used for scripts is /var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/yarn--1606516213882-0.026593492711227684/node but npm is using /private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/node-dist/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.

><EMAIL_ADDRESS>lint /private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/frontend
> echo 'Frontend linted'

Frontend linted
npm WARN lifecycle The node binary used for scripts is /var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/yarn--1606516213882-0.026593492711227684/node but npm is using /private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/node-dist/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.

><EMAIL_ADDRESS>test /private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/frontend
> echo 'Frontend tested'

Frontend tested
Done in 1.10s.

BUILD SUCCESSFUL in 5s
4 actionable tasks: 3 executed, 1 up-to-date
> Task :installNode UP-TO-DATE
> Task :installYarn UP-TO-DATE

> Task :installFrontend
yarn install v1.22.4
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/4] Resolving packages...
success Already up-to-date.
Done in 0.04s.

> Task :myRunNpmYarnTask
yarn run v1.22.4
$ node -v && npm -v && echo 'Another frontend script executed' && npm run check
v12.18.3
6.14.6
Another frontend script executed
npm WARN lifecycle The node binary used for scripts is /var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/yarn--1606516215510-0.9477202198734205/node but npm is using /private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/node-dist/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.

><EMAIL_ADDRESS>check /private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/frontend
> npm run lint && npm run test

npm WARN lifecycle The node binary used for scripts is /var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/yarn--1606516215510-0.9477202198734205/node but npm is using /private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/node-dist/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.

><EMAIL_ADDRESS>lint /private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/frontend
> echo 'Frontend linted'

Frontend linted
npm WARN lifecycle The node binary used for scripts is /var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/yarn--1606516215510-0.9477202198734205/node but npm is using /private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/node-dist/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.

><EMAIL_ADDRESS>test /private/var/folders/n9/78xkbtyj785_mdfnhg3rv08w0000gn/T/junit5042318668945607359/frontend
> echo 'Frontend tested'

Frontend tested
Done in 0.89s.

BUILD SUCCESSFUL in 1s
4 actionable tasks: 2 executed, 2 up-to-date

The issue is still there, but let me investigate more, or try to upgrade to Apache HTTP 5.xx to see whether it works or not

Hi @v1nc3n4,
I think I found the issue, probably because of library version clashing of plugins, one of the other plugins I used must be also having another version of Apache HTTP client that having the SSL bug.
If I create a completely empty Gradle project with only our frontend plugin here then we have no problem.
Let me investigate more to see which plugin is that and work with the author to solve it and put the workaround here.
Thanks again for your help.
Cheers,
Huy

I found a workaround, just explicitly specify the version of HTTP client as following
buildscript {
    repositories {
        jcenter()
    }
    dependencies {
        classpath("org.apache.httpcomponents:httpclient:4.5.13")
    }
}

Hello,
I’m really glad you found the cause of this problem!
The fact the automated test above succeeded also suggested another cause than the plugin itself. And indeed the next step would have been to start a new project with the same configuration than the one created by the integration test. So great job!
I’m glad you also found a workaround by explicitly setting the dependency in the project. I’m sure it will help a lot in the future because it’s not the first time a dependency issue occurs with another library.
Cảm ơn nhiều anh giúp em, chúc anh ngày ngon!
BR

"I don't see any reason the plugin and its internal Apache HTTP client would fail with the s3.amazonaws.com domain name."
I had same exception in 4.5.12/4.5.13 Http client because my basket name contained dots, like  xx.yy.zz and url was like https://xxx.yyy.zzz.s3.amazon.... After I removed dots from basket name to xxyyzz everything works.

Hi @seleznevmm
Actually, the issue you faced is a different issue, and it is a relevant behaviour I guess. The AWS S3 server uses a wildcard SSL certificate *.s3.amazonaws.com, and the wildcard matches one sub-domain level only. So, it is normal you see such error if the bucket name contains a dot, i.e. a true positive case.
Renaming the bucket is the appropriate solution, and that’s what you did successfully.
Hope this helps!
BR

I'm seeing the same issue. Adding the classpath dependency didn't fix it. Anything else I can try?

Hi @efenderbosch,
Have you tried running the installYarn task in a blank project with the plugin only? As suggested by @huynguyentuong, there may be a library conflict depending on the dependencies used in your project.
Regards

@efenderbosch
I can also confirm that, if you tried to add the HTTP client 5.0.3 explicitly, for sure this library was not chosen at runtime, because the 2 warnings Invalid cookie header are typical warnings of the HTTP client 4.5.13 and don't exist anymore in the 5.0.3 release (see issue #134).
I can only suggest to start from one of the project templates provided in the examples section of this repository, to find out when the problem occurs.
Feel free to share the results here!
BR

It works as expected in an empty project.

@efenderbosch,
To help you progressing to the source of the problem:
I just realised one thing regarding what you tried: adding an explicit dependency on release 5.0.3 of Apache HTTP client can't work for sure if I assume you are using release 4.0.1 of this plugin. The expected release of the HTTP client is 4.5.13.
Can you try changing the release and share the results here? Thanks again for your help.

First thing I tried was 4.5.13.

I'm seeing the same issue. Adding the classpath dependency didn't fix it. Anything else I can try?

Sorry to read that. Apart from progressing step by step by adding dependencies into a sample project and see when the problem occurs, I don't have a solution. To me, it doesn't seem to be a plugin issue.
Maybe you could try to use Gradle's dependencies task, to find which dependencies use an obsolete release of Apache HTTP client.

The only version of org.apache.httpcomponents:httpclient in the report is 4.5.13.


[main] Format Go code

Cron -knative-prow-robot
/cc knative-sandbox/source-wg-leads
/assign knative-sandbox/source-wg-leads
Produced by: knative-sandbox/knobots/actions/update-gofmt
Details:

/lgtm
/approve


Redirects greater than 1 are not processed.

Seems the underlying dependency only follows 1 redirect. So an HTTP anchor to a post url will fail as there are 2 (one to https, and another to the full topic url)

https://github.com/ospfranco/link-preview-js/issues/135

😱 so much for async


Add example list info hook

Add an example list_additional_information hook so that users of gps can refer to it and discover the full capabilities of this feature.
There will also be a reference to this example from the docs.
FI-123

NOT READY FOR REVIEW


Added the baseline experiments for english to tiv languages.

So we don't need the training data, but what we need are the bpe codes. This file is generated by the notebook, the name should be something like "bpe.4000.codes" or so. Could you please also add the configuration file? It is stored in the model directory. Thanks!

Can you please add your results to the benchmark file as well? Thanks!


[REDBOX-496/498] Make the default route go to chat with LLM; chat with or without documents

Context

As the first step of making chat more widely available to users, the default route should be changed to chat. In addition, the chat route now has logic to tell if no documents are selected chat_no_docs which results in sending question to GPT model or if a document is selcted, chat_with_docs, the document is stuffed into the context window along with the users' question.
Changes proposed in this pull request

Change default route to chat. Summarise and RAG functionality can still be accessed using keywords as seen in this screenshot

Chat as default is split into chat no documents:

and chat with documents:

Guidance to review

Please review and check that you are happy with the approach to selecting chat with documents or chat with no documents?
Relevant links
Things to check

[x] I have added any new ENV vars in all deployed environments
[x] I have tested any code added or changed
[x] I have run integration tests

@andy-symonds  Had a chat with Charlotte and demoed this branch. We think we should rename @chat_no_docs to @chat and keep @chat_with_docs the same

Could we add our new route names to the tool tip?
@lmwilkigov how does this work for you?


Seeking Contributions: Feature Enhancements, Bug Fixes, and Support for Maintainerr

Hey there, welcome to Maintainerr! Up until now, this project was caried by @jorenn92 as the solo developer and @ydkmlt84 for support and documentation. However, we've reached a point where the project has grown beyond what we can handle alone.
Time these days seems to vanish into a black hole of support questions and bug reports, leaving little room for the fun stuff like adding cool features or enhancing existing ones. I've got a whole bunch of ideas swirling around in my head, but alas, they're stuck in the "someday" folder.
That's where you come in! I need your help to keep Maintainerr on track and moving forward.
Ways You Can Pitch In:

Feature Enhancements: Have ideas for new features or improvements? Share your suggestions and code contributions to enhance the project's functionality. You're also welcome to work on suggested feature requests in the GitHub discussions.
Bug Fixes: Spot a bug? Help squash it by submitting bug reports or even better, fixing them directly with a pull request. Or, fix bugs submitted by other users.
Support: Whether it's answering questions, providing guidance, or troubleshooting issues, your support contributions are invaluable.

Ready to Dive In?

Check out our contribution  guidelines for the nitty-gritty details.
Explore our open issues / feature requests to find your perfect starting point.
Fork the repository, get creative, and send us your shiny new pull requests!
Don't forget to join the community discussions and Discord, ask questions, and share your thoughts along the way.
Feel free to send @jorenn92 a private message on Discord for more details or questions!

Thanks a million for considering lending a hand to Maintainerr!

Donate via PayPal option?


Handedness between ISwapPowGate and FSim is different.

The ISwapPowGate and FSim gate rotate in different directions on the |01>, |10> subspace.  This feels a bit odd to me.

This morning I meant to change signs of the angles in fSim only to notice that @maffoo has already done this in #1726. It seems that his PR missed ISwapPowGate. I'll send out a fix soon.

https://quantumcomputing.stackexchange.com/questions/2594/what-is-the-matrix-of-the-iswap-gate

Changing these kinds of conventions is a silent breaking change on our users. The iswap gate has been around for several versions now; we can't just change what it means.
Personally I don't mind so much if iswap is at fsim(-90deg) instead of fsim(+90deg).
If we want to change this convention, we first need to deprecate iswap for one version then delete it for one version then re-introduce it with the new convention.

OK.


[consumer-kafka-quarkus] config errors

Logs
15:50:44 WARN  [io.sm.re.me.kafka] (main) SRMSG18216: No `group.id` set in the configuration, generate a random id: 181463b3-8d4b-4b03-85ce-f6b1085d16d6
15:50:44 WARN  [or.ap.ka.cl.co.ConsumerConfig] (main) The configuration 'service.port.port' was supplied but isn't a known config.
15:50:44 WARN  [or.ap.ka.cl.co.ConsumerConfig] (main) The configuration 'port.9092.tcp.addr' was supplied but isn't a known config.
15:50:44 WARN  [or.ap.ka.cl.co.ConsumerConfig] (main) The configuration 'port.9092.tcp.proto' was supplied but isn't a known config.
15:50:44 WARN  [or.ap.ka.cl.co.ConsumerConfig] (main) The configuration 'port.9092.tcp.port' was supplied but isn't a known config.
15:50:44 WARN  [or.ap.ka.cl.co.ConsumerConfig] (main) The configuration 'port' was supplied but isn't a known config.
15:50:44 WARN  [or.ap.ka.cl.co.ConsumerConfig] (main) The configuration 'service.port' was supplied but isn't a known config.
15:50:44 WARN  [or.ap.ka.cl.co.ConsumerConfig] (main) The configuration 'port.9092.tcp' was supplied but isn't a known config.
15:50:44 WARN  [or.ap.ka.cl.co.ConsumerConfig] (main) The configuration 'service.host' was supplied but isn't a known config.

same as jaxrs-kafka-quarkus
15:56:18 WARN  [io.sm.re.me.kafka] (main) SRMSG18216: No `group.id` set in the configuration, generate a random id: a00b4854-301e-4739-8a3c-4c5cd554f28e
15:56:18 WARN  [or.ap.ka.cl.co.ConsumerConfig] (main) The configuration 'service.port.port' was supplied but isn't a known config.
15:56:18 WARN  [or.ap.ka.cl.co.ConsumerConfig] (main) The configuration 'port.9092.tcp.addr' was supplied but isn't a known config.
15:56:18 WARN  [or.ap.ka.cl.co.ConsumerConfig] (main) The configuration 'port.9092.tcp.proto' was supplied but isn't a known config.
15:56:18 WARN  [or.ap.ka.cl.co.ConsumerConfig] (main) The configuration 'splitkey' was supplied but isn't a known config.
15:56:18 WARN  [or.ap.ka.cl.co.ConsumerConfig] (main) The configuration 'port.9092.tcp.port' was supplied but isn't a known config.
15:56:18 WARN  [or.ap.ka.cl.co.ConsumerConfig] (main) The configuration 'port' was supplied but isn't a known config.
15:56:18 WARN  [or.ap.ka.cl.co.ConsumerConfig] (main) The configuration 'service.port' was supplied but isn't a known config.
15:56:18 WARN  [or.ap.ka.cl.co.ConsumerConfig] (main) The configuration 'port.9092.tcp' was supplied but isn't a known config.
15:56:18 WARN  [or.ap.ka.cl.co.ConsumerConfig] (main) The configuration 'service.host' was supplied but isn't a known config.

same as producer-kafka-quarkus
10:21:06 WARN  [or.ap.ka.cl.pr.ProducerConfig] (main) The configuration 'service.port.port' was supplied but isn't a known config.
10:21:06 WARN  [or.ap.ka.cl.pr.ProducerConfig] (main) The configuration 'port.9092.tcp.addr' was supplied but isn't a known config.
10:21:06 WARN  [or.ap.ka.cl.pr.ProducerConfig] (main) The configuration 'port.9092.tcp.proto' was supplied but isn't a known config.
10:21:06 WARN  [or.ap.ka.cl.pr.ProducerConfig] (main) The configuration 'splitkey' was supplied but isn't a known config.
10:21:06 WARN  [or.ap.ka.cl.pr.ProducerConfig] (main) The configuration 'port.9092.tcp.port' was supplied but isn't a known config.
10:21:06 WARN  [or.ap.ka.cl.pr.ProducerConfig] (main) The configuration 'port' was supplied but isn't a known config.
10:21:06 WARN  [or.ap.ka.cl.pr.ProducerConfig] (main) The configuration 'generate.message.period.seconds' was supplied but isn't a known config.
10:21:06 WARN  [or.ap.ka.cl.pr.ProducerConfig] (main) The configuration 'service.port' was supplied but isn't a known config.
10:21:06 WARN  [or.ap.ka.cl.pr.ProducerConfig] (main) The configuration 'port.9092.tcp' was supplied but isn't a known config.
10:21:06 WARN  [or.ap.ka.cl.pr.ProducerConfig] (main) The configuration 'service.host' was supplied but isn't a known config.

Ignore this Warning because of https://github.com/apache/kafka/pull/5876


Add sonar scan

Signed-off-by: xuezhaojun<EMAIL_ADDRESS>https://github.com/stolostron/backlog/issues/23658

/assign @qiujian16

/assign @elgnay

/approve
/lgtm


Length Histograms in texts columns are being wrongly plotted

Describe the bug
Assuming all text columns length frequency histograms are referring to the length on values found on the text columns, I noticed several columns that have only two possible values for lengths col1(null, 13);  col2 (null, 8) but the profiling report calculates mins, mean, median not found in the table data.
To Reproduce
Use a single column with multiple values of unique length combine with null values: should only exist one bin for the total frequency of values in DF.
 Seems like a duplicate of #613, for which a fix is started in #619.

Everything has recently installed, downgrade from python 3.9 to 3.7 because incompatibility with pandas-profiling==2.9.0
I'd be interested in knowing where the incompatibility comes from, we might be able to resolve this.

Hi @sbrugman,
I have created a virtualenv with 3.9.0, upgrade pip, install pandas; and then after, when I try to install pandas-profiling an error during installation is occurring.  Attached complete detail.
Building wheels for collected packages: numba, llvmlite
Building wheel for numba (setup.py) ... error
ERROR: Command errored out with exit status 1:
error_installing_pp.txt

@leopascual  I've just released v2.10.1 that should resolve your issue!
Want me to continue to support this package? Please consider sponsoring


Can't support mathematical formula

Steps to reproduce the problem (provide example Markdown if applicable):
$x+y=z$ or  $$x+y=z$$

Expected behavior:
such as

Actual behavior:

$$x+y=z$$

(Also see what the reference implementation does: https://spec.commonmark.org/dingus/)

the markdown to html should render like the pciture below

This is not a bug. Maths rendering is not part of CommonMark. So it's an additional extension that would be needed (depending on how it's done).
Note that if you're rendering it as HTML and can add some JS, you can already do it, see https://github.com/commonmark/commonmark-java/issues/194#issuecomment-737856598
(Also linking some general discussion about syntax here: https://talk.commonmark.org/t/mathjax-extension-for-latex-equations/698/8)

this shouldnt be hard to do with https://github.com/opencollab/jlatexmath

This is not a bug. Maths rendering is not part of CommonMark. So it's an additional extension that would be needed (depending on how it's done).
Note that if you're rendering it as HTML and can add some JS, you can already do it, see #194 (comment)
(Also linking some general discussion about syntax here: https://talk.commonmark.org/t/mathjax-extension-for-latex-equations/698/8)

Render math formula after markdown html is generated has lots of corner cases.
For example:
`$`$

$$
$`$`

$$
would have different effects.


Crime.net Cargo disabled, why?

Hi, I know this is not really an issue and it was likely disabled for a good reason but I just want to know why. Earlier today before the update (when Goonmod was running on an unsupported Payday 2 version), I sent someone a mask using Crime.net Cargo and it worked fine.

I disabled it since there's a bunch of edge cases which aren't going to be fixed until the new version of GoonMod comes out. DLC items being traded away and not being able to be retrieved and stuff like that. It'll be coming back, just not until the new version is ready and released.

That's all I wanted to know, thanks! I absolutely love the mod, keep up the great work!


[SPIKE] Implement Title Bar Icons

The design calls for main window manipulation via icons in the title bar. Implement the listed buttons.
Definition of Done
The following tasks need to be completed.

[ ] create settings button
[ ] create add column button

Tech Notes
Buttons don't need to do anything yet. Tests don't need to be complete at first. Get something running in the prototype app. Grow tests as features are developed.

Closing this one. Tasks tracked in #9.


do not use set-env or add-path

Wanna maybe send a PR to one of the repos to check this works as intended? It'd be awesome if this could do a similar check like pkg :D

Wanna maybe send a PR to one of the repos to check this works as intended? It'd be awesome if this could do a similar check like pkg :D

That is where I started, was still getting the PR staged for review. :D

/lgtm
/approve


Add missing status Proposed

adr-viewer implements the status "Pending", but the original blog article by Michael Nygard and adr-tools-python use the status "Proposed" for new ADRs. This patch adds "Proposed" as synonyme for "Pending".

I'll take this one...... - my alt repo for this is the one I forked August 2022 - has all the PRs in it that I've authored:
https://github.com/alshapton/adr-viewer

Happy to roll this in, I'm going to start releasing this again soon as the project has been on unofficial hiatus for a while

Welcome back then.


Socket hangup on getting metrics

Describe the bug
I have the kube-prometheus operator installed on multiple clusters, and for some of them it's fine, but a recent install in our non-govcloud clusters (ironically) end up having the metrics spin forever, and result in a socket hangup. I've tried letting it auto-configure, setting it to connect to the operator service, connect to the non-operator prometheus service, and nothing seems to work for the recently added clusters. They have the same configuration as far as settings go and have not had issues until today.
To Reproduce
Steps to reproduce the behavior:

Open the Lens app with the
Click on anything to show metrics

Expected behavior
Metrics either error out immediately to show improper configuration or display metrics
Actual behavior
All metrics spin forever. If I wait long enough, they finally come back with metrics errors. Eventually, the logs come back with socket hangups as well.
Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

Lens Version: 5.4.3-latest.20220317.1
MacOS
Installation method (e.g. snap or AppImage in Linux): Mac Installer

Logs:
When you run the application executable from command line you will see some logging output. Please paste them here:
Errors on first connection:
debug:   ┏ [CLUSTER]: broadcasting connection update Connected, waiting for view to load ... +1ms
debug:   ┃ [ 1] {
debug:   ┃ [ 2]   isError: false,
debug:   ┃ [ 3]   meta: {
debug:   ┃ [ 4]     id: '7d72c0ee469feccc1e73fd2c04dd2fd1',
debug:   ┃ [ 5]     name: 'ops',
debug:   ┃ [ 6]     ready: true,
debug:   ┃ [ 7]     online: true,
debug:   ┃ [ 8]     accessible: true,
debug:   ┃ [ 9]     disconnected: false
debug:   ┃ [10]   }
debug:   ┗ [11] }
debug:   ▪ Acquired a lock for 1.21.9 +7ms
info:    ▪ Creating a new port-forward monitoring/service/prometheus-operated:9090 +296ms
debug:   ▪ Local kubectl is version 1.21.9 +411ms
debug:   ▪ [KUBECTL]: Releasing lock for 1.21.9 +1ms
debug:   ▪ [PORT-FORWARD-ROUTE]: kubectl port-forward process stderr: I0320 09:40:36.495145   35778 log.go:184] (0xc0005fa420) (0xc000afb7c0) Create stream
I0320 09:40:36.495682   35778 log.go:184] (0xc0005fa420) (0xc000afb7c0) Stream added, broadcasting: 1
 +3s
debug:   ▪ [PORT-FORWARD-ROUTE]: kubectl port-forward process stderr: I0320 09:40:36.529373   35778 log.go:184] (0xc0005fa420) Reply frame received for 1
I0320 09:40:36.529396   35778 log.go:184] (0xc000afb7c0) (1) Writing data frame
 +34ms
debug:   ▪ [PORT-FORWARD-ROUTE]: kubectl port-forward process stderr: I0320 09:40:36.529433   35778 log.go:184] (0xc0005fa420) (0xc000ae28c0) Create stream
I0320 09:40:36.529441   35778 log.go:184] (0xc0005fa420) (0xc000ae28c0) Stream added, broadcasting: 3
 +1ms
debug:   ▪ [PORT-FORWARD-ROUTE]: kubectl port-forward process stderr: I0320 09:40:36.564144   35778 log.go:184] (0xc0005fa420) Reply frame received for 3
 +34ms
debug:   ▪ [PORT-FORWARD-ROUTE]: kubectl port-forward process stderr: I0320 09:40:36.564288   35778 log.go:184] (0xc000ae28c0) (3) Writing data frame
 +1ms
debug:   ▪ [PORT-FORWARD-ROUTE]: kubectl port-forward process stderr: I0320 09:40:37.603831   35778 log.go:184] (0xc0005fa420) Data frame received for 1
I0320 09:40:37.603860   35778 log.go:184] (0xc000afb7c0) (1) Data frame handling
I0320 09:40:37.603877   35778 log.go:184] (0xc0005fa420) (0xc000afb7c0) Stream removed, broadcasting: 1
I0320 09:40:37.603896   35778 log.go:184] (0xc0005fa420) Data frame received for 3
I0320 09:40:37.603906   35778 log.go:184] (0xc000ae28c0) (3) Data frame handling
I0320 09:40:37.603937   35778 log.go:184] (0xc0005fa420) (0xc000ae28c0) Stream removed, broadcasting: 3

Errors after connecting:
debug:   ┏ [CLUSTER]: broadcasting connection update E0320 09:24:56.497045   34601 proxy_server.go:147] Error while proxying request: context canceled

error:   ┏ [Metrics]: metrics not available Error: socket hang up +2ms
error:   ┃ [ 1] RequestError: Error: socket hang up
error:   ┃ [ 2]     at new RequestError (/Applications/Lens.app/Contents/Resources/app.asar/node_modules/request-promise-core/lib/errors.js:14:15)
error:   ┃ [ 3]     at Request.plumbing.callback (/Applications/Lens.app/Contents/Resources/app.asar/node_modules/request-promise-core/lib/plumbing.js:87:29)
error:   ┃ [ 4]     at Request.RP$callback [as _callback] (/Applications/Lens.app/Contents/Resources/app.asar/node_modules/request-promise-core/lib/plumbing.js:46:31)
error:   ┃ [ 5]     at self.callback (/Applications/Lens.app/Contents/Resources/app.asar/node_modules/request/request.js:185:22)
error:   ┃ [ 6]     at Request.emit (events.js:376:20)
error:   ┃ [ 7]     at Request.emit (domain.js:470:12)
error:   ┃ [ 8]     at Request.onRequestError (/Applications/Lens.app/Contents/Resources/app.asar/node_modules/request/request.js:877:8)
error:   ┃ [ 9]     at ClientRequest.emit (events.js:388:22)
error:   ┃ [10]     at ClientRequest.emit (domain.js:470:12)
error:   ┃ [11]     at Socket.socketOnEnd (_http_client.js:499:9)
error:   ┃ [12] {
error:   ┃ [13]   name: 'RequestError',
error:   ┃ [14]   cause: Error: socket hang up
error:   ┃ [15]       at connResetException (internal/errors.js:611:14)
error:   ┃ [16]       at Socket.socketOnEnd (_http_client.js:499:23)
error:   ┃ [17]       at Socket.emit (events.js:388:22)
error:   ┃ [18]       at Socket.emit (domain.js:470:12)
error:   ┃ [19]       at endReadableNT (internal/streams/readable.js:1336:12)
error:   ┃ [20]       at processTicksAndRejections (internal/process/task_queues.js:82:21) {
error:   ┃ [21]     code: 'ECONNRESET'
error:   ┃ [22]   },
error:   ┃ [23]   error: Error: socket hang up
error:   ┃ [24]       at connResetException (internal/errors.js:611:14)
error:   ┃ [25]       at Socket.socketOnEnd (_http_client.js:499:23)
error:   ┃ [26]       at Socket.emit (events.js:388:22)
error:   ┃ [27]       at Socket.emit (domain.js:470:12)
error:   ┃ [28]       at endReadableNT (internal/streams/readable.js:1336:12)
error:   ┃ [29]       at processTicksAndRejections (internal/process/task_queues.js:82:21) {
error:   ┃ [30]     code: 'ECONNRESET'
error:   ┃ [31]   },
error:   ┃ [32]   options: {
error:   ┃ [33]     timeout: 0,
error:   ┃ [34]     resolveWithFullResponse: false,
error:   ┃ [35]     json: true,
error:   ┃ [36]     method: 'POST',
error:   ┃ [37]     form: {
error:   ┃ [38]       query: 'sum(node_filesystem_size_bytes{mountpoint="/"} * on (pod,namespace) group_left(node) kube_pod_info) by (node)',
error:   ┃ [39]       start: '1647778740',
error:   ┃ [40]       end: '1647782340',
error:   ┃ [41]       step: '60',
error:   ┃ [42]       kubernetes_namespace: ''
error:   ┃ [43]     },
error:   ┃ [44]     headers: { Host: '7d72c0ee469feccc1e73fd2c04dd2fd1.localhost:63648' },
error:   ┃ [45]     uri: 'http://localhost:63648/api-kube/api/v1/namespaces/monitoring/services/monitoring-prometheus:9090/proxy/api/v1/query_range',
error:   ┃ [46]     callback: [Function: RP$callback],
error:   ┃ [47]     transform: undefined,
error:   ┃ [48]     simple: true,
error:   ┃ [49]     transform2xxOnly: false
error:   ┃ [50]   },
error:   ┃ [51]   response: undefined
error:   ┗ [52] }

Manually port forwarding the service works fine:

I apologize, it seems I forgot something crucial - node need to allow 9090 from the control plan because of how this works. Adding the security group rule fixed the issue. Closing.


Add CPack capabilities to CMakeLists.txt

Add several CPACK_BINARY_<GENNAME> options and package and package_source targets to configure and build SYCL-Bench packages.

We found we were creating packages quite often to run SYCL-Bench on different machines, so having a target for that may save some time in the long run.


aws-iam-authenticator no longer used, remove references from Dockerfile

I was told that aws-iam-authenticator was no longer used.  I see ARG related to the version and a curl pulling down aws-iam-authenticator in the Dockerfile.   Shouldn't this be removed?

viya4-iac-aws no longer requires aws-iam-authenticator. However, we support any BYO cluster. So, we need to keep it in case a customer brings a cluster that uses it.


Kumarabd/feature/helm

Description
This PR fixes #
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Is the .tgz file committed by accident? Also, can we place the chart under charts directory rather than helm?
The later is just for the sake of convention, can be ignored.

The tgz file is the helm package-d. Im having this in the repository for now to figure out which way to install the chart with the client. Im not naming it charts because we are having content specific to technology (helm).

The automated action need gh-page protected branch, a valid github repo admin token and a git configuration setup.
That is why I was saying to store charts in chart directory, all the automated actions follow the convention to search for charts in the chart sub-folder.


Combine I/B/P frames and motion vectors back to video?

Hello. I'm thinking about trying to use this in a machine learning project, and I'm wondering if I'd be able to extract all this information, do some processing on it, and then combine it back into video? As far as I know there's currently no way to do this

Hey JoeyBallentine,
what information exactly do you want to extract? The library provides the decoded frame, the motion vectors and the frame type (I/P/B) for each frame in the stream.
Combining the I/P/B frames and motion vectors to full video frames is exactly what the decoder does when playing the stream. For details on this, I can recommend the book "The H.264 Advanced Video Compression Standard" by Iain E. Richardson (ISBN: 978-0-470-51692-8).

My goal was to extract these things, feed them into a custom machine learning model, and have it spit out an upscaled version of everything that can be put back into video form.
Normally, machine learning video networks work on extracted frames as either individual images or sequenced of images. My goal was to work with the raw components of the video instead, but maybe that's just not feasible.

I see. You can certainly train a neural network or other ML algorithm on the motion vectors. In fact, I have tried that out in the past for the task of object tracking. I didn't get the model to train properly. But there are works on exactly this. For example, this object tracker: https://ieeexplore.ieee.org/document/8734056/ There are other works, which use extracted motion vectors for action recognition and object detection.

What I haven't seen so far but what would be very useful is an algorithm, which can track instance segmentation masks in a video based on motion vectors. The masks could either be rigidly tracked or deformed.

Closing due to inactivity. Feel free to reopen for further discussion.

@LukasBommes Thanks for great work. I also want to know if there is an algorithm that can take "I frames, motion vector " as input, then reconstruction the original video with dimention. [time, height, width, channel]


[HOTFIX] better support for large files

The issue was with variable scope when tracking if the cell is quoted or not. PR includes large file test.
fixes #39

correct me if I'm wrong, but the size of the csv in this PR is irrelevant
right? it just happens to contain a failing case on some of the lines?
ideally the cases can be identified and added to csv-spectrum
On Tuesday, December 22, 2015, Andrew Turner<EMAIL_ADDRESS>wrote:

The issue was with variable scope when tracking if the cell is quoted or
not. PR includes large file test.
fixes #39 https://github.com/mafintosh/csv-parser/issues/39
You can view, comment on, or merge this pull request online at:
https://github.com/mafintosh/csv-parser/pull/40
Commit Summary

hotfix support for large files

File Changes

M index.js
https://github.com/mafintosh/csv-parser/pull/40/files#diff-0 (6)
A test/data/large_file.csv
https://github.com/mafintosh/csv-parser/pull/40/files#diff-1 (7269)
M test/test.js
https://github.com/mafintosh/csv-parser/pull/40/files#diff-2 (9)

Patch Links:

https://github.com/mafintosh/csv-parser/pull/40.patch
https://github.com/mafintosh/csv-parser/pull/40.diff

—
Reply to this email directly or view it on GitHub
https://github.com/mafintosh/csv-parser/pull/40.

--
Sent from my phone

@maxogden, you're correct that the size is irrelevant. I was simply using the example file provided in Issue #39 . The purpose of this PR is purely to fix that issue where the parser does not process all lines in the file.

thanks for the fix. i agree that we should move the test to csv-spectrum at some point.

1.9.1

The issue has appeared again in 1.9.2

@vladimirkrasulya-planorama the tests seem to be passing? are we missing a case?

@mafintosh  I'm sorry - my input file was broken.


[fix:bug]:merge k8s-ingress-controller into a yaml file

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed ./mvnw clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #5179 (065edac) into master (c159ccd) will decrease coverage by 0.17%.
Report is 1 commits behind head on master.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #5179      +/-   ##
============================================
- Coverage     61.97%   61.81%   -0.17%
+ Complexity     8576     8557      -19
============================================
  Files          1243     1243
  Lines         37571    37557      -14
  Branches       3556     3551       -5
============================================
- Hits          23285    23216      -69
- Misses        12255    12311      +56
+ Partials       2031     2030       -1

see 27 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Added support for privilege key.

Short description outlining key changes/additions
Added support for privilege key.
JIRA Ticket Number
IDVA6-673
Type of change

[ ] Bug fix
[x] New feature
[ ] Breaking change
[x] Infrastructure change

Pull request checklist

[x] I have added unit tests for new code that I have added
[x] I have added/updated functional tests where appropriate
[x] The code follows our coding standards

An exhaustive list of peer review checks can be read here

CI: No security warnings found

CI: No security warnings found

CI: No security warnings found

CI: No security warnings found

CI: No security warnings found


[Crash] Guilded netherite

[Startup crash]
GameVer : 1.16.4
Fabric: Version: <IP_ADDRESS> (Latest)
Mods gilded-netherite-fabric-1.5.2.jar & netherite-plus-mod-1.1.0-1.16.4 https://www.curseforge.com/minecraft/mc-mods/gilded-netherite-for-fabric?page=2
gilded-netherite-fabric-1.5.2.jar + NP latest = Crash
gilded-netherite-fabric-1.5.1.jar + NP latest = Crash
gilded-netherite-fabric-1.5.0.jar + NP latest = Crash
gilded-netherite-fabric-1.4.0.jar + NP latest = Crash
netherite-plus-mod-1.0.0 + GN latest = Crash
netherite-plus-mod-1.1.0-1.16.4 + GN latest = Crash
netherite-plus-mod-beta-1.9.1 + GN latest = Crash
Crash log is for latest of both mods, with jumploader, modmenu, fabric api

latest.log

Yes I am aware of this and working the the gilded netherite dev on a solution, but I have some personal responsibilities I have to finish first. Expect a solution by Saturday.

That was fast, no problem at all, didnt see anything in issues on it or on the curse disc


Authentication with Google  option is not there

Sign up with Google button not showing

next is not start @iamparas0


Fix tomorrow to use Calendar.date(byAdding:to:) (Related to Issue #640)

Fixes method Date.tomorrow (Pair of #641 )
Checklist

[x] I checked the Contributing Guidelines before creating this request.
[x] New extensions are written in Swift 4.
[x] New extensions support iOS 8.0+ / tvOS 9.0+ / macOS 10.10+ / watchOS 2.0+.
[x] I have added tests for new extensions, and they passed.
[x] All extensions have a clear comments explaining their functionality, all parameters and return type in English.
[x] All extensions are declared as public.
[ ] I have added a changelog entry describing my changes.

          2 Errors

:no_entry_sign:
error: unexpected service error: The Xcode build system has crashed. Please close and reopen your workspace.

:no_entry_sign:
error: The Xcode build system has crashed. Please close and reopen your workspace.

          1 Warning

:warning:
The source files have been modified. Please consider adding a CHANGELOG entry if necessary.

          3 Messages

:book:
Thank you for submitting a pull request to SwifterSwift. The team will review your submission as soon as possible.

:book:
tvOS: Executed 502 tests, with 0 failures (0 unexpected) in 7.295 (10.518) seconds

:book:
macOS: Executed 366 tests, with 0 failures (0 unexpected) in 1.318 (1.676) seconds

  Generated by :no_entry_sign: Danger

Hey @AlexeiGitH, the tests you had updated were the yesterday tests, and since this is tommorow, can you update the relative tests? There was a conflict with master because of that solved on 957f7cf


Protocols?

Hello,
Does the RelyingParty have different protocols for Technical Profile element than what the Technical Profile actually supports?
For example,
According to this document the technicalprofile element only supports SAML2 or OpenIDConnect. However, when I Go to the technical profile page https://docs.microsoft.com/en-us/azure/active-directory-b2c/technicalprofiles it shows that the supported protocols are OAuth1, OAuth2, SAML2, OpenIDConnect, WsFed, WsTrust, Proprietary.

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

ID: 1e3ce49f-746e-9326-9846-32d569558b65
Version Independent ID: 4978d164-555d-b3cc-2989-5246b0f44313
Content: RelyingParty - Azure Active Directory B2C
Content Source: articles/active-directory-b2c/relyingparty.md
Service: active-directory
GitHub Login: @davidmu1
Microsoft Alias: davidmu

@Norrch2
Thanks for your feedback! We will investigate and update as appropriate.

@Norrch2 - The RelyingParty actually does only support a subset of the protocols that a TechnicalProfile supports. This is the example I got from engineering:  Client application -> OIDC, SAML -> Federated sign in -> OAuth1, OAuth2, OpenIdConnect, WsFed, WsTrust. The articles are correct.
#please-close

Thank you for the clarification. Perhaps the documentation can be updated to state that it only supports a subset of protocols :-) to prevent future confusion.

@Norrch2 - Thank you for the feedback. I have made a note to add the info to the article.


exec opt the topn nullable column order performance in  Heap Sort

Proposed changes
Reduce the virtual Function call in nullable column order by
Before：
exec 4.6s

After:
exec 2.7s

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

run buildall