Parsing error: Illegal import declaration

I'm getting the error Parsing error: Illegal import declaration
I'm using ES6 imports.
When I first run lint, or run it manually I don't get the error, it's only when I save and it's run with my watch task. I was using 0.15 when I first got the error, upgraded to 1.0 and still get it.
This seems to maybe be related to https://github.com/eslint/eslint/issues/2112 and https://github.com/adametry/gulp-eslint/issues/39, but none are helping my issue.
I'm not sure where the error comes from as I haven't changed my eslintrc or babel setup since I first started my project a few months ago. So I'm guessing there is some dependency change causing this issue?
Any ideas how to fix?
[09:07:46] ESLintError in plugin 'gulp-eslint'
Message:
    Parsing error: Illegal import declaration

lintrc:
{
  "ecmaFeatures": {
    "arrowFunctions": true,
    "blockBindings": true,
    "classes": true,
    "destructuring": true,
    "modules": true,
    "objectLiteralComputedProperties": true,
    "objectLiteralShorthandMethods": true,
    "objectLiteralShorthandProperties": true,
    "templateStrings": true,
    "jsx": true
  },
  "env": {
    "browser": true,
    "node": true,
    "jasmine": true
  },
  "plugins": [
    "react"
  ],
  "rules": {
    "camelcase": 0,
    "no-alert": 0,
    "no-else-return": 1,
    "strict": [2, "global"],
    "brace-style": [2, "stroustrup"],
    "comma-style": [1, "last"],
    "no-lonely-if": 1,
    "no-multi-spaces": 0,
    "no-mixed-requires": 2,
    "no-underscore-dangle": 0,
    "no-var": 2,
    "no-duplicate-case": 0,
    "no-func-assign": 0,
    "quotes": [1, "single", "avoid-escape"],
    "space-before-function-paren": [1, "never"],
    "space-after-keywords": [1, "always"],
    "space-before-blocks": [1, "always"],
    "space-in-brackets": 0,
    "space-in-parens": 0,
    "spaced-comment": 0,
    "new-cap": 0,
    "react/jsx-uses-react": 1,
    "react/jsx-uses-vars": 1,
    "react/prop-types": 1,
    "react/react-in-jsx-scope": 1,
    "new-parens": 0,
    "no-use-before-define": 0,
    "no-shadow": 0
  },
  "globals": {
    "__BROWSER__": false,
    "__SERVER__": false,
    "__DEV__": false,
    "__PROD__": false,
    "__": false,
    "Promise": true,
    "casper": false,
    "jest": false
  }
}

My package.json includes:
    "babel-core": "^4.7.0",
    "babel-eslint": "^4.1.3",
    "gulp-eslint": "^1.0.0",

My lint and watch tasks:
// var $ = require('gulp-load-plugins')();
gulp.task('lint', function () {
  return gulp.src(['./app/scripts/**/*.{js, jsx}'])
    .pipe($.eslint())
    .pipe($.eslint.format())
    .pipe($.eslint.failOnError());
});

gulp.task('watch', function() {
  gulp.watch(app + 'images/**/*.{png,jpg,jpeg,gif,svg}', ['images']);
  gulp.watch(app + 'stylus/**/*.styl', ['styles']);
  gulp.watch(app + 'index.mustache', ['html']);
  gulp.watch(app + 'scripts/**/*.jsx', ['scripts', 'lint']);
  gulp.watch(app + 'scripts/**/*.js', ['scripts', 'lint']);
});

Unfortunately, I haven't been able to reproduce this issue. So, here are some wild guesses:

Syntax error: Is the import nested? If import is not at the top level of a module, the espree parser produces the error your seeing.
Wrong parser: I see you have espree's "ecmaFeatures":{"modules":true} option, but are you trying to use babel-eslint? If so, set the parser with "parser":"babel-eslint". The babel-eslint parser may provide a more helpful error message.
Stale node_modules: Try deleting your node_modules directory and reinstalling your package dependencies.
Unexpected app value: Ensure that app + 'scripts/**/*.js' produces the expected path.

If none of the above resolve the issue, provide a gist or repo that demonstrates the issue so I can get an exact copy.
On another note: you may want to switch to using failAfterError so you can see the lint report before the the "lint" task fails.

@benrlodge what you do?

@Xurma2 @benrlodge  Wrong parser was the problem. "parser": "babel-eslint" did fix the problem.


build orbs are not fresh

Latest CI build succeeded, but build orb is still showing red.   I think I may have messed up setting them up.

Fixed on the kokoro side.
b/62478133


How to use poetry with url without version?

boto3 = {url = "https://github.com/boto/boto3/archive/31a8a3d7bcd021aadceba63d6f207a3a61c58aac.zip"}

poetry lock is successful

# This file is automatically @generated by Poetry 1.8.2 and should not be changed by hand.

[[package]]
name = "boto3"
version = "1.35.13"
description = "The AWS SDK for Python"
optional = false
python-versions = ">= 3.8"
files = [
    {file = "31a8a3d7bcd021aadceba63d6f207a3a61c58aac.zip", hash = "sha256:166f093e1d7905b6e116f413f22780151c010f916092772ee1c19e2def949517"},
]

[package.dependencies]
botocore = ">=1.35.13,<1.36.0"
jmespath = ">=0.7.1,<2.0.0"
s3transfer = ">=0.10.0,<0.11.0"

[package.extras]
crt = ["botocore[crt] (>=1.21.0,<2.0a0)"]

[package.source]
type = "url"
url = "https://github.com/boto/boto3/archive/31a8a3d7bcd021aadceba63d6f207a3a61c58aac.zip"

[[package]]
name = "botocore"
version = "1.35.13"
description = "Low-level, data-driven core of boto 3."
optional = false
python-versions = ">=3.8"
files = [
    {file = "botocore-1.35.13-py3-none-any.whl", hash = "sha256:dd8a8bb1946187c8eb902a3b856d3b24df63917e4f2c61a6bce7f3ea9f112761"},
    {file = "botocore-1.35.13.tar.gz", hash = "sha256:f7ae62eab44d731a5ad8917788378316c79c7bceb530a8307ed0f3bca7037341"},
]

[package.dependencies]
jmespath = ">=0.7.1,<2.0.0"
python-dateutil = ">=2.1,<3.0.0"
urllib3 = {version = ">=1.25.4,<2.2.0 || >2.2.0,<3", markers = "python_version >= \"3.10\""}

[package.extras]
crt = ["awscrt (==0.21.2)"]

[[package]]
name = "jmespath"
version = "1.0.1"
description = "JSON Matching Expressions"
optional = false
python-versions = ">=3.7"
files = [
    {file = "jmespath-1.0.1-py3-none-any.whl", hash = "sha256:02e2e4cc71b5bcab88332eebf907519190dd9e6e82107fa7f83b1003a6252980"},
    {file = "jmespath-1.0.1.tar.gz", hash = "sha256:90261b206d6defd58fdd5e85f478bf633a2901798906be2ad389150c5c60edbe"},
]

[[package]]
name = "python-dateutil"
version = "2.9.0.post0"
description = "Extensions to the standard Python datetime module"
optional = false
python-versions = "!=3.0.*,!=3.1.*,!=3.2.*,>=2.7"
files = [
    {file = "python-dateutil-2.9.0.post0.tar.gz", hash = "sha256:37dd54208da7e1cd875388217d5e00ebd4179249f90fb72437e91a35459a0ad3"},
    {file = "python_dateutil-2.9.0.post0-py2.py3-none-any.whl", hash = "sha256:a8b2bc7bffae282281c8140a97d3aa9c14da0b136dfe83f850eea9a5f7470427"},
]

[package.dependencies]
six = ">=1.5"

[[package]]
name = "s3transfer"
version = "0.10.2"
description = "An Amazon S3 Transfer Manager"
optional = false
python-versions = ">=3.8"
files = [
    {file = "s3transfer-0.10.2-py3-none-any.whl", hash = "sha256:eca1c20de70a39daee580aef4986996620f365c4e0fda6a86100231d62f1bf69"},
    {file = "s3transfer-0.10.2.tar.gz", hash = "sha256:0711534e9356d3cc692fdde846b4a1e4b0cb6519971860796e6bc4c7aea00ef6"},
]

[package.dependencies]
botocore = ">=1.33.2,<2.0a.0"

[package.extras]
crt = ["botocore[crt] (>=1.33.2,<2.0a.0)"]

[[package]]
name = "six"
version = "1.16.0"
description = "Python 2 and 3 compatibility utilities"
optional = false
python-versions = ">=2.7, !=3.0.*, !=3.1.*, !=3.2.*"
files = [
    {file = "six-1.16.0-py2.py3-none-any.whl", hash = "sha256:8abb2f1d86890a2dfb989f9a77cfcfd3e47c2a354b01111771326f8aa26e0254"},
    {file = "six-1.16.0.tar.gz", hash = "sha256:1e61c37477a1626458e36f7b1d82aa5c9b094fa4802892072e49de9c60c4c926"},
]

[[package]]
name = "urllib3"
version = "2.2.2"
description = "HTTP library with thread-safe connection pooling, file post, and more."
optional = false
python-versions = ">=3.8"
files = [
    {file = "urllib3-2.2.2-py3-none-any.whl", hash = "sha256:a448b2f64d686155468037e1ace9f2d2199776e17f0a46610480d311f73e3472"},
    {file = "urllib3-2.2.2.tar.gz", hash = "sha256:dd505485549a7a552833da5e6063639d0d177c04f23bc3864e41e5dc5f612168"},
]

[package.extras]
brotli = ["brotli (>=1.0.9)", "brotlicffi (>=0.8.0)"]
h2 = ["h2 (>=4,<5)"]
socks = ["pysocks (>=1.5.6,!=1.5.7,<2.0)"]
zstd = ["zstandard (>=0.18.0)"]

[metadata]
lock-version = "2.0"
python-versions = "3.11.9 || 3.12.4"
content-hash = "936bf419505533623b19f273b900d813fd26820d7c1dd5c876d497ea858f71b7"

However lock generation failed
Traceback (most recent call last):
  File "/private/.../bin/external/rules_pycross~/pycross/private/tools/poetry_translator.runfiles/_main/../rules_pycross~/pycross/private/tools/poetry_translator.py", line 281, in <module>
    main(parse_flags())
  File "/private/.../bin/external/rules_pycross~/pycross/private/tools/poetry_translator.runfiles/_main/../rules_pycross~/pycross/private/tools/poetry_translator.py", line 243, in main
    lock_set = translate(args.project_file, args.lock_file)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/private/.../bin/external/rules_pycross~/pycross/private/tools/poetry_translator.runfiles/_main/../rules_pycross~/pycross/private/tools/poetry_translator.py", line 125, in translate
    pinned_package_specs[pin] = parse_constraint(pin_info["version"])
                                                 ~~~~~~~~^^^^^^^^^^^
KeyError: 'version'

