How to use distinct query using this library? I want to fetch distinct values of fields from collection.

How to use distinct query using this library? I want to fetch distinct values of fields from collection.
There is a function for distinct in library. I have used function from controller by below code.
$logs = $this->mongo_db->distinct('logs', 'log_section');
echo "<pre>";print_r($logs);exit;

Here logs is collection name and log_section is field name but i am getting below error
A PHP Error was encountered
Severity: Notice
Message:  Undefined property: MongoDB\Driver\Manager::$logs

Filename: libraries/Mongo_db.php
Line Number: 1337

Backtrace:
			File: /var/www/html/nkninst/master/application/libraries/Mongo_db.php
			Line: 1337
			Function: _error_handler

			File: /var/www/html/nkninst/master/application/controllers/Migration.php
			Line: 48
			Function: distinct

			File: /var/www/html/nkninst/master/index.php
			Line: 315
			Function: require_once

@vidhisampat2807  do you the way to implement this function?


SyntaxError: Unexpected token 'export' using next.js

💬 Questions and Help
When using the simplebar-react in a next.js project I get a SyntaxError:
Unexpected token 'export'

C:\Path\To\Project\node_modules\lodash-es\lodash.js:10
export { default as add } from './add.js';

it looks like it's an issue with lodash-es not transpiling properly, but looking around I can't find anyone else who has this issue. I've tried using next-transpile-modules to no avail, but it looks like it might be a webpack issue not transpiling node modules. Any guidance would be greatly appreciated!

Actually this might be more a question for next-transpile-modules


fix PoW and other functions not working with USE_TORCH=0 despite torch being available

Bug
This fixes problem that after #1904 uses wanting PoW and other torch-using functionality were forced to use USE_TORCH=1 which also forced the legacy torch-based interface.
Description of the Change

users can now use torch-requiring code despite using new interface - this should prevent users being even more reluctant to upgrade just because they use few functions that require torch
the default value in example.env is now USE_TORCH=0, so users don't accidentally run legacy interface - we want old users to move to new one as soon as it is viable AND none of the new users should accidentally run legacy interface
fixed recursion error in lazy torch loader class which happend when requesting nonexistent attribute
refactored the lazy torch loader and added tests for it
added legacy_torch_api_compat for an easier way of maintaining two interfaces, but only used it in limited fashion for now

Alternate Designs
as written above, no
Possible Drawbacks
No real drawbacks that Im aware of.
Verification Process
Unit tests added and manual tests.
Release Notes
None, this fixes regression introduced by #1904 that was yet to be released.

@thewhaleking as author of #1904 you maybe interested in this PR
@gus-opentensor this probably should also land in v7, as it will make users less reluctant to switch to numpy interface


Fix for flakey Download 304 tests to check LastModified time from Upload

Resolves https://github.com/Azure/azure-sdk-for-net/issues/33324
It might be difficult to check if the live tests are running fine for the 304 tests because right now there's live test pipeline failure with AesGcm and ShareClient Exists Error Tests. But also cause these 304 error tests are transient.

/azp run net - storage - tests

API change check
API changes are not detected in this pull request.

/azp run net - storage - tests

/check-enforcer override


Create API to destroy impersonating session

Description
Create an API to stop the current impersonating session.

This feature is no longer required as this will be taken care in the frontend.


Plugin tweaks

Various minor improvements to UI Plugins.

Renamed ot 'Extensions'
Fix LazyImage so that the icon updates when src changes (otherwise icon in preview panel does not update correctly)
Fix for plugin does not show up if CR exists but load failed
Add support for systemDefaultRegistry
Improvements to the info panel
Fixed issue with developer load of plugins with hyphen character in the name

Codecov Report
Base: 36.88% // Head: 36.87% // Decreases project coverage by -0.01% :warning:

Coverage data is based on head (4975ac8) compared to base (89cadd7).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #7095      +/-   ##
==========================================
- Coverage   36.88%   36.87%   -0.02%
==========================================
  Files         977      977
  Lines       17262    17268       +6
  Branches     4482     4484       +2
==========================================
  Hits         6367     6367
- Misses      10895    10901       +6

Flag
Coverage Δ

e2e
47.47% <0.00%> (-0.02%)
:arrow_down:

merged
36.87% <0.00%> (-0.02%)
:arrow_down:

unit
5.29% <0.00%> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

shell/components/LazyImage.vue
0.00% <ø> (ø)

shell/core/plugin.ts
0.00% <0.00%> (ø)

shell/core/plugins.js
11.84% <0.00%> (-0.33%)
:arrow_down:

shell/models/catalog.cattle.io.uiplugin.js
0.00% <0.00%> (ø)

...es/c/_cluster/uiplugins/DeveloperInstallDialog.vue
0.00% <ø> (ø)

shell/pages/c/_cluster/uiplugins/InstallDialog.vue
0.00% <ø> (ø)

...ell/pages/c/_cluster/uiplugins/PluginInfoPanel.vue
0.00% <ø> (ø)

shell/pages/c/_cluster/uiplugins/index.vue
0.00% <ø> (ø)

shell/plugins/plugin.js
55.17% <0.00%> (+3.55%)
:arrow_up:

shell/plugins/dashboard-store/resource-class.js
47.17% <0.00%> (-0.16%)
:arrow_down:

... and 1 more

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

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


feat: gas service and deposit service deployment

PR for AxelarGasService and AxelarDepositService deployment
Note: Import.sol is being used to generate artifacts for CGP repo contracts until the new npm library is published

fix the lint issues?


[e2e] Can't create backport when assignee is invalid

What's the test to develop? Please describe
A clear and concise description of what the test you want to develop.
Prerequisite and dependency of test
Any prerequisite environment and pre-condition required for this test.
Provide test case dependency here if any.
Describe the items of the test development (DoD, definition of done) you'd like

Please use a task list for items on a separate line with a clickable checkbox https://docs.github.com/en/issues/tracking-your-work-with-issues/about-task-lists

[ ] item 1

Additional context
Add any other context or screenshots about the test request here.
related issue: harvester/bot#26

test some webhook


Intercom API upgrade, dbt-expectations removal, and more!

PR Overview
This PR will address the following Issue/Feature: v0.8.0
This PR will result in the following new package version: Issue #35 and Issue #33

This is not necessarily a breaking change. However, the removal of the dependency on dbt-expecations and the tests associated with it are enough that I would prefer we make these major updates so it doesn't cause any hiccups following release.
Please detail what change(s) this PR introduces and any additional information that should be known during the review of this PR:
🚨 Breaking Changes 🚨

In October 2023 the Intercom API upgraded from 2.9 to 2.10 which resulted in the the connector schema has seeing updates. These updates have downstream impacts on the data models within this package. The following changes are a result of the Intercom API and connector upgrades:

The _fivetran_deleted column within the *_history staging models have been removed as they were deprecated in the connector.

Feature Updates

The _fivetran_active, _fivetran_start, and _fivetran_end fields have been added to all *_history staging models to address the removal of the _fivetran_deleted columns and properly track historical records.

Test Updates

Removal of the "author is not null" test within the stg_intercom__conversation_history model.
Updated the source freshness test enablement/disablement to leverage the dbt-core config: enabled: architecture.

Dependency Updates

Removal of the dbt_expectations dependency.

PR Checklist
Basic Validation
Please acknowledge that you have successfully performed the following commands locally:

[X] dbt compile
[X] dbt run –full-refresh
[X] dbt run
[X] dbt test
[X] dbt run –vars (confirmed the source freshness tests worked as expected with the various variables disabled)

Before marking this PR as "ready for review" the following have been applied:

[X] The appropriate issue has been linked and tagged
[X] You are assigned to the corresponding issue and this PR
[x] BuildKite integration tests are passing

Detailed Validation
Please acknowledge that the following validation checks have been performed prior to marking this PR as "ready for review":

[X] You have validated these changes and assure this PR will address the respective Issue/Feature.
[X] You are reasonably confident these changes will not impact any other components of this package or any dependent packages.
[X] You have provided details below around the validation steps performed to gain confidence in these changes.

In order to validate these changes performed the following:

I confirmed that the dbt test command worked without error as the test has been removed and dependency on dbt expectations has been removed as well.

I confirmed the source freshness didn't encounter any strangeness when running with the sources disabled.

Please note that I realized this is not working as expected in the latest dbt-core v1.7.0. I have opened an issue on dbt core that raises this question.

I confirmed the API updates were appropriate by confirming with Ray that the removal of _fivetran_deleted and addition of _fivetran_active, _fivetran_start, and _fivetran_end were appropriate.

Additionally, I was able to validate the outputs of the modified staging models via the new connector with the API upgrades were working as expected and the all tests were still properly passing.
Extensive testing of the staging models was not performed as the changes were fairly straight forward with the removal of the _fivetran_deleted and the addition of the other fields. Additionally, I feel fairly comfortable and confident that these changes are appropriate and no further validation is required.
Additionally, please see the Hex notebook for downstream validations linked in the Height ticket.

Standard Updates
Please acknowledge that your PR contains the following standard updates:

Package versioning has been appropriately indexed in the following locations:

[X] indexed within dbt_project.yml
[X] indexed within integration_tests/dbt_project.yml

[X] CHANGELOG has individual entries for each respective change in this PR

[X] README updates have been applied (if applicable)

[n/a] DECISIONLOG updates have been updated (if applicable)
[n/a] Appropriate yml documentation has been added (if applicable)

dbt Docs
Please acknowledge that after the above were all completed the below were applied to your branch:

[x] docs were regenerated (unless this PR does not include any code or yml updates)

If you had to summarize this PR in an emoji, which would it be?

ℹ

Thanks @fivetran-jamie! Changes have been applied and responses provided. Let me know if there are any other questions.


"Set current tag to all images" button is actually a "Set current tag list to all images"

Nothing more than that: i thought that that was a function to copy the currently selected tag in the current image to every other image in the dataset, but instead it takes all the tags of the current image, even the unselected ones, and replaces all other tag lists with this one, so every image ends in having the same tag list. Also this operation is not undoable so i've lost hours of work :( I think it could be a good idea to rename it correctly
Image:

Fixed in 2.2.0

Fixed in 2.2.0

Thank you very much!


"Minimum module configuration" for IIS + ANCM caused confusing for perf test

https://github.com/aspnet/Docs/blob/master/aspnetcore/host-and-deploy/iis/modules.md
Looks like the "Minimum module configuration" in this doc caused a lot of confusing among users - while it is the right minimum requirement to make ASP.NET core app work, people think it's the fastest configuration and use it in all sorts of perf tests:
aspnet/IISIntegration#747
aspnet/Performance#186
I think it might worth to make some clarifications in this doc.

Thanks @bangbingsyb ... btw -- no need to cross-post so many times. We see it. :wink: :smile:

Thanks for pointing this out @bandbingsyb. I agree we should point it out. I'd like to even steal :smile: some of your language for the note on your other comment.
@shirhatti We have two options here:

Add a couple of lines under our current content; because technically speaking, the module is still not strictly required.
Go ahead and add it to the recommended minimum module configuration, making our advice never to run without it. I would still state that it isn't strictly required.

