LabelAnnotator doesn't recognize labeling function schema?

  File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/home/debnil/projects/recon/labeling/run_generative_labeling.py", line 27, in <module>
    run_labeling(session, args.feature)
  File "/home/debnil/projects/recon/labeling/run_generative_labeling.py", line 18, in run_labeling
    L_train = labeler.apply(split=0, parallelism=1)
  File "/home/debnil/projects/snorkel/snorkel/annotations.py", line 197, in apply
    count=cids_count, **kwargs)
  File "/home/debnil/projects/snorkel/snorkel/udf.py", line 48, in apply
    self.apply_st(xs, progress_bar, clear=clear, count=count, **kwargs)
  File "/home/debnil/projects/snorkel/snorkel/udf.py", line 71, in apply_st
    for y in udf.apply(x, **kwargs):
  File "/home/debnil/projects/snorkel/snorkel/annotations.py", line 267, in apply
    c = self.session.query(Candidate).filter(Candidate.id == cid).one()
  File "/home/debnil/projects/recon/.env/local/lib/python2.7/site-packages/sqlalchemy/orm/query.py", line 2894, in one
    ret = self.one_or_none()
  File "/home/debnil/projects/recon/.env/local/lib/python2.7/site-packages/sqlalchemy/orm/query.py", line 2864, in one_or_none
    ret = list(self)
  File "/home/debnil/projects/recon/.env/local/lib/python2.7/site-packages/sqlalchemy/orm/loading.py", line 98, in instances
    util.raise_from_cause(err)
  File "/home/debnil/projects/recon/.env/local/lib/python2.7/site-packages/sqlalchemy/util/compat.py", line 203, in raise_from_cause
    reraise(type(exception), exception, tb=exc_tb, cause=cause)
  File "/home/debnil/projects/recon/.env/local/lib/python2.7/site-packages/sqlalchemy/orm/loading.py", line 79, in instances
    rows = [proc(row) for row in fetch]
  File "/home/debnil/projects/recon/.env/local/lib/python2.7/site-packages/sqlalchemy/orm/loading.py", line 741, in polymorphic_instance
    _instance = polymorphic_instances[discriminator]
  File "/home/debnil/projects/recon/.env/local/lib/python2.7/site-packages/sqlalchemy/util/_collections.py", line 729, in __missing__
    self[key] = val = self.creator(key)
  File "/home/debnil/projects/recon/.env/local/lib/python2.7/site-packages/sqlalchemy/orm/loading.py", line 725, in configure_subclass_mapper
    discriminator)