I guess this format isn't currently supported. Is there a way to include a version parameter along with the URL to satisfy it?
The translator looks at pyproject.toml to get the set of pinned dependencies - i.e., the roots used in a later step that computes a transitive closure. The actual lock file can contain multiple versions of a single package in some uncommon scenarios, so the translator doesn't look there for the version. But we could make a change to have it defer to the version in the lock file if pyproject.toml doesn't provide one and poetry.lock only has a single version, which I think would handle most scenarios.

I gave a shot - https://github.com/jvolkman/rules_pycross/compare/main...chulkilee:poetry-url?expand=1
Done

read package level instead of file level version

Not working

the result does not have any select for alias..

    _fastapi_0_113_0_deps = [
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>    ]

    native.alias(
        name =<EMAIL_ADDRESS>        actual = select({
        }),
    )

    pycross_wheel_library(
        name =<EMAIL_ADDRESS>        deps = _fastapi_0_113_0_deps,
        wheel =<EMAIL_ADDRESS>    )

get_package_sources_by_environment returns no candidate since pip LinkEvaluator does not handle archives.

I also just ran into this, except that we have some entries that looks like this:
random-project = { git = "https://github.com/owner/repo.git", rev = "random-git-hash"}


[Refactor] Changed all Colors.clear to .clear. No change in actual color

I didn't see a need to have a color called clear when we already have .clear.

If we keep it, can you add a comment to the color definition to explain why?

I don't know why it was added, but keeping it might be better. Say we want to debug colors and figure out where/if it is use in a certain screen? We can override the value to .red with alpha and it'll jump out.

We would need to split this into two. There is a clear for borders and clear for backgrounds. I'd split them into clearBackground and clearBorder. @hboon

I don't know why it was added, but keeping it might be better. Say we want to debug colors and figure out where/if it is use in a certain screen? We can override the value to .red with alpha and it'll jump out.

the idea was to keep colors in single namespace, Colors as it was, its easier to track actual used colors and yes, override them when needed.

I don't know why it was added, but keeping it might be better. Say we want to debug colors and figure out where/if it is use in a certain screen? We can override the value to .red with alpha and it'll jump out.
We would need to split this into two. There is a clear for borders and clear for backgrounds. I'd split them into clearBackground and clearBorder

Does this make sense?

@eviltofu Yes, this works; bottom line is to not replace them with UIColor.clear

Remember to update PR title and commit messages too.

Needs approval @hboon


[HELP] Boot multi-core on FVP A510, but the code still run "while (up_testset(lock) == SP_LOCKED)"  loop in spin_lock()

Description
Hi everyone!
I want to boot multi-core on FVP A510. After cpu1 run to WFI instruction, cpu0 run to "while (up_testset(lock) == SP_LOCKED)"  loop. This flow is: sched_unlock() (in nx_start()) -> nxsched_merge_pending() -> nxsched_add_readytorun() -> "DEBUGVERIFY(up_cpu_pause(cpu));" -> "spin_lock(&g_cpu_paused[cpu]);" -> spin_lock() -> "while (up_testset(lock) == SP_LOCKED)" in spin_lock(), then the code is still run in this loop. the input parameter "cpu" of up_cpu_pause() is 1 because of the task in “btcb” belong to cpu1 but the code run on cpu0 currently, and the cpu1 is in idle loop. So, it seem that cpu0 is waiting cpu1 to end its task but cpu1 task is still running. I don't know how to solve this issue and I don't konw the task scheduler how to work correctly in this case
Thank you very much!

Verification

[X] I have verified before submitting the report.

@hujun260

@lzc1001
You are using an older version of the code. In the latest community implementation, the synchronous pause function has been removed. It is recommended that you synchronize with the latest community code and try again.
Based on the problem you described, the issue seems to be that CPU1 is unable to respond to interrupts.

The old version can also run well,  but the new version will have significantly improved performance, especially in SMP.

@hujun260 @anchao OK! Thank you very much!
I solve this issues by define "CONFIG_ARCH_SET_VMPIDR_EL2" in configuration file. The GIC was initilized incorrectly because the value of MPIDR_EL1 is incorrect in EL1. And it would casue an incorret cpuid and initilized GIC redistributor incorrectly. So, When I set VMPIDR_EL2 in EL2, this isuse is solved, hhh✌

Hi, I have another question for function "int arm64_gic_send_sgi()". I find that read vaule of GICR_IGROUP0 is 0x0 in non-secure EL1, but the value is 0xDFFF00FF in secure and the value(0xDFFF00FF) is set by ARM TF-A in EL3. So, Is the "if " judgement condition reasonable when the core run in non-secure EL1?

Those two pictures are from Learn the architecture - Generic Interrupt Controller v3 and v4, Overview

There are modifications to arm64_gic_send_sgi in the latest code. Please check it out first.

@hujun260 I download the latest code(commit<PHONE_NUMBER>86e940fbb29a9a524de9b9e063d3e0 (HEAD -> master, origin/master, origin/HEAD)), but the function "arm64_gic_send_sgi" is same as my location code(commit 7a865b247969a9dbc06eddcaf58c59a14dd05d6d (HEAD -> releases/12.6, tag: nuttx-12.6.0-RC1, origin/releases/12.6)), I'm just curious about this issue. hhh


opentracing: remove legacy open tracing extension

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes: inline
Fixes https://github.com/envoyproxy/envoy/issues/27401
Fixes https://github.com/envoyproxy/envoy/issues/34321

/docs


Cannot be switch off

🐛 Describe the bug

the Humidifier cannot be switch off. Please refer to the error message. It said to report it to the author of the "jcihitachi_tw"
Environment Information
Core
2024.5.5
Supervisor
2024.05.1
Operating System
12.3
前端
20240501.1

In our bug report issue template, it clearly states "search previous issues before opening a new issue." IIRC.

Sorry, I did check with all the closed issues before I raise a new issue. I could not find a similar issue.
In face, I did a double check on all the closed issues right now, but still could not find a similar issue.
Please help to give me a direction on rectify the problem. Many thanks.

Sorry again, after did a search, I did find a similar issue.
I will try to change the line 246 to "self.schedule_update_ha_state()", and see how it go.
Anyway, thanks a lot.

That is not the right way to fix. Why don't you even bother with just updating the integration?

I'm currently using version 1.6.0. Just check and realize that there is a new release v1.7.1
I will update my system to 1.7.1 now
Thank you very much


✨ Add needimport caching and needs_import_cache_size configuration

Currently based on top of #1292

This PR introduces "lazy and size-bounded" caching for the reading of needs.json in the needimport directive.
This reads/writes to an in-memory cache, keyed on the path and mtime,
and is bounded by the needs_import_cache_size (configurable by the user),
which sets the maximum number of needs allowed in the cache,
to ensure we do not have large increases in build memory usage.

Note, in #1148 there was discussion of "centralised, pre-caching",
however, that is problematic because:

It means all import sources have to be read in for every build/re-build, irrespective of whether they actually may be used
this can introduce a noticeable increase in memory usage and time for re-builds
for parallel builds, all of this data will be copied to every process, irrespective of whether that processes actually uses it, again meaning potentially large multipliers of memory usage

Hi @chrisjsewell , first of all thanks for tackling this topic, even before I had conducted the performance measurement :-)

Note, in #1148 there was discussion of "centralised, pre-caching", however, that is problematic because:
1. It means all import sources have to be read in for every build/re-build, irrespective of whether they actually may be used

How do we handle that the needs.json import source has changed? Sphinx will not consider the importing document changed, so in this case do we need to trigger a full re-build? Or does sphinx-needs have a way to handle this?
Is this maybe a general problem of needimport?

How do we handle that the needs.json import source has changed? Sphinx will not consider the importing document changed

It informs sphinx of the documents dependency on the file: https://github.com/useblocks/sphinx-needs/blob/fcf40f8efdd87faab9e1ba00c4d8b6e3d8652c3d/sphinx_needs/directives/needimport.py#L144
so yes sphinx will check if it's mtime is changed and re-build all dependant documents


[1.20.1] Client crash on adding this mod to my modpack.

https://gist.github.com/ProsperCraft/f768b9463c655d7e63e3c2c60d5f8c7e

This was an issue with compatibility in Thermoo that was fixed almost 2 months ago. Update Thermoo and it'll work.


Add changeWidth param to allow animating width

Previously it was only possible to animate the height of the component.
This adds the possibility to animate width together with height.
Width change animation can be enabled by passing in changeWidth: true
in props for the component.
This change is backwards compatible.

Thanks for contributing this. I will merge it soon and publish as is, and then I will also be releasing yet another rewrite of the component to solve some other issues (which will also include height animation). I want to release it all in one go, and I need to do a bit more testing on the rewrite before it's ready.


sim: To avoid system calls being interrupted when use host api

Summary
To avoid system calls being interrupted when use host api
Impact
sim/posix api
Testing

Please rebase


weight converter

Hello,
i find the converter for  convert caffe weight to tensorflow . can use this weight in the keras.?

It is possible but the current VGG16/VGG19 models have used ImageNet pre-trained weights already. I don't see it is necessary to replace them with caffe weights.

i mean FC-VGG16 in caffe .


Move/Copy doesn't work on sitemap flat view

How to reproduce

Visit index.php/dashboard/sitemap/explore
Click on a page and select Move/Copy
Click on any page of the popup.

[Tested on <IP_ADDRESS>, <IP_ADDRESS>, 8.4.4, develop branch]

@aembler
Any thoughts about solving this issue?
This was a request from our client. And we would like to apply the patch for him.


Add merge_group triggers

See https://github.blog/changelog/2023-02-08-pull-request-merge-queue-public-beta/
Checklist

[ ] I have added tests
[ ] I have updated the docs and cheatsheet
[ ] I have not broken the cheatsheet

Closing until https://github.com/orgs/community/discussions/46757#discussioncomment-4934046 is addressed

Taking another swing at this one now that dependabot is spamming us and looks like there's a workaround for CodeQL issue

hmm that didn't work.  trying again; need another quick look @AndreasArvidsson


Installer pipeline is now broken when all architectures is passed

Since https://github.com/adoptium/installer/commit/b7d100c6164d0b60a6cc3c3b39b5c059c7ae2559 was landed we have now broken the ability to build the Debian job for all architectures.
I've already fixed one issue via https://github.com/adoptium/installer/commit/3ea74367542f1c25d315d0e241d062ff8f788434 but the job will not automatically create several child jobs for each available Debian architecture which renders it useless.
As a workaround for now I'll run the Debian job for each architecture that we need individually.

is the problem/error from https://ci.adoptopenjdk.net/job/adoptium-packages-linux-pipeline_new/ or https://ci.adoptopenjdk.net/job/adoptium-packages-linux-pipeline?

with the _new pipeline

related to https://github.com/adoptium/installer/issues/459

think i finally understand the problem.
when we select "all" as ARCH it wont work for Debian,  because:
the label will be set to"dockerBuild&&linux&&x64" which only works for x86_64 not the other ARCH
i will draft an PR to fix this one.
for the time being it is best to run each ARCH per build (i.e not use all)

the build of deb "dpkg-buildpackage" does not really take in different ARCH, it only use the host arch to build package, this probably is the reason why we have to set label for the runs.