Sorry for spamming multiple discussion on the same topic - was used to StackOverflow and ServerFault where copy & paste the same comment to similar problems is often needed otherwise the right people might not see it 😄.  Sure, feel free to use the explanation I put in the comment.

Thanks ... no worries on the posting. On second thought, it's just as well that you DID post over on the perf issue because they will need to see that when they setup their perf tests.
Thanks for allowing the use of your language for this. Let's confer with @shirhatti (and perhaps @Tratcher will weigh in) on how best to handle it according to those two approaches that I laid out above :point_up:.

@pan-wang @jkotalik


Hard link

https://github.com/automaticanalysis/automaticanalysis/blob/6c036f0114657e90af5f457c759547bd6bb65b0d/aa_engine/aas_retrieve_inputs_part2.m#L128-L135 uses hard link to copy streams for certain cases (~ismodified), which is problematic for several reasons:

The assumption that it acts like a cp and source is not deleted with the destination is not true. See: https://www.unixtutorial.org/reference/what-is-ln
Certain systems (e.g. in Surrey) does not allow using hard links

Therefore, I propose replacing it with cp or rsync (i.e. removing condition check).
AFAIK, the original idea was to introduce links to avoid data redundancy; but it may be dangerous.

Any comments on this issue? I would really like to remove the hand links because it causes a serious issue in Surrey.

To make what is probably an obvious suggestion, could we make hard/soft links an option in the parameters file?
I seem to recall aa uses hardlinks for a reason, but that decision was way before my time...

An option can certainly work.


Fix issue with programatically tapping button

I needed to add check if tapCircle is nil because when you try to add nil to array it causes crash.
tapCircle is nil when you programatically tap button.
For me this happens in tests (in some tests I would like to simulate user clicking on button).
To invoke tap on button I use this code:
extension UIButton {
    func tap() {
        self.sendActionsForControlEvents(.TouchUpInside)
    }
}

Hi @adamszeptycki !
Thank for this! I'm ashamed that it took me this long to see this. I was on vacation when you submitted this and totally forgot when I got back. Sorry!
At the time, there were merge conflicts so I manually added this change. I credited you in both the CHANGELOG.md and git commit message.
The new version 2.0.27 has this fix.
Thanks again.

:+1:


K8SPXC-576: Fix custom labels

Test name
Status

upgrade-haproxy
passed

big-data
passed

storage
passed

scaling
passed

haproxy
passed

recreate
passed

init-deploy
passed

self-healing
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

upgrade-proxysql
passed

limits
passed

security-context
failed

self-healing-advanced
passed

monitoring-2-0
passed

demand-backup
passed

affinity
passed

smart-update
passed

operator-self-healing
failed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

pitr
passed

users
passed

demand-backup-encrypted-with-tls
passed

upgrade-consistency
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

scheduled-backup
failed

validation-hook
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/803/commits/005769b7b3bec4e99122bfbcc1258d6c260723fb
image: perconalab/percona-xtradb-cluster-operator:PR-803-005769b7

Test name
Status

scaling
passed

upgrade-haproxy
passed

recreate
passed

haproxy
passed

storage
passed

big-data
passed

scaling-proxysql
passed

self-healing
passed

init-deploy
passed

restore-to-encrypted-cluster
passed

upgrade-proxysql
passed

security-context
failed

limits
passed

self-healing-advanced
passed

monitoring-2-0
passed

demand-backup
passed

smart-update
passed

affinity
passed

operator-self-healing
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

pitr
passed

users
passed

demand-backup-encrypted-with-tls
failed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

upgrade-consistency
failed

scheduled-backup
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/803/commits/f8e4a7362c98d82b4dd71cf38a1c00f8ceb8483a
image: perconalab/percona-xtradb-cluster-operator:PR-803-f8e4a736

Test name
Status

haproxy
passed

upgrade-haproxy
passed

recreate
passed

big-data
passed

scaling
passed

storage
passed

init-deploy
passed

scaling-proxysql
passed

self-healing
passed

restore-to-encrypted-cluster
passed

upgrade-proxysql
passed

limits
passed

security-context
failed

self-healing-advanced
passed

monitoring-2-0
passed

demand-backup
passed

smart-update
passed

affinity
passed

one-pod
passed

operator-self-healing
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

pitr
passed

users
passed

upgrade-consistency
passed

demand-backup-encrypted-with-tls
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

scheduled-backup
failed

validation-hook
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/803/commits/558481f0432ba5725b2869137f09f0d9f313b394
image: perconalab/percona-xtradb-cluster-operator:PR-803-558481f0

Test name
Status

scaling
passed

scaling-proxysql
passed

security-context
failed

upgrade-haproxy
passed

big-data
passed

haproxy
passed

init-deploy
passed

limits
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

storage
passed

self-healing
passed

self-healing-advanced
passed

operator-self-healing
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/803/commits/558481f0432ba5725b2869137f09f0d9f313b394
image: perconalab/percona-xtradb-cluster-operator:PR-803-558481f0

Test name
Status

big-data
passed

upgrade-haproxy
passed

storage
passed

scaling
passed

recreate
passed

haproxy
passed

init-deploy
passed

scaling-proxysql
failed

self-healing
passed

restore-to-encrypted-cluster
passed

upgrade-proxysql
passed

limits
passed

self-healing-advanced
passed

security-context
passed

monitoring-2-0
passed

demand-backup
passed

affinity
passed

operator-self-healing
passed

one-pod
passed

smart-update
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

pitr
passed

users
passed

demand-backup-encrypted-with-tls
passed

tls-issue-self
passed

upgrade-consistency
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

scheduled-backup
failed

validation-hook
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/803/commits/bcd8dde4a6de9c52102213840f828f55017c8d2c
image: perconalab/percona-xtradb-cluster-operator:PR-803-bcd8dde4

Test name
Status

upgrade-haproxy
passed

recreate
passed

storage
passed

scaling
passed

big-data
passed

haproxy
passed

init-deploy
passed

scaling-proxysql
passed

self-healing
passed

restore-to-encrypted-cluster
passed

security-context
passed

limits
passed

upgrade-proxysql
passed

self-healing-advanced
passed

monitoring-2-0
passed

demand-backup
passed

affinity
passed

smart-update
passed

one-pod
passed

operator-self-healing
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

pitr
passed

users
passed

demand-backup-encrypted-with-tls
passed

tls-issue-self
passed

upgrade-consistency
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

scheduled-backup
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/803/commits/21d24816a6df26a51734b67e6e31c8f48343ced1
image: perconalab/percona-xtradb-cluster-operator:PR-803-21d24816

Test name
Status

big-data
passed

scaling
passed

scaling-proxysql
passed

security-context
passed

storage
passed

self-healing
passed

self-healing-advanced
passed

operator-self-healing
passed

haproxy
passed

init-deploy
passed

limits
passed

monitoring-2-0
passed

affinity
passed

upgrade-haproxy
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/803/commits/2771e4cd1b52de0104e29dbef3b97ad5c2898932
image: perconalab/percona-xtradb-cluster-operator:PR-803-2771e4cd

Test name
Status

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/803/commits/482861c888945b1fdf3c35f950491720951dc4a2
image: perconalab/percona-xtradb-cluster-operator:PR-803-482861c8

Test name
Status

upgrade-haproxy
passed

haproxy
passed

recreate
passed

big-data
failed

storage
passed

scaling
passed

init-deploy
passed

self-healing
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
failed

security-context
passed

upgrade-proxysql
passed

limits
passed

self-healing-advanced
passed

monitoring-2-0
passed

smart-update
passed

affinity
passed

demand-backup
failed

operator-self-healing
passed

one-pod
failed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

upgrade-consistency
passed

users
passed

pitr
passed

demand-backup-encrypted-with-tls
failed

tls-issue-self
passed

tls-issue-cert-manager
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/803/commits/a3c813e6f96f63baaf75e23c89f22b48cb4afc43
image: perconalab/percona-xtradb-cluster-operator:PR-803-a3c813e6

Test name
Status

haproxy
passed

upgrade-haproxy
passed

storage
passed

recreate
passed

big-data
failed

scaling
passed

init-deploy
passed

self-healing
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
failed

upgrade-proxysql
passed

limits
passed

self-healing-advanced
passed

security-context
passed

monitoring-2-0
passed

smart-update
passed

affinity
passed

demand-backup
failed

operator-self-healing
passed

one-pod
failed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
failed

upgrade-consistency
passed

pitr
passed

demand-backup-encrypted-with-tls
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/803/commits/afc2a8ad2921627112932f3d8fe3ea7cecbaf30d
image: perconalab/percona-xtradb-cluster-operator:PR-803-afc2a8ad

Test name
Status

big-data
failed

haproxy
passed

scaling
passed

storage
passed

recreate
passed

upgrade-haproxy
passed

init-deploy
passed

scaling-proxysql
passed

self-healing
passed

restore-to-encrypted-cluster
failed

upgrade-proxysql
passed

security-context
passed

limits
passed

self-healing-advanced
passed

monitoring-2-0
passed

smart-update
passed

affinity
passed

demand-backup
failed

one-pod
failed

operator-self-healing
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

pitr
passed

tls-issue-cert-manager
passed

upgrade-consistency
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

demand-backup-encrypted-with-tls
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/803/commits/e5ddbab9cac4e57cb090ebba6a37e67f8e14abcc
image: perconalab/percona-xtradb-cluster-operator:PR-803-e5ddbab9

Test name
Status

haproxy
passed

init-deploy
passed

limits
passed

monitoring-2-0
passed

affinity
passed

storage
passed

one-pod
passed

self-healing
passed

self-healing-advanced
passed

scaling
passed

big-data
failed

operator-self-healing
passed

scaling-proxysql
passed

security-context
passed

upgrade-haproxy
passed

upgrade-proxysql
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

smart-update
passed

upgrade-consistency
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/803/commits/e5ddbab9cac4e57cb090ebba6a37e67f8e14abcc
image: perconalab/percona-xtradb-cluster-operator:PR-803-e5ddbab9

Test name
Status

scaling
passed

scaling-proxysql
passed

security-context
passed

haproxy
passed

init-deploy
passed

limits
passed

storage
passed

monitoring-2-0
passed

self-healing
passed

affinity
passed

self-healing-advanced
passed

upgrade-haproxy
passed

one-pod
passed

operator-self-healing
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

big-data
failed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/803/commits/e5ddbab9cac4e57cb090ebba6a37e67f8e14abcc
image: perconalab/percona-xtradb-cluster-operator:PR-803-e5ddbab9


Fail to set Credentials when using Bolt protocol in URI

I'm trying to connect neo4j using bolt protocol, but I'm getting this error: Method threw 'java.net.MalformedURLException' exception.
It seems new URL("bolt://neo4j:neo4j@localhost:7687") will throw that exception because it does not understand bolt as a valid protocol.
detailMessage from the error: unknown protocol: bolt
https://github.com/neo4j/neo4j-ogm/blob/2.0/api/src/main/java/org/neo4j/ogm/config/DriverConfiguration.java#L58
As a result, the credentials are not set properly from the URI.

