Consuming high amounts of memory?

Hiya, team!
We're running the daemon on our servers and are seeing extraordinarily high memory usage. I'm currently seeing one server with 20% (800M), and I've seen other servers with 50% (I don't recall if that was a 2G or 4G instance, but either way: 1-2G of memory consumed).
We're running the default configuration:
# Maximum buffer size in MB (minimum 3). Choose 0 to use 1% of host memory.
TotalBufferSizeMB: 0
# Maximum number of concurrent calls to AWS X-Ray to upload segment documents.
Concurrency: 8
# Send segments to AWS X-Ray service in a specific region
Region: ""
# Change the X-Ray service endpoint to which the daemon sends segment documents.
Endpoint: ""
Socket:
  # Change the address and port on which the daemon listens for UDP packets containing segment documents.
  UDPAddress: "<IP_ADDRESS>:2000"
Logging:
  LogRotation: true
  # Change the log level, from most verbose to least: dev, debug, info, warn, error, prod (default).
  LogLevel: "prod"
  # Output logs to the specified file path.
  LogPath: ""
# Turn on local mode to skip EC2 instance metadata check.
LocalMode: false
# Amazon Resource Name (ARN) of the AWS resource running the daemon.
ResourceARN: ""
# Assume an IAM role to upload segments to a different account.
RoleARN: ""
# Disable TLS certificate verification.
NoVerifySSL: false
# Upload segments to AWS X-Ray through a proxy.
ProxyAddress: ""
# Daemon configuration file format version.

I'm unsure of how to debug this. Any ideas?

Hi nathanielks,
I'm sorry to hear you've been seeing issues. The daemon logs should give a good indication to what's going on. Please see the logs section at the bottom of the docs page here: https://docs.aws.amazon.com/xray/latest/devguide/xray-daemon.html#
Can you give me a bit of information about your setup? Are you using EC2, Elastic Beanstalk or another service for your hosts? Do you have an idea of your traffic shape or requests per second? Are you experiencing any throttling? How long has the daemon been running?
We'll help you figure this out.
Thanks!
Sandra

Can you give me a bit of information about your setup?

I would be happy to provide more information!

Are you using EC2, Elastic Beanstalk or another service for your hosts?

✅ EC2

Do you have an idea of your traffic shape or requests per second?
How long has the daemon been running?

I'll use a single instance as an example. Its daemon has clocked 261:40.20 cpu minutes:seconds (pulled from top). It's currently consuming 1.5G. The instance gets anywhere from 5-10 requests per second.

Are you experiencing any throttling?

Not to my knowledge.

Can also confirm (same machine as @nathanielks) that the init looks good:
2018-08-10T18:01:49Z [Info] Initializing AWS X-Ray daemon 2.1.2
2018-08-10T18:01:49Z [Info] Using buffer memory limit of 37 MB
2018-08-10T18:01:49Z [Info] 592 segment buffers allocated
2018-08-10T18:01:49Z [Info] Using region: us-east-1

So far it seems that an update to 2.1.3 has resolved this, though I'll continue to monitor for another day or so.

Hi @nathanielks, @joehoyle ,
We recommend using daemon version 2.1.3 since we have upgraded AWS GO SDK and optimizes memory usage. Changelog: Link
Please let me know if you have questions and the daemon version works for you.
Thanks,
Yogi

Closing this issue, but please feel free to reopen if needed. Thank you!


Tab title shows './'

I have two test.ts-files open. One in the workspace root and another in a nested folder. The former shows as test.ts ./ which not very helpful. I'd rather not add more information here

This came in via #27718 and we settled on the decision to show an indicator to emphasize that the file is in root.


I followed the documentation . I prepared 350 one line Arabic images (xx.png) and their transcript (xx.gt.txt) and starting training with START_MODEL=ara.

I followed the documentation . I prepared 350 one line Arabic images (xx.png) and their transcript (xx.gt.txt) and starting training with START_MODEL=ara.

make training MODEL_NAME=elda START_MODEL=ara TESSDATA=data/ara_best

I am getting 100% as error rate.

I there something I am missing?
Originally posted by @soufieneghribi in https://github.com/tesseract-ocr/tesstrain/issues/252#issuecomment-854469078

This was fixed by LANG_TYPE=RTL. I'm closing this issue


Custom networking ipv4

Issue #, if available:
Description of changes:
New Blueprint Pattern to enable custom networking with IPv4.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

CDK version in the package.json was using older version 2.66.1. It caused some PRs to fail at the CDK list step. I have changed it to 2.72.0 and it passes. I have added the change as per this PR. Please review.

@shapirov103 Do you mind having a look in to this pattern which we want to use for our upcoming blog.

@ratnopamc Good Work on the Custom Networking Pattern some feedback :

We are changing our approach to add Primary CIDR to create VpcProvider which means you need to change that line of code to be in line.
Mikhail is changing to improve the make process based on pattern which is something we need to watch for.

@shapirov103 FYI

@elamaran11 @shapirov103
Thanks for your reviews.
I have opened https://github.com/aws-samples/cdk-eks-blueprints-patterns/pull/83 that incorporates the latest framework changes and incorporates review comments.
Will close this one.


Add layer API

Making ensemble initiate without estimator, and add add_layer method to construct ensemble of general layer structure.

On the topic of layer connections, assume full connection between specified estimators in layers for now.


fix: Relax websockets version requirements

relax websockets version requirements

Hey @impredicative , thank you for heads-up! Good point. I have just checked trade and stream (crypto) with websockets v12.0 and seems it works in my env. Based on the changelog of websockets, the incompatibility change is cutting Python 3.7 supports. Their policy is to keep compatibility as much as possible. If you found an issue, please let us know.
The reason of this change is that there was an issue to bump alpaca-py to v0.20.2 due to websockets requirements in a partner. Without upgrading alpaca-py, broker api could not fetch a trade account. Therefore, it is a critical issue and required to be resolved quickly. Decided to relax this version requirements.


Project License

I would like to use this in an Flask project I am working on, it basically consists of fetching and adding simulated assignments to calculate required scores. If this is possible, please add a License, such as the MIT License, the GNU GPLv3, or the Apache 2.0.

I added an MIT License. I made this over 2 years ago so there is no guarantee that it will still work. I believe powerschool has an actual api you can use as seen in this repo if you want to check that out.


GapsFiller.java:26-27: GapsFiller: get rid of this...

The puzzle 74-fdc38b44 from #74 has to be resolved:
https://github.com/iakunin/codexia-bot/blob/497e15b048f64f0b33f05ce00988b12af82a899c/src/main/java/dev/iakunin/codexiabot/hackernews/cron/GapsFiller.java#L26-L27
The puzzle was created by iakunin on 07-May-20.
role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle 74-fdc38b44 has disappeared from the source code, that's why I closed this issue.


Upgrade rules_kotlin_version to version that is compatible with bazel 6

This is the latest as seen in:
https://github.com/bazelbuild/rules_kotlin#workspace
Fixes #39

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

There is also mention of the supported Bazel versions in README.md.

I plan on dealing with that with:
https://github.com/google/summit-ast/pull/42


[crash] memory allocation failed error during parsing

Hey,
Just triggered this memory allocation bug. Don't know if your cargo-fuzz was able to catch it so I prefer to open an issue anyway ;)
$ ./target/debug/wain alloc_failed_wain.wasm
memory allocation of<PHONE_NUMBER>2 bytes failed[1]    10077 abort (core dumped)  ./target/debug/wain alloc_failed_wain.wasm

Download: alloc_failed_wain.zip
backtrace from gdb
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x00007ffff71e1801 in __GI_abort () at abort.c:79
#2  0x0000555555711a37 in std::sys::unix::abort_internal () at src/libstd/sys/unix/mod.rs:167
#3  0x000055555570f62d in rust_oom () at src/libstd/alloc.rs:282
#4  0x000055555572a9a7 in alloc::alloc::handle_alloc_error () at src/liballoc/alloc.rs:307
#5  0x00005555556a273c in alloc::raw_vec::RawVec<T,A>::reserve (self=0x7fffffffac38, used_capacity=0,
    needed_extra_capacity=266784254)
    at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4/src/liballoc/raw_vec.rs:345
#6  0x00005555556b19a9 in alloc::vec::Vec<T>::reserve (self=0x7fffffffac38, additional=266784254)
    at /rustc/49cae55760da0a43428eba73abcb659bb70cf2e4/src/liballoc/vec.rs:500
#7  0x00005555556a52cd in <wain_ast::Module as wain_syntax_binary::parser::Parse>::parse (
    parser=0x7fffffffd650) at wain-syntax-binary/src/parser.rs:325
#8  0x0000555555683827 in wain_syntax_binary::parser::Parser::parse (self=0x7fffffffd650)
    at wain-syntax-binary/src/parser.rs:126
#9  0x00005555556a2be2 in <wain_ast::Root<wain_syntax_binary::source::BinarySource> as wain_syntax_binary::parser::Parse>::parse (parser=0x7fffffffd650) at wain-syntax-binary/src/parser.rs:218
#10 0x0000555555683707 in wain_syntax_binary::parser::Parser::parse (self=0x7fffffffd650)
    at wain-syntax-binary/src/parser.rs:126
#11 0x00005555556806c8 in wain_syntax_binary::parse (input=...) at wain-syntax-binary/src/lib.rs:16
#12 0x00005555555930cb in wain::run_binary (bin=...) at src/main.rs:150
#13 0x00005555555933f1 in wain::main () at src/main.rs:179

Yes, I also triggered the same issue with cargo fuzz. And running cargo run with the same input does not trigger OOM crash.
This is because cargo fuzz runs fuzzer with RSS limit 2048Mb. I'm not sure that this is actually a bug.

using cargo run I trigger the crash as well:
$ cargo run alloc_failed_wain.wasm
    Finished dev [unoptimized + debuginfo] target(s) in 0.03s
     Running `target/debug/wain alloc_failed_wain.wasm`
memory allocation of<PHONE_NUMBER>2 bytes failed[1]    26931 abort (core dumped)  cargo run alloc_failed_wain.wasm

wasm-validate detect that the module is invalid
$ wasm-validate alloc_failed_wain.wasm
000000e: error: invalid global count 266784254, only 24 bytes left in section

I think your parser allocate the globals before checking the section validity.

Here is a summary I got from cargo fuzz
==14933== ERROR: libFuzzer: out-of-memory (malloc(2583691176))
   To change the out-of-memory limit use -rss_limit_mb=<N>

    #0 0x108465045 in __sanitizer_print_stack_trace+0x35 (librustc-nightly_rt.asan.dylib:x86_64h+0x4f045)
    #1 0x107ccd3e2 in fuzzer::PrintStackTrace() FuzzerUtil.cpp:205
    #2 0x107cab3ee in fuzzer::Fuzzer::HandleMalloc(unsigned long) FuzzerLoop.cpp:130
    #3 0x107cab233 in fuzzer::MallocHook(void const volatile*, unsigned long) FuzzerLoop.cpp:99
    #4 0x10846b5ba in __sanitizer::RunMallocHooks(void const*, unsigned long)+0x1a (librustc-nightly_rt.asan.dylib:x86_64h+0x555ba)
    #5 0x108419a46 in __asan::Allocator::Allocate(unsigned long, unsigned long, __sanitizer::BufferedStackTrace*, __asan::AllocType, bool)+0x816 (librustc-nightly_rt.asan.dylib:x86_64h+0x3a46)
    #6 0x108419208 in __asan::asan_malloc(unsigned long, __sanitizer::BufferedStackTrace*)+0x28 (librustc-nightly_rt.asan.dylib:x86_64h+0x3208)
    #7 0x10845bd4b in wrap_malloc+0xfb (librustc-nightly_rt.asan.dylib:x86_64h+0x45d4b)
    #8 0x107c8eb36 in alloc::alloc::alloc::hd266daa3740076ac alloc.rs:80
    #9 0x107c90085 in _$LT$alloc..alloc..Global$u20$as$u20$core..alloc..AllocRef$GT$::alloc::h011d981bf79805d2 alloc.rs:174
    #10 0x107c91dfe in alloc::raw_vec::finish_grow::h1680bcb9f7d39ad0 raw_vec.rs:514
    #11 0x107bb3ed1 in alloc::raw_vec::RawVec$LT$T$C$A$GT$::grow_amortized::h649b87ff493bc594 raw_vec.rs:440
    #12 0x107bad995 in alloc::raw_vec::RawVec$LT$T$C$A$GT$::try_reserve::h6504414e47357017 raw_vec.rs:281
    #13 0x107bbd5a3 in alloc::raw_vec::RawVec$LT$T$C$A$GT$::reserve::hfb92161d76ef410f raw_vec.rs:267
    #14 0x107c6df8b in alloc::vec::Vec$LT$T$GT$::reserve::h5065619728a4bf2e vec.rs:500
    #15 0x107c02b89 in _$LT$wain_ast..Module$u20$as$u20$wain_syntax_binary..parser..Parse$GT$::parse::h69b5dcf285f57ac4 parser.rs:310
    #16 0x107bd4fe6 in wain_syntax_binary::parser::Parser::parse::ha025a033f2f0d22a parser.rs:126
    #17 0x107bfbe3b in _$LT$wain_ast..Root$LT$wain_syntax_binary..source..BinarySource$GT$$u20$as$u20$wain_syntax_binary..parser..Parse$GT$::parse::he287170c56bf22a1 parser.rs:218
    #18 0x107bd5026 in wain_syntax_binary::parser::Parser::parse::hbc5ce223ae2fb081 parser.rs:126
    #19 0x107bc2971 in wain_syntax_binary::parse::h42ea5e43561b7c12 lib.rs:16
    #20 0x107b945e8 in rust_fuzzer_test_input binary_parser.rs:5
    #21 0x107ca5a62 in libfuzzer_sys::test_input_wrap::_$u7b$$u7b$closure$u7d$$u7d$::h2629f014b9239b24 lib.rs:27
    #22 0x107ca6c63 in std::panicking::try::do_call::h0b729c537da6eba6 panicking.rs:297
    #23 0x107ca7120 in __rust_try+0x30 (binary_parser:x86_64+0x100117120)
    #24 0x107ca67d6 in std::panicking::try::hc708128672bd0eca panicking.rs:274
    #25 0x107ca9d5e in std::panic::catch_unwind::h7be88b52f7253974 panic.rs:394
    #26 0x107ca53be in LLVMFuzzerTestOneInput lib.rs:25
    #27 0x107cae01d in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, unsigned long) FuzzerLoop.cpp:553
    #28 0x107d0bee1 in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) FuzzerDriver.cpp:292
    #29 0x107d113fd in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char const*, unsigned long)) FuzzerDriver.cpp:775
    #30 0x107d3d5c9 in main FuzzerMain.cpp:19
    #31 0x7fff60dfd3d4 in start+0x0 (libdyld.dylib:x86_64+0x163d4)

SUMMARY: libFuzzer: out-of-memory

Though the position OOM occurred is a bit different from yours, this has the same root cause. Let me explain.
Wasm binary format defines vec(B) structure. It is something like variadic length.
https://webassembly.github.io/spec/core/binary/conventions.html#vectors
It contains the length of vector at first u32 value. And the same number of elements are followed.
wain_syntax_binary::Parser at first parses the first u32 value and reserves memory on Vec with Vec::reserve (e.g. here). However, when the binary incorrectly sets too large value to the first u32 value, the Vec::reserve method crashes. To avoid this, we need Vec::try_reserve. But it is not stabilized yet so we need to wait for stabilization.

I think your parser allocate the globals before checking the section validity.

OK, I think I can add check by looking length of input before Vec::reserve. This is not perfect because input may contain the number of elements actually (imagine more than 4GB wasm binary). But almost all cases can be detected by checking input length in advance.

I fixed this at 6b09f8c.
After the fix, the fuzzer for the parser could run for 10 minutes without crash.


Doesn't return nearest neighbor

I'm getting some unexpected results from knn, like it ignores some of my points.
const tree = new RBush();
tree.load([
  [0, 0],
  [10, 10],
  ]);
console.log(knn(tree, 0, 0, 1)); // Prints [[10, 10]].

(Observable notebook)
Why doesn't it print [[0, 0]]? Am I doing something wrong?
Thanks!

RBush expects a different data format, not pairs of numbers. See https://github.com/mourner/rbush#data-format

RBush expects a different data format, not pairs of numbers. See https://github.com/mourner/rbush#data-format

Oh, sorry! Thanks a lot! I switched to https://github.com/ubilabs/kd-tree-javascript in the meantime but now I've switched back. rbush-knn is faster in my application!

@darabos great! Also, if you don't insert/remove points dynamically after the initial load, you might want to look at https://github.com/mourner/flatbush which is by far the fastest.

Ah, thanks, that's very helpful! I found https://github.com/mourner/kdbush but somehow missed Flatbush. Perfect.


Key-Value pair swapped

I have tried with documents where the end result leads to having the keys and values swapped wrongly. Is this a common occurrence? Has anyone else dealt with it?

Can you provide more context/code?

@matthewayne I wonder if it's just a service issue, as in the model isn't 100% accurate.

Is there a way to finetune the model and/or provide the samples it gets wrong ?

Closing for now, please reopen or create a new issue with the requested context if you're still having this issue


CLOUD-44707 use locally redundant storage accounts

@doktoric @martonsereg

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1820/

LGTM


Invalid compact creation date and processing date

I have generated AUX_INS___ product using the following scenario definition:
{
  "mission": "biomass",
  "scenarios": [
    {
      "name": "AUX_INS___",
      "file_name": "N/A",
      "processor_name": "procsim",
      "processor_version": "1.3.0",
      "task_name": "N/A",
      "task_version": "N/A",
      "log_level": "debug",
      "begin_position": "2020-01-01T00:00:00.000Z",
      "end_position": "2050-01-01T00:00:00.000Z",
      "creation_date": "2020-01-01T00:00:00.000Z",
      "compact_creation_date_epoch": "2000-01-01T00:00:00.000Z",
      "baseline": 1,
      "outputs": [
        {
          "type": "AUX_INS___"
        }
      ]
    }
  ]
}

and running:
$ procsim -s AUX_INS___ aux-gen-scenarios.json
2021-09-07T10:18:45.442104 N/A    [0000002773]: [I] Procsim v1.3.0 processor stub simulator
2021-09-07T10:18:45.442140 N/A    [0000002773]: [I] Simulate scenario AUX_INS___
2021-09-07T10:18:45.442151 N/A    [0000002773]: [I] No input files
2021-09-07T10:18:45.451642 N/A    [0000002773]: [D] Set baseline to 1
2021-09-07T10:18:45.453640 N/A    [0000002773]: [D] Set begin_position to 2020-01-01 00:00:00
2021-09-07T10:18:45.453683 N/A    [0000002773]: [D] Set end_position to 2050-01-01 00:00:00
2021-09-07T10:18:45.453715 N/A    [0000002773]: [D] Overwrite compact_creation_date_epoch from 2000-01-01 00:00:00 to 2000-01-01 00:00:00
2021-09-07T10:18:45.454106 N/A    [0000002773]: [D] Output directory is /opt/pnode/data/inputs
2021-09-07T10:18:45.454219 N/A    [0000002773]: [I] Create BIO_AUX_INS____20200101T000000_20500101T000000_01_BBFB39
2021-09-07T10:18:45.455495 N/A    [0000002773]: [I] Task done, exit with code 0

The creation_date specified in the scenario file is not taken into account and it is set equal to the product's generation date. In fact:

the compact creation date part of the product name BBFB39 is equal to 2021-09-07T08:18:45Z
the processingDate included in the MPH is equal to 2021-09-07T08:18:45Z.

Scenario parameters that are common to all generators (including the creation date) were ignored in AUX and MPL generation. I have pushed a fix to master that aims to resolve this bug.
I verified that

the compact creation date reads AFRS00 for your test case, correctly corresponding to 2020-01-01T00:00:00Z;
the processingDate in the MPH reads 2020-01-01T00:00:00Z as well.
I also verified the validity of the compact creation date and processingDate for different, randomly picked, dates.


[tool_crash] SentinelException

Command
flutter run

Steps to Reproduce

...
...
...

Logs
SentinelException
#0      new _OutstandingRequest (package:vm_service/src/vm_service.dart:1746:45)
#1      VmService._call (package:vm_service/src/vm_service.dart:2262:21)
#2      VmService.reloadSources (package:vm_service/src/vm_service.dart:2117:7)
#3      _reloadDeviceSources (package:flutter_too

Hi @goutham-tez, there's an existing issue tracking this in https://github.com/flutter/flutter/issues/96746.
Kindly follow up in the issue linked above for updates.
Closing from here as duplicate.
Thank you


Message Count isn't always accurate

Issue submitter TODO list

[X] I've searched for an already existing issues here
[X] I'm running a supported version of the application which is listed here and the feature is not present there

Is your proposal related to a problem?
It's common to use highwater - lowwater to get message count, but this isn't always accurate.
If a topic is compacted or has transactional markers, the message count on the topics list isn't exactly accurate.
related issue might be: https://github.com/provectus/kafka-ui/issues/3275
Describe the feature you're interested in
A bit unclear. I'm not sure how to get message count without consuming the whole topic..
Describe alternatives you've considered
No response
Version you're running
42c236d
Additional context
No response

Hi, we're not aiming to display the precise message count for the reasons you've already mentioned -- that's not possible without reading out the topic completely. Can you elaborate on why do you need to see the precise message count for such topics?

I had same case where I m comparing message count for source and target topics to ensure my Mirrormaker2 is replicating all data. Statistics page seem to show correct number where as summary is showing approx number

Indeed, using topic statistics is better suited for this goal.


easier helper functions instead of webpack

After using this package for a little while, I quickly grew tired of dealing with webpack, so I wrote some helper functions to eliminate the need for it entirely.
myproject/utils.py
from django_react.render import render_component
from django.contrib.staticfiles import finders
from django.shortcuts import render

def prerender_component(jsx_path, *arg, **argv):
    preren_path = finders.find(jsx_path).replace('.jsx', '_prerenderable.jsx')
    with file(preren_path, 'w+') as prerenderable_jsx:
        prerenderable_jsx.write("import React from 'react';\n");
        with file(finders.find(jsx_path), 'r') as jsx_file:
            prerenderable_jsx.write(jsx_file.read())
        prerenderable_jsx.write("\nexport default render;");
    return render_component(preren_path, *arg, **argv)

def render_react(request, template_path, context, *arg, **argv):
    """add the prerendered html to any react components found in context"""
    # pass it a context formatted like this:
    # context = {
    #     'components': {
    #         'MyComponent': {                          # component name
    #             'jsx_path': 'test.jsx',               # relative to static root
    #             'props': {
    #                 'themessage': 'barbarblackshee',
    #             },
    #             'html': 'generated by this function'
    #         },
    #     },
    #     ...
    # }
    # then use this in the template to get the component's html
    # {{components.MyComponent.html}}
    # and this to access its props
    # {{components.MyComponent.props.themessage}}
    if 'components' in context:
        for name, component in context['components'].iteritems():
            context['components'][name]['html'] = prerender_component(component['jsx_path'], props=component['props']) if 'jsx_path' in component else 'No JSX Path Specified'

    return render(request, template_path, context, *arg, **argv)

I use render_react inside my view, in place of plain render, e.g.:
views.py
from myproject.utils import render_react

def react_test(request):
    context = {
        'components': {
            'main': {
                'jsx_path': 'test.jsx',
                'props': {
                    'themessage': 'baabaablacksheep',
                },
            },
        },
    }

    return render_react(request, 'frontend/test.html', context)

And my template:
templates/frontend/test.html

        <title>Django + React demo</title>

            {{components.main.html}}

static/test.jsx
var TestView = React.createClass({
    render: function() {
        return (

{this.props.message}

        )
    }
});

var render = TestView;

That way the prerendered html is properly displayed, and I can mount the component using the same JSX file used to prerender it.  What do you think?  If I wrote a pull request implementing these as part of the package, would you consider merging it?  I'm open to suggestions/criticism as well.

Based on a superficial scan, this looks kinda similar to how I had django-react set up originally. You pointed it at a JSX file which exported a component, it would render it and provide a hook to dump in JS to mount it over the top of the pre-rendered html. I ended up stripping out those helpers because they necessitated that your app was tightly coupled to React's mounting strategy - if you wanted to hit an API or interact with the DOM you would have to run your code in the componentDidMount function which only runs on the client-side.
For a lot of use-cases where you only really want to a add a little bit of interactivity to your front-end, I think it would be useful to have some helpers in there. My big concern is that the more opaque the helpers, the more limiting the workflow becomes.
Anyway, a possible workflow...
# in your view

mountable_component = render_component(path_to_source, props, mountable=True)

{{ mountable_component }}

{{ mountable_component.render_js }}

From memory, the issues that I experienced when I implemented something similar:

need to wrap the markup in a uniquely identified html element so that the mount js knows what to target
the component will need access to React, so you either need to have a global React instance defined above the render_js call, or you can bundle React with the component (but this means that multiple components on the one page will React's codebase and increase network overhead)

I'll leave this open and mull it over for a few days.

Makes a lot of sense, the limitation on componentDidMount is definitely not desirable.  What about including the render_react helper method, but making it optional instead of using it as the primary render method?
I have to find a better way of handling the creation of the _prerender.jsx files, it's pretty hacky right now, definitely not production-ready.
I think the ability to specify and manipulate components in the context variable is really powerful though:
'components': {
            'Main': {
                'jsx_path': 'Main.jsx',
                'props': {
                    'first_name': 'firstnamename',
                    'last_name': 'lastnamename',
                    'username': 'adfsdf',
                    'total_lead_count': '{:,}'.format(52000),
                    'notification_count': 101,
                    'notifications': [
                        {'icon': 'users', 'color': 'red', 'text': "50 new leads added today"},
                        {'icon': 'download', 'color': 'aqua', 'text': "25 users bought stuff"},
                        {'icon': 'users', 'color': 'green', 'text': "418 duplicates need to be resolved"},
                        {'icon': 'users', 'color': 'yellow', 'text': "You changed your username"},
                        {'icon': 'users', 'color': 'red', 'text': "50 new leads abbb today"},
                        {'icon': 'users', 'color': 'red', 'text': "2 new BDRs joined"},
                    ],
                    'page_name': 'MAIN',
                    'page_description': 'The Home Dashboard',
                },
            },
        },

Coincidentally, it's already bundling the components when the WATCH_SOURCE setting is True (defaults to DEBUG). The renderer uses webpack to detect changes and rebuild everything on demand, mostly to circumvent Node's module cache.
The component's render bundle wouldn't be too easily usable outside of the Node though, the client-side would probably want global variables and node wants commonjs.
I suppose you could probably point webpack at a shim which exposes itself via a global variable. If you informed webpack to not parse the render bundle, it would be fairly performant as well.
Though, this still leaves the issue with bundling react along and potentially duplicating its codebase.
I suppose you could bundle react with the component if DEBUG and - if desired - generate a bundle omitting react for production.

After a few more days of building a data dashboard with this, I've revised my  method entirely.  I think if people want to do it the way I did in the above snippet, that's perfectly reasonable, and they can just write that code snippet, no need to include it in the library.  I was too quick to try and improve it before using it long enough haha.
On a related topic, what is your recommended way of building "Adapters" or API method groups to talk to mounted react components?
I've chosen to ditch Django templating entirely and compose everything in views and jsx files.  I have a single base.html file with basic head tags, shared scripts (react), and css, then it has the pre-rendered html and the props.
I then have several jsx (or compiled) files that represent my app pages, and I can use all the usual require()/import stuff to inherit an reuse components between them.  In my views I have ReactPage(View) classes that choose the appropriate jsx file to render, and compose smaller view functions to get the necessary props to pass to the pre-renderer and the template.
Incidentally I then can use those smaller view functions to make a REST api or other pages.  Not sure if it's the best system, but it's what I've figured out so far.  Are there any established best practices? What works best for you?

Did anyone make progress on this?
I'm trying to upgrade from 0.9 to 0.10, and the old render_js fit my project very well before, apart from the horrible speed. I don't think my requirements justify polluting my project with Webpack, and I can't imagine I'm the only one. I think there is much value in a library making React available to Django developers, without forcing them to learn half the javascript ecosystem as well.

I've excised and started rewriting the service, my intention is still to use a CommenJS bundled version of the component to circumvent the caches. You wouldn't be able to plug that straight into the frontend, but you could shim it pretty easily by wrapping it in another bundle with exports some mounting js.
The 0.9 mount script could be easily copy-pasted into a JS file. If you get the absolute path to the bundled component that we generate for rendering, you could simply require it, bundle that mount script, and then the frontend could pass in a selector and props to mount it.
The big issue I can see with this is the risk of generating multiple bundles which duplicate your codebase. I can't think of a good solution though, so maybe it should simply be documented with a long list of caveats.
PRs are more than welcome.

Hmm, this shouldn't be too hard actually.
The bundle target could be switched to umd - http://webpack.github.io/docs/configuration.html#output-librarytarget
Can probably infer an exportable var from the component's path. This'll need to be overridable (var kwarg) but for most cases you could probably just mangle the filename and append a hash of the full path - so /path/to/some-app/Foo-Component.jsx becomes Foo_Component_bbc717359e77c7150d55fe835b82c469 - http://webpack.github.io/docs/configuration.html#output-library
Will probably need a bundle kwarg to the render call, so that it uses webpack even if not watching.
The render_js method could be ported across mostly intact.

If watch or bundle kwargs, bundle it first, then pass into the renderer.
Will probably need to recouple to django-webpack, but this would enable all the webpack stuff to be excised from the renderer. Re #28
This is blocked by the rewrite of the webpack service :crying_cat_face:  but that'll land shortly

Might have to shim around React and the module exports though. Probably use externals and hope that the UMD setup will try to require it on the server and access a global on the client side.  http://webpack.github.io/docs/configuration.html#externals
Otherwise, will need to do a bit of a song and dance involving exporting both React and the component. If so, will probably need support for an option indicating the name that the component's exported as.

Very impressive progress you're making! I'm sorry I don't know enough of the Javascript stuff to be of any help, but I will happily test it in my setup and submit PR's for any bugs I may find when it is ready.

Thanks, @RasmusKlett.
I'm in the process of updating a project to use the new codebase. If everything goes ok, I'll push a new release up in a day or two.

@RasmusKlett @pirate
I've just pushed 0.11.0, which adds comparable functionality to what used to be in an older version django-react.
You can now now call {{ bundle.render_js }} to remount the component back over the renderer markup. You'll need to make sure that you've got a


[Web] HtmlElementView can not work with AutomaticKeepAliveClientMixin, Attempted to build a PersistedPlatformView, but it already has an HTML element FLT-PLATFORM-VIEW

Steps to Reproduce

full code to reproduce
	import 'package:flutter/material.dart';
import 'dart:html' as html;
import 'dart:ui' as ui;

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
	return MaterialApp(
	  title: 'Flutter Demo',
	  theme: ThemeData(
		primarySwatch: Colors.blue,
	  ),
	  home: MyPortal(title: 'Flutter Demo Home Page'),
	);
  }
}

class MyPortal extends StatefulWidget {
  MyPortal({Key key, this.title}) : super(key: key);

  final String title;

  @override
  _MyPortalState createState() => _MyPortalState();
}

class _MyPortalState extends State<MyPortal> {
  int _currentIndex = 0;
  PageController _pageController = PageController();

  @override
  Widget build(BuildContext context) {
	return Scaffold(
	  appBar: AppBar(
		title: Text(widget.title),
	  ),
	  body: SizedBox.expand(
		child: PageView(
		  controller: _pageController,
		  children: <Widget>[
			Iframe1(),
			Iframe2(),
		  ],
		  onPageChanged: (int index) {
			print("onPageChanged");
			setState(() {
			  _currentIndex = index;
			});
		  },
		),
	  ),
	  bottomNavigationBar: BottomNavigationBar(
		currentIndex: _currentIndex,
		selectedItemColor: Colors.amber[800],
		unselectedItemColor: Colors.blue,
		onTap: (index) {
		  print("onItemSelected");
		  setState(() => _currentIndex = index);
		  _pageController.jumpToPage(index);
		},
		items: const <BottomNavigationBarItem>[
		  BottomNavigationBarItem(
			icon: Icon(Icons.apps),
			label: 'Challenges',
		  ),
		  BottomNavigationBarItem(
			icon: Icon(Icons.people),
			label: 'Users',
		  ),
		],
	  ),
	);
  }
}

class Iframe1 extends StatefulWidget {
  Iframe1() {
	// ignore: UNDEFINED_PREFIXED_NAME
	ui.platformViewRegistry.registerViewFactory('iframe1', (int viewId) {
	  print("viewId $viewId");
	  var iframe = html.IFrameElement();
	  iframe.src = 'https://flutter.dev';
	  return iframe;
	});
  }

  @override
  _Iframe1State createState() => _Iframe1State();
}

class _Iframe1State extends State<Iframe1> with AutomaticKeepAliveClientMixin {
  @override
  bool get wantKeepAlive => true;

  @override
  Widget build(BuildContext context) {
	super.build(context);
	return Container(
		width: MediaQuery.of(context).size.width,
		height: MediaQuery.of(context).size.height,
		child: HtmlElementView(viewType: 'iframe1'));
  }
}

class Iframe2 extends StatefulWidget {
  Iframe2() {
	// ignore: UNDEFINED_PREFIXED_NAME
	ui.platformViewRegistry.registerViewFactory('iframe2', (int viewId) {
	  print("viewId $viewId");
	  var iframe = html.IFrameElement();
	  iframe.src = 'https://www.w3.org/';
	  return iframe;
	});
  }

  @override
  _Iframe2State createState() => _Iframe2State();
}

class _Iframe2State extends State<Iframe2> with AutomaticKeepAliveClientMixin {
  @override
  bool get wantKeepAlive => true;

  @override
  Widget build(BuildContext context) {
	super.build(context);
	return Container(
		width: MediaQuery.of(context).size.width,
		height: MediaQuery.of(context).size.height,
		child: HtmlElementView(viewType: 'iframe2'));
  }
}

Expected results:
click BottomNavigationBarItem can switch without reload web page again
Actual results:
switch between BottomNavigationBarItem produce error
Attempted to build a PersistedPlatformView, but it already has an HTML element FLT-PLATFORM-VIEW
════════ Exception caught by scheduler library ═════════════════════════════════════════════════════
PersistedOffset: is in an unexpected state.
Expected one of: PersistedSurfaceState.active, PersistedSurfaceState.released
But was: PersistedSurfaceState.created

flutter doctor -v
[√] Flutter (Channel master, 1.22.0-10.0.pre.161, on Microsoft Windows [Version 10.0.17763.737], locale zh-TW)
	• Flutter version 1.22.0-10.0.pre.161 at C:\flutter
	• Framework revision cba91c97d0 (2 hours ago), 2020-09-13 18:57:03 -0400
	• Engine revision 2fc054147e
	• Dart version 2.10.0 (build 2.10.0-121.0.dev)

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.0-rc1)
	• Android SDK at C:\Users\00016986\AppData\Local\Android\sdk
	• Platform android-30, build-tools 29.0.0-rc1
	• ANDROID_HOME = C:\Users\00016986\AppData\Local\Android\sdk
	• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
	• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
	• All Android licenses accepted.

[√] Chrome - develop for the web
	• Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[√] Android Studio (version 3.6)
	• Android Studio at C:\Program Files\Android\Android Studio
	• Flutter plugin version 49.0.1
	• Dart plugin version 192.8052
	• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)

[√] IntelliJ IDEA Community Edition (version 2018.3)
	• IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2018.2.6
	• Flutter plugin version 31.3.4
	• Dart plugin version 183.4886.3

[√] VS Code, 64-bit edition (version 1.48.0)
	• VS Code at C:\Program Files\Microsoft VS Code
	• Flutter extension version 2.25.1

[√] Connected device (3 available)
	• AOSP on IA Emulator (mobile) • emulator-5554 • android-x86    • Android 9 (API 28) (emulator)
	• Web Server (web)             • web-server    • web-javascript • Flutter Tools
	• Chrome (web)                 • chrome        • web-javascript • Google Chrome 85.0.4183.102

• No issues found!

flutter run -d chrome -v
[ +166 ms] executing: [C:\flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[ +133 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] 4732a214a7362a3781989977429f14202143b4f5
[   +1 ms] executing: [C:\flutter/] git tag --points-at HEAD
[ +129 ms] Exit code 0 from: git tag --points-at HEAD
[   +2 ms] executing: [C:\flutter/] git describe --match *.*.* --first-parent --long --tags
[ +157 ms] Exit code 0 from: git describe --match *.*.* --first-parent --long --tags
[        ] 1.22.0-9.0.pre-87-g4732a214a7
[  +13 ms] executing: [C:\flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[  +80 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/master
[        ] executing: [C:\flutter/] git ls-remote --get-url origin
[  +74 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[ +137 ms] executing: [C:\flutter/] git rev-parse --abbrev-ref HEAD
[  +80 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[   +1 ms] master
[  +89 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +5 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +32 ms] executing: C:\Users\username\AppData\Local\Android\sdk\platform-tools\adb.exe devices -l
[ +154 ms] List of devices attached
					emulator-5554          device product:sdk_gphone_x86_arm model:AOSP_on_IA_Emulator device:generic_x86_arm transport_id:6
[  +13 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[   +5 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[ +300 ms] Generating C:\Users\username\source\flutter\so_iframe_keep\android\app\src\main\java\io\flutter\plugins\GeneratedPluginRegistrant.java
[ +133 ms] Launching lib\main.dart on Chrome in debug mode...
[  +96 ms] Updating assets
[ +130 ms] Syncing files to device Chrome...
[  +70 ms] Generating C:\Users\username\source\flutter\so_iframe_keep\android\app\src\main\java\io\flutter\plugins\GeneratedPluginRegistrant.java
[  +67 ms] <- reset
[   +9 ms] C:\flutter\bin\cache\dart-sdk\bin\dart.exe --disable-dart-dev C:\flutter\bin\cache\artifacts\engine\windows-x64\frontend_server.dart.snapshot --sdk-root
C:\flutter\bin\cache\flutter_web_sdk/ --incremental --target=dartdevc --debugger-module-names --experimental-emit-debug-metadata -Ddart.developer.causal_async_stacks=true
--output-dill C:\Users\username\AppData\Local\Temp\flutter_tools.347b3692\flutter_tool.b941be9a\app.dill --libraries-spec
file:///C:/flutter/bin/cache/flutter_web_sdk/libraries.json --packages .packages -Ddart.vm.profile=false -Ddart.vm.product=false
--bytecode-options=source-positions,local-var-info,debugger-stops,instance-field-initializers,keep-unreachable-code,avoid-closure-call-instructions --enable-asserts
--track-widget-creation --filesystem-root C:\Users\username\AppData\Local\Temp\flutter_tools.347b3692\flutter_tools.d7b02faf --filesystem-scheme org-dartlang-app
--initialize-from-dill build\cache.dill.track.dill --platform file:///C:/flutter/bin/cache/flutter_web_sdk/kernel/flutter_ddc_sdk.dill
[ +492 ms] <- compile org-dartlang-app:/web_entrypoint.dart
[+20399 ms] Syncing files to device Chrome... (completed in 21,025ms, longer than expected)
[   +1 ms] Synced 26.9MB.
[        ] <- accept
[        ] Caching compiled dill
[ +498 ms] [CHROME]:
[   +3 ms] [CHROME]:DevTools listening on ws://<IP_ADDRESS>:64881/devtools/browser/54a64599-7e30-48b5-bb81-55f00c49c4b4
[+5526 ms] Debug service listening on ws://<IP_ADDRESS>:64912/AvKpMp9FyWc=

[ +355 ms] Debug service listening on ws://<IP_ADDRESS>:64912/AvKpMp9FyWc=
[   +2 ms] Warning: Flutter's support for web development is not stable yet and hasn't
[        ] been thoroughly tested in production environments.
[        ] For more information see https://flutter.dev/web
[   +1 ms]   To hot restart changes while running, press "r" or "R".
[   +1 ms] For a more detailed help message, press "h". To quit, press "q".
[+1026 ms] viewId 0
[+7768 ms] onItemSelected
[   +3 ms] onPageChanged
[  +53 ms] viewId 1
[+3160 ms] onItemSelected
[   +1 ms] onPageChanged
[  +34 ms] Attempted to build a PersistedPlatformView, but it already has an HTML element FLT-PLATFORM-VIEW.
[ +644 ms] C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 212:49  throw_
					C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 350:9                    build
					C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/platform_view.dart 88:7               update
					C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 878:15                   [_updateManyToOne]
					C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 714:7                    update
					C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/offset.dart 46:11                     update
					C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 878:15                   [_updateManyToOne]
					C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 714:7                    update
					C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/offset.dart 46:11                     update
					C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 878:15                   [_updateManyToOne]
					C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 714:7                    update
					C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/clip.dart 101:11                      update
					C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 878:15                   [_updateManyToOne]
					C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 714:7                    update
					C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/offset.dart 46:11                     update
					C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 950:17                   [_updateManyToMany]
					C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 718:7                    update
					C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/clip.dart 320:11                      update
					C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 853:15                   [_updateManyToOne]
					C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 714:7                    update
[  +67 ms] ══╡ EXCEPTION CAUGHT BY SCHEDULER LIBRARY ╞═════════════════════════════════════════════════════════
[  +10 ms] The following assertion was thrown during a scheduler callback:
[   +1 ms] Assertion failed: org-dartlang-sdk:///flutter_web_sdk/lib/_engine/engine/html/surface.dart:357:12
[   +4 ms] rootElement == null
[   +2 ms] is not true
[   +1 ms] When the exception was thrown, this was the stack:
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 212:49  throw_
[   +1 ms] C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 24:3    assertFailed
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 357:27                   build
[   +1 ms] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/platform_view.dart 88:7               update
[   +1 ms] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 878:15                   [_updateManyToOne]
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 714:7                    update
[   +1 ms] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/offset.dart 46:11                     update
[   +1 ms] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 878:15                   [_updateManyToOne]
[   +1 ms] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 714:7                    update
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/offset.dart 46:11                     update
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 878:15                   [_updateManyToOne]
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 714:7                    update
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/clip.dart 101:11                      update
[   +1 ms] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 878:15                   [_updateManyToOne]
[   +4 ms] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 714:7                    update
[   +1 ms] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/offset.dart 46:11                     update
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 950:17                   [_updateManyToMany]
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 718:7                    update
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/clip.dart 320:11                      update
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 853:15                   [_updateManyToOne]
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 714:7                    update
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/offset.dart 46:11                     update
[   +2 ms] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 853:15                   [_updateManyToOne]
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 714:7                    update
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/offset.dart 46:11                     update
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 950:17                   [_updateManyToMany]
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 718:7                    update
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/transform.dart 43:11                  update
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 853:15                   [_updateManyToOne]
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/surface.dart 714:7                    update
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/scene_builder.dart 542:25             <fn>
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/profiler.dart 36:18                        timeAction
[   +1 ms] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/html/scene_builder.dart 538:12             build
[   +1 ms] packages/flutter/src/rendering/layer.dart 772:35                                                                           buildScene
[        ] packages/flutter/src/rendering/view.dart 231:30                                                                            compositeFrame
[        ] packages/flutter/src/rendering/binding.dart 440:18                                                                         drawFrame
[   +1 ms] packages/flutter/src/widgets/binding.dart 914:13                                                                           drawFrame
[   +1 ms] packages/flutter/src/rendering/binding.dart 302:5                                                                          [_handlePersistentFrameCallback]
[   +1 ms] packages/flutter/src/scheduler/binding.dart 1117:15                                                                        [_invokeFrameCallback]
[   +2 ms] packages/flutter/src/scheduler/binding.dart 1055:9                                                                         handleDrawFrame
[   +1 ms] packages/flutter/src/scheduler/binding.dart 971:5                                                                          [_handleDrawFrame]
[   +1 ms] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/window.dart 758:13                         _invoke
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/window.dart 358:5                          invokeOnDrawFrame
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine.dart 228:18                                <fn>
[        ] ════════════════════════════════════════════════════════════════════════════════════════════════════
[   +1 ms] Another exception was thrown: PersistedScene: is in an unexpected state.
[+3112 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[   +2 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[  +13 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[  +18 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[  +14 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[+3001 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[   +3 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[  +22 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[   +6 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[   +8 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[  +17 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[  +17 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[  +14 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[  +16 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[  +19 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[  +13 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[  +17 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[  +17 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[  +68 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[  +60 ms] onItemSelected
[   +1 ms] onPageChanged
[  +34 ms] Another exception was thrown: PersistedScene: is in an unexpected state.
[  +17 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[  +20 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[  +19 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[  +16 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[  +19 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[  +22 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[  +19 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[  +16 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[  +15 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[  +20 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[ +689 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[   +6 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[  +27 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[  +12 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[  +13 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[  +15 ms] Another exception was thrown: PersistedOffset: is in an unexpected state.
[+2703 ms] Stopped debug service on ws://<IP_ADDRESS>:64912

[ +101 ms] Application finished.
[   +2 ms] "flutter run" took 51,438ms.
[ +156 ms] ensureAnalyticsSent: 150ms
[   +2 ms] Running shutdown hooks
[        ] Shutdown hook priority 4
[ +639 ms] Shutdown hooks complete
[   +1 ms] exiting with code 0

</details>

Hi @chunhunghan,
The issue seems to be occuring due to the fact that you are using HtmlElementView as a child inside another widget.
There's another open issue describing your case, 49634.
Can you check if that issue resembles yours ?
Thanks.

@darshankawar , thank you for your reply. the following full code works well without AutomaticKeepAliveClientMixin, but when switch between BottomNavigationBarItem, web page will reload again. the goal is to prevent reload web page.

 work well without AutomaticKeepAliveClientMixin
import 'package:flutter/material.dart';
import 'dart:html' as html;
import 'dart:ui' as ui;

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
	return MaterialApp(
	  title: 'Flutter Demo',
	  theme: ThemeData(
		primarySwatch: Colors.blue,
	  ),
	  home: MyPortal(title: 'Flutter Demo Home Page'),
	);
  }
}

class MyPortal extends StatefulWidget {
  MyPortal({Key key, this.title}) : super(key: key);

  final String title;

  @override
  _MyPortalState createState() => _MyPortalState();
}

class _MyPortalState extends State<MyPortal> {
  int _currentIndex = 0;
  PageController _pageController = PageController();

  @override
  Widget build(BuildContext context) {
	return Scaffold(
	  appBar: AppBar(
		title: Text(widget.title),
	  ),
	  body: SizedBox.expand(
		child: PageView(
		  controller: _pageController,
		  children: <Widget>[
			Iframe1(),
			Iframe2(),
		  ],
		  onPageChanged: (int index) {
			print("onPageChanged");
			setState(() {
			  _currentIndex = index;
			});
		  },
		),
	  ),
	  bottomNavigationBar: BottomNavigationBar(
		currentIndex: _currentIndex,
		selectedItemColor: Colors.amber[800],
		unselectedItemColor: Colors.blue,
		onTap: (index) {
		  print("onItemSelected");
		  setState(() => _currentIndex = index);
		  _pageController.jumpToPage(index);
		},
		items: const <BottomNavigationBarItem>[
		  BottomNavigationBarItem(
			icon: Icon(Icons.apps),
			label: 'Challenges',
		  ),
		  BottomNavigationBarItem(
			icon: Icon(Icons.people),
			label: 'Users',
		  ),
		],
	  ),
	);
  }
}

class Iframe1 extends StatefulWidget {
  Iframe1() {
	// ignore: UNDEFINED_PREFIXED_NAME
	ui.platformViewRegistry.registerViewFactory('iframe1', (int viewId) {
	  print("viewId $viewId");
	  var iframe = html.IFrameElement();
	  iframe.src = 'https://flutter.dev';
	  return iframe;
	});
  }

  @override
  _Iframe1State createState() => _Iframe1State();
}

class _Iframe1State extends State<Iframe1> {
  @override
  Widget build(BuildContext context) {
	return Container(
		width: MediaQuery.of(context).size.width,
		height: MediaQuery.of(context).size.height,
		child: HtmlElementView(viewType: 'iframe1'));
  }
}

class Iframe2 extends StatefulWidget {
  Iframe2() {
	// ignore: UNDEFINED_PREFIXED_NAME
	ui.platformViewRegistry.registerViewFactory('iframe2', (int viewId) {
	  print("viewId $viewId");
	  var iframe = html.IFrameElement();
	  iframe.src = 'https://www.w3.org/';
	  return iframe;
	});
  }

  @override
  _Iframe2State createState() => _Iframe2State();
}

class _Iframe2State extends State<Iframe2> {
  @override
  Widget build(BuildContext context) {
	return Container(
		width: MediaQuery.of(context).size.width,
		height: MediaQuery.of(context).size.height,
		child: HtmlElementView(viewType: 'iframe2'));
  }
}

Hi @chunhunghan,
I am trying to replicate your original code sample on latest beta, but it's complaining about label, and ui.platformViewRegistry.  Am I missing anything here ?
Thanks.

title was deprecated after v1.19.0. my version is 1.22.0-10.0.pre.87
source code of BottomNavigationBarItem
const BottomNavigationBarItem({
	@required this.icon,
	@Deprecated(
	  'Use "label" instead, as it allows for an improved text-scaling experience. '
	  'This feature was deprecated after v1.19.0.'
	)
	this.title,
	this.label,
	Widget activeIcon,
	this.backgroundColor,
  }) : activeIcon = activeIcon ?? icon,

You can use ignore: UNDEFINED_PREFIXED_NAME
// ignore: UNDEFINED_PREFIXED_NAME
ui.platformViewRegistry.registerViewFactory('iframe2', (int viewId) {

@chunhunghan,
I am on latest master (1.22.0-10.0.pre.136) and getting compile time error while trying to run your code.

I have update flutter version to Channel master, 1.22.0-10.0.pre.161 and also update full code. please try again.

Issue replicable on latest master.  When I switch from Challenges to Users tab and try to switch back to Challenges, I was not able to switch and it threw below exception log.
65529.mov.zip

log
════════ Exception caught by scheduler library ═════════════════════════════════════════════════════
The following assertion was thrown during a scheduler callback:
Assertion failed: org-dartlang-sdk:///flutter_web_sdk/lib/_engine/engine/html/surface.dart:357:12
rootElement == null
is not true

When the exception was thrown, this was the stack:
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 216:49  throw_
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 24:3    assertFailed
lib/_engine/engine/html/surface.dart 357:27                                   build
lib/_engine/engine/html/platform_view.dart 88:7                               update
lib/_engine/engine/html/surface.dart 878:15                                   [_updateManyToOne]
...
════════════════════════════════════════════════════════════════════════════════════════════════════

════════ Exception caught by scheduler library ═════════════════════════════════════════════════════
PersistedScene: is in an unexpected state.
Expected one of: PersistedSurfaceState.active, PersistedSurfaceState.pendingUpdate
But was: PersistedSurfaceState.released
════════════════════════════════════════════════════════════════════════════════════════════════════

════════ Exception caught by scheduler library ═════════════════════════════════════════════════════
PersistedOffset: is in an unexpected state.
Expected one of: PersistedSurfaceState.active, PersistedSurfaceState.released
But was: PersistedSurfaceState.pendingRetention
════════════════════════════════════════════════════════════════════════════════════════════════════

════════ Exception caught by scheduler library ═════════════════════════════════════════════════════
PersistedOffset: is in an unexpected state.
Expected one of: PersistedSurfaceState.active, PersistedSurfaceState.released
But was: PersistedSurfaceState.pendingRetention
════════════════════════════════════════════════════════════════════════════════════════════════════

════════ Exception caught by scheduler library ═════════════════════════════════════════════════════
PersistedOffset: is in an unexpected state.
Expected one of: PersistedSurfaceState.active, PersistedSurfaceState.released
But was: PersistedSurfaceState.pendingRetention
════════════════════════════════════════════════════════════════════════════════════════════════════

════════ Exception caught by scheduler library ═════════════════════════════════════════════════════
PersistedOffset: is in an unexpected state.
Expected one of: PersistedSurfaceState.active, PersistedSurfaceState.released
But was: PersistedSurfaceState.pendingRetention
════════════════════════════════════════════════════════════════════════════════════════════════════

flutter doctor -v
Flutter 1.22.0-10.0.pre.161 • channel master • https://github.com/flutter/flutter.git
Framework • revision cba91c97d0 (8 hours ago) • 2020-09-13 18:57:03 -0400
Engine • revision 2fc054147e
Tools • Dart 2.10.0 (build 2.10.0-121.0.dev)

Running flutter doctor...
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, 1.22.0-10.0.pre.161, on Mac OS X 10.15.4 19E2269, locale en-IN)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
[✓] Android Studio (version 4.0)
[✓] VS Code (version 1.46.1)
[✓] Connected device (2 available)

• No issues found!
dhs@Dhss-MacBook-Pro ~ % flutter config --enable-web
Setting "enable-web" value to "true".

You may need to restart any open editors for them to read new settings.
dhs@Dhss-MacBook-Pro ~ % flutter devices
Waiting for another flutter command to release the startup lock...
4 connected devices:

SM A260G (mobile)                   • 5200763ebcfa861f                     •
android-arm    • Android 8.1.0 (API 27)
iPhone SE (2nd generation) (mobile) • 312977A7-2DB1-4737-AEBB-35FA6522A309 • ios
• com.apple.CoreSimulator.SimRuntime.iOS-13-5 (simulator)
Web Server (web)                    • web-server                           •
web-javascript • Flutter Tools
Chrome (web)                        • chrome                               •
web-javascript • Google Chrome 85.0.4183.102

May be similar to 49634

@ditman can you please triage this? It sounds like a missing lifecycle event of some sort.

Will take a look!

Interesting that this works as expected in CanvasKit mode. Taking a look at the DOM renderer.

This seems to happen because the HTML renderer tries to recycle the "oldSurface" to render the next webview (when the fail happens, the old surface corresponds to view 1, and the current is 0). To do this, it calls build again to redo the build procedure.
This is a problem because build() asserts that the surface that we're going to render is fresh in a couple of places:

Checks that rootElement is not null (not true in our case).
Checks that the surface is in created state (not true in our case either!).

I worked around both issues by adding some code to the platform view's update code:
if (viewId != oldSurface.viewId) {
  // The content of the surface has to be rebuild if the viewId is changed.
  discard(); // Discard and transition to released...
  revive(); // But not really...
  // Now build...
  build();
}

Having to discard, then revive the surface is a little bit old; Probably the framework should create a new surface, instead of attempting to recycle an old one. I'll dive deeper into this.

After talking to @yjbanov, I discovered a method that seems better to implement this check: canUpdateAsMatch, that way we can discard view reuses before the framework even calls update.

A fix for this is coming; once the PR above rolls to flutter/flutter.
(It's a flutter/engine fix, so this might not get immediately fixed when the ticket is closed)


TheilSen and DpGumbelMedian

TheilSen - a data transformation which returns an array of pairwise slopes and intercepts from the given data.
DpGumbelMedian - implementation of a DP median using noise sampled from a Gumbel distribution.

(created for PR #287)

[ ] update so private candidates passed to utility matched private candidates passed into the mechanism

For the Gumbel, make sure that effective epsilon is used. This is dependent on p, from generalized resize, and c, the c-stability. P is optional, would be nice to rebase on top of the generalized resize branch.

Jayshree also mentioned- we need to change the behavior dependent on the privacy definition. Essentially--
Add/Remove - omit nans/infs
Substitute - include +-inf to be clipped later


Pandas append deprecation

Codecov Report

Merging #424 (9c3f8d0) into master (b4fe3dc) will increase coverage by 76.31%.
The diff coverage is 84.12%.

:exclamation: Current head 9c3f8d0 differs from pull request most recent head 10f848c. Consider uploading reports for the commit 10f848c to get more accurate results

@@             Coverage Diff             @@
##           master     #424       +/-   ##
===========================================
+ Coverage        0   76.31%   +76.31%
===========================================
  Files           0      176      +176
  Lines           0    28515    +28515
===========================================
+ Hits            0    21762    +21762
- Misses          0     6753     +6753

Impacted Files
Coverage Δ

resqpy/olio/wellspec_keywords.py
75.57% <66.66%> (ø)

resqpy/grid/grid.py
83.87% <85.39%> (ø)

resqpy/well/_blocked_well.py
87.51% <88.23%> (ø)

resqpy/olio/read_nexus_fault.py
95.45% <100.00%> (ø)

resqpy/olio/point_inclusion.py
95.69% <0.00%> (ø)

resqpy/well/_deviation_survey.py
95.03% <0.00%> (ø)

resqpy/grid/extract_functions.py
81.13% <0.00%> (ø)

resqpy/grid/write_hdf5_from_caches.py
76.54% <0.00%> (ø)

resqpy/surface/combined_surface.py
97.72% <0.00%> (ø)

resqpy/organize/tectonic_boundary_feature.py
88.57% <0.00%> (ø)

... and 170 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b4fe3dc...10f848c. Read the comment docs.


Dropwizard 2.0.0 release notes

As one of the last steps before we can release the major version of Dropwizard:
Update and write the Dropwizard 2.0.0 release notes.
@dropwizard/core
@dropwizard/committers

Hej, could you please provide some info when the final 2.0.0 will be ready?


Provide variable fields from ClusterClass

To make use of all possible variables provided by the specific ClusterClass, this should be generated out of it, the same way we do for the documentation, see https://github.com/SovereignCloudStack/cluster-stacks/pull/94.
In case of moin cluster, they are available publicly available here

Not only the variables can be fetched from the apiserver-link. The available cluster-classes and the namespaces they are deployed in can be used as input too.

The new dynamic approach fetches all available ClusterClass definitions from the kubeapi-server of the moin-cluster via the REST API provided by capi-jsgen. The response is a JSON Schema document, which gets read by react-jsonschema-form to render the form. This new form library allows us to dynamically render forms by just providing the schema of the data and the associated UI components


Apache Commons codec 1.11 dependency is having a vulnerability due to which Restassured is caught by BlackDuck and other scans.

Apache Commons codec 1.11 dependency is having a vulnerability due to which Restassured is caught by BlackDuck and other scans to have vulnerability.
This is the issue in current latest Restassured library 5.3.1 version. Curious when the next release is coming up and if the Commons-codec dependency is going to be upgraded to latest version?

Apache Commons codec 1.11 is a dependency of Apache httpclient 4.5. It was droppen by the switch to httpclient5. I expect that MR #1719 will fix this issue. @pvchaitu, can you confirm?

Yes, HttpClient5 (5.2.1) should take care of the issue and has no vulnerabilities as of today. Please also see if you can bump up below dependencies:
johnzon-mapper to 1.2.21 or later
jackson-mapper-asl to 2.15.2 or later


Display tags on website

Please Select if your Request is Either something new or an Enhancement

[x] Enhancement of an existing Feature.
[ ] Request of a new feature.

Please select the area your request applys to. (Multiple selections are Possible)

[x] UI
[ ] Workbench
[x] Publishing
[ ] Pods
[ ] Markdown
[ ] Hierarchy
[ ] Graph
[ ] Misc (Choose this if your not sure)

Is your feature request related to a problem? Please describe
No
Describe the solution you'd like
When publishing to website, it would be nice to have the list of tags of the page at the end of the page, like on Docker or Amazon documentation.
Describe alternatives you've considered
It could also be at the top of the page under the breadcrumb.
Additional context

For that, I think we would need a way to specify what a tag actually is.
Currently, they are Hierarchies as well.
Possible solutions to that would be to extend schemas to flag a hierarchy as a tag collection.

Yeah, I'd like to see that too. How about defining the tags outside of the actual note tree maybe in a seperate tag "environment"? Navigating tags in the hierarchy is a little cumbersome.


Item to be removed when checked

As of now we have a separate edit and delete button,

the item in the list should be deleted, once checked..

Hey @Pranavnk15 i would like to work on this issue!!

Hey @Pranavnk15 , Please assign this issue to me I want contribute to this project

Hey @Pranavnk15 i would like to work on this issue!!

@Panth1823 What's the progress??? Plz update

Hey @Pranavnk15 i tried solving the issue but i got an urgent college project presentation so i dont think i can solve it rn

Hey i would like to work on this issue

Hey @Pranavnk15 i would like to work on this issue


 Then please.  You even removed some comments. You never remove comments from somebody else's codes

Are you kidding me ? it's only css not rocket science.


[Tracking issue]: Improvements and Bugs fixes for December GA

### Tasks
- [ ] https://github.com/sourcegraph/cody/issues/1931
- [ ] https://github.com/sourcegraph/cody/issues/1932
- [ ] https://github.com/sourcegraph/cody/issues/1933
- [ ] https://github.com/sourcegraph/cody/issues/1934
- [ ] https://github.com/sourcegraph/cody/issues/1935
- [ ] https://github.com/sourcegraph/cody/issues/1936
- [ ] https://github.com/sourcegraph/cody/issues/1937
- [ ] https://github.com/sourcegraph/cody/issues/1959
- [ ] https://github.com/sourcegraph/cody/issues/1960
- [ ] https://github.com/sourcegraph/cody/issues/1964
- [ ] https://github.com/sourcegraph/cody/issues/1992
- [ ] https://github.com/sourcegraph/cody/issues/1993
- [ ] https://github.com/sourcegraph/cody/issues/1994
- [ ] https://github.com/sourcegraph/cody/issues/1995

CC: @danielmarquespt @thenamankumar @vdavid @kalanchan  for visibility

Everything is done here except one item which is on the board, so closing this; we can return to using the board.
@chenkc805, feel free to reopen this if it suits your workflow better to keep on using this in the remaining few hours.


[AnVIL DX] Determine files name and size fields being used

As per @dsotirho-ucsc:

Our /index/files endpoint (for AnVIL) currently returns two duplicated fields under hits[].files[]: file_name duplicates name, and file_size duplicates size.
Could you please confirm which of these the Data Browser uses? We would like to remove the duplication and not break the Data Browser in the process ;)
Note: This is not an issue for the /index/files endpoint for HCA, which only returns the short versions (name and size).
Thanks!

For example, see name and file_name in the files response:

@MillenniumFalconMechanic and @dsotirho-ucsc, I can confirm AnVIL CMG uses name and size. Thanks!

@MillenniumFalconMechanic and @dsotirho-ucsc, after double checking 🙄, I can confirm AnVIL CMG uses file_name and file_size.

Complete!


[9.4.x] ISPN-9725 Blackbox query tests are failing due to improper teardown

https://issues.jboss.org/browse/ISPN-9725

Merged


[Removal]: Skinny Wool Weasel

Hotspot Name
Skinny-Wool-Weasel
Hotspot b58 Address
112hcACkBuwcKKf3XjTcrkEEQqBqvAbEjvcgTCuQmGqduBZBXDAU
Discord Handle
Sharp818#3198
Hotspot Manufacturer
PantherX
Removal Reason
I bought this hotspot on the second hand market on March 26, 2022, total 10 hotspots, but not notice it was included in the denylist, I am buying the machine now to put it in the actual location, and did it right Deployment, without any cheating, please help me get removed from the denylist, thank you!
Modifications
No
Extra forwarders
No
Extra antennas
No
Additional Information
Helium Team
Thank you very much for your contribution to the healthy development of the network. As a victim of buying banned hotspots, I sincerely hope that you can help us solve the problem of hotspots being included in the denylist. I have deployed the machine correctly, please help me Detected, and lifted the denylist, thanks again!

This the same cheater who wants to be delisted from the denylist; Please refer to #3060. The hotspot shall be remain on the denylist.


[TCC] Evaluation gives very high loss value

Hi @debidatta
Once training is completed, I usually see that I get the training loss of around 0.005 with 60000 iterations for my settings.
But for evaluation when I run python -m tcc.evaluate --alsologtostderr --logdir $MODEL_DIR, I get a very high training loss like ~1.000. And I got a very small value for the kendalls tau task like 0.02. Though alignment looks working quite well.
I am wondering what could cause this discrepancy in the training loss between training and evaluation. Any feedback would be appreciated. Thank you!

Hi @yongwanlim thanks for reaching out.
Can you check the logs of the evaluate script to see if the checkpoint is getting loaded properly? Another thing to check would be if the function calls in eval script are being run in eval mode (training=False in Keras model calls). This used to happen implicitly before due to tf.keras.backend.set_learning_phase(0) but this feature was supposed to be deprecated in newer TF versions.

Hi @debidatta,
Thanks for the suggestions.
I think I resolved the issue. I had an issue in the following line:
restore_ckpt(logdir=CONFIG.LOGDIR, optimizer=optimizer, **algo.model) in evaluate_once function.
CONFIG.LOGDIR is being updated in evaluate() by assigning CONFIG.LOGDIR = FLAGS.logdif but in evaluate_once() when loading the checkpoint, CONFIG.LOGDIR was not actually FLAGS.logdir so I happened to refer to a wrong logdir.  I had to add CONFIG.LOGDIR = FLAGS.logdir again at the beginning of evaluate_once function.
Regarding your second suggestion, I have questions.
Shouldn't the following update make the base_model be operated in eval mode?
training = (tf.keras.backend.learning_phase() and CONFIG.MODEL.TRAIN_BASE != 'frozen')
x = self.base_model(images, training=training)

Should I additionally modify ConvEmbedder for the eval mode? For example, turning off fc_dropout and/or inputting training=false for batch normalization?
Any feedback would be appreciated. Thank you!

Yes you are right. That is the reason the eval is off.
I rechecked the second suggestion and you don't need to change anything if you are using the version of TF mentioned in requirements.txt.
For newer versions, tf.keras.backend.learning_phase() will be deprecated and you need to pass training=True/False explicity. The part you pasted already does this, so that's ok. The part that will need changing in the future is https://github.com/google-research/google-research/blob/master/tcc/utils.py#L302 and https://github.com/google-research/google-research/blob/master/tcc/utils.py#L396 where training=False needs to be passed.
Let me know if eval works for you now.


.autohentai doesn't work

Ok so idk if I'm using this correctly but whenever I try to do .autohentai in the nsfw channel, it doesn't work. .hentai and .hentaobomb work but not this for whatever reason. When I tried it in pm it didn't work either. Am o doing something wrong here?

Disabled on the public bot.


WIP: Add Python 2 support

Python2 support works for me locally, I'll try adding Python tests in this PR


Missing grounded actions.

Describe the bug
For some reason, some grounded actions are unavailable when using Pyperplan Grounder.
To Reproduce
from unified_planning.io import PDDLReader
from unified_planning.shortcuts import *

domain  = './domain.pddl'
problem = './problem.pddl'
task = PDDLReader().parse_problem(domain, problem)

with Compiler(problem_kind=task.kind, compilation_kind=CompilationKind.GROUNDING) as grounder:
    print(f'Grounder name: {grounder.name}')
    grounded_problem = grounder.compile(task, compilation_kind=CompilationKind.GROUNDING).problem

grounded_actions = [str(a.name) for a in grounded_problem.actions]

is_action_missing = not 'drive_truck1_distributor0_distributor0'in grounded_actions

with open('grounded_actions.txt', 'w') as f:
    for item in grounded_actions:
        f.write("%s\n" % item)

Screenshots

Additional context
instance.zip

Hi @MFaisalZaki! The reason is that the grounder removes all the grounded actions that are inapplicable or not useful to solve the problem. The smarter the grounder, the fewer grounded actions are generated.

That is so true @alvalentini, but I think this could impact when trying to solve goal recognition as planning tasks since an observation is a grounded action which may not be generated by the grounder. Is there any flag I can set to force the grounder to generate all actions?

It is possible using this grounder with the option prune_actions=False.
with Compiler(name='up_grounder', params={'prune_actions':False}) as grounder:
    grounded_problem = grounder.compile(task).problem

or
from unified_planning.engines.compilers.grounder import Grounder
grounder = Grounder(prune_actions=False)
grounded_problem = grounder.compile(task).problem

Awesome, thanks @alvalentini.

If the issue is solved, can you close the issue? Thanks!


Barcode detection not working (Android 10, Pixel 3XL)

See #3: @alvindizon
I was able to reproduce this on my Pixel 3XL running Android 10. Logcat contains the following line:
W/Gralloc3: allocator 3.x is not supported
Will update/close this issue, if I find out more about this...

May be related to this issue

Fixed in commit b452839bf22783074d67e6fb26d5898563bd7c1c by downgrading androidx.camera from 1.0.0-alpha05 to 1.0.0-alpha03.
I'll leave this open until I am able to use a newer version (waiting for beta/rc at least)

@kroegerama any news with that?

Thanks for your reminder! I just published an update of barcode-kaiteki (1.2.0).

available via MavenCentral
uses CameraX 1.0.0 stable

Feel free to open a new issue, if you encounter any errors :)

not  scanning show error like
E/ActivityThread: Failed to find provider info for com.oplus.statistics.provider
E/OplusStatistics--: IllegalArgumentException:java.lang.IllegalArgumentException: Unknown URL content://com.oplus.statistics.provider/track_event

E/ActivityThread: Failed to find provider info for com.oplus.statistics.provider

The same issue, camera in webview opens, but paused and works only while pressing on image

Hello. How did you decide this problem?

not scanning show error like E/ActivityThread: Failed to find provider info for com.oplus.statistics.provider E/OplusStatistics--: IllegalArgumentException:java.lang.IllegalArgumentException: Unknown URL content://com.oplus.statistics.provider/track_event

Hello. How did you decide this problem?


Typo  on 'welcome' / 'getting started' page.

'Provide' in sentence below should be 'prove'.
Discerning whether the correct security guidance was provided by the model might provide difficult using only text matching algorithms. Here we use a model to read the response and assess the quality of the answer.

Thanks, just fixed!


Inheritance redundancy column

I create 3 entities, for example :
class A {
public int Id {get; set }
public string Name {get; set; }
}
class B : A {
public string Location {get; set;}
}
class C : A {
public int Number {get; set;}
}
I run the command : k ef migration add initial, and entity framework generate 3 tables :
Table A with the columns Id, Name.
Table B with the columns Id, Name, Location.
Table C with the columns Id, Name, Number.
Don't create 1 table with column discriminator, what is the guideline for the inheritance code first implementation ?

Inheritance is one of the features that has not been implemented yet. The work is being tracked by this work item https://github.com/aspnet/EntityFramework/issues/247.


revert builder pit hack (FAILS)

#208
Upgraded to TileDB-SOMA 1.0rc0, which was expected to allow us to specify an explicit write timestamp. Alas, the unit test for the builder continues to fail (it passes without specifying the explicit write timestamp, as before).

I made a regression test in https://github.com/single-cell-data/TileDB-SOMA/pull/983 to at least be confident we fixed the specific problem in https://github.com/single-cell-data/TileDB-SOMA/issues/919 (not to exclude that others may exist). Agree with @thetorpedodog that condition looks sus.


[Fix #9235] Allow --only and --except to be able to properly qualify cops added by require.

Previously, cop names passed to --only or --except were qualified immediately, but because the configuration is not yet loaded when Options.parse is called, it could not properly resolve cops that are added by an extension or a local require. This was generally not a problem because unresolved cops were accepted, but in the case of a cop that shares a name with a default cop, this resulted in raising a warning that the department name was wrong, and in fact loading the wrong cop.
Instead, qualifying cop names is now done lazily, so that they are only qualified right before they are needed. This ensures that the full registry is present and external cops can be properly detected.
Fixes #9235.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Great solution to the problem at hand!


refactor: use k8s_service_info lib instead of SDI

Use the k8s_service_info for receiving the MLMD GRPC Service info instead of using the SDI, as it will stop being supported soon.
Fixes #76
NOTE for reviewers:

I have added a component for wrapping the k8s service info requirer because we need to:

Have a way to return a status based on the relation conditions
Because there is no other way to do logic that prevents errors in the init method of the charm. For instance, it would be weird to have a try/catch in the init method for ensuring the required relation is established.

Also note that this component could be placed in chisme, BUT that requires us to put charm libraries in the package, which is under discussion by the team.

Testing instructions

Deploy the charm in this branch
Deploy mlmd from channel latest/edge with trust
Relate both charms
Verify both charms go to active and idle

Test upgrade path
Because this charm was recently refactored from podspec to sidecar pattern, there will no be a migration from its previous stable version.

Created canonical/charmed-kubeflow-chisme#94 to capture the discussion about how we could reuse code like the Component here that needs a charm library

Approving since the last comment @ca-scribner had is resolved now.

Thanks @orfeas-k ! It looks like @ca-scribner has to approve it as he requested changes ;(

Approving since the last comment @ca-scribner had is resolved now.

Thanks @orfeas-k ! It looks like @ca-scribner has to approve it as he requested changes ;(

Dismissing @ca-scribner as the change he requested was very small and I did the change. Thanks both for the reviews!

:+1:  ty!


Add the ability to construct a HoverEvent from items

Since the ItemStack class implements HoverEventSource only on modern Paper, is there a way to show it through Adventure?
With my other reports, Adventure looks like it is mostly broken for 1.7.10-1.8.8.

Someone had to implement it by himself, can't this just be ported into adventure-platform? Especially when you advertise 1.7.10+ support.
https://github.com/FunnyGuilds/FunnyGuilds/blob/ffa1976ac2bc6e2c36e6c1ad3366483a4c6407f2/plugin/src/main/java/net/dzikoysk/funnyguilds/shared/adventure/ItemComponentHelper.java#L106

There is no such API for this at this time. If you wish to open a PR implementing this across adventure-platform, feel free! :D

But then why Adventure claims it's 1.8.8 compatible for years when major APIs are missing? Specifically if the wiki states on all places that 1.7.10+ is supported then it should be in alignment with that statement

The Adventure API does not have any representation of an "item" and therefore there is no support for such a thing in adventure-platform. 1.7.10+ is supported, but that doesn't mean that every single element of the entire game is supported obviously. Item hover events are just one of those things that aren't natively supported in the API. Of course, you can easily construct your own item hover events using the methods provided, similar to the code you linked earlier.
Please don't change the title of this issue back as you are specifically asking for new API that does not exist to be created for all versions.

The adventure-platform is specifically written to bridge Bukkit/Spigot/Paper to Adventure, hence I suggest the method to convert an ItemStack into the object that Adventure works with.
I changed the title intentionally because imho the logical outcome of a lack of this method is downstream incompatibility.


Turn pages using Volume Buttons

Hey, first, really great app. Would it be possible to add page browsing with volume up/down for back/forward? I used perfect viewer before finding ubooquity+kuboo and loved that feature.

Nice idea. I will try this evening.

@Skyline2k Can you please verify if this behavior is correct or vice versa? I have never seen this feature so I don't know what is standard.
Volume Up -> Next
Volume Down -> Previous

In perfect viewer it was an option to choose which hardware key has which function. On my phone I prefer volume down for page forward because it's easier to reach and used more often.
When reading on my tablet, I would mount it and use headphones with volume buttons to navigate the pages. There was also a 3rd button on the headphone cable, which I used to skip a comic/manga.
So. It's really up to you how you would like to implement it, I'm just happy you are doing it at all and replied that fast, thank you :)

Since this behavior intercepts the volume change, I have made it optional and can be enabled in the SETTINGS screen. It is disabled by default. The option is a single toggle for simplicity sake, if anyone wants a more advanced customization like Perfect Viewer let me know, maybe I will add it later.
I agree with your binding recommendation and it is set as follows:
Volume Up -> Previous
Volume Up Long Press -> Go to first
Volume Down-> Next
Volume Down Long Press -> Go to last
If the NEXT  book dialog is on screen, then a volume down button press will load the next book.
The long press feature only applies to COMICS  and PDF  because it does not make sense for EPUB.
It will be available in the next release or you can build the apk from source. Let me know if there are any issues.
commit fb833b72150a160eee4dfa17f4b13b792efe5711

@Skyline2k Your requested feature is live now on the Play Store (version 1.0.6).


Added the Alert Dialog for Signout

Added A Alert Dialog for Signout
Preview : https://github.com/user-attachments/assets/bbf23871-20ec-4920-85ec-5c7fa59610df
🛠 Type of Change

[ ] 🐛 Bug fix
[✅] ✨ New feature
[ ] 🚨 Breaking change
[ ] 📚 Documentation update

✅ Checklist
To ensure a smooth review process, please check off each item as you complete it:

[✅] Code Style: My code adheres to the project’s style guidelines.
[✅ ] Self-Review: I have reviewed my own code and made improvements.
[✅] Comments: I’ve added comments to explain complex or non-obvious parts of the code.
[✅] Documentation: I’ve updated the documentation to reflect my changes.
[✅] Warnings: My changes introduce no new warnings.
[✅] Tests: I’ve added tests to verify that my changes work as expected.
[✅] Passes Locally: All new and existing unit tests pass on my local machine.

@cb7chaitanya

Why have you added a pnpm lock file? @pruthviraj7714

@cb7chaitanya removed it

@cb7chaitanya can I create a new PR for this

Your Lint checks have been failed
And why did you push so many commits of others
You can close this pr and later you can create a fresh pr if this feature is required
thanks for your contribution
@pruthviraj7714


Stack Pointer Address Computation

In oder to implement a formula graph (#12), we have to have concrete addresses for every ld and sd instruction in the path.  Otherwise we can't solve aliasing.

@ckirsch I responded also in #12 .

we solve this issue during dataflow graph generation by partially evaluating RISC-U like old Monster. The stack pointer stays concrete at all times.


#70 Update version to 1.7

Coverage remained the same at 90.665% when pulling 268e4c1a589c774eb8ee7dc86441ca45a71cfbd2 on version-1.7 into 8db27b481e9cb585666c02b99f3b9218cc43530d on master.

Coverage remained the same at 90.665% when pulling 268e4c1a589c774eb8ee7dc86441ca45a71cfbd2 on version-1.7 into 8db27b481e9cb585666c02b99f3b9218cc43530d on master.

:+1:


clarify on how to open ~/.zshrc file in README.md

I had to stckoverflow this issue out. So I think it would be better to specify the method here.

I've reworded your changes to make more obvious that you have to use your favorite text editor. Thanks for bringing up this issue.


OnPremise version connections are unsuported in XrmToolbox?

Hello, thanks for the look. I'm trying to run tool against OnPremise connection and it tells that "current connection is not compatible". What is the reason of that?

@FixRM the XrmToolBox version of Dataverse REST Builder uses the Access Token in order to connect, the Access Token (as far as I know) is returned only for online connections.
If you need to use Dataverse REST Builder for an OnPremise instance, you can install the Managed Solution version.
Let me know if this solve your issue.

Not really, but thanks.


Support mapped operators

Airflow plugin was crashing when trying to apply task policies to dynamically generated tasks (i.e., MappedOperators). This fix will support current versions of Airflow and future versions when the following issue is addressed: https://github.com/apache/airflow/issues/24547.
Related Datahub issue: https://github.com/datahub-project/datahub/issues/6606
Checklist

[X] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[X] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[X] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[X] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

Addressed some linting issues + rebased


Add a git fetch module.

Assumes the repository is already checked out, and the remote exists,
otherwise we consider this an error.
If nothing is fetched, we return no change.

ok to test

ok to test

:+1:


Website: Ensure API documentation version matches site release.

This ensures that the version of the generated documentation matches that
specified in the site config file instead of what is checked in at HEAD, which
may differ.

lgtm


Doom not loaded when starting

When I start doom emacs, doom is not correctly loaded? (maybe)
I followed the install manual, and used all example files in core/template.
But when I open c++ file with doom emacs, smart-parens and lsp does not start.
(even (default +bindings +smartparens) and (cc +lsp) are included in init.el file)
But smartparens are enabled when I reload doom.
(Not lsp)
Does anyone knows how to fix it?

Did you setup the packages for lsp and friends? did you run doom update (and maybe doom sync?)?

What do you mean setup?

Yes, I followed all the steps.
I resolved by using (add-hook 'c++-mode-hook 'lsp).
Thanks!


report for AutoSDE events last week

added report to content>reports
widgets to content>dashboard>widgets

@agrare Hi Adam, I moved all the report and widget changes to the AutoSDE plug-in

@OrGur1987 can you add screenshots to the description here? (You can just copy from your old core PR)  This helps me build the sprint review slides.  Thanks!


Permutations of Array

Is your feature request related to a problem? Please describe.
I want to add the solution for the Problem Permutations which states to return all the possible permutations of the given array
[Problem Link]https://leetcode.com/problems/permutations/
Describe the solution you'd like
I would solve the problem using recursion.
Describe alternatives you've considered
An Alternate solution would be using the DFS algorithm but the recursive approach would be much easier to understand.
Programming language

[ ] C
[x] C++
[ ] Java
[ ] Python

@Ayush7614, @Amit366 I would like to add solution to this problem in Java. Please assign me this issue.

@Ayush7614 @Amit366 @Saurabh4626 @ravikr126 kindly assign me this issue.

@Ayush7614 @Amit366 i would like to add solution to this problem in java