Install SSH Key: Add "More information" link

Before

After

We can rely on docs.microsoft.com to handle changes to the path and if they ever change the host I trust them to redirect.


Form issue on Row level security

Bug description
The form style is showing as broken
How to reproduce the bug
Go to create new rule on RLS
Screenshots/recordings

Superset version
master / latest-dev
Python version
3.10
Node version
16
Browser
Chrome
Additional context
No response
Checklist

[X] I have searched Superset docs and Slack and didn't find a solution to my problem.
[X] I have searched the GitHub issue tracker and didn't find a similar bug report.
[X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

resolution : 1300x600  or 1300x500  (responsive)


Documentation Website Has Broken Links: I Can't Submit Pull Requests!

On each page of Docs.Manim.Community there is a Pencil icon if editing needs be for that page.
But now if I click the Pencil for any page it gives a 404!

Fix it!

Thanks for letting us know, I wasn't aware our documentation theme has added an edit button feature.
The problem is: the way this is currently implemented does not work correctly with documentation pages generated from docstrings via autodoc: In the example you gave above, https://docs.manim.community/en/stable/reference/manim.mobject.geometry.arc.Circle.html tries to link to (after setting up things correctly) https://github.com/ManimCommunity/manim/edit/main/docs/source/reference/manim.mobject.geometry.arc.Circle.rst, so it basically is looking for the corresponding document in our docs/source directory.
However, it cannot be found there as this page is autogenerated from the docstring of the Circle class in https://github.com/ManimCommunity/manim/blob/44f78f1dfdd7498542869fc06bb39619f2b2d57b/manim/mobject/geometry/arc.py#L467-L490
We'll have to disable the feature for now.

Huh? But what do we do if we have edits to make?
Many pages have properties left unexplained/blank.
Important properties not even mentioned in the Doc pages.
Text(...) has attributes not explained in the Doc.
Also, Circle(...) lacks the important attribute stroke_width which works, is a crucial parametre but never mentioned it is possible to customise.

Huh? But what do we do if we have edits to make?

You can still edit the documentation of classes and methods, you just need to navigate to the corresponding page manually on GitHub. The redirect from the documentation page to GitHub does not work; editing the docstrings works just normally.

Text(...) has attributes not explained in the Doc. Also, Circle(...) lacks the important attribute stroke_width which works, is a crucial parametre but never mentioned it is possible to customise.

stroke_width should be documented as an argument of VMobject in https://docs.manim.community/en/stable/reference/manim.mobject.types.vectorized_mobject.VMobject.html#manim.mobject.types.vectorized_mobject.VMobject. With how the documentation is setup currently, you often have to look for arguments in the base classes of the class you are interested in. (Not saying I particularly like this system, but that is how it currently is.)

O.K.


First clip doesn't load

Hi,
I'm using the Frigate Lovelace card. Since the latest update the Lovelace card doesn't show the 1st (latest) video anymore.
I'm using the card in the "most recent clip" view.

I need to
Android HA app:
Swipe to the previous video and then swipe back to the newest video to be able to watch the newest video.
Firefox browser:
Navigate to another dashboard tab and go back to my "security" tab to be able to watch the newest video.
or
Choose to edit the HA dashboard > Then it showes the video correctly
Chrome browser:
Navigate to another dashboard tab and go back to my "security" tab to be able to watch the newest video.
or
Choose to edit the HA dashboard > Then it showes the video correctly
I did think about the browser cache and history wipe.
No error(s) logs in the HA log
No error(s) in the Frigate log
Yesterday I rebuild all of the Frigate installation:
Deleted HA add-on
Deleted HA integration > Wich the Lovelace card is comming from
Deleted all Frigate related files via the file editor
Deleted all Media
Media > Frigate (Integration folder)
Media > My Media > frigate (Add-On folder)
Deleted the Lovelace card and builded it back up via the GUI
  - type: custom:frigate-card
    cameras:
      - camera_entity: camera.frigate_cam1
      - camera_entity: camera.frigate_cam2
      - camera_entity: camera.frigate_cam3
    view:
      default: clip
      update_force: true
      scan:
        show_trigger_status: true
    menu:
      style: outside
      buttons:
        media_player:
          enabled: false
        timeline:
          enabled: false
        live:
          enabled: false
        snapshots:
          enabled: false
    media_viewer:
      controls:
        title:
          mode: none
        thumbnails:
          mode: none
        timeline:
          mode: below
          window_seconds: 28800
    media_gallery:
      controls:
        thumbnails:
          show_favorite_control: false
          show_timeline_control: false
          show_download_control: false
        filter:
          mode: none

Just to make sure I understand, the most recent clip doesn't work, but all the others do? Is this the case no matter how recently the clip was? i.e. even if it was hours ago, the first clip will never work?

Hi,
That is correct.
I have 3 camera's configured in the card. Only the first (default) camera clip acts this way.

I have 3 camera's configured in the card. Only the first (default) camera clip acts this way.

And can you view the same clip that won't load via the HA media browser? (i.e. outside the card, but inside the HomeAssistant Media sidebar tab)

In the media browser I see the same issue. The first clip doesn't load

I have same problem.
In browser console, I have an error, when click on first clip:
96996.w7vKRby48d0.js:1 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'KeySystemFormats')
    at 96996 (96996.w7vKRby48d0.js:1:283711)
    at Function.c (bootstrap:19:32)
    at async p.value (ha-hls-player.ts:112:11)
96996 @ 96996.w7vKRby48d0.js:1
c @ bootstrap:19
log-message.ts:37

GET https://xxx/unknown/webpack/bootstrap 404 (Not Found)

Hi dermotduffy.
I did report it upstream first ;)
https://github.com/blakeblackshear/frigate/issues/9827
I think it is not a Frigate Add-on media browser problem because in the media browser of the add-on I do not have issues.
I have 2 media browser directories:

From the Frigate Add-on: Media > My Media > frigate
From this Frigate integration: Media > Frigate

Media directory number 1 does not show this behaviour. Some clips are split in 2 peaces inside the directory.
The most recent clip (recording) of Media directory number 2 is showing the same behaviour as the Lovelace card.

Frigate Add-on 0.13.1

I'm sorry you are being bounced around! On the other issue you mentioned the card and not that this ALSO doesn't work in the stock HA media browser without the card being involved.

I think it is not a Frigate Add-on media browser problem because in the media browser of the add-on I do not have issues.

I think the issue can only be with one of these (none of which are the Frigate add-on, and none of which are the card):

Frigate itself ... which passes the video to ...
... the Frigate integration ... which plays through ...
... the video player that resides in the HASS frontend to play videos

Put simply: You could uninstall the card entirely, and it still wouldn't play in the HA media browser. Can't be the card ;-)

Hi,
Correct me if I am wrong but your integration provides a media directory.
In that directory I can reproduce the issue. In the Frigate Add-on directory I can't

Correct me if I am wrong but your integration is creating a media directory. In this directory I can reproduce the issue.

That's the integration, this repo is the card.

Swipe to the previous video and then swipe back to the newest video to be able to watch the newest video.

This indicates that it is not a backend issue right? Because the same request works after updating the ui?

This indicates that it is not a backend issue right? Because the same request works after updating the ui?

I missed that, great point! However, there's must be more than just the card going on here since the issue happens in the stock media browser without the card at all.
@woempiej  I wonder if you try to open it in the HA media browser (and it fails), but then you try to open it a second time, does it succeed? [i.e. are we seeing the same symptoms in the media browser as in the card].
Both the card and HA share the same video player code, so it could be that. Or I guess it could be that somehow something on the backend is returning different data on the first and subsequent requests?

Hi,
Here a small tutorial of my actions to try to reproduce

@dermotduffy Yes the second time in the media browser there is no issue.
Because of this, I thought it was a problem just with the default camera in the card but it is not!
When I log out of HA en close the browser > Login again ant follow the above tutorial to another camera > It is showing the same behaviour > Latest recording isnt't playing

