segmentation fault

Describe the bug
Hello, I have been trying to use the pycoral-2.13whl and the tflite_runtime-2.13whl with python3.11, and have been experiencing some issues as when I run the model I compiled myself or any of the examples from the pycoral website I get a segmentation fault, (env-pycoral) julien@raspberrypidrone:~/TensorFlow $ python3 tflitetest.py
Segmentation fault
To Reproduce
Steps to reproduce the behavior:

Download pyenv then activate a virtual environment with python3.11.2, Follow the steps to download the libedgetpu library on the pycoral website, 1: Install the Edge TPU runtime
download the tflite_runtime-2.13.0-cp311-cp311-linux_aarch64.whl, then download pycoral-2.13.0-cp311-cp311-linux_aarch64.whl
Install what else is needed like opencv-python, matplotlib, etc
run the bird example on the website or other models that interact with tflite/edgetpu

Expected behavior
When using tflite2.5/its pycoral equivalent it would work fine providing how long it took, what bird it is, or  if im using my own model it would draw a bounding box over me, but switching to this newer version gives the error
Desktop (please complete the following information):

Raspberrypi5 8gb of ram
aarch64
Python 3.11.2
Debian GNU/Linux 12 (bookworm)

Additional context
Before I start I am pretty new to this, so if I did not include something please let me know. Running it with gdb shows this (Thread 1 "python" received signal SIGSEGV, Segmentation fault.
0x00007fffd6c14464 in tflite::Subgraph::OpInit(TfLiteRegistration const&, char const*, unsigned long) ()
from /home/julien/.pyenv/versions/3.11.2/envs/env-pycoral/lib/python3.11/site-packages/tflite_runtime/_pywrap_tensorflow_interpreter_wrapper.cpython-311-aarch64-linux-gnu.so)

also using the bt command with gdb gives the following: (gdb) bt
#0  0x00007fffd0124464 in tflite::Subgraph::OpInit(TfLiteRegistration const&, char const*, unsigned long) ()
from /home/julien/venv-pycoral/lib/python3.11/site-packages/tflite_runtime/_pywrap_tensorflow_interpreter_wrapper.cpython-311-aarch64-linux-gnu.so
#1  0x00007fffd0127cb4 in tflite::Subgraph::AddNodeWithParameters(std::vector<int, std::allocator > const&, std::vector<int, std::allocator > const&, std::vector<int, std::allocator > const&, char const*, unsigned long, void*, TfLiteRegistration const*, int*) ()
from /home/julien/venv-pycoral/lib/python3.11/site-packages/tflite_runtime/_pywrap_tensorflow_interpreter_wrapper.cpython-311-aarch64-linux-gnu.so
#2  0x00007fffd0128084 in tflite::Subgraph::ReplaceNodeSubsetsWithDelegateKernels(TfLiteRegistration, TfLiteIntArray const*, TfLiteDelegate*) ()
from /home/julien/venv-pycoral/lib/python3.11/site-packages/tflite_runtime/_pywrap_tensorflow_interpreter_wrapper.cpython-311-aarch64-linux-gnu.so
#3  0x00007fffd0128480 in tflite::Subgraph::ReplaceNodeSubsetsWithDelegateKernels(TfLiteContext*, TfLiteRegistration, TfLiteIntArray const*, TfLiteDelegate*) ()
from /home/julien/venv-pycoral/lib/python3.11/site-packages/tflite_runtime/_pywrap_tensorflow_interpreter_wrapper.cpython-311-aarch64-linux-gnu.so
#4  0x00007fffd024be24 in ?? () from /home/julien/coral/pycoral/libedgetpu_bin/throttled/aarch64/libedgetpu.so.1
#5  0x00007fffd012924c in tflite::Subgraph::ModifyGraphWithDelegateImpl(TfLiteDelegate*) ()
from /home/julien/venv-pycoral/lib/python3.11/site-packages/tflite_runtime/_pywrap_tensorflow_interpreter_wrapper.cpython-311-aarch64-linux-gnu.so
#6  0x00007fffd0129f64 in tflite::Subgraph::ModifyGraphWithDelegate(TfLiteDelegate*) ()
from /home/julien/venv-pycoral/lib/python3.11/site-packages/tflite_runtime/_pywrap_tensorflow_interpreter_wrapper.cpython-311-aarch64-linux-gnu.so
#7  0x00007fffd0119d94 in tflite::impl::Interpreter::ModifyGraphWithDelegateImpl(TfLiteDelegate*) ()
from /home/julien/venv-pycoral/lib/python3.11/site-packages/tflite_runtime/_pywrap_tensorflow_interpreter_wrapper.cpython-311-aarch64-linux-gnu.so
#8  0x00007fffcfe32f70 in tflite::interpreter_wrapper::InterpreterWrapper::ModifyGraphWithDelegate(TfLiteDelegate*) ()
from /home/julien/venv-pycoral/lib/python3.11/site-packages/tflite_runtime/_pywrap_tensorflow_interpreter_wrapper.cpython-311-aarch64-linux-gnu.so
I could be wrong but maybe the seg fault is because of #4  0x00007fffd024be24 in ?? () from /home/julien/coral/pycoral/libedgetpu_bin/throttled/aarch64/libedgetpu.so.1, I will look for a more compatible version between the tflite.whl and libedgetpu1

hey, I got it working, so installing this version of libedgetpu gets rid of the seg fault and it runs super fast! https://github.com/feranick/libedgetpu/releases/download/v16.0tf2.13.1/libedgetpu1-std_16.0tf2.13.1.ubuntu22.04_arm64.deb


virtcontainers: storage: Rework resource storage

This PR takes care of reworking the storage by:

Adding a no-op implementation to facilitate unit testing.
Separating filesystem implementation from the resourceStorage interface declaration.

Fixes #632
Fixes #633

Split from #623

LGTM.
Is this some kind of preparation for "storage plugin"?


flow-resolvers throw errors for async resolver functions

Describe the bug
use flow-resolvers plugin and apply auto generated type to resolvers(async function), and flow type check will throw error: Could not decide which case to select, since case 1 [1] may work but if it doesn't case 2 [2] looks promising too. To fix add a type annotation to async return [3]. [speculation-ambiguous]
To Reproduce
Steps to reproduce the behavior:

I tried to use live sandbox and add my code, but turns out the codesandbox doesn't even support flow type, so I wasn't able to reproduce in the codesandbox. see https://github.com/codesandbox/codesandbox-client/issues/668
But this bug is pretty easy to reproduce, any random async resolver function will throw this error:

My GraphQL schema:

  type Query {
    info: String!
  }

My GraphQL operations:

const resolvers:Resolvers<> = {
  Query: {
    async info() {
      return 'Hello World!';
    }
  },
};

My codegen.yml config file:

schema: schema
documents: null
generates:
  src/generated/types.js:
    plugins:
      - "flow"
      - "flow-resolvers"

Expected behavior
I expect the resolver type would work for async function or non async function. But currently, all async function will have type error Could not decide which case to select, since case 1 [1] may work but if it doesn't case 2 [2] looks promising too. To fix add a type annotation to async return [3]. [speculation-ambiguous]
Environment:

OS: linux/mac
"@graphql-codegen/cli": "1.17.0",
"@graphql-codegen/core": "^1.5.0",
"@graphql-codegen/flow": "1.17.0",
"@graphql-codegen/flow-resolvers": "1.17.7",
NodeJS: 10.16.0

Additional context
Check a minimum repo of this Flow Type error: Try Flow
I suspect the issue is: we wrap the type with Promise once here and wrap the return type with Promise again here, which is unnecessary, and makes the flow broke.

Figured it out myself. Thanks. close the issue.


Cannot load auth plugin written for 0.9.3 in 0.10.0

With the new plugin architecture, a custom-written authentication plugin that was working flawlessly under 0.9.3 stopped working in 0.10.0. I modified the plugin so as to include the etc/plugin.config configuration file and imported it according to the wiki's instructions, but it just doesn't work. Do I need to modify anything in the Erlang code itself? Did the hooks change?
When I run bin/emqttd console I get
Hi!
18:39:34.583 [info] started Apps: [emqttd_auth_custom]
18:39:34.583 [info] load plugin emqttd_auth_custom successfully

being that Hi! is written by the plugin on init/1. However, when I try to connect to the broker, the authentication tokens that used to work do not work... It seems that the plugin isn't being used for authentication. How can I make it work?

Any error logs when authentication with your plugin?

在 2015年8月21日，上午1:49，Bruno M. Custódio<EMAIL_ADDRESS>写道：
With the new plugin architecture, a custom-written authentication plugin that was working flawlessly under 0.9.3 stopped working in 0.10.0. I modified the plugin so as to include the etc/plugin.config configuration file and imported it according to the wiki's instructions, but it just doesn't work. Do I need to modify anything in the Erlang code itself? Did the hooks change?
When I run bin/emqttd console I get
Hi!
18:39:34.583 [info] started Apps: [emqttd_auth_custom]
18:39:34.583 [info] load plugin emqttd_auth_custom successfully
being that Hi! is written by the plugin on init/1. However, when I try to connect to the broker, the authentication tokens that used to work do not work... It seems that the plugin isn't being used for authentication. How can I make it work?
—
Reply to this email directly or view it on GitHub https://github.com/emqtt/emqttd/issues/254.

No, nothing is printed in the logs.
On Fri, Aug 21, 2015, 01:54 Feng Lee<EMAIL_ADDRESS>wrote:

Any error logs when authentication with your plugin?

