[FLINK-7384][cep] Unify event and processing time handling in the Abs…

What is the purpose of the change
This PR introduces a new configuration parameter that allows partial matches to be timeouted without any subsequent events in the stream. Just based on the time. The timers in case of custom operators are also registered less often.
Verifying this change
This change changed existing tests and can be verified as follows:
The TODO was removed from testCEPOperatorCleanupProcessingTime
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (yes, but just in CEP)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)

Documentation

Does this pull request introduce a new feature? (yes)
If yes, how is the feature documented? (docs / JavaDocs)

I'm closing this as abandoned for now. Please re-open if we plan to continue working on this.


Modify how logFailure handles assertions

Currently we don't pass all the assertions needed to create an accurate model to the logFailure method. For instance: https://github.com/insufficiently-caffeinated/caffeine/blob/737bb4e4f6cc0b74735ad7255c3f0d4f8f59d58c/src/Interpreter/Interpreter.cpp#L162
The Context passed to logFailure doesn't contain the assertion that the denominator is 0, so when we go to create a model of it, the denominator won't necessarily be 0.
As a fix, we can copy the Context, add the new assertions, and pass it into logFailure, and discard it after that.

Just as note, it's probably more helpful to go about this the other way: Both the check and resolve methods of Solver allow you to pass in an extra assertion. So it's easier for the default to be "we have this extra assertion that's not in the list" and then if you don't you can just set the extra assertion to a constant true.


Fixes #184 add UserHandler

This fixes #184. I dont think you actually need to look at the config object because in Laravel 8.x documentation it's stated that:

By default, Laravel includes an App\Models\User Eloquent model in your app/Models directory.

https://laravel.com/docs/8.x/authentication#introduction-database-considerations

Would you be able to add a corresponding test for this by chance?

@mr-feek yes I can do tests for this. Just need some time so if you want you can draft this PR

FYI: I'm working on alternative, more comprehensive solution

@lptn you can close this then no worries. Looking forward to your solution!

@tm1000
I just created a draft PR, feel free to review and leave some feedback: https://github.com/psalm/psalm-plugin-laravel/pull/326


Bring README.md up to date. Closes #357

Not ready to be merged yet as we should wait for Vagrant 1.8.2 so that ansible_local works reliably.
I mentioned that it's tested under 1.8.2 as of February 2016, so let's hope it gets released by then :)

Halfway through February... fingers crossed for a Vagrant 1.8.2 release... someday!

I'm getting worried https://github.com/mitchellh/vagrant/issues/6726 wont get in before....

@oxyc - At least that issue isn't breaking anything with Drupal VM in particular. It's definitely annoying, but it's not breaking my stuff :)

But it's postponing this awesomeness https://github.com/geerlingguy/drupal-vm/pull/378!

Does this also add travis ci test tags, now that #412 is merged?

What are travis ci test tags?

sorry, I should have been more specific. They are the build status tags that get added to the README, and I see them now.
html tags
not git tags.

I jumped the gun, merged this, and un-updated the Vagrant release to 1.8.1. In #445 I switched the provisioner away from ansible_local. I'll switch it back in #450.


Task/refactor to files

Refactored the huge file to easier to read folders

Will merge.

1. Can we remove those annoying toasts? They accumulate pretty fast and are an obstacle for clicking things on the actual VS Code UI.

Yes, they are for debug. They run natively and don't require opening devtools.

2. Should we remove console logs for safety?

Yeah, maybe have a debug logger.

3. Is the test/suite dir necessary for our MVP and near-future product iterations?

I'd like to add CI in the short term, at least a test to see that it opens (smoke test)


Value When Importing New Variables Does Not Update Token Value

Describe the bug
When a number variable's value is changed and is to be imported (previously imported) into TS, the token's value isn't updated until unless the active set is checked and unchecked.
To Reproduce
Instructions are long, test file has steps to reproduce.
Expected behavior
Token value should update once the new value is imported.
Figma file (optional)
Test File

Added to Featurebase Roadmap as a known issue to test and track with V2 beta testers -	❖ 🪄 Sync variables and styles is now Export to Figma

@keeganedwin FYI this issue only exists if you haven't hooked up the variables to a theme group and theme (pro). Once you do that and the tokens are connected, you can update the variables and run the import and the values will update.

@SamIam4Hyma @six7 this bug is still present in rc9. Even if themes are setup after importing variables and you change a value in figma then import this change, it only updates if you either switch themes or switch between sets
Video

I have raised a PR to fix when a Figma Variable value is updated & imported into the plugin, the token value is instantly reflected 🌟
Cross posting here, as there are another two ❓ scenarios ❓ I'm not sure what the behaviour should be, when variables are imported into the plugin. Perhaps worth refining?
CC @SamIam4Hyma @keeganedwin @six7

Action
Current Behaviour
Expectation

What happens when a Figma Variable is renamed (i.e. test-color to test-color-new)
A new token is created with the name test-color-new
❓

What happens when a Figma Variable is deleted
There is no change in the tokens
❓

This is now merged into the v2 branch 🎉
CC @SamIam4Hyma @keeganedwin will be available to test on the next fix 😄


Remove public modifier in metadata and registry

What is the purpose of the change
Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #10980 (d668eb7) into 3.1 (f8e5a92) will decrease coverage by 4.31%.
The diff coverage is n/a.

:exclamation: Current head d668eb7 differs from pull request most recent head 304a205. Consider uploading reports for the commit 304a205 to get more accurate results

@@             Coverage Diff              @@
##                3.1   #10980      +/-   ##
============================================
- Coverage     68.95%   64.64%   -4.32%
+ Complexity       99       14      -85
============================================
  Files          1462     1418      -44
  Lines         76070    58849   -17221
  Branches      13335     8637    -4698
============================================
- Hits          52457    38042   -14415
+ Misses        18964    16778    -2186
+ Partials       4649     4029     -620

Impacted Files
Coverage Δ

...luster/router/script/ScriptStateRouterFactory.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...zookeeper/curator/CuratorZookeeperTransporter.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...pc/cluster/router/file/FileStateRouterFactory.java
0.00% <0.00%> (-80.96%)
:arrow_down:

...mmon/serialize/fastjson2/FastJson2ObjectInput.java
0.00% <0.00%> (-56.25%)
:arrow_down:

...mon/serialize/fastjson2/FastJson2ObjectOutput.java
0.00% <0.00%> (-56.25%)
:arrow_down:

...dubbo/test/check/exception/DubboTestException.java
50.00% <0.00%> (-50.00%)
:arrow_down:

...o/rpc/cluster/router/script/ScriptStateRouter.java
0.00% <0.00%> (-46.67%)
:arrow_down:

...ting/zookeeper/curator/CuratorZookeeperClient.java
15.38% <0.00%> (-38.84%)
:arrow_down:

...center/initializer/UnpackZookeeperInitializer.java
42.55% <0.00%> (-34.05%)
:arrow_down:

...ubbo/registry/nacos/NacosNamingServiceWrapper.java
54.54% <0.00%> (-33.98%)
:arrow_down:

... and 398 more

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


Height of textarea in modal is wrong

If I have a form with a textarea in a modal popup, the height gets wrongly calculated, because the original element is hidden from the DOM.

Is there a way I can work around that problem?

Same issue inside "cards"

Currently the modal height seems to be set to 70%, independently of the content inside:
https://github.com/Dogfalo/materialize/blob/master/bin/materialize.css#L5928
Unless there is some js to recalculate the height I'm not sure that is a feature.

The height is only for fixed footer modals. regular modals scale in height
On Thu, Feb 19, 2015 at 11:15 AM, Carlos<EMAIL_ADDRESS>wrote:

Currently the modal height seems to be set to 70%, independently of the
content inside:
https://github.com/Dogfalo/materialize/blob/master/bin/materialize.css#L5928
Unless there is some js to recalculate the height I'm not sure that is a
feature.
—
Reply to this email directly or view it on GitHub
https://github.com/Dogfalo/materialize/issues/684#issuecomment-75080736.

--
Doggy sends his greetings from Mars.

The height of the modal window is not the issue, it is the height of the textarea in the modal which is calculated wrong, because the hidden div to calculate seems to be only 100px wide.
If you want to have modals with fixed footer and dynamic height you could try to add this to the css (this is for now the only solution I have found but it is with fixed max-height - 380px seems to be a reasonable max-height for all devices):
.modal {
overflow-y: scroll;
}
.modal .modal-content {
display: block;
max-height: 380px !important;
overflow: scroll;
text-overflow: ellipsis;
}
.modal .modal-footer {
border-top: 1px solid rgba(0, 0, 0, 0.1);
}

I just tested textareas in both cards and regular modals and they both seem to be working correctly. If you are still having an issue let us know specifics

With release 0.95.2 files?

I've noticed it with 0.95.2 (I don't know if it happened before). I've created a jsfiddle with the problem:
http://jsfiddle.net/3e5fgfzo/

Still the same issue on 0.95.3 , Thanks @SmileyChris for the fix!

Fixed in e7d7d150de6b49a045b1d999b1bd16170f56d4aa


set more secure defaults when making governances

I decided to split this off from the work to create the upgraded new wallet form (which would replace NewTreasuryAccountForm).
This PR:

Upgrades NewProgramForm and NewTreasuryAccountForm to v3
Sets healthier defaults in these forms
Disables Community vote tipping in these forms

Here is what the upgraded NewTreasuryAccountForm looks like. I have tested it and it works. I didn't test NewProgramForm since I don't know how, but it's made from the same component (BaseGovernanceForm).

these views have all been replaced instead


data binging and setOnclickListener

Why to use onClickListener on the binding if listener can be defined on xml level?

@Malachiasz Most of the click listeners are defined in xml (recycler-view adapter for example). There's a PR #91 which contains impl. of +/- button in detail page with data-binding as well.
If any listener is forgotten you can make a PR to fix or write down here , letz know it.

ListItemPLantBinding and PlantAdapter set OnClickListener.

@Malachiasz try a PR to optimize?


How to "unsubscribe" or Subscribe to other markets?

