chore: consolidate dependencies in yarn.lock

Description of changes
Resolve to a single version for babel-loader<EMAIL_ADDRESS><EMAIL_ADDRESS>=> version 8.3.0.
Since there's only 1 version of babel-loader, there's no more dependency on<EMAIL_ADDRESS>so yarn resolves the dependency to just version 2.0.3

Description of how you validated changes
yarn test
Checklist

[x] PR description included
[x] yarn test passes
[x] Pull request labels are added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #11345 (37d999a) into dev (644faa1) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev   #11345   +/-   ##
=======================================
  Coverage   49.67%   49.68%
=======================================
  Files         684      684
  Lines       32956    32956
  Branches     6720     6720
=======================================
+ Hits        16372    16373    +1
+ Misses      15094    15093    -1
  Partials     1490     1490

Impacted Files
Coverage Δ

...li/src/domain/amplify-usageData/getUsageDataUrl.ts
100.00% <0.00%> (+12.50%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Closing in favor of https://github.com/aws-amplify/amplify-cli/pull/11389


MvxImageLoadingView - notification about image loading finished

Trying to figure it out how to check if the image has been loaded and cannot find if it is already done or where it sits ? ImageLoaderTask is always null if I set image through DataLocationUri. Any ideas?

Hi @Immons,
Did you try to set those properties:
https://github.com/luberda-molinet/FFImageLoading/blob/fc351f8a7ffc8110c2e172e7e877312c7b40c81a/source/FFImageLoading.Cross/MvxImageLoadingView.cs#L73-L77
?

@Immons Any news?

@Immons MvxImageLoadingView is now depreciated. Try the new MvxCachedImageView which has the callbacks you want.
Fully working example here: https://github.com/luberda-molinet/FFImageLoading/tree/master/samples/ImageLoading.MvvmCross.Sample


Updated version and download URL

docker build -t sonar-test . was failing because Sonar changed the URL link. I fixed the link and added the latest version as well.

I am so sorry I missed this. I got notifications disabled somehow.

Fixed via #3 sorry for the delay

no worries!


feat: support conditional policies

fixes: #118
Add support for conditional policies based on design document.
PTAL: @broady @jkwlui @JesseLovelace @chingor13

Hi @chingor13 @JesseLovelace @jkwlui @broady,
I resolved presubmit checks, please review when you have a moment. Thank you!

Thanks for the review @chingor13, below I've added links to example usage:
https://github.com/googleapis/google-cloud-java/pull/7128
PLMK if you have suggestions. Thank you for your review.

@chingor13 @elharo friendly ping. The PR is ready for another review and I've addressed comments.

cc: @netdpb (David)

I'll make a separate list and file an issue to track it. Thanks @chingor13!


Integrate modular core contracts + mintableERCxxx extensions

Problem solved
Short description of the bug fixed or feature added
Changes made

[ ] Public API changes: list the public API changes made if any
[ ] Internal API changes: explain the internal logic changes

How to test

[ ] Automated tests: link to unit test file
[ ] Manual tests: step by step instructions on how to test

Contributor NFT
Paste in your wallet address below and we will airdrop you a special NFT when your pull request is merged.
Address:

#3413  👈
main

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

Join @joaquim-verges and the rest of your teammates on  Graphite


filebeat can not push to kafka

filebeat version 6.6.0
kafka version 2.11
env: docker
the follow is my Dockerfile

l use command docker run -d  --restart always --name=filebeat nx_filebeat setup filebeat
the follow is my filebeat.yml

@ClementeGao we can’t really help on this without the logging output from Sarama
If you add the following block to your filebeat config you should get some debug output from Sarama to show what’s happening with kafka
logging:
  level: debug
  to_files: false
  to_syslog: false

here?

do not create topic in kafka i guess the filebeat dot have connect to kafka   but l do not know why  l really ping kafka host

@dnwe


Deadlinks

When using links to documents, they must not move.
URL testing happens in our tests doesn't prevent URLs in emails to be dead in the future.

Need to ensure all URLs are also tested as part of the generated material. There seems to be instances where it isn't in scope of the current CI tests.

Also realized that the URLs generated via the draw.io graphic are never assessed as the local file is a compressed XML: our tests wouldn't be able to test those!

those compressed XML are rendered as HTML in the browser though. There must be something to leverage and use to test

Tests are ran before the site is rendered, we need deploy tests before
merging
Le ven. 2 août 2019 08 h 25, Rémy Bernard<EMAIL_ADDRESS>a
écrit :

those compressed XML are rendered as HTML in the browser though. There
must be something to leverage and use to test
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/sara-sabr/ITStrategy/issues/157?email_source=notifications&email_token=AAM4TZLENA5SW4B33S33VO3QCQRS3A5CNFSM4IISGUJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3NS3EQ#issuecomment-517680530,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAM4TZJCCJF7QQHPXT67K6LQCQRS3ANCNFSM4IISGUJQ
.

For ORE we run HTMLProofer and HTML5Validator.  I think they can both check links on the site.
But it wont fix old links we shared before we created the sebsite
https://github.com/canada-ca/ore-ero/blob/master/.travis.yml

Definitely, those are two issues we need to work separately. Part one is
going to be fixed in my next PR (moving all documents into pages by default)
Part two, we'd need the proofing you just mentioned.
Le ven. 2 août 2019 10 h 06, Sébastien Lemay<EMAIL_ADDRESS>a
écrit :

For ORE we run HTMLProofer and HTML5Validator. I think they can both check
links on the site.
But it wont fix old links we shared before we created the sebsite
https://github.com/canada-ca/ore-ero/blob/master/.travis.yml
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/sara-sabr/ITStrategy/issues/157?email_source=notifications&email_token=AAM4TZOJMZ5GBIC6W7J5MYLQCQ5O3A5CNFSM4IISGUJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3N3ACA#issuecomment-517713928,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAM4TZKQM3OPXW6XSXJ2FEDQCQ5O3ANCNFSM4IISGUJQ
.

@gcharest can we discuss versioning before the PR?
I.e. how do we communicate the maturity of documents/pages from "an idea" to "work in progress" to "approved"

@remyb2canada moving the files won't display them until we add the front matter so it's essentially the same as leaving them in the wip-tec folder for us.
See Contributing Jekyll Pages info for more details :D

:+1:

In fact, this is more consistent as if we keep a document in wip-tec but are ready to "publish" it, we'd need to move it to the pages folder for consistency.
The end user of the site wouldn't see that workflow but people who would have consulted the actual wip-tec documents would lose the access to that URL at the time which isn't right.

@smellems if you have a few cycles in the upcoming week, setting up HTMLProofer and HTML5Validator could be a great addition to our tests.
If not, I'll try to have a look myself.

#278 enables the markdown link checking for external links.

Markdown link checking is now working during the build.  This checks links in markdown files and not the resulting HTML. but It's good to validate that external link work.  Internal links are now shown as warnings so that we can see what they are and fix them as needed.
This test can be run using npm run link-check
The HTML on the live site can be validate using npm run site-validator
This will crawl internal links and validate the HTML but I don't think it fails on dead links


ManagedReconciler could be used as a general purpose reconciler

What observation are you making?
The managed reconciler provides a rich set of functionalities and features that saves the developer from an extensive amount of boiler-plate code. In particular, the break-down of operations into 4 distinct categories could be extended to a lot of reconcilers, not necessarily the ones that are managing an external resource. I have personally found this pattern much more intuitive when writing new reconcilers (even when it's not managing an external cloud resource), as it provides a nice logical scaffolding for the resource reconciliation , and leaving the rest to be taken care of by the managed reconciler (e.g. deletion timestamp handling, status update, etc...).

Do you have any suggestions?

I suggest to remove the assumption that the library only can be used for external cloud resources. I think the current ExternalClient interface could be generalized and renamed to something like ResourceDriver, which provides the same interface. Some other limitations (for instance https://github.com/crossplane/crossplane-runtime/issues/101) could be also lifted.

I like this idea in principle, but it might be a a little difficult to implement. Presumably we do get some benefits from the managed reconciler logic assuming it's reconciling crossplane managed resources; i.e. expecting the resources being managed to have certain fields and satisfy a certain interface.
Perhaps it would be possible to nest these concerns? Something like managed.Reconciler that extends a more generic resource.Reconciler?


Make.defs: Fix to exclude loadable apps from builtin app list

Summary

When an application is built as a loadable app, the application name should not be shown in the builtin app list (i.e. apps/builtin/buitlin_list.h) This PR does not create .bdat as well as .pdat if an application is built as a loadble.

Impact

This PR affects application build for both builtin and loadable.

Testing

I checked this PR with spresense:rndis and spresense:wifi which include both builtin apps and loadable apps.

I only tested on Ubuntu. However, I applied the changes to Windows native build as well (please see the changes).

@anchao keep the entry intentionly because .bdat contain one important information: the main stack size. Without this information, some application which need a bigger stack size can't start up correctly.
We discuss a better solution internally: embed this type of information into ELF(maybe a special section), but hasn't time to implemnt.

@anchao keep the entry intentionly because .bdat contain one important information:
the main stack size. Without this information, some application which need a bigger stack size >can't start up correctly.

@xiaoxiang781216 However, what happens if we disable builtin apps (CONFIG_NSH_BUILTIN_APPS=n) but enable loadable apps (CONFIG_NSH_FILE_APPS=y)

@anchao keep the entry intentionly because .bdat contain one important information:
the main stack size. Without this information, some application which need a bigger stack size >can't start up correctly.

@xiaoxiang781216 However, what happens if we disable builtin apps (CONFIG_NSH_BUILTIN_APPS=n) but enable loadable apps (CONFIG_NSH_FILE_APPS=y)

If I remeber correctly: @anchao also modify the launch code a little bit, so nsh will reference this information regardless wether CONFIG_NSH_BUILTIN_APPS iis on or off.

After @anchao review the related code, nuttx side has a bug which block what we want, @masayuki2009 here is the patch fix, please take a look:
https://github.com/apache/incubator-nuttx/pull/333

I started to merge this into the pr80 branch.  But it looks like there is some discussion.
What is the resolution?  Should I merge this?  Or should it be closed with merging?

Yes, this patch may make the application which need the bigger stack size can't launch. Before we get the better solution, it's better to keep the current state.

It is merged on the pr80 branch, but has not been merged to master.  Sorry I did not read the discussion completely.  Please advise.

It's better to close without merge before @masayuki2009 find the method resolve the issue I mention in this thread.

I cannot close without merge, but I can remove the pr80 branch without merging to master.  That is effectively the same thing... except that the PR cannot be re-opened.
I need to read comments more carefully.  There are more PRs than I can handle and I do not always do  a perfect job at merging them.

@xiaoxiang781216 @patacongo I've just read what you discussed while asleep.

After @anchao review the related code, nuttx side has a bug which block what we want, >@masayuki2009 here is the patch fix, please take a look:
apache/incubator-nuttx#333

I checked  apache/incubator-nuttx#333 and I think this would be a workaround to load an application with big stack size.
However,  apache/incubator-nuttx#333 does not solve this issue (i.e. When an application is built as a loadable app, the application name should not be shown in the builtin app list).
I think my this PR can solve the above issue and now can co-exist with apache/incubator-nuttx#333 .
What do you think?

@xiaoxiang781216 @patacongo I've just read what you discussed while asleep.

After @anchao review the related code, nuttx side has a bug which block what we want, >@masayuki2009 here is the patch fix, please take a look:
apache/incubator-nuttx#333

I checked apache/incubator-nuttx#333 and I think this would be a workaround to load an application with big stack size.
However, apache/incubator-nuttx#333 does not solve this issue (i.e. When an application is built as a loadable app, the application name should not be shown in the builtin app list).
I think my this PR can solve the above issue and now can co-exist with apache/incubator-nuttx#333 .
What do you think?

We need a new method which remove loadable apps from help but keep the info in .pdat, so the fix could modify cmd_help to skip the item with null entry pointer.
But there is a side effect I need point out: this workaround work only when user enter something like:
nsh >hello
The full path name can't work:
nsh >/mnt/hello
Since the entry finding match the whole string.
With the help output plus the search path(PATH=/mnt), user naturally issue the first format.

Hi, @xiaoxiang781216,

The full path name can't work:
nsh >/mnt/hello

Oh, really?
I tried with my patch and it works as I expected.
nsh> help
help usage:  help [-v] []
[          cp         exec       ifup       mksmartfs  reboot     time
?          cmp        exit       kill       mh         rm         true
addroute   dirname    false      ls         mount      rmdir      uname
arp        date       free       mb         mv         route      umount
basename   dd         help       md5        mw         set        unset
break      delroute   hexdump    mkdir      nslookup   sh         usleep
cat        df         ifconfig   mkfatfs    ps         sleep      wget
cd         echo       ifdown     mkrd       pwd        test       xd
Builtin Apps:
webserver  ping       ostest     nsh         <== no hello apps shown
nsh> hello
Hello, World!! <== hello ELF apps at /mnt/sd0/bin works
nsh> mv /mnt/sd0/bin/hello /mnt/sd0/hello  <== move the file to /mnt/sd0
nsh> hello
nsh: hello: command not found  <== no command found (because CONFIG_PATH_INITIAL="/mnt/sd0/bin")
nsh> /mnt/sd0/hello
Hello, World!!  <== command with full path works
nsh>

BTW, the workaround also require that we add the binary folder to PATH, otherwise we can't launch the program by short name.

BTW, the workaround also require that we add the binary folder to PATH,
otherwise we can't launch the program by short name.

Yes. I know.
nsh> env
PATH=/mnt/sd0/bin <== It's the same as CONFIG_PATH_INITIAL

Hi, @xiaoxiang781216,

The full path name can't work:
nsh >/mnt/hello

Oh, really?
I tried with my patch and it works as I expected.

I mean the workaround which pass the big stack size to posix_spawn can't work. Yes, we can still launch the program but with the default and small stack size.
hello is handled by nsh_builtin(->exec_builtin->posix_spawn)
/mnt/hello is handled by nsh_fileapp(->posix_spawn)
The stacksize happen inside exec_builtin, so the 2nd case can't get the correct stack size.

nsh> help
help usage: help [-v] []
[ cp exec ifup mksmartfs reboot time
? cmp exit kill mh rm true
addroute dirname false ls mount rmdir uname
arp date free mb mv route umount
basename dd help md5 mw set unset
break delroute hexdump mkdir nslookup sh usleep
cat df ifconfig mkfatfs ps sleep wget
cd echo ifdown mkrd pwd test xd
Builtin Apps:
webserver ping ostest nsh <== no hello apps shown
nsh> hello
Hello, World!! <== hello ELF apps at /mnt/sd0/bin works

with your patch, stack size will be ELF_STACKSIZE
without, stack size will be EXAMPLES_HELLO_STACKSIZE

nsh> mv /mnt/sd0/bin/hello /mnt/sd0/hello <== move the file to /mnt/sd0
nsh> hello
nsh: hello: command not found <== no command found (because CONFIG_PATH_INITIAL="/mnt/sd0/bin")
nsh> /mnt/sd0/hello
Hello, World!! <== command with full path works

with/without your patch, ELF_STACKSIZE is used.

nsh>

so the workaround can pass the right stack size(EXAMPLES_HELLO_STACKSIZE) in hello case, but fail with full path(/mnt/hello).

@xiaoxiang781216 Thanks for the detailed explanation on how stack size will be affected with/without the patch. Just for your information. In our products, we added a new environment value to change ELF_STACKSIZE to load an application which needs a large stack.

See https://github.com/apache/incubator-nuttx-apps/pull/158 as well.


manifest: update sof module

Update SOF module to latest main.
Signed-off-by: Iuliana Prodan<EMAIL_ADDRESS>

@iuliana-prodan so I've just had notifications from Zephyr CI that the SOF module main branch update failed. I'm not sure if this is due to the change to main from master or something else. It cant be a build failure since the west manifest is not updated and still pointing to the old branch and commit.

After adding this commit, that updates the manifest with the commit id from main branch, I did a west update sof and it brought me the latest SOF module.

so I've just had notifications from Zephyr CI that the SOF module main branch update failed.

Can you share a link?  I don't see any failure here.

so I've just had notifications from Zephyr CI that the SOF module main branch update failed.

Can you share a link? I don't see any failure here.

Thank you @marc-hb !
https://github.com/zephyrproject-rtos/sof/actions/runs/1071625778
https://github.com/zephyrproject-rtos/sof/actions/runs/1071625775
https://github.com/zephyrproject-rtos/sof/actions/runs/1071625776

Thanks @lgirdwood for the links. What's happening is the zephyrproject-rtos/sof fork[*] tries to run the same github actions than the original thesofproject/sof, because it shares the same .github/ directory. Then it fails because of configuration differences.
["fork" is how github calls any remote clone whether it actually branches out or not. There is no formal definition of the word "fork". This is discussing a github problem so I'm using github terminology]
The fix is to simply disable github actions on zephyrproject-rtos/sof  https://docs.github.com/en/github/administering-a-repository/managing-repository-settings/disabling-or-limiting-github-actions-for-a-repository.
We have no interest in maintaining github actions that work across forks, especially not when that "fork" is not actually branching out and would re-run the same github actions on the same commits on which they have already been run in the original repo. No value in that.

@marc-hb thanks, so you mean this is an AR for Zephyr team to disable locally for SOF module in the GH settings ?

@marc-hb thanks, so you mean this is an AR for Zephyr team to disable locally for SOF module in the GH settings ?

Yes, exactly that - and probably for most other zephyrproject-rtos/forks using github actions too.
It looks like github enables this by default which makes no sense: https://github.community/t/stop-github-actions-running-on-a-fork/17965/3. Maybe they'll stop enabling this by default once some hackers figure out how to abuse it? https://www.infoq.com/news/2021/04/GitHub-actions-cryptomining/

Can somebody, please, merge this - is pending for a week now.
cc: @nashif @MaureenHelm @lgirdwood @dbaluta @dcpleung @dleach02

@iuliana-prodan merging is blocked as the buildkite check is failing. Can you check and fix.

there is a build failure for samples/subsys/audio/sof/sample.audio.sof that needs to be resolved.. not sure if this is associated with the manifest change or not

@lgirdwood @dleach02 I've looked on the failure and it seem like the rimage submodule is not brought into modules/audio/sof:
-- Git submodules update
fatal: Needed a single revision
Unable to find current revision in submodule path '../rimage'
CMake Error at /workdir/modules/audio/sof/scripts/cmake/git-submodules.cmake:47 (message):
  git submodule update --init failed with 1, please checkout submodules
Call Stack (most recent call first):
  CMakeLists.txt:23 (include)

I still couldn't figure out, yet, why is not bringing the rimage submodule.
cc: @carlescufi @nashif @dcpleung

@nashif do we need to do anything else when pushing commits from SOF main to SOF module main ? We are just do a synchronisation ?

Usually, you need to push changes as a PR, you also need to keep the local changes of the module.
This does not seem to be the case here.

@lgirdwood we need this in the SOF tree: https://github.com/thesofproject/sof/pull/4594

@lgirdwood we need this in the SOF tree: thesofproject/sof#4594, then we could just have a clean fork of SOF

Thanks @nashif SOF https://github.com/thesofproject/sof/pull/4594 now merged.

@iuliana-prodan are you able to shed any light on the rimage issue ? @kv2019i fyi.
Could this be a result of changing branch master -> main for rimage after the initial rimage commit ID and branch was added to west ?

@iuliana-prodan are you able to shed any light on the rimage issue ? @kv2019i fyi.
Could this be a result of changing branch master -> main for rimage after the initial rimage commit ID and branch was added to west ?

@lgirdwood the problem is this commit: https://github.com/thesofproject/sof/pull/3993/commits/c6b6d74aef3f652c66f13a4d145c14b1f661807b that changes the rimage repo URL to a relative path.
On Zephyr project we have a fork of SOF, but not of rimage repo.
That's why the rimage submodule is not brought with SOF.
A solution is to revert this commit just in the SOF fork: set the rimage URL as https://github.com/thesofproject/rimage.git.
Or clone/fork rimage repo on Zephyr project.
I prefer the 1st fix.
Do you agree with this?
cc: @marc-hb @nashif @kv2019i @dleach02 @MaureenHelm @dcpleung @carlescufi @dbaluta

@iuliana-prodan are you able to shed any light on the rimage issue ? @kv2019i fyi.
Could this be a result of changing branch master -> main for rimage after the initial rimage commit ID and branch was added to west ?

@lgirdwood the problem is this commit: thesofproject/sof@c6b6d74 that changes the rimage repo URL to a relative path.
On Zephyr project we have a fork of SOF, but not of rimage repo.
That's why the rimage submodule is not brought with SOF.
A solution is to revert this commit just in the SOF fork: set the rimage URL as https://github.com/thesofproject/rimage.git.
Or clone/fork rimage repo on Zephyr project.
I prefer the 1st fix.
Do you agree with this?
cc: @marc-hb @nashif @kv2019i @dleach02 @MaureenHelm @dcpleung @carlescufi @dbaluta

Ok, @marc-hb is back from vacation today - lets wait for his feedback as he is working on the Zephyr integration too so this may be part of his plans (and possible missing further updates). I think he was looking at better integration with west.

the problem is this commit: thesofproject/sof@c6b6d74 that changes the rimage repo URL to a relative path.

Interesting but why does it fail only now? sof/.gitmodules already has a relative path right now in Zephyr even before this PR: https://github.com/zephyrproject-rtos/sof/blob/779f28ed465c0/.gitmodules
This PR does NOT change sof/.gitmodules, it's been like this in Zephyr since May 24:
https://github.com/zephyrproject-rtos/zephyr/pull/35559/files
Unable to find current revision also does not really sound like a failure to find the entire submodule, does it? I will try to reproduce.

A solution is to revert this commit just in the SOF fork: set the rimage URL as https://github.com/thesofproject/rimage.git

I believe upstream Zephyr has a policy not to point at external git repos (that can come and go).
From https://docs.zephyrproject.org/latest/guides/modules.html#module-repositories

All modules included in the default manifest shall be hosted in repositories under the zephyrproject-rtos GitHub organization.

the problem is this commit: thesofproject/sof@c6b6d74 that changes the rimage repo URL to a relative path.

Interesting but why does it fail only now? sof/.gitmodules already has a relative path right now in Zephyr even before this PR: https://github.com/zephyrproject-rtos/sof/blob/779f28ed465c0/.gitmodules
This PR does NOT change sof/.gitmodules, it's been like this in Zephyr since May 24:
https://github.com/zephyrproject-rtos/zephyr/pull/35559/files

I don't see any tests run on https://github.com/zephyrproject-rtos/sof/tree/779f28ed465c03899c8a7d4aaf399856f4e51158.
The last pull request (before the current falling one) is https://github.com/zephyrproject-rtos/sof/pull/11 and I don't see any tests or builds.
Are you sure this really worked before the relative path change?

Audio tests in shard 3/20 passed in https://buildkite.com/zephyr/zephyr/builds/31091#a0d6c1c0-1509-4fd6-b8b1-42389e2046fe for SOF update https://github.com/zephyrproject-rtos/zephyr/pull/35559/files

I don't see any tests run on https://github.com/zephyrprojectrtos/sof/tree/779f28ed465c03899c8a7d4aaf399856f4e51158.

There should be no CI on the zephyrprojectrtos/sof/ "fork", see July 27th discussion above. CI is on upstream thesofproject/sof and on zephyrprojectrtos/zephyr/

It could be caused by https://github.com/thesofproject/sof/commit/f6c71c21d03b8111 that added a dependency on the sof-logger, stay tuned.

It could be caused by thesofproject/sof@f6c71c2 that added a dependency on the sof-logger and smex, stay tuned.

Confirmed.
The spurious sof-logger -> rimage dependency is fixed by https://github.com/thesofproject/sof/pull/4669
I tested this more and found that smex does not depend on rimage either. smex depends only on a small ext_manifest.h file which can be copied (and was copied into sof/zephyr by https://github.com/zephyrproject-rtos/sof/pull/7). I worked around this smex issue by copying ext_manifest.h manually into some made-up directory and that was enough to build zephyr/samples/subsys/audio/sof fully and successfully. Will hopefully find a clean way to fix this smex issue tomorrow.
tl;dr: the Zephyr build should still not need any rimage clone.

@marc-hb @iuliana-prodan SOF patches are now merged. Is there any work needed for this to get in?

@marc-hb @iuliana-prodan SOF patches are now merged.

This fixed only one rimage dependency.

Is there any work needed for this to get in?

I'm finalizing another and last SOF PR to remove the remaining rimage dependencies.

@marc-hb  I like to understand if we can hep with that, as we figured out today that zephyr merge window is Friday :)

They were actually not just 2 but 3 rimage-related failures in this PR:

Fail1 sof-logger misses rimage. Already fixed by https://github.com/thesofproject/sof/pull/4669

Fail2.1 smex misses   #include <rimage/__/ext_manifest.h>

Fail2.2 SOF FW misses #include <rimage/__/ext_manifest.h>

Fail2.1 and Fail2.2 are both addressed by brand new https://github.com/thesofproject/sof/pull/4682
Fail1 and Fail2.1 were new and caused by the recent addition of sof-logger and smex in https://github.com/thesofproject/sof/commit/f6c71c21d03b8111
Failure 2.2 was NOT new! It used to be "fixed" by a Zephyr-specific copy of rimage/__/ext_manifest.h in commit https://github.com/nashif/sof/blob/973de63bef8658ed/zephyr/include/rimage/sof/kernel/ext_manifest.h / https://github.com/zephyrproject-rtos/sof/pull/7 but this PR drops 973de63bef8!
This should be the very first time a "clean", unmodified SOF commit builds in Zephyr CI! Crossing fingers...


Try typecast returned by method Query::count() value to integer

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
❌

Fixed issues
#23

Sorry I am going to improve the tests and I made the wrong branch checking the pr, i already reverted it, and I am checking because the tests do not pass if it works locally.

closed solved in dev branch.


Make the difficulty cataloguetype ID not include the resource location. Fixes SpongeAPI#1254

In reference to https://github.com/SpongePowered/SpongeAPI/issues/1254
This uses just the name for the ID of Difficulty, rather than the resource location.
It makes more sense to use just the name, as it firstly fixes the issue above, and the ID should be something easily identifiable, which options.difficulty.etc isn't,
Edit:
This was tested by running

System.out.println(Sponge.getGame().getRegistry().getType(Difficulty.class, "easy"));
The output was
Optional[EASY]

IMO we should use the minecraft: prefix more  consistently.

As @ST-DDT said, could you make the ids be prefixed with minecraft:? Take a look at BlockTypeRegistryModule for how it's done.

@Aaron1011 Done.


PAF dataset problem about classnames_idxs

Hello，Thank you for your invaluable work.I've met some problems using train_dp_PAF.py. In the function evaluate_one_epoch,  the values of classnames_idxs seem incorrect. The values of classnames_idxs are as follows:
classnames_idxs = [0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,                        1000,1001,1002,1003,1004,1005,1006,1007,1008,1009,1010,                        1011,1012,1013,1014,1015,1016,1017,1018,1019,1020,                        2000,2001,2002,2003,2004,2005,2006,                        3000,3001,3002,3003,3004,3005,3006]
but the PAF.json file that records the categories of the PAF dataset only contains 10 classes.
{"arm crossing": 0, "get up": 1, "jumping": 2, "kicking": 3, "picking up": 4, "sit down": 5, "throwing": 6, "turning around": 7, "walking": 8, "waving": 9}
Is classnames_idxs correct? If it is incorrect, what is the correct value?
Looking forward to your reply

I have rewrite the corresponding part to ensure the classnames_idxs is correct.

I have rewritten the relevant section to ensure the classnames_idxs is accurate.

Thanks a lot for the assistance!


Is there a way to define the initalState only in the model?

I love this repo, it has helped me a lot. However, I don't like the idea of defining the initial state in the Root model. Is there a way to define the initial state in the model, and then import it into the root model?

Closing this because I realized you can just simply export an initial state from the model itself.

Closing this because I realized you can just simply export an initial state from the model itself.


[Backport to v0.8] Upgrade Zookeeper to 3.5.8

Backport #1853 to v0.8 branch.
It should be synchronised, done and tested together with #1919

Tested:
✔ epicli apply with 2 kafka nodes
✔ epicli upgrade with 2 kafka nodes: upgraded ZooKeeper from v3.4.12 (epicli v0.7) to v3.5.8 (epicli v0.8)


Public projects - Window resizing is needed to show DOIs for projects

While on the page of an study e.g. https://nmrxiv.org/S83 the DOI 10.57992/nmrxiv.p16.s83 is shown in a badge, although not copyable see #773 , the corresponding project page https://nmrxiv.org/P16 does not show the DOI corresponding 10.57992/nmrxiv.p16 .
DOI of project should be added to UI.

Actually it is shown be resizing of the page is needed. I will change the title of the issue accordingly. Thanks for reporting

Found it on 133% zoom.


Feature: Update interval should distinguish if there is flow or not

It would be great if it would be possible to have not only the i option which allows to specify the general update interval but also to specific it more in detail, e.g -i 20/300 which would then request the BMS every 20 seconds if there is flow but only every 5 minutes if the battery is idle based on the latest received value. This would improve energy consumption a lot.

I'm not sure I follow.  Are you asking to compare the output with a previous collection and then if no change, don't send anything?  I don't know if I've ever seen output that didnt change (even by .001) from the previous pull.
I'll give this some thought, however, it might require I compare based on a percentage change vs absolute values.

Thanks for your response.
Basically yes, but not a collection. At least in my case I can say that I only need high frequent polling if the battery is not idle (so it is actively charging or discharging) if none of these is happening right now I don’t need high frequent polling.
So I would do the first poll on program Start, then check charge if 0 use the idle poll interval, else the regular poll interval. On next poll again check if idle and then use the appropriate interval.
Of course it can happen that I just have polled on idle state and one second later it will chat free or discharge but that’s the downside I would take.


Update timescale logo in diagrams

Description

Timescale did a rebrand a couple months ago in which the logo changed.
I have updated the Timescale logos used in several diagrams to reflect these changes.
Thank you.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@JeremyTheocharis CF is stuck here, can you manually overwrite ?


Bump actions to same versions as github-config uses

Summary
Sync changes made in https://github.com/paketo-buildpacks/github-config/pull/715 and https://github.com/paketo-buildpacks/github-config/pull/716
Use Cases
Keep the pipelines alive
Checklist

[x] I have viewed, signed, and submitted the Contributor License Agreement.
[x] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[x] I have added an integration test, if necessary.
[x] I have reviewed the styleguide for guidance on my code quality.
[x] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

@phil9909 this PR just needs to be rebased against main before I can merge it in

done


Error running Groovy REPL

I am attempting the Rama tutorial and after cloning the repo and running mvn compile successfully, I have attempted to run a Groovy REPL with:
$ mvn gplus:shell

but receive the following error:
[INFO] Scanning for projects...
[INFO]
[INFO] -----------------------< com.rpl:rama-examples >------------------------
[INFO] Building rama-examples 1.0.0-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- gmavenplus-plugin:1.13.1:shell (default-cli) @ rama-examples ---
[INFO] Using isolated classloader, without GMavenPlus classpath.
[INFO] Using Groovy 3.0.9 to perform shell.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  1.050 s
[INFO] Finished at: 2023-08-24T19:05:04-04:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.gmavenplus:gmavenplus-plugin:1.13.1:shell (default-cli) on project rama-examples: Error occurred while calling a method on a Groovy class from classpath.: InvocationTargetException: BUG! exception in phase 'semantic analysis' in source unit 'Script1.groovy' Unsupported class file major version 63 -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Please let me know if any additional information would be useful.

This is the java I was using when I encountered the issue:
openjdk version "19.0.2" 2023-01-17
OpenJDK Runtime Environment GraalVM CE 22.3.1 (build 19.0.2+7-jvmci-22.3-b12)
OpenJDK 64-Bit Server VM GraalVM CE 22.3.1 (build 19.0.2+7-jvmci-22.3-b12, mixed mode, sharing)

and I'm running NixOS 23.05. I can confirm that things work as expected using JDK17. Thanks for the tip! If it would be helpful I could send a small change to the README mentioning this caveat?

Sure, please do.

I ran into the same problem, I got this error:
[ERROR] Failed to execute goal org.codehaus.gmavenplus:gmavenplus-plugin:1.13.1:shell (default-cli) on project rama-examples: Error occurred while calling a method on a Groovy class from classpath.: InvocationTargetException: BUG! exception in phase 'semantic analysis' in source unit 'Script1.groovy' Unsupported class file major version 64 -> [Help 1]

when running the shell with Java 20:
> java --version
openjdk 20.0.2 2023-07-18
OpenJDK Runtime Environment Temurin-20.0.2+9 (build 20.0.2+9)
OpenJDK 64-Bit Server VM Temurin-20.0.2+9 (build 20.0.2+9, mixed mode)

With java version 17 it dit work.

I'm getting the same error, but with Java 17:
> java --version                                                                                branch: on master
java 17.0.8 2023-07-18 LTS
Java(TM) SE Runtime Environment (build 17.0.8+9-LTS-211)
Java HotSpot(TM) 64-Bit Server VM (build 17.0.8+9-LTS-211, mixed mode, sharing)


Feature Request: Introducing "Secret" Field Type

Context
You know when we need to store sensitive stuff like API keys, secret keys, and other hush-hush data in the database? Well, right now, it's up to us to make sure these data are encrypted before storing and decrypted when we need them. This back-and-forth can be a pain and sometimes it feels like a game of hide-and-seek where we're always "it".
Proposal
So, let's spice things up with a new field type called "secret". What's cool about "secret"?
It Does the Heavy Lifting: When you store data in the 'secret' field, PocketBase would automatically encrypt it. And when you need that data back, it'll decrypt it on-the-fly for you. No more manual encrypt-decrypt shenanigans.
Safety First: By handling the encryption right at the database level, we're reducing the chance of data leaks from potential app vulnerabilities or breaches. Think of it as a safe within a safe.
Potential Approach
We could use a tried-and-true encryption algorithm like AES-256 for the 'secret' field. The keys for encryption/decryption could be securely stored and managed using a Key Management Service (KMS) or we could bake them right into PocketBase.
Benefits
Adding this feature would mean:

Leveling up the security of any app using PocketBase.
Saying goodbye to the hassle of dealing with client-side encryption and decryption.
Making life easier for devs who need to interact with sensitive data.

What's Next?
I'd love to hear your thoughts on this. Maybe there's already a simple way of doing this and this feature makes little sense 🤷
Got any insights on potential challenges, or suggestions for improvements and alternative approaches? Let's get this conversation started!

Something like this was requested before (eg. https://github.com/pocketbase/pocketbase/discussions/1835#discussioncomment-4946404), but for me the main issue with a secret field is that it is not clear how this field will be managed, who will have access to its value and whether the filter/sort operations will work at all.
Could you elaborate on your use case and how do you plan using it?

Context
You know when we need to store sensitive stuff like API keys, secret keys, and other hush-hush data in the database? Well, right now, it's up to us to make sure these data are encrypted before storing and decrypted when we need them. This back-and-forth can be a pain and sometimes it feels like a game of hide-and-seek where we're always "it".
Proposal
So, let's spice things up with a new field type called "secret". What's cool about "secret"?
It Does the Heavy Lifting: When you store data in the 'secret' field, PocketBase would automatically encrypt it. And when you need that data back, it'll decrypt it on-the-fly for you. No more manual encrypt-decrypt shenanigans.
Safety First: By handling the encryption right at the database level, we're reducing the chance of data leaks from potential app vulnerabilities or breaches. Think of it as a safe within a safe.
Potential Approach
We could use a tried-and-true encryption algorithm like AES-256 for the 'secret' field. The keys for encryption/decryption could be securely stored and managed using a Key Management Service (KMS) or we could bake them right into PocketBase.
Benefits
Adding this feature would mean:

Leveling up the security of any app using PocketBase.
Saying goodbye to the hassle of dealing with client-side encryption and decryption.
Making life easier for devs who need to interact with sensitive data.

What's Next?
I'd love to hear your thoughts on this. Maybe there's already a simple way of doing this and this feature makes little sense shrug Got any insights on potential challenges, or suggestions for improvements and alternative approaches? Let's get this conversation started!

jjj

Context
You know when we need to store sensitive stuff like API keys, secret keys, and other hush-hush data in the database? Well, right now, it's up to us to make sure these data are encrypted before storing and decrypted when we need them. This back-and-forth can be a pain and sometimes it feels like a game of hide-and-seek where we're always "it".
Proposal
So, let's spice things up with a new field type called "secret". What's cool about "secret"?
It Does the Heavy Lifting: When you store data in the 'secret' field, PocketBase would automatically encrypt it. And when you need that data back, it'll decrypt it on-the-fly for you. No more manual encrypt-decrypt shenanigans.
Safety First: By handling the encryption right at the database level, we're reducing the chance of data leaks from potential app vulnerabilities or breaches. Think of it as a safe within a safe.
Potential Approach
We could use a tried-and-true encryption algorithm like AES-256 for the 'secret' field. The keys for encryption/decryption could be securely stored and managed using a Key Management Service (KMS) or we could bake them right into PocketBase.
Benefits
Adding this feature would mean:

Leveling up the security of any app using PocketBase.
Saying goodbye to the hassle of dealing with client-side encryption and decryption.
Making life easier for devs who need to interact with sensitive data.

What's Next?
I'd love to hear your thoughts on this. Maybe there's already a simple way of doing this and this feature makes little sense shrug Got any insights

Context
You know when we need to store sensitive stuff like API keys, secret keys, and other hush-hush data in the database? Well, right now, it's up to us to make sure these data are encrypted before storing and decrypted when we need them. This back-and-forth can be a pain and sometimes it feels like a game of hide-and-seek where we're always "it".
Proposal
So, let's spice things up with a new field type called "secret". What's cool about "secret"?
It Does the Heavy Lifting: When you store data in the 'secret' field, PocketBase would automatically encrypt it. And when you need that data back, it'll decrypt it on-the-fly for you. No more manual encrypt-decrypt shenanigans.
Safety First: By handling the encryption right at the database level, we're reducing the chance of data leaks from potential app vulnerabilities or breaches. Think of it as a safe within a safe.
Potential Approach
We could use a tried-and-true encryption algorithm like AES-256 for the 'secret' field. The keys for encryption/decryption could be securely stored and managed using a Key Management Service (KMS) or we could bake them right into PocketBase.
Benefits
Adding this feature would mean:

Leveling up the security of any app using PocketBase.
Saying goodbye to the hassle of dealing with client-side encryption and decryption.
Making life easier for devs who need to interact with sensitive data.

What's Njjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjj
I'd love to hear your thoughts on this. Maybe there's already a simple way of doing this and this feature makes little sense shrug Got any insights on potential challenges, or suggestions for improvements and alternative approaches? Let's get this conversation started!

Something like this was requested before (eg. #1835 (comment)), but for me the main issue with a secret field is that it is not clear how this field will be managed, who will have access to its value and whether the filter/sort operations will work at all.
Could you elaborate on your use case and how do you plan using it?

If the keys are stored in the database then the field is no more secret, because if some one manages to get the database, he will also get the keys in it, and easily decrypt the secret fields

I'm closing this issues as it is lacking details and it is not clear to me how it could be implemented in a general way.
If users need encryption, they will have to attach to app event hooks and could use the built-in helpers security.Encrypt/Decrypt (the same helpers are also available if extended with JS under the $security namespace).

I'm closing this issues as it is lacking details and it is not clear to me how it could be implemented in a general way.
If users need encryption, they will have to attach to app event hooks and could use the built-in helpers security.Encrypt/Decrypt (the same helpers are also available if extended with JS under the $security namespace).

How do we decrypt and verify if we dont know the secret? is there a way to find the pocket base secret keys?


mimic_iii: recognise which folders of the code on the remote server is the latest version

The files size so huge and the code combine with data together. It's hard to find out which one was the latest version in that time. We're going to implement by ourselves.


Thesis Story

Thesis story wrap-up:

should contain a comparison to PENN when with polyphonic pitch audio to show that it does not work at all
show that PENN with split hexaphonic input works quite well
make a common metric for FretNet and PPN and hope for the best
make a strong conclusion about the string confusion problem with PPN, compare the standard metrics with the Multi-Pitch specific string agnostic metrics (close the generalization gap). The monophonic audio example is great for showing the confusion.
rethink the visualizations
** consider making the lines NOT dotted, just make one of the lines thicker, green and yellow color scheme for the logits isn't the best, maybe try a gray scale.

FretNet has multiple evaluator classes like PitchListEvaluator or MultipitchEvaluator. Each class has an unpack() method and evaluate method. The idea now is to derive from PitchListEvaluator class, use the same unpack() function, but a completely different evaluate().

Why does the reference differ so much from estimated in time stamps, but only in the pitch_list?

As for the previous question, it seems that only every 4th timestamp is present in the predicted set. This means that FretNet is only made to handle larger buffers and latency is larger then what was designed in PPN.

Thesis story wrap-up:
* [ ]  should contain a comparison to PENN when with polyphonic pitch audio to show that it does not work at all

How should this be presented?
Plot of an example track with ground truth and predicted pitch, both over a spectrogram - This should be pretty good.
In addition to that a metric for FRMSE and FRPA would be a great addition.

Thesis should be 30-40-50 pages.

including pictures

Introduction:

General motivation
Something about the results
Introduction usually does not get into model details

Section 2:

go over theory: CNN - methods section
usually this is split into the background section and proposed method section
the background section is more detailed then in papers
background: explain the model of the original paper: PENN and FretNet
simply discover the problem with the GuitarSet dataset

Section 3: Proposed method

How is the model adapted to the polyphonic tracking
Explain the RMSE / RPA - accuracy metrics, the string agnostic metrics

Section 4: experiments

dataset explanation / description
tell more about the problem with the GuitarSet datset

Results 5: results and analysis

Conclusion
Fully convolutional models or transformers
New dataset with better ground truth is needed! [https://arxiv.org/abs/2309.09085](new dataset)

For the next meeting: the table of contents + anything extra is nice.

Main results table:
String Agnostic RMSE, String Agnostic RPA
Non-String Agnosic RMSE, Non-String Agnostic RPA,
if possible, copy String-Agnostic Note from FretNet

[ ] methods and background section is START IT!

[ ] explain the math behind everything that you use: Feed Forward NNs, CNNs, CQT. You don't have to talk about anything more, like transformers etc.


support inline visibility modifiers

Support formatting rbs files with inline visibility modifiers per https://github.com/prettier/plugin-ruby/pull/1173#issuecomment-1091684815

Oh gosh sorry I didn't see this because I wasn't watching the repo accidentally! This is great!


Notification tray does not appear when app in foreground?

Expected Behaviour
Notification tray should appear when app is in foreground. Notification tray appears when app is background.But I do get the message in my code, when the app is in foreground. Just that I dont get the tray that appears when app is in background.
push.on('notification', function(data) {
                console.log(data.message);
                console.log(data.title);
            });

Actual Behaviour
The Notification tray should appear even when app is in foreground.
Reproduce Scenario (including but not limited to)
Send push notification when app is closed. Notification tray pops up.
Send push notification when app is in foreground . Notification tray does not appear.
Steps to Reproduce
Platform and Version (eg. Android 5.0 or iOS 9.2.1)
Androd 5.0
(Android) What device vendor (e.g. Samsung, HTC, Sony...)
MotoG
Cordova CLI version and cordova platform version
cordova --version     : 5.3.3
cordova platform version android     : android 4.1.1

Plugin version
cordova plugin version   : 1.6.2

Sample Push Data Payload
Sample Code that illustrates the problem
Logs taken while reproducing problem

@jayeshjain24 that is the correct behaviour. On Android if you want to show the notification even in the foreground use the forceShow option in init:
https://github.com/phonegap/phonegap-plugin-push/blob/browser/docs/API.md#pushnotificationinitoptions

@macdonst I was trying to emulate the notification experience of twitter. When in foreground, twitter seems to be getting the forceShow and on('notification') callback at the same time. Do  I need to click on the notification bar to trigger the event  on('notification')

I tried this (forceShow:"true") for android. it is not working.


on-done URL not called?

Further to #46 I just had a number of successful runs from the GitHub Action but the ON_DONE URL wasn't called for any of them, I can see it in the command being issued but it seems there's no other mention of it in the logs
2023-06-01T21:05:02.4191495Z ##[group]Run python find_posts.py --lock-hours=0 --access-token=*** --server=social.racf.guru --reply-interval-in-hours=0 --home-timeline-length=200 --max-followings=80 --user= --max-followers=0  --http-timeout=5 --max-follow-requests=0 --on-fail="https://uptime.xxx.com/api/push/xxxxx?status=down&msg=Failed%20run" --on-start="" --on-done="https://uptime.xxx.com/api/push/xxxxx?status=up&msg=OK" --max-bookmarks=0 --remember-users-for-hours=168 --from-notifications=1 --backfill-with-context=1  --backfill-mentioned-users=1  --max-favourites=0
2023-06-01T21:05:02.4193319Z python find_posts.py --lock-hours=0 --access-token=*** --server=social.racf.guru --reply-interval-in-hours=0 --home-timeline-length=200 --max-followings=80 --user= --max-followers=0  --http-timeout=5 --max-follow-requests=0 --on-fail="https://uptime.xxx.com/api/push/xxxxx?status=down&msg=Failed%20run" --on-start="" --on-done="https://uptime.xxx.com/api/push/xxxxx?status=up&msg=OK" --max-bookmarks=0 --remember-users-for-hours=168 --from-notifications=1 --backfill-with-context=1  --backfill-mentioned-users=1  --max-favourites=0

Here is the code snippet that's calling that URL:
if(arguments.on_done != None and arguments.on_done != ''):
    try:
        get(f"{arguments.on_done}?rid={runId}")
    except Exception as ex:
        log(f"Error getting callback url: {ex}")

log(f"Processing finished in {datetime.now() - start}.")

As you can see, if you cannot see the 'Error getting callback url' line, then it would've called it.
However, I suspect that the way that it appends the rid parameter with a question mark, means it breaks something: It simply appends it with a question mark, and your resulting URL becomes https://uptime.xxx.com/api/push/xxxxx?status=up&msg=OK?rid={uuid}. As a result the ?rid={uuid} now becomes part of the value of your msg parameter, and presumably your service can't cope with that.
You could try to end your URL with a & parameter like this: https://uptime.xxx.com/api/push/xxxxx?status=up&msg=OK&. Maybe that works?

Turns out it was my issue! My uptime-kuma instance is behind a Cloudflare Access tunnel so it's calling the URL but never getting to the target as it hits the Cloudflare tunnel logon instead. This does lead me on to another question though: is there any way to add a header so that I could use a service token?

That's good to know.
I don't think I'll be adding support for this myself, to be honest. The configuration is already complex enough, and this is quite the edge case.
But you can easily do this in your own fork:
The call is made in line 930:
https://github.com/nanos/FediFetcher/blob/d4dfa1e315d20b3895c21fee7a23a64197bc2973/find_posts.py#L930
You can easily add a dictionary of headers to the requests.get function like this:
get(f"{arguments.on_done}?rid={runId}", headers = {
    "Authorization": "Bearer <JWT>",
})

(or whatever other headers you need)
Obviously repeat the same on line 941 for the fail callback, and on line 757 for the start callback, if desired.


Docs.MS Readme Update.

Docs.MS Readme Update.

Docs Build status updates of commit 35c2df7:
:clock10: Full build: the average full build time is 141 min(s) 43 sec(s), this is based on the last 353 build(s) for this repository.

Docs Build status updates of commit 35c2df7:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-services/template-readme-pre.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/mgmt-loganalytics-readme.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/template-readme-pre.md

Line 13: [Warning-h1-not-first] Markdown content is not allowed before H1.
Line 25: [Warning-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading.
Line 29: [Warning-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading.
Line 33: [Warning-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading.
Line 37: [Warning-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading.
Line 41: [Warning-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading.
Line 45: [Warning-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading.

docs-ref-services/mgmt-loganalytics-readme.md

Line 9: [Warning-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading.
Line 15: [Warning-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


New version: Jackett.Jackett version 0.22.426

Pull request has been created with WinGet Releaser :rocket:
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installation failed with exit code -1978335187
2024-08-09 00:02:49.234 [FAIL] Installer failed security check. Url: https://github.com/Jackett/Jackett/releases/download/v0.22.426/Jackett.Installer.Windows.exe Result: 0x80004005

Automated error analysis suggests -1978335187 may mean Installer failed security check. Another script should retry this every 18 hours.
(Automated response - build 887.)

🔥

/azp run


Remove slots from Biosample if they are not about biosamples, and examples

and autoformatting it

This is an illustration of the state I consider desirable after merging @mslarae13's  PR below. We can merge this in any direction, or just copy this branch's src/data/valid/Database-biosample-exhasutive.yaml into 1557-slot-moving-cont
I can help with merge conflicts, but let's decrease the scope by getting rid of src/data/typeless/*

https://github.com/microbiomedata/berkeley-schema-fy24/pull/42

Migration to delete these fields from all instances of class Biosample.
These fields should have been moved to materialprocessing or processedsample class

I'm supposed to do some post-hoc QC on this PR, right? I can't remember what it it.

@turbomam I think the QC was to evaluate if the slots we moved off Biosample exist on any mongo records. To determine if we need to do a migration.

Removing migration label - none of these slots are used in mongo


Test encoder and decoder

Codecov Report

Merging #33 (c58ef60) into main (10db353) will increase coverage by 14.43%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##             main      #33       +/-   ##
===========================================
+ Coverage   33.34%   47.77%   +14.43%
===========================================
  Files           4        7        +3
  Lines         144      268      +124
===========================================
+ Hits           48      128       +80
- Misses         90      112       +22
- Partials        6       28       +22

Impacted Files
Coverage Δ

pkg/talespire/talespirecoder/decoder.go
63.94% <100.00%> (ø)

pkg/talespire/talespirecoder/encoder.go
59.26% <100.00%> (ø)

pkg/talespire/talespirecoder/axis.go
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


[Release 0.5.0+beta]

An automated PR for next release.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.8%) to 87.511%

Totals

Change from base Build<PHONE_NUMBER>:
-0.8%

Covered Lines:
1983

Relevant Lines:
2266

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.8%) to 87.511%

Totals

Change from base Build<PHONE_NUMBER>:
-0.8%

Covered Lines:
1983

Relevant Lines:
2266

💛  - Coveralls


Use defined constant for consistency

Which issue(s) this PR fixes:
Fixes #
What this PR does / why we need it:
The default value of dir or file permission is defined in fluent/env.rb.
So it should be used everywhere.
I've found this issue when checking #3521.
Docs Changes:
N/A
Release Note:
N/A

It should be, I'll fix it too.

Fixed.

Removed needless constant definition.


Feedback to the starter

Hey @DanielRosenwasser I didn't know where I should post it so I do it here. Please let me know, whether it is not correct.
I saw your talk about Vue + TypeScript on the VueConf 2018. I liked the talk very much, thx for that. Maybe I misunderstand smth but why do you "prefer" the way, using TS + Vue w/o using classes and decorators? I think using the class syntax and decorators are the more common way nowadays when we use TypeScript, isn't it? Using the class syntax is more optional, correct? Are there any pros and cons of using the one or the other way, in your example?
I also have an example, it is not finished yet and w/o using the CLI but my first steps with Vue and TypeScript: https://github.com/Chris2011/Vue-TypeScript-Live-Search-Sample and do a refactoring right now. Remove some old, dumbass code ;).
Cheers
Chris

Closing due to no reaction.


fn calls list ignores path filter

Fn API allows to filter calls by app and route but CLI ignores path.
fn calls list --help
NAME:
   fn calls list - list all calls for specific app / route route is optional

USAGE:
   fn calls list <app> [route]
Deniss-MBP-2:cli denismakogon$ fn calls list application /env
ID: 01BWK116ZNY7WNT00000000000
App: application
Route: /traceback
Created At: 2017-10-16T19:42:23.605+03:00
Started At: 2017-10-16T19:42:23.605+03:00
Completed At: 2017-10-16T19:42:23.606+03:00
Status: success

ID: 01BWK115YHY7WNP00000000000
App: application
Route: /env
Created At: 2017-10-16T19:42:22.545+03:00
Started At: 2017-10-16T19:42:22.728+03:00
Completed At: 2017-10-16T19:42:23.587+03:00
Status: success

dead


fixing nav transition and some typos

Summary
The transition in the navigation did not work clearly, having problems between the contact and the support section
List of changes proposed in this PR (pull-request)

Changed the id of the section in the id and support section and made the id section matched id nav bar

Thank you @Mublin!
The ID tags are linked with CSS - changing the ID messed up the images of the funders.


Completely customizable linenr, maxlinenr, colnr symbols and strings

Additional changes in response to feedback from #2374

Completely customizable linenr, maxlinenr, colnr symbols and strings

That's a very good idea. The way it is, it's a mess to configure. Also, any changes to init.vim would mess up with user config, which is very bad

Also I think line 383 and 384 of the doc text file, among others perhaps after the changes, should be updated.

Thanks, looks good so far.
Can you please check, whether the help file needs an update: here: https://github.com/vim-airline/vim-airline/blob/03ec880101305b41a282ab85f7184f91187392ac/doc/airline.txt#L349-L394
and here: https://github.com/vim-airline/vim-airline/blob/03ec880101305b41a282ab85f7184f91187392ac/doc/airline.txt#L73-L79
thanks.

Updated docs.


An existing connection was forcibly closed by the remote host #6426

Expected behavior the exception not throw
Actual behavior
throws exception at about 45000th connection:
java.io.IOException: Istniejące połączenie zostało gwałtownie zamknięte przez zdalnego hosta
at sun.nio.ch.SocketDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
at sun.nio.ch.IOUtil.read(IOUtil.java:192)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:384)
at io.netty.buffer.PooledUnsafeDirectByteBuf.setBytes(PooledUnsafeDirectByteBuf.java:288)
at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1100)
at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:372)
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:123)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:644)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:579)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:496)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:458)
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:138)
at java.lang.Thread.run(Thread.java:745)
Steps to reproduce
run the attached code
Minimal yet complete reproducer code (or URL to code)
SO site: https://stackoverflow.com/questions/44898590/netty-exception-when-making-multiple-requests-netty-all-4-1-12-final-jar
Netty version netty-all-4.1.12.Final.jar
JVM version (e.g. java -version) jdk1.7.0_80
OS version (e.g. uname -a) Windows 10

Can you please translate the exception to English?
Possibly unrelated but the way you use ThreadLocal in TimeClientHandler doesn't seem right. There may be multiple instances of TimeClientHandler per thread.
Your backlog is 128 ... how do you control back pressure for accepting new sockets? It could be that you are creating connections faster than the server can keep up.

The exception in english is: An existing connection was forcibly closed by the remote host
When i've changed the BACKLOG from 128 to 65536 the exception still occured.
I understand that I could create the connections faster than the server could accept, but the exception is about "existing connection was forcibly closed by the remote host". What this BACKLOG option is for? I found nothing about it in javadoc, What do you mean with "how do you control back pressure for accepting new sockets" are there any patterns for that? Please elaborate or point me to some documentation about it.

Im away from the computer but checkout http://www.linuxjournal.com/files/linuxjournal.com/linuxjournal/articles/023/2333/2333s2.html for more info on the backlog. Make sure there are not OS limits which prevent/limit the value your are setting in the application. Use something like lsof (not sure what this would be on windows) to see socket parameters.

I will close this for now due lack of response. Please re-open if you still think there is anything wrong in netty


Do policy controls work for Teams as well?

This article mentions policy controls for Microsoft Teams apps. The linked articles though (policy controls in Office apps) do not mention Teams (desktop or mobile) as a clients those controls would apply to.
Either the Teams documentation or the Office policy controls documentation is not correct. Clarification would be required on how to set Teams policy controls for diagnostic data.

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

ID: a4898302-208e-0d21-a17f-53e2a9506e21
Version Independent ID: 17d47df2-074b-071a-5179-9ebcc21b709e
Content: Policy control overview for Microsoft Teams - Microsoft Teams
Content Source: Teams/policy-control-overview.md
Service: msteams
GitHub Login: @MicrosoftHeidi
Microsoft Alias: heidip

@andrasg Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.