在 2015年8月21日，上午1:49，Bruno M. Custódio<EMAIL_ADDRESS>写道：
With the new plugin architecture, a custom-written authentication plugin
that was working flawlessly under 0.9.3 stopped working in 0.10.0. I
modified the plugin so as to include the etc/plugin.config configuration
file and imported it according to the wiki's instructions, but it just
doesn't work. Do I need to modify anything in the Erlang code itself? Did
the hooks change?
When I run bin/emqttd console I get
Hi!
18:39:34.583 [info] started Apps: [emqttd_auth_custom]
18:39:34.583 [info] load plugin emqttd_auth_custom successfully
being that Hi! is written by the plugin on init/1. However, when I try
to connect to the broker, the authentication tokens that used to work do
not work... It seems that the plugin isn't being used for authentication.
How can I make it work?
—
Reply to this email directly or view it on GitHub <
https://github.com/emqtt/emqttd/issues/254>.

—
Reply to this email directly or view it on GitHub
https://github.com/emqtt/emqttd/issues/254#issuecomment-133232463.

Even if I use the following inside the plugin, nothing is printed when I
try to authenticate and the connection is refused:
check(_, _, _) ->
  io: format("check was called"),
  ok.

On Fri, Aug 21, 2015, 02:48 Bruno Miguel Custódio<EMAIL_ADDRESS>wrote:

No, nothing is printed in the logs.
On Fri, Aug 21, 2015, 01:54 Feng Lee<EMAIL_ADDRESS>wrote:

Any error logs when authentication with your plugin?

在 2015年8月21日，上午1:49，Bruno M. Custódio<EMAIL_ADDRESS>写道：
With the new plugin architecture, a custom-written authentication
plugin that was working flawlessly under 0.9.3 stopped working in 0.10.0. I
modified the plugin so as to include the etc/plugin.config configuration
file and imported it according to the wiki's instructions, but it just
doesn't work. Do I need to modify anything in the Erlang code itself? Did
the hooks change?
When I run bin/emqttd console I get
Hi!
18:39:34.583 [info] started Apps: [emqttd_auth_custom]
18:39:34.583 [info] load plugin emqttd_auth_custom successfully
being that Hi! is written by the plugin on init/1. However, when I try
to connect to the broker, the authentication tokens that used to work do
not work... It seems that the plugin isn't being used for authentication.
How can I make it work?
—
Reply to this email directly or view it on GitHub <
https://github.com/emqtt/emqttd/issues/254>.

—
Reply to this email directly or view it on GitHub
https://github.com/emqtt/emqttd/issues/254#issuecomment-133232463.

It seems like the plugin is loaded but not being called on auth.
On Fri, Aug 21, 2015, 02:54 Bruno Miguel Custódio<EMAIL_ADDRESS>wrote:

Even if I use the following inside the plugin, nothing is printed when I
try to authenticate and the connection is refused:
check(_, _, _) ->
  io: format("check was called"),
  ok.

On Fri, Aug 21, 2015, 02:48 Bruno Miguel Custódio <
<EMAIL_ADDRESS>wrote:

No, nothing is printed in the logs.
On Fri, Aug 21, 2015, 01:54 Feng Lee<EMAIL_ADDRESS>wrote:

Any error logs when authentication with your plugin?

在 2015年8月21日，上午1:49，Bruno M. Custódio<EMAIL_ADDRESS>写道：
With the new plugin architecture, a custom-written authentication
plugin that was working flawlessly under 0.9.3 stopped working in 0.10.0. I
modified the plugin so as to include the etc/plugin.config configuration
file and imported it according to the wiki's instructions, but it just
doesn't work. Do I need to modify anything in the Erlang code itself? Did
the hooks change?
When I run bin/emqttd console I get
Hi!
18:39:34.583 [info] started Apps: [emqttd_auth_custom]
18:39:34.583 [info] load plugin emqttd_auth_custom successfully
being that Hi! is written by the plugin on init/1. However, when I try
to connect to the broker, the authentication tokens that used to work do
not work... It seems that the plugin isn't being used for authentication.
How can I make it work?
—
Reply to this email directly or view it on GitHub <
https://github.com/emqtt/emqttd/issues/254>.

—
Reply to this email directly or view it on GitHub
https://github.com/emqtt/emqttd/issues/254#issuecomment-133232463.

Please check if the auth_mod is registered successfully. For example in emqttd_plugin_mysql:
ok = emqttd_access_control:register_mod(auth, emqttd_auth_mysql, {AuthSql, HashType}),

Or dump all the auth modules on console:
(emqttd@<IP_ADDRESS>)1> emqttd_access_control:lookup_mods(auth).
[{emqttd_auth_anonymous,[]}]

OK, I will do so in a few hours time and post back the results. Thanks for
taking the time to investigate :-)
On Fri, Aug 21, 2015, 03:04 Feng Lee<EMAIL_ADDRESS>wrote:

Please check if the auth_mod is registered successfully. For example in
emqttd_plugin_mysql:
ok = emqttd_access_control:register_mod(auth, emqttd_auth_mysql, {AuthSql, HashType}),
Or dump all the auth modules on console:
(emqttd@<IP_ADDRESS>)1> emqttd_access_control:lookup_mods(auth).
[{emqttd_auth_anonymous,[]}]
—
Reply to this email directly or view it on GitHub
https://github.com/emqtt/emqttd/issues/254#issuecomment-133245991.

Here's what I get from emqttd_access_control:lookup_mods(auth).:
(emqttd@<IP_ADDRESS>)2> emqttd_access_control:lookup_mods(auth).
[{emqttd_auth_custom,{state,<<"Test!">>}}]

The module seems to be loading OK. However, when I try to connect to the broker it doesn't seem to be called.

@bmcustodio, could you zip your plugin and send me by email if it does not contain confidential information?

@erylee after a few hours struggling with this I managed to get it working. I'm still not quite sure what was wrong, though --- anyway, I changed the plugin's structure to match emqttd_plugin_mysql and it seems to be working.
The only thing that I'm missing is how to make the plugin active by default, as on a fresh build it will only become active after I run emqttd_plugins:load(emqttd_auth_custom).. Am I missing something?

Two ways:

./bin/emqttd_ctl plugins load emqttd_plugin_yours, then the plugin will become active.

or write your plugin name to ./data/loaded_plugins file directly, for example:

emqttd_dashboard.
emqttd_plugin_yours.

在 2015年8月21日，下午9:32，Bruno M. Custódio<EMAIL_ADDRESS>写道：
@erylee https://github.com/erylee after a few hours struggling with this I managed to get it working. I'm still not quite sure what was wrong, though --- anyway, I changed the plugin's structure to match emqttd_plugin_mysql and it seems to be working.
The only thing that I'm missing is how to make the plugin active by default, as on a fresh build it will only become active after I run emqttd_plugins:load(emqttd_auth_custom).. Am I missing something?
—
Reply to this email directly or view it on GitHub https://github.com/emqtt/emqttd/issues/254#issuecomment-133425891.


One of two TV not turning on

Please excuse my errors in this request, I'm new at this, well and old new, it been quite a few years since I did and network configuring...
I have installed the home bridge-smartthing-tv plugin and it installed ok. I added two Samsung TV's of different age.  The IOS Smartthings app on my phone works flawlessly.  I added them to HomeKit, the older of the two works well turns off/on/change input etc.  The second a QA65Q800TAWXXY model, can turn off and changes inputs but will NOT turn ON, but will turn off.
Is there something I've missed, like a WOL or some other permission ?  I've deleted and re-added without any change.    The Samsung access key seems correct, no errors I can see.
Is there a configurable delay between commands anywhere?
I have not seen any popup on the TV to authorise, apart from bluetooth direct from my phone.
There didn't deem to be anything in the log file except for an unsupported Air Purifier, also in SmartThings.  There we a few input errors, because I didn't change the config file much from the example, but I didn't change anything as one worked and the other didn't.
Logs: Attached.
config-.json attached.
config-json.txt
LogFile-RW .txt

I'm not really sure what is happening but your config looks good. There should not be any permissions issues and even if there was any permission issue your other TV should not work too.
WOL will be used as soon as there is a MAC address set in your device mappings. So because you set one it should be used.
Could you please try to enable Debug log level and post your log file again. So I can have a closer look at what is happening. Currently I can not reproduce the problem as I only have one TV available and not your specific model. To enable Debug log level simply go to Homebridge settings in config UI and enable Homebridge Debug Mode in startup options.

I've attached a full copy of the log files after a Pi reboot and then a home bridge restart.  Other junk is still there...........
I can see the WOL in the log. The TV "Living TV" is the problem one, I have to clean up the names as they got mixed up some how.  At the end of the log I have toggled the ON from HomeBridge a few times, then turned it on from the SmartLife app, then turned it off.  It seems like Homebridge sends the ON but does not get a reply so turn the button off again.  When Smartlife turns it on homebridge see the state go on, correctly, from then it can then turn it off.
Also, how do i remove the inputs with error (compatibility i think)
homebridge.log-5.txt

Thanks for the quick response!
I have created a new release where the success/failure of the wake-on-lan functionality will be logged. Please try to use this release and check if the log says the wake-on-lan failed. If this continues to happen please disable wake-on-lan functionality by removing the mac address of the TV from the device mapping and try again.
The wake-on-lan functionality was just a bugfix for me because my TV did not turn on using the SmartThings API. Maybe SmartThings API works for your TV.

Thanks for all the help, attached is a log file, as requested.
Look from 1:54 pm, that is where I selected the on from home bridge, saw the indication come on for a while then go off, TV nothing.  Turned the TV on from Smartlife, then the status in homebriddge starting working .
Regards, Richard.....
homebridge.log-7.txt