It seems the fix for that is to use an URI instead of URL.

Hello @jdorleans. Thanks very much for the PR - great work!
We could merge this in right away, however I'd really like to understand the root cause of the error, and after trying a few ways to reproduce it here, wasn't able to. Are you able to provide the following:

A failing test. Preferably in the OGM codebase itself, that will subsequently pass once the patch is applied.
Your environment details - Operating system and version, JVM vendor and version. These details are sometimes very important - we worked on an issue like that last week.

Thanks again for your PR.

@jdorleans could you help us with a failing test? We were unable to reproduce this issue. Thanks!

Not reproducible, please reopen with a test case if it is, thanks.

Sorry for the delay... I've created a new PR #235 to fix that.


[Purpose of v0.11] Separation of config files

Currently we have one configuration file for Voyager.
For v0.11 we will be having multiple files in the following structure:
- config
| - voyager
  | - database.php
  | - widgets.php
  | - storage.php
  | - user.php
  | - assets.php

@marktopper: just my thoughts about this change: are you sure that voyager config can become so big that we need multiple files? Laravel has already enough files to load ...
(BTW: you did an amazing job and I like voyager so much)

Well, I see your point.
I just like to get this done before the configuration file gets to heavy.
I'm however open for a discussion on whether or not to separate things.

You're supposed to config:cache on productions so the number of config files shouldn't be a problem.
Configs are better than querying DB for settings.

The configuration files are not that big yet so I decided to move this to v0.12.


Fix: Icon dropdown shifts layout when suggestions are shown

Fixes #9717
Check List (Check all the applicable boxes)

[X] My code follows the code style of this project.
[X] All new and existing tests passed.
[X] This PR does not contain plagiarized content.
[X] The title of my pull request is a short description of the requested changes.

Screenshots

Looks good! What about the icon search on milestone page?

Hello @eddiejaoude changes for milestone page has been commited.


knife solo prepare fails on AWS CentOS 7 AMI

I think that this should just be ignored, but since its a warning, knife fails to run.
Bootstrapping Chef...
ERROR: SyntaxError: (eval):1: syntax error, unexpected tSYMBEG, expecting end-of-input
...straps::/etc/profile.d/lang.sh:line19:warning:setlocale:LC_C...
...

The original message probably is /etc/profile.d/lang.sh: line 19: warning: setlocale: LC_CTYPE: cannot change locale (UTF-8): No such file or directory. To fix this all you need to do is add the folllowing to /etc/environment:
export LANG=en_US.UTF-8
export LC_ALL=en_US.UTF-8

related:

http://keiwt.hatenablog.com/entry/2014/10/31/231157

I noticed the same problem on RHEL 6.x/7.x (AWS). Your workaround works. Thanks.

I think this is solved @ v0.7.0.pre

My bad. I think that what changed is that the newer CentOS AMI comes with those settings in place.

Well, that works too. Thanks @plentz


🐛BUG : Sign Up page - Name field validation

Description
The "Name" field on the Sign Up page should only accept alphabetical letters (a-z, A-Z). Currently, the field allows users to input symbols and special characters, which may lead to invalid or spam submissions.
Steps to Reproduce

Go to SignUp page
Click on Name field and type numbers and symbols.
See there is no error message.

Expected Behavior
The "Name" field in the Sign Up Page should only accept alphabetical letters (a-z, A-Z).
Actual Behavior
Currently, the field allows users to input symbols and special characters, which may lead to invalid or spam submissions.
Screenshots

Additional Information
No response
What browser are you seeing the problem on?

[ ] Firefox
[X] Chrome
[ ] Safari
[ ] Microsoft Edge

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)

/assign

@akash70629 i am reopening and merging your pr for now but make sure not to work on a issue till i have assigned you that issue


Context switching metrics

As of context switching can have a big impact of application performance
it would be nice to control how often it happens. Context switches are
generally slow operation taking about 100-1000 cycles of CPU and more
over after the switch we can observe CPU cache missing as the memory
cached for previous thread should be invalidated for the current one.
Measuring this value allow us to estimate overheads of using hundreds
of threads in classic blocking application or figure out that something
wrong happens in reactive application.

As context switches are thread related, could you imagine putting these metrics into ProcessThreadMetrics?
I'll leave some small inline comments nevertheless.

@mweirauch Thanks for your review, I applied all of your suggestions. I agree that context switches can be put in ProcessThreadMetrics

@wyhasany sorry for taking it so long. (I polished some tiny bits, squashed locally, push forced to your branch.)
Do you need a timely release? I do have some stuff pending, but it would very likely take me another two weeks. (I am a bit limited on free time at the moment.)

@mweirauch first of all thanks for approving that PR. I don't need a timely release, I'm fine to wait couple of weeks for it 🙂


IE8 Wrapping Issue

I'm using IE8 on Windows XP and am experiencing an issue with my content not wrapping correctly.
It appears to be present in the 'basic' example on this page as well:  http://nicolahibbert.com/demo/liteAccordion/
I can send screenshots if you need them.  Basically the content on the right hand side appears to be extending under the tabs to the right for a bit before wrapping...
An easy way to see this is to simply modify the "Link Somewhere" link with a float right.  It will disappear and be hidden behind the tabs.
Works fine in Opera/Firefox (of course)

Fixed in v2.0.2


MaterialXEditor: fan-in on inputs allowed in UI

Strangely an input can show up with 2 connections on it (fan-in). This does not save out but
is pretty confusing.
It seems there is a check to see if the pin is connected but this always returns false
as it appears another pin has it's connection set ? This is what was observed in Graph::AddLink()
with this check which never seems to return true:
if (inputPin._connected == false)

Snapshot of example test case. UI allows the fan-in but the document when saved is okay.

Digging some more I see two things:

The Graph keeps a list of 'Pin's but when accessing them, they are accessed as copies instead of references when setting connections. This is for iterators (for pin : pinlist) vs for pin& : pinlist) and getPin().
Even when trying to fix this there still seems to be issues, as when checking for existing connections, every pin in the Graph has no connections?

Thanks for this report, @kwokcb, and I believe this issue has been addressed in #1244.


adding service eligibility map to referral page

Adds a referral eligibility map of all services to the referral overview page:

@esmithayer what do you think we should put inside the popups of each map marker? I was thinking any combination of address information, link to the service profile, and a deep # anchor link to the service information further down the page. Currently just service name and address:

Looks nice! What service info is already on this page? Like all the estimated prices etc? Address + link to that sounds good to me (and that has links to the full service profiles).


label and release-label for each packages are ignored

I configured label and release-label for each packages, but it is not reflected in to release PR.
I think it is a bug because the JSON Schema of the config allows label or release-label inside packages.
However, I'm sorry if it is correct behavior.
An example of my release-please-config.json follows:
{
  "separate-pull-requests": true,
  "packages": {
    "packages/a": {
      "label": "autorelease: pending,Package-A",
      "release-label": "autorelease: tagged,Package-A",
    },
    "packages/b": {
      "label": "autorelease: pending,Package-B",
      "release-label": "autorelease: tagged,Package-B",
    }
  }
}

Environment details

OS: macOS
Node.js version: v16.11.0
npm version: 8.0.0
release-please version: 13.21.0

Steps to reproduce

configure release-please-config.json with label or release-label properties in packages
run release-please release-pr to create a release PR

=> The created release PR does not have the labels specified in the config.
Root cause
The ReleaserConfig has labels and releaseLabels properties on the type definition,
https://github.com/googleapis/release-please/blob/3169b4331ddad030a528cfc4003b5fef04ca8588/src/manifest.ts#L95
but mergeReleaserConfig() doesn't return then.
https://github.com/googleapis/release-please/blob/3169b4331ddad030a528cfc4003b5fef04ca8588/src/manifest.ts#L1508

I think this was an oversight in building these configs. The label and release-label fields were intended to be load-bearing state labels so that release-please can identify it's pull requests.
I see 2 options here:

adjust the handling of the per-component labels so that it reads from the component configs (like most other options)
make label and release-label fields on the root manifest (not per-component) and introduce a new extra-labels option

For (1), the downside is that you have to repeat the desired label in both label and release-label and for each component.
For (2), the downside is having an additional config option to maintain. An example config:
{
  "separate-pull-requests": true,
  "packages": {
    "packages/a": {
      "extra-label": "Package-A"
    },
    "packages/b": {
      "extra-label": "Package-B"
    }
  }
}

In either case, we probably need to fix the merge logic when combining pull requests to include all labels of the merged component pull requests. So if in your example you skipped the separate-pull-requests option, then the resulting pull request would have 3 labels: autorelease: pending, Package-A and Package-B.

@chingor13
Sorry for the late response.
I think (2) is better because the main purpose of label release-label and extra-label looks different.

The label and release-label fields are referenced by release-please
The extra-label is referenced by users, other CI/CD pipelines, and so on.

The label and release-label fields were intended to be load-bearing state labels so that release-please can identify it's pull requests.


Use with Hapijs?

Documentation Is:

[ ] Missing
[ ] Needed
[ ] Confusing
[x] Not Sure?

Please Explain in Detail...
While researching how to get an app that was built using create-react-app working with Hapi, I landed on https://github.com/webpack/webpack-dev-server#project-in-maintenance, which directed me to webpack-serve. There are some articles out there on rolling your own hapi-webpack setup, but nothing (that I've found) on making it work as part of a create-react-app setup.
This seems to be a bit of an issue with the Webpack/React ecosystem in general - documentation is more oriented to hobby/side projects, and lacks some structure that would be very useful when trying to actually migrate existing production apps to use these tools.
Your Proposal for Changes

@bschwartz757 appreciate the issue. looks like you're more so hunting for some support or a point in the right direction, versus an issue with the documentation here. I have next to zero knowledge of Hapijs, so I'm afraid I won't be of more help. It might be a good play to try one of the support channels mentioned on the issues entry page. We'll leave this one open for a while to see if anyone else can weigh in.

I've used [this plugin successfully before, so I would assume the webpack-serve integration can be done in a similar way?

DEPRECATED. Please use webpack-dev-server (he is in support and update mode again). Feel free to create a issue if some features are not implemented in webpack-dev-server.
Why deprecated webpack-serve ?

