[Run][Plugin Manager] Move plugin specific settings under the plugin settings

Link to parent issue #5273
It should be possible for plugins to have different settings.
Now we only have one option Disable drive detection warning for the file search plugin

Here are three examples when we have an indirect reference from PowerLauncher project to plugin projects. We should get rid of them.
https://github.com/microsoft/PowerToys/blob/419a143bf25a94137cd0dc39edece7142f230f8a/src/modules/launcher/PowerLauncher/SettingsWatcher.cs#L121-L127
https://github.com/microsoft/PowerToys/blob/419a143bf25a94137cd0dc39edece7142f230f8a/src/modules/launcher/PowerLauncher/SettingsWatcher.cs#L104-L109
https://github.com/microsoft/PowerToys/blob/419a143bf25a94137cd0dc39edece7142f230f8a/src/modules/launcher/PowerLauncher/ViewModel/MainViewModel.cs#L896-L899

@enricogior
We have two options here:

The responsibility of rendering plugin settings is taken by the settings app. That means that we would add information about checkboxes, textboxes, etc. to PowerLauncherPluginSettings. So far we only need to add an array of checkboxes. It is easy to implement but it is not very flexible. It is something between small and medium cost.
The responsibility of rendering plugin settings is taken by the plugin project. More precisely settings xaml file is stored in the plugin project and is loaded dynamically in the settings app. It is definitely a big work item.

@mykhailopylyp
let's go with option 1.

Should we creaze a spec here how json should be formated and what elements are sllowed.
Example:
<group name=Result settings />
<checkbox name="test" default="on" settingsJsonString="ShowExampleResult" />
<radioGroup name="Show redults of type">
<radio order=1 name=all description="test" default="on" settingsJsonString="ShowAllRedults" />
<radio order=2 name="games only" description="test" default="on" settingsJsonString="ShowGameResult" />
</radioGroup>
</group>

Should we create a spec here how json should be formated and what elements are allowed.

@htcfreek
Do you mean spec for the plugin.json file? If yes, it would make a lot of sense when we allow third-party plugins.

Should we create a spec here how json should be formated and what elements are allowed.

@htcfreek
Do you mean spec for the plugin.json file? If yes, it would make a lot of sense when we allow third-party plugins.

As you see in my example I used xml for demonstration. May xml is here a better choice.

@htcfreek
I think I am not following.

What I mean is we should strict define what elements are allowed (edit, text, button, ...) and what attributes (name, description, settingValue, ...) can be defined.

You mean to define it for additional plugin settings, right? We agreed above that we go with an array of checkboxes for now.

I think we should introduce an independent config file for settings and shouldn't integrate them into the general plugin metadata json. (This is more flexible.)

If you think about it we have not introduced any new settings to plugin.json. Maybe we can create an issue to reduce the number of settings in the metadata.

@htcfreek
I think I am not following.

What I mean is we should strict define what elements are allowed (edit, text, button, ...) and what attributes (name, description, settingValue, ...) can be defined.

You mean to define it for additional plugin settings, right? We agreed above that we go with an array of checkboxes for now.

Yes, thats what I meant.
Okay. This is not much flexible. But let's go with that in the first step. Imo there will come plugins for that a checkbox isn't the best for all settings. (Example: Websearch plugin with selection of search provider.)

I think we should introduce an independent config file for settings and shouldn't integrate them into the general plugin metadata json. (This is more flexible.)

If you think about it we have not introduced any new settings to plugin.json. Maybe we can create an issue to reduce the number of settings in the metadata.

I think we should splitt between plugin metadata definition and complex settings definition. But in the first step we con go with one file.

@mykhailopylyp , @niels9001 , @enricogior
At the moment we have the plugin settings group between "Search & results" and "Appearance". I think we should move it at the end after "Appearance" because "Plugins" is the biggest settings group.
What's your thoughts on this?

@enricogior
The new issue for the remaining enhancement idea in this issue is created.

Great news!  This was resolved in the newly released 0.33 version of PowerToys!  Head to https://aka.ms/installpowertoys to grab latest.


fix: remove popstate listener in popover

avoid auto-dismissal issue in some browser

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/44082
PROPOSAL: https://github.com/Expensify/App/issues/44082#issuecomment-2227286620
Tests

Create two manual money request
Go to the first expense > Select Hold from 3-Dot menu
Add reason to hold and tap Hold button

Verify that: Modal with Got it button should appear and user should tap Got it to dismiss the modal

[ ] Verify that no errors appear in the JS console

Offline tests

QA Steps

Create two manual money request
Go to the first expense > Select Hold from 3-Dot menu
Add reason to hold and tap Hold button

Verify that: Modal with Got it button should appear and user should tap Got it to dismiss the modal

[ ] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/user-attachments/assets/9bc63f2b-e57e-4393-a1ef-db14cbf586d0

Android: mWeb Chrome

https://github.com/user-attachments/assets/2931a3ec-6881-48b7-be66-10dd7c7459c7

iOS: Native

https://github.com/user-attachments/assets/48ed39c4-0552-4b5a-8b2f-cd0922fd901a

iOS: mWeb Safari

https://github.com/user-attachments/assets/48ed39c4-0552-4b5a-8b2f-cd0922fd901a

MacOS: Chrome / Safari

https://github.com/user-attachments/assets/e5e37839-07c8-434f-b2bb-776a550ad402

MacOS: Desktop
https://github.com/user-attachments/assets/e5e37839-07c8-434f-b2bb-776a550ad402

I'm not sure what you mean 🤔 I'm saying you should record video/screenshots correctly for each platform

Sorry for this confusion but if you record screenshots/videos for a native platform, you should run it on their simulator/emulator, I see you're using web inspector instead.

You're using mSafari for both mSafari and IOS, and android native for both mChrome and Android right? 🤔
Please correct me if I'm wrong.

Thanks for understanding.

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

https://github.com/user-attachments/assets/9ab136e6-d6c0-4784-a9b9-e2f4276e9fed

Android: mWeb Chrome

https://github.com/user-attachments/assets/6f148f39-5c13-4fde-ab27-8b3358e8ddbb

iOS: Native

// running issue

iOS: mWeb Safari

https://github.com/user-attachments/assets/5c2b067f-5b55-4a48-a37f-6c93ddf19de1

MacOS: Chrome / Safari

https://github.com/user-attachments/assets/10707b56-772b-4131-bb20-146b826f77c3

MacOS: Desktop

https://github.com/user-attachments/assets/255ab964-030a-45b6-ae78-5413927cba5f

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Cherry-picked to staging by https://github.com/roryabraham in version: 9.0.14-1 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by https://github.com/roryabraham in version: 9.0.14-6 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


[DO NOT MERGE] Testing Pipeline for ACS Communication

There have been some concern about ACS Communication .NET pipeline causing error due to CallingServer code - investigating.

API change check
API changes are not detected in this pull request.


(Electron) Iohook events (mousemove/mousedown, etc) are not working on Chrome latest version (93.0.4577.82)

Expected Behavior
The mousemove and mousedown and keydown events should be captured using iohook on Chrome (93.0.4577.82).
Current Behavior
The mousemove and mousedown and keydown events CANNOT be captured using iohook on Chrome (93.0.4577.82).
This Chrome IS NOT the electron chome, just the Chrome application on the desktop. the log not showing anything. Outside Chome window area, iohook works again and log start to show event. Move mouse back to Chrome window the log disappears again just look like the events on the Chrome tab/window cannot be captured by iohook.
Possible Solution
Do not know what's the cause.
Steps to Reproduce (for bugs)

This code snippet running in a Election application

start electron application
start iohook with above code (triggered by button click)
minimize the application window.
click on desktop or other application, the event logs are shown.
Start a Chrome on desktop
click or mouse move in Chrome window, no event logs are shown.
minimize the Chrome window
click on anywhere else, the event logs are shownd again.

Your Environment

IOHook Version: 0.9.3
Environment name and version :  Chrome (93.0.4577.82), Nodejs 14, Election 12.0.12
Operating System and version   :  Windows 10 Home x64bit,
GPU                                            :  NVIDIA GeForce 640MX, Driver version: 471.75

Sounds like security restrictions, try running your packaged electron app (or dev electron) as administrator and see if the events are captured that way.

@marcelblum  Hey man, you are so smart! After I run as administrator the problem disappears, however I just wondering that the Chrome also opened by the same user as my application, why the event cannot be captured in Chrome window? If you facing same issue before could you please tell me the cause of this and is it a configure issue regarding Chrome or Windows 10? how I could fix this by changing some configuration?

@marcelblum  thank you so much for your detailed feedback, you are absolutely a star to me. Based on your comment I did fund that the Chrome run as elevated everytime I start double click on chrome.exe without any UAC alart, however if I run chrome in cmd it becomes "un-elevated", I never intented to startup chrome on elevated mode and I cannot think of anything I did make chrome behave this way, so still not sure why this is happening, however I do know that this issue has nothing to do with iohook now. Thank you again for your detail explaination and patient.
I'm still researching why and nothing seems like to be the answer or solution, if you know reset the chrome back to normal please let me know, thanks in advanced.

That's really odd, I can only guess that Chrome was installed in some particular way that is making that happen, so maybe just try uninstalling/reinstalling. Keep in mind even a shortcut can have "run as administrator" checked. So even if the actual exe doesn't have that set in the properties, but you start it from a shortcut that does, it will run elevated. Good luck.


Use absolute paths for all file names to hipify.

This fixes issues where some files with names in relative paths were not handled correctly.

@wenchenvincent ,
The changes looks fine. But I havent come across this error. Can you please explain what was the issue happening due to relative paths for my understanding. Also I am not if any side effects of this change.

