fix: use dl.k8s.io, not kubernetes-release bucket

What type of PR is this?
/kind cleanup
/kind deprecation
What this PR does / why we need it:
There are still references to https://storage.googleapis.com/kubernetes-release instead of https://dl.k8s.io/
dl.k8s.io is the correct advertised download host and will eventually move to be fastly shielding a fully community-owned bucket
ref: https://github.com/kubernetes/k8s.io/issues/2396
NONE

/lgtm

looks like https://github.com/kubernetes/cloud-provider-openstack/pull/2240 already opened for this
and identical to this ,so maybe we need close this as duplicate


feat: Konnect API examples for plugins

Description
For any plugin that is supported in Konnect, it’s now possible to configure it using the Konnect runtime groups API, via core-entities. This PR adds support for generated Konnect API examples in the plugin docs, which makes the Konnect API more visible and positions it as a parallel option to the Kong Admin API.
A simple service example for the Basic auth plugin:

A global example for the Rate Limiting Advanced plugin:

Along with that, there were several fixes/improvements that I had to make:

Placeholders in curl examples: after team discussion, settled on { } as the placeholder characters for URLs. This format is heavily used in our API specs, and is the OpenAPI standard: https://swagger.io/docs/specification/describing-parameters/. Going forward, we should be using { } to enclose variables in specs and API examples.

Placeholders in other situations still need revisiting. Out of scope here.

The global example now explains what "global" means in the context of Konnect, Kong Enterprise, and Kong OSS. This is a long-running painpoint, and it seems timely to add this as we add Konnect examples.

Removed the duplicate konnect_examples and manager_examples metadata keys from plugin docs. We don't have Kong Manager examples, and we don't need a separate konnect_examples key. konnect: false/true already performs the same function.

https://konghq.atlassian.net/browse/DOCU-2949
Testing instructions
Check any plugin doc. For example:

Rate Limiting Advanced plugin - has all example types, good way to see everything in one place
OAuth2 plugin - isn't supported in Konnect so the Konnect API tab doesn't show up
Update to style guide

Checklist

[x] Review label added
[x] PR pointed to correct branch (main for immediate publishing, or a release branch: e.g. release/gateway-3.2, release/deck-1.17)

Finally got around to testing this and realized that the Konnect API doesn't accept the same format as the Kong Admin API. It has to be json data, eg:
  curl -i -X POST \
  https://us.api.konghq.com/v2/runtime-groups/{runtime-group-id}/core-entities/services/{service-id}/plugins \
  --header 'accept: application/json' \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer kpat_abcd' \
  --data '{"name":"basic-auth","config":{"anonymous":null,"hide_credentials":false}}'

So now I'm trying to figure out how to generate the config part, and struggling.

@lena-larionova how can I help?

@lena-larionova I pushed something, would that work?

Tested out the changes you made, I think we're good now. The examples work!


Flatten nested kdeWrappers

Motivation for this change
Takes a stab at https://github.com/NixOS/nixpkgs/issues/21345. With this nested kdeWrappered packages are flattened into one symlink tree, saving disk space.
As @FRidh suggested we now use this in KDE5 service with a new option extraPackages. I've moved all the wrapped packages from the big list (there are not too many of them; is this right?).
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Tested with this configuration:
{
  services.xserver.enable = true;
  services.xserver.desktopManager.kde5.enable = true;
  services.xserver.desktopManager.kde5.enableQt4Support = true;
  hardware.bluetooth.enable = true;
  hardware.pulseaudio.enable = true;
  powerManagement.enable = true;
  networking.networkmanager.enable = true;
  services.colord.enable = true;
  services.samba.enable = true;

  users.extraUsers.root.password = "";
}

@ttuegel Updated.

Looks good to me! Thanks for putting this together.


Fix incorrect Y position for any tooltip displayed with a .left ArrowPosition

Thanks for your contribution. Your commit has been integrated here: fdb2b49d2ba6319e271ea41116b4ae21b40c69fb

Thanks for your contribution. Your commit has been integrated here: fdb2b49d2ba6319e271ea41116b4ae21b40c69fb


[FEATURE] Support Maintenance Mode 🚧

It would be cool if PWA Kit allowed displaying a "Be right back!" maintenance screen when the associated B2C Commerce instance is in maintenance mode.
B2C Commerce instances can enter maintenance mode two ways:

In BM, you can put your Site's Status into Maintenance.
During the B2C Commerce release process, Salesforce might put your instance into Maintenance.

When B2C Commerce maintenance mode is enabled, requests to SCAPI return an HTTP 503:
https://developer.salesforce.com/docs/commerce/commerce-api/guide/response-handling.html
Today, when a request to SCAPI returns an HTTP 503, PWA Kit renders a generic error.
There are a few ways we could implement this, but one way would be to propogate HTTP 503 errors from SCAPI calls upward to our <ErrorBoundary>.
We might then add special handling for the case where the error is a 503 to <Error>, displaying a user configurable maintenance page.
It looks like lots of the plumbing is already there – we likely need to need to a) make sure errors are passed enough b) make sure we have the details of the error to act on.
For the implementation, we'd want to test maintenance mode being enabled in a few different places:

Server side rendering
Landing on a cached page as a new visitor (eg. call to oauth2/authorize fails)
Landing on a cache page as a returning visitor with valid token (eg. catagory load fails or requests made to navigate to PLP fail)
Basket modifications from the cart page
Basket modifications from the checkout

This feature should also help you understand when the ODS you're connecting to is stopped or or longer exists.
SCAPI requests to stopped sandboxes return an HTTP 521 Stopped sandboxes return an "HTTP 521 Web server is down" status code.
This should result in a clear error message.
Right now we get this:

The issue only becomes clear when you open DevTools:


Titlebar gets transparent when Zed lost focus

https://github.com/zed-industries/zed/issues/15112
the titlebar looks ugly if the editor isnt in focus.. please help

the titlebar looks ugly if the editor isnt in focus.. please help

Could you share a screenshot of what it looks like for you? I do set the title_bar.inactive_background highlight to be the same as the normal title bar so it might just be a bug the zed team has to fix.

Here you go! thanks a lot! I installed from the editor extension list


[Numpy]  add numpy op bitwise_xor, hsplit, moveaxis, rot90

add numpy op bitwise_xor
fix some format problems
add numpy op moveaxis
fix code style
add numpy op rot90
fix pylint error
updata rot90
address comments
add  numpy op hsplit
refactor split compute function
Description
(Brief description on what this PR is about)
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

LGTM in general, for implementing the forward op based on the forward/backward of another op, you may refer to the PR in https://github.com/apache/incubator-mxnet/pull/12821

@sxjscience  i refactor this code


RF Coreg-GUI:  remove MNE-C dependency for fsaverage files

Addresses #3903

Thanks @Eric89GXL , I addressed your two comments

Current coverage is 85.61% (diff: 11.11%)

Merging #3904 into master will increase coverage by <.01%

@@             master      #3904   diff @@
==========================================
  Files           347        349     +2
  Lines         61930      61948    +18
  Methods           0          0
  Messages          0          0
  Branches       9496       9492     -4
==========================================
+ Hits          53015      53036    +21
+ Misses         6255       6247     -8
- Partials       2660       2665     +5

Powered by Codecov. Last update eb418d2...e7d6175

Is there a way I can access the documentation build from the CIs? I added a link to the description of the MNE fsaverage files and wanted to check that it links correctly.

Yes, look at CircleCI link, artifacts tab. You might need to sign into CircleCI using your GitHub account
https://3535-1301584-gh.circle-artifacts.com/0/home/ubuntu/mne-python/doc/_build/html/python_reference.html

Thanks! Yes I had to sign in to see it.
I think I addressed everything, here is the updated documentation.

LGTM, +1 for merge

Thanks @christianbrodbeck


faad2: 2.10.1 -> 2.11.0

Main change is switch to cmake build system.
Changes: https://github.com/knik0/faad2/releases/tag/2.11.0
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Needs to backport a few upstream fixed to get i686Linux.faad to compile:
faad2> /nix/store/pldw5bd9yc7da0mjh01zd9azbfshpd2c-glibc-2.38-23-dev/include/bits/mathcalls.h:317:1: error: conflicting types for 'lrintf'; have 'long int(float)'
faad2>   317 | __MATHDECL (long int,lrint,, (_Mdouble_ __x));
faad2>       | ^~~~~~~~~~

Both faad2 and pkgsi686Linux.faad2 build successfully now. Ready for review.


[Bigquery] Empty arrays are not supported as query parameter values

It is perfectly valid to run queries with an empty array as a parameter. Our application has one such query that takes two ARRAY<INT64> parameters; either of which (but never both) could potentially be empty. Said query is trivial and is quoted in its entirety below:
SELECT
  (SELECT AS STRUCT FT.*) AS form_transaction,
  IF(FS.id IS NULL, NULL, (SELECT AS STRUCT FS.*)) AS form_session
FROM
  dev1_1208.FormTransaction AS FT
LEFT JOIN
  dev1_1208.FormSession AS FS
ON
  FS.form_transaction_id = FT.id
WHERE
  FT.id IN UNNEST(@transactionIds) OR
  FS.id IN UNNEST(@sessionIds)

Running this query with explicit array literals (i.e. building the query string with these values pre-substituted, rather than via proper query parameters) works fine, even if one of the arrays is empty (e.g. FS.id IN UNNEST([])). Executing this same request against the Bigquery REST API manually via the API Explorer correctly handles empty array parameters also; so this issue is certainly within google-cloud-bigquery itself - it's not a backend API limitation.
Attempting to execute this query via google-cloud-bigquery fails when handling the response from the Bigquery API with a NullPointerException in QueryParameterValue.fromPb upon executing the query, at the following line (427):
valueBuilder.setValue(valuePb.getValue());

java.lang.NullPointerException
	at com.google.cloud.bigquery.QueryParameterValue.fromPb(QueryParameterValue.java:427)
	at com.google.cloud.bigquery.QueryJobConfiguration$Builder.<init>(QueryJobConfiguration.java:143)
	at com.google.cloud.bigquery.QueryJobConfiguration$Builder.<init>(QueryJobConfiguration.java:85)
	at com.google.cloud.bigquery.QueryJobConfiguration.fromPb(QueryJobConfiguration.java:813)
	at com.google.cloud.bigquery.JobConfiguration.fromPb(JobConfiguration.java:140)
	at com.google.cloud.bigquery.JobInfo$BuilderImpl.<init>(JobInfo.java:184)
	at com.google.cloud.bigquery.Job.fromPb(Job.java:307)
	at com.google.cloud.bigquery.BigQueryImpl.query(BigQueryImpl.java:595)
	at com.google.cloud.bigquery.BigQueryImpl.query(BigQueryImpl.java:567)
	at com.avoka.transact.insights.common.model.BaseQuery$DoSyncQuery.call(BaseQuery.java:489)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at com.google.apphosting.runtime.ApiProxyImpl$CurrentRequestThreadFactory$1$1.run(ApiProxyImpl.java:1249)
	at java.security.AccessController.doPrivileged(Native Method)
	at com.google.apphosting.runtime.ApiProxyImpl$CurrentRequestThreadFactory$1.run(ApiProxyImpl.java:1243)
	at java.lang.Thread.run(Thread.java:745)
	at com.google.apphosting.runtime.ApiProxyImpl$CurrentRequestThread.run(ApiProxyImpl.java:1210)

