Fix post-flatterning textures

This change updates the textures to use the 1.19.2 release. I've tested this on a number of versions, including 1.8.9, 1.12.2, 1.13.2, and 1.16.5. This covers pre and post flattening.
The largest change is the rework of the define_blocks macro. Rather than including data, offset, and offsets as a method of resolving the block ID, I've changed it to just store information about a block with different states, and then have a separate mapping for the IDs at different versions. The benefit of this is we can generate both the define_blocks block, and the mappings from information in https://github.com/PrismarineJS/minecraft-data. I've included a tool called generate-blocks that will generate those new structures.
For all post-flattening versions, this mapping is a const array of each block state in order. This will add ~1.4MiB to the compiled size, but will allow for very fast lookups from IDs. For the pre-flattening versions, I instead made a match block since it needs to do a lookup on both block ID and blockstate.
The pre-flattening file (blocks/src/versions/legacy.rs) was the only mapping file that can't currently be automatically updated. I generated the initial version from minecraft-data, but then needed to make manual changes to get it to work correctly. I've done lots of testing on 1.8.9 and 1.12.2 to try to catch any issues. While doing this, I found a few bugs in the original code, particularly around update_state that are now fixed.
After looking into the update_state structure, it seems like it is only required for pre-flattening versions, since post-flattening versions just send multiple block updates in those cases. A few cases I tested for this were top half of doors, chests/double chests, stairs, pumpkin stems, and redstone. Pre 1.13, some of these states aren't sent by the server, but are intended to be calculated on the client side. After 1.12, these states are calculated on the server side. Since it's no longer required in 1.13+, I've disabled calls to update_state on those versions.

@terrarier2111 I'm not sure how to fix the build issue. It seems like it's related to #255.

@terrarier2111 I'm not sure how to fix the build issue. It seems like it's related to #255.

I'll look into this in the upcoming days.

So this should now be mergable, right?


weird problem caused by save modifier_id

I had a problem that caused all my older records to get "modified" by the same user regardless of the current_user.  After looking around at why only older records had this behavior and new records were recording the correct modifier I discovered that the old records all had a saved "modifier_id" on the root document itself (not the history tracks, those should have it) and the new ones had nil.
That seemed to fix it.  Should there be a modifier_id?  I'm assuming it's not suppose to have a permanent value on the root document itself (just the history tracks)?

Closing because this is old and doesn't have a repro. Please reopen if you can reproduce.


Update check_springboot_actuator.py

Fixes to make sprinboot nagios plugin actually return data

Can you please give an example of your health status json? It looks like your changes break compatibility with default springboot applications.


Revert the fix using DISTINCT in order to overcome data corruption

This PR reverts https://github.com/symphonycms/symphony-2/commit/58bc57f2a4153ce0d7ad0e47406ab4a9e6b60746 and the related commit 3b30f8e. It keeps (resp. re-adds) some formatting improvements that were contained in the first (main) commit.

Closing in favor of  #2676 and #2677


Is it possible to add Components as an optional value to the Test Execution ticket?

I would like to request if Component field could be added as an additional option. As I am working on a project that has this field configured as a requirement when creating new test execution, and currently the api is returning 400 bad request due to this field being ignored.

I will close this because it is related to #62


Errno: EPIPE when trying to push

When trying to do an initial push of a module, I'm getting Errno::EPIPE: Broken pipe
Uploading to Puppet Forge jaxxstorm/cron
rake aborted!
Errno::EPIPE: Broken pipe
/Users/Lee/github/puppet-cron/vendor/bundle/ruby/2.3.0/gems/rest-client-1.8.0/lib/restclient/request.rb:270:in `net_http_do_request'
/Users/Lee/github/puppet-cron/vendor/bundle/ruby/2.3.0/gems/rest-client-1.8.0/lib/restclient/request.rb:418:in `block in transmit'
/Users/Lee/github/puppet-cron/vendor/bundle/ruby/2.3.0/gems/rest-client-1.8.0/lib/restclient/request.rb:413:in `transmit'
/Users/Lee/github/puppet-cron/vendor/bundle/ruby/2.3.0/gems/rest-client-1.8.0/lib/restclient/request.rb:176:in `execute'
/Users/Lee/github/puppet-cron/vendor/bundle/ruby/2.3.0/gems/rest-client-1.8.0/lib/restclient/request.rb:41:in `execute'
/Users/Lee/github/puppet-cron/vendor/bundle/ruby/2.3.0/gems/rest-client-1.8.0/lib/restclient.rb:69:in `post'
/Users/Lee/github/puppet-cron/vendor/bundle/ruby/2.3.0/gems/puppet-blacksmith-3.4.0/lib/puppet_blacksmith/forge.rb:56:in `push!'
/Users/Lee/github/puppet-cron/vendor/bundle/ruby/2.3.0/gems/puppet-blacksmith-3.4.0/lib/puppet_blacksmith/rake_tasks.rb:118:in `block (2 levels) in define'
/Users/Lee/.rvm/gems/ruby-2.3.1/gems/bundler-1.12.5/lib/bundler/cli/exec.rb:63:in `load'
/Users/Lee/.rvm/gems/ruby-2.3.1/gems/bundler-1.12.5/lib/bundler/cli/exec.rb:63:in `kernel_load'
/Users/Lee/.rvm/gems/ruby-2.3.1/gems/bundler-1.12.5/lib/bundler/cli/exec.rb:24:in `run'
/Users/Lee/.rvm/gems/ruby-2.3.1/gems/bundler-1.12.5/lib/bundler/cli.rb:304:in `exec'
/Users/Lee/.rvm/gems/ruby-2.3.1/gems/bundler-1.12.5/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/Users/Lee/.rvm/gems/ruby-2.3.1/gems/bundler-1.12.5/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
/Users/Lee/.rvm/gems/ruby-2.3.1/gems/bundler-1.12.5/lib/bundler/vendor/thor/lib/thor.rb:359:in `dispatch'
/Users/Lee/.rvm/gems/ruby-2.3.1/gems/bundler-1.12.5/lib/bundler/vendor/thor/lib/thor/base.rb:440:in `start'
/Users/Lee/.rvm/gems/ruby-2.3.1/gems/bundler-1.12.5/lib/bundler/cli.rb:11:in `start'
/Users/Lee/.rvm/gems/ruby-2.3.1/gems/bundler-1.12.5/exe/bundle:27:in `block in <top (required)>'
/Users/Lee/.rvm/gems/ruby-2.3.1/gems/bundler-1.12.5/lib/bundler/friendly_errors.rb:98:in `with_friendly_errors'
/Users/Lee/.rvm/gems/ruby-2.3.1/gems/bundler-1.12.5/exe/bundle:19:in `<top (required)>'
/Users/Lee/.rvm/gems/ruby-2.3.1/bin/bundle:23:in `load'
/Users/Lee/.rvm/gems/ruby-2.3.1/bin/bundle:23:in `<main>'
/Users/Lee/.rvm/gems/ruby-2.3.1/bin/ruby_executable_hooks:15:in `eval'
/Users/Lee/.rvm/gems/ruby-2.3.1/bin/ruby_executable_hooks:15:in `<main>'
Tasks: TOP => module:push
(See full trace by running task with --trace)

Running ruby 2.3.1 on OS X if that helps

It looks like the reason for this is that the package that's being built is including the vendor directory, which is in my .gitignore and creating a very large (~40mb) package.
Is there something which might be causing blacksmith to include the vendor path even though it's in my .gitignore ?

For those that come across this, it's kinda silly.
Your gitignore must have a slash after the dir name.
So vendor won't work
But vendor/ will.

@jaxxstorm does git ignore the folder and blacksmith not?

@rski see last comment, was a silly typo

Yes, I see, but i think this is still an issue. Blacksmith should ignore the same things that git does.  vendor works for git so why not for blacksmith?
Also the fact that a typo causes a completely irrelevant error like Errno::EPIPE: Broken pipe should probably be addressed imo.

The broken pipe error was because of the size of the resulting module, which I didn't immediately notice. It should probably catch the error from the API better about the size of the uploaded module? I'll reopen and let someone else triage


Crashes under Wayland in Linux

Trying to run the downgrader under wayland leads to the following error:
curl: try 'curl --help' for more information
xdg_toplevel#35: error 2: minimum width can't be bigger than the maximum width
The Wayland connection experienced a fatal error: Protocol error

Work around is to force X11/XWayland by setting QT_QPA_PLATFORM=xcb.

The workaround Athemis posted did not work for me. However, running the downgrader using this command does work for me:
env WAYLAND_DISPLAY= ./FOLON-Downgrader

My situation required this on arch
create python venv
python -m venv path/to/venv
source venv/bin/activate
install pip PyQt5
install tk system package from arch repo
To run:
env WAYLAND_DISPLAY= python3 ./FOLON-Downgrader.py

Could one of you try with the following command?
git clone https://github.com/Fallout-London/FOLON-FO4Downgrader.git && cd FOLON-FO4Downgrader && chmod +x && ./Run.sh

Fixed in with https://github.com/Fallout-London/FOLON-FO4Downgrader/commit/bb85a66a43473554eebf9c9b715d1e290918ba40

Fixed in with bb85a66

Just gave it a try and got this twice when at the download section.

That is a known error on the main branch, will be fixed when BackendSwitch get's merged


pdf query not catching some text in page

I am using the following code
tax = pdf.pq('LTTextLineHorizontal:in_bbox("%s, %s, %s, %s")' % (
col['tax']['start'], line, col['tax']['end'], line+10)).text()
where i am expecting to catch text something like '8 G1' or '32 G1'
here it catches value '32 G1' but not '8 G1'
actually any single digit value is not caught here.
'589 TKTT<PHONE_NUMBER> 14APR17 FVVV D CA 4,440 3,425 8 G1 450 YQ
75 YR 3,386 1.01 39 0.00'
above what my line in pdf line is.
it is catching values at that posssition before and after but not here and in situations like this one.
please help with it
Mayuresh A

Hi! I can't really debug this for you. My general suggestion is to try pdf.tree.write("tree.xml", pretty_print=True) and see why the element you're looking for doesn't match your selector.


Update mdbx to 0.11.8

Update mdbx to version 0.11.8.