AssertionError: No such polymorphic_identity u'gang' is defined```

Getting from following code --
def run_labeling(session, feature):
    lfs_arr = lfs.get_lfs_by_feature(feature)
    lfs_arr = [lf[1] for lf in lfs_arr]
    # Above makes list of labeling function pointers
    labeler = LabelAnnotator(lfs=lfs_arr)
    L_train = labeler.apply(split=0, parallelism=1)
    L_dev = labeler.apply(split=1, parallelism=1)

Pretty simple call to LabelAnnotator following tutorial, but I don't understand the schema issue here and am not sure what I'm doing wrong. Thanks!

@debnil I have the same problem, could you resolve your issue?


Activeadmin closes  #22

Coverage remained the same at 100.0% when pulling 25429b46189b64e11b71f437ff60df2e8c77f429 on activeadmin-#22 into fa64e82924331ba639a923bd9cde8454f5bca8fa on develop.


[TFLite micro] Update EvalQuantizedInt8() method of Fully Connected kernel (CMSIS-NN)

Add some checks on the dimensions of the input tensor.
Fix initialization of input_dims: the fully connected op takes in input a tensor having two dimensions and returns in output a tensor with two dimensions. However, when initializing the input_dims variable, the code tries to access to higher dimensions (that is input_shape.Dims(2) and input_shape.Dims(3) causing the assertion TFLITE_DCHECK_LT(i, size_) in the Dims() method to be false.

Tested on a STM32F4 board using the hello_world example (but it could be tested on any model that contains a FC layer).
Best,
Biagio.

@biagiom  Can you please check @felix-johnny's comments and keep us posted ? Thanks!

@biagiom  Can you please resolve conflicts? Thanks!


Allow for hidden unit tests

Hidden unit tests are stored in tests/hidden.c. The sections of code in
tests/testsuite.c that require functions from hidden.c are removed when
preparing for distribution using the existing
BEGIN_SOLUTION/END_SOLUTION removal logic.
dist/rebuild-p*.sh need to be modified to not copy tests/testsuite.c
directly into the distribution directory.

Thanks! This partially addresses #3.


Minor: change wording for PMC membership notice

Which issue does this PR close?
N/A
Rationale for this change
Per https://apache.org/foundation/glossary.html#PMC
Make it clear this the person will not become the PMC, rather they will join the PMC
What changes are included in this PR?
Adjust email template wording
Are these changes tested?
N/A

Are there any user-facing changes?

Thanks @Dandandan


dockbarx: 1.0-beta -> 1.0-beta2, xfce4-dockbarx-plugin: 0.6 -> 0.7.2

Description of changes
$ ./result/bin/dockx
Traceback (most recent call last):
  File "/nix/store/r6wvaqc5ljwp0rz6zrrqpyhdbnsh13li-dockbarx-1.0-beta-d98020ec49f3e3a5692ab2adbb145bbe5a1e80fe/bin/.dockx-wrapped", line 31, in <module>
    gi.require_version("Gtk", "3.0")
  File "/nix/store/4qd2y985alz4hig3src0lfipdpjd48r6-python3.10-pygobject-3.44.1/lib/python3.10/site-packages/gi/__init__.py", line 126, in require_version
    raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Gtk not available

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Give me a sec, let me try to bump it also

Okay, the panel plugin seems to work now.
Screenshot


bug: JDBC connector error may lead to recovery of risingwave.

Describe the bug
According to report from user, when jdbc connector has been killed(maybe due to inactivity), risingwave may recover.
Error message/log
No response
To Reproduce
No response
Expected behavior
Risingwave should handle connection error and retry.
How did you deploy RisingWave?
No response
The version of RisingWave
No response
Additional context
No response

Will support connection pool to keep the connection alive https://github.com/risingwavelabs/risingwave/issues/13170. btw decouple JDBC sink with log store is also on going.

We agree to recreate a new connection when the connection is broken instead employ a connection pool.


ffprobe: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory

Morning folks, we've discovered a snag when clean deploying MRE into an AWS environment. Please find a description and the investigation below as well as a possible fix PR attached
Linked PR

#14

Steps to reproduce

Remove any locally stored amazonlinux docker images form your deployment instance. This is important as a clean instance will pull amazonlinux:latest a.k.a amazonlinux:2023
Clean deploy aws-media-replay-engine using the steps outlined here
Setup an S3 bucket using the steps outlined here
Setup an event to take in the chunks from the bucket

Expected behaviour
AWS Media replay engine is able to process the chunks on a clean install
Actual behaviour
The following error occurs
INIT_START Runtime Version: python:3.8.v17	Runtime Version ARN: arn:aws:lambda:us-east-1::runtime:48ae60ef4cd46a5f33291797e798b3aaefe09e5000e8f58c605db8540c47dd8d
START RequestId: {REDACTED} Version: $LATEST
Lambda got the following event:
{'Event': {'Name': '{REDACTED}', 'Program': '{REDACTED}', 'Start': '2023-05-08T09:09:13Z', 'GenerateOrigClips': True, 'GenerateOptoClips': True}, 'Input': {'ExecutionId': '{REDACTED}', 'Media': {'S3Bucket': '{REDACTED}', 'S3Key': '{REDACTED}.ts'}}}
Probing the HLS video segment '{REDACTED}/{REDACTED}/{REDACTED}-1min/{REDACTED}.ts' from S3 bucket '{REDACTED}'
POST /workflow/execution
Message from Cleanup Decorator: Removed 0 files/sub-directories in '/tmp/'
GET /media/{REDACTED}/{REDACTED}.ts
ffprobe: Encountered an error while probing the HLS segment file '{REDACTED}/{REDACTED}/{REDACTED}/{REDACTED}-Profile-1min/{REDACTED}.ts': b'ffprobe: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory\n'
[ERROR] MREExecutionError: b'ffprobe: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory\n'
Traceback (most recent call last):
  File "/var/task/lambda_function.py", line 279, in lambda_handler
    raise MREExecutionError(e.stderr)
END RequestId: {REDACTED}
REPORT RequestId: {REDACTED}	Duration: 3018.93 ms	Billed Duration: 3019 ms	Memory Size: 1024 MB	Max Memory Used: 86 MB	Init Duration: 557.22 ms

## Investigation
Upon running this snippet in an AWS Lambda Python 3.8 environment to match the MRE environment
import json
import glob

def lambda_handler(event, context):
    for item in glob.glob("/lib64/*"):
        print(item)
    return {
        'statusCode': 200,
        'body': json.dumps('Hello from Lambda!')
    }

We can observe the following output
START RequestId: 51113ff1-f1ae-4e32-85f0-79c60e4681d2 Version: $LATEST
// ... removed for space
/lib64/libssl.so.1.0.2k
// ... removed for space
/lib64/libssl.so.10
// ... removed for space
END RequestId: 51113ff1-f1ae-4e32-85f0-79c60e4681d2
REPORT RequestId: 51113ff1-f1ae-4e32-85f0-79c60e4681d2	Duration: 2.79 ms	Billed Duration: 3 ms	Memory Size: 128 MB	Max Memory Used: 39 MB	Init Duration: 122.29 ms

This indicates that from a quick glance that the shared object libssl.so.3 is not available in the Lambda execution context. On observing the built ffprobe asset we can observe that it was linked against libssl.so.3
user:~/environment/aws-media-replay-engine/source/layers/ffprobe/bin (main) $ LD_LIBRARY_PATH=/home/ubuntu/environment/aws-media-replay-engine/source/layers/ffprobe/lib ldd ./ffprobe
./ffprobe: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by ./ffprobe)
./ffprobe: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./ffprobe)
./ffprobe: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /home/ubuntu/environment/aws-media-replay-engine/source/layers/ffprobe/lib/libavdevice.so.58)
./ffprobe: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /home/ubuntu/environment/aws-media-replay-engine/source/layers/ffprobe/lib/libavfilter.so.7)
./ffprobe: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/ubuntu/environment/aws-media-replay-engine/source/layers/ffprobe/lib/libavfilter.so.7)
./ffprobe: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /home/ubuntu/environment/aws-media-replay-engine/source/layers/ffprobe/lib/libavformat.so.58)
./ffprobe: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /home/ubuntu/environment/aws-media-replay-engine/source/layers/ffprobe/lib/libavformat.so.58)
./ffprobe: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /home/ubuntu/environment/aws-media-replay-engine/source/layers/ffprobe/lib/libavformat.so.58)
./ffprobe: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /home/ubuntu/environment/aws-media-replay-engine/source/layers/ffprobe/lib/libavcodec.so.58)
./ffprobe: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/ubuntu/environment/aws-media-replay-engine/source/layers/ffprobe/lib/libavcodec.so.58)
./ffprobe: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/ubuntu/environment/aws-media-replay-engine/source/layers/ffprobe/lib/libswresample.so.3)
./ffprobe: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/ubuntu/environment/aws-media-replay-engine/source/layers/ffprobe/lib/libswscale.so.5)
./ffprobe: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/ubuntu/environment/aws-media-replay-engine/source/layers/ffprobe/lib/libavutil.so.56)
./ffprobe: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /home/ubuntu/environment/aws-media-replay-engine/source/layers/ffprobe/lib/libavutil.so.56)
./ffprobe: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /home/ubuntu/environment/aws-media-replay-engine/source/layers/ffprobe/lib/libavutil.so.56)
./ffprobe: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /home/ubuntu/environment/aws-media-replay-engine/source/layers/ffprobe/lib/libavutil.so.56)
./ffprobe: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /home/ubuntu/environment/aws-media-replay-engine/source/layers/ffprobe/lib/libfreetype.so.6)
./ffprobe: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/ubuntu/environment/aws-media-replay-engine/source/layers/ffprobe/lib/libpng16.so.16)
        linux-vdso.so.1 (0x00007ffe0aabe000)
        libavdevice.so.58 => /home/ubuntu/environment/aws-media-replay-engine/source/layers/ffprobe/lib/libavdevice.so.58 (0x00007f08f52bb000)
        libavfilter.so.7 => /home/ubuntu/environment/aws-media-replay-engine/source/layers/ffprobe/lib/libavfilter.so.7 (0x00007f08f4d1b000)
        libavformat.so.58 => /home/ubuntu/environment/aws-media-replay-engine/source/layers/ffprobe/lib/libavformat.so.58 (0x00007f08f4ab0000)
        libavcodec.so.58 => /home/ubuntu/environment/aws-media-replay-engine/source/layers/ffprobe/lib/libavcodec.so.58 (0x00007f08f37bf000)
        libswresample.so.3 => /home/ubuntu/environment/aws-media-replay-engine/source/layers/ffprobe/lib/libswresample.so.3 (0x00007f08f529c000)
        libswscale.so.5 => /home/ubuntu/environment/aws-media-replay-engine/source/layers/ffprobe/lib/libswscale.so.5 (0x00007f08f5209000)
        libavutil.so.56 => /home/ubuntu/environment/aws-media-replay-engine/source/layers/ffprobe/lib/libavutil.so.56 (0x00007f08f3526000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f08f3188000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f08f2d97000)
        libfreetype.so.6 => /home/ubuntu/environment/aws-media-replay-engine/source/layers/ffprobe/lib/libfreetype.so.6 (0x00007f08f512c000)
        libbz2.so.1 => /home/ubuntu/environment/aws-media-replay-engine/source/layers/ffprobe/lib/libbz2.so.1 (0x00007f08f5118000)
        libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f08f2b7a000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f08f50a4000)
        libssl.so.3 => not found
        libcrypto.so.3 => not found
        libpng16.so.16 => /home/ubuntu/environment/aws-media-replay-engine/source/layers/ffprobe/lib/libpng16.so.16 (0x00007f08f50da000)
        libharfbuzz.so.0 => /usr/lib/x86_64-linux-gnu/libharfbuzz.so.0 (0x00007f08f28dc000)
        libbrotlidec.so.1 => not found
        libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007f08f25c5000)
        libgraphite2.so.3 => /usr/lib/x86_64-linux-gnu/libgraphite2.so.3 (0x00007f08f2398000)
        libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f08f2127000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f08f1f08000)
user:~/environment/aws-media-replay-engine/source/layers/ffprobe/bin (main) $

Observing the difference between amazonlinux:2 and amazonlinux:2023 /lib64/ directories we can see a difference in the available libraries. The former aligning closer to the AWS Lambda execution context
Possible Fix
We were able to remove the problem by forcing the Dockerfile to pull explicitly from amazonlinux:2

Hi @deadcore ! Thanks for raising this issue and the related PR. We're currently looking into it and will provide an update as soon as possible.

👍 please do let me know if you require any more information


[flutter_tools] fix flutter create --offline

Fixes: https://github.com/flutter/flutter/issues/96286
Pre-launch Checklist

[ ] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[ ] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[ ] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[ ] I signed the [CLA].
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is [test-exempt].
[ ] All existing and new tests are passing.

For testing, I would recommend adding a new test to test/commands.shard/hermetic/create_usage_test.dart and use the FakeProcessManager and FakeCommand like: https://github.com/flutter/flutter/blob/master/packages/flutter_tools/test/commands.shard/hermetic/build_ios_test.dart#L122


Sample show GetDroidModel.DeviceHardware.Model but should end in GetModel

Thank you for letting me know @raymondjstone will get the readme samples corrected today.

Was not the readme samples I was referring to but the text on

In the meantime thanks for this and especially the IOS version.

No problem, glad it's helpful. Just updated ReadMe and thanks once again for letting me know.


Error on "steam.on('webSessionID', function(id)...

steam = the steamClient() here.

steam.on('webSessionID', function(id) {
steam.webLogOn(function(newCookie){
offers.setup({
sessionID: id,
webCookie: newCookie
});
});
});

Once this gets called, I get this error:

c:\Users\sandro\steambot\node_modules\steam\lib\handlers\user.js:106
'steamLogin=' + response.authenticateuser.token,
^
TypeError: Cannot read property 'authenticateuser' of null
at IncomingMessage. (c:\Users\sandro\steambot\node_modules\steam
lib\handlers\user.js:106:35)
at IncomingMessage.emit (events.js:104:17)
at emitReadable_ (_stream_readable.js:424:10)
at emitReadable (_stream_readable.js:418:7)
at onEofChunk (_stream_readable.js:401:3)
at readableAddChunk (_stream_readable.js:146:7)
at IncomingMessage.Readable.push (_stream_readable.js:126:10)
at HTTPParser.parserOnMessageComplete (_http_common.js:154:14)
at TLSSocket.socketOnData (_http_client.js:310:20)
at TLSSocket.emit (events.js:107:17)

Any idea on how to fix this?

You should install node-steam from git, because the npm version is old and doesn't support node.js 0.12 / io.js.
See also: https://github.com/seishun/node-steam/issues/115
This is not a steam-tradeoffers error, so I'm closing this anyway.


Bot Publishing to Azure Error

cat provision.Dev.log
{
"profileName": "Dev",
"jobId": "b3dcbfbd-1172-4d02-8cd0-7aa0aa002952",
"projectId": "73780.06396914319",
"time": "2022-10-13T18:41:31.870Z",
"log": [
"Creating Azure resources...",
"Checking the Existence of the Resource Group ...",
"Use the Resource Group: Dev-Prod at eastus",
"> Creating App Registration ...",
"App create failed, retrying ...",
"App create failed, retrying ...",
"App create failed, retrying ...",
"App create failed, retrying ...",
"App create failed after 3 retries. Error: Request failed with status code 403",
"{"name":"CREATE_APP_REGISTRATION","message":"App create failed! Please file an issue on Github.","stack":"Error\n    at new CustomizeError (/Applications/Bot Framework Composer.app/Contents/Resources/app.asar.unpacked/extensions/azurePublish/dist/extension.js:276418:25)\n    at createCustomizeError (/Applications/Bot Framework Composer.app/Contents/Resources/app.asar.unpacked/extensions/azurePublish/dist/extension.js:276423:10)\n    at BotProjectProvision.createApp (/Applications/Bot Framework Composer.app/Contents/Resources/app.asar.unpacked/extensions/azurePublish/dist/extension.js:277931:17)"}",
"{"name":"CREATE_APP_REGISTRATION","message":"App create failed! Please file an issue on Github.","stack":"Error\n    at new CustomizeError (/Applications/Bot Framework Composer.app/Contents/Resources/app.asar.unpacked/extensions/azurePublish/dist/extension.js:276418:25)\n    at createCustomizeError (/Applications/Bot Framework Composer.app/Contents/Resources/app.asar.unpacked/extensions/azurePublish/dist/extension.js:276423:10)\n    at BotProjectProvision.createApp (/Applications/Bot Framework Composer.app/Contents/Resources/app.asar.unpacked/extensions/azurePublish/dist/extension.js:277931:17)"}. See provision.Dev.log in your bot folder"
]
}

Hi @manthenavamsi,
Could you please provide further details regarding your issue?

What language?
Which App Service type?
Does your account have permission to publish each kind of resource that Composer is attempting to publish?
How many tenants is your account connected to, and what resources appear in which tenant, if applicable?
Any other details that may help.

Closing this issue due to inactivity.

Apologize for the delay. I was offline for sometime.  Currently, working with Microsoft support team to identify the issue.  Appreciate your quick response on this @anishprasad01.
Apologize again.

@anishprasad01 any lead here, tried all possible resolutions provided in other thread like providing contributor access on subscription, Application developer role on AD. But none help, can you suggest.


Resolving correct decimal precision for slp token qty

Use BigNumber for SLP token quantities to prevent rounding errors.

:tada: This PR is included in version 4.4.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


When having multiple security handlers, logic AND is not respect

The issue is that I have two security handlers, handler1 and handler2. handler1 succeeds and handler2 fails. I assume the middleware will return errors, but it actually advance to next(). I believe this is a bug. Please help me with this.

This was recently documented here: https://github.com/apigee-127/swagger-tools/issues/296#issuecomment-153891769  Update this issue with the results.

@whitlockjc thanks a lot for pointing out that reference. It worked as it described, it does support both logic AND and logic OR
In case other people have the same question, here is the yaml:
OR
security:
   - handler1: []
   - handler2: []

AND
security:
  -
    handler1: []
    handler2: []

Again, thanks a lot!


Deprecate internal_aliases

Since the introduction of multiple backends, it's possible (and more natural in my opinion) to define internal aliases by adding a backend that uses the "dummy" driver, and add aliases to that backend. The only annoying thing at the moment is that you're forced to map them, even though it will be ignored. Taxi should allow aliases not to have a mapping.
The plan would be to allow empty values in the configuration file, allow aliases not to have any mapping, and deprecate the internal_aliases setting, removing it completely in > 4.1.
Since you're the initial author of internal aliases, what do you think @jeanmonod ?

Fixed in https://github.com/sephii/taxi/commit/588bde1d6a66cf26d6f485f5fa1d773f42cd9925.


Add support for Apple Silicon and Big Sur

Partly taken from upstream in https://github.com/Reflejo/pam-touchID/pull/18.
It's necessary to create a universal binary to avoid the following error when a program running in Rosetta invokes sudo:
sudo: unable to initialize PAM: No such file or directory

Fixes #7.

It's also working for me on a Mac mini M1 (macOS Big Sur Version 11.2.3 (29D91) 🥳
Thanks @msanders!

This should get merged someday!

I had to update the TARGET for macOS 11.4
TARGET = apple-darwin20.5.0

I also had to manually add write permissions to the sudo file.
$ sudo chmod +w sudo

Then I was able to complete the install steps successfully:

$ sudo make install
Edit /etc/pam.d/sudo to include as the first line:

auth sufficient pam_watchid.so "reason=execute a command as root"

I think the -target flag can be removed completely (as I understand it's set to the current platform by default). At least it worked fine for me.

The target flag is required to make a universal binary so it can work under Rosetta. You can reproduce the above error with:
arch -x86_64 sudo echo

The latest version of macOS, Version 11.6 (20G165) works when you follow my instructions above and replace the target with this:
TARGET = apple-darwin20.6.0


Filter could not configure the , is it a vulnerability?

while I write a link tracker, if the Log API is a dubbo api too, it will be a circle. So I want to add the Log API to exclude list.

I try to understand what you mean, you are talking about a custom Filter is also a Provider interface?

pls refer http://dubbo.apache.org/zh-cn/docs/dev/impls/filter.html, config like

filter="-foo1"

to exclude the filter you don't want to load.


Putting mouse in main menu before initialization is complete crashes

Describe the bug
Putting mouse in main menu before initialization is complete crashes
Application: Brain Simulator,
To Reproduce
Steps to reproduce the behavior:

Start the program
Before the neuron array is displayed, put mouse in vicinity of mainmenu
Crash

The problem is that some of the parameters in the main menu require querying the NeuronEngine before it has been initialized.

This problem is apparently now fixed....


convert packages/example-boards/src/boards/playground/gemini-simple.ts to new Build API

Attempted to migrate this board, but awaiting guidance under discussion #2542 https://github.com/orgs/breadboard-ai/discussions/2542


[RichText] Add file upload support to rich text editor

What

Why

How Tested

Process & policy checklist

[ ] I have updated the project documentation to reflect my changes if necessary.
[ ] I have read the CONTRIBUTING documentation.

Is this a breaking change?

[ ] This change causes current functionality to break.

It looks like bottom padding for the input is bigger than the top padding for the compact mode

and the bottom padding is also increased for the "full" mode

See
https://main--60c7ae6891f0e90039d7cd54.chromatic.com/?path=/docs/ui-components-internal-richtextsendbox--rich-text-send-box
for the previous version


Taxonomy API Support

Any plan to support Taxonomy API?
Anyway thanks a lot for your package, it rocks !

Support for the Taxonomy API is currently on the develop branch. I'm hoping to get this merged into the main branch do a full release over the next week.
I'll leave this issue open in case anyone else is interested and close it once the support is live.

Support for the Taxonomy API has been added to the 13.0.0 release.

There is also an example available.


Return raw array data for further processing with numpy

I'm transferring several float arrays with millions of samples each second by using read_by_name with PLCTYPE_ARR_REAL(1000000).
After profiling i noticed the function is spending most of its time in converting the ctypes array to a Python list:
 if type(data_type).__name__ == "PyCArrayType": return [i for i in data]
Adding a "raw" argument, that returns the ctypes array directly, and reading it into a numpy array via np.frombuffer afterwards/manually reduces the time spent in this function by ~80% and increases the overall throughput a lot.

Update: I compared the normal implementation with the one i quickly patched to return a normal ctype array. The speedup is up to factor 20.
import numpy as np
from pyads import Connection, constants as pyadsconstants
from mctrl_tb.pkg.pyads import Connection as Connection_patched

if __name__ == '__main__':
    import timeit
    c = Connection("<IP_ADDRESS>.1.1", 852)
    c.open()
    c_patched = Connection_patched("<IP_ADDRESS>.1.1", 852)
    c_patched.open()

    buffer = pyadsconstants.PLCTYPE_ARR_REAL(1000000)

    ##### Quick'n'Dirty Patch - pyads_ex.py, line 539 #####
    #
    # if type(data_type).__name__ == "PyCArrayType":
    # if getattr(data_type, "__raw__", False):
    #     return data
    # else:
    #     return [i for i in data]
    #

    buffer.__raw__ = True

    print(timeit.timeit("""data = c.read_by_name("MAIN.fbDataBuffer_array1.aTransferBuffer", buffer)""",
                        globals=globals(),
                        number=20) / 20)

    print(timeit.timeit("""data = np.frombuffer(c_patched.read_by_name("MAIN.fbDataBuffer_array1.aTransferBuffer", buffer), dtype=np.float32)""",
                        globals=globals(),
                        number=20) / 20)

First is 0.166s per call, second is 0.008s per call.

@pyhannes That is definetely a massive amount of time it takes to convert to a Python list. Thanks for bringing that up. I think my preferable way to go here is to add a parameter raw to the read/write functions to prevent type conversion if wanted.

I added a parameter return_ctypes to read functions to allow omit the conversion to Python data types.


graphiql + webpack 5 errors

"graphiql": "^1.8.7",
"graphql": "^16.3.0"
After upgrading to webpack 5 (I'm using the latest graphql and graphiql versions) I am getting a lot of the following errors:
ERROR in ./node_modules/graphiql/esm/components/DocExplorer.js 83:17-23 export 'isType' (imported as 'isType') was not found in 'graphql' (possible exports: default)
Anyone else running into these issues?

oof - we aren't testing for<EMAIL_ADDRESS>yet my bad, I have this PR where we will address this issue

I solved my issue by changing my webpackChunkName to something other than  "graphql"


Erroneous aggregation with nulls.

Hello.
I have an aggegation over a measure with a lot of nulls. Let's say I have a point each 5 minutes while whisper stores each minute.
When I configure the aggregation method "max" or "latest", it always returns null, so I'm losing all the stores.
I'm not sure if I'm doing something wrong, but IMHO, "max" should just consider the not-null values, so I should not lose any value.
Thank you in advance.
Configuration:
[example]
pattern = metrics.example
xFilesFactor = 0.5
aggregationMethod = max

I think i have a similiar problem. Carbon Cache is configured with saving points every minute for 7 days. But most most of our metrics come in a 5min interval. And that works fine for the period of 7 daysl. I can see the graph in graphite-web without the "null" points.
But as soon as it gets to the second timeperiod the graph is empty.
This is my storage scheme:
[icinga_default]
pattern = ^icinga2.
retentions = 1m:5d,5m:14d,10m:90d,30m:180d,60m:1y,360m:4y
bizarrely we also have metrics that come only once an hour but they are correctly aggregated without the nulls in higher timeperiods.
graphite-carbon version is 0.9.12-3
python-whisper version is 0.9.12-1

I think i have a similiar problem. Carbon Cache is configured with saving points every minute for 7 days. But most most of our metrics come in a 5min interval. And that works fine for the period of 7 daysl. I can see the graph in graphite-web without the "null" points.
But as soon as it gets to the second timeperiod the graph is empty.
This is my storage scheme:
[icinga_default]
pattern = ^icinga2.
retentions = 1m:5d,5m:14d,10m:90d,30m:180d,60m:1y,360m:4y
bizarrely we also have metrics that come only once an hour but they are correctly aggregated without the nulls in higher timeperiods.
graphite-carbon version is 0.9.12-3
python-whisper version is 0.9.12-1

I suspect you're not familiar with how the xFilesFactor attribute works. See the following documentation.
http://obfuscurity.com/2012/04/Unhelpful-Graphite-Tip-9
http://graphite.readthedocs.org/en/latest/config-carbon.html?highlight=xfilesfactor#storage-aggregation-conf
If this addresses your question, please go ahead and close this issue. If you still think you're seeing a bug please let me know and we'll look into it further.

So by setting xFilesFactor to 0.0 should fit the bill. I will try, and if it works, I will close this issue.
Thank you very much.

Checked and working.
Thank you very much!


Support for MacOS

Could you document in the Readme whether you plan to support MacOS in the future or it will be a limitation?

Supporting macOS would be great, but unless I get my hands on a Mac or somebody with a Mac makes a pull request, it's not happening.

Just my 0.02$, as I was also looking for Mac support and the only thing I needed to do was copy some HTML into the HTML clipboard, I solved it like this (just leaving this here because it might help someone in the future):
import subprocess
import binascii
from sys import platform

html = '''

Title text

Example, Bold

'''.encode()

if platform == "darwin":
    hexvalue = html.hex()
    command = f"echo 'set the clipboard to «data HTML{hexvalue}»'|osascript"
    #print(command)
    subprocess.run(command, shell=True)
else:
    pass # use klembord

So basically using Apple script (osascript) a lot of the functionalities are possible (although subprocessing to the shell might not be everyone's favourite option).
Btw. if anybody is wondering, this way you can generate Microsoft Word formatted clipboard content (you can use a tool like ClipSpy to reverse engineer the HTML clipboard contents generated by Word) on a client host machine with python and then paste it into a Windows VM that runs Microsoft Word.


[BUG] This app package is not signed with a trusted certificate.

:information_source: Info

Version: v0.1.15
:speech_balloon: Description

Misx Installer gives this message
This app package is not signed with a trusted certificate. Contact your system administrator or the app developer to obtain a new certificate or app package with trusted certificates. The root certificate and all immediate certificates of the signature in the app package must be trusted (0x800B010A)

and hence cant install the app on windows with msix.
msix_config:
  display_name: myCompany
  publisher_display_name: myCompany Pvt Ltd
  identity_name: com.myCompany
  msix_version: <IP_ADDRESS>
  certificate_path: certificates\certificate.pfx
  certificate_password: pass...
  publisher: E=s..gmail.com, CN=myCompany, OU=myCompany, O=myCompany Pvt Ltd, L=Delhi, S=DL, C=IN
  logo_path: windows\runner\resources\app_logo.png
  start_menu_icon_path: windows\runner\resources\app_logo.png
  tile_icon_path: windows\runner\resources\app_logo.png
  vs_generated_images_folder_path: images
  icons_background_color: transparent
  architecture: x64
  capabilities: 'internetClient'

Hey
you have valid certificate but this certificate is not in your "trusted certificates"
you need to add it
try this: new certificate must be installed for this app package

Thanks for the help I figured this was the issue. Now there are two questions.

It doesn't seem scalable. How to deal with a situation when we put msix file for direct download. Is there a way these certificate direct auto-installs
I'm receiving this error now

App installation failed with error message: AppxManifest.xml(89,27): error 0x80070002: Cannot install or update package com.OneRootsappTechnologies.Blup_feq996qmq6gam because the splash screen image [SplashScreen.png] cannot be located. Verify that the package contains an image that can be used as a splash screen for the application, and that the package manifest points to the correct location in the package where this splash screen image can be found. (0x80070002)

@YehudaKremer, The app after install does not go ahead of the splash screen. Is this package only working with UWP version of flutter? I have build the app in win32 API version of flutter [https://github.com/google/flutter-desktop-embedding]

The app after install does not go ahead of the splash screen.

I believe it is happening because it is not mapping with the correct .exe file.
I looked into the installed folder everything is there and runs perfectly if run through .exe file but not working if run from start menu.


Connection between BFD/BGP alarms and its outgoing interface

Today, when a bgp or bfd neighbor goes down there are no connection between this alarm and what physical interface it is connected to.
But as zino collects at least all ip adresses used on each device (and probably also its subnet-mask?) it could be possible to trace back its connected interface for this neighborship. This information could  then be available to the client so it could be displayed to the user to make it easier to show the connection between "port down" and "bgp alarms".
This will only work for directly connected neighbours, and not for multihop neighbours, but i think at least in our net we have 99% singlehop neighbors.. so this will work for almost all neighbors but might not for all.

i think both outgoing ifname and ifalias could at least be fetched to the bgp and bfd cases.


mgmt, increment version after cosmos release

Description
This PR is for the increment fix after azure-resourcemanager-cosmos 2.28.0-beta.1 released.
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.

/checkenforcer override

/check-enforcer override


Latest release is incompatible with latest jsinterop-base release

Latest elemental2 release is 1.0.0-beta-1 (released April 5, 2017), and in Document has the inner type CreateTextNodeDataUnionType, which defines:
@JsOverlay
default double asDouble() {
  return Js.castToDouble(this);
}

However, latest jsinterop-base release is 1.0.0-beta-2 (released May 5, 2017) has a Js class with no castToDouble. Instead, it has
@SuppressWarnings("ReferenceEquality") // GWT is not good at optimizing equals
public static double asDouble(Object obj) {
  checkType(Js.typeof(obj) == "number");
  return InternalJsUtil.asDouble(obj);
}

This results in a compile-time error with GWT 2 (and a runtime error with j2cl).

We are working on new jsinterop.base release and in the process of releasing source in a repo as well.

fixed with 70c4a8560bbaabc77ea5a383e89fa811f2e51210


feat(load-more)

UPDATE:
There is still a bug in the page-feed cards layout (WIP - we have to QA the pages, including the page "Learn", to make sure they look okay before merging)

Works great!


Install on stretch, php7.0 package not found

Joe please add:
sudo apt update after OS update.
Otherwise setup is cancelled after 5 unsuccessfull attempts to locate php7.0 package.
"sudo apt update" is solving this problem.
Thanks in advance

That is strange the apt update executed when the script is initially executeds should get all current packages. This package list should only become out dated when a new package is added to the Debian repository.
There is a check where if the apt update command was executed within the last 30 mins it skips this command. I just added a way to override this check by using either the -u or --apt-update flag when executing install.sh.
./install.sh --apt-update
commit 6bbae71eb9915148293d5e56164a3f4a96c146d8


Missing Passphrase Option in Backups for Oneview 8.6 and above

https://techlibrary.hpe.com/docs/enterprise/servers/oneview8.6/cicf-api/en/index.html#whatIsNew
According to the release Notes of oneview 8.6, backups now require a passphrase on creation.
Due to that reason, this code needs to be adjusted, to allow the input of passphrases:
https://github.com/HewlettPackard/oneview-python/blob/v8.6.0/hpeOneView/resources/settings/backups.py#L62-L77

Hi lukas,
Thanks for pointing this out. We will add this issue into our backlog and take it as per our priority


abstract/loose equality assertion?

In looking through the API docs, it seems as though there's only assertions for strict equality (===). Am I missing a function somewhere, or is only strict equality supported? If only strict equality is supported now, would you be open to a PR for adding abstract/loose equality (==)? Perhaps something along the lines of:
var foo = '123';
foo.should.looseEqual(123);

I'm obviously very open to alternatives to the function name, I just threw () out there to start the conversation.

I am open to PR in general, but it a bit sounds strange. I could not imagine where current .equal and .eql
'equality' assertions do not suite.
Could you please describe your real use case? Or it is just something potential.
In past i did not added == because it is adding more confusion (3 assertion equality methods) and allow literally to shoot in the foot.

The real use case for me is I have a unit test where I want to assert that both my express route is returning the right status code, and that my JSONAPI serialized response also has that same response code. The problem is that express returns it as a number, and JSONAPI expects status as a string.
so in my case I have something like this (abridged):
let status = 401;
request.post({ url }, function(err, resp, body) {
  resp.statusCode.should.equal(status);

  // wish I could do this:
  // body.errors[0].status.should.looseEqual(status);
  body.errors[0].status.should.equal(String(status));
});

We check this in tons of places. It's by no means critical and converting the value explicitly works. Was more wondering what the maintainers thought and if any other users of should.js would find this useful, and if I wrote a PR if it would get merged.

I got you. But to me it looks you just need to extend should yourself for your project (as your usecase pretty valid for your project mostly, but outside it is something questinable).

Yep, I'm extending it now. I'll close this for now. If in the off-chance others have more valid use cases they can drop a comment here and you can revisit.

Thank you. 👍 Awaiting feedback.


Use execute instead of execpipe

Current version of brew does not allow 'brew tap' to be run as root.  Figured I would fix the execpipe() in homebrew.rb as well.
This fixes the following error:
Error: Instances failed: #IO:0x007fc02df13d68
Error: Could not prefetch package provider 'tap': undefined method `each' for nil:NilClass

