pinocchio.Data(model) fails with -march=native

Hi all,
I have spent a couple of hours understanding what it is going, however, I have to admit that I don't have any clue. I have compiled Pinocchio with march=native flag, without support of Codegen and Collision to narrow down the issue, and this is the problem:
import pinocchio

model = pinocchio.buildSampleModelHumanoid()
for i in range(100): # I used a for-loop because sometime doesn't fail in the first call
  data = pinocchio.Data(model) # This produces an error
  #data = pinocchio.Model.createData(model) # Instead this works, WHY?

Additionally, this is the detailed information error generated by gdb:
python: /usr/local/include/eigen3/Eigen/src/Core/DenseStorage.h:128: Eigen::internal::plain_array<T, Size, MatrixOrArrayOptions, 32>::plain_array() [with T = double; int Size = 36; int MatrixOrArrayOptions = 0]: Assertion `(internal::UIntPtr(eigen_unaligned_array_assert_workaround_gcc47(array)) & (31)) == 0 && "this assertion is explained here: " "http://eigen.tuxfamily.org/dox-devel/group__TopicUnalignedArrayAssert.html" " **** READ THIS WEB PAGE !!! ****"' failed.

Thread 1 "python" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51	../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x00007ffff7a24801 in __GI_abort () at abort.c:79
#2  0x00007ffff7a1439a in __assert_fail_base (fmt=0x7ffff7b9b7d8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n",
    assertion=assertion@entry=0x7fffcacef920 "(internal::UIntPtr(eigen_unaligned_array_assert_workaround_gcc47(array)) & (31)) == 0 && \"this assertion is explained here: \" \"http://eigen.tuxfamily.org/dox-devel/group__TopicUnalignedArrayAssert.htm"..., file=file@entry=0x7fffcacee9f8 "/usr/local/include/eigen3/Eigen/src/Core/DenseStorage.h", line=line@entry=128,
    function=function@entry=0x7fffcacf7160 <Eigen::internal::plain_array<double, 36, 0, 32>::plain_array()::__PRETTY_FUNCTION__> "Eigen::internal::plain_array<T, Size, MatrixOrArrayOptions, 32>::plain_array() [with T = double; int Size = 36; int MatrixOrArrayOptions = 0]") at assert.c:92
#3  0x00007ffff7a14412 in __GI___assert_fail (
    assertion=0x7fffcacef920 "(internal::UIntPtr(eigen_unaligned_array_assert_workaround_gcc47(array)) & (31)) == 0 && \"this assertion is explained here: \" \"http://eigen.tuxfamily.org/dox-devel/group__TopicUnalignedArrayAssert.htm"..., file=0x7fffcacee9f8 "/usr/local/include/eigen3/Eigen/src/Core/DenseStorage.h", line=128,
    function=0x7fffcacf7160 <Eigen::internal::plain_array<double, 36, 0, 32>::plain_array()::__PRETTY_FUNCTION__> "Eigen::internal::plain_array<T, Size, MatrixOrArrayOptions, 32>::plain_array() [with T = double; int Size = 36; int MatrixOrArrayOptions = 0]") at assert.c:101
#4  0x00007fffc9ee8771 in Eigen::internal::plain_array<double, 36, 0, 32>::plain_array (this=0x5555561eb730) at /usr/local/include/eigen3/Eigen/src/Core/DenseStorage.h:128
#5  0x00007fffc9ed5bec in Eigen::DenseStorage<double, 36, 6, 6, 0>::DenseStorage (this=0x5555561eb730) at /usr/local/include/eigen3/Eigen/src/Core/DenseStorage.h:187
#6  0x00007fffc9ec310a in Eigen::PlainObjectBase<Eigen::Matrix<double, 6, 6, 0, 6, 6> >::PlainObjectBase (this=0x5555561eb730) at /usr/local/include/eigen3/Eigen/src/Core/PlainObjectBase.h:484
#7  0x00007fffc9ead944 in Eigen::Matrix<double, 6, 6, 0, 6, 6>::Matrix (this=0x5555561eb730) at /usr/local/include/eigen3/Eigen/src/Core/Matrix.h:259
#8  0x00007fffca5ef9dd in pinocchio::DataTpl<double, 0, pinocchio::JointCollectionDefaultTpl>::DataTpl (this=0x5555561eb450, model=...)
    at /home/cmastalli/devel/pinocchio/build_debug/include/pinocchio/multibody/data.hxx:108
#9  0x00007fffca5eb391 in boost::python::objects::value_holder<pinocchio::DataTpl<double, 0, pinocchio::JointCollectionDefaultTpl> >::value_holder<boost::python::objects::reference_to_value<pinocchio::ModelTpl<double, 0, pinocchio::JointCollectionDefaultTpl> > > (this=0x5555561eb430, self=0x7fffc3af01d0, a0=...) at /usr/include/boost/python/object/value_holder.hpp:133
#10 0x00007fffca5e7711 in boost::python::objects::make_holder<1>::apply<boost::python::objects::value_holder<pinocchio::DataTpl<double, 0, pinocchio::JointCollectionDefaultTpl> >, boost::mpl::vector1<pinocchio::ModelTpl<double, 0, pinocchio::JointCollectionDefaultTpl> > >::execute (p=0x7fffc3af01d0, a0=...) at /usr/include/boost/python/object/make_holder.hpp:94
#11 0x00007fffca7e469c in boost::python::detail::invoke<int, void (*)(_object*, pinocchio::ModelTpl<double, 0, pinocchio::JointCollectionDefaultTpl>), boost::python::arg_from_python<_object*>, boost::python::arg_from_python<pinocchio::ModelTpl<double, 0, pinocchio::JointCollectionDefaultTpl> > > (
    f=@0x5555560d8868: 0x7fffca5e7694 <boost::python::objects::make_holder<1>::apply<boost::python::objects::value_holder<pinocchio::DataTpl<double, 0, pinocchio::JointCollectionDefaultTpl> >, boost::mpl::vector1<pinocchio::ModelTpl<double, 0, pinocchio::JointCollectionDefaultTpl> > >::execute(_object*, pinocchio::ModelTpl<double, 0, pinocchio::JointCollectionDefaultTpl>)>, ac0=..., ac1=...)
    at /usr/include/boost/python/detail/invoke.hpp:79
#12 0x00007fffca7d9fc5 in boost::python::detail::caller_arity<2u>::impl<void (*)(_object*, pinocchio::ModelTpl<double, 0, pinocchio::JointCollectionDefaultTpl>), boost::python::default_call_policies, boost::mpl::vector3<void, _object*, pinocchio::ModelTpl<double, 0, pinocchio::JointCollectionDefaultTpl> > >::operator() (this=0x5555560d8868, args_=0x7ffff7efddc0)
    at /usr/include/boost/python/detail/caller.hpp:216
#13 0x00007fffca7d007d in boost::python::objects::caller_py_function_impl<boost::python::detail::caller<void (*)(_object*, pinocchio::ModelTpl<double, 0, pinocchio::JointCollectionDefaultTpl>), boost::python::default_call_policies, boost::mpl::vector3<void, _object*, pinocchio::ModelTpl<double, 0, pinocchio::JointCollectionDefaultTpl> > > >::operator() (this=0x5555560d8860, args=0x7ffff7efddc0, kw=0x0)
    at /usr/include/boost/python/object/py_function.hpp:38
#14 0x00007fffc529fe55 in boost::python::objects::function::call(_object*, _object*) const () from /usr/lib/x86_64-linux-gnu/libboost_python-py27.so.1.65.1
#15 0x00007fffc52a0008 in ?? () from /usr/lib/x86_64-linux-gnu/libboost_python-py27.so.1.65.1
#16 0x00007fffc52a6bcb in boost::python::detail::exception_handler::operator()(boost::function0<void> const&) const () from /usr/lib/x86_64-linux-gnu/libboost_python-py27.so.1.65.1
#17 0x00007fffc57386d3 in boost::detail::function::function_obj_invoker2<boost::_bi::bind_t<bool, boost::python::detail::translate_exception<eigenpy::Exception, void (*)(eigenpy::Exception const&)>, boost::_bi::list3<boost::arg<1>, boost::arg<2>, boost::_bi::value<void (*)(eigenpy::Exception const&)> > >, bool, boost::python::detail::exception_handler const&, boost::function0<void> const&>::invoke(boost::detail::function::function_buffer&, boost::python::detail::exception_handler const&, boost::function0<void> const&) () from /usr/local/lib/libeigenpy.so
#18 0x00007fffc52a696f in boost::python::handle_exception_impl(boost::function0<void>) () from /usr/lib/x86_64-linux-gnu/libboost_python-py27.so.1.65.1
#19 0x00007fffc529d6c9 in ?? () from /usr/lib/x86_64-linux-gnu/libboost_python-py27.so.1.65.1
#20 0x000055555567a70e in ?? ()
#21 0x000055555567a33a in ?? ()
#22 0x00005555556370ab in ?? ()
#23 0x000055555564db20 in PyEval_EvalFrameEx ()
#24 0x00005555556462aa in PyEval_EvalCodeEx ()
#25 0x0000555555645d19 in PyEval_EvalCode ()
#26 0x000055555567694f in ?? ()
#27 0x0000555555671be2 in PyRun_FileExFlags ()
#28 0x000055555567160d in PyRun_SimpleFileExFlags ()
#29 0x0000555555620356 in Py_Main ()
#30 0x00007ffff7a05b97 in __libc_start_main (main=0x55555561fd30 <main>, argc=2, argv=0x7fffffffda98, init=<optimised out>, fini=<optimised out>, rtld_fini=<optimised out>, stack_end=0x7fffffffda88)
    at ../csu/libc-start.c:310
#31 0x000055555561fc4a in _start ()

I inspected the pinocchio::Data structure looking for possible issue regarding data alignment, and IMHO everything looks OK. I wonder if this is related to the bindings of the copy constructor function.
Carlos

It will be hard to debug your case if you did not provide the compilation flags you're using to compile EigenPy and Pinocchio. In addition, you should provide the current version of Eigen you're using. If you are still on the master branch of Eigen (according to the output you provided, this is the case), I prefer to avoid debugging it. Please use a release version instead.

It will be hard to debug your case if you did not provide the compilation flags you're using to compile EigenPy and Pinocchio.

I compiled both in Release mode with -march=native, nothing else.

In addition, you should provide the current version of Eigen you're using

I am using Eigen 3.3.7. As a side comment -- there are other issues in the Eigen master but I abandon this since it is not stable neither priority.

Do you have the same behavior in C++ ?

It is weird, because in Release mode you should not see any of the assert.

I guess it is in debug mode: /home/cmastalli/devel/pinocchio/build_debug/include/pinocchio/multibody/data.hxx

It is weird, because in Release mode you should not see any of the assert.

Sorry, I meant that I encountered the issue with Release mode. Then I debugged with gdb and of course switch to Debug mode (only in Pinocchio).

Do you have the same behavior in C++ ?

I didn't try in c++.

It would help understanding whether the issue is at the bindings level or at the core level. Could you to it ?

The issue is coming from Python in fact. At the Boost level, we have to mention that Model has to be realigned by thanks to some template specialization provided by EigenPy.

@jcarpent at the moment, is there a way to list known bugs that will not be fixed, as this one ?

Not really. The memory is currently stored in the issues.

Perhaps let's add a label "known-bug-wont-fix". That way it can easily be filtered

Nowadays, more and more python packages are distributed with at least such AVX support, and I'm wondering if there is still no plan to fix this issue. Storing objects in shared pointers is fixing the issue but it seems to impede performance. Therefore, I suggest to use a preprocessor macro to add the necessary argument iif __AVX__ is defined. This way, it has no effect by default, and the performance boost overweights the drawbacks if AVX and onward is enabled.

Pinocchio and its dependencies are compliant with AVX support, even in Python.
Currently, as far as I know, there is no rule to force deployment with AVX support on apt, conda, etc. but maybe I'm a bit outdated.

Overall, I won't go into the non-standard approach (e.g., forcing AVX compilation) to avoid multiplying the management time that @nim65s and I are already spending a lot. @duburcqa Are you willing to support this deployment on your own time?

Pinocchio and its dependencies are compliant with AVX support, even in Python.

What do you mean ? I could reproduce the segfault described in this issue on my machine after enabling -march=native. You think it is because it is enabling more than AVX but also AVX2 and AVX512...etc ?

Pinocchio and its dependencies are compliant with AVX support, even in Python.

What do you mean ? I could reproduce the segfault described in this issue on my machine after enabling -march=native. You think it is because it is enabling more than AVX but also AVX2 and AVX512...etc ?

Did you try to recompile eigenpy and hpp-fcl with the same flags?

The original issue was coming initially from Eigen which does not use the same constructor/destructor whether the objects are aligned or not in memory.

Did you try to recompile eigenpy and hpp-fcl with the same flags?

Yes of course, I'm compiling the whole stack, from ground zero including boost. It works just fine for everything I do, except the specific example provided in the issue.

The original issue was coming initially from Eigen which does not use the same constructor/destructor whether the objects are aligned or not in memory.

You mean the PR about using smart pointers here is outdated and I should update eigenpy ? I'm still using 2.6.4.

Are you willing to support this deployment on your own time?

For now it is more about discussing in which direction things are going before taking any action.

Here: https://github.com/stack-of-tasks/pinocchio/blob/5c93f4e043886ec43659a10a79701263a1e8fa18/bindings/python/multibody/data.hpp#L102
You should replaced bp::init<Model> by bp::init<const Model &>.

Here:
https://github.com/stack-of-tasks/pinocchio/blob/5c93f4e043886ec43659a10a79701263a1e8fa18/bindings/python/multibody/data.hpp#L102
You should replaced bp::init<Model> by bp::init<const Model &>.

This has been fixed in pinocchio-3x.

This has been fixed in pinocchio-3x.

Ah amazing! Is it based on this patch ? Do you know if it was an isolated "bug" for pinocchio::data in particular and AVX is otherwise fully supported by pinocchio<2.9 in Python ?

There are many places in Pinocchio where this has been fixed. But I guess for your case, this is the only place that matters.

OK I see. For the record, the patch you proposed is not working on my machine. But I have the feeling waiting for Pinocchio before taking into action seems more reasonable as there is no rush anyway.


[Autocomplete] Custom renderOption with action button

Hi,
I'm currently using the autocomplete component and I create a custom renderOption function to display :

option name
specific button to open other window

When I click on the specific button near the option name, this action automatically set the option and this is not expected.

[X] The issue is present in the latest release.
[X] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
Custom renderOption with component to display option name and a specific button near.
Clicking on the near button also select the option.

Expected Behavior 🤔
Clicking on the near button need to only proceed the button action.

Steps to Reproduce 🕹

IssueWithAutocomplete.mov.zip
Context 🔦

The autocomplete provide list of foreign record. By clicking on the preview button, I can access to record view.
Your Environment 🌎

Tech
Version

Material-UI
v5.11.0

React
v16.13.1

Browser
Chrome

TypeScript
v4.0.2

etc.

@matthintosh You need to stop the propagation of the event to avoid the autocomplete's option handler to trigger the value.

@oliviertassinari Thank you very much for your reply. How can stop the event propagation ?

@matthintosh Feel free to share the solution, so others can save time.


support open notebook & local environment

this implements #7 requires https://github.com/fonsp/Pluto.jl/pull/341

I updated the version, since in Comonicon's convention (also Julia's, I think) the first version starts from v0.1.0

Thanks a lot! I'll have a look at the Pluto PR

Feel free to merge this when you're happy

Cool, I'll merge this first, and probably I think it's time to tag the first version to make this more accessible.

Yeah, I think I'll try to finish the other environment variable PR before your next release, since that along with the per notebook environment PR should be in a minor version.
I also just realize tho the feature seems right, but the fallbacks seems not (not falling back to @. but global one if notebook environment not specified but run with --project flag). I will need to adjust this a bit here.


Skybox does not write to velocity render layer

Tested versions
v4.3.beta2.official https://github.com/godotengine/godot/commit/b75f0485ba15951b87f1d9a2d8dd0fcd55e178e4
System information
Windows 10 - Godot v4.3.beta https://github.com/godotengine/godot/commit/16f98cd7079c2b22248ec358371f17bca355e42e
Issue description
This comes from testing the motion blur implementation made by me and the one made by @wojtekpil. In the debug view in the demo I made, you can see the velocity texture at the top left, being left at (0, 0) when nonoccluded skybox is in view, regardless of camera motion and rotation.

Discussion has started here:
https://discord.com/channels/809721752019402762/1250813037221384245/1259859226336034916
Steps to reproduce

download and open the demo at https://github.com/sphynx-owner/JFA_driven_motion_blur_demo
press play, and then Z to enable the debug view
look at the sky and keep it in view while looking around to see that is does not feed to the velocity buffer displayed at the top left, and thus does not get blurred.

Minimal reproduction project (MRP)
https://github.com/sphynx-owner/JFA_driven_motion_blur_demo

This is also not a bug.
Skybox intentionally doesn't write motion vectors as they're not required for TAA to work and are also derived from depth in the case of FSR2 as the motion vector is written out as an invalid value instead. This is a conscious choice to reduce the amount of bandwidth used during skybox rendering (both this and the invalid vector are choices for mobile mostly).
Adding these does not come for free so you'd need whatever effect API you're plugging in to indicate it wants a different behavior out of the renderer.

Hi Dario, the link to the engine code you posted in this comment, we can use that to derive the motion vectors for the sky in the case of FSR 2 being turned off, right?

Hi Dario, the link to the engine code you posted in this comment, we can use that to derive the motion vectors for the sky in the case of FSR 2 being turned off, right?

That won't quite work as TAA opts to write out a (0, 0) value instead and treats it as if the pixel didn't move. An MV of (0, 0) could be treated as an invalid vector, but it'll also hold true for anything that moves relative to the camera with the exact same movement. There's no explicit handling for the (0, 0) value in the TAA shader. This behavior is laid out in the rendering code in the different branches. This is why FSR2 opts to write a (-1, -1) as the clear value instead as it's not realistic for an MV like that to ever show up.
This inconsistency between TAA and FSR2's MV derivation is something that has yet to be solved and it's laid out as such in the rendering code. You can see the different choices it does based on 'using_motion_pass' versus the behavior it does with regular TAA.
https://github.com/godotengine/godot/blob/26d1577f3985363faab48a65e9a0d9eed0e26d86/servers/rendering/renderer_rd/forward_clustered/render_forward_clustered.cpp#L1678
https://github.com/godotengine/godot/blob/26d1577f3985363faab48a65e9a0d9eed0e26d86/servers/rendering/renderer_rd/forward_clustered/render_forward_clustered.cpp#L2029-L2034

Hmm, any recommendations how to deal with this as a Compositor effect? Is there a way to differentiate, within Compositor, skybox pixels from the rest?
cc @sphynx-owner

Hmm, any recommendations how to deal with this as a Compositor effect?

The simplest solution I can think of is to just clear the vectors to an invalid value (-1, -1) in TAA as well and add the derivation logic to it that FSR2 does. The problem is this adds a cost that wasn't there before, but it'd be the simplest way to merge both of the techniques together to have consistent behavior. Then the compositor effect can use the exact same reprojection logic the renderer uses and derive the vector the same way.

Can't we NaN it instead?


Graphic artifacts on fonts in ui

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
Graphic artifacts displaying fonts.

Steps to Reproduce

Turn it on.

Expected behavior: Just the text rendered correctly
Actual behavior: Graphics artifacts on rendered text (see image).
Reproduces how often: 100%
Versions
output from atom --version:
Atom    : 1.24.0
Electron: 1.6.16
Chrome  : 56.0.2924.87
Node    : 7.4.0

Output fom apm --version
apm  1.18.12
npm  3.10.10
node 6.9.5 x64
atom 1.24.0
python 2.7.15rc1
git 2.17.0

Ubuntu 18.04
4.15.0-20-generic
Additional Information
Just turn it on.

Thanks for the report!

Atom    : 1.24.0

I think this might be a duplicate of https://github.com/atom/atom/issues/15737 which was fixed in 1.25 - please update to the latest release version of Atom (currently 1.26.1) and let us know if you still see the issue.

Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.

Yup, it's resolved in 1.26.0, thank you!


Notification Template - create button position is swap with filter button

Describe the bug

create button position is swap with filter button


[Task]: Test observability with update 4

Description
$Subject
Describe your task(s)
No response
Related area
-> Runtime
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

Tested with 2201.4.0, no blockers found regarding Observability (Found a minor bug and created an issue https://github.com/ballerina-platform/ballerina-lang/issues/39717).
Tested with this a multiple service Ballerina project https://github.com/gabilang/travel-agency.
Following is the result from Jaeger for distributed tracing.


Elastic stock extension cannot connect to ElasticSearch

I was looking at the elastic-stock extension but accessing the endpoint kept on failing.
Upon further inspection, it looks like the following problems exist:

indexName does not exist (https://github.com/DivanteLtd/vue-storefront-api/blob/master/src/api/extensions/elastic-stock/index.js#L15)
product.hits doesn't exist. Instead, product.body.hits should be used (https://github.com/DivanteLtd/vue-storefront-api/blob/master/src/api/extensions/elastic-stock/index.js#L22).

@themreza @pkarw
This sounds a lot like what I came across when upgrading an api-extension from 1.10 to 1.11.
The problem was when using different ES versions. We solved it with a helper like this:
Credit should be awarded to @benjick 🍺
export function getHits (result) {
  if (result.body) { // differences between ES5 and ES7
    return result.body.hits
  } else {
    return result.hits
  }
}

This shouldn't be a problem anymore. instead indexName is now used index and we have helper to get hits


Fixed broken link to supported node versions for Ubuntu

Fixed broken link to supported node versions
On the Ubuntu Installation Guide under Server Setup I noticed the link to supported versions of Node was broken. This should fix that.
URL: https://docs.ghost.org/install/ubuntu/#install-nodejs

Thanks for the suggestion @daviddarnes! Good catch on the redirect. I think I merged your suggestion into this pull request.


[WFLY-4811] Add new batch-jberet subsystems

This PR adds a new batch-jberet subsystem.
First Commit
This commit reverts a change to the original batch subsystem that will only be allowed in the new subsystem.
Second Commit
This commit brings JBeret to a level required for the new subsystem.
Third Commit
This commit just changes a few things to prepare for the new subsystem. It could be squashed with the next commit, but for the review process it may be easier having it separate.
Fourth Commit
This commit is the addition of the new subsystem. The new subsystem model looks like the following.
{
    "default-job-repository" => "in-memory",
    "default-thread-pool" => "batch",
    "in-memory-job-repository" => {"in-memory" => {}},
    "jdbc-job-repository" => {"jdbc" => {"data-source" => "test"}},
    "thread-factory" => undefined,
    "thread-pool" => {"batch" => {
        "keepalive-time" => {
            "time" => 30L,
            "unit" => "SECONDS"
        },
        "max-threads" => 10,
        "name" => "batch",
        "thread-factory" => undefined
    }}
}

This new model allows for the use of capabilities & requirements as well as hopefully cleans up the user experience. The default-job-repository and default-thread-pool attributes seem a bit awkward to me, but allow the deployments to work without a deployment descriptor.
The JNDI name is no longer used for a jdbc-job-repository. The data source capability is used and the data source is no longer looked up via a JNDI lookup.
Multiple thread pools and job repositories are allowed to be defined. The jboss-all.xml deployment descriptor can be used to define specific job repositories or thread pools to the deployment.
Once this is acceptable I will submit a PR for the capabilities documentation.
Fifth Commit
This is just the tests and can be squashed with the third commit. I only left this separate as it may be easier to review the commits separated.

Windows Build 2176 is now running using a merge of 7eca3367c0240b90fed5a2feee172958594d6862

Linux Build 7124 is now running using a merge of 7eca3367c0240b90fed5a2feee172958594d6862

Linux with security manager Build 1997 is now running using a merge of 7eca3367c0240b90fed5a2feee172958594d6862

Linux with security manager Build 1997 outcome was SUCCESS using a merge of 7eca3367c0240b90fed5a2feee172958594d6862
Summary: Tests passed: 889, ignored: 286 Build time: 0:07:13

Linux Build 7124 outcome was FAILURE using a merge of 7eca3367c0240b90fed5a2feee172958594d6862
Summary: Tests failed: 9 (9 new), passed: 2934, ignored: 357 Build time: 0:44:55
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.security.jacc.JACCAuthzPropagationTestCase.testBridge: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCAuthzPropagationTestCase.testTarget: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCForEarModulesTestCase.testWebPermissions: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCForEarModulesTestCase.testEJBPermissions: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCTranslateServletDDTestCase.testHTTPMethodCanonical: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCTranslateServletDDTestCase.testConnectionType: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCTranslateServletDDTestCase.testQualifiedPatterns: <no details avaliable>

org.jboss.as.test.integration.domain.mixed.eap630.MixedDomain630TestSuite: org.jboss.as.test.integration.domain.mixed.eap620.MixedDomain620TestSuite: <no details avaliable>

org.jboss.as.test.integration.domain.mixed.eap630.MixedDomain630TestSuite: <no details avaliable>

Windows Build 2176 outcome was FAILURE using a merge of 7eca3367c0240b90fed5a2feee172958594d6862
Summary: Tests failed: 11 (9 new), passed: 2932, ignored: 357 Build time: 0:45:12
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.security.jacc.JACCAuthzPropagationTestCase.testBridge: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCAuthzPropagationTestCase.testTarget: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCForEarModulesTestCase.testWebPermissions: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCForEarModulesTestCase.testEJBPermissions: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCTranslateServletDDTestCase.testHTTPMethodCanonical: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCTranslateServletDDTestCase.testConnectionType: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCTranslateServletDDTestCase.testQualifiedPatterns: <no details avaliable>

org.jboss.as.test.integration.domain.mixed.eap630.MixedDomain630TestSuite: org.jboss.as.test.integration.domain.mixed.eap620.MixedDomain620TestSuite: <no details avaliable>

org.jboss.as.test.integration.domain.mixed.eap630.MixedDomain630TestSuite: <no details avaliable>

org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutRelayedToBackups: <no details avaliable>

org.jboss.as.test.manualmode.ejb.client.cluster.EJBClientClusterConfigurationTestCase.testServerToServerClusterFormation: <no details avaliable>

##### there are 1 more failed tests, see build details

retest this please

Linux Build 7139 is now running using a merge of 7eca3367c0240b90fed5a2feee172958594d6862

Windows Build 2192 is now running using a merge of 7eca3367c0240b90fed5a2feee172958594d6862

Linux with security manager Build 2012 is now running using a merge of 7eca3367c0240b90fed5a2feee172958594d6862

Linux with security manager Build 2012 outcome was SUCCESS using a merge of 7eca3367c0240b90fed5a2feee172958594d6862
Summary: Tests passed: 889, ignored: 286 Build time: 0:07:15

Windows Build 2192 outcome was FAILURE using a merge of 7eca3367c0240b90fed5a2feee172958594d6862
Summary: Tests failed: 9, passed: 2930, ignored: 359 Build time: 0:45:06
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.security.jacc.JACCAuthzPropagationTestCase.testBridge: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCAuthzPropagationTestCase.testTarget: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCForEarModulesTestCase.testWebPermissions: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCForEarModulesTestCase.testEJBPermissions: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCTranslateServletDDTestCase.testHTTPMethodCanonical: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCTranslateServletDDTestCase.testConnectionType: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCTranslateServletDDTestCase.testQualifiedPatterns: <no details avaliable>

org.jboss.as.test.integration.domain.mixed.eap630.MixedDomain630TestSuite: org.jboss.as.test.integration.domain.mixed.eap620.MixedDomain620TestSuite: <no details avaliable>

org.jboss.as.test.integration.domain.mixed.eap630.MixedDomain630TestSuite: <no details avaliable>

Linux Build 7139 outcome was FAILURE using a merge of 7eca3367c0240b90fed5a2feee172958594d6862
Summary: Tests failed: 9, passed: 2930, ignored: 359 Build time: 0:46:56
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.security.jacc.JACCAuthzPropagationTestCase.testBridge: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCAuthzPropagationTestCase.testTarget: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCForEarModulesTestCase.testWebPermissions: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCForEarModulesTestCase.testEJBPermissions: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCTranslateServletDDTestCase.testHTTPMethodCanonical: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCTranslateServletDDTestCase.testConnectionType: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCTranslateServletDDTestCase.testQualifiedPatterns: <no details avaliable>

org.jboss.as.test.integration.domain.mixed.eap630.MixedDomain630TestSuite: org.jboss.as.test.integration.domain.mixed.eap620.MixedDomain620TestSuite: <no details avaliable>

org.jboss.as.test.integration.domain.mixed.eap630.MixedDomain630TestSuite: <no details avaliable>

Linux Build 7144 is now running using a merge of e6c5e1638f896406fa93f2fdf934abff9dc3933d

Linux with security manager Build 2017 is now running using a merge of e6c5e1638f896406fa93f2fdf934abff9dc3933d

Windows Build 2197 is now running using a merge of e6c5e1638f896406fa93f2fdf934abff9dc3933d

Linux with security manager Build 2017 outcome was SUCCESS using a merge of e6c5e1638f896406fa93f2fdf934abff9dc3933d
Summary: Tests passed: 889, ignored: 286 Build time: 0:07:27

Linux Build 7144 outcome was FAILURE using a merge of e6c5e1638f896406fa93f2fdf934abff9dc3933d
Summary: Tests failed: 9, passed: 2933, ignored: 357 Build time: 0:45:38
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.security.jacc.JACCAuthzPropagationTestCase.testBridge: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCAuthzPropagationTestCase.testTarget: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCForEarModulesTestCase.testWebPermissions: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCForEarModulesTestCase.testEJBPermissions: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCTranslateServletDDTestCase.testHTTPMethodCanonical: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCTranslateServletDDTestCase.testConnectionType: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCTranslateServletDDTestCase.testQualifiedPatterns: <no details avaliable>

org.jboss.as.test.integration.domain.mixed.eap630.MixedDomain630TestSuite: org.jboss.as.test.integration.domain.mixed.eap620.MixedDomain620TestSuite: <no details avaliable>

org.jboss.as.test.integration.domain.mixed.eap630.MixedDomain630TestSuite: <no details avaliable>

Windows Build 2197 outcome was FAILURE using a merge of e6c5e1638f896406fa93f2fdf934abff9dc3933d
Summary: Tests failed: 11, passed: 2931, ignored: 357 Build time: 0:46:10
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.security.jacc.JACCAuthzPropagationTestCase.testBridge: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCAuthzPropagationTestCase.testTarget: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCForEarModulesTestCase.testWebPermissions: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCForEarModulesTestCase.testEJBPermissions: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCTranslateServletDDTestCase.testHTTPMethodCanonical: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCTranslateServletDDTestCase.testConnectionType: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCTranslateServletDDTestCase.testQualifiedPatterns: <no details avaliable>

org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutRelayedToBackups: <no details avaliable>

org.jboss.as.test.manualmode.ejb.client.cluster.EJBClientClusterConfigurationTestCase.testServerToServerClusterFormation: <no details avaliable>

org.jboss.as.test.integration.domain.mixed.eap630.MixedDomain630TestSuite: org.jboss.as.test.integration.domain.mixed.eap620.MixedDomain620TestSuite: <no details avaliable>

org.jboss.as.test.integration.domain.mixed.eap630.MixedDomain630TestSuite: <no details avaliable>

##### there are 1 more failed tests, see build details

Windows Build 2199 is now running using a merge of 44b096db24a094b4ead9a81b1ab6014d5853bc3d

Linux Build 7146 is now running using a merge of 44b096db24a094b4ead9a81b1ab6014d5853bc3d

Linux with security manager Build 2019 is now running using a merge of 44b096db24a094b4ead9a81b1ab6014d5853bc3d

Linux with security manager Build 2019 outcome was SUCCESS using a merge of 44b096db24a094b4ead9a81b1ab6014d5853bc3d
Summary: Tests passed: 889, ignored: 286 Build time: 0:06:28

Linux Build 7146 outcome was FAILURE using a merge of 44b096db24a094b4ead9a81b1ab6014d5853bc3d
Summary: Tests failed: 7, passed: 2963, ignored: 357 Build time: 0:46:22
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.security.jacc.JACCAuthzPropagationTestCase.testBridge: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCAuthzPropagationTestCase.testTarget: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCForEarModulesTestCase.testWebPermissions: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCForEarModulesTestCase.testEJBPermissions: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCTranslateServletDDTestCase.testHTTPMethodCanonical: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCTranslateServletDDTestCase.testConnectionType: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCTranslateServletDDTestCase.testQualifiedPatterns: <no details avaliable>

Windows Build 2199 outcome was FAILURE using a merge of 44b096db24a094b4ead9a81b1ab6014d5853bc3d
Summary: Tests failed: 9, passed: 2961, ignored: 357 Build time: 0:48:54
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.security.jacc.JACCAuthzPropagationTestCase.testBridge: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCAuthzPropagationTestCase.testTarget: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCForEarModulesTestCase.testWebPermissions: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCForEarModulesTestCase.testEJBPermissions: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCTranslateServletDDTestCase.testHTTPMethodCanonical: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCTranslateServletDDTestCase.testConnectionType: <no details avaliable>

org.jboss.as.test.integration.security.jacc.JACCTranslateServletDDTestCase.testQualifiedPatterns: <no details avaliable>

org.jboss.as.test.clustering.xsite.XSiteSimpleTestCase.testPutRelayedToBackups: <no details avaliable>

org.jboss.as.test.manualmode.ejb.client.cluster.EJBClientClusterConfigurationTestCase.testServerToServerClusterFormation: <no details avaliable>

Linux Build 7161 is now running using a merge of 949329c5dd3b690aafb9b5cdd1bf7ef95d67424e

Linux with security manager Build 2033 is now running using a merge of 949329c5dd3b690aafb9b5cdd1bf7ef95d67424e

Windows Build 2217 is now running using a merge of 949329c5dd3b690aafb9b5cdd1bf7ef95d67424e

Linux with security manager Build 2033 outcome was SUCCESS using a merge of 949329c5dd3b690aafb9b5cdd1bf7ef95d67424e
Summary: Tests passed: 891, ignored: 284 Build time: 0:09:18

Linux Build 7161 outcome was SUCCESS using a merge of 949329c5dd3b690aafb9b5cdd1bf7ef95d67424e
Summary: Tests passed: 2965, ignored: 356 Build time: 0:47:03

Windows Build 2217 outcome was SUCCESS using a merge of 949329c5dd3b690aafb9b5cdd1bf7ef95d67424e
Summary: Tests passed: 2963, ignored: 357, muted: 1 Build time: 0:54:28


fix: compatibility with mysql8.0

What this PR does:
fix compatibility with mysql8.0
Which issue(s) this PR fixes:

Fixes #449
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Codecov Report
Base: 35.96% // Head: 35.86% // Decreases project coverage by -0.09% :warning:

Coverage data is based on head (de69364) compared to base (186a3f8).
Patch coverage: 3.35% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #450      +/-   ##
==========================================
- Coverage   35.96%   35.86%   -0.10%
==========================================
  Files         124      124
  Lines       19966    20599     +633
==========================================
+ Hits         7180     7388     +208
- Misses      12000    12393     +393
- Partials      786      818      +32

Impacted Files
Coverage Δ

pkg/boot/discovery.go
53.57% <0.00%> (+10.57%)
:arrow_up:

pkg/config/api.go
80.00% <ø> (ø)

pkg/config/config.go
0.00% <0.00%> (ø)

pkg/config/default.go
96.29% <ø> (+10.58%)
:arrow_up:

pkg/config/diff.go
9.64% <ø> (-0.68%)
:arrow_down:

pkg/config/equals.go
7.69% <ø> (+1.59%)
:arrow_up:

pkg/config/etcd/etcd.go
78.81% <ø> (+5.12%)
:arrow_up:

pkg/config/file/file.go
73.93% <ø> (-0.06%)
:arrow_down:

pkg/config/nacos/nacos.go
41.17% <ø> (+2.56%)
:arrow_up:

pkg/executor/redirect.go
4.54% <ø> (-0.37%)
:arrow_down:

... and 18 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


add a to_json for all serializable classes

Current access patterns for serialized data in various classes are difficult to maintain. necessary to make a more standard to_json method which can be called from a top level json.dumps.

not necessary at this time, LOCO is adequate. Might be important for niche applications but won't be built in.


SIMD splat instruction throws "index lane" error?

Error even if there's no index lane value and related instruction.
To reproduce, launch the test suite: npm run test

Solved with last versions of Node/Chrome


Selective updates of modules

I don't like to include non-standard expressions in import specifiers. Therefore, the solution here would be just providing ignore and only options in APIs and the CLI.

I haven't encountered a situation where this is needed so...

OK now I need to skip x/import_map since the module has a problem. Let's implement this feature.
https://github.com/hasundue/molt/pull/84


Has This Project Been Abandoned; Can Anyone Help?

@tomlandia @victorgrego @shyrat @genevera @Kav28
Hey Tom, Victor, Shyrat and Genevera, anyone who can help:
Has this project  been abandoned?? I know Tom is busy but he said many things needed to be updated with nw 0.12.1 . Can anyone else update or help to fix the issues. It's like mine never logs in anymore, I tried blocking on the software and they are still there on the phone's app. Also messages only appear in Fuckr but not in grindr chat when someone messages me and I close out. The process does not get killed when the program is closed until a hard reset. IT would be nice to have the ability to do multiple logins, say if someone blocks you to check using a different login / logins for different moods / times. The program retains the last login info even if you logout, especially if there is a memory / program crash.
Thanks for ALL YOUR WORK!
;-)

@tomlandia
tomlandia commented on May 7 • edited
I'm confused as if it's yet another weird v1.6.1 bug but going to implement XMPP disconnect just to make sure.
@genevera
genevera commented on May 27
@tomlandia i think maybe it's confirmchatmessagesdelivered that deletes them from the server. I've been experimenting with that locally and it seems to be the case.

powline99 commented on May 3 • edited
@tomlandia Fuckr will not logout, it stays in the background processes after the program is closed or crashes (seems I am still on Grindr still). Multiple instances taking up resources. Have to do full shutdown to make them go away.
@tomlandia
Owner
tomlandia commented on May 7
Yeah v1.6.1 is a shitshow sorry. It's not the one on Fuckr.me. Going to release 1.6.2 using nw 0.12.1.

nw.js ›
Single process mode is now supported in 0.14.x
_Apr 20
You can launch nw with command line argument '--single-process' from upstream. And then nw will run in single process mode.

Hi @powline99 - have you pulled the latest version of master / 1.6.1 and built the application therefrom?  If you're on OSX I can give you the one-liner I use to build and launch the app each time.  I haven't been doing much beyond playing around with increasing the accuracy of long distance pinpointing and disallowing the confirmChatMessagesDelivered API call.  I may look into improving a couple of missing features / bugs that I've encountered in my own use but seeing as I am not the author of this project do not take that as evidence that it hasn't been dropped :)

Hi @genevera thank you for taking your time to help, unfortunately I am on Windows 7 32bit. The biggest annoyance to me is it's like Fuckr is running a separate profile using my username and password for my phone's app. I get a error like icon and then I see messages that do not show up while I do not use the software in my app. Before it shared the same profile. It's really weird that since the login and password across platforms does not share the profile. Perhaps it is not connecting to the server and by me blocking on the pc program it's not even communicating with gindr (When I open the iphone app all the blocks are still there, before we would get a eclipse server error and it would log you out of the software / shutdown). Kinda like if you never login to grindr. Secondly it is very annoying that when the software crashes on my pc, it has a phantom process and when I open it up again it continues to run and use resources in the background, it is not killing the process and the only way to get rid of the stacks of them is to restart the computer  (when it closes everything should be killed and not stay logged in). I think tom found some Google single process work around below.
Thanks for all your help!
P
@tomlandia was working on these issues:

Error Pops up every so often (while chatting, deleting, or blocking), eclipse wants login (I must go put in CAPTCHA phrase and click to get rid of Fuckr errors. Shows brief screen with unblocked local profiles. Second image is a error type thing after CAPTCHA phrase and then it goes to main screen.
2016-04-28_082528
2016-04-28_072714
Could we implement that "Looks like https://groups.google.com/forum/#!topic/nwjs-general/LtJql3LSV44 may offer a solution provided it's stable and we can add a nw command line flag to releases"

powline99 commented on May 3 • edited
@tomlandia Fuckr will not logout, it stays in the background processes after the program is closed or crashes (seems I am still on Grindr still). Multiple instances taking up resources. Have to do full shutdown to make them go away.
@tomlandia
Owner
tomlandia commented on May 7
Yeah v1.6.1 is a shitshow sorry. It's not the one on Fuckr.me. Going to release 1.6.2 using nw 0.12.1.

@tomlandia Map function not working when I click on world icon in profiles, it just spins and does nothing. Map does work if you use drop down view in main screen. Could this be my spam blocker in Chrome or setting not to open new windows, just tabs?
Thanks!
@Kav28
Kav28 commented on Apr 28
Have had that prob but think it happens sporadically - might be due to
load.
…
@tomlandia
Owner
tomlandia commented on May 7
V1.6.1 is a shitshow sorry. It's not the one on Fuckr.me. Going to release 1.6.2 using nw 0.12.1.

@tomlandia
Can't get the Conversion Metric / US Setting Drop Down to Work. I logged in and out. Tried to close down the program / open. Nothing seems to change not even my profile settings to inches and pounds ;-p
@tomlandia
Owner
tomlandia commented on May 7
Works fine in dev but only in profile view.

This one is a bit strange. I start chats while at my laptop on the same username as my IOS mobile. I know chats do not save across platforms but before I was able to start a convo and then go mobile and also have a new chat open up if the person responded. Now the responses only go to Fuckr even if the software is closed and I am fully mobile and logged in for a few hrs??? I wonder if this has to do with the phantom processes / sessions after crash issue I posted before, it still thinks I am logged in and so never truly closes software / logs out. I tried to manually log out same thing, but if a session is running after a crash and stuck in memory then I suppose it does nothing.
@Kav28
Kav28 commented on Apr 28
If I start a chat with the most current version of Fuckr, sign out and then
start a older version of Fuckr replies to the chat will not come in until I
sign out and then start the new version of Fuckr. If I have two users (not
used at the same time) chat history of both users will be visible but new
messages will not appear until I am signed in as the user intended for the
chat (changed behavior from earlier versions).
…
@tomlandia
Owner
tomlandia commented on May 7 • edited
I'm confused as if it's yet another weird v1.6.1 bug but going to implement XMPP disconnect just to make sure.
@genevera
genevera commented on May 27
@tomlandia i think maybe it's confirmchatmessagesdelivered that deletes them from the server. I've been experimenting with that locally and it seems to be the case.

i have also wondered if the program has been abandoned. i had never used fuckr/grindr before until February, and used it regularly once I got it. i had occasional msg blackouts, but for the most part it worked well. however the new version made things worse... ive only gotten a message from one user in the past 40 days, and i asked if he was real and not spam and to type a word to prove he was real, and he did.
i am able to log online, but im never visible to other members, and never get email from other members (99% of the time). this version for some reason, works a lot worse than the version before it. i installed the earlier version after all the problems with the new version, and there's no improvement, i dont know why. i have both versions on my computer, currently.
i do want to comment that i do like the search options on the new version of age, ethnic background, types (i love otter types and Middle Eastern types for example, and it brings up so many attractive guys!). however this new version doesnt give us the option to choose our own "tribes" so that we show up for other members, for example i cant select myself as an otter.
also, in both versions, i have never been able to view my own profile. is it possible in a future version that we can view our own profile?
i have been checking for a new version since mid may when all the problems started, and ive pretty much given up on grindr/fuckr, and been telling people on other sites, that i never can use grindr anymore. its really frustrating since i see so many other guys are actually on grindr and i cant even communicate with them.
i get this msg pop up a lot on the newer version:
"XMPP chat error. If you're using public wifi, XMPP protocol is probably blocked."
I would have attached an image I screenshotted when this happened, but it said that github doesnt allow bitmap files to be uploaded for some reason, as that is what i saved it as, as that is the default format when one screenshots into the paint program.
I suspect the above reason is why fuckr never will show me online/get msgs anymore. ive also tried using a different email account under registration to try to see if that will allow me on grindr/fuckr and it has no impact.
If there is a way to have XMPP protocol UNBLOCKED someone tell me how, and I will try to see if I can do that. the only internet connection i have is wireless.

im chatting to a guy on another site that says he can get grindr to work fine today (June 6, 2016)... but im assuming he's using the real grindr, and not fuckr. i never knew of anyone i chatted with on there that was using fuckr other than myself.
theres a few reasons i dont use grindr on my phone.
a) ive never been an app person in general. about the only app i use is my photo album, to take pictures with and send pictures out.
b) file size. even when fuckr worked right back in february/march and part of april, when conversations kept going on and on, it uses a lot of memory not just to operate the program, but in file sizes of conversation logs. i dont want all that weighing down my phone. a computer can handle all that far easier. also, a computer has an expanded window, so you dont have everything compressed to a small screen.
i tried using bluestacks for another program once, but i got rid of it. im not a fan of google at all, and i dont like how they pervade nearly every device and website possible, them admitting to spying and storing private data on everyone, just isnt something i condone. i try to avoid anything that deals with google. however if fuckr incorporates technology that is google-based, im willing to accept that, but ill still avoid google in general otherwise.
maybe someone could track down the creator of "Chat Client" that was used for gay dot com back in the 2000's era, and get some technical advice from them, and maybe even see if they want to contribute to this project. one of the reasons gay dot com was so successful was because of chat client, and once gay dot com changed the design layout of their entire website, and blocked chat client from accessing them, nearly half of all members of their site (including me) left. i probably used gay dot com about 300 days out of 365 days for many years back during their peak era. ive only used gay dot com about 7 days in the past 2 years, now. they shot their own foot off, they had such an empire of members (i met guys from it), but i digress.
im not technically advanced when it comes to technology about the builds on here. i tried doing something back in may (you contributed to that discussion), but the program wouldnt edit at all for me. so i gave up.
as for removing all traces... i did at first, and this caused more problems than less. because when i got the newer version, it would not create its own folder, like the older version had. i had removed too much traces of the older version. i have considered removing all traces of both versions i have now, and then downloading the latest version again, and see if that works. but if i do that, ill erase all the msg histories currently stored.
grindr is good at bringing in so many attractive guys, which is why its so frustrating how i cant interact with them. its like being a kid in a candy store and not having any teeth. :D
i do hope that tom, or someone else continues working on this, and lets the mantle of fuckr continue on in years to come, with improvements that are so profound that we forget these errors that are occurring. due to my ignorance of program technology, all i have to do is wait and wish more enlightened wisdom on the program creator(s).

I ended up deleting all the data of fuckr from my computer both the recent version and the older version and downloaded the april version. I was able to get online briefly, but I was unable to update any of the age/weight/height information. I tried, and went to a different window, and when I went back to this page, they were all cleared. After re-entering it, it was cleared again.
and now I cannot get online at all. it says "requests to the server have been blocked by an extension". with a frowny face above it. i would post a screenshotted pic but github doesnt allow bmp files.
does this mean that grindr has blocked all fuckr users from getting online?
if so, i hope tom can bypass this.
right now, it is impossible to get online at all, and when i was actually online, i was able to view profiles, and now i cant even do that. it seems each time i remove fuckr from the registry, a downloaded version is even worse than the one before.
if tom doesnt want to be part of this project anymore, maybe he could appoint someone else in this community to work on it?

@newtofuckr I don't know what to tell you, haha. Well just have to wait and see if their is a response. I would suggest you get the app for your phone in the mean time or download like bluestacks and install it.

Sorry about not updating sooner. I think I've fixed the recent chat problem even if Grindr now does certificate pinning so it's harder to reverse engineer (documentation will have to be updated). I'll release a new version tonight (European time) latest. Closing this issue as it's redundant with #61.


Added iGlance

NOTE: A similar PR may already be submitted! Please search among the Pull request before creating one.
Types of Changes
What types of changes does your PR introduce? Put an x in all boxes that apply

[x] New addition to list
[ ] Fixing bug in existing item in list
[ ] Removing item from list
[ ] Changing structure (organization) of list

Proposed Changes
Describe each of your changes here to communicate to the maintainers why we should accept this pull request.
As I said in the commit comment, I think it is a pretty neat tool for the menu bar. There is a similar paid tool called iStat. Because I couldn't find a free alternative, I decided to make one for free. And since I think it can be useful for a lot of people, I would be happy to see it on the list :)
PR Checklist
Put an x in the boxes once you've completed each step. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING guide
[x] I have explained why this PR is important
[x] I have added necessary documentation (if appropriate)

Further Comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

Thanks for contributing!

Wow, you are fast! thanks :D


Support .opossum files: create info popup

Summary of changes
Implement a new popup for providing information to the user if an outdated
filetype (other than .opossum) is opened. The corresponding component is
not wired.
How can the changes be tested
Uncomment lines 58-60 in importFromFile.ts, restart application, and open a file. The popup should be displayed. Since it is not wired, the file will load anyway, independent of the user decision.
Screenshot of the popup:

I think the changes should be based on the current main branch, not POC, because we are currently working on that.
The popup should be shown only if we open old format.

@vasily-pozdnyakov regarding your comment

Makes sense when thinking about it. Rebased.
This should be taken care of in the upcoming ticket about wiring the popup. In the current ticket, the popup is not visible at all. Only when uncommenting the lines mentioned in the PR comment (for review only).
Good suggestion. I adapted text and buttons.


Right Click "Release Item" edits tag rather than removes

Right clicking on remove item in bank to remove seems to just prompt to edit?

Goes to this ->

Fixed in #1440

@Adam- Will a new release be pushed to fix this behavior, or will players encountering this issue need to disable the plugin until next Thursday?

Adam's working on pushing this out as a hotfix today, far as I can tell.


How do I send an IOS signed filecoin transaction through the lotus node, I encountered the following error

Describe the bug
When I use IOS signed filecoin transaction to broadcast lotus testnet node, there is an error(decode unmarshaling t.Message: cbor input had wrong number of fields). How can I solve this problem
Screenshots
ios sign got the result: 82885501a699731e9d4f382d01539a72985a431c75f74b9b55014074462b17b9d28f6579acdf634c1d28af2e89110048004f550445d5a000430013884300c35000405842013dd5cb90d156b356e7d53c8f85600c838b132afdb3896cd67f5ec6e379c658b708346b8d5d418a57125318448b18c6e735a889d80ac4e12e70e14d9303da6ca700

go decode signedMessage got the error :  decode unmarshaling t.Message: cbor input had wrong number of fields

And, How can I solve this problem?

Maybe missed “from”

probably lotus has some new updates, will check it soon

can you share your golang decoding code?

`func DecodeSignedMessage(data []byte) (*SignedMessage, error) {
var msg SignedMessage
if err := msg.UnmarshalCBOR(bytes.NewReader(data)); err != nil {
return nil, err
}
return &msg, nil

}`

Here! https://github.com/filecoin-project/lotus/blob/master/chain/types/signedmessage.go            `func DecodeSignedMessage(data []byte) (*SignedMessage, error) {
var msg SignedMessage
if err := msg.UnmarshalCBOR(bytes.NewReader(data)); err != nil {
return nil, err
}
return &msg, nil

}`

Here!  https://github.com/filecoin-project/lotus/blob/master/chain/types/signedmessage.go
`func DecodeSignedMessage(data []byte) (*SignedMessage, error) {
var msg SignedMessage
if err := msg.UnmarshalCBOR(bytes.NewReader(data)); err != nil {
return nil, err
}
return &msg, nil

}`

@hewigovens iirc Filecoin changed the message layout since original integration. I'll take a look later today!

@terorie Thanks 🙏

@togiter Here's a version of wallet-core that should fix this issue: https://github.com/terorie/trustwallet-core/tree/terorie/filecoin-changes
If you could verify that it indeed solves your issue, that'd be great!

How do I verify with ios Cocoapods Import？

we will publish a new build later, so you can verify it

I got the same error using cocoapods' latest trustwallet core (v2.1.3), haven't you built the latest package yet?

could you please try 2.1.4?

swift sign tx：82885501a699731e9d4f382d01539a72985a431c75f74b9b55014074462b17b9d28f6579acdf634c1d28af2e89110048004ef2ca9032e000430013884300c3500040584201e73d6e65cbdc680dbb67cede877f5503199554e94a38dd11708f0524fc349f6075f5d0548996937fd240c21c9dc30a56ed8ed04aa25ecec6da135b8bcfb9d8a401
pod trustcore v2.1.4 got the same error ：unmarshaling t.Message: cbor input had wrong number of fields。

have you tired to clean and rebuild your swift project? the length of your data(134 bytes) seems shorter than FilecoinTests.swift (164 bytes)

@togiter The CBOR message you posted decodes to this (https://cbor.me):
82                                      # array(2)
   88                                   # array(8)  # <==== This indicates the old version
      55                                # bytes(21)
         01A699731E9D4F382D01539A72985A431C75F74B9B
      55                                # bytes(21)
         014074462B17B9D28F6579ACDF634C1D28AF2E8911
      00                                # unsigned(0)
      48                                # bytes(8)
         004EF2CA9032E000
      43                                # bytes(3)
         001388
      43                                # bytes(3)
         00C350
      00                                # unsigned(0)
      40                                # bytes(0)
   58 42                                # bytes(66)

The version field is missing, so I'm 90% sure this is generated by the old version of wallet-core.
The new wallet-core version generates array(9), which is compatible with new Lotus.

Yes, now it is. I used to use pod update and pod install = > pod 'trustwalletcore' '~ > 2.1.4'
Get the same error, but remove the pod 'trustwalletcore', '~ > 2.1.4' = > pod install, and then re install it. The build is successful.

@hewigovens  New I Got the Same Error unmarshaling t.Message: cbor input had wrong number of fields, FileCoin Space Race Network not support yet! , When can you add support Space Race Network?

We don't have plans to do it now.  Contribution from FileCoin community is welcome.

@togiter do you know what has been changed in space race network?

The Msg Struct is `
type Message struct {
Version uint64
To   address.Address
From address.Address

Nonce uint64

Value abi.TokenAmount

GasLimit   int64
GasFeeCap  abi.TokenAmount
GasPremium abi.TokenAmount

Method abi.MethodNum
Params []byte

}
`
A little bit of a change is move ‘gasPrice’ field, Added ‘GasFeeCap’，‘GasPremium’ fields!
https://github.com/filecoin-project/lotus/blob/master/chain/types/message.go

Thanks for the info, will take a look soon

@catenocrypt @togiter could you guys please take a look the new changes if any chance, mainnet is going to launch soon (hopefully), I will take a look after web3 stuff on iOS

@hewigovens I can file a PR if you want.

@terorie for sure, thanks 🙏, hope this is the last time change before mainnet

Space race network has become stable. When can you add support for filecoin message signature!

Same problem, field has been changed, hope to be supported as soon as possible

@terorie is working on this, he will open a pr soon, be patient :)

See my PR #1114 for a fix to this, updating wallet-core to the latest Filecoin message ABI.
@togiter @wjd-jax these "+1" comments are not helpful, won't help prioritize and just spam everyone's inbox. Please use the :+1: or :-1: buttons on GitHub to show support instead.


ConfigMap of peer restore sometimes somehow

we changed some value in the configmap org1-peer0--peer--core, which is basically the core.yaml of the peer, but somehow the changes are reverted to original after some time. We don't really know when.
How can they stay permanently?

Hi @luca-simonetti
The configmap of the peer is automatically generated by the operator, that's why it will get restored when operator synchronizes the peer.
What kind of configuration you want to customize?

hi!
the configuration we're trying to change are basically three and they all reside in core.yaml
totalQueryLimit
limits. endorserService
limits. deliverService

@luca-simonetti
You can use environment variables to configure these properties dynamically.
You can look at this: https://stackoverflow.com/a/48868576/5468614


Wrong topic in section Test the API

This tutorial is about creating a To Do API but section 'Test the API' states "The project template creates a WeatherForecast API" and shows sample JSON containing weather information. This makes for a very confusing tutorial.

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

ID: 583ae3e7-5915-f22b-e54c-6c100cf2a7da
Version Independent ID: 95f2549e-29f9-e31a-b4d0-432b971643ff
Content: Tutorial: Create a web API with ASP.NET Core
Content Source: aspnetcore/tutorials/first-web-api.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

The templates create WeatherForecast


Missing attributes from the regular Text widget

strutStyle
locale
softWrap
overflow
textScaleFactor
maxLines

@IhorKlimov I apologize for the delay in responding. Because this widget is built using an underlying EditableText widget, then the only parameters it can support are the same as the TextField. Therefore, all of the above are not supported, except for maxLines. However, maxLines also has an issue where if it's set, the widget will actually lay itself out taking up all the space necessary for that number of lines, even if the Text supplied is shorter, so I decided to not support it.


merge head version into jdk

fix #8401
Merged Head version step into jdk step with jdk8

The jdk step inputs jdk version into mvn -P, like 'individual,pre-merge,jdk11', but head version step does not, 'individual,pre-merge'.
In this case, I make activate profiles as an item of matrix. https://github.com/NVIDIA/spark-rapids/pull/8564/files#diff-031910b9e60925c8a39b96ae87fd04572bc53b41b28ced0fbb35b95790cf9613R67
Can we align the arguments of mvn -P for these 2 steps, so that we don't need to add profiles to the matrix. cc @pxLi

The jdk step inputs jdk version into mvn -P, like 'individual,pre-merge,jdk11', but head version step does not, 'individual,pre-merge'.
In this case, I make activate profiles as an item of matrix. https://github.com/NVIDIA/spark-rapids/pull/8564/files#diff-031910b9e60925c8a39b96ae87fd04572bc53b41b28ced0fbb35b95790cf9613R67
Can we align the arguments of mvn -P for these 2 steps, so that we don't need to add profiles to the matrix. cc @pxLi

sound OK to me. Also please remove/comment out verify-all-modules-with-headSparkVersion in this PR even its still in draft to make it clear whats the purpose for the change, thx

OK
Removed profiles from matrix. Just added jdk8 and head spark version as default version to the matrix.
Also renamed the step as verify-all-modules, the original name verify-modules-with-jdk may cause misunderstanding that the step is only a JDK test.

can we please have a more descriptive title and description on this?   It should be descriptive about what and why the change is being made.

build


Update bindings

As mentioned in #100 , these are the new bindings. You should be able to reproduce these changes by doing the following:

Download the newest version of the Steamworks SDK (1.53a in this case)
cd steamworks-sys
Delete the public and redistributable_bin folders from lib/steam
Unpack the SDKs' public and redistributable_bin folders into lib/steam
cargo clean (might not be necessary if you pulled from scratch, if you didn't, there is a high likelihood that the bindings are not regenerated! I've had that happening)
cargo build --features rebuild-bindings

This is a fairly large diff, so I hope it doesn't break anything.
Seemingly the bindings now feature various packed reprs and more changes.

The steamworks SDK v1.54 just got released! Maybe we can upgrade to it directly.

I will check really quick :D

It seems like the bindings generated are different depending on which platform you're using. I bound against v153a on Windows when generating those bindings. A quick look at the generated code seems to have #define variables that correspond to Linux. We may need to have platform specific bindings in the repo.

It seems like the bindings generated are different depending on which platform you're using. I bound against v153a on Windows when generating those bindings. A quick look at the generated code seems to have #define variables that correspond to Linux. We may need to have platform specific bindings in the repo.

That makes sense... Would definetly explain the issues I have faced, if the bindings that are in currently were made on a Windows PC... though I guess another way would be to introduce build caching and let the bindings be generated once for a version via build script. As the Steamworks SDK provides redistributables, this could also solve the issue, but increases the crate size and probably pumps up the first compile time by a fair amount.

It seems like the bindings generated are different depending on which platform you're using. I bound against v153a on Windows when generating those bindings. A quick look at the generated code seems to have #define variables that correspond to Linux. We may need to have platform specific bindings in the repo.
Happy to approve the new v154 bindings when made available, but we likely need a separate PR to split the bindings based on target.

Hmm... Are the bindings different if you just change the target? Or are they only different if they're built on Windows/Mac/Linux? That result would change the way the new PR would have to be implemented.

Alright, I created #105 for v1.53a platform-specific bindings and #106 for v1.54 platform-specific bindings

Closing this in favor of #106


Datajoin cleanup

Fixes #474 and fixes #443
This PR depends on #475

Includes fix for comment from #475

Superseded by #483


Atualiza a techstack do projeto no README para incluir Redux e Saga

Coverage remained the same at 45.918% when pulling a06bed816113f00d043d29a5fa1e130486414252 on add-redux into 4d3a90a84078042845e724f0d7d83474c4b3318c on master.


File is in stage not download dir

Coverage remained the same at 81.034% when pulling e66691d01ab4529eef7cfb7ccd28db032fc47377 on fix-upload-to-s3 into<PHONE_NUMBER>990d5695f9323fc4464e3025ebda80 on master.

Coverage remained the same at 81.036% when pulling 6118518ba6ba5da59550e306a505627a84a0e6af on fix-upload-to-s3 into 1ebd997cec9d94d5332021b50e76cf7c501b2c7a on master.


⚠ ClamAV has degraded performance

In b145a32, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 86 ms

Resolved: ClamAV performance has improved in 222e121.


Fix caching for post requests

Posts should not be cached

Do you mean for the Http cache on the website?

@dantleech the caching header is set and it seems this is the problem that a post still returned the cached page #747

The cache stuff from @dantleech is merged, so this should not be an issue anymore.


any way to use \displaystyle maths?

It would be very useful...

Not right now but you could send a PR


wasmtime vs wasmer

Would wasmtime provide any advantage over wasmer?

There's one blocker for using wasmtime: https://github.com/bytecodealliance/wasmtime-go/issues/34
We need an easy way to capture stdout to receive results from the Prolog interpreter.
We could work around it using files but it's not ideal.
wasmer solves this with a little C shim: https://github.com/wasmerio/wasmer-go/blob/b4462e6583f8d7b964e32bdd8d065cf96fba6c08/wasmer/wasi.go#L18-L54
So it probably wouldn't be too hard to add this to wasmtime.
I think we could also maybe export Go functions WASM and have Trealla call it via FFI to report results, but I'm not quite sure how that works and if it is possible yet.
I would be especially interested in switching to any WASM runtime with good Windows support. Then we can support all major platforms out of the box.

Sorry for "hijacking" this issue, though I do believe what I have observed is not entirely unrelated to the current state of wasmer-go
I have played around with the library, really like the concept, though I have ran into some issues with memory usage.
As an example, the code below demonstrates three separate issues:

Using a single engine instance for a large number of queries will cause memory usage to climb until around 7GiBs or so, at which point all subsquent queries are stuck - I suspect it has to do with the allocator, though I have not verified it. I'm pretty sure a leak is involved somewhere because I do not think any state should be retained from just querying for nl.
Using a single engine instance for a large number of queries that involve host-interop, will cause memory usage to climb until around 2GiBs, at which point I think the interop-related code uses an int32 to slice into WASM-allocated memory, resulting in a panic:

$ go run main.go -- --with-interop
2023/04/20 14:59:30
2023/04/20 15:00:53 trealla: query error: trealla: panic: runtime error: slice bounds out of range [-2130246640:]
exit status 1

The reason I described the issue here lies with this leak. In theory, it is not an issue if a WASM application leaks any memory, since it is very cheap to to just throw it away and allocate one with a fresh slate... except doing so will consume memory infinitely. The runtime does not seem to ever release the instantiated WASM modules/memory, and the result is a far larger, and faster memory leak than just using a persistent instance.

package main

import (
	"context"
	"fmt"
	"log"
	"math/rand"
	"os"
	"time"

	"github.com/trealla-prolog/go/trealla"
)

func newEngine(ctx context.Context) (trealla.Prolog, error) {
	engine, err := trealla.New()
	if err != nil {
		return nil, err
	}

	err = engine.Register(ctx, "invoke", 1, trealla.Predicate(func(pl trealla.Prolog, subquery trealla.Subquery, goal trealla.Term) trealla.Term {
		v := fmt.Sprintf("%v", rand.Float64())
		return trealla.Compound{
			Functor: "invoke",
			Args: []trealla.Term{
				trealla.Atom(v),
			},
		}
	}))
	return engine, err
}

func main() {
	ctx, cancel := context.WithCancel(context.Background())
	defer cancel()

	engine, err := newEngine(ctx)
	if err != nil {
		log.Fatal(err)
	}

	log.Print()
	defer func() {
		recover()
		log.Print()
		os.Exit(2)
	}()

	getEngine := func() trealla.Prolog {
		return engine
	}

	// perhaps ugly, but suffices for testing
	query := `nl`
	for _, arg := range os.Args[1:] {
		switch arg {
		case "--with-interop":
			query = `invoke(A)`

		case "--with-new-instance":
			getEngine = func() trealla.Prolog {
				engine, _ := newEngine(ctx)
				return engine
			}
		}
	}

	for {
		func() {
			ctx, cancel := context.WithTimeout(ctx, 10*time.Second)
			defer cancel()
			engine := getEngine()
			doWork(ctx, query, engine)
		}()
	}
}

func doWork(ctx context.Context, query string, engine trealla.Prolog) {
	resultSet := engine.Query(ctx, query)
	defer resultSet.Close()

	for resultSet.Next(ctx) {
	}

	if err := resultSet.Err(); err != nil {
		log.Println(err)
		os.Exit(1)
	}
}

Since the alternative is getting stuck forever, I'm not entirely sure the int32 issue should be fixed just yet - I would personally prefer crashing and restarting to never getting anywhere at all, for one. But I think, assuming I'm not wrong about the source of the leak when each query is served by a new instance, a different WASM runtime might be more beneficial than it seems at first glance.

Thanks @enoperm, that is very concerning. I’ll look into it 👀

Do remember to use a separate cgroup or something if you run the repro code with --with-new-instance. It is a good way to test your OOM killer...

I think the leak around instantiating new Prologs is my fault, not wasmer's, seems like I forgot to add a Close to Prolog. I'll add that and let's see if it helps.
I think it would also not be too hard to move to wasmtime, Trealla has some stuff now to capture stdout/stderr so we can work around the wasmtime-go issue.

It is possible that I may have been harsh towards wasmer, I suppose. I'm not an expert on the Go runtime, so when I dug into the code and saw that finalizers exist, I just assumed they'd be surely called by the GC before the kernel triggers the OOM killer, and then encountered the previously linked issue and it kind of fit, that if the runtime does not free up things anyway, then any finalizers are pointless.

I'm not too sure how Go's runtime handles them either, TBH, so no worries.
I tried adding a Close() method to the Prolog instance that calls wasmer's instance.Close() but it doesn't seem to help. I'll try and figure out whether it's a problem here or with wasmer-go. I'll also check if trealla-js has the same issue or not (I remember measuring it a while back and it was fine) which will rule out Trealla itself.
Thanks again for the test code, it is very helpful.

trealla-js looks fine so it shouldn't be a problem with Trealla itself. I think the issue here is we hold a global wasmer.Store which probably just infinitely accumulates memory. So we'd need to instantiate a new module for each Prolog to avoid that, but then we run into the wasmer-go bug you linked. I'll see about using a different library.
BTW the interop bug with the negative pointers should be fixed in the next release, but it can still run out of memory if hits 4GB. Not sure if any of the Go libraries support 64-bit WASM but if they do it should be possible to fix that.

Good news, I got wasmtime working (in the wasmtime branch if you want to check it out). Running the test program with --with-new-instance and closing the engine in the loop allows it to properly garbage collect the memory. Also, looks like it properly supports 64-bit Wasm so I'll play around with compiling Trealla to that this weekend.
Bad news, it seems like there's still a leak with queries against a single Prolog instance. Looks like this is happening on the Wasm side, probably from the stuff I added to get wasmtime to work ;). Should be able to fix it.
Also the Tak function benchmark seems like twice as slow on wasmtime vs wasmer, not sure what's up with that.

Found the leak! Got the default test stable at around ~64MB. Looks like there's some weirdness with the interop stuff still, so once that gets fixed we should be good and I'll push the new stuff.

I believe this is what was causing the interop memory issue: https://github.com/trealla-prolog/trealla/issues/162
Once we fix that everything should be solid.

More good news: we've fixed all the leaks. Just need to tweak the interop stuff to work better with wasmtime and I can make a new release.

I have plugged in the wasmtime branch into the toy project where I initially detected the memory leak and I can confirm that it can now serve each request on a new Trealla instance just fine without any apparent leaks. :heavy_check_mark:

Great! I have some more changes I'm just about to push. Will test it a bit more and make a new release shortly.

Hmm, seems like wasmtime can crash sometimes. Probably my fault, investigating.

Whoops, was a concurrency issue, fixed now.
Made an issue for wasm64 support as well: #8


ManualGazeControl arrow keys not working

In inspector for camera -> Manual Gaze Control -> Keyboard,Supported is checked and enabled.
I run more or less an empty  scene with a plane and one 3D object.
The mouse look works fine, but the arrow keys don't work
These are all initialized properly and are not null
public AxisController KeyboardXYRotationAxisControl;
public AxisController KeyboardXZRotationAxisControl;
public AxisController KeyboardXYTranslationAxisControl;
public AxisController KeyboardXZTranslationAxisControl;

Is this for the HoloToolkit component? ManualGazeControl has been replaced with ManualCameraControl and the input simulation service in MRTK.
We don't really support the HoloToolkit anymore. Offhand, I can't think of a reason why ManualGazeControl shouldn't be working the way you describe. I'd say just make sure the AxisControllers are properly assigned and also properly set (check that the AxisType is what you expect, etc)

I am switching back and forth between HoloToolkit and the MRTK, because all the e-books only cover HoloToolKit. Plus I wanted to use it outside of both, that is, in a regular project (because the mouse look is nicely done, and if I could just get the moving part working, I would be happy).
It is very difficult to debug, because the debugging process intercepts the keystrokes as well inside of VS. The AxisType = mouse.... (it is initialized to it).
Even if I disable the mouse support, and only enable the key support, it's still "mouse".''
All the AxisControllers are initialized....at first, I did not do that, but then I fixed it...and again, the mouse looking part works great,....love it....but there is no joy in HoloLand because the arrow keys do not work....

Do I have to do anything or modify anything as far as input in the Unity 3D project settings?

The AxisType = mouse.... (it is initialized to it)

Sounds like you might need to update the KeyboardXYRotationAxisControl etc to be one of the keyboard settings instead of mouse.
ManualCameraControl.unity should be set up properly, to give you an idea.

How do I move forward or backward with just the mouse?
I can look around with mouse, but not move with mouse, aren't I supposed to be able to move with the mouse as well?

           if (KeyboardSupported)             { ,,,,................             Vector3 keyboardXYTranslate = KeyboardXYTranslationAxisControl.GetDisplacementVector3();,,,,................
}

Ugh, I accidentally "closed", how do I unclose?

(thx)
keyboardXYTranslate  always returns back (0.0, 0.0, 0.0{

axisType = AxisType.Mouse;
axisType is initialize to mouse, and never re-assigned to anything else...
What should I use to test it with keyboard?
axisType = AxisType.Keyboard8426;    <---- should I try this?

I'm not sure about moving with the mouse. I don't remember that being supported, but it's been a while since I've look at HTK.

What should I use to test it with keyboard?
axisType = AxisType.Keyboard8426; <---- should I try this?

Worth trying! That should use the numpad for movement. I think WASD is an option as well. ManualCameraControl.unity should be set up properly, to give you an idea. Check the keyboard AxisControllers there.

I will look at ManualCameraControl

Yes, MRTK, uses the classic WASD +QE approach.....
In MRTK, the WASD + QE works great, as well at the mouse looking.
Would it be easy to pull out the "gaze" stuff so I could use it in a regular project? (non-AR project)
For HoloToolKit, it looked easy to do that....(except for the arrow key problem)

OK, I know what's wrong....

I don't care about using the keyboard for rotations....
But what is the correct settings for the keyboard?

For the XY and XZ ROTATION, I set the axis types to "none"

For the XY TRANSLATION I set the axis type to "Keyboard QE"

For the XY TRANSLATION I set the axis type to "Keyboard WASD"

To go up and/or down I use the "Q" and "E", so that's working now...
The "A" key goes left
The  "D" key goes right
But the "W" and "S" keys go up and down, instead of forward and backward?

Oops....I double checked...The "Q" and "E" go left and right too, not up and down....

OK....I think I got it working correctly now...
I had to correct the "Axis 0 Destination" and the "Axis 1 Destination"
for the XY and XZ translations,.

Looks like this has been resolved based on last comment in discussion


Make design systems insights board publicly accessible

The insights for the design system are currently tracked in a Google Sheets spreadsheet which is only accessible within the DTA.
External members of our community should be able to view these insights without requiring a DTA email account or having to log in to a third party service.

Blocked — The G Suite settings for the DTA do not allow sharing Data Studio reports outside of the DTA. Further discussion is needed to determine a suitable alternative.

Going to close this one unfortunately as we can't make our analytics publicly facing despite how awesome it would be.


inline mode doesn't work without selection

See the demo doesn't work:
https://www.froala.com/wysiwyg-editor/docs/examples/inline
But it will work when you select text like https://www.froala.com/wysiwyg-editor/docs/examples/always-visible

BTW I am on Chrome.

You should ask its author, not CDNJS.

oh sorry i am on the wrong github page.


IOS build : xcodebuild: error: Could not resolve package dependencies, app using Firebase

Steps to Reproduce

git clone git@github.com:user/myrepo.git.
cd myrepo && flutter create .

Expected results:
Flutter create . should work directly, but this error happens on every project when i use firebase.
This is quiet anoying when using CI/CD platform because to fix it you have to add a script to modify xcode settings.
The steps to fix it locally are:
open ios/Runner.xcodeproj , go to project settings and in advance select Xcode default build location.
Actual results:
flutter create .

Oops; flutter has exited unexpectedly: "ProcessException: Process exited abnormally:
Command line invocation:
    /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -list

xcodebuild: error: Could not resolve package dependencies:
  Packages are not supported when using legacy build locations, but the current project has them enabled.
  Command: xcrun xcodebuild -list".
A crash report has been written to /Users/arnauddelubac/Repository/Flutter/Apps/behero/tmp/hero/flutter_01.log.
This crash may already be reported. Check GitHub for similar crashes.
https://github.com/flutter/flutter/issues?q=is%3Aissue+ProcessException%3A+Process+exited+abnormally%3A%0ACommand+line+invocation%3A%0A++++%2FApplications%2FXcode.app%2FContents%2FDeveloper%2Fusr%2Fbin%2Fxcodebuild+-list%0A%0A%0Axcodebuild%3A+error%3A+Could+not+resolve+package+dependencies%3A%0A++Packages+are+not+supported+when+using+legacy+build+locations%2C+but+the+current+project+has+them+enabled.%0A++Command%3A+xcrun+xcodebuild+-list

To report your crash to the Flutter team, first read the guide to filing a bug.
https://flutter.dev/docs/resources/bug-reports

Create a new GitHub issue by pasting this link into your browser and completing the issue template. Thank you!
https://git.io/Jt5Ms

Flutter doctor -v

[✓] Flutter (Channel beta, 1.26.0-17.3.pre, on Mac OS X 10.15.7 19H114 darwin-x64, locale en-ES)
    • Flutter version 1.26.0-17.3.pre at /Users/arnauddelubac/Development/flutter
    • Framework revision 4b50ca7f7f (3 weeks ago), 2021-02-04 19:44:27 -0800
    • Engine revision 2c527d6c7e
    • Dart version 2.12.0 (build 2.12.0-259.8.beta)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/arnauddelubac/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    • CocoaPods version 1.10.1

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 51.0.1
    • Dart plugin version 193.7547
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.53.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.19.0

[✓] Connected device (1 available)
    • Arnaud’s iPhone (mobile) • 00008030-0005399A3EDB802E • ios • iOS 14.4

• No issues found!

I am just guessing firebase plugin is the one that make this happen because it's a common point between my projects, but i'll give a shot with the firebase github repo

Hi @arnaudelub
To better address, the issue Can you please provide a minimal complete reproducible code sample without using third-party packages
Thank you

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


restarting nats streaming server client connections dont recover

On a fresh install when things are working fine we can see 7 clients and 12 channels(subscriptions)

After we restart the nats-streaming-server service these counts drop and some channels and client connections are unable to recover.

I added a connectionListener on all streaming connections to debug further, looking at the debug logs it looks like we get a disconnect -> connect -> resubscribed events in order when i restart the nats streaming server.

Observing the connection events being fired on a nats streaming server restart it looks like all client connections and subscriptions have recovered successfully but that is not the case as we have seen from the nats streaming server metrics and also grafana metrics.
I am using nats java stan library
https://github.com/nats-io/stan.java
Does anyone know why my clients and subscriptions never come back even though the connection events say that everything is connected and resubscribed ?

Seems to be the same as #118

Seems to be the same as #118


Batched Stream Consumer contains KafkaNull objects inside a List

Description
I am using version 3.2.3 of Spring Cloud Stream. I have created a batch consumer for a Kafka topic. The following Java code describes my consumer.
public Consumer<Message<List<Car>>> processCarStream() {
    return message -> {
      final List<Car> payload = message.getPayload();
      // ...
    };
  }

When a message with null payload is received, I get a KafkaNull object inside the payload list. As per my understanding, we should have never got a KafkaNull inside the payload List.
Is this a bug with Spring Cloud Stream?
To Reproduce
Steps to reproduce the behavior:

Create a batch consumer using spring cloud stream.
Send a single kafka message with null payload.
See KafkaNull objects in the payload list.

Version of the framework
Spring Cloud Stream : 3.2.3
Expected behavior
We should receive Nulls instead of KafkaNulls.

@rishabh-agarwal792 3.2.3 is an older version that is out of regular OSS support. See the support timeline here.
We tried your issue with the latest version (4.1.x), and it works as expected. In batch mode, it correctly provides null elements for KafkaNull in the collection received on the consumer side. Similarly, it works for the type signature of Consumer<List<Car>>. Please try to upgrade to a later GA version and see if that takes care of the issue.


[FancyZones] Improve zone selection

Summary of the Pull Request
Some users like to have their zones overlap, sometimes, it was impossible to drop a window into a zone if it's covered by other, smaller zones. This PR should hopefully fulfill these users' needs. For the discussion, see issue #1167
What is include in the PR:
A modification of a single function. With this change, if there are multiple overlapping zones covering the point above which the user is hovering, one of the zones will be selected based on the position inside the overlapped area, allowing the user to drop the window into the desired zone.
How does someone test / validate:
Check the discussion in #1167. Also, make sure there are no changes in behavior if zones don't overlap, e.g. we can still select multiple non-overlapping zones by hovering between them.
One unit test is failing but I will add a commit to this PR to fix it.
Quality Checklist

[x] Linked issue: #1167
[x] Communication: I've discussed this with core contributors in the issue.
[ ] Tests: Added/updated and all pass (see above)
[ ] Installer: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Docs: Added/ updated
[ ] Binaries: Any new files are added to WXS / YML

[x] No new binaries
[ ] YML for signing for new binaries
[ ] WXS for installer for new binaries

Contributor License Agreement (CLA)
A CLA must be signed. If not, go over here and sign the CLA.

I implemented three different algorithms and added a zone config option, so we can set the algorithm on a per-ZoneSet basis.


[Feature] Via the application controller to write workflow-records instead of vela-apiserver

For some main reasons

make the vela apiserver stateless
make the vela apiserver deploy in multiple clusters
make workflow recording better performance

/cc @FogDong

APIserver and controller are decoupled, we don't have a resource called workflow record in controller. Its status is from application revision and application.

@oeular Why do you rely on the workflow record generated from vela-apiserver?
AFAIK, we don't use the records, we use the application revision. \cc @FogDong

@wonderflow  On velaUX, the workflow-record stored in configmap is used to store the workflow configuration and vela apiserver update it periodically. So is it suitable to let vela-core update or not ?

@wonderflow  On velaUX, the workflow-record stored in configmap is used to store the workflow configuration and vela apiserver update it periodically. So is it suitable to let vela-core update or not ?

Application revision also stores the config of workflow. All the source data of workflow record in VelauUX is from Application and its revision, you can checkout the code here: https://github.com/kubevela/kubevela/blob/master/pkg/apiserver/domain/service/workflow.go#L325


Fix minio icon upload with Docker approach

The minio:9000 guest isn't usually available from the Docker host under that name, but instead binds to localhost with the given port. This allows the webserver to connect to minio directly inside the Docker network, and also allows the host to connect to the minio instance from the UI.

Coverage 😤


[MediaBundle] Single and Multiple File Delete does not work

By @pjeroen from https://github.com/sulu-cmf/SuluMediaBundle/issues/73
Deleting a single file or mutliple files does not work. After confirming the warning dialog the files are still in the collection.

The UI could definitely be a bit better (showing some loader while files are deleted), but in general it works.


ENHANCEMENT: Decouple content processing from UI

Right now, if I load a bunch of material in, specifically long running tasks like mp3, mp4 or YouTube videos, the Web UI hangs.

Being able to scale out the 'workers' separately from the web-ui in a queue / scale out type system would be great. The queue is sending back a processing notification to the web-ui, and someone could continue to load resources in, and then they take a long to process as they take, but the UI is still available.
Does this make sense? Let me know if I am talking crazy.

Yes, I also noticed that issue when using the YouTube loader.
Anyway ;) I already separated the process on the v1.0.0 branch, as seen here https://github.com/n4ze3m/dialoqbase/blob/5b917a42cee2c647a1ce47fef1b874b16ea1481b/server/src/plugins/bull.ts#L22
This is based on the Bull Queues docs https://github.com/OptimalBits/bull#separate-processes

Awesome sir. You are already ahead of it. Thank you!


MINOR: Reduce memory allocation in ClientTelemetryReporter.java

ClientTelemetryReporter.timeToNextUpdate is called really often when sending a lot of data to Kafka servers. This is due to its logging. It tries to log the current state by formatting a string which generates a lot of char[] underneath.
This change will make it such that it will not generate string if the tracing is disabled.
Committer Checklist (excluded from commit message)

[X] Verify design and implementation
[X] Verify test coverage and CI build status
[X] Verify documentation (including upgrade notes)

@testn could you please fix the checkstyle failures which is causing the build to fail. https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka-pr/detail/PR-15402/2/pipeline

Add the file to the suppression list instead.

Nice! Small but very helpful change.
Out of curiosity, do you happen to have any ideas to detect such performance-inefficiencies automatically in future?

Currently, kafka is not really optimized yet. There are too many areas of improvements we can achieve especially from the memory usage perspective.

The build is still failing though @testn please check.

@divijvaidya  seem like the build is orange!

The test failures are unrelated to this change.
@testn You can see the test failures in the orange build by clicking on the arrow on top right. We have a flaky test suite but if a test is failing consistently, it usually is caused by the change in the PR. In this case, things look ok.

@testn congratulations on your first contribution to Apache Kafka! Hopefully first of many more to come.