Unable to select end date when using date range in a specific case

I am using start date and end date selection range with following condition:

end date cannot be less than start date

If the current system time is in AM, say 13/05/2018, 09:00 AM and i want to select date range as 12/05/2018-10:00PM to 12/05/2018-11:00PM.
After Selecting start date-time as 12/05/2018-10:00PM, i am not able to select end date-time as 12/05/2018-11:00PM because when I open the end date-time picker, it shown todays date, ie 13th (and time as 9:00 AM). and if I try to select 12th, it cannot select as 12/5/18, 9:00 AM is lesser than start date already selected.
I would like to know if there is a way to work around this particular isssue
Thanks

Can you paste some template code and why the end date-time is set to today?

this is how the code is handled in html:

And have the following code in javascript (using angular framework):
$scope.setMaxStartDate = function () {
$scope.closeAlert();
if($scope.fromDate == null)
$scope.maxStartDate = $scope.toDate;
$scope.checkStartEndDate();
}
$scope.checkStartEndDate = function () {
$scope.closeAlert();
if($scope.fromDate > $scope.toDate)
$scope.toDate = null;
//if($scope.toDate==null && current system time = AM &&
$scope.fromDate = yesterday PM) then set $scope.toDate as
$scope.fromDate
}
im using this code in an app. Now if current system time is say 17/5/18 -
9:00 AM.
I need to set the start and end date as follows:
start: 16/5/18, 10:00 PM
end: 16/5/18, 11:00 PM
I select the start date and enter as required.
Then I select the end date. currently it shows 17/5/18. If i select
17/5/18, i get the time auto set at 9:00AM, i.e. the current time.
This is the expected behaviour.
However, when i click the end date and select 16/5/18. I guesss, the
time still refers to 9:00 AM so, effectively the ref is to
16/5/18-9:00AM
Now as i have set that the end date has to be greater than start date,
i am not able to select anything as 16/5/18-9:00AM is lesser than the
already selected start date.
If I try to select PM, as the hour reading refers to 9, it will point
to 9:00PM which is still smaller than 10:00PM selected in the start
date.
So it does not allow me to select PM. I am completely stuck.
I hope i have been able to clear my question
Thanks for your time
Regards
Rahul
On Wed, May 16, 2018 at 5:56 AM, Michel Couillard<EMAIL_ADDRESS>wrote:

Can you paste some template code and why the end date-time is set to today?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/logbon72/angular-material-datetimepicker/issues/130#issuecomment-389356324,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ac1kGswAbDZ0FjJMRLfwhCbU4nnRzeLeks5ty3IwgaJpZM4T8t3q
.

What version are you using? v1.15.1 ?
I tried to reproduce it with you code, but it's working as I think it should.

I set manually my system time to 17/5/18 - 9:00 AM
start: 16/5/18, 10:00 PM
end: 16/5/18, 11:00 PM
go to change end again, but I clicked "today"
Then change date to 16/5/18 and the time stay at 9:00 AM
Cannot change time, but I can click on PM circle
Then I can only select 10 PM or 11PM in hours. Max 11:59PM

Please see my video of this:
https://drive.google.com/file/d/1M-y5GL_SpNVzTdoaNmm_xuOiA866cMbh/view?usp=sharing

@rahulgadhyan have you found something?

Hi Michel,
I was busy with some other portion of our code. I shall try to work as
directed this week. If the issue persists, I shall record the video and
share it with you
Thanks a lot for your time and effort
Regards
Rahul
On Thu, May 31, 2018 at 1:48 AM, Michel Couillard<EMAIL_ADDRESS>wrote:

@rahulgadhyan https://github.com/rahulgadhyan have you found something?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/logbon72/angular-material-datetimepicker/issues/130#issuecomment-393304016,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ac1kGqpQInEmreSUsUJBl5LNUjhnFKK8ks5t3v6GgaJpZM4T8t3q
.

Yes you can record a video with something like Screencastify.

I fixed this in https://github.com/beenote/angular-material-datetimepicker/issues/54.


ios: add support for toggling trust chain verification

Description: Adds feature parity to the Android/JVM engine builder, and allows TLS trust chain verification to be bypassed.
Risk Level: Low
Testing: Unit & CI
Signed-off-by: Mike Schore<EMAIL_ADDRESS>

Note this currently differs slightly from the Android/Java API, which exposes a binary enumeration to represent trust verification status (which matches Envoy internal configuration). I think this public API is simpler, and if folks agree, propose updating the Java side to this model as well.

I think this public API is simpler, and if folks agree, propose updating the Java side to this model as well.

I agree, unless there's any possibility of adding a 3rd option in the future, at which point an enum could be both more descriptive and more extensible.

This looks mostly good to me, but I wonder if we should have any guardrails to prevent our users from accidentally turning this on?
It defaults to verified+enforced, which I think should be safe enough right now. I've considered bucketing some of these features under an "Advanced/Experimental" mechanism previously, and if we make that distinction, then this could go there.

I agree, unless there's any possibility of adding a 3rd option in the future, at which point an enum could be both more descriptive and more extensible.
My intuition is it's unlikely we'll expose a third option here even if one is added internally (some configuration is advanced enough that it probably warrants manual configuration).

Thanks Mike!
FYI: For Java, I picked an Enum for readability purposes, even if I don't foresee that there would be more values.


Fixed Tapas ripper

Category
This change is exactly one of the following (please change [ ] to [x]) to indicate which:

[X] a bug fix (Fix #261)
[ ] a new Ripper
[ ] a refactoring
[ ] a style change/fix

Description
I changed the domain to tapas.io
Testing
Required verification:

[X] I've verified that there are no regressions in mvn test (there are no new failures or errors).
[X] I've verified that this change works as intended.

[X] Downloads all relevant content.
[X] Downloads content from multiple pages (as necessary or appropriate).
[X] Saves content at reasonable file names (e.g. page titles or content IDs) to help easily browse downloaded content.

[X] I've verified that this change did not break existing functionality (especially in the Ripper I modified).

Optional but recommended:

[X] I've added a unit test to cover my change.

Coverage decreased (-0.04%) to 30.206% when pulling<PHONE_NUMBER>457e4e42ce1930b588e5b6371f5bb3 on cyian-1756:tapas into f6d58ee7482a980c8ed583e2019136771cebdac6 on RipMeApp:master.


Dynamic Input System

Enhance the input system to support fully re-mappable key assignment etc.
Add an 'input settings' ImGui menu to provide a GUI layer over this.
Key codes and Input Actions have been defined in input_types.h.
Basic input events have been defined in engine_events.h. A dedicated 'input.h' header within 'include/ecs/events/' may be defined contain a more extensive list of input event types and parameter types.
The input manager within input_manager.h and input_manager.cpp already contains a potential starting point for remapping functionality via its use of a {KeyInput, Event} map and the void BindKeyInputEvent(key, action, event) registration method.
The current GUI implementation allows for definition of new ImGUI menu's via inheritance from the base class sge::gui::ImGuiWindow (see imgui_window.h and imgui_window.cpp).
See existing examples such as ImGuiECSWindow (imgui_ecs_window.h, imgui_ecs_window.cpp).
The ImGui Interactive Manual is an excellent resource.

I'll start looking into and working on this issue starting on 4/2 or 4/3


Simplify FileArrayDAODecorator

I did this while trying to fix a bug but this file didn't end being the cause of the bug.
Just thought I'd open a PR for the refactor in case anyone thought this version was more readable. If not then I'll just close this PR.

I like it, thanks for the cleanup!


⚠ Bofrost.fr has degraded performance

In f006120, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 947 ms

Resolved: Bofrost.fr performance has improved in fcfe740 after 6 minutes.


ltcd: rpctest to work in conjunction with btcd rpctest

rpctest to target ltcd build instead of btcd build.
rpctest to use different port sequence then what's used in btcd's rpctest. This is necessary for rpctest of ltcd & btcd to work in conjunction.

@losh11 @thrasher- Thanks. Can this be merged?

Sorry about the late reply, but finally done!


Feature/dictionary generator

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+26.1%) to 60.175%