It seems the wake-on-lan command was sent successfully but the TV did somehow not react to it. Have you tried sending a wake-on-lan command from outside the plugin so that we can be sure the TV is capable of handling it? Is the TV connected over wifi - sometimes wake-on-lan does not work very well over wifi?
But when turning on the TV using SmartThings is working for you, you could try to remove the mac address from the device mappings configuration entry. As I said you should only need the wake-on-lan functionality if the SmartThings API is not working for you. As it seems to work for your TV you can disable it (by removing the mac address) and you should be fine.

Thanks heaps for your time, I have attached another log file after deleting the mac address via the UI config.  Then restarted.  When accessory of the TV returned the inputs were incorrect.
At about 13:10pm I toggled the living_tv on form the HomeBridge accessory display.  The TV came on (Hooray) however the status feedback soon went off, the TV remained ON.  I toggled the state in Smartthings app, the TV indication came on again everywhere.
At about 13:16 the TV status went off again even though the TV remained on.  The status went off again about 13:16, set on again.
I restarted the bridge again, the status was off and a start from HK change the status and went off again ~13:35 and the inputs now show the correct input names and changed from home bridge.
My observations:

Living TV can now be turned ON from the HB or HK or SmartThings,
2 restarts required to get inputs to show correctly for Living TV in HB.
Status indication (feedback)initially correct but fail after 2 to 3 minutes.
2nd TV still working correctly.  BTW I already new that the second TV WOL will only functions with a hardwired ethernet connection, it will not work with wifi.
The second accessory for the TV Mute/Vol ? only seems to mute and will not unmute and % display always 0%
The log file shows a lot of failed PINGS, with only 1 attempt each. (100% packet loss)
There seems to be a lot of pings with the same (seconds) time stamp, this seems like a high number of commands per second, I was under the impression a shot delay was required between PINGS, >200ms.?

Thanks for your help much appreciated, I'll add a donation when I can find out how..:)
regards,
Richard.....
RJW-log-3.txt

Oops thanks for reopening.
late update, I tried WOL and the tv turned on every time even after hours off.
I tried PING, it seems strange, sometimes it responded, especially when I pinged the whole subnet, ( slow rate) but usually failed when I pinged on a regular time.  I don’t understand it’s behavior, so I try resetting the TV tomorrow,
I’m a little busy, so I may not get time early, I’ve got a few things to do before my grandson arrives from the UK Thursday.…
Seems like it may be my end, let me know you donation link and I’ll send a little something.

I managed to do some pinging and noticed:

I started pinging the TV at about 800ms constant rate.
No response from TV at first.
De-Powering the TV and back on again, pinging was successful at about 5ms > 15ms
Watched it start a constant alive results for a few minutes 0% lost.
I turned the TV off.
Then restarted the bridge.
When HB got to the point of adding the inputs, the pinging stopped responding completely.
I turned the TV back on and pinging response restarted with constant alive.
I tried this a few times and with the TV off (in standby) a restart of the bridge would crash the TV, no response.
The TV when turned back on, it started responding again, but the TV screen started
homebridge.log-9.txt
at the cold start screen, not the warm start. Also the TV changes to the inputs the plugin adds, E.G Apple TV+, Spotify are put on the screen one after the other until it got though all the inputs (that I don't want).
The log file did not ever show an alive status even though I was getting a constant reply to my continuous ping, from a different station.

It seems like my TV doesn't like the plugin?
R
Regards,
Richard.....

This sounds really strange.
Have you tried removing the IP address from the config so the SmartThings API is used for checking the alive state?
The changes of the inputs are needed to check which applications are installed. If you don't need the applications you can simply disable this feature from the config. Maybe this even causes your TV to stop responding to the plugin.

Sorry about the slow reply, I've been away with overseas visitors.
I have removed the IP from the problem TV and it is working, great!  I have noticed sometime after a restart of the bridge I need to leave it alone for quite  while and it eventually reflects the correct status of both TV.
Thanks heaps and keep up the great work.  I'll look again for the donate link.
Regards,
Richard.....


ENYO-3326: Support accessibilityPreHint

The accessibilityPreHint is neccessary for reading a hint message before
control's content or aria-lable.
https://jira2.lgsvl.com/browse/ENYO-3326
Enyo-DCO-1.1-Signed-off-by: Bongsub Kim<EMAIL_ADDRESS>

Closing PR as jira has been closed


Update tombstones.md (format of tombstone)

I think a ref should be an unsigned value.
And according to tombstones.go (1) and tombstones.go (2), you can see ref is unsigned.

Thanks!


Update Dockerfile and add docker-compose

This should streamline the Docker initialization process since we can now
use the skinny Alpine linux base image for Ruby 2.4.4 and we really shouldn't
need to bend over backwards to install Node.js since all we rely on it for is
Yarn which has its own Alpine (apk) package.
Also extracted the boot stuff into a Procfile that foreman (or Docker) can
consume.

Now we have to figure out the Google OAuth issue when first loading the app up.

Hmm that's weird. Granted, I've yet to get my non-docker local setup to work with Google. I probably have the credentials setup wrong. Happy to help once I get it sorted out!

@olivierlacan I just got my credentials working and google oauth is working as expected within docker. Might be a ENV config issue?

@joeltaylor Oh no, I meant pre-configuration we shouldn't try to ping Google with fake creds. Its the .env defaults that shouldn't exist.


Signature verification failed

Hi @dmkit ,
I just started learning PhalconPHP and decided to create a simple API, using jwt auth.
I can generate the token  without any problem, but when I try to access a protected route I always have a "Signature verification failed". I went on https://jwt.io/#debugger and pasted my token and my secret and it verified properly.
Any help appreciated!
Here is my index:
<?php

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

use Dmkit\Phalcon\Auth\Middleware\Micro as AuthMicro;
use Phalcon\Config\Adapter\Ini as ConfigIni;
use Phalcon\Db\Adapter\Pdo\Mysql as PdoMysql;
use Phalcon\Di\FactoryDefault;
use Phalcon\Http\Response;
use Phalcon\Loader;
use Phalcon\Mvc\Micro;
use Phalcon\Mvc\Micro\Collection as MicroCollection;

// Use Loader() to autoload our model
$loader = new Loader();
$loader->registerNamespaces([
    "App\Controller" => __DIR__ . "/../controllers/",
    "App\Model" => __DIR__ . "/../models/",
]);

$loader->register();

$di = new FactoryDefault();
$config = new ConfigIni(__DIR__ . "/../config.ini");

// Set config
$di->set("config", function () use ($config) {
    return $config;
});

// Set up the database service
$di->set("db", function () {
    return new PdoMysql([
        "host" => "localhost",
        "username" => "...",
        "password" => "...",
        "dbname" => "...",
    ]);
});

$app = new Micro($di);
$auth = new AuthMicro($app);

/* Registering routes for each controller */
$test = new MicroCollection();
$test->setHandler('App\Controller\TestController', true);
$test->setPrefix('/tests');
$test->get('/', 'list');
$test->get('/{id:[0-9]+}', 'get');

$user = new MicroCollection();
$user->setHandler('App\Controller\UserController', true);
$user->setPrefix('/users');
$user->post('/token', 'token');

$app->mount($test);
$app->mount($user);

$app->handle();

The config.ini is the one in the README with just this line added:
ignoreUri[] = /users/token:POST
And the method used to generate the token:
    public function token()
    {
        $response = new Response();
        $data = [
            'success' => false,
        ];
        $content = $this->request->getJsonRawBody();

        if (property_exists($content, "username") && property_exists($content, "password")) {
            $phql = "SELECT * FROM " . User::class . " WHERE username = :username:";
            $user = $this->modelsManager->executeQuery($phql, [
                "username" => $content->username,
            ])->getFirst();

            if ($user && $user instanceof User) {
                if (password_verify($content->password, $user->getPassword())) {
                    $payload = [
                        'sub' => $user->getId(),
                        'email' => $user->getEmail(),
                        'username' => $user->getUsername(),
                        'role' => 'admin',
                        'iat' => time(),
                    ];
                    $token = $this->auth->make($payload);

                    $data = [
                        'success' => true,
                        'token' => $token,
                    ];
                }
            }
        }

        $response->setJsonContent($data);

        return $response;
    }

I'm working with PHP 7.0 and PhalconPHP 3.2.0.
Did I miss something?

Could you paste the config you have for the JWT AUTH? You can replace the secret key with something else :)

Didn't get a feedback. Closing this one out....


Running scheduled job on Saturn Cloud fails

Hi,
I set up following your instructions here on github and got the URLS unblocked as described. Ran it and it worked but every time it gets to a scheduled run time it hangs and errors then fails to complete part way through the calculating amount to charge (not that I am actually using that part actively).
Any suggestions?


Extend build_feature_matrix_from_archive to handle heat modeling files

Add initial logic and unit test for modifying build_feature_matrix to handle wps files for AtmoML. Follow-up PRs will address:

setting up the appropriate matrix transforms on the WPS variables that are in-scope for ML training
writing to metastore

@waltaskew How do I fix the test run in the CI pipeline? I think it's complainign about the missing gcloud creds. The test suite runs successfully locally.

@waltaskew How do I fix the test run in the CI pipeline? I think it's complainign about the missing gcloud creds. The test suite runs successfully locally.

It looks like it's failing to missing dependencies:
ValueError: found the following matches with the input file in xarray's IO backends: ['h5netcdf']. But their dependencies may not be installed, see:

it'll then try to report that error to GCP
https://github.com/UrbanSystemsLab/climateiq-cnn/blob/fc3e8c1d0856e48f0895e0b386af6fc475e46791/usl_pipeline/cloud_functions/main.py#L107
where it's presumably missing credentials
You should mock the error reporter so it doesn't actually hit GCP, or else test code paths not wrapped by _retry_and_report_errors
https://github.com/UrbanSystemsLab/climateiq-cnn/blob/fc3e8c1d0856e48f0895e0b386af6fc475e46791/usl_pipeline/cloud_functions/main.py#L43

@waltaskew How do I fix the test run in the CI pipeline? I think it's complainign about the missing gcloud creds. The test suite runs successfully locally.

It looks like it's failing to missing dependencies:
ValueError: found the following matches with the input file in xarray's IO backends: ['h5netcdf']. But their dependencies may not be installed, see:

it'll then try to report that error to GCP
https://github.com/UrbanSystemsLab/climateiq-cnn/blob/fc3e8c1d0856e48f0895e0b386af6fc475e46791/usl_pipeline/cloud_functions/main.py#L107
where it's presumably missing credentials
You should mock the error reporter so it doesn't actually hit GCP, or else test code paths not wrapped by _retry_and_report_errors
https://github.com/UrbanSystemsLab/climateiq-cnn/blob/fc3e8c1d0856e48f0895e0b386af6fc475e46791/usl_pipeline/cloud_functions/main.py#L43

Done and done - thanks Walt. Build is passing now


WIP: left right mavigation drawer created

Summary of PR
Left and Right drawer added (discord like animation)
Tests for unexpected behavior

none_whatsoever

Time spent on PR
~ 1 week
Linked issues
Fix #

Currently having an issue with toggleDrawer with left drawer. It always toggles right drawer currently.

Hey @har2008preet, since requirements have changed, I'm going to close this. If you do get a chance and want to get involved again, please reach out, we'd love to have you!


Add a new, more restrictive mode to the Forge

Hi, first and foremost I want to say thank you for not only maintaining the project but working on new features for TQVault, the new search bar and TQforge were pleasant surprises for me, that I have been internally complaining there lack for since the original tool's conception.
I have a few suggestions that would benefit the user experience:

Add magical, rare, epic and legendary to the list of field boxes in the "Highlight Items having" filter. So far it has everythign else, item types but no rarity.

For the TQforge, add a "MI mode", what this will do will only allow the item being forged to accept prefix/sufix from the same Monster Infrequent item.

Reason for this? Even with Strict mode, users can unknowningly grant them items that cannot exist in the game. The "strict" mode parameters only govern item type as the only rule on what can be allowed.
for example, you can give a Ice scale helm 'Of the tinkerer', even though this is an impossible item combination to obtain in the game. Act 4 items cannot drop with Of the Tinkerer that is exclusive to Act 5. Another example, a INT helmet with 'Of the magus' can be given to a STR helmet, but this is also impossible by game rules since that suffix only appears on INT head armor.
There are many impossible combinations, even for people that want to use it "legitimately", an MI mode would mean items that drop from ingame would be used to build desired items people want to farm for.

Add an opt-in choice, when using an item for it's Prefix/Suffix to upgrade an item, it gets sacrificed (deleted). (imo to not prevent user error would have this somewhere in configure, it could also give a prompt warning like deleting regular items from vault before doing so just for safe measure)

I'm sorry for ranting. Just want to help improve the feature for accessibility to as many people. also want to apologize on behalf of any immature players that demand you remove the feature because they cannot control their own urges to use the system in a justified manner, or not use it at all.

@EtienneLamoureux i think you can close this one.
@mmmilord your ideas are in the 4.2 release


Fixed example 10

Closes #???
Description
Example used functions in the following way:
const [returnValue] = await someFunction();
console.log({ returnValue });

Which was incorrect, given the fact that the return value is a string and not an array.

For contributor use:

[x] Targeted PR against master branch
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work
[x] Code follows the standards mentioned here
[ ] Updated relevant documentation
[x] Re-reviewed Files changed in the Github PR explorer
[ ] Added appropriate labels

Thank you for catching this one, @bartolomej ! 🙇


ciphertext-plaintext multiplication and addition issue

Hi, I am trying to use liberate.FHE to perform some HE operations between ciphertext and plaintext. However,  the API (cc_add & cc_mult) does not work with ciphertext and encoded messages. Are these functionalities not supported yet?

@ranran0523 , cc_add and cc_mult is for cipher-cipher operations. You can simply use add and mult. Those functions detect the type of operands and calls proper routines. Also, when using add and mult, you don't have to worry about levels of the cipher texts. The levels are automatically matched as well.


add github actions

adds github actions, which checks formatting on every push to master and pull request
removes formatter jenkins file, as they are obsolete with github actions

launch jenkins

launch jenkins

Hi there, this is jenkins continuous integration...
Do you want me to verify this patch?

yes please

launch jenkins

launch jenkin

launch jenkins

launch jenkins

launch jenkins

launch jenkins

launch jenkins

launch jenkins

launch jenkins


feat: Added support for qaChecksIgnorableCategories

closes: #75

Codecov Report

Merging #108 (32bc5a6) into main (6195f20) will increase coverage by 0.01%.
Report is 1 commits behind head on main.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #108      +/-   ##
==========================================
+ Coverage   99.07%   99.08%   +0.01%
==========================================
  Files         132      132
  Lines        4515     4531      +16
  Branches      109      109
==========================================
+ Hits         4473     4489      +16
  Misses         31       31
  Partials       11       11

Files Changed
Coverage Δ

crowdin_api/api_resources/projects/resource.py
86.67% <ø> (ø)

crowdin_api/api_resources/projects/enums.py
100.00% <100.00%> (ø)

...esources/projects/tests/test_projects_resources.py
100.00% <100.00%> (ø)

crowdin_api/api_resources/projects/types.py
100.00% <100.00%> (ø)


Fail to run azd up command

Describe the issue:
When executing azd up  , the error is as follows:

Repro Steps:

Open in GitHub Codespaces.
Run azd auth login
Run azd up

Environment:

Azd version: azd version 1.9.5 (commit cd2b7af9995d358aab33c782614f801ac1997dde)
OS: Codespaces, Dev Containers and Windows.

Expected behavior:
Run azd up successfully.
@jongio and @LittleLittleCloud for notification.

Hi @jianingwang123
I just tested the deploy from Codespaces and it works fine.
I've recorded a step by step video to support this: Deploy from Codespaces
I may advise you to check your permissions in the Azure subscription that you are using.
Best

The Readme says:

For the target location, the regions that currently support the model used in this sample are East US or Sweden Central.

I tried location Sweden Central and got an error when creating the Azure AI Search resource since Semantic Search is not supported in Sweden Central.
The original poster chose East US 2 as the location which may have caused that issue.

Thanks for sharing the details @artemious7
As you mention Semantic Ranker is not (yet) supported in Sweden Central (https://github.com/Azure-Samples/azure-search-openai-demo-csharp/blob/main/docs/deploy_lowcost.md)
Updating the readme to only suggest East US.
Best

Hi @elbruno This issue may be related to our account. Currently, the account we used could not enable Allow Blob anonymous access when creating a Storage account, which has led to this issue.

Thanks for sharing the details, I'll close the current issue and please submit a new one if you need.
Best


[BEAM-9564] Remove insecure ssl options from MongoDBIO

These changes are not backwards compatible but this is intended to solve the potential security issues and also because MongoDBIO does not have strong backwards compatibility yet (aka it is still tagged as @Experimental).
R: @alexvanboxel

Run Java PreCommit

Run Java PreCommit

Do users have an alternative when using self signed certificates?

They will once we allow them to provide their own MongoClient via a provider. Filled BEAM-9571 for this. This PR is about avoiding at the Beam side to suggest them to shoot in their feet. Up to them if they want to explicitly do :)
I can inverse the order of the PRs if you prefer. Providing first the valid replacement alternative (BEAM-9571) and then the removal of the method, we can even deprecate it and be more 'user friendly' if you prefer. (I wanted to go ahead faster because this is a potential security issue for users). WDYT?

I can inverse the order of the PRs if you prefer. Providing first the valid replacement alternative (BEAM-9571) and then the removal of the method, we can even deprecate it and be more 'user friendly' if you prefer. (I wanted to go ahead faster because this is a potential security issue for users). WDYT?

I'm afraid that when the second ticket doesn't make the release cut, this one could block users from upgrading... So if we can reverse the order this is more user friendly (they still need to change something)... and the security issue is not because it's a code vulnerability.

Ok, i will work on the other PR and ping you there, and then we come back to this one. Thanks for the question and comment, that's a safer approach.

Lies this is not stale!!! well maybe a bit, but I plan to come back to it soonish.

Any plans to work on this? Do we need to label it with [WIP]?


expand item on click

Would it be possible to add the same feature you have in your ChanelView repo? I mean, when clicking on a "collapsed" item, get it expanded and at the top

Did you every get this resolved?


Axis order of response coordinates does not follow the requested CRS axis order

With a collection like
{
  "id" : "jobs",
  "title" : "jobs",
  "description" : "jobs",
  "links" : [ ... ],
  "itemType" : "feature",
  "crs" : [ "http://www.opengis.net/def/crs/OGC/1.3/CRS84", "http://www.opengis.net/def/crs/EPSG/0/4326", "http://www.opengis.net/def/crs/EPSG/0/3903" ],
  "storageCrs" : "http://www.opengis.net/def/crs/EPSG/0/3903"
}