I think is probably better to update our mirror libmdbx instead of directly point to gitflic.ru

I've updated our mirror BUT latest release is 0.12 ... is it ok for you ?

I've updated our mirror BUT latest release is 0.12 ... is it ok for you ?

0.12 seems to be a placeholder. https://gitflic.ru/project/erthink/libmdbx/tag says "v0.12.0 - Not a release but preparation for changing feature set and API."


Image list is empty in gallery

I have uploaded a few pictures in the gallery using the admin plugin.
Image was successfully uploaded and saved.
However when I go to the Images tab to create an item, the list is somehow empty.

Any idea?

If you refresh or save the page, are the images shown after that?

Nope. Nothing on the drop down list. I've used different browser & also private browsing mode.

I'm not sure if it is a problem from filepicker field or from us. Grav's filepicker field doesn't consider ".JPG" extension as ".jpg". You have 2 solutions:

Rename your images to *.jpg
Edit user/themes/big-picture/blueprints/modular/gallery.yaml and add ".JPG" to the list of header.images, the result looks like this:

            header.images:
              name: images
              type: list
              style: vertical
              label: Images
              fields:
                .title:
                  type: text
                  label: Title
                  help: Image's title.
                .full:
                  type: filepicker
                  folder: '@self'
                  preview_images: true
                  accept:
                    - .png
                    - .jpg
                    - .JPG
                  label: Full Image
                  help: Full image's filename.

I will need to contact Grav developer for their comments.

Ah... I renamed the file extension to small caps and re-uploaded it and it appears.


Update 027-fireworks.md

Community Contribution
Link to live project, video, or image:
https://media.giphy.com/media/XxSadBn6UaU0bWqqTV/giphy.gif

Sharing

[x ] I would be happy to have my project shared on The Coding Train's social media!

Instagram:
Twitter:

This is great!


How to format Yaml-file for an array of AD-objects

I'm trying to understand how to format a Yaml-document for a DomainController when using AdGroup and ADOrganizationalUnit from ActiveDirectoryDSC (6.6.0) and I want several Groups and several OUs.
The goal is to build several complete Labs with their own domain, apps, OUs and AD-groups. For example for OUs I would like something like this:

Domain Operation
Domain Operation/Groups
Domain Operation/Services
Domain Operation/Users
Customers//Users
Customers//Users

I tried something like this:
ADOrganizationalUnit:

Name: Domain Operation
Path:
Name: Groups
Path:

But this results in some error of not able to convert array to hashtable.

DSC resources cannot be used directly in the DscWorkshop concept. Instead, configurations (DSC composite resources) serve as a kind of translation between the Yaml configuration data and the DSC resources. These configurations are provided by the CommonTasks module.
Please have a look at the test data for getting an idea how to use the configrations:

AddsDomainPrincipals.yml
AddsOrgUnitsAndGroups.yml

This was definitely a helpful answer!
I will look into it first thing in the morning, but I am quite confident this will bring me in the right direction.
Thank you for your time, and a very fast and precise response.

BTW, if the configurations don't do what you need or are missing entirely, you can write (and share) your own ones. We have covered this in 2.5 - Create a custom Configuration (DSC Composite Resource).


Model attribute type:'text' size validation

Waterline version: 0.11.9
Node version: 6.9.4
NPM version: 3.10.10
Operating system: Ubuntu 16.04

Hi,
I'm using sails v0.12.11 on a project, and I came across this problem.
When the value of a model attribute with type: 'text' excedes the database's data type size limit, an E_UNKNOWN error is generated.
I was unsure whether the size of the underlying database type was automatically taken into account, since 'text', 'mediumtext' and 'longtext' are all listed in http://sailsjs.com/documentation/concepts/models-and-orm/attributes, but it seems it's not.
Are these three types any different from waterline's point of view?
And specifying the size of the attribute manually seems to make no difference either:
attributes: {
    description: {
      type: 'text',
      size: 10000 // characters? bytes?
    }
}

For example, for mysql, this limit is 65535 bytes. If that limit is exceded, that error is not handled and results in an E_UNKNOWN error, which in turn is interpreted as a Server Error, instead of a Bad Request.
I guess I could do something like this myself:
MyModel.create(data).exec(function (err, result) {
  if (err && err.originalError && err.originalError.code === 'ER_DATA_TOO_LONG') {
    if (err.originalError.message) {
      let matches = err.originalError.message.match(/Data too long for column '(.*?)'/);

      if (matches && matches.length > 1) {
        let column = matches[1];

        // now let's figure out what model attribute is associated with that column,
        // and then how the request payload is related to that attribute, if necessary.

        // finally, send a "Bad Request" response to the user specifying that
        // said attribute is too long...
      }
    }
  }
});

But that's really smelly error handling, having to manually parse the originalError.message is ugly, and the fact that originalError.message is not even an Enumerable object property makes it even worse. Are we, as waterline/sailsjs users even supposed to be using originalError.message?
Thanks!
Btw, I'm sorry if this is the wrong project to report this issue to, I wasn't sure whether the sails-mysql adapter, waterline or sailsjs should take care of this.

Hey @fgallardograzio the Waterline auto-migrations system is pretty rudimentary. It doesn't really understand all the various independent SQL database types and such. When you need specific database types we suggest you do manual migrations using something like knex.
In Waterline 0.13 which will be included in Sails v1 we made this a bit more flexible with a columnType attribute but still recommend the manual migration route when building anything that will go into production.

@particlebanana Thanks for your reply. Unfortunately that's not what I meant.
I was not referring to migrations. I'm using db-migrate for that. The database structure is already in place, I already have a table with a TEXT column.
I may have not expressed myself clearly.
What I meant is how to approach size validation when storing a model with an attribute with type: 'text'.
I would've thought that Sails/Waterline (plus sails-mysql in my case) would take care of that, just like they take care of other validations that can't be handled programmatically before querying the database, such as unique constraints.
If the framework doesn't already take care of that, should it? I'd be willing to work on this, if you point me in the right direction :)
If it it won't, then am I supposed to handle that myself by checking the size of the attribute before calling Model.create(), tightly coupling my code with the underlying database type definitions?
That would go against the point of using an ORM such as Waterline that would allow my code to be database agnostic.
Or should I call Model.create() anyways, check if it returns an E_UNKNOWN error, manually parse the originalError.message or something, check if contains "ER_DATA_TOO_LONG" with the name of a column. Check what model attribute that column is associated to, etc, etc. Similarly to the code I posted in my original message.
I think both solutions are quite bad. Is there an alternative I'm not thinking of?
Thanks.


Make parameter binding API public

This allows others to build proxies without using internal code.
Fixes #14554 #15252
Internal code is still being used for conventions.

/azp run


Android 11+

Will you implement DocumentFile and scoped storage except old File way?

OK.
It is also on my wish list.

I have changed the target api level to 30(Android 11) in the hxftpserver application and the ftpserver library. The existing code is working as expected on my testing device, which is running Android 12. You can try the most recent commit of hxftpserver application: https://github.com/hxcan/hxftpserver/tree/a405014731a55d8324ec49acce08d4304731444b
And I'm doing some research and going to abstract the logic based on the DocumentFile API instead of the File API. What is your actual problem about this issue?
What do you mean by this ?

The app is not working on Android 11+...

Please give me some more details about your use case, and some screen shots / screen records.

As I do not know the details of your problem, I have to do it according to my own plan. And now my own requirement has been fulfilled.
There are two changes which might help solve your problem, whatever it is:

The ftpserver library will notify the calling application of an event "NEED_EXTERNAL_STORAGE_MANAGER_PERMISSION", when it needs the permission of "Managing all files" to do its job. By default, the ftpserver library does its work based on the File api, which is more effecient than the Storage Access Framework. And it needs this permission to work properly on Android 11 and high versions. https://github.com/hxcan/ftpserver/commit/6d3f82f0279a98b0c474c55db69a5e97889a9372#diff-3d69424eee52bf60d527f532cded020ca311e57fc0322a97ad52a2ab74af6df5R11 . The application is supposed to show some kind of prompt and guide the user to the system settings page of granting "Managing all files" permission. This is demonstrated by the hxftpserver application: https://github.com/hxcan/hxftpserver/commit/de4f5291180f1ab6f1ed49d353c45d0567cce3f7#diff-34b9d8d14418eddcfcd2764fa5f116c9dbe40881e1d755a489a3961d14a49f35R41
The ftpserver library provides an api of mounting a Uri to a virtual path.  https://github.com/hxcan/ftpserver/commit/5484b8b3232cdf3f50d97093f83d8f213d049774#diff-b35f6a0ef28c102a1e8f3eeff2f397bac3c151480e67b4ec775f07c5877a4101R320  The application can guide the user to select a directory on the external storage with the help of the Storage Access Framework, and then mount that returned Uri to a virtual path of the ftpserver. With this api, the calling application can even overwrite the root directory of the ftpserver. This is compatible with the Scoped Storage model provided by Android, although it's a little slower than the raw File mode. It is demonstrated by the hxftpserver application: https://github.com/hxcan/hxftpserver/commit/de4f5291180f1ab6f1ed49d353c45d0567cce3f7#diff-3841e77b4c74774f7ccc9816bece53cc041cf08f1f50e5fbc7682b554ce143a1R105

You can try these features with the latest precomiled version of hxftpserver:
https://stupidbeauty.com/ArticleImages/1907/HxFtpServer.4623.2023.4.4.e.apk
I'm going to merge this branch and close this issue.
Please open it again and provide some details about your problem if your it was still not solved.


Projects fail to package with plugin enabled on UE5-Main

While the plugin seems to be functioning flawlessly in Standalone, when packaging, the error encountered is:
SLoadingWidget.cpp(121): error C2065: 'Visibility': undeclared identifier
It then Skips the remaining 2 steps for compiling the plugin when packaging. The logs say the project packages, but in truth it fails (nothing in the output directory).
Removed intermediate & saved folders and repackaged; no success there either.

Hi, I'll support UE5 when it's officially released, so please don't use this plugin for production in UE5 yet.

Project compiles fine with plugin in UE5 for me. @entergeist @truong-bui


Recipe for conda build #667