Totals

Change from base Build<PHONE_NUMBER>:
26.1%

Covered Lines:
589

Relevant Lines:
966

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+26.1%) to 60.175%

Totals

Change from base Build<PHONE_NUMBER>:
26.1%

Covered Lines:
589

Relevant Lines:
966

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+26.1%) to 60.175%

Totals

Change from base Build<PHONE_NUMBER>:
26.1%

Covered Lines:
589

Relevant Lines:
966

💛  - Coveralls


Alive test: enabling spectrometer functionality freezes the board

This is likely an issue with available memory, etc. since this used to work in the past.
Anze should go and fix it.

Fixed in the latest coreloop.


tarsnapaccount.cpp: include QHeaderView for Qt 5.11.0 compatibility

Fixes https://github.com/Tarsnap/tarsnap-gui/issues/179

Thanks, @apjanke!

Excellent. You're welcome.
What's your release policy? Any chance of a 1.0.1 release to pick up this and any other recent fixes? Or do we need to wait for the next regular minor release?

I was hoping to get some more automated tests in place before looking at making a release, but I agree that it would be good to get these build fixes out sooner rather than later.  I'll aim to have a release candidate in a few days.

Sweet. :+1:

What is the status of https://github.com/Tarsnap/tarsnap-gui/releases/tag/v1.0.1 ? It doesn't seem to be designated as an actual release: https://github.com/Tarsnap/tarsnap-gui/releases/latest

Hi @ilovezfs.
The release is almost ready, but I forgot some stuff:
https://github.com/Tarsnap/tarsnap-gui/pull/182
I didn't realize that pushing a tag called v1.0.1 would make github automatically add it to the release list.  :(

Hi @ilovezfs,
I've now made 1.0.1 official.  Please note that the tarball has changed; the .tar.gz sha256 is now 502e53a4eacb2795bfbe62b9e6ef236cce6fdb43cb15153c0fc4ad61c161eb97.  This value has been updated in util/tarsnap-gui.rb in git master.
Release email:
http://mail.tarsnap.com/tarsnap-users/msg01456.html
Release on github:
https://github.com/Tarsnap/tarsnap-gui/releases/tag/v1.0.1
Sorry for the confusion over this release; it was a bit of a learning process.  :)


select kubeflow pods by node selectors

Bug Description
I would like to make sure my charmed kubeflow pods only land on certain nodes (selected by some label on the k8s nodes).  How can I achieve this given that the charms can re-render the pod manifests on a variety of hooks?
To Reproduce
N/A
Environment
N/A
Relevant Log Output
N/A

Additional Context
N/A

btw @ca-scribner pointed me to https://github.com/canonical/namespace-node-affinity-operator

Closing since namespace-node-affinity charm is responsible for this functionality. In the future, this should move to juju as mentioned in https://github.com/canonical/namespace-node-affinity-operator/issues/31.


Xapian Not found