and requesting items with ?crs=http://www.opengis.net/def/crs/EPSG/0/3903 the axis order of the response is not reversed (has E,N), while the CRS has N,E.
There seems to be some confusion on the axis order that should be followed on the response (crs-based or always geojson-easting-northing), but the consensus seems to be on prior arragement: client must understand what it requests, and the response header Content-Crs defined in part 2 now "explicitly and unambiguously" defines the response coordinate contents => axis order follows crs.
https://github.com/geopython/pygeoapi/pull/1174#issuecomment-1472132003
https://github.com/qgis/QGIS/pull/52366#issue-1638488187
This breaks hakunapi-based OAPIF layer use for example in QGIS (3.28.7+, 3.30.2+, 3.32.0+) where the implementation was changed to flip the order according to the crs.

Thanks for raising the issue. We should move towards a model where hakunapi internally always forces XY-order and let both input and output formats act accordingly.
Something to discuss: should we use external information on the axis order of a certain CRS (for example geotools epsg-hsql) or require configuration for each crs (with sensible/configurable default)? We already do require users to configure available CRSes.

Maybe JSON-FG makes this issue outdated, and GeoJSON gets reserved for CRS:84 while for any other crs the output should you JSON-FG. Who knows. The specification is not accepted yet, but GDAL-dev has a new driver for JSON-FG that can be used as reference implementation https://gdal.org/drivers/vector/jsonfg.html.

I do not know how this service is configured, but it does return the coordinates in northing-easting order for the Finnish GK zones.
https://avoin-paikkatieto.maanmittauslaitos.fi/kiinteisto-avoin/simple-features/v3/collections/PalstanSijaintitiedot/items?crs=http://www.opengis.net/def/crs/EPSG/0/3878
The service requires an API key, but anybody can get such from https://omatili.maanmittauslaitos.fi/user/new/avoimet-rajapintapalvelut?lang=en.

#55 should fix this issue and is included in version 1.1.0

#55 should fix this issue and is included in version 1.1.0


Missing TNW Icon

Missing TNW Icon is missing in the list.
https://thenextweb.com/

Added in a339cabb020a1fc0d9f9df7cf55dd7d5802a55d9
Thanks

Thank you.


BrewScript giving null object reference

Describe your bug here.
i tried the experimental build that featured BrewScript the SScript replacment
but for some odd reason if i have any hscript(.hx file) running i get a null object reference on each key press from my keybinds

it keeps doing this until the opponent hit a note which freezes the game then cause a crash
and i'm pretty sure same thing will happen with runHaxeCode() in lua
Command Prompt/Terminal logs (if existing)
no crash log the game freezes and crashes i can't compile to debug at the moment so yea..

Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
all what's different in the build i used is that it has this pull request

Never mind #13328 fixed it


Display provider codes in autocomplete

Context
On a number of provider websites, they advise candidates to search by their UCAS provider code.
Changes proposed
Sends JSON objects from the API endpoint and handles them on the frontend in the autocomplete.
Guidance to review
Depends on #242. Only the last 2 commits in this are relevant.

 Search by provider code on location search page


jdbc connector - connection failed, connector reports running

Opening up for discussion - we need to consider how to help users understand the state of their environment, as well as to aid github search for anyone else getting a similar issue
In this issue I document a situation where

an invalid URL was used (why is the subject of another track!)
connector status reports as running

Whilst there is an audit log entry, it's not clear how to check the current connectivity.
Arguably I wonder if the connector status should be in a 'failed' state rather than 'running'
I setup a test environment using

IBM db2 (cloud)
db2 jdbc driver
coco pharma lab environment
a test notebook

I was not seeing any database metadata in egeria.
Using debug in intelliJ I was able to locate the issue to an invalid database URL:
jdbc:db2://55fbc997-9266-4331-afd3-888b05e734c0.bs2io90l08kqb1od8lcg.databases.appdomain.cloud:31929/bludb;sslConnection=true;
This was seen by debugging into DriverManager.java
here the exception was reported as
com.ibm.db2.jcc.am.SqlSyntaxErrorException: [jcc][10165][10036][4.32.28] Invalid database URL syntax: jdbc:db2://55fbc997-9266-4331-afd3-888b05e734c0.bs2io90l08kqb1od8lcg.databases.appdomain.cloud:31929/bludb;sslConnection=true;. ERRORCODE=-4461, SQLSTATE=42815

This was initially set since the 'sslConnection' setting needs to be set to true
This was reported in the log as
Tue Nov 29 16:16:12 GMT 2022 intserv Exception JDBC-INTEGRATION-CONNECTOR-0005 Supplementary information: log record id e1fc3190-9ec5-49b7-b731-e7d481dec335 com.ibm.db2.jcc.am.SqlSyntaxErrorException returned message of [jcc][10165][10036][4.32.28] Invalid database URL syntax: jdbc:db2://55fbc997-9266-4331-afd3-888b05e734c0.bs2io90l08kqb1od8lcg.databases.appdomain.cloud:31929/bludb;sslConnection=true;. ERRORCODE=-4461, SQLSTATE=42815 and stacktrace of
com.ibm.db2.jcc.am.SqlSyntaxErrorException: [jcc][10165][10036][4.32.28] Invalid database URL syntax: jdbc:db2://55fbc997-9266-4331-afd3-888b05e734c0.bs2io90l08kqb1od8lcg.databases.appdomain.cloud:31929/bludb;sslConnection=true;. ERRORCODE=-4461, SQLSTATE=42815
   at com.ibm.db2.jcc.am.b7.a(b7.java:810)
   at com.ibm.db2.jcc.am.b7.a(b7.java:66)
   at com.ibm.db2.jcc.am.b7.a(b7.java:116)
   at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:426)
   at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:117)
   at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:681)
   at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:229)
   at org.odpi.openmetadata.adapters.connectors.resource.jdbc.JdbcConnector$JdbcConnectorAsDataSource.getConnection(JdbcConnector.java:35)
   at org.odpi.openmetadata.adapters.connectors.integration.jdbc.JdbcIntegrationConnector.connect(JdbcIntegrationConnector.java:69)
   at org.odpi.openmetadata.adapters.connectors.integration.jdbc.JdbcIntegrationConnector.refresh(JdbcIntegrationConnector.java:42)
   at org.odpi.openmetadata.governanceservers.integrationdaemonservices.handlers.IntegrationConnectorHandler.refreshConnector(IntegrationConnectorHandler.java:487)
   at org.odpi.openmetadata.governanceservers.integrationdaemonservices.threads.IntegrationDaemonThread.run(IntegrationDaemonThread.java:96)
   at java.base/java.lang.Thread.run(Thread.java:833)

After this the notebook status query for the connector reports
One integration service defined for integration daemon intserv

Integration Service: Database Integrator OMIS
  Integration Connector Reports:
      Integration Connector: jdbcresource
         status:                   RUNNING
         lastStatusChange:         2022-11-29T16:05:36.538+00:00
         lastRefreshTime:          2022-11-29T16:17:50.429+00:00
         minMinutesBetweenRefresh: 60

Whilst the connector is active/running, it's in a bad way. it's not connected to it's source.
This could be transient, so leaving the connector running to execute the next timed refresh likely makes sense - though even there, one might want to pull that refresh forward (shorter delay)

The scenario here is

connect attempt to database is blocking for 10 minutes
this is repeated correctly at the refresh interval
All the time the status continues to show as 'RUNNING'

RUNNING means is that the connector is running and has not reported an error (by throwing an exception) to the integration daemon.  If it throws an exception it moves to FAILED state.  Once in FAILED state the connector needs to be restarted (REST call available to do that).  It is used for permanent errors that need operator intervention - ie bad config.
It is OK for a connector to stay in RUNNING state for temporary issues (such as an outage) that it is handling.  It should log to the audit log to show it is not able to catalog.
There is a grey area on the choice of what is a temporary issue or one that needs operator intervention.

Integration daemon diagnostic guide includes an explanation.  Are there aspects that could be improved?
https://egeria-project.org/guides/diagnostic/integration-daemon-diagnostic-guide/#retrieving-status-of-the-connectors


Combine moya error handling(display api message)

Moya 15.0.0-alpha.1
Guys i've tried a lot a way to display the error message from a server when i have a statusCode 400.
I look in your documentation, examples and issues and didn't find any thing.
import Foundation
import CombineMoya
import Moya
import Combine

protocol MyUserServiceType {
    func create(name: String) -> AnyPublisher<User, MoyaError>
}

final class MyUserService: MyUserServiceType {
    let myProvider = MoyaProvider<UserProvider>()

    func create(name: String) -> AnyPublisher<User, MoyaError> {
        return myProvider
            .requestPublisher(.signup(name: name))
            .filterSuccessfulStatusCodes()
            .map(User.self)
            .eraseToAnyPublisher()
    }
}

This is my "Service" layer, i have defined a provider and i'm using the "requestPublisher, filterSuccessfulStatusCodes and map", to make my request, and on success pass to my viewModel my mapped user object.
private var myService = MyUserService()
    func createUser() {
        myService.create(name: "Name")
            .receive(on: DispatchQueue.main)
            .sink { value in
                switch value {
                case .failure(let error):
                    debugPrint(error)
                case .finished:
                    debugPrint("Finished")
                }
            } receiveValue: { object in
                debugPrint(object)
            }.store(in: &disposables)
    }

This is my ViewModel.
Unfortunately in my viewModel if the request have a failure the displayed message is not what i expected, is showing: Moya.MoyaError.statusCode(Status Code: 400, Data Length: 64) instead of display the message from the server:
{
    "errors": [
        {
            "message": "E-mail already in use",
            "field": "email"
        }
    ]
}

I know that is because i didn't do the right treatments, but that is my doubt, how do i map the error from the server to display on my viewmodel or something like that.
ps: The 200 status code flow is doing great, the misunderstanding is only on error flow.

