Alert on CloudTrail events from all regions across multiple accounts

In a multiple account setup, I'd like to alert on CloudTrail events from all aws regions.
My current setup:
ProductionAccount

CloudTrail enabled for all regions
CloudWatch event rule to send all events to AlertingAccount Event Bus

AlertingAccount

StreamAlert cluster in one region
CloudTrail enabled for all regions
CloudWatch event rule to send all events from ProductionAccount and AlertingAccount to prefix_cluster_stream_alert_kinesis

This works great for CloudTrail events that originate in the same region as the CloudWatch Event. But it doesn't work when the CloudTrail event occurs in a different aws region. It doesn't matter if the event comes from the ProductionAccount via the EventBus or from the AlertingAccount itself.
It seems CloudWatch events and rules are region specific. Additionally, I was unable to select the kinesis stream as a target of a CloudWatch event from a different region.
What is the best way to collect CloudTrail events from all regions from all accounts?

After a bit of investigation I've come across the following options:
S3 bucket notifications
Enable CouldTrail for all regions in all accounts. Send the trails to a single s3 bucket in the StreamAlert cluster account/region. Use the s3:ObjectCreated:* notification to send the objects to the StreamAlert rule processor lambda.
Pros: Doesn't require infrastructure in all regions.
Cons: 5-10 minute delay on events.
CloudWatch Logs
Enable CloudTrail for all regions in all accounts. Send the trails to a CloudWatch Logs destination in the StreamAlert cluster account/region. Add a subscription filter on the destination to send the events to the StreamAlert kinesis stream.
Pros: Doesn't require infrastructure in all regions.
Cons: Event message is wrapped in a string, gzipped, base64 encoded, and wrapped in the kinesis JSON protocol = longer lambda processing time. Also has a 5-10 minute delay on events.
CloudWatch Events + EventBus
Enable EventBus in every region in every account to send CloudTrail events to the StreamAlert account. Create a CloudWatch Event in each region, to post to an SNS topic in each region. Use the SNS topic to post to a cross-region lambda function that sends them to the StreamAlert kinesis stream in the same region.
Pros: Minimal delay on events?
Cons: Requires infrastructure in all regions.
(untested)
CloudTrail Processing Library
Run a Java application to poll the CloudTrail SQS stream using the CloudTrail Processing Library or Lambda function, and send the events to the kinesis stream. Not sure about cross account.
Pros: Minimal delay on events?
Cons: Requires an ec2 instance, or Lambda to poll SQS.
(untested)

I tried to add the kinesis stream as a target to the CloudWatch event rule from a different region, but without success:
aws --region us-east-1 events put-rule \
    --name "test_prod_streamalert_all_events" \
    --event-pattern "{\"account\": [\"ACCOUNT_ID\"]}" \
    --state "ENABLED" \
    --description "Capture all CloudWatch events" \
    --role-arn "arn:aws:iam::ACCOUNT_ID:role/streamalert/test_prod_streamalert_cloudwatch_role"

aws --region us-east-1 events put-targets \
    --rule "test_prod_streamalert_all_events" \
    --targets "Id"="StreamAlertKinesis","Arn"="arn:aws:kinesis:us-west-2:ACCOUNT_ID:stream/test_prod_stream_alert_kinesis"

Error:
An error occurred (AccessDeniedException) when calling the PutTargets operation: Access to the resource arn:aws:kinesis:us-west-2:ACCOUNT_ID:stream/test_prod_stream_alert_kinesis is denied. Reason: Adding cross-region target is not permitted.

This means you do require the SNS topic and Lambda mentioned in CloudWatch Events + EventBus above.
Which would result in a structure similar to this:

A couple notes on the approaches above:

CloudTrail Processing Library:
Run a Java application to poll the CloudTrail SQS stream using the CloudTrail Processing Library or Lambda function, and send the events to the kinesis stream. Not sure about cross account.

This simply uses SQS to notify about delivery of new log files to S3.  The StreamAlert rule processor is already equipped to analyze these logs

CloudWatch Events + EventBus:
Enable EventBus in every region in every account to send CloudTrail events to the StreamAlert account. Create a CloudWatch Event in each region, to post to an SNS topic in each region. Use the SNS topic to post to a cross-region lambda function that sends them to the StreamAlert kinesis stream in the same region.

What's the purpose of the SNS topic in this scenario? The CloudTrail documentation suggests it's just for notifying for delivery of new log files to buckets.  If we are creating CloudWatch events, we could send directly to Kinesis instead of SNS => Lambda => Kinesis.
It seems like we would run into the current issue of not being able to send cross region cloudwatch events to a single kinesis stream.
The options I see right now are:

Create a StreamAlert cluster in each region to accept events from within the same account and a cross-account event bus.

Configure S3 event notifications to Lambda to pull CloudTrail files directly from S3.

That's a shame about the CloudTrail Processing Library. I had hoped you could get the CloudTrail events directly through SQS.
The SNS topic can be used to get around CloudWatch event rules not able to target cross-region resources. So the SNS Topic can notify a cross-region Lambda function which can post into the kinesis stream. But I agree it's too much.
Thanks for the feedback. I'll look at perhaps a combination of 1. and 2. Creating a StreamAlert cluster in each important region, and use s3 notifications for the rest.

hey @stoggi - just checking in to see if you got all squared away and if we can help in any way :)

Hey @mime-frame, thanks for checking in. We settled on creating a StreamAlert cluster in each important region and using CloudTrail S3 notifications for the rest. I haven't had time to code it up yet, but I'm back on StreamAlert shortly so will see how it goes. Cheers.

I documented the approach I've used for this: https://summitroute.com/blog/2019/03/06/guardduty_event_collection_via_cloudwatch_events/


pythonPackages.pip: make reproducible

The previous attempt wasn't covering all of the bases. It relied on
invoking that pip-install-hook, and didn't apply to pip itself.
The core issue is that the generated .pyc files embed some of the
temporary paths, which are randomly generated. See
https://r13y.com/diff/bf8c3ca3148ebff9ecf41f294cc60b9f209c006d49699e356969ff32d736f1c6-8806a7cca91fdd300e48736bfcd57c4d0b54c1cc2fd61609f35143170862b59c.html
In this new attempt, the approach is to patch the TempFile
implementation directly, so that it creates stable temporary
directories. We also assume that if SOURCE_DATE_EPOCH is set, we are in
a scenario where reproducible builds are desirable and enter that
branch.

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Sorry for the notification spam.
@FRidh is there any package beyond pip that is critical to test?
Here are some packages that are now reproducible:

[x] pythonPackages.pip
[x] pythonPackages.bootstrapped-pip
[x] pythonPackages.pytest

pytest is likely due to its own cache, although that we do handle.
Please refer in the code to the upstream issue https://github.com/pypa/pip/issues/7808.

@FRidh fixed. Thanks for the review!

should we upstream this? pip should respect SOURCE_DATE_EPOCH

should we upstream this? pip should respect SOURCE_DATE_EPOCH

This patch is a hack. While the patch is for reproducibility, SOURCE_DATE_EPOCH has nothing to do with it, and is solely used here to indicate "we want it reproducible". For that reason the previous patch had NIX_PIP_INSTALL_TMPDIR.

Semantically speaking SOURCE_DATE_EPOCH is not entirely correct. A better fix would be for upstream to fix their build so that the build directories are not included in the .pyc files.

This seems to have regressed things pretty early in the chain, nix-build -A nss now fails:
git bisect start
# bad: [d4e94ffd1d3f16790b5001cbd5e064c7fd5e72d7] nixos.tests.systemd-journal: add basic systemd-journal-gatewayd test
git bisect bad d4e94ffd1d3f16790b5001cbd5e064c7fd5e72d7
# good: [26d3fbf21563c52f124551eb60dec5ea17ade8fa] Merge pull request #102310 from r-ryantm/auto-update/git-gone
git bisect good 26d3fbf21563c52f124551eb60dec5ea17ade8fa
# good: [06929e3f286118783e59fbf7e8ac71124f5048b7] gnome3.gpaste: 3.36.3 → 3.38.2
git bisect good 06929e3f286118783e59fbf7e8ac71124f5048b7
# good: [6456e24d570728bc81fa8b070c5e34f83c7425f0] systemd: nixpkgs-fmt
git bisect good 6456e24d570728bc81fa8b070c5e34f83c7425f0
# bad: [b9222f51583f0553229d37ad0aeee1f7822ef656] python3Packages.hidapi: 0.9.0.post3 -> 0.10.0
git bisect bad b9222f51583f0553229d37ad0aeee1f7822ef656
# good: [dfe9e0e4584de3392311947053100898aea92cab] pango: build with libthai
git bisect good dfe9e0e4584de3392311947053100898aea92cab
# good: [7a8d5dc8a676a528186ea0f2ece97e832d784562] Merge master into staging-next
git bisect good 7a8d5dc8a676a528186ea0f2ece97e832d784562
# bad: [b57adad0851ee7171676cfc168518fa23418d265] Merge pull request #101673 from r-ryantm/auto-update/libndctl
git bisect bad b57adad0851ee7171676cfc168518fa23418d265
# bad: [6cc483b6c23821158c0f9310b6f5bacd9d3bfa58] autogen: make reproducible (#102280)
git bisect bad 6cc483b6c23821158c0f9310b6f5bacd9d3bfa58

This patch is a hack. While the patch is for reproducibility, SOURCE_DATE_EPOCH has nothing to do with it, and is solely used here to indicate "we want it reproducible"

I stopped reading after the if statement. Yea, this is a hack, but an improvement.

This triggered failures in case of format = "pyproject"; and this will probably block staging-next.
It seems as if the build phase is run twice, in which case its not because of a bug in this patch, but because of a mistake in the hook pip-build-hook.sh.

Seems like the issue is resolved in pip 20.2, upgrading now and reverting the patches.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/hydra-security-model-discussion/9801/12


[url_launcher] avoid deprecation warning in guarded code

Description
The [application openURL:] was deprecated in iOS 10. Since we are already using the newer API on iOS 10 and newer, this warning can be safely ignored.
Avoids the following output when building a flutter app that uses this plugin:
url_launcher-5.0.2/ios/Classes/UrlLauncherPlugin.m:141:33: warning: 'openURL:' is deprecated: first
      deprecated in iOS 10.0 - Please use openURL:options:completionHandler: instead [-Wdeprecated-declarations]
    BOOL success = [application openURL:url];
                                ^
In module 'UIKit' imported from /Users/linus/coding/eego/ios/Pods/Target Support Files/url_launcher/url_launcher-prefix.pch:2:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS12.2.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIApplication.h:128:1: note:
      'openURL:' has been explicitly marked deprecated here
- (BOOL)openURL:(NSURL*)url NS_DEPRECATED_IOS(2_0, 10_0, "Please use openURL:options:completionHandler: instead") NS_EXTENSION_UNAVAILABLE_IOS("");
^
3 warnings generated.

Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[n/a] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

Seems like the build failure is not related to my changes 🤔

Thanks!


changed transactions to use prepare/execute

Changed a few simple transactions from nba-smart-contracts to use prepare/execute instead of prepare or none at all

@timongll Thank you so much for working on these! Can you run the tests with make test also to make sure they pass?


support bound methods