Hello,
I am using this:
function updateMarket(dataM) {
bittrex.websockets.client(function() {
console.log('Websocket connected');
bittrex.websockets.subscribe([dataM], function(data) {
if (data.M === 'updateExchangeState') {
data.A.forEach(function(data_for) {
console.log('Market Update for '+ data_for.MarketName+" Price: "+data_for.Fills[0].Rate);
client.emit('marketUpdate', data_for.Fills[0].Rate);
});
}
});
});
};
Is there a way to unsubscribe and stop receiving updates, and then subscribe to other markets???

From my experience, the only way to cancel a subscription is to reconnect (there is no SignalR method to cancel an existing subscription)

@aloysius-pgast  is correct, right now that's the only way.

How do we reconnect properly without keeping the precedent existing subscription alive?


Configure NFS version for Primary Storage

ISSUE TYPE

Improvement Request

COMPONENT NAME
NFS Primary Storage

CLOUDSTACK VERSION
ALL

CONFIGURATION

Primary Storage
NFS

OS / ENVIRONMENT

Ubuntu / CentOS

SUMMARY
NFS Primary Storage mounts are handled by libvirt.
Currently libvirt defaults to NFS version 3 when mounting while it does support NFS version 4 if provided in the XML definition: https://libvirt.org/formatstorage.html#StoragePoolSource
  <source>
    <host name='localhost'/>
    <dir path='/var/lib/libvirt/images'/>
    <format type='nfs'/>
    <protocol ver='4'/>
  </source>

Maybe pass the argument 'nfsvers' to the URL provided to the Management Server and then pass this down to the Hypervisors which generate the XML for libvirt.
EXPECTED RESULTS
Primary Storage is mounted over NFS version 4

looks great, @wido . plan to put it behind a config option? or in the create primary call? (/me having the impertinence of marking it for 4.16)

looks great, @wido . plan to put it behind a config option? or in the create primary call? (/me having the impertinence of marking it for 4.16)

See: https://cloudstack.apache.org/api/apidocs-4.14/apis/createStoragePool.html
We provide the URL in this form:
nfs://my-nfs-server/exports/ps01
We could change that URL by setting:
nfs://my-nfs-server/exports/ps01?nfsvers=4

