Add SetFocusOnEntryCompletedBehavior

Documentation added for .NET MAUI Community Toolkit proposals:

[Proposal] SetFocusOnEntryCompletedBehavior https://github.com/CommunityToolkit/Maui/issues/36

Docs Build status updates of commit e463631:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/maui/TOC.yml
:white_check_mark:Succeeded
View

docs/maui/behaviors/characters-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/email-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/event-to-command-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/index.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/masked-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/maximum-length-reached-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/numeric-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/progressbar-animation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/required-string-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/set-focus-when-entry-completed-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/text-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/uri-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/user-stopped-typing-behavior.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

PRMerger Results

Issue
Description

Added File(s)
This PR contains added files. New files require human review.

Yaml File(s)
This PR includes changes to .yml file(s) owned by another author.

Changed Files
This PR contains more than 10 changed files.

File Change Percent
This PR contains file(s) with more than 20% file change.

Index File
This PR contains a change to the index file.

Docs Build status updates of commit 0ddbd00:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/maui/TOC.yml
:white_check_mark:Succeeded
View

docs/maui/behaviors/characters-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/email-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/event-to-command-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/index.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/masked-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/maximum-length-reached-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/numeric-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/progressbar-animation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/required-string-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/set-focus-when-entry-completed-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/text-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/uri-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/user-stopped-typing-behavior.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

PRMerger Results

Issue
Description

Added File(s)
This PR contains added files. New files require human review.

Yaml File(s)
This PR includes changes to .yml file(s) owned by another author.

Changed Files
This PR contains more than 10 changed files.

File Change Percent
This PR contains file(s) with more than 20% file change.

Index File
This PR contains a change to the index file.

Docs Build status updates of commit 1e56399:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/maui/TOC.yml
:white_check_mark:Succeeded
View

docs/maui/behaviors/characters-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/email-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/event-to-command-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/index.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/masked-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/maximum-length-reached-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/numeric-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/progressbar-animation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/required-string-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/set-focus-when-entry-completed-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/text-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/uri-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/user-stopped-typing-behavior.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

PRMerger Results

Issue
Description

Added File(s)
This PR contains added files. New files require human review.

Yaml File(s)
This PR includes changes to .yml file(s) owned by another author.

Changed Files
This PR contains more than 10 changed files.

File Change Percent
This PR contains file(s) with more than 20% file change.

Index File
This PR contains a change to the index file.

Docs Build status updates of commit 3d143e2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/maui/TOC.yml
:white_check_mark:Succeeded
View

docs/maui/behaviors/characters-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/email-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/event-to-command-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/index.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/masked-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/maximum-length-reached-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/numeric-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/progressbar-animation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/required-string-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/set-focus-when-entry-completed-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/text-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/uri-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/user-stopped-typing-behavior.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

PRMerger Results

Issue
Description

Added File(s)
This PR contains added files. New files require human review.

Yaml File(s)
This PR includes changes to .yml file(s) owned by another author.

Changed Files
This PR contains more than 10 changed files.

File Change Percent
This PR contains file(s) with more than 20% file change.

Index File
This PR contains a change to the index file.

Docs Build status updates of commit ea812d0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/maui/TOC.yml
:white_check_mark:Succeeded
View

docs/maui/behaviors/characters-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/email-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/event-to-command-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/index.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/masked-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/maximum-length-reached-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/numeric-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/progressbar-animation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/required-string-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/set-focus-when-entry-completed-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/text-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/uri-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/user-stopped-typing-behavior.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

PRMerger Results

Issue
Description

Added File(s)
This PR contains added files. New files require human review.

Yaml File(s)
This PR includes changes to .yml file(s) owned by another author.

Changed Files
This PR contains more than 10 changed files.

File Change Percent
This PR contains file(s) with more than 20% file change.

Index File
This PR contains a change to the index file.

Docs Build status updates of commit 9f1173f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/maui/TOC.yml
:white_check_mark:Succeeded
View

docs/maui/behaviors/characters-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/email-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/event-to-command-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/index.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/masked-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/maximum-length-reached-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/numeric-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/progressbar-animation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/required-string-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/set-focus-when-entry-completed-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/text-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/uri-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/user-stopped-typing-behavior.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

PRMerger Results

Issue
Description

Added File(s)
This PR contains added files. New files require human review.

Yaml File(s)
This PR includes changes to .yml file(s) owned by another author.

Changed Files
This PR contains more than 10 changed files.

File Change Percent
This PR contains file(s) with more than 20% file change.

Index File
This PR contains a change to the index file.


Add validation support for inputs

This PR is implementing base for refactoring of #1121 with including of vee-validate and example of using in send screen.

Tested in Chrome, FF, Safari, Brave browsers, LGTM.


Handle propTables=false properly

The propTables prop is an array type but the option
may be set to false. Change it to null to avoid warnings

Related issue: https://github.com/kadirahq/react-storybook-addon-info/issues/47


Svelte support

Describe the feature
Do you have any plans for supporting svelte in near future?

In the future yes. In the near future....probably not. We have a few other high priority things on the burner, but I appreciate the request!


Dynamic fields

I have a form where some fields are dynamically created, some of the dynamic fields are required and some are optional,
I couldn’t find a way to make vest support this use case, any suggestions?

Not knowing much about your specific use-case (maybe share a more detailed example?), but just from the overall description, it seems like you require something of that sort: A combination of each+optional
https://vestjs.dev/docs/writing_tests/advanced_test_features/dynamic_tests - allows you to iterate over a list of values to create dynamic tests
https://vestjs.dev/docs/writing_your_suite/optional_fields - allows you to set values as optional so they do not set the form to become invalid

I appreciate your quick response!
I will share with you more details -
My form library is Felete and my validator is Vest.
There are some fields in my form that are not consts and I'm getting them at runtime (I don't have the fields names)
It looks something like this:
[
{name: "address" , required: true},
{name: "building_number", required: false},
...
]

Is there a way to create a dynamic suite that gets data on the fly?

each(data.fields, field => {
    optional(field.name)
    test(
      field.name,
      'item price must be greater than 0',
      () => {
        enforce(field.price).isNumeric().greaterThan(0);
      },
    );
});

@ealush is this how you would write these validation tests? Combining each and optional this way doesn't seem to work (i.e., the fields aren't marked as optional).

@swithek I just ran a test with the exact scenario that you mentioned, and I can confirm it works correctly: https://codesandbox.io/s/react-forked-0bobdc?file=/src/suite.js
Type in Req_1 and Req_2, and you'll see that the submit button lights up, even though you did not fill out the optional field.
I believe that what you're experiencing is this:
You type in the optional field, and then remove its content. In this scenario, the field is indeed not valid any more.
It all boils down to what optional really means in your app's context, and what qualifies as optional-satisfying-test.
Let me explain:
If the field is empty, does that qualify for optional? Maybe. But what if the user typed inside the field and then removed its content - is that qualify as optional? Maybe in your app, the field is optional only if some other condition applies, for example - when another field has been filled...
As you see, optional can mean different things in different context. As I mentioned in a previous answer a couple of weeks back, Vest doesn't have a notion of your apps logic, or in other words - Vest has no knowledge of "what should happen now", it also doesn't make sense of your data, so marking a certain field as optional, doesn't mean Vest is going to check the data properties passed to it, because you may name them whatever you want.
Instead, a different approach is taken in Vest, assuming it isn't aware of your business logic.
Vest determines whether a field qualifies as optional by a certain rule: did it have any test runs?
Meaning, if a test of a certain field did indeed run, it will be regarded as required, because its tests were triggered.

or, in other words - Vest allows the Suite to be regarded as valid, if the fields marked as optional did not run at all.

Thank you for your quick reply @ealush! What you're saying makes complete sense, however, as specified in the docs, you can have custom rules that determine whether the field should be optional or not, is that correct? If that's the case, shouldn't having
optional({
    optional: !data["optional"],
});

be enough cover all the empty value/undefined field cases, even when there are existing validation results from previous runs? This doesn't seem to work when each is used. Maybe I'm missing something?
Here's an example based on your example: https://codesandbox.io/s/react-forked-oy06l8?file=/src/suite.js

I will have to dig deeper to see why that specific case didn't work for you, but just to unblock you now - using a function should solve it for you.
    optional({
      optional: () => !data. Optional
    });

https://codesandbox.io/s/react-forked-hpry5u?file=/src/suite.js


Check on the compatibility with Midi-QOL

Midi-QOL has built in integration for the cover features of dnd5e helpers. It may just be a matter of tposney detecting the name of the new module in order to enable the features again if nothing significantly changed in the API.

I've spoken to Tim and he'll chaneg his checks to use my module instead


Update doc

to introduce:

manual_correction.py

Fixed by https://github.com/spine-generic/spine-generic/pull/122


Show underlying Types of alias Types.

Is your feature request related to a problem? Please describe.
Its very annoying when i make types alias's for ease of documentation/domain modeling and it then completely obscures what the underlying type actually is.
Describe the solution you'd like
I would like an option to show the underlying types of aliases both in intellisense popups/hovering and also in the inline auto-generated type annotations
Example
type id = int
type location= id list
type hierarchy= Dictionary<location,item>

I think a good idea for type annotations and intellisene displaying would be something along these lines
hierarchy{Dictionary<location{id {int} list},item>}
or even just one level deep like:
hierarchy{Dictionary<location,item>}

I don't think Ionide should do this. The goal of type abbreviations is to provide a different name for something as an abstraction. Showing the implementation details of that abstraction doesn't feel right. If it's awkward to use because tooling doesn't show the implementation details, then that's probably a sign that the type alias wasn't a good choice.
You should still get a tooltip if you hover over the name of the alias itself, though.
type Doot = int -> int -> int

let f (d: Doot) = ()

Hovering over Doot in the f definition should probably show a tooltip like so:
type Doot = int -> int -> int

