How to use kafka connect with port 443?

This page is very helpful but it shows going through port 9093, which is fine but unfortunately my corporate VPN blocks that port. In production, no problem I'll be able to go to port 9093 but to build and test it I'm sort of hamstrung.
Is there a solution where a connector can go through AMQP on port 443 / websocket, instead of the 9093 kafka projection?

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

ID: a585d03f-fa14-f78f-65d7-c8a92b6f1c1f
Version Independent ID: 7420d0da-80c7-4289-68dd-b131baf3ee70
Content: Integrate with Apache Kafka Connect- Azure Event Hubs - Azure Event Hubs
Content Source: articles/event-hubs/event-hubs-kafka-connect-tutorial.md
Service: event-hubs
GitHub Login: @spelluru
Microsoft Alias: spelluru

Thanks for the ask  . At this time we are reviewing the ask and we will reply back as soon as we can .

Well, there might be, @justinmchase , but since the point of test environment is to make sure everything works for prod environment, having 2 different solutions might invite trouble.  To make test and prod as similar as possible, how about using a proxy to do Port Address Translation?
My colleague suggested using Network Virtual Appliance to do so.  It also comes in high availability flavor.

test

Its forbidden at the corporate level sadly. We have a global rule that sates all outbound traffic must be through port 80 or 443. Like I said once we push up to azure the systems there can communicate with 9093 fine but our internal systems including developer machines are affected.
I'm planning on writing an abstract called something like StreamService, which abstracts what I'm doing to call either Kafka when debugging locally or EventHubs when reaching out to azure. Its doable but honestly if there was a way for me to add some flags when provisiong the event hubs such as:
{
  "properties": {
    "kafkaEnabled": true,
    "ampqEnabled": false,
    "kafakPort": 443
    }
 }

I would probably do that and it would save me a lot of time and energy.

The point of the proxy is to let you go through 443 / 80 and then have something else change to 9093.

We will now proceed to close this thread as we have not heard back from you. If there are further questions regarding this matter, please tag me in your reply and reopen the issue. We will gladly continue the discussion.

Ok, thank you for your time. I do wish you'd take the feedback regarding changing the default kafka port to heart though, it would be very helpful if that was configurable in a variety of situations.


use deb822 format when using apt for installation

This PR:

replaces the One-Line-Style format with the deb822 format, which will be the default in Ubuntu 24.04. See eg https://discourse.ubuntu.com/t/spec-apt-deb822-sources-by-default/29333 and https://repolib.readthedocs.io/en/latest/deb822-format.html

I'm surprised that deb822 has been supported since Ubuntu 16.04 and Debian 9.

This is a new format supported by apt itself since version 1.1. Previous versions ignore such files with a notice message as described earlier.   ---https://manpages.ubuntu.com/manpages/xenial/man5/sources.list.5.html

This change should also be made in https://aka.ms/InstallAzureCLIDeb, but I can't find the source for that script.

It is managed by https://github.com/Azure/azure-cli/blob/dev/scripts/release/debian/deb_install.sh

@konstruktoid  Thanks for your contribution


merge from template-arlac77-github

package.json

chore(deps): add ^9.0.1 remove ^9.0.0 (devDependencies.npm-pkgbuild)

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

v1.10.92
GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Fix gpu usage in parallel bagging

Issue #, if available:
Description of changes:

Fix GPU usage in parallel bagging, remove hacked code.
Unified resource calculator for HPO and bagging
Moved resource calculator unit tests

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Job PR-1817-2 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1817/2/index.html

Job PR-1817-3 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1817/3/index.html

Job PR-1817-4 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1817/4/index.html

Committed by both @Innixma and @yinweisu. Both of us have reviewed the PR, but @Innixma won't be able to approve because he started the PR. Will merge with only one approval


[API] Add gettransactionsigners endpoint

Adds rudimentary support for determining which pubkey(s) correspond to the private key(s) that signed a given transaction input.
Currently it supports P2PKH and federation multisig transactions. Support for others can be added as needed; it is mostly the scriptPubKey comparisons that need to be amended. We have to take this approach because we don't know what the correct recId value is for the pubkey recovery without something to check against (in this case the prevOut's scriptPubKey).
This may also need better handling of the script verify flag values to truly support every transaction type (e.g. cold staking).

Ah, this is targeting the wrong branch, I'll fix that


Laravel 5.1: attachPermissions fails with "Unknown Column 'entrust_role_id'"

Hi,
When doing
$role->attachPermissions([$permission]);
from a database seed file, i get the following error:
 [PDOException]
  SQLSTATE[42S22]: Column not found: 1054 Unknown column 'entrust_role_id' in 'field list'

I managed to fix that, by altering the following file:
/vendor/zizaco/entrust/src/Entrust/Traits/EntrustRoleTrait.php
And add the correct foreign key to the relation at line 33 from
return $this->belongsToMany(Config::get('entrust.permission'), Config::get('entrust.permission_role_table'));

to
return $this->belongsToMany(Config::get('entrust.permission'), Config::get('entrust.permission_role_table'), 'role_id');

Now the migration runs properly. Did i miss something or is this a bug?
Regards

I had the same problem and your solution has worked.
Has this been accepted as an actual bug?

I, too, had this issue; adding the 'role_id' to the end of the function call worked as well.


Fuse.js constructor options typing are widened

Describe the bug
Typings of options allow to privide illegal options:
https://github.com/krisk/Fuse/blob/master/src/index.d.ts#L4
So currently this is possible:
new Fuse(items, {
  whatever: true
})