does that mean that it can be upgraded to version 4 by updating the URL, appending the nfsvers argument? (url is no argument for updateStoragePool now: https://cloudstack.apache.org/api/apidocs-4.14/apis/updateStoragePool.html)
or is any other mech envisioned?

does that mean that it can be upgraded to version 4 by updating the URL, appending the nfsvers argument? (url is no argument for updateStoragePool now: https://cloudstack.apache.org/api/apidocs-4.14/apis/updateStoragePool.html)
or is any other mech envisioned?

I don't think we can do and want to do this for existing primary storages. People could hack the DB and modify it if they really want to.
Otherwise we only support it when adding a new Primary Storage. We just need to parse the URL and store the nfs version in the DB and pass it all the way down to the XML we provide to libvirt.

copy

@wido @DaanHoogland there is a global setting to control the NFS version for secondary storage 'secstorage.nfs.version' perhaps it's easier to include a new global setting for primary storage and pass the version on the storage pool parameters down to the XML? cc @weizhouapache

@nvazquez this could be an option indeed

@GabrielBrascher @wido @nvazquez @sureshanaparti @davidjumani @shwstppr @Pearl1594 @DaanHoogland @weizhouapache - any update on this, who's assigned/working on this? Or should we change milestone? Thanks.

Moved to the 4.17 milestone

Hi @wido @GabrielBrascher is there any update on this?

@nvazquez not yet, this is still on our "backlog".

Ok - moving it tentatively to the 4.18 milestone

Hi @nvazquez I wasn't well the last 2 weeks of past month sustaining a back injury, it will helpful if we can have a small connect regarding the project. I have mailed you if we can connect the coming week then kindly let me know.
Thanks

We do not have any work in progress for this at the moment so moving it out of the <IP_ADDRESS> milestone

This would be fixed by https://github.com/apache/cloudstack/pull/8947

Fixed in #8947


CVE-2014-3803 and CVE-2010-4576

Completed research for CVE-2014-3803

4 points for CVE-2010-4567 and 4 points for CVE-2014-3803!


Quality gets lowered for sjpg

hello guys, I have a doubt with one JPG image, if I load the C-array from the "small image" I can see it in the screen, but looks the colors are lowered in quality. To make a test, I tried to load a normal jpg as C-array but doesnt load, just gives me the no-data message, if I convert it to sjpg, it does load, but also as in the example the quality gets lowered, I already tried with the png decoder and works good with a minor detail but loads, could it be the format of my jpg image?

Actually the convention script takes the jpg as input and do a 90% quality on top of input image. Might be the due to this reason the quality is getting a bit compromised. You can try changing the quality by modifying the line no 57 in converter script but when we keep higher value the conversion somehow takes more time. Will try some fix for this soon.
By the way, I hope you are not comparing the image between 24bit and 16bit, say if you open jpeg in pc and open it via lvgl in 16bit mode, you may find difference. I hope this is not the case here.


Update cgroups to c4b9ac5c7601384c965b9646fc51588

Signed-off-by: Michael Crosby<EMAIL_ADDRESS>

Codecov Report

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

@@           Coverage Diff           @@
##           master    #3423   +/-   ##
=======================================
  Coverage   45.05%   45.05%
=======================================
  Files         113      113
  Lines       12563    12563
=======================================
  Hits         5660     5660
  Misses       6049     6049
  Partials      854      854

Flag
Coverage Δ

#linux
48.98% <ø> (ø)
:arrow_up:

#windows
40.27% <ø> (ø)
:arrow_up:

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 063a4ff...a1f3eba. Read the comment docs.

brings in https://github.com/containerd/cgroups/pull/93, which fixes https://github.com/containerd/containerd/issues/3412


make check (AppImagerTest.Get*Parameters) fails on O3D303 Camera

Hi all,
I am trying to use libo3d3xx with our IFM O3D303 Camera and eventually I want to use o3d3xx-ros to extract the Point Cloud from the camera and use it for navigation of our Robot. I am able to ping the camera but when I run make inside the build directory, I get the following output with 2 Failed tests (AppImagerTest.GetAppParameters and AppImagerTest.GetImagerParameters Tests failed) :
namanpc@namanpc-All-Series:~/libo3d3xx/build$ make
Scanning dependencies of target O3D3XX_CAMERA
[  3%] Creating directories for 'O3D3XX_CAMERA'
[  6%] No download step for 'O3D3XX_CAMERA'
[ 10%] No patch step for 'O3D3XX_CAMERA'
[ 13%] No update step for 'O3D3XX_CAMERA'
[ 16%] Performing configure step for 'O3D3XX_CAMERA'
-- The C compiler identification is GNU 4.8.4
-- The CXX compiler identification is GNU 4.8.4
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Boost version: 1.54.0
-- Found the following Boost libraries:
--   program_options
--   system
-- Found PythonInterp: /usr/bin/python (found version "2.7.6")
-- Looking for include file pthread.h
-- Looking for include file pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Configuring done
-- Generating done
-- Build files have been written to: /home/namanpc/libo3d3xx/build/O3D3XX_CAMERA-prefix/src/O3D3XX_CAMERA-build
[ 20%] Performing build step for 'O3D3XX_CAMERA'
Scanning dependencies of target o3d3xx_camera
[  3%] Building CXX object src/libo3d3xx_camera/CMakeFiles/o3d3xx_camera.dir/net_config.cpp.o
[  6%] Building CXX object src/libo3d3xx_camera/CMakeFiles/o3d3xx_camera.dir/device_config.cpp.o
[ 10%] Building CXX object src/libo3d3xx_camera/CMakeFiles/o3d3xx_camera.dir/spatial_filter_config.cpp.o
[ 13%] Building CXX object src/libo3d3xx_camera/CMakeFiles/o3d3xx_camera.dir/err.cpp.o
[ 16%] Building CXX object src/libo3d3xx_camera/CMakeFiles/o3d3xx_camera.dir/camera.cpp.o
[ 20%] Building CXX object src/libo3d3xx_camera/CMakeFiles/o3d3xx_camera.dir/app_config.cpp.o
[ 23%] Building CXX object src/libo3d3xx_camera/CMakeFiles/o3d3xx_camera.dir/cmdline_opts.cpp.o
[ 26%] Building CXX object src/libo3d3xx_camera/CMakeFiles/o3d3xx_camera.dir/util.cpp.o
[ 30%] Building CXX object src/libo3d3xx_camera/CMakeFiles/o3d3xx_camera.dir/version.cpp.o
[ 33%] Building CXX object src/libo3d3xx_camera/CMakeFiles/o3d3xx_camera.dir/temporal_filter_config.cpp.o
[ 36%] Building CXX object src/libo3d3xx_camera/CMakeFiles/o3d3xx_camera.dir/imager_config.cpp.o
[ 36%] Built target o3d3xx_camera
Scanning dependencies of target o3d3xx_camera_shared
Linking CXX shared library libo3d3xx_camera.so
[ 36%] Built target o3d3xx_camera_shared
Scanning dependencies of target o3d3xx_camera_static
Linking CXX static library libo3d3xx_camera_static.a
[ 36%] Built target o3d3xx_camera_static
Scanning dependencies of target o3d3xx-config
[ 40%] Building CXX object src/bin/CMakeFiles/o3d3xx-config.dir/o3d3xx-config.cpp.o
Linking CXX executable o3d3xx-config
[ 40%] Built target o3d3xx-config
Scanning dependencies of target o3d3xx-dump
[ 43%] Building CXX object src/bin/CMakeFiles/o3d3xx-dump.dir/o3d3xx-dump.cpp.o
Linking CXX executable o3d3xx-dump
[ 43%] Built target o3d3xx-dump
Scanning dependencies of target o3d3xx-ifm-export
[ 46%] Building CXX object src/bin/CMakeFiles/o3d3xx-ifm-export.dir/o3d3xx-ifm-export.cpp.o
Linking CXX executable o3d3xx-ifm-export
[ 46%] Built target o3d3xx-ifm-export
Scanning dependencies of target o3d3xx-ifm-import
[ 50%] Building CXX object src/bin/CMakeFiles/o3d3xx-ifm-import.dir/o3d3xx-ifm-import.cpp.o
Linking CXX executable o3d3xx-ifm-import
[ 50%] Built target o3d3xx-ifm-import
Scanning dependencies of target o3d3xx-imager-types
[ 53%] Building CXX object src/bin/CMakeFiles/o3d3xx-imager-types.dir/o3d3xx-imager-types.cpp.o
Linking CXX executable o3d3xx-imager-types
[ 53%] Built target o3d3xx-imager-types
Scanning dependencies of target o3d3xx-ls
[ 56%] Building CXX object src/bin/CMakeFiles/o3d3xx-ls.dir/o3d3xx-ls.cpp.o
Linking CXX executable o3d3xx-ls
[ 56%] Built target o3d3xx-ls
Scanning dependencies of target o3d3xx-reboot
[ 60%] Building CXX object src/bin/CMakeFiles/o3d3xx-reboot.dir/o3d3xx-reboot.cpp.o
Linking CXX executable o3d3xx-reboot
[ 60%] Built target o3d3xx-reboot
Scanning dependencies of target o3d3xx-reset
[ 63%] Building CXX object src/bin/CMakeFiles/o3d3xx-reset.dir/o3d3xx-reset.cpp.o
Linking CXX executable o3d3xx-reset
[ 63%] Built target o3d3xx-reset
Scanning dependencies of target o3d3xx-rm
[ 66%] Building CXX object src/bin/CMakeFiles/o3d3xx-rm.dir/o3d3xx-rm.cpp.o
Linking CXX executable o3d3xx-rm
[ 66%] Built target o3d3xx-rm
Scanning dependencies of target o3d3xx-version
[ 70%] Building CXX object src/bin/CMakeFiles/o3d3xx-version.dir/o3d3xx-version.cpp.o
Linking CXX executable o3d3xx-version
[ 70%] Built target o3d3xx-version
Scanning dependencies of target gtest
[ 73%] Building CXX object test/gtest_bin/CMakeFiles/gtest.dir/src/gtest-all.cc.o
Linking CXX shared library libgtest.so
[ 73%] Built target gtest
Scanning dependencies of target gtest_main
[ 76%] Building CXX object test/gtest_bin/CMakeFiles/gtest_main.dir/src/gtest_main.cc.o
Linking CXX shared library libgtest_main.so
[ 76%] Built target gtest_main
Scanning dependencies of target o3d3xx-camera-tests
[ 80%] Building CXX object test/CMakeFiles/o3d3xx-camera-tests.dir/o3d3xx-camera-tests.cpp.o
[ 83%] Building CXX object test/CMakeFiles/o3d3xx-camera-tests.dir/o3d3xx-camera-testrunner.cpp.o
[ 86%] Building CXX object test/CMakeFiles/o3d3xx-camera-tests.dir/o3d3xx-import-export-tests.cpp.o
[ 90%] Building CXX object test/CMakeFiles/o3d3xx-camera-tests.dir/o3d3xx-app-imager-tests.cpp.o
[ 93%] Building CXX object test/CMakeFiles/o3d3xx-camera-tests.dir/o3d3xx-temporal-filter-tests.cpp.o
[ 96%] Building CXX object test/CMakeFiles/o3d3xx-camera-tests.dir/o3d3xx-spatial-filter-tests.cpp.o
[100%] Building CXX object test/CMakeFiles/o3d3xx-camera-tests.dir/o3d3xx-basic-tests.cpp.o
Linking CXX executable o3d3xx-camera-tests
[100%] Built target o3d3xx-camera-tests
[ 23%] Performing test step for 'O3D3XX_CAMERA'
[  5%] Built target gtest
[ 60%] Built target o3d3xx_camera
[ 60%] Built target o3d3xx_camera_shared
[ 65%] Built target gtest_main
[100%] Built target o3d3xx-camera-tests
Scanning dependencies of target check
[==========] Running 43 tests from 6 test cases.
[----------] Global test environment set-up.
[----------] 17 tests from Camera_Tests
[ RUN      ] Camera_Tests.Ctor
[       OK ] Camera_Tests.Ctor (0 ms)
[ RUN      ] Camera_Tests.GetXMLRPCURLPrefix
[       OK ] Camera_Tests.GetXMLRPCURLPrefix (1 ms)
[ RUN      ] Camera_Tests.GetAllParameters
[       OK ] Camera_Tests.GetAllParameters (595 ms)
[ RUN      ] Camera_Tests.GetParameter
[       OK ] Camera_Tests.GetParameter (1105 ms)
[ RUN      ] Camera_Tests.GetSWVersion
[       OK ] Camera_Tests.GetSWVersion (17 ms)
[ RUN      ] Camera_Tests.GetApplicationList
[       OK ] Camera_Tests.GetApplicationList (13 ms)
[ RUN      ] Camera_Tests.RequestSession
[       OK ] Camera_Tests.RequestSession (38 ms)
[ RUN      ] Camera_Tests.CancelSession
[       OK ] Camera_Tests.CancelSession (41 ms)
[ RUN      ] Camera_Tests.Heartbeat
[       OK ] Camera_Tests.Heartbeat (56 ms)
[ RUN      ] Camera_Tests.SetOperatingMode
[       OK ] Camera_Tests.SetOperatingMode (357 ms)
[ RUN      ] Camera_Tests.GetDeviceConfig
[       OK ] Camera_Tests.GetDeviceConfig (873 ms)
[ RUN      ] Camera_Tests.ActivateDisablePassword
[       OK ] Camera_Tests.ActivateDisablePassword (446 ms)
[ RUN      ] Camera_Tests.SetDeviceConfig
[       OK ] Camera_Tests.SetDeviceConfig (2284 ms)
[ RUN      ] Camera_Tests.DeviceConfig_JSON
[       OK ] Camera_Tests.DeviceConfig_JSON (270 ms)
[ RUN      ] Camera_Tests.GetNetParameters
[       OK ] Camera_Tests.GetNetParameters (356 ms)
[ RUN      ] Camera_Tests.NetConfig
[       OK ] Camera_Tests.NetConfig (417 ms)
[ RUN      ] Camera_Tests.NetConfig_JSON
[       OK ] Camera_Tests.NetConfig_JSON (410 ms)
[----------] 17 tests from Camera_Tests (7280 ms total)
[----------] 1 test from ImportExport_Tests
[ RUN      ] ImportExport_Tests.ImportExportApp
[       OK ] ImportExport_Tests.ImportExportApp (964 ms)
[----------] 1 test from ImportExport_Tests (964 ms total)
[----------] 15 tests from AppImagerTest
[ RUN      ] AppImagerTest.CopyDeleteApplication
[       OK ] AppImagerTest.CopyDeleteApplication (1123 ms)
[ RUN      ] AppImagerTest.CreateApplication
[       OK ] AppImagerTest.CreateApplication (713 ms)
[ RUN      ] AppImagerTest.ChangeAppNameAndDescription
[       OK ] AppImagerTest.ChangeAppNameAndDescription (1016 ms)
[ RUN      ] AppImagerTest.EditApplication
[       OK ] AppImagerTest.EditApplication (1132 ms)
[ RUN      ] AppImagerTest.GetAppParameters
/home/namanpc/libo3d3xx/modules/camera/test/o3d3xx-app-imager-tests.cpp:131: Failure
Value of: 8
Expected: params.size()
Which is: 9
[  FAILED  ] AppImagerTest.GetAppParameters (1466 ms)
[ RUN      ] AppImagerTest.AppConfig
[       OK ] AppImagerTest.AppConfig (1866 ms)
[ RUN      ] AppImagerTest.AppConfig_JSON
[       OK ] AppImagerTest.AppConfig_JSON (1723 ms)
[ RUN      ] AppImagerTest.GetAvailableImagerTypes
[       OK ] AppImagerTest.GetAvailableImagerTypes (1489 ms)
[ RUN      ] AppImagerTest.ChangeImagerType
[       OK ] AppImagerTest.ChangeImagerType (2840 ms)
[ RUN      ] AppImagerTest.GetImagerParameters
/home/namanpc/libo3d3xx/modules/camera/test/o3d3xx-app-imager-tests.cpp:279: Failure
Expected: params.at("MaxAllowedLEDFrameRate") doesn't throw an exception.
Actual: it throws.
[  FAILED  ] AppImagerTest.GetImagerParameters (1761 ms)
[ RUN      ] AppImagerTest.GetImagerParameterLimits
[       OK ] AppImagerTest.GetImagerParameterLimits (2879 ms)
[ RUN      ] AppImagerTest.ImagerConfig
[       OK ] AppImagerTest.ImagerConfig (4629 ms)
[ RUN      ] AppImagerTest.ImagerConfigValueOutOfRange
[       OK ] AppImagerTest.ImagerConfigValueOutOfRange (2951 ms)
[ RUN      ] AppImagerTest.ImagerConfig_JSON
[       OK ] AppImagerTest.ImagerConfig_JSON (1488 ms)
[ RUN      ] AppImagerTest.Exposure
[       OK ] AppImagerTest.Exposure (3720 ms)
[----------] 15 tests from AppImagerTest (30800 ms total)
[----------] 4 tests from TemporalFilterTest
[ RUN      ] TemporalFilterTest.TemporalFilterConfig_General
[       OK ] TemporalFilterTest.TemporalFilterConfig_General (1061 ms)
[ RUN      ] TemporalFilterTest.GetTemporalFilterParameters
[       OK ] TemporalFilterTest.GetTemporalFilterParameters (1975 ms)
[ RUN      ] TemporalFilterTest.GetTemporalFilterParameterLimits
[       OK ] TemporalFilterTest.GetTemporalFilterParameterLimits (2019 ms)
[ RUN      ] TemporalFilterTest.TemporalFilterConfig_JSON
[       OK ] TemporalFilterTest.TemporalFilterConfig_JSON (2030 ms)
[----------] 4 tests from TemporalFilterTest (7085 ms total)
[----------] 4 tests from SpatialFilterTest
[ RUN      ] SpatialFilterTest.SpatialFilterConfig_General
[       OK ] SpatialFilterTest.SpatialFilterConfig_General (783 ms)
[ RUN      ] SpatialFilterTest.GetSpatialFilterParameters
[       OK ] SpatialFilterTest.GetSpatialFilterParameters (1780 ms)
[ RUN      ] SpatialFilterTest.GetSpatialFilterParameterLimits
[       OK ] SpatialFilterTest.GetSpatialFilterParameterLimits (2021 ms)
[ RUN      ] SpatialFilterTest.SpatialFilterConfig_JSON
[       OK ] SpatialFilterTest.SpatialFilterConfig_JSON (1858 ms)
[----------] 4 tests from SpatialFilterTest (6442 ms total)
[----------] 2 tests from General_Tests
[ RUN      ] General_Tests.Exceptions
[       OK ] General_Tests.Exceptions (0 ms)
[ RUN      ] General_Tests.Version
[       OK ] General_Tests.Version (0 ms)
[----------] 2 tests from General_Tests (0 ms total)
[----------] Global test environment tear-down
[==========] 43 tests from 6 test cases ran. (52571 ms total)
[  PASSED  ] 41 tests.
[  FAILED  ] 2 tests, listed below:
[  FAILED  ] AppImagerTest.GetAppParameters
[  FAILED  ] AppImagerTest.GetImagerParameters
2 FAILED TESTS
make[6]: *** [test/CMakeFiles/check] Error 1
make[5]: *** [test/CMakeFiles/check.dir/all] Error 2
make[4]: *** [test/CMakeFiles/check.dir/rule] Error 2
make[3]: *** [check] Error 2
make[2]: *** [O3D3XX_CAMERA-prefix/src/O3D3XX_CAMERA-stamp/O3D3XX_CAMERA-test] Error 2
make[1]: *** [CMakeFiles/O3D3XX_CAMERA.dir/all] Error 2
make: *** [all] Error 2
After running o3d3xx-dump, this is the output :
namanpc@namanpc-All-Series:~/libo3d3xx/build/O3D3XX_CAMERA-prefix/src/O3D3XX_CAMERA-build/src/bin$ ./o3d3xx-dump
{
"o3d3xx":
{
"libo3d3xx": "402",
"Date": "Wed Apr 20 10:31:57 2016",
"HWInfo":
{
"Mainboard": "#!02_M381_003_02178445_008022954",
"Illumination": "#!02_I300_001_02118157_008001175",
"MiraSerial": "0430-5384-0021-059c",
"MACAddress": "00:02:01:40:2C:0C",
"Frontend": "#!02_F342_002_15_00289_802259343",
"Diagnose": "#!02_D322_C30_02157009_008023093",
"Connector": "#!02_A300_001_02105252_008001175"
},
"SWVersion":
{
"IFM_Software": "1.3.1001",
"Linux": "Linux version 3.11.0-00005-g2394d14 (eswadmin@dettlx79) (gcc version 4.7.2 (GCC) ) #1 SMP Wed Nov 25 16:10:41 CET 2015",
"Diagnostic_Controller": "0.3.87",
"ELDK": "GOLDENEYE_ELDK-2015-11-26_16-11-02-5321dac5357219d1408dbf7f53f164e8c138302a",
"Calibration_Version": "0.9.0",
"Calibration_Device": "00:02:01:40:2c:0c",
"Main_Application": "0.4.100",
"Algorithm_Version": "1.2.6"
},
"Device":
{
"Name": "New sensor",
"Description": "",
"ActiveApplication": "1",
"PcicEipEnabled": "false",
"PcicTcpPort": "50010",
"PcicProtocolVersion": "3",
"IOLogicType": "1",
"IODebouncing": "true",
"IOExternApplicationSwitch": "0",
"SessionTimeout": "30",
"ServiceReportPassedBuffer": "15",
"ServiceReportFailedBuffer": "15",
"ExtrinsicCalibTransX": "0",
"ExtrinsicCalibTransY": "0",
"ExtrinsicCalibTransZ": "0",
"ExtrinsicCalibRotX": "0",
"ExtrinsicCalibRotY": "0",
"ExtrinsicCalibRotZ": "0",
"EvaluationFinishedMinHoldTime": "10",
"SaveRestoreStatsOnApplSwitch": "true",
"IPAddressConfig": "0",
"PasswordActivated": "false",
"OperatingMode": "0",
"DeviceType": "",
"ArticleNumber": "",
"ArticleStatus": "",
"UpTime": "1.144125602437825e-316",
"ImageTimestampReference": "23157600",
"TemperatureFront1": "6.953222953505516e-310",
"TemperatureFront2": "1.144149317588825e-316",
"TemperatureIMX6": "1.144161175164325e-316",
"TemperatureIllu": "6.953189366787785e-310"
},
"Net":
{
"MACAddress": "",
"NetworkSpeed": "0",
"StaticIPv4Address": "<IP_ADDRESS>",
"StaticIPv4SubNetMask": "<IP_ADDRESS>",
"StaticIPv4Gateway": "<IP_ADDRESS>",
"UseDHCP": "false"
},
"Apps":
[
{
"Name": "Sample Application",
"Description": "",
"TriggerMode": "1",
"PcicTcpResultSchema": "{ "layouter": "flexible", "format": { "dataencoding": "ascii" }, "elements": [ { "type": "string", "value": "star", "id": "start_string" }, { "type": "blob", "id": "normalized_amplitude_image" }, { "type": "blob", "id": "distance_image" }, { "type": "blob", "id": "x_image" }, { "type": "blob", "id": "y_image" }, { "type": "blob", "id": "z_image" }, { "type": "blob", "id": "confidence_image" }, { "type": "blob", "id": "diagnostic_data" }, { "type": "string", "value": "stop", "id": "end_string" } ] }",
"PcicEipResultSchema": "{ "layouter": "flexible", "format": { "dataencoding": "binary", "order": "big" }, "elements" : [ { "type": "string", "value": "star", "id": "start_string" }, { "type": "records", "id": "models", "elements": [ { "type": "int16", "id": "boxFound" }, { "type": "int16", "id": "width", "format": { "scale": 1000 } }, { "type": "int16", "id": "height", "format": { "scale": 1000 } }, { "type": "int16", "id": "length", "format": { "scale": 1000 } }, { "type": "int16", "id": "xMidTop", "format": { "scale": 1000 } }, { "type": "int16", "id": "yMidTop", "format": { "scale": 1000 } }, { "type": "int16", "id": "zMidTop", "format": { "scale": 1000 } }, { "type": "int16", "id": "yawAngle" }, { "type": "int16", "id": "qualityLength" }, { "type": "int16", "id": "qualityWidth" }, { "type": "int16", "id": "qualityHeight" } ] }, { "type": "string", "value": "stop", "id": "end_string" } ] }",
"LogicGraph": "{"IOMap": {"OUT1": "RFT","OUT2": "AQUFIN"},"blocks": {"B00001": {"pos": {"x": 200,"y": 200},"properties": {},"type": "PIN_EVENT_IMAGE_ACQUISITION_FINISHED"},"B00002": {"pos": {"x": 200,"y": 75},"properties": {},"type": "PIN_EVENT_READY_FOR_TRIGGER"},"B00003": {"pos": {"x": 600,"y": 75},"properties": {"pulse_duration": 0},"type": "DIGITAL_OUT1"},"B00005": {"pos": {"x": 600,"y": 200},"properties": {"pulse_duration": 0},"type": "DIGITAL_OUT2"}},"connectors": {"C00000": {"dst": "B00003","dstEP": 0,"src": "B00002","srcEP": 0},"C00001": {"dst": "B00005","dstEP": 0,"src": "B00001","srcEP": 0}}}",
"Type": "Camera",
"Index": "1",
"Id": "32358960",
"Imager":
{
"Channel": "0",
"ClippingBottom": "131",
"ClippingLeft": "0",
"ClippingRight": "175",
"ClippingTop": "0",
"ContinuousAutoExposure": "false",
"EnableAmplitudeCorrection": "true",
"EnableFastFrequency": "false",
"EnableFilterAmplitudeImage": "true",
"EnableFilterDistanceImage": "true",
"EnableRectificationAmplitudeImage": "false",
"EnableRectificationDistanceImage": "false",
"ExposureTime": "5000",
"ExposureTimeList": "125;5000",
"ExposureTimeRatio": "40",
"FrameRate": "5",
"MinimumAmplitude": "42",
"Resolution": "0",
"ClippingCuboid": "{"XMin": -3.402823e+38, "XMax": 3.402823e+38, "YMin": -3.402823e+38, "YMax": 3.402823e+38, "ZMin": -3.402823e+38, "ZMax": 3.402823e+38}",
"SpatialFilterType": "0",
"SymmetryThreshold": "0",
"TemporalFilterType": "0",
"ThreeFreqMax2FLineDistPercentage": "80",
"ThreeFreqMax3FLineDistPercentage": "80",
"TwoFreqMaxLineDistPercentage": "80",
"Type": "under5m_moderate",
"MaxAllowedLEDFrameRate": "0",
"SpatialFilter":
{
"Type": "0",
"TypeStr_": "Off"
},
"TemporalFilter":
{
"Type": "0",
"TypeStr_": "Off"
}
}
}
]
}
}
I have already tried resetting the o3d3xx camera by running the command o3d3xx-reset but I still got the same output.
Also, libo3d3xx: version=0.4.2 and "IFM_Software": "1.3.1001".
Any help will be appreciated.
Thanks!

You should update your camera to firmware version 1.4.1639. On the main README we maintain a software compatibility matrix that maps compatible versions of libo3d3xx to the associated IFM firmware. The firmware is available in the firmware directory of this source distribution. The easiest way to do the update is to run o3d3xx-reboot -r from your build directory (since you don't have it installed yet). Then hit the sensor's internall http server at: http://<IP_ADDRESS>:8080. Here you can upload the firmware CPIO archive.

Thanks tpanzarella! It worked :)


IGNITE-6254 : Fixed assertions for req.txState().

The ticket is resolved, closing PR. Feel free to reopen if it is needed.


Changes to MessageEvent

API | Common | Vanilla | Forge
This PR makes some substantial changes to how MessageEvents are handled. Instead of passing around a Text object, the event now contains a MessageFormatter which can be used to modify the event's message in a more reliable and modular fashion. This will make interactions and compatibility between chat plugins a lot easier. Previous methods like getOriginalMessage, getRawMessage, getMessage, and setMessage still behave as expected except instead of Optionals, a non-null Text is always returned. Developers should use setMessageCancelled to cancel the sending instead of setting the message to null.

Some example uses:
Let's say I would like to insert a "group" prefix to the message but I also would like to keep existing prefixes that other plugins may or may not have already applied. I can do something like:
class GroupApplier extends SimpleTextTemplateApplier {
    public GroupApplier() {
        super(of('[', arg("group"), "] "));
    }
}

@Listener
void onChat(MessageChannelEvent.Chat event) {
    GroupApplier applier = new GroupApplier();
    applier.setParameter("group", Text.builder("admin").color(TextColors.RED));
    event.getFormatter().getHeader().insert(0, applier);
}

On an unaltered message, this will produce something equivalent to:
[<red>admin</red>] <NAME> MESSAGE
Now lets say another plugin wants to override that prefix and make it say "mod" instead of "admin". Well then they can do:
event.getHeader().forEach(GroupApplier.class, applier -> applier.setParameter("group", Text.builder("mod").color(TextColors.AQUA));

These are only a few of the many uses this PR will provide.
Note: This PR depends on https://github.com/SpongePowered/SpongeAPI/pull/1079. https://github.com/SpongePowered/SpongeAPI/pull/1079 should be merged into master and then into bleeding before this PR is merged.

@windy1 Instead of continuously closing and opening new PRs you could just update them.
This makes tracking the discussion a lot easier.

@ST-DDT Trust me it's not intentional :P I keep messing up rebasing the feature/text-template branch....

@windy1 You can undo the changes with git reflog and then force-push the old versions.

Well you can still fix / recreate your changes and then force push to the branch associated with the PRs. Even if the original branch is horribly broken a simple force push with a working state will also fix the PR.

Okay -- I'd like to get this merged ASAP now that TextTemplates are in. I'm still partial to "header, body, footer" but if someone can make a compelling argument against it other than "I like 'x' better" I'll change it.


validation: ensure non-empty poolName

We wanted to have this validation, but we didn't actually add it yet :)
So, if the user supplies a PoolName, it must be non-empty string: the rest of our code expects
it that way, and it's a pretty reasonable restriction anyway.
Add validation to enforce this, and simplify code after the validation.

/lgtm


fix: avoid duplicate trigger of session fetch hook due to request retry

The nitro session fetch hook is likely to be used for implementing the necessary checks to ensure token validity, this might require making additional network requests to the pertinent authentication server.
The current implementation results in the aforementioned checks being made twice whenever the session cookie is present, and the earlier checks have failed (returned throw createError() within session fetch hook), hence resulting in unnecessary overhead.

Nice one @Diizzayy ❤


Apache loading sqlsrv.so crashes with error invalid free(). build with -Ggdb -O0 is a workaround

.+Please check the FAQ (frequently-asked questions) first. If you have other questions or something to report, please address the following:
+## PHP Driver version or file name
+pdo_sqlsrv 5.9.0   stable and pdo_sqlsrv 5.9.0   stable
+## SQL Server version
+Microsoft SQL Server 2019 (RTM) - 15.0.2000.5 (X64) Sep 24 2019 13:48:23 on WIndows10
+## Client operating system
+Linux  5.4.0-84-generic #94-Ubuntu SMP Thu Aug 26 20:27:37 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
+## PHP version
+PHP 8.0.10 (cli) (built: Aug 26 2021 15:50:07) ( NTS )
+## Microsoft ODBC Driver version
+Driver={ODBC Driver 17 for SQL Server};  (libmsodbcsql-17.8.so.1.1)
+## Table schema
+
+## Problem description
+Running Ubuntu Apache Webserver (Server version: Apache/2.4.41 (Ubuntu)) with /usr/lib/apache2/modules/libphp8.0.so
loaded. Trying to add both (or either) pdo_sqlsrv.so or sqlsrv.so via enablin modules in the php ini.
+## Expected behavior and actual behavior

I expected the driver to load seamlessly - but the apache server crashes. I have supplied a backtrace in attached file.
+## Repro code or steps to reproduce
sudo pecl install sqlsrv ; sudo service apache2 restart

I rebuilt the driver with CFLAGS and CPPFLAGS set to -g -O0 and it crashed.
I then rebuilt the driver with CFLAGS and CPPFLAGS set to -ggdb -O0 and it is now working.
in analysing the crash crash_o0_g gdb states warning: .dynamic section for "/usr/lib/php/20200930/sqlsrv.so" is not at the expected address (wrong library or version mismatch?), I am not sure if this is because of unoptimised code (I suspect not) but maybe it is indicating my problem. This is not a production system I am working on, and so I can work on my system with the debug build.
I have attached a testsqlsrv.php which runs from the command line and so the issue is not with php module setup. It is rather to do with the integration with apache.
sqlsrv_O0_g_crash.txt
sqlsrv_O2_g_crash.txt
sqlsrv_environ.txt

Attached is the gcc version.
An observation which I don't know how to address is outlined by % file /usr/lib/php/20200930/*.so
...
/usr/lib/php/20200930/pdo.so:        ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=08cd37724e59464b8ba8ac45b78abd02deea1ce1, stripped
/usr/lib/php/20200930/pdo_sqlsrv.so: ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked, BuildID[sha1]=20fd15438f6dacabf4012a8d3eedbe7cee19da89, with debug_info, not stripped
/usr/lib/php/20200930/pgsql.so:      ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=bbac5e092887db2694e1a205bd047309cee30a7d, stripped
/.
The only .so file with (GNU/Linux) are slqsrv.so and pdo_sqlsrv.so. maybe it explains the issue ?
/tmp$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 9.3.0-17ubuntu1~20.04' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-9 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-9-HskZEa/gcc-9-9.3.0/debian/tmp-nvptx/usr,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)

Hi @tombay , which ubuntu are you using?
If I understand you correctly, you were trying to debug the drivers? In that case, you might need to build PHP from source with the --enable-debug option. Without altering the flags, try this first. If necessary, modify the config.m4 files to use -O0 instead of -O2 to avoid compiler optimizations.
Will also do some investigation and get back to you.

Hi Jenny.
Ubuntu 20.04 (lts).
I am running with -O0 -ggdb. I am only running like that so that the driver loads and Apache keeps running. I was just suspicious that it is a memory allocation issue - interaction between stdc and c++ .
I'd someone could suggest how to have the image link as SYSV I would do that. I had a cursory look but could see no ld flags to do that. I am quite happy for someone else to debug the driver, I am glad it loads so I can develop my self app. It works and so it's probably a build environment issue I can't resolve %-?

Woops

I didn't mean to close this. 😕

hi @tombay , it's likely something to do with your settings or env in Ubuntu 20.04. I tested on both Ubuntu 20.04 and Ubuntu 18.04 (they are relatively clean) and found no issues with Apache. The images below are cropped from Ubuntu 20.04:

How did you install PHP or Apache? Did you follow our instructions? Or did you build from source?

Hi @yitam .
Thanks for checking this out.
Apache came from the Ubuntu archive
My php was installed from the ondrej repositories.
I spent some time trying to ascertain what was causing the crashes.
With CFLAGS and CXXFLAGS set to -ggdb -O0 the shared images load.
With CFLAGS and CXXFLAGS set to -ggdb -O2 the shared images crash.
I will close this defect as it does seem environmental issue. My development task was involving a php framework and pgsql,mysql,sqlsrv. Now that I have sqlsrv working I can get back to it. Out of interest I built Apache/2.5.1-dev and the images worked. But ubuntu 20.04 (my world) standard Apache is the 2.4 stream %-)
Thanks again for your assistance
Fyi
$ grep -i php /etc/apt/sources.list.d/*|grep focal
/etc/apt/sources.list.d/ondrej-ubuntu-php-focal.list:deb http://ppa.launchpad.net/ondrej/php/ubuntu focal main
/etc/apt/sources.list.d/ondrej-ubuntu-php-focal.list:# deb-src http://ppa.launchpad.net/ondrej/php/ubuntu focal main
Apache came from the Ubuntu archive
$ apt-cache showpkg apache2
Package: apache2
Versions:
2.4.41-4ubuntu3.4 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_focal-updates_main_binary-amd64_Packages) (/var/lib/dpkg/status)
Description Language:
File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_focal_main_binary-amd64_Packages


Allow users to skip specific preflight checks

Allow users to skip specific preflight checks using a new flag skip-preflight-check
The new flag was added since changing the flag type to string slice from bool requires an input value which would break any automation calling Sonobuoy from the CLI with --skip-preflight and no value.

There is some issue; the tests do seem to have legitimate failures:
    sonobuoy_integration_test.go:119: Expected "run --wait -f /tmp/gen.2299213011.yaml" to not error but got error: "exit status 1" with stdout: "" and stderr: "time=\"2022-08-02T23:05:02Z\" level=error msg=\"Preflight checks failed\"\ntime=\"2022-08-02T23:05:02Z\" level=error msg=\"invalid preflight check \"\n"

Continuing with review though.


toplevel set() fails to make a copy of passed-in sets

The set() function returns its argument if it is a Set<Element> rather than making an immutable copy.
Sort of a crummy test case for this:
    object set1 satisfies Set<String> & Identifiable {
        clone() => nothing;
        iterator() => nothing;
        hash => nothing;
        equals(Object that) => nothing;
    }
    if (is Identifiable set2 = set(set1)) {
        assert (!set1 === set2); // fails
    }

Oops, wrong repo. Moved to https://github.com/ceylon/ceylon/issues/5749


Document #[system_set(base)]

I had to add #[system_set(base)] to an enum that derives SystemSet to make it build. I have zero idea why, nor what #[system_set(base)] does. I just found that my app builds with it and doesn't without. This was a very wild guess; I just saw that line in some Bevy code and tried it because my sets are inserted between built-in sets so they might be somehow related to some "base" thing. Maybe?

Basw sets are removed in 0.11.


nuttx-bringup: make archives modifies NuttX submodule

Before make archives:
/NuttX git:remotes/origin/upstream git status
HEAD detached at 69283d3
nothing to commit, working directory clean

After make archives:
/NuttX git:remotes/origin/upstream git status                                                                                ✱ ◼
HEAD detached at 69283d3
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   nuttx/include/signal.h
	modified:   nuttx/include/stdio.h
	modified:   nuttx/include/stdlib.h
	modified:   nuttx/include/sys/stat.h

Untracked files:
  (use "git add <file>..." to include in what will be committed)

	nuttx/.patchedpx4common
	nuttx/arch/arm/include/math.h

no changes added to commit (use "git add" and/or "git commit -a")

Output of git diff

@thomasgubler The nuttx_bringup build supports build time patching of the things we can not get into nuttx upstream (PX4 specific requirements that may be as simple as gcc pragmas)
The make targets nuttxpatches and cleannuttxpatches apply and remove the patches.
Currently
archives depends on nuttxpatches
distclean depends on cleannuttxpatches
So a make distclean (or cleannuttxpatches) will bring NuttX back to unmodified state.
Would you like this to work differently?

The problem is that the NuttX submodule shows up as modified when running git status in the Firmware repo. So you can never be sure if you have a clean version of NuttX. Are the patches required for the Firmware build? Would it maybe make sense to run cleannuttxpatches automatically after a archives build?

For the developer whose primary focus is on PX4 Firmware Yes, it would make sense to run cleannuttxpatches automatically after a archives build. So I totally agree I think that should be the default.
For developer whose primary focus is on Nuttx development for PX4. I would like to see changes persist.
When I added the patching I was thinking there were common (one time patches) and possible per hw targets patches. (I still have not seen a case for the per hw patching yet.)
I would like to to see some sort if a "mode" setting that would allow one to focus on a HW platform and be able to build the PX4 Firmware on top of Nuttx without exporting the archive. This would allow the developer to incrementally build Nuttx and save a lot of time.
We need some makefile magic - I would appreciate any suggestions and help implementing same.

For developer whose primary focus is on Nuttx development for PX4. I would like to see changes persist.

You want to see the changes persist but do you really want them to show up as a change in git? Ideally git would only show changes if you did a change to the patch? (which would again be ok for the developer with px4 firmware focus)

We should probably have a Skype discussion on this. I am david_s5

Cmake made this a non-issue


Noise Gate Demo

This code enables a demo for the noise gate where the noise gate can be used to mute white noise during a pause in speech. There are 4 new files:

noisegate.html  resembles the structure of bitcrusher.html
src/noisegate-demo.js resembles the structure of src/bitcrusher-demo.js
sound/white_noise.ogg is white noise
sound/speech.ogg  is a speech sample with a pause of the same duration as the noise file.

In addition, there is a slight modification to src/noisegate-script-processor.js. I changed the default threshold from 0 to -100. Zero does not make sense as a default threshold since that mutes all sound by default. In addition, I changed the logic supporting the default assignment of parameters. If the default value is nonzero, the current code does not allow for that default to be overriden to
zero since (0 || |nonZeroValue|)  evaluates to a nonzero value.
The demo can be found at http://rawgit.com/GoogleChrome/web-audio-samples/fcca7efd31fe7a5e8f3b5a391150521b3ff55243/audio-worklet/noisegate.html

Can you suggest the right parameters for the demo? I tried a couple of config but none of them works as I expected.

The latest demo can be found here. In the latest commit,

I created a new, longer audio sample, where I try to speak quickly and take longer pauses.
With the noise gain at 1 and the threshold at -40db, the noise is inaudible during my pauses.
A toggle button enables switching between active and bypass modes.
Other stylistic changes in response to comment.

The new demo can be found at http://rawgit.com/GoogleChrome/web-audio-samples/372779777b3bc4b2c3c4f25674bbc79fbf916978/audio-worklet/noisegate.html


integrate with Google Analytics

Hi MoveOn,
_

I'm going to add a bunch of issues that might be not be issues, but as we discussed SB this morning with Sandra, I wanted to share them for the hackathon next week for further analysis or dev.

_
when a visitor clicks on one of the shared link, instead of only redirecting to the petition url
http://www.example.com/story/the-world-is-burning?abid=123&abver=abc789
it would add &utm_campaign=sb_abc789&utm_medium=facebook&utm_source=xyz
If the shared url is ttps://share.example.com/r/0/www.example.com/story/the-world-is-burning?utm_campaign=sb_abc789&utm_medium=facebook&utm_source=xyz and SB does include the utm params, it might be enough
#techsummithackathon

++ to this.


Add GAV to XML Report

See https://github.com/jeremylong/DependencyCheck/issues/665 - the gradle plugin needs to be updated to take advantage of this new feature.

After investigating this a bit more - this is not simple due to the less structured nature of gradle. These elements appear to be located in different places depending on which publishing plugin you are using.

This was completed with the 2.0.0 release.


Change bson-codec to bson-mongodb

bson-codec version 1.0.0 remains unchanged. bson-mongodb starts from 1.0.1.

Published


启动报错

C:\Users\Administrator\bilive_client>npm start

<EMAIL_ADDRESS>start C:\Users\Administrator\bilive_client
node build/app.js

(node:2512) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or dir
ectory, scandir 'C:\Users\Administrator\bilive_client\build\bilive\plugins'
(node:2512) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This
error originated either by throwing inside of an async function without a catch
block, or by rejecting a promise which was not handled with .catch(). (rejection
id: 1)
(node:2512) [DEP0018] DeprecationWarning: Unhandled promise rejections are depre
cated. In the future, promise rejections that are not handled will terminate the
Node.js process with a non-zero exit code.

哦，昨天更新的去除了所有插件，忘了加个空目录了

From: s1073700227<EMAIL_ADDRESS>Sent: Sunday, June 23, 2019 11:29:26 AM
To: bilive/bilive_client
Cc: Subscribed
Subject: [bilive/bilive_client] 启动报错 (#138)
C:\Users\Administrator\bilive_client>npm start
<EMAIL_ADDRESS>start C:\Users\Administrator\bilive_client
node build/app.js
(node:2512) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or dir
ectory, scandir 'C:\Users\Administrator\bilive_client\build\bilive\plugins'
(node:2512) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This
error originated either by throwing inside of an async function without a catch
block, or by rejecting a promise which was not handled with .catch(). (rejection
id: 1)
(node:2512) [DEP0018] DeprecationWarning: Unhandled promise rejections are depre
cated. In the future, promise rejections that are not handled will terminate the
Node.js process with a non-zero exit code.
―
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/bilive/bilive_client/issues/138?email_source=notifications&email_token=ADGFLUVOZTN6QWIZZ567ASDP33UZNA5CNFSM4H2YADGKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G3D466A, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADGFLUQANTX2S3OUPLBT7JTP33UZNANCNFSM4H2YADGA.


Added Swift 4.2 commit for CoreStore

Pull Request Description
Added commit hash for CoreStore's Swift 4.2 support.
Acceptance Criteria
To be accepted into the Swift source compatibility test suite, a project must:

[x] be an Xcode or swift package manager project
[x] support building on either Linux or macOS
[x] target Linux, macOS, or iOS/tvOS/watchOS device
[x] be contained in a publicly accessible git repository
[x] maintain a project branch that builds against Swift 4.0 and passes any unit tests
[x] have maintainers who will commit to resolve issues in a timely manner
[x] be compatible with the latest GM/Beta versions of Xcode and swiftpm
[x] add value not already included in the suite
[x] be licensed with one of the following permissive licenses:

BSD
MIT
Apache License, version 2.0
Eclipse Public License
Mozilla Public License (MPL) 1.1
MPL 2.0
CDDL

[x] pass ./project_precommit_check script run

Ensure project meets all listed requirements before submitting a pull request.

@JohnEstropia Thanks!


task follow-up 3

minor nitpicks from https://github.com/iterative/terraform-provider-iterative/issues/258#issuecomment-1051948425:
p2-nice-to-have

[ ] Escape rclone connection strings properly https://github.com/rclone/rclone/issues/4996#issuecomment-778628943
[ ] Refactor orchestrator events & status as separate data sources
[ ] Chain attributes read to the outer task structs with pointers
[ ] Use https://github.com/openlyinc/pointy or https://github.com/samber/lo on every provider
[ ] Rename regions to locations so it's valid for zones and node selectors

Rename regions to locations so it's valid for zones and node selectors

I'd advise against. regions and zones are important concepts for cloud compute and have delicate meaning for HA and performance for different cloud providers.
Those are distinctly different from k8s' node affinity (or anti-) and node selectors - their meaning depends on the topology of the k8s cluster and the syntax is different as well
I suggest to keep original terminology.
Supporting node affinity/anti-affinity is a necessary next step for running anything on an existing k8s cluster with the necessary customizability and it then the new "abstraction" will break anyways

regions and zones are important concepts for cloud compute and have delicate meaning for HA and performance for different cloud providers.

Given the availability and performance[^1] requirements of the use cases this tool covers (i.e. experimentation and not serving), the current behavior seems appropriate: specifying a region causes the task to pick any zone with enough available resources, and providing a zone letter constrains the placement to that specific zone.
[^1]: Which kind of performance are we talking about? 🤔

Those are distinctly different from k8s' node affinity (or anti-) and node selectors - their meaning depends on the topology of the k8s cluster and the syntax is different as well

Definitely. Kubernetes syntax is too rich for a single string variable; trying to fit everything into a single parameter can be detrimental.

I suggest to keep original terminology.

Agreed for affinity & selectors, not quite for regions and zones.

@0x2b3bfa0

Which kind of performance are we talking about? 🤔

Latency between client machine and the hosted compute resources.
(There's also a cost consideration when considering regions)
None of this translates nicely to k8s node selection - it CAN, if you set up your node groups or use labels in a certain way that you actually pick nodes in specific cloud zone, maybe cross-node-groups, but that's besides the point.
Anything that has to do with selecting nodes on k8s is only meaningful in the context of how that specific cluster and its node groups are set up.
On the other hand -  for cloud providers, regions/zones is a common terminology
I believe that inventing another abstraction here is not helpful - it will add confusion, people will be looking for familiar terms (rightfully so).
Also if/when node affinity/anti-affinity is added - we would want that api to be consistent with node selectors (inside a k8s specific block, probably 😉  ).


Terminal showing on Windows because of Debug build

Contact Details
None
contact
No response
What happened?
The terminal opens with the windows application because the tauri app is a debug build. Updating from debug build to release build is causing issues but there might be a way to just remove the terminal from debug build.
Version
v0.1.0
What operating system are you using?
None
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

This was resolved by changing the cfg header in src-tauri/main.rs


BUG: Clipping Wikipedia pages from iOS/iPadOS generate malformed urls

Version (please complete the following information):

OS: iOS/iPadOS
Browser: Safari
Web Clipper version: 0.9.4
Obsidian version: 1.7.4

Describe the bug
Trying to clip a Wikipedia page from mobile (iPhone or iPad) return a file with the correct content but image urls are malformed. They are missing of "http:" part.
If, before clipping, the desktop version of the same page has been selected, the URLs are correct (including also the "http:" missing prefix)
To reproduce
Steps to reproduce the behavior:

Import kepano's template for Wikipedia from here
Go to a Wikipedia page from a iOS/iPadOS device (e.g. https://it.wikipedia.org/wiki/Baluardo)
3  Check it is the mobile version of the page.
Clip the page selecting the Wikipedia template
Go to the page and verify that links to images are broken (i.e. they are like that //upload.wikimedia.org/wikipedia/commons/thumb/c/c4/Bastion.rempare.png/220px-Bastion.rempare.png)

If, in step 3, instead to use the mobile version you select "show desktop version" subsequent steps return the correct import (i.e. the links are http://upload...)
Indeed importing Wikipedia pages into obsidian using clipper works fine on my MacBook or windows laptop.
Expected behavior
I would have the same behavior using desktop and mobile version of the same Wikipedia page, so the import should ends producing a markdown file  with the correct external URLs (including images included into the text).
Your template file
Below the template I'm using. I tried to reimport the original from kepano's GitHub project obtaining the same results.
{
  "schemaVersion": "0.1.0",
  "name": "Wikipedia",
  "behavior": "create",
  "noteContentFormat": "{{selectorHtml:#mw-content-text|remove_html:(\".navbox,.printfooter,.side-box\")|markdown}}",
  "properties": [
    {
      "name": "title",
      "value": "{{title}}",
      "type": "text"
    },
    {
      "name": "source",
      "value": "{{url}}",
      "type": "text"
    },
    {
      "name": "author",
      "value": "{{author|split:\\\", \\\"|wikilink|join}}",
      "type": "multitext"
    },
    {
      "name": "published",
      "value": "{{published}}",
      "type": "date"
    },
    {
      "name": "created",
      "value": "{{date}}",
      "type": "date"
    },
    {
      "name": "description",
      "value": "{{description}}",
      "type": "text"
    },
    {
      "name": "tags",
      "value": "clippings",
      "type": "multitext"
    }
  ],
  "triggers": [
    "Https://*wikipedia*"
  ],
  "noteNameFormat": "{{title}}",
  "path": "Appunti/Estratti Web"
}

Should be fixed in 0.9.5

The issue is still here with 0.10.0.
For instance clipping the following page for iOS leads to the same "//upload" wrong links.
https://it.m.wikipedia.org/wiki/Petrolio


使用中文tags报错

Error while rendering "page" in "post/": template: /home/kerwin/git/buyaoshushu/themes/hugo-nuo/layouts/post/single.html:12:32: executing "main" at <.Params.tags>: range can't iterate over 游戏

{{ range $tag := .Params.tags }}

{{ $tag | title }}

{{ end }}

The error line in single.html template maybe have problem with function urlize.
I can't figure out what your problem is, you can read the official docs of urlize and try to find the answer.


Feat: expose hook extend locales

The purpose of this feature is to open to other modules the ability to add extra translated content and merge it to the main i18n messages.
Closes https://github.com/nuxt-community/i18n-module/issues/1308

Thanks!


Export components correctly

This fixes the exports for
content-kit-link-button
content-kit-markup-button
content-kit-section-button
so they can be used in the destination app's templates.

thanks!


several crash wallet

When i testing wallet, several minutes, Web will crash.

@stanxii also for this issue, browser and os info is helpful for us.

chrome 版本 60.0.3112.90（正式版本） （64 位）
Os win7 64bit

I have the same issue in Windows and Mac OS X. Working on it.

Also crash on Chrome latest Version 60.0.3112.101 (Official Build) (64-bit).

@whyka  Great work,  thanks for resolve issue so fast.

@whyka It still crash in my chrome. My environment is as the same as stanxil.

@andrewsource I see. Seem it only fixed on Mac OS X. Let's me investigate more on Windows.

@whyka more info for you, my Chrome 60 on Mac was crashing constantly and then suddenly it was not crashing anymore without any browser update or wallet update. So it doesn't always crash.
One of my best bets on this is that Chrome 60 has some flaws (or features) that would crash when React's virtual DOM is being updated in high frequency. We update the wallet quite frequently. The updater is trigger each 10s (or block time if the node supports filter) and does element 10-15 updates as fast as it can.

@tranvictor I've tested chrome with different versions in my windows 7 OS, and here is results:

46.0.2490.80 64 bit: no crash
47.0.2526.73 32 bit: no crash
59.0.3071.115 64 bit: no crash
60.0.3112.101 64bit (lastest build): crash

I also think of that Chrome 60 have flaws.

After searching, neither I saw similar report nor issue in React project.
I don't think this is flaw of Chrome 60 but stricter in resource management.
Actually, my PR #71  fixed crash in the case fresh open and no wallet yet, both Windows and Mac OS X. It's crash again when you create or import wallet.
My current direction is investigating more on React/Redux best practices and implementations of Kyber components.

@tranvictor 10 second update is not a big deal though. I've seen React app that much frequently update than that, such as https://cryptowat.ch/

Maybe both that Chrome has something strange and we do not follow best practices. Race condition is one possible thing to concern.
@andrewsource can you also test the wallet with no accounts nor wallets on those browsers to see if you see the same thing with @whyka ?
@whyka one thing you can try is to disable all of the updates. I myself disabled all of them before to test but no luck.

@stanxii we have just deployed a patch to this issue, can you please try again and tell us if it really fixes the crashing problem? Thanks.

Still crash if open dialog Exchange and input some amount. Happens on both Windows and Mac OS X.

@whyka Could you describe details steps causing crash? I also input amount in Exchange form, but there is no crash in my Chrome (Windows)

@andrewsource You can try this:
Click Exchange to open Quick Exchange.
In field "Exchange", choose GNT.
In field "Expected to receive", choose ETH.
Input some amount and wait.
I have a screen record if you need. I tried on Windows too.

@whyka lets go ahead and upload the video. It is even better if you can find a root cause of that.
@andrewsource i still don't quite believe that .toString(10) is the reason. I read their implementation and it has nothing that I can suspect. But yeah, somehow it crashes much less!

I upload video here https://drive.google.com/open?id=0B7ltVC8U1G-YdVk1Qk9EeXpHZzQ

@whyka, @tranvictor  When change value quickly, the onChange events are fired, and it calls function BigNumber.toString(10) many times so it causes crash. I also change other functions, which have .toString(10) (to .toString()) and the crash does not happen, at least in my computer.
I'm still finding the root cause


Rabbitmq to Devel

Addresses several open tasks. Including the switch to rabbitMQ.

@par-hermes format


Rebates Available to Renters

As a [description of user]?
renter in BC,
I want to [functionality]
access resources and rebates programs available to someone who rents
So that [benefit]
find actions I can take.
Additional context
Add any other context, attachments or screenshots
Acceptance Criteria
Agreed-upon confirmation of the requirements when done can be deemed as complete

duplicated by #76


Test OpenStack install using snapsopenstack DockerHub repo

Could test on OpenStack first and then on bare metal.

This worked when manually setting the docker_namespace to snapsopenstack.  A patch is needed to automate this process.

add another option to the deployment file to set the docker_namespace:.  This option is optional and only used when use_docker_hub is yes.
Write this to globals.yaml on the controller.  This would be a part of the if statement on line 319 in kolla_utils.py.
Documentation will need to be updated and the example deployment.yaml will need to be updated.  snapsopenstack is the namespace that we are using.
if you look at /etc/kolla/globals.yaml on the lab 3 controller, you can see what the file should look like.  The docker_namespace: “snapsopenstack” is there an uncommented.


Bash image not handling arguments

Which image/versions are related to this issue/feature request?
cgr.dev/chainguard/bash
Issue/Feature description
I'd expect this to work:
$ docker run cgr.dev/chainguard/bash echo hello world

The arguments to echo get swallowed for some reason. The same thing happens with other commands e.g. uname -a
Fixing this is annoyingly not straightforward. There are two choices I can see:

Remove entrypoint and symlink /bin/sh to /bin/bash. That way the default container command handling will kick in, which correctly handles the above, but assumes the shell is at /bin/sh
Write an entrypoint script similar to the one for Docker Hub official bash image.

Lack of convenient args handling is present in all images, not just cgr.dev/chainguard/bash. It would be great if we could add the proposed entrypoint.sh wrapper to all such "utility" images.
Presently, Chainguard images cannot be used as drop-in replacements for initContainers in helm charts with hard-coded command: ["sh", "-c", ...] style arguments. Here is an example from the mattermost-enterprise-edition chart where you'd ideally be able to drop in cgr.dev/chainguard/curl: https://github.com/mattermost/mattermost-helm/blob/02228aa9356b2a86d39aede9d09d0af3de6d5e26/charts/mattermost-enterprise-edition/templates/deployment-mattermost-app.yaml#L61-L82
Also some additional variations on the entrypoint.sh wrapper I have seen in the wild:
via tianon/docker-bash (linked in OP):
#!/usr/bin/env bash
set -Eeuo pipefail

# first arg is `-f` or `--some-option`
# or there are no args
if [ "$#" -eq 0 ] || [ "${1#-}" != "$1" ]; then
	# docker run bash -c 'echo hi'
	exec bash "$@"
fi

exec "$@"

via curlimages/curl:
#!/bin/sh
set -e

if [ "${1#-}" != "${1}" ] || [ -z "$(command -v "${1}")" ]; then
  set -- curl "$@"
fi

exec "$@"

via appropriate/docker-curl:
#!/bin/sh
set -e

# Prepend "curl" if the first argument is not an executable
if ! type -- "$1" &> /dev/null; then
	set -- curl "$@"
fi

exec "$@"

For bash image sounds like we should add bash-binsh package to it.
For curl not sure if we want to keep curl:latest without any shell and have separate curl-docker:latest that has shell and does args mangling as the other curl images do. Unless we are loosing the battle of shell less images.
Any idea which helm charts expect curl images with shell and if we can improve those to not need shell?

I did some work on this previously and created https://github.com/wolfi-dev/container-entrypoint/, the idea being it could be added as a package to any containers with a shell to mimic this functionality.

@xnox maybe we could create small binary to serve as the entrypoint and performs similar args manipulation and calls exec(...) even if a shell is not available? Like what @amouat put together but without the shell dependency.
For example, here is an shell interpreter written in Go that implements the type and exec built-ins: https://github.com/mvdan/sh/blob/793d36450a0a5a466199b04c458fb4a1202cf641/interp/builtin.go#L249-L332
This is obviously much too heavy a solution to use off the shelf, and maybe not worth doing at all, but it would be great if you could exec any program in a distroless (or dev) images by overriding the command args.


[Feature Request] Information Request - Range of IP's used by Azure Load Testing

Please describe.
Currently looking at using Azure Load Testing with internal API's but would require a range of IP's to whitelist
Describe the solution you'd like
Would it be possible to get a range of IP's that Azure Load Testing uses?
AB#1457325

Hi @MonzT Thanks for sharing your scenario. With our current solution, it would not be feasible for us to publish our IPs. We have shared our longer term plans around this ask in this thread . I am closing this issue in this thread so that we can consolidate all similar asks.


JSON validation enhancement without dashboard change

Removed v2.6.0 label since this is not included in 2.6.0 release.


Vide network activity. Video loading twice at first!

Hi,
from my experience with Vide, it is initially loading the video twice and re downloading it every time the video is over. So my question is, is it possible to have it cache the video so that it deosn't download itself on every loop and am i the only one experiencing the video initially being downloaded twice?
Other than that, thanks for the plugin!

+1

Do you use the latest version?

I can't replicate the 'video loading twice' issue. It sounds like bad/duplicate initialization.
However, I too was stumped by Vide sending a network request every time the video looped. It was giving my video-heavy page serious performance issues. Then I realised I had "Disable Cache" checked whilst in devtools. Now it fetches the video from the cache.

@willviles
That makes more sense now, thank you!


feat: Add create_scheduling_policy option to job_queue

With this, someone can use attach_scheduling_policy in their job_queue definition to skip over scheduling policy attachment.
Description
Right now, a scheduling policy is auto-attached to all job queues. Adding "attach_scheduling_policy" when defining people's job queues will override the default behaviour.
Motivation and Context
I don't want to always have a scheduling policy for my queues.
Breaking Changes
No, it uses lookup, and defaults to the original behaviour
How Has This Been Tested?

[x] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[x] I have tested and validated these changes using one or more of the provided examples/* projects

[x] I have executed pre-commit run -a on my pull request

Hey @bryantbiggs @antonbabenko can I get this added as well? I want to add job queues that don't have scheduling policies.

Hey @bryantbiggs, did you see my comment?

yes, I started to take a look and haven't come up with a solution that seems reasonable yet

It's tricky, we need a way to say we don't want the scheduling policy, and it has to be at the queue level. Curious to see what you come up with

@bryantbiggs I actually found a workaround, you can supply scheduling_policy_arn = null when you define your job queue, and it works. Not sure this change is needed anymore (although scheduling policies will still be created)

@bryantbiggs done and ready

This PR is included in version 1.2.0 :tada:


Neo4jError: "BoltProtocol.sessionExpired" ("Session expired.")

Example bug report
I get Neo4jError: "BoltProtocol.sessionExpired" ("Session expired.") many time in my application.
Neo4j Mode: Single instance
Driver version: Go driver 5.18
Operating System: Ubuntu 16.10 on AWS
Steps to reproduce

Start Neo4j on a AWS instance
Run a query with the driver
Put the driver idle for 2h
Run another query

Expected behavior
The second query shall run successfully
Actual behavior
The client failed to run the second query with a Neo4jError: "BoltProtocol.sessionExpired" ("Session expired.") stacktrace.

Hello, thanks for the report.
Can you please share an example of "run[ning] a query with the driver"? What API are you using?
Can you allow share the Bolt logs from the Go application?

I am using the driver for AWS Neptune.

sorry about that, it is Neptune. Is there exponential backoff and retry strategy implementation example in golang?

@gsingh-ds there is a built-in retry mechanism on some errors when you use the session#ExecuteRead and session#ExecuteWrite APIs. It is implemented as an exponential backoff.
There is also a public API that exposes the error predicate function that is used, which is called neo4j.IsRetryable(error).
By the looks of it, I don't think the error you get is deemed retryable.

Hi @gsingh-ds, unfortunately as this is Neptune and not Neo4j we aren't able to help. If you notice this behavior when using Neo4j too, we can reopen this issue. If so please include any bolt logs, example query, and how you're using the driver with what config to help us track the issue down. Thanks

@fbiville does exponential backoff also implemetned in session#ExecuteQuery ? if now why? and can we do it?


Support automatically updating existing DevWorkspaceTemplates

Is your enhancement related to a problem? Please describe.
Currently, WTO only creates DevWorkspaceTemplates to support Web Terminals, but does not update existing ones on startup in case the user has customized them. In the coming release, these templates will need to be updated to support the new tooling and exec images, so WTO will need to implement a mechanism for updating templates on startup.
Describe the solution you'd like
By default, WTO should update DevWorkspaceTemplates on every start-up. A special annotation should be available to disable this functionality in case a user wants to override e.g. the image used for tooling. The diff for each update should be logged for information purposes.
Additional context

Woops, this didn't get ticked off my TODO list when I created https://github.com/redhat-developer/web-terminal-operator/pull/97. This issue is already resolved :D


nixos/usbStorage: update device flag

Description of changes
Fixes #265013

Things done

Built on platform(s)

[x] 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/)
23.11 Release Notes (or backporting 23.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.

Tested this today with an external drive.
~ grep -rn --include 'manage*start_stop' . /sys/devices/
/sys/devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4:1.0/host0/target0:0:0/0:0:0:0/scsi_disk/0:0:0:0/manage_system_start_stop:1:0
/sys/devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4:1.0/host0/target0:0:0/0:0:0:0/scsi_disk/0:0:0:0/manage_runtime_start_stop:1:0
/sys/devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4:1.0/host0/target0:0:0/0:0:0:0/scsi_disk/0:0:0:0/manage_start_stop:1:0

Can we merge this?

Can you merge this @AndersonTorres ?

No :(

I set manage_system_start_stop to replicate the old behavior.
I presume el-cheapo USB devices won't be able to wake up after suspend if we set manage_runtime_start_stop.
It looks like they've made another change in https://github.com/torvalds/linux/commit/24eca2dce0f8d19db808c972b0281298d0bafe99.


Multiple Entity Managers and Connections

This patch provides the ability to reference multiple database connections in laravel-doctrine. It will register the default database or the set of databases outlined in the entity_managers configuration. Existing functionality is maintained by continuing to register the EntityManager and returning a connection from the ManagerRegistry

Any update on whether this will be merged or not? This looks very handy to me.

If tests can be written to manage all the changes, then we can move forward with the implementation.

:thumbsup:

@kirkbushel Do you have a list of tests or features you would like tests added for? Since the old configuration is rebuild into the new format the old test should confirm that basic functionality is still intact.

@kirkbushell Sorry this took so long. I needed to do a little refactoring in order to make it more testable. Let me know your thoughts on this and / or any feedback on any additional tests you need in order to move this forward.

Along with the entity_managers a new configuration option default_connection was adding in this pass.  This will default to the default database in the laravel database configuration but can be changed when you want to maintain a different list.
From http://symfony.com/doc/current/cookbook/doctrine/multiple_entity_managers.html

If you do omit the entity manager's name when asking for it, the default entity manager (i.e. default) is returned

:+1:

@FoxxMD You are correct. Instead of creating an entity manager for the default database we now create a new entry in $app['config']['doctrine::doctrine'] (doctrine.php) called entity_managers. This item will be populated automatically from the default database connection if not specified in $app['config']['database']. This allows a default configuration with the entity name being the same as the database connection. We also create default_connection  in $app['config']['doctrine::doctrine'] to match the default in $app['config']['database']. This is important in a multi-connection environment where we may want a doctrine default separate from the listed default in $app['config']['database'].
So the thing to note is if you create an 'entity_managers'  entry in doctrine.php it requires its own configuration. Missing items will be filled with some defaults. You then need to set a name for the entity manager and list the matching connection from $app['config']['database'] if they are not the name. Doctrine does not require that the connection and entity name be the same so this provides a little more flexibility.  You still need to define the default_connection in doctrine.php outside of the entity_managers array if for some reason this is different from the default connection in $app['config']['database']. If default_connection is not specified then it will be created with from the default value from $app['config']['database'].
If you have any questions/comments I'd be happy to review it.

@FoxxMD \Tests\MultipleEntityManagersAndConnections\SchemaCreateCommandTest uses the following connection information. It will call the command with sqlite to use a non-default entity manager from the operation. For reference the test adds the following to doctrine.php.
default_connection = 'mysql',

'entity_managers' = [
    'pgsql' => [
        'connection' => 'pgsql',
        'metadata' => [
            __DIR__.DIRECTORY_SEPARATOR.'Models',
        ],
    ],
    'mysql' => [
        'connection' => 'mysql',
        'metadata' => [
                __DIR__.DIRECTORY_SEPARATOR.'Models',
        ],
    ],
    'sqlite' => [
        'connection' => 'sqlite',
        'metadata' => [
                __DIR__.DIRECTORY_SEPARATOR.'Models',
        ],
    ],
];
``

Thanks @npmarrin ! How do I get a non-default entity manager from code? Right now I'm just using the EntityManager facade provided by laravel-doctrine. Do I need to instantiate a new IlluminateRegistry and do getManager('nonDefaultManager') every time I want one? Or can it be set up using the facade?

@FoxxMD
You want to replace use Doctrine\ORM\EntityManagerInterface; with use Doctrine\Common\Persistence\ManagerRegistry; and then replace EntityManagerInterface $entityManager with ManagerRegistry $registry. This will inject the IlluminateRegistry. EntityManagerInterface is still available for backwards compatibility.
You can get the default manager using $registry->getManager() or you can pull a specific manager using $registry->getManager('sqlite'). You can also pull a connection from the IlluminateRegistry if you don't need ORM for a specific query. Again their is no requirement that the connection and entity manager names are the same. Only that the connection name is present in database.php. If you are using multiple-connections you should be passing the registry into your controllers.
You can review http://symfony.com/doc/current/cookbook/doctrine/multiple_entity_managers.html if you need more background.
If you have any issues / concerns let me know. It is great to get another pair of eyes on this.

Thanks @npmarrin, this has been extremely helpful!