Added functionality to generate conda packages in addition to the wheel files as part of the Jenkins build process. This still does not auto deploy the conda packages to h2oai conda channel, however that can be easily implemented by providing a promote option on our internal conda server.
Issue #667

@mdymczyk  and @pseudotensor ,
X86_64 build via jenkins for all cuda versions (8,9,9.2) is working for this PR.
For ppc64le we have 2 issues

Multiple dependencies for ppc64le are not available in the conda environment. It will take considerable time to get all possible packages available.
To get the x86_64 packages working i had to update some dependencies in requirements_build.txt, namely llvmlite from 0.20.0 to 0.21.0. However that version does not seem to be compatible with the LLVM version that is downloaded from artifacts.h2o.ai as part of the docker build step. So pip install of requirements_build.txt is failing with the below error

/opt/h2oai/h2o4gpu/python/bin/python /tmp/pip-build-pjuilgvd/llvmlite/ffi/build.py
17:49:51   LLVM version... 4.0.1
17:49:51
17:49:51   Traceback (most recent call last):
17:49:51     File "/tmp/pip-build-pjuilgvd/llvmlite/ffi/build.py", line 141, in <module>
17:49:51       main()
17:49:51     File "/tmp/pip-build-pjuilgvd/llvmlite/ffi/build.py", line 131, in main
17:49:51       main_posix('linux', '.so')
17:49:51     File "/tmp/pip-build-pjuilgvd/llvmlite/ffi/build.py", line 105, in main_posix
17:49:51       raise RuntimeError(msg)
17:49:51   RuntimeError: Building llvmlite requires LLVM 5.0.x. Be sure to set LLVM_CONFIG to the right executable path.
17:49:51   Read the documentation at http://llvmlite.pydata.org/ for more information about building llvmlite.
17:49:51
17:49:51   error: command '/opt/h2oai/h2o4gpu/python/bin/python' failed with exit status 1
17:49:51
17:49:51   ----------------------------------------
17:49:51   Failed building wheel for llvmlite

What are your thoughts on approach this? Can we merge this PR for x86_64 build ?

@hemenkapadia please don't merge anything that fails (either ppc64le or X86_64).
If it's too much work and we don't need it immediately (or at all) then I'd say we should just skip it during ppc64le build and only build it for x86_64.

However that version does not seem to be compatible with the LLVM version that is downloaded from artifacts.h2o.ai as part of the docker build step

Can we try removing that LLVM stuff from the docker and see if it still works?

Ya, definitely don't merge if not green.  But as we discussed, I don't see why llvm is needed, so remove it  unless I'm confused.

All checks passed now. We discussed on PR#678 that llvm is needed for llvmlite which is a dependency for numba. Since all checks are passing if you are ok please approve this PR so that I can merge to dev


signal 0x13 when bootstrapping

The current version of master can't bootstrap on my machine, but thats not this bug, its the "foreign thread received signal: 0x13" message after accidentally hitting ^Z.
resource:basis/stack-checker/dependencies/dependencies.factor

81:         [ [ class1>> valid-classoid? ] [ class2>> valid-classoid? ] bi and ]
                                        ^
No word named “valid-classoid?” found in current vocabulary search path

The following restarts are available:

:1      Defer word in current vocabulary
:2      Load resource:basis/stack-checker/dependencies/dependencies.factor again
:3      Load resource:basis/stack-checker/backend/backend.factor again
4 :res  Load resource:basis/stack-checker/stack-checker.factor again
5 :res  Load resource:basis/combinators/smart/smart.factor again
6 :res  Load resource:basis/compiler/compiler.factor again
7 :res  Load resource:basis/bootstrap/compiler/compiler.factor again
IN: scratchpad ^C^C^C^C^C^Z
[1]+  Stopped                 ./build-support/factor.sh update
$
$
^Cfatal_error: Foreign thread received signal: 0x13

[1]+  Terminated: 15          ./build-support/factor.sh update

If ^C doesn't work, try ^. I made it so it doesn't install a handler for SIGQUIT so you can still kill factor if ^C leaves it wedged.

Can you maybe try to reproduce the ^C wedge under gdb and file a bug report for that? Use these gdb commands so it will pass the signal on to the process:
handle SIGINT pass
handle SIGINT nostop


Replace the webpack-stream dependency

With PR #11436 we became locked at a particular (older) version of the webpack-stream dependency, because of bugs in the latest versions; see https://github.com/mozilla/pdf.js/pull/11436#issuecomment-568430643 for details.
Looking at the GitHub-page for webpack-stream, it unfortunately seems that the project may be unmaintained/dead at this point given that the latest commit was in 2018.
Hence, rather than trying to update webpack-stream it's probably better to attempt to replace it completely instead (possibly with our own code if necessary) to ensure that we'll be able to e.g. update to Webpack 5 when it's released (which will likely be needed to properly support new ECMAScript features).

This dependency is now updated to the most recent version in #12397. However, given that's it's a very inactively maintained dependency I also think we should get rid of it. Moreover, we only seem to be using it in one place in the Gulpfile...

Now that we're using Webpack 5, the dependency got updated and there was more development on their GitHub page, do we still want to do this?

Now that we're using Webpack 5

Given that the Webpack upgrade itself wasn't actually blocked by the webpack-stream dependency, as I incorrectly assumed previously, I suppose this reduces the severity of this issue considerably.

the dependency got updated and there was more development on their GitHub page, do we still want to do this?

To me, this all depends on whether or not they'll try to re-introduce the broken caching mechanism (which originally forced us to pin the version number).

I guess we could make https://github.com/mozilla/pdf.js/blob/master/package.json#L61 use ^ instead of ~ now.

I suppose that could work, as long as we remember to check webpack-stream for any possible breakage when updating the npm packages (which I've been doing the last few times).
If you want to submit a PR with this change, and then simply close this issue, then please be my guest :-)


feat: implement tokens architecture

Note: Please transform - [ ] into - (NA) in the description when things are not applicable
Related issues

Description

Motivation & Context

Types of change

Bug fix (non-breaking which fixes an issue)
New feature (non-breaking change which adds functionality)
Refactoring (non-breaking change)
Breaking change (fix or feature that would change existing functionality)

Previews

Checklist

Contribution

[ ] I have read
the contributing guidelines

Accessibility

[ ] My change follows accessibility good practices

Design

[ ] My change respects the design guidelines of Orange Unified Design System

Development

[ ] My change follows
the developer guide
[ ] I have added unit tests to cover my changes (optional)

Documentation

[ ] My change introduces changes to the documentation and/or I have updated the documentation
accordingly

Checklist (for Core Team only)

[ ] Manually test (dark mode, RTL, landscape display, tablet)
[ ] Documentation has been updated if relevant
[ ] Code review
[ ] Design review
[ ] A11y review
[ ] Internal files have been updated if relevant (THIRD_PARTY, NOTICE)
[ ] changelog.md has been updated
respecting keep a changelog rules and referencing the
issue

Replaced by #52


Overlap and overflow detection

What:
Overlap and overflow detection

Why:

How:

Checklist:

[ x ] Documentation
[ x ] Tests
[ x ] Ready to be merged

Yes, but I'm always open to any feedback and obviously corrections.

I have updated the commit msg's now.

@all-contributors please add @satueveliina for code, doc and ideas


What's your question?


[HUDI-855] Run Auto Cleaner in parallel with ingestion

When auto-clean is enabled, Writer would automatically run the cleaner job asynchronously along with the write operation.

@vinothchandar : Ready for review.


Aether is not an eclipse project anymore

The Eclipse Aether is not an Eclipse project anymore for a longer time..
https://projects.eclipse.org/projects/technology.aether/reviews/termination-review
It has been migrated to https://maven.apache.org/resolver/

Thanks for your comment!
I was aware of that situation, but I had been using the Eclipse version for a while in personal projects without issues, so I though I would be a good starting point. However, it's true that for a public library I should use the up-to-date version.
Version 1.1.0 fixes the issue using Apache Maven Artifact Resolver instead of Eclipse Aether.


Can't install any extensions

VSCode Version: version 1.42
OS Version:Ubuntu 18.04

Steps to Reproduce:
1.Installed VSC as per https://linuxize.com/post/how-to-install-visual-studio-code-on-ubuntu-18-04/
2.Select Extension in activity bar
3. select any extension and install
Example result: Failed to install 'formulahendry.code-runner'.
4. does not matter what extension I try similar notification results

Does this issue occur when all extensions are disabled?: Yes/No

Please follow these steps

Help -> Toggle Developer Tools -> Network
Then check for any network failed requests while browsing and installing the extensions if found all requests fails then its probably a proxy or DNS issue at your end.
To confirm its a DNS issue check if you can access this page https://ms-python.gallerycdn.vsassets.io/extensions/ms-python/python/2019.8.29288/1565127378610/Microsoft.VisualStudio.Services.Icons.Default, if you cannot please try configuring your DNS like pointing to <IP_ADDRESS> as suggested here? https://<IP_ADDRESS>/dns/. Otherwise please contact your network administrator.
If it is not a network issue, please share the logs from the following locations

Help -> Toggle Developer Tools -> Console
View -> Command Pallette... -> Toggle Shared Process -> Console
View -> Open View… -> Log (Shared)
View -> Open View… -> Log (Window)


can you release a more specific manual or example for the simulation of decision and planning?

It is a little difficult to do simulations with 1.5, at least to people like me, who does not know too much about the docker, the ROS. will you just show us how to subscribe the perception and map info ,and how to output the planning or decision result in several examples or manuals?
Thank you!
-shan

You can do a rostopic echo <topic_name> to output the data received. You can do a rostopic list to show the available ros topics, including perception, planning, etc.

Closing for inactivity.


CNI logging issues

CNI logging works by sending logs over a UDS socket from the istio-cni binary up to the user-space install-cni container. There are a few issues here around logging levels and scopes.