How strange. Thanks for the walk-thru screenshot. For the record, I can do the same, go to the media browser, choose Recordings, choose a camera, choose the latest available hour -- it will play first time every time. I'm on HA 2024.1.3 (slightly  older than you), I can try to upgrade later to see if perhaps something changed in HA itself?
Suggestion: In one window, navigate to "Logs" in your Frigate instance, and choose "Nginx" on the top-right. In another window, repeat your steps above (with the first request than fails, and the second that succeeds), then paste in what new log lines are created. Interesting ones likely contain something like "GET /vod/2024-02/..." [these are the requests HA is making to your backend, I'm curious if both requests are being received at all].

Looks like both requests are served okay from the backends perspective (both http status 200), although the response sizes look small compared to my testing, but that could be a red herring.
@woempiej Do you get any messages in your Javascript console (press F12 in Chrome), when you attempt to play the video from the media browser?

Anyone have any working solutions? I am experiencing the exact same issue as described above

Hi all,
Issue is fixed in HA 2024.3.0

Can confirm that 2024.3 has fixed this issue


Fix typo in man page.

👍🏻

@homu r+

@bundlerbot r+

@indirect what's up with that?

@segiddins I set github to require travis to pass, and now github returns a 422 when bundlerbot tries to fast forward. 😬  I guess I'll just remove the travis requirement?

@bundlerbot retry

great, I don't know how to get out of this failure state >_>

Yeah, shouldn't need it since we use bundlerbot


Add support for python3.9

Signed-off-by: yzdann<EMAIL_ADDRESS>

Thanks!


Unable to connect to AKS cluster with 'az aks get-credentials --resource-group mygroup --name mycluster

Azure CLI version: 2.44.1
Powershell command window in Terminal, attempted with both admin and non-admin mode.
Repo:
az login
az set account --subscription 'mysubscriptionid'
az aks get-credentials --resource-group mygroup --name mycluster
Error:
az aks get-credentials --resource-group MyResourceGroup --name akstestcluster
The command failed with an unexpected error. Here is the traceback:
[Errno 13] Permission denied: 'C:\Users\larrywa\.kube\config'
Traceback (most recent call last):
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 233, in invoke
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 663, in execute
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 726, in _run_jobs_serially
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 697, in _run_job
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 333, in call
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/acs/custom.py", line 1118, in aks_get_credentials
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/acs/custom.py", line 1250, in _print_or_merge_credentials
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/acs/custom.py", line 1214, in merge_kubernetes_configurations
PermissionError: [Errno 13] Permission denied: 'C:\Users\larrywa\.kube\config'
To check existing issues, please visit: https://github.com/Azure/azure-cli/issues
To open a new issue, please run az feedback
I did not try older versions of az cli.

route to CXP team

@larrywa Can you please check if you have admin privileges to access the config file over here C:\Users\<username>\.kube\ ?

@larrywa Please let us know if you still having issues and needs help.

Sorry, it took so long to get a response, I forgot I even had a problem.

Hi @larrywa / @SaurabhSharma-MSFT ,
I've faced similar error like your case.
Could share what is steps required on resolving this issue?
Error Logs:
17:53:38  + az account set --subscription ****
17:53:39  + az aks get-credentials --resource-group RG-AKS-EXP-BI-DEV-WEU-001 --name AKS-EXP-BI-DEV-WEU-001
17:53:41  ERROR: The command failed with an unexpected error. Here is the traceback:
17:53:41  ERROR: [Errno 30] Read-only file system: '/.kube/config'
17:53:41  Traceback (most recent call last):
17:53:41    File "/usr/lib64/az/lib/python3.9/site-packages/knack/cli.py", line 233, in invoke
17:53:41      cmd_result = self.invocation.execute(args)
17:53:41    File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 663, in execute
17:53:41      raise ex
17:53:41    File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
17:53:41      results.append(self._run_job(expanded_arg, cmd_copy))
17:53:41    File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 697, in _run_job
17:53:41      result = cmd_copy(params)
17:53:41    File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 333, in __call__
17:53:41      return self.handler(*args, **kwargs)
17:53:41    File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
17:53:41      return op(**command_args)
17:53:41    File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/command_modules/acs/custom.py", line 1280, in aks_get_credentials
17:53:41      _print_or_merge_credentials(
17:53:41    File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/command_modules/acs/custom.py", line 1403, in _print_or_merge_credentials
17:53:41      with os.fdopen(os.open(path, os.O_CREAT | os.O_WRONLY, 0o600), 'wt'):
17:53:41  OSError: [Errno 30] Read-only file system: '/.kube/config'
17:53:41  To check existing issues, please visit: https://github.com/Azure/azure-cli/issues

Thank you.
Best Regards,
Jerry Chong

Hi @larrywa / @SaurabhSharma-MSFT ,
I've faced similar error like your case.
Could share what is steps required on resolving this issue?
Error Logs:
17:53:38  + az account set --subscription ****
17:53:39  + az aks get-credentials --resource-group RG_1 --name AKS-1
17:53:41  ERROR: The command failed with an unexpected error. Here is the traceback:
17:53:41  ERROR: [Errno 30] Read-only file system: '/.kube/config'
17:53:41  Traceback (most recent call last):
17:53:41    File "/usr/lib64/az/lib/python3.9/site-packages/knack/cli.py", line 233, in invoke
17:53:41      cmd_result = self.invocation.execute(args)
17:53:41    File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 663, in execute
17:53:41      raise ex
17:53:41    File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
17:53:41      results.append(self._run_job(expanded_arg, cmd_copy))
17:53:41    File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 697, in _run_job
17:53:41      result = cmd_copy(params)
17:53:41    File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 333, in __call__
17:53:41      return self.handler(*args, **kwargs)
17:53:41    File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
17:53:41      return op(**command_args)
17:53:41    File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/command_modules/acs/custom.py", line 1280, in aks_get_credentials
17:53:41      _print_or_merge_credentials(
17:53:41    File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/command_modules/acs/custom.py", line 1403, in _print_or_merge_credentials
17:53:41      with os.fdopen(os.open(path, os.O_CREAT | os.O_WRONLY, 0o600), 'wt'):
17:53:41  OSError: [Errno 30] Read-only file system: '/.kube/config'
17:53:41  To check existing issues, please visit: https://github.com/Azure/azure-cli/issues

Thank you.
Best Regards,
Jerry Chong

PowerShell runs in admin mode.
Azure CLI v 2.56.0
Executed commands:
az login
works fine
az account set --subscription [my sub]
works fine
az aks get-credentials --resource-group [rg] --name [name] --overwrite-existing
returns this
The command failed with an unexpected error. Here is the traceback:
[Errno 13] Permission denied: 'C:\\Users\\barsi\\.kube\\config'
Traceback (most recent call last):
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 233, in invoke
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 663, in execute
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 697, in _run_job
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 333, in __call__
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/acs/custom.py", line 1298, in aks_get_credentials
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/acs/custom.py", line 1430, in _print_or_merge_credentials
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/acs/custom.py", line 1353, in merge_kubernetes_configurations
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/acs/custom.py", line 1342, in load_kubernetes_configuration
PermissionError: [Errno 13] Permission denied: 'C:\\Users\\barsi\\.kube\\config'
To check existing issues, please visit: https://github.com/Azure/azure-cli/issues


add test for previously-skipped patient method

I rule and have completed some work on Case Manager that's ready for review!
(brief, plain english overview of your changes here)
This pull request makes the following changes:

Test the trim_shared_patients method, which we had been skipping.
Replaces #2583 (now using the new shared rather than flagged language)

(If there are changes to the views, please include a screenshot so we know what to look for!)
It relates to the following issue #s:

Fixes #2575
Bumps #Y

For reviewer:

Adjust the title to explain what it does for the notification email to the listserv.
Tag this PR:

feature if it contains a feature, fix, or similar. This is anything that contains a user-facing fix in some way, such as frontend changes, alterations to backend behavior, or bug fixes.
dependencies if it contains library upgrades or similar. This is anything that upgrades any dependency, such as a Gemfile update or npm package upgrade.

If it contains neither, no need to tag this PR.

Seeing some weird system test failures (had to re-run test suite, and also seeing these happen with local system tests). I think we're good to merge but will take a look to see if we borked something with system test reliability.


Ideas for new features and projects

See https://github.com/Ellzord/JALSE/wiki/Future-changes
Can we get some suggestions of what you would like to see?

@benwaffle @wlmiller @pbremer @mariosk89 @ckerr89 @stelioskiayias

I'd say that having a number of well-known simulation projects will be good for a start. Robomop and  Termites simulations can act as a nice tutorial, because the goal of the simulation is simple and easy to understand. Based on this, we can have tutorials matching the steps required to build a JALSE project, to the steps required by the simulation.
After this, we could have a bigger simulation running over the web.
This would require a JALSE RESTful wrapper

Taking this in mind + Reddit post


Add stock support to cookie corner [dirt road implementation]

In the current system, the cookie corner does not keep track of how many products are currently available. The following improvement aims to improve this by including a stock count for each product which will be deducted by tallies, and the ability of the board to update this stock count whenever there is a new delivery.
This improvement is planned using the so-called "dirt-cobblestone-alphalt road implementation," where each step contains a functioning product with increasing requirements. The requirements are shown below as user stories. This issue will implement the dirt road implementation.
Features dirt road implementation
D.1 As a user, I want to see the (presumed) stock for each product when using the cookie corner terminal.
D.2 As a board member, I want to easily update  the stock of the cookie corner.
D.3 As a board member, I want to add stock based on the amount of boxes, which automatically calculates the correct increase in stock.
D.4 As a board member, I want to manually set the amount of items per box per product.
Features cobblestone road implementation
C.1 As a user, I want to see a difference between products which are sold out and those that are not.
C.2 As a user, I want to see an indicator if a product is almost sold out.
C.3 As a treasurer, I want an overview of the current stock for stock counts.
Features asphalt road implementation
A.1 As a user, I want to notify the board whenever the presumed stock of a product does not correspond to the actual stock
A.2 As a treasurer, I want to be able to import deliveries of products to update the stock count.
A.3 As a treasurer, I want stock counts to be easily importable into the bookkeeping software

I would recommend against this, since it adds additional work for the treasurer without much benefit, and does not really align with the way the finances are handled. Should the whish still exist to keep stock, I would highly recommend having Exact Online as the single source of thruth for this, as it has stock count implemented and even has an app to easily count and update stock. The website could then access this through Ecact's API.

Furthermore, D.1., C.1. and C.2. can be accomplished symply by turning around, without this requiring extra effort from the board, or causing beration as described in A.1.

No longer relevant


issue #1983: Fixed to prevent InAppBrowser Activity from being restored

@pichillilorenzo
Connection with issue(s)
Resolve issue #1983

Connected to #1983

Testing and Review Notes

launch the example application and open InAPpBrowser
kill the process depending on the OS (can be achieved by changing permissions)
start the example app again MainActivity is restarted and operation is possible (InAppBrowser is closed)

Screenshots or Videos

After this PR marged:

To Do

[x] double check the original issue to confirm it is fully satisfied
[x] add testing notes and screenshots in PR description to help guide reviewers
[ ] request the "UX" team perform a design review (if/when applicable)

Best Regards,

@ShuheiSuzuki-07
Open your PR on the forked project here and I will merge. There is a new package now. zikzak_inappwebview

https://github.com/all-contributors please add @ShuheiSuzuki-07 for code

@all-contributors please add @ShuheiSuzuki-07 for code

@all-contributors please add @ShuheiSuzuki-07 for code


Fix procedural macros

Currently procedural macros do not work outside of uefi crate, because they are referencing crate-local items (Guid, Protocol etc.) and when invoked from a crate other than 'uefi' those items cannot be found (well because the other crate does not have them).
This is a known (as I learned) procedural macro issue and the latest best workaround is what I implemented here - allow 'uefi' to reference itself by ::uefi and then use ::uefi in those macros.
As an additional bonus (I can revert that if you have objections but it's neat and does not break anything) I made the 'entry' macro always make the exported entry function have the name 'efi_main', which is required by the rust efi target I think.
Anyway, with that change, users can name their entry function whatever they want (right now that leads to cryptic errors iirc), and the fact that this is an entry function is clearly marked by the #[entry] attribute above it.

Thank you, the changes look great!

I made the 'entry' macro always make the exported entry function have the name 'efi_main', which is required by the rust efi target I think

Could you also update the docs to mention that the main function can be named in any way, but will be renamed to efi_main by the proc macro?

I've also added the 'extern crate libc' thing to said doc, because that one took me an extra minute at some point :)

Thanks for the contribution!


Add guided dialog for adding a whitelist

User Story
As a: Teacher
I want: a guided dialog for adding a whitelist.
Currently the feature is not that good, in a UX aspect. The dialog should be guided. So the screen is for uploading a file. The second screen should show the user, which are in geli and which are currently not. Also a accept or cancel button should be there. The functionality is present but the UI is not that good.
Acceptance criteria:

[ ] new dialog for whitelist feature
[ ] use the shared upload component
[ ] show the user at the end of the dialog
[ ] don't create the whitelist user object in the db until the user accept

Estimated:

5 x 4hr

I think that using a dialog for this is a direct violation of the material style guide, since dialogs should only be used for interruptive messages but never for things like content creation.
https://material.io/guidelines/components/dialogs.html

@lukas-schardt @MichaelNarkus Can you please close this too https://github.com/utetrapp/geli/issues/509 !

Maybe you could use this https://material.angular.io/components/stepper/overview


add FAQs for mapping PVC and ConfigMap to instances

Added FAQ entries to explain how to add per-server persistent volume claims and config maps.
I could not find information on what is actually required to get the new entries added to the index page, or the reason for the headers on other such pages that include dates and weight. Is that documented somewhere?
Note: this requires creating both a volume and a volumeMount entry. If we aren't attempting to support the full range of persistent volumes, but only these two, we might consider simplifying to a single entry. As it is, we should add some validations, including the existing of a matching volume for every volume mount, and possibly also some validation that the specified resource (PVC or ConfigMap) actually exists.

I could not find information on what is actually required to get the new entries added to the index page, or the reason for the headers on other such pages that include dates and weight. Is that documented somewhere?

I assume there's documentation somewhere in the hugo docs, but, when I added a FAQ entry recently, I experimentally found that (a) the weight determines the location of the FAQ entry relative to the other FAQ entries - the lower the weight the earlier the FAQ entry, and (b) the FAQ index is automatically updated when new FAQ entries are added.

FWIW I recently took a stab at setting the weights of each FAQ entry - they were all at '1' previously.  Feel free to change the weights around if you think the ordering is wacky.


Atom is not responding during a filter

First thanks you for your package :)
I had a issue with it when I open Android Logcat file issued from command adb logcat -v threadtime
In my example I've approximately 5000 lines.
When I do a filter regularly Atom is not responding. Filter can be a string or log level.
I don't use your package (and Atom) for a long time and I don't know if it produces on other logs type.

Hi @varod, I agree in your observation. The filter scan (tokenizing or regex) and folding of lines just takes too long when filteringen on log files larger than 2000 lines. This causes Atom to become non-responding, which is far from ideal.
I'll have a look at where the bottleneck is or else I'll have to change the way filtering works. I'm open for suggestions.

So it turns out the bottleneck is the folding / unfolding of lines (probably because of a render happening) and not the actual filtering (although tokenizeLine under level filtering is also pretty heavy). This means I'll have to change the way lines are filtered out or mark log files above 2000 lines as 'unfilterable'.


QFED-v3.0.0

Redesign QFED to facilitate integration of VIIRS(S-NPP and JPSS-1).
Objectives:

better code organization
add VIIRS/S-NPP and VIIRS/JPSS-1
reproduce QFED-v2.5.r1

MODIS works as expected in 89a13b5. Differences are present with respect to v2.5.r1 because the internal pixel classifications are not (yet) identical.

Close. See PR #8 (f342153).

Close.


Multilingual chat-bot

Has anyone tried this on any other language other than English?
There German pre-trained models available for GPT. Will it work for the German language?

i guess it will work yes. Just you ll need and a dataset like Persona-Chat in German language.


BTF does not appear to be detected

Following along with tutorial one liners I see that If the kernel has BTF (BPF Type Format) data, all kernel structs are always available.
I believe this means that I can omit these includes from example path.bt:
#include <linux/path.h>
#include <linux/dcache.h>

This does not work as expected and gives an error that the struct definitions are missing even though my system appears to have BTF support.
I think I satisfy the following requirements from btf_support
    Linux 4.18+ with CONFIG_DEBUG_INFO_BTF=y
        Building requires dwarves with pahole v1.13+
    bpftrace v0.9.3+ with BTF support (built with libbpf v0.0.4+)

bpftrace was installed from the apt repo
What reproduces the bug?
sudo bpftrace path.bt
path.bt:6:28-49: ERROR: Unknown struct/union: 'struct path'
    printf("open path: %s\n", str(((struct path *)arg0)->dentry->d_name.name));

cat path.bt
//#include <linux/path.h>
//#include <linux/dcache.h>

kprobe:vfs_open
{
	printf("open path: %s\n", str(((struct path *)arg0)->dentry->d_name.name));
}

bpftrace --info
sudo bpftrace --info
Kernel helpers
  get_current_cgroup_id: yes
  send_signal: yes
  override_return: yes

Kernel features
  Loop support: yes

other relevant info
uname -r
5.13.0-37-generic

cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.4 LTS"

bpftrace -V
bpftrace v0.9.4

cat /boot/config-`uname  -r` | grep BTF
CONFIG_VIDEO_SONY_BTF_MPX=m
CONFIG_DEBUG_INFO_BTF=y
CONFIG_PAHOLE_HAS_SPLIT_BTF=y
CONFIG_DEBUG_INFO_BTF_MODULES=y

ls -l /sys/kernel/btf/vmlinux
-r--r--r-- 1 root root 5044520 Apr 18 19:57 /sys/kernel/btf/vmlinux

Ended up finding a fix, but it wasn't pretty. Documenting in case it is useful for someone in the future
I built bpftrace from source, but it was not able to detect libbpf as being installed or a package called libdw-dev.
libdw-dev was as easy as an apt install, but I needed to build libbpf from source (version 0.8).
cmake was able to find libbpf and libdw, but then I got several compilation errors with bpftrace.
file src/btf.cpp did not correctly set HAVE_LIBBPF_BTF_DUMP_NEW_V0_6_0 even though I was on v0.8. Hacky solution was to hardcode the cpp file to use that case since it was falling to the old case.
I needed a couple slight modifications in /usr/include/bpf/bpf.h and /usr/include/bpf/btf.h which were adding a couple enum definitions in.
btf.h needed btf_func_linkage:
enum btf_func_linkage {
	BTF_FUNC_STATIC = 0,
	BTF_FUNC_GLOBAL = 1,
	BTF_FUNC_EXTERN = 2,
};

and bpf.h needed bpf_stats_type to be changed from
enum bpf_stats_type; /* defined in up-to-date linux/bpf.h */

changed to (https://github.com/libbpf/libbpf/issues/249)
enum bpf_stats_type
#ifdef __cplusplus
: int
#endif
; /* defined in up-to-date linux/bpf.h */

I also needed to add /usr/lib64 to my loader path otherwise the libbpf.so would not be found at runtime.
I am now able to run path.bt example without the header files.
Leaving this issue open due to missing definition of HAVE_LIBBPF_BTF_DUMP_NEW_V0_6_0 seeming like an error that should be fixed. Will close if devs think otherwise

Hi, sorry for a late answer. Just sharing some thoughts here for future reference.
First of all, bpftrace version 0.9.4 is fairly old and it's very likely that BTF support is not good there. So yes, your only option is to upgrade your system or to build bpftrace from source.
Now to the build problems:

HAVE_LIBBPF_BTF_DUMP_NEW_V0_6_0 is not correctly detected due to using old GCC. A solution would be to update your GCC or to use an older version of libbpf (0.5.0).
When installing libbpf, it's possible to use e.g. LIBDIR=/usr/local/lib make install to install libraries into a path that Ubuntu searches by default. We do the same for our CI docker builds (see docker/build.sh).
Not sure about the rest of the problems but I'd expect a similar issue (some libbpf feature not properly detected due to old GCC).

Anyway, I think that the issue can be closed.

Ended up finding a fix, but it wasn't pretty. Documenting in case it is useful for someone in the future
I built bpftrace from source, but it was not able to detect libbpf as being installed or a package called libdw-dev. libdw-dev was as easy as an apt install, but I needed to build libbpf from source (version 0.8).
cmake was able to find libbpf and libdw, but then I got several compilation errors with bpftrace.
file src/btf.cpp did not correctly set HAVE_LIBBPF_BTF_DUMP_NEW_V0_6_0 even though I was on v0.8. Hacky solution was to hardcode the cpp file to use that case since it was falling to the old case.
I needed a couple slight modifications in /usr/include/bpf/bpf.h and /usr/include/bpf/btf.h which were adding a couple enum definitions in. btf.h needed btf_func_linkage:
enum btf_func_linkage {
	BTF_FUNC_STATIC = 0,
	BTF_FUNC_GLOBAL = 1,
	BTF_FUNC_EXTERN = 2,
};

and bpf.h needed bpf_stats_type to be changed from
enum bpf_stats_type; /* defined in up-to-date linux/bpf.h */

changed to (libbpf/libbpf#249)
enum bpf_stats_type
#ifdef __cplusplus
: int
#endif
; /* defined in up-to-date linux/bpf.h */

I also needed to add /usr/lib64 to my loader path otherwise the libbpf.so would not be found at runtime.
I am now able to run path.bt example without the header files.
Leaving this issue open due to missing definition of HAVE_LIBBPF_BTF_DUMP_NEW_V0_6_0 seeming like an error that should be fixed. Will close if devs think otherwise

I have same problem. I followed your quick fix and the bpftrace --info:
System
  OS: Linux 5.13.0-51-generic #58~20.04.1-Ubuntu SMP Tue Jun 14 11:29:12 UTC 2022
  Arch: x86_64

Build
  version: v0.15.0
  LLVM: 12.0.0
  ORC: v2
  foreach_sym: yes
  unsafe uprobe: no
  bfd: yes
  bpf_attach_kfunc: yes
  bcc_usdt_addsem: yes
  bcc bpf_attach_uprobe refcount: yes
  bcc library path resolution: yes
  libbpf: yes
  libbpf btf dump: no
  libbpf btf dump type decl: no
  libdw (DWARF support): yes

Kernel helpers
  probe_read: yes
  probe_read_str: yes
  probe_read_user: yes
  probe_read_user_str: yes
  probe_read_kernel: yes
  probe_read_kernel_str: yes
  get_current_cgroup_id: yes
  send_signal: yes
  override_return: yes
  get_boot_ns: yes
  dpath: yes

Kernel features
  Instruction limit: 1000000
  Loop support: yes
  btf (depends on Build:libbpf): no
  map batch (depends on Build:libbpf): yes
  uprobe refcount (depends on Build:bcc bpf_attach_uprobe refcount): yes

Map types
  hash: yes
  percpu hash: yes
  array: yes
  percpu array: yes
  stack_trace: yes
  perf_event_array: yes

Probe types
  kprobe: yes
  tracepoint: yes
  perf_event: yes
  kfunc: yes
  iter:task: yes
  iter:task_file: yes


Incorrect display of skins

I made myself a skin the other day and went to New Frontier Craft and here the glasses are incorrectly displayed on the skin  :(
https://cdn.discordapp.com/attachments/646412212507770958/884460740059213844/2021-09-06_18.30.05.png

What's being displayed incorrectly with the glasses? How are they supposed to look? Is the issue with transparency, them rendering in the wrong location, or what?

Transparency, the outer hat layers are supposed to have that.

Я когда играю в New Frontier Craft у меня везде не прозрачная текстура на
скине, хотя она у меня прозрачная...
ср, 13 окт. 2021 г., 4:40 Logan @.***>:

What's being displayed incorrectly with the glasses? How are they supposed
to look? Is the issue with transparency, them rendering in the wrong
location, or what?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/LO6AN/New-Frontier-Craft/issues/71#issuecomment-941829563,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVQHFFCSRWHHQVA7PMBIGMDUGTPPDANCNFSM5DQWGVKQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Logging config doesn't make a difference

Changes to the [logging] parameters in the influxdb.conf file don't seem to make any difference.
I have set write-trace to true and http-access to false, restarted and yet I still see http and no writes.

@zeroXten -- what version are you running?

0.9.0 from http://s3.amazonaws.com/influxdb/influxdb_latest_amd64.deb

There have been significant improvements in the 0.9.1 release, I strongly suggest you upgrade and try again. Please let us know if it does not address the issue.
https://influxdb.com/download/index.html
(Those "latest" links are deprecated)


Write how to article for persist google sheets datastore

Description:
A article should be written, exploring the persist googlesheets datastore support and integration

Article published in medium - https://medium.com/@sahanhemachandra/enhanced-data-management-google-sheets-empowered-by-bal-persist-392096c045c8


Followed the install instructions and it isn't working.

Followed the install instructions and it isn't working.
Is this a version issue? Please specify in the in the readme which version of jhipster and node it was tested against.
$ node -v
v8.12.0

$ npm -v
6.4.1

$ jhipster --version
Using JHipster version installed globally
5.3.4

$ npm i -g generator-jhipster-vuejs
npm WARN deprecated<EMAIL_ADDRESS>gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated<EMAIL_ADDRESS>This package is unmaintained. Use @sinonjs/formatio instead
+<EMAIL_ADDRESS>
updated 1 package in 23.038s

$ jhipster --blueprint vuejs

Welcome to JHipster v5.3.4
Application files will be generated in folder: /home/luis/third-party/easy
 _______________________________________________________________________________________________________________

  Documentation for creating an application is at https://www.jhipster.tech/creating-an-app/
  If you find JHipster useful, consider sponsoring the project at https://opencollective.com/generator-jhipster
 _______________________________________________________________________________________________________________

events.js:167
      throw er; // Unhandled 'error' event
      ^

Error: ERROR! The generator-jhipster-vuejs blueprint provided is not installed. Please install it using command npm i -g generator-jhipster-vuejs.
    at Environment.error (/home/luis/.nvm/versions/node/v10.5.0/lib/node_modules/generator-jhipster/node_modules/yeoman-environment/lib/environment.js:157:40)
    at module.exports.error (/home/luis/.nvm/versions/node/v10.5.0/lib/node_modules/generator-jhipster/generators/generator-base.js:2060:18)
    at shelljs.exec (/home/luis/.nvm/versions/node/v10.5.0/lib/node_modules/generator-jhipster/generators/generator-base-private.js:697:26)
    at /home/luis/.nvm/versions/node/v10.5.0/lib/node_modules/generator-jhipster/node_modules/shelljs/src/exec.js:124:9
    at ChildProcess.exithandler (child_process.js:298:5)
    at ChildProcess.emit (events.js:182:13)
    at maybeClose (internal/child_process.js:961:16)
    at Socket.stream.socket.on (internal/child_process.js:380:11)
    at Socket.emit (events.js:182:13)
    at Pipe._handle.close (net.js:595:12)
Emitted 'error' event at:
    at Environment.error (/home/luis/.nvm/versions/node/v10.5.0/lib/node_modules/generator-jhipster/node_modules/yeoman-environment/lib/environment.js:159:15)
    at module.exports.error (/home/luis/.nvm/versions/node/v10.5.0/lib/node_modules/generator-jhipster/generators/generator-base.js:2060:18)
    [... lines matching original stack trace ...]
    at Pipe._handle.close (net.js:595:12)

tried it with different node versions
events.js:183
      throw er; // Unhandled 'error' event
      ^

Error: ERROR! The generator-jhipster-vuejs blueprint provided is not installed. Please install it using command npm i -g generator-jhipster-vuejs.
    at Environment.error (/home/luis/.nvm/versions/node/v8.12.0/lib/node_modules/generator-jhipster/node_modules/yeoman-environment/lib/environment.js:157:40)
    at module.exports.error (/home/luis/.nvm/versions/node/v8.12.0/lib/node_modules/generator-jhipster/generators/generator-base.js:2060:18)
    at shelljs.exec (/home/luis/.nvm/versions/node/v8.12.0/lib/node_modules/generator-jhipster/generators/generator-base-private.js:697:26)
    at /home/luis/.nvm/versions/node/v8.12.0/lib/node_modules/generator-jhipster/node_modules/shelljs/src/exec.js:124:9
    at ChildProcess.exithandler (child_process.js:283:5)
    at emitTwo (events.js:126:13)
    at ChildProcess.emit (events.js:214:7)
    at maybeClose (internal/child_process.js:915:16)
    at Socket.stream.socket.on (internal/child_process.js:336:11)
    at emitOne (events.js:116:13)

This is still work in progress and there is no stable release yet. If you
wanna try it you need to clone the repo and run npm link inside
On Tue, 25 Sep 2018, 7:50 pm Luis<EMAIL_ADDRESS>wrote:

tried it with different node versions
events.js:183
throw er; // Unhandled 'error' event
^
Error: ERROR! The generator-jhipster-vuejs blueprint provided is not installed. Please install it using command npm i -g generator-jhipster-vuejs.
at Environment.error (/home/luis/.nvm/versions/node/v8.12.0/lib/node_modules/generator-jhipster/node_modules/yeoman-environment/lib/environment.js:157:40)
at module.exports.error (/home/luis/.nvm/versions/node/v8.12.0/lib/node_modules/generator-jhipster/generators/generator-base.js:2060:18)
at shelljs.exec (/home/luis/.nvm/versions/node/v8.12.0/lib/node_modules/generator-jhipster/generators/generator-base-private.js:697:26)
at /home/luis/.nvm/versions/node/v8.12.0/lib/node_modules/generator-jhipster/node_modules/shelljs/src/exec.js:124:9
at ChildProcess.exithandler (child_process.js:283:5)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:915:16)
at Socket.stream.socket.on (internal/child_process.js:336:11)
at emitOne (events.js:116:13)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jhipster/jhipster-vuejs/issues/13#issuecomment-424438968,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABDlF0248bm25HKtHkxT9sB6lnWlWlqHks5uemzogaJpZM4W5Ktl
.


Remove ToHex

The ToHex trait was replaced by either simple Display/LowerHex where appropriate or DisplayHex from bitcoin_internals which is faster.
This change replaces the usages and removes the trait.

Would love if this was brought back. This makes things really hard to work with, basically need to memorize which things are encoded to hex with .to_string() and which aren't, also need to guarantee that for all future versions. This basically forces us to use the hex crate

All types that are naturally displayed as hex are displayed as hex. :) Not so hard. All hashes, public keys... The only one which I think is weird is Script, which displays ASM, but that one does have as_hex method.
And yes, we do guarantee it for those important types, there's no reason to change it.

It still makes the code harder to read without that knowledge, we also lost the ability to call .to_hex on types like [u8; 32]

Why not create a strong type? We have hash_newtype! macro for instance. And if you have a 32B object that is neither a public key nor a hash (which I don't remember existing in Bitcoin) then I'm interested to know if we should add it to the library. And if you don't want to wait and don't want hex (which is understandable, there's a reason we don't depend on it) we have the hex-conservative crate which backs our conversions and was released for people who need this.

@Kixunil I've gotten complaints from many people about this. It does make things harder to use. To tell whether something is being hex-encoded you now need to infer its type and also know what's "natural" about it, vs using to_hex where you don't need to know either.
The change also forces people to change their code all over the place, and it's not a mechanical change because you need to think about whether to_string is appropriate or if they need to use as_hex and dig out the appropriate trait for it. The resulting code is harder to read, and it makes people resentful because the change really wasn't necessary.
We should just bring the trait back. Nobody has to use it if they don't want to, it can exist alongside the "proper" traits. And we can taboo them within rust-bitcoin projects.

This one is really quite curly, I flat out agree that the DisplayHex trait is hard/annoying to use, however I also flat out agree that it is more correct.
Recently we added the trait to our private prelude module which made using it more ergonomic (for those who like use prelude::*), would it be useful to have a public prelude? (Obviously we'd have to re-name our private one first.)
If we add back in ToHex with a big comment saying that a more-correct-kinda-hard-to-use impl can be found in DisplayHex

It still makes the code harder to read without that knowledge, we also lost the ability to call .to_hex() on types like [u8; 32]

We implement DisplayHex for variuos array sizes so you can call the longer but more descriptive to_lower_hex_string.
impl_array_as_hex!(
    1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 20, 32, 33, 64, 65, 128, 256, 512, 1024,
    2048, 4096
);

We should just bring the trait back. Nobody has to use it if they don't want to, it can exist alongside the "proper" traits. And we can taboo them within rust-bitcoin projects.

We'd still have to litter the rust-bitcoin crates with code supporting it, I'm not super keen on this.

OK, if people really need to be explicit about things being hex, I suggest adding inherent methods instead of a trait. They obviate the need to import anything which I previously found annoying (part of the motivation for removing it). But rather than to_hex it should be to_hex_string and as_hex to nudge people into not allocating strings just to display them.
There's one thing I find weird though: reversed hashes. Should they be still reversed? Both options feel wrong TBH.

We have a prelude to make it more ergonomic to import the trait, this is even better than it was when we had ToHex and FromHex

I don't see how this is better. It looks significantly worse. Now you have unreadable code and you've hidden its origin behind a wildcard.

We implement DisplayHex for various array sizes so you can call the longer but more descriptive to_lower_hex_string.

Just adding an alias to_hex for to_lower_hex_string would go a long way. And/or we could maybe add a deprecated ToHex trait saying to use DisplayHex instead which simply passes through to this (and has a blanket impl). Then the majority of existing to_hex code will have a clear migration path.

If people have problem migrating specifically because of missing to_hex then I'm OK with adding a deprecated one, even backport it. But otherwise I would prefer not to add deprecated items.

Somebody just asked on IRC how to hex-serialize Transaction and I had to look it up because I can't remember how to use this.
I think we should bring to_hex back and not even deprecate it.

Actually, what if we added serialize(&T) -> Vec<u8> and serialize_hex(&T) -> String to the Encodable trait? Maybe we can even create an efficient as_hex() method which returns a hex-encoding Display object. This would cover transactions, blocks and hashes, which is probably half the stuff people want to hex-encode. (The other half are signatures and pubkeys, which I think should implement Encodable, but we can debate that elsewhere.)
This would still be a clean/correct API and also show up when people search hex on the docs page for these various types.
I'd still like to add a deprecated to_hex/ToHex so peoples' existing code wouldn't break without a friendly upgrade path. But I think we can drop it after a version or two, if we had this extended Encodable API.

That sounds like a good idea. I can have a play with it when I'm back off break.

Actually, what if we added serialize(&T) -> Vec<u8> and serialize_hex(&T) -> String to the Encodable trait?

Yeah, I was wondering why they're not methods before and IIRC there was some reason actually but I can't remember. We'll see when we try. :) I thought I added it in push_decode but don't see it now.
But for vec one I'd prefer it to mention vec. And probably mention consensus. consensus_to_hex, consensus_to_vec or something.

This would still be a clean/correct API and also show up when people search hex on the docs page for these various types.

Yes.
Also Transaction is serialized to hex so often I'd be fine with adding an inherent method.

seems this broke fedimint today :(
https://github.com/fedimint/fedimint/pull/5813

I'm confused. The old to_hex method did the right thing and the new to_string method does the right thing.
encode_hex is not part of this crate and has never been part of rust-bitcoin.

It looks like Fedimint switched from bitcoin_hashes::hex to the hex crate, which is understandable because you have to hex-encode somehow, but how were you able to implement hex::ToHex on our hash types? The coherence rules should have prevented that.

It also looks like the whole migration started at the end of April, at which point the hex-conservative crate we maintain had had multiple releases. So I'm actually quite confused why you switched to the 3rd-party hexcrate because all of the missing functionality had been restored. (And of course, the ability to hex-encode blockhashes was never missing.) Though the hex stuff happened in https://github.com/fedimint/fedimint/3994 (December). But this was still after hex-conservative was out.
Then it looks like the genesis_hash field in question was an untyped [u8; 32]. There is no point at which our hex implementation would've hex-encoded this object backward, nor would the hex crate, nor would hex-conservative.


FeathersVuexFormWrapper with Vuelidate

It would be wonderful to have an example of using the FeathersVuexFormWrapper component with what seems to be one of, or the most popular validation library: vuelidate.  Maybe it's not possible, but it would seemingly be the act of making the clone available to vuelidate.

This is definitely possible, already, but probably not in the way you might be thinking.  Vuelidate validations would be handled inside the nested component.  In the case of the below example, Vuelidate would be used inside the SomeEditor component:
<template>
  <FeathersVuexFormWrapper :item="currentItem" watch>
    <template v-slot="{ clone, save, reset, remove }">
      <SomeEditor
        :item="clone"
        @save="save().then(handleSaveResponse)"
        @reset="reset"
        @remove="remove"
      ></SomeEditor>
    </template>
  </FeathersVuexFormWrapper>
</template>

By the time a form submission reaches the FeathersVuexFormWrapper, the data should already have been validated.
I'm working on another awesome project for the FeathersJS community right now, which will really improve people's experience with Feathers-Vuex, so I won't make time for this for a week or so, maybe more.  I'm going to keep this open because this is a great idea to add to the common patterns section of the docs.
Thank you!

I'm facing the same problem - I try to validate the input inside the SomeEditor component with vuelidate. My problem is that the error is always shown, even if the input is valid.
My parent component looks like above:
<FeathersVuexFormWrapper :item="item" watch>
  <template v-slot="{ clone, save, reset, remove }">
    <BuildingEditor :item="clone" @save="save().then(handleSaveResponse)" @reset="reset" @remove="remove"></BuildingEditor>
  </template>
</FeathersVuexFormWrapper>

My BuildingEditor component looks like this:
<template>
  <form class="q-pa-md full-width" @submit.prevent="$emit('save')">
    <input v-model="item.name" @blur="$v.building.name.$touch">

Name is required

    <button type="submit">Save</button>
    <button type="button" @click="$emit('reset')">Reset</button>
    <button type="button" @click="$emit('remove')">Delete</button>
  </form>
</template>

However the error is always shown, even if the input is valid.

Any help or an example would be greatly appreciated! Thanks in advance!

@anli-xsigns I've added an example to the docs that shows how to use the new Vuelidate composition API.  Vuelidate alpha is a tad bit buggy, but it's all I can offer at this point, because I usually do validations manually.  ;)

Here's the example: https://vuex.feathersjs.com/feathers-vuex-forms.html#vuelidate-2-example
When Vuelidate 2 is actually released (which I imagine will be AFTER Vue 3 is released), I'll update the example to something more concrete and applicable.


Schema Driven Visual Editor

Description
Visual Editor and Form Editor are both visualization libs for AdaptiveDialog schema, they work on the same abstraction level.
In Form Editor, we have an uischema.ts file in which render process is defined by a json.

We should also have a schema definition file in Visual Editor. Then we can possibily

define multiple versions of schema to support different SDK versions' rendering
let users define their own ui elements for customization

Plan
To accomplish the 'schema driven' target smoothly, we may need several PRs.

[ ] Extract our current visual nodes / visual elements as a built-in element library. (Then we can reference them in uischema file easily.)
[ ] Transform current visual-editor code logic to a uischema file. (built upon PR1's work)
[ ] (long term work) Add uischema files for specific versions

Interface
Ideally, a semantic Visual Editor could be used like this
import  { uischema } from<EMAIL_ADDRESS>
const customizedSchema = { ...uischema, ...myshema };

const render = () => {
    return (
        <VisualEditor
               data={data}
               schema={customizedSchema}
         />
    );
}

@cwhitten this is the 'schema driven' topic we talked today

In FormEditor, uischema contains several types of elements:

ui:widget
ui:field
ui:order
ui:hidden
ui:options

1 & 2 define what a SDK type looks like; 3,4,5 provide us convenience to config the form.

In Visual Editor, we will build something similar with FormEditor. Here is an example on 'SendActivity'.
const FormCard = (title, content, menu) => <div>{title}{content}{menu}</div>;
const AdaptiveTitle = data => ConceptLabels[data.$type].title;
const LgField= value = > <LgContent value={value} />

const uischema = {
  [SDKTypes.SendActivity]: {
    'ui:widget': FormCard,
    'ui:theme': <a group of styles>,
    title: AdaptiveTitle,
    content: data => <LgField value={data.activity} />,
  }
}

It will produce a node like this:

Another example on IfCondition.
const uischema = {
  [SDKTypes.IfCondition]: {
    'ui:widget': IfCondition,
    condition: {
      'ui:widget': FormCard,
      title: 'Condition',
      content: data => data.condition,
    }
  }
}

@cwhitten @a-b-r-o-w-n do you have suggestions on the schema format?

https://github.com/microsoft/BotFramework-Composer/pull/1811

PR plan

[x] stage 1 (in PR) - support basic rendering with uischema definition

set up uischema definition & implement a generic renderer based on uischema
covered $types: 15 simple $types, such as LogAction

[ ] stage 2 - support complicated content rendering

extract more widget to support complicated node content
covered $types: SendActivity, CallDialog, BeginDialog`

[ ] stage 3 - support multiple nodes rendering

implement a InputWidget which looks like current BaseInput
covered $types: all input $types, such as TextInput, NumberInput (but exclude OauthInput)

[ ] stage 4 - support nested uischema definition

extend 'uischema''s definition to support rendering nested $types such as IfConditon, Foreach
covered $types: branching - IfCondtion, SwitchConditon; loop - Foreach, ForeachPage;


Fixed Invite New User endpoints for organizations and projects

Proposed changes

Checklist

[x] I have signed the MongoDB CLA
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added any necessary documentation (if appropriate)
[x] I have run make fmt and formatted my code

Further comments

@gssbzn I am updating projects here as well


Fix for the iterate function in SciData object

Work includes:

Adds a test for nested objects via using datum in datapoints
Adds this as an example to the example python script
Fix for a recursion error in SciData.__iterate_function. Mainly fixed:

Making sure the category count was incremented properly
This category count was used in constructing the @id entry
Upon "leaving", the function drops the "leaf" / latest level of nesting so that it doesn't include it in the next @id AND resetting the counter for the category back to 0 such that the counter doesn't use the previous max value for a separate nested object

This looks great Marshall. Thanks!


Create docker files to containerize the backend and frontend

Create two separate docker files that build the backend and the frontend as two separate containers.

can u assign me to this issue

Hello @braydenidzenga,
I will create 2 Dockerfile in each directory a directory and docker-compose.yml file in the root directory to build both the api and frontend with one command. i.e. docker-compose up --build.
Kindly assign me this issue.

@vipul-dixit-2004 I assigned this over to you.

Thanks @braydenidzenga,
I have done a PR kindly check

@braydenidzenga I have completed the frontend docker setup also. Kindly review my latest PR.

/assign this to me i complete by EOD


Slowness in deploying stacksets for organization with 800+ accounts

Describe the bug
Customer reported slowness in CfCT pipeline irrespective of vending a new account or updating existing stacksets.
To Reproduce
Create an organization with 800+ accounts with 8+ regions.
Create a manifest with any sample template and point the deployment_targets to all the OUs of those accounts.
Now, perform a code release to the pipeline without any changes in template.
It would take approximately 30 mins per stackset even if there is no change to templates or changesets.
With this situation, the customer has 50+ customizations and takes almost 8-14 hrs for the pipeline to complete.
Expected behavior
Pipeline should complete in less than 5 mins per stackset if there is no changes to the customization templates.
Please complete the following information about the solution:

[v2.2.0 v2.4.0 v2.6.0] Version: [e.g. v1.0.0]

To get the version of the solution, you can look at the description of the created CloudFormation stack. For example, "(SO0089) - customizations-for-aws-control-tower Solution. Version: v1.0.0". You can also find the version from releases

[ us-east-1 ] Region: [e.g. us-east-1]
[ No ] Was the solution modified from the version published on this repository?
[ ] If the answer to the previous question was yes, are the changes available on GitHub?
[ Yes ] Have you checked your service quotas for the sevices this solution uses?
[ No ] Were there any errors in the CloudWatch Logs?

Screenshots

Additional context
I am from ProServe and investigated the issue. Upon digging into the code, it turns out the function "list_stack_instances_account_ids" has MaxResults set to just 20 and for such a large environment with 7600+ stack instances it takes 378 iterations to build the stack instances and on top the stepfunction has wait cycle of 5 seconds between each function call. It causes 30+ mins just to build the list.
Solution: If we change the MaxResults to 100 and reduce the wait time to 1 second, the statemachine completes the task in just about 2.51 mins. This improves the performance significantly. This has been tested in the environment and working fine. I also do not see API throttling issue by making this change. I request the team to review and add this fix to the future release so the other customers would benefit. thanks!

@bdesika-aws I have cut a backlog item to review this request.

Hi @bdesika-aws,
CFCT v2.7.0 optimizes how these account IDs are fetched. Please upgrade to v2.7.0 and let us know if you do not see an improvement in performance.


(bug)eToro - Splash screen: Change text

Description
Changed test in Welcome screen  for only EToro
Fixes #745
How Has This Been Tested?
Go to main screen (Welcome screen) this only for EToro network
Checklist:

[x] PR title matches follow: (Feature|Bug|Chore) Task Name
[x] My code follows the style guidelines of this project
[x] I have followed all the instructions described in the initial task (check Definitions of Done)
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have added reference to a related issue in the repository
[x] I have added a detailed description of the changes proposed in the pull request. I am as descriptive as possible, assisting reviewers as much as possible.
[x] I have added screenshots related to my pull request ( for frontend tasks)
[ ] I have pasted a gif showing the feature.
[ ] @mentions of the person or team responsible for reviewing proposed changes


I can't browse hidden (dot)folders

While showing hidden (dot)files works perfectly, I can't see dotted folders while browsing remote host.

Works great here.
what atom and remote-edit version are you using? Have you tried multiple hosts? ftp or ssh? os? any errors in console?

Works now for me too. I don't know if it was the recent update of the plugin or is it just me blind at the time being ;-)


Fixed potential TFTP issues

Should fix #66

@psychomario I think you should take a peek since you originally wrote these pieces

This all looks good to me. I'm going to merge this.


[CSL-286] Enable with-rocks in CI

@gromak
We have a with-rocks cabal flag which enables compilation of code which depends on rocksdb. Now it's optional, but will be come mandatory soon (and this flag will disappear). We need to somehow make CI install rocksdb.
@domen will you be able do to it?

@domen
https://github.com/input-output-hk/pos-haskell-prototype/pull/5

@domen
This works for Linux and Windows. OSX is being bad.


App crash setting default icon (Didn't find class com.google.firebase.messaging.default_notification_icon on path DexPathList...)

I try to set my notification icon following these steps: https://github.com/dpa99c/cordova-plugin-firebasex#android-notification-icons
This is my android platform config:
<platform name="android">
    <edit-config file="app/src/main/AndroidManifest.xml" mode="merge" target="/manifest/application" xmlns:android="http://schemas.android.com/apk/res/android">
        <application android:networkSecurityConfig="@xml/network_security_config" />
        <application android:layout_width="match_parent" />
        <application android:layout_height="match_parent" />
    </edit-config>
    <config-file mode="merge" parent="/*" target="AndroidManifest.xml" xmlns:android="http://schemas.android.com/apk/res/android">
        <uses-permission android:name="android.permission.FOREGROUND_SERVICE" />
        <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
    </config-file>
	<config-file target="AndroidManifest.xml" parent="/manifest/application" xmlns:android="http://schemas.android.com/apk/res/android">
		<meta-data android:name="com.google.firebase.messaging.default_notification_icon" android:resource="@drawable/notification_icon" />
	</config-file>
    <feature name="SocialSharing">
        <param name="android-package" value="nl.xservices.plugins.SocialSharing" />
    </feature>
    <resource-file src="resources/android/xml/network_security_config.xml" target="app/src/main/res/xml/network_security_config.xml" />
    <resource-file src="google-services.json" target="app/google-services.json" />
	<resource-file src="resources/android/icon/drawable-mdpi-icon.png" target="app/src/main/res/drawable-mdpi/notification_icon.png" />
	<resource-file src="resources/android/icon/drawable-hdpi-icon.png" target="app/src/main/res/drawable-hdpi/notification_icon.png" />
	<resource-file src="resources/android/icon/drawable-xhdpi-icon.png" target="app/src/main/res/drawable-xhdpi/notification_icon.png" />
	<resource-file src="resources/android/icon/drawable-xxhdpi-icon.png" target="app/src/main/res/drawable-xxhdpi/notification_icon.png" />
	<resource-file src="resources/android/icon/drawable-xxxhdpi-icon.png" target="app/src/main/res/drawable-xxxhdpi/notification_icon.png" />
    <allow-intent href="market:*" />
    <icon background="resources/android/icon/ldpi-background.png" density="ldpi" foreground="resources/android/icon/ldpi-foreground.png" src="resources/android/icon/drawable-ldpi-icon.png" />
    <icon background="resources/android/icon/mdpi-background.png" density="mdpi" foreground="resources/android/icon/mdpi-foreground.png" src="resources/android/icon/drawable-mdpi-icon.png" />
    <icon background="resources/android/icon/hdpi-background.png" density="hdpi" foreground="resources/android/icon/hdpi-foreground.png" src="resources/android/icon/drawable-hdpi-icon.png" />
    <icon background="resources/android/icon/xhdpi-background.png" density="xhdpi" foreground="resources/android/icon/xhdpi-foreground.png" src="resources/android/icon/drawable-xhdpi-icon.png" />
    <icon background="resources/android/icon/xxhdpi-background.png" density="xxhdpi" foreground="resources/android/icon/xxhdpi-foreground.png" src="resources/android/icon/drawable-xxhdpi-icon.png" />
    <icon background="resources/android/icon/xxxhdpi-background.png" density="xxxhdpi" foreground="resources/android/icon/xxxhdpi-foreground.png" src="resources/android/icon/drawable-xxxhdpi-icon.png" />
    <splash density="land-ldpi" src="resources/android/splash/drawable-land-ldpi-screen.png" />
    <splash density="land-mdpi" src="resources/android/splash/drawable-land-mdpi-screen.png" />
    <splash density="land-hdpi" src="resources/android/splash/drawable-land-hdpi-screen.png" />
    <splash density="land-xhdpi" src="resources/android/splash/drawable-land-xhdpi-screen.png" />
    <splash density="land-xxhdpi" src="resources/android/splash/drawable-land-xxhdpi-screen.png" />
    <splash density="land-xxxhdpi" src="resources/android/splash/drawable-land-xxxhdpi-screen.png" />
    <splash density="port-ldpi" src="resources/android/splash/drawable-port-ldpi-screen.png" />
    <splash density="port-mdpi" src="resources/android/splash/drawable-port-mdpi-screen.png" />
    <splash density="port-hdpi" src="resources/android/splash/drawable-port-hdpi-screen.png" />
    <splash density="port-xhdpi" src="resources/android/splash/drawable-port-xhdpi-screen.png" />
    <splash density="port-xxhdpi" src="resources/android/splash/drawable-port-xxhdpi-screen.png" />
    <splash density="port-xxxhdpi" src="resources/android/splash/drawable-port-xxxhdpi-screen.png" />
</platform>

The resource's paths are correct but i recieve this error opening the app:

Cordova Firebasex: 7.0.1
Cordova: 9.0.0<EMAIL_ADDRESS>Android: 8.1.0
Node: v12.13.0

I see that you have multiple <edit-config>/<config-file> blocks operating on AndroidManifest.xml.
Cordova has some race conditions around this that can cause some elements to be omitted from the resulting AndroidManifest.xml - see #94.
I would check that all the elements specified in your config.xml are actually appearing in AndroidManifest.xml.
You can verify that setting the default icon for Android works properly in this plugin by building and running the example project which uses a <custom-config-file> block via cordova-custom-config to ensure its config is injected into AndroidManifest.xml.

I have an error setting this:
<custom-config-file parent="./application" target="AndroidManifest.xml">
    <meta-data android:name="com.google.firebase.messaging.default_notification_icon" android:resource="@drawable/notification_icon" />
</custom-config-file>

Adding "xmlns:android="http://schemas.android.com/apk/res/android" builds correctly:
<custom-config-file parent="./application" target="AndroidManifest.xml" xmlns:android="http://schemas.android.com/apk/res/android">
    <meta-data android:name="com.google.firebase.messaging.default_notification_icon" android:resource="@drawable/notification_icon" />
</custom-config-file>

I see in the topbar:

But not in notification:

i check platforms\android\app\src\main\AndroidManifest.xml and it appears
<meta-data android:name="com.google.firebase.messaging.default_notification_icon" android:resource="@drawable/notification_icon"/>

I use Xiaomi mi9 se

I clone and run de test project, obtain the fcm token but it ocurrs the same problem. I send a test message in firebase console but icons stay blank/green

Please try building and running the example project and confirm if the custom icon works correctly on your device in the example app.

i found the problem.
All works fine, but accent color override all icon and painting with this green color. I try to set ANDROID_ICON_ACCENT with #ffffff00 but it doesnt work jeje
If i use a monochrome icon it works :)

As outlined in the documentation:

The icons should be monochrome transparent PNGs

Android only supports monochrome icons for the default (small notification) icon.
Only large notification icons support polychromatic icons but since FCM does not currently support large icons, these can only be used in foreground notifications generated by this plugin when the app is in the foreground.

Much thanks for all :)

i found the problem.
All works fine, but accent color override all icon and painting with this green color. I try to set ANDROID_ICON_ACCENT with #ffffff00 but it doesnt work jeje
If i use a monochrome icon it works :)

Hi 50l3r,
and what was the problem? Im facing the same issue.

Install this plugin https://github.com/dpa99c/cordova-custom-config and try to set this:
<custom-config-file parent="./application" target="AndroidManifest.xml" xmlns:android="http://schemas.android.com/apk/res/android">
    <meta-data android:name="com.google.firebase.messaging.default_notification_icon" android:resource="@drawable/notification_icon" />
</custom-config-file>

@50l3r Wow! Awesome! Worked ;) I suppose it has something to do with the Cordova race conditions dpa99c mentioned earlier.

Facing the same issue, tried everything suggested above but still no luck, but I find alternative way.
Finally added an icon property in notification payload at server side and added #<resource-file > in config.xmlfor that particular icon.
Hope this helps people (I wasted half day for this)


add docker test_env components

Codecov Report
Attention: 243 lines in your changes are missing coverage. Please review.

Comparison is base (0d51fed) 22.30% compared to head (a480997) 21.07%.
Report is 5 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #729      +/-   ##
==========================================
- Coverage   22.30%   21.07%   -1.23%
==========================================
  Files          27       30       +3
  Lines        3672     3929     +257
==========================================
+ Hits          819      828       +9
- Misses       2773     3019     +246
- Partials       80       82       +2

Files
Coverage Δ

blockchain/blockchain.go
0.00% <ø> (ø)

blockchain/ethereum.go
0.00% <0.00%> (ø)

docker/test_env/zookeeper.go
0.00% <0.00%> (ø)

docker/test_env/schema_registry.go
0.00% <0.00%> (ø)

docker/test_env/kafka.go
0.00% <0.00%> (ø)

... and 3 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Installation via Docker behind reverseproxy

Deployment Method

[ ] Installer
[ ] Docker Development
[X] Docker Production
[ ] Bare metal Development
[ ] Bare metal Production
[ ] Digital Ocean image
[ ] Other (please provide a link Steps to Reproduce

Describe the problem*
First, I think it is not a bug but me doing something wrong.
When using Inventree as Admin everything is fine.
Adding a user with only view permissions sometimes gives "Permission Denied" after hammering F5 in the Browser it works.
When I setup Inventree I didn't manage to get it to work on port 80. But with another external Reverseproxy to port 1337 it is working so I am not using port 80. Withing the ".env" file I could switch it away from port 80?
Steps to Reproduce

Open https://service.example.com/index/
Page shows incomplete see screenshot:

After hitting F5 like crazy things can look different:

Relevant log output
how to collect logs?

Can you explain a bit more how you have your reverse proxy setup?

Infront of the nginx provided in the docker-compose file is another nginx (LXC-Container) as a reverseproxy with TLS.
Its configuration looks as follows:
  location / {
    proxy_pass http://<IP_ADDRESS>:1337;
    #proxy_pass http://<IP_ADDRESS>:80;
    proxy_set_header    Host              $http_host;
    proxy_set_header    X-Forwarded-Proto $scheme;
    proxy_set_header    X-Real-IP         $remote_addr;
    proxy_set_header    X-Forwarded-For   $proxy_add_x_forwarded_for;
    proxy_set_header    X-Original-URI    $request_uri;
    proxy_set_header    Upgrade           $http_upgrade;
    proxy_hide_header   Upgrade;
  }

Infront of the nginx provided in the docker-compose file is another nginx (LXC-Container) as a reverseproxy with TLS.
Its configuration looks as follows:
  location / {
    proxy_pass http://<IP_ADDRESS>:1337;
    #proxy_pass http://<IP_ADDRESS>:80;
    proxy_set_header    Host              $http_host;
    proxy_set_header    X-Forwarded-Proto $scheme;
    proxy_set_header    X-Real-IP         $remote_addr;
    proxy_set_header    X-Forwarded-For   $proxy_add_x_forwarded_for;
    proxy_set_header    X-Original-URI    $request_uri;
    proxy_set_header    Upgrade           $http_upgrade;
    proxy_hide_header   Upgrade;
  }

not clear what caused the Problem on my side, but I am sure it is NOT an application problem.

sysadmin is always tricky :)