[Automation] Missing utils Resource test boot for DBUS cmd

==============================================================================
Tests.Test Boot :: This testsuite is for testing the Boot Device Functions
Set the Boot Device as Default using REST API :: This testcase is ...
FFDC Collection Started         :<PHONE_NUMBER>2206958939
FFDC Collection Completed       :<PHONE_NUMBER>2219824980
| FAIL |
Setup failed:
No keyword with name 'Initialize DBUS cmd' found.
Set the Boot Device as Default using ipmitool :: This testcase is ...
FFDC Collection Started         :<PHONE_NUMBER>2219852801
FFDC Collection Completed       :<PHONE_NUMBER>2230113898
| FAIL |
Setup failed:
No keyword with name 'Initialize DBUS cmd' found.
Set the Boot Device as Network using REST API :: This testcase is ...
FFDC Collection Started         :<PHONE_NUMBER>2230134294
FFDC Collection Completed       :<PHONE_NUMBER>2244941848
| FAIL |
Setup failed:
No keyword with name 'Initialize DBUS cmd' found.
Set the Boot Device as Network using ipmitool :: This testcase is ...
FFDC Collection Started         :<PHONE_NUMBER>2244974880
FFDC Collection Completed       :<PHONE_NUMBER>2258254180
| FAIL |
Setup failed:
No keyword with name 'Initialize DBUS cmd' found.

This is due to one of the recent ipmitool related changes to test_boot use case..
The fix is simple.. just include the resource file of utils.robot which has this Dbus Keyword

==============================================================================
Tests.Test Boot :: This testsuite is for testing the Boot Device Functions
Set the Boot Device as Default using REST API :: This testcase is ...
Response code:200, Content:{
"data": null,
"message": "200 OK",
"status": "ok"
}
Response code:200, Content:{
"data": "Default",
"message": "200 OK",
"status": "ok"
}

PASS

Set the Boot Device as Default using ipmitool ::

Response code:200, Content:{

"data": "Default",

"message": "200 OK",

"status": "ok"

}

PASS


Html block contains raw HTML code

Everything within a Html block is assumed to be raw HTML.
Because of the implementation, pod6 syntax will be removed, only its raw text remind. That is, C<code> -> code., =item2 something -> something
To write C<> within Html block, you can use C&<&>(because we unescape after generate from Html block, but why?)
To mix up pod6 and HTML, you can separate them into different blocks. See the example below:
=begin Html
111
=end Html

=begin code
  =begin code
  =end code
=end code

=begin Html
222
=end Html

@coke is this what you want?
@gfldex anything unhandled?
Anyway, if the code inside is assumed to be HTML, why should we unescape after generate?


feat: commando connector

Fixes #1390
Commando is implemented through the lnmessage library, thanks to @aaronbarnardsound. This library uses a websocket proxy (lnproxy.getalby.com) to communicate with a remote CLN node over the p2p port.
Features out of scope for this PR (but coming later):

Tor support
WebLN support for arbitrary CLN (+plugin) RPC calls
Finer grained permissions for WebLN calls
Stream network gossip to website over WebLN
I'm probably forgetting more awesome stuff

To test:

download and install the development build of this PR
Add a new connector, pick Core Lightning.
Go to here for the connection details of our testnet CLN node, or connect your own (mainnet or testnet) node.
Fill in the connection details
Try to spend and receive some sats on testnet.

bumi noticed: package-lock.json can be removed. We use yarn and yarn.lock.

Boostagrams are currently not supported. As pointed out by Aaron over e-mail:
Actually it looks like the extratlvs field was only merged in to master on the 22nd of September - https://github.com/ElementsProject/lightning/pull/5619

I just checked with the CoreLn team and they said that it is going in to the next release.

So you can test it by installing CoreLn from master rather than a tagged release for the moment.

Aaron

So if we want to test this, we have to wait for the next Core LN release or build from master.


The minimum version of Python to run the emulator

It would be nice to specify in the readme.md that at least Python 3.10 and above is required.

Fixed in https://github.com/grafalex82/ut88/commit/bed4cb7357c4b362c931b3850e8c8ccd76d9eb91


Apalache throws an IllegalArgumentException

Description