https://github.com/istio/istio/blob/764e6688921e326bdaa530d5ef3a9ed5d87372f7/cni/pkg/plugin/plugin.go#L177 sets the scope as configured by logLevel in the configmap, which is Values.cni.logLevel. This only handles default scope. if we have other scopes, we cannot configure them. Either we should apply this to all scopes, or allow the standard parsing of scopes that log_output_level does
Daemonset doesn't allow setting the level at all: https://github.com/istio/istio/blob/ff3ccd19943796e58e9ac16db114a99dcaa8b4d6/manifests/charts/istio-cni/templates/daemonset.yaml#L76
Maybe not a bug, but something we should consider: https://github.com/istio/istio/blob/bf2adb0be5c057924a79d1a78a39ffb87aeb1175/cni/pkg/log/uds.go#L121 loses the original scope of the log. If we send scoped logs, we lose that info. Either we can lookup the original scope, or we should add a key to do the equivalent

(1) and (3) should be consider together.
For now, all logs from istio-cni binary' scope is default, there's why we see log.FindScope("default").SetOutputLevel(getLogLevel(conf.LogLevel)) ; uds-server will output them in cni scope.
2022-07-19T06:40:16.980423Z	info	cni	istio-cni cmdAdd with k8s args: {CommonArgs:{IgnoreUnknown:true} IP:<nil> K8S_POD_NAME:sleep-5887ccbb67-kjds5 K8S_POD_NAMESPACE:default K8S_POD_INFRA_CONTAINER_ID:0903460cebefc2d22d2d04b152031b4021450b4be4988f08d04d4fd2791198c0}
2022-07-19T06:40:16.980444Z	info	cni	============= Start iptables configuration for sleep-5887ccbb67-kjds5 =============
2022-07-19T06:40:16.980448Z	info	cni	Istio iptables environment:

so I prefer to keep the status quo unchanged.


Mute crashes Safari (SimpleUser)

Describe the bug
Muting outgoing media crashes the page in the latest version of Safari.
Logs
traceSip is enabled, but no error is logged. The last log is:
[Log] Fri Nov 26 2021 12:31:40 GMT+0100 (CET) | sip.SimpleUser | [user15@{server}] disabling media tracks... (demo-2.js, line 7697)

To Reproduce (if possible)
Steps to reproduce the behavior:

Clone the repository.
Build the demo applications.
Go to the demo-2 application in Safari 15.1.
Connect and register users and start a call.
Check the "Mute" checkbox in Safari.

Expected behavior
The outgoing media stream should be disabled, and the "Mute" checkbox should be checked.
Observed behavior
The page reloads and Safari shows the following error:
This web page was reloaded because a problem occurred.

Environment Information

FreeSWITCH 1.10.7
Safari 15.1

Additional context
The websocket server in the demo doesn't currently work with Safari 15.1 so I used a FreeSWITCH to do the testing. Everything works fine in Chrome.

Could not reproduce in Safari 15.6


Merge conceptual WebApi content

Currently, there is a migrated version in the web-api folder not shown and a raw version in api-reference/webapi shown.
Bring this content together in web-api and rename folder to webapi.
After PR is approved and merged, we need to update docfx.json to include this folder.

Cleanup done. Added folder to end of data-access toc. To make docfx happy, add the webapi folder and its images to the Json file.

Done


Ej/fix env vars

An attempt to begin addressing the env vars issue. In particular, moving the secrets back to secrets.
Also reducing the amount of repetition in the secrets.yaml file due to the multiple keys with the same value.

fixes #28

Looks good to me but I haven't had a chance to test.


feat: explicitly allow paradigm sizes

What's in this PR?
DRAFT because I think I over generalized the whole... sorting thing ¯\_(ツ)_/¯

added: MORPHODICT_PARADIGM_SIZE_ORDER setting for crkeng. A list where you list the paradigm sizes!
changed: ParadigmManager.sizes_of(paradigm_name) returns a list of the paradigms in a sorted order
added: some gross static-typing code!

Codecov Report

Merging #863 (ba58bdd) into main (0b16c65) will increase coverage by 0.07%.
The diff coverage is 91.83%.

@@            Coverage Diff             @@
##             main     #863      +/-   ##
==========================================
+ Coverage   81.67%   81.74%   +0.07%
==========================================
  Files         106      106
  Lines        4414     4454      +40
  Branches      650      653       +3
==========================================
+ Hits         3605     3641      +36
  Misses        685      685
- Partials      124      128       +4

Impacted Files
Coverage Δ

...eeDictionary/CreeDictionary/paradigm/generation.py
83.33% <71.42%> (-6.15%)
:arrow_down:

...Dictionary/CreeDictionary/paradigm/test_manager.py
97.18% <93.10%> (-2.82%)
:arrow_down:

.../CreeDictionary/CreeDictionary/paradigm/manager.py
82.95% <100.00%> (+2.69%)
:arrow_up:

.../search_quality/management/commands/featuredump.py
32.69% <0.00%> (ø)

...ranslate/management/commands/translatewordforms.py
73.17% <0.00%> (ø)

Continue to review full report at Codecov.

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


Improve assertion messages

One thing that was annoying me when writing unit tests is that assertion messages where not really usefull. When your tests expects 20 diagnostics and your diagnostic only reports 19 it would only tell you that the number of diagnostics didnt match but it would not tell you which diagnostic was missing. So I was debugging the unit tests and diffing the expected and the actual results in the auto window myself which is really annoying. This change changes the way assertion messages are generated. With this change the VerifyDiagnosticResults will diff the expected results and the actual results of the diagnostic and it will include the changes in the assertion message. This makes writing tests a lot easier.
One drawback with this is that if the severity, the message or any other property of the diagnostic is wrong it will not print the specific assertion message defined in AssertDiagnosticsMatch but it will instead report that one diagnostic is missing, and that one was reported that was not expected. But these mistakes are easy to figure out anyway and they are not really the ones you run into very often.

I see a lot of
if (...)
{
   Assert.True(false, ... );
}

constructions in the code. I'm not particularly fond of those and would personally rather see them wrapped up in one statement.

The last for statement in VerifyDiagnosticsResult() seems to imply that the actual diagnostics and the expected diagnostics should be matched in the same order. AppendMissmatchErrorText() does a full cross check to allow matchings in random order.
If the diagnostics should be matched in the same order, a more efficient implementation can be made.
The code outline below shows what I mean
// The code below assumes that both expectedDiagnostics and actualDiagnostics are arrays!
var indexActual = 0;
var indexExpected = 0;
var matches = new Dictionary<Diagnostic,Diagnostic>();

while ((indexActual < actualDiagnostics.Length) && (indexExpected < expectedDiagnostics.Length))
{
    if (DiagnosticMatches(expectedDiagnostics[indexExpected], actualDiagnostics[indexActual]))
    {
        matches.Add(expectedDiagnostics[indexExpected], actualDiagnostics[indexActual]);
        indexActual++;
        indexExpected++;
    }
    else
    {
        // detect if there are additional actual diagnostics
        // if there are no matches in the remaining actual diagnostics,
        // the expected diagnostic is skipped as unmatched.
        for (var i = indexActual + 1; i < actualDiagnostics.Length; i++)
        {
            if (DiagnosticMatches(expectedDiagnostics[indexExpected], actualDiagnostics[i]))
            {
                matches.Add(expectedDiagnostics[indexExpected], actualDiagnostics[i]);
                indexActual = i + 1;
                break;
            }
        }

        indexExpected++;
    }

    var unmatchedExpectedDiagnostics = expectDiagnostics.Except(matches.Keys);
    var unmatchedActualDiagnostics = actualDiagnostics.Except(matches.Values);

    // TODO: Report the mismatches.
}

Thanks for your feedback!
I adressed all of your feedback except the last one. You are right, that the cross search is not efficient (O(n^2)), but I think that the number of diagnostics we deal with in our tests is so small, that it does not really matter if we use an O(n) or O(n^2) algorithm and I think (maybe its just because I wrote it) that my version is easier to read.
The actual diagnostics array is ordered by the caller and the expected diagnostics array (should) be ordered by the test that uses it.

You are quick in processing feedback :+1:
The readability of your code is good, so I'm perfectly fine with leaving stuff as it is.

@pdelvo I'm reviewing this now, but for a quick consideration, how certain are you that this will not cause problems when we move to testing SA1027?

:exclamation: In addition to my comment in the diff, the current algorithm allows an item in actualResults to match multiple items in expectedResults (and vice versa). How certain are we that this behavior will not cause a problem?

The old and the new version will fail at the same condition. the difference is the way it formats the message for it. If you have a bigger test with a lot of diagnostics that should be created it can be really annoying to figure out which specific diagnostic that should be reported is reported, or which diagnostic is reported that shouldnt be. At least for me these two things are the main reason that a unit test I write fails. So this solution is optimized create an assertion message that helps you figuring out what is going wrong. The old one was better if maybe you expect one diagnostic, it is present, and you are expecting a different servity. But thats not really what happens a lot of times

The algorithm only allows an item in actualResults to match multiple in expectedResults and vice versa if both list have the same number of items in them. This last test is basicly the old test as a fall back if the new one did not detect a problem. This makes sure that the number of the same diagnostics in the lists match.

I don't think there is any interest in this PR any more. and the underlying code changed too much. Im closing this.


Build failure with rust nightly

rustc 1.2.0-nightly (2f5683913 2015-06-18)

This recent build failures comes from two sources:

We should use #![feature(arc_weak)] now.
scoped was deprecated.

The reason behind deprecation is old.
This post is a good reading on the problem.
The discussion still heated and I'm not sure they'll provide a replacement soon.

So, I'm going to replace all scoped usages with spawn.

+1 .. Thanks Vinícius

Previously, join couldn't fail, but outside of the scoped API, this scenario might happen.
I couldn't easily convert Err(Box<Any + Send + 'static>) to Err(std::io::Error), so I used unwrap for now. Possibly I'll refactor to use some adapter (e.g. Err(Error::new(Other, /* ... */)) or change BroadcastAcceptor::accept return type. These solutions touch public interface and I would need some time to make sure I don't break anything, but I was told you guys are in a hurry to getting this thing building for now, so I used unwrap.


Default profile for integrated terminal is not reliable immediately after starting (and after loading workspace)

VS Code Version: 1.56.1
OS Version: Windows 10 20H2

Steps to Reproduce:

Set "terminal.integrated.defaultProfile.windows": "Command Prompt",
Open integrated terminal => it's a command prompt
Close VSCode, leaving terminal open
Restart VSCode => terminal is Powershell Core