We're running into this too, since we run puppet as root but not brew.

Thanks a lot for spotting this one.
Sorry for the slow response, I was on business travel away from easy Internet access.


fix: support of various PHP, Composer, and Symfony versions

It adds support of various PHP, Composer, and Symfony versions.
Description
Different versions of composer depends on different versions of symfony/console, devtools runs in composer context and can conflict with project's version of symfony. I added support of all the relevant combinations.
Motivation and context
I like that tool, but it didn't work with modern versions of PHP and Symfony.
How has this been tested?
Tests are fixed and runs in matrix of:

PHP 7.4, 8.0, 8.1
Symfony 5.4, 6.0, 6.1
composer 1, 2.2, 2.3, 2.4

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

PR checklist

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING.md document.
[x] I have added tests to cover my changes.

I am currently experiencing this error:

Fatal error: Declaration of Ramsey\Dev\Tools\Composer\Command\BaseCommand::getApplication(): Symfony\Component\Console\Application must be compatible with Composer\Command\BaseCommand::getApplication(): Composer\Console\Application in /Users/danpock/MyGitProjects/php-whois-server-list/vendor/ramsey/devtools-lib/src/Composer/Command/BaseCommand.php on line 135

Which appears to be fixed by this PR. Additionally as noted it seems this PR fixes an older open issue I opened (#90).

Thank you for contributing! 🎉


Remove remaining links to old docs

Hmm. Github checks seems confused, with two travis builds, one completed and one still in progress.


FluentBit Sidecar Injection

Is your feature request related to a problem? Please describe.
Hello! I work for a really big Italian Company in the Energy sector and we are creating a log pipeline solution using FluentBit as a sidecar container sending record to FluentD deployment pods. We are onboarding hundreds of microservices, so there is a lot of repetitive work to do right now.
Describe the solution you'd like
So, I'm wondering if a sidecar injector pattern ( the same you find in opentelemetry, envoy, ecc...) with a combination of pod metadata annotations and admission mutating webhook is something that are you considering to implement and if not why so?
Additional context
I've tried to find related issues but I didn't find anything. Yet, I don't know the fluent operator project codebase, so maybe what I am asking is not feasibile in the first place, but since this is a real world scenario we are facing, maybe it could be in the community interest.
To conclude, I would be willing to contribute to implement this feature if you express interest in it.

It's not on the roadmap yet. But Fluent operator maintainers are open to seeing proposals and contributions for this feature. @AlessandroFazio

Hello @benjaminhuo  , I'm glad to see you open to a proposal. I have taken some time to come up with the more formal feature request which follows.
FluentBit Sidecar Feature Request
Disclosure
Before proceeding with the technical content, I would like to stress 2 points:

I haven’t had the time to look closely at the Fluent Operator codebase, so I could have missed some points in this initial draft of the solution.
This is not meant to be an exhaustive description of the feature, it is purely written for you to know more concretely (and likely me too) what I have in mind and how it can be achieved.

Introduction
This feature request aims at adding the ability for FluentOperator users to inject FluentBit as a sidecar container in pods.
This container should in some way featch log events produced by main application container and forward them to some destination. It could be FluentD and in this way leverage the FluentD CR provided by the operator or some other destionation.
For fetching log events I proposed here to use an emptyDir volume, where the app writes and the FluentBit reads. In the General Considerations section below I explained the reason behind this choice.
This solution requires making the manager to bootstrap a new Webhook Server (which is not already bootstrapped in the operator codebase for what I have seen) serving at least a mutating admission webhook under some path, could be /mutate-core-v1-pods.
Configuration
The mutating webhook could be configured using a ConfigMap added as part of the manifests and mounted as a volume in the controller-manager container.
The configMap can be read from its mountPath adding an additional flag in the main.go file and adding common logic for loading its content in go program memory.
The user should opt in for the sidecar injector, i.e the feature would be disabled by default.
To enable the injection logic to take place, edit the first property enabled: bool.
So by default the webhook server will be part of the controller-manager process, basically doing nothing and returning pod object as is.
The ConfigMap could like as the following:
apiVersion: admissionregistration.k8s.io/v1
kind: ConfigMap
metadata:
 name: fluent-sidecar-injector
 ...
data: |
  enabled: true
  fluentBitImage: kube-sphere/fluent-bit:tag
  sidecarRequestsCPU: 100m
  ...
  sidecarLimitsCPU: 300m
  ...

Other webhook manifests like Deployment, Service, CertManager related manifests, etc… are skipped for the sake of brevity, but naturally required.
The webhook configuration manifest could look something like this:
apiVersion: admissionregistration.k8s.io/v1
kind: MutatingWebhookConfiguration
webhooks:
 - name: fluent-sidecar.example.com
   namespaceSelector:
     matchLabels:
       fluent.sidecar.io/enabled: true
       rules:
      - apiGroups:   [""]
  apiVersions: ["v1"]
  operations:  ["CREATE"]
  resources:   ["pods"]
  scope:       "Namespaced"
...

Sidecar Injection Logic
The sidecar injection implementation follows the ‘Istio way’. You should label the namespace with fluent.sidecar.io/enabled: true, then for each pod created in this namespace the webhook will be called by the APIServer. This way you can limit the number of pods the webhook will process, based on the Namespace selector configuration.
Then, if the user specifies fluent.sidecar.io/inject: false in the pod metadata.annotations[] , injection will be skipped.
Sidecar customization can be achieved either through:

Pod metadata annotations
Partial configuration of FluentBit sidecar in pod.spec.containers

Pod Metadata Annotations
The following pod metadata.annotations[] let the user customize the sidecar injection execution logic.
- Key: fluent.sidecar.io/inject
  Value: bool
  Desc: specify whether the webhook should inject the sidecar
- Key: fluent.sidecar.io/application-logs/path
  Value: string
  Desc: specify the path on app container directory where app logger appender will write log files
- Key: fluent.sidecar.io/position-db/volume
  Value: bool
  Desc: specify whether the webhook should inject the position-db volume
- Key: fluent.sidecar.io/applications-logs/volume-size-limit
  Value: quantity
  Desc: specify the application logs volume size limit
- Key: fluent.sidecar.io/sidecar/request-cpu
  Value: quantity
  Desc: specify the FluenBit sidecar container resource.requests.cpu
- Key: fluent.sidecar.io/sidecar/request-memory
  Value: quantity
  Desc: specify the FluenBit sidecar container resource.requests.memory
- Key: fluent.sidecar.io/sidecar/request-ephemeral-storage
  Value: quantity
  Desc: specify the FluenBit sidecar container resource.requests.ephemeral-storage
- Key: fluent.sidecar.io/sidecar/limit-cpu
  Value: quantity
  Desc: specify the FluenBit sidecar container resource.limit.cpu
- Key: fluent.sidecar.io/sidecar/limit-memory
  Value: quantity
  Desc: specify the FluenBit sidecar container resource.limit.memory
- Key: fluent.sidecar.io/sidecar/limit-ephemeral-storage
  Value: quantity
  Desc: specify the FluenBit sidecar container resource.limit.ephemeral-storage
- Key: fluent.sidecar.io/sidecar/image
  Value: string
  Desc: specify the FluenBit sidecar container image

Partial Sidecar Configuration
The user could include directly the fluent-bit sidecar container in the pod .spec.containers[].
The partial configuration could look like the following:
apiVersion: apps/v1
kind: Pod
metadata:
  name: example
spec:
  containers:
   # other containers #
name: fluent-bit
image: auto
...

If this is done, the following will happen:

Webhook will know the pod needs to be processed
Webhook will check if the image field is set to ‘auto’. If so it will replace it with the kube-sphere FluentBit image
Webhook will add the usual components to FluentBit container if not already specified by the user

This customization option is found in Istio sidecar injection implementation and offers both flexibility and ease of implementation (either for users and us as developers)
Reconcile Logic
Here is described in short the webhook business logic:

Check if pod should not be processed depending on:
a) If sidecar injector config property enabled: false
b) If pod metadata.annotations[] specify fluent.sidecar.io/inject: false