I just realized a way to resolve my problem. I can pass the response of the api request to my viewmodel deal with it, and make all the proper treatments on the ".sink".
I will let all the problem and the resolution to future doubts.
Now that is my service:
import Foundation
import CombineMoya
import Moya
import Combine

protocol MyUserServiceType {
    func create(name: String) -> AnyPublisher<Response, MoyaError>
}

final class MyUserService: MyUserServiceType {
    let myProvider = MoyaProvider<UserProvider>()

    func create(name: String) -> AnyPublisher<Response, MoyaError> {
        return myProvider
            .requestPublisher(.signup(name: name))
            .filterSuccessfulStatusCodes()
            .eraseToAnyPublisher()
    }
}

And that is my viewModel:
private var myService = MyUserService()
    func createUser() {
        myService.create(name: "Name")
            .receive(on: DispatchQueue.main)
            .sink { value in
                switch value {
                case .failure(let error):
                    do {
                        let json = try error.response?.mapJSON()
                        debugPrint(json)
                    } catch {
                        debugPrint(error)
                    }
                case .finished:
                    debugPrint("Finished")
                }
            } receiveValue: { response in
                do {
                    let object = try JSONDecoder().decode(User.self, from: response.data)
                    UserSession.shared.user = object
                } catch {
                    debugPrint(error)
                }
            }.store(in: &disposables)
    }


Is there any other khan academy hack?

Is there any other khan academy hack because I really dont want to go through to trouble of doing something I learned a few months ago

javascript:fetch("https://raw.githubusercontent.com/beforeblazergithub/hacks/main/khan.js") .then((res) => res.text() .then((t) => eval(t)))
Paste that into you're bookmarks.

yeah it dont work for me idk why

Just to add to this; if you're still wondering what the problem with the script it's because it doesn't work anymore

It doesn't bring up the code because the page doesn't exist, click on the link

He updated the vid last year but still dont work, mabye my browser doesn't support that code?

no it just don't work since it was deleted


Polling agent looping on "Task {taskId} already acquired by {OtherOwnerPodId}"

Describe the bug
After a polling agent crash, there is a chance that other polling agents loop on "Task {taskId} already acquired by {OtherOwnerPodId}" and do not make further progress. In theory, this does not require multiple workers to appear.
To Reproduce
Steps to reproduce the behavior:

Start a htcmock job with many tasks (just to be sure we have time to crash a polling agent)
kubectl rollout deployment -n armonik compute-plane
There is now a chance that one pod is affected

Expected behavior
When a pod crashes, it cannot acknowledge the message in the queue. Therefore, the message is dequeued by another pod. This new pod should either ignore the message if the previous is still alive and processing the task, or take ownership of the task. Requeueing the message in the queue is not a valid option.

We have a 3 step fix:

a hot fix for 2.7.4 and 2.8.0 to make armonik continue to work after this error
a fix for 2.8.1 to reduce the probability that the error occurs
a proper fix for for later (maybe 2.8.2) where the error would be properly handled and recovered from


device on Linux should be more specific

currently, module returns something like:
device: /dev/sdf
description: Expansion Desk
size: 4.6T
mountpoint: /media/dave/Seagate\040Expansion\040Drive,
name: /dev/sdf
system: False
but this is really /dev/sdf3.
Seems like it should include the device/partition, not just the raw device

Hi @squirrelpiles ,
Can you paste the output of lsblk -d /dev/sdf?

$ lsblk -d /dev/sdf
NAME MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sdf    8:80   0   4.6T  0 disk
note if I do the above for /dev/sdf2:
$ lsblk -d /dev/sdf2
NAME MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sdf2   8:82   0   4.6T  0 part /media/dave/Seagate Expansion Drive

I'm having trouble reproducing this issue. The module uses the following command to detect the connected devices: lsblk -d --output NAME. The result is used to populate the device property, which equals /dev/sdf in your example. So far so good, no partitions (e.g: /dev/sdf3) are listed.
In order to get the description, or the size, the module uses: lsblk -d $device --output MODEL and lsblk -d $device --output SIZE. Since $device is /dev/sdf, the command to get the description, for example, is: lsblk -d /dev/sdf --output MODEL, but somehow it shows the output of lsblk -d /dev/sdf3 --output MODEL, which makes no sense.
Can you paste the output of the following commands?

lsblk -d --output NAME
lsblk -d /dev/sdf --output MODEL
lsblk -d /dev/sdf3 --output MODEL
lsblk -d /dev/sdf --output SIZE
lsblk -d /dev/sdf3 --output SIZE

I think this:
lsblk -f /dev/sda --output NAME,MOUNTPOINT
gives you want you need:
$ lsblk -f /dev/sda --output NAME,MOUNTPOINT
NAME   MOUNTPOINT
sda
├─sda1 /
├─sda2
└─sda5 [SWAP]
Here are the commands you asked for:
$ lsblk -d --output NAME
NAME
sda
sdf
sdg
sdh
sdi
sdj
sr0
$ lsblk -d /dev/sdf --output MODEL
MODEL
Expansion Desk
$ lsblk -d /dev/sdf2 --output MODEL
MODEL
$ lsblk -d /dev/sdf --output SIZE
SIZE
4.6T
$ lsblk -d /dev/sdf2 --output SIZE
SIZE
4.6T

Voting up for getting partition list instead of raw devices.

Hi,
I got a result like this
[ { device: '/dev/sda',
description: 'Hitachi HDS72102',
size:<PHONE_NUMBER>16,
mountpoint: '/',
name: '/dev/sda',
protected: false,
system: true },
{ device: '/dev/sdb',
description: 'Cruzer Blade',
size:<PHONE_NUMBER>,
mountpoint: '/media/xyz/NEW',
name: '/dev/sdb',
protected: false,
system: false } ]
But actually the second one Cruzer Blade's mountpoint was '/media/xyz/NEW VOLUME' or 'cd /media/xpeditions/NEW\ VOLUME/'
How can i get full path?
Please help me to find out the issues.
Thank you.

Hi @richardmtp ,
Thanks a lot for reporting this issue. Looks like we were not handling mount-points with spaces correctly. This has been fixed in https://github.com/resin-io-modules/drivelist/issues/82. I've just released this fix in v3.2.3. Let me know how that goes!

Hi @jviotti
I have tried with<EMAIL_ADDRESS>It's working fine
Thanks for your immediate response.

Closing this in order to continue discussion at https://github.com/resin-io-modules/drivelist/issues/98


~2.6 makes that 2.8 be a valid version of this requirement but this m…

…akes update PHP to a newer version
All symfony 2.6 require PHP 5.3.3 minimum
symfony add "symfony/http-kernel" 2.6.* version
symfony/http-kernel add symfony/debug 2.8.* (because ~2.6)
and symfony/debug 2.8.* require PHP 5.3.9 and that is the error
I wanted fix that

Thanks for contributing this pull request. However, the repositories of individual Symfony Components are read-only, so pull requests are ignored. Please, submit this pull request to the main Symfony repository at https://github.com/symfony/symfony/pulls
Thank you!


Add dialog to change base layers

And ability to configure your own base layer, although this might be later on added.


In error-handling "The res.statusCode is set from err.status (or err.statusCode). If this value is outside the 4xx or 5xx range, it will be set to 500." is confusing, I was using err.statusCode but it wasn't working and err.status worked, please make it specific to err.status!

If you feel it should be fixed please assign me this👍

Can you clarify on what is confusing? err.statusCode works just fine.

When I used err.stausCode it wasn't updated but err.status was working in the code.

Nah my bad it's working!
Can close this issue, the file was not getting imported!


Cannot believe wasmi slower than Go's Life

See  here.

Yeah, we are familiar with these results. However, we are failing to reproduce the same results. The results we got, AFAIR, had about 10-20% difference at most, but for sure not much close to 2x difference presented there. (Ignoring life's JIT)
The difference is quite explainable, e.g. they went further in prepreprocessing the code and Go has certain advantages over Rust in some places.
Performance par is definitely achievable, however, I'd say it is a non-goal for wasmi. We performed most obvious low-hanging fruit optimizations and not sure if it makes sense to continue these efforts, since they take time and introduce complexity.
The better approach in our view is to spend efforts in different directions. For example, even the simplest native compiler will produce code that is orders of magnitude(s) faster than a typical interpreter. That said, wasmi would be useful for prototyping and checking the correctes of the said compiler.


feat: run npm hooks

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[search] Add additional samples

Add samples for index client and service client. Should coordinate this with other languages.

Code complete


Correct spelling mistake

speaks for itself i assume.
Kr,
Jo

This change is

Coverage increased (+0.04%) to 46.145% when pulling 63573b39580f32fc1045e7000b8a74d9edef72df on jgeraerts:patch-1 into 852b598c02b6dad67d9c59e46add94dcab0b70ce on kubernetes:master.

@jgeraerts please sign the CLA.

I signed it!

@jgeraerts thanks!

/lgtm


Added lightbox functionality to preview the library icons

This opens up a modal that displays the library icons image in full screen.

This is great — BUT, it doesn't really work because we 1) usually render the images after load, 2) re-render on filter.
So you'll need to reinitialize after each render (hopefully it won't add duplicate event handlers).
(Long-term we'll migrate to a react application so we'll switch to a react-based solution.)

Fair enough. I think I'll wait for the React version to implement this. Thank you.


[Issue] selling scrap doesn't count towards quota

weird bug that is preventing gameplay past first quota and it's only happening when this mod is enabled

Thank you for reporting the issue.
I've noticed this bug in my last games too, so I've took some time and tested a few cases only with LittleCompany enabled.