I had two issues, which were addressed by the two additions in the PR:
I had some relative paths in the header_include_dirs. So the all_files list would include the relative paths of these header files. But when hipify_torch was processing the include lines in a file, it would look up using the absolute file path. So those include will not be replaced with their hipified header files. I had to use the absolute path to work around this, but I felt it would be more robust to have hipify_torch do it.
I had some relative paths in the cuda_source_list. When replace_cuda_with_hip_files.py looks for the hipified list, hipified_result dict uses absolute paths as keys. So we would also need to supply the cuda_source_list with absolute paths.

Requested @wenchenvincent to provide reproductions details offline for further debug. At first glance, it seems that the change in  hipify_python.py should not be required, but the change in replace_cuda_with_hip_files.py looks correct.


208 basic composability

/test all

@mike-winberry Given the decision to move the Software Factory package to its own repo, I believe this should get the same treatment. I propose we make a repo https://github.com/defenseunicorns/zarf-package-flux and add this code to that repo.
Thoughts?
/cc @jeff-mccoy @YrrepNoj

I think it's find to move it to it's own repo once this PR is merged--but I do have a concern with a whole bunch of packages sitting at the top-level of the Defense Unicorn group.  Maybe we need to discuss a new org something for all these repos?

If we're just gonna move it I'm not sure why we would merge this PR, just to pull it back out.
Do we want to wait on a decision here until we are able to make a decision on what org these go in?

That works for me. I’m gonna play with a repo tomorrow and see if we can push to GitHub packages with a sha using GitHub ci to make it easy to pull with validation. I’ll also push what I have to a new repo on DU as it really doesn’t need to be in zarf.

@mike-winberry and I are going to sync tomorrow on this PR so I can take review responsibility for that.

Closing to move to new repo. https://github.com/defenseunicorns/zarf-package-flux


chore(requirements): Django REST Framework 3.4.3

http://www.django-rest-framework.org/topics/release-notes/#342
http://www.django-rest-framework.org/topics/release-notes/#343

Current coverage is 81.75% (diff: 100%)

Merging #954 into master will not change coverage

@@             master       #954   diff @@
==========================================
  Files            28         28
  Lines          3053       3053
  Methods           0          0
  Messages          0          0
  Branches        509        509
==========================================
  Hits           2496       2496
  Misses          407        407
  Partials        150        150

Powered by Codecov. Last update 61ec98c...e0a3f02


Conditional subscriptions don't work in 0.19.1

When having conditional subscriptions, like in a SPA with routes where different routes might have different subscriptions, they don't work anymore in 0.19.1.
SSCCE
module Main exposing (main)

import Browser exposing (Document)
import Browser.Navigation as Navigation
import Html exposing (Html, a, div, li, text, ul)
import Html.Attributes exposing (href)
import Time
import Url
import Url.Parser as Parser exposing (Parser, s)

-- MODEL

type alias Model =
    { navigation : Navigation
    , counter : Int
    }

type alias Navigation =
    { key : Navigation.Key
    , page : Page
    }

initialModel : Url.Url -> Navigation.Key -> Model
initialModel url key =
    { navigation =
        { key = key
        , page =
            case fromUrl url of
                Nothing ->
                    NotFound

                Just a ->
                    a
        }
    , counter = 0
    }

parser : Parser (Page -> b) b
parser =
    Parser.oneOf
        [ Parser.map Home Parser.top
        , Parser.map About (s "about")
        ]

fromUrl : Url.Url -> Maybe Page
fromUrl url =
    -- Treat fragment as path for convenience
    { url | path = Maybe.withDefault "" url.fragment, fragment = Nothing }
        |> Parser.parse parser

type Page
    = Home
    | About
    | NotFound

type alias Flags =
    ()

init : Flags -> Url.Url -> Navigation.Key -> ( Model, Cmd Msg )
init flags url key =
    ( initialModel url key, Cmd.none )

-- UPDATE

type Msg
    = UrlRequested Browser.UrlRequest
    | UrlChange Url.Url
    | Tick Time.Posix

update : Msg -> Model -> ( Model, Cmd Msg )
update msg model =
    case Debug.log "" msg of
        UrlRequested urlRequest ->
            case urlRequest of
                Browser.Internal url ->
                    ( model, Navigation.pushUrl model.navigation.key (Url.toString url) )

                Browser.External href ->
                    ( model, Navigation.load href )

        UrlChange url ->
            let
                navigation =
                    model.navigation
            in
            ( { model
                | navigation =
                    { navigation
                        | page =
                            case fromUrl url of
                                Nothing ->
                                    NotFound

                                Just a ->
                                    a
                    }
              }
            , Cmd.none
            )

        Tick _ ->
            ( { model | counter = model.counter + 1 }, Cmd.none )

-- VIEW

view : Model -> Document Msg
view model =
    { title = "hello title"
    , body = [ bodyView model ]
    }

bodyView : Model -> Html Msg
bodyView model =
    div []
        [ text "hello world"
        , ul []
            [ li [] [ a [ href "#/" ] [ text "Home" ] ]
            , li [] [ a [ href "#/about" ] [ text "About" ] ]
            ]
        , div []
            [ case model.navigation.page of
                NotFound ->
                    text "Page not Found"

                Home ->
                    Html.div
                        []
                        [ text "Home page"
                        , Html.div
                            []
                            [ text <| String.fromInt model.counter ]
                        ]

                About ->
                    text "About page"
            ]
        ]

-- SUBSCRIPTIONS

subscriptions : Model -> Sub Msg
subscriptions model =
    case model.navigation.page of
        Home ->
            Time.every 1000 Tick

        _ ->
            Sub.none

-- MAIN

main : Program Flags Model Msg
main =
    Browser.application
        { init = init
        , update = update
        , view = view
        , subscriptions = subscriptions
        , onUrlRequest = UrlRequested
        , onUrlChange = UrlChange
        }

Expected
When visiting http://localhost:8000/src/Main.elm#/ for the first time, the counter should start increasing every second. Visiting the http://localhost:8000/src/Main.elm#/about should hide the counter. Going back to http://localhost:8000/src/Main.elm#/ should display de counter again and start increasing it again every second.
Actual
Visiting http://localhost:8000/src/Main.elm#/ starts the counter. Visiting http://localhost:8000/src/Main.elm#/about hides the counter. Going back to http://localhost:8000/src/Main.elm#/ shows the counter but it does not increase any more, unless you click on the home link twice.

Elm: 0.19.1
Browser: Chrome, Safari
Operating System: macOS, iOS

Possible issue
Some people have reported this problem and done some investigation about the possible root of the issue. Here you cand find what they have discovered https://elmlang.slack.com/archives/C13L7S5GR/p1572031426192200
This might also be related to https://github.com/elm/compiler/issues/1776

The bug here is in how "synchronous commands" are handled internally. It should be fixed by this commit: https://github.com/elm/core/commit/704dcc08d4617d45c8b0fce7a68729335c880756
Trying out the commit locally with the changes, I am seeing the behavior you expect. So the fixed version should come out in a patch release (1.0.3) along with some other fixes. Thank you for the SSCCE, it really help test fixes that touch on really tricky code (task scheduling!)

Awesome! Thank you @evancz for putting effort into this :)

I believe issues like this one: https://github.com/elm/browser/issues/62 also caused by the same flaw. If so, many related cases can be closed!
Thanks you for the effort 👍

I've just tried out the elm/core 1.0.3 and everything related to conditional subscriptions is finally working fine 😍


Multiline Text is not supported with drawText

As per code with multiline text it only changes X values everytime but the Y value remains same which create overflow.
but does not support linebreak like API.Text()

is it support urdu font.

I had the same issue - I've adjusted the following:
In pageOut(...) adjust the return-value:
// x, y, width, height + padding of 1.8
return [x, y, tmpsum, (fontSize + 1.8) * lineHeightProportion];

and in drawText adjust the calls(3) of pageOut(...):
axisCache = pageOut(text[i], fontSize, key, Color, charSpace, 0/* was 'sum' */, x, y);
// sum = axisCache[0]; // not needed for vertical linebreaks
y = axisCache[1] + axisCache[3]; // update 'y' to the last 'y' + the returned lineHeight

I just edited it. Can you check it?


Submitting the TextField leaves a blank area on Safari

Steps to reproduce:

Focus the TextField
Start typing
Submit the TextField

Visual represntation for the issue:
https://user-images.githubusercontent.com/12971971/146666905-e62c1686-25cc-49ca-93db-8c5d7df00755.mp4
Minimal reproducible sample:
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      home: FirstPage(),
    );
  }
}

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

  @override
  State<FirstPage> createState() => _FirstPageState();
}

class _FirstPageState extends State<FirstPage> {
  late TextEditingController _controller;
  @override
  void initState() {
    _controller = TextEditingController();
    super.initState();
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Column(
        children: [
          TextField(
            controller: _controller,
            onSubmitted: (_) {
              FocusScope.of(context).unfocus();
            },
          ),
          ElevatedButton(
              onPressed: () {
                Navigator.of(context).push(
                    MaterialPageRoute(builder: (_) => const SecondPage()));
              },
              child: const Text('go to second page')),
        ],
      ),
    );
  }

  @override
  void dispose() {
    _controller.dispose();
    super.dispose();
  }
}

class SecondPage extends StatelessWidget {
  const SecondPage({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return const Scaffold(
      body: Center(
        child: Text('Second Page'),
      ),
    );
  }
}

More information on the issue:

Reproduced on both versions of flutter: stable 2.8.1 and on latest master 2.9.0-1.0.pre.129 with both debug or release versions.
Reproduced using either canvaskit or html renderers.
Seems to be exclusive to Safari web browser on devices running iOS 15.
Changing Safari tabs' settings from Tab Bar to Single Tab (i.e: reverting back the address bar to the top where it used to be) seems to solve the issue, but obviously we can not force users to choose one behavior over the other.
We can notice another issue when I try to dismiss the keyboard it re pops everytime as if the TextField regains focus for some reason. I am not sure if the two issues are related, however, I consider the blank area at the bottom is my main focus since its sabotaging the entire user experience.

HI @shadyaziza, there's already a similar issue describing what you're experiencing in https://github.com/flutter/flutter/issues/95010. Kindly follow up there for more information.
Closing from here as duplicate.
Thank you


Remove global variable declaration

data wasn't declared as var data so it leaked into the global scope

Many thanks for this. :) Released to npm as v0.4.5.

