jupyter updates 2024-09-01

Description of changes

Things done

Built on platform(s)

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

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

[x] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 338730 at 7c038690 run on x86_64-linux 1

9 packages marked as broken and skipped:

python311Packages.bambi
python311Packages.cirq
python311Packages.distrax
python311Packages.elegy
python311Packages.jupyter-contrib-nbextensions
python311Packages.rlax
python311Packages.treex
python312Packages.cirq
python312Packages.jupyter-contrib-nbextensions

25 packages failed to build:

cantor
labplot
python311Packages.ansible-kernel
python311Packages.cirq-ft
python311Packages.layoutparser
python311Packages.llama-index
python311Packages.llama-index-cli
python311Packages.llama-index-vector-stores-chroma
python311Packages.orange3
python311Packages.pdfplumber
python311Packages.private-gpt
python311Packages.spyder
python312Packages.ansible-kernel
python312Packages.cirq-ft
python312Packages.coffea
python312Packages.layoutparser
python312Packages.nbconflux
python312Packages.orange3
python312Packages.pdfplumber
spyder (python312Packages.spyder)
python312Packages.vector
sage
sageWithDoc
whisper-ctranslate2
wolfram-notebook

269 packages built successfully:

aider-chat
ihaskell
inkcut
inkscape-extensions.inkcut
jupyter
jupyter-all
manim (python312Packages.manim)
manim-slides
marimo (python312Packages.marimo)
napari (python312Packages.napari)
nbqa
nitrokey-app2
pynitrokey (python312Packages.pynitrokey)
python311Packages.altair
python311Packages.anywidget
python311Packages.arviz
python311Packages.atomman
python311Packages.augmax
python311Packages.ax-platform
python311Packages.batchspawner
python311Packages.bayesian-optimization
python311Packages.bqplot
python311Packages.bqscales
python311Packages.calysto
python311Packages.coffea
python311Packages.corner
python311Packages.cufflinks
python311Packages.dalle-mini
python311Packages.datashader
python311Packages.dm-haiku
python311Packages.dockerspawner
python311Packages.einops
python311Packages.encodec
python311Packages.evosax
python311Packages.experiment-utilities
python311Packages.fastai
python311Packages.flax
python311Packages.flowmc
python311Packages.folium
python311Packages.gradio
python311Packages.ipycanvas
python311Packages.ipydatawidgets
python311Packages.ipympl
python311Packages.ipyniivue
python311Packages.ipytablewidgets
python311Packages.ipyvue
python311Packages.ipyvuetify
python311Packages.ipywidgets
python311Packages.jupysql
python311Packages.jupysql-plugin
python311Packages.jupyter
python311Packages.jupyter-book
python311Packages.jupyter-collaboration
python311Packages.jupyter-contrib-core
python311Packages.jupyter-lsp
python311Packages.jupyter-nbextensions-configurator
python311Packages.jupyter-server
python311Packages.jupyter-server-fileid
python311Packages.jupyter-server-mathjax
python311Packages.jupyter-sphinx
python311Packages.jupyterhub
python311Packages.jupyterhub-ldapauthenticator
python311Packages.jupyterhub-systemdspawner
python311Packages.jupyterhub-tmpauthenticator
python311Packages.jupyterlab
python311Packages.jupyterlab-execute-time
python311Packages.jupyterlab-git
python311Packages.jupyterlab-lsp
python311Packages.jupyterlab-server
python311Packages.jupyterlab-widgets
python311Packages.jupytext
python311Packages.k-diffusion
python311Packages.kmapper
python311Packages.labelbox
python311Packages.lightparam
python311Packages.livelossplot
python311Packages.llama-index-agent-openai
python311Packages.llama-index-core
python311Packages.llama-index-embeddings-gemini
python311Packages.llama-index-embeddings-google
python311Packages.llama-index-embeddings-huggingface
python311Packages.llama-index-embeddings-ollama
python311Packages.llama-index-embeddings-openai
python311Packages.llama-index-graph-stores-nebula
python311Packages.llama-index-graph-stores-neo4j
python311Packages.llama-index-graph-stores-neptune
python311Packages.llama-index-indices-managed-llama-cloud
python311Packages.llama-index-legacy
python311Packages.llama-index-llms-ollama
python311Packages.llama-index-llms-openai
python311Packages.llama-index-llms-openai-like
python311Packages.llama-index-multi-modal-llms-openai
python311Packages.llama-index-program-openai
python311Packages.llama-index-question-gen-openai
python311Packages.llama-index-readers-database
python311Packages.llama-index-readers-file
python311Packages.llama-index-readers-json
python311Packages.llama-index-readers-llama-parse
python311Packages.llama-index-readers-s3
python311Packages.llama-index-readers-twitter
python311Packages.llama-index-readers-txtai
python311Packages.llama-index-readers-weather
python311Packages.llama-index-vector-stores-google
python311Packages.llama-index-vector-stores-postgres
python311Packages.llama-index-vector-stores-qdrant
python311Packages.llama-parse
python311Packages.manim
python311Packages.manim-slides
python311Packages.marimo
python311Packages.memestra
python311Packages.mkdocs-jupyter
python311Packages.napari
python311Packages.napari-console
python311Packages.nbclassic
python311Packages.nbconflux
python311Packages.nbconvert
python311Packages.nbdev
python311Packages.nbdime
python311Packages.nbexec
python311Packages.nbsmoke
python311Packages.nbsphinx
python311Packages.nikola
python311Packages.nix-kernel
python311Packages.notebook
python311Packages.notebook-shim
python311Packages.notedown
python311Packages.oauthenticator
python311Packages.osmnx
python311Packages.ploomber-extension
python311Packages.potentials
python311Packages.pweave
python311Packages.pyannote-audio
python311Packages.pydeck
python311Packages.pyls-memestra
python311Packages.pymc
python311Packages.pymoo
python311Packages.pynitrokey
python311Packages.pytest-notebook
python311Packages.pyzx
python311Packages.qcodes
python311Packages.qcodes-contrib-drivers
python311Packages.qgrid
python311Packages.qtconsole
python311Packages.rotary-embedding-torch
python311Packages.scikit-tda
python311Packages.skops
python311Packages.spacy
python311Packages.spacy-loggers
python311Packages.spacy-lookups-data
python311Packages.spacy-transformers
python311Packages.spsdk
python311Packages.spyder-kernels
python311Packages.streamlit
python311Packages.stytra
python311Packages.textacy
python311Packages.textnets
python311Packages.thinc
python311Packages.tsfresh
python311Packages.unidic
python311Packages.unstructured-api-tools
python311Packages.vector
python311Packages.vega
python311Packages.vqgan-jax
python311Packages.wasabi
python311Packages.weasel
python311Packages.widgetsnbextension
python311Packages.xarray-einstats
python312Packages.altair
python312Packages.anywidget
python312Packages.arviz
python312Packages.atomman
python312Packages.augmax
python312Packages.ax-platform
python312Packages.batchspawner
python312Packages.bayesian-optimization
python312Packages.bqplot
python312Packages.bqscales
python312Packages.calysto
python312Packages.corner
python312Packages.cufflinks
python312Packages.dockerspawner
python312Packages.einops
python312Packages.experiment-utilities
python312Packages.folium
python312Packages.gradio
python312Packages.ipycanvas
python312Packages.ipydatawidgets
python312Packages.ipympl
python312Packages.ipyniivue
python312Packages.ipytablewidgets
python312Packages.ipyvue
python312Packages.ipyvuetify
python312Packages.ipywidgets
python312Packages.jupysql-plugin
python312Packages.jupyter
python312Packages.jupyter-book
python312Packages.jupyter-collaboration
python312Packages.jupyter-contrib-core
python312Packages.jupyter-lsp
python312Packages.jupyter-nbextensions-configurator
python312Packages.jupyter-server
python312Packages.jupyter-server-fileid
python312Packages.jupyter-server-mathjax
python312Packages.jupyter-sphinx
python312Packages.jupyterhub
python312Packages.jupyterhub-ldapauthenticator
python312Packages.jupyterhub-systemdspawner
python312Packages.jupyterhub-tmpauthenticator
python312Packages.jupyterlab
python312Packages.jupyterlab-execute-time
python312Packages.jupyterlab-git
python312Packages.jupyterlab-lsp
python312Packages.jupyterlab-server
python312Packages.jupyterlab-widgets
python312Packages.jupytext
python312Packages.kmapper
python312Packages.labelbox
python312Packages.lightparam
python312Packages.livelossplot
python312Packages.manim-slides
python312Packages.memestra
python312Packages.mkdocs-jupyter
python312Packages.napari-console
python312Packages.nbclassic
python312Packages.nbconvert
python312Packages.nbdev
python312Packages.nbdime
python312Packages.nbexec
python312Packages.nbsphinx
python312Packages.nikola
python312Packages.nix-kernel
python312Packages.notebook
python312Packages.notebook-shim
python312Packages.notedown
python312Packages.oauthenticator
python312Packages.osmnx
python312Packages.ploomber-extension
python312Packages.potentials
python312Packages.pweave
python312Packages.pyannote-audio
python312Packages.pydeck
python312Packages.pyls-memestra
python312Packages.pymoo
python312Packages.pytest-notebook
python312Packages.pyzx
python312Packages.qcodes
python312Packages.qcodes-contrib-drivers
python312Packages.qgrid
python312Packages.qtconsole
python312Packages.rotary-embedding-torch
python312Packages.scikit-tda
python312Packages.skops
python312Packages.spsdk
python312Packages.spyder-kernels
streamlit (python312Packages.streamlit)
python312Packages.stytra
python312Packages.thinc
python312Packages.unidic
python312Packages.unstructured-api-tools
python312Packages.vega
python312Packages.wasabi
python312Packages.weasel
python312Packages.widgetsnbextension
python312Packages.xarray-einstats
quarto
rstudio
rstudio-server
rstudioServerWrapper
rstudioWrapper

@ofborg build spyder
Fails to build for me, nixos x86_64
Otherwise nixpkgs-review reveals no other new failures for me, macos 12 x86_^4 & nixos x86_64

regarding spyder
Checking runtime dependencies for spyder-5.5.6-py3-none-any.whl - qtconsole<5.6.0,>=5.5.1 not satisfied by version 5.6.0 - spyder-kernels<2.6.0,>=2.5.2 not satisfied by version 3.0.0

I'll check tomorrow.

It looks like spyder will support qtconsole >= 5.6 and spyder-kernel >= 3 in the next major release.
I will remove those updates from this PR.

 It also needs a patch to replace SafeConfigParser with ConfigParser
rtree fails with in finder.py OSError: Could not load libspatialindex_c library. This smells like a darwin-specific issue.
In skops, skops/io/tests/test_persist.py segfaults.
arviz fails in the setup for the pytestCheckHook
qcodes-contrib-drivers test test_stability_diagram_external fails due to a rounding difference (       > E         At index 5 diff: 'sour6:volt 0.26599999999999996' != 'sour6:volt 0.266'
In pdf-plumber, test_annots and test_annots_rotated fail with TypeError: 'PDFObjRef' object is not iterable
jupysql testing also breaks as arviz does: pytest-check-hook/nix-support/setup-hook: line 53: 19111 Trace/BPT trap: 5
In awkward, test_serialise_with_nonserialisable_attrs fails with a Regex mismatch.
And faiss fails to build due to two undeclared identifiers.

I hope this distillation is useful.

There doesn't seem to be any regression caused by this update, so I'll merge it.
I'll fix these packages in another PR.

@natsukium I made some edits to my list, making it much shorter and easier to fix.


Fixed Select components initial state.

Please check if the PR fulfills these requirements:

[x] After these changes, the app was run and still works as expected
[ ] Tests for these changes were added (if applicable)
[x] All existing unit tests were run and still pass

Please specify the type of change this PR introduces (Bug fix, feature addition, content update, chore, etc.):
Additional Notes:

The issue was because the <select> element didn't use a v-model, it wouldn't bind the initial null value to the default option. And then there was an issue when selecting a valid option and then selecting the empty option, the empty option wasn't be selected. For some reason it use the option label value instead of the null value. That's why there's the additional logic in the change handler. This might only apply to <select> elements, but it could be worth double checking.


Sanitize tags values

We are unable at the moment to collects stats for sidekiq workers nested under ruby modules, because they have :: in their names.
2017-09-28T10:52:40Z E! Error: splitting '|', Unable to parse metric: smartly.pena.sidekiq.perform,worker=Priceline::PriceQueryWorker:426|ms
2017-09-28T10:52:40Z E! Error: splitting '|', Unable to parse metric: smartly.pena.price_query_worker_performed,product_catalog=#<ProductCatalog:0x00007efcc005a2d0>,type=Priceline:1|c

https://www.flowdock.com/app/smartly/dpa/threads/2FEOep9UfMMNhsgTirszLRQ9NvJ

Is there a reason you closed your pull request?

It was created by accident, and wasn't meant to be merged into main statsd repo.


SCIM2 test case for provisioning a user with insufficient permission

Purpose
This test case validates for permission when attempting to provision a user
Tested environments
1.Ubuntu18.04
2.Java: 1.8.0_161
3.Identity Server fresh pack with embedded ldap
Test case
1.The test case initially provisions a user(ex:scim2user) by a user with admin credentials and then we try to create a second user by using scim2user who does not have adequate permissions. We assert for SC_FORBIDDEN status code

closing this PR will be sending this with another PR


Create a Unit Test mechanism for each vulnerability

Currently, we have an integration test that allows us to run a test. However, we don't have a unit test for all vulnerabilities types.
It will be amazing if we create an engine to test each vulnerability.
This engine would have two verifications:

One to make sure that the engine find the code vulnerability
One to avoid false-positive test

Once we have this motor, it would be great to receive tests from the community.

for tools created using horusec-engine we have only unit tests for leaks. it's good first issue for resolve in horusec improvements of others tools 😄

Hi @otaviojava,
Can you assign it for me?

Hey @mcruzdev how are you?
I believe that @wiliansilvazup  is working on it.
Will, could you sync up?

Hi @mcruzdev , thanks for you interest on contributing for Horusec. We created a new issue #630  with all tests that we should create and some guide to help to create them.

I'm closing this issue since we created a new one on #630 with all the tasks that should be done.


HikariScan: Migrate theme

Closes #5613
Checklist:

[ ] Updated extVersionCode value in build.gradle for individual extensions
[x] Updated overrideVersionCode or baseVersionCode as needed for all multisrc extensions
[x] Referenced all related issues in the PR body (e.g. "Closes #xyz")
[ ] Added the isNsfw = true flag in build.gradle when appropriate
[x] Have not changed source names
[ ] Have explicitly kept the id if a source's name or language were changed
[x] Have tested the modifications by compiling and running the extension through Android Studio
[ ] Have removed web_hi_res_512.png when adding a new extension

did the manga url change? both are on /manga/slug right?

did the manga url change? both are on /manga/slug right?

You're right, the URL didn't change, I saw it on the Wayback Machine.


Update pydeck layer docs to reflect new JSON API

For #2929

Background

Change List

Closed in favor of #3611


⚠ ETF has degraded performance

In 93d2540, ETF (https://markets.hankyung.com/equity-product/etf) experienced degraded performance:

HTTP code: 200
Response time: 6136 ms

Resolved: 마켓맵 performance has improved in bed805e.


Wire up metrics server infra

Remaining work is these steps: https://quip-amazon.com/alrhAWPfLlD4/New-Package-Creation-Guide#temp:C:DSY376b6d37de774b68b6764f441


Where to find the output of "Generate the inference dataset for APC / ATEPC task" ?

When I ran this-
from pyabsa.utils.file_utils import generate_inference_set_for_apc  generate_inference_set_for_apc(dataset_path="/content/dataset")
I got the output- "Process Finished" but I'm unable to find output inference file.

Hi,
the dataset file name should contain the train, test or valid string, please see the existing file names. Once the dataset was processed, its file name will be printed before process finished.

The .txt file which I received output from web browser tool are all "sentences" line after line. Ex-
can you check whether its cancelled completely?
cannot rely on both milk delivery and grocery items.
I get no notification, however the app is really fine
Love this app, but would love it even more if Gantt charts and Calendar view were available on iPhone!
Is this normal?

Got no idea what are the real problem. The PDT tool should give us several files, including a .txt file that formated as existing apc datasets. It seems your output is not expected. Can you tell us how to reproduce your problem?

I downloaded this repository in my local pc. Then opened the "ABSADatasetPrepareTool.html" file load the csv file(no headers) and assigned the polarity and clicked save. Received 3 outputs as expected- .txt, .csv and .json.
Do I have to install any library or run some files first before working on this web based tool(I have not pip installed PyABSA in my local pc) ?

Can you provide a small cut of your data, e.g., data before process and behind process.

Sure. Here it is- https://imgur.com/a/uJoMOAO

So, I restarted the web tool and finally got the result in the format-
Sentence
AspectWord
Polarity
But still unable to get the inference file after running this piece of code-
from pyabsa.utils.file_utils import generate_inference_set_for_apc generate_inference_set_for_apc(dataset_path="/content/dataset")

Hi,
Here are my suggestions.
make sure your dataset file name dont be confusing, e.g., file name should not contain both 'train' and 'test' string.
use a more detailed dataset_path arg, and it should contain a 'apc' string. Due to distinguish apc datasets and atepc datasets
check your folder if there is the generated inference file, if it exists and doesnt work, please fell free to report.

Hi,
Followed these suggestions, its working now! Thank you.


Update API test tooling: Test gRPC services with gRPCURL & Postman: Remove Postman content

Description
Related to parent issue #31967
This topic covers both testing with gRPCurl and Postman:  Remove Postman instruction.
Page URL
https://learn.microsoft.com/en-us/aspnet/core/grpc/test-tools?view=aspnetcore-8.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/grpc/test-tools.md
Document ID
771cd7a3-e343-1f85-8c8a-a65eeb2dc2ab
Article author
@JamesNK

@JamesNK, just a heads up that I will be removing the Postman part of this doc per the latest API test tool recommendations.


Add virtual joystick input

Visually, it should look similar to this.
First, the API design should be proposed based on what information we want to obtain from the joystick. Presumably, we want a vector from the joystick center to where the player pointer (finger / cursor) is, when the joystick is being pressed. Using the vector we can obtain both the direction and length (magnitude that we can use to estimate force).

Initial API design complete, see initial commit
The commit includes two TODO placeholders, which primarily require UI design and implementation. See link in the description for visual reference (does not have to look exactly like that).

@ross-holloway94 interested? There is also a sample included in the above commit to see how the virtual joystick would work.

Yeah, I'll have a look this week and see if I can get my head around it

Okay, initial thoughts are that the VirtualJoystick should instead be  composed of two Circle objects: A background and a foreground.
Then:

The center of the foreground circle shall not be dragged past the edge of the background circle. If those points are equal, the maximum possible magnitude is returned.
The foreground circle shall listen for dragging events
On release, the foreground circle shall reset its position back to the center of the background circle.

Yes, sounds good, you should be able to use the pressedProperty() of the Parent (which VirtualJoystick is) to see if the foreground circle should be moved to where player input (cursor or finger) is.

Good stuff! :)


Update to Azimuth nomenclature

Ship -> point, etc.

Probably not? This is about Urbit key generation, and Urbit deals with ships. Points are an Azimuth thing, and while they lie at the foundation of Urbit ships, they are not the surface.

There is, of course, an argument to be made about turning this and our spec into being about Azimuth wallets, but I'd counter that by saying that different applications of Azimuth have different requirements as far as wallets are concerned.

Hard to say.  I'd argue that in the general case one is generating a wallet for an Azimuth point, not specifically a ship (which, as you state correctly, is an Arvo-level concept).
But perhaps you're right.  My main concern is that the switching of nomenclature from 'point' to 'ship' in Bridge for keygen arguments alone feels weird. 😄

Bridge is an Urbit tool for dealing with Urbit assets, and so should already be talking about ships rather than points. Exception there is, of course, the azimuth-js interfacing.

eyes cutlass

This one doesn't seem necessary, and hasn't gone anywhere, so let's shut 'er down.


Continuous fuzzing

Proposing to integrate with Fuzzit for automated bug discovery.
This fuzzes code generation and unmarshaling of some generated code. It's complementary to nice existing fuzzing of marshaling. For unmarshaling I generated from the nice test struct in the existing fuzzing.
If you wanted to get marshaling running on the platform too I think it's possible to link up by fuzzing the entropy used to populate objects. If you're interested I can look into it.
There's a successful run under my Travis account. The PR build will fail due to missing an API key. If you're interested in trying it setup is like this:

In Fuzzit create targets ffjson-generate ffjson-unmarshal.
In Fuzzit settings grab an API key. In repo settings in Travis paste it to envvar FUZZIT_API_KEY.

If you commit tests/fuzz/generated.go every pull request will have to update it as well otherwise it would never fuzz the latest version. It's much better if this file is automatically generated only when the fuzzer is build.

The problem I had with setting it in the repo settings is that it won't be set for pull requests which prevented me from running local-regression tests in pull requests.

Thanks for looking at it @pquerna.

Thanks a lot for reviewing @pquerna. I think you can remove me from the org in settings, then it's all yours.

Oh, I see the fuzz stage failed. Is it possible you used an API key from your default org? They give different keys to the different orgs. If that was it, you can switch org in the drop down then go to settings to get the right key.


Changing console.logs to match spec

Just a heads up: this is going to need rebasing before it can land

Ready to merge @rwaldron or @johnnyman727 ?

looks good to me


HBASE-24664 Some changing of split region by overall region size rath…

…er than only one store size
(cherry picked from commit b434ccaaeaeb08b3088a6a437e5d49ef1fcbb0cb)

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 44s
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.3 Compile Tests _

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

+1 :green_heart:
mvninstall
4m 24s
branch-2.3 passed

+1 :green_heart:
compile
2m 47s
branch-2.3 passed

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

-0 :warning:
javadoc
0m 19s
root in branch-2.3 failed.

-0 :warning:
javadoc
0m 17s
hbase-common in branch-2.3 failed.

-0 :warning:
javadoc
0m 40s
hbase-server in branch-2.3 failed.

_ Patch Compile Tests _

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

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

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

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

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

-0 :warning:
javadoc
0m 19s
hbase-common in the patch failed.

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

-0 :warning:
javadoc
0m 16s
root in the patch failed.

_ Other Tests _

-1 :x:
unit
15m 26s
root in the patch failed.

47m 48s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 48b3723c0107 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.3 / c582fb5d11

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-root.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-common.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-common.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-root.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/1/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-root.txt

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

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

modules
C: hbase-common hbase-server . U: .

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 43s
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.3 Compile Tests _

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

+1 :green_heart:
mvninstall
3m 38s
branch-2.3 passed

+1 :green_heart:
compile
2m 12s
branch-2.3 passed

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

+1 :green_heart:
javadoc
3m 11s
branch-2.3 passed

_ Patch Compile Tests _

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

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

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

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

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

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

_ Other Tests _

-1 :x:
unit
23m 41s
root in the patch failed.

54m 35s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 7288eb6ff3ca 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.3 / c582fb5d11

Default Java
1.8.0_232

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/1/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-root.txt

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

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

modules
C: hbase-common hbase-server . U: .

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m 42s
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.3 Compile Tests _

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

+1 :green_heart:
mvninstall
5m 14s
branch-2.3 passed

+1 :green_heart:
checkstyle
2m 46s
branch-2.3 passed

+0 :ok:
refguide
12m 55s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
spotbugs
11m 45s
branch-2.3 passed

_ Patch Compile Tests _

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

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

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

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

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+0 :ok:
refguide
7m 30s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

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

+1 :green_heart:
spotbugs
12m  8s
the patch passed

_ Other Tests _

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

89m 10s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/1/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle refguide xml

uname
Linux 6517cf2445d7 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.3 / c582fb5d11

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/1/artifact/yetus-general-check/output/branch-site/book.html

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/1/artifact/yetus-general-check/output/patch-site/book.html

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

modules
C: hbase-common hbase-server . U: .

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 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.3 Compile Tests _

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

+1 :green_heart:
mvninstall
4m  7s
branch-2.3 passed

+1 :green_heart:
checkstyle
2m 29s
branch-2.3 passed

+0 :ok:
refguide
12m 20s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
spotbugs
13m 29s
branch-2.3 passed

_ Patch Compile Tests _

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

+1 :green_heart:
mvninstall
4m 17s
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:
xml
0m  2s
The patch has no ill-formed XML file.

+0 :ok:
refguide
8m 13s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

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

+1 :green_heart:
spotbugs
14m 28s
the patch passed

_ Other Tests _

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

94m  8s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/2/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle refguide xml

uname
Linux 18ae5e5263b2 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.3 / c582fb5d11

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/2/artifact/yetus-general-check/output/branch-site/book.html

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/2/artifact/yetus-general-check/output/patch-site/book.html

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

modules
C: hbase-common hbase-server . U: .

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 41s
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.3 Compile Tests _

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

+1 :green_heart:
mvninstall
4m  8s
branch-2.3 passed

+1 :green_heart:
compile
2m 39s
branch-2.3 passed

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

-0 :warning:
javadoc
0m 18s
root in branch-2.3 failed.

-0 :warning:
javadoc
0m 16s
hbase-common in branch-2.3 failed.

-0 :warning:
javadoc
0m 37s
hbase-server in branch-2.3 failed.

_ Patch Compile Tests _

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

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

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

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

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

-0 :warning:
javadoc
0m 17s
hbase-common in the patch failed.

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

-0 :warning:
javadoc
0m 16s
root in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
163m 20s
root in the patch passed.

194m 55s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 80d73717a951 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.3 / c582fb5d11

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/2/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-root.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/2/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-common.txt

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

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-common.txt

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

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-root.txt

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

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

modules
C: hbase-common hbase-server . U: .

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 41s
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.3 Compile Tests _

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

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

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

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

+1 :green_heart:
javadoc
3m 17s
branch-2.3 passed

_ Patch Compile Tests _

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

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

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

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

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

+1 :green_heart:
javadoc
3m 50s
the patch passed

_ Other Tests _

-1 :x:
unit
319m 11s
root in the patch failed.

355m 10s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/2/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux db6a1fc45dcf 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.3 / c582fb5d11

Default Java
1.8.0_232

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/2/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-root.txt

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

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

modules
C: hbase-common hbase-server . U: .

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 38s
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.3 Compile Tests _

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

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

+1 :green_heart:
checkstyle
2m 29s
branch-2.3 passed

+0 :ok:
refguide
12m 14s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
spotbugs
13m 33s
branch-2.3 passed

_ Patch Compile Tests _

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

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

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

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

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+0 :ok:
refguide
8m 10s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

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

+1 :green_heart:
spotbugs
15m  2s
the patch passed

_ Other Tests _

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

92m 59s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/3/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle refguide xml

uname
Linux 868db182ffad 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.3 / 89e3d3c399

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/3/artifact/yetus-general-check/output/branch-site/book.html

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/3/artifact/yetus-general-check/output/patch-site/book.html

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

modules
C: hbase-common hbase-server . U: .

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ branch-2.3 Compile Tests _

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

+1 :green_heart:
mvninstall
5m 45s
branch-2.3 passed

+1 :green_heart:
compile
3m 27s
branch-2.3 passed

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

-0 :warning:
javadoc
0m 19s
hbase-common in branch-2.3 failed.

-0 :warning:
javadoc
0m 46s
hbase-server in branch-2.3 failed.

-0 :warning:
javadoc
0m 17s
root in branch-2.3 failed.

_ Patch Compile Tests _

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

+1 :green_heart:
mvninstall
5m 41s
the patch passed

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

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

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

-0 :warning:
javadoc
0m 20s
hbase-common in the patch failed.

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

-0 :warning:
javadoc
0m 18s
root in the patch failed.

_ Other Tests _

-1 :x:
unit
222m  2s
root in the patch failed.

263m 29s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/3/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 47629ce4aafc 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.3 / 89e3d3c399

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/3/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-common.txt

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

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/3/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-root.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/3/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-common.txt

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

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/3/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-root.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/3/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-root.txt

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

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

modules
C: hbase-common hbase-server . U: .

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 36s
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.3 Compile Tests _

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

+1 :green_heart:
mvninstall
4m  6s
branch-2.3 passed

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

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

+1 :green_heart:
javadoc
3m 13s
branch-2.3 passed

_ Patch Compile Tests _

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

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

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

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

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

+1 :green_heart:
javadoc
3m 45s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
378m 42s
root in the patch passed.

414m 38s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2086/3/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux aed1bb60f45a 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.3 / 89e3d3c399

Default Java
1.8.0_232

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

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

modules
C: hbase-common hbase-server . U: .

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.

TEST-org.apache.hadoop.hbase.util.TestHBaseFsckCleanReplicationBarriers.xml.[failed-to-read]

This failure on jdk11 seems unrelated to this PR.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 36s
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.3 Compile Tests _

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

+1 :green_heart:
mvninstall
3m 35s
branch-2.3 passed

+1 :green_heart:
checkstyle
2m  3s
branch-2.3 passed

+0 :ok:
refguide
11m 31s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
spotbugs
10m 16s
branch-2.3 passed

_ Patch Compile Tests _

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

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

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

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

+1 :green_heart:
xml
0m  2s
The patch has no ill-formed XML file.

+0 :ok:
refguide
7m  0s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

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

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

_ Other Tests _

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

77m  9s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2086/1/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle refguide xml

uname
Linux 8d52c8301be8 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.3 / c6744c0a8b

refguide
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2086/1/artifact/yetus-general-check/output/branch-site/book.html

refguide
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2086/1/artifact/yetus-general-check/output/patch-site/book.html

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

modules
C: hbase-common hbase-server . U: .

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 33s
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.3 Compile Tests _

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

+1 :green_heart:
mvninstall
3m 32s
branch-2.3 passed

+1 :green_heart:
compile
2m 11s
branch-2.3 passed

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

+1 :green_heart:
javadoc
3m  2s
branch-2.3 passed

_ Patch Compile Tests _

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

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

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
309m 43s
root in the patch passed.

340m 38s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2086/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 539accb1b62a 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.3 / c6744c0a8b

Default Java
1.8.0_232

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

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

modules
C: hbase-common hbase-server . U: .

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.

Ping. @wchevreuil


Use Binary File Format to Store Simple Selector State

The insertion process at the selector is a bottleneck. Postgres inserts with 80-100k rows/second, which means waiting for 30+ minutes for a day of Criteo data to be inserted.
For many simple strategies (retraining/finetuning/random subsampling/…), we actually do not need any complicated Postgres query. We can implement this on a simple binary file format. We can leverage a file structure such as /tmp/<pipeline id>/<trigger id>/<files containing binary data>
These files can be binary fixed size tables with at least the sample ID as a column. We need to build a nice abstraction around this, such that strategies can add other fields as well. For example, GDumb might require to fetch and store the labels of all data from the storage. With #261 in mind, this would be the place where we go from intervals to sample level information.
For other strategies that require more complex queries or state across components (e.g., storing information from the training), we can still keep the SelectorStateMetadata table. For example, a strategy similar to RHO-LOSS might be a use case of such a table.
Superseeds #204. Will probably include #250.

This is implementing the LocalStorageBackend, which @Sipondo started to work on - thanks!

Solved by #364!


Broken variable assignments with parenthesised expressions

If a variable is assigned to a parenthesised expression, then it is not thought to be already declared. Fix this so it is either regarded as "already declared", or alternatively "not yet declared".
For example:
a = 10 + (a = 1)
----------------------------
a   11   INTEGER_OBJECT
----------------------------
11

This turns out to be working as expected.


Switch unoptimized handlers from spatial editor viewport to optimized ones

Sorry, completely forgot about it.
They are also being pushed to the godot-design repo: https://github.com/godotengine/godot-design/pull/28

Thanks!


[WIP] Fix missing Flow Aggregator logs in the artifacts when tests failed

In this commit, we fix missing Flow Aggregator logs in the artifacts
when tests failed. Also we add verbosity level of Flow Aggregator to
help debugging when tests failed.

Codecov Report

Merging #2621 (b5e68fa) into main (b10a794) will decrease coverage by 6.69%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #2621      +/-   ##
==========================================
- Coverage   60.42%   53.73%   -6.70%
==========================================
  Files         283      283
  Lines       22455    22510      +55
==========================================
- Hits        13569    12096    -1473
- Misses       7465     9129    +1664
+ Partials     1421     1285     -136

Flag
Coverage Δ

kind-e2e-tests
35.37% <100.00%> (-12.05%)
:arrow_down:

unit-tests
42.00% <0.00%> (+0.06%)
:arrow_up:

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


Refactor reactivity system to use version counting and doubly-linked list tracking

This PR refactors the core reactivity system to use version counting and a doubly-linked list data structure inspired by Preact signals.
It brings some improvements and solves some issues around computed.
Bug fixes
close #10236
close #10069
PRs made stale by this one
close #10290
close #10354
close #10189
close #9480
@vue/reactivity API surface changes
diff
These are changes to the @vue/reactivity package only and do not affect Vue core's public API surface.

Removed pauseScheduling and resetScheduling exports (never publicly documented)
Removed deferredComputed export (previously deprecated)
Added EffectFlags export (for Vue core internal use)

Memory Usage Improvements
Given a test case with 1000 refs + 2000 computeds (1000 chained pairs) + 1000 effects subscribing to the last computed, comparing the total memory used by these class instances:

Before (3.4.19): 1426k
After (this PR): 631k (-56%)

A computed now also lazily subscribe to deps only when itself gets the first subscriber, and unsubscribes when it loses all subscribers. This means they are more reliably garbage-collected, including in SSR.
Performance Comparison
Reasonable gains across the board, most notably for single ref invoking multiple effects (+118%~185%) and reading multiple invalidated computeds (+176%~244%).

 The effects are stopped / made inactive when the owner unmounts, and in 3.4 leading to issues like #10236.
Also, previously during SSR we disable computed effects to avoid tracking overhead. But to avoid cost of repeated computation, we make computeds cached during render, leading to issues like #10069.
With this PR, computeds are now a subscriber type with its own invalidation logic. They can longer be "stopped" and thus can never be stale. During SSR, we use a global mutation version counter to provide a fast path for repeated access.

/ecosystem-ci run

The snapshot fail for Vant should be expected - the styles of the components are computed refs and should be updated when the parent container gets more children linked. Previously it just never got updated and the new behavior is considered more correct.
/cc @chenjiahan

Get it 👌 I will temporarily skip the failed test cases in Vant until the next version of Vue is upgraded.

Congratulations! You have finally passed the tests for the absence of unnecessary side effects and your reactivity system is suitable for use in production.
Unfortunately, you have not yet got rid of unnecessary recalculations. @preact/signals is not the best option to follow here.

https://mol.hyoo.ru/#!section=bench/bench=reactivity

@nin-jin our priority is making improves while retaining backwards compatibility, not "winning" in arbitrary micro-benchmarks.

Don't be offended by my praise. Accept it with pride. But don't get too cocky. A year ago, in my analysis, I classified your library as unsuitable for production. In this patch, you fixed it. Now I should update my analysis and move you significantly higher. But if you read my series of articles on reactivity, you may understand how to catch up with the leaders without even breaking backward compatibility.

They tell me here that you use a double double linked list to implement pub/sub.

This is extremely wasteful of memory (from 44 bytes per edge) and heavily fragments it, which increases processor misses past caches.
In a recent article on pub/sub, I talked about how to achieve a more compact storage of edges (from 16 bytes per edge) while ensuring constant asymptotic of all operations.

mol.hyoo.ru/#!section=bench/bench=reactivity

@nin-jin The result seems to be based on Vue 3.4.x rather than this PR.

Hello yyx, I read your pr in detail, thx your this amazing work!
But because of my stupidity, I don't quite understand why double-linked lists improve memory efficiency
i guess use double-linked lists ,It makes it easier to implement certain functions, but what else does it mean , can you give me some.
Can you give me a hint to help me understand,thx.

@moushicheng Try to answer your question(I haven't read this change carefully yet. I plan to spend some time to finish reading the source code of preact/signals first.).
In the current version of Vue, there are many cases of recursive calls, but by using double-linked lists, the number of recursive operations will be reduced. This means that the call stack will be reduced and memory usage will also be significantly improved.

Some of it is likely only relevant to Preact signals, and not necessarily this change here in Vue, but there's a blog article going over why we used linked lists (amongst other things) here: https://preactjs.com/blog/signal-boosting


[Packager] Source-map explicitly enabled, but lost when --minify is enabled

TLDR: I enabled source maps in node_modules/react-native/local-cli/bundle.js by explicitly setting inlineSourceMap: true, in the code. Then running react-native bundle --out js.bundle works, but react-native bundle --minify --out js.bundle loses the source maps. I am looking to generate a source map between the original files and the minified bundle.
We use a minified bundle in production and send the error string to a server to accumulate errors (Crashlytics). The problem at the moment is that the error message is not helpful as it is completely minified code without source maps.
Is there a way to hand over a separate source-maps file in production, or be able to keep a source-map file on the server so that the server could link the error to the correct place in code? Anyone who has done this?
I was looking around and something like this looks useful: https://errorception.com/docs/sourcemaps (it fetches source maps on the remote server to help with debugging.)

Looks like this was fixed!

Thanks @jsierles - Yes, it was! I forgot the close this when I closed the PR.


Kingpin setAnnotation(RLMObject) causes realm::IncorrectThreadException:

Issue Description
Hi, I'm working on a map-based iOS project, and I'm trying to persist my annotation objects through Realm. Also, the annotations are managed by Kingpin's clustering controller. Unfortunately, this is causing a 'realm::IncorrectThreadException:'
Steps to Reproduce

Create an AnnotationObject subclassing a Realm Object and conforming to MKAnnotation protocol.
Use Kingpin to manage the clusters on the map.
Add a non-manged AnnotationObject instance to Realm.
Set the same instance to be managed form Kingpin clustering controller.

Version of Realm and Tooling
Realm version: Latest version.
Kingpin version: 0.3
Xcode version:  7.3.1
iOS/OSX version: iOS 9.3.5 / 10

Maybe you do some staff in separate thread like dispatch_get_global and this it the reason why you have this exception.

You'll get this exception if external libraries, or your code, is using Realm Objects created or added to the Realm on a different thread. This violates Realm's thread confinement rules and therefore throws an exception, to prevent you from using potentially stale or incorrect data.
See Realm's docs on Threading to learn more about how Realm deals with threads.

@FedericoPaliotta did you resolve this issue? Can we close this issue or do you still need help?

My apologizes, I got caught in this project and didn't take a minute to
follow this thread. I'm so sorry. 😔
The issue is still there, but we ended up decoupling the object that we use
with kingpin and the one we store in realm. So not exactly resolved the
issue itself, but feel free to close it on gitHub.
We tried all of the above suggested as well as what the documentation says.
In any case, we could not get it to work. It's really weird, even though we
create a new realm object each time we access an annotation object, and
even calling fictions like beginTransaction, commitTransaction and so on,
nothing seems to save us from that realm::IncorrectThreadException.
We were able to dig into kingpin's code (I can show you if you are
interested) and isolate the code where the exception raises, but we have no
clue of why that happen.
Thanks for your support.
Federico Paliotta
On Monday, October 10, 2016, Dmitry Obukhov<EMAIL_ADDRESS>wrote:

@FedericoPaliotta https://github.com/FedericoPaliotta did you resolve
this issue? Can we close this issue or do you still need help?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/realm/realm-cocoa/issues/4106#issuecomment-252589777,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APJncUaq32GBZv-cRO06qxF6H7AUMKWEks5qyh4mgaJpZM4J_vyR
.

@FedericoPaliotta thanks for your response! It would be great if you could provide some sample code that causes this exception for you, so we can try to help with this.

Hi, unfortunately I’m not allowed to disclose any code for the actual
project I’m working on, but I’ve made this
https://github.com/FedericoPaliotta/RealmKingpin-IssueSample sample
project, replicating the same scenario causing the issue.
I didn’t had time to add the different kind of (non)solutions we tried. So
the code as it is in the sample project is just meant to cause the same
issue. But, the architecture needs to be like described, viewControllers
talk to a dataStore singleton which is in charge of requesting data from a
server an persist it in realm..
Let me know if you have any questions
Best,
Federico Paliotta
2016-10-10 8:56 GMT-04:00 Dmitry Obukhov<EMAIL_ADDRESS>
@FedericoPaliotta https://github.com/FedericoPaliotta thanks for your
response! It would be great if you could provide some sample code that
causes this exception for you, so we can try to help with this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/realm/realm-cocoa/issues/4106#issuecomment-252610599,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APJncUMVMMCNpcTeGs0S7BTG5rqP7Xtwks5qyjXjgaJpZM4J_vyR
.

You've got this exception because you create AnnotationObjs on background thread (https://github.com/FedericoPaliotta/RealmKingpin-IssueSample/blob/master/RealmKingpinSample/RealmKingpinSample/DataStore.swift#L43) and then trying to access these instances  on the main thread.
I'd suggest you to not to pass these instances via callback from fetchAnnotations method but use Fine-Grained Notifications for updating the map view, check out this tutorial: https://realm.io/news/marin-todorov-fine-grained-notifications/

Closing since @stel's last comment seems to have correctly diagnosed the problem and offered a solution.

That's cool. Thanks for your support! ;)
On Monday, October 17, 2016, JP Simard<EMAIL_ADDRESS>wrote:

Closing since @stel https://github.com/stel's last comment seems to
have correctly diagnosed the problem and offered a solution.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/realm/realm-cocoa/issues/4106#issuecomment-254368131,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APJncaJJl7-eBPdGbsxoK5pr3O7SkgtBks5q1AqzgaJpZM4J_vyR
.


Calling .clear() while elements are in the cache causes an exception when they are subsequently attempted to be purged as stale

TypeError: this.expirations[exp] is not iterable
    at TTLCache.purgeStale (node_modules/@isaacs/ttlcache/index.js:204:41)
    at Timeout._onTimeout (node_modules/@isaacs/ttlcache/index.js:79:41)
    at listOnTimeout (node:internal/timers:564:17)
    at process.processTimers (node:internal/timers:507:7)

https://github.com/isaacs/ttlcache/blob/1fe77335fd4a13036af1fa7bd69d0e66267a8d86/index.js#L204

This may be related to https://github.com/isaacs/ttlcache/issues/16 where the internal state seems to be corrupted within my dispose() method and subsequently performing mutations on the collection from within it.


The future of jsforce

Hey folks! We have some exciting news to share.
After talking with @stomita , we've agreed the Salesforce CLI team will help maintain jsforce!
jsforce is a core component of the Salesforce CLI, Salesforce Extensions for VSCode, DevOps Center and a bunch of other Salesforce tools and we hope we can help Shinichi keep the project alive while delivering new features.
We know there hasn't been much activity triaging issues and PRs except for a few specific bug fixes/features, you can expect us to be more active in the repo while we work towards the v3 GA.
Dropping support for old node and browsers
jsforce v2 has been in beta for almost 3 years supporting node >= v8 and some old browsers (polyfills).
To avoid breaking projects already using v2 we plan to skip and go straight to v3 for the GA, requiring node >= 18 (current LTS) and modern browsers.
Browser usage
While we don't use jsforce in browsers (CLI and others run via node), we are committed to keep jsforce an isomorphic library.
We've already improved our CI test setup to run browser tests on latest Chrome, updated webpack/babel deps and fixed some flaky tests to ensure a safe path while we finish the last bits of work.
Remaining work

[ ] Migration guide v1 → v3
[ ] Triage issues and PRs targeting v2 branch
[x] Documentation equivalent to the current jsforce.github.io (http://jsforce.github.io/). PR https://github.com/jsforce/jsforce/pull/1362
[ ] Drop support for old node and browsers
[ ] node-only release, see: https://github.com/jsforce/jsforce/issues/1374
[ ] Annotations to the code for API references.
[x] Run CLI tests on PRs to catch regressions PR https://github.com/jsforce/jsforce/pull/1359
[ ] Run node test on Windows
[ ] Automate TS typegen (followup issue)

@cristiand391 how can we be helpful? The remaining work is unclear in how we can participate.

we hope we can help Shinichi keep the project alive while delivering new features.

This is fantastic news! Very cool that Salesforce is investing in open source. As a Salesforce user/customer, very glad to see this happening as this library is very important to us as well.
Would love to know if Salesforce will be sponsoring Shinichi or any other open source developers?
Also curious how Salesforce will prioritise work - will it be any/all of the open issues, or issues with most activity, or PRs the community puts forward, or more tightly focused on features that more closely align with the CLI team's needs? I imagine knowing this might help I or others know how best to collaborate.

@gmaliar
The CLI team is currently working on the listed work above. I wouldn't feel comfortable asking people to contribute while we still have a ton of PRs to triage. That said, if anyone is interested in working on something, just ping me in the issue/pr and we can discuss any fix/feature request before submitting a PR 👍🏼

@techieshark

Would love to know if Salesforce will be sponsoring Shinichi or any other open source developers?

Salesforce has a program called FOSS Fund where employees can nominate and vote on projects to receive $10K, this is done every quarter. I know jsforce won it a few years ago (before I joined Salesforce) but seems it ended up rejected, see:
https://opencollective.com/salesforce/expenses/40748
@stomita do you remember what happened with that grant?
Anyway, the one for this quarter is closed but I would expect jsforce could be nominated for the next one (will be checking with the program manager since it's jsforce isn't owned by Salesforce but now we help maintain it).
I'm not aware of other Salesforce program to fund individual developers.

Also curious how Salesforce will prioritise work - will it be any/all of the open issues, or issues with most activity, or PRs the community puts forward, or more tightly focused on features that more closely align with the CLI team's needs? I imagine knowing this might help I or others know how best to collaborate.

We'll probably be fixing a few bugs as we triage issues and PRs targeting v2.
Features/bug fixes that align with our team's need would be our priority but as part of maintainers we'll also review community contributions and/or work on stuff not related to the CLI as much as we can.
In the past other internal teams offered to work on new features and we helped them reviewing/testing (Heroku added support for the Bulk V2 api in jsforce v2).

Sorry to disturb you by asking questions here. I would like to ask if there is any progress on the following issues?
I am using webpack5 now and I still get errors as below

Hey @FeiPengDev, sorry for the late reply. If you still have issues with webpack 5 see this comment: https://github.com/jsforce/jsforce/issues/1222#issuecomment-1800209924

node-only plan: https://github.com/jsforce/jsforce/issues/1374
feedback is welcome 👍🏼

I'm also curious to know about documentation for V2 and V3. Does the currently hosted documentation at https://jsforce.github.io/ reflect the changes already in the V2 beta version? I'm unable to find any reference to a version number other than what is mentioned in specific method documentation -- but i'm assuming that the live docs refer to the latest stable release, and not V2.
I see the TODO for Documentation (linked below) is marked as complete. Is the command referenced a way to generate docs locally?
[X] Documentation equivalent to the current [jsforce.github.io](http://jsforce.github.io/) (http://jsforce.github.io/). PR https://github.com/jsforce/jsforce/pull/1362

Hey @john-bflow-mcgowan , sorry for the late reply 🙏🏼

Does the currently hosted documentation at https://jsforce.github.io/ reflect the changes already in the V2 beta version?

no, we had those under https://jsforce.github.io/jsforce/doc/ for v2 but had to revert back to v1 docs because of the current docs setup.

I see the TODO for Documentation (linked below) is marked as complete. Is the command referenced a way to generate docs locally?

yeah, those generate API docs using typedoc, the end result is smt like this:
https://forcedotcom.github.io/sfdx-core/
but that's just the API reference, the document section will also be updated for v3 changes
https://jsforce.github.io/document/

@cristiand391 Is there any expected release date for v3?

I would like to request that the base package be truly isomorphic, as it is not today. With many frameworks that do server-side rendering (SSR), like Sveltekit and Next.js, this library does not work. These run javascript on the server but do so with a browser runtime (not node) for rendering, so if you include node modules like Buffer, it will fail to build and run.
For example, if you import jsforce like this:
import jsforce from 'jsforce';
And then when you attempt to build for a serverless environment like Cloudflare Pages, you will receive the following error:
✘ [ERROR] Could not resolve "buffer"

    node_modules/core-util-is/lib/util.js:103:27:
      103 │ exports.isBuffer = require('buffer').Buffer.isBuffer;
          ╵                            ~~~~~~~~

  The package "buffer" wasn't found on the file system but is built into node. Are you trying to
  bundle for node? You can use "platform: 'node'" to do that, which will remove this error.

As this library is rebuilt to use modules, it would be good to import node-specific libraries with the following import as many hosting platforms will automatically polyfill these:
// Do this:
import { Buffer } from 'node:buffer';

// Do not do this:
import { Buffer } from 'buffer';

@tehnrd which version of jsforce are you using?
that import comes from core-util-is which I don't see being shipped in prod. versions.

These run javascript on the server but do so with a browser runtime (not node) for rendering, so if you include node modules like Buffer, it will fail to build and run.

Yeah, by isomorphic we mean node + browsers for now.
Not sure if we would "officially" support new runtimes now, but maybe if it's not too much effort we can help with stuff like you mentioned about imports, feel free to open new issues if something doesn't work with the node-compat mode 👍🏼 .
IIRC, using node:* imports triggered some errors in the build/bundle process with webpack but I can check again.

I tried 1.11.1 and 3.0.0-next.3 but I need to do some deeper debugging.
@cristiand391 ya, I will spin up a new issue. It think (haven't investigated too much) the issue is that there is code directly referencing modules like Buffer (and others) object globally but this isn't recommended in the official node docs and it should be explicitly imported with the node: prefix. This way it can easily be polyfilled when doing builds across runtimes.

While the Buffer class is available within the global scope, it is still recommended to explicitly reference it via an import or require statement.

const { Buffer } = require('node:buffer');

https://nodejs.org/api/buffer.html#buffer

@GBvanDam

open up the Query class such that we can make calls like new Query(conn, { ...conditions }, locator).toSOQL() (currently this class is protected)

Actually the find() method returns Query object so you can do the following:
const soql = await conn.sobject("Contact").find({ ...conditions }).toSOQL();
const queryResult = await conn.query(soql);

One more question on jsforce, as far as I can see uploading files or blobs (especially the blob upload way with the highest file size limit) is not part of the jsforce scope. Is that intentionally, or am I overseeing something once again?

@GBvanDam yes, this isn't implemented yet in jsforce.
have you seen this?
https://github.com/jsforce/jsforce/discussions/1426#discussioncomment-9501281

@cristiand391 When may we expect a release date for v3?

@Joemusarurwa pretty much all the work is done now, we'll wrap up last details about jsforce v1 (mostly about maintenance) and get back last week.

Hi @cristiand391 any news about the release date ? :)

we plan to do it next week. FYI @stomita, I've been trying to reach out to you via email to get your thoughts 🙏🏼

Is there any upgrade documentation with breaking changes for v1 to v3?

@matthewblewitt yes, see the MIGRATING*.md docs in the v3 branch:
https://github.com/jsforce/jsforce/tree/3.0

v3 is GA 🚀
https://github.com/jsforce/jsforce/discussions/1529
will let this issue pinned for a bit, feel free to continue discussions in the announcement post.


Fix protocol period timing bug by updating the protocol timing metric af...

...ter every ping
This was effectively a one-line change that has been broken since the move over to tchannel. This bug caused the protocol period to be around 400ms stable-state instead of 200ms. The reason is because the timing metric wasn't updated after ping responses were received. This was subtle logic baked into the HTTP transport. I need to harden this against future issues. But I'm punting on that for now.
I took this opportunity to clean some code out of index.js and move it into Gossip. I think this separates concerns better. Everything having to do with the gossip protocol period is managed by the Gossip abstraction.
The one-line fix is literally the line that now reads: this.protocolTiming.update(new Date() - pingStartTime);
@Raynos @mranney

lgtm.


we are not properly escaping function column names in the column char estimate profiling

This appears to be a new kind of error, since we've had this feature for a few releases and it has been working pretty efficiently to date.

@AdityaHegde mind taking a look at this bug? I think this can be traced back to the column size estimation profile query.
Here's the dataset that uncovered the bug, w/ the query above in the screenshot (this is from Marissa)
senate.csv


Delete Main.storyboard and ViewController

delete Main.storyboard (fix #3 ) and ViewController.swift

Added Users.storyboard


Increment version for core releases

Increment package version after release of com.azure azure-core

@srnagar @alzimmermsft looks like we might need to run the script to update some of the updated service directories to exclude their pom files.


Unknown custom element:  when using vueMultiSelect latest version

package.json file
 "dependencies": {     "chartist": "^0.10.1",     "chartist-plugin-pointlabels": "0.0.4",     "font-awesome": "^4.7.0",     "highlightjs": "^9.8.0",     "jquery": "^3.1.1",     "select2": "^4.0.3",     "vue": "^2.1.0",     "vue-chartist": "^2.0.2",     "vue-datatable": "^1.0.4",     "vue-multiselect": "^2.0.0-beta.15",     "vue-router": "^2.1.1",     "vue-strap": "^1.1.34",     "vuex": "^2.1.1"   }
main.js file
`import VueFormGenerator from "vue-form-generator/dist/vfg-core.js"
import Multiselect from 'vue-multiselect'
Vue.use(VueFormGenerator)
Vue.use(Multiselect)
Vue.component(Multiselect)`
Component
``
When I added to the package.json this
"vue-multiselect": "next", as per [here](https://github.com/icebob/vue-form-generator/issues/100)
It worked
but there is this new error
vue.common.js:436 [Vue warn]: Unknown custom element:  - did you register the component correctly? For recursive components, make sure to provide the "name" option.

Please format better the content of your message.

Here is the guide to use Github Markdown. Also, provide a jsfiddle so we can test the problem.


Fix creation QtViewer for ViewerModel with already added layers

Description

This PR fix bug that prevents the creation of QtViewer for models that already have added layers.
Type of change

[x] Bug-fix (non-breaking change which fixes an issue)

References

How has this been tested?

[ ] example: the test suite for my feature covers cases x, y, and z
[ ] example: all tests pass with my change
[ ] example: I check if my changes works with both PySide and PyQt backends
as there are small differences between the two Qt bindings.

Final checklist:

[x] My PR is the minimum possible work for the desired functionality
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[ ] If I included new strings, I have used trans. to make them localizable.
For more information see our translations guide.

I do not understand this test failure.

I tried to del viewer and viewer_model as it's unlikely it will be collected by the wait if there are still local references inside the test, as well as add a gc.collect(), if not I'll try to run the test with and collect the object graph.


Change config .json file to .env files

create-react-app supports .env files for environment specific variables. We should be using those instead of async loading the config.json files.

Mohs brings up the point that this would mean that our builds are no longer environment agnostic, so this is a no go. Instead, we should make sure the config is loaded at early in the app load so if can be referred to synchronously.

Closing this because we're taking a different approach


FileNotFoundException: cwebp_tmp/dwebp

io.github.biezhi.webp.WebpIOException: java.io.FileNotFoundException: cwebp_tmp/dwebp: open failed: ENOENT (No such file or directory)
        at io.github.biezhi.webp.WebpIO.init(WebpIO.java:58)
        at io.github.biezhi.webp.WebpIO.<init>(WebpIO.java:27)
        at io.github.biezhi.webp.WebpIO.create(WebpIO.java:63)

I think you must add those library files cwebp dwebp in the project. I think It looking for temp folder which is created by WebIo.java file (you can check that in src folder).

@STG284  I released a new version, do you still have that question?


[secrets] Align passphrase to lock code when applicaple. Contributes to JB#36797

LGTM although there is typo in commit message: applicaple -> applicable

Fixed typo. Thanks @chriadam .


Error: "Failed to run Trivy scan" with Trivy v0.23.0

Having Trivy v0.23.0 installed on my WSL2 Ubuntu 20.04 distro. When trying to use extension two errors pops up:
Failed to run Trivy scan, error: 1 check logs for details. and  Unsupported Trivy version found. Please upgrade to v0.9.1 or higher
From source code and logs I see trivy --format=json --version command is executed and it ends up to flag provided but not defined: -format Trivy error in logs.

this should work on the next release of the extension (shortly) - there was a regression in trivy where it no longer outputs the version in the same way


Option --tarball does not prevent node-gyp from downloading SHASUMS.txt

I try to build node-modules without an internet connection and provide a local tar ball for node-gyp. It would be nice to make node-gyp use a SHASUMS.txt  file in the same directory.

closing due to staleness, but this is probably a good candidate for a pull request if someone wants this sorted out (if it's not already)


Calculate fixed offsets via constants

This allows a custom fixed-size header to be used in theming.

Fixed header and sub-head height, based on LESS variables
Aligns main-content with header
Fixes alignment of closed panel

fec-eregs:

This is a great direction and specifically fixes several little bugs introduced during the notice-and-comment pilot. Only one little question around where a number comes from.

The variable settings come from what I measured the existing .main-head and .sub-head to be. Also replacing the hard-coded numbers seemed to confirm the math. Maybe it's worth renaming header_height -> mainhead_height.

Changes pushed, but there's still some funny business with the .reg-section::before pseudo element. It has it's own offset via negative margin. I'd like to remove that in another PR as I'm sure it will bring up some extra issues but cleans things up overall.

Looks good on ATF and  N&C as well. Nice work!


Use html meta tag / js to redirect result after authorization in oidc authorize endpoint

require #1325
refs #1334
See commit dae84bc
This is workaround for fixing ios version < 13.4 that fails to redirect back to the app after signin with apple in auth ui. We will update sdk to provide params by checking the os version. Not sure if this is a good idea to have such custom response mode, or any better idea?

@kiootic When you have time, would like to hear your thoughts on this. After testing, auth ui works fine in ios app with native sign in with apple, but we hit the bugs of webkit that auth ui failed to redirect back to the custom scheme after sign in with apple. The bug has been fixed in ios >= 13.4, but we do need a workaround for the old version app.
The redirect will work if we return 200 and use html meta tag or js to do the redirect. I added a custom response mode query_html_redirect  in our oidc authorize endpoint, and only the old version ios will add this response mode parameter. Seems not very good though :(
see commit: https://github.com/SkygearIO/skygear-server/pull/1335/commits/dae84bc2ba9d4cedd1af83751960e86ed0ba292a

I think we can always have a page to do the JS/meta tag redirection? We can add a message like 'You're now logged in. Now redirecting to app...' in case redirection takes a bit longer.

You mean authorize endpoint will not return 302 anymore and always do the JS/meta tag redirection?

Yes, at least for this case.

We may want to support form post response mode, which requires such a page to do form submission.
We may need to support prompt = none, which we should not use this page.

The default response mode is query which should be using HTTP redirect. If we do not use HTTP redirect anymore, would our implementation be compliant?

I think it has not mentioned how we do the redirect, as long as we put the result in query?
Section 2.1.  Response Modes
https://openid.net/specs/oauth-v2-multiple-response-types-1_0.html

https://tools.ietf.org/html/rfc6749#section-1.7
Seems any redirect method is fine

Updated! Thanks @kiootic @louischan-oursky :D


Aseprite integration

So, Aseprite is kinda the best software about pixel art around there (and according to me obviously).
I want to be able to have a nice and simple integration with aseprite format and exports. So when you 'load' an aseprite asset into the game, you just have access to everuthing you could want.
That said, I don't know enough the aseprite export right now but this issue will help me keep track of my research about this subject.

https://github.com/aseprite/aseprite/blob/master/docs/ase-file-specs.md


Be an installable Chrome application.

We will need to create a manifest.json file, background.html page, background.js file and an index.html page