Is there a reason why not change it to:
declare class Fuse<T> {
  constructor(list: ReadonlyArray<T>, options?: Fuse.IFuseOptions<T>, index?: FuseIndex<T>)

?

Good catch. Will update.


Allow non-default databases in cloud bucket to be downloaded on first run

Currently a custom database can be specified using --index. However, this needs to be already available on a local filesystem. If no index is specified and the default (human-t2t-hla) is not cached locally, it is downloaded. It would be useful if applications depending on Hostile could override the default database such that a custom database could be automatically downloaded on first run of not already present.
Another way to do this would be to implement a database / fetch subcommand

Use environment variable to override default?

Leaning towards --index accepting either an index path OR a name of a standard index in the cloud bucket, if not already cached locally. An alternative is to have seperate args (e.g. --index and --custom-index for standard indexes referenced by name, or custom indexes referenced by path, respectively)

Complete, to be released in 1.0.0 shortly


The azure account was added via the deleted environment still shows well on the account panel

Storage Explorer Version: 1.15.0-dev
Build: 20200702.2
Branch: master
Platform/OS: Windows 10/ Linux Ubuntu 18.04/ macOS Catalina
Architecture: ia32/x64
Regression From: Not a regression
Steps to reproduce:

Launch Storage Explorer.
Open connect dialog -> Select 'Add New Environment' -> Next.
Input the environment a name and arm endpoint (https://management.azure.com) -> Click 'Next'.
Enter the credentials for one azure account.
Delete the environment then check the ACCOUNT MANAGEMENT panel.

Expect Experience:
The account was added via the deleted environment no longer be visible on the account panel.
Actual Experience:
The account was added via the deleted environment still shows well on the account panel.

Verified this issue on build 20200720.3. Reproduce. So we re-open it.

We have merged the fix back to master. This should not reproduce anymore.

Verified this issue on build 20200723.3. Fixed. So close it.


Bug located in ...

🔍 Before submitting the issue

[X] I have searched among the existing issues
[X] I am using a Python virtual environment

🐞 Description of the bug
I wanted to obtain a dynamic mesh, but what I ended up with was a static image .Additionally, I installed the trame module as required, but in the end, I still couldn't achieve it.
📝 Steps to reproduce

💻 Which operating system are you using?
Windows
📀 Which ANSYS version are you using?
2023r2
🐍 Which Python version are you using?
3.11
📦 Installed packages
pyfluent

We need to install the following packages: trame-vtk , trame-vuetify and ipywidgets along with trame for rendering in notebook.
https://github.com/pyvista/pyvista/issues/5848#issuecomment-2097245444

@XIAO-GUO-commint, did this solve your issue?


Unreal Engine Support

Add a client library for the Unreal engine (with compatibility for other C++ based game engines).

Some idea:

Have a visual blueprint as it can be found on the gamesparks plugin (I'm talking about the visible part of blueprint https://docs.gamesparks.com/getting-started/using-authentication/unreal-authentication.html).

Equally like gamesparks plugin have a visual blueprint function that allows automatic login via steam (via steamworks if install) on gamesparks this functionality retrieves the steamID and token and sends it to the server that checks via the api public steam. its very powerfull.

This is now online as a separate GitHub project - https://github.com/heroiclabs/nakama-unreal 🎉
Blueprints and a full test harness are in progress as a separate development sprint. I'll close this issue and any other questions/feature requests can be made on the separate repo.


Combine latest on some

In conversation with @ordirules and @mrocklin
The idea is that you may only want combine latest to trigger on some of the updates.

I think for simplicity, maybe combine_latest should just assume that you only emit on the first child, which means changing this line in combine_latest:
        if not self.missing and who == self.children[0]:

thus this will emit once:
s1 = Stream()
s2 = Stream()
sout = s1.combine_latest(s2)
sout.map(print)

s2.emit(1)
s1.emit(1)

In the long run, I think a trigger should be added. Perhaps add a trigger flag to the buffer stream element?
What do you think? I think it's simpler than anything else I can think of. Also, we should fork streams itself (separate from event model). It could be on your or my branch, up to you.

There are definitely cases where people want to emit on updates from
multiple children.  I think that one would take in a list of booleans in a
trigger= or emit_on= keyword for which children should activate an emit.
On Mon, Jun 12, 2017 at 10:52 AM, Julien Lhermitte<EMAIL_ADDRESS>
wrote:

I think for simplicity, maybe combine_latest should just assume that you
only emit on the first child, which means changing this line in
combine_latest:
    if not self.missing and who == self.children[0]:

thus this will emit once:
s1 = Stream()
s2 = Stream()
sout = s1.combine_latest(s2)
sout.map(print)
s2.emit(1)
s1.emit(1)
In the long run, I think a trigger should be added. Perhaps add a trigger
flag to the buffer stream element?
What do you think? I think it's simpler than anything else I can think of.
Also, we should fork streams itself (separate from event model). It could
be on your or my branch, up to you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mrocklin/streams/issues/22#issuecomment-307813570,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AASszNoW7QmX8K82PjNuecizgG-3bscfks5sDVCrgaJpZM4N124G
.

I like the idea of a kwarg for this.
I guess it would be like:
emiting_children = [child for child, t in zip(self.children, trigger) if t is True]
if not self.missing and who in allowed_emiting:

Sorry yes, that was too restrictive. I like that too.
Maybe have the keyword be the list (or one element) of numerically ordered children as a compromise?
(so s.combine_latest(emit_on=0) would be fine)
I suggest a PR somewhere? Maybe @CJ-Wright self-PR from your feature branch to your master and we can work from there? (Unless @mrocklin  you want to do it)

Closed by #32


When we upgrade to webpack v5 I can live in Norway for free.

@vikiival told me that when we upgrade to webpackV5 I can live in Norway for free.
jk, we can drop some packages like ...
Originally posted by @yangwao in https://github.com/kodadot/nft-gallery/issues/2653#issuecomment-1077491946

remember that webpack can be replaced by #1418, it would speedup development server and improve performance

Love to have Vite && Vitest in the repo

Closing in favour

#3908


Fix mk-cacerts.sh Solaris sed failure and escaped subject commas

Fixes https://github.com/adoptium/temurin-build/issues/3418
Solaris sed does not recognise [[:space:]]
and don't split on escaped commas (\,) in the subject

Test Solaris build: https://ci.adoptium.net/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-solaris-x64-temurin/347/


Lokalise: Translations update

This pull request was initiated by Lokalise (user Tian) at 2019-03-23 06:01:33

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


From Categories: + Add Phrase Button OnClick Action

User Story: As a user, I want to enter in a phrase using a keyboard so that I can add a phrase to any category. (note: this keyboard is the same one throughout the app but with one difference noted in the AC)
Acceptance Criteria:

When the "+ Add Phrase" button is selected by head-tracking or touch, a keyboard screen opens

This keyboard does not have the star option
This keyboard has a checkmark option to indicate saving of the phrase
The design doesn't reflect this but in discussion the team wanted to keep the speak button on this screen

If the user does not input any letter from the keyboard, the checkmark should not be clickable to save the phrase (disabled state)
Once the user starts to input any letter, the checkmark changes to an active state with background color "Active green" and font color "Primary Purple"
User can use head tracking or type to write a phrase
If user selects (x) on the keyboard it erases the last letter.
If the user selects trash on keyboard, it clears all text
If user types at least one letter and exits, an alert message appears to ask the user to confirm if they want to exit
If the user exits without typing anything, there is no alert message and they are taken back to preset category where they opened the keyboard from

Design:
Keyboard Disabled Checkmark
Keyboard Active Checkmark
Exiting Without Saving Alert

@Ly-Kyli What does "similar keyboard" mean in the User Story?

@Ly-Kyli What does "similar keyboard" mean in the User Story?

Just updated the ticket. It means the same keyboard with a slight difference. We are replacing the star option with the checkmark instead.


Recommendations for production deployment

Description:
Bhathiya mentioned that there needs to be a document that lists the recommendations for production deployment, such as the following.

A distributed API Manager setup or at least an active-active node deployment.
At least a 2-node cluster of API Gateways in a distributed setup.
The reason for this recommendation is that out of all the components of the WSO2 API Manager distributed setup, the API Gateway is the most critical because it handles all inbound calls to APIs.

Please note that PR [1] only addresses the formatting in the en/docs/install-and-setup/perfromance-tuning-and-test-resu… …
…lts/tuning-performance page. This doc gap still exists.
[1] https://github.com/wso2/docs-apim/pull/798

@RakhithaRR , please work on this task.

This[1] is our current list, and we need to improve that. We can get feedback from people who recently did production deployments before starting this. I will share this with some such people and try to get feedback.
[1] https://apim.docs.wso2.com/en/latest/install-and-setup/setup/deployment-best-practices/production-deployment-guidelines/#common-guidelines-and-checklist

@gayanlggd

Since the latest APIM verision are heavily depending on traffic manager component, please mention the details such as ports and connections required in distributed setup. Specifically ports are not mentioned in the firewall rules section.
When using external KM as 3rd party KM, explain how the communication is happening. This may be not related to the production guideline, but general deployment pattern docs.

Some configurations are defined with no explanation of what they are doing. It would be nice to add a sentence or two briefly explaining its use.
e.g. Step 9 in https://apim.docs.wso2.com/en/latest/install-and-setup/setup/single-node/configuring-an-active-active-deployment/

Explicitly explain the minimum and maximum number of keystores needed. Additionally, state the commands for how a Primary keystore can be defined with required keyUsages.

In the database specific configurations explicitly mention that the databases and the users have to be created using an admin user and to grant privileges and then use the specific users to create tables, configure in deployment.toml.
https://apim.docs.wso2.com/en/latest/install-and-setup/setup/setting-up-databases/changing-default-databases/changing-to-mysql/


Add requirements for Key Vault (soft delete and purge protection) to doc

Hi team, in the Portal version of this document (deploying/enabling SSE CMK), I see that there is no mention of Key Vault requirements. However, in the PS version here, the requirements for the Key Vault (more specifically, soft delete and purge protection) are listed. Is this something that can be added?
From what I understand, clicking the banner in step 8 here will apply those permissions:

However, I think it would still be nice to have this included in the restrictions or wherever may be appropriate in this document, since customers can specify this during Key Vault deployment time.
Thank you as always!!

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

ID: 86428829-cdc2-eb90-2b47-4ab5f73ea5a0
Version Independent ID: 64768b9c-96aa-d455-161d-fe5d194900de
Content: Use the Azure portal to enable customer-managed keys with SSE - managed disks - Azure Windows Virtual Machines
Content Source: articles/virtual-machines/windows/disks-enable-customer-managed-keys-portal.md
Service: virtual-machines
Sub-service: disks
GitHub Login: @roygara
Microsoft Alias: rogarana

@nickmcmahan Thank you for your feedback . We will investigate and update the thread further.

@nickmcmahan Thank you for your feedback. We will have discussion internally and will make necessary changes as per your ask.
Further for clarification when you are creating a Key Vault in Azure you do get an option of Purge and soft delete at the time of Key Vault creation as below:

So initially you can specify the settings for Key Vault at time of creation specifically for purge protection and soft delete in portal.
Coming to the later part the Key Vault has something called as Access Policies which grant a user, group, or application access to execute specific operations for keys or secrets in a key vault.You can refer to this for more information.
You can add the user or application or Service Principle to Access Policies in order to get them access on the Key Vault to retrieve secrets,keys and certificates.
In the suggested article once the Disk Encryption Set is created the pop up is just for adding this Service Principle to the Access Policies in Key Vault which you might need in order for Keys and Certificates to get retrieved. Just like in below example once I have created the Disk Encryption Set named "test" following the suggested article and  click on pop-up this is adding test to the Access Policies of Key Vault

Do let me know in case you have any further concerns on same.

Hi @psmanhas - thanks for the quick turnaround on this! Much appreciated.
The idea to submit feedback for this article actually came from my own mistake when I was deploying a new environment for testing. When I initially created the Key Vault following the Portal doc, I unchecked the soft-delete and purge protection so that when I was done with my test environment, I could quickly delete all my resources without having those soft-delete protections get in the way (since you can't delete the whole resource group when those are enabled due to retention). After reviewing the other docs, I found the requirement for soft-delete and purge protection in the CLI article, and I also see it's in the PowerShell article.
Just for some background, the reason I mentioned the popup banner is because I think the pop-up also adds soft-delete and purge protection as well (as long as you haven't already added an access policy) - this was something I found out when I was troubleshooting why it didn't work (I had created the access policy through Azure CLI, since that's my usual preferred way of doing things - the red banner still appeared even though I applied the necessary permissions using the CLI, more specifically az keyvault set-policy -n $desName -g $desRg --object-id $desSp --key-permissions get wrapkey unwrapkey - and it turns out that the banner was appearing because I didn't enable soft-delete + purge protection on the KV).
No concerns from me, I appreciate your time in taking a look at this.

@nickmcmahan  I have assigned the issue to content author to check and update the document as appropriate.We will update you accordingly.

@roygara As per our discussion can you please check and add your comments on this doc update request as applicable.
Thanks

@nickmcmahan Thanks for reaching out and making us aware of this, we appreciate it! :)
We've gone ahead and updated the article to include this information, those changes are live right now.
Accordingly, I'll close this out.
Again, thanks for pointing this out and helping us improve the docs, we appreciate it!
#please-close


Improvements for the Ballerina Project Overview

Description:
Design improvements to be considered.

Can we add test details? (Have to comply with the lowcode diagram)
The difference between multiple projects on the project view is not clearly visible
Try to replace the visitor with the semantic model, as mentioned in https://github.com/ballerina-platform/ballerina-lang/pull/27488. (A current limitation is reported in https://github.com/ballerina-platform/ballerina-lang/issues/27493)

Suggested Labels:

Suggested Assignees:

Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

Removed the project overview https://github.com/ballerina-platform/plugin-vscode/issues/123.

Removed the project overview https://github.com/ballerina-platform/plugin-vscode/issues/123.

We'll be introducing the project overview again.

Description:
Design improvements to be considered.

Can we add test details? (Have to comply with the lowcode diagram)
The difference between multiple projects on the project view is not clearly visible
Try to replace the visitor with the semantic model, as mentioned in ballerina-platform/ballerina-lang#27488. (A current limitation is reported in ballerina-platform/ballerina-lang#27493)
This was addressed with https://github.com/ballerina-platform/plugin-vscode/pull/288

Suggested Labels:
Suggested Assignees:
Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:


move pytorch_lightning >> lightning/pytorch

What does this PR do?
this will alow easier developing lightning in future with lower developer overhead
Before submitting

[x] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] Did you list all the breaking changes introduced by this pull request?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃
cc @borda @carmocca @akihironitta

pre-commit is failing

updating the path :+1:


How to make a link load its content in "_top"?

I have a ModernTab control, to which I'm dynamically adding a Link:
InstallationTab.Links.Add(new Link { DisplayName = "Review Configuration", Source = new Uri("/Views/InstallationProgress.xaml", UriKind.Relative) });

I'd like InstallationProgress.xaml to load in the top frame instead of the current content frame.
How can I do this?

I answered my own question, in case anyone else finds themselves here:
This is just one example of "hijacking" the click on the ModernTab. Here, you can force the content to load in the top frame, for example:
Handle the SelectedSourceChanged event of the ModernTab:
MyModernTab.SelectedSourceChanged += MyModernTab_SelectedSourceChanged;
void MyModernTab_SelectedSourceChanged(object sender, SourceEventArgs e)
{
    if (e.Source.OriginalString.EndsWith("Foo.xaml"))
    {
        var url = "/Pages/Foo.xaml";
        var bb = new BBCodeBlock();
        bb.LinkNavigator.Navigate(new Uri(url, UriKind.Relative), this, NavigationHelper.FrameTop);
    }
}


Reducer: in for loop header condition, i < int(1.0) → i < 1

This:
for (int i = 0; i < int(1.0); i++) {}
Could be reduced to:
for (int i = 0; i < 1; i++) {}

PR #403 addresses this.

Fixed via #403


Optimize set union and intersection

For intersection: take the smaller set, and check each element
exists in the larger set.
For union: take the larger set, and append missing elements from
the smaller set.
Similar optimizations exist in Rust's HashSet.

@bors r+
Thanks!

:pushpin: Commit d5cc5a8395801f9b9cdc761ff85688538d7c89ee has been approved by Amanieu

:hourglass: Testing commit d5cc5a8395801f9b9cdc761ff85688538d7c89ee with merge 2c60ecb9d9712543baded0d4d766a1d38b66d34c...

:sunny: Test successful - checks-travis
Approved by: Amanieu
Pushing 2c60ecb9d9712543baded0d4d766a1d38b66d34c to master...


observation.taxon not set correctly

With this observation, the Obs ID is S. valerandi, but the CID is S. parviflorus. Perhaps something got weirded by the taxon swap?

https://www.inaturalist.org/observations/6520438 seems to now be working properly (ie RG at S. parviflorus). Was this fixed or did it fix itself?

It was "fixed" I think by wdvanhem's ID. Prior to that the observation.taxon was S. valerandi.

Thanks tony,
I spent some time investigating the situation pre wdvanhem's ID
I think it could be fixed by changing
https://github.com/inaturalist/inaturalist/blob/master/app/models/observation.rb#L1584 to
i.taxon_change_id.nil? && i.disagreement == false && i.previous_observation_taxon && i.previous_observation_taxon.ancestor_ids.include?( id_taxon.id ) && !i.taxon.ancestor_ids.include?( id_taxon.id )
ie conservative_non_disagreements must:

not be from taxon_changes AND
not be disagreements AND
have previous taxa AND
previous taxon must be descendants of the taxon AND
must not be descendants of the taxon

seems sensible with https://staging.inaturalist.org/observations/6520438 and https://staging.inaturalist.org/observations/10220495 at least
let me try to get my local instance current so I can investigate more


Issue/57

Coins Display has been changed

Header color changed

Buttons send and receive fixed

Animation for coins fixed

@ankushdharkar , The merged changes is not updated in crypto site, is
there any prod deployment failure issue?


move regedit to optional dependencies

On Osx npm install regedit fails. Hence moving regedit to optional dependencies and vstest tests to execute only on windows

Approved once review is fixed


Update bundle extension

It's now .dab, for Distributed Application Bundle.

There's some text in experimental/docker-stacks-and-bundles.md that references .dsb, otherwise LGTM

LGTM once experimental/docker-stacks-and-bundles.md is updated

LGTM 👼
Doing a follow-up for the experimental documentation :wink:


Publish v1.0.0

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

Comparison is base (dc8c1f9) 100.00% compared to head (85afa40) 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##              main       #43   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           21        21
  Lines          239       239
=========================================
  Hits           239       239

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


[Bug]: Call for std::move for non-moveable types

Describe the issue
Hi!
I've mentioned that abseil-cpp sometimes is trying to call for std::move for non-moveable class types so std::move calls for copy-ctors.
Examples:
/home/exactlywb/abseil-cpp/absl/flags/marshalling.cc:158:24:   required from here
/home/exactlywb/abseil-cpp/absl/strings/internal/str_split_internal.h:268:25: warning: classtype absl::string_view has no move constructor [-Wclobbered]
   268 |       : text_(std::move(input_text)),
          |                         ^~~~~~~~~~
 13 /home/exactlywb/abseil-cpp/absl/strings/internal/str_split_internal.h:268:24: note: ‘std::move’ i    s going to call for a copy constructor
   268 |       : text_(std::move(input_text)),
          |               ~~~~~~~~~^~~~~~~~~~~~

and another one:
/home/exactlywb/abseil-cpp/absl/strings/internal/cord_rep_consume.cc: In function ‘void absl::cor    d_internal::ReverseConsume(CordRep*, ConsumeFn)’:
/home/exactlywb/abseil-cpp/absl/strings/internal/cord_rep_consume.cc:57:33: warning: classtype ha    s no move constructor [-Wclobbered]
    57 |   return Consume(rep, std::move(consume_fn));
         |                                 ^~~~~~~~~~
/home/exactlywb/abseil-cpp/absl/strings/internal/cord_rep_consume.cc:57:32: note: ‘std::move’ is     going to call for a copy constructor
    57 |   return Consume(rep, std::move(consume_fn));
         |                       ~~~~~~~~~^~~~~~~~~~~~
/home/exactlywb/abseil-cpp/absl/strings/internal/cord_rep_consume.cc:45:38: note:   initializing     argument 2 of ‘void absl::cord_internal::Consume(CordRep*, ConsumeFn)’
    45 | void Consume(CordRep* rep, ConsumeFn consume_fn) {
         |                            ~~~~~~~~~~^~~~~~~~~~

absl::string_view and absl::FunctionRef don't have move constructor. Excerpt from standard:
If the definition of a class X does not explicitly declare a move constructor, a non-explicit one will be implicitly
declared as defaulted if and only if
(8.1) — X does not have a user-declared copy constructor,
(8.2) — X does not have a user-declared copy assignment operator,
(8.3) — X does not have a user-declared move assignment operator, and
(8.4) — X does not have a user-declared destructor.
[Note: When the move constructor is not implicitly declared or explicitly supplied, expressions that otherwise
would have invoked the move constructor may instead invoke a copy constructor. — end note]

Steps to reproduce the problem
I've used gcc with own patch.
What version of Abseil are you using?
f39f340c589354db8ab2f07894894f23c9ea3ae6
What operating system and version are you using?
ubuntu
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.6 LTS
Release:	20.04
What compiler and version are you using?
11.2 + own patches
What build system are you using?
cmake version 3.16.3
Additional context
No response

Is this -Wclobbered warning something that exists only in your patched gcc? I can't reproduce it.
Fixing the second example is straightforward. The first example is in templated code that uses either std::string or absl::string_view. It seems to rely on the following:

[Note: When the move constructor is not implicitly declared or explicitly supplied, expressions that otherwise
would have invoked the move constructor may instead invoke a copy constructor. — end note]

std::is_move_assignable<absl::string_view>::value returns true in my testing. Why should this be changed?

Is this -Wclobbered warning something that exists only in your patched gcc? I can't reproduce it.

Yes. This warning is reproducible only in my patched gcc and can't be reproduces with the regular one.

Fixing the second example is straightforward. The first example is in templated code that uses either std::string or absl::string_view. It seems to rely on the following:

[Note: When the move constructor is not implicitly declared or explicitly supplied, expressions that otherwise
would have invoked the move constructor may instead invoke a copy constructor. — end note]

std::is_move_assignable<absl::string_view>::value returns true in my testing. Why should this be changed?

I am agree with you that the first example doesn't need to be fixed and the behavior is founded on the following note. Anyway, the second example looks redundant. Don't you think that it looks better to remove calling std::move for ConsumeFn?

I am agree with you that the first example doesn't need to be fixed and the behavior is founded on the following note. Anyway, the second example looks redundant. Don't you think that it looks better to remove calling std::move for ConsumeFn?

Yes. I think the second example is probably a vestigial std::move that was once correctly called on std::function. It will be removed by a pending change.


Fix some psalm findings

Q
A

Type
improvement

BC Break
yes/no

Fixed issues

Summary

Some other fixes for https://github.com/doctrine/mongodb-odm/pull/2329

Thanks @franmomu!


Road to CI: Automate Docs

Automate the rendering, generation of docs after #64.

ReadTheDocs is building the docs automatically once there is an update on the main branch of this repo. So this is closed. :)


Cannot create event without saving event first

If we save an event and action at the same time (i.e. haven't clicked save before adding action) the ui gets some error. @davepagurek  has context.

Fixed now


502 wrongly returned from change_upstream_proxy

Steps to reproduce the problem:

Use something like "mitmproxy -U http://localhost:8082/ -s change_upstream_proxy.py" to point mitmproxy to a non-existing upstream proxy.
Attempt to use that mitmproxy to connect to the alternate, real upstream you specified in change_upstream_proxy.py.
Notice that fails with 502.
Try again with a -U argument of a different, but real upstream proxy.
Now it works.

What is the expected behavior?
It should connect to the alternate upstream in change_upstream_proxy.py instead of returning 502
because of the deadness of the proxy specified with -U.
What went wrong?
From my new-to-mitmproxy perspective it looks like an optimization that usually makes sense, except in the case where one wants to change proxies.
Any other comments?
For context, my eventual goal is an evil smart proxy load balancer.  The smarts would include gathering metrics, for example of what proxies get blocked by whom and when, then store that for offline analysis.  Then later perhaps use that data to make a smarter proxy load balancer.
As I'm new to mitmproxy, any guidance would be appreciated.  Especially if somebody has already done this, yet eluded my google-fu.

refs #548

Thanks, this is fixed on master now (with a slightly different syntax). :smile:


Convert code to Typescript

This will allow us to make use of interfaces to bring type-safety and object completion for parsed JS object in editors.

thanks for expressing your interest. I assigned it to you. @aabhas-sao

Hi Folks, This issue is still open. Please comment on this if anyone wants to work on it and I can re-assign. Thanks!

Hi @nsinghal12 Could you assign this to me please


MB-1921: enable prime contractor to access prime api

Description

Create a new docker-compose file that will run the various docker builds and spin up the prime api
Create a script that will run the new docker-compose file and generate test data
Add a new Make command to run the script

Reviewer Notes
This is my first rodeo with Docker as well as making a new script and make command so keep a keen eye.
Setup
make run_prime_docker
rm -rf bin/prime-api-client && make bin/prime-api-client
prime-api-client --insecure fetch-mtos | jq

Code Review Verification Steps

[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Thanks, @chrisgilmerproj. I will apply those suggested changes. As for documentation, there's an already written story to take care of this. I'll add your reference to the story.

Thanks, @chrisgilmerproj. I will apply those suggested changes. As for documentation, there's an already written story to take care of this. I'll add your reference to the story.

As a general rule I prefer documentation to come along with the code changes. Then I can test the documentation while I'm testing the code. Until I see the docs I'm probably not going to approve this to move forward.

@chrisgilmerproj, understood. This was going to be just a small piece of the aforementioned doc but I'll at least write documentation on how to run this docker.

@chrisgilmerproj, understood. This was going to be just a small piece of the aforementioned doc but I'll at least write documentation on how to run this docker.

Yep, that's all I'm asking for. Just make small incremental steps on docs so that we always have them available.

Putting WIP tag until I figure out if this should open up access to the web applications.


1.3.0 Beta 1 Android Release - Different APK Signature

Hello,
I tried upgrading to the newest 1.3.0 Beta release, Beta 1, on my Android phone, but it the installation failed. After looking at the Android logs through ADB logcat, it indicated that the Beta 1 release is signed with a different signature than that of 1.2.0. Is there any possibility to continue signing with production/release signatures?
Thanks!

Hello,
I tried upgrading to the newest 1.3.0 Beta release, Beta 1, on my Android phone, but it the installation failed. After looking at the Android logs through ADB logcat, it indicated that the Beta 1 release is signed with a different signature than that of 1.2.0. Is there any possibility to continue signing with production/release signatures?
Thanks!

I assume you downloaded the beta from GitHub and not Google Play, correct? If so, it may have just been an issue with that build. When we release the next beta, I'll be sure to make sure the sigs are the same. TBH I'm not sure why they were different with this one... was built the same way

I don’t know if this was just an eff up, but this should be fixed. Google Play and Github have different signatures, that is intended


Smod tries to read my dependency dll as a plugin, it did not before 3.1.11

Aka a dll I have placed inside /sm_plugin/dependencies

should be sm_plugins not sm_plugin

That was just a typo on here, the folder is correct on my end.

can you post the MA log

2018-09-07_19_24_MA_output_log.txt
[19:24:41] ServerMod2 Plugin Manager initializing...
[19:24:41] ServerMod2 v3.1.14-A Plugin Manager initialized
[19:24:41] Loading config...
[19:24:41] [19:24:41] [ERROR] [PLUGIN_LOADER]  Failed to load DLL [C:/Users/Karl/Desktop/scpserver/SCPSL_Data/../sm_plugins/dependencies\Newtonsoft.Json.dll], is it up to date?

[19:24:42] [19:24:42] [INFO] [PLUGIN_LOADER]  Plugin loaded: SCPDiscord(karlofduty.scpdiscord)

[19:24:42] [19:24:42] [INFO] [karlofduty.scpdiscord]  Enabling plugin SCPDiscord 0.3.1

[19:24:42] [19:24:42] [INFO] [karlofduty.scpdiscord]  SCPDiscord 0.3.1 enabled.

[19:24:42] Selected central server: GRA (https://gra.scpslgame.com/)
[19:24:42] ServerMod - Version 3.1.14-A
[19:24:42] SCP:SL - Version 7.3.1 (Revision I)
[19:24:43] Port queue loaded: 7777, 7778, 7779, 7780, 7781, 7782, 7783, 7784
[19:24:43] Trying to init port: 7777...
[19:24:43] Done!

Fixed


Test 'noCancel' behavior to prevent #5344

We should probably rewrite the relevant code to make it easier to extract requests; that sounds less effort than screwing around with test/assert.js.

Originally posted by @Zarel in https://github.com/Zarel/Pokemon-Showdown/pull/5345

saves lastRequest emitted by Side
renames currentRequest to requestState (open to naming suggestions) to avoid confusion with lastRequest, given they are different shapes
check noCancel state in tests - some tests seem to have uninuitive noCancel behavior - added comments and left as FIXME for now. NOTE: Not sure if the implementation or tests are actually incorrect or if I don't understand the intended behavior, but I figured I'd highlight.

RE: maybe-cases
Being unable to cancel only applies if the player chooses to move/switch when that Pokémon is maybe-disabled/maybe-trapped, respectively, so the global noCancel shouldn't be true.
However, it could be tested if noCancel were a per-Pokémon flag of the form true | 'move' | 'switch'. (Is it worth it?)

I'm OK just commenting about why the maybe-cases are they way they are for now. Extending it seems useful, but a little more work than my immediate goal of regression testing #5344.

Maybe activeRequest is a better name than lastRequest? Also requestState is tracked inside it, right? No need to track it separately.

requestType would be best imo. The names activeRequest and lastRequest suggest that it's the actual object returned by getRequestData().

activeRequest/lastRequest is the actual data returned by getRequestData(), isn't it?

Oh, mb

Maybe activeRequest is a better name than lastRequest?

I may be confused about the ordering here - requestState is the request we're currently building, and lastRequest is the request which was sent. We refer to the current requestState to be able to build lastRequest. I don't think active is accurate?

Also requestState is tracked inside it, right? No need to track it separately.

No? The emitted request shape differs depending on the requestState ('switch' requests have 'forceSwitch': true', 'teampreview' requests have 'teamPreview': true, 'move' request have 'active'), but its not explicit.

activeRequest is the request that we're waiting for a response for. In fact, when commitDecisions is called, activeRequest should be cleared.

Done. I was wrong, I didn't think that would work.
I know you don't like getters, but it really seems logical in this case... (and also means I don't need to modify the request object and/or change a zillion callsites to be more verbose)

I would have solved this by actually adding a type property on the activeRequest.


Style theme used for d3fc-showcase

Styling similar to Techan.js. Implement a more professional UI.

Closing as this is replaced by smaller tasks with the new UX design.


Implement Service Provider SAML Component

Is your feature request related to a problem? Please describe.
Yes, Only Identity Provider implementation is supported now, need to implement the Service Provider side of Component

Generating Authnrequest(signed/unsigned) for both Post/Rediect method
Parse and validate  SAML Response
Generating LogoutRequest(signed/unsigned) for both Post/Rediect method
Parse and validate  LogoutResponse
SP Metadata

Describe the solution you'd like
Implement Service Provider component.

@mayankagwl also this one. Can you guide me in implementing this? I want to contribute. Thanks

@avats-dev As go-saml module currently only supporting the Identity provider implementation (Like validate AuthnResponse, Generating SAML Response etc)
So we need to implement Service Provider side of Implementation as well (Like Generating AuthnRequest, Validatinig SAML Response etc).
To know it more you from below
https://en.wikipedia.org/wiki/SAML_2.0


Catching errors based on Error.name

I was thinking that in many cases, it might be more convenient to use a String to catch errors rather than constructors, and the reason is that when it comes to modules, you actually need to export modules, making it much more cumbersome to type. Compare the following:
Promise.resolve(foo)
.then(() => { ... })
.catch(MyModule.errors.MyFirstError, err => { ... })
.catch(MyModule.errors.MySecondError, err => { ... })
...

vs:
Promise.resolve(foo)
.then(() => { ... })
.catch("MyFirstError", err => { ... })
.catch("MySecondError", err => { ... })
...

Where in the first catch err.name === "MyFirstError" and in the second catch err.name === "MySecondError".

Bluebird 3.0 supports something similar. Assuming you don't want to alias and import the errors directly anyway:
  promise.catch({name: "MyFirstError"}, err => { ... }); // valid Bluebird 3

Thanks for the suggestion. https://github.com/petkaantonov/bluebird/issues/499

I see, that's very useful! Still, different modules might expose error constructors differently or not at all, and then using the whole {name: "MyFirstError"} syntax would be rather verbose when you could just use "MyFirstError" as a string, would it not? It would only be a matter of converting "MyFirstError" -> {name: "MyFirstError"} internally when passed a string parameter, would it not?

let {MyFirstError, MySecondError} = MyModule.errors;

Promise.resolve(foo)
.then(() => { ... })
.catch(MyFirstError, err => { ... })
.catch(MySecondError, err => { ... })

Seems to work just fine. Would it not?

Interesting, I didn't know that ES6 construct, I actually like it :)
Yeah, that would work in most cases I presume, but you still need to explicitly alias the constuctors each time, maybe in many files with many different modules which expose their error constructors in different manners (maybe across different objects...). I mean, in a language like Java it would really make sense to do all that explicitly, but I'm not sure aliasing the constructors is true to the spirit of Javascript...
The other question would be, what are the objections to being able to pass a string as a parameter to catch?

@perrin4869 there are many benefits

With ES6 imports can be statically checked for correctness / typos. Strings cannot
With JSHint error names that refer to variables can be checked for typos. Strings cannot.
If you add TypeScript or Flowtype later, errors can be refactored (renamed or moved) and leftover renames and moves can be pointed out by the typechecker. Strings cannot.

Oh, I never argued to choose one over the other, I just think it would be great if we had all three of them available since it'd be so trivial to do and it would make sense to use it in many cases. I mean, is there any reason to have clients who want to match errors based on their names all implement the predicate function above, let errName = name => err => err.name === name and then pass errName("MyError"), when you could handle string arguments to behave just that way?

The first 4 reasons refer to the pitfalls of using strings when refactoring.
And... I know this feature is just one little thing. Its true, by itself its not a big deal at all - its quite trivial to implement, really. But there've been hundreds of feature requests like this, and they really add up after a while. They contribute to library bloat and API documentation bloat, and sometimes make it harder to reason about all the potential interactions. So they aren't really free.
P.S. If it were really up to me, I would also remove the object matching functionality. Most of the people I recommend Bluebird to don't find the lack of features a problem (save for a few fundamental ones like cancellation). Their objection is more like "oh its too huge, the API is too complex, I need something simpler" - but they normally don't open issues here and look elsewhere instead :(
I guess the two choices to deal with this this are:

a. start removing some features, and
b. be selective when adding new ones, and
c. look into splitting off more specialised functionality into separate related libraries

embrace the bloat

What we're doing now is just 1.b. and that probably doesn't make sense by itself...

Well no I totally agree with 1a and 1b and each single feature has to be judged on its own merit on a case by case basis, and if my suggestion doesn't cut for you guys then that is that... But you know, the more I learned about bluebird and read the documentation, the more interesting and useful features I kept finding! I'm sure I used most of the features available in bluebird in my current project... and there were times where I was wishing for features like being able to simulate something like async.series with promises by passing functions that return promises or something... And I never opened an issue because I felt that it really is not justified to have that in, just as a personal opinion even though it might save me a few lines of reduce code here and there and might slightly increase readability...
So going back to the error matching problem, now that I think about it, if you are giving people the option to use predicate functions then the object matching functionality does seem somewhat redundant after all although it could improve readability in some cases... Still, error names are such a defacto standard in Javascript that I maintain that matching them in catch clauses would not really be a bloat

@perrin4869  Are you sure its so common for everyone, or is it a particular problem you have with libraries that don't export their errors, or the way you have those libraries arranged in the modules? I've personally had no trouble importing error types (and predicates) and using them, so I find it hard to see any benefit at all. I know its just a difference in perspective...
regarding the rest of my comment it was off topic so I moved it to https://gist.github.com/spion/294bb53db70bd700b0c4 . (Unfortunately the solution I came up with doesn't apply to this issue as its impossible to move such a feature into a separate lib)

Well, the only problem I have with ES6 exports is that unfortunately, they do not yet work natively in node.js, even the newest 4.1.x versions, so they are not a viable solution yet.
OK, my very last pitch to supporting strings in catch clauses will be that there are times when constructors are just not available at all. For example, take socket.io. If, say, the client gives a callback to their emit to the server, and the server throws and error and wants to hand it to the client, the error gets serialized and sent back as json to the client... This is what I mean:
client.emitAsync('login', credentials)
.catch(err => err.name === 'RetryLoginError', err => { ... })

Of course this means that the client can't have a constructor because the error they got is not an instance of Error, and it could never be. At that point, the only way to write multiple catch clauses is to use predicate functions, which work perfectly, but are more verbose than I would like.


[jvm-packages] Rewrite xgboost jvm packages

To fix https://github.com/dmlc/xgboost/issues/10415

Hi, huge thanks for working on this.
Could you please do a small write-up for the new implementation? We haven't heard about the details of it yet. It would be great if you could write an introduction in a tour style with examples, along with potential breaking changes, etc.

Merging into the jvm branch. We will do the reviews and tests when the branch is ready.