Thank you for the quick release :)


can't run the RAG_Chatbot_Example.ipynb

System Info
Hello,
I have issues running the RAG_Chatbot_Example.ipynb notebook.
When running the curl command in the notebook,
!curl localhost:8080/generate -X POST -H 'Content-Type: application/json' -d '{"inputs": "What is good about Beijing?", "parameters": { "max_new_tokens":64}}' #Replace the locahost with the IP visible to the machine running the notebook
I get the following error
curl: (6) Could not resolve host: application
curl: (3) URL rejected: Malformed input to a URL function
curl: (3) URL rejected: Port number was not a decimal number between 0 and 65535
curl: (3) unmatched brace in URL position 1:
{

I replaced the localhost with the my machine IP which is running the notebook and I'm having Apache HTTP server running in background. What could be wrong to fix this issue?
Information

[X] The official example scripts
[ ] My own modified scripts

🐛 Describe the bug
Hello,
I have issues running the RAG_Chatbot_Example.ipynb notebook.
When running the curl command in the notebook,
!curl localhost:8080/generate -X POST -H 'Content-Type: application/json' -d '{"inputs": "What is good about Beijing?", "parameters": { "max_new_tokens":64}}' #Replace the locahost with the IP visible to the machine running the notebook
Error logs
curl: (6) Could not resolve host: application
curl: (3) URL rejected: Malformed input to a URL function
curl: (3) URL rejected: Port number was not a decimal number between 0 and 65535
curl: (3) unmatched brace in URL position 1:
{
Expected behavior
The curl command should execute correctly.

@monaalsh sorry for the late reply. did you run TGI on your local machine?
Can you try steps here?

Hi! It seems that a solution has been provided to the issue and there has not been a follow-up conversation for a long time. I will close this issue for now and feel free to reopen it if you have any questions!


Format auth_controller.ex

This is the first in a series of pull request I plan to open, inspired by Elixir Issue #6643.
It's the result of running the Elixir formatter (shipping with Elixir 1.6) against one file in Tilex. Like the Elixir language, I'd like Tilex to conform to the Elixir formatter and growing style consensus of this community. A final step will be enforcing it on each CI build.
I realize this will create churn, but in my opinion it's worth it. These changes can start conversation about our code, and maybe some pull requests against the Elixir formatter itself.
If you're interested in joining in, install Elixir head (with homebrew for example):
$  brew install elixir --HEAD

And run the formatter on your file of choice:
$ mix format lib/tilex/path/to/my_file.ex

Elixir Issue #6643 explains how to use this tool in greater detail.

The big change here is adding parens to make it more obvious what the arguments to a function are.  I like this more than 'poetry mode' most of the time.
The spacing changes make sense to me and I think are an improvement.

Definitely looks a lot better, thanks for the repo 👍


Microsoft.StreamAnalytics/streamingJobs

Describe the noise
Resource type (i.e. Microsoft.Storage/storageAccounts)
Microsoft.StreamAnalytics/streamingJobs
apiVersion (i.e. 2019-04-01)
2017-04-01-preview
Client (PowerShell, Azure CLI, or API)
PowerShell
Relevant ARM Template code (we only need the resource object for the above resourceType and apiVersion, but if it's easier you can include the entire template
Expected response (i.e. "I expected no noise since the template has not been modified since the resources were deployed)
Properties should not change
Current (noisy) response (either include a screenshot of the what-if output, or copy/paste the text)
Scope: /subscriptions/<subscription id>/resourceGroups/lz-stream-analytics-rg

  ~ Microsoft.StreamAnalytics/streamingJobs/lzaztestsaj01 [2017-04-01-preview]
    - properties.contentStoragePolicy: "SystemAccount"
    - properties.jobType:              "Cloud"
    + properties.transformation:

        name:                   "lzaztestsaj01Query"
        properties.query:       "SELECT
  *
INTO
   [YourOutputAlias]
FROM
   [YourInputAlias]"
        properties.streamUnits: 1

Additional context
Add any other context about the problem here.

[w45].

This fix should be fully deployed. Let us know if you are still setting this issue.


Request - version bump on js files or revert master

Preface: I know this project is not maintained any longer.
I'm looking to upgrade to the new non-jquery version and checked to see if there were any fixes since the 1.4.1 release I have in the interim.
I noticed that these lines still reads 1.4.1 -

https://github.com/carhartl/jquery-cookie/blob/master/src/jquery.cookie.js#L2
https://github.com/carhartl/jquery-cookie/blob/master/bower.json#L3
https://github.com/carhartl/jquery-cookie/blob/master/component.json#L5
https://github.com/carhartl/jquery-cookie/blob/master/cookie.jquery.json#L3
https://github.com/carhartl/jquery-cookie/blob/master/package.json#L3

Since this project is essentially shut down and the commits since 1.4.1 won't be integrated, I wanted to suggest either:

Roll "master" back to the 1.4.1 release (the current master can be a working version or something)
Update the 1.4.1 release number in master to 1.4.2-dev or 1.4.2-unreleased

I don't understand exactly what is the problem. 1.4.1 is the latest release for jquery.cookie. js-cookie started from https://github.com/js-cookie/js-cookie/commit/4527b3725ce7b61066e6aa12bbe8d20c0371a1d7 up to the version 1.5.0, which contains everything this repo has, except the notices.

The problem with hard reset is that it will break forks.
Releasing a new version doesn't seems to make sense because everything here is contained in the version 1.5.0 anyway.

Btw, the master branch should not be used in production because it is, by default, an unstable branch. The only version that should be considered here is the ones that were released up to 1.4.1.

I'm not suggesting a new release.  I'm suggesting that either the "master" branch of this project roll-back to the 1.4.1 release, or that the files be tagged "1.4.2-dev" (but no new release made).
The reason is because the master branch is not actually "1.4.1" -- it has a lot of commits since then, but the repo's design makes it look like master is 1.4.1.  I

The reason is because the master branch is not actually "1.4.1"

Now I got it, it can be confusing for people that copies the code directly from the source. Is that it?

So you expect the master branch to practically match a release, like in the git flow model?

@FagnerMartinsBrack yes.  If someone looks at this repo and says "ok, let's just see what the last update here is..." then looks at the file, they get the unreleased version not the actual 1.4.1
@carhartl I'm a fan of that model, but not expecting it. Many projects might use a "-dev" or other placeholder version in their master branch, or bump the version number up to the forthcoming release.  This repo is weird/misleading because there is a "1.4.1" tag, but the "master" branch used for development has files labeled "1.4.1" as well.  It suggests that the master and the tag are the same, but master is many commits ahead.

I am convinced that changing the version number to 1.4.2-unreleased or 1.4.2-frozen for all relevant files in master (without publishing it on npm) is a reasonable request to prevent further confusion.
@carhartl what do you think?

@jvanasco sorry to take too long, here is the Pull Request, care to take a look?

I still haven't unterstood up to this day what the problem is.

I still haven't unterstood up to this day what the problem is.

Basically if he goes to the Releases page it says:

39 commits to master since this release

This will make one to think that there were additional important fixes on this repository after 1.4.1 which weren't released with 1.4.1. We know it is not the case and all commits went to the new repo, but those ending up here don't know that. Since most people jump straight to the version in the source file or json metadata to check the actual version, 1.4.2-unreleased provides a clear hint that the commits belong to a non released version 1.4.1.
Other solution is to create an actual new 1.4.2 release and publish on npm so that master is not too far away from the latest release.

@carhartl @jvanasco I will leave #388 open, if there is no feedback for a few days I will just merge it to close this issue, then we can monitor if anybody else will have this kind of problem in the future.
Does that makes sense?

Looks good.
That's a good distillation of the confusion.
Also, If you search online for the latest version, you'll end up seeing the current master which is really "1.4.2-unreleased" and not 1.4.1 as labeled.  So it can be confusing to see what version is really running -- especially if junior devs are checking in the file.

On Mar 4, 2016, at 6:12 AM, Fagner Brack<EMAIL_ADDRESS>wrote:
I still haven't unterstood up to this day what the problem is.
Basically if he goes to the Releases page it says:
39 commits to master since this release
This will make one to think that there were additional important fixes on this repository after 1.4.1 which weren't released with 1.4.1. We know it is not the case and all commits went to the new repo, but those ending up here don't know that. Since most people jump straight to the version in the source file or json metadata to check the actual version, 1.4.2-unreleased provides a clear hint that the commits belong to a non released version 1.4.1.
Other solution is to create an actual new 1.4.2 release and publish on npm so that master is not too far away from the latest release.
—
Reply to this email directly or view it on GitHub.

It seems this s going nowhere, as from this comment.
I have added the following to the version 1.4.1 in the releases page, I hope this at least clarifies for those who don't read the README and go straight to the releases page:

Note:
This is the last version on this repository. To see all the versions, check the new repository.
For more information, see this comment.


No genesis proof file was found and not allowed to generate a new genesis proof

I followed the instruction of this documentation: https://minaprotocol.com/docs/connecting. running ubuntu 20 on a vps with plesk. for further details, see attached log:
coda_crash_report_2021-03-26_13-50-23.432444.zip

Same error, running debian:9 in Docker.
docker run \
  --env-file $HERE/.env \
  -p 8302:8302 \
  --restart=always \
  --mount "type=bind,source=${HERE}/keys,dst=/keys,readonly" \
  --mount "type=bind,source=${HERE}/.mina-config,dst=/root/.mina-config" \
  --name my-mina \
  my-mina \
  daemon \
  --block-producer-key /keys/my-wallet \
  --insecure-rest-server \
  --file-log-level Debug \
  --log-level Info \
  --peer-list-url https://storage.googleapis.com/mina-seed-lists/mainnet_seeds.txt

coda_crash_report_2021-03-29_06-50-39.365662.tar.gz

The issue is solved for me. I had to instruct mina daemon to --generate-genesis-proof true when connecting for the first time. It is mentioned at the top of the "Start up a node" chapter however missing from the "Docker" chapter.

thanks for the hint @aleksey-mahanov looking at the docker daemon config, it seems that the --block-producer-key $PATH_TO_WALLET was missing. so it also worked for me with that option.


How do I get the tile position from the cursor position?

Also it would be very convenient if there was an event that was responsible for pointing the mouse at the object/tile, and not just when clicking

it is costly in terms of performance. but you can look at this method if you want to implement it anyway: https://github.com/axaq/traviso.js/blob/881652092fc417fd8671e215a302655700494513/bin/traviso.dev.js#L3972


first responder error on window creation (since macOS Sierra)

2016-11-29 12:03:03.040681 Tribes[12757:699578] [General] ERROR: Setting <GLFWContentView: 0x101422470> as the first responder for window <GLFWWindow: 0x10400ec10>, but it is in a different window ((null))! This would eventually crash when the view is freed. The first responder will be set to nil.
(
0   AppKit                              0x00007fffa58f29a4 -[NSWindow _validateFirstResponder:] + 566
1   AppKit                              0x00007fffa50e39eb -[NSWindow _setFirstResponder:] + 31
2   AppKit                              0x00007fffa518b66a -[NSWindow _realMakeFirstResponder:] + 406
3   AppKit                              0x00007fffa518b480 -[NSWindow makeFirstResponder:] + 123
4   Tribes                              0x000000010003392e createNativeWindow + 1230
5   Tribes                              0x000000010003320f _glfwPlatformCreateWindow + 63
6   Tribes                              0x000000010003d947 glfwCreateWindow + 887
7   Tribes                              0x000000010000cee0 _ZN4Game8initGLFWEv + 192
8   Tribes                              0x000000010000ccc1 _ZN4GameC2Ev + 129
9   Tribes                              0x000000010000cfd5 _ZN4GameC1Ev + 21
10  Tribes                              0x0000000100015226 main + 38
11  libdyld.dylib                       0x00007fffbc514255 start + 1
12  ???                                 0x0000000000000001 0x0 + 1
)

This should be fixed with #883.

Built from master just now, still throws the exact same error.

I experience the same issue. MacOS Sierra 10.12.1.

@MyForteIsTimeTravel What does glfwGetVersionString return?

"Version: 3.2.1 Cocoa NSGL chdir menubar retina"
As Jhauberg says it isn't a crash error or anything, but it does throw this error consistently on 10.12.

@MyForteIsTimeTravel The version in master is 3.3, so you are linking against an older version.

Okay, i must have copied the wrong one after i built. Sorry, my bad!

@MyForteIsTimeTravel No worries! Happens to us all. Does the library built from master work better?

Yeah it does, i got 3.3.0 and the errors gone. Many thanks

@kesperado What does glfwGetVersionString return?


Add current serial scheduler test to parallel scheduler test

This includes consolidating the use of create_transaction and
create_batch, adding setUp and tearDown to TestParallelScheduler,
adding test to TestParallelScheduler that should also work from
TestSerialScheduler, and adding the previous context_id to
create_context in test_transaction_order_with_dependencies.
Two tests are currently failing.

I suggest that the test file should have the parallel scheduler and serial scheduler test classes right after one another, instead of having the predecessor tree tests in between.
This commit, aa93605a77e9466274edc789566761b7bb5edb34, from my yaml-based scheduler PR, refactors the txn and batch creation utilities. Since this PR refactors those same utilities, we can save ourselves some work if we refactor them in one way to decrease merge conflicts in the future.
I would suggest again that we are using the same test code to test the parallel scheduler and serial scheduler where we have determined that each scheduler implementation needs to pass those tests. That could be done with a joint test class that all scheduler implementations must pass with non-test methods that are the actual test code, that take a scheduler instance, and then test methods that create the scheduler instance and the pass it in to the non-test method with the current code. That way, when looking at an error, it would be possible to tell just from the test framework failure message which scheduler implementation failed, whether the test was one that was specific to the implementation, or whether it was general to all scheduler implementations.

Updated to incorporate @boydjohnson suggestions


Split up compute API tutorial

split compute into: clusters (prev merged), modules/functions, and envs

Current dependencies on/for this PR:

#536  👈
main

This stack of pull requests is managed by Graphite.


vega-lib has no tagged commits/releases

Do we want to have tagged commits for consistency or is this going away with a monorepo anyway?

I don't know / think it is related but I have the following issue since v4.4.0: I can't seem to be able to install any other versions than the 4.4.0:
npm i<EMAIL_ADDRESS>+<EMAIL_ADDRESS>
Could it be an issue with the last publication?


Install go-junit-report in the cit presubmit container

The presubmit currently can't find the go-junit-report command, this should fix that.

/lgtm


[3459] Update calculations of diversity and disability disclosure

Context
Background:

DTTP has option 'Not known' for disabilities and ethnicities, Register does not.
Register has option 'Not provided' for disabilities and ethnicities, DTTP does not.

When we send to DTTP, we map "Not provided" => "Not known".
Now we're mapping in the other direction, so DTTP "Not known" comes through as "Not provided"
This makes things confusing.
https://trello.com/c/6rAWkoy1/3459-fix-imported-dttp-trainees-with-incomplete-ethnicity-sections
Changes proposed in this pull request
This PR:

Calculates diversity_disclosure in a separate method, since this depends on both disability and/or ethnicity presence. Before it was being calculated first based on disability, then based on ethnicity.. which would override the first calculation!
Records a disability_disclosure of "disability_not_provided" when the disability is not provided.
Records an ethnic_group of "not_provided_ethnic_group" when the ethnic background in DTTP is "Not known"

Guidance to review
Important business

Does this PR introduce any PII fields that need to be overwritten or deleted in db/scripts/sanitise.sql?
Does this PR change the database schema? If so, have you updated the config/analytics.yml file and considered whether you need to send 'import_entity' events?

 Fix imported DTTP Trainees with incomplete ethnicity sections


[IMPROVEMENT] Replace MuiTextField for Input

The TextField component implements a MuiTextField inside of a FormControl, but it isn't necessary since MuiTextField already implements a FormControl by design. We should replace it for an Input component and restructure the props passed to it.

@brunomous would you please confirm if this was fixed/merged?

@MrMaz fixed on #https://github.com/conceptadev/rockets-react/pull/104


do not impl Component for Task

Objective

Task are Component.
They should not.

Solution

Remove the impl, and update the example to show a wrapper.

#4052 for reference

You're right, I did link the wrong PR in https://github.com/bevyengine/bevy/pull/4052#pullrequestreview-894474081; the link should have been https://github.com/bevyengine/bevy/pull/2975.

Oh I missed that was part of that PR!

This is better as a standalone PR as it seems #2975 may take some time before it could be merged

bors r+

Should this be considered a breaking change?


No validation error on missing input binding source

Describe the bug
As a user I can create invalid (empty) input bindings, causing the diagram to become undeployable:
Command 'CREATE' rejected with code 'INVALID_ARGUMENT': Expected to deploy new resources, but encountered the following errors:
'diagram-5.bpmn':
[...]
- Element: Activity_0jjnbx9 > extensionElements > ioMapping > input
    - ERROR: Expected expression but not found.
 [ deploy-error ]

While the deployment fails the error is not indicated in the error panel.
Steps to reproduce

Open diagram_1.bpmn
Deploy to C8 (8.2-alpha) cluster
See deploy error / see no prior error in Problems tab

Expected behavior

Validation indicates that input source (and target) must be provided.
Validation indicates that output source (and target) must be provided.

Environment

OS: any
Camunda Modeler Version: 5.6.0
Execution Platform: Camunda Cloud
Installed plug-ins: camunda-modeler-custom-linter-rules-plugin

Additional context
No response

As we pick this up we must ensure we have a proper interaction between technical property validation and element templates (https://github.com/camunda/camunda-modeler/issues/3360).

CC @christian-konrad


Compose problems

See if it's practical to compose problems for the new games by looking for advice on composing orthodox problems.
Some possible sources of advice:

The Chess Polyglot introduction
The Chess Polyglot resources
Oz Problems
Olive tool

After studying chess problems for a while, I realised that the point of this project was to avoid chess study!
Maybe instead of including formal chess problems, I use solvable examples to clarify the rules. "Only one move is legal in this situation. Can you see what's wrong with the others?"


Add data type to error message when failing to convert an array

This can help debug incorrect data types.

@progval  Thanks for your PR! debugging story / erorr messages def. is a big todo.


Failed reading cpu stats file on WSL2

Starting the service it exists with exit code 0 and throws "Failed reading cpu stats file".
Im using WSL2 and Docker Engine v4.16.1. I tried running it as a seperate docker container and adding it as a service to livekit, but seems to return the same message.
These are the logs:
{"level":"info","ts":1674200810.1469305,"logger":"ingress","caller":"redis/redis.go:53","msg":"connecting to redis","nodeID":"NE_hdd82Cduay5A","sentinel":false,"addr":"host.docker.internal:6379"} failed reading cpu stats file {"level":"debug","ts":1674200810.1541233,"logger":"ingress","caller":"service/service.go:119","msg":"starting service","nodeID":"NE_hdd82Cduay5A"} {"level":"info","ts":1674200810.1541848,"logger":"ingress","caller":"stats/monitor.go:126","msg":"available CPU cores: 12.000000 max cost: 2.000000","nodeID":"NE_hdd82Cduay5A"}
This is my configuration file:
log_level: debug api_key: <retracted> api_secret: <retracted> ws_url: ws://<retracted>:7880 redis:   address: host.docker.internal:6379   username: ""   password: ""   db: 0 cpu_cost:   rtmp_cpu_cost: 2.0 ingress:   rtmp_base_url: rtmp://<retracted>

Issue is fixed when building docker image from source...


The RSI calculation fails with a certain dataset

I am trying to figure out why I cannot get the RSI to work with one certain dataset in JSON.
As a reference I tried the RSI with multiple datasets and all work great, it is just this one that does not seem to work. I debugged for a while and cant find the answer.
const calculateRSI = data => {

  const rsiData = data.map((dataPoint, index) => {
    if (index < 14) {
      return {
        rsi: null,
        price: dataPoint.price,
        date: dataPoint.date,
      }
    }

    let rsi = new RSI(14)
    for (let i = 0; i < 15; i++) {
      rsi.update(data[index - i].price)
    }

    const result = parseFloat(rsi.getResult().valueOf())
    return {
      rsi: result,
      price: dataPoint.price,
      date: dataPoint.date,
    }
  })

  return rsiData
}

I execute the function as follows:
const { RSI } = require('trading-signals')

const weeklyData = require('./weeklyData.json')
const rsi = calculateRSI(weeklyData)

I get the following error for the weeklyData:
NotEnoughDataError: Not enough data

This happens exactly at position 139 of the weekly array.
This does not happen with the dailyData array, which has exactly the same structure.
Any ideas what is going on?
I uploaded the json files in txt format as reference.
Thank you in advance.
dailyData.txt
weeklyData.txt

Hi @matiasdc1, the NotEnoughDataError is thrown when you are not feeding enough data to the RSI instance. With new RSI(14) you have to call rsi.update at least 14 times before you can query rsi.getResult().


Assembly: reset doesn't clear selected libraries

Submitted a job. Hit reset button to submit next job. It cleared all fields, except selected libraries.
Also, after hitting reset button:

Reset button should be greyed out
job has been queued message should go away.

-Maulik

Fixed in https://github.com/PATRIC3/p3_web/pull/301

Submission message clearing fixed. The reset button being always active is not really a problem and would some effort to change.


Missing async function

Hi there,
I've been migrating from vue-snotify to vue3-snotify in my VueJS project and encountered an issue regarding the absence of the expected async function.
Here's a snippet of how the async function was used in the old version:
this.$snotify.async(`Link checking PR #${id}...`, () => new Promise((resolve, reject) => {
  DistributionsRepository.linkCheck(id)
    .then(() => {
      resolve({
        body: 'PR link checked!',
        config: {
          timeout: 2000,
          closeOnClick: true
        }
      });
      this.retrieveReportCounters();
    })
    .catch(() => {
      this.loading = false;
      reject({
        body: 'Error occurred during PR link check!',
        config: {
          timeout: 2000,
          closeOnClick: true
        }
      });
    });
}));

However, when attempting to use this functionality, I encountered the following error:
Uncaught TypeError: this.$snotify.async is not a function

It seems that the async function is missing or not implemented as expected in the current version of the vue3-snotify package.
Could you please provide guidance on this matter or consider addressing it in a future release?
Your assistance in resolving this issue would be greatly appreciated.
Thank you for your time and effort in maintaining this valuable npm package.
Best regards,
Robert

Hi @chiribuc, sorry for the late response.
The async function was added in this PR, and has gone into the 0.1.0 release.


Breaks if Skewness >= 1 as in BoE's latest forecast

I love what you've done here.
I wanted to see if I could reproduce the latest BoE fanchart (August 2022) but I am encountering the attached error message.
I have played around a bit with the data to try to see what is causing the issue and I think it occurs when Skewness >= 1 as it is in the latest BoE projections for two periods

Thanks for finding this issue. Fix is in progress and to be addressed in the new release.

Great :)

After investigating this issue, I have found that the package behaviour is consistent with the assumptions of the distribution forecasts as twopiece normals. That is, the skewness parameter should be in (-1, 1). So, the only change that I plan to make to the package is to raise an appropriate warning when parameters out of range are provided. I wrote a brief explanation about this on my blog. Thanks again for highlighting this to me.

Interesting!  Great blog post.  Thanks for looking into this and for publishing your insight into what the out of range skewness implies.

After some communication with BoE, they confirmed that what is published in their recent spreadsheet as Skewness is not the actual $\gamma$ parameter. Instead, they publish Skewness = difference between the mean and the median of the distribution. This quantity indeed can be outside the interval (-1, 1). So, what I did was to change my package twopiece (release 1.3.1) to accept this quantity and then calculate the parameter $\gamma$. This will in turn solve the issue with the fancharts. Besides, I updated fanchart (release 1.0.0) to require twopiece>=1.3.1. So, you can just update fanchart and the correct twopiece will be installed.
Once again, thanks for highlighting this issue! It was very helpful.


Screenshot functions and "find text on screen in a dialog box"

I have read Screenshot functions, and I know we can locate a button on screen, from a pre-made image of this button, such as this (example: calc.exe):

Question: How would it be possible to locate a UI element on screen via text and not via an image?
This is a generalization of https://github.com/asweigart/pyautogui/issues/520.
I see three approaches:

Do OCR on pyautogui.screenshot(), and find the text
Use WinAPI to get the actual text content of a dialog box, and find the position of each text element
Render the text with the default Windows GUI font (Segoe UI?) to a search.png file, and then use pyautogui.locateOnScreen('search.png') ?

Did someone get any success @asweigart with one of these methods, or another?

First attempt for approach number 3:
Open notepad.exe, go in "About Notepad", and run this:
import pyautogui, time
from PIL import Image, ImageFont, ImageDraw

def findTextOnScreen(text, fontsize=12):
    font = ImageFont.truetype("segoeui.ttf", fontsize)
    w, h = ImageDraw.Draw(Image.new("RGB", (1, 1), (255, 255, 255))).textsize(text, font=font)
    img = Image.new("RGB", (w, h), (255, 255, 255))
    ImageDraw.Draw(img).text((0, 0), text, (0,0,0), font=font)
    img.save('test.png')
    yield from pyautogui.locateAllOnScreen('test.png', grayscale=True, confidence=0.75)

for box in findTextOnScreen('About Notepad'):
    print(box)
    pyautogui.moveTo(box.left, box.top)
    time.sleep(1)

It will mouse the mouse to "About notepad" title bar.
Problem: even if using grayscale=True, it's still very sensitive to color background. For example it doesn't work for buttons with grey background. Any idea @asweigart?

First attempt for approach number 3:
Open notepad.exe, go in "About Notepad", and run this:
import pyautogui, time
from PIL import Image, ImageFont, ImageDraw

def findTextOnScreen(text, fontsize=12):
    font = ImageFont.truetype("segoeui.ttf", fontsize)
    w, h = ImageDraw.Draw(Image.new("RGB", (1, 1), (255, 255, 255))).textsize(text, font=font)
    img = Image.new("RGB", (w, h), (255, 255, 255))
    ImageDraw.Draw(img).text((0, 0), text, (0,0,0), font=font)
    img.save('test.png')
    yield from pyautogui.locateAllOnScreen('test.png', grayscale=True, confidence=0.75)

for box in findTextOnScreen('About Notepad'):
    print(box)
    pyautogui.moveTo(box.left, box.top)
    time.sleep(1)

It will mouse the mouse to "About notepad" title bar.
Problem: even if using grayscale=True, it's still very sensitive to color background. For example it doesn't work for buttons with grey background. Any idea @asweigart?

Are you interested for a pull request for something like this:
def clickTextOnScreen(text, fontname="segoeui.ttf", fontsize=12):
    font = ImageFont.truetype(fontname, fontsize)
    w, h = ImageDraw.Draw(Image.new("RGB", (1, 1), (255, 255, 255))).textsize(text, font=font)
    img = Image.new("RGB", (w, h), (255, 255, 255))
    ImageDraw.Draw(img).text((0, 0), text, (0,0,0), font=font)
    pos = pyautogui.locateCenterOnScreen(img, grayscale=True, confidence=0.75)
    pyautogui.click(pos)

clickTextOnScreen('About Notepad')

It seems to work in many cases (except when the background color is not white).

Are you interested for a pull request for something like this:
def clickTextOnScreen(text, fontname="segoeui.ttf", fontsize=12):
    font = ImageFont.truetype(fontname, fontsize)
    w, h = ImageDraw.Draw(Image.new("RGB", (1, 1), (255, 255, 255))).textsize(text, font=font)
    img = Image.new("RGB", (w, h), (255, 255, 255))
    ImageDraw.Draw(img).text((0, 0), text, (0,0,0), font=font)
    pos = pyautogui.locateCenterOnScreen(img, grayscale=True, confidence=0.75)
    pyautogui.click(pos)

clickTextOnScreen('About Notepad')

It seems to work in many cases (except when the background color is not white).

@josephernest thanks man you just saved me so much time 🙏


Add functionality to dynamically add groups, paths etc. to the Vector

i do this but no work ;
setPathData(M M806.004057 333.205894 364.566136 333.2.271448-167...)
update();
how can i do it?

setPathData() function is currently doesn't do anything; It will be really expensive to build whole path data again.
Instead of changing path data , just create a new vector and use it. Use two VectorMasterDrawable and set the different source vectors for each of them. Then just use these two drawables anywhere you want to use.

Thank you for your answer.But I have a demand,I get the .svg from the server, but I can not manipulate it, so I want to get it on his path settings, but I can not find a way to set the vector dynamically.

oh ! i did it like this;
leftPath.setPathData("M806.004057 333.20589..)
leftPath.buildPath(true);
left.update(); -->need buildpath(true) it work
but why when i do like this it not work anymore
public void onClick(View v){
leftPath.setPathData("M806.004057 333.20589..)
leftPath.buildPath(true);
left.update();
}

if pathdata too long it also not work,I need to dynamically add group, path, pathDate ,plesase help me
thank you

@ViewMikeZhou : I will add the functionality to dynamically add groups,paths etc. in some time.

Very much looking forward,thank you

Hey bro is now setpathdata working???

WOW


some suggestions abort UI display

I found that once the [Activity Bar Position] is set to [Top], i can't find the activity bar at the top anymore, when i click [File->New Window] to open a new window.
Therefore, i suggest  display the activity bar by default when opening a new window.

As shown in the picture, the new window displays nothing.

I like this idea, I will look into it.


[BUG] Error "Unable to start actor, Failed to find host " on trying to load hot reload actor from file

Describe the bug
When following the instructions at: https://wasmcloud.com/docs/app-dev/create-actor/update/
I get an error upon trying to create the hot reload actor: "Unable to start actor, Failed to find host "
To Reproduce
Follow the documentation at https://wasmcloud.com/docs/app-dev/create-actor/update/.
Expected behavior
To not get the error
Screenshots

**Environment (please complete the following information) **

Additional context
It's incredibly likely I've simply done something wrong, and I really wish I knew what and didn't have to bother you xD

Hey @connorsmith256 !
I just did a wash up from my bash terminal, no docker or anything. I cargon installled wash if that helps.

Thanks for the extra info. There is a workaround you could use if hot-loading is important to you, before we release the next version:
When starting a host with wash, you can specify the version to use, i.e.
WASMCLOUD_VERSION=v0.59.0 wash up

(v0.59.0 of the host doesn't have the bug that v0.60.0 of the host does)
A new version of the host with the fix should be released soon, but I hope this helps in the meantime!

This was definitely an issue as of 0.59, but it was fixed by @vados-cosmonic in a future version


Inconsistent data in cargo metadata

Problem
cargo metadata produces inconsistent dependency graph (there's an edge to the node which does not exist)
Steps
$ git clone https://github.com/ChaseElectr/analyzer-panic
$ cd analyzer-panic
$ cargo metadata

Notice how the packages section has
"diesel 1.4.3 (git+https://github.com/ChaseElectr/diesel?branch=1.4.x#066bc412d7ead423e71de811b1dac9428a63712c)"

but the resolve section has
"diesel 1.4.3 (git+https://github.com/ChaseElectr/diesel?branch=1.4.x#24af5f700c111c2b995953a40f7a262d0872a00d)"

Notes
This is using master (c326fcb37e7eacbcc1f3671193db133440ea1968) cargo. Here's the gist with various printouts:
https://gist.github.com/matklad/eed0d46f427af5abf3c024cc07c59663
(I've added some printfs to the code which produces metadata)
This is what I gather from that output:

Cargo.lock uses diesel #24af5f7, I assume this is what we want to see.
cargo metadata uses the right #24af5f7 in the deps section, and the wrong one in the packages section.
the package_map contains the wrong diesel (this I think the bug)
the node_map contains both diesels.

I haven't looked into this further yet, as I am hoping someone from cargo team immediately knows what's the issue :)

I'm inclined to close this. After further inspection, it looks like the issue is related to specifying both a branch and a revision at the same time.  Cargo specifically warns about this:
warning: dependency (diesel) specification is ambiguous. Only one of `branch`, `tag` or `rev` is allowed. This will be considered an error in future versions
warning: dependency (diesel_derives) specification is ambiguous. Only one of `branch`, `tag` or `rev` is allowed. This will be considered an error in future versions

Of course it's probably best for Cargo not to stumble on it, but since it isn't supported to start with, I'm not sure it is worth putting time into.  We could change the warning to an error, since it has been around for a few years.
Does that sounds reasonable?

Yeah, I think upgrading to an error would be totally OK here. Well, maybe adding some asserts internally to elevate this to an ICE of sorts would also be prudent, but only if that doesn’t require much new logic.

Hey, any updates here? 😅 🙏


Document setup of azure devops pipeline variable group for credential sharing

Include instructions for granting pipelines permission to read the group variables

Completed in wiki


PLAT-124516: Fixed console error when tapping SliderButton

Enact-DCO-1.0-Signed-off-by: Adrian Cocoara<EMAIL_ADDRESS>Checklist

[x] I have read and understand the contribution guide
[x] A CHANGELOG entry](http://enactjs.com/docs/developer-guide/contributing/changelogs/) is included
[ ] At least one test case is included for this feature or bug fix
[x] Documentation was added or is not needed
[ ] This is an API breaking change

Issue Resolved / Feature Added
Issue: A console error is shown when tapping SliderButton in QA-sampler
Resolution
Solution: Refactored SliderButtonBehaviorDecorator and used @enact/core/handle to forward the onChange function
Links
PLAT-124516
Comments

I don't know why we should change the component to the hoc.
I think we could just change onChange to
			forward('onChange', {
				type: 'onChange',
				value
			}, this.props);

will fix the error. You could replace this.props to props from by replacing ({onChange, ...rest}) to props.
Let's not converting this component to hoc.

Considering this paragraph: "core/handle provides a set of utilities to support handling events for kind()s and React.Components" (https://enactjs.com/docs/modules/core/handle/), do you think we could use forward with a simple function component?

@MikyungKim I just tried your suggestion and it works. I will change it accordingly. Thanks!

I don't know why we should change the component to the hoc.
I think we could just change onChange to
			forward('onChange', {
				type: 'onChange',
				value
			}, this.props);

will fix the error. You could replace this.props to props from by replacing ({onChange, ...rest}) to props.
Let's not converting this component to hoc.

Considering this paragraph: "core/handle provides a set of utilities to support handling events for kind()s and React.Components" (https://enactjs.com/docs/modules/core/handle/), do you think we could use forward with a simple function component?

Actually, I didn't think of this much. I think we need a discussion on this. Thanks!

@adrian-cocoara-lgp I think we could use forward in functional components. Please go ahead changing.


Display image into conversation after a suggested action based on image is selected

Feature Request
When an image is used into a suggested action, the webchat send a message (hidden behind the image) to the bot when the suggested action is selected.
Into the conversation, the message sent back to the bot is displayed astext but the image used as suggested action is not displayed.
Describe the suggestion or request in detail
It could be very nice if, when a user selects a suggested action with an image, the image of the suggested action selected is displayed into the conversation.
This image should not be send back to the bot, the text behind the suggested action is enough.

@stevkan Can you take a look at this?

@RenaudDemarneffe, a few questions for you to fully understand:

Can you share with me the code you are using for sending/processing the suggested action both from your bot and in web chat?
Which version of Web Chat are you using?
Is this a new issue or did this previously work and only recently stopped (i.e. worked on 4.8.0, but not in 4.10.1)?
What is the image you are trying to send? Can you share a link or can you include details about the image (size, type, etc.)?

@stevkan , thank you for taking my issue into acount. Here are the responses to your questions:

Can you share with me the code you are using for sending/processing the suggested action both from your bot and in web chat?
The code from the bot is the following:

const buttons: CardAction[] = [];
buttons.push({
   type: ActionTypes.MessageBack,
   title: "Button label",
   text: "Button response sent to bot",
   image: "https://cdn-3d.niceshops.com/upload/image/product/large/default/vallejo-game-color-bloody-red-17-ml-279653-fr.jpg",
   displayText: "Button label",
   value: undefined,
   imageAltText: "Button label",
});
MessageFactory.suggestedActions(buttons, "Response title);

I don't add code to WebChat to handle the suggested action.
Here is a screen cap of the suggested actions into WebChat.

When I click on the suggested action, I get this message into the conversation.

and I think it could be nice to also have the image into the message.

Which version of Web Chat are you using?

I use the version 4.8.1 of WebChat and 4.10.3 of botbuilder.

Is this a new issue or did this previously work and only recently stopped (i.e. worked on 4.8.0, but not in 4.10.1)?

I don't know, it's the first time I use suggested actions with images. I think it's an more an enhancement than an issue.

What is the image you are trying to send? Can you share a link or can you include details about the image (size, type, etc.)?

This image I try to send is an icon to give more insight to the user.

@RenaudDemarneffe, thank you for your patience. I'm looking into how this could be implemented. Whether there is a possibility of a temporary workaround or is only achievable via a change to the SDK.

@stevkan , what is the status of this item? Could you please update it? Thank you.

@RenaudDemarneffe, apologies for the delay. I may have the solution worked out but need to check a couple aspects of it. If I not today, I should have an update by early next week.


snr estimate

what are #1~#5 mean in the 75~79 lines of file "pns/noise_suppressor.py"?
like this:
#1 rough noise estimation
#2 rough a priori and posteri snr estimation
#3 speech presence prabability estimation
#4 precise noise estimation
#5 a priori and posteri snr estimation
I only see codes of condition "fnz_flag==1" here. Are you going to accomplish them in the future?
Actually, I want to do snr estimate with your code in this project. could you please tell me how I can do the calculation? Thanks !!!

hi @rainskyfyy
I think #1~5 is implemented in noise_estimator (line 82), which are the steps of IMCRA.

Hi @rainskyfyy , sorry I've not very active on github for a while.
The nosie estimation is implemented in noise_estimator.py.
Please refer to Cohen's papers for more details on noise estimation.
I. Cohen and B. Berdugo, Speech Enhancement for Non-Stationary Noise Environments, Signal Processing, Vol. 81, No. 11, Nov. 2001, pp. 2403-2418.
I. Cohen, Noise Spectrum Estimation in Adverse Environments: Improved Minima Controlled Recursive Averaging, IEEE Trans. Speech and Audio Processing, Vol. 11, No. 5, Sep. 2003, pp. 466-475.
Thank you @SouppuoS  for the reply.


Add default to participant_allowlist

Description
Small thing I found - when making a new experiment I was getting errors in the javascript console as {{ form.initial.participant_allowlist}} resolves to nothing.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Additional details and impacted files

:loudspeaker: Thoughts on this report? Let us know!


Mono iOS Deploy - System.EntryPointNotFoundException for SystemNative_GetNonCryptographicallySecureRandomBytes

Godot version:
3.2.2-beta2-mono
OS/device including version:
OSX 10.15.4
XCode 11.4.1
iPhone 8, iOS 13.4.1
Issue description:
Deploying a Mono C# project on iOS with 3.2.2 works fine in the simulator, fails on real device deploy when you "Archive" the project and deploy on physical iOS device via Ad hoc distribution of an .ipa file. The application display the loading image, then crashes immediately with this unhandled exception of an apparent linking error:
May 17 14:02:26 Davids-iPhone DodgetheCreeps[22461] <Notice>:
Unhandled Exception:
System.TypeInitializationException: The type initializer for 'System.Random' threw an exception. ---> System.EntryPointNotFoundException: SystemNative_GetNonCryptographicallySecureRandomBytes
  at Interop.GetRandomBytes (System.Byte* buffer, System.Int32 length) [0x00000] in <e8ca3a82b1c44b21ba65f40b11f07643>:0
  at System.Random.GenerateGlobalSeed () [0x00000] in <e8ca3a82b1c44b21ba65f40b11f07643>:0
  at System.Random..cctor () [0x00000] in <e8ca3a82b1c44b21ba65f40b11f07643>:0
   --- End of inner exception stack trace ---
  at Main..ctor () [0x00000] in <928693da75cb4a549db27400f3bb9797>:0

This is reproducible on my personal Godot project, as well as the public sample of "Dodge the Creeps".
Relevant logs:
Archive Build Log
idevicesyslog output during crash (I build in cloud and deploy local, so unfortunately no access to USB debugging in xCode...)
Steps to reproduce:

Using the "Dodge The Creeps" Mono demo project, Export for iOS. Fill in Apple Team ID, identifier, 120x120 icon, etc.
Open the exported project in XCode. Optionally run in simulator to assert that it works there. Change device to Build Only Device of DodgeTheCreeps > Generic iOS Device, select Build > Archive, like his:

Press "Distribute App" then "Ad hoc distribution"

Make sure you authenticate to Apple in XCode and have added your device udid in apple developer settings

Finish off the distribution process to get your outputed DodgeTheCreeps.ipa file. Deploy to your physical iOS device

I did this with libimobiledevice software by running ideviceinstaller -i /path/to/DodgeTheCreeps.ipa

After the app installs on your physical iOS device, open the app. You should see the loading screen, then an immediate crash.

I parsed captured logs with idevicesyslog

Minimal reproduction project:
https://github.com/godotengine/godot-demo-projects/tree/master/mono/dodge_the_creeps with the above steps

FYI, just tested again with 3.2.2-beta3--I'm getting the same result with that as well.

Just tested again with 3.2.2-rc1--same result

For reference, #40633 also includes an example project for reproducing this issue.

So its documented, Random is used by ThreadPool.QueueSegment internally, and so you can end up running into this when using Tasks (e.g. Task.Delay will throw this exception for me).

Reproduce this when export for macOS too, at version v3.2.3.stable.mono.official.

This was created first but I'm going to close it as duplicate of #40757 because discussion has developed more there.


monitor future package vulnerabilities

For later
We might also want to consider how we monitor for future vulnerabilities, the more packages we have the more checks we need although these can be automated with tools like Snyk:
https://gds-way.cloudapps.digital/standards/tracking-dependencies.html#how-to-manage-third-party-software-dependencies

github seems to be doing this automatically for us, but i can also set up snyk to do this

closing as can't be addressed in the code base


Suggestion: open on the correct day

I was using the QtWS2018 app (Berlin) and the app always opened with the first day/tab opened.  It would be nice that, when you are on one of the days of the conference, that the app opens with that day/tab active.
And another minor issue: On Android, it was close to impossible to leave the app with the device back key (it opened the left menu).

opening on the actual day is already on my todo list.
aaah ... there should be a "Close App" in Drawer (left Menu)
or I can ask if user wants really to quit
thx


Add property to center GridList

It could be great if a GridList could be centered, by a prop in <GridList> element.
The prop should add a CSS property to the 'mdc-grid-list__tiles' class, applied to the <ul> element:
justify-content: center
Now I'm doing this manually, adding the same property to a CSS module class, applied to my component:
.mdcGridListTiles ul {
    justify-content: center;
}

Thanks for the comment @alecchisi. RMWC strives to be an un-opinionated wrapper around material-web-components. While this feature might be useful, it's not one that implements any MWC behavior.
Your solution is the recommended way of achieving it though. Another option is to make a wrapping component that can handle your additional features and props.


Non browsers requests to satellite apps  should not throw intestitial

Requests to satellite apps visited by non browsers should be treated as signed out
This is necessary, because tools like opengraph.xyz will not follow redirects, and they will always end up with parsing our interstitial template.
Type of change

[x] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[ ] @clerk/clerk-js
[ ] @clerk/clerk-react
[ ] @clerk/nextjs
[ ] @clerk/remix
[ ] @clerk/types
[ ] @clerk/themes
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[x] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] @clerk/chrome-extension
[ ] gatsby-plugin-clerk
[ ] build/tooling/chore

Description

[ ] npm test runs as expected.
[ ] npm run build runs as expected.

!snapshot

Hey @panteliselef - the snapshot version command generated the following package versions:

Package
Version

@clerk/backend
0.23.7-snapshot.3f63646

@clerk/chrome-extension
0.3.18

@clerk/clerk-js
4.51.0

eslint-config-custom
0.3.0

@clerk/clerk-expo
0.18.9

@clerk/fastify
0.5.6-snapshot.3f63646

gatsby-plugin-clerk
4.3.19-snapshot.3f63646

@clerk/localizations
1.22.0

@clerk/nextjs
4.21.13-snapshot.3f63646

@clerk/clerk-react
4.21.0

@clerk/remix
2.6.16-snapshot.3f63646

@clerk/clerk-sdk-node
4.10.14-snapshot.3f63646

@clerk/shared
0.19.1

@clerk/themes
1.7.5

@clerk/types
3.46.1

Tip: use the snippet copy button below to quickly install the required packages.
# @clerk/backend
npm i<EMAIL_ADDRESS>
# @clerk/chrome-extension
npm i<EMAIL_ADDRESS>
# @clerk/clerk-js
npm i<EMAIL_ADDRESS>
# eslint-config-custom
npm i<EMAIL_ADDRESS>
# @clerk/clerk-expo
npm i<EMAIL_ADDRESS>
# @clerk/fastify
npm i<EMAIL_ADDRESS>
# gatsby-plugin-clerk
npm i<EMAIL_ADDRESS>
# @clerk/localizations
npm i<EMAIL_ADDRESS>
# @clerk/nextjs
npm i<EMAIL_ADDRESS>
# @clerk/clerk-react
npm i<EMAIL_ADDRESS>
# @clerk/remix
npm i<EMAIL_ADDRESS>
# @clerk/clerk-sdk-node
npm i<EMAIL_ADDRESS>
# @clerk/shared
npm i<EMAIL_ADDRESS>
# @clerk/themes
npm i<EMAIL_ADDRESS>
# @clerk/types
npm i<EMAIL_ADDRESS>

!snapshot

Hey @panteliselef - the snapshot version command generated the following package versions:

Package
Version

@clerk/backend
0.23.7-snapshot.a1cee25

@clerk/chrome-extension
0.3.18

@clerk/clerk-js
4.51.0

eslint-config-custom
0.3.0

@clerk/clerk-expo
0.18.9

@clerk/fastify
0.5.6-snapshot.a1cee25

gatsby-plugin-clerk
4.3.19-snapshot.a1cee25

@clerk/localizations
1.22.0

@clerk/nextjs
4.21.13-snapshot.a1cee25

@clerk/clerk-react
4.21.0

@clerk/remix
2.6.16-snapshot.a1cee25

@clerk/clerk-sdk-node
4.10.14-snapshot.a1cee25

@clerk/shared
0.19.1

@clerk/themes
1.7.5

@clerk/types
3.46.1

Tip: use the snippet copy button below to quickly install the required packages.
# @clerk/backend
npm i<EMAIL_ADDRESS>
# @clerk/chrome-extension
npm i<EMAIL_ADDRESS>
# @clerk/clerk-js
npm i<EMAIL_ADDRESS>
# eslint-config-custom
npm i<EMAIL_ADDRESS>
# @clerk/clerk-expo
npm i<EMAIL_ADDRESS>
# @clerk/fastify
npm i<EMAIL_ADDRESS>
# gatsby-plugin-clerk
npm i<EMAIL_ADDRESS>
# @clerk/localizations
npm i<EMAIL_ADDRESS>
# @clerk/nextjs
npm i<EMAIL_ADDRESS>
# @clerk/clerk-react
npm i<EMAIL_ADDRESS>
# @clerk/remix
npm i<EMAIL_ADDRESS>
# @clerk/clerk-sdk-node
npm i<EMAIL_ADDRESS>
# @clerk/shared
npm i<EMAIL_ADDRESS>
# @clerk/themes
npm i<EMAIL_ADDRESS>
# @clerk/types
npm i<EMAIL_ADDRESS>

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


awair sensor ... sensor precision

Home Assistant release with the issue:

0.85.1
Last working Home Assistant release (if known):
since first release
Operating environment (Hass.io/Docker/Windows/etc.):

venv on intel NUC running ubuntu 18.x
Component/platform:

awair -> https://www.home-assistant.io/components/sensor.awair/
Description of problem:
awair air quality monitor reports sensor values with varying precision.

in both instances,  temperature and humidity are reported with 13 significant digits while other sensor values have one significant digit

( i have used templates to generate rounded versions of the numbers ... however, i have 3 units so naming is messy)

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
# Awair air monitors
  - platform: awair
    access_token: !secret awair_token
    devices:
      - uuid: awair-r2_4750
      - uuid: awair-r2_4742

Traceback (if applicable):

Additional information:

@bmf7777 I believe this may have been an error on our side, where we were accidentally sending float values. Is this still happening for you?

i believe so ... i've recently upgraded to 0.91.0 and awair component stopped working ...
2019-04-04 16:47:07 ERROR (MainThread) [homeassistant.components.awair.sensor] Unexpected Awair API error: The query
2019-04-04 16:47:07 WARNING (MainThread) [homeassistant.components.sensor] Platform awair not ready yet. Retrying in 180 seconds.2019-04-04 16:47:07 ERROR (MainThread)
...

@bmf7777 we're looking into it. I've tracked it down to something either on our end (specifically our GraphQL structure) or the /python_awair repository.

@danielsjf and I were working on a Awair component before this was added which is available as a custom component here https://github.com/danielsjf/awair_component
The custom component still works as a backup while we wait for the official component to be fixed.

The files probably need to be renamed after the great migration.


Header component changes

Header Component.
Updated the header component and some header changes.
@aka-jain

Static header doesn't look nice in mobile view. Still improving it...

@aka-jain Please have a look :)
Travis is failing because surge is expecting some inputs.

@spyshiv @aka-jain Please review this. I want to finish the header today, so I can raise new PRs for other components dependent on this 💃

For now, clicking on Log in logs the user in after a tiny delay. Will add the complete login functionality with the login page later today 🍕

Codecov Report

Merging #56 into master will increase coverage by 2.82%.
The diff coverage is 74%.

@@            Coverage Diff             @@
##           master      #56      +/-   ##
==========================================
+ Coverage   67.92%   70.74%   +2.82%
==========================================
  Files           6       11       +5
  Lines          53      147      +94
  Branches        2        6       +4
==========================================
+ Hits           36      104      +68
- Misses         17       42      +25
- Partials        0        1       +1

Impacted Files
Coverage Δ

src/app/about/about.component.ts
100% <100%> (ø)

src/app/home/home.component.ts
100% <100%> (ø)
:arrow_up:

src/app/signup/signup.component.ts
100% <100%> (ø)

src/app/login/login.component.ts
100% <100%> (ø)

src/app/services/auth.service.ts
45% <46.15%> (-5%)
:arrow_down:

src/app/app.component.ts
51.28% <57.14%> (-2.29%)
:arrow_down:

...tials/nav/header-static/header-static.component.ts
75.6% <74.35%> (-24.4%)
:arrow_down:

src/app/global.service.ts
75% <75%> (ø)

src/app/auth/auth.component.ts
87.5% <87.5%> (ø)

... and 4 more

Impacted Files
Coverage Δ

src/app/about/about.component.ts
100% <100%> (ø)

src/app/home/home.component.ts
100% <100%> (ø)
:arrow_up:

src/app/signup/signup.component.ts
100% <100%> (ø)

src/app/login/login.component.ts
100% <100%> (ø)

src/app/services/auth.service.ts
45% <46.15%> (-5%)
:arrow_down:

src/app/app.component.ts
51.28% <57.14%> (-2.29%)
:arrow_down:

...tials/nav/header-static/header-static.component.ts
75.6% <74.35%> (-24.4%)
:arrow_down:

src/app/global.service.ts
75% <75%> (ø)

src/app/auth/auth.component.ts
87.5% <87.5%> (ø)

... and 4 more

Continue to review full report at Codecov.

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

@RishabhJain2018 Should have closed this PR before, I opened smaller PRs for the smaller components. Closing this now to avoid further confusion.
Please review #61 for the header :)


Rethink the examples in examples/

I was really happy when we finally could close #54. Opened in October, closed it in March. (And finally got all the tests in place in July.)
But I find that directory needs to live up to a higher standard nowadays. It should be about macros, (maybe) slangs, grammar hacking, language extensions, and the other things that makes 007 unique. It shouldn't just be examples that could be written in any half-competent ALGOLoid, no matter how nice they may look in 007.
Basically, I don't want people to go to the examples/ directory and be underwhelmed.
Let's go through them. Anything that's just "ordinary code" takes the cut.

[ ] 99-bottles.007: Remove.
[ ] euclid-gcd.007: Remove.
[ ] fizzbuzz.007: Remove.
[x] format.007: This one has a macro. #183 will make it better. Keep.
[ ] hanoi.007: Remove.
[ ] hello-world.007: Remove.
[x] name.007: Keep.
[ ] nicomachus.007: Remove.
[ ] quicksort.007: Remove.

Uh. But I also don't want just two examples in that directory.
So how about we also introduce new conforming examples with each one we remove? Yes, that'll make this issue decidedly non-low-hanging fruit. But I think it'll be worth it. It's a high ambition, but one we can comfortably aim for. There's plenty of macro ideas in the issue queue that we want to try anyway.

I just want to add, for sentimentality, that once it did feel amazing that we had all those code examples. But 007 has basically outgrown that. The previously fantastic is now the mundane. And that's a good thing.

I think two of the most realistic macro ideas to include in the examples would be #122 and #203. Both of those are definitely tied to real use cases.

Oh, and if I were to dream a bit, #116 would be really nice to have in examples/. To the point where it would almost be worth two old example scripts. :smile:
But the thing is, 007 as interpreted through Rakudo is still too slow to make an effective demonstration of #116. So we'd need either a JavaScript backend (#166), or something similarly fast and impressive.

I see I haven't mentioned #176 as an example I want in examples/. It definitely has a place there.
Yay! I love how this issue is now pushing the roadmap places. :smile:

Heck, a swap macro! I just tried to write one, but...
$ bin/007 -e='macro swap(a, b) { return quasi { my temp = {{{a}}}; {{{a}}} = {{{b}}}; {{{b}}} = temp; None } }; my w = 5; my z = 10; swap(w, z); say([w, z])'
Missing quasi
[...]

Dang, we really need to clean up our act with #10 and better parse errors in general. I want really good line/column numbers, and an arrow/⏏ into the place that's wrong.
As I tried to reduce this parse error, I ran into a simpler variant of #212. *sigh*
But anyway. swap macro. That takes our count to 6 macro examples. Since I said #116 is worth two old examples, we can actually throw out all the 7 old ones once we have those 6 new ones.

I have two ideas for slangs. These should probably not be considered blockers for this issue, but I figure I'd jot them down.

A Forth-like DSL inside a forth { ... } block term. The value of the whole term is what's on top of the stack at the end of the run. The powerful thing that makes this a slang is that values from the outside can be lexically accessed. Including custom operators. (Since notions of "infix" and "prefix" etc do not make sense inside the slang, some kind of pecking order has to be determined. What would we like - to mean, for example: prefix:<-> or infix:<->? The boring solution would be to require the long names for everything; but that doesn't look so elegant.)

An SQL DSL whose claim to fame would be that it doesn't allow injection attacks, because it escapes all the parametric values by default. This is an old idea; in 007 we don't really have to go all the way and connect to an actual database (although we could) — the main idea could be showcased somehow by just showing the resulting queries.

Here, let me summarize the macro examples that we want to implement and replace the old examples with. I'll try to put them in order, most desirable first:

[ ] ff and family (#207)
[ ] swap macro (#218)
[ ] reduce metaops (#176) ♁
[ ] postfix:<++> and family (#122) ❦
[ ] += and family (#152) ❦♁
[ ] .= mutating method call (#203) ❦♁
[ ] SEND + MORE = MONEY (#116)

The ones marked ❦ need #214 to land in order to work non-buggily. The ones marked ♁ need is parsed.

Also #202 and #215. My, there's no dearth of good macro examples to implement! (In my copious spare time, no less.) I would say importance-wise, these two slot in right above SEND MORE MONEY above.

Also #158 since it nicely showcases nested macros.

I think #229 (Elvis operator) deserves to go on this list as well.

I know this issue isn't really accepting any more nominations... But as I'm thinking about #481 and what I'd like to have ready by then to talk about, I realize #186 would be a really nice, small example.

Added a "currently blocked" label, because all the remaining examples are waiting on #177.


Update sbt-native-packager to 1.7.6

Updates com.typesafe.sbt:sbt-native-packager from 1.7.5 to 1.7.6.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.typesafe.sbt", artifactId = "sbt-native-packager" } ]

labels: sbt-plugin-update, semver-patch

+1

[X] Do all automated continuous integration checks pass?
Yes, additionally I tested the release candidate container, and checked the rpm/msi/tar/zip work as expected
[X] Is the update a patch, minor, or major update?
Minor release, no obvious changes that affect Daffodil
[X] Is the license still compatible with ASF License Policy?
Yes, same license. Note that we do not distribute this plugin, it is only used for generating releases
[X] Have any changes been made to LICENSE/NOTICE files that need to be incorporated?
No
[X] Have any transitive dependencies been added or changed?
No changes to transitive dependencies


Black Screen

Really new to this, got it running, but is only showing me a black screen in the browser. Am I doing something wrong? Thanks for your help!

Managed to fix it

Have another issue now, seems like the API key isn't set for cloud vision API. Do I need to create one for own use?

Fixed it, works!! Really cool 👍

@matthijswardenier How did you fix it?