That's what VS tooltips do and it's probably the right call.
I noticed that Ionide doesn't do that today, so that would feel like the right feature request to me.
The code to do that would lie in FsAutocomplete - https://github.com/fsharp/FsAutoComplete/blob/master/src/FsAutoComplete.Core/TipFormatter.fs

The code to do that would lie in FsAutocomplete - ~https://github.com/fsharp/FsAutoComplete/blob/master/src/FsAutoComplete.Core/TipFormatter.fs~

https://github.com/fsharp/FsAutoComplete/blob/master/src/FsAutoComplete.Core/SignatureFormatter.fs

yeehaw

It's actually interesting that we don't show any tooltip for Doop 🤔

Yep, a bug in there I guess? I don't recall ever intentionally hovering over type aliases in Ionide before so I can't say.
The signature does show in a completion list though, so when you're typing out f you'll see the correct Doop signature as you are typing it.

I hear what your saying about aliases but let me give a great example of why it does make sense. (Though I do think just that hover working correctly would make a big difference). Say I make a type alias jobID that is an int. Internally I don't what it to be just any old int I want it to be obvious what that int is in my type definitions and when passing it into functions. And maybe at some point I might even change it from an in t to a guid or something. But when I want to cast outside received data into a jobID if I can't see the type I have to look at the implementation.
Another good example is using a few dictionary's as a simple database. An alias is great so you don't have to write out a monster type signature, but a pain because upon hovering over the variable it has no info about what it actually is.
But I'll  take my feature request fsautocomplete, even if it doesn't get approved, seems useful to have it for posterity

Closing it here, we have an issue in FSAC repo.


[BUG] Course editor can't be reached

OS: Windows 10
CPU/GPU: irrelevant I think
Please give your StepMania Info
StepMania Version: 4.8.2
Theme: Default
Describe the problem
Clicking on "Edit Courses/Mods" takes you to the "Edit Songs/Steps" screen
Describe what should happen
I was expecting a different interface which would allow editing of a course (although I remember the course interface being broken in 5.1)

The course editor seems to be broken;
For now, it may be better to use a different program to work on the courses.


Anime homepage errors out in IE 11

SCRIPT5007: Object expected
anime.min.js (18,295)

Same error happens after an animation:
var scrollTo = $("#some-element-on-the-page");
anime({
targets: "html, body",
scrollTop: scrollTo.offset().top,
duration: 1200,
easing: 'easeOutQuart'
});

Yeah, same issue here.

It was the promise, will be fixed in 2.0.2

Error still appears in anime.js v3.0.1

I see it as well, IE11.

I am also experiencing this issue - exactly the same as previously reported in both v3.0.1 & v3.1.0

Have the same issue in v3.1.0 + IE11


Enable consolidate blocks to to work with single gate blocks

Summary
This commit updates the ConsolidateBlocks pass to also consolidate a
block if it's outside of the target basis. A use case for the
consolidate blocks pass is part of the synthesis basis translation
method where it is expected to convert all gates outside of the
specified basis set to a unitary so that can be synthesized to the
target basis. This was not worker though because the consolidate blocks
pass would not ever convert a single gate block to a unitary. This
commit fixes that by adding additional conditions to the consolidate
blocks pass to convert a single gate block to a unitary if it is outside
the target basis, and is actually a gate with a matrix defined (so we
can use that for the unitary gate) otherwise the behavior remains
unchanged.
Details and comments
Fixes #5203

@mtreinish here is the alternative PR: #6036
It makes the main loop handle the 1-length block by identifying the condition when consolidation is not wanted (as per offline conversation with @kdk). Feel free to ignore if you find it more complicated.


Why v-bind="$attrs" cannot replace the declared same name props in front of itself?

Version
2.6.11
Reproduction link
https://codesandbox.io/s/cocky-brahmagupta-ejn2z
Steps to reproduce
See the codesandbox result~
What is expected?
In my opinion and normal thoughts, if v-bind="$attrs" or v-bind="$props" is behind a declared and in same name property, it should replace the property value ahead.
Test

if $attrs contain the property named 'href', In the normal thoughts, it should replace the data ahead.
What is actually happening?
Cannot replace.

Am I wrong?
Or Hmmm... v-bind="$attrs" take the lower priority of the normal v-bind:href="__"?

In Vue 3, the order of attributes matter but in Vue 2 they don't and a single attribute is more specific that a v-bind. See https://github.com/vuejs/vue/issues/7811

In Vue 3, the order of attributes matter but in Vue 2 they don't and a single attribute is more specific that a v-bind. See https://github.com/vuejs/vue/issues/7811

OK. Thank you. @posva.
I left a version3 demo.
https://codesandbox.io/s/brave-rubin-gofp0

OK. Thank you. @posva.
I left a version3 demo.
https://codesandbox.io/s/brave-rubin-gofp0


Canvas: trying to draw too large(144000000bytes) bitmap on CarbonROM flashed phone

Hi, I am new to Flutter. Before I have developed many Android apps. My app crashes in some Android devices. All logs are here. I've tested in following devices.
OnePlust 7T: works
Samsung Galaxy A50: works
Emulator: works
Sony Xperia Z2: crashes.

Android Logcat
2020-03-08 01:28:32.227 15257-15257/com.mobiaxe.wasd E/AndroidRuntime: FATAL EXCEPTION: main
    Process: com.mobiaxe.wasd, PID: 15257
    java.lang.RuntimeException: Canvas: trying to draw too large(144000000bytes) bitmap.
        at android.view.DisplayListCanvas.throwIfCannotDraw(DisplayListCanvas.java:229)
        at android.view.RecordingCanvas.drawBitmap(RecordingCanvas.java:97)
        at android.graphics.drawable.BitmapDrawable.draw(BitmapDrawable.java:529)
        at android.view.View.getDrawableRenderNode(View.java:19454)
        at android.view.View.drawBackground(View.java:19390)
        at android.view.View.draw(View.java:19187)
        at com.android.internal.policy.DecorView.draw(DecorView.java:788)
        at android.view.View.updateDisplayListIfDirty(View.java:18146)
        at android.view.ThreadedRenderer.updateViewTreeDisplayList(ThreadedRenderer.java:669)
        at android.view.ThreadedRenderer.updateRootDisplayList(ThreadedRenderer.java:675)
        at android.view.ThreadedRenderer.draw(ThreadedRenderer.java:783)
        at android.view.ViewRootImpl.draw(ViewRootImpl.java:2992)
        at android.view.ViewRootImpl.performDraw(ViewRootImpl.java:2806)
        at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:2359)
        at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1392)
        at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:6752)
        at android.view.Choreographer$CallbackRecord.run(Choreographer.java:911)
        at android.view.Choreographer.doCallbacks(Choreographer.java:723)
        at android.view.Choreographer.doFrame(Choreographer.java:658)
        at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:897)
        at android.os.Handler.handleCallback(Handler.java:790)
        at android.os.Handler.dispatchMessage(Handler.java:99)
        at android.os.Looper.loop(Looper.java:164)
        at android.app.ActivityThread.main(ActivityThread.java:6499)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:440)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)