The same happens when the terminal shall be started via menu immediately after launching VSCode.
And it happens as well, as I open a folder or work space via MRZ list on "Gettings started" page if that folder or work space had an open terminal when accessed last.

Does this issue occur when all extensions are disabled?: Yes
It does not seem to happen (at least rather rarely) when an empty folder with extensions disabled is opened.
Looks very much like a race.

I just came here to talk about the same behavior, I performed the same steps and had the same findings.

This should be fixed in Insider's tomorrow via https://github.com/microsoft/vscode/pull/123729


Issue with GrpcClient.Create

When following the instructions, I get an error on GrpcClient.Create. "GrpcClient" name does not exist

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

ID: 1d298a6c-8ddc-dbc8-d219-0fa7138442c2
Version Independent ID: b96be346-958a-cfcd-d80a-c352d64223e8
Content: Create a .NET Core gRPC client and server in ASP.NET Core
Content Source: aspnetcore/tutorials/grpc/grpc-start.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @JunTaoLuo
Microsoft Alias: johluo

Installed NuGet package is Grpc.Net.Client 0.2.23-pre1.
In the sample folder  I see that Grpc.Net.Client 0.1.22-pre2 is used
( xx\AspNetCore.Docs-master\AspNetCore.Docs-master\aspnetcore\tutorials\grpc\grpc-start\sample\GrpcGreeterClient ).
When downgrading to that version, the issue is solved

Grpc.Net.Client is no longer a pre-release. The GrpcClient type still does not exist, and none of the documentation has been updated to remove that and replace it with whatever it is you're supposed to do now.

I have the same issue.
GreeterClient does not exist ?!
This line does not compile:
var client = new Greeter.GreeterClient(channel);

+1, I have the same issue.

GrpcClient.Create has been removed in the latest version of Grpc.Net.Client. Use the client constructor with GrpcChannel.

I don't think this issue should have been closed, as the tutorial still said to call GrpcClient.Create. Sent pull request to fix.


IndexError while running the NMT example

I am running the NMT example but with a different dataset. During inference, I get the following error with top_k > 1:
site-packages/graph4nlp_cu111-0.4.0-py3.9.egg/graph4nlp/pytorch/models/graph2seq.py", line 251, in translate
return self.encoder_decoder_beam_search(
File "/xxxxxx/lib/python3.9/site-packages/graph4nlp_cu111-0.4.0-py3.9.egg/graph4nlp/pytorch/models/graph2seq.py", line in encoder_decoder_beam_search
beam_results = generator.generate(batch_graph=batch_graph, oov_dict=oov_dict, topk=topk)
File "/xxxxxx/lib/python3.9/site-packages/graph4nlp_cu111-0.4.0-py3.9.egg/graph4nlp/pytorch/modules/prediction/generation/decoder_strategy.py", line 150, in gener        ate
return self._beam_search(**params)
File "/xxxxxx/lib/python3.9/site-packages/graph4nlp_cu111-0.4.0-py3.9.egg/graph4nlp/pytorch/modules/prediction/generation/decoder_strategy.py", line 206, in _beam        _search
graph_node_mask[batch_idx, :].unsqueeze(0).expand(beam_size, -1).contiguous()
IndexError: too many indices for tensor of dimension 1

The problem is it does not happen for all datasets. But it is evident there is a subtle bug in the beam search. Can anyone please help?

This issue will be closed. Feel free to reopen it if needed.


[Rust][Runtime] Add basic object system support.

Add initial support for the new Object system to the Rust bindings, including a few example nodes. This enables the construction of new types of things from Rust such as the Relay AST, with TIR and the pass system to come in future passes. # #

Closing in favor of finer grained PRs.


HBASE-25091 Move LogComparator from ReplicationSource to AbstractFSWA…

…LProvider#.WALsStartTimeComparator
Give the comparator a more descriptive name, a better location,
and make it work even when passed hbase:meta WAL files.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m 13s
Docker mode activated.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 45s
the patch passed

+1 :green_heart:
compile
1m 15s
the patch passed

+1 :green_heart:
javac
1m 15s
the patch passed

+1 :green_heart:
shadedjars
7m 56s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 46s
hbase-server in the patch failed.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
6m 14s
the patch passed

+1 :green_heart:
compile
1m 39s
the patch passed

+1 :green_heart:
javac
1m 39s
the patch passed

+1 :green_heart:
shadedjars
10m 42s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 58s
hbase-server in the patch failed.

_ Other Tests _

-1 :x:
unit
11m 20s
hbase-server in the patch failed.

54m 49s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2449/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2449

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 49275b010f5f 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 687e53b7e4

Default Java
2020-01-14

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2449/2/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2449/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2449/2/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2449/2/testReport/

Max. process+thread count
527 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2449/2/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

Address @Apache9 and @infraio feedback (add you lads as reviewers.. thanks).

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  4s
Docker mode activated.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 55s
the patch passed

+1 :green_heart:
compile
1m 23s
the patch passed

+1 :green_heart:
javac
1m 23s
the patch passed

+1 :green_heart:
shadedjars
8m 20s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 52s
hbase-server in the patch failed.

_ Other Tests _

-1 :x:
unit
158m 15s
hbase-server in the patch failed.

192m 39s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2449/3/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2449

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 3f8135605e6d 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 01876071b9

Default Java
2020-01-14

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2449/3/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2449/3/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2449/3/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2449/3/testReport/

Max. process+thread count
3974 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2449/3/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 34s
Docker mode activated.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
6m 11s
the patch passed

+1 :green_heart:
compile
1m 37s
the patch passed

+1 :green_heart:
javac
1m 37s
the patch passed

+1 :green_heart:
shadedjars
10m  7s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
1m  3s
hbase-server in the patch failed.

_ Other Tests _

-1 :x:
unit
159m 37s
hbase-server in the patch failed.

202m 24s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2449/4/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2449

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 8ab4fef06f96 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / ee02e673b7

Default Java
2020-01-14

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2449/4/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2449/4/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2449/4/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2449/4/testReport/

Max. process+thread count
3775 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2449/4/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

Rerunning build. Looks like all tests passed but we have some of the below going on again. Will push tomorrow unless objection (or if the hanging tests seem related)
[WARNING] Tests run: 5115, Failures: 0, Errors: 0, Skipped: 33, Flakes: 1 [INFO]  [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time:  02:39 h (Wall Clock) [INFO] Finished at: 2020-10-01T03:38:34Z [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M4:test (secondPartTestsExecution) on project hbase-server: There are test failures. [ERROR]  [ERROR] Please refer to /home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-2449/yetus-jdk11-hadoop3-check/src/hbase-server/target/surefire-reports for the individual test results. [ERROR] Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream. [ERROR] ExecutionException The forked VM terminated without properly saying goodbye. VM crash or System.exit called? [ERROR] Command was /bin/sh -c cd /home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-2449/yetus-jdk11-hadoop3-check/src/hbase-server && /usr/lib/jvm/jdk-11.0.6+10/bin/java --add-opens=java.base/jdk.internal.ref=ALL-UNNAMED -enableassertions -Dhbase.build.id=2020-10-01T00:59:10Z -Xmx2200m -Djava.security.egd=file:/dev/./urandom -Djava.net.preferIPv4Stack=true -Djava.awt.headless=true -Djdk.net.URLClassPath.disableClassPathURLCheck=true -Dorg.apache.hbase.thirdparty.io.netty.leakDetection.level=advanced -Dio.netty.eventLoopThreads=3 -jar /home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-2449/yetus-jdk11-hadoop3-check/src/hbase-server/target/surefire/surefirebooter11638926920950205436.jar /home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-2449/yetus-jdk11-hadoop3-check/src/hbase-server/target/surefire 2020-10-01T01-00-45_753-jvmRun4 surefire944740561571154280tmp surefire_167910535663385871688825tmp [ERROR] Process Exit Code: 0 [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: ExecutionException The forked VM terminated without properly saying goodbye. VM crash or System.exit called? [ERROR] Command was /bin/sh -c cd /home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-2449/yetus-jdk11-hadoop3-check/src/hbase-server && /usr/lib/jvm/jdk-11.0.6+10/bin/java --add-opens=java.base/jdk.internal.ref=ALL-UNNAMED -enableassertions -Dhbase.build.id=2020-10-01T00:59:10Z -Xmx2200m -Djava.security.egd=file:/dev/./urandom -Djava.net.preferIPv4Stack=true -Djava.awt.headless=true -Djdk.net.URLClassPath.disableClassPathURLCheck=true -Dorg.apache.hbase.thirdparty.io.netty.leakDetection.level=advanced -Dio.netty.eventLoopThreads=3 -jar /home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-2449/yetus-jdk11-hadoop3-check/src/hbase-server/target/surefire/surefirebooter11638926920950205436.jar /home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-2449/yetus-jdk11-hadoop3-check/src/hbase-server/target/surefire 2020-10-01T01-00-45_753-jvmRun4 surefire944740561571154280tmp surefire_167910535663385871688825tmp [ERROR] Process Exit Code: 0 [ERROR] 	at org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:513) [ERROR] 	at org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:460) [ERROR] 	at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:301) [ERROR] 	at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:249) [ERROR] 	at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1217) [ERROR] 	at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1063) [ERROR] 	at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:889) [ERROR] 	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137) [ERROR] 	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210) [ERROR] 	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156) [ERROR] 	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148) [ERROR] 	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117) [ERROR] 	at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:190) [ERROR] 	at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:186) [ERROR] 	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) [ERROR] 	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [ERROR] 	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) [ERROR] 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [ERROR] 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [ERROR] 	at java.base/java.lang.Thread.run(Thread.java:834) [ERROR] Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called? [ERROR] Command was /bin/sh -c cd /home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-2449/yetus-jdk11-hadoop3-check/src/hbase-server && /usr/lib/jvm/jdk-11.0.6+10/bin/java --add-opens=java.base/jdk.internal.ref=ALL-UNNAMED -enableassertions -Dhbase.build.id=2020-10-01T00:59:10Z -Xmx2200m -Djava.security.egd=file:/dev/./urandom -Djava.net.preferIPv4Stack=true -Djava.awt.headless=true -Djdk.net.URLClassPath.disableClassPathURLCheck=true -Dorg.apache.hbase.thirdparty.io.netty.leakDetection.level=advanced -Dio.netty.eventLoopThreads=3 -jar /home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-2449/yetus-jdk11-hadoop3-check/src/hbase-server/target/surefire/surefirebooter11638926920950205436.jar /home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-2449/yetus-jdk11-hadoop3-check/src/hbase-server/target/surefire 2020-10-01T01-00-45_753-jvmRun4 surefire944740561571154280tmp surefire_167910535663385871688825tmp [ERROR] Process Exit Code: 0 [ERROR] 	at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:690) [ERROR] 	at org.apache.maven.plugin.surefire.booterclient.ForkStarter.access$600(ForkStarter.java:118) [ERROR] 	at org.apache.maven.plugin.surefire.booterclient.ForkStarter$2.call(ForkStarter.java:447) [ERROR] 	at org.apache.maven.plugin.surefire.booterclient.ForkStarter$2.call(ForkStarter.java:423) [ERROR] 	... 4 more [ERROR] -> [Help 1]

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 16s
Docker mode activated.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 51s
the patch passed

+1 :green_heart:
compile
1m 21s
the patch passed

+1 :green_heart:
javac
1m 21s
the patch passed

+1 :green_heart:
shadedjars
7m 58s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 56s
hbase-server in the patch failed.


no pin widget for `file_upload()

if it's possible to add pin widget for `file_upload()?

For performance reason, there is no pin widget for file_upload(). A workaround is output a buttion and use file_upload()` in the button's click callback.

"file_upload in a popup" is a good function, looking forward to it.

file_upload() is supported in pywebio dev version, and will be released to stable version soon.
dev doc: https://pywebio.readthedocs.io/en/dev/pin.html#pywebio.pin.put_file_upload

Thanks! This is awesome!


Crash in key, keyboard shortcut remapping

Microsoft PowerToys version
0.81.0
Installation method
PowerToys auto-update
Running as admin
No
Area(s) with issue?
Keyboard Manager
Steps to reproduce

Open Powertoys

Goto Keyboard Manager

Open key or keyboard shortcut remap, MAKE NO CHANGE and choose OK, click any space in PowerToys

Crash!

PowerToysReport_2024-05-25-22-02-46.zip
This bug is weird because it happens randomly, but probability is pretty high. Assume over 80%?
Faster do these steps, more bug chance.
Env is Windows 10 Pro 22H2, and system locale is Korean(Korea).
✔ Expected Behavior
Can choose ok in OK/Cancel dialog even there's no change.
❌ Actual Behavior
Crash.
It happens regardless of exist mappings, I've tested.
The only way to make this bug is
"open remap -> MAKE NO CHANGE -> choose OK -> click any space in PowerToys"
Other Software
No response

powertoyscrash.zip
Here's event viewer file of this bug


Unable to predict models

Got this error:
(py36) (localizer-main-VK8Pfd4G) C:\Users\internship\Desktop\localizer-main>python localizer\predict_for_images.py models\tools\config.json datasets\tools
2021-08-30 07:56:08.984216: I tensorflow/core/platform/cpu_feature_guard.cc:142] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX AVX2
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2021-08-30 07:56:09.538818: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1510] Created device /job:localhost/replica:0/task:0/device:GPU:0 with 10815 MB memory:  -> device: 0, name: Tesla K80, pci bus id: 0001:00:00.0, compute capability: 3.7
WARNING:tensorflow:No training configuration found in save file, so the model was *not* compiled. Compile it manually.
2021-08-30 07:56:10.462987: I tensorflow/compiler/mlir/mlir_graph_optimization_pass.cc:185] None of the MLIR Optimization Passes are enabled (registered 2)
2021-08-30 07:56:11.098206: I tensorflow/stream_executor/cuda/cuda_dnn.cc:369] Loaded cuDNN version 8202
Traceback (most recent call last):
  File "localizer\predict_for_images.py", line 31, in <module>
    predictions = localizer.predict(image)
  File "C:\Users\internship\Desktop\localizer-main\localizer\predict.py", line 264, in predict
    result = self._model.predict(batch.inputs)
  File "C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\keras\engine\training.py", line 1751, in predict
    tmp_batch_outputs = self.predict_function(iterator)
  File "C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\tensorflow\python\eager\def_function.py", line 885, in __call__
    result = self._call(*args, **kwds)
  File "C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\tensorflow\python\eager\def_function.py", line 933, in _call
    self._initialize(args, kwds, add_initializers_to=initializers)
  File "C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\tensorflow\python\eager\def_function.py", line 760, in _initialize
    *args, **kwds))
  File "C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\tensorflow\python\eager\function.py", line 3066, in _get_concrete_function_internal_garbage_collected
    graph_function, _ = self._maybe_define_function(args, kwargs)
  File "C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\tensorflow\python\eager\function.py", line 3463, in _maybe_define_function
    graph_function = self._create_graph_function(args, kwargs)
  File "C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\tensorflow\python\eager\function.py", line 3308, in _create_graph_function
    capture_by_value=self._capture_by_value),
  File "C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\tensorflow\python\framework\func_graph.py", line 1007, in func_graph_from_py_func
    func_outputs = python_func(*func_args, **func_kwargs)
  File "C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\tensorflow\python\eager\def_function.py", line 668, in wrapped_fn
    out = weak_wrapped_fn().__wrapped__(*args, **kwds)
  File "C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\tensorflow\python\framework\func_graph.py", line 994, in wrapper
    raise e.ag_error_metadata.to_exception(e)
TypeError: in user code:

    C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\keras\engine\training.py:1586 predict_function  *
        return step_function(self, iterator)
    C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\keras\engine\training.py:1576 step_function  **
        outputs = model.distribute_strategy.run(run_step, args=(data,))
    C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\tensorflow\python\distribute\distribute_lib.py:1286 run
        return self._extended.call_for_each_replica(fn, args=args, kwargs=kwargs)
    C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\tensorflow\python\distribute\distribute_lib.py:2849 call_for_each_replica
        return self._call_for_each_replica(fn, args, kwargs)
    C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\tensorflow\python\distribute\distribute_lib.py:3632 _call_for_each_replica
        return fn(*args, **kwargs)
    C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\keras\engine\training.py:1569 run_step  **
        outputs = model.predict_step(data)
    C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\keras\engine\training.py:1537 predict_step
        return self(x, training=False)
    C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\keras\engine\base_layer.py:1037 __call__
        outputs = call_fn(inputs, *args, **kwargs)
    C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\keras\engine\functional.py:415 call
        inputs, training=training, mask=mask)
    C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\keras\engine\functional.py:550 _run_internal_graph
        outputs = node.layer(*args, **kwargs)
    C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\keras\engine\base_layer.py:1044 __call__
        self._set_save_spec(inputs, args, kwargs)
    C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\tensorflow\python\training\tracking\base.py:530 _method_wrapper
        result = method(self, *args, **kwargs)
    C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\keras\engine\base_layer.py:3040 _set_save_spec
        flat_specs = [tf_utils.get_tensor_spec(x) for x in flat_arg]
    C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\keras\engine\base_layer.py:3040 <listcomp>
        flat_specs = [tf_utils.get_tensor_spec(x) for x in flat_arg]
    C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\keras\utils\tf_utils.py:467 get_tensor_spec
        spec = tf.TensorSpec(shape=t.shape, dtype=t.dtype, name=name)
    C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\tensorflow\python\framework\tensor_spec.py:51 __init__
        self._shape = tensor_shape.TensorShape(shape)
    C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\tensorflow\python\framework\tensor_shape.py:784 __init__
        self._dims = [as_dimension(dims)]
    C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\tensorflow\python\framework\tensor_shape.py:729 as_dimension
        return Dimension(value)
    C:\Users\internship\.virtualenvs\localizer-main-VK8Pfd4G\lib\site-packages\tensorflow\python\framework\tensor_shape.py:209 __init__
        .format(value, type(value))), None)
    <string>:3 raise_from

    TypeError: Dimension value must be integer or None or have an __index__ method, got value '<attribute 'shape' of 'numpy.generic' objects>' with type '<class 'getset_descriptor'>'

Any ideas why this is occuring?

Can it be that you are using grayscale images (RGB is expected)?

Actually i am running the sample program ( the one with tools), it's facing the same problem as well.

It is running on my computer. Are you running with the Pipfile from the repo? Which CUDA version do you have? I have 11.0, my log looks different:
2021-08-31 20:06:21.515057: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cudart64_110.dll
2021-08-31 20:06:23.918642: I tensorflow/compiler/jit/xla_cpu_device.cc:41] Not creating XLA devices, tf_xla_enable_xla_devices not set
2021-08-31 20:06:23.919854: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library nvcuda.dll
2021-08-31 20:06:23.953431: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1720] Found device 0 with properties:
pciBusID: 0000:01:00.0 name: GeForce RTX 2080 with Max-Q Design computeCapability: 7.5
coreClock: 1.095GHz coreCount: 46 deviceMemorySize: 8.00GiB deviceMemoryBandwidth: 357.69GiB/s
2021-08-31 20:06:23.954071: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cudart64_110.dll
2021-08-31 20:06:23.960619: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cublas64_11.dll
2021-08-31 20:06:23.961238: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cublasLt64_11.dll
2021-08-31 20:06:23.966340: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cufft64_10.dll
2021-08-31 20:06:23.968507: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library curand64_10.dll
2021-08-31 20:06:23.976967: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cusolver64_10.dll
2021-08-31 20:06:23.980579: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cusparse64_11.dll
2021-08-31 20:06:23.981558: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cudnn64_8.dll
2021-08-31 20:06:23.981993: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1862] Adding visible gpu devices: 0
2021-08-31 20:06:23.982527: I tensorflow/core/platform/cpu_feature_guard.cc:142] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2021-08-31 20:06:23.984163: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1720] Found device 0 with properties:
pciBusID: 0000:01:00.0 name: GeForce RTX 2080 with Max-Q Design computeCapability: 7.5
coreClock: 1.095GHz coreCount: 46 deviceMemorySize: 8.00GiB deviceMemoryBandwidth: 357.69GiB/s
2021-08-31 20:06:23.984963: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cudart64_110.dll
2021-08-31 20:06:23.985285: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cublas64_11.dll
2021-08-31 20:06:23.985600: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cublasLt64_11.dll
2021-08-31 20:06:23.985927: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cufft64_10.dll
2021-08-31 20:06:23.986292: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library curand64_10.dll
2021-08-31 20:06:23.986610: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cusolver64_10.dll
2021-08-31 20:06:23.986932: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cusparse64_11.dll
2021-08-31 20:06:23.987245: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cudnn64_8.dll
2021-08-31 20:06:23.987583: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1862] Adding visible gpu devices: 0
2021-08-31 20:06:24.556811: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1261] Device interconnect StreamExecutor with strength 1 edge matrix:
2021-08-31 20:06:24.557195: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1267]      0
2021-08-31 20:06:24.557383: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1280] 0:   N
2021-08-31 20:06:24.557750: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1406] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 6599 MB memory) -> physical GPU (device: 0, name: GeForce RTX 2080 with Max-Q Design, pci bus id: 0000:01:00.0, compute capability: 7.5)
2021-08-31 20:06:24.559108: I tensorflow/compiler/jit/xla_gpu_device.cc:99] Not creating XLA devices, tf_xla_enable_xla_devices not set
WARNING:tensorflow:No training configuration found in save file, so the model was not compiled. Compile it manually.
2021-08-31 20:06:26.013824: I tensorflow/compiler/mlir/mlir_graph_optimization_pass.cc:116] None of the MLIR optimization passes are enabled (registered 2)
2021-08-31 20:06:26.228832: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cudnn64_8.dll
.....

I have 11.4, I'll try it with 11.0

I have CUDA VERSION 11.4, I will try it with 11.0 and check if it works.

It worked
{
  "dataset": "datasets/maps/dataset.anno",
  "transfer_learning_base": "models/transfer_learning_base/features.tf",
  "pad_to": 32,
  "object_size": 88,
  "background_weight": 0.2,
  "object_weight_sigma_factor": 4,
  "weight_border": 7,
  "validated_training_examples_count": 50000,
  "final_training_examples_count": 25000,
  "training_fraction": 0.8,
  "training_examples_per_batch": 16,
  "training_examples_per_epoch": 5000,
  "training_examples_count_for_mean_computation": 100,
  "data_augmentation_rotation": [
    -0.05,
    0.05
  ],
  "data_augmentation_shear_rotation": [
    -0.05,
    0.05
  ],
  "data_augmentation_shear_scale": [
    0.95,
    1.05
  ],
  "data_augmentation_scale": [
    0.95,
    1.05
  ],
  "data_augmentation_color": [
    0.9,
    1.1
  ],
  "loss_weight_pos": 1,
  "loss_weight_angle": 1,
  "rng_seed": 1,
  "sigma": 1.5,
  "confidence_ksize": 7,
  "angle_ksize": 3,
  "pos_ksize": 3,
  "confidence_thr": 0.5,
  "position_diff_thr": 15,
  "angle_diff_thr": 15,
  "input_scale": 0.7,
  "model_scale": 0.125,
  "input_shape": [
    384,
    384,
    3
  ],
  "random_background_probability": 0.1,
  "process_count": 4
}

This is the config file I used for my own dataset named maps, which is same as the tools program.
But i am facing error
(localizer-main-VK8Pfd4G) (py36) C:\Users\internship\Desktop\localizer-main>python localizer\train.py models\maps\config.json
2021-09-01 10:54:55.122252: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library cudart64_110.dll
Filter "validate" contains 3 data elements
Filter "train" contains 12 data elements
Traceback (most recent call last):
  File "localizer\train.py", line 981, in <module>
    trainer.run()
  File "localizer\train.py", line 374, in run
    self._read_dataset()
  File "localizer\train.py", line 456, in _read_dataset
    assert np.allclose(1, flt.data_element_weights.sum()), flt_name
AssertionError: train

Should there be adjustments in the program?

This is because you only have 2 objects of category 1, and they all were reserved for validation by random selection. So there is no objects of category 1 for training. Can you add more such objects?

Thank you!


Multi-language UI components

Visual Designs:

https://app.zeplin.io/project/5878c3481bb7631c20cb161a/screen/5b05b3fce25151ce13d86d48
https://app.zeplin.io/project/5878c3481bb7631c20cb161a/screen/5d63b15b38345e9b5a6d7de0

@DominikGuzei will advise on where to add the components, but this is not a blocker to begin development

UI is implemented @DominikGuzei @rhyslbw @a-rukin


[WIP] Detection of DV frame format change & DV errors per Dseq

Info in events (not available by classic API)

Ooh,sound really cool.

@kieranjol, follow https://github.com/mipops/dvrescue

😍😍😍😍


Test rook-ceph component in e2e tests

Right now we test only rook which essentially does not deploy anything important(it deploys operator which is kicked into action once we create a CR called CephCluster using rook-ceph component).
So this deploy rook-ceph via CI config. But before doing this we need to make sure there are machines available to run rook-ceph on. This component needs raw disk which it uses for its own purpose, they can't conflict with OpenEBS. So we need to add extra machines, label them so that rook is deployed there and now use some other component to test if it can create PVC from rook.

Add e2e monitoring tests as well while someone is working on this. As mentioned in https://github.com/kinvolk/lokomotive/pull/405#issuecomment-626521195

Partially done in https://github.com/kinvolk/lokomotive/pull/1084. Will be finished in #1153.


Junk drawer of papercuts

[ ] New/edit podcast/episode flow should be rewritten as SPA
[ ] Uploader should be made much more pretty
[ ] Count episode feedback on podcast dash
[ ] Show asset statuses in importer
[ ] Play button on embed widget needs love
[ ] Site settings should be a tab on podcast settings
[ ] Site should have its own tab on podcast dash for URL, list of links. For pro: list blog posts and button to write new one
[x] Issue a test charge on newly added credit card when user is a subscriber
[x] Show episode feedback links on podcast feedback dash
[x] Move episode analytics to main dash
[x] Remove ability to edit slug

Closing the test charge. Two reasons why it's not a great idea after all:

An uncaptured charge still shows up as a charge for a lot of users, so they think we'd have charged them unnecessarily.
If the auth fails, we don't find out until later anyway. It's not synchronous. So there's little benefit to implementing that feature now, since it doesn't help prevent bad cards and it doesn't make the UX better.


HBASE-22277 Removed deprecated methods from Get

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
39
Docker mode activated.

_ Prechecks _

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 17 new or modified test files.

_ master Compile Tests _

0
mvndep
29
Maven dependency ordering for branch

+1
mvninstall
272
master passed

+1
compile
190
master passed

+1
checkstyle
202
master passed

+1
shadedjars
271
branch has no errors when building our shaded downstream artifacts.

+1
findbugs
485
master passed

+1
javadoc
146
master passed

_ Patch Compile Tests _

0
mvndep
17
Maven dependency ordering for patch

+1
mvninstall
321
the patch passed

+1
compile
222
the patch passed

+1
javac
222
the patch passed

+1
checkstyle
225
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
332
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
737
Patch does not cause any errors with Hadoop 2.7.4 or 3.0.0.

+1
findbugs
608
the patch passed

+1
javadoc
168
the patch passed

_ Other Tests _

+1
unit
205
hbase-client in the patch passed.

-1
unit
14420
hbase-server in the patch failed.

+1
unit
1376
hbase-mapreduce in the patch passed.

+1
unit
324
hbase-thrift in the patch passed.

+1
unit
1012
hbase-backup in the patch passed.

+1
unit
446
hbase-rest in the patch passed.

+1
asflicense
191
The patch does not generate ASF License warnings.

22424

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-173/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/173

Optional Tests
dupname  asflicense  javac  javadoc  unit  findbugs  shadedjars  hadoopcheck  hbaseanti  checkstyle  compile

uname
Linux 631339c42012 3.13.0-153-generic #203-Ubuntu SMP Thu Jun 14 08:52:28 UTC 2018 x86_64 GNU/Linux

Build tool
maven

Personality
/testptch/patchprocess/precommit/personality/provided.sh

git revision
master / 226c90c058

maven
version: Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T18:33:14Z)

Default Java
1.8.0_181

findbugs
v3.1.11

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-173/1/artifact/out/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-173/1/testReport/

Max. process+thread count
4549 (vs. ulimit of 10000)

modules
C: hbase-client hbase-server hbase-mapreduce hbase-thrift hbase-backup hbase-rest U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-173/1/console

Powered by
Apache Yetus 0.9.0 http://yetus.apache.org

This message was automatically generated.

Retriggered the build. Waiting for a +1 from it.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
77
Docker mode activated.

_ Prechecks _

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 17 new or modified test files.

_ master Compile Tests _

0
mvndep
43
Maven dependency ordering for branch

+1
mvninstall
298
master passed

+1
compile
188
master passed

+1
checkstyle
197
master passed

+1
shadedjars
273
branch has no errors when building our shaded downstream artifacts.

+1
findbugs
476
master passed

+1
javadoc
136
master passed

_ Patch Compile Tests _

0
mvndep
14
Maven dependency ordering for patch

+1
mvninstall
246
the patch passed

+1
compile
185
the patch passed

+1
javac
185
the patch passed

+1
checkstyle
189
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
263
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
532
Patch does not cause any errors with Hadoop 2.7.4 or 3.0.0.

+1
findbugs
502
the patch passed

+1
javadoc
140
the patch passed

_ Other Tests _

+1
unit
203
hbase-client in the patch passed.

-1
unit
16859
hbase-server in the patch failed.

+1
unit
1315
hbase-mapreduce in the patch passed.

+1
unit
309
hbase-thrift in the patch passed.

+1
unit
1236
hbase-backup in the patch passed.

+1
unit
466
hbase-rest in the patch passed.

+1
asflicense
221
The patch does not generate ASF License warnings.

24549

Reason
Tests

Failed junit tests
hadoop.hbase.quotas.TestSpaceQuotas

hadoop.hbase.master.procedure.TestSCPWithReplicasWithoutZKCoordinated

hadoop.hbase.replication.TestReplicationDisableInactivePeer

hadoop.hbase.client.TestSnapshotTemporaryDirectoryWithRegionReplicas

hadoop.hbase.client.TestFromClientSideWithCoprocessor

hadoop.hbase.master.procedure.TestSCPWithReplicas

hadoop.hbase.client.replication.TestReplicationAdminWithClusters

hadoop.hbase.client.TestFromClientSide3

hadoop.hbase.client.TestAsyncTableAdminApi

hadoop.hbase.client.TestAdmin1

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-173/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/173

Optional Tests
dupname  asflicense  javac  javadoc  unit  findbugs  shadedjars  hadoopcheck  hbaseanti  checkstyle  compile

uname
Linux 4f28804ff981 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 GNU/Linux

Build tool
maven

Personality
/testptch/patchprocess/precommit/personality/provided.sh

git revision
master / 184568cadd

maven
version: Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T18:33:14Z)

Default Java
1.8.0_181

findbugs
v3.1.11

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-173/3/artifact/out/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-173/3/testReport/

Max. process+thread count
5230 (vs. ulimit of 10000)

modules
C: hbase-client hbase-server hbase-mapreduce hbase-thrift hbase-backup hbase-rest U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-173/3/console

Powered by
Apache Yetus 0.9.0 http://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
63
Docker mode activated.

_ Prechecks _

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 17 new or modified test files.

_ master Compile Tests _

0
mvndep
36
Maven dependency ordering for branch

+1
mvninstall
339
master passed

+1
compile
218
master passed

+1
checkstyle
225
master passed

+1
shadedjars
330
branch has no errors when building our shaded downstream artifacts.

+1
findbugs
580
master passed

+1
javadoc
172
master passed

_ Patch Compile Tests _

0
mvndep
16
Maven dependency ordering for patch

+1
mvninstall
292
the patch passed

+1
compile
231
the patch passed

+1
javac
231
the patch passed

+1
checkstyle
223
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
326
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
667
Patch does not cause any errors with Hadoop 2.7.4 or 3.0.0.

+1
findbugs
621
the patch passed

+1
javadoc
182
the patch passed

_ Other Tests _

+1
unit
204
hbase-client in the patch passed.

+1
unit
13847
hbase-server in the patch passed.

+1
unit
1247
hbase-mapreduce in the patch passed.

+1
unit
275
hbase-thrift in the patch passed.

+1
unit
996
hbase-backup in the patch passed.

+1
unit
437
hbase-rest in the patch passed.

+1
asflicense
190
The patch does not generate ASF License warnings.

21905

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-173/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/173

Optional Tests
dupname  asflicense  javac  javadoc  unit  findbugs  shadedjars  hadoopcheck  hbaseanti  checkstyle  compile

uname
Linux bfaa7bc756b7 3.13.0-153-generic #203-Ubuntu SMP Thu Jun 14 08:52:28 UTC 2018 x86_64 GNU/Linux

Build tool
maven

Personality
/testptch/patchprocess/precommit/personality/provided.sh

git revision
master / 3f40df8085

maven
version: Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T18:33:14Z)

Default Java
1.8.0_181

findbugs
v3.1.11

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-173/4/testReport/

Max. process+thread count
5234 (vs. ulimit of 10000)

modules
C: hbase-client hbase-server hbase-mapreduce hbase-thrift hbase-backup hbase-rest U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-173/4/console

Powered by
Apache Yetus 0.9.0 http://yetus.apache.org

This message was automatically generated.


Pagination documentation

Does anyone have documentation on how to use this with django's built in pagination capabilities ? https://docs.djangoproject.com/en/dev/topics/pagination/
--edit--
Can documentation on how to do this be added to the project documentation section about using django-filters with class based generic views?

Pass the FilterSet's QuerySet to the pagination mechanism. (StackOverflow is your place for this kind of question.)

@carltongibson - I've clarified my issue. I wasnt so much asking for help with fixing my problem as pointing out something that could be better documented in the project documentation.


Tooling page is significantly outdated

https://github.com/rust-embedded/book/blob/master/src/intro/tooling.md
Nothing about probe-rs project; old Rust version, etc.

Indeed. Thanks for noticing.
To anybody reading this, please feel free to send a PR updating it.
Here is an example of a more up-to-date setup

Yeah I came across this today and went to write up basically the same ticket.

I think the steps are now:

Install rustup
Add appropriate targets (i.e. pre-compiled rust libraries) for your MCU
cargo install probe-run --features=cli

No OpenOCD required, nor arm-none-eabi-gcc.
You could still list GDB (or arm-none-eabi-gdb) as an optional thing, but you should probably call it through the rust-gdb wrapper script (first setting RUST_GDB=arm-none-eabi-gdb to it knows what to call).

I think the steps are now:

Install rustup
Add appropriate targets (i.e. pre-compiled rust libraries) for your MCU
cargo install probe-run --features=cli

No OpenOCD required, nor arm-none-eabi-gcc.
You could still list GDB (or arm-none-eabi-gdb) as an optional thing, but you should probably call it through the rust-gdb wrapper script (first setting RUST_GDB=arm-none-eabi-gdb to it knows what to call).

Is there a guide somewhere on how to set this up? I just got my first STM chip to follow the embedded Rust book, and I'm not sure where to start or how to follow along since the tooling is outdated now. For now I guess I'm going to follow the current version of the book exactly just so I can get some code flashed to my board, but it would be nice to use the newer tools.
probe-rs sounds neat, but it also seems like its a library? I'm not sure how I'd use it to flash and debug. Any help would be appreciated.


Bugfix: replace tap-parser with tap-out

There were certain conditions that would lead tap-dot to return 1 exit code despite all tests passing. This has been fixed by replacing tap-parser with your own tap parser tap-out. I also updated chalk/through2 to their latest versions.
I would have added a test fixture, but there weren't any tests. Given the purpose of this module, presumably you use either node-tap or tape, but I didn't want to speculate and possibly do unnecessary work.

ping @scottcorgan

Sorry about that. It was merged and published to NPM.
I have a complete rewrite of tap-dot and tap-spec based off of a set of new modules that are more composable to create the ultimate tap formatter. Keep a look out for tap-dot 2.0.


Changed debug::print to print hex values

This change is

Is there a way to continue printing values as decimals following this update? In our case decimals are more relevant than hex for debugging

Hey, please see this:
https://github.com/starkware-libs/cairo/issues/3459

What about printing decimal values rather than short strings? Is there a different print method to support this?


ERROR: FATAL when adding a new SkeletonProfileHumanoid

Tested versions
v4.2.1.stable.official [b09f793f5]
System information
Windows 11 Pro - 23H2 - AtlasOS - Vulkan API 1.3.277
Issue description
Godot crash when I want to add a new SkeletonProfileHumanoid :
ERROR: FATAL: Index p_index = 2 is out of bounds (size() = 2).
at: get (./core/templates/cowdata.h:158)

Steps to reproduce

Download the gltf model here : https://sketchfab.com/3d-models/curious-skeleton-757d9863b3504a75a439b2b99a530454#download
Add it to the project folder
In Godot, select the "scene.gltf" and click on the "Advecement..." button in the import tab
Select the Skeleton3D and add a new BoneMap
Add a new SkeletonProfileHumanoid to the BoneMap

Minimal reproduction project (MRP)
game.zip

Found an error, but couldn't reproduce the crash itself. Can anyone confirm this still causes a crash?


FB get user's profile data (first_name, last_name etc).

I've tried to find out if there is an api for getting user profile data, but unfortunately i didn't found it. Am I missing smth. or it's just not a part of the api? If so, I'd be happy to contribute and extend current api.

take a look at this one #1098

Yeah, this is coming soon! If you grab the branch @ouadie-lahdioui linked to, you'll have both bot.getMessageUser and controller.api.user_profile() for Facebook.

@benbrown sweet 😻

What is the status of this PR?

I'm closing this issue, since it was resolved within this PR #1098.


Fix bug for putting duplicated messsages while sending batch message

What is the purpose of the change
Fix bug for putting duplicated messsages while sending batch message
Brief changelog
Remove the redundant code
Verifying this change
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage increased (+0.2%) to 47.327% when pulling acbc6f95e1c713eb44e4331bb5ebdd4984db0812 on jameslcj:5.0.0-beta into 33fd330899145654b7c25eac36c0ceb3bbfe5aba on apache:5.0.0-beta.

Codecov Report

Merging #4466 (acbc6f9) into 5.0.0-beta (33fd330) will decrease coverage by 0.08%.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             5.0.0-beta    #4466      +/-   ##
================================================
- Coverage         43.15%   43.06%   -0.09%
+ Complexity         6064     6049      -15
================================================
  Files               801      801
  Lines             57087    57086       -1
  Branches           7805     7805
================================================
- Hits              24637    24586      -51
- Misses            29229    29274      +45
- Partials           3221     3226       +5

Impacted Files
Coverage Δ

...ocketmq/broker/processor/SendMessageProcessor.java
45.64% <ø> (+0.13%)
:arrow_up:

...rg/apache/rocketmq/common/stats/StatsSnapshot.java
84.61% <0.00%> (-15.39%)
:arrow_down:

...va/org/apache/rocketmq/common/stats/StatsItem.java
50.00% <0.00%> (-5.00%)
:arrow_down:

...org/apache/rocketmq/common/stats/StatsItemSet.java
41.79% <0.00%> (-2.99%)
:arrow_down:

...ava/org/apache/rocketmq/filter/util/BitsArray.java
59.82% <0.00%> (-2.57%)
:arrow_down:

...va/org/apache/rocketmq/logging/inner/Appender.java
30.33% <0.00%> (-2.25%)
:arrow_down:

...a/org/apache/rocketmq/filter/util/BloomFilter.java
59.13% <0.00%> (-2.16%)
:arrow_down:

...che/rocketmq/container/BrokerContainerStartup.java
55.31% <0.00%> (-2.13%)
:arrow_down:

...a/org/apache/rocketmq/store/StoreStatsService.java
48.06% <0.00%> (-1.66%)
:arrow_down:

...rocketmq/client/impl/factory/MQClientInstance.java
45.64% <0.00%> (-1.39%)
:arrow_down:

... and 7 more

Continue to review full report at Codecov.

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