When asking a question please also include where you looked for an answer (so we can update the documentation if needed).
I want to test some C++ search engine support with Xapian.[https://github.com/xapian/xapian]
but cannot search the lib with vcpkg search xapian.

Hi @hudengjunai
Thanks for posting this issue.
Of course, xapian is not in vcpkg now. You can open a new issue or comment here #8946 if you wish to add xapian
in vcpkg.
Thanks.

Closing this issue for now, please open a new issue if you still have the request for xapian.

https://github.com/microsoft/vcpkg/issues/8946

https://github.com/microsoft/vcpkg/pull/27038


Ending in the middle of downloading

Prerequisites

[ ] Did you read FAQ section in readme.md?
[ ] Did you test with the latest releases or commit ?
[ ] Did you search for existing issues in Issues?

Description
[Description of the bug or feature]
Steps to Reproduce

[First Step]
[Second Step]
[and so on...]

Expected behavior: [What you expected to happen]
Actual behavior: [What actually happened]
Log file: [Attach the pixivutil.log file in the application folder, recommended to delete the old file, reproduce the issue, and upload the newly generated file here]
Versions
You can get this information from executing PixivUtil2.py --help.
Latest version available in https://github.com/Nandaka/PixivUtil2/releases
====================================================
While downloading by tag, I set the download to page 450, but the download stops at page 2.
The following settings are set, and related photos and log files are attached.

pixivutil.log

Exact same problem on the latest commit. Doesn't seem to happen when downloading by member.


Slider in Draggable.feedback does not work as expected and throws an error LeaderLayer anchor must come before FollowerLayer in paint order, but the reverse was true.

Steps to Reproduce

Execute flutter run on the code sample
Drag container around.
This works as expected (Feedback is shown and dragging works).
Change state of slider by moving thumb.
Drag container around.

Expected results: The container remains draggable and feedback is properly shown and no error occurs.
Actual results: The feedback is not displayed any more. The child jumps to the target position. The following error is thrown:

[+13303 ms] ══╡ EXCEPTION CAUGHT BY SCHEDULER LIBRARY ╞═════════════════════════════════════════════════════════
[   +3 ms] The following assertion was thrown during a scheduler callback:
[   +1 ms] Assertion failed:
[        ] file:///C:/Users/***/tools/flutter/packages/flutter/lib/src/rendering/layer.dart:2498:7
[        ] leader._lastOffset != null
[        ] "LeaderLayer anchor must come before FollowerLayer in paint order, but the reverse was true."
[        ] When the exception was thrown, this was the stack:
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 251:49  throw_
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 29:3    assertFailed
[        ] packages/flutter/src/rendering/layer.dart 2498:13                                                                          [_establishTransform]
[        ] packages/flutter/src/rendering/layer.dart 2557:5                                                                           addToScene
[        ] packages/flutter/src/rendering/layer.dart 546:5                                                                            [_addToSceneWithRetainedRendering]
[        ] packages/flutter/src/rendering/layer.dart 1106:12                                                                          addChildrenToScene
[        ] packages/flutter/src/rendering/layer.dart 1681:5                                                                           addToScene
[        ] packages/flutter/src/rendering/layer.dart 938:5                                                                            buildScene
[        ] packages/flutter/src/rendering/view.dart 226:30                                                                            compositeFrame
[        ] packages/flutter/src/rendering/binding.dart 501:18                                                                         drawFrame
[   +1 ms] packages/flutter/src/widgets/binding.dart 883:13                                                                           drawFrame
[        ] packages/flutter/src/rendering/binding.dart 363:5                                                                          [_handlePersistentFrameCallback]
[        ] packages/flutter/src/scheduler/binding.dart 1145:15                                                                        [_invokeFrameCallback]
[        ] packages/flutter/src/scheduler/binding.dart 1082:9                                                                         handleDrawFrame
[        ] packages/flutter/src/scheduler/binding.dart 996:5                                                                          [_handleDrawFrame]
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/platform_dispatcher.dart 1005:13           invoke
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine/platform_dispatcher.dart 159:5             invokeOnDrawFrame
[        ] C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/_engine/engine.dart 455:45                                <fn>
[        ] ════════════════════════════════════════════════════════════════════════════════════════════════════

Code Sample

import 'package:flutter/material.dart';

void main() => runApp(const SampleApp());

final GlobalKey myKey = GlobalKey();

class SampleApp extends StatefulWidget {
  const SampleApp({Key? key}) : super(key: key);

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

class _SampleAppState extends State<SampleApp> {
  Offset position = Offset.zero;

  @override
  Widget build(BuildContext context) {
    final floatingPanel = Container(
      key: myKey,
      padding: const EdgeInsets.all(20),
      color: Colors.teal,
      child: const ContentWidget(),
    );
    return MaterialApp(
      title: 'Sample',
      home: Scaffold(
          body: Stack(
        children: [
          Positioned(
            left: position.dx,
            top: position.dy,
            child: Draggable<int>(
              data: 1,
              onDragEnd: (DraggableDetails details) {
                setState(() {
                  position = details.offset;
                });
              },
              feedback: floatingPanel,
              childWhenDragging: const SizedBox.shrink(),
              child: floatingPanel,
            ),
          )
        ],
      )),
    );
  }
}

class ContentWidget extends StatefulWidget {
  const ContentWidget({Key? key}) : super(key: key);

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

class _ContentWidgetState extends State<ContentWidget> {
  double sliderValue = 0;
  @override
  Widget build(BuildContext context) => Material(
        child: Slider(
            value: sliderValue,
            onChanged: (v) {
              setState(() {
                sliderValue = v;
              });
            }),
      );
}

Logs

Analyzing sample_apps...
No issues found! (ran in 7.5s)

[√] Flutter (Channel stable, 2.8.1, on Microsoft Windows [Version 10.0.19042.867], locale de-DE)
    • Flutter version 2.8.1 at C:\Users\jonscn\tools\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 77d935af4d (6 weeks ago), 2021-12-16 08:37:33 -0800
    • Engine revision 890a5fca2e
    • Dart version 2.15.1

[√] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at C:\Users\jonscn\AppData\Local\Android\sdk
    • Platform android-30, build-tools 30.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

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

[√] Visual Studio - develop for Windows (Visual Studio Professional 2019 16.7.2)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional
    • Visual Studio Professional 2019 version 16.7.30413.136
    • Windows 10 SDK version 10.0.17763.0

[√] Android Studio (version 4.1)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] VS Code (version 1.63.2)
    • VS Code at C:\Users\jonscn\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.32.0

[√] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.19042.867]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 97.0.4692.71
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 97.0.1072.62

• No issues found!

This doesn't seem to be specific to web, as running the code on mobile (ios in my case), results in same error as below:

 console error log

======== Exception caught by scheduler library =====================================================
The following assertion was thrown during a scheduler callback:
LeaderLayer anchor must come before FollowerLayer in paint order, but the reverse was true.
'package:flutter/src/rendering/layer.dart':
Failed assertion: line 2507 pos 7: '_debugCheckLeaderBeforeFollower(forwardLayers, inverseLayers)'

Either the assertion indicates an error in the framework itself, or we should provide substantially more information in this error message to help you determine and fix the underlying cause.
In either case, please report this assertion by filing a bug on GitHub:
  https://github.com/flutter/flutter/issues/new?template=2_bug.md

When the exception was thrown, this was the stack:
#2      FollowerLayer._establishTransform (package:flutter/src/rendering/layer.dart:2507:7)
#3      FollowerLayer.addToScene (package:flutter/src/rendering/layer.dart:2554:5)
#4      Layer._addToSceneWithRetainedRendering (package:flutter/src/rendering/layer.dart:546:5)
#5      ContainerLayer.addChildrenToScene (package:flutter/src/rendering/layer.dart:1106:13)
#6      TransformLayer.addToScene (package:flutter/src/rendering/layer.dart:1681:5)
#7      ContainerLayer.buildScene (package:flutter/src/rendering/layer.dart:938:5)
#8      RenderView.compositeFrame (package:flutter/src/rendering/view.dart:228:37)
#9      RendererBinding.drawFrame (package:flutter/src/rendering/binding.dart:501:18)
#10     WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:883:13)
#11     RendererBinding._handlePersistentFrameCallback (package:flutter/src/rendering/binding.dart:363:5)
#12     SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1144:15)
#13     SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1081:9)
#14     SchedulerBinding._handleDrawFrame (package:flutter/src/scheduler/binding.dart:995:5)
#18     _invoke (dart:ui/hooks.dart:151:10)
#19     PlatformDispatcher._drawFrame (dart:ui/platform_dispatcher.dart:308:5)
#20     _drawFrame (dart:ui/hooks.dart:115:31)
(elided 5 frames from class _AssertionError and dart:async)
====================================================================================================

======== Exception caught by scheduler library =====================================================
The following assertion was thrown during a scheduler callback:
LeaderLayer anchor must come before FollowerLayer in paint order, but the reverse was true.
'package:flutter/src/rendering/layer.dart':
Failed assertion: line 2507 pos 7: '_debugCheckLeaderBeforeFollower(forwardLayers, inverseLayers)'

Either the assertion indicates an error in the framework itself, or we should provide substantially more information in this error message to help you determine and fix the underlying cause.
In either case, please report this assertion by filing a bug on GitHub:
  https://github.com/flutter/flutter/issues/new?template=2_bug.md

When the exception was thrown, this was the stack:
#2      FollowerLayer._establishTransform (package:flutter/src/rendering/layer.dart:2507:7)
#3      FollowerLayer.addToScene (package:flutter/src/rendering/layer.dart:2554:5)
#4      Layer._addToSceneWithRetainedRendering (package:flutter/src/rendering/layer.dart:546:5)
#5      ContainerLayer.addChildrenToScene (package:flutter/src/rendering/layer.dart:1106:13)
#6      TransformLayer.addToScene (package:flutter/src/rendering/layer.dart:1681:5)
#7      ContainerLayer.buildScene (package:flutter/src/rendering/layer.dart:938:5)
#8      RenderView.compositeFrame (package:flutter/src/rendering/view.dart:228:37)
#9      RendererBinding.drawFrame (package:flutter/src/rendering/binding.dart:501:18)
#10     WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:883:13)
#11     RendererBinding._handlePersistentFrameCallback (package:flutter/src/rendering/binding.dart:363:5)
#12     SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1144:15)
#13     SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1081:9)
#14     SchedulerBinding._handleDrawFrame (package:flutter/src/scheduler/binding.dart:995:5)
#18     _invoke (dart:ui/hooks.dart:151:10)
#19     PlatformDispatcher._drawFrame (dart:ui/platform_dispatcher.dart:308:5)
#20     _drawFrame (dart:ui/hooks.dart:115:31)
(elided 5 frames from class _AssertionError and dart:async)
====================================================================================================

======== Exception caught by scheduler library =====================================================
The following assertion was thrown during a scheduler callback:
LeaderLayer anchor must come before FollowerLayer in paint order, but the reverse was true.
'package:flutter/src/rendering/layer.dart':
Failed assertion: line 2507 pos 7: '_debugCheckLeaderBeforeFollower(forwardLayers, inverseLayers)'

Either the assertion indicates an error in the framework itself, or we should provide substantially more information in this error message to help you determine and fix the underlying cause.
In either case, please report this assertion by filing a bug on GitHub:
  https://github.com/flutter/flutter/issues/new?template=2_bug.md

When the exception was thrown, this was the stack:
#2      FollowerLayer._establishTransform (package:flutter/src/rendering/layer.dart:2507:7)
#3      FollowerLayer.addToScene (package:flutter/src/rendering/layer.dart:2554:5)
#4      Layer._addToSceneWithRetainedRendering (package:flutter/src/rendering/layer.dart:546:5)
#5      ContainerLayer.addChildrenToScene (package:flutter/src/rendering/layer.dart:1106:13)
#6      TransformLayer.addToScene (package:flutter/src/rendering/layer.dart:1681:5)
#7      ContainerLayer.buildScene (package:flutter/src/rendering/layer.dart:938:5)
#8      RenderView.compositeFrame (package:flutter/src/rendering/view.dart:228:37)
#9      RendererBinding.drawFrame (package:flutter/src/rendering/binding.dart:501:18)
#10     WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:883:13)
#11     RendererBinding._handlePersistentFrameCallback (package:flutter/src/rendering/binding.dart:363:5)
#12     SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1144:15)
#13     SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1081:9)
#14     SchedulerBinding._handleDrawFrame (package:flutter/src/scheduler/binding.dart:995:5)
#18     _invoke (dart:ui/hooks.dart:151:10)
#19     PlatformDispatcher._drawFrame (dart:ui/platform_dispatcher.dart:308:5)
#20     _drawFrame (dart:ui/hooks.dart:115:31)
(elided 5 frames from class _AssertionError and dart:async)
====================================================================================================

May be related to : https://github.com/flutter/flutter/pull/92598 / https://github.com/flutter/flutter/pull/96144

 master, stable flutter doctor -v
[✓] Flutter (Channel master, 2.10.0-1.0.pre.307, on Mac OS X 10.15.4 19E2269
    darwin-x64, locale en-GB)
    • Flutter version 2.10.0-1.0.pre.307 at
      /Users/dhs/documents/fluttersdk/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision b7424c619c (3 hours ago), 2022-01-26 17:25:45 -0800
    • Engine revision c248c6e38e
    • Dart version 2.17.0 (build 2.17.0-63.0.dev)
    • DevTools version 2.10.0-dev.1

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • Mac OS X 10.15.4 19E2269
      darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 97.0.4692.99

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

[✓] Flutter (Channel stable, 2.8.1, on Mac OS X 10.15.4 19E2269 darwin-x64,
    locale en-GB)
    • Flutter version 2.8.1 at /Users/dhs/documents/fluttersdk/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 77d935af4d (13 hours ago), 2021-12-16 08:37:33 -0800
    • Engine revision 890a5fca2e
    • Dart version 2.15.1

[✓] Android toolchain - develop for Android devices (Android SDK version 30)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Users/dhs/Library/Android/sdk
    • Java binary at: /Users/dhs/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/202.7486908/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Users/dhs/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/202.7486908/Android
      Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.57.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (4 available)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 93.0.4577.82

• No issues found!

/cc @goderbauer

Hi @darshankawar,
true. I only tested it with web, but it seems to be an issue on other platforms as well.
I tested the same behavior with multiple other widgets but it seems to be slider specific (at least I did not experience this with another widget so far). I have no workaround for the issue and would like to avoid building a custom slider widget just because of this.

I have run into the same problem.
Any news here?

Same problem here intermittently.

@josne Is one of those other cases related to TextFields?
I'm trying to create dragable TextFormFields using ReorderableListView.builder(), and everything works fine until android's cursor-handle shows up. Then smooth dragging goes out the window.

/cc @HansMuller @goderbauer .
There was a similar issue reported : https://github.com/flutter/flutter/issues/102902

@josne Is one of those other cases related to TextFields? I'm trying to create dragable TextFormFields using ReorderableListView.builder(), and everything works fine until android's cursor-handle shows up. Then smooth dragging goes out the window.

I get a similar error when I have a TextField inside a ReorderableListView. In my Listview row, I have an icon and a textfield. It works fine as long as I don't focus the textfield and just reorder by clicking the icon. Once the textfield is focused, dragging doesn't work and keeps crashing with "LeaderLayer anchor...." error.

@josne Is one of those other cases related to TextFields? I'm trying to create dragable TextFormFields using ReorderableListView.builder(), and everything works fine until android's cursor-handle shows up. Then smooth dragging goes out the window.

So far I have resolved by removing the focus when the drag gesture starts:
ReorderableListView.builder(
  onReorderStart: (_) {
    FocusScope.of(context).unfocus();
  },
  //...
);

btw,
this exception "LeaderLayer anchor must come before FollowerLayer in paint order, but the reverse was true" with Slider looks like caused by its label rendering.
So that, wrapping Slider with SliderTheme.of(context).copyWith(showValueIndicator: ShowValueIndicator.never), child: Slider(..., and fixing forgotten 'if' in
https://github.com/flutter/flutter/blob/df602da850247ffb410a7807e39b93be39cceb1c/packages/flutter/lib/src/material/slider.dart#L1490
with
-    _state.showValueIndicator();
+    if (showValueIndicator) _state.showValueIndicator();

made it possible to get rid of this annoying exception with ReorderableListView use

It seems that this issue has resurfaced. Unfortunately, @gianmarcocalbi  's workaround seems to be not working in the latest version. Any updates or alternative solutions would be appreciated!


Remove dependency on imagemagick

You don't even need to save the new png. You create a component snapshot, load the comparison PNG into a different juce::Image, and then do the subtraction.
This would completely eliminate the dependency on imagemagick and make this tool completely stand-alone.
If you need help with that function let me know.

One could even save the new snapshot and even save the differences as a separate image. Optionally one could increase the contrast for the difference image, so it's easier to see the visual changes (fringes, wrong alpha values, etc.)

Thanks! I'd certainly appreciate help.
I wonder how much it's worth to implement that functionality to get rid of the dependency though; as it stands it'd be quite easy to change the diffing algorithm or parameters, since it's just calling into imagemagick.
I understand how distribution gets harder though.

It's around 10-15 lines of code, so IMO totally worth it. It also removes a barrier for newcomers. I find the installation of ImageMagick confusing. There are multiple different versions (I've counted 27 different ones for Windows alone), people have to make sure it's in their PATH, etc.
Plus, adding a comparison function allows other creative outputs, like a "heatmap" where identical pixels are dark-purple, and the bigger the difference, the more the colors shift into red/yellow, up to white.

I've implemented the comparison using JUCE facilities. So this project no longer requires image-magick.


Implement alignment for map_overelap

ref #525
sits on #700 and #699

Will review once #699 is in. :)

Rebased after the merge, so this should be ready to review as well


New travis script failing due to missing secret file

The following error is being reported by the Travis script:
  File "manage.py", line 22, in <module>
    execute_from_command_line(sys.argv)
  File "/home/travis/virtualenv/python2.7.14/lib/python2.7/site-packages/django/core/management/__init__.py", line 364, in execute_from_command_line
    utility.execute()
  File "/home/travis/virtualenv/python2.7.14/lib/python2.7/site-packages/django/core/management/__init__.py", line 308, in execute
    settings.INSTALLED_APPS
  File "/home/travis/virtualenv/python2.7.14/lib/python2.7/site-packages/django/conf/__init__.py", line 56, in __getattr__
    self._setup(name)
  File "/home/travis/virtualenv/python2.7.14/lib/python2.7/site-packages/django/conf/__init__.py", line 41, in _setup
    self._wrapped = Settings(settings_module)
  File "/home/travis/virtualenv/python2.7.14/lib/python2.7/site-packages/django/conf/__init__.py", line 110, in __init__
    mod = importlib.import_module(self.SETTINGS_MODULE)
  File "/opt/python/2.7.14/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "/home/travis/build/spdx/spdx-online-tools/src/src/settings.py", line 14, in <module>
    from secret import getGithubKey, getGithubSecret, getSecretKey
ImportError: No module named secret

This is due to the file containing the github secret info being missing.  I don't believe the current unit tests use the secrets, so may be able to get away with creating a set of fake credentials in a src/src/secret.py file to get around this issue.  Another approach would be to use encrypted environment variables to store the credentials in travis then create the secret.py file as part of the travis script.

IMHO making a fake credentials file would be a better approach so if anyone tries to run the project he should not have to create the file, he can just replace the values.


Additional Arguments: Configure permanent settings

Hello,
I have read the documentation and have been unable to find a feature that allows permanent configuration for additional arguments. I have resorted to running the EF Migrations via CLI for now. Does this plugin support permanent additional arguments for the EF migrations? If not, is this something that would be supported in the future?
Thank you!

Hi @GrapeJuice787, thanks for the request. Do you mean parameters that will be saved across dialogs? If so, you need to check the "Autofill additional options" checkbox. After the next command execution through the UI, additional parameters will be available on further dialog usages.
In Rider 2023.2 version of the plugin this settings entry is called "Store sensitive data in a secure store"

Just tried again, I am running on Mac, and the Additional arguments: block does not retain prior used values. Upgraded Rider to version 2023.2.3

Could you check this behavior in 2023.3 EAP?

2023.3 Does not appear to exist. When checking for updates on 2023.2.3 I receive the dialog which states, "You already have the latest version of JetBrains Rider and plugins installed."

https://www.jetbrains.com/rider/nextversion/

We have Early Access Preview (EAP) versions with cutting-edge features. The plugin will be bundled into rider starting with 2023.3, so new features and fixes are available there.


'latest' version doesn't work

What happened?
As per description:

node_exporter_version : Node exporter package version. Also accepts latest as parameter.

It fails upon trying to get a checksum
Did you expect to see some different?
Role run successfully
How to reproduce it (as minimally and precisely as possible):
    - name: run Prometheus 'node_exporter' role
      include_role:
        name: cloudalchemy.node_exporter
      vars:
        node_exporter_version: "latest"

Environment
$ lsb_release -d
Description:	Debian GNU/Linux 10 (buster)

Role version:

/etc/ansible/roles/cloudalchemy.node_exporter/meta/.galaxy_install_info:
{install_date: 'Thu Aug 26 19:30:37 2021', version: 2.0.0}

Ansible version information:
ansible --version

$ ansible --version
ansible [core 2.11.4]
  config file = /etc/ansible/ansible.cfg
  ansible python module location = /usr/local/lib/python3.7/dist-packages/ansible
  executable location = /usr/local/bin/ansible
  python version = 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0]
  jinja version = 2.10
  libyaml = True