The author stopped developing the package.
Two development servers are misleading for developers.
Hard to maintain two packages with same purpose.
Some dependencies are not available to fixes/implement new features/etc (https://www.npmjs.com/package/webpack-hot-client and https://github.com/shellscape/koa-static) and there's nothing we can do here.
webpack-dev-server is stable.

Thanks for using webpack! We apologize for the inconvenience. In the future, we will avoid such situations.


Exception when trying to name box θ a

Repro steps
I reproed this with Boxer 3.4.19 2024-06-24 on macOS.

Create a data box. Name it θ a (note the space between θ and a)
Hit return to accept the name

Unexpected result: A Common Lisp exception is thrown:
Lisp Error:#\θ (of type CHARACTER) is not of type BASE-CHAR.

Screenshot:

(θ seems to work fine when the box name doesn't contain any spaces.)

Fixed in 88115315d4cb8c37af56f738cd66fcb55a86f15e will be in 3.4.21

Verified in v.3.4.21 and closing.


chore: fetch spec with removed third party

Description
Updated third party URLs.
Fixes #36437
Automation
/ok-to-test<EMAIL_ADDRESS>:mag: Cypress test results

[!WARNING]
Tests have not run on the HEAD 20018d4cb2dda69e8670a695a8b21adac59584eb yet
Thu, 03 Oct 2024 03:32:14 UTC

Communication
Should the DevRel and Marketing teams inform users about this change?

[ ] Yes
[x] No

Summary by CodeRabbit

New Features

Enhanced fetch functionality with improved error handling and updated button interactions.
Introduced delay mechanism for fetch calls to ensure functionality after a timeout.

Bug Fixes

Updated button label and fetch endpoint to correctly retrieve and display user names.

Documentation

Updated test specifications to focus on server-side JavaScript function execution.

/ci-test-count-limit run_count=10

/ci-test-count-limit run_count=10

/ci-test-limit-count run_count=10

/ci-test-limit-count run_count=10

/ci-test-limit-count run_count=10

/ci-test-limit-count run_count=10 runId=11155992956

/ci-test-limit-count run_count=10 runId=11155992956


Parameter jenkins::slave::ui_pass not enclosed in quotes.

For our Jenkins setup, our passwords (jenkins::slave::ui_pass) contain special characters that cause the user to not get authenticated because the password is escaped by the shell.
For example, a test password of: '8jiks#kjke$jk$gjk#' will not authenticate with our Jenkins server unless we patch 'jenkins-slave-defaults.erb' with the following
@@ -55,7 +55,7 @@
 OTHER_ARGS=""

 if [ -n "$JENKINS_USERNAME" ]; then
-  CREDENTIALS_ARG="-username $JENKINS_USERNAME -password $JENKINS_PASSWORD"
+  CREDENTIALS_ARG="-username $JENKINS_USERNAME -password '$JENKINS_PASSWORD'"
 fi

 if [ -n "$CLIENT_NAME" ]; then

Our environment is:

Jenkins v1.654
Ubuntu 14.04.03 x86_64

It is probably worth investigating if https://docs.puppetlabs.com/puppet/latest/reference/function.html#shellquote would work here, as that would also be able to handle '.

@jhoblitt , It looks like shellquotes is already being called.
In slave.pp at line 106, I see the following:
$quoted_ui_user = shellquote($ui_user)
$quoted_ui_pass = shellquote($ui_pass)

I just got back from holiday so I'll be able to do a little more testing today to see if I can't track this down a bit more.

@madelaney are you running from master or 1.6.1?

@jhoblitt , I'm using 1.6.1 but I used master as my reference; sorry in hindsight, I should have referenced the 1.6.x branch.

@madelaney No worries, this module is overdue for a new release official release.  I'm glad we could get this sorted out.

Sorry but I don't think this is resolved. The issue still persists on the 1.6.x branch.
@jhoblitt, would you be open to a pull request that allows me to set my own version of 'jenkins-slave-defaults.erb' either on master or 1.6.x (your preference).


It would be better to add a hyphen between the words 'four year' on the 'Bundling of JavaScript Files' part of release notes

Storage Explorer Version: 1.33.0 (97)
Build Number: 20240217.4
Branch: rel/1.33.0
Platform/OS: Windows 10/Linux Ubuntu 22.04/MacOS Sonoma 14.3(Apple M1 Pro)
Architecture: x64/x64/x64
How Found: From running test cases
Regression From: Not a regression
Steps to Reproduce

Launch Storage Explorer -> Click 'Help -> Release Notes'.
Go to the 'Bundling of JavaScript Files' part.
Go through the descriptions.
Check whether there is a hyphen between the words 'four year'.

Expected Experience
It would be better to add a hyphen between the words 'four year'.
Actual Experience
There is no hyphen between the words 'four year'.

Verified this issue on the rel build 20240220.6. Fixed.


Create count_alpha_words_lines.py

This is in response to issue #266

They are not considering dsa,cp,algorithm repository :(
all the pr will not be considered in hacktoberfest but your contribution will be for lifetime, this will help many students to practice dsa .
Thank you for your contribution :)
you can contribute to other repo


BOOT Mode support

Hi Pelya,
Please, can you add BOOT Mode support in your patches for the kernel?
See this post for the patch: http://www.spinics.net/lists/linux-usb/msg125007.html
I hope you agree. ;-)
Regards.

I thought USB keyboard already works in BIOS, and the patch already has
Boot interface subclass in USB descriptor. Does this patch fix an issue
with some particular device that you have?
Anyway, I'll be able to only patch Nexus 7 2012 kernel, because I don't
have other devices.
On Mon, May 25, 2015 at 1:19 PM, lars18th<EMAIL_ADDRESS>wrote:

Hi Pelya,
Please, can you add BOOT Mode support in your patches for the kernel?
See this post for the patch:
http://www.spinics.net/lists/linux-usb/msg125007.html
I hope you agree. ;-)
Regards.
—
Reply to this email directly or view it on GitHub
https://github.com/pelya/android-keyboard-gadget/issues/27.

Hi Pelya,
Your patches describe the correct subclass (BOOT mode), but they DON'T work with bioses because the reasons described in the thread:

The USB specification describes that ALL HID devices start in REPORT mode (not in BIOS mode), then after the initial handshake is when it can requested to can change to BOOT mode. And yes, the report and boot modes can be equal (as in your code), but when a BIOS requests to change to BOOT mode, and the device respons with an error (like now), then it refuses to work with the device and remove it from the HID input list.

The current problem is in the driver implementation of the Linux(/Android) kernel, mainly with the lack of the HID "Set_Protocol" and "Get_Protocol" functions. Without this patch it's IMPOSSIBLE to change from the report protocol to the boot protocol, and this is a requiment to work with bioses.

Please, belive me... I test your software and patches with several bioses, KVMs, etc. I don't work at all for this specific problem: the misimplementation of these funtions. This patch partially solves the problem, so I suggest to incorporate in yours. If you can only test on Nexus 7 2012, don't care about it. I'll work as it's a small change with all devices.
Please, try it, and comment your results.
Regards.

I've merged that patch to all kernel patches in the Git repo. I've built
Nexus 7 2012 boot image for Android 5.1.1, but for other kernel patches,
I've only checked that they can be applied and respective kernels will
compile. I've tested it and it does not break any functionality, please
reply if it improves anything on your setup.
I still remember about options for camera feed size and for redefining VNC
hotkey, I don't have much free time this month, but I'll implement them
eventually.
On Mon, May 25, 2015 at 7:13 PM, lars18th<EMAIL_ADDRESS>wrote:

Hi Pelya,
Your patches describe the correct subclass (BOOT mode), but they DON'T
work with bioses because the reasons described in the thread:

The USB specification describes that ALL HID devices start in REPORT
mode (not in BIOS mode), then after the initial handshake is when it can
requested to can change to BOOT mode. And yes, the report and boot modes
can be equal (as in your code), but when a BIOS requests to change to BOOT
mode, and the device respons with an error (like now), then it refuses to
work with the device and remove it from the HID input list.

The current problem is in the driver implementation of the
Linux(/Android) kernel, mainly with the lack of the HID "Set_Protocol" and
"Get_Protocol" functions. Without this patch it's IMPOSSIBLE to change from
the report protocol to the boot protocol, and this is a requiment to work
with bioses.

Please, belive me... I test your software and patches with several bioses,
KVMs, etc. I don't work at all for this specific problem: the
misimplementation of these funtions. This patch partially solves the
problem, so I suggest to incorporate in yours. If you can only test on
Nexus 7 2012, don't care about it. I'll work as it's a small change with
all devices.
Please, try it, and comment your results.
Regards.
—
Reply to this email directly or view it on GitHub
https://github.com/pelya/android-keyboard-gadget/issues/27#issuecomment-105258847
.

Hi Pelya,
Thank you for fast reply, and for the new patches! I'll try and post results.
Regards.

Hi Pelya,
A new version of the patch is available: http://permalink.gmane.org/gmane.linux.usb.general/126204
Sorry for not comment until this definitive version. This new version fixes the default mode and improves conformance with specifications. I hope this will be the last modification. And I belive it will be commited to the main kernel branch when sufficient testing is done.
Please, can you upgrade your patch as are only a minimal modification?
Thank you!

Maybe next week
On May 27, 2015 7:40 PM, "lars18th"<EMAIL_ADDRESS>wrote:

Hi Pelya,
A new version of the patch is available:
http://permalink.gmane.org/gmane.linux.usb.general/126204
Sorry for not comment until this definitive version. This new version
fixes the default mode and improves conformance with specifications. I hope
this will be the last modification. And I belive it will be commited to the
main kernel branch when sufficient testing is done.
Please, can you upgrade your patch as are only a minimal modification?
Thank you!
—
Reply to this email directly or view it on GitHub
https://github.com/pelya/android-keyboard-gadget/issues/27#issuecomment-105988117
.


[WIP] Fix CI 4.16

Description
This PR unblocks the 4.16 pipeline by:

refactoring some of our test packages to conform to the new validation from opm (url type format, no capitals, etc.)
parameterizing the e2e job and pinning the opm image to the dependency version in go.mod
updating the skopeo test to handle some changes in the secret annotations (username/password no longer there - have to use the secret as an authfile now
pinning one of the test catalog images to the compatible version (given the operator-registry version in go.mod)
slipping in some flake patches for extra greeness

Notes
I manually created and pushed quay.io/olmtest/test-catalog:v1.39.0 and it is statically pinned in the e2e command:
E2E_OPTS="-communityOperators=quay.io/olmtest/test-catalog:v1.39.0"

I'm currently fixing up the upstream jobs to automagically manage the e2e test fixture images ref. So, I'll need to follow up with that to make it :chefs-kiss:

/retest

/retest

/retest

/jira refresh

/jira refresh

/lgtm
/label qe-approved

/label cherry-pick-approved

/backport-risk-assessed

/label backport-risk-assessed


refactor daemon image tagging

Using this PR to start discussion.
daemon exposes directly it's internal repositories member, which is a *graph.TagStore. Any external caller then needs to be able to import the docker/graph package. Most of these functions return only an error. The docker/image/Image struct will need to be moved into the api at some point in the future. graph.ImagePullConfig needs to move as well.
If this looks okay in principle, I would then do something similar for all of the remaining daemon.Repositories().XYZ calls.
Here is a list of what remains:
λ ag '\.Repositories\(\)'
api/server/image.go
115:		err = s.daemon.Repositories().Pull(ctx, image, tag, imagePullConfig)
132:		err = s.daemon.Repositories().Import(ctx, src, repo, tag, message, r.Body, output, newConfig)
187:	if err := s.daemon.Repositories().Push(ctx, name, imagePushConfig); err != nil {
215:	if err := s.daemon.Repositories().ImageExport(names, output); err != nil {
226:	return s.daemon.Repositories().Load(r.Body, w)
259:	imageInspect, err := s.daemon.Repositories().Lookup(vars["name"])
367:	images, err := s.daemon.Repositories().Images(r.Form.Get("filters"), r.Form.Get("filter"), boolValue(r, "all"))
381:	history, err := s.daemon.Repositories().History(name)

builder/dispatchers.go
212:	image, err := b.Daemon.Repositories().LookupImage(name)

builder/internals.go
519:	if err := b.Daemon.Repositories().Pull(ctx, remote, tag, imagePullConfig); err != nil {
523:	image, err := b.Daemon.Repositories().LookupImage(name)

daemon/image_delete.go
57:	img, err := daemon.Repositories().LookupImage(imageRef)
94:		repoRefs := daemon.Repositories().ByID()[img.ID]
120:	return len(daemon.Repositories().ByID()[imageID]) > 1
149:	_, err := daemon.Repositories().Delete(repository, ref)
160:	imageRefs := daemon.Repositories().ByID()[imgID]
312:	if daemon.Repositories().HasReferences(img) {
341:	return !(daemon.Repositories().HasReferences(img) || daemon.Graph().HasChildren(img))

daemon/list.go
167:			image, err := daemon.Repositories().LookupImage(ancestor)
296:	img, err := daemon.Repositories().LookupImage(container.Config.Image)

Idea sounds good to me. But why you need to be able to import docker/graph?

We want to avoid importing docker/graph, or anything else in base docker. At which point we can rip the API out of where it is and into a pkg/.

I really need to stop forgetting to @calavera @icecrime @duglin

Seems good, but I'd call it just PullImage and TagImage unless there is some conflict there.

Yep, looks right. Agree with @cpuguy83 on the shorter names, if possible.  Needs a rebase.

Thanks for the tips. I'll continue on with shorter names.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "daemon-derepo" git@github.com:MHBauer/docker.git somewhere
$ cd somewhere
$ git rebase -i HEAD~2
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

As I get down to the end, should I continue to remove all external references to daemon.Repositories() and then privatize it? Or do only the work necessary to cut the tie in api/ ?

@MHBauer makes sense for consistency to do that. In other PR of course.

I changing to code-review, because seems like we agree on this and it more like refactoring, than design decision.

@MHBauer golint failure

Looks good ! @MHBauer I pointed out the 2 golint failures :stuck_out_tongue_closed_eyes:

This takes care of everything necessary to isolate api/server. I'm having trouble running the validate section of the makefile, but the tests pass. I'll wait for CI to do a build and then squash.

@MHBauer what problem do you have with the validate section ? :sweat_smile: (I know this is not really related to the PR, but I'm curious)

@vdemeester I'm seeing this:
Step 46 : COPY . /go/src/github.com/docker/docker
 ---> a1310fe013f4
Removing intermediate container 76ea10924de6
Successfully built a1310fe013f4
docker run --rm -it --privileged -e BUILDFLAGS -e DOCKER_CLIENTONLY -e DOCKER_DEBUG -e DOCKER_EXECDRIVER -e DOCKER_EXPERIMENTAL -e DOCKER_GRAPHDRIVER -e DOCKER_STORAGE_OPTS -e DOCKER_USERLANDPROXY -e TESTDIRS -e TESTFLAGS -e TIMEOUT  "docker-dev:daemon-derepo" hack/make.sh validate-dco validate-gofmt validate-pkg validate-lint validate-test validate-toml validate-vet

---> Making bundle: validate-dco (in bundles/1.9.0-dev/validate-dco)
fatal: unable to access 'https://github.com/docker/docker.git/': Could not resolve host: github.com
make: *** [validate] Error 128

I probably just need to restart the VM I am using.

failure looks unrelated.
LGTM
ping @jfrazelle @vdemeester

LGTM


you should include notion / command palette

I'm no big Notion user, but am happy to take a PR. :)

Great list.
i was curious how do you use cmdk bar in apps like obsidian, or vs code. i mean there are essentially two one for feature and other for file search?

I'm not sure I understand, but I guess depending on the application I "just" learn which command does what. 🫣


Remove getAllTables() interface to SQLStatement

For #4520.

Pull Request Test Coverage Report for Build 41

9 of 39 (23.08%)  changed or added relevant lines in 36 files are covered.
16 unchanged lines in 16 files lost coverage.
Overall coverage increased (+0.3%) to 58.416%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

shardingsphere-sql-parser/shardingsphere-sql-parser-engine/src/main/java/org/apache/shardingsphere/sql/parser/sql/statement/dal/dialect/mysql/DescribeStatement.java
0
1
0.0%

shardingsphere-sql-parser/shardingsphere-sql-parser-engine/src/main/java/org/apache/shardingsphere/sql/parser/sql/statement/dal/dialect/mysql/ShowColumnsStatement.java
0
1
0.0%

shardingsphere-sql-parser/shardingsphere-sql-parser-engine/src/main/java/org/apache/shardingsphere/sql/parser/sql/statement/dal/dialect/mysql/ShowCreateTableStatement.java
0
1
0.0%

shardingsphere-sql-parser/shardingsphere-sql-parser-engine/src/main/java/org/apache/shardingsphere/sql/parser/sql/statement/dal/dialect/mysql/ShowIndexStatement.java
0
1
0.0%

shardingsphere-sql-parser/shardingsphere-sql-parser-engine/src/main/java/org/apache/shardingsphere/sql/parser/sql/statement/dcl/DenyUserStatement.java
0
1
0.0%

shardingsphere-sql-parser/shardingsphere-sql-parser-engine/src/main/java/org/apache/shardingsphere/sql/parser/sql/statement/dcl/GrantStatement.java
0
1
0.0%

shardingsphere-sql-parser/shardingsphere-sql-parser-engine/src/main/java/org/apache/shardingsphere/sql/parser/sql/statement/dcl/RevokeStatement.java
0
1
0.0%

shardingsphere-sql-parser/shardingsphere-sql-parser-engine/src/main/java/org/apache/shardingsphere/sql/parser/sql/statement/ddl/AlterIndexStatement.java
0
1
0.0%

shardingsphere-sql-parser/shardingsphere-sql-parser-engine/src/main/java/org/apache/shardingsphere/sql/parser/sql/statement/ddl/CreateIndexStatement.java
0
1
0.0%

shardingsphere-sql-parser/shardingsphere-sql-parser-engine/src/main/java/org/apache/shardingsphere/sql/parser/sql/statement/ddl/DropIndexStatement.java
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

shardingsphere-sql-parser/shardingsphere-sql-parser-relation/src/main/java/org/apache/shardingsphere/sql/parser/relation/statement/dal/DescribeStatementContext.java
1
0%

shardingsphere-sql-parser/shardingsphere-sql-parser-relation/src/main/java/org/apache/shardingsphere/sql/parser/relation/statement/dal/ShowColumnsStatementContext.java
1
0%

shardingsphere-sql-parser/shardingsphere-sql-parser-relation/src/main/java/org/apache/shardingsphere/sql/parser/relation/statement/dal/ShowCreateTableStatementContext.java
1
0%

shardingsphere-sql-parser/shardingsphere-sql-parser-relation/src/main/java/org/apache/shardingsphere/sql/parser/relation/statement/dal/ShowIndexStatementContext.java
1
0%

shardingsphere-sql-parser/shardingsphere-sql-parser-relation/src/main/java/org/apache/shardingsphere/sql/parser/relation/statement/dcl/DenyUserStatementContext.java
1
0%

shardingsphere-sql-parser/shardingsphere-sql-parser-relation/src/main/java/org/apache/shardingsphere/sql/parser/relation/statement/dcl/GrantStatementContext.java
1
0%

shardingsphere-sql-parser/shardingsphere-sql-parser-relation/src/main/java/org/apache/shardingsphere/sql/parser/relation/statement/dcl/RevokeStatementContext.java
1
0%

shardingsphere-sql-parser/shardingsphere-sql-parser-relation/src/main/java/org/apache/shardingsphere/sql/parser/relation/statement/ddl/AlterIndexStatementContext.java
1
0%

shardingsphere-sql-parser/shardingsphere-sql-parser-relation/src/main/java/org/apache/shardingsphere/sql/parser/relation/statement/ddl/AlterTableStatementContext.java
1
0%

shardingsphere-sql-parser/shardingsphere-sql-parser-relation/src/main/java/org/apache/shardingsphere/sql/parser/relation/statement/ddl/CreateIndexStatementContext.java
1
0%

Totals

Change from base Build 968:
0.3%

Covered Lines:
10530

Relevant Lines:
18026

💛  - Coveralls


[HTTP2] Make HTTPVersion public and set to .automatic by default

This PR does two things:

makes it possible to enabling and disabling HTTP/2 by making HTTPVersion public
set HTTPVersion to .automatic by default

HTTP/2 will then be used if we connect to a server with HTTPS and the server supports HTTP/2, otherwise we will continue to use HTTP/1.
A user will still be able to disable HTTP/2 if they want to by setting HTTPVersion to .http1Only on HTTPClient.Configuration e.g.:
HTTPClient(
    eventLoopGroupProvider: .createNew,
    configuration: HTTPClient.Configuration(httpVersion: .http1Only)
)

Fixes #28.


feat: add config.mode

Choices:
- 'cursor' (default): current behaviour, context is determined by
cursor position
- 'topline': context is determined by the top of the window
Resolves #77

Hmm, well I guess topline is a little more intrusive. I think each mode is pretty valid.

Ok, LGTM then, I'll let you merge it if you're done.


[3.18] BPF Additional Felix config parameter for bpfForceTrackPacketsFromIfaces

Additional Felix config parameter to specify interfaces allowing traffic to be tracked by Linux conntrack
NB: should only be used for interfaces that are not used for the Calico fabric
Product Version(s):
Calico 3.27, Calico Enterprise 3.18, and Calico Cloud 3.18

Issue:
CORE-9468

Link to docs preview:

SME review:

[ ] An SME has approved this change.

DOCS review:

[ ] A member of the docs team has approved this change.

Additional information:

@StevenTigera Thanks for the update. Two more things:

What versions does this apply to? Right now, you've got things in place for 3.26, 3.17, and CC/3.17. If these belong in earlier versions, you'll need to modify the corresponding file for each version.
Needs squash + rebase, conflicts resolved, etc.

@StevenTigera Thanks for the update. Two more things:

What versions does this apply to? Right now, you've got things in place for 3.26, 3.17, and CC/3.17. If these belong in earlier versions, you'll need to modify the corresponding file for each version.
Needs squash + rebase, conflicts resolved, etc.

Thanks @ctauchen - squash + rebase as requested.
PS: not sure where I should update the versions therefore I have added under Product Version(s) - hope that's OK

Ok, so by "Calico 3.18, Calico Enterprise 3.18, and Calico Cloud 3.28", do you mean "OS 3.27, CE 3.18, CC/3.18"?

@StevenTigera If this is for 3.18, we have not cut docs branches yet. And that is because we have not done 3.17.0 (early preview) or 3.17.1 (GA). From dates we have, I won't be cutting 3.18 until June.

Ok, so by "Calico 3.18, Calico Enterprise 3.18, and Calico Cloud 3.28", do you mean "OS 3.27, CE 3.18, CC/3.18"?
Yes - apologies @ctauchen - I had the numbers mixed up but have corrected above - my understanding is CC aligns with OS - thanks

@StevenTigera We've finally got somewhere to put this. As it stands now, merging this PR will add these changes for OS 3.27, CE 3.18, and CC 3.18.
Please fetch and rebase, and we can do the final checks to get this merged.

@StevenTigera We've finally got somewhere to put this. As it stands now, merging this PR will add these changes for OS 3.27, CE 3.18, and CC 3.18.
Please fetch and rebase, and we can do the final checks to get this merged.
@ctauchen Done

@StevenTigera Perhaps I got the order wrong here, but I merged #644 first and now this one has conflicts. Can you resolve these?

@StevenTigera Perhaps I got the order wrong here, but I merged #644 first and now this one has conflicts. Can you resolve these?

@ctauchen - NP: resolved conflicts and now two PRs 610 and 644 are in the correct order - OK to merge now - thx


Rewrite rule for composing more than 1 free wires into one

Description
Many people who want to use a syntax-based model such as DisCoCat are confused from the fact that the parser can return in some cases more than one output wires, e.g. for an imperative sentence it would return n.r s, as below:
    Do      your  homework
─────────  ─────  ────────
n.r·s·n.l  n·n.l     n
 │  │  ╰───╯  ╰──────╯

This is actually not a bug but the expected behaviour, since e.g. in cases like the above the subject of the sentence is considered missing. However, this issue makes impossible for the user to apply a unified treatment to all sentences in their dataset, e.g. during the training (see for example Discussion https://github.com/CQCL/lambeq/discussions/88).
A simple solution to this would be to add a rewrite rule that goes through the generated diagrams and adds a box that merges any output wires, more than 1 in number, into a single wire. In this way, all sentence states would live into the same space, allowing easy training and post-processing.
Notes

Please accompany your code with meaningful tests.
Other ways to approach the problem would be to create a dedicated functor class or a simple imperative function (less preferable).

See also

Creating rewrite rules tutorial
Diagram rewriting

Finally!! Thank you so much for this issue. I was actually about to request it hehe.


Link token instead of public key?

I'd love to set this up, but it looks like Plaid has moved to link tokens instead of public keys as of July 2020. How can I amend this to use link tokens instead?

Im also trying to figure this out.

I have updated plaid to the latest version in a fork and i think its all working - if @blairun would like I can make a PR.

Scratch that - although it appeared I got everything working by integrating the latest version of the Plaid sample app, and I'm getting the transactions in that sample app, running testplaid is not returning transactions.
> node scripts/testPlaid.js

Transactions fetch successful!
[]

Im trying to figure out the code and what had been customized in the sample plaid app but the structure is confusing.

I have a version running now that supports link tokens - however i'm stuck debugging a transform issues:
$ node update_*.js
Update failed:  { Error: Unable to parse range: BalanceSpace
    at Gaxios._request (/home/tristan/Documents/Development/automated_finances/node_modules/gaxios/build/src/gaxios.js:112:23)
    at process._tickCallback (internal/process/next_tick.js:68:7)
  response:

@TristanBrotherton did you end up figuring it out? I've been trying to work this problem out as well

@TristanBrotherton did you end up figuring it out? I've been trying to work this problem out as well

I didn’t. I ended up going a different direction and paying for tiller
(which isn’t currently meeting all my needs)
On Mon, Jan 25, 2021 at 22:33, Alexandra Kassis<EMAIL_ADDRESS>wrote:

@TristanBrotherton https://github.com/TristanBrotherton did you end up
figuring it out? I've been trying to work this problem out as well
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/blairun/automated_finances/issues/1#issuecomment-767331938,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAATIDR22GIV5AP3IST2ZO3S3ZO3RANCNFSM4URK4OFA
.

I didn’t. I ended up going a different direction and paying for tiller
(which isn’t currently meeting all my needs)
On Mon, Jan 25, 2021 at 22:33, Alexandra Kassis<EMAIL_ADDRESS>wrote:

@TristanBrotherton https://github.com/TristanBrotherton did you end up
figuring it out? I've been trying to work this problem out as well
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/blairun/automated_finances/issues/1#issuecomment-767331938,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAATIDR22GIV5AP3IST2ZO3S3ZO3RANCNFSM4URK4OFA
.

https://github.com/kevinschaich/mintable/commit/27508c49353b665e808b4c88f6772141f610dccc
On Mon, Jan 25, 2021 at 11:35 PM The British<EMAIL_ADDRESS>wrote:

I didn’t. I ended up going a different direction and paying for tiller
(which isn’t currently meeting all my needs)
On Mon, Jan 25, 2021 at 22:33, Alexandra Kassis<EMAIL_ADDRESS>wrote:

@TristanBrotherton https://github.com/TristanBrotherton did you end up
figuring it out? I've been trying to work this problem out as well
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/blairun/automated_finances/issues/1#issuecomment-767331938
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAATIDR22GIV5AP3IST2ZO3S3ZO3RANCNFSM4URK4OFA
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/blairun/automated_finances/issues/1#issuecomment-767334515,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AITLQKSEVEQ5IOOOZH2COVDS3ZPBLANCNFSM4URK4OFA
.

--
Alexandra Kassis
B.S. Biomedical Informatics
College of Health Solutions at Arizona State University
<EMAIL_ADDRESS><EMAIL_ADDRESS>

https://github.com/kevinschaich/mintable/commit/27508c49353b665e808b4c88f6772141f610dccc
On Mon, Jan 25, 2021 at 11:35 PM The British<EMAIL_ADDRESS>wrote:

I didn’t. I ended up going a different direction and paying for tiller
(which isn’t currently meeting all my needs)
On Mon, Jan 25, 2021 at 22:33, Alexandra Kassis<EMAIL_ADDRESS>wrote:

@TristanBrotherton https://github.com/TristanBrotherton did you end up
figuring it out? I've been trying to work this problem out as well
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/blairun/automated_finances/issues/1#issuecomment-767331938
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAATIDR22GIV5AP3IST2ZO3S3ZO3RANCNFSM4URK4OFA
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/blairun/automated_finances/issues/1#issuecomment-767334515,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AITLQKSEVEQ5IOOOZH2COVDS3ZPBLANCNFSM4URK4OFA
.

--
Alexandra Kassis
B.S. Biomedical Informatics
College of Health Solutions at Arizona State University
<EMAIL_ADDRESS><EMAIL_ADDRESS>


assign command console output

The output on console can be phrased better.

remove square brackets
add space after address
wrapping of words

Also, maybe can change the wedding panel to the list of wedding jobs assigned to that person?

Assigned Emily Davis | Phone: 99690505 | Email<EMAIL_ADDRESS>| Address: Vivo| Role: [caterer] to wedding(s):
Jamie Wedding | Client: Jamie Tan | Date: 2025-01-10 | Venue: Grand Hyatt

Ignoring the square brackets part, I fixed the rest.


Theme font not applied for React 19

Steps to reproduce
1- Create a React 19 app (Vite)
2- Import createTheme from @mui/material/styles
3- Import ThemeProvider from @mui/material/styles
4- Wrap the app wit the ThemeProvider
5- Create a custom theme with a custom font name
6- Set that theme as the <ThemeProvider theme={customTheme}
7- That font does not load
Current behavior
No response
Expected behavior
No response
Context
No response
Your environment

npx @mui/envinfo
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

Search keywords: 19

@Nefcanto Would you mind providing a repro in CodeSandbox/Stackblitz?

@mj12albert, maybe it's related to the Helmet because I see that no font is being loaded in the Networks tab.
I reported it: https://github.com/staylor/react-helmet-async/issues/237

@Nefcanto Do share a repro if you can so we can rule out issues with material UI as well ~

@mj12albert, I understand the need for an MRE. But in some cases, like supporting a major dependency version, honesty is not required because everything is clear. I'm against making the path to reporting bugs expensive. If a problem is the outcome of a special way of using a library, and the developers of the library have no idea how to reproduce it, then a repo is a must. But with due respect, for simple cases like this one, asking for repo makes the open-source world a difficult terrain to live in.


Relay ISet<> to HashSet<> by default

To close the story about basic .NET interfaces I added the ISet<> support as well, given that we already support HashSet<>.
After we merge this PR, it seems that AutoFixture supports all the basic .NET interfaces.
@moodmosaic Please take a look 🍷

4.1 soon?

@Kralizek Yep, after this PR merge

@Kralizek Welcome v4.1.0

@zvirja already using it! <3


Channels now starting from 1 & Alternating row colors

The bottom controll panel is now also scrollable

With a light theme, the table looks very dark. I personally would prefer a white and light-gray stripes instead of gray and dark-gray. Also the font-color should be updated because black on gray is not so easy to read.

Now fixed with :


Flutter crash on real devices on IOS 14.x

The app launches and runs correctly, when using the iPhone 12 pro Max 14.2 simulator. There are no errors in the debug console.
When connecting a real iPhone 12 pro Max 14.2 device to Xcode, the app launches and runs correctly.
The app version, -published in testFlight and installed on users' devices with 14.1.0, 14.2.0, 14.2.1 version OS,- launches correctly, users pass the authorization stage, then they are thrown to the main screen then, and touching the screen causes the app to crash. However, not performing any action and waiting at least 5 seconds after being thrown to the main screen, allows you to go to other screens.
Trying to switch to another screen and performing any actions without delay still cause the app to crash.
flutter run --verbose
verbose.docx
flutter analyze
analyze.docx
flutter doctor -v
[✓] Flutter (Channel stable, 1.22.4, on Mac OS X 10.15.7 19H15 darwin-x64, locale ru-RU)
    • Flutter version 1.22.4 at /Users/nikita/Projects/flutter
    • Framework revision 1aafb3a8b9 (2 weeks ago), 2020-11-13 09:59:28 -0800
    • Engine revision 2c956a31c0
    • Dart version 2.10.4

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/nikita/Library/Android/sdk
    • Platform android-30, build-tools 29.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.2, Build version 12B45b
    • CocoaPods version 1.10.0

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin installed
    • Dart plugin version 201.9245
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] Connected device (1 available)
    • iPhone 12 Pro Max (mobile) • E7C9DE16-00A9-481A-B9B4-43927E7D894C • ios • com.apple.CoreSimulator.SimRuntime.iOS-14-2 (simulator)

Hi @nikit106
Can you please provide logs in a .txt file instead of .docx, it's a proprietary extension, I cannot open in standard text editor
Crash only reproduce when publishing the app? Can you reproduce it when running in flitter run--release -v, release mode?
Can you please provide your  your crash logs, your pubspec.yaml
Thank you

analyze.txt
verbose.txt
flutter run --release -v have an error
[   +5 ms] Release mode is not supported by iPhone 12 Pro Max.
[   +2 ms]
#0      throwToolExit (package:flutter_tools/src/base/common.dart:14:3)
#1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:492:9)

#2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:977:18)
#3      _rootRunUnary (dart:async/zone.dart:1198:47)
#4      _CustomZone.runUnary (dart:async/zone.dart:1100:19)
#5      _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
#6      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
#7      Future._propagateToListeners (dart:async/future_impl.dart:725:32)
#8      Future._completeWithValue (dart:async/future_impl.dart:529:5)
#9      _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:40:15)
#10     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:311:13)
#11     RunCommand.usageValues (package:flutter_tools/src/commands/run.dart)
#12     _rootRunUnary (dart:async/zone.dart:1198:47)
#13     _CustomZone.runUnary (dart:async/zone.dart:1100:19)
#14     _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
#15     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
#16     Future._propagateToListeners (dart:async/future_impl.dart:725:32)
#17     Future._completeWithValue (dart:async/future_impl.dart:529:5)
#18     Future._asyncCompleteWithValue. (dart:async/future_impl.dart:567:7)
#19     _rootRun (dart:async/zone.dart:1190:13)
#20     _CustomZone.run (dart:async/zone.dart:1093:19)
#21     _CustomZone.runGuarded (dart:async/zone.dart:997:7)
#22     _CustomZone.bindCallbackGuarded. (dart:async/zone.dart:1037:23)
#23     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#24     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#25     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#26     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:169:5)
The 3 most common types of crashes in Crashlytics

libsystem_kernel.dylib
__pthread_kill
Heap corruption
The stack trace indicates that heap corruption may have caused your app to crash. Memory corruption can occur pretty easily from freeing a dangling pointer, a thread race, or bad pointer arithmetic. The important thing to keep in mind is that the resulting crash may happen long after the initial corruption. As a result, the stack trace for this crash might not provide any clues to the location of the bug in your code. However, you can still fix memory issues with tools from Apple. For speedy resolution of memory corruption issues, we recommend regularly auditing your app with Xcode’s memory debugging facilities: Visual Memory Debugger, Zombies Instrument, Address Sanitizer, Thread Sanitizer and malloc diagnostics.
Crashed: io.flutter.1.raster
SIGABRT ABORT 0x00000001c4a0584c
Crashed: io.flutter.1.raster
0  libsystem_kernel.dylib         0x1c4a0584c __pthread_kill + 8
1  libsystem_pthread.dylib        0x1dff619e8 pthread_kill + 212
2  libsystem_c.dylib              0x1a25718f4 abort + 100
3  libsystem_malloc.dylib         0x1a82f1030 _malloc_put + 554
4  libsystem_malloc.dylib         0x1a82f12a4 malloc_zone_error + 100
5  libsystem_malloc.dylib         0x1a82dffcc free_list_checksum_botch + 36
6  libsystem_malloc.dylib         0x1a82dd3fc small_free_list_remove_ptr_no_clear + 1228
7  libsystem_malloc.dylib         0x1a82de244 free_small + 592
8  Flutter                        0x105014dcc (Missing)
9  Flutter                        0x10501700c (Missing)
10 Flutter                        0x10501194c (Missing)
11 Flutter                        0x104f255c4 (Missing)
12 Flutter                        0x104f24db4 (Missing)
13 Flutter                        0x104f82a70 (Missing)
14 Flutter                        0x104f26400 (Missing)
15 Flutter                        0x104f1a6f4 (Missing)
16 Flutter                        0x104f1aa14 (Missing)
17 Flutter                        0x104f4641c (Missing)
18 Flutter                        0x104fba42c (Missing)
19 Flutter                        0x1051d481c (Missing)
20 Flutter                        0x104df0cd0 (Missing)
21 Flutter                        0x1050685f8 (Missing)
22 Flutter                        0x105069074 (Missing)
23 Flutter                        0x105068890 (Missing)
24 Flutter                        0x10506ed90 (Missing)
25 Flutter                        0x104d9f43c (Missing)
26 Flutter                        0x104da13b0 (Missing)
27 CoreFoundation                 0x1998463d0 CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION + 28
28 CoreFoundation                 0x199845fd4 __CFRunLoopDoTimer + 1004
29 CoreFoundation                 0x1998454b4 __CFRunLoopDoTimers + 324
30 CoreFoundation                 0x19983f840 __CFRunLoopRun + 1912
31 CoreFoundation                 0x19983eb90 CFRunLoopRunSpecific + 572
32 Flutter                        0x104da128c (Missing)
33 Flutter                        0x104da0c14 (Missing)
34 libsystem_pthread.dylib        0x1dff60b3c _pthread_start + 288
35 libsystem_pthread.dylib        0x1dff65880 thread_start + 8

Metal
invocation function for block in MTLCompilerFSCache::getElement(MTLUINT256_t, void**, unsigned long*)
Crashed: io.flutter.1.raster
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000000002030
Crashed: io.flutter.1.raster
0  libsystem_malloc.dylib         0x19fd0ab20 small_free_list_remove_ptr_no_clear + 312
1  libsystem_malloc.dylib         0x19fd0d26c small_malloc_from_free_list + 492
2  libsystem_malloc.dylib         0x19fd0b5e0 small_malloc_should_clear + 232
3  libsystem_malloc.dylib         0x19fd08318 szone_malloc_should_clear + 136
4  libsystem_malloc.dylib         0x19fd167f8 _malloc_zone_malloc + 152
5  Metal                          0x1a645779c invocation function for block in MTLCompilerFSCache::getElement(MTLUINT256_t, void**, unsigned long*) + 356
6  libdispatch.dylib              0x190898ac8 _dispatch_client_callout + 20
7  libdispatch.dylib              0x1908a6c8c _dispatch_lane_barrier_sync_invoke_and_complete + 60
8  Metal                          0x1a6457594 MTLCompilerFSCache::getElement(MTLUINT256_t, void**, unsigned long*) + 308
9  Metal                          0x1a64b9e34 MultiLevelPipelineCache::getElement(MTLUINT256_t const&) const + 168
10 Metal                          0x1a64b9a2c MTLLibraryBuilder::initLibraryContainerWithRequestData(MTLLibraryContainer*, void*, unsigned long, MTLBuildRequestType, MTLCompileOptions const*, MTLCompilerFunctionRequest const*, unsigned int, bool, void () block_pointer) + 1000
11 Metal                          0x1a64ba704 MTLLibraryBuilder::newLibraryWithRequestData(void*, unsigned long, MTLBuildRequestType, MTLCompileOptions const*, MTLCompilerFunctionRequest const*, unsigned int, bool, void (id, NSError*) block_pointer) + 248
12 Metal                          0x1a64bbe78 MTLLibraryBuilder::newLibraryWithSource(id, NSString*, MTLCompileOptions*, bool, void (id, NSError*) block_pointer) + 4704
13 Metal                          0x1a6488ab8 -[_MTLDevice newLibraryWithSource:options:error:] + 228
14 AGXMetalA13                    0x1da08303c (Missing)
15 Flutter                        0x104e9e454 (Missing)
16 Flutter                        0x104e99ef4 (Missing)
17 Flutter                        0x104e98d68 (Missing)
18 Flutter                        0x104e9b00c (Missing)
19 Flutter                        0x104e9594c (Missing)
20 Flutter                        0x104da95c4 (Missing)
21 Flutter                        0x104da8db4 (Missing)
22 Flutter                        0x104e06a70 (Missing)
23 Flutter                        0x104daa400 (Missing)
24 Flutter                        0x104d9e6f4 (Missing)
25 Flutter                        0x104d9ea14 (Missing)
26 Flutter                        0x104dca41c (Missing)
27 Flutter                        0x104e3e42c (Missing)
28 Flutter                        0x10505881c (Missing)
29 Flutter                        0x104c74cd0 (Missing)
30 Flutter                        0x104eec5f8 (Missing)
31 Flutter                        0x104eed074 (Missing)
32 Flutter                        0x104eec890 (Missing)
33 Flutter                        0x104ef2d90 (Missing)
34 Flutter                        0x104c2343c (Missing)
35 Flutter                        0x104c253b0 (Missing)
36 CoreFoundation                 0x190c18050 CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION + 32
37 CoreFoundation                 0x190c17c50 __CFRunLoopDoTimer + 1064
38 CoreFoundation                 0x190c170c4 __CFRunLoopDoTimers + 328
39 CoreFoundation                 0x190c11178 __CFRunLoopRun + 1936
40 CoreFoundation                 0x190c104bc CFRunLoopRunSpecific + 600
41 Flutter                        0x104c2528c (Missing)
42 Flutter                        0x104c24c14 (Missing)
43 libsystem_pthread.dylib        0x1d8b89ca8 _pthread_start + 320
44 libsystem_pthread.dylib        0x1d8b92788 thread_start + 8

Metal
invocation function for block in MTLCompilerFSCache::getElement(MTLUINT256_t, void**, unsigned long*)
Crashed: io.flutter.1.raster
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000000002030
Crashed: io.flutter.1.raster
0  libsystem_malloc.dylib         0x1a82dd064 small_free_list_remove_ptr_no_clear + 308
1  libsystem_malloc.dylib         0x1a82df410 small_malloc_from_free_list + 488
2  libsystem_malloc.dylib         0x1a82dda3c small_malloc_should_clear + 192
3  libsystem_malloc.dylib         0x1a82dac80 szone_malloc_should_clear + 132
4  libsystem_malloc.dylib         0x1a82e69ac _malloc_zone_malloc + 144
5  Metal                          0x1ae8c420c invocation function for block in MTLCompilerFSCache::getElement(MTLUINT256_t, void**, unsigned long*) + 352
6  libdispatch.dylib              0x1994fe280 _dispatch_client_callout + 16
7  libdispatch.dylib              0x1994e10ec _dispatch_lane_barrier_sync_invoke_and_complete + 56
8  Metal                          0x1ae8c4008 MTLCompilerFSCache::getElement(MTLUINT256_t, void**, unsigned long*) + 252
9  Metal                          0x1ae922c54 MultiLevelPipelineCache::getElement(MTLUINT256_t const&) const + 160
10 Metal                          0x1ae922894 MTLLibraryBuilder::initLibraryContainerWithRequestData(MTLLibraryContainer*, void*, unsigned long, MTLBuildRequestType, MTLCompileOptions const*, MTLCompilerFunctionRequest const*, unsigned int, bool, void () block_pointer) + 908
11 Metal                          0x1ae9234b4 MTLLibraryBuilder::newLibraryWithRequestData(void*, unsigned long, MTLBuildRequestType, MTLCompileOptions const*, MTLCompilerFunctionRequest const*, unsigned int, bool, void (id, NSError*) block_pointer) + 224
12 Metal                          0x1ae924ba4 MTLLibraryBuilder::newLibraryWithSource(id, NSString*, MTLCompileOptions*, bool, void (id, NSError*) block_pointer) + 4660
13 Metal                          0x1ae8f3760 -[_MTLDevice newLibraryWithSource:options:error:] + 152
14 AGXMetalA11                    0x1e0f97e50 (Missing)
15 Flutter                        0x100dbe454 (Missing)
16 Flutter                        0x100db9ef4 (Missing)
17 Flutter                        0x100db8d68 (Missing)
18 Flutter                        0x100dbb00c (Missing)
19 Flutter                        0x100db594c (Missing)
20 Flutter                        0x100cc95c4 (Missing)
21 Flutter                        0x100cc8db4 (Missing)
22 Flutter                        0x100d26a70 (Missing)
23 Flutter                        0x100cca400 (Missing)
24 Flutter                        0x100cbe6f4 (Missing)
25 Flutter                        0x100cbea14 (Missing)
26 Flutter                        0x100cea41c (Missing)
27 Flutter                        0x100d5e42c (Missing)
28 Flutter                        0x100f7881c (Missing)
29 Flutter                        0x100b94cd0 (Missing)
30 Flutter                        0x100e0c5f8 (Missing)
31 Flutter                        0x100e0d074 (Missing)
32 Flutter                        0x100e0c890 (Missing)
33 Flutter                        0x100e12d90 (Missing)
34 Flutter                        0x100b4343c (Missing)
35 Flutter                        0x100b453b0 (Missing)
36 CoreFoundation                 0x1998463d0 CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION + 28
37 CoreFoundation                 0x199845fd4 __CFRunLoopDoTimer + 1004
38 CoreFoundation                 0x1998454b4 __CFRunLoopDoTimers + 324
39 CoreFoundation                 0x19983f840 __CFRunLoopRun + 1912
40 CoreFoundation                 0x19983eb90 CFRunLoopRunSpecific + 572
41 Flutter                        0x100b4528c (Missing)
42 Flutter                        0x100b44c14 (Missing)
43 libsystem_pthread.dylib        0x1dff60b3c _pthread_start + 288
44 libsystem_pthread.dylib        0x1dff65880 thread_start + 8
pubspec.yaml
environment:
sdk: ">=2.7.0 <3.0.0"
dependencies:
material_design_icons_flutter: ^4.0.5045
flutter:
sdk: flutter
flutter_localizations:
sdk: flutter
cupertino_icons: ^0.1.3
dev_dependencies:
flutter_test:
sdk: flutter
http: ^0.12.0+4
jwt_decoder: ^1.0.3
carousel_slider: ^2.3.1
url_launcher: ^5.7.10
provider: ^4.3.2+2
dio: ^3.0.10
rxdart: ^0.24.1
bloc: ^4.0.0
flutter_secure_storage: ^3.3.5
flutter_bloc: ^4.0.0
equatable: ^1.2.5
flutter_widget_from_html: ^0.5.1+5
flutter_widget_from_html_core: ^0.5.1+4
flutter_launcher_icons: ^0.7.5
intl: ^0.16.1
path_provider: ^1.6.24
open_file: ^3.0.3
flutter_mailer: ^1.0.1
date_range_picker: ^1.0.6
charts_flutter: ^0.9.0
firebase_messaging: ^6.0.16
device_info: ^1.0.0
month_picker_dialog: ^0.3.3
dotted_border: ^1.0.7
file_picker: ^2.1.0
mask_text_input_formatter: ^1.1.0
firebase_crashlytics : ^0.2.3
firebase_core : ^0.5.0
shared_preferences: ^0.5.12+4

Hi @nikit106
Can you please provide logs  flutter run --release --verbose  from the real device as stated you have access to or complete logs with flutter run --release without release with smulator

When connecting a real iPhone 12 pro Max 14.2 device to Xcode

We solved this problem by changing in Xcode-> Runner -> build settings-> packaging-> Product Name from Cyrillic to Latin name

Hi @nikit106
Yay! Glad you resolved the issue
Given your last message I feel safe to close this issue, if you disagree please write in the comments and I will reopen it.
Thank you


Problem with installing pycairo dependencies from requirements.txt [2]

Wanted to track my work activity with speaking-eye and found some issues while installing it.
Problem:
After removed pkg-resources (https://github.com/alena-bartosh/speaking-eye/issues/1) from requirements.txt I got next error while building pycairo dependencies
$ git clone https://github.com/alena-bartosh/speaking-eye.git && \
    cd speaking-eye && \
    python3 -m venv .env && \
    source .env/bin/activate && \
    pip install --upgrade pip && \
    pip install -r requirements.txt

...
ERROR: Command errored out with exit status 1: /home/tas/Workspace/speaking-eye/.env/bin/python3 /home/tas/Workspace/speaking-eye/.env/lib/python3.7/site-packages/pip install --ignore-installed --no-user --prefix /tmp/pip-build-env-qk6wrbri/overlay --no-warn-script-location --no-binary :none: --only-binary :none: -i https://pypi.org/simple -- setuptools wheel pycairo Check the logs for full command output.

Solution:
In order to resolve this issue I installed missing system dependency with sudo apt-get install libcairo2-dev
Environment:
$ cat /etc/lsb-release
DISTRIB_ID=LinuxMint
DISTRIB_RELEASE=19.1
DISTRIB_CODENAME=tessa
DISTRIB_DESCRIPTION="Linux Mint 19.1 Tessa"

$ python3
>>> import sys; print(sys.version)
3.7.3 (default, Mar 27 2019, 22:11:17)
[GCC 7.3.0]

Fixed. Thank you for your interest in speaking-eye 🙃


Remove all uses of the client supplied me

@aaronpk, @sknebel, and I spend an evening talking, and now there is a PR. Foreboding? 😉
This removes any dependence on a me parameter being passed from the client. Basically, Selfauth will always identify as the user you have configured it to be. This means Selfauth will be more compatible with existing OAuth tooling, see indieweb/indieauth#19 for the background discussion.
This version of the file is currently in use by me, and I haven’t run into problems logging in anywhere. Looks like everything seems to work. One question: should the login page clearly tell the user what identity they are providing to the client?

Also discussed this with @aaronpk and it sounds like a good idea to show the user the URL they will be sending to the party they authenticate to. Especially since it may be different from what they entered in the form (as this PR makes us ignore any me parameter).
I am just not sure where to put it or how to phrase it. The simplest change would be:
--- a/index.php
+++ b/index.php
@@ -376,6 +376,7 @@ padding:20px;

         <form method="POST" action="">

Authenticate

+
Identifying as
<?php echo htmlspecialchars(USER_URL); ?>

You are attempting to login with client
<?php echo htmlspecialchars($client_id); ?>

             <?php if (strlen($scope) > 0) : ?>

It is requesting the following scopes, uncheck any you do not wish to grant:

I’d prefer to get something like this added before merging.

Another option could be something like this?

My one concern with merging it into the “login” form is that it may not be clear to the user that this is the URL that will be shared. But maybe that is unfounded?

I like @sknebel's suggestion. Given that the user will have just typed their URL into the previous site before getting here, they have at that point already shared their URL even if they don't finish logging in.

Given that the user will have just typed their URL into the previous site before getting here, they have at that point already shared their URL […]

I think I am going from the perspective where they may have entered a different URL on the previous site. Something we were previously blocking because we checked the me parameter.

But wouldn't that only occur if:

there is a normal setup with site A pointing to Selfauth, and Selfauth being setup for A.
there is a different site B, which also points to A's Selfauth.
the user of site B enters B into a login-form and thus visits A's Selfauth, which asks for A + password.

I think this would just not really happen often, as it's clearly a mistake by Person B. Person B would now at least see that Selfauth is still expecting A. Person B will never think their setup is correct, for it will never work.

My scenario only has one user, cross-user contamination wouldn’t happen because Alice and Bob do not know eachother’s passwords.

Alice has a website on alice.example.com. This points at Selfauth on alice.example.com/auth.
She creates a new website to have an anonymous identity, call it avocado.example.org. To get a running start the HTML is based on her other website and accidentally points at alice.example.com/auth for authorization.
She now goes to login to a service (e.g. the indieweb.org wiki) with her new anonymous identity avocado.example.org and gets send to the auth endpoint alice.example.com/auth.
Her password manager (everyone uses one, right?!) already auto-filled the password and all she needs to do is press Submit.

Before this PR, step 3 would result in an error message because avocado.example.org is not the configured identity. After this PR, pressing Submit will tell the service that the user is alice.example.com and not avocado.example.org, breaking the anonymity of the secondary identity.
So somehow I’d like to make it clear for the end-user they are telling the third-party they are alice.example.com, even after they might have entered a different URL.

BTW: Not saying @sknebel’s suggested UI doesn’t make this clear. Just saying I find it hard to figure out what is or isn’t clear enough 😄

That latest commit adds the user’s URL to the login box, right above the password, as proposed by @sknebel. If people are OK with how that looks lets move on to merging this and being ready for possible future IndieAuth spec changes.


Disable y normalization

Added pulse3D support for disabling y-axis normalization.
Added new  disable_y_normalization to docs

You'll need to bump the version number in setup.py so you can publish to PyPI and bring this new version into the pulse3d-worker. You should also update the changelog since you're bumping the version


Mouse selection/picking broken in Safari

see https://github.com/arose/nglview/issues/698

workaround fix, see fe247fa41234b8bd2957d03963a6734aad8e372f


in ./graph_embedding/watch_your_step Reason for scaling up positive loss by the number of nodes, significance of attention and why no validation split?

[Line no 226, graph_attention_learning.py, Watch Your Step] return tf.transpose(d_sum) * GetNumNodes() * 80, feed_dict
Why is an arbitrary scaling by the number of nodes done? I am not sure if it is reported in the Watch Your Step paper.
When I remove the scaling, there is some decrease in the results for most of the datasets
Results and Ablation Study:
PPI(without scaling,learn attention) - 90.84
PPI(with scaling,learn attention) - 91.8
PPI(uniform attention,scaling) - 91.7
ca-HepTh(without scaling,learn attention) - 93.14
ca-HepTh(with scaling,learn attention) - 93.8
ca-HepTh(uniform attention,scaling) - 93.9
Wiki-Vote(without scaling,learn attention) - 94.3
Wiki-Vote(with scaling,learn attention) - 93.7
Wiki-Vote(uniform attention,scaling) - 94.0
Configs:
Embedding dimension:128
Share Embeddings: False
Transition_powers: 5
Loss: nlgl
context_regularizer: 0.1
learnable attention - softmax over 5 hops
uniform attention - Equal attention of earch of 5 hops(0.2 for each hop)
A couple of more questions:

Why is a validation set(validation positive edges, negative edges) not chosen for stopping? I know that Learning Edge Representations via Low-Rank Asymmetric Projections, other baselines and many of the graph embedding literature doesn't use it for link prediction, but I feel that stopping based on validation from ROC-AUC scores is more appropriate than stopping by best train ROC-AUC.

2.a) I see that attention makes only little contribution to an increase in the performance. Uniform attention works well. For example, in PPI, the paper reports that the attention learned favors the first hop. But not learning any attention(or in other words, uniform attention) also performs equally well. This is true even for Soc-Facebook, Wiki-Vote, ca-HepTh, ca-AstroPh.
2.b)
Why is the stopping criteria in line 441
"if i - 100 > eval_metrics['i at best train']:
LogMsg('Reached peak a while ago. Terminating...')
break"
based on training error? Shouldn't stopping criteria be always based on validation error?
2.c) in line 340 "eval_metrics['test auc at best train'] = float(test_auc)"
Why log and report test AUC at best train? We always report metrics and save model that gives the best performance on the validation set. If we modify the code to report the AUC / precision scores at least validation error then there is little to no difference between having weights and trainable attention.

@karthik63 These are great questions! Did you ever figure out any answers?