Add to pod spec.volumes[] the following:
a) Application logs emptyDir volume
b) FluentBit config emptyDir volume
c) FluentBitDb emptyDir volume

Create FluentBit sidecar container

Mount inside the FluentBit sidecar container:
b) FluentBit config volume
c) FluentBitDb volume if specified in the
d) ApplicationLogs volume

Add FluentBit sidecar container in pod spec.containers[]

Mount ApplicationLogs volume into application container at specified mount point

General Considerations
A natural decision is to leverage CRs already provided by the Fluent Operator, such as the configuration-related CRs.
Both the namespaced and the cluster-level configuration CRs can be leveraged depending on the user needs.
In both cases the FluentBit configuration secret will be mounted as a volume inside the FluentBit sidecar container.
However, an issue can arise when the user deploys the operator but not the configuration CRs.
There is really low probability this will happen, but it can happen.
In this situation the secret would not be created and if some namespaces are matched, scheduled pods will be stuck in the ContainerCreating phase indefinitely, since they are trying to mount a non-existent secret.
To overcome this issue I have came across these 2 solutions:

Create a validation webhook to check for secret exists and reject the pod if this is not the case
Use an InitContainer which queries the APIServer for secret in its namespace equipped with appropriate service account permissions. The InitContainer will fail on timeout exceeded or resource not found error, causing the pod to fail.

As you can imagine they are not mutually exclusive, in the sense that the validation webhook can be useful at least to send warnings to the user.
You may notice that, given this issue, it becomes even more important to give the user the ability to skip the injection using pod metadata annotations.
I guess there are other ways to deal with this, I haven't had the time to think about it yet. I hope you can help me in this regard.
For what concerns the emptyDir volume solution to store applications log files written by app and read by FluentBit, we actually came up with this solution at my company.
Avoiding weird tricks, for example I’ve seen one somewhat weird using linux pipes, we found no easy way to make log events available to FluentBit process in separate container other than mounting that volume and reading files in it.
To conclude, I haven't talked about kustomize or helm configuration. I know this is a really crucial topic, indeed if this sofware is not easy to install, it looses lot of its value. However, I preferred to discuss the business logic and related issues for now. If the discussion about this feature will progress, we will have the time for think about the deployment side of things.
Well, this is the end for now. I know that this description is far from complete,  but we have to start from something. Let me know what you think about it with some feedback.

I think the feature is overall useful, but from what I've seen, in k8s sidecar is only useful for logging when the application isn't writing logs to stdout and instead writes it to some file in the container.
Questions or comments on your proposal:

You mentioned using existing CRs to configure fluent-bit sidecar. Will this result in creation of a secret per pod that'd be mounted?
I wouldn't recommend using the same set of CRs for configuring sidecars, since logging sidecar configs are specific to pods being injected into (or the application running in the pod, you'd use a different filter/parser for different applications), so the sidecar configs don't really have a cluster or namespace scope.

Hello @adiforluls , I'm glad to see some feedbacks on this feature.
To address the points you raised:

Based on my experience, choosing between writing logs to stdout or the filesystem isn't necessarily an either-or decision. Most mature logging libraries in common programming languages allow for configuring handlers to output logs to multiple streams simultaneously. This setup is common in several large projects at the company where I currently work, where applications write logs both to a file mounted as a container volume and to stdout and then they follow different path downstreams.

Regarding the handling of secrets, they should be created as usual using Configuration CRs and then mounted by each instrumented Pod in the Namespace. I didn't clarify this point sufficiently in the initial draft proposal: it's advisable to set up a default Secret per Namespace for mounting configuration into containers. Then, using Pod metadata annotations[], you can override the default Secret name as needed. Typically, it's a best practice and common to maintain consistent logging patterns and formats across applications grouped into projects, preferably ones that are parseable by a common parser. However, and I'm facing such a case right now, this is not always the case. If a common parser doesn't fit all applications needs in the Namespace, you still have the flexibility to override the mounted Secret. Going to the extreme, in cases where each logging format or pattern differs, you can still delegate parsing to aggregators and have FluentBit sidecars act solely as forwarders, optionally adding metadata for disambiguation downstream (often relevant at the Namespace level, based on my experience).


kie-kogito-images-1744: Disable question about collecting Quarkus analytics

Many thanks for submitting your Pull Request :heart:!
Fix #1744
Please make sure your PR meets the following requirements:

[X] You have read the contributors guide
[X] Pull Request title is properly formatted: [KOGITO|RHPAM-XYZ] Subject
[X] Pull Request contains link to the JIRA issue
[X] Pull Request contains description of the issue
[X] Pull Request does not include fixes for issues other than the main ticket
[X] Your feature/bug fix has a testcase that verifies it
[X] You've tested the new feature/bug fix in an actual OpenShift cluster
[X] You've added a RELEASE_NOTES.md entry regarding this change

How to retest this PR or trigger a specific build:

(Re)run Jenkins tests
Please add comment: Jenkins [test|retest] this

How to backport a pull request to a different branch?

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

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

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

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

Waiting for green CI + testing it locally.

The image has been build and can be tested here: quay.io/ricardozanini/kogito-swf-devmode:srvlogic-231