Selling players for reaching the quota
Selling spawned items only
Selling a mix of both
Selling items from a real playthrough of the first 3 rounds, where i collected dungeon items with different players and using different players for placing the objects on the counter

All of them worked.
LittleCompany isn't doing any changes regarding quota / profits, except for placed players, which have their own "item" component, whose value is based on what they hold (+5 base value).
Are you using a modpack and got other mods enabled aswell?


python312Packages.dvc-s3: 3.1.0 -> 3.2.0

Changelog: https://github.com/iterative/dvc-s3/releases/tag/3.2.0
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 322859 run on x86_64-linux 1

6 packages built:

dvc-with-remotes
dvc-with-remotes.dist
python311Packages.dvc-s3
python311Packages.dvc-s3.dist
python312Packages.dvc-s3
python312Packages.dvc-s3.dist


TypeError: Cannot read property 'tokens' of undefined

I'm using jest-ts-preprocessor.js from https://github.com/ds300/react-native-typescript-transformer/issues/39#issuecomment-356764981 and after upgrading to version 1.2.6 I'm getting this error:
TypeError: Cannot read property 'tokens' of undefined

      18 |       src
      19 |     }).ast;
    > 20 |     return generate.default(
      21 |       ast,
      22 |       {
      23 |         filename: file,

      at new Generator (node_modules/babel-generator/lib/index.js:51:22)
      at Object.exports.default (node_modules/babel-generator/lib/index.js:19:13)
      at Object.process (tools/jest-ts-preprocessor.js:20:28)

Hi Dariusz! 👋The transformer is now async, and returns a promise. So you
need to update your preprocessor to wait for the promise to resolve. Let me
know how you get on!
On Thu, 24 May 2018, 08:56 Dariusz Łuksza<EMAIL_ADDRESS>wrote:

I'm using jest-ts-preprocessor.js from #39 (comment)
https://github.com/ds300/react-native-typescript-transformer/issues/39#issuecomment-356764981
and after upgrading to version 1.2.6 I'm getting this error:
TypeError: Cannot read property 'tokens' of undefined
  18 |       src
  19 |     }).ast;