Flutter Verbose[  +16 ms] executing: [/home/abdullah/Flutter/flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +21 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] 0b8abb4724aa590dd0f429683339b1e045a1594d
[        ] executing: [/home/abdullah/Flutter/flutter/] git describe --match v*.*.* --first-parent --long --tags
[   +4 ms] Exit code 0 from: git describe --match v*.*.* --first-parent --long --tags
[        ] v1.12.13+hotfix.8-0-g0b8abb472
[   +5 ms] executing: [/home/abdullah/Flutter/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[   +4 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/stable
[        ] executing: [/home/abdullah/Flutter/flutter/] git ls-remote --get-url origin
[   +4 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +33 ms] executing: [/home/abdullah/Flutter/flutter/] git rev-parse --abbrev-ref HEAD
[   +4 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] stable
[  +61 ms] executing: /home/abdullah/Android/Sdk/platform-tools/adb devices -l
[   +6 ms] Exit code 0 from: /home/abdullah/Android/Sdk/platform-tools/adb devices -l
[        ] List of devices attached
           BH905Q8517             device usb:3-10.1 product:D6503 model:Xperia_Z2 device:sirius transport_id:1
           emulator-5554          device product:sdk_gphone_x86 model:Android_SDK_built_for_x86 device:generic_x86 transport_id:2
[  +13 ms] /home/abdullah/Android/Sdk/platform-tools/adb -s BH905Q8517 shell getprop
[ +118 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[   +3 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +1 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.

[        ] Xperia Z2 startApp
[   +1 ms] executing: /home/abdullah/Android/Sdk/platform-tools/adb -s BH905Q8517 shell am start -a android.intent.action.RUN -f 0x20000000 --ez enable-background-compilation true --ez enable-dart-profiling true --ez enable-checked-mode true --ez verify-entry-points true com.mobiaxe.wasd/com.mobiaxe.wasd.MainActivity
[ +102 ms] Starting: Intent { act=android.intent.action.RUN flg=0x20000000 cmp=com.mobiaxe.wasd/.MainActivity (has extras) }
[        ] Waiting for observatory port to be available...
[ +228 ms] D/FlutterActivity(15257): Using the launch theme as normal theme.
[   +3 ms] D/FlutterActivityAndFragmentDelegate(15257): Setting up FlutterEngine.
[        ] D/FlutterActivityAndFragmentDelegate(15257): No preferred FlutterEngine was provided. Creating a new FlutterEngine for this FlutterFragment.
[ +230 ms] D/FlutterActivityAndFragmentDelegate(15257): Attaching FlutterEngine to the Activity that owns this Fragment.
[ +459 ms] Observatory URL on device: http://<IP_ADDRESS>:59357/H6q4IHLSQLg=/
[   +3 ms] executing: /home/abdullah/Android/Sdk/platform-tools/adb -s BH905Q8517 forward tcp:0 tcp:59357
[  +12 ms] 38403
[        ] Forwarded host port 38403 to device port 59357 for Observatory
[   +6 ms] Connecting to service protocol: http://<IP_ADDRESS>:38403/H6q4IHLSQLg=/
[ +139 ms] D/FlutterView(15257): Attaching to a FlutterEngine: io.flutter.embedding.engine.FlutterEngine@cc181eb
[  +47 ms] D/FlutterActivityAndFragmentDelegate(15257): Executing Dart entrypoint: main, and sending initial route: /
[ +444 ms] Successfully connected to service protocol: http://<IP_ADDRESS>:38403/H6q4IHLSQLg=/
[   +2 ms] Sending to VM service: getVM({})
[   +7 ms] Result: {type: VM, name: vm, architectureBits: 32, hostCPU: Qualcomm MSM8974PRO-AB, operatingSystem: android, targetCPU: arm, version: 2.7.0 (Fri Dec 6 16:26:51 2019 +0100) on "android_arm", _profilerMode: VM, _nativeZoneMemoryUsage: 0, pid: 15257, startT...
[   +3 ms] Sending to VM service: getIsolate({isolateId: isolates/3983678871753151})
[   +2 ms] Sending to VM service: _flutter.listViews({})
[  +69 ms] Result: {type: FlutterViewList, views: [{type: FlutterView, id: _flutterView/0x9b1c9890, isolate: {type: @Isolate, fixedId: true, id: isolates/3983678871753151, name: main.dart$main-3983678871753151, number:<PHONE_NUMBER>753151}}]}
[   +7 ms] DevFS: Creating new filesystem on the device (null)
[        ] Sending to VM service: _createDevFS({fsName: wasd})
[  +14 ms] Result: {type: Isolate, id: isolates/3983678871753151, name: main, number:<PHONE_NUMBER>753151, _originNumber:<PHONE_NUMBER>753151, startTime:<PHONE_NUMBER>955, _heaps: {new: {type: HeapSpace, name: new, vmName: Scavenger, collections: 1, avgCollectionPeriodMillis...
[  +80 ms] Result: {type: FileSystem, name: wasd, uri: file:///data/user/0/com.mobiaxe.wasd/code_cache/wasdLJJDTQ/wasd/}
[        ] DevFS: Created new filesystem on the device (file:///data/user/0/com.mobiaxe.wasd/code_cache/wasdLJJDTQ/wasd/)
[   +3 ms] Updating assets
Debug service listening on ws://<IP_ADDRESS>:38403/H6q4IHLSQLg=/ws
Syncing files to device Xperia Z2...
[  +65 ms] Scanning asset files
[   +1 ms] <- reset
[        ] Compiling dart to kernel with 0 updated files
[   +5 ms] /home/abdullah/Flutter/flutter/bin/cache/dart-sdk/bin/dart /home/abdullah/Flutter/flutter/bin/cache/artifacts/engine/linux-x64/frontend_server.dart.snapshot --sdk-root /home/abdullah/Flutter/flutter/bin/cache/artifacts/engine/common/flutter_patched_sdk/ --incremental --target=flutter -Ddart.developer.causal_async_stacks=true --output-dill /tmp/flutter_tool.UIFTVW/app.dill --packages /home/abdullah/StudioProjects/wasd/.packages -Ddart.vm.profile=false -Ddart.vm.product=false --bytecode-options=source-positions,local-var-info,debugger-stops,instance-field-initializers,keep-unreachable-code,avoid-closure-call-instructions --enable-asserts --track-widget-creation
[   +8 ms] <- compile package:wasd/main.dart
[ +544 ms] D/vndksupport(15257): Loading<EMAIL_ADDRESS>from current namespace instead of sphal namespace.
[        ] D/vndksupport(15257): Loading /vendor/lib/hw/gralloc.msm8974.so from current namespace instead of sphal namespace.

Flutter Doctor
[✓] Flutter (Channel stable, v1.12.13+hotfix.8, on Linux, locale en_US.UTF-8)
    • Flutter version 1.12.13+hotfix.8 at /home/abdullah/Flutter/flutter
    • Framework revision 0b8abb4724 (4 weeks ago), 2020-02-11 11:44:36 -0800
    • Engine revision e1e6ced81d
    • Dart version 2.7.0

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /home/abdullah/Android/Sdk
    • Android NDK location not configured (optional; useful for native profiling
      support)
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /home/abdullah/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

[✓] Android Studio (version 3.6)
    • Android Studio at /home/abdullah/android-studio
    • Flutter plugin version 44.0.2
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)

[✓] Connected device (2 available)
    • Xperia Z2                 • BH905Q8517    • android-arm • Android 8.1.0
      (API 27)
    • Android SDK built for x86 • emulator-5554 • android-x86 • Android 10 (API
      29) (emulator)

• No issues found!

main.dart
import 'package:flutter/material.dart';
import 'package:wasd/onboarding.dart';
import 'strings.dart';

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

class WASD extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: Strings.appTitle,
      theme: ThemeData(
        primaryColor: Colors.white
      ),
      initialRoute: Strings.navOnboarding,
      routes: {
        Strings.navOnboarding: (context) => Onboarding()
      },
    );
  }
}

onboarding.dart
import 'package:flutter/material.dart';
import 'package:wasd/select_platform.dart';
import 'strings.dart';

class Onboarding extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return PageView(
      children: <Widget>[
        PagerPage(path: Strings.pathWitcherJpg, title: Strings.titlePageOne, description: Strings.subtitlePageOne),
        PagerPage(path: Strings.pathGodofwarJpg, title: Strings.titlePageTwo, description: Strings.subtitlePageTwo),
        PagerPage(path: Strings.pathRdrJpg, title: Strings.titlePageThree, description: Strings.subtitlePageThree),
        SelectPlatform()
      ],
    );
  }
}

class PagerPage extends StatelessWidget {
  final String path;
  final String title;
  final String description;

  PagerPage({Key key, this.path, this.title, this.description})
      : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Stack(
      children: <Widget>[
        Image.asset(
          path,
          height: MediaQuery.of(context).size.height,
          width: MediaQuery.of(context).size.width,
          fit: BoxFit.fill,
        ),
        Container(
          alignment: Alignment.bottomCenter,
          padding: EdgeInsets.only(bottom: 120.0),
          child: Column(
            mainAxisAlignment: MainAxisAlignment.end,
            crossAxisAlignment: CrossAxisAlignment.center,
            children: <Widget>[
              Padding(
                  child: Text(
                    title,
                    style: TextStyle(
                        color: Colors.white,
                        fontSize: 34.0,
                        decoration: TextDecoration.none),
                  ),
                  padding: EdgeInsets.only(bottom: 32.0)),
              Text(
                  description,
                  textAlign: TextAlign.center,
                  style: TextStyle(
                      color: Colors.white,
                      fontSize: 20.0,
                      decoration: TextDecoration.none)),
            ],
          ),
        )
      ],
    );
  }
}

This sample image is used in app.
https://i.imgur.com/n9qBj7S.jpg

Could you please share some sample code that reproduces this issue?
Are you just trying to render an image that's too large?  Or have you created some non-raster-image widget that is leading to this?

Right now, it's not clear if your app is just trying to do something it shouldn't (e.g. render a really high resolution image at full resolution), or if you've found an issue with Flutter.

Could you please share some sample code that reproduces this issue?
Are you just trying to render an image that's too large? Or have you created some non-raster-image widget that is leading to this?

Hi @dnfield, I updated my issue.

Tested this code sample, reproduce no issue. Could be device specific

Code Sample
import 'package:flutter/material.dart';

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

class WASD extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      theme: ThemeData(primaryColor: Colors.white),
      home: Onboarding(),
    );
  }
}

class Onboarding extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return PageView(
      children: <Widget>[
        PagerPage(
            path: 'https://i.imgur.com/n9qBj7S.jpg',
            title: 'Page one',
            description: 'Subtitle PageOne'),
        PagerPage(
            path: 'https://i.imgur.com/n9qBj7S.jpg',
            title: 'Page Two',
            description: 'Subtitle PageTwo'),
        PagerPage(
            path: 'https://i.imgur.com/n9qBj7S.jpg',
            title: 'Page Three',
            description: 'Subtitle PageThree'),
      ],
    );
  }
}

class PagerPage extends StatelessWidget {
  final String path;
  final String title;
  final String description;

  PagerPage({Key key, this.path, this.title, this.description})
      : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Stack(
      children: <Widget>[
        Image.network(
          path,
          height: MediaQuery.of(context).size.height,
          width: MediaQuery.of(context).size.width,
          fit: BoxFit.fill,
        ),
        Container(
          alignment: Alignment.bottomCenter,
          padding: EdgeInsets.only(bottom: 120.0),
          child: Column(
            mainAxisAlignment: MainAxisAlignment.end,
            crossAxisAlignment: CrossAxisAlignment.center,
            children: <Widget>[
              Padding(
                  child: Text(
                    title,
                    style: TextStyle(
                        color: Colors.white,
                        fontSize: 34.0,
                        decoration: TextDecoration.none),
                  ),
                  padding: EdgeInsets.only(bottom: 32.0)),
              Text(description,
                  textAlign: TextAlign.center,
                  style: TextStyle(
                      color: Colors.white,
                      fontSize: 20.0,
                      decoration: TextDecoration.none)),
            ],
          ),
        )
      ],
    );
  }
}

Screenshot

Tested this code sample, reproduce no issue. Could be device specific
Code Sample
Screenshot

You seem to use network image. I used this image from my assets. Please download image to assets folder and use from there.

Hi @abalta
I have tested with asset image too found no issue in issue in emulator to confirm, this could be device specific issue and added network image for easy testing for others .
Thank you

The compilation paths are different for simulator and real device.

You're missing Strings.dart and select_platform.dart.

