Would be nice if it could keep the tree selection UI open when on tree mode

Right now every time we activate it takes away the tree selection UI.
So if I'm doing lots of line tree placements, every time I want to change the tree I need to hit the tree button to open the UI, the mod UI goes away, then select a new tree, then hit CTRL+L.
The fact that we can't customize the shortcut  also doesn't help, as CTRL + L isn't one we can hit with left-hand easily
Great work btw!

Thanks!
Yes, you've just hit on the two biggest pain points that I'm addressing after the addition of tooltips and localization in 1.2 (just uploaded).
Development is now focusing on integrating the tool with the default object tool (as with the CS1 version) so you'll be able to change prefabs while still using the tool (and switch to/from the tool without a hotkey - just like you can change modes in the network tool).
I'm also working on customizable input bindings integrating with the game's inbuilt input system - that's actually been a very complex piece of work (I estimate I've spent at least 20 hours on that alone so far).  I'm very near to a releasable version, but still have two hurdles left (one of which is quite significant).

Thanks!
Yes, you've just hit on the two biggest pain points that I'm addressing after the addition of tooltips and localization in 1.2 (just uploaded).
Development is now focusing on integrating the tool with the default object tool (as with the CS1 version) so you'll be able to change prefabs while still using the tool (and switch to/from the tool without a hotkey - just like you can change modes in the network tool).
I'm also working on customizable input bindings integrating with the game's inbuilt input system - that's actually been a very complex piece of work (I estimate I've spent at least 20 hours on that alone so far). I'm very near to a releasable version, but still have two hurdles left (one of which is quite significant).

That is really nice, and big kudos.
I can image that modding at this stage before the official mod support is launched is being a pain.
Regarding the in-game input system, I have seen other mods that uses it to setup bindings, not sure if would help you tell you which one (I don't remember by head but could check)
Thanks for replying and keep up the great work!

If you do know of someone who's already figured out the game's input system bindings then I'm definitely interested in taking a look, thanks!  I'd rather not have to resort to menu selections instead of using dynamic key bindings and conflict detection.

If you do know of someone who's already figured out the game's input system bindings then I'm definitely interested in taking a look, thanks! I'd rather not have to resort to menu selections instead of using dynamic key bindings and conflict detection.

Hey man, I took a look and I got it wrong, the mods are not using the game Input, they just using the game Options screen to create their own options here, not sure if it helps in any way (529 Tiles and Tree Controller are the mods)
Sorry!

No worries!  And yeah, I know those two mods - I wrote one and helped a bit with the other :)
I'm making very good progress and have just cracked the most significant outstanding problem, so I'm not going to resort to setting file editing just yet....

I think both issues have been addressed with the new 1.3 update (tree selection panel remains open, and the hotkey has been removed entirely as the mod is now activated via the UI).
Feel free to reopen this if you disagree.

The new version looks / works awesome man, great work <3


Cannot add mods in latest version.

Used pax to create a simple test modpack a few days ago, have since updated the version of pax (from version 1.2.1 to 1.4.0 or 1.3.0) and I can no longer add mods to any modpack.
Tried redownloading the latest versions, and making new modpacks to no avail (forge, fabric, 1.16.5, 1.17...)
This is the response I get when trying to add a mod with the new versions:
$ ./pax add lithium
[:] Loading data from manifest..
[:] Searching for mod..
httpclient.nim(1080)     responseContentIter
asyncfutures.nim(390)    read
asyncfutures.nim(390)    read
asyncfutures.nim(390)    read
asyncfutures.nim(390)    read
Error: unhandled exception: 400 Bad Request [HttpRequestError]
When I roll back to the 1.2.1 release the command works as expected.

Ok, got the error.

In the old versions, I was retrieving 50 mods at once from the Forge API.
In the new version, I'm retrieving 100 mods at once from the Forge API,

Apparently this used to work a few days ago when testing but doesn't work anymore? Somehow?

Doesn't matter, I can just reset it to 50 again and it should work. Bugfix coming in a few minutes.

Fixed in latest release.


Fix floating point precision in resize

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 93.61%. Comparing base (369943b) to head (d9cac20).

Additional details and impacted files
@@           Coverage Diff           @@
##           master      #79   +/-   ##
=======================================
  Coverage   93.61%   93.61%
=======================================
  Files          22       22
  Lines        1816     1818    +2
=======================================
+ Hits         1700     1702    +2
  Misses        116      116

Flag
Coverage Δ

93.61% <100.00%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Wrong signature for snake_case methods of DirectGui objects

Hi! I've been using this project for a few months now, and it has been very helpfull. Thank you!
There seems to be an issue when calling some snake_case aliasses of DirectGui objects. Specifically when the gui-object is passed to a function. It seems to choose the wrong signature of the function. I am using version 0.3.3 of types-panda3d and Pycharm as IDE. I hope the example below illustrates the issue.
class GuiTest(ShowBase):
    def __init__(self):
        super().__init__()
        button = DirectGui.DirectButton(
            text="test"
        )

        # works as it should
        button.set_pos(0.1, 0.1, 0.1)
        button.reparent_to(base.render)

        self.button_test(button)

    def button_test(self, button: DirectGui.DirectButton):
        # complains about the arguments

        button.set_pos(0.1, 0.1, 0.1)
        # expects:
        # def set_pos(self,
        #             const_NodePath_self: Any,
        #             const_LVecBase3f_pos: Any) -> None
        # instead of def set_pos(self, pos: Vec3Like) -> None:

        button.reparent_to(base.render)
        # expects:
        # def reparent_to(self,
        #                 const_NodePath_self: Any,
        #                 const_NodePath_other: Any,
        #                 int_sort: Any,
        #                 Thread_current_thread: Any) -> None

        # works as it should
        button.setPos(0.1, 0.1, 0.1)
        button.reparentTo(base.aspect2dp)

Alright, thank you for the help!

Bizarrely, this appears to be resolved if DirectButton is imported from direct.gui.DirectButton instead.

That is rather strange. It would also be a reasonable workaround if the issue can not be resolved.


Livesync crash with UIKitCore error when running iOS emulator

@NickIliev commented on Mon Apr 01 2019
@isawk commented on Mon Apr 01 2019
Environment
Provide version numbers for the following components (information can be retrieved by running tns info in your project folder or by inspecting the package.json of the project):

CLI: 5.3.0

Cross-platform modules: 5.3.1

Android Runtime:5.3.0

iOS Runtime:5.3.0

Plugin(s):
"nativescript-3dtouch": "^1.2.2",
"nativescript-angular": "^7.2.3",
"nativescript-camera": "^4.4.0",
"nativescript-fingerprint-auth": "^6.2.0",
"nativescript-localstorage": "^2.0.0",
"nativescript-plugin-firebase": "^8.1.1",
"nativescript-theme-core": "^1.0.4",
"nativescript-vibrate": "^2.1.3",

Describe the bug
after running tns run ios --emulator any changes thereafter appears to crash and reloading needs to be executed manually by closing emulated/virtual application and reloading it.
Occurs after updating Nativescript and plugins 5.3.0. See crash report below
To Reproduce
tns run ios --emulator
Expected behavior
Reload after changes shouldn't crash.
Sample project
Additional context
CONSOLE LOG file:///app/tns_modules/@angular/core/bundles/core.umd.js:15747:24: Angular is running in the development mode. Call enableProdMode() to enable the production mode.
(UIKitCore) [com.apple.UIKit:Animation] +[UIView setAnimationsEnabled:] being called from a background thread. Performing any operation from a background thread on UIView or a subclass is not supported and may result in unexpected and insidious behavior. trace=(
0   UIKitCore                           0x0000000107ea5146 kFixedAnimationDuration_block_invoke_5 + 125
1   libdispatch.dylib                   0x0000000106a8454b _dispatch_client_callout + 8
2   libdispatch.dylib                   0x0000000106a85d52 _dispatch_once_callout + 20
3   UIKitCore                           0x0000000107ea50c7 +[UIView(Animation) setAnimationsEnabled:] + 76
4   UIKitCore                           0x0000000107ea522f +[UIView(Animation) performWithoutAnimation:] + 84
5   UIKitCore                           0x00000001070fdb83 -[UIVisualEffectView _updateSubviews] + 325
6   UIKitCore                           0x00000001070fe9e8 -[UIVisualEffectView _configureAllEffects] + 1436
7   UIKitCore                           0x00000001070fce22 -[UIVisualEffectView setBackgroundEffects:] + 396
8   UIKitCore                           0x00000001071071b8 -[_UIBarBackground updateBackground] + 229
9   UIKitCore                           0x0000000107107467 -[_UIBarBackground transitionBackgroundViews] + 208
10  UIKitCore                           0x000000010719170c -[_UINavigationBarVisualProviderModernIOS _updateBackgrounds] + 851
11  UIKitCore                           0x000000010719194e -[_UINavigationBarVisualProviderModernIOS layoutSubviews] + 272
12  UIKitCore                           0x0000000107146691 -[UINavigationBar layoutSubviews] + 256
13  UIKitCore                           0x0000000107eb3795 -[UIView(CALayerDelegate) layoutSublayersOfLayer:] + 1441
14  UIKitCore                           0x00000001071463e8 -[UINavigationBar layoutSublayersOfLayer:] + 248
15  QuartzCore                          0x000000010425bb19 -[CALayer layoutSublayers] + 175
16  QuartzCore                          0x00000001042609d3 _ZN2CA5Layer16layout_if_neededEPNS_11TransactionE + 395
17  UIKitCore                           0x0000000107e9e077 -[UIView(Hierarchy) layoutBelowIfNeeded] + 1429
18  UIKitCore                           0x00000001072f7d87 -[UINavigationController _positionNavigationBarHidden:edge:initialOffset:] + 800
19  UIKitCore                           0x00000001072f8024 -[UINavigationController _positionNavigationBarHidden:edge:] + 388
20  UIKitCore                           0x00000001072f76d7 -[UINavigationController setNavigationBar:] + 1430
21  UIKitCore                           0x00000001072f7010 -[UINavigationController _navigationBarHiddenByDefault:] + 145
22  UIKitCore                           0x00000001072ff4f1 -[UINavigationController loadView] + 176
23  UIKitCore                           0x00000001073aa0ee -[UIViewController loadViewIfRequired] + 175
24  UIKitCore                           0x00000001073aa940 -[UIViewController view] + 27
25  NativeScript                        0x000000010200843d ffi_call_unix64 + 85
26  ???                                 0x0000000131999b50 0x0 +<PHONE_NUMBER>

@isawk Thank you for finding and reporting this issue. The fix will be released later today in version<EMAIL_ADDRESS>


Ecobee - Celsius

Related issue (if applicable): fixes #3899
**Pull request in home-assistant.github.io

Changed based on discussion with @turbokongen as he felt it would impact all climate modules.  This is tested only on ecobee in both metric and imperial configurations.

These changes look good 🐬


Design updates

This PR continues the work from #73, including:

homepage, Businesses, Maintainers, and user layouts;
small layout and typography fixes for different screen sizes and new components.

Ready for new creative assets!
cc @sophshep

Some design feedback:
Home

The navigation could be given a wider container (.container-lg). This will give more breathing room to the links.
On smaller screens, the "sign up with github" wraps:
. This should be a block element so it jumps to the next line.
The GitHub logo should be removed from each of the buttons (we usually don't put it in our sign up buttons)
Too much extra space here - we can remove the horizontal rule and let the bg colors separate the sections
The form gets pretty squished on small screens:

Business

The Set A Reminder box here isn't prominent enough. What if it was white?

User profile page

Don't forget to give this page some design love! You can get to it by hitting "sign in with github" and then accepting.

Thanks for the feedback, @sophshep! Updates made in the latest set of commits.
User profile layouts:
Logged-in user with some profile info filled out & some commit history:

"Empty" state of a user who isn't you, who hasn't yet joined, but has lots in their GitHub profile:

Welp, that didn't work!
@MikeMcQuaid, can you give me (and @skullface!) full access to this repo so that we can make changes?

Sorry @sophshep. You have access now.


Unexpected error occured on clicking City.

Duplicate of #41

Fixed in https://github.com/someshkar/covid19india-network/pull/54


2.1.16 - Video background issue

I just started using this Pluign, which i LOVE it btw :)
However, on latest version 2.1.16 while everything works fine with images but videos doesn't work
I also tested on your Demo page
same issue which the url returns [object Object]

Also noticed this and would love to know why the video feature doesnt work. Thanks for a update!


Add Similarity Join Predicate and Reuse the old Join

This PR adds SimilarityJoinPredicate, which is used to join different tuples if two tuples' values in spans are similar within a similarity threshold.
SimilarityJoinPredicate implements the IJoinPredicate interface and it is parallel to the existing JoinDistancePredicate. It is able to use the existing Join class (which implements nested loop join) after some minor modifications.
SimilarityJoinPredicate can also re-use the existing JoinTestHelper after some minor modifications.

@chenlica To review this PR, start from the newly added class SimilarityJoinPredicate and its test cases SimilarityJoinTest. There are some newly added test data in JoinTestConstants
Then proceed to review the interface changes in Join, IJoinPredicate and JoinDistancePredicate. These changes are made to enable SimilarityJoinPredicate to re-use the existing Join code.
There are also some changes in JoinTestHelper and the old Join test. You can safely ignore these changes, since the changes are also for reusing the test helper for the new test.

@zuozhiw I gave two batches of review comments.  Your instructions made the review much easier :-)