We provide to apalache a specification having many statements that build a role-based policy. The statements have all the same form:
PolicyNo == /\ MEMBERS \subseteq {"m0","m1", ...}
/\ ROLE = "RoleNo"
/\ PERMISSIONS \subseteq {"p0","p1",...}
/\ access' = "granted"
When trying to verify a temporal property, Apalache throws a "java.lang.IllegalArgumentException: The argument region 436:1-436:49 intersects with 436:9-436:49" exception. This is a behaviour we encounter when we increase the number of statements (Policy##) from 82 to 83; i.e., with 82 policy statements, it works as anticipated.
The specification is made available below, but removed a few statements at the end to submit it here (restriction of no of characters). Shared the remaining statements in a next comment.

Omitted the remaining due to a error on submitting this: body is too long (maximum is 65536 characters).

Init == access = "denied"
Next == \/ Policy0 \/ Policy1 \/ Policy2 \/ Policy3 \/ Policy4 \/ Policy5 \/ Policy6 \/ Policy7 \/ Policy8 \/ Policy9 \/ Policy10 \/ Policy11 \/ Policy12 \/ Policy13 \/ Policy14 \/ Policy15 \/ Policy16 \/ Policy17 \/ Policy18 \/ Policy19 \/ Policy20 \/ Policy21 \/ Policy22 \/ Policy23 \/ Policy24 \/ Policy25 \/ Policy26 \/ Policy27 \/ Policy28 \/ Policy29 \/ Policy30 \/ Policy31 \/ Policy32 \/ Policy33 \/ Policy34 \/ Policy35 \/ Policy36 \/ Policy37 \/ Policy38 \/ Policy39 \/ Policy40 \/ Policy41 \/ Policy42 \/ Policy43 \/ Policy44 \/ Policy45 \/ Policy46 \/ Policy47 \/ Policy48 \/ Policy49 \/ Policy50 \/ Policy51 \/ Policy52 \/ Policy53 \/ Policy54 \/ Policy55 \/ Policy56 \/ Policy57 \/ Policy58 \/ Policy59 \/ Policy60 \/ Policy61 \/ Policy62 \/ Policy63 \/ Policy64 \/ Policy65 \/ Policy66 \/ Policy67 \/ Policy68 \/ Policy69 \/ Policy70 \/ Policy71 \/ Policy72 \/ Policy73 \/ Policy74 \/ Policy75 \/ Policy76 \/ Policy77 \/ Policy78 \/ Policy79 \/ Policy80 \/ Policy81 \/ Policy82 \/ Policy83
Spec == /\ Init /\ [][Next]_vars /\ WF_vars(Next)
Test == <> ( [](/\ MEMBERS = {"m0"} /\ ROLE = "r0" /\ PERMISSIONS = {"p0"}=> [](access = "granted")))

=============================================================================

The command line parameters used to run the tool

--config=Main.cfg

Main.cfg
SPECIFICATION
Spec
CONSTANT
MEMBERS = {"m0"}
ROLE = "r0"
PERMISSIONS = {"p0"}
PROPERTY
Test
CHECK_DEADLOCK FALSE
Expected behavior
 Receive a EXITCODE: OK. The specification is checked with TLC and works correctly.
Log files

```
2023-02-21T09:40:15,142 [main] INFO  a.f.a.t.Tool\$ - # APALACHE version: 0.30.1 | build: d447364
2023-02-21T09:40:15,181 [main] INFO  a.f.a.i.p.o.OptionGroup\$ -   > Main.cfg: Loading TLC configuration
2023-02-21T09:40:15,279 [main] WARN  a.f.a.i.t.TlcConfigParserApalache\$ - TLC config option CHECK_DEADLOCK true will be ignored
2023-02-21T09:40:15,287 [main] INFO  a.f.a.i.p.o.OptionGroup\$ -   > Using temporal predicate(s) Test from the TLC config
2023-02-21T09:40:15,288 [main] INFO  a.f.a.t.t.o.CheckCmd - Tuning: search.outputTraces=false
2023-02-21T09:40:15,617 [main] INFO  a.f.a.i.p.PassChainExecutor\$ - PASS #0: SanyParser
2023-02-21T09:40:17,182 [main] ERROR a.f.a.t.Tool\$ - Unhandled exception
java.lang.IllegalArgumentException: The argument region 436:1-436:49 intersects with 436:9-436:49
	at at.forsyte.apalache.tla.lir.src.RegionTree.locateAndAdd\$1(RegionTree.scala:39)
	at at.forsyte.apalache.tla.lir.src.RegionTree.add(RegionTree.scala:60)
	at at.forsyte.apalache.tla.imp.src.SourceStore.addRegion(SourceStore.scala:126)
	at at.forsyte.apalache.tla.imp.src.SourceStore.add(SourceStore.scala:93)
	at at.forsyte.apalache.tla.imp.OpDefTranslator.translate(OpDefTranslator.scala:75)
	at at.forsyte.apalache.tla.imp.ModuleTranslator.\$anonfun\$translate\$4(ModuleTranslator.scala:72)
	at at.forsyte.apalache.tla.imp.ModuleTranslator.\$anonfun\$translate\$4\$adapted(ModuleTranslator.scala:64)
	at scala.collection.immutable.List.foreach(List.scala:333)
	at at.forsyte.apalache.tla.imp.ModuleTranslator.translate(ModuleTranslator.scala:64)
	at at.forsyte.apalache.tla.imp.SanyImporter.\$anonfun\$loadFromFile\$1(SanyImporter.scala:108)
	at scala.collection.ArrayOps\$.foldLeft\$extension(ArrayOps.scala:782)
	at at.forsyte.apalache.tla.imp.SanyImporter.loadFromFile(SanyImporter.scala:106)
	at at.forsyte.apalache.tla.passes.imp.SanyParserPassImpl.loadFromTlaFile(SanyParserPassImpl.scala:65)
	at at.forsyte.apalache.tla.passes.imp.SanyParserPassImpl.\$anonfun\$loadFromTlaSource\$1(SanyParserPassImpl.scala:78)
	at at.forsyte.apalache.tla.passes.imp.SanyParserPassImpl.parseSource(SanyParserPassImpl.scala:121)
	at at.forsyte.apalache.tla.passes.imp.SanyParserPassImpl.execute(SanyParserPassImpl.scala:105)
	at at.forsyte.apalache.infra.passes.PassChainExecutor\$.exec(PassChainExecutor.scala:64)
	at at.forsyte.apalache.infra.passes.PassChainExecutor\$.\$anonfun\$runPassOnModule\$3(PassChainExecutor.scala:53)
	at scala.util.Either.flatMap(Either.scala:352)
	at at.forsyte.apalache.infra.passes.PassChainExecutor\$.\$anonfun\$runPassOnModule\$1(PassChainExecutor.scala:51)
	at scala.collection.LinearSeqOps.foldLeft(LinearSeq.scala:183)
	at scala.collection.LinearSeqOps.foldLeft\$(LinearSeq.scala:179)
	at scala.collection.immutable.List.foldLeft(List.scala:79)
	at at.forsyte.apalache.infra.passes.PassChainExecutor\$.runOnPasses(PassChainExecutor.scala:44)
	at at.forsyte.apalache.infra.passes.PassChainExecutor\$.run(PassChainExecutor.scala:34)
	at at.forsyte.apalache.tla.tooling.opt.CheckCmd.run(CheckCmd.scala:126)
	at at.forsyte.apalache.tla.Tool\$.runCommand(Tool.scala:138)
	at at.forsyte.apalache.tla.Tool\$.run(Tool.scala:118)
	at at.forsyte.apalache.tla.Tool\$.main(Tool.scala:40)
	at at.forsyte.apalache.tla.Tool.main(Tool.scala)
```

System information

Apalache version: 0.30.1 build d447364
OS: Mac OS X
JDK version: 19.0.1

Additional context

The exception appears to be raised in:
RegionTree.scala
def locateAndAdd(node: Node):
Triage checklist (for maintainers)

[x] Reproduce the bug on the main development branch.
[x] Add the issue to the apalache GitHub project.
[ ] If the bug is high impact, ensure someone available is assigned to fix it.

We have identified the root cause and working on a fix. It's in my old code that has been around for 4 years.

Thanks for the bug report @agouglidis!
We've just released v0.30.2 which fixes this issue.


Learning Path 7 - Lab 1 - Exercise 7 - Task 1: No results from WIN2

Contact Details
No response
What happened?
Description of issue: No results from WIN2
Repro steps:
Run the following KQL Statement again to recall the tables where we have this data:
search "temp\startup.bat"
Lab
Lab 07 Exercise 06 Create Detections
Relevant screenshots
paste here 😉
Do you want to help us? 👏

[ ] Create a Pull Requestt by following this project's Contribution Guide

Fixed by PR.


[Release 1.26] Integrate tailscale into k3s

Backport: https://github.com/k3s-io/k3s/issues/7353

Validated tailscale integration into k3s using commit id<PHONE_NUMBER>e1459aba5644fed2f4f241fad944a1 on release-1.26 branch
Environment Details
Infrastructure
Cloud EC2 instance
Node(s) CPU architecture, OS, and Version:
SLES15 SP4


Not working

It is failing the online test for reCAPTCHA 3 score, https://antcpt.com/eng/information/demo-form/recaptcha-3-test-score.html

I suggest you turn off fingerprint and turnstile plugins and try it.

The best I can get is 0.3 with this configuration :/

Hello, unfortunately it catches because of the CDP session. I will try to hide the CDP session. This error is something I have been investigating for a long time.

Hello, unfortunately it catches because of the CDP session. I will try to hide the CDP session. This error is something I have been investigating for a long time.

see https://github.com/kaliiiiiiiiii/brotector?tab=readme-ov-file#detections
workarounds can be

using a custom compilled chromium to patch that detection
make puppeteer not use Runtime.enable (will induce bugs, which have to be patched)

@ibrahimmus You can create and use the scanner with the scanner creation code in the file below. Recaptcha score is very good. Soon the library will initialize the scanner as in the file below.
https://github.com/zfcsoftware/cf-clearance-scraper/blob/main/module/browser.js

The library has been updated and this problem has been solved. It now gets 0.9 points.


[DO NOT MERGE Update tabs design exploration]

Design 1
Desktop

Mobile

Design 2
Desktop

Mobile

Design 3
Desktop

Mobile

For what it's worth, I like the second design the most :D
Open this PR up, if you'd like it to act on it :) I wasn't sure what to do on it :D

For what it's worth, I like the second design the most :D
Open this PR up, if you'd like it to act on it :) I wasn't sure what to do on it :D


Add xibalba and small fixes

The system font was nearly transparent on my setup, added Xibalba

Black doesn't work for me:

White:

Maybe taking another font may help ?


Code base structure and documentation

The codebase structure is complex and becomes a barrier to maintenance:

Directories sdk, test-collateral and *-test contain a mix of code and artefact.
There is no clear sign of examples and dev-tool, and the readme is not very helpful.
more readable policy file.
Complicated Error enum.
Large cargo dependency in certain components.

#487 #489 #490 #491 #493


make it so that when one clones the repo, (s)he does not get 1 GB of stuff, including any atlases, etc.

agreed!
Best,
Will
On Tue, Feb 17, 2015 at 1:33 PM, joshua vogelstein<EMAIL_ADDRESS>
wrote:

—
Reply to this email directly or view it on GitHub
https://github.com/openconnectome/m2g/issues/34.


Add Chocolatey support

Chocokatey is the most popular package manager for windows

Discussed in #56.
I want to have WingetUI in a more stable, mature state before adding other package-managers.

Hi, the first beta with chocolatey support has been released.
WingetUI 1.6.0 beta: https://github.com/marticliment/WingetUI/releases/tag/1.6.0-beta1


Attempting to run pier list segfaults straight away

Hello,
Unfortunately, when I attempt to run pier list it simply segfaults:
zsh ❯ pier list
[1]    503177 segmentation fault (core dumped)  pier list

From syslog:
2024-01-20T10:45:50.051578-06:00 mosthated-pc kernel: [ 3786.184976] pier[503177]: segfault at 89 ip 0000561acae62840 sp 00007ffd0699a570 error 4 in pier[561acae22000+ea000] likely on CPU 19 (core 3, socket 0)
2024-01-20T10:45:50.051588-06:00 mosthated-pc kernel: [ 3786.184985] Code: 73 08 31 c9 45 31 d2 eb 46 90 49 89 d0 49 83 e0 fc 4c 8d 8e 10 01 00 00 31 c9 45 31 d2 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 <49> 03 89 28 ff ff ff 49 03 89 70 ff ff ff 49 03 49 b8 49 03 09 49

I only just installed it and attempted to run pier config-init then was trying other commands, one being list which lead the the segfault.
I checked my config and there was not an interpreter, so I set it and my config looks like this:
[scripts.hello-pier]
alias = 'hello-pier'
command = 'echo Hello, Pier!'
description = 'This is an example command.'

[default]
interpreter = ["/bin/bash", "-c"]

System Details
OS: Ubuntu 23.10 x86_64
Host: X670E Taichi
Kernel: 6.5.0-14-generic
Uptime: 1 hour, 9 mins
Packages: 3591 (dpkg), 73 (flatpak), 27 (snap)
Shell: zsh 5.9
Resolution: 2560x1080
DE: GNOME 45.2
WM: Mutter
WM Theme: Adwaita
Theme: Yaru-dark [GTK2/3]
Icons: Yaru [GTK2/3]
Terminal: alacritty
CPU: AMD Ryzen 9 7950X (32) @ 5.881GHz
GPU: AMD ATI Radeon RX 6800/6800 XT / 6900 XT
GPU: AMD ATI 5a:00.0 Raphael
Memory: 13501MiB / 63398MiB

@MostHated Thanks for picking this up. I can confirm I recreated this error on my own machine, a Mac M1—so it's likely not system specific. If you've managed to fix this in the meantime, please let me know, otherwise I'll look into it.

@BenSchZA I've raised a PR to resolve this issue 😁 , can you please review and merge it?


responsive CSS fix

Hi, your player is great, thank you! I found a syntax error that breaks some of the responsive CSS. This tiny edit -- adding a single semicolon to one line of CSS -- fixes the problem. Thank you for considering this pull request.

Published in v2.11.1


Simplify review UI

Instead of always displaying all available actions as buttons, merge them into a single dropdown menu, same as GitHub. That decreases visual overload and is more mobile-friendly, while not losing any functionality.
Screenshots
Before

After (unexpanded)

After (expanded)

Sidenote: I didn't even know we had an edit file button already.
For some reason, it was never shown…
All I did was move the code and add the item class and surrounding menu.

Sidenote: I didn't even know we had an edit file button already. For some reason, it was never shown… All I did was move the code and add the item class and surrounding menu.

It's a new feature of v1.22, I would like to have a delete file and rename file in v1.23

Need to fix some bugs:  #32631

The menu would go behind the sticky header
The menu doesn't get initialized when "load more files"


Homie Configurator didn't go to next step

Homie configurator did not go to next step, when I checked "Use MQTT authentication".
But, if not checked, can go to next step. I tested Web UI and app, and result is same.
I couldn't find any issues about.  Now I'm testing with release 2.0.0 and using CloudMQTT broker.

So I trying to debug using Chrome on PC, there are some errors below when pushed next button.

It should be fixed now. Can you try again?

Thanks Marvin.
It works good. But there are problem " Invalid or too big JSON" in serial monitor.  It seems same second issue in #178..
Below is capture of structure of data.

Can you try with the latest git?

Hi Marvin
It work good without any error. But my device did not work normally.
It repeat endlessly to connect MQTT and disconnect MQTT.

The reason of repetition is I have a another device using same Device Id.  So MQTT is disconnected and Homie trying to reconnect.

Great!

double confirmed that it works :) thanks for your effort on all! I'm just starting to learn the capabilities of an ESP8266 with your stuff!