If you run flutter clean and try again does the problem go away?
Does it reproduce in a fresh project?

You're missing Strings.dart and select_platform.dart.

Hi, @dnfield here are string.dart and selectplatform.dart files.

strings.dart
class Strings {

  static String appTitle = "WASD";

  //routes
  static String navOnboarding = '/onboarding';

  //assets path
  //jpgs
  static String pathWitcherJpg = 'assets/witcher_bg.jpg';
  static String pathGodofwarJpg = 'assets/godofwar_bg.jpg';
  static String pathRdrJpg = 'assets/rdr_bg.jpg';
  static String pathSelectPlatformBgJpg = 'assets/platform_bg.jpg';

  //svgs
  static String pathWindowsSvg = 'assets/ic_windows.svg';
  static String pathPS4Svg = 'assets/ic_ps4.svg';
  static String pathXboxSvg = 'assets/ic_xbox.svg';
  static String pathNintendoSvg = 'assets/ic_nintendo.svg';

  //onboarding
  static String titlePageOne = 'Keşfet';
  static String subtitlePageOne = 'Popüler oyunları keşfet\nÇıkacak oyunları takip et';
  static String titlePageTwo = 'Oyna';
  static String subtitlePageTwo = 'Oynadığın oyunları listene ekle\nYorum yap, beğen';
  static String titlePageThree = 'Oyuncu Ol';
  static String subtitlePageThree = 'Casual, Pro, Hardcore sen hangi oyuncusun?';

  //select platform
  static String selectYourPlatform = 'Platformunu Seç';
  static String pc = 'PC';
  static String playStation = 'Play Station';
  static String xbox = 'Xbox';
  static String nintendo = 'Nintendo';
}

select_platform.dart
import 'package:flutter/material.dart';
import 'package:flutter_svg/flutter_svg.dart';

import 'strings.dart';

class SelectPlatform extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Stack(
      children: <Widget>[
        Image.asset(
          Strings.pathSelectPlatformBgJpg,
          height: MediaQuery.of(context).size.height,
          width: MediaQuery.of(context).size.width,
          fit: BoxFit.cover,
        ),
        Container(
          alignment: Alignment.topCenter,
          padding: EdgeInsets.all(16.0),
          child: Column(
            children: <Widget>[
              Padding(
                padding: const EdgeInsets.only(top: 64.0),
                child: Text(Strings.selectYourPlatform,
                    style: TextStyle(
                        color: Colors.white,
                        fontSize: 34.0,
                        decoration: TextDecoration.none)),
              ),
              Padding(
                padding: const EdgeInsets.only(top: 32.0),
                child: Row(
                  mainAxisAlignment: MainAxisAlignment.spaceEvenly,
                  children: <Widget>[
                    Platform(Strings.pc, Strings.pathWindowsSvg),
                    Platform(Strings.playStation, Strings.pathPS4Svg)
                  ],
                ),
              ),
              Row(
                mainAxisAlignment: MainAxisAlignment.spaceEvenly,
                children: <Widget>[
                  Platform(Strings.xbox, Strings.pathXboxSvg),
                  Platform(Strings.nintendo, Strings.pathNintendoSvg)
                ],
              )
            ],
          ),
        )
      ],
    );
  }
}

class Platform extends StatefulWidget {
  final String label;
  final String asset;

  Platform(this.label, this.asset);

  @override
  PlatformState createState() => PlatformState(label, asset);
}

class PlatformState extends State<Platform> {
  bool isSelected = false;
  String label;
  String asset;

  PlatformState(this.label, this.asset);

  @override
  Widget build(BuildContext context) {
    return _buildFlexibleCard(label, asset, isSelected);
  }

  Flexible _buildFlexibleCard(String label, String asset, bool isSelected) {
    return Flexible(
        flex: 1,
        fit: FlexFit.tight,
        child: Padding(
          padding: const EdgeInsets.all(8.0),
          child: GestureDetector(
            onTap: () {
              _selectPlatform();
            },
            child: Container(
              padding: const EdgeInsets.all(16.0),
              decoration: BoxDecoration(
                  borderRadius: BorderRadius.all(Radius.circular(8.0)),
                  color: Color(0x99222d45)),
              child: Stack(
                children: <Widget>[
                  Center(
                    child: Column(
                      children: <Widget>[
                        SvgPicture.asset(asset, width: 64, height: 64),
                        Padding(
                          padding: const EdgeInsets.only(top: 8.0),
                          child: Text(label,
                              style: TextStyle(
                                  color: Colors.white,
                                  fontSize: 16.0,
                                  decoration: TextDecoration.none)),
                        )
                      ],
                    ),
                  ),
                  Visibility(
                      visible: isSelected,
                      child: Positioned(
                          top: 0,
                          right: 0,
                          child: SvgPicture.asset('assets/ic_tick.svg',
                              width: 24, height: 24, color: Colors.white)))
                ],
              ),
            ),
          ),
        ));
  }

  void _selectPlatform() {
    setState(() {
      isSelected = !isSelected;
    });
  }
}

Hi @abalta
I have tested with asset image too, found no issue in issue in emulator to confirm, this could be device specific issue and added network image for easy testing for others .
Thank you