I did a smoke test and apparently, it's working. Waiting for CI:
docker run --rm -it quay.io/ricardozanini/kogito-swf-devmode:srvlogic-231
INFO Configure Maven
INFO --> checking if .mvn/jvm.config exists.
INFO ---> .mvn/jvm.config does not exists, memory will be calculated based on container limits.
[INFO] Scanning for projects...
[INFO]
[INFO] ----------------< org.acme:serverless-workflow-project >----------------
[INFO] Building serverless-workflow-project 1.0.0-SNAPSHOT
[INFO]   from pom.xml
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- clean:3.2.0:clean (default-clean) @ serverless-workflow-project ---
[INFO]
[INFO] --- resources:3.3.1:resources (default-resources) @ serverless-workflow-project ---
[INFO] Copying 0 resource from src/main/resources to target/classes
[INFO]
[INFO] --- quarkus:3.2.9.Final:generate-code (default) @ serverless-workflow-project ---
[WARNING] K_SINK variable is empty or doesn't exist. Please make sure that this service is a Knative Source or has a SinkBinding bound to it.
[INFO]
[INFO] --- compiler:3.11.0:compile (default-compile) @ serverless-workflow-project ---
[INFO] Changes detected - recompiling the module! :source
[INFO] Compiling 1 source file with javac [debug release 17] to target/classes
[INFO]
[INFO] --- quarkus:3.2.9.Final:dev (default-cli) @ serverless-workflow-project ---
[INFO] Invoking resources:3.3.1:testResources (default-testResources) @ serverless-workflow-project
[INFO] skip non existing resourceDirectory /home/kogito/serverless-workflow-project/src/test/resources
[INFO] Invoking quarkus:3.2.9.Final:generate-code-tests (default) @ serverless-workflow-project
[WARNING] K_SINK variable is empty or doesn't exist. Please make sure that this service is a Knative Source or has a SinkBinding bound to it.
[INFO] Invoking compiler:3.11.0:testCompile (default-testCompile) @ serverless-workflow-project
[INFO] Changes detected - recompiling the module! :dependency
Listening for transport dt_socket at address: 5005
2024-02-20 16:35:41,985 27f28debb463 WARN  [org.kie.kogito.addons.quarkus.knative.eventing.KnativeEventingConfigSourceFactory:-1] (main) K_SINK variable is empty or doesn't exist. Please make sure that this service is a Knative Source or has a SinkBinding bound to it.
2024-02-20 16:35:42,262 27f28debb463 WARN  [org.kie.kogito.addons.quarkus.knative.eventing.KnativeEventingConfigSourceFactory:-1] (main) K_SINK variable is empty or doesn't exist. Please make sure that this service is a Knative Source or has a SinkBinding bound to it.
2024-02-20 16:35:42,977 27f28debb463 WARN  [io.quarkus.resteasy.mutiny.deployment.ResteasyMutinyProcessor:-1] (build-10) The quarkus-resteasy-mutiny extension is deprecated. Switch to RESTEasy Reactive instead.
This extension adds support for Uni and Multi to RESTEasy Classic, without using the reactive execution model, as RESTEasy Classic does not use it. To properly integrate Mutiny and RESTEasy, use RESTEasy Reactive. See https://quarkus.io/guides/getting-started-reactive for detailed instructions

2024-02-20 16:35:43,977 27f28debb463 INFO  [org.kie.kogito.codegen.api.utils.AddonsConfigDiscovery:-1] (build-24) Performed addonsConfig discovery, found: AddonsConfig{usePersistence=false, useTracing=false, useMonitoring=false, usePrometheusMonitoring=false, useCloudEvents=true, useExplainability=false, useProcessSVG=false, useEventDrivenDecisions=false, useEventDrivenRules=false}
2024-02-20 16:35:44,101 27f28debb463 INFO  [org.kie.kogito.codegen.core.utils.ApplicationGeneratorDiscovery:69] (build-32) Generator discovery performed, found [processes]
2024-02-20 16:35:44,105 27f28debb463 INFO  [org.kie.kogito.codegen.core.ApplicationGenerator:145] (build-32) Skipping generator 'processes' because disabled
2024-02-20 16:35:46,352 27f28debb463 WARN  [org.kie.kogito.jobs.service.openapi.JobServiceModelFilter:77] (build-10) SpecVersion enum schema is not present in the OpenAPI document.
__  ____  __  _____   ___  __ ____  ______
 --/ __ \/ / / / _ | / _ \/ //_/ / / / __/
 -/ /_/ / /_/ / __ |/ , _/ ,< / /_/ /\ \
--\___\_\____/_/ |_/_/|_/_/|_|\____/___/
2024-02-20 16:35:49,557 27f28debb463 WARN  [io.quarkus.config:-1] (Quarkus Main Thread) Unrecognized configuration key "kogito.data-index.domain-indexing" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo

2024-02-20 16:35:49,557 27f28debb463 WARN  [io.quarkus.config:-1] (Quarkus Main Thread) Unrecognized configuration key "kogito.data-index.health-enabled" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo
2024-02-20 16:35:49,557 27f28debb463 WARN  [io.quarkus.config:-1] (Quarkus Main Thread) Unrecognized configuration key "kogito.data-index.blocking" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo
2024-02-20 16:35:49,558 27f28debb463 WARN  [io.quarkus.config:-1] (Quarkus Main Thread) Unrecognized configuration key "quarkus.container-image.group" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo
2024-02-20 16:35:49,558 27f28debb463 WARN  [io.quarkus.config:-1] (Quarkus Main Thread) Unrecognized configuration key "kogito.apps.persistence.type" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo
2024-02-20 16:35:49,558 27f28debb463 WARN  [io.quarkus.config:-1] (Quarkus Main Thread) Unrecognized configuration key "quarkus.container-image.build" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo
2024-02-20 16:35:51,531 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (Quarkus Main Thread) Detected a Linux x86_64 system
2024-02-20 16:35:51,586 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.DefaultPostgresBinaryResolver:-1] (Quarkus Main Thread) Detected distribution: 'Red Hat Enterprise Linux'
2024-02-20 16:35:51,588 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.DefaultPostgresBinaryResolver:-1] (Quarkus Main Thread) System specific postgres binaries found: 'postgres-linux-x86_64.txz'
2024-02-20 16:35:51,694 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (Quarkus Main Thread) Extracting Postgres...
2024-02-20 16:35:54,328 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (Quarkus Main Thread) Postgres binaries at /tmp/embedded-pg/PG-102e6363fced1e91aa3b6178e0d6f3a9
2024-02-20 16:35:54,359 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (initdb:pid(278)) The files belonging to this database system will be owned by user "kogito".
2024-02-20 16:35:54,359 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (initdb:pid(278)) This user must also own the server process.
2024-02-20 16:35:54,359 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (initdb:pid(278))
2024-02-20 16:35:54,359 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (initdb:pid(278)) The database cluster will be initialized with locale "C".
2024-02-20 16:35:54,359 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (initdb:pid(278)) The default text search configuration will be set to "english".
2024-02-20 16:35:54,359 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (initdb:pid(278))
2024-02-20 16:35:54,359 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (initdb:pid(278)) Data page checksums are disabled.
2024-02-20 16:35:54,359 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (initdb:pid(278))
2024-02-20 16:35:54,359 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (initdb:pid(278)) fixing permissions on existing directory /tmp/epg11798243420465647914 ... ok
2024-02-20 16:35:54,360 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (initdb:pid(278)) creating subdirectories ... ok
2024-02-20 16:35:54,360 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (initdb:pid(278)) selecting dynamic shared memory implementation ... posix
2024-02-20 16:35:54,372 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (initdb:pid(278)) selecting default max_connections ... 100
2024-02-20 16:35:54,387 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (initdb:pid(278)) selecting default shared_buffers ... 128MB
2024-02-20 16:35:54,472 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (initdb:pid(278)) selecting default time zone ... UTC
2024-02-20 16:35:54,473 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (initdb:pid(278)) creating configuration files ... ok
2024-02-20 16:35:54,627 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (initdb:pid(278)) running bootstrap script ... ok
2024-02-20 16:35:55,222 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (initdb:pid(278)) performing post-bootstrap initialization ... ok
2024-02-20 16:35:56,175 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (initdb:pid(278)) syncing data to disk ... ok
2024-02-20 16:35:56,175 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (initdb:pid(278))
2024-02-20 16:35:56,175 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (initdb:pid(278)) Success. You can now start the database server using:
2024-02-20 16:35:56,175 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (initdb:pid(278))
2024-02-20 16:35:56,175 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (initdb:pid(278))     /tmp/embedded-pg/PG-102e6363fced1e91aa3b6178e0d6f3a9/bin/pg_ctl -D /tmp/epg11798243420465647914 -l logfile start
2024-02-20 16:35:56,175 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (initdb:pid(278))
2024-02-20 16:35:56,178 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (Quarkus Main Thread) 77debbea-3d48-4586-8df0-97dcfdd70da8 initdb completed in 00:00:01.846
2024-02-20 16:35:56,188 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (Quarkus Main Thread) 77debbea-3d48-4586-8df0-97dcfdd70da8 postmaster started as Process[pid=289, exitValue="not exited"] on port 38067.  Waiting up to PT10S for server startup to finish.
2024-02-20 16:35:56,211 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (postgres:pid(289)) waiting for server to start....2024-02-20 16:35:56.211 UTC [292] LOG:  starting PostgreSQL 14.8 on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0, 64-bit
2024-02-20 16:35:56,212 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (postgres:pid(289)) 2024-02-20 16:35:56.212 UTC [292] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 38067
2024-02-20 16:35:56,212 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (postgres:pid(289)) 2024-02-20 16:35:56.212 UTC [292] LOG:  could not bind IPv6 address "::1": Cannot assign requested address
2024-02-20 16:35:56,212 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (postgres:pid(289)) 2024-02-20 16:35:56.212 UTC [292] LOG:  listening on Unix socket "/tmp/.s.PGSQL.38067"
2024-02-20 16:35:56,215 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (postgres:pid(289)) 2024-02-20 16:35:56.215 UTC [293] LOG:  database system was shut down at 2024-02-20 16:35:55 UTC
2024-02-20 16:35:56,218 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (postgres:pid(289)) 2024-02-20 16:35:56.218 UTC [292] LOG:  database system is ready to accept connections
2024-02-20 16:35:56,296 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (postgres:pid(289))  done
2024-02-20 16:35:56,296 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (postgres:pid(289)) server started
2024-02-20 16:35:56,377 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:-1] (Quarkus Main Thread) 77debbea-3d48-4586-8df0-97dcfdd70da8 postmaster startup finished in 00:00:00.198
2024-02-20 16:35:56,377 27f28debb463 INFO  [io.quarkiverse.embedded.postgresql.EmbeddedPostgreSQLRecorder:-1] (Quarkus Main Thread) Embedded Postgres started at port "38067" with database "postgres", user "postgres" and password "postgres"
2024-02-20 16:35:56,496 27f28debb463 WARN  [org.kie.kogito.addons.quarkus.knative.eventing.KnativeEventingConfigSourceFactory:-1] (Quarkus Main Thread) K_SINK variable is empty or doesn't exist. Please make sure that this service is a Knative Source or has a SinkBinding bound to it.
2024-02-20 16:35:56,496 27f28debb463 WARN  [org.kie.kogito.addons.quarkus.knative.eventing.KnativeEventingConfigSourceFactory:-1] (Quarkus Main Thread) K_SINK variable is empty or doesn't exist. Please make sure that this service is a Knative Source or has a SinkBinding bound to it.
2024-02-20 16:35:56,794 27f28debb463 WARN  [io.quarkus.agroal.runtime.AgroalConnectionConfigurer:-1] (Quarkus Main Thread) Agroal does not support detecting if a connection is still usable after an exception for database kind: postgresql
2024-02-20 16:35:56,809 27f28debb463 WARN  [io.quarkus.agroal.runtime.AgroalConnectionConfigurer:-1] (Quarkus Main Thread) Agroal does not support detecting if a connection is still usable after an exception for database kind: postgresql
2024-02-20 16:35:56,811 27f28debb463 WARN  [io.quarkus.agroal.runtime.AgroalConnectionConfigurer:-1] (Quarkus Main Thread) Agroal does not support detecting if a connection is still usable after an exception for database kind: postgresql
2024-02-20 16:35:56,990 27f28debb463 INFO  [org.flywaydb.core.internal.license.VersionPrinter:36] (Quarkus Main Thread) Flyway Community Edition 9.17.0 by Redgate
2024-02-20 16:35:56,990 27f28debb463 INFO  [org.flywaydb.core.internal.license.VersionPrinter:36] (Quarkus Main Thread) See release notes here: https://rd.gt/416ObMi
2024-02-20 16:35:56,991 27f28debb463 INFO  [org.flywaydb.core.internal.license.VersionPrinter:36] (Quarkus Main Thread)
2024-02-20 16:35:57,052 27f28debb463 INFO  [org.flywaydb.core.internal.database.base.BaseDatabaseType:36] (Quarkus Main Thread) Database: jdbc:postgresql://localhost:38067/jobs_service (PostgreSQL 14.8)
2024-02-20 16:35:57,088 27f28debb463 INFO  [org.flywaydb.core.internal.schemahistory.JdbcTableSchemaHistory:36] (Quarkus Main Thread) Schema history table "public"."flyway_schema_history" does not exist yet
2024-02-20 16:35:57,094 27f28debb463 INFO  [org.flywaydb.core.internal.command.DbValidate:36] (Quarkus Main Thread) Successfully validated 7 migrations (execution time 00:00.021s)
2024-02-20 16:35:57,115 27f28debb463 INFO  [org.flywaydb.core.internal.schemahistory.JdbcTableSchemaHistory:36] (Quarkus Main Thread) Creating Schema History table "public"."flyway_schema_history" ...
2024-02-20 16:35:57,150 27f28debb463 INFO  [org.flywaydb.core.internal.command.DbMigrate:36] (Quarkus Main Thread) Current version of schema "public": << Empty Schema >>
2024-02-20 16:35:57,158 27f28debb463 INFO  [org.flywaydb.core.internal.command.DbMigrate:36] (Quarkus Main Thread) Migrating schema "public" to version "2.0.0 - Create Table"
2024-02-20 16:35:57,185 27f28debb463 INFO  [org.flywaydb.core.internal.command.DbMigrate:36] (Quarkus Main Thread) Migrating schema "public" to version "2.0.1 - job details increase job id size"
2024-02-20 16:35:57,195 27f28debb463 INFO  [org.flywaydb.core.internal.command.DbMigrate:36] (Quarkus Main Thread) Migrating schema "public" to version "2.0.2 - job details add fire time col"
2024-02-20 16:35:57,207 27f28debb463 INFO  [org.flywaydb.core.internal.command.DbMigrate:36] (Quarkus Main Thread) Migrating schema "public" to version "2.0.3 - Create Table Management"
2024-02-20 16:35:57,221 27f28debb463 INFO  [org.flywaydb.core.internal.command.DbMigrate:36] (Quarkus Main Thread) Migrating schema "public" to version "3.0.0 - Create Jobs Table V2"
2024-02-20 16:35:57,236 27f28debb463 INFO  [org.flywaydb.core.internal.command.DbMigrate:36] (Quarkus Main Thread) Migrating schema "public" to version "3.0.1 - Migrate Jobs v1 to v2 Table"
2024-02-20 16:35:57,248 27f28debb463 INFO  [org.flywaydb.core.internal.command.DbMigrate:36] (Quarkus Main Thread) Migrating schema "public" to version "3.0.2 - Add Execution Timeout Col"
2024-02-20 16:35:57,256 27f28debb463 INFO  [org.flywaydb.core.internal.command.DbMigrate:36] (Quarkus Main Thread) Successfully applied 7 migrations to schema "public", now at version v3.0.2 (execution time 00:00.112s)
2024-02-20 16:35:58,400 27f28debb463 INFO  [org.kie.kogito.index.addon.ProcessDefinitionRegister:64] (Quarkus Main Thread) No process definitions to register.
2024-02-20 16:35:58,404 27f28debb463 INFO  [org.kie.kogito.jobs.service.management.JobServiceInstanceManager:193] (Quarkus Main Thread) Current Job Service Instance JobServiceManagementInfo[id=kogito-jobs-service-leader, lastHeartbeat=2024-02-20T16:35:58.403Z, token=e0ce6106-7913-4ff4-abe4-0061e040ba0c]
2024-02-20 16:35:58,408 27f28debb463 INFO  [org.kie.kogito.jobs.service.repository.postgresql.PostgreSqlJobServiceManagementRepository:54] (Quarkus Main Thread) get kogito-jobs-service-leader
2024-02-20 16:35:58,427 27f28debb463 INFO  [org.kie.kogito.addon.quarkus.messaging.common.QuarkusKogitoExtensionInitializer:55] (Quarkus Main Thread) Registered Kogito CloudEvent extension
2024-02-20 16:35:58,529 27f28debb463 INFO  [io.quarkus:109] (Quarkus Main Thread) serverless-workflow-project 1.0.0-SNAPSHOT on JVM (powered by Quarkus 3.2.9.Final) started in 16.986s. Listening on: http://<IP_ADDRESS>:8080
2024-02-20 16:35:58,530 27f28debb463 INFO  [io.quarkus:113] (Quarkus Main Thread) Profile dev activated. Live Coding activated.
2024-02-20 16:35:58,530 27f28debb463 INFO  [io.quarkus:115] (Quarkus Main Thread) Installed features: [agroal, cache, cdi, embedded-postgres, flyway, grpc-server, hibernate-orm, hibernate-orm-panache, jackson-jq, jdbc-postgresql, job-http-recipient, kogito-addon-jobs-management-extension, kogito-addon-knative-eventing-extension, kogito-addon-kubernetes-extension, kogito-addon-messaging-extension, kogito-addon-microprofile-config-service-catalog-extension, kogito-addon-process-management-extension, kogito-addon-source-files-extension, kogito-addons-quarkus-data-index-inmemory, kogito-addons-quarkus-jobs-service-embedded, kogito-addons-quarkus-knative-serving, kogito-serverless-workflow, kogito-serverless-workflow-devui, kubernetes-client, narayana-jta, oidc, qute, reactive-pg-client, reactive-routes, rest-client, rest-client-jackson, resteasy, resteasy-jackson, resteasy-multipart, resteasy-mutiny, security, security-properties-file, servlet, smallrye-context-propagation, smallrye-fault-tolerance, smallrye-health, smallrye-openapi, smallrye-reactive-messaging, smallrye-reactive-messaging-http, swagger-ui, vertx, vertx-graphql]

2024-02-20 16:35:58,683 27f28debb463 INFO  [org.kie.kogito.jobs.service.management.JobServiceInstanceManager:154] (vert.x-eventloop-thread-1) SET Leader JobServiceManagementInfo[id=kogito-jobs-service-leader, lastHeartbeat=2024-02-20T16:35:58.683Z, token=e0ce6106-7913-4ff4-abe4-0061e040ba0c]
2024-02-20 16:35:58,688 27f28debb463 INFO  [org.kie.kogito.jobs.service.management.JobServiceInstanceManager:123] (vert.x-eventloop-thread-1) Enabled communication for leader instance
2024-02-20 16:35:58,708 27f28debb463 INFO  [org.kie.kogito.jobs.service.management.JobServiceInstanceManager:104] (vert.x-eventloop-thread-1) Initial leader check completed
2024-02-20 16:35:58,718 27f28debb463 INFO  [org.kie.kogito.jobs.service.scheduler.JobSchedulerManager:135] (vert.x-eventloop-thread-1) Loading scheduled jobs completed !
2024-02-20 16:36:31,543 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:133] (postgres:pid(289)) 2024-02-20 16:36:31.542 UTC [292] LOG:  received fast shutdown request
2024-02-20 16:36:31,543 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:133] (postgres:pid(289)) 2024-02-20 16:36:31.543 UTC [292] LOG:  aborting any active transactions

--
Press [e] to edit command line args (currently ''), [:] for the terminal, [h] for more options>
2024-02-20 16:36:31,624 27f28debb463 WARN  [org.kie.kogito.jobs.service.openapi.JobServiceModelFilter:77] (Shutdown thread) SpecVersion enum schema is not present in the OpenAPI document.
2024-02-20 16:36:31,643 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:133] (pg_ctl:pid(337)) waiting for server to shut down.... done
2024-02-20 16:36:31,643 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:133] (pg_ctl:pid(337)) server stopped
2024-02-20 16:36:31,645 27f28debb463 INFO  [io.zonky.test.db.postgres.embedded.EmbeddedPostgres:391] (postgres-77debbea-3d48-4586-8df0-97dcfdd70da8-closer) 77debbea-3d48-4586-8df0-97dcfdd70da8 shut down postmaster in 00:00:00.112
2024-02-20 16:36:31,705 27f28debb463 INFO  [org.kie.kogito.jobs.service.repository.postgresql.PostgreSqlJobServiceManagementRepository:72] (Shutdown thread) set JobServiceManagementInfo[id=kogito-jobs-service-leader, lastHeartbeat=null, token=null]
2024-02-20 16:36:31,711 27f28debb463 ERROR [org.kie.kogito.jobs.service.management.JobServiceInstanceManager:180] (vert.x-eventloop-thread-4) Error releasing leader [Error Occurred After Shutdown]
2024-02-20 16:36:31,711 27f28debb463 ERROR [org.kie.kogito.jobs.service.management.JobServiceInstanceManager:139] (vert.x-eventloop-thread-4) Shutdown error [Error Occurred After Shutdown]: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: localhost/<IP_ADDRESS>:38067
Caused by: java.net.ConnectException: Connection refused
        at java.base/sun.nio.ch.Net.pollConnect(Native Method)
        at java.base/sun.nio.ch.Net.pollConnectNow(Net.java:672)
        at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:946)
        at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:337)
        at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:334)
        at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:776)
        at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724)
        at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650)
        at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
        at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
        at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
        at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
        at java.base/java.lang.Thread.run(Thread.java:840)

PR job #95 was: FAILURE
Possible explanation: Pipeline failure or project build failure
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/95/display/redirect
See console log:

Console Logs
[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-swf-builderBuild KIE » kogito » main » pullrequest » kogito-images.build-image #1291 completed: FAILURE[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-jobs-service-allinoneBuild KIE » kogito » main » pullrequest » kogito-images.build-image #1294 completed: FAILURE[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-runtime-jvmBuild KIE » kogito » main » pullrequest » kogito-images.build-image #1300 completed: FAILURE[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-swf-devmodeBuild KIE » kogito » main » pullrequest » kogito-images.build-image #1295 completed: FAILURE[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-runtime-nativeBuild KIE » kogito » main » pullrequest » kogito-images.build-image #1289 completed: FAILURE[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-data-index-postgresql[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/95/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

PR job #96 was: FAILURE
Possible explanation: Pipeline failure or project build failure
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/96/display/redirect
See console log:

Console Logs
[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-jobs-service-ephemeralBuild KIE » kogito » main » pullrequest » kogito-images.build-image #1310 completed: FAILURE[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-runtime-jvmBuild KIE » kogito » main » pullrequest » kogito-images.build-image #1306 completed: FAILURE[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-jobs-service-allinoneBuild KIE » kogito » main » pullrequest » kogito-images.build-image #1305 completed: FAILURE[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-data-index-postgresqlBuild KIE » kogito » main » pullrequest » kogito-images.build-image #1303 completed: FAILURE[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-base-builderBuild KIE » kogito » main » pullrequest » kogito-images.build-image #1304 completed: FAILURE[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-data-index-ephemeral[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/96/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

PR job #99 was: FAILURE
Possible explanation: Pipeline failure or project build failure
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/99/display/redirect
See console log:

Console Logs
Failed in branch kogito-swf-devmodeBuild KIE » kogito » main » pullrequest » kogito-images.build-image #1317 completed: FAILURE[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-jobs-service-allinoneBuild KIE » kogito » main » pullrequest » kogito-images.build-image #1319 completed: FAILURE[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-jit-runnerBuild KIE » kogito » main » pullrequest » kogito-images.build-image #1321 completed: FAILURE[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-management-consoleBuild KIE » kogito » main » pullrequest » kogito-images.build-image #1322 completed: FAILURE[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-runtime-nativeBuild KIE » kogito » main » pullrequest » kogito-images.build-image #1318 completed: FAILURE[Pipeline] error[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-base-builderBuild KIE » kogito » main » pullrequest » kogito-images.build-image PR #1745 - kogito-data-index-postgresql: https://github.com/apache/incubator-kie-kogito-images/pull/1745 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/99/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

PR job #106 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/106/display/redirect
See console log:

Console Logs
[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1745 - kogito-jobs-service-allinone: https://github.com/apache/incubator-kie-kogito-images/pull/1745 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-jobs-service-allinone seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1745 - kogito-jobs-service-ephemeral: https://github.com/apache/incubator-kie-kogito-images/pull/1745 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1745 - kogito-base-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1745 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1745 - kogito-runtime-jvm: https://github.com/apache/incubator-kie-kogito-images/pull/1745 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1745 - kogito-management-console: https://github.com/apache/incubator-kie-kogito-images/pull/1745 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1745 - kogito-swf-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1745 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1745 - kogito-swf-devmode: https://github.com/apache/incubator-kie-kogito-images/pull/1745 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1745 - kogito-s2i-builder: https://github.com/apache/incubator-kie-kogito-images/pull/1745 completed: SUCCESS[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/106/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh


Update gas limit to 4700000 in Universal Dapp

Is 4,700,000 the standard amount?

Gas limit is currently 4,712,388. Just picking 4,700,000 to be in line with #91.

Thanks.

@Denton-L the gas limit you have set is not 4700000, but<PHONE_NUMBER>.
It is not a change as simple as that.  The web3 option will run estimateGas and always execute the transaction with the needed gas limit.  The vm option doesn't have this, but an arbitrarily high limit.
I have some changes which make this configurable via the UI. I think that should be the proper way to resolve it.

@axic Do your changes allow a person to specify/override the gas sent in a transaction? /cc @simondlr

Sorry, @axic... My bad...

@redsquirrel @Denton-L fixed it in #125 :)
We could go with 4,7M as a default, but that is the block gas limit, which depends on the miners.


can flambe save all tensorboard plots to a specified dir?

Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
I'd like a tb_plots_save_dir option in the Flambe config; if given, the runner saves all TensorBoard plots to that dir.
Describe alternatives you've considered
Writing a tool to do this myself.
Additional context
Erm, no.

Is the current output directory not sufficient? Can you provide a use case for this feature?

You want to delete the output after the run terminates, but keep the plots!

Where can these plots be found in the output directory, currently?

Ah i see. I don't think this is supported in Tensorboard: https://github.com/tensorflow/tensorboard/issues/32.
We plan on having a report mechanism is Flambé to create plots and whatnot that will not depend on tensorboard. It's in the agenda for Flambe 0.5, and will likely cover your use case.

Closing for now :)


Undefined reference to __imp__wassert when linking statically against raylib 4.5 on Windows

Issue description
When I link my project statically against raylib 4.5 (libraylib.a), I get a bunch of errors:
C:\Users\vtere\Desktop\umplot>gcc -O3 -DUMKA_STATIC umplot.c -o umplot_windows.umi -shared -Wl,--dll -static-libgcc -static -lumka_static -lraylib -L. -lkernel32 -luser32 -lgdi32 -lwinmm
.\libraylib.a(rglfw.o):rglfw.c:(.text+0x160b): undefined reference to `__imp__wassert'
.\libraylib.a(rglfw.o):rglfw.c:(.text+0x1982): undefined reference to `__imp__wassert'
.\libraylib.a(rglfw.o):rglfw.c:(.text+0x19d9): undefined reference to `__imp__wassert'
.\libraylib.a(rglfw.o):rglfw.c:(.text+0x19f5): undefined reference to `__imp__wassert'
.\libraylib.a(rglfw.o):rglfw.c:(.text+0x1a11): undefined reference to `__imp__wassert'
.\libraylib.a(rglfw.o):rglfw.c:(.text+0x1a5d): more undefined references to `__imp__wassert' follow
collect2.exe: error: ld returned 1 exit status

The problem doesn't happen with raylib 4.0.
 I'm quite certain the issue does not lie with raylib
Having the output of gcc --version would be useful too.

The best way to ensure a library will work is to build it yourself

@vtereshkov GCC 10 fliped some defaults (specially -fcommon to -fno-common). That caused some problems on another project I was working on when I upgraded to GCC 10. Perhaps it could be the case here.

It seems a compiler-related issue other than raylib itself, I'm closing this issue.


Quick way to create highlights from editor selection

Hi,
I would love to have something similar to notepad++, that can create a syntax highlight by right-clicking on a selection and choosing a style (See image below).
I can try to create a PR for it, if you'd likely accept it.

Hi @elazarcoh, yes please do work on a PR.
If it's to be close to the Notepad++ implementation it will need a new set of default styles adding as well.
I have other ideas in mind for this extension, plus some other requests, some of which are beyond my skills. (I'm maintaining this with little JS experience; I'm not the original author.) So I'd welcome being able to ask you for some advice/tips on those, as it sounds like you're confident enough to be making a fairly significant PR.


[Flow Aggregator] Fix template ID error in IPFIX exporter

The template ID is only available after the exporter has been initialized.
With this fix, we avoid the following error for the first data record to be exported:
error when sending IPFIX record: error when doing sanity check:process:
templateID 0 does not exist in exporting process

/test-all


Cut & Paste overwrote the directory

When I was cutting a directory to paste it in a different location, instead of merging the two folders together, it overwrote my original files and I was left with the new files

I've also tested it with copy & paste with the same results.  If the two folders have the same name, "Generate new name" creates a separate folder, but "Replace existing item" will overwrite anything in the destination folder with the current items.  I hope that helps :)

@banoctopus The replace existing item option is not a merge option so this is the expected behavior. We are looking at adding a merge option though. Merging with #4601.


NPE trying to access resources when running older code

When taking code compiled for 1.3.2 that accesses a resource file I get an NPE when running it with 1.3.3-SNAPSHOT. Running it with 1.3.2 works as expected.

@FroMage does this count as a regression DYT?

Just tested it and could not find any NPE: it worked.


XSS Vulnerability

XSS Vulerability detected:
I tried using Inject an XSS query in simple MDE, By creating a link as following.
[XSS](javascript:alert%28sessionStorage.clear%28%29%29)
and it works as following:
This converted into a link, that clears users sessionStorage in this example while clicking

you should be setting your marked parse options to sanitize

Hi @dantrevino
I did not find any configuration to set it equal to sanitize. Please let me know how to mark parse options to sanitize ?. I am looking here for configuration https://github.com/sparksuite/simplemde-markdown-editor#configuration

Until this is fixed, you can enable the sanitize marked option.
You can do this in the last version, which is not in Master branch, so you need to build simplemde files from sources:
git clone https://github.com/sparksuite/simplemde-markdown-editor.git
cd simplemde-markdown-editor
npm install --save-dev
gulp

Note that as I write this text, the current gulpfile doesn't support gulp4. If my pull request to fix this is not merged as the time you read this, you must edit the gulpfile too (just see the PR diff).
Then, copy simplemde-markdown-editor/dist/simplemde.min.css and simplemde-markdown-editor/dist/simplemde.min.js to your project.
Finally, set sanitize rule to true:
var simplemde = new SimpleMDE(
     {
        renderingConfig: {
            markedOptions: {
                sanitize: true
            }
        },
        element: $('#articleContent')[0]
    });