Unable to run on react typescript template

Tried running the playground project and it works fine . However when i integrate the new syntax with reactjs typescript template with fields still get the "Maximum stack error". Can you please help me with running the playground code with the attached template react ? I am quite clueless as to what needs to be done to get this to working.
I have tried with changing tsconfig values with no luck. Thanks in advance.
exp-app - Copy.zip

Sure, let me download the attachment and find a convenient approach.

Hi @franferns
First of all, I've reproduced your problem using the sources provided. Since this thing was driving me mad I've inspected it thoroughly. It seems that the approach with properties defined directly on Model classes is not going to work and it has little to do with typings.
Redux-ORM build generates different transpilation outputs for Node.js and loader environments (lib and es folders in the npm package), which I had wrongly suspected of being responsible for the issue.

I have tried with changing tsconfig values with no luck. Thanks in advance.

create-react-app pipeline for TypeScript apps is built around Babel, TypeScript source transpilation included and the tsc isn't actually used anywhere besides tooling. As a result, there are subtle differences between transpilation outputs and the shape of class properties being one of them - details in related babel issue.
Bottom line is that the types are not going to work this way, at least not until the issue is resolved or not with Babel-based TypeScript transpilation.
I'm back to optimizing types on master branch, In the meantime you might be able to progress by swapping MutableQuerySets with QuerySets where applicable.

You can track optimization progress at #5

Hi @franferns
I've managed to get it working 🕺
I've created a repo with a minimal working example:
https://github.com/tomasz-zablocki/redux-orm-ex-types-react-example
Check the README for details - any questions are welcome.


[TC-OO-3.2] How to run Simulated Test?

Describe the bug
I'm testing the switch app. In Simulated Test TC-OO-3.2, you need to commssion the DUT to TH, and then issue a command like on/off to pass the test. However, the parameters required for commissioning are not given in the step, and there is no bind operation for DUT and other device, so I don't know who to send the onoff command to.
May I ask if the Simulated Test is just a reference for us and we don't need to actually test it with TH?
Steps to reproduce the behavior
No response
Expected behavior
No response
Log files
No response
PICS file
No response
Screenshots

Environment
TH Fall2023
Additional Information
No response

Hi @Yinxq,
It's possible to run the simulated tests, so I'll provide you here a step by step for TC-OO-3.2 to clarify an execution in practice.
So, first thing is to start two ubuntu terminals:

In the Terminal1 you may start a app of your choice, like the chip-all-clusters-app for example
In the Terminal2 we will issue DUT commands using the chip-tool, available in the ~/apps/chip-tool

So, in the Terminal2 for the TC-OO-3.2, we'll have the steps:

./chip-tool pairing code 1 MT:-24J0AFN00KA0648G00
./chip-tool onoff off 1 1
./chip-tool onoff on 1 1
./chip-tool onoff toggle 1 1
./chip-tool onoff off-with-effect 1 0 1 1
./chip-tool onoff on-with-recall-global-scene 1 1
./chip-tool onoff on-with-timed-off 0 120 5 1 1
./chip-tool pairing unpair 1
Just a reminder that every step will need to be manually verified if it was a success or not.

Let me know if this helps.

There has been no answer in a while, so closing the issue. If the problem persists, please feel free to reopen it or create a new one


Share classes between the core and tests

trait FileUtils is used by project bindgen but it's also useful in project tests.
At the moment, I've simply copied/pasted this trait next to the place it's required in project tests.
@jonas : Could you please advise how we could share code in this situation.
Do we need a CrossProject or this thing would be overkill?
i wouldn't like to spend too much time/effort with this sort of refactoring.
A very pragmatic solution would suffice.

I don't see any FileUtils in the project. If we stay with the high-level way of testing in BindgenSpec it is probably OK to duplicate a few things.

I took some time to review a few things and push.
Please have a look at: https://github.com/frgomes/scala-bindgen/tree/issue_13-processing_multiple_files
By the way, I would like to share the responsibility of code review with you.
I should not merge without your review first.

@jonas https://github.com/frgomes/scala-bindgen/pull/28

@jonas :: Please have a look at test002.h, which is the inner workings on A including B.


[ZEPPELIN-5156]. Support flink 1.12

What is this PR for?
Flink 1.12 is almost the same as flink 1.11 in api perpsctive, the only change is ExecutionConfig#disableSysoutLogging is removed. So in this PR I fix this issue by didn't call this method if flink version is newer or equal to 1.12.
What type of PR is it?
[ Improvement]
Todos

[ ] - Task

What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-5156

How should this be tested?

Manually tested on flink 1.12

Screenshots (if appropriate)
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

CI pass, will merge if no more comment

@zjffdu Please remove the file zeppelin-interpreter-integration/hs_err_pid48011.log out of your PR.


Adds a config file to map the dataset columns

Adds the file src/table_config.json to map the files basename to the
specific columns in them. I'm going to take a better look on the other datasets to check if there are any other map/columns that could be placed in the config file.

merged.


Exception: This experimental setting for (Memory, TransE) has not been configured

Hi all,
When I am training with custom dataset and custon hyperparameter (.yaml) file I am getting following error

The command I used is "python3 train.py -mn TransE -ds Memory -dsp Memory -hpf custom_hp.yaml -exp True"
if I omit the 'exp' parameter model trained with the default parameter.
I am attaching the screenshot for the reference

It would be great if someone can help me. Thanks in advance

Hey,
I had got the same error which in my case was due to a mismatch in the name of the dataset in the custom (.yaml) file and the one I passed in for the -ds flag in command line. Changing that solved it in my case.


proper sorting

love the work you're doing so far, being able to make custom channels is a game changer.
sorting is a little funky, on the collections page, it sorts it alphabetically, but it does it capitalized, a - z then lowercase a - z.
while adding content to a collection, the drop down menu sorts the available collections by their creation date instead alphabetically.
on the schedules page, it doesn't properly sort numerically, it does 1, 10, 2, 20, etc.
out of scope, but on the schedules page and playouts page, could the add new * button be moved to the top, that way you don't have to scroll down to the bottom to create a new instance.
thanks again for all the hard work!

Thanks for the feedback. In addition to pointing out unexpected behavior, it would help if you could define what expected behavior would be (or what you consider "proper sorting").
For the collections page, I think the implication is that you would want case-insensitive sorting for collection names?
For the collection drop downs, it sounds like you want alphabetical? Also case-insensitive?
For the schedules page, are you referring to the schedule name (a string)?

Yeah. So for collections, they ought to be case insensitive.

When adding to a collection from a library, sort them alphabetically as well.

Here's the schedules page, i give their name the channel number at the beginning i associate it with so that they're roughly in the same order.


Added RandomPrimaryKey Behavior

Behavior for automatic random digit primary key creation for your model instead of AI.
https://github.com/51seven/cakephp-random-primary-key-behavior

Tests missing.
Whats the use case, what happens if there is a (quite likely) collision, existing key etc?

Most common use case i can think of is not showing sequential / guessable IDs to user. For that one can use uuids primary key or just use primary key obfuscation (we already have plugins listed for that).
So I don't see a common enough use case for this behavior/plugin to be included in awesome list.

thanks for this advice. Did not notice that there is already a plugin for that :)


Typo fix in guide/english/computer-hardware/cpu/index.md

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

@iamrajiv Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


"Comment and close" replaces first issue comment with last comment

Gitea version (or commit ref): d155d0e
Git version: 2.1.4
Operating system: Debian 8
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[x] Yes (provide example URL): https://try.gitea.io/mxmehl/test1/issues/1
[ ] No
[ ] Not relevant

Log gist:

Description
This is a very severe bug because is modifies issues and potentially important information!
In an open issue, when clicking "comment and close", the text of the closing comment replaces the text of the first comment in this issue (fortunately not those in between).
Examples: https://try.gitea.io/mxmehl/test1/issues/1 or https://git.fsfe.org/pmpc/website/issues/89

Not present in 1.2.0-rc2 only on master branch

The bug also happens when reopening an issue with a comment.
Does anyone have an idea how this could have been caused in the latest commits?

Workaround: Comment on an issue, and close it in a second step. Then the first message isn't overwritten. But who does it this way if there's a shortcut?


Handle IPFS Stalling W/ Timeouts & Fallback Providers

When an IPFS node cannot access a requested document, it will hang. In order to work around this, I've added options for:

Registering fallback providers to try if an operation fails to complete on the default provider.
Specifying a timeout to be used for a given operation.
Specifying a provider override to be used for a given operation.
Added support for the resolve API, allowing you to quickly check if a file exists.

closes https://github.com/Web3-API/monorepo/issues/290

@dOrgJelli just some linter errors to fix


Fix file watching soak test

We now don't invalidate the whole VFS if we
receive an overflow for some location. So
the number of retained files won't be 0.
Moreover, sometimes changing the files takes
more than 2 minutes which may cause the daemon
to time out.
Fixes https://github.com/gradle/gradle-private/issues/3093.

@lptr PTAL, I removed the increased idle timeout.

@lptr PTAL!


Frontend PRs fail CI

Description

"Preview full-stack docs" step fail: during loading of Docker images it can't find the ingestion_server artifact.
Reproduction
See this run: https://github.com/WordPress/openverse/actions/runs/4434321396/jobs/7780271518

Preview of docs should not need the images at all!


MEDIA.BUFFER_READ_OUT_OF_BOUNDS in cea_decoder parsing captions from h.265 content