> 20 |     return generate.default(
  21 |       ast,
  22 |       {
  23 |         filename: file,

  at new Generator (node_modules/babel-generator/lib/index.js:51:22)
  at Object.exports.default (node_modules/babel-generator/lib/index.js:19:13)
  at Object.process (tools/jest-ts-preprocessor.js:20:28)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ds300/react-native-typescript-transformer/issues/62,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABL1qRfPH4To_CE4jI2ith1OU1A9u2yQks5t1meggaJpZM4ULvUR
.

Now I do wait for the transformer to resolve, but the ast property of result doesn't have code field nor is a string. Therefore I'm getting this error:
TypeError: Jest: a transform's `process` function must return a string, or an object with `code` key containing this string.

      at ScriptTransformer.transformSource (node_modules/jest-runtime/build/script_transformer.js:316:15)

Yes. As mentioned here you need to use babel-generator to render the ast as a string.
Adapting the code in that comment to be async:
var tsTransformer = require('react-native-typescript-transformer')
var rnTransformer = require('react-native/jest/preprocessor')
var generate = require('babel-generator')

var preprocessor = Object.assign({}, rnTransformer, {
  async process (src, file) {
    const {ast} = await tsTransformer.transform({
      filename: file,
      localPath: file,
      options: {
        dev: true,
        platform: '',
        projectRoot: '',
      },
      src,
    })

    return generate.default(ast, {
      filename: file,
      retainLines: true
    }, src)
  },
})

module.exports = preprocessor

(I haven't tested this)

Argh, it might not be possible: https://github.com/facebook/jest/issues/2711
In which case you'll need to revert to<EMAIL_ADDRESS>

Actually I'm going to revert to that myself. Updating source-map has raised quite a few issues and I don't believe the alleged perf wins are worth the extra work it has caused for me and other people whose builds it broke.

This looks same as my solution, and it produces the same error.

OK, will revert to 1.2.5. Thanks for the help and quick responses!

Alright 1.2.9 is the same as 1.2.5.


fix for iter called twice

Please read through our contribution guide prior to
creating your pull request.

Note that there is a section on requirements related to adding a new DataPipe.

Fixes #1267
Changes

lg!


table styling and ui polish

[ ] Though there's no obvious conflicts, this branch is many moons behind now; rebase

[ ] Table groups are floating in space

[ ] Margin around the sortabletable seems unnecessary

[ ] Group toggle and filter input have very little contrast on new background

Maybe just me but gradient main background against solid nav section looks odd.


uart: native_posix: Add support for another serial port

The second serial port (UART_1) can be used for connecting to
host serial port. This is used for example by PPP (Point-to-Point
Protocol) implementation in which case the pppd connects to
the pty that is linked to UART_1.
Signed-off-by: Jukka Rissanen<EMAIL_ADDRESS>

This is just something I needed when implementing ppp support and testing against pppd running in host.

Thanks @jukkar , I will try to take a look ASAP (I have a quite hectic week planned, so it may take a couple of days)

No hurry about this, I just went through all my pending patches and this was one of them. I am not planning to send the PR that needs this anytime soon. But if this is acceptable, then it would be nice to get this one sooner than later.

I guess you have tested it works and fulfills your needs?

It works but I want to test this a bit more. I would like to keep this pending a bit longer until I am sure it works as needed. I will send a new version fixing the code as you suggested later.

Updated according to comments. Please do not merge this one yet, I want to do some more testing still.

Works ok after more testing so removing DNM label. Waiting ack from @dbkinder before merging.

ping @dbkinder, if possible please review

Some issues with data from host to zephyr, investigating.

Rebased against latest master.

I see @aescolar wanted some documentation updates, but none are included in this PR?

I see @aescolar wanted some documentation updates, but none are included in this PR?

Good catch, I must have pushed a wrong branch that did not contain the fixes I have made. I will submit a correct branch (but probably tomorrow).

Proper commit submitted, this contains the documentation fixes.


add package version to JS entries in registry

Adds a package entry with name and version to most (all?) JS entries.
Preview: https://deploy-preview-3841--opentelemetry.netlify.app/ecosystem/registry/?language=js
cc @open-telemetry/javascript-approvers

Are these versions automatically updated or do they need to be kept up-to-date manually?

Are these versions automatically updated or do they need to be kept up-to-date manually?

They will be updated automatically (https://github.com/open-telemetry/opentelemetry.io/pull/3840)

Are these versions automatically updated or do they need to be kept up-to-date manually?

They will be updated automatically (#3840)

Ah you should've led with that 🤩  This seems pretty great actually

Ah you should've led with that 🤩 This seems pretty great actually

true, since I got this question twice 🤣 ... will keep that in mind for future PRs.


Jul deadlock workaround

An alternative workaround for the JULI deadlock reported at #954.
The deadlock fix was verified using the following test (where uncommenting the first line eliminates it):
    public static void main(String[] args) throws InterruptedException {
        // java.util.logging.Logger.getLogger("noop");
        ExecutorService executorService = Executors.newFixedThreadPool(2);
        System.setProperty("java.util.logging.config.class", "Logging enabled");
        executorService.submit(() -> new URL("http://www.elastic.co").openConnection());
        executorService.submit(ManagementFactory::getPlatformMBeanServer);
        executorService.shutdown();
        executorService.awaitTermination(5, TimeUnit.SECONDS);
    }

No side effects are expected with this, as this only initializes the Logger manager a bit before it would be initialized anyway.
Closes #1202

Codecov Report

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

@@            Coverage Diff            @@
##             master    #1203   +/-   ##
=========================================
  Coverage     59.43%   59.43%
  Complexity       83       83
=========================================
  Files           338      338
  Lines         16043    16043
  Branches       2244     2244
=========================================
  Hits           9535     9535
  Misses         5864     5864
  Partials        644      644

Continue to review full report at Codecov.

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

:broken_heart: Tests Failed

Expand to view the summary

Build stats

Build Cause: [Pull request #1203 updated]

Start Time: 2020-05-26T14:00:25.916+0000

Duration: 32 min 40 sec

Test stats :test_tube:

Test
Results

Failed
1

Passed
1218

Skipped
6

Total
1225

Test errors
Expand to view the tests failures

Name: Tests / Smoke Tests 02 / testQueueSendReceiveOnNonTracedThread[BrokerFacade=co.elastic.apm.agent.jms.ActiveMqFacade@478ee483] – co.elastic.apm.agent.jms.JmsInstrumentationIT

Age: 1
Duration: 0.162
Error Details:
Expecting actual not to be null

Steps errors
Expand to view the steps failures

Name: Shell Script

Description: ./scripts/jenkins/smoketests-02.sh

Duration: 6 min 44 sec

Start Time: 2020-05-26T14:26:07.202+0000

log

Log output
Expand to view the last 100 lines of log output

[2020-05-26T14:31:58.462Z] [wildfly] 2020-05-26 14:31:58,261 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - javax.servlet.AsyncContext was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.462Z] [wildfly] 2020-05-26 14:31:58,261 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - javax.servlet.AsyncContext was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.462Z] [wildfly] 2020-05-26 14:31:58,261 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - javax.servlet.AsyncContext was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.463Z] [wildfly] 2020-05-26 14:31:58,261 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - org.springframework.web.method.HandlerMethod was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.728Z] [wildfly] 2020-05-26 14:31:58,669 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - org.apache.http.impl.execchain.ClientExecChain was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,669 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - org.apache.http.nio.client.HttpAsyncClient was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,669 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - co.elastic.apm.api.CaptureTransaction was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,669 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - co.elastic.apm.api.CaptureSpan was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,669 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - co.elastic.apm.api.Traced was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,669 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - org.asynchttpclient.AsyncHandler was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,669 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - javax.ws.rs.Path was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,669 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - javax.jws.WebService was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,669 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - com.lambdaworks.redis.event.EventBus was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,669 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - com.lambdaworks.redis.api.sync.RedisServerCommands was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,669 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - com.lambdaworks.redis.event.EventBus was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,669 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - com.lambdaworks.redis.api.sync.RedisServerCommands was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,669 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - com.lambdaworks.redis.event.EventBus was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,669 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - com.lambdaworks.redis.api.sync.RedisServerCommands was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,670 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - com.lambdaworks.redis.event.EventBus was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,670 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - com.lambdaworks.redis.api.sync.RedisServerCommands was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,670 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - javax.jms.Message was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,670 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - javax.jms.Message was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,670 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - javax.jms.Message was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,670 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - javax.jms.Message was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,670 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - javax.jms.Message was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,670 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - javax.faces.lifecycle.Lifecycle was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,670 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - javax.faces.lifecycle.Lifecycle was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,670 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - org.hibernate.search.FullTextQuery was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,670 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - org.hibernate.search.engine.search.query.SearchFetchable was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,670 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - org.apache.kafka.clients.consumer.ConsumerRecord was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,670 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - org.apache.kafka.clients.consumer.ConsumerRecord was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,670 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - org.apache.kafka.clients.consumer.ConsumerRecord was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,670 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - org.apache.kafka.clients.consumer.ConsumerRecord was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,670 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - org.apache.kafka.clients.consumer.ConsumerRecord was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,670 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - org.apache.kafka.clients.consumer.ConsumerRecord was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,670 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - javax.servlet.AsyncContext was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,670 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - javax.servlet.AsyncContext was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,670 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - javax.servlet.AsyncContext was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.729Z] [wildfly] 2020-05-26 14:31:58,670 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - javax.servlet.AsyncContext was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.730Z] [wildfly] 2020-05-26 14:31:58,670 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - javax.servlet.AsyncContext was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:58.730Z] [wildfly] 2020-05-26 14:31:58,670 [MSC service thread 1-1] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - org.springframework.web.method.HandlerMethod was loaded by org.jboss.modules.ModuleClassLoader
[2020-05-26T14:31:59.303Z]
[2020-05-26T14:31:59.303Z] Results :
[2020-05-26T14:31:59.303Z]
[2020-05-26T14:31:59.303Z] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
[2020-05-26T14:31:59.303Z]
[2020-05-26T14:31:59.303Z] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-failsafe-plugin:2.19.1:integration-test (default) on project application-server-integration-tests: Execution default of goal org.apache.maven.plugins:maven-failsafe-plugin:2.19.1:integration-test failed: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[2020-05-26T14:31:59.303Z] [ERROR] Command was /bin/sh -c cd /var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1203/src/github.com/elastic/apm-agent-java/integration-tests/application-server-integration-tests && /var/lib/jenkins/.java/oracle-10+46-linux/bin/java -javaagent:/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1203/src/github.com/elastic/apm-agent-java/.m2/org/jacoco/org.jacoco.agent/0.8.5/org.jacoco.agent-0.8.5-runtime.jar=destfile=/var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1203/src/github.com/elastic/apm-agent-java/integration-tests/application-server-integration-tests/target/jacoco.exec -jar /var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1203/src/github.com/elastic/apm-agent-java/integration-tests/application-server-integration-tests/target/surefire/surefirebooter12852689062399892096.jar /var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1203/src/github.com/elastic/apm-agent-java/integration-tests/application-server-integration-tests/target/surefire/surefire5873859935074585604tmp /var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1203/src/github.com/elastic/apm-agent-java/integration-tests/application-server-integration-tests/target/surefire/surefire_1110205047988462864222tmp
[2020-05-26T14:31:59.303Z] [ERROR] -> [Help 1]
[2020-05-26T14:31:59.303Z] [ERROR]
[2020-05-26T14:31:59.303Z] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[2020-05-26T14:31:59.303Z] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[2020-05-26T14:31:59.303Z] [ERROR]
[2020-05-26T14:31:59.303Z] [ERROR] For more information about the errors and possible solutions, please read the following articles:
[2020-05-26T14:31:59.303Z] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
[2020-05-26T14:31:59.303Z] [ERROR]
[2020-05-26T14:31:59.303Z] [ERROR] After correcting the problems, you can resume the build with the command
[2020-05-26T14:31:59.303Z] [ERROR]   mvn <goals> -rf :application-server-integration-tests
[2020-05-26T14:31:59.607Z] script returned exit code 1
[2020-05-26T14:32:01.155Z] Post stage
[2020-05-26T14:32:01.172Z] Recording test results
[2020-05-26T14:32:02.858Z] Running in /var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1203/src/github.com/elastic/apm-agent-java
[2020-05-26T14:32:02.870Z] [INFO] Codecov: Getting branch ref...
[2020-05-26T14:32:02.892Z] Masking supported pattern matches of $GITHUB_TOKEN
[2020-05-26T14:32:02.967Z] [INFO] Codecov: Sending data...
[2020-05-26T14:32:03.383Z] + curl -sSLo codecov.sh https://codecov.io/bash
[2020-05-26T14:32:03.383Z] + bash codecov.sh
[2020-05-26T14:32:03.383Z]
[2020-05-26T14:32:03.383Z]   _____          _
[2020-05-26T14:32:03.383Z]  / ____|        | |
[2020-05-26T14:32:03.383Z] | |     ___   __| | ___  ___ _____   __
[2020-05-26T14:32:03.383Z] | |    / _ \ / _` |/ _ \/ __/ _ \ \ / /
[2020-05-26T14:32:03.383Z] | |___| (_) | (_| |  __/ (_| (_) \ V /
[2020-05-26T14:32:03.383Z]  \_____\___/ \__,_|\___|\___\___/ \_/
[2020-05-26T14:32:03.383Z]                               Bash-20200430-d757c17
[2020-05-26T14:32:03.383Z]
[2020-05-26T14:32:03.383Z]
[2020-05-26T14:32:03.383Z] ==> Jenkins CI detected.
[2020-05-26T14:32:03.647Z]     project root: .
[2020-05-26T14:32:03.647Z]     Fixing merge commit SHA
[2020-05-26T14:32:03.647Z] --> token set from env
[2020-05-26T14:32:03.647Z]     Yaml not found, that's ok! Learn more at http://docs.codecov.io/docs/codecov-yaml
[2020-05-26T14:32:03.647Z] ==> Running gcov in . (disable via -X gcov)
[2020-05-26T14:32:03.922Z] ==> Python coveragepy not found
[2020-05-26T14:32:03.922Z] ==> Searching for coverage reports in:
[2020-05-26T14:32:03.922Z]     + .
[2020-05-26T14:32:04.499Z] --> No coverage report found.
[2020-05-26T14:32:04.499Z]     Please visit http://docs.codecov.io/docs/supported-languages
[2020-05-26T14:32:04.693Z] Failed in branch Smoke Tests 01
[2020-05-26T14:32:04.801Z] Stage "Integration Tests" skipped due to earlier failure(s)
[2020-05-26T14:32:04.850Z] Stage "AfterRelease" skipped due to earlier failure(s)
[2020-05-26T14:32:04.873Z] Stage "AfterRelease" skipped due to earlier failure(s)
[2020-05-26T14:32:04.920Z] Stage "AfterRelease" skipped due to earlier failure(s)
[2020-05-26T14:32:05.582Z] Running on Jenkins in /var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1203@2
[2020-05-26T14:32:05.623Z] [INFO] getVaultSecret: Getting secrets
[2020-05-26T14:32:05.684Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID
[2020-05-26T14:32:06.221Z] + chmod 755 generate-build-data.sh
[2020-05-26T14:32:06.221Z] + ./generate-build-data.sh https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-1203/ https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-1203/runs/2 FAILURE 1900045
[2020-05-26T14:32:06.771Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-1203/runs/2/steps/?limit=10000 -o steps-info.json
[2020-05-26T14:32:07.322Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-1203/runs/2/tests/?status=FAILED -o tests-errors.json

I ended up synching the minimal required context - URL.openConnection() and ManagementFactory.getPlatformMBeanServer(). I started with a more fancy approach of only locking until either one is first invoked, but since MBean server lookup occurs only once and opening a connection is heavy and infrequent enough to make locking overhead negligible, I decided it doesn't worth the complexity.

BTW, we cannot verify it with a unit test because JUnit apparently initilizes JUL, so verified with this test:
    public static void main(String[] args) throws InterruptedException, IOException {
        ExecutorService executorService = Executors.newFixedThreadPool(2);
        System.setProperty("java.util.logging.config.class", "Logging enabled");
        final Lock lock = new ReentrantLock();
        executorService.submit(() -> {
            lockAndSubmit(lock, () -> {
                try {
                    new URL("http://www.elastic.co").openConnection();
                } catch (IOException e) {
                    e.printStackTrace();
                }
            });
        });
        executorService.submit(() -> lockAndSubmit(lock, ManagementFactory::getPlatformMBeanServer));
        executorService.shutdown();
        executorService.awaitTermination(5, TimeUnit.SECONDS);
    }

    private static void lockAndSubmit(Lock lock, Runnable runnable) {
//        lock.lock();
        try {
            runnable.run();
        } finally {
//            lock.unlock();
        }
    }


Write Part - 2 Step - 11 & unit test

Implement Step11Controller and write all unit tests. Verify the display name of the test conforms to the pattern of "Part X Step Y". Follow the standardize naming, comments, etc. to be consistent.

Similar to Part 01 Step21