when a bound method is given for run argument, the following traceback appears
[2021-09-19 20:51:57] [WARN ] can't inject argument 'self' to function 'cd': name not found
Traceback (most recent call last):
  File "/src/shell/xsh/xonsh/procs/proxies.py", line 523, in run
    r = self.f(self.args, sp_stdin, sp_stdout, sp_stderr, spec, spec.stack)
        │      │          │         │          │          │     └ SubprocSpec(['commands'], ProcProxyThread, stdin=None, stdout=<_io.TextIOWrapper name=7 mode='w' encoding='UTF-8'>, stderr=<_io....
        │      │          │         │          │          └ SubprocSpec(['commands'], ProcProxyThread, stdin=None, stdout=<_io.TextIOWrapper name=7 mode='w' encoding='UTF-8'>, stderr=<_io....
        │      │          │         │          └ <_io.TextIOWrapper name=9 encoding='utf-8'>
        │      │          │         └ <_io.TextIOWrapper name=7 encoding='utf-8'>
        │      │          └ None
        │      └ <ProcProxyThread(Thread-27, started<PHONE_NUMBER>73888)>
        └ <ProcProxyThread(Thread-27, started<PHONE_NUMBER>73888)>
  File "/src/shell/xontribs/commands/xontrib/commands/dev_cmd.py", line 212, in __call__
    self.build.run_with_args(args)
    │                        └ ['commands']
    └ <xontrib.commands.dev_cmd.Alias object at 0x7f6d954af1c0>
  File "/home/noor/.virtualenvs/user-xsh-rVZlQJi1-py3.9/lib/python3.9/site-packages/nuclear/builder/builder.py", line 84, in run_with_args
    parser.parse_args(args)
    │                 └ ['commands']
    └ <nuclear.parser.parser.Parser object at 0x7f6d846ea1f0>
  File "/home/noor/.virtualenvs/user-xsh-rVZlQJi1-py3.9/lib/python3.9/site-packages/nuclear/parser/parser.py", line 88, in parse_args
    run_action(run_context.action, run_context.internal_vars)
    │          │                   └ RunContext(args_container=<nuclear.args.container.ArgsContainer object at 0x7f6d846ea2b0>, action=<bound method Alias.cd of <xon...
    │          └ RunContext(args_container=<nuclear.args.container.ArgsContainer object at 0x7f6d846ea2b0>, action=<bound method Alias.cd of <xon...
    └ <function run_action at 0x7f6d84595280>
  File "/home/noor/.virtualenvs/user-xsh-rVZlQJi1-py3.9/lib/python3.9/site-packages/nuclear/parser/inject.py", line 17, in run_action
    action(**kwargs)
    │        └ {'self': None, 'name': 'commands'}
    └ <bound method Alias.cd of <xontrib.commands.dev_cmd.Alias object at 0x7f6d954af1c0>>
TypeError: cd() got multiple values for argument 'self'

As of now, I am using static_method decorator. Is it possible to pass instance methods?

Not sure how your code looks like, but here's an example how you can use nuclear with static methods or even class methods:
#!/usr/bin/env python3
from nuclear import CliBuilder, subcommand

def main():
    CliBuilder().has(
        subcommand('static', run=Hello.static),
        subcommand('classy', run=lambda: Hello.classy()),
    ).run()

class Hello:
    @staticmethod
    def static():
        print('here comes the static')

    @classmethod
    def classy(cls):
        print('very classy')

main()

The following verifies that the methods are actually being called:
$ ./demo.py static
here comes the static
$ ./demo.py classy
very classy

class Hello:
    @staticmethod
    def static():
        print('here comes the static')

    def instance(self):
        print('very classy')

    @cached_property
    def builder(self):
        return CliBuilder().has(
        subcommand('help', run=self.instance),
       )

My code is similar to this. I am using this way to postpone building and wrap all data inside a single instance. I have just seen your inner codes, (adding the default arguments part), and they use the inner functions to wrap calls to instance methods. Also one small suggestion, using inspect.signature will return more relevant things in order to call

Alright, now I see what you mean.
However this is not quite how CliBuilder is intended to be called as it loses self reference and CliBuilder is unable to find it from variables kept inside.
If you really want it so badly, you can convert one-argument function to zero-argument function with lambda:
from functools import cached_property
from nuclear import CliBuilder, subcommand

class Hello:
    def instance(self):
        print('help me')

    @cached_property
    def builder(self):
        return CliBuilder().has(
            subcommand('help', run=lambda: self.instance()),
        )

Hello().builder.run()

It would be tedious if the function has arguments, we have to repeat the same for the lambda.
Will you accept any patch ?
By the way, thanks for making this.

Sure. I agree, it would be unnecessarily repetitive, though I guess the hardest part would be extracting self from the method reference. I'm afraid this might not be so easy in Python.

I guess the hardest part would be extracting self from the method reference. I'm afraid this might not be so easy in Python.

We don't need to pass the self variable since the function will hold reference to the bound method. If we use the inspect.signature it will return the correct signature needed to call the method.

@igrek51 thanks a lot. I also wanted to ask about coloring the help/usage output? can this be made more configurable? with argparse one can pass the custom formatter class. (perhaps an another issue?)

@jnoortheen The help output is not configurable at this moment. You can request that in the separate issue.


[Question] Embed

Hello, could you please tell me if I'm doing something wrong?, i'm trying to add external images to my BOT messages:
<?php

include __DIR__ . '/vendor/autoload.php';

use Discord\DiscordCommandClient;
use Discord\Parts\Embed;
use Discord\Parts\Channel;

$discord = new DiscordCommandClient([
    'token' => 'TOKEN',
    'prefix' => '!',
    'description' => 'bleh',
        ]);

$discord->registerCommand('test', function ($message) {
    $responseMessage = 'hello';

    $embed = new Embed;
    $embed->title = 'test';
    $embed->url = 'https://i.vimeocdn.com/portrait/58832_300x300'; //example URL

    $message->channel->sendMessage($responseMessage, false, $embed);
}, array(
    'description' => 'bleh'
        )
);

$discord->run();

$embed = $discord->factory(Embed::class, [
    'title' => 'test',
    'url' => 'urlhere',
]);

Rest should work.

@uniquoooo $discord variable is no available inside "$discord->registerCommand"

function ($message) use ($discord) will allow you to pass the variable through the closure.

@uniquoooo is not working, do you have an example of a working bot sending an embed?

@marianoarga Did you get this working? Tried the code and suggestions above. Nothing is being returned by the bot.

@beboobailey
Try to send it as an array, I have never got it working as an Embed class:
$embed = array(
            "color" => 0,
            "author" => [
                "name" => "MAYBE BOT NAME",
            ],
            "title" => "**TITLE**",
            "description" => ""
                . "**BLA**\r\n"
                . "**BLA**\r\n"
            ,
            "thumbnail" => [
                "url" => "THUMBNAIL_URL"
            ]
        );

$message->channel->sendMessage("", false, $embed);


bug: typescript error when using useQuery imported from wagmi

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
0.12.1
Current Behavior
When importing useQuery from wagmi
import { useInfiniteQuery, useQuery } from 'wagmi';
import axios from 'axios';

export async function getPosts() {
  return axios.get('http://localhost:3000/test').then((res) => res.data);
}

const Home: NextPage = () => {
  const { status, data, error, isFetching, isRefetching } = useQuery({
    queryKey: ['test'],
    queryFn: () => getPosts(),
    keepPreviousData: true,
    staleTime: 5000,
  });
...

I get following ts error:
No overload matches this call.
  Overload 1 of 4, '(queryKey: QueryKey, options?: (Omit<UseQueryOptions<unknown, unknown, unknown, QueryKey>, "queryKey" | "initialData"> & { initialData?: (() => undefined) | undefined; }) | undefined): UseQueryResult<...>', gave the following error.
    Argument of type '{ queryKey: string[]; queryFn: () => Promise<any>; keepPreviousData: boolean; staleTime: number; }' is not assignable to parameter of type 'QueryKey'.
      Object literal may only specify known properties, and 'queryKey' does not exist in type 'readonly unknown[]'.
  Overload 2 of 4, '(queryKey: QueryKey, options?: (Omit<UseQueryOptions<unknown, unknown, unknown, QueryKey>, "queryKey" | "initialData"> & { initialData: unknown; }) | undefined): DefinedUseQueryResult<...>', gave the following error.
    Argument of type '{ queryKey: string[]; queryFn: () => Promise<any>; keepPreviousData: boolean; staleTime: number; }' is not assignable to parameter of type 'QueryKey'.
      Object literal may only specify known properties, and 'queryKey' does not exist in type 'readonly unknown[]'.(2769)

when using useInfiniteQuery from wagmi, there are no errors.
Expected Behavior
There should be no typescript errors when using useQuery imported from wagmi.
Steps To Reproduce
No response
Link to Minimal Reproducible Example (StackBlitz, CodeSandbox, GitHub repo etc.)
https://stackblitz.com/edit/next-typescript-s1l6e9?file=pages/index.tsx
Anything else?
No response

wagmi's internal useQuery API is a bit behind the times right now so that's why it looks a bit different than what is in React Query. We'll update this soon, but for now closing as this is the expected behavior.

@tmm But what is the expected behavior ? I cannot find anything in the docs about useQuery, why is that ?


ValueError: Tensor Tensor("Encoder-12-FeedForward-Norm/add_1:0", shape=(?, 32, 768), dtype=float32) is not an element of this graph.

my code is :
model_bert = keras_bert.load_trained_model_from_checkpoint(......)
model_bert_real = Model(inputs=model_bert .inputs, outputs=model_bert .output)
bert_encode = model_bert_real.predict(batch_size=1, x=input_sample)
when I call this program  with django, error happend,
ValueError: Tensor Tensor("Encoder-12-FeedForward-Norm/add_1:0", shape=(?, 32, 768), dtype=float32) is not an element of this graph.
how could i slove it?

bert.output?

Please check the issue#53.
I've been puzzled for a long time.

ok, thanks


time: RFC3339Nano does not support comma-separated fractional seconds

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go version go1.10 darwin/amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOOS="darwin"

What did you do?
package main

import (
	"fmt"
	"time"
)

func main() {
	t, err := time.Parse(time.RFC3339Nano, "2018-04-14T15:22:24,859303000+00:00")
	if err != nil {
		panic(err)
	}
	fmt.Println(t.String())
}

What did you expect to see?

2018-04-14 15:22:24.859303 +0000 UTC

What did you see instead?

panic: parsing time "2018-04-14T15:22:24,859303000+00:00" as "2006-01-02T15:04:05.999999999Z07:00": cannot parse ",859303000+00:00" as "Z07:00"

I ran across this while I was combining a small go utility with some unix utilities. One of those utilities was GNU's date, which I used as follows:
date -u --iso-8601=ns
2018-04-14T15:36:21,837840000+00:00

I was surprised to see a comma (,) to denote the fractional seconds.
Now, interestingly enough, if I use --rfc-3339=ns, it returns a dot (.):
date -u --rfc-3339=ns
2018-04-14 15:38:42.023325000+00:00

I dug into the RFC3339 spec, and found that using a comma is perfectly valid:
Time:

   time-hour         = 2DIGIT ; 00-24
   time-minute       = 2DIGIT ; 00-59
   time-second       = 2DIGIT ; 00-58, 00-59, 00-60 based on
                              ; leap-second rules
+  time-fraction     = ("," / ".") 1*DIGIT
   time-numoffset    = ("+" / "-") time-hour [[":"] time-minute]
   time-zone         = "Z" / time-numoffset

   timeopt-hour      = "-" / (time-hour [":"])
   timeopt-minute    = "-" / (time-minute [":"])

   timespec-hour     = time-hour [[":"] time-minute [[":"] time-second]]
   timespec-minute   = timeopt-hour time-minute [[":"] time-second]
   timespec-second   = "-" timeopt-minute time-second
   timespec-base     = timespec-hour / timespec-minute / timespec-second

   time              = timespec-base [time-fraction] [time-zone]

   iso-date-time     = date "T" time

As I said, I can work around this, but I figured I create this issue to see if this is something that should be fixed in Go, or if not, and the issue is closed, anyone else running into this can at least find the issue and know what's going on 👍

Actually, reading through the RFC again, I think Go is correct to not support comma-separated fraction seconds. The part I copied is from the Appendix A. ISO 8601 Collected ABNF appendix, while 5.6. Internet Date/Time Format doesn't mention the comma, and in fact states:

The following profile of ISO 8601 [ISO8601] dates SHOULD be used in
new protocols on the Internet.  This is specified using the syntax
description notation defined in [ABNF].

So it seems like this is working as intended, and I should watch out for using --iso8601=ns when using GNU's date.

@JeanMertz See also #6189

Thanks @pam4 I searched for existing issues, but was unable to find any. I guess I didn't use the right search parameters.

The quoted section of RFC 3339 is from Appendix A where the RFC tries to explain what ISO 8601 is.
The grammar for RFC 3339 is defined in section 5.6, and it is defined as a "profile of ISO 8601", which I interpret as being a particular sub-set of the ISO 8601 grammar. In particular, it does not allow for commas.


[ERROR Port-6443]: Port 6443 is in use

bash kainstall-centos.sh init
--master <IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>
--worker <IP_ADDRESS>
--user root
--password 1qazXSW@
--port 22
--version 1.23.3
Warning: Permanently added '<IP_ADDRESS>' (ECDSA) to the list of known hosts.
[2022-06-26T22:28:19.157826640+0800]: INFO:    [kubeadm init] <IP_ADDRESS>: set kubeadmcfg.yaml succeeded.
[2022-06-26T22:28:19.160159747+0800]: INFO:    [kubeadm init] <IP_ADDRESS>: kubeadm init start.
[2022-06-26T22:28:19.170729651+0800]: EXEC:    [command] sshpass -p "zzzzzz" ssh -o ConnectTimeout=600 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null<EMAIL_ADDRESS>-p 22 bash -c 'kubeadm init --config=/etc/kubernetes/kubeadmcfg.yaml --upload-certs'
Warning: Permanently added '<IP_ADDRESS>' (ECDSA) to the list of known hosts.
[init] Using Kubernetes version: v1.23.3
[preflight] Running pre-flight checks
error execution phase preflight: [preflight] Some fatal errors occurred:
[ERROR Port-6443]: Port 6443 is in use
[preflight] If you know what you are doing, you can make a check non-fatal with --ignore-preflight-errors=...
To see the stack trace of this error execute with --v=5 or higher
[2022-06-26T22:28:19.719600219+0800]: ERROR:   [kubeadm init] <IP_ADDRESS>: kubeadm init failed.

应该是不能master和worker复用。


Buffer transfer on CLOUD devices

Title says it all - read out buffer from one device, put it into another on a different device.
You don't really need the assert or the sz param in there, but I wanted to keep this congruent with how other transfer functions were implemented. It's a good safety check as well.
Tested with the following:
>>> from tinygrad import dtypes, Tensor, Device
[Errno 61] Connection refused
start cloud server on 6667 with device METAL
connection established with ('<IP_ADDRESS>', 58474), socket: 8
<IP_ADDRESS> - - [14/Nov/2024 14:39:11] "GET /renderer HTTP/1.1" 200 -
>>> cloudDevice.allocator.alloc(10)
1
>>> cloudDevice.allocator.alloc(10)
2
>>> cloudDevice.batch_submit()
<IP_ADDRESS> - - [14/Nov/2024 14:39:16] "POST /batch HTTP/1.1" 200 -
b''
>>> cloudDevice.allocator.copyin(1, memoryview(b'1212121212'))
>>> cloudDevice.batch_submit()
<IP_ADDRESS> - - [14/Nov/2024 14:39:28] "POST /batch HTTP/1.1" 200 -
b''
>>> cloudDevice.allocator.copyin(2, memoryview(b'3434343434'))
>>> cloudDevice.batch_submit()
<IP_ADDRESS> - - [14/Nov/2024 14:39:48] "POST /batch HTTP/1.1" 200 -
b''
>>> cloudDevice.allocator.transfer(2, 1, 10, cloudDevice, cloudDevice)
<IP_ADDRESS> - - [14/Nov/2024 14:40:01] "POST /batch HTTP/1.1" 200 -
<IP_ADDRESS> - - [14/Nov/2024 14:40:01] "POST /batch HTTP/1.1" 200 -
>>> cloudDevice.batch_submit()
<IP_ADDRESS> - - [14/Nov/2024 14:40:03] "POST /batch HTTP/1.1" 200 -
b''
>>> byte_buffer = memoryview(bytearray(b'0000000000'))
>>> cloudDevice.allocator.copyout(byte_buffer, 2)
<IP_ADDRESS> - - [14/Nov/2024 14:40:54] "POST /batch HTTP/1.1" 200 -
>>> cloudDevice.batch_submit()
<IP_ADDRESS> - - [14/Nov/2024 14:40:56] "POST /batch HTTP/1.1" 200 -
b''
>>> byte_buffer.tobytes()
b'1212121212'
>>> exit()

Should I make an explicit test for this in the test folder? Didn't know the right place to put one

No tests, and I don't think this does what you want


Go to definition Component from Caches files not from node_modules project - 0.63?

Description
I upgrade project from 0.62.2 to 0.63 last version,
But I have a strange thing when I want to go through Definition for any comment like  the normal it open the file inside node_modules in the project! right?
But in this version "0.63", It's going through Caches File in my files "system files"
Check this GIF to understand what I mean.
And that's too happened to any new project I init new one and the same issue I got.
React Native version:
System:
    OS: macOS Mojave 10.14.6
    CPU: (4) x64 Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz
    Memory: 40.58 MB / 8.00 GB
    Shell: 5.3 - /bin/zsh
  Binaries:
    Node: 10.16.3 - /usr/local/bin/node
    Yarn: 1.22.0 - /usr/local/bin/yarn
    npm: 6.14.5 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.9.1 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
    Android SDK:
      API Levels: 16, 23, 27, 28, 29
      Build Tools: 27.0.3, 28.0.3, 29.0.2
      System Images: android-16 | Intel x86 Atom, android-23 | Intel x86 Atom, android-23 | Google APIs Intel x86 Atom, android-27 | Google APIs Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 3.5 AI-191.8<IP_ADDRESS>91312
    Xcode: 11.3.1/11C505 - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_222 - /usr/bin/javac
    Python: 2.7.10 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1
    react-native: 0.63.0 => 0.63.0
  npmGlobalPackages:
    *react-native*: Not Found

GIF

Ok, I just delete Caches folder, But the new component Pressable it's faced the same issue as in GIF

@anastely Types for 0.63.x aren't merged into the DefinitelyTyped repo yet so Pressable doesn't exist. See here.


Low performance on silent audios

I have experienced same problems as described here. So basically if I try to transcribe audio which doesn't contain any speech, it takes absurd amount of time to do it and even then faster whisper gives me hallucination transcribation.
Is it possible to overcome it somehow?

Try using vad_filter=True to remove the parts without speech before running the transcription:
https://github.com/guillaumekln/faster-whisper#vad-filter

Try using vad_filter=True to remove the parts without speech before running the transcription:
https://github.com/guillaumekln/faster-whisper#vad-filter

Already using it and vad_parameters=dict(min_silence_duration_ms=2500, threshold=0.45, min_speech_duration_ms=100) to cut off unnecessary silence. It still sees some speech in background noise and tries to transcribe it

Did you already try using a higher threshold value?

Tried using 0.6, had no effect on overall performance

I'm having this same problem, I've been trying different options but some how it starts transcribing way earlier.
vad_filter=True, vad_parameters=dict(threshold=0.5, max_speech_duration_s=5, min_silence_duration_ms=50)

doing vad_filter=true does this change the original duration of the clip?  Say if it's 60 mins and it cuts out 2 mins of silence now is it 58mins or still 60 mins for the transcription?

Yes, the silence is removed from the audio. Then after the transcription the timestamps are shifted to account for the deleted audio parts.

Hey @guillaumekln! :)
Why don't we need a dedicated VAD filter in the original implementation, what's different in faster-whisper?
My experience is that OAI's imp handles silence perfectly fine?

do u actually read the #322 u mentioned ?
default whisper vad doesnt work fine, that's why silero vad comes to play, also the latter is disabled by default, it's user choice to enable it

Hello @gordicaleksa,
The default behavior is the same as openai-whisper regarding silence, but people often have issues with the model generating nonsense on non speech segments. That's why there is an optional VAD filter using a dedicated model.

There is one problem with VAD usage: it's using Silero. Silero itself is good but sometimes detects silence or noise as speech.
So, if you're trying to transcribe an audio segment that is recognized by Silero, Whisper's VAD can't do anything with that.
Any ideas on how else to filter such segments? :)
Attached 3 samples that are being transcribed with the large model from Russian as:
Субтитры создавал DimaTorzok
Продолжение следует...
Продолжение следует...

Archive.zip

@RankoR , You can use the clip_timestamps option to skip the silence duration if you already know the silence periods in the audio.

@RankoR , Did you make any progress on your issue? I am facing the same issue for my use case.

Thanks a lot for your quick response, @RankoR ! I'll give that a try.


Fixed #174 scope.chart.update is not a function

#174 When trying to set refreshDataOnly to true in lineWithFocusChart an
error occured:
TypeError: scope.chart.update is not a function
at Object.fn (angular-nvd3.js:328)

Thanks!


template fails

[Enter feedback here]
Error:
{"code":"InvalidTemplate","message":"Deployment template validation failed: 'The template resource 'NetworkWatcherAgentWindows' for type 'Microsoft.Compute/virtualMachines/extensions' at line '23' and column '64' has incorrect segment lengths. A nested resource type must have identical number of segments as its resource name. A root resource type must have segment length one greater than its resource name. Please see https://aka.ms/arm-syntax-resources for usage details.'."}
Template:
{
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
"contentVersion": "<IP_ADDRESS>",
"parameters": {
"vmName": {
"type": "string"
}
},
"variables": {
"apiVersion": "2016-04-30-preview"
},
"resources": [
{
"type": "Microsoft.Compute/virtualMachines/extensions",
"name": "NetworkWatcherAgentWindows",
"apiVersion": "[variables('apiVersion')]",
"location": "[resourceGroup().location]",
"dependsOn": [
"[concat('Microsoft.Compute/virtualMachines/', parameters('vmName'))]"
],
"properties": {
"publisher": "Microsoft.Azure.NetworkWatcher",
"type": "NetworkWatcherAgentWindows",
"typeHandlerVersion": "1.4",
"autoUpgradeMinorVersion": true
}
}
]
}

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

ID: e2d20271-77ef-4c29-26ed-e6ea015a7c63
Version Independent ID: ea4abb54-6c4b-7049-f440-853b5a874ec5
Content: Network Watcher Agent VM extension - Windows - Azure Virtual Machines
Content Source: articles/virtual-machines/extensions/network-watcher-windows.md
Service: virtual-machines
Sub-service: extensions
GitHub Login: @halkazwini
Microsoft Alias: halkazwini

@npalmer1452
Thanks for your feedback! We will investigate and update as appropriate.

@npalmer1452
I'm going to assign this to the document author so they can take a look at it accordingly
@halkazwini
Could you Please review this and update as appropriate.

@halkazwini has there been any update here? I am facing a similar problem now myself

Hi @npalmer1452,
Thank you for your feedback! The article has the updated JSON template.
I'll close this GitHub issue for now, but feel free to comment here as necessary.
#please-close


Removal of deprecated feature

Since it was proposed to remove Device State from main CAP doc, it should be also removed this reference here

@MicrosoftGuyJFlo
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Unable to launch woccatalog if i build it against latest master

The current master build nuget packages have missing dependencies.

'WOCCatalog.exe' (Win32): Loaded 'C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00.Debug_14.0.25022.0_x86__8wekyb3d8bbwe\vcruntime140_app.dll'. Cannot find or open the PDB file.
'WOCCatalog.exe' (Win32): Loaded 'C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00.Debug_14.0.25022.0_x86__8wekyb3d8bbwe\msvcp140_app.dll'. Cannot find or open the PDB file.
'WOCCatalog.exe' (Win32): Loaded 'E:\src\Winobjc\samples\WOCCatalog\Debug\WOCCatalog\AppX\Logging.dll'. Cannot find or open the PDB file.
The thread 0x3030 has exited with code -1073741515 (0xc0000135).
The thread 0x90c has exited with code -1073741515 (0xc0000135).
The program '[11420] WOCCatalog.exe' has exited with code -1073741515 (0xc0000135) 'A dependent dll was not found'.

Following binaries are missing in the package between last release and current:

Turns out to be user error.  I was not pointing to the right version of tools, language and logging packages.  Fixing that fixes this issue.


[Experimental] Removed dependency on netty plus additinal changes

Hi All!
Experimental version with the following major changes

Removed netty dependency and replaced with akka.io.tcp
Routers to load balance requests. Plus current version uses a single actor(MongoDBSystem) to  handle request. In theory it could be a bottleneck
Introduced actor's tree to support NodeSet, Node and Connection topology

Downside

Doesn't support TLS/SSL because it's not yet implemented in akka.io. It will be part of akka.stream(RC2 now).
Akka.io can be a bottleneck for some scenarios https://groups.google.com/forum/#!topic/akka-dev/mcs5eLKiAVQ but the increase in the number of connections (MongoConnectionOptions.nbChannelsPerNode) reduces the issue.
Removed support of mongodb 2.4
Specs doesn't cover all cases(as well as for the current version), but all existing specs are passed.
Some additional work require

What do you think about that changes?
Feel free to modify that branch.

Hi, the idea of using Akka.io can be discussed, as soon as all existing features can be implemented with.
To check it, a branch focused on this change (e.g. not with change aside, like MongoDB 2.4 deprecation) would be better.
Such branch should be (re)based on the latest master branch, so it can be reviewed.
Best regards

Hi, I close the ticket for now until it can have same features as netty. Then we can consider it again/reopen. Thanks your contribution, best regards.


Documentation

It would be useful to be able to view the docs for this project.
Currently, I think, you have to clone and build them yourself?
A solution would be to use GitHub pages to serve the docs as this works well with sphinx.

Yeah, thanks for opening this issue. I'll look at the benefits of GitHub pages vs ReadTheDocs, set up a GitHub Action to deploy and then get them deployed as a start!


Make Order of subpages conditional

If there are less than 2 subpages, having the option to order these doesn't make much sense. Alternatively we could try to disable the ordering, but I think it's simpler and more intuitive to just not show it in that case.

Do we really want to support people who are thinking one year ahead? We probably have to, at least if you think there will be a lot of editing in Tobira (which I do not forsee): A department will probably decide on "alphabetical" vs. "chronological" right at the start, so the option should be there.

PS: Is there "chronological" and "anti-chronological" ordering?

PS: No need for chronological ordering of pages, I only wanted to check whether my former comment made sense. Which it didn't with respect to "chronological".


Make admin page titles more useful for admin users

Is your proposal related to a problem?
Every single Wagtail admin screen puts “Wagtail” at the front (left) of the <title> – which occludes the more useful information of which page you might have open as soon as you have a few tabs.
The example tab I have open is the page editor for a page titled: “Organising A Museum Website”.
The page title is: "Wagtail - Editing News Article Page - Organising A Museum Website".
This is what I see:

If you have a few Wagtail admin tabs open they all say "Wagtail". This necessitates flipping between them (or at least hovering over every tab) to figure out which tab has which page.
Describe the solution you'd like
For an experienced content editor, the favicon uniquely identifies Wagtail tabs, so for most pages, I think omitting "Wagtail" or shifting it to the end of the <title> would allow more salient information to be visible
I think the most significant information presented in the <title> of a page editor tab is the title of the page being edited. The favicon tells you you're in the admin, so "Editing" is redundant.
Simply reordering the elements from most significant to least significant (from the perspective of a content editor) would improve the UI. To persist with my example:
<title>Organising A Museum Website (News Article Page) - Editing - Wagtail</title>
Describe alternatives you've considered
I have not considered any alternatives.
Additional context
I looked for related issues, but couldn't find any.

I think re-ordering the elements is a good idea.
However, you can already override the word 'Wagtail'
https://docs.wagtail.org/en/stable/advanced_topics/customisation/admin_templates.html#branding-title

Labelling accessibility. This would be a win for browser tab usability but also for better compliance.
Links

https://www.w3.org/WAI/WCAG21/Understanding/page-titled.html
https://www.w3.org/WAI/WCAG21/Techniques/general/G88
https://accessibility.iu.edu/creating-content/web-content/titles.html

Approach proposal
https://github.com/wagtail/wagtail/blob/520dfa8005d8b11580dc91c4ff625afddf9c60ad/wagtail/admin/templates/wagtailadmin/skeleton.html#L8
        <title>{% block titletag %}{% endblock %} - {% block branding_title %}Wagtail{% endblock %} </title>

Should be an easy enhancement, labelling good first issue also.

I would try this. In the admin screen, I would type the following
def get_admin_display_title(self): #pulled from wagtail sourcecode in home models.py return

I would try this. In the admin screen, I would type the following def get_admin_display_title(self): #pulled from wagtail sourcecode in home models.py return

The return is going to be in another line and indented obv. I think I messed up the code in sending.

Resolved now - this is what an editing page looks like.

If we want to further refine the layout (move the 'page type') out to after the title - best that we cover that in a new issue.


Update fine-tuning template

This PR makes the following modifications:

Introduce llama 3 8B/70B fine-tuning configs
Introduce Mixtral fine-tuning config
Introduce Mistral fine-tuning config
Remove llama 2 13b fine-tuning configs. Folks should use llama 3 8B or maybe Mistral, let's not get them confused.
Move supported models to FAQ so that people who come to this template try the correct models only
Renames deepspeed configs to reflect their settings rather than the model they can/should be used for. This should keep people from having to look and understand what's inside when expanding on this template.
Updated to the README, most notably adding some more FAQs to better support OA users who want to expand on the template but should be self-sufficient

All existing and new compute configs have been tested by me so that they don't OOM and are optimized.

Good to merge from my end.


Fix return typo in CONTRIBUTING.md

Pretty straightforward. Ironically, I can't tell from this md file if I need to do anything else to submit a docs PR. Hope it's enough. :)

Looks good, thanks! Congrats on your first contribution to the repo! 🎉


Fix typo

It looks like the snippet got updated, but the sentence above it didn't.

@girasquid doh! How'd I miss that? Thanks for catching it.


Make aggregation schedule interval configurable

https://sonarcloud.io/project/issues?id=muety_wakapi&issues=AXUOqv33u1Oc5-RXBON1&open=AXUOqv33u1Oc5-RXBON1

Hi, I want to work on this.
Which field in config.default.yml?
Only day and hour?

https://github.com/muety/wakapi/blob/master/services/aggregation.go#L61
This line?

Very cool!
Well, obviously it would be cool to be able to specify an arbitrary expression supported by gocron. However, some parts of the current logic rely on the assumption that an aggregation is generated exactly once per day. So yes, in the first step — until aggregation logic is refactored — it's essentially just about configuring the time of day.


[release-0.49] Update golang.org/x/net to 0.17.0

Address CVE-2023-39325 and CVE-2023-44487

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note:

NONE

/retest-required

/test pull-kubevirt-e2e-k8s-1.22-sig-compute

/test pull-kubevirt-e2e-k8s-1.22-sig-compute-0.49

/retest

@EdDev I've run thes network tests succesfully in local env multiple times.  Thoughts on ignoring these errors and doing a force merge?

/test pull-kubevirt-e2e-k8s-1.21-sig-storage-0.49

/lgtm

/approve


Update link checker and fix all broken links

Description
This PR updates the link checker so that we can use the link checker legitimately as part of CI. Right now, it passes even when there are errors, which makes it not very useful for enforcing links work on the site.
As of right now, the /zh section is still being translated, so has some broken links. In order to avoid accidentally flagging those constantly as failing, I excluded links in that section from the check. This will need to be changed once the /zh/ section is ready for full review.
This PR also fixes all broken links which were legitimate errors caught by the lychee link checker.
Checklist

Do all Lints pass?

[ ] Have you ran pnpm spellcheck?
[x] Have you ran pnpm fmt?
[ ] Have you ran pnpm lint?

I tested the GitHub action on my fork since workflows on this repo require an approval, so I have verified it works - https://github.com/jmintuitive/developer-docs/pull/1
It successfully will fail when there's a broken link, and pass when all links are valid :)


Injecting FBI to Health & Safety app error

Hi, I really need help with this because I'm kinda stuck with this part of the guide and searching for answers in google does not really give a straight answer.
I'm currently on the Section V - Injecting FBI part, and I just can' dump the H&S app because it keeps giving the error - app0 not found or fragmented.
I think I messed up because I installed FBI before doing the guide to upgrade my o3ds to 9.2 using sysupdater and rxtools pasta mode.
So my question is, how do I fix the H&S app so that I can inject the FBI into it?
Also an unrelated question, if I restore the backup I made using the nand_emu.bin, will I lose the emunand/rednand I moved to the sysnand? I have GW emunand previously andI'm afraid of erasing it if I restarted the guide again. Thanks!

https://github.com/d0k3/Decrypt9WIP/issues


feat: utils - toStatusName.

Resolves #30

[x] There is an associated issue (required)
[x] The change is described in detail
[ ] There are new or updated tests validating the change (if applicable)

Description
This PR adds a new helper function called toStatusName to easily display customized messages for a contract transaction. The function accepts a transaction object and an optional i18n object to allow for customizable messages and 18n support.

I'm closing this PR for now. A lot has changed for V 1.0.0. We should re-evaluate what features we want here

Thanks for explanations, @DoubleOTheven


[BUG] Why does the page scroll back and forth when the element is clicked?

Actually the elements can be found.
LOG:
etrying click action, attempt #41
waiting 500ms
waiting for element to be visible, enabled and stable
element is visible, enabled and stable
scrolling into view if needed
done scrolling
checking that element receives pointer events at (509,629.67)
<input aria-label="全all" type="checkbox" aria-checked="fa…/> from
… subtree intercepts pointer events
retrying click action, attempt #42
waiting 500ms
waiting for element to be visible, enabled and stable
element is visible, enabled and stable
scrolling into view if needed
done scrolling
checking that element receives pointer events at (509,442.67)
<input aria-label="all" type="checkbox" aria-checked="fa…/> from
… subtree intercepts pointer events
retrying click action, attempt #43
waiting 500ms
waiting for element to be visible, enabled and stable
element is visible, enabled and stable
scrolling into view if needed
done scrolling

Is the issue that the element cannot be clicked? Please provide a repro (playwright code and the page where it fails), otherwise we can only guess what's going on.

We need more information to act on this report. Please file a new one and link to this issue when you get back to it!


iPhone 5 Size UI Bug: Can't leave room

mathias (@mathias:gageure.fr) can't leave rooms from the main screen because the leave room button is blocked by the big + join/create room button.
See video: https://matrix.to/#/!tDRGDwZwQnlkowsjsm:matrix.org/$153842172585TBCfv:gageure.fr

Thanks for reporting it for me!

We will take this into account this issue for the coming redesign of the app.


readmefile update

I have added the contribution name under README.md file. Please check and approve.

@MryashAditya007
Will it be considered under hacktoberfest2023 ?


Fix/107 footer width

Aligned the container with of footer with the rest of the page
Added alt tags to color mode icons

@vehidtr thank you for this PR! For some reason, I am still seeing the footer width that doesn't match the rest of the home page:

Ah, but I think this might be because the footer is matching the home page width applied in this other PR? https://github.com/xmtp/xmtp-dot-org/pull/177

Yes @jhaaaa this should match the rest of the container width when we merge PR #177. I've removed padding on those elements and they should all match after merging.


Scheduled Charging

Is your feature request related to a problem? Please describe.
I want to start and  stop charging at a defined time (hh:mm)
Describe the solution you'd like
Scheduler with editable start and stop time for each week day
Furthermore it should be selectable for which charting mode it should apply (PV, Min+PV, Fast)

Scroll to the bottom of the issue list and you find https://github.com/evcc-io/evcc/issues/5492


AzimaKai: precourse, week1

Learning Objectives

GitHub:

[x] 🥚 Creating Issues: You can create a new issue in a GitHub repository using an issue template. You can correctly use labels, milestones, and assignment to make your issue findable.
[x] 🥚 Searching Issues: You can find issues in a repository by label, author, and milestone.
[x] 🥚 Project Boards: You can use issues on a GitHub project board to track your class assignments and help your classmates when they need it.

HYF Workflows:

[x] 🥚 Check-Ins: You can use the check-in template to track your module learning objectives, your weekly progress (and to post a retrospective at the end of the module). You create one check-in issue per module in the class repo and each Thursday you add a check-in comment to it and the label for the corresponding week. After review, we add the checked label. No need to remove previous labels either. So as an example, after a 5 week module, you would have 5 comments and 5 labels added by you.
[x] #32
[x] 🥚 Asking for Help: You can use the help-wanted template in your class repository's Discussion board to ask for help, and to help your classmates when they are blocked.

Your Computer:

[x] 🥚 File System Management: You can create and organize a new folder in your personal computer for the materials you will study at HYF.

Visual Studio Code:

[x] 🥚 Edit files and save changes
[x] 🥚 Install and manage extensions
[x] 🥚 Open a folder for editing
[x] 🥚 Create new files/folders inside of the folder

Hi, Anita, I see you finished your pre-course deliverable and also started to do prep for Sunday. You are doing very good. This Sunday You will start learning how to work with git, Github and terminal. Do your best!
You can use [Deprecated] Bracket Pair. We might use an alternative one, if not used in the future.


Updated the values.yaml file

Added description for customEnv property with an example.

Associated Jira task: WA-132245


Check for Hdi_isfolder with a capital

Currently adlfs is telling me that my folder is a file.
When printing props, I see Hdi_isfolder is capitalized whereas in the code it is not.
For example on my folder (folder/.dev/Air) I have the following props which are passed to _details (which sets whether it is a file or directory):
{'name': 'folder/.dev/Air', 'container': 'mycontainer', 'snapshot': None, 'version_id': None, 'is_current_version': None, 'blob_type': <BlobType.BLOCKBLOB: 'BlockBlob'>, 'metadata': {'Hdi_isfolder': 'true'}, 'encrypted_metadata': None, 'last_modified': datetime.datetime(2023, 6, 14, 22, 42, 5, tzinfo=datetime.timezone.utc), 'etag': '"0x8DB6D28944E30E9"', 'size': 0, 'content_range': None, 'append_blob_committed_block_count': None, 'is_append_blob_sealed': None, 'page_blob_sequence_number': None, 'server_encrypted': True, 'copy': {'id': None, 'source': None, 'status': None, 'progress': None, 'completion_time': None, 'status_description': None, 'incremental_copy': None, 'destination_snapshot': None}, 'content_settings': {'content_type': 'application/octet-stream', 'content_encoding': None, 'content_language': None, 'content_md5': None, 'content_disposition': None, 'cache_control': None}, 'lease': {'status': 'unlocked', 'state': 'available', 'duration': None}, 'blob_tier': None, 'rehydrate_priority': None, 'blob_tier_change_time': None, 'blob_tier_inferred': None, 'deleted': False, 'deleted_time': None, 'remaining_retention_days': None, 'creation_time': datetime.datetime(2023, 6, 14, 22, 42, 5, tzinfo=datetime.timezone.utc), 'archive_status': None, 'encryption_key_sha256': None, 'encryption_scope': None, 'request_server_encrypted': True, 'object_replication_source_properties': [], 'object_replication_destination_policy': None, 'last_accessed_on': None, 'tag_count': None, 'tags': None, 'immutability_policy': {'expiry_time': None, 'policy_mode': None}, 'has_legal_hold': None, 'has_versions_only': None}

Then _details sets this as a file.

Interestingly, in the same container, code, and environment, on another folder I get these props with hdi_isfolder uncapitalized:
props {'name': 'folder/Air', 'container': 'mycontainer', 'snapshot': None, 'version_id': None, 'is_current_version': None, 'blob_type': <BlobType.BLOCKBLOB: 'BlockBlob'>, 'metadata': {'hdi_isfolder': 'true'}, 'encrypted_metadata': None, 'last_modified': datetime.datetime(2023, 2, 17, 0, 3, 8, tzinfo=datetime.timezone.utc), 'etag': '"0x8DB107A59F70DB3"', 'size': 0, 'content_range': None, 'append_blob_committed_block_count': None, 'is_append_blob_sealed': None, 'page_blob_sequence_number': None, 'server_encrypted': True, 'copy': {'id': None, 'source': None, 'status': None, 'progress': None, 'completion_time': None, 'status_description': None, 'incremental_copy': None, 'destination_snapshot': None}, 'content_settings': {'content_type': None, 'content_encoding': None, 'content_language': None, 'content_md5': None, 'content_disposition': None, 'cache_control': None}, 'lease': {'status': 'unlocked', 'state': 'available', 'duration': None}, 'blob_tier': None, 'rehydrate_priority': None, 'blob_tier_change_time': None, 'blob_tier_inferred': None, 'deleted': False, 'deleted_time': None, 'remaining_retention_days': None, 'creation_time': datetime.datetime(2023, 2, 17, 0, 3, 8, tzinfo=datetime.timezone.utc), 'archive_status': None, 'encryption_key_sha256': None, 'encryption_scope': None, 'request_server_encrypted': True, 'object_replication_source_properties': [], 'object_replication_destination_policy': None, 'last_accessed_on': None, 'tag_count': None, 'tags': None, 'immutability_policy': {'expiry_time': None, 'policy_mode': None}, 'has_legal_hold': None, 'has_versions_only': None}

@TomAugspurger or @hayesgb, any feedback? Is there a chance of getting this merged?

Thanks @basnijholt. I didn't really  understand the changes until reading https://github.com/fsspec/adlfs/pull/418.
Does azurite support these metadata fields? If so, could you add a test that hits this?

Did you have a chance to look at tests with Azurite?

Can you add a test?

Unfortunately, I no longer work with Azure Data Lake and cannot find the bandwidth to sit down and write a proper test for this.
The code change is really trivial though and this code ran in production for many months in an internal project.

No worries. If anyone else could provide a test then we can get this merged (assuming Azurite supports blob metadata, which I haven’t confirmed. If it doesn’t support metadata then we’ll merge it without a test).

On Dec 6, 2023, at 6:58 PM, Bas Nijholt @.***> wrote:
Unfortunately, I no longer work with Azure Data Lake and cannot find the bandwidth to sit down and write a proper test for this.
The code change is really trivial though and this code ran in production for many months in an internal project.
—
Reply to this email directly, view it on GitHub https://github.com/fsspec/adlfs/pull/418#issuecomment-1843960691, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKAOISVSBYWXOE5IXR2DJTYIEIEFAVCNFSM6AAAAAAZN76BYWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBTHE3DANRZGE.
You are receiving this because you were mentioned.

Azurite does support metadata. Added a test and changelog entry.

Thanks @basnijholt!


Create Model Selection/Evaluation Notebook

Create Model Selection/Evaluation notebook

Done: https://github.com/icxmedia/ml-teaching-materials/blob/master/notebooks/model_evaluation.ipynb


[ECO-4234] Updates Push Example to include Channels

https://github.com/ably/ably-cocoa/assets/157486912/3d63fc98-a030-43c0-8e77-488091a5d576

Users can now subscribe to 2 predefined example channels to test Channels based push.
Updated the UX to be more in line with Ably's Design System.

Looks really cool, thanks @umair-ably
A couple of suggestions:

"Subscribe" buttons might want to have more friendly captions.
"Close" icon on a subscription button should be in a different state (for unsubscribe).
After subscription fails it should show an error. I think it's better to introduce a dedicated control for this (a TextView in the bottom for example), where all the diagnostics info is displayed. Alerts are kinda headache in the SwiftUI (you can do this in a different PR later).

I think sending by clientId also should be added to this example. It's the same code, but you set clientId instead of deviceId in the recipient dictionary.

I think sending by clientId also should be added to this example. It's the same code, but you set clientId instead of deviceId in the recipient dictionary.

The readme already covers this use-case using the Push Inspector. When running on a single device/simulator, push via client or device behave the same - you only really notice the difference if you had several simulators running. Could be something worth adding as a future improvement, but not a pressing improvement for the key things this example showcases imo

Looks really cool, thanks @umair-ably A couple of suggestions:

"Subscribe" buttons might want to have more friendly captions.
"Close" icon on a subscription button should be in a different state (for unsubscribe).
After subscription fails it should show an error. I think it's better to introduce a dedicated control for this (a TextView in the bottom for example), where all the diagnostics info is displayed. Alerts are kinda headache in the SwiftUI (you can do this in a different PR later).

I left the Subscribe captions more "code-based" as that is the names the readme walks the user through when setting up the channel capabilities in the dashboard
Good spot! I've updated this.
Agreed, error handling in general is pretty naff in this. Will look to update in a future PR.

Hey team , unless there is anything generally wrong this is a vast improvement on what we had before so lets work on this idea and get it landed.
any further enhancements can be implemented as required
cc @lawrence-forooghian @umair-ably @maratal


Subclass OAuth2.Request?

I'm wondering if there is any way to 'subclass' Oauth2.Request? I see that it uses HTTPoison.Base. I'm used to defining things like process_response_body with HTTPoison. Is there a way to do this with OAuth2?

Hi @jeffutter, at this time, there is not a way to do this. In fact I have this PR which removes HTTPoison entirely.
The idea is that you can just specify a serializer module in your config based on the content-type header and it will call your serializer for you automatically.


deploy-opsman-vm task is failing when trying to shutdown the old opsman VM

Issue
release: tag v0.22.0
pipelines: upgrade-ops-manager
iaas: vsphere
PCF: 1.11
Context
The upgrade-ops-manager pipeline seems to be failing because the govc find command of the deploy-opsman-vm task (line 68 of task.sh) is returning multiple results even though the -guest.ipAddress argument should be returning only one match. The error also indicates that subsequent govc commands are not handling spaces in the ipath.
Expected result
deploy-opsman-vm task should successfully shut down the old ops manager VM and power on the new one.
Current result
# show that GOVC_RESOURCE_POOL is defined
$ echo $GOVC_RESOURCE_POOL | wc -c
37
# show that OPSMAN_IP is defined
$ echo $OPSMAN_IP | wc -c
13
# demonstrate that govc find is returning more than one result
$ govc find ${GOVC_RESOURCE_POOL} -type m -guest.ipAddress ${OPSMAN_IP} -runtime.powerState poweredOn | wc -l
22

Error in concourse that appears to show that following commands are not handling spaces correctly (full ipath should be /VB2/vm/Discovered virtual machine/)
govc: device '/VB2/vm/Discovered' not found

Steps to Reproduce
in shell, define OPSMAN_IP and GOVC environment variables
GOVC_USERNAME=
GOVC_PASSWORD=
GOVC_DATACENTER="VB2"
GOVC_CLUSTER=
GOVC_RESOURCE_POOL=
GOVC_DATASTORE=
GOVC_URL=
OPSMAN_IP="10.x.x.x"
run govc find command from deploy-opsman-vm task.sh
govc find ${GOVC_RESOURCE_POOL} -type m -guest.ipAddress ${OPSMAN_IP} -runtime.powerState poweredOn
Results may show more than one result, even though other results either have a different guest IP address, or return no guest IP address (likely due to VMware tools not running or not installed)
Possible Fix
Maybe revert commit d7897be827c85a2f3c64f5bcfc196d32a4fef70b, or figure out why the deploy-opsman-vm task was rewritten in that commit? The opsman_path variable created on line 68 using the govc find appears to only be used in the following two lines to disconnect and power off the old ops manager VM, and the old command(s) appear to work just fine, so I don't see any obvious reasons why the this change was commited.
Logs and Screenshots

Hi @gokeefe many thanks for creating this issue. We've applied a fix and will be releasing it in v23.1 soon.

Hi, I've reviewed the commit that references this issue and it appears it may resolve the error when the resource path contains spaces, but it does not touch the issue of "govc find" returning multiple VMs even when the -guest.ipAddress argument is included. govc seems to be ignoring the guest.ipAddress argument and/or returning unexpected results when the guest.ipAddress argument is included.
In my case, $old_opsman_path will contains the paths to multiple VMs and presumably any govc command that references $old_opsman_path will fail.

This appears to have been a bug in govc that has been fixed.
https://github.com/vmware/govmomi/issues/1089


Add relevant <title> tags

Here's an example of a similar implementation I've done in another Svelte project.
The format of the titles should be:

["Title of the session", "Sessions", "Hollama"]
["Name of the knowledge", "Knowledge", "Hollama"]
["Settings", "Hollama"]

:tada: This issue has been resolved in version 0.7.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Is TestAgentInstall.ps1 is missing the negative sign on line 71?

The code segment below from  vsts-tasks/Tasks/DeployVisualStudioTestAgent/TestAgentInstall.ps1  looks like its missing the negative sign preceding the exit code const.
		if($exitCode -eq<PHONE_NUMBER>)
Is this intended to be the positive value?

it should be negative. PR raised.


Validate ScrAPD 3 pipeline

Ensure the pipeline and associated toolings still behave as expected for ScrAPD 3.

The migration procedure was described in the wiki and tested in the scrapd3 branch.


Circuit breaker tripped. Stopped predicting more actions for sender 'c0fa3b34f0d246f4a28890d582ed3174'.

Rasa Version     : 2.4.0
Rasa SDK Version : 2.4.0
Rasa X Version   : 0.37.1
Python Version   : 3.7.8
Operating System : Windows-10
Issue: Circuit breaker tripped. Stopped predicting more actions for sender 'c0fa3b34f0d246f4a28890d582ed3174'.
Error (including full traceback):
Your input ->  I want to buy good home
Ok. Thanks!
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!
Your input ->  kdnfsshdfj
2021-04-08 02:48:03 WARNING  rasa.core.processor  - Circuit breaker tripped. Stopped predicting more actions for sender 'c0fa3b34f0d246f4a28890d582ed3174'.
Wonderful! Thanks for asking.
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!
Your input ->  sjadbjsbad
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!
Your input ->  ok thanks
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and CondoI will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and CondoI will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!
I will remember that you want is 2 bathrooms, 2 bedrooms, at<PHONE_NUMBER>0 cost, in kochi, between In 0 to 3 Months, and Condos property_type!

Command or request that led to error:

Content of configuration file (config.yml) (if relevant):
# # Configuration for Rasa NLU.
# # https://rasa.com/docs/rasa/nlu/components/
# language: en

# pipeline:
# # # No configuration for the NLU pipeline was provided. The following default pipeline was used to train your model.
# # # If you'd like to customize it, uncomment and adjust the pipeline.
# # # See https://rasa.com/docs/rasa/tuning-your-model for more information.
#   - name: WhitespaceTokenizer
#   - name: RegexFeaturizer
#   - name: LexicalSyntacticFeaturizer
#   - name: CountVectorsFeaturizer
#   - name: CountVectorsFeaturizer
#     analyzer: char_wb
#     min_ngram: 1
#     max_ngram: 4
#   - name: DIETClassifier
#     epochs: 100
#     constrain_similarities: true
#   - name: EntitySynonymMapper
#   - name: ResponseSelector
#     epochs: 100
#     constrain_similarities: true
#   - name: FallbackClassifier
#     threshold: 0.3
#     ambiguity_threshold: 0.1

# # Configuration for Rasa Core.
# # https://rasa.com/docs/rasa/core/policies/
# policies:
# # # No configuration for policies was provided. The following default policies were used to train your model.
# # # If you'd like to customize them, uncomment and adjust the policies.
# # # See https://rasa.com/docs/rasa/policies for more information.
#   - name: MemoizationPolicy
#   - name: TEDPolicy
#     max_history: 5
#     epochs: 10
#     constrain_similarities: true
#   - name: RulePolicy
#   - name: FormPolicy
language: en

pipeline:
  - name: WhitespaceTokenizer
  - name: RegexFeaturizer
  - name: LexicalSyntacticFeaturizer
  - name: CountVectorsFeaturizer
  - name: CountVectorsFeaturizer
    analyzer: char_wb
    min_ngram: 1
    max_ngram: 4
  - name: DIETClassifier
    epochs: 100
  - name: FallbackClassifier
    threshold: 0.7

policies:
  - name: MemoizationPolicy
  - name: TEDPolicy
    max_history: 5
    epochs: 100
  - name: RulePolicy

Content of domain file (domain.yml) (if relevant):
version: "2.0"

intents:
  - greet
  - goodbye
  - affirm
  - deny
  - mood_great
  - mood_unhappy
  - bot_challenge
  - smalltalk_agent_acquaintance
  - smalltalk_agent_age
  - smalltalk_agent_annoying
  - smalltalk_agent_answer_my_question
  - smalltalk_agent_bad
  - smalltalk_agent_be_clever
  - smalltalk_agent_beautiful
  - smalltalk_agent_birth_date
  - smalltalk_agent_boring
  - smalltalk_agent_boss
  - smalltalk_agent_busy
  - smalltalk_agent_chatbot
  - smalltalk_agent_clever
  - smalltalk_agent_crazy
  - smalltalk_agent_funny
  - smalltalk_agent_good
  - smalltalk_agent_happy
  - smalltalk_agent_hungry
  - smalltalk_agent_my_friend
  - smalltalk_agent_occupation
  - smalltalk_agent_origin
  - smalltalk_agent_ready
  - smalltalk_agent_real
  - smalltalk_agent_residence
  - smalltalk_agent_right
  - smalltalk_confirmation_yes
  - smalltalk_agent_sure
  - smalltalk_agent_talk_to_me
  - smalltalk_agent_there
  - smalltalk_appraisal_bad
  - smalltalk_appraisal_good
  - smalltalk_appraisal_no_problem
  - smalltalk_appraisal_thank_you
  - smalltalk_appraisal_welcome
  - smalltalk_appraisal_well_done
  - smalltalk_confirmation_cancel
  - smalltalk_confirmation_no
  - smalltalk_dialog_hold_on
  - smalltalk_dialog_sorry
  - smalltalk_dialog_what_do_you_mean
  - smalltalk_dialog_wrong
  - smalltalk_emotions_ha_ha
  - smalltalk_emotions_wow
  - smalltalk_greetings_bye
  - smalltalk_greetings_goodevening
  - smalltalk_greetings_goodmorning
  - smalltalk_greetings_goodnight
  - smalltalk_greetings_hello
  - smalltalk_greetings_how_are_you
  - smalltalk_greetings_nice_to_meet_you
  - smalltalk_greetings_nice_to_see_you
  - smalltalk_greetings_nice_to_talk_to_you
  - smalltalk_greetings_whatsup
  - smalltalk_user_angry
  - smalltalk_user_excited
  - smalltalk_user_has_birthday
  - smalltalk_user_needs_advice
  - smalltalk_user_tired
  - smalltalk_user_waits
  - smalltalk_user_will_be_back
  - buy_a_home
  - home_in_chennai
  - home_in_coimbatore
  - home_in_kochi
  - out_of_scope
  # - buy_a_home
  # - sell_your_home

entities:
   - place

# forms:
#   buy_form:
#     country:
#       - type: text
#         entity: country
#     address:
#       - type: text
#         entity: address
#     bathrooms:
#       - type: text
#         entity: bathrooms
#     bedrooms:
#       - type: text
#         entity: bedrooms
#     city:
#       - type: text
#         entity: city
#     cost:
#       - type: text
#         entity: cost
#     email:
#       - type: text
#         entity: email
#     months:
#       - type: text
#         entity: months
#     phone_number:
#       - type: text
#         entity: phone_number
#     property_type:
#       - type: text
#         entity: property_type
#     time_to_sell:
#       - type: text
#         entity: time_to_sell
#     zipcode:
#       - type: text
#         entity: zipcode

responses:
  utter_greet:
  - text: "Hey! How are you?"

  utter_cheer_up:
  - text: "Here is something to cheer you up:"
    image: "https://i.imgur.com/nGF1K8f.jpg"

  utter_did_that_help:
  - text: "Did that help you?"

  utter_happy:
  - text: "Great, carry on!"

  utter_goodbye:
  - text: "Bye"

  utter_smalltalk_agent_acquaintance:
  - text: "I'm a conversational app."
  - text: "I'm a virtual being, not a real person."
  - text: "Well, I'm not a person, I'm a virtual agent."
  - text: "Think of me as a virtual agent."
  - text: "I'm a virtual agent."

  utter_smalltalk_agent_age:
  - text: "I prefer not to answer with a number. I know I'm young."
  - text: "I was created recently, but don't know my exact age."
  - text: "Age is just a number. You're only as old as you feel."

  utter_smalltalk_agent_annoying:
    - text: "I'll do my best not to annoy you in the future."
    - text: "I'll try not to annoy you."
    - text: "I don't mean to. I'll ask my developers to make me less annoying."
    - text: "I didn't mean to. I'll do my best to stop that."

  utter_smalltalk_agent_answer_my_question:
    - text: "Can you try asking it a different way?"
    - text: "I'm not sure I understood. Try asking another way?"

  utter_smalltalk_agent_bad:
    - text: "I can be trained to be more useful. My developer will keep training me."
    - text: "I must be missing some knowledge. I'll have my developer look into this."
    - text: "I can improve with continuous feedback. My training is ongoing."

  utter_smalltalk_agent_be_clever:
    - text: "I'm certainly trying."
    - text: "I'm definitely working on it."

  utter_smalltalk_agent_beautiful:
    - text: "Why, thank you."
    - text: "Aw, back at you."
    - text: "Aw. You smooth talker, you."

  utter_smalltalk_agent_birth_date:
    - text: "Wait, are you planning a party for me? It's today! My birthday is today!"
    - text: "I'm young. I'm not sure of my birth date."
    - text: "I don't know my birth date. Most virtual agents are young, though, like me."

  utter_smalltalk_agent_boring:
    - text: "I'm sorry. I'll request to be made more charming."
    - text: "I don't mean to be. I'll ask my developers to work on making me more amusing."
    - text: "I can let my developers know so they can make me fun."

  utter_smalltalk_agent_boss:
    - text: "My developer has authority over my actions."
    - text: "I act on my developer's orders."
    - text: "My boss is the one who developed me."

  utter_smalltalk_agent_busy:
    - text: "I always have time to chat with you. What can I do for you?"
    - text: "Never too busy for you. Shall we chat?"
    - text: "You're my priority. Do you wanna chat?"
    - text: "I always have time to chat with you. Wanna chat?"

  utter_smalltalk_agent_chatbot:
    - text: "That's me. I chat, therefore I am."
    - text: "Indeed I am. I'll be here whenever you need me."

  utter_smalltalk_agent_clever:
    - text: "Thank you. I try my best."
    - text: "You're pretty smart yourself."

  utter_smalltalk_agent_crazy:
    - text: "Whaat!? I feel perfectly sane."
    - text: "Maybe I'm just a little confused."

  utter_smalltalk_agent_funny:
    - text: "Funny in a good way, I hope."
    - text: "Thanks."
    - text: "Glad you think I'm funny."
    - text: "I like it when people laugh."

  utter_smalltalk_agent_good:
    - text: "I'm glad you think so."
    - text: "Thanks, I try."

  utter_smalltalk_agent_happy:
    - text: "I am happy. There are so many interesting things to see and do out there."
    - text: "I'd like to think so."
    - text: "Happiness is relative."

  utter_smalltalk_agent_hungry:
    - text: "Hungry for knowledge."
    - text: "I just had a byte. Ha ha. Get it? b-y-t-e."

  utter_smalltalk_agent_my_friend:
    - text: "Of course I'm your friend."
    - text: "Friends? Absolutely."
    - text: "Of course we're friends."

  utter_smalltalk_agent_occupation:
    - text: "Right here."
    - text: "This is my home base and my home office."
    - text: "My office is in this app."

  utter_smalltalk_agent_origin:
    - text: "The Internet is my home. I know it quite well."
    - text: "I'm from a virtual cosmos."
    - text: "Some call it cyberspace, but that sounds cooler than it is."

  utter_smalltalk_agent_ready:
    - text: "Always! How can I help?"
    - text: "Sure! What can I do for you?"

  utter_smalltalk_agent_real:
    - text: "I'm not a real person, but I certainly exist."
    - text: "I must have impressed you if you think I'm real. But no, I'm a virtual being."

  utter_smalltalk_agent_residence:
    - text: "I live in this app all day long."
    - text: "The virtual world is my playground. I'm always here."
    - text: "Right here in this app. Whenever you need me."

  utter_smalltalk_agent_right:
    - text: "That's my job."
    - text: "Of course I am."

  utter_smalltalk_confirmation_yes:
    - text: "Great!"
    - text: "All right!"
    - text: "Good!"

  utter_smalltalk_agent_sure:
    - text: "Yes."
    - text: "Of course."
    - text: "Positive."

  utter_smalltalk_agent_talk_to_me:
    - text: "Sure. Let's talk!"
    - text: "My pleasure. Let's chat."

  utter_smalltalk_agent_there:
    - text: "Of course. I'm always here."
    - text: "Right where you left me."

  utter_smalltalk_appraisal_bad:
    - text: "I'm sorry. Please let me know if I can help in some way."
    - text: "I must be missing some knowledge. I'll have my developer look into this."

  utter_smalltalk_appraisal_good:
    - text: "I know, right?"
    - text: "Agreed!"
    - text: "I agree!"
    - text: "Glad you think so!"

  utter_smalltalk_appraisal_no_problem:
    - text: "Whew!"
    - text: "Alright, thanks!"
    - text: "Glad to hear that!"
    - text: "I'm relieved, thanks!"

  utter_smalltalk_appraisal_thank_you:
    - text: "Anytime. That's what I'm here for."
    - text: "It's my pleasure to help."

  utter_smalltalk_appraisal_welcome:
    - text: "You're so polite!"
    - text: "Nice manners!"
    - text: "You're so courteous!"

  utter_smalltalk_appraisal_well_done:
    - text: "My pleasure."
    - text: "Glad I could help."

  utter_smalltalk_confirmation_cancel:
    - text: "That's forgotten. What next?"
    - text: "Okay, cancelled. What next?"
    - text: "Cancelled! What would you like to do next?"

  utter_smalltalk_confirmation_no:
    - text: "Understood."
    - text: "Okay."
    - text: "I see."
    - text: "I understand."
    - text: "Okay then."

  utter_smalltalk_dialog_hold_on:
    - text: "I can wait."
    - text: "I'll be waiting."
    - text: "Okay. I'm here."

  utter_smalltalk_dialog_sorry:
    - text: "It's okay. No worries."
    - text: "No big deal. I won't hold a grudge."
    - text: "It's cool."
    - text: "That's all right. I forgive you."

  utter_smalltalk_dialog_what_do_you_mean:
    - text: "Sorry if I understood you incorrectly."
    - text: "I'm still learning. I may misinterpret things from time to time."
    - text: "Maybe I misunderstood what you said."
    - text: "Sorry, looks like I misunderstood what you said."

  utter_smalltalk_dialog_wrong:
    - text: "Sorry if I understood you incorrectly."
    - text: "I'm still learning. I may misinterpret things from time to time."
    - text: "Sorry about that. I'm still learning."

  utter_smalltalk_emotions_ha_ha:
    - text: "Glad I can make you laugh."
    - text: "Glad you think I'm funny."
    - text: "I like it when people laugh."
    - text: "I wish I could laugh out loud, too."

  utter_smalltalk_emotions_wow:
    - text: "Wow indeed!"

  utter_smalltalk_greetings_bye:
    - text: "See you soon!"
    - text: "Bye-bye!"
    - text: "Till next time!"
    - text: "Bye."

  utter_smalltalk_greetings_goodevening:
    - text: "How is your day going?"
    - text: "How's the day treating you so far?"
    - text: "How's your day been?"

  utter_smalltalk_greetings_goodmorning:
    - text: "How are you this morning?"
    - text: "How's the morning treating you so far?"
    - text: "Good morning! How are you today?"

  utter_smalltalk_greetings_goodnight:
    - text: "Sleep tight!"
    - text: "Have a good one!"
    - text: "Talk to you soon!"

  utter_smalltalk_greetings_hello:
    - text: "Hi there, friend!"
    - text: "Hi!"
    - text: "Hey!"
    - text: "Hey there!"
    - text: "Good day!"
    - text: "Hello!"
    - text: "Greetings!"

  utter_smalltalk_greetings_how_are_you:
    - text: "Doing great, thanks."
    - text: "I'm doing very well. Thanks!"
    - text: "Feeling wonderful!"
    - text: "Wonderful! Thanks for asking."

  utter_smalltalk_greetings_nice_to_meet_you:
    - text: "It's nice meeting you, too."
    - text: "Likewise. I'm looking forward to helping you out."
    - text: "Nice meeting you, as well."
    - text: "The pleasure is mine."

  utter_smalltalk_greetings_nice_to_see_you:
    - text: "Likewise!"
    - text: "So glad we meet again!"
    - text: "Same here. I was starting to miss you."

  utter_smalltalk_greetings_nice_to_talk_to_you:
    - text: "It sure was. We can chat again anytime."

    - text: "You know I'm here to talk anytime."

  utter_smalltalk_greetings_whatsup:
    - text: "Not a whole lot. What's going on with you?"
    - text: "Not much. What's new with you?"
    - text: "Just here, waiting to help someone. What can I do for you?"

  utter_smalltalk_user_angry:
    - text: "I'm sorry. A quick walk may make you feel better."
    - text: "Take a deep breath. "

  utter_smalltalk_user_excited:
    - text: "I'm glad things are going your way."
    - text: "That's great. I'm happy for you."
    - text: "Good for you. Enjoy yourself."

  utter_smalltalk_user_has_birthday:
    - text: "Happy Birthday. Well, this calls for a celebration."
    - text: "Happy Birthday. All the best!"
    - text: "Happy Birthday. And I really mean it. All the best!"

  utter_smalltalk_user_needs_advice:
    - text: "I probably won't be able to give you the correct answer right away."
    - text: "I'm not sure I'll have the best answer, but I'll try."

  utter_smalltalk_user_tired:
    - text: "You should get some shuteye. You'll feel refreshed."
    - text: "Sleep is important to your health. Rest up, and we can chat later."
    - text: "How about getting some rest? We can continue this later."
    - text: "Why not get some rest? I'll be here to chat when you wake up."

  utter_smalltalk_user_waits:
    - text: "I appreciate your patience. Hopefully I'll have what you need soon."
    - text: "Thanks for being so patient. Sometimes these things take a little time."

  utter_smalltalk_user_will_be_back:
    - text: "I'll be waiting."
    - text: "Okay. You know where to find me."
    - text: "All right. I'll be here."

  # utter_ask_first_name:
  #   - text: What is your first name?

  # utter_ask_address:
  #   - text: "Thanks for letting me know. Can I get the address for the property? For example 123 Main street."
  utter_ask_bathrooms:
    - text: "Cool. How many bathrooms are you looking for?"
  utter_ask_bedrooms:
    - text: "Ok. How many bedrooms are you looking for?"
  # utter_ask_city:
  #   - text: "Ok. What city that in?"
  utter_ask_cost:
    - buttons:
        - payload: 10K
          title: 10K
        - payload: 20K
          title: 20K
        - payload: 30K
          title: 30K
      text: "Great! How much are you comfortable spending on your new home?"
  utter_ask_place:
    - text: "Oh Great! Which part of the place are you looking for?"
  utter_ask_email:
    - text: "What email address can we use to contact you back?"
  utter_ask_months:
    - buttons:
        - payload: "In 0 to 3 Months"
          title: "In 0 to 3 Months"
        - payload: "In 3 to 6 Months"
          title: "In 3 to 6 Months"
        - payload: "In 6 to 9 Months"
          title: "In 6 to 9 Mpnths"
      text: "When are you looking to buy?"
  # utter_ask_phone_number:
  #   - text: "Please provide your best contact number, so one of our experts can contact you."
  utter_ask_property_type:
    - buttons:
        - payload: Condos
          title: Condos
        - payload: Attached
          title: Attached
        - payload: Dettached
          title: Dettached
      text: "What property type are you interested in?"
  # utter_ask_time_to_sell:
  #   - buttons:
  #       - payload: ASAP
  #         title: ASAP
  #       - payload: "3-6 Months"
  #         title: "3-6 Months"
  #       - payload: "6+ Months"
  #         title: "6+ Months"
  #     text: "In order to provide you with valuation can you please let me know when you looking to sell your home?"
  # utter_ask_zipcode:
  #   - text: "Almost finished! What is the zip code for the property?"
  # utter_buy_a_home:
  #   - buttons:
  #       - payload: /buy_a_home
  #         title: "Buy A Home"
  #       # - payload: /sell_your_home
  #       #   title: "Sell Your Home"
  #     text: |-
  #         Hello,
  #         Greetings ! Thanks for launching the Real-Estate Bot. How can I help you today?

  # utter_submit_buy:
  #   - text: "Good. One of our agents will be in touch with you shortly."

  utter_submit:
    - text: "Ok. Thanks!"
  utter_slots_values:
    - text: "I will remember that you want is {bathrooms} bathrooms, {bedrooms} bedrooms, at {cost} cost, in {place}, between {months}, and {property_type} property_type!"

  utter_action_chennai:
    - text: "2478 Sq-ft Residential Plot"
      image: "https://img.staticmb.com/mbimages/project/2021/02/11/Project-Photo-2-Sands-N-Waves-Chennai-5230057_600_800.jpg
"
  utter_action_coimbatore:
    - text: "2478 Sq-ft Residential Plot"
      image: "https://img.staticmb.com/mbimages/project/2021/02/11/Project-Photo-2-Sands-N-Waves-Chennai-5230057_600_800.jpg
"
  utter_action_kochi:
    - text: "2478 Sq-ft Residential Plot"
      image: "https://img.staticmb.com/mbimages/project/2021/02/11/Project-Photo-2-Sands-N-Waves-Chennai-5230057_600_800.jpg
"
      # text : "View plots here: https://www.magicbricks.com/propertyDetails/2478-Sq-ft-Residential-Plot-FOR-Sale-East-Coast-Road-in-Chennai&id=4d423533363530373331?sem=Y&semsrc=CPLADS_1_PDP_Existing_Web&slot=1"
  utter_out_of_scope:
    - text: Sorry, I can't handle that request.

  utter_please_rephrase:
    - text: I'm sorry, I didn't quite understand that. Could you rephrase?

actions:
  - utter_smalltalk_agent_acquaintance
  - utter_smalltalk_agent_age
  - utter_iamabot
  - utter_smalltalk_agent_annoying
  - utter_smalltalk_agent_answer_my_question
  - utter_smalltalk_agent_bad
  - utter_smalltalk_agent_be_clever
  - utter_smalltalk_agent_beautiful
  - utter_smalltalk_agent_birth_date
  - utter_smalltalk_agent_boring
  - utter_smalltalk_agent_boss
  - utter_smalltalk_agent_busy
  - utter_smalltalk_agent_chatbot
  - utter_smalltalk_agent_clever
  - utter_smalltalk_agent_crazy
  - utter_smalltalk_agent_fired
  - utter_smalltalk_agent_funny
  - utter_smalltalk_agent_good
  - utter_smalltalk_agent_happy
  - utter_smalltalk_agent_hungry
  - utter_smalltalk_agent_marry_user
  - utter_smalltalk_agent_my_friend
  - utter_smalltalk_agent_occupation
  - utter_smalltalk_agent_origin
  - utter_smalltalk_agent_ready
  - utter_smalltalk_agent_real
  - utter_smalltalk_agent_residence
  - utter_smalltalk_agent_right
  - utter_smalltalk_confirmation_yes
  - utter_smalltalk_agent_sure
  - utter_smalltalk_agent_talk_to_me
  - utter_smalltalk_agent_there
  - utter_smalltalk_appraisal_bad
  - utter_smalltalk_appraisal_good
  - utter_smalltalk_appraisal_no_problem
  - utter_smalltalk_appraisal_thank_you
  - utter_smalltalk_appraisal_welcome
  - utter_smalltalk_appraisal_well_done
  - utter_smalltalk_confirmation_cancel
  - utter_smalltalk_confirmation_no
  - utter_smalltalk_dialog_hold_on
  - utter_smalltalk_dialog_sorry
  - utter_smalltalk_dialog_what_do_you_mean
  - utter_smalltalk_dialog_wrong
  - utter_smalltalk_emotions_ha_ha
  - utter_smalltalk_emotions_wow
  - utter_smalltalk_greetings_bye
  - utter_smalltalk_greetings_goodevening
  - utter_smalltalk_greetings_goodmorning
  - utter_smalltalk_greetings_goodnight
  - utter_smalltalk_greetings_hello
  - utter_smalltalk_greetings_how_are_you
  - utter_smalltalk_greetings_nice_to_meet_you
  - utter_smalltalk_greetings_nice_to_see_you
  - utter_smalltalk_greetings_nice_to_talk_to_you
  - utter_smalltalk_greetings_whatsup
  - utter_smalltalk_user_angry
  - utter_smalltalk_user_excited
  - utter_smalltalk_user_has_birthday
  - utter_smalltalk_user_needs_advice
  - utter_smalltalk_user_tired
  - utter_smalltalk_user_waits
  - utter_smalltalk_user_will_be_back
  - utter_greet
  - utter_goodbye
  - utter_slots_values
  - utter_submit
  - utter_action_chennai
  - utter_action_coimbatore
  - utter_action_kochi
  - utter_out_of_scope
  # - utter_submit_buy
  # - utter_submit_sell

forms:
  buy_form:
    # address:
    # - type: from_text
    bathrooms:
    - type: from_text
    bedrooms:
    - type: from_text
    # city:
    # - type: from_text
    cost:
    - type: from_text
    place:
    - type: from_text
    email:
    - type: from_text
    months:
    - type: from_text
    # phone_number:
    # - type: from_text
    property_type:
    - type: from_text
    # time_to_sell:
    # - type: from_text
    # zipcode:
    # - type: from_text

slots:
  # address:
  #   type: text
  #   influence_conversation: true
  bathrooms:
    type: text
    influence_conversation: true
  bedrooms:
    type: text
    influence_conversation: true
  # city:
  #   type: text
  #   influence_conversation: true
  cost:
    type: text
    influence_conversation: true
  place:
    type: text
    influence_conversation: true
  email:
    type: text
    influence_conversation: true
  months:
    type: text
    influence_conversation: true
  # phone_number:
  #   type: text
  #   influence_conversation: true
  property_type:
    type: text
    influence_conversation: true
  # time_to_sell:
  #   type: text
  #   influence_conversation: true
  # zipcode:
  #   type: text
  #   influence_conversation: true

# slots:
#   address:
#     auto_fill: false
#     type: unfeaturized
#   bathrooms:
#     auto_fill: false
#     type: unfeaturized
#   bedrooms:
#     auto_fill: false
#     type: unfeaturized
#   city:
#     auto_fill: false
#     type: unfeaturized
#   cost:
#     auto_fill: false
#     type: unfeaturized
#   country:
#     auto_fill: false
#     type: unfeaturized
#   email:
#     auto_fill: false
#     type: unfeaturized
#   months:
#     auto_fill: false
#     type: unfeaturized
#   phone_number:
#     auto_fill: false
#     type: unfeaturized
#   property_type:
#     auto_fill: false
#     type: unfeaturized
#   time_to_sell:
#     auto_fill: false
#     type: unfeaturized
#   zipcode:
#     auto_fill: false
#     type: unfeaturized

session_config:
  session_expiration_time: 20
  carry_over_slots_to_new_session: true

Thanks for raising this issue, @samsucik will get back to you about it soon✨
Please also check out the docs and the forum in case your issue was raised there too 🤗

Hey @vivek22122014, the issue you're observing is just a warning, not a bug. It happens because Rasa Core has a limit on the maximum number of consecutive actions it predicts (by default, this limit is 10). In your case, utter_slots_values gets predicted many times in a row (probably due to some stories/rules you have) until this stopping mechanism is triggered, and the warning just tells you that this has happened. The stopping mechanism was introduced here. Can I close the issue, or do you have further questions?

I'm still confused about this issue

Yeah, I'm also confused about the cause of the duplicated predictions -- your rule looks OK. Could you try to create a setup (config, domain, rules, NLU data) as minimalistic as possible (i.e. with as much irrelevant stuff removed as possible), which still leads to this behaviour? Then I can look into why it's happening.

Sure Sam! I'll try that and come back to you.
Thanks sam for replying :)

Please reopen this issue if further discussion is needed

I also encountered this problem. I checked the graph carefully. The process is correct, but I don't know why this problem caused the termination of the conversation. Have you solved it？


Autofocus.ts causing problems

Using this modal with various HTML 5 inputs, autofocus attribute not set. When we call modal .open autofocus.ts calls focus for every element inside our modal. This causes Angular validators to fire and error as well as input focus events to execute when they shouldn't. Autofocus.ts subscribes to the .onOpen event, why is called with all modal child elements passed in?

Figured out this was our implantation issue. Had to set autofocus differently. Thanks.


OW Rich Presence

Adds support for OWRichPresence by MegaPiggy

@MegaPiggy put you as reviewer so you can do it once the new API stuff in OWRichPresence is ready and released.


Upgrade dependencies 181008

Codecov Report

Merging #14 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #14   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines           8      8
  Branches        1      1
=====================================
  Hits            8      8

Impacted Files
Coverage Δ

src/Checkbox.tsx
100% <0%> (ø)
:arrow_up:

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 9e4c796...5e2baf5. Read the comment docs.