Fix Difference calculations in Frequency.scala

There was a bug in difference calculation for Month and Day calculations where time differences of larger than 30 days would cause errors in the resulting time index. These have been updated to use the ChronoUnit class to measure difference (also consistent with BusinessDayFrequency).
This resolves https://github.com/cloudera/spark-timeseries/issues/113.

This looks like the right fix.  Any chance you'd be interested in adding a test for this?

Can do. Might be a few days.
Thank you,
Ilya Ganelin
-----Original Message-----
From: Sandy Ryza [notifications<EMAIL_ADDRESS>Sent: Monday, January 11, 2016 11:35 PM Eastern Standard Time
To: cloudera/spark-timeseries
Cc: Ganelin, Ilya
Subject: Re: [spark-timeseries] Fix Difference calculations in Frequency.scala (#114)
This looks like the right fix. Any chance you'd be interested in adding a test for this?
—
Reply to this email directly or view it on GitHubhttps://github.com/cloudera/spark-timeseries/pull/114#issuecomment-170786872.

The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.

@sryza I've added the relevant tests. As a minor note, any difference in excess of MAX_INT is subject to roll-over. I'd recommend converting all differences and periods to use Long unless there is an underlying reason not to.
This will be noticeable when dealing with nanosecond scale.

Merged this.  Thanks @ilganeli!


feat: add debugging

What problem does this feature solve?
When contributing to the core repo, writing a loader/plugin, or even working on a complex project, debugging tools can be central to your workflow.
What does the proposed API of configuration look like?
node --inspect node_modules/.bin/rspack build

Would this be helpful to you? https://web-infra-dev.github.io/rspack-dev-guide/debugging/intro.html

@hyf0 i try by following this docs, but got warning: npm/darwin-arm64                         |  WARN  Unsupported platform: wanted: {"cpu":["arm64"],"os":["darwin"],"libc":["any"]} (current: {"os":"darwin","cpu":"x64","libc":"unknown"})
.
i got error<EMAIL_ADDRESS>when running debug-rspack.
so, what libs that i need to install ?
thanks

@Phinome I'm getting the same issue. Could you move forward?

@Phinome I was having the same issue and it was missing protobuf.
brew install protobuf

I still have this problem after install protobuf 😢

protobuf is no longer required.
I followed the instructions at https://web-infra-dev.github.io/rspack-dev-guide/debugging/intro.html and managed to run the debugger.

May I get a double confirmation that this actually works?

I'll close this as fixed, feel free to reopen if this is not the case.


Add user-defined creativity level

Enable the user to set temperature

solved in release v0.2.0 https://github.com/souzatharsis/podcastfy/discussions/38
please update podcastfy to latest
language is tricky hence I welcome feedback, See Conversation Customization for more details.


apply_ufunc broadcasting issues

Code Sample
I am having some troubles understanding apply_ufunc broadcasting rules. As I had some trouble understanding the docs, I am not 100% sure it is a bug, but I am quite sure. I will try to explain why with the following really simple example.
import xarray as xr
import numpy as np

a = xr.DataArray(data=np.random.normal(size=(7, 3)), dims=["dim1", "dim2"])
c = xr.DataArray(data=np.random.normal(size=(5, 6)), dims=["dim3", "dim4"])

def func(x,y):
    print(x.shape)
    print(y.shape)
    return

The function defined always raises an error when trying to call apply_ufunc, but this is intended, as the shapes have already been printed by then, and this keeps the example as simple as possible.
Problem description
xr.apply_ufunc(func, a, c)
# Out
# (7, 3, 1, 1)
# (5, 6)

Here, a has been kind of broadcasted, but I would expect the shapes of a and c to be the same as when calling xr.broadcast, as there are no input core dims, so all dimensions are broadcasted. However:
print([ary.shape for ary in xr.broadcast(a,c)])
# [(7, 3, 5, 6), (7, 3, 5, 6)]

Using different input core dims does not get rid of the problem, instead I believe it shows some more issues:
xr.apply_ufunc(func, a, c, input_core_dims=[["dim1"],[]])
# (3, 1, 1, 7), expected (3, 5, 6, 7)
# (5, 6), expected (3, 5, 6)

xr.apply_ufunc(func, a, c, input_core_dims=[[],["dim3"]])
# (7, 3, 1), expected (7, 3, 6)
# (6, 5), expected (7, 3, 6, 5)

xr.apply_ufunc(func, a, c, input_core_dims=[["dim1"],["dim3"]])
# (3, 1, 7), expected (3, 6, 7)
# (6, 5), expected (3, 6, 5)

Is this current behaviour what should be expected?
 If multiple
    arguments with non-matching dimensions are supplied, this function is
    expected to vectorize (broadcast) over axes of positional arguments in
    the style of NumPy universal functions [1]_ (if this is not the case,
    set ``vectorize=True``). If this function returns multiple outputs, you
    must set ``output_core_dims`` as well.

Then shouldn't a in the first example keep its original shape?

Because func receives unlabelled arrays, apply_ufunc aligns the axes order. So if they share a dimension:
In [8]: import xarray as xr
   ...: import numpy as np
   ...:
   ...: a = xr.DataArray(data=np.random.normal(size=(7, 3)), dims=["dim1", "dim2"])
   ...: c = xr.DataArray(data=np.random.normal(size=(7, 6)), dims=["dim1", "dim4"])  # <- change here
   ...:
   ...: def func(x,y):
   ...:     print(x.shape)
   ...:     print(y.shape)
   ...:     return x
   ...:

In [9]: xr.apply_ufunc(func, a, c)
(7, 3, 1)
(7, 1, 6)

...otherwise func wouldn't know how to align.
Another option would be for your original example to put lengths of 1 in all axes, rather than only forward filling, e.g.
xr.apply_ufunc(func, a, c)
# Out
# (7, 3, 1, 1)
# (1, 1, 5, 6) # <- change here

I think it operates this way because functions 'in the wild' generally will handle that themselves, but that's a guess and needs someone who knows this better to weight in

For what it's worth, I agree that this behavior is a little surprising. We should probably make apply_ufunc() explicitly broadcast arrays first.

We should probably make apply_ufunc() explicitly broadcast arrays first.

To confirm, so that we have something like this?
xr.apply_ufunc(func, a, c)
# Out
# (7, 3, 5, 6)
# (7, 3, 5, 6)

Yes, exactly.

I'm trying to think whether there would be any performance cost there - i.e. are there any arrays where preemptive broadcasting would be both expensive and unnecessary?

I'm trying to think whether there would be any performance cost there - i.e. are there any arrays where preemptive broadcasting would be both expensive and unnecessary?

Even if there were a performance cost (compared to the actual behaviour), it could be easily avoided by using all dims as input_core_dims couldn't it? IIUC, all dims should be broadcasted unless they are in input core dims, so it broadcasting could still be avoided without problem.

With NumPy arrays at least, there is no cost for broadcasting, because it
can always be done with views.  But even for other array types, inserting
size 1 dimensions in the correct location should be basically free, and
would be more helpful than what we currently do
On Wed, Jun 19, 2019 at 9:25 PM Oriol Abril<EMAIL_ADDRESS>wrote:

I'm trying to think whether there would be any performance cost there -
i.e. are there any arrays where preemptive broadcasting would be both
expensive and unnecessary?
Even if there were a performance cost (compared to the actual behaviour),
it could be easily avoided by using all dims as input_core_dims couldn't
it? IIUC, all dims should be broadcasted unless they are in input core
dims, so it broadcasting could still be avoided without problem.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/pydata/xarray/issues/3032?email_source=notifications&email_token=AAJJFVUDJUKKVSXB5DQONF3P3J2YXA5CNFSM4HZEHCZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYCXX4Y#issuecomment-503675891,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJJFVTEQBAYTYROYMQNGC3P3J2YXANCNFSM4HZEHCZA
.

@shoyer thanks for the clarity
@OriolAbril would you mind if we changed this issue to "apply_ufunc should preemptively broadcast"

@max-sixty Not at all, whatever is best. I actually opened the issue without being 100% it was one.


TypeError: jsPsych.getDisplayElement(...).querySelector(...) is null

I am new to jsPsych. I have created a small experiment. I am able to run it locally without any errors. But, when I host it on the website, I am getting the following errors. Can someone please help?
Website URL: http://harishbalakrishnan.online/f/expa.html

It looks like the page at that URL has been removed. Is the problem solved?

It looks like the page at that URL has been removed. Is the problem solved?

Hi! The problem seems to be related to the huge size (~ 1.5GB) of animation frames that I am using as the stimuli for the jspsych-animation plugin. Now, I have reduced the number of animation frames and the size of each frame. I don't see the problem now.
So, yes we can close this thread. I forgot about this thread. Apologies and thanks!


Not really an issue...

Not sure if you're still at DB. My email is still<EMAIL_ADDRESS>I'm coming to Germany again this fall. Send me an email with your current email address.

Answered by PM.


Update swift 4.2

Can someone merge this? @kishikawakatsumi I would love to see this framework continue, are you not interested in maintaining?

@kyleturner you can use my branch
pod 'SpreadsheetView', :git => "https://github.com/markgravity/SpreadsheetView.git", :branch => "swift-4.2"

@kyleturner I don't have enough time to maintain this library now. You can still use this library which you build it with Swift 4.0 mode. Swift can mix different Swift versions. Or you can use ci branch https://github.com/kishikawakatsumi/SpreadsheetView/tree/ci


-g is throwing error on --upgrade

Describe the bug
Using -g for --upgrade is throwing error.
To Reproduce
C:\dev\liquibase\liquibase-4.17.2>lpm upgrade --global
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x28 pc=0x9696d9]
goroutine 1 [running]:
github.com/hashicorp/go-version.(*Version).String(0x0)
/Users/mcred/projects/go/pkg/mod/github.com/hashicorp/go-version@v1.6.0/version.go:369 +0x39
github.com/hashicorp/go-version.(*Version).Compare(0xc0000d0280, 0x0)
/Users/mcred/projects/go/pkg/mod/github.com/hashicorp/go-version@v1.6.0/version.go:116 +0x3b
github.com/hashicorp/go-version.(*Version).LessThan(...)
/Users/mcred/projects/go/pkg/mod/github.com/hashicorp/go-version@v1.6.0/version.go:308
package-manager/internal/app/packages.Package.GetLatestVersion({{0xc0000121e0, 0x11}, {0xc000588e90, 0x9}, {0xc000066d80, 0x2a, 0x2a}}, 0xc000066d80?)
/Users/mcred/projects/liquibase/package-manager/internal/app/packages/Package.go:23 +0x1ab
package-manager/internal/app/packages.Packages.GetOutdated({0xc000076000?, 0x170f453ffff?, 0x197?}, 0x2030000?, {0xc0000d8400, 0x7, 0x8})
/Users/mcred/projects/liquibase/package-manager/internal/app/packages/Packages.go:41 +0x205
package-manager/internal/app/commands.glob..func7(0xf5f6c0?, {0xc1ce63?, 0x1?, 0x1?})
/Users/mcred/projects/liquibase/package-manager/internal/app/commands/upgrade.go:24 +0x5f
github.com/spf13/cobra.(*Command).execute(0xf5f6c0, {0xc000089200, 0x1, 0x1})
/Users/mcred/projects/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:920 +0x847
github.com/spf13/cobra.(*Command).ExecuteC(0xf5ee20)
/Users/mcred/projects/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:1044 +0x3bd
github.com/spf13/cobra.(*Command).Execute(...)
/Users/mcred/projects/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:968
package-manager/internal/app/commands.Execute({0xc0000c8360?, 0xc0000c8330?}, {0xc1c8a4, 0x1})
/Users/mcred/projects/liquibase/package-manager/internal/app/commands/root.go:39 +0x125
main.main()
/Users/mcred/projects/liquibase/package-manager/cmd/lpm/windows.go:49 +0x2a9
C:\dev\liquibase\liquibase-4.17.2>lpm upgrade
You have no outdated packages installed.
C:\dev\liquibase\liquibase-4.17.2/liquibase_libs/
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Do you have any packages installed globally? What is the output from lpm ls -g?

Do you have an env for LIQUIBASE_HOME?

C:\dev\liquibase\liquibase-4.17.2>lpm ls -g C:\dev\liquibase\liquibase-4.17.2\lib\      Package                                Category ├──<EMAIL_ADDRESS>                      driver └──<EMAIL_ADDRESS>             extension
C:\dev\liquibase-kubernetes\spring>env | grep LIQUIBASE_HOME LIQUIBASE_HOME=C:\dev\liquibase\liquibase-4.17.2

lpm update solved the issue. Thanks!


fix(compiler-core): If v-if="true" in the slots, ignore it (fix #6833)

Description
fix #6833
 <Comp><template v-if="true" #header>Header</template></Comp>
 <Comp><template #header>Header</template></Comp>

compiler

new

export function render(_ctx, _cache, $props, $setup, $data, $options) {
  const _component_Comp = _resolveComponent("Comp")

  return (_openBlock(), _createElementBlock(_Fragment, null, [
    _createVNode(_component_Comp, null, {
      header: _withCtx(() => [
        _createTextVNode("Header")
      ]),
      _: 1 /* STABLE */
    }),
    _createVNode(_component_Comp, null, {
      header: _withCtx(() => [
        _createTextVNode("Header")
      ]),
      _: 1 /* STABLE */
    })
  ], 64 /* STABLE_FRAGMENT */))
}

old

export function render(_ctx, _cache, $props, $setup, $data, $options) {
  const _component_Comp = _resolveComponent("Comp")

  return (_openBlock(), _createElementBlock(_Fragment, null, [
    _createVNode(_component_Comp, null, _createSlots({ _: 2 /* DYNAMIC */ }, [
      true
        ? {
            name: "header",
            fn: _withCtx(() => [
              _createTextVNode("Header")
            ]),
            key: "0"
          }
        : undefined
    ]), 1024 /* DYNAMIC_SLOTS */),
    _createVNode(_component_Comp, null, {
      header: _withCtx(() => [
        _createTextVNode("Header")
      ]),
      _: 1 /* STABLE */
    })
  ], 64 /* STABLE_FRAGMENT */))
}

What is use case of v-if="true"?

v-if="true" doesn't make sense in any real apps. But green hand, maybe will write such code during development， ignore is just to reduce one question.

I don't think this really fixes the original issue.
The original reproduction needed a v-if to hit the relevant code path. Using v-if="true" was just the simplest way to achieve that. Adding special handling for v-if="true" doesn't fix the underlying problem, it just hides it in that specific example.
The main 'use case' for v-if="true" is in reproductions that need a v-if, like in that example. It would be counterproductive to introduce an inconsistency and handle that case differently to any other v-if.
The only other use case I can think of is for templates that aren't directly written by a human. e.g. A template coming from a PHP backend, where v-if="true" is in the generated code, not the original source. But I don't think that use case justifies the extra effort to handle it specially.
In my opinion, this PR should be closed.


[WIP] Try use yarn for CI (closes #864)

Still blocked on npm env variables
We need to do something with node10


Using tippecanoe's mbtiles in Geoserver

I've created a mbtile file from a geojson layer using tippecanoe command tool. The qustion is that is it possible to publish this mbtile in Geoserver with mbtile extension? I've used the extension to publish mbtile but the layer preview throws the error rendering coverage on the fast path. Is it something wrong with publish procedure or something else?

This issue may be better suited to the geoserver repo, since the error is not coming from tippecanoe: https://github.com/geoserver/geoserver

Thanks, @morganherlocker. I go through it.

Please reopen if something turns out to be wrong on the Tippecanoe side.


Augment HSV will allow configuring bgr_channels in case there are oth…

…er channels in the input tensor

Sorry for not elaborating. The intention is to allow using this
augmentation with inputs of more than 3 channels (e.g, RGB+IR) while
applying it to the relevant channels.
On Sun, 18 Sep 2022 at 22:47 Ofri Masad @.***> wrote:

@.**** commented on this pull request.
looks like setting the order of the colors is a bit too redundant.
there is RGB and BGR but I don't think anyone uses GRB or RBG...
why not just add a flag 'rgb:bool = False' and then use
cv2.cvtColor(img, cv2.COLOR_RGB2HSV)
—
Reply to this email directly, view it on GitHub
https://github.com/Deci-AI/super-gradients/pull/393#pullrequestreview-1111581346,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEZYKMWQRDDKNIF37D7J5ELV65WV3ANCNFSM6AAAAAAQPPU5YM
.
You are receiving this because you authored the thread.Message ID:
@.***>


Add new env vars

Adds the system id env var, and the fail callback env var

This change is

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from the review on Reviewable.io


missing credentials error using AWS

Missing Credentials.
2015-05-06T01:47:25.619025+00:00 app[web.1]:
2015-05-06T01:47:25.619028+00:00 app[web.1]: AWS::Errors::MissingCredentialsError (
2015-05-06T01:47:25.619041+00:00 app[web.1]:
In config/initializers/refile.rb
require "refile/backend/s3"
aws = {
access_key_id: Rails.application.secrets.access_key_id,
secret_access_key: Rails.application.secrets.secret_access_key,
bucket: Rails.application.secrets.bucket
}
Refile.cache = Refile::Backend::S3.new(prefix: "cache", **aws)
Refile.store = Refile::Backend::S3.new(prefix: "store", **aws)
In secrets.yaml
production:
secret_key_base: <%= ENV["SECRET_KEY_BASE"] %>
access_key_id: <%= ENV["AWS_KEY_ID"] %>
secret_access_key: <%= ENV["AWS_SECRET_KEY"] %>
bucket: <%= ENV["S3_BUCKET"] %>

I set my production environment variables in heroku. The only thing I can think is that the secrets file is in .gitignore

Yes, your credentials may be blank, you can heroku run console and check for Rails.application.secrets.* credentials if they're set. One other thing that may be causing the error is that you wrote *aws when passing the credentials instead of **aws.


[9.101.x-prod] kie-kogito-serverless-operator-533: Builder image is not used according to the configuration semantic (#534)

Description of the change:
Motivation for the change:
Checklist

[X] Add or Modify a unit test for your change
[X] Have you verified that tall the tests are passing?

How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-7.67.x to backport the original PR to the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

Counterpart for the already merged into main https://github.com/apache/incubator-kie-kogito-serverless-operator/pull/534


ASP.NET Core runtime binaries for non-admin ?

Question regarding the downloads of .NET SDKS:
I want to download the .NET Core 2.2. Preview 2.
But on my dev-machine I don't have admin rights.
So I downloaded the runtime-binaries and the sdk-binaries from
https://github.com/dotnet/core/blob/master/release-notes/2.2/preview/2.2.0-preview2.md
Unpacked to a directory in user-dir, and then I overwrote the path environment variable in cmd, and started visual studio from the command line.
Seems to work.
Now the download | ASP.NET Core Runtime | does not have binaries, it only has an installer, which requires admin rights.
Why is there no zip-file for the ASP.NET Core runtime ?
Or is |  ASP.NET Core runtime | the same as | Runtime Binaries | ?
Or is this not required at all, and will it just download that from nuget ?
Or is that some sort of IIS integration that I don't require with IIS express, as hosting-bundle would imply ?

@leecow @Eilon do you know where to route this problem?

Thanks @natemcmaster.
Closing as it seems to be answered.


scrolling with cursor makes page jump

When I scroll with the cursor in VS Code (f.e. holding j), the page jumps like this:
https://user-images.githubusercontent.com/297678/103330141-127eca80-4a15-11eb-8a46-fec21f5f8eaf.mp4
But I would like it to be like in neovim with no jumping:
https://user-images.githubusercontent.com/297678/103330258-81f4ba00-4a15-11eb-97c8-6de79cfa482d.mp4
Is there any way to prevent the jumping?

Your cursor is just too 🐎  🐎  🐎  🚗
Here the behaviour at normal speed:
https://user-images.githubusercontent.com/8881674/103330427-bf7f3480-4a61-11eb-9c31-b73fbff06fa7.mp4
Changing this:
https://github.com/asvetliakov/vscode-neovim/blob/d366766f397954078e5b9eeb01532913fb90b48f/src/cursor_manager.ts#L422
to TextEditorRevealType.Default can help but will possibly degrade UX of over jumps

I just compiled PR in #479 . Please try attached build to GHA check once them completed.

Your cursor is just too :racehorse: :racehorse:  :racehorse:  :car:

Oh, I see. :smile:

I just compiled PR in #479 .

I think it might be a good change. I also have mappings like this:
nmap <c-j> 5j
nmap <c-k> 5k

and those trigger it on a single move, which makes sense based on what you described, but also not like Neovim:
VS Code:

Neovim:

I just compiled PR in #479 . Please try attached build to GHA checks once they are completed.

Cool, it works exactly as expected!
Also I tried VS Code's Go to Definition command on some things, and I don't experience any issues, it seems to work fine like before. What other other jumps should I test (and how specifically)?

Also I tried VS Code's Go to Definition command on some things, and I don't experience any issues

Is the screen centered after go to def?

What other other jumps should I test (and how specifically)?

Various jumps from vscodee:

go to def to same file
to to def to another file
open definition aside to same file (<C-w>gd)
Open definition aside to another file
Peek definition to same file
Peek def to another file
outline navigation
search navigation
navigation from search results editor

From vim side:
200j or k
jump to mark
search/incsearch jump

hm, probably the PR can be improved by taking account into a jump line delta, if < 10 lines or so - use default revealing, otherwise use viewport centering

Is the screen centered after go to def?

Not quite, but totally not bothersome: it appears on screen, and VS Code highlights it for a brief moment so I know where on screen it is. This video show both go to def in current file, and other file:
https://user-images.githubusercontent.com/297678/103331790-5a552000-4a1c-11eb-9293-72dd15f67b73.mp4
As for the others:

open definition aside to same file (gd) - appears the same as go to def
Open definition aside to another file - appears the same as go to def in other file
Peek definition to same file - that was visible in the above video (looks fine)
Peek def to another file - that was visible in the above video (looks fine)
outline navigation - looks fine
search navigation - just fine
navigation from search results editor - just fine

I noticed if the jump is within the same view (no scroll needed) then the view doesn't adjust, but I think that's totally fine.

Outline jump:
https://user-images.githubusercontent.com/297678/103331998-3e9e4980-4a1d-11eb-8266-73fec755154a.mp4
Search jump is just fine.

<c-w>gd just stopped working, now it just does Go to Definition, no split. Will make a new issue.

I think the jumps are working very well, and even if they aren't centered, the un-centering along with the expected cursor movement is much more desirable (at least for me). I can do both just fine now: go to definition (no centering is ok) and move the cursor same as vim, whereas before jumping may have had perfect centering but the cursor movement was unbearable.

fixed in 0.0.73


Describe broadcasting rules

closes #981

For what it's worth, my presentation at practitioner's forum also talked about broadcasting if you want to take a look: https://learning.quantum.ibm.com/tutorial/updates-to-qiskit-runtime#numpy-array-broadcasting

I'm getting a "file not found" error.

+1 to Jessie's suggestions, I left an additional comment that I think would be useful to have, and I also see 2 missing pieces of information:

These rules only talk about circuits and observables, what about the parameters? Shouldn't we also include examples with different parameter array sizes?

What about the sampler rules? Even if the mechanics are the same, I think that the sampler should be at least mentioned. Once the parameter mechanics are explained in the estimator it's quite natural to just say "the sampler is the same but without observables"

@ElePT, these rules actually apply to observables and parameter arrays in a PUB. Each pub only has 1 circuit, and each element in the broadcasted observables + parameter arrays is then applied to that circuit (and hence the result has the same size/shape as the broadcasted arrays). Sampler is not mentioned because there are no special rules - i.e. each parameter value set is applied to the circuits. But we should definitely clarify if it's not obvious.

@ElePT, these rules actually apply to observables and parameter arrays in a PUB. Each pub only has 1 circuit, and each element in the broadcasted observables + parameter arrays is then applied to that circuit (and hence the result has the same size/shape as the broadcasted arrays). Sampler is not mentioned because there are no special rules - i.e. each parameter value set is applied to the circuits. But we should definitely clarify if it's not obvious.

I guess that the point I was trying to make is that I don't think it's obvious to everyone, even if it's not that difficult to extrapolate, I think one example for the sampler and one for the estimator with parameters (even if it is to show that the rules are the same) will go a long way.

each parameter value set is applied to the circuits.

@ElePT, these rules actually apply to observables and parameter arrays in a PUB. Each pub only has 1 circuit, and each element in the broadcasted observables + parameter arrays is then applied to that circuit (and hence the result has the same size/shape as the broadcasted arrays). Sampler is not mentioned because there are no special rules - i.e. each parameter value set is applied to the circuits. But we should definitely clarify if it's not obvious.

I guess that the point I was trying to make is that I don't think it's obvious to everyone, even if it's not that difficult to extrapolate, I think one example for the sampler and one for the estimator with parameters (even if it is to show that the rules are the same) will go a long way.

But I think that the broadcasting rules apply only to how we combine multiple arrays.  Since you can't have multiple arrays with Sampler, they don't apply.


EDU-1301 Fix storage reminders error and improve actions column content

Closes https://educandu.atlassian.net/browse/EDU-1301
I also changed the actions column content for that tab.
Old:

New:

Closes https://educandu.atlassian.net/browse/EDU-1301
I also changed the actions column content for that tab. Old:
New:

Nice (and space-saving) :grin:


Update Disable-InboxRule.md

https://github.com/MicrosoftDocs/office-docs-powershell/issues/4148

Docs Build status updates of commit c17a980:
:clock10: Full build: the average full build time is 11 min(s) 46 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit c17a980:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/mailboxes/Disable-InboxRule.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 5b35f46:
:clock10: Pending: waiting for processors (6 builds ahead of you)
:warning: Docs Build is busy, currently there are 6 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 5b35f46:
:clock10: Full build: the average full build time is 11 min(s) 46 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 5b35f46:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/mailboxes/Disable-InboxRule.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Airlock processor networking (vnet integration and airlock subnet)

Fixes #2038
What is being addressed
Adding:

Airlock subnet in the core vnet
Airlock processor is now vnet integrated
Airlock storage subnet
All PEs of the Airlock storage accounts are in the subnet created at (3)

Note to reviewer: Had to create a new subnet as the one in (1) has service delegation, hence PE are not possible

/test

/test-extended

/test-destroy-env

/test-extended

/test-extended

/test-destroy-env

/test-extended

/test-extended

/test-destroy-env

/test

/test-extended

/test-extended

/test-destroy-env

/test-extended

/test-destroy-env

/test

/test

/test-destroy-env

/test

/test

/test

/test

/test

/test

/test-destroy-env

/test-extended

/test-extended


How to Improve Security of Django Applications with Penetration Testing

Topic Suggestion
Writing sample(s):
https://www.section.io/engineering-education/authors/muhammed-ali/
Proposal Submission
Proposed title of article
How to Improve Security of Django Applications with Penetration Testing
Proposed article introduction
This article will go through how the reader can improve the security of their Django application by applying penetration testing. I will go through some basics about penetration testing and then build a simple Django, apply penetration testing, and find ways in which we can solve the security faults discovered during the penetration testing process.
ONLY viable topics to pick from:

Languages

Key takeaways

introduction to penetration testing
Ways to perform penetration testing in Django
How to improve security in Django

Article quality
The article is unique

Good afternoon and thank you for submitting your topic to the EngEd program.
After some careful consideration it struck us that this topic may be a bit over saturated throughout other blog sites and official documentations. We're more interested in original, practitioner-focused content that takes a deeper dive into programming-centric concepts. Please feel free to suggest an alternate topic to explore. 🚀


We can't redefine Order for ObservedAspect

When I used the @Observed annotation with another one like @MyCustomAspect, I observed that the ObservedAspect is always lastely excuted :
See AspectJAwareAdvisorAutoProxyCreator#sortAdvisors()
Could we have an abastract class for Extends ObservedAspect and put my own orders.
with Spring annotation @Order

wrong project


SPM - can't resolve v1.6.2

Describe the bug
I tried upgrading from 1.5.4 -> 1.6.2, but doing so caused an SPM conflict. 1.6.2 depends on QRCode, but it points to a branch, not a version. This is classified as an "un-stable" version, and SPM doesn't allow you to use "stable" versions of packages that depend on un-stable versions
SDK Version

Client: Swift
Version 1.6.2

To Reproduce
Steps to reproduce the behavior:

Add 1.6.2 via SPM

Screenshots

Device (please complete the following information):

Xcode 14.2

@llbartekll hi, no its still pointing to a branch

So importing 1.6.3 produces the same error with a new verison number. To be clear, the only solution to this issue is to point to a specific version like the below:

hey @simonmcl could you check with 1.6.4, please?

@llbartekll yep, working now. Thanks


Update Readme with Ethermint Deployment

Addition of Ethermint Deployment

Thank you very much. This looks very promising.
Could you remove everything that has currently a todo. For example the Docker section. Also, let's group the installation for Ethermint and Tendermint and make sure that they follow the same format.
Besides that it looks awesome.

Is there a possibility to run ethermint in a docker container similar to how we currently do it with testrpc?

I think, before making the docker container, people should test it in order to know if there are some problems with the setup with Ethermint. And when we are sure that it is totally working we can do the docker container.

I agree with @jeamick

the dockerizing would be to make the setup easier for users such as they do not need to have a local go/ethermint/tendermint/geth install.
on a sidenote: could we opt for having the current default (docker / vanilla ethereum) and ethermint side by side? As it is now the ethermint docs overwrite the old docs.

@axelhodler I agree. I believe @jeamick and I also discussed this offline. In theory the main Readme should offer both as branches... perhaps in separate Markdown files.

That being said, I'm a big fan of the tutorial for building ethermint locally as it's not only useful for docker experts to be able to dockerize but also makes for a good fallback option.

Especially if you want to roll something out to several people it makes sense to do so via docker. A non docker solution is prone to 'works on my machine' problems and it will not integrate with the current setup as this is purely docker based.

Yes @anoff  you're right! I will try to make a video demo for this repo.
If someone can do the docker file because I'm not an expert on it.
So to make things clear, let's make to differents repo right?

how can I call it ?

given the other PR, i'll go ahead and close this one :) Great job!

@iamtrask Could you reference the other PR here.


[ttx_diff] Remove manifest path arguments

I'm not really sure what these were doing there? My best guess is that I'd had a little brain fart and forgot that I could just pass -p to specify the package that cargo should build, since package selection is the only thing we're using this for.

Oops: for the record we need to use an explicit manifest path because we are running in a tempdir in crater.


Update MD file on new branch 2017-12-03_13-39-09

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Node name reverts back from device name to Alexa home on change of topic.

The title says it all.
If you have deployed a node and then try to edit the topic name the node name displayed on the node on the canvas reverts back from the device name to the generic "alexa home".
workaround is to reselect alternative device and then select initial device again.

Bah, this all worked before I had to change it for you freaks on Macs...
I'll have a look.

Try changing the oneditsave on on the alexa-home node to:
        oneditsave: function() {
             var n = $('#node-input-device option:selected').text();
            //console.log("selected name " + n);
            this.name = n;
            $('#node-input-name').val(n);
        },

yep editing the topic now maintains the node-name.   Ta very muchly!


Too unstable... bugs

I literally just followed all the steps in this tutorial, choosing a JS echo bot. I then used the web chat testing feature and experienced failed messages:

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

ID: baa9e2e6-b901-9e27-d070-701922396a4c
Version Independent ID: c29a68b2-886d-2cec-0ce7-c49c586d7ea8
Content: Create a bot with Bot Service - Bot Service
Content Source: articles/bot-service-quickstart.md
Service: bot-service
Product: bot-framework
GitHub Login: @v-ducvo
Microsoft Alias: v-ducvo

Thanks for your feedback Yousef. There are reported issues with the Web Chat tool in Azure. In the meantime here are a few things you can try to improve performance issues:

after selecting your Web App Bot, click on channels and the Web Chat edit button.

When the Edit page opens, scroll down to the bottom, uncheck the Enable Preview option, and select Done. (This improves the tool's performance)
If you are experiencing issues due to msg delivery delay, you can also try the following: Select the App Service plan and  Scale it up from Free (F1) to Small (S1), Run your test, then scale it back down to Free when you are finished.

Hope these short term workarounds help with your Web Chat performance issue.

Closing this feedback PR.


[feature request] add an option for custom notification message.

I mean, YubiKey is waiting for a touch is fine, but it would be nice if it could be customizable. Me, for example, this weird 'minimalist', thinks the current message is too long and takes a lot of screen's real estate ;-)

To be entirely honest I never liked having libnotify integration built-in in the first place (and treated "specially" comparing to all other GUI integrations), precisely because with all the titles, messages and icons you can end up maintaining more configuration options for libnotify than for the rest of the app... 😅
Especially because it's super easy to hook into the app (using socket (many examples here), or the more recent stdout) and provide completely custom kind of GUI indication.
It was a very popular request to have libnotify built-in, something that just works out of the box, everywhere, and requires no configs, that made me add it... But you can probably sense I'm a bit hesitant to make it more flashy than it already is. 😁

As a minimalist to a minimalist, wouldn't you want to add a Yubikey indicator to your bar in qtile, like is shown on the demo gif in the README? Wiki has a lot of examples of how this can be done, and I can also help you out if you get stuck (if you promise to document it on wiki to help other fellow users of qtile 😜 ).

I already have it in my bar. I just wanted to modify the message without modifying the code/building it from sources locally. That's what github binary releases are for, especially for go ;-)
An hour ago I was using --stdout in a helper script (and my qtile had the item in statusbar which invoked the other helper, to show the actual message) - it's all removed in this commit. Now, when qtile can handle notifications properly, I want to get rid of silly helpers - which I did in this commit.
I fully understand you don't want to add blows&whistles when you don't feel they are needed. Sure, I will live with 'long' message or clone, edit and build it locally in the future, maybe ;-)
If you're 100% sure you don't want to add it, please close the issue. No hard feeling, I promise.

Wow, a bar getting content from libnotify is definitely a new idea to me, interesting! What if you add fmt: "touch the yubikey" to the config of your Notify widget?

fmt works, but it obviously breaks all other notifications ;-)
parse_text looks like something worth checking. I will do it (tomorrow, it's 1:39 am in my timezone) and let you know.

<closing as 'no longer relevant'>

Happy we could solve your use-case! Maybe you could add a snippet of your config to the wiki, since it's an interesting and perhaps unique feature of qtile to be able to modify notification text? And in any case, enjoy the app 😉

Ah, perfect, thanks 👍


iPad is identified as macOS

I have an iPad (not Pro) on iPadOS 13, which is defined as macOS (desktop).
I'm using version 0.9.1 of your library.
Can you suggest a solution to this problem, please?

This is no longer an issue in current releases.

This is no longer an issue in current releases.


[FEAT]: Allow previewing files in notes or opening them directly

Is your feature request related to a problem? Please describe.
Hello community, my request
It seems that the community has made similar requests to this one, to compile them here I think they are these:

#658
#661
#710
#738
#767
#786
#810
#901
#1002

The same issue but with PDF files

#728
#790 (this one in particular asks to open in the default app)

Describe the solution you'd like
In summary, what is requested can be two things. When a card is being reviewed and there is a link to a note or PDF inside, it is possible to:

By clicking on the links, said file can be opened, either in

A new tab
It can also be in the side panel
A pop-up window

As well as this, there may be more ideas, my suggestion for this case is that before creating the card, a line is created with a "Link to a block in a note" so that clicking there redirects to that block of the note.

By hovering over the link and holding the Ctrl/cmd key, a preview can be made, of This note can be used for this:

The one that comes in Obsidian by default
My suggestion is to use hover editor, since that plugin allows you to edit right there.
It would look something like this:

Additional context
I believe that this way the above issues could be resolved. If you have any suggestions, please feel free to ask.
Regards.

Love this, would seriously make my workflow so much smoother! btw, you can edit preview popups in place now with Obsidian 1.7 without needing to use the hover editor.


snap: add option border_overlap and other improvements

Describe your PR, what does it fix/add?
I really liked the way borders used to overlap when snapping and how only the window's main surface would snap to the monitor, so I would like to bring that behavior back, but in the form of a config option.
Other improvements include:

reduced the number of snap functions from 4 down to 2, and only one ever gets declared at any given time.

border size should not be added to gap size. It seemed like the right way to do it at the time, but it makes snapping feel way stronger than it actually should.

all const variables have been given the all-caps naming convention.

to avoid excessive casting, border size is declared as a double.

to avoid excessive x + w, y + h calculations. I'm using a struct called Range and working only with start and end values until the very end of the function.

check for both monitor snapping as well as reserved monitor space
snapping in a relatively efficient way.

Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
Not that I can think of.
Is it ready for merging, or does it need work?
It's ready to merge.

Here is a video demonstrating what these changes look like:
https://github.com/user-attachments/assets/e248a568-1dbc-48e2-9545-58f3e3f9230b


Adding cloudfoundry commands

@animenon  - Thanks for the review, I added the commands and descriptions.

@satpot123 :+1:
You may add docs related to how cloud-foundry works.


Website backend docker file update

Description
[Provide a brief description of the changes made in this PR]
Related Issues

[ ] GitHub issues:

[ ] Closes #123
[ ] Closes #456
[ ] Any other relevant GitHub Issues...

[ ] JIRA cards:

[ ] JIRA-7890
[ ] JIRA-101112
[ ] Any other relevant JIRA cards...

Changes Made

[ ] Brief description of change 1
[ ] Brief description of change 2
[ ] Brief description of change 3

Testing

[ ] Tested locally
[ ] Tested against staging environment
[ ] Relevant tests passed: [List test names]

Affected Services

[ ] Which services were modified:

[ ] Service 1
[ ] Service 2
[ ] Other...

Endpoints Ready for Testing

[ ] New endpoints ready for testing:

[ ] Endpoint 1
[ ] Endpoint 2
[ ] Other...

API Documentation Updated?

[ ] Yes, API documentation was updated
[ ] No, API documentation does not need updating

Additional Notes
[Add any additional notes or comments here]

Summary by CodeRabbit

New Features

Enhanced container setup for the Django application, ensuring database migrations and static files are handled during the build process.
Updated method for starting the application using Gunicorn.

Documentation

Minor update to the README.md for clarity.

Chores

Removed the entrypoint script as its functionalities are now integrated into the Dockerfile.

Hi @OchiengPaul442 , thanks for the WIP PR.
Even though it is a work in progress, please take off sometime to edit the template PR description to match the intention of the PR. You can continue editing accordingly in case of any scope change. Thanks!


How do we handle failed validation?

We should come up with a uniform way of gracefully failing when a component's or trait's validation fails. Right now, the status checks still run for those.
Might we be able to use admission controllers to run the validation of an AppConfig or a Component? That could provide a more robust path to error handling.

On #348, @wonderflow suggested an admission controller, too. I think that is probably the direction we should go.

+1 on admission controller for validation.

Updated title and labels to reflect current plan

I'm working on it


Set the jre8 version as default

this is in relation to issue #59

@gstojsic thank you very much for the great idea to have a default build. our team likes your idea a lot. just one suggestion, instead of moving profile build42 to the  section, can we just add  to the profile build42 to make it default? thanks.

Of course you could make the build42 the active profile. In fact that was my first solution but then I decided for the submitted one because it requires less code (the xml stuff is already very noisy). This reduced the pom by 9 lines and the other solution would increase the noise and add several lines. Secondly, it is clearer for beginners to understand (you need not care about maven profiles if you are not interested in jre7 stuff to make sense of the pom). Also I believe that the solution I submitted is closer to the way maven builds were intended to work - try to use defaults as much as possible and specify overrides only when needed. Anyway, feel free to amend the pom as you see fit. Having the build42 set as the active profile would also be a step forward IMHO.

@gstojsic thank you for your valuable thought. after talking to the team, we decided to keep 2 profiles because we think using profiles is better for maintenance when new JDK comes out.
However, it is a great idea to make jre8 the default profile. Do you mind to help us adding '' to 'build42' profile and keep anything else the same as it is? thank you.

There you go. Thanks for considering the idea.

@gstojsic thank you for your contribution. We really appreciate all your ideas and fixes.


Redirect validation

Why you tried to validate redirect property as a URL while Redirect::to will get a page also?
// it could be a page name/path
Redirect::to('mypagename');

// CHECK FOR REDIRECT
if (filter_var($redirect, FILTER_VALIDATE_URL)) {
    return Redirect::to($redirect);
}

sorry for my English! :)

Excellen point @EleRam
I will say the idea was to prevent an invalid URL, but i think it's a great suggestion.


Android: Double posted replies

https://getsatisfaction.com/newsblur/topics/android-comment-reply-double-post

Having a hard time reproing this very often, but I think I have a fix in place.  Will want to have some various people test this out before we push.

Fixed in #836.


Instructions are not accurate

Both cases: Powershell and Azure Cli. At the time we are creating the assignments , parameters are not passed so lines failed. Please complete the instructions with fictional but instructive scope as well as the switch parameters (with an example). It took me some time to finally complete the lines with the corresponding help of the cmdlet (PowerShell) and command (azure cli).

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

ID: 2d3dbc7c-8d83-5087-2753-eb27beea64c4
Version Independent ID: e482906f-9ed8-6a2d-3359-4fb3cb17dbb1
Content: Sample - Allowed locations - Azure Policy
Content Source: articles/governance/policy/samples/allowed-locations.md
Service: azure-policy
GitHub Login: @DCtheGeek
Microsoft Alias: dacoulte

@wasytb Thanks for the feedback! What does your listOfAllowedLocations value look like for PowerShell? I do see that the Azure CLI step doesn't use the --params parameter.  The -PolicyParameter (PowerShell) and --params (Azure CLI) parameters take a JSON object. You can see how to structure the JSON in Example 3 on the New-AzureRmPolicyAssignment reference doc. This Sample page is intended to showcase the policy definition and the steps are the simple creation and assignment of that definition. For exhaustive instructions on using either Azure PowerShell or Azure CLI with Policy, I'd review Programmatically create policies and then use the Reference in the Policy Table of Contents to review cmdlet (PowerShell) and commands (Azure CLI) with all parameters, switches, and numerous examples of use.
As a note, this Sample is of a built-in policy definition that has been updated to exclude Microsoft.AzureActiveDirectory/b2cDirectories and resources that use the global region.  I'm hoping to have the update published, as it comes with more complete steps for both Azure PowerShell and Azure CLI, as well as adds REST API steps and details about each cmdlet/command/endpoint used.
@MicrosoftDocs/azure-cxp-triage Please assign to me, label 'doc-bug', and #in-progress.


Adding basic badges

Badges for the project
Pre-merge checklist:

[n/a] Code changes have tests
[n/a] Any changes to the config are documented in docs/parameter_reference.md
[n/a] Any new required config is documented in README.md
[n/a] Any large changes have been verified by running a Drone job

Force merging since it's readme only and start first build from clould.drone.io


changes to mutation panel

partial fix for issue #66
fixes issue #65

added an index column to mutations df so we can display mutation ID on hover (not sure if this is the right way to do this)
added test case for above
coloured mutations by number of inheritors
changed tooltip information on hover to display mutation ID, number of parents, inheritors and descendants.

https://github.com/tskit-dev/tsinfer-qc/assets/25925005/f72fa2e3-10ee-429b-9c54-444a6f1b48c0

Needs a rebase @savitakartik

Needs a rebase @savitakartik

Done (I think!)

@mergifyio rebase


On device wakeword broken last two updats. Have to say "Hey Jarvis then OK Nabu" to get device to respond

This has been an issue the past two ESPHome updates. Wake word is set to "hey_Jarvis" and when you say the wake word, the ESPHome logs show it trying to work, but the device only responds if you say the initial wake word, followed by "Ok Nabu". It seems the device also locks up after a few interactions.
Here is a Youtube upload of the issue live: https://youtu.be/iLQAnyJkeNg?si=QMIaMI12fZLtSYJT
###Config###########
`substitutions:
name: esp32-s3-box-3-bedroom
friendly_name: ESP32 S3 Box 3 Bedroom
micro_wake_word_model: hey_jarvis
packages:
esphome.voice-assistant: github://esphome/firmware/wake-word-voice-assistant/esp32-s3-box-3.yaml@main
esphome:
name: ${name}
name_add_mac_suffix: false
friendly_name: ${friendly_name}
api:
encryption:
key: nope
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
`
#######Logs
INFO ESPHome 2024.6.6 INFO Reading configuration /config/esphome/esp32-s3-box-3-bedroom.yaml... INFO Updating https://github.com/esphome/esphome.git@pull/5230/head INFO Updating https://github.com/jesserockz/esphome-components.git@None WARNING GPIO0 is a strapping PIN and should only be used for I/O with care. Attaching external pullup/down resistors to strapping pins can cause unexpected failures. See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins INFO Starting log output from /dev/ttyACM0 with baud rate 115200 [12:13:48]pio: GPIO[1]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| [D][micro_wake_word:363]: Wake word sliding average probability is 0.573 and most recent probability is 1.000 [12:13:48][D][micro_wake_word:129]: Wake Word Detected [12:13:48][D][micro_wake_word:178]: State changed from DETECTING_WAKE_WORD to STOP_MICROPHONE [12:13:48][D][micro_wake_word:135]: Stopping Microphone [12:13:48][D][esp_adf.microphone:234]: Stopping microphone [12:13:48][D][micro_wake_word:178]: State changed from STOP_MICROPHONE to STOPPING_MICROPHONE [12:13:48][D][esp-idf:000][filter]: W (356480) AUDIO_ELEMENT: IN-[filter] AEL_IO_ABORT [12:13:48] [12:13:48][D][esp-idf:000][read_task]: E (356482) AUDIO_ELEMENT: [filter] Element already stopped [12:13:48] [12:13:48][D][esp-idf:000][read_task]: W (356514) AUDIO_PIPELINE: There are no listener registered [12:13:48] [12:13:48][D][esp-idf:000][read_task]: I (356516) AUDIO_PIPELINE: audio_pipeline_unlinked [12:13:48] [12:13:48][D][esp-idf:000][read_task]: W (356516) AUDIO_ELEMENT: [i2s] Element has not create when AUDIO_ELEMENT_TERMINATE [12:13:48] [12:13:48][D][esp-idf:000][read_task]: I (356520) I2S: DMA queue destroyed [12:13:48] [12:13:48][D][esp-idf:000][read_task]: W (356520) AUDIO_ELEMENT: [filter] Element has not create when AUDIO_ELEMENT_TERMINATE [12:13:48] [12:13:48][D][esp-idf:000][read_task]: W (356522) AUDIO_ELEMENT: [raw] Element has not create when AUDIO_ELEMENT_TERMINATE [12:13:48] [12:13:48][D][esp_adf.microphone:285]: Microphone stopped [12:13:48][D][micro_wake_word:178]: State changed from STOPPING_MICROPHONE to IDLE [12:13:48][D][voice_assistant:504]: State changed from IDLE to START_MICROPHONE [12:13:48][D][voice_assistant:510]: Desired state set to WAIT_FOR_VAD [12:13:48][D][voice_assistant:221]: Starting Microphone [12:13:48][D][ring_buffer:024]: Created ring buffer with size 16384 [12:13:48][D][voice_assistant:504]: State changed from START_MICROPHONE to STARTING_MICROPHONE [12:13:48][D][esp-idf:000][read_task]: I (356539) I2S: DMA Malloc info, datalen=blocksize=512, dma_buf_count=8 [12:13:48] [12:13:48][D][esp-idf:000][read_task]: I (356543) I2S: I2S0, MCLK output by GPIO2 [12:13:48] [12:13:48][D][esp-idf:000][read_task]: I (356547) AUDIO_PIPELINE: link el->rb, el:0x3d0593a8, tag:i2s, rb:0x3d0597bc [12:13:48] [12:13:48][D][esp-idf:000][read_task]: I (356551) AUDIO_PIPELINE: link el->rb, el:0x3d05951c, tag:filter, rb:0x3d05b7fc [12:13:48] [12:13:48][D][esp-idf:000][read_task]: I (356554) AUDIO_ELEMENT: [i2s-0x3d0593a8] Element task created [12:13:48] [12:13:48][D][esp-idf:000][read_task]033[0;32mI (356557) AUDIO_THREAD: The filter task allocate stack on external memory [12:13:48] [12:13:48][D][esp-idf:000][read_task]: I (356560) AUDIO_ELEMENT: [filter-0x3d05951c] Element task created [12:13:48] [12:13:48][D][esp-idf:000][read_task]: I (356562) AUDIO_ELEMENT: [raw-0x3d05964c] Element task created [12:13:48] [12:13:48][D][esp-idf:000][read_task]: I (356564) AUDIO_PIPELINE: Func:audio_pipeline_run, Line:359, MEM Total:16485039 Bytes, Inter:90844 Bytes, Dram:90844 Bytes [12:13:48] [12:13:48] [12:13:48][D][esp-idf:000][i2s]: I (356568) AUDIO_ELEMENT: [i2s] AEL_MSG_CMD_RESUME,state:1 [12:13:48] [12:13:48][D][esp-idf:000][filter]: I (356570) AUDIO_ELEMENT: [filter] AEL_MSG_CMD_RESUME,state:1 [12:13:48] [12:13:48][D][esp-idf:000][filter]: I (356573) RSP_FILTER: sample rate of source data : 16000, channel of source data : 2, sample rate of destination data : 16000, channel of destination data : 1 [12:13:48] [12:13:48][D][esp-idf:000][read_task]: I (356577) AUDIO_PIPELINE: Pipeline started [12:13:48] [12:13:48][D][esp_adf.microphone:273]: Microphone started [12:13:48][D][voice_assistant:504]: State changed from STARTING_MICROPHONE to WAIT_FOR_VAD [12:13:48][D][voice_assistant:245]: Waiting for speech... [12:13:48][D][voice_assistant:504]: State changed from WAIT_FOR_VAD to WAITING_FOR_VAD [12:13:57][D][voice_assistant:258]: VAD detected speech [12:13:57][D][voice_assistant:504]: State changed from WAITING_FOR_VAD to START_PIPELINE [12:13:57][D][voice_assistant:510]: Desired state set to STREAMING_MICROPHONE [12:13:57][D][voice_assistant:275]: Requesting start... [12:13:57][D][voice_assistant:504]: State changed from START_PIPELINE to STARTING_PIPELINE [12:13:57][D][voice_assistant:525]: Client started, streaming microphone [12:13:57][D][voice_assistant:504]: State changed from STARTING_PIPELINE to STREAMING_MICROPHONE [12:13:57][D][voice_assistant:510]: Desired state set to STREAMING_MICROPHONE [12:13:57][D][voice_assistant:627]: Event Type: 1 [12:13:57][D][voice_assistant:630]: Assist Pipeline running [12:13:57][D][voice_assistant:627]: Event Type: 9 [12:14:03][D][voice_assistant:627]: Event Type: 0 [12:14:03][D][voice_assistant:627]: Event Type: 2 [12:14:03][D][voice_assistant:717]: Assist Pipeline ended [12:14:03][D][voice_assistant:504]: State changed from STREAMING_MICROPHONE to WAIT_FOR_VAD [12:14:03][D][voice_assistant:510]: Desired state set to WAITING_FOR_VAD [12:14:03][D][voice_assistant:245]: Waiting for speech... [12:14:03][D][voice_assistant:504]: State changed from WAIT_FOR_VAD to WAITING_FOR_VAD [12:14:06][D][voice_assistant:258]: VAD detected speech [12:14:06][D][voice_assistant:504]: State changed from WAITING_FOR_VAD to START_PIPELINE [12:14:06][D][voice_assistant:510]: Desired state set to STREAMING_MICROPHONE [12:14:06][D][voice_assistant:275]: Requesting start... [12:14:06][D][voice_assistant:504]: State changed from START_PIPELINE to STARTING_PIPELINE [12:14:07][D][voice_assistant:525]: Client started, streaming microphone [12:14:07][D][voice_assistant:504]: State changed from STARTING_PIPELINE to STREAMING_MICROPHONE [12:14:07][D][voice_assistant:510]: Desired state set to STREAMING_MICROPHONE [12:14:07][D][voice_assistant:627]: Event Type: 1 [12:14:07][D][voice_assistant:630]: Assist Pipeline running [12:14:07][D][voice_assistant:627]: Event Type: 9 [12:14:14][D][voice_assistant:627]: Event Type: 0 [12:14:14][D][voice_assistant:627]: Event Type: 2 [12:14:14][D][voice_assistant:717]: Assist Pipeline ended [12:14:14][D][voice_assistant:504]: State changed from STREAMING_MICROPHONE to WAIT_FOR_VAD [12:14:14][D][voice_assistant:510]: Desired state set to WAITING_FOR_VAD [12:14:14][D][voice_assistant:245]: Waiting for speech... [12:14:14][D][voice_assistant:504]: State changed from WAIT_FOR_VAD to WAITING_FOR_VAD [12:14:30][D][voice_assistant:258]: VAD detected speech [12:14:30][D][voice_assistant:504]: State changed from WAITING_FOR_VAD to START_PIPELINE [12:14:30][D][voice_assistant:510]: Desired state set to STREAMING_MICROPHONE [12:14:30][D][voice_assistant:275]: Requesting start... [12:14:30][D][voice_assistant:504]: State changed from START_PIPELINE to STARTING_PIPELINE [12:14:30][D][voice_assistant:525]: Client started, streaming microphone [12:14:30][D][voice_assistant:504]: State changed from STARTING_PIPELINE to STREAMING_MICROPHONE [12:14:30][D][voice_assistant:510]: Desired state set to STREAMING_MICROPHONE [12:14:30][D][voice_assistant:627]: Event Type: 1 [12:14:30][D][voice_assistant:630]: Assist Pipeline running [12:14:30][D][voice_assistant:627]: Event Type: 9 [12:14:38][D][voice_assistant:627]: Event Type: 10 [12:14:38][D][voice_assistant:636]: Wake word detected [12:14:38][D][voice_assistant:627]: Event Type: 3 [12:14:38][D][voice_assistant:641]: STT started [12:14:38][D][text_sensor:064]: 'text_request': Sending state '...' [12:14:38][D][text_sensor:064]: 'text_response': Sending state '...' [12:14:38][W][component:237]: Component voice_assistant took a long time for an operation (224 ms). [12:14:38][W][component:238]: Components should block for at most 30 ms. [12:14:40][D][voice_assistant:627]: Event Type: 11 [12:14:40][D][voice_assistant:781]: Starting STT by VAD [12:14:41][D][voice_assistant:627]: Event Type: 12 [12:14:41][D][voice_assistant:785]: STT by VAD end [12:14:41][D][voice_assistant:504]: State changed from STREAMING_MICROPHONE to STOP_MICROPHONE [12:14:41][D][voice_assistant:510]: Desired state set to AWAITING_RESPONSE [12:14:41][D][esp_adf.microphone:234]: Stopping microphone [12:14:41][D][voice_assistant:504]: State changed from STOP_MICROPHONE to STOPPING_MICROPHONE [12:14:41][D][esp-idf:000][filter]: W (409658) AUDIO_ELEMENT: IN-[filter] AEL_IO_ABORT [12:14:41] [12:14:41][D][esp-idf:000][read_task]: E (409660) AUDIO_ELEMENT: [filter] Element already stopped [12:14:41] [12:14:41][D][esp-idf:000][read_task]: W (409691) AUDIO_PIPELINE: There are no listener registered [12:14:41] [12:14:41][D][esp-idf:000][read_task]: I (409693) AUDIO_PIPELINE: audio_pipeline_unlinked [12:14:41] [12:14:41][D][esp-idf:000][read_task]: W (409695) AUDIO_ELEMENT: [i2s] Element has not create when AUDIO_ELEMENT_TERMINATE [12:14:41] [12:14:41][D][esp-idf:000][read_task]: I (409697) I2S: DMA queue destroyed [12:14:41] [12:14:41][D][esp-idf:000][read_task]: W (409699) AUDIO_ELEMENT: [filter] Element has not create when AUDIO_ELEMENT_TERMINATE [12:14:41] [12:14:41][D][esp-idf:000][read_task]: W (409701) AUDIO_ELEMENT: [raw] Element has not create when AUDIO_ELEMENT_TERMINATE [12:14:41] [12:14:41][W][component:237]: Component voice_assistant took a long time for an operation (241 ms). [12:14:41][W][component:238]: Components should block for at most 30 ms. [12:14:41][D][voice_assistant:627]: Event Type: 4 [12:14:41][D][voice_assistant:655]: Speech recognised as: "Never mind." [12:14:41][D][text_sensor:064]: 'text_request': Sending state 'Never mind.' [12:14:41][W][component:237]: Component voice_assistant took a long time for an operation (238 ms). [12:14:41][W][component:238]: Components should block for at most 30 ms. [12:14:41][D][voice_assistant:627]: Event Type: 5 [12:14:41][D][voice_assistant:660]: Intent started [12:14:41][D][esp_adf.microphone:285]: Microphone stopped [12:14:41][D][voice_assistant:504]: State changed from STOPPING_MICROPHONE to AWAITING_RESPONSE [12:14:44][D][voice_assistant:627]: Event Type: 6 [12:14:44][D][voice_assistant:627]: Event Type: 7 [12:14:44][D][voice_assistant:683]: Response: "Very well, Sir." [12:14:44][D][text_sensor:064]: 'text_response': Sending state 'Very well, Sir.' [12:14:44][D][voice_assistant:627]: Event Type: 98 [12:14:44][D][voice_assistant:768]: TTS stream start [12:14:44][D][esp-idf:000][speaker_task]: I (412589) I2S: DMA Malloc info, datalen=blocksize=2048, dma_buf_count=8 [12:14:44] [12:14:44][D][esp-idf:000][speaker_task]: I (412594) I2S: I2S0, MCLK output by GPIO2 [12:14:44] [12:14:44][D][esp-idf:000][speaker_task]: I (412598) AUDIO_PIPELINE: link el->rb, el:0x3d059248, tag:raw, rb:0x3d0593b8 [12:14:44] [12:14:44][D][esp-idf:000][speaker_task]: I (412600) AUDIO_ELEMENT: [raw-0x3d059248] Element task created [12:14:44] [12:14:44][D][esp-idf:000][speaker_task]: I (412603) AUDIO_ELEMENT: [i2s-0x3d058fa4] Element task created [12:14:44] [12:14:44][D][esp-idf:000][speaker_task]: I (412603) AUDIO_PIPELINE: Func:audio_pipeline_run, Line:359, MEM Total:16471871 Bytes, Inter:70436 Bytes, Dram:70436 Bytes [12:14:44] [12:14:44] [12:14:44][D][esp-idf:000][i2s]: I (412607) AUDIO_ELEMENT: [i2s] AEL_MSG_CMD_RESUME,state:1 [12:14:44] [12:14:44][D][esp-idf:000][i2s]: I (412608) I2S_STREAM: AUDIO_STREAM_WRITER [12:14:44] [12:14:44][D][esp-idf:000][speaker_task]: I (412609) AUDIO_PIPELINE: Pipeline started [12:14:44] [12:14:44][W][component:237]: Component voice_assistant took a long time for an operation (267 ms). [12:14:44][W][component:238]: Components should block for at most 30 ms. [12:14:44][D][voice_assistant:627]: Event Type: 8 [12:14:44][D][voice_assistant:703]: Response URL: "http://<IP_ADDRESS>:8123/api/tts_proxy/7fa2c56ba8483f251bddd92eaf57c912805af57a_en_ec8f721e35_tts.elevenlabs_tts.wav" [12:14:44][D][voice_assistant:504]: State changed from AWAITING_RESPONSE to STREAMING_RESPONSE [12:14:44][D][voice_assistant:510]: Desired state set to STREAMING_RESPONSE [12:14:44][D][voice_assistant:627]: Event Type: 2 [12:14:44][D][voice_assistant:717]: Assist Pipeline ended [12:14:45][D][voice_assistant:627]: Event Type: 99 [12:14:45][D][voice_assistant:776]: TTS stream end [12:14:45][D][voice_assistant:375]: End of audio stream received [12:14:45][D][voice_assistant:504]: State changed from STREAMING_RESPONSE to RESPONSE_FINISHED [12:14:45][D][voice_assistant:510]: Desired state set to RESPONSE_FINISHED [12:14:47][D][esp-idf:000][speaker_task]: W (415282) AUDIO_PIPELINE: There are no listener registered [12:14:47] [12:14:47][D][esp-idf:000][speaker_task]: I (415284) AUDIO_PIPELINE: audio_pipeline_unlinked [12:14:47] [12:14:47][D][esp-idf:000][speaker_task]: W (415286) AUDIO_ELEMENT: [i2s] Element has not create when AUDIO_ELEMENT_TERMINATE [12:14:47] [12:14:47][D][esp-idf:000][speaker_task]: I (415290) I2S: DMA queue destroyed [12:14:47] [12:14:47][D][esp-idf:000][speaker_task]: W (415294) AUDIO_ELEMENT: [filter] Element has not create when AUDIO_ELEMENT_TERMINATE [12:14:47] [12:14:47][D][esp-idf:000][speaker_task]: W (415296) AUDIO_ELEMENT: [raw] Element has not create when AUDIO_ELEMENT_TERMINATE [12:14:47] [12:14:47][D][voice_assistant:407]: Speaker has finished outputting all audio [12:14:47][D][voice_assistant:504]: State changed from RESPONSE_FINISHED to IDLE [12:14:47][D][voice_assistant:510]: Desired state set to IDLE [12:14:47][W][component:237]: Component voice_assistant took a long time for an operation (219 ms). [12:14:47][W][component:238]: Components should block for at most 30 ms. [12:14:47][D][micro_wake_word:178]: State changed from IDLE to START_MICROPHONE [12:14:47][D][micro_wake_word:116]: Starting Microphone [12:14:47][D][micro_wake_word:178]: State changed from START_MICROPHONE to STARTING_MICROPHONE [12:14:47][W][micro_wake_word:158]: Wake word is already running [12:14:47][W][micro_wake_word:158]: Wake word is already running [12:14:47][D][esp-idf:000][read_task]: I (415528) I2S: DMA Malloc info, datalen=blocksize=512, dma_buf_count=8 [12:14:47] [12:14:47][D][esp-idf:000][read_task]: I (415532) I2S: I2S0, MCLK output by GPIO2 [12:14:47] [12:14:47][D][esp-idf:000][read_task]: I (415536) AUDIO_PIPELINE: link el->rb, el:0x3d0593a8, tag:i2s, rb:0x3d0597bc [12:14:47] [12:14:47][D][esp-idf:000][read_task]: I (415540) AUDIO_PIPELINE: link el->rb, el:0x3d05951c, tag:filter, rb:0x3d05b7fc [12:14:47] [12:14:47][D][esp-idf:000][read_task]: I (415544) AUDIO_ELEMENT: [i2s-0x3d0593a8] Element task created [12:14:47] [12:14:47][D][esp-idf:000][read_task]: I (415546) AUDIO_THREAD: The filter task allocate stack on external memory [12:14:47] [12:14:47][D][esp-idf:000][read_task]: I (415549) AUDIO_ELEMENT: [filter-0x3d05951c] Element task created [12:14:47] [12:14:47][D][esp-idf:000][read_task]: I (415551) AUDIO_ELEMENT: [raw-0x3d05964c] Element task created [12:14:47] [12:14:47][D][esp-idf:000][read_task]: I (415555) AUDIO_PIPELINE: Func:audio_pipeline_run, Line:359, MEM Total:16483287 Bytes, Inter:89092 Bytes, Dram:89092 Bytes [12:14:47] [12:14:47] [12:14:47][D][esp-idf:000][i2s]: I (415557) AUDIO_ELEMENT: [i2s] AEL_MSG_CMD_RESUME,state:1 [12:14:47] [12:14:47][D][esp-idf:000][filter]: I (415560) AUDIO_ELEMENT: [filter] AEL_MSG_CMD_RESUME,state:1 [12:14:47] [12:14:47][D][esp-idf:000][filter]: I (415562) RSP_FILTER: sample rate of source data : 16000, channel of source data : 2, sample rate of destination data : 16000, channel of destination data : 1 [12:14:47] [12:14:47][D][esp-idf:000][read_task]: I (415566) AUDIO_PIPELINE: Pipeline started [12:14:47] [12:14:47][D][esp_adf.microphone:273]: Microphone started [12:14:47][D][micro_wake_word:178]: State changed from STARTING_MICROPHONE to DETECTING_WAKE_WORD [12:14:58][D][micro_wake_word:363]: Wake word sliding average probability is 0.571 and most recent probability is 1.000 [12:14:58][D][micro_wake_word:129]: Wake Word Detected [12:14:58][D][micro_wake_word:178]: State changed from DETECTING_WAKE_WORD to STOP_MICROPHONE [12:14:58][D][micro_wake_word:135]: Stopping Microphone [12:14:58][D][esp_adf.microphone:234]: Stopping microphone [12:14:58][D][micro_wake_word:178]: State changed from STOP_MICROPHONE to STOPPING_MICROPHONE [12:14:58][D][esp-idf:000][filter]: W (426636) AUDIO_ELEMENT: IN-[filter] AEL_IO_ABORT [12:14:58] [12:14:58][D][esp-idf:000][read_task]: E (426638) AUDIO_ELEMENT: [filter] Element already stopped [12:14:58] [12:14:58][D][esp-idf:000][read_task]: W (426670) AUDIO_PIPELINE: There are no listener registered [12:14:58] [12:14:58][D][esp-idf:000][read_task]: I (426672) AUDIO_PIPELINE: audio_pipeline_unlinked [12:14:58] [12:14:58][D][esp-idf:000][read_task]: W (426674) AUDIO_ELEMENT: [i2s] Element has not create when AUDIO_ELEMENT_TERMINATE [12:14:58] [12:14:58][D][esp-idf:000][read_task]: I (426676) I2S: DMA queue destroyed [12:14:58] [12:14:58][D][esp-idf:000][read_task]: W (426676) AUDIO_ELEMENT: [filter] Element has not create when AUDIO_ELEMENT_TERMINATE [12:14:58] [12:14:58][D][esp-idf:000][read_task]: W (426678) AUDIO_ELEMENT: [raw] Element has not create when AUDIO_ELEMENT_TERMINATE [12:14:58] [12:14:58][D][esp_adf.microphone:285]: Microphone stopped [12:14:58][D][micro_wake_word:178]: State changed from STOPPING_MICROPHONE to IDLE [12:14:58][D][voice_assistant:504]: State changed from IDLE to START_MICROPHONE [12:14:58][D][voice_assistant:510]: Desired state set to WAIT_FOR_VAD [12:14:58][D][voice_assistant:221]: Starting Microphone [12:14:58][D][voice_assistant:504]: State changed from START_MICROPHONE to STARTING_MICROPHONE [12:14:58][D][esp-idf:000][read_task]: I (426694) I2S: DMA Malloc info, datalen=blocksize=512, dma_buf_count=8 [12:14:58] [12:14:58][D][esp-idf:000][read_task]: I (426698) I2S: I2S0, MCLK output by GPIO2 [12:14:58] [12:14:58][D][esp-idf:000][read_task]: I (426701) AUDIO_PIPELINE: link el->rb, el:0x3d0593a8, tag:i2s, rb:0x3d0597bc [12:14:58] [12:14:58][D][esp-idf:000][read_task]: I (426706) AUDIO_PIPELINE: link el->rb, el:0x3d05951c, tag:filter, rb:0x3d05b7fc [12:14:58] [12:14:58][D][esp-idf:000][read_task]: I (426709) AUDIO_ELEMENT: [i2s-0x3d0593a8] Element task created [12:14:58] [12:14:58][D][esp-idf:000][read_task]: I (426711) AUDIO_THREAD: The filter task allocate stack on external memory [12:14:58] [12:14:58][D][esp-idf:000][read_task]: I (426714) AUDIO_ELEMENT: [filter-0x3d05951c] Element task created [12:14:58] [12:14:58][D][esp-idf:000][read_task]: I (426716) AUDIO_ELEMENT: [raw-0x3d05964c] Element task created [12:14:58] [12:14:58][D][esp-idf:000][read_task]: I (426718) AUDIO_PIPELINE: Func:audio_pipeline_run, Line:359, MEM Total:16483287 Bytes, Inter:89092 Bytes, Dram:89092 Bytes [12:14:58] [12:14:58] [12:14:58][D][esp-idf:000][i2s]: I (426722) AUDIO_ELEMENT: [i2s] AEL_MSG_CMD_RESUME,state:1 [12:14:58] [12:14:58][D][esp-idf:000][filter]: I (426724) AUDIO_ELEMENT: [filter] AEL_MSG_CMD_RESUME,state:1 [12:14:58] [12:14:58][D][esp-idf:000][filter]: I (426727) RSP_FILTER: sample rate of source data : 16000, channel of source data : 2, sample rate of destination data : 16000, channel of destination data : 1 [12:14:58] [12:14:58][D][esp-idf:000][read_task]: I (426730) AUDIO_PIPELINE: Pipeline started [12:14:58] [12:14:58][D][esp_adf.microphone:273]: Microphone started [12:14:58][D][voice_assistant:504]: State changed from STARTING_MICROPHONE to WAIT_FOR_VAD [12:14:58][D][voice_assistant:245]: Waiting for speech... [12:14:58][D][voice_assistant:504]: State changed from WAIT_FOR_VAD to WAITING_FOR_VAD [12:15:01][D][voice_assistant:258]: VAD detected speech [12:15:01][D][voice_assistant:504]: State changed from WAITING_FOR_VAD to START_PIPELINE [12:15:01][D][voice_assistant:510]: Desired state set to STREAMING_MICROPHONE [12:15:01][D][voice_assistant:275]: Requesting start... [12:15:01][D][voice_assistant:504]: State changed from START_PIPELINE to STARTING_PIPELINE [12:15:01][D][voice_assistant:525]: Client started, streaming microphone [12:15:01][D][voice_assistant:504]: State changed from STARTING_PIPELINE to STREAMING_MICROPHONE [12:15:01][D][voice_assistant:510]: Desired state set to STREAMING_MICROPHONE [12:15:01][D][voice_assistant:627]: Event Type: 1 [12:15:01][D][voice_assistant:630]: Assist Pipeline running [12:15:01][D][voice_assistant:627]: Event Type: 9 [12:15:02][D][voice_assistant:627]: Event Type: 10 [12:15:02][D][voice_assistant:636]: Wake word detected [12:15:02][D][voice_assistant:627]: Event Type: 3 [12:15:02][D][voice_assistant:641]: STT started [12:15:02][D][text_sensor:064]: 'text_request': Sending state '...' [12:15:02][D][text_sensor:064]: 'text_response': Sending state '...' [12:15:02][W][component:237]: Component voice_assistant took a long time for an operation (223 ms). [12:15:02][W][component:238]: Components should block for at most 30 ms. [12:15:04][D][voice_assistant:627]: Event Type: 11 [12:15:04][D][voice_assistant:781]: Starting STT by VAD [12:15:04][D][voice_assistant:627]: Event Type: 12 [12:15:04][D][voice_assistant:785]: STT by VAD end [12:15:04][D][voice_assistant:504]: State changed from STREAMING_MICROPHONE to STOP_MICROPHONE [12:15:04][D][voice_assistant:510]: Desired state set to AWAITING_RESPONSE [12:15:04][D][esp_adf.microphone:234]: Stopping microphone [12:15:04][D][voice_assistant:504]: State changed from STOP_MICROPHONE to STOPPING_MICROPHONE [12:15:04][D][esp-idf:000][filter]: W (433163) AUDIO_ELEMENT: IN-[filter] AEL_IO_ABORT [12:15:04] [12:15:04][D][esp-idf:000][read_task]: E (433165) AUDIO_ELEMENT: [filter] Element already stopped [12:15:04] [12:15:05][D][esp-idf:000][read_task]: W (433196) AUDIO_PIPELINE: There are no listener registered [12:15:05] [12:15:05][D][esp-idf:000][read_task]: I (433197) AUDIO_PIPELINE: audio_pipeline_unlinked [12:15:05] [12:15:05][D][esp-idf:000][read_task]: W (433199) AUDIO_ELEMENT: [i2s] Element has not create when AUDIO_ELEMENT_TERMINATE [12:15:05] [12:15:05][D][esp-idf:000][readtask]: I (433203) I2S: DMA queue destroyed [12:15:05] [12:15:05][D][esp-idf:000][read_task]: W (433205) AUDIO_ELEMENT: [filter] Element has not create when AUDIO_ELEMENT_TERMINATE [12:15:05] [12:15:05][D][esp-idf:000][read_task]: W (433207) AUDIO_ELEMENT: [raw] Element has not create when AUDIO_ELEMENT_TERMINATE [12:15:05] [12:15:05][W][component:237]: Component voice_assistant took a long time for an operation (240 ms). [12:15:05][W][component:238]: Components should block for at most 30 ms. [12:15:05][D][voice_assistant:627]: Event Type: 4 [12:15:05][D][voice_assistant:655]: Speech recognised as: "Never mind." [12:15:05][D][text_sensor:064]: 'text_request': Sending state 'Never mind.' [12:15:05][W][component:237]: Component voice_assistant took a long time for an operation (237 ms). [12:15:05][W][component:238]: Components should block for at most 30 ms. [12:15:05][D][voice_assistant:627]: Event Type: 5 [12:15:05][D][voice_assistant:660]: Intent started [12:15:05][D][esp_adf.microphone:285]: Microphone stopped [12:15:05][D][voice_assistant:504]: State changed from STOPPING_MICROPHONE to AWAITING_RESPONSE [12:15:06][D][voice_assistant:627]: Event Type: 6 [12:15:06][D][voice_assistant:627]: Event Type: 7 [12:15:06][D][voice_assistant:683]: Response: "Understood, Sir." [12:15:06][D][text_sensor:064]: 'text_response': Sending state 'Understood, Sir.' [12:15:06][D][voice_assistant:627]: Event Type: 98 [12:15:06][D][voice_assistant:768]: TTS stream start [12:15:06][D][esp-idf:000][speaker_task]: I (434300) I2S: DMA Malloc info, datalen=blocksize=2048, dma_buf_count=8 [12:15:06] [12:15:06][D][esp-idf:000][speaker_task]: I (434306) I2S: I2S0, MCLK output by GPIO2 [12:15:06] [12:15:06][D][esp-idf:000][speaker_task]: I (434308) AUDIO_PIPELINE: link el->rb, el:0x3d059248, tag:raw, rb:0x3d0593b8 [12:15:06] [12:15:06][D][esp-idf:000][speaker_task]: I (434310) AUDIO_ELEMENT: [raw-0x3d059248] Element task created [12:15:06] [12:15:06][D][esp-idf:000][speaker_task]: I (434313) AUDIO_ELEMENT: [i2s-0x3d058fa4] Element task created [12:15:06] [12:15:06][D][esp-idf:000][speaker_task]: I (434313) AUDIO_PIPELINE: Func:audio_pipeline_run, Line:359, MEM Total:16469927 Bytes, Inter:68492 Bytes, Dram:68492 Bytes [12:15:06] [12:15:06] [12:15:06][D][esp-idf:000][i2s]: I (434317) AUDIO_ELEMENT: [i2s] AEL_MSG_CMD_RESUME,state:1 [12:15:06] [12:15:06][D][esp-idf:000][i2s]: I (434318) I2S_STREAM: AUDIO_STREAM_WRITER [12:15:06] [12:15:06][D][esp-idf:000][speaker_task]: I (434319) AUDIO_PIPELINE: Pipeline started [12:15:06] [12:15:06][W][component:237]: Component voice_assistant took a long time for an operation (265 ms). [12:15:06][W][component:238]: Components should block for at most 30 ms. [12:15:06][D][voice_assistant:627]: Event Type: 8 [12:15:06][D][voice_assistant:703]: Response URL: "http://<IP_ADDRESS>:8123/api/tts_proxy/ad6a435acd1929a5b2dcbe2eaab8ef26ce1af229_en_ec8f721e35_tts.elevenlabs_tts.wav" [12:15:06][D][voice_assistant:504]: State changed from AWAITING_RESPONSE to STREAMING_RESPONSE [12:15:06][D][voice_assistant:510]: Desired state set to STREAMING_RESPONSE [12:15:06][D][voice_assistant:627]: Event Type: 2 [12:15:06][D][voice_assistant:717]: Assist Pipeline ended [12:15:07][D][voice_assistant:627]: Event Type: 99 [12:15:07][D][voice_assistant:776]: TTS stream end [12:15:07][D][voice_assistant:375]: End of audio stream received [12:15:07][D][voice_assistant:504]: State changed from STREAMING_RESPONSE to RESPONSE_FINISHED [12:15:07][D][voice_assistant:510]: Desired state set to RESPONSE_FINISHED [12:15:08][D][esp-idf:000][speaker_task]: W (436930) AUDIO_PIPELINE: There are no listener registered [12:15:08] [12:15:08][D][esp-idf:000][speaker_task]: I (436932) AUDIO_PIPELINE: audio_pipeline_unlinked [12:15:08] [12:15:08][D][esp-idf:000][speaker_task]: W (436934) AUDIO_ELEMENT: [i2s] Element has not create when AUDIO_ELEMENT_TERMINATE [12:15:08] [12:15:08][D][esp-idf:000][speaker_task]: I (436938) I2S: DMA queue destroyed [12:15:08] [12:15:08][D][esp-idf:000][speaker_task]: W (436942) AUDIO_ELEMENT: [filter] Element has not create when AUDIO_ELEMENT_TERMINATE [12:15:08] [12:15:08][D][esp-idf:000][speaker_task]: W (436945) AUDIO_ELEMENT: [raw] Element has not create when AUDIO_ELEMENT_TERMINATE [12:15:08] [12:15:08][D][voice_assistant:407]: Speaker has finished outputting all audio [12:15:08][D][voice_assistant:504]: State changed from RESPONSE_FINISHED to IDLE [12:15:08][D][voice_assistant:510]: Desired state set to IDLE [12:15:08][W][component:237]: Component voice_assistant took a long time for an operation (218 ms). [12:15:08][W][component:238]: Components should block for at most 30 ms. [12:15:09][D][micro_wake_word:178]: State changed from IDLE to START_MICROPHONE [12:15:09][D][micro_wake_word:116]: Starting Microphone [12:15:09][D][micro_wake_word:178]: State changed from START_MICROPHONE to STARTING_MICROPHONE [12:15:09][D][esp-idf:000][read_task]: I (437176) I2S: DMA Malloc info, datalen=blocksize=512, dma_buf_count=8 [12:15:09] [12:15:09][D][esp-idf:000][read_task]: I (437180) I2S: I2S0, MCLK output by GPIO2 [12:15:09] [12:15:09][D][esp-idf:000][read_task]: I (437184) AUDIO_PIPELINE: link el->rb, el:0x3d0593a8, tag:i2s, rb:0x3d0597bc [12:15:09] [12:15:09][0;36m[D][esp-idf:000][read_task]: I (437188) AUDIO_PIPELINE: link el->rb, el:0x3d05951c, tag:filter, rb:0x3d05b7fc [12:15:09] [12:15:09][D][esp-idf:000][read_task]: I (437191) AUDIO_ELEMENT: [i2s-0x3d0593a8] Element task created [12:15:09] [12:15:09][D][esp-idf:000][read_task]: I (437193) AUDIO_THREAD: The filter task allocate stack on external memory [12:15:09] [12:15:09][D][esp-idf:000][read_task]: I (437196) AUDIO_ELEMENT: [filter-0x3d05951c] Element task created [12:15:09] [12:15:09][D][esp-idf:000][read_task]: I (437198) AUDIO_ELEMENT: [raw-0x3d05964c] Element task created [12:15:09] [12:15:09][D][esp-idf:000][read_task]: I (437200) AUDIO_PIPELINE: Func:audio_pipeline_run, Line:359, MEM Total:16483111 Bytes, Inter:88916 Bytes, Dram:88916 Bytes [12:15:09] [12:15:09] [12:15:09][D][esp-idf:000][i2s]: I (437204) AUDIO_ELEMENT: [i2s] AEL_MSG_CMD_RESUME,state:1 [12:15:09] [12:15:09][D][esp-idf:000][filter]: I (437206) AUDIO_ELEMENT: [filter] AEL_MSG_CMD_RESUME,state:1 [12:15:09] [12:15:09][D][esp-idf:000][filter]: I (437208) RSP_FILTER: sample rate of source data : 16000, channel of source data : 2, sample rate of destination data : 16000, channel of destination data : 1 [12:15:09] [12:15:09][D][esp-idf:000][read_task]: I (437212) AUDIO_PIPELINE: Pipeline started [12:15:09] [12:15:09][D][esp_adf.microphone:273]: Microphone started [12:15:09][D][micro_wake_word:178]: State changed from STARTING_MICROPHONE to DETECTING_WAKE_WORD [12:15:12][D][micro_wake_word:363]: Wake word sliding average probability is 0.592 and most recent probability is 1.000 [12:15:12][D][micro_wake_word:129]: Wake Word Detected [12:15:12][D][micro_wake_word:178]: State changed from DETECTING_WAKE_WORD to STOP_MICROPHONE [12:15:12][D][micro_wake_word:135]: Stopping Microphone [12:15:12][D][esp_adf.microphone:234]: Stopping microphone [12:15:12][D][micro_wake_word:178]: State changed from STOP_MICROPHONE to STOPPING_MICROPHONE [12:15:12][D][esp-idf:000][filter]: W (441021) AUDIO_ELEMENT: IN-[filter] AEL_IO_ABORT [12:15:12] [12:15:12][D][esp-idf:000][read_task]: E (441023) AUDIO_ELEMENT: [filter] Element already stopped [12:15:12] [12:15:12][D][esp-idf:000][read_task]: W (441055) AUDIO_PIPELINE: There are no listener registered [12:15:12] [12:15:12][D][esp-idf:000][read_task]: I (441057) AUDIO_PIPELINE: audio_pipeline_unlinked [12:15:12] [12:15:12][D][esp-idf:000][read_task]: W (441059) AUDIO_ELEMENT: [i2s] Element has not create when AUDIO_ELEMENT_TERMINATE [12:15:12] [12:15:12][D][esp-idf:000][read_task]: I (441061) I2S: DMA queue destroyed [12:15:12] [12:15:12][D][esp-idf:000][read_task]: W (441063) AUDIO_ELEMENT: [filter] Element has not create when AUDIO_ELEMENT_TERMINATE [12:15:12] [12:15:12][D][esp-idf:000][read_task]: W (441065) AUDIO_ELEMENT: [raw] Eement has not create when AUDIO_ELEMENT_TERMINATE [12:15:12] [12:15:12][D][esp_adf.microphone:285]: Microphone stopped [12:15:12][D][micro_wake_word:178]: State changed from STOPPING_MICROPHONE to IDLE [12:15:12][D][voice_assistant:504]: State changed from IDLE to START_MICROPHONE [12:15:12][D][voice_assistant:510]: Desired state set to WAIT_FOR_VAD [12:15:12][D][voice_assistant:221]: Starting Microphone [12:15:12][D][voice_assistant:504]: State changed from START_MICROPHONE to STARTING_MICROPHONE [12:15:12][D][esp-idf:000][read_task]: I (441086) I2S: DMA Malloc info, datalen=blocksize=512, dma_buf_count=8 [12:15:12] [12:15:12][D][esp-idf:000][read_task]: I (441090) I2S: I2S0, MCLK output by GPIO2 [12:15:12] [12:15:12][D][esp-idf:000][read_task]: I (441094) AUDIO_PIPELINE: link el->rb, el:0x3d0593a8, tag:i2s, rb:0x3d0597bc [12:15:12] [12:15:12][D][esp-idf:000][read_task]: I (441098) AUDIO_PIPELINE: link el->rb, el:0x3d05951c, tag:filter, rb:0x3d05b7fc [12:15:12] [12:15:12][D][esp-idf:000][read_task]: I (441101) AUDIO_ELEMENT: [i2s-0x3d0593a8] Element task created [12:15:12] [12:15:12][D][esp-idf:000][read_task]: I (441103) AUDIO_THREAD: The filter task allocate stack on external memory [12:15:12] [12:15:12][D][esp-idf:000][read_task]: I (441106) AUDIO_ELEMENT: [filter-0x3d05951c] Element task created [12:15:12] [12:15:12][D][esp-idf:000][read_task]: I (441108) AUDIO_ELEMENT: [raw-0x3d05964c] Element task created [12:15:12] [12:15:12][D][esp-idf:000][read_task]: I (441110) AUDIO_PIPELINE: Func:audio_pipeline_run, Line:359, MEM Total:16483111 Bytes, Inter:88916 Bytes, Dram:88916 Bytes [12:15:12] [12:15:12] [12:15:12][D][esp-idf:000][i2s]: I (441114) AUDIO_ELEMENT: [i2s] AEL_MSG_CMD_RESUME,state:1 [12:15:12] [12:15:12][D][esp-idf:000][filter]: I (441116) AUDIO_ELEMENT: [filter] AEL_MSG_CMD_RESUME,state:1 [12:15:12] [12:15:12][D][esp-idf:000][filter]: I (441119) RSP_FILTER: sample rate of source data : 16000, channel of source data : 2, sample rate of destination data : 16000, channel of destination data : 1 [12:15:12] [12:15:12][D][esp-idf:000][read_task]: I (441122) AUDIO_PIPELINE: Pipeline started [12:15:12] [12:15:12][D][esp_adf.microphone:273]: Microphone started [12:15:12][D][voice_assistant:504]: State changed from STARTING_MICROPHONE to WAIT_FOR_VAD [12:15:12][D][voice_assistant:245]: Waiting for speech... [12:15:12][D][voice_assistant:504]: State changed from WAIT_FOR_VAD to WAITING_FOR_VAD [12:15:15][D][voice_assistant:258]: VAD detected speech [12:15:15][D][voice_assistant:504]: State changed from WAITING_FOR_VAD to START_PIPELINE [12:15:15][D][voice_assistant:510]: Desired state set to STREAMING_MICROPHONE [12:15:15][D][voice_assistant:275]: Requesting start... [12:15:15][D][voice_assistant:504]: State changed from START_PIPELINE to STARTING_PIPELINE [12:15:15][D][voice_assistant:525]: Client started, streaming microphone [12:15:15][D][voice_assistant:504]: State changed from STARTING_PIPELINE to STREAMING_MICROPHONE [12:15:15][D][voice_assistant:510]: Desired state set to STREAMING_MICROPHONE [12:15:15][D][voice_assistant:627]: Event Type: 1 [12:15:15][D][voice_assistant:630]: Assist Pipeline running [12:15:15][D][voice_assistant:627]: Event Type: 9 [12:15:20][D][voice_assistant:627]: Event Type: 0 [12:15:20][D][voice_assistant:627]: Event Type: 2 [12:15:20][D][voice_assistant:717]: Assist Pipeline ended [12:15:20][D][voice_assistant:504]: State changed from STREAMING_MICROPHONE to WAIT_FOR_VAD [12:15:20][D][voice_assistant:510]: Desired state set to WAITING_FOR_VAD [12:15:20][D][voice_assistant:245]: Waiting for speech... [12:15:20][D][voice_assistant:504]: State changed from WAIT_FOR_VAD to WAITING_FOR_VAD [12:15:21][D][voice_assistant:258]: VAD detected speech [12:15:21][D][voice_assistant:504]: State changed from WAITING_FOR_VAD to START_PIPELINE [12:15:21][D][voice_assistant:510]: Desired state set to STREAMING_MICROPHONE [12:15:21][D][voice_assistant:275]: Requesting start... [12:15:21][D][voice_assistant:504]: State changed from START_PIPELINE to STARTING_PIPELINE [12:15:21][D][voice_assistant:525]: Client started, streaming microphone [12:15:21][D][voice_assistant:504]: State changed from STARTING_PIPELINE to STREAMING_MICROPHONE [12:15:21][D][voice_assistant:510]: Desired state set to STREAMING_MICROPHONE [12:15:21][D][voice_assistant:627]: Event Type: 1 [12:15:21][D][voice_assistant:630]: Assist Pipeline running [12:15:21][D][voice_assistant:627]: Event Type: 9 [12:15:25][D][voice_assistant:627]: Event Type: 10 [12:15:25][D][voice_assistant:636]: Wake word detected [12:15:25][D][voice_assistant:627]: Event Type: 3 [12:15:25][D][voice_assistant:641]: STT started [12:15:25][D][text_sensor:064]: 'text_request': Sending state '...' [12:15:25][D][text_sensor:064]: 'text_response': Sending state '...' [12:15:25][W][component:237]: Component voice_assistant took a long time for an operation (222 ms). [12:15:25][W][component:238]: Components should block for at most 30 ms. [12:15:26][D][voice_assistant:627]: Event Type: 11 [12:15:26][D][voice_assistant:781]: Starting STT by VAD [12:15:27][D][voice_assistant:627]: Event Type: 12 [12:15:27][D][voice_assistant:785]: STT by VAD end [12:15:27][D][voice_assistant:504]: State changed from STREAMING_MICROPHONE to STOP_MICROPHONE [12:15:27][D][voice_assistant:510]: Desired state set to AWAITING_RESPONSE [12:15:27][D][esp_adf.microphone:234]: Stopping microphone [12:15:27][D][voice_assistant:504]: State changed from STOP_MICROPHONE to STOPPING_MICROPHONE [12:15:27][D][esp-idf:000][filter]: W (455618) AUDIO_ELEMENT: IN-[filter] AEL_IO_ABORT [12:15:27] [12:15:27][D][esp-idf:000][read_task]:E (455620) AUDIO_ELEMENT: [filter] Element already stopped [12:15:27] [12:15:27][D][esp-idf:000][read_task]: W (455651) AUDIO_PIPELINE: There are no listener registered [12:15:27] [12:15:27][D][esp-idf:000][read_task]: I (455653) AUDIO_PIPELINE: audio_pipeline_unlinked [12:15:27] [12:15:27][D][esp-idf:000][read_task]: W (455655) AUDIO_ELEMENT: [i2s] Element has not create when AUDIO_ELEMENT_TERMINATE [12:15:27] [12:15:27][D][esp-idf:000][read_task]: I (455657) I2S: DMA queue destroyed [12:15:27] [12:15:27][D][esp-idf:000][read_task]: W (455659) AUDIO_ELEMENT: [filter] Element has not create when AUDIO_ELEMENT_TERMINATE [12:15:27] [12:15:27][D][esp-idf:000][read_task]: W (455661) AUDIO_ELEMENT: [raw] Element has not create when AUDIO_ELEMENT_TERMINATE [12:15:27] [12:15:27][W][component:237]: Component voice_assistant took a long time for an operation (241 ms). [12:15:27][W][component:238]: Components should block for at most 30 ms. [12:15:27][D][voice_assistant:627]: Event Type: 4 [12:15:27][D][voice_assistant:655]: Speech recognised as: "Never mind." [12:15:27][D][text_sensor:064]: 'text_request': Sending state 'Never mind.' [12:15:27][W][component:237]: Component voice_assistant took a long time for an operation (239 ms). [12:15:27][W][component:238]: Components should block for at most 30 ms. [12:15:27][D][voice_assistant:627]: Event Type: 5 [12:15:27][D][voice_assistant:660]: Intent started [12:15:27][D][esp_adf.microphone:285]: Microphone stopped [12:15:27][D][voice_assistant:504]: State changed from STOPPING_MICROPHONE to AWAITING_RESPONSE [12:15:28][D][voice_assistant:627]: Event Type: 6 [12:15:28][D][voice_assistant:627]: Event Type: 7 [12:15:28][D][voice_assistant:683]: Response: "As you wish, Sir." [12:15:28][D][text_sensor:064]: 'text_response': Sending state 'As you wish, Sir.' [12:15:28][D][voice_assistant:627]: Event Type: 98 [12:15:28][D][voice_assistant:768]: TTS stream start [12:15:28][D][esp-idf:000][speaker_task]: I (456621) I2S: DMA Malloc info, datalen=blocksize=2048, dma_buf_count=8 [12:15:28] [12:15:28][D][esp-idf:000][speaker_task]: I (456624) I2S: I2S0, MCLK output by GPIO2 [12:15:28] [12:15:28][D][esp-idf:000][speaker_task]: I (456628) AUDIO_PIPELINE: link el->rb, el:0x3d059248, tag:raw, rb:0x3d0593b8 [12:15:28] [12:15:28][D][esp-idf:000][speaker_task]: I (456630) AUDIO_ELEMENT: [raw-0x3d059248] Element task created [12:15:28] [12:15:28][D][esp-idf:000][speaker_task]: I (456634) AUDIO_ELEMENT: [i2s-0x3d058fa4] Element task created [12:15:28] [12:15:28][D][esp-idf:000][speaker_task]: I (456634) AUDIO_PIPELINE: Func:audio_pipeline_run, Line:359, MEM Total:16474895 Bytes, Inter:73460 Bytes, Dram:73460 Bytes [12:15:28] [12:15:28] [12:15:28][D][esp-idf:000][i2s]: I (456638) AUDIO_ELEMENT: [i2s] AEL_MSG_CMD_RESUME,state:1 [12:15:28] [12:15:28][D][esp-idf:000][i2s]: I (456639) I2S_STREAM: AUDIO_STREAM_WRITER [12:15:28] [12:15:28][D][esp-idf:000][speaker_task]: I (456640) AUDIO_PIPELINE: Pipeline started [12:15:28] [12:15:28][W][component:237]: Component voice_assistant took a long time for an operation (265 ms). [12:15:28][W][component:238]: Components should block for at most 30 ms. [12:15:28][D][voice_assistant:627]: Event Type: 8 [12:15:28][D][voice_assistant:703]: Response URL: "http://<IP_ADDRESS>:8123/api/tts_proxy/174c1a4b8d7a365dffc8b2bbee1b3ba69e8c84c7_en_ec8f721e35_tts.elevenlabs_tts.wav" [12:15:28][D][voice_assistant:504]: State changed from AWAITING_RESPONSE to STREAMING_RESPONSE [12:15:28][D][voice_assistant:510]: Desired state set to STREAMING_RESPONSE [12:15:28][D][voice_assistant:627]: Event Type: 2 [12:15:28][D][voice_assistant:717]: Assist Pipeline ended [12:15:28][D][esp-idf:000][i2s]: W (457142) AUDIO_ELEMENT: IN-[i2s] AEL_IO_ABORT [12:15:28] [12:15:30][D][voice_assistant:627]: Event Type: 99 [12:15:30][D][voice_assistant:776]: TTS stream end [12:15:30][D][voice_assistant:375]: End of audio stream received [12:15:30][D][voice_assistant:504]: State changed from STREAMING_RESPONSE to RESPONSE_FINISHED [12:15:30][D][voice_assistant:510]: Desired state set to RESPONSE_FINISHED [12:15:31][D][esp-idf:000][speaker_task]: W (459186) AUDIO_PIPELINE: There are no listener registered [12:15:31] [12:15:31][D][esp-idf:000][speaker_task]: I (459188) AUDIO_PIPELINE: audio_pipeline_unlinked [12:15:31] [12:15:31][D][esp-idf:000][speaker_task]: W (459190) AUDIO_ELEMENT: [i2s] Element has not create when AUDIO_ELEMENT_TERMINATE [12:15:31] [12:15:31][D][esp-idf:000][speaker_task]: I (459194) I2S: DMA queue destroyed [12:15:31] [12:15:31][D][esp-idf:000][speaker_task]: W (459198) AUDIO_ELEMENT: [filter] Element has not create when AUDIO_ELEMENT_TERMINATE [12:15:31] [12:15:31][D][esp-idf:000][speaker_task]: W (459200) AUDIO_ELEMENT: [raw] Element has not create when AUDIO_ELEMENT_TERMINATE [12:15:31]

Same experience here, I need to repeat the wakeword twice.

Same problem here. I have to repeat the word awakening several times.

The new update should have fixed this. I believe this was because it starts streaming audio after it detects the first wake word. My guess is you have local wake word to 'hey_jarvis' and open wake word to "okay_nabu". One thing that worked for me after I did the update is change the option on the device to go from 'On Device' to "In Home Assistant", and then change it back. I am not sure, but I believe there is some variable that gets written in the beginning that doesn't get over written when it should. Doing this seems to fix that issue. However, I believe they have to fix that issue properly in the firmware code.

Yes, I confirm that after the update everything works as expected.


code won't form with the theme

Hello, my code sections do not take the theme
asciidoctor-pdf version :

part of the theme "code" block in theme.yml :
code:
  font-color: #333333
  font-family: Courier Prime Sans
  font-style: normal
  font-size: 10
  background-color: #f6f6f6
  border-color: #0f80aa
  border-radius: 2

code in my .adoc file
[source,powershell]
----
Get-Command New*
----

command :
asciidoctor-pdf -a pdf-themesdir=. -a pdf-theme=theme.yml -a pdf-fontsdir=fonts -a iconsdir=icons myfile.adoc

result :

Do you have any idea pls ?

Please direct questions to the project chat. The issue tracker is not the right place to ask for support. You can find our support policy on the following page: https://docs.asciidoctor.org/about/support/


Add Python API tutorial on object recognition

Hi Wu!
I'm requesting a new entry for a tutorial by Mort Canty (GH, Twitter) that wasn't a good fit for us to host as an EE Community Tutorial (see issue).
Thanks for your consideration

Many thanks for adding this, Justin!

Thanks! :)


[Infineon] Add Implementation for Door Lock cluster

Change overview
Add Implementation for Door Lock cluster.
Testing
TC-DRLK-*

Accepted for 1.0: platform change


Proving keys should be handled by the package that uses them

currently, proving keys are downloaded by a script in the extension's package.json. this should be handled by the package/build step of the wasm package that actually needs the keys.

https://github.com/penumbra-zone/penumbra/issues/4130


Auditor forced pwd change fails

creating a new user with role=auditor
when forced to change pwd at first login, we get the following error:
Sep 17 21:55:18 fworch-comp fworch-ui[2785]: Audit - AuthenticateUser (Login.razor in line 142): user au successfully authenticated
Sep 17 21:55:28 fworch-comp fworch-ui[2785]: Error - Request "ChangePassword" (RequestSender.cs in line 68): An error occured while sending request "ChangePassword".
Sep 17 21:55:28 fworch-comp fworch-ui[2785]:  ---
Sep 17 21:55:28 fworch-comp fworch-ui[2785]: Exception thrown:
Sep 17 21:55:28 fworch-comp fworch-ui[2785]:  JsonException
Sep 17 21:55:28 fworch-comp fworch-ui[2785]: Message:
Sep 17 21:55:28 fworch-comp fworch-ui[2785]:  The input does not contain any JSON tokens. Expected the input to start with a ```

Reason is the missing API permission to change own password in uiuser table for auditor role (works for e.g. reporter).
For the current setup with auditor used as a demo user this is actually OK. But for a standard auditor he/she should be able to change the password.
Maybe it is time to split auditor role into auditor/demo role now?

suggest to leave this for phase 2 - issue already exists: #854

duplicate to #854


saveFile produces empty file after upgrade to 0.2.0 (Web)

After I upgraded from v0.1.1 to v0.2.0 the resulting file on web release is empty.
Code before:
final Uint8List data = Uint8List.fromList(csv.codeUnits);

MimeType type = MimeType.CSV;

await FileSaver.instance.saveFile(
  "inventory.csv",
  data,
  "csv",
  mimeType: type);

After upgrade:
final Uint8List data = Uint8List.fromList(csv.codeUnits);

MimeType type = MimeType.csv;

await FileSaver.instance.saveFile(
  name: "inventory.csv",
  bytes: data,
  ext: "csv",
  mimeType: type);

Flutter/Dart versions are 3.7.8/2.19.5

Okay, sure, I'll test it out, I just wanna know 1 thing, from where are you generating/getting the file

Thanks a lot! :)
The "csv" variable is a string filled with the csv-formatted data. Debugging shows me correct contents of "csv" and "data" so these shouldn't be the issue.

https://github.com/incrediblezayed/file_saver/blob/54aba56e6d3df700925340407fa6dfba2eadcbbd/lib/file_saver_web.dart#L45
This line seems to cause the problem: Blob should take "fileModel.bytes" as argument instead of "fileModel.name".

Thanks a lot! :)
https://github.com/incrediblezayed/file_saver/blob/54aba56e6d3df700925340407fa6dfba2eadcbbd/lib/file_saver_web.dart#L45
This line seems to cause the problem: Blob should take "fileModel.bytes" as argument instead of "fileModel.name".
Currently it writes only the file name into the file but not the contents.

Oops, a silly mistake, actually I was trying something new for web and that might have messed it up

Came here to report the same issue with 0.2.0 -- seems like the fix is quite straight forward :)

Came here to report the same issue with 0.2.0 -- seems like the fix is quite straight forward :)

This will be fixed tonight don't worry

Thanks for the update!
I'll close the issue :-)

Thanks for the update!
I'll close the issue :-)

Thank you as well, keep supporting please