get the system cast volume to appear

[ ] put change vol +/- in notification?
[ ] look at audio manager : https://stackoverflow.com/questions/40925722/how-to-increase-and-decrease-the-volume-programmatically-in-android
[ ] managing volume: https://developer.android.com/guide/topics/media-apps/volume-and-earphones
[ ] handle audio focus: https://developer.android.com/guide/topics/media-apps/audio-focus
[ ] looks at samples again : it works somehow: https://github.com/googlecast/CastVideos-android
[ ] also look at intent to join: https://developers.google.com/cast/docs/android_sender/intent_to_join

its in flux tm anyways :)

[ ] https://liliputing.com/2021/11/android-12-kills-google-cast-volume-controls-android-12l-will-bring-them-back.html

fixed in #244 PR (#295) - by making custom volume slider


Store for Java?

I was thinking today about Store and it being an Android library. That's cool and all, but upon a superficial search on GitHub there doesn't seem to be a reason to it - its important dependencies are RxJava, Retrofit, Moshi, Gson and Jackson, none of which are Android-specific, and I didn't find any android.* imports. Only thing that would seem to be required as far as I can see is a bit of a refactoring regarding things like removing android manifests, and I'd be happy to do it. What do you think of this? Is it something you'd be open to?

I don't see any reason not to do this -- it would be greater to make Store available for a wider set of uses.
If this is something you're interested in doing, we'd welcome a PR.

Thanks, I'll see what I can get together this weekend.


Install Cobigen plugins into eclipse

We need to integrate cobigen as a plugin for Eclipse. Therefore all we need is a public update site URL and the feature id:
https://github.com/devonfw/devon-ide/blob/8a8c4a661d81e325260fd6c44423bfdb07f64b74/scripts/src/main/resources/scripts/command/eclipse#L106

@maybeec / @jdiazgon any progress, any milestone, any feedback?
Seems I have to release 3.0.0 without CobiGen integration.

BTW: This was accidentally closed due to a bug in githubs autoclose feature.

https://dl.bintray.com/devonfw/cobigen.p2/

There is only one valid plugin available from the update site with ID  com.devonfw.cobigen.eclipse.feature.feature.group. The duplicated feature was already presented earlier. However, all the other plugins (com.devonfw.cobigen.tempeng-freemarker, etc. can not be found).

Advanced health check then gives me this error:

Generation gives me this error:

Technically implemented with PR #148
However, we have to analyse what is wrong with the update site and ensure we have all feature IDs included in eclipse commandlet of this IDE.

@hohwille I did not change anything, but installation was no problem for me at all.
All plugins were available, all plugins could be installed, sample generation works without error.
I took the latest devonfw ide as a reference, uninstalling all cobigen related plugins and reinstalling them from the new update site.
Let's have a chat if you are available.

Hello,
I can confirm the JAXB error, when installing eclipse & Cobigen with devon-ide scripts.
@maybeec : since this looks like a dependency error, you have to start from a fresh eclipse install to see the problem.
Uninstalling from a working install probably keep the dependency installed.
Nicolas

@nricheton I just tried it with a fresh eclipse version downloaded from the eclipse public pages and installed cobigen. No problem. So I am wondering now how to reproduce this issue. What exactly did you do? What did you install, what didn't you install?

I used devon-ide scripts 3.0.0 beta 11 (latest) to do the full environment setup.
=> Install succeed but I get the jab error when I do the advanced health check.

ok, I drilled it down. It seems to be an issue with jdk 11. I created a new issue in the cobigen repository regarding that: devonfw/tools-cobigen#970

@nricheton and @maybeec 👍 for your analysis and taking this further.
So IMHO we need to get CobiGen fixed, create a new release, push this out to update site and then retest.
What about the plugins meanwhile? I removed all the plugin IDs except the core one in devon-ide as otherwise I was getting more errors. Is that correct and CobiGen is more monolytic now or is there still some other issue to solve?
https://github.com/devonfw/devon-ide/blob/3b098ce7188a137e7a1bd8a45455f4f10280c2f5/scripts/src/main/resources/scripts/command/eclipse#L117

So IMHO we need to get CobiGen fixed, create a new release, push this out to update site and then retest.

I will keep you posted.

What about the plugins meanwhile? I removed all the plugin IDs except the core one in devon-ide as otherwise I was getting more errors. Is that correct and CobiGen is more monolytic now or is there still some other issue to solve?

I will check about the issue and if there is some. But IMHO we should install all plug-ins by default. CobiGen is not yet able to lazily install plug-ins and as we actually don't know in which context the user is trying to make use of CobiGen, we have to be prepared as otherwise everyone will simply quit saying "it does not work".

My intention was always to install CobiGen completely with all plugins, so I fully agree @maybeec.
However, the update site I got was not able to resolve these plugin IDs that I got from an earlier manual installation and prepared in the commandlet.
Maybe also the IDs have changed. I will then already read them locally and try again...

OK, tried it and got the same error again:
devon eclipse add-plugin cobigen
Installing eclipse plugin com.devonfw.cobigen.eclipse.feature from https://dl.bintray.com/devonfw/cobigen.p2/
org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized.  Will retry after the state location is initialized.
log4j:WARN No appenders could be found for logger (org.apache.http.client.protocol.RequestAddCookies).
log4j:WARN Please initialize the log4j system properly.
Installation failed.
The installable unit com.devonfw.cobigen.tsplugin.com.devonfw.cobigen.tempeng-velocity has not been found.
There were errors. See log file: /projects/software/default/eclipse/2019-06/Eclipse.app/Contents/Eclipse/configuration/1566325705342.log

******** ATTENTION ********
WARNING: Installation of plugin com.devonfw.cobigen.eclipse.feature failed. Please try to install manually.

➜  devon cat /projects/software/default/eclipse/2019-06/Eclipse.app/Contents/Eclipse/configuration/1566325705342.log
!SESSION 2019-08-20 20:28:25.242 -----------------------------------------------
eclipse.buildId=4.12.0.I20190605-1800
java.version=11.0.4
java.vendor=AdoptOpenJDK
BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_DE
Framework arguments:  -product org.eclipse.epp.package.java.product -application org.eclipse.equinox.p2.director -repository https://dl.bintray.com/devonfw/cobigen.p2/ -installIU com.devonfw.cobigen.eclipse.feature.feature.group,com.devonfw.cobigen.tempeng-freemarker,com.devonfw.cobigen.htmlplugin,com.devonfw.cobigen.javaplugin,com.devonfw.cobigen.jsonplugin,com.devonfw.cobigen.openapiplugin,com.devonfw.cobigen.propertyplugin,com.devonfw.cobigen.textmerger,com.devonfw.cobigen.tsplugin.com.devonfw.cobigen.tempeng-velocity,com.devonfw.cobigen.xmlplugin
Command-line arguments:  -os macosx -ws cocoa -arch x86_64 -product org.eclipse.epp.package.java.product -application org.eclipse.equinox.p2.director -repository https://dl.bintray.com/devonfw/cobigen.p2/ -installIU com.devonfw.cobigen.eclipse.feature.feature.group,com.devonfw.cobigen.tempeng-freemarker,com.devonfw.cobigen.htmlplugin,com.devonfw.cobigen.javaplugin,com.devonfw.cobigen.jsonplugin,com.devonfw.cobigen.openapiplugin,com.devonfw.cobigen.propertyplugin,com.devonfw.cobigen.textmerger,com.devonfw.cobigen.tsplugin.com.devonfw.cobigen.tempeng-velocity,com.devonfw.cobigen.xmlplugin

!ENTRY org.eclipse.equinox.p2.director.app 4 0 2019-08-20 20:28:29.045
!MESSAGE The installable unit com.devonfw.cobigen.tsplugin.com.devonfw.cobigen.tempeng-velocity has not been found.

OK. Obviously an invalid ID. It may have changed but it is more likely I did some copy&past bug as this does not make any sense:
com.devonfw.cobigen.tsplugin.com.devonfw.cobigen.tempeng-velocity

Do you know the correct ID for temeng-velocity before I find it?

Is it this one?
https://github.com/devonfw/tools-cobigen/blob/master/cobigen/cobigen-templateengines/cobigen-tempeng-velocity/src/main/resources/META-INF/services/com.devonfw.cobigen.api.extension.TextTemplateEngine
com.devonfw.cobigen.tempeng.velocity.VelocityTemplateEngine

It was just a . that needs to be a , in tsplugin.com.

Merged PR #205
AFAIK all left to be done is creating a new CobiGen release working with Java11 and updating the update site on bintray.
So technically all is already done in this code-base if everything works as planned.

Requires this issue to be fixed:
https://github.com/devonfw/tools-cobigen/issues/970
and a release to be pushed out.
Do we have a critical path here?

Do we have a critical path here?

I'm currently working on it. The CobiGen CLI is > JDK9 compatible, but now I'm fixing CobiGen for Eclipse with > JDK9

I have already tested the lastest state and it works like a charm. Great job CobiGen team 👍

@hohwille, @maybeec, @jdiazgon: I just ran into apparently the same problem, although I am using devonfw-ide release 3.2.4-SNAPSHOT as of December, 21st.
I am also using Java 11:
openjdk version "11.0.5" 2019-10-15
OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.5+10)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.5+10, mixed mode)
The problem occured first during the setup of the ide. After firs setup, the eclipse installation is not attempted a second time ("already installed"), so I tried "devon eclipse add-plugin".
`C:\projects\cashplanner3>devon eclipse add-plugin cobigen
Installing eclipse plugin com.devonfw.cobigen.eclipse.feature from https://dl.bintray.com/devonfw/cobigen.p2/
******** ATTENTION ********
WARNING: Installation of plugin com.devonfw.cobigen.eclipse.feature failed. Please try to install manually.`
Threre is no further error message on the command line
Is there anything like an error log, so that I can try to find out more?

OK, I just found a log file:
!SESSION` 2019-12-31 17:24:36.790 -----------------------------------------------
eclipse.buildId=4.13.0.I20190916-1045
java.version=11.0.5
java.vendor=AdoptOpenJDK
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments:  -product org.eclipse.epp.package.java.product -application org.eclipse.equinox.p2.director -repository https://dl.bintray.com/devonfw/cobigen.p2/ -installIU com.devonfw.cobigen.eclipse.feature.feature.group,com.devonfw.cobigen.tempeng-freemarker,com.devonfw.cobigen.htmlplugin,com.devonfw.cobigen.javaplugin,com.devonfw.cobigen.jsonplugin,com.devonfw.cobigen.openapiplugin,com.devonfw.cobigen.propertyplugin,com.devonfw.cobigen.textmerger,com.devonfw.cobigen.tsplugin,com.devonfw.cobigen.tempeng-velocity,com.devonfw.cobigen.xmlplugin
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.java.product -application org.eclipse.equinox.p2.director -repository https://dl.bintray.com/devonfw/cobigen.p2/ -installIU com.devonfw.cobigen.eclipse.feature.feature.group,com.devonfw.cobigen.tempeng-freemarker,com.devonfw.cobigen.htmlplugin,com.devonfw.cobigen.javaplugin,com.devonfw.cobigen.jsonplugin,com.devonfw.cobigen.openapiplugin,com.devonfw.cobigen.propertyplugin,com.devonfw.cobigen.textmerger,com.devonfw.cobigen.tsplugin,com.devonfw.cobigen.tempeng-velocity,com.devonfw.cobigen.xmlplugin

!ENTRY org.eclipse.equinox.p2.artifact.repository 4 1000 2019-12-31 17:24:41.949
!MESSAGE No repository found at https://dl.bintray.com/devonfw/cobigen.p2/.

!ENTRY org.eclipse.equinox.p2.metadata.repository 4 1000 2019-12-31 17:24:42.800
!MESSAGE No repository found at https://dl.bintray.com/devonfw/cobigen.p2/.

!ENTRY org.eclipse.equinox.p2.core 4 0 2019-12-31 17:24:42.806
!MESSAGE Unable to load repositories.

Where are the plugins?

Hmmmm... now I am stuck with the next problem: The guide says: "Checkout (clone) your project’s templates folder or use the current templates released with
CobiGen (https://github.com/devonfw/tools-cobigen/tree/master/cobigen-templates) and [...]" However, I cannot git clone https://github.com/devonfw/tools-cobigen/tree/master/cobigen-templates ("fatal: repository 'https://github.com/devonfw/tools-cobigen/tree/master/cobigen-templates/' not found") I can also not clone the complete repository due to excessively long paths and file names that are not supported unter Windows..
What can I do?

A hint on your last point about the issues with long paths:
git is able to use the newer Windows API - without that limitation - when needed, since longer. But you need to activate this with help of the following config setting
git config --system core.longpaths true

Besides that you could also download each github repository as ZIP archive (check the web gui on main directory of repo for that option) and such extract only those dirs/files to filesystem, you need.

Also it might be good to open this as an own issue, since this issue was (mostly) about the former JDK 11 incompatibility.
The current issue seems just to be some coordination mix-up: the devonfw-ide has already started referig the bintray repository for cobigen-eclipse-plugin installation - but this repo does not seem to have any released files yet, (see https://bintray.com/devonfw/cobigen.p2 )

@Jan-PeterRichterCG , @markusschuh , as of discussions with legal regarding public distribution of packaged solutions like CobiGen eclipse installation bundles, we needed to take them offline.
Now we are currently in the process to redistribute them by assuring correct licensing texts shipped with the bundles.


fix generate_projects.sh fails in M1 Mac

use buildozer-darwin-arm64 package with ARM Mac
add if __name__ == "__main__": test which is required on Mac after Python 3.8 because spawn is used in multiprocessing

Were you waiting on me, @sampajano? If so, LGTM.


feat: Add Helm Chart folder

Added folder charts with a Helm Chart to release docat in Kubernetes.
This first iteration just contain the default helm template ( https://helm.sh/docs/helm/helm_create/ ) with the docker image changed to docat, also contains a statefulset requesting 1 GB of storage, in the next iteration we can improve the chart files

I do like the idea of having a helm chart deployment as we anyway mainly support the docker workflow.
I will look at this next week in more detail, one thin I would like to change is remove a lot of the default helm boilerplate as IMO it is mostly not needed and can be simplified, it would also be nice to add a CI job to test the deployment.

can we have that as an extra repo eg something like docat-helm ?

closed as non active
feel free to just reopen if you work on it again

Hello, I can contribute to that docat-helm repository, can you create it please? Thanks :)

Sorry i completely forgot yesterday, you should now have a invite


apiVersion still v1 in Helm v3

The apiVersion in charts for Helm v3 is v1. Yet, there have been some chart changes including:

dependencies moved to the Chart.yaml file
requirements.lock is now Chart.lock
annotations added to the Chart.yaml file

I understand that Helm v3 works for both the older and newer setups. But, external tools that work with charts don't know about the changes.
Should we move the apiVersion to v2?

slating to get this done before we release the first beta.

@mattfarina @bacongobbler I can work on this if it is open to be done?

Sure!

Here are the tasks required:

[ ] Update scaffold chart to be "v2"
[ ] Update linting to handle new dependencies and annotations
[ ] Update documentation to specify "v2" as default version and "v1" for specific scenarios

Additional TODO:

[ ] Helm 2 should fail to load a chart with an apiVersion field of anything other than v1 or the empty string (Helm 2 doesn't validate the apiVersion field, so those charts are assumed to be compiled against apiVersion v1

Thanks @bacongobbler for the heads up in https://github.com/helm/helm/issues/5907#issuecomment-516963275. I have added it to the task list in https://github.com/helm/helm/issues/5907#issuecomment-516063552.

all of the PRs for the tasks have been merged so this can now be closed :)

Thanks @bacongobbler for the doc PR.


Updating CNI image

0.6.0 image is failing for reason
starting IPAM daemon in background ... ok.
checking for IPAM connectivity ...  failed.
timed out waiting for IPAM daemon to start.

0.6.3 has a fix for this error
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Closing this PR. As we dont need this change anymore


How can I serve responses larger than 32MB with Cloud Run?

Information from https://twitter.com/steren/status/1334281184965140483
See also https://github.com/simonw/datasette/issues/749

do you mind:

wrapping lines to 80 char width
running the command at the top to update table of contents

Thank you. 🙏


Cleanup pumpkin-config

Description
Most changes are because serde_inline_default is no longer needed, see here

Testing
ran diff on booth configs to see if anything changed.

Checklist
Things need to be done before this Pull Request can be merged.

[x] Code is well-formatted and adheres to project style guidelines: cargo fmt
[x] Code does not produce any clippy warnings cargo clippy

The only reason we use serde_inline_default is to have default values for config fields we can't parse. I tested your changes and removed a random config value. It gave me an error Couldn't parse config at "configuration.toml". Reason: missing field hardcore. This is is proberbly caused by an Config update, Just delete the old Config and start Pumpkin again

The only reason we use serde_inline_default is to have default values for config fields we can't parse. I tested your changes and removed a random config value. It gave me an error Couldn't parse config at "configuration.toml". Reason: missing field hardcore. This is is proberbly caused by an Config update, Just delete the old Config and start Pumpkin again

Now it should work

Just tested again. Works fine now and looks much better.
Thanks @Commandcracker :D


Derive PartialEq, Eq, PartialOrd, Ord, and Hash

These traits permit using a Transcript as a key in a HashMap or BTreeMap, which permits handy optimizations, such as in conjunction with pairings.  These do leak state to the caller of course, but if that's a concern then they could operate on only the first 32-64 bytes of the state.. or Hash could include its own siphasher invocation, and the others could be ignored.  It's a nice feature of strobe that the state contains almost only the 200 byte keccak state, so siphash can usually process it faster than ant relevant from which the Transcript was created.

Hi, I'm not really sure of a good usecase for using transcripts as keys, or checking equality of transcripts (which seems like an XY problem), and I'd prefer to keep the API as minimal as possible, so I'm going to close this PR for now.

Anytime I want this myself I already have a [u8; 32] so no concrete use case from me.  No worries.  :)


ReadMe UPM Links Broken

Neither of these work in Unity 2021 LTS

Unity 2021.3.15

If I just use this part it does work.
https://github.com/James-Frowen/Mirage.Profiler.git?path=/Assets/Mirage.Profiler#v1.1.0-mirror.10

copy the whole thing to clipboard and paste it into Package Manager "Add package from git URL" produces those errors.

That seems to work fine for me, I can't reproduce the error.

URL alone works, whole thing as below, throws errors (in case I wasn't clear above)
"com.james-frowen.mirage-profiler": "https://github.com/James-Frowen/Mirage.Profiler.git?path=/Assets/Mirage.Profiler#v1.1.0-mirror.10",

I dont think this is a problem with the readme, the "Add package from git URL" implies that it should only use url part not the full string

I don't think this is a problem with the readme, the "Add package from git URL" implies that it should only use URL part not the full string

Except that when the mouse goes over one of those, there's a handy Copy UI button that appears, that invites you to click it to copy the whole string, which you can't actually use.  That whole string would only be for people wanting to manually hack their manifest files, not paste what got copied into Unity's URL field in the editor's UI.


QG 4 checks (Release 12.23)

QG checks
Please keep this issue open until QG is concluded and will be managed by the Issue Creator!
We will inform you about finding and proposals in separated issues, this issue here is for the Overview of the Checks!
Please keep this issue open until QG is concluded!
Product Owner:
Dev SPOC:
Helm Chart Version:
App Version:
Check of Tractus-X Release Guidelines

Currently implemented automatic checks can be found under your product on our Release Guidelines Checks Board
This QG Check is depending on the mandatory information from our current Release Guidelines

TRG 1 Documentation

[ ] TRG 1.01 appropriate README.md
[ ] TRG 1.02 appropriate install instructions either INSTALL.md or in README.md
[ ] TRG 1.03 appropriate CHANGELOG.md

back on top
TRG 2 Git

[ ] TRG 2.01 default branch is named main
[ ] TRG 2.03 repository structure
[ ] TRG 2.04 leading product repository
[ ] TRG 2.05 .tractusx metafile in a proper format

back on top
TRG 3 Kubernetes

[ ] TRG 3.02 persistent volume and persistent volume claim is used when needed

back on top
TRG 4 Container

[ ] TRG 4.01 semantic versioning and tagging
[ ] TRG 4.02 top level README.md file or separate README.md file for DockerHub, that contains information about the used base image
[ ] TRG 4.03 image has USER command and Non Root Container
[ ] TRG 4.05 released image must be placed in DockerHub, remove GHCR references
[ ] TRG 4.06 notice file for DockerHub has all necessary information

back on top
TRG 5 Helm

[ ] TRG 5.01 Helm chart must be released
[ ] TRG 5.02 Helm chart location in /charts directory and correct structure
[ ] TRG 5.04 CPU / MEM resource requests and limits and are properly set
[ ] TRG 5.06 Application must be configurable through the Helm chart
[ ] TRG 5.07 Dependencies are present and properly configured in the Chart.yaml
[ ] TRG 5.08 Product has a single deployable helm chart that contains all components
[ ] TRG 5.09 Helm Test running properly
[ ] TRG 5.10 Products need to support 3 versions at a time
[ ] TRG 5.11 Upgradeability

back on top
TRG 6 Released Helm Chart

[ ] TRG 6.01 Released Helm Chart

back on top
TRG 7 Open Source Governance

[ ] TRG 7.01 Legal Documentation
[ ] TRG 7.02 License and copyright header
[ ] TRG 7.03 IP checks for project content
[ ] TRG 7.04 IP checks for 3rd party content
[ ] TRG 7.05 Legal information for distributions
[ ] TRG 7.06 Legal information for end user content
[ ] TRG 7.07 Legal notice for documentation

back on top
Hints
Information Sharing

Hi @bs-sili , @tunacicek this is a QG 4 issue created for source code.
Can you please confirm below:

Product Owner: Thomas Henn
Dev SPOC: Tunahan Cicek / Sahil Aggarwal (@agg3fe)

and provide following versions for which the check needs to be performed:

Helm Chart Version:
App Version:

Thank you in advance.

Hey @tunacicek, @agg3fe I'm a bit not clear on the CHANGELOG.md which is detailing latest version 2.6.0 however I can't actually find it released, can you help me with that?

Hey @tunacicek, @agg3fe I'm a bit not clear on the CHANGELOG.md which is detailing latest version 2.6.0 however I can't actually find it released, can you help me with that?

@tomaszbarwicki, yes actually 2.6.0 is not required in CHANGELOG.md, there was a small mistake from our side. I will clean the changelog.md now.

Hey @tunacicek, @agg3fe I'm a bit not clear on the CHANGELOG.md which is detailing latest version 2.6.0 however I can't actually find it released, can you help me with that?

@tomaszbarwicki, yes actually 2.6.0 is not required in CHANGELOG.md, there was a small mistake from our side. I will clean the changelog.md now.

We have cleaned the changelog.md file.

Hey @tunacicek, @agg3fe I'm a bit not clear on the CHANGELOG.md which is detailing latest version 2.6.0 however I can't actually find it released, can you help me with that?

@tomaszbarwicki, yes actually 2.6.0 is not required in CHANGELOG.md, there was a small mistake from our side. I will clean the changelog.md now.

We have cleaned the changelog.md file.

Thanks @agg3fe, are you able to provide following info: https://github.com/eclipse-tractusx/sldt-discovery-finder/issues/64#issuecomment-1818514358

Hi @tomaszbarwicki,
Product Owner: Thomas Henn
Dev SPOC: Tunahan Cicek / Sahil Aggarwal (@agg3fe) / Simone Lindner (@bs-sili )
Helm Chart Version: 0.1.12
App Version: 0.2.5

Hi @tomaszbarwicki,
thank you for creating already a PR for the missing copyright header in tractusx file. Is this QG blocking or can we update this file after QG?

Hi @bs-sili,
It's my recommendation to fully comply with the TRGs, wouldn't call it a blocker though. However the other PR I raised for helm workflow would be necessary for me to test installation on different k8s versions and upgradeability of the helm chart.

Thank you for cooperation, QG4 checks approved.


METRON-108 Created fast packet capture process

Changes

Created top-level metron-sensors directory to contain Metron probes and sensors.
Created fast packet capture process leveraging DPDK at metron-sensors/packet-capture.
Moved Bro plugin to metron-sensors/bro-plugin-kafka.
Created Ansible role to manage deployment of packet capture at deployment/roles/packet-capture.
Created separate role for librdkafka installation since this is required by both Bro and Packet Capture.
Created deployment/vagrant/packet-capture for launching packet capture process.  CentOS 7 is required which prevents this from being used in deployment/vagrant/singlenode-vagrant.

It's unfortunate that we are unable to get this to work with singlenode vagrant.  In lieu of that, can we have at least a utility and some sample data to publish to kafka so that we can test downstream processes in singlenode vagrant?
Also, as we talked about earlier, please add a utility class and unit test showing the appropriate way to add headers to the raw data.

Yes, I am going to work on that next.  I wanted to get this chunk of code in first.

Got it, makes sense.  This looks great, btw.

So, since this touches the ansible stuff, could we please get someone else to verify that singlenode vagrant isn't broken in a too-subtle-for-me-to-detect way.  If that's ok and there's a followup PR with the testing utility, then I'm +1.

Updated description with the validation that I completed.

Last time I checked, there was a pretty large bit of work to get EC2 working with Centos7 as well. Has that changed or is the plan to defer packet-capture until we have Centos7 deployment working?

I think that's a bridge to cross later once we refine specific deployment topologies.  The packet capture process differs from the rest of the sensors that we have to date and requires a bit of special treatment.

This packet capture process is overkill and too cumbersome in demo/test environments.  It is really only useful for high-throughput production environments.
Using kernel bypass technology like this means that the packet capture process does not share well with others.  No other sensors leveraging libpcap drivers can share the same network interface.
Packet capture would most always run on a node isolated from the rest of your cluster.  The cluster could be running CentOS 6 while this runs on CentOS 7.
This process has to be run close to your data.  I don't foresee this running "in the cloud." It could potentially be used in a hybrid cloud deployment sending data from a secured network to the cloud.

+1 from me


feature: support Russian language 'ru-RU'

Is your feature request related to a problem? Please describe.
Currently Schedule-X doesn't support Russian language.
Describe the solution you'd like
I want to add Russian translation into Schedule-X (packages/translations/src/locales/ru-RU)
Additional context
I have cloned project and use another language locale for a example. It's clear.

Thanks! For documentation purposes, here my answer for the same question on Discord:
There's a quick guide on how to contribute here: https://github.com/schedule-x/schedule-x/blob/main/.github/contributing.md#developing
If the step with husky does not work, try either to "npm i -g husky" first, or just skip the husky install step completely.

Released as version 1.9.0 🎉


Add Getiing Started section to README

README Update
please add a getting started section to the README so folks know how to start with this project

Added Getting started section to README file


CC installing old version of p2p

logs.txt
I installed p2p from CC and it installed very old  version of build.
It happened on windows and on ubuntu.

it's p2p buiders does not update packages in master cdn


Propagate general status for decorators

Introduce status propagation for decorator nodes.
Extra steps are needed for Retry, Repeat and KeepRunningUntilFailure nodes.
ConsumeQueue is only partially tested, because it is not part of the default behavior_tree include

Closing pull request in favor of #2


[Question] How do you add an application's API to Intellisense?

I am using Lua for the purpose of writing scripts for the application Blackmagic Fusion.  My wish would be to have API auto-completion/intellisense based on that application API.  I'm willing to put in the work to put the API into some format that VS Code can interpret, as I have done for other projects (Typescript).  But I am unsure how to go about this.  Thank you for any help!
Here's an example of the type of script I'm talking about:
https://github.com/movalex/fusion_scripts/blob/master/Scripts/Tool/Macro2Group.lua

You may use EmmyLua for now.

Is there a recommended method of "including" such files in your VS Code workspace?  Or must you just have your "defintion file" somewhere in your workspace?

What i have done is make a folder called api/ and then another folder named after what its defining
and then put lua files for there definitions
I created 2 python scripts to automate converting a webpage into bare lua files with Emmy's format for auto-completions ect
https://github.com/Dude112113/RobloxApi-Definitions-Emmy

Yes, I've done much the same myself.  Havent put it on github yet but intend to.
Have you somehow managed to get function descriptions to show up?  I use a format like this:
--- Opens a filename for seeking and playback
function preview:Open()end

But in VSCode I don't see that comment "Opens a filename..." etc when i begin to type "Open", as I would in other languages.

Very good point, im currently using a different extension for the time being until this one has better support for EmmyLua...
i will create a suggestion for it.

I think this may meet your needs.

Wow, sounds great!  Also, the English looks good to me...