Have you read the FAQ and checked for duplicate open issues?
It is possibly related to https://github.com/google/shaka-player/issues/3634, but I am not sure.  I can send some sample content which the others cannot provide.
Not sure if the problem is with the content, or shaka.   A couple of interesting things to note though
1 - There are no actual captions in the content until about 1 minute in, but the cea_parser error occurs at about 20 seconds into the content
2 - Exoplayer does not have any issues with the content.
What link can we use to reproduce this?
I will send the content to your private address
What version of Shaka Player are you using?
v3.2.0-uncompiled
What browser and OS are you using?
Windows 10 - Edge - With HEVC decoder plugin
What did you do?
Playback content
What did you expect to happen?
Uninterrupted playback
What actually happened?

Attempting to buffer the 6th segment, this error occurs
Error: Shaka Error MEDIA.BUFFER_READ_OUT_OF_BOUNDS ()
    at new shaka.util.Error (https://shaka-player-demo.appspot.com/lib/util/error.js:94:17)
    at shaka.util.DataViewReader.outOfBounds_ (https://shaka-player-demo.appspot.com/lib/util/data_view_reader.js:267:12)
    at shaka.util.DataViewReader.readUint8 (https://shaka-player-demo.appspot.com/lib/util/data_view_reader.js:83:18)
    at shaka.cea.CeaDecoder.extract (https://shaka-player-demo.appspot.com/lib/cea/cea_decoder.js:120:16)
    at shaka.media.ClosedCaptionParser.parseFrom (https://shaka-player-demo.appspot.com/lib/media/closed_caption_parser.js:89:24)
    at shaka.media.MediaSourceEngine.appendBuffer (https://shaka-player-demo.appspot.com/lib/media/media_source_engine.js:547:52)
    at shaka.media.StreamingEngine.append_ (https://shaka-player-demo.appspot.com/lib/media/streaming_engine.js:1571:51)
    at async shaka.media.StreamingEngine.fetchAndAppend_ (https://shaka-player-demo.appspot.com/lib/media/streaming_engine.js:1261:9)

Im also facing the same issue. Here is the error log:
Error: Shaka Error MEDIA.BUFFER_READ_OUT_OF_BOUNDS ()
    at new shaka.util.Error (http://localhost/shaka-player/lib/util/error.js:94:17)
    at shaka.util.DataViewReader.outOfBounds_ (http://localhost/shaka-player/lib/util/data_view_reader.js:267:12)
    at shaka.util.DataViewReader.skip (http://localhost/shaka-player/lib/util/data_view_reader.js:204:18)
    at shaka.cea.Mp4CeaParser.parseMdat_ (http://localhost/shaka-player/lib/cea/mp4_cea_parser.js:239:16)
    at http://localhost/shaka-player/lib/cea/mp4_cea_parser.js:186:16
    at shaka.util.Mp4Parser.parseNext (http://localhost/shaka-player/lib/util/mp4_parser.js:187:7)
    at shaka.util.Mp4Parser.parse (http://localhost/shaka-player/lib/util/mp4_parser.js:93:12)
    at shaka.cea.Mp4CeaParser.parse (http://localhost/shaka-player/lib/cea/mp4_cea_parser.js:190:10)
    at shaka.media.ClosedCaptionParser.parseFrom (http://localhost/shaka-player/lib/media/closed_caption_parser.js:83:44)
    at shaka.media.MediaSourceEngine.appendBuffer (http://localhost/shaka-player/lib/media/media_source_engine.js:547:52)

I checked the previous versions and it seems the last version with which it worked is 3.0.13. From version 3.1.0 and later "BUFFER_READ_OUT_OF_BOUNDS" occurs. The problem occurs on both firefox and chrome. Also playback works fine with latest dash.js.

Could it be a duplicate of https://github.com/google/shaka-player/issues/3608?
Have you tried the master branch to see if it happens?
Note: there are two commits possibly related to this: https://github.com/google/shaka-player/commit/97ba4dfd7bdcbf1b612af3679ee85273a1967715 and https://github.com/google/shaka-player/commit/6a775e29a4c96588822288188d8e34ea4c992713

I just checked-out master, recompiled and can confirm it is happening with latest master.

Yes I just ran it against the nightly build from your appspot demo.  I assume that is built from latest master.  It is still happening there.


Adding server pre_shared_key extension

Resolved issues:
resolves #2392
Description of changes:
The server must send a pre_shared key extension indicating which PSK it accepted by sending the chosen psk wire index value. The client must receive this extension and set its own chosen PSK accordingly.
The extension itself is pretty straightforward:

is_response: true. Should only be sent/received if the client version was.
should_send: true if a chosen PSK is set on the connection.
if_missing: Not an error. For now, we can always fall back to key_share.
send: Send the index of the chosen PSK that is stored on the connection.
recv: Set the chosen PSK pointer to the PSK at the index received. Wipe the other PSKs.

Other misc checks the client has to do on recv:

“Clients MUST verify that the server's selected_identity is within the range supplied by the client, that the server selected a cipher suite indicating a Hash associated with the PSK, and that a server "key_share" extension is present if required by the ClientHello "psk_key_exchange_modes" extension [note: we should leave the mode requirement until we implement modes]. If these values are not consistent, the client MUST abort the handshake with an "illegal_parameter" alert."

Describe s2n’s current behavior and how your code changes that behavior. If there are no issues this pr is resolving, explain why this change is necessary.
Call-outs:
Client verification that the server selected a cipher suite indicating a Hash is associated with the PSK is done during s2n_server_hello_recv in the s2n_server_hello_parse logic as conn->secure.cipher_suite is set only after calling the server psk extension s2n_server_psk_recv, and conn->secure.cipher_suite is NULL within s2n_server_psk_recv logic flow.
Testing:
How is this change tested (unit tests, fuzz tests, etc.)? Are there any testing steps to be verified by the reviewer? Unit and Functional Testing
Is this a refactor change? If so, how have you proved that the intended behavior hasn't changed? No, but changes struct s2n_psk_parameters.chosen_psk_wire_index from uint8_t to uint16_t to match the RFC, the changes are tested in unit tests.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

CI is failing on false positive for Codecov/patch/fuzz target:  https://github.com/awslabs/s2n/pull/2494/checks?check_run_id=1596936170


api example not working

Hi, I'm attempting to run the api inference example.  this is my command( run from the apiexample directory ):
taskname=Baron
  tgthighres=a5
  mkdir -p ./demo/${taskname}/${tgthighres}
    taskname=Baron
  tgthighres=a5
  mkdir -p ./demo/${taskname}/${tgthighres}
  python ./client.py --input_type singlecell --output_type cell --pool_type all --pre_normalized F --version 0.2 --tgthighres $tgthighres --data_path ./data/baron_human_samp_19264_fromsaver_demo.csv --save_path ./demo/${taskname}/${tgthighres}/ --token ...

I get the following error:
code:404 text:<!DOCTYPE html>

<meta charset="utf-8">
<title>Error</title>

Cannot POST /v2/models/xtrimogene/infer

 reason:Not Found

is the api still active?

Hi,
Thank you for your feedback. Can you try it again? I think the engineer has fixed this.
Sorry for the inconvenience.

The example above works for me now. I'm now trying to run it with my own data, some bulk RNA seq. I followed the preprocessing instructions, and used the following command:
taskname=chunk1
tgthighres=f1
mkdir -p results/${taskname}/${tgthighres}/
python client.py --input_type bulk \
    --output_type cell --pool_type all \
    --pre_normalized F \
    --version 0.1 \
    --tgthighres $tgthighres \
    --data_path chunk1.csv \
    --save_path results/${taskname}/${tgthighres}/ \
    --token ...

however, I'm now getting the following error:
code:400 text:{"error":"Failed to process the request(s) for model instance 'xtrimogene_0', message: TypeError: __init__(): incompatible constructor arguments. The following argument types are supported:\n    1. c_python_backend_utils.InferenceResponse(output_tensors: List[c_python_backend_utils.Tensor], error: c_python_backend_utils.TritonError = None)\n\nInvoked with: kwargs: error=<c_python_backend_utils.TritonError object at 0x7f9fae6108f0>\n\nAt:\n  /work/xtrimogene/service/xtrimogene/1/model.py(151): execute\n"} reason:Bad Request

Hi, could you check the format, especially the row or col name? The customized data should have the same format as the example data.

I figure out the issue, I wasn't saving the index of the counts data frame. I was able to successfully generate embedding.  One last thing, just to make sure I'm using the tool correctly - My data is bulk RNA seq counts that are variance stabilized but not log transformed. When generating the embeddings, I'm using the settings --pre_normalized F and --tgthighres f1 , is this correct?

Hi if your bulk data are not log-transformed, you can use --pre normalized T according to the API doc. But this is not a restricted choice. You can try there settings for the best performance.


Added  @typescript-eslint/explicit-module-boundary-types rule

Closes: RHOAIENG-506
Description
Added @typescript-eslint/explicit-module-boundary-types as an error frontend/backend

How Has This Been Tested?
npm run test

Test Impact

Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

/lgtm
/approve


Text input with left & right Icon

Is your feature request related to a problem? Please describe.
As I worked so far, Galio just supported one icon for a text input, but in real life in some moment I need both left & right Icon for a text input.
Describe the solution you'd like
Support both left & right icon for a text input.

If nobody has started work on this, I would like to contribute in adding this small feature. May I?

no, you can add your contribute. Thank you 🙏

Hi @marqbeniamin,
I did fork the project, but unable to run the same.
Also I could not find any documentation to run the project.
It'll be really helpful if you could guide me on the same, please.


Refresh Opioid Ingredient Data

Source opioid drug data has been refreshed as of 2021-01-29, need to refresh the relevant ingredient data.

Also document and potentially automate (more of) the process


update table docs for error classification

View formatted markdown at: https://github.com/Jigsaw-Code/censoredplanet-analysis/blob/doc/docs/tables.md#error-classification.
Would appreciate your thoughts on more ways to make these docs accessible to people who have less background in network interference or are learning.

I think if I were looking at this for the first time a quick description of the type of data ("this test tries to connect using tls, so it records blah blah blah and also any network (e.g. TCP) errors") as well as links to reference documentation ("these are golang network error messages") would be helpful.

I think it will be helpful to have a section explaining how we model each probe. For example:
Discard

Establish TCP connection
Write HTTP request
Read response
Validate response content is empty

Echo

Establish TCP connection
Write HTTP request
Read response
Validate response content equals the request sent

HTTP

Establish TCP connection
Write HTTP request
Read HTTP response
Parse HTTP response
Validate response content

HTTPS

Establish TCP connection
Establish TLS connection
Write HTTP request
Read HTTP response
Parse HTTP response
Validate response content

Then you can easily tie the error stages to the probe model. That would also be a nice summary and explanation of the probes.

added probe diagrams as images


Add validation checks for volumeMount/artifact path collision and activeDeadlineSeconds (#620)

Partially addresses issue #620 by adding:

path collision between input artifacts and volumeMounts
activeDeadlineSeconds > 0

Here is the new error message:
/tmp/asdf.yaml: template 'pass' inputs.artifacts[0].path '/src' already mounted in container.volumeMounts.workdir

stemming from this bad yaml:
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: path-collision-
spec:
  volumeClaimTemplates:
  - metadata:
      name: workdir
    spec:
      accessModes: [ "ReadWriteOnce" ]
      resources:
        requests:
          storage: 1Gi
  entrypoint: pass
  templates:
  - name: pass
    inputs:
      artifacts:
      - name: argo-source
        path: /src
        git:
          repo: https://github.com/argoproj/argo.git
    container:
      image: alpine:latest
      command: [sh, -c]
      args: ["exit 0"]
      volumeMounts:
      - name: workdir
        mountPath: /src


Skype api for business to send message to owner

I'm a developer.
Recently, one of my clients requested that he should be notified on skype message personally and also in one of his skype groups on certain actions in the application I'm developing for him.
I'm developing the application PHP. Is there any API for that?
Message only needs to send to him and one of his skype group. Is it possible?
Is there any payment for that? my client might be willing for that as well.
Can you please confirm and respond it as quickly and possible.
Thank You,

Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.

Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


Add autogen-extension topic

Will help the client show up in community extensions.

Thanks for the suggestion! Just added and I'm able to see it in community extensions now


SPARK-25999: make-distribution.sh failure with --r and -Phadoop-provided

Signed-off-by: Shanyu Zhao<EMAIL_ADDRESS>What changes were proposed in this pull request?
It is not possible to build a distribution that doesn't contain hadoop dependencies but include SparkR. This is because R/check_cran.sh builds R document which depends on hadoop dependencies in assembly/target/scala-xxx/jars folder.
To reproduce:
MAVEN_BUILD_OPTS="-Dmaven.javadoc.skip=true -Pyarn -Phadoop-2.7 -Phive -Psparkr -Phadoop-provided"
./dev/make-distribution.sh --tgz --r $MAVEN_BUILD_OPTS
Error:
creating vignettes ... ERROR
...
Error: A JNI error has occurred, please check your installation and try again
Exception in thread "main" java.lang.NoClassDefFoundError: org/slf4j/Logger
The fix is to create an optional project that brings all dependencies to R/rjarsdep/target folder, and copy the missing jars to assembly/target folder before building R.
How was this patch tested?
Tested on my dev box, the build works fine.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

thx, but I'm not sure about this approach. this step will now cause hadoop jar to be packaged into the release tarball of hadoop-provided, which is undoing the point of hadoop-provided.

btw, please see the page https://spark.apache.org/contributing.html and particularly "Pull Request" on the format.

It is not possible to build a distribution that doesn't contain hadoop dependencies but include SparkR

I wouldn't say that. It seems like it's possible, it just can't be published to CRAN because it fails tests without further configuration.
Which is kinda the point of hadoop-provided (it requires the user to configure Spark to point at existing Hadoop libraries).

I'm sorry this PR completely slipped out of my mind. Sorry for the late reply.
I copied hadoop dependencies to $SPARK_HOME/assembly/target/scala-${SCALA_VERSION}/jars, that's where these jars are read during building R packages. This is not where we package the tar ball. The folder where we create the dist tar ball is defined at the top of this file:
DISTDIR="$SPARK_HOME/dist"
And we've done copying from the assembly folder to the dist folder earlier:
cp "$SPARK_HOME"/assembly/target/scala*/jars/* "$DISTDIR/jars/"
If we build with hadoop, then hadoop jars will end up in the assembly folder first, then copied to dist folder. If we don't choose to build with hadoop, then before building R packages, we copy the dependencies to assembly folder. These jars won't get in the dist tar ball. I've tested this.

Is there any way to reconsider this patch? thanks!

See comments above. I think this breaks what hadoop-provided is for

@srowen This won't break hadoop-provided because it does not package hadoop jars to the tar ball. It only download hadoop jars so that we can build SparkR successfully.
There should be a way to build Spark with R support but leave all hadoop jars out. And this PR enables that scenario.


forever blocked on a profile screen

if I enter a wrong email address and I ask for a magic link for account creation, I can never go back and change my email adress (unless I clean my cache).

Still relavent @renardpal ?


Error: unsupported_response_type

I get the following logs when running your code:
[2020-06-09T07:04:53.043Z]  INFO: AzureAD: OIDC Passport Strategy/10772 on WorkPC: Error received in the response was:  unsupported_response_type
[2020-06-09T07:04:53.044Z]  INFO: AzureAD: OIDC Passport Strategy/10772 on WorkPC: authentication failed due to: unsupported_response_type

Full log:
[2020-06-09T07:10:15.629Z]  WARN: AzureAD: OIDC Passport Strategy/18052 on WorkPC: Using http for redirectUrl is not recommended, please consider using https
[2020-06-09T07:10:19.171Z]  INFO: AzureAD: Metadata Parser/18052 on WorkPC: Parsing JSON retreived from the endpoint
[2020-06-09T07:10:19.171Z]  INFO: AzureAD: Metadata Parser/18052 on WorkPC: Request to update the Open ID Connect Metadata
[2020-06-09T07:10:19.370Z]  INFO: AzureAD: OIDC Passport Strategy/18052 on WorkPC: entering Strategy.prototype._flowInitializationHandler
[2020-06-09T07:10:19.370Z]  INFO: AzureAD: OIDC Passport Strategy/18052 on WorkPC: We are sending the response_type:  id_token
[2020-06-09T07:10:19.370Z]  INFO: AzureAD: OIDC Passport Strategy/18052 on WorkPC: We are sending the response_mode:  form_post
::1 - - [09/Jun/2020:07:10:19 +0000] "GET /login HTTP/1.1" 302 0 "http://localhost:3000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.61 Safari/537.36"
[2020-06-09T07:10:20.015Z]  INFO: AzureAD: OIDC Passport Strategy/18052 on WorkPC: Error received in the response was:  unsupported_response_type
[2020-06-09T07:10:20.015Z]  INFO: AzureAD: OIDC Passport Strategy/18052 on WorkPC: authentication failed due to: unsupported_response_type
::1 - - [09/Jun/2020:07:10:20 +0000] "POST /auth/openid/return HTTP/1.1" 302 46 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.61 Safari/537.36"
::1 - - [09/Jun/2020:07:10:20 +0000] "GET / HTTP/1.1" 304 - "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.61 Safari/537.36"

I can't for the life of me find what is going wrong and where.

Ok, I found the fix for it, the issue lay on my end, there was something wrong with the clientID

I ran into this issue as well. My problem was caused by not checking the ID Token option in the advanced settings > implicit grant section on the app registration.


DRF Serializer class to pydantic model conversion

For inferring schemas from rest_framework Serializer classes

Feature added in 1.1.0


Listchar nbsp should also apply to other unicode spaces (e.g. Em Space U+2003)

There are a number of invisible unicode characters:
Em Space: U+2003
Tag Space: U+E0020
Thin Space: U+2009
En Space: U+2002
Hair Space: U+200A
Zero Width No-Break Space: U+FEFF
Figure Space: U+2007
Punctuation Space: U+2008
Six-Per-Em Space: U+2006
Four-Per-Em Space: U+2005
Three-Per-Em Space: U+2004
Ideographic Space: U+3000
Medium Mathematical Space: U+205F

These characters are invisible, but not necessarily considered whitespace, which can lead to numerous issues.
Vim already has a mechanism to handle this (listchars), but currently there is no option to highlight these characters.
Expected Behaviour
The character set for nbsp should also be displayed for these other invisible characters.
Alternatives
I can't think of any better alternatives.

I don't think those spaces are actually non-breaking spaces (nbsp) though? Seems like we wouldn't want to hijack the meaning of that word, and the issue here is there are a lot of different kinds of spaces in Unicode, but I'm not sure if we want them to all be replaced with the same listchars character. This is particularly important because sometimes the reason I would use listchars to begin with is to see if someone injected a wrong space character in my document to begin with. If all kinds of spaces show up as the same listchar character I think that decreases its utility a little bit.

Yes, I think this was discussed before and the general agreement was to use nbsp only for a realy non-breaking space and none of the other UTF-8 special whitespace characters.

There are a number of invisible unicode characters:
Em Space: U+2003
Tag Space: U+E0020
Thin Space: U+2009
En Space: U+2002
Hair Space: U+200A
Zero Width No-Break Space: U+FEFF
Figure Space: U+2007
Punctuation Space: U+2008
Six-Per-Em Space: U+2006
Four-Per-Em Space: U+2005
Three-Per-Em Space: U+2004
Ideographic Space: U+3000
Medium Mathematical Space: U+205F

These characters are invisible, but not necessarily considered
whitespace, which can lead to numerous issues.

Some of these actually show, but are not a full cell width.

Vim already has a mechanism to handle this (listchars), but currently
there is no option to highlight these characters.
Expected Behaviour
The character set for nbsp should also be displayed for these other
invisible characters.

The "nbsp" is used quite often in HTML.  Most of the characters you list
are unusual.  I think they deserve a different entry.  If the user
doesn't care the same replacement character can be used, but if the user
does want to see the difference we do need another entry.
Perhaps we can group these into a small number of categories?
--
hundred-and-one symptoms of being an internet addict:
156. You forget your friend's name but not her e-mail address.
/// Bram Moolenaar -- @.*** -- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


Feat: customize reportDir

Hey guy, thanks for the great work of mochawesome-report-generator.
I noticed that in getFilename function, it returns with path.resolve(process.cwd(), reportDir, filename). I've made this PR to add a rootDir option which equals process.cwd() by default.
Thanks again and wait for your reply.

Not sure if this is really needed. You can specify a path relative to process.cwd() in the reportDir option. For example:
If your current directory is /myproject and you pass ../myreportdir as the reportDir option, your reports will be saved in a new directory at the same level as your project like below:
.
├── myproject
└── myreportdir
    ├── assets
    ├── mochawesome.json
    └── mochawesome.html

Yes, to specify a path relative can resolve the problem, but it will be not super neat in my case, like:
('../../../A/B/C', reportDir)

I've made the same PR for  mochawesome-merge
Issue 10
Anyway, it is not a block, (if it is) just a little improvement by my side. You can close this if it is necessary from most use case


docs(add observables to TOH http)

@wardbell @johnpapa
This PR contains my addition of Observables to the TOH Http chapter

@wardbell
Removing the WIP label. I have rebased with master and tested with the new version of in-memory-web-api.
The chapter is ready for review.

I resolved merge conflicts from other PRs. This one is ready to go

@chalin Good call. I agree

Changed from chapter to section based on feedback from @chalin

Rebased to latest master

Rebased to latest master

@wardbell, @Foxandxss : I think that it would be nice if this were merged before the next wave(s) of changes hit the ToH. It is a well contained addition that would nicely round up the http toh chapter. (Btw, we should probably mark parts of the server-communication chapter as outdated, or just trim them out, because this ToH chapter will have outpaced it!)

Will review soon!

I made a bunch of clarifying edits in a separate commit.
Ready to squash and merge


Update vae_example.ipynb

I guess, D has forgotten in the equation.

I guess, D has forgotten in the equation.

No, this is not correct because log_var is of size mini_batch x D. When we calculate log_p , we treat all variables as tensors. Adding D as you suggest would result in scaling log_var which would be incorrect.
However, I spotted a different mistake. The constant shouldn't have D. I am going to correct it.


use componentDidMount instead of componentWillMount

Coverage remained the same at 100.0% when pulling 25be2d91d90670a6543830e9e01af4b0324585ba on use-componentdidmount into 2afffe3f172fe94acb9d110aa9726e91e6190ef3 on master.


Fix errors in README

I fixed some errors in the README file. Thank you for the great icons!

I fixed some errors in the README file. Thank you for the great icons!

谢谢你对图标的赞赏和修正


refactor(FormGroup): use inject instead of cloning slots

This is a proposal to refactor the FormGroup component. It replaces vProps / slot manipulations by injecting relevant attributes directly into the children components.
This allows the use of v-slots (fixes #484) and provides an easy way to make custom input components compatible with the Form / FormGroup components using useFormGroup.
I also replaced how labels and inputs are bound by nesting them directly, to avoid conflicts with duplicate ids c.f.

Alternatively, you can nest the input directly inside the label, in which case the for and id attributes are not needed because the association is implicit:
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/label#attributes

Just made this commit https://github.com/nuxtlabs/ui/commit/83c42cd1ccf81f2aaf64a7fc20bbe3a9cf25b8d5 that fixes the size on the FormGroup.
Do you need me to solve the conflicts?

I'll do it if you're good with the changes, I need adapt the other input components too


Create HttpOperations class with static methods

Create an HttpOperations class with static methods for all HTTP methods. Design this for the Mule connector but extract into JAR for API utilities and Java (CI Wise). Add to Maven Central.

Closing this as not needed.


camara

Not a scratch feature, but very important to support large scene.

https://github.com/goplus/spx/releases/tag/v1.0.0-beta5


View and/or Regenerate Wallet Words

Is it possible to regenerate the wallet words for a running instance of Multibit-hd?
Situations like where the paper copy is missing and/or compromised come to mind.
Or should the coins be sent to another wallet and Multibit-hd be reinstalled?

It is not possible to regenerate the wallet words no. They are only shown in the wallet creation wizard and  no record of them is kept. This is for security reasons.
IF you have lost your wallet words then the best thing to do is:

Create a new wallet (press the create button on the password entry screen)
Generate a receiving address in the NEW wallet.
Switch to the old wallet and do a 'Manage wallet | Empty wallet' and transfer all your bitcoin to your new wallet.

That way if anything happens to the new wallet you will have your wallet words to recover your bitcoins.

Makes a lot of sense. Yes I was planning on doing just that, but thought I'd check first.
Thanks.
Maybe those details could be added to the help files?

Glad you got that sorted.
This issue is probably all the documentation users need ! (it's quite a specific query rather than general help).
C

Doubt many users will venture in here - I'll flesh out the restore article to cover this scenario.

Added as website issue #252.


Add validation rule to SignDeclarationRequest

Method: Sign declaration request
After encoding b64:

Check $.person.patient_signed

[ ] If false generate error (422, "Patient must sign declaration form")

Check $.seed

[ ] if not exist generate error (422, "Attribute Seed is required")

The first check is done. The second one is not needed anymore

When I try to sign declaration request without sign content with electronic sign I have 500 error:
request
curl -X PATCH \
  http://dev.ehealth.world/api/declaration_requests/760bc6df-308f-43c7-a1b1-9c82e6577676/actions/sign \
  -H 'authorization: Bearer OVRNWmNBMmY3OXJvRjBiZnE4YzcyUT09' \
  -H 'cache-control: no-cache' \
  -H 'content-type: application/json' \
  -H 'postman-token: 3e44079c-42ff-0c47-d5bf-05e4bec4c975' \
  -d '{
  "signed_declaration_request":

response
{
    "meta": {
        "url": "http://dev.ehealth.world/api/declaration_requests/760bc6df-308f-43c7-a1b1-9c82e6577676/actions/sign",
        "type": "object",
        "request_id": "40omg6oite9qpgacagkmd3gvcse1ha1g",
        "code": 500
    },
    "error": {
        "type": "internal_error"
    }
}

Fixed

Ok


Pin display area

xref #1118

@rafaelgm looked into the cause of #1118 and narrowed it down to @nteract/display-area. Pinning the version at 3.0.2 will be  a quick fix for now.

Thanks!


Add a page for Weddings, meet-ups at ITC hotel banquets.

Claim

I have made PR to my assigned issue . Now can you assign this to me ?

I have made PR to my assigned issue . Now can you assign this to me ?

yes go ahead, note: create new html page with bootstrap or react, any one of ur choice

I have made PR to my assigned issue . Now can you assign this to me ?

are you working?

can i take this issue?

can i take this issue?

go ahead use bootstrap, for content refer to ITC hotels website & SITEMAP is below:


pip doesn't work.

[~/Documents]$ pip install pyping
stash: <type 'exceptions.TypeError'>: call() takes exactly 2 arguments (1 given)

Hi @i0nsec,
Have you checked this thread on the forum? It appears to be the same issue.

Perfect, it worked. Thanks.


[Vue warn]: Do not use built-in or reserved HTML elements as component id: Switch

The Issue
I get the following warning whilst running the library in my new project, trying to register the components globally (as shown in the readme:

[Vue warn]: Do not use built-in or reserved HTML elements as component id: Switch

<switch> element documentation page: https://developer.mozilla.org/en-US/docs/Web/SVG/Element/switch
From the Vue documentation style guide:

Component names should always be multi-word, except for root App components. This prevents conflicts with existing and future HTML elements, since all HTML elements are a single word.

Suggested Change
In order to stay compliant with the style guide, and prevent this from happening in the future, I propose we add a prefix to each of custom elements, and even maybe make the prefix customizable so that, if need be (for backwards compatibility) the prefix can be turned off:
Ex: ui-switch

Getting the same warning
I think prefixing all elements is a great solution.

How would I get past this error when using the LibraryModule ?

For now, you can remove import of switch component to LibraryModule in coreui-vue/src/index.js and then rebuild package (you need github config files to do this) or remove switch component from LibraryModule in build file.
This component name will be changed in the next version.

Would you be able to give me a couple of pointers to do this - I've made the changes to the module and tried rebuilding but i still get the old version at the front end

You can check if the build is done right by checking dist files (there should be no Switch component in LibraryModule).

@woothu  This issue has not been solved yet, is there any reason to close this issue?

I gave the instruction on how to solve this issue, for now, we cannot just introduce fix because it is a breaking change and we will introduce it in version 3.

Thx, I'm looking forward to a quick release.


Allow loaders to emit wasm

Feature request

What is the expected behavior?
Loader can emit wasm
What is motivation or use case for adding/changing the behavior?
WebAssembly is just a compilation target and can be abstracted away from the user.
They should be able to write C, rust, etc and interact with JavaScript. Some loaders already offer a similar experience but Webpack restrict their usage.
How should this be implemented in your opinion?
A loader can already ask for an ArrayBuffer but still need to emit JavaScript. I would suggest to allow an ArrayBuffer in emit since wasm has a magic header and can reliably be detected.
In the future we could even concat all wasm modules together or treeshake them. Webpack will basically act as a linker.
Are you willing to work on this yourself?
yes

Loaders can return wasm. You just have to add type: "webassembly/experimental" to the rule.
i. e.
module.rules: [{
  test: /\.c$/,
  loader: "compile-c-to-wasm-loader",
  type: "webassembly/experimental"
}]

With webpack 4, do you even need any wasm loader? In this official-example, they don't seem to be using anything.


Initialization issue

As you can see in the picture, after the initial load by calling "tagsItems" of the already existing tags the cursor start at the very left instead after the last tag. Can somebody help me please?

I am having the same problem here, if I find a fix I will post it.

textext.plugin.ajax.js file
line 227 add this code
setTimeout(function () { core.invalidateBounds(); }, 1000);`


Can't select all groups

We can't select any group except for cloud only security groups. Is there no way to select groups that were synched to AAD using AAD Connect? Thanks!

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

ID: e04567e4-6efd-adfe-8367-d6bf3535607e
Version Independent ID: 21365359-28dd-7aa4-cb62-b08cc90abb2a
Content: Tag sensitive accounts with Azure ATP
Content Source: ATPDocs/sensitive-accounts.md
Service: azure-advanced-threat-protection
GitHub Login: @mlottner
Microsoft Alias: mlottner

@Maaarteen Thanks for your question.
You should be able to choose any/all groups in Active Directory, whether they are synced to Azure AD or not. If you can't chose groups configured in AD, open a support ticket to help resolve the  issue.
Appreciate your contribution to our docs community!

#please-close


feat(HeroVideoDialog): add support for dynamic gradient colors

fix #317

Implemented: Dynamic gradient color support using hex and RGB values.
Note: Tailwind CSS color classes (e.g., red-500, zinc-400, primary) are not supported for gradient backgrounds. Custom colors must be provided as hex or RGB codes.
Feedback Request: Please let me know if there are any issues or areas for improvement.

Thanks for opening this PR! 🙏
We decided to close this PR for now with the reasoning described in this issue https://github.com/magicuidesign/magicui/issues/317


Adjust setup.py to work on newer M3 Macs.

Small edit to setup.py so Python compilation on newer M3 Macs works again.

@rwxayheee @diogomart Thank the both of you for testing :-) Merging ...


An after-image can be seen when switching to a new scene

Godot version
v4.0.beta3.official [01ae26d31]
System information
Windows 10, Nvidia GTX 1080 Ti
Issue description
An after-image of the previous scene can be seen when we switch scene tabs.
I could not find an issue raised for this and while this is not a major issue considering that zooming in\out or changing the editor view in some way erodes the after-image, I thought I would raise it anyway.
Also, could not reproduce it with beta 2.
Steps to reproduce

Add a mesh instance (any mesh will do)
Switch to a new scene

Minimal reproduction project

I assume TAA is enabled? With it, I can also see ghosting when changing scenes.

Yes TAA was enabled! I was checking anti-aliasing and I guess I forgot to disable it.

Closing as duplicate of https://github.com/godotengine/godot/issues/62887 then.


(PDB-3639) Optimize existing-fact-values query

This was previously done with the text version of the value_hash column; it's
stored as bytea, so it required a conversion. Change the query to compare in the
bytea domain.

Fact storage benchmark results
Before:
medium:<PHONE_NUMBER>66 ms
After:
medium: 87886.204174 ms

what's the exact test you're using?

Test FAILed

CLA signed by all contributors.

@wkalt these timings are https://github.com/puppetlabs/puppetdb/pull/2355, using the 'medium' profile.

@puppetlabs-jenkins retest this please

Test PASSed


Feature Request: improved gitolite support: negative permissions for protected branches

Negative permissions can be very handy to restrict access to certain tags or branches.
Gitolite documentation refers to it: http://gitolite.com/gitolite/conf.html#what-does-a-rule-look-like
Similarly, option support for "option deny-rules = 1" would be a nice add as well.

It might be useful to also support the @all group for the users field in order to restrict read access to a particular repository for any additional users that get added to a project (Explicit permission as opposed to implicit permission).

+1 for this. Definitely would be helpful!

+1, this is actually what I need !

Added in commit : https://github.com/jbox-web/redmine_git_hosting/commit/8f7e433834f27dab8ca57f283796c20889d8e663
Example (from Gitolite):
repo    blibl
  RW+                            = redmine_admin
  -     master                   = redmine_developer1 redmine_developer2 redmine_developer3
  -     refs/tags/v[0-9]         = redmine_developer1 redmine_developer2
  RW+   dev/                     = redmine_developer1 redmine_developer2 redmine_developer3
  RW                             = redmine_developer1 redmine_developer2 redmine_developer3
  R                              = redmine_reporter1
  config redminegitolite.projectid = blibl
  config redminegitolite.repositoryid =
  config redminegitolite.repositorykey = bMs2qj6sPl1ttTZJH5vWJOClIQ2V8ZhwK2d7Szy1CnSDX0EYzE7SuTgAnyrVS7b
  config http.uploadpack = true
  config http.receivepack = true
  config multimailhook.enabled = false
  option mirror.master = mars
  option mirror.slaves = phobos deimos
  option mirror.redirectOK = all


Add spell checking GitHub Actions workflow

Follow up to https://github.com/rubocop/rubocop/pull/10128.
This PR adds spell checking GitHub Actions workflow.

Nice!


Fix ./waf install

Since default ./waf install only copies app into /usr/bin with broken libclang.so, we need to provide a customized build() in wscript.
Probably we can replace absolute rpath with relative one (e.g. libs/) and copies app, libclang.so and clang_resource_dir to /opt/cquery.
Current package on Arch Linux patched wscript to perform the above instructions, but I think it would be better to have these steps builtin in scripts. The directory structure is as follows:
/opt/cquery
├── clang_resource_dir
│   ├── include
│   └── README.md
├── cquery // with rpath=lib/
└── lib
    ├── BugpointPasses.so
    ├── libc++abi.so
    ├── libc++abi.so.1
    ├── libc++abi.so.1.0
    ├── libclang.so
    ├── libclang.so.4
    ├── libclang.so.4.0
    ├── libc++.so
    ├── libc++.so.1
    ├── libc++.so.1.0
    ├── libgomp.so
    ├── libiomp5.so
    ├── libLTO.so
    ├── libLTO.so.4
    ├── libLTO.so.4.0.0
    ├── libomp.so
    ├── libunwind.so
    ├── libunwind.so.1
    ├── libunwind.so.1.0
    └── LLVMHello.so

➜  cat /usr/bin/cquery
#!/usr/bin/bash
cd /opt/cquery
./cquery $@

IMHO I prefer not using ./waf install but I’m happy to merge any fixes so the Arch Linux script is simpler. Some wscript changes just got merged which change how libclang is used (https://github.com/jacobdufault/cquery/pull/64) but I don't expect they will affect this issue in particular.

On Linux, the clang executable uses DT_RUNPATH to encode the search path of shared libraries .so it depends on.
% readelf -d Dev/llvm/build/bin/clang | grep RUNPATH
 0x000000000000001d (RUNPATH)            Library runpath: [$ORIGIN/../lib]

Ideally, the build directory reflects the directory hierarchy that will be installed to somewhere (a prefix):
build
  bin
    cquery  (renamed from build/app)
  clang_resource_dir
  lib
    libclang.so.4
    libclang.so
    libclang.so.4.0

Then https://aur.archlinux.org/packages/cquery-git/ PKGBUILD can be simplified by just coping the directory contents to the system root.

Noe the file hierarchy has been changed to:
build
  release
    bin
      cquery
    clang_resource_dir    # not exist
    lib                               # not exist
      libclang.so.4             # This may cause conflicts if --prefix is /usr/local or /usr
      libclang.so
      libclang.so.4.0

It appears to be fixed in recent waf improvement.


feat: add undici fetch interceptor

Homarr

Thank you for your contribution. Please ensure that your pull request meets the following pull request:

[ ] Builds without warnings or errors (pnpm buid, autofix with pnpm format:fix)
[ ] Pull request targets dev branch
[ ] Commits follow the conventional commits guideline
[ ] No shorthand variable names are used (eg. x, y, i or any abbrevation)

All credit goes to Meier- I only adjusted the format & logging

IMO info is fine here because...

most people will not know how to change the log level
network requests are crucial information
we don't perform thousands of requests. The noise from Nextjs will be more than this one.
However, I'm open to discussions and we can easily change this in a future commit. I'll merge it for now so we can make use of it while developing.


[feat] adds scrypt passwords plus pipelines and renovatebot

Hi @MarinX,
As mentioned in #2, here is the PR :smile:

perfect. Thank you for the PR and work!


M3-197 Profile OAuth Client Section

@asauber let me know when ready to review this as I have a few comments about what I have done, and a couple questions as well


Upgrade prometheus-blackbox-exporter to v0.22.0

What Chart should be upgraded?
upstream/prometheus-blackbox-exporter chart-7.1.0
Why should this Chart be upgraded?

[ ] We need to perform a security upgrade.
[ ] We need it for a new feature: which feature (link to blocked issue).
[x] We need to keep up to prevent future issues.
[ ] Other: Write the reason here

Acceptance criteria

I checked the migration of the new Chart:

[ ] I upgraded a Chart and determined that no migration steps are needed.
[ ] I upgraded a Chart and added migration steps.

[ ] I tested the functionality provided by the new Chart (e.g., Auth flow, Grafana dashboards, etc.)

Please upgrade to the chart version v0.23.0 -  https://github.com/prometheus/blackbox_exporter/releases/tag/v0.23.0 as it has some security CVE fixes !!!


chore(deps): avoid 'path' issues with @rnx-kit tools

Please verify the following:

[x] yarn ci:test jest tests pass with new tests, if relevant
[x] README.md has been updated with your changes, if relevant

Describe your PR
This is a follow-up to the live stream with Adam from a few weeks back. I actually found the issue the same night, but forgot to submit it over the weekend.
Some of the tools are relying on a new behaviour introduced in @rnx-kit/tools-node 1.2.7. Things broke because Yarn decided that the older version should be hoisted instead.

cc @afoxman @jamonholmgren

Beautiful, thanks @tido64.
Do tests pass locally? They seem to be timing out in CI.

Beautiful, thanks @tido64.
Do tests pass locally? They seem to be timing out in CI.

This is what I see locally:

Test failure log
 FAIL  test/vanilla/ignite-new.test.ts (92.699 s)
  ● Igniting new app! 🔥
Go get a coffee or something. This is gonna take a while. › ignite new Foo

    expect(received).toContain(expected) // indexOf

    Expected substring: "Ignite CLI ignited Foo"
    Received string:    " ignite command: /usr/local/bin/node /~/bin/ignite new Foo --debug
     [object Object]·····
       · · · · · · · · · · · · · · · · · · 🔥 Ignite 🔥 · · · · · · · · · · · · · · · · · ··
        █ Creating Foo using Ignite 7.10.9
        █ Powered by Infinite Red - https://infinite.red
        █ Using ignite-cli with pnpm
        █ Bundle identifier: com.Foo
        ────────────────────────────────────────────────·
     /private/var/folders/qc/zygl93h53zb3ctbyw0f0jbzm0000gn/T/ignite-27d4ee3ff9a300fb15dec7abdb4a939b
     /private/var/folders/qc/zygl93h53zb3ctbyw0f0jbzm0000gn/T/ignite-27d4ee3ff9a300fb15dec7abdb4a939b/Foo/.gitignore
     Progress: resolved 1, reused 0, downloaded 0, added 0···
       ╭─────────────────────────────────────────────────────────────────╮
       │                                                                 │
       │                Update available! 6.32.3 → 7.1.5.                │
       │   Changelog: https://github.com/pnpm/pnpm/releases/tag/v7.1.5   │
       │                 Run pnpm add -g pnpm to update.                 │
       │                                                                 │
       │     Follow @pnpmjs for updates: https://twitter.com/pnpmjs      │
       │                                                                 │
       ╰─────────────────────────────────────────────────────────────────╯··
     Progress: resolved 33, reused 4, downloaded 17, added 0·
     Progress: resolved 54, reused 5, downloaded 34, added 0·
     Progress: resolved 67, reused 6, downloaded 52, added 0·
     Progress: resolved 145, reused 37, downloaded 92, added 0·
     Progress: resolved 221, reused 86, downloaded 119, added 0·
      WARN  deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.·
     Progress: resolved 302, reused 142, downloaded 137, added 0·
      WARN  deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.·
     Progress: resolved 374, reused 189, downloaded 172, added 0·
      WARN  deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.·
     Progress: resolved 456, reused 252, downloaded 188, added 0·
      WARN  deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.·
     Progress: resolved 612, reused 372, downloaded 222, added 0·
     Progress: resolved 732, reused 411, downloaded 283, added 0·
      WARN  deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.·
      WARN  deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.·
     Progress: resolved 798, reused 443, downloaded 334, added 0·
     Progress: resolved 847, reused 474, downloaded 348, added 0·
      WARN  deprecated<EMAIL_ADDRESS>some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added·
     Progress: resolved 1021, reused 593, downloaded 393, added 0·
      WARN  deprecated<EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.·
      WARN  deprecated<EMAIL_ADDRESS>You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1·
     Progress: resolved 1206, reused 677, downloaded 483, added 0·
      WARN  deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.·
      WARN  deprecated<EMAIL_ADDRESS>Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410·
      WARN  deprecated<EMAIL_ADDRESS>Critical bug fixed in v3.0.1, please upgrade to the latest version.·
     Progress: resolved 1312, reused 750, downloaded 529, added 0·
      WARN  deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated·
      WARN  deprecated<EMAIL_ADDRESS>Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies·
      WARN  deprecated<EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.·
     Progress: resolved 1436, reused 836, downloaded 553, added 0·
      WARN  deprecated<EMAIL_ADDRESS>Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies·
      WARN  deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.·
      WARN  deprecated<EMAIL_ADDRESS>Support has ended for 9.x series. Upgrade to @latest·
     Progress: resolved 1601, reused 931, downloaded 627, added 0·
      WARN  deprecated<EMAIL_ADDRESS>Critical bug fixed in v3.0.1, please upgrade to the latest version.·
      WARN  deprecated<EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.·
      WARN  deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated·
      WARN  deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated·
      WARN  deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-url#deprecated·
     Progress: resolved 1694, reused 1003, downloaded 646, added 0·
      WARN  deprecated<EMAIL_ADDRESS>You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1·
      WARN  deprecated<EMAIL_ADDRESS>Version no longer supported. Upgrade to @latest·
      WARN  deprecated<EMAIL_ADDRESS>support for ECMAScript is superseded by `uglify-js` as of v3.13.0·
      WARN  deprecated<EMAIL_ADDRESS>Critical bug fixed in v3.0.1, please upgrade to the latest version.·
     Progress: resolved 1783, reused 1044, downloaded 695, added 0·
     Progress: resolved 1904, reused 1114, downloaded 751, added 0·
     Packages: +1914
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++·
     Packages are hard linked from the content-addressable store to the virtual store.
      Content-addressable store is at: ~/.pnpm-store/v3
      Virtual store is at:             node_modules/.pnpm·
     Progress: resolved 1904, reused 1114, downloaded 785, added 63·
     Progress: resolved 1904, reused 1114, downloaded 789, added 297·
     Progress: resolved 1904, reused 1114, downloaded 789, added 397·
     Progress: resolved 1904, reused 1114, downloaded 789, added 619·
     Progress: resolved 1904, reused 1114, downloaded 790, added 724·
     Progress: resolved 1904, reused 1114, downloaded 790, added 961·
     Progress: resolved 1904, reused 1114, downloaded 790, added 1000·
     Progress: resolved 1904, reused 1114, downloaded 790, added 1233·
     Progress: resolved 1904, reused 1114, downloaded 790, added 1443·
     Progress: resolved 1904, reused 1114, downloaded 790, added 1562·
     Progress: resolved 1904, reused 1114, downloaded 790, added 1712·
     Progress: resolved 1904, reused 1114, downloaded 790, added 1774·
     Progress: resolved 1904, reused 1114, downloaded 790, added 1836·
     Progress: resolved 1904, reused 1114, downloaded 790, added 1914, done·
     .../node_modules/dtrace-provider install$ node-gyp rebuild || node suppress-error.js·
     .../node_modules/core-js-pure postinstall$ node -e \"try{require('./postinstall')}catch(e){}\"·
     .../node_modules/ejs postinstall$ node ./postinstall.js·
     .../node_modules/core-js postinstall$ node -e \"try{require('./postinstall')}catch(e){}\"·
     .../node_modules/fsevents install$ node install.js·
     .../node_modules/core-js-pure postinstall: Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!·
     .../node_modules/core-js-pure postinstall: The project needs your help! Please consider supporting of core-js:·
     .../node_modules/core-js-pure postinstall: > https://opencollective.com/core-js··
     .../node_modules/core-js-pure postinstall: > https://patreon.com/zloirock··
     .../node_modules/core-js-pure postinstall: > bitcoin: bc1qlea7544qtsmj2rayg0lthvza9fau63ux0fstcz··
     .../node_modules/core-js-pure postinstall: Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)·
     .../node_modules/ejs postinstall: Thank you for installing EJS: built with the Jake JavaScript build tool (https://jakejs.com/)·
     .../node_modules/core-js-pure postinstall: Done·
     .../node_modules/ejs postinstall: Done·
     .../node_modules/highlight.js postinstall$ node deprecated.js·
     .../node_modules/core-js postinstall: Done·
     .../node_modules/postinstall-prepare postinstall$ node ./run.js·
     .../node_modules/highlight.js postinstall: -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*·
     .../node_modules/highlight.js postinstall:··
     .../node_modules/highlight.js postinstall:   Verion 9 of Highlight.js has reached EOL.
      ELIFECYCLE  Command failed with exit code 1.·
    "

      36 |
      37 |     expect(result).toContain(`Using ignite-cli`)
    > 38 |     expect(result).toContain(`Ignite CLI ignited ${APP_NAME}`)
         |                    ^
      39 |
      40 |     // now let's examine the spun-up app
      41 |     const appPath = filesystem.path(tempDir, APP_NAME)

      at test/vanilla/ignite-new.test.ts:38:20
      at step (test/vanilla/ignite-new.test.ts:33:23)
      at Object.next (test/vanilla/ignite-new.test.ts:14:53)
      at fulfilled (test/vanilla/ignite-new.test.ts:5:58)

Test Suites: 1 failed, 1 passed, 2 total
Tests:       1 failed, 3 passed, 4 total
Snapshots:   0 total
Time:        93.166 s
Ran all test suites matching /.\/test\/vanilla/i.
error Command failed with exit code 1.

@tido64 I figured it out ... our CI server installs dependencies in the generated vanilla app via PNPM, to test the symlink support and ensure that we support PNPM (it uses Yarn for Expo, since we haven't totally solved Expo using PNPM yet). If you install PNPM and run pnpm install in the ./boilerplate folder, you'll see a peerDependencies issue.
So -- I don't know as much about this as you likely do. What do you suggest? Yarn and npm install peerDeps automatically, but pnpm fails. Do we do the whole shamefully-hoist thing?

So -- I don't know as much about this as you likely do. What do you suggest? Yarn and npm install peerDeps automatically, but pnpm fails. Do we do the whole shamefully-hoist thing?

I did this, and it at least fixed the patch-package error, and pnpm no longer complains about missing dependencies:
% git diff package.json
diff --git a/boilerplate/package.json b/boilerplate/package.json
index d0669cca..9616089a 100644
--- a/boilerplate/package.json
+++ b/boilerplate/package.json
@@ -61,6 +61,7 @@
     "@react-native-community/cli-platform-ios": "^6.2.0",
     "@rnx-kit/metro-config": "^1.2.31",
     "@rnx-kit/metro-resolver-symlinks": "^0.1.15",
+    "@storybook/addons": "5.3.21",
     "@storybook/react-native": "5.3.25",
     "@storybook/react-native-server": "5.3.23",
     "@types/i18n-js": "3.0.3",
@@ -85,8 +86,12 @@
     "fbjs-scripts": "3.0.0",
     "jest": "26",
     "jest-circus": "26",
+    "jest-environment-node": "26",
     "jest-expo": "^44.0.1",
     "jetifier": "1.6.6",
+    "metro-config": "0.66.2",
+    "metro-react-native-babel-preset": "0.66.2",
+    "mocha": "6",
     "patch-package": "6.2.2",
     "postinstall-prepare": "1.0.1",
     "prettier": "2.2.1",
@@ -96,9 +101,11 @@
     "react-native-clean-project": "^3.6.3",
     "react-native-web": "^0.16.3",
     "reactotron-core-client": "^2.8.10",
+    "regenerator-runtime": "^0.13.4",
     "solidarity": "2.3.1",
     "ts-jest": "26",
-    "typescript": "4.2.3"
+    "typescript": "4.2.3",
+    "webpack": "4"
   },
   "resolutions": {
     "@types/react": "^17"

But I don't know if that's enough to pass CI.

I applied that patch, running now.

Thanks @tido64 !

Hm, it failed on CI, timeout. Running again.
We really need to speed up our integration tests.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Clean up reactions settings

From #2022 cc @Huddie
There were enough changes that it would've taken a while to update. Some things that I want to call out:

Explicit "disabled" value vs hacking "Disabled" into the unknown value
Localization for disabled
Code formatting! 4-space tabs, { on sameline (TODO SwiftLint....)
Fixed up some naming
Files weren't added to .xcodeproj, build was failing

@rnystrom Yicks. My bad. Thanks for fixing it up.
Sent with GitHawk


Improve access to resolver data in module.rules and rule.use

Feature request

What is the expected behavior?
When writing loader criteria that should select specific modules of npm dependencies, it is more ergonomic to be able to specify the module to be matched as a combination of the package name (currently doable via descriptionData.name) and the relative path within the package (currently not doable). The latter path is always normalized by the resolver to use POSIX / as the directory separator, and is therefore cross-platform friendly, compared to the resourcePath value, which is the fully-resolved platform-specific disk path.
It would be beneficial to have access to the relativePath value from the resolver as a field to be used in conditions, and also for the descriptionFile object (or at least the path, name, version) and relative path within the package to be available as parameters to custom rule.use functions.
What is motivation or use case for adding/changing the behavior?
Ergonomics, portability, performance. If the description file data and relative path are passed to rule.use, then it becomes possible to perform dynamic dispatch based on package name to select the appropriate loaders.
How should this be implemented in your opinion?
Since the description file data, relative path and other resolver properties are already present in the module factory, forward them into the rule execution engine.
Are you willing to work on this yourself?
yes

Yeah, feel free to send a PR


Provide a formal official release flow

Provide a formal official release flow which pushes a new version to Docker Hub for our Docker containers and is only triggered on demand.
We can still have a new image for every master change but would move that to a new Docker image or experimental tag.
Relates to #491 & #439

This was done via #495 with a master tag


Change content of the Razor View in a module is not Effect

Hi @thiennn
First, I really thank you for the great project.
I tried to download and run this project on my local and I am having an issue with this project:

While the website is running in debug mode, I open a Razor view (.cshtml) in a module and change some text in the Razor view (.cshtml), then I refresh the browser, but the text that I was changed was not affected. I need to rebuild the project to see the text I changed

How can I resolve this issue?
I use .net core 2.2

Hi @lucy1417 Yes, you have to build the project for change in Razor file effect :)

I have the same issue with my project. :(
https://github.com/aspnet/AspNetCore/issues/14572

I found solution. Checkout my attached earlier issue. 😃


Fix event url normalization

This fixes #466.
It fixes normalization and moves it out of templatetags/links.py and into two Event model methods (tests provided, too — so this should be less erroneous).

@gvwilson fixed :-)

@gvwilson bump


Pass enableNamespacesByDefault to istio config

in this PR https://github.com/istio/istio/pull/15284, we enable get enableNamespacesByDefault from command line. pass this value in the new installer to enable test with enableNamespacesByDefault is false
Signed-off-by: clyang82<EMAIL_ADDRESS>

I turned of the test that sets this, can you turn it back on ?Line 302 of .circleci/config.yaml

@howardjohn done. I need to have the istio/istio#15284 merged firstly, then monitor if circleci can be passed or not.


Intellisense Sometimes Stop Working.

 Does this still happen if you disable extensions?

I can confirm this for powershell. Hard to reproduce this though. Sometimes intellisense just does not work and then works again.

@mjbvz Honestly I love Visual Studio Code, but the Intellisense issue is really a pain. For almost 2 weeks, I have been restarting Code more than 20 times a day.
Trust me it's really frustrating. Very simple insignificant code  like import JsClass from "./utils" where the class does not exist in that file easily break Intellisense and you are on your own until you restart Code.
I disable all extensions and its all the same. Actually right now I just removed the 64bit version to install 32bit and see if there would be a difference.
I keep asking my self why should my code break Intellisense. I don't see it happening elsewhere. I switched to Code based on the small memory footprint and enjoyable workflow. Every other feature works great but Intellisense really needs a lot of work and we all appreciate the great effort the contributors have been putting into this project.

I am also experiencing this issue. Primarily when using the path intellisense, when I get to a directory that takes awhile to load (if it ever loads) it blocks any other intellisense from working.

@jonathanhupp  I believe you could have been hitting https://github.com/Microsoft/TypeScript/issues/16329 Can you please try using the current VS Code insiders builds and let me know if you see any improvement
@sojimaxi It sounds like intellisense just completely breaks for you sometimes, is that correct? Can you also please try out the insiders builds but also set 	"typescript.tsserver.trace": "verbose" in your user settings. Then, if intellisense stops working, please open the output panel and look in the typescript section. There may be some error messages that can help us track down what is going wrong


Run examples as out of box

Hi,
I found that there is a missing information for new users to run the first example, which is for creation of parameters.yaml.
It should be done with seisflows init (but not seisflows setup with current devel), but I could not find an instruction for this step (sorry if I have just been missing it).
So I put some line to create a default parameter file automatically if it does not exist, when the setup function is called.
I added some parameters to allow seisflows check to work.
Please let me know if it would be ok, or would be better to add more parameters in the default file e.g.

path_specfem_bin
...

Because I think that it would be useful if the first examples can be run with the out-of-box state, otherwise new users resign to use the library instead of digging around the correct way to do.

Thanks for raising this @mnagaso, I swapped the names of two command line parameters init and setup to be more inline with their actual functionality in this big PR (https://github.com/adjtomo/seisflows/pull/181). I think what is needed here is just a simple update to the namespace in the example. I can have a look at this real quick and see if the fix is that simple.

Thank you very much @bch0w  !
Yes I tried to just replace the setup and init as my last commit by following your guide, then it worked like a charm!
In the later part of this example (seisflows examples run 1), I got the error below. It seems that data/001 directory is not created.
I am checking this on my side for understanding seisflows, but it would be great if you could give me any idea on this error?
================================================================================
COMPLETE EXAMPLE SETUP
================================================================================

================================================================================
RUNNING SEISFLOWS EXAMPLE WORKFLOW
================================================================================
2024-02-22 20:41:39 [INFO] | setup Inversion workflow
2024-02-22 20:41:48 [DEBU] | running setup for module 'system.Workstation'
2024-02-22 20:41:51 [DEBU] | running setup for module 'solver.Specfem2D'
2024-02-22 20:41:51 [INFO] | initializing 1 solver directories
2024-02-22 20:41:51 [DEBU] | mkdir 001
2024-02-22 20:41:55 [DEBU] | linking source '001' as 'mainsolver'
2024-02-22 20:41:57 [DEBU] | running setup for module 'preprocess.Default'
2024-02-22 20:41:57 [DEBU] | running setup for module 'optimize.Gradient'
2024-02-22 20:41:59 [INFO] | no optimization checkpoint found, assuming first run
2024-02-22 20:42:01 [INFO] |
////////////////////////////////////////////////////////////////////////////////
                              RUNNING ITERATION 01
////////////////////////////////////////////////////////////////////////////////
2024-02-22 20:42:01 [INFO] |
================================================================================
                           RUNNING INVERSION WORKFLOW
================================================================================
2024-02-22 20:42:01 [INFO] |
////////////////////////////////////////////////////////////////////////////////
                      EVALUATING MISFIT FOR INITIAL MODEL
////////////////////////////////////////////////////////////////////////////////
2024-02-22 20:42:01 [INFO] | evaluating misfit for model in `path_model_init`
2024-02-22 20:42:01 [INFO] | checking model parameters:
2024-02-22 20:42:01 [INFO] | vp: min=5800.000; mean=5800.000; max=5800.000
2024-02-22 20:42:01 [INFO] | vs: min=3500.000; mean=3500.000; max=3500.000
2024-02-22 20:42:01 [INFO] | preparing observation data for source 001
2024-02-22 20:42:01 [DEBU] | looking for data in: '/home/mnagaso/workspace/MINES/seisflows_projects/test/data/001/*'
2024-02-22 20:42:01 [CRIT] |
================================================================================
                               DATA IMPORT ERROR
                               /////////////////
001 found no `obs` data with wildcard:
'/home/mnagaso/workspace/MINES/seisflows_projects/test/data/001/*'. Please check
`path_data` or manually import data and re-submit
================================================================================

================================================================================
EXAMPLE FAILED

Command 'seisflows submit' returned non-zero exit status 255.
================================================================================

I close this PR because there is a dedicated development on the branch
https://github.com/adjtomo/seisflows/tree/bugfix-example_namspace_change

Thanks @mnagaso, yes I started working on that branch last week but did not have time to finish. There are a few critical changes I had made that need to be fixed before the example can run, should hopefully PR that early this week!

Hi @bch0w, Thanks you very much for this mention and updating the example class! It will be helpful for me to understand the structure of seisflow.


DisplayList has no proactive culling or support for RTrees as was available in SkPicture

Issue https://github.com/flutter/flutter/issues/92366 points out that DisplayList can be a lot slower rendering very complex scrolling pictures.
One tool that SkPicture uses to reduce rendering time is to maintain a BoundingBox Hierarchy for the picture. If such a hierarchy is available, it can use that data structure to home in on the draw records that intersect the clip. If it has no hierarchy then it will render all records.
The reason this may be important for #92366 is that it is rendering a picture with hundreds of thousands of lines, but only a tiny fraction of a percent of those lines fit in the scrolling window at any time. If the picture paint code can skip over a lot of those records quickly then it can more quickly draw only what is visible.
Adding such a mechanism to DisplayList may provide huge improvements for apps like the above sample.

Note that a workaround was posted for the developer issue mentioned above: https://github.com/flutter/flutter/issues/92366#issuecomment-965965579

https://github.com/flutter/engine/pull/34809 adds the ability to get an RTree from a DisplayList which will hopefully pave the way for PlatformView embedders to use a DisplayListBuilder instead of an SkPicturRecorder to capture the before/after rendering of the tree, but the information is not (yet) used for culling.

As you mentioned in https://github.com/flutter/flutter/issues/114784. In cases like platformview, DisplayList may also need the ability of rtree?

If we don't record saveLayer operations in RTree then we probably should. For one thing they may affect the correctness for PlatformView. Also, if we are basing culling on entries in the RTree then we need to consider the saveLayer ops. We potentially could just execute all saveLayers and rely on Impeller to cull them if they have no content, but not dispatching them at all is an even bigger win. I'm not sure how much they affect the PlatformView case since the individual content items already have their mutated bounds recorded I think?
We could also deal with saveLayer operations by recording the range of rendering ops that are in their content. If one of those ops is included in the selection from the RTree, then the saveLayer is needed.
Matrix ops are probably less critical to include, but we could save a bunch of math if we include them. They don't render anything so how does one compute their bounds?
Are clip ops included? Those could be handled like saveLayer - either include their bounds in the RTree so they get selected, or include a range until they are evicted by a restore operation and only execute them if something inside the range is selected.
Finally, there are attribute DLOps which don't really have "bounds", but rather they have a window of usage until the next attribute op replaces them. Given how fast they are to just update a field value, I don't think it would be worth it to pollute the RTree with bounds for every one of them or remembering a range over which they apply.

This is how the skia handles the non-drawing ops. Maybe we can do the same things.

-- SkRecordDraw.cpp --
// The interesting part here is how to calculate bounds for ops which don't
// have intrinsic bounds.  What is the bounds of a Save or a Translate?
//
// We answer this by thinking about a particular definition of bounds: if I
// don't execute this op, pixels in this rectangle might draw incorrectly.  So
// the bounds of a Save, a Translate, a Restore, etc. are the union of the
// bounds of Draw* ops that they might have an effect on.  For any given
// Save/Restore block, the bounds of the Save, the Restore, and any other
// non-drawing ("control") ops inside are exactly the union of the bounds of
// the drawing ops inside that block.
//
// To implement this, we keep a stack of active Save blocks.  As we consume ops
// inside the Save/Restore block, drawing ops are unioned with the bounds of
// the block, and control ops are stashed away for later.  When we finish the
// block with a Restore, our bounds are complete, and we go back and fill them
// in for all the control ops we stashed away.

In fact, in this way the bounds of non-drawing ops is equal to the range they apply. There will be an uncomplicated calculation process with this.
In the case of platformviews on DisplayList/Impeller, it can avoid drawing a full canvas with an overlay_canvas, I think it's worth for its improvement.

@endless7 I read that comment right before I wrote my previous comment here.
There are quite a few non-drawing operations that would need to add rectangles to the RTree when they do not need to.
The test of "is the next op that is visible within the bounds of my content" is the comparison of a single number so it is not complicated. We would be trading storing a single index into the DL record for these operations in lieu of storing an entire SkRect inside the RTree which not only has larger storage requirements, but also adds more work to balance the RTree with more "non-rendering" bounds stored in it.
In the case of platformviews on DL/Impeller, nothing has changed. We don't need to store bounds for non-rendering ops to be able to avoid a full redraw.

Also to be considered is that the incremental state property of DisplayList allows it to be 5 times smaller than the random access capable SkPicture. Hard data for this improvement is in this comment.

I have created a prototype of a culling mechanism that only needs a list of buffer offsets to perform the culling. Random access was not needed, the only thing we would need to do to enable it would be to associate the rects in the RTree with the offsets of the rendering primitive that executed them and then to iterate that list within the Dispatch method.
https://github.com/flutter/engine/pull/38189

Final, more mature solution is provided in https://github.com/flutter/engine/pull/38429


Deleting of wallet no password prompt Improvement

When deleting a wallet which has a sending password on it there is no prompt to enter the password. This seems insecure.
Suggest making users enter sending password to delete ad password protected wallet.

My only issue with this is if someone forgets the password, they can't remove the wallet.
Technically you should have the wallet backed up if you have a spending password, so if you lose it you can restore it.

➤ Craig MacGregor commented:
Closing this issue as per Matt's recommendation


first cut at #65

we can merge this if we want. unicode character entry is a little clunky via TeX mode but totally possible. i spent some time trying to figure out a much smoother way--where we give specific bindings for \F instead of \Bbb{F}---but got lost in elisp stuff and it wasn't that important.


Add Source to Mintscan chain info

Thanks for PR

@Source-Protocol-Cosmos
Thanks for PR.
we re-format chain param json.
I will merge your info soon with other task.

https://github.com/cosmostation/chainlist/commit/8a6a51a490f26a3a7fcf42338babbfd0af292a89
https://github.com/cosmostation/chainlist/commit/caa826ee428961e95dd6ba2417861d4f6d417549
Hi @Source-Protocol-Cosmos
The mintscan folder will be deleted.
We will update param with the same your information.
thank you