Add-VSTeamBuild queues a build, but throws an error post-queue

Steps to reproduce
$build = Add-VSTeamBuild -ProjectName Core -BuildDefinitionName $buildDefinition -BuildParameters $buildParameters -SourceBranch master

Expected behavior
Build queued and information returned
Actual behavior
Queued, but with following exception:
The property 'name' cannot be found on this object. Verify that the property exists.
At C:\Program Files\WindowsPowerShell\Modules\VSTeam\6.4.6\vsteam.classes.ps1:313 char:47
+    ) : base($obj.name, $obj.id, $Projectname) {
+                                               ~
    + CategoryInfo          : NotSpecified: (:) [], PropertyNotFoundException
    + FullyQualifiedErrorId : PropertyNotFoundStrict

The property 'name' cannot be found on this object. Verify that the property exists.
At C:\Program Files\WindowsPowerShell\Modules\VSTeam\6.4.6\vsteam.classes.ps1:313 char:47
+    ) : base($obj.name, $obj.id, $Projectname) {
+                                               ~
    + CategoryInfo          : NotSpecified: (:) [], PropertyNotFoundException
    + FullyQualifiedErrorId : PropertyNotFoundStrict

Environment data
OS

[ ] macOS
[X] Windows
[ ] Linux

Server

[ ] TFS 2017
[ ] TFS 2018
[ ] Azure DevOps Server
[X] Azure DevOps Service

> Get-VSTeamAPIVersion
Name                           Value
----                           -----
Release                        5.1-preview
Version                        VSTS
MemberEntitlementManagement    5.1-preview
TaskGroups                     5.1-preview.1
DistributedTask                5.0-preview
Core                           5.0
Packaging                      5.1-preview
ServiceFabricEndpoint          5.0-preview
VariableGroups                 5.0-preview.1
Build                          5.1-preview
Git                            5.1-preview
ExtensionsManagement           5.1-preview
Graph                          5.1-preview
Tfvc                           5.0

> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      5.1.19041.1
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.19041.1
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

Thanks @richardgavel . We gonna check this in time. Are you using YAML pipeline or the classic build pipelines?

Raw powershell command line, not even inside a pipeline yet.
On Thu, Apr 23, 2020, 12:34 AM Sebastian Schütze<EMAIL_ADDRESS>wrote:

Thanks @richardgavel https://github.com/richardgavel . We gonna check
this in time. Are you using YAML pipeline or the classic build pipelines?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/DarqueWarrior/vsteam/issues/291#issuecomment-618188260,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA5SUDZLJ3JI5QX27MMTLXLRN7HPBANCNFSM4MOQNONQ
.

Did some more research via logging and it's actual the result of the issue https://github.com/DarqueWarrior/vsteam/issues/198. So closing this and will help out on that one.

Thanks for checking it yourself. We are maintaining this module in our limited free time that we have. So if you think you know a fix, then you can always suggest fixing snippets in the issue or submit a PR. Thanks for your effort!


virtcontainers: network: Simplify the network into a class

Following the #568 from @amshinde, I don't think there is any reason to have several implementations of network. From a Kata API perspective, we know we will receive some info about the network through the PodConfig. And then from there, we will scan the network namespace if one is provided, and go on with the action that we're already doing to create the connection between host and VM.
I think this should be part of another decision, that is moving the OCI hooks out of the Kata API. This way, we would first handle the OCI hooks from the CLI layer only, and the Kata API would stay OCI agnostic (thing that is not true currently).
Without the hooks, the removal of the network interface replaced with a simple network class should be feasible and would make sense IMO.

Closing this one as I have changed my mind. We should have only one real implementation, but keeping network as an interface makes it easier for unit testing (relying on noopNetwork).


Pub serve always builds/hosts all possible targets in a project

This issue was originally filed by<EMAIL_ADDRESS>
What steps will reproduce the problem?

Create a project with multiple entry points
Run your app
Pub serve will host multiple IPs with different ports

What is the expected output? What do you see instead?
In my case, I have the main target, and some unit test targets.
Building/transforming/hosting all targets seems like overhead and slows down development workflow,
when I launch, I only want to launch one target at a time.
Please provide an option to set a 'main' target when launching for example.
What version of the product are you using? On what operating system?
SDK 1.5.xx
Windows 7

This issue has been moved to dart-lang/pub#1001.


Hide overflow on individual pages in tab view

cc @grabbou

Hi, when this PR will be implemented? is kind of weird that shadow...

Is there any news on this ? When will it be deployed ?

for the record, it has been deployed as of https://github.com/react-community/react-navigation/releases/tag/v1.0.0-beta.10

I am using beta 10 but this issue is not fixed

My setup is as follows:
Host StackNavigator
  TabNavigator
    StackNavigator A
    StackNavigator B
    StackNavigator C
    StackNavigator D

the TabNavigator is set to lazy=true. When I first launch, the shadow is not present. The shadow appears only on screens whose nearest neighbor to the right has been loaded. If i switch to StackNavigator B (therefore loading that component) then there is a shadow only on StackNavigator A. There is never a shadow on StackNavigator D.


Apply Rails practices for performance optimization

Part of https://github.com/bigbinary/neeto-engineering-web/issues/943

0.25D _t neeto-engineering _t

No issues were found.


STORM-2018: Supervisor V2

Still need to do some more manual testing but the unit tests passed for me.

I ran the same set of manual tests as before, but I now want to wait on #1699 to go into master, and then I will pull it in here.  We are in the process of rolling essentially what is this same patch out to staging at Yahoo, and plan to roll it out to production shortly too.  If others are feeling uncomfortable about merging this into the 1.x line I am happy to wait until we have it in production.

We also found #1700 so once that goes in I'll pull it in here too.

Still have #1699 and #1712 to backport before this is ready

@revans2 Relevant PRs (#1699 #1700 #1705 #1712) are all merged to master. Please pull them here.

Just pulled in the latest set of bug fixes from master.  All known issues have been addressed and we have been running in staging with various versions of this patch for over a week now.  Expect to roll out to production fairly soon.

The test failures look unrelated.  Some are rat failures caused by test logs not being excluded.

I just cherry-picked commit which excludes logs from RAT. It's merged to master but was part of port work so didn't port back.

While running build in storm-core I found that null/storm-local directory is created in storm-core. Maybe there's a case base path is set to null.

I found two issues, but other than that manual tests passed. Code review is already done from PR for master branch. +1 once these are resolved.

@revans2
It would be better to address STORM-2131 here as well. Please pull #1724 here.
And could you update the pull request according to the review comments? Supervisor V2 is the one I would want to include to 1.1.0.
Thanks in advance.

@revans2 Do you have any updates on this? I'm occasionally seeing Supervisor failures so would like to get this merged to 1.x, and even 1.0.x.

@HeartSaVioR Sorry this has taken so long.  I am going to upmerge this and pull in #1724 next.

Just pushed the upmerged code.  Will look into pulling in #1724 too.

Merged in #1724 now too (it was a trivial cherry pick).
@HeartSaVioR if you want to take a look this should be good for merging in.
Just as an FYI we have been running with a version of this in production for a little while now with no real issues.
Once this goes in if you want me to I can take a look at pulling it back to 1.0.x too.

@revans2 Shouldn't healthcheck.clj be deleted? At least for me HealthCheck.java clashes with healthcheck.clj. I can't clearly say why, might be specific issue with OSX, but anyway there's an issue. I left a comment regarding this.

@HeartSaVioR good catch, I thought I had deleted it.

I seem to be getting a few new errors when running some of our own unit tests with this branch. The exceptions are intermittent.
java.lang.NullPointerException
	at org.apache.storm.utils.DisruptorQueue$FlusherPool.stop(DisruptorQueue.java:110)
	at org.apache.storm.utils.DisruptorQueue$Flusher.close(DisruptorQueue.java:293)
	at org.apache.storm.utils.DisruptorQueue.haltWithInterrupt(DisruptorQueue.java:410)
	at org.apache.storm.disruptor$halt_with_interrupt_BANG_.invoke(disruptor.clj:77)
	at org.apache.storm.daemon.executor$mk_executor$reify__4923.shutdown(executor.clj:412)
	at sun.reflect.GeneratedMethodAccessor303.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:93)
	at clojure.lang.Reflector.invokeNoArgInstanceMember(Reflector.java:313)
	at org.apache.storm.daemon.worker$fn__5550$exec_fn__1372__auto__$reify__5552$shutdown_STAR___5572.invoke(worker.clj:668)
	at org.apache.storm.daemon.worker$fn__5550$exec_fn__1372__auto__$reify$reify__5598.shutdown(worker.clj:706)
	at org.apache.storm.ProcessSimulator.killProcess(ProcessSimulator.java:66)
	at org.apache.storm.ProcessSimulator.killAllProcesses(ProcessSimulator.java:79)
	at org.apache.storm.testing$kill_local_storm_cluster.invoke(testing.clj:207)
	at org.apache.storm.testing4j$_withLocalCluster.invoke(testing4j.clj:93)
	at org.apache.storm.Testing.withLocalCluster(Unknown Source)

and this kind of error
java.lang.IllegalStateException: Timer is not active
	at org.apache.storm.timer$check_active_BANG_.invoke(timer.clj:87)
	at org.apache.storm.timer$cancel_timer.invoke(timer.clj:120)
	at org.apache.storm.daemon.worker$fn__5550$exec_fn__1372__auto__$reify__5552$shutdown_STAR___5572.invoke(worker.clj:682)
	at org.apache.storm.daemon.worker$fn__5550$exec_fn__1372__auto__$reify$reify__5598.shutdown(worker.clj:706)
	at org.apache.storm.ProcessSimulator.killProcess(ProcessSimulator.java:66)
	at org.apache.storm.ProcessSimulator.killAllProcesses(ProcessSimulator.java:79)
	at org.apache.storm.testing$kill_local_storm_cluster.invoke(testing.clj:207)
	at org.apache.storm.testing4j$_withLocalCluster.invoke(testing4j.clj:93)
	at org.apache.storm.Testing.withLocalCluster(Unknown Source)

Our tests are running Storm in local mode with no time simulation. I've tried running the same tests on 1.x-branch, and these don't seem to occur there.

OK so going through the code in both cases it looks like the only way that can happen is if the workers is somehow being shut down multiple times.  My guess is that because the slots are on different threads there is a race now between shutting down a worker through the slot and shutting down the worker through the cluster shutting down.
I'll look into reproducing it.  @srdo is there any way you can share your test case with us?  It would make my job a lot simpler of trying to reproduce and fix it.

@revans2 @srdo
I'm even OK if we file an issue regarding intermittent race condition for local cluster and merge this now, since the race condition of Supervisor in 1.x is much critical. It even occurs on clustered environment.

@revans2 I can't share our actual test code since it depends on pretty large chunks of our codebase. I'll try reproducing with an example topology.
I'd be fine with filing a separate issue to fix the race so this PR isn't blocked.

@srdo sounds good.  I filed https://issues.apache.org/jira/browse/STORM-2175 to address the race condition.

OK. Unit and integration tests, and manual tests passed on recent commits.
I'm +1 and will merge this now since there's no more reviewer and this was open for fairly long, more than 1 month despite it's kind: backport.
Thanks for the amazing work.
Btw, I'm in favor of just having 1.1.0, not having 1.0.3 unless there's specific request on it. If you  would be OK to port back on demand, we could skip it.


Possible feature flaw about the call history page

@zyng233 not sure if they will count this as a feature flaw for your feature but
you might want to check which screen they are on to allow/disallow certain commands
ie. if they are on the history 2 screen, you might want to disable the mark by index command?
up for discussion

ok, I will disable the commands that will modify data (e.g. delete, edit, mark) if user is in the history view. So that user has to navigate back to the person list before modifying the data.


Rust: Streamline deserialization/validation of endpoint secrets

I've re-tooled deserialization and validation per comments and other discussion.


Add in check if game is running

Fixes #714
Attempts to add in a check for if the game is running before closing the client currently an alert pops up but the window closes anyway

@micheljung I am trying to add in the check for if FA is still running before closing the client however a closerequest event never gets sent so that event handler cannot be used. Currently it uses onHiding as the event to pick up on however there is no way to stop the window from being hidden. From looking at the code it might be best to implement something in the windowController or override its onCloseClicked method however the windowController is defined in your fxStage and wanted to know if you had any ideas and if we should implement our own windowFXML as there is an option to specify the fxml used.

anything to do here?

Remember me if CI ran through

CI passed


Ferdi 5.6.0-nightly.15 doesnt load Google Hangouts

Bug description:

Google probably changed something in Google Hangouts, because it gets stuck on welcome screen and doesnt switch to chats. Works fine on desktop browser.
Steps to reproduce:

load Hangouts
you get stuck on Hi, Username! screen, no chats are loading.

Expected behavior

After loading Hangouts and welcome screen it should switch to chat list on left side and chat window on right.
Screenshots

Environment:

Operating System: Windows 10 with all latest updates

Ferdi Version: 5.6.0-nightly.15

Server: Ferdi

Debug information:

{"host":{"platform":"win32","release":"10.0.19042","screens":[{"id":2528732444,"bounds":{"x":0,"y":0,"width":2560,"height":1440},"workArea":{"x":0,"y":0,"width":2560,"height":1400},"accelerometerSupport":"unknown","monochrome":false,"colorDepth":24,"colorSpace":"{primaries_d50_referred: [[0.6544, 0.3330],  [0.3047, 0.6260],  [0.1455, 0.0469]], transfer:IEC61966_2_1, matrix:RGB, range:FULL}","depthPerComponent":8,"size":{"width":2560,"height":1440},"workAreaSize":{"width":2560,"height":1400},"scaleFactor":1,"rotation":0,"internal":false,"touchSupport":"unknown"},{"id":2779098405,"bounds":{"x":2560,"y":-57,"width":1200,"height":1600},"workArea":{"x":2560,"y":-57,"width":1200,"height":1560},"accelerometerSupport":"unknown","monochrome":false,"colorDepth":24,"colorSpace":"{primaries_d50_referred: [[0.6526, 0.3252],  [0.3303, 0.5945],  [0.1482, 0.0772]], transfer:IEC61966_2_1, matrix:RGB, range:FULL}","depthPerComponent":8,"size":{"width":1200,"height":1600},"workAreaSize":{"width":1200,"height":1560},"scaleFactor":1,"rotation":90,"internal":false,"touchSupport":"unknown"}]},"ferdi":{"version":"5.6.0-nightly.15","electron":"9.4.0","installedRecipes":[{"id":"discord","version":"1.1.3"},{"id":"hangouts","version":"1.0.4"},{"id":"icq","version":"1.0.1"},{"id":"messenger","version":"1.1.0"},{"id":"skype","version":"2.1.0"},{"id":"slack","version":"1.0.16"},{"id":"telegram","version":"3.0.0"},{"id":"whatsapp","version":"2.0.8"},{}],"devRecipes":[],"services":[{"id":"690323bc-ee45-47eb-8501-85eefa332838","recipe":"whatsapp","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"8a4704f3-080f-401b-a33a-d75caaeb0800","recipe":"messenger","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"533acb65-6254-4c54-b291-b827d0f0de18","recipe":"hangouts","isAttached":true,"isActive":true,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"441340fc-da40-41e1-8c86-474a63fae38a","recipe":"slack","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"4dc69a82-4c45-4d86-b337-d7c1e8e3179d","recipe":"icq","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"2d61354b-9797-42ed-8640-467ce405e4cd","recipe":"skype","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"a27abadd-bcb9-447a-b31d-d6490a9a72cd","recipe":"telegram","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true},{"id":"d35d70b6-c022-4a8a-9234-8be703fafed4","recipe":"discord","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":true}],"messages":[{"type":"error","request":{"result":null,"wasExecuted":true,"method":"getInfo"},"error":{},"response":{},"server":"https://api.getferdi.com"},{"type":"error","request":{"result":null,"wasExecuted":true,"method":"features"},"error":{},"response":{},"server":"https://api.getferdi.com"},{"type":"error","request":{"result":null,"wasExecuted":true,"method":"all"},"error":{},"response":{},"server":"https://api.getferdi.com"}],"workspaces":[],"windowSettings":{"width":1079,"height":813,"x":2659,"y":457,"isMaximized":true,"isFullScreen":false,"displayBounds":{"x":2560,"y":-57,"width":1200,"height":1600}},"settings":{"autoLaunchInBackground":false,"runInBackground":true,"reloadAfterResume":true,"enableSystemTray":true,"startMinimized":true,"minimizeToSystemTray":true,"closeToSystemTray":false,"privateNotifications":true,"notifyTaskBarOnMessage":false,"showDisabledServices":true,"showMessageBadgeWhenMuted":true,"showDragArea":false,"enableSpellchecking":true,"spellcheckerLanguage":""\"\\\"\\\\\\\"\\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\"en-us\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\"\\\\\\\"\\\"\""","darkMode":true,"locale":"en-US","fallbackLocale":"en-US","beta":true,"isAppMuted":true,"enableGPUAcceleration":true,"serviceLimit":5,"server":"https://api.getferdi.com","predefinedTodoServer":"https://app.franztodos.com","autohideMenuBar":false,"lockingFeatureEnabled":false,"locked":false,"lockedPassword":"******","useTouchIdToUnlock":true,"scheduledDNDEnabled":false,"scheduledDNDStart":"17:00","scheduledDNDEnd":"09:00","hibernate":false,"hibernateOnStartup":true,"hibernationStrategy":300,"inactivityLock":0,"automaticUpdates":true,"showServiceNavigationBar":false,"universalDarkMode":false,"adaptableDarkMode":false,"accentColor":"#7367f0","serviceRibbonWidth":68,"iconSize":20,"sentry":false,"nightly":true,"navigationBarBehaviour":"never","useVerticalStyle":false,"alwaysShowWorkspaces":false,"todoServer":"isUsingCustomTodoService","customTodoServer":""},"features":{"isSpellcheckerIncludedInCurrentPlan":true,"needToWaitToProceed":false,"needToWaitToProceedConfig":{"delayOffset":3600000,"wait":10000},"isServiceProxyEnabled":true,"isServiceProxyIncludedInCurrentPlan":true,"isAnnouncementsEnabled":true,"isWorkspaceIncludedInCurrentPlan":true,"isWorkspaceEnabled":true,"isCommunityRecipesIncludedInCurrentPlan":true,"isSpellcheckerPremiumFeature":false,"isServiceProxyPremiumFeature":true,"isWorkspacePremiumFeature":false,"isSettingsWSEnabled":false,"isServiceLimitEnabled":false,"serviceLimitCount":0,"isCommunityRecipesPremiumFeature":false,"isCustomUrlIncludedInCurrentPlan":true,"isMagicBarEnabled":true,"isTeamManagementIncludedInCurrentPlan":true,"isTodosEnabled":true,"isTodosIncludedInCurrentPlan":true,"defaultTrialPlan":"franz-pro-yearly","subscribeURL":"https://getferdi.com","planSelectionURL":"https://getferdi.com","hasInlineCheckout":true,"isPlanSelectionEnabled":false,"isTrialStatusBarEnabled":false,"canSkipTrial":true,"pricingConfig":{"currency":"$","currencyID":"USD","plans":{"personal":{"monthly":{"id":"ferdi-free","price":0,"billed":0},"yearly":{"id":"ferdi-completely-free","price":0,"billed":0}},"pro":{"monthly":{"id":"ferdi-still-free","price":0,"billed":0},"yearly":{"id":"ferdi-forever-free","price":0,"billed":0}}}}},"user":"82c1cf9d-ab58-4da2-b55e-aaa41d2142d8"}}

I am experiencing this issue as well. I am still running 5.6.0-beta.5.2741 and it quit working in the past day or two.

probably related to #1276

I see this too. Tried to delete and readd the service. But now after the login the site is stuck in a reload loop

I have this same issue. I switched over to Google Hangouts Chat (since that has been opened up for standard gmail accounts) and that is working for now.

I can confirm "Hangouts Chat" works for me as well

Can you please try the steps that I have outlined here please? and report back whether replacing the recipe files did the trick?

Closing this since the latest nightlies have updated recipes and its working.


If file is too large it shouldn't try to upload it

If I add a file larger the limit (4 MB), it is added to the list.
Could it maybe just ignore too large files, when you click "Begin Upload" or remove the files for you? And maybe disable the button if all files are too large for upload?
v. 0.2.1

ohh, I then noticed that the upload icon have a higher z-index than the text it self.

Yes of course! The files should not get queued. It might be a new thing due to my latest changes. Thanks for letting me know :)

Should be fixed :)

I see this issue in v. 0.3.1 too :)


Add CompositeRecordBuilder example

I know it's been years but eta?

I know it's been years but eta?

Never mind, my use-case is many output data rows for a single input


Bug that causes the first scene init to not work.

For some reason, when I play test my game, it somehow causes the first scene init code to not work.

I use windows 10 to code and play test.

Attaching the project that is causing the issue: themagicpencil.zip

I'm struggling to reproduce this issue, I've tried both Mac and Windows 10, the release version of 1.2.0 and the dev build 1.2.1-beta1 on both but using the project that @pau-tomas attached it seems to work as expected. Attached a screen recording of what happens when opening that project file and running on Windows 10 for me.
@pau-tomas does the project you attached fail for you in the same way? Wondering how I can reproduce this.

I haven't been able to reproduce on Mac either. I don't have access to Windows machine. The project was shared by @bigjawed on Discord. I wonder if it's related to 32 or 64 bits builds specifically?

This issue is a random intermittent fault, where a scene init doesn't fire, or something random like an emote happens on scene start, around a 1 in 20 chance, windows 10, usually in live development sessions where i'm re testing a scene frequently.
It's the worst kind of issue to fix, but i've just had it happen 4 times out of about 30 simple scene tests, seems like it's jumping to a random bank at the start and running that, but only sometimes...
Are the roms from testing stored somewhere so i can rip a copy when a bad build happens again? like now where i got a full game crash?

Here we go! found it in C:\tmp\18c3a1b6-00c9-4c62-92cf-fb40af88af59\build\web\rom (only when using dev builds.
This is my own project, built 2 times, one working, one not. and the project file.
BadBuilds.zip
Gotta compare it in a hex editor

@RichardULZ that’s exactly what’s happening. The first scene init doesn’t activate sometimes.

Thanks @RichardULZ that's really useful. I've put those two ROMs into Hex Fiend, there's only a few very small hex differences.

I believe this is the header checksum value so it's only different because of the other changes.

This appears to be the main change, not figured out which part of the game this corresponds to yet though.

This is just removing the extra empty data from the added part in 2.

Annoyingly if I build on a Mac there's a very large number of small hex differences so I can't easily test this myself right now but I'm assuming given the address location that it's in bank 1, meaning it's in the engine itself. My immediate thought would be an issue with some of the code that modifies the engine before build
https://github.com/chrismaltby/gb-studio/blob/1d1d5ca7f966f46e1d9684406f466727e01f5d3d/src/lib/compiler/makeBuild.js#L100-L116
or
https://github.com/chrismaltby/gb-studio/blob/1d1d5ca7f966f46e1d9684406f466727e01f5d3d/src/lib/compiler/compileData.js#L355-L383
When I get access to Windows again (my PC is boxed away while I'm moving flat right now!) I might try making small changes to these parts and seeing which sections of the ROM get modified, it might help narrow down the issue.

Another update from investigating, I found this disassembler https://github.com/mattcurrie/mgbdis which I ran both of your ROMs though @RichardULZ

The only diff (other than the checksum) is this, an extra ld no idea whats causing this yet but getting closer.
I've attached the assembly of the only files that differ.
bank_000_bad.asm.txt
bank_000_good.asm.txt

It gets even weirder the missing $c24c seems to refer to the value of emote_timer value set in Scene_b.c https://github.com/chrismaltby/gb-studio/blob/2965819a45f052b78bec2f3e710da8db96824d44/appData/src/gb/src/Scene_b.c#L40
I found that in the .sym and .map files that get generated with the ROM and looking at the other ld commands around those lines seem to match up
./build/rom/game.sym:00:C24D _emote_timer
./build/rom/game.map:		_emote_timer	C24D

Don't see any reason right now why that line would be missing from a build.
Is the Windows GBDK compiler nondeterministic? :-/

It gets even weirder the missing $c24c seems to refer to the value of emote_type value set in Scene_b.c
https://github.com/chrismaltby/gb-studio/blob/2965819a45f052b78bec2f3e710da8db96824d44/appData/src/gb/src/Scene_b.c#L39
I found that in the .sym and .map files that get generated with the ROM and looking at the other ld commands around those lines seem to match up
./build/rom/game.sym:00:C24C _emote_type
./build/rom/game.map:		_emote_type	C24C

Don't see any reason right now why that line would be missing from a build.
Is the Windows GBDK compiler nondeterministic? :-/

What an insane bug, I'll try to run a few more compiles, perhaps even good builds have subtle differences...
Uh, well these good build are different now with a new dev session, perhaps i modified the project accidentally?
The compiles have been identical for 8 runs, and now i have another bad build 9, and then a good build 10, that has differences.. and then a good build that's identical again 11.
Next time i find a bad build i might dump the whole working folder.
9-01-2020_b11_GoodBuild game.zip

Alright get ready to scream!
Here's a bunch of builds with the full working folder, i haven't looked through the actual differences yet, but there are a few types, one Bad build where an emote pops up, and a few different versions of Good Roms...
I used WinMerge to test for binary/text differences and decide if i should copy them, but didn't realize sdcc puts in a timestamp, so i copied a lot of them then skipped through until a visible bug showed up (the dreaded emote, it just mocks you, then runs like any other build).
Can't rule that out as a possibility though... timestamps and that they also have different NAME lcc148360 each time you generate.
BuildDumps15-25.zip

From those test builds, it seems to be missing commands like ld hl,#_emote_actor, ld hl,#_text_out_speed, and ld hl,#_menu_index despite having references to these as normal later on.
I expect all of these cause a subtle issue even in good builds, but the one most noticeable/severe seem to relate with ld hl,#_emote_actor.
GoodC19 with Bad25, emote actor issue that's noticeable at start.

GoodC19 with Bad25, signs that a menu event might fail on this bad build too?

GoodC19 with GoodB18, signs that even on this normal build you may have issues with text box closing speed?

The src files are identical, so it must be lcc messing something up.
Now, i have no idea how sdcc and lcc work, but we can either figure out how to fix/update it in gbdk, may need @gregtour 's help,
or run a brutal after check on the tmp files in obj for the right number of ld hl,#_ links in each file against a known good, then error/retry many times until it's perfect... the boggle sort way.
Possibly both.

Here's a zip with gbdk and a project for testing, perhaps in a virtual machine, just press make.bat and if you're lucky, it'll make different files in /obj/ 😅
Win64GBDK_testbed.zip
If you get a copy of WinMerge https://winmerge.org/, you can compare the insides with a copy of the project quickly.
F5 to refresh, and add the Differences display column by customizing columns, if it's over 2 differences (time and lcc numb), you have a bug, double click to open the text compare view to see what's changed.
Might be nice to compare against how mac / linux create their files too, since they seem different.

Nice one, thanks for investigating further into this. Still in the middle of moving (made it to the other flat at least) so I’ll probably be quiet for a while as I’m getting settled but this seems really helpful!
I wonder if there’s any chance that the code that inserts the game name and patches the ROM after building is not writing the file correctly? I had a similar issue with project files corrupting on save that only affected Windows, might just be grasping at this point.
The other thing is I’ve got a web assembly port of GBDK that’s almost ready:
https://github.com/chrismaltby/gbdk-emscripten
This would mean the build process would be identical across all platforms, it’s a little slower than running natively but I could set it up to not recompile the engine each time. If I cached the built engine files all it really needs to do is recompile the data files each time and link everything.

Hi @RichardULZ If I'd have actually read your comments properly I'd have seen you're checking the .lst files which means it's definitely before the ROM patching happens.
So I did a bit more research and narrowed it down a little more. When you build the game it's using lcc to build the files but really that's mostly just a wrapper that calls sdcpp then sdcc then asgbz80 to build the .o files, then it links the files to build the ROM using linkgbz80. The issue seems to happen in sdcc so I've made a branch with a test script that runs sdcc on a number of files 100 times, strips out the timestamps and lists how many times the files differ. On Windows 10 64-bit I'm seeing around 5 to 10% of the engine file tests having these small errors (the data bank files always seem fine though interestingly). Running the same tests on macOS and Windows 7 32-bit (the only other Windows OS I have access to) always seems to work though.
You can run the tests by using the branch
https://github.com/chrismaltby/gb-studio/tree/test/sdcc-bug
and running
yarn
npm run test-sdcc-bug

Since it seems to work in 32-bit Windows I thought maybe the issue would be solved by using the 32-bit binaries on 64-bit Windows too but unfortunately that didn't help.
One thing that actually seems to potentially fix the issue is setting SDCC to run in Windows 8 compatibility mode

When I turn that on I'm unable to reproduce the bug with the test suite again but unfortunately it doesn't seem to actually make a change that I commit to git, not sure where those settings are stored or if there's a way to force Windows to run a binary in compatibility mode.

I might have fixed it! :-D
I found a way to set compatibility mode within a batch script by adding set __COMPAT_LAYER=WIN7RTM to the top of the file. I dropped this into the Windows build process in 314e67373a21cb57011a7172d0e7f1b774e70a26 and since then haven't been able to reproduce the issue in Windows 10. Hope I'm not speaking too soon.

I was thinking about trying that, lots of results were showing to edit the registry, but one or two suggested COMPAT_LAYER, Didn't have time to check it out at work, but testing now.
Zalo has some wizard stuff going on where it's running native Make commands through a make.exe app, and then through a much newer sdcc 3.80.

No issues so far! 🤞
I suppose if the command is not recognized on windows 7 it will continue as normal. Great job!
That's a lot of fixes piled up for 1.2.1

Excellent, I'll close this for now then. Yeah, I think this is the last fix for 1.2.1 now. I'll start getting it ready for release when I have a minute.

I might have fixed it! :-D
I found a way to set compatibility mode within a batch script by adding set __COMPAT_LAYER=WIN7RTM to the top of the file. I dropped this into the Windows build process in 314e673 and since then haven't been able to reproduce the issue in Windows 10. Hope I'm not speaking too soon.

Thank you so much. I hope this will come into 1.2.1


README & Features documents are out of date.

Problem Statement
README & Features markdown documents are out of date by a full release.
Proposed Solution
Update the README & Feature documents to match the work that has been done.
Environment

Keycloak Version: N/A
keycloak-config-cli Version: 4.6.1
Java Version: N/A

Additional information
No response
Acceptance Criteria

[] As a User, I should see the latest information in the README & features markdown files.

Hi,
looking at README: Can you explain what is out of date here?


Deprecate AbstractOptions

This type exposes a non-type-safe API and relies on reflection. It stands as a blocker to the provider API migration as this method cannot be migrated.
Fixes #26550
Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

@bot-gradle test this

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

Pull Request Feedback (Trigger) (Check)

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

Pull Request Feedback (Trigger) (Check)

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

Pull Request Feedback (Trigger) (Check)

The merge queue build has failed. Click here to see all failures.


Error in UseMethod("mutate") & Error in robyn_outputs(InputCollect, OutputModels, pareto_fronts = "auto"

Project Robyn
Describe issue
So I ran the model again after making some alterations to the variables included and I never had any issues before with the Outputcollect, but now all of a sudden I get two error messages.
`>>> Running Pareto calculations for 12500 models on auto fronts...

Automatically selected 5 Pareto-fronts to contain at least 100 pareto-optimal models (124)
Pareto-Front: 1 [23 models]
00:00:10 [==================================================] 100% | 23
Pareto-Front: 2 [19 models]
00:00:07 [==================================================] 100% | 19
Pareto-Front: 3 [24 models]
00:00:09 [==================================================] 100% | 24
Pareto-Front: 4 [33 models]
00:00:14 [==================================================] 100% | 33
Pareto-Front: 5 [25 models]
00:00:23 [==================================================] 100% | 25

Calculating clusters for model selection using Pareto fronts...
Couldn't automatically create clusters: Error: empty cluster: try a better set of initial centers

Error in UseMethod("mutate") :
no applicable method for 'mutate' applied to an object of class "NULL"
Error in robyn_outputs(InputCollect, OutputModels, pareto_fronts = "auto",  :
object '"auto"' not found`
Environment & Robyn version
`> packageVersion("Robyn")
[1] ‘3.9.0’

sessionInfo()
R version 4.3.0 (2023-04-21)
Platform: x86_64-apple-darwin20 (64-bit)
Running under: macOS Monterey 12.6

Matrix products: default
BLAS:   /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
LAPACK: /Library/Frameworks/R.framework/Versions/4.3-x86_64/Resources/lib/libRlapack.dylib;  LAPACK version 3.11.0
locale:
[1] en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8
time zone: Europe/Amsterdam
tzcode source: internal
attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base
other attached packages:
[1] doRNG_1.8.6                rngtools_1.5.2             foreach_1.5.2
[4] dplyr_1.1.2                Robyn_3.9.0                reticulate_1.28
[7] readxl_1.4.2               PerformanceAnalytics_2.0.4 xts_0.13.1
[10] zoo_1.8-12
loaded via a namespace (and not attached):
[1] tidyselect_1.2.0     farver_2.1.1         loo_2.6.0            bitops_1.0-7
[5] RCurl_1.98-1.12      lazyeval_0.2.2       pROC_1.18.0          digest_0.6.31
[9] rpart_4.1.19         timechange_0.2.0     lifecycle_1.0.3      StanHeaders_2.21.0-7
[13] survival_3.5-5       processx_3.8.1       magrittr_2.0.3       compiler_4.3.0
[17] rlang_1.1.1          tools_4.3.0          igraph_1.4.2         utf8_1.2.3
[21] yaml_2.3.7           labeling_0.4.2       lares_5.2.1          prettyunits_1.1.1
[25] pkgbuild_1.4.0       here_1.0.1           RColorBrewer_1.1-3   plyr_1.8.8
[29] xml2_1.3.4           withr_2.5.0          purrr_1.0.1          rPref_1.4.0
[33] h2o_<IP_ADDRESS>         grid_4.3.0           stats4_4.3.0         fansi_1.0.4
[37] colorspace_2.1-0     inline_0.3.19        ggplot2_3.4.2        scales_1.2.1
[41] iterators_1.0.14     ggridges_0.5.4       cli_3.6.1            crayon_1.5.2
[45] generics_0.1.3       RcppParallel_5.1.7   rstudioapi_0.14      httr_1.4.5
[49] rstan_2.21.8         stringr_1.5.0        splines_4.3.0        rvest_1.0.3
[53] prophet_1.0          parallel_4.3.0       cellranger_1.1.0     matrixStats_0.63.0
[57] vctrs_0.6.2          glmnet_4.1-7         Matrix_1.5-4         jsonlite_1.8.4
[61] minpack.lm_1.2-3     callr_3.7.3          patchwork_1.1.2      tidyr_1.3.0
[65] glue_1.6.2           nloptr_2.0.3         codetools_0.2-19     ps_1.7.5
[69] lubridate_1.9.2      stringi_1.7.12       shape_1.4.6          gtable_0.3.3
[73] quadprog_1.5-8       rpart.plot_3.1.1     munsell_0.5.0        tibble_3.2.1
[77] pillar_1.9.0         R6_2.5.1             doParallel_1.0.17    rprojroot_2.0.3
[81] lattice_0.21-8       extraDistr_1.9.1     png_0.1-8            openxlsx_<IP_ADDRESS>
[85] Rcpp_1.0.10          zip_2.3.0            gridExtra_2.3        pkgconfig_2.0.3    `

looks like a dependency version issue at the first glance. have you updated dependencies like the whole tidyverse packages lately? you can try update robyn to the latest github version and rerun?

haven't seen this one reported anymore for a long time. please reopen if it reoccurs


Icons after 2024.2.0

A lot of the integration icons were not coming up after the last core update.  Everything seems fine now except this one. i.e. for my battery state, I used to get a battery icon that was colored and changed based on the percentage.  Now it's just a mdi:battery-unknown icon, no color or percentage changes.

https://developers.home-assistant.io/blog/2024/01/30/ha-state-icon-properties-changes/

My battery icons are still showing the changes in color and level as the battery level goes down. Does the mobile app battery level also fail for you when you add it to a Lovelace card? The icon that is displayed is an attribute of the battery entity that can be seen on the HA Developer Tools >States screen.

@bkr1969 Maybe is as simple as clearing your cache?

My fault.  Seems it's not this integration with the problem.  The icons are all fine when viewing them normally.  The problem is that I only use them in battery-state cards, which seems to be causing the problem.


Accessibility: react-slider doesn't announce to assistive tech that it is disabled

Description
When using assistive technology such as a screen reader, this component does not indicate to the screen reader when it is disabled
Adding aria-disabled to the 'handle' elements should resolve this easily.

this is still an issue, please don't close

Thank you for your patience. Merged and published in v2.0.5


Add column flattening via UI creating wrong spec for Kafka ingestions

Affected Version
I'm using Druid 29
Description
The Console UI creates wrong spec when adding a column flatten for a Kafka ingestion.
Reproducing:

Create a new Kafka ingestion
Add a column flattening like 'type: path', 'path: $'
The flatten section will be in spec > ioConfig > inputFormat > flattenSpec
It should be on spec > ioConfig > inputFormat > valueFormat > flattenSpec

It's difficult to understand at first because you can see your data just fine in the 'Configure Schema' tab, but after submit you won't see your data in the table and checking the supervisor the wrong flattenspec will not even be present.

Hi, it would probably be more intuitive if there could be a screenshot to demonstrate.

guess this PR has make it adaptive already, it has been marked as milestone 29.0.1
#15946


[SPARK-20452][SS][Kafka]Fix a potential ConcurrentModificationException for batch Kafka DataFrame

What changes were proposed in this pull request?
Cancel a batch Kafka query but one of task cannot be cancelled, and rerun the same DataFrame may cause ConcurrentModificationException because it may launch two tasks sharing the same group id.
This PR always create a new consumer when reuseKafkaConsumer = false to avoid ConcurrentModificationException. It also contains other minor fixes.
How was this patch tested?
Jenkins.

Test build #76120 has started for PR 17752 at commit cc05f2b.

Test build #76120 has finished for PR 17752 at commit cc05f2b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76120/
Test PASSed.

Test build #76124 has started for PR 17752 at commit b59573f.

Test build #76124 has finished for PR 17752 at commit b59573f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76124/
Test PASSed.

Merged build finished. Test PASSed.

LGTM. Merging to master and 2.2


A11y_Model Builder_Train_Advance Training Options_Usability: Screen reader is not reading the section name for the radio buttons which are present in the "Advanced training options" popup.

GitHubTags
#A11yUsable; #A11ySev4; #A11yTCS; #DesktopApp; #Win11; #Visual Studio Client; #SH_ModelBuilder_Win32_May2023; #Win32; #Benchmark; #Screenreader; #Narrator; #NVDA; #FTP; #STP;
Environment Details
Application Name: Microsoft Visual Studio Enterprise 2022 (64-bit) - Current
Version 17.6.1
Microsoft Windows 11 Enterprise 10.0.22621 Build 22621
Screenreader: Narrator, NVDA
Repro steps

Turn on Narrator/NVDA
Launch the Visual Studio with at least one of the .NET workload.
Tab till enable ML.NET Model Builder (Tools -> Options -> Environment -> Preview Features) and select it.
Create a new .NET project or open an existing .NET project.
Open context menu(Right-click) of the project in the solution explorer.
Tab till Add and then tab till Machine Learning Model and press enter.
Model Builder dialog will open.
Complete the required details of All the three(scenario, environment, data) steps.
Train screen will appear. Tab till Advance Training Option and press enter.
Optimizing Metric screen will appear.
Verify whether screen reader is reading the section name for the radio buttons which are present in the "Advanced training options" popup or not.

Actual Result
Screen reader is not reading the section name for the radio buttons which are present in the "Advanced training options" popup.
Issue observed throughout the application.
Issue reproducible with NVDA.
Expected Result
Screen reader should read the section name for the radio buttons which are present in the "Advanced training options" popup.
User Impact
Screen reader user will not be able to get the proper information regarding the radio buttons.
Attachment

@Samhitha66  ,this  can be validated by a private build you can download from here.

@zewditu
We are expecting screen reader must read the section name for the radio button , like choose the metric that MB use.... when focus lands on radio button.
#Regressed:07-17-23; #Pendinginput;


docs: third-party state management and migration guide

resolves #19696
❓ Type of change

[x] 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Added example to do mimic vuex global state management from Nuxt 2 with pinia and nuxt 3.
Referenced popular modules related to state management in docs

📝 Checklist

[x] I have linked an issue or discussion.
[x] I have updated the documentation accordingly.

Let me know what you think. This is good to go from my point of view - and thank you so much for this! ❤

Thank you all !

Isn't the "stores" folder plural tho?

Isn't the "stores" folder plural tho?

Note in nuxt 2 https://nuxtjs.org/docs/directory-structure/store


Roll Flutter Engine from 0ad18fe4c0b5 to 0e3e68f0af2f (4 revisions)

https://github.com/flutter/engine/compare/0ad18fe4c0b5...0e3e68f0af2f
2024-06-18<EMAIL_ADDRESS>Reland "Upgrade all[most] androidx dependencies to latest" (flutter/engine#53462)
2024-06-18<EMAIL_ADDRESS>Roll Skia from 1675eeabb289 to f0bab26f6818 (2 revisions) (flutter/engine#53459)
2024-06-18<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from TwoeJy5Tn0ARHF5O4... to u8WOst9tlXsVQ02eJ... (flutter/engine#53461)
2024-06-18<EMAIL_ADDRESS>Roll Dart SDK from 7245875f5191 to 7f1642cd8bed (1 revision) (flutter/engine#53460)
Also rolling transitive DEPS:
fuchsia/sdk/core/linux-amd64 from TwoeJy5Tn0AR to u8WOst9tlXsV
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC jsimmons@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


How do you collectstatic in production?

I've been searching around not finding much on this.Hope it's fine to ask this here as I originally started the project from this template.
My first thought to collect the static files in a production environment was to go onto the production server and run ./manage.py collectstatic. The issue with this was that the developer pip packages weren't installed so running manage.py threw an import error. I'm assuming this is the incorrect way to do it. My next thought was that collectstatic should be done in a similar fashion to the Amazon S3 collectstatic class but I can't seem to find an already built solution to send your static files to your own server and save them in some directory. Is there a solution to this already?

This is one of project features.
When you create a new project, if you say "no" to use_whitenoise, I believe you will get this behavior in production, serving statics files from s3.

The issue with this was that the developer pip packages weren't installed so running manage.py threw an import error

You should be able to run collectstatic on your prod server, it doesn't require any dev requirements. What import error specifically?
If you use Docker, collectstatic is run automatically [when the server starts](The issue with this was that the developer pip packages weren't installed so running manage.py threw an import error).
If you deploy on Heroku, it should be done automatically.
The collectstatic command is working with your static files config and copies files to whatever static file storage you have configured.

@browniebroke the import error I was getting was for django debug-toolbar. It tries to import the local settings file which contains this dependency because of [line 6 in manage.py|https://github.com/pydanny/cookiecutter-django/blob/ffbec778a6fb3b0231755bb40560f4af83b7643c/%7B%7Bcookiecutter.project_slug%7D%7D/manage.py#L6].
    os.environ.setdefault("DJANGO_SETTINGS_MODULE", "config.settings.local")
This made me think I shouldn't be using manage.py on the production server. Maybe whitenoise is what I'm looking for.
@sfdye does whitenoise allow for deploying static files to your own server or is it only configurable for S3 instances?

Would a safe solution be to simply change which settings file manage.py uses  and run collectstatic directly on the production server? For this server I'm serving the static files.
That brings up the question of serving files from S3 then. Collectstatic in that case should be done from a local development environment?

This is working as expected, the manage script defaults to local settings, and on production, you should set an environment variable to use the production settings: DJANGO_SETTINGS_MODULE='config.settings.production'
Here are links:

Doc for Python anywhere
Doc for Heroku
For Docker, it should be done out of the box by the env file.

If you deploy the project on another type of production machine, not using Docker, I would recommend checking with your hosting provider how to set environment variables.

@browniebroke That seems obvious now, thank you.


bug in function excludeCorrectlyTaggedNodes()

In function excludeCorrectlyTaggedNodes() when matching tags with tagOwners:
https://github.com/juanfont/headscale/blob/e80954b6c8f97f19ca881ab1c3bf5d7d2428d74c/acls.go#L314
The above line missing the condition when tagOwners are groups.
Adding two lines here could fix this problem
owners, _ := expandTagOwners(aclPolicy, namespace, true)
ns = append(owners, namespace)
But the third parameter (true/false) needs to be filled correctly, which I'm not sure how could be elegantly done.

We will be grateful for a PR to solve this issue :)
@restanrm, does this look right to you? Maybe this is already fixed?


bumps lwip version to 0.0.9

Fixes issues with node v6+. #7
See PR #250 on lwip

Any news for this fix ? We need it ! 😄

@aslansky checking in on this! Got any feedback?

+1 :)

please, merge this! 👍

Another request to please merge this.

Please merge :)

@aslansky @thibthib @zoubin, could you merge this one please ?

Folks, it's available on<EMAIL_ADDRESS>


The results of reimplemented models

I want to know the results of re-implemented models.

PSPNet ~78.5 Deeplabv3 ~78.9 on cityscapes val dataset with single scale testing.
And we have uploaded the document to arxiv and it may take a little time to be public.

The document is here https://weiyc.github.io/assets/pdf/toolbox.pdf


Re-fix win build  after move to configure file

It compiles, but it fails during execution with:
Related to CXX17? pragma flags? grpc version?
https://github.com/meztez/bigrquerystorage/actions/runs/7161678616/job/19497609842
Error: Error: gRPC method CreateReadSession error -> empty address list:
Backtrace:
    ▆
 1. └─bigrquerystorage::bqs_table_download(...) at test-integration.R:139:9
 2.   └─bigrquerystorage:::bqs_ipc_stream(...) at bigrquerystorage/R/bqs_download.R:68:3

Can I reproduce this somehow?


where can I find example for implementing EntitiyFormField

Rasa Core version:
0.9.7
Python version:
2.7.4
Operating system (windows, osx, ...):
centOS 7
Issue:
where can I find example for implementing EntitiyFormField? .. I found this issue #502 and there is a link
https://core.rasa.com/master/patterns.html .. but the link was broken :(
thanks
Content of domain file (if used & relevant):

@Primtek
.. _patterns:
Slot Filling and Common Patterns
.. note::
Here we go through some typical conversation patterns and explain how to implement
them with Rasa Core.
Rasa Core uses ML models to predict actions, and slots provide important
information these models rely on to keep track of context and handle multi-turn dialogue.
Slots are for storing information that's relevant over multiple turns. For example, in
our restaurant example, we would want to keep track of things like the cuisine and number of
people for the duration of the conversation.
Collecting Information to Complete a Request (Slot Filling)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Probably the most common pattern of all is to collect a few pieces of information
from a user in order to do something (book a restaurant, call an API, search a database, etc.).
This is also called slot filling.
To make this easier, Rasa has a special action class called FormAction.
This lets you have a single action for this task, rather than separate actions for each question,
e.g. utter_ask_cuisine, utter_ask_numpeople, etc.
You don't have to use FormAction s to do slot filling, but it can be easier.
A form action has a set of required fields, which you define for the class:
.. literalinclude:: ../tests/test_forms.py
:pyobject: ActionSearchRestaurants
The way this works is that every time you call this action, it will pick one of the
REQUIRED_FIELDS that's still missing and ask the user for it. You can also ask a yes/no
question with a BooleanFormField.
The story will look something like this:
.. code-block:: md

request_restaurant

action_restaurant_form
slot{"requested_slot": "people"}

inform{"number": 3}

action_restaurant_form
slot{"people": 3}
slot{"requested_slot": "time"}

inform{"time": "8pm"}

action_restaurant_form

Some important things to consider:

Your domain needs to have a slot called requested_slot. This can be unfeaturized, but if you want
to support contextual questions like "why do you need to know that information?" it will help if you make this
a categorical slot.
You need to define utterances for asking for each slot in your domain, e.g. utter_ask_{slot_name}.
We strongly recommend that you create these stories using interactive learning, because if you
type these by hand you will probably forget to add all of the slots.
Any slots that are already set won't be asked for. E.g. if someone says "I'd like a Chinese restaurant for 8 people" the submit function should get called right away.

Validation and Free-text Input

For any subclass of  ``FormField``, it's ``validate()`` method will be called before setting it
as a slot. By default this just checks that the value isn't ``None``, but if you want to check
the value against a DB, or check a pattern is matched, you can do so by defining your own class
like ``MyCustomFormField`` and overriding the ``validate()`` method.

There is also a ``FreeTextFormField`` class which will just extract the user message as a value.
However, there is no way to write a 'wildcard' intent in Rasa Core stories as of now. Typically
your NLU model will assign this free-text input to 2-3 different intents.
It's easiest to add stories for each of these.

Collecting Information using Slots
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

For collecting a set of preferences, you can use ``TextSlot`` s like in the restaurant example:

.. code-block:: yaml

   slots:
     cuisine:
       type: text
    people:
       type: text
    ...

When Rasa sees an entity with the same name as one of the slots, this value is automatically saved.
For example, if your NLU module detects the entity ``people=8`` in the sentence *"I'd like a table for 8"*,
this will be saved as a slot,

.. testsetup::

   from rasa_core.trackers import DialogueStateTracker
   from rasa_core.slots import TextSlot
   from rasa_core.events import SlotSet
   tracker = DialogueStateTracker("default", slots=[TextSlot("people")])
   tracker.update(SlotSet("people", "8"))

.. doctest::

   >>> tracker.slots
   {'people': <TextSlot(people: 8)>}

When Rasa Core predicts the next action to take, the only information it has about the ``TextSlot`` s is
**whether or not they are defined**. So you have enough information to know that you don't have to ask for this
information again, but the *value* of a ``TextSlot`` has no impact on which actions Rasa Core predicts. This is
explained in :ref:`more detail below <slot_features>`.

The full set of slot types and their behaviour is described here: :ref:`slot_types`.

Using Slot Values to Influence Which Actions are Predicted
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

**Custom Slots**

Maybe your restaurant booking system can only handle bookings for up to 6 people, so the
request above isn't valid. In this case you want the *value* of the slot to influence the
next selected action (not just whether it's been specified). You can achieve this using a custom
slot class.

The way we defined it below, if the number of people is less than or equal to 6, we return ``(1,0)``,
if it's more we return ``(0,1)``, and if it's not set ``(0,0)``.

Rasa Core can use that information to distinguish between different situations - so long as
you have some training stories where the appropriate responses take place, e.g.:

.. code-block:: md

   # story1
   ...
   * inform{"people": "3"}
   - action_book_table
   ...
   # story2
   * inform{"people": "9"}
   - action_explain_table_limit

.. doctest::

   from rasa_core.slots import Slot

   class NumberOfPeopleSlot(Slot):

     def feature_dimensionality(self):
         return 2

     def as_feature(self):
         r = [0.0] * self.feature_dimensionality()
         if self.value:
             if self.value <= 6:
                 r[0] = 1.0
             else:
                 r[1] = 1.0
         return r

If you want to store something like the price range, this is actually a little simpler. Variables
like price range usually take on one-of-n values, e.g. low, medium, high. For these cases you can use
a ``categorical`` slot.

.. code-block:: yaml

   slots:
     price_range:
       type: categorical
       values: low, medium, high

Rasa automatically represents (featurises) this as a one-hot encoding of the values: ``(1,0,0)``, ``(0,1,0)``, or ``(0,0,1)``.

.. _slot_features:

**Slot features**

When Rasa Core runs trains a dialogue model using your stories the presence of a ``Slot`` entry will be used to help
determine the next action that should be taken. This works best with ``CategoricalSlot`` slot types.

A ``TextSlot`` can have any value, but it only has a single feature. It can be set, in which case the feature
has a value ``(1)``, or if it is not set it will have a value ``(0)``.

A ``CategoricalSlot`` has a number of values each of which is a feature. Taking the example below, when the
``restaurant_availability`` slot is set Rasa Core will be able to determine whether or not the restaurant in question is
available and choose radically different actions to perform based on the value.

.. code-block:: yaml

    restaurant_availability:
        type: categorical
        values:
        - unknown
        - booked-out
        - waiting-list
        - available

A ``Slot`` will be set by Rasa Core if its name and the name of the entity detected by the NLU module
match. The value of the slot will influence the story dialogue if you add the slot to the training
stories - this is explained in the examples below. Slots can also be set explicitly from our own custom ``Action``
and influence the dialogue based on real-world information.

.. code-block:: python

    class ActionMakeBooking(Action):

        def run(self, dispatcher, tracker, domain):
            restaurant_name=tracker.get_slot("restaurant_name")
            location=tracker.get_slot("location")
            num_people=tracker.get_slot("people")
            date=tracker.get_slot("date")
            # this will fetch the availability of the restaurant from your DB or an API
            availability=restaurantService.check_availability(restaurant_name, location, num_people, date)
            return [SlotSet("restaurant_availability", availability)]

The snippet of code above from a hypothetical ``Action`` shows that the value of the slot ``restaurant_availability`` is determined by querying a database or API. The restaurant availability is not something that is known when we train the dialogue model, the ``Slot`` value is the only way we can alter the course of the conversation based on information from the outside world.

The data fetched from an API call can also be stored for later use without altering the outcome of a conversation as detailed in :ref:`unfeaturized_slots`.

**Slot Features Example**

.. note::
    These example stories have been constructed manually for illustrative purposes. While this is a valid approach to training your model the preferred approach is to use :ref:`interactive learning <tutorial_interactive_learning>` which generates stories that are *much* less error-prone.

In this first story we will try and make a booking for 5 people in a restaurant on the night of 21st August 2018.
In this case the restaurant is booked out so we want to apologize to the customer and suggest similar restaurants. It is assumed that the Rasa Core model has been trained to recognise a message like *"Book Murphys Bistro on August 21 for 5 people"*

.. code-block:: md

    # restaurant unavailable
    * _make_booking{"people":"5", "date":"2018-08-21T19:30:00+00:00", "restaurant_id":"145"}
    - slot{"restaurant_availability": "booked-out"}
    - utter_sorry_unavailable
    - action_show_similar

This second story details the flow when the restaurant is available. We will tell the customer we have booked
the restaurant and ask if any further help is required.

.. code-block:: md

    # restaurant available
    * _make_booking{"people":"5", "date":"2018-08-22T19:30:00+00:00", "restaurant_id":"145"}
    - slot{"restaurant_availability": "available"}
    - action_make_booking
    - utter_restaurant_booked
    - utter_anything_more
    * _bye
    - utter_thank_you

In this last example, the intent ``make_booking`` was found but either Rasa Core failed to parse a date or the
date was not provided. In this case we would need to ask for more information.

**Note:** this last story is using the fact that ``date`` is a ``TextSlot`` and therefore has a single feature that
is set or not.

.. code-block:: md

    # restaurant request without date
    * _make_booking{"people":"5", "restaurant_id":"145"}
    - slot{"date": null}
    - utter_date_required
    * _inform{"date":"2018-08-22T19:30:00+00:00"}
    - action_make_booking
    - utter_restaurant_booked
    - utter_anything_more
    * _bye
    - utter_thank_you

.. _unfeaturized_slots:

Storing API responses in the tracker
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

The result from an API call can be stored in a ``Slot`` as :ref:`explained above <slot_features>`. In that case
the data is stored in a ``Slot`` that is featurized, influencing the flow of the dialogue.

A slot of type ``unfeaturized`` can be used to store the results from a database query or API call so that it will
not influence the course of a dialogue. An exaple ``unfeaturized`` slot defined in a domain file:

.. code-block:: yaml

    slots:
        api_result:
            type: unfeaturized

You can set this value in a custom ``Action``:

.. code-block:: python

   from rasa_core.actions import Action
   from rasa_core.events import SlotSet
   import requests

   class ApiAction(Action):
       def name(self):
           return "api_action"

       def run(self, tracker, dispatcher):
           data = requests.get(url).json
           return [SlotSet("api_result", data)]

This is especially useful when you are :ref:`persisting your tracker <persisting_trackers>` in Redis or another data store. You could cache the API or database responses separately, but storing them in the tracker means they will be persisted automatically with the rest of the dialogue state, and will be restored along with the rest of the state should the system require a reboot.

Fallback / Default Actions
^^^^^^^^^^^^^^^^^^^^^^^^^^

Sometimes you want to fall back to a default action like saying "Sorry, I didn't understand that".
To do this, add the ``FallbackPolicy`` to your policy ensemble.
The default action will be executed if the intent recognition has a confidence below ``nlu_threshold``
or if none of the dialogue policies predict an action with confidence higher than ``core_threshold``

.. code-block:: python

   from rasa_core.policies.fallback import FallbackPolicy
   from rasa_core.policies.keras_policy import KerasPolicy
   from rasa_core.agent import Agent

   fallback = FallbackPolicy(fallback_action_name="utter_default",
                             core_threshold=0.3,
                             nlu_threshold=0.3)

   agent = Agent("domain.yml",
                  policies=[KerasPolicy(), fallback])

@Primtek
You can see the page source at
https://core.rasa.com/_sources/patterns.rst.txt

ah the link changed, so it's just http://core.rasa.com/patterns.html
because 'master' uses the new docs (will be released with new version) which renamed this page

ah the link changed, so it's just http://core.rasa.com/patterns.html
because 'master' uses the new docs (will be released with new version) which renamed this page

Have you removed FormAction in version 0.12 of core

We are working on a major refactor of forms which make them much better :)