This occurs due to a number of reasons, detailed as follows:
QueryParameterValue.toValuePb does not set arrayValues when the provided array is empty:
if (arrayValues != null && !arrayValues.isEmpty()) {
  valuePb.setArrayValues(
      Lists.transform(arrayValues, QueryParameterValue.TO_VALUE_PB_FUNCTION));
}

google-cloud-bigquery defers to the older google-api-services-bigquery client library internally, which seems to strip empty arrays from the returned Job object, in HttpBigQueryRpc.create(Job, ...):
  @Override
  public Job create(Job job, Map<Option, ?> options) {
    try {
      String projectId = job.getJobReference() != null
          ? job.getJobReference().getProjectId() : this.options.getProjectId();

      // job.getConfiguration().getQuery().getQueryParameters() at this point is:
      //  [{name=transactionIds, parameterType={arrayType={type=INT64}, type=ARRAY}, parameterValue={arrayValues=[{value=688}, {value=689}, {value=690}, {value=686}, {value=687}]}}, {name=sessionIds, parameterType={arrayType={type=INT64}, type=ARRAY}, parameterValue={arrayValues=[]}}]

      return bigquery.jobs()
          .insert(projectId, job)
          .setFields(Option.FIELDS.getString(options))
          .execute();
      // getConfiguration().getQuery().getQueryParameters() on the returned job is as follows. Note that the 'arrayValues' field of the 'sessionIds' parameter has been dropped:
      // [{"name":"transactionIds","parameterType":{"arrayType":{"type":"INT64"},"type":"ARRAY"},"parameterValue":{"arrayValues":[{"value":"688"},{"value":"689"},{"value":"690"},{"value":"686"},{"value":"687"}]}}, {"name":"sessionIds","parameterType":{"arrayType":{"type":"INT64"},"type":"ARRAY"}}]
    } catch (IOException ex) {
      throw translate(ex);
    }
  }

@jscinoz Thank you for the report! This is a repro with public data:
public static void main(String[] args) throws Exception {
    BigQuery bigquery = BigQueryOptions.getDefaultInstance().getService();
    String[] words = {};
    QueryJobConfiguration queryConfig =
        QueryJobConfiguration.newBuilder(
                "SELECT word, word_count FROM `bigquery-public-data.samples.shakespeare` WHERE word IN UNNEST(@words)")
            .addNamedParameter("words", QueryParameterValue.array(words, String.class))
            .build();
    for (FieldValueList vals : bigquery.query(queryConfig).getResult().iterateAll()) {
      System.out.println(vals);
    }
  }

If words is not empty, everything works OK.

@pongad This use case works now? I am trying to use the library in Kotlin. I try to pass empty array, it doesn't work only works if the array is not empty.

I'm using version 2.17.1 of the library "google-cloud-bigquery" library and it's not working properly for me, passing an empty array to the query that has an array for that parameter. Is it possible this is a regression? Or a different library I'm using


mWeb - Expense - Renamed the report system message is shown incorrectly.

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: V9. 0.73-6
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: N
Email or phone of affected tester (no customers): N
Issue reported by: Applause Internal Team
Action Performed:

Go to https://staging.new.expensify.com/home
Open a workspace chat
Create a expense
Open the expense

Expected Result:
Renamed the report system message must not be shown.
Actual Result:
Renamed the report system message is shown incorrectly.
Workaround:
Unknown
Platforms:

[ ] Android: Standalone
[ ] Android: HybridApp
[x] Android: mWeb Chrome
[ ] iOS: Standalone
[ ] iOS: HybridApp
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/b96ac34b-bf14-4b05-95db-8a309b479f38
View all open jobs on GitHub

Production
https://github.com/user-attachments/assets/5766d058-1ec8-4885-8da5-8e3bee848e68

@IuliiaHerets is this an actual Deploy Blocker, or did you accidentally use the label?

@jliexpensify No, I added the label on purpose. Issue was reproduced in stg and prod with staging server off, issue was not repro with SS on.
QA team can still repro this issue
https://github.com/user-attachments/assets/0b23eb7c-ab35-44c3-bead-0080938c7107

Clarifying if this is a true deploy blocker here

Hi @francoisl - Applause seems to think this is a deploy blocker, but I don't think it is (and I can't repro). Puneet advised applying both labels here.

I can repro on Web on staging, looking now. Not sure if it's a backend or NewDot blocker yet, let's keep both labels for now.

This is a backend bug caused by https://github.com/Expensify/Web-Expensify/pull/44662/, removing the NewDot blocker label.

I think the revert of https://github.com/Expensify/Web-Expensify/pull/44662 worked and we're good to remove the blocker label.
https://github.com/user-attachments/assets/da7db0e1-480d-451d-8cb4-b53a0fc97e2d

Asked Applause for a retest here https://expensify.slack.com/archives/C9YU7BX5M/p1733940322271419?thread_ts=1733940210.713079&cid=C9YU7BX5M

We cherry-picked a backend fix https://github.com/Expensify/Web-Expensify/pull/44733. Both Scott and I confirmed the regression is no longer on staging, removing the blocker label.

Awesome, are we good to close this @francoisl @deetergp ?

Looks that way @jliexpensify. Closing!


Support for the XDG Base Directory Specification

Possible duplicate of #405  but it would be nice to have .hstr_favorites and .hstr_blacklist in XDG_CONFIG_HOME/hstr in pursuit of a cleaner home directory.

Makes sense 👍 - I will make it priority. Thanks!


Inconsistent indentation suggestions for Python

The Python style guide for docstrings gives inconsistent advice for indentation.  It initially says,

Sections should be indented two spaces, except for the heading

Yet all of the examples feature four spaces of indentation.  Further, under the Args section, it says,

If the description is too long to fit on a single 80-character line, use a hanging indent of 2 or 4 spaces (be consistent with the rest of the file).

Probably the first quote should read "Sections should be indented two or four spaces (be consistent with the rest of the file), except for the heading."

Thanks, internally we recommend two for this as it matches our internal coding convention. But I like your suggestion of just saying use either within the docstrings so long as it is consistent within the file. There is no strong reason to require four for docstring section indentation regardless of PEP-8 code four space indentation.

@gpshead as you said internally we recommend two spaces for code indentation. But this style guide recommands four. I think it should be changed to two?
See http://google.github.io/styleguide/pyguide.html#34-indentation

Nope.  The world at large should not be infected with Google's internal style quirks.  This guide keeps in line with PEP-8 and what the entire world's Python editor configs use: four space indentation.

Ok that makes sense. Thanks for the clarification!


Update schemas to 2.1 WD05

Updated schemas are available here: https://github.com/oasis-open/cti-stix2-json-schemas/tree/update-to-2.1WD03
Tests are failing because the stix2 validator hasn't been updated yet, but when it does we can merge this in.

It appears in the update-to-2.1WD04 that the change to remove the restriction where identifiers MUST be ONLY UUID4 wasn't made yet.

Are all changes from WD03 to current WD implemented? I know that UUID requirements were taken care of in my most recent PR, but is everything fully implemented, or is there leftover pieces from older WD's missing?

You are correct; these changes have been made and this can be closed now.


chore: add memo in ics20 packet data (cosmos#2411)

Description

Add memo field in ics20 packet data proto
closes: #2411

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against correct branch (see CONTRIBUTING.md)
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[x] Code follows the module structure standards.
[x] Wrote unit and integration tests
[x] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[x] Added relevant godoc comments.
[x] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[x] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

Full disclosure: I couldn't manage to update packet.pb.go file from cli (generate code from proto file), so for now, I updated the file manually (not ideal, especially when the file starts with "do not edit")
I updated the corresponding code in keeper & types for transfer; if someone can help me generate the packet.pb.go file from cli, that would be great!

Hi @alizahidraja. Thanks a lot for picking this up. Unfortunately, there was already a couple of branches opened here and here implementing the changes. I am sorry that the issue was not properly assigned and gave the impression that it was available. We should have assigned it immediately to the person that was already working on it.
Is it ok if we close this PR then? I am very sorry for the confusion. If you're interested in working on ibc-go issues, please take a look at our good first issues and help wanted issues. We hope you can find one interesting for you; otherwise, let us know and I am sure we will be able to find something else!

Hey @crodriguezvega! No worries at all :D
And yes, I will take a look at the ones with the mentioned tags


Bloom Perspective not allowing DB Switch

I am running into an issue with Bloom not connecting to Databases running a local instance of Neo4j Desktop 1.5.8, on a 5.8.0 DB using ports 7687 and 7474.
I had just installed a new version of the Bloom app.
I tried forcing a reinstall of Bloom, but that didn't change anything.
Sometimes Bloom will load the default database no problem, and usually if I reload Bloom it will tell me that there is no active DB. I can't find errors on the Neo4j Desktop side. When it does load, under perspectives it behaves normally for the default DB, but I cannot switch to my other DB.
I also spun up a new 5.8.0 DBMS to test there, same results.
Message in Bloom after a reload:

We couldn't find an active graph in Neo4j Desktop. Please check that you have connected to a graph.

Neo4j Browser does not display this behavior, allows switching between the default 'neo4j' and other databases without issue.

Recurring events in logs which may be related:
security.log:
2023-05-25 18:46:47.504+0000 INFO  {plugin-com.neo4j.plugin.jwt.auth.JwtAuthPlugin} Log in attempted for user 'neo4j'.
2023-05-25 18:46:47.504+0000 ERROR {plugin-com.neo4j.plugin.jwt.auth.JwtAuthPlugin} Invalid serialized unsecured/JWS/JWE object: Missing part delimiters
2023-05-25 18:46:47.504+0000 INFO  [neo4j]: logged in

debug.log:
2023-05-25 18:47:17.179+0000 WARN  [i.n.c.DefaultChannelPipeline] An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.
org.neo4j.bolt.runtime.BoltConnectionFatality: Terminated connection 'bolt-52' ([id: 0xd65fb4cc, L:/<IP_ADDRESS>:7687 ! R:/<IP_ADDRESS>:56852]) as the client failed to authenticate within 30000 ms.
	at org.neo4j.bolt.protocol.common.handler.AuthenticationTimeoutHandler.authTimerEnded(AuthenticationTimeoutHandler.java:91) ~[neo4j-bolt-5.8.0.jar:5.8.0]
	at org.neo4j.bolt.protocol.common.handler.AuthenticationTimeoutHandler.lambda$handlerAdded$0(AuthenticationTimeoutHandler.java:59) ~[neo4j-bolt-5.8.0.jar:5.8.0]
	at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98) [netty-common-4.1.92.Final.jar:4.1.92.Final]
	at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:153) [netty-common-4.1.92.Final.jar:4.1.92.Final]
	at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:174) [netty-common-4.1.92.Final.jar:4.1.92.Final]
	at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:167) [netty-common-4.1.92.Final.jar:4.1.92.Final]
	at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470) [netty-common-4.1.92.Final.jar:4.1.92.Final]
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569) [netty-transport-4.1.92.Final.jar:4.1.92.Final]
	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) [netty-common-4.1.92.Final.jar:4.1.92.Final]
	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [netty-common-4.1.92.Final.jar:4.1.92.Final]
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [netty-common-4.1.92.Final.jar:4.1.92.Final]
	at java.lang.Thread.run(Thread.java:833) [?:?]