Variables:

see above

Ansible playbook execution Logs:

TASK [cloudalchemy.node_exporter : Get latest release] *************************
task path: /etc/ansible/roles/cloudalchemy.node_exporter/tasks/preflight.yml:75
Thursday 26 August 2021  20:38:47 +0000 (0:00:00.034)       0:05:32.931 *******
ok: [/tmp/build/project/mnt -> localhost] => {
    "attempts": 1,
    "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
    "changed": false
}

TASK [cloudalchemy.node_exporter : Set node_exporter version to 1.2.2] *********
task path: /etc/ansible/roles/cloudalchemy.node_exporter/tasks/preflight.yml:89
Thursday 26 August 2021  20:38:48 +0000 (0:00:00.771)       0:05:33.702 *******
ok: [/tmp/build/project/mnt -> localhost] => {
    "ansible_facts": {
        "node_exporter_version": "1.2.2"
    },
    "changed": false
}

TASK [cloudalchemy.node_exporter : Get checksum list from github] **************
task path: /etc/ansible/roles/cloudalchemy.node_exporter/tasks/preflight.yml:99
Thursday 26 August 2021  20:38:48 +0000 (0:00:00.057)       0:05:33.759 *******
fatal: [/tmp/build/project/mnt -> localhost]: FAILED! => {}

MSG:

An unhandled exception occurred while running the lookup plugin 'url'. Error was a <class 'ansible.errors.AnsibleError'>, original message: Received HTTP error for https://github.com/prometheus/node_exporter/releases/download/vlatest/sha256sums.txt : HTTP Error 404: Not Found

NO MORE HOSTS LEFT *************************************************************

Anything else we need to know?:
overriding a variable via set_fact won't work the way it's done in https://github.com/cloudalchemy/ansible-node-exporter/blob/master/tasks/preflight.yml#L90
See more in this discussion - https://stackoverflow.com/questions/27038553/ansible-set-fact-doesnt-change-the-variable-value

any updates on this?

I'm still getting this error when node_exporter_version: "latest" on debian 11

it crashes the whole python process for me on my mac. Passing -K does not fix it.

To @sixtus:
If it crashes during multithreading tasks on your mac then it doesn't related to this problem and you have to add this line "export OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES" to your .zshrc/.bashrc

@wowpetr thanks, that fixed the crash, however I need to pass a version, "Get latest release" fails with FAILED! => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result"}

@sixtus with -K flag and local sudo password provided?

Running into this issue as well:
node_exporter_version = latest
TASK [cloudalchemy.node_exporter : Get checksum list from github] **********************************************************************************************************************************************************************************
task path: /usr/share/ansible/roles/cloudalchemy.node_exporter/tasks/preflight.yml:99
fatal: [<REDACTED> -> localhost]: FAILED! =>
  msg: 'An unhandled exception occurred while running the lookup plugin ''url''. Error was a <class ''ansible.errors.AnsibleError''>, original message: Received HTTP error for https://github.com/prometheus/node_exporter/releases/download/vlatest/sha256sums.txt : HTTP Error 404: Not Found'

I've faced with same issue.
As I understand, in string https://github.com/cloudalchemy/ansible-node-exporter/blob/master/tasks/preflight.yml#L91), we're trying to override node_exporter_version variable by using set_fact.
- name: "Set node_exporter version to {{ _latest_release.json.tag_name[1:] }}"
      set_fact:
        node_exporter_version: "{{ _latest_release.json.tag_name[1:] }}"

However, set_fact have low precedence and precedence is more important than the order in which the value is assigned.
For more info please see -> https://stackoverflow.com/questions/27038553/ansible-set-fact-doesnt-change-the-variable-value
Workaround is to create additional variable (i.e. internal variable _node_exporter_version) which will be used instead of variable node_exporter_version in steps after "Set node_exporter version to" and add additional step to define this variable for node exporter with already defined version.
Example:
- block:
    - name: Get latest release
      uri:
        url: "https://api.github.com/repos/prometheus/node_exporter/releases/latest"
        method: GET
        return_content: true
        status_code: 200
        body_format: json
        user: "{{ lookup('env', 'GH_USER') | default(omit) }}"
        password: "{{ lookup('env', 'GH_TOKEN') | default(omit) }}"
      no_log: "{{ not lookup('env', 'MOLECULE_DEBUG') | bool }}"
      register: _latest_release
      until: _latest_release.status == 200
      retries: 5

    - name: "Set internal variable for node_exporter version to {{ _latest_release.json.tag_name[1:] }}"
      set_fact:
        _node_exporter_version: "{{ _latest_release.json.tag_name[1:] }}"
  when:
    - node_exporter_version == "latest"
    - node_exporter_binary_local_dir | length == 0
  delegate_to: localhost
  run_once: true

