Updates

Coverage remained the same at 71.795% when pulling 8b9aca2e6d67afcadb2728e6506cc877e5c19d41 on proinsias/updates into 74f739f258ea6574efb8533e58df0609b2bd0dc5 on develop.

Coverage remained the same at 71.795% when pulling 8b9aca2e6d67afcadb2728e6506cc877e5c19d41 on proinsias/updates into 74f739f258ea6574efb8533e58df0609b2bd0dc5 on develop.

Codecov Report

Merging #91 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop      #91   +/-   ##
========================================
  Coverage    71.79%   71.79%
========================================
  Files            2        2
  Lines           78       78
========================================
  Hits            56       56
  Misses          22       22

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 74f739f...8b9aca2. Read the comment docs.


Error when importing idle-vue

I want to use idle-vue in an electron app using https://github.com/SimulatedGREG/electron-vue, but when I import idle-vue in my main.js file it throws an error:
Uncaught SyntaxError: Unexpected token import
    at createScript (vm.js:53:10)
    at Object.runInThisContext (vm.js:95:10)
    at Module._compile (module.js:543:28)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.require (module.js:498:17)
    at require (internal/module.js:20:19)
    at eval (eval at <anonymous> (http://localhost:9080/renderer.js:1959:1), <anonymous>:1:18)

The main.js looks like this:
import 'basscss/css/basscss.min.css'
import 'flexboxgrid/css/flexboxgrid.min.css'

import 'gsap'

import Vue from 'vue'
import axios from 'axios'

import App from './App'
import router from './router'
import store from './vuex/store'
import i18n from './locales/index'
import IdleVue from 'idle-vue'

import './lib/qrcode'

if (!process.env.IS_WEB) Vue.use(require('vue-electron'))
Vue.http = Vue.prototype.$http = axios
Vue.config.productionTip = false

Vue.use(IdleVue, { store })

/* eslint-disable no-new */
new Vue({
  components: { App },
  router,
  store,
  i18n,
  template: '<App/>'
}).$mount('#app')

It might happen because of a bad babel-loader configuration

Any luck figuring out why this happens? I haven't come across it, so if you still don't know where it's from, could you send me a link to a commit with this error?

Got the same issue. Anyone resolved that?

I too had the same issue. Still not working, beause for main key u mentioned dist/index.js but in the actual directory there is no index file in dist folder.

Thank you for pointing this out @rajeshwar-fissionhq, it is now fixed with 2.0.3.


get_frame_count

get_frame_count is now deprecated in favor of frame_count but there is no way to safely get a context.
It appears that frame_count does not need &Context: https://docs.rs/imgui/0.1.0/src/imgui/lib.rs.html#102-104

there is no way to safely get a context.

But you need a context to call almost all imgui-rs functions...?
The upstream C++ function dereferences a NULL pointer if a context is not available.

The only way get Context is https://docs.rs/imgui/0.1.0/imgui/struct.Ui.html#method.imgui
which is

Deprecated since 0.1.0: This function is potentially unsafe and will be removed

If you have a Ui reference, you can use Ui::frame_count


Cache rel size

Makes sense. Needs comments. Please squash the commits into one, they don't make much sense separately.
How much speedup does this give? I think it's a bit early to do performance optimizations in general, but this is pretty straightforward so I don't see much downside. We can always rip this out again later if it gets in the way.

Makes sense. Needs comments. Please squash the commits into one, they don't make much sense separately.

Done

How much speedup does this give? I think it's a bit early to do performance optimizations in general, but this is pretty straightforward so I don't see much downside. We can always rip this out again later if it gets in the way.

Did you missed my message in Element?
Time of zenith-rel-truncate is reduced almost twice:
With BTreeMap for relation size the time is decreased from 30 seconds till 16.
You can look at my implementation at cache_rel_size branch.
But I failed to normally add cache in ObjectRepository: I ave to place it in mutex, while it is actually not needed. Otherwise it requires to make many functions mutable and it is not possible because non-mutable reference to object stored is passed.

Makes sense. Needs comments. Please squash the commits into one, they don't make much sense separately.

Done

Thanks!

How much speedup does this give? I think it's a bit early to do performance optimizations in general, but this is pretty straightforward so I don't see much downside. We can always rip this out again later if it gets in the way.

Did you missed my message in Element?
Time of zenith-rel-truncate is reduced almost twice:
With BTreeMap for relation size the time is decreased from 30 seconds till 16.

Cool. Let's mention that in the commit message too.

You can look at my implementation at cache_rel_size branch.
But I failed to normally add cache in ObjectRepository: I ave to place it in mutex, while it is actually not needed. Otherwise it requires to make many functions mutable and it is not possible because non-mutable reference to object stored is passed.

You could use RwLock intead of Mutex to allow concurrent readers. Or the (chashmap crate or something similar.

Issue for CI failure that appeared in this tests: https://github.com/zenithdb/zenith/issues/225
Let's fix failure first and merge this after


VP3210 refuses to take dcu-altered rom

Device
Protectli VP3210
RTE version

OSFV version
branch: vp-3210-testing, (based on develop 4147db463598a5d7a8757667b8f14f1ecac09801) current commit b125dabeefd936b8296e6718c393fd9ccd67b953
Affected component(s) or functionality
No response
Brief summary
DCU suite fails due to the changes made not being actually implemented
How reproducible
happens every time to me
How to reproduce
try running dcu.robot suite
Expected behavior
the test should modify the rom
Actual behavior
the test fails because the changes made, are not properly implented
Link to screenshots or logs
dcu.robot_log-fail.zip
Additional context
No response
Solutions you've tried
No response

According to logs:
11:46:35.937	INFO	Flash write failed with code 1
11:46:35.938	INFO	Executing command: flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=16000 -c MX25L12833F/MX25L12835F/MX25L12845E/MX25L12865E/MX25L12873F -w /data/write.rom
flashrom v1.3.0 on Linux 5.4.69 (armv7l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
No EEPROM/flash device found.
Note: flashrom can never write if the flash chip isn't found automatically.

So obviously, if the flashing failed, the changes would not apply.

Today it started working just fine, i guess something changed and updating submodules & launching requirements.txt solved this problem.
dcu.robot_log_pass.zip


Empty Views

Hello,
I've been supporting a developer who ran into a recurring issue: Some iModels are showing up empty in the sample apps. It looks this happens when the default view doesn't have any models in it. I found some design review code as a solution for now. Is there any other convenient way to create a default view that contains all models within an iModel?
Thanks,
Roop

There currently isn't. Unfortunately the the core team doesn't have this on the backlog. Would you be willing to create an API from the code you are sharing as the solution?

Sure, I can do that.

The API has been pushed.
Links to:

Blog
APIs: ViewCreator3d | ViewCreator2d


User audit log updates

We need to update "active user" representation - add ID in brackets to user name.

Merged


[stable/postgresql] add postgresqlExtendedConf for statefulset slave

What this PR does / why we need it:
the value postgresqlExtendedConf should also be used by slave, not only master.
Special notes for your reviewer:
this commit merged before may be useful.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

@LittleWhiteYA can you solve the conflicts in the stable/postgresql/Chart.yaml file?

@tompizmor solved !


[Feature Request]: Model Serving - Taints/Tolerations/Affinities/Etc

Feature description
Model Serving is growing to support accelerators -- this could be problematic if the pods in question end up using nodes that support GPUs when we are not intending it. Flip-side, we need to be able to "opt-in" to that when we want to use GPUs.
This likely is affinities/anti-affinities but I don't know a ton about this space, so this is a placeholder for future discussions.
Describe alternatives you've considered
No response
Anything else?
No response

cc @jedemo @kywalker-rh @vconzola

we essentially need to ensure that if the user has conveyed that they do NOT want to use GPUs for model serving, their pods actively avoid GPU nodes, so as to not hog them for nothing, and potentially preventing other pods from accessing those GPU nodes.
that behavior is not provided by OpenShift by default: a pod could land on a GPU node even if it did not actively seek it, just by fluke.
maybe the easier thing is to let customer taint GPU nodes. But we would need to make sure that the matching toleration is only given to the pod when we know the user wants a GPU, and taken away when we know they don't want a GPU.

I think this change should happen at the kube scheduler level rather than in each of our individual products. It makes sense that there should be some flag in the scheduler to prefer other nodes over ones with specialized tags

Just to add a question here:
It seems that specifying 0 GPUs is not the same as not adding them. We need to translate that to UX cause, as other k8s flows, that might mislead the user. We need to add the logic and actively say that it's not the same having 0 gpus than not having them (that could translate to a checkbox or whatever)

Making that change in base Kube will be a long-term thing. We probably want something done in-house in a shorter timeframe, IMO. Also, the reply would likely be that it's what anti-affinities are for.
Whether a user asked for zero GPU or whether they did not even see a box showing them GPU ... does not really make a difference.
Logic is simple:
if requested_gpu > N   (where N>0) then seek a node with a N available GPUs
else (all other cases), actively avoid nodes that have GPUs

Right, there's a bit more to it than that, but I think it's a suboptimal thing to require each product to have that logic, and it's not just Nvidia GPUs, there are other accelerators that are coming too. We need some global solution rather than an ad-hoc set of solutions in each product

@cfchase do we have a more global solution here? I'm not sure Kube will jump on board with this -- do we want some middle-man controller or something?

Turns out -- this is already done in code -- we may want to support UI for it.
  if (hasGpu) {
    tolerations.push({
      effect: 'NoSchedule',
      key: 'nvidia.com/gpu',
      operator: 'Exists',
    });
  }

This code is used for both Notebooks and Model Servers. It's not configurable and there may be a need to flex the functionality in the future so "GPU Notebooks" and "GPU Model Servers" are not on the same resource stack... but for today this is handled in the current Dashboard code.

A couple of questions for this:

We already created a way to intentionally hide GPU/accelerator resources in Custom Serving Runtimes with a special annotation: https://github.com/opendatahub-io/odh-dashboard/issues/1258
Maybe part of this is already cover by the accelerator work

Should we still work on this?
cc @Gkrumbach07

@lucferbux

Maybe part of this is already cover by the accelerator work
accelerators still respect this annotation and will set the accelerator to none.

Ok great, but my question was broader, now that we have a different UI and users actively select an accelerator in the code, do you think everything from this conversation is covered here?
We had two open threads:

Ability to hide GPUs in runtimes that don't support that feature (already covered)
Ability to control taints/tolerations/affinity and enablement of accelerators in model servers

My impression is that everything is covered by the work, but I would like to double check @Gkrumbach07
@andrewballantyne just adding you to the conversation in case I'm missing something

Ability to hide GPUs in runtimes that don't support that feature (already covered)

Yep this is already implemented

Ability to control taints/tolerations/affinity and enablement of accelerators in model servers

accelerator profiles can have an array of tolerations which get assigned in the model serving form. however there is not a UI for setting taints. I am also not familiar with affinity being used. I was under the impression that affinity was not needed and taints was something an admin did through the console and not odh dashboard.
So im guessing we are just missing affinities, but if gpu nodes are set up properly with taints, then im not sure why they are needed. If the case we are trying to avoid is scheduling on a gpu node when not specifically requested

I say we close this -- affinities isn't something we are supporting today on any resource. If we want to rework this later we should do it for all our resources.
/close
I'm closing it with the expectation of no disagreement, if there is one, feel free to reopen and we can discuss the value. This ticket is old and the original goal it set out to do is handled well enough for the needs of accelerators as they are handled today.


Updated support for launching cockpit and console

@miq-bot add_label bug
@miq-bot add_label fine/no
BZ https://bugzilla.redhat.com/show_bug.cgi?id=1471158

@miq-bot remove_label fine/no
@miq-bot add_label fine/yes

@miq-bot add_label blocker

@chalettu This can be backported to Euwe branch?

for the record, no this cannot be backported to Euwe.  I'll make a PR to the Euwe branch.

Can you confirm Fine should uses supports_cockpit (not supports_launch_cockpit)? I know there were lots of discussion around what version uses what... so I want to make sure I can resolve conflicts by just moving supports_cockpit from attributes to decorators.


Update info in FAQ for data permissions and txns

I've added some logic around the new read/write rules - some of this @mateuszmlc is finalising, so will push to docs once that is complete.


problem/ others: inkedlist-intersection

Codecov Report

Merging #22 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #22   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          13     14    +1
  Lines         266    300   +34
=====================================
+ Hits          266    300   +34

Flag
Coverage Δ

#go
100% <100%> (ø)
:arrow_up:

#javascript
100% <ø> (ø)
:arrow_up:

Impacted Files
Coverage Δ

problems/other/listintersection/intersection.go
100% <100%> (ø)

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 39a9279...eb6988c. Read the comment docs.


ODBC Driver not found on Mac OS 12.4 Monterey

Hello,
I can't connect to mssql from my fresh OS X.
Clean OS installation, installed ODBC driver 18 via homebrew, no errors
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"
brew tap microsoft/mssql-release https://github.com/Microsoft/homebrew-mssql-release
brew update
HOMEBREW_NO_ENV_FILTERING=1 ACCEPT_EULA=Y brew install msodbcsql18 mssql-tools18
and
pecl install sqlsrv
pecl install pdo_sqlsrv
PHP looks ok, extensions in version 5.10.0 but when I tried establish connection, script returned me SQLSTATE[IMSSP]: This extension requires the Microsoft ODBC Driver for SQL Server to communicate with SQL Server. Access the following URL to download the ODBC Driver for SQL Server for x64: https://go.microsoft.com/fwlink/?LinkId=163712.
Command bcp -v returned version 18.0.0001.1.
I tried different versions of odbc connector (17.9) and sqsrv libs (5.9) and different version of PHP but the same result.
In old PHP 7.1 i established PDO_DBLIB connection, but no chance via sqlsrv (in compatible version of all of course).
Mac os X firewall is disabled.

Solved. Problem with self signed certificate on server. Parameter TrustServerCertificate=1 fixed issue.


Minimum Lua version?

Hi, package maintainer for Hilbish here. With release 0.4.0, I've decided to package Lunacolors for the AUR instead of tying it to Hilbish. The source tarball doesn't come with the git info anyways, so I'd have no way of pulling this.
I only need to know if this library targets a specific Lua version to decide whether I need to split this package or not.

ill say the minimum version that works is 5.1, since gopher-lua (the lua vm for Hilbish) is 5.1


Use correct kotlin gradle plugin version

Goal
Our build script setup means we have to specify versions in two places. The kotlin gradle plugin version was not updated under buildSrc so I changed it to use the correct one. This shouldn't affect our compile-time language support.

I'd check with a test app using kotlin 1.4 just in case 😅


Fails to parse enum value, possibly because it is declared over multiple lines

In SecPolicy.h in the Security framework:
CF_ENUM(CFOptionFlags) {
    kSecRevocationOCSPMethod = (1 << 0),
    kSecRevocationCRLMethod = (1 << 1),
    kSecRevocationPreferCRL = (1 << 2),
    kSecRevocationRequirePositiveResponse = (1 << 3),
    kSecRevocationNetworkAccessDisabled = (1 << 4),
    kSecRevocationUseAnyAvailableMethod = (kSecRevocationOCSPMethod |
                                           kSecRevocationCRLMethod)
};

emits:
  kSecRevocationOCSPMethod = 1;
  kSecRevocationCRLMethod = 2;
  kSecRevocationPreferCRL = 4;
  kSecRevocationRequirePositiveResponse = 8;
  kSecRevocationNetworkAccessDisabled = 16;
  kSecRevocationUseAnyAvailableMethod = ;

Fixed


HBASE-26154: Adds exception metrics for QuotaExceededException and RpcThrottlingException

Adds https://github.com/apache/hbase/pull/3544 to branch-2.4

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2.4 Compile Tests _

+0 :ok:
mvndep
0m 16s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 41s
branch-2.4 passed

+1 :green_heart:
compile
5m 16s
branch-2.4 passed

+1 :green_heart:
checkstyle
2m 11s
branch-2.4 passed

+1 :green_heart:
spotbugs
4m 20s
branch-2.4 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 26s
the patch passed

+1 :green_heart:
compile
5m 13s
the patch passed

+1 :green_heart:
javac
5m 13s
the patch passed

+1 :green_heart:
checkstyle
2m  9s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
17m 49s
Patch does not cause any errors with Hadoop 2.10.0 or 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
5m  9s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 48s
The patch does not generate ASF License warnings.

59m 47s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3546/1/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile

uname
Linux e4786d50dbce 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / f8ba9b3fe1

Default Java
AdoptOpenJDK-1.8.0_282-b08

Max. process+thread count
96 (vs. ulimit of 12500)

modules
C: hbase-hadoop-compat hbase-hadoop2-compat hbase-server hbase-thrift U: .

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

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

-0 :warning:
yetus
0m  7s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.4 Compile Tests _

+0 :ok:
mvndep
0m 16s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 43s
branch-2.4 passed

+1 :green_heart:
compile
2m  8s
branch-2.4 passed

+1 :green_heart:
shadedjars
6m 27s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 43s
branch-2.4 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 52s
the patch passed

+1 :green_heart:
compile
2m  8s
the patch passed

+1 :green_heart:
javac
2m  8s
the patch passed

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

+1 :green_heart:
javadoc
1m 43s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 27s
hbase-hadoop-compat in the patch passed.

+1 :green_heart:
unit
0m 28s
hbase-hadoop2-compat in the patch passed.

+1 :green_heart:
unit
158m 40s
hbase-server in the patch passed.

+1 :green_heart:
unit
4m 18s
hbase-thrift in the patch passed.

196m 49s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3546/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 269b485e0a82 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
branch-2.4 / f8ba9b3fe1

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

Max. process+thread count
3602 (vs. ulimit of 12500)

modules
C: hbase-hadoop-compat hbase-hadoop2-compat hbase-server hbase-thrift U: .

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

-0 :warning:
yetus
0m  8s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.4 Compile Tests _

+0 :ok:
mvndep
0m 20s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
6m 11s
branch-2.4 passed

+1 :green_heart:
compile
3m 22s
branch-2.4 passed

+1 :green_heart:
shadedjars
9m 38s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
2m 57s
branch-2.4 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 26s
Maven dependency ordering for patch

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

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

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

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

+1 :green_heart:
javadoc
2m 59s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 35s
hbase-hadoop-compat in the patch passed.

+1 :green_heart:
unit
0m 46s
hbase-hadoop2-compat in the patch passed.

+1 :green_heart:
unit
249m 43s
hbase-server in the patch passed.

+1 :green_heart:
unit
5m  7s
hbase-thrift in the patch passed.

306m 52s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3546/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 16c92e3df7b2 4.15.0-142-generic #146-Ubuntu SMP Tue Apr 13 01:11:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / f8ba9b3fe1

Default Java
AdoptOpenJDK-11.0.10+9

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

Max. process+thread count
2668 (vs. ulimit of 12500)

modules
C: hbase-hadoop-compat hbase-hadoop2-compat hbase-server hbase-thrift U: .

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2.4 Compile Tests _

+0 :ok:
mvndep
0m 18s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 51s
branch-2.4 passed

+1 :green_heart:
compile
5m 35s
branch-2.4 passed

+1 :green_heart:
checkstyle
2m 38s
branch-2.4 passed

+1 :green_heart:
spotbugs
4m 49s
branch-2.4 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 32s
the patch passed

+1 :green_heart:
compile
5m 26s
the patch passed

+1 :green_heart:
javac
5m 26s
the patch passed

+1 :green_heart:
checkstyle
2m 36s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
18m 16s
Patch does not cause any errors with Hadoop 2.10.0 or 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
5m 37s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 54s
The patch does not generate ASF License warnings.

63m 15s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3546/2/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile

uname
Linux d961b920a2e1 4.15.0-136-generic #140-Ubuntu SMP Thu Jan 28 05:20:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / cb1174e9e1

Default Java
AdoptOpenJDK-1.8.0_282-b08

Max. process+thread count
96 (vs. ulimit of 12500)

modules
C: hbase-hadoop-compat hbase-hadoop2-compat hbase-server hbase-thrift U: .

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

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

-0 :warning:
yetus
0m  6s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.4 Compile Tests _

+0 :ok:
mvndep
0m 16s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 37s
branch-2.4 passed

+1 :green_heart:
compile
2m  5s
branch-2.4 passed

+1 :green_heart:
shadedjars
6m  4s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 43s
branch-2.4 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 16s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 20s
the patch passed

+1 :green_heart:
compile
2m  5s
the patch passed

+1 :green_heart:
javac
2m  5s
the patch passed

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

+1 :green_heart:
javadoc
1m 43s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 27s
hbase-hadoop-compat in the patch passed.

+1 :green_heart:
unit
0m 27s
hbase-hadoop2-compat in the patch passed.

+1 :green_heart:
unit
143m 30s
hbase-server in the patch passed.

+1 :green_heart:
unit
4m 10s
hbase-thrift in the patch passed.

179m 37s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3546/2/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 7e8bb1fa1e17 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
branch-2.4 / cb1174e9e1

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

Max. process+thread count
4206 (vs. ulimit of 12500)

modules
C: hbase-hadoop-compat hbase-hadoop2-compat hbase-server hbase-thrift U: .

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

-0 :warning:
yetus
0m  6s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.4 Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m  0s
branch-2.4 passed

+1 :green_heart:
compile
2m 31s
branch-2.4 passed

+1 :green_heart:
shadedjars
6m 53s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
2m  6s
branch-2.4 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 16s
Maven dependency ordering for patch

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

+1 :green_heart:
compile
2m 31s
the patch passed

+1 :green_heart:
javac
2m 31s
the patch passed

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

+1 :green_heart:
javadoc
2m  8s
the patch passed

_ Other Tests _

-1 :x:
unit
0m 27s
hbase-hadoop-compat in the patch failed.

+1 :green_heart:
unit
0m 31s
hbase-hadoop2-compat in the patch passed.

+1 :green_heart:
unit
141m 15s
hbase-server in the patch passed.

+1 :green_heart:
unit
4m 48s
hbase-thrift in the patch passed.

182m 57s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3546/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux b9b93cf19a19 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / cb1174e9e1

Default Java
AdoptOpenJDK-11.0.10+9

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

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

Max. process+thread count
4009 (vs. ulimit of 12500)

modules
C: hbase-hadoop-compat hbase-hadoop2-compat hbase-server hbase-thrift U: .

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

I'm not sure why this is failing

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2.4 Compile Tests _

+0 :ok:
mvndep
0m 27s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 14s
branch-2.4 passed

+1 :green_heart:
compile
6m  7s
branch-2.4 passed

+1 :green_heart:
checkstyle
2m 50s
branch-2.4 passed

+1 :green_heart:
spotbugs
5m  4s
branch-2.4 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 39s
the patch passed

+1 :green_heart:
compile
5m 43s
the patch passed

+1 :green_heart:
javac
5m 43s
the patch passed

+1 :green_heart:
checkstyle
2m 39s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
18m  4s
Patch does not cause any errors with Hadoop 2.10.0 or 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
5m 33s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 53s
The patch does not generate ASF License warnings.

65m 19s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3546/3/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile

uname
Linux 78f58656c810 4.15.0-136-generic #140-Ubuntu SMP Thu Jan 28 05:20:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / cb1174e9e1

Default Java
AdoptOpenJDK-1.8.0_282-b08

Max. process+thread count
96 (vs. ulimit of 12500)

modules
C: hbase-hadoop-compat hbase-hadoop2-compat hbase-server hbase-thrift U: .

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

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

-0 :warning:
yetus
0m  8s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.4 Compile Tests _

+0 :ok:
mvndep
0m 17s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 12s
branch-2.4 passed

+1 :green_heart:
compile
2m 23s
branch-2.4 passed

+1 :green_heart:
shadedjars
6m 47s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
2m  7s
branch-2.4 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 21s
Maven dependency ordering for patch

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

+1 :green_heart:
compile
2m 30s
the patch passed

+1 :green_heart:
javac
2m 30s
the patch passed

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

+1 :green_heart:
javadoc
2m  8s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 30s
hbase-hadoop-compat in the patch passed.

+1 :green_heart:
unit
0m 33s
hbase-hadoop2-compat in the patch passed.

+1 :green_heart:
unit
137m 24s
hbase-server in the patch passed.

+1 :green_heart:
unit
4m 30s
hbase-thrift in the patch passed.

178m 49s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3546/3/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 832ffda49529 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
branch-2.4 / cb1174e9e1

Default Java
AdoptOpenJDK-11.0.10+9

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

Max. process+thread count
4273 (vs. ulimit of 12500)

modules
C: hbase-hadoop-compat hbase-hadoop2-compat hbase-server hbase-thrift U: .

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

-0 :warning:
yetus
0m  7s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.4 Compile Tests _

+0 :ok:
mvndep
0m 19s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 37s
branch-2.4 passed

+1 :green_heart:
compile
2m  8s
branch-2.4 passed

+1 :green_heart:
shadedjars
6m 11s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 42s
branch-2.4 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 16s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 32s
the patch passed

+1 :green_heart:
compile
2m 10s
the patch passed

+1 :green_heart:
javac
2m 10s
the patch passed

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

+1 :green_heart:
javadoc
1m 41s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 27s
hbase-hadoop-compat in the patch passed.

+1 :green_heart:
unit
0m 29s
hbase-hadoop2-compat in the patch passed.

+1 :green_heart:
unit
147m 34s
hbase-server in the patch passed.

+1 :green_heart:
unit
4m 14s
hbase-thrift in the patch passed.

184m 11s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3546/3/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 762a03d5e70a 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
branch-2.4 / cb1174e9e1

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

Max. process+thread count
4012 (vs. ulimit of 12500)

modules
C: hbase-hadoop-compat hbase-hadoop2-compat hbase-server hbase-thrift U: .

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2.4 Compile Tests _

+0 :ok:
mvndep
0m 25s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 17s
branch-2.4 passed

+1 :green_heart:
compile
5m  5s
branch-2.4 passed

+1 :green_heart:
checkstyle
2m 30s
branch-2.4 passed

+1 :green_heart:
spotbugs
4m 18s
branch-2.4 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 19s
the patch passed

+1 :green_heart:
compile
5m  2s
the patch passed

+1 :green_heart:
javac
5m  2s
the patch passed

+1 :green_heart:
checkstyle
2m 23s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
17m  5s
Patch does not cause any errors with Hadoop 2.10.0 or 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
5m  4s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 49s
The patch does not generate ASF License warnings.

58m 51s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3546/4/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile

uname
Linux 1173e11c769a 4.15.0-136-generic #140-Ubuntu SMP Thu Jan 28 05:20:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / cb1174e9e1

Default Java
AdoptOpenJDK-1.8.0_282-b08

Max. process+thread count
96 (vs. ulimit of 12500)

modules
C: hbase-hadoop-compat hbase-hadoop2-compat hbase-server hbase-thrift U: .

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

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

-0 :warning:
yetus
0m  6s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.4 Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m  4s
branch-2.4 passed

+1 :green_heart:
compile
2m 10s
branch-2.4 passed

+1 :green_heart:
shadedjars
6m 57s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 45s
branch-2.4 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 53s
the patch passed

+1 :green_heart:
compile
2m  8s
the patch passed

+1 :green_heart:
javac
2m  8s
the patch passed

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

+1 :green_heart:
javadoc
1m 41s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 26s
hbase-hadoop-compat in the patch passed.

+1 :green_heart:
unit
0m 29s
hbase-hadoop2-compat in the patch passed.

+1 :green_heart:
unit
216m  5s
hbase-server in the patch passed.

+1 :green_heart:
unit
5m  7s
hbase-thrift in the patch passed.

255m 51s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3546/4/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 64443f5fb1b7 4.15.0-147-generic #151-Ubuntu SMP Fri Jun 18 19:21:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / cb1174e9e1

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

Max. process+thread count
2426 (vs. ulimit of 12500)

modules
C: hbase-hadoop-compat hbase-hadoop2-compat hbase-server hbase-thrift U: .

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

-0 :warning:
yetus
0m  7s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.4 Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 51s
branch-2.4 passed

+1 :green_heart:
compile
2m 28s
branch-2.4 passed

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

+1 :green_heart:
javadoc
2m 12s
branch-2.4 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 18s
Maven dependency ordering for patch

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

+1 :green_heart:
compile
2m 28s
the patch passed

+1 :green_heart:
javac
2m 28s
the patch passed

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

+1 :green_heart:
javadoc
2m 10s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 27s
hbase-hadoop-compat in the patch passed.

+1 :green_heart:
unit
0m 33s
hbase-hadoop2-compat in the patch passed.

+1 :green_heart:
unit
208m  1s
hbase-server in the patch passed.

+1 :green_heart:
unit
5m 31s
hbase-thrift in the patch passed.

252m 43s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3546/4/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 13f6cb3567e4 4.15.0-128-generic #131-Ubuntu SMP Wed Dec 9 06:57:35 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / cb1174e9e1

Default Java
AdoptOpenJDK-11.0.10+9

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

Max. process+thread count
2565 (vs. ulimit of 12500)

modules
C: hbase-hadoop-compat hbase-hadoop2-compat hbase-server hbase-thrift U: .

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.


Add name, author name, explaination and list of collections to asset

Hi.
Fixes #4.
Here the small PR with the features I stated previously.
Note that I do not know whether you want the list of collection IDs or not. I think it can be useful but the description of the repo currently says collections aren't managed.
In addition, I called the description of the asset "explaination". This is to avoid the word "description", which already has another meaning in OGA.
However, if you find a better name please do use that instead.
Please run a quick test before merging.

I'm going to rename from explanation to description and authorName to author_name but otherwise this looks great.  Thanks again for contributing!

The thing is that you already use "description" to mean the whole description object.
Are you sure this will not create confusion?
(I agree explaination isn't a very good name).


Updated README; renamed push-github-token to just push-token

Current dependencies on/for this PR:

main

PR #464   👈

This comment was auto-generated by Graphite.


🤗 Integrate E2B into Hugging Face Agents

🤗 Integrate E2B into Hugging Face Agents
To see all bounties and learn everything about the bounty program, go HERE.
Description
Hugging Face is a platform for working on models, datasets, and applications. Hugging Face offers Transformers Agents, which is an experimental API.
The Hugging Face Hub is a platform with over 350k models, 75k datasets, and 150k demo apps (Spaces), all open source and publicly available, in an online platform where people can easily collaborate and build ML together.
Useful links
Each integration works differently, and it's up to you to think of the necessary steps. These resources might help you better understand Hugging Face and E2B.

Hugging Face Hub docs
E2B docs

Existing integrations
For inspiration and to understand how the integrations may work, see:

E2B Sandbox used with OpenAI Assistants API
Custom Data Analysis Sandbox for LangChain
E2B as a tool for code execution in Superagent

I'm interested in this bounty

I'm interested in this bounty

Hey @dbmanifest, thanks! Do you want to start working on the bounty immediately, or learn more first?
You can jump on our Discord server to discuss your approach or ask us questions anytime. We are also happy to schedule a call if needed.
Let me know here or on Discord, and we can confirm your starting date.

I am also interested in this can i also join please let me know

Hey @saisreesatyassss, thanks! The same comment applies, just please join our Discord server to discuss your approach or ask us questions anytime. We are also happy to schedule a call if needed.
Let me know here or on Discord, and we can confirm your starting date.
If you prefer to discuss on another channel, just let me know.
Thanks!

Yes i have joined the discord and i also messaged in e2b-discussion Let me know when u r free we can discuss about it


Option to use a different language for commit messages than UI

Feature Description
When performing actions through the web UI (Adding files, editing them or deleting them) without defining a commit message will Gitea default to a default message, which is used for the commit.
Said message is using the language you're viewing the UI in, so updating a file while using german would display <filename> aktualisiert as the commit message.
This at first may not be a big problem, but it can start to confuse people if you have your content in english, but prefer to use a different language for the UI.
This situation could confuse people who visit your repository and then see commit messages in a foreigin language they don't understand. And using a translator just to figure out that a commit means <filename> updated seems a bit much to ask for.
So, an option to set a different language than what the UI is set to should be introduced here.
By default should it be set to (Use UI language) meaning if you switch the language, the commit message language will then change too for future commits.
I would apreciate if this could be considered.
(Also, yes I am well aware that I could just put a commit message myself, but what is the purpose of these default messages then if not to safe time?)
Screenshots
No response

Seems useful. Could add a app.ini option for it:
ui.PREFILL_LANGUAGE = auto | en_US

Hi,
I was very interested in adding this enhancement, I have already taken the code and started the changes. But before finalizing the implementation I wanted to confirm a few things:

If no one has solved this issue yet and if I can.
If the solution will be the same, a new config in app.init. I think it's a simple and efficient solution.
Would it make sense for this new config to have a default value? Or if the user doesn't provide the config, does it continue using the language you're viewing the Ui?

Pretty sure no one has taken this yet.
I guess a argument could be made for this to be a per-user setting, but it'll be much harder to implement and I think it's at least initially enough to have it per-server in the ini.
I'd actually disagree with @Andre601 and lean towards having en_US as the default. I think it's generally the consensus that commit messages should be written in english, so we should not encourage non-recommended practices. Of course, still accept the auto value to restore previous behaviour.

I absolutely agree with @silverwind on 3.
I've been annoyed for years by Gitea's behavior of localizing self-created commits.

I feel like allowing the user to set the language used for commit messages when none is defined would be the better option here to have. Would allow them more freedom without having to type out every commit message themself.

Cool!!
I agree with @Andre601 this config gives more freedom and embraces different people.
During this week I'll keep working on it

Yes, per-user setting would be nice but we don't really have infrastructure for per-user settings yet except some backend functions. We should define a way that allows easy additions of such user settings.
I can accept this as a server-only setting until then as well.

Hello everyone! My name is Paul and I am looking for some 'good first ' issue to start my GitHub activity. If it is suitable for beginners can I be assigned for it?

It's better to enforce the system's commit messages in English but not have an option on app.ini.

And what exactly is the state now?
Are commit messages now english by default (if no own is set) or is it still the default which is using whatever UI language the user has set?

I think currently it will follow UI langauge if you submit commits from UI. But maybe it should be changed to English-only.


⚠ Bofrost.fr has degraded performance

In 625231f, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1348 ms

Resolved: Bofrost.fr performance has improved in 0471e30 after 9 minutes.


Add Xtreme Download Manager

Made some changes:

use msi because the jar version is outdated
remove post_install because jre is provided by msi
simplified version regex (don't make them so strict)

I recommend installing pester and running tests locally before creating a PR :smile:
And at least 5 successful installs/uninstalls of the program to test it :grin:


Feedback options not readable in dark mode.

Describe the bug
Feedback options not readable in dark mode. not readable in dark mode.
To Reproduce
Steps to reproduce the behavior

Go to 'dark mode'
Click on 'Share feedback'
See error

Expected behavior
Feedback options should be readable in dark mode.
Screenshots

Computer (please complete the following information):

Windows Version: 11
Visual Studio Version: 2022
AWS Toolkit for Visual Studio Version: latest

Thank you for bringing this to our attention

Version <IP_ADDRESS> of the Toolkit now shows these images properly in light and dark mode.


Remove nr of participants from API

The API has to be edited that it is not possible to view how many people have signed up.

We would like to use the same policy as the one used for activities on the website: Make the amount of signups available only if you are logged in, and give an indication if you're not. The last part is already done by the getActivityDetailed method's signupAvailable property. The only thing we would need to change is make the availability and signups properties of that method only available if you are logged in.

After discussion with the board, the availability property does not fall within the scope of this issue as it is only required to drop the amount of registrations, not the maximum amount of spots. Thus, the only property removed will be the signups property.


⚠ GitLab Server has degraded performance

In b76ea4d, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 6974 ms

Resolved: GitLab Server performance has improved in 6289bfa.


configure intranet access, but vite hot update fixed bearer port

the page has been repeatedly refreshed,can you add the port of judgment, just like webpack?

I'm not sure what you are want, can you explain it more detailed?

Close it for now.It will be reopen if you give a specific explain.


AWS put fails

Able to connect to AWS via SSL using these commands:
AT> AT+CIPSSLCCONF=0,0
AT? OK%n
AT<
AT< AT+CIPSSLCCONF=0,0
AT= OK
AT> AT+CIPSTART=0,"SSL","bucket.s3-us-west-2.amazonaws.com",443
AT? OK%n

However, I can't seem to get the signatures to match when I send a string like this:
sprintf(sbufferFile,"PUT /%s HTTP/1.1\r\nContent-Length: %d\r\nContent-Type: text/plain\r\nHost: bucket.s3-us-west-2.amazonaws.com\r\nX-Amz-Content-Sha256: %s\r\nX-Amz-Date: %s\r\nAuthorization: AWS4-HMAC-SHA256 Credential=%s/%s/us-west-2/s3/aws4_request, SignedHeaders=content-length;content-type;host;x-amz-content-sha256;x-amz-date, Signature=%s\r\n\r\n%s", upload_file_name, payload_len, payloadSHA256, fulltime_str, api_access, date_stamp, signature_print, payload);

The signature matches output from other tools such as python, so was wondering if this is:
a) a string formatting issue
or
b) if something to do with certificates
Was hoping someone might have some insight into how to achieve this via AT commands.

@cwq9999
https://esp32.com/viewtopic.php?f=2&t=9374

@xiewenxiang  Thank you for providing this link. Do you know if there is a way to publish directly to a s3 bucket rather than needing to use the iot route? Perhaps it all ends up in the same place, but I'm actually trying to push to digitalocean (which is bases on AWS), but I don't believe they provide the iot option as AWS does.

Probably it is a problem with port 443. AWS needs a special option during the TLS handshake called Application-Layer Protocol Negotiation Extension. With this extension Amazon can distinguish between different protocols on the same port like HTTP / MQTT ...
Here a link from Amazon:
https://docs.aws.amazon.com/iot/latest/developerguide/protocols.html
With dedicated different ports it is working but port 443 is usually better for going through firewalls etc.
Unfortunately it is not supported over AT-Commands right now (as of my knowledge). I would appreciate if Espressif would implement this feature (e.g. as an optional parameter in AT+CIPSSLCCONF param).

We have a guidance  to connect AWS using AT+MQTT, but it is in Chinese. https://blog.csdn.net/espressif/article/details/101714951

I will close this issue, if you have any question, please reopen it again.


Rooms incorrectly show red shield

Heya, for sorus dad all rooms incorrectly show the red shield, even those where every device etc. is verified.
If you go into the detailed member list view of the room, it correctly displays the green shields for every member, but the room as a whole still has a red shield. This is using 0.11.5, IOS claims there was no update.

Same on my device.


Confidential clients are not service accounts.

Based on keycloak-dev mailing list conversations, it had become clear that the GrantManager object was obtaining "Service Account" grants instead of "Direct Access Grants" when initialized as private.
Also, refactor a bunch of code to eliminate duplication.

@lance ahoy, do you think we should update the examples? Btw, if I'm not mistaken the initial implementation make use of the implicit grant flow instead of Service Account.
This is something to think together in the near future. IMO Node.js adapter should support the same flows supported by the Java adapter. Don't you think?
If yes, we can start to enumerate/prioritize the flows supported to keep the features in sync.
ps: This is not a deal breaker for this PR.

@abstractj this PR reverts the code to the previous functionality. When converting to the new KC endpoints, I mistakenly used service accounts. This just fixes that.
Agree, wrt supporting identical flows across languages. Updated docs will help me track that. :)

Landed, thank you.


Update link to license in philosophy document

Followup to aea2ed879de2ce4fee10f512c0783dba7ecf4a5b.

Looks good to me. Thanks!

Oh, and glad to see this was your first contribution! Hope to see you around some more. :)

Thanks, @RichardLitt! I appreciate the welcome. :)


Auto-calibration needs to be performed over more samples

Currently auto calibration only happens over the first 50 samples of the trace, in order to hit < 1mA accuracy we need to calibrate over a longer period of time. Somebody needs to download traces and take a look to see how long is necessary for the auto calibration.
The goal here should be to have very consistent auto calibration data for the same run in the same environment.

Implemented auto calibration over multiple flights of DMA sample buffers.


Fix obstructed diagonal movement

When moving diagonally, if there are blocks obstructing the movement, the bot will get stuck forever.
In this example, the red block is the target, the blue block is where the bot is, and the yellow blocks are obstructing the diagonal movement.

This checks if there are obstructing blocks, and moves around them.

Identified root cause, turns out this worked on versions lower than 1.18.


Missing year and copyright name

As stated in the how to apply the license these fields must be filled out.
https://www.apache.org/licenses/LICENSE-2.0#apply
https://github.com/themaplelab/swan/blob/ced08828ddea3cda6184114ac097befcbeeffdad/LICENSE.txt#L189

Fixed, thanks!


Allow destruction

What do you think about adding the possibility to allow original image destruction in spite of using clone.AsRGBA() ?
It can result in better performance.

After reviewing the changes required for this, a lot of functionality is based on the assumption that the image changes are immutable, which would make this change quite difficult to introduce into the codebase.
Will be closing the issue for now until it becomes a performance bottleneck.


EKS Log Collector - InvalidDocumentContent

What happened:
I'm trying to follow the directions here  https://github.com/awslabs/amazon-eks-ami/tree/master/log-collector-script/linux#to-invoke-ssm-agent-to-run-eks-log-collector-script-and-push-bundle-to-s3-from-worker-nodes for collecting the logs. I get the following error:
aws ssm create-document --name "EKSLogCollector" --document-type "Command" --content 'https://raw.githubusercontent.com/awslabs/amazon-eks-ami/master/log-collector-script/linux/eks-ssm-content.json'
An error occurred (InvalidDocumentContent) when calling the CreateDocument operation: JSON not well-formed. at Line: 1, Column: 6
exit status 254

Debug output here: https://gist.github.com/Chili-Man/1be262c422d929b87ccc822570553919
What you expected to happen:
I expect the command to succeed per the documentation
How to reproduce it (as minimally and precisely as possible):
aws ssm create-document --name "EKSLogCollector" --document-type "Command" --content 'https://raw.githubusercontent.com/awslabs/amazon-eks-ami/master/log-collector-script/linux/eks-ssm-content.json'

**Anything else we need to know?**:
I'm running the command in Ubuntu 20.04

```shell
aws --version
aws-cli/2.2.14 Python/3.9.5 Linux/5.8.0-63-generic source/x86_64.ubuntu.20 prompt/off

Environment:

AWS Region: us-east-1
Instance Type(s):
EKS Platform version (use aws eks describe-cluster --name <name> --query cluster.platformVersion): eks.1
Kubernetes version (use aws eks describe-cluster --name <name> --query cluster.version): 1.21
AMI Version: amazon-eks-node-1.21-v20210722 (ami-005fb2dc84caa293d)
Kernel (e.g. uname -a):  5.4.129-63.229.amzn2.x86_64 #1 SMP Tue Jul 20 21:22:08 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Release information (run cat /etc/eks/release on a node):

BASE_AMI_ID="ami-01e809b6b105324b3"
BUILD_TIME="Thu Jul 22 16:13:01 UTC 2021"
BUILD_KERNEL="5.4.129-63.229.amzn2.x86_64"
ARCH="x86_64"

This seems to be working for me:
 ➜  amazon-eks-ami git:(master) aws ssm create-document --name "EKSLogCollector" --document-type "Command" --content 'https://raw.githubusercontent.com/awslabs/amazon-eks-ami/master/log-collector-script/linux/eks-ssm-content.json'
{
    "DocumentDescription": {
        "Hash": "ee9faba0507893796ba61a4148833ea036200fd5f3720765ac8641e8fa036957",
        "HashType": "Sha256",
        "Name": "EKSLogCollector",
        "Owner": "143436755772",
        "CreatedDate":<PHONE_NUMBER>.643,
        "Status": "Creating",
        "DocumentVersion": "1",
        "Description": "EKS Log Collector",
        "Parameters": [
            {
                "Name": "bucketName",
                "Type": "String",
                "DefaultValue": "Enabled"
            }
        ],
        "PlatformTypes": [
            "Windows",
            "Linux"
        ],
        "DocumentType": "Command",
        "SchemaVersion": "2.2",
        "LatestVersion": "1",
        "DefaultVersion": "1",
        "DocumentFormat": "JSON",
        "Tags": []
    }
}

Closing this issue, please let me know if this still doesn't work for you.

I'm able to reproduce this issue on:
aws-cli/2.4.13 Python/3.8.8 Darwin/20.6.0 exe/x86_64

and
aws-cli/2.4.13 Python/3.8.8 Linux/5.4.156 exe/x86_64

It works as expected on:
aws-cli/1.22.32 Python/3.8.11 Linux/5.4.156 botocore/1.23.32

I'm considering this a documentation issue for us, because this boils down to the behavior of the --content flag for aws ssm create-document. But it'd be nice to narrow things down however much we can.

I am getting this issue while trying to collect logs for windows. Not sure if I missing something.
❯ aws --version
aws-cli/2.9.20 Python/3.9.11 Windows/10 exe/AMD64 prompt/off

❯ aws ssm create-document --name "EKSLogCollectorWindows" --document-type "Command" --content https://raw.githubusercontent.com/awslabs/amazon-eks-ami/master/log-collector-script/windows/eks-ssm-content.json

An error occurred (InvalidDocumentContent) when calling the CreateDocument operation: JSON not well-formed. at Line: 1, Column: 6


Add optional button to create an issue on a page

Like the "Edit this page" button, we could have a "Create an issue" button for a page. It could be used to create an issue for missing/wrong information.

Funny, I was meaning to do this for my own site which uses this theme (thank you!)
In my Issue I include helpful information about how Github allows this to be achieved via simpe URL's:
https://github.com/salesagility/SuiteDocs/issues/8
So it should be pretty easy for anyone with knowledge of Hugo (I'm still just starting to learn it...)


nixos/znc: add proxychains support, maintainers, password tip

Motivation for this change
Privacy. Weakly depends on #86225.
Things done

proxychains support
Added meta.maintainers
note about generating new password

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Still important. Dependent PR merged, this one rebased.

cc @Infinisil


Memory Optimized Temporal table needs NONCLUSTERED

Needed to be a NONCLUSTERED index for the Primary Key.

@dbaduck : Thanks for your contribution! The author, @edmacauley, has been notified to review your proposed change.

Thanks @dbaduck for catching that and making the edit.  #sign-off


Add JDK 11 support

Fixes #271.
Changes in this pull request:

Adds openjdk11 in Travis build matrix.
Rewrites the deprecated klass.newInstance() with klass.getDeclaredConstructor().newInstance()
Adds the jaxb dependencies which had been removed from JDK since JDK 9.
Updates aws-sdk and sbt-assembly to support JDK 11.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@pauljamescleary
Because Java EE-related modules, including JAXB, had been deprecated and removed starting from JDK 9.
This blog may help.
https://jaxenter.com/jdk-11-java-ee-modules-140674.html

@exoego goodness, thanks for that article.  That is kind of insane that they did that

Looks like travis is having problems.  Version conflict in jaxb?

Thank you.
I will open PR for that.

;validate;verify worked for me on my local


Odd Flow Direction during STEPS nowcast

I am trying to nowcast using the STEPS forecast method with the following details:
nwc_method = "steps"
oflow_method = "lucaskanade"
adv_method = "semilagrangian"
noise_method = "parametric"
bandpass_filter = "gaussian"
decomp_method = "fft"

It usually yields pretty good results but it has predicted an odd forecast for a case of mine. I am attaching the observations (input) and the forecasts (output) as video but I can surely provide the raw files as well.
Observations

Forecasts (Nowcasts)

I wasn't able to figure out why the nowcasts are pointing to a south-based flow when the observations have a clear north-east based flow. I am not really an expert on the domain so please feel free to close the issue if this is an user-error.
Thanks!

I believe this is because of limitations in the Lucas-Kanade method (and optical flow in general). There is growth of new precipitation especially in the lower part of your domain. In such cases the advection velocities cannot be reliably determined. Have you tested with other optical flow methods?

Oh, I see! I figured the new precipitation fields would be the source of the issue. In that case, I can try zooming in a bit more to make sure that I run the nowcast on a smaller, more focused area.
@pulkkins Which optical flow method would you recommend for this case?

You can try the Proesmans method. It gives a quality measure for the advection velocities based on forward-backward consistency. Based on the consistency, you can replace unreliable advection velocities by interpolation from those that are known to be reliable.

Hello @5fcgdaeb
On top of what @pulkkins already suggested, I'd like to say that LK is quite sensitive to the motion of the precipitation mask itself, that is, the limit between precipitation and non-precipitation. This is because the dry/wet transition is very sharp, meaning that the gradient is high, which is the criterion used by the Shi-Tomasi feature detection algorithm to define a good feature to track.
In your case, this might explain the resulting motion field. The overall motion of precipitation is north-west, but the precipitation mask somewhat appears to move south (also because of the growth of new precipitation areas).
With LK, you can try to account for that in some ways (but such cases remain quite challenging for all motion fields):

Try to minimize the dry/wet discontinuity of your transformed field.

If transforming to reflectivity, make sure that the value assigned to dry pixels (zerovalue) is as close as possible to the value of your lowest wet pixels (threshold).
Try a different transformation, such as sqrt_transform.
Set all dry pixels to nan and pass a positive buffer_mask argument with the fd_kwargs argument. This will prevent the feature detection algorithm to use the dry/wet discontinuity as tracking feature.

Improve the feature detection algorithm

The default parameters might not be appropriate for your data
Try the blob detection which instead should focus on the actual maxima in your field (or implement a new one that is better suited to your case).

Remember that you can always check the result of the sparse tracking algorithm before interpolation, see this example:
https://pysteps.readthedocs.io/en/latest/auto_examples/LK_buffer_mask.html#sphx-glr-auto-examples-lk-buffer-mask-py
This should help identify the cause of the problem.
Finally, you can compare the estimation from LK with more advanced optical flow methods such as Proesmans, as @pulkkins already suggested, but also VET would probably be a good reference.
Hope this helps!

This is excellent @dnerini, thanks! It gives so much insight into how the nowcasts are generated. I will now take a closer look at the examples gallery with this in mind.
I think we can close this issue, I do know where to look and what to do in case I see such odd flows/results.
Thanks everyone, really appreciated.


Dphan/update to cpp17

https://github.com/apigear-io/internal-issue-tracker/issues/12

Closes #
📑 Description

✅ Checks

[ ] My pull request adheres to the code style of this project
[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required
[ ] All the tests have passed

ℹ Additional Information

PR was open to cpp14 template and should be on cpp 17, moved here:
https://github.com/apigear-io/template-cpp17/pull/4


pomoplus: new setting and minor changes

see https://notevil.github.io/BangleApps/?q=pomoplus

adds setting "Show clock"

If set, returns to clock (Bangle.showClock()) after start/resume.

minor changes

(changed*) buzz pattern of long break
added g.clear() and adjusted .clearRect in drawTimerAndMessage
replaced g.getWidth() and g.getHeight() with w and h

@bruceblore is this in conflict with your vision for this app?
*nothing changed since atm the last buzz immediately follows the second one

No conflict with my vision. I think that's a good feature to have, and people who do not like it can just turn it off. And I appreciate the code quality improvements.

Looks good to me! Thanks for the link to try it out.
I guess a nice addition at some point might be to try and use the sched library to schedule the timer (rather than boot code?). Having less boot code means app switching is a bit faster :)


Work around Travis "virtual memory exhausted" error

This is a trial build to see if this fixes the "virtual memory exhausted" error

Rebased and taken out of WIP now that #3600 has gone in. This works by adding "--debug" to the build that runs out of virtual memory compiling curve25519.c. This has the effect of forcing -O0 which is much less memory intensive than -O3.

Pushed. Thanks.

should we update the FAQ or something?  Or are people not going to run into this?

should we update the FAQ or something? Or are people not going to run into this?

Let's wait until people do. I'm not sure how much of this is just because of the environment that travis is running in. In any case the solution here (reduce the optimisation level), is likely not suitable for others.


Remove version: ChilliBits.Spice version 0.17.4

This version is older than what has been set in max-versions-to-keep by the publisher.
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/spicelang/spice/releases/download/0.17.4/spice_x64_setup.msi
Status Code: 200
(Automated message - build 857)


Project-wide Checkstyle Config

Motivation
Checkstyle allows us to enforce project norms and safe coding practices.
Modifications
Add project-wide checkstyle config to root pom.xml, add buildtools project to house config. The config is taken from bookkeeper as a starting point.

OOF, I messed this up, I had meant to just add the config and the managed-ledger changes in a separate PR. Let me fix this.

@sijie fixed the comment on naming and restricted the changes to just adding the checkstyle config and infrastructure. Once this is merged I will submit the PR for the managed-ledger changes.

@mgodave Change LGTM. Will this start enforcing the style on new PRs or will need to be enabled module by module after fixing them?

Enabled module by module as they are fixed.
On Feb 1, 2018 11:58, "Matteo Merli"<EMAIL_ADDRESS>wrote:

Assigned #1162 https://github.com/apache/incubator-pulsar/pull/1162 to
@mgodave https://github.com/mgodave.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-pulsar/pull/1162#event-1453650704,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAh9Fvysa6OMEem4dQJEdVG98ogLOfJ3ks5tQglCgaJpZM4R0y09
.


It does not use msbuild from mono, but dotnet msbuild

OS: Mac
I have mono(installed from Visual Studio for Mac) and  dotnet-cli co-exist in my macOS. My project required to use .NET framework 461. When I open vscode, the F# Project explorer always marks my .fsproject (load failed). It also build failed when I use Command "MSBuild: Build Project". Then I run Command "MSBuild: Switch host type" to use mono msbuild, output:
MSBuild (.NET) activated

It built success
However, no matter what I have selected, the Project Explorer, on the left hand side, still using dotnet msbuild to build my project, with the result "(load failed)".
Error
Error:
MSBuild failed with exitCode 1 Working Directory: 'somewhere' Exe Path: 'dotnet' Args: 'msbuild somewhere/someproject.fsproj ....'

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net461</TargetFramework>
  </PropertyGroup>
  <ItemGroup>
    <Compile Include="Program.fs" />
  </ItemGroup>
  <ItemGroup>
    ...
  </ItemGroup>
  <ItemGroup>
    <Reference Include="System.Configuration" />
  </ItemGroup>
</Project>

I tried to add the following to my workspace setting .vscode/settings.json
{
    "FSharp.msbuildHost": ".net"
}

no effect to the Project Explorer (load failed), but good at Command "MSBuild: Build Project".
Thanks

Hi @kkpoon
Atm this is a limitation of the FSAC (the language service) who parse the fsproj, who use dotnet executable (running dotnet msbuild)
The parsing fails, because dotnet cli doesnt known where the mono references assemblies are (see below), so dotnet build will fail, and project parsing too.
the FSharp.msbuildHost setting is used only to choose what use when you do Build like commands, not yet for project parsing
As workaround, dotnet cli can  build projects targeting .net (llike net461), you just need to know where reference assemblies are (the assemblies of .net framework 4.6.1 installed in mono).
Yo can use this workaround https://github.com/dotnet/netcorecli-fsc/wiki/.NET-Core-SDK-1.0#using-net-framework-as-targets-framework-the-osxunix-build-fails
You can add that for your user, so will work opening new terminal and code
After that, doing dotnet build will work from command line too, and project parsing will work correctly in code
Closing because is tracked in https://github.com/fsharp/FsAutoComplete/issues/213 and there is a workaround
@kkpoon any issue with workaround, feel free to reopen this.


ARROW-11325: [Packaging][C#] Release Apache.Arrow.Flight and Apache.Arrow.Flight.AspNetCore

@github-actions crossbow submit nuget

@github-actions crossbow submit nuget

+1

+1


ConCom Structure - control department emails

when double clicking on department names in the admin-concom structure section, we should be able to edit the department emails (and aliases, if any).  Especially useful for department name changes.

Ah!  indeed it is!  Just in a newer version than is in production!  Disregard! )


proxy authentication does not work on 1.49

Issue Type: Bug
When I start VScode 1.49, proxy authentication window seems to popped up, but immediately closed.
Thus, updating any extensions are failed.
VS Code version: Code 1.49.0 (e790b931385d72cf5669fcefc51cdf65990efa5d, 2020-09-10T13:22:08.892Z)
OS version: Windows_NT x64 6.3.9600
Remote OS version: Linux x64 4.18.0-193.14.2.el8_2.x86_64

Confirm, my proxy auth dialog dissappear at VS start.

Sorry about this! can confirm the bug, sadly this is third time in the last few releases that proxy dialog was broken. @chrmarti we should add this to the smoke test list.
There was no change to the proxy code path in the past month, seems like this one broke with electron update. Trying to create a minimal repro now.

Created a minimal sample based on our implementation https://gist.github.com/deepak1556/c478da04a57addd17894f8c93844664b , running it with 9.2.1 in electron fiddle https://www.electronjs.org/fiddle doesn't repro the issue.
@chrmarti seems like this is not an issue with electron.

@deepak1556 checking the history of auth.ts I see that only the revert of Electron 9 appears:
https://github.com/microsoft/vscode/commit/227d533937b17f54bae09f94083bf6304e6262e1#diff-f4a449c54f8cff44ffedcbdf9ea0b2dd
But it looks like the revert of the revert (going back to Electron 9) did not happen for auth.ts? As such, for example this change did not make it back:
https://github.com/microsoft/vscode/commit/227d533937b17f54bae09f94083bf6304e6262e1#diff-f4a449c54f8cff44ffedcbdf9ea0b2dd
I think all of the spellcheck changes I did before did not make it back, any reason for this?

I think all of the spellcheck changes I did before did not make it back, any reason for this?

Yeah just noticed it, no reason, I seemed to have missed it with my revert.

checking the history of auth.ts I see that only the revert of Electron 9 appears:

yeah and it doesn't make any change apart from the spellcheck config which won't affect this issue. Don't see any other change in history related to auth code.

@deepak1556 I see the IPC listener being called with channel === 'vscode:fetchShellEnv': https://github.com/microsoft/vscode/blob/e790b931385d72cf5669fcefc51cdf65990efa5d/src/vs/code/electron-main/auth.ts#L91
Should these two lines move within the if block?
win.removeListener('close', onWindowClose);
win.close();

Not sure why this broke now, maybe this has also previously been a race condition that just now happens to hit more often.
@joaomoreno I suggest to queue this for a recovery release. Could take over as the owner of the code?

I may have broken this with my sandbox work where now the preload script will call this IPC message, but agree the fix to move this into an if block seems legit 👍

I'll let @deepak1556 tackle it. 👌

I can approve a PR.

Or I can fix :) https://github.com/microsoft/vscode/pull/106490

Thanks @chrmarti for narrowing down the issue!
@bpasero follow-up question, why is the ipc for vscode:fetchShellEnv being sent for proxy auth window ? I only see that whenResolved is waited for the workbench window which would be a different process from the auth window https://github.com/microsoft/vscode/blob/07ad5d6f18d91a365d6fa3faa2c2e05c590dc40f/src/vs/code/electron-browser/workbench/workbench.js#L55

There are many time vscode fail with proxy network. Could you please test it before release?
If an user cannot connect to proxy network. How do he update vscode? How do he know there is a fix?

Guys, it has been 3 times in a row. Can you at least add this in one your test cases? This bug has no impact for personal use and small businesses but it is catastrophic for cooperation use.

Sorry for that, I added this to https://github.com/microsoft/vscode/issues/106489

Verified. @joaomoreno @deepak1556 I see the auth dialog twice, it seems there are two 'login' events from Electron for the same proxy. Is that a known issue?

I always see the authentication dialogue twice.
I've hear that VSCode have two HTTP engine in the past, thus I thought this could be normal behaviour.
If this is not expected behaviour, fixing this is happy to me.

Verified. @joaomoreno @deepak1556 I see the auth dialog twice, it seems there are two 'login' events from Electron for the same proxy. Is that a known issue?

For me it also so - dialog showing twice, as also credentials needed to be entered twice.

About showing twice proxy dialog, with the latest updated, I have checked and it shows only one time.
Could you check it?
@shkit @shamarin

About showing twice proxy dialog, with the latest updated, I have checked and it shows only one time.
Could you check it?
@shkit @shamarin

Will check it.

About showing twice proxy dialog, with the latest updated, I have checked and it shows only one time.
Could you check it?
@shkit @shamarin

Checked, it's showing twice.

@quyleanh I also see twice.

We will look into that issue as part of https://github.com/microsoft/vscode/issues/106489 as well.

We will look into that issue as part of #106489 as well.

Ok, thank you! And what about an option to store credentials so that there will be no need to enter them again after programm restart?

Yeah that might be possible too, will add it to the list.

Yeah that might be possible too, will add it to the list.

Great!

Please refer to #32566. It has been more than 3 years.

Version 1.49.1 fixed this for me. And then 1.49.2 promptly broke it again!


hello-dapr-slim sample: Missing data file for curl example call

Add missing file sample.json to enable curl example request.
fixes #105

Closing issue


Enhance Pinot streaming consumer interface

Description
This PR is related to the issue #7988. We are expanding the Pinot's realtime consumer interface to accommodate other (non-kafka) streaming systems.
Changes introduced:

2 new apis in PartitionGroupConsumer  - start and checkpoint. These APIs are backward-compatible with existing consumer plugins.
some minor code/comment clean-up

Codecov Report

Merging #8047 (fe13ba1) into master (d317c59) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master    #8047      +/-   ##
============================================
+ Coverage     71.35%   71.38%   +0.02%
+ Complexity     4264     4261       -3
============================================
  Files          1599     1600       +1
  Lines         83075    83080       +5
  Branches      12402    12402
============================================
+ Hits          59282    59304      +22
+ Misses        19788    19762      -26
- Partials       4005     4014       +9

Flag
Coverage Δ

integration1
29.04% <75.00%> (+0.03%)
:arrow_up:

integration2
27.70% <75.00%> (-0.04%)
:arrow_down:

unittests1
68.14% <100.00%> (-0.05%)
:arrow_down:

unittests2
14.36% <0.00%> (+0.02%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...manager/realtime/LLRealtimeSegmentDataManager.java
70.45% <100.00%> (+0.24%)
:arrow_up:

...pache/pinot/spi/stream/PartitionGroupConsumer.java
100.00% <100.00%> (ø)

...va/org/apache/pinot/spi/utils/CommonConstants.java
23.63% <100.00%> (ø)

...ller/helix/core/minion/TaskTypeMetricsUpdater.java
80.00% <0.00%> (-20.00%)
:arrow_down:

...nt/local/startree/v2/store/StarTreeDataSource.java
40.00% <0.00%> (-13.34%)
:arrow_down:

...ot/segment/local/startree/OffHeapStarTreeNode.java
72.22% <0.00%> (-5.56%)
:arrow_down:

...he/pinot/segment/local/segment/store/IndexKey.java
70.00% <0.00%> (-5.00%)
:arrow_down:

...l/segment/index/readers/OnHeapFloatDictionary.java
90.00% <0.00%> (-5.00%)
:arrow_down:

...core/startree/operator/StarTreeFilterOperator.java
86.71% <0.00%> (-4.20%)
:arrow_down:

...pinot/core/query/request/context/TimerContext.java
91.66% <0.00%> (-4.17%)
:arrow_down:

... and 24 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 d317c59...fe13ba1. Read the comment docs.

Please hold off merging until the conversation is resolved ,thanks


expose bridge.dispatchBlock as public method

https://github.com/facebook/react-native/blob/403f3560826a2c121d225a527c1cdc07c90a571f/React/Base/RCTBridge%2BPrivate.h#L109
this should be in Bridge public interface IMO.
there are usecase where you want to execute things in the JS thread and this bridge.dispatchBlock allows it.
I'm porting code (gl-react-native) that used to do executor executeBlockOnJavaScriptQueue but since the javaScriptExecutor is no longer exposed I have found this alternative dispatchBlock – however I currently need to #import "RCTBridge+Private.h" which I guess is bad

(if you think this is correct usecase I can provide a PR for this)

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!
If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.


[fix] Re-cleanup legacy filters

CATEGORY
Choose one

[x] Bug Fix
[ ] Enhancement (new features, refinement)
[ ] Refactor
[ ] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY
Whilst spelunking through our production data in preparation to migrate slices from the Druid native JSON-based API to SQLAlchemy I discovered that a non-trivial amount of slices (~ 10%) still contained the legacy filter fields in the form-data; filters, having, having_filters, and where in addition to adhoc_filters (which takes precedence). Though these fields are not problematic it adds cruft to the form-data and makes analyses unnecessarily more complex.
These fields should have been removed in this migration (the convert_legacy_filters_into_adhoc method deletes the old fields) and after trying several flows I wasn't able to determine how these fields were persisting (note loading/saving a slice with legacy filters will replace them with ad-hoc).
This PR performs the following:

Re-applies the previous migration logic. The hypothesis is that maybe when the previous migration was run the code was in a state where these fields persisted.
Updates the example data to remove the obsolete fields and updates the filters to be ad-hoc.

TEST PLAN
Ran the DB upgrade on a dump of our production data and verified that the legacy filters were no longer present in the form-data.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[x] Requires DB Migration.
[x] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

REVIEWERS
to: @betodealmeida  @graceguo-supercat @michellethomas @mistercrunch @villebro

@etr2460 I addressed your comments.

@etr2460 the last migration is defined by this commit which is the defined down revision for the migration in this PR.

ignore me, this looks good

Codecov Report

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

@@           Coverage Diff           @@
##           master    #8523   +/-   ##
=======================================
  Coverage   66.82%   66.82%
=======================================
  Files         450      450
  Lines       22721    22721
  Branches     2366     2366
=======================================
  Hits        15183    15183
  Misses       7400     7400
  Partials      138      138

Impacted Files
Coverage Δ

superset/examples/random_time_series.py
20% <ø> (ø)
:arrow_up:

superset/examples/country_map.py
24.32% <ø> (ø)
:arrow_up:

superset/examples/birth_names.py
100% <ø> (ø)
:arrow_up:

superset/examples/multiformat_time_series.py
15.38% <ø> (ø)
:arrow_up:

superset/examples/deck.py
11.11% <ø> (ø)
:arrow_up:

superset/examples/long_lat.py
23.07% <ø> (ø)
:arrow_up:

superset/examples/energy.py
100% <ø> (ø)
:arrow_up:

superset/examples/unicode_test_data.py
100% <ø> (ø)
:arrow_up:

superset/examples/world_bank.py
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Alternate reducer composition (Docs)

It seems likely that most people will have an app reducer already combined at the point at which the store is created, having imported their top-level precombined reducer.
Happy to reformulate this into an alternate section as opposed to a comment or whatever you suggest. I think the current example will likely lead people to introducing an extra level into their reducers that they did not want.

Actually, this wont work, I'll have a rethink.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #193   +/-   ##
=======================================
  Coverage   99.06%   99.06%
=======================================
  Files          19       19
  Lines         215      215
=======================================
  Hits          213      213
  Misses          2        2

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 4dacfe8...d52734c. Read the comment docs.


Css background images not working

Challenge Name

Issue Description

I've tried a number of external image providers such as postimage.org and cloudinary.com but when I use the following css code, there is no background property added to the html output, seen when I inspect the element in chrome.
Example Pen:
http://codepen.io/rocifier/pen/pepjaK
Browser Information

Chrome 56.0.2924.87 (64-bit)
Windows 10 and Windows 7
Your Code

#banner{
  width:300px;
  height:300px;
  background：url("http://res.cloudinary.com/dxvvzbawu/image/upload/v1489794718/star--background-seamless-repeating5_p28xxy.jpg");
}

Screenshot

Capture.png

Thank you for reporting the issue.
This is not a freeCodeCamp issue, so this is why I am closing this one.
Good luck and happy coding!


Great Expectations Fail

This isn't necessarily a bug. But in Validation.py. Line 136. If Great Expectations fail it would be preferable not to raise an error and have the whole prefect flow fail. It would be better just to warn that it failed and comment out the raising_on_validation_failure. So that I know the flow is fine but I can print out some results.

if not result.success:
        logger.warn(
            "Great Expectations validation run %s failed", result.run_id.run_name
        )
        if raise_on_validation_failure:
            raise GreatExpectationValidationError(result)
    else:
        logger.info(
            "Great Expectations validation run %s succeeded", result.run_id.run_name
        )

Hey @tbabin02! raise_on_validation defaults to True, but you can pass in False so that your task doesn't raise an exception if the validation fails. It sounds like the task already supports the behavior that you're looking for, but feel free to let me know if I've misunderstood your request.

Oh thank you, nope that solves my problem! Did not notice that.


Burrow Support

Signed-off-by: greg<EMAIL_ADDRESS>Provides basic Hyperledger Burrow support for Caliper based on the official (Alpha) JavaScript API. This PR includes a basic two node network and support for transactional based tests.
Installation: npm i<EMAIL_ADDRESS>

Thanks for your contribution.   I left some minor comments under your code. And here are some eslint errors/warnings existing. Would you please run the linting to check the code style and correct any possible eslint errors/warnings?

Great! I'll write up the documentation this week (I presume just on the gh-pages branch), and hopefully we can review the smart contracting integration over the next few weeks.


Option to add 'end' to if..then and functions

Right now, this works great with:
for ... do
A carraige return gives an automatic
end
Would like this for if.. then and function()

I have tried to implement this feature, but unfortunately, the current LSP interface does not seem to be able to complete this feature (it is also possible that I did not find the correct method).
See https://github.com/microsoft/language-server-protocol/issues/1214

Done


Support other slots

I really like the functionality of this commit, but I will not merge because the purpose of fishhook as a whole is to be able to generate offsets and addresses dynamically. This commit uses several hardcoded offsets that will fail on different build settings of python. If you can develop a way to generate them dynamically I will merge the functionality

Closing since 0.2.1 adds force_setattr that enables more slots