Admin panel to list resources by type

This will help finding resources easier as well potentially avoid timeout issue when we have large number of resources and all getting loaded on to a single page.

@pkdash can we close this?

@cuahsimarko I am going to close this even though this has not been implemented. Probably this is not an issue any more.


Updated how to determine if a node is ready or not

Related to #37 this updates how the check for NodeStatus is done. Please take a look @sttts
//cc @preillyme

LGTM but will wait for a :+1: from @sttts to merge

lgtm

LGTM

Can you build and push a v4 version with this patch?

@mikedanese can you please do the push for @sttts?

looks like v4 was pushed https://github.com/kubernetes/kubernetes/commit/b660cf9596149b23df4dd3df1f2d1e0bf9f5f2ce


Fix a bug where basepath nextUrl is invalid when it should be valid

Description
[Describe what this change achieves]
Category
[Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation]
Why these changes are required?
What is the old behavior before changes and new behavior after changes?
Issues Resolved
[List any issues this PR will resolve (Is this a backport? If so, please add backport PR # and/or commits #)]
Testing
[Please provide details of testing done: unit testing, integration testing and manual testing]
Check List

[ ] New functionality includes testing
[ ] New functionality has been documented
[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Without the change the test fails


remove screenshots from genome-annot/annot-w-prokka

genome-annot/annotation-with-prokka
@bebatut

@AnnaSyme, @Slugger70 do you want to have a look at the changes?


Document the Archive initialization logic better

Archives can be initialized with URLS, or from short names of .csv files. Having it both ways is confusing (see #156). Documentation in the README would make this better.

Fixed with #500 ?


Docker Password Mask in ECR Login action

Description
We have identified a critical issue in our pipeline where the Docker password is not masked when logging into ECR. This exposes our password anytime DEBUG logs are enabled in a workflow. This PR addresses this security concern by masking the Docker password during the ECR login process.
Fixes #1415
Type of change

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
The changes have been tested by executing the workflow and ensuring that the Docker password is masked during the ECR login process. Further tests were conducted to ensure that the masking does not interfere with other functionalities.

[x] Test A: Verify Docker password is masked during ECR login by having no more warning, as seen in this action

Checklist

[x] My changes generate no new warnings

FYI, github_actions isn't a valid label for our releases. You can drop it from this PR. @ldraney


Inconsistent spacing with button groups across multiple browsers

This is a modification and re-opening of #5735, which was closed despite not being fixed.
The issue looks like this (from the Buttons Group documentation):

(credit for image goes to ghost who opened #5735)
Notice the uneven gap on the left.
I made this issue because I found a solution that has worked for me and I wanted to post my findings hopes that someone might implement it as a more permanent solution to this issue. I do not have enough familiarity with the project to feel comfortable messing with its code, so I am submitting it for scrutiny as an issue. As far as I can tell it fixes the issue across all web-browsers and does not break anything, but your mileage may vary.
Here is the solution:
in \foundation\components_button-groups.scss,  near line 152 :
change
// We use this to make the buttons even width across their container
@if $even {
    width: percentage((100/$even) / 100);
    button, .button { width: 100%; }
}

to
// We use this to make the buttons even width across their container
@if $even {
    width: percentage((100/$even) / 100);
    button, .button { width: 101%; }
}

Basically just change width from 100% to 101%.
It doesn't seem to have broken anything and as far as I can tell it fixes the problem across all my browsers!
Here it is afterwards, fixed, in one of my own pages

Cheers!

Thanks for posting your solution. I don't think it's ideal though as a framework solution. This spacing is due to how Chrome is rounding widths.
I dug back in the codebase and found the commit that fixed this a while back. https://github.com/zurb/foundation/commit/d13e7e3b453b572317cf966e9659613d212519aa
Looks like the mixin has changed a bit since then but we just added the fix back in.

55ddbb7


Issue#1106

@ewpatton I've added the scrollable property to HVArrangement. Kindle review.
Solves #1106
During testing, I'm facing an issue. Whenever we switch the scrollable property, a new instance of the respective view group is created and added at the end of the Component Container. For this, we need to have a method that would replace the view group at the same index in the component container.
Can you please help me out with the same?
I've attached below a couple of screenshots. The first one of them is before checking the scrollable property and the other one is after checking the scrollable property.

Thank you.

Can one of the admins verify this patch?


Configure lerna to increment versions together and generate docs

#6199 generates docs for all the new sdk packages

#6199 generates docs for all the new sdk packages


[MM-23095] - Update action to take into consideration system posts

Summary
Fixes a JS error related to marking a system post as unread. There are two types of posts and system posts have an array of posts ID's, which needs to be taken into account in the mattermost-redux action.
Ticket Link
https://mattermost.atlassian.net/browse/MM-23095
Related Pull Requests

Has webapp changes (https://github.com/mattermost/mattermost-webapp/pull/5042)

Updated


Add MD4,MD5; add warning about obsolete hash functions

Resolves #71 by adding MD4 and MD5 to the list of supported hash functions.
Adds a note to the README cautioning about their use.

@jbenet could you please look this over? I'm actually in need of this functionality.

I think these codes look good to me, what do you think @diasdavid @whyrusleeping
@celeduc could you also add these to the csv in multicodec? That one is the canonical table and multihash is just a subset. I dislike the duplication too, PRs very welcome :)

Seems that there is no collision with https://github.com/multiformats/multicodec/blob/master/table.csv, as @lgierth said, we prefer to have the codecs first merged at the multicodec table then on the specs that dependent on it, so once we have that, we are golden to merge all of them PRs :)

I submitted PR #41 to multicodec, where it's held with a comment by @Kubuxu

thank you @celeduc :)


TypeError: unhashable type: 'dict'

When I write fig.yml like this:
web:
  build: .
  volumes:
    - .:/var/www/sso
  environment:
    - MOUNTED: true
  ports:
    - "4000:80"
  links:
    - db

Traceback (most recent call last):
  File "<string>", line 3, in <module>
  File "/Users/ben/fig/build/fig/out00-PYZ.pyz/fig.cli.main", line 31, in main
  File "/Users/ben/fig/build/fig/out00-PYZ.pyz/fig.cli.docopt_command", line 21, in sys_dispatch
  File "/Users/ben/fig/build/fig/out00-PYZ.pyz/fig.cli.command", line 28, in dispatch
  File "/Users/ben/fig/build/fig/out00-PYZ.pyz/fig.cli.docopt_command", line 24, in dispatch
  File "/Users/ben/fig/build/fig/out00-PYZ.pyz/fig.cli.command", line 56, in perform_command
  File "/Users/ben/fig/build/fig/out00-PYZ.pyz/fig.cli.main", line 427, in up
  File "/Users/ben/fig/build/fig/out00-PYZ.pyz/fig.project", line 174, in up
  File "/Users/ben/fig/build/fig/out00-PYZ.pyz/fig.service", line 207, in recreate_containers
  File "/Users/ben/fig/build/fig/out00-PYZ.pyz/fig.service", line 237, in recreate_container
  File "/Users/ben/fig/build/fig/out00-PYZ.pyz/fig.service", line 176, in create_container
  File "/Users/ben/fig/build/fig/out00-PYZ.pyz/fig.service", line 370, in _get_container_create_options
TypeError: unhashable type: 'dict'

Fig will raise error like this, looks like the root cause is I pass an array in environment, if I give a dict, then it works.
My fig version is 1.0.1, docker is 1.3.2

environment is a mapping. It should be:
environment:
    MOUNTED: true

@marksteve But in doc it's mentioned

environment
Add environment variables. You can use either an array or a dictionary.

Environment variables with only a key are resolved to their values on the machine Fig is running on, which can be helpful for secret or host-specific values.

environment:
RACK_ENV: development
SESSION_SECRET:
environment:

RACK_ENV=development
SESSION_SECRET

You've fallen prey to YAML's permissive syntax.
This is an array of strings:
environment:
  - MOUNTED=true

This is a dictionary:
environment:
  MOUNTED: true

This is an array of dictionaries:
environment:
  - MOUNTED: true

Sigh.

@aanand Yeah, got it. Thanks a lot.

I request that this issue be re-opened. The error in the YAML file certainly shouldn't cause an internal error with a stacktrace. Docker-compose should be checking that the YAML file satisfies the expected schema, and providing the user with sensible error messages if it doesn't.

This should be handled by the new validation code, which will be out in Compose 1.5.


Auto detecting user's systems colour mode and loading the game with that mode

auto detecting the systems colour mode so that the user doesnot have to change it manually ,
by this  if the user has  his device on dark mode the the game will auto load with dark mode and vice versa and the manual choosing option will of course be there too like it is already
assign me this issue please @iamparas0

auto detecting the systems colour mode so that the user doesnot have to change it manually , by this if the user has his device on dark mode the the game will auto load with dark mode and vice versa and the manual choosing option will of course be there too like it is already
assign me this issue please @iamparas0

Go for it please put ss before pr


is it possible to specify sourceMappingURL?

Hi guys.
Help, please, with the specifying of sourceMappingURL.
We have our own dev-server, so we need to specify sourceMappingURL as a static asset URL like /dist/bundle.js.map, but the default output of the webpack is
# sourceMappingURL=bundle.js.map.
Thanks in advance.

You can use the append option for the SourceMapDevToolPlugin. i. e. append: "\n//# sourceMappingURL=/dist/"

Thanx a lot for the response.
But tell, please, how could I specify it for the dynamic names like bundle.js, 1.bundle.js ... n.bundle.js?


Tutorials

Should we add some tutorials links ? What do you think ?

I am not convinced. In general I think it is better to focus on more comprehensive resources.

I agree with you on that. But I was thinking of that maybe as a side project. Creating eventually the Spark Learning Hub. I might be early for that now, but eventually wouldn't it be a good idea ?

If you feel like this is a good idea and want to maintain it i trust your judgment. We can create a separate repository for that.

I also think that we should create a separate repository fo tutorials as well. Thus I'm closing this issue for now.


Fix location of validating hostname functionality

Similar in functionality to #807 (thanks for the tipoff @crunchywelch!), I'd prefer to validate the hostname before we attempt to make the host / serialize it to disk at all.
There seems to be no need for multiple returns as the regex match only returns bool, so I've updated that as well.
cc @ehazlett @sthulb
Signed-off-by: Nathan LeClaire<EMAIL_ADDRESS>

I don't think this is related to your PR but should we be showing the entire help test for an invalid hostname?

I don't think this is related to your PR but should we be showing the entire help test for an invalid hostname?

Do you mean the "check on resources you created" message?

I can't actually see anywhere that calls ValidateHostName(name string). We seem to have a regression there.

@nathanleclaire this was an error is my usage -- disregard :)
@sthulb does that answer your question?

LGTM


Flux RGBW Bulb Error on light.turn_on

Home Assistant release with the issue:
0.73.1
Last working Home Assistant release (if known):
0.72.1
( worked perfectly )
Operating environment (Hass.io/Docker/Windows/etc.):
Hassio running on Ubuntu Server
Component/platform:
Flux (RGBW) LED Light Bulb
Description of problem:
Unable to perform light.turn_on in 0.73.1 (LoveLace UI)
Effects still function using UI
light.turn_off still functions using UI
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
light:
  ### office desk lamp
  - platform: flux_led
    devices:
      !secret office_desk_lamp_host:
        name: office_desk_lamp
#
# if using the developer console services, light no longer turns on but turns off via this method:
Service
light.turn_on

Entity
light.office_desk_lamp

Service Data (JSON, optional)
{
  "entity_id": "light.office_desk_lamp"
}

Traceback (if applicable):
2018-07-19 22:29:34 ERROR (MainThread) [homeassistant.core] Error executing service <ServiceCall light.turn_on: entity_id=['light.office_desk_lamp']>
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/homeassistant/core.py", line 1021, in _event_to_service_call
    await service_handler.func(service_call)
  File "/usr/lib/python3.6/site-packages/homeassistant/components/light/__init__.py", line 360, in async_handle_light_service
    await light.async_turn_on(**params)
  File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/lib/python3.6/site-packages/homeassistant/components/light/flux_led.py", line 266, in turn_on
    self._bulb.setRgbw(*tuple(rgb), w=white, brightness=brightness)
  File "/usr/lib/python3.6/site-packages/flux_led/__main__.py", line 868, in setRgbw
    raise Exception
Exception

Additional information:

If I select a color, the light does not respond. However, if I then physically switch the light off and back on, the color that was selected is the one that the bulb displays. I am then able to call "effects" and am able to turn the light off using controls in hass.
Note: I had just refreshed all of the yaml related to this light to fix minor annoyances in 0.72.1 prior to switching over to Lovelace. So far this is the first component issue that i have experienced using Lovelace over the default UI; however, switching to default UI has same result

Tested in 0.74.0. Able to turn the light on or off; unable to select colors, but am able to send effects commands

Still an issue in 0.74.2
selecting any effect from the entities pop up menu functions correctly; however:
simply attempting to turn the light on results in:
2018-07-26 21:05:29 ERROR (MainThread) [homeassistant.core] Error executing service <ServiceCall light.turn_on: entity_id=['light.office_desk_lamp'], hs_color=(135.0, 100.0)>
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/homeassistant/core.py", line 1038, in _event_to_service_call
    await service_handler.func(service_call)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/light/__init__.py", line 360, in async_handle_light_service
    await light.async_turn_on(**params)
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/light/flux_led.py", line 269, in turn_on
    self._bulb.setRgbw(*tuple(rgb), w=white, brightness=brightness)
  File "/usr/local/lib/python3.6/site-packages/flux_led/__main__.py", line 868, in setRgbw
    raise Exception
Exception

Additionally, this error occurs on each attempt to select a color from the picker within the pop up menu
service light.turn_off functions correctly.

This is confusing. Can you list just a single sequence of steps that do not work as expected?
Do not mention a lot of stuff that does work :)

Thanks for looking!
Essentially what doesn’t work:
Turning the light on any time a solid color is selected.
Details:
— Turning the light on via previously working input selections fail
— Color picker does not work

This exception is raised because "RGBW command sent to non-RGBW device".
I suggest you try adding mode: rgb to your configuration:
light:
  ### office desk lamp
  - platform: flux_led
    devices:
      !secret office_desk_lamp_host:
        name: office_desk_lamp
        mode: rgb

Try it anyway.

I'm seeing this error also popping up in the log. I have a Magiclight v7 and if I set the mode: rgbw, it throws an error on line 868 (rgbw to a nonRGB bulb?) but it is a rgbw bulb. If I set it to mode: rgb it's fine. If I don't add mode it defaults to rgbw and throws the error. How can I see what the software thinks it is, i.e. command line call for debugging info?

@amelchio I tried it. Setting to RGB worked as expected and corrected the issue of not being able to turn on the light or select colors; however, I'm (obviously) unable to select "warm" white color, which I was able to do previously. I appreciate the suggestion but I still have a problem here...
I believe there was a change between 0.72.1 and 0.73+ that caused this.

That's odd, as far as I can see flux_led has never supported color temperature.

Not sure what to tell you ... it truly is an RGBW bulb ... in version 0.72.1 I had WORKING automations to switch between warm white light (2700K/typical lamp) and colors or 'cool'/daylight light. This was with the default config (RGBW) ... RGB works as far as turning the light on/off goes, but I've lost my most-used, warm white setting. 😞

Again ... something between changes from 0.72.1 to ~0.73 caused the issue.

I think that I see the issue now. Your bulb probably has RGB and W light but cannot set both at the same time. This was indeed changed in 0.73, to support lights that do have that ability.
Can you post those automations that used to work?

Check my repo:
GitHub /rrubin0/hassio-config
On Tue, Aug 7, 2018 at 11:12 PM Anders Melchiorsen<EMAIL_ADDRESS>wrote:

I think that I see the issue now. Your bulb probably has RGB and W light
but cannot set both at the same time. This was indeed changed in 0.73, to
support lights that do have that ability.
Can you post those automations that used to work?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/15566#issuecomment-411297216,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUT6RIf2QRG2HxoLVfthINYamvifOBUDks5uOoFAgaJpZM4VXfBB
.

still no love ... have not yet upgraded to 0.76.x since nothing is in the release notes for a fix. Flux light still not working properly. If anyone could look into it, I'd appreciate it...or if someone has a workaround / sees a problem with my code, then let me know. thanks!

You did not yet post the relevant configuration as requested.
Looking at the code though, it seems that providing just a brightness value used to toggle on a white mode before 0.73. This was wrong because setting a new brightness level should not change the color. However, fixing that issue has then removed the ability to activate the white mode for bulbs of type rgb.
Let's see if @oblogic7 is around to comment.

Actually, that appears to be 0.68 working like that, I see no code in 0.72.1 that could enable the white mode.
Anyway, I just wanted to add that you can upgrade Home Assistant and copy an old flux_led.py to <config>/custom_components/light/flux_led.py to downgrade just the flux_led light module.

The changes I made to the flux component were only tested against RGBW controllers.  I do not currently have any bulbs.
@rrubin0 If you can link me to the exact bulb you are using I'll be glad to purchase one and try to figure out why it is not behaving as expected.

@amelchio I posted a link to the configuration just above my last post a couple of weeks ago. That is a good idea, replacing just the .py code ... maybe I'll give that a shot.
@oblogic7 thanks for looking at this! The bulb I have is the first gen version of this one: https://www.amazon.com/dp/B01KJEKDFS?m=A1387MCC2SPAIV&th=1
I believe it has been redesigned since I purchased, as mine has the heat sink fins around it. . . It's been a good RGBW bulb for a while now tho. I got it cheap on sale but I'm sure other users who invested in them would be upset that the code is not working properly.

@amelchio Yo man, great idea! I copied the working 0.72.1 flux_led.py to my custom components folder and am happy to report that I once again have full RGBW control over my Flux LED bulb!

Color picker: working
Effects: working
Brightness: working
Warm white: working

This is a suitable workaround until a more permanent solution can be developed. Thank you all.

I am confused that 0.72.1 works for you. Can you do a sha1sum or something to verify that we are looking at the same file?

Please tell me why you have added white_value to your linked config.

Well, it's in the docs :)
I added it as part of my troubleshooting the last time that the component broke my bulb's behavior. It started working and so I left it. It can probably be removed. I will test that and report back asap. Thanks for the continued support too!!

So rather than copy/pasting the relevant automation that I asked for, you point me at 500 lines of configuration that does not even match what you are using 😖

Not totally sure what you’re talking about but I did recently update my github so, apologies if previous link has broken.
My flux configuration is here now and is relevant to this thread:
https://github.com/rrubin0/homeassistant-config/blob/master/packages/office.yaml

If somebody wants to fix this, I propose using setWarmWhite255() for white_value, setRgb() for hs_color and only setRgbw() if both white_value and hs_color is specified.
Also include SUPPORT_WHITE_VALUE for MODE_RGB in supported_features() and don't test for MODE_RGBW in turn_on().
That should do it :-)

I believe I tried a similar approach when I added separate control of white_value.  I don't remember why it didn't work out.  The bulb I ordered came in today, but I am heading out of town for the holiday weekend tonight.  Hopefully I will have some time on Monday to take a look and see if I can work on it.

@oblogic7 Hey man, Hope you had a great Labor Day Weekend.
I appreciate you looking into this and going so far as to purchase a bulb. Thank you again for the contribution to the community!

I was able to track this down to the flux_led library that HA uses to communicate with the bulb.  The bulb is definitely capable of RGBW, but the library was not looking for the value returned by this bulb when checking for RGBW capability.
I have a PR open on the library.  Once that is merged, we can bump the library version on the flux_led component for HA and all should be good.  The library repo is owned by @Danielhiversen, so hopefully he will get it merged quickly.
https://github.com/Danielhiversen/flux_led/pull/55

that is great news - thanks!

I see some conflicts in the merge, but if you want me to test manually, let me know and I can add/modify what I'm using for custom component "flux_led.py"

I'm trying to track down why the change is causing the tests to fail on the library.  Feel free to test it out and verify if it works for you.

Since the commit was to main.py I'm not sure how to use that for testing in the state it is in ... Can you make a "flux_led.py" file for me with these changes that I can test as a custom component, perhaps?

The change can't be made in a custom component since it is in the library that is used by the component.

I‘d like to test that...
On which version of home assistant did you edit flux_led.py?
Or, do you mind sharing your file?

I just updated to the latest package via pip this weekend. So it should be the currently released version.

@btreecat
I tested on the bulb; the white values work (selecting 'warm' and 'warm dim' in my setup) but the color picker does not, nor am i able to call colors from my input select list. Closer! but not quite a valid fix, I'm afraid. I'm still on 78.3 but see there has been no updates to the code in the last 2 months, so we are using the same flux_led.py file.

Have you tried changing color with just the flux_led Python library the
home assistant component is based on?
See if you can use it to change your rgb values from the command line.
Also what did your setrgbw call look like, did you only pass the rgb values
and brightness?
--
Stephen Tanner
Part 107 Certified Drone Pilot
Web, Research, and Cloud Application Developer
Virginia Tech Transportation Institute
https://TannAir.com
https://StephenTanner.com
On Sun, Oct 14, 2018, 01:38 Rick Rubino<EMAIL_ADDRESS>wrote:

@btreecat https://github.com/btreecat
I tested on the bulb; the white values work (selecting 'warm' and 'warm
dim' in my setup) but the color picker does not, nor am i able to call
colors from my input select list. Closer! but not quite a valid fix, I'm
afraid. I'm still on 78.3 but see there has been no updates to the code in
the last 2 months, so we are using the same flux_led.py file.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/15566#issuecomment-429598273,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAO3HCFV1hQw8MuQgglev5KsMM8QkMFLks5uks3dgaJpZM4VXfBB
.

That was my original issue ...bulb would not respond to color picker or list actions.
I did notice that if I turned the bulb off at the switch after selecting a color it would change to the selected color upon turning the switch back on.
I have not specifically tried testing it again, as the file does not appear to have changed since the last test. I’ll do this after upgrading to 0.79.x or 0.80.x (planning to do soon) and report back

But have you tested the underlying library directly?
If the underlying library isn't working right then there isn't a way to fix
it in home assistant.
Did you change the line for the setRGBW?
--
Stephen Tanner
Part 107 Certified Drone Pilot
Web, Research, and Cloud Application Developer
Virginia Tech Transportation Institute
https://TannAir.com
https://StephenTanner.com
On Tue, Oct 16, 2018, 16:36 Rick Rubino<EMAIL_ADDRESS>wrote:

That was my original issue ...bulb would not respond to color picker or
list actions.
I did notice that if I turned the bulb off at the switch after selecting a
color it would change to the selected color upon turning the switch back on.
I have not specifically tried testing it again, as the file does not
appear to have changed since the last test. I’ll do this after upgrading to
0.79.x or 0.80.x (planning to do soon) and report back
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/15566#issuecomment-430390676,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAO3HBaFiZQIPyM3vaC9sM0KqhsLJ7Wuks5ulkNFgaJpZM4VXfBB
.

I'm unable to test this directly but did test with the native code in 0.80.3 and the issues persist.
I can say that this used to work fine, so the library is probably ok. The flux_led.py file from 0.72.1 also works fine too and that is what I'm using for now as a custom component.

Hey guys, sorry for the lack of response.  Been pretty busy lately.
I was able to update the tests on the flux library, so that PR should be merged soon.  When that happens, we will be able to bump the library version so the changes will be available in HA.  I'm confident that this will correct the behavior that is being reported here.  I have tested on the bulb that @rrubin0 linked above and it is behaving exactly the same as the other two magic home controllers that I have.

Confirm ... working now with old code once again ... I do notice that the white value setting is removed in this older version; not sure if that matters tho, the bulb is working as RGBW via my input_selections and the native flux app, whereas I barely have on/off control with the updated code.

Fix is also not working for me either.
I'll clone the latest copy of the flux_led library and do some more testing
of the method calls.
--
Stephen Tanner
Part 107 Certified Drone Pilot
Web, Research, and Cloud Application Developer
Virginia Tech Transportation Institute
https://TannAir.com
https://StephenTanner.com
On Wed, Oct 31, 2018, 01:38 Rick Rubino<EMAIL_ADDRESS>wrote:

Confirm ... working now with old code once again ... I do notice that the
white value setting is removed in this older version; not sure if that
matters tho, the bulb is working as RGBW via my input_selections and the
native flux app, whereas I barely have on/off control with the updated code.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/15566#issuecomment-434567405,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAO3HI-p-cU_ZW2hGNn8S5BvJmBJktP2ks5uqTdngaJpZM4VXfBB
.

Thanks for the reports guys.
@rrubin0 I was able to reproduce the unresponsive strip controller issue on this controller.  Seems that it is not correctly detecting that it is RGBW capable.  I need to dig further but specifying mode: 'RGBW' in the config makes it work for me.
Regarding the issue of getting the same bad result, do you mean you are still seeing this error?  If not that, can you describe what you are seeing or how you are trying to control the light (GUI, service calls, etc)?
@btreecat Thanks for diving in.  Curious to see what you find as well.  Be sure to try setting mode: 'RGBW' for the devices that aren't working to see if it changes the behavior.

TEST 1: GUI CONTROL
Turn light on via GUI = OK; no errors
Open colorpicker in GUI = presented with menu which now includes "white value" slider
increase white value via slider = no effect; no errors
increase brightness via slider = no effect; no errors
choose new color from colorpicker via GUI = no effect; no errors
Turn light off via GUI = OK; no errors
TEST 2: Service Calls via Input Select Menu
Select option in my input select list "cool" = no effect; no errors; entry in log "executing step call service" but light does not turn on; GUI shows light is on and is supposed to be at a white value; no errors
(and now it is not responding to on/off or color changes via GUI; GUI icon reflects the color it thinks it should be but light does not respond; no errors)
Select option "random" input selection = light turns on and is able to randomly pick a color
(light responds to on/off commands after this option is selected; no errors)
(also, if I now change a color via the colorpicker, the color does not change, the light responds to off command, but will not respond to an on command)
Selecting my predefined "warm or warm dim" settings from the input select list have no effect; no errors
Selecting ANY effect from the GUI menu works like a charm (strobe; crossfade; color jump/loop) but brightness control is unresponsive and interrupts the effect; no errors
VERDICT (thus far) = The light only responds to on/off and effects...BUT If any value changes are attempted (color, brightness, white level) the bulb will become unresponsive to all commands except the OFF command until the last state was an "effect" setting or random color (aka a working mode).
All of the above tests were performed sequentially, with the same configuration used as the 'custom component' code (from 0.72.1)

Excellent work! This is exactly my experience with my bulb.
--
Stephen Tanner
Part 107 Certified Drone Pilot
Web, Research, and Cloud Application Developer
Virginia Tech Transportation Institute
https://TannAir.com
https://StephenTanner.com
On Thu, Nov 1, 2018, 01:07 Rick Rubino<EMAIL_ADDRESS>wrote:

TEST 1: GUI CONTROL
Turn light on via GUI = OK; no errors
Open colorpicker in GUI = presented with menu which now includes "white
value" slider
increase white value via slider = no effect; no errors
increase brightness via slider = no effect; no errors
choose new color from colorpicker via GUI = no effect; no errors
Turn light off via GUI = OK; no errors
TEST 2: Service Calls via Input Select Menu
Select option in my input select list "cool" = no effect; no errors; entry
in log "executing step call service" but light does not turn on; GUI shows
light is on and is supposed to be at a white value; no errors
(and now it is not responding to on/off or color changes via GUI; GUI icon
reflects the color it thinks it should be but light does not respond; no
errors)
Select option "random" input selection = light turns on and is able to
randomly pick a color
(light responds to on/off commands after this option is selected; no
errors)
(also, if I now change a color via the colorpicker, the color does not
change, the light responds to off command, but will not respond to an on
command)
Selecting my predefined "warm or warm dim" settings from the input select
list have no effect; no errors
Selecting ANY effect from the GUI menu works like a charm (strobe;
crossfade; color jump/loop) but brightness control is unresponsive and
interrupts the effect; no errors
VERDICT (thus far) = The light only responds to on/off and effects...BUT
If any value changes are attempted (color, brightness, white level) the
bulb will become unresponsive to all commands except the OFF command until
the last state was an "effect" setting or random color (aka a working mode).
All of the above tests were performed sequentially, with the same
configuration used as the 'custom component' code (from 0.72.1)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/15566#issuecomment-434932016,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAO3HOsqhePPcmfCUuiElH-Uc4BnGxcgks5uqoGRgaJpZM4VXfBB
.

I don't see any mention of whether or not you tested with mode: 'RGBW' set on the config.  Can you confirm that you added that before testing?

Mode RGBW is the default to my knowledge. My config is posted in /packages/office if you want to look. I’m mobile so I can’t link as well.

You do have that mode set on your config.  I'm curious to know how the light behaves if you set mode: rgb.  If that doesn't improve anything, try removing the mode completely.  That will cause the component to use whatever mode the bulb/library is returning.  Let me know if either of those cases behave differently.

OK, I was able to re-test just now. As requested, I changed the flux_led bulb mode from RGBW to RGB and restarted HA using 0.81.2 default code/library. Results are as follows:
Turn light on via GUI = OK; no errors
Open colorpicker in GUI = presented with menu which does not include a "white value" slider
increase brightness via slider = OK; no errors
choose new color from colorpicker via GUI = OK; no errors
Turn light off via GUI = OK; no errors
Select option in my input select list "cool" = OK; no errors
increase/decrease brightness via slider = OK; no errors
Select option in my input select list "warm" = no effect; no errors - FAIL
VERDICT: All functions of the bulb work properly (including effects, random, strobe) EXCEPT selecting 'warm' white light (via input_select); no errors. Since the white light is primarily what I use on this light, it is a deal breaker to use this as a long-term workaround.

That is helpful.  Sounds to me like the bulb is reporting that it is RGBW compatible, but requires the white level to be set via the warm white functions on the library.  I will take a look at the code and see if there is a way we can work around that or if there is a way that the library can already handle this situation.

This is exactly why I tried to detect the difference in input commands and
then if detect warm white, call the setWarmWhite() method instead of the
setRGBW().
Setting the bulb to RGB works fine for color but doesn't support the warm
white channel.
I don't think it's reliable to have a predefined hard coded list of bulb Id
that work with rgbw/rgb/w modes. It's a great way to play whack-a-mole with
hardware support. But not sure what the alternative is other than just
require a bulb to have a mode be set and trusting it.
Additionally there is a cold white channel (w2) in the underlying library.
Does the ha light package support more than one white ch option or an
ability to pick one or the other? I hadn't had time to look into that
deeply enough.
--
Stephen Tanner
Part 107 Certified Drone Pilot
Web, Research, and Cloud Application Developer
Virginia Tech Transportation Institute
https://TannAir.com
https://StephenTanner.com
On Fri, Nov 2, 2018, 09:47 Matt Snyder<EMAIL_ADDRESS>wrote:

That is helpful. Sounds to me like the bulb is reporting that it is RGBW
compatible, but requires the white level to be set via the warm white
functions on the library. I will take a look at the code and see if there
is a way we can work around that or if there is a way that the library can
already handle this situation.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/15566#issuecomment-435385067,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAO3HKcxZcFwm6sqaf0ACFhBe8sPj0TEks5urEzTgaJpZM4VXfBB
.


Backend TypeError Error

Description
INFO:     <IP_ADDRESS>:50158 - "GET /api/agent/TestAgent2 HTTP/1.1" 500 Internal Server Error
ERROR:    Exception in ASGI application
Traceback (most recent call last):
File "/Users/timur/Library/Python/3.9/lib/python/site-packages/uvicorn/protocols/http/httptools_impl.py", line 435, in run_asgi
result = await app(  # type: ignore[func-returns-value]
File "/Users/timur/Library/Python/3.9/lib/python/site-packages/uvicorn/middleware/proxy_headers.py", line 78, in call
return await self.app(scope, receive, send)
File "/Users/timur/Library/Python/3.9/lib/python/site-packages/fastapi/applications.py", line 276, in call
await super().call(scope, receive, send)
File "/Users/timur/Library/Python/3.9/lib/python/site-packages/starlette/applications.py", line 122, in call
await self.middleware_stack(scope, receive, send)
File "/Users/timur/Library/Python/3.9/lib/python/site-packages/starlette/middleware/errors.py", line 184, in call
raise exc
File "/Users/timur/Library/Python/3.9/lib/python/site-packages/starlette/middleware/errors.py", line 162, in call
await self.app(scope, receive, _send)
File "/Users/timur/Library/Python/3.9/lib/python/site-packages/starlette/middleware/cors.py", line 92, in call
await self.simple_response(scope, receive, send, request_headers=headers)
File "/Users/timur/Library/Python/3.9/lib/python/site-packages/starlette/middleware/cors.py", line 147, in simple_response
await self.app(scope, receive, send)
File "/Users/timur/Library/Python/3.9/lib/python/site-packages/starlette/middleware/exceptions.py", line 79, in call
raise exc
File "/Users/timur/Library/Python/3.9/lib/python/site-packages/starlette/middleware/exceptions.py", line 68, in call
await self.app(scope, receive, sender)
File "/Users/timur/Library/Python/3.9/lib/python/site-packages/fastapi/middleware/asyncexitstack.py", line 21, in call
raise e
File "/Users/timur/Library/Python/3.9/lib/python/site-packages/fastapi/middleware/asyncexitstack.py", line 18, in call
await self.app(scope, receive, send)
File "/Users/timur/Library/Python/3.9/lib/python/site-packages/starlette/routing.py", line 718, in call
await route.handle(scope, receive, send)
File "/Users/timur/Library/Python/3.9/lib/python/site-packages/starlette/routing.py", line 276, in handle
await self.app(scope, receive, send)
File "/Users/timur/Library/Python/3.9/lib/python/site-packages/starlette/routing.py", line 66, in app
response = await func(request)
File "/Users/timur/Library/Python/3.9/lib/python/site-packages/fastapi/routing.py", line 237, in app
raw_response = await run_endpoint_function(
File "/Users/timur/Library/Python/3.9/lib/python/site-packages/fastapi/routing.py", line 163, in run_endpoint_function
return await dependant.call(**values)
File "/Users/timur/Agent-LLM/app.py", line 162, in get_agent_config
agent_config = Agent(agent_name).get_agent_config()
File "/Users/timur/Agent-LLM/Config/Agent.py", line 28, in init
self.PROVIDER = Provider(self.AI_PROVIDER, **self.PROVIDER_SETTINGS)
File "/Users/timur/Agent-LLM/provider/init.py", line 24, in init
self.instance = provider_class(**kwargs)
File "/Users/timur/Agent-LLM/provider/huggingchat.py", line 19, in init
if MAX_TOKENS <= self.MAX_TOKENS_CEILING
TypeError: '<=' not supported between instances of 'str' and 'int'
Steps to Reproduce the Bug

Start frond and back ends
Create agent
Select 'huggingchat' as AI provider
Set max tokens and AI temperature

Expected Behavior
Settings saved correctly
Actual Behavior
TypeError thrown
Additional Context / Screenshots
No response
Operating System

[ ] Microsoft Windows
[X] Apple MacOS
[ ] Linux
[ ] Android
[ ] iOS
[ ] Other

Python Version

[ ] Python <= 3.9
[ ] Python 3.10
[X] Python 3.11

Environment Type - Connection

[X] Local
[ ] Remote

Environment Type - Container

[ ] Using Docker
[X] Not Using Docker

Acknowledgements

[X] My issue title is concise, descriptive, and in title casing.
[X] I have searched the existing issues to make sure this bug has not been reported yet.
[X] I am using the latest version of Agent-LLM.
[X] I have provided enough information for the maintainers to reproduce and diagnose the issue.

Should be fixed in #274


Syntax error in class name with uppercase

When you attempt to create the name of the class in uppercase produces a syntax error
ip.zep
class IP
{
 ....
}

output
Zephir\ParseException: Syntax error in ...\ip.zep on line N
        class IP
        -------^

Identifiers in uppercase are reserved for constants, you have to use: Ip

@andresgutierrez Thanks!
I did so when transfer class from the incubator to core, see https://github.com/phalcon/cphalcon/pull/10572


provide a way to extend the Autocomple option button using svelte slots

Describe the feature in detail (code, mocks, or screenshots encouraged)
I started a project with skeleton where I want to use the Autocomplete component and display more than a text label for the selectable options.
I started by adding html tags inside the AutocompleteOption label property, but I can only put "standard" html tags this way and I'd like to use other svelte components there.
So I tried to do this by copying the skeleton Autocomplete.svelte into my project and added a named slot around the existing autocomplete Button (the button with the @html option.label still provides the default implementation)
The <slot> definition can pass the {option} property into the slot, this way when you define the  corresponding <svelte:fragment>   you can use the let:option={myOption} attribute to retrieve the current option and use it inside your fragment. This is better  described in the slot section of the svelte doc.
I also tried passing the onSelection callback, it works but in the end it seems easier to just call my function directly using the option.value or meta property.
It seems to work, but would probably require additional testing...
What type of pull request would this be?
Enhancement
Provide relevant links or additional information.
The test I made by copying the Autocomplete component in my project and adding the slot is
here

                        <slot name="optionButton" {option} {classesButton} {onSelection} >
                            <button class="autocomplete-button {classesButton}" type="button" on:click={() => onSelection(option)} on:click on:keypress>
                                {@html option.label}
                            </button>
                        </slot>

And the corresponding svelte:fragment where I use it is there
The selectable option is mapped to the artistOption variable:
                <DeezerAutocomplete bind:input={$artistSearch} options={$artistsFound} >
                    <svelte:fragment slot="optionButton" let:option={artistOption} >

                                {artistOption.meta.name}

                            <button class="btn"
                                    title="add all artist titles to the playlist"
                                    on:click={()=>addArtistTracks(artistOption.meta.id, trackSelections)}
                            ><AddIcon/></button>

                    </svelte:fragment>
                </DeezerAutocomplete>

Making a note that we'll evaluate this as part of Skeleton v3, which will support Svelte 5 and the new Snippet features.

In an effort to prepare for Skeleton v3, we're consolidate some related issues down to a single ticket. This will ensure that we can see the full context of requests when the time comes to refactor and update this feature going forward. If you wish to add additional feedback or suggestions, please so here:

https://github.com/skeletonlabs/skeleton/issues/2366


Datastore v2

Fixes #118

I will look into resolving any E2E test problems, but I don't think it should hold up the review.


CI: update CircleCI config for master to main branch rename

Let's see if this comes back green ....

FYI in the future you can push with [skip actions] [skip azp] to save some other CI cycles

I know, but in this case I do want to see all CI because we just renamed master to main - it could all be broken.

I thought I took care of this in #15314.

I thought I took care of this in #15314.

Ah yes you did, I got my wires crossed on branches when looking for a quick PR to trigger CI. Missed a git pull after setting up my main locally. Leaving this open to see CI status, then I'll close.

@rgommers I merged https://github.com/scipy/scipy.org/pull/430 and am ready to update netlify for scipy.org as soon as you rename its default branch.

Might want to check scipy-wheels as well, especially nightly builds of master. I forget what other changes may be needed.

Might want to check scipy-wheels as well, especially nightly builds of master. I forget what other changes may be needed.

Probably best to leave the MacPython repos alone. Hopefully we're migrating away from them soon, and testing them is fragile. There's only a few users, so it's not really relevant.

Okay, this is all happy, including docs deployment via https://github.com/scipy/devdocs. Closing.


Error immediately after installation

Prerequisites

[X] I am running the latest version
[x] I checked the documentation and found no answer
[X] I checked to make sure that this issue has not already been filed

Expected Behavior
Init an existing package manager.
Current Behavior
I'm trying to switch my Angular project from npm to pnpm, so I downloaded this.
I've installed it, with no errors, and as soon I run the first command it gives me this error:
`$ swpm init npm
🔒 npm init npm
node:events:491
throw er; // Unhandled 'error' event
^
Error: spawn npm ENOENT
at ChildProcess._handle.onexit (node:internal/child_process:283:19)
at onErrorNT (node:internal/child_process:476:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Emitted 'error' event on ChildProcess instance at:
at ChildProcess._handle.onexit (node:internal/child_process:289:12)
at onErrorNT (node:internal/child_process:476:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
errno: -4058,
code: 'ENOENT',
syscall: 'spawn npm',
path: 'npm',
spawnargs: [ 'init', 'npm' ]
}
Node.js v18.13.0
`
Or, if I try other commands like "swpm test" the error changes in:
`$ swpm test
🔒 npm test
node:events:491
throw er; // Unhandled 'error' event
^
Error: spawn npm ENOENT
at ChildProcess._handle.onexit (node:internal/child_process:283:19)
at onErrorNT (node:internal/child_process:476:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Emitted 'error' event on ChildProcess instance at:
at ChildProcess._handle.onexit (node:internal/child_process:289:12)
at onErrorNT (node:internal/child_process:476:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
errno: -4058,
code: 'ENOENT',
syscall: 'spawn npm',
path: 'npm',
spawnargs: [ 'test' ]
}
Node.js v18.13.0
`
Steps to Reproduce

I've installed it with command "npm install swpm --location=global" on an existing Angular project, and it gives me no error
I've tried to run some commands and everytime I got the error above.

Context

swpm Version: 1.0.1
node Version: 18.13.0
Package Manager: npm
Package Manager Version: 9.4.0
Operating System: Windows 11
Angular CLI project version: 14.2.10

Thanks a lot!

Could you please run the command: swpm --info and show the result here?

Could you please run the command: swpm --info and show the result here?

That's what I get when i run swpm --info:
$ swpm --info
using:  npm
origin: 🔒 lock

Versions:
swpm:   1.0.2
Node:   18.13.0
npm:    8.19.3

Are you running those commands inside the angular project path?

Yes, of course.

What's the result of running these commands node --version and npm --version?

$ node --version
v18.13.0

$ npm --version
8.19.3

What happens if you run the commands directly with npm?
npm init npm
npm test

Seems to be that is something related to the PATH:
https://stackoverflow.com/a/37366944/812915
I'll try to do some tests and I tell you when a new version is available for testing.

Try installing this version: npm install<EMAIL_ADDRESS>--location=global and test running the commands again.

Hi!
I've installed<EMAIL_ADDRESS>and now I got this:
$ swpm init npm
🔒 npm init npm

Usage: GITHUB_TOKEN=? NPM_TOKEN=? yarn create user/repo

And this:
$ swpm test
🔒 npm test

><EMAIL_ADDRESS>test
> ng test

✔ Browser application bundle generation complete.
...
...

Now it seems to work properly.
Thanks a lot, I appreciate what you did! ;)

Excellent news. I'll try to release this version as stable tonight.
Thanks for reporting it and for your help.

New version is available:
npm install swpm@latest --location=global


After correctly extracting the information, it is reported in the last step.

{
"expected_update_period_in_days": "2",
"url": "http://book.zongheng.com/book/342974.html",
"type": "html",
"mode": "on_change",
"extract": {
"url": {
"xpath": "//[@class='chap']/@href",
"value": "."
},
"title": {
"xpath": "//[@class='chap']/text()",
"value": "normalize-space(.)"
}
}
}

I am no expert when it comes to xpath, I think using CSS selectors gives you the response to expect:
{
  "expected_update_period_in_days": "2",
  "url": "http://book.zongheng.com/book/342974.html",
  "type": "html",
  "mode": "on_change",
  "extract": {
    "url": {
      "css": ".chap",
      "value": "@href"
    },
    "title": {
      "css": ".chap",
      "value": "normalize-space(.)"
    }
  }
}

It's hard to believe that this is true. I tried it and it worked successfully. Because xpath is easier for me than css, because there is a plugin for xpath helper. Thank you! This may be a bug.

It is my negligence, you are correct, thank you very much, I will pay attention next time.


feat: log SuperchainWETH events

#142  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @tremarkley and the rest of your teammates on  Graphite


Change the default position of the camera in RenderPanel.

Current behaviour: when adding a new camera display, the grid is displayed in the associated widget, but if you detach the widget or close and then reopen the displays panel, the grid is gone, because the position of the camera of the associated render panel is reset to the valueOgre::Vector3(999999, 999999, 999999).

New behaviour: with these changes the position of the camera is set to that value from the beginning, so that when the camera display is added, the grid is not displayed.

CI:

Linux
Linux-aarch64
macOS
Windows


[BUG] [timeseries] Deep learning models fail if item_id is of type string[python]

Bug Report Checklist

[x] I provided code that demonstrates a minimal reproducible example.
[x] I confirmed bug exists on the latest mainline of AutoGluon via source install.

Describe the bug
If the item_id column is of type string[python] (i.e., pd.StringDtype()), all deep learning models fail during training
Expected behavior
Models train normally.
To Reproduce
N = 100
df = pd.DataFrame(
    {
        "item_id": ["A"] * N,
        "timestamp": pd.date_range("2020-01-01", freq="D", periods=N),
        "target": range(N),
    },
).astype({"item_id": pd.StringDtype()})

tsdf = TimeSeriesDataFrame(df)
TimeSeriesPredictor(prediction_length=5).fit(tsdf, hyperparameters={"DeepAR": {"epochs": 2}})

Screenshots / Logs
...
Models that will be trained: ['DeepAR']
Training timeseries model DeepAR.

        Warning: Exception caused DeepAR to fail during training... Skipping this model.
        'IntegerArray' object has no attribute 'cumsum'

Installed Versions
Current master branch.

Current workaround for this problem: Convert item_id to str dtype before creating the TimeSeriesDataFrame:
df = pd.DataFrame(...)
tsdf = TimeSeriesDataFrame.from_data_frame(df.astype({"item_id": "str"}))

The problem is caused in
https://github.com/autogluon/autogluon/blob/65d8d6e6017d7e175459ea8ac0eae43375ecb489/timeseries/src/autogluon/timeseries/models/gluonts/abstract_gluonts.py#L72C3-L78C7
There are the min code to Reproduce
import pandas as pd
from autogluon.timeseries import TimeSeriesDataFrame

N=100
df = pd.DataFrame(
    {
        "item_id": ["A"] * N,
        "timestamp": pd.date_range("2020-01-01", freq="D", periods=N),
        "target": range(N),
    },
).astype({"item_id": pd.StringDtype()})
tsdf = TimeSeriesDataFrame(df)
ITEMID = "item_id"
item_id_index = tsdf.index.get_level_values(ITEMID)
indices_sizes = item_id_index.value_counts(sort=False)
cum_sizes = indices_sizes.values.cumsum()
print(cum_sizes)

I think we can add .astype(int) in item_id_index.value_counts(sort=False)
like this: item_id_index.value_counts(sort=False).astype(int)

Fixed in #4539. Thank you @rsj123!


Release v4.2.0

[x] I've updated the (WIP) tag to today's date in CHANGELOG.md
[x] I've added the release label to this PR

Changes

Added support for the TZ environment variable (setting timezones ex. "Europe/Stockholm") through the tzdata package. (#40)

Added config loading from YAML files using
github.com/iver-wharf/wharf-core/pkg/config together with new config models for configuring wharf-api. See config.go or the reference documentation on the Config type for information on how to configure wharf-api. (#38, #51)

Deprecated all environment variable configs. They are still supported, but may be removed in the next major release (v5.0.0). Please refer to the new config schema seen in config.go and config_example_test.go. (#38)

Added Makefile to simplify building and developing the project locally. (#41, #42)

Added wharf-core logging for Gin debug and errors logging. (#45)

Added wharf-core logging for GORM debug logging. (#45)

Changed version of github.com/iver-wharf/wharf-core from v1.0.0 to v1.1.0. (#45)

Added documentation to the remaining types in the project. No more linting errors! (#46, #54)

Added new endpoints /api/ping and /api/health. (#44)

Deprecated / and /health endpoints, soon to be moved to /api/ping and /api/health respectively, so they are aligned with the current Swagger documentation. (#44)

Changed logging and moved the httputils package to stay consistent with the provider API repos. (#47)

Changed version of github.com/swaggo/swag/cmd/swag from v1.7.0 to v1.7.1 in Dockerfile and Makefile. (#48)

Changed logging on "attempting to reach database" during initialization from "ERROR" to "WARN", and rephrased it a little. (#50)

Fixed so failed parsing of build status in the PUT /build/{buildid} and POST /build/{buildid}/log endpoints not silently ignore it and fallback to "Scheduling", but instead respond with appropriate problem responses. (#54)

Removed constraint that project groups cannot be changed in the PUT /project endpoint. This deprecates the problem /prob/api/project/cannot-change-group. (#55)

Actions after merge
Follow the step-by-step guide found here:
https://iver-wharf.github.io/#/development/releasing-a-new-version?id=merging-a-release-pr

Made a quick trivy scan and found some vulnerabilities:
$ trivy i -i v4.2.0-rc.1.tar
2021-09-09T08:49:56.783+0200	INFO	Detected OS: alpine
2021-09-09T08:49:56.783+0200	INFO	Detecting Alpine vulnerabilities...
2021-09-09T08:49:56.784+0200	INFO	Number of language-specific files: 1
2021-09-09T08:49:56.784+0200	INFO	Detecting gobinary vulnerabilities...

v4.2.0-rc.1.tar (alpine 3.14.0)
===============================
Total: 5 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 2, CRITICAL: 3)

+--------------+------------------+----------+-------------------+---------------+---------------------------------------+
|   LIBRARY    | VULNERABILITY ID | SEVERITY | INSTALLED VERSION | FIXED VERSION |                 TITLE                 |
+--------------+------------------+----------+-------------------+---------------+---------------------------------------+
| apk-tools    | CVE-2021-36159   | CRITICAL | 2.12.5-r1         | 2.12.6-r0     | libfetch before 2021-07-26, as        |
|              |                  |          |                   |               | used in apk-tools, xbps, and          |
|              |                  |          |                   |               | other products, mishandles...         |
|              |                  |          |                   |               | -->avd.aquasec.com/nvd/cve-2021-36159 |
+--------------+------------------+          +-------------------+---------------+---------------------------------------+
| libcrypto1.1 | CVE-2021-3711    |          | 1.1.1k-r0         | 1.1.1l-r0     | openssl: SM2 Decryption               |
|              |                  |          |                   |               | Buffer Overflow                       |
|              |                  |          |                   |               | -->avd.aquasec.com/nvd/cve-2021-3711  |
+              +------------------+----------+                   +               +---------------------------------------+
|              | CVE-2021-3712    | HIGH     |                   |               | openssl: Read buffer overruns         |
|              |                  |          |                   |               | processing ASN.1 strings              |
|              |                  |          |                   |               | -->avd.aquasec.com/nvd/cve-2021-3712  |
+--------------+------------------+----------+                   +               +---------------------------------------+
| libssl1.1    | CVE-2021-3711    | CRITICAL |                   |               | openssl: SM2 Decryption               |
|              |                  |          |                   |               | Buffer Overflow                       |
|              |                  |          |                   |               | -->avd.aquasec.com/nvd/cve-2021-3711  |
+              +------------------+----------+                   +               +---------------------------------------+
|              | CVE-2021-3712    | HIGH     |                   |               | openssl: Read buffer overruns         |
|              |                  |          |                   |               | processing ASN.1 strings              |
|              |                  |          |                   |               | -->avd.aquasec.com/nvd/cve-2021-3712  |
+--------------+------------------+----------+-------------------+---------------+---------------------------------------+

app/main (gobinary)
===================
Total: 0 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 0, CRITICAL: 0)

Will wait with this PR until a fix for that is merged.


flutter_meedu_videoplayer video control pannel

In the control panel shown in the flutter_meedu_videoplayer library, I want to add a playback progress bar, back, forward, volume control, and other icons on the control panel to adjust the position and add other functions, but it doesn't seem to be that part. Can I create my own control panel using flutter's stack widget without using your control panel?

check version 4.1.0
and this the demo for it
https://zezo357.github.io/flutter_meedu_videoplayer_example/#custom_controls
for code example check this
https://github.com/zezo357/flutter_meedu_videoplayer/blob/master/package/example/lib/pages/custom_controls.dart

if you need any help open a issue with it.
and if that fixes your problem let me know to close this issue.

also if you want me to implemnt the controls let know how they should look and i will do my best

Discord invite code. Can we talk to each other here?
https://discord.gg/nhpDWWh3


bold text in h2s needs style update

Bolded text in H2s is not appearing correctly: https://www.cockroachlabs.com/docs/stable/ui-custom-chart-debug-page.html

@luciaaaaaaa, @lnhsingh, is this a known or new issue?

Oh this is weird! I'm pretty sure this is a new issue, but semi-related to #9401


Casting Icon Disappeared

OS: Windows 10
Issue Descriptions: The player used to display the casting icon in order to cast music to either Chromecasts, Chromecast Audio, or Google Home. Now it does not, even though I'm connected to a network with multiple casting options. I have tried uninstalling and reinstalling the app as well. The first screenshot is from: https://play.google.com/music/listen?u=0#/wmp

And the second is from the app itself.

Steps to Reproduce: Open Google Play Music Desktop Player while connected to a network with multiple casting options.

I'm back on a network where testing Chromecast is exceedingly difficult.  Can someone else test this ( @jostrander )?

My Google Home and Chromecast are both listed on my Windows 10 box.
Have you allowed GPMDP through your firewall?

same here, no Cast icon.

firewall checked with this settings
Allow Chromecast Outbound	32768-61000	TCP, 8008-8009	TCP
Chromecast SSDP	1900	UDP
Chromecast Inbound	32768-61000	UDP
also GPMDP is allowed to do whatever it wishes to do (in firewall)

hapilly casting from Chrome

need to check anything else?

@BeheSQ Assuming you are on Windows can you install Bonjour 👍

@MarshallOfSound yes! although I was a bit reluctant to install anything Applish into my Windows, installing Bonjour and restart helped. thanks a lot.
PS: for those looking for Bonjour installation, it is included in Bonjour Printer Services (convenient, isn'it?) on this link: https://support.apple.com/kb/DL999?viewlocale=en_US&locale=en_US
BEWARE! during installation double check, that you have the autoupdate option unchecked. Apple auto update is a slippery slope into hell. BEWARE!

@sanjay228 Do you have Bonjour installed? Can you test after installing Bonjour? I'm going to close this for now, but if that doesn't work please reply and we'll try to figure it out.

I'm running into the same issue. Chromecast works fine on version 4.0.4 of GPMDP but not on 4.2.0 of GPMDP. I have bonjour installed and nothing blocking it in my firewall settings. I am running Windows 10 on both computers.

I am having this same issue even after re-installing Bonjour - Windows 8.1 - any suggestions?

Check for firewalls. You need to allow in port 5353 UDP to GPMDP in order for the app to see casts on the network.

Everything is allowed for GPDMP and Bonjour. Can someone please post a screenshot of all the rules needed for Chromecast support to work?

Does turning the firewall off temporarily fix the problem?


Add archive for python-clang_5.0 [dunfell]

For the buld of the proprietary DDK we still need python-clang_5.0. Unfortunately required archive is not accessible anymore because author dropped support.
So we took archive from yocto's caches and put it directly into recipes' files.

Updated according to comment in #55.

RB is added.
Additional explanation is provided in the recipe, to address the comment.
Tested.
Ready to be merged.


[readme] Add FOSSRIT/infrastructure, alphabetically sort related project list

@patcon mentioned adding this to the README in #642. I added a link and short explanation to the Related projects section.

Thanks!


Failed to resolve:com.commonsware.cwac:camera:0.7+

Failed to resolve:com.commonsware.cwac:camera:0.7+ in AS 2.2 with gradle version 2.14.1. Any ideas?

In your project level build.gradle file change this:
maven {             url "https://repo.commonsware.com.s3.amazonaws.com"         }
to this:
maven {             url "https://s3.amazonaws.com/repo.commonsware.com"         }


Add a different calling-convention for Mac Aarch64

MacOS Aarch64 uses the same ARM64 calling convention with tweaks: https://developer.apple.com/documentation/xcode/writing_arm64_code_for_apple_platforms
Returning a different default CallingConvention for this triple would be a nice way to signal users that they might require handling it particularly.

Makes sense! I've now submitted #70 to implement this.


Add unit tests for KeyStoreManager

$subject
Related Issue https://github.com/wso2/product-is/issues/21359

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/11560162946

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/11560162946
Status: success


[Feature] Support for definitions

Problem I am trying to solve:
Given Java Objects:
@JsonSubTypes({
    @JsonSubTypes.Type(value = A.class),
    @JsonSubTypes.Type(value = B.class)
})
public interface I {}

public class A implements I {
    public int varA;
}
public class B implements I {
    public int varB;
}
public class C {
    public I varC;
}

I desire a json schema as follows:
{
  "definitions": {
    "urn:jsonschema:com:mycompany:GenerateSchemas:A": {
        "type" : "object",
        "id" : "urn:jsonschema:com:mycompany:GenerateSchemas:A",
        "properties" : {
          "varA" : {
            "type" : "integer"
          }
        }
      },
    "urn:jsonschema:com:mycompany:GenerateSchemas:B": {
        "type" : "object",
        "id" : "urn:jsonschema:com:mycompany:GenerateSchemas:B",
        "properties" : {
          "varB" : {
            "type" : "integer"
          }
        }
      }
  },
  "type" : "object",
  "id" : "urn:jsonschema:com:mycompany:GenerateSchemas:C",
  "properties" : {
    "varC" : {
      "type" : "object",
      "oneOf": [
        { "$ref": "urn:jsonschema:com:mycompany:GenerateSchemas:A" },
        { "$ref": "urn:jsonschema:com:mycompany:GenerateSchemas:B" }
      ]
    }
  }
}

Using version 2.9.8 of the library, the schema that is generated is:
{
  "type" : "object",
  "id" : "urn:jsonschema:com:mycompany:GenerateSchemas:C",
  "properties" : {
    "varC" : {
      "type" : "any"
    }
  }
}

It would be nice if it was possible to natively support this given that  @JsonSubType annotations are present.
Please see related to StackOverflow Question: https://stackoverflow.com/questions/56174997/json-schema-generator-with-inheritance-and-references
My workaround: https://gist.github.com/rrmistry/2246c959d1c9cc45894ecf55305c61fd
(Could be improved if approved)
Thank you,

Any update?

If there is an update, someone will actually write a note here.


How to use only syntax color/highlighting?

The syntax highlighting of this extension is really great and I want use this with other themes. So, I tried copying the content of new_dark.json from semanticHighlighting: true to the end of the file into editor.tokenColorCustomizations{} basically skipping colors but it didn't work. Any help regarding this is much appreciated.

You can refer to this link.
semanticTokenColors is https://code.visualstudio.com/docs/getstarted/themes#_editor-semantic-highlighting
tokenColors is https://code.visualstudio.com/docs/getstarted/themes#_editor-syntax-highlighting
Maybe, like this?


[bug/help] examples not working whatsoever

I'm trying the examples but I can't really get anything to work right now.
It seems axum::Server has been replaced with axum::serve (using a TcpListener). I think I got this one figured out.
The next one is serve_dioxus_application which basically does not seem to exist (anymore?).
In particular, I'm following this guide: https://dioxuslabs.com/docs/nightly/guide/en/fullstack/getting_started.html
Help appreciated.

That guide is for an older version of Dioxus (0.3). Here is the guide for 0.4: https://dioxuslabs.com/learn/0.4/getting_started

Thank you. I got confused because the URL said nightly.


fix a misspell

fixes #

Checklist:

[x] Add tests that demonstrate the correct behavior of the change. Tests should fail without the change.
[x] Add or update relevant docs, in the docs folder and in code.
[x] Add an entry in CHANGES.rst summarizing the change and linking to the issue.
[x] Add .. versionchanged:: entries in any relevant code docs.
[x] Run pre-commit hooks and fix any issues.
[x] Run pytest and tox, no tests failed.

Thanks, but this was already fixed in #4757 on the 2.2.x branch (this commit will be merged to the main branch later).


setValue giving Error: options.uri is a required argument

I don't if if I did anything wrong but I can't set a value
cell.setValue("test", function(err) {
      console.log(err);
});

I'm getting options.uri is a required argument
let me know if there is another way to save things. I tried save() but did't work

Just released a big update! Please upgrade to the latest version and let me know if you are still having problems. Thanks :)

still a problem @ 2.0.1 and @ 1.4.1

`
async function promisedUpdateSheet (sheetId, values, workSheetId = 1) {
let workSheet = await promisedWorkSheet(sheetId, workSheetId);

let cells = await promisedCells(workSheet);

values.forEach(function (value){
    cells.forEach( function (cell, index) {
        if (value.col === cell.col && value.row === cell.row) {
            cell.value=value.value;
            cell.save(function(err){
                if (err) {
                console.log(err); }
            });
            console.log('matched' + cells[index].value);
            return;
        }
    });

});

}
`
returns:
[Error: options.uri is a required argument]
Still a problem with recent version.

I had a thought: I'm using Meteor.Js, which uses an old version of node. Maybe this is the problem? The strange thing is that it stopped working a few months ago, before it was fine.

Hi guys! It does not seem to be an issue related to the Node version since I just confirmed that it do happens to me using v0.10.46, v0.12.16, v4.6.0 and v6.7.0 :)
In my case, I am getting this options.uri missing error when executing a SpreadsheetWorksheet.clear() which internally uses the SpreadsheetCell.setValue() as far as I saw: https://github.com/theoephraim/node-google-spreadsheet/blob/master/index.js#L397
Any help on this is more than appreciated! ;)
Thanks!

As mentioned by @josmcg in this issue, it is related to the use of the request package: https://github.com/request/request/issues/1509

@gtorodelvalle  I solved this by writing my own library, using promises and the API v4. It radically solves the problem by delegating the request to the new API library. If you want I can send you the code.

@servermeta , any plans tu publish it as an NPM package? :)

@servermeta yes do you plan to share? :)

I've just a published a new version of this module which is a complete rewrite using Google's V4 Sheets API (v3 is being deprecated on March 3, 2020).
Docs available here - https://theoephraim.github.io/node-google-spreadsheet
I do believe this issue should be fixed in the new version.
Please test it out and if you find that there is still a problem, reopen the issue.
Thanks! 😄


GPUPicker: Fix class doc

Snapshot stored with reference name:
refs/pull/15840/merge
Test environment:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15840/merge/index.html
To test a playground add it to the URL, for example:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15840/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/15840/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/15840/merge
https://gui.babylonjs.com/?snapshot=refs/pull/15840/merge
https://nme.babylonjs.com/?snapshot=refs/pull/15840/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/15840/merge#BCU1XR#0

Visualization tests for WebGPU (Experimental)
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15840/merge/testResults/webgpuplaywright/index.html

WebGL2 visualization test reporter:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15840/merge/testResults/webgl2playwright/index.html


First steps towards analyzing duplicated reimbursiments and DeepLearning Keras

Converting PDF files to png and then applying sift descriptors
DeepLearning Keras to detect generalization in reimbursements

Hi @silviodc, thank you very much for the contribution! 🎉
Thanks for you patience!
Me, @jtemporal and @cabral took a closer look into it and found the best way to understand what you have done! Discussing in the public group helped us to find a way to do that! :)
So you are looking for some answers, so here it is:
The document is the following one

It is clear to me that the description of the items was made by someone else than the restaurant, is it allowed ???

No it is not allowed, should be described on the receipt

Are the deputies or acessors changing a document?? What are the implications about it?

No, it is not allowed that the receipt is altered (as the law says). It looks very suspicious. It is important to notice that the receipt was not changed but extra information was added by hand outside of the receipt while scanning it, and the CEAP clearly states that also can't happen. We have added an image that highlights part of the law bellow that proves that.

Taking a closer look at the place, that is the value of at least (two people meal)[http://imgur.com/fzcv15T]
Can we bring the discussion here?

Hey @silviodc,
I have some questions on the effectiveness of your model! First things first, thanks for sending a PR to serenata that includes CNNs and DNNs to this project, it's a great way to contribute to Brazilian politics! Keep doing it man!
Let me ask you some questions (then it will help you to see if your work is really doing what it is meant to be or not):

Have you tried to create a cross validation set to test out the dataset?
Is the 70% accuracy rate suffering any kind of overfitting/underfitting?
What would happen if a new kind of receipt is inputed (a new place, new items or other data like CNPJ has changed)? Would it still be effective?

Hi everyone,
So, regarding the suspicious recipe, let's bring the discussion here :+1:
1- How this scanning of documents is done?
a - by the Deputy Assessor?
b - Someone in the chamber of deputies in charge of it?
2- Since it is not allowed, who assumes the responsibility of this mistake ??
a- The deputies?
b- The employees?
c- Both?
Going to the method:

Have you tried to create a cross validation set to test out the dataset?

I didn't try, but it is my plan to the future.  I will use the 2483 suspicious reimbursements i got in my run to build a proper training set and out dataset.

Is the 70% accuracy rate suffering any kind of overfitting/underfitting?
What would happen if a new kind of receipt is inputed (a new place, new items or other data like CNPJ has changed)? Would it still be effective?

So, verifying the first results and the 2483 files, it is suffering of overfitting. I thought that generating many images with ImageDataGenerator could increase the performance of the model, but it seems not the case.
The main point is: I used few data (500 reimbursements; 250 per class), i was really lazy to build the corpus haha.
In the example i followed, they are using (2000 images, 1000 per class) and in my opinion it has a huge impact.
Well, to change the cnpj, data or place don’t lead to get false positives. However, the change of items (description and number) has a huge impact.
So, I already classified 1400 reimbursements of 2483 by hand. Maybe until august I will have the training dataset prepared. I guess with this dataset we can have a better view whether it’s a good approach to include.
In my opinion is too soon to use it directly. However, I think that including the reimbursements showed on twitter and Facebook and validated by the citizens, could be an approach in the future. Only with this 2483 files I’ve noticed some interesting cases.
PS: thank you guys so much for this project! I'm very proud of you :+1:  and happy for participate

Hi @silviodc, so according the law, we have that:

1- How this scanning of documents is done?
a - by the Deputy Assessor?
b - Someone in the chamber of deputies in charge of it?

According to the law, the congressperson have to give the original document, and the chamber will scan it. By knowing that, they cannot bring an scanned document to the Chamber.
The law is below:
" Art 3 - § 2º Será objeto de ressarcimento a despesa comprovada por documento original, em primeira via, quitado e em nome do Deputado, ressalvado o disposto nos §§ 4º a 6ºdeste artigo e admitindo-se, na hipótese de conta telefônica, apenas a apresentação da folha de rosto, acompanhada do pertinente comprovante de quitação. (Parágrafo com redação dada pelo Ato da Mesa nº 66, de 8/1/2013) "
source

2- Since it is not allowed, who assumes the responsibility of this mistake ??
a- The deputies?
b- The employees?
c- Both?

The responsibility lies on the deputy, according this piece of the law:
" Art. 4º A solicitação de reembolso será efetuada mediante requerimento padrão, assinado pelo parlamentar, que, nesse ato, declarará assumir inteira responsabilidade pela liquidação da despesa, atestando que:
I - o material foi recebido ou o serviço, prestado;
II - o objeto do gasto obedece aos limites estabelecidos na legislação;
III - a documentação apresentada é autêntica e legítima."
source

So, I already classified 1400 reimbursements of 2483 by hand. Maybe until august I will have the training dataset prepared. I guess with this dataset we can have a better view whether it’s a good approach to include.

So you are thinking about classifying all those reimbursements to create a training dataset, and plan to use it as approach to include? Is there something that we can do to help, besides testing and giving opinion about it?

Hi @anaschwendler
Continuing the discussion.
Since the responsibility lies only in the deputy, what we do when they push it to others?
Take a look:

A Câmara possui um setor que analisa e aprova as prestações de contas de cada parlamentar, portanto, se este valor (que consumi e paguei) estivesse ferindo alguma norma da Casa este setor responsável teria apontado o problema e, certamente, não aprovaria minha despesa, devolvendo a nota sem ressarcimento.

Nota deputado Marcon sobre refeição de 130 reais
Did you find a answer to it?

Nosso próximo passo é descobrir a qual instância recorrer quando os próprios deputados negam os números, os dados públicos e a matemática.

Cuducos post
PS: For how long we have to play the game: "I'm not guilty..." ?
So, for the method....

You can help validating the reimbursements i didn't check.
Publishing it on web to be validate by others...

need validation
Best,
Silvio

Did you find an answer to it?

We’ve found a answer and we wrote a article in Portuguese about that.
Creating news around it and developing social pressure will have good results and education. We’re aligning with lawyers the next steps.

PS: For how long we have to play the game: "I'm not guilty..." ?

We are not playing, they’re :)

So, for the method....

We had an amazing experience with crowdsourcing before, and we've got plans to do the same here. Soon we’ll release a spreadsheet and drop a line through FB and Twitter.
Thank you very much! :tada:

hi @silviodc and everyone! Just an update here: We are releasing today the file for the crowdsourcing ;)
Pretty soon we'll have the files identified for testing the method 🎉

Hi @jtemporal
Great news!! I guess already in this week we can test this method again :D

Why not run the model on all ~160k meals receipts and make the spreadsheet available and ordered by the probability generated by the model? It will make the process faster. And after that, a better model can be built.

Hi everyone!
Finally i executed the code over the new Dataset! Take a look in the results they are amazing :D

Hi @thiagoalencar
Thanks so much for follow this PR too.
So, regarding the overfitting, i guess you missed that the 91% was in an external dataset. It was also suggested by @vmesel to verify whether we could use it on other recipes.
During the construction, we archived 86% in training and 94% in evaluation.
acc: 0.8691 - val_loss: 0.2265 - val_acc: 0.9423
Therefore, the built model can also be generalized to other data.
I suggest you to take a look in the definition of overfitting in this paper vldb ML

For instance, overfitting occurs when the model fits the training data well but does not generalize to unseen or test data.

I think that now the model is pretty good to be used. We have 91% in an external test data.
Regarding the probability value, mentioned here:

Why not run the model on all ~160k meals receipts and make the spreadsheet available and ordered by the probability generated by the model?

Well, this is the probability value regarding the model. It doesn't confirm any think about the reimbursement. In the end we will have a lot of reimbursements which must be validate by hand.
It will lead us some points:

Validate reimbursements by hand is a laborious task, and we want to avoid it! It is the main reason why we built the ML model.
Since the first model wasn't good enough, we will have tons of data with strange probability.

Thanks so much for your comments and interest.

thanks for the response. but I think that a small test data does not capture all variability of the dataset. and applying in all dataset will not generate too many cases. With this accuracy, only a feel cases will remain in doubt. There will never be a model that prevents manual classification. So, the questionable classification can be iteratively corrected, like google us in they captcha system. Can you post the confusion matrix,sensitivity and specificityof the model?


[release-2.3] trigger a new build

Signed-off-by: liuwei<EMAIL_ADDRESS>

refert to https://github.com/open-cluster-management/backlog/issues/15256

/lgtm


QS links update

Description of your changes
Update links for quickstart. Quickstarts have been combined into a single page.

Fixes #
I have:

[ ] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

Thank you for this PR @tr0njavolta,
Please ignore the publish-artifacts job, the issue is a known one with the recent SSO changes.
It seems that CLA is not signed yet, could you please sign it?

Superseded by https://github.com/crossplane-contrib/provider-upjet-gcp/pull/532


windows ?

Based on Windows？

I run the code on a linux machine but it shouldn't be too hard to change paths to make it os agnostic. If you are running into an issue here let me know!