- name: "Set internal variable for node_exporter version to {{ node_exporter_version }}"
    set_fact:
      _node_exporter_version: "{{ node_exporter_version }}"
  when:
    - node_exporter_version != "latest"

it crashes the whole python process for me on my mac. Passing -K does not fix it.

Try the fix from here, it worked on my M1. https://github.com/ansible/ansible/issues/76631

This role has been deprecated in favor of a the prometheus-community/ansible collection.


Fast abstract JSON size

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Diversity and representation

While the conversation here is really energetic and inspiring, I have the feeling that we might be missing the point of view of under-represented groups. Particularly as we dive into potentially dangerous territory, like the review process (#4), in which some groups are at high risk of harassment and implicit biases.
Before we get too far along, it would be great to increase the diversity of people actively involved and commenting in these threads.
Please spread the word to people you think might be interested and encourage them to comment here and elsewhere in the repo.

While Slack activity initially has been really viral, and lots signed up to the channel, it sort of dried out pretty quickly I have the impression. Here on GitHub it is mainly you (@leouieda), @filippo82, and @JesperDramsch active. I assume many are sort of interested, but also aware that it will be a lot of work (time). If the project should move forward I assume one would have to gather a core team that is willing to push thing, e.g. draft out some ideas, do some brainstorming, gather information, and come up with questionnaires and similar to make people participate in the shape-process. Just an idea.

That's a very good point @prisae. I noticed the same but it was expected. It's tough to commit to these things and it's ok for people to phase in and out as life gets busy.
We should keep on the discussion and hope that some more people will get involved as we move forward with this. It might be easier once we actually have something going.


Update document  in React app

This issue covers updating the document head, including meta tags, links and title in the React app to match the attributes of the main dev-jot app as seen here: https://github.com/jrobind/dev-jot/blob/master/app-main/public/index.html
[Happy to take this on to get the ball rolling but for future issues I'll give space to someone else 😉 ]

Thanks for raising the issue. It's all yours!
Open and work on as many issue as you want to – the React side of the app needs lots of work 😄

Okay, thanks 😄


Proposed change to CONTRIBUTING.md: Two-person review

Let's do more two-person review - and say so in the CONTRIBUTING.md file.
Signed-off-by: David A. Wheeler<EMAIL_ADDRESS>

+1 (just to be self-referential).


some picture not ready to download

some picture not ready
Loading image 'chancetstorms.bmp'
Loading image '/mini/chancetstorms.bmp'

Have you any solution?

No, the file should exists unless it was never downloaded

If yiu test the links in the first post, they are not present

thank you

The file name is correct 'chance of thunder storms' so the t should be there. Weather underground do not use BMP formatted files so at some point they have all been converted and are downloaded from Daniels server to the ESP spiffs storage, he must have missed that file out which is why it's not found.


Fix grammer of markdown in swarm-mode.md

Proposed changes
Fix (maybe) wrong markdown syntax in swarm-mode guide. The sentences are not any header contents. See also commonmark spec https://spec.commonmark.org/0.28/#setext-heading
https://docs.docker.com/engine/swarm/swarm-mode/

before
after

I don't remove ==== because of the reason of introduced that is unclear in commit 8f465b4a012d. But I think that it is good to remove ====.

Deploy preview for docsdocker ready!
Built with commit 1bf949bf9089eff72b55a78d96e140538a1ea345
https://deploy-preview-7662--docsdocker.netlify.com

Resolved at #7776 . Thanks. :blush:


Folder unfolds can't see the inside of the content

VSCode Version:
OS Version:

Steps to Reproduce:

2.Folder unfolds can't see the inside of the content

@wangying31 do you have settings to exclude files (files.exclude)?


Created subsections in "Platforms"

Locize: replaced commercial tagline with an actual description
Platforms: created subsections by theme as the list is getting longer.

If that sounds good, I'd like to also do it for the other sections - just tell me if it's ok! :)

Hi @alexture Awesome!! 🎉 for me looks great, really 🚀 Thank you so much for your effort and contribution here, as well as thank you for vigilance and good idea. Will be merged very soon, have a great day and thanks again ✨
Best wishes,


Add "direct" dependency identification to usage report

The usage report should identify packages that are directly included by a repo as opposed to packages that are included via transitive dependencies.

Closing: this was done in https://github.com/dotnet/source-build/pull/871 and is in all branches now.


Folding fix

-Fix folding to include the final layer (needed for https://github.com/soniajoseph/ViT-Prisma/issues/72).
-Also fixed import errors from renaming
Aside: "head" is a confusing name for the final layer since it conflicts with the attention heads. We should probably rename it.

Great catch, thank you.


State is set incorrectly in Redux

This is a bug, I think no explanation is needed, just take a look at the screenshot and how is state.tracker.projects is set in console and in redux devtools: http://prntscr.com/bqc1yi
Reducer code:
export default function tracker(state = initialState, action) {
  switch (action.type) {
    case SET_PROJECTS:
      return Object.assign({}, state, { projects: action.projects });
    default:
      return state;
  }
}

I am using "redux": "^3.5.2" inside electron-react-boilerplate (https://github.com/chentsulin/electron-react-boilerplate)

I don't think this is a bug in Redux, if anything it seems like the log monitor is not correctly reporting the state. If you call store.getState() does it have the correct state?

no, it has same values as in redux dev tools

I'm really not clear on what the actual issue is here.  This certainly doesn't look like a problem with Redux itself, and I'm not seeing anything actionable.  Whatever's going on is likely due to your reducer logic and your middleware configuration.  I'm going to go ahead and close this.  If you come up with information that shows this is an actual bug with Redux, I'll reopen it.

I already added the reducer, the redux setup code (with middlewares):
import { createStore, applyMiddleware, compose } from 'redux';
import thunk from 'redux-thunk';
import createLogger from 'redux-logger';
import { hashHistory } from 'react-router';
import { routerMiddleware, push } from 'react-router-redux';
import rootReducer from '../reducers';
import { SET_LOCATION } from '../actions/app';

const logger = createLogger({
  level: 'info',
  collapsed: true,
});

var setLocationMiddleware = store => next => action => {
  if (action.type !== SET_LOCATION) {
    return next(action);
  }

  store.dispatch(push(action.location));
}

const router = routerMiddleware(hashHistory);

const enhancer = compose(
  applyMiddleware(thunk, router, logger, setLocationMiddleware),
  window.devToolsExtension ? window.devToolsExtension() : noop => noop
);

export default function configureStore(initialState) {
  const store = createStore(rootReducer, initialState, enhancer);

  if (module.hot) {
    module.hot.accept('../reducers', () =>
      store.replaceReducer(require('../reducers')) // eslint-disable-line global-require
    );
  }

  return store;
}

the actual bug in redux: in console and debugger state.tracker.projects is array but in redux devtools it is null

the actual bug in redux: in console and debugger state.tracker.projects is array but in redux devtools it is null

Right, that doesn't sound like a bug in Redux.  Redux devtools is a separate project. If store.getState() is returning the correct value then it is not a bug in Redux core.

please read carefully: http://prntscr.com/bqeuly

It would help if you could provide a sample project demonstrating this issue.

@cutbko Your first screenshot --> http://prntscr.com/bqc1yi , clearly shows that redux-logger is outputting the state i.e state.tracker.projects = [array] correctly, which mimics what store.getState() would return. Are you sure store.getState() is returning state.tracker.projects = null?


Allow creation of new Helm Charts and Kustomizations from the UI

Similar to how we have the NewResourceWizard, we want to create 2 new forms for creating basing helm charts or kustomizations.
We should only require the user to input the mandatory fields and then generate either a Chart.yaml file in a folder, or a kustomization.yaml file in a folder.
I'm guessing we'll always have to create a new folder for these.

Optionally, for the helm chart form, we could have it as a two-step form, where in the second step you defined the initial values file with some default values. Basically you have a form where you can create new fields where you set the name of the field and then a value.

@devcatalin already has a prototype


fix: set web dialog for login behavior

Fix this issue : https://github.com/capacitor-community/facebook-login/issues/83
(Login error when Facebook application installed on device)

I need this to be merged...

I think we should first import LoginBehavior first then we can use it. So in the top of the file, add import com.facebook.login.LoginBehavior;
Also I need this to be merged as well! And I don't know why it wasn't implemented in the first place.


Map Polyline on Road

I have added a polyline between two points by using addpolyline() method pollyline was added but show a straight line from one point to other i want to map that polyline on road

Use google snap to roads api

thanks


Mention terminfo update is required when changing tabspaces

Changing tabspaces from the default (8) requires a corresponding
update to the it item in the terminfo entry used.
Some applications, like Emacs, rely on knowing the width of a tab, and
will experience unexpected behavior if the terminfo data does not
match the actual width used.
Closes #1482.

@chrisduerr


cannot install custom version of existing lib anymore

Describe the bug
I didn't test it on every lib but it's an issue for sepal_ui. I wanted to work with a custom installation and I get the following error:
PermissionError: [Errno 13] Permission denied: '/usr/local/bin/activate_venv'

I checked the permission and as expected owner has everythong and group and other only read and execute:
$ ls -l /usr/local/bin/activate_venv
-rwxr-xr-x 1 root root 225 Oct 21 09:59 /usr/local/bin/activate_venv

To Reproduce
git clone git@github.com:12rambau/sepal_ui.git
pip install -e sepal_ui/

Expected behavior
It should replace the default one. As a workaround I'll be using a venv but that is way to complicated for normal users.

I thought it was only related to my sepal env but apparently, not... This happens because when you install sepal_ui  locally, it first uninstalls the previous version, this will try to remove bin scripts, but I think that in someway it cannot find the local bin scripts, and then it tries to uninstall /user/local/bin scripts which of course is not possible, throwing PermissionError.
In short, I could solve the issue by removing my .local folder and installing sepal_ui again, not the best way to solve but I couldn't do anything different from my side.
I think the cause of the problem is that we are adding sepal_ui bin path in manually, but this is no longer required since sepal_ui will install the scripts as entry points.

You don't have permission to change the system libraries. You should install it as a user library instead, with the --user flag:
pip install -e sepal_ui/ --user

You're absolutely right, pip is clever enough. That means that I get the same behavior without the --user flag, and am unable to replicate the problem. Installation adds binaries under ~/.local/bin and even if I remove that directory before uninstalling and/or reinstalling, it works properly. No attempt to write in /usr/local/bin/ is made.

You're absolutely right, pip is clever enough. That means that I get the same behavior without the --user flag, and am unable to replicate the problem. Installation adds binaries under ~/.local/bin and even if I remove that directory before uninstalling and/or reinstalling, it works properly. No attempt to write in /usr/local/bin/ is made.
Perhaps you have an old version of the library in .local, one that tries to delete files under  /usr/local/bin/ when uninstalling?

the solution proposed by @dfguerrerom worked for me. I'm trying to update sepal_ui and I tried with numpy which worked as expected.
I'll close this when sepal_ui become a better neighbours (WIP)


You were added to awesome-humane-tech

This is just a FYI issue to notify that you were added to the curated awesome-humane-tech in the 'Analytics' category, and - if you like that - are now entitled to wear our badge:

By adding this to the README:
[![Awesome Humane Tech](https://raw.githubusercontent.com/humanetech-community/awesome-humane-tech/main/humane-tech-badge.svg?sanitize=true)](https://github.com/humanetech-community/awesome-humane-tech)

https://github.com/humanetech-community/awesome-humane-tech

Thanks a lot for adding Ackee! Re-styling the README is on my todo list and I will consider adding some new badges to it.


[Feature Req] Concave polygon support

Would be nice to have concave polygon support for user defined shapes.

Hi @ahomphophone, thanks for the feature request. I added a story to our backlog including a reference to the slack video and convo for additional context. Will update this issue when we have more info.

This feature has been added to the latest release, ViroCore 1.9


[Impeller] Large scale transforms prevent glyph atlas population.

Steps to reproduce
Run the following on macOS with --enable-impeller:
import 'package:flutter/rendering.dart';
import 'package:flutter/widgets.dart';

void main() {
  runApp(
    const Directionality(
      textDirection: TextDirection.ltr,
      child: _BugReport(
        child: Text('foo', style: TextStyle(fontSize: 300)),
      ),
    ),
  );
}

class _BugReport extends SingleChildRenderObjectWidget {
  const _BugReport({required super.child});

  @override
  _RenderBugReport createRenderObject(BuildContext context) => _RenderBugReport();
}

class _RenderBugReport extends RenderBox with RenderObjectWithChildMixin<RenderBox> {
  @override
  void performLayout() {
    size = constraints.biggest;
    child!.layout(constraints);
  }

  @override
  void paint(PaintingContext context, Offset offset) {
    // Modified from `makePerspectiveMatrix(0.001, 1.0, 1.0, 10.0)..translate(0.0, 0.0, -7000.0)`
    Matrix4 transform = Matrix4(
      2000,  0,       0,      0,
      0,     2000,    0,      0,
      0,        0,   -1,   9000,
      0,        0,   -1,   7000,
    );
    context.pushTransform(false, offset, transform, paintChild);
  }

  void paintChild(PaintingContext context, Offset offset) {
    context.paintChild(child!, offset);
  }
}

Expected results
You expect to see the "foo" text on a black screen.  This is what you see when you run using Skia.
Actual results
Nothing is rendered, and the following error shows up in the console:
[ERROR:flutter/impeller/base/validation.cc(49)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(49)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(49)] Break on 'ImpellerValidationBreak' to inspect point of failure: Failed to render entity.
[ERROR:flutter/shell/platform/embedder/embedder_external_view_embedder.cc(198)] Could not render into the embedder supplied render target.

Flutter version
[✓] Flutter (Channel main, 3.16.0-6.0.pre.29, on macOS 13.6 22G120 darwin-arm64, locale en)
    • Flutter version 3.16.0-6.0.pre.29 on channel main at /Users/tvolkert/project/flutter/flutter
    • Upstream repository git@github.com:flutter/flutter.git
    • Framework revision 5207a309e8 (8 minutes ago), 2023-10-07 02:51:32 -0400
    • Engine revision 8711c1fd21
    • Dart version 3.3.0 (build 3.3.0-0.0.dev)
    • DevTools version 2.28.1

Impeller and Skia both do at scale rendering of glyphs into an atlas. At bigger sizes, Skia will decay to SDF or paths, while impeller will not. It's likely that this glyph is exceeding the size that can be placed into an atlas and needs to decay to path rendering.

In case it's useful for reference, here's what it looks like when run using Skia:

This particular example is creating glyphs of size (637500, 712500) with Impeller. 🤔

glyph size: (159.375, 178.125) with scale 4000

The reason the scale is so big is that we only take the max basis length into account:
Scalar Entity::DeriveTextScale() const {
  return GetTransformation().GetMaxBasisLengthXY();
}

We could either limit that somehow or take the full transform into account.

One problem with the current design is that we don't know the text scale until after we've populate all of our entities, which is a bit too late to fall back to path rendering. We'd need to detect that a glyph's scale is such that it would never fit in an atlas and fallback to path rendering.
alternatively, the text scale computation needs to be smarter.
FYI @dnfield.

Talked a bit with @dnfield offline. Instead of taking max basis, we should compute the bounding box of a unit rectangle transformed by the matrix. This is blocked by fixing https://github.com/flutter/flutter/issues/131445
For actually large paths, we do need to add a fallback to path rendering.

Got the exact same issue, I have an animation that scales text from huge to normal to obtain a nice effect.
Unfortunately since impeller is the default backed, the animation is laggy:
https://github.com/user-attachments/assets/0804e87a-8c3c-410d-bec7-8ef38ef63b0f
Output is this:
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Failed to render entity.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Failed to render entity.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Failed to render entity.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Failed to render entity.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Failed to render entity.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Failed to render entity.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Failed to render entity.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Failed to render entity.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Failed to render entity.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Failed to render entity.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Failed to render entity.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Failed to render entity.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Failed to render entity.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Failed to render entity.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Failed to render entity.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Failed to render entity.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Failed to render entity.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Failed to render entity.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Failed to render entity.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Failed to render entity.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create valid atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Cannot render glyphs without prepared atlas.
[ERROR:flutter/impeller/base/validation.cc(59)] Break on 'ImpellerValidationBreak' to inspect point of failure: Failed to render entity.


Directory collection view margins are wrong

Possible things to try:
section.contentInsetsReference = .safeArea

section.contentInsetsReference = .layoutMargins

collectionView.preservesSuperviewLayoutMargins = true

It may also be good to revisit the cell layout here. Things to bear in mind:
Using safeAreaLayoutGuide.leadingAnchor, etc, will give the platform standard margins (16), and it's possible to set a maximum text size if you wish to be more explicit about larger text size behaviour.

Done.


chore: use @rjsf/validator-ajv6

Types

[x] 🧹 Chores

Background or solution
ref: #2803.

🤖 Generated by Copilot at 4e53c9b

Downgrade @rjsf/validator-ajv8 to @rjsf/validator-ajv6 in debug package to fix JSON schema validation issue (link)
Add support for custom components and container IDs in PanelView component in main-layout package to enable debug console and breakpoints view integration (link)
Use AccordionContainer component for non-custom panel views in PanelView component in main-layout package to allow collapsibility and resizability (link)
Remove unused variable and rename another variable in PanelView component in main-layout package for clarity (link)

Changelog

🤖 Generated by Copilot at 4e53c9b
This pull request adds custom components and accordion containers to the main layout and fixes a JSON schema validation issue in the debug package. It modifies packages/main-layout/src/browser/tabbar/panel.view.tsx and packages/debug/package.json files.

/next


fix!: pss target length verification

Closes #380
Most of the validation was already in place from my earlier validation work, I was just asserting wrong values 😅
Breaking changes

bee.pssSend() now throws error if the specified target exceeds maximal value. Use Utils.makeMaxTarget() that will give you the max target that Bee accepts.

The only downside about this fix is that it is breaking 😒 But honestly the other work (directory streaming and fetch refactor) are also breaking so I guess we should just go with 2.0 release.

You are right, but that is not the scope of this PR. I was only reproducing the current state which was passing the whole address which then got truncated with the original slice().
I have created an issue about this improvement and I will work on it in the future.

You are right, but that is not the scope of this PR. I was only reproducing the current state which was passing the whole address which then got truncated with the original slice().

Okay, I see.

I have created an issue about this improvement and I will work on it in the future.

I also opened one long time ago, you may want to close either as duplicate.

Thanks for the info!

@nugaon Bee API also has the same restrictions. It will return Bad Request for target exceeding the limit. See https://github.com/ethersphere/bee/blob/master/pkg/api/pss.go#L29 (btw. there the limit is 3 bytes = 6 hex chars, but this was bumped only after Bee 1.1.0 release, so it is not propagated to Bee-js for now and I will change it once release cycle will begin).


a problem in utils/util.py

I have a little confuse about line 302 in util.py
lr_blured = torch.clamp(lr_blured.round(), 0, 255)
is that right for a (0,1) tensor? when we use degrade for training, dose tensor value between (0,255)?
maybe the following code is more suitable？
lr_blured = torch.clamp(lr_blured, 0, 1)

Hi @zhangjinyangnwpu, input LR images with ranges [0, 1] and [0, 255] are both okay for SR networks. In this work, we follow EDSR and RCAN to use images with range [0, 255] as the input of our network.


miner: pick activeset deterministically from the first block

related: https://github.com/spacemeshos/go-spacemesh/issues/5282
in the latest epoch there are many different activesets that causes unnecessary state growth and noticeable increases
load on the network. the root cause of that is suboptimal propagation of atxs.
in order to mitigate this problem all ballots after first epoch will select activeset deterministically using first applied block.
this is the same method that we are using to select hare active set.

bors try

actually it doesn't help as they will compute it in the first layer


App Logo do not change

After changing the Assets Images and build the apk
I install the apk to my mobile
but the app icon is not change to the new one.
It stay with the SWV logo

its in the path app\src\main\res\raw
replace image from there

in android studio Select the folder APP, then go in the menu to File -> New -> image asset, and there you have to change your logo, or other way is overwrite the images in the folder assets, res>mimap, in all the folders with the diferentes sizes.


Add swagger documentation for all methods.

There are some DAV methods whose Swagger Docs are missing.

Added : https://github.com/noveens/js-owncloud-client/commit/314f5861b84ce15c287ca8f4a502fa26e828a715


WSEGAN weights

Hi!
I would be very interested in using a pre-trained of WSEGAN. However, from what I can see you have not released the pre-trained weights for this version of your model, only for SEGAN. Do you plan to release these at any point?
Thanks a lot.

Did you obtain them @miraodasilva ??

No, unfortunately not.


[Docs] Add documentation for LayoutAnimation

Current docs are a bit sparse, would be nice to have a description and example in there.

breadcrumb https://github.com/facebook/react-native/issues/456 nom nom

Closing this because I think Animations guide covers this well enough for now


type wrongful character in the selection box

Describe the bug
While dropdown is closed, it opens after entering a key like (down arrow) but it prints "arrow Down" on the combo box. We should stop writing values that are more than one character on the select boxes or combo boxes.
To Reproduce
Steps to reproduce the behavior:

Go to Choicejs
Click on 'Right-to-left'
Select 'Choice1'
enter Arrow Down
It will type it into the select box.

Expected behavior
We expect not to type anything in the select box.
Screenshots

Desktop (please complete the following information):
-OS: Windows 10
-Browser: Chrome
-Version: Latest

Fixed as part of #1116

It's possible to backport this fix to the 10.x branch?
Some projects, including Laravel Filament 3.x depend on this branch and due to breaking changes in 11.x branch will not update the dependency.

There has been significant code churn in the v11.0.0+ update, and the fix ended up being significantly more complicated than the linked PR