Maybe, because this device (Sony Xperia Z2) is rooted with custom rom. (https://get.carbonrom.org/device-sirius.html)

@abalta is the ROM you're running certified for use with the PlayStore?  If not, that could very well be why this is crashing, and I don't think we'll be able to fix this issue.

Looking into this a bit more - CarbonROM does not appear to be certified with the PlayStore, we do not have any devices to test with this ROM, and it's not clear whether this is a bug in CarbonROM or the engine.
Given that your app seems to be working fine on stock Android, I'm moving this over tot he Future milestone.  I don't expect anyone will be actively working on this, unless they're also encountering this issue on a CarbonROM flashed phone.  I am not aware of any active team members who do have access to such a device right now.

Looking into this a bit more - CarbonROM does not appear to be certified with the PlayStore, we do not have any devices to test with this ROM, and it's not clear whether this is a bug in CarbonROM or the engine.
Given that your app seems to be working fine on stock Android, I'm moving this over tot he Future milestone. I don't expect anyone will be actively working on this, unless they're also encountering this issue on a CarbonROM flashed phone. I am not aware of any active team members who do have access to such a device right now.

Thanks @dnfield and @TahaTesser. İt is good to be fine on future milestone. Maybe, future releases of CarbonRom fixed this kind of issues.

I created new flutter default project from curiosity and then run CarbonRom flashed device, it works.  I think, something else caused crashes instead of images.

Right - your whole stack trace is in Java code, and it is not Java code from Flutter.

Sony Xperia Z2: crashes.

This specific device model and make seems to be discontinued per https://www.gsmarena.com/sony_xperia_z2-6144.php
Also, considering the age of this issue and no activity since the last comment that was 4 years ago, I will consider this issue now as obsolete and will close as stale.
If anybody still sees the same crash using latest stable version on similar device make and model, file a new issue with relevant details.


Scene Graph?

https://en.wikipedia.org/wiki/Scene_graph
https://docs.unity3d.com/Manual/Hierarchy.html
https://archive.gamedev.net/archive/reference/programming/features/scenegraph/index.html

[ ] SceneGraph:

[ ] Transformation support.
[ ] Audio Support
[] Graphics Support
[ ] ECS Support


Undefined Very Easy Judgment

https://github.com/m8nscape/lunaticvibes/issues/45

clone failure

Clone failure also in VS2022

There are Judgment tables for LV
#RANK 5 is IIDX judge

New judgment rank.zip

origin is nanasigroove from https://hitkey.nekokan.dyndns.info/cmds.htm


Changes and corrupts everything

Describe the bug
I just ask him to make certain changes and he changes the whole code and changes the parts that are working properly. This leads to spending more tokens and not getting my money's worth.
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-m5qphh
Steps to reproduce

I just asked him to add an analysis type. 2. He changed the other parts and the whole code broke

Expected behavior
Only the desired changes should be made. parts that work properly should not be changed.
Screen Recording / Screenshot
No response
Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 131
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 140722385,
  "usedJSHeapSize": 131576657,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = hhurma
Chat ID = 1e02aa45ab6b

Additional context
No response

Sorry to hear this! You can prevent Bolt from making changes to specific files by right-clicking and selecting "Lock file". You can read more here.


Instruction to extension (WIP)

Add instructions to extend OpenAgents in README

[x] Code structure explanation (@WhiteWolf82 add frontend part)
[x] Extension to a new agent. (@WhiteWolf82 add frontend part)
[x] Extension to a new LLM (@SivilTaram add LLM hosting tutorial)
[x] Extension to a new tool
[x] Update news
[x] Update contributing notice at the front
[x] Sync to all READMEs

Request @Timothyxxx to review

LGTM!


Error while initializing the database (superset db upgrade) for superset in editable mode.

While trying to install Superset in the editable mode on running superset db upgrade, I keep running into this issue where the value being passed to the uuid module is a 'function' object instead of a string, which isn't the expected type giving this error:
Error Log:
File "/Users/tannishtha./superset/superset-local-editable-7/lib/python3.9/site-packages/sqlalchemy/sql/type_api.py", line 1631, in process
    return impl_processor(process_param(value, dialect))
  File "/Users/tannishtha./superset/superset-local-editable-7/lib/python3.9/site-packages/sqlalchemy_utils/types/uuid.py", line 86, in process_bind_param
    value = self._coerce(value)
  File "/Users/tannishtha./superset/superset-local-editable-7/lib/python3.9/site-packages/sqlalchemy_utils/types/uuid.py", line 65, in _coerce
    value = uuid.UUID(value)
  File "/Users/tannishtha./opt/anaconda3/lib/python3.9/uuid.py", line 174, in __init__
    hex = hex.replace('urn:', '').replace('uuid:', '')
sqlalchemy.exc.StatementError: (builtins.AttributeError) 'function' object has no attribute 'replace'
[SQL: UPDATE sl_tables SET uuid=?, changed_on=? WHERE sl_tables.id = ?]
[parameters: [{'uuid': <function uuid4 at 0x7fd2b9d770d0>, 'sl_tables_id': 1}, {'uuid': <function uuid4 at 0x7fd2b9d770d0>, 'sl_tables_id': 2}, {'uuid': <function  ... (1143 characters truncated) ... l_tables_id': 20}, {'uuid': <function uuid4 at 0x7fd2b9d770d0>, 'sl_tables_id': 21}, {'uuid': <function uuid4 at 0x7fd2b9d770d0>, 'sl_tables_id': 22}]]

Since, I'm installing in the editable mode, the versions of the external dependencies are as specified in the requirements/testing.txt file.

browser type and version: Safari Version 16.0
superset version: Superset 0.0.0-dev
python version: Python 3.9.13
node.js version: v12.17.0
any feature flags active:

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[✅ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[ ✅] I have reproduced the issue with at least the latest released version of superset.
[✅ ] I have checked the issue tracker for the same issue and I haven't found one similar.

whats the correct superset version?
Superset 0.0.0-dev will show on every superset version if its run with development mode.

It's the latest release, did a git clone from the master branch today.  @mayurnewase

It's not giving the same error on a different machine with python version 3.9.7. Tried downgrading python to 3.9.7 but it's still giving the same error.

Well, not sure if it will be helpful for other as I'm using teh amancevice/superset docker image but I had to move first to 1.5.1 then to 2.0.0 run db upgrades, and finally move 2.1.0 to be able to run all db migrations.

Since we're now on 3.1, on the verge of 4.0, we're not supporting 2.x  or prior versions actively. If anyone is experiencing this issue in current versions, please file a new issue with updated context and repro steps. Thank you for understanding :)

Maybe @dpgaspar or @villebro might know something about the uuid issue?

It's been another four months since this was reopened without comment. If @wisefool769 or anyone else on the thread wants to dig deeper and tackle any of this with a PR, I'm more than happy to reopen this again. Meanwhile, we're just trying to keep the backlog more active/actionable :D


Merge SIL tested functions into master.

Add TRIAD, magnetometer bias estimation, quaternion bug fixes and corresponding tests into master.

Looks good to me


JournalEnabled parameter is incorrect

-JournalEnabled
The JunkEmailEnabled parameter specifies whether the Junk Email folder and junk email management are available in Outlook on the web.
$true: The Junk Email folder and junk email management are available in Outlook on the web. This is the default value.
$false: The Junk Email folder and junk email management aren't available in Outlook on the web.

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

ID: be262e6d-2342-9d63-e807-ad931f15b847
Version Independent ID: b20464e1-8659-1d1c-5010-c73526f440ca
Content: Set-OwaVirtualDirectory (exchange)
Content Source: exchange/exchange-ps/exchange/client-access-servers/Set-OwaVirtualDirectory.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@vboyev-MSFT, do you have a correct description that you would want me to use instead?

@vboyev-MSFT, ugh; I didn't read closely enough. Clearly, that's a copy/paste error talking about the JunkeMailEnabled parameter in the JournalEnabled parameter. I fixed them both.
Thanks for the feedback.


feat: Module Federation, part 2, ContainerReferencePlugin

Summary

Test Plan

Require Documentation?

[ ] No
[ ] Yes, the corresponding rspack-website PR is __

Current dependencies on/for this PR:

main

PR #4642

PR #4735   👈

This stack of pull requests is managed by Graphite.


CJM program error

When we open CJM program, there is an error in console and some elements are not visible. Elements are shown after scroll, but error remains. Its ok with bb.

aside from the toUpperCase error, the source maps seems broken

Fixed broken sourcemaps. Still someone needs to debug that toUpperCase problem or show it to me how to reproduce.

Thank you, now we can see the problem (still examining the source of it though).

Let me know if you need help

It seems to be about missing translation (the translation file contains only 3 items for this particular string, 4 otherwise)

bb2 returns undefined in this case
bb returns the original english string


API for hic file format

Hi,
do you provide an API or documentation about your hic file format?
Thanks a lot,
Joachim

Yes, there are several places to look. One is here, in the supplementary
materials of our paper:
https://www.cell.com/cms/attachment/2078691992/2071115658/mmc2.xlsx
There is also documentation on the wikis for Juicer and Juicebox for how to
manipulate hic files.
Finally, the “straw” tool provides direct access to matrices.
https://github.com/theaidenlab/straw
On Thu, May 24, 2018 at 9:27 AM Joachim Wolff<EMAIL_ADDRESS>wrote:

Hi,
do you provide an API or documentation about your hic file format?
Thanks a lot,
Joachim
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/theaidenlab/Juicebox/issues/733, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABWiWxW_lrk7i7yj17emejPYvE_-JB1cks5t1rU5gaJpZM4UMPop
.

--
Neva Cherniavsky Durand, Ph.D.
Staff Scientist, Aiden Lab
www.aidenlab.org


realsense-viewer has a problem with pixel formatting

Required Info

Camera Model
{  D435}

Firmware Version
(Open RealSense Viewer --> <IP_ADDRESS>)

Operating System & Version
Linux (Ubuntu 20.04) /

Kernel Version (Linux Only)
(5.8.0-40-generic)

Platform
PC

SDK Version
{ legacy / 2.41.0 }

Language
{C/C#/labview/nodejs/opencv/pcl/python/unity }

Segment
{Robot/ }

Issue Description
I installed realsense viewer as per the tutorial.
(https://github.com/IntelRealSense/librealsense/blob/master/doc/distribution_linux.md#installing-the-packages)
But, I command
realsense-viewer

I got the warning
WARNING [140278774392576] (backend-v4l2.cpp:1357) Pixel format 36315752-1a66-a242-9065-d01814a likely requires patch for fourcc code RW16!

How I can solve this warning?

Hi @takijo0116   I would begin by clarifying that the installation process installs the librealsense SDK software for use with RealSense cameras.  The RealSense Viewer is a program that is part of the librealsense SDK that enables easy use of the camera without requiring any programming knowledge.
The RealSense SDK currently officially supports kernels up to 5.4.  Results from using more recent kernels such as the 5.8 version that you are using cannot be guaranteed.
Also , which type of computer are you installing librealsense on, please (PC, Mac, Raspberry Pi, Nvidia Jetson, etc).  If you are installing on a computer / computing device with an Arm processor such as Pi or Jetson then the dkms package installation method in the link above would be incompatible with such machines, as these packages are designed for computers with x86 / x64 processors.
If you are installing for Ubuntu 20.04 on a PC computer then you can use an installation method called RSUSB backend.  This method requires an internet connection but is not dependent on Linux versions or kernel versions and does not require patching.
https://github.com/IntelRealSense/librealsense/wiki/Release-Notes#release-2400
If you are installing on a Pi or a Jetson then I can direct you to specialist installation instructions for those boards.

Hi @takijo0116   I would begin by clarifying that the installation process installs the librealsense SDK software for use with RealSense cameras.  The RealSense Viewer is a program that is part of the librealsense SDK that enables easy use of the camera without requiring any programming knowledge.
The RealSense SDK currently officially supports kernels up to 5.4.  Results from using more recent kernels such as the 5.8 version that you are using cannot be guaranteed.
Also , which type of computer are you installing librealsense on, please (PC, Mac, Raspberry Pi, Nvidia Jetson, etc).  If you are installing on a computer / computing device with an Arm processor such as Pi or Jetson then the dkms package installation method in the link above would be incompatible with such machines, as these packages are designed for computers with x86 / x64 processors.
If you are installing for Ubuntu 20.04 on a PC computer then you can use an installation method called RSUSB backend.  This method requires an internet connection but is not dependent on Linux versions or kernel versions and does not require patching.
https://github.com/IntelRealSense/librealsense/wiki/Release-Notes#release-2400
If you are installing on a Pi or a Jetson then I can direct you to specialist installation instructions for those boards.

Thank you for your answer.
My computer is laptop.
I will try RSUSB backend method.
Also, Is it possible to  return to v4l2 backend ?

Thank you for your answer.
My computer is laptop.
I will try RSUSB backend method.
Also, Is it possible to  return to v4l2 backend ?

You are not committed to a particular installation method permanently.  I would recommend removing the previous installation before trying a different method, but otherwise it is fine.  For example, removing a package-file installation of librealsense before building it from source code to avoid a 'multiple udev files installed' error.
The link below has guidance for installing with RSUSB using the CMake flag -DFORCE_RSUSB_BACKEND=true
https://github.com/IntelRealSense/librealsense/issues/6368#issuecomment-636316279

You are not committed to a particular installation method permanently.  I would recommend removing the previous installation before trying a different method, but otherwise it is fine.  For example, removing a package-file installation of librealsense before building it from source code to avoid a 'multiple udev files installed' error.
The link below has guidance for installing with RSUSB using the CMake flag -DFORCE_RSUSB_BACKEND=true
https://github.com/IntelRealSense/librealsense/issues/6368#issuecomment-636316279

I cannot find CMakeLists.txt in Librealsense root directory.
Is it need to make the file?

I cannot find CMakeLists.txt in Librealsense root directory.
Is it need to make the file?

Did you download the source code zip-file from the Assets file list of the SDK Releases page and extract the zip-file's contents to obtain the librealsense source-code folder, please?

Typically, the extracted source code folder's structure takes the form of librealsense > librealsense, with the files being in the sub-folder (the real 'parent' folder).  CMakeLists.txt is within this sub-folder.

Did you download the source code zip-file from the Assets file list of the SDK Releases page and extract the zip-file's contents to obtain the librealsense source-code folder, please?

Typically, the extracted source code folder's structure takes the form of librealsense > librealsense, with the files being in the sub-folder (the real 'parent' folder).  CMakeLists.txt is within this sub-folder.

Thank you for your response.
I will try it/

Thank you for your response.
I will try it/

Hi @takijo0116  Do you require further assistance with this case, please?   Thanks!

No.
I solved it.
Thank you for your help.

That's great news @takijo - thanks very much for the update!


feat(headers): add strict-transport-security header

Strict-Transport-Security allows servers to inform user-agents that
they'd like them to always contact the secure host (https) instead of
the insecure one (http).
Closes hyperium/hyper#589

Impressive work! I'll look through this, but seems travis is reporting this doesn't build on stable...

I appreciated the design of the StsParser, it seems well designed to handle many different directives. However, I have 2 concerns.

There's only 2 possible directives that are defined and understood for this header.
Several Strings are allocated through the parsing process, including ones that are discarded immediately, such as from pop_whitespace. Parsing could be done with less allocations, which would make it faster and use less memory.

I'd recommend a parsing strategy that splits on ;, and then again on =. That, along with a trim(), could be compared with max-age and includeSubdomains. An example can be seen in the [Range]https://github.com/hyperium/hyper/blob/master/src/header/common/range.rs#L129) header.

@seanmonstar, I would have preferred a simple split, but the spec allows for quoted strings (which could contain ;" and, in the future, more than just the two directives. Perhaps that's too much YAGNI? To be honest, a split is probably fine for 100% of cases at present. Thoughts?
I'm happy to alter the parsing if that's the concern. My rust is a bit ahem neolithic, so it's probably just my lack of understanding idioms. I'll go through and clean up pointlessly allocated Strings
I used a tuple struct reluctantly, since it seemed to be the way most of the other headers were implemented. I'd prefer a field struct too, so I'll update that as well as the constructors.

The usage of tuple structs is usually for when it's a single value, and so something like ContentLength(100) reads better than ContentLength { value: 100 } (at least, in my opinion).
And, nice catch on it being valid to have foo="bar; baz", which is different from foo=bar; baz. While in the current case, any instance where there is a ; inside a quoted string means it's a value that no directive knows, I'm not against future-proofing. If that check is kept, I'd prefer if the parser could just work on an Iterator<Item=u8>, such as raw.iter(), and then instead of pushing bytes into temporary Strings, the positions could just be recorded instead, since only a &str slice is needed for the matching.

I'm hoping this addresses the performance/allocation concerns. There's now only one allocation per-directive-name -- try as I might to please the borrow-checker gods, I cannot seem to convince that compiler that I'm not really borrowing *self twice.

Thanks @Ryman! Changed so now there's no allocation.
(sidenote: I was confused because the error message was talking about borrowing *self, not the &str...)

I noticed a few other details, which I tried to just fix myself in the parser (duplicate directives should be an error, some unwrap()s I'd rather not have, and bounds checks after already checking self.eof()), and I ended up just rewriting the parsing to use splits as I had mentioned earlier in this thread. Please don't take this the wrong way, I greatly appreciate the work and PR that you sent. I simply felt there were a couple flaws that made me feel I was fighting the parser when I tried to correct them.
I've rebased my fixes onto your commit, and merged manually as https://github.com/hyperium/hyper/commit/7c2e5124e6678a5806f980902031e6f01652d218

@seanmonstar No worries, mate. No offence taken. Like I said before, I didn't think it was necessarily the best code to start with. Glad to have it merged.


Too much dependencies

my app does not use gulp, building semantic require to add much those gulp related packages that makes my app large
when I run npm install in clean directory, it will ask if I need automatic or custom install and I found it annoying

I love what semantic provide but I, at the same time, hate what the workflow that force us to do.
These are just comments. Hope it will be better.

You can always install the semantic to other than your project folder. Configure semantic build folder to project folder.

Please check the contributing guide for the kind of commentary intended for GitHub Issues.


Can configuring VVCs and their BFMs be a procedure call?

When configuring a VVC and BFM with shared__vvc_config there is no check if the VVC actually exists.
E.g. I accidentally called shared_axistream_vvc_config with an index which there was no VVC present, but the number was in the range 0 to C_MAX_VVC_INSTANCE_NUM-1, so nothing happened. This took me some time to find and correct.
Can this be changed, so that it has a built-in mechanism to check whether or not the VVC exists?

Hi,
Yes, but it will require a bit work to implement this feature. We recommend that our users use constants as VVC indexes.
A potential solution would be to add a procedure to each VVC to set the VVC configuration record and check that it exists.
We will consider implementing this in a future release.
Br.
Marius


Parameters not parsed

Rails does not parse the JSON params unless the MIME type is registered.
This should either be documented in the README or automatically register the MIME type
Mime::Type.register 'application/vnd.api+json', :json

This gem's sole purpose is to allow to easily consume JSON:API compliant input in the Rails application. Because of that I think it makes sense to make it register the mime type for the user.
Thank you for this input.

This issue should be resolved now.


Restore the smokey_deploy job in AWS Staging and AWS Production

This job was removed in [1], but the smokey-loop serivce is still
running on the monitoring boxes in both environments.
While there may be some problems with smokey in AWS environments, it's
still useful to be able to run the deploy Jenkins job, so that at
least an up to date version is running.
1: ce9f0051dcfd8f43d6b7324cdd72f0b353ad7d7f

Is this fine with you @fredericfran-gds , @schmie ?

I'm fine with that. May I know what is the smokey-loop service?

Can we find when the fix smokey tests will work for AWS?

I'm fine with that. May I know what is the smokey-loop service?

It's the name of the upstart service that runs the Smokey tests, in a tight loop, on the monitoring machine [1].
1: https://github.com/alphagov/govuk-puppet/blob/master/modules/monitoring/manifests/checks/smokey.pp

Can we find when the fix smokey tests will work for AWS?

I don't know much about Smokey in AWS, but I think the first step forward is to restore the deploy job, and get AWS running the latest version of Smokey.


Multi-task learning pretrained models

Hey,
Thank you for the implementations!
Are there any plans on releasing a pretrained version on the multi-task learning objective (section 5.7 in the paper)?
Thanks,
Eliahu

Sorry, Eliahu. I don't have time to try it for now.

Thanks


Background request with redirect

Alamofire Environment
Alamofire version: 4.7.2
Xcode version: 9.3.1
Swift version: 4.1
Platform(s) running Alamofire: iOS
macOS version running Xcode:
Hi, im trying to do a request with redirect. I need make a download request and the request manager has background mode. I saw that if I do this request with URLSessionConfiguration.default I can make this request but I lost the background mode. How I can a request with background mode if the request takes time to execute, for example for download data?
Thanks for your help!

You can create background sessions by using the URLSessionConfiguration.background(withIdentifier:) API. You can then pass the background session to Alamofire. However, Alamofire doesn't fully support background sessions, including restoring from the background, so if you need true background behavior, I'd suggest implementing it manually, outside of Alamofire. Of course you can still use Alamofire's other tools, like URLRequestConvertible, ParameterEncoding and ResponseSerializer to make handling the requests easier, but true background handling needs to happen outside of Alamofire.
FYI, for background sessions, things like redirects happen without your having to do anything.


Add /-/ready based on mesh status

This is not a final proposal, merely an attempt to get an idea of what should be done.
As an heuristic for mesh readyness, try to see if
the mesh looks stable (the number of peers isn't changing too much).
This implementation always mark the altermanager as ready after a maximum of 60s.
It was briefly discussed in 991, would be affected by #1200.
It's important not to start processing requests ASAP when you have thousands of alerts and silences to gossip and alertmanager instances in other continents.

When sd is properly checking the alertmanager instances and not returning unhealthy instances to prometheus, this seems like a fair start/restart strategy.
There's nothing preventing an alertmanager from restarting and sending alerts based on its on-disk stored state. If we are preventing an alertmanager from receiving any new alerts, maybe we should also gate the sending of alerts with this same variable until the instance is considered "settled"?

When sd is properly checking the alertmanager instances and not returning unhealthy instances to prometheus, this seems like a fair start/restart strategy.

That doesn't sound in line with how the AM is intended to work, it needs to get all alerts - especially if the mesh is unstable.

That doesn't sound in line with how the AM is intended to work, it needs to get all alerts - especially if the mesh is unstable.

This is true. Is a configurable (~60sec) timeout acceptable for a booting alertmanager not sending out any alerts, in the hopes it makes a stable mesh connection? Maybe it makes sense to move this implementation from preventing AM being in sd (and getting all alerts) to waiting initially before sending alerts.
60 seconds probably wouldn't be the end of the world for an initial delay, and the alertmanager would have all alerts and be ready to act on them if it cannot make the mesh connection (this current implementation would potentially have no alertmanagers available via SD if they all were restarted at once).

@stuartnelson3 do you mean delaying most things (not only accepting traffic) until the mesh is considered ready (and maximum after 1 minute or so ?)
I'll update the patch according to your comments during the day.

This is true. Is a configurable (~60sec) timeout acceptable for a booting alertmanager not sending out any alerts, in the hopes it makes a stable mesh connection?

That's not unreasonable, if you've an AM crashlooping that fast you have bigger problems. This might also help a bit with https://github.com/prometheus/prometheus/issues/2585.

Maybe it makes sense to move this implementation from preventing AM being in sd (and getting all alerts)

For frameworks supporting /-/ready it also makes it clear for the administrator that the instance is healthy but not ready. So I think this bit is important.

this current implementation would potentially have no alertmanagers available via SD if they all were restarted at once

To be fair that's already the case during the restart. This is just making the restart a little bit longer.

@iksaif which frameworks are you referencing? In kubernetes, readiness is defined as should or should not receive traffic, but alertmanager should always be receiving incoming prometheus alerts.

@stuartnelson3  do you mean delaying most things (not only accepting traffic) until the  mesh is considered ready (and maximum after 1 minute or so ?)

delaying sending any notifications. AM flushes its state to disk periodically; when an instance starts up and doesn't receive mesh information from a peer it might start sending out duplicate alerts.

@iksaif which frameworks are you referencing? In kubernetes, readiness is defined as should or should not receive traffic, but alertmanager should always be receiving incoming prometheus alerts.

I'm not sure I understand what you think should be done. Do you think we should accept traffic ASAP but delay sending notifications ? That sounds like it would be more complex to implement and to understand for users/operators.
In your opinion what is the value of accepting traffic ASAP ? (If you restart all alertmanager at once, you're going to have downtime anyway since it probably takes more time to start a new container than to wait for the mesh to settle).
In our usecase, we don't use persistent disk, so it's even more likely that the alertmanager will send duplicate notification (or worse, silenced ones). It means that if we delay notification, this could delay alerts that would otherwise have been sent if this instance hadn't registered to SD right away.
(Note: I'm happy to implement any of the two solutions as both would be an improvement)

I'm not sure I understand what you think should be done. Do you think we should accept traffic ASAP but delay sending notifications ? That sounds like it would be more complex to implement and to understand for users/operators.

That was my desire, yes. Why is it more difficult to understand? It should result in all alertmanagers receiving alerts as soon as possible, but delay sending any notifications until the mesh has settled. From a user/operator perspective, an AM instance has an initial delay when it attempts to join the mesh before sending out notifications.

In your opinion what is the value of accepting traffic ASAP ? (If you restart all alertmanager at once, you're going to have downtime anyway since it probably takes more time to start a new container than to wait for the mesh to settle).

Piggy-backing off of @brian-brazil's original comment. The model is for a prometheus server to send alerts to all AM instances, and then for them to coordinate sending notifications. Marking an AM instance as unready so as to avoid receiving alerts breaks that model. What do you see as a benefit in not accepting alerts from prometheus?

In our usecase, we don't use persistent disk, so it's even more likely that the alertmanager will send duplicate notification (or worse, silenced ones). It means that if we delay notification, this could delay alerts that would otherwise have been sent if this instance hadn't registered to SD right away.

Many places still have alertmanager running on baremetal, which will flush state to disk. If an instance is restarted and takes a while to join the mesh, it may send out alerts before receiving confirmation that another instance has already sent the messages. Waiting for the mesh to settle should give a new instance a current view of the world.

The model is for a prometheus server to send alerts to all AM instances, and then for them to coordinate sending notifications.

I did not know that, this makes much more sense. I'll come up with a patch doing this.

New version, the important part isn't done yet, I'm not sure how I'll implement the delay itself. I was thinking about adding another stage, that would probably block on a channel. The channel would replace meshReady. Does that look ok to you ?
Wait for the mesh to settle before sending notifications
See #1209 for details.
As an heuristic for mesh readyness, try to see if
the mesh looks stable (the number of peers isn't changing too much).
This implementation always mark the altermanager as ready after a maximum of 60s.
This adds two new flags to control this behavior:
      --mesh.poll-interval=60s   mesh poll interval during startup.
      --mesh.settle-timeout=10s  mesh settling timeout. Do not wait more than this duration on startup.

It also adds /-/ready which always return 200 (in order to make it clear
that we are ready as soon as we can receive requests).
The mesh status is exposed in /api/v1/status and visible on /#/status.

--mesh.poll-interval=60s   mesh poll interval during startup.
--mesh.settle-timeout=10s  mesh settling timeout. Do not wait more than this duration on startup.

Would poll-interval be something like 5s (check mesh connection count against previous connection count every 5s), and settle-timeout be 60s (continue booting after 60s regardless of changing mesh connection count)? The values seem flipped in your example and I just wanted to be clear I understood.

I like the settle stage, but whether it aborts the pipeline execution or blocks is something I'll think about. I think blocking makes sense so that any pipelines that attempted to execute will as soon as the mesh has settled.

Yes, the example was supposed to be the other way around. 10s is notify.MinTimeout, and I think this kind of makes sense. But I could put 5s instead. I'll try to implement a settling stage to see how it looks.

we can worry about the details on default timings later, no worries

New patch sent with code moved to mesh/mesh.go and a new stage to inhibit alerts.

this highly clashes with changes proposed in #1232 (cc @fabxc )

Is there an estimate on when that will be ready to merge? I think the logic here around settling and having a stage that prevents notifications before being settled will be able to remain mostly unchanged. If the memberlist PR will be ready in a week we could put this on hold until then?

https://github.com/prometheus/alertmanager/pull/1232 has been merged, I'll rebase

Rebased

@simonpasquier  / @stuartnelson3  do you think it looks ok now ? Thanks !

LGTM, just need to rebase on master.

rebased


Sidebar improvements

Add

Connection details (project name etc)
icons for data types as columns?
names of data types?

See snowflake for inspiration

Remove

No need for top level database icon?

This maps to a "project" and only one can be connected to at a time in this implementation

No need for "Tables" and "Views" folders - they can be distinguished by icons

completed in https://github.com/evidence-dev/sqltools-bigquery-driver/pull/16


Evaluate the implementation of a raster handler

Raster import could be implemented in way similar to vectors, using a shared volume from which the raster file could be published.
This approach needs careful analysis of the implications, although I don't see blockers.
Meanwhile the current importer-based flow could be wrapped inside a geonode-importer handler. This way we could get rid of the old implementation, both upload and import.
@etj @mattiagiupponi opinions?

Raster import could be implemented in way similar to vectors, using a shared volume from which the raster file could be published.

The handler now contains all the methods needed to import and publish the resource

Meanwhile the current importer-based flow could be wrapped inside a geonode-importer handler. This way we could get rid of the old implementation, both upload, and import.

Yes, thanks to the creation of the registry, we can set which kind of file the new importer can handle, so once the handler is ready is enough to register the new app here https://github.com/geosolutions-it/geonode-importer/blob/d92d796d485366ae6f693d08e728523ef5e09d4e/importer/handlers/apps.py#L14-L16

This approach needs careful analysis of the implications, although I don't see blockers.

Indeed, the main sensitive point is related to where to store these images. I suggest adding a settings/env_var to configure the path outside the normal upload folder. The storage manager may need an improvement to clone the files into a different directory from the standard one by adding a param here

TODO:

To be decided the usage of rasterio to handle the raster files. Maybe is better to continue with ogr2ogr with its drivers to avoid the usage of too many libraries
Change the storage manager to le the destination folder of the clone being bookable. This is needed for example if we want to store the images in the non-default upload path:
The changes must be done in the storage manager and the data-retriever
To be analyzed if smart_open can save the file in another destination (even in another container if needed)
create a "raster" handler. Probably it will contain less customization than the vector, it will be unique unless validation for each format is required
basic validation is needed
publish the resource in geoserver, probably this method is needed
the creation of the geonode resource and the dynamic model
handle the "copy" of the resource
Test coverage with unittest and end2end testing

Integration:

Test with docker instances and relative volume share (this test may require different changes in the code to let it possible)
Fix project docker-compose to let the volume be visible between the two instances (Geonode/Geoserver) (it may be needed the support of a DevOps)

Estimation without docker: 13 (~ 1 week)
Estimation with docker: 18 (~ 1 and 1/2 week)
@giohappy can I proceed?


Fix getting started guide

Coverage remained the same at 100.0% when pulling b250fa88369d503dad8cb584daca768728dd587e on fix-getting-started-guide into 0abb9ea000e78aad72ffc659bb6d0e95f99aa09e on master.


Tuya lights turn back on even after command to turn off

I have the adaptive lighting working well for various lights such as Wyze, Sengled, and various others. I have one Cree LED in HA that gets turned off with all the others (via a Goodnight automation) but about 10 seconds later it turns right back on. It doesn't behave like this if I disable my one Adaptive Lighting integration. Is it possible that somehow this one is NOT respecting the rules about outside changes?

Possible duplicate of https://github.com/basnijholt/adaptive-lighting/issues/377
In the Adaptive Lighting configuration, try setting interval to smaller value than transition and sleep_transition and restarting Home Assistant.

I have the same with my nanoleafs and a couple of Ikeas.

Possible duplicate of #377
In the Adaptive Lighting configuration, try setting interval to smaller value than transition and sleep_transition and restarting Home Assistant.

I'm using the default integration configuration from github readme. Is such a configuration a faulty one then (as interval is higher than the other two)?

Possible duplicate of #377
In the Adaptive Lighting configuration, try setting interval to smaller value than transition and sleep_transition and restarting Home Assistant.

This seems to work. Thanks!

Unfortunately it’s back to happening as I’ve been fighting it for several nights now. Only solution so far has been to remove that light from the adaptive lighting.

this should be solved in 1.10.1


Dublin Core namespace not available on atom feeds

Dc tags sometimes occurs in atom feeds, dc:date for example inside entries.
Or may be there is some reason why dc should not be available with atom?

Hi @tknjfs,
Since this is an old issue, please reopen if you still wish to have the dublin core namespace on atom feeds. I'll take a look at it.
Thank you


No tags for releases

This makes it very hard to track what is considered aa released version!

each release has a branch named as branch-1.X ..
master branch is latest release

each release has a branch named as branch-1.X ..
master branch is latest release

I'm afraid that that doesn't help me know what the release is exactly. Also only a small number of versions have a branch.
I would suggest a standard software-style release process of bumping the version in the .core file, readme, etc, and then tagging that point with v

I'm afraid that that doesn't help me know what the release is exactly. Also only a small number of versions have a branch.
I would suggest a standard software-style release process of bumping the version in the .core file, readme, etc, and then tagging that point with v

@robtaylor, actually all official releases (1.0 - 1.8) do have a branch. However your point is also valid regarding tag usage. We will  look into this - maybe even consult with a person versed in "software-style" :-)
Thanks for the suggestion.

@robtaylor, actually all official releases (1.0 - 1.8) do have a branch. However your point is also valid regarding tag usage. We will  look into this - maybe even consult with a person versed in "software-style" :-)
Thanks for the suggestion.

Added tags v1.5, v1.6, v1.7, and v1.8

Added tags v1.5, v1.6, v1.7, and v1.8

Amazing! Thank you Ajay and jrahmeh
On Fri, 22 Jan 2021 at 17:50, jrahmeh<EMAIL_ADDRESS>wrote:

Added tags v1.5, v1.6, v1.7, and v1.8
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/chipsalliance/Cores-SweRV/issues/91#issuecomment-765581899,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAB4O4HJIXUYS2CYI3TO4KDS3G3E7ANCNFSM4WNCYAAQ
.

Amazing! Thank you Ajay and jrahmeh
On Fri, 22 Jan 2021 at 17:50, jrahmeh<EMAIL_ADDRESS>wrote:

Added tags v1.5, v1.6, v1.7, and v1.8
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/chipsalliance/Cores-SweRV/issues/91#issuecomment-765581899,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAB4O4HJIXUYS2CYI3TO4KDS3G3E7ANCNFSM4WNCYAAQ
.


MXF identified as MPEG2-PS when using JS/WASM sample

I have an MXF file which is incorrectly being parsed as an MPEG2-PS file (output results attached) when uploading at:
https://mediaarea.net/MediaInfoOnline
The problem file is correctly identified using the MediaInfo CLI. (output results attached)
I have also attached the mediatrace for the working scenario. I cannot get some code to work which uses the buffer method AND also outputs mediatrace. If I could have, I expect that would have been useful.
The sample file is quite large and also confidential, I can provide access to it if you need in a less public message.
What I have worked out is the following:

when opening via the CLI, the MXF file parser is selected based on the ".mxf" extension, and parsing proceeds as expected.
when opening via browser or buffers, the multiple file parsing logic is used to select a parser. The MPEG2-PS parser is tried before the MXF parser. It is accepted for this MXF, but not any others. If I disable the MPEG2-PS parser then the MXF parser is selected and parsing proceeds as normal.

What I haven't been able to identify is where or why in the code base, the MPEG2-PS parser rejects other MXF files, but accepts this one?!
As I said, this is reproducible using the installed CLI and the online service, however I was also using the following hacked example app where I ran the same file through the file based and buffer based interfaces and got the different format identification results:
int main(int argc, char* argv_ansi[])
{
    MediaInfo MI;
    MI.Open(__T("problem1.mxf"));
    STRINGOUT(MI.Get(Stream_General, 0, __T("Format")));

    FILE* F = fopen("problem1.mxf", "rb");

    unsigned char* From_Buffer = new unsigned char[10 * 1024 * 1024];
    size_t From_Buffer_Size;

    fseek(F, 0, SEEK_END);
    long F_Size = ftell(F);
    fseek(F, 0, SEEK_SET);

    MI.Open_Buffer_Init(F_Size, 0);
    do {
        From_Buffer_Size = fread(From_Buffer, 1, 10 * 1024 * 1024, F);
        size_t Status = MI.Open_Buffer_Continue(From_Buffer, From_Buffer_Size);
        if (Status & 0x08) {
            break;
        }
        if (MI.Open_Buffer_Continue_GoTo_Get()!=(MediaInfo_int64u)-1) {
            fseek(F, (long)MI.Open_Buffer_Continue_GoTo_Get(), SEEK_SET);
            MI.Open_Buffer_Init(F_Size, ftell(F));
        }
    }
    while (From_Buffer_Size > 0);
    MI.Open_Buffer_Finalize();
    STRINGOUT(MI.Get(Stream_General, 0, __T("Format")));
}

correct-result.txt
incorrect-result.txt
cli-working-mediatrace.txt

@JeromeMartinez sorry to ping, but wondering if you had a chance to read this issue and if you have any ideas? I am happy to dig further and help with a fix, but I would need a bit of direction in where to look.
Thanks
Nick

Didn't take the time yet to dig in it (I have some stuff to finish for sponsors first) but in my todo-list.


Helm conversion: adapt the helm chart to be adaptable to the metallb-operator deployment

As part of https://github.com/metallb/metallb-operator/pull/232 , we are doing some sed-ing in order to have the deployment aligned to what the operator is currently deploying.
We may want to adapt the charts to be more flexible and offer such deployment settings some parameters, in order to make the transition from one deployment type to the other smoother

closing as completed


[WIP] Test CI stability(1)

focus on addTaskCompletionListener method

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2539/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/carbondata-pr-spark-1.6/430/


Cannot update to newer versions of Xam.Firebase.Messaging

If you are creating an issue for a BUG please fill out this information. If you are asking a question or requesting a feature you can delete the sections below.
Failure to fill out this information will result in this issue being closed. If you post a full stack trace in a bug it will be closed, please post it to http://gist.github.com and then post the link here.
Bug Information
Version Number of Plugin:2.3.0
Device Tested On:Android
Simulator Tested On:
Version of VS: 7.6 (build 711)
Version of Xamarin:<IP_ADDRESS>
Versions of other things you are using:
Steps to reproduce the Behavior
Install the plugin
Update Xam.Firebase.Messaging to 60
Expected Behavior
Updates
Actual Behavior
Doesn't update (incompatible)

Hi
Which firebase messaging nuget are you updating to?

Hi,
I'm currently facing this issue too with 2.3.0. My google play services libraries version are 60.1142.1, but the nuget dependency want Xamarin.Firebase.Messaging v60.1142.0, which is not compatible with v60.1142.1

Just released this beta with support for newer version of fcm nuget package:
https://www.nuget.org/packages/Plugin.FirebasePushNotification/2.3.5-beta


tasks: doi registration in datacite

Requires https://github.com/inveniosoftware/invenio-rdm-records/pull/583, note that some code refactor needs to be added after the rebase (error logging related)
closes #584
Wondering about tests... I could add them, but then we are mocking the DataCite client... I am not sure of how useful would it be?
We could set test credentials in GH, but it might lead to non-locally reproducible errors.

closed in favour of https://github.com/inveniosoftware/invenio-rdm-records/pull/814


Moving emails to trash won't work when the account language is different that english

Try switching your account to polish and try to move stuff (delete!) to trash. Won't work. Instead of hardcoding it (message.rb - line 77-78):
trash = @gmail.labels.exist?('[Gmail]/Bin') ? '[Gmail]/Bin' : '[Gmail]/Trash'
move_to(trash) unless %w[[Gmail]/Spam [Gmail]/Bin<EMAIL_ADDRESS>
would be nice if you could add a method to manually set trash name (and set Bin/Trash by default).
The work around is quite simple:
mail.delete!
mail.move_to(TRASH_NAME)

Where TRASH_NAME is the localized trash name (for polish it is '[Gmail]/Kosz')

#83 is now merged hence closing.

This issue was moved to gmailgem/gmail#58


breakdown account service

Split account service into a user account and a DDA - Demand Debit Account Service. The user account is responsible for the user information (id, name, address, password, etc). The DDA is responsible for keeping track of the transactions on the account (i.e. debits and credits) and overall balance.
Also, the password should be split out from the "account" object and stored safely, i.e. a salted.

look into SSO tile for PCF for user management. What does it provide?


Don't use IDs as part of log message Keys (#1971)

Downgrade to log.Debug and remove the wiCount map from the
message fields.
Fixes #1971
Signed-off-by: Xavier Coulon<EMAIL_ADDRESS>

Ike Plugins (test-keeper)
Thank you @xcoulon for this contribution!

It appears that no tests have been added or updated in this PR.
Automated tests give us confidence in shipping reliable software. Please add some as part of this change.
If you are an admin or the reviewer of this PR and you are sure that no test is needed then you can use the command /ok-without-tests as a comment to make the status green.
Your plugin configuration is stored in the file.

/ok-without-tests

@xcoulon snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-2031-1

Codecov Report

Merging #2031 into master will decrease coverage by 0.06%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2031      +/-   ##
==========================================
- Coverage   66.37%   66.31%   -0.07%
==========================================
  Files         151      151
  Lines       13734    13733       -1
==========================================
- Hits         9116     9107       -9
- Misses       3790     3798       +8
  Partials      828      828

Impacted Files
Coverage Δ

controller/space_iterations.go
82.02% <100%> (-0.2%)
:arrow_down:

remoteworkitem/jira.go
75% <0%> (-25%)
:arrow_down:

remoteworkitem/scheduler.go
53.65% <0%> (-7.32%)
:arrow_down:

Continue to review full report at Codecov.

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


Unicode (UTF-8) CPP files are detected as binaries in pull reqest diff view

Our project contains UTF-16 cpp files (because of unicode literals inside). Github shows them as binary. I tried to convert them to UTF-8 and committing changes, but existing pull request still shows them as binary. I also tried to set diif attribute for *.cpp files - didn't help. I though that github caches some data during pull request creation, So i just tried to use "compare" buttin to compare my branch with dev to check the issue separatelly - no results, files were still displayed as binary... Is this your old issue with handling of unicode files or after converting to UTF-8 it had to work and my issue relates to some diff results caching?
BTW, when i set "*cpp diff" attribute GitHub desktop Win client (<IP_ADDRESS>) crashes when i click i the UTF-8 file to view the diff.

I checked my UTF-8 files, they don't have 0x00 byte anywhere in the body

Do you have an example of file detected as binary?

Do you have an example of file detected as binary?

test_generic_flow.zip
Sure, i attached zipped cpp file. it is UTF-8 encoded.

Linguist does not seem to be the culprit here:
linguist test_generic_flow.cpp
test_generic_flow.cpp: 1775 lines (1452 sloc)
  type:      Text
  mime type: text/plain
  language:  C++

(This would mention binary if Linguist detected it as binary.)
You will probably have to report it to<EMAIL_ADDRESS>Do you have a link to the pull request diff view?

Flagging as stale :flags: