Feature xplat targets

Fixes #134

@yonaskolb This is now pretty much feature-complete. If you could provide feedback that would be much appreciated!

Coverage increased (+0.06%) to 88.28% when pulling 9fd01a2257fe70a732b8ed1a24b36de285312d42 on feature-xplat-targets into 7455c7a55245324ba3b8a64ae64cbf1d8c9ffaed on develop.

Thanks! Going through this now, looking good! I'll list issues here as I find them. First off:
Specific platform targets are generated with the names appended with -tvOS and -iOS which is great. (They're the platforms I'm testing with) When referencing these frameworks however, the lowercase version must be used - target: Framework-ios instead of - target: Axis_API-iOS. That makes sense as that's what the platforms you defined where, but there's a mismatch with the generated target name.
Personally I think that iOS is better than ios, and the platforms should be renamed to iOS, tvOS, watchOS, and macOS to match apple's naming scheme, but that's just me

Struct's identifiers are all lower-cased by convention (it's more of a Ruby convention than anything). I'll fix up the referencing so it matches the final target name, since this goes against what a user expects.

@yonaskolb I'm considering changing the suffix naming anyway to underscores rather than hyphens, in Swift when you import the module, you have to replace the hyphen with an underscore anyway, so this may make everything a bit simpler if the target name, module name and reference name all match.

Regarding the platform names wouldn't it be good to name them what the platforms are actually called, rather then a ruby convention? The fact that ruby is used in the background is probably just an unknown implementation detail for many people. Just my 2 cents

I think this is one of those situations where we'll have to agree to disagree. I've taken your feedback on board, but for now the platform names will remain the same.

In regards to hyphens to underscores, makes sense. I actually changed the product name of the framework so the import is without any suffix at all

When specifying properties by platform (configuration of references), is there any way to set properties for all platforms? A $base platform or some other way?

Hi @yonaskolb, yes that is supported. You can use the fully fleshed out declaration style:
targets:
  App:
    configurations:
      $base:
        SWIFT_VERSION: 3.0
      ios: {...}
      tv: {...}

$base retains its existing behaviour of being merged into any configuration.

Nice one!

When I use $base I get an error:
undefined local variable or method `target' for #<StructCore::Processor::TargetCrossPlatformComponent:0x007fe78e118398>

configuration:
      $base:
        INFOPLIST_FILE: SDK/Support/Info.plist
        PRODUCT_NAME: SDK
      ios:
        FRAMEWORK_SEARCH_PATHS:
          - $(inherited)
          - $(PROJECT_DIR)/Carthage/Build/iOS
      tv:
        FRAMEWORK_SEARCH_PATHS:
          - $(inherited)
          - $(PROJECT_DIR)/Carthage/Build/tvOS

If I comment out the $base section, it generates without errors

Hi @yonaskolb, it's configurations, not configuration.

Oh whoops, thanks! I guess that might be an easy mistake for a user to make. They have a configuration section, and then add another platform or add a config specific setting, and they forget to rename configuration to configurations

Renaming to configurations gets me a new error.
undefined method `map' for nil:NilClass

configurations:
      $base:
        INFOPLIST_FILE: SDK/Support/Info.plist
        PRODUCT_NAME: SDK
      ios:
        FRAMEWORK_SEARCH_PATHS:
          - $(inherited)
          - $(PROJECT_DIR)/Carthage/Build/iOS
      tv:
        FRAMEWORK_SEARCH_PATHS:
          - $(inherited)
          - $(PROJECT_DIR)/Carthage/Build/tvOS

Also in the example file in this PR it's using configuration  when specifying platforms. Is it supposed to change only when using $base?
https://github.com/workshop/struct/blob/9fd01a2257fe70a732b8ed1a24b36de285312d42/examples/Cross_Platform_Application/project.yml

Hi @yonaskolb, can you paste you full project file please? The error could be elsewhere in the spec file.
No, that's not the case. Both configuration and configurations support specifying platforms, as well as sources, resources and references.

I guess the question is, in it's current state, when would you pick configuration over configurations? Plural only when specifying multiple configs? As in my example I'm not doing specifying config specific settings, only platform specific.
Also can can you specify both platform and configuration specific build settings and if so, in what order?

Ok, found the minimum spec that throws the error. It seems to be when you have configurations that aren't debug and release, and also specify a multi-platform target with platform specific and $base settings:
version: 2.2.0
configurations:
  debug new:
    type: debug
  release:
    type: release
targets:
  MyFramework:
    sources: source
    platform:
      - ios
      - tv
    type: ":framework"
    configurations:
      $base:
        SWIFT_VERSION: '3.0'
      ios:
        INFOPLIST_FILE: Info-ios.plist
      tv:
        INFOPLIST_FILE: Info-tv.plist

This shows the warning and error:
Warning: Config name INFOPLIST_FILE for target MyFramework was not defined in this spec. Ignoring target...
undefined method `map' for nil:NilClas

Ah yes, I see the issue now. Thanks for providing this!
You need to specify your configurations within the platform blocks, like this:
version: 2.2.0
configurations:
  debug new:
    type: debug
  release:
    type: release
targets:
  MyFramework:
    sources: source
    platform:
      - ios
      - tv
    type: ":framework"
    configurations:
      $base:
        SWIFT_VERSION: '3.0'
      ios:
        debug new: # <----------
          INFOPLIST_FILE: Info-ios.plist
        release: # <----------
          INFOPLIST_FILE: Info-ios.plist
      tv:
        debug new: # <----------
          INFOPLIST_FILE: Info-tv.plist
        release: # <----------
          INFOPLIST_FILE: Info-tv.plist

A platform block does not operate the same way as $base, it's almost like a namespace for configurations. The Specfile DSL may help you understand this better, as it's a little more descriptive:
target 'MyFramework' do
  platform 'ios' do
    configuration 'ios' do
      override 'INFOPLIST_FILE', 'Info-ios.plist'
    end
  end
end

I think the source of your other error is most likely down to not enough validation being applied to cross-platform targets. I'll see if I can tighten that up before this is merged!

Ok cool. So the only way to not have to repeat build settings for multiple platforms and configurations would be to use yaml anchors?

Yes that's correct. Either that or using configuration, but if you use that you can't use $base. In your scenario you could use configuration and YAML anchors to achieve this.

I was testing out referencing the multi-platform targets again without the upcoming fix to final target names. It seems at the moment there doesn't seem to be a workaround. Neither of these seem to work properly:
references:
  - target: MyFramework-ios

references:
  - target: MyFramework-iOS

The first one doesn't create any reference, and the second creates a broken reference and broken framework in the frameworks group with the name MyFramework-iOS. (note the dot suffix).

I was trying to put together an example that showed this broken referencing behaviour but encountered a different issue?
version: 2.2.0
configurations:
  debug:
    type: debug
  release:
    type: release
targets:
  MyApp:
    sources:
      - AppSource
    platform: ios
    type: ":application"
    references:
      - target: MyFramework-ios
      # - target: MyFramework-ios
        copy: true
        codeSignOnCopy: true
  MyFramework:
    sources:
      - FrameworkSource
    platform:
      - ios
      - tv
    type: ":framework"

This shows a warning and then error:
Warning: SDKROOT not recognised in configuration for target: 'MyFramework'. Ignoring...
Unknown platform for target

Is there something incorrect I can't see in the spec?

I'm thinking this'll need a little more time in the oven 😀
I'm considering copying the change for adding a source set to two targets into a seperate PR since it's a tiny change, and moving this PR to 2.3.0. That way you should still be able to achieve what you're after, in a slightly more verbose manner. Then later once this PR is merged you could migrate to what is essentially a shorthand.

#144 might have been contributing to an issue I had here

Yeah that's definitely a possibility. Xcodeproj' target generation was behaving very strangely which meant I had to rewrite one of the processor components.
I'll merge develop into this branch and see if the new issues you've mentioned are reproducible.

Cool, I'll test it again once 2.2.1 is merged into this 👍


Fix fix auto partition load lost data in multi sender

Proposed changes
Issue Number: close #xxx
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


iOS screenshot API

Fixes https://github.com/tangrams/tangram-es/issues/857

Also can you add some documentation for this? Thanks


Set up workflow to automatically add issues to the project board

After failing with https://github.com/marketplace/actions/assign-to-one-project (maybe that's just for the old projects, not the new "projects (beta)"???), I'm now trying to set it up with the automation from here: https://github.com/community/community/discussions/5378

This works now.
For future reference:
What is required?

Have a .github/workflow/project-management.yml file that contains the following:

name: Project automation

on:
  issues:
    types:
      - opened

jobs:
  add_issue_to_project:
    name: Add new issues to project board
    runs-on: ubuntu-latest
    steps:
      - run: |
          gh api graphql -f query='mutation($project:ID!, $issue:ID!) { addProjectNextItem(input: {projectId: $project, contentId: $issue}) { projectNextItem { id }  } }' -f project=${{ secrets.PROJECT_BOARD_ID }} -f issue=${{ github.event.issue.node_id }}
        env:
          GITHUB_TOKEN: ${{ secrets.MY_GITHUB_TOKEN }}

Have a github Personal access token in the repository that has the following permissions:

repo, workflow, write:org, read:org

It needs to be saved in settings; secrets; Actions => New repository secret as MY_GITHUB_TOKEN

Have the Project_Board_ID Node-ID set as a repository secret as well, i.e. PROJECT_BOARD_ID contains the node id.
To get the Node-ID, install github CLI, authenticate & do the following:
gh api graphql -f query='query{ organization(login: "fractal-analytics-platform"){ projectNext(number: 1) { id } } }’

This needs to be set up for each repo that should auto-add issues to the project board.


[Bug][iOS/Swift SDK] Multiple image input to vision models will throw error from TVM

🐛 Bug
When using the mlc-llm Swift package to chat with vision language models, specifically the Phi-3-vision-instruct model, errors occur when attempting to input an image for the second time or input multiple images simutaneously. The first image input processes correctly, but subsequent attempts result in one of the following errors:

NDArray size mismatch:

libc++abi: terminating due to uncaught exception of type tvm::runtime::InternalError: [23:07:43] /Users/neet/code/mlc-llm/3rdparty/tvm/src/runtime/ndarray.cc:213: Check failed: relative_byte_offset + view_size <= curr_size (11046600 vs. 1017846) : ValueError: View with shape [1, 1700, 2166, 3] and datatype uint8 would have a size of 11046600 bytes. This would occupy bytes 0 <= i_byte < 11046600 within the backing array. However, the NDArray being viewed only contains 1017846 bytes (shape = [1, 618, 549, 3], dtype= uint8).

Embedding shape mismatch:

libc++abi: terminating due to uncaught exception of type tvm::runtime::InternalError: [23:22:38] /Users/neet/code/mlc-llm/cpp/serve/model.cc:1023: InternalError: Check failed: embedding->shape[0] + offset <= dst->shape[0] (2535 vs. 2048) :

To Reproduce
Steps to reproduce the behavior:

Send an image from the iOS app through the Swift mlc-llm SDK MLCEngine.chatCompletion() as base64 encoded url. This image shall input into the pipeline and decode tokens correctly.
Send a second image, this time it will throw one of the two errors above.

or,

Send multiple images from the iOS app through the Swift mlc-llm SDK MLCEngine.chatCompletion() as base64 encoded url.

Expected behavior
The model should process multiple image inputs without throwing exceptions.
Environment

Platform: iOS
Operating system: macOS
Device: macOS
How you installed MLC-LLM: conda & pip
How you installed TVM-Unity: Source

I have the same issue on Ubuntu 24.04. Using openai API with mlc_llm serve of phi-3.5-vision.  Compiled from source

Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python3.12/threading.py", line 1073, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.12/threading.py", line 1010, in run
    self._target(*self._args, **self._kwargs)
  File "tvm/_ffi/_cython/./packed_func.pxi", line 339, in tvm._ffi._cy3.core.PackedFuncBase.__call__
  File "tvm/_ffi/_cython/./packed_func.pxi", line 270, in tvm._ffi._cy3.core.FuncCall
  File "tvm/_ffi/_cython/./packed_func.pxi", line 259, in tvm._ffi._cy3.core.FuncCall3
  File "tvm/_ffi/_cython/./base.pxi", line 185, in tvm._ffi._cy3.core.CHECK_CALL
  File "/home/chris/AI/mlc-llm-cuda/lib/python3.12/site-packages/tvm/_ffi/base.py", line 481, in raise_last_ffi_error
    raise py_err
  File "/workspace/mlc-llm/cpp/serve/threaded_engine.cc", line 182, in mlc::llm::serve::ThreadedEngineImpl::RunBackgroundLoop()
  File "/workspace/mlc-llm/cpp/serve/engine.cc", line 594, in mlc::llm::serve::EngineImpl::Step()
  File "/workspace/mlc-llm/cpp/serve/engine_actions/new_request_prefill.cc", line 119, in mlc::llm::serve::NewRequestPrefillActionObj::Step(mlc::llm::serve::EngineState)
  File "/workspace/mlc-llm/cpp/serve/data.cc", line 96, in mlc::llm::serve::ImageDataNode::GetEmbedding(mlc::llm::serve::Model, tvm::runtime::ObjectRef*, int) const
  File "/workspace/mlc-llm/cpp/serve/model.cc", line 116, in mlc::llm::serve::ModelImpl::ImageEmbed(tvm::runtime::NDArray const&, tvm::runtime::ObjectRef*, int)
  File "/workspace/mlc-llm/cpp/serve/function_table.cc", line 320, in mlc::llm::serve::FunctionTable::CopyToWorker0(tvm::runtime::NDArray const&, tvm::runtime::String, tvm::runtime::ShapeTuple, bool)
ValueError: Traceback (most recent call last):
  7: mlc::llm::serve::ThreadedEngineImpl::RunBackgroundLoop()
        at /workspace/mlc-llm/cpp/serve/threaded_engine.cc:182
  6: mlc::llm::serve::EngineImpl::Step()
        at /workspace/mlc-llm/cpp/serve/engine.cc:594
  5: mlc::llm::serve::NewRequestPrefillActionObj::Step(mlc::llm::serve::EngineState)
        at /workspace/mlc-llm/cpp/serve/engine_actions/new_request_prefill.cc:119
  4: mlc::llm::serve::ImageDataNode::GetEmbedding(mlc::llm::serve::Model, tvm::runtime::ObjectRef*, int) const
        at /workspace/mlc-llm/cpp/serve/data.cc:96
  3: mlc::llm::serve::ModelImpl::ImageEmbed(tvm::runtime::NDArray const&, tvm::runtime::ObjectRef*, int)
        at /workspace/mlc-llm/cpp/serve/model.cc:116
  2: mlc::llm::serve::FunctionTable::CopyToWorker0(tvm::runtime::NDArray const&, tvm::runtime::String, tvm::runtime::ShapeTuple, bool)
        at /workspace/mlc-llm/cpp/serve/function_table.cc:320
  1: tvm::runtime::NDArray::CreateView(tvm::runtime::ShapeTuple, DLDataType, unsigned long)
  0: _ZN3tvm7runtime6deta
  File "/workspace/tvm/src/runtime/ndarray.cc", line 213
ValueError: Check failed: relative_byte_offset + view_size <= curr_size (4320000 vs. 2260800) : View with shape [1, 1200, 1200, 3] and datatype uint8 would have a size of 4320000 bytes.  This would occupy bytes 0 <= i_byte < 4320000 within the backing array.  However, the NDArray being viewed only contains 2260800 bytes (shape = [1, 628, 1200, 3], dtype= uint8).

And it only goes wrong if the second image is larger than the first image.


Use child property tree

Use child property tree to group input parameters.
Relates to #37

Codecov Report

Merging #48 into master will increase coverage by 0.02%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master     #48      +/-   ##
=========================================
+ Coverage   88.78%   88.8%   +0.02%
=========================================
  Files          19      19
  Lines        1106    1108       +2
=========================================
+ Hits          982     984       +2
  Misses        124     124

Impacted Files
Coverage Δ

tests/test_restriction_matrix.cc
100% <100%> (ø)
:arrow_up:

tests/test_hierarchy.cc
82.23% <100%> (ø)
:arrow_up:

include/mfmg/dealii_adapters.hpp
91.3% <100%> (+0.39%)
:arrow_up:

include/mfmg/dealii_operator.templates.hpp
57.3% <100%> (ø)
:arrow_up:

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 862d7df...fc3057c. Read the comment docs.


expose id_token

I want access to the raw id_token (from the /oauth/token response).  My "serverless" single-page app integrates with a third-party app that needs an oidc token, access tokens are not appropriate.  I found that id_token is digested into the User object (accessible from useAuth0) but then that token is cached & inaccessible.  The auth0-spa-js and auth0-react SDKs (nevermind the Auth0 dashboard & docs) don't address this problem.
Blog articles why-should-use-accesstokens-to-secure-an-api come somewhat close, but again do not recognize that the 3rd-party Service will have the same relationship to Auth0 as Auth0 has to (e.g.) Google OAUTH.  Based on an id_token, Service will establish a user and issue its own access/refresh tokens.
Describe the ideal solution
useAuth0() should provide a method to get the authenticated user's id_token, or maybe the id_token should be a static member of the user object.  (The latter might be easier and require modification in auth0-spa-js only, but I see reasons to not make that object a Christmas tree.)
Alternatives and current work-arounds
There is more than one strategy to intercept fetch/request/xhr responses, but these are not accessible to a moderately skilled frontend dev.  SAML et al are not available or preferable for my intended 3rd-party Service (MongoDB Realm, btw).
Additional context
I look forward to discussion here, I'll likely submit a PR here and/or on auth0-spa-js sometime.

Dig deeply enough into the source, and you'll find that type IdToken has a member __raw.  Not sure if this is a documented feature anywhere, but it'll serve the need.

We had similar need, and ended up using __raw property too.
If that's the supported way, having it officially documented would be nice. If not, then we do need something supported.

@tgerk ,
Thanks for opening this, before we look into whether or not exposing the ID Token would be something we want to be doing, could you elaborate on why you need the ID Token to access MongoDB Realm? When I read https://docs.mongodb.com/realm/authentication/custom-jwt/, it talks about JWT format and which fields it expects but doesn't realy mention the fact that it should be an ID Token.
Thanks.

@frederikprijck The backend service I'm using requires ID token. Unfortunately, that's outside of my control to change that.

The Realm login flow is to issue its own access token for some provided user credential (email + password) or a third-party credential.  It makes more sense to me to provide an id_token in exchange for an access_token.  This flow is neither a subset or superset of OIDC or necessarily OAUTH.
Auth0-provided id_token and access_token provide different basic claims.  There is information in the id_token (e.g. data from the original social provider) which is useful to pass along.
I admit your point that setting up an audience for my Realm app, defining permissions and roles for that audience makes good sense.  Both paths will make sense, though:  an access_token can be passed as a second authorization with each Realm request to control function capabilities.  I believe I still need the id_token to establish user identity and the tenant they belong to.

If that's the supported way

This is the supported way and you should continue to use __raw if you really need the raw ID token. We would not remove it without considering it a breaking change. We will also take on board the feedback to improve our docs in this area, but we're not sure yet what form that will take.

Appreciation and thanks for <3 for the __raw property.
My previous comment in other words:  It is interesting to think of Auth0 as just another social provider.  And also, the assumption that the OAuth "Resource Provider" is on a managed server is unwarranted; counter-example being a serverless app, native app, or PWA.
Auth0 is miles ahead of Onelogin in this regard, though.  So thanks!


Changes for v3.0

It's time for a 3.0. This issue will be used to keep track of the changes planned or made for that release:
Breaking Changes

[ ] Remove deprecated NeoTree* commands, along with their methods in the base neo-tree module.
[ ] Remove close_floats_on_escape_key option in favor of explicit mappings
[ ] Change git_status table to return higher level objects instead of the raw two letter codes
[ ] Extract git module into separate library?
[ ] Default to Nerdfonts v3.0

Features
Other Changes

[ ] Make main the default branch to simplify the PR workflow

(feature request) could the default icons be made to be the Nerd Font v3 icons in neo-tree.vim v3? (see readme for what I'm talking about)

@miversen33 @nhat-vo @pysan3 I think it's time to cut over to working on v3.0 now. I really want to get the nerd font icon changes out and since #1017 will have a new config migration it's enough to finally push me over the edge of getting this done.
I think from here forward anything merged to main will be destined for the v3x branch and the next release we make will be v3.0. Also, once 3.0 is released, main will be the default branch.
Any comments or objections?

@cseickel
I think that is a great idea :) I know @nhat-vo  and @pysan3  spend more time working on the fancy new things, I just poke the borked shit ;) But still, I think moving forward is a good idea. Might be worth setting up a milestone and pinning issues to it so we have a general idea of what work we want to do for v3.x?

Totally agree. Let me just finish #1017 before the upgrade but other than that, I think it's a good time to upgrade.
I agree with making a milestone and I want @cseickel to actively distribute the feature requests into those milestones (v3.x, v4.x, or otherwise, never-implement) since we have a growing number of enhancement issues piling up with no hope of being addressed.

Sure, I can make a milestone for v3.0. I don't think we need milestones for future versions though because we only get a new major version number when breaking changes are needed.
Outside of that it's just a new minor version on every release, and I release every time we have new changes that have had some completely arbitrary amount of time sitting in main. Honestly, it's not completely arbitrary, I make judgment calls based on how long I think it should take to get bug reports on a given set of changes if there are any bugs to be found.
This all means that nothing is planned for v4 yet and there's no way we would ever think ahead more than one major version.

I'm closing this issue now that it has been converted to a milestone.

We may want to unpin this from the issue tab as well @cseickel?
As well as #486? tho I'm not sure why it's pinned in the first place.

I don't actually remember why "Extract git module into separate library? #1032" exists. I'm going to just close it. If anyone else remembers what this is, let me know.

As well as #486? tho I'm not sure why it's pinned in the first place.

I think I pinned it because enough people asked that I got sick of answering it. I think we can unpin both though.


Enable RAFT training reference to run on cpu and non-distributed mode

Do some of the task on: https://github.com/pytorch/vision/issues/5056

Change function name from validate to evaluate
Support --device and enable training on non-distributed mode

Sample script to run on non-distributed mode and on cpu:
 python train.py \
    --dataset-root $dataset_root \
    --name $name_chairs \
    --model raft_small \
    --train-dataset chairs \
    --batch-size 2 \
    --lr 0.0004 \
    --weight-decay 0.0001 \
    --epochs 2 \
    --output-dir $out_chairs \
    --device cpu

To test on CPU, I run on a mock dataset by replacing https://github.com/pytorch/vision/blob/main/torchvision/datasets/_optical_flow.py with https://gist.github.com/YosuaMichael/9c49729243ff9d467ece06ab8641680d.
Note that as of now, if we run on distributed mode using torchrun, then it must use --device cuda.

Update:
Support saving of the optimizer and scheduler on the checkpoint.

Hi @NicolasHug , I decided to put the commit for saving optimizer and scheduler in this PR as well: https://github.com/pytorch/vision/pull/5590/commits/09d78d102088d73215dea4bcf89bf9d68ed40e53
Could you also help to review this? Thanks!


Automatic support for animated webp

Steps to reproduce

Deploy site with animated Webp images using this plugin.
Note that the images are not animated after the site is deployed.

A link to a reproduction repository
N/A
More information about your build

[ ] I am building using the CLI
[X] I am building using file-based configuration (netlify.toml)

What OS are you using?
No response
Your netlify.toml file
The site uses the automatically generated `netlify.toml` created by the plugin.

Relevant log output (or link to your logs)
The logs are private but the support team at Netlify can get them for you.

Upstream issue https://github.com/unjs/ipx/issues/53

I've renamed this because it already supports animated output, but there's currently no way of automatically enabling it.

The same goes for gifs. Please give at least an opportunity to disable netlify optimization 👉👈

We now support animated webp images with the new image CDN using the v5 runtime.
I'll close this issue as we won't add it to the v4 runtime.
The v4 runtime is now in the maintenance support phase with no new features being added. Occasional bug fixes and security patches will be applied when needed.


toClass helper function

Implemented toClass helper function described in #34. Actually, this is something I really wanted!
Please take a look.

Excellent! Could you add some docs as well, please?

Sure!
And I just updated. Almost same as you've written on the issue.

This PR and #36 are duplicates, but I like elements of each so I'm going to merge both. Thanks!


Return non-zero exit code on failure

Currently, rustlr seems to just return from main once an error condition has been triggered, implicitly returning an exit code of 0. It's more useful to return a non-zero exit code, so that you can for example invoke rustlr in a build script and be able to tell if it succeeded or not.
To implement this change I modified the signature of rustle to return bool (true on success, false on failure) so that it is in line with other functions in the project that also return a Boolean value indicating success (perhaps returning Result<(), _> would be more appropriate?). In addition, if rustle returns false, rustlr exits with an exit code of 1.
P.S. This PR also changes some println! invocations to eprintln! as it seems that is what they should have been.

Thanks for the comments.  I'll try to look into the problem as soon as I can
On Thu, Dec 29, 2022 at 9:30 AM BridgeTheMasterBuilder <
@.***> wrote:

Currently, rustlr seems to just return from main once an error condition
has been triggered, implicitly returning an exit code of 0. It's more
useful to return a non-zero exit code, so that you can for example invoke
rustlr in a build script and be able to tell if it succeeded or not.
To implement this change I modified the signature of rustle to return bool
(true on success, false on failure) so that it is in line with other
functions in the project that also return a Boolean value indicating
success (perhaps returning Result<(), _> would be more appropriate?). In
addition, if rustle returns false, rustlr exits with an exit code of 1.
P.S. This PR also changes some println! invocations to eprintln! as it
seems that is what they should have been.
You can view, comment on, or merge this pull request online at:
https://github.com/chuckcscccl/rustlr/pull/1
Commit Summary

3194efb
https://github.com/chuckcscccl/rustlr/pull/1/commits/3194efb7087d8c16aa919fedee315a24bd50b26d
Changed a few println! invocations into more appropriate eprintln!
invocations
a54f632
https://github.com/chuckcscccl/rustlr/pull/1/commits/a54f632d380db3fa9d10f818dbeb4b037906af2c
Changed rustle to return a Boolean value indicating success

File Changes
(1 file https://github.com/chuckcscccl/rustlr/pull/1/files)

M src/main.rs
https://github.com/chuckcscccl/rustlr/pull/1/files#diff-42cb6807ad74b3e201c5a7ca98b911c5fa08380e942be6e4ac5807f8377f87fc
(28)

Patch Links:

https://github.com/chuckcscccl/rustlr/pull/1.patch
https://github.com/chuckcscccl/rustlr/pull/1.diff

—
Reply to this email directly, view it on GitHub
https://github.com/chuckcscccl/rustlr/pull/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKUYAC2Z6MO3MIKEZBVK66DWPXDBVANCNFSM6AAAAAATMIQ2AQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Add Weblate for translations

Add Weblate for translations.

Thank you for bringing this up. Unfortunately, it looks like it requires payment unless I self-host it (and I would have to pay to self-host it 😄).
Other than that, the project is still pretty small, so I don't see the need. Pull requests with new strings.xml files should be fine for now.
Still, I will keep this in mind if the need for such a service arises.


build(scripts): Add dev script

Closes #12
Changes

Adds script to run dev mode. Will watch and rebuild on changes
Deleted extra line (prettier)

Other notes (things to check, explanation of implementation, etc.)
Automatically updates and the yarn link will change with it. Makes dev much easier!

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Register theme with viser-ng?

Hi all,
I have download a them json file from https://viserjs.github.io/theme.html,
then just want to know how to register theme with viser-ng in Angular 2+ framework!
very urgent!
Thanks

https://github.com/viserjs/viser/issues/256

// theme color
var theme = {
  // data
}
// register theme
import { Global } from 'viser-vue';
Global.registerTheme('myTheme', theme)
//注册完后，设置主题
Global.setTheme('myTheme')


Adding a new Kafka plugin

It's a very simple plugin that do a bunch of _describe on the most convenient CLI tools of Apache Kafka.
This file is actually automatically generated from the help menus, the whole source code is available on https://github.com/Dabz/kafka-zsh-completions.
It's probably not perfect at all, so if you have any feedback, I take!
BTW: Code generation is pure evil, unfortunately I didn't find a better way to avoid starting a JVM at startup...

@mcornella would be awesome to have this plugin in oh-my-szh.


implement the possibility to type the entire version when conflict occured

Implements feature from #1714
Here's screencast:

Looks cool, thank you :)


Kubernetes Example Address already in use

Hey there,
I have a plain fresh Kuberentes setup running. Now I wanted to add Treafik, but it gives me an error, that the address 8080 is already in use:
kubectl apply -f traefik.yaml

The config is the default config from the examples folder.
Error syncing pod, skipping: failed to "StartContainer" for "traefik-ingress-lb" with CrashLoopBackOff: "Back-off 10s restarting failed container=traefik-ingress-lb pod=traefik-ingress-controller-2249976834-5a8l0_kube-system(d61d4637-b0af-11e6-9d04-0050563cd6c3)"

or the logs
time="2016-11-22T12:35:00Z" level=fatal msg="Error creating server: listen tcp :8080: bind: address already in use"

of course the port 8080 is already in use, because the api server uses it
tcp        0      0 <IP_ADDRESS>:8080          <IP_ADDRESS>:*               LISTEN      0          1750820     21231/kube-apiserve...

Any ideas? Thank you :)

Dont use 8080 for the web ui. Change to 8081 for example
apiVersion: v1
kind: Deployment
apiVersion: extensions/v1beta1
metadata:
  name: traefik-ingress-controller
  namespace: kube-system
  labels:
    k8s-app: traefik-ingress-lb
spec:
  replicas: 1
  selector:
    matchLabels:
      k8s-app: traefik-ingress-lb
  template:
    metadata:
      labels:
        k8s-app: traefik-ingress-lb
        name: traefik-ingress-lb
    spec:
      terminationGracePeriodSeconds: 60
      hostNetwork: true
      containers:
      - image: traefik
        name: traefik-ingress-lb
        resources:
          limits:
            cpu: 200m
            memory: 30Mi
          requests:
            cpu: 100m
            memory: 20Mi
        ports:
        - name: http
          containerPort: 80
          hostPort: 80
        - name: admin
          containerPort: 8081
        args:
        - --web
        - --web.address=:8081
        - --kubernetes

Thank you that works


add tsv renderer/output

#3! :-) let me know!
I went with TSV as the data has commas, and github only deals with comma- and tab-separated files.
also: it would probably make sense to add a link from the readme to the .tsv file

I went with TSV as the data has commas, and github only deals with comma-, or tab-separated files.

Wow, didn't expect it that quickly! :)
Looks great!


Apparently there is a crash with the video player when you exit the app and switch to another one

Seemingly fixed?


Auth refresh access tokens

added .gitignore and added creating user functionality.

Looks good to me! I'll go ahead and close the request.


depth infomation is lost after aligning depth to color

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
D435i

Firmware Version
<IP_ADDRESS>

Operating System & Version
Ubuntu 18.04

Kernel Version (Linux Only)
5.4.0-60-generic

Platform
PC

SDK Version
2.41.0 }

Language
python }

Segment
others

Issue Description
when I run align-depth2color.py, I found the showed pictures like this:

and when I debug, I found all the elements of depth matrix are zero:

however, the depth has infomation before aligned to color, so what can I do to get the aligned depth without losing infomation?

Hi @w-phenix   The example program align-depth2color.py produced a similar depth image in a past case.
https://github.com/IntelRealSense/librealsense/issues/2501
As advised in the case, could you try changing the line clipping_distance_in_meters = 1 #1 meter to use a value higher than '1' (meter).  A good test value would be '4'.

Hi @w-phenix   The example program align-depth2color.py produced a similar depth image in a past case.
https://github.com/IntelRealSense/librealsense/issues/2501
As advised in the case, could you try changing the line clipping_distance_in_meters = 1 #1 meter to use a value higher than '1' (meter).  A good test value would be '4'.

Hi @w-phenix The example program align-depth2color.py produced a similar depth image output and zeroed depth values in a past case.
#2501
As advised in the case, could you try changing the line clipping_distance_in_meters = 1 to use a value higher than '1' (meter). A good test value would be '4'.
https://github.com/IntelRealSense/librealsense/blob/master/wrappers/python/examples/align-depth2color.py#L34

It doesn't seem to work. I tried from 2 to 4, even a bigger number 10, but the depth data are still zero and the color picture shows grey all the time. Maybe I should check if my camera is broken?

Hi @w-phenix The example program align-depth2color.py produced a similar depth image output and zeroed depth values in a past case.
#2501
As advised in the case, could you try changing the line clipping_distance_in_meters = 1 to use a value higher than '1' (meter). A good test value would be '4'.
https://github.com/IntelRealSense/librealsense/blob/master/wrappers/python/examples/align-depth2color.py#L34

It doesn't seem to work. I tried from 2 to 4, even a bigger number 10, but the depth data are still zero and the color picture shows grey all the time. Maybe I should check if my camera is broken?

As you stated that you can receive depth successfully with a non-aligned image, that would indicate that your camera is not broken.
Are you able to receive a color image too when not performing alignment, please?

As you stated that you can receive depth successfully with a non-aligned image, that would indicate that your camera is not broken.
Are you able to receive a color image too when not performing alignment, please?

As you stated that you can receive depth successfully with a non-aligned image, that would indicate that your camera is not broken.
Are you able to receive a color image too when not performing alignment, please?

Yes, I can receive  both non-aligned depth image and non-aligned color image, like this:

The code I used is opencv_viewer_example.py

As you stated that you can receive depth successfully with a non-aligned image, that would indicate that your camera is not broken.
Are you able to receive a color image too when not performing alignment, please?

Yes, I can receive  both non-aligned depth image and non-aligned color image, like this:

The code I used is opencv_viewer_example.py

I researched your problem further but could not find an obvious reason why align-depth2color.py is not working for you.  Does the program close down if you press the Esc or Q key?  This would indicate that the program is at least responsive and not frozen.

I researched your problem further but could not find an obvious reason why align-depth2color.py is not working for you.  Does the program close down if you press the Esc or Q key?  This would indicate that the program is at least responsive and not frozen.

I researched your problem further but could not find an obvious reason why align-depth2color.py is not working for you. Does the program close down if you press the Esc or Q key? This would indicate that the program is at least responsive and not frozen.

Yes, I can quit normally by pressing the Esc or Q key. Futhermore, I can receive aligned color image (depth data are still 0) after commenting out this line bg_removed = np.where((depth_image_3d > clipping_distance) | (depth_image_3d <= 0), grey_color, color_image) and modifying this line to images = np.hstack((color_image, depth_colormap))
The output is as below:

I researched your problem further but could not find an obvious reason why align-depth2color.py is not working for you. Does the program close down if you press the Esc or Q key? This would indicate that the program is at least responsive and not frozen.

Yes, I can quit normally by pressing the Esc or Q key. Futhermore, I can receive aligned color image (depth data are still 0) after commenting out this line bg_removed = np.where((depth_image_3d > clipping_distance) | (depth_image_3d <= 0), grey_color, color_image) and modifying this line to images = np.hstack((color_image, depth_colormap))
The output is as below:

It looks as though the logic of this line:
bg_removed = np.where((depth_image_3d > clipping_distance) | (depth_image_3d <= 0)
is basically saying to set to a grey color the pixels whose depth either exceeds the defined clipping distance, or is equal to or less than zero.
Since the left-hand side of the image in your original comment was colored completely grey, that would suggest to me that the program interpreted the depth as either being equal / less than zero (i.e no depth detected) or that all the measured depth values were outside of the defined clipping distance.  Indeed, going back to the original images in this discussion, all of the depth coordinates registered as zero, which may account for the entire left-hand side being colored grey.
It may be worth using the Dynamic Calibrator tool on your camera (which calibrates both depth and RGB) to check whether the problems when aligning are due to a mis-calibration between the sensors.

It looks as though the logic of this line:
bg_removed = np.where((depth_image_3d > clipping_distance) | (depth_image_3d <= 0)
is basically saying to set to a grey color the pixels whose depth either exceeds the defined clipping distance, or is equal to or less than zero.
Since the left-hand side of the image in your original comment was colored completely grey, that would suggest to me that the program interpreted the depth as either being equal / less than zero (i.e no depth detected) or that all the measured depth values were outside of the defined clipping distance.  Indeed, going back to the original images in this discussion, all of the depth coordinates registered as zero, which may account for the entire left-hand side being colored grey.
It may be worth using the Dynamic Calibrator tool on your camera (which calibrates both depth and RGB) to check whether the problems when aligning are due to a mis-calibration between the sensors.

@MartyG-RealSense I studied the issue you suggested, but I still can't resolve my problem. They got the alignment order wrong (process the alignment before starting the pipeline) while I didn't.
By the way, just in case, I tried to put the alignment code before creating a pipeline or starting streaming, they all get the same result as the original order.

@MartyG-RealSense I studied the issue you suggested, but I still can't resolve my problem. They got the alignment order wrong (process the alignment before starting the pipeline) while I didn't.
By the way, just in case, I tried to put the alignment code before creating a pipeline or starting streaming, they all get the same result as the original order.

I carried out further careful research into your problem but could not find any other leads that might fix your problem with align-depth2color.py unfortunately.
The logical next step would be to try the alignment code from Intel's distance_to_object Python tutorial.
https://github.com/IntelRealSense/librealsense/issues/2560

I carried out further careful research into your problem but could not find any other leads that might fix your problem with align-depth2color.py unfortunately.
The logical next step would be to try the alignment code from Intel's distance_to_object Python tutorial.
https://github.com/IntelRealSense/librealsense/issues/2560

@MartyG-RealSense Yes, I tried distance_to_object, but encountered the same problem. So I think  the code is no problem, but the camera is something wrong.

@MartyG-RealSense Yes, I tried distance_to_object, but encountered the same problem. So I think  the code is no problem, but the camera is something wrong.

Thanks very much.  Another quick way to test the ability of the camera to align depth and color would be to map RGB to a depth point-cloud in the 3D mode of the RealSense Viewer.  The method for doing so is described in the link below.
https://support.intelrealsense.com/hc/en-us/community/posts/360051738754/comments/360015204353
If the depth and RGB still do not align then you can perform a quick calibration of the camera by going to the More option near the top of the Viewer's options side-panel and selecting the On-Chip Calibration option from its menu.
https://dev.intelrealsense.com/docs/self-calibration-for-depth-cameras

Thanks very much.  Another quick way to test the ability of the camera to align depth and color would be to map RGB to a depth point-cloud in the 3D mode of the RealSense Viewer.  The method for doing so is described in the link below.
https://support.intelrealsense.com/hc/en-us/community/posts/360051738754/comments/360015204353
If the depth and RGB still do not align then you can perform a quick calibration of the camera by going to the More option near the top of the Viewer's options side-panel and selecting the On-Chip Calibration option from its menu.
https://dev.intelrealsense.com/docs/self-calibration-for-depth-cameras

@MartyG-RealSense I use the RealSense Viewer to observe color frame and depth frame, they shows as belows:

and I also tried On-Chip Calibration. However, the alignment code still doesn't work after I calibrate:

I tried both intrinsic and extrinsic (speed fast and OCC All)

@MartyG-RealSense I use the RealSense Viewer to observe color frame and depth frame, they shows as belows:

and I also tried On-Chip Calibration. However, the alignment code still doesn't work after I calibrate:

I tried both intrinsic and extrinsic (speed fast and OCC All)

The alignment in the 3D mode of the Viewer also seems broken.
If On-Chip Calibration did not improve results then a more robust calibration of the depth and RGB sensors can be performed using the Dynamic Calibrator software tool.  Page 14 onwards of the tool's user guide instructs how to install it on Linux.
https://www.intel.com/content/www/us/en/support/articles/000026723/emerging-technologies/intel-realsense-technology.html

The alignment in the 3D mode of the Viewer also seems broken.
If On-Chip Calibration did not improve results then a more robust calibration of the depth and RGB sensors can be performed using the Dynamic Calibrator software tool.  Page 14 onwards of the tool's user guide instructs how to install it on Linux.
https://www.intel.com/content/www/us/en/support/articles/000026723/emerging-technologies/intel-realsense-technology.html

@MartyG-RealSense I installed the Dynamic Calibrator software tool as written in the user guide. Everything is good until I tried to calibrate the camera; The calibration unexpectedly failed to start:

@MartyG-RealSense I installed the Dynamic Calibrator software tool as written in the user guide. Everything is good until I tried to calibrate the camera; The calibration unexpectedly failed to start:

Are you using the camera in a USB 3 port please?  The tool was created before USB 2 support was introduced to the RealSense SDK and lists USB 3.1 in its Hardware Requirements documentation.
This error has also been reported to occur on a Windows computer with the RealSense UWP Driver version .<IP_ADDRESS> installed, though you are using Ubuntu and so that would not apply in this case.

Are you using the camera in a USB 3 port please?  The tool was created before USB 2 support was introduced to the RealSense SDK and lists USB 3.1 in its Hardware Requirements documentation.
This error has also been reported to occur on a Windows computer with the RealSense UWP Driver version .<IP_ADDRESS> installed, though you are using Ubuntu and so that would not apply in this case.

@MartyG-RealSense Can every camera eliminate the blue square in the middle? I tried for a long time but I couldn't completely eliminate it. After eliminating a part, the part that was eliminated before moving the camera will turn back to blue again. I don’t know if my method of elimination is wrong, or there are other things I didn’t notice...

@MartyG-RealSense Can every camera eliminate the blue square in the middle? I tried for a long time but I couldn't completely eliminate it. After eliminating a part, the part that was eliminated before moving the camera will turn back to blue again. I don’t know if my method of elimination is wrong, or there are other things I didn’t notice...

I have performed this procedure recently with a D435i myself, so it is certainly possible to eliminate all of the blue area.  It can be a little awkward though.
You should try to keep the camera at relatively the same distance throughout, and move it left, right, up and down until all of the blue area is removed.  For myself personally, the technique that worked best was following a regular movement pattern of the camera: up-down-left-right, up-down-left-right etc and repeat until all of the blue was removed.
I also highly recommend having a high timeout value set so that you are not repeatedly returned to the start of the process if it is not completed within the permitted time.

I have performed this procedure recently with a D435i myself, so it is certainly possible to eliminate all of the blue area.  It can be a little awkward though.
You should try to keep the camera at relatively the same distance throughout, and move it left, right, up and down until all of the blue area is removed.  For myself personally, the technique that worked best was following a regular movement pattern of the camera: up-down-left-right, up-down-left-right etc and repeat until all of the blue was removed.
I also highly recommend having a high timeout value set so that you are not repeatedly returned to the start of the process if it is not completed within the permitted time.

Hi @w-phenix   Do you require further assistance with this case, please?   Thanks!

Hi @w-phenix   Do you require further assistance with this case, please?   Thanks!

@MartyG-RealSense The camera still cann't perform the alignment, so our lab bought a new one. I will close this issue and thank you for your help!

@MartyG-RealSense The camera still cann't perform the alignment, so our lab bought a new one. I will close this issue and thank you for your help!

Thanks very much @w-phenix for the update!

Thanks very much @w-phenix for the update!


[Feature] Support business configuration management at the application level

Is your feature request related to a problem? Please describe.

In the actual enterprise implementation process, in order to reduce application size and effectively improve maintainability, it is necessary to abstract business-level configuration, provide application-level configuration management capabilities, and complete configuration content sharing between applications.
The current problems are as follows:

The component type Ref-Object can support the delivery of the ConfigMap of the Hub-Cluster to the Managed-Cluster, but it requires the object to exist in the cluster and manually associates the objects in the storage trait for business configuration. I think business configuration is a trait that needs to be independent and have the ability to reference metadata to increase the readability of the application.
At the same time, for the shared-resource policy to be provided in pr  (#4213) , it can complete resource sharing, but it still needs to clear the modifiable entry.  IMO, the complete sharing of underlying resources should be avoided as much as possible at the business configuration. Users only need to care about the configuration content.
The current configuration capability (storage trait) provided by the application will cause the expansion of the application specification. With the increase of configuration content, its readability and maintainability will be greatly reduced, and the number of applications that can be managed will be limited.

Therefore, it is hoped that KubeVela can have the unified management capability of configuration. It can use the Ref form to relieve the pressure of application expansion. At the same time, the configuration management can be completed independently of the application, so as to realize the reuse of configuration content.
Describe the solution you'd like

We can try to introduce the trait of config to manage business configurations such as ConfigMap and Secret. The UX layer provides a configuration management interface that supports users to pre-fill the configuration. The generated configuration metadata can be carried by ConfigMap or DB but differentiated from ref-object capabilities, and a provider of DynamicLoadTraitResource is provided to complete configuration conversion and support configuration delivery.
- type: config
    properties:
        - name: zsj-cm-1
          mountPath: /mount/test
          dataRef: nginx-conf
          version: v1
          encrypt: true

Topics to be discussed

When the configuration is stored in an external data source, whether the distribution and conversion of the configuration need to be upgraded to an independent controller. In this scenario, the configuration needs to have the GC capability to support the effective recovery of the corresponding resources during the application life cycle. Can ResourceTracker monitor secondary resources?
Need to effectively control the order in which resources are delivered. #4143
When trait only uses a ref to describe the specific configuration, version management needs to be performed for the configuration to support operations such as rollback.
How components perceive configuration changes and thus have the ability to proactively update. #4161
How to support canary release scenarios at the configuration level.

Describe alternatives you've considered

Additional context

What do you mean for "ResourceTracker monitor secondary resources"? Like patterns like ResourceTracker->Deployment->Pod?

Yes, if config works independently as a controller, it will need to monitor the resources generated by config and support effective recycling.


Overriding session middleware fails

Overriding session middleware fails.
Minimal reproduction:
import { MandarineCore, Mandarine, Override, MandarineSecurity, Controller, GET } from<EMAIL_ADDRESS>import { MandarineSessionContainer } from<EMAIL_ADDRESS>
@Override()
class WebMvcConfigurer extends Mandarine.Native.WebMvcConfigurer {
  getSessionContainer(): MandarineSessionContainer {
    return new MandarineSessionContainer();
  }
}

@Controller()
class Test {
  @GET("/hello")
  hello() {
    return "Hello, world!";
  }
}

new MandarineCore().MVC().run();

Stacktrace:
TypeError: Cannot use 'in' operator to search for '0' in undefined
    at new KeyStack (keyStack.ts:33:12)
    at Function.getCookieForSession (sessions.util.ts:35:31)
    at SessionMiddleware.createSessionCookie (sessionMiddleware.ts:83:78)
    at MandarineMvcFrameworkStarter.preRequestInternalMiddlewares (mandarineMvcFrameworkStarter.ts:80:44)
    at responseHandler (mandarineMvcFrameworkStarter.ts:156:18)
    at dispatch (middleware.ts:41:13)
    at router.ts:866:20
    at dispatch (middleware.ts:41:13)
    at composedMiddleware (middleware.ts:44:12)
    at dispatch (router.ts:872:28)

The reason why this is happening is because changeSessionContainer called in the proxy is not setting the keys property. It is set when Mandarine is initialized but after that it is ignored.


Deactivate Forms after Timeout

My Complete functionality is based on FormActions.
My Requirement is whenever a form is in active state, if user doesn't respond within 10 minutes, then automatically bot should say "Session Timeout Happened" and form should be deactivated.
Lets suppose think, if I enter "update case", bot will respond as "Please enter Case Number". If user doesnt enter any value within 10 minutes, in that case, the bot should automatically reply as "Timeout Happened" and should deactivate the form.
My Actions has following methods(required_slots,slot_mappings,slot_ask_messages,submit).
Can anyone help me on how to implement this and in which method of FormAction, do we need to incorporate the changes ?

Thanks for the question, our Github issue board is for bugs and feature requests only, though 😕
Please ask this question in the forum✨
If you were describing a bug, please create a report and fill out the template


Not compatible with Laravel 5.6

Getting the following error
In RemoveUnusedDefinitionsPass.php line 75:

  Serialization of 'Closure' is not allowed

Similar to #72, it won't work with Laravel 5.6 as it now pulls in Symfony 4 components and has a requirement for symfony/dependency-injection (^4.1) meaning downgrading to symfony/dependency-injection:"3.*" will no longer work.

The same here. Just installed Laravel 5.6 and Behat Extension, but it fails when I run:
vendor/bin/behat --init  giving the error described by @chriscornford
Trying to install symfony/dependency-injection:"3.*" raise an error due ^4.1 requirement.
Any Idea?

Think I may have this working using flaxandteal/Behat-Laravel-Extension@6fb801694365cdccd6cb3721e4abda7549e9aa97 - however, I am not familiar with Symfony DI so, as indicated in Behat/Behat#1108, I would be keen to get feedback from someone more knowledgeable about it before tidying for PR.
Nonetheless, combining this with flaxandteal/Behat@8f9c9d9a4dc857bc3d7437bd4ea27d3e2b2297d7 I have been able to run Behat-Laravel-Extension with Laravel 5.6

I'm facing the same issue

@philtweir Thanks! That worked!
For anyone else having this problem recently: make sure you apply the changes from each of the links mentioned by @philtweir, you will have to change two files: BehatExtension.php and HelperContainerExtension.php
Cheers!

Thanks for the feedback @edumueller ! As the upstream bugfix has now been merged (Behat/Behat#1163) and it seems this works for others OK, I've PR'd the above in #81

How did you get this to work? I've added to composer the repository to flaxandteal/Behat-Laravel-Extension and tried with dev-master and dev-bug/78-not-compatible-with-laravel-56 but I should put also "symfony/dependency-injection": "^4.1" as a composer require. Is that correct?

That should work - IIRC, symfony/dependency-injection will be pulled in from 4.x by Laravel automatically, so explicitly adding the 3.x requirement was essentially to avoid the breaking change (that should no longer be breaking).
Did you still have the same error message as at the start of this thread after pulling in dev-master Behat and dev-bug/78-not-compatible-with-laravel-56 from flaxandteal/Behat-Laravel-Extension?


impl Fromanyhow::Error for Trap

This is useful for using ? in functions exported from the host which return Result<_, Trap>.

Thanks for this! I'm a little wary to do it, however, because it's a lossy conversion. The original error object contains important contextual information (like the backtrace, list of error contexts, etc), and that all gets lost on conversion into a Trap. One thing we could consider, however, is to refactor the internals of Trap to have a variant of its representation where it stores an anyhow::Error perhaps?
One thing that'd also be great is if we could support anything that's E: Error or otherwise support other error types via generics rather than just anyhow::Error

Doing a better conversion is out of my depth, but I'd expect that those improvements can be made backwards compatibly. Right now this is the best that can be done with the public API, so this is just making the public API more ergonomic.
I didn't make this generic over E: Error because I didn't want to create any backwards compatibility hazard wrt to coherence, but I can do so if that's preferred.

We've already got an enum TrapReason, so how about doing something like this:
impl<T> From<T> for Trap where T: Into<anyhow::Error> {
    // ...
}

enum TrapReason {
    // ...
    Error(anyhow::Error),
}

impl Error for Trap {
    fn source(&self) { /* ... */ }
}

We can figure out later if it's necessary to expose the underlying error's original type, but otherwise for now that will at least sidestep issues with Display vs Debug and we'll be able to get a structure stack of causal errors.

FWIW, there are a few existing places that could use that too:
$ rg 'Trap::new\(format!\("\{:\?\}"'
crates/wasmtime/src/linker.rs
410:                        Err(error) => Trap::new(format!("{:?}", error)),

crates/c-api/src/error.rs
14:        Box::new(wasm_trap_t::new(Trap::new(format!("{:?}", self.error))))

The suggested impl<T> From<T> for Trap where T: Into<anyhow::Error> conflicts with the reflexive impl impl<T> std::convert::From<T> for T since Trap itself implements Error. I did add a conversion Box<dyn std::error::Error + Send + Sync>.
Based on the suggestions given and the uses in the project, I added a Error(Box<dyn std::error::Error + Send + Sync>) variant to TrapReason which allowed for some nice refactorings.
Trap::message is confusing to me, imo along with Display and Debug there are too many ways of converting a Trap to a string. But I kept it, though the return type had to be changed to an owned String.

This all looks great to me, thanks again for this!


chore(deps): upgrade configuration

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-configuration-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1376

Questions ?
Please refer to the Backport tool documentation


Problem in the description of class MetalModuleNode

The description of class MetalModuleNode is same to the class CUDAModuleNode.

thanks for the catch, can you create a PR to fix this?

@solin319 do you mind to send a PR?

Sorry, I'm not familiar with metal.


FlatList: Unexpected onEndReached when updating contentContainerStyle

Description
Hey there 👋
I recently discovered that when the contentContainerStyle of a FlatList changes this can result in unexpected calls of the onEndReached callback.
Additional notes
I discovered that the behavior changes based on what is in the provided style.
E.g. in our application our style only contained a paddingTop.
With that I was only able to discover the unexpected calls to onEndReached on Android.
Additionally when increasing the amount of dummy data to 200 entries the issue seems to disappear.
My thoughts
I wouldn't call this a huge bug, but it is an unexpected behavior.
And at least for us it caused a bug, where clearing our list caused our app to load the next page of it 🙈
React Native version:
Reproducible in Expo Snack.
We discovered it in
npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1
    react-native: 0.63.2 => 0.63.2

Steps To Reproduce
I created an Expo Snack demoing the issue.
Please note the issue does not occur in React Native Web, so please don't test with the web version in the snack
The link: https://snack.expo.io/@baumstumpf/onendreacheddifference

Switch to either iOS or Android (The web version works as expected)
See a list of 50 elements being rendered.
Go to the logs
See in the console that onEndReached is being called without any scrolling, just by updating the style every second.

Expected Results
I would expect that onEndReached is only called when I get close to the end.
Snack, code example, screenshot, or link to a repository:
The snack link is: https://snack.expo.io/@baumstumpf/onendreacheddifference
FYI
I changed the logic of our app to not update the style and the issue was gone.
So I don't urgently need a fix here, however I thought it is worth creating an issue here for further discussions and investigation and as it behaves as expected in Expo Web I would say it is a difference that is not really needed.
Thank you for your time 🙏

Also, with the ListFooterComponent property update, the same thing happens: the onEndReached event is logged twice.
 npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1
    react-native: 0.63.3 => 0.63.3

code example:
ListFooterComponent={isLoading ? ListFooterLoadingComponent : ListFooterComponent}


Change version to 0.22.0 for daily release

What do these changes do?

Related issue number

Fixes

Codecov Report

Merging #2658 (a7f575f) into main (2657bec) will decrease coverage by 6.21%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2658      +/-   ##
==========================================
- Coverage   73.66%   67.45%   -6.21%
==========================================
  Files          99       99
  Lines       10279    10279
==========================================
- Hits         7572     6934     -638
- Misses       2707     3345     +638

see 19 files with indirect coverage changes

Continue to review full report in Codecov by Sentry.

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


[DO NOT MERGE] Teaser video thumbnail/teaser update

Jira
(Enter a link to the Jira issue this PR applies to, if any)
Summary
(Enter a one-line summary of the changes in this PR. This will be included in the release notes)
Details
(Explain the changes in enough detail fo reviewers to understand. Raise any questions for reviewers to consider.)
How to test
(List clear steps to test that the changes are working)
Release notes
(Optionally, add details that will be added to the release notes. Use this to call out deprecations. Read more)
Visual changes
(Note any visual changes associated with this PR. This will be shared with QA team for VRT.)

The work will be done in this ticket, https://pegadigitalit.atlassian.net/browse/DS-471. Closing.


Bug: The database connection executed by sql in the dashboard lacks self-built library loading (mysql).

Chat2DB Version
2.0.13
Describe the bug
In the dashboard, only the built-in schema is loaded in the database loading part (Mysql) next to SQL execution, and the created schema cannot be loaded.

try pro version
https://chat2db.ai/zh-CN/download


Add an "edit" API endpoint

This should take a set of data that's essentially a subset of States Daily rows, but with an edit note and explanation. The endpoint should create a new "edit" batch for this data.

And also done


High-DPI icons for server (and tracker viewer)

Apparently when I built those icons, I didn't include high-enough resolution for a nice crisp image in the toolbar on a high-dpi display like that on the Razer Blade 2014.
Need to:

[ ] Find out which resolutions are needed in Windows icons these days
[ ] Find out if we can commit the SVG versions of the logo and icons to this repo ( @yboger ?)
[ ] Export the SVG at the correct resolutions
[ ] Make an .ICO file with them - think IcoFX 1.6.4 (free) should work, though would be nice if there was something command-line and thus scriptable

Assigning to myself since I have the SVGs right now.

The most obvious way to generate PNG from SVG images would be through pretty much the only option most people use for SVG editing, the open source Inkscape program. To use export images with it:
inkscape -z -e icon.png -w WIDTH -h HEIGHT test.svg

If you have to combine these into a .ico file, imagemagick is good for the job:
convert icon-32.bmp icon-64.bmp icon-128.bmp icon-256.bmp myicon.ico

I believe imagemagick also supports PNG, but from what I've heard it's quite finicky and doesn't give as-good results.

Yes, made them in Inkscape, and that the inkscape command in a script is how I made them in the first place. Didn't realize imagemagick could make an .ico, though - I can't remember the command line tool I had used a few years back, but used IcoFX free (not command line) this past time.
I'm thinking it should be OK to commit the SVGs since there's lots of OSVR art out there now.

OK, looks like the stack is 16, 24, 32, 48, 256. Got the OK to commit. Not scripted right now, but better than before.


Only single instance allowed

Describe the bug
Whenever I try to reauthorize the integration I get the error "Only single instance"

To Reproduce
Steps to reproduce the behavior:

Go to settings to reauthorize integration
Click on configure
Enter catch
See error

Expected behavior
A working system
Screenshots
see above

please retest with latest version and comment back here

Go exactly the same issue :-/

Im having the same issue

Same issue here, totally removed from system then added back but same problem

same problem

Solution: https://github.com/fuatakgun/eufy_security/issues/293#issuecomment-1118093661

Solution: #293 (comment)

This does not solve it for me, I am using the docker eufy-ws container, so the details are stored there.


Why is this project blank when I run it?

please help me.I unskilled about nowinandroid

Could you tell me more details?
What does your build variants use when build?

Could you tell me more details? What does your build variants use when build?

I not know I just download this project, after by android-Studio's default build to run.
the git'branch is main.

this is my project catalogue.

This project is using room database for demo build project.
I'm not sure, but I'm thinking that room database part went something wrong.
However, I don't know what's going on your device and Build, so that It is me hard to know what happened.

该项目使用房间数据库进行演示构建项目。 我不确定，但我认为房间数据库部分出了问题。 然而，我不知道你的设备和Build上发生了什么，所以我很难知道发生了什么。
另一个期望是，您的设备看起来没有连接到互联网。 请检查互联网连接。

wooooow! yout right.  This is my mistake. I am so sorry because I do not examine log info.


IB Error with Futures - "No security definition has been found for the request"

Expected Behavior
No error should be thrown.
Actual Behavior
When using futures with IB, the following error is thrown on Saturdays (at midnight in exchange time zone):
System.Exception: No security definition has been found for the request. Origin: FindContracts: ES (FUT ES USD )

This error is caused by InteractiveBrokersBrokerage.LookupSymbols() attempting to refresh the list of contracts in the futures chain during the IB weekend period:

Connect fails silently here:
https://github.com/QuantConnect/Lean/blob/master/Brokerages/InteractiveBrokers/InteractiveBrokersBrokerage.cs#L2814
This could potentially cause "Not connected" exceptions to be thrown also with options.
FindContracts throws the error above:
https://github.com/QuantConnect/Lean/blob/master/Brokerages/InteractiveBrokers/InteractiveBrokersBrokerage.cs#L2844

Potential Solution

The IB brokerage should never attempt to connect or call other IB API methods when IsWithinScheduledServerResetTimes() is true.

Reproducing the Problem
n/a
System Information
n/a
Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues
[ ] I have provided detailed steps to reproduce the issue

The issue is still present -- IB LookupSymbols was called even if IsWithinScheduledServerResetTimes() was true:
2019-12-14T04:59:59.7939430Z TRACE:: InteractiveBrokersBrokerage.IsWithinScheduledServerResetTimes(): True
2019-12-14T05:00:00.2942790Z TRACE:: InteractiveBrokersBrokerage.LookupSymbols(): Requesting symbol list for ES ...


add delete_by_field method in RedisVectorStore

Description
The addition of the delete_by_field method provides more flexibility and functionality to the RedisVectorStore class compared to the previous delete method.  The delete method allows for deletion of nodes based on a specific document ID (ref_doc_id). This means that to delete a node, you must know its exact document ID. This can be limiting in situations where you want to delete nodes based on other criteria.  On the other hand, the delete_by_field method allows developers to delete nodes based on a specific field name and field value. This means you can delete nodes based on any field, not just the document ID. This is particularly useful when dealing with large amounts of data and needing to delete data based on specific conditions

@minglu7 we recently added delete_nodes and get_nodes to the base vector store class.
You can get/delete by node ids or filters.
Let's implement these methods instead? So far been slowly implementing these in vector stores as it comes up
(clear() was also added, to delete everything in the index)

Reference
https://github.com/run-llama/llama_index/blob/267ae33537cbda88093a97d93786bbd6034566f7/llama-index-core/llama_index/core/vector_stores/types.py#L323


FolderPicker Won't Initially Allow Selection of Starting Folder

Describe the bug
When calling PickSingleFolderAsync(), the initial folder (whatever that's set to or remembered) cannot be selected (i.e., the Select button is grayed out).
Drilling down and then up, or up and then down, through the folder tree then allows you to select that same initial folder that you couldn't initially select.
Steps to reproduce the bug
Here's the code that sets up the FolderPicker to illustrate the behavior:
var picker = new FolderPicker { SuggestedStartLocation = PickerLocationId.Desktop };

var hWnd = WinRT.Interop.WindowNative.GetWindowHandle( App.Current.MainWindow );
WinRT.Interop.InitializeWithWindow.Initialize( picker, hWnd );

picker.SuggestedStartLocation = PickerLocationId.Desktop;

_storageFolder = await picker.PickSingleFolderAsync();
ExportFolder = _storageFolder == null ? null : _storageFolder.Path;

Expected behavior
You shouldn't have to drill down/up (or up/down) to be able to select the initial starting folder.
Screenshots
No response
NuGet package version
None
Windows version
Windows 11 (22H2): Build 22621
Additional context
No response

Just to add a little information.
This is fully reproducible in a Windows API application without the Windows App SDK loaded. This would mean that this is an Windows issue and not a WinUI issue.

This seems to be a bug in PickerHost.exe of Windows.
(related SO issue https://stackoverflow.com/questions/50657601/uwp-folderpicker-select-folder-button-disabled-by-default)
But how can we tell Microsoft that this is a bug in Windows?


Don't remap line mappings

Problem: O# sets the start/end characters of a location to 0 if the location is within a line mapping directive. This is problematic in Razor, where we're attempting to implement document highlighting for the first time and need exact start/end characters.
Solution: Use the original line and character locations. This also means we need to return the non-mapped file path.
I confirmed features that go through this call path (document highlighting, find all references, go-to-impl, etc.) still work correctly with this change in both C# and Razor files. Most features still work since many do their own re-mapping behind the scenes. As a result of this change, document highlighting in Razor now works too. 🙂

Thanks for the suggestion, Filip - that makes sense. I took your feedback and excluded Razor files. I also added tests specifically for the Razor scenario. Could you take another look?

Also, it doesn't have to be addressed in this PR, but it seems that VS and VS Code have different behaviors for line mappings in *.cs files. VS doesn't respect line mappings while VS Code does - for example, when running FindAllRefs in VS Code with the following:
public class Foo
{
    public void bar() { }
}
public class FooConsumer
{
    public FooConsumer()
    {
#line 100
        new Foo().bar();
#line default
    }
}

VS Code result:

VS result:

Not sure if we want to make these consistent eventually, just food for thought.


Rails 3 Development mode crashes after the first usage of ImageMagick

 Issue by jeffdeville
Saturday Jan 08, 2011 at 06:10 GMT
Originally opened as https://github.com/rmagick/rmagick/issues/22

The error message is:
cannot remove Object::Version
I think what's happening is that in development mode, Rails tries to clear itself, and reload the environment somewhat after each page. It's this process that is dying.  (The code that actually manipulates my image works, and setting cache_classes: true avoids the problem, but makes it necessary to restart my development server constantly.
 Rails has seen many new versions and RMagick has been updated too.

Hi @vassilevsky thanks for asking, I'm not seeing this problem any more. I'm happy to see this get closed and then file a new issue if it comes back.

Yeah, just close it at this point. I'm sure someone will let you know if it's still an issue.

👍


Notifications Extension: Doesn't work on Windows

the extension doesn't work on windows.
I have notification permission, but creating a notification doesn't work.
The project and site have notification permission

are you on dnd?

and make sure you did not block the app from using notifications

No, I have checked

are you on dnd?  and make sure you did not block the app from using notifications

is the app blocked from sending notifications

I checked windows settings and it isn't blocked, but also not on the list (browser: chrome)

wait they were off oops

fixed, thanks!


Updated Code to use aiohttp instead of requests

Libraries such as requests and urllib are blocking. The use of requests shouldn't be used in an asynchronous program. This is because in case the modules gets stuck in some functioning, it could result in freezing the whole bot and making the bot dead.
This Pull Request shifts the module from requests to aiohttp. Since, discord.py already installs aiohttp as its dependency, aiohttp is not needed to install separately.
Along with this, the README.md file has been updated to show the basic usage of this module.
CHECKLIST

[x]   This has been tested before submitting the PR

It's my first time publicly releasing a package and it's great to see your cooperation in this. Thanks for explaining the issue. I'll get to work on some other aspects and will publish the changes in 1.0.6.


add date to Zulip notification subject

We sometimes have discussions in those threads; let's make sure we have a new thread for each new day (which likely means a new problem... or nobody got around to fixing things yet^^).

@bors r+ rollup

:pushpin: Commit 2902ad91deb5593dca3ee98b8bfa869747240e65 has been approved by oli-obk

:hourglass: Testing commit 2902ad91deb5593dca3ee98b8bfa869747240e65 with merge 904e66a7a6e4f2af9333b06521e47b8bf55fbae4...

:sunny: Test successful - checks-actions
Approved by: oli-obk
Pushing 904e66a7a6e4f2af9333b06521e47b8bf55fbae4 to master...


"Return back this list of words"

Summary
It struggles to return back a list of words.
(that look like a python array)
Model version:
RWKV-4-Raven-7B-v10-Eng99%-Other1%-20230418-ctx8192
Example 1
Instruction:
return back this list of words
Input:
[hello,there,how,are,you]
Output:
[Hello, There, How are you]
Example 2
Instruction:
return back this list of words
Input:
[abc,dsd,aoho,oo]
Output:
['a', 'o', 'd', 's']
Example 3
Instruction:
return back this list of words
Input:
[there,are,eleven,cars,in,the,street,2,bicycles,and,a,train,is,also,passing,nearby]
Output:
There are eleven cars in the street, two bicycles nearby, and a train passing by.

Re-tested:
RWKV-4-Raven-7B-v11-Eng99%-Other1%-20230427-ctx8192
No noticeable difference


Don't send notifications for not trusted txs

Related to https://github.com/safe-global/safe-ios/issues/2886

@fmrsabino @hectorgomezv do you think this can have be problematic for the client gateway? I can think on the lists not being refreshed
@DmitryBespalov Mobile team must also fix this on their side

From my point of view, this change shouldn't be an issue on the Client Gateway side since an untrusted transaction shouldn't trigger a cache invalidation IMHO. In fact, we're explicitly sending a hardcoded trusted=true param for the  transaction queue retrieval in the Client Gateway new implementation 🤔

Thanks for the input @hectorgomezv , good to know


Generate statuses from BCD at build time

This has been the intention from the start, but to make progress fast in the beginning we did a bunch of work manually. Now it's starting to be a nuisance, in https://github.com/web-platform-dx/web-features/pull/512 @Elchi3 notes:

I really don't want to author PRs like this one. I maintain BCD on a daily basis and also maintaining compat-data in another repo is not a good use of time. BCD has a support object with the same and up-to-date info as in this file. BCD could also export computed baseline statuses as well if needed. There is no need to record/maintain this info twice.

An added note about this: users are starting to report issues in BCD about the Baseline data shown on MDN, see https://github.com/mdn/browser-compat-data/issues/21794 (I remember closing another one, but I can't find it).


nthFibonacciNumber[javascript]

This issue is about nthFibonacciNumber.

[x] Issue Title is in form Algo/DS Name [Language].
[x] I searched or browsed the repo’s other issues to ensure this is not a duplicate.
[x] This Algo/DS is worth adding to this repository.
[ ] Assign this issue to me (I want to work on this).

[ ] I ensure that I am not already assigned to 2 or more issues.

[x] I will send my PR only after I'm assigned to this issue by any maintainer.
[x] I understand that I will be unassigned from this issue if I fail to send a PR for this within a week.

Please assign me this under contribute-a-thon.

@Vijay-K-2003 GFI 👍.

@vidit2512 Kindly assign me BellmanFord also.

Issue #723

@vidit2512 Kindly assign me BellmanFord also.

@Vijay-K-2003 Why are you mixing up these 2 issues here, if you want to talk about any other algorithm kindly discuss it in another issue and as you have told earlier, you have worked on 2 algorithms in a single PR in the master branch, this will not work.
Kindly make separate branches to work on separate issues simultaneously and then make PR.


Feature/large file uploads

No longer redraw upon every chunk sent, saves a crap load of CPU
No longer attempt to generate thumbnails for all file uploads
Enable parallel uploads for everything but Github
Make the upload progress animated
Handle rejected upload requests
Bump dropzones max file size, fangorn will handle that

Closes #3325

Will this PR address https://github.com/CenterForOpenScience/osf.io/issues/2822 ?

Yes it will.


Flutter is taking longer than expected to report its views. Still trying...

hey i am facing a problem : when i am trying to run me app for the first time on my phone
the "Flutter is taking longer than expected to report its views. Still trying..." message starts to appear and i want to know where is the problem please .
and what i meant by the first time is that : when the app starts to create the db
please want to know what is wrong and how to avoid it
what Show Up to me i the terminal ::
Launching lib\main.dart on Redmi Note 5 in debug mode...
Initializing gradle...                                              1.7s
Resolving dependencies...                                           5.5s
Running Gradle task 'assembleDebug'...
Running Gradle task 'assembleDebug'... Done                         5.1s
Built build\app\outputs\apk\debug\app-debug.apk.
Installing build\app\outputs\apk\app.apk...                        11.8s
Flutter is taking longer than expected to report its views. Still trying...
W/Activity(20834): Slow Operation: Activity com.example.iam_here_to_try/.MainActivity onCreate took 3278ms
W/iam_here_to_tr(20834): Accessing hidden method Landroid/view/accessibility/AccessibilityNodeInfo;->getSourceNodeId()J (light greylist, reflection)
W/iam_here_to_tr(20834): Accessing hidden method Landroid/view/accessibility/AccessibilityRecord;->getSourceNodeId()J (light greylist, reflection)
W/iam_here_to_tr(20834): Accessing hidden field Landroid/view/accessibility/AccessibilityNodeInfo;->mChildNodeIds:Landroid/util/LongArray; (light greylist, reflection)
W/iam_here_to_tr(20834): Accessing hidden method Landroid/util/LongArray;->get(I)J (light greylist, reflection)
I/OpenGLRenderer(20834): Initialized EGL, version 1.4
D/OpenGLRenderer(20834): Swap behavior 2
Syncing files to device Redmi Note 5...
 2,949ms (!)

🔥  To hot reload changes while running, press "r". To hot restart (and rebuild state), press "R".
An Observatory debugger and profiler on Redmi Note 5 is available at: http://<IP_ADDRESS>:53210/Xj1O8udEUT4=/
For a more detailed help message, press "h". To detach, press "d"; to quit, press "q".
I/iam_here_to_tr(20834): ProcessProfilingInfo new_methods=465 is saved saved_to_disk=1 resolve_classes_delay=8000

I also get the same error with an android emulator, but the app is working fine with ios simulator.
Thanks in advance.

hell

I also get the same error with an android emulator, but the app is working fine with ios simulator.
Thanks in advance.

Buddy. I had the same problem. The SDK version is too high and the Android version of the simulator is too low. At first, my Android simulator version was Android 6.0, but the SDK version was Android Q. Later, I switched the Android version of the simulator to the latest version and compiled it.

hey i am facing a problem : when i am trying to run me app for the first time on my phone
the "Flutter is taking longer than expected to report its views. Still trying..." message starts to appear and i want to know where is the problem please .
and what i meant by the first time is that : when the app starts to create the db
please want to know what is wrong and how to avoid it
what Show Up to me i the terminal ::
Launching lib\main.dart on Redmi Note 5 in debug mode...
Initializing gradle... 1.7s
Resolving dependencies... 5.5s
Running Gradle task 'assembleDebug'...
Running Gradle task 'assembleDebug'... Done 5.1s
Built build\app\outputs\apk\debug\app-debug.apk.
Installing build\app\outputs\apk\app.apk... 11.8s
Flutter is taking longer than expected to report its views. Still trying...
W/Activity(20834): Slow Operation: Activity com.example.iam_here_to_try/.MainActivity onCreate took 3278ms
W/iam_here_to_tr(20834): Accessing hidden method Landroid/view/accessibility/AccessibilityNodeInfo;->getSourceNodeId()J (light greylist, reflection)
W/iam_here_to_tr(20834): Accessing hidden method Landroid/view/accessibility/AccessibilityRecord;->getSourceNodeId()J (light greylist, reflection)
W/iam_here_to_tr(20834): Accessing hidden field Landroid/view/accessibility/AccessibilityNodeInfo;->mChildNodeIds:Landroid/util/LongArray; (light greylist, reflection)
W/iam_here_to_tr(20834): Accessing hidden method Landroid/util/LongArray;->get(I)J (light greylist, reflection)
I/OpenGLRenderer(20834): Initialized EGL, version 1.4
D/OpenGLRenderer(20834): Swap behavior 2
Syncing files to device Redmi Note 5...
2,949ms (!)
🔥 To hot reload changes while running, press "r". To hot restart (and rebuild state), press "R".
An Observatory debugger and profiler on Redmi Note 5 is available at: http://<IP_ADDRESS>:53210/Xj1O8udEUT4=/
For a more detailed help message, press "h". To detach, press "d"; to quit, press "q".
I/iam_here_to_tr(20834): ProcessProfilingInfo new_methods=465 is saved saved_to_disk=1 resolve_classes_delay=8000

Buddy. I had the same problem. The SDK version is too high and the Android version of the simulator is too low. At first, my Android simulator version was Android 6.0, but the SDK version was Android Q. Later, I switched the Android version of the simulator to the latest version and compiled it.

@Abdaallaa Is the issue still relevant? Can you please try it with current stable version?

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.

After updated to sdk 1.12.13, I hit this issue too

Flutter is taking longer than expected to report its views. Still trying...
I running on real device.

Hi guys, as the same code is running in iOS simulator perfectly but for android emulator it is very slow and showing this warning and error.
Note: /Users/dev/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider-1.5.1/android/src/main/java/io/flutter/plugins/pathprovider/PathProviderPlugin.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
/Users/dev/flutter/.pub-cache/hosted/pub.dartlang.org/shared_preferences-0.5.6/android/src/main/java/io/flutter/plugins/sharedpreferences/SharedPreferencesPlugin.java:25: warning: [deprecation] getFlutterEngine() in FlutterPluginBinding has been deprecated
setupChannel(binding.getFlutterEngine().getDartExecutor(), binding.getApplicationContext());
^
1 warning
✓ Built build/app/outputs/apk/debug/app-debug.apk.
Flutter is taking longer than expected to report its views. Still trying...

It happened to me too after update sdk to 1.12...

Could everyone who still has this problem please file a new issue with the exact descriptions what happens, logs and the output of 'flutter doctor -v'  please.
All system setups can be slightly different so it's always better to open new issues and reference related issues.

Launching lib\main.dart on Redmi Note 7 Pro in debug mode...
Running Gradle task 'assembleDebug'...
Note: C:\flutter.pub-cache\hosted\pub.dartlang.org\firebase_messaging-6.0.9\android\src\main\java\io\flutter\plugins\firebasemessaging\FirebaseMessagingPlugin.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: C:\flutter.pub-cache\hosted\pub.dartlang.org\path_provider-1.6.0\android\src\main\java\io\flutter\plugins\pathprovider\PathProviderPlugin.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
√ Built build\app\outputs\apk\debug\app-debug.apk.
Installing build\app\outputs\apk\app.apk...
Flutter is taking longer than expected to report its views. Still trying...
Lost connection to device.

I solved this problem by opening my plugin in Settings, where under the 'installed' tab I opened the blue text  'Plugin homepage' which was a shortcut to the  JetBrains plugin page. I noticed that there was an agreement that I had to accept, being notified in the page. It said I had to accept them to get the full functionality. I did so and my problem disappeared.


Fix template inheritance

Fix #4382
And fix XFRAME options in the process

Coverage decreased (-0.007%) to 91.06% when pulling e63911cd07b2a9204b3efd8c1e97db36e37613df on yakky:fix/template_inheritance into ab24d1b4f4ad292c92dcf6a114153ce2e5844ff0 on divio:support/3.1.x.


how i can use export default and require (webpack2)

t.js:
export default class {

}

index.js:
const cls = require("./t");

export default class PreferenceOmitDialogCondition extends cls {

}

i know that i can  require("./t").default , but i have many old code and it difficult change.

Is there a reason you are opposed to using:
import cls from './t';

@TheLarkInn I know but i have very very big project and can not change it, and i need compatibility . Is exists solution  ?

Can you change t.js? If you want to use CommonJS require, you'll want to also use CommonJS exports. This will allow you to require('./t'):
t.js:
module.exports = class {
}

Otherwise, using Babel and a plugin like add-module-exports] could help.

@also I can't change t.js it is as blackbox. This plugin not work on this code:
LinkUtils.js
export default class {
    static getObjectParamsFromUrl() {
       ...code
    }
}

RouterHashParams:
import LinkUtils from "./common/LinkUtils";
export default class RouterHashParams {

    constructor() {
        let linkParams = LinkUtils.getObjectParamsFromUrl();
    }
}

because after build i have:
RouterHashParams:
var __WEBPACK_IMPORTED_MODULE_2__common_LinkUtils__ = __webpack_require__(28);
  	class RouterHashParams {

	    constructor() {
	        let linkParams = __WEBPACK_IMPORTED_MODULE_2__common_LinkUtils__["a" /* default */].getObjectParamsFromUrl(); <<<< "a" overridden by  exports["default"]
           ....

LinkUtils
/* harmony default export */ exports["a"] = class {
	    static getObjectParamsFromUrl() {
            }
   ...
module.exports = exports["default"]; // <<<<<<<<<------- override exports

Why after build i have exports["a"] and exports["default"] ?

Don't mix babel es6 module handling with webpacks. webpack allows to mix CommonJs and ES6 modules this way:
// es6.js
import something from "./commonjs";

export default "xyz";
export var abc = "abc";

// commonjs.js
var xyz = require("./es6").default;
var abc = require("./es6").abc;

module.exports = "something";

Don't use the add-module-exports plugin.
PS: exports.a is used instead of exports.default when a es6 module is only imported via es6 imports. webpack mangles the export names.

@sokra  Yes, i know, but how i can solve this problem if i have code ashttps://github.com/webpack/webpack/issues/2631#issue-159642878 and i cannot change him ?

The code is wrong. Change it.

I'm having a related problem. I have a module that looks like this (note, I'm using Babel's transform-class-properties plugin, hence the class properties syntax):
import { observable } from 'mobx';

class AppStateStore {
  @observable firstName = 'hi';
  @observable lastName = '';
  @observable phoneNumber = '';
  @observable mail = '';
  @observable city = '';
  @observable referralCode = '';
  @observable backgroundCheckOk = false;

  constructor() {}
}

let appStateStore = new AppStateStore();

//module.exports = appStateStore;
export default appStateStore;

Then I shim the module using ProvidePlugin like so:
plugins: [
  new webpack.ProvidePlugin({
    'app.state': 'stores/app_state.js'
  })
]

Then when I call app.state, I get an object that has a property called default that has all of the properties like firstName, lastName, etc. But that's wrong, there shouldn't be any property called default. app.state should simply point to the instance that I created.
On the other hand, when I use commonJS-style exporting (i.e., module.exports = appStateStore), it works perfectly.
What gives?


To add flag to show source documents #64 solved

source document flag done kindly check nd merge

Thanks for your contribution @Priyamakeshwari 🌟


add marc and move bharathi-tenneti to sdk-emeritus-approvers

Looks like we need to get @marc-obrien added to the org. It's probably best to do that before merging in case that messes up any automation that exists around the OWNERS file (e.g. being added to various CNCF aliases).
NOTE: Marc has been a member of the Red Hat Operator Framework team for over a year and is grandfathered into the GitHub organization and the SDK contributor membership.

/restest

/verify-owners

/verify-owners