Hai,
Sorry for the inconvenience, Could you please verify it happens only after upgrading to 2.8.0 ?
You can verify through About section in Bloom.
If yes, it's a known issue. It will be fixed in upcoming patch release within this week.
Thank you for reporting.

Updating to 2.8.1 resolved this issue.
Thank you!


Not working with powershell on Windows

Hi,
I’m facing issues with the extensions on Win 11 and Powershell.
I first encounter

and had to properly configure nvim:
vim.opt.shell = "pwsh.exe"
vim.opt.shellcmdflag = ""

but then I’m stuck on:

What am I missing?

Follow up, I have this config now:
{
        "aohoyd/broot.nvim",
        lazy = false,
        opts = {
            shellcmdflag = "-Command ",
        },
    },

and I don’t have any error messages anymore but the floating window is empty and disappears after a second or so.

OK I manage to make it work:
opt.shell = "pwsh.exe"
opt.shellcmdflag = "-Command "
opt.shellquote = '"'
opt.shellxquote = ""
opt.shellpipe = "| Out-File -Encoding UTF8 "
opt.shellredir = "| Out-File -Encoding UTF8 "

and
    {
        "aohoyd/broot.nvim",
        lazy = false,
        opts = {
            broot_conf_path = "C:\\Users\\Geob\\AppData\\Roaming\\dystroy\\broot\\config\\conf.hjson",
        },
    },

as C:\\Users\\Geob\\.config\\broot\\config\\conf.hjson is not the default path for broot on Windows


Add more API docs

What was wrong?
I wanted to have some docs on the trinity.protocol APIs
How was it fixed?
I ended up just documenting the events because those are consumable by plugins. I'm hesitant to add docs on other trinity.protocol stuff because there's still a lot in flux (proxy peer pool, multi protocol support, reduce exposure of peer etc)
To-Do

[ ] Clean up commit history

[ ] Add entry to the release notes PR

Cute Animal Picture

GTG, given that you've built the docs locally to make sure it looks right, and squashed any doc build warnings

I did but we also use the turn warnings into errors  feature so these things are caught in CI
https://github.com/ethereum/trinity/blob/d4161cd98f3b5caedde6f23c5321954ce25e3cbe/Makefile#L41

I did but we also use the turn warnings into errors feature so these things are caught in CI

Nice! That one doesn't seem to be everywhere yet, so I can't remember which repos do that. :heart:


Fix Issue 642: Throw exception for invalid accuracy values.

Throw exception for invalid accuracy values.
Document value requirements.

Thanks!


Not able to see the Graph

How do i see the graph as show in the read me on git page but i cant see that

Click the topic to get to a page of all its consumers, then click on a specific consumer group to get the graph.

I used to be able to see offsets and log size, and I upgraded to ZK 3.5.0 alpha and i can't see anything anymore.
Is there such changes between versions that this console can't connect to it?

in my zk logs I keep seeing:
2015-08-28 23:16:57,023 - INFO  [ProcessThread(sid:1015213 cport:-1)::PrepRequestProcessor@849] - Got user-level KeeperException when processing sessionid:0xad4f762d11380004 type:delete cxid:0xb8b zxid:0x2000001ca txntype:-1 reqpath:n/a Error Path:/consumers/web-console-consumer-54626/owners Error:KeeperErrorCode = NoNode for /consumers/web-console-consumer-54626/owners


Need an Authentication section

It's great that you have an authorization section, as that's so often overlooked, but an authentication section would be very welcome.  Things like Passport, Auth.js, and so on.

@freeborough There's a Web Authentication section. Maybe I should rename it to just Authentication? 🤔

@Maximization sounds good


coarse_match_mkpts_c

Than for your jobs！
And where is the "coarse_match_mkpts_c" in points_matchers\aspanformer.py line 122 ?

Hi~
It comes from a modified version of ASpanFormer. See here.
You can run git submodule update --init --recursive to achieve the modified point matchers.


Casting error in lbp.py

Found in: d866ef68ffe96de11e164493d29cc4b124cf7844
MY_FR_STUFF raised unexpected: TypeError("Cannot cast ufunc add output from dtype('int64') to dtype('uint32') with casting rule 'same_kind'",)
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/celery/app/trace.py", line 240, in trace_task
    R = retval = fun(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/celery/app/trace.py", line 438, in __protected_call__
    return self.run(*args, **kwargs)
  MY_FR_STUFF, in train
    model.train(images, labels)
  MY_FR_STUFF, in train
    self.model.compute(imgpp, labels)
  File "/usr/local/lib/python2.7/dist-packages/facerec/model.py", line 21, in compute
    features = self.feature.compute(X,y)
  File "/usr/local/lib/python2.7/dist-packages/facerec/feature.py", line 245, in compute
    h = self.spatially_enhanced_histogram(x)
  File "/usr/local/lib/python2.7/dist-packages/facerec/feature.py", line 255, in spatially_enhanced_histogram
    L = self.lbp_operator(X)
  File "/usr/local/lib/python2.7/dist-packages/facerec/lbp.py", line 97, in __call__
    result += (1<<i)*D
TypeError: Cannot cast ufunc add output from dtype('int64') to dtype('uint32') with casting rule 'same_kind'

Images  - list of np.ndarray (output from cv2.imread() and similar)
Labels - list of string
Data by itself looks ok.
Appears non-permanent. Maybe some checks or casts should be added?
Possible workaround:
result += ((1<<i)*D).astype(np.uint32)

or about.

NumPy version: 1.10.4


Custom styling in example usage

I'm new to react and was wondering if I could get a code example of custom styling. I've tried this so far:
<Markdown text={styles.text}>
  Some *really* basic **Markdown**.
</Markdown>

But to no avail. It would be nice if there was an example of styling in the documentation.

<Markdown style={styles.text}>
  Some *really* basic **Markdown**.
</Markdown>

is probably what you're looking for!

Great, thanks!


ModuleNotFoundError: No module named 'Vgamepad'

\genshin-dialogue-autoskip-main\autoskip_dialogue.py", line 5, in
import vgamepad as vg
ModuleNotFoundError: No module named 'vgamepad'
Do I have to install a virtual controller or something?

As of now you have to install the vgamepad too, even if you're only going to use keyboard and mouse.
You can install all required modules with pip install -r requirements.txt

Do I do this through cmd as admin?

cmd or any other command line interface will work. Admin privileges are not strictly required.
If you're on windows, one way to install the modules is:

Open the genshin-dialogue-autoskip folder with File Explorer
In the search window of File Explorer type cmd
In that cmd, type pip install -r requirements.txt

Hope that helps!

Two issues that might hold you back:

It seems like you run this command in C:\WINDOWS\system32 and not genshin-dialogue-autoskip's location (that's why I said to open the cmd from File Explorer
If pip is not recognized, that probably means you don't have Python in your PATH

So I'd say, reinstall Python and make sure that the "add to PATH" checkbox is checked. Then install required modules by following the 3-step process I described earlier. GL!

I actually didnt do either, I did both now and it works, Thank you!


Fix flush

Fixes #7

@dbuenzli , I've tested manually that the code works, but I have problems with running tests:
$ b0 -- trip_spec
[FAIL] [ocamlopt][2]: (b0 file log --id 21)
File "/Users/rafal/Projects/Tarides/cmarkit/B0.ml", line 2, characters 5-18:
Error: Unbound module Result.Syntax

b0: [ERROR] Could not compile B0 file /Users/rafal/Projects/Tarides/cmarkit/B0.ml

Any idea how to make it work?

Any idea how to make it work?

Yes sorry. You likely need an opam pin b0 --dev. I should make a release of b0.
In any case don't bother, looks corerct. Thanks for the issue and the fix.

I did the change myself. Thanks. Your patch is in as f2215cbc0f291e104b6fccd5ec8c6268e61e726d. If you confirm it works for you I'll do a bugfix release (there's already another one).

Works fine, thanks! :)


Enforce labels secretness

Fixes https://github.com/pulumi/pulumi-gcp/issues/1316
This is a WIP PR. The code should be complete, but there are not any tests.
Update:
The bridge is not currently set up to accept secrets from the engine:
https://github.com/pulumi/pulumi-terraform-bridge/blob/218029989c4c3e1086b576dada10f77ccff30cf9/pkg/tfbridge/provider.go#L537-L539
https://github.com/pulumi/pulumi-terraform-bridge/blob/218029989c4c3e1086b576dada10f77ccff30cf9/pf/internal/plugin/provider_server.go#L274-L279
The code in this PR propagates secrets, but it never receives secrets to propagate. Enforcing this will require allowing the bridge to accept secrets.

Blocked on https://github.com/pulumi/pulumi-terraform-bridge/issues/1506.


Improve Onyx.merge performance by informing listeners that a key has changed before persisting it in local storage

Context https://expensify.slack.com/archives/C01GTK53T8Q/p1618405920178400
Problem
When we set a key in onyx, the time it takes to inform listeners that they key was set is quite long. This is because we are waiting for the value to be saved to AsyncStorage, but there's really no need for that wait.
Solution
We can inform listeners that the value has changed at the same time we tell AsyncStorage to save it.
Coming from https://github.com/Expensify/react-native-onyx/issues/63 the Onyx merge path is:
Onyx.merge -> get -> set -> AsyncStorage.setItem -> then(() => keyChanged(key, val))

The idea is to trigger keyChanged at the same time setItem or set is called.

Is there any risk that we will call keyChanged() before it's saved to disk, which might create race conditions with whatever is in that callback -- which might do something that reads from disk, and expects that value to be set?

Great question, I really don't know, but thinking of it, it's totally possible someone uses it in the callback... so maybe we can't really change this.

Can you set up an example of how someone might read from the same storage key inside the callback ?
Also why would someone ever use it like that
Is this the potential problem?
Onyx.connect({
    myAlias: {
        key: 'SOME.ITEM',
        // keyChanged would trigger this callback
        callback: (data) => {
            // Yes calling Onyx.get('SOME.ITEM') is uncertain
            // But why would make such a call when I've just received the latest value in data

            // Retrieving other keys won't be a problem e.g. Onyx.get('OTHER.ITEM')
        }
    }
})

You can introduce this enhancement as a configuration for connect so whoever is using that method can opt in to that behavior
Onyx.connect({
    myAlias: {
        key: 'SOME.ITEM',
        callback: (data) => {/* ... */},
        // I hereby declare I just need the data ASAP and won't read from storage for the same key in my callback
        optimistic: true,
    }
})

On the surface, this idea sounds reasonable, but there is one piece I think we are missing
Scenario:

Data is prepared and we are ready to call set() after batching together merges
We call keyChanged() before set() (and assume the write will be fine)
The data fails to be set for some reason (storage exceeded most likely)
We now have a bad picture of state when calling get() then next time we merge() so that merge will possibly return incomplete data (since we are initial referencing what's in storage to make the merge in the first place)

So, I think is a problem, but I also think we are also maybe underestimating (or at least not considering) the time it takes to get() data before setting it. The most obvious solution to both would be to use a JS object memory cache this way we are never referencing what is in storage to apply a merge (besides from whatever data we dump into the cache when Onyx initializes).
I am optimistic that this will improve things, but besides the potential data loss stuff that I've brought up... would it be helpful to maybe just quickly benchmark a change where we put keyChanged before set() to see what improvements there are?

The data fails to be set for some reason (storage exceeded most likely)

But it will get stored eventually since we evict things from the storage when it's full, no?

would it be helpful to maybe just quickly benchmark a change where we put keyChanged before set() to see what improvements there are?

Yep! As well as measure where the time is spent (get, set, other?)

But it will get stored eventually since we evict things from the storage when it's full, no?

That's true, I was thinking of a hypothetical irrecoverable error where the write never happens at all and in this case the expectation would be that the app should still be able to sync the JS object store. But perhaps that's not a real problem yet.

Ok so this is just one test I ran but perhaps there are some better ideas...
Test
From completely empty storage measure the time it takes for Onyx.merge() to set post downloaded reportActions data to storage and then update the subscriber of the active report. This does not take into account network request time only the time between when data is returned from the fetch() and when the component props are updated with this data.
Web
Before:
Timing:expensify.cash.fetchActionsAndDataAvailableToOnyx 58
After:
Timing:expensify.cash.fetchActionsAndDataAvailableToOnyx 52
iOS
Before:
Timing:expensify.cash.fetchActionsAndDataAvailableToOnyx 63
After:
Timing:expensify.cash.fetchActionsAndDataAvailableToOnyx 59
Android
Before:
Timing:expensify.cash.fetchActionsAndDataAvailableToOnyx 558
After:
Timing:expensify.cash.fetchActionsAndDataAvailableToOnyx 482
There is some measurable performance impact, but I'd be curious to see a more global test. In general, moving the call to keyChanged() before set() improved timing a bit.
Note: Android looks much slower compared to others in this test, but we are comparing Apples to Androids and not all hardware emulation is equal.

hmmm from those numbers, it does not look like the change is worth it, agree?

Possibly, but to be fair, the test was pretty myopic. There was a 76ms savings in Android which could be significant. And keyChanged() also got called 168 times after set() on a cold boot so it could add up to some more significant delay.

I think we are already doing this as a side effect of the Onyx.get() proposed changes so I'm going to close this one.


Add write event support to HANDLE

Added write event support to WaitForSingleObject and WaitForMultipleObjects
Modified CreateFileDescriptorEvent to enable write event support
Fixed WSAEventSelect with lNetworkEvents == 0 as argument
Modified SetEventFileDescriptor to enable write event support, fixed missing bAttached to allow file descriptor cleanup.
Added winpr_log_backtrace

besides my remarks LGTM

+1


SignatureVerificationFailedException has a different naming pattern then the other exceptions

All the other Exceptions start with SecurityToken...
SignatureVerificationFailedException sticks out.
We should change to: SecurityTokenSignatureInvalidException.

SignatureVerificationFailedException was never used, so we just have to delete it.

https://github.com/AzureAD/azure-activedirectory-identitymodel-extens… #214


deep link should be lower case

deeplink parameters does not work if capitalized, all letters should be lower case for the deep link parameters to work
also added an example to enroll with username and servername

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


Microsoft.ManagedIdentity/userAssignedIdentities/federatedIdentityCredentials properties.audiences marked as required

Bicep version
Bicep CLI version 0.21.1 (d4acbd2a9f)
Describe the bug
Warning BCP035: The specified "object" declaration is missing the following required properties: "audiences". If this is an inaccuracy in the documentation, please report it to the Bicep Team. [https://aka.ms/bicep-type-issues]
Under the azure CLI audiences is optional, is there a reason for this discrepency between CLI and Bicep?
See docs: https://learn.microsoft.com/en-us/cli/azure/identity/federated-credential?view=azure-cli-latest#az-identity-federated-credential-create
To Reproduce
Steps to reproduce the behavior:
Create a Microsoft.ManagedIdentity/userAssignedIdentities/federatedIdentityCredentials without a properties.audiences
Additional context
None

correct, it worked.


Added the Search Bar in Music page

This PR contains:

The Search Bar added and integrated onto the Music page.
The Searches would be dynamic as the user types.
The Searches are supposed to align with the "Title" or "Label" of the music card for best results.
The Searched are case-insensitive.

https://github.com/nikohoffren/nikohoffrenmusic-homepage/assets/63151043/f76d6370-a4d6-435f-a69c-f25cc1664941

This PR contains:
* The Search Bar added and integrated onto the Music page.

* The Searches would be dynamic as the user types.

* The Searches are supposed to align with the "Title" or "Label" of the music card for best results.

* The Searched are case-insensitive.

VID_20230824_162909.mp4

That looks really good, nicely done! This makes the page much more user friendly and also good way to search music by year, label, name etc. Thanks for contributing to this project!


Apply turquoise body text link styling from Homepage to links in the stories and financials cards.

Apply turquoise body text link styling from Financials to links in the stories and financials cards. These are external links, can you make them open in a new tab? If that's difficult at this point, then skip for now.

The link color and bold are updated for links in stories, financial snippets, and the related fund's links. There's at least one other place where the link color isn't the same, but it follows the design. Let me know any other links that need changes.

Looks good
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Alex Finnarn @.>
Sent: Friday, October 29, 2021 1:13:26 PM
To: CUCentralAdvancement/essential-cu @.>
Cc: Yifei Wu @.>; Author @.>
Subject: Re: [CUCentralAdvancement/essential-cu] Apply turquoise body text link styling from Homepage to links in the stories and financials cards. (Issue #464)
The link color and bold are updated for links in stories, financial snippets, and the related fund's links. There's at least one other place where the link color isn't the same, but it follows the design. Let me know any other links that need changes.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/CUCentralAdvancement/essential-cu/issues/464#issuecomment-954986439, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AVYBARTD3P2SA6WRDVHIKDDUJLW5NANCNFSM5G7Z4TSQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Issue with Pronunciation

Chapter 13 - 4th phrase for "A funny paper/A Comic page   ᎤᏬᎵᏗ  ᎪᏪᎵ
Audio pronunciation of the word:  ᎤᏬᎵᏗ  (uwolidi) is incorrect on all 8 recorded voices for this phrase:  ᎤᏬᎵᏗ  ᎪᏪᎵ
The word ᎤᏬᎵᏗ  (uwolidi)  is being pronounced as uwosdi  ᎤᏬᏍᏗ -
All 8 recordings us the pronunciation with Ꮝ (s).  The Li ( Ꮅ ) is not used at all.
In looking up this word it shows as uwolidi - funny with various ways to write and pronounce it such as unohldi and uwotladiha.
Although there are other ways to say the word, none of the various references such as DAILP/The Cherokee Nation Word List/
OU Dictionary, show that an S ( Ꮝ ) sound is used in the word.  Uwosdi appears to be used with regard to apparel or wearing.
Is the problem with the Cherokee or English audio?
It is with the Cherokee
DO NOT EDIT BELOW
Problematic audio:

/online-exercises/source/chr/uwohldi_gohweli_en-333-f_a1.30_e663106ba9d26ed62fcc307ea341f86a7815bd0a.mp3

Additional metadata:
{"term":"uwőhldi go:hwe:li"}

I hear a lateral fricative and not an 's'.


Use $CHOOSE_ROS_DISTRO uniformly

Change uses of $ROS_DISTRO (the old variable name in previous documentation, if I recall correctly) to $CHOOSE_ROS_DISTRO.
Going the other way and unifying on $ROS_DISTRO would also work, but I am not aware of why $CHOOSE_ROS_DISTRO was chosen so maybe that was to avoid confusion with a ROS-provided environment variable.

@gbiggs @cottsay I think we can get this one merged after a rebase.

Ok, merging.


Using this for Code Commit --git-credential-AWSSV4.exe , This does not fetches the .Net SDK credentials set using SAML federation.  But instead this error is throw always

https://github.com/aws/aws-sdk-net/blob/5e89eed153496a9c0a6bc0d5279c9e409be2b787/sdk/src/Core/Amazon.Runtime/Credentials/_bcl%2Bcoreclr/StoredProfileAWSCredentials.cs#L142

My RegisteredAccounts.json
{
"9a85f8b3-127e-4e95-9414-0bbdaf31159b" : {
"EndpointName" : "ADFS-Demo",
"RoleArn"      : "arn:aws:iam::504971575277:saml-provider/ADFS,arn:aws:iam::504971575277:role/ADFS-Users",
"ProfileType"  : "SAML",
"DisplayName"  : "SAMLDemoProfile"
},
"9c18e795-4207-4816-9c33-567745427529" : {
"EndpointName" : "ADFS-Demo",
"RoleArn"      : "arn:aws:iam::504971575277:saml-provider/ADFS,arn:aws:iam::504971575277:role/ADFS-Users",
"ProfileType"  : "SAML",
"DisplayName"  : "default",
"Region"       : "us-east-1"
}
}

I am trying to setup CodeCommit + ADFS - SAML profile in a windows environment (without AWS CLI and ). If I use AWS CLI Git helper with .ini credential file format, git commands work without issues. But if I use git-credential-AWSSV4.exe and proper profile, then this error is thrown.
My .gitconfig files looks like this
[user]
name = Ameen
email =<EMAIL_ADDRESS>[credential]
helper = !'C:\Users\ameen\AppData\Roaming\GitCredStore\git-credential-AWSSV4.exe' --profile=default
UseHttpPath = true

Could you clarify what you mean by .NET SDK credentials?  Are you talking about encrypted stored credentials?  Those are only accessible by .NET SDK and VS toolkit.
The only credentials that git-credentials-AWSSV4 would work with is the credential pair in C:\users\<user>\.aws\credentials

Hi ssteven,
Yes you are right. I meant the credentials stored in C:\Users<username>\AppData\Local\AWSToolkit/RegisteredAccounts.json encrypted creds.
It would be ideal if the git-credentials-AWSSV4 would read the credentials stored after SAML authentication for federated users.
Also I see in code that this first looks for creds in SDK store if not found searches for the shared credentials file in user home location.
                _wrappedCredentials = ProfileManager.GetAWSCredentials(lookupName);

https://github.com/aws/aws-sdk-net/blob/5e89eed153496a9c0a6bc0d5279c9e409be2b787/sdk/src/Core/Amazon.Runtime/Credentials/_bcl%2Bcoreclr/StoredProfileAWSCredentials.cs#L114

This is not a supported use case.  :(
The encrypted stored credentials is a custom solution for .NET SDK and Toolkit.  It's not AWS wide specification.


[Enhancement request] merge spring.cloud.vault scheme+host+port property

Is your feature request related to a problem? Please describe.
Nothing frustrating, this project is pretty cool actually. But just wanted to start an enhancement request to make the property management better / simpler.
Currently, if one needs to customize the information regarding Vault backend, such as scheme, host, port, this has to be done via three separate properties:
spring:
  cloud:
    vault:
      scheme: https
      host: mycustomvault.com
      port: 1234
  config:
    import: vault://

The three properties are very well made, with default values.
However, one same information is scattered within three different places.
This also leaves room for guesses if one of the three is not explicitly configured.
Describe the solution you'd like
A solution backward compatible with the existing properties, where maybe a new property can be introduced, some kind of spring.cloud.vault.schemeHostPort=https://mycustomvault.com:1234 which would facilitate this configuration management.
An even better solution would be to merge this information with
spring.config.import=vault://https://mycustomvault.com:1234 something like that, which makes more use of the property spring.config.import=vault://
Describe alternatives you've considered
Looking at alternative in the Spring data portfolio, as well as Spring Kafka, many supports this one configuration where all information can be configured at once.
If not anything else, just wanted to say thank you to this cool project

I've also considered a spring.config.import=vault://mycustomvault.com:123 style. This would lead to the possibility of using various host names and ports such as spring.config.import=vault://mycustomvault.com:123,vault://another.one:8100.
Vault is stateful in terms of its session. We have a singleton session manager that is wired towards the endpoint and introducing hostname and port support for vault:// imports would introduce a whole new level of complexity that is rarely asked for.
In regard to schemeHostPort: Have you seen the spring.cloud.vault.uri property?

Example 2. application.yml
spring.cloud.vault:
    host: localhost
    port: 8200
    scheme: https
    uri: https://localhost:8200
    connection-timeout: 5000
    read-timeout: 15000
    config:
spring.config.import: vault://

host sets the hostname of the Vault host. The host name will be used for SSL certificate validation
port sets the Vault port
scheme setting the scheme to http will use plain HTTP. Supported schemes are http and https.
uri configure the Vault endpoint with an URI. Takes precedence over host/port/scheme configuration

Hello @mp911de ,
The explanation is very clear.
I didn't know about spring.cloud.vault.uri, many thanks for that.
With that said, I am still hopeful for a full integration, something like spring.config.import=vault://mycustomvault.com:123, as we do have this use case.
I understand it is not a popular demand, hence closing, but I will come back from time to time with a bit of hope it can help someone else as well.
Good day!


Can I use GPU to speed up this project?

Hello,
I'm using this project on my machine with GTX-1080ti GPU,
but this project seems to use only cpu resources.
Compute-Depthmap takes most of time during all process,
So I want to improve the speed of [Computing depthmap for images... with PATCH_MATCH_SAMPLE] by using GPU,
Are there any points in dense.py to apply the gpu?

Hey @kjkim-kr :hand: currently there's no GPU support in OpenSfM. Contributions toward implementing GPU support are welcome, however.

Hey @kjkim-kr  , I implemented GPU support for the OpenSFM repository, It can be found here #623 feel free to check it.


update1 test.js

added comments as required

Made the necessary changes

@archu5 thanks! You're now a contributor to Squirrelly!


Initial setup appears to not work in Firefox

I set up a fresh instance of Speedtest-tracker in Docker. On starting up for the first time, I was able to reach the user/login page and after entering the default credentials was returned to the "Getting Started" screen. Clicking on the link to return to the login just reloads the getting started screen. No errors in the logs. I re-pulled the container images with the same result.
I completed the first login in Chrome and since then am able to use Firefox.
Firefox
"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:120.0) Gecko/20100101 Firefox/120.0"

It was also not working for me, either with Chrome or FF.
I reverted to v0.13.3, which resolved it for me.

@parallax-home I'm going to change the title of this issue on you just so it stands out and reflects the actual root cause.


Error on load of plugin

Hello, first off, i love this plugin,
I do have this error on launch of neovim, can somebody help with this please ?
Thanks in advance

Update setup: https://github.com/ggandor/leap-spooky.nvim#setup.

Thanks !


pull request for post_train and post_infer

py file for post_traind and post_infer
refer to readme.md

확인했습니다. 좋은 결과물 만들어 주셨네여.


Add method for getting partial message from url to Client

Summary
Closes #1
Added get_partial_message to client which allows getting a PartialMessage object from a URL or Channel ID & Message ID combination.
I decided to not except the possible exceptions from fetching the channel to allow for developers to implement their own exceptions based on their use case. I have also tested this with Threads so all should be good.
Checklist

[x] If code changes were made then they have been tested.

[x] I have updated the documentation to reflect the changes.

[x] This PR fixes an issue.
[x] This PR adds something new (e.g. new method or parameters).
[ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
[ ] This PR is not a code change (e.g. documentation, README, ...)

Ideally I'd like this changed to a non-async method. All of our get_partial_* methods should be usable without making an API call. That's really the point of them.


Improve docs about configuration with env variables

 Issue by akshaymhetre
Wednesday Jul 28, 2021 at 02:44 GMT
Originally opened as https://github.com/neo4j-contrib/neo4j-apoc-procedures/issues/2120

I am using neo4j with docker version 4.2.5 and cypher file to initialize data.
I am setting following environment property to initialize data with docker-compose -
NEO4J_apoc_initializer_cypher=CALL apoc.cypher.runFile ("file:///sample.cypher")
This works fine and load the data after server started. However, you cannot create indexes in this file. You need runSchema call to create indexes. As per doc for neo4j 4.2, you can run multiple cypher,
NEO4J_apoc_initializer_cypher_0=CALL apoc.cypher.runSchemaFile ("file:///schema.cypher")
NEO4J_apoc_initializer_cypher_1=CALL apoc.cypher.runFile ("file:///sample.cypher")
However, this throws error:
unknown settings: apoc.initializer.cypher.0
unknown settings: apoc.initializer.cypher.1
Raised this on neo4j docker site as well.

 Comment by aowss
Wednesday Jul 28, 2021 at 12:10 GMT

Sorry @conker84 , i am confused. I might not have understood your comment correctly.
Are you suggesting to just drop the leading NEO4J_ part?
That's strange because :

all the docs ( including some of your comments on other issues ) mention that prefix
all the other environment variables seem to start with that prefix
the error message unknown settings: apoc.initializer.cypher.0 seems to have stripped that prefix

 Comment by conker84
Wednesday Jul 28, 2021 at 09:29 GMT

@akshaymhetre can you please try with?:
apoc_initializer_cypher_0=CALL apoc.cypher.runSchemaFile ("file:///schema.cypher")
apoc_initializer_cypher_1=CALL apoc.cypher.runFile ("file:///sample.cypher")

Looking forward to hearing from you!

 Comment by conker84
Wednesday Jul 28, 2021 at 14:03 GMT

Sorry @conker84 , i am confused. I might not have understood your comment correctly.
Are you suggesting to just drop the leading NEO4J_ part?
That's strange because :

all the docs ( including some of your comments on other issues ) mention that prefix
all the other environment variables seem to start with that prefix
the error message unknown settings: apoc.initializer.cypher.0 seems to have stripped that prefix

Yes @aowss you understood correctly, we leverage under-the-hood Apache Configuration that should be capable of recognising that kind of env variable and configure APOC properly.
I did a mistake in the copy and paste in the previous comment, use this env variable:
apoc.initializer.cypher.0=CALL apoc.cypher.runSchemaFile ("file:///schema.cypher")
apoc.initializer.cypher.1=CALL apoc.cypher.runFile ("file:///sample.cypher")

As I said Apache Configuration should be capable of understanding these.
Please lemme know

 Comment by conker84
Wednesday Jul 28, 2021 at 15:51 GMT

We definitely need to update the docs, I'm sorry I was sure that we did it in the past. I'll change the title of the issue

apoc.initializer.cypher is part of APOC and are documented here.
NEO4J_ ... environment variables a part of the Neo4j docker images and are documented here. Note that this page does not list the APOC environment variables.
The mechanism that picks up these two distinct set of environment variables is different. Likewise, they go to different configuration files in a non-docker setting (apoc.conf vs. neo4j.conf).
Nevertheless, the examples here are indeed wrong. I have issued a correction and clarification and it will show in the documentation in due time.

Correction: The use of the NEO4J_ also for docker is correct since the following fix: https://github.com/neo4j/docker-neo4j/pull/409/
Nevertheless, the issue has been addressed.


Bug when unsaved file is exists and try to exit overlay

If I select cancel to close file, overlay bar disappear.

The save file dialog on exit never showed up on my computer. What version of Sublime Text are you using?

Figured it out. This happens when hot_fix setting is set to false. Working on it now


Is Zero Trust Mode supported by React Native SDK?

Hi @lexer! Yes, the React Native SDK will also receive only the requestId in the response, if Zere Trust Mode is enabled.


Implement speech functionality

Overview:
This PR implements a new sonification display for Speech, using the Web Speech API; documentation for the API can be found here. It also includes another demo to demonstrate the functionality of the new display in conjunction with filtering data.
Functionality:
The display is built using SpeechSynthesis as the controller interface, as well as SpeechSynthesisUtterance as each speech request. The SpeechSynthesis is connected to a single utterance, which is then updated when a new data point is provided. Each data point is handled by updating the text of the utterance to appropriately say the given value.
When the Speech is started, it speaks the current utterance provided, and then clears the value in order to avoid using stale values. If the Speech is updated before the current utterance is done speaking, it cuts it off and begins to speak the next value, providing a "rude" implementation. Pausing is handled by effectively muting the Speech until it's started again, at which the volume is returned back to its original state.
The volume, rate, language, and voice of speech can all be adjusted within the constructor for Speech, as well.
Future additions:

Allow the speech's pitch to be appropriately mapped to the data point
Add into the UI a way to adjust the volume and rate of the speech

Great work @noramorsi! I noticed one small issue: if we pause when a value is being spoken, the audio pauses but the speech finishes speaking that point. I know we discussed this and from what I understand you attempted a fix by reducing the volume to 0. Does this work as it should (by pausing speech by turning the volume to 0 when the pause button is pressed) on your machine? I want to rule out the possibility of this being a browser specific issue.


Connection Name Conflict

Hi I have field resolvers on a GraphQL type that seem to be clashing because they each seem to define a type of Connection with the same name. I'm not sure how I can solve the error. I have the following:
#[derive(SimpleObject)]
pub struct ConnectionFields {
    /// Total result set count
    total_count: usize,
}

pub type ConnectionResult<T> = Result<Connection<Base64Cursor, T, ConnectionFields, EmptyFields>>;
pub type ConnectionOffsetResult<T> = Result<Connection<usize, T, ConnectionFields, EmptyFields>>;

Then in a field resolver on one graphql type:
    pub async fn produce(
        &self,
        ctx: &Context<'_>,
        input: GrowerProduceInput,
    ) -> Result<relay::ConnectionResult<Produce>> {
        ...
    }

Then on the second graphql type:
pub async fn produce(
        &self,
        ctx: &Context<'_>,
        input: ProduceSearchInput,
    ) -> Result<relay::ConnectionOffsetResult<Produce>> {
        ...
    }

These both seem to be causing the same GraphQL Connection ProduceConnection to be generated and then leading to a have same name error.
I'm not sure how to solve this as in my root schema.rs file I am using MergedObject on all my GraphQL types.
Do you know what I can do to work around this issue?

Although relay::ConnectionResult<Produce> and relay::ConnectionOffsetResult<Produce> are two different Rust types, but they generate the same GraphQL type name by default, both are ProduceConnection, which is the cause of the conflict .
You may consider renaming one of them to solve the problem, here is an [example](https://docs.rs/async-graphql/6.0.5/async_graphql/types/connection/fn.query.html#custom-connection -and-edge-type-names)

@sunli829 from the example it seems that gives the connection a static name, is there a way to keep it Dynamic but have a different Prefix/PostFix in the name?


[DEVHAS-359] use patch instead of update for status update

What does this PR do?:

use patch instead of update for status update
Which issue(s)/story(ies) does this PR fixes:

https://issues.redhat.com/browse/DEVHAS-359
PR acceptance criteria:

[ ] Unit/Functional tests

[ ] Documentation

[ ] Client Impact

How to test changes / Special notes to the reviewer:

/test images

/retest

/retest

/lgtm


Add-on is installing global custom command, but it can't be accessed (with DDEV HEAD) at ~/.ddev/commands

Discussed in https://github.com/orgs/ddev/discussions/6251
From @apotek:

Originally posted by apotek May 28, 2024
Hello, I have an add-on at https://github.com/ChromaticHQ/ddev-dblog/. Three days ago, it's test began to fail.
Leaving alone the bizarre fact that stable passes but HEAD doesn't even though they are identical, in the HEAD test output, there is no indication of the failure point. Everything looks fine until

not ok 1 install from release
# (in test file tests/test.bats, line 71)
#   `ddev get chromatichq/ddev-dblog' failed

More context...

Bash completion has been installed to:
  /home/linuxbrew/.linuxbrew/etc/bash_completion.d
Run ddev debug download-images >/dev/null
  ddev debug download-images >/dev/null
  shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
  env:
    HOMEBREW_NO_INSTALL_FROM_API:
Run cd ./ && bats tests
  cd ./ && bats tests
  shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
  env:
    HOMEBREW_NO_INSTALL_FROM_API:
    DDEV_GITHUB_TOKEN: ***
    DDEV_NONINTERACTIVE: true
    DDEV_NO_INSTRUMENTATION: true
1..3
# ddev get chromatichq/ddev-dblog with project ddev-dblog in /home/runner/tmp/test-ddev-dblog (/home/runner/tmp/test-ddev-dblog)
not ok 1 install from release
# (in test file tests/test.bats, line 71)
#   `ddev get chromatichq/ddev-dblog' failed
# Creating a new DDEV project config in the current directory (/home/runner/tmp/test-ddev-dblog)
# Once completed, your configuration will be written to /home/runner/tmp/test-ddev-dblog/.ddev/config.yaml
#
# Configuring a 'php' project named 'ddev-dblog' with docroot '' at '/home/runner/tmp/test-ddev-dblog'.
# For full details use 'ddev describe'.
# Configuration complete. You may now run 'ddev start'.
# ssh-agent container is running: If you want to add authentication to the ssh-agent container, run 'ddev auth ssh' to enable your keys.
# Not trying to add hostnames because DDEV_NONINTERACTIVE=true
# .....Installing chromatichq/ddev-dblog:v1.0.0
# Downloading https://api.github.com/repos/ChromaticHQ/ddev-dblog/tarball/v1.0.0
#
# Installing global components:
# 👍 commands/db/dblog
#
# Executing post-install actions:
# chmod: cannot access '/home/runner/.ddev/commands/db/dblog': No such file or directory
# failed to change mode of '/home/runner/.ddev/commands/db/dblog' from 0000 (---------) to 0000 (---------)
#
# 👎
# Could not process post-install action (0) ''

When I run the same commands in my shell, I am able to download/add the add-on just fine.
My guess is that maybe the test have  changed and I need to update them? I am looking for docs on how to diagnose and fix failing add-on tests... What steps should I take?
Thank you.

Answer from the discussion:
What's going on (I think) is that in the latest (2) commits in DDEV HEAD the XDG_CONFIG_HOME environment variable is supported, and Github actions has XDG_CONFIG_HOME set. That means that DDEV is going to try to put the dblog command into ~/.config/ddev/commands/db/dblog. It's doing that... but then your post-install action is trying to find it at the ~/.ddev location.
So the HEAD tests did what they want to do and told us when something is failing...
However...

Please remove the chmod, as it's not necessary anyway, DDEV does that for you. Or check it in with executable.
You don't need the removal_action, because DDEV will remove things that you installed with your install.yaml.

So removing those two will solve this.
However, I'm going to convert this to an issue for now because this general problem may affect other add-ons that make assumptions about where the global DDEV config dir lives.

Answer from the discussion:
What's going on (I think) is that in the latest (2) commits in DDEV HEAD the XDG_CONFIG_HOME environment variable is supported, and Github actions has XDG_CONFIG_HOME set. That means that DDEV is going to try to put the dblog command into ~/.config/ddev/commands/db/dblog. It's doing that... but then your post-install action is trying to find it at the ~/.ddev location.
So the HEAD tests did what they want to do and told us when something is failing...
However...
* Please remove the chmod, as it's not necessary anyway, DDEV does that for you. Or check it in with executable.

* You don't need the removal_action, because DDEV will remove things that you installed with your install.yaml.

So removing those two will solve this.
However, I'm going to convert this to an issue for now because this general problem may affect other add-ons that make assumptions about where the global DDEV config dir lives.

First and foremost, THANK YOU for taking the time to answer and explain. I ended up with a few questions:
I removed my post_install_actions and removal_actions from my install.yaml file and pushed back up to main. So unless I am missing something fundamental, HEAD should now have an install file that does not try to chmod or remove. However, when I ran the tests (triggered manually), the test still attempts to run the same actions.
I still get:

# ddev get chromatichq/ddev-dblog with project ddev-dblog in /home/runner/tmp/test-ddev-dblog (/home/runner/tmp/test-ddev-dblog)
not ok 1 install from release
# (in test file tests/test.bats, line 71)
#   `ddev get chromatichq/ddev-dblog' failed

in the output, and the post_install action is still triggered, despite it no longer existing in the install.yaml file.
So that is head-scratcher number one for me.
The second head-scratcher is that you reference, in your answer ~/.config/ddev/... whereas I don't have that directory. I only have ~/.ddev/....
Do I need to be updating my tests? And if so, is there a documented way to do that? (Basically refresh the add-on template in my existing add-on). Thanks again.

You changed your code but didn't do a release. So when it does "install from release" it's still getting the old code.
On Github Actions (linux) GitHub sets XDG_CONFIG_HOME, which on DDEV Head now respects, and it's set to ~/.config/ddev . The default for DDEV remains ~/.ddev, but Github Actions by setting XDG_CONFIG_HOME causes the new behavior. I'm currently trying to sort this out in
https://github.com/ddev/ddev/pull/6239

Thank you @rfay . Tests are now passing.
Lessons learned (in case anyone else is reading):

If your changes are related to the tests themselves, you will need to create a release to test those changes.
Try not to assume paths that work will continue to work. See if there is an environment variable that gives you what you need.
Don't test more than you need to test. (In this case, adding actions that weren't necessary).

Thank you for the overview @apotek !

If your changes are related to the tests themselves, you will need to create a release to test those changes

That actually isn't correct. It's when the changes are related to the functionality that you need to create a release for it to work. But it's confusing!

https://github.com/ddev/github-action-add-on-test/issues/30 proposes not running the release test on a PR.

Glad it's working for you!


DevPool by Ubiquity DAO v0.1

Project Abstract
DevPool is a crypto-native platform that organically sits on top of GitHub to optimally match developers with open tasks and get paid in crypto while automating the administrative components for DAOs and Repo managers.
https://github.com/ubiquity/
Grant level

[ ] Level 1:  Up to $10,000, 2 approvals
[x] Level 2:  Up to $30,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[x] I have read the application guidelines.
[x] Payment details have been provided (bank details via email or BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (USDT) address in the application).
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
[ ] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @rser:matrix.org (change the homeserver if you use a different one)

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

Thanks for your interest in our grants program. I know this is still in the draft status, but I just want to provide already some feedback here. The most important part of the application is usually the milestone tables of our template, including the default deliverables. Also ideally the deliverables are included in the application itself (=contract) and not in a linked document. Apart from this, I recommend including Polkadot-specific technical deliveries and integration.

@Noc2 Hello, great thank you for the valuable feedback!

Thanks. Let me know once I should take another look at the application.

I'm closing the application due to inactivity. Let me know if I should reopen it.

I'm closing the application due to inactivity. Let me know if I should reopen it.

Yes, this draft PR should be closed. We'll create a new one when we're ready. Thank you!


African Growth and Opportunity Act

Kenya has been among the key beneficiaries of the African Growth and Opportunity Act (AGOA). AGOA is a trade provision by the US Government that offers tangible incentives for African countries to continue their efforts to open up their economies and build free markets. Sectors such as tea, horticulture, textile and apparels, coffee, tobacco products among others have fruitfully benefited from the AGOA trade provision.
Despite the success and the subsequent formation of a special AGOA unit under the Ministry of Trade (MoT), Kenya is still far from realising the potential under AGOA. For instance, in the apparel sector, out of the 18 garment makers in Kenya's export processing zones (EPZ), only one is Kenyan-owned. Similarly, out of the over 6400 products allowed to be exported under AGOA, Kenya only exports under 20 products. Other challenges Kenya faces in taking advantage of AGOA include;
US market requirements that need to be met
Transportation costs to different markets Erratic and costly electricity supply Complicated and burdensome customs and trade regulations Establishing how to manage entry into a comparatively new market ACTIF has been in the fore front leading advocacy to the US government on the extension of AGOA beyond the expiry deadlines. ACTIF wants to assess the extent to which other Kenyan businesses, other than those in the cotton and textile sector, have taken up the business opportunities offered by AGOA. The assessment will also establish policy changes needed in Kenya to ensure more awareness and participation by the private sector under AGOA.
Expected Outcome
ACTIF expects that the AGOA uptake assessment exercise will develop a strong position for both ACTIF and the Kenyan Government to present at the annual AGOA forum, 2013. The forum is an excellent platform to present Kenya's and ACTIF's position given that the key US Government officials will be participating.
Key among the positions that ACTIF wants to advocate is the extension of AGOA beyond 2015 to allow the African economies to be fully developed and able to complete adequately for the US market.

no one


Incorporating vector node features

Hi, nice work! I was wondering what it would take to accommodate for systems with nodes that have additional non-scalar features. Any hints or snippets would be greatly appreciated. Thanks.

Hi @patriksimurka
The node embeddings have the shape (num_nodes, (1 + L_{max}) ** 2, num_channels).
To add scalars to the node embeddings, we can first expand the scalar properties to have num_channels channels, and then add those scalar vectors to the type-0 part:
num_channels = 128
lmax = 6
num_nodes = 128
node_embedding = torch.randn(num_nodes, (1 + lmax) ** 2, num_channels)
input_scalar = torch.randn(num_nodes, 1, num_channels)
node_embedding[:, 0:1, :] = node_embedding[:, 0:1, :] + input_scalar

For type-1 vectors, you can do the following:
type_1_vectors = torch.randn(num_nodes, 3, num_channels)
node_embedding[:, 1:4, :] = node_embedding[:, 1:4, :] + type_1_vectors

Basically, the second dimension of node_embedding in the above examples corresponds to [one type-0 vector, one type-1 vector, ... one type-lmax vector]. So you can just add the type-L vector to the corresponding slice.


Add Alerts of the Create Dataset Form

Overview of the Feature Request
Add all Alerts related to the Create Dataset Form.

What kind of user is the feature intended for?
This feature is intended for all users.
What inspired the request?

Suggestions from the beta proposal labeled as "nice to haves."

What existing behavior do you want changed?
None
Any brand new behavior do you want to add to Dataverse?
Add all Alerts related to the Create Dataset Form.
Any open or closed issues related to this feature request?

#316

It depends on:

https://github.com/IQSS/dataverse-frontend/pull/334


participant profile / clearbit / privacy issues

I searched for anything related and didn't spot anything obvious. However...
I noticed that N1 is using clearbit to lookup information about users you are interacting with, as part of the participant-profile package. Unfortunately, this package is non optional, so it's not possible to disable this API lookup.
This is quite a privacy violation -- it's leaking the full sender information to clearbit, without any way for the user to choose whether or not they are OK with this. Fortunately, it's all over SSL.
Also, why is there no cache of this at all? Even if for a session-only cache -- the data is requested repeatedly.
Related to this is the nylas-private-analytics package, which I assume is simple usage data, but again is not possible to opt-out, which is really poor privacy and user engagement.
For a company which has a full copy of ALL my email, i'd prefer to see a stronger commitment to protecting my privacy.

This project is open source. You can fork it, remove the the packages you don't like, then run it. ;)

Hey—thanks for the feedback! As always, you're welcome to fork the project if you'd like to create your own build that excludes certain features.
The Clearbit data is cached client-side while the app is open, but only if Clearbit returns a "final" response for a particular address (a 200 rather than a 202). That may have been what you were seeing.  It's also worth noting that the requests are proxied through our infrastructure, so your Clearbit API requests are indistinguishable from others when they reach Clearbit. They all come from the same IP address and contain no information about you, only the recipient email.
We're committed to protecting your mail data (see nylas.com/security), but we're also committed to building the best mail experience, which involves long term planning based on the vast majority of consumers and quantified assessment of which features people use, how fast the app is performing in the wild, etc.
Thanks!

@bengotow does this mean that you will never close this issue?
Could you please list all the cases when and where your servers are called and why it ?
@imajes did you find any fork or other solution?
Privacy issues seem to be a big topic here although these tickets are always closed by Nylas members ( i.e. #1082, #1681, #1339, #1444, #2432 or #2432 )

I completely agree with some of the previous comments:
By the way: By installing Nylas Mail, you agree that your email contacts will be send to the third party service clearbit.com. Accept this, fork and modify or leave.
Doesn't sound fun at all!
Now let's have a closer look at what clearbit.com does with the millions of emails you send them on a daily basis: "We may disclose your Personal Information to law enforcement, government officials, or other third parties" and "in the event of a merger, acquisition, reorganization, bankruptcy, or other similar events, any information in our possession may be transferred to our successor or assign".
The fact that this is an open source app, makes this sort of privacy invasion even worse. What's easy for me to do (either block the connection or rebuild the app), isn't nearly as easy for probably 90% of the world population. So, we're making the assumption that
a) they are happy with their emails being send to clearbit
b) if they are not, they will simply fork the app or move on
I'd suggest to simply allow users to turn this off and be done with it. What's the problem?

@alexanderadam from what I can see, Nylas Mail calls the following servers:
Nylas Mail via Nylas Mail Helper
n1.nylas.com - probably billing / sends info about Nylas Version, OS
clearbit.com - via proxy, Nylas Mail sends Email address to clearbit.com
api.segment.io - link and click tracking notification?
k.root-server.net
f.root-server.net
j.root-server.net
omniprox-3.nylas.com - proxy for clearbit.com?
<IP_ADDRESS>
192.203.330.10
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
imap.fastmail.com - my email provider, OK
smtp.fastmail.com - my email provider, OK
Nylas Mail
sentry.io - error reporting?
omniproxy-3.nylas.com
n1.nylas.com - probably billing / sends info about Nylas Version, OS
Apparently their hosted service (Nylas Pro?) runs on AWS, hence the IP's change frequently. This is documented here but this is still an astonishing number of connections for a mail client, that's supposed to retrieve and send emails.

@franzos thank you for the awesome analysis!
I guess there won't be a better solution than really fork it, remove tracking and allow the usage without nylas servers. 😞

@alexanderadam I'm just disappointed.
The only reason I'm here is, because I believe that Nylas is building an amazing mail client. A unified interface across platforms, seamless integration with 3rd party apps such as CRM or data enrichment. However, by default Nylas Mail should communicate as LITTLE as possible. That means, after your first download and install, there should be 0 network activity. Only once you add your email accounts or enable this sort of data enrichment (clearbit.com), Nylas Mail should connect to the relevant servers.
Instead, users that simply don't know any better, download Nylas Mail (and previously N1) and have, for some part, no idea what's actually happening with their data. Alone the fact that all my email contacts are send to clearbit.com, is a huge red flag which I would like to protect users from! Who knows what else is going on behind the scene and what sort of arrangements Nylas Mail has with these individual vendors.
Here's what the average user goes trough to send an Email:
OS: Microsoft Windows - phones home to Microsoft, collects statistics about you
Mail provider: Google Mail - processed, enriched with Ads (they make money with your identity)
Mail client: Nylas Mail - sends all your contacts to wherever
Internet (ISP) -  collects information about what you do (they make money with your identity)
It seems like a bad joke.

We don't share contact data with Clearbit. To make a Clearbit API request you need to send the email addesss as a query parameter. We proxy this server-side to anomoize the

@grinich Clearbit could be hacked, acquired or transform into a completely different business. In other words, all the people I've been in touch with, stand to lose their Email address to yet another corporation. Sure, the Clearbit integration is a fantastic idea and useful especially in sales but why can't we turn this into a plugin and make it optional - you know, for sales people.
Just by using Nylas Mail, my data goes to a lot of services:

Yourself (Nylas)
Clearbit.com (Enrichtment)
Sentry.io (Error tracking - but what data is being logged? My IP?)
Segment.io
?

Don't you find this a bit worrisome as default?
At the end of the day, I'd love to see a Nylas Mail that makes no assumption about it's users. I fully support the argument that you're building the best mail experience ever but on the way, please take a look at what YOU can do to help protect your users privacy. It's surprisingly easy: Not more secure, hack-proof infrastructure but simply less data / leaks / logs / services.

Since we did the open sores merge last night, I'm actually not sure how much of these packages exist in the main Nylas Mail repo. Happy to look at PRs that disable them or encourage forks with them removed completely.

*Open Source yikes autocorrect (I'm on my phone)

@grinich that would be great. Let's see what happens over the coming weeks.

clean version is definitely needed

There exist privacy respecting alternatives. Search for them. Also checkout @franzos' comments and @herrbischoff's Questions regarding privacy and project motivation.

My questions were never answered in a satisfying way. As you can see from now a dozen or so similar issues, Nylas simply don’t care about changing their product to be more privacy-respecting. As they never gave good reasons for doing what they do, one can only surmise it’s because of some financial motivation having to do with user data.
The “fork it or shut up” approach further undermines the motivations for open sourcing it in the first place. It appears to have something to do with reaping the benefits of free work from submitters, trying to build a platform, but pocketing the rewards privately.
Those are just some of the impressions you get when you are a little privacy-conscious, whether they are correct or now.
Whatever Nylas’ true motivations are (and I don’t doubt there are “true believers” just like in Facebook), I suggest an easy way: just don’t use it. It’s a shame, yes, but when you deal with a tone-deaf entity, eventually it’s time to let it go. They won’t change. They want something that is deeply linked to the way they built it. You should walk away and find a better solution. It wouldn’t be the first time that certain technology would have to be reinvented because the original inception was fiercely defended against change.
In the end, as long as people want stuff for free instead of paying a couple of bucks for privacy, “business models” like this one work. Unfortunately it’s a systemic problem that may only ever be resolved on a policy level, explicitly forbidding data mining or user profiling.

@herrbischoff I completely agree with you but this project is pretty much dead. I'd suggest you to checkout #3621. There are two, promising alternatives based on Nylas mail:
https://github.com/Foundry376/Mailspring
https://github.com/nylas-mail-lives/nylas-mail

I see, so they finally revealed their true face in closing everything down and making it a commercial-only venture.

@franzos, @herrbischoff, thanks for getting touch. I stared holes into their website and the issue tracker on my quest to find out, if I'm the product here for quite a while.

Mailspring follows Nylas' approach with a "Mailspring ID".
Nylas-mail-lives seems to deliver the promised land. Has some issues, though:

I would just stay clear from this clusterfuck altogether. It is just not meant to be used in a privacy-friendly way. Imagine being given all of Facebook’s source code. You wouldn’t be able to decouple its tracking functions from the social media functions. They’re one.

What's all this negativity? Kudos to the Nylas Mail developers for bringing us such an amazing, flexible mail client and respect to everyone who's working to continue fixing bugs and making sure that we can enjoy this experience, on virtually every mainstream OS.
I sure don't agree with all the features but it's an open source project after all, and in time, we will see forks that fixes these privacy issues (mostly Clearbit integration). If you're familiar with your OS firewall software, or the host file, feel free to block all connections except for IMAP / SMTP.
Aside from that, since we're all so concerned about privacy, I hope you're all running a custom-build Linux / Unix OS because Mac OS / Windows / even Ubuntu loves to phone home. I've probably got 100+ entries in my host file, just to keep Mac OS quiet. Let's not talk about all the other applications, that are quietly phoning home...

@franzos, indeed. I'm a big fan of: https://surf.suckless.org/files/adblock-hosts using hosts-gen. 😊


Fix the calculation of start and end times for GetMetricData

Fixes #479
This PR tries to address the problems I outlined in #479.
Here's what I did:

Updated to always use the wall clock time to calculate start/end of GetMetricData requests
Remove the hard coded 5 minute rounding of time currently done prior to finding start/end times and instead round based on the shortest configured period for the scrape job
Add a config option to the job which allows users to easily control the rounding of the time. This is especially useful when someone has a very long period such as 1 day (for S3 metrics) but doesn't want to the time rounded to the nearest day.
Remove the floating-time-window flag. The same functionality can be achieved by setting the new roundingPeriod configuration option to 0.
The fips arg was unused by some functions, so I removed it from all function params where it wasn't used (just basic cleanup work, I can put it back if you need it?)
Extract constants for default period, delay and length settings

Looking forward to your feedback!

Awesome will review this Thuersday Morning! - Thanks a lot.
I am so full of client work currently / switched to being freelancer that I did not find to fix anything yet. So happy to see this PR and work on it.

Hey would you be so kind and fix the linting issues @csquire ? :)

@thomaspeitz I think it should be good now for the linting, IntelliJ failed me. 😉
I also rebased the branch.


d3 v4

It would be great to have this library to work with d4 v4.
If someone could lay out a plan for it I could try to tackle that.

hey, sorry for the horrendous delay on my answer, I've started working on the update to d3 v4, stay tuned...

[ ] make the required modules of d3 a dependency
[ ] migrate build system to rollup
[ ] add webcola as a dependency? it would be awesome to treat the layout engine as a pluggable module

I upgraded the app to use d3 v6, this is released in the alpha tag
npm install greuler@alpha

I upgraded the app to use d3 v6, this is released in the alpha tag
npm install greuler@alpha


[FIX] Consistently refer to Neuromag/Elekta/MEGIN

closes #1309

Thanks for your report @robertoostenveld -- I have looked through the spec to see where else we are inconsistently referring to that system that has been owned by three manufacturers.
In this draft PR I have naively changed the naming to Neuromag/Elekta/MEGIN, however:

If we want to go through with this, some metadata field values have to be deprecated. For example ElektaNeuromag is currently a restricted keyword for the MEGCoordinateSystem metadata. We can change it to be NeuromagElektaMegin, and deprecate EletaNeuromag, that is, print a warning when somebody uses that "old" term and recommend they use the new one instead.
if this MEG system changes "owners" in the future again, e.g., to company XYZ, are we then calling it Neuromag/Elekta/MEGIN/XYZ?

This PR can remain a draft until we've discussed these issues.

Does it make sense to just declare that these are synonyms that SHOULD be used consistently throughout a dataset, and then we use one consistently throughout the spec (linking to the bit about synonyms)?

@robertoostenveld what do you think about the two points mentioned in my OP, and about Chris' point?
Perhaps @ftadel and @Moo-Marc  can offer additional opinions?

I like the idea of considering them as synonyms, that also aligns with (non-technical) use of these in regular conversations.
With FieldTrip I also suffered from this (also for other companies), which I why I at a certain point adopted the strategy to refer to them as "old/new/newer/evennewer", as that at least puts them in a consistent order. But considering them as synonyms is better, and aligns better with the actual market situation. E.g. Elekta (the company) might not like it nowadays that we still refer to their name in relation to MEG systems that are currently not manufactured by them any more (but by MEGIN), whereas labs that purchased their system a few years back will still have the old brand stickers on the scanner and probably prefer to refer to that system as their "Elekta" system, and not the name it would have had - had they bought it recently.

another similar update would be desired for the MEG system that was initially designed at the Kanazawa Institute of Technology (KIT), later produced and supported by Yokogawa and that now continues at the Ricoh company (we have a copying machine of them, not a MEG system). That should be considered the KIT/Yokogawa/Ricoh system

+1 for synonyms. Could this also apply to keywords?  Instead of renaming ElektaNeuromag, could we have Neuromag, Elekta and Megin as synonym keywords?
Even CTF has renamed itself at least 4 times, though people kept calling them CTF, hence its return: CTF, VSM, MISL, CTF MISLP, CTF Neuro Innovations

I decided to go the deprecation route here. Let's discuss the "synonym" idea again when one of our supported manufacturers actually changes their name. The changes here are "bug fixes".
Ready for review / merge @effigies @robertoostenveld @Moo-Marc @Remi-Gau


[TechDocs HomePage] Docs Favorites

This is a sub-issue out of #2028.

As a software engineer, I should be able to favorite any documentation page.
As a software engineer, I should be able to see my list of favorited documentation pages on the TechDocs HomePage.

On the TechDocs HomePage, a "Your Favorites" box should be displayed showing the signed in users documentation favorites.

Note: This issue may be blocked by a more global favorite feature in Backstage.

Hi, I'm wondering what the status of this issue is in terms in prioritization or any additional details about the "global favorite feature" encompassing this?
I noticed there might be a potential implementation by leveraging the EntityListProvider and UserListPicker used by the catalog in conjunction with the DocsTable component to create a custom TechDocs home page that looks similar to the catalog with support for starring docs (assuming support for starring doc entries is implemented by the DocsTable component). This would also remove the need for a separate "Owned" tab
May be interested in contributing the above implementation if it makes sense

I put together a PR to demonstrate my proposed implementation, let me know if this is a viable solution here


error in execute in production

Hello,
When I build to production after npm start I've got errors in the models : it say thatn not give schemo of model it seams not detected the js only TS.
I think it take in .env the :

PATH STRUCTRUE

TYPEORM_MIGRATIONS=src/database/migrations//*.ts
TYPEORM_MIGRATIONS_DIR=src/database/migrations
TYPEORM_ENTITIES=src/api/models//*.ts
TYPEORM_ENTITIES_DIR=src/api/models
CONTROLLERS=src/api/controllers//*Controller.ts
MIDDLEWARES=src/api/middlewares//*Middleware.ts
INTERCEPTORS=src/api/interceptors//*Interceptor.ts
SUBSCRIBERS=src/api/subscribers//*Subscriber.ts
RESOLVERS=src/api/resolvers/**/*Resolver.ts
and not the .js files ...
Thanks

to works i must remplace the all .ts in the .env to .js ....


Rename Templatizer->Templatize & add bc Templatizer behavior

Rename Polymer.Templatizer library to Polymer.Templatize & add pseudo-backwards-compatible Polymer.Templatizer behavior for slightly better hybrid support.
For now, users will need to implement both 1.0 & 2.0 callbacks differently (to e.g. deal with path differences due to removal of Collection, different TemplateInstance API, etc:
Example hybrid element:
Polymer({
  ...
  behaviors: [ Polymer.Templatizer ],
  // 2.0 callback implementation
  _fwdHostPropToInstance function(inst, prop, value) { /* use 2.0 API */ },
  _fwdInstancePropToHost function(inst, prop, value) { /* use 2.0 API */ },
  // 1.0 callback implementation
  _forwardInstancePath function(inst, path, value) { /* use 1.0 API */ },
  _forwardInstanceProp function(inst, prop, value) { /* use 1.0 API */ },
  _forwardParentPath: function(path, value) { /* use 1.0 API */ },
  _forwardParentProp: function(prop, value) { /* use 1.0 API */ },
  ...
});

@kevinpschaaf could you check these issues please?
#3755 #3307

Having the tests for iron-list 2.0 in hybrid mode passing, I think the changes LGTM. Thanks!

@blasten We treated this PR as an overall review of the 2.0 Templatizer API, and made the following changes:

Renamed callback fwdHostPropToInstance -> forwardHostProp
Renamed callback fwdInstancePropToHost -> notifyInstanceProp
Renamed behavior callback _fwdHostPropToInstance -> _forwardHostPropV2
Renamed behavior callback _fwdInstancePropToHost -> _notifyInstancePropV2
templatize now takes 2nd arg for the binding context of the callbacks (normally this of the element calling templatize)
removed first argument of forwardHostProp callback
TemplateInstance constructor no longer takes host argument
TemplateInstance API forwardProperty & flushProperties removed
TemplateInstance API forwardHostProp added, should be called from forwardHostProp callback

Refer to e.g